build of release 4 (2026-11-15): report, register (R-1397 closed; R-1400, R-1401 filed), status (D86, D87), context
gates / gates (push) Successful in 2m13s
gates / gates (push) Successful in 2m13s
No box changed, nothing released. Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
1 parent
c72ecf52b4
commit
5c3b17283b
6 files changed
+201
-8
No files matched your search
+21
@@ -16,6 +16,27 @@
|
||||
> and holds nothing of its own; this file does hold its own content, namely the standing rulings below.
|
||||
|
||||
|
||||
> **2026-11-15 afternoon (unattended) — release 4 („the promises”) is BUILT IN SOURCE; nothing is released.**
|
||||
> Report: `REPORT-build-release-4-2026-11-15.md`. Heads: `felhom.eu` hub code to `c72ecf52`, controller `c5acb91`,
|
||||
> installer 1.38.0 on `main` (NOT tagged); the agent is untouched. Rulings: `09` §3 decisions 308–312 (D83, D84, D85).
|
||||
> What a session must know before it touches this code: (1) **Off-site end of a removed app** (`07` §8.2f): the box's
|
||||
> record is `settings.offsite_ends`, written only by `backup.StartOffsiteEnd`; EVERY install deletes it at one point
|
||||
> (`stacks.SaveAppConfig`); the hub agrees from its own table `offsite_app_presence` and per snapshot id; the box
|
||||
> re-reads its records immediately before the forget; the box sends end records only to a hub that answered
|
||||
> `accepts_ended`; the household's receipt mail is written by the HUB (`householdReceiptEvents`), never from the box's
|
||||
> words. Hub-made operator events are NOT in `allowedEventTypes` (a box could post them). (2) **Installer:**
|
||||
> `check_system_disk` is first in the preflight; `--accept-small-disk`. (3) **Own names:** `monitor.OwnNameChecker`,
|
||||
> names only from the setting `HUB_OWN_NAMES` — **not in the manifest yet; the release adds it** (`08` §12.3).
|
||||
> **Decided by CC unattended — operator may reverse (D87 asks):** one weekly window removes at most the cap's size of
|
||||
> a removed app's copies beside the cap, and a removal of more than half of the store waits one week and mails the
|
||||
> operator. Options: as D84 was worded (everything the hub agreed to, at once) — then a taken-over box needs only 30
|
||||
> days of patience to empty the store in one window with no mail; or the bound — an honest large removal takes a
|
||||
> week or more longer. Reversible: it is two numbers and one wait in `hub/internal/offsitekeys/ended.go`. Also decided
|
||||
> the same way: the receipt mail ignores the household's switches; no end record on a NAS target; „delete in 30 days”
|
||||
> for every removed app with copies and no mark; an app the hub never saw starts its 30 days at the first claim, with
|
||||
> a mail to the operator. Designs, not built: `03` §12a item 8 (a blind box reports why), `05` §14.3 (the delete
|
||||
> journal's id; D86). Rows: R-1397 closed; R-1398, R-1400, R-1401 opened.
|
||||
|
||||
> **2026-11-15 (attended release run) — releases 2b and 3 are RELEASED; the note below is history.**
|
||||
> Report: `REPORT-release-2b-3-2026-11-15.md`. Hub 0.182.0 (deployed 09:48 CET on the operator's yes), agent 0.175.1
|
||||
> (vouched 11:07:35; 0.175.0 exists and is NOT vouched), controller 0.353.0 (global floor 10:26:53 UTC, MinAgent
|
||||
|
||||
@@ -0,0 +1,159 @@
|
||||
# Build of release 4 („the promises”) — 2026-11-15 afternoon, unattended, commit only
|
||||
|
||||
**No box was changed and none was read. Nothing was released.** No release, no deploy, no vouch, no floor change, no
|
||||
manifest change, no golden, no installer tag. No ep0 change. No call to the off-site provider, Cloudflare or the mail
|
||||
service: the tests use the repositories' fakes and a TLS server on the test machine. No call from the live hub to
|
||||
anything new. No mail or alarm that can reach a household. Nothing removed from the `sec` store. No text published.
|
||||
Provisioned nothing.
|
||||
|
||||
Two helpers worked on Part A (one built, one reviewed); each got the brief's fences word for word.
|
||||
|
||||
## 1. What is ready to release
|
||||
|
||||
| Part | Repo and commit | Proof it still needs on a box | Who must say yes |
|
||||
|---|---|---|---|
|
||||
| **A — the off-site copies of a removed app end after 30 days** | controller `c5acb91` (CI by commit: see §8); hub `1e34953a` | A whole run on demo-hp's scratch guest against a TEST store, never a household's: remove an app with „delete backup data”, read the date and the mail, take it back once, press again; then, with the hub's and the box's 30 days shortened ONLY in a test build, one weekly window that removes the ended app's snapshots and leaves a living app's; the 07:10 check silent. Also: how long `prune` takes, and the two pages in a browser. **Release the hub first** (a new box sends nothing of this to an older hub) | The operator: the hub deploy; the texts (§2) before either release |
|
||||
| **B — the installer stops below 200 GB** | felhom.eu `92853bed`, installer 1.38.0, **not tagged** | One fresh install on a VM with a 200G disk (no flag); the same VM with a 64G disk and `--preflight-only` must stop with the sentence and change nothing; one install with `--accept-small-disk` | The operator (a tag publishes it). **Read R-1398 first:** on the public image a refused machine repeats the refusal on its screen every 30 seconds and the hub is not told |
|
||||
| **C — the hub's own five names** | felhom.eu `c72ecf52` | After the deploy: the start line names the five names; the next day 06:40 one line per name with its end date; no mail (no date is within 14 days today) | The operator: the hub deploy, and **the five names in the manifest setting** (`08` §12.3 holds the lines; they are not in the manifest yet) |
|
||||
| **0 — the rulings** | felhom.eu `552e19cd` | none | — |
|
||||
|
||||
Each part can be released alone. A and C ride one hub release.
|
||||
|
||||
## 2. Every household-facing text, as built
|
||||
|
||||
The Hungarian date carries its own final dot („2026. december 15.”), so the Hungarian sentences have none after it.
|
||||
|
||||
| Where | Hungarian | English |
|
||||
|---|---|---|
|
||||
| The remove dialog, under „delete backup data” | „A helyi mentések most törlődnek. A távoli másolatok még 30 napig megmaradnak. Törlésük napja: {dátum} Addig a Mentések oldalon visszavonhatod.” | "The local backups are deleted now. The off-site copies stay for 30 more days. They are deleted on: {date}. Until then you can take this back on the Backups page." |
|
||||
| The off-site list, a marked app (also the notice after „delete in 30 days”) | „Törlésre kijelölve. Törlés napja: {dátum}” | "Marked for deletion. Deleted on: {date}." |
|
||||
| The button | „Mégis megtartom” | "Keep it after all" |
|
||||
| After the button | „A távoli másolatok megmaradnak.” | "The off-site copies are kept." |
|
||||
| „Keep” when nothing is marked, or the window is already removing | „Ennek az alkalmazásnak a távoli másolatai nincsenek törlésre kijelölve, vagy már törlődtek.” | "The off-site copies of this app are not marked for deletion, or are already deleted." |
|
||||
| The history line (after the app's name and a colon) | „A távoli másolatok törölve: {dátum}” | "The off-site copies were deleted on {date}." |
|
||||
| A removed app with copies and no mark | „Ennek az alkalmazásnak a távoli másolatai megmaradtak.” | "The off-site copies of this app were kept." |
|
||||
| Its button | „Törlés 30 nap múlva” | "Delete in 30 days" |
|
||||
| The press was refused | „Ennek az alkalmazásnak a távoli másolatait most nem lehet törlésre kijelölni.” | "The off-site copies of this app cannot be marked for deletion now." |
|
||||
| The save failed | „Nem sikerült elmenteni. Próbáld újra.” | "This could not be saved. Try again." |
|
||||
| **The mail, subject** | „[Felhom] Információ: {app}: a távoli másolatok törlésre kijelölve” | "[Felhom] Information: {app}: the off-site copies are marked for deletion" |
|
||||
| **The mail, the message line** (inside the hub's usual household frame; the hub writes it, never the box) | „{app}: az alkalmazás távoli másolatai törlésre vannak kijelölve. Törlésük napja: {dátum} Addig a Mentések oldalon a „Mégis megtartom” gombbal visszavonhatod.” | "{app}: the off-site copies of this app are marked for deletion. They are deleted on: {date}. Until then you can take this back on the Backups page with the “Keep it after all” button." |
|
||||
|
||||
Whole mails as the hub makes them: `hub/internal/notify/testdata/mail_goldens/{hu,en}/customer_shape_offsite_end_scheduled_receipt.txt`.
|
||||
**To read together with the new dialog line:** the dialog's older sentence („Az éjszakai restic pillanatképek nem
|
||||
törölhetők egyenként…”) stays above it and reads oddly beside it.
|
||||
A household with no notification address gets no mail, only the page.
|
||||
The installer's sentences are English only (the installer has no Hungarian text); they are in
|
||||
`16-storage-physical-identity.md` §14.5.
|
||||
|
||||
## 3. What stopped at a design
|
||||
|
||||
- **A box that cannot reach Proxmox still reports why** (Part D, second half; `03-host-agent.md` §12a item 8). It
|
||||
changes what a report means for the hub: every reader of a report in the hub must be listed first.
|
||||
- **The delete journal keeps an id that is not a name** (Part E; `05-hub-architecture.md` §14.3). Design only, by the
|
||||
brief. One decision (D86).
|
||||
- **A refused small-disk machine on the public image** (R-1398): the first-boot unit repeats the installer; it needs a
|
||||
new installer image, which is a public and lasting thing.
|
||||
- **In Part A, three limits are named, not closed** (`07` §8.2f): a box that stops listing a living app looks like an
|
||||
honest removal (bounded by the 30 days and by the cap's size per week); an install during the removal itself loses
|
||||
the copies; a box that names agreed ids but removes others is caught at 07:10, not at the window's close.
|
||||
|
||||
## 4. Decisions
|
||||
|
||||
**Taken by CC unattended — the operator may reverse each.**
|
||||
|
||||
1. **D84 was narrowed (D87 asks).** One weekly window removes at most the cap's size of a removed app's copies beside
|
||||
the cap; a removal of more than half of the store waits one week and mails the operator first. Why: the review
|
||||
showed that with D84 as worded, a taken-over box needs only 30 days of patience to have the hub agree to the whole
|
||||
store in one window, with no mail. Cost: an honest large removal takes a week or more longer.
|
||||
2. **The receipt mail ignores the household's notification switches** and never goes to the operator. Why: D84's
|
||||
reason is a login that someone else uses; that person could switch a group off first.
|
||||
3. **No end record on a box whose off-site target is the household's own NAS:** there is no hub window there, so the
|
||||
copies stay as today and the dialog says nothing.
|
||||
4. **„Delete in 30 days” is offered for every removed app with copies and no mark:** the box cannot tell „removed
|
||||
before this existed” from „kept the backups”.
|
||||
5. **An app the hub never saw installed:** the hub's 30 days start when the box first names it, and the operator gets
|
||||
a mail that day.
|
||||
|
||||
**For the operator (in `STATUS.md`):**
|
||||
|
||||
| # | Question | CC's pick | The other option | If nothing is decided |
|
||||
|---|---|---|---|---|
|
||||
| D86 | After a household is deleted, the delete journal keeps its id for ever, and an id can be a name. After one year: remove the id, or put a code in its place? | Remove it | A code: „was this id deleted?” can still be answered, but a code made from a name is still that person's data, and the hub keeps a key | The id stays for ever; the privacy sentence stays unpublished |
|
||||
| D87 | Keep CC's narrowing of D84 (item 1 above)? | Keep | Reverse: a large removed app goes in one window; the 30 days are the only brake | It stays as built |
|
||||
|
||||
## 5. Claims in the prompt that turned out wrong
|
||||
|
||||
1. **Part D, gap 1 („the hub reads the stanza and raises one alarm that names the cause”) was not to build: it is
|
||||
live** since hub 0.182.0 this morning, and it was seen from a real event on Tester 1.
|
||||
2. **„The hub's own records”** (Part A, must-hold 2) are not independent of the box: the hub's record of a box's app
|
||||
list is what the box reports. A box that stops listing an app makes the hub's 30 days run. The build bounds what
|
||||
that can cost; it cannot make the record independent.
|
||||
3. **„Build the five parts as designed” was not enough.** The design, built to the letter, had five defects that an
|
||||
independent review found (§6).
|
||||
4. **The window code** is in `hub/internal/offsitekeys/`; `06-offsite-connectivity.md` does not describe the window.
|
||||
|
||||
The three claims the reviewer asked to check:
|
||||
|
||||
- **„The weekly window can take a second allowance without touching the cap's own rule” — true.** The guard call and
|
||||
the cap are unchanged on both sides; the ended ids are added after the guard passes, and the close allows the cap
|
||||
plus the agreed ids. Pinned by tests and a mutation.
|
||||
- **„A household mail path exists that Part A can use” — true, but not as it stood.** The path exists. Four things in
|
||||
it would have stopped or doubled this mail (an information-level event is dropped; a warning also mails the
|
||||
operator; the switches; a cooldown per type). A one-entry register and a per-press key were added.
|
||||
- **„The size of the system disk can be read before the installer changes anything” — true**, with three reads
|
||||
(`pvs`, `lsblk`, one file under `/sys/block`), first in the preflight. Not true for a RAID or two physical volumes:
|
||||
there the size „cannot be read” and an appliance install stops with the flag named.
|
||||
|
||||
## 6. Per part
|
||||
|
||||
**Baselines at the start (12:54 CET):** felhom.eu `07bf7786`, controller `591195f`, agent `3411592`, catalog
|
||||
`f4c5c797`. Evidence: `documentation/audits/build-release-4-2026-11-15/{A,B,C}/`.
|
||||
|
||||
| Part | Commits | Tests and red-proofs | Documents read | Not proven |
|
||||
|---|---|---|---|---|
|
||||
| 0 | felhom.eu `552e19cd` | — | `09` §3 | — |
|
||||
| A, built by a helper | controller `f628cb5`; hub `01a106b7`, `a63f5b2b`, docs `bb226f23` | `TestD72_*`, `TestD84_*` in 11 packages; 110 mutations seen red (7 redone, said in the files) | `07` §8.2f; `09` §3 decisions 68, 69, 292, 309; `08` §6.5, §8.1; `05`; `06` (searched: no window there) | everything on a box: no press, no window, no file removed at a store, no mail in an inbox, no page in a browser; `prune`'s time |
|
||||
| A, after an independent review and three findings of the automatic security review | controller `3928c3d`, `c7e4ec9`, `c5acb91`; hub `875c339c`, `be272b7c`, `1fac9c16`, `6d2d4bd0`, `45848f6e`, `1e34953a` | each finding first as a test seen red; 55 more mutations seen red (4 redone); two mutations are said to be not provable | the same | the same |
|
||||
| B | felhom.eu `92853bed` | 8 tests, 15 mutations seen red (2 after the test was made real) | `16` §14.3, §14.5; the installer and its tests; `scripts/iso/felhom-bootstrap.sh` | not run on a machine |
|
||||
| C | felhom.eu `c72ecf52` | `TestOwnNames_*` (6), `TestD85_*` (2); 18 mutations seen red | `08` §12; the end-dates evidence, DH20 | no outside name was read; the five names are CC's reading of the evidence |
|
||||
| D | felhom.eu `90ba98b1` (design) | — | `03` §12a; `hub/collect.go` in the agent | all of it |
|
||||
| E | felhom.eu `90ba98b1` (design) | — | `05` §14.2; the two journal tables and every reader of them in the hub's source | all of it |
|
||||
| F | no commit: a read | — | the agent's `PoolAddVMID` and its test; the fresh-install evidence | the 500's body on the box was not kept |
|
||||
|
||||
**What the review of Part A found (all fixed):** a box could invent an ended app, or stop listing a living one, wait
|
||||
30 days and have the hub agree to the whole store in one window; a take-back or an install during the window still
|
||||
deleted; an import of the app kept the end record; a box could word the household's mail and send it without limit;
|
||||
a new box with an older hub stalled the weekly clean-up. The security review of the fixes found two more (a box could
|
||||
plant words that shortened the new wait; two different app sets shared one wait) — fixed.
|
||||
|
||||
**Part F, the answer:** the call is the agent's `PoolAddVMID` after a restore. On a fresh install the guest is already
|
||||
in the pool, Proxmox answers 500 „already”, and the agent reads that as success on purpose; a test pins it. No retry,
|
||||
no log line. R-1397 is closed as not a defect.
|
||||
|
||||
## 7. The register
|
||||
|
||||
248 rows before. **251 after.** Opened by this run: 3 (a refused small-disk machine tells nobody, R-1398; every
|
||||
household mail but one prints raw details, R-1400; the controller's fixture tool rewrites unrelated files, R-1401).
|
||||
Closed by this run: 1 (R-1397). The other session opened 1 (R-1399) in the same hours.
|
||||
Dated lines: R-1374, R-1370, R-1379, R-1396, R-1376.
|
||||
`unproven.py --summary`: 32 walked, 15 partial, 4 built, 4 missing, 23 not walked — no number moved. The capability
|
||||
map: no row moves for unreleased code.
|
||||
|
||||
## 8. CI, gates, other facts
|
||||
|
||||
- CI by commit hash is in the session's final message (the last push ran after this file was written).
|
||||
- One push was held for a time by two gates that were red from outside this run: the memory index was over its size
|
||||
(fixed: three of this session's index lines became one) and the site gate missed a logo of the other session's new
|
||||
app (the other session added it).
|
||||
- The other session (Securo onboarding) worked in the same clones; it pushed eight of this run's commits with its
|
||||
own, by agreement.
|
||||
- Instruction files changed: none. System poster: no fact changed (nothing is released).
|
||||
|
||||
## 9. Observations
|
||||
|
||||
- The hub's two marks `offsite_snapshot_listing:<household>` and `offsite_window_grant:<household>` stay after a
|
||||
household's delete — on R-1376, dated line.
|
||||
- Raw details in household mails — FILED: R-1400. The fixture tool — FILED: R-1401.
|
||||
- The 500 at a fresh install — NOT-A-FINDING: the designed „already a member” answer (R-1397 closed).
|
||||
- The automatic check warned about a TLS read with no chain check in the own-names check — NOT-A-FINDING: on purpose;
|
||||
a certificate that has ended must still give its date; nothing is trusted from the connection and nothing is sent.
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
**Ready for Tester 2? Yes — tell the friend go (`documentation/pilot/TESTER2-handover.md`).**
|
||||
|
||||
**Updated 2026-11-15 (midday).** Releases 2b and 3 are out: hub 0.182.0, agent 0.175.1 (vouched), controller 0.353.0 on every box, golden 0.353.0 (vouched), installer 1.37.0 (published). A box now trusts Proxmox through its own root certificate, and the hub tells you about a wrong box clock and other silent problems (`REPORT-release-2b-3-2026-11-15.md`).
|
||||
**Updated 2026-11-15 (evening).** Release 4 is built in source; nothing is released, no box was changed. It holds: a removed app's off-site copies end after 30 days, the installer stops below 200 GB, the hub reads its own names' end dates (`REPORT-build-release-4-2026-11-15.md`).
|
||||
|
||||
## What works
|
||||
- **The Plex attack did not reach Felhom's secrets** (R-1241).
|
||||
@@ -32,6 +32,8 @@ 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 |
|
||||
|---|---|---|---|---|---|---|
|
||||
| D87 | R-1374 | CC narrowed your D84 by itself: one weekly window removes at most the cap's size of a removed app's off-site copies, and a removal of more than half of the store waits one week and mails you first. Keep it? | **Keep** (a review showed that without it a taken-over box empties the whole store after 30 days, in one window, with no mail) | reverse: a large removed app goes in one window; the 30 days are then the only brake | it stays as built | — |
|
||||
| D86 | R-1376 | After a household is deleted, the delete journal keeps its id for ever, and an id can be a name. After one year: remove the id, or put a code in its place? | **Remove it** (the privacy sentence is then short and true; nothing in the hub reads the id after the year) | a code: you can still ask „was this id deleted?”, but a code made from a name is still that person's data, and the hub must keep a key | the id stays for ever and the privacy sentence stays unpublished | the privacy sentence |
|
||||
| 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 | — |
|
||||
@@ -39,7 +41,7 @@ Newest first. CC's pick is in the „Pick" column. Each row also has its full te
|
||||
| D7 | R-990, R-989 | Rule on the forum ideas and the selfh.st ideas now, or park them? | **Park them** (P4; nothing waits on them) | Rule now: about one hour of reading | nothing changes; the research gets old | — |
|
||||
|
||||
## Waiting on you — do
|
||||
**2026-11-15 midday.** 1. Hosts page: discard host `Tester4-2f0c25` and appliance `ab0b8310…` (CC's test install; else it alarms). 2. Once: read each off-site sub-account's label against the hub's list (R-1375). 3. The privacy sentence in the night report: publish or not. **2026-11-11.** 2. Hosts page: discard `3fb5fed3…`. 3. Rotate login `kisfenyo`'s Gitea token into the store as `GITEA_GIT_TOKEN` (R-925); the push after `sec put` is in R-1390. 4. Home DNS: remove the `felhom.eu` override (R-1389). 5. Read the dates only you can read (R-1381). 6. Search Console read (R-1035, 11-18).
|
||||
**2026-11-15 evening.** Read `REPORT-build-release-4-2026-11-15.md`: what is ready to release, and every text a household will see — read them first. **2026-11-15 midday.** 1. Hosts page: discard host `Tester4-2f0c25`, appliance `ab0b8310…` (else it alarms). 2. Once: read each off-site sub-account's label against the hub's list (R-1375). **2026-11-11.** 2. Hosts page: discard `3fb5fed3…`. 3. Rotate login `kisfenyo`'s Gitea token into the store as `GITEA_GIT_TOKEN` (R-925); the push after `sec put` is in R-1390. 4. Home DNS: remove the `felhom.eu` override (R-1389). 5. Read the dates only you can read (R-1381). 6. Search Console read (R-1035, 11-18).
|
||||
|
||||
**Still needed? (yes/no)** — answer per line.
|
||||
1. Look at `roms/roms/` on the N100's drive in the file manager (R-1099). (since 10-16)
|
||||
|
||||
@@ -26,6 +26,12 @@
|
||||
|
||||
---
|
||||
|
||||
## 2026-11-15 (evening) — R-1397 closed: the 500 at a fresh install is the designed „already a member” answer (full text of the row: `git show c72ecf52:documentation/backlog/OPEN-ITEMS.md`)
|
||||
|
||||
| Row | What | Closed | Evidence |
|
||||
|---|---|---|---|
|
||||
| **R-1397** | **One call of the agent to Proxmox is answered 500 during a fresh install, and the agent logs no ERROR line.** (P4) | CLOSED 2026-11-15 — NOT A DEFECT: read in source. The call is `proxmox.Client.PoolAddVMID` (`PUT /pools/felhom`, `vms=<id>`), which the bring-up runs after a restore to put the guest back into the pool. On a fresh install `pct restore --pool` has already made the guest a member, Proxmox answers 500 „already”, and the agent reads that answer as success on purpose (no retry, no log line; pinned by `TestPoolAddVMID_*` in `internal/proxmox/pool_test.go`). The body of the 500 on the box was not kept; a different error would have failed the bring-up, and the install ended „SUCCESS” with 0 ERROR lines. No earlier install's evidence holds the access log of a day-0 | `felhom-agent/internal/proxmox/mutate.go` (`PoolAddVMID`); `documentation/tests/golden-0.353.0-2026-11-15/fresh-install/trust-state.txt` |
|
||||
|
||||
## 2026-11-15 — releases 2b and 3: R-1380, R-1395, R-1050 closed (full text of the rows: `git show f561c85b:documentation/backlog/OPEN-ITEMS.md`)
|
||||
|
||||
| Row | What | Closed | Evidence |
|
||||
|
||||
@@ -220,7 +220,8 @@ stopping line that lies.
|
||||
| **R-1263** | Backup & restore | P4 | **Small items from review round 2:** a LOCAL restore's put-back mails the operator „its off-site restore FAILED” (`felhom-controller/controller/cmd/controller/main.go:1514-1518`, shared via `restore_unit.go:517-518`); Remove — even „keep my data” — deletes undeclared volumes labelled with the app's project, which no tier holds (`internal/stacks/delete.go:763-764`, R-1117); the capped copy's `--delete` reads the source in the daemon's mount view, the emptiness check in the controller's (`tier2.go:834` vs `:464`); stale comments — `felhom-agent/internal/localapi/backup_cap.go:15` („keep-last”) and `restore_crash_putback.go:32` (names a test file that does not exist); the qBittorrent password goes to whatever answers the DNS name `qbittorrent` (`upwatch/explain.go:94,108-113`); kept-copy Remove has a check-to-remove gap (`tier2_kept.go:92-111`); the release-copy restore check trusts hashes stored on ep0 (`runbooks/total-loss-of-dooplex.md`); rrsync without `-munge`/`-wo` (`audits/day-2026-10-23/08-release-copy-D33.txt:6`). | OPEN | — | fix in each repo's next attended pass | CC |
|
||||
| **R-1294** | Backup & restore | P3 | **demo-hp's weekly off-site clean-up was refused by its own guard on 2026-10-26 (window 16): the plan would remove 209 of 359 snapshots, above the week's cap (179) — nothing was deleted, and each refused week adds to the next plan.** Seen in the operator mailbox during the 2026-10-26 release run (03:17Z, `offsite_prune_guard_refused`, error; details `count_before 359, count_after 359, outcome guard-refused`). The cap refusal is kept on purpose (R-824, R-867 closed the false ones); the open question is whether a store that once exceeds the cap can ever prune again by itself, or refuses every week while it grows. demo-hp is the Tier-0 box with many hand-made backups (sweeps, probes). Earlier cap refusals: demo-hp 2026-10-03 (window 1), demo-felhom 2026-10-05 (window 3). **2026-11-11:** the End-dates list leans on this row (`documentation/audits/end-dates-list-2026-11-11/TABLE.md` DB05). | **OPEN — the grant is SET (D55 = 260, `09` §3 decision 268)**: 2026-10-26 19:10:31Z through the operator's one-purpose token `cc-d55-window`, read back `max:260`; it is used at demo-hp's next window request (after its nightly off-site run, ~03:15Z). Close when that window prunes; then the operator revokes the token. **Earlier:** WAITING-ON-OPERATOR — 2026-10-26 evening: CC could NOT set the D54 grant — `POST /offsite/window-grant/demo-hp` (`max_remove=220`) with CC's hub token answered **403 „missing scope offsite:write"** (the hub log shows the refusal; nothing granted). The plan also grows: restic's dry-run 2026-10-26 18:56Z still 359 copies / plan 209 / default cap 179 (before tonight's run); a simulation of the keep rule adds ~14 per night (14 of 18 groups back up nightly), so ~223 at the night of 10-27 and ~237 at 10-28 — a cap of 220 would be refused again. STATUS D55: the operator grants it, with the cap. The grant opens the box's NEXT window request, which comes after its next nightly off-site run. Ruled D54 = prune once (`09` §3 decision 266). **Earlier:** WAITING-ON-OPERATOR — 2026-10-26 (read only, `audits/r1294-offsite-cap-2026-10-26/`): the plan is HONEST (restic's own dry-run: keep 150, remove 209; every removal 7–30 days old; every app keeps ≥ 9 or its last copies; the bulk is one test day, 2026-10-16, 152 snapshots). It can NOT recover by itself: the cap is half the store and grows ~49/week while the plan grows ~84/week. Only demo-hp has this shape (demo-felhom and Tester 1 pruned normally 10-26). The pick is STATUS D54. **Earlier:** OPEN **2026-11-10 (space list, `documentation/audits/space-list-2026-11-10/TABLE.md`):** place O1, listed from documents only (the off-site box was not read in this run — second pass). **2026-11-10:** the endings list leans on this row (`documentation/audits/endings-list-2026-11-10/TABLE.md` EC23-7). | — | read the guard's cap rule (controller off-site prune) against demo-hp's snapshot list: is the plan honest (old, superseded) or not; if honest, say how such a store gets back under the cap (an attended one-time prune, or a cap that follows the store) — a design question for the operator if it changes what a box may delete | CC |
|
||||
| **R-1362** | Backup & restore | P3 | **With the internet down, the Backups page takes over 2 minutes (135 s and 145 s measured; 5 s with only the hub down).** Walked 2026-11-03 on Tester 1: every other page answers at once on the home network. The page waits on something off-site inside its handler; a household that lost its line and opens exactly this page sees a hang. `audits/security-2026-11-02/part5/outage-wan.log` | OPEN — filed 2026-11-03 | — | name the wait with a timing, then give it a short deadline and show „the off-site state could not be read" | CC |
|
||||
| **R-1374** | Backup & restore | P3 | **Four kinds of copy are kept with no end named, and nobody is reminded of them.** Found 2026-11-10 (the endings list, `documentation/audits/endings-list-2026-11-10/TABLE.md` endings EC02, EC23, EC18, EC27; read in source; 9202 has no off-site store, so not measured). (1) **Off-site snapshots of a removed app**: the removal keeps them by ruling (closed R-474), and the weekly clean-up keeps the last snapshots of each app for ever (`internal/backup/offbox_window.go:80-82`), also for an app that is gone. No rule says when they end. (2) **A whole restore from the second drive** moves the old files beside the restored ones (`internal/backup/tier2_whole.go:52`, `:132`, `:345`); nothing removes them later and no page lists them. (3) **Exported app files** stay in the export folder of the drive; the pages can start, list and read an export, none deletes one, and nothing ages it (`internal/web/handler_export.go:30-87`). **Members (answers marked N):** EC02-4, EC23-4, EC18-4, EC27-4. | OPEN — **2026-11-15 12:49 — RULED (D84 = yes; `09` §3 decision 309).** Fix shape for part (1): the five parts of `07` §8.2f, with the ended apps' own allowance outside the weekly cap (only for ids the hub agreed to) and ONE mail to the household at the press of „delete backup data” (the app, the end date, how to take it back). Earlier: OPEN — **2026-11-14 (night build):** the design for part (1) is written, not built: `07-backup-architecture.md` §8.2f (the record, the date shown before the press, the take-back button, the deletion inside the weekly window after the hub agrees, 14 edge cases, the texts in Hungarian and English as a proposal). One open decision is in it: do the ended apps' snapshots count toward the window's weekly cap (CC's pick: no). Parts (2) and (3) are not touched. OPEN — filed 2026-11-10 (endings list) **2026-11-10 15:19 — RULED (D72 = yes, by the household's own choice; `09` §3 decision 292).** Not built. | — | Controller (D72): when the household pressed „delete backup data” for an app, its off-site copies end 30 days later, at the next clean-up after that day (the number of a restore copy, D62); when the household kept the backups, the off-site copies stay. The page shows the end date before anything is deleted — write that into `07-backup-architecture.md` before the build. Parts (2) and (3): a delete on the export page; a line on the kept-data page for the files a whole restore set aside. | CC |
|
||||
| **R-1374** | Backup & restore | P3 | **Four kinds of copy are kept with no end named, and nobody is reminded of them.** Found 2026-11-10 (the endings list, `documentation/audits/endings-list-2026-11-10/TABLE.md` endings EC02, EC23, EC18, EC27; read in source; 9202 has no off-site store, so not measured). (1) **Off-site snapshots of a removed app**: the removal keeps them by ruling (closed R-474), and the weekly clean-up keeps the last snapshots of each app for ever (`internal/backup/offbox_window.go:80-82`), also for an app that is gone. No rule says when they end. (2) **A whole restore from the second drive** moves the old files beside the restored ones (`internal/backup/tier2_whole.go:52`, `:132`, `:345`); nothing removes them later and no page lists them. (3) **Exported app files** stay in the export folder of the drive; the pages can start, list and read an export, none deletes one, and nothing ages it (`internal/web/handler_export.go:30-87`). **Members (answers marked N):** EC02-4, EC23-4, EC18-4, EC27-4. | NARROWED — **2026-11-15 (build of release 4): part (1) is BUILT on both sides, not released** (controller `main` after 0.353.0, hub `main` after 0.182.0; `07-backup-architecture.md` §8.2f `[FACT — built, not released]`). The record, the date before the press, the take-back, the hub's agreement by its own clock, the deletion inside the weekly window by id, the audit's explanation, one mail to the household at the press. An independent review found five defects, all fixed with tests seen red (a box could have the hub agree to the whole store; a take-back or an install during the window still deleted; an import kept the record; a box could word and flood the household's mail; a version skew stalled the clean-up). **Decided by CC unattended (D87 asks the operator):** one window removes at most the cap's size of ended-app snapshots beside the cap, and a request for more than half of the store waits one week with a mail to the operator. **Open limits, said in §8.2f:** a box that stops listing a living app looks like an honest removal (bounded by the cap per week, and by the 30 days); an install during the forget itself loses the copies; a box that names agreed ids but removes others is caught at 07:10, not at the close. **Nothing ran on a box or against a real store.** Parts (2) and (3) are not touched. Earlier: OPEN — **2026-11-15 12:49 — RULED (D84 = yes; `09` §3 decision 309).** Fix shape for part (1): the five parts of `07` §8.2f, with the ended apps' own allowance outside the weekly cap (only for ids the hub agreed to) and ONE mail to the household at the press of „delete backup data” (the app, the end date, how to take it back). Earlier: OPEN — **2026-11-14 (night build):** the design for part (1) is written, not built: `07-backup-architecture.md` §8.2f (the record, the date shown before the press, the take-back button, the deletion inside the weekly window after the hub agrees, 14 edge cases, the texts in Hungarian and English as a proposal). One open decision is in it: do the ended apps' snapshots count toward the window's weekly cap (CC's pick: no). Parts (2) and (3) are not touched. OPEN — filed 2026-11-10 (endings list) **2026-11-10 15:19 — RULED (D72 = yes, by the household's own choice; `09` §3 decision 292).** Not built. | — | Controller (D72): when the household pressed „delete backup data” for an app, its off-site copies end 30 days later, at the next clean-up after that day (the number of a restore copy, D62); when the household kept the backups, the off-site copies stay. The page shows the end date before anything is deleted — write that into `07-backup-architecture.md` before the build. Parts (2) and (3): a delete on the export page; a line on the kept-data page for the files a whole restore set aside. | CC |
|
||||
| **R-1401** | Backup & restore | P4 | **The controller's fixture tool rewrites unrelated files.** Found 2026-11-15: `-update-i18n-golden` writes `?v=ASSET` where 20 stored page fixtures hold `?v=test`, so a regeneration changes files that the change did not touch; the D72 build patched its 143 fixtures by hand, one line each. Cost: the next change of a shared page string does the same by hand, or commits noise. | OPEN — filed 2026-11-15 | — | make the tool and the stored fixtures agree on the asset version word, then regenerate once | CC |
|
||||
| **R-1385** | Backup & restore | P3 | **Two timed jobs can meet with no lock and no order (12 answers).** Found 2026-11-11 (the Clock list, class W3, `documentation/audits/clock-list-2026-11-11/TABLE.md`). MEASURED on the night of 2026-11-11: on Tester 1 and the N100 the whole-guest backup started at about 05:30 local, the minute of the off-site proof restore (CC09-5); on demo-hp one whole-guest backup started at 02:30:38, with the dump leg; on the N100 the whole-guest backup starts about 5 minutes later each day. From source: the controller's auto-update default is the minute the whole-guest gate opens (CC11-5); the second-drive copy and the abandon sweep wait only for the clock (CC02-5, CC19-5, CC21-5); the PBS verify can run beside a backup (CA13-5, CA04-5); the timers on DooPlex and ep0 are not ordered against the hub's copies (CH05-8, CH24-5, CH25-3, CH26-5, CH26-6; from documents only, not measured). No harm was seen; the durations are from small test stores. | OPEN — filed 2026-11-11 (clock list) | — | Measure one night with a large store on Tier 0 (as a task), then decide per pair: a shared flag, a fixed offset, or „harmless, written down”. | CC |
|
||||
|
||||
## Storage & devices — 15 rows (P3 6, P4 9)
|
||||
@@ -283,8 +284,9 @@ stopping line that lies.
|
||||
| **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. | NARROWED — **2026-11-15 06:35 — the FIRST real night removal: the N100, by itself, at 05:58 CET.** 8 kernels before, 2 after (it kept 7.0.14-26 and 7.0.14-28, the running one), 6 packages purged in 35 s, 6.81 GB gained (the wrapper's own figure; 65.1 GB free after), 0 left-over paths; the default kernel and the pinned file are unchanged (the file's time is still 2026-11-08); the hub's „Kernel step” cell reads „cleaned”; 0 failed units, 9 of 9 containers healthy, clock +0.06 s to DooPlex. demo-hp had a QUIET night (2 installed, nothing to remove) — it does not count; its 6 old kernels went on 2026-11-10 at 13:51, by day. **D82 count: the N100 1 of 2, demo-hp 0 of 2.** demo-hp can count only after two more kernels arrive (it holds 2 and keeps 2). Evidence: `audits/night-build-2026-11-14/E/`. Earlier: NARROWED — **2026-11-14 16:06 — RULED (D82, `09` §3 decision 307): a household's box may remove its old kernels, after two REAL night removals on each ring-0 box (the N100 and demo-hp); quiet nights do not count. Count so far: the N100 0, demo-hp 0 (the Tester 1 removal of 2026-11-14 was started by hand and is not a night). It needs a later agent release to switch it on.** Earlier: NARROWED — **2026-11-14 (release 2a): the old-kernel part is BUILT — agent 0.174.0, vouched 15:21 CET (`11` §5.11.1 `[FACT — built]`).** A ring-0 box removes its old kernels at night by the wrapper's own rule. On boxes: a real removal on Tester 1 (3 → 2 kernels, 1.12 GB, 8.5 s; the default, the pinned file, the generators and the state file unchanged; a second run removed nothing; one clean restart) — started by hand with a ring-0 mark set for the test on the operator's yes, because a night cannot be started by day (R-1394); dry runs on demo-hp (nothing to remove; refusals P1, P2, P3) and the N100 (6 of 8 will go). **LEFT for this part: the step by the agent at night — read the N100's and demo-hp's night of 2026-11-15; then a ruling for ring-1 boxes (D82).** Evidence `audits/release-2a-2026-11-14/`. The other four places of this row are unchanged. Earlier: 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). **2026-11-10:** the endings list leans on this row (`documentation/audits/endings-list-2026-11-10/TABLE.md` EA01-4, EA23-4, EA24-4, EA26-4). **2026-11-10 — the kernel part's fix shape is PROVEN by hand on demo-hp** (`documentation/audits/kernel-cleanup-spike-2026-11-10/`; design `11-os-updates.md` §5.11.1, not built): the rule removed 6 of 8 kernels and nothing else, 6.4 GB gained, boot settings unchanged, one orderly reboot back on the same kernel, a second run removed nothing. Not proven: a box whose running kernel is not its newest; a boot of the kept old kernel. **2026-11-10 — part (2) FIXED IN SOURCE, NOT RELEASED** (felhom-agent `776025c8`): after an update that ended well the agent removes every staged binary but the running version's; nothing is removed while an update is pending. `TestPrune_*` (6 tests, one runs the wrapper's real commit and rollback verbs), red seen three times. A box cleans its folder at the first good update after the release that carries it. Part (4), the `.bak-*` copies, is not reached (root-owned, made by a person). Parts (1), (3), (5) stay open. **2026-11-10 14:46 UTC — the kept old kernel boots:** on demo-hp the one-shot flag booted 7.0.14-26-pve to a healthy Line truncated
|
||||
| **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) **2026-11-10 (afternoon) — the runbook is written:** `documentation/runbooks/disk-full.md`, five parts, each hand step marked PROVEN (date and evidence; all on demo-hp) or NOT PROVEN. Still open: one rehearsal of the whole runbook on demo-hp; the NOT PROVEN steps (copies on a former target, template archives, the `.bak-*` binaries, the guest root disk); what fails when the EFI partition or a temp folder is full. | — | 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 — **2026-11-15 12:49 — RULED (D83 = refuse, with one named flag; `09` §3 decision 308).** Fix shape: the installer reads the size of the disk that holds the `pve` volume group before any change; below 200 × 10⁹ bytes an appliance install stops with the designed sentence; `--accept-small-disk` goes on, prints the cost, records `small_disk: true`; a BYO host is warned only; a size that cannot be read refuses on an appliance and names the flag (`16` §14.5). Earlier: OPEN — **2026-11-14 (night build):** the open point of D75 has a written design with a pick, not built: `16-storage-physical-identity.md` §14.5 — refuse below 200 GB on an appliance install, with one named flag for the operator; warn only on a BYO host; 8 edge cases. It waits for the operator's yes. 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. **2026-11-10 (afternoon) — the section is written:** `16-storage-physical-identity.md` §14 (45 places, the list „no limit, by ruling”, the budget, the open design points); `PROMPT-TEMPLATE.md` §N.5 keeps it true. The budget from measured numbers: the root needs about 14 GB when the whole-box copies go to a backup drive, and 28–54 GB at keep 3 when they do not. **D75 (for the operator):** the smallest system disk Felhom accepts. CC's pick: 128 GB only with a backup drive, 200 GB without one. The other option, 128 GB always, lets a box with many apps and no backup drive stop its local copies. With no ruling the installer accepts any disk. Open after the ruling: the installer's refusal. **2026-11-10 15:19 — RULED (D75 = one number, 200 GB, with or without a backup drive; `09` §3 decision 295).** This replaces CC's two-step pick. **Open, not ruled:** what the installer does below 200 GB — refuse, or warn. demo-hp (128 GB) stays as a test box. `16` §14.3 carries the ruling. | — | Design first: what the installer does below 200 GB (refuse, or warn) — a later session. Then the installer. | 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. | NARROWED — **2026-11-15 (build of release 4): BUILT, not released** — installer v1.38.0 on `main`, NOT tagged (`16` §14.5 `[FACT — built, not released]`): `check_system_disk` first in the preflight; an appliance below 200 × 10⁹ bytes stops; `--accept-small-disk` goes on, prints the cost, records `small_disk`; a BYO host is warned only; an unreadable size stops and names the flag. 8 tests, 15 mutations seen red. **Not run on a machine.** What it does not do is R-1398. For the release: the proof VM gets a 200G disk; demo-hp's reinstall needs the flag. Earlier: OPEN — **2026-11-15 12:49 — RULED (D83 = refuse, with one named flag; `09` §3 decision 308).** Fix shape: the installer reads the size of the disk that holds the `pve` volume group before any change; below 200 × 10⁹ bytes an appliance install stops with the designed sentence; `--accept-small-disk` goes on, prints the cost, records `small_disk: true`; a BYO host is warned only; a size that cannot be read refuses on an appliance and names the flag (`16` §14.5). Earlier: OPEN — **2026-11-14 (night build):** the open point of D75 has a written design with a pick, not built: `16-storage-physical-identity.md` §14.5 — refuse below 200 GB on an appliance install, with one named flag for the operator; warn only on a BYO host; 8 edge cases. It waits for the operator's yes. 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. **2026-11-10 (afternoon) — the section is written:** `16-storage-physical-identity.md` §14 (45 places, the list „no limit, by ruling”, the budget, the open design points); `PROMPT-TEMPLATE.md` §N.5 keeps it true. The budget from measured numbers: the root needs about 14 GB when the whole-box copies go to a backup drive, and 28–54 GB at keep 3 when they do not. **D75 (for the operator):** the smallest system disk Felhom accepts. CC's pick: 128 GB only with a backup drive, 200 GB without one. The other option, 128 GB always, lets a box with many apps and no backup drive stop its local copies. With no ruling the installer accepts any disk. Open after the ruling: the installer's refusal. **2026-11-10 15:19 — RULED (D75 = one number, 200 GB, with or without a backup drive; `09` §3 decision 295).** This replaces CC's two-step pick. **Open, not ruled:** what the installer does below 200 GB — refuse, or warn. demo-hp (128 GB) stays as a test box. `16` §14.3 carries the ruling. | — | Design first: what the installer does below 200 GB (refuse, or warn) — a later session. Then the installer. | CC |
|
||||
| **R-1398** | Box system & updates | P3 | **A machine that the installer refuses for a small system disk tells nobody but its own screen, and the hub does not read the „small disk” mark.** Found 2026-11-15 while building D83 (installer v1.38.0, not tagged). (1) On the public image the first-boot unit (`scripts/iso/felhom-bootstrap.sh`, „retry until success”) runs the installer again every 30 seconds: a refused 128 GB machine prints the refusal on its screen for ever, and the hub shows a bound appliance that never installs, with no reason. (2) An install that went on with `--accept-small-disk` sends `"small_disk":true` in its enrolment request; the hub ignores the field, so no page shows which boxes were accepted small (`16-storage-physical-identity.md` §14.5, the last row of the built table). | OPEN — filed 2026-11-15 | the next installer ISO for (1) | (1) a final exit code for a refusal that no retry can cure; the first-boot unit stops retrying on it, shows the sentence once, and tells the hub the reason; (2) the hub stores `small_disk` at the enrolment and shows it on the box's page | CC |
|
||||
| **R-1400** | Monitoring & notifications | P4 | **Every household mail but one prints the event's raw details as a line „Megjegyzés”.** Found 2026-11-15 while building the receipt mail of D84: the hub's household frame adds the event's details JSON under „Megjegyzés” (a note); the new receipt mail leaves it out, the other household mails keep it. A household reads a line of field names and values. Not measured: which mails, and how it reads in an inbox (`hub/internal/notify/testdata/mail_goldens/`). | OPEN — filed 2026-11-15 | — | read the household mail frame: which event types carry details worth a sentence, and drop the raw line for the rest | 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 |
|
||||
@@ -330,10 +332,9 @@ stopping line that lies.
|
||||
| **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) **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. **2026-11-10 — parts (2) and (3) FIXED IN SOURCE, NOT RELEASED.** (2) felhom-controller `844f19f1`: one fill target per filesystem (`system.FilesystemKey`; the container's `/` is an overlay with its own device number, so the identity is taken from a Docker-kept file — `documentation/audits/space-list-2026-11-10/evidence/extra/fs-identity.txt`); `TestR1371_*`, red seen three times; not proven on a box. (3) hub source, no build: `host_disk_warning` / `host_disk_critical` are operator-only and the critical is not seeded; `storage_fill_*` reaches a household only for `usb`, `local-dir`, `nfs`, `cifs` (`notify.operatorOnlyFor`; `08-alarm-ladder.md`); `TestD68_*`, red seen three times. Parts (1) and (4) stay open: who watches the guest root disk is a design point in `16-storage-physical-identity.md`. **2026-11-10 (afternoon) — two design points added** (`16-storage-physical-identity.md` §14.4): a drive in the backup role reports as `usb` or `local-dir`, so the household gets the `storage_fill` mail for a drive it must not clean by hand; the hub's first list for a household still holds `storage_fill_critical` until the box sends its own list (not measured on the running hub). Also noted: the closed row R-521 and `felhom-controller/controller/cmd/controller/r521_f7_rootfs_test.go:29,36` call the watched path „the guest's root filesystem”; it is the container's `/`, an overlay on the data volume. The guest's real root disk is the one part (1) says nobody watches. **2026-11-10 (release run) — parts (2) and (3) RELEASED** (`documentation/audits/release-space-fixes-2026-11-10/`). (2) controller 0.352.0, global floor 15:31 UTC: on scratch guest 9202 one fill sent TWO warnings on the version before and ONE on the new one (so the double warning is now seen on a box, not only read from source); Tester 1, demo-hp and demo-felhom each check 2 filesystems where they checked 3. (3) hub 0.180.0 live since 15:12 UTC, Synced/Healthy; proof = the `TestD68_*` tests and the deployed commit. **Not proven on the running hub:** that a household which saved its own alarm list before no longer gets the host-disk type — the pages that show a household's list refuse a token (by design, `05` §17) and no test alarm was made (`16` §14.4). **Still open:** (1) the guest root disk has no watcher (design point); (4) the small places; a real fill on a household's box. | — | 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-1379** | Monitoring & notifications | P3 | **An end date exists and nobody is warned before it (18 answers).** Found 2026-11-11 (the End-dates list, class T1, `documentation/audits/end-dates-list-2026-11-11/TABLE.md`; dates measured read-only on three boxes and from public certificates). No alarm fires before any of these ends: the box's web certificate (DB01-5, DB01-7: Traefik renews by itself; a renewal that fails is silent until the day), the hub address certificate (DH20-5), the operator tokens with a 90-day life (DH22-5), a node's Tailscale key (DH30-5), Debian's package keys (DB16-5), the 30-day restore copy (DB24-5), the end of OS security support (DB17-5), app and tunnel-client images (DB18-5, DB19-5), the local-API certificate (DB03-5), and the outside accounts: mail key, domains, Cloudflare, Hetzner, GitHub and Gitea tokens (DH23-5, DH24-5, DH27-5, DH28-5, DH29-5, DH31-5, DH32-5). Decision D77 in `STATUS.md` asks if the product warns 14 days before. **Ruled 2026-11-11 13:17: yes, D77 (`09` §3 decision 298). Not built.** | NARROWED — **2026-11-15 12:49 — RULED (D85 = yes; `09` §3 decision 310).** Fix shape: once a day the hub opens a TLS connection to each of its five public names (`08` §12.2 row DH20; the list is configuration), reads the end date, and raises the operator-only alarm 14 days before, per name; a name that cannot be reached is a line in the daily ledger, not an end-date alarm. Earlier: NARROWED — **2026-11-15: the two warnings are LIVE** (hub 0.182.0, controller 0.353.0). The three test boxes' reports carry their web certificate's end date and issuer (read from a copy of the live database: 2026-12-31, 2027-01-02, 2027-01-19); the hub's end-date check set its baseline at the start. **Not seen:** no real certificate or token 14 days from its end, so no warning was seen. The other sixteen stay a design table; D85 is not ruled. Earlier: NARROWED — the two ruled warnings are built, not released. **2026-11-14 (night build):** the hub warns the operator 14 days before an operator token ends and 14 days before a box's web certificate ends (the box reads the date from its own store and sends it in its report) — `08-alarm-ladder.md` §12.1. The other sixteen are a design table there (§12.2): one is small and waits for a yes (the hub's own five public names), one is a design question (a household's Cloudflare token), the rest stay the operator's list. Not seen on a box or a deployed hub. OPEN — filed 2026-11-11 (end-dates list) | — | Fix shape (ruled, not built): the box reads its web certificate's date, the hub reads its tokens' dates, one operator alarm 14 days before. The outside accounts stay a list the operator reads (`documentation/audits/end-dates-list-2026-11-11/README.md`). | CC |
|
||||
| **R-1379** | Monitoring & notifications | P3 | **An end date exists and nobody is warned before it (18 answers).** Found 2026-11-11 (the End-dates list, class T1, `documentation/audits/end-dates-list-2026-11-11/TABLE.md`; dates measured read-only on three boxes and from public certificates). No alarm fires before any of these ends: the box's web certificate (DB01-5, DB01-7: Traefik renews by itself; a renewal that fails is silent until the day), the hub address certificate (DH20-5), the operator tokens with a 90-day life (DH22-5), a node's Tailscale key (DH30-5), Debian's package keys (DB16-5), the 30-day restore copy (DB24-5), the end of OS security support (DB17-5), app and tunnel-client images (DB18-5, DB19-5), the local-API certificate (DB03-5), and the outside accounts: mail key, domains, Cloudflare, Hetzner, GitHub and Gitea tokens (DH23-5, DH24-5, DH27-5, DH28-5, DH29-5, DH31-5, DH32-5). Decision D77 in `STATUS.md` asks if the product warns 14 days before. **Ruled 2026-11-11 13:17: yes, D77 (`09` §3 decision 298). Not built.** | NARROWED — **2026-11-15 (build of release 4): D85 is BUILT, not released** (hub `main` after 0.182.0; `08` §12.3): once a day the hub reads the end date of each name in the setting `HUB_OWN_NAMES` and warns 14 days before, per name; a name that does not answer is its own line; with no setting the hub makes no call. **The release must add the setting to the manifest** (the lines are in `08` §12.3; the operator confirms the five names). No outside name was read. Earlier: NARROWED — **2026-11-15 12:49 — RULED (D85 = yes; `09` §3 decision 310).** Fix shape: once a day the hub opens a TLS connection to each of its five public names (`08` §12.2 row DH20; the list is configuration), reads the end date, and raises the operator-only alarm 14 days before, per name; a name that cannot be reached is a line in the daily ledger, not an end-date alarm. Earlier: NARROWED — **2026-11-15: the two warnings are LIVE** (hub 0.182.0, controller 0.353.0). The three test boxes' reports carry their web certificate's end date and issuer (read from a copy of the live database: 2026-12-31, 2027-01-02, 2027-01-19); the hub's end-date check set its baseline at the start. **Not seen:** no real certificate or token 14 days from its end, so no warning was seen. The other sixteen stay a design table; D85 is not ruled. Earlier: NARROWED — the two ruled warnings are built, not released. **2026-11-14 (night build):** the hub warns the operator 14 days before an operator token ends and 14 days before a box's web certificate ends (the box reads the date from its own store and sends it in its report) — `08-alarm-ladder.md` §12.1. The other sixteen are a design table there (§12.2): one is small and waits for a yes (the hub's own five public names), one is a design question (a household's Cloudflare token), the rest stay the operator's list. Not seen on a box or a deployed hub. OPEN — filed 2026-11-11 (end-dates list) | — | Fix shape (ruled, not built): the box reads its web certificate's date, the hub reads its tokens' dates, one operator alarm 14 days before. The outside accounts stay a list the operator reads (`documentation/audits/end-dates-list-2026-11-11/README.md`). | CC |
|
||||
| **R-1383** | Monitoring & notifications | P3 | **A job on a timer does not run, gives up, or loses its state at a restart, and nobody is told (23 answers).** Found 2026-11-11 (the Clock list, class W1, `documentation/audits/clock-list-2026-11-11/TABLE.md`; read in source, times measured read-only on three boxes). The four worst: the guest-power watchdog gives up with one journal line (CA07-7, CA07-8); a signed job that is refused or runs out stays silent, so an agent update never arrives (CA09-4, CA09-7); the hub's daily checks are skipped with no trace when the hub is down at their minute (CH02-4, CH02-8, CH11-4, CH16-4); an operator mail waiting for a retry is lost at a hub restart, and a household mail is never retried (CH04-4, CH04-7, CH04-8, CH03-7). The others: CA13-7, CC07-7, CC12-4, CC19-7, CC20-4, CH07-4, CH09-4, CH14-4, CH26-7, CH27-4, CH27-8. Beside R-1361 (a lost event) and R-1186 (the silent off-site skip); not the same gaps. **Ruled 2026-11-11 13:17: yes (`09` §3 decision 299). Not built.** | NARROWED — **2026-11-15: LIVE** (hub 0.182.0, agent 0.175.1 vouched). Seen on the running hub: the daily-check ledger has its first records, the lost-mail scan ran at the start („none”), the „Security profiles” cell is filled for the three test boxes, the „Kernel clean-up” cell shows the N100's night. **Tests only, not seen on a box:** a refused signed job told, a guest-power give-up told, a lost operator mail told, a skipped daily check told. Earlier: NARROWED — **2026-11-14 (night build, second part):** the two things release 2a did not tell are built, not released: the System page has a cell for the kernel clean-up (removed, kept, space gained) and one for the security-profile refresh (the kernel, how many profiles changed, any failed service it restarted) — `11` §5.11.1, §5.12. On the way a display defect was fixed: a clean-up hid a kernel that fell back the night before in the „Kernel step” cell. NARROWED — the four worst cases are built, not released. **2026-11-14 (night build):** the operator is told when a hub daily check's slot passed while the hub was down, when an operator mail was never sent, when a box did not take a signed job in two hours, when a box refused a signed job (with the cause), and when the guest-power watchdog gave up (`05` §16.6, `08-alarm-ladder.md`). Tests only; not deployed, not seen on a box. LEFT: the other 15 answers of the class; a household mail is still never retried (R-1361); the kernel clean-up and profile-refresh detail (next part of release 3). OPEN — **2026-11-14 (release 2a), two more things the hub does not tell:** (1) a kernel clean-up that removed kernels shows only as „cleaned <time ago>” in the System page's „Kernel step” cell — what was removed, kept and gained is stored and shown nowhere; (2) the security-profile refresh sends nothing to the hub at all, also when it restarted a failed service (it did on the N100). Both for release 3. Earlier: OPEN — filed 2026-11-11 (clock list) | — | Fix shape (ruled, not built): one hub alarm for the four worst cases (agent: watchdog give-up and refused job as events; hub: a start-up check „did my daily jobs run”, and the mail retry kept across a restart). | CC |
|
||||
| **R-1396** | Monitoring & notifications | P3 | **The agent now names WHY its trust in Proxmox is wrong, and the hub does not tell the operator yet.** Found 2026-11-14 night (release 2b, built). The agent's host report carries a `proxmox_trust` stanza (`mode`, `problem`, `detail`, the CA copy's end date; `03-host-agent.md` §12a). Two gaps: (1) the hub does not read the stanza — a box whose CA copy does not verify, ends within 30 days, or whose move failed is said only in the box's journal; (2) a box that is fully blind (neither the pinned certificate nor the CA copy works) sends NO host report, because the report starts with a call to Proxmox — that case reaches the operator only as „host stale” after 45 minutes, with no cause. With release 2b a pinned box heals itself at the first failed call, so (2) needs both ways to fail at once. | NARROWED — **2026-11-15: gap (1) is LIVE and was seen from a real event** (hub 0.182.0): Tester 1 reported `ca_copy_unavailable` for the minutes between its agent update and its root-files update; the hub mailed the operator only, named the cause, and said „no problem any more” at the next report. That alarm was FALSE (the pin worked) and agent 0.175.1 no longer raises it. **LEFT: gap (2), the fully blind box** — a box whose trust does not work sends no report, so a staged wrong CA copy can raise no alarm (it also repairs itself at the agent's start, seen on demo-hp). Earlier: NARROWED — **2026-11-14 night: gap (1) is BUILT, not deployed** — the hub reads `proxmox_trust` and raises one operator-only `proxmox_trust_problem` per (box, cause), and `proxmox_trust_ok` at the recovery (hub `main` after v0.181.0; the wire-contract gate asked for the receiver in the same push as the sender). **LEFT: gap (2), the fully blind box.** Earlier: OPEN — filed 2026-11-14 | — | hub: an operator-only event from `proxmox_trust.problem` (raise once per cause, clear when it is empty), and the mode on the System page; agent: send a report without the Proxmox part when the failure is one of trust (a design choice: what the hub does with a report that has no guests) | CC |
|
||||
| **R-1397** | Monitoring & notifications | P4 | **One call of the agent to Proxmox is answered 500 during a fresh install, and the agent logs no ERROR line.** Seen 2026-11-15 on the fresh test box (golden 0.353.0, agent 0.175.1): Proxmox's own access log holds `PUT /api2/json/pools/felhom` → 500 at day-0, between 102 calls answered 200; the install ended „SUCCESS”, the guest is in the pool's box and one app installed; the agent's journal has 0 ERROR lines. Not read: which call it is in the agent, whether it is retried, and whether the same line was there on earlier installs (`documentation/tests/golden-0.353.0-2026-11-15/fresh-install/`). | OPEN — filed 2026-11-15 | — | read the pool call in the agent's day-0 path: is the 500 an expected „already a member” answer, and is it logged | CC |
|
||||
| **R-1396** | Monitoring & notifications | P3 | **The agent now names WHY its trust in Proxmox is wrong, and the hub does not tell the operator yet.** Found 2026-11-14 night (release 2b, built). The agent's host report carries a `proxmox_trust` stanza (`mode`, `problem`, `detail`, the CA copy's end date; `03-host-agent.md` §12a). Two gaps: (1) the hub does not read the stanza — a box whose CA copy does not verify, ends within 30 days, or whose move failed is said only in the box's journal; (2) a box that is fully blind (neither the pinned certificate nor the CA copy works) sends NO host report, because the report starts with a call to Proxmox — that case reaches the operator only as „host stale” after 45 minutes, with no cause. With release 2b a pinned box heals itself at the first failed call, so (2) needs both ways to fail at once. | NARROWED — **2026-11-15 (build of release 4): gap (2) has a design, not built** (`03-host-agent.md` §12a item 8): a short report with the cause, sent only to a hub that says it understands it; the hub skips every reader but last-seen, the clock, the trust check and one new alarm. Not built because it changes what a report means for the hub: every reader of a host report in the hub must be listed first. The test that settles it: `pveproxy` stopped for 20 minutes on demo-hp. Gap (1) is live since hub 0.182.0. Earlier: NARROWED — **2026-11-15: gap (1) is LIVE and was seen from a real event** (hub 0.182.0): Tester 1 reported `ca_copy_unavailable` for the minutes between its agent update and its root-files update; the hub mailed the operator only, named the cause, and said „no problem any more” at the next report. That alarm was FALSE (the pin worked) and agent 0.175.1 no longer raises it. **LEFT: gap (2), the fully blind box** — a box whose trust does not work sends no report, so a staged wrong CA copy can raise no alarm (it also repairs itself at the agent's start, seen on demo-hp). Earlier: NARROWED — **2026-11-14 night: gap (1) is BUILT, not deployed** — the hub reads `proxmox_trust` and raises one operator-only `proxmox_trust_problem` per (box, cause), and `proxmox_trust_ok` at the recovery (hub `main` after v0.181.0; the wire-contract gate asked for the receiver in the same push as the sender). **LEFT: gap (2), the fully blind box.** Earlier: OPEN — filed 2026-11-14 | — | hub: an operator-only event from `proxmox_trust.problem` (raise once per cause, clear when it is empty), and the mode on the System page; agent: send a report without the Proxmox part when the failure is one of trust (a design choice: what the hub does with a report that has no guests) | CC |
|
||||
| **R-1377** | Monitoring & notifications | P4 | **Two endings tell nobody outside the page.** Found 2026-11-10 (the endings list, `documentation/audits/endings-list-2026-11-10/TABLE.md` endings EC03, EC15; read in source). **Orphan delete** of an app sends the hub a fresh report and no 'app removed' event (`internal/api/router.go:1150-1178`); the normal remove sends one. **Wipe of a drive** sends no event to the hub (`internal/web/storage_handlers.go:911-1000`). Not a member: retiring a drive — the hub does not read that field by ruling (decision 130, closed R-888). **Members (answers marked N):** EC03-6, EC15-6. | OPEN — filed 2026-11-10 (endings list) | — | Controller: send the 'app removed' event from orphan delete; decide in `08-alarm-ladder.md` whether a wipe is an operator event. | CC |
|
||||
|
||||
## Hub & operator — 18 rows (P2 1, P3 5, P4 12)
|
||||
@@ -355,7 +356,7 @@ stopping line that lies.
|
||||
| **R-1345** | Hub & operator | P4 | **An access token's scopes cannot be changed after it is made — widening or narrowing one means a new token (and a new secret).** The operator, 2026-10-29: to give CC `hosts:read` + `hosts:write` for the live proofs he had to make `CC_HOSTS` (now in `sec`) beside `cc-releases-2`. Wanted: edit a token's scopes in the session (an audit line per change), so a scope can also be taken away after a session without retiring the secret. | OPEN | — | design + build the scope edit (session only), red-first test that an unticked scope is refused at once | CC |
|
||||
| **R-1353** | Hub & operator | P4 | **Statements still over 1 s, named by the new slow-statement line (hub 0.178.0) in its first hour:** a background deadline/restore-test check reading days of full host-report JSON (`GetHostReportsSince`, `store.go`; 1.5–9.2 s cold, from `monitor/deadline.go` and `monitor/restoretest.go` — no page waits on it); the start-up prune of `events` and `app_log_issues` (1.1 s and 1.8 s; no index on `created_at` / `last_seen`); the customer page's newest-report read (`GetCustomer`, 1.3 s cold in the pod probe). With the 1 GiB limit most of this should come from the cache once warm. Evidence: the hub log 2026-10-30 09:22–10:05 UTC; `audits/release-2026-10-30/p2-r1346/`. | OPEN **2026-11-02 read (`audits/security-2026-11-02/part4/hub-slow-lines-2026-11-01-02.txt`; the log covers only the 31 h since DooPlex restarted on 2026-11-01 16:11 CET, the lines from 10-30 are gone with the old pod):** 35 lines, 15 statements. What repeats: `VACUUM INTO` 5× (avg 110 s, the 6-hourly snapshot, expected); `GetHostReportsSince` 9× (avg 7.9 s, max 26.6 s); `GetCustomer`'s newest report 3× (1.1 s). Once, at the cold start: the prune of `events` (10.4 s) and `app_log_issues` (21 s, again 04:30), the OS-release and host lists (2–22 s). No fix before the full week (11-06). **2026-11-10 read (the hub's start after a deploy, `audits/release-space-fixes-2026-11-10/hub/10-watch.txt`):** 11 slow lines in the first 2 minutes of the new pod, the longest 19.1 s (`GetHostReportsSince`), then the OS-report reads (3–4 s) and the two prunes (2.7 s, 4.2 s); none in the 28 minutes after. The 13:02 UTC snapshot's `VACUUM INTO` took 127.8 s. The same statements as the 11-02 read; no new one. | — | read a week of slow-statement lines; index or narrow what still repeats (the history read needs only a few fields, not the whole JSON) | CC |
|
||||
| **R-1375** | Hub & operator | P2 | **The outside part of three endings is done by hand or not at all — the worst: an off-site account can stay at the provider with no record in the hub.** Found 2026-11-10 (the endings list, `documentation/audits/endings-list-2026-11-10/TABLE.md` endings EH06, EH01, EA21 and the ending "a tester ends"; read in source and documents; no account was called). (1) **Unticking the off-site tier** of a household takes nothing down and leaves no reminder (`hub/internal/web/configs.go:1737-1743`). A later RESET takes the account down only when the tier is ticked (`hub/internal/web/customer_reset.go:203-245`), so the sub-account and its data stay, are paid for, and the hub holds no record that they exist. (2) **Switching the second off-site tier off** takes nothing down: storage entry, token and copies stay; the source calls the teardown 'a deliberate future op' (agent `internal/pbsdr/manager.go:274`). (3) **A tester ends**: no handler and no runbook; done by hand once (2026-09-25); no list says what to collect. **Members (answers marked N):** EH06-4, EH01-4, EA21-4, and 'a tester ends' in the table's head. Related: R-810 (a household leaves), R-32. | NARROWED — **2026-11-15: part 1 is LIVE** (hub 0.182.0). The record of an off-site account now outlives an untick. **Tests only:** the provider path (no call to the provider was made today; no household was unticked). The operator's one-time label check at the provider is still to do. Earlier: NARROWED — part 1 (D71) is built, not released. **2026-11-14 (night build):** the hub keeps the record of an off-site account after the tier is unticked; RESET and delete take the account down when a record exists; an untick alone takes nothing down (pinned by a test); the config form says that the account still exists (`05` §14.1). The runbook „a household or a tester leaves” is written (D74, `runbooks/household-leaves.md`). **For the operator, once, after the release:** at the provider's page read each sub-account's label `felhom-customer=<id>`; for a household whose tier is unticked in the hub, tick it again and save — the account's record comes back. LEFT: part (2) has no fault (the second tier keeps its record, read in source and its test); part (3) is the runbook; a household mail at leaving stays R-810. OPEN — filed 2026-11-10 (endings list) **2026-11-10 15:19 — RULED (D71 = yes, D74 = yes; `09` §3 decisions 291, 294).** Not built. | — | Hub (D71): keep the account record after an untick; RESET and delete take the account down, ticked or not. Docs (D74): the runbook 'a household or a tester leaves', from the five code doors, in a later documents-only session. Parts (2) and (3) of this row have no ruling of their own. | CC |
|
||||
| **R-1376** | Hub & operator | P3 | **Records of a thing that is gone stay in six places.** Found 2026-11-10 (the endings list, `documentation/audits/endings-list-2026-11-10/TABLE.md` endings EH00, EH02, EH21, EA00, EA11, EA27; read in source, `documentation/audits/endings-list-2026-11-10/evidence/hub-delete-statements.txt`; no hub database was read). (1) **Hub:** thirteen tables have no delete statement anywhere. Deleting a box leaves its update settings, its update reports and its kernel notices; deleting a household leaves its off-site key rows, off-site window rows and abandon requests. Most are small; the update reports of each box grow with time. (2) **Host uninstall** leaves the mount units and host mounts of household drives (said when R-179 closed; no open row carried it). (3) **A drive wiped by a signed job** keeps a record and a mount unit that name the old filesystem (agent `internal/signedjobs/wipe.go:61-110`). (4) **The token of a destroyed guest** stays valid until a new guest takes its number: the token store has no remove (agent `internal/localapi/tokenstore.go:127-210`). **Members (answers marked N):** EH00-4, EH02-4, EH21-4, EA00-4, EA11-4, EA27-4. | NARROWED — **2026-11-15: part 1 is LIVE** (hub 0.182.0). The first sweep at the start deleted 26 rows (old update reports of 13 boxes deleted earlier), the same count as the preview on a copy; the ids are kept off git. A box delete by the operator at 11:29 ran with the new code. **One thing the sweep does not cover:** the hub's own alarm marks of a box deleted BEFORE the release (4 marks of one such box were read today) — a delete now removes them, the sweep of old ones does not. Small; to add to the sweep. Earlier: NARROWED — part 1 (the hub, D73) is built, not released. **2026-11-14 (night build):** deleting a box removes its update settings, update reports, kernel notices and the hub's alarm marks that name it; deleting a household removes its off-site key, window and abandon rows; the operator's action log of a deleted household goes one year after the deletion with the other audit rows (decided by CC unattended — the operator may reverse); the delete journal stays; a daily sweep removes what earlier deletes left (`05` §14.2). The privacy sentence is proposed in the report, not published. LEFT: the agent part (a destroyed guest's token), parts (2) and (3), and an age limit for a LIVE box's update reports (needs a design: the kernel lane reads old reports). OPEN — filed 2026-11-10 (endings list) **2026-11-10 15:19 — RULED (D73 = yes, with one exception; `09` §3 decision 293).** Not built. | — | Hub (D73): add the tables with no delete to the two purges and to the daily clean-up; the delete journal (`host_deletions`, `customer_resets`) stays on purpose, and the privacy text says so. Agent: remove a guest's token when the guest is destroyed. Parts (2) and (3) have no ruling of their own. | CC |
|
||||
| **R-1376** | Hub & operator | P3 | **Records of a thing that is gone stay in six places.** Found 2026-11-10 (the endings list, `documentation/audits/endings-list-2026-11-10/TABLE.md` endings EH00, EH02, EH21, EA00, EA11, EA27; read in source, `documentation/audits/endings-list-2026-11-10/evidence/hub-delete-statements.txt`; no hub database was read). (1) **Hub:** thirteen tables have no delete statement anywhere. Deleting a box leaves its update settings, its update reports and its kernel notices; deleting a household leaves its off-site key rows, off-site window rows and abandon requests. Most are small; the update reports of each box grow with time. (2) **Host uninstall** leaves the mount units and host mounts of household drives (said when R-179 closed; no open row carried it). (3) **A drive wiped by a signed job** keeps a record and a mount unit that name the old filesystem (agent `internal/signedjobs/wipe.go:61-110`). (4) **The token of a destroyed guest** stays valid until a new guest takes its number: the token store has no remove (agent `internal/localapi/tokenstore.go:127-210`). **Members (answers marked N):** EH00-4, EH02-4, EH21-4, EA00-4, EA11-4, EA27-4. | NARROWED — **2026-11-15: two more hub marks are not removed at a household's delete** — `offsite_snapshot_listing:<household>` and `offsite_window_grant:<household>` in `hub_settings` (found while building D72; the same shape as the alarm marks). To add to the delete and to the sweep. Earlier: NARROWED — **2026-11-15: part 1 is LIVE** (hub 0.182.0). The first sweep at the start deleted 26 rows (old update reports of 13 boxes deleted earlier), the same count as the preview on a copy; the ids are kept off git. A box delete by the operator at 11:29 ran with the new code. **One thing the sweep does not cover:** the hub's own alarm marks of a box deleted BEFORE the release (4 marks of one such box were read today) — a delete now removes them, the sweep of old ones does not. Small; to add to the sweep. Earlier: NARROWED — part 1 (the hub, D73) is built, not released. **2026-11-14 (night build):** deleting a box removes its update settings, update reports, kernel notices and the hub's alarm marks that name it; deleting a household removes its off-site key, window and abandon rows; the operator's action log of a deleted household goes one year after the deletion with the other audit rows (decided by CC unattended — the operator may reverse); the delete journal stays; a daily sweep removes what earlier deletes left (`05` §14.2). The privacy sentence is proposed in the report, not published. LEFT: the agent part (a destroyed guest's token), parts (2) and (3), and an age limit for a LIVE box's update reports (needs a design: the kernel lane reads old reports). OPEN — filed 2026-11-10 (endings list) **2026-11-10 15:19 — RULED (D73 = yes, with one exception; `09` §3 decision 293).** Not built. | — | Hub (D73): add the tables with no delete to the two purges and to the daily clean-up; the delete journal (`host_deletions`, `customer_resets`) stays on purpose, and the privacy text says so. Agent: remove a guest's token when the guest is destroyed. Parts (2) and (3) have no ruling of their own. | CC |
|
||||
| **R-1386** | Hub & operator | P3 | **Timed jobs with no time limit and no measured duration (25 answers).** Found 2026-11-11 (the Clock list, class W4, `documentation/audits/clock-list-2026-11-11/TABLE.md`; read in source; the hub was not measured, by ruling). The hub's 60-second sweep runs its checks one after the other with no limit for each: one slow check delays all the others, the liveness check too (CH19-3, CH19-8, CH01-3, CH08-3, CH08-8, CH10-3, CH13-8, CH18-3, CH06-8, CH02-3); the 07:10 audit has 10 minutes, measured with three boxes only (CH11-3, CH11-8). On the box: the interval jobs have no limit of their own (CC11-3, CC12-3, CC13-3, CC14-3, CC15-3, CC16-3, CC20-3, CA06-3, CA10-3, CA10-8, CA13-8, CA15-3, CA19-3). Every measured duration is from a small test store. | OPEN — filed 2026-11-11 (clock list) | — | Hub: log each sweep step's duration and alarm when one sweep takes longer than its interval; then read a week of numbers and set limits. Box: the same for the controller's interval jobs. | CC |
|
||||
| **R-1393** | Hub & operator | P4 | **For about 8 minutes after a hub restart its database statements take 1 to 32 seconds; the System page took 12.7 s and a box's enrolment 11.4 s.** Measured 2026-11-14 at the 0.181.0 deploy (`audits/release-1-dates-2026-11-14/hub/05-watch.txt`): 24 `slow statement` lines from 09:58 to 10:06 UTC, none in the 20 minutes after. The database file is 678 MB; the slow ones read `host_reports`, `os_reports` and `events` (whole report JSON per row). One 32-second statement ran while CC copied the database out of the pod for a read (CC's own load). No report was lost that CC could see; not measured: whether a box's report timed out in that window. | OPEN — filed 2026-11-14 | — | measure a restart with no copy running; then decide: an index or a shorter keep on `host_reports`/`os_reports`, or accept | CC |
|
||||
|
||||
|
||||
@@ -5,6 +5,10 @@ Moved here byte for byte on 2026-10-14 (night session), newest first, so that `S
|
||||
|
||||
**Updated 2026-10-13 (night): demo-hp, demo-felhom and Tester 1 run agent 0.155.0; demo-felhom runs controller 0.310.0, the other two 0.309.0 until the floor is raised. The open-items list is at 127. Reports: `REPORT-poweroff.md`, `REPORT-plugmeter.md`, `REPORT-usenet-2026-10-12.md`, `REPORT-newapps-2026-10-12.md`, `REPORT-disk-evening-2026-10-12.md`, `REPORT-answers-2026-10-12.md`, `REPORT-m3-2026-10-11.md`, `REPORT-redesign-2026-10-10.md`, `REPORT-testers-2026-10-10.md`, `REPORT-register-shrink-2026-10-10.md`, `REPORT-new-apps-2026-10-10.md`, `REPORT-release-2026-10-10.md`, `REPORT-break-the-circle-2026-10-09.md`, `REPORT-dooplex-survival-2026-10-09.md`, `REPORT-day4-2026-10-09.md`.**
|
||||
|
||||
## Moved from STATUS on 2026-11-15 (evening)
|
||||
|
||||
**Updated 2026-11-15 (midday).** Releases 2b and 3 are out: hub 0.182.0, agent 0.175.1 (vouched), controller 0.353.0 on every box, golden 0.353.0 (vouched), installer 1.37.0 (published). A box now trusts Proxmox through its own root certificate, and the hub tells you about a wrong box clock and other silent problems (`REPORT-release-2b-3-2026-11-15.md`).
|
||||
|
||||
## Moved from STATUS on 2026-11-15 (midday)
|
||||
|
||||
**Updated 2026-11-15 (morning).** The N100 removed 6 of its 8 old kernels by itself at night and is healthy: 1 of the 2 nights D82 asks for; demo-hp had nothing to remove (0 of 2). Releases 2b and 3 are built and tested in source; nothing is released (`REPORT-night-build-2026-11-14.md`).
|
||||
|
||||
Reference in new issue
Block a user