@synapsor/runner 1.6.4 → 1.6.5

package/docs/agent-guided-setup.md

@@ -161,7 +161,8 @@ Next: connect the same reviewed tool surface to your MCP client.
 Workbench displays ready-to-copy configurations for:
 
 - Cursor project MCP;
-- Claude-compatible local stdio MCP;
+- Claude Code project MCP and Claude-compatible local stdio MCP;
+- VS Code project MCP;
 - Codex;
 - generic stdio MCP.
 
@@ -171,17 +172,18 @@ authority surface.
 For a terminal-rendered generic configuration, run:
 
 ```bash
-npx -y @synapsor/runner mcp config --absolute-paths
+synapsor-runner mcp config --absolute-paths
 ```
 
-Do not write into a client configuration without explicit user consent. Cursor
-has a separate consent-gated installer:
+Do not write into a client configuration without explicit user consent.
+Cursor, Claude Code, and VS Code have consent-gated project installers:
 
 ```bash
-npx -y @synapsor/runner mcp install cursor --project --dry-run
+synapsor-runner mcp install claude-code --project --dry-run
 ```
 
-Show the dry-run result first. Installation remains a human choice.
+Use `cursor` or `vscode` instead when that is the selected client. Show the
+dry-run result first. Installation remains a human choice.
 
 ## Guided Write Action
 

package/docs/auto-boundary-and-scoped-explore.md

@@ -206,23 +206,25 @@ The no-model composer, CLI Try, and external MCP routes remain fully supported
 when no provider is configured or a provider is unavailable. See [Workbench
 Ask With Your Model](workbench-ask.md).
 
-## Add The Authoring Tools To Cursor
+## Add The Authoring Tools To A Project MCP Client
 
 After activation, let Runner manage only its own project entry:
 
 ```bash
-synapsor-runner mcp install cursor \
+synapsor-runner mcp install claude-code \
   --project \
   --authoring \
   --project-root . \
   --yes
 
-synapsor-runner mcp status cursor --project
+synapsor-runner mcp status claude-code --project
 ```
 
-The Cursor config contains command paths and package identity, not database
-URLs, credential values, tenant values, or principal values. Authoring mode
-uses local stdio and advertises exactly:
+Use `cursor` or `vscode` instead of `claude-code` for those clients. Runner
+manages `.cursor/mcp.json`, `.mcp.json`, or `.vscode/mcp.json` and preserves
+unrelated entries. The client config contains command paths and package
+identity, not database URLs, credential values, tenant values, or principal
+values. Authoring mode uses local stdio and advertises exactly:
 
 ```text
 app.describe_data
@@ -358,16 +360,18 @@ join-safety, deny, drift, and boundary tests. It becomes active only after a
 human reviews and confirms its exact contract digest outside MCP.
 
 When activation disables temporary Explore, the named capability remains
-available. Update Cursor from authoring mode to the production config:
+available. Update the selected project client from authoring mode to the
+production config:
 
 ```bash
-synapsor-runner mcp install cursor \
+synapsor-runner mcp install claude-code \
   --project \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --yes
 ```
 
+Again, substitute `cursor` or `vscode` for the selected client.
 Production then advertises only reviewed named capabilities. It does not
 advertise `app.explore_data`.
 

package/docs/client-recipes.md

@@ -89,17 +89,30 @@ list. Then ask for the shared proposal call.
 
 ## Claude Code
 
-**Status:** configuration-tested with Claude Code 2.1.216 and
+**Status:** managed project configuration-tested with Claude Code 2.1.220 and
 protocol-tested; a manual model-driven call remains a release gate.
 
-Run the checked command from the repository root:
+Use Runner's owned project lifecycle:
 
 ```bash
