task-pipeline-skill 1.85.0 → 1.85.2

package/CHANGELOG.md

@@ -1,3 +1,68 @@
+## v1.85.2 — the two-merge protocol, followed this time
+
+**v1.85.1 is a burned tag** — the third of this wave's choreography lessons, and
+this member's own: the release gate on the tag's tree demands a run stamp inside
+the tag's range, the branch run cannot see a tag that does not exist yet, and the
+stamp was never written. Nothing shipped; npm never saw 1.85.1. This version is
+the same change released by the protocol B-134 wrote down: the payload merges
+first, the stamp merges second citing the payload's merge commit, and the tag
+lands on the stamp.
+
+Guards: 429 → **429** — nothing but version surfaces, this record, and the
+stamp's own choreography move in this release.
+
+## v1.85.1 — five surfaces a reader trusts, each disagreeing with the tree it ships from
+
+The family audit of 2026-09-06 (wave `AUDIT-WAVE-0906`) read every member's shipped
+surfaces at once, and five of this member's disagreed with what the tree holds. No
+behaviour changed in this release; what changed is what a reader — a person on the
+marketplace page, or a resolver following a path — is told.
+
+- **The marketplace entry taught the old gate vocabulary.** `plugin.json` says *typed
+  auto/judgment/manual gates*; `.claude-plugin/marketplace.json` said *typed
+  auto/manual*. The `judgment` type has been in the schema since v1.73.0 and the
+  v1.80.0 sweep put it on seven surfaces — the marketplace blurb was not one of them,
+  because the cross-surface guard reads the schema and `SKILL.md`, never the
+  marketplace entry. The two descriptions are byte-equal now, compared rather than
+  eyeballed: `json.load` both, `==` → `True` (the sole difference was 9 bytes at
+  character 298, the string `judgment/`).
+- **Two in-directory references in `project-audit`'s `SKILL.md` resolved only in the
+  sibling skill.** Its §6 named `references/backlog.md` and
+  `references/prioritisation.md` bare — directories the flagship skill carries and
+  `project-audit` does not — while the routing table at the top of the same file
+  already used the `../task-pipeline/references/…` form. Both now use that form, as
+  links that resolve from the file that carries them.
+- **`certification.md` pointed at a file no install of this plugin can resolve.**
+  `references/statistics.md` lives in `agent-stack`'s `agent-evals` skill, another
+  member entirely; the sentence carried it as a bare path beside the owner's name. It
+  is a named-owner prose pointer now, with no bare in-repo path left to resolve.
+- **Front matter inside the pack moves together.** `evidence-docs` carried neither
+  `license:` nor `compatibility:`; `project-audit` carried no `license:`. Both now
+  carry the flagship's keys — `license: MIT`, and a compatibility line true of each
+  skill rather than copied: `evidence-docs` ships no scripts, and its line says so.
+- **The `quick` opt-out is retired; the canon refusal replaces it.** *"quick fix"*
+  carries the trigger `fix` and the opt-out `quick` in one natural breath, and the
+  board already records the escape being used on work that should not have taken it
+  (`B-095`). The description now names *'no pipeline' / 'без пайплайна'* — the refusal
+  wording the operator's routing doctrine states — and the opt-out guard in
+  `test/validate.py` demands exactly that pair, so a description that drops either
+  valve fails. No recorded decision protects the old token: the only decision-bearing
+  surfaces that name it are `B-095`, which argues against it, and dated records, which
+  are not rewritten. No advertised trigger phrase was removed. Measured with
+  make-skill's auditor before and after: description 897 → 903 of 1024, inside the
+  970-character working limit, all sixteen description checks green both times.
+
+The dated spec `docs/evidence/specs/2026-08-10-routing-taxonomy.md` still quotes the
+old opt-out pair, deliberately: it records what was true at its commit, and this
+repository has already decided that dated records are counted, not rewritten.
+
+Guards: 429 → **429** — no planted-defect step added or removed; one existing guard's
+needle moved with the surface it reads (`quick` → `no pipeline`). And the gate earned
+its keep on this very release: its first run refused three restated figures this entry's
+own change had gone stale — the board's description budget (897 → 903), its headroom
+(127 → 121 spare), and the README's conformance figure (899 → 905) — each rewritten to
+the value the owning check computes, so the next drift fails the same way this one did.
+
 ## v1.85.0 — a release stamp names the tag, and the amend rule's sibling one level up
 
 `B-124`, filed by the umbrella's coordinator after watching the same class three times:

package/README.md

@@ -587,7 +587,7 @@ must say so.
 ### Held to Anthropic's own Skill authoring guidance
 
 Audited against the four Agent Skills pages. Most of it already held — `name`
-13/64 chars, `description` 899/1024 chars, `SKILL.md` 262/500 lines, all 38 references
+13/64 chars, `description` 903/1024 chars, `SKILL.md` 262/500 lines, all 38 references
 linked **directly** from `SKILL.md`, and the bundle far under the 30 MB ceiling. What
 did not, now does:
 

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.85.0 |
+| **Version** | 1.85.2 |
 | **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, and **one of two browser channels** — `playwright` (CLI or MCP) or `chrome-devtools` (MCP); either satisfies the browser step and neither is required. 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.85.0",
+  "version": "1.85.2",
   "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

@@ -3,7 +3,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/judgment/manual gates, a frozen requirement spine that closes with evidence, a work board and a verification ledger that outlive a run, an exposure line naming what shipped unconfirmed, a progress rail computed from the project's own config, a loop guard whose review ceiling measures rather than stops, and stage-3 tracks for what a product does, how it sounds and how it looks. Two modes need no task: `checkup` (what is unverified) and `setup` (audit existing docs). Retro insights can publish upstream as issues, opt-in and redacted.",
-  "version": "1.85.0",
+  "version": "1.85.2",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

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

