v0.9.91 MCP Clients as Providers with Session Replay and Google Sheets

[LakshmanTurlapati]

Summary

This draft delivers the v0.9.91 MCP Clients as Providers milestone. FSB can discover installed Claude Code, OpenCode, and Codex clients, show them as keyless providers, and delegate side-panel tasks through the existing MCP bridge.

It also includes the refinements previously tracked in #105: MCP session replay, explicit terminal task outcomes, signed-in Google Sheets capabilities, stronger terminal-summary and spreadsheet redaction, and aligned Extension 0.9.91 and fsb-mcp-server 0.11.0 release metadata.

The latest replay follow-up makes the feature behave like an actual replay: one logical recording spans all tabs used by a task, and replay opens and maps fresh target tabs automatically after one exact-manifest approval. The user is no longer asked to open each recorded page manually or approve high-impact steps one by one.

Major changes

1. Persist MCP client identity from installer intent, local inventory, and live initialize handshakes. Present one canonical Providers view without changing existing BYOK provider behavior.

2. Add an authenticated reverse request channel, an adapter contract, supervised process lifecycle management, and provider implementations for Claude Code, OpenCode, and Codex.

3. Add durable delegation consent, streamed tool activity, task cancellation, tab ownership recovery, daemon diagnostics, and native-host wake support across Chrome service-worker restarts.

4. Add adapter compatibility data and drift checks. Keep task mode only and preserve existing MCP wire contracts.

5. Record MCP sessions in local history with replayable steps and confirmed completion, partial, or failure outcomes. Sanitize signed URLs and recognized standalone credential shapes before terminal summaries enter history or Task Memory.

6. Add bounded signed-in Google Sheets read and write capabilities with session isolation, multiple-tab safety, redaction, and fail-closed recovery.

7. Remove completed Phase 26 through Phase 56 workspaces while retaining milestone archives and repository history. Point catalog completeness and write-activation evidence at canonical archived or stable repository references, and preserve required test ordering.

8. Refresh generated crawler metadata for the v0.9.91 release.

Session recording and replay behavior

• Group one live logical MCP task per agent across every tab it touches. Physical tabs are persisted as ordered logical tracks (primary, tab-2, and so on), with task-run and tab-count metadata retained in history.
• Treat is_final only as visual-overlay state. Recording closes on complete_task, partial_task, or fail_task; the 60-second idle timeout remains a fail-safe when no terminal outcome arrives.
• Build signed replay manifests with a start URL and origin for each logical tab. A missing or redacted URL blocks only that tab's steps instead of poisoning the entire timeline, and a secondary tab's URL is never borrowed for the primary tab.
• Open fresh owned browser tabs automatically and map each logical track to its replay tab. open_tab, switch_tab, and close_tab consume that mapping without duplicate tabs; service-worker recovery validates and reclaims every surviving track.
• Use one side-panel approval for the exact verified manifest, including its write and high-impact scopes. Pending MCP approvals survive side-panel closure, duplicate requests coalesce, approvals expire after ten minutes, and failed starts remain retryable.
• Add get_session_replay for a verified, structurally redacted, receipt-free preview and replay_session for the consent-gated replay request. get_session_detail now exposes only a shallow replay summary instead of deeply nested raw receipt data.
• Preserve the Google Sheets privacy boundary: Sheets targets remain boolean-only and never contribute document URLs to session records, while ordinary HTTP(S) pages retain sanitized bootstrap URLs needed for automatic replay.
• Update the registered MCP surface and user-facing references from 66 to 68 tools.
• Remove a zero-byte, carriage-return-suffixed Finder icon artifact that Windows cannot check out, allowing the Windows native-host CI job to reach its build and packaging steps.
• Discover the installed MSVC developer environment with vswhere instead of hardcoding a Visual Studio 2022 path, keeping native-host CI compatible with current Windows runner images.
• Keep CI installs bound to the committed MCP lockfile with npm ci, and stop the Windows registry helper from appending a NUL byte after its JSON response.
• Synchronize the 68-tool count across the source catalog and all five translated showcase catalogs, including exact Angular extraction metadata.

Security and compatibility

1. Existing MCP message values and tool schemas remain additive and byte-stable.

2. Replay approval is bound to the exact signed manifest hash. Only trusted extension UI senders can approve, cancel, or start it, and replay always uses fresh owned tabs rather than an arbitrary active tab.

3. Agent processes use validated argument arrays, scrubbed environments, bounded process-tree termination, explicit consent, loopback host checks, extension-origin checks, and rotating shared secrets.

4. Unsafe permission-bypass flags remain forbidden by CI.

5. Extension 0.9.91 requires Chrome 116 or newer. MCP server 0.11.0 must be upgraded with the extension for terminal task-outcome and replay-tool support.

Validation

• npm test
• npm run build
• npm --prefix mcp run build
• Focused recorder, replay, recovery, routing, tool-surface, version-parity, logger-retention, and Sheets-redaction tests
• Native-host workflow/packaging and Windows bootstrap source contracts
• Translation drift, adversarial translation-tool, translation-quality, and exact extract-i18n checks
• git diff --check

Review notes

This PR intentionally includes the changes from #105. PR 105 was already closed before this draft was created; this draft does not modify it.

Existing fragmented history rows are not rewritten retroactively. The logical cross-tab grouping applies to newly recorded MCP tasks.

This remains a draft because final live milestone UAT, including Codex adapter and real-browser replay scenarios, is still pending.