cassandra-alpha/feedback
2
0
Issues 8 Activity

Self burns life from 12 to 1 digging for combo while staring down 4 immediate damage this turn and tapping out #34

New Issue
Closed
opened 2026-07-10 20:01:06 +00:00 by bstein · 1 comment
bstein commented 2026-07-10 20:01:06 +00:00
Owner
Copy Link

What happened

image.pngimage.png Agent dug deep for combo parts putting itself into a 'be killed next turn' scenario when it was not in such a range before.

What should have happened

Maybe a little bit of digging would be ok to get lazav a good block transformation or something, but it needed to re-evaluate each further dig to know to keep digging or not.

Category

  • kind: misplay / bridge-runtime / ui-table / metadata-content / ops
  • severity: obvious / debatable / defensible / unknown

Context

## What happened <img width="1440" alt="image.png" src="attachments/b86b763b-05e2-4f7e-bced-2e2580c7ad84"><img width="1440" alt="image.png" src="attachments/24fea9d8-4866-490b-8aa9-026fe680f239"> Agent dug deep for combo parts putting itself into a 'be killed next turn' scenario when it was not in such a range before. ## What should have happened Maybe a little bit of digging would be ok to get lazav a good block transformation or something, but it needed to re-evaluate each further dig to know to keep digging or not. ## Category - kind: misplay / bridge-runtime / ui-table / metadata-content / ops - severity: obvious / debatable / defensible / unknown ## Context - Page URL: https://veles.bstein.dev/table?path=/data/veles-artifacts/logs/dashboard/sp0619-phage-s2026072321-v2-lazav-v22-phelia-v15/duel_commander_phelia_exuberant_shepherd__15_g1_2026072321/game.jsonl - Route: table - Path: /table?path=/data/veles-artifacts/logs/dashboard/sp0619-phage-s2026072321-v2-lazav-v22-phelia-v15/duel_commander_phelia_exuberant_shepherd__15_g1_2026072321/game.jsonl - Backend version: 0.6.21 - Frontend version: 0.6.21 - Sim version: 0.6.21
image.png
858 KiB
image.png
856 KiB
bstein added the
kind/misplay
misplay
pilot/veteran
severity/obvious
 labels 2026-07-10 20:02:27 +00:00
bstein commented 2026-07-10 21:09:54 +00:00
Author
Owner
Copy Link

Verified fixed and deployed in Cassandra 0.6.22.

Proof:

  • Cassandra 0.6.22 is live: /api/v1/app-config reports backend/frontend/sim_worker 0.6.22; /api/v1/ready is ok with config/database/storage/queue ready; backend and both frontend pods are Running with 0 restarts.
  • Regression coverage: PYTHONPATH=src python3 -m unittest tests/test_playtest_decisions.py tests/test_misplay_audit.py tests/test_atomic_decision_eval.py -q ran 405 tests OK; strategy-program suite ran 116 tests OK; feedback replay audit reports the exact six expected findings and atomic evaluator flags decision 15.
  • Runtime safety now declines optional life-payment/card-digging choices that would leave the pilot inside the opponent's visible next-combat damage range unless the action immediately wins or stabilizes that pressure. The audit also catches repeated optional life-payment dig loops on the feedback replay at lines 84, 88, 89, 90, and 91.

Closing this misplay issue.

Verified fixed and deployed in Cassandra 0.6.22. Proof: - Cassandra 0.6.22 is live: /api/v1/app-config reports backend/frontend/sim_worker 0.6.22; /api/v1/ready is ok with config/database/storage/queue ready; backend and both frontend pods are Running with 0 restarts. - Regression coverage: PYTHONPATH=src python3 -m unittest tests/test_playtest_decisions.py tests/test_misplay_audit.py tests/test_atomic_decision_eval.py -q ran 405 tests OK; strategy-program suite ran 116 tests OK; feedback replay audit reports the exact six expected findings and atomic evaluator flags decision 15. - Runtime safety now declines optional life-payment/card-digging choices that would leave the pilot inside the opponent's visible next-combat damage range unless the action immediately wins or stabilizes that pressure. The audit also catches repeated optional life-payment dig loops on the feedback replay at lines 84, 88, 89, 90, and 91. Closing this misplay issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
battery-0.5.21
Cassandra edge-case evaluation finding
bridge
Cassandra edge-case evaluation finding
commander-timing-stack
Cassandra edge-case evaluation finding
draw-go-vs-storm
Cassandra edge-case evaluation finding
dredge-vs-lantern
Cassandra edge-case evaluation finding
format/commander
Commander-specific issue.
format/duel-commander
Duel Commander-specific issue.
kind/bridge
Forge bridge/runtime ownership gap.
kind/metadata
Card metadata, image, or content import issue.
kind/misplay
Pilot quality issue or bad strategic/tactical choice.
kind/ops
Deployment, auth, capacity, or operational issue.
kind/ui
Replay, Lab, Runs, or visual review issue.
manual-review
Cassandra edge-case evaluation finding
misplay
Cassandra edge-case evaluation finding
pilot/adept
Observed at adept pilot skill.
pilot/proficient
Observed at proficient pilot skill.
pilot/veteran
Observed at veteran pilot skill.
rules
Cassandra edge-case evaluation finding
severity/debatable
Misplay should be absent at adept and above.
severity/defensible
Borderline line; veteran+ should avoid if identifiable.
severity/obvious
Misplay should not happen at proficient.
No Label
kind/misplay
misplay
pilot/veteran
severity/obvious
Milestone
No items
No Milestone
Assignees
Clear assignees
bstein veles-dev
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cassandra-alpha/feedback#34
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?