hailin 78119bc6a4 fix(proto): add party_index to JoinSessionResponse for correct index assignment ... The JoinSessionResponse from coordinator was missing party_index field, causing message router to try finding self's index in OtherParties (which only contains other parties). This resulted in incorrect party index assignment leading to "duplicate indexes" error in TSS keygen. Changes: - Add party_index field to coordinator's JoinSessionResponse proto - Coordinator now includes PartyIndex in gRPC response - Message router uses party_index from coordinator instead of searching 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>		2025-12-06 00:08:47 -08:00
..
adapters	fix(proto): add party_index to JoinSessionResponse for correct index assignment	2025-12-06 00:08:47 -08:00
application/use_cases	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
cmd/server	feat(mpc-system): add signing parties configuration and delegate signing support	2025-12-05 22:47:55 -08:00
domain	feat(mpc-system): integrate reliability mechanisms and enable party-driven architecture	2025-12-05 20:30:03 -08:00
Dockerfile	chore(mpc-system): update Dockerfiles to Go 1.24 and fix line endings	2025-12-05 16:40:32 -08:00