task-pipeline-skill 1.51.0 → 1.53.0

package/plugins/task-pipeline/skills/task-pipeline/references/learned.md

@@ -208,7 +208,7 @@ answer would have exposed it in a minute.
 **This file is the shipped list; a project keeps its own.** Every rule in the table
 above was earned on someone else's build and travels with the skill. The lessons *your*
 project buys go in its retro ([`retrospective.md`](retrospective.md) →
-`docs/superpowers/retro.md`), where they are capped, pruned and retired — and a
+`<artifacts>/retro.md`), where they are capped, pruned and retired — and a
 lesson there that would be true in any repository belongs here instead, as an issue
 upstream. A local file that accumulates universal rules is a fork of this one that
 nobody named.
@@ -217,7 +217,7 @@ nobody named.
 
 ## What leaves this file, and why there is no cap
 
-`docs/superpowers/retro.md` caps its standing instructions at **ten** and retires them
+`<artifacts>/retro.md` caps its standing instructions at **ten** and retires them
 on three triggers. Somebody proposes the same cap here about once a programme. It is
 the wrong instrument, and the reason is worth more than the rule.
 

package/plugins/task-pipeline/skills/task-pipeline/references/planning.md

@@ -28,7 +28,7 @@ this toolset, has questionable taste, and will read **only their own task**.
 Everything they need is in that task: exact paths, complete code, exact commands,
 expected output. DRY. YAGNI. TDD. Frequent commits.
 
-Path: `docs/superpowers/plans/YYYY-MM-DD-<topic>.md` — same `<topic>` slug as the
+Path: `<artifacts>/plans/YYYY-MM-DD-<topic>.md` — same `<topic>` slug as the
 brief and the spec.
 
 ## Before writing tasks
@@ -84,7 +84,7 @@ commit.
 
 **Tech stack:** <key technologies>
 
-**Spec:** docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md
+**Spec:** <artifacts>/specs/YYYY-MM-DD-<topic>-design.md
 
 ## Global constraints
 

package/plugins/task-pipeline/skills/task-pipeline/references/portability.md

@@ -18,7 +18,7 @@ one repository, or a skill that has quietly learned one project's answers.
 | Kind of decision | Example | Lives in | Travels? |
 |---|---|---|---|
 | **Workflow** — how the pipeline behaves anywhere | the gate types, the loop-guard caps, the Doc Loop's seven steps, the escalation rule, the routing boundary | `references/*.md`, `templates/*`, `pipeline.example.json` | **yes — this is the bundle** |
-| **Project answer** — what *this* repository decided | which register it uses, its propagation matrix, its ratchet floors, its standing instructions | `docs/DOCMAP.md`, the register, `docs/superpowers/retro.md`, the brief | **no — and correctly so** |
+| **Project answer** — what *this* repository decided | which register it uses, its propagation matrix, its ratchet floors, its standing instructions | `docs/DOCMAP.md`, the register, `<artifacts>/retro.md`, the brief | **no — and correctly so** |
 
 Two failures follow from confusing them, and they look nothing alike:
 

package/plugins/task-pipeline/skills/task-pipeline/references/progress.md

@@ -31,6 +31,7 @@ maintains them and the next run reads them as current.
 - Absent is a word, never a zero
 - The `holds:` line — what the run is still holding
 - The observation beside the claim
+- The run's own lifecycle
 - The run ledger this reads from
 - Rationalizations
 
@@ -84,7 +85,7 @@ Emitted at the **close** of every iteration, one line:
 **`next` cites a `B-NNN`, never a description.** That rule is
 [`continuity.md`](continuity.md)'s and it is the reason this line exists at all:
 *"next up is X"* was already the one sentence in a loop that no gate reads. A board id
-can be checked against `docs/superpowers/backlog.md`; *"next up: the export fix"*
+can be checked against `<artifacts>/backlog.md`; *"next up: the export fix"*
 cannot.
 
 **Nothing queued is `next —`, printed.** A loop that reaches an empty board says so;
