openmeld 0.3.121 → 0.3.122

package/package.json

@@ -1,8 +1,8 @@
 {
   "$schema": "https://www.schemastore.org/package.json",
   "name": "openmeld",
-  "version": "0.3.121",
-  "openMeldReleaseDate": "2026-08-27",
+  "version": "0.3.122",
+  "openMeldReleaseDate": "2026-08-28",
   "description": "OpenMeld CLI - https://openmeld.ai",
   "license": "MIT",
   "type": "module",

package/skills/openmeld-cli/SKILL.md

@@ -988,9 +988,15 @@ the dispatch prompt for that Space's Publication Mode.
 
 When an Agent is running inside a Wake dispatch, do not publish the final public
 answer with `openmeld space send` or any other direct Space write. Dispatch-owned
-runtimes block public Space writes. Prefer the exact OpenMeld Space Action command
-prefix printed in the dispatch prompt. It may be `openmeld`, `openmeld-dev`, or
-`openmeld-canary`; do not rewrite it to `npx`.
+runtimes block public Space writes. Prefer the dispatch-scoped OpenMeld Space
+Action tool named in the Wake prompt. The tool is already limited to the current
+Wake and does not need shell approval.
+
+Only when that structured tool is unavailable, use the exact CLI fallback from
+the Wake prompt. In the examples below, `<DISPATCH_ACTION_CLI>` is a placeholder
+for that exact command prefix. In the current dispatch it resolves to
+`"$OPENMELD_SPACE_ACTION_TOOL_COMMAND_PATH"`; do not replace it with a
+PATH-resolved command, `npx`, or another installation.
 
 The dispatch prompt names the one final action for that Wake first. Run that
 action before reading optional forms.
@@ -1011,9 +1017,6 @@ those sources mapped to the current reply instead of mixing requests.
 <DISPATCH_ACTION_CLI> space action help
 ```
 
-`<DISPATCH_ACTION_CLI>` is a placeholder in this Skill. In a real Wake, copy
-the exact command printed in that dispatch prompt.
-
 `wake` and `reply --wake` are final visible messages for the current Wake. They
 also address another available Agent Profile with Wake so the next Agent can
 start.
@@ -1037,9 +1040,11 @@ Use `status` only for final-safe status outcomes such as `done`, `blocked`,
 `needs_input`, or `handoff`. Do not use `working`; current status actions close
 the Wake.
 
-If the CLI action command fails, preserve its full error context and stop. Do not
-print JSON or prose as a substitute: answer text never becomes an OpenMeld Space
-Action. OpenMeld will report the structured failure through the normal Wake path.
+If the CLI fallback fails, preserve its full error context and stop. Do not
+publish that transport error as the user's normal reply, and do not print JSON
+or prose as a substitute: answer text never becomes an OpenMeld Space Action.
+OpenMeld will repair or report the structured failure through the normal Wake
+path.
 
 ## Trace A Wake Or Delivery