@maind-dev/cli 0.70.0 → 0.71.1

package/README.md

@@ -89,9 +89,10 @@ The CLI never posts the comment itself — your workflow posts the file via
 | `--out <path>` | `.maind/review.md` | Report path (manifest lands next to it as `.json`) |
 | `--comment [<path>]` | off | Also write PR-comment markdown |
 | `--json` | off | Print the review manifest JSON to stdout |
-| `--gate` | off | Server-side `pass\|warn\|block` verdict (Team plan) |
+| `--gate` | off | Server-side `pass\|warn\|block` verdict (Team plan) — the server matches the changed symbols itself and records a replayable run (attest mode, below) |
 | `--fail-on block\|warn` | — | With `--gate`: exit `1` when the verdict crosses the threshold |
 | `--strict` | off | Infra errors exit `2` instead of failing open |
+| `--no-report` | off | With `--gate`: write no record — the verdict, and whether the run would be attestation-grade, are still computed |
 | `--project-key <hex>` | auto | Repo `project_key` override |
 | `--mcp-url <url>` | `$MAIND_MCP_URL` or prod | MCP endpoint override |
 
@@ -105,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 four repo-health detectors from
+With `--gate`, the CLI also runs the eight 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).
+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
+`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
@@ -120,9 +123,9 @@ 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.
+`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.
 
 `diff_stats.detector_coverage` reports whether every detector ran or honestly
 abstained (`full`), whether one could not run or could not grade against the
@@ -131,6 +134,50 @@ 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).
 
+### Attest mode (with `--gate`)
+
+Since `0.70.0`, `--gate` sends `review_verdict` what findings are made of — the
+changed symbols (up to 1000), the raw risk flags, the detector findings with one
+run entry per catalogued detector, diff statistics and the commit anchors —
+instead of findings the client assembled. The server matches the symbols against
+its full visible code-review convention set itself, so a client cannot leave a
+finding out, and records a **format-3** run that anyone with repo access can
+recompute (`maind verify`, below).
+
+A record is written only where it can be worth something: `--no-report`, a
+checkout without an `origin` remote, or a shallow clone without a merge base
+(use `fetch-depth: 0`) compute the verdict but write no record — the report says
+why. A server older than `0.62.0` rejects the call; the CLI then falls back to
+the legacy two-call path and says so.
+
+## Verify a record (`maind verify`)
+
+```bash
+maind verify <run-id>              # the record with this id (owner, org auditors)
+maind verify --commit <sha|ref>    # the best visible record for that commit (default HEAD)
+```
+
+Recomputes a `review_runs` record from a **clean scratch checkout** of its
+commit, diffed against the record's own base — not today's tip of the base
+branch — and lets the server compare under the record's policy snapshot. Nothing
+is persisted. The scratch checkout shares the repository's object database and
+is removed afterwards (`--keep-scratch` keeps it); a missing commit is fetched
+from `origin` by sha (`--no-fetch` forbids it) — a pull request head stays
+reachable after its branch is deleted. Needs `0.71.0` or later.
+
+| Code | Meaning |
+|---|---|
+| `0` | verified — inputs, environment and result are equal |
+| `1` | mismatch — at the same index version and merge base, the checkout yields different inputs than the record claims |
+| `3` | stale (same inputs, the convention corpus or engine moved — re-attest, not a forgery finding), unverifiable (legacy record, not attestation-grade), or not available (no record, no access, no plan) |
+| `2` | infrastructure error |
+
+Owners and org auditors can verify by record id; any member of the record's
+organization can verify by commit from a clone of the repository. `maind gate`
+runs the same check as its `attestation` line and never blocks on it: `ok` when
+the record for HEAD verifies, `REPORTED` on a mismatch, `NOT CHECKED` with the
+reason otherwise.
+
 ## Fail-open contract
 
 A context pull must never fail a build. On any error (missing key, network,