debug-web2d-gamelisted

# Debug a Web 2D Game Reduce the report to the first incorrect state transition, fix its owning layer, and preserve the reproduction as a regression scenario. Keep visual symptoms separate from rule evidence. ## Workflow 1. Translate the report into expected initial state, minimal actions, expected result, and observed result. 2. Call `web2d_project_inspect`, start the game, then call `web2d_session_start` with a recorded seed. 3. Call `web2d_observe` before acting. Verify that the bridge exposes every state field needed to distinguish the hypotheses. 4. Reproduce with the shortest `web2d_scenario_run` possible. If reproduction depends on uncontrolled waiting, first add deterministic stepping or a domain action. 5. Classify the first failure using [references/failure-layers.md](references/failure-layers.md). Keep input, state/rules, lifecycle, rendering, assets, and performance as separate boundaries. 6. Change the smallest owner of the incorrect transition. Do not rewrite the rendering stack to repair a rule defect. 7. Re-run the exact seed and scenario, then adjacent scenarios and existing tests. When state is correct but presentation was wrong, use the host browser/capture capability to verify the repaired rendered state. 8. Keep the scenario in project test fixtures when it protects a real bug contract. 9. Run `web2d_quality_check`, stop the session, and report root cause, changed boundary, before/after evidence, and remaining uncertainty. ## Debugging rules - If str