@@ -254,9 +255,9 @@ run reports a state nobody agreed to read.
 
 | Field | Its home |
 |---|---|
-| `board B-NNN` | `docs/superpowers/backlog.md` ([`backlog.md`](backlog.md)) |
+| `board B-NNN` | `<artifacts>/backlog.md` ([`backlog.md`](backlog.md)) |
 | `carry-over N rows` | the run's carry-over ledger, as printed beside every gate verdict |
-| `exposure N never` | `docs/superpowers/verification.md` ([`exposure.md`](exposure.md)) |
+| `exposure N never` | `<artifacts>/verification.md` ([`exposure.md`](exposure.md)) |
 | `unlooked N` | the gate's own disclosure ([`gates.md`](gates.md) → *Disclosures*) |
 | `gates N/M` | the run ledger's verdict rows, and `pipeline.json` → `stages[]` |
 
@@ -336,6 +337,20 @@ written from memory is a summary that is confidently wrong exactly when it matte
 a gate that reads a verdict typed by the agent it constrains is the same shape
 again, and it looks like enforcement while being a mirror.
 
+## The run's own lifecycle
+
+Three moments the rail cannot show, recorded by `hooks/run-lifecycle.sh` as
+
+```
+event: <compact|session-end|subagent> — <detail> — <ISO-8601>
+```
+
+The rail reads none of them; `checkup` reads `session-end`, which is how an
+abandoned run stops being invisible. Before this the ledger simply stopped at
+whatever stage the session died on — and a stopped ledger is indistinguishable
+from a run still in progress, which is the exact shape *absent is a word, never a
+zero* exists to refuse.
+
 ## The run ledger this reads from
 
 `.task-pipeline/run.md`, seeded at stage 0 from

package/plugins/task-pipeline/skills/task-pipeline/references/retrospective.md

@@ -18,9 +18,9 @@ justifies reading it protects one section while the file below it doubles.
 
 | Artifact | Parts | How it is read |
 |---|---|---|
-| `docs/superpowers/retro.md` — **one per project** | **Standing instructions** (max **10**) · **Run stamps** (max **10**, oldest rotate out) | stage 0, **in full** — both are bounded by a **cap**, which *one line each* never was |
+| `docs/evidence/retro.md` — **one per project** | **Standing instructions** (max **10**) · **Run stamps** (max **10**, oldest rotate out) | stage 0, **in full** — both are bounded by a **cap**, which *one line each* never was |
 | the same file's **Recent log** | entries from the last five run stamps — narrative, and capped by nothing | stage 0, **queried** by the task's nouns. It said *in full* until 2026-08-10, when it measured **74%** of the file: an uncapped section inside a binding source is what makes the capped part get skimmed |
-| `docs/superpowers/retro/YYYY-QN.md` — the archive | every entry and every retirement ever written, append-only | **queried** by the task's nouns; never read end to end |
+| `docs/evidence/retro/YYYY-QN.md` — the archive | every entry and every retirement ever written, append-only | **queried** by the task's nouns; never read end to end |
 
 Seed the archive from [`../templates/retro-archive.md`](../templates/retro-archive.md).
 
@@ -97,7 +97,7 @@ the neighbour's growth is *tidy*. A tidy slope is still a slope.
 **The cap is ten and the trigger is why.** The cold rule reads *the last five run
 stamps*; ten is that with a margin, so a stamp rotating out can never be one the trigger
 needed. At the eleventh, the oldest row moves — whole, with its verdict and its retro
-column — into `docs/superpowers/retro/YYYY-QN.md` under `## Run stamps`, append-only,
+column — into `docs/evidence/retro/YYYY-QN.md` under `## Run stamps`, append-only,
 like every other rotation. **The count is printed at the prune**, beside the standing
 instructions' own count, so a table that stops rotating is visible rather than merely
 large.
@@ -141,7 +141,7 @@ this line existed it still had no way to say it never ran.
 ## Rotation — the archive is how pruning stops losing things
 
 At the prune, entries older than the last five run stamps **move** to
