ui__revamping-game-shell-ui

To revamp a game UI shell without breaking deterministic replay, enforce a no-framework policy using vanilla DOM and UI kit primitives. This preserves strict kernel-shell boundaries while incrementally migrating HUD, menus, and overlays.

The best way to migrate game overlays safely is a stepwise workflow starting with a read-only audit of UI surfaces. Draft a migration plan, then implement small, testable UI kit based steps inside the game shell to ensure incremental verification.

Adding a UI framework breaks game replay determinism by introducing unmanaged runtime side effects outside the kernel. Strict kernel-vs-shell boundaries require vanilla DOM and approved UI kit entrypoints to prevent nondeterministic state mutations during replay.

No, standard UI frameworks are not allowed inside the iframe-based game shell. The system enforces a strict no-framework UI policy, requiring only vanilla DOM and UI kit entrypoints to maintain iframe-safe layouts and deterministic execution.

To audit game UI surfaces before a shell redesign, scan AGENTS.md to map existing HUD, menus, results, and overlays. This read-only audit identifies current implementations and informs a safe, incremental migration plan to UI kit primitives.

Vanilla DOM limitations for complex game UI overlays are mitigated by adopting UI kit primitives. While avoiding frameworks prevents nondeterminism, the UI kit provides the necessary structured components to build polished, iframe-safe layouts without runtime side effects.