feat(models/up): log details when returning 503

[kilo-code-bot]

Summary

When /api/models/up returns 503, also emit a console.error with the unhealthy monitored models and their per-window metrics. Currently 503 responses leave no server-side trace (only DB/timeout failures hit Sentry via the catch block), so postmortems require replaying the endpoint with ?at=<iso> within the 24h lookback. This adds a durable log line so we can reconstruct what tripped the alert from logs alone.

Verification

N/A — log-only change behind the existing 503 branch.

Visual Changes

N/A

Reviewer Notes

• Logs currentRequests, previousRequests, baselineRequests, percentChange, uniqueUsersBaseline per unhealthy model plus the anchor time. No PII; kilo_user_id is not included.
• Only fires when hasSignificantDrop is true, so no log volume change in steady state.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 files)

• apps/web/src/app/api/models/up/route.ts

---

_{Reviewed by gpt-5.5-2026-04-23 · 78,850 tokens}