Enhancement| Corrections during Transfers of Ownership

### User Story
**As a** registry analyst (staff user),
**I want** to correct an owner’s name directly within the Transfer upon Death workflow when a mismatch is detected,
**So that** the ownership record reflects the accurate legal name without requiring a separate Statutory Declaration or additional filings.

### Context
Part of the **“Review & File Transfer”** activity in the Transfer Upon Death process. Today, analysts must reject or delay filings whenever the name on record differs from supporting documents. Enabling an inline correction reduces turnaround time and improves data integrity.
```
Sprint Planning Notes:
- 🧭 PO Work – Sprint 26.4 (August 20 – September 2, 2025)
- 📌 BA Work – Sprint 26.5 (September 3 – September 16, 2025)
- 🎨 Design Work – Sprint 26.6 (September 17 – September 30, 2025)
- 💻 Development Work – Sprint 27.1 (October 1 – October 14, 2025)
```

#### UX/UI Link
_To be added (Figma – Transfer Workflow ► Dual Registration concept)_

### Business Rules
- [ ] Feature is **staff-only**; external users cannot access name-correction controls.
- [ ] System must support **two registration actions in one transaction**:
- [ ] **Correction registration** (updates legal name on title)
- [ ] **Transfer registration** (completes ownership transfer)
- [ ] A visual badge **“Name Corrected”** appears on the registration record and in search results.
- [ ] All corrections are timestamped and audit-logged with the analyst’s ID.
- [ ] Data validation blocks submission if the corrected name still mismatches supporting docs.

### Acceptance Criteria / Scenarios
- **GIVEN** an analyst opens a Transfer upon Death application
**AND** the system detects a name mismatch between the title and supporting docs
**WHEN** the analyst selects **“Correct Name”**
**THEN** a name-editable field becomes available
**AND** the system prepares a **correction registration** alongside the transfer.

- **GIVEN** the analyst has entered the corrected legal name
**WHEN** they click **“Submit Transfer”**
**THEN** both the correction and transfer registrations are filed in a single transaction
**AND** the registration history shows a **“Name Corrected”** badge.

- **GIVEN** the transaction is complete
**WHEN** another staff member or external party searches the MH record
**THEN** the corrected name is displayed
**AND** the badge is visible to indicate historical accuracy
**AND** audit logs reflect the change.

### Notes
- Requires updates to the backend registration API to bundle two filing types.
- Consider edge cases where multiple name corrections may be required; only the latest should display the badge.
- **Could-Have (Post-MVP)** pending team capacity.

______### Context & Problem
During the transfer of ownership of manufactured homes, there are frequent cases where name discrepancies arise—often due to:

- Errors on death certificates
- Misspellings or incorrect names in existing records

These discrepancies can cause issues in the registration process, especially when the name on the ownership record does not match supporting documentation. Staff are requesting to be enabled to edit and correct names during the transfer process when there is a mismatch in the names, without the need for a Statutory Declaration (currently the name field is read-only).

### Proposed Enhancement:
Allow dual registration types during a single transaction:

- A correction registration
- A transfer registration

This would be a staff-only feature to maintain control and accuracy.
Would require development work and UI changes to support dual actions in one workflow.
**UI/UX Suggestion:**
Add a badge or label (e.g., “Name Corrected”) in the registry to indicate that a correction occurred during the transfer.
Helps maintain transparency for future searches and audits.

Related Ticket: #28868

No files, tests, or entry points are identified; start by reviewing related ticket #28868 and locating the Transfer upon Death workflow and registration API. Done means staff-only name correction can be bundled with a transfer, with validation, audit logging, and the “Name Corrected” badge reflected in registration history and search.

Written by the indexing model from the issue text.