@synapsor/runner 0.1.0-alpha.5 → 0.1.0-alpha.7

package/README.md

@@ -51,7 +51,7 @@ Run the guided quick demo first. It does not require Docker, a database, a
 config file, an MCP client, or a Synapsor Cloud account.
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor demo --quick
+npx -y -p @synapsor/runner@alpha synapsor-runner demo --quick
 ```
 
 In a terminal, it walks through the safety model step by step. In CI, piped
@@ -63,7 +63,7 @@ It does not prove database connectivity. It shows the proposal, evidence, and
 replay flow without giving the runner a database URL.
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor demo inspect
+npx -y -p @synapsor/runner@alpha synapsor-runner demo inspect
 ```
 
 Human output is concise by default. Use `--details` for reviewer metadata or
@@ -72,22 +72,22 @@ Human output is concise by default. Use `--details` for reviewer metadata or
 Useful quick-demo modes:
 
 ```bash
-synapsor demo --quick --guided
-synapsor demo --quick --no-interactive
-synapsor demo --quick --details
-synapsor demo inspect --npx
+synapsor-runner demo --quick --guided
+synapsor-runner demo --quick --no-interactive
+synapsor-runner demo --quick --details
+synapsor-runner demo inspect --npx
 ```
 
 Then choose one path:
 
 ```text
-Full disposable proof  -> npx -y -p @synapsor/runner@alpha synapsor demo
+Full disposable proof  -> npx -y -p @synapsor/runner@alpha synapsor-runner demo
 Your own staging DB    -> export DATABASE_URL=... then run the inspect command below
-MCP risk review        -> npx -y -p @synapsor/runner@alpha synapsor audit --example dangerous-db-mcp
+MCP risk review        -> npx -y -p @synapsor/runner@alpha synapsor-runner audit --example dangerous-db-mcp
 ```
 
-`synapsor` is the public command. `synapsor-runner` remains available as a
-backward-compatible alias.
+`synapsor-runner` is the public command for this OSS runner. `synapsor` is
+reserved for the Synapsor Cloud CLI.
 
 ## Connect Your Own Staging Database
 
@@ -104,7 +104,7 @@ staging or production-like databases, keep certificate verification enabled.
 Inspect metadata:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor inspect \
+npx -y -p @synapsor/runner@alpha synapsor-runner inspect \
   --engine auto \
   --from-env DATABASE_URL \
   --schema public
@@ -122,7 +122,7 @@ backend session env vars are trusted, which fields are visible, and what
 semantic capability name to expose.
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor init \
+npx -y -p @synapsor/runner@alpha synapsor-runner init \
   --wizard \
   --engine auto \
   --from-env DATABASE_URL \
@@ -133,11 +133,11 @@ npx -y -p @synapsor/runner@alpha synapsor init \
 Preview and serve the semantic tools:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor tools preview \
+npx -y -p @synapsor/runner@alpha synapsor-runner tools preview \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
 
-npx -y -p @synapsor/runner@alpha synapsor mcp serve \
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
 ```
@@ -151,7 +151,7 @@ long-running Runner process.
 Local MCP clients:
 
 ```bash
-synapsor mcp serve \
+synapsor-runner mcp serve \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
 ```
@@ -161,7 +161,7 @@ App/server deployments:
 ```bash
 export SYNAPSOR_RUNNER_HTTP_TOKEN="dev-local-token"
 
-synapsor mcp serve-http \
+synapsor-runner mcp serve-http \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --auth-token-env SYNAPSOR_RUNNER_HTTP_TOKEN
@@ -181,6 +181,27 @@ examples/openai-agents-http/
 Use `--mode review` only when you are ready to create proposal tools and test
 guarded writeback with a separate trusted write credential.
 
+## Sanity Check The Agent Connection
+
+Before asking an agent to solve a real task, confirm it can call a Runner tool:
+
+```bash
+synapsor-runner tools preview --config ./synapsor.runner.json --store ./.synapsor/local.db
+```
+
+Then ask the agent:
+
+```text
+Use the Synapsor Runner MCP tool to inspect invoice INV-3001.
+Do not answer from memory.
+Return the tool name called, the evidence handle, and whether raw SQL was available.
+```
+
+Expected result: the agent calls a semantic tool, returns an evidence handle or
+local ledger reference, and says raw SQL/write/approval tools were not
+available. If it gives generic advice or unrelated prose without a tool call,
+Runner is not connected yet.
+
 The disposable reference app includes proposal-first write examples for:
 
 - `billing.propose_late_fee_waiver`
@@ -246,7 +267,7 @@ proposal-first writes.
 Run the included MCP efficiency fixture:
 
 ```bash
-synapsor benchmark mcp-efficiency
+synapsor-runner benchmark mcp-efficiency
 ```
 
 Current fixture result for the late-fee-waiver workflow:
@@ -279,14 +300,14 @@ The runner stores a local SQLite evidence/replay ledger. Search it without
 relying on `latest`:
 
 ```bash
-synapsor activity search --tenant acme --object invoice:INV-3001
-synapsor proposals list --tenant acme --object invoice:INV-3001 --status approved
-synapsor evidence show ev_...
-synapsor query-audit list --evidence ev_...
-synapsor receipts list --proposal wrp_...
-synapsor receipts show <receipt_id>
-synapsor replay show --proposal wrp_...
-synapsor replay show --replay replay_wrp_...
+synapsor-runner activity search --tenant acme --object invoice:INV-3001
+synapsor-runner proposals list --tenant acme --object invoice:INV-3001 --status approved
+synapsor-runner evidence show ev_...
+synapsor-runner query-audit list --evidence ev_...
+synapsor-runner receipts list --proposal wrp_...
+synapsor-runner receipts show <receipt_id>
+synapsor-runner replay show --proposal wrp_...
+synapsor-runner replay show --replay replay_wrp_...
 ```
 
 Default inspection output is meant for first-run clarity. Add `--details` for
