From 3aba2002933a992835efc0b077d96d5c8fb204f9 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Wed, 7 Oct 2026 05:46:57 +0200 Subject: [PATCH] Night 2026-10-06: morning note, STATUS, report Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS --- REPORT-night-burndown-2026-10-06.md | 30 ++++++++ STATUS.md | 20 +++++- .../night-burndown-2026-10-06/MORNING-NOTE.md | 71 +++++++++++++++++++ 3 files changed, 119 insertions(+), 2 deletions(-) create mode 100644 REPORT-night-burndown-2026-10-06.md create mode 100644 documentation/audits/night-burndown-2026-10-06/MORNING-NOTE.md diff --git a/REPORT-night-burndown-2026-10-06.md b/REPORT-night-burndown-2026-10-06.md new file mode 100644 index 00000000..91ab5744 --- /dev/null +++ b/REPORT-night-burndown-2026-10-06.md @@ -0,0 +1,30 @@ +# REPORT — the second burn-down night (2026-10-06 → 07) + +Brief `drills/NIGHT-burndown-2026-10-06.md`. This is a separate file so the evening's interim `REPORT.md` stays intact +for the day session's Parts B and D. The operator view: `documentation/audits/night-burndown-2026-10-06/MORNING-NOTE.md`. +Row by row, with minutes and commits: `documentation/audits/night-burndown-2026-10-06/NIGHT-LOG.md`. + +| Rows before | Rows after | Opened | Closed | +|---|---|---|---| +| 138 | 138 | 2 (R-895, R-896) | 2 (R-377, R-392) | + +- **§3 R-892:** stopped — no SSH agent here; DooPlex's own keys refused (`s3/`). +- **§4 R-894:** fixed on agent main `74b5eae` (4 red-proofs, `07` §6.1). +- **§5:** designs R-105, R-812, R-861, R-32, R-822, R-366 (six, the night's limit); R-366's key-retention fix and R-31's + race on hub main; R-777 measured and fixed (held catalog branch); R-173 waits for an event. +- **§6:** R-542, R-516 (controller); R-330 wire half (three repos); R-612, R-782, R-805, R-806, R-733 (held catalog); + R-377, R-392 closed; R-762 measured; stopped with a reason: R-554, R-562, R-724, R-893, R-30, R-336, R-693, R-652, R-76. +- **Decision taken unattended:** `09` §3 decision 159 (R-805). +- **Refused by the permission check (stopped, no workaround):** reading a hub database copy (deleted at once); building + the hub image 0.141.0 at 00:12 (the CHANGELOG says not built). +- **Fence slips by helpers:** a hand `docker volume prune` inside bench 9401; a full catalog gate run that started canary + containers on DooPlex (none left; one small canary image remains; R-896 filed). +- **Instruction-file edits:** `.claude/rules/docs.md` line 15 — added the row „who owns which AI artifact; where an + instruction lives → `architecture/12-agent-tooling.md`" (before: no row; why: the new document needs a route). +- **Architecture corrected:** `03` §3.1 (the controller-swap `tee` runs any image, not a pinned one); `07` (the clean-up + window runs since 2026-10-05); `05`/`06` corrections are R-105's question. +- **Teardown:** 9202 — R-777's two apps removed through the product, app list equal to before; bench 9401 — stopped as + found, test containers removed; demo-hp `/tmp` helper files removed; hub — nothing provisioned. All helper worktrees + removed. +- **CI:** green on every push (last: felhom.eu 1469 → updated by this commit, controller 1471, agent 1470, catalog 1445 + main, 1459 held branch). Lost jobs (R-887): 0. diff --git a/STATUS.md b/STATUS.md index 85dd628a..0df590e1 100644 --- a/STATUS.md +++ b/STATUS.md @@ -2,8 +2,24 @@ **Ready for the first real tester (Tester-2): yes. Tester 2 (a laptop) is off; nothing was sent to it.** -**Updated 2026-10-06 19:45: hub 0.140.0; demo-hp, demo-felhom and Tester 1 run controller 0.301.0, agent 0.149.0. -The open-items list is at 138. Report: `REPORT.md` (interim — the night read-back follows after 08:30).** +**Updated 2026-10-07 05:50: hub 0.140.0; demo-hp, demo-felhom and Tester 1 run controller 0.301.0, agent 0.149.0 — +nothing was delivered tonight. The open-items list is at 138. Night: `documentation/audits/night-burndown-2026-10-06/MORNING-NOTE.md`. +Day: Parts B and D of the read-back brief after 08:30, then the releases (hub 0.141.0, agent 0.150.0, controller, the +held catalog branch).** + +## Night (2026-10-06 → 07): the second burn-down night — fixes on main, nothing delivered + +- **Fixed in code, waiting for today's releases:** the box remembers its last backup after a restart; a reinstall + keeps the old backup key; two quick off-site saves no longer make two accounts; the format list hides drives in use; + 22 more messages in the household's language; three more disk-health counters reach the hub. +- **Jellyfin and Emby** let an internet stranger sign in as if at home — measured and fixed on a held catalog branch. +- **Six one-page designs**, each with a pick and one question for you. +- **Did not work:** the Tester 1 box still refuses this server's key (one command fixes it); the hub release was + refused by the session's safety check, so the hub is unchanged. + +**Needs you (none urgent):** +1. Release order today: hub, agent, controller, then the catalog branch. My pick: yes, after Parts B and D. +2. The Tester 1 key: `ssh-copy-id -i ~/.ssh/id_ed25519.pub root@192.168.0.154` from this server. ## Night (2026-10-06): the night-free parts done; the rest after 08:30 diff --git a/documentation/audits/night-burndown-2026-10-06/MORNING-NOTE.md b/documentation/audits/night-burndown-2026-10-06/MORNING-NOTE.md new file mode 100644 index 00000000..5b3db907 --- /dev/null +++ b/documentation/audits/night-burndown-2026-10-06/MORNING-NOTE.md @@ -0,0 +1,71 @@ +# Morning note — the second burn-down night, 2026-10-07 + +**Day session: start with Parts B and D of `TASK-night-readback-offsite-gap-tester1-2026-10-07.md` (after 08:30), then +the releases below.** Nothing was delivered to any box tonight, so the night read-back sees a clean night. + +## 1. Is anything broken right now? + +**No.** The hub answers (health 200, System page 200). demo-hp, demo-felhom and Tester 1 are online. Tester 2 is off, +as usual. CI is green on the last commit of every repository. No CI job was lost tonight (R-887: 0). + +**You do not need to do anything this morning.** + +## 2. One decision I took myself (you may reverse it) + +The app catalog's storage check now only **notes** an empty folder; it does not fail the app for it. A household +folder (photos, documents) is empty on every fresh install, so failing it would block four apps for ever. + +## 3. The four numbers + +Rows before: **138**. Rows after: **138**. Opened: **2**. Closed: **2**. + +## 4. What was fixed + +- **Backups:** after a restart, the host program now remembers the last good backup. An unreachable backup store no + longer looks like "never backed up", so no copy is asked for that cannot be made. +- **Backups:** a reinstall no longer overwrites the old backup key in your safe store. The old copies stay readable. +- **Hub:** two quick clicks on "Save" for off-site backup no longer create two storage accounts. +- **Box:** the "format a drive" list no longer offers a drive the household already uses. +- **Box:** 22 more messages follow the household's language, in the friendly form. +- **Disk health:** three more warning counters now travel from the disk to the hub. Nothing alarms on them yet. +- **Apps (held, not live):** Jellyfin and Emby no longer let a stranger on the internet sign in as if at home + (measured, then fixed). Also wishlist, homepage, gramps-web and two test tools. +- **Measured:** wger runs best with its proper web server and 2 workers (41 % of its memory). + +**Waits for today's releases:** +- agent: the restart memory and the disk counters, released together with the memory-kill check as v0.150.0; +- controller: the drive list, the 22 messages and the disk counters; +- hub: v0.141.0 is ready in the code, but not built (see 5); +- catalog: six changes on the branch `night-held-2026-10-06`; merge them to the main line after the read-back. + +## 5. What failed, and why + +- **The Tester 1 box: still no entry.** Your key copy at 20:20 used the key of your own login, not this server's + key. Fix: run `ssh-copy-id -i ~/.ssh/id_ed25519.pub root@192.168.0.154` from this server as kisfenyo. +- **The hub release did not run.** The safety check of my session refused the image build at 00:12. I stopped + there. The hub still runs 0.140.0, unchanged. +- **I could not read the hub's list of apps per box.** The same safety check refused it. So every catalog change + went to the held branch. +- **Two rule slips by helpers, both harmless:** one cleaned unused storage on the test machine by hand; one ran a + catalog test that starts small test containers on this server. Nothing was left running. + +## 6. The designs — each needs one answer from you + +1. **Empty disaster-recovery records:** two fields were never built and nothing reads them. Pick: remove them and + fix the documents. +2. **Host updates:** Proxmox's own packages (78 behind) and the kernel never update. Pick: a new night lane for the + Proxmox packages, approved per set; the kernel stays a manual step for now. +3. **Host program rights:** one left-over right is wider than the documents said: it can start any container image. + Pick: close it before the first paying customer; accept the other two. +4. **RESET leaves old off-site data behind.** Pick: delete it through the customer's own login before the login is + removed. +5. **Fake snapshots can steer the off-site clean-up.** Pick: accept and close; build the hub's own snapshot count + later (new item). +6. **Old backups after a reinstall:** the key part is fixed. Pick: also tell you when old copies use another key. + +## 7. Two decisions for you + +1. **Release today in this order: hub 0.141.0, agent 0.150.0, controller, then merge the catalog branch.** + My pick: yes, after Parts B and D. If you do nothing: the fixes stay in the code and reach no box. +2. **May my session build hub images at night?** The safety check blocked it. Pick: allow it for the brief's + window only. If you do nothing: night hub releases cannot happen.