Split from #184 (F1.12)
Summary
Scan a player's Play! Pokemon QR code at an event to quickly identify them for borrowing workflows. This is the core use case extracted from F1.12, focused on the borrowing/event context only.
Details
QR code content
The Play! Pokemon app displays a QR code containing a JWT token with player identity data (name, player ID).
PlayPokemonQrDecoder service
- Decode and validate the JWT from the QR payload
- Extract player name and Pokemon Player ID
- Match against existing users by `playerId` field
Use case: Player identification at events
- Staff scans a player's QR at an event (using camera scanner from F5.6)
- System looks up the player by Pokemon ID
- Shows their profile, active borrows, and deck assignments
- Enables quick hand-off confirmation for deck lending
Dependencies
NOT in scope (stays in #184 for Phase F)
- Quick account creation from QR
- Staff assignment from QR
Acceptance Criteria
Split from #184 (F1.12)
Summary
Scan a player's Play! Pokemon QR code at an event to quickly identify them for borrowing workflows. This is the core use case extracted from F1.12, focused on the borrowing/event context only.
Details
QR code content
The Play! Pokemon app displays a QR code containing a JWT token with player identity data (name, player ID).
PlayPokemonQrDecoder service
Use case: Player identification at events
Dependencies
NOT in scope (stays in #184 for Phase F)
Acceptance Criteria