admin
bca013edec
Round 2 (restore gokapi + power cut, 20s into the restore): the box came back BY ITSELF in 148 seconds, 0 -> 25 -> 26 containers, and gokapi - the app being restored when the plug came out - returned healthy. The only alarm was controller_started, which is what the ladder expects for a 60-second outage: no node_stale (30 min threshold), no app_start_failed (90s boot grace). No false alarm, none missed. Round 2's household measure is recorded as NOT COLLECTED, not as a pass: the loop died with the box and zero lines is not zero failures. The round also handed over immich's whole diagnosis. app_oom fired - "immich (immich-postgres) - egy folyamatat a memoriakorlat leallitotta" - naming the app and the exact container. That is why immich saw CONNECTION_CLOSED and crash-looped twelve times. It is added as tonight's line on the EXISTING OOM row rather than filed as a new one, because this project's standing finding is that those signals are invisible inside LXC guests and on this box the scan caught one. The diagnosis I spent twenty minutes reaching from logs was sitting in the alarm feed, correctly labelled, the whole time. 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.