patchwork-os 0.2.0-beta.9.canary.86 → 0.2.0-beta.9.canary.89

package/README.bridge.md

@@ -21,11 +21,11 @@ https://github.com/user-attachments/assets/a81a8d11-2cc3-46f3-88ad-6a905a221a2c
 
 ## Quick Start
 
-**Prerequisites:** [Claude Code CLI](https://claude.ai/code), Node.js ≥ 20
+**Prerequisites:** [Claude Code CLI](https://claude.ai/code), Node.js ≥ 22
 
 ```bash
 # 1. Install the bridge
-npm install -g claude-ide-bridge
+npm install -g patchwork-os
 
 # 2. One-command setup (installs extension, writes CLAUDE.md, registers MCP server)
 cd /your/project
@@ -38,7 +38,7 @@ claude-ide-bridge --watch
 claude --ide
 ```
 
-> **Updating?** Use `npm install -g claude-ide-bridge@latest` — `npm update -g` may lag the registry cache after a new release.
+> **Updating?** Use `npm install -g patchwork-os@latest` — `npm update -g` may lag the registry cache after a new release.
 
 > **macOS LaunchAgent users:** always install from the registry (`npm install -g patchwork-os`) or
 > from a tarball (`npm pack && npm install -g patchwork-os-*.tgz`).
@@ -81,7 +81,7 @@ Or search **Claude IDE Bridge** in the VS Code / Cursor / Windsurf marketplace.
 
 ## Slim vs Full Mode
 
-The bridge starts in **full mode** by default (changed in v2.43.0) — all ~140 tools, covering LSP/debugger/refactoring plus git, GitHub, terminal, file tree, and orchestration.
+The bridge starts in **full mode** by default (changed in v2.43.0) — all 177 tools, covering LSP/debugger/refactoring plus git, GitHub, terminal, file tree, and orchestration.
 
 Pass `--slim` to restrict to the ~60 IDE-exclusive tools (LSP, debugger, editor state only) — useful when you want Claude to use its native Read/Write/Bash tools for everything else:
 
@@ -144,7 +144,7 @@ Claude calls `refactorAnalyze` (checks blast radius and risk), `refactorPreview`
 Standard setup. Extension connects automatically. Full LSP, debugger, and editor state available.
 
 ### Remote SSH
-VS Code Remote-SSH and Cursor SSH load the extension on the VPS side (`extensionKind: ["workspace"]`). Start the bridge on the remote machine. All ~140 tools work over SSH.
+VS Code Remote-SSH and Cursor SSH load the extension on the VPS side (`extensionKind: ["workspace"]`). Start the bridge on the remote machine. All 177 tools work over SSH.
 
 ```bash
 # On the remote machine
@@ -274,7 +274,7 @@ claude-ide-bridge install claude-mem
 |---|---|
 | `claude-ide-bridge init` | One-command setup: install extension + write CLAUDE.md + register MCP server |
 | `claude-ide-bridge --watch` | Start bridge with auto-restart on crash (2s → 30s backoff) |
-| `claude-ide-bridge --slim` | Restrict to ~60 IDE-exclusive tools (default: ~140 full tools) |
+| `claude-ide-bridge --slim` | Restrict to ~60 IDE-exclusive tools (default: 177 full tools) |
 | `claude-ide-bridge install-extension` | Install companion VS Code extension |
 | `claude-ide-bridge gen-claude-md --write` | Add bridge section to existing CLAUDE.md |
 | `claude-ide-bridge print-token` | Print auth token from active lock file |
@@ -291,7 +291,7 @@ claude-ide-bridge install claude-mem
 
 | Flag | Default | Description |
 |---|---|---|
-| `--slim` | off | Restrict to IDE-exclusive tools (default: full, ~140 tools) |
+| `--slim` | off | Restrict to IDE-exclusive tools (default: full, 177 tools) |
 | `--full` | on | No-op (retained for backward compat — full is the default since v2.43.0) |
 | `--watch` | off | Auto-restart on crash |
 | `--bind <host>` | `127.0.0.1` | Bind address (`0.0.0.0` for remote access) |
@@ -315,7 +315,7 @@ claude-ide-bridge install claude-mem
 |---|---|
 | [ARCHITECTURE.md](ARCHITECTURE.md) | System topology, request lifecycle, component map, design decisions |
 | [documents/platform-docs.md](documents/platform-docs.md) | Full tool reference — all 170+ tools with parameters and examples |
-| [documents/prompts-reference.md](documents/prompts-reference.md) | All MCP prompts (31 prompts, 12 plugin skills, 4 subagents) |
+| [documents/prompts-reference.md](documents/prompts-reference.md) | All MCP prompts (36 prompts, 12 plugin skills, 4 subagents) |
 | [docs/automation.md](docs/automation.md) | Automation hooks reference — all 18 events, policy schema, condition filters |
 | [docs/troubleshooting.md](docs/troubleshooting.md) | Diagnostics, common errors, and fixes |
 | [docs/remote-access.md](docs/remote-access.md) | VPS setup, OAuth 2.0, nginx/Caddy reverse proxy |
@@ -333,7 +333,7 @@ claude-ide-bridge install claude-mem
 
 ## Requirements
 
-- **Node.js ≥ 20** (bridge)
+- **Node.js ≥ 22** (bridge)
 - **VS Code, Cursor, or Windsurf** — optional. Headless mode covers git, terminals, GitHub, and LSP via `typescript-language-server`. Extension required for debugger, editor decorations, and live editor state.
 - **Claude Code CLI** — for local use. Remote MCP clients (claude.ai, Codex CLI) work via Streamable HTTP transport with OAuth 2.0.
 

package/README.md

@@ -1,15 +1,27 @@
 # Patchwork OS
 
 [![npm beta](https://img.shields.io/npm/v/patchwork-os/beta.svg?label=npm%20%40beta)](https://www.npmjs.com/package/patchwork-os)
+[![CI](https://github.com/Oolab-labs/patchwork-os/actions/workflows/ci.yml/badge.svg)](https://github.com/Oolab-labs/patchwork-os/actions/workflows/ci.yml)
+[![npm downloads](https://img.shields.io/npm/dm/patchwork-os.svg)](https://www.npmjs.com/package/patchwork-os)
 [![license](https://img.shields.io/npm/l/patchwork-os.svg)](LICENSE)
 
 ### Your personal AI runtime, local-first.
 
-> ⭐ If this saves you a config file or a debug session, drop a star — it's the only signal I get that it's helping.
+**You decide which model. You decide which actions need a human nod. You own the credentials, the logs, and the deployment.** Nothing phones home unless you [opt in to anonymous analytics](#telemetry).
+
+![Patchwork OS dashboard — connected bridge, live telemetry, and a 45-recipe library](docs/images/dashboard-overview.png)
 
 > Patchwork OS is a local-first personal AI runtime: pluggable model providers, hot-reloadable tools, YAML recipes, a delegation policy with approval queue, and a durable trace memory — all running on your machine, all under your policy.
 
-You decide which model. You decide which actions need a human nod. You own the credentials, the logs, and the deployment. Nothing phones home unless you [opt in to anonymous analytics](#telemetry).
+## Contents
+
+- [Two ways to use it](#the-same-codebase-ships-two-ways-to-use-it)
+- [Dashboard only — no editor required](#dashboard-only--no-code-editor-required)
+- [Claude IDE Bridge — quick start](#-claude-ide-bridge--quick-start)
+- [Windows](#windows)
+- [Architecture](#architecture)
+- [Telemetry](#telemetry)
+- [Contributing & support](#support)
 
 **Five primitives, one runtime:**
 
@@ -25,7 +37,9 @@ You decide which model. You decide which actions need a human nod. You own the c
 
 ---
 
-The same codebase ships **two ways to use it.** Pick the layer you need.
+## The same codebase ships two ways to use it
+
+Pick the layer you need.
 
 | | What you get | Install | Best for |
 |---|---|---|---|
@@ -42,7 +56,7 @@ Same codebase. Bridge is the foundation; Patchwork OS is the optional layer on t
 
 The dashboard is a standalone Next.js app that communicates with the bridge over HTTP. No editor extension required.
 
-**Prereqs:** [Node.js 20+](https://nodejs.org) · tmux on macOS/Linux (`brew install tmux` / `apt install tmux`) — auto-detected, falls back to background mode if absent. **Windows:** natively supported — no WSL required.
+**Prereqs:** [Node.js 22+](https://nodejs.org) · tmux on macOS/Linux (`brew install tmux` / `apt install tmux`) — auto-detected, falls back to background mode if absent. **Windows:** natively supported — no WSL required.
 
 ```bash
 npx patchwork-os@beta init   # scaffolds ~/.patchwork and generates a dashboard login (no install needed)
@@ -61,7 +75,7 @@ Open **http://localhost:3200** — that's it. `npx patchwork-os@beta init` auto-
 
 > Developers only — skip to [Dashboard Only](#dashboard-only--no-code-editor-required) above if you just want the web dashboard.
 
-**Prerequisites:** a supported code editor — **VS Code, Cursor, Windsurf, or Google Antigravity** (or JetBrains via the [companion plugin](#jetbrains-plugin)) — plus Node.js 20+ and the [Claude Code CLI](https://docs.anthropic.com/en/docs/claude-code). The bridge's LSP, debugger, and editor-state tools run through the editor extension; without one you're limited to the headless CLI subset.
+**Prerequisites:** a supported code editor — **VS Code, Cursor, Windsurf, or Google Antigravity** (or JetBrains via the [companion plugin](#jetbrains-plugin)) — plus Node.js 22+ and the [Claude Code CLI](https://docs.anthropic.com/en/docs/claude-code). The bridge's LSP, debugger, and editor-state tools run through the editor extension; without one you're limited to the headless CLI subset.
 
 ```bash
 # 1. Install the npm package
@@ -75,11 +89,16 @@ claude-ide-bridge install-extension
 claude-ide-bridge --workspace .
 
 # 4. Connect Claude Code (in another terminal)
+#    The env var skips Claude Code's built-in IDE-detection check — the bridge
+#    manages this connection itself. Add `export CLAUDE_CODE_IDE_SKIP_VALID_CHECK=true`
+#    to your shell profile so `claude --ide` is all you need going forward.
 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 177 tools to act on them.
 
+> ⭐ If this saves you a config file or a debug session, drop a star — it's the only signal I get that it's helping.
+
 **What the bridge gives Claude:**
 
 - Diagnostics, LSP navigation (goto / references / call hierarchy), refactoring with risk analysis
@@ -126,82 +145,13 @@ Bridge-only docs: [documents/platform-docs.md](documents/platform-docs.md)
 
 ---
 
-## 🪟 Windows Quick Start
-
-The bridge, VS Code extension, and full Patchwork OS orchestrator (`patchwork start`) all work natively on Windows — no WSL required. A PowerShell-native orchestrator is also available as `npm run start-all:win`. For architecture details, troubleshooting, and contribution patterns, see [docs/windows.md](docs/windows.md).
-
-### Prerequisites
-
-- Node.js 20+ (from [nodejs.org](https://nodejs.org))
-- VS Code, Cursor, or Windsurf
-- [Claude Code CLI](https://docs.anthropic.com/en/docs/claude-code)
-- PowerShell 5.1+ (built into Windows 10/11) or PowerShell 7+ (`pwsh`)
-
-### Bridge-only (recommended starting point)
-
-Open **PowerShell** or **cmd.exe**:
-
-```powershell
-# 1. Install
-npm install -g patchwork-os
-
-# 2. Install the VS Code extension
-claude-ide-bridge install-extension
-
-# 3. Start the bridge (bash-free entry point)
-npm run start:bridge
-# or equivalently:
-node "$(npm root -g)/patchwork-os/dist/index.js" --workspace .
-
-# 4. Connect Claude Code (new terminal)
-claude --ide
-```
-
-Type `/ide` in Claude Code to confirm the connection.
+## Windows
 
-### Full orchestrator (bridge + Claude + dashboard)
-
-Two options — both work on Windows, macOS, and Linux:
-
-```powershell
-# Option A: cross-platform Node.js orchestrator (recommended)
-npm run start-all:node
-npm run start-all:node -- --workspace C:\myproj --full --no-dashboard
-
-# Option B: PowerShell-native orchestrator (Windows only, no Node wrapper overhead)
-npm run start-all:win
-npm run start-all:win -- -NoDashboard -Workspace C:\myproj -Full
-```
-
-Both start the bridge, wait for the lock file, launch `claude --ide` and `remote-control`, start the Next.js dashboard on `http://localhost:3200`, poll until it's ready, then open it in your default browser. The health monitor restarts the bridge automatically if it crashes, with exponential backoff.
-
-```powershell
-# Node orchestrator options (--key value form)
-npm run start-all:node -- --full               # all 177 tools
-npm run start-all:node -- --no-dashboard       # skip dashboard
-npm run start-all:node -- --dashboard-port 3300
-npm run start-all:node -- --no-remote          # skip remote-control
-npm run start-all:node -- --notify my-topic    # ntfy.sh push notifications
-```
-
-### Known limitations on native Windows
-
-| Feature | Status |
-|---|---|
-| Bridge + extension (LSP, debugger, editor state) | ✅ Full support |
-| `npm run start:bridge` | ✅ Supported |
-| `npm run start-all:node` (Node.js orchestrator) | ✅ Supported — cross-platform |
-| `npm run start-all:win` (PS1 orchestrator) | ✅ Supported — Windows-native |
-| Dashboard (`http://localhost:3200`) | ✅ Opens automatically |
-| `patchwork start` / `npm run start-all` | ⚠️ Requires WSL2 or Git Bash (uses bash + tmux) |
-| `npm run remote:node` | ✅ Supported — cross-platform Node auto-restart wrapper |
-| `npm run remote` / `npm run vps` | ⚠️ Requires WSL2 or Git Bash |
-| Screenshot capture (standalone bridge) | ⚠️ Not yet supported; extension screenshot works via VS Code |
-| Credential storage | ✅ Uses DPAPI (Windows Data Protection API) via PowerShell |
+The bridge, VS Code extension, and orchestrator all run **natively on Windows — no WSL required**. Install the same way (`npm install -g patchwork-os`), then start the bridge with `npm run start:bridge` or the full stack with `npm run start-all:node` (cross-platform) / `npm run start-all:win` (PowerShell-native).
 
-### WSL2 alternative
+A few bash+tmux entry points (`patchwork start`, `npm run remote`) still need WSL2 or Git Bash. Credential storage uses Windows DPAPI.
 
-For full Patchwork OS functionality including orchestrator, recipes, and morning-brief, run everything inside WSL2 and install the VS Code Remote-WSL extension. The bridge extension loads on the WSL side automatically (`extensionKind: ["workspace"]`), giving full tool coverage.
+**Full setup, the orchestrator flag reference, and the native-Windows limitations table:** [docs/windows.md](docs/windows.md).
 
 ---
 
@@ -327,7 +277,7 @@ The package ships these in `templates/recipes/`. Recipes that need API keys are
 
 **Delegation policy presets** ([`templates/policies/`](templates/policies/)): five persona starters — conservative, developer, headless-CI, regulated-industry, personal-assistant. Copy one into `~/.patchwork/config.json` and restart.
 
-**Webhook recipe starters** ([`templates/recipes/webhook/`](templates/recipes/webhook/)): five webhook-triggered recipes — capture-thought, morning-brief (on-demand), meeting-prep, incident-intake, customer-escalation. Anything that can POST HTTP can drive these — iPhone Shortcut, Stream Deck, Home Assistant, NFC tag, monitoring tool.
+**Webhook recipe starters** ([`templates/recipes/webhook/`](templates/recipes/webhook/)): six webhook-triggered recipes — capture-thought, morning-brief (on-demand), meeting-prep, incident-intake, customer-escalation, apple-watch-health-log. Anything that can POST HTTP can drive these — iPhone Shortcut, Stream Deck, Home Assistant, NFC tag, monitoring tool.
 
 ### Automation hooks
 
@@ -419,7 +369,7 @@ Use whichever fits your mental model.
 
 | Category | Tools |
 |---|---|
-| LSP / Code Intelligence | `getDiagnostics`, `goToDefinition`, `findReferences`, `getCallHierarchy`, `renameSymbol`, `refactorAnalyze`, `explainSymbol`, … (37 tools) |
+| LSP / Code Intelligence | `getDiagnostics`, `goToDefinition`, `findReferences`, `getCallHierarchy`, `renameSymbol`, `refactorAnalyze`, `explainSymbol`, … (34 tools) |
 | Git | `getGitStatus`, `getGitDiff`, `gitCommit`, `gitPush`, `gitCheckout`, `gitBlame`, … (16 tools) |
 | GitHub | `githubCreatePR`, `githubListPRs`, `githubCreateIssue`, `githubPostPRReview`, … (13 tools) |
 | Terminal | `runInTerminal`, `createTerminal`, `getTerminalOutput`, `waitForTerminalOutput` |
@@ -558,6 +508,7 @@ Patchwork ships an **opt-in** anonymous usage summary. It is **disabled by defau
 
 - **Bugs & feature requests:** [GitHub Issues](https://github.com/Oolab-labs/patchwork-os/issues)
 - **Questions & community:** [GitHub Discussions](https://github.com/Oolab-labs/patchwork-os/discussions)
+- **Contributing:** see [CONTRIBUTING.md](CONTRIBUTING.md)
 
 ---
 

package/deploy/README.md

@@ -31,7 +31,7 @@ DOMAIN=bridge.example.com bash deploy/bootstrap-new-vps.sh
 ```
 
 The bootstrap script handles everything end-to-end:
-1. Installs Node.js 20, nginx, certbot
+1. Installs Node.js 22, nginx, certbot
 2. Creates a dedicated `claude-bridge` system user (non-root)
 3. Clones the repo to `/opt/claude-ide-bridge`
 4. Runs `npm ci && npm run build`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchwork-os",
-  "version": "0.2.0-beta.9.canary.86",
+  "version": "0.2.0-beta.9.canary.89",
   "description": "Your personal AI runtime, local-first. Patchwork OS gives any AI model a consistent set of tools, YAML recipes, a delegation policy with approval queue, and a durable trace memory — all on your machine, all under your policy.",
   "type": "module",
   "main": "dist/index.js",