0.28.3 — widen api healthcheck start_period to 180s

Measured startup is ~93s: NewHandler stalls on Infisical auth retries (~40s)
and OIDC discovery timeouts to auth.hubris.network (~35s) before binding
:8090. The api IS healthy once bound (serves /healthz); the window just needs
to clear both external-timeout phases so nomos (depends_on: api-healthy) can
start and the deploy completes.

VERSION

@@ -1 +1 @@
-0.28.2
+0.28.3

docker-compose.yml

@@ -115,10 +115,11 @@ 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.
-      # The api also retries Infisical at startup (4x with backoff) before
+      # The api's NewHandler stalls on TWO unreachable external deps at startup
-      # binding :8090 — when Infisical is unreachable that adds ~60s, so the
+      # before binding :8090: Infisical (4x auth retries, ~40s) and OIDC
-      # start period must cover it or nomos (depends_on: api-healthy) fails.
+      # discovery (auth.hubris.network, ~35s of timeouts). Total ~90-95s, so
-      start_period: 90s
+      # the start period must clear it or nomos (depends_on: api-healthy) fails.
+      start_period: 180s
 
   # Scheduler (Phase 3) — observe loop
   scheduler: