@mmerterden/multi-agent-pipeline 16.25.0 → 16.25.1

package/CHANGELOG.md

@@ -16,6 +16,16 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ## [Unreleased]
 
+## [16.25.1] - 2026-09-09
+
+### Fixed
+
+- **A contract that named two consumers neither of which read it.** `features/design-conformance.md` shipped declaring Phase 4 review and `features/visual-evidence.md` as consumers; both were silent. That is the declared-but-inert class the prefs gate already hunts elsewhere - the contract looks wired, the surfaces never open it.
+
+  `visual-evidence.md` now points at it for what a capture is worth checking against: one contract owns getting the picture, the other owns reading it. Phase 4 Step 1.8 cites it in place of a hand-rolled list of eight visual-fidelity items (avatar icon, field grouping, character counter, header style, inline error layout, button height, indicator chip, placeholder copy) that were an ad-hoc subset of what the 30-group catalog now defines properly - so the step got shorter _and_ stricter, and carries the two rules that matter in review: a height or inset is measured rather than read from the token under test, and an unrun check is a fail-to-verify.
+
+  `smoke-design-conformance.sh` gained the check that would have caught it: every consumer the ref names must cite it back.
+
 ## [16.25.0] - 2026-09-09
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mmerterden/multi-agent-pipeline",
-  "version": "16.25.0",
+  "version": "16.25.1",
   "description": "8-phase AI development pipeline with full orchestration on Claude Code, Copilot CLI and Codex CLI. Analysis, planning, TDD, CLI-aware parallel review with consensus surfacing + Fable triage, default-FAIL evidence gates, secret + intent guards, per-phase cost ledger, persistent learnings memory, wiki generation, commit automation. Token-preserving uninstall.",
   "type": "module",
   "main": "index.js",

package/pipeline/multi-agent-refs/features/visual-evidence.md

@@ -64,6 +64,11 @@ bash $HOME/.claude/scripts/capture-evidence.sh after \
   --task "$TASK_ID" --platform "$PLATFORM" --label "<screen-slug>"
 ```
 
+What the capture is worth checking against - the per-component catalog, the
+measure-never-the-token rule, the presence gate - is
+`$HOME/.claude/multi-agent-refs/features/design-conformance.md`. This contract
+owns getting the picture; that one owns reading it.
+
 The script boots the device if needed, launches the built app, cleans the status
 bar (`ios_status_bar preset:clean` / the Android equivalent) so the frame carries
 no clock, carrier or battery noise, captures at device resolution, downscales to

package/pipeline/multi-agent-refs/phases/phase-4-review.md

@@ -262,14 +262,7 @@ Visual-fidelity mismatches against the captured screenshot are BLOCKING findings
 
 - Canonical component usage: the Code Connect-mapped component is used verbatim  -  a sound-alike substitute, a forked copy, or ad-hoc inline UI where a mapping exists is blocking (Phase 3 "Design fidelity contract")
 - Inter-component spacing: gaps, paddings, and alignment BETWEEN components match the design's measured values mapped to spacing tokens  -  invented numeric values are blocking
-- Avatar icon (presence, glyph, shape, position)
-- Field grouping (one rounded box vs two; separator vs gap)
-- Character counter visibility
-- Header style (size, weight, alignment)
-- Inline error layout (icon presence, text colour, position relative to the input)
-- Button height
-- Indicator chip placement
-- Placeholder copy and position
+- Everything else: the 30-group catalog in `$HOME/.claude/multi-agent-refs/features/design-conformance.md`. Two of its rules carry into review: a height or inset is **measured**, never read from the token under test; an unrun check is a fail-to-verify, not a pass.
 
 When `state.figmaAccess.tier === 3` (user-attached screenshot, no Code Connect snippet), the reviewer additionally sets `findings[i].severity = "blocking"` and `findings[i].tag = "review_blocking_tier3"` on every UI atom that lacks a confirmed canonical-component mapping. The triage step preserves these findings unless the user has explicitly cleared the open question.
 

package/pipeline/skills/.skill-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": "1.0.0",
-  "generatedAt": "2026-09-09T17:46:50Z",
+  "generatedAt": "2026-09-09T18:15:55Z",
   "skillCount": 207,
   "entries": [
     {