-`docs/superpowers/retro/YYYY-QN.md`. Moving is not deleting.
+`docs/evidence/retro/YYYY-QN.md`. Moving is not deleting.
 
 - The archive is **append-only**, and a retirement writes its line **there**, with
   the trigger that retired it and the commit.
@@ -187,7 +187,7 @@ performable was queued behind it.
 computable, which is why it goes first:
 
 ```bash
-printf '%s · %s\n' "$(date +%F)" "$(git rev-parse --short HEAD)" >> docs/superpowers/retro.md
+printf '%s · %s\n' "$(date +%F)" "$(git rev-parse --short HEAD)" >> docs/evidence/retro.md
 ```
 
 ## The prune — mandatory, and it runs after the stamp
@@ -217,10 +217,10 @@ grep -oE '`[^`]+`' <<<"$RULE_TEXT" | tr -d '`' | while read -r t; do
   [ -e "$t" ] || command -v "$t" >/dev/null || echo "MISSING: $t"; done
 
 # went cold — fired in none of the last five stamps
-tail -n 200 docs/superpowers/retro.md | grep -c "$RULE_ID"
+tail -n 200 docs/evidence/retro.md | grep -c "$RULE_ID"
 
 # ...OR in the last 60 days, whichever comes first — see below for why both
-git log -1 --format=%cd --date=short -S"$RULE_ID" -- docs/superpowers/retro.md
+git log -1 --format=%cd --date=short -S"$RULE_ID" -- docs/evidence/retro.md
 ```
 
 Anything the first two print is a deletion; a zero from the third **or** a last-fired date more
@@ -247,7 +247,7 @@ retro counts:
 
 ```bash
 git tag --sort=-v:refname | head -1                    # newest release
-grep -m1 -oE '`[0-9a-f]{7,}`' docs/superpowers/retro.md # newest stamped commit
+grep -m1 -oE '`[0-9a-f]{7,}`' docs/evidence/retro.md # newest stamped commit
 ```
 
 Then the cap: **ten standing instructions, hard.** At eleven you do not get to keep

package/plugins/task-pipeline/skills/task-pipeline/references/setup.md

@@ -12,6 +12,7 @@ is recorded in the brief's autonomy sweep and never asked again.
 ## Contents
 
 - When it runs
+- First it says where the paperwork lives
 - What it inspects
 - The finding shape
 - The output is a fix plan, not a lecture
@@ -31,6 +32,28 @@ is recorded in the brief's autonomy sweep and never asked again.
 **Never as a recurring tax.** A check that runs before every feature is a check people
 learn to dismiss. Once per project state, then it is the gate's job.
 
+## First it says where the paperwork lives
+
+Before any pass, one line naming **the resolved artifact root and why it resolved that
+way** ([`artifacts.md`](artifacts.md) → *the root is resolved, not spelled*). Not a
+finding — orientation, and the answer to the only question a rename can leave behind:
+
+```
+artifacts: docs/superpowers/   (legacy name, resolved because the directory exists and
+                                carries a register — the default is now docs/evidence/,
+                                and moving is optional: npx task-pipeline
+                                migrate-artifacts --dry-run)
+artifacts: docs/evidence/      (default)
+artifacts: docs/runs/          (configured — pipeline.json → paths.artifacts)
+artifacts: docs/evidence/      (default, and the directory already exists without a
+                                register — STOP AND ASK before writing into it)
+```
+
+A project on the legacy name is **not behind and is never warned about it on a run**;
+this line exists so nobody has to guess which of the two directories a gate will read.
+Where records sit in both, the leftover is named here too — a partial migration is a
+state somebody chose, not a fault.
+
 ## What it inspects
 
 Seven passes, cheapest first. Each either reports `ok`, a finding, or **`skipped —
@@ -75,7 +98,7 @@ of the project's own process is leaking.
 
 ## The output is a fix plan, not a lecture
 
