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
Linux strict security lane (G-C) / strict isolation escape matrix (push) Waiting to run
ci/woodpecker/push/woodpecker Pipeline was successful
The built-in Python provider scanned PATH for the extension-less token python3; a Windows PATH contains python3.exe, so a working interpreter was reported as kernel.unavailable and the semantic golden suite failed on windows-latest. Expand candidates with PATHEXT (conservative default) and use the same platform-aware resolver in the conformance test's availability probe. Also make native failures diagnosable: strip ANSI before matching and emit the panic/build context as public check annotations, and run Linux tests through the same annotator. This fixes the Windows native lane and gives the macOS failure the context needed to diagnose it.
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'.