From 6f74df83ba719fb930e809e78d270cee2301a600 Mon Sep 17 00:00:00 2001 From: Orca Worker Date: Sat, 5 Sep 2026 18:46:36 -0700 Subject: [PATCH] docs(windows): state the CIM scan as the relay's normal path, not a fallback No released relay carries the optional `windows-process-tree.node` addon -- release-cut.yml has zero references to it and only dev-channel-win-build.yml builds it -- so the PowerShell CIM scan is what every SSH host runs. The call-site docstring read as a conditional fallback standalone. Comment-only. --- src/relay/windows-port-scan.ts | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/relay/windows-port-scan.ts b/src/relay/windows-port-scan.ts index 4ed53c96ecb..f99fce4a087 100644 --- a/src/relay/windows-port-scan.ts +++ b/src/relay/windows-port-scan.ts @@ -128,8 +128,9 @@ export function resetWindowsPortScanDiagnosticsForTests(): void { * * Names are optional data — the panel renders host/port/pid without them — so a * host that cannot read the table keeps its rows. This shares whatever scan the - * table already runs rather than avoiding one: without the native addon that - * scan is itself a `powershell.exe` CIM query, just not a second one. + * table already runs rather than avoiding one, and on a relay that scan is a + * `powershell.exe` CIM query -- no released relay carries the native addon, so + * that is the path every SSH host takes, not a fallback. * See docs/reference/windows-process-enumeration.md. * * Only `name` is read here, so this wants `readWindowsProcessIdentityTable`