Team Credentials, Matchmaking Status, and Collaboration Messages
TeamIds, purpose-separated TeamKeys, TeamPairingRole/State, TeamPairingCoordinator, TeamService actions, and wire messages are currently explicitly present.
Why are you still a candidate?
TeamService has performed roster, kick, leader transfer, key distribution, and PKI verification, but roster is still a NodeId vector; the code has no closed TeamMember, membership, revision, revocation, and team lifecycle models.