@sabaiway/agent-workflow-engine 4.0.0 → 4.1.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 `3.0.0`).
 
+## 4.1.0 — the queue is a named surface with a checker, not a prose promise
+
+`references/planning.md` gains **`## The queue`**: `docs/plans/queue.md` NAMES work and never holds
+the analysis of it — a row is one plain sentence saying what the work is and for whom, then its id,
+then a short body, while measurements and `file:line` citations belong to an ADR or the record the
+row points at. A row that goes terminal is DELETED in the same change that mints its closing
+artifact, and where the queue is gitignored the deleted text is first written to a purge archive,
+because there git history is no tombstone. Frozen work with a stated resume condition is not
+terminal and stays, in its own bucket; order inside a bucket IS priority.
+
+The canon names its own rung and the command that runs it, because a prose promise to trim later was
+measured failing — 62 dead rows had accumulated by the time anybody counted.
+
+`references/procedures.md` points at the new section by named anchor and stays the terse pointer it
+is meant to be (its own test asserts it stays smaller than the canon it binds to).
+
 ## 4.0.0 — the scenario floor, and five answers the canon now states at its own points of use (AD-117)
 
 Slice 4 wrote the layer's first real specs and came back with six questions the canon had left for

package/SKILL.md

@@ -3,7 +3,7 @@ name: agent-workflow-engine
 description: Canonical home of the agent-workflow planning methodology — the capped plan shape (goal and boundary, module ledger, verification), plan lifecycle, queue.md series index, mandatory Cleanup phase, the feature-spec canon (the durable per-feature contract layer with its frozen schema and Out-of-scope discipline), 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: '4.0.0'
+  version: '4.1.0'
 ---
 
 # agent-workflow-engine

package/capability.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-engine",
-  "version": "4.0.0",
+  "version": "4.1.0",
   "description": "Canonical home of the agent-workflow planning methodology — the capped plan shape (goal and boundary, module ledger, verification), 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

@@ -118,6 +118,20 @@ plan file, and plan paths inside committed docs, are forbidden.
 and the docs cap-validator is green. An aborted plan still runs Cleanup — partial outputs land in
 `known_issues.md`.
 
+## The queue
+
+`docs/plans/queue.md` NAMES work; it never holds the analysis of it. A row is one plain sentence
+saying what the work is and for whom, then its id, then a short body — measurements, `file:line`
+citations and fix direction belong to an ADR or the record the row points at. A row that goes
+terminal is DELETED in the same change that mints its closing artifact — and where the queue is
+gitignored, the deleted text is first written to a purge archive beside the history docs, because
+there git history is no tombstone. In a hidden deployment that archive is machine-local like the rest
+of the substrate: its guarantee is the working copy, not git. Frozen work with a stated resume
+condition is not terminal and stays, in its own bucket. Order inside a bucket IS priority.
+A prose promise to trim later has been measured failing: a checker over the file is the rung, and it
+is runnable — `node <kit>/tools/queue-audit-cli.mjs --check docs/plans/queue.md --section '<bucket
+heading>' --max-rows <n> --max-row-lines <n>`, declared as a project gate once the queue has migrated.
+
 ## The plan must read cold
 
 The executing session sees the plan file and the repository, never the authoring conversation.

package/references/procedures.md

@@ -38,7 +38,7 @@ Slots: review
    a `create` row and a revision of a governed contract a `modify` row, both written here so they
    exist AT review.
 3. **Self-review** — apply *What gets cut*; fold by code (read and cite the `file:line`); update
-   `queue.md` for a series.
+   `queue.md` for a series, to the shape *The queue* fixes.
 4. **review {recipe}** — Solo (self-review only) / Reviewed (one backend) / Council (both; you
    synthesize), as the resolved `review` recipe selects.
 5. **Fold + loop** — fold every finding and re-review; CLEAN is **0 blockers + 0 majors** from every