Add worker alert and notification tests

docs/progress.md

@@ -50,11 +50,12 @@ Implemented alerting management slice:
 - Existing simple alert conditions are shown in friendly language instead of raw condition data.
 - Worker honors alert rule cooldown before opening a new incident for a recently-triggered rule.
 
-Implemented backend test coverage:
+Implemented monitor and notification test coverage:
 
 - Test fixtures isolate API tests with an in-memory database and authenticated owner override.
 - Website monitor tests cover asset creation, default alert rule creation, TLS config persistence, and disabled default alerts.
 - Notification channel tests verify saved webhook URLs are encrypted and are not returned by create, list, or update responses.
+- Worker scheduler tests cover alert threshold incident opening, recovery resolution, notification history deduplication, and alert cooldown behavior.
 
 ## Known Gaps
 
@@ -69,7 +70,7 @@ Implemented backend test coverage:
 - Email/SMTP notifications are not implemented yet.
 - Graphing exists only as placeholders; metric visualization is not implemented.
 - Worker scheduling is simple polling, not a Redis queue yet.
-- Tests still need worker notification delivery, alert evaluation, and frontend coverage.
+- Tests still need frontend coverage and broader edge-case coverage across monitor types.
 - Production deployment hardening is not done.
 
 ## Recommended Next Work
@@ -84,7 +85,7 @@ Implemented backend test coverage:
 8. Add user administration UI.
 9. Add graphs for website response time and monitor status history.
 10. Add richer alert condition editing.
-11. Add worker tests for alert evaluation and notification delivery.
+11. Add frontend coverage for monitor, alert, and notification workflows.
 
 ## Operational Notes