felhom.eu/REPORT.md

REPORT — three fixes before the first real kernel night, 2026-10-07 (evening)

The brief said 2026-10-08; at 18:34 it was 2026-10-07. Asked; the operator answered "Start today, and do both boxes this night" (09 §3 decision 176). So the first real kernel night is 7→8, read back on the morning of 2026-10-08.

Part	Result
Rulings	Decisions 174 (mail text stays + a reply address), 175 (window 09–20, max 3 mails: keep), 176 (today, both boxes tonight) recorded FIRST (a0ff737e).
A — the told kernel boots (R-898)	Done, delivered, closed. Agent v0.153.0: ring 0 stages EXACTLY the told kernel (select listed, the set from the kver). Told 20 / sources offer 22 → 20 installs (wrapper test); 20 gone → R7 before any change (wrapper test); the hub keeps R7 temporary and tells the household again for the newer kernel (hub test). Red-proofs audits/kernel-night-2026-10-07/A/redproof.txt.
B — first backup after a restart waits (R-897)	Done, delivered, closed. The reviewer's pick, taken: controller v0.303.0 — for 10 min after the controller starts, a capture for an app on a drive runs only once that drive is a LIVE mount in the controller's own namespace (/proc/self/mountinfo, the signal the startup app gate already uses); the 5-min refresh skips, a data run waits; after 10 min it runs and logs once. The agent's bind order is unchanged. Red test: not-bound → no capture; bound → capture.
C — a reply reaches a person	Built and delivered (hub v0.143.1); the header read-back is NOT done. Every mail to a household now carries reply_to = admin@felhom.eu (all household templates invite contact: the kernel notice, the event sign-off "contact your operator", the setup/link mails); a mail to the operator carries none. Test pinned and red-proved. One test mail sent through the mail service with the hub's exact fields to tester1@felhom.eu — it arrived in Gmail (16:54 UTC). Read-back tried: the Gmail tool returns no headers (METADATA_ONLY, no RAW); the mail service's read API refused (restricted_api_key — send-only, correctly). Note: the demo households' own address IS admin@felhom.eu, so their mails carry no Reply-To by design.
D — deliver, arm the night	Done. Hub 0.143.1 deployed 18:54 local (operator attending), agent 0.153.0 on all three boxes 19:03 (binary only — no root file changed), controller 0.303.0 on all three 18:50 (per-customer floors; global untouched). Armed: demo-felhom → 7.0.14-20-pve, household mail 18:12; demo-hp → 7.0.14-22-pve, household mail 18:38. No reboot by hand.

Rows: 128 before → 126 after. Opened 0. Closed 2 (R-897, R-898).

How demo-hp got told tonight: its apt lists were a day old, so its last report named no new kernel. I switched its OS updates OFF on the hub for ~1 minute, ran the agent's own report-only pass (--selftest=os-update; with the switch off it installs nothing and runs no Docker/Proxmox/kernel step), and switched it back ON (kernel-night-2026-10-07/demo-hp-inventory-pass.txt). The hub mailed 20 s after the host report arrived (18:37:51 → 18:38:11).

Releases: agent v0.153.0 (binary b204ebe6…, tag at 2d1e5d0); controller v0.303.0 (29bebbb, MinAgent 0.131.0); hub v0.143.1 (87765bfa, deployed d1457892, Synced/Healthy). CI green on every push, checked by commit. No change on ep0, Tester 2 or DooPlex's own system.

What the morning read-back must check: each demo box on its told kernel as the default; the household apps back and the minutes they were down; no false backup failure after the restart (R-897's fix); the hub's kernel events. The two boxes run DIFFERENT kernels after tonight, so "Approve kernel set" waits until both boot the same one.

Decisions for you

1. Check the reply address in one click: open „TEST — Reply-To check" in Gmail and press Reply — it should go to admin@felhom.eu. My pick: do it once. If you do nothing: the code and its test say it works; nobody has seen it.
2. The demo households' address is your own, so their kernel mails carry no Reply-To. My pick: leave it. If you do nothing: it stays (a reply to them lands in your catch-all anyway).