0.1.66-beta2 — Cmd-` stops resurrecting a workspace you quit
Pre-release
⌘` no longer brings back a workspace you quit.
Cycling walks the running workspaces, not the folder (#330)
⌘` and ⌘⇧` cycle between workspaces. They were walking every workspace directory on disk, and switching to one that has no instance launches it — so the shortcut kept resurrecting a workspace you had deliberately quit.
The cycle now steps only through workspaces that actually have a window, in the same creation order the ⌥⌘1–9 rows are numbered in. One with no instance is stepped over, never launched. Starting a workspace is what those numbered rows are for.
Two details worth stating, because both were easy to get wrong:
- Wrapping counts the running ones. With three workspaces on disk and two running, the wrap is over two — not three with a hole in it.
- Nothing else running means nowhere to go. ⌘` does not switch you to yourself.
The check reuses the same question the update path already asks before it swaps the app bundle, rather than inventing a second notion of "is this workspace alive".
Verified on the merged tree: 1701 tests · 181 suites · 0 failures · swiftlint 0 errors · swift-format clean. The three new cycle tests were confirmed running, and confirmed failing against the previous reducer — the fix is pinned, not asserted.
Everything in 0.1.66-beta1 is carried forward.