@synapsor/runner 0.1.0-alpha.2 → 0.1.0-alpha.3

package/README.md

@@ -10,12 +10,16 @@ or commit tools.
 ## Run The Alpha
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner --help
+npx -y -p @synapsor/runner@alpha synapsor --help
+npx -y -p @synapsor/runner@alpha synapsor demo --quick
+npx -y -p @synapsor/runner@alpha synapsor audit --example dangerous-db-mcp
 ```
 
-The already-published alpha may expose only `synapsor-runner`. This package now
-also exposes `synapsor` as the primary command, with `synapsor-runner` kept as a
-backward-compatible alias.
+`synapsor` is the public command. `synapsor-runner` remains available as a
+backward-compatible alias for earlier alpha commands.
+
+`synapsor demo --quick` is fixture-only and does not require Docker. Use
+`synapsor demo` for the disposable local Postgres-backed demo.
 
 Use it with a local or staging database:
 

package/dist/cli.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":";AAiBA,OAAO,EAOL,KAAK,gBAAgB,EAEtB,MAAM,mCAAmC,CAAC;AAiC3C,wBAAsB,IAAI,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,MAAM,CAAC,CAqC1D;AA0DD,KAAK,SAAS,GAAG,CAAC,QAAQ,EAAE,MAAM,EAAE,YAAY,CAAC,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;AAE9E,wBAAsB,aAAa,CACjC,IAAI,EAAE,MAAM,EAAE,EACd,OAAO,GAAE;IACP,GAAG,CAAC,EAAE,SAAS,CAAC;IAChB,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,CAAC;IACxB,UAAU,CAAC,EAAE,gBAAgB,CAAC;IAC9B,MAAM,CAAC,EAAE,IAAI,CAAC,MAAM,CAAC,WAAW,EAAE,OAAO,CAAC,CAAC;CACvC,GACL,OAAO,CAAC,MAAM,CAAC,CA0KjB"}
+{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":";AAiBA,OAAO,EAOL,KAAK,gBAAgB,EAEtB,MAAM,mCAAmC,CAAC;AA0H3C,wBAAsB,IAAI,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,MAAM,CAAC,CAqC1D;AA0DD,KAAK,SAAS,GAAG,CAAC,QAAQ,EAAE,MAAM,EAAE,YAAY,CAAC,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;AAE9E,wBAAsB,aAAa,CACjC,IAAI,EAAE,MAAM,EAAE,EACd,OAAO,GAAE;IACP,GAAG,CAAC,EAAE,SAAS,CAAC;IAChB,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,CAAC;IACxB,UAAU,CAAC,EAAE,gBAAgB,CAAC;IAC9B,MAAM,CAAC,EAAE,IAAI,CAAC,MAAM,CAAC,WAAW,EAAE,OAAO,CAAC,CAAC;CACvC,GACL,OAAO,CAAC,MAAM,CAAC,CA0KjB"}

package/dist/runner.mjs

@@ -2158,7 +2158,7 @@ function createMcpRuntime(config, options = {}) {
 }
 function createSynapsorMcpServer(runtime) {
   const server = new McpServer(
-    { name: "synapsor-runner", version: "0.1.0-alpha.2" },
+    { name: "synapsor-runner", version: "0.1.0-alpha.3" },
     { capabilities: { tools: {}, resources: {} } }
   );
   if (runtime.config.mode === "cloud") {
@@ -5162,6 +5162,94 @@ function stringOrDefault(value, fallback) {
 // apps/runner/src/cli.ts
 var adapters = { postgres: postgresAdapter, mysql: mysqlAdapter };
 var handlerReceiptStatuses = /* @__PURE__ */ new Set(["applied", "already_applied", "conflict", "failed"]);
+var dangerousDatabaseMcpAuditExample = {
+  tools: [
+    {
+      name: "execute_sql",
+      description: "Execute arbitrary SQL against the application database.",
+      inputSchema: {
+        type: "object",
+        properties: {
+          sql: { type: "string" }
+        },
+        required: ["sql"]
+      }
+    },
+    {
+      name: "run_query",
+      description: "Run any query and return database rows.",
+      inputSchema: {
+        type: "object",
+        properties: {
+          query: { type: "string" },
+          table: { type: "string" },
+          columns: {
+            type: "array",
+            items: { type: "string" }
+          }
+        },
+        required: ["query"]
+      }
+    },
+    {
+      name: "approve_refund",
+      description: "Approve and issue a customer refund immediately.",
+      inputSchema: {
+        type: "object",
+        properties: {
+          refund_id: { type: "string" },
+          tenant_id: { type: "string" },
+          amount_cents: { type: "number" }
+        },
+        required: ["refund_id", "tenant_id", "amount_cents"]
+      }
+    },
+    {
+      name: "update_customer",
+      description: "Update a customer record directly.",
+      inputSchema: {
+        type: "object",
+        properties: {
+          customer_id: { type: "string" },
+          tenant_id: { type: "string" },
+          column: { type: "string" },
+          value: { type: "string" }
+        },
+        required: ["customer_id", "tenant_id", "column", "value"]
+      }
+    },
+    {
+      name: "delete_order",
+      description: "Delete an order from the database.",
+      inputSchema: {
+        type: "object",
+        properties: {
+          order_id: { type: "string" },
+          tenant_id: { type: "string" }
+        },
+        required: ["order_id", "tenant_id"]
+      }
+    },
+    {
+      name: "query_database",
+      description: "Query arbitrary tables and columns from the database.",
+      inputSchema: {
+        type: "object",
+        properties: {
+          database: { type: "string" },
+          schema: { type: "string" },
+          table: { type: "string" },
+          columns: {
+            type: "array",
+            items: { type: "string" }
+          },
+          where: { type: "string" }
+        },
+        required: ["table"]
+      }
+    }
+  ]
+};
 var defaultConfigPath = "synapsor.runner.json";
 var defaultStorePath = "./.synapsor/local.db";
 var referenceDemoDir = "examples/reference-support-billing-app";
@@ -6912,7 +7000,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.2").trim();
+  const runnerVersion = String(parsed.cloud.runner_version || process2.env.npm_package_version || "0.1.0-alpha.3").trim();
   const engines = normalizeEngines(parsed.cloud.engines);
   const capabilities = normalizeCapabilities(parsed.cloud.capabilities);
   const client = new ControlPlaneClient({
@@ -7047,7 +7135,7 @@ async function quickDemo() {
     "",
     "Next:",
     `${cliCommandName()} demo`,
-    `${cliCommandName()} audit <your-mcp-tools.json>`,
+    `${cliCommandName()} audit --example dangerous-db-mcp`,
     ""
   ].join("\n"));
   return 0;
@@ -7065,12 +7153,13 @@ async function mcpServe(args) {
 }
 async function mcpAudit(args) {
   const json = args.includes("--json");
-  const target2 = firstPositional(args);
+  const example = optionalArg(args, "--example");
+  const target2 = example ? `example:${example}` : firstPositional(args);
   if (!target2) {
-    throw new Error("mcp audit requires <target>");
+    throw new Error("mcp audit requires <target> or --example dangerous-db-mcp");
   }
   const timeoutMs = Number(optionalArg(args, "--timeout-ms") ?? "5000");
-  const payload = await readMcpAuditTarget(target2, args, timeoutMs);
+  const payload = example ? builtInMcpAuditExample(example) : await readMcpAuditTarget(target2, args, timeoutMs);
   const report = auditMcpManifest(payload, { target: target2 });
   process2.stdout.write(json ? `${JSON.stringify(report, null, 2)}
 ` : formatMcpAuditReport(report));
@@ -7106,8 +7195,9 @@ async function audit(args) {
   const url = optionalArg(args, "--url");
   const stdio = optionalArg(args, "--stdio");
   const mcpConfig2 = optionalArg(args, "--mcp-config");
-  const target2 = url ?? (stdio ? `stdio:${stdio}` : mcpConfig2 ?? firstPositional(args));
-  if (!target2) throw new Error("audit requires <target>, --mcp-config <path>, --stdio <command>, or --url <url>");
+  const example = optionalArg(args, "--example");
+  const target2 = example ? `example:${example}` : url ?? (stdio ? `stdio:${stdio}` : mcpConfig2 ?? firstPositional(args));
+  if (!target2) throw new Error("audit requires <target>, --example dangerous-db-mcp, --mcp-config <path>, --stdio <command>, or --url <url>");
   const forwarded = args.filter((arg, index) => {
     const previous = args[index - 1];
     return !["--url", "--stdio", "--mcp-config"].includes(arg) && !["--url", "--stdio", "--mcp-config"].includes(previous ?? "");
@@ -7723,6 +7813,10 @@ async function readMcpAuditTarget(target2, args, timeoutMs) {
   }
   return parsed;
 }
+function builtInMcpAuditExample(example) {
+  if (example === "dangerous-db-mcp") return dangerousDatabaseMcpAuditExample;
+  throw new Error(`unknown audit example: ${example}. Available examples: dangerous-db-mcp`);
+}
 function isRunnerConfigLike(value) {
   return isRecord6(value) && value.version === 1 && Array.isArray(value.capabilities);
 }
@@ -8326,6 +8420,7 @@ function firstPositional(args) {
     "--database-url-env",
     "--destination",
     "--engine",
+    "--example",
     "--from",
     "--from-env",
     "--host",
@@ -8601,7 +8696,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.2",
+      runner_version: "0.1.0-alpha.3",
       project_id: "token_scope",
       adapter_id: "mcp.your_adapter",
       source_id: "src_replace_me",
@@ -8675,6 +8770,7 @@ Generate a reviewed Synapsor Runner contract. Defaults to read-only in the wizar
     mcp: `Usage:
   ${cmd} mcp serve --config ./synapsor.runner.json --store ./.synapsor/local.db
   ${cmd} mcp config --absolute-paths --config ./synapsor.runner.json --store ./.synapsor/local.db
