Coordinator Stats Screen

This is the highest-complexity screen in the coordinator-facing mobile experience, with a high complexity rating justified by its multi-chapter aggregation logic, role-based data scoping, and the strict Bufdir export parity requirement. It depends on six other components — time-window-selector, stats-summary-cards, peer-mentor-stats-list, activity-chart-widget, stats-notifier, and chapter-scope-resolver — meaning most of those must be stable before integration testing can begin. The drill-down navigation to individual peer mentor records introduces additional coordination with the peer mentor stats screen. Plan for dedicated QA cycles to validate data accuracy against Bufdir exports across different chapter combinations (1, 3, and 5 chapters) and time windows.

Any changes to the chapter-scope-resolver or stats-notifier carry direct regression risk here.

This screen acts as the top-level coordinator widget, composing stats-summary-cards, peer-mentor-stats-list, activity-chart-widget, and time-window-selector into a cohesive layout. It subscribes to stats-notifier (likely a Riverpod StateNotifier or equivalent) for reactive state updates, and delegates chapter scoping entirely to chapter-scope-resolver to enforce the multi-chapter boundary (max 5 per NHF rule). The onChapterFilterChanged and onTimeWindowChanged callbacks trigger data refreshes through stats-notifier, which re-fetches and re-aggregates from the local data layer. Drill-down is handled via onPeerMentorSelected, which should push a new route onto the Navigator stack.

The strictest invariant is Bufdir export parity — aggregation logic must be co-located with or directly derived from the export calculation path to prevent drift. Use golden tests or snapshot tests against known Bufdir fixture data to catch any regressions.