D52: the golden waiver renewed for 2026-10-26 only (expires 2026-10-27) — the Sunday bake was missed; the golden is baked today on v0.344.0 and the waiver goes after the vouch. D51 (Start) and D52 recorded (09 §3 263, 264; CONTEXT; STATUS-HISTORY).

documentation/architecture/09-update-architecture.md

@@ -1099,6 +1099,18 @@ its length, and both fixes cost something the household would notice — operato
      `plex: security fix CVE-2026-96652,CVE-2026-96654,CVE-2026-96655,CVE-2026-96656 taken` and ended `done` in 30.1 s
      after the update's second-drive copy and undo copy. Released as controller 0.341.0, global floor 11:24 UTC.
 
+### 2026-10-26 (attended release run) — D51: Kimai's hold; D52: the missed weekly golden
+
+263. **demo-hp's Kimai, held by the crash-loop guard since the 2026-10-14 power drill, is started again, not removed
+     (D51 = Start).** *Operator, 2026-10-26 07:57.* Options: A) Start — cost: if it crash-loops again it is held again;
+     B) remove it through the product — cost: the test app and its data are gone. Why A: the household's Start is the
+     designed way to lift this kind of hold (decision 28), and it is a test box. Result: hold lifted, healthy (R-1286).
+264. **The missed Sunday bake is made up the same day, on the new controller, and the waiver covers that one day only
+     (D52 = bake today on v0.344.0).** *Operator, 2026-10-26.* Options: A) renew the waiver to the next Sunday — cost: a
+     week of new installs on a golden 13 releases behind; B) bake today — cost: about an hour of the release day. Why B:
+     the gate goes green by a fresh golden, not by a waiver. The weekly Sunday bake (`runbooks/nightly-rotation.md`)
+     stays the rule; every Sunday-night brief names it.
+
 ### 2026-10-25 (evening, attended) — D50: which agent packages the registry keeps
 
 262. **The registry keeps the newest 5 released agent versions, plus the hub's MinAgent floor, plus the version the hub's