Connect PauseReactivateToggle to MentorStatusBLoC
epic-peer-mentor-pause-ui-state-task-009 — Wire PauseReactivateToggle to MentorStatusBLoC using BlocBuilder and BlocListener. The toggle renders based on current state (loading spinner during Loading, badge colour from Success payload, error snackbar on Error). Dispatch PauseMentorEvent or ReactivateMentorEvent with reason string from PauseConfirmationDialog confirmation callback.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 3 - 413 tasks
Can start after Tier 2 completes
Implementation Notes
Use BlocConsumer with both listener (for side effects: SnackBar) and builder (for UI rebuild). Set buildWhen: (previous, current) => current is MentorStatusLoading || current is MentorStatusSuccess || current is MentorStatusError to avoid rebuilding on unrelated states. For the loading spinner, use SizedBox(width: buttonWidth, height: 44, child: Center(child: CircularProgressIndicator.adaptive())) to preserve layout dimensions. For the dialog flow: await the showDialog
Use ScaffoldMessenger.of(context).showSnackBar() inside the BlocListener — never inside the builder. Guard the dispatch call: if (context.read
Testing Requirements
Widget tests with MockBloc (using bloc_test / mocktail): emit MentorStatusLoading and assert spinner visible + button disabled. Emit MentorStatusSuccess(newStatus: paused) and assert badge shows 'Paused'. Emit MentorStatusError(message: 'Network error', isInvalidTransition: false) and assert SnackBar appears. Emit MentorStatusError with isInvalidTransition: true and assert warning-style SnackBar.
Tap 'Pause' and assert PauseConfirmationDialog opens. Confirm dialog and assert PauseMentorEvent dispatched with correct reason string. Tap 'Reactivate' and assert ReactivateMentorEvent dispatched. Integration test: full flow from tap → dialog → dispatch → Success state update using a real BLoC with a mocked MentorStatusService.
PauseConfirmationDialog must meet WCAG 2.2 AA focus trap requirements: when the dialog opens, focus must move to the first interactive element; when it closes, focus must return to the triggering toggle. Flutter's default showDialog does not always guarantee correct focus restoration on Android, which could trap screen-reader users.
Mitigation & Contingency
Mitigation: Use a custom modal implementation wrapping Flutter's Dialog with explicit FocusScope management and test with TalkBack on Android and VoiceOver on iOS during development, not just in final QA. Reference the accessible-modal-sheet pattern already used elsewhere in the codebase.
Contingency: If full WCAG focus management cannot be achieved within the sprint, ship the feature with a documented accessibility defect and schedule a dedicated accessibility remediation task. Communicate the known gap to the accessibility stakeholder at HLF/NHF.
If the user taps the PauseReactivateToggle rapidly before the BLoC emits a loading state, multiple PauseMentorEvents could be added to the BLoC stream, resulting in duplicate service calls and inconsistent UI state (toggle flickering between states).
Mitigation & Contingency
Mitigation: Disable the toggle widget immediately on first tap by emitting MentorStatusLoading synchronously before the async service call begins. Use BLoC's event transformer with droppable() to discard subsequent events while a transition is in progress.
Contingency: If BLoC event deduplication is not sufficient, add a debounce at the widget level (300 ms) and a server-side idempotency check in MentorStatusService that no-ops if the requested transition is already in progress.
PauseStatusBanner must conditionally render the reactivate shortcut only for users with coordinator permission. If the permission check relies on a stale role state in the Riverpod provider, a peer mentor could briefly see a reactivate action they are not authorised to use, which could cause a confusing permission-denied error if tapped.
Mitigation & Contingency
Mitigation: Source the permission check directly from the role-resolution Riverpod provider (which is kept in sync with Supabase auth) rather than from local component state. Add a widget test asserting the shortcut is absent when the user role is peer_mentor.
Contingency: If the shortcut is accidentally shown to an unauthorised user, the underlying MentorStatusService enforces role validation server-side, so the worst outcome is a visible error message rather than an actual unauthorised state change.