-bash ./examples/support-plan-credit/mcp-client-examples/claude-code.sh
+synapsor-runner mcp install claude-code --project --dry-run \
+  --config ./examples/support-plan-credit/synapsor.runner.json \
+  --store ./tmp/support-plan-credit/local.db
+synapsor-runner mcp install claude-code --project --yes \
+  --config ./examples/support-plan-credit/synapsor.runner.json \
+  --store ./tmp/support-plan-credit/local.db
+synapsor-runner mcp status claude-code --project --check-launch
 ```
 
-Claude Code records project-scoped MCP configuration without embedding source
-credentials. It will print the exact proposal prompt after configuration.
+Runner merges only `mcpServers.synapsor` into the project `.mcp.json`, creates
+a backup, pins the exact Runner version, and never embeds source credentials.
+Restart or open a new Claude Code project session, approve the project server
+when prompted, and make the shared proposal call. Remove only Runner's intact
+entry with `synapsor-runner mcp uninstall claude-code --project --yes`.
+
+The older checked shell recipe remains available for users who intentionally
+prefer Claude Code's own configuration command:
+[`claude-code.sh`](../examples/support-plan-credit/mcp-client-examples/claude-code.sh).
 
 Official source checked 2026-07-20:
 [Claude Code MCP](https://code.claude.com/docs/en/mcp).
@@ -120,13 +133,29 @@ Official source checked 2026-07-20:
 
 ## VS Code
 
-**Status:** configuration-parsed and protocol-tested; manual VS Code UI
-behavior is not claimed.
+**Status:** managed project configuration-tested with VS Code 1.123.0 and
+protocol-tested; manual VS Code UI behavior is not claimed.
+
+Use Runner's owned project lifecycle:
+
+```bash
+synapsor-runner mcp install vscode --project --dry-run \
+  --config ./examples/support-plan-credit/synapsor.runner.json \
+  --store ./tmp/support-plan-credit/local.db
+synapsor-runner mcp install vscode --project --yes \
+  --config ./examples/support-plan-credit/synapsor.runner.json \
+  --store ./tmp/support-plan-credit/local.db
+synapsor-runner mcp status vscode --project --check-launch
+```
+
+Runner merges only `servers.synapsor` into `.vscode/mcp.json`, preserves JSONC
+comments and trailing commas, creates a backup, and pins the exact Runner
+version. Reload the VS Code window, start the server, inspect the listed tools,
+and ask for the shared proposal call. Remove only Runner's intact entry with
+`synapsor-runner mcp uninstall vscode --project --yes`.
 
-Copy or merge
-[`vscode.mcp.json`](../examples/support-plan-credit/mcp-client-examples/vscode.mcp.json)
-into `.vscode/mcp.json`. Start the server from VS Code, inspect the listed
-tools, and ask for the shared proposal call.
+The checked standalone template remains available at
+[`vscode.mcp.json`](../examples/support-plan-credit/mcp-client-examples/vscode.mcp.json).
 
 Official source checked 2026-07-20:
 [VS Code MCP servers](https://code.visualstudio.com/docs/agent-customization/mcp-servers).

package/docs/getting-started-own-database.md

@@ -30,7 +30,7 @@ inspect the whole selected schema and structured application artifacts
 -> draft disabled public DSL, canonical JSON, tests, and generation lock
 -> review scope, fields, analytics permissions, relationships, and budgets
 -> activate the exact exploration-boundary digest in local Workbench
--> install exactly app.describe_data and app.explore_data in Cursor
+-> install exactly app.describe_data and app.explore_data in your project MCP client
 -> ask a bounded row or PM-style aggregate question against staging
 -> Protect This Query into a disabled named capability
 -> activate that exact digest and remove broad Explore
@@ -241,32 +241,34 @@ There is intentionally no CLI or MCP command a coding agent can use to
 activate the draft. If the host does not refresh `tools/list`, reconnect the
 MCP server after activation as the Workbench instructs.
 
-## 5. Add the reviewed tools to Cursor
+## 5. Add the reviewed tools to your MCP client
 
-After setting trusted environment values, preview and install a project-scoped
-entry without hand-editing `.cursor/mcp.json`:
+After setting trusted environment values, choose Cursor, Claude Code, or VS
+Code and preview a project-scoped entry without hand-editing client JSON:
 
 ```bash