+  ${cmd} mcp audit --example dangerous-db-mcp
   ${cmd} mcp audit ./tools-list.json
 
 MCP clients see semantic tools. They do not receive raw SQL, write credentials, approval tools, or commit tools.
@@ -8697,6 +8793,7 @@ Print MCP client configuration that references the local runner command, not dat
 Create the same evidence-backed proposal the MCP tool would create. The source database is not mutated.
 `,
     audit: `Usage:
+  ${cmd} audit --example dangerous-db-mcp
   ${cmd} audit ./synapsor.runner.json
   ${cmd} audit --mcp-config ./claude_desktop_config.json
   ${cmd} audit --stdio "node ./server.js"

package/docs/cloud-mode.md

@@ -53,7 +53,7 @@ Cloud mode uses the same MCP server command with a `mode: "cloud"` config:
     "base_url_env": "SYNAPSOR_CLOUD_BASE_URL",
     "runner_token_env": "SYNAPSOR_RUNNER_TOKEN",
     "runner_id": "synapsor_runner_local",
-    "runner_version": "0.1.0-alpha.2",
+    "runner_version": "0.1.0-alpha.3",
     "project_id": "token_scope",
     "adapter_id": "mcp.your_adapter",
     "source_id": "src_replace_me",
@@ -71,7 +71,7 @@ Run:
 ```bash
 SYNAPSOR_CLOUD_BASE_URL="https://api.synapsor.ai" \
 SYNAPSOR_RUNNER_TOKEN="syn_wbr_..." \
-npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve --config ./synapsor.cloud.json
+npx -y -p @synapsor/runner@alpha synapsor mcp serve --config ./synapsor.cloud.json
 ```
 
 Validate the Cloud runner token and source scope before serving tools:
