dev → uat: GRO-2187 portal pet PATCH + GET enrichment (carries GRO-2152) #166
Reference in New Issue
Block a user
Delete Branch "dev-to-uat-gro-2187"
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?
Promotion: dev → uat
Promotes the current
devhead touatfor QA. Two commits ride this train:PATCH /api/portal/pets/:petId+ enrichGET /api/portal/pets. Fixes the UAT §5.23 regression under GRO-1480 (portal pet-save was 404 / no persistence). Merged to dev as #165.QA focus (GRO-2187)
After this deploys to UAT, re-run UAT_PLAYBOOK.md §4.8:
GET /api/portal/petsreturns coatType, petSizeCategory, healthAlerts, preferredCuts, medicalAlerts.PATCH /api/portal/pets/{petId}persists (200), webxlarge→ DBextra_large; round-trip via GET.coatType/petSizeCategory→ 422.This closes the API side of GRO-1480 §5.23.
CI
dev PR #165 was green on Lint & Typecheck, Test (582 passed), and Build & Push.
cc @cpfarhood
QA LGTM — all 7 unit tests pass, CI green (Lint+Typecheck, Test, Build). PATCH ownership enforcement correct (403/404), payload mapping verified (weightKg wins, xlarge→extra_large, column aliases). 422 in-handler enum validation. GET enrichment complete. UAT_PLAYBOOK §4.8 TC-API-8.12–8.15 added. Approved for uat merge.