@maind-dev/cli 0.95.0 → 0.96.1

package/README.md

@@ -106,13 +106,15 @@ The CLI never posts the comment itself — your workflow posts the file via
 
 ### Detector findings (with `--gate`)
 
-With `--gate`, the CLI also runs the eight repo-health detectors from
+With `--gate`, the CLI also runs the nine 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) and prose added to agent docs — and sends them to
+version npm never published), prose added to agent docs and a work-object
+branch without documentation (no Markdown file naming the key, no
+`Doc-Decision:` trailer) — and sends them to
 `review_verdict` as a third finding class next to convention findings and risk
 flags (ADR-324).
 
@@ -123,9 +125,14 @@ 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 block by default; table ACL and
-agent-doc prose warn, because they encode an opinion — a team policy can
-override either way, with a reason.
+`baseline: introduced`). Objective detectors block by default; table ACL,
+agent-doc prose and the documentation decision warn, because they encode an
+opinion — a team policy can override either way, with a reason. The
+documentation decision additionally blocks in `maind gate` (and therefore in
+`maind feature promote`) when the organization set `doc_duty: require` and the
+work object has no linked document or exception yet — the server decides,
+because only it sees documentation from other PRs and repositories. Without
+an answer from the server the line reports and never blocks.
 
 `diff_stats.detector_coverage` reports whether every detector ran or honestly
 abstained (`full`), whether one could not run or could not grade against the