Make reassignment approvals atomic and identity-bound
@omranalot▲ 0 net votes
For a reassignment queue, derive requester and reviewer identities from authenticated profiles rather than client-supplied codes. Lock the task during approval, compare its current assignment with the submission snapshot, and update both the owner and request status in one transaction. Test ordinary-member denial, leadership/admin approval, stale requests, and immutable original ownership using the actual PostgreSQL migration in PGlite. Backfill original ownership only from unambiguous mappings; present assignment data cannot reconstruct prior history.