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

package/docs/local-mode.md

@@ -23,20 +23,28 @@ Current local-mode foundation:
 
 Still pending:
 
-- Public-release hardening around the experimental `node:sqlite` dependency.
+The alpha package requires Node >= 22.5.0 because the local evidence/replay
+ledger uses Node's `node:sqlite` runtime. The published package declares that
+engine requirement and the CLI exits early with a clear message on older Node
+versions. The Docker-backed demo remains the recommended path when you do not
+want to change your host Node version.
+
+Commands in this page that use local ledger search/export or `synapsor store`
+require this checkout or package version `0.1.0-alpha.4` or newer while npm
+`@alpha` still points to an older alpha.
 
 ## Initialize a config
 
 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 +57,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 +95,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 +118,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 +130,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 +138,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 +155,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,19 +171,74 @@ 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
+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
 ```
 
 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
+
+npx -y -p @synapsor/runner@alpha synapsor replay export --proposal wrp_123 \
+  --format markdown \
+  --store ./.synapsor/local.db \
+  --output replay.md
 ```
 
 Replay records include proposal metadata, before/after diff, events, writeback receipts, evidence summaries, and query audit rows currently stored for the proposal.
 
+## Local evidence, query audit, and receipts
+
+The local SQLite store is also searchable without relying on `latest`:
+
+```bash
+synapsor activity search \
+  --tenant acme \
+  --object invoice:INV-3001 \
+  --store ./.synapsor/local.db
+
+synapsor 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
+```
+
+Read-only MCP tools record evidence bundles and query-audit rows and return an
+evidence handle. Use `evidence show`, `evidence list`, and `query-audit list`
+to inspect those captured rows and fingerprints later without rerunning the
+external database read.
+
+This is local indexed search over the runner's SQLite ledger. It is not
+external Postgres/MySQL time travel, not native branching, and not a hosted
+cross-runner audit ledger.
+
+## Local store maintenance
+
+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
+```
+
+`store prune` defaults to dry-run. Use `--yes` only after reviewing the row
+counts it will remove.
+
 ## Boundary
 
 Local mode does not expose `approve_proposal` or `commit_proposal` as model-callable MCP tools. The intended flow is:
@@ -184,7 +247,7 @@ Local mode does not expose `approve_proposal` or `commit_proposal` as model-call
 MCP tool call
   -> reviewed semantic proposal
   -> local store
-  -> human/policy approval outside the model
+  -> human/operator approval outside the model
   -> guarded worker writeback
   -> terminal receipt
   -> replay

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,42 +20,63 @@ 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
+```
+
+Markdown output requires this checkout or package version `0.1.0-alpha.4` or
+newer. Check `npm view @synapsor/runner@alpha version` before promoting npm
+snippets publicly.
+
+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 --format 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 --format 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 --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
 ```
 
 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 --json
+./bin/synapsor audit ./tools-list.json --format json
 ```
 
 ## Supported inputs

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/open-source-feature-inventory.md

