CI / runtime contract (macos-latest) (push) Waiting to run
CI / runtime contract (windows-latest) (push) Waiting to run
Linux strict security lane (G-C) / strict isolation escape matrix (push) Waiting to run
CI / fmt + clippy + test (Linux x86_64) (push) Waiting to run
CI / schema instance validation + consumers (push) Waiting to run
ci/woodpecker/push/main Pipeline was successful
The manual .woodpecker/performance.yml workflow ran on the designated fixed agent (platform_id woodpecker-agent-1): 5 warmups + 20 samples, all 9 workloads correctness-verified, CPU 0 pinned from the container cpuset. Two runs differed by -10.9%..+7.1% p50 and -1.9% RSS. The node is a shared Docker container with the powersave governor and loadavg ~5.7-6.1, so the release gate is WARN, not PASS, and comparisons are same-platform only. Store both marqdo.perf.v2 reports and the SHA-bound release manifest. The manifest is DO_NOT_RELEASE only because strict_vm remains UNVERIFIED; Linux, Windows, macOS and performance have real same-SHA results.
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 uploaded
by the release-evidence CI job. Do not hand-edit a manifest into PASS.
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_CANDIDATEonly when every required gate is PASS with the same SHA and performance is PASS/WARN. Anything else isDO_NOT_RELEASE.
The manifest is evidence, not permission to tag; owner approval is separate.