fix(2): plausible HTTP_TIMEOUT 600→1200 + DEPLOY_TIMEOUT 1200 — app 500s until clickhouse/migrations ready

v1 failed wait_healthy 'not healthy / (last status 500)': plausible's app starts before clickhouse
(plausible_events_db) is ready (recipe depends_on names events_db, mismatched → no swarm ordering) and
returns 500 until DB migrations finish (several min on cold deploy). It serves 302 once ready; widen
the health window.

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

tests/plausible/recipe_meta.py

@@ -3,8 +3,12 @@
 # We use a fixed CI value for SECRET_KEY_BASE — safe for ephemeral per-run deploys.
 HEALTH_PATH = "/"
 HEALTH_OK = (200, 302)
-DEPLOY_TIMEOUT = 900
-HTTP_TIMEOUT = 600
+# plausible's app starts before its clickhouse events DB is ready (the recipe's `app` depends_on lists
+# `events_db` but the service is named `plausible_events_db`, so swarm applies no ordering) and returns
+# 500 until clickhouse + DB migrations finish — several minutes on a cold deploy. Give a wide HTTP
+# window so the health poll waits out that init (it serves 302 once ready). [v1 failed at HTTP_TIMEOUT=600.]
+DEPLOY_TIMEOUT = 1200
+HTTP_TIMEOUT = 1200
 
 # Phase-2: configure the recipe's required env (no placeholders allowed).
 EXTRA_ENV = {