Add Phase 3 Spark Control integration spec; mark Phase 2 done

docs/spark-control-integration.md: the SSH command contract (status via
docker inspect; restart via docker restart; update via git fetch + reset
--hard origin/master + docker compose up -d --build) plus the one-time
conversion of the Spark's ~/matrix-bridge to a Gitea clone. No bot code
change. Update source = git-pull-from-Gitea; rides Spark Control's existing
SSH into spark-32d0 (no new key). Corrected the infra note: Spark is on the
LAN with the Start9/Gitea host, so Spark->Gitea resolves directly.

ROADMAP.md

@@ -26,19 +26,23 @@ after it.
 - **Exit (falsifiable):** 3 consecutive real messages each correctly launch a drivable
   session on the phone.
 
-## Phase 2 — Multi-room routing
+## Phase 2 — Multi-room routing — DONE (2026-06-15)
 
 - Room → repo mapping table; the bot routes by `room_id` (config over code).
 - **Exit (falsifiable):** 3 real uses across ≥2 rooms, correct repo every time, zero
-  wrong-directory launches.
+  wrong-directory launches. *Met — owner-confirmed N=3 pass.*
 
-## Phase 3 — Spark Control integration
+## Phase 3 — Spark Control integration — SPEC DRAFTED (2026-06-15), awaiting Spark Control dev
 
 - Bot container status surfaced on the Spark Control dashboard.
 - One-click update (pull + restart) wired the same way Spark Control drives the Sparks today
   (SSH/commands behind a button).
 - **Exit (falsifiable):** bot status is visible and the bot can be updated/restarted from the
   panel.
+- **Spec:** `docs/spark-control-integration.md` — the SSH command contract + one-time Spark
+  migration to a Gitea clone. Decided: update = git-pull-from-Gitea; Spark Control's existing
+  SSH into `spark-32d0` carries the buttons (no new key). matrix-bridge needs no code change;
+  remaining work is Spark Control-side + the one-time migration.
 
 ## Phase 4+ — Future direction (documented, not yet scoped to build)