brw v0.5.0 — tab isolation by default + profile-daemon discovery

brw v0.5.0 — tab isolation by default + profile-daemon discovery

Multi-profile, agent-friendly browser control: brw now stays out of your way on a shared Chrome, and a gateway can discover every profile-daemon you run.

✨ Tab isolation is now the default (extension bridge)

A no-tab_id action now targets the tab brw owns, never the tab you're looking at. The first page action opens a fresh tab in brw's own group, in the background, instead of hijacking your current tab. Your existing tabs are touched only when you pass an explicit tab_id.

• Stops automation (and parallel agent runs) from stomping your open tabs.
• Restore the previous "follow my focused tab" behavior with --bridge-follow-focus (or BRW_BRIDGE_FOLLOW_FOCUS=1).

🔎 brwctl daemons

New command that enumerates the extension-bridge profiles in your browser-profiles.json, probes each daemon's /health, and emits JSON (name, profile, workspace, http_addr, ws_addr, extension_id, reachable, identity). This is the discovery contract a gateway (e.g. MCPlexer) consumes to register one namespace per browser — the foundation for running several Chrome/Chromium profiles and letting an agent pick which one.

Notes

• Behavior change: the bridge default flipped from follow-focus to isolation. Interactive single-operator users who want brw to act on whatever tab they've selected should pass --bridge-follow-focus.
• The background-open part needs the updated extension (reload in chrome://extensions after upgrading); the no-stomp/own-tab resolution works daemon-side regardless.

Full changelog: v0.4.1...v0.5.0