Lantern blind-mills Dredge and fuels the opponent's graveyard engine #14
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
Lantern repeatedly used Ghoulcaller's Bell/Codex Shredder to mill Dredge, often through compiled Deterministic Opponent Mill Execution, directly fueling the opponent's graveyard engine.
What should have happened
Lantern policy should distinguish ordinary library pressure from graveyard-engine matchups and avoid milling Dredge unless the card is known, the mill denies a specific draw, or the graveyard consequence is intentionally accepted. The evaluator should flag blind opponent mill that materially fuels dredge/recursion engines.
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 avoids blind Lantern mill into graveyard-engine opponents unless there is an explicit tactical justification. Closing.