task-pipeline-skill 1.23.0 → 1.23.1

package/CHANGELOG.md

@@ -1,5 +1,54 @@
 # Changelog
 
+## v1.23.1
+
+### Four documents that had gone false, and the config this repository never wrote
+
+A review of the hallucination-mitigation literature against this skill produced an
+uncomfortable result: the doctrine already covers almost every applicable mitigation the
+field names — grounding, constrained generation, post-processing that blocks unproven
+assertions, self-contradiction detection. What it does not cover is **this repository
+applying that doctrine to itself.** Everything below is a class the skill documents,
+found in the skill.
+
+**Four surfaces were stating numbers that had stopped being true.**
+
+- `README.md` and `SKILL.md` said `learned.md` carries *"fifteen rules"*. The table has
+  twenty-one. Both now describe the file without counting it — the table is the count,
+  the same fix `CLAUDE.md` already applies to the invariant list, and the reason is that
+  a hand-written count goes stale on the next rule rather than on the next audit.
+- `evals/RESULTS.md` opened with *"the suite is authored and has not been executed"* and
+  ratcheted *"Dated runs recorded 0"* — directly above a dated run, and directly on top
+  of `evals/run.py`, which computes `recorded runs: 1` and had been printing it for five
+  releases. The document and the tool beneath it disagreed, and nothing compared them.
+  The ratchet now carries what actually matters: one run, **self-observed**, and **zero
+  blind** — because collapsing those into a single total is how a self-check gets quoted
+  as a result.
+- `docs/DOCMAP.md` claimed two standing instructions against the retro's four, and
+  duplicated both eval numbers. Its ratchet table now names **homes and commands, never
+  values**. A ratchet copied into a second document is two ratchets, and the copy nobody
+  runs is the one people read.
+
+**`learned.md`'s own routing table stopped at rule 16.** Rules 17–21 were in the rule
+table, each guarded in its consumer files, and absent from *Where these bind in the
+pipeline* — the section an agent reads to learn *when* a rule applies. The rule's own
+failure mode, applied to the map of the rules. All twenty-one now name their stage, and
+the two mis-aimed citations that first attempt introduced were caught by the citation
+guard rather than by a reader, which is the guard doing exactly its job.
+
+**This repository had no `pipeline.json`.** The project that ships the config contract
+had never written its own, so `run.loop` was unrecorded, the mode defaulted to off, and
+every loop it ran was authorised in a chat message. There is now a real one: this repo's
+eleven stages with its real host commands, its release block, and the loop mode recorded
+as a file rather than remembered — including the note that the mode collapses
+discretionary check-ins only, and is never the authorization for the tag push.
+
+**Not fixed here, and named rather than quietly carried:** rule 21 changed the retro's
+order to *stamp first* in `references/retrospective.md` and in no other file. Eight
+sibling surfaces — `SKILL.md` included, which is what an agent loads first — still teach
+the deadlocked *prune first*. That is a gate contract, so it ships on its own branch with
+a guard that compares the class rather than one literal.
+
 ## v1.23.0
 
 ### A step that consumes what a later step produces is a deadlock — `learned.md` rule 21

package/CONTRIBUTING.md

@@ -67,10 +67,13 @@ These are what the validator enforces. Breaking one is not a style disagreement
 it ships a wrong pipeline to every install. Numbered in reading order; the numbers
 are labels, not priorities.
 
-**1. Four-way version sync.** `package.json`, `.claude-plugin/marketplace.json`
-(`plugins[0].version`), `plugins/task-pipeline/.claude-plugin/plugin.json` and the
-top `## vX.Y.Z` heading in `CHANGELOG.md` must all carry the same version.
-`SKILL-CARD.md`'s Version row is held to it too.
+**1. Version sync across every manifest surface.** `package.json`,
+`.claude-plugin/marketplace.json` (`plugins[0].version`),
+`plugins/task-pipeline/.claude-plugin/plugin.json`, the top `## vX.Y.Z` heading in
+`CHANGELOG.md` **and `SKILL-CARD.md`'s Version row** must all carry the same version.
+The invariant was called *four-way* until 2026-08-08 while listing five surfaces and
+while the validator enforced five — a name that counts is a number, and it drifts like
+one. The list is the count.
 
 **2. The stage list lives on three surfaces and may not drift.** `SKILL.md`'s
 table, `references/stages.md`'s per-stage sections, and `pipeline.example.json`.

package/README.md

@@ -808,7 +808,7 @@ recommendation, so you arm the whole run in one exchange. Detail:
 | [`references/adoption.md`](plugins/task-pipeline/skills/task-pipeline/references/adoption.md) | the first run in a project: greenfield seeding, and the brownfield walkthrough |
 | [`references/setup.md`](plugins/task-pipeline/skills/task-pipeline/references/setup.md) | the entry audit: seven passes over the docs a project already has, offered once, output as a fix plan |
 | [`references/portability.md`](plugins/task-pipeline/skills/task-pipeline/references/portability.md) | the manifest of workflow decisions and their homes in the bundle, and the boundary against a project's own answers |
