Windows parity: Workspace deletion needs live teardown and recovery qualification #723

Current reconciliation - 2026-11-09

Saved-session discovery is no longer an unimplemented gap: PR #912, merged at 6bdc23701b00230a2a683008f9db909e05286380, discovers project- and loop-level saved layouts for extra tabs/splits in a closed workspace. Its injected/disposable-fixture results are source/contract evidence, not live deletion. The 2026-10-13 narrowed deletion scope below remains authoritative.

PR #965, merged at ca286b4bdb42574db0e148f75e3b8cdb1f19858c, separately implements native New Workspace directory/window preview and Create & Open. Bounded runtime acceptance covers directory creation, a distinct owned window, selected workspace, onboarding and exact-path publication to an explicitly registered observer. It does not prove the application's separate pipe handle or workspace deletion. Beta31 was built from fd8d1516430877e4bce3a6466695d29402ed5120 BEFORE #965 and does not contain this new form.

Still open / Partial: ordinary live deletion of a non-current fixture workspace, actual daemon shutdown and termination of every owned saved session, fail-closed confirmation, and Recycle Bin recovery. Broader manager/rename/multi-instance and visual/input criteria remain separate. New-creation naming is now in main: PR #966 merged on 2026-11-09 at f0e8ac1e11a29d25f6282142a5be6339ae4c23ea (tree 78174bcac01e5a3ddcd6b0e955c8c5e69896c6d7). All 26 checks on PR head c30b789c2cb70a970960550b6b9e01b5f4f1af7e completed: 21 SUCCESS / 5 SKIPPED, including legitimate Linux/macOS skips, not executions. Local naming/full/shard/default-integration acceptance retains its original source bindings, NOT newly executed merge-head runtime evidence; original wrapper policy-stop and earlier integration failures remain preserved. Existing directory identities and legacy rename are unchanged. This bounded creation-only change does not establish all-Unicode or paired visual/device parity. Windows beta32 was published as a public prerelease on 2026-11-09 at 17:48:21Z from exact f0e8ac1e11a29d25f6282142a5be6339ae4c23ea / tree 78174bcac01e5a3ddcd6b0e955c8c5e69896c6d7, including #965 and #966. Hosted release run 42665844030 completed successfully on attempt 1 at that source. GitHub lists exactly the 49,982,485-byte ZIP (SHA-256 010807612977ffba628f0cb0a8c77e0fd09767aba93d7eae7b60b5c1d7430402) and 96-byte checksum sidecar; release evidence records fresh build/Verify and 50/50 manifest hashes. This unsigned invitation-only preview is not an installed beta31-to-beta32 upgrade, installer walkthrough, all-Unicode or whole-parity qualification; publication does not relabel old native receipts as new executions. Beta31 remains fd8d-based and excludes both #965 and #966. This does not qualify deletion or close this lifecycle issue.

The original report, acceptance criteria and historical evidence below are preserved; the dated scope/progress above supersedes obsolete missing-feature claims.

Is your feature request related to a problem?
Parity row Workspace lifecycle (Application shell and navigation) in investigation/ui-parity-matrix.md is Partial.

macOS: List/switch, create, rename, delete with fail-closed confirmation, keyboard/UIA reachable.

Windows today: List, switch, create, rename and delete exist with confirmation.

Gap: Deletion effects are injected in tests only (no real recycle, daemon signal or session kill). Shell sessions of a non-current workspace saved outside its own projects directory cannot be discovered and are reported unended. A shared-host menu failure has an unproven cause.

Describe the solution you'd like
Make a non-current workspace's shell sessions discoverable, then add a live Dev Box delete that recycles a fixture workspace, signals the daemon, ends its sessions and checks the Recycle Bin recovery.

Describe alternatives you've considered
N/A

Additional context
This is an implementation gap: work remains in the product before the row can be validated. Parity status and the beta25 Dev Box review are recorded in #719.