Files

T

Claude Code b802a9e7de docs(backlog): SPEC for R-85 Phases 4 & 5 (docs, then deploy)

Written against verified state, not assumption. Records three gaps the original
Phase 5 ordering does not cover:

1. hub v0.77.0 is COMMITTED BUT NOT DEPLOYED — manifest pins 0.76.0 and the pod
   runs 0.76.0, so the R-85 signal exists only in git. The original Phase 5 only
   mentions the agent.
2. R-85 has no ROADMAP row.
3. The agent CHANGELOG says v0.104.0-dev; an ldflags version disagreeing with
   the CHANGELOG is the reconciliation problem hub 0.73.2 already caused.

One ordering correction: THE HUB GOES FIRST. Agent v0.104.0 makes the offsite
tier testable; hub v0.77.0 makes a failure audible. Agent-first means rotation
begins with nothing listening — two tiers able to fail silently instead of one,
which is the fault R-85 exists to end. Also drops the retired drill box, so the
rollout is demo-hp -> demo-felhom.

Names the phase's most likely SILENT failure: the new rotation state lands at
/var/lib/felhom-agent/restore-test-state.json and the agent is non-root. If that
is not writable, RecordSuccess warns and continues — a quiet return to one tier
being starved, not a crash.

Flags for operator judgement: demo-felhom's 14.46 GB offsite archive makes its
unattended restore-test a ~2h operation every other day, holding the heavy-op
gate throughout. Ruled when the only measured restore was demo-hp's 4 minutes.

2026-07-26 23:14:00 +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

README.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

ROADMAP.md

docs: R-84 SHIPPED (agent v0.103.0) + demo-hp's first offsite backup

2026-07-26 18:56:04 +02:00

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

docs(backlog): SPEC for R-85 Phases 4 & 5 (docs, then deploy)

2026-07-26 23:14:00 +02:00

README.md

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 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.