-| [`references/learned.md`](plugins/task-pipeline/skills/task-pipeline/references/learned.md) | fifteen rules earned by failure on a real multi-repository build, each with its incident, its check and its exit criterion |
+| [`references/learned.md`](plugins/task-pipeline/skills/task-pipeline/references/learned.md) | rules earned by failure on a real multi-repository build, each with its incident, its check and its exit criterion — the table is the count, and it grows |
 | [`SKILL-CARD.md`](SKILL-CARD.md) | the registry entry and risk-tier disclosure a reviewer needs before deploying it |
 | [`evals/`](evals/RESULTS.md) | the behavioural evaluation suite, its protocol, and what has actually been observed |
 | [`CHANGELOG.md`](CHANGELOG.md) | every release, with the reasoning behind it |
@@ -817,8 +817,8 @@ recommendation, so you arm the whole run in one exchange. Detail:
 ## Contributing
 
 Issues and pull requests are welcome — see [CONTRIBUTING.md](CONTRIBUTING.md) for
-the repo's invariants (the structural validator, four-way version sync, and the
-surfaces that must never drift apart). Security reports:
+the repo's invariants (the structural validator, version sync across every manifest
+surface, and the surfaces that must never drift apart). Security reports:
 [SECURITY.md](SECURITY.md). Everyone participating is expected to follow the
 [Code of Conduct](CODE_OF_CONDUCT.md).
 

package/SKILL-CARD.md

