docs: F9/F20-BUG2/F20-BUG3 FIXED (agent v0.31.0, live-validated); queue golden controller-tag follow-up

documentation/backlog/FOLLOWUP-golden-default-controller-tag.md

@@ -0,0 +1,32 @@
+# 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).
+
+## The problem
+`felhom-agent/configs/build-golden.sh:43` bakes the controller image into the golden as:
+
+```
+CONTROLLER_IMAGE="${6:-gitea.dooplex.hu/admin/felhom-controller:0.43.0}"
+```
+
+`:0.43.0` is ~20 versions stale (current is `0.63.0`). The bootstrap writes it to
+`/etc/felhom-controller-image` and `docker run`s that tag on first boot. So the **next time a golden is
+actually baked for a real provision, it would stand a customer guest up on an ancient controller** —
+missing every fix since 0.43.0 (incl. F1 memory guard, F17 DB restore, the M18/M19 fixes, etc.). It only
+hasn't bitten because the running demo guest 9201 had its `/etc/felhom-controller-image` updated in place
+post-provision; a fresh provision would not.
+
+This is why the F9 session chose **attach-to-existing** over destroy+re-provision (a re-provision would
+have regressed 9201's controller 0.62.0 → 0.43.0).
+
+## The fix (separate task)
+1. Bump the `build-golden.sh` default `CONTROLLER_IMAGE` to the current released controller tag (and
+   establish a convention so it tracks releases — e.g. read a `LATEST_CONTROLLER` pin, or pass it
+   explicitly from the build pipeline).
+2. **Validate the full path end-to-end**, which *does* warrant a supervised destroy + re-provision (it is
+   the real customer-onboarding flow, not coverable by attach-to-existing): bake golden → provision a
+   scratch guest → first boot stands up the **current** controller → controller ONLINE on the hub →
+   enrolled user-data drive is bound (F9 `ReassertGuestBinds` / provision bind) → an app deploys.
+3. While there: confirm the provision path itself asserts known user-data binds (F9 part A for the
+   re-provision case, complementing the agent-startup re-assert already shipped in v0.31.0).

documentation/backlog/README.md

@@ -9,6 +9,10 @@ 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.
+
 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
 mkfs) — to be implemented in the agent/golden supervised session.