Files

T

gates / gates (push) Successful in 26s

Details

Rulings 61-62 built: calibre-web generated login name, the registry prune rule; R-750/R-752 closed, R-756/R-757 opened; runbook 4.1a; STATUS, report, evidence

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

2026-10-01 13:29:46 +02:00

2.3 KiB

Raw Blame History

STATUS — what works, what's broken, what's next

Ready for the first real tester (Tester-2): yes. You confirmed the tunnel route and the connect mails (2026-09-30).

Updated 2026-10-01 (late afternoon). Both demo boxes run controller 0.285.0 and host agent 0.138.0. Hub 0.126.0. New installs get golden 0.285.0 with agent 0.138.0.

Tester-2 — read only, from the hub. The customer record exists. Tester-2's box has not registered yet.

Your two decisions of this afternoon — built

calibre-web gets a secret login name (your A). The box makes the name at install and shows it on the app page, next to the password. Tested on the scratch box: a stranger tried 40 wrong passwords with admin, and the household still logged in at once with its own name. The lock against guessing stays. The HP demo box's calibre-web has a new name too. It is in your credentials file, under the same key as before.
The registry clean-up script keeps 20 versions and never one in use (your A). "In use" means: the golden, the floor, the approved agent, the running hub. I ran it only in "show me" mode: today it would delete 70 old controller versions and 8 hub versions. It deleted nothing. If it cannot read what is in use, it refuses to run.

What broke, and what I did

A box makes up a value when a template gains a new generated field. On the HP demo box it made up a calibre-web login name that the app never had. I fixed that box by giving the app that name. Written down. No other box has calibre-web today.
On the scratch box, removing calibre-web "with its data" was refused, although the folder is there. Written down.

Rows. This afternoon: 2 closed, 2 opened. The list went from 390 to 392 rows.

What needs you

Nothing urgent. Two questions from earlier stay open, and nothing breaks if you wait: should apps see each visitor's real address (a bigger build), and is the design document or the build right about where the tunnel runs?

Standing steps

Monthly security re-test: last run 2026-10-01, next due ~2026-11-01. (You start it with the standing brief.)
Weekly: the golden bake (around 8 October).
Registry clean-up: only when the registry disk fills; "show me" mode first, then a person decides.