How the backend side consumes the Boardex UI contract (event stream, command API, JSON Schema) without ever editing it. Use when working on servers/boardex-runner, deciding which event to emit, validating events against the schema, or when a needed…
Set up the Python venv and run the Boardex server test suites (boardex-core, boardex-target, boardex-logic, boardex-runner). Use when changing anything under servers/, when asked to run server tests, or when pytest/imports fail for the Python packages.
Run servers/boardex-runner (the real §5 runner) and prove conformance — start it in fake-bench or live-bench mode, point the UI and the parameterized mock-runner suite at it via RUNNER_BASE_URL, record a §10.3 fixture, and validate the recording. Use when…
Add support for new lab hardware to Boardex — a new probe backend (J-Link, OpenOCD), logic analyzer, peripheral inspector for a silicon family, or a whole new domain server. Use when adding hardware/vendor/backend support under servers/ or writing a new…
Drive real bench hardware through the boardex-target and boardex-logic MCP servers — flash firmware, stream RTT, capture and decode buses. Use when asked to flash a board, run a bring-up checkpoint, capture I2C/SPI/UART, debug RTT/serial output, or otherwise…
Drive the Boardex UI against the mock runner in a headless browser to verify a change end-to-end.