@synapsor/runner 1.6.3 → 1.6.5

package/docs/limitations.md

@@ -1,14 +1,14 @@
 # Limitations
 
-Synapsor Runner is intentionally narrow. Version 1.6 adds deterministic
-whole-application boundary drafting and a local authoring-only Explore ->
-Protect path on top of guarded writes. Version 1.6.1 also adds opt-in
-proposal/evidence freshness for exact same-source direct-SQL proposals. It does
-not turn Runner into a generic database query tool, claim Synapsor Cloud scale,
-or claim an enterprise SLA. Version 1.6.3 adds guided onboarding, verified
-approval-role evidence, default-off exact-digest supervised execution for a
-narrow write subset, and quiet human-attention delivery without changing
-existing manual behavior.
+Synapsor Runner is intentionally narrow. It combines deterministic
+whole-application boundary drafting, local authoring-only Explore -> Protect,
+guarded writes, opt-in proposal/evidence freshness, verified operator identity,
+default-off supervised execution, and quiet human-attention delivery. Reviewed
+aggregate paths are limited to proven star/depth-two many-to-one relationships,
+not a general join planner. Optional local Workbench Ask is a client of the
+existing reviewed tools; the complete no-model path remains the default.
+Runner does not become a generic database query tool, Synapsor Cloud, or an
+enterprise SLA.
 
 ## Supported
 
@@ -63,10 +63,20 @@ existing manual behavior.
   existing Synapsor definitions. Generated authority starts disabled.
 - Local development/staging Scoped Explore through exactly
   `app.describe_data` and `app.explore_data`, with no SQL-string argument.
+- Optional development/staging loopback Workbench Ask through OpenAI,
+  Anthropic, or a configured OpenAI-compatible endpoint. Provider calls use the
+  exact active MCP/runtime surface, explicit direct-egress consent, in-memory
+  credential/history state, fixed tool/time/size/token bounds, and
+  proposal-only write behavior.
 - Reviewed PM-style aggregate Explore with `count`, `count_distinct`, `sum`,
   `avg`, categorical dimensions, fixed time buckets, typed filters, bounded
-  top-N, optional one-hop proven many-to-one relationships, cohort suppression,
-  and durable extraction/differencing budgets.
+  top-N, up to three reviewed relationship paths of at most two proven
+  many-to-one links each, cohort suppression, and durable
+  extraction/differencing budgets.
+- Demand-driven operator review for an exact catalog-proven relationship,
+  including an explicit missing-row choice for nullable links. The model cannot
+  activate a relationship, and every participating relation receives trusted
+  tenant/principal scope.
 - Protect This Query to public DSL, canonical JSON, tests, and a disabled named
   capability that survives Explore shutdown after exact-digest activation.
 - Generation-lock drift detection for generated authority. Manually authored
@@ -123,14 +133,18 @@ truth for the model-facing tools.
 - Unbounded/high-throughput or multi-region ledger scale.
 - Managed fleet, SLA, compliance certification, or production support guarantee.
 - Production, shared HTTP, remote, or non-loopback Scoped Explore.
+- Production, shared HTTP, remote, or non-loopback Workbench Ask; model-facing
+  provider configuration; Synapsor-relayed provider traffic; durable chat
+  history; automatic provider retries; exact monetary spend enforcement; or
+  universal compatibility with OpenAI-compatible servers.
 - Automatic supervised execution for hard DELETE, reversible changes, bounded
   sets, app-owned/external effects, or writes without deterministic conflict,
   deduplication, freshness, and receipt authority.
 - Arbitrary aggregate expressions, dynamic identifiers, unrestricted joins,
   many-to-many joins, formulas, window functions, subqueries, `HAVING`,
-  user-defined functions, or a statistical privacy guarantee. Version 1.6
-  supports only the explicitly reviewed authoring cube described above and
-  fixed protected named capabilities produced from it.
+  user-defined functions, or a statistical privacy guarantee. Runner supports
+  only the explicitly reviewed authoring cube described above and fixed
+  protected named capabilities produced from it.
 - Automatic policy widening or activation from graduated-trust metrics.
 - Immutable/WORM compliance storage from the local report exporter.
 
@@ -165,6 +179,12 @@ jobs. Mixed-minor v3/v4 rolling compensation is not claimed.
 See [Running A Small Runner
 Fleet](running-a-runner-fleet.md).
 
