Test Scenario: Verify screenshot capture in the QA Validation Runner panel

Open the QA Validation Runner panel and load this file (scenario_verify-screenshot-capture.org). Confirm a "Screenshot" toolbar action appears next to Open/Save, and is enabled now that a scenario is loaded (it should be disabled before any scenario is loaded).

Click the toolbar's Screenshot action. Within ~1-2 seconds (before the capture fires), switch focus to some other window (e.g. a terminal or this doc in an editor) so the capture isn't just a screenshot of the runner itself. Confirm a status bar message reports a saved filename, and that a PNG file named after this scenario's slug plus a timestamp appears in the same directory as this .org file.

Double-click this step (or any other) to open its detail window. Confirm a "Screenshot" button appears in the button row alongside Mark PASS/Mark FAIL/Reset to Pending. Click it, again switching focus away within the delay window. Confirm: a PNG named after this scenario's slug, this step, and a timestamp is saved next to the scenario doc, a status bar message confirms the save, and a line referencing the screenshot's filename is auto-appended into this step's Notes box.

Trigger a second scenario-level screenshot and a second per-step screenshot (same step as above). Confirm both produce new files with distinct names (timestamp differs) rather than overwriting the first captures.

Click the toolbar's Save icon. Confirm no errors, and that the step Notes (including the auto-appended screenshot reference) are persisted.

Outside the app (file browser, git status, or an editor), confirm: all captured PNGs exist next to this scenario doc and open as valid images showing the expected content; this doc's * Results section and each exercised step's *** Result child heading are filled in correctly; the Steps' instructional text above is unchanged.