@gtrabanco/pi-agentic-workflow 0.24.4 → 0.26.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gtrabanco/pi-agentic-workflow",
-  "version": "0.24.4",
+  "version": "0.26.0",
   "description": "Pi package: canonical agentic-workflow skills, friendly slash commands, and per-command model routing.",
   "keywords": [
     "pi-package",

package/skills/execute-phase/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: execute-phase
 user-invocable: true
-version: 6.0.0
+version: 6.1.0
 argument-hint: <NN-slug> [P<k>|step] [--max-attempts N] [--force]
 allowed-tools: [Bash, Read, Edit, Write, MultiEdit]
 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"

package/skills/execute-phase/references/FOLDING.md

@@ -15,7 +15,12 @@ when every step below ran — fixing the code and stopping is the classic way
 findings end up "solved" locally but absent from the merged PR:
 
 ```
-✓ Fixes implemented (scope: only the routed findings — nothing extra)
+✓ Fixes implemented — the batch is the routed findings **plus everything that
+  depends on them**: callers of what changes, consumers of what it delivers, and
+  every mention that stops being true (a comment, a prose claim, a declared
+  validator, a manifest narration). Nothing beyond that
+✓ `bun scripts/promise-coherence.mjs` RUN → `verdict PASS` (the repaired claims
+  reproduce at the head; a skipped line is read, never assumed)
 ✓ Gate RUN and green (exit codes pasted)
 ✓ Never edit an existing test's expectation to match behaviour — a setup
   repair keeps assertions at least as strong and never touches expectations

package/skills/init-workspace/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: init-workspace
 user-invocable: true
-version: 4.0.2
+version: 4.0.3
 argument-hint: <target-dir>
 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
@@ -152,9 +152,9 @@ loads exactly upgrade and skips bootstrap plus portability.
 
 The adaptive lane (feature 61) replaces the fixed pipeline with a single-unit-
 document model. Every NEW unit produces one `SPEC.md` under
-`docs/features/<NN>-<slug>/` with 14 sections: Objective, Why, User outcome, Impact,
-Acceptance criteria, Non-goals, Future cost, Applicable tests, Known pre-existing
-issues, Tasks, Evidence, Progress log, Next, References.
+`docs/features/<NN>-<slug>/` with 14 sections: Objective, Why, User outcome, Acceptance criteria, Impact,
+Non-goals, Future cost, Applicable tests, Known pre-existing issues, Tasks,
+Evidence, Progress log, Next, References.
 
 Conventions written into the project's AGENTS.md:
 

package/skills/orchestration-envelope/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: orchestration-envelope
 user-invocable: false
-version: 2.3.0
+version: 2.4.0
 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
 description: >

package/skills/orchestration-envelope/references/TURN_CONTRACT.md

@@ -16,6 +16,14 @@
 ✓ 11. No reconstruction from memory — missing reference → STOP.
 ```
 
+**A box that runs a command discloses what the command needs.** When a box
+invokes a script with a placeholder (`node scripts/x.mjs <unit-dir>`), the same
+skill's text must name the artifact that placeholder requires — the script
+declares it (`PREREQUISITES` in `scripts/needs-input.mjs`) and
+`scripts/promise-coherence.mjs` checks the disclosure. A box that instructs a
+run the skill never equips reproduces the failure it was written to prevent
+(fix #258 F45/F53: `missing-unit-doc`).
+
 **Single owner:** orchestration-envelope/references/TURN_CONTRACT.md. All skills load this + skill-specific additions only. Duplication forbidden. Missing reference = STOP.
 
 **Push policy supplement:** Box 4 covers the end-of-unit push. Some consumers (e.g. `execute-phase/references/PREFLIGHT.md`) define additional push rules for mid-phase commits when a PR is already open — those per-consumer supplements extend this contract and must be loaded alongside it by the consumer skill.

package/skills/pre-execution-review/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: pre-execution-review
 user-invocable: false
-version: 2.7.1
+version: 2.8.0
 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
 description: >

package/skills/pre-execution-review/references/LEDGERS.md

@@ -55,7 +55,7 @@ task | implementation-owner | validator | required-evidence | status
 | `authority-source` | the SPEC/acceptance/criterion or ledger row that *requires* it — never the implementation |
 | `phase` / `task` | exactly one phase and one task; a row needing two phases means the phase cut is wrong |
 | `implementation-owner` | the skill/role that performs it (usually `execute-phase`) |
-| `validator` | the command or check that proves it, copied from the acceptance artifact (`ACCEPTANCE.md` for legacy (pre-feature 61) units; `sed -n '/^## Acceptance criteria/,/^## /p' <unit>/SPEC.md \| git hash-object --stdin` for post-feature 61) or the phase's done-when |
+| `validator` | the command or check that proves it, copied from the acceptance artifact (`ACCEPTANCE.md` for legacy (pre-feature 61) units; `sed -n '/^## Acceptance criteria/,/^## /p' <unit>/SPEC.md \| git hash-object --stdin` for post-feature 61) or the phase's done-when. When it is a backticked reader command, state the outcome it must produce — `` … matches <N> `` or `` … exits <N> `` — because `scripts/promise-coherence.mjs` re-runs it at the head and `verified` is only truthful while it reproduces. A validator with no stated outcome is a claim nobody can check |
 | `required-evidence` | what must be recorded where (test name, receipt line, ledger row) |
 | `status` | `planned \| in-progress \| verified \| n/a \| deferred` |
 
@@ -66,7 +66,9 @@ Status lifecycle and its hard edges:
   follow-up issue.
 - `verified` requires the named validator to have run and its evidence to be
   recorded where `required-evidence` says. An assertion of intent is not a
-  status change.
+  status change. A count or exit code in the validator cell is re-run by
+  `scripts/promise-coherence.mjs`; when the command stops producing it, the row
+  is stale even while it still reads `verified`.
 - `n/a` needs evidence in the row (a `path:line`, ledger row, or cited contract)
   and may never contradict the SPEC's scope section. `n/a` without evidence is
   an open obligation.

package/skills/unit-lane/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: unit-lane
 user-invocable: true
-version: 2.2.0
+version: 2.3.0
 argument-hint: <NN-slug | "<idea>"> [--retriage] | --fix <issue-number> | --from-issue <issue-number>
 description: >
   One-shot lane conductor for a delivery unit: triage, implement, evidence, and

package/skills/unit-lane/references/IMPLEMENT.md

@@ -43,6 +43,12 @@ its work landed in the unit doc before continuing:
 - [ ] Each executor turn recorded its Evidence row and dated Progress entry
 - [ ] Diff guard run at the lane's resume (see step 4 in SKILL.md)
 - [ ] `git status --porcelain` is empty when the lane resumes
+- [ ] Each phase swept the change **plus everything that depends on it** —
+      callers of what changed, consumers of what it delivers, and every mention
+      that stops being true; a surviving mention is part of the same phase, not
+      a finding for the next review
+- [ ] `bun scripts/promise-coherence.mjs` RUN at the lane's resume → `verdict
+      PASS` (the unit doc's declared validators reproduce at the head)
 
 ## Allowed
 

package/skills/verification-contract/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: verification-contract
 user-invocable: false
-version: 1.4.2
+version: 1.4.3
 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
 description: >
@@ -17,6 +17,16 @@ description: >
 Single owner of the delivery finish line. Planning freezes it; executors may
 strengthen coverage but cannot move it; review checks the same bytes.
 
+## Executable claims
+
+An acceptance criterion or Evidence row that states a count, an exit code or a
+length is a promise, not a description: `scripts/promise-coherence.mjs` re-runs
+it. Write the outcome a command must produce (`` `cmd` matches <N> ``,
+`` `cmd` exits <N> ``) or, for a shape promise, name the file and the
+`## Section` the count is about (`` … a 3–5 line `## Inputs` in
+`skills/<name>/SKILL.md` ``) — a length with no named surface cannot be recounted
+and fails closed.
+
 ## Artifact
 
 Legacy (pre-feature 61) units (ACCEPTANCE.md present — binding if present):