@owlmeans/viable-sdk 0.1.18-rc.41 → 0.1.18-rc.42

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/viable-sdk",
-  "version": "0.1.18-rc.41",
-  "generatedAt": "2026-10-03T15:33:53.018Z",
+  "version": "0.1.18-rc.42",
+  "generatedAt": "2026-10-04T01:01:54.400Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

package/agent-meta/skills/viable-sdk/SKILL.md

@@ -8,7 +8,7 @@ user-invocable: false
 # @owlmeans/viable-sdk
 
 **Layer:** Tooling (Node/Bun; not a browser or React package)
-**Install:** `"@owlmeans/viable-sdk": "^0.1.18-rc.41"` in `dependencies`
+**Install:** `"@owlmeans/viable-sdk": "^0.1.18-rc.42"` in `dependencies`
 **Subpaths:** `.` · `./executor` · `./run` · `./tools` · `./task` · `./harness`
 **Contracts:** `@owlmeans/viable-common` (`./connect`, `./slot`, `./integrity`, and the planning
 vocabulary — story type and story flow) and `@owlmeans/planning` (the planning protocol tree
@@ -120,7 +120,8 @@ opening one there would claim the project's single connector slot, **supersede t
 legitimately holding it**, and be abandoned before the first operation was delivered.
 
 So `ensureSession` — what `confirm_project`, `reinitialize_project`, `develop_story`,
-`modify_project`, `apply_planning_kit` and `resume_pipeline` call before returning their job — opens one only on a
+`modify_project` and `resume_pipeline` call before returning their job, and `apply_planning_kit`
+before its write — opens one only on a
 `sessionCapable` host, and `next_task`/`submit_task_result` are available on `performsModelTasks`
 (delegated **and** session-capable) rather than on the account setting alone. `serverInstructions`
 reads the same predicate: a parent told to call `next_task` when the tool is not in its list is a

package/build/harness/templates.js

@@ -50,7 +50,7 @@ const marked = (body) => `<!-- viable:begin -->\n${body}\n<!-- viable:end -->`;
  * viable-mcp release. A tag (`@next`) is refused by that audit, and a copy per harness was how three
  * of four configs kept a tag while the fourth carried the pin.
  */
-const MCP_COMMAND = ['npx', '-y', '@owlmeans/viable-mcp@^0.1.18-rc.40'];
+const MCP_COMMAND = ['npx', '-y', '@owlmeans/viable-mcp@^0.1.18-rc.41'];
 const MCP_EXECUTABLE = MCP_COMMAND[0];
 const MCP_ARGS = MCP_COMMAND.slice(1);
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/viable-sdk",
-  "version": "0.1.18-rc.41",
+  "version": "0.1.18-rc.42",
   "license": "MIT",
   "description": "Drive the OwlMeans Viable platform from outside it — the connector session, the local slot executor, the tool catalogue and the model-task protocol an external coding agent answers.",
   "type": "module",
@@ -70,15 +70,15 @@
     "@owlmeans/client-config": "^0.1.18-rc.41",
     "@owlmeans/client-context": "^0.1.18-rc.45",
     "@owlmeans/client-entrypoint": "^0.1.18-rc.44",
-    "@owlmeans/client-planning": "^0.1.18-rc.19",
+    "@owlmeans/client-planning": "^0.1.18-rc.20",
     "@owlmeans/config": "^0.1.18-rc.41",
     "@owlmeans/context": "^0.1.18-rc.32",
     "@owlmeans/entrypoint": "^0.1.18-rc.39",
     "@owlmeans/error": "^0.1.18-rc.36",
-    "@owlmeans/planning": "^0.1.18-rc.16",
+    "@owlmeans/planning": "^0.1.18-rc.17",
     "@owlmeans/route": "^0.1.18-rc.33",
     "@owlmeans/socket": "^0.1.18-rc.37",
-    "@owlmeans/viable-common": "^0.0.42",
+    "@owlmeans/viable-common": "^0.0.43",
     "ajv": "^8.17.1",
     "fs-extra": "^11.3.0",
     "globby": "^14.1.0",
@@ -95,7 +95,7 @@
   "devDependencies": {
     "@modelcontextprotocol/sdk": "^1.30.0",
     "@owlmeans/dep-config": "workspace:*",
-    "@owlmeans/server-planning": "^0.1.18-rc.19",
+    "@owlmeans/server-planning": "^0.1.18-rc.20",
     "@types/bun": "^1.4.0",
     "@types/fs-extra": "^11.0.4",
     "@types/node": "^26.1.0",