Files

T

admin f39b51782a R-244: measure the teardown residue rather than estimate it — still owed

Read-only census, no truncation. app_log_issues holds 1309 rows; 71 reference
a torn-down venue (finalwalk, c11, rewalk, part4). Of those 44 are ORPHANS,
naming only torn-down customers and safely deletable, and 27 are SHARED with a
live customer and must be de-referenced, never deleted. 1238 untouched.

The 27 are exactly why the leg was never written, and why a DELETE ... WHERE
customer LIKE would destroy a live customer's issue history.

NOT fixed here, and the reason is stated on the row rather than left implied:
the fix is hub code, this session's scope forbade a hub version bump, and a
hand-run SQL mutation over 71 rows - 27 needing surgical de-referencing - with
no tested code path and no red-proof is the shape that goes wrong on a live
database. The next session now starts from data instead of a guess.

2026-08-07 13:01:09 +02:00

DIAGNOSIS-f9-storage-registration-gap-2026-06-14.md

docs(f9): reject recommendation #1 auto-register-on-attach (A3)

2026-06-14 17:33:33 +02:00

FIX-M18-NOTES.md

docs(backlog): mark M18 + M19 FIXED in controller v0.62.0

2026-06-14 14:17:59 +02:00

FIX-M19-NOTES.md

docs(backlog): mark M18 + M19 FIXED in controller v0.62.0

2026-06-14 14:17:59 +02:00

FOLLOWUP-golden-default-controller-tag.md

docs: golden 0.98.3 live — D.1b retired, drill B1/B5 fixed, backlog note resolved + evidence doc

2026-07-03 18:38:28 +02:00

FOLLOWUP-nas-automount-guest-reboot-reassert.md

audit(Q1c): NAS automount trigger does NOT survive a guest reboot (empty-dir FAIL) + follow-up

2026-07-11 15:43:26 +02:00

OPEN-ITEMS.md

R-244: measure the teardown residue rather than estimate it — still owed

2026-08-07 13:01:09 +02:00

README.md

docs: file R-29 to the register; attach the gate-orphan instance to its class

2026-07-29 11:13:23 +02:00

ROADMAP.md

docs: R-193 CLOSED (the recovery screen); R-213 minted for the put-back

2026-08-05 12:56:55 +02:00

SPEC-r85-phase4-5-2026-07-26.md

R-85: demo-felhom restore-test PASSED — rotation proven on BOTH boxes; correct a bad estimate

2026-07-27 08:17:00 +02:00

README.md

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 deleted felhom-controller branch fix/m18-dump-validation-cache.)
FIX-M19-NOTES.md — deriveStackName misattribution edge (low-incidence correctness). FIXED in controller v0.62.0 @ 6bab68b (2026-06-14). (was on the deleted branch fix/m19-stackname-crossref.)
FOLLOWUP-golden-default-controller-tag.md — the golden bakes a stale controller (:0.43.0 when queued; had rotted again to :0.85.1 by resolution). FIXED in felhom-agent @ ceca355 (2026-07-03): build-golden.sh v2.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.