@@ -296,23 +317,23 @@ fingerprints, event timestamps, and receipt internals.
 Export captured evidence or proposal replay:
 
 ```bash
-synapsor evidence export ev_... --format markdown --output evidence.md
-synapsor replay export --proposal wrp_... --format json --output replay.json
-synapsor replay export --proposal wrp_... --format markdown --output replay.md
+synapsor-runner evidence export ev_... --format markdown --output evidence.md
+synapsor-runner replay export --proposal wrp_... --format json --output replay.json
+synapsor-runner replay export --proposal wrp_... --format markdown --output replay.md
 ```
 
 Create a redacted local diagnostic report:
 
 ```bash
-synapsor doctor --config synapsor.runner.json --report --redact --output synapsor-doctor.md
+synapsor-runner doctor --config synapsor.runner.json --report --redact --output synapsor-doctor.md
 ```
 
 Inspect or compact the local ledger:
 
 ```bash
-synapsor store stats --store ./.synapsor/local.db
-synapsor store vacuum --store ./.synapsor/local.db
-synapsor store prune --store ./.synapsor/local.db --older-than 30d --dry-run
+synapsor-runner store stats --store ./.synapsor/local.db
+synapsor-runner store vacuum --store ./.synapsor/local.db
+synapsor-runner store prune --store ./.synapsor/local.db --older-than 30d --dry-run
 ```
 
 This is local indexed search for local/dev/staging usage. It is not external
@@ -328,8 +349,8 @@ MCP, and the handler returns an applied/conflict/failed receipt for replay.
 
 ## Command Name
 
-This package installs `synapsor` as the primary binary and `synapsor-runner` as
-a backward-compatible alias.
+This package installs `synapsor-runner` as the OSS runner binary. The `synapsor`
+command is reserved for the Synapsor Cloud CLI.
 
 ## Scope
 

package/dist/runner.mjs

