ci/woodpecker/push/main Pipeline was successful
Linux strict security lane (G-C) / strict isolation escape matrix (push) Canceled after 0s
CI / fmt + clippy + test (Linux x86_64) (push) Canceled after 0s
CI / schema instance validation + consumers (push) Canceled after 0s
CI / runtime contract (macos-latest) (push) Canceled after 0s
CI / runtime contract (windows-latest) (push) Canceled after 0s
CI / release evidence manifest (push) Canceled after 0s
CI / release candidate artifact (macos-latest) (push) Canceled after 0s
CI / release candidate artifact (ubuntu-latest) (push) Canceled after 0s
Records the tagged SHA 2c7c4f31e7 evidence:
same-SHA Woodpecker pipeline #37 PASS (including archive build + cold-install
smoke), fixed-node G4 #38 MEASURED/WARN with 9/9 correctness, the same-SHA
disposable-VM strict G3 PASS, the frozen-binary external conformance manifest
(7/7 categories, unchanged CLI hash), and the archive-only clean-install smoke.
Adds docs/evidence/ci/<sha>/manifest.json in the explicit beta profile
(BETA_RELEASE_CANDIDATE), the strict evidence JSON/log, the G4 report, the
release gate record, the third-party handbook validation matrix/log, and the
user-facing 3.0.0-beta.1 release notes. Updates STATUS, COMPATIBILITY, CURRENT,
CHANGELOG, README, security-gate and the prerelease plan to the exact released
SHA, tag, release URL and archive hashes. No source code changes after the tag.
CI release-evidence manifests
docs/evidence/ci/<full-40-hex-sha>/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 arelinux,windows,macos,strict_vm; every one must bePASSontarget_sha, andperformancemust bePASS/WARN.beta— the supported scope is declared byCOMPATIBILITY.md(3.0.0-beta.1: Linux x86_64 only). Required gates arelinux,strict_vm,extension,clean_install,version_compat;windows/macosmust be explicitly present asUNSUPPORTED(not silently omitted);strict_vmmay beUNSUPPORTEDonly when the tested policy is an explicit fail-closed refusal;performancemay beWARNwith the environment recorded. Decision:BETA_RELEASE_CANDIDATE.
Rules:
- every gate records its own
tested_sha; it must equaltarget_sha; - skipped, cancelled, queued, timed-out, missing or older-SHA jobs are
UNVERIFIED/FAIL, neverPASS; strict_vmneeds a real disposable-VMstrict-evidence.json(schemamarqdo.strict-evidence.v1) withoutcome: PASS, non-rootuidand the same SHA; a URL alone is not enough;performanceneeds aMEASUREDreport from the fixed node; TCG/QEMU or development-container numbers are not a baseline;release_decisionisRELEASE_CANDIDATE(stable) orBETA_RELEASE_CANDIDATE(beta) only when every required gate is satisfied with the same SHA. Anything else isDO_NOT_RELEASE.
The manifest is evidence, not permission to tag; owner approval is separate.