Backfill roster, staff, suspension, and team-role-usage state into Sprocket

[gankoji]

Summary

Backfill the remaining active roster/admin state from MLEDB into Sprocket, including roster placement, staff assignments, suspensions, and any remaining team-role-usage data that still matters operationally.

Why

Sprocket cannot become the complete system of record for active league administration until historical roster/staff/admin state exists there as well.

Source data

• mledb.player
• mledb.team
• mledb.team_to_captain
• suspension / restricted-player signals currently represented in legacy player state
• mledb.team_role_usage if still needed for active workflows or historical continuity

Scope

• Backfill team membership / roster slot state.
• Backfill franchise staff and captain assignments.
• Backfill suspension / restricted-player state.
• Backfill any remaining team-role-usage data required by active systems.
• Produce parity reporting by team / league.

Acceptance criteria

• Historical roster/admin state is present in Sprocket.
• Team-by-team parity can be verified after migration.
• The backfill is idempotent and reports unmapped or conflicting records.
• Active informational lookups can be answered from Sprocket after cutover.