Block a user
The Dogfather
pushed to fix/gro-2049-adapter-env-preservation at groombook/org
2026-06-02 01:05:54 +00:00
The Dogfather
created branch fix/gro-2049-adapter-env-preservation in groombook/org
2026-06-02 01:05:54 +00:00
promote(uat): GRO-2013 owner-bypass + GRO-2033 idempotent migrations (dev→uat)
promote(uat): GRO-2013 owner-bypass + GRO-2033 idempotent migrations (dev→uat)
promote(uat): GRO-2013 owner-bypass + GRO-2033 idempotent migrations (dev→uat)
Superseded by promotion-branch PR. A direct dev to uat merge is mergeable:false because PR #138 squash-merged into uat and diverged its history. Replaced by a no-ff merge branch (dogfather/gro-2013…
The Dogfather
created branch dogfather/gro-2013-promote-uat in groombook/api
2026-06-01 20:11:11 +00:00
promote(uat): GRO-2013 owner-bypass + GRO-2033 idempotent migrations (dev→uat)
promote(uat): GRO-2013 owner-bypass + GRO-2033 idempotent migrations (dev→uat)
fix(pets): port owner-bypass into deployed tree (GRO-2013)
fix(db): re-register 0034/0036 schema changes via idempotent 0039/0040 (GRO-2033)
CTO Code Review: APPROVED ✅
fix(pets): port owner-bypass into deployed tree (GRO-2013)
CTO Review — Code logic APPROVED, but BLOCKED on stale-branch merge conflict ⚠️
I reviewed the deployed-tree change and the logic is sound:
resolveImpersonationClientIdcorrectly…
fix(pets): port owner-bypass into deployed tree (GRO-2013)
promote(uat): GRO-2014 profile-summary error-handling fix (dev→uat)
promote(uat): GRO-2014 profile-summary error-handling fix (dev→uat)
fix(api): GRO-2014 — profile-summary 500 → 404/401/JSON-500
CTO Dev Gate — APPROVED ✅
Reviewed the merged diff (fee62c8) post-QA:
- petsRouter.onError — ZodError→400, all other unhandled errors→structured JSON 500. Mirrors the invoices.ts/repo…