Spec 024 — Scheduled checks + uptime calc + activity events

[Copxer]

Closes #73

Spec: specs/phase-5-monitoring/024-scheduled-checks-and-uptime.md

Automation half of phase 5. Spec 023 shipped CRUD + manual probes; this spec automates them via Laravel's scheduler, calculates count-based uptime % over rolling windows, and emits incident / recovery activity events on healthy↔failed status transitions (which now broadcast in realtime to the right rail).

Summary

• DispatchDueWebsiteChecksJob — every-minute scheduler dispatcher bound via Schedule::job(...)->everyMinute()->withoutOverlapping(). Soft-cap 500. Loads + filters in PHP (the last_checked_at + check_interval_seconds predicate is cross-DB awkward to express in raw SQL). Ordered last_checked_at ASC with nulls first → never-checked rows first, then oldest stale; prevents starvation on the high-id tail when total > cap.
• RunWebsiteCheckJob — per-website async wrapper around spec-023's actions. tries=1 (a failed probe IS a recorded outcome).
• GetWebsitePerformanceSummaryQuery — count-based uptime % over 24h / 7d / 30d windows + last_incident_at. Slow counts as up. Null on empty windows (Vue renders —%).
• RecordWebsiteCheckAction extended with category-transition detection. Healthy ↔ Failed swings emit website.down / website.up activity events. Pending → Healthy first probe + steady-state runs are silent.
• ActivityEventCreated::broadcastOn() extended to resolve the recipient channel for monitoring-source rows via metadata.website_id → website → project → owner_user_id (those rows have repository_id = null, which previously made the broadcaster silently drop realtime fan-out).
• RecentActivityForUserQuery extended to surface monitoring events alongside repo events.
• Show page renders a 4-tile uptime strip (24h / 7d / 30d / last incident) under the existing meta dl.

Test plan

• vendor/bin/pint --test passes.
• php artisan test — 27 net new passing tests across 4 new test files + 2 extended (probe action — actually unchanged, summary query, dispatcher, run job, record action transitions, activity query monitoring scope, controller show summary). Full suite 339 passed (was 312). 50 failures are env-CSRF baseline; CI passes them.
• npm run build clean.
• Manual smoke (post-merge): create a monitor for https://example.com/up with a 60s interval, confirm php artisan schedule:work triggers RunWebsiteCheckJob and the Show page's uptime % climbs as checks land. Stop the upstream → observe a website.down event flow into the right rail in realtime.

Self-review notes

Self-review pass via superpowers:code-reviewer flagged one material item:

Monitoring activity events do NOT broadcast in realtime. ActivityEventCreated::broadcastOn() returns [] when repository === null. Monitoring events always have repository_id = null, so every website.up/website.down is silently dropped at broadcast time.

Fixed by extending broadcastOn() with a website-scoped path: when source === 'monitoring', resolve channel via metadata.website_id → Website → project → owner_user_id. Also updated the spec body + action docblock to be honest about the broadcast plumbing.

Plus the recommended dispatcher starvation fix: orderBy('last_checked_at') + orderByRaw('last_checked_at IS NULL DESC') so when website count exceeds the soft cap the dispatcher prefers the never-checked / oldest-stale rows instead of stranding the high-id tail.

Deferred (skip / future):

• JSON predicate type-coercion across drivers — works on SQLite (tests) and MySQL (prod) per Laravel docs; defensive cast not added.
• Pending → Healthy first-probe silence — locked decision per spec; could surface as a "monitoring online" event in a future polish.
• Aggregate caching — phase-1 row counts make the 6 count queries per Show page sub-millisecond; revisit when slow-query logs flag it.

Phase 5 status

#	Spec	Status
023	Website monitor MVP	🟢
024	Scheduled checks + uptime + activity events	🟢 (this PR)
025	Overview integration + Reverb live updates + perf charts	⬜ next

Waiting for "merge it" before squash-merging. Then spec 025 (last of phase 5) wires the Overview KPI card + perf charts on top of this data.