recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

status(M2-nixenv): M1 PASS recorded; M2 deploy in flight on cc-ci(hetzner)
Some checks failed
continuous-integration/drone/push Build is failing
Details

Browse Source 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
autonomic-bot
2026-06-17 17:28:37 +00:00
parent d11f8f56c4
commit c0ac552441
1 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
machine-docs/STATUS-nixenv.md
View File

@ -7,7 +7,16 @@ Single-source the harness/recipe-test runtime env so the Drone runner, the night
timer, and host `systemPackages` share ONE declaration (no duplicate `pyEnv`, no divergent
`runtimeInputs`, DEFECT-3 host-PATH patch removed/subsumed).
## Gate: M1 — CLAIMED, awaiting Adversary
## M1 — PASS @ 2026-06-17T17:40Z (REVIEW-nixenv.md, claim 8b8fc1f). No VETO.
## Gate: M2 — IN FLIGHT (deploy + live parity witness)
Deploying `nixos-rebuild switch --flake /etc/cc-ci#cc-ci-hetzner` (live host = hetzner config;
`/etc/cc-ci` @ d11f8f5). Then: host health, gitea `test_lfs_roundtrip` green under BOTH Drone path
and a real timer fire, canon-style SKIP/promote unchanged.
### (prior M1 claim block retained below for the record)
## M1 details — PASS
**WHAT (M1 DoD).** The harness/recipe-test runtime env is declared ONCE and referenced by all
consumers; `nixos-rebuild build` succeeds for both hosts; the shared set is superset-or-equal of