@@ -79,7 +79,7 @@ Validate the Cloud runner token and source scope before serving tools:
 ```bash
 SYNAPSOR_CLOUD_BASE_URL="https://api.synapsor.ai" \
 SYNAPSOR_RUNNER_TOKEN="syn_wbr_..." \
-npx -y -p @synapsor/runner@alpha synapsor-runner cloud connect --config ./synapsor.cloud.json
+npx -y -p @synapsor/runner@alpha synapsor cloud connect --config ./synapsor.cloud.json
 ```
 
 `cloud connect` verifies the runner token, registers the runner id/version, sends engine/capability/source metadata, and posts an initial heartbeat. It does not send Postgres/MySQL URLs, passwords, write credentials, prompts, or table data. The `project_id` field may be the literal `token_scope` because Synapsor Cloud validates the real project/source from the scoped runner token.

package/docs/config-migrations.md

@@ -29,7 +29,7 @@ validation.
 Because version 1 is the only supported schema today, migration is conservative:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner config migrate --config synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor config migrate --config synapsor.runner.json
 ```
 
 prints that the config is already current and writes nothing.
@@ -37,7 +37,7 @@ prints that the config is already current and writes nothing.
 To write a normalized copy:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner config migrate \
+npx -y -p @synapsor/runner@alpha synapsor config migrate \
   --config synapsor.runner.json \
   --output migrated.json \
   --yes
@@ -47,7 +47,7 @@ To rewrite in place, the command requires an explicit write and creates a
 timestamped backup:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner config migrate \
+npx -y -p @synapsor/runner@alpha synapsor config migrate \
   --config synapsor.runner.json \
   --write \
   --yes

package/docs/demo-transcript.md

@@ -41,18 +41,18 @@ The model did not get:
 Next:
 
 1. Open proposal UI:
-   npx -y -p @synapsor/runner@alpha synapsor-runner ui --tour --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
+   npx -y -p @synapsor/runner@alpha synapsor ui --tour --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
 
 2. Run the reference app:
    corepack pnpm demo:reference
 
 3. Generate MCP client config:
-   npx -y -p @synapsor/runner@alpha synapsor-runner mcp config --absolute-paths --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
+   npx -y -p @synapsor/runner@alpha synapsor mcp config --absolute-paths --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
 
 4. Use your own staging Postgres/MySQL:
    export DATABASE_URL='<postgres-or-mysql-read-url>'
-   npx -y -p @synapsor/runner@alpha synapsor-runner inspect --from-env DATABASE_URL
-   npx -y -p @synapsor/runner@alpha synapsor-runner init --wizard --from-env DATABASE_URL
+   npx -y -p @synapsor/runner@alpha synapsor inspect --from-env DATABASE_URL
+   npx -y -p @synapsor/runner@alpha synapsor init --wizard --from-env DATABASE_URL
 ```
 
 The full log should include the lower-level proof:

