Measured on tabertron today: stop -> start -> first HTTP 200 on 4041 takes 31s, against a 30000ms probe. So `pgh app start favela-web` has been reporting "readiness probe (http) did not succeed within 30000ms" on every start while the app came up fine seconds later — a false failure that reads exactly like a broken install. 31s is the WARM case: an existing index and already-known DID topics. favela-web binds 4041 only after joining its topics and starting to index, so a cold start (empty store, first-time joins) is strictly slower — which is precisely the case about to be exercised installing this on stortron. 120s is the ceiling for "still booting", not a target; readiness exists to catch a crash-loop, and a crash-loop is still caught, just later. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>