[BrandDead]

ATTACK and OPS PLAN previously selected a fabricated rival/vehicle roster and entered the legacy shooter without carrying the selected block or crew. Both entries now plan a supported on-foot response on an owned block and open MAP’s existing UnifiedEncounter with its confirmed crew and terrain.

The existing combat-intent store carries only the block ID. Queue, consume and encounter entry recheck live ownership and roster; empty, all-downed, missing, changed and illegal placements stay in planning. The result handler guards all shared consequences and service submission against the existing block receipt, including two callbacks in one render. No new engine, game-state store, result writer, assets or dependencies.

Refs #192 (partial slice; keep open), #194 characterization. Reservations: issue comments 6086081491 and 6086309780. Base 9eef5aa; exact published tree matches the verified local tree 02231867fa1ffc9e8a7c5d3106d603f801bfceee.

Validation:

• Regression first: 12 new planner/intent/MAP failures and 2 BlockMode failures on the unchanged base, passing after the fix; 17 focused tests plus the existing 4 tutorial tests passed.
• preflight.sh passed: 93 files / 1,047 tests passed / 4 existing skips; TypeScript passed; lint 0 errors / 200 baseline warnings, no new warnings.
• Asset audit 112 assets / 7.70 MB of 20 MB / 0 errors or warnings; package validation 5 packages / 4 schemas; production build passed with the existing large-chunk warning.
• Offline backend: 107 passed, 0 warnings.
• Built-game 390×844 and 1440×900: age gate → ATTACK → confirmed Lil Dre/Kilo → launch → fire/reload → retreat → one local receipt → return → reload. Receipt, heat and morale persisted; no happy-path page/console errors. Simulated encounter chunk failure retained the board and retry. Screenshots and restricted-network/font details: docs/evidence/2026-10-09-attack-response/.

Known limits: this is local demo proof, not #175 authenticated server proof. The existing remote commit remains fire-and-forget with a warning on failure. The server receipt authorizes owned blocks only, so NPC invasions and vehicle driver dismounts remain open under #192. #169 member identity/resolver, #201 DRIVE, #175 staging, migrations/RLS/secrets/production are untouched. Legacy shooter code remains on disk but these routes no longer enter it. Independent #190 presentation work follows; no runtime dependency on it. No merge or deployment.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
slide	Ready	Preview	Oct 9, 2026 6:23pm UTC