+Workbench Ask token accounting uses provider-reported usage. A provider that
+omits or misreports usage cannot provide exact token or monetary enforcement.
+Runner still enforces request/response, tool-result, iteration, history, and
+wall-clock bounds. A provider outage does not disable the no-model composer or
+external MCP path. See [Workbench Ask With Your Model](workbench-ask.md).
+
 Use this wording:
 
 ```text

package/docs/local-mode.md

@@ -44,13 +44,13 @@ when you do not want to change your host Node version.
 Create a starter config without putting credentials in the file:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner init --engine postgres --mode review
+npx -y @synapsor/runner init --engine postgres --mode review
 ```
 
 For MySQL:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner init --engine mysql --mode review --output synapsor.mysql.runner.json
+npx -y @synapsor/runner init --engine mysql --mode review --output synapsor.mysql.runner.json
 ```
 
 The generated config uses environment-variable names for read/write URLs and trusted context. Edit the table, column, and capability names before serving tools.
@@ -63,8 +63,8 @@ persisted into proposals, evidence, query audit, runner state, or replay.
 For a reviewed own-database setup generated from explicit selections, use:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner init --spec onboarding-selection.json --non-interactive
-npx -y -p @synapsor/runner synapsor-runner doctor --config synapsor.runner.json
+npx -y @synapsor/runner init --spec onboarding-selection.json --non-interactive
+npx -y @synapsor/runner doctor --config synapsor.runner.json
 ```
 
 `doctor --config` checks config validation, required environment variables,
@@ -76,7 +76,7 @@ and the semantic MCP tool boundary without printing credential values.
 Use stdio for local MCP clients that launch Synapsor Runner:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner mcp serve \
+npx -y @synapsor/runner mcp serve \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
 ```
@@ -87,7 +87,7 @@ MCP client:
 ```bash
 export SYNAPSOR_RUNNER_HTTP_TOKEN="$(node -e 'process.stdout.write(require("node:crypto").randomBytes(32).toString("base64url"))')"
 
-npx -y -p @synapsor/runner synapsor-runner mcp serve-streamable-http \
+npx -y @synapsor/runner mcp serve-streamable-http \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --auth-token-env SYNAPSOR_RUNNER_HTTP_TOKEN
@@ -131,19 +131,19 @@ If neither is set, the CLI uses:
 List proposals:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner proposals list --store ./.synapsor/local.db
+npx -y @synapsor/runner proposals list --store ./.synapsor/local.db
 ```
 
 Show a proposal:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner proposals show wrp_123 --store ./.synapsor/local.db
+npx -y @synapsor/runner proposals show wrp_123 --store ./.synapsor/local.db
 ```
 
 Check a freshness-enabled proposal without copying its id:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner proposals check-freshness latest \
+npx -y @synapsor/runner proposals check-freshness latest \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
 ```
@@ -151,7 +151,7 @@ npx -y -p @synapsor/runner synapsor-runner proposals check-freshness latest \
 Approve:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner proposals approve wrp_123 \
+npx -y @synapsor/runner proposals approve wrp_123 \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --actor local_reviewer \
@@ -177,7 +177,7 @@ revalidates again because source data can change after approval. See
 Create a guarded writeback job from an approved proposal:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner proposals writeback-job wrp_123 \
+npx -y @synapsor/runner proposals writeback-job wrp_123 \
   --store ./.synapsor/local.db \
   --project local \
   --runner local_runner \
@@ -189,7 +189,7 @@ The generated job uses the public `synapsor.writeback-job.v1` protocol and can b
 ```bash
 export SYNAPSOR_DATABASE_WRITE_URL="postgresql://writer:<password>@localhost:5432/app"
 SYNAPSOR_ENGINE=postgres \
-npx -y -p @synapsor/runner synapsor-runner apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y @synapsor/runner apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 When `--config` is passed, direct SQL writeback reads the writer connection from
@@ -201,7 +201,7 @@ Passing `--store` records the terminal `synapsor.execution-receipt.v1` locally.
 Reject:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner proposals reject wrp_123 \
+npx -y @synapsor/runner proposals reject wrp_123 \
   --store ./.synapsor/local.db \
   --reason "policy evidence is incomplete" \
   --yes
@@ -222,7 +222,7 @@ pilot, use [Shadow Studies](shadow-studies.md).
 Start a localhost-only review UI:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner ui --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y @synapsor/runner ui --config synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 The UI shows setup summary, semantic tools, proposal states, exact diffs,