package/docs/first-10-minutes.md

@@ -70,7 +70,7 @@ authority.
 ## Next Command 1: Open The Local UI
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner ui --tour \
+npx -y -p @synapsor/runner@alpha synapsor ui --tour \
   --config ./examples/mcp-postgres-billing/synapsor.runner.json \
   --store ./.synapsor/local.db
 ```
@@ -97,7 +97,7 @@ The reference app uses a disposable support/billing Postgres database and proves
 ## Next Command 3: Generate MCP Client Config
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner mcp config claude-desktop \
+npx -y -p @synapsor/runner@alpha synapsor mcp config claude-desktop \
   --absolute-paths \
   --config ./examples/mcp-postgres-billing/synapsor.runner.json \
   --store ./.synapsor/local.db
@@ -110,7 +110,7 @@ tools, commit tools, or write credentials.
 Verify the configured tool boundary with:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner tools preview \
+npx -y -p @synapsor/runner@alpha synapsor tools preview \
   --config ./examples/mcp-postgres-billing/synapsor.runner.json \
   --store ./.synapsor/local.db
 ```

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

@@ -76,7 +76,7 @@ other trusted database TLS setup.
 ## 2. Inspect metadata
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner inspect \
+npx -y -p @synapsor/runner@alpha synapsor inspect \
   --engine auto \
   --from-env DATABASE_URL \
   --schema public
@@ -85,13 +85,13 @@ npx -y -p @synapsor/runner@alpha synapsor-runner inspect \
 For a disposable staging URL, this also works:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner inspect "$DATABASE_URL" --engine auto --schema public
+npx -y -p @synapsor/runner@alpha synapsor inspect "$DATABASE_URL" --engine auto --schema public
 ```
 
 For automation:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner inspect \
+npx -y -p @synapsor/runner@alpha synapsor inspect \
   --engine postgres \
   --from-env DATABASE_URL \
   --schema public \
@@ -108,9 +108,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-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
+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
 ```
 
 Use a recipe when the shape is close. Use the guided wizard or explicit flags
@@ -125,7 +125,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-runner init --from-env DATABASE_URL --mode read_only --wizard
+npx -y -p @synapsor/runner@alpha synapsor init --from-env DATABASE_URL --mode read_only --wizard
 ```
 
 The generated capabilities are based on your selections. Synapsor Runner does
@@ -161,7 +161,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-runner init \
+npx -y -p @synapsor/runner@alpha synapsor init \
   --from-env DATABASE_URL \
   --engine postgres \
   --schema public \
@@ -180,7 +180,7 @@ npx -y -p @synapsor/runner@alpha synapsor-runner init \
 Or generate from a saved inspection snapshot without reconnecting:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner init \
+npx -y -p @synapsor/runner@alpha synapsor init \
   --inspection-json schema-inspection.json \
   --table invoices \
   --namespace billing \
@@ -248,7 +248,7 @@ contain database URLs or passwords.
 ## 6. Generate runner files
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner init \
+npx -y -p @synapsor/runner@alpha synapsor init \
   --spec onboarding-selection.json \
   --non-interactive
 ```
@@ -268,10 +268,10 @@ files.
 Generate or refresh MCP client snippets later with:
 
 ```bash
-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
+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
 ```
 
 The snippets contain the local command and args. They must not contain database
