fix: the address and token screens and the address scan no longer log requests a popup reload cancels (closes #475)

The transaction lists on the address and token screens, the address scan
after a wallet is created, and the endpoint checks in Settings now check
the signal the popup aborts on pagehide before reporting a failed request,
as the home screen and the balance refresh already do. scanForAddresses()
takes the signal ahead of its gap limit.

End-to-end tests reload the popup on the address screen with Blockscout
held, and during the address scan with its requests held. Jest tests show
the transaction lists, the scan and the Settings checks report a real
failure and stay silent once the popup has closed. The transaction detail
and confirmation screens are left out: they do not keep the popup context.

Model: opus-5-5

TODO.md

@@ -45,6 +45,18 @@ but the review is broader than any of them.
 
 # Completed Steps
 
+- 2026-10-06: Reloading or closing the popup no longer logs a request it cancels
+  as a failure on the address and token screens, in the address scan after a
+  wallet is created, or in the endpoint checks in Settings
+  ([#475](https://git.eeqj.de/sneak/AutistMask/issues/475)). Each checks the
+  signal the popup aborts on `pagehide`
+  ([#218](https://git.eeqj.de/sneak/AutistMask/issues/218)) before reporting a
+  failure; a real failure is still logged. The e2e suite reloads the popup on
+  the address screen with Blockscout held, and during the address scan with that
+  scan held; jest tests cover the transaction lists, the scan and the Settings
+  checks. The transaction detail and confirmation screens are not covered: they
+  do not keep the popup context that carries the signal.
+
 - 2026-10-06: Reloading or closing the popup mid-refresh no longer logs the
   requests that cancels as failures
   ([#218](https://git.eeqj.de/sneak/AutistMask/issues/218)). Chrome cancels a