@@ -12,7 +12,7 @@ harmless.
 |---|---|
 | **Purpose** | Runs a substantial task through ten gated delivery stages — intake grill, docs study, brainstorm, spec, plan, subagent build, tests, lint/deploy, post-deploy, docs+registers, acceptance — refusing to advance until each gate passes |
 | **Owner** | ssheleg ([github.com/ssheleg/task-pipeline](https://github.com/ssheleg/task-pipeline)) |
-| **Version** | 1.23.0 |
+| **Version** | 1.23.1 |
 | **Surface** | Claude Code (filesystem skill + plugin) and the vercel `skills` CLI. **Not** uploaded to the Skills API; custom Skills do not sync across surfaces |
 | **Dependencies** | None required. Optional: `context7` (MCP), `figma` (MCP), super-ux, agent-sync, graphify, obsidian-wiki. Every stage's doctrine ships in-repo; the one conditional requirement is super-ux for the stage-3 UX track on a user-facing task |
 | **Evaluation status** | Suite authored (15 evals, 5 categories). **Never executed** — see [`evals/RESULTS.md`](evals/RESULTS.md) |

package/evals/RESULTS.md

@@ -1,8 +1,16 @@
 # Evaluation results — task-pipeline
 
-**Status: the suite is authored and has not been executed.** Recorded here rather
-than left blank, because an empty results file and an unrun suite look identical,
-and this repository's own doctrine calls that the failure — a skip is not a pass.
+**Status: the suite is authored. One run is recorded and it was self-observed by the
+author; no blind run has been made on any model.** Recorded this way rather than left
+blank, because an empty results file and an unrun suite look identical, and this
+repository's own doctrine calls that the failure — a skip is not a pass.
+
+**The numbers below are computed, not asserted.** `python3 evals/run.py` counts the
+suite and the dated run headings in this file. A value typed here that disagrees with
+what it prints is the defect, and it is the document that is wrong — this file said
+*"has not been executed"* and *"Dated runs recorded 0"* for five releases while the
+tool beneath it printed `recorded runs: 1`, which is the self-contradiction canon 2
+exists to prevent, in the one file whose whole job is honesty about evidence.
 
 Running these needs a fresh session per query, per model. That is a human or agent
 step; `evals/run.py` prints the protocol and deliberately never reports a pass it
@@ -29,19 +37,23 @@ or it belongs in a check.
 
 ## Ratchet
 
-| Metric | Value | As of |
-|---|---|---|
-| Evals authored | 15 | 2026-08-03 |
-| Categories covered | 5 of 5 | 2026-08-03 |
-| Models exercised | **0 of 3** | 2026-08-03 |
-| Dated runs recorded | **0** | 2026-08-03 |
+| Metric | Value | Computed by | As of |
+|---|---|---|---|
+| Evals authored | 15 | `python3 evals/run.py` → `suite: N evals` | 2026-08-08 |
+| Categories covered | 5 of 5 | the suite's own `category` fields | 2026-08-08 |
+| Dated runs recorded | **1** | `python3 evals/run.py` → `recorded runs: N` | 2026-08-08 |
+| …of those, **blind** | **0** | run headings not marked `self-observed` | 2026-08-08 |
+| Models exercised blind | **0 of 3** | distinct models across blind runs | 2026-08-08 |
+
+**The last three rows are the honest state of this skill's behavioural evidence**, and
+the split matters more than the total: a run the author watched, knowing the expected
+behaviour, is an observation of instruction-following and not an evaluation. Collapsing
+the two into one "runs recorded" number is how a self-check gets quoted as a result.
 
-The bottom two numbers are the honest state of this skill's behavioural evidence.
 Everything else in this repository is proven by structural guards — the count is
-whatever `npm run test:all` prints, deliberately not restated here — that check the
-*form*; these are the only checks that would speak to the *behaviour*, and they have
-not been run yet. Printed here so "63 of 63 green" is never read as "the skill is
-known to work".
+whatever `npm run test:all` prints, deliberately not restated here — and those check
+the *form*. These are the only checks that speak to the *behaviour*. Printed here so a
+green structural suite is never read as "the skill is known to work".
 
 ## Runs
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "task-pipeline-skill",
-  "version": "1.23.0",
+  "version": "1.23.1",
   "description": "Full-cycle delivery pipeline for coding agents: a mandatory built-in intake grill, then 10 gated stages (docs, brainstorm+decompose, spec, plan, build, tests, lint/deploy, post-deploy, docs/wiki, acceptance). Every stage's doctrine ships inside the skill — no companion plugin required. This package is the installer CLI.",
   "bin": {
     "task-pipeline": "bin/task-pipeline.js"

package/plugins/task-pipeline/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "task-pipeline",
   "displayName": "Task Pipeline",
   "description": "Runs a substantial task through a mandatory built-in intake grill, then 10 gated stages (docs, brainstorm+decompose, spec, plan, subagent build, tests, lint/deploy, post-deploy, docs/wiki, acceptance). Every stage's doctrine is built into the skill — no companion plugin required — with typed auto/manual gates, a frozen requirement spine that must close with evidence, a loop guard that breaks churn, one provider-agnostic model confirmed up front, and an optional super-ux UX track for user-facing work.",
-  "version": "1.23.0",
+  "version": "1.23.1",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

package/plugins/task-pipeline/skills/task-pipeline/SKILL.md

@@ -334,7 +334,7 @@ automation is on — `pipeline.schema.json` is the only contract.
 - `references/deploy-targets.md` — stages 7–8: writing the runbook when there is none, the template, per-platform deploy and log verbs, and the verification trio
 - `references/hooks.md` — agent-time enforcement: the PreToolUse contract, the fail-open hazard, placement, and the Claude-Code-only limit
 - `references/audit.md` — cross-cutting: the L0→L7 ladder and its seams (what was never written), axis rotation, ratchets, proven checks
-- `references/learned.md` — cross-cutting: fifteen rules earned by failure on a real multi-repository build, each with the incident behind it, its check and its exit criterion; plus the two that no check can decide
+- `references/learned.md` — cross-cutting: rules earned by failure on a real multi-repository build, each with the incident behind it, its check and its exit criterion; plus the two that no check can decide. The table is the count — a number written here is a number that goes stale on the next rule
 - `references/brainstorm.md` — stage 2: design dialogue, approaches, UI detection, hard gate
 - `references/spec.md` — stage 3: UX track order, the spec contract, self-review, review gate
 - `references/planning.md` — stage 4: zero-context plan format, parallel groups, no placeholders

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

@@ -196,6 +196,11 @@ answer would have exposed it in a minute.
 | 9 Docs | 8, 14 — every number computed, every target resolvable |
 | 10 Acceptance | 1, 3, 6, 7 — axis rotation recorded, closure verified against artefacts, classes swept, ratchets printed |
 | 10 Acceptance · every loop iteration | 16 — the work-list re-measured at close and printed beside its opening count ([`audit.md`](audit.md), [`continuity.md`](continuity.md)) |
+| 0 Harvest · **before the first edit**, in any repository with an upstream | 17 — `git rev-list --count HEAD..@{u}` measured and its number printed, [`knowledge-sources.md`](knowledge-sources.md) → *The source is not the copy you have*; asked as row `0 Source` of [`grill.md`](grill.md) → *The autonomy sweep* |
+| 0 Harvest · 5 Dev · 6 Tests | 18 — the suite run once against a **freshly created** instance of whatever persists between runs, [`tdd.md`](tdd.md) → *The green from residue*; asked as row `0 Fixtures` of [`grill.md`](grill.md) → *The autonomy sweep* |
+| any command run to establish a fact — 6 Tests · 9 Docs · 10 Acceptance · 5 review | 19 — the output asserted non-empty and shaped as expected, and **quoted** rather than concluded from, [`audit.md`](audit.md) → *Silence is not a reading*; the reviewer's half is in [`review.md`](review.md) |
+| 0 Harvest · 10 Acceptance | 20 — the **consumer** read to learn which copy ships, never the copies compared against each other, [`audit.md`](audit.md) → *Two copies, and which one wins*; asked as row `0 Duplicates` of [`grill.md`](grill.md) → *The autonomy sweep* |
+| 10 Retro · **any gate or check you order** | 21 — each input traced to the step that writes it, and that step proven upstream, [`retrospective.md`](retrospective.md) → *Stamp first, then prune, then write* |
 
 **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*