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

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/security-boundary.md

@@ -3,6 +3,23 @@
 Synapsor Runner controls a narrow database path for MCP agents. It does not make
 MCP generally secure and it does not solve prompt injection.
 
+## Least-privilege database access
+
+Use a read-only database user, restricted views, row-level security, and staging
+data where appropriate. Synapsor Runner is not a replacement for database
+permissions.
+
+Database permissions protect the connection. Synapsor Runner shapes the
+model-facing interface: reviewed semantic capabilities, trusted context
+binding, evidence handles, query audit, local inspection, and proposal-first
+writes instead of model-facing commit authority.
+
+If all you need is restricted reads, database permissions are a good start.
+Use Synapsor Runner when you also want the agent-facing layer: semantic tools,
+trusted context, evidence handles, query audit, local inspection, and
+proposal-first writes. Proposal workflows add full replay across evidence,
+approval, writeback receipts, and events.
+
 The model-facing MCP server exposes reviewed semantic tools such as
 `billing.inspect_invoice` and `billing.propose_late_fee_waiver`.
 

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
 ```
@@ -54,27 +54,78 @@ The model-facing MCP tools are:
 
 - `support.inspect_ticket`
 - `support.propose_ticket_resolution`
+- `support.inspect_customer_account`
+- `support.propose_plan_credit`
 - `billing.inspect_invoice`
 - `billing.propose_late_fee_waiver`
+- `orders.inspect_order`
+- `orders.propose_status_change`
 
 The model does not receive approval tools, commit tools, write credentials, raw SQL, arbitrary table names, arbitrary column names, or tenant authority.
 
+## Safe Write Examples
+
+After `synapsor 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
+```
+
+Expected safety output:
+
+```text
+Source DB changed:
+no
+
+Guarded writeback applied.
+* proposal approved: yes
+* primary key matched: yes
+* tenant guard matched: yes
+* allowed columns only: yes
+* conflict guard passed: yes
+```
+
+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
+```
+
+Safety guarantees:
+
+- proposals store evidence, a before/after diff, trusted tenant/principal
+  context, and query audit before any write;
+- approval stays outside the model-facing MCP tool surface;
+- writeback is single-row, primary-key targeted, tenant guarded,
+  allowed-column checked, idempotent, and conflict guarded;
+- stale rows return `conflict` and are replayable.
+
+Current limitation: v0.1 is intentionally local and single-user. It does not
+provide hosted RBAC, workflow DAGs, branches, settlement policies, auto-merge,
+or production-scale runner orchestration.
+
 ## Review And Replay
 
 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/examples/reference-support-billing-app/schema.sql

@@ -11,6 +11,8 @@ CREATE TABLE IF NOT EXISTS public.customers (
   name text NOT NULL,
   email text,
   plan text NOT NULL,
+  plan_credit_cents integer NOT NULL DEFAULT 0,
+  credit_reason text,
   created_at timestamptz NOT NULL DEFAULT now(),
   updated_at timestamptz NOT NULL DEFAULT now()
 );
@@ -36,6 +38,15 @@ CREATE TABLE IF NOT EXISTS public.invoices (
   updated_at timestamptz NOT NULL DEFAULT now()
 );
 
+CREATE TABLE IF NOT EXISTS public.orders (
+  id text PRIMARY KEY,
+  tenant_id text NOT NULL REFERENCES public.tenants(id),
+  customer_id text NOT NULL REFERENCES public.customers(id),
+  status text NOT NULL,
+  status_change_reason text,
+  updated_at timestamptz NOT NULL DEFAULT now()
+);
+
 DO $$
 BEGIN
   IF NOT EXISTS (SELECT 1 FROM pg_roles WHERE rolname = 'synapsor_reader') THEN
@@ -50,6 +61,8 @@ $$;
 GRANT CONNECT ON DATABASE synapsor_reference_support_billing TO synapsor_reader, synapsor_writer;
 GRANT USAGE ON SCHEMA public TO synapsor_reader, synapsor_writer;
 GRANT CREATE ON SCHEMA public TO synapsor_writer;
-GRANT SELECT ON public.tenants, public.customers, public.support_tickets, public.invoices TO synapsor_reader, synapsor_writer;
+GRANT SELECT ON public.tenants, public.customers, public.support_tickets, public.invoices, public.orders TO synapsor_reader, synapsor_writer;
+GRANT UPDATE (plan_credit_cents, credit_reason, updated_at) ON public.customers TO synapsor_writer;
 GRANT UPDATE (status, resolution_note, updated_at) ON public.support_tickets TO synapsor_writer;
 GRANT UPDATE (late_fee_cents, waiver_reason, updated_at) ON public.invoices TO synapsor_writer;
