felhom-controller/REPORT.md

REPORT — v0.348.0 released as the global floor: „Clear hold" from the hub (2026-10-29, attended)

Plain words first. The controller 0.348.0 is the floor for every box since 14:48 CET. The operator can now clear any held app from the hub (D64 = B); the running controller clears it and saves at once, so a later save cannot bring it back (R-1343). The box command (--clear-restore-hold) goes through the running controller too. The held-app mail names the real cause (R-1340), the OOM line is logged once per kill (R-1341), and a restore copy cannot be deleted during the 30-minute stable-start watch (R-1342).

Commits

Commit	CI (job id)	What
652a690	2500 green	R-1342 (from the morning, first released now).
5b3b541	2508 green	clear_hold in the closed operator-action list; the socket <data>/ctl/hold.sock (0600 in a 0700 folder, peer uid checked); ClearHoldByOperator also drops a waiting put-back from the app-stop marker; R-1340 hold mail from the hold record; R-1341 OOM line once per kill. Tests red first.
6077ac0	2509 green	R-1343 fallback: with no controller running, the box command's own edit goes through the same clear door. Test red first.
99fac06	2514 green	R-1340 second producer: RestoreHold.Why() builds the restore_mixed text from the record (found live on rc.1). Test red first.
2a0a17a	2515 green	v0.348.0 CHANGELOG heading — the release build's commit. MinAgent 0.158.1.

Release

• rc.1 (5b3b541+) and rc.2 (2a0a17a, sha256:1d96f60c…) on 9202; the walk green on rc.2 (6 containers, 0 errors, login and file manager 200; the hold socket present).
• 0.348.0 from a clean clone of 2a0a17a: sha256:672fc1c1deaaf1cbeecfc2c5b04da731b076a9194f4ce7ed9678339fcd4548bf.
• Per-box floors 14:41 CET (Tester 1, demo-hp, demo-felhom; MinAgent 0.158.1): all three on 0.348.0 within 25 s; the walk green on all three (no unhealthy container, 0 refusals, 0 ERROR lines, login and file manager 200, the socket 0600) and https_only_check.py green.
• Global floor 14:48 CET on the operator's yes (303 floor_set; the hub page and the hub log read 0.348.0 / 0.158.1).

Live proofs (Tester 1)

• Clear from the hub, crash-loop hold (rc.1): pressed 13:44 CET; gone on the box and on the hub; still gone after the next settings save (14:00:45). No false app_start_failed after the clear in 18 minutes (F2: NOT-A-FINDING).
• Clear from the hub, restore_mixed hold (fault test build): the page showed the data warning; cleared; the copy kept.
• R-1340: the mixed-hold mail names a local restore, the failed put-back stop and the kept copy; no „database".
• R-1341: one WARN line over 4 scans; one app_oom event.
• R-1342 (rc.1): the list says „checking", the button is off, a delete gets 409; removing the app ended the watch with no alarm.
• On the release builds: see the felhom.eu report REPORT-release-2026-10-29b.md (one restart, one clear).

Evidence: felhom.eu documentation/audits/release-2026-10-29b/ (p3-clear-hold/, release-controller-0.348.0/, final/).