@btraut/browser-bridge 0.11.1 → 0.12.1

package/CHANGELOG.md

@@ -6,6 +6,39 @@ The format is based on "Keep a Changelog", and this project adheres to Semantic
 
 ## [Unreleased]
 
+_TBD_
+
+## [0.12.1] - 2026-02-17
+
+### Changed
+
+- Extension popup now shows a compact `Connected` indicator (green/red) instead of the verbose connection diagnostics panel.
+
+### Fixed
+
+- Extension background now preflights Core `/health` before dialing websocket, avoiding noisy `ERR_CONNECTION_REFUSED` extension errors while Core is offline.
+
+## [0.12.0] - 2026-02-17
+
+### Changed
+
+- Core runtime bootstrap: CLI and MCP adapter now share one Core readiness/runtime resolution path (default/env/metadata precedence + health/ensure-ready behavior), with new shared parity tests.
+- MCP adapter now enables Core ensure-ready by default when constructing its client, so first tool calls auto-bootstrap Core after cold start.
+- Diagnostics doctor payload/report now carries runtime endpoint/source/process context for caller, Core, and extension components so endpoint/version mismatches are explicit.
+- Extension hello events now include the endpoint settings they are dialing (`core_host`, `core_port`, `core_port_source`) for mismatch diagnostics.
+- Extension Drive socket now tracks explicit connection states (`connecting`, `connected`, `disconnected`, `backoff`) with a status surface (`drive.connection_status`) for UI diagnostics.
+- Popup UI now includes a live connection health panel (state, endpoint/source, last success/failure, next retry) and a `Copy diagnostics` action for bug reports.
+- README/manual docs now include post-reboot startup semantics and an end-to-end endpoint mismatch troubleshooting flow.
+- MCP startup is now lazy; no startup filesystem writes unless initialized by first tool call.
+
+### Fixed
+
+- MCP adapter now returns bounded retryable `UNAVAILABLE` envelopes when Core ensure-ready cannot establish health, instead of opaque internal failures.
+- Extension reconnect failures now use throttled warning logs to avoid disconnect spam while preserving exponential backoff behavior.
+- Shared Core readiness now resets failed ensure-ready attempts for next-caller retry, adds bounded health probe timeouts/budget, and covers retry/dedupe behavior with regression tests.
+- Diagnostics now ignores disconnected extension runtime identity for endpoint/version mismatch checks, and extension bridge disconnect clears cached runtime identity fields to prevent stale mismatch reporting.
+- Popup diagnostics now clears cached status on refresh failure (blocking stale copy payloads), resets retry metadata outside backoff state, and announces async connection/copy feedback via live regions.
+
 ## [0.11.1] - 2026-02-16
 
 ### Fixed

package/README.md

@@ -267,6 +267,8 @@ For normal usage, Browser Bridge is zero-setup:
 - Core and CLI default to `127.0.0.1:3210`.
 - The extension also defaults to `3210`.
 - You do not need `dev activate` unless you intentionally opt into isolated worktree routing.
+- After reboot/cold start, the first CLI or MCP request auto-starts Core (no manual daemon wake-up required).
+- If Core is idle/offline, the extension popup may show `disconnected` or `backoff`; this is expected until Core is reachable again.
 
 Optional status check:
 
@@ -315,6 +317,43 @@ tail -n 80 .context/logs/browser-bridge/mcp-adapter.jsonl
 
 - CLI: `browser-bridge diagnostics doctor --session-id <id>`
 - Reports extension and debugger status alongside session state.
+- Includes runtime context for caller, Core, and extension endpoints so mismatch causes are visible in one run.
+- Popup shows a simple `Connected` indicator (`green` when connected, `red` otherwise).
+
+### End-to-End Connection Troubleshooting Flow
+
+Use this exact flow when commands fail after reboot, runtime changes, or worktree switching:
+
+1. Check runtime resolution:
+
+```bash
+browser-bridge dev info --json
+```
+
+2. Run diagnostics from CLI (captures caller + Core + extension runtime context):
+
+```bash
+browser-bridge diagnostics doctor --json
+```
+
+3. Open the extension popup and check `Connected`:
+   - Green dot: extension is currently connected to Core.
+   - Red dot: extension is disconnected or reconnecting.
+
+4. If caller/core/extension endpoints differ in the diagnostics report:
+   - Default mode: remove custom host/port env overrides and retry (`BROWSER_BRIDGE_CORE_HOST`, `BROWSER_BRIDGE_CORE_PORT`).
+   - Isolated mode: re-run `browser-bridge dev activate --extension-id <id>` for the intended worktree.
+
+5. If the popup stays red and failures continue:
+   - Inspect logs:
+
+```bash
+tail -n 80 .context/logs/browser-bridge/cli.jsonl
+tail -n 80 .context/logs/browser-bridge/core.jsonl
+tail -n 80 .context/logs/browser-bridge/mcp-adapter.jsonl
+```
+
+6. Retry the command once endpoint mismatch is corrected.
 
 ## 🔧 Recovery