# Platforms

## Claim

The tooling has repeatable Linux test runs. Windows use appears in an operator account and field manual, but no repeatable Windows suite is recorded. macOS and Raspberry Pi are not tested.

This is about the machine that runs the agent and Bootscry code, separate from the machine the KVM controls. KVM input is independent of the target operating system in principle; this project has not tested every target OS.

## What supports it

- The NAS recovery began from a Windows workstation, according to the operator's account. See [nas-recovery](nas-recovery.md).
- The field manual documents a Windows line-ending fault: commands built on the Windows workstation carried `\r\n` into the keystroke stream. The documented fix was newline cleanup and chunked console payloads.
- The unit tests run on Linux: `tests/test_glkvm_client.py` and `tests/test_glkvm_mock.py`, against the mock server in `tests/glkvm_mock.py`.
- The live suites (`scripts/kvm/live_test.py`, `live_mouse_test.py`, `live_typing_test.py`) ran on Linux against a real Comet wired to a Linux test machine. Results are on [mouse-accuracy](mouse-accuracy.md) and [typing](typing.md).
- Windows-specific code here: `scripts/kvm/ok.cmd` launches the health check, and `src/bootscry/kvm_tool.py` has Windows key helpers (Ctrl+Alt+Del, Task Manager, Shift+F10 for Windows Setup). The key helpers send input to a Windows target. They say nothing about the host the agent runs on.
- The code reads and writes files with `pathlib` and talks to the Comet over HTTP and a WebSocket. That is a design note, not a test result.

## What is not done

- No unit or live suite has been run on macOS or on a Raspberry Pi.
- The Windows evidence is the overnight run and the manual's post-mortem. There is no repeatable Windows test run recorded on these pages. The full unit suite has not been recorded as run on Windows.
- To claim macOS, we need to run the unit tests and one live suite from a Mac, and record the versions.
- To claim Raspberry Pi, we need the same on a Pi, plus a check that local OCR (Tesseract, and RapidOCR if used) runs at a usable speed on that hardware. The OCR speeds on the other pages come from a server, not a Pi.
- Until then both are labelled planned.

## Limits

- One operator, one Windows workstation, one Linux server. No other host has been tried.
- The manual is the operator's own post-mortem, so Discovery 4 is documented, not independently confirmed.

## Where the raw documentation lives

The private field manual, `scripts/kvm/`, and `tests/` are the source records. The manual needs redaction before public release.