@synapsor/runner 0.1.0-alpha.8 → 0.1.0-alpha.9

package/README.md

@@ -7,6 +7,25 @@ Runner lets an MCP agent inspect scoped data and request database-backed
 business actions without receiving raw SQL, write credentials, approval tools,
 or commit tools.
 
+## Alpha Operational Notes
+
+These are current alpha requirements, not hidden behavior:
+
+- Writeback with `--config ./synapsor.runner.json` reads the trusted writer
+  connection from the source `write_url_env`, for example
+  `SYNAPSOR_DATABASE_WRITE_URL`. `SYNAPSOR_DATABASE_URL` is only the legacy
+  fallback when you run direct worker/apply flows without a local config.
+- `synapsor-runner mcp serve-http` is a small authenticated JSON-RPC endpoint
+  for `tools/list`, `tools/call`, and `resources/read`. It is not full MCP
+  Streamable HTTP and does not implement the `initialize`/SSE handshake. Use
+  stdio MCP for standard local MCP clients, or wrap the HTTP endpoint like the
+  OpenAI HTTP example.
+- Direct SQL writeback creates or writes `synapsor_writeback_receipts` for
+  idempotency and replay. The trusted writer needs permission for that table,
+  or an administrator must pre-create it and grant access. Use an app-owned
+  `http_handler` or `command_handler` if Runner should not create receipt
+  tables in your application schema.
+
 ```text
 AI agent or MCP client
 (Claude, Cursor, OpenAI Agents SDK, LangGraph)

package/dist/runner.mjs

@@ -2685,7 +2685,7 @@ function createMcpRuntime(config, options = {}) {
 }
 function createSynapsorMcpServer(runtime) {
   const server = new McpServer(
-    { name: "synapsor-runner", version: "0.1.0-alpha.8" },
+    { name: "synapsor-runner", version: "0.1.0-alpha.9" },
     { capabilities: { tools: {}, resources: {} } }
   );
   if (runtime.config.mode === "cloud") {
@@ -7986,7 +7986,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.8").trim();
+  const runnerVersion = String(parsed.cloud.runner_version || process2.env.npm_package_version || "0.1.0-alpha.9").trim();
   const engines = normalizeEngines(parsed.cloud.engines);
   const capabilities = normalizeCapabilities(parsed.cloud.capabilities);
   const client = new ControlPlaneClient({
@@ -11444,7 +11444,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.8",
+      runner_version: "0.1.0-alpha.9",
       project_id: "token_scope",
       adapter_id: "mcp.your_adapter",
       source_id: "src_replace_me",
@@ -11655,6 +11655,14 @@ Inspect local query fingerprints, table names, row counts, and redacted-paramete
   ${cmd} apply --job job.json --config ./synapsor.runner.json --store ./.synapsor/local.db
 
 Apply an approved proposal through guarded writeback. Requires a trusted write credential.
+
+With --config, the writer connection comes from source.write_url_env, such as
+SYNAPSOR_DATABASE_WRITE_URL. SYNAPSOR_DATABASE_URL is only the legacy fallback
+for direct worker/apply flows without a local config.
+
+Direct SQL writeback creates or writes synapsor_writeback_receipts for
+idempotency and replay, so the trusted writer needs permission for that table
+or an administrator must pre-create and grant it.
 `,
     replay: `Usage:
   ${cmd} replay list [--tenant acme] [--object invoice:INV-3001]

package/package.json

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