check:queen-honesty is FAIL (3) on main: three pins point at code that moved, and no workflow runs it #1351

npm run check:queen-honesty on main (d047a86) prints Queen honesty contract: FAIL (3). The page is not wrong: the three pins point at code that moved.

1. The round decision line. The pin held ${decisionInfo} · ${verb} (decisionLine), the fallback line of the command rail's second round button. 9316e9e removed that button and moved its popover onto the resource tile. The popover still spells the decision out, as the verb on its own line followed by {decisionInfo} · {skippedCount}.
2. GitHub facts (H-C1). The pin required Queen.tsx to name "./queen/foundation.json". feat(queen): one spec corpus for every tab of /game #1206 moved every corpus read into src/lib/queenCorpus.ts, and rule B of qa/queen-spec-sync-contract.mjs (which runs in CI) refuses any other file that names it. The two contracts cannot both pass.
3. Yellow coverage. The same move took fetch("t27/manifest.json" out of Queen.tsx; the coverage now reads useCorpus("manifest").

Why nobody saw it: no workflow has run check:queen-honesty since it was written (#897, 2026-09-04). That is A48, the anomaly website-checks.yml opens with.

Done when:

• each pin is re-homed to the surface that survived, with a negative control per pin;
• the store's order is pointed to rule C of spec-sync rather than restated;
• website-checks.yml runs check:queen-honesty.

Also measured: 26 other check:* scripts in apps/website/package.json are run by no workflow. Some of them are red on main. They are out of scope here and will be listed in the PR.