umami: fix Goals/Funnels 'Something went wrong' (migrate saved reports to v3.1.0 schema)

The saved Goal + Funnel reports used a pre-v3.1.0 parameters shape (urls/dateRange)
that umami 3.1.0's report schema rejects (400 -> 'Something went wrong'). Migrated
both reports in the umami DB to the current funnelReportSchema/goalReportSchema
(steps[], top-level dates, goal type/value). Verified funnel route now passes schema
validation. TODO updated/closed.

docs/TODO.md

@@ -1,10 +1,18 @@
 # Performance West — TODO / Backlog
 
-
 ## Analytics / Umami
-- [ ] **Fix Umami Goals and Funnels** — both report "Something went wrong" when
+- [x] **Fix Umami Goals and Funnels "Something went wrong"** — RESOLVED 2026-06-13.
-      opened. Investigate the self-hosted Umami instance (analytics.performancewest.net):
+      Root cause: the saved Goal and Funnel reports were created in an older umami
-      likely a DB/migration, version, or query issue specific to the Goals and
+      version and stored `parameters` in a pre-v3.1.0 shape. umami 3.1.0's
-      Funnels reports (other Umami reports appear to work). Check umami container
+      funnelReportSchema / goalReportSchema reject the old shape (HTTP 400 ->
-      logs + version, and whether these features need a schema migration or a
+      client shows "Something went wrong").
-      newer Umami release. (Reported 2026-06-13.)
+        - Funnel old: {urls:[...], window, dateRange:{startDate,endDate}}
+          v3.1.0 needs: {startDate, endDate, window, steps:[{type:'path',value,filters:[]}]}
+        - Goal old: {dateRange:{...}} (no type/value)
+          v3.1.0 needs: {startDate, endDate, type, value}
+      Fix: migrated the two saved reports in the umami DB to the v3.1.0 schema
+      (urls->steps, lifted dateRange to top-level dates, set goal type=url/value).
+      Verified: the funnel route now returns 401 (auth-gated, schema valid) instead
+      of 400; underlying data exists (3,195 -> 86 on the compliance funnel paths).
+      NOTE: running v3.1.0 = latest; the "Failed to find Server Action ... older/
+      newer deployment" log lines are unrelated stale-browser-cache noise.