add-frontend-component

Using a transport-agnostic adapter for WaitingFor states, frontend overlays integrate with the engine by enforcing frontmatter metadata, component patterns, and routing alignment to ensure TypeScript types match Rust serde output.

Gate UI overlays by active player using WaitingFor data routing, ensuring the correct player sees choices in multiplayer by enforcing routing and gating alignment through a standardized adapter pattern.

TypeScript frontend types mismatch Rust serde output when WaitingFor routing alignment is not enforced, which this approach resolves by applying frontmatter metadata and component patterns that guarantee type safety.

Yes, a transport-agnostic adapter applies to React overlay components like CardChoiceModal, ScryChoice, and ModeChoiceModal, covering routing, animation integration, and gating by the active player.

The best way to separate display logic from game logic is enforcing CR-correctness through standardized pipelines that dispatch engine actions, guiding creation of reusable overlays without mixing logic layers.

Yes, adding frontend UI components requires specific frontmatter metadata to enforce component patterns and WaitingFor routing alignment, ensuring consistent and safe UI behavior across the React and TypeScript frontend.