First-class “dev/unpacked” install recipe for box Chrome that survives restarts

[Trace824]

Summary

Local development needs a durable way to run the repo extension/ as unpacked so patches (CDP resolve, draft fast-path) survive Chrome restarts without fighting web-store content verification.

Repro

• Context: Developer Chrome profile used for FSB MCP testing.
• Steps:
  1. Load unpacked from /workspace/FSB/extension (or clone path).
  2. Restart Chrome / profile.
  3. Confirm extension still loaded (location: 4 unpacked) and bridge reconnects to ws://localhost:7225.
• Observed: ad-hoc flags/--load-extension work inconsistently across Chrome versions unless Developer mode and policy flags are documented.

Code pointers (verified against /workspace/FSB)

• extension/README.md — Load unpacked steps.
• Root README.md — extension package overview; bridge 7225/7226.
• mcp/README.md — hub/relay and HTTP MCP endpoint.

Proposed fix

Publish a short ops/dev recipe: Developer mode, Load unpacked path, optional --load-extension=…, verify SW + bridge health on :7226/health, and note when full Chrome restart is required vs chrome.runtime.reload().

Acceptance / regression

• Recipe reproduces unpacked install across restart on a clean profile.
• Linked from extension/README.md.

Owner

ops (recipe) + docs (land in README)

---

Priority: P2 · Owner: ops

[LakshmanTurlapati]

Fixed in #143: the READMEs now cover loading an unpacked build, recording its extension ID, running pair --reset after an ID change, and Chrome 137 dropping --load-extension.