Wire proxy submission to proxy registration service
epic-bulk-and-proxy-registration-bulk-ui-task-005 — Connect the proxy activity wizard's final confirmation step to the Proxy Registration Service. On coordinator confirmation, dispatch the assembled ProxyActivityPayload including recorded_by_user_id and peer_mentor_id. Handle success and error responses, navigate back on success, and display inline error feedback without closing the wizard on failure.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 4 - 323 tasks
Can start after Tier 3 completes
Implementation Notes
Use a BLoC or Cubit to manage the submission lifecycle (idle → loading → success/failure). The confirm button should emit a SubmitProxyActivity event. In the BLoC, call the Proxy Registration Service and emit ProxySubmissionSuccess or ProxySubmissionFailure states. In the widget, use BlocListener to trigger navigation on success and BlocBuilder to render the inline error on failure — never mix navigation logic inside BlocBuilder.
Derive recorded_by_user_id from Supabase Auth's currentUser.id at submission time, not from wizard state, to prevent tampering. For the error banner, use a conditional widget below the CTA that appears only when the state is ProxySubmissionFailure; do not use a dialog as it breaks the 'do not close wizard' requirement. Cancel in-flight requests using a CancelToken pattern or by disposing the BLoC on page pop.
Testing Requirements
Unit tests: test BLoC/Cubit event handling for submission success, submission failure (network), submission failure (RLS 403), and duplicate warning acknowledgement. Mock the Proxy Registration Service interface. Integration tests: verify that the correct ProxyActivityPayload (with coordinator's user_id and target mentor_id) is sent to the service. Widget tests: confirm loading indicator appears on confirm tap, inline error renders on failure, wizard does not close on failure, wizard closes and navigates back on success.
E2E (flutter_test): simulate a full proxy wizard flow ending in a successful submission and verify navigation outcome. Test coverage target: ≥85% on the confirmation step widget and its BLoC.
If the batch insert RPC returns a mix of successes and failures (e.g., 3 of 10 mentors fail due to constraint violations that slipped through application-level duplicate detection), the confirmation screen result state becomes ambiguous. A coordinator who sees '7 of 10 succeeded' may not know whether to manually register the 3 failures, retry, or escalate — leading to either duplicate registrations or silent underreporting.
Mitigation & Contingency
Mitigation: Design the Bulk Registration Service to return a strongly typed BulkRegistrationResult with per-mentor RegistrationOutcome (success | duplicate_detected | constraint_violation | permission_denied). Design the result screen to list each failed mentor with a specific, plain-language reason and a one-tap 'Retry for this mentor' action that pre-fills the activity wizard with the batch template for that individual.
Contingency: If per-mentor retry UI is too complex to deliver within the epic scope, fall back to displaying failed mentors with their error codes and instructing coordinators to use single-proxy mode for the failures. Document this as a known limitation in release notes and create a follow-up ticket for per-mentor retry in the next sprint.
The Proxy Activity Wizard must reuse the existing activity wizard step widgets (type, date, duration, notes) while injecting a proxy attribution banner and a different submission payload builder. If the existing wizard is not designed for composability, the proxy variant may require forking the widget tree, creating two maintenance-diverging codebases that will drift out of sync when the base wizard is updated (e.g., new activity types added, new mandatory fields).
Mitigation & Contingency
Mitigation: Before implementing the Proxy Activity Wizard, audit the existing activity wizard's architecture. If steps are already extracted as independent StatelessWidget/ConsumerWidget classes, compose them directly with a wrapping Column that injects the attribution banner. If they are tightly coupled inside a parent widget, refactor the existing wizard to accept a nullable ProxyContext parameter before starting the proxy variant — this refactor should be a prerequisite task in this epic.
Contingency: If refactoring the base wizard is blocked by unrelated in-flight work on that component, implement the proxy wizard as a full fork but create a shared StepWidgets library file that both the base wizard and proxy wizard import. Schedule a deduplication refactor as a tech-debt ticket in the next planning cycle.
The bulk registration flow spans three sequential screens (multi-select → activity form → confirmation → result) with shared mutable state: the selected mentor list, the activity template, the per-mentor duplicate warnings, and the final submission result. Managing this state across screens without a well-designed Bloc risks state leaks, stale duplicate warning data after mentor removal, and confirmation screen inconsistencies if the user navigates back and changes the mentor selection.
Mitigation & Contingency
Mitigation: Define a single BulkRegistrationBloc (or Cubit) with explicit state transitions covering: MentorsSelected → ActivityTemplateCompleted → DuplicatesChecked → ConfirmationReady → Submitting → SubmissionResult. Each backward navigation event (e.g., 'Back' from confirmation to mentor selection) dispatches a ResetToMentorSelection event that clears downstream state. Unit test every state transition with edge cases including empty mentor list, all mentors having duplicates, and network failure during submission.
Contingency: If state management complexity causes persistent bugs in testing, simplify by passing state explicitly through Navigator arguments (immutable snapshots per screen) rather than a shared Bloc. This reduces flexibility but eliminates cross-screen state mutation bugs.