task-pipeline-skill 1.24.0 → 1.25.0

package/CHANGELOG.md

@@ -1,5 +1,67 @@
 # Changelog
 
+## v1.25.0
+
+### One check over one number, made into a registry over the class
+
+The "compute, never restate" guard has existed since v1.5.0 and covered exactly one
+number: the count of negative self-tests, added because two living documents claimed 46
+after the suite reached 50. It stayed one check while the same class went stale in five
+more places, each fixed as an instance and none of them gating the shape:
+
+- `README.md` and `SKILL.md` described `learned.md` as *"fifteen rules"* against a table
+  of twenty-one;
+- `evals/RESULTS.md` ratcheted zero dated runs directly above a dated run, and directly
+  on top of `evals/run.py`, which computes one and had been printing it for five releases;
+- `docs/DOCMAP.md` claimed two standing instructions against the retro's four;
+- the version invariant was **named** *four-way* on four surfaces while `test/validate.py`
+  enforced five;
+- `SKILL-CARD.md` counted "the 26 files under `references/`" against a directory of 28.
+
+`audit.md` says a class seen twice belongs in a script. Six instances later, the file that
+enforces that rule had not applied it to itself.
+
+**The check is now a registry.** One row per claim class, each naming the pattern that
+recognises the claim in prose, the command that computes the truth, and the incident that
+earned the row. Adding a class costs one line instead of one more bespoke block nobody
+generalises.
+
+Two limits are stated rather than implied, because both were learned the hard way this
+release:
+
+- **A quoted number is a citation, not a claim.** `evals/RESULTS.md` narrates its own
+  stale `"Dated runs recorded 0"` while explaining the incident, and the first version of
+  the registry rejected it. The exemption is a quoted span — deterministic, with no marker
+  vocabulary to grow per incident, which is the same drift this release is about.
+- **A count of an enumeration inside one sentence is not computable from outside it.**
+  `CLAUDE.md` said *"the stage list lives on nine surfaces"* above a list of ten. There is
+  no command that can check that, so it is **deleted** rather than gated, and the line now
+  says why.
+
+**Numbers are read as digits and as words.** The incident that named the second row was a
+word — `README.md` said *"fifteen rules"*, not *"15 rules"* — so a digit-only registry could
+not have caught the defect it is named after. Adding word forms immediately found **four
+live claims** the patterns had been skipping in silence: *"the ten canons"*, on four
+surfaces. All four are correct, and none of them was being checked.
+
+That correction matters more than the fix, because the first draft of this entry claimed
+every dormant class was dormant *because the number had been deleted*. For the canons class
+that was simply untrue: it was dormant because the check could not see the form the claim
+was written in. **A dormant state is a claim about the corpus, and it needs the same
+evidence as any other** — this one was plausible, unverified, and wrong.
+
+**Every class reports `ok` or `dormant` beside the verdict.** Four of six are dormant now,
+and that is measured rather than assumed: v1.23.1 and v1.24.0 deleted those numbers rather
+than correcting them, which git history confirms. A registry reporting green over classes
+it never looked at would be precisely the false success it exists to catch. It is a ratchet
+against re-introduction more than a finder of present drift, and the verdict line says so
+every run.
+
+One false positive was measured and removed before shipping: `CONTRIBUTING.md` narrates
+that its invariant list *"was eight guards behind"*, which is a **lag**, not a count of the
+suite. The pattern excludes it explicitly rather than tolerating a noisy check — a gate that
+cries wolf is switched off by the third person who hits it.
+
 ## v1.24.0
 
 ### A rule that reached one file, and the guard shape that let it

package/CONTRIBUTING.md

@@ -143,10 +143,11 @@ list is a second source that goes stale on the next heading.
 A citation of the form `file.md → *Section*` is checked against the target's headings. The
 link checker proves the file resolves; only this proves the pointer is not false.
 
-**13. Numbers stated in living documents are computed, not restated.** The guard
-count in `README.md`, `SKILL-CARD.md` and `evals/RESULTS.md` is compared against the
-negative self-tests the workflow defines. CHANGELOG entries are exempt — they record
-what a past release shipped.
+**13. Numbers stated in living documents are computed, not restated.** Superseded in
+substance by **invariant 35**, which turns this single guard-count comparison into a
+registry over the class. Kept as the entry point because it is the shorter statement of
+the law and the one people look for; the mechanism, the exemptions and the scope live in
+35, and this text names no surfaces of its own so the two cannot disagree.
 
 **14. Every relative link in `README.md` resolves inside the published package.**
 `package.json` → `files[]` must ship whatever the README points at, or the link
@@ -279,7 +280,24 @@ A paragraph that narrates the old order as the defect is exempt by an explicit m
 list, not by a heuristic.
 *(guard: `enumerates the retro's acts as`)*
 
-**35. Every invariant above names the guard that enforces it, and that guard exists.**This list claims to be *what the validator enforces*; it was eight guards behind when
+**35. A number a living document states is compared against the command that computes
+it — from a registry, not a bespoke check.** This began as one check over one number, and
+stayed one check while the same class went stale in five more places: `learned.md`
+described as *"fifteen rules"* against a table of twenty-one, `evals/RESULTS.md` ratcheting
+zero dated runs directly above a dated run and directly on top of a tool computing one,
+`docs/DOCMAP.md` claiming two standing instructions against four, and the version invariant
+**named** *four-way* while five surfaces were enforced. Each was fixed as an instance; the
+class was never gated — `audit.md`'s own rule, unapplied to the file that enforces it.
+Adding a class is now **a row**, naming the claim pattern, the computing command and the
+incident that earned it. Two things are stated rather than implied: a **quoted** number is a
+citation of what a document said and is exempt, so a register can narrate its own drift;
+and a count of an enumeration inside one sentence is not computable from outside it, so
+those are **deleted** instead — `CLAUDE.md`'s stage-list line says so where it used to carry
+one. Every class prints `ok`/`dormant` beside the verdict, because a registry reporting
+green over classes it never looked at is the false success it exists to catch.
+*(guard: `— derive the number or delete it. This class is registered `)*
+
+**36. Every invariant above names the guard that enforces it, and that guard exists.**This list claims to be *what the validator enforces*; it was eight guards behind when
 an audit measured it. A claim of enforcement is now checked like any other claim.
 *(guard: `whose message does not appear in`)* — and a cited literal must lie inside
 a **single** string in `test/validate.py`: the check reads that file as text, so a

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.24.0 |
+| **Version** | 1.25.0 |
 | **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, 5 categories. One recorded run, **self-observed by the author**; **zero blind runs on zero of three models** — the split, and the numbers, live in [`evals/RESULTS.md`](evals/RESULTS.md) and are computed by `evals/run.py` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "task-pipeline-skill",
-  "version": "1.24.0",
+  "version": "1.25.0",
   "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.24.0",
+  "version": "1.25.0",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"