@hwfee/dsh-git-bash 0.1.1

Two changes, both about a command that should have stopped and did not.

Restricted sessions are refused before anything starts. On Windows, read-only and workspace-write sessions, and any session whose mode cannot be determined, are rejected before a process is spawned instead of being run and annotated afterwards.

Cancellation, timeout and an output overrun now stop the real process tree. They used to kill only the shell the plugin started and leave a grandchild alive; because that grandchild held the stdio pipes, the call could also hang past its deadline. An output overrun returns a marked result and stops the tree, and an unconfirmed kill is reported as unconfirmed rather than claimed as a stop.

If you upgrade: a read-only or workspace-write session on Windows that used to run commands through Git Bash now gets an error. The message points at Windows PowerShell, which runs inside the sandbox.

Verified with real processes: the suite spawns a real shell that starts a real grandchild and asserts what is on disk afterwards, for the timeout, cancellation and output-overrun paths.