@maind-dev/cli 0.97.3 → 0.99.0

package/README.md

@@ -106,23 +106,60 @@ The CLI never posts the comment itself — your workflow posts the file via
 
 ### Detector findings (with `--gate`)
 
-With `--gate`, the CLI also runs the nine repo-health detectors from
+With `--gate`, the CLI also runs the ten repo-health detectors from
 `@maind/code-index` on this machine — number collisions in counter-style
 namespaces (`ADR-263-*.md` twice), spec drift (a registry vs. the artefact it
 declares), dead theme classes (a Tailwind v4 utility pointing at a token that
 does not exist), table ACL (Supabase default grants never revoked), duplicate
 changelog headings, unparsable workflow YAML, release claims (a changelog
-version npm never published), prose added to agent docs and a work-object
+version npm never published), prose added to agent docs, a work-object
 branch without documentation (no Markdown file naming the key, no
-`Doc-Decision:` trailer) — and sends them to
+`Doc-Decision:` trailer) and mockup labels (a product mockup showing text the
+product no longer renders) — and sends them to
 `review_verdict` as a third finding class next to convention findings and risk
 flags (ADR-324).
 
 Only a **commitment** leaves the machine: `detector_id`, `detector_version`,
 `rule_id`, `level`, `baseline`, an `evidence_hash` (sha256 over the normalised
-evidence) and a count. Paths, tokens, class names, table names and numbers
-stay local — they appear in the report (`.maind/review.md`) but never in the
-manifest, the PR comment or the wire.
+evidence) and a count. Paths, tokens, class names, table names, labels and
+numbers stay local — they appear in the report (`.maind/review.md`) but never
+in the manifest, the PR comment or the wire.
+
+#### Mockup labels
+
+A demo, product tour or screenshot rebuilt in code shows the product's labels
+"verbatim" — until the product renames one. Pin each label to the file that
+renders it, and the mockup-label detector checks every pin in both directions:
+the product source still contains the label (`mockup.label_not_in_source`,
+blocks), and some mockup still shows it (`mockup.pin_unused`, warns — a dead
+pin reads as coverage that does not exist). A pinned source that moved is
+`mockup.source_missing`, an unreadable pins file `mockup.pins_unreadable`.
+Comments are ignored on both sides and whitespace is collapsed, so JSX text
+broken across lines still matches.
+
+Declare the sets in `.maind/mockup-labels.json` at the repository root:
+
+```json
+{
+  "sets": [
+    {
+      "id": "site-tour",
+      "reason": "The website tour recreates the dashboard navigation verbatim.",
+      "pins_file": "apps/website/src/tour/labels.json",
+      "source_root": "apps",
+      "mockups": ["apps/website/src/tour/", "apps/website/src/DemoFrame.tsx"]
+    }
+  ]
+}
+```
+
+`pins_file` holds `{"pins": [{"label": "Agent sessions", "source":
+"dashboard/src/nav.ts"}]}` (or a bare array); small sets may inline them as
+`pins` instead. `source` resolves against `source_root`; `mockups` are path
+prefixes (a directory with a trailing `/`, or a file), and tests never count
+as a mockup. Without the file the detector abstains — it cannot know which of
+your mockups claim to be verbatim. It checks the labels you pinned; a label
+nobody pinned, and how the mockup looks, stay unchecked.
 
 Block-eligible is only a finding this branch **introduces** (`level: open`,
 `baseline: introduced`). Objective detectors block by default; table ACL,