patchwork-os 0.2.0-alpha.33 → 0.2.0-alpha.35

package/README.md

@@ -1,92 +1,292 @@
-# Patchwork OS
+# Claude IDE Bridge & Patchwork OS
 
-**AI that works while you're away. Runs on your machine. Doesn't lock you in.**
+**One npm package. Two products.** Pick the layer you need.
+
+| | What you get | Install | Best for |
+|---|---|---|---|
+| **🔌 Claude IDE Bridge** | MCP bridge connecting Claude Code to your IDE. 170+ tools — diagnostics, LSP, debugger, terminal, git, GitHub, file ops. | `npm i -g patchwork-os` then run `claude-ide-bridge` | Anyone who wants Claude Code to see and act on their editor state |
+| **🤖 Patchwork OS** | Everything in the bridge **plus** YAML recipes, approval queue, oversight dashboard, mobile push approvals, multi-model providers, JetBrains companion. | Same package, run `patchwork patchwork-init` | Power users running automation, agent workflows, or background tasks |
+
+Same codebase. Bridge is the foundation; Patchwork OS is the optional layer on top. **No vendor lock-in. Runs on your machine.**
+
+---
+
+## 🔌 Claude IDE Bridge — Quick Start
+
+```bash
+# 1. Install the npm package
+npm install -g patchwork-os
+
+# 2. Install the VS Code / Cursor / Windsurf extension
+#    Search "Claude IDE Bridge" on OpenVSX, or:
+claude-ide-bridge install-extension
+
+# 3. Start the bridge for your workspace
+claude-ide-bridge --workspace .
+
+# 4. Connect Claude Code (in another terminal)
+CLAUDE_CODE_IDE_SKIP_VALID_CHECK=true claude --ide
+```
+
+Type `/ide` in Claude Code to confirm the connection. That's it — Claude now sees your diagnostics, open files, and editor state, and can call 170+ tools to act on them.
+
+**What the bridge gives Claude:**
+
+- Diagnostics, LSP navigation (goto / references / call hierarchy), refactoring with risk analysis
+- Terminal — run commands, read output, wait for async work
+- Git — status, diff, commit, push, blame, checkout, branch list
+- GitHub — open PRs, list issues, post reviews, fetch run logs
+- Debugger — set breakpoints, evaluate expressions, inspect runtime state
+- Files — read, edit by line range, search and replace, capture screenshots
+- Code quality — `auditDependencies`, `detectUnusedCode`, `getCodeCoverage`, `getGitHotspots`
+
+The bridge runs without any flags. No recipes, no automation, no dashboard — just the IDE-Claude connection.
+
+**Compatible IDEs:** VS Code, Cursor, Windsurf, Google Antigravity. JetBrains IDEs via [companion plugin](#jetbrains-plugin).
+
+**Transport layers:**
+
+| Client | Protocol |
+|---|---|
+| Claude Code CLI | WebSocket `ws://127.0.0.1:<port>` |
+| Claude Desktop | stdio shim → WebSocket |
+| Remote (claude.ai, Codex CLI) | Streamable HTTP + Bearer token |
+
+**Tool modes:**
+
+| Mode | Tools | When to use |
+|---|---|---|
+| Full _(default)_ | ~170 | All git, GitHub, terminal, file ops, orchestration |
+| Slim (`--slim`) | ~60 | LSP + debugger + editor state only |
+
+Bridge-only docs: [documents/platform-docs.md](documents/platform-docs.md)
+
+---
+
+## 🤖 Patchwork OS — Quick Start
 
 ```bash
 npx patchwork-os@alpha patchwork-init
 ```
 
-That one command sets up 5 local recipes, detects Ollama, and drops a terminal dashboard at your fingertips — under 90 seconds on a warm npm cache.
+Sets up 5 local recipes, detects Ollama, and opens a terminal dashboard — under 90 seconds.
+
+### What it adds on top of the bridge
 
-## What it does
+Patchwork OS is a local automation platform that watches your workspace for events, runs AI-powered recipes in response, and routes anything risky through an approval queue before it goes anywhere.
 
-Patchwork OS watches for things that matter, acts, and asks before anything risky goes out.
+Think of it as a background agent that acts on your behalf — but asks before sending, writing, or modifying anything consequential.
 
-- **A developer's overnight.** Tests fail on a push → a one-paragraph triage note lands in your inbox. You wake up knowing where to look.
-- **A small business's inbox.** New customer questions triaged, follow-ups drafted in your voice. Nothing sends without your nod.
-- **A parent's morning.** Field-trip form flagged, reply drafted to the teacher — done before the first coffee.
+- Test suite fails on CI → triage note in your inbox before you wake up
+- Customer email arrives → draft reply in your voice, pending your approval
+- Field-trip permission form flagged → reply drafted to the teacher, waiting for your nod
 
-## How it works
+**Recipes** are plain YAML files. They declare a trigger (cron, file save, git commit, test run, webhook) and an action (run a prompt, write to inbox, call a connector). No code required. Share them like dotfiles.
 
-- **Recipes** — plain YAML files describe what to watch and what to do. Share them like dotfiles. No code required.
-- **Your models, your keys** — Claude, GPT, Gemini, Grok, or local Ollama. Swap anytime. Nothing phones home.
-- **Oversight first** — everything risky lands in `~/.patchwork/inbox/` for your approval before it goes anywhere.
+**Models** are yours. Claude, GPT, Gemini, Grok, or local Ollama. Swap at any time. Nothing phones home.
 
-## After init
+**Oversight** is non-negotiable. Every write or external action lands in `~/.patchwork/inbox/` for approval. The web UI at `http://localhost:3100` shows pending approvals, live sessions, recipe run history, and analytics.
+
+### Patchwork commands
 
 ```bash
-patchwork-os recipe list                    # see installed recipes
-patchwork-os recipe run daily-status      # run one now
-patchwork-os recipe run morning-brief --local  # run with local LLM
-patchwork-os tools list                   # browse all 140+ tools
-patchwork-os                              # open terminal dashboard
+# One-command setup: extension + CLAUDE.md + starter recipes
+patchwork patchwork-init
+
+# Explore
+patchwork recipe list                      # installed recipes
+patchwork recipe run daily-status         # run one now
+patchwork recipe run morning-brief --local # run with local Ollama
+patchwork tools list                      # browse 170+ tools
+patchwork                                 # open terminal dashboard
+
+# Web UI — bridge + extension watcher in tmux
+patchwork start-all                       # then http://localhost:3100
 ```
 
-The oversight web UI runs at `http://localhost:3100` when the bridge is active. The dashboard shows live sessions, pending approvals, recent recipe runs, and analytics.
+### Starter recipes
 
-## Starter recipes (no external API keys needed)
+No external API keys needed for these:
 
 | Recipe | Trigger | What it does |
 |---|---|---|
-| `ambient-journal` | git commit | appends one line to `~/.patchwork/journal/` |
-| `daily-status` | cron 08:00 | morning brief from yesterday's commits |
-| `watch-failing-tests` | test run | drops triage note to inbox on failure |
-| `lint-on-save` | file save | surfaces new TS/JS diagnostics to inbox |
-| `stale-branches` | cron weekly | lists branches older than 30 days |
-| `morning-brief` | cron 08:00 | commits + Linear issues + Calendar events |
+| `ambient-journal` | git commit | Appends one line to `~/.patchwork/journal/` |
+| `daily-status` | cron 08:00 | Morning brief from yesterday's commits |
+| `watch-failing-tests` | test run | Drops triage note to inbox on failure |
+| `lint-on-save` | file save | Surfaces new TS/JS diagnostics to inbox |
+| `stale-branches` | cron weekly | Lists branches older than 30 days |
+| `morning-brief` | cron 08:00 | Commits + Linear issues + Calendar events |
 | `sentry-to-linear` | manual | Sentry issue → Linear ticket (one-shot) |
+| `google-meet-debrief` | manual | Meeting notes → Linear + Slack |
+
+Connectors (Linear, Sentry, Slack, Google Calendar, Intercom, HubSpot, Datadog, Stripe) require API keys and approval-gated writes.
+
+### Automation hooks
 
-Local recipes write to `~/.patchwork/inbox/` only. Connectors (Linear, Sentry, etc.) require API keys and approval-gated writes.
+Event-driven hooks trigger Claude tasks automatically. Activate with `--automation --automation-policy <path.json> --claude-driver subprocess`.
 
-## What's working today
+Key hooks:
+
+| Hook | Fires when |
+|---|---|
+| `onFileSave` | Matching files saved |
+| `onDiagnosticsStateChange` | Errors appear or clear |
+| `onRecipeSave` | Any `.yaml`/`.yml` saved — runs preflight |
+| `onGitCommit` / `onGitPush` / `onGitPull` | Git tools succeed |
+| `onTestRun` | Test run completes (filter: any/failure/pass-after-fail) |
+| `onBranchCheckout` | After branch switch |
+| `onPullRequest` | After `githubCreatePR` succeeds |
+| `onCompaction` | Before/after Claude context compaction |
+| `onTaskCreated` / `onTaskSuccess` | Orchestrator task lifecycle |
+
+All hooks support inline prompts, named prompt references, and a minimum 5s cooldown. Full reference: [documents/platform-docs.md → Automation Hooks](documents/platform-docs.md)
+
+---
+
+## Architecture
+
+```
+patchwork-os (npm package)
+│
+├── claude-ide-bridge          ← run alone for bridge-only mode
+│   ├── MCP server             170+ tools over WebSocket / HTTP / stdio
+│   ├── VS Code extension      LSP, debugger, editor state, live diagnostics
+│   ├── Git / GitHub           gitCommit, gitPush, githubCreatePR, …
+│   ├── Terminal               runInTerminal, getTerminalOutput, …
+│   └── Code quality           auditDependencies, detectUnusedCode, getCodeCoverage
+│
+└── patchwork                  ← run for full Patchwork OS layer
+    ├── Recipe runner          YAML triggers → LLM prompt → action
+    ├── Connectors             Linear, Sentry, Slack, Google Calendar, +
+    ├── Orchestrator           Claude subprocess tasks, automation hooks
+    ├── Oversight inbox        ~/.patchwork/inbox/ — approval queue
+    └── Web dashboard          http://localhost:3100 — approvals, sessions, analytics
+```
+
+The npm package ships **three CLI binaries** that share the same code:
+
+| Binary | Default behavior |
+|---|---|
+| `claude-ide-bridge` | Bridge only — no automation, no recipe runner, no dashboard |
+| `patchwork` | Full Patchwork OS — automation + recipes + dashboard |
+| `patchwork-os` | Alias for `patchwork` |
+
+Use whichever fits your mental model.
+
+---
+
+## Tool surface (v0.2.0-alpha.35)
+
+170+ MCP tools across 15 categories. Highlights:
+
+| Category | Tools |
+|---|---|
+| LSP / Code Intelligence | `getDiagnostics`, `goToDefinition`, `findReferences`, `getCallHierarchy`, `renameSymbol`, `refactorAnalyze`, `explainSymbol`, … (37 tools) |
+| Git | `getGitStatus`, `getGitDiff`, `gitCommit`, `gitPush`, `gitCheckout`, `gitBlame`, … (16 tools) |
+| GitHub | `githubCreatePR`, `githubListPRs`, `githubCreateIssue`, `githubPostPRReview`, … (13 tools) |
+| Terminal | `runInTerminal`, `createTerminal`, `getTerminalOutput`, `waitForTerminalOutput` |
+| File Operations | `editText`, `searchAndReplace`, `searchWorkspace`, `findFiles`, `getFileTree`, … |
+| Debugger | `setDebugBreakpoints`, `startDebugging`, `evaluateInDebugger` |
+| Orchestrator | `runClaudeTask`, `listClaudeTasks`, `getClaudeTaskStatus` |
+| Context Platform | `ctxGetTaskContext`, `ctxQueryTraces`, `ctxSaveTrace`, `enrichStackTrace` |
+
+Full reference: [documents/platform-docs.md](documents/platform-docs.md)
+
+---
+
+## Plugin system
+
+Extend the tool surface without forking the bridge.
+
+```bash
+# Scaffold a new plugin
+patchwork gen-plugin-stub ./my-plugin --name "org/name" --prefix "myPrefix"
+
+# Load at runtime
+claude-ide-bridge --plugin ./my-plugin
+```
+
+Plugins register MCP tools in-process. Publish to npm with keyword `claude-ide-bridge-plugin`.
+
+Full reference: [documents/plugin-authoring.md](documents/plugin-authoring.md)
+
+---
+
+## JetBrains plugin
+
+Companion IntelliJ plugin (v1.0.0) on the JetBrains Marketplace. Covers 49 handlers: core tools, PSI-based LSP (goto, references, hover, rename, symbols, format), XDebugger integration, and code style tools.
+
+Use the same bridge from VS Code and JetBrains IDEs simultaneously — IntelliJ IDEA, PyCharm, GoLand, WebStorm, and other IntelliJ-platform editors.
+
+Source: [intellij-plugin/](intellij-plugin/)
+
+---
+
+## Remote deployment
+
+Run headless on a VPS with full tool support via VS Code Remote-SSH.
+
+```bash
+claude-ide-bridge --bind 0.0.0.0 \
+  --issuer-url https://your-domain.com \
+  --fixed-token <uuid> \
+  --vps
+```
+
+Systemd service and deploy scripts in [`deploy/`](deploy/). Full guide: [docs/remote-access.md](docs/remote-access.md).
+
+---
+
+## What's shipped
 
 | Feature | Status |
 |---|---|
+| 170+ MCP tools (LSP, git, tests, debugger, diagnostics) | **shipped** |
+| VS Code / Cursor / Windsurf / Antigravity extension | **shipped** |
+| JetBrains plugin (49 handlers) | **shipped** |
 | `patchwork-init` — one-command setup | **shipped** |
-| Terminal dashboard (`patchwork-os`) | **shipped** |
+| Terminal dashboard | **shipped** |
 | Web oversight UI (approvals, sessions, recipes) | **shipped** |
 | Recipe runner (YAML, cron, manual, webhook) | **shipped** |
 | Multi-provider LLM (Claude, Gemini, OpenAI, Grok, Ollama) | **shipped** |
-| Linear connector (read + approval-gated write) | **shipped** |
-| Sentry connector (fetch issues, stack traces) | **shipped** |
-| Google Calendar connector (read-only) | **shipped** |
-| Slack connector (post messages, list channels) | **shipped** |
-| 140+ MCP tools (LSP, git, tests, diagnostics) | **shipped** |
+| Connectors: Linear, Sentry, Slack, Google Calendar, Intercom, HubSpot, Datadog, Stripe | **shipped** |
 | Cross-session memory (traces, handoff notes) | **shipped** |
-| Gmail connector | W2 |
-| Mobile oversight PWA | W3 |
-| Community recipe marketplace | Q3 |
+| Mobile oversight PWA (push approvals) | **shipped (alpha)** |
+| Community recipe marketplace | Q3 2026 |
 
-## Install
+---
 
-**From the registry (recommended):**
-```bash
-npm install -g patchwork-os
-patchwork-os patchwork-init
-```
+## Install from source
 
-**From a local build (development / CI):**
 ```bash
 git clone https://github.com/Oolab-labs/patchwork-os
 cd patchwork-os
 npm install && npm run build
-# Use npm pack to create a real copy — do NOT use `npm install -g .`
-# That creates a symlink which breaks the macOS LaunchAgent (EPERM at startup).
+
+# Pack first — do NOT use `npm install -g .`
+# Symlink installs break the macOS LaunchAgent (EPERM at startup)
 npm pack
 npm install -g patchwork-os-*.tgz
-patchwork-os patchwork-init
+patchwork patchwork-init
 ```
 
+---
+
+## Documentation
+
+| Doc | Contents |
+|---|---|
+| [documents/platform-docs.md](documents/platform-docs.md) | Full tool reference (170+ tools), automation hooks, connectors |
+| [documents/prompts-reference.md](documents/prompts-reference.md) | All 72 MCP prompts |
+| [documents/styleguide.md](documents/styleguide.md) | Code conventions, UI patterns |
+| [documents/roadmap.md](documents/roadmap.md) | Development direction |
+| [documents/data-reference.md](documents/data-reference.md) | Data flows, state management, protocol details |
+| [documents/plugin-authoring.md](documents/plugin-authoring.md) | Plugin manifest schema, entrypoint API, distribution |
+| [docs/adr/](docs/adr/) | Architecture Decision Records |
+| [docs/remote-access.md](docs/remote-access.md) | VPS deployment guide |
+
+---
+
 ## License
 
-MIT © Oolab Labs. Built on the [Claude IDE Bridge](./README.bridge.md).
+MIT © Oolab Labs

package/deploy/bootstrap-new-vps.sh

@@ -1,10 +1,10 @@
 #!/usr/bin/env bash
 # deploy/bootstrap-new-vps.sh
-# Full fresh-server setup for claude-ide-bridge on a NEW VPS.
+# Full fresh-server setup for patchwork-os on a NEW VPS.
 # Handles everything from Node.js install to running HTTPS service.
 #
 # Usage (run as root on a fresh Ubuntu 22.04/24.04 VPS):
-#   curl -fsSL https://raw.githubusercontent.com/Oolab-labs/claude-ide-bridge/main/deploy/bootstrap-new-vps.sh | \
+#   curl -fsSL https://raw.githubusercontent.com/Oolab-labs/patchwork-os/main/deploy/bootstrap-new-vps.sh | \
 #     DOMAIN=bridge.example.com bash
 #
 #   Or after cloning:
@@ -14,9 +14,9 @@
 #   DOMAIN        Subdomain for the bridge  (e.g. bridge.example.com)
 #
 # Optional environment variables:
-#   REPO_URL      Git repo URL              (default: https://github.com/Oolab-labs/claude-ide-bridge)
-#   INSTALL_DIR   Where to clone the repo   (default: /opt/claude-ide-bridge)
-#   SERVICE_USER  System user to run bridge (default: claude-bridge)
+#   REPO_URL      Git repo URL              (default: https://github.com/Oolab-labs/patchwork-os)
+#   INSTALL_DIR   Where to clone the repo   (default: /opt/patchwork-os)
+#   SERVICE_USER  System user to run bridge (default: patchwork)
 #   PORT          Bridge port               (default: 9000)
 #   BRANCH        Git branch to clone       (default: main)
 #   SKIP_CERTBOT  Set to 1 to skip TLS cert (useful if DNS not yet set)
@@ -25,13 +25,13 @@ set -euo pipefail
 
 # ── Config ────────────────────────────────────────────────────────────────────
 DOMAIN="${DOMAIN:-}"
-REPO_URL="${REPO_URL:-https://github.com/Oolab-labs/claude-ide-bridge}"
-INSTALL_DIR="${INSTALL_DIR:-/opt/claude-ide-bridge}"
-SERVICE_USER="${SERVICE_USER:-claude-bridge}"
+REPO_URL="${REPO_URL:-https://github.com/Oolab-labs/patchwork-os}"
+INSTALL_DIR="${INSTALL_DIR:-/opt/patchwork-os}"
+SERVICE_USER="${SERVICE_USER:-patchwork}"
 PORT="${PORT:-9000}"
 BRANCH="${BRANCH:-main}"
 SKIP_CERTBOT="${SKIP_CERTBOT:-0}"
-SERVICE_NAME="claude-ide-bridge"
+SERVICE_NAME="patchwork-os"
 
 RED='\033[0;31m'; GREEN='\033[0;32m'; YELLOW='\033[1;33m'; NC='\033[0m'
 info()    { echo -e "${GREEN}✓${NC} $*"; }
@@ -163,8 +163,8 @@ section "Systemd service"
 # Generate service file from template (parameterised for this install)
 cat > "/etc/systemd/system/${SERVICE_NAME}.service" <<SERVICE
 [Unit]
-Description=Claude IDE Bridge MCP Server
-Documentation=https://github.com/Oolab-labs/claude-ide-bridge
+Description=Patchwork OS bridge
+Documentation=https://github.com/Oolab-labs/patchwork-os
 After=network.target
 StartLimitIntervalSec=120
 StartLimitBurst=5
@@ -193,7 +193,7 @@ RestartSec=5
 
 StandardOutput=journal
 StandardError=journal
-SyslogIdentifier=claude-ide-bridge
+SyslogIdentifier=patchwork-os
 
 NoNewPrivileges=true
 PrivateTmp=true

package/deploy/bootstrap-vps.sh

@@ -40,9 +40,12 @@ mkdir -p "${BRIDGE_HOME}"
 chown "${BRIDGE_USER}:${BRIDGE_USER}" "${BRIDGE_HOME}"
 
 # ── 4. Install bridge globally ────────────────────────────────────────────────
-info "Installing claude-ide-bridge from npm..."
-npm install -g claude-ide-bridge 2>&1 | tail -5
-BRIDGE_BIN="$(which claude-ide-bridge)"
+info "Installing patchwork-os from npm..."
+npm install -g patchwork-os@alpha 2>&1 | tail -5
+# `patchwork-os` ships three bin aliases: `patchwork` (preferred),
+# `patchwork-os`, and the legacy `claude-ide-bridge`. Use the canonical
+# `patchwork` name for the systemd unit + nginx config below.
+BRIDGE_BIN="$(which patchwork)"
 info "Bridge binary: ${BRIDGE_BIN}"
 
 # ── 5. Generate fixed token ───────────────────────────────────────────────────

package/deploy/deploy-landing.sh

@@ -9,9 +9,16 @@ NGINX_CONF="/etc/nginx/sites-available/patchworkos"
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
 
-echo "==> Copying landing page to VPS..."
+echo "==> Copying landing page + assets to VPS..."
 ssh "$VPS" "mkdir -p $LANDING_DIR"
-scp "$REPO_ROOT/landing/index.html" "$VPS:$LANDING_DIR/index.html"
+# index.html plus the favicon + manifest browsers probe at apex. Without
+# these the browser console fills with /favicon.svg and /manifest.json
+# 401s on every page load (nginx falls through to the dashboard middleware
+# for paths that don't have an explicit `location`).
+scp "$REPO_ROOT/landing/index.html"   "$VPS:$LANDING_DIR/index.html"
+scp "$REPO_ROOT/landing/favicon.ico"  "$VPS:$LANDING_DIR/favicon.ico"
+scp "$REPO_ROOT/landing/favicon.svg"  "$VPS:$LANDING_DIR/favicon.svg"
+scp "$REPO_ROOT/landing/manifest.json" "$VPS:$LANDING_DIR/manifest.json"
 
 echo "==> Updating nginx to serve landing page at root..."
 ssh "$VPS" bash <<'REMOTE'
@@ -70,6 +77,56 @@ else
   echo "nginx: landing location already present, skipping"
 fi
 
+# Independent idempotency block for the apex asset locations — these were
+# added after the original landing block, so existing installs miss them.
+if ! grep -q "location = /favicon.ico" "$NGINX_CONF"; then
+  python3 - "$NGINX_CONF" <<'PYEOF'
+import sys
+
+path = sys.argv[1]
+with open(path) as f:
+    content = f.read()
+
+asset_blocks = """
+    # Apex assets — favicon + PWA manifest browsers probe at root
+    location = /favicon.ico {
+        root /var/www/patchwork-landing;
+        try_files /favicon.ico =404;
+        access_log off;
+    }
+    location = /favicon.svg {
+        root /var/www/patchwork-landing;
+        try_files /favicon.svg =404;
+        access_log off;
+    }
+    location = /manifest.json {
+        root /var/www/patchwork-landing;
+        try_files /manifest.json =404;
+        access_log off;
+    }
+"""
+
+# Insert immediately after the existing `location = /` block
+marker = '    location = / {'
+idx = content.find(marker)
+if idx == -1:
+    print("WARN: could not find `location = /` to anchor; appending to end", flush=True)
+    idx = content.rfind('\n}')
+    new_content = content[:idx] + asset_blocks + content[idx:]
+else:
+    # find end of the location = / block
+    end = content.find('    }', idx)
+    end = content.find('\n', end) + 1 if end != -1 else idx
+    new_content = content[:end] + asset_blocks + content[end:]
+
+with open(path, 'w') as f:
+    f.write(new_content)
+print("nginx: apex asset location blocks inserted")
+PYEOF
+else
+  echo "nginx: apex asset locations already present, skipping"
+fi
+
 nginx -t && systemctl reload nginx
 echo "nginx reloaded"
 REMOTE

package/dist/bridge.js

@@ -16,6 +16,7 @@ import { CommitIssueLinkLog } from "./commitIssueLinkLog.js";
 import { DecisionTraceLog } from "./decisionTraceLog.js";
 import { createDriver } from "./drivers/index.js";
 import { ExtensionClient } from "./extensionClient.js";
+import { lockKillSwitchEnv } from "./featureFlags.js";
 import { FileLock } from "./fileLock.js";
 import { buildEnforcementReminder } from "./instructionsUtils.js";
 import { LockFileManager } from "./lockfile.js";
@@ -683,7 +684,11 @@ export class Bridge {
     async start() {
         // 0. Initialize OpenTelemetry (no-op when OTEL_EXPORTER_OTLP_ENDPOINT is unset)
         initTelemetry();
-        // 0a. Auto-repair .claude/rules/bridge-tools.md if stale (present but missing the
+        // 0a. Snapshot env-derived kill-switch flags. After this, plugins or
+        // recipe steps mutating `process.env.PATCHWORK_FLAG_*` cannot disable an
+        // active emergency stop. Closes MED-2 from the 2026-04-28 audit.
+        lockKillSwitchEnv();
+        // 0b. Auto-repair .claude/rules/bridge-tools.md if stale (present but missing the
         // current version sentinel). Older package versions write stale files that may
         // lack new tool substitution rules. Repair is silent on success; falls back to
         // warn-only if the template is missing or the write fails.
@@ -792,6 +797,7 @@ export class Bridge {
                     getOrchestrator: () => this.orchestrator,
                     recipeOrchestrator: this.recipeOrchestrator,
                     recipeRunLog: this.recipeRunLog,
+                    activityLog: this.activityLog,
                     workdir: this.config.workspace,
                     logger: this.logger,
                 });
@@ -1078,6 +1084,9 @@ export class Bridge {
                     automationEnabled: this.config.automationEnabled,
                     port: this.port,
                     webhookUrl: this.server.approvalWebhookUrl ?? null,
+                    pushServiceUrl: this.server.pushServiceUrl ?? null,
+                    pushServiceToken: this.server.pushServiceToken ? "***" : null,
+                    pushServiceBaseUrl: this.server.pushServiceBaseUrl ?? null,
                 },
             };
         };
