Refresh or retire scripts/ui_mock_preview.py so docs visuals match the current UI

Summary

As of 2026-04-15, scripts/ui_mock_preview.py appears stale relative to the current preflight/runtime UI and the current operator workflow.

This matters because the script is the obvious candidate for generating consistent docs visuals, but right now several mock values and labels do not line up with the actual app behavior.

Why this matters

We want human-first docs with integrated screenshots inside the manual pages, not a separate screenshot dump. A stale mock-preview script will produce misleading screenshots and weak docs.

Current signs of drift

• Uses older/static labels and states that may not reflect the current preflight launch flow
• Hard-codes example content that does not match the latest operator wording
• May no longer cover the most important states we want to document

Candidate direction

Decide whether scripts/ui_mock_preview.py should be:

1. refreshed and kept as the canonical docs-visual generator, or
2. retired if we prefer screenshots from real runs only

If kept, it should render the states we actually want to document:

• preflight dashboard
• preflight resize-warning state
• Doric/Teensy setup success states
• open-loop launch summary
• closed-loop assignment flow
• runtime waiting / active / fault states

Acceptance criteria

• Decide keep vs retire
• If kept, update labels/content to match the current UI wording and flows
• Ensure docs authors can generate stable visuals from it intentionally
• Add a short README/doc note explaining how to use it for docs screenshots or exports

Start with scripts/ui_mock_preview.py and compare its labels, example content, and rendered states against the current preflight and runtime UI. Decide whether the script remains useful, then either update it for the listed documentation states or retire it. Done includes a short README or documentation note explaining how docs authors should generate visuals, if the script is kept.