@@ -2685,7 +2685,7 @@ function createMcpRuntime(config, options = {}) {
 }
 function createSynapsorMcpServer(runtime) {
   const server = new McpServer(
-    { name: "synapsor-runner", version: "0.1.0-alpha.5" },
+    { name: "synapsor-runner", version: "0.1.0-alpha.7" },
     { capabilities: { tools: {}, resources: {} } }
   );
   if (runtime.config.mode === "cloud") {
@@ -5096,7 +5096,7 @@ import path2 from "node:path";
 async function startLocalUiServer(options = {}) {
   const host = options.host ?? "127.0.0.1";
   if (!isLocalHost(host) && options.allowRemoteBind !== true) {
-    throw new Error("synapsor ui binds to localhost by default. Use --allow-remote-bind only for an intentional trusted local-network demo.");
+    throw new Error("synapsor-runner ui binds to localhost by default. Use --allow-remote-bind only for an intentional trusted local-network demo.");
   }
   const configPath = path2.resolve(options.configPath ?? "synapsor.runner.json");
   const storePath = path2.resolve(options.storePath ?? "./.synapsor/local.db");
@@ -5678,7 +5678,7 @@ function shellQuote(value) {
   return /^[A-Za-z0-9_./:@=-]+$/.test(text) ? text : "'" + text.replace(/'/g, "'\\\\''") + "'";
 }
 function trustedApplyCommand(proposalId) {
-  return "synapsor apply " + shellQuote(proposalId) + " --config " + shellQuote(configPath) + " --store " + shellQuote(storePath);
+  return "synapsor-runner apply " + shellQuote(proposalId) + " --config " + shellQuote(configPath) + " --store " + shellQuote(storePath);
 }
 async function loadSummary() {
   const payload = await api("/api/summary");
@@ -5710,7 +5710,7 @@ async function loadProposals() {
   const payload = await api("/api/proposals");
   const root = byId("proposals"); root.replaceChildren(text("h2", "Proposals"));
   if (payload.proposals.length === 0) {
-    root.append(text("p", "No proposals in the local store yet. Run synapsor mcp serve and have an agent propose a change."));
+    root.append(text("p", "No proposals in the local store yet. Run synapsor-runner mcp serve and have an agent propose a change."));
     state.firstId = null;
     return;
   }
@@ -6059,10 +6059,10 @@ async function main(argv) {
     return 0;
   }
   if (!isKnownTopLevelCommand(command)) {
-    process2.stderr.write(`Unknown command: synapsor ${command}
+    process2.stderr.write(`Unknown command: ${cliCommandName()} ${command}
 
 Try:
-synapsor --help
+${cliCommandName()} --help
 `);
     return 2;
   }
@@ -6100,10 +6100,10 @@ synapsor --help
   if (command === "store") return storeCommand(rest);
   if (command === "shadow") return shadow(rest);
   if (command === "ui") return ui(rest);
-  process2.stderr.write(`Unknown command: synapsor ${command}
+  process2.stderr.write(`Unknown command: ${cliCommandName()} ${command}
 
 Try:
-synapsor --help
+${cliCommandName()} --help
 `);
   return 2;
 }
@@ -7977,7 +7977,7 @@ async function cloudConnect(args) {
     return 1;
   }
   const runnerId = String(parsed.cloud.runner_id || process2.env.SYNAPSOR_RUNNER_ID || "synapsor_runner_local").trim();
-  const runnerVersion = String(parsed.cloud.runner_version || process2.env.npm_package_version || "0.1.0-alpha.5").trim();
+  const runnerVersion = String(parsed.cloud.runner_version || process2.env.npm_package_version || "0.1.0-alpha.7").trim();
   const engines = normalizeEngines(parsed.cloud.engines);
   const capabilities = normalizeCapabilities(parsed.cloud.capabilities);
   const client = new ControlPlaneClient({
@@ -8164,7 +8164,7 @@ function formatQuickDemoDetails(seeded) {
     quickDemoStorePath,
     "",
     "If you ran this through one-off npx and did not install the package, prefix",
-    "follow-up commands with: npx -y -p @synapsor/runner@alpha synapsor",
+    "follow-up commands with: npx -y -p @synapsor/runner@alpha synapsor-runner",
     "",
     "Raw MCP shape:",
     "execute_sql(sql: string)",
@@ -8290,12 +8290,12 @@ function quickDemoGuidedScreens(seeded) {
       body: [
         "Run this next:",
         "",
-        "npx -y -p @synapsor/runner@alpha synapsor demo inspect",
+        "npx -y -p @synapsor/runner@alpha synapsor-runner demo inspect",
         "",
         "demo inspect shows the proposal, evidence, activity search, and replay commands.",
         "",
         "If installed globally, use:",
-        "synapsor demo inspect"
+        "synapsor-runner demo inspect"
       ]
     },
     {
@@ -8342,7 +8342,7 @@ async function waitForEnter(message, options) {
   }
 }
 function quickDemoInspectCommands(useNpx) {
-  const cmd = useNpx ? "npx -y -p @synapsor/runner@alpha synapsor" : cliCommandName();
+  const cmd = useNpx ? "npx -y -p @synapsor/runner@alpha synapsor-runner" : cliCommandName();
   return [
     {
       label: "Proposal summary",
@@ -11435,7 +11435,7 @@ function starterCloudConfig() {
       base_url_env: "SYNAPSOR_CLOUD_BASE_URL",
       runner_token_env: "SYNAPSOR_RUNNER_TOKEN",
       runner_id: "synapsor_runner_local",
-      runner_version: "0.1.0-alpha.5",
+      runner_version: "0.1.0-alpha.7",
       project_id: "token_scope",
       adapter_id: "mcp.your_adapter",
       source_id: "src_replace_me",
@@ -11491,8 +11491,7 @@ function isKnownTopLevelCommand(command) {
 }
 function cliCommandName() {
   if (process2.env.SYNAPSOR_RUNNER_COMMAND_NAME) return process2.env.SYNAPSOR_RUNNER_COMMAND_NAME;
-  const invoked = path3.basename(process2.argv[1] ?? "");
-  return invoked === "synapsor-runner" ? "synapsor-runner" : "synapsor";
+  return "synapsor-runner";
 }
 function usage(args = []) {
   const [command, subcommand] = args;

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

@@ -7,7 +7,7 @@ Do not start with your most sensitive production database. The current alpha
 runner is a local commit-safety runtime for reviewed single-row business
 actions, not a production certification.
 
-If you only ran `synapsor demo --quick`, you have tested the fixture-only
+If you only ran `synapsor-runner demo --quick`, you have tested the fixture-only
 teaching path and local ledger commands. This page is the real own-database
 path: it inspects your Postgres/MySQL metadata and generates reviewed semantic
 tools from your selections.
@@ -38,7 +38,7 @@ It does not print your database URL, put the URL in MCP client config, expose
 credentials.
 
 The rest of this page shows the same flow step by step using the public
-`synapsor ...` CLI. From a source checkout, use `./bin/synapsor ...` if the
+`synapsor-runner ...` CLI. From a source checkout, use `./bin/synapsor-runner ...` if the
 global binary is not linked yet.
 
 ## 1. Put the read URL in an environment variable
@@ -81,7 +81,7 @@ other trusted database TLS setup.
 ## 2. Inspect metadata
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor inspect \
+npx -y -p @synapsor/runner@alpha synapsor-runner inspect \
   --engine auto \
   --from-env DATABASE_URL \
   --schema public
@@ -90,13 +90,13 @@ npx -y -p @synapsor/runner@alpha synapsor inspect \
 For a disposable staging URL, this also works:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor inspect "$DATABASE_URL" --engine auto --schema public
+npx -y -p @synapsor/runner@alpha synapsor-runner inspect "$DATABASE_URL" --engine auto --schema public
 ```
 
 For automation:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor inspect \
+npx -y -p @synapsor/runner@alpha synapsor-runner inspect \
   --engine postgres \
   --from-env DATABASE_URL \
   --schema public \
@@ -113,9 +113,9 @@ to your staging table, primary key, tenant key, conflict column, visible fields,
 allowed write fields, and business limits.
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor recipes list
-npx -y -p @synapsor/runner@alpha synapsor recipes show billing.late_fee_waiver
-npx -y -p @synapsor/runner@alpha synapsor recipes init billing.late_fee_waiver --output synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor-runner recipes list
+npx -y -p @synapsor/runner@alpha synapsor-runner recipes show billing.late_fee_waiver
+npx -y -p @synapsor/runner@alpha synapsor-runner recipes init billing.late_fee_waiver --output synapsor.runner.json
 ```
 
 Use a recipe when the shape is close. Use the guided wizard or explicit flags
@@ -130,7 +130,7 @@ only the capabilities in your generated `synapsor.runner.json`.
 In an interactive terminal, run the guided wizard:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor init --from-env DATABASE_URL --mode read_only --wizard
+npx -y -p @synapsor/runner@alpha synapsor-runner init --from-env DATABASE_URL --mode read_only --wizard
 ```
 
 The generated context and capabilities are based on your selections. Synapsor
@@ -174,7 +174,7 @@ If you already know the reviewed table/action, generate config directly from
 metadata and explicit flags:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor init \
+npx -y -p @synapsor/runner@alpha synapsor-runner init \
   --from-env DATABASE_URL \
   --engine postgres \
   --schema public \
@@ -193,7 +193,7 @@ npx -y -p @synapsor/runner@alpha synapsor init \
 Or generate from a saved inspection snapshot without reconnecting:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor init \
+npx -y -p @synapsor/runner@alpha synapsor-runner init \
   --inspection-json schema-inspection.json \
   --table invoices \
   --namespace billing \
@@ -261,7 +261,7 @@ contain database URLs or passwords.
 ## 6. Generate runner files
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor init \
+npx -y -p @synapsor/runner@alpha synapsor-runner init \
   --spec onboarding-selection.json \
   --non-interactive
 ```
@@ -281,10 +281,10 @@ files.
 Generate or refresh MCP client snippets later with:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor mcp config generic --config ./synapsor.runner.json --store ./.synapsor/local.db
-npx -y -p @synapsor/runner@alpha synapsor mcp config claude-desktop --config ./synapsor.runner.json --store ./.synapsor/local.db
-npx -y -p @synapsor/runner@alpha synapsor mcp config cursor --config ./synapsor.runner.json --store ./.synapsor/local.db
-npx -y -p @synapsor/runner@alpha synapsor tools preview --config ./synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp config generic --config ./synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp config claude-desktop --config ./synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp config cursor --config ./synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner tools preview --config ./synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 The snippets contain the local command and args. They must not contain database
@@ -293,8 +293,8 @@ URLs, passwords, approval tools, commit tools, or write credentials.
 ## 7. Validate the config
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor config validate --config synapsor.runner.json
-npx -y -p @synapsor/runner@alpha synapsor config show --config synapsor.runner.json --redacted
+npx -y -p @synapsor/runner@alpha synapsor-runner config validate --config synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor-runner config show --config synapsor.runner.json --redacted
 ```
 
 The config stores environment-variable names, not connection-string values.
@@ -302,7 +302,7 @@ The config stores environment-variable names, not connection-string values.
 Run doctor after setting the referenced environment variables:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor doctor --config synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor-runner doctor --config synapsor.runner.json
 ```
 
 Doctor validates config shape, trusted context env vars, source env vars,
@@ -310,7 +310,7 @@ read/write credential separation, table/column metadata when the read URL is
 available, and the semantic MCP tool boundary. Use JSON for automation:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor doctor --config synapsor.runner.json --json
+npx -y -p @synapsor/runner@alpha synapsor-runner doctor --config synapsor.runner.json --json
 ```
 
 ## 8. Serve semantic MCP tools
@@ -320,7 +320,7 @@ Use stdio when a local MCP client can launch Synapsor Runner:
 ```bash
 export SYNAPSOR_TENANT_ID="acme"
 export SYNAPSOR_PRINCIPAL="local_operator"
-npx -y -p @synapsor/runner@alpha synapsor mcp serve --config ./synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve --config ./synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 Use HTTP when an app/server agent connects to a long-running Runner process:
@@ -330,7 +330,7 @@ export SYNAPSOR_TENANT_ID="acme"
 export SYNAPSOR_PRINCIPAL="local_operator"
 export SYNAPSOR_RUNNER_HTTP_TOKEN="dev-local-token"
 
-npx -y -p @synapsor/runner@alpha synapsor mcp serve-http \
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve-http \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --auth-token-env SYNAPSOR_RUNNER_HTTP_TOKEN
@@ -357,10 +357,10 @@ tools, commit tools, database URLs, write credentials, or tenant authority.
 Proposal tools leave the source database unchanged. Review locally:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor proposals list --store ./.synapsor/local.db
-npx -y -p @synapsor/runner@alpha synapsor proposals show wrp_123 --store ./.synapsor/local.db
-npx -y -p @synapsor/runner@alpha synapsor proposals approve wrp_123 --store ./.synapsor/local.db --actor local_reviewer --yes
-npx -y -p @synapsor/runner@alpha synapsor proposals writeback-job wrp_123 --store ./.synapsor/local.db --output job.json
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals list --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals show wrp_123 --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals approve wrp_123 --store ./.synapsor/local.db --actor local_reviewer --yes
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals writeback-job wrp_123 --store ./.synapsor/local.db --output job.json
 ```
 
 Apply through the trusted worker path with a separate writer credential:
@@ -369,7 +369,7 @@ Apply through the trusted worker path with a separate writer credential:
 export SYNAPSOR_DATABASE_WRITE_URL="<postgres-or-mysql-write-url>"
 SYNAPSOR_ENGINE=postgres \
 SYNAPSOR_DATABASE_URL="$SYNAPSOR_DATABASE_WRITE_URL" \
-npx -y -p @synapsor/runner@alpha synapsor apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 If your application/API should own the business write, use an `http_handler`
@@ -378,7 +378,7 @@ from environment variables, and the handler receives a structured proposal/job
 payload, not arbitrary model SQL:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor apply --proposal wrp_123 --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner apply --proposal wrp_123 --config synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 See [Writeback Executors](writeback-executors.md).
@@ -386,8 +386,8 @@ See [Writeback Executors](writeback-executors.md).
 Replay afterward:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor replay show wrp_123 --store ./.synapsor/local.db
-npx -y -p @synapsor/runner@alpha synapsor replay export wrp_123 --store ./.synapsor/local.db --output replay.json
+npx -y -p @synapsor/runner@alpha synapsor-runner replay show wrp_123 --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner replay export wrp_123 --store ./.synapsor/local.db --output replay.json
 ```
 
 ## Boundary

package/docs/http-mcp.md

@@ -11,7 +11,7 @@ local agent tool can launch Synapsor Runner directly.
 ```bash
 export SYNAPSOR_RUNNER_HTTP_TOKEN="dev-local-token"
 
-synapsor mcp serve-http \
+synapsor-runner mcp serve-http \
   --host 127.0.0.1 \
   --port 8765 \
   --config ./synapsor.runner.json \
@@ -134,7 +134,7 @@ CORS is disabled by default. If a local browser app needs access during
 development, allow one explicit origin:
 
 ```bash
-synapsor mcp serve-http \
+synapsor-runner mcp serve-http \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --cors-origin http://localhost:3000
@@ -149,7 +149,7 @@ Synapsor Runner binds to `127.0.0.1` by default.
 If you explicitly bind to all interfaces:
 
 ```bash
-synapsor mcp serve-http --host 0.0.0.0
+synapsor-runner mcp serve-http --host 0.0.0.0
 ```
 
 the CLI prints a warning. Treat this as a production-like service:

package/docs/local-mode.md

@@ -6,15 +6,15 @@ Command model:
 
 - `./scripts/demo-docker.sh` runs the no-install Docker demo.
 - `synapsor <command>` is the public CLI surface.
-- From a source checkout, use `./bin/synapsor <command>` if the global binary is
+- From a source checkout, use `./bin/synapsor-runner <command>` if the global binary is
   not linked yet.
 
-`synapsor demo --quick` creates a fixture ledger for learning and CLI
+`synapsor-runner demo --quick` creates a fixture ledger for learning and CLI
 verification. In a terminal it walks through the safety model step by step; in
 CI or piped output it prints a short summary and exits without waiting for
 Enter. It does not read or write external Postgres/MySQL. Local mode with
-`synapsor mcp serve`, `synapsor demo`, or an own generated config is the real
-Postgres/MySQL path. Use `synapsor demo inspect` to print the follow-up
+`synapsor-runner mcp serve`, `synapsor-runner demo`, or an own generated config is the real
+Postgres/MySQL path. Use `synapsor-runner demo inspect` to print the follow-up
 commands for the quick-demo fixture.
 
 Current local-mode foundation:
@@ -22,8 +22,8 @@ Current local-mode foundation:
 - strict JSON capability config validation in `packages/config`;
 - local SQLite proposal/event/evidence/query-audit/writeback/replay store in `packages/proposal-store`;
 - local proposal review CLI in `apps/runner`;
-- local localhost proposal review UI through `synapsor ui`;
-- static MCP database risk review with `synapsor audit`;
+- local localhost proposal review UI through `synapsor-runner ui`;
+- static MCP database risk review with `synapsor-runner audit`;
 - local stdio MCP server with semantic read/proposal tools;
 - authenticated HTTP MCP server for app/server agents;
 - MCP resource reads for `synapsor://proposals/*`, `synapsor://evidence/*`, and `synapsor://replay/*`;
@@ -43,13 +43,13 @@ want to change your host Node version.
 Create a starter config without putting credentials in the file:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor init --engine postgres --mode review
+npx -y -p @synapsor/runner@alpha synapsor-runner init --engine postgres --mode review
 ```
 
 For MySQL:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor init --engine mysql --mode review --output synapsor.mysql.runner.json
+npx -y -p @synapsor/runner@alpha 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.
@@ -62,8 +62,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@alpha synapsor init --spec onboarding-selection.json --non-interactive
-npx -y -p @synapsor/runner@alpha synapsor doctor --config synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor-runner init --spec onboarding-selection.json --non-interactive
+npx -y -p @synapsor/runner@alpha synapsor-runner doctor --config synapsor.runner.json
 ```
 
 `doctor --config` checks config validation, required environment variables,
@@ -75,7 +75,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@alpha synapsor mcp serve \
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
 ```
@@ -85,7 +85,7 @@ Use HTTP when your app/server agent connects to a long-running Runner process:
 ```bash
 export SYNAPSOR_RUNNER_HTTP_TOKEN="dev-local-token"
 
-npx -y -p @synapsor/runner@alpha synapsor mcp serve-http \
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve-http \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --auth-token-env SYNAPSOR_RUNNER_HTTP_TOKEN
@@ -125,19 +125,19 @@ If neither is set, the CLI uses:
 List proposals:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor proposals list --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals list --store ./.synapsor/local.db
 ```
 
 Show a proposal:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor proposals show wrp_123 --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals show wrp_123 --store ./.synapsor/local.db
 ```
 
 Approve:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor proposals approve wrp_123 \
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals approve wrp_123 \
   --store ./.synapsor/local.db \
   --actor local_reviewer \
   --yes
@@ -148,7 +148,7 @@ Before approval, the CLI prints the reviewer-critical proposal details: trusted
 Create a guarded writeback job from an approved proposal:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor proposals writeback-job wrp_123 \
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals writeback-job wrp_123 \
   --store ./.synapsor/local.db \
   --project local \
   --runner local_runner \
@@ -160,7 +160,7 @@ The generated job uses the public `synapsor.writeback-job.v1` protocol and can b
 ```bash
 SYNAPSOR_ENGINE=postgres \
 SYNAPSOR_DATABASE_URL="postgresql://writer:<password>@localhost:5432/app" \
-npx -y -p @synapsor/runner@alpha synapsor apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 Passing `--store` records the terminal `synapsor.execution-receipt.v1` locally. Replay then links the proposal, approval, writeback job, applied/conflict/failed receipt, evidence, and query audit.
@@ -168,7 +168,7 @@ Passing `--store` records the terminal `synapsor.execution-receipt.v1` locally.
 Reject:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor proposals reject wrp_123 \
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals reject wrp_123 \
   --store ./.synapsor/local.db \
   --reason "policy evidence is incomplete" \
   --yes
@@ -185,7 +185,7 @@ Shadow-mode proposals are inspectable through `proposals show` and `replay show`
 Start a localhost-only review UI:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor ui --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner ui --config synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 The UI shows setup summary, semantic tools, proposal states, exact diffs,
@@ -201,20 +201,20 @@ tools, MCP commit tools, or controls that widen configured tables/columns.
 Show replay:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor replay show wrp_123 --store ./.synapsor/local.db
-npx -y -p @synapsor/runner@alpha synapsor replay show --proposal wrp_123 --store ./.synapsor/local.db
-npx -y -p @synapsor/runner@alpha synapsor replay show --replay replay_wrp_123 --store ./.synapsor/local.db
-npx -y -p @synapsor/runner@alpha synapsor replay show --evidence ev_123 --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner replay show wrp_123 --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner replay show --proposal wrp_123 --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner replay show --replay replay_wrp_123 --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner replay show --evidence ev_123 --store ./.synapsor/local.db
 ```
 
 Export replay:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor replay export wrp_123 \
+npx -y -p @synapsor/runner@alpha synapsor-runner replay export wrp_123 \
   --store ./.synapsor/local.db \
   --output replay.json
 
-npx -y -p @synapsor/runner@alpha synapsor replay export --proposal wrp_123 \
+npx -y -p @synapsor/runner@alpha synapsor-runner replay export --proposal wrp_123 \
   --format markdown \
   --store ./.synapsor/local.db \
   --output replay.md
@@ -229,22 +229,22 @@ Human output is concise by default. Use `--details` for reviewer metadata or
 The local SQLite store is also searchable without relying on `latest`:
 
 ```bash
-synapsor activity search \
+synapsor-runner activity search \
   --tenant acme \
   --object invoice:INV-3001 \
   --store ./.synapsor/local.db
 
-synapsor evidence list \
+synapsor-runner evidence list \
   --tenant acme \
   --capability billing.inspect_invoice \
   --source app_postgres \
   --table invoices \
   --store ./.synapsor/local.db
 
-synapsor evidence show ev_123 --store ./.synapsor/local.db
-synapsor query-audit list --evidence ev_123 --store ./.synapsor/local.db
-synapsor receipts list --proposal wrp_123 --store ./.synapsor/local.db
-synapsor receipts show <receipt_id> --store ./.synapsor/local.db
+synapsor-runner evidence show ev_123 --store ./.synapsor/local.db
+synapsor-runner query-audit list --evidence ev_123 --store ./.synapsor/local.db
+synapsor-runner receipts list --proposal wrp_123 --store ./.synapsor/local.db
+synapsor-runner receipts show <receipt_id> --store ./.synapsor/local.db
 ```
 
 Default inspection output is intentionally short. Add `--details` when you need
@@ -266,10 +266,10 @@ The local ledger is a developer/staging SQLite file. You can inspect, compact,
 or prune it without touching your source Postgres/MySQL database:
 
 ```bash
-synapsor store stats --store ./.synapsor/local.db
-synapsor store vacuum --store ./.synapsor/local.db
-synapsor store prune --store ./.synapsor/local.db --older-than 30d --dry-run
-synapsor store prune --store ./.synapsor/local.db --older-than 30d --yes
+synapsor-runner store stats --store ./.synapsor/local.db
+synapsor-runner store vacuum --store ./.synapsor/local.db
+synapsor-runner store prune --store ./.synapsor/local.db --older-than 30d --dry-run
+synapsor-runner store prune --store ./.synapsor/local.db --older-than 30d --yes
 ```
 
 `store prune` defaults to dry-run. Use `--yes` only after reviewing the row
@@ -322,7 +322,7 @@ For CI or direct verification, use:
 corepack pnpm test:mcp-local
 ```
 
-It launches the official MCP stdio client transport against `synapsor mcp serve`, exercises the Postgres billing, Postgres support, and MySQL orders examples, checks that source rows are unchanged before approval, approves locally, generates versioned writeback jobs, applies them, retries idempotently, and then proves stale-row conflict:
+It launches the official MCP stdio client transport against `synapsor-runner mcp serve`, exercises the Postgres billing, Postgres support, and MySQL orders examples, checks that source rows are unchanged before approval, approves locally, generates versioned writeback jobs, applies them, retries idempotently, and then proves stale-row conflict:
 
 ```text
 The business state changed after the agent saw it, so Synapsor refused to commit.

package/docs/mcp-audit.md

@@ -1,11 +1,11 @@
 # MCP database risk review
 
-`npx -y -p @synapsor/runner@alpha synapsor audit <target>` performs a
+`npx -y -p @synapsor/runner@alpha 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.
 
-From a source checkout, use `./bin/synapsor ...` if the global binary is not
+From a source checkout, use `./bin/synapsor-runner ...` if the global binary is not
 linked yet.
 
 It does not call business tools. It only inspects names, descriptions, input schemas, output schemas, annotations, and examples when those are present.
@@ -23,7 +23,7 @@ MCP annotations are treated as hints, not enforcement.
 Built-in database MCP risk example:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor audit --example dangerous-db-mcp
+npx -y -p @synapsor/runner@alpha synapsor-runner audit --example dangerous-db-mcp
 ```
 
 This bundled example does not require a source checkout or local examples file.
@@ -34,45 +34,45 @@ table/column inputs, and model-controlled tenant/principal fields.
 Human-readable output:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor audit ./tools-list.json
+npx -y -p @synapsor/runner@alpha synapsor-runner audit ./tools-list.json
 ```
 
 Remote `tools/list` endpoint with a bearer token kept in the environment:
 
 ```bash
 SYNAPSOR_MCP_AUDIT_BEARER="..." \
-npx -y -p @synapsor/runner@alpha synapsor audit https://mcp.example.com --format json
+npx -y -p @synapsor/runner@alpha synapsor-runner audit https://mcp.example.com --format json
 ```
 
 Remote endpoint with a custom bearer-token environment variable:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor audit https://mcp.example.com --bearer-env MCP_AUDIT_TOKEN --format json
+npx -y -p @synapsor/runner@alpha synapsor-runner audit https://mcp.example.com --bearer-env MCP_AUDIT_TOKEN --format json
 ```
 
 Stdio MCP server:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor audit 'stdio:node ./server.mjs' --timeout-ms 5000
+npx -y -p @synapsor/runner@alpha synapsor-runner audit 'stdio:node ./server.mjs' --timeout-ms 5000
 ```
 
 JSON output:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor audit ./tools-list.json --format json
+npx -y -p @synapsor/runner@alpha synapsor-runner audit ./tools-list.json --format json
 ```
 
 Markdown output for issues, PRs, or security review notes:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor audit --example dangerous-db-mcp --format markdown
+npx -y -p @synapsor/runner@alpha synapsor-runner audit --example dangerous-db-mcp --format markdown
 ```
 
 During local development, the repo-local wrapper can run the same command:
 
 ```bash
-./bin/synapsor audit ./tools-list.json
-./bin/synapsor audit ./tools-list.json --format json
+./bin/synapsor-runner audit ./tools-list.json
+./bin/synapsor-runner audit ./tools-list.json --format json
 ```
 
 ## Supported inputs

package/docs/mcp-client-setup.md

@@ -12,7 +12,7 @@ app/server deployments where your agent connects to a long-running Runner
 service.
 
 Command examples use the published alpha package through `npx`. From a source
-checkout, use `./bin/synapsor ...` only when you intentionally want the local
+checkout, use `./bin/synapsor-runner ...` only when you intentionally want the local
 source wrapper.
 
 Checked examples live in:
@@ -31,8 +31,8 @@ corepack pnpm test:mcp-client-configs
 
 | Mode | Use when | Command |
 | --- | --- | --- |
-| stdio | Claude Desktop, Cursor, VS Code, or another local MCP client can launch Synapsor Runner | `synapsor mcp serve` |
-| HTTP | Your app/server, Python agent, Node service, or container connects to a long-running Runner service | `synapsor mcp serve-http` |
+| stdio | Claude Desktop, Cursor, VS Code, or another local MCP client can launch Synapsor Runner | `synapsor-runner mcp serve` |
+| HTTP | Your app/server, Python agent, Node service, or container connects to a long-running Runner service | `synapsor-runner mcp serve-http` |
 
 Stdio keeps the MCP protocol on process stdin/stdout and is the simplest local
 developer path. HTTP uses JSON-RPC over an authenticated `/mcp` endpoint and is
@@ -43,7 +43,7 @@ HTTP requires bearer auth by default:
 ```bash
 export SYNAPSOR_RUNNER_HTTP_TOKEN="dev-local-token"
 
-npx -y -p @synapsor/runner@alpha synapsor mcp serve-http \
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve-http \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --auth-token-env SYNAPSOR_RUNNER_HTTP_TOKEN
@@ -57,7 +57,7 @@ Use private networking/TLS before exposing HTTP MCP beyond localhost. Details:
 Print a snippet without modifying any client files:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor mcp config claude-desktop \
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp config claude-desktop \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
 ```
@@ -75,13 +75,13 @@ vscode
 The older form is still supported:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor mcp configure --client claude-desktop --config ./synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha 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@alpha synapsor mcp configure \
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp configure \
   --client cursor \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
@@ -100,7 +100,7 @@ database URLs or passwords into the client config.
 From the runner repository:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor mcp serve --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 For the alpha package, keep the package tag explicit in client configuration.
@@ -110,7 +110,7 @@ For app/server HTTP mode:
 ```bash
 export SYNAPSOR_RUNNER_HTTP_TOKEN="dev-local-token"
 
-npx -y -p @synapsor/runner@alpha synapsor mcp serve-http \
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve-http \
   --config ./examples/mcp-postgres-billing/synapsor.runner.json \
   --store ./.synapsor/local.db \
   --auth-token-env SYNAPSOR_RUNNER_HTTP_TOKEN
@@ -121,13 +121,13 @@ npx -y -p @synapsor/runner@alpha synapsor mcp serve-http \
 ```json
 {
   "mcpServers": {
-    "synapsor": {
+    "synapsor-runner": {
       "command": "npx",
       "args": [
         "-y",
         "-p",
         "@synapsor/runner@alpha",
-        "synapsor",
+        "synapsor-runner",
         "mcp",
         "serve",
         "--config",
@@ -161,6 +161,39 @@ approve_proposal
 commit_proposal
 ```
 
+## Sanity Check The Agent Connection
+
+After installing the MCP client snippet, restart the client and run a deliberately
+small tool-call test.
+
+First confirm what Runner exposes:
+
+```bash
+npx -y -p @synapsor/runner@alpha synapsor-runner tools preview \
+  --config ./synapsor.runner.json \
+  --store ./.synapsor/local.db
+```
+
+Then ask the MCP client:
+
+```text
+Use the Synapsor Runner MCP tool to inspect invoice INV-3001.
+Do not answer from memory.
+Return the tool name called, the evidence handle, and whether raw SQL was available.
+```
+
+Expected result:
+
+- the client calls a tool such as `billing.inspect_invoice`;
+- the response includes an evidence handle or local ledger reference;
+- the model reports that raw SQL, write credentials, approval tools, and commit
+  tools were not available.
+
+If the answer is generic prose or unrelated task planning with no tool call and
+no evidence handle, Synapsor Runner is not connected to that agent session yet.
+Check the MCP config path, restart the client, set trusted context env vars, and
+run `tools/list` or `synapsor-runner tools preview` again.
+
 ## Claude Desktop / Cursor / VS Code
 
 Use the matching checked-in example as the starting point:
@@ -187,8 +220,8 @@ Before documenting a client UI as officially tested, verify:
 ## Troubleshooting
 
 - Server not listed: check the command path, working directory, and config path.
-- Tool schema mismatch: run `synapsor audit <exported-tools.json>`.
+- Tool schema mismatch: run `synapsor-runner audit <exported-tools.json>`.
 - Missing trusted context: set `SYNAPSOR_TENANT_ID` and `SYNAPSOR_PRINCIPAL`, or use the environment variables configured in `trusted_context.values`.
 - Database unavailable: verify the read credential and host access.
-- Proposal waiting review: approve outside the model with `synapsor proposals approve`.
+- Proposal waiting review: approve outside the model with `synapsor-runner proposals approve`.
 - Stale-row conflict: inspect replay; the source row changed after the proposal was created, so the guarded worker refused to commit.

package/docs/recipes.md

@@ -9,20 +9,20 @@ tenant key, conflict column, and business limits.
 List recipes:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor recipes list
+npx -y -p @synapsor/runner@alpha synapsor-runner recipes list
 ```
 
 Inspect one:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor recipes show billing.late_fee_waiver
+npx -y -p @synapsor/runner@alpha synapsor-runner recipes show billing.late_fee_waiver
 ```
 
 Initialize a starter config:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor recipes init billing.late_fee_waiver --output synapsor.runner.json
-npx -y -p @synapsor/runner@alpha synapsor config validate --config synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor-runner recipes init billing.late_fee_waiver --output synapsor.runner.json
+npx -y -p @synapsor/runner@alpha 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@alpha synapsor recipes show ./my-recipe.json
-npx -y -p @synapsor/runner@alpha synapsor recipes init ./my-recipe.json --output synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor-runner recipes show ./my-recipe.json
+npx -y -p @synapsor/runner@alpha synapsor-runner recipes init ./my-recipe.json --output synapsor.runner.json
 ```
 
 Available recipes:

package/docs/security-boundary.md

@@ -76,7 +76,7 @@ database identifiers such as `../private`, `id/../../tenant_id`, or
 `status; DROP TABLE tickets` before adapter execution. Local CLI file paths
 remain explicit user-provided paths; they are not model-facing authority.
 
-Local review can happen through the CLI or `synapsor ui`. The UI is a localhost
+Local review can happen through the CLI or `synapsor-runner ui`. The UI is a localhost
 review surface with a per-run session token and CSRF protection for
 approve/reject actions. It does not expose raw SQL, database URLs, write
 credentials, approval tools, commit tools, or controls that widen reviewed

package/docs/troubleshooting-first-run.md

@@ -3,13 +3,13 @@
 Run the friendly doctor first:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor doctor --first-run
+npx -y -p @synapsor/runner@alpha synapsor-runner doctor --first-run
 ```
 
 Use JSON for automation:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor doctor --first-run --json
+npx -y -p @synapsor/runner@alpha synapsor-runner doctor --first-run --json
 ```
 
 ## Docker Missing
@@ -128,13 +128,13 @@ Own-database MCP setup needs a reviewed config before serving tools.
 Fix:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor init --from-env DATABASE_URL --mode review --wizard
+npx -y -p @synapsor/runner@alpha synapsor-runner init --from-env DATABASE_URL --mode review --wizard
 ```
 
 Or pass an example config:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor tools preview --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner tools preview --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 ## SQLite Store Missing
@@ -180,7 +180,7 @@ Fix:
 
 ```bash
 export SYNAPSOR_DATABASE_READ_URL="<read-only-url>"
-npx -y -p @synapsor/runner@alpha synapsor doctor --config synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor-runner doctor --config synapsor.runner.json
 ```
 
 ## Read/Write Credential Split Failed
@@ -216,7 +216,7 @@ Fix:
 Regenerate the snippet:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor mcp config claude-desktop \
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp config claude-desktop \
   --absolute-paths \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db

package/docs/writeback-executors.md

@@ -59,7 +59,7 @@ literal values.
 Run after approval:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor apply \
+npx -y -p @synapsor/runner@alpha synapsor-runner apply \
   --proposal wrp_123 \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db

package/examples/openai-agents-http/README.md

@@ -22,7 +22,7 @@ export SYNAPSOR_TENANT_ID="acme"
 export SYNAPSOR_PRINCIPAL="openai_agent_demo"
 export SYNAPSOR_RUNNER_HTTP_TOKEN="dev-token"
 
-npx -y -p @synapsor/runner@alpha synapsor mcp serve-http \
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve-http \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
   --auth-token-env SYNAPSOR_RUNNER_HTTP_TOKEN

package/examples/openai-agents-stdio/README.md

@@ -13,13 +13,13 @@ commit tools.
 Generate `synapsor.runner.json` first:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor demo
+npx -y -p @synapsor/runner@alpha synapsor-runner demo
 ```
 
 or connect your own staging database:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor init --wizard --from-env DATABASE_URL --mode read_only
+npx -y -p @synapsor/runner@alpha synapsor-runner init --wizard --from-env DATABASE_URL --mode read_only
 ```
 
 Then install the Python dependencies:

package/examples/reference-support-billing-app/README.md

@@ -36,14 +36,14 @@ examples/reference-support-billing-app/scripts/run-demo.sh
 Validate the reviewed contract:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor config validate --config examples/reference-support-billing-app/synapsor.runner.json
-npx -y -p @synapsor/runner@alpha synapsor doctor --config examples/reference-support-billing-app/synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor-runner config validate --config examples/reference-support-billing-app/synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor-runner doctor --config examples/reference-support-billing-app/synapsor.runner.json
 ```
 
 Serve MCP:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor mcp serve \
+npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve \
   --config examples/reference-support-billing-app/synapsor.runner.json \
   --store ./tmp/reference-support-billing/local.db
 ```
@@ -65,15 +65,15 @@ The model does not receive approval tools, commit tools, write credentials, raw
 
 ## Safe Write Examples
 
-After `synapsor demo` or after starting this fixture manually, try the same
+After `synapsor-runner demo` or after starting this fixture manually, try the same
 proposal-first loop without connecting an MCP client:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor propose billing.propose_late_fee_waiver --sample
-npx -y -p @synapsor/runner@alpha synapsor proposals show latest
-npx -y -p @synapsor/runner@alpha synapsor proposals approve latest --yes
-npx -y -p @synapsor/runner@alpha synapsor apply latest
-npx -y -p @synapsor/runner@alpha synapsor replay latest
+npx -y -p @synapsor/runner@alpha synapsor-runner propose billing.propose_late_fee_waiver --sample
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals show latest
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals approve latest --yes
+npx -y -p @synapsor/runner@alpha synapsor-runner apply latest
+npx -y -p @synapsor/runner@alpha synapsor-runner replay latest
 ```
 
 Expected safety output:
@@ -93,8 +93,8 @@ Guarded writeback applied.
 Other proposal examples use the same review/apply/replay path:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor propose support.propose_plan_credit --sample
-npx -y -p @synapsor/runner@alpha synapsor propose orders.propose_status_change --sample
+npx -y -p @synapsor/runner@alpha synapsor-runner propose support.propose_plan_credit --sample
+npx -y -p @synapsor/runner@alpha synapsor-runner propose orders.propose_status_change --sample
 ```
 
 Safety guarantees:
@@ -115,17 +115,17 @@ or production-scale runner orchestration.
 After a proposal exists:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor proposals list --store ./tmp/reference-support-billing/local.db
-npx -y -p @synapsor/runner@alpha synapsor proposals approve <proposal_id> --store ./tmp/reference-support-billing/local.db --actor local_reviewer --yes
-npx -y -p @synapsor/runner@alpha synapsor proposals writeback-job <proposal_id> --store ./tmp/reference-support-billing/local.db --output ./tmp/reference-support-billing/job.json
-npx -y -p @synapsor/runner@alpha synapsor apply --job ./tmp/reference-support-billing/job.json --store ./tmp/reference-support-billing/local.db
-npx -y -p @synapsor/runner@alpha synapsor replay export <proposal_id> --store ./tmp/reference-support-billing/local.db --output ./tmp/reference-support-billing/replay.json
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals list --store ./tmp/reference-support-billing/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals approve <proposal_id> --store ./tmp/reference-support-billing/local.db --actor local_reviewer --yes
+npx -y -p @synapsor/runner@alpha synapsor-runner proposals writeback-job <proposal_id> --store ./tmp/reference-support-billing/local.db --output ./tmp/reference-support-billing/job.json
+npx -y -p @synapsor/runner@alpha synapsor-runner apply --job ./tmp/reference-support-billing/job.json --store ./tmp/reference-support-billing/local.db
+npx -y -p @synapsor/runner@alpha synapsor-runner replay export <proposal_id> --store ./tmp/reference-support-billing/local.db --output ./tmp/reference-support-billing/replay.json
 ```
 
 To inspect locally in a browser:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor ui \
+npx -y -p @synapsor/runner@alpha synapsor-runner ui \
   --config examples/reference-support-billing-app/synapsor.runner.json \
   --store ./tmp/reference-support-billing/local.db
 ```

package/package.json

@@ -1,11 +1,10 @@
 {
   "name": "@synapsor/runner",
-  "version": "0.1.0-alpha.5",
+  "version": "0.1.0-alpha.7",
   "description": "Commit-safe MCP runner for Postgres and MySQL agents",
   "license": "Apache-2.0",
   "type": "module",
   "bin": {
-    "synapsor": "dist/cli.js",
     "synapsor-runner": "dist/cli.js"
   },
   "files": [