# Windows resource monitor comparison

Base: 7fcec368cb13ce14cad8d7d4f4aca9b3f9a041e0
Head: 587035624935bd4564f91a8579a954fb267106e3

1. In separate checkouts, install dependencies with `vp i` and build the web client with `vp run --filter @t3tools/web build`.
2. From each repository root, build the Windows x64 monitor exactly as the release workflow does:
   `cargo xwin build --locked --release --manifest-path native/resource-monitor/Cargo.toml --target x86_64-pc-windows-msvc`.
3. Inspect each executable with `llvm-objdump -p`. Copy those exact executables to Windows Server 2025. The hashes in runtime-proof.json identify the executables tested.
4. Uninstall the official signed Visual C++ x64 redistributable with `/uninstall /quiet /norestart`. Verify System32/vcruntime140.dll does not exist and `where.exe vcruntime140.dll` finds nothing.
5. Run `probe-monitors.ps1 -BaseMonitor <base-executable> -HeadMonitor <head-executable>` with both executables in folders containing no runtime DLLs. It closes stdin, reads stdout and records the exit code.
6. On Windows, in each corresponding app checkout, use the standalone official Node 26.13.1 executable to start the real server: `node apps/server/src/bin.ts serve --base-dir <fresh-isolated-home> --host 0.0.0.0 --port <port> --no-browser`. Set `T3CODE_DEV_SEED=0` and `T3CODE_RESOURCE_MONITOR_PATH=<corresponding-built-executable>` in each server's environment. The web client is served from that checkout's apps/web/dist.
7. Open the server in Chromium, pair through the app, choose Start without an agent, then open `/settings/diagnostics`. Both homes start empty; no production data or real agent is used.
8. At a 1440x1500 CSS viewport in the light theme, scroll the Settings content 75 pixels. Record the same scroll and hold on both sides. Screenshots crop the Settings content at identical coordinates, without changing app content.

Observed without the runtime: base exits 0xC0000135 and Diagnostics reports NATIVE UNAVAILABLE, zero counters, a 5000ms handshake timeout, and no sidecar. Head exits 0 with its JSON hello and Diagnostics reports NATIVE HEALTHY, live memory/process/I/O telemetry, No reported errors, and sidecar 0.1.0 with a PID.

The web assets were built on Linux and copied to their respective Windows checkouts; the servers and native monitors ran on Windows. The final release installer/archive and Windows ARM64 were not exercised.
