Spaces:
Paused
Paused
Commit History
-
Fix ailab.test.js hang misdiagnosis; correct stale task numberingβ
Claude +1: Claude Sonnet 5Unverified signatureThe "hang" reported for test/ailab.test.js during T-012/T-013 validation was a diagnostic error in this session, not a real bug: node --test runs each file as a child process, and every check looked at the parent orchestrator's near-idle CPU instead of the child actually doing the work. Direct measurement of the child process confirms the full 95-test file completes in ~5 minutes (several evolutionary-archive tests individually take 20+ seconds β a genuinely heavy AI bench, never a hang). TASKS.md's T-012/T-013 rows corrected to the true full-suite count (2,555 then 2,565) instead of excluding this file. One real, harmless, pre-existing bug found along the way and fixed: test 9 in that file calls applyOverrides() to inject a strategy into the live shared STRATEGIES table and never restores it β the exact leak pattern the very next test's own comment already documents happening once before. Wrapped in the same snapshotTables/restoreTables the neighboring test uses. Nothing else in the β¦a2ff995 -
T-008a: /data confirmed ephemeral without a Storage Bucket, measuredβ
Unverified signatureTwo real production deploys landed back to back (0d2ee80 at 02:55:40 UTC, 9bf0f04 at 02:57:38 UTC β the exact two-boot gap T-008a needed), and /__data-probe answered the actual question rather than the documentation's hedge: the second boot found previousMarker: null. Nothing from the first boot's marker survived a ~2-minute-later restart. /data is ephemeral here today, measured, not inferred. This has a real consequence beyond the checkbox: ADR-0012's whole snapshot/restore mechanism assumes the opposite. A match snapshot written to /data right now would vanish on the very restart it exists to survive β silently, which is the worst way for that to fail. The ADR already named this as unverified follow-on work rather than an assumed premise, so nothing there was wrong; the follow-up just came back with an answer that requires action. The fix is well-understood and confirmed free (buckets are not PRO-gated), but this session can't perform it β no hf CLI, no write-scoped HF token, and iβ¦bae18b7
-
T-007a: a free account can rebuild the Space β the paywall risk is closedβ
Unverified signatureRan the probe. A non-PRO account pushed to the existing Docker Space and it rebuilt: 22:01:52 RUNNING_BUILDING 22:02:12 RUNNING_APP_STARTING 22:02:33 RUNNING (41s end to end) The Space's HEAD advanced to the pushed commit 894b2c6, and the app answered an anonymous request with 200 immediately afterwards. PRO is not a prerequisite, which closes the risk that gated everything downstream of ADR-0010, and with it U7 and U11. Q1 is closed too: the owner made the Space public, verified unauthenticated β private: False, and both the repo API and the running app return 200 to an anonymous caller. The probe also found something nobody was looking for. The stage sequence was RUNNING_BUILDING, not BUILDING: HF keeps serving the old build while the new image builds, so a deploy is a rolling swap rather than a hard outage. Real unavailability was the app-start window alone, about 21 seconds. This does not change ADR-0012 β a new container still destroys in-memory state, so sβ¦eb10230 -
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: HF dossier gains real edge measurements and a build gotchaβ
Unverified signatureThe platform research now carries numbers rather than inference: 400/400 frames round-tripped through the live HF edge with 0% loss, p50 RTT 32.6ms, max 48.8ms. A 20Hz server push is comfortable. Also pins a concrete trap into T-006. The HF Python recipe's `RUN useradd -m -u 1000 user` fails on node:* images, which already ship a UID-1000 `node` user β copying it blindly breaks the first Docker build. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PzkfXsTz4hxPfuySb1GvyS107d022 -
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