Make a passing CI/release result mean the checks actually ran.
- .forgejo/workflows/ci.yml is fail-closed: it provisions the pinned
toolchain or fails, then runs one 'make ci' (fmt-check, clippy, workspace
tests, VM-harness safety tests, release build, static installer build).
- Pin stable Rust 1.93.1 in installer-rs/rust-toolchain.toml; run cargo gates
with --locked for reproducible dependencies.
- phoebus-release gates now records passed/failed/blocked/skipped/not_run
(only passed is a pass), executes real host gate commands, and imports the
existing VM-harness results.json instead of a competing harness. Gates with
no automation are always blocked.
- Bind gate reports and harness evidence to a candidate name+SHA-256
(--candidate; PHOEBUS_VM_ARTIFACT[_SHA256]); stale or unbound evidence is
failed, never passed.
- publish refuses unless the report is candidate-bound and all-passed, the
manifest verifies the artifact and a detached signature verifies; atomic
publish preserves and restores the previous release on failure.
- vmsafety.Results records the verified artifact digest; 3 new Python tests.
- 20 new Rust regression tests; ADR 0012 and docs updated.
Verified locally: make ci (364 Rust tests, 19 harness tests, release and
static builds) exit 0; static binary is static-pie linked. CI runner, VM and
model gates remain unexecuted here.