STATUS 2026-10-23 morning: D29-D31 to history; D32-D36 (the DooPlex survey and two website sentences); the morning list in the brief's order (hold or go, controller, agent + installer, hub 0.167.0, website, discards, the DooPlex hour); verdict of the test night at 07:00

2026-10-22 23:39:06 +02:00
parent 70a600d0c2
commit 1805f8bbf0
2 changed files with 26 additions and 11 deletions
@@ -5,6 +5,18 @@ 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-23
+
+**Updated 2026-10-22 (night).** Your seven picks of 15:47 are in effect or ready: D6 and D8 are live, D21 waits for the controller release, and D3, D5 (the website) and D4 (root SSH) are ready patches. Four controller fixes are built and proven on the scratch box, among them a gentler night copy (the 03:30 memory pressure) and no import over a stopped app. Nothing was released or deployed; the morning list below has the order.
+
+**Decided 2026-10-22 evening — CC's picks accepted** (the operator; each ruling is in its row, and in CONTEXT.md): D29 = no, the controller repository stays public for now (R-925); D30 = the agent makes a new key on the peer path that exists (R-1204); D31 = the hub skips a deleted install that never made a key (R-1205). The rows as they stood:
+
+| # | Row | Question | Pick (why) | The other option costs | If you do nothing | Blocked |
+|---|---|---|---|---|---|---|
+| D31 | R-1205 | After a box death, a second install that is deleted before it makes a key stops the automatic re-issue of the whole-box copy. Let the hub skip such a deletion, or keep your manual press? | **Skip it** (that install held no key, so nothing is lost — the same reasoning the key carry uses) | Keep the press: you get a mail and press „Re-issue PBS credentials” each time | that household gets no whole-box copy until you press | — |
+| D30 | R-1204 | After a box ran with its clock ahead, how does its tunnel to ep0 heal? | **The agent makes a new key and registers it** (the peer path that exists; nothing new on ep0) | ep0 removes and re-adds the peer on a hub-signed request: a new write path on ep0 | with hub 0.166.0 you get the alarm, and the repair is by hand on ep0 | the tunnel fix |
+| D29 | R-925 | Make the controller's repository private now? (felhom.eu, the agent and the catalog must stay public: the website, every install and every box read them with no login.) | **No, not now** (its image stays public anyway, and the no-secret gate is the control; look again when felhom.eu can go private) | Yes: a read token in CI for every repo that clones it, one more secret to keep | nothing changes | — |
+
 ## Moved from STATUS on 2026-10-22

 **Updated 2026-10-22 (day).** A rebuilt box no longer overwrites the family's saved mail list (hub 0.165.0, controller 0.339.0); demo-felhom's own list, replaced this morning, is back. The swap warning now fires only when a machine has clearly too little swap (your D28 = A).