@@ -1164,6 +1173,31 @@ export class Bridge {
             : null, async () => {
             await this.refreshRecentTracesDigest();
             return this.buildInstructions();
+        }, 
+        // Tail-end deps so `registerAllTools` registers the same tool set
+        // on Streamable-HTTP sessions as on WebSocket. Without this object,
+        // `ctxSaveTrace`, `ctxQueryTraces`, and any tool gated on the
+        // remaining deps silently failed to register over Streamable HTTP
+        // (caught dogfooding `ctx-loop-test` from a remote MCP client).
+        {
+            automationHooks: this.automationHooks,
+            getDisconnectInfo: () => ({
+                at: this.lastDisconnectAt,
+                code: this.lastDisconnectCode,
+                reason: this.lastDisconnectReason,
+            }),
+            onContextCacheUpdated: (generatedAt) => {
+                this._lastContextCachedAt = generatedAt;
+                this._emitLiveState();
+            },
+            getExtensionDisconnectCount: () => this.extensionDisconnectCount,
+            ...(this.commitIssueLinkLog && {
+                commitIssueLinkLog: this.commitIssueLinkLog,
+            }),
+            ...(this.recipeRunLog && { recipeRunLog: this.recipeRunLog }),
+            ...(this.decisionTraceLog && {
+                decisionTraceLog: this.decisionTraceLog,
+            }),
         });
         this.server.httpMcpHandler = (req, res) => this.httpMcpHandler?.handle(req, res) ?? Promise.resolve();
         // 3. Check for stale lock files