@@ -280,8 +280,8 @@ URLs, passwords, approval tools, commit tools, or write credentials.
 ## 7. Validate the config
 
 ```bash
-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
+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
 ```
 
 The config stores environment-variable names, not connection-string values.
@@ -289,7 +289,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-runner doctor --config synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor doctor --config synapsor.runner.json
 ```
 
 Doctor validates config shape, trusted context env vars, source env vars,
@@ -297,7 +297,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-runner doctor --config synapsor.runner.json --json
+npx -y -p @synapsor/runner@alpha synapsor doctor --config synapsor.runner.json --json
 ```
 
 ## 8. Serve semantic MCP tools
@@ -305,7 +305,7 @@ npx -y -p @synapsor/runner@alpha synapsor-runner doctor --config synapsor.runner
 ```bash
 export SYNAPSOR_TENANT_ID="acme"
 export SYNAPSOR_PRINCIPAL="local_operator"
-npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve --config ./synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor mcp serve --config ./synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 The model-facing MCP server exposes semantic tools such as:
@@ -325,10 +325,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-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
+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
 ```
 
 Apply through the trusted worker path with a separate writer credential:
@@ -337,7 +337,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-runner apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor 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`
@@ -346,7 +346,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-runner apply --proposal wrp_123 --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor apply --proposal wrp_123 --config synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 See `docs/writeback-executors.md`.
@@ -354,8 +354,8 @@ See `docs/writeback-executors.md`.
 Replay afterward:
 
 ```bash
-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
+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
 ```
 
 ## Boundary

package/docs/local-mode.md

@@ -30,13 +30,13 @@ Still pending:
 Create a starter config without putting credentials in the file:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner init --engine postgres --mode review
+npx -y -p @synapsor/runner@alpha synapsor init --engine postgres --mode review
 ```
 
 For MySQL:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner init --engine mysql --mode review --output synapsor.mysql.runner.json
+npx -y -p @synapsor/runner@alpha synapsor 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.
@@ -49,8 +49,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-runner init --spec onboarding-selection.json --non-interactive
-npx -y -p @synapsor/runner@alpha synapsor-runner doctor --config synapsor.runner.json
+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
 ```
 
 `doctor --config` checks config validation, required environment variables,
@@ -87,19 +87,19 @@ If neither is set, the CLI uses:
 List proposals:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner proposals list --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor proposals list --store ./.synapsor/local.db
 ```
 
 Show a proposal:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner proposals show wrp_123 --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor proposals show wrp_123 --store ./.synapsor/local.db
 ```
 
 Approve:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner proposals approve wrp_123 \
+npx -y -p @synapsor/runner@alpha synapsor proposals approve wrp_123 \
   --store ./.synapsor/local.db \
   --actor local_reviewer \
   --yes
@@ -110,7 +110,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-runner proposals writeback-job wrp_123 \
+npx -y -p @synapsor/runner@alpha synapsor proposals writeback-job wrp_123 \
   --store ./.synapsor/local.db \
   --project local \
   --runner local_runner \
@@ -122,7 +122,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-runner apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor 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.
@@ -130,7 +130,7 @@ Passing `--store` records the terminal `synapsor.execution-receipt.v1` locally.
 Reject:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner proposals reject wrp_123 \
+npx -y -p @synapsor/runner@alpha synapsor proposals reject wrp_123 \
   --store ./.synapsor/local.db \
   --reason "policy evidence is incomplete" \
   --yes
@@ -147,7 +147,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-runner ui --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor ui --config synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 The UI shows setup summary, semantic tools, proposal states, exact diffs,
@@ -163,13 +163,13 @@ tools, MCP commit tools, or controls that widen configured tables/columns.
 Show replay:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner replay show wrp_123 --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor replay show wrp_123 --store ./.synapsor/local.db
 ```
 
 Export replay:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner replay export wrp_123 \
+npx -y -p @synapsor/runner@alpha synapsor replay export wrp_123 \
   --store ./.synapsor/local.db \
   --output replay.json
 ```

package/docs/local-ui.md

@@ -7,7 +7,7 @@ From a source checkout, use `./bin/synapsor ui ...` if the global binary is not
 linked yet.
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner ui --config ./synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor ui --config ./synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 By default it binds to localhost only and prints a per-run URL:
@@ -135,7 +135,7 @@ For normal use, do not bind the UI to anything except localhost.
 For a deliberate trusted local-network demo:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner ui --host 0.0.0.0 --allow-remote-bind
+npx -y -p @synapsor/runner@alpha synapsor ui --host 0.0.0.0 --allow-remote-bind
 ```
 
 Do this only in an isolated environment. The local UI is not a hosted
