Files
felhom.eu/documentation/audits/night-2026-09-23/PROGRESS.md
T
admin 0030cbd1de
gates / gates (push) Successful in 26s
night 2026-09-23: evidence so far (Parts A, B, C in progress)
The records the catalog's ladder entries cite (apps/<app>/bench and
apps/<app>/verdict.json), the drill tools, the spike, R-626's run,
R-612/R-613 red-proofs, the chaos schedule (seed 20260923) drawn
BEFORE round 1. Docs and register follow at the end of the night.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-23 21:33:54 +02:00

3.8 KiB

PROGRESS — night 2026-09-23 (one line per finished step, written when it finishes)

time (CEST; rows before 20:53 are approximate) step result evidence
19:16 P0 baselines controller 15e630aa02ed v0.266.0 · agent d9864a94bf62 v0.132.0 · felhom.eu e443841b752a · catalog cfcfe5278428 — all match the brief; trees clean; disk 37 % / 53 % this line
~19:40 P0 drift re-run 66 pins; 26 within-a-major edges, 11 across-a-major (listed, not moved), 1 error (plant-it, abandoned) 02-drift.json, 02-drift.log
19:20 P0 capacity demo-hp 29 GB RAM (23 free), nvme-scratch 7 %; 9202 25.9 GB, /var/lib/docker 64 % (24 GB free); 9201 standing apps listed 00-demo-hp-before.txt, 01-capacity-9202-9201.txt
20:00 A1 R-650 internal/dockerexec guard + repo-wide sweep test; 8 api tests + web/stacks fixtures were reaching real docker → package TestMain stub; red-proofs both FAIL as expected A1-r650-redproof.txt, A1-r650-sweep.txt
20:05 A2 R-640 completion-marker check on all three restore paths, before the first mutation; 3 red-proofs FAIL as expected A2-r640-redproof.txt
20:17 A3 R-626 NOT reproduced on v0.266.0: remove → 390 s of events (destroy seen, no create) + controller restart + guest reboot → 0 containers, 0 volumes. Leftover applied-compose.yml/applied-meta (row) A3-r626-*.txt/json
20:15 A4 R-499 4-branch system-disk sentence; 2 red-proofs FAIL as expected; parity fixtures per branch A4-r499-redproof.txt
20:20 A5 R-518 the "few seconds" promise was ALREADY gone (v0.243.0) — brief claim wrong; copy now states the measured ~8 min; red-proof FAILs as expected A5-r518-redproof.txt
20:26 A6 v0.267.0 pushed 80e6ad8c4772, gates + full suite rc 0; image built; deployed to 9202 only (Up, healthy). Floor waits for Part E A6-deploy-0.267.0-on-9202.txt
20:28 A7 pages live 9202 (no agent): R-499 renders the unknown branch in hu+en, matching /api/storage/backup-target known:false; R-518 text on /backups in hu+en A7-pages-live-0.267.0.txt
20:28 B1 SPIKE PASS on v0.266.0 AND v0.267.0: drill navidrome with a top-level update_ladder: (JSON flow lines) synced, deploy-fields read, deployed running, probe API GET :4533/ping → 200, badge „Naprakész"/"Up to date", no yaml errors. Source agrees: no KnownFields anywhere B1-spike-v0.26{6,7}.0.{json,log}
20:55 B2 gate check-test-record.py (static, CI) + check-test-record-move.py (history + registry for moved refs); 16 decoys both ways; 3 red-proofs FAIL as expected B2-gate-redproofs.txt
21:05 B3 writer upgrade-test.py --write-ladder (+ --move, harness v3: box fixtures on the bench, files_may_change); test_ladder_writer.py 5/5 catalog scripts/
21:10 B4 backfill 21 of 21 proven from their cited records (nextcloud's commit cited none — its record named, entry says so); romm carries M1's 80.9 % memory_tight catalog 6db08a5
21:12 B5 pushed catalog 6db08a5, hook gates OK, CI job 920 success (matched on head_sha) —
20:58 C0 venue bench LXC 9401 on demo-hp (nvme-scratch, 6c/10G), docker 26.1.5, Docker Hub login; C3 negative control → failed (bench measures) C0-harness-venue-create.txt
21:06 C R-612 bench: 128M → seed OOM-killed (oom_kill 3), 1024M peak 345M, 512M peak 312M seed completes; 9202 before: seed SIGKILLed but after the rows (sign-up worked — lie NOT reproduced, timing-dependent); after 512M: seed completes. Live catalog a5a729a apps/wishlist/r612-*.json
21:15 C R-613 UPTIME_KUMA_DB_TYPE=sqlite: before setup-database while box says running; after entryPage, /metrics 401; db in the volume. First "after" run used a stale template (R-607 lag) — kept, renamed. Live catalog a5a729a apps/uptime-kuma/r613-*.json