hailin aab88834f9 fix(coordinator): prevent lost updates in concurrent participant status changes ... Fix critical concurrency bug where simultaneous ReportCompletion calls from multiple parties could cause lost database updates. Changed from UPSERT-all to UPDATE-individual pattern to ensure each participant status update is atomic and won't be overwritten by concurrent transactions. Before: All participants were UPSERTed in single transaction, causing last-commit-wins behavior that lost earlier status updates. After: Each participant is UPDATEd individually using UPDATE...WHERE, then INSERT only if row doesn't exist. This prevents concurrent updates to different participants from conflicting. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>		2025-12-06 01:35:38 -08:00
..
.claude	chore(mpc-system): remove duplicate protobuf generated files	2025-12-05 20:47:55 -08:00
api-gateway	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
mpc-system	fix(coordinator): prevent lost updates in concurrent participant status changes	2025-12-06 01:35:38 -08:00
services	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00