Describe terminal selection and focus acceptance workflow

This commit is contained in:
Codex
2026-10-13 15:29:07 +03:00
parent 4e65a0bdc3
commit dcf1fbae40
+13 -11
View File
@@ -72,22 +72,24 @@ result, compiler errors and process exit status remain the build acceptance gate
## Fresh-session recovery and profile changes
A session with no profiles opens recovery with first-use guidance. Enter `:shell`
to run `hydra add NAME --iso PATH` and `hydra start NAME`; leave the shell and enter
`:refresh`. After adding or removing profiles, refresh reloads the profile list,
rebuilds workspace rules, restarts only the session's own compositor, and attaches
new isolated viewers to running guests. QEMU processes and workloads survive.
The recovery prompt can then reconnect the new names; reserved Left/Right chords
switch between their workspaces. `:quit` closes the recovery prompt.
A session with no profiles opens the terminal VM menu with first-use guidance.
Use `:run` for guided creation, or `:shell` for the existing CLI. Selecting a
machine opens it on its own workspace. `:refresh` reloads the profile list after
manual edits, rebuilds workspace rules, restarts only the session's own compositor,
and attaches viewers to verified live guests. QEMU processes and workloads
survive. Reserved Left/Right chords switch between their workspaces; `:quit`
closes the menu.
`dev/session-refresh-smoke.py` exercises the actual product launch loop, recovery
helper, `:shell` and `:refresh`, starting with an empty profile directory. A
test-only labwc wrapper selects private headless backends; a terminal command
feeder drives recovery and a scratch shell adds and starts two counter guests.
Actual labwc and native Wayland viewers then demonstrate fresh keyboard focus
transitions in both directions, hidden workload continuity, unchanged QEMU
PIDs/UUIDs through refresh, and guest survival after normal compositor exit.
This checks the recovery command flow, not physical terminal rendering/usability.
The menu explicitly selects the second VM, and the rebuilt compositor must
start on its workspace with that viewer focused. Actual labwc and native
Wayland viewers then demonstrate fresh keyboard focus transitions in both
directions, hidden workload continuity, unchanged QEMU PIDs/UUIDs through
refresh, and guest survival after normal compositor exit. This checks the
terminal command flow, not physical terminal rendering/usability.
It leaves snapshots, recovery output, protocol logs and `result.json` in
`/tmp/hydra-session-refresh-*` and stops only its verified scratch QEMU processes.