From 449b065fbd2c9db7b8de56f394d9b6657e35d4a6 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Tue, 10 Nov 2026 12:46:21 +0100 Subject: [PATCH] =?UTF-8?q?Record=20the=20operator's=20rulings=20of=202026?= =?UTF-8?q?-11-10=2012:22=20(D67-D70,=20the=20gap=20review's=20scope):=200?= =?UTF-8?q?9=20=C2=A73=20decisions=20286-290?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit D67 yes as a separate step (R4 unchanged), D68 operator only, D69 a section inside 16, D70 yes with three changes; DooPlex is never measured, ep0 not yet. STATUS: D67-D70 out. Rows R-1368, R-1370, R-1371 carry the ruling. Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS --- STATUS.md | 6 +---- .../architecture/09-update-architecture.md | 25 +++++++++++++++++++ .../audits/space-list-2026-11-10/README.md | 2 +- .../audits/space-list-2026-11-10/TABLE.md | 16 ++++++------ documentation/backlog/OPEN-ITEMS.md | 6 ++--- 5 files changed, 38 insertions(+), 17 deletions(-) diff --git a/STATUS.md b/STATUS.md index 4f78b649..e2aabeb0 100644 --- a/STATUS.md +++ b/STATUS.md @@ -2,7 +2,7 @@ **Ready for Tester 2? Yes — tell the friend go (`documentation/pilot/TESTER2-handover.md`).** -**Updated 2026-11-10.** CC listed every place that holds data on a box — 45 places, read-only on the three test boxes — and asked eight questions of each: 47 answers were „nobody asked”, now in five new rows (R-1368…R-1372). The worst one: nothing removes old kernels from the host; a ring-0 box holds 8 of them (8 GB) and gets about one more each week. Four decisions wait for you (D67–D70); the list is in `documentation/audits/space-list-2026-11-10/README.md`. +**Updated 2026-11-10.** CC listed every place that holds data on a box — 45 places, read-only on the three test boxes — and asked eight questions of each: 47 answers were „nobody asked”, now in five new rows (R-1368…R-1372). The worst one: nothing removes old kernels from the host; a ring-0 box holds 8 of them (8 GB) and gets about one more each week. You ruled on its four questions at 12:22 (D67–D70: yes, operator only, yes, yes — `09` §3 decisions 286–290); the list is in `documentation/audits/space-list-2026-11-10/README.md`. ## What works - **The Plex attack did not reach Felhom's secrets** (R-1241). @@ -32,10 +32,6 @@ Newest first. CC's pick is in the „Pick" column. Each row also has its full te | # | Row | Question | Pick (why) | The other option costs | If you do nothing | Blocked | |---|---|---|---|---|---|---| -| D70 | — | Run the next gap list („Endings”: every way a thing stops, is removed or expires) with the same method as the Space list? | **Yes, with three changes** (it found real gaps in about 1.5 hours of work; the changes cut the repeats) | no: the gap review stops after its pilot; the other four lists are never made | no second list is started | — | -| D69 | R-1370 | Write a short „disk space” section in an architecture document: each place, its limit, its cleaner? Today no document covers disk space as a whole. | **Yes** (8 of 45 places are named in no document; about one session) | no: the audit table of 2026-11-10 stays the only reference and goes stale | new places that grow appear unseen, as the kernels and the agent's old binaries did | — | -| D68 | R-1371 | Who gets the „host disk critical” and „storage critical” mail? Today you and, by default, the household. Only you can free a host disk. | **Operator only** (the household cannot act on it; one hub change) | keep: the household gets an alarm it cannot act on and asks you | the household is mailed when the host disk passes 95 % | — | -| D67 | R-1368 | May the nightly update remove old kernels by itself — keep the running one, the one before it and the newest? Today the wrapper refuses every removal (rule R4), so a box keeps every kernel it ever got. | **Yes, ring 0 first** (8 kernels = 8 GB on a ring-0 box, about 1 GB more each week) | no: you remove them by hand on each box, every few months | the host system disk of a ring-0 box grows about 1 GB a week until the 90 % alarm | — | | D66 | R-1365 | Should a security-watch source that stays down mail again every 7 days, as an open notice does? Today it mails once, then only the Monday summary lists it. | **Yes** (a real outage then cannot be forgotten; the seven pins that can never be read no longer count, so it stays quiet when all is well) | no: one line in a long Monday mail stays the only reminder | a source that stays down mails once; the Monday list still shows it | — | | D38 | R-1235 | Put the newest golden (637 MB) into the nightly release copy on ep0 too? | **Yes** (a new install after a DooPlex loss needs it; it fits under the 3 GB cap) | leave it out: after a loss, no new install until a golden is rebuilt and vouched | the same | — | | D37 | R-1236 | Raise Gitea's memory limit from 1 GiB to 2 GiB? It was killed for memory 4 times in 17 days, once during today's release. | **Yes** (DooPlex has the RAM; a DooPlex change, so yours) | keep 1 GiB: a restart in release hours fails box updates and CI for a minute | the same | — | diff --git a/documentation/architecture/09-update-architecture.md b/documentation/architecture/09-update-architecture.md index baa518b8..d08d0ad6 100644 --- a/documentation/architecture/09-update-architecture.md +++ b/documentation/architecture/09-update-architecture.md @@ -1240,6 +1240,31 @@ Wanderer's Meilisearch went 256 → 384 MB and was measured again (it sizes itse image rides the whole-guest copy (mp0 holds Docker's data). **Cost:** a hand roll-back two pins back pulls the image again. Controller v0.351.0, `internal/stacks/infra_image_retention.go`, `TestInfraRetention_*`. +### 2026-11-10 (12:22, operator) — four rulings on the Space list, and the gap review's scope + +Recorded before the work (`audits/space-list-2026-11-10/README.md` §5 held the four questions, D67–D70). + +286. **D67 = yes, as a separate step: the box may remove old kernels by itself.** **Rule R4 („a plan that removes a + package is refused", `11` §5.4.1) stays exactly as it is for update plans.** The clean-up is its own step with its + own narrow rule: it can remove old kernel packages and nothing else, and it runs only after the box has booted well + on its newest kernel. It is built only after a hand proof on demo-hp (`audits/kernel-cleanup-spike-2026-11-10/`; + the design is `11` §5.11.1). **Cost of the other option:** the operator removes kernels by hand on each box. R-1368. + *Operator, 2026-11-10 12:22.* +287. **D68 = operator only: the household is not mailed about a host disk it cannot free.** `host_disk_critical` leaves + the household's seeded list and joins the operator-only register. `storage_fill_critical` moves with it only if + every storage it judges is one only the operator can free — checked in source before the change, not assumed. + R-1371, `08`. *Operator, 2026-11-10 12:22.* +288. **D69 = yes: „disk space" becomes a new section inside `16-storage-physical-identity.md`.** No new document. Each + customer place with what makes it grow, its limit, its cleaner and its alarm; the audit folder stays the evidence. + R-1370. *Operator, 2026-11-10 12:22.* +289. **D70 = yes: the next gap list („Endings") runs with the Space list's method, with three changes** — the runbook + question is asked once per ending, not per place; tiny things that cannot grow are dropped in the first hour; a + helper's answer enters a table only after the main session has read its pointer. *Operator, 2026-11-10 12:22.* +290. **The gap review does not measure DooPlex at all, and does not measure ep0 yet.** DooPlex is the recovery chain + (`runbooks/target-selection.md`, Tier 2) and its inventory belongs to the homelab session. The hub, Cloudflare, + Hetzner and the mail service are read from source and documents only: no hub database read, no account call. + *Operator, 2026-11-10 12:22.* + ### 2026-10-28 (day, attended) — RomM kept; the runtime cache fills itself in CI 277. **D61 = keep RomM offered** (R-1330) while no RomM release carries Node ≥ 24.22.1; the first one that does is taken diff --git a/documentation/audits/space-list-2026-11-10/README.md b/documentation/audits/space-list-2026-11-10/README.md index 5f2237b2..12463a6a 100644 --- a/documentation/audits/space-list-2026-11-10/README.md +++ b/documentation/audits/space-list-2026-11-10/README.md @@ -83,7 +83,7 @@ answer 21 times: that is one gap, not 21. Some places are too small to matter (t places under 100 MB that cannot grow, in the first hour; (3) a helper's answer does not go into the table until the main session has read its pointer — the off-box places here are still candidates for that reason. **Weak spot:** the off-box places (ep0, DooPlex, the off-site box, the hub database) were not measured, and the -Prometheus rules in `homelab-manifests` were not read. That is the second pass. +Prometheus rules in `homelab-manifests` were not read. Ruling 2026-11-10 12:22: DooPlex is never measured; ep0 not yet. ## For a later session (small fixes, not done today — no code change in this run) diff --git a/documentation/audits/space-list-2026-11-10/TABLE.md b/documentation/audits/space-list-2026-11-10/TABLE.md index 966abe87..33ded52d 100644 --- a/documentation/audits/space-list-2026-11-10/TABLE.md +++ b/documentation/audits/space-list-2026-11-10/TABLE.md @@ -713,17 +713,17 @@ on any of the three boxes today. --- -## DOC-ONLY places — second pass +## DOC-ONLY places — DooPlex: not measured — operator ruling 2026-11-10 · ep0 and the off-site box: not yet -Not measured in this run (no login to ep0, no inventory of DooPlex, no read of the hub database). The marks are +Not measured in this run (no login to ep0, no inventory of DooPlex, no read of the hub database). **Operator ruling 2026-11-10 12:22 (`AR/09-update-architecture.md` §3 decision 290): the gap review does not measure DooPlex at all (O4, O5, O6), and does not measure ep0 yet (O2, O3).** The marks are candidates from documents and source; they are NOT in `MATRIX.md`. A helper filled them; the main session did not read each pointer. | Place | What the documents say | Candidate gaps | |---|---|---| -| O1 — the shared off-site box (Hetzner Storage Box, restic) | keep 7 daily, 4 weekly, 6 monthly; hub warns at 80 % / 90 % of the box (`AR/07-backup-architecture.md:400`) | limit and "what when it fills": R-540; a weekly clean-up refused by its own guard: R-1294 | -| O2 — ep0's backup store (PBS datastore) | a 100 GB volume, 13 % used on 2026-07-27; the server prunes | what happens when it is full; a runbook for that | -| O3 — ep0's own system disk | no document found | grow, limit, full, alarm, runbook — all open; clean-up: R-91 | -| O4 — DooPlex's copy of ep0's store | 8 weekly copies (decision 71) | what happens when full; who is alarmed | -| O5 — the hub's database and its snapshots | rows 90 days; the newest 2 snapshots; a 4 GiB volume (`E/manifests/hub.yaml:58`) | what happens when full; who is alarmed | -| O6 — the image registry and the release copy | one image per version for ever; pruned only by hand (decision 62 — decided, not built as a job) | what happens when full; who is alarmed; R-1235, R-1259 | +| O1 — the shared off-site box (Hetzner Storage Box, restic) — **not yet** | keep 7 daily, 4 weekly, 6 monthly; hub warns at 80 % / 90 % of the box (`AR/07-backup-architecture.md:400`) | limit and "what when it fills": R-540; a weekly clean-up refused by its own guard: R-1294 | +| O2 — ep0's backup store (PBS datastore) — **ep0: not yet** | a 100 GB volume, 13 % used on 2026-07-27; the server prunes | what happens when it is full; a runbook for that | +| O3 — ep0's own system disk — **ep0: not yet** | no document found | grow, limit, full, alarm, runbook — all open; clean-up: R-91 | +| O4 — DooPlex's copy of ep0's store — **DooPlex: not measured — operator ruling 2026-11-10** | 8 weekly copies (decision 71) | what happens when full; who is alarmed | +| O5 — the hub's database and its snapshots — **on DooPlex: not measured — operator ruling 2026-11-10** | rows 90 days; the newest 2 snapshots; a 4 GiB volume (`E/manifests/hub.yaml:58`) | what happens when full; who is alarmed | +| O6 — the image registry and the release copy — **on DooPlex: not measured — operator ruling 2026-11-10** | one image per version for ever; pruned only by hand (decision 62 — decided, not built as a job) | what happens when full; who is alarmed; R-1235, R-1259 | diff --git a/documentation/backlog/OPEN-ITEMS.md b/documentation/backlog/OPEN-ITEMS.md index e6380810..a540b15b 100644 --- a/documentation/backlog/OPEN-ITEMS.md +++ b/documentation/backlog/OPEN-ITEMS.md @@ -278,9 +278,9 @@ stopping line that lies. | **R-1301** | Box system & updates | P3 | **The N100's Proxmox host keeps no time: `chrony` fails at every boot** („Fatal error : Could not send notification to $NOTIFY_SOCKET", seen 2026-10-16 and 2026-10-21 boots); measured 2026-10-26 20:06 UTC: the host clock 14 s behind DooPlex and demo-hp, `System clock synchronized: no`. demo-hp has the same package (4.8-4~bpo13+2) and `DAEMON_OPTS="-F 1"` and runs it. A drifting host clock feeds backup times (R-1206's class) and TLS. Found while timing the cloudflared update (R-1300). `audits/cloudflared-2026.10.3-2026-10-26/obs-n100-clock.txt` | OPEN — filed 2026-10-26 | — | find why the notify socket fails on this host only (compare the unit and `systemd-analyze` with demo-hp), fix it, and check whether a fresh install could hit it too | CC | | **R-1260** | Box system & updates | P3 | **Spring 2027 (2027-03-28): two clock-change effects in the controller's night (review round 2, HUNT-4 H2/H3).** The update leg's deadline is W + 5 h of REAL time while the full-system backup's gate counts wall-clock minutes, so a step can start after the gate stopped waiting (`felhom-controller/controller/internal/stacks/unattended.go:225`; `internal/quiesce/quiesce.go:922-933`); with W in 02:00–02:59 the DB dump and the second-drive copy start at the same instant (`internal/scheduler/scheduler.go:509`; VERIFIED: Go maps 2027-03-28 02:30 Europe/Budapest to 03:30 CEST). | OPEN | — | before 2027-03-28: one wall-clock basis for both, and a test at the spring date | CC | | **R-1367** | Box system & updates | P3 | **The host journal fills a small system disk: 61% of its lines are `pam_unix(sudo:session)` open/close pairs from the agent's sudo calls.** MEASURED 2026-11-09, one hour, same on demo-hp and the N100: ~14,000 journal lines, ~8,500 of them sudo session lines; the top commands are `smartctl -a` (1,074 per hour — one every ~3 s), `lxc-info -n` (662), `mkdir -p` (540), `lvs` (537), `pct exec` (~520). The journal grows by journald's default cap (10% of the filesystem, max 4 GB): the N100 sits at 4 GB, demo-hp was 3.8 GB on 2026-11-07 and reached 0.7 GB again two days after a vacuum to 500 MB. On a 39 GB root that space is what the whole-guest local copy needs (R-548). | OPEN — filed 2026-11-09 **2026-11-10 (space list, `documentation/audits/space-list-2026-11-10/TABLE.md`):** place H7: the N100 (4.28 GB, 74 files) and Tester 1 (4.29 GB, 81 files) sit at the journal's own cap; Tester 1 writes about 150 MB a day. Lines written by `sudo` are 92 / 92 / 90 % of all lines in one hour — this counts three lines for each call (the command and the session pair), while this row's 61 % counts the session pair only: the same fact, counted two ways. No rank change is proposed: the journal stops at its own cap (about 4.3 GB), so it costs space and log history, not safety. | — | Agent, through the signed config bundle: `Defaults:felhom-agent !pam_session` (and `!syslog` only if the command log has no reader — check the audit trail's needs first) in the sudoers file; a journald cap drop-in (e.g. `SystemMaxUse=500M`) on the host; and read why `smartctl -a` runs every ~3 s (the SMART poll's interval or a loop). Red-proof each in the agent's tests; measure the line rate after on demo-hp. Evidence: `/mnt/5_hdd/felhom.eu/evidence/demo-hp-images-2026-11-09/journal-noise.txt` (off-git) | CC | -| **R-1368** | Box system & updates | P3 | **Five places on the host's system disk only grow: nothing deletes them and no rule says how many to keep.** MEASURED 2026-11-10 on demo-hp, demo-felhom and Tester 1 (the space list, `documentation/audits/space-list-2026-11-10/TABLE.md` places H5, H6, H9, H12, H13). (1) **Old kernels** (`/lib/modules`, `/boot`): 8 / 8 / 3 kernels = 8.15 / 8.15 / 3.05 GB. The ring-0 boxes got 7 kernels in 37 days and no kernel was ever removed: the update wrapper refuses a plan that removes a package (`11-os-updates.md` rule R4), and nothing runs `apt autoremove` (searched: architecture folder, both registers, runbooks, three source trees — 0 hits). The N100's system disk grew 4.6 GiB in 26 days, about a kernel a week. (2) **The agent's self-update folder** `/var/lib/felhom-agent/selfupdate`: 49 / 48 / 33 binaries = 740 / 724 / 509 MB, one for each agent version the box ever got; no document names the folder. (3) **Guest template archives** `vzdump-lxc-9100-*` in `/var/lib/vz/dump`: 1 / 4 / 1 = 0.65 / 2.56 / 0.65 GB. (4) **Old agent binary copies** `/usr/local/bin/felhom-agent.bak-*`: 1 / 11 / 0 files, up to 155 MB. (5) **Logs of failed whole-guest backup runs** in the dump folder (small; 9 on demo-hp). **Members (answers marked N):** H5-3, H5-4, H6-3, H9-3, H9-4, H9-8, H12-3, H12-4, H13-3, H13-4. | OPEN — filed 2026-11-10 (space list) | the kernel part needs the operator's word (it changes what rule R4 allows) — STATUS D67 | Agent: after a good update keep the running kernel, the one before it and the newest, and remove the rest — ring 0 first; keep the newest N self-update binaries and `.bak` copies; keep one template archive. Each with a test that a kept item is never removed. | CC | +| **R-1368** | Box system & updates | P3 | **Five places on the host's system disk only grow: nothing deletes them and no rule says how many to keep.** MEASURED 2026-11-10 on demo-hp, demo-felhom and Tester 1 (the space list, `documentation/audits/space-list-2026-11-10/TABLE.md` places H5, H6, H9, H12, H13). (1) **Old kernels** (`/lib/modules`, `/boot`): 8 / 8 / 3 kernels = 8.15 / 8.15 / 3.05 GB. The ring-0 boxes got 7 kernels in 37 days and no kernel was ever removed: the update wrapper refuses a plan that removes a package (`11-os-updates.md` rule R4), and nothing runs `apt autoremove` (searched: architecture folder, both registers, runbooks, three source trees — 0 hits). The N100's system disk grew 4.6 GiB in 26 days, about a kernel a week. (2) **The agent's self-update folder** `/var/lib/felhom-agent/selfupdate`: 49 / 48 / 33 binaries = 740 / 724 / 509 MB, one for each agent version the box ever got; no document names the folder. (3) **Guest template archives** `vzdump-lxc-9100-*` in `/var/lib/vz/dump`: 1 / 4 / 1 = 0.65 / 2.56 / 0.65 GB. (4) **Old agent binary copies** `/usr/local/bin/felhom-agent.bak-*`: 1 / 11 / 0 files, up to 155 MB. (5) **Logs of failed whole-guest backup runs** in the dump folder (small; 9 on demo-hp). **Members (answers marked N):** H5-3, H5-4, H6-3, H9-3, H9-4, H9-8, H12-3, H12-4, H13-3, H13-4. | OPEN — filed 2026-11-10 (space list) **2026-11-10 12:22 — RULED (D67 = yes, as a separate step; `09` §3 decision 286):** the box may remove old kernels by itself; rule R4 stays as it is for update plans; the clean-up is its own step with its own narrow rule (old kernel packages only, only after a good boot on the newest kernel). | the kernel part: the hand proof on demo-hp (`documentation/audits/kernel-cleanup-spike-2026-11-10/`), then an agent release | Agent: after a good update keep the running kernel, the one before it and the newest, and remove the rest — ring 0 first; keep the newest N self-update binaries and `.bak` copies; keep one template archive. Each with a test that a kept item is never removed. | CC | | **R-1369** | Box system & updates | P3 | **When a disk is full there is no written way out: no runbook and no self-repair, for the host system disk, the thin pool, the guest disks or a data drive.** Found 2026-11-10 (the space list, `documentation/audits/space-list-2026-11-10/TABLE.md`, question 7). One missing runbook, seen from 21 places; the search of the runbooks folder for a disk-full procedure gave 0 hits (`evidence/searches.txt` S6). The alarms exist (hub: 90 / 95 % host disk, 85 / 90 % thin pool; controller: 85 / 95 % on the data volume and each drive) but they end in a mail, not in a step. For three small places nobody wrote what fails when they are full (EFI partition, host and guest temp folders). **Members (answers marked N):** H1-7, H2-7, H5-7, H9-7, H10-5, H10-7, H12-7, H13-7, H15-5, G1-7, G2-7, G7-7, G12-7, G13-7, G14-7, G17-5, D1-7, D2-7, D3-7, D6-7, D7-7, D8-7, D9-7, D10-7. | OPEN — filed 2026-11-10 (space list) | — | Docs: one runbook „a disk is full” with one section per disk (host system disk, thin pool, guest root, data volume, data drive): what to look at first, what is safe to delete (the places of R-1368 and R-1367), what is never deleted by hand (household data, the kept-data rulings). Rehearse it once on demo-hp. | CC | -| **R-1370** | Box system & updates | P3 | **The host's system disk has no space budget: no document says how much the host's own files may take, and the installer's sizing rule covers the guest only.** Found 2026-11-10 (the space list, `documentation/audits/space-list-2026-11-10/TABLE.md` place H1, answer H1-3; search S5 — 0 hits). Today: demo-hp 58 % of 41 GB, N100 38 % of 101 GB, Tester 1 34 % of 63 GB — and the parts that grow are the journal (R-1367), old kernels and agent binaries (R-1368), old backup copies (R-1087) and the local whole-guest copy (R-548). Second half, known but with no row until now: on a small disk the guest's own guards read the guest's 70 GiB while the thin pool behind it holds 54 GiB (demo-hp: 102 GiB promised on a 53.9 GiB pool, 70.67 % used), so only the hub's thin-pool alarm stands before a full pool. **Member:** H1-3. | OPEN — filed 2026-11-10 (space list) | an operator pick: a written budget or not — STATUS D69 | Docs: a short „disk space” section in an architecture document: each part of the system disk with its limit and its cleaner, pointing at the audit table. Then the installer can refuse a disk that cannot hold the sum. | CC | +| **R-1370** | Box system & updates | P3 | **The host's system disk has no space budget: no document says how much the host's own files may take, and the installer's sizing rule covers the guest only.** Found 2026-11-10 (the space list, `documentation/audits/space-list-2026-11-10/TABLE.md` place H1, answer H1-3; search S5 — 0 hits). Today: demo-hp 58 % of 41 GB, N100 38 % of 101 GB, Tester 1 34 % of 63 GB — and the parts that grow are the journal (R-1367), old kernels and agent binaries (R-1368), old backup copies (R-1087) and the local whole-guest copy (R-548). Second half, known but with no row until now: on a small disk the guest's own guards read the guest's 70 GiB while the thin pool behind it holds 54 GiB (demo-hp: 102 GiB promised on a 53.9 GiB pool, 70.67 % used), so only the hub's thin-pool alarm stands before a full pool. **Member:** H1-3. | OPEN — filed 2026-11-10 (space list) **2026-11-10 12:22 — RULED (D69 = yes; `09` §3 decision 288):** the section goes inside `16-storage-physical-identity.md`, no new document. | — | Docs: a short „disk space” section in an architecture document: each part of the system disk with its limit and its cleaner, pointing at the audit table. Then the installer can refuse a disk that cannot hold the sum. | CC | | **R-984** | Box system & updates | P4 | **Host and agent hardening, low risk each: the backup-target route has no role check; the unsigned guest spec has no size bounds; signed ops have no maximum validity; the guarded mkfs does not refuse LVs, zvols or RAID devices; the local API is reachable from the LAN by a static route; a sudoers inspect pattern is wider than needed; install passes secrets on the command line; guest settings files are world-readable; the host offers rpcbind and DNS on the LAN.** Fix each in its own small change. Security review 2026-10-12 (`audits/security-review-2026-10-12/`); detail held off-git for the operator (`/mnt/5_hdd/felhom.eu/evidence/security-review-2026-10-12-PRIVATE/`). | OPEN | — | Batch into hardening work | CC | | **R-979** | Box system & updates | P3 | **Controller updates are trusted by registry tag alone (no digest, no signature), and the Update button offers any newer tag, even an unvouched one; the built-in traefik, cloudflared and FileBrowser images are also pinned by tag only.** Whoever can push to the registry decides what runs. Fix: pin by digest from the hub's vouched list; offer only vouched versions. Security review 2026-10-12 (`audits/security-review-2026-10-12/`); detail held off-git for the operator (`/mnt/5_hdd/felhom.eu/evidence/security-review-2026-10-12-PRIVATE/`). | OPEN — design-proposal | — | Design note, then build | CC | | **R-974** | Box system & updates | P3 | **A compromised host agent can likely become root on the host through the root wrapper that applies PBS settings: the wrapper accepts a folder path inside the agent's own writable tree and then acts on it as root.** Static (the symlink behaviour was reasoned, not run). Same class as R-861. Fix: a fixed root-owned folder, and refuse symlinks before any root action. Security review 2026-10-12 (`audits/security-review-2026-10-12/`); detail held off-git for the operator (`/mnt/5_hdd/felhom.eu/evidence/security-review-2026-10-12-PRIVATE/`). | OPEN | — | Fix the wrapper with a test on a throwaway box | CC | @@ -323,7 +323,7 @@ stopping line that lies. | **R-1361** | Monitoring & notifications | P2 | **An event the box sends while the hub cannot be reached is lost: 3 tries over 9 s, then dropped.** Walked 2026-11-03 on Tester 1 (hub blackholed 13 min): the box ran normally, an app install worked, a crash loop stopped the app and held it, and `app_stopped_unhealthy` and `app_held` failed after 3 attempts (`notifier.go`). Afterwards NOTHING was re-sent: the hub's log shows no event from the outage, its „Held apps" had no row (`a row existed: false`), and the hold reporter had already recorded the app as reported (`holdreport.go`, the push is asynchronous) so only its periodic re-send can repair it. Any DooPlex restart (2026-11-01 was one) can swallow a household's and the operator's mails this way. `audits/security-2026-11-02/part5/outage-hub.log` | OPEN — filed 2026-11-03 **2026-11-03, a second cost seen:** the walk's cut (01:17–01:39 UTC) covered Tester 1's 01:30 dump, its `db_dump_completed` was lost, and at 04:00 UTC the hub mailed `expected_dbdump_missed` „No DB dump completed or failed since midnight", while the box's own report read `last_db_dump` 03:15 UTC. A lost event becomes a false alarm. | — | a small on-disk outbox for events, sent in order when the hub answers (a design: which types, how long kept); the hold reporter marks „reported" only after a 2xx. Test red first | CC | | **R-1363** | Monitoring & notifications | P3 | **A household's mail ends with raw JSON: `Megjegyzés: {"avail_gb":5.192043304443359,"band":"warning",...}`.** Seen in the walks of 2026-11-02 (`audits/security-2026-11-02/part5/mail-fill-household.txt`, `mail-crash-household.txt`). `api/handler.go` adds the details as the „Megjegyzés" line; a golden pins it (`mail_golden_test.go`), so it was once wanted. The sentence itself is right and Hungarian. | OPEN — filed 2026-11-03 | — | drop the line from a household's mail, or render known fields in words; the operator's mail keeps it | CC | | **R-1365** | Monitoring & notifications | P3 | **A security-watch source that stays down mails once and never again; after that only one line of the Monday summary says so.** An open advisory reminds every 7 days, a failed source does not (`08` §11 [DESIGN], „once per streak"). The cost was seen 2026-10-28 → 11-02: one mail, then a week of silence. With the seven pins that can never be read now a stated GAP (R-1334), a streak means a real outage. | WAITING-ON-OPERATOR — D66 | D66 | on yes: `plan()` mails a streak again every 7 days, with a test seen failing; `08` §11's line changes | operator (decision), CC (build) | -| **R-1371** | Monitoring & notifications | P3 | **Seven places have no space alarm, and the host-disk alarm that does exist goes to the household.** Found 2026-11-10 (the space list, `documentation/audits/space-list-2026-11-10/TABLE.md`, question 6). (1) **The guest root disk has no watcher.** The controller watches `/` and the system data path, but inside its container both are the data volume (measured on all three boxes, `evidence/extra/controller-fs-view.txt`); the 32 GiB guest root disk, which holds `/opt/docker/stacks`, is not a target. Closed row R-521 says it is — true only before the two volumes were merged; capability-map row C13 („warned before a filesystem fills — per filesystem”) does not hold for this one filesystem (the map's status is not changed here). (2) **The same filesystem is two targets**, and warnings are de-duplicated by path, so two warnings for one full disk are expected (read from source, not proved live; the comment at `cmd/controller/main.go:2694-2707` says the opposite). (3) **`host_disk_critical` and `storage_fill_critical` are mailed to the household by default** (`hub/internal/claim/engine.go:229-243`), but only the operator can free a host disk; the seed list was chosen as „critical only” and the question „can this reader act on it” was not asked. No architecture document names the host-disk event (search S4; `08-alarm-ladder.md` names the thin-pool one). (4) Small places with no alarm: EFI partition, temp folders, guest system log, guest package cache. **Members (answers marked N):** H10-6, H15-6, G1-6, G13-6, G15-6, G16-6, G17-6. | OPEN — filed 2026-11-10 (space list) | part 3 needs an operator pick — STATUS D68 | Controller: add the guest root disk as a fill-watch target, de-duplicate targets by filesystem, correct the comment; red-proof with two paths on one filesystem. Hub: after the pick, route the two host-disk events. Docs: name the host-disk alarm and its reader in `08-alarm-ladder.md`. | CC | +| **R-1371** | Monitoring & notifications | P3 | **Seven places have no space alarm, and the host-disk alarm that does exist goes to the household.** Found 2026-11-10 (the space list, `documentation/audits/space-list-2026-11-10/TABLE.md`, question 6). (1) **The guest root disk has no watcher.** The controller watches `/` and the system data path, but inside its container both are the data volume (measured on all three boxes, `evidence/extra/controller-fs-view.txt`); the 32 GiB guest root disk, which holds `/opt/docker/stacks`, is not a target. Closed row R-521 says it is — true only before the two volumes were merged; capability-map row C13 („warned before a filesystem fills — per filesystem”) does not hold for this one filesystem (the map's status is not changed here). (2) **The same filesystem is two targets**, and warnings are de-duplicated by path, so two warnings for one full disk are expected (read from source, not proved live; the comment at `cmd/controller/main.go:2694-2707` says the opposite). (3) **`host_disk_critical` and `storage_fill_critical` are mailed to the household by default** (`hub/internal/claim/engine.go:229-243`), but only the operator can free a host disk; the seed list was chosen as „critical only” and the question „can this reader act on it” was not asked. No architecture document names the host-disk event (search S4; `08-alarm-ladder.md` names the thin-pool one). (4) Small places with no alarm: EFI partition, temp folders, guest system log, guest package cache. **Members (answers marked N):** H10-6, H15-6, G1-6, G13-6, G15-6, G16-6, G17-6. | OPEN — filed 2026-11-10 (space list) **2026-11-10 12:22 — RULED (D68 = operator only; `09` §3 decision 287):** the household is not mailed about a host disk it cannot free. | — | Controller: add the guest root disk as a fill-watch target, de-duplicate targets by filesystem, correct the comment; red-proof with two paths on one filesystem. Hub: after the pick, route the two host-disk events. Docs: name the host-disk alarm and its reader in `08-alarm-ladder.md`. | CC | ## Hub & operator — 14 rows (P3 3, P4 11)