Record independent qualification progress and Fleet browser evidence

docs/SESSION-HANDOVER-20261007.md

@@ -455,8 +455,34 @@ Monitoring gate or deferred connection UX/removal work.
 - Companion retains its dashboard WebView across navigation. Operator was asked
   to use the existing Restart app action, reconnect to Yaya, play a free demo,
   and check for the notification before backgrounding, to rule out a retained
-  page from before the matching UI deployment. No result yet; not a fix claim.
+  page from before the matching UI deployment. Operator subsequently confirmed
+  it still failed after following the guide. Do not request another blind retry.
 - No replacement APK, real payment, phone reset or wallet change performed.
 - IndeeHub agent committed final dispatch fixes as 2bfa84ef: isolated backend
   suite 2,004 passed, zero failed, five ignored. VM-only binary preparation and
   isolated full update/recovery rehearsal are ongoing; no live activation.
+
+
+## Independent workstreams — operator authorized 7 October
+
+- IndeeHub agent owns seven-service update/recovery qualification. Its VM-only
+  executable completed (SHA25614100aa55192b79ede0e9ec37317efd9125065f1336b0084d8f1b6ee37c59490);
+  all seven baseline images imported. Actual RPC rehearsal is underway in an
+  isolated VM. This executable predates the new paid-file fixes and is not a
+  release artifact. Yaya remains unchanged.
+- Companion agent owns no-USB native playback diagnostics and APK57. Code is
+  ready, Android tests/build underway. This is diagnostic, not a claimed fix;
+  physical background acceptance remains failed. See its dedicated investigation.
+- Paid-file agent owns guard fixes18b08720: unresolved on-chain attempts block
+  alternate Cashu/Lightning payment; unsafe legacy spending fails closed. Fresh
+  Fedimint file purchases are temporarily unavailable; cached delivery/recovery
+  remains.62 UI tests and typecheck pass; isolated backend suite is queued.
+  Both nodes' previously purchased20MiB fixtures still reopen with exact hashes,
+  with no new payment or spend-ledger change. See dedicated qualification doc.
+- Root owns Fleet recovery65d265f2: explicit retained-report outage notice,
+  Retry, rejection of old replies and unmount cleanup.21 tests, Vue typecheck
+  and isolated390/1440 Chromium keyboard/layout recovery checks pass. Production
+  combined UI build and deployed acceptance remain.
+- Wrong-window PWA request was inspection only and was withdrawn; no PWA change.
+- Heavy builds are serialized around the constrained host; no live wallet/app
+  shutdown was used to free resources. No OTA/ISO/catalog publication occurred.

docs/fleet-recovery-qualification-20261007.md

@@ -1,6 +1,6 @@
 # Fleet recovery qualification — 7 October 2026
 
-Status: source regression fixes qualified; deployed-browser and distributed
+Status: source regressions and isolated browser checks qualified; deployed-browser and distributed
 transport acceptance remain open. This supplements tasks 8, 10 and 12 without
 claiming that the full Fleet acceptance matrix is complete.
 
@@ -26,7 +26,21 @@ Retry. Other cases cover a missing cache, late status/alert replies, a malformed
 status response, late responses after unmount, real zero versus unavailable
 metrics, report ageing, sorting and selected-node history isolation.
 
-Log: `/tmp/archy-fleet-recovery-tests-final.log`.
+Logs: `/tmp/archy-fleet-recovery-tests-final.log` and
+`/tmp/archy-fleet-recovery-typecheck.log` (Vue typecheck passed).
+
+An isolated real Chromium harness rendered the actual Fleet component and styles
+at 390px and 1440px. Cached cards and failure notice remained visible; keyboard
+focus/Enter on Retry recovered the view; genuine zero remained 0%; no horizontal
+overflow or page errors occurred. RPC was replaced with synthetic replies; all
+non-fixture network requests were blocked. This was source-served component
+qualification, not a deployed artifact or real outage. Initial harness attempts
+failed because its standalone app initialization/import was incomplete; corrected
+before both widths passed. Failed logs retained.
+
+Browser scenario: `/tmp/archy-fleet-recovery-browser.cjs`,
+server: `/tmp/archy-fleet-browser-server.mjs`,
+result: `/tmp/archy-fleet-recovery-browser.log`. The owned server was stopped.
 This is local component/composable evidence, not a live-node outage test.
 No node service, peer relationship, wallet or payment was changed.
 
@@ -36,7 +50,7 @@ No node service, peer relationship, wallet or payment was changed.
 | --- | --- | --- |
 | Report rendering | Local normalization/render tests; earlier dev/Yaya metrics evidence in progress ledger | Updated sender/receiver comparison across supported versions |
 | Status freshness | Clock-driven ageing, unknown versus stale, no synthetic metric zero | Real partition, reconnect and transport delivery |
-| Refresh failures | Visible retained reports; empty failure; Retry recovery | Candidate browser at phone/desktop widths and deployed artifact |
+| Refresh failures | Visible retained reports; empty failure; Retry recovery | Deployed artifact and actual-node outage; isolated 390/1440 browser passed |
 | Concurrent replies | Newest status/alerts win; no unmount cache repopulation | Distributed delay/out-of-order delivery |
 | Selection/sorting | Retained across failure; history request isolation | Larger-fleet navigation and keyboard checks |
 | Authorization | No permission changes in this patch | Unauthorized/expired-trust actual-handler matrix |