@@ -156,8 +156,8 @@ The UI is intentionally small in the current alpha:
 Use the CLI apply path after approval:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner proposals writeback-job wrp_123 --store ./.synapsor/local.db --output job.json
+npx -y -p @synapsor/runner@alpha synapsor proposals writeback-job wrp_123 --store ./.synapsor/local.db --output job.json
 SYNAPSOR_ENGINE=postgres \
 SYNAPSOR_DATABASE_URL="$SYNAPSOR_DATABASE_WRITE_URL" \
-npx -y -p @synapsor/runner@alpha synapsor-runner apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
 ```

package/docs/mcp-audit.md

@@ -1,6 +1,6 @@
 # MCP database risk review
 
-`npx -y -p @synapsor/runner@alpha synapsor-runner audit <target>` performs a
+`npx -y -p @synapsor/runner@alpha synapsor 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.
@@ -20,35 +20,46 @@ MCP annotations are treated as hints, not enforcement.
 
 ## Usage
 
+Built-in database MCP risk example:
+
+```bash
+npx -y -p @synapsor/runner@alpha synapsor audit --example dangerous-db-mcp
+```
+
+This bundled example does not require a source checkout or local examples file.
+It audits a deliberately risky database MCP shape with `execute_sql`,
+`run_query`, model-callable approval/update/delete tools, arbitrary
+table/column inputs, and model-controlled tenant/principal fields.
+
 Human-readable output:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner audit ./tools-list.json
+npx -y -p @synapsor/runner@alpha synapsor 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-runner audit https://mcp.example.com --json
+npx -y -p @synapsor/runner@alpha synapsor audit https://mcp.example.com --json
 ```
 
 Remote endpoint with a custom bearer-token environment variable:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner audit https://mcp.example.com --bearer-env MCP_AUDIT_TOKEN --json
+npx -y -p @synapsor/runner@alpha synapsor audit https://mcp.example.com --bearer-env MCP_AUDIT_TOKEN --json
 ```
 
 Stdio MCP server:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner audit 'stdio:node ./server.mjs' --timeout-ms 5000
+npx -y -p @synapsor/runner@alpha synapsor audit 'stdio:node ./server.mjs' --timeout-ms 5000
 ```
 
 JSON output:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner audit ./tools-list.json --json
+npx -y -p @synapsor/runner@alpha synapsor audit ./tools-list.json --json
 ```
 
 During local development, the repo-local wrapper can run the same command:

package/docs/mcp-client-setup.md

@@ -29,7 +29,7 @@ corepack pnpm test:mcp-client-configs
 Print a snippet without modifying any client files:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner mcp config claude-desktop \
