hub v0.139.0: R-444 System page last disk trim, R-872 early-return log lines

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-10-06 11:51:56 +02:00
parent f5400268a7
commit c823dc68d3
1 changed files with 3 additions and 1 deletions
@@ -1,4 +1,6 @@
-## unreleased
+## v0.139.0 — the System page shows each box's last disk trim; the 05:00 check says why it did not judge a down box (R-444, R-872) (2026-10-06)
+
+**Operator action on deploy: none.**

 - hub: R-444 — the System page shows each box's 'Last disk trim' (from the agent's guest_disk_trim stanza): last successful trim and the GiB freed; amber when the newest attempt failed (its error shown) or the last success is older than 14 days; '—' when the agent sends none. wire_contract_gate checks guest_disk_trim field by field both ways against hub sysfacts.DiskTrim (SUBTREE_MIRRORS), with decoys (decision 139).
 - **Fixed without a row (R-872 night watch):** the 05:00 deadline check's down-box judgement returned early in silence for a box never bound or first seen under 48 h ago, so the log read only „1 skipped (down)" and a night watch could not tell „too young to judge" from „judged, nothing missed". Each early return now logs why. `TestR872_DownButTooYoungIsLogged`; red-proved (without the line: the test fails).