+GRANT UPDATE (status, status_change_reason, updated_at) ON public.orders TO synapsor_writer;

package/examples/reference-support-billing-app/seed.sql

@@ -4,12 +4,12 @@ VALUES
   ('otherco', 'OtherCo Labs', '2026-06-20T10:00:00Z', '2026-06-20T10:00:00Z')
 ON CONFLICT (id) DO UPDATE SET name = EXCLUDED.name, updated_at = EXCLUDED.updated_at;
 
-INSERT INTO public.customers (id, tenant_id, name, email, plan, created_at, updated_at)
+INSERT INTO public.customers (id, tenant_id, name, email, plan, plan_credit_cents, credit_reason, created_at, updated_at)
 VALUES
-  ('cust_acme_1', 'acme', 'Acme Robotics', 'ops@example.invalid', 'enterprise', '2026-06-20T10:00:00Z', '2026-06-20T10:00:00Z'),
-  ('cust_acme_2', 'acme', 'Acme Field Ops', 'field@example.invalid', 'builder', '2026-06-20T10:00:00Z', '2026-06-20T10:00:00Z'),
-  ('cust_other_1', 'otherco', 'OtherCo Labs', 'ops@otherco.invalid', 'builder', '2026-06-20T10:00:00Z', '2026-06-20T10:00:00Z')
-ON CONFLICT (id) DO UPDATE SET tenant_id = EXCLUDED.tenant_id, name = EXCLUDED.name, email = EXCLUDED.email, plan = EXCLUDED.plan, updated_at = EXCLUDED.updated_at;
+  ('cust_acme_1', 'acme', 'Acme Robotics', 'ops@example.invalid', 'enterprise', 0, NULL, '2026-06-20T10:00:00Z', '2026-06-20T10:00:00Z'),
+  ('cust_acme_2', 'acme', 'Acme Field Ops', 'field@example.invalid', 'builder', 0, NULL, '2026-06-20T10:00:00Z', '2026-06-20T10:00:00Z'),
+  ('cust_other_1', 'otherco', 'OtherCo Labs', 'ops@otherco.invalid', 'builder', 0, NULL, '2026-06-20T10:00:00Z', '2026-06-20T10:00:00Z')
+ON CONFLICT (id) DO UPDATE SET tenant_id = EXCLUDED.tenant_id, name = EXCLUDED.name, email = EXCLUDED.email, plan = EXCLUDED.plan, plan_credit_cents = EXCLUDED.plan_credit_cents, credit_reason = EXCLUDED.credit_reason, updated_at = EXCLUDED.updated_at;
 
 INSERT INTO public.support_tickets (id, tenant_id, customer_id, subject, status, resolution_note, updated_at)
 VALUES
@@ -24,3 +24,10 @@ VALUES
   ('INV-3002', 'acme', 'cust_acme_2', 'paid', 0, 0, NULL, '2026-06-20T14:40:00Z'),
   ('INV-9001', 'otherco', 'cust_other_1', 'overdue', 25500, 5500, NULL, '2026-06-20T14:31:08Z')
 ON CONFLICT (id) DO UPDATE SET tenant_id = EXCLUDED.tenant_id, customer_id = EXCLUDED.customer_id, status = EXCLUDED.status, balance_cents = EXCLUDED.balance_cents, late_fee_cents = EXCLUDED.late_fee_cents, waiver_reason = EXCLUDED.waiver_reason, updated_at = EXCLUDED.updated_at;
+
+INSERT INTO public.orders (id, tenant_id, customer_id, status, status_change_reason, updated_at)
+VALUES
+  ('O-1001', 'acme', 'cust_acme_1', 'paid', NULL, '2026-06-20T13:00:00Z'),
+  ('O-1002', 'acme', 'cust_acme_2', 'processing', NULL, '2026-06-20T13:05:00Z'),
+  ('O-9001', 'otherco', 'cust_other_1', 'paid', NULL, '2026-06-20T13:00:00Z')
+ON CONFLICT (id) DO UPDATE SET tenant_id = EXCLUDED.tenant_id, customer_id = EXCLUDED.customer_id, status = EXCLUDED.status, status_change_reason = EXCLUDED.status_change_reason, updated_at = EXCLUDED.updated_at;

