Q-01: Pi 4 Runtime Shape & Configuration

Define the full Pi 4 runtime surface. This is the “T-00” from the task queue, expanded.

Scope: - Docker container shape — new container vs existing d3-tui vs host process. Base image. Port allocation. - LangGraph runtime — venv binding, startup sequence, health checks - Forgejo — configuration (currently unconfigured), repo hosting, bind mounts, SSH/git access - Bind mounts — what directories surface to the container (wiki files, game-surface repo, secrets, toolchains) - Agent handling — how the Pi runs agent harnesses (subprocess, HTTP, raw API). Where API keys live. - Cleanup/reset — archive current state of d3-tui-pi-teams-proto before reconfiguring. What to preserve. - Bootstrap start state — what’s running when the player connects. What ports, what processes, what health checks. - Resource budget — RAM ceiling, disk, CPU given existing Docker load (d3-tui, forgejo)

Depends on: Q-02 (which harnesses), Q-03 (LangGraph config)