@synapsor/runner 0.1.5 → 0.1.6

package/README.md

@@ -277,9 +277,16 @@ synapsor-runner dsl compile ./contract.synapsor --out ./synapsor.contract.json
 synapsor-runner contract validate ./synapsor.contract.json
 synapsor-runner contract bundle ./synapsor.contract.json --out ./synapsor-runner-bundle
 synapsor-runner cloud push ./synapsor.contract.json --dry-run
+cd ./synapsor-runner-bundle
+cp .env.example .env  # fill in and export your read-only database values
 synapsor-runner mcp serve --config ./synapsor.runner.json --store ./.synapsor/local.db
 ```
 
+The `contract bundle` step generates `synapsor.runner.json` (with env-var
+placeholders) inside the bundle directory, which is why `mcp serve` runs from
+there. The server keeps stdout clean for MCP protocol frames and prints its
+ready line on stderr.
+
 Your `synapsor.runner.json` supplies local wiring: database env var names,
 SQLite store path, MCP transport settings, and local debug options. The
 contract supplies the portable meaning: contexts, capabilities, evidence,

package/dist/runner.mjs

@@ -3521,6 +3521,7 @@ async function serveStdio(options = {}) {
   const server = createSynapsorMcpServer(runtime, { toolNameStyle: options.toolNameStyle });
   const transport = new StdioServerTransport();
   await server.connect(transport);
+  process.stderr.write("synapsor-runner MCP stdio server ready. Waiting for an MCP client on stdio; logs stay on stderr.\n");
   await new Promise((resolve) => {
     const previousOnClose = transport.onclose;
     const close = () => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synapsor/runner",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "Stop giving AI agents execute_sql; expose reviewed Postgres/MySQL MCP actions with proposals, approval, writeback, and replay.",
   "license": "Apache-2.0",
   "type": "module",