golden 0.287.0 — 2026-10-02 (controller v0.287.0: the family gate, R-780)
Baked in the drill VM on DooPlex per RUNBOOK-manual-build.md §4.0/§4.1 by bake-driver.sh (this folder; the token goes
file → file and is read inside the VM; the driver wrote bake-full.log, renamed bake.log after the run). Markers:
overlay2 1, mount points rootfs + mp0, upload OK (HTTP 201), FATAL 0, excluding 0.
GOLDEN_SHA256=c95fbd9c62accd8b7ff6cf4edd4a19fcebb4e09cb40e0bbb3b03d2e8ee904b65.
Token leak: 0 in the unit, 0 in the saved log, positive control 1. Registry range-GET 206; an anonymous full download
(651 452 967 bytes) hashes to the same sha (02-round-trip.txt). Vouched — three fields: golden 0.287.0, agent 0.138.0,
min_agent 0.131.0 (the v0.287.0 CHANGELOG header); the R-120 gate then refused golden 0.286.1 (05-vouch.txt).
Teardown: CT 9100 destroyed, secrets shredded (3/3), qemu exited, the disk reverted to virgin.
Why baked now (not on the weekly cadence): the catalog's check-family-gate.py refuses a family_gate: true template while
the newest baked golden is older than 0.287.0 — a box installed from 0.286.1 would publish Grimmory and MeTube OPEN until
its first self-update.