Let Windows gate like everywhere else, and say what the platforms are

Windows went green in three commits, so continue-on-error is gone and it blocks
like the others.

The README said macOS first and Linux works. Both true, both incomplete now: the
install matrix runs on ubuntu, macos and windows every push, and Linux also
installs for real and fires the hooks. Windows means Git Bash or WSL. Native
PowerShell is not a target and never will be — everything here is a shell script.

What is actually macOS-only is smaller than the old wording implied, and neither
half is the installer: Conductor is a Mac app, and the claude wrapper is zsh so
bash users get the environment without it. The launchd sentence is gone for good
— nothing here schedules anything on any platform.

Author: itsvedantkumar

.github/workflows/verify.yml

@@ -151,12 +151,11 @@ jobs:
   # Windows user running these scripts actually has. Native PowerShell is not a target and the
   # README says so; this proves the Git Bash and WSL-shaped path, which is the one people use.
   #
-  # continue-on-error until the platform is green: the job exists to report the truth about
-  # Windows on every push rather than to gate merges on a platform that was never supported.
-  # Flip it off once it passes.
+  # It gates like every other platform. It started as continue-on-error because Windows had
+  # never been supported and the job existed to report the truth rather than block merges; it
+  # went green in three commits, so the crutch is gone.
   install-windows:
     runs-on: windows-latest
-    continue-on-error: true
     defaults:
       run:
         shell: bash

README.md

@@ -325,10 +325,19 @@ commits and the full diff of every script the gate executes, and asks before mer
 re-recording trust hashes; without a terminal it refuses instead of assuming. The `--yes`
 flag exists for automation, and anything automated enough to use it is back to trust-on-pull.
 
-**macOS first.** CI installs and exercises the hooks on Linux every push, so Linux works and
-stays working. But Conductor is macOS only, and `setup-machine.sh` reaches for Homebrew first
-and falls back to apt, dnf or apk. Nothing here installs a scheduled job on either platform:
-`install.sh` writes no launchd plist and no systemd unit, so scheduling is yours to arrange.
+**macOS, Linux and Windows all run in CI on every push.** The install matrix runs on
+`ubuntu-latest`, `macos-latest` and `windows-latest`, and Linux additionally installs for real
+and fires the hooks. Windows means Git Bash or WSL, which is what `shell: bash` selects on a
+Windows runner and what a Windows user of these scripts actually has. Native PowerShell is not
+a target: everything here is a shell script and none of it is being ported.
+
+Two things are still macOS-only, and neither is the installer. Conductor is a Mac app, so the
+`.conductor` lanes only mean something there. The `claude` shell wrapper is written in zsh and
+bash cannot source it, so a bash user gets the environment without the wrapper and the
+installer says so as it runs.
+
+Nothing here installs a scheduled job on any platform: `install.sh` writes no launchd plist, no
+systemd unit and no scheduled task. Scheduling is yours to arrange.
 
 **The counts in this README are enforced, the prose is not.** `.claude/verify.sh` check 12
 reads every number back and fails on a mismatch. Nothing checks whether a sentence is still