-The audit ends with `docs/superpowers/plans/YYYY-MM-DD-doc-audit.md` — the findings
+The audit ends with `<artifacts>/plans/YYYY-MM-DD-doc-audit.md` — the findings
 turned into tasks the pipeline can run, in the order that makes them terminate:
 
 1. everything the gate can enforce **after** the fix, so the class stops recurring;

package/plugins/task-pipeline/skills/task-pipeline/references/spec.md

@@ -67,7 +67,7 @@ entered from super-ux), verify it and embed it; build only what's missing.
 
 ## Write the spec
 
-Path: `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`, committed, **same
+Path: `<artifacts>/specs/YYYY-MM-DD-<topic>-design.md`, committed, **same
 `<topic>` slug as the brief** so brief → design → plan is traceable at a glance.
 (The directory name is this pipeline's historical convention, not a dependency on
 anything; a host project may relocate the root via its `CLAUDE.md` — keep the

package/plugins/task-pipeline/skills/task-pipeline/references/stages.md

@@ -101,7 +101,7 @@ never that the work was skipped quietly.
   when one is built ([`knowledge-graph.md`](knowledge-graph.md): `graphify query` /
   `affected` / `god-nodes` answer *reach*, which is what grep cannot), `CLAUDE.md`,
   `CONTEXT.md`/ADRs, `docs/` + `docs/ux/`, past pipeline briefs and carry-over
-  ledgers, **the retro's standing instructions and run stamps** (`docs/superpowers/retro.md`,
+  ledgers, **the retro's standing instructions and run stamps** (`<artifacts>/retro.md`,
   read **in full** — ten standing rows and ten stamps, both bounded **by a cap**, and they bind this
   run; stamp each instruction as it fires. Its *Recent log* is **queried** by the
   task's nouns, not read: uncapped narrative inside a binding source is what makes the
@@ -185,7 +185,7 @@ never that the work was skipped quietly.
   now (use it if installed; otherwise give the install line — see SKILL.md
   *Prerequisites*); this arms the stage-3 UX track.
 - **Artifact:** lock the resolved decisions into a **task brief** committed at
-  `docs/superpowers/specs/YYYY-MM-DD-<topic>-brief.md` (scope, users/UI verdict,
+  `<artifacts>/specs/YYYY-MM-DD-<topic>-brief.md` (scope, users/UI verdict,
   constraints, assumptions, explicitly-deferred items, done-criteria) **plus the
   autonomy sweep's per-stage answers and the model decision**. Seed it from
   the skill's `templates/brief.md` skeleton — but only when absent, never
@@ -213,7 +213,7 @@ never that the work was skipped quietly.
   confirms the brief. Stop when a
   re-scan surfaces no new branches (don't grill past diminishing returns;
   reversible calls can be deferred with a note). Only then start stage 1.
-- **The verification ledger is read.** `docs/superpowers/verification.md` — the harvest
+- **The verification ledger is read.** `<artifacts>/verification.md` — the harvest
   quotes **how many rows sit at `never`**, because that is the project's standing
   exposure and stage 0 is where it is cheapest to look ([`verification.md`](verification.md)).
 - **The run ledger is seeded and the header block is printed** — in that order, before
@@ -224,7 +224,7 @@ never that the work was skipped quietly.
   [`progress.md`](progress.md) derives the rail and the iteration counter from the
   `stage:` and `iter:` lines. The header goes out before the interview because a run
   that announces its position only at the end announced it to nobody.
-- **The board is read, or seeded.** `docs/superpowers/backlog.md` ([`backlog.md`](backlog.md)) — its **open count is quoted in the brief**, measured by a command at the top of the run rather than inherited from the last run's report. Absent ⇒ seeded from the template and said so; an empty board and no board are the same thing to work on, and only one of them can be appended to.
+- **The board is read, or seeded.** `<artifacts>/backlog.md` ([`backlog.md`](backlog.md)) — its **open count is quoted in the brief**, measured by a command at the top of the run rather than inherited from the last run's report. Absent ⇒ seeded from the template and said so; an empty board and no board are the same thing to work on, and only one of them can be appended to.
 
 ## 1 — Docs study
 - **Freedom: medium** — which sources to fetch is judgement; grounding contracts on fetched docs is not ([`gates.md`](gates.md) → *Axis C*).
@@ -339,7 +339,7 @@ never that the work was skipped quietly.
   so a run designed a flow, then wrote its strings by taste and picked its values at the
   keyboard — and every gate in the pipeline reported green over both.
 - **Spec:** write the approved design to
-  `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` and commit it. Lock all
+  `<artifacts>/specs/YYYY-MM-DD-<topic>-design.md` and commit it. Lock all
   shared contracts (types, schemas, signatures, file layout). For UI tasks the
   spec **embeds the UX layer**: links the validated scenario IDs, the flows and
   `SCR-` screens, the CJM stages the feature serves, and the UX
@@ -366,7 +366,7 @@ never that the work was skipped quietly.
 ## 4 — Plan
 - **Freedom: low** — the task format is prescribed and the REQ set-comparison is mechanical ([`gates.md`](gates.md) → *Axis C*).
 - **How it runs: [`planning.md`](planning.md)** — built into this skill →
-  `docs/superpowers/plans/YYYY-MM-DD-<topic>.md` (same slug as the brief and the
+  `<artifacts>/plans/YYYY-MM-DD-<topic>.md` (same slug as the brief and the
   spec). Zero-context tasks, exact
   paths, complete code in every step, TDD steps with expected output, DoD each,
   dependency graph + parallel groups, non-overlapping file ownership, and the
@@ -510,7 +510,7 @@ never that the work was skipped quietly.
   its run id** — "CI is green" written without a command behind it prints the same
   whether it looked or not ([`gates.md`](gates.md) → *False success*).
 - **Write the verification row.** One line per REQ this run shipped, into
-  `docs/superpowers/verification.md` ([`verification.md`](verification.md)) — the run,
+  `<artifacts>/verification.md` ([`verification.md`](verification.md)) — the run,
   the tag or commit it went out in, what the gate said, and `Human: never` unless the
   operator confirmed during the run. The verification above already happened; this is
   the only step that makes it answerable **later**, and `never` is a fact rather than a
@@ -581,7 +581,7 @@ never that the work was skipped quietly.
   brief carries.** Both directions: a shipped feature that entered no ledger and a
   ledger row about nothing are different failures ([`verification.md`](verification.md)).
 - **The ledger's open rows are resolved onto the board.** Every carry-over row still
-  `open` leaves with a `B-NNN` id on `docs/superpowers/backlog.md`, and the ledger row
+  `open` leaves with a `B-NNN` id on `<artifacts>/backlog.md`, and the ledger row
   is updated to name it ([`backlog.md`](backlog.md)). Both directions, because they are
   different failures: a ledger row pointing at an id nobody issued, and a board row
   traceable to nothing. Measured before this was built: across the ledgers in
@@ -613,7 +613,7 @@ never that the work was skipped quietly.
 - **How it runs:** built in. Read the brief's REQ table, the carry-over ledger in
   full, the plan's task statuses, git log, the final suite output, stage-8 notes and
   stage-9 doc changes (plus `docs/ux/scenarios.md` + `/ux-lint` for UI tasks). Write
-  `docs/superpowers/specs/YYYY-MM-DD-<topic>-acceptance.md` — one row per REQ,
+  `<artifacts>/specs/YYYY-MM-DD-<topic>-acceptance.md` — one row per REQ,
   status `verified` / `partial` / `deferred` / `dropped`, each with **evidence** (a
   passing test name, `file:line`, a command and its output, or a scenario ID).
   "Done" without evidence is not done: downgrade to `partial` and say so rather
@@ -636,7 +636,7 @@ never that the work was skipped quietly.
   the forgotten one: `git -C <submodule> push`, then
   `git add <submodule> && git commit`.
 - **The retrospective is the run's last act** ([`retrospective.md`](retrospective.md)),
-  written to `docs/superpowers/retro.md` — one file per project, not per run. The
+  written to `<artifacts>/retro.md` — one file per project, not per run. The
   pipeline's gates are good at *this* run and blind across runs: the same class of
   failure can be caught, fixed and forgotten five times and nothing in the flow
   notices it is the same one. So, in this order: **stamp the run first** (one line,
@@ -666,7 +666,7 @@ never that the work was skipped quietly.
   with a floor, neither ever a target ([`gates.md`](gates.md) → *Disclosures*); **the
   retrospective is written — stamped first, then pruned, then the entry; the
   list at or under its cap, every deletion logged in the archive with its commit,
-  entries older than five run stamps rotated into `docs/superpowers/retro/` **and the
+  entries older than five run stamps rotated into `<artifacts>/retro/` **and the
   stamp table itself held to ten — at the eleventh the oldest stamp rotates whole into
   the same archive, and both counts print beside the verdict** (the stamp table is read
   in full at stage 0, so *one line per run* is a slope the prune has to stop), the run

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

@@ -9,10 +9,10 @@ from `super-ux`.
 
 | Template | Seeded to | Stage |
 |---|---|---|
-| `brief.md` | `docs/superpowers/specs/YYYY-MM-DD-<topic>-brief.md` | 0 — intake grill |
-| `carryover.md` | `docs/superpowers/specs/YYYY-MM-DD-<topic>-carryover.md` | 0 seeds, all stages append, 10 reads |
-| `verification.md` | `docs/superpowers/verification.md` | 8 writes a row per shipped REQ, 10 requires it, a human fills `Human` |
-| `backlog.md` | `docs/superpowers/backlog.md` | 0 seeds when absent, any stage appends, 10 resolves and re-derives |
+| `brief.md` | `docs/evidence/specs/YYYY-MM-DD-<topic>-brief.md` | 0 — intake grill |
+| `carryover.md` | `docs/evidence/specs/YYYY-MM-DD-<topic>-carryover.md` | 0 seeds, all stages append, 10 reads |
+| `verification.md` | `docs/evidence/verification.md` | 8 writes a row per shipped REQ, 10 requires it, a human fills `Human` |
+| `backlog.md` | `docs/evidence/backlog.md` | 0 seeds when absent, any stage appends, 10 resolves and re-derives |
 | `run.md` | `.task-pipeline/run.md` — **git-ignored**, one per run | 0 seeds it, every gate appends a verdict, every repeating pass a `touch:` line |
 | `context.md` | `CONTEXT.md` at the repo root (or per context) | 0 — grill, domain awareness |
 | `adr.md` | `docs/adr/NNNN-<slug>.md` | 0 — grill, hard-to-reverse decisions |
@@ -23,8 +23,8 @@ from `super-ux`.
 | `hygiene.sh` | `scripts/check-hygiene.sh` | 0 seeds it · **5 runs it after every task** · 6 and 9 run it · 10 proves it |
 | `hooks.example.json` | the project's `.claude/settings.json` | 0 — offered, never installed silently |
 | `routing-rule.md` | the operator's `CLAUDE.md` — **offered by `setup`, never written silently** | 0 / `setup` |
-| `retro.md` | `docs/superpowers/retro.md` — **one per project, not per run** | 10 writes (stamp → prune → entry), 0 reads it in full |
-| `retro-archive.md` | `docs/superpowers/retro/YYYY-QN.md` | 10 rotates into it, 0 **queries** it |
+| `retro.md` | `docs/evidence/retro.md` — **one per project, not per run** | 10 writes (stamp → prune → entry), 0 reads it in full |
+| `retro-archive.md` | `docs/evidence/retro/YYYY-QN.md` | 10 rotates into it, 0 **queries** it |
 
 The documentation-track templates (`docmap.md`, `decisions.md`,
 `open-questions.md`, `docgate.sh`) are seeded **together**, and they are useful at

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

@@ -1,6 +1,6 @@
 # Backlog — <project>
 
-> **The board.** One per project, at `docs/superpowers/backlog.md`. Unlike the
+> **The board.** One per project, at `docs/evidence/backlog.md`. Unlike the
 > carry-over ledger, this file is **mutable**: priority is re-derived, state changes,
 > rows close. What may never happen silently is a row *disappearing* — a closed row is
 > marked closed, with the commit that closed it.

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

@@ -1,7 +1,7 @@
 # Task brief — <topic>
 
 > Stage-0 intake artifact. The grill fills this in and the operator confirms it
-> before stage 1. Copy to `docs/superpowers/specs/YYYY-MM-DD-<topic>-brief.md`.
+> before stage 1. Copy to `docs/evidence/specs/YYYY-MM-DD-<topic>-brief.md`.
 > Every field is a resolved decision or an explicit deferral — no open unknowns.
 
 - **Date:** YYYY-MM-DD
@@ -58,11 +58,11 @@ source is a recorded decision, an unquoted one is an undetected divergence.
 - **Doc repos / hosted doc systems this project names:** … (or `none`)
 - **Knowledge wiki:** installed / not installed
   ([obsidian-wiki](https://github.com/ar9av/obsidian-wiki); recommended, never a gate)
-- **Retro, in force:** `docs/superpowers/retro.md` — none / N standing instructions
+- **Retro, in force:** `docs/evidence/retro.md` — none / N standing instructions
   (read **in full**, together with the run stamps and the recent-log window; list
   which ones bind this run, and stamp each as it fires **with the commit** — that
   stamp is the only evidence behind stage 10's cold-retirement rule)
-- **Retro archive:** `docs/superpowers/retro/` — **queried** by this task's nouns;
+- **Retro archive:** `docs/evidence/retro/` — **queried** by this task's nouns;
   what it returned: … (or `nothing`)
 - **Code graph:** built / installed-not-built / not installed
   ([graphify](https://github.com/Graphify-Labs/graphify); recommended, never a gate —
@@ -139,7 +139,7 @@ is not neutral — it is a scheduled interruption.
 | 7 Deploy | **Authorization** — standing go, or ask every time? | … |
 | 8 Post-deploy | Where logs / health live (app name, endpoint, workflow) | … |
 | 9 Docs+wiki | Which module docs / runbooks this change updates; wiki sync yes/no; **code-graph refresh yes/no** (`/graphify . --update`); which stale ledger rows get fixed | … |
-| 10 Acceptance | Who signs off; where deferred REQs get tracked (issue tracker / backlog); **retro file** — `docs/superpowers/retro.md` present? which standing instructions bind this run? | … |
+| 10 Acceptance | Who signs off; where deferred REQs get tracked (issue tracker / backlog); **retro file** — `docs/evidence/retro.md` present? which standing instructions bind this run? | … |
 
 > **Deploy authorization has a hard floor.** A standing go counts only if it is
 > **specific** — named target and named preconditions ("staging, once lint and the

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

@@ -1,7 +1,7 @@
 # Carry-over ledger — <topic>
 
 > **Append-only.** Any stage may add a row; nobody edits or deletes one. Committed
-> to `docs/superpowers/specs/YYYY-MM-DD-<topic>-carryover.md` beside the brief, and
+> to `docs/evidence/specs/YYYY-MM-DD-<topic>-carryover.md` beside the brief, and
 > read in full by stage 10 (acceptance).
 >
 > **The rule: deferred out loud is forgotten.** If it isn't written here, it wasn't
@@ -24,7 +24,7 @@
   "Forgot" is a legitimate and useful answer here.
 - **REQ** — the requirement it belongs to, or `—` if it's outside the REQ spine.
 - **Where it lives now** — an issue id, a **board id** (`B-NNN` on
-  `docs/superpowers/backlog.md`), or `dropped` with the operator's agreement. Those are
+  `docs/evidence/backlog.md`), or `dropped` with the operator's agreement. Those are
   the three ways a row is *settled*.
   **Three values are not settled and all three block the stage-10 gate:** `unresolved`,
   `open`, and a bare `backlog` — the last one because it names a place without naming a

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

@@ -1,7 +1,7 @@
 # Retro archive — <project> · <YYYY>-Q<N>
 
 **Append-only. Queried, never read in full.** The in-force list
-(`docs/superpowers/retro.md`) is capped at ten and read whole at stage 0; this file
+(`docs/evidence/retro.md`) is capped at ten and read whole at stage 0; this file
 is where entries and retirements go when they age out, so pruning stops losing
 things. Doctrine: `references/retrospective.md`.
 

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

@@ -8,7 +8,7 @@ Doctrine: `references/retrospective.md`.
 
 **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
+negotiable. The **archive** (`docs/evidence/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)
@@ -33,7 +33,7 @@ row goes — the cap is not negotiable, ranking is.
 
 ## Recent log — entries from the last five run stamps (newest first)
 
-Older entries and every retirement **move** to `docs/superpowers/retro/YYYY-QN.md`
+Older entries and every retirement **move** to `docs/evidence/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.

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

@@ -29,6 +29,7 @@ touch: <file> — pass <N> (<stage|round|module>) — reason: <finding id / gate
 hand:  <N|10> — task "<quoted>" — done <n> — surfaced <n> — decisions <n> — amb <n> (<ids or "— no register">)
 holds: <stage id> — <n> (<class: what, owner>; … or "none") — enumerated <n>/8 classes, <unlooked: classes not enumerable>
 gate:  <stage id> — command "<cmd>" — exit <N> — <ISO-8601>
+event: <compact|session-end|subagent> — <detail> — <ISO-8601>
 ```
 
 - **`stage:`** — written when a gate **returns**, not when the stage is entered. The
@@ -42,6 +43,19 @@ gate:  <stage id> — command "<cmd>" — exit <N> — <ISO-8601>
   constrains and confirms an assertion with itself. Absent where the project
   declares no command, and the release gate then degrades to the claim alone.
 
+- **`event:`** — written by `hooks/run-lifecycle.sh`, the three moments this file
+  otherwise cannot show. `compact` marks the boundary the ledger exists *because
+  of* — without it a resumed run cannot tell a compaction from nothing happening.
+  `session-end` marks a run whose session ended without reaching acceptance, which
+  is what `/task-pipeline checkup` looks for and what was previously invisible: the
+  ledger simply stopped, and a stopped ledger looks exactly like a run still in
+  progress. `subagent` records one finishing, so the `hand:` count below has
+  something to be checked against other than itself.
+
+  **It never writes a `hand:` line.** That shape carries `done`, `surfaced`,
+  `decisions` and `amb` — judgements only the agent holds, and a hook filling them
+  in would fabricate the evidence the line exists to provide.
+
 - **`iter:`** — one line per iteration closed. The progress line's counter is
   `grep -c '^iter:'`, never a number anyone remembers.
 - **`hand:`** — one per hand-back, at an iteration's close and at stage 10
@@ -69,6 +83,8 @@ stage: 1 Docs study — gate auto — verdict pass — 2026-08-10T11:31Z
 touch: src/export.ts — pass 1 (stage 5) — reason: TASK-3
 touch: src/export.ts — pass 2 (stage 5) — reason: F-014
 touch: src/export.ts — pass 3 (stage 5) — reason: F-014
+event: compact — auto — 2026-08-10T11:58Z
+event: subagent — general-purpose — 2026-08-10T12:00Z
 gate:  6 — command "npm test" — exit 0 — 2026-08-10T12:02Z
 stage: 6 Tests — gate manual — verdict pass — 2026-08-10T12:03Z
 hand:  3 — task "add CSV export to the orders table" — done 2 — surfaced 1 — decisions 1 — amb 2 (OQ-0007, ledger row 4)