admin
3e2bdda721
gates / gates (push) Successful in 6m46s
Read-back: live sizing-data.json?v=4 byte-equal to the commit; the presets keep their verdicts, Immich alone on 8 GB still tight; only the set without Immich changed. Spike B2 on 9202: POST /api/assets/jobs regenerate-thumbnail rebuilt exactly the 10 broken assets (1.55 s, 5.3 s CPU), 0 of the other 20 photos' 40 files rewritten (control: all rewrote 40 of 40); an empty file maps to its asset by the first 36 characters of its name. Immich removed through the product, no leftovers. Register 134 -> 133 (opened 0, closed 1). STATUS D9/D10 ruled. Claude-Session: https://claude.ai/code/session_012qRErfCoiTkvDK9N5XHbzb
5.3 KiB
5.3 KiB
STATUS — what works, what's broken, what's next
Ready for the first real tester (Tester-2): yes. Tester 2 (a laptop) is off; nothing was sent to it.
Updated 2026-10-14 (day). Agent 0.156.1 + its bundle and controller 0.310.0 on all three boxes; golden 0.310.0. Open items: see documentation/backlog/OPEN-ITEMS.md. Older notes, day by day:
documentation/backlog/STATUS-HISTORY.md. Reports: REPORT-power-cut-fixes-2026-10-14.md, REPORT-night-power-2026-10-13.md, REPORT-poweroff.md.
What works
- A power cut in the middle of a backup no longer blocks later backups: the box removes the half-written backup at start-up (proven with a real cut on demo-hp, on all three boxes now).
- A household can switch the machine off; the hub holds alarms for 14 days and clears the state by itself (N100).
- A real power cut on demo-hp: it started by itself after all 8 cuts of the night (with the BIOS set), every app back in ~4 min; stale and recovered mails true and paired.
- The machine estimator is public (/gepigeny, /en/sizing), with figures from two machines (N100 and HP t740; raised only, 2026-10-14).
- 62 apps in the catalog, the Usenet and torrent clients included. OS updates, the kernel lane too, run at night.
- The hub is closed again after the 2026-10-12 security review; one box cannot read another's data.
What is broken
- Several root-level weaknesses wait on your four decisions below (R-954, R-971, R-982, R-985).
- DooPlex: a failed disk with its alarms silenced (R-934); CI jobs still get lost (R-887); something sets the shared checkout to „bare" (R-935); a Longhorn volume at 91 %.
- Tester 2 has never made an off-site check (R-862). The scratch box cannot read the drill catalog (R-992).
- After a power cut: Immich keeps photos with empty previews or no original; your ruling „fix only the broken photos" is shown to work (Immich rebuilds single photos) — the build is a later task (R-1007).
What we work on
- The power-cut findings still open (R-1004, R-1005, R-1007, R-1010, R-1012, R-1013) and the Immich repair build (R-1007).
Waiting on you — decide
| # | Row | Question | Pick | The other option costs | If you do nothing | Blocked |
|---|---|---|---|---|---|---|
| D1 | R-954 | Change every box's break-glass root password, since we cannot see if the old key was used? | Yes — about one hour, one box at a time, through the vault | Accept: no work, a password that may have been read stays valid | the old root passwords stay; if they were read, they still open the boxes from the LAN or console | — |
| D2 | R-971 | Should the box refuse a catalog change that asks for dangerous container rights? | Yes — an allow-list on the box (one controller release) | Keep trusting the catalog repo: whoever can push to it reaches every box | a catalog push keeps reaching every box's apps with no check | — |
| D3 | R-985 | „Zero-knowledge": change the wording, or remove the operator's root reach to the key? | Change the wording now; revisit after the first sale | Remove the reach: a design change to break-glass | the promise stays stronger than the product | the website text |
| D4 | R-982 | Root SSH with a password from the LAN? | No — key only; the password stays for the console | Keep it: anyone on the household network can try it | the host keeps accepting root password logins from the LAN | — |
| D5 | R-993 (R-991) | Approve the minimum machine (audits/sizing-2026-10-13/SIZING.md §5: x86-64, 4 cores, 8 GB, 256 GB SSD)? |
Approve | Change it: one edit | no hardware page; a buyer with a Raspberry Pi can still download the installer | the hardware page |
| D6 | R-992 | The scratch box cannot read the private drill catalog: give it a read-only login, or make that copy readable? | A read-only login | Readable copy: the drill catalog becomes public | every new-app test needs hand-staging | new-app tests |
| D7 | R-990, R-989 | Rule yes / no / later on the forum ideas (audits/forum-research-2026-10-12/FELHOM.md §5) and the selfh.st ideas (audits/selfhst-survey-2026-10-12/FELHOM.md §6) |
— | — | nothing changes; the research ages | — |
| D8 | R-206 | Install DooPlex's Docker settings from git (restarts Docker), and prune the build cache weekly: yes or no? | Yes, in a quiet window | — | a rebuild of DooPlex still has the settings in git | — |
Waiting on you — do
- N100 BIOS: read „After Power Loss" (the HP's „Previous State" made it start after 8 of 8 cuts). HP BIOS: „Bypass F1 Prompt on Configuration Changes" → Enable.
- Pull the failed disk Z6A07P2G (R-934; the twin Z6A070XZ is
/mnt/3_hdd). If not: its alarms return on 11 November. - Hub master key into the password manager, then
shred -uthe key file (security review 2026-10-12, in the history). - 12 reused homelab logins to rotate, and the repo-visibility decision (R-925, P1).
- Before the first paying customer: Tandoor permission (R-789); a lawyer for the licence list (R-802) and the terms (R-813); SparkyFitness (R-784 — its author replied on 2026-10-13); print the break-glass sheet (R-923).
- Smaller: pin the first Facebook post (R-917); Tester 2's bootstrap (R-862); look at the uncommitted
deny-list edit inhomelab-manifests/.claude/settings.json; the rest of „Your own tasks" (T6–T19) is in the history, 2026-10-10.