admin/felhom.eu

Fork 0

Files

T

History

admin 11a5c3bd92

gates / gates (push) Successful in 13s

Details

R-265 second sighting: a CI run failed and its log cannot be retrieved

felhom.eu run 293 (67eced8, the demo-felhom recovery commit) FAILED, and
/actions/jobs/293/logs returns HTTP 500 while runs 292 and 294 both return 200
with 12290 bytes. The failure is real and its reason is not establishable --
exactly what this row was filed for, now seen a second time.

What can be said: the same tree passes the FULL gate set locally, all eight OK,
and run 294 on the next commit passed in CI, so nothing persisted. What cannot:
why 293 failed.

The process failure is mine. The checklist says confirm your own push's CI run by
ID; I pushed 67eced8 without doing so, and it surfaced only because the next
session happened to list recent runs. A pull check that is skipped is not a check.

2026-08-10 11:17:37 +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-265 second sighting: a CI run failed and its log cannot be retrieved

2026-08-10 11:17:37 +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

R-265 CI timeout + golden 0.210.0 baked; R-221/R-259/R-258 closed, R-266 minted, G-3 unblocked

2026-08-08 16:52:39 +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.