Bump Frigate retention and add recording health check

Increase retention: continuous 3→180d, detections 14→30d, alerts 30→730d.
Plenty of NFS headroom (~9.4 TiB free, ~6.6 GB/day for one camera).

Add frigate-recording check to services-check that verifies camera_fps > 0,
which would have caught the 6-day outage from the mqtt config removal.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

argocd/manifests/frigate/frigate-config.yml

@@ -70,14 +70,14 @@ model:
 record:
   enabled: true
   continuous:
-    days: 3
+    days: 180
   alerts:
     retain:
-      days: 30
+      days: 730
       mode: active_objects
   detections:
     retain:
-      days: 14
+      days: 30
       mode: motion
 
 snapshots:

docs/changelog.d/+frigate-retention-and-check.infra.md

@@ -0,0 +1 @@
+Bump Frigate recording retention (180d continuous, 30d detections, 730d alerts) and add camera-fps health check to services-check.

mise-tasks/services-check

@@ -83,6 +83,7 @@ check_http "CV" "https://cv.ops.eblu.me/"
 check_http "Ntfy" "https://ntfy.ops.eblu.me/v1/health"
 check_http "Authentik" "https://authentik.ops.eblu.me/-/health/live/"
 check_http "Frigate" "https://nvr.ops.eblu.me/api/version"
+check_service "frigate-recording" "curl -sf --max-time 5 https://nvr.ops.eblu.me/api/stats | jq -e '.camera_fps > 0'"
 check_http "JobSync" "https://jobsync.ops.eblu.me/"
 
 echo ""