Integrate Peer Mentor Selector into Proxy Registration Screen
epic-proxy-activity-registration-ui-task-013 — Embed the ProxyPeerMentorSelector (single-select mode) into ProxyRegistrationScreen. Dispatch SelectMentor events to the BLoC on selection. Display the selected mentor's name with a confirmation chip and clear button. Show inline validation error if form is submitted without a mentor selected.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 15 - 2 tasks
Can start after Tier 14 completes
Implementation Notes
Use BlocBuilder scoped to only the mentor-selection slice of ProxyRegistrationState to avoid rebuilding the entire screen on every BLoC state change — consider using BlocSelector. The validation error should be stored as a nullable string in the BLoC state, not as a local widget variable, so that it survives widget rebuilds and is testable. The confirmation chip should use InputChip (which has built-in delete support) rather than a custom Row. Do not use FilterChip for the selected state as it lacks semantic delete action.
The mentor selector from task-009 should be passed a callback that the screen translates into a BLoC event — keep the selector widget decoupled from BLoC directly for reusability.
Testing Requirements
Widget tests (flutter_test): stub BLoC with mentor-loaded state, verify selector renders, simulate mentor selection and verify SelectMentor event is emitted, verify confirmation chip appears with correct name, tap clear button and verify ClearMentorSelection event is emitted and chip disappears, tap submit with no mentor selected and verify validation error text appears. Unit tests: BLoC transitions for SelectMentor and ClearMentorSelection events. Accessibility test: confirm chip and clear button have correct semantics labels via SemanticsController.
The bulk registration screen combines pre-filled defaults, a dynamic multi-select participant list, per-participant conflict badges, and a batch submission confirmation — making it one of the most complex screens in the application. Scope creep or underestimated interaction complexity could cause the epic to exceed its estimate significantly.
Mitigation & Contingency
Mitigation: Implement the bulk screen in two vertical slices: (1) participant selection and form submission without conflict handling, (2) conflict badge rendering and override flow. Validate slice 1 with coordinators before building slice 2.
Contingency: If the full conflict review UI cannot be completed within the epic, ship the bulk screen with a simplified 'skip all duplicates' fallback mode and defer per-participant override toggles to a follow-up sprint.
The proxy-registration-bloc must manage state across two distinct flows (single proxy and bulk) with branching conflict paths, intermediate buffering of bulk participant selections, and reliable state reset. Incorrect state transitions could leave the UI in a loading or stale-conflict state after submission.
Mitigation & Contingency
Mitigation: Model the BLoC state as a sealed class hierarchy with exhaustive pattern matching in the UI. Write state-machine unit tests that exercise every valid transition and assert that invalid transitions are no-ops. Use flutter_bloc's BlocObserver in debug builds to log all transitions.
Contingency: If BLoC state bugs surface in QA, introduce an explicit ResetToIdle event triggered on screen disposal to guarantee clean state, and add a 'Start over' affordance visible to the coordinator at any conflict step.
The typeahead peer mentor selector with multi-select mode may be difficult to operate with VoiceOver/TalkBack, particularly the dynamic search results list and the selected-chip removal controls, risking WCAG 2.2 AA non-compliance for screen reader users.
Mitigation & Contingency
Mitigation: Wrap all search result items and selected chips with explicit Semantics widgets providing role, label, and selected-state announcements. Test the selector with VoiceOver on iOS and TalkBack on Android during development, not only at QA time.
Contingency: If the multi-select typeahead cannot be made fully accessible within the sprint, provide an alternative flat scrollable list with checkboxes as a fallback mode, toggled by an accessibility-settings flag.
The peer mentor selector must apply RLS chapter-scope filtering to show only mentors the coordinator is responsible for. If the Supabase query for the selector does not correctly join against the coordinator's chapter assignments, coordinators may see mentors from other chapters, violating data isolation.
Mitigation & Contingency
Mitigation: Implement the selector's data query using the same RLS-aware Supabase client used by the contact list feature, which already handles chapter-scope filtering. Write an integration test with a multi-chapter coordinator fixture asserting cross-chapter mentors are not returned.
Contingency: If a data isolation breach is discovered, immediately add a client-side chapter_id filter as a defence-in-depth measure and audit selector query logs for any unauthorised cross-chapter results.