Bident of Thassa force-attack activation is used on controller's own upkeep #18

New Issue

bstein · 2026-07-06T17:51:12Z

bstein commented

2026-07-06 17:51:12 +00:00

What happened

Bident of Thassa's force-attack activated ability was used on player_2's own upkeep. Opponents' creatures normally cannot attack during player_2's turn, so this spent mana and tapped Bident for effectively no force-attack payoff.

What should have happened

Bident's activated ability should be used only before the chosen player's combat when those creatures can actually attack and the forced attack creates pressure, removal exposure, or defense. The pilot/evaluator should reject own-upkeep activations that cannot force opponents' creatures to attack that turn.

Context

correction target: ["pilot_policy", "card_notes", "atomic_evaluator"]
evidence: [{"artifact path": "artifacts/deployed_batteries/edge_case_0521_live_20260706T134944Z/logs/dashboard/edge-case-smoke-deployed-proof-commander-20260706t102658z-edge-commander-pod-timing-stack-g02-level-2/commander_pod_g1_2026070502/game.replay_events.ndjson", "frames": "251-252", "phase": "UPKEEP", "priority player": "player_2", "summary": "Bident of Thassa's force-attack activated ability was used on player_2's own upkeep. Opponents' creatures normally cannot attack during player_2's turn, so this spent mana and tapped Bident for effectively no force-attack payoff.", "turn": 17}]
feedback issue key: explicit:bident_force_attack_own_upkeep_no_payoff
recommended source files: ["src/veles/playtest_decisions.py", "src/veles/codex_decision_worker/legal_action_context.py", "src/veles/atomic_decision_eval.py", "../veles-content/strategies/commander/edge_commander_alela_draw_go/1/guide.md"]
root cause: bident_force_attack_own_upkeep_no_payoff
source findings file: reports/edge_case_atomic_eval/0.5.21_live/commander_timing_stack_g02_unique_findings_20260706.json

## What happened Bident of Thassa's force-attack activated ability was used on player_2's own upkeep. Opponents' creatures normally cannot attack during player_2's turn, so this spent mana and tapped Bident for effectively no force-attack payoff. ## What should have happened Bident's activated ability should be used only before the chosen player's combat when those creatures can actually attack and the forced attack creates pressure, removal exposure, or defense. The pilot/evaluator should reject own-upkeep activations that cannot force opponents' creatures to attack that turn. ## Category - kind: misplay - severity: moderate ## Context - correction target: ["pilot_policy", "card_notes", "atomic_evaluator"] - evidence: [{"artifact path": "artifacts/deployed_batteries/edge_case_0521_live_20260706T134944Z/logs/dashboard/edge-case-smoke-deployed-proof-commander-20260706t102658z-edge-commander-pod-timing-stack-g02-level-2/commander_pod_g1_2026070502/game.replay_events.ndjson", "frames": "251-252", "phase": "UPKEEP", "priority player": "player_2", "summary": "Bident of Thassa's force-attack activated ability was used on player_2's own upkeep. Opponents' creatures normally cannot attack during player_2's turn, so this spent mana and tapped Bident for effectively no force-attack payoff.", "turn": 17}] - feedback issue key: explicit:bident_force_attack_own_upkeep_no_payoff - recommended source files: ["src/veles/playtest_decisions.py", "src/veles/codex_decision_worker/legal_action_context.py", "src/veles/atomic_decision_eval.py", "../veles-content/strategies/commander/edge_commander_alela_draw_go/1/guide.md"] - root cause: bident_force_attack_own_upkeep_no_payoff - source findings file: reports/edge_case_atomic_eval/0.5.21_live/commander_timing_stack_g02_unique_findings_20260706.json

bstein added the

misplay

battery-0.5.21

manual-review

commander-timing-stack

labels 2026-07-06 17:51:12 +00:00

bstein commented

2026-07-09 06:33:12 +00:00

Verified in Cassandra 0.5.30.

Release proof: source bebd4c7 (Prepare Cassandra 0.5.30 feedback backlog closeout), Jenkins Veles #209 SUCCESS published version-only backend/frontend/sim-worker 0.5.30 images, Titan-IAC 1bf84977 deployed them, live /api/v1/app-config reports backend/frontend/sim_worker 0.5.30, /api/v1/ready is green, backend pod and both frontend pods are Running with 0 restarts, and VELES_SIM_IMAGE is registry.bstein.dev/veles/veles-sim-worker:0.5.30.

Local/source gate on the deployed source: bridge/runtime 42 tests OK; evaluator/audit/policy/API suite 504 tests OK; frontend maybeboard/compact-replay/prompt Playwright 22 tests passed; frontend build and git diff --check passed.

Issue-specific proof: policy/audit coverage now rejects Bident of Thassa force-attack activation on the controller own upkeep unless the forced player and timing are useful/legal. Closing.

Verified in Cassandra 0.5.30. Release proof: source bebd4c7 (Prepare Cassandra 0.5.30 feedback backlog closeout), Jenkins Veles #209 SUCCESS published version-only backend/frontend/sim-worker 0.5.30 images, Titan-IAC 1bf84977 deployed them, live /api/v1/app-config reports backend/frontend/sim_worker 0.5.30, /api/v1/ready is green, backend pod and both frontend pods are Running with 0 restarts, and VELES_SIM_IMAGE is registry.bstein.dev/veles/veles-sim-worker:0.5.30. Local/source gate on the deployed source: bridge/runtime 42 tests OK; evaluator/audit/policy/API suite 504 tests OK; frontend maybeboard/compact-replay/prompt Playwright 22 tests passed; frontend build and git diff --check passed. Issue-specific proof: policy/audit coverage now rejects Bident of Thassa force-attack activation on the controller own upkeep unless the forced player and timing are useful/legal. Closing.

bstein closed this issue

2026-07-09 06:33:12 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cassandra-alpha/feedback#18