boards(BRINGUP): the SER5 bench steps for the plug-and-play stick and the real Zuse (#92, Task 5 step 6) [skip ci]

First boot (genesis, growth, the time to the prompt), the second boot, MINT-ZUSE onto a second stick, the system stick alone (the fixed screen), both sticks at power-on -- each rehearsed first in QEMU by the qemu_session.py mode named. 3.2's 'boots headless' corrected: the stick's first boot now mints its Zuse.

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

boards/BRINGUP.md

@@ -156,8 +156,9 @@ One QEMU at a time. Use a copy of the image: the kernel writes to its disk.
       2026-10-27 the PC image is the StarshipOS stick (`docs/v4.0.0/STICK.md` §4: ESP,
       identity, Artemis) and `make -f kernel/Makefile ARCH=amd64 qemu-stick` does exactly
       this: a copy of the stick as a USB stick on the xHCI controller (`bootindex=0`), OVMF
-      booting its ESP, logs under `logs/<TS>/amd64/`. The stick's identity partition is
+      booting its ESP, logs under `logs/<TS>/amd64/`. Since 2026-11-08 (stick increment 5,
-      blank until first-boot genesis (stick increment 5), so today it boots headless.
+      `plans/2026-10-29-stick-5`) its first boot mints the stick's own Zuse and reaches
+      `[zuse@Hera] ok>` with nothing set up; `qemu_session.py stick_genesis` checks it.
 - [ ] **MILKV:** the command in `boards/milkv/README.md` (OpenSBI, U-Boot, `bootefi`).
 - [ ] **RASPI:** there is no QEMU model of the Pi 5, but its native path -- raw image, entry
       at EL2 with the MMU off, devicetree in x0 -- is rehearsed on QEMU virt:
@@ -207,6 +208,28 @@ the one QEMU exercises most closely, and the Pi 5's can be rehearsed only in par
       on until login (screen=boot)"). Secure Boot off. Watch for `Boot disk: a StarshipOS stick`, `Artemis: the stick's partition
       attached`, then `[zuse@Hera] ok>`. The same image boots in QEMU first:
       `make -f kernel/Makefile ARCH=amd64 qemu-stick STICK_PAIR=disk/zuse-scratch`.
+- [ ] **Plug and play, and the real Zuse** (2026-11-10, after the stick's increments 5 and 5a,
+      `docs/v4.0.0/plans/2026-10-29-stick-5-proxy-zuse-and-real-zuse.md`, Task 5 step 6). Two USB
+      sticks: the system stick, written from `make boot_image TARGET=PC` (no `STICK_PAIR`) with
+      `make write_stick DEVICE=/dev/sdX`, and a second stick of 64 MiB or more that may be erased.
+      Each step rehearsed first in QEMU by the session named:
+  - [ ] **First boot** (`stick_genesis`, `stick_grow`): the system stick alone. Watch for
+        `Artemis: grown to fill the stick` (a stick of 8 GB or more) or `Artemis: the stick is
+        under 8 GB -- not grown`, then `Zuse: genesis minted onto attached thumbdrive`, then
+        `[zuse@Hera] ok>`. Nothing typed before it. Write down the time from power-on to the
+        prompt.
+  - [ ] **The second boot of the same stick:** `Zuse: identity confirmed from attached
+        thumbdrive`, no genesis line, no growth line.
+  - [ ] **`MINT-ZUSE`** (`mint_zuse`): type it, plug in the second stick when asked; check the
+        size it names is that stick's; type `YES`. Watch for `Zuse: real Zuse minted onto the
+        second stick`, then `identity confirmed`, then the prompt.
+  - [ ] **The system stick alone** (`fallback`): power off, take the second stick out, boot. The
+        fixed screen's four lines (`Zuse's stick is not here.` ...), no prompt; keys typed there
+        do nothing. Plug the second stick in: the prompt. Pull it: the screen comes back.
+  - [ ] **Both sticks at power-on** (`zuse_stick_first`): her stick in the lower port if the
+        PC's ports are numbered; she is logged in once.
+  - [ ] Not done on the bench unless a spare stick is to hand: `R` and a replacement
+        (`replace`) -- the second stick stops working for good.
 - [ ] The timer lines differ from QEMU's by design: no hypervisor, so the HPET path runs for
       the first time. S1 is the finding to remember if it stops there.