[enaboapps]

Closes #1302

Third slice of #1299, stacked on #1304.

• Try it in the editor header opens the panel being edited in the scanner straight away, as if chosen from Home: one of the user's panels, a built-in menu, or the Mouse panel or Keyboard. The Switchify window minimises first, because the scan acts on whatever is in front and the editor's own fields must not be what the tried tiles type into. It is off while there are unsaved changes.
• Backend: try_panel command (main thread) → scanning_runtime::try_panel, which builds a point-scan engine as a switch would, begins the session with Workflow::open_for_trial(TrialTarget) (Session::begin_with), dispatches OpenMouse/OpenKeyboard where needed, renders and publishes. Refused while scanning is not armed, while a phone is scanning, during switch practice, or when the licence is locked. Menus that need a chosen point cannot be tried.
• Docs: a "Try a panel" section on the Panels page.

Validation

• cargo fmt --check, cargo clippy --all-targets -D warnings, cargo test (940 passed; new workflow test covering each target and the Back route home), npm run lint, npm test (354 passed), npm run build in site/.
• Dev build with Cua Driver: Try it on the Keyboard editor minimised the window and the scanning keyboard appeared over the browser that was behind it.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
site	Ready	Preview	Nov 2, 2026 10:04pm UTC

[enaboapps]

Owed: a run on a Mac (npm run macos:run) to confirm that Try it hides the app, the previous app comes forward, and the scan overlays stay on screen now that they are marked as unable to hide. Only the CI macOS build has compiled that path.