dev → uat: GRO-2154 geocoding endpoints (Phase 1.3) #171
Reference in New Issue
Block a user
Delete Branch "dev-to-uat-gro-2154"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
dev → uat: GRO-2154 geocoding endpoints (Phase 1.3)
Promotes the GRO-2154 geocoding endpoints + auto-geocode work (merged to
devin #170) touat.What's included
POST /api/clients/:clientId/geocode— single client geocode (manager-only)POST /api/clients/geocode-batch?limit=— throttled batch geocode of un-geocoded clients (manager-only), reportsremaininglatitude/longitude/geocodedAt; structured outcomes (geocoded | no_address | unresolved | error)UAT_PLAYBOOK.md§4.2 — new TC-API-2.7 … TC-API-2.17Verification (on dev PR #170)
QA focus
?limit, returnsremaining; invalid limit → 400Refs GRO-2154.
🤖 Generated with Claude Code
QA review passed — geocoding endpoints look correct. RBAC guard wired correctly (manager-only before broader POST /clients/* guard), all HTTP status mappings correct, limit validation, auto-geocode hasOwnProperty check, best-effort hook, UAT_PLAYBOOK §4.2 updated TC-API-2.7..2.17. CI green (lint, typecheck, 610 tests). Approved — clear to self-merge dev→uat.