@synapsor/runner 0.1.0-alpha.14 → 0.1.0-alpha.15

package/CHANGELOG.md

@@ -33,6 +33,14 @@
   `result_format: 2` or `--result-format v2`.
 - The public command remains `synapsor-runner`.
 
+## 0.1.0-alpha.15
+
+### Changed
+
+- Clarified that users install only `@synapsor/runner`. A handler is the
+  user's app endpoint or script for rich approved writes, and Runner includes
+  templates/examples to help build one.
+
 ## 0.1.0-alpha.14
 
 ### Changed

package/README.md

@@ -25,6 +25,10 @@ After writeback, Runner keeps receipts and replay so you can inspect what happen
 - Executor: your app's writeback handler for anything richer than a guarded
   one-row update.
 
+You install only `@synapsor/runner`. There is no separate handler package to
+install. A handler is your app's endpoint or script for rich approved writes;
+Runner includes templates and examples to help you build one.
+
 ## Who Does What
 
 You write the config: sources, trusted context, capabilities, visible fields,

package/dist/runner.mjs

@@ -2747,7 +2747,7 @@ function assertPersistentStoreAvailable(storePath) {
 }
 function createSynapsorMcpServer(runtime, options = {}) {
   const server = new McpServer(
-    { name: "synapsor-runner", version: "0.1.0-alpha.14" },
+    { name: "synapsor-runner", version: "0.1.0-alpha.15" },
     { capabilities: { tools: {}, resources: {} } }
   );
   const toolNameStyle = options.toolNameStyle ?? "canonical";
@@ -9172,7 +9172,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.14").trim();
+  const runnerVersion = String(parsed.cloud.runner_version || process2.env.npm_package_version || "0.1.0-alpha.15").trim();
   const engines = normalizeEngines(parsed.cloud.engines);
   const capabilities = normalizeCapabilities(parsed.cloud.capabilities);
   const client = new ControlPlaneClient({
@@ -13311,7 +13311,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.14",
+      runner_version: "0.1.0-alpha.15",
       project_id: "token_scope",
       adapter_id: "mcp.your_adapter",
       source_id: "src_replace_me",

package/docs/app-owned-executors.md

@@ -17,6 +17,11 @@ The model-facing MCP tool only creates a proposal. Approval happens outside MCP.
 After approval, Runner calls your `http_handler` or `command_handler`, records
 the receipt, and includes the result in replay.
 
+A handler is your application endpoint or script. It is not a second Synapsor
+package that users need to install. Install `@synapsor/runner`, then generate
+or copy a handler template only when your approved write needs app-owned
+business logic.
+
 Do not use generic SQL for rich business transactions. Let the model propose,
 let Synapsor Runner approve/replay, and let your app execute the transaction.
 

package/docs/handler-helper.md

@@ -3,6 +3,10 @@
 Use the TypeScript handler helper when an approved Synapsor proposal should be
 executed by your application service, not by Runner's direct SQL writer.
 
+This is optional support code for your app-owned handler. Users install
+`@synapsor/runner`; they do not install a separate handler package in the
+current alpha.
+
 The helper is the safe-by-default path for rich writes such as:
 
 - inserting account-credit, refund-review, ticket, or ledger rows;

package/docs/release-notes.md

@@ -11,6 +11,14 @@ npx -y -p @synapsor/runner@alpha synapsor-runner demo --quick
 The OSS runner command is `synapsor-runner`. The `synapsor` command is reserved
 for the Synapsor Cloud CLI.
 
+## 0.1.0-alpha.15
+
+### Handler Wording Clarification
+
+- README and app-owned executor docs now state that users install only
+  `@synapsor/runner`. A handler is the user's own app endpoint or script for
+  rich approved writes, not a second Synapsor package to install.
+
 ## 0.1.0-alpha.14
 
 ### Handler Helper And Changelog Clarity
@@ -209,5 +217,5 @@ After publishing an alpha, verify the public package from a clean temporary
 directory:
 
 ```bash
-./scripts/verify-published-alpha.sh 0.1.0-alpha.14
+./scripts/verify-published-alpha.sh 0.1.0-alpha.15
 ```

package/docs/release-policy.md

@@ -5,7 +5,7 @@ or an exact version:
 
 ```bash
 npx -y -p @synapsor/runner@alpha synapsor-runner demo --quick
-npm install -g @synapsor/runner@0.1.0-alpha.14
+npm install -g @synapsor/runner@0.1.0-alpha.15
 ```
 
 Do not rely on the untagged `latest` dist-tag until a stable release is

package/package.json

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