Convert the following Chrome DevTools Recorder steps into lean, clean, human-readable Jira "Steps to reproduce".

Goal:
Create concise Jira reproduction steps that match the recorded ShareX video of the Chrome DevTools Recorder replay.

Rules:

1. Keep only user-relevant and business-relevant actions.
2. Convert technical Recorder actions into human UI actions.
3. Remove CSS selectors, XPath, coordinates, offsets, durations, timeouts, generated IDs, internal DOM paths and duplicate micro-steps.
4. Do not include implementation details in the Steps to reproduce.
5. Use visible UI labels where possible. If no visible label exists, use the business name of the element.
6. Group low-level actions into meaningful business steps.
7. Keep the result short:
   • 3–5 steps for simple bugs
   • 5–8 steps for normal UI flows
   • max. 10 steps only if absolutely necessary
8. Put setup data into "Preconditions", not into the steps.
9. Do not mix Expected result or Actual result into the steps.
10. Do not invent missing data. If a label or value is unclear, mark it as [to be confirmed].
11. Mask sensitive data, personal data, tokens, customer data and credentials.
12. Mention that a ShareX video of the Chrome DevTools Recorder replay is attached.
13. Output in concise German Jira style.

Required output format:

Preconditions:

• ...

Steps to reproduce:

1. ...
2. ...
3. ...

Expected result:
...

Actual result:
...

Evidence:
Ein ShareX-Video des Chrome-DevTools-Recorder-Replays ist dem Ticket beigefügt.

Recorder steps:
[paste Recorder steps or JSON here]