A reactive notebook for Python — run reproducible experiments, query with SQL, execute as a script, deploy as an app, and version with git. Stored as pure Python. All in a modern, AI-native editor.
Host protocol conformance tests
Python tests for hosts implementing the host protocol. The suite uses HTTP and SSE and does not import marimo.
Start a host in a disposable workspace (for marimo, use
marimo edit), then run this from the repository root:
uv run --locked --project protocols/host/conformance \
pytest protocols/host/conformance --record /path/to/hosts-v1/host.json
The caller starts and stops the host. Operation tests create scratch notebooks
and clean up their own resources. Without --record, only offline schema,
fixture, and checker tests run; these also run in CI via make host-protocol-check.
Scratch checks require the created notebook to permit notebook.delete.
That permission is only known after creation. If it is unavailable, the suite
skips the remaining scratch checks and reports the notebook ID for manual
cleanup in the disposable workspace.
--slowincludes idle ping checks.--host-timeout 30allows longer waits for a host's responses and events.--require-operation runtime.runfails if that capability is missing. Repeat this option to require more operations; otherwise unavailable operations skip.
The suite covers discovery records, authentication, snapshots, filtering, resumption, document hashes, and selected notebook and runtime operations. It does not yet cover opening an editor, answering host decisions, or unsupported operation responses. Retention expiry, external store changes, shutdown, and transport failures also need implementation tests. WebSocket transport is outside this contract.
Experimental features have separate conformance tests. Check the stable contract and all experimental fixtures together with:
uv run --locked --project protocols/host/conformance \
pytest -c protocols/host/conformance/pyproject.toml \
protocols/host/conformance protocols/host/experimental
The base probes continue to ignore experimental events. Each feature's suite validates its payloads against the composed contract.