Windows notes

zerd builds and runs on Windows 10/11 (x64; on ARM it runs under emulation). Shell commands run in Git Bash, so the same bash the model writes for Mac and Linux works unchanged. What differs from Mac and Linux:

	Mac / Linux	Windows
Shell for tool calls, checks, hooks, `!cmd`	`/bin/bash` (plain `sh` if bash is missing)	Git Bash; PowerShell if Git for Windows is not installed
Stopping a command	kills its whole process group	`taskkill /T /F` on its process tree
Data folder	`~/Library/Application Support/zerd` or `~/.local/share/zerd`	`%APPDATA%\zerd`
File permissions on sessions and `.env`	`0600` / `0700`	the profile folder's own permissions
OS sandbox	macOS `sandbox-exec` only	none: confined tools and shell path checks still apply
Workspace guard	blocks `~`, `/etc`, other users' homes	blocks `~`, other users' profiles under `C:\Users`, and `C:\Windows`

Known gaps on Windows, said plainly:

The shell path scan looks for Unix-style paths. A command that names a C:\... path outside the project is not caught by the scan the way /etc/passwd is; the file tools are still confined, but shell commands only have that scan to lean on.
Real symlinks need Developer Mode or an administrator, so the helper that links node_modules into a review scratch copy may skip the link there.
CI builds and tests on Windows, but the Windows test run is reported, not required, until the tests that assume a Unix shell and /tmp are ported. Treat Windows as supported, not battle-tested.
Run zerd from Windows Terminal or any ANSI-capable terminal; the old cmd.exe console host draws the full-screen UI poorly. ZERD_PLAIN=1 gives the classic scrolling layout.