[orbitingflea]

This pull request makes the board page's browser tab show T3's blue icon and the title T3 (<project>). Until the chat reports a project, the title is plain T3. With the chat's server stopped, Chrome showed a grey globe icon. The tab used to show the board's own icon, even with the chat's server stopped. Its title was Board (<project>) or Board.

The fork's owner asked for this icon and title. The page holds T3's chat beside the board, but the old tab named the board and not T3. For the title, the request named only the form with a project. The owner later approved the plain T3 title and the grey globe.

The tab takes its icon from the chat's server. T3's own tab uses the same file.

I compared the old and new tabs in a desktop browser, using real board pages with a real chat beside them. In a phone-size window, the title and the icon file are the same as on desktop.

Details

• Title. fork/whiteboard/web/bridge.ts takes the project label from the last segment of the reported path.
• Icon. The /chat proxy in fork/whiteboard/vite.config.ts forwards the icon request to the chat's server. The served bytes equal apps/web/public/favicon.ico, the file that apps/web/index.html links as /favicon.ico.
• Check. .agents/skills/verify-whiteboard/scripts/wb-verify.sh up --chat ran the page and the sync server, plus a T3 server with a whiteboard build of apps/web. For the "before" column, a second Vite server ran a copy of the board from main. That copy connected to the same sync and chat servers.

Case	Before	After
Chat has a project	Board (project), board icon	T3 (project), blue T3 icon
Chat has no project	Board, board icon file	T3, T3 icon file
Chat's server stopped	Board, board icon	T3, globe icon, proxy answers 500 for the icon

• Phone size. A phone-size render draws no tab strip, so that check reads the title and fetches the icon file. Desktop Chrome at its smallest window shows both in its tab strip. The icon in a real phone's tab list was not seen.
• Page. With a project open, the before and after screenshots match pixel for pixel at both sizes. With no project, the phone-size screenshots show T3's setup dialog with the same text, a few pixels off. The cause of that offset was not traced. The no-project desktop screenshots differ by 254 pixels. I did not open those two screenshots.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Codex	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Codex	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	21.5 KiB	21.5 KiB	0 B (0.0%)	24.4 KiB	✅
Codex	Live turn messages	1	1	0 (0.0%)	8	✅
Claude	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Claude	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Claude	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Claude	Live turn WebSocket decoded	21.9 KiB	21.9 KiB	0 B (0.0%)	24.4 KiB	✅
Claude	Live turn messages	1	1	0 (0.0%)	8	✅

Baseline: 88df9b9 · PR result: 8df7a87 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.