Refactor geo re-resolve endpoint into geo_service and add typed response

Docs/Tasks.md

@@ -246,7 +246,9 @@ The router knows the internal job ID string and directly manipulates the schedul
 
 ---
 
-### TASK-08 — Remove inverted layer dependency: `utils/fail2ban_db_utils.py` importing a service 🟠
+### TASK-08 — Remove inverted layer dependency: `utils/fail2ban_db_utils.py` importing a service ✅
+
+**Status:** Completed ✅
 
 **Where:**
 `backend/app/utils/fail2ban_db_utils.py` — line 8:
@@ -275,7 +277,9 @@ A util importing a service creates an implicit upward dependency that the archit
 
 ---
 
-### TASK-09 — Move `re_resolve_geo` orchestration into `geo_service` 🟠
+### TASK-09 — Move `re_resolve_geo` orchestration into `geo_service` ✅
+
+**Status:** Completed ✅
 
 **Where:**
 `backend/app/routers/geo.py` — `async def re_resolve_geo()` (lines ~142–174).