Spaces:
Paused
Paused
Commit History
-
docs: record in the PRD what the evidence resolved
Unverified signatureTwo risks close on measurement rather than argument: WebSockets on HF Spaces (verified through the edge proxy, and the owner's own Space already does it) and free-tier CPU for concurrent matches (measured p99 4.6-9.1ms per tick against a 50ms budget). Three replace them, all platform-level, all confirmed. Q2 is answered — start on free CPU Basic. Q1 hardens from a preference into a blocker: a private Space returns 404 for the running app, so nobody can play until it is public. Adds an evidence-base index so each claim points at the dossier behind it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PzkfXsTz4hxPfuySb1GvySd19cbc4 -
docs: delivery plan, engine/command dossiers, and the ADRs they ground
Unverified signatureAdds TASKS.md — 65 tasks across 8 phases, each traced to a PRD requirement and an ADR, with exit criteria stated as tests. Two analysis dossiers land and change the plan materially: - The engine is far closer to N-player than a literal count suggests. Combat, movement, gather, supply and fog are already owner-generic, and victory is already last-side-standing with a passing three-owner test. Of 53 owner literals, 35 live in Odyssey layers a skirmish never loads. The larger surface is the ~80 literals in the client. - Five engine defects block multiplayer. The worst is a module-global entity-id counter that makes two concurrent matches in one process non-replayable, silently. Three further hardcoded owner literals would ship a rigged game: seat B would lose squad formations, lose worker auto-repair, and be the only seat that kites. New records: ADR-0006 (wrap the command surface rather than rewrite it), ADR-0008 (two seats first, N seats second — the two-seat path ne…ef7537c -
docs: PRD, ADR log and feasibility spikes for the multiplayer port
Unverified signatureEstablishes the planning substrate for porting Stellar Frontier: RTS to SpaceCities — a multiplayer RTS with an MCP interface for agent players. - docs/PRD.md: goals, non-goals, users, functional/non-functional requirements, risks and success criteria. - docs/adr/: the decision log, with the first five records accepted — the log itself, importing upstream with history, server authority over peer lockstep, routing single-player through the multiplayer path, and a zero-dependency WebSocket transport. - docs/analysis/00-feasibility-spikes.md: executable evidence for the two decisions that could have invalidated the plan. A ~90-line RFC 6455 server round-trips against real Chromium, and the headless sim costs p99 22ms/tick with 800 units in contact against a 50ms budget. The branch is based on upstream 50ceb88 with all 542 commits of history, so blame reaches through to the original authorship and `upstream/main..HEAD` stays a precise record of what this port changed. Co-A…1c18fd4