lock line endings and expand Windows lint to .ps1

Cross-platform audit for medical-grade rigor:

- Add .gitattributes with explicit eol=crlf for .bat/.cmd/.ps1 so a
  Mac contributor's commit can't silently strip CR bytes and break
  start.bat / start-local-agent.ps1 on Windows. .command / .sh are
  pinned to LF since macOS double-clicks on them.
- Strip em dash from start-local-agent.ps1 (added in an earlier
  commit). Windows PowerShell 5.1 can't read BOM-less UTF-8 reliably,
  so Windows launcher scripts follow the same ASCII rule as .bat.
- Extend the Windows CI lint to cover scripts/dev/*.ps1 and
  scripts/windows/*.ps1 with the same ASCII / CRLF / NUL checks.

Author: ouyyyyang

.gitattributes

@@ -0,0 +1,27 @@
+# Default: let Git decide (text auto-detect, normalize to LF in repo).
+* text=auto
+
+# Windows launchers MUST stay CRLF regardless of client core.autocrlf.
+# cmd.exe is picky about line endings, and PowerShell on Windows expects
+# them too. Without this, a Mac contributor's commit can silently strip
+# CR bytes and break start.bat on every Windows machine.
+*.bat  text eol=crlf
+*.cmd  text eol=crlf
+*.ps1  text eol=crlf
+
+# macOS / Linux launchers MUST stay LF. Double-click .command files break
+# on macOS if they ever get CRLF endings.
+*.command text eol=lf
+*.sh       text eol=lf
+
+# Binary types - never touch.
+*.png binary
+*.jpg binary
+*.jpeg binary
+*.gif binary
+*.ico binary
+*.pdf binary
+*.zip binary
+*.tar binary
+*.gz binary
+*.node binary

.github/workflows/windows-smoke.yml

@@ -26,42 +26,56 @@ jobs:
         shell: pwsh
         run: npm ci
 
-      - name: Lint .bat launchers
+      - name: Lint Windows launchers (.bat / .ps1)
         shell: pwsh
         run: |
           $ErrorActionPreference = "Stop"
-          $bats = @("start.bat", "stop.bat")
+          $targets = @(
+            "start.bat", "stop.bat",
+            "scripts/dev/start-local-agent.ps1",
+            "scripts/dev/stop-local-agent.ps1",
+            "scripts/windows/capture-screen.ps1"
+          )
           $failed = $false
-          foreach ($bat in $bats) {
-            $bytes = [System.IO.File]::ReadAllBytes($bat)
+          foreach ($target in $targets) {
+            if (-not (Test-Path $target)) {
+              Write-Host "skip missing: $target"
+              continue
+            }
+            $bytes = [System.IO.File]::ReadAllBytes($target)
             $text  = [System.Text.Encoding]::ASCII.GetString($bytes)
 
-            # 1. Pure ASCII (no UTF-8 multi-byte sequences that would
-            #    be misread under Chinese Windows code page 936).
+            # 1. Pure ASCII. cmd.exe on zh-CN runs code page 936 and will
+            #    misdecode UTF-8 multi-byte sequences in .bat files,
+            #    producing '文件名、目录名或卷标语法不正确'. Applying the
+            #    same rule to .ps1 keeps us consistent and protects
+            #    Windows PowerShell 5.1 hosts that can't read BOM-less
+            #    UTF-8 reliably.
             foreach ($b in $bytes) {
               if ($b -gt 0x7f) {
-                Write-Error "$bat contains non-ASCII byte 0x$("{0:X2}" -f $b) — cmd.exe on zh-CN will fail to parse it"
+                Write-Error "$target contains non-ASCII byte 0x$("{0:X2}" -f $b) - use ASCII-only for Windows compatibility"
                 $failed = $true
                 break
               }
             }
 
-            # 2. CRLF line endings — LF-only .bat files misbehave on some
-            #    cmd.exe versions.
+            # 2. CRLF line endings. LF-only .bat files confuse some cmd.exe
+            #    versions, and Windows PowerShell 5.1 parses CRLF more
+            #    reliably than LF.
             if ($text -notmatch "`r`n") {
-              Write-Error "$bat has no CRLF line endings"
+              Write-Error "$target has no CRLF line endings"
               $failed = $true
             }
 
-            # 3. No Unix-style /dev/null redirection — cmd.exe would create
+            # 3. No Unix-style /dev/null redirection. cmd.exe would create
             #    an actual file named 'null' under a 'dev' directory.
             if ($text -match "/dev/null") {
-              Write-Error "$bat contains Unix-style '/dev/null' — use 'NUL' instead"
+              Write-Error "$target contains Unix-style '/dev/null' - use 'NUL' instead"
               $failed = $true
             }
           }
           if ($failed) { exit 1 }
-          Write-Host "All .bat files passed ASCII / CRLF / NUL lint."
+          Write-Host "All Windows launchers passed ASCII / CRLF / NUL lint."
 
       - name: Run start.bat end-to-end
         shell: cmd

scripts/dev/start-local-agent.ps1

@@ -219,7 +219,7 @@ $process = Start-Process `
     -WindowStyle Hidden `
     -PassThru
 
-# Do NOT write $process.Id to $PidFile here — $process is the launcher
+# Do NOT write $process.Id to $PidFile here - $process is the launcher
 # PowerShell wrapper, not the node agent. server.ts writes its own real
 # PID once it binds the port. Writing the wrapper PID makes the agent's
 # ensureSingleInstance() see a "live" PID and exit immediately.