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
The one-shot flag booted 7.0.14-26-pve: every health point good after 313 s. An orderly restart
brought 7.0.14-28-pve back: 324 s. The pinned default, grub.cfg and the step's state file did not
change. No kernel report and no alarm at the hub. Evidence: evidence/fallback-boot/.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
C4: documentation/runbooks/disk-full.md (R-1369). Five disks; each hand step
is PROVEN with its date and evidence, or NOT PROVEN.
C5: 16-storage-physical-identity.md §14 (D69, decision 288). 45 places, each
with limit, cleaner and alarm; the rulings behind "no limit"; the host disk
budget; the open design points. PROMPT-TEMPLATE §N.5 gets the keep-it-true line.
Close-out: STATUS (D75 new), CONTEXT, dated lines on R-1369, R-1370, R-1371,
three small stale-document fixes, the report of the run.
Documents only. No release, no build, no deploy.
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS