felhom-agent/REPORT.md

REPORT — v0.168.0 released and vouched (2026-10-29, attended)

Plain words first. The agent 0.168.0 is out, on the three test boxes, and vouched by the operator — new boxes install it. It carries R-528 (the host's per-container OOM count) and R-1254's ceremony half.

• Release: release-agent.sh from a clean clone of 91bd96c (CI 2479 green): agent sha256 1e70196c51346cf10e3f04f51975de5899b5dc6baa5a45ec1d17bc248830d2ca, bundle 3415c034955d46c59ca3f7b284a648abf852b1257b77cc49bd6ea9994a7b8cb8, tag v0.168.0, verified by independent download.
• Delivery: no configs/ change since v0.167.0 → one signed agent_update per box: demo-hp 09:56, Tester 1 09:57, demo-felhom 10:04 CET — each „signed op COMPLETED", self-check 76/76, „update committed"; the binary's sha256 matches on all three.
• Proof: on Tester 1 (controller 0.347.0) a 128 MB Gokapi had a memory hog killed: host counter 1, one app_oom „seen by docker,cgroup", one operator mail. R-1254: a ceremony ran on 0.168.0 (the happy path); the lost-answer branch has tests only.
• Vouch: the operator, 10:21:56 CET (hub log: agent=0.168.0, the bundle sha above). pinned.day0_agent = 0.168.0 (6b0b093).

Evidence: felhom.eu documentation/audits/d63-2026-10-29/ (opsign-agent.txt, agent-delivery*.txt, run-p4-oom.log).