@@ -1,6 +1,8 @@
 ---
 name: evidence-docs
 description: "Use when writing or reviewing anything that will be read as true — a decision record, a README, an acceptance report, a runbook, a changelog entry, an audit finding, or any claim that something was verified. Applies the ten canons of evidence-backed documentation — what makes a claim documentation rather than an assertion — and routes to the doctrine that enforces each one. Also use when a project needs a documentation gate, a decision register, a propagation matrix, or a retrospective that outlives its author. Triggers - 'documentation gate', 'decision record', 'ADR', 'acceptance report', 'runbook', 'is this verified', 'доказательная документация', 'записать решение', 'запиши решение', 'отчёт о приёмке', 'раннбук', 'чем это подтверждено', 'доки в синхроне'. Not for: drafts, chat answers, commit messages or code comments — say 'без доков' to opt out."
+license: MIT
+compatibility: "Doctrine runs on any agent. No bundled scripts — nothing to install and nothing to degrade."
 ---
 
 # Evidence-backed documentation

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

@@ -1,6 +1,7 @@
 ---
 name: project-audit
 description: "Use when someone asks what is actually true of a whole project right now — what is finished, what is half-built, what is broken, and what nobody has looked at. Walks a cold start: discover what the project is, run a registry of probes chosen from that, read production evidence (published artefact against source, CI history, telemetry present or absent), then leave a self-contained HTML report and a JSON sidecar so the next audit can say what moved. Read-only: it proposes board rows and commits nothing. Triggers - 'project audit', 'audit the project', 'codebase audit', 'state of the project', 'what is unfinished', 'project health check', 'аудит проекта', 'проаудируй проект', 'состояние проекта', 'что не доделано', 'аудит кодовой базы'. Not for: auditing one deliverable inside a run (that is the pipeline's own ladder), reviewing a diff, or checking a skill's construction — say 'без диагностики' to opt out."
+license: MIT
 compatibility: "The collector (scripts/audit.py) needs python3 and reads committed state, so it needs git. Probes needing gh, npm, network or a browser declare it and report blind when it is absent — degraded, never silent."
 ---
 
@@ -115,10 +116,10 @@ what ran are the same object.
 
 **This skill commits nothing.** Findings leave as board rows in the project's
 own vocabulary, priced with **the board header's declared formula** — the shipped
-default is `Sev × Blast + age_bonus` (`references/backlog.md`, the pipeline's
+default is `Sev × Blast + age_bonus` ([`references/backlog.md`](../task-pipeline/references/backlog.md), the pipeline's
 board doctrine) — and the operator accepts them. Effort never ranks inside an
 audit: what a fix costs is the fixer's decision, not the finder's
-(`references/prioritisation.md`). An audit
+([`references/prioritisation.md`](../task-pipeline/references/prioritisation.md)). An audit
 that edits while it reads cannot be re-run to check itself.
 
 ## A finding carries its consequence, or it is a hypothesis

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

@@ -1,6 +1,6 @@
 ---
 name: task-pipeline
-description: "Use when work changes the repository — feature, fix, refactor, migration, integration, rewrite, adoption or hardening; фича, фикс, рефактор, миграция, интеграция, доработать, починить, внедрить, перевести — or when the output is a finding that lands in it: audit/аудит, bug hunt/проверь ошибки, production check/проверь прод, PR review/ревью PR — or on 'run this through the pipeline' / 'прогони по конвейеру', 'full cycle, the full cycle' / 'полный цикл', /task-pipeline. Runs a substantial task through an intake grill, docs study, brainstorm, spec, plan, build, tests, deploy, post-deploy, docs/wiki sync and acceptance with explicit gates. 'checkup' / 'чекап' reports unconfirmed releases; 'setup' audits existing docs. Not for: answering a question, explaining code, a typo or a one-line edit, a mechanical rename, reconnaissance that lands nothing — say 'без пайплайна' / 'quick' to opt out."
+description: "Use when work changes the repository — feature, fix, refactor, migration, integration, rewrite, adoption or hardening; фича, фикс, рефактор, миграция, интеграция, доработать, починить, внедрить, перевести — or when the output is a finding that lands in it: audit/аудит, bug hunt/проверь ошибки, production check/проверь прод, PR review/ревью PR — or on 'run this through the pipeline' / 'прогони по конвейеру', 'full cycle, the full cycle' / 'полный цикл', /task-pipeline. Runs a substantial task through an intake grill, docs study, brainstorm, spec, plan, build, tests, deploy, post-deploy, docs/wiki sync and acceptance with explicit gates. 'checkup' / 'чекап' reports unconfirmed releases; 'setup' audits existing docs. Not for: answering a question, explaining code, a typo or a one-line edit, a mechanical rename, reconnaissance that lands nothing — say 'no pipeline' / 'без пайплайна' to opt out."
 license: MIT
 compatibility: "Doctrine runs on any agent. The bundled scripts need python3; the run needs git. Missing either degrades, never blocks — the graph verbs and seeded gates go unused, and the run says so."
 ---

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

@@ -116,8 +116,9 @@ severity. Sequential testing cuts the trials such a verdict needs by **78%**.
 
 So: **two severities for a finding, three verdicts for a stochastic check.** A
 deterministic command exits 0 or it does not, and admitting a maybe there does admit
-everything. The instrument for the other case is `agent-stack`'s `agent-evals` —
-`references/statistics.md` for how many runs make a difference real — and a gate whose
+everything. The instrument for the other case is `agent-stack`'s `agent-evals` skill —
+its own `references/statistics.md`, shipped in that member, says how many runs make a
+difference real — and a gate whose
 subject is non-deterministic belongs on that axis rather than this one
 ([`gates.md`](gates.md) → *Axis A*).