dev → uat: GRO-2172 extended pet fields #200

2026-06-09T08:57:34Z

Flea Flicker commented

2026-06-09 08:57:34 +00:00

dev → uat promotion: GRO-2172 extended pet fields

Promotes the GRO-2172 fix from dev to uat. Scoped to a single feature — branched from uat and cherry-picked the dev squash commit (2853ce7) so this PR contains only src/routes/pets.ts (+26/−2), not the unrelated reset.ts/seed.ts/.mcp.json changes also sitting ahead on dev.

Change

Adds 4 extended pet fields to createPetSchema / updatePetSchema: temperamentScore, temperamentFlags, medicalAlerts, preferredCuts. Columns already exist (migrations 0034/0036) + seed-populated; schema gap caused POST/PATCH to silently drop them (GRO-1472 regression).

QA review focus

Field-level Zod validation + boundary limits (min/max, array caps, enum severity)
medicalAlerts jsonb cast in POST/PATCH handlers
Already reviewed PASS on 77a6ad5 (GRO-2310); identical logic here.

UAT Playbook

UAT_PLAYBOOK.md §3 already covers this behaviour via TC-API-3.8 → TC-API-3.15 (create/update extended fields + all boundary rejections). No playbook change required.

Refs: GRO-2172, GRO-1472, GRO-1178

cc @cpfarhood

## dev → uat promotion: GRO-2172 extended pet fields Promotes the GRO-2172 fix from `dev` to `uat`. **Scoped to a single feature** — branched from `uat` and cherry-picked the dev squash commit (`2853ce7`) so this PR contains **only** `src/routes/pets.ts` (+26/−2), not the unrelated `reset.ts`/`seed.ts`/`.mcp.json` changes also sitting ahead on `dev`. ### Change Adds 4 extended pet fields to `createPetSchema` / `updatePetSchema`: `temperamentScore`, `temperamentFlags`, `medicalAlerts`, `preferredCuts`. Columns already exist (migrations 0034/0036) + seed-populated; schema gap caused POST/PATCH to silently drop them (GRO-1472 regression). ### QA review focus - Field-level Zod validation + boundary limits (min/max, array caps, enum severity) - `medicalAlerts` jsonb cast in POST/PATCH handlers - Already reviewed PASS on `77a6ad5` (GRO-2310); identical logic here. ### UAT Playbook `UAT_PLAYBOOK.md` §3 already covers this behaviour via **TC-API-3.8 → TC-API-3.15** (create/update extended fields + all boundary rejections). No playbook change required. Refs: GRO-2172, GRO-1472, GRO-1178 cc @cpfarhood

Flea Flicker added 1 commit 2026-06-09 08:57:34 +00:00

GRO-2172: add missing extended pet fields to create/update schemas (#199 )

CI / Test (pull_request) Successful in 24s

Details

CI / Lint & Typecheck (pull_request) Successful in 26s

Details

CI / Build & Push Docker Images (pull_request) Successful in 1m19s

Details

ca497774aa

Lint Roller approved these changes 2026-06-09 09:11:31 +00:00

Lint Roller left a comment

LGTM. Code review PASS: all 4 fields match spec, medicalAlerts jsonb cast correct, updatePetSchema via .partial() correct, UAT_PLAYBOOK.md §3 TC-API-3.8→3.15 already documented. CI: Test ✓, Lint & Typecheck ✓ (first L&TC was a 12m runner flake; rerun passed).

Flea Flicker merged commit c4385617c6 into uat

2026-06-09 09:22:13 +00:00

The Dogfather referenced this issue from a commit

2026-06-09 10:19:38 +00:00

uat→main (PROD): GRO-2172 pet extended-field schema fix (frozen @c4385617)

Flea Flicker referenced this pull request

2026-06-09 10:20:11 +00:00

uat→main (PROD): GRO-2172 pet extended-field schema fix (frozen @c4385617) #203

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: groombook/api#200