Linux strict security lane (G-C) / strict isolation escape matrix (push) Waiting to run
ci/woodpecker/push/main Pipeline was successful
ci/woodpecker/manual/performance Pipeline was successful
CI / fmt + clippy + test (Linux x86_64) (push) Waiting to run
CI / schema instance validation + consumers (push) Waiting to run
CI / runtime contract (macos-latest) (push) Waiting to run
CI / runtime contract (windows-latest) (push) Waiting to run
REL-01: workspace/CLI/Analysis product version 3.0.0-beta.1 with updated Cargo.lock; project.marqdo is enforced against the running core with package.marqdo_range_invalid/package.marqdo_incompatible fail-closed diagnostics; Tool SemVer prerelease negotiation tests; init template and examples use the beta range. Verify init derives the project name from the target directory instead of falling back to 'example'. REL-02: beta support matrix is Linux x86_64 only; macOS/Windows are explicitly experimental/unclaimed; strict policy and G4 Beta-only WARN are documented for the release evidence. REL-03: deterministic release packaging (tools/release/package.py) ships the CLI and provider worker together with SOURCE_SHA, RELEASE_INFO.json, known-limitations, specs, developer docs, examples incl. built plugin/provider artifacts and consumers; tools/release/smoke.py cold-install tests the archive. REL-04: docs/developers entry pages; corrected and self-contained third-party integration handbook; stale Proposed/native-only/informational spec claims fixed; release/status/compatibility/changelog/releasing docs updated. REL-05: release_evidence.py gains an explicit beta profile (BETA_RELEASE_CANDIDATE) distinct from the stable profile; Woodpecker build step now packages and smoke-tests the archive on every pipeline. Adds a runnable Resource Provider v2 example and corrects check --emit to Analysis v2.
CI evidence tools
strict-evidence.py
Writes marqdo.strict-evidence.v1, called by tests/security/run-lane.sh when
MARQDO_STRICT_EVIDENCE is set and by the self-hosted security workflow. It
records only measured or explicitly supplied facts:
tested_shaand whether it came fromgit rev-parseor an operator env;- source archive SHA256 (and whether it matched the expected digest);
- kernel/uname/cgroup2/container,
uid/root, bwrap/rustc/cargo/cc versions; - runner kind, image digest, run URL, start/finish and outcome.
A root-only PASS is rejected. PASS from a container or a persistent
self-hosted runner with production credentials is not valid G-C evidence; see
docs/security-vm.md.
release_evidence.py
Aggregates per-gate results into marqdo.release-gates.v1:
python3 tools/ci/release_evidence.py \
--target-sha "$SHA" \
--gate "linux=PASS:$SHA:https://ci.example/run/1" \
--gate "windows=PASS:$SHA:https://ci.example/run/2" \
--gate "macos=PASS:$SHA:https://ci.example/run/3" \
--gate "strict_vm=PASS:$SHA:https://ci.example/run/4" \
--gate "performance=WARN:$SHA:https://ci.example/run/5" \
--out "docs/evidence/ci/$SHA/manifest.json"
A missing gate becomes UNVERIFIED. Any non-PASS required gate, a
tested_sha different from target_sha, an unknown gate name or a malformed
SHA forces DO_NOT_RELEASE. performance may be PASS or WARN.
Unit tests: python3 -m unittest discover -s tools/ci -p 'test_*.py'.