-synapsor-runner mcp install cursor --project --dry-run \
+synapsor-runner mcp install claude-code --project --dry-run \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
-synapsor-runner mcp install cursor --project --yes \
+synapsor-runner mcp install claude-code --project --yes \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
-synapsor-runner mcp status cursor --project --check-launch
+synapsor-runner mcp status claude-code --project --check-launch
 ```
 
+Use `cursor` or `vscode` in place of `claude-code` for those clients. Runner
+targets `.cursor/mcp.json`, `.mcp.json`, or `.vscode/mcp.json` as appropriate.
 Runner merges rather than replaces existing MCP servers, creates a backup,
 records an integrity marker, and is idempotent. The entry uses an exact Runner
 version and contains no database URL, trusted tenant/principal value, approval,
 apply, or revert authority. Remove only the Runner-owned entry with:
 
 ```bash
-synapsor-runner mcp uninstall cursor --project --yes
+synapsor-runner mcp uninstall claude-code --project --yes
 ```
 
 See the [host compatibility matrix](host-compatibility.md) for the precise
-Cursor evidence and MCP Apps limitation.
+host evidence and MCP Apps limitations.
 
 ## 6. Inspect local activation evidence
 
@@ -460,16 +462,16 @@ files.
 Generate or refresh MCP client snippets later with:
 
 ```bash
-npx -y @synapsor/runner mcp config generic --config ./synapsor.runner.json --store ./.synapsor/local.db
-npx -y @synapsor/runner mcp config claude-desktop --config ./synapsor.runner.json --store ./.synapsor/local.db
-npx -y @synapsor/runner mcp config cursor --config ./synapsor.runner.json --store ./.synapsor/local.db
-npx -y @synapsor/runner tools preview --config ./synapsor.runner.json --store ./.synapsor/local.db
+synapsor-runner mcp config generic --config ./synapsor.runner.json --store ./.synapsor/local.db
+synapsor-runner mcp config claude-desktop --config ./synapsor.runner.json --store ./.synapsor/local.db
+synapsor-runner mcp config cursor --config ./synapsor.runner.json --store ./.synapsor/local.db
+synapsor-runner tools preview --config ./synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 Call one generated tool locally before wiring an MCP client:
 
 ```bash
-npx -y @synapsor/runner smoke call --config ./synapsor.runner.json --store ./.synapsor/local.db
+synapsor-runner smoke call --config ./synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 `smoke call` uses the same runtime as the MCP server. It records evidence and

package/docs/guided-onboarding.md

@@ -315,9 +315,9 @@ Never reuse the model/read credential as the elevated setup connection.
 
 ## Connect An MCP Client
 
-Workbench generates ready-to-copy Cursor, Claude, Codex, and generic stdio
-snippets for the same reviewed authority. Stdio opens no network listener and
-needs no HTTP bearer credential.
+Workbench generates ready-to-copy Cursor, Claude Code/Desktop, VS Code, Codex,
+and generic stdio snippets for the same reviewed authority. Stdio opens no
+network listener and needs no HTTP bearer credential.
 
 Render the generic snippet:
 
@@ -325,10 +325,12 @@ Render the generic snippet:
 synapsor-runner mcp config --absolute-paths
 ```
 
-Preview a project-scoped Cursor change:
+Preview a managed project change for the client you use:
 
 ```bash
+synapsor-runner mcp install claude-code --project --dry-run
 synapsor-runner mcp install cursor --project --dry-run
+synapsor-runner mcp install vscode --project --dry-run
 ```
 
 No client config contains database URLs, trusted scope values, approval,

package/docs/host-compatibility.md

@@ -1,7 +1,7 @@
 # MCP Host Compatibility
 
 This matrix separates host evidence from protocol evidence. It was last
-reviewed on 2026-07-20. A working MCP SDK handshake is not presented as proof
+reviewed on 2026-07-25. A working MCP SDK handshake is not presented as proof
 that a specific editor renders an extension or protects app-only controls.
 
 | Host/surface | Status | Evidence and boundary |
