Fix pending transaction check to cover both initiator and partner

[Copilot]

The pending transaction guard only checked whether initiatorId was already involved in a pending transaction, allowing a partnerId with an existing pending offer to be targeted — creating conflicting concurrent pending transactions for the same player.

Changes

• app/api/sessions/[id]/transactions/route.ts: Expanded the pending check to block creation if either initiatorId or partnerId appears in any role (initiator or partner) in an existing pending transaction for the round.

// Before: only blocks if initiatorId is involved
WHERE round_id = ${round.id} AND status = 'pending'
  AND (initiator_id = ${initiatorId} OR partner_id = ${initiatorId})

// After: blocks if either player is involved in any role
WHERE round_id = ${round.id} AND status = 'pending'
  AND (
    initiator_id = ${initiatorId} OR partner_id = ${initiatorId}
    OR initiator_id = ${partnerId} OR partner_id = ${partnerId}
  )

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
live-game	Error		Mar 10, 2026 5:43am