drill: a stranger's first hour on 0.242.0 — 1 intervention, not ready for a volunteer

Golden 0.242.0 baked, round-trip verified and vouched (cadence rule, R-468).
Fresh box from the public ISO on demo-hp: landed on the vouched set, two apps
deployed and used, backup, remove, byte-identical restore, power cut and code
typo all PASS. Stopped for a volunteer by R-493 (no instructions) and R-494
(the setup mail's dashboard link has no DNS; intervention I1). R-493..R-500
filed. Capability map: first-hour row added (PARTIAL), journey row scoped.
Stopgap Hungarian volunteer guide written. Hub teardown layer pending.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

STATUS.md

@@ -1,5 +1,39 @@
 # STATUS — what works, what's broken, what's next
 
+**Updated 2026-09-14 (afternoon) — the first-hour drill on a fresh box.**
+
+> **Ready for a volunteer: not yet.** Two things would stop a stranger before their first app: **there
+> are no instructions anywhere telling them where the installer is or what to type**, and **the link
+> in the "your server started" e-mail does not open for a new customer**, because nobody creates its
+> web address automatically. Everything after that point worked.
+
+**What I exercised.** A brand-new machine on the HP, installed from the public installer, connected
+to a new test customer, claimed, two apps installed and used (a family wiki with a Hungarian page and
+an attachment, and an encrypted note), a manual backup, one app removed with its data, the other
+restored after I deleted its page, a power cut, and a mistyped code. The new golden image was built
+first, as the weekly rule says, and the fresh box landed on today's release by itself.
+
+**What broke.** Nothing lost data: the restore brought the deleted page back byte for byte, and the
+power cut brought every app back on the same version with no false alarm. What a stranger would trip
+on: no instructions (I wrote a Hungarian draft for you to approve); the dashboard address; the
+installer refusing its own default machine name; the box's screen first telling people, in English, to
+open the admin page they must never use; the five-word passphrase that no e-mail ever delivers; one
+backup page wrongly saying "already covered, nothing to do"; app pages saying "open wiki.DOMAIN"
+literally; and the dashboard showing the backup two hours off from the backup page. I reached the
+dashboard once in a way a volunteer could not — that is the single intervention. I fixed nothing; this
+run only records.
+
+**Rows.** Opened 8, closed 0. Register table rows: 200 before, 208 after.
+
+**Needs you.** (1) **Decide how a new customer reaches their dashboard**: the hub creates the web
+address automatically, or the box offers a home-network address that works with no setup. **If you do
+nothing:** every volunteer needs you to create their address by hand before they can log in.
+(2) **Read and approve the Hungarian volunteer instructions**, and choose how they are sent. **If you
+do nothing:** there is nothing to send a volunteer. (3) **Hand the five-word passphrase to each
+volunteer yourself** until an e-mail does it. **If you do nothing:** they cannot connect their box.
+
+---
+
 **Updated 2026-09-14 (morning note, the second night) — the scratch guest is built, one controller release, the rotation restarted.**
 
 **Decisions I took.** (1) The scratch guest on the HP was built as you ruled: a second guest under