fix(GRO-623): implement groomer data isolation in appointmentGroups, groomingLogs + batherStaffId conflict check #285

Merged
the-dogfather-cto[bot] merged 2 commits from feature/gro-623-groomer-isolation into main 2026-04-14 18:15:05 +00:00

2 Commits

Author SHA1 Message Date
Flea Flicker 67282256a7 ci: retrigger CI after flaky E2E 502
Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-04-14 18:08:14 +00:00
Flea Flicker 79effb439c fix(GRO-623): implement groomer data isolation in appointmentGroups, groomingLogs + batherStaffId conflict check
- appointmentGroups router: add Hono<AppEnv>(), groomer isolation on GET /:id, PATCH /:id, DELETE /:id; managers/receptionists only for POST /
- groomingLogs router: add Hono<AppEnv>(), groomer isolation on GET /, POST /, DELETE /:id
- appointments POST/PATCH conflict check: also check batherStaffId conflicts
- Non-groomer roles retain full access on all endpoints

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-04-14 17:52:20 +00:00