saqib mirandClaude Sonnet 5 58d0a98134 fix(016-load-concurrency-testing): US1 — retry assignment creation on race conflict ...

AssignmentRepository.createAssignment now catches the
assignments_one_current_per_ticket unique-violation and retries the whole
supersede-then-create transaction (bounded, with jitter) instead of
propagating a raw P2002 to the caller. Verified against real Postgres: before
this fix, 20 genuinely concurrent assignment attempts on the same ticket
reliably threw an unhandled unique-constraint error; after it, exactly one
current assignment results every time across 10 repeated runs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-09-09 17:10:10 +05:30

..

concurrency

fix(016-load-concurrency-testing): US1 — retry assignment creation on race conflict

2026-09-09 17:10:10 +05:30

e2e

first commit

2026-08-19 16:29:17 +05:30

fixtures

first commit

2026-08-19 16:29:17 +05:30

helpers

feat(013-auth-hardening): password reset, password strength policy, login rate-limiting

2026-09-07 21:22:49 +05:30

integration

fix(015-reporting-dashboards): count humanEscalated by Assignment existence, not status

2026-09-09 16:31:13 +05:30

unit

feat(015-reporting-dashboards): four real reporting/analytics endpoints

2026-09-09 11:59:38 +05:30