@gtrabanco/pi-agentic-workflow 0.11.2 → 0.13.1

package/skills/review-spec/references/CHECKS.md

@@ -101,5 +101,8 @@ Each finding is one row of the receipt's `findings` array: stable `id`,
 source | environment | runtime`), `claim` (what is wrong, with the section
 pointer), `evidenceRefs` (≥ 1 — a finding without evidence is a hunch and gets
 dropped), `verification` (`verified | unverified`), `resolution` (`open` on
-emission). Material = anything above `info`; a `PASS` may not carry an open or
+emission). Material = `medium` and above; a `low` row is a persisted report-note
+the stage author resolves without a re-review, and `info` is immaterial.
+Deflating a real defect below the `medium` minimum to unblock a pass is itself a
+finding; a `PASS` may not carry an open or
 unverified material row.

package/skills/review-spec/references/OUTPUT.md

@@ -106,8 +106,8 @@ not authority.
 | Verdict | Who repairs | What happens next |
 |---|---|---|
 | `SPEC-REVIEW-PASS` | nobody | `/plan-feature <NN-slug>` binds this receipt + exact snapshot digest |
-| `SPEC-REVIEW-FAIL` | `design-feature` (the author) | one root-caused repair batch → new revision → re-review of the new snapshot |
-| `NEEDS-DESIGN` | the human, through `design-feature` | dated `## Amendments`/`Product decisions` entry → new revision → re-review |
+| `SPEC-REVIEW-FAIL` | `design-feature` (the author) | one root-caused repair batch → new revision → next cycle (default re-review; a recorded wording-only batch skips it) |
+| `NEEDS-DESIGN` | the human, through `design-feature` | dated `## Amendments`/`Product decisions` entry → new revision → next cycle |
 
 A finding whose `class` is `plan`, `source`, `environment`, or `runtime` does not
 become work here: record it, keep it open, and route it to its owner (`review-plan`
@@ -117,8 +117,11 @@ schedules nothing.
 Repeating this review follows the no-progress and convergence rules in
 `pre-execution-review/references/POLICY.md` §4: a repeat needs a
 changed snapshot or a named falsifiable question plus a new evidence route, and
-entering a second repair/re-review cycle prints `CONVERGENCE-ANOMALY` before any
-further edit. A `design-feature` repair turn re-reads the union of open findings
+a second consecutive repair/re-review cycle prints `CONVERGENCE-ANOMALY` before
+any further edit. A third cycle never starts without explicit user instruction:
+the orchestrator's `stop-review-loop-cap` refusal stops the invocation and names
+`design-feature` as the human route, and a PASS resets the count. A
+`design-feature` repair turn re-reads the union of open findings
 from `planning-findings.md`, not just the newest receipt, so nothing recorded here
 is ever lost between cycles.
 
@@ -150,7 +153,8 @@ On FAIL or NEEDS-DESIGN, name every finding id once, in order, joined with ` + `
 
 ```
 → Next: /design-feature <NN-slug> "<instruction>" — one repair batch for F1 + F2 + F4,
-    then /review-spec <NN-slug> re-reviews the new artifact revision
+    then /review-spec <NN-slug> judges the new artifact revision
+  · a third cycle → explicit user instruction first; the decider refuses it (`stop-review-loop-cap`) and names design-feature
   · a product choice is missing → answer it in the instruction; nothing here chooses for you
   · finding class is plan/source/environment/runtime → route to its owner, do not edit the SPEC
 ```

package/skills/review-verify/SKILL.md

@@ -2,7 +2,7 @@
 name: review-verify
 user-invocable: false
 version: 1.1.0
-author: "Gabriel Trabanco <gtrabanco@users.noreply.github.com>"
+author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
 description: >
   Internal run-it verification review pass of the agentic-workflow review pack —

package/skills/triage-issue/SKILL.md

@@ -3,7 +3,7 @@ name: triage-issue
 user-invocable: true
 version: 2.8.0
 argument-hint: <issue-number> [more issue numbers…] | <audit-id> F<k> [F<j>…] | --prioritize-now <unit> F<k> [F<j>…]
-author: "Gabriel Trabanco <gtrabanco@users.noreply.github.com>"
+author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
 description: >
   Verify an issue, persisted audit finding, or unresolved review finding against

package/skills/verification-contract/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: verification-contract
 user-invocable: false
-version: 1.2.1
-author: "Gabriel Trabanco <gtrabanco@users.noreply.github.com>"
+version: 1.3.0
+author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
 description: >
   Internal contract: one compact frozen ACCEPTANCE.md per delivery unit, its
@@ -88,6 +88,12 @@ a cover-up. The sole legitimate amendment is a **proven mis-encoding of external
 documented semantics of the platform/library/language, cited from authoritative documentation — not a product decision change. Even that surfaces as a
 **finding plus a SPEC amendment**, never a silent edit to go green.
 
+The deterministic backstop for this rule is the feature 60 path-protection
+checkpoint (`path-protection@1` in the turn contract): the Tier 1 gate fails a
+protected-path change with no recorded justification/approval, and the pi guard
+blocks the write before it lands. This manifest is the finish line those
+recorded escapes are checked against.
+
 Prevention rides the research gate (**research-before-encode**): platform
 semantics are verified against authoritative documentation **before a test encodes them**, so **adding stronger tests stays allowed**; **editing expectations never** (except the proven-mis-encoding path above).
 

package/skills/workflow-status/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: workflow-status
 user-invocable: true
-version: 3.7.0
-author: "Gabriel Trabanco <gtrabanco@users.noreply.github.com>"
+version: 3.8.1
+author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>"
 license: MIT
 argument-hint: "[--json-only] [--last-envelope <json|path>]"
 description: >

package/skills/workflow-status/references/ENVELOPE_CORE.md

@@ -9,10 +9,11 @@ placement per the installed `orchestration-envelope` skill. The
 states** (the schema package needs no release):
 
 - `CLEAN` → `state: OK` (the sensor default when the substrate is usable).
-- A missing or non-frozen repository-state ledger is a run-scoped substrate
-  gate and overrides the crash-recovery state with `state: BLOCKED`; the
-  blocker and concrete discovery/resolution command are emitted before
-  readiness data.
+- `draft`, `contradicted`, or `resolved` repository-state ledger is a
+  run-scoped substrate gate and overrides the crash-recovery state with
+  `state: BLOCKED`; the blocker and concrete discovery/resolution command
+  are emitted before readiness data.
+  An absent ledger is a non-blocking notice, not a blocker.
 - `RESUMABLE` → `state: CONTINUE`, `next.recommended` = the resume command
   from the decision table.
 - `AMBIGUOUS` → `state: NEEDS_INPUT`, `needs_input.question` = what is

package/skills/workflow-status/references/SENSOR_CORE.md

@@ -12,12 +12,13 @@ the JSON and interprets it.
 
 Read `docs/workflow/REPOSITORY_STATE.md` when present and always emit
 `detail.repository_state: {status, snapshot_id, source_revision}`. Before
-readiness classification, if the ledger is missing, `draft`, `contradicted`, or
+readiness classification, if the ledger is `draft`, `contradicted`, or
 `resolved`, add a run-scoped `substrate` blocker, set the envelope state to
 `BLOCKED`, leave `startable_now` empty, and set `next.recommended` to
-`/discover-repository-state` for missing/non-frozen state or
-`/resolve-repository-state <contradiction-id>` for `contradicted` state. The
-sensor remains read-only; it never edits or resolves the ledger. Conflicting
+`/discover-repository-state` for non-frozen state or
+`/resolve-repository-state <contradiction-id>` for `contradicted` state.
+An absent ledger emits a non-blocking substrate notice instead of a blocker.
+The sensor remains read-only; it never edits or resolves the ledger. Conflicting
 live evidence against a frozen ledger remains a contradiction candidate.
 
 3. **Urgency labels (`detail.urgent`) — labels-only, presence-only, never

package/skills/workflow-status/references/SENSOR_SIGNALS.md

@@ -83,8 +83,9 @@ mechanized.*
 
     A row is **open** under the router's own predicate (`scripts/unit-route.mjs`
     `isOpen`), never a re-derived one: `folded: yes`, `—`, `-`, `n/a` and an empty
-    cell all close it. The id shapes `VF-<n>` (a finding's verification mark) and
-    `REVIEW-RAN` (a review mark) are **never** findings — a ledger pads a mark row
+    cell all close it. The id shapes `VF-<n>` (a finding's verification mark),
+    `REVIEW-RAN` (a review mark) and `GATE-RAN` (a gate-run mark) are **never**
+    findings — a ledger pads a mark row
     with empty cells, so it reaches the row parser looking like an open finding and
     would otherwise project a suggestion for a merged unit. A **decision-required**
     open row contributes **nothing**: it outranks the fold in the route table (which