@@ -240,20 +240,20 @@ tools, MCP commit tools, or controls that widen configured tables/columns.
 Show replay:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner replay show wrp_123 --store ./.synapsor/local.db
-npx -y -p @synapsor/runner synapsor-runner replay show --proposal wrp_123 --store ./.synapsor/local.db
-npx -y -p @synapsor/runner synapsor-runner replay show --replay replay_wrp_123 --store ./.synapsor/local.db
-npx -y -p @synapsor/runner synapsor-runner replay show --evidence ev_123 --store ./.synapsor/local.db
+npx -y @synapsor/runner replay show wrp_123 --store ./.synapsor/local.db
+npx -y @synapsor/runner replay show --proposal wrp_123 --store ./.synapsor/local.db
+npx -y @synapsor/runner replay show --replay replay_wrp_123 --store ./.synapsor/local.db
+npx -y @synapsor/runner replay show --evidence ev_123 --store ./.synapsor/local.db
 ```
 
 Export replay:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner replay export wrp_123 \
+npx -y @synapsor/runner replay export wrp_123 \
   --store ./.synapsor/local.db \
   --output replay.json
 
-npx -y -p @synapsor/runner synapsor-runner replay export --proposal wrp_123 \
+npx -y @synapsor/runner replay export --proposal wrp_123 \
   --format markdown \
   --store ./.synapsor/local.db \
   --output replay.md

package/docs/mcp-audit.md

@@ -1,6 +1,6 @@
 # MCP database risk review
 
-`npx -y -p @synapsor/runner synapsor-runner audit <target>` performs a
+`npx -y @synapsor/runner audit <target>` performs a
 static MCP database risk review over an exported tool manifest, a remote MCP
 `tools/list` endpoint, or a stdio MCP server. The `mcp audit` subcommand is also
 available for users who look for the command under the MCP namespace.
@@ -26,7 +26,7 @@ MCP annotations are treated as hints, not enforcement.
 Built-in database MCP risk example:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit --example dangerous-db-mcp
+npx -y @synapsor/runner audit --example dangerous-db-mcp
 ```
 
 This bundled example does not require a source checkout or local examples file.
@@ -37,7 +37,7 @@ table/column inputs, and model-controlled tenant/principal fields.
 Human-readable output:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit ./tools-list.json
+npx -y @synapsor/runner audit ./tools-list.json
 ```
 
 The default terminal report groups repeated findings into the three most
@@ -46,32 +46,32 @@ and one next action instead of repeating the same explanation for every tool.
 Use the complete view when triaging every finding:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit ./tools-list.json --verbose
+npx -y @synapsor/runner audit ./tools-list.json --verbose
 ```
 
 Remote `tools/list` endpoint with a bearer token kept in the environment:
 
 ```bash
 SYNAPSOR_MCP_AUDIT_BEARER="..." \
-npx -y -p @synapsor/runner synapsor-runner audit https://mcp.example.com --format json
+npx -y @synapsor/runner audit https://mcp.example.com --format json
 ```
 
 Remote endpoint with a custom bearer-token environment variable:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit https://mcp.example.com --bearer-env MCP_AUDIT_TOKEN --format json
+npx -y @synapsor/runner audit https://mcp.example.com --bearer-env MCP_AUDIT_TOKEN --format json
 ```
 
 Stdio MCP server:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit 'stdio:node ./server.mjs' --timeout-ms 5000
+npx -y @synapsor/runner audit 'stdio:node ./server.mjs' --timeout-ms 5000
 ```
 
 JSON output:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit ./tools-list.json --format json
+npx -y @synapsor/runner audit ./tools-list.json --format json
 ```
 
 The JSON contract remains `synapsor.mcp-audit.v1`; its published schema is
@@ -80,19 +80,19 @@ The JSON contract remains `synapsor.mcp-audit.v1`; its published schema is
 SARIF 2.1.0 output for code-scanning ingestion:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit ./tools-list.json --format sarif > mcp-audit.sarif
+npx -y @synapsor/runner audit ./tools-list.json --format sarif > mcp-audit.sarif
 ```
 
 Markdown output for issues, PRs, or security review notes:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit --example dangerous-db-mcp --format markdown