@@ -14,32 +14,45 @@ that a specific editor renders an extension or protects app-only controls.
 | Generic stdio MCP client | Protocol-tested | Official MCP SDK initialization, tool listing, calls, resources, and display-only Apps metadata are covered in the suite. |
 | Generic Streamable HTTP MCP client | Protocol-tested | Official MCP SDK sessions, signed context, secret rotation, JWKS, mTLS, aliases, and session isolation are covered. |
 | Claude Desktop | Protocol-tested | Packaged stdio configuration and MCP transport are tested; manual host UI behavior varies by version and remains a release checklist item. |
-| Claude Code | Configuration-tested and protocol-tested | Claude Code 2.1.216 accepted the secret-free stdio configuration through `mcp add-json`; the same command completed MCP `tools/list`. A manual model-driven proposal call remains a release gate. |
+| Claude Code project `.mcp.json` lifecycle | Configuration-tested and protocol-tested | Runner install/status/uninstall tests cover preview, merge, backup, idempotency, ownership, tamper refusal, exact-version wiring, and the exact reviewed `tools/list`. Local Claude Code version observed: 2.1.220. A manual model-driven proposal call remains a release gate. |
 | Codex | Configuration-tested and protocol-tested | Codex CLI 0.144.6 accepted the secret-free stdio configuration through `codex mcp add`; the same command completed MCP `tools/list`. A manual model-driven proposal call remains a release gate. |
-| VS Code | Protocol-tested | The checked `.vscode/mcp.json` shape is parsed and the same stdio command completes MCP `tools/list`; manual editor UI behavior is not claimed. |
+| VS Code project `.vscode/mcp.json` lifecycle | Configuration-tested and protocol-tested | Runner install/status/uninstall tests cover JSONC-preserving merge, backup, idempotency, ownership, tamper refusal, exact-version wiring, and the exact reviewed `tools/list`. Local VS Code version observed: 1.123.0. Manual editor UI behavior is not claimed. |
 | OpenAI Agents SDK | Recipe-checked and protocol-tested | Packaged stdio/Streamable HTTP examples are syntax/safety checked and OpenAI-safe aliases are protocol-tested. The exact SDK agent call remains protocol-only until run with an owner-supplied API key. |
 | LangChain/LangGraph | Recipe-checked, protocol-only | The current `@langchain/mcp-adapters` recipe lists tools, rejects unsafe authority, and calls the proposal tool. The framework runtime has not been executed in this release environment. |
 | Google ADK | Recipe-checked, protocol-only | The current `McpToolset`/`StdioConnectionParams` recipe exposes only the two reviewed tools. The framework runtime has not been executed in this release environment. |
 | LlamaIndex | Recipe-checked, protocol-only | The current `BasicMCPClient` recipe lists tools and calls the proposal tool. The framework runtime has not been executed in this release environment. |
 
-## Cursor Project Setup
+## Managed Project Setup
 
-Current Cursor documentation supports project MCP configuration in
-`.cursor/mcp.json`. Runner manages only its `synapsor` entry:
+Runner manages only its `synapsor` entry in each supported project-local
+configuration:
 
 ```bash
 synapsor-runner mcp install cursor --project --dry-run
-synapsor-runner mcp install cursor --project --yes
-synapsor-runner mcp status cursor --project --check-launch
+synapsor-runner mcp install claude-code --project --dry-run
+synapsor-runner mcp install vscode --project --dry-run
+
+synapsor-runner mcp install claude-code --project --yes
+synapsor-runner mcp status claude-code --project --check-launch
 ```
 
