night build 2026-11-14: the N100's first night kernel removal read (D82: 1 of 2), close-out — report, status, register
gates / gates (push) Successful in 2m8s

Reads only on the N100 and demo-hp; no box changed, nothing released.

Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
admin committed 2026-11-15 06:41:21 +01:00
1 parent 5da5b05192
commit fffbb40ce0
17 files changed
+830 -4

No files matched your search

+5 -2
View File
@@ -2,7 +2,7 @@
**Ready for Tester 2? Yes — tell the friend go (`documentation/pilot/TESTER2-handover.md`).**
**Updated 2026-11-14 (afternoon).** Release 2a is out: agent 0.174.0, vouched. A ring-0 box now removes its old kernels at night, and a box reloads its security profiles after a kernel change. The N100 keeps time again; the product repaired it, with no hand step.
**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`).
## What works
- **The Plex attack did not reach Felhom's secrets** (R-1241).
@@ -32,6 +32,9 @@ 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 |
|---|---|---|---|---|---|---|
| D85 | R-1379 | Should the hub read the end dates of its own five public names each day and warn you 14 days before? | **Yes** (small; the same check that is built for a box's certificate; a hub name that ends takes every box's link down) | no: you keep the five dates in your own list | nobody warns you before a hub name ends | — |
| D84 | R-1374 | When a household removes an app with „delete backup data”, do that app's off-site copies leave outside the weekly deletion cap? | **Yes — their own allowance, only for copies the hub agreed to** (the hub's own 30-day check does the cap's job here; under the cap one big removal stops every clean-up for weeks) | they count: no new rule, but a refused window and your one-shot grant at each large removal | the design stays a design; the off-site copies of removed apps stay for ever | the build of D72 |
| D83 | R-1370 | Below 200 GB of system disk: does the installer refuse, or warn? | **Refuse, with one named flag for you** (a warning on an install that nobody watches is read by nobody; the flag keeps demo-hp possible) | warn: a 128 GB box installs and stops its local copies months later | the installer takes any disk; the 200 GB is only a sentence | the build of D75 |
| 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 +42,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 morning — read:** the N100 removed 6 of its 8 kernels at night, the hub's „Kernel step” cell says „cleaned”, the box is healthy. If not: tell CC (R-1368). **2026-11-14.** Next builds: 2b (trust in Proxmox), „hub tells you”, promises; no new gap list first. Hosts page: delete host `Tester4-46836f` (else it alarms). Say „HSTS now” from 11-15 (R-1050). **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 morning.** 1. Read `REPORT-night-build-2026-11-14.md`, „Ready to release”: hub, agent, controller and installer wait for your yes. If not: nothing reaches a box. 2. Say „HSTS now” (R-1050). 3. Hosts page: delete host `Tester4-46836f` (else it alarms). 4. The report has a privacy sentence as a proposal; you publish it 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).
**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)