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).

CONTEXT.md

@@ -16,6 +16,13 @@
 > and holds nothing of its own; this file does hold its own content, namely the standing rulings below.
 
 
+> **2026-10-26 (attended release run) — D51 = Start; D52 = bake the golden today on v0.344.0.** (`09` §3 decisions 263,
+> 264.) D51: the operator pressed Start on demo-hp's Kimai (07:57 local); the crash-loop hold lifted, both containers
+> healthy, 0 restarts (R-1286). D52: the Sunday 2026-10-25 bake was missed (not in that night's brief); the golden waiver
+> is renewed for 2026-10-26 only (`expires: 2026-10-27`) so the release commits can be pushed; the golden is baked on
+> v0.344.0 the same day and the waiver is removed after the vouch. The weekly Sunday bake stays the rule; every
+> Sunday-night brief names it.
+
 > **2026-10-25 night (unattended, commit only) — the night's fixes, each red-proved; proven live on a BYO test VM (demo-hp
 > VM 9372, customer Tester4, agent 0.165.0, controller rc.1–rc.3).** Controller (`a79a292`…`7ea942a`, rides v0.344.0):
 > R-1261 the line hold holds EVERY running seeder, drops a removed app's record, names qBittorrent's slot (`up_limit` /

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

documentation/backlog/STATUS-HISTORY.md

@@ -5,6 +5,12 @@ Moved here byte for byte on 2026-10-14 (night session), newest first, so that `S
 
 **Updated 2026-10-13 (night): demo-hp, demo-felhom and Tester 1 run agent 0.155.0; demo-felhom runs controller 0.310.0, the other two 0.309.0 until the floor is raised. The open-items list is at 127. Reports: `REPORT-poweroff.md`, `REPORT-plugmeter.md`, `REPORT-usenet-2026-10-12.md`, `REPORT-newapps-2026-10-12.md`, `REPORT-disk-evening-2026-10-12.md`, `REPORT-answers-2026-10-12.md`, `REPORT-m3-2026-10-11.md`, `REPORT-redesign-2026-10-10.md`, `REPORT-testers-2026-10-10.md`, `REPORT-register-shrink-2026-10-10.md`, `REPORT-new-apps-2026-10-10.md`, `REPORT-release-2026-10-10.md`, `REPORT-break-the-circle-2026-10-09.md`, `REPORT-dooplex-survival-2026-10-09.md`, `REPORT-day4-2026-10-09.md`.**
 
+## Moved from STATUS on 2026-10-26 (attended release run)
+
+| D51 | R-1286 | demo-hp's Kimai was stopped by the crash-loop guard on 10-14 (the power drill) and is still held. Start it again, or remove it? | **Press Start** (it lifts this kind of hold; if it crash-loops again it is held again and we look) | remove it through the product: the test app and its data are gone | it stays stopped; nothing else waits on it | — |
+
+**Ruled:** D51 = Start (operator, 2026-10-26 07:57; `09` §3 decision 263) — healthy, 0 restarts. D52 = bake the golden today on v0.344.0 (operator, 2026-10-26; decision 264) — asked in chat, never on the page; the waiver covers 2026-10-26 only.
+
 ## Moved from STATUS on 2026-10-26 (morning)
 
 **Updated 2026-10-25 (evening, attended release).** Every box runs the new controller: a restore that does not start says so and keeps both copies (D49), a reinstall never touches the old backup, a restore downloads first. The hub stores the recovery package in one step; the new agent is vouched; the catalog has three fixes.

documentation/tests/golden-waiver.yml

@@ -11,7 +11,10 @@
 # the weekly due date.
 # 2026-10-14: goldens 0.310.0 and 0.311.0 were baked the same day (`golden-0.311.0-2026-10-14/`), so the golden is at
 # the newest controller and this waiver covers nothing today. It stays until its date for a release before the next bake.
-issued: 2026-10-13
-expires: 2026-10-20
-reason: pre-customer development; goldens on a weekly cadence (operator ruling 2026-09-13)
+# 2026-10-26 by CC, on the operator's D52 (bake today on v0.344.0): the Sunday 2026-10-25 bake was missed (it was not in
+# that night's brief); golden 0.331.0 is 8 days old. Renewed for TODAY ONLY so the release commits can be pushed; the
+# gate is green tomorrow by the new golden, and this waiver is removed after the vouch.
+issued: 2026-10-26
+expires: 2026-10-27
+reason: D52: bake on v0.344.0 the same day
 register_row: R-468