feat(game): show recorded .t27 spec earnings, and stop promising there will never be a token

[gHashTag]

What

The leaderboard tab of /game gets a SPEC EARNINGS panel, QueenSpecEarnings.tsx. It reads GET /queen/public-earnings from the swarm (added in gHashTag/BrowserOS#516) and shows the following:

• Per lender: how many accepted .t27 commits were recorded as earned, and how many a later verdict on the same commit took back. The GitHub login is re-validated before it becomes a link.
• Above the counts: the server's own status sentence, recorded, not withdrawable: no token is deployed. It is translated only when it matches that text exactly; any other status is printed unchanged.
• Under the counts: the server's own list of what is not yet true. Examples are that no TRI amount per spec is decided and that accept does not require a merge.
• When the route is not deployed yet: the panel says the record is not published yet. It does not say the leaderboard broke.

Copy

AgiGameBlock (move 03), FaqBlock and the motto.ts comment now state only present-tense facts, with no "never a token" wording:

• Accepted turns and accepted .t27 specs are recorded; each spec earning has an id anyone can recompute.
• TRI is the token those earnings are designed to mint (100% mined, no pre-mine).
• It is not deployed yet, so nothing is withdrawable today.

What this does NOT do

• No token, no amount, no balance and no wallet.
• Nothing is withdrawable.
• The panel shows counts of recorded work and nothing else.

Checks

• typecheck:ratchet: 179 errors across 26 files, equal to the baseline. No file gained errors, and the changed files have none.
• eslint: QueenSpecEarnings.tsx is clean. The only hit in QueenLeaderboard.tsx is line 75 (LEADERBOARD_COPY export), which is already on main.
• Pre-commit: the explorer and Queen bilingual contracts pass, and english-only passes.

Dependency

Until gHashTag/BrowserOS#516 is merged and the swarm that serves this page is redeployed, the panel shows the "not published yet" line. After that, 999 needs a QUEEN_REF bump through the usual release(board) PR.

🤖 Generated with Claude Code

{
  "version": 1,
  "head_sha": "3197a570867761df872d3d048c25c44f9bf64ad5",
  "summary": "The leaderboard tab gains a SPEC EARNINGS panel that reads the swarm's public record of accepted .t27 commits, and the game copy stops promising there will never be a token, saying instead that TRI is not deployed yet.",
  "changes": [
    "New QueenSpecEarnings.tsx reads /queen/public-earnings with credentials omitted and lists, per person, accepted .t27 commits recorded as earned and those later taken back, re-validating any GitHub login before it becomes a link.",
    "The panel prints the server's status sentence (translated only when it matches the known not-withdrawable text exactly) and the server's list of what is not yet true; an unreachable route reads as not published rather than broken.",
    "AgiGameBlock move 03, FaqBlock and the motto.ts comment drop the never-a-token wording and state that TRI is designed to be minted from accepted work and is not deployed, so nothing is withdrawable today.",
    "Merge of origin/main: main had removed the lanes ranking from QueenLeaderboard.tsx and added QueenRunners; the resolution keeps main's file and inserts the SPEC EARNINGS panel between PEOPLE and the runners.",
    "Because main also pruned the row styles from QueenLeaderboard.css, the panel now carries its own scoped QueenSpecEarnings.css, registered in qa/queen-contrast-contract.mjs; motto.ts keeps the PR's comment and main's SITE_NAME export."
  ],
  "tests": [
    {
      "command": "Website checks / checks job on head 3197a570",
      "status": "failed",
      "result": "The job stopped at the Silicon coverage step, which also fails on main for the unclassified spec gf16_attn.t27; the typecheck ratchet and API contract steps passed before it, and later contract steps were skipped.",
      "evidence": "https://github.com/gHashTag/trinity/actions/runs/37224912474/job/111502474873"
    },
    {
      "command": "CI / Build & Test",
      "status": "passed",
      "result": "The repository Build and Test job completed successfully on this head.",
      "evidence": "https://github.com/gHashTag/trinity/actions/runs/37224912466/job/111502474796"
    },
    {
      "command": "Docs check / Check Documentation Links",
      "status": "failed",
      "result": "The documentation link check failed on this head; it is not a required check and was not investigated in this merge.",
      "evidence": "https://github.com/gHashTag/trinity/actions/runs/37224910679/job/111502469155"
    }
  ],
  "limitations": [
    "The contrast contract and the other website contract steps did not run in CI on this head because the job stops at the Silicon coverage failure inherited from main.",
    "The panel shows the not published line until the /queen/public-earnings route is deployed on the swarm that serves the page; no token, amount, balance or wallet is shown.",
    "The new QueenSpecEarnings.css restores styles main removed; it was not checked visually in a browser during this merge."
  ],
  "tags": [
    "Leaderboard",
    "SpecEarnings",
    "TRI"
  ],
  "blog": {
    "title": "Spec earnings on the leaderboard, and honest wording about the TRI token",
    "summary": "The leaderboard now shows a public record of accepted .t27 commits counted as earnings and those taken back, and the game copy says plainly that the TRI token is not deployed yet instead of promising there will never be one.",
    "outline": [
      "Each accepted .t27 commit is recorded once with an id anyone can recompute from repository, issue and commit, and a later send-back of the same commit is recorded beside it.",
      "The panel prints the server's own status sentence above the counts, so the numbers cannot be read as a balance, and lists what the server says is not yet true.",
      "The home page move three, the FAQ answer and the motto comment now describe TRI as designed to be minted from accepted work and not deployed, with nothing withdrawable today.",
      "Merging main meant placing the panel into a leaderboard that had dropped its lanes ranking, and giving the panel its own stylesheet because the shared row styles had been removed."
    ]
  }
}

[gHashTag]

Reviewer bee Y: not merged. (1) CONFLICTING with main. (2) Required status 'T27 work report' = FAILURE. Still relevant: origin/main FaqBlock.tsx still says there is no token and 'the block above says why there will not be one', while main now has a TOKEN tab (#1237). Overlaps #1200 on the same wording; land one source of truth for the token statement, with the owner's approval of the text.

[gHashTag]

bee review: left open -- CONFLICTING with main (head 7676706). Conflicts are in the Queen leaderboard / motto area, which #1237 (TOKEN tab, spec authors ranked) changed since. No credentials in the diff. Author should rebase and re-check whether #1237 already covers the earnings display.

[github-actions]

X Brain Health Check

Score: 100.0/100
Status: 🟢 HEALTHY
Threshold: 80/100

X Brain is above merge threshold

[github-actions]

🧪 Brain Stress Test Results

Tests: 261/261 passed, 0 leaked
Status: 🟢 PASS
Gate: every test in zig build test-brain-stress passes and none leaks