Pithing Needle names cards with no activated abilities without a clear blank-name plan #16
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
Pithing Needle named Silversmote Ghoul in g01 and own Ensnaring Bridge as a blank in g03; neither has an activated ability to shut off, and the reasoning does not clearly separate intentional blank naming from real hate.
What should have happened
Pithing Needle naming should prefer real activated-ability targets. Intentional blank naming for artifact count, hand size, or lock texture should be explicit in the reason and separately classified from hate-card targeting.
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: policy/audit coverage now requires Pithing Needle names to map to meaningful activated-ability targets or to carry an explicit blank-name plan. Closing.