feat: Add Windows-native test infrastructure with batch execution and compatibility patches

[jianlins]

What does this PR do?

This PR adds Windows-native test infrastructure to enable running the full hermes-agent test suite natively on Windows without requiring WSL. It includes:

• New Windows-specific test configuration and runner
• Batch execution support for parallel test execution on Windows
• Compatibility patches for Windows file system and path handling
• Documentation with setup instructions and troubleshooting guide

The changes enable developers on Windows to run the full ~3000-test suite natively, improving cross-platform development experience.

Related Issue

No specific issue filed. This addresses the need for native Windows testing support.

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• ests/test_windows_native.py - New Windows-specific test suite with batch execution and compatibility tests
• ests/conftest.py - Updated to support Windows-native test configuration
• .gitignore - Added �uild/ directory
• README_WINDOWS_TESTING.md - Setup instructions and troubleshooting guide for Windows testing

How to Test

1. On Windows, activate the virtual environment: �env\Scripts\activate
2. Run the Windows-native tests: pytest tests/test_windows_native.py -v
3. Run the full test suite: pytest tests/ -q
4. Verify batch execution works: python batch_runner.py --help

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (ix(scope):, eat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: Windows 11

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — Added README_WINDOWS_TESTING.md
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — Windows-specific feature
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

Screenshots / Logs

Test output showing successful Windows-native execution:
$ pytest tests/test_windows_native.py -v ... 20 tests passed in 3.45s

Native Windows CI Pipeline: GitHub Actions Run #24335204580 - Full test suite passing on Windows 11 native environment.

[alt-glitch]

Related: #12317 (Windows native compat) and #16212 (Windows path normalization) — overlapping Windows support effort. Consider coordinating.

[teknium1]

Thanks for this — appreciate the work. We're closing the entire cluster of open native-Windows PRs (44 of them spanning installer, terminal routing, file ops, gateway PID handling, encoding, docs, and more) because the surface area needs a designed, consolidated approach rather than piecemeal merges. Cherry-picking individual fixes keeps leaving inconsistencies and we'd rather land Windows support properly, in one coherent pass.\n\nYour PR is catalogued in our internal Windows support plan. When we pick this back up (soon), we'll mine every PR in the cluster for its fix shape and credit all contributors whose work informs the final patch via lines. Watch for the consolidating PR and feel free to chime in with context on the specific failure mode you were hitting.\n\nClosing for now, not as a rejection of the fix — just queueing it for the designed rollout. Thanks again.