1## Purpose2Specify shared interfaces and helper expectations for built-in game runtimes.34## Requirements56### Requirement: Gamer Interface7Every active puzzle game MUST implement initialization, update, view, reset, title setting, solved-state, save serialization, debug info, and full help bindings.89#### Scenario: Run game session10- **WHEN** the app activates a game model11- **THEN** the model can initialize, render, accept Bubble Tea messages, save state, and report completion through the shared interface1213### Requirement: Spawner Interfaces14Runtime entries SHALL expose variant Elo spawners for current creation and MAY expose legacy mode, seeded, cancellable, or import behavior as needed by CLI, daily, weekly, and export flows.1516#### Scenario: Spawn variant by Elo17- **WHEN** a variant is selected with target Elo18- **THEN** the owning game creates a deterministic puzzle and returns difficulty confidence metadata when available1920### Requirement: Shared Helpers21Grid games SHALL use shared cursor, key, border, dynamic grid, and style helpers where applicable so movement, rendering, and save/import behavior remain consistent.2223#### Scenario: Move cursor24- **WHEN** a grid game handles movement keys25- **THEN** cursor bounds and wrapping behavior follow the shared helper semantics used by that game