F6 deeper half: poll agent /disks/format/status on the 15s client timeout (slow USB mkfs runs detached) — agentapi.FormatStatus + awaitAgentFormat; then mount+register. Found on the live leg.

This commit is contained in:
2026-07-17 09:41:50 +02:00
parent 0025a3b090
commit 0515d153db
4 changed files with 142 additions and 3 deletions
+7 -1
View File
@@ -19,7 +19,13 @@ Closes two `VALIDATION-n100-baremetal-2026-07-16.md` findings. Green:
is the LAST step (marker-last, Scenario B) and every prior step is idempotent (`AddStoragePath`
dedups) → a crash leaves at most an unregistered orphan, never a broken/duplicate registration.
Red-proof `TestStorageInit_DetachedSurvivesClientDisconnect` (pre-fix: cancelled-ctx chain fails at
mount, NOT registered → FAIL; fixed: detached job registers exactly once).
mount, NOT registered → FAIL; fixed: detached job registers exactly once). **Deeper half (found on
the live leg — a 64 GB USB):** a slow mkfs outruns the agentapi client's 15 s `Timeout`; the agent
runs it DETACHED and records the job, so `runStorageInit` now POLLS the agent's
`GET /disks/format/status` (new `agentapi.Client.FormatStatus`) to the terminal outcome on a client
timeout, then continues to mount+register (the F6 root-cause's "mkfs continues detached; poll the
status"). Test `TestStorageInit_PollsAgentFormatStatusOnTimeout` (timeout→done registers;
timeout→failed surfaces the error, no register).
- **F7 (LOW) — the "Vissza" (Back) anchor on `/storage/init` and `/storage/attach` now routes to
`/storage`** (was `/settings`). The init success link also points to `/storage` (where the new
drive appears). Test `TestStorageWizardBackAnchors_PointToStorage`.