docs: add guide for running from WSL-2 via Windows interop (#5)

* docs: add guide for running from WSL-2 via Windows interop

sensorwatch is Windows-only (it reads HWiNFO64's named shared memory), but
it can be driven from a WSL-2 shell by launching the Windows build through
interop — useful for WSL-2's persistent SSH and terminal-multiplexer
sessions. Document why the native-Linux path can't work, the Windows-venv
prerequisite, the launch command and the cwd/UNC gotcha, and note that
dev/test still runs natively in WSL-2.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01U3kvTdPBsyec71LpZBHEy7

* docs: correct CI-platform wording, add log_dir + persistence notes

Address PR review feedback:
- Fix "CI runs on Linux" — the CI matrix runs the suite on both Ubuntu and
  Windows (Python 3.12/3.13), matching the README's Testing/CI scope section.
  Flagged by Copilot, the codex reviewer, and the claude reviewer.
- Note that an absolute log_dir in config.toml sidesteps the relative-cwd
  output gotcha (only the relative --config lookup then depends on cwd).
- Ground the "persistent session" rationale: run inside tmux / WezTerm so SSH
  disconnects don't interrupt the capture.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01U3kvTdPBsyec71LpZBHEy7

* docs: reorder so venv creation precedes the launch steps

Move "Creating the Windows venv" to directly after Prerequisites (ahead of
Launch) so the guide reads in setup -> run order; a reader without a venv now
sees how to create it before the launch command references `.venv`. Pure
reordering, no content change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01U3kvTdPBsyec71LpZBHEy7

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>