Validate v1.1 Windows PowerShell and Git Bash lifecycle

[BrettKinny]

This was generated by AI during triage.

Type: HITL

What to build

Run the v1.1 lifecycle end to end on Windows with PowerShell 7, Docker Desktop, Git for Windows, ConsoleHost, and the VS Code PowerShell host. Qualify PowerShell and Git Bash as separate adapter-native lifecycle paths: each must safely consume and clean up its own Install identity. Validate profile integration, paths and characters, supported SSH behavior, and destructive-operation prompts.

Record the Candidate version, source SHA, image digest, Windows build, Docker Desktop, PowerShell and Git versions, shell hosts, and pass or fail evidence in this issue.

Acceptance criteria

• Fresh install.ps1, Box launch, rebuild, uninstall.ps1, and purge complete under PowerShell 7.
• Generated PowerShell profile text parses before installation; existing profile content and unmatched managed markers are never truncated or followed through a reparse point.
• Shell functions work in ConsoleHost and VS Code PowerShell hosts.
• Install in one PowerShell host and uninstall in another removes only the intended CurrentUserAllHosts integration.
• Git Bash uses the MSYS home while its Install identity remains under the Windows user home; its launcher retains required winpty and MSYS path-conversion behavior.
• Each FORMAT=1 identity is consumed only by the adapter that created it, and a foreign adapter refuses it without mutation. Adapter switching is unsupported in v1.1 and tracked by Design Windows SSH-agent forwarding and cross-adapter lifecycle migration #107.
• Paths containing spaces and non-ASCII characters survive install, launch, rebuild, and uninstall.
• Git identity contains name and email only; host credentials and signing configuration are not mounted.
• Native PowerShell read-only SSH-directory fallback works with correct permissions. Git Bash agent forwarding and its read-only fallback are validated separately.
• Purge asks the second nonempty-Workspace confirmation and refuses unrelated colliding resources.
• Results and any failures are attached here and the v1.1 manual UAT checklist is updated.

Deferred follow-up

• Design Windows SSH-agent forwarding and cross-adapter lifecycle migration #107 tracks Windows OpenSSH-agent forwarding and safe cross-adapter identity migration after v1.1.

Blocked by

None - can start immediately.