From b40464cb813e80ab1183f2856058ea9e6f689fd2 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Sun, 15 Nov 2026 17:42:17 +0100 Subject: [PATCH] =?UTF-8?q?release=204,=20second=20build=20(2026-11-15=20e?= =?UTF-8?q?vening):=20report,=20register=20(R-1403,=20R-1404,=20R-1405=20f?= =?UTF-8?q?iled),=20status=20(D88,=20D89),=20context;=2005=20=C2=A715.1=20?= =?UTF-8?q?lists=20the=20new=20notice?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit No box changed, nothing released. Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS --- CONTEXT.md | 19 +++ REPORT-build-release-4b-2026-11-15.md | 140 ++++++++++++++++++ STATUS.md | 6 +- .../architecture/05-hub-architecture.md | 3 +- documentation/backlog/OPEN-ITEMS.md | 11 +- documentation/backlog/STATUS-HISTORY.md | 4 + 6 files changed, 176 insertions(+), 7 deletions(-) create mode 100644 REPORT-build-release-4b-2026-11-15.md diff --git a/CONTEXT.md b/CONTEXT.md index 5d8e30dc..95981265 100644 --- a/CONTEXT.md +++ b/CONTEXT.md @@ -16,6 +16,25 @@ > and holds nothing of its own; this file does hold its own content, namely the standing rulings below. +> **2026-11-15 evening (unattended) — release 4, second build; nothing is released.** +> Report: `REPORT-build-release-4b-2026-11-15.md` (it holds one table for ALL of release 4). Rulings: `09` §3 decisions +> 313–316 (D86 remove, D87 keep, the notice lock, the text changes). Heads: `felhom.eu` hub code to `efea8382`, +> controller `10df99b`; the agent and the installer are untouched. What a session must know before it touches this: +> (1) **No notice, no deletion** (`07` §8.2f): the hub's own table `offsite_end_notices` holds „told”; the hub mails +> the household itself from the REPORT path (`api/end_notice.go`, `notify.SendEndNotice`) until the mail service +> accepted it; `offsitekeys.agreeEnded` needs 30 days of absence AND told ≥ 30 days ago; the box's event +> `offsite_end_scheduled` mails nobody any more. „Told” is told AT AN ADDRESS (`told_addr`, a hash): a change of the +> notification address un-tells. Only a plain app slug can be noticed (`store.ValidNoticeApp`). The daily limits count +> failed tries. The three `…ForTest` helpers refuse outside a test binary. (2) **The delete journal** loses its ids at +> the household's year-end, in one transaction (`store.pruneOneDeletedCustomer`): the EMPTY string, only the deleted +> life's rows; a row with no id is skipped. (3) **Small disk:** the mark is `os_alarm:small_disk::` +> (`store.NoteSmallDisk`), so a box delete removes it. (4) **Working practice, earned tonight:** a helper and the main +> session share one git index — never the same file at the same time; a mutation run rewrites whole files, so it runs +> in a private copy when anybody else edits the tree (commit `c3fa43a4` took a helper's half-done hunk and did not +> build on the server until the next push). Lists for the release: `audits/build-release-4b-2026-11-15/E/` (the proof +> of the deletion — D88; the small-disk flag and the public image) and `F/` (every reader of a host report). +> Open decisions: D88, D89. Rows opened: R-1403, R-1404, R-1405. + > **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). diff --git a/REPORT-build-release-4b-2026-11-15.md b/REPORT-build-release-4b-2026-11-15.md new file mode 100644 index 00000000..55c32807 --- /dev/null +++ b/REPORT-build-release-4b-2026-11-15.md @@ -0,0 +1,140 @@ +# Release 4, second build — „no notice, no deletion”, the texts, the journal id — 2026-11-15 evening, 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). 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. The live hub's database was not read and +not changed. Provisioned nothing. + +Follows `REPORT-build-release-4-2026-11-15.md`. The operator's start line: „D86 remove. D87 keep. Notice lock yes. +Text changes yes.” — all four words given, so nothing here is built without a ruling. + +## 1. What is ready to release — all of release 4, both builds + +| Part | Repo and commit | Proof it still needs on a box | Who must say yes | +|---|---|---|---| +| **The off-site copies of a removed app end after 30 days — and only 30 days after the hub's own notice** | hub: `felhom.eu` `0a53315b` (code to `efea8382`); controller `10df99b` | See `documentation/audits/build-release-4b-2026-11-15/E/proving-the-deletion-on-a-test-store.md`. On the release day, on the scratch guest: press, read the mail in the test inbox (subject, day, the „if this was not you” line), take it back, press again, change the address once and see the notice come again. The removal itself: by time (D88) or by hand. **Release the hub first.** | The operator: the hub deploy; the texts (§2); D88 | +| **The installer stops below 200 GB** | `felhom.eu` `92853bed`, installer 1.38.0, **not tagged** | `…/E/small-disk-flag-on-the-public-image.md`: a 200G VM installs with no flag; a 64G VM stops at `--preflight-only` and changes nothing; one install with the flag | The operator (a tag publishes). R-1398: a refused machine on the public image repeats the refusal on its screen, and the bind page cannot pass the flag | +| **The hub shows boxes accepted on a small disk** | `felhom.eu` `c3fa43a4` | After the deploy and one install with the flag: the box's page shows „System disk: small — accepted below 200 GB” | The operator: the hub deploy | +| **The hub reads its own five names' end dates** | `felhom.eu` `c72ecf52` | After the deploy: the start line names five names; next day 06:40 one line per name | The operator: the deploy and **the five names in the manifest setting** (`08` §12.3) | +| **The delete journal drops the id after one year** | `felhom.eu` `0fa1fe56` | None possible before 2027-09-25 (the first household's year). After the deploy: the daily prune's log line has no error | The operator: the hub deploy | + +All hub parts ride one hub release. The controller part needs the hub first. The installer is alone. + +## 2. Every household-facing text of release 4 as it now stands + +Date form in every place: Hungarian `2026. 12. 15.`, English `2026-12-15`. The mail's day is the hub's (the day of +the mail plus 30); the page's day is the box's. They can differ by a day, and by more when the mail waited. + +| Where | Hungarian | English | | +|---|---|---|---| +| Mail, subject | „[Felhom] {app}: a távoli másolatok törlésének napja: {dátum}” | "[Felhom] {app}: the off-site copies will be deleted on {date}" | **CHANGED** | +| Mail, headline | „{app}: a távoli másolatok törlésre kijelölve” | "{app}: the off-site copies are marked for deletion" | | +| Mail, message line | „{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." | the day is now the hub's | +| Mail, own paragraph after it | „Ha ezt nem te kérted, vond vissza a Mentések oldalon, és változtasd meg a jelszavadat.” | "If you did not ask for this, take it back on the Backups page and change your password." | **NEW** | +| Remove dialog, where a day is shown | „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." | | +| Remove dialog, where NO day is shown (only there now) | „Az éjszakai restic pillanatképek nem törölhetők egyenként — a megőrzési szabályok szerint automatikusan elavulnak.” | "The nightly restic snapshots cannot be deleted one by one — they expire automatically under the retention rules." | **CHANGED** (shown in one case only) | +| List line | „Törlésre kijelölve. Törlés napja: {dátum}” | "Marked for deletion. Deleted on: {date}." | | +| Button | „Mégis megtartom” | "Keep it after all" | | +| After the button | „A távoli másolatok megmaradnak.” | "The off-site copies are kept." | | +| Take-back too late | „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." | | +| History line | „A távoli másolatok törölve: {dátum}” | "The off-site copies were deleted on {date}." | | +| Removed app, not marked | „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" | | +| Press 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." | | +| Save failed | „Nem sikerült elmenteni. Próbáld újra.” | "This could not be saved. Try again." | | + +The operator's own lines (English only) are in `07` §8.2f and `08` §6.5: the notice in the household's place, the +line after 3 days, the reasons in a window's answer. The installer's sentences: `16` §14.5. + +## 3. What was built without a ruling + +Nothing as a part. Inside the ruled parts, these are CC's or the helper's choices; each is said in the document as +reversible, and each is one place in the code: + +| Choice | Why | How to reverse | +|---|---|---| +| A change of the notification address un-tells a waiting notice: the address of the day is told again and the 30 days start again | the review's real hole: a stolen login could point the notice at itself and back | `store.SaveNotificationPrefsAs` and the reader's address check (`a6f4aa0b`) | +| A household with no usable address: the operator is told in its place and that starts the 30 days; an address added later is told and the 30 days start again | the brief asked for the first half; the second half follows from the row above | the same commit, and `42ef25c2` | +| A notice that cannot go out: the operator gets one line after 3 days | longer than any mail outage seen; short enough that a wanted deletion lost days, not a month | one number in `hub/internal/api/end_notice.go` | +| At most 5 notices per household a day, counting failed tries; the wait between tries doubles to 24 h | a mail that was accepted and then reported as failed was sent every hour | `b391a232` | +| Only a plain app name (lower-case letters, digits, `-`, `_`) can be noticed, and so deleted this way | a box could put a link-shaped word into the mail's subject | `73a534e7`; all 66 catalog names pass | +| The journal's placeholder is the empty value; only the deleted life's rows lose their ids | a word could be a new household's id; an id used again must keep its new rows | `0fa1fe56` | + +## 4. What stopped at a design + +- **A press with the off-site tier switched off gets no notice until the tier is on** (R-1404). The controller's + report names pending records only with the tier on; closing it changes the report's shape. +- **Two controllers reporting for one household undo each other's notice** (R-1405). Safe for the copies; noisy. +- **A household whose delete never ended** keeps its ids, and no page names it (R-1403). +- **The public image and the small-disk flag** (R-1398): the bind page has no field for it; a refusal loops. +- **A box that cannot reach Proxmox** (R-1396): the list of readers is made; the design is simpler now; not built. + +## 5. Decisions + +| # | Question | CC's pick | The other option | If nothing is decided | +|---|---|---|---|---| +| D88 | Prove the off-site deletion by time, or by hand-dated rows? | By time: the scratch box presses on the release day and is the first box whose copies go, 30 days later | By hand: the removal is seen on the release day, but two rows of the live hub's database are written by hand, and the 30-day clocks are not proven | By time | +| D89 | When the notification address is changed while a deletion waits, one mail to the OLD address too? | Yes: it closes the last way a stolen login deletes copies unseen | No: no new mail, no old address kept; a person who keeps the address changed gets the notice himself | As built: only the address of the day is told | + +## 6. Claims in the prompt that turned out wrong + +1. **„The box names its pending end records in every report” — false as worded.** Only while the off-site tier is on + (`backup/offbox.go`, `OffboxStatusForReport`). With the tier off the report has none. Hence R-1404. +2. **„The hub's bind form has an 'extra args' field” — false.** The handler takes the value; the page has no input for + it; the household's own bind sends none. The other two links (the pairing answer, the first-boot unit) are true. +3. **„The hub can mail a household from the report path” — true** (the kernel notice is the precedent). +4. **„The hub keeps its sent-mail log for more than 30 days” — true today, and not a promise:** the only delete is for + deleted households. „Told” is kept in the hub's own table; the log feeds only the limits. +5. **`05` §14.3's design, built to the letter, had two defects** (found by reading it against bad cases before the + build): a word as the placeholder would let the daily run take a new household of that name for a deleted one; + and with no date limit an id used again would lose the journal rows of its new life. + +## 7. Per part + +Baselines at the start (15:48 CET): `felhom.eu` `2abfdd9` on the server, controller `c5acb91`, agent `3411592` +(untouched), catalog `b605815`. Evidence: `documentation/audits/build-release-4b-2026-11-15/{A,B,C,D,E,F}/`. + +| Part | Commits | Tests and red-proofs | Documents read | Not proven | +|---|---|---|---|---| +| 0 — rulings | `b07e4af0` | — | `09` §3 | — | +| A — the notice lock, built by a helper | `42ef25c2`, `c9d67309`, docs `b8a48f70` | store 4, agreement 2 (one of 12 rows), api 14, notify 8 tests; 39 mutations seen red (2 redone) | `07` §8.2f; `08` §6.5, §8.1; `05` (headings); R-1361, R-1383 | no box, no inbox, no store; two boxes of one household; a hub restart in the middle of a walk | +| A — after the independent review | `73a534e7`, `508f936a`, `b391a232`, `cbfeeb62`, `a6f4aa0b`, `efea8382`, docs `0a53315b` | each finding first as a test seen red (12 mails in 12 hours; a subject with a link-shaped word; „told” after an address change); 14 more mutations seen red | the same | the address change was driven through the hub's own endpoint in tests, not from a controller | +| B — the texts | hub `9ef8cee1`; controller `10df99b` | hub 4, controller 3 mutations seen red; 144 page fixtures patched on the changed lines only | `07` §8.2f's text table; the mail frame and its stored examples; both language files | the dialog in a browser; the mail in an inbox | +| C — the journal id | `0fa1fe56` | `TestD86_*` (5); 15 mutations seen red (1 after the test was made to ask for the staged error) | `05` §14.2, §14.3; every reader of the two journal tables | on a deployed hub; the first real run is 2027-09-25 | +| D — the small-disk mark | `c3fa43a4` | `TestSmallDisk_*` (2), `TestD83_*` (3); 13 mutations seen red (1 redone), run in a private copy of the hub | `16` §14.5; the enrolment handler | on a deployed hub; installer 1.38.0 sends the flag and no size | +| E — two lists | `b8cf6c24`, `7b46dbcc` | — | the bind handler, the pairing answer, the first-boot unit, the Hosts page; the two hub tables of Part A | nothing was run | +| F — the readers of a host report | `b8cf6c24` | — | `handleHostReport` (lines 957–1190) and the eight stored-report readers | the pages' templates field by field | + +**What the independent review of Part A found:** with an honest box, no way to an agreement without an accepted +mail. One real hole: the notice stayed „told” after the notification address was changed. Five smaller: a mail +accepted but reported as failed was sent every hour, outside the daily limit; a link-shaped word in the subject; the +told time was the walk's start, not the send's end; test-only helpers reachable from production code; one guard with +no test. The automatic security review found one more during the build (the operator's notice had no limit). All +fixed, each with a test seen red first. + +## 8. Two mistakes of the main session + +1. **Commit `c3fa43a4` took a half-finished piece of the helper's work.** The helper and the main session shared one + file (`handler.go`) and one git index; the commit was made minutes after the check that the file held only the + main session's change. That commit did not build, and it reached the server (the other session's push carried + it). The next push (`b8a48f70`) repaired it; the head is green. **The operator may have one „build failed” mail + for `c3fa43a4`.** Lesson, kept in the session's practice from that point: a helper and the main session do not + edit the same file at the same time, and mutation runs go to a private copy. +2. **The first commit of the run (`b07e4af0`, rulings only) was made in one command with a gate run**, against the + standing rule; the gate was red at that minute from the other session's work (the sizing data), not from the + commit. Documents only. + +## 9. The register + +251 rows before. **254 after.** Opened 3 (R-1403, R-1404, R-1405). Closed 0. Dated lines: R-1374, R-1376, R-1398, +R-1396. `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. Instruction files changed: none. System poster: no fact changed. + +## 10. Observations + +- A press with the tier off — FILED: R-1404. Two reporters — FILED: R-1405. A delete that never ended — FILED: R-1403. +- The bind page has no field for extra installer arguments — on R-1398, dated line. +- `05` §15.1 („the four mails”) did not list the new notice — FIXED in the close-out commit (one row). +- Sharing one git index between a helper and the main session — the mistake of §8; no row: a practice, not a product + fact. diff --git a/STATUS.md b/STATUS.md index e53b1099..9d99faab 100644 --- a/STATUS.md +++ b/STATUS.md @@ -2,7 +2,7 @@ **Ready for Tester 2? Yes — tell the friend go (`documentation/pilot/TESTER2-handover.md`).** -**Updated 2026-11-15 (late).** Securo (family finances) is in the catalog, all checks passed (`REPORT-securo-onboarding.md`). Release 4 is built in source only (`REPORT-build-release-4-2026-11-15.md`). +**Updated 2026-11-15 (late evening).** Release 4's second build is in source; nothing is released. New: no notice, no deletion; the delete journal drops the id after a year; the hub shows boxes accepted on a small disk (`REPORT-build-release-4b-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 | |---|---|---|---|---|---|---| +| D89 | R-1374 | When a household's notification address is changed while an off-site deletion waits, send one mail to the OLD address too? | **Yes** (it closes the last way a stolen login deletes copies unseen: today only the new address is told) | no: nothing new is mailed and no old address is kept; a person who changes the address and keeps it changed gets the notice himself | as built: only the address of the day is told | — | +| D88 | R-1374 | How do we prove the off-site deletion before households can use it: by time, or by hand-dated rows? | **By time** (the scratch box presses on the release day and is the first box whose copies go, 30 days later; nothing is written by hand) | by hand: the removal is seen on the release day, but two rows of the live hub's database are written by hand, and the 30-day clocks are not proven | by time | the release of Part A | | 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 evening.** Publish the website again (Securo's card): `scripts/publish-site-cloudflare.sh`. 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). +**2026-11-15 evening.** Publish the website again (Securo's card): `scripts/publish-site-cloudflare.sh`. Read `REPORT-build-release-4b-2026-11-15.md` (all of release 4; the texts). **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) diff --git a/documentation/architecture/05-hub-architecture.md b/documentation/architecture/05-hub-architecture.md index f28533d7..deeca06c 100644 --- a/documentation/architecture/05-hub-architecture.md +++ b/documentation/architecture/05-hub-architecture.md @@ -571,13 +571,14 @@ year has not started), and nothing on the System page names it — R-1403. **The section this document did not have.** The hub composes every sentence a household reads before it has seen any box screen, and until v0.118.0 nothing here described that. -### 15.1 The four mails +### 15.1 The mails (four until 2026-11-15; the off-site end notice is the fifth, not released) | Mail | Trigger | Rendered by | Language source | |---|---|---|---| | Event notification (44 event types — the `mail.event.*` keys of `internal/i18n/locales/hu.json`, counted 2026-10-24) | a box event, or a hub checker | `FormatCustomerEmail` | reported → created-with → `hu` | | Claim / reset / re-enroll / claimed | the claim arc | `FormatClaimEmail` | created-with (no box has reported yet) | | Self-bind link | customer creation, or the operator's button | `FormatSelfBindEmail` | created-with | +| The off-site end notice (D84, the notice lock — `07-backup-architecture.md` §8.2f; built, not released, hub `main` after v0.182.0) | **the hub's own state, not an event:** a controller report first names an app in the box's pending end records; sent again at later reports until the mail service has accepted it | `notify.SendEndNotice` (the household frame, with its own subject and no raw details line) | the box's reported language | | The public bind PAGE at `/bind/` | the customer opens the link | one template per language | created-with, **except `expired`** — see 15.4 | The operator's channel (`FormatOperatorEmail`, and the R-182 backup-run digest) is **not** in this diff --git a/documentation/backlog/OPEN-ITEMS.md b/documentation/backlog/OPEN-ITEMS.md index c0c3374b..6fc3c62d 100644 --- a/documentation/backlog/OPEN-ITEMS.md +++ b/documentation/backlog/OPEN-ITEMS.md @@ -219,7 +219,9 @@ 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. | NARROWED — **2026-11-15 evening — RULED: D87 = keep (decision 313); the notice lock = yes (315); the text changes = yes (316).** Fix shape of the lock: the hub mails the household itself, from its own state, when a report first names an app in the box's pending end records, and tries again until its record says „told”; the hub agrees to an app only 30 days after that record, by its own clock, beside the 30 days of absence; no address → the operator is told once and that starts the 30 days; a take-back or an install voids the notice. Earlier: 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-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 evening (second build): the notice lock and the text changes are BUILT, not released** (hub `main` after 0.182.0, controller `main` after 0.353.0; `07` §8.2f). The hub sends the household's notice itself from its own table `offsite_end_notices`, at every report until the mail service has accepted it; the hub agrees to an app only 30 days after that, beside the 30 days of absence; no usable address → the operator is told in its place; a take-back, an install or a new press voids the notice; a notice that cannot go out blocks the deletion and tells the operator after 3 days. An independent review found one real hole and five smaller defects, all fixed with tests seen red: the notice stayed „told” after the notification address was changed (now: told at an address — a change tells the address of the day again and the 30 days start again). **Open, said in §8.2f:** a person who holds the login and keeps the address changed gets the mail himself (D89 asks: one mail to the OLD address at a change); R-1404; R-1405; a rooted box can ignore the take-back. **Nothing ran on a box, in an inbox or against a real store.** How to prove it: `audits/build-release-4b-2026-11-15/E/proving-the-deletion-on-a-test-store.md` (D88). Earlier: NARROWED — **2026-11-15 evening — RULED: D87 = keep (decision 313); the notice lock = yes (315); the text changes = yes (316).** Fix shape of the lock: the hub mails the household itself, from its own state, when a report first names an app in the box's pending end records, and tries again until its record says „told”; the hub agrees to an app only 30 days after that record, by its own clock, beside the 30 days of absence; no address → the operator is told once and that starts the 30 days; a take-back or an install voids the notice. Earlier: 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-1404** | Backup & restore | P3 | **A household that presses „delete backup data” while its off-site tier is switched off gets no notice until the tier is on again.** Found 2026-11-15 (the notice lock, `07` §8.2f, `[DESIGN — proposed, not built]`). The controller names its pending end records in its report only while the off-site tier is ON (`backup/offbox.go`, `OffboxStatusForReport`), so the hub does not learn of the press and mails nobody. Nothing is deleted meanwhile (the safe direction); when the tier is on again the notice goes and the 30 days start then. The household sees a date on its page that the hub does not keep. | OPEN — filed 2026-11-15 | — | the controller reports pending records with the tier off too — a change of the report's shape, so both sides and the wire gate | CC | +| **R-1405** | Backup & restore | P4 | **Two controllers that report for one household undo each other's off-site end notice.** Found 2026-11-15 by the review of the notice lock. A controller's report is taken on the household's one key and stored per household; one household is expected to have one box, and nothing prevents two (a guest that was cloned or restored and kept its config). The notice is then made by one report and voided by the next: up to 5 mails a day to the household, and the deletion it asked for never comes. Safe for the copies. | OPEN — filed 2026-11-15 | — | first: tell the operator when two different controllers report for one household inside one report cycle | 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 | @@ -284,7 +286,7 @@ stopping line that lies. | **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 host in 313 s, and an orderly restart brought 7.0.14-28-pve back in 324 s; the pinned default, `grub.cfg` and the step's state file did not change, and the hub got no kernel report and no alarm (`documentation/audits/kernel-cleanup-spike-2026-11-10/evidence/fallback-boot/`). Still open for the kernel part: a second box; the step built as a program. **2026-11-10 (release run) — part (2) RELEASED, VOUCHED and PROVEN on three test boxes** (agent 0.173.0, vouched by the operator 15:29 UTC; `documentation/audits/release-space-fixes-2026-11-10/agent/`): the folder went 49 → 1, 48 → 1 and 33 → 1 files (about 700 / 690 / 485 MB back) at the commit of THIS update, not at the next one (the earlier sentence here and in the agent's CHANGELOG was wrong, and is corrected there). A rollback after the clean-up worked on Tester 1: a signed update to the older version was crashed once, 9 seconds into the 60-second dwell, and the wrapper put the released version back in the same second; the failed version's file stays until the next good update (by design). The kept older kernel on demo-hp booted to healthy in 313 s and the box went back (`documentation/audits/kernel-cleanup-spike-2026-11-10/evidence/fallback-boot/`). **Still open:** (1) the kernel clean-up as a program (`11-os-updates.md` §5.11.1, not built) and a second box; (3) template archives; (4) the `.bak-*` copies — the release does not reach them; (5) the failed-run logs. A household box gets part (2) at its first good agent update after the vouch. | the kernel part: the hand proof on demo-hp (`documentation/audits/kernel-cleanup-spike-2026-11-10/`), then an agent release | Agent: after a good update keep the running kernel, the one before it and the newest, and remove the rest — ring 0 first; keep the newest N self-update binaries and `.bak` copies; keep one template archive. Each with a test that a kept item is never removed. | CC | | **R-1369** | Box system & updates | P3 | **When a disk is full there is no written way out: no runbook and no self-repair, for the host system disk, the thin pool, the guest disks or a data drive.** Found 2026-11-10 (the space list, `documentation/audits/space-list-2026-11-10/TABLE.md`, question 7). One missing runbook, seen from 21 places; the search of the runbooks folder for a disk-full procedure gave 0 hits (`evidence/searches.txt` S6). The alarms exist (hub: 90 / 95 % host disk, 85 / 90 % thin pool; controller: 85 / 95 % on the data volume and each drive) but they end in a mail, not in a step. For three small places nobody wrote what fails when they are full (EFI partition, host and guest temp folders). **Members (answers marked N):** H1-7, H2-7, H5-7, H9-7, H10-5, H10-7, H12-7, H13-7, H15-5, G1-7, G2-7, G7-7, G12-7, G13-7, G14-7, G17-5, D1-7, D2-7, D3-7, D6-7, D7-7, D8-7, D9-7, D10-7. | OPEN — filed 2026-11-10 (space list) **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. | 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-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 — **2026-11-15 evening (second build): part (2) is BUILT, not released** (hub `main` after 0.182.0): the hub keeps `small_disk` (and a size, when an installer sends one) from the enrolment and the box's page shows „System disk: small — accepted below 200 GB”. **Part (1) is open, and one more thing was read:** the hub's bind form has NO field for extra installer arguments (the handler takes `extra_args`, the page does not offer it; the household's own bind sends none), so `--accept-small-disk` cannot reach an install from the public image today (`audits/build-release-4b-2026-11-15/E/small-disk-flag-on-the-public-image.md`). Earlier: 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 | @@ -333,7 +335,7 @@ stopping line that lies. | **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 (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