@gtrabanco/pi-agentic-workflow 0.13.3 → 0.14.0

package/skills/ship-roadmap/references/STOP_CONDITIONS.md

@@ -1,9 +0,0 @@
-### Stop conditions
-
-| Banner | Fires when |
-|---|---|
-| `SHIP: COMPLETE` | Every roadmap feature is `done` **and its PR merged** (default mode: the human merged them all; `--fullauto`: merged under the floors) — `done` alone is not enough, since it only means *built + PR open* — **AND the issue sweep ran to completion**: existing issues inventoried/triaged, every fix-now issue shipped or parked, and untracked residue deduplicated as report proposals without creating backlog. Features merged but sweep pending → the run is NOT complete. Report written, report PR open. |
-| `SHIP: BLOCKED` | Everything remaining is `done`-but-pr-open awaiting human merges, or planned with unmerged deps (default mode); or a parked feature transitively blocks the rest. Always includes the unblock map. |
-| `SHIP: STOPPED` | Budget/iteration cap; a Round-5 milestone stop line; substrate invariant broken (gate unrunnable, roadmap unparseable, unexplained dirty default branch, decision record missing); forge unavailable (no stage that depends on PR state may proceed on guesses). |
-| (feature parked, run continues) | Repeated red gate (retry cap), review ping-pong (2 cycles), audit ping-pong (2 cycles), capacity guard (3 partials), planning contradiction, **undesignable-from-record** (DESIGN stage `NEEDS_INPUT` — the recorded gap is a human-only unpark, never a mid-run re-ask). |
-| **Systemic drift stop** | `review-change` flags SPEC drift on **two consecutive features** → the locked founding assumptions are probably stale; the whole run stops rather than auto-merging a compounding error. |

package/skills/ship-roadmap/references/TERMINAL_REPORT.md

@@ -1,34 +0,0 @@
-### Final report
-
-Written by the terminal iteration to `docs/features/SHIP_REPORT_<date>.md` on a
-`docs/ship-report` branch as a docs-only PR (default: human merges; `--fullauto`:
-audit-gated like any PR), and printed in full under the banner:
-
-1. **Run summary** — mode, iterations used vs cap, stop reason, feature counts
-   (merged / `done`-awaiting-merge / parked / not started).
-2. **Per-feature outcomes** — size planned vs final, phases, gate history,
-   review findings folded vs postponed, audit verdict + SHA, PR + final state,
-   merged by human or autopilot.
-3. **Issues** — the sweep's existing-issue inventory and outcomes: fix-now issues
-   shipped (PR links), postponed/wontfix verdicts with the trigger that
-   should reopen each (feeds `triage-issue`'s verification model), and
-   anything the sweep could not finish (budget/parked) as the explicit
-   remaining triage batch. Untracked residue is listed separately as proposals;
-   the run created no backlog for it.
-4. **New feature proposals** — capabilities discovered during the build that
-   serve the product goal (Round 1 quoted as the yardstick), each sized with a
-   suggested roadmap slot. Recommend-only.
-5. **Residual risks** — weak test areas, `--fullauto` merges deserving a second
-   look, parked features and why, silent decisions with outsized consequences.
-6. **Manual-verification checklist** — the deduplicated union of every review
-   checkpoint's manual checks plus audit notes: what no gate proved.
-7. **Going forward** — concrete `product-audit` cadence for this project
-   (first one now if ≥2–3 features merged; then ~every 5 or pre-release), and
-   the suggested command sequence to continue, closed with the canonical block:
-
-   ```
-   → Next: <merge the open PRs | /triage-issue <batch> | /plan-feature --next>
-     · accepted proposals → /plan-feature   · product-audit due → /product-audit
-   ```
-
-Closing line, verbatim policy: **this report recommends; the human decides.**