0.28.2 — widen api healthcheck start_period to 90s

The api retries Infisical at startup (4x with backoff) before binding :8090.
When Infisical is unreachable that adds ~60s, and the old start_period (10s)
+ 10 retries (~60s grace) ran out just before the bind — marking the api
unhealthy and failing the deploy (nomos depends_on api-healthy). 90s covers
the slow-startup window; the api genuinely serves /healthz once bound.

VERSION

@@ -1 +1 @@
-0.28.1
+0.28.2

docker-compose.yml

@@ -115,7 +115,10 @@ services:
       retries: 10
       # Migrations and seed run before this container, but the first bind can
       # still take a moment; failures inside the start period don't count.
-      start_period: 10s
+      # The api also retries Infisical at startup (4x with backoff) before
+      # binding :8090 — when Infisical is unreachable that adds ~60s, so the
+      # start period must cover it or nomos (depends_on: api-healthy) fails.
+      start_period: 90s
 
   # Scheduler (Phase 3) — observe loop
   scheduler: