feat(queen): the ALL board -- CRM, mail, code and the agent's browser by whose move it is

[gHashTag]

What

A third board on /game/kanban -- ALL -- beside TASKS and CLIENTS. It shows every open thing the signed-in person is part of: their CRM matters, mail threads, GitHub work and their own AI-browser session, grouped by whose move it is (OUR MOVE / DUE / THEIR MOVE / NOBODY'S).

• Spec of record: t27 specs/automation/ball-board.t27 (feat(automation): ball-board v2 -- refuse shared-domain links, title links, card specs t27#5375). Host: render ball_board (gHashTag/999-multibots-telegraf, branch feat/ball-board-v2).
• Every card names its .t27 spec and opens it in the specs view; unspecced cards are labelled and counted, never given one.
• The browser card plus a head chip "open the AI browser" go to the app's own /game/browser, so the person can watch the agent and step in at any time.

Privacy and safety

New gate check:ball-board (66 checks, wired into website-checks.yml) feeds the reader a hostile answer:

Property	Held by
No credential in the module; one tool, no arguments	BALL_BOARD_TOOL: PlayerTool, loadBallBoard
Links only https to github.com / t27.ai, or exactly /game/browser	safeLink -- dropped, never rewritten
A browser card carries no stream URL, view token or endpoint	readCard keeps 8 named fields only
Spec paths cannot climb out of specs/	specPath
Nothing fetched directly, stored in the browser, or logged	source scan
Private lane never default, drawn only behind the clients guard	hive-board / clients-filter contracts, now component-aware

Known limit, stated not hidden

The render's GAME_TOKEN_TOOLS refuses hive_board/ball_board to a bare game token, so on t27.ai both private lanes answer "refused" and draw nothing. They work on app.t27.ai, where the token is the app session's. Fail-closed and intended; the PLAYER_TOOLS doc comment now says so.

Checks run locally

• check:hive-board 65, check:clients-filter 56, check:ball-board 66, check:queen-direction 92 -- all PASS.
• tsc -b: no errors in changed files (179 pre-existing errors elsewhere, unchanged).
• queen-viewport skipped locally (no Chrome on this machine); CI runs it.

Do not merge before the render side (ball_board v3) is deployed, or the lane answers "refused".

🤖 Generated with Claude Code

[gHashTag]

Reviewer bee Y: not merged. (1) CONFLICTING with main. (2) Required status 'T27 work report' = FAILURE. (3) It edits .github/workflows/website-checks.yml, so it needs the owner's workflow scope anyway. (4) It is a second, diverging implementation of the same ball board as #1202: both rewrite apps/website/src/lib/ballBoard.ts, qa/ball-board-contract.mjs, Queen.tsx/Queen.css, triIdentity.ts (diff between the two heads: 10 files, +726/-541), and neither contains the other. Only one can land; the owner/author should pick one and close the other before anyone reviews further.

[gHashTag]

bee review: left open -- CONFLICTING with main (head 0781b36). Conflicts in Queen.tsx, Queen.css, queen-viewport-contract.mjs and website-checks.yml, all moved on main (#1236, #1239, #1221). No credentials. Note the overlap with #1202 (mail lane, same ball-board idea): the author should decide which one survives before rebasing.

[gHashTag]

Bee review: #1199, not merged (head 0781b36d9c16538b65c8f8d33b30a7c4d0e5a638)

This PR was already CONFLICTING/DIRTY against main. #1202 has now merged (92e1d48d) with the narrower mail lane: it adds the same apps/website/src/lib/ballBoard.ts and qa/ball-board-contract.mjs, the same check:ball-board script and workflow step, and edits the same Queen.tsx, Queen.css, triIdentity.ts, hive-board and clients-filter contracts. Every one of those is now an add/add or content conflict.

If the ALL board (CRM, code and browser cards, spec links) is still wanted, it needs a rebase on top of #1202's ballBoard.ts, extending it rather than replacing it. Its own description also says not to merge before render ball_board v3 is deployed, and that has not been confirmed here. If the ALL board is not wanted, close this PR as superseded by #1202.