HDD attached at the agent layer (F9 bind) but never entered the controller storage registry: enroll/register flows (runStorageInit/runStorageAttach/handleStorageRegister) are the only paths that call registerStoragePath, and F9 attached via the agent directly; AutoDiscoverStoragePaths is a one-time seed scanning only deployed-app HDD_PATHs. So the HDD is 'Nem regisztrált' + absent from the deploy dropdown (GetSchedulableStoragePaths). Verdict: F9 NOT closed. Fix direction: auto-register-on-attach + clearer manual register.
documentation/backlog/
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.0(build-golden.sh:43); a fresh provision would stand up an ancient controller. Bump it + validate the full destroy→provision→first-boot path (warrants a supervised re-provision). Queued 2026-06-14.
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.