feat(windows): enable dashboard /chat tab via ConPTY (win_pty_bridge) + tests

[teknium1]

Summary

Native Windows users currently can't use the dashboard's /chat tab — the POSIX pty_bridge.py import fails on import (no fcntl / termios), and /api/pty cleanly refuses with a "use WSL2" banner. This PR enables it end-to-end via ConPTY.

Salvages the design from #39913 (@JoelJJohnson) with @Nea74's converging shape from #40022 noted (same WinPtyBridge module + same WebPtyBridge as PtyBridge import branch — credited in commit trailers + AUTHOR_MAP). Adds the test coverage both PRs were missing, plus the live-on-Windows validation those PRs explicitly couldn't run.

What's in here

1. hermes_cli/win_pty_bridge.py (from #39913) — a pywinpty-backed WinPtyBridge with the exact public surface /api/pty consumes: spawn / read / write / resize / close / is_available + PtyUnavailableError. Same PtyProcess.spawn(dimensions=(rows, cols)) API already shipping in tools/process_registry.py, so no new pywinpty surface area. pywinpty is already a declared win32 dep (pyproject.toml).

2. hermes_cli/web_server.py import branch (from #39913) — if sys.platform.startswith("win"): from hermes_cli.win_pty_bridge import WinPtyBridge as PtyBridge / else: from hermes_cli.pty_bridge import PtyBridge. POSIX path is byte-for-byte unchanged (verified by diff).

3. README caveat removal (from #39913) — the "the only Hermes feature that currently needs WSL2 is the dashboard chat pane" line is now wrong.

4. NEW: tests/hermes_cli/test_win_pty_bridge.py — 22 tests mirroring the POSIX test_pty_bridge.py layout: spawn / io / resize / close / env / clamp, all @windows_only except the cross-platform fallback surface (PtyUnavailableError exists, off-Windows spawn → PtyUnavailableError). 21 pass + 1 platform-skip on Windows.

5. NEW: tests/hermes_cli/test_web_server_pty_import.py — asserts web_server.PtyBridge is WinPtyBridge on win32, is PtyBridge (POSIX) elsewhere, both PtyUnavailableError types match the same module, and a source-text check pinning the platform-branched import shape so a future refactor can't quietly collapse it back to a POSIX-only import.

6. NEW: scripts/release.py AUTHOR_MAP entries — both authors use plain (non-noreply) emails, so the release-note generator needs explicit mappings: josephjohnson.joel@gmail.com → JoelJJohnson, andreas@schwarz-ketsch.de → Nea74. Resolved via gh api 'repos/.../commits/<sha>' against the original commits.

Live validation on Windows

Ran on native Windows 11 (Python 3.11, pywinpty 2.0.15) against hermes dashboard --no-open --skip-build driving a Python WS client at ws://127.0.0.1:<port>/api/pty?token=…:

• ✅ TUI renders through ConPTY — 7306 bytes of ANSI streamed back. First chunk includes xterm mode set, screen clear, and \x1b]0;C:\Program Files\nodejs\node.EXE\x07 title-bar OSC → _make_tui_argv resolved node correctly on Windows, ConPTY bootstrapped the spawned hermes --tui (node entry.js) without issues, xterm.js would render it cleanly. Server log: INFO hermes_cli.web_server: pty accepted peer=127.0.0.1 mode=loopback cred=token.
• ✅ Resize escape forwarded — sent ESC[RESIZE:99;41] mid-stream, no exception, server-side setwinsize(rows=99, cols=41) accepted, more bytes streamed back.
• ✅ No orphaned processes — closing the WS killed all node.exe / pywinpty agent children cleanly (0 new orphans). pywinpty's terminate(force=True) plus the existing reap path are sufficient on Windows; no extra taskkill /T /F machinery needed for this code path.
• ✅ pywinpty present — pywinpty==2.0.15 already installed in the Hermes venv on a fresh uv install; no extra dep work.

Read-fidelity caveat (documented, acceptable)

pywinpty returns decoded str from read(), so a multibyte UTF-8 character can theoretically split across reads when the bridge re-encodes it to bytes. xterm.js tolerates the rare replacement char; called out in a comment in win_pty_bridge.py:read(). Author of #39913 flagged this honestly — no fix needed, just know it's there.

What this closes / supersedes

• Supersedes feat(windows): enable dashboard chat tab via ConPTY (win_pty_bridge) #39913 (same author, same diff — this is the salvage)
• Supersedes fix: enable dashboard PTY chat on native Windows #40022 (@Nea74, near-duplicate design — credited as co-author)
• Supersedes [codex] Fix Windows dashboard chat PTY #37141 (@Cosmic-Construct, wrong module shape — jams Windows logic into the POSIX bridge)
• Supersedes feat: add Windows backend for dashboard PTY bridge #21982 (@bgmbgm94, stale May-2026 attempt — pre-dates pywinpty being a declared dep)
• Supersedes the import-guard-only graceful-degradation PRs fix: keep dashboard importable without Unix PTY modules #21770 / fix(windows): guard fcntl/termios import + add __main__.py launcher #21465 — those are obviated by an actual ConPTY backend, but worth closing with credit.

Test plan

• ✅ pytest tests/hermes_cli/test_win_pty_bridge.py — 21 passed, 1 skipped (Windows host)
• ✅ pytest tests/hermes_cli/test_web_server_pty_import.py — 3 passed, 1 skipped (Windows host)
• ✅ pytest tests/hermes_cli/test_web_server.py tests/hermes_cli/test_pty_bridge.py -k "pty or chat" — 19 passed, 13 skipped, no regressions
• ✅ End-to-end live drive of /api/pty against a running dashboard (see "Live validation on Windows" above)
• ⏳ Linux CI will exercise the POSIX side of test_web_server_pty_import.py (Windows-side asserts skip there and vice versa)

[github-actions]

🔎 Lint report: fix/windows-dashboard-pty-salvage vs origin/main

ruff

Total: 0 on HEAD, 0 on base (➖ 0)

🆕 New issues: none

✅ Fixed issues: none

Unchanged: 0 pre-existing issues carried over.

ty (type checker)

Total: 10419 on HEAD, 10406 on base (🆕 +13)

🆕 New issues (12):

Rule	Count
unresolved-attribute	6
invalid-argument-type	3
unresolved-import	2
unused-type-ignore-comment	1

First entries

hermes_cli/win_pty_bridge.py:171: [unresolved-attribute] unresolved-attribute: Attribute `terminate` is not defined on `None` in union `Unknown | None`
tests/hermes_cli/test_win_pty_bridge.py:227: [invalid-argument-type] invalid-argument-type: Argument to function `_clamp` is incorrect: Expected `int`, found `float`
tests/hermes_cli/test_win_pty_bridge.py:225: [invalid-argument-type] invalid-argument-type: Argument to function `_clamp` is incorrect: Expected `int`, found `Literal["not-a-number"]`
tests/hermes_cli/test_win_pty_bridge.py:224: [invalid-argument-type] invalid-argument-type: Argument to function `_clamp` is incorrect: Expected `int`, found `None`
hermes_cli/win_pty_bridge.py:26: [unused-type-ignore-comment] unused-type-ignore-comment: Unused blanket `type: ignore` directive
tests/hermes_cli/test_web_server_pty_import.py:22: [unresolved-import] unresolved-import: Cannot resolve imported module `pytest`
tests/hermes_cli/test_win_pty_bridge.py:21: [unresolved-import] unresolved-import: Cannot resolve imported module `pytest`
hermes_cli/win_pty_bridge.py:150: [unresolved-attribute] unresolved-attribute: Attribute `write` is not defined on `None` in union `Unknown | None`
hermes_cli/win_pty_bridge.py:112: [unresolved-attribute] unresolved-attribute: Attribute `isalive` is not defined on `None` in union `Unknown | None`
hermes_cli/win_pty_bridge.py:127: [unresolved-attribute] unresolved-attribute: Attribute `read` is not defined on `None` in union `Unknown | None`
hermes_cli/win_pty_bridge.py:106: [unresolved-attribute] unresolved-attribute: Attribute `pid` is not defined on `None` in union `Unknown | None`
hermes_cli/win_pty_bridge.py:160: [unresolved-attribute] unresolved-attribute: Attribute `setwinsize` is not defined on `None` in union `Unknown | None`

✅ Fixed issues: none

Unchanged: 5439 pre-existing issues carried over.

Diagnostics are surfaced as warnings — this check never fails the build.