@maind-dev/cli 0.14.0 → 0.16.0

package/README.md

@@ -103,6 +103,34 @@ The CLI never posts the comment itself — your workflow posts the file via
 | `1` | Only a server verdict crossing `--fail-on` (requires `--gate`) |
 | `2` | Infra error, only under `--strict` |
 
+### Detector findings (with `--gate`)
+
+With `--gate`, the CLI also runs the four 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), and table ACL (Supabase default grants never revoked) — 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.
+
+Block-eligible is only a finding this branch **introduces** (`level: open`,
+`baseline: introduced`). Objective detectors (number collisions, spec drift,
+dead theme classes) block by default; table ACL warns, because it encodes an
+architecture opinion — a team policy can override either way, with a reason.
+
+`diff_stats.detector_coverage` reports whether every detector ran or honestly
+abstained (`full`), whether one could not run or could not grade against the
+merge base (`partial`), or whether none ran (`none`). Only `full` keeps a run
+attestation-grade; `partial` never does — the verdict still stands. Servers
+before 0.48.0 ignore the section silently; the CLI detects the missing echo
+and says so (`server_acknowledged: false` in the manifest).
+
 ## Fail-open contract
 
 A context pull must never fail a build. On any error (missing key, network,