REPORT/CHANGELOG: F3 capstone live-validated (re-provision onboot:1 + host-reboot auto-start)

Destroyed + re-provisioned 9201 through the real provision chain with v0.41.0: fresh pct config
showed onboot:1 with no manual set. Host reboot of felhom-pve -> 9201 auto-started (running, no
manual pct start); onboot:0 scratch guests stayed stopped; drives re-bound at stable, sys_drive
separate, controller + infra healthy. Demo controller redeployed to v0.82.0.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FpBYrZCt9sFDqLgbG5GRGD

CHANGELOG.md

@@ -18,8 +18,11 @@ The **golden stays `onboot:0`** (`build-golden.sh` unchanged): a template must n
 `onboot` is a per-guest property the back-half is the right place to set. Unit-tested
 (`TestProvision_SetsOnbootOne` asserts the exact `pct set … -onboot 1` invocation, with a red-proof
 against removing the call). The pre-existing demo guest 9201 (provisioned pre-fix) was remediated
-non-destructively with `pct set 9201 -onboot 1`. Full back-half validation rides with the deferred
-supervised capstone re-provision (assert a freshly-provisioned guest is `onboot:1` with no manual set).
+non-destructively with `pct set 9201 -onboot 1`. **Capstone live-validated (2026-06-24):** destroyed +
+re-provisioned 9201 through the real provision chain with v0.41.0 → fresh `pct config` showed `onboot: 1`
+with no manual set; a subsequent **felhom-pve host reboot** brought 9201 back **running with no manual
+`pct start`** (the `onboot:0` scratch guests correctly stayed stopped), controller + base infra healthy,
+drives re-bound at stable, sys_drive separate — the exact Phase-4.1 failure now passes.
 
 ## v0.40.0 — third CT volume: SSD user-data (`/mnt/sys_drive`, mp1) baked + `-sysdata-grow` (2026-06-23)