task-pipeline-skill 1.6.0 → 1.7.0

package/plugins/task-pipeline/skills/task-pipeline/templates/retro.md

@@ -4,8 +4,10 @@ One file per project, not per run. Written as the **last act of stage 10**:
 prune first, then stamp, then write an entry **only if the run diverged**.
 Doctrine: `references/retrospective.md`.
 
-Stage 0 reads *Standing instructions* in full, every run — which is why the list
-has a hard cap of **ten**.
+**What stage 0 reads in full:** *Standing instructions*, *Run stamps* and *Recent
+log* — all three are bounded by construction, which is why the cap is not
+negotiable. The **archive** (`docs/superpowers/retro/YYYY-QN.md`) is *queried* by
+the task's nouns and never read end to end.
 
 ## Standing instructions (max 10 — in force right now)
 
@@ -13,18 +15,25 @@ Every row is a rule an agent must follow, that **no check can decide**. A rule a
 check *can* decide is not written here: it is written as the check (grade 1).
 No row is accepted without its **retire-when** trigger, written at birth.
 
-| id | Born | Instruction | Because (incident) | Retire when | Last fired |
-|---|---|---|---|---|---|
-| R-001 | 2026-05-04 · `<topic>` | … | … (one line, links the log entry) | … (e.g. "the export path is covered by a test") | 2026-06-18 |
+Two SHA columns, and they are not bookkeeping: a `file:line` rots at the next edit,
+while `git show <sha>` reconstructs the whole incident months later. Every SHA here
+must resolve — the documentation gate runs `git rev-parse --verify` over all of
+them.
+
+| id | Born | Commit | Instruction | Because | Retire when | Last fired | Fired at |
+|---|---|---|---|---|---|---|---|
+| R-001 | 2026-05-04 · `<topic>` | `<sha>` | … | … (one line; links the archive entry) | … (e.g. "the export path is covered by a test") | 2026-06-18 | `<sha>` |
 
 Retire on **any** of: it became a check · every path/command it names is gone · it
 has not fired in the last five run stamps. At eleven rows, the oldest never-fired
 row goes — the cap is not negotiable, ranking is.
 
-## Log — problem → cause → fix (newest first)
+## Recent log — entries from the last five run stamps (newest first)
 
-Retirements are logged here too, one line each: *silent deletion is forbidden; the
-record stays, the instruction leaves.*
+Older entries and every retirement **move** to `docs/superpowers/retro/YYYY-QN.md`
+at the prune. Moving is not deleting: the archive is append-only and holds the
+incident forever, so pruning the in-force list costs no knowledge. This section
+stays short precisely so that reading it in full at stage 0 stays cheap.
 
 ### 2026-05-04 · `<topic>` · gate 6 reopened twice
 
@@ -35,17 +44,22 @@ record stays, the instruction leaves.*
 - **Fix:** grade 1 (mechanical) — … / grade 2 → `R-00N` / grade 3, expires in
   2 runs
 - **The check:** … (what catches this the first time, from now on)
+- **Commit:** `<sha>` — the change that fixed it
 - **Upstream?** … (a lesson true in any repo belongs in the skill's own
   `references/learned.md` — open an issue and say so here)
 
-### 2026-05-04 · retired R-000 — became a check (`npm run lint:paths`)
+### 2026-05-04 · retired R-000 — became a check (`npm run lint:paths`) · `<sha>`
 
 ## Run stamps
 
 One line per run, appended at stage 10. This is what makes "five runs" countable
 — without it the cold-rule is a guess and the prune becomes a mood.
 
-| Date | Topic | Verdict | Retro |
-|---|---|---|---|
-| 2026-05-04 | `<topic>` | 14/14 verified | 1 entry · 7 standing (was 9) · retired 3 · added 1 |
-| 2026-05-02 | `<topic>` | 9/9 verified | no divergence · 9 standing · retired 0 |
+| Date | Topic | Commit | Verdict | Retro |
+|---|---|---|---|---|
+| 2026-05-04 | `<topic>` | `<sha>` | 14/14 verified | 1 entry · 7 standing (was 9) · retired 3 · added 1 |
+| 2026-05-02 | `<topic>` | `<sha>` | 9/9 verified | no divergence · 9 standing · retired 0 |
+
+The `Commit` column is what turns a stamp from a date into a navigable point in
+history: `git show <sha>` is the run, and `git log <sha>..HEAD` is everything that
+happened since a rule last fired.