[Help wanted] Benchmark MCP tool latency on Windows + Linux — first cross-platform validation

[hoainho]

🌟 Before claiming this issue

Two quick steps before you open a PR:

1. ⭐ Star the repository — low-friction signal that you'll follow through
2. 💬 Comment I'll take this (or similar) below — prevents two contributors racing on the same issue

Full policy: CONTRIBUTING.md → How to claim. If a claim is older than 7 days with no PR, you can reclaim it politely.

---

Context

Phase 0 latency targets (p95 under 500ms warm, under 1000ms cold per proposal.md success metrics) will be measured by the maintainer on macOS. We need independent validation on Windows and Linux to catch platform-specific surprises (firewall prompts, named-pipe oddities, stdio buffering).

Where to look

• The npx @nhonh/react-debugger mcp CLI subcommand (built in Phase A)
• The evidence/phase0-latency.json format established by task 1.5

Expected outcome

• evidence/phase0-latency-windows.json from a Windows 11 contributor
• evidence/phase0-latency-linux.json from a Linux contributor (any distro)
• Each file follows the same JSON shape as the macOS baseline
• A short markdown writeup (under 500 words) describing any platform-specific issues encountered

Estimated effort

M (3 to 6h)

How to claim

Comment "@hoainho I will take this" to claim. Note which OS you can test on. PR within 10 days or unclaimed.

Acceptance criteria

• Both platform JSON files committed with valid timing data
• Writeup names: Node version, Chrome version, OS version, network conditions
• If p95 exceeds 500ms on any platform, the cause is documented (network? Chrome SW restart timing? other?)