Spaces:
Paused
Paused
Commit History
-
docs: final dossier passes correct three tasks and add a real defect
Unverified signatureBoth remaining agents finished their refinement passes, and the corrections are worth more than the additions. T-019a was wrong: closing the two trust-boundary holes needs one new command, not two. issueSetHomeBase already accepts null, so the HUD was bypassing a command that would have done the job. The genuine gap is `electrified`, which has two direct writers and zero commands, guarded today only by a client-side owner check that disappears with the client. T-030 gains a trap worth knowing before anyone runs a rename: data.js defines a commodity whose id is literally "ai", so the owner-literal sweep must be site-by-site. The count also firms up — 119 sites, of which 110 collapse to one seam and 9 are the harder "the enemy is ai" assertion. T-013 gains the one thing that genuinely resists the loopback transport: input.js:521 passes synchronously, so a sync-only path would pass every test and fail over a real socket. New T-019b for a defect found in passing — boot.js fires your un…a75dff0 -
docs: client dossier returns with measurements, and a gap in NFR-3
Unverified signatureThe client-coupling analysis now quantifies the replication choice instead of arguing it. Full state at 800v800 on a 4x map serializes to 404KB in 4.45ms — at 20Hz across 4 seats that is 32MB/s and 18ms of a 50ms tick budget spent in JSON.stringify alone. The fog-filtered equivalent is 55KB in 0.69ms. Filtering is what makes replication affordable, not what makes it expensive, which settles ADR-0009 from the cost side as well as the anti-cheat side. That same number exposes a gap in my own NFR-3: 55KB per snapshot still exceeds the 32KB/s target at the pathological end. Rather than quietly claiming the requirement is met, T-015 now owns settling it — by snapshot rate and delta-encoding, or by restating the target on evidence. Also adds T-019a for the finding with the sharpest edge: exactly two client lines write simulation fields directly, bypassing engine/ entirely. They have no command envelope, so they would have been the first two ways around the codec. Co-Authored-By: Claude Op…a4e3249 -
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