arcade-plan-it

Use the inspect and plan stages. Read the pinned Engine exports and implementations, existing optional Kits, game brief and previous evidence. Map every responsibility to core-existing, kit-existing, arcade-candidate or game-specific, with real engine: or repo: paths. Core mappings name a real public package export. State controls, decisions, success/failure, recovery, game feel, acceptance tests and scope. Preserve the full intent on retries. No invented APIs or automatic shared extraction.