Files
felhom.eu/documentation/tests/golden-0.276.0-2026-09-28/README.md
T

1.8 KiB

Golden 0.276.0 — baked, published and vouched 2026-09-28

The weekly bake (operator ruling 2026-09-13, R-468), and the one before a fresh install: the Day-0 test install of the same session installed from it. The operator asked for it on 2026-09-27 together with vouching agent 0.137.0.

GOLDEN_VERSION 0.276.0 (controller image gitea.dooplex.hu/admin/felhom-controller:0.276.0)
GOLDEN_SHA256 d8e273930953f400afa62b356753d4a99fd9a330cf174436c7096a2307cc4a23
archive 654 383 234 B (anonymous download, sha re-computed off the registry: identical)
template debian-13-standard_13.6-1_amd64.tar.zst — listed with pveam available on the day, not assumed
markers docker OK (overlay2 1 · including mount point 2 (rootfs, mp0) · upload OK (HTTP 201) 1 · excluding 0 · FATAL 0
token leak 0 in the committed bake.log; the planted control (a throwaway copy with the token appended) read 1
registry …/generic/felhom-golden/0.276.0/golden.tar.zst → 404 before, 200 after
teardown CT 9100 destroyed --purge; token, runner and log shredded inside the VM; qemu exited; drill.qcow2 reverted to virgin
vouched Artifact manifest set: agent=0.137.0 golden=0.276.0 min_agent="0.131.0" — the R-120 gate refused golden 0.258.0 first (negative control)
proven a Day-0 install in the drill VM fetched agent 0.137.0 and golden 0.276.0 through the manifest, both sha-verified; the controller answered healthy at 0.276.0

Deviation: the first attempt picked the arm64 template (the driver sorted both arches) and was stopped by CC before the container was created; nothing was published. The attempt's log and note: documentation/audits/evidence-golden-0276-2026-09-28/phaseA-*-ATTEMPT1-aborted.*. Full evidence of the run: the same folder.