feat(queen): /queen/public-credits - whose lane carried each accepted issue

[dmitrii-f-t27]

Why

• The spec-authors board in gHashTag/trinity credits a commit to its GitHub author.
• A swarm commit reaches t27 master as the squash of a queen-<issue> PR, authored by whoever merged it. So every bee's work counted as the merger's own: 514 merged Queen PRs since 2026-09-17.
• The owner (2026-10-03): credit that work to the person whose provider key the bee ran on.

What

• GET /queen/public-credits returns { measuredAt, repo, credits: [{ issue, github, at }] }.
  • Each entry is the GitHub login that claimed the lane of an issue's latest accepted turn, read from queen_dispatch and queen_dispatch_history.
  • An unclaimed lane, or an owner name that is not a login, is left out.
• TRIOS_KEY_OWNERS_SINCE (login=YYYY-MM-DD): a lane is a slot, not a key. Turns from before a login lent its lanes are not credited. Set to dmitrii-f-t27=2026-09-17, the day the pool moved off the operator's plan onto our keys.
• The endpoint is public-read like /queen/public-leaderboard: issue numbers and logins only. The route-guard pins are re-measured: 47→48 mounts, 9→10 public-read.

Tests

• tests/api/queen-lane-credits.test.ts (4) and route-guard pins.
• All queen-* API tests plus route tests pass locally.

🤖 Generated with Claude Code

[github-actions]

✅ Tests passed — 2500/2560

Suite	Passed	Failed	Skipped
✅ agent	87/87	0	0
✅ build	9/9	0	0
✅ cdp-protocol	5/5	0	0
✅ eval	93/93	0	0
✅ server-agent	280/280	0	0
✅ server-api	1349/1408	0	59
✅ server-browser	6/6	0	0
✅ server-integration	10/11	0	1
✅ server-lib	279/279	0	0
✅ server-pglive	25/25	0	0
✅ server-root	68/68	0	0
✅ server-skills	31/31	0	0
✅ server-tools	244/244	0	0
✅ shared	14/14	0	0

View workflow run