@gtrabanco/pi-agentic-workflow 0.35.2 → 0.36.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gtrabanco/pi-agentic-workflow",
-  "version": "0.35.2",
+  "version": "0.36.0",
   "description": "Pi package: canonical agentic-workflow skills, friendly slash commands, and per-command model routing.",
   "keywords": [
     "pi-package",
@@ -58,7 +58,7 @@
   },
   "dependencies": {
     "@gtrabanco/agentic-workflow": "0.5.0",
-    "@gtrabanco/agentic-workflow-schema": "4.8.0"
+    "@gtrabanco/agentic-workflow-schema": "4.9.0"
   },
   "devDependencies": {
     "@types/node": "24.13.3",

package/skills/execute-phase/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: execute-phase
 user-invocable: true
-version: 6.3.1
+version: 6.5.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

@@ -19,8 +19,28 @@ findings end up "solved" locally but absent from the merged PR:
   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
+✓ Sweep declaration EMITTED when the change is token- or claim-shaped — the
+  fixed line below appended to this fold's `## Log` entry (a legacy unit's
+  `## Progress log`). One line per stale form swept, no prose around it, no
+  judgment call: a published vocabulary token, a claim kind, a phrase a
+  surface asserted, a reader/echo pattern. It is the survivors rule with a
+  receipt the gate can re-run:
+
+  ```
+  swept: /<pattern>/<flags> → expected <n> in <glob>
+  ```
+
+  The field shapes and the bounds the gate enforces on them are stated once, in
+  the `sweep-declaration@1` block at the foot of this file — a declaration
+  outside those bounds is **refused, not run**, and the failed claim names which
+  bound tripped. Name the literal stale form, never a program. A fold that
+  changes a token/claim-shaped surface and emits no declaration is a `workflow`
+  finding at review.
 ✓ `bun scripts/promise-coherence.mjs` RUN → `verdict PASS` (the repaired claims
-  reproduce at the head; a skipped line is read, never assumed)
+  reproduce at the head; every declared sweep re-runs to its expected count and
+  an over-bound pattern is refused by name; a skipped line is read, never
+  assumed, and a document whose tally says nothing was machine-checked is not a
+  verified green)
 ✓ 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
@@ -75,3 +95,24 @@ open the PR with `gh pr create` (per the project's Workflow conventions) —
 regardless of the review still to come. The PR body carries the unit doc's
 verification record (its `## Evidence` rows, or a re-cut unit's `## Log` `E`/`G`
 lines) and closes the unit's tracked issues via `Closes #N`.
+
+## The sweep declaration grammar
+
+The one statement of the fields the checklist box names. `scripts/promise-coherence.mjs`
+parses the line and re-runs it; `AGENTS.md`'s `normative-surfaces@1` inventory
+declares this block as the grammar's owner, and the schema package's
+`SWEEP_CLAIM_KINDS` const cites it as its home.
+
+```text
+sweep-declaration@1
+# literal: swept: /<pattern>/<flags> → expected <n> in <glob>
+field | shape | bound the gate enforces
+pattern | /<the stale form as a JS regex body>/ | at most 200 characters; a group that is quantified while its own body is quantified is refused before it is compiled — one such pattern cost 83 s on a 29-character line, and the gate runs the body once per line of the whole `<glob>` corpus
+flags | <a-z, empty allowed> | `g` and `y` are stripped: the gate counts matching lines and carries no lastIndex
+expected | <n> | the survivor count outside the exempt surfaces — normally 0; non-zero only where `<glob>` names the surfaces that legitimately keep the form (the ledger's own quote of the finding, log lines, fixtures)
+glob | <repo-relative scope> | the finding's cited surface plus its inventory-declared siblings, never a repo-wide sweep
+```
+
+Outside a bound the claim fails closed naming which one tripped: a refused
+declaration is a red fold gate, not a warning, and the fold names the literal
+stale form instead.

package/skills/fold-findings/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: fold-findings
 user-invocable: true
-version: 1.9.2
+version: 1.11.0
 argument-hint: [finding-id …]
 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
@@ -167,6 +167,32 @@ cycle. The fold ends when nothing still asserts what is no longer true; state
 in the commit which surfaces the correction swept. Artifact language follows user
 instruction > project docs language > English; conversation language never decides.
 
+**A token- or claim-shaped change carries its sweep declaration.** When the
+fold changes a published vocabulary token, a claim kind, a phrase a surface
+asserted, or a reader/echo pattern, append one fixed line per stale form to
+this fold's `## Log` entry (a legacy unit's `## Progress log`) — the same
+bar as `log-kind@1` and `findings-table@1`: fixed grammar, fixed output, no
+judgment calls:
+
+```
+swept: /<pattern>/<flags> → expected <n> in <glob>
+```
+
+`<pattern>` is the stale form as a JS regex body, `<flags>` its flags (empty
+allowed); `<n>` is the survivor count you expect outside the allowlist —
+normally `0`, and non-zero only where the `<glob>` names surfaces that
+legitimately keep the form (the ledger's own quote of the finding, log lines,
+fixtures). `<glob>` is the bounded scope: the finding's cited surface plus its
+inventory-declared siblings, never a repo-wide sweep. The pattern body carries
+the bounds the gate refuses outside — at most 200 characters, and never a
+quantified group whose own body is quantified — because the gate runs that body
+once per line of the whole `<glob>` corpus, so an over-bound declaration is
+refused by name instead of compiled (`bun
+scripts/promise-coherence.mjs`, node fallback if bun is not installed) re-runs
+every declared grep and fails closed with `sweep-mismatch`, naming
+`file:line`, the regex and the observed count. A fold that changes such a
+surface and emits no declaration is a `workflow` finding at review.
+
 ## Portability (agents other than Claude Code)
 
 Use explicit fallbacks when a primitive is absent: open named `SKILL.md` files in

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

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

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

@@ -77,7 +77,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. 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 |
+| `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 or one of the committed report validators (`scripts/promise-coherence.mjs` names the class), state the outcome it must produce — `` … matches <N> `` or `` … exits <N> `` — because the gate 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; a validator the gate declines to execute is disclosed as a skip naming why, never counted as checked |
 | `required-evidence` | what must be recorded where (test name, receipt line, ledger row) |
 | `status` | `planned \| in-progress \| verified \| n/a \| deferred` |
 

package/skills/review-code/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: review-code
 user-invocable: false
-version: 1.2.0
+version: 1.3.0
 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
 description: >
@@ -43,6 +43,12 @@ default branch. State the scope at the top of the returned table.
   behavior (cite before/after)
 ✓ Reference trace: every changed symbol/API got a reference search —
   un-updated callers are findings
+✓ Sweep declaration present: a changed token- or claim-shaped surface (a
+  published vocabulary token, a claim kind, a phrase a surface asserted, a
+  reader/echo pattern) carries its `swept: /<pattern>/<flags> → expected <n> in
+  <glob>` line on the fold's `## Log` entry — class `workflow`, the project's
+  own survivors rule, and `scripts/promise-coherence.mjs` re-runs it as
+  `sweep-mismatch`
 ✓ Edge cases the SPEC's dev scenarios name are actually handled in code, not
   just in tests