+npx -y @synapsor/runner audit --example dangerous-db-mcp --format markdown
 ```
 
 Inspect a project-scoped Cursor configuration without launching anything:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit \
+npx -y @synapsor/runner audit \
   --mcp-config ./.cursor/mcp.json \
   --format markdown
 ```
@@ -102,7 +102,7 @@ as `requires_operator_verification`. To query one reviewed stdio command, name
 that exact server and give explicit consent:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit \
+npx -y @synapsor/runner audit \
   --mcp-config ./.cursor/mcp.json \
   --live-server synapsor \
   --yes \
@@ -132,7 +132,7 @@ Audit can create a separate review directory without editing or activating the
 source configuration:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit generate \
+npx -y @synapsor/runner audit generate \
   ./tools-list.json \
   --output ./synapsor-audit-candidates
 ```
@@ -141,7 +141,7 @@ Open the same blocked candidate directly in the secured local review
 workbench:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner audit generate \
+npx -y @synapsor/runner audit generate \
   ./tools-list.json \
   --output ./synapsor-audit-candidates \
   --open-ui

package/docs/mcp-client-setup.md

@@ -57,7 +57,7 @@ provisions the same environment value to Runner and the authorized client:
 ```bash
 export SYNAPSOR_RUNNER_HTTP_TOKEN="$(node -e 'process.stdout.write(require("node:crypto").randomBytes(32).toString("base64url"))')"
 
-npx -y -p @synapsor/runner synapsor-runner mcp serve-streamable-http \
+npx -y @synapsor/runner mcp serve-streamable-http \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --auth-token-env SYNAPSOR_RUNNER_HTTP_TOKEN
@@ -69,7 +69,7 @@ OpenAI-safe aliases while keeping canonical Synapsor capability names in MCP
 metadata:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner mcp serve-streamable-http \
+npx -y @synapsor/runner mcp serve-streamable-http \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --auth-token-env SYNAPSOR_RUNNER_HTTP_TOKEN \
@@ -85,7 +85,7 @@ same time.
 Preview the exact alias mapping before wiring a client:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner tools preview \
+npx -y @synapsor/runner tools preview \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --alias-mode openai
@@ -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 -p @synapsor/runner 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 -p @synapsor/runner 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 -p @synapsor/runner synapsor-runner mcp client-config \
 The older form is still supported:
 
 ```bash
-npx -y -p @synapsor/runner 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 -p @synapsor/runner synapsor-runner mcp configure \
+synapsor-runner mcp configure \
   --client cursor \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
@@ -162,7 +162,7 @@ standalone local UI or terminal for human review.
 From the runner repository:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner mcp serve --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
+npx -y @synapsor/runner mcp serve --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 For reproducible deployments, pin an exact stable version in package manifests
@@ -172,7 +172,7 @@ the current `latest` release.
 For standard app/server HTTP MCP mode:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner mcp serve-streamable-http \
+npx -y @synapsor/runner mcp serve-streamable-http \
   --config ./examples/mcp-postgres-billing/synapsor.runner.json \
   --store ./.synapsor/local.db \
   --auth-token-env SYNAPSOR_RUNNER_HTTP_TOKEN
@@ -190,10 +190,7 @@ sessions, so do not use it for a shared identity deployment.
     "synapsor-runner": {
       "command": "npx",
       "args": [
-        "-y",
-        "-p",
-        "@synapsor/runner",
-        "synapsor-runner",
+        "-y", "@synapsor/runner",
         "mcp",
         "serve",
         "--config",
@@ -235,7 +232,7 @@ small tool-call test.
 First confirm what Runner exposes:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner tools preview \
+npx -y @synapsor/runner tools preview \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
 ```
