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.
External-extension evidence
RFC-EXT-0001 §10.2/§11.3 requires SHA-bound proof that an unchanged CLI binary can use extensions from physically separate Git repositories. This directory holds that evidence.
schema.json— JSON Schema for the evidence manifest.<40-hex-source-SHA>/manifest.json— generated bytools/ci/verify_extension_contracts.py; never hand-written.
Generation (from a clean fixture checkout and a release build of this repo):
cargo build --release --locked -p marqdo-cli
CLI="$(realpath target/release/marqdo)"
python3 tools/ci/verify_extension_contracts.py \
--cli "$CLI" \
--fixtures /path/to/marqdo-extension-conformance
python3 tools/ci/verify_extension_contracts.py \
--validate docs/evidence/extension/<SHA>/manifest.json
The generator refuses to write evidence when:
- the CLI binary hash changes between the start and end of the suite;
- the fixture repository has uncommitted changes;
- a required result is missing or
FAIL; UNSUPPORTED/SKIPPEDis recorded without--allow-unverifiedand a report entry explaining the platform limitation.
A local or container run is not a substitute for the release gates in
docs/releasing.md (G3/G4), and no tag is created by this evidence.