@sabaiway/agent-workflow-engine 1.13.0 → 1.14.0

package/CHANGELOG.md

@@ -4,6 +4,25 @@ 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.14.0 — The review canon names its computed instrument, activity-aware (AD-046)
+
+A **feature** release (canon content + guards; installer unchanged; deployment-lineage head stays
+`1.3.0` — no migration). The kit's review-round ledger (AD-045 / AD-046) is now NAMED by the canon,
+at the right activity scope:
+
+- **`references/procedures.md`** — the plan-**execution** review step names the ledger (record ·
+  `--status` · `--check` as the loop's gate; the exit contract stays in the tool's own header —
+  point, don't restate); the review steps of BOTH activities gain the triage classification
+  vocabulary (`fixable-bug / inherent-layer-residual / escalate`; a minor never forces triage);
+  plan-**authoring** carries NO tool pointer — the ledger is plan-execution-scoped.
+- **`references/planning.md` §9** — a new **"Computed instrument (plan-execution)"** paragraph: the
+  stop decision is READ from the ledger, never remembered; stated neutrally that the same per-round
+  tally + classification discipline governs plan-authoring review.
+- **Drift-guards in BOTH directions** — `test/procedures-canon.test.mjs` pins the pointer INSIDE the
+  plan-execution review step (a step extractor, not a whole-section match) and its ABSENCE from
+  plan-authoring; `test/planning-canon.test.mjs` pins §9's ledger naming + the exact scope phrase.
+  Lens files untouched (the 22 discipline tokens unchanged).
+
 ## 1.13.0 — The agent-rules lens gets its ONE canonical home here (slot-render, AD-041)
 
 A **feature** release (canon content + its guard; installer unchanged; deployment-lineage head

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.13.0'
+  version: '1.14.0'
 ---
 
 # agent-workflow-engine

package/capability.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-engine",
-  "version": "1.13.0",
+  "version": "1.14.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",

package/references/planning.md

@@ -132,3 +132,5 @@ These disciplines keep a plan converging instead of churning, and keep a fold or
 **Convergence bar.** A review loop is CLEAN only when one round returns **0 blockers + 0 majors** from EVERY named backend the recipe runs (nits / non-blocking + a ship verdict is the stop). FOLDING a finding is NOT convergence — re-review after folding. This §9 governs the ALTITUDE at which you reach clean (fix the major, or raise it to an explicit acceptance invariant Execute must meet) — it NEVER lowers the bar to "majors folded".
 
 **Convergence heuristic.** When a review round keeps finding code-mechanism issues on a stable architecture, STOP refining prose — either raise the spec to invariant + acceptance altitude, or hand the mechanics to Execute. Do not re-litigate code mechanics in the plan.
+
+**Computed instrument (plan-execution).** The **review-ledger** computes the crossover-stop for the plan-execution (code) loop: each round and each triage classification — **fixable-bug** (a fold pinned by a red→green test) / **inherent-layer-residual** (raised to an acceptance criterion) / **escalate** (a maintainer decision) — is recorded, and the stop decision is READ from the ledger, never remembered; its `--check` is the loop's gate (the exit contract lives in the tool's own header — point, don't restate). The same per-round tally + classification discipline governs plan-authoring review; the ledger itself is plan-execution-scoped.

package/references/procedures.md

@@ -69,7 +69,10 @@ Produce a self-contained, cold-readable plan, reviewed to the configured depth b
    exhausting the strictest backend. Run a **self-consistency** read before every re-review and route an
    all-mechanics/CI or prose-only artifact to a **thin plan + diff-review** ([`planning.md`](planning.md)
    §9). Each round MUST emit **{round N · finding-origin tally (first-draft / fold-induced / mechanics) ·
-   per-backend verdict}** so the crossover is a computed signal, not a remembered rule.
+   per-backend verdict}** so the crossover is a computed signal, not a remembered rule. At the cap,
+   classify every surviving blocking finding — **fixable-bug** (fold ONCE as a red→green test, re-review)
+   / **inherent-layer-residual** (document + raise to an acceptance criterion) / **escalate** (the
+   maintainer decides); a minor never forces triage.
 6. **Present for approval** — surface the finished plan to the user; do not begin execution here. A
    harness "approved — start coding" prompt (**ExitPlanMode**) authorizes the PLAN only
    ([`planning.md`](planning.md) §6); continuing into `plan-execution` is a deliberate transition taken
@@ -106,7 +109,11 @@ Execute an approved plan Step by Step; each Step is one logical commit.
    runs every named backend **every round** (recipe fidelity, [`orchestration.md`](orchestration.md) §4);
    loop to **0 blockers + 0 majors** from every backend before the gate. Each round MUST emit
    **{round N · finding-origin tally · per-backend verdict}**; when backends diverge, that is the
-   crossover — resolve at altitude, not by exhausting the strictest backend.
+   crossover — resolve at altitude, not by exhausting the strictest backend. Classify survivors at the
+   cap the same way (**fixable-bug / inherent-layer-residual / escalate**). This loop's computed
+   instrument is the **review-ledger**: record each round + triage, read the stop from its `--status`
+   render (it replaces the hand-composed tally), and wire `review-ledger --check` as the gate — the
+   exit contract lives in the tool's own header, never restated here.
 6. **Gates** — run the project's verification gate (tests + checks) to green before committing.
 7. **Commit boundary** — the orchestrator makes the single commit for the Step; a backend never
    commits. The project's commit-approval policy (e.g. ask first) lives in the project's own rules.