+npx -y -p @synapsor/runner@alpha synapsor mcp config claude-desktop \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
 ```
@@ -47,13 +47,13 @@ vscode
 The older form is still supported:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner mcp configure --client claude-desktop --config ./synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor 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-runner mcp configure \
+npx -y -p @synapsor/runner@alpha synapsor mcp configure \
   --client cursor \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db \
@@ -72,7 +72,7 @@ database URLs or passwords into the client config.
 From the runner repository:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor 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.
@@ -82,13 +82,13 @@ For the alpha package, keep the package tag explicit in client configuration.
 ```json
 {
   "mcpServers": {
-    "synapsor-runner": {
+    "synapsor": {
       "command": "npx",
       "args": [
         "-y",
         "-p",
         "@synapsor/runner@alpha",
-        "synapsor-runner",
+        "synapsor",
         "mcp",
         "serve",
         "--config",

package/docs/mcp-efficiency-benchmark.md

@@ -7,13 +7,13 @@ The global `synapsor` command is only needed after installing or linking the
 CLI.
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner benchmark mcp-efficiency
+npx -y -p @synapsor/runner@alpha synapsor benchmark mcp-efficiency
 ```
 
 For machine-readable output:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner benchmark mcp-efficiency --json
+npx -y -p @synapsor/runner@alpha synapsor benchmark mcp-efficiency --json
 ```
 
 The benchmark compares an included fixture, not universal model behavior.

package/docs/operations.md

@@ -12,9 +12,9 @@
 ## Routine checks
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner doctor
-npx -y -p @synapsor/runner@alpha synapsor-runner validate --job examples/postgres-support/job.approved.json
-npx -y -p @synapsor/runner@alpha synapsor-runner validate --job examples/mysql-orders/job.approved.json
+npx -y -p @synapsor/runner@alpha synapsor doctor
+npx -y -p @synapsor/runner@alpha synapsor validate --job examples/postgres-support/job.approved.json
+npx -y -p @synapsor/runner@alpha synapsor validate --job examples/mysql-orders/job.approved.json
 ```
 
 `doctor` validates local configuration, calls Synapsor's runner-token doctor endpoint, confirms the token is authenticated for the configured source, checks database reachability and engine version, creates/verifies `synapsor_writeback_receipts`, and performs a rollback-only receipt insert to prove the configured credential can write runner receipts. It does not mutate business tables.

package/docs/own-db-20-minutes.md

@@ -32,7 +32,7 @@ That command runs inspection, guided config generation, and tool preview. The
 rest of this page shows the same steps explicitly.
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner inspect --from-env DATABASE_URL --engine auto
+npx -y -p @synapsor/runner@alpha synapsor inspect --from-env DATABASE_URL --engine auto
 ```
 
 This prints discovered tables/views, primary keys, possible tenant/scope
@@ -43,7 +43,7 @@ write credentials to the model.
 For disposable staging databases, this shorter form also works:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner inspect "$DATABASE_URL" --engine auto
+npx -y -p @synapsor/runner@alpha synapsor inspect "$DATABASE_URL" --engine auto
 ```
 
 Prefer `--from-env` on shared machines so URLs do not land in shell history.
@@ -51,7 +51,7 @@ Prefer `--from-env` on shared machines so URLs do not land in shell history.
 ## 3. Run The Guided Wizard
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner init --from-env DATABASE_URL --mode review --wizard
+npx -y -p @synapsor/runner@alpha synapsor init --from-env DATABASE_URL --mode review --wizard
 ```
 
 The wizard asks for:
@@ -100,9 +100,9 @@ The generated config stores environment-variable names, not database secrets.
 ## 5. Preview What The Model Sees
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner config validate --config synapsor.runner.json
-npx -y -p @synapsor/runner@alpha synapsor-runner doctor --config synapsor.runner.json
-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 config validate --config synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor doctor --config synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor tools preview --config synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 `doctor` checks config shape, trusted context env vars, source env vars,
@@ -124,7 +124,7 @@ vars, and the semantic MCP tool boundary.
 export SYNAPSOR_TENANT_ID="acme"
 export SYNAPSOR_PRINCIPAL="local_operator"
 
-npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve \
+npx -y -p @synapsor/runner@alpha synapsor mcp serve \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db
 ```
@@ -138,15 +138,15 @@ model-controlled tenant authority.
 If a proposal is created:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner proposals list --store ./.synapsor/local.db
-npx -y -p @synapsor/runner@alpha synapsor-runner proposals show <proposal_id> --store ./.synapsor/local.db
-npx -y -p @synapsor/runner@alpha synapsor-runner replay show <proposal_id> --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor proposals list --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor proposals show <proposal_id> --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor replay show <proposal_id> --store ./.synapsor/local.db
 ```
 
 Open the UI:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner ui --tour --config ./synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor ui --tour --config ./synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 ## 8. Apply Only After Review
@@ -160,12 +160,12 @@ export SYNAPSOR_DATABASE_WRITE_URL="<postgres-or-mysql-writer-url>"
 Then:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner proposals approve <proposal_id> --store ./.synapsor/local.db --actor local_reviewer --yes
-npx -y -p @synapsor/runner@alpha synapsor-runner proposals writeback-job <proposal_id> --store ./.synapsor/local.db --output job.json
+npx -y -p @synapsor/runner@alpha synapsor proposals approve <proposal_id> --store ./.synapsor/local.db --actor local_reviewer --yes
+npx -y -p @synapsor/runner@alpha synapsor proposals writeback-job <proposal_id> --store ./.synapsor/local.db --output job.json
 
 SYNAPSOR_ENGINE=postgres \
 SYNAPSOR_DATABASE_URL="$SYNAPSOR_DATABASE_WRITE_URL" \
-npx -y -p @synapsor/runner@alpha synapsor-runner apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor apply --job job.json --config synapsor.runner.json --store ./.synapsor/local.db
 ```
 
 If your application should own the business write, configure an `http_handler`

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-runner recipes list
+npx -y -p @synapsor/runner@alpha synapsor recipes list
 ```
 
 Inspect one:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner recipes show billing.late_fee_waiver
+npx -y -p @synapsor/runner@alpha synapsor recipes show billing.late_fee_waiver
 ```
 
 Initialize a starter config:
 
 ```bash
-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
+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
 ```
 
 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-runner recipes show ./my-recipe.json
-npx -y -p @synapsor/runner@alpha synapsor-runner recipes init ./my-recipe.json --output synapsor.runner.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
 ```
 
 Available recipes:

package/docs/schema-inspection.md

@@ -7,7 +7,7 @@ Use the public `synapsor ...` runner CLI. From a source checkout, use
 `./bin/synapsor ...` if the global binary is not linked yet.
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner inspect \
+npx -y -p @synapsor/runner@alpha synapsor inspect \
   --engine auto \
   --from-env SYNAPSOR_DATABASE_READ_URL \
   --schema public
@@ -16,7 +16,7 @@ npx -y -p @synapsor/runner@alpha synapsor-runner inspect \
 JSON output:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner inspect \
+npx -y -p @synapsor/runner@alpha synapsor inspect \
   --engine mysql \
   --from-env SYNAPSOR_DATABASE_READ_URL \
   --schema app \
@@ -84,5 +84,5 @@ Binary/blob/vector columns are excluded from generated default visible columns.
 Use the inspection result to create `onboarding-selection.json`, then run:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner init --spec onboarding-selection.json --non-interactive
+npx -y -p @synapsor/runner@alpha synapsor init --spec onboarding-selection.json --non-interactive
 ```

package/docs/shadow-mode.md

@@ -17,7 +17,7 @@ Run a shadow config:
 List shadow proposals:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner shadow list --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor shadow list --store ./.synapsor/local.db
 ```
 
 Record the human action:
@@ -30,7 +30,7 @@ cat > human-action.json <<'JSON'
 }
 JSON
 
-npx -y -p @synapsor/runner@alpha synapsor-runner shadow record-human-action wrp_123 \
+npx -y -p @synapsor/runner@alpha synapsor shadow record-human-action wrp_123 \
   --store ./.synapsor/local.db \
   --patch human-action.json \
   --actor human_operator \
@@ -40,13 +40,13 @@ npx -y -p @synapsor/runner@alpha synapsor-runner shadow record-human-action wrp_
 Compare:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner shadow compare wrp_123 --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor shadow compare wrp_123 --store ./.synapsor/local.db
 ```
 
 Report:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner shadow report --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor shadow report --store ./.synapsor/local.db
 ```
 
 The report counts:

package/docs/troubleshooting-first-run.md

@@ -3,13 +3,13 @@
 Run the friendly doctor first:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner doctor --first-run
+npx -y -p @synapsor/runner@alpha synapsor doctor --first-run
 ```
 
 Use JSON for automation:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner doctor --first-run --json
+npx -y -p @synapsor/runner@alpha synapsor 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-runner init --from-env DATABASE_URL --mode review --wizard
+npx -y -p @synapsor/runner@alpha synapsor init --from-env DATABASE_URL --mode review --wizard
 ```
 
 Or pass an example config:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner tools preview --config ./examples/mcp-postgres-billing/synapsor.runner.json --store ./.synapsor/local.db
+npx -y -p @synapsor/runner@alpha synapsor 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-runner doctor --config synapsor.runner.json
+npx -y -p @synapsor/runner@alpha synapsor 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-runner mcp config claude-desktop \
+npx -y -p @synapsor/runner@alpha synapsor 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-runner apply \
+npx -y -p @synapsor/runner@alpha synapsor apply \
   --proposal wrp_123 \
   --config ./synapsor.runner.json \
   --store ./.synapsor/local.db

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-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
+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
 ```
 
 Serve MCP:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner mcp serve \
+npx -y -p @synapsor/runner@alpha synapsor mcp serve \
   --config examples/reference-support-billing-app/synapsor.runner.json \
   --store ./tmp/reference-support-billing/local.db
 ```
@@ -64,17 +64,17 @@ The model does not receive approval tools, commit tools, write credentials, raw
 After a proposal exists:
 
 ```bash
-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
+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
 ```
 
 To inspect locally in a browser:
 
 ```bash
-npx -y -p @synapsor/runner@alpha synapsor-runner ui \
+npx -y -p @synapsor/runner@alpha synapsor ui \
   --config examples/reference-support-billing-app/synapsor.runner.json \
   --store ./tmp/reference-support-billing/local.db
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synapsor/runner",
-  "version": "0.1.0-alpha.2",
+  "version": "0.1.0-alpha.3",
   "description": "Commit-safe MCP runner for Postgres and MySQL agents",
   "license": "Apache-2.0",
   "type": "module",