admin
c8100aad6b
Compresses the six rows closed today into CLOSED-ITEMS, keeping title, shipping
version, evidence paths and every sentence that states a RULE. Full original:
`git show e027b5d9 -- documentation/backlog/OPEN-ITEMS.md`. No open row touched.
Register 165 -> 167 -> 161.
Files two rows that would otherwise have died in an overwritten REPORT.md, which
is what the controller's observations gate exists to prevent:
R-397 -- NotifyIntegrityOK/NotifyIntegrityFailed have no caller anywhere and the
controller runs no integrity check at all. The part that actively misleads is not
the dead code: config.Monitoring.PingUUIDs carries a backup_integrity field and
the monitoring page renders "Mentes integritas -- Hetente (vasarnap)", so the
operator is told a weekly check runs. Decide WHETHER one is wanted, then delete
or build -- do not leave the third state.
R-398 -- resticStep is not a seam, so no test can drive any restic-backed path.
Felt directly in v0.226.0: R-358's safety property is an ORDER (clear the marker
before restic, write it after) and with no seam it could only be pinned by an AST
walk. The contrast is the argument -- offboxLatestSnapshot got a seam in the same
release, in four lines, because a correctness gate could not otherwise be proven.
This push used `git push --no-verify`. golden-currency remains CONVICTED and
remains right: three controller releases today, golden still 0.223.0. Bypass, not
waiver, on the operator's standing ruling, re-checked for this release rather
than reused blindly. Tracked on R-242; one bake carrying 0.226.0 covers all three.
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.