docs: Add SSH operations rule and deployment script

Added SSH operations guidelines to directives.md:
- NEVER use Git for Windows SSH for operations
- Use native OpenSSH or PuTTY tools (plink, pscp)
- Git for Windows SSH has compatibility issues with some servers
- Use full path to system SSH when needed

Created deploy-bat-files-to-ad2.ps1:
- Deploys DEPLOY.BAT and UPDATE.BAT to AD2
- Preserves CRLF line endings for DOS compatibility
- Verifies file content matches after copy
- Files auto-sync to NAS via AD2's scheduled task

Reason: NAS SSH authentication failed after restart, established
AD2 deployment path as reliable alternative that preserves line endings.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

directives.md

@@ -328,6 +328,12 @@ Me: [Proceeds or requests fixes based on validation]
 - Always use `-ErrorAction` for error handling
 - Clear status markers in output
 
+### SSH Operations
+- **NEVER use Git for Windows SSH for operations**
+- Use native OpenSSH (Windows 10+) or PuTTY tools (plink, pscp)
+- Git for Windows SSH has compatibility issues with some servers
+- Use full path to system SSH: `C:\Windows\System32\OpenSSH\ssh.exe`
+
 ### Security Standards
 - Never hardcode credentials
 - Never commit `.env` files