-The generated entry contains command paths only. Database credentials and
-trusted tenant/principal values must come from the environment that launches
-Runner. Other Cursor MCP servers and settings are preserved.
+Cursor uses `.cursor/mcp.json` and `mcpServers`; Claude Code uses `.mcp.json`
+and `mcpServers`; VS Code uses `.vscode/mcp.json` and `servers`. The generated
+entry contains command paths and an exact package version only. Database
+credentials and trusted tenant/principal values must come from the environment
+that launches Runner. Other servers and project settings are preserved.
+
+`--dry-run` never writes. An approved install creates a backup and an integrity
+marker. A repeated install is idempotent; uninstall removes only an unchanged,
+Runner-owned entry. Claude Code still requires its own human project-server
+approval, and VS Code still requires the operator to reload/start the server.
+Those host actions do not grant Synapsor approval or commit authority.
 
 Primary references:
 
 - [Cursor MCP documentation](https://cursor.com/docs/context/mcp)
+- [Claude Code MCP documentation](https://code.claude.com/docs/en/mcp)
+- [VS Code MCP servers](https://code.visualstudio.com/docs/agent-customization/mcp-servers)
 - [MCP TypeScript SDK](https://github.com/modelcontextprotocol/typescript-sdk)
 - [MCP Apps specification](https://github.com/modelcontextprotocol/ext-apps/blob/main/specification/2026-01-26/apps.mdx)
 

package/docs/mcp-client-setup.md

@@ -101,7 +101,7 @@ with tenant/principal bound from verified claims. Details: [HTTP MCP](http-mcp.m
 Print a snippet without modifying any client files:
 
 ```bash
-npx -y @synapsor/runner mcp config claude-desktop \
+synapsor-runner mcp config claude-desktop \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
 ```
@@ -121,7 +121,7 @@ For OpenAI Agents SDK, generate the Streamable HTTP start command and Python
 snippet:
 
 ```bash
-npx -y @synapsor/runner mcp client-config \
+synapsor-runner mcp client-config \
   --client openai-agents \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
@@ -130,13 +130,13 @@ npx -y @synapsor/runner mcp client-config \
 The older form is still supported:
 
 ```bash
-npx -y @synapsor/runner mcp configure --client claude-desktop --config ./synapsor.runner.json --store ./.synapsor/local.db
+synapsor-runner mcp configure --client claude-desktop --config ./synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 Write is opt-in and requires an explicit destination:
 
 ```bash
-npx -y @synapsor/runner mcp configure \
+synapsor-runner mcp configure \
   --client cursor \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
@@ -267,6 +267,21 @@ examples/mcp-client-configs/cursor.json
 examples/mcp-client-configs/vscode.json
 ```
 
+For project-local Cursor, Claude Code, or VS Code configuration, prefer the
+managed lifecycle instead of editing JSON:
+
+```bash
+synapsor-runner mcp install claude-code --project --dry-run
+synapsor-runner mcp install claude-code --project --yes
+synapsor-runner mcp status claude-code --project --check-launch
+```
+
+Use `cursor` or `vscode` instead when that is the selected client. Runner
+backs up and merges only its own entry, pins the exact package version, and
+keeps credentials and trusted scope out of the client file. Claude Desktop is
+global application configuration and remains a checked template rather than a
+managed project install.
+
 Each example uses the same stdio command/args/env structure. Replace the placeholder environment variables in your client settings or shell environment.
 
 These checked-in desktop examples use stdio, which is the recommended local

package/docs/mcp-clients.md

@@ -33,7 +33,8 @@ the checked-in client JSON.
 
 ## Stdio
 
-Use stdio for Claude Desktop, Cursor, and other local MCP clients:
+Use stdio for Claude Code, Claude Desktop, Cursor, VS Code, and other local MCP
+clients:
 
 ```json
 {
@@ -65,25 +66,52 @@ environment. Supply the required env values through the OS process environment
 or a local secret-manager wrapper; do not paste production credentials into a
 repository file.
 
-### Cursor
+### Managed Project Installs
 
-Prefer Runner's owned project lifecycle for one repository:
+Runner can safely manage its own project-local entry for Cursor, Claude Code,
+or VS Code. Choose the client you actually use:
 
 ```bash
 synapsor-runner mcp install cursor --project --dry-run \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
-synapsor-runner mcp install cursor --project --yes \
+synapsor-runner mcp install claude-code --project --dry-run \
+  --config ./synapsor.runner.json \
+  --store ./.synapsor/local.db
+synapsor-runner mcp install vscode --project --dry-run \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
-synapsor-runner mcp status cursor --project --check-launch
 ```
 
-Runner previews the merge, backs up an existing `.cursor/mcp.json`, preserves
-other MCP servers/settings, writes an exact-version `npx` invocation, and
-tracks only its own entry with an integrity marker. Repeating install is
-idempotent. `mcp uninstall cursor --project --yes` removes only that intact,
-Runner-owned entry and also creates a backup.
+Replace `--dry-run` with `--yes` only after reviewing the preview, then verify
+the selected client:
+
+```bash
+synapsor-runner mcp install claude-code --project --yes \
+  --config ./synapsor.runner.json \
+  --store ./.synapsor/local.db
+synapsor-runner mcp status claude-code --project --check-launch
+```
+
+| Client | Managed project file | Server map |
+| --- | --- | --- |
+| Cursor | `.cursor/mcp.json` | `mcpServers.synapsor` |
+| Claude Code | `.mcp.json` | `mcpServers.synapsor` |
+| VS Code | `.vscode/mcp.json` | `servers.synapsor` |
+
+Runner previews the merge, backs up an existing file, preserves unrelated
+servers and settings, writes an exact-version `npx` invocation, and tracks only
+its own entry with a client-specific integrity marker under `.synapsor/`.
+Repeating install is idempotent. VS Code JSON-with-comments, comments, and
+trailing commas are preserved. `mcp uninstall <client> --project --yes`
+removes only an intact Runner-owned entry and creates another backup.
+
+No managed client file contains a database URL, credential, trusted tenant or
+principal value, approval authority, or apply authority. Claude Code asks the
+human to approve project-scoped MCP servers; that host approval does not grant
+Synapsor activation, proposal approval, or writeback authority.
+
+### Cursor
 
 For global setup, merge `cursor-global.mcp.json` through Cursor's MCP settings
 and replace every `<absolute-path-to-bundle>` marker. Restart the MCP server
@@ -100,6 +128,14 @@ the secured localhost workbench or operator CLI. No Add to Cursor deep link is
 generated because Runner has not verified a currently documented generic
 payload for this server. See [Host Compatibility](host-compatibility.md).
 
+### Claude Code And VS Code
+
+For Claude Code, restart or open a new project session after installation and
+approve the project MCP server when prompted. For VS Code, reload the window
+and start the Synapsor server. `mcp status <client> --project --check-launch`
+validates the generated command with a real MCP initialize and `tools/list`
+handshake; it does not claim that a model completed a host UI interaction.
+
 ### OpenAI Agents SDK
 
 Install the SDK in your agent project and run either TypeScript template:

package/docs/release-notes.md

@@ -10,7 +10,29 @@ npx -y @synapsor/runner demo --quick
 The OSS runner command is `synapsor-runner`. The `synapsor` command is reserved
 for the Synapsor Cloud CLI.
 
-## 1.6.4 (prepared, not published)
+## 1.6.5 (prepared, not published)
+
+### Managed Claude Code and VS Code project MCP installs
+
+- The same reviewed, backup-producing project lifecycle previously available
+  for Cursor now manages Claude Code `.mcp.json` and VS Code
+  `.vscode/mcp.json`.
+- Install previews preserve unrelated project settings, pin the exact Runner
+  version, write no credentials or trusted scope, and refuse unowned or
+  tampered `synapsor` entries. Reinstall is idempotent and uninstall removes
+  only Runner's intact entry.
+- VS Code JSONC comments and trailing commas survive install and uninstall.
+  `mcp status <client> --project --check-launch` validates the generated
+  command against the exact reviewed MCP tool list.
+- README, Workbench, onboarding, host recipes, and `doctor` now present Cursor,
+  Claude Code, and VS Code as peer project clients. Existing Cursor commands
+  and configuration remain compatible.
+
+Prepared package versions: `@synapsor/runner@1.6.5` and
+`synapsor-runner@1.6.5`. Spec 1.7.0 and DSL 1.7.0 are unchanged. No package is
+published by this change.
+
+## 1.6.4 (published 2026-07-25)
 
 ### Review-correct onboarding and reviewed relationship paths
 
@@ -77,17 +99,9 @@ for the Synapsor Cloud CLI.
   their exact normalized bytes/digests and existing tool lists remain
   unchanged unless the feature is adopted.
 
-Prepared package versions: `@synapsor/runner@1.6.4`,
+Published package versions: `@synapsor/runner@1.6.4`,
 `@synapsor/spec@1.7.0`, `@synapsor/dsl@1.7.0`, and the optional
 `synapsor-runner@1.6.4` command alias.
-No package is published by this change.
-
-Publish Spec first, then DSL, then the scoped Runner, and finally its exact
-version command alias. Force the final registry-only Runner dependency check
-with
-`VERIFY_PACKED_RUNNER_USE_LOCAL_SPEC=0 ./scripts/verify-packed-runner.sh` after
-Spec 1.7.0 is visible on npm, and verify the alias only after
-`@synapsor/runner@1.6.4` is visible.
 
 ## 1.6.3 (published 2026-07-24)
 

package/docs/troubleshooting-first-run.md

@@ -84,9 +84,10 @@ Check:
 ```bash
 synapsor-runner boundary status --json
 synapsor-runner boundary diff --json
-synapsor-runner mcp status cursor --project
+synapsor-runner mcp status claude-code --project
 ```
 
+Use `cursor` or `vscode` instead when that is the selected client.
 The exact boundary digest must be active, the profile must explicitly be
 `development` or `staging`, the generation lock and compiler/Spec versions
 must be current, and the inspected database role must still be SELECT-only,
@@ -133,12 +134,12 @@ Select **Clear** after a session to cancel active work and discard in-memory
 provider configuration/history. See [Workbench Ask With Your
 Model](workbench-ask.md).
 
-## Cursor Has Production Tools Instead Of Authoring Tools
+## A Project Client Has Production Tools Instead Of Authoring Tools
 
 Install the managed local authoring entry only after boundary activation:
 
 ```bash
-synapsor-runner mcp install cursor \
+synapsor-runner mcp install claude-code \
   --project \
   --authoring \
   --project-root . \
@@ -151,13 +152,15 @@ production config. The protected named capability remains available while
 Explore disappears:
 
 ```bash
-synapsor-runner mcp install cursor \
+synapsor-runner mcp install claude-code \
   --project \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --yes
 ```
 
+Use `cursor` or `vscode` instead of `claude-code` for those clients.
+
 ## Boundary Became Stale After A Schema Or Grant Change
 
 Generated authority is bound to the schema, role, grants, ownership, RLS
@@ -204,19 +207,20 @@ Open the secured Workbench, run the real source-unchanged staging Data PR
 preview, review the complete digest, and activate it there. There is
 intentionally no activation CLI command to hand to a coding agent.
 
-## Activated Tool Does Not Appear In Cursor
+## Activated Tool Does Not Appear In The MCP Client
 
 Some MCP hosts do not refresh `tools/list` for a running stdio session. First
 confirm that Runner's active tool surface changed:
 
 ```bash
 synapsor-runner action status --json
-synapsor-runner mcp status cursor --project --check-launch
+synapsor-runner mcp status claude-code --project --check-launch
 ```
 
+Use `cursor` or `vscode` instead of `claude-code` for those clients.
 Then reconnect or restart the project MCP server as directed by the Workbench.
 Do not work around a stale host session by adding approval, apply, activation,
-credentials, tenant values, or raw SQL to the Cursor configuration.
+credentials, tenant values, or raw SQL to the client configuration.
 
 ## Safe Action Validation Reports Review Placeholders
 
@@ -531,7 +535,7 @@ Fix:
 Regenerate the snippet:
 
 ```bash
-npx -y @synapsor/runner mcp config claude-desktop \
+synapsor-runner mcp config claude-desktop \
   --absolute-paths \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synapsor/runner",
-  "version": "1.6.4",
+  "version": "1.6.5",
   "description": "Open-source MCP runtime for governed Postgres/MySQL access with reviewed capabilities, proposals, guarded writes, receipts, and replay.",
   "license": "Apache-2.0",
   "type": "module",
@@ -95,6 +95,7 @@
     "@modelcontextprotocol/sdk": "1.29.0",
     "@synapsor/spec": "^1.7.0",
     "jose": "6.2.3",
+    "jsonc-parser": "3.3.1",
     "mysql2": "^3.11.0",
     "pdf-lib": "1.17.1",
     "pg": "^8.13.0",