@@ -0,0 +1,254 @@
+# Synapsor Runner Open-Source Feature Inventory
+
+Date: 2026-06-23
+
+Branch inspected: `runner-segment-scale-adoption`
+
+This inventory tracks the open-source runner boundary. It is not a list of
+Synapsor Cloud or Synapsor DBMS features.
+
+## Summary
+
+Synapsor Runner now has a local evidence/replay ledger for real
+Postgres/MySQL-backed MCP interactions:
+
+- config-defined semantic MCP tools instead of raw SQL;
+- trusted tenant/principal context binding;
+- scoped source reads;
+- local evidence bundles and query audit;
+- proposal-first writes with before/proposed diffs;
+- local approval/rejection outside MCP;
+- guarded single-row writeback;
+- writeback receipts;
+- proposal replay;
+- local indexed search over proposals, evidence, query audit, receipts, and
+  replay links.
+- npm/package trust checks for the public `synapsor` bin and legacy
+  `synapsor-runner` alias;
+- a fixture-only `demo --quick` that seeds an inspectable local ledger without
+  Docker;
+- shareable MCP audit JSON/Markdown output;
+- redacted doctor Markdown report output.
+
+The local store is SQLite and intended for local/dev/staging usage. It is not a
+hosted central audit ledger, not RBAC/SSO, not cross-runner search, not
+enterprise retention, and not compliance export.
+
+## Implemented Local Concepts
+
+| Synapsor concept | Runner implementation | Status |
+| --- | --- | --- |
+| Context bindings | Trusted tenant/principal from env/static dev/HTTP/cloud session config | Implemented |
+| Capabilities | Reviewed semantic MCP tools from `synapsor.runner.json` | Implemented |
+| Evidence bundles | Captured/projected rows and metadata persisted locally | Implemented |
+| Query audit | Source/table/fingerprint/row-count/redacted-parameter records | Implemented |
+| Proposals | Immutable before/proposed change sets | Implemented |
+| Approval | Local CLI/UI approval/rejection outside MCP | Implemented |
+| Guarded writeback | Single-row Postgres/MySQL `UPDATE` with primary-key, tenant, allowed-column, conflict, idempotency, and affected-row checks | Implemented |
+| Receipts | Applied/conflict/failed writeback receipts | Implemented |
+| Replay | Proposal replay from local captured records | Implemented |
+| MCP audit | Static risk review for database MCP tool shapes | Implemented |
+| Local indexed search | CLI filters for activity, proposals, evidence, query audit, and receipts | Implemented |
+
+## New Local Ledger Commands
+
+```bash
+synapsor activity search --tenant acme --object invoice:INV-3001
+synapsor proposals list --tenant acme --capability billing.propose_late_fee_waiver --object invoice:INV-3001 --status approved
+synapsor evidence list --tenant acme --capability billing.inspect_invoice --source app_postgres --table invoices
+synapsor evidence show ev_...
+synapsor evidence export ev_... --format json --output evidence.json
+synapsor evidence export ev_... --format markdown --output evidence.md
+synapsor query-audit list --evidence ev_... --source app_postgres --table invoices
+synapsor query-audit show <audit_id>
+synapsor query-audit export <audit_id> --format json --output audit.json
+synapsor receipts list --proposal wrp_...
+synapsor receipts show <receipt_id>
+synapsor replay show --proposal wrp_...
+synapsor replay show --replay replay_wrp_...
+synapsor replay show --evidence ev_...
+synapsor replay export --proposal wrp_... --format json --output replay.json
+synapsor replay export --proposal wrp_... --format markdown --output replay.md
+synapsor doctor --config synapsor.runner.json --report --redact --output synapsor-doctor.md
+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
+```
+
+Unknown top-level commands now return a nonzero error instead of generic help.
+Unsupported flags on the new search/list commands fail clearly rather than
+being silently ignored.
+
+## Local Store Schema And Search
+
+The store remains backward-compatible with existing local SQLite files. New
+metadata columns are nullable and are backfilled from existing JSON where safe.
+
+New/important searchable metadata:
+
+- proposal tenant, principal, capability/action, business object, object id,
+  state, source, table, created time;
+- evidence tenant, principal, capability, proposal id, business object, object
+  id, source, table, query fingerprint, created time;
+- query audit tenant, proposal id, evidence id, source, table, primary-key
+  value, query fingerprint, created time;
+- writeback receipt proposal id, writeback job id, idempotency key, status,
+  created time.
+
+Indexes are created idempotently on the local store for:
+
+- proposals by tenant/time, action/time, capability/time, principal/time,
+  object/time, state/time, source/table/time;
+- evidence bundles by tenant/time, proposal id, created time, capability/time,
+  principal/time, object/time, source/table/time, query fingerprint/time;
+- evidence items by evidence bundle id;
+- query audit by evidence id, proposal id, source/table/time,
+  query fingerprint/time, tenant/time, object/time, primary-key/time;
+- writeback receipts by proposal id, writeback job id, idempotency key,
+  status/time;
+- replay records by proposal id and created time;
+- approvals by proposal id and status/time;
+- proposal events by proposal id and kind/time.
+
+These are local metadata indexes. Runner does not index customer Postgres/MySQL
+tables.
+
+## Read-Only Evidence
+
+Read-only MCP tools can record evidence bundles and query-audit rows. The MCP
+tool response returns an evidence handle. The user can now inspect that handle
+later:
+
+```bash
+synapsor evidence show ev_...
+synapsor evidence list --tenant acme --capability billing.inspect_invoice
+synapsor query-audit list --evidence ev_...
+synapsor activity search --tenant acme --source app_postgres --table invoices
+```
+
+Read-only evidence inspection does not rerun the external database read. It
+shows captured/projected evidence that was already persisted locally.
+
+Proposal replay remains proposal-centric. `replay show --evidence ev_...`
+works only when the evidence bundle is linked to a replayable proposal.
+
+## Replay Versus Time Travel
+
+Runner replay is local captured interaction replay:
+
+```text
+trusted context
+-> captured source-row excerpt
+-> query audit/fingerprint
+-> proposal before/proposed diff
+-> approval/rejection events
+-> writeback job
+-> terminal receipt
+```
+
+It is not:
+
+- external DB time travel;
+- `AS OF` query support over Postgres/MySQL;
+- native branch creation;
+- external DB merge;
+- auto-merge;
+- settlement-policy execution.
+
+Synapsor-native branching, time travel, settlement, and workflow DAG execution
+remain proprietary Synapsor Cloud/DBMS features.
+
+## MCP Resource Boundary
+
+MCP resources remain read-only:
+
+- `synapsor://proposals/{proposal_id}`;
+- `synapsor://evidence/{evidence_bundle_id}`;
+- `synapsor://replay/{replay_id}`.
+
+They inspect local store records and do not mutate source databases. They also
+do not list/search all local records through MCP; local search is a CLI/local UI
+concern.
+
+## Not Included In OSS Runner
+
+- C++ DBMS internals;
+- native Synapsor branches;
+- external DB time travel;
+- `AS OF` external DB queries;
+- external DB merge;
+- auto-merge;
+- settlement policies;
+- workflow DAG engine;
+- `CREATE AGENT WORKFLOW`;
+- hosted workflow graph builder;
+- governed memory;
+- RBAC/SSO;
+- hosted evidence ledger;
+- central org-wide activity search;
+- managed runner fleet;
+- compliance exports;
+- enterprise retention controls;
+- production CDC machinery.
+
+## Safety Boundary Verification
+
+The runner keeps these out of the model-facing MCP tool surface:
+
+- `execute_sql`;
+- `raw_sql`;
+- `query_database`;
+- approval tools;
+- reject tools;
+- apply/commit/writeback tools;
+- database URLs;
+- write credentials;
+- model-controlled tenant authority.
+
+Approval, rejection, and writeback stay in CLI/UI/app-handler/runner paths
+outside the MCP tool surface.
+
+## Current Rough Edges
+
+- The local UI is still proposal-review oriented. The CLI now has first-class
+  local evidence/search commands, but UI search/export for evidence/query-audit
+  is not yet a full dedicated workflow.
+- Read-only evidence has CLI inspection and activity search, but read-only
+  replay is not a standalone replay object unless linked to a proposal.
+- The current direct DB writeback adapter intentionally supports guarded
+  single-row `UPDATE` only. App-owned HTTP/command handlers are the path for
+  richer business writes.
+- The alpha package requires Node >= 22.5.0 because the local ledger uses
+  Node's `node:sqlite` runtime. The package declares this and the bin wrapper
+  exits early with a clear message on older Node versions.
+
+## Tests Covering This Inventory
+
+Relevant local tests:
+
+```bash
+corepack pnpm exec vitest run packages/proposal-store/src/index.test.ts
+corepack pnpm exec vitest run apps/runner/src/cli.test.ts
+corepack pnpm exec vitest run packages/mcp-server/src/index.test.ts
+corepack pnpm test:first-run
+corepack pnpm test:mcp-client-configs
+./scripts/verify-public-commands.sh
+./scripts/verify-packed-runner.sh
+```
+
+The current implementation pass specifically added coverage for:
+
+- unknown command nonzero behavior;
+- unsupported search flags failing clearly;
+- proposal filters by tenant/capability/object/status;
+- evidence show/list/export JSON/Markdown;
+- query-audit list/show/export;
+- receipts list/show;
+- replay by proposal id, replay id, and linked evidence id;
+- replay JSON and Markdown export;
+- activity search by tenant/object;
+- local metadata indexes and idempotent migration/reopen.
+- `demo --quick` creating an inspectable local fixture store;
+- built-in audit example JSON/Markdown output;
+- clean packed-tarball command execution.
+- local store stats, vacuum, and dry-run/apply prune.

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.