felhom-agent/REPORT.md

REPORT — agent v0.162.0 released (2026-10-22 morning, operator yes) — NOT VOUCHED (the vouch is the operator's)

What: the swap fix (R-1192: every guest may swap as much as its RAM), the host-swap report and check, and R-1194 (no false „operator access degraded" on a fresh box). Proven the night before on a fresh 8 GB box: 11 h, no freeze; with the host's swap off the freeze comes back (felhom.eu REPORT-night-2026-10-21.md).

• Released with scripts/release-agent.sh 0.162.0 from a clean clone at b310773: binary sha256 5fd7a23bfe319cb521c4bc399612d5fb3413f1e695f79bc663c386f69c757928 (the same bytes as the night's candidate), bundle ac772967…60b5a5, tag v0.162.0, round trip verified by the script.
• Delivered by one signed agent_update job per box to demo-hp, Tester 1 and demo-felhom: all three update committed with capabilities self-check ok=76 total=76; each raised its 9201's swap from 512 MB to its RAM. Evidence felhom.eu documentation/audits/morning-2026-10-22/release/04-agent-delivery.txt.
• Found: the host-swap check is too strict for a guest larger than 8 GB. demo-hp (host 8191 MB vs guests 25898 MB) and demo-felhom (8191 vs 12288) warned and the hub mailed host_swap_short; the soak used at most 2.7 GB of host swap. Filed felhom.eu R-1216 with two options for the operator.
• Not done: the vouch (Configs → Day-0 artifacts, agent 0.162.0 / the sha above, the bundle with it) — the operator's click; CC's token cannot. Tester 2's box was not sent the update (not a test box; the operator's word).