NAMES - E2E Usability Testing MVP - Name Request and Name Examination

> _This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2024-03-13. For more details see [this post](https://changelog.zenhub.com/migration-of-epics-projects-to-sub-issues-313645?zenhub_entity_id=Z2lkOi8vcmFwdG9yL1plbmh1YkVwaWMvMjA4NzA4)._

## Description (Hypothesis):
- Short Description of the needed Epic in the below format

* As a (who/ person)
* I want (what/ goal)
* so that (why/ benefit proposal)
or
* What are the most critical features being built as part of this Epic
* Expected Outcome – Justification why this Feature must be built, what is expected value and justification for priority.

----
## Acceptance Criteria
* Used to determine whether the implementation is correct and delivers the business benefits

----
## Additional Information
* Start date when team will start to work on: This is visible in ZenHub under "Roadmap"
* End date Epic will be delivered: This is visible in ZenHub under "Roadmap"
* T-shirt size: X (S, M, L, or XL) (S=1-2 Sprints, M=2-3 Sprints, L=4-5 Sprints, XL=not sure, probably more than 5 Sprints). Story points needs to be updated in Epic. This can be decided by team.
* Process Flow (if applicable)
* CM considerations?
* Possible dependencies or blockers foreseen right now? - Please create a story and block this epic by the dependency story.

----
Enabler Epics:
* action
* result
* object

No implementation files, tests, entry points, or concrete acceptance criteria are named; the issue is an auto-created epic template. Start by clarifying the missing Description, Acceptance Criteria, process flow, and dependencies, then identify the relevant E2E test entry points. Done should be defined by agreed acceptance criteria for name request and name examination usability.

Written by the indexing model from the issue text.