@@ -270,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,13 +33,14 @@ 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
 {
   "command": "npx",
   "args": [
-    "-y", "-p", "@synapsor/runner", "synapsor-runner",
+    "-y", "@synapsor/runner",
     "mcp", "serve", "--config", "./synapsor.runner.json",
     "--store", "./.synapsor/local.db"
   ]
@@ -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/migrating-to-synapsor-spec.md

@@ -150,11 +150,15 @@ use Runner/spec/DSL 1.1 together. Omitted fields preserve 1.0 behavior.
 
 ## 1.6 Generated Authority And Supervised Execution
 
-Runner 1.6.3, Spec 1.6.0, and DSL 1.6.0 are additive. Existing hand-authored
+Runner 1.6.4, Spec 1.7.0, and DSL 1.7.0 are additive. Existing hand-authored
 DSL/JSON/config projects do not need Auto Boundary, Workbench, a generation
 lock, schema rescanning, or supervised execution. Contracts that omit the new
 fields retain their previous canonical normalization and digest.
 
+Spec/DSL 1.7.0 add optional reviewed relationship-path fields and `LINK`
+syntax. The legacy one-hop relationship form remains accepted and canonical;
+an unchanged legacy contract retains its exact normalized bytes and digest.
+
 Auto Boundary writes a generation lock only for authority it generated.
 Drift enforcement applies only when `synapsor.runner.json` explicitly
 references that lock under `generated_authority`; manually authored projects

package/docs/openai-agents-sdk.md

@@ -10,7 +10,7 @@ surface.
 ```bash
 export SYNAPSOR_RUNNER_HTTP_TOKEN="$(node -e 'process.stdout.write(require("node:crypto").randomBytes(32).toString("base64url"))')"
 
-npx -y -p @synapsor/runner synapsor-runner mcp serve-streamable-http \
+npx -y @synapsor/runner mcp serve-streamable-http \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --auth-token-env SYNAPSOR_RUNNER_HTTP_TOKEN \
@@ -30,7 +30,7 @@ model and maps calls back to canonical Synapsor capability names such as
 ## Generate The Snippet
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner mcp client-config \
+npx -y @synapsor/runner mcp client-config \
   --client openai-agents \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \

package/docs/proposal-evidence-freshness.md

@@ -1,6 +1,6 @@
 # Proposal And Evidence Freshness
 
-Runner 1.6.1 adds an optional fail-closed freshness gate for proposals whose
+Runner provides an optional fail-closed freshness gate for proposals whose
 review depends on live source state.
 
 This closes two different review gaps without changing the model-facing MCP
@@ -11,8 +11,8 @@ surface:
 2. A proposal can declare reviewed supporting rows whose exact versions must
    still match before approval and again at apply.
 
-Target-row drift was already blocked by the exact conflict guard at apply.
-Version 1.6.1 does not replace that protection. It adds an earlier review-time
+Target-row drift is also blocked by the exact conflict guard at apply.
+Freshness does not replace that protection. It adds an earlier review-time
 check and extends the final transaction to declared same-source dependencies.
 
 ## What Freshness Does And Does Not Mean
@@ -36,10 +36,10 @@ new source read and create a new proposal with a new hash and review.
 
 ## Configuration
 
-Freshness is a Runner deployment overlay in `synapsor.runner.json`. Version
-1.6.1 adds no DSL clause and no canonical Spec field. Existing hand-authored
-DSL, canonical JSON, contract digests, and `tools/list` output remain unchanged
-when this optional section is absent.
+Freshness is a Runner deployment overlay in `synapsor.runner.json`. It adds no
+DSL clause and no canonical Spec field. Existing hand-authored DSL, canonical
+JSON, contract digests, and `tools/list` output remain unchanged when this
+optional section is absent.
 
 ```json
 {

package/docs/recipes.md

@@ -9,20 +9,20 @@ tenant key, conflict column, and business limits.
 List recipes:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner recipes list
+npx -y @synapsor/runner recipes list
 ```
 
 Inspect one:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner recipes show billing.late_fee_waiver
+npx -y @synapsor/runner recipes show billing.late_fee_waiver
 ```
 
 Initialize a starter config:
 
 ```bash
-npx -y -p @synapsor/runner synapsor-runner recipes init billing.late_fee_waiver --output synapsor.runner.json
-npx -y -p @synapsor/runner synapsor-runner config validate --config synapsor.runner.json
+npx -y @synapsor/runner recipes init billing.late_fee_waiver --output synapsor.runner.json
+npx -y @synapsor/runner config validate --config synapsor.runner.json
 ```
 
 Built-in recipes are JSON files under `recipes/`. They are starter data, not
@@ -31,8 +31,8 @@ domain, and initialize from your file:
 
 ```bash
 cp recipes/billing.late_fee_waiver.json my-recipe.json
-npx -y -p @synapsor/runner synapsor-runner recipes show ./my-recipe.json
-npx -y -p @synapsor/runner synapsor-runner recipes init ./my-recipe.json --output synapsor.runner.json
+npx -y @synapsor/runner recipes show ./my-recipe.json
+npx -y @synapsor/runner recipes init ./my-recipe.json --output synapsor.runner.json
 ```
 
 Available recipes: