Add interactive multi-select mode with 5-chapter cap
epic-contact-detail-and-edit-foundation-task-014 — Extend multi-chapter-affiliation-chip with an edit mode presenting available chapters as a selectable list. Wire the NHF 5-chapter validation rule from contact-form-validator: disable selection of additional chips once 5 are chosen and show an inline error message. Emit a typed ChapterSelectionChanged event on each change for parent widgets to consume.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 3 - 413 tasks
Can start after Tier 2 completes
Implementation Notes
Introduce an `editMode` boolean prop and an `onSelectionChanged` callback of type `void Function(ChapterSelectionChanged)`. Internally track selected IDs in a local `Set
Use `AnimatedSwitcher` for the inline warning banner to animate in/out smoothly. Avoid `GestureDetector` on top of `InkWell` — use only `InkWell` for correct ripple behavior. Follow the organization labels system so 'chapter' terminology can be overridden per org via the labels map.
Testing Requirements
Widget tests are handled in task-015. For this task: manually verify on both iOS (VoiceOver) and Android (TalkBack) that the cap enforcement reads aloud as 'Maximum affiliations reached, this item is disabled'. Verify that tapping a disabled item produces no state change. Run `flutter analyze` and confirm zero lints before PR.
Integration with contact-form-validator NHF rule must be traced by reading the validator source and confirming the cap constant is sourced from there (not duplicated).
Blindeforbundet's encryption key retrieval mechanism may not be finalised at implementation time, or session key availability via Supabase RLS may be inconsistent, causing decryption failures that expose masked placeholders to users and degrade the experience.
Mitigation & Contingency
Mitigation: Agree with Blindeforbundet on key storage and retrieval contract before implementation starts. Prototype key retrieval in a spike against the staging Supabase instance and validate the full decrypt/verify cycle with real test data before committing to the implementation.
Contingency: Implement a fallback that shows a 'field temporarily unavailable' state with a retry affordance. Log decryption failures server-side for audit. Escalate to Blindeforbundet stakeholders to unblock key management before the service tier epic begins.
NHF contacts may belong to up to 5 chapters, each governed by separate RLS policies. A coordinator's chapter scope may not cover all affiliations, causing partial profile reads or silent data omissions that are difficult to detect in tests.
Mitigation & Contingency
Mitigation: Map all RLS policy combinations for multi-chapter contacts early. Write integration tests that create contacts with 5 affiliations and query them from coordinators with varying chapter scopes. Use Supabase's RLS test utilities to verify row visibility per role.
Contingency: Add an explicit 'affiliation partially visible' state in the repository response model so the UI can communicate scope limitations to the coordinator rather than silently showing incomplete data.
Organisation-specific validation rules (e.g., NHF chapter limit, Blindeforbundet encrypted field edit flow) may expand in scope during implementation as edge cases are discovered, causing the validator to grow beyond the planned complexity.
Mitigation & Contingency
Mitigation: Define the complete validation rule set with product and org stakeholders before coding begins. Document each rule with its source organisation and acceptance test. Use a rule registry pattern so new rules can be added without modifying core validator logic.
Contingency: Timebox validator enhancements to 2 hours per additional rule. Defer non-blocking rules to a follow-on maintenance task rather than blocking the epic delivery.