feat(queen): the leaderboard reads all time, not the last thirty days

[gHashTag]

The tab said LAST 30 DAYS because that is what the server answered. It is the wrong frame for a record of who carried the swarm: a lender whose lanes worked hard last month and rested this one read as having done nothing, and the board shrank on its own as time passed rather than growing with the work.

The server now answers the whole record by default (gHashTag/BrowserOS#512), so days arrives as null and the tab says All time / За всё время.

A narrowed read still says which window it is showing, because a number on a board that does not say what it covers is a number nobody can check.

Checks

• qa/queen-language-contract.mjs — 375 EN / 375 RU.
• npm run typecheck:ratchet — no file gained errors.

{
  "version": 1,
  "head_sha": "0397279bc676dd57f1461deac940ea5c63af3cce",
  "summary": "The leaderboard showed only the last thirty days, so a lender who worked earlier read as having done nothing and the board shrank as time passed; it now reads the whole record and says so.",
  "changes": [
    "Read the leaderboard over the whole record instead of a thirty-day window",
    "Say All time on the tab, in both languages, and keep naming the window when one is asked for",
    "Accept null as the window, because a board that does not say what it covers cannot be checked"
  ],
  "tests": [
    {
      "command": "node --experimental-strip-types qa/queen-language-contract.mjs",
      "result": "Queen language contract PASS with 375 English keys and 375 Russian keys",
      "status": "passed",
      "evidence": "Both wordings for the window are written in both languages and the counts stay balanced."
    },
    {
      "command": "npm run typecheck:ratchet",
      "result": "179 errors against a baseline of 179 with no file gaining any",
      "status": "passed",
      "evidence": "The window type widened to number or null and nothing else had to change."
    }
  ],
  "limitations": [
    "How much further back the record actually reaches is decided by the archive table, so the answer grows only as far as the swarm kept its own history",
    "The wording is driven by the server's answer, so a server still on the windowed build will keep saying the window rather than all time"
  ],
  "tags": [
    "queen",
    "leaderboard"
  ],
  "blog": {
    "title": "A leaderboard that quietly forgot last month",
    "summary": "The record of who carried the swarm was cut to thirty days, which meant it shrank on its own as time passed and told a contributor their earlier work had stopped counting.",
    "outline": [
      "The board was built with a thirty-day window, which seemed like a reasonable default for a live view of activity.",
      "It is the wrong frame for a record of contribution: work does not stop having happened because a month went by.",
      "A lender whose lanes ran hard in one month and rested the next appeared on the board as having done nothing at all.",
      "Removing the window means no time predicate at all rather than a very large number of days, so nothing can be off by one.",
      "A narrowed read still names its window, because a number that does not say what it covers is a number nobody can check."
    ]
  }
}

🤖 Generated with Claude Code