test(windows-smoke): check the local server by connecting when sockets can't be listed #52

Merged

jared merged 1 commits from fix/smoke-listen-check into main

2026-11-09 23:10:17 -05:00

Author	SHA1	Message	Date
jaredandClaude Opus 5.5	13ebba77c0	test(windows-smoke): check the local server by connecting when sockets can't be listed The `windows` runner session can't enumerate sockets: Get-NetTCPConnection and netstat come back empty even for the DevTools port the script is connected to, so "local server listening" failed on every run (main too, run 3145) and masked real regressions. When the socket list is empty, test what cinny #43 is about directly: the server must accept a connection on 127.0.0.1:44548 and refuse it on every non-loopback IPv4 address of the machine. The list-based check is kept for runners where it works. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA	2026-11-09 21:41:43 -05:00

Author

SHA1

Message

Date

jaredandClaude Opus 5.5

13ebba77c0

test(windows-smoke): check the local server by connecting when sockets can't be listed

The `windows` runner session can't enumerate sockets: Get-NetTCPConnection
and netstat come back empty even for the DevTools port the script is
connected to, so "local server listening" failed on every run (main
too, run 3145) and masked real regressions.

When the socket list is empty, test what cinny #43 is about directly:
the server must accept a connection on 127.0.0.1:44548 and refuse it on
every non-loopback IPv4 address of the machine. The list-based check is
kept for runners where it works.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA

2026-11-09 21:41:43 -05:00