octwin-cli 0.7.0 → 0.7.1

package/CHANGELOG.md

@@ -5,6 +5,19 @@ Format: [Keep a Changelog](https://keepachangelog.com/) — newest first, bucket
 **Added · Changed · Deprecated · Removed · Fixed · Security**. The platform-wide view lives in the
 repo root [`CHANGELOG.md`](../../CHANGELOG.md); this file is the CLI-only cut that ships with the package.
 
+## [0.7.1] - 2026-08-19
+
+### Fixed
+- **`work decide` now says when an action moves nothing.** `to_stage` is optional — an action may
+  record a decision without a transition — but both outputs communicated that by omission: `--dry-run`
+  left `to_stage: null` sitting among twenty other keys, and a real apply printed a bare
+  `✓ Applied '<action>'`. An author read both, shipped `request_more_info` with no `to_stage`, and
+  lost the `awaiting_customer` their whole customer-reply capture branched on — their words: *"Nothing
+  about this failed loudly; it just quietly never did the one thing the whole feature depends on."*
+  The preview now states `→ does NOT change the status (this action only records a decision)` and the
+  apply says `status unchanged (the action declares no to_stage)`. The console's decision panel got the
+  same sentence in the same change.
+
 ## [0.7.0] - 2026-08-18
 
 ### Added

package/dist/index.js

@@ -1959,11 +1959,11 @@ async function cmdRecordsWrite(flags) {
         if (json?.has_xrm === false)
             die('this pack declares no XRM entities');
         const rec = json?.record ?? {};
-        // 200 = the dedupe key matched an existing row; 201 = genuinely new. Saying
-        // "created" for a match would misreport what the pack's `dedupe_by` did.
+        // 200 = the entity's identity matched an existing row; 201 = genuinely new.
+        // Saying "created" for a match would misreport what the save actually did.
         console.log(status === 201
             ? `✓ Created #${rec.record_number ?? '?'}  ${rec.id ?? ''}`
-            : `✓ Matched an EXISTING record (the entity's dedupe key hit) — #${rec.record_number ?? '?'}  ${rec.id ?? ''}`);
+            : `✓ Matched an EXISTING record (its unique constraint identified it) — #${rec.record_number ?? '?'}  ${rec.id ?? ''}`);
         if (rec.id)
             readBack(rec.id);
         return;
@@ -2747,10 +2747,17 @@ async function cmdWorkWrite(flags) {
     }
     if (dryRun) {
         console.log('Preview (nothing was committed):');
+        // Stated in words BEFORE the dump. `to_stage: null` is already in the JSON below, but a null
+        // among twenty keys is not an answer anyone reads — a pack author previewed exactly this,
+        // shipped an action with no `to_stage`, and lost the `awaiting_customer` their whole
+        // reply-capture branched on. Same reason the console preview now says it too.
+        console.log(json?.to_stage
+            ? `  → moves the record to '${json.to_stage}'.`
+            : '  → does NOT change the status (this action only records a decision).');
         console.log(JSON.stringify(json, null, 2));
         return;
     }
-    console.log(`✓ Applied '${action}'${json?.to_stage ? ` — record is now '${json.to_stage}'` : ''}.`);
+    console.log(`✓ Applied '${action}'${json?.to_stage ? ` — record is now '${json.to_stage}'` : ' — status unchanged (the action declares no to_stage)'}.`);
     // `relayed`/`notified` are the customer-facing half; silence here usually means
     // the action had no message template, which is easy to mistake for a failure.
     const reached = json?.relayed || json?.notified;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "octwin-cli",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "Octwin external-pack developer CLI (by CEQUENS) — scaffold, validate, deploy, and check pure-YAML packs on your tenant.",
   "type": "module",
   "bin": {