--chrome --resume sessions start without the Chrome bridge; workaround multiplies token cost

Resumed interactive sessions boot with zero claude-in-chrome tools even with the bridge enabled by env var.
Environment: VS Code terminal on Windows 11 / Claude Code 2.1.226 / extension 1.0.85.
/chrome then Reconnect opens claude.ai/new which closes and does nothing.
Fresh claude -p children at the same minute get the bridge fine, so extension and native host are healthy.

Impact: all live-browser work must run through -p child sessions.
Every child boots a full session, so simple browser tasks cost several times the tokens.
Each child is also isolated from the others' tabs, which fragments the work.
On a Max plan this burned ~75% of a weekly quota in 2 days of setup work.