feat(queen): spec authors - the swarm's work goes to the person whose key it ran on

[dmitrii-f-t27]

Why

• A bee's work reaches t27 master as the squash of a queen-<issue> pull request. GitHub authors that squash as whoever merged it: Vasilev Dmitrii <admin@t27.ai>, i.e. gHashTag.
• So all 564 merged Queen PRs counted as gHashTag's own commits on WHO WROTE THE SPECS.
• The owner, 2026-10-03: credit that work to the person whose provider key the bee ran on.

What

• scripts/spec-authors.mjs reads the Queen's record /queen/public-credits (feat(queen): /queen/public-credits - whose lane carried each accepted issue BrowserOS#527, 👑 QUEEN TRINITY — The 27-Agent Sovereign (Meta-Repo Orchestrator) #528). The record maps each issue to the GitHub login of the lane its latest turn ran on, counted only from the day that login lent the lane (TRIOS_KEY_OWNERS_SINCE).
• It maps every merged queen-<issue> PR in t27 to its squash sha, and credits that commit to the lane owner as via: lane. This takes priority over the author rule.
• If the record cannot be read, nothing is re-attributed, and the JSON says so in laneCredits.
• QueenPeople shows N by the swarm on their keys next to through their merged pull requests.
• public/roadmap/spec-authors.json will be regenerated in this PR once 👑 QUEEN TRINITY — The 27-Agent Sovereign (Meta-Repo Orchestrator) #528 is live.

{
  "version": 1,
  "head_sha": "efa641e8441928f29381b8c4efd0463a73a6f4cf",
  "summary": "WHO WROTE THE SPECS credits the swarm's work to the person whose provider key the bee ran on: a squash of a merged queen-<issue> pull request in t27 now goes to the lane owner from the Queen's /queen/public-credits record instead of to whoever merged it.",
  "changes": [
    "apps/website/scripts/spec-authors.mjs: reads /queen/public-credits (issue -> GitHub login of the lane of its latest turn, only from the day the login lent the lane), maps every merged queen-<issue> pull request in gHashTag/t27 to its squash sha, and credits that commit to the lane owner with via 'lane' before the author rule; without the record nothing is re-attributed and the JSON records laneCredits.read=false.",
    "apps/website/src/lib/queenPeople.ts and src/components/QueenPeople.tsx: CreditedVia gains 'lane' and each row shows how many commits came 'by the swarm on their keys' (EN) / RU equivalent.",
    "apps/website/public/roadmap/spec-authors.json: regenerated; gHashTag 3235 -> 2953, dmitrii-f-t27 36 -> 358 (311 via lane), mxfill77 74, Karim13014 1, 49 unattributed."
  ],
  "tests": [
    {
      "command": "node qa/tri-board-contract.mjs",
      "result": "56 checks OK",
      "status": "passed",
      "evidence": "Local run 2026-10-03 in the feat/spec-authors-lane-credit worktree"
    },
    {
      "command": "GH_TOKEN=$(gh auth token) node scripts/spec-authors.mjs",
      "result": "53 spec paths in 13 repositories, 3435 commits, 4 accounts, 49 unattributed, 940 requests; laneCredits read=true, 1190 credited issues, 564 queen squashes",
      "status": "passed",
      "evidence": "Run 2026-10-03 against the live Queen after gHashTag/BrowserOS#528"
    },
    {
      "command": "npm run typecheck",
      "result": "not run locally (no node_modules on this machine); left to CI",
      "status": "not_run",
      "evidence": "Website checks on this pull request"
    }
  ],
  "limitations": [
    "The record only credits turns dispatched on or after 2026-09-17 for dmitrii-f-t27 (TRIOS_KEY_OWNERS_SINCE), the day the worker pool moved from the operator's plan onto his keys; 50 earlier queen squashes keep the old rule.",
    "203 of the 514 queen squashes since 2026-09-17 are not credited because the Queen's database holds no turn for their issue; they keep the old rule.",
    "The change of attribution was decided by the co-founder Dmitrii Fedorov on 2026-10-03; the co-founder Dmitrii Vasilev was asked by e-mail the same day and has not replied yet."
  ],
  "tags": [
    "queen",
    "leaderboard",
    "specauthors",
    "website"
  ],
  "blog": {
    "title": "The swarm's specs now count for the people who lend it keys",
    "summary": "Why the spec-authors board used to credit every bee commit to whoever merged it, and how the Queen's own record of lanes now routes that credit to the person whose provider key did the work.",
    "outline": [
      "A swarm commit reaches master as the squash of a queen-<issue> pull request, and GitHub authors that squash as the merger, so 564 bee pull requests read as one person's own commits.",
      "The Queen already records which lane ran each turn and who lent it; a new public record maps each issue to that login, counted only from the day the lane was lent.",
      "The board script maps squash shas to issues and credits the lane owner first, falling back to the old rule when the record is missing; the regenerated board moves 311 commits."
    ]
  }
}

🤖 Generated with Claude Code