MHR | Q2 | Navigation Improvements |Preserve Table State When Returning from Registration Detail View

As a **registry analyst reviewing a list of registrations**,
I want to **return to the registration table exactly as I left it after viewing a registration**,
So that **I can move through multiple registrations efficiently without losing my place or reapplying filters**.

---

### User Story
**As a** registry analyst reviewing a list of registrations,
**I want** a **Close** button on the registration-details view that returns me to the **registration table** exactly as I left it (same filters, sort order, scroll position, and highlighted row),
**So that** I can move through multiple registrations efficiently without losing my place or re-applying table settings.

### Context
This story supports the **Registration Review** activity. It improves workflow efficiency by preserving the user's table state when navigating between the registration list and detail views. This enhancement reduces repetitive actions and supports high-volume review tasks.

```
🗓️ Sprint Planning
Sprint 26.4 started July 23, 2025
BA work – already completed
Design work – Sprint 26.5
Development work – Sprint 26.6
```

#### UX/UI Link
[Figma or design spec URL – to be added]

### Business Rules
- [ ] A clearly labeled “Close” or “Back to Table” button must be placed at the top-right and/or bottom of the registration detail view.
- [ ] The button must use a consistent icon (e.g., ← or ✖) with a tooltip: “Return to previous table view”.
- [ ] The system must retain the following using session storage:
- Active filters
- Sort order
- Scroll position
- Highlighted row
- [ ] The previously selected row should be briefly highlighted upon return.
- [ ] If no session data is found, display a banner: “Default view loaded – previous session expired or unavailable.”
- [ ] The Close button and restored table view must support keyboard navigation and screen readers.

### Acceptance Criteria / Scenarios

**Scenario:** Return to registration table with preserved filters
- **GIVEN** I am viewing a registration from a filtered registration table
- **WHEN** I click the Close button
- **THEN** I should return to the registration table with the same filters, sort order, and scroll position applied

**Scenario:** Preserve highlighted row after closing registration
- **GIVEN** I have a row highlighted in the registration table
- **WHEN** I open and then close a registration
- **THEN** The previously highlighted row should remain highlighted

**Scenario:** Session-based persistence of table state
- **GIVEN** I have not left the registration module or ended the session
- **WHEN** I close a registration
- **THEN** The table state should be restored to the last known state

**Scenario:** Fallback to default view when no filters are applied
- **GIVEN** I open a registration from an unfiltered registration table
- **WHEN** I click the Close button
- **THEN** I should return to the default unfiltered registration table view

### Notes
- This feature improves workflow efficiency by eliminating the need to reapply filters and scroll position.
- Tooltip suggestion: “Return to previous table view”
- Consider displaying a message like: “Returning to your previous view…” for clarity.
- Refer to the parent ticket for additional business rules and technical details.

Start with the registration table and registration-detail views, then review the parent ticket and the design specification once its URL is available. Implement the Close or Back to Table flow with session-based filters, sorting, scroll position, and row highlighting, including the fallback message and keyboard and screen-reader support; verify the listed acceptance scenarios.

Written by the indexing model from the issue text.