feat(queen): one spec corpus for every tab of /game

[gHashTag]

The owner's report: the specs were not in sync across the tabs of https://app.t27.ai/game. This makes every Queen tab read one spec corpus from one store. A contract now holds them equal on every tab of the built page.

Measured on t27.ai first.

• Every tab happened to print 1577, because one scan wrote every file.
• The shell and the Spec Explorer frame each fetched the 1.8 MB manifest.
• The comb and the hero block each fetched the universe atlas.
• The SPECS rung read a sixth file, ladder.specs.
• A tab switch dropped spec=, the comb's spec stayed local, and the Explorer ignored the world chosen in the shell.

Nothing stated that two tabs were showing one corpus.

Before → after, on the built page (check:queen-spec-sync --browser):

	before	after
tabs reporting a corpus version	0	14 of 14: gHashTag/t27@2e4093d33/1577 (shell root, 6 SPECS rungs, the Explorer frame and its list)
manifest fetches, shell + Explorer frame	2	1
atlas holders inside the Queen	2 (comb, hero)	1 store
world= in the shell → Explorer	ignored	narrowed to the comb's count (tri-net: 113)
spec= across a tab switch	dropped	kept

{
  "version": 1,
  "head_sha": "9af298948b7121e5f48a21d62e67586a62bf4123",
  "summary": "Every Queen tab now reads one spec corpus from one store, src/lib/queenCorpus.ts. It is fetched once for the shell and its Explorer frame, and each tab says which corpus it shows. A new contract checks the files, the source, the store, the address and all 14 tabs of the built page. Each of those checks is also fed a broken fixture that must fail.",
  "changes": [
    "Added src/lib/queenCorpus.ts, one store for the manifest, atlas, modules and foundation. Each part is fetched once per window tree, because the Explorer frame adopts the shell's registry. The wire is tried first and the vendored file is the fallback. Each part reports its source and generatedAt, and the manifest's identity is its commit plus the SHA-256 of its bytes.",
    "Added src/lib/queenCorpusCheck.ts, a pure definition of one corpus. The manifest, the universe atlas, the shared core and the five spec-* ladders must agree on the count, on the manifest bytes they were built from, and world by world.",
    "Rewired the shell, the Specs directive, the hero block, the comb, the universe view, the compiler driver and the Spec Explorer onto the store. The SPECS rung now prints the store's count.",
    "The address now carries the selection: a tab switch keeps spec= and world=, and the comb writes the spec it opens. world= in the shell narrows the Explorer frame, which shows a world chip.",
    "The shell root and the Explorer root carry data-spec-count, data-corpus-version and data-corpus-source.",
    "Added qa/queen-spec-sync-contract.mjs as check:queen-spec-sync, with negative fixtures, and wired both its pure and --browser modes into Website checks.",
    "t27-world-scan.yml now dispatches pr-blog-report.yml for the refresh PR it opens, because a GITHUB_TOKEN event starts no workflow and #1176 sat BLOCKED. The discovery audit allows that one dispatch and nothing else."
  ],
  "tests": [
    {
      "command": "npm run check:queen-spec-sync -- --browser --no-build",
      "status": "passed",
      "result": "27 checks pass. All 14 tabs report gHashTag/t27@2e4093d33/1577 across 22 readings, the manifest is read once between the shell and the frame, and world=ghashtag/tri-net lists 113. The negative fixtures (stale ladder, foreign atlas, comb world mismatch, rogue fetch, a tab reading 1576, a whole run on a stale public/ that exits 1) are all reported.",
      "evidence": "apps/website/qa/queen-spec-sync-contract.mjs; local BrowserOS headless run"
    },
    {
      "command": "node qa/queen-embed-address-contract.mjs --no-build",
      "status": "passed",
      "result": "25 checks pass: deep links, picks, reload, Back, language and cross-Explorer links still keep the address and the frame on one card.",
      "evidence": "apps/website/qa/queen-embed-address-contract.mjs"
    },
    {
      "command": "every pure npm run step of .github/workflows/website-checks.yml (34 steps)",
      "status": "passed",
      "result": "All exit 0, including typecheck:ratchet (no file worsened), check:discovery, check:spec-catalog, check:queen-atlas, check:shared-core, check:queen-spec-mirrors, check:queen-catalog and check:subpath-urls.",
      "evidence": "local run, each exit code read directly rather than through a pipe"
    },
    {
      "command": "npx vite build",
      "status": "passed",
      "result": "Production build completed with the existing large-chunk warning.",
      "evidence": "local npx vite build in the task worktree, exit code read directly; dist/ served to the browser contracts above"
    }
  ],
  "limitations": [
    "The vendored corpus is still the 1577-spec snapshot at t27 2e4093d33. The 1737-spec refresh is bot PR #1176 and lands separately once its work report is dispatched.",
    "The comb's spec selection flows one way, from the comb to the address to the Explorer. The comb does not open a spec from the address on arrival, so the default spec= of the Specs tab does not pop a card open.",
    "QUEEN_API has no public-manifest or public-atlas route, so those two parts come from the vendored file, and modules and foundation fall back to it while the wire returns 404.",
    "The outer /game shell is another repository and iframes this Queen, so the store spans the Queen and its Explorer frame, not the outer shell."
  ],
  "tags": [
    "Engineering",
    "Verification",
    "Queen"
  ],
  "blog": {
    "title": "Fourteen tabs, one corpus",
    "summary": "The Queen's tabs printed the same spec count only because one scan wrote every file. They now read one store, say which corpus they show, and a contract proves it on every tab.",
    "outline": [
      "What the owner saw: tabs that could disagree. What was measured: five holders of the corpus, two copies of the manifest, and a selection lost on every tab switch.",
      "One store per window tree: the Explorer frame adopts the shell's registry, and every part carries its source, time and manifest hash.",
      "A contract that has been seen to fail: stale ladders, foreign atlases, rogue fetches and a whole stale public/ tree must each be reported, before 14 real tabs are read in Chrome."
    ]
  }
}

🤖 Generated with Claude Code