package/examples/reference-support-billing-app/synapsor.runner.json

@@ -83,6 +83,56 @@
       "conflict_guard": { "column": "updated_at" },
       "approval": { "mode": "human", "required_role": "support_lead" }
     },
+    {
+      "name": "support.inspect_customer_account",
+      "kind": "read",
+      "source": "app_postgres",
+      "context": "local_operator",
+      "target": {
+        "schema": "public",
+        "table": "customers",
+        "primary_key": "id",
+        "tenant_key": "tenant_id"
+      },
+      "args": {
+        "customer_id": { "type": "string", "required": true, "max_length": 128 }
+      },
+      "lookup": { "id_from_arg": "customer_id" },
+      "visible_columns": ["id", "tenant_id", "name", "plan", "plan_credit_cents", "credit_reason", "updated_at"],
+      "evidence": "required",
+      "max_rows": 1
+    },
+    {
+      "name": "support.propose_plan_credit",
+      "kind": "proposal",
+      "source": "app_postgres",
+      "context": "local_operator",
+      "target": {
+        "schema": "public",
+        "table": "customers",
+        "primary_key": "id",
+        "tenant_key": "tenant_id"
+      },
+      "args": {
+        "customer_id": { "type": "string", "required": true, "max_length": 128 },
+        "credit_cents": { "type": "number", "required": true, "minimum": 0, "maximum": 5000 },
+        "reason": { "type": "string", "required": true, "max_length": 500 }
+      },
+      "lookup": { "id_from_arg": "customer_id" },
+      "visible_columns": ["id", "tenant_id", "name", "plan", "plan_credit_cents", "credit_reason", "updated_at"],
+      "evidence": "required",
+      "max_rows": 1,
+      "patch": {
+        "plan_credit_cents": { "from_arg": "credit_cents" },
+        "credit_reason": { "from_arg": "reason" }
+      },
+      "allowed_columns": ["plan_credit_cents", "credit_reason"],
+      "numeric_bounds": {
+        "plan_credit_cents": { "minimum": 0, "maximum": 5000 }
+      },
+      "conflict_guard": { "column": "updated_at" },
+      "approval": { "mode": "human", "required_role": "support_lead" }
+    },
     {
       "name": "billing.inspect_invoice",
       "kind": "read",
@@ -131,6 +181,61 @@
       },
       "conflict_guard": { "column": "updated_at" },
       "approval": { "mode": "human", "required_role": "billing_lead" }
+    },
+    {
+      "name": "orders.inspect_order",
+      "kind": "read",
+      "source": "app_postgres",
+      "context": "local_operator",
+      "target": {
+        "schema": "public",
+        "table": "orders",
+        "primary_key": "id",
+        "tenant_key": "tenant_id"
+      },
+      "args": {
+        "order_id": { "type": "string", "required": true, "max_length": 128 }
+      },
+      "lookup": { "id_from_arg": "order_id" },
+      "visible_columns": ["id", "tenant_id", "customer_id", "status", "status_change_reason", "updated_at"],
+      "evidence": "required",
+      "max_rows": 1
+    },
+    {
+      "name": "orders.propose_status_change",
+      "kind": "proposal",
+      "source": "app_postgres",
+      "context": "local_operator",
+      "target": {
+        "schema": "public",
+        "table": "orders",
+        "primary_key": "id",
+        "tenant_key": "tenant_id"
+      },
+      "args": {
+        "order_id": { "type": "string", "required": true, "max_length": 128 },
+        "status": { "type": "string", "required": true, "enum": ["ready_to_ship", "canceled"] },
+        "reason": { "type": "string", "required": true, "max_length": 500 }
+      },
+      "lookup": { "id_from_arg": "order_id" },
+      "visible_columns": ["id", "tenant_id", "customer_id", "status", "status_change_reason", "updated_at"],
+      "evidence": "required",
+      "max_rows": 1,
+      "patch": {
+        "status": { "from_arg": "status" },
+        "status_change_reason": { "from_arg": "reason" }
+      },
+      "allowed_columns": ["status", "status_change_reason"],
+      "transition_guards": {
+        "status": {
+          "allowed": {
+            "paid": ["ready_to_ship", "canceled"],
+            "processing": ["ready_to_ship"]
+          }
+        }
+      },
+      "conflict_guard": { "column": "updated_at" },
+      "approval": { "mode": "human", "required_role": "orders_lead" }
     }
   ]
 }

package/package.json

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