[codex] Add no-hardware operator console demo

[lishehao]

Summary

• Polish the Tkinter operator console into a three-panel lab workflow UI with setup, measurement plot, run/status/export, source receipt, and operator safety areas.
• Add deterministic no-hardware Hyperframe fixture data, generation script, docs, and tests.
• Add real Tkinter UI capture helpers plus point-by-point fixture replay demo artifacts.
• Embed the point-by-point demo video in the README with poster/direct-link fallback.

Honesty boundary

This demo is a simulated/no-hardware fixture replay. It does not claim live hardware validation, and the production AWG/oscilloscope adapters are not used in the demo capture path.

Validation

• PYTHONPATH=src python -m unittest discover -s tests -> 47 tests OK
• python -m py_compile scripts/generate_hyperframe_fixture.py scripts/capture_operator_console_demo.py scripts/capture_operator_console_point_replay.py src/app/presentation/tk/app_window.py src/app/presentation/tk/control_panel.py src/app/presentation/tk/controller.py src/app/presentation/tk/plot_widget.py src/app/presentation/tk/run_panel.py src/app/presentation/tk/ui_event_handler.py src/app/presentation/tk/view_model.py src/app/demo/hyperframe_fixture.py
• git diff --check origin/main..HEAD
• Confirmed README demo mp4/png and fixture artifacts exist locally with nonzero sizes.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 482136d7b8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Resolve demo fixture from bundled assets

When the app is launched from outside the repo, or with AUTO_LOAD_OFF_TEST_ROOT set to a writable runtime directory as the README recommends for packaged/lab installs, self._paths.root_dir is not where the committed demo_data assets live. In that context the new Load Demo Fixture button looks for <runtime-root>/demo_data/hyperframe_simulated_fixture.mat and reports it missing even though the fixture is bundled with the project; resolve this path relative to the package/repo asset location, or copy/fallback to the runtime root.

Useful? React with 👍 / 👎.