Implement BLoC state rendering in screen widget
epic-peer-mentor-detail-screen-bloc-and-assembly-task-008 — Connect PeerMentorDetailScreenWidget to PeerMentorDetailBLoC using BlocBuilder. Render a centered CircularProgressIndicator for loading state, a full-screen error widget for total failure, and the assembled section layout for loaded/partial-error states. Partial errors must show per-section fallback UI (e.g., 'Assignment data unavailable') without collapsing other sections.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 6 - 158 tasks
Can start after Tier 5 completes
Implementation Notes
Use a sealed class hierarchy for PeerMentorDetailState so that the BlocBuilder switch expression is exhaustive and the compiler enforces all branches. The partial-error state should carry a Map
Do not use BlocListener for UI rendering — keep rendering purely in BlocBuilder. The fallback widget should be a small, reusable SectionFallbackWidget(message: String) so it can be tested independently.
Testing Requirements
Unit-test PeerMentorDetailScreenWidget using flutter_test and bloc_test. Pump the widget with a fake BLoC stub emitting each state in turn (Loading, Loaded, PartialError, Error) and assert the correct child widget tree is rendered using find.byType and find.text. Verify that the retry button in Error state dispatches LoadPeerMentorDetail. Verify that each partial-error section shows its fallback text while sibling sections still render their real data.
Use mockito or mocktail to mock the BLoC. Target 100% branch coverage across all four state branches.
The parallel Future.wait aggregation pattern may produce race conditions or incorrect merged state when some repositories resolve significantly faster than others, particularly if the BLoC receives a RefreshDetail event while a prior fetch is still in flight.
Mitigation & Contingency
Mitigation: Implement cancellation token pattern in the aggregation service to abort in-flight fetches on new events. Add BLoC test scenarios for rapid successive refresh events to validate state consistency.
Contingency: If race conditions persist, switch to a sequential-with-timeout fetch strategy for the first release and profile the performance impact before deciding whether parallel fetch optimization is worth the complexity.
Integrating PeerMentorDetailScreenWidget into the existing StatefulShellRoute navigation structure may conflict with the Contacts tab's existing route hierarchy, requiring changes to navigation-route-config that could affect other teams' features.
Mitigation & Contingency
Mitigation: Coordinate with the Contact List and Contact Detail feature teams before adding the new route. Review the existing StatefulShellRoute configuration and confirm the peer mentor detail route can be nested under the Contacts branch without path conflicts.
Contingency: If route conflicts arise, temporarily implement the peer mentor detail as a modal overlay (push route) rather than a shell route child, preserving functionality while the navigation architecture conflict is resolved.
The course enrollment screen that the certification alert banner links to may not yet exist or may be implemented in a separate feature epic, leaving a broken navigation tap for HLF users in the initial release.
Mitigation & Contingency
Mitigation: Check the certification management feature implementation status before finalizing Epic 4 scope. If the enrollment screen is not available, design the tap action to open the HLF course enrollment URL in an external browser as an interim solution.
Contingency: Implement the CTA as a configurable action: if the enrollment route exists in the router, push it; otherwise, launch the configured org-specific enrollment URL via url_launcher, ensuring HLF users can always take action on expired certifications.