@sabaiway/agent-workflow-engine 1.8.0 → 1.9.0

package/CHANGELOG.md

@@ -4,6 +4,22 @@ All notable changes to the methodology engine. Versions are this **package's** n
 they are distinct from the **deployment-lineage** stamp written into a project's `docs/ai/`
 (which tracks the shared `agent-workflow` lineage, head `1.3.0`).
 
+## 1.9.0 — Honest installer messaging: the verb states what was observed, the note states facts
+
+A **feature** release (installer output contract only; the canon text is unchanged). `bin/install.mjs`
+no longer claims "updated the canon to vX" on every run and no longer accuses the npx cache on a
+same-version re-run:
+
+- **The final verb is keyed on the OBSERVED version comparison**, never on mere presence: fresh or
+  legacy/unstamped → `installed` (no transition claim when the prior version is unknowable); older →
+  `updated the canon to vX`; same → `refreshed the already-current canon`; newer → `downgraded the
+  canon to vX` (reachable only under the explicit `--allow-downgrade`).
+- **The same-version note states observable facts only** — the copy still ran (a re-run repairs
+  locally modified or deleted files) — plus a CONDITIONAL hint: *if you expected a newer version*,
+  invoke the `@latest` tag explicitly. The "npx likely served a cached build" accusation is gone
+  (not observable without a network check).
+- The never-downgrade gate, its refusal wording, and the read-before-write ordering are untouched.
+
 ## 1.8.0 — Mechanize the §9 review-loop discipline (round cap · crossover · finding-origin)
 
 A **feature** release. The methodology canon institutionalizes the review-loop economics so the round

package/SKILL.md

@@ -3,7 +3,7 @@ name: agent-workflow-engine
 description: Canonical home of the agent-workflow planning methodology — the Plan→Phase→Step→Substep vocabulary, plan lifecycle, queue.md series index, mandatory Cleanup phase, the bounded methodology slot fragment, the orchestration-recipe vocabulary (Solo / Reviewed / Council / Delegated), and the activity-procedures canon (plan-authoring / plan-execution, with typed recipe slots). A published, installable npm package (available:true) that *provides* the methodology text; it mutates nothing. The composition root (agent-workflow-kit) reads this canon LIVE from the installed engine and injects the bounded slots from it — one source of truth, no bundled mirror; `npx @sabaiway/agent-workflow-kit@latest init` installs the engine.
 disable-model-invocation: true
 metadata:
-  version: '1.8.0'
+  version: '1.9.0'
 ---
 
 # agent-workflow-engine

package/bin/install.mjs

@@ -241,15 +241,25 @@ const main = async () => {
   await Promise.all(
     PAYLOAD.map((entry) => copyRecursive(resolve(PKG_ROOT, entry), resolve(target, entry), target)),
   );
-  console.log(
-    `[agent-workflow-engine] ${wasPresent ? 'updated the canon to' : 'installed'} v${version} -> ${tildify(target)}`,
-  );
+  // Verb keyed on the OBSERVED version relation (cmp), never on mere presence: null (fresh install,
+  // or a legacy/unstamped one whose prior version is unknowable) → "installed"; -1 → a real update;
+  // 0 → already current (the copy still ran — see the note below); 1 is reachable only under
+  // --allow-downgrade (the gate above refused otherwise) and says so plainly.
+  const verb =
+    cmp === 0 ? 'refreshed the already-current canon'
+    : cmp === 1 ? 'downgraded the canon to'
+    : cmp === -1 ? 'updated the canon to'
+    : 'installed';
+  console.log(`[agent-workflow-engine] ${verb} v${version} -> ${tildify(target)}`);
 
-  // No-op re-run (same version) → almost always npx served a cached build; say so + point at @latest.
+  // Same-version re-run: state observable facts only. The copy DID run (repair-on-rerun is a feature —
+  // it restores locally modified/deleted files), and whether npx served a cached build is NOT
+  // observable here (no network), so the note never claims it; the @latest hint is conditional.
   if (cmp === 0) {
     console.log(
-      `[agent-workflow-engine] note: no version change — the canon was already v${version}. If you ` +
-        `expected an update, npx likely served a cached build; re-run bypassing the cache:\n` +
+      `[agent-workflow-engine] note: the canon was already v${version} — the copy still ran, restoring ` +
+        `any locally modified or deleted canon file to this version's packaged contents. If you ` +
+        `expected a NEWER version, invoke the @latest tag explicitly:\n` +
         `    npx @sabaiway/agent-workflow-engine@latest init`,
     );
   }

package/capability.json

@@ -3,7 +3,7 @@
   "schema": 1,
   "name": "agent-workflow-engine",
   "kind": "methodology-engine",
-  "version": "1.8.0",
+  "version": "1.9.0",
   "available": true,
   "provides": ["plan"],
   "roles": {},

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-engine",
-  "version": "1.8.0",
+  "version": "1.9.0",
   "description": "Canonical home of the agent-workflow planning methodology — the Plan→Phase→Step vocabulary, plan lifecycle, queue.md series index, and mandatory Cleanup phase, consumed by the kit (composition root). The methodology engine of the agent-workflow family.",
   "keywords": [
     "ai-agents",