- Create new server-party-co-managed service with two-phase event handling - Phase 1 (session_created): Store join token and wait - Phase 2 (session_started): Execute TSS protocol (same timing as service-party-app) - Add PartyRoleCoManagedPersistent role to isolate from normal keygen/sign - Update docker-compose.yml with 3 co-managed party instances - Update deploy.sh service lists - Modify selectPartiesByCompositionForCoManaged to use new role This ensures co_managed_keygen sessions use dedicated parties that behave 100% compatible with service-party-app, without affecting existing keygen/sign flows. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| account | ||
| message-router | ||
| server-party | ||
| server-party-api | ||
| server-party-co-managed | ||
| service-party-app | ||
| session-coordinator | ||
| tss-wasm | ||