admin/felhom.eu
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: golden 0.98.3 live — D.1b retired, drill B1/B5 fixed, backlog note resolved + evidence doc

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PSK5g6qYLknKj8u3QAFEr6
This commit is contained in:
authentik Default Admin
2026-07-03 18:38:28 +02:00
parent 2e33a8b86b
commit 7ad111cfb5
8 changed files with 339 additions and 96 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/backlog/FOLLOWUP-golden-default-controller-tag.md
+10 -2
View File
@@ -1,7 +1,15 @@
# FOLLOW-UP — bump the golden's default controller tag + validate the full provision path
**Status:** OPEN (queued 2026-06-14). Surfaced during the F9/F20 supervised session (agent v0.31.0).
**Class:** provisioning correctness / customer-onboarding. **Risk:** SUPERVISED (golden + a real destroy→provision).
**Status:** **RESOLVED 2026-07-03** — `build-golden.sh` v2.0.0 (felhom-agent @ `ceca355`) makes the
controller tag a MANDATORY argument (the hand-bumped default had rotted AGAIN, 0.43.0 → 0.85.1 →
stale vs 0.98.3 — a required arg cannot rot); golden **0.98.3** baked + validated clean-room on the
drill VM (first boot lands the current controller, self-update reports up-to-date, app deploys) +
published + operator-vouched. The full first-boot path was validated WITHOUT a supervised
destroy→re-provision (drill VM virgin snapshot instead — nothing touched 9201/felhom-pve).
Evidence: `../audits/DRILL-golden-098-2026-07-03.md`. Item 3 (provision re-asserting user-data
binds) was shipped separately (agent-startup re-assert + F9 part A). Original note kept below for
history.
**Class:** provisioning correctness / customer-onboarding. **Risk (as queued):** SUPERVISED (golden + a real destroy→provision).
## The problem
`felhom-agent/configs/build-golden.sh:43` bakes the controller image into the golden as:
documentation/backlog/README.md
+6 -3
View File
@@ -9,9 +9,12 @@ Verified-LIVE findings with implementable fix plans that are **not yet implement
- **FIX-M19-NOTES.md** — `deriveStackName` misattribution edge (low-incidence correctness). **FIXED** in
controller v0.62.0 @ `6bab68b` (2026-06-14). (was on the deleted branch `fix/m19-stackname-crossref`.)
- **FOLLOWUP-golden-default-controller-tag.md** — the golden bakes a stale controller `:0.43.0`
(`build-golden.sh:43`); a fresh provision would stand up an ancient controller. Bump it + validate the
full destroy→provision→first-boot path (warrants a supervised re-provision). Queued 2026-06-14.
- **FOLLOWUP-golden-default-controller-tag.md** — the golden bakes a stale controller (`:0.43.0` when
queued; had rotted again to `:0.85.1` by resolution). **FIXED** in felhom-agent @ `ceca355`
(2026-07-03): `build-golden.sh` v2.0.0 makes the controller tag a MANDATORY argument (a required arg
cannot rot) and golden **0.98.3** was baked + clean-room-validated (bake → first-boot-current →
self-manage → app deploy, on the drill VM — no supervised touch of live guests needed) + published +
vouched. Evidence: `../audits/DRILL-golden-098-2026-07-03.md`.
Related: the live-drive fixspec (`../audits/live-drive-fixspec-2026-06-14.md`) carries the **deferred
supervised items** F9 (HDD provisioning/guest-attach), F20-BUG2 (durable_id scheme), F20-BUG3 (async