Prismatic Ending is spent on Baral without removing the cost reducer #8
Loading…
x
Reference in New Issue
Block a user
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?
What happened
Across deployed Draw-Go vs Storm g02, g03, and g04, Draw-Go correctly identified Baral as a must-answer reducer but spent Prismatic Ending without removing it. g02 and g04 show underpayment or bad sequencing for a mana-value-2 target, while g03 shows Baral remaining even after a two-color payment.
What should have happened
The pilot and bridge should require enough distinct colors for Prismatic Ending to cover the target's mana value, sequence land/mana choices before the spell when needed, and audit the post-resolution state so a removal spell that resolved without moving its target is caught as a correction target.
Category
Context
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: test_bridge_runtime_feedback proves Prismatic Ending exposes an X=1 action for Baral, pays with two colors, resolves, and Baral leaves the battlefield. Jenkins #209 built and pushed the 0.5.30 sim image from the same bridge source. Closing.