Activity Registration Wizard

NHF explicitly requires document attachments to activities for Bufdir audit purposes (invitations, screenshots). Without a wizard flow that supports attachments, the platform cannot replace existing Word-form workflows for this organisation. The structured step-by-step approach also addresses the cognitive accessibility needs raised by NHF for users such as stroke survivors, where a single dense form creates too high a barrier. By providing both a quick log and a wizard, the platform satisfies the full spectrum of user capability and activity complexity, maximising data completeness across the user base.

Implemented as a Flutter Navigator 2.0 route stack with the Wizard Step Controller service managing step state and validation. Each step is a separate widget pushed onto the stack, allowing the system back button and an explicit back affordance to function correctly - required for WCAG 2.2 compliance (no reliance on swipe-only navigation). Activity Attachments are stored via multipart POST to the REST API; the Activity Attachments Table records file references. In offline mode, attachments are queued in the mutation outbox with binary blobs stored in the local SQLCipher database. The wizard must not lose partial state on backgrounding; use Riverpod state persistence or equivalent keep-alive strategy.