Design UI | - Corrections during Transfers (Staff Only)

Question: is this for all transfer types?
Completing Name Correction During a Transfer and Identifying as Two Separate Registrations Upon Submission

User Type: Staff Only

**Description**
When a name correction is completed as part of a transfer, the system processes this as two separate registrations:
- Corrections Registration
- Transfer Registration

There is a possibility that the Corrections registration succeeds while the Transfer registration fails. In such cases, the system must:
- Save a draft of the failed Transfer registration
- Clearly notify the user that the Transfer portion failed
- Prompt the user to open the saved draft to complete the Transfer

**To Do**
- Define and design the user flow for handling partial registration failures
- Confirm and finalize the success view for the Corrections registration
- Add badges for corrections
- update feed summary to show correction and change of ownership type
- Update the table/dashboard view to reflect separate registrations and their statuses
- Ensure outputs (confirmation messages, receipts, document records) reflect the partial completion accurately

Start by mapping the staff-only transfer flow, including the corrections and transfer registrations, partial failure state, saved draft, success view, badges, feed summary, and dashboard statuses. Define what confirmation messages, receipts, and document records must show before implementing the UI changes; done means the flow and each partial-completion outcome are finalized.

Written by the indexing model from the issue text.