feat(health): add weighted health scoring algorithm for deployment monitoring

[Nexha-dev]

Closes #761

Summary

Replaces the basic health status of GET /api/deployments/[id]/health with a weighted health score (0–100) aggregated from the last 24h of analytics data.

Changes

• Add health-score.service.ts computing a weighted score from:
  • uptime (40%) — ratio of successful uptime_check events
  • p95 latency (30%) — linear interpolation between 200ms (full) and 2000ms (zero)
  • error rate (20%) — 1 - errors/total
  • RPC connectivity (10%) — live probe (Vercel circuit state used as connectivity proxy)
• Update the health route to return { score, breakdown: { uptime, latency, errorRate, rpc }, ... }.
• Tests for perfect score, proportional uptime, latency thresholds/interpolation, error-rate scoring, unhealthy RPC, and the no-data case.

Notes

• Score range 0–100, weights sum to 1.0, computed over the last 24h.

🤖 Generated with Claude Code

[drips-wave]

@Nexha-dev Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits