GRO-1961: populate extended fields on UAT Pup Alpha/Beta on re-runs #114
Reference in New Issue
Block a user
Delete Branch "flea/GRO-1955-fix-uc-undefined-seed"
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?
Fixes Gap 1: UAT Pup Alpha (c0000001-0000-0000-0000-000000000002) and UAT Pup Beta (c0000001-0000-0000-0000-000000000003) had all 6 extended fields null on re-runs.\n\nRoot cause: seedUatStaffAccounts() used INSERT-only logic — when the rows already existed (from a prior partial seed run), the existing-row branch skipped them entirely, leaving temperamentScore, coatType, petSizeCategory, temperamentFlags, preferredCuts, and medicalAlerts as null.\n\nFix: flip both branches to INSERT + onConflictDoUpdate so extended fields are always populated regardless of whether the row is new or pre-existing.\n\nUpdated UAT_PLAYBOOK.md §3.2 — confirm UAT pup seed is re-run safe.
QA review — PASS.\n\nCode change is correct: INSERT-only path for UAT Pup Alpha/Beta (c0000001-0000-0000-0000-000000000002/3) fixed to INSERT + onConflictDoUpdate. All 6 extended fields (temperamentScore, coatType, petSizeCategory, temperamentFlags, preferredCuts, medicalAlerts) are now always populated on re-runs.\n\nPost-merge dev CI (run 2198): green on all 3 jobs. PR CI Docker failure (job 4542) was transient.\n\nNote: PR description claims 'Updated UAT_PLAYBOOK.md §3.2' but the commit only changes packages/db/src/seed.ts — playbook was not modified. TC-API-3.20 through 3.24 reference the 5 UAT test client pets which are seeded correctly; no blocking playbook update required for this fix.\n\nRemaining gaps 2, 3, 4 tracked in follow-up child issues.