Problem
The Scans page still uses alert() for delete and clear-history failure paths. This is inconsistent with the app toast/modal patterns and is harder to test/accessibly style.
Expected behavior
Failure feedback should use the existing ToastContext or an accessible in-app error state instead of browser alerts.
Acceptance criteria
- Replace
alert() calls in Scans destructive-action failure paths.
- Keep the existing console logging for diagnostics if useful.
- Add or update tests for one delete failure and one clear/bulk failure path.
Problem
The Scans page still uses
alert()for delete and clear-history failure paths. This is inconsistent with the app toast/modal patterns and is harder to test/accessibly style.Expected behavior
Failure feedback should use the existing
ToastContextor an accessible in-app error state instead of browser alerts.Acceptance criteria
alert()calls in Scans destructive-action failure paths.