gates / gates (push) Successful in 2m1s
The close-out of the attended release run of 2026-11-10 (afternoon). - Evidence: documentation/audits/release-space-fixes-2026-11-10/ (agent, controller, hub) and the hub row after the fallback-kernel test. - Rows: dated lines on R-1368, R-1371, R-1301, R-1353. 236 open before and after; opened 0, closed 0. - Capability map: dated notes under C13 and G5; no status changed. - disk-full runbook and 16 §14: the self-update folder is PROVEN as a product path on three test boxes. - STATUS: new "Updated" paragraph; the old one moved to STATUS-HISTORY. - REPORT-release-space-fixes-2026-11-10.md: wrong claims first, one deviation (the hub deploy ran before CI for the manifest-bump commit was read), what stays not proven. Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
22 lines
1.9 KiB
Markdown
22 lines
1.9 KiB
Markdown
# REPORT — the three Space fixes are released (2026-11-10, afternoon, attended)
|
||
|
||
**Plain words first.** Three fixes are released. The agent cleans its own update folder; the operator vouched it. The
|
||
controller sends one warning for one full disk; the global floor is set. The hub sends the host-disk alarm to the
|
||
operator only; it was deployed on the operator's yes. The HP box booted its kept older kernel once, was healthy, and
|
||
went back. The five rulings D71–D75 are written down and none is built.
|
||
|
||
**The full report is `REPORT-release-space-fixes-2026-11-10.md`.** It names first the claims that turned out wrong,
|
||
and one deviation from the rules (the hub deploy ran before CI for the manifest-bump commit was read).
|
||
|
||
| | |
|
||
|---|---|
|
||
| Agent | 0.173.0, vouched by the operator 15:29 UTC. The self-update folder on the three test boxes: 49 → 1, 48 → 1, 33 → 1 files. A rollback worked after the clean-up |
|
||
| Controller | 0.352.0, MinAgent 0.158.1. Global floor 15:31 UTC. The three boxes that report are on it. Each watches 2 filesystems, one target each |
|
||
| Hub | 0.180.0, live since 15:12 UTC, deployed by manifest bump. Synced/Healthy, no alarm sent in the 30 minutes after |
|
||
| The older kernel | demo-hp booted it to healthy in 313 seconds and went back in 324 seconds. Nothing was left behind |
|
||
| Rulings | D71–D75 in `documentation/architecture/09-update-architecture.md` §3, decisions 291–296 |
|
||
| Register | 236 open at the start, 236 at the end. Opened 0, closed 0. Dated lines on R-1368, R-1371, R-1301, R-1353 |
|
||
| Not proven | That a household which saved its own alarm list no longer gets the host-disk alarm, on the running hub. A real fill on a household's box. The kernel clean-up as a program |
|
||
| Evidence | `documentation/audits/release-space-fixes-2026-11-10/` and `documentation/audits/kernel-cleanup-spike-2026-11-10/evidence/fallback-boot/` |
|
||
| Not done, by the brief | No golden. No catalog push. No change on ep0. No test alarm. No mail to a household |
|