# CI release-evidence manifests `docs/evidence/ci//manifest.json` is generated by `tools/ci/release_evidence.py` (schema `marqdo.release-gates.v1`) and recorded for the release. Do not hand-edit a manifest into `PASS`. Two profiles are explicit in the manifest (`profile` field): * `stable` — required gates are `linux`, `windows`, `macos`, `strict_vm`; every one must be `PASS` on `target_sha`, and `performance` must be `PASS`/`WARN`. * `beta` — the supported scope is declared by `COMPATIBILITY.md` (`3.0.0-beta.1`: Linux x86_64 only). Required gates are `linux`, `strict_vm`, `extension`, `clean_install`, `version_compat`; `windows`/`macos` must be explicitly present as `UNSUPPORTED` (not silently omitted); `strict_vm` may be `UNSUPPORTED` only when the tested policy is an explicit fail-closed refusal; `performance` may be `WARN` with the environment recorded. Decision: `BETA_RELEASE_CANDIDATE`. Rules: * every gate records its own `tested_sha`; it must equal `target_sha`; * skipped, cancelled, queued, timed-out, missing or older-SHA jobs are `UNVERIFIED`/`FAIL`, never `PASS`; * `strict_vm` needs a real disposable-VM `strict-evidence.json` (schema `marqdo.strict-evidence.v1`) with `outcome: PASS`, non-root `uid` and the same SHA; a URL alone is not enough; * `performance` needs a `MEASURED` report from the fixed node; TCG/QEMU or development-container numbers are not a baseline; * `release_decision` is `RELEASE_CANDIDATE` (stable) or `BETA_RELEASE_CANDIDATE` (beta) only when every required gate is satisfied with the same SHA. Anything else is `DO_NOT_RELEASE`. The manifest is evidence, not permission to tag; owner approval is separate.