lists: the Clock list (70 jobs) and the End-dates list (39 things), 9 register rows, 4 decisions
gates / gates (push) Successful in 2m2s
gates / gates (push) Successful in 2m2s
Read-only review of every job on a timer and of everything that ends on a date, with measurements from the three test boxes. Nothing ends in the next 14 days. Register 236 -> 245 (R-1379..R-1387), pointer lines on twelve rows, D76-D79 in STATUS.md. Part C: felhom-agent's clone address holds no token now; the other clones wait for the operator's yes. R-1035's 4-week check moved to 2026-11-18 (operator read needed). Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
1 parent
43e244ad8f
commit
978666dde3
81 files changed
+26738
-20
No files matched your search
@@ -2,7 +2,7 @@
|
||||
|
||||
**Ready for Tester 2? Yes — tell the friend go (`documentation/pilot/TESTER2-handover.md`).**
|
||||
|
||||
**Updated 2026-11-10 (evening).** Three releases are live: the agent that cleans its own update folder (you vouched it), the controller that sends one warning for one full disk (every box takes it by itself), and the hub that sends the host-disk alarm to you only. You ruled D71–D75 at 15:19 and none is built; the smallest system disk is 200 GB, and what the installer does below 200 GB (refuse, or warn) is open (R-1370). The report of the run is `REPORT-release-space-fixes-2026-11-10.md`.
|
||||
**Updated 2026-11-11 (midday).** Two read-only lists are ready: every job on a timer (70) and everything that ends on a date (39); nothing ends in the next 14 days (`documentation/audits/end-dates-list-2026-11-11/README.md`). The golden passed its 7-day limit on 2026-11-10, so code pushes to `felhom.eu` are refused. Four decisions wait (D76–D79).
|
||||
|
||||
## What works
|
||||
- **The Plex attack did not reach Felhom's secrets** (R-1241).
|
||||
@@ -32,6 +32,10 @@ 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 |
|
||||
|---|---|---|---|---|---|---|
|
||||
| D76 | R-1380 | Shall the agent follow Proxmox's new certificate by itself? | **Yes** (one agent change, long before 2028; no box then depends on a calendar) | a hand step in a runbook and a calendar date for each box, for ever | in July 2028 the N100's agent loses guest control and backups, with no alarm that says why; the other boxes follow | — |
|
||||
| D77 | R-1379 | Shall the product warn you 14 days before an end date (a box's web certificate, a hub token)? | **Yes** (a renewal that fails is silent today) | you keep the dates in a calendar by hand | the list of 2026-11-11 is the only guard | — |
|
||||
| D78 | R-1383 | Shall a timed job that gives up or is skipped tell you (four cases: the guest-power watchdog, a skipped hub daily check, a lost operator mail, a refused signed job)? | **Yes** (small changes in the agent and the hub) | the logs stay the only trace | you learn of a dead guest from the household | — |
|
||||
| D79 | R-1384 | Shall the hub check each box's clock and alarm above one minute of error? | **Yes** (a box with a wrong clock can look healthy and cannot take an agent update) | R-1301 (repair the N100's time service) stays the only guard | the N100 stays 32 s behind, and nobody is told when it gets worse | — |
|
||||
| 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,6 +43,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-11.** 1. Bake and vouch a golden, or write a waiver (R-468). If not: no code push to `felhom.eu`. 2. Read the dates of „Only you can read these dates” (`documentation/audits/end-dates-list-2026-11-11/README.md`, R-1381). If not: a domain or a token can end with no warning. 3. Rotate the Gitea token of login `kisfenyo` into the store as `GITEA_GIT_TOKEN` (R-925); it was printed on 11-10. 4. Yes or no: may CC fix the two other clone addresses (`cc-secrets`, the plug-meter clone)? Only `felhom-agent` is fixed. 5. Search Console read (R-1035, now 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)
|
||||
|
||||
Reference in new issue
Block a user