docs: record D53, D54 and R-1297 (B) (09 §3 decisions 265-267); STATUS moves the two picks to history

documentation/architecture/09-update-architecture.md

@@ -1099,6 +1099,23 @@ 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 (evening brief) — D53: held apps reach the operator; D54: demo-hp's stuck clean-up; R-1297 (B): a second CI runner
+
+265. **A held app reaches the OPERATOR first, never the household (D53 = operator-only reminders first).** *Operator,
+     2026-10-26 evening (starting the brief is the yes).* Options: A) operator only — cost: a household whose app is held
+     still learns only from the app's page; B) the operator and, for the two holds a household can clear, the household
+     too — cost: two more customer mails to write and translate, about a stop they may not understand. Why A: the
+     operator can act on every reason; household mails can follow once the operator list has run. Built from `08` §10.
+266. **demo-hp's off-site store gets ONE clean-up window with a raised cap of 220, through the hub's existing one-shot
+     grant; the cap rule itself is unchanged (D54 = prune once).** *Operator, 2026-10-26 evening.* Options: A) a one-shot
+     grant — cost: one window prunes 209 snapshots at once on a test box (the plan was read honest, R-1294); B) change the
+     cap rule — cost: hub and controller code, and a weaker guard against a mass deletion on every box. Why A: the guard
+     stays as strong as it is; the grant expires after one use.
+267. **CI gets a second runner on DooPlex; both runners have 2 CPUs (R-1297 B).** *Done by the operator, 2026-10-26.*
+     Options: A) a second runner — cost: DooPlex CPU while two jobs run; B) only trim the suites — cost: every repo's job
+     still queues behind felhom.eu's run. Why both (the operator's „both"): the trim makes one run short, the runner stops
+     the queue. The trim (A) is CC's and keeps every check (path filters, a tag run and a nightly run).
+
 ### 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