take-two re-drill record: zero-stop Day-0 on v1.15.0/0.86.0/0.51.0 — 1h22m, hands-free DR cascade, floor-update first proof, offsite round-trip; new findings F-14/F-15/F-16

Claude-Session: https://claude.ai/code/session_01NptTCFtu7dz2Ru89qHRagN
This commit is contained in:
2026-07-12 23:13:29 +02:00
parent ccf89c0a67
commit 11d0f55303
2 changed files with 87 additions and 5 deletions
+10 -5
View File
@@ -42,9 +42,14 @@ by `pbsdr.Manager.DRConfigured` (marker-backed); F-3 root-run provision parent c
(`--reference`, non-recursive). felhom-pve's latent F-3 state confirmed + fixed live; Peti's box
unreachable (check deferred).
### Pending (deploy + validation phase)
### Deployed + LIVE-VALIDATED (same evening)
Build/deploy hub 0.51.0 (ArgoCD manifest bump) + agent 0.86.0 (felhom-pve + publish + Day-0
manifest vouch) + installer serve-verify; then the §13 "Day-0 take two" re-drill on qm 300 —
**requires Viktor's GO** (rolls back to `pre-day0-clean`, deletes the drill escrow via the
stale-host flow). Scenario B/C hub-side validation via tests + UI screenshots (drill box stays ON).
All three artifacts deployed: hub 0.51.0 (ArgoCD Synced/Healthy, auto-provision hook armed),
agent 0.86.0 (felhom-pve `ok=62 degraded=0`, published `d77355c5…`, Day-0 manifest vouched),
installer v1.15.0 served. **§13 take-two re-drill EXECUTED with Viktor (GO given): the entire
drill §5 sequence completed with ZERO fix-and-continue stops in 1h 22m (vs 1h 55m)** — all
F-fixes proven on a fresh box, scenario A hands-free cascade fired 1 s after WG registration,
auto-confirm 6m 39s, floor-driven self-update 0.120→0.122 FIRST LIVE PROOF, offsite round-trip
proven (1 snapshot → 48K verification restore). Full record + metrics + new findings
(F-14 tenancy re-attach dead-end, F-15 reset-code lag — operator must-fix, F-16 hub native
confirm()): `documentation/audits/DRILL-day0-take2-2026-07-12.md`.