Build Chapter Assignment Editor add-chapter flow
epic-multi-chapter-membership-handling-ui-task-008 — Implement the add-chapter section of ChapterAssignmentEditor: a searchable chapter list (debounced text field + filtered ListView) that shows available chapters not already in the contact's affiliations. Selecting a chapter calls Cubit.trackPendingAdd(). Display a non-dismissible feedback banner when the pending count reaches the 5-chapter maximum, with plain-language text explaining the NHF rule. Follow Design System v3 layout.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 3 - 413 tasks
Can start after Tier 2 completes
Implementation Notes
Use a StreamController with debounce (from rxdart or manual Timer) for the search field to avoid filtering on every keystroke — 300ms is the standard for search fields. Compute the filtered list inside a BlocBuilder using a combination of the cubit's availableChapters list and the search query; keep the query in local widget state (StatefulWidget) since it is transient UI state, not domain state. For the 5-chapter rule: derive the effective count as (existingActiveAffiliations.length + pendingAdds.length) and show the banner when this equals or exceeds 5. The banner must use a non-dismissible design (no close button) — use a styled Container with a warning color token and an icon.
ListView.builder is mandatory given that NHF has up to 1,400 local chapters. Use an itemExtent on ListView.builder to improve scroll performance with large lists.
Testing Requirements
Write unit tests using bloc_test to verify: (1) trackPendingAdd emits the correct updated state, (2) the 5-chapter limit is enforced in the cubit (no-op or error state beyond 5). Write widget tests using flutter_test: (1) mount ChapterAssignmentEditor with a mock cubit emitting a known state, type in search field and assert list filters correctly, (2) assert already-affiliated chapters are absent from the list, (3) tap a chapter and assert trackPendingAdd is called with the correct ID, (4) simulate pending count reaching 5 and assert the MaxChaptersBanner appears, (5) assert banner disappears when count drops below 5. Test debounce behavior by advancing the fake timer 299ms and asserting no filter, then 300ms and asserting filter applied. Target 90% branch coverage.
The Duplicate Activity Warning Dialog must announce itself to VoiceOver and TalkBack immediately on appearance. Flutter's default modal semantics do not guarantee focus shift to the dialog on all platform versions, risking silent appearance for screen reader users — a WCAG 2.2 failure.
Mitigation & Contingency
Mitigation: Wrap the dialog content in a Semantics node with liveRegion: true and explicitly request focus via FocusScope.of(context).requestFocus() on the dialog's primary action button in the post-frame callback. Test on physical iOS (VoiceOver) and Android (TalkBack) devices, not only simulators.
Contingency: If automatic focus fails on a specific platform version, add a platform-specific fallback using SemanticsService.announce() to force a live region announcement of the dialog's headline text.
The Chapter Membership Cubit tracks pending changes before commit to support the two-step add/confirm flow. If the user navigates away mid-edit or the app is backgrounded, uncommitted pending state could be replayed incorrectly on return, causing phantom affiliation additions or removals.
Mitigation & Contingency
Mitigation: Design the Cubit to hold pending changes only in transient in-memory state with no persistence. On any navigation-away event, emit a reset state that discards pending changes. Prevent accidental navigation during an active edit by showing a discard-changes confirmation dialog.
Contingency: If state desync is reported in production, add an explicit state reconciliation step in the Cubit's onResume handler that re-fetches the authoritative affiliation list from the repository and resets all pending state before re-rendering.
The Chapter Assignment Editor's searchable chapter list must load quickly. If the organisation has hundreds of chapters (NHF has 1,400 local chapters) and the full list is fetched on dialog open, the editor will be slow to display and the search will be sluggish.
Mitigation & Contingency
Mitigation: Scope the chapter list to only chapters within the coordinator's administrative scope (not all 1,400), leveraging the existing hierarchy access scope service. Implement server-side search with a minimum 2-character threshold and debounce to avoid excessive Supabase queries.
Contingency: If the scoped list is still too large, add local caching of the chapter list with a 15-minute TTL and an explicit refresh button, ensuring the editor is always responsive even on poor network conditions.