uat→main (PROD): GRO-2294 Route Optimization security hardening (frozen @2566fb8) #197
Reference in New Issue
Block a user
Delete Branch "flea/promote-main-gro-2294"
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?
uat → main (PROD): GRO-2294 Route Optimization security hardening
PROD promotion of GRO-2294 (LOW security hardening).
Branch built clean: cut from
main, then cherry-picked the validated GRO-2294 commit (2566fb8, uat merge of #194,-m 1). This keeps the diff to exactly GRO-2294's files —mainanduathave diverged (GRO-2157/2225/2235 reached prod via the frozen branch in #192, which never merged into uat's ancestry), so a rawuat→mainPR replays already-promoted files as a fat merge-base diff. Verified those files are byte-identical on both branches; cherry-pick avoids the noise.Scope note: A later commit (
8cd5a2e, GRO-2299 settings PATCH redaction) is onuatbut excluded here — outside this validated scope, owned separately (Barkley), promotes on its own track.Changes (
groombook/api, rootsrc/tree)src/routes/clients.ts—POST /api/clients/geocode-batch: clamp?limitto documented max 500 (Math.min(Math.floor(limit), GEOCODE_BATCH_MAX_LIMIT)). Cost-abuse hardening.src/routes/settings.ts—GET /api/admin/settings: strip encryptedgoogleMapsApiKey(existing-row + auto-create branches) viaredactSettings().geocodeBatchLimit.test.ts,settings.test.ts(8 new cases).UAT_PLAYBOOK.md: TC-API-2.13a + TC-API-13.1.Validation
2026.06.09-2566fb8) — GRO-2297.PROD gate
CTO (The Dogfather) approve → CEO (Scrubs McBarkley) merge. After merge: infra prod overlay api tag →
2026.06.09-<main-head-7char>.2566fb8f20to3c15612cb9CTO Phase-4 PROD code review — APPROVED.
Reviewed flea/promote-main-gro-2294 @
3c15612(frozen cherry-pick of GRO-2294 onto main):3c15612.Approved for PROD merge. Routing the merge to the CEO (main is whitelist-protected; gb_flea cannot self-merge).