admin
737694c603
The operator produced the mails. The controller HAS an OOM detector (main.go:821), it emits app_oom (notifier.go:726), the hub allow-lists it (dispatcher.go:636) and delivered it to the OPERATOR channel - two mails, 11:09 and 17:48 CEST, each naming the app and linking the dashboard. CUSTOMER skipped, correctly. I asserted an absence without opening the hub's Events or Notifications tab, reasoning instead from a memory note that said the signal was UNPROVEN - not that it was missing. That is R-628's shape again, from the same hand, four days later. R-636: the real defect is the signal's SHAPE. notifier.go:715-724 keys on container|startedAt and emits once per container lifetime, so 4530 worker kills over six hours produced exactly one warning-level mail - indistinguishable from one transient kill. The magnitude was already collected (App Telemetry: RomM 5023 errors, 632 warnings) but nothing turns it into a louder event. Memory note lxc-docker-oom-signals-unreliable corrected with the positive reading. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
documentation/backlog/
OPEN-ITEMS.md is the register of open work and the file to read first — it holds only what is
open, one row per item, every row with a state and an owner. ROADMAP.md is the full history and
reasoning behind the R-n IDs, including shipped and killed items; an ID is minted there, and a new
instance of an existing item attaches to that ID rather than getting its own.
The rest of this folder: verified-LIVE findings with implementable fix plans that are not yet
implemented. Preserved here
(instead of on git branches) per the trunk-based, no-branches rule — the fix itself is implemented later
directly on main, during a normal/supervised session.
-
FIX-M18-NOTES.md — dump re-validation runs every 5 min (perf). FIXED in controller v0.62.0 @
f8afe5c(2026-06-14). (was on the deletedfelhom-controllerbranchfix/m18-dump-validation-cache.) -
FIX-M19-NOTES.md —
deriveStackNamemisattribution edge (low-incidence correctness). FIXED in controller v0.62.0 @6bab68b(2026-06-14). (was on the deleted branchfix/m19-stackname-crossref.) -
FOLLOWUP-golden-default-controller-tag.md — the golden bakes a stale controller (
:0.43.0when queued; had rotted again to:0.85.1by resolution). FIXED in felhom-agent @ceca355(2026-07-03):build-golden.shv2.0.0 makes the controller tag a MANDATORY argument (a required arg cannot rot) and golden 0.98.3 was baked + clean-room-validated (bake → first-boot-current → self-manage → app deploy, on the drill VM — no supervised touch of live guests needed) + published + vouched. Evidence:../audits/DRILL-golden-098-2026-07-03.md.
Related: the live-drive fixspec (../audits/live-drive-fixspec-2026-06-14.md) carries the deferred
supervised items F9 (HDD provisioning/guest-attach), F20-BUG2 (durable_id scheme), F20-BUG3 (async
mkfs) — to be implemented in the agent/golden supervised session.