fix: migrate legacy peak-level sign-ups onto their peak's expedition

Existing sign-ups (event_id NULL, made before per-expedition joins) now get attached to the peak's earliest non-cancelled plan event on startup, so '+n going' shows inside the expedition. Idea peaks with no plan event stay peak-level.

Author: Dmenec

src/store.rs

@@ -160,6 +160,21 @@ fn run_migrations(conn: &Connection) {
     let _ = conn.execute("ALTER TABLE peaks ADD COLUMN is_challenge INTEGER NOT NULL DEFAULT 0", []);
     let _ = conn.execute("ALTER TABLE peaks ADD COLUMN expedition_group TEXT", []);
     let _ = conn.execute("ALTER TABLE peak_signups ADD COLUMN event_id TEXT", []);
+    // Attach legacy peak-level sign-ups to their peak's (earliest) planned expedition,
+    // so the "+n going" now shows inside the expedition. Idea peaks (no plan event)
+    // keep event_id NULL and stay peak-level.
+    let _ = conn.execute(
+        "UPDATE peak_signups SET event_id = (
+            SELECT ce.id FROM calendar_events ce
+            WHERE LOWER(ce.peak_name) = peak_signups.peak_key
+              AND ce.event_type = 'plan' AND ce.status != 'cancelled'
+            ORDER BY ce.planned_date ASC LIMIT 1)
+         WHERE event_id IS NULL
+           AND EXISTS (SELECT 1 FROM calendar_events ce
+                       WHERE LOWER(ce.peak_name) = peak_signups.peak_key
+                         AND ce.event_type = 'plan' AND ce.status != 'cancelled')",
+        [],
+    );
     let _ = conn.execute("ALTER TABLE users ADD COLUMN avatar_url TEXT", []);
     let _ = conn.execute("ALTER TABLE calendar_events ADD COLUMN category TEXT NOT NULL DEFAULT 'peak'", []);
     let _ = conn.execute("ALTER TABLE calendar_events ADD COLUMN track TEXT", []);