interaction-check
This page documents 1.0.0. Check the release status for registry availability.
Version 1.0.0 preserves Unicode JSON reports even when the terminal uses ASCII or Windows-1252. See the CLI/report compatibility contract.
A small Python command-line tool that replays semantic JSON event sequences against an explicitly selected local adapter. Python 3.10+; zero runtime dependencies. Licensed under MIT OR Apache-2.0. The 1.x CLI and report compatibility policy is linked above.
Installation
Install the release from PyPI:
python -m pip install 'interaction-check==1.0.0'
Use an exact version and run your adapter regressions before upgrading.
Use a virtual environment. On Windows, the same command works with py -m pip.
For other distribution options and current publication status, see the
project README.
Usage
interaction-check --version
interaction-check --failure-dir failures --trace --report report.json scenario.json -- path/to/adapter
The adapter is a trusted program you select; it receives events as JSONL and returns states. Expected states are never sent to it. Each scenario starts a fresh process. The runner is not a sandbox and does not download or discover adapters automatically.
--failure-dir creates a new directory containing numbered JSON scenarios through
the first state mismatch. Expectations stay unchanged. These are checked prefixes, not
automatically minimized or independently verified reproductions. Re-run an export with
the same adapter revision. Crashes, timeouts and malformed protocol replies do not
produce a guessed state-mismatch scenario.
The installed wheel contains the runner and its licenses. Examples and application adapters remain in the repository and may have their own dependencies. The separate Rust library edit-session is not required.
- Scenario and adapter protocol
- First example: no application or extra packages
- Real callbacks and Mermaid diagrams
- Native tests or replay?
- Worked XState example
- Moving a useful scenario into a native test
- Measured benefits and costs
If a normal project test is simpler, keep that test. Replay is useful when sharing an event sequence and a consistent report earns the adapter and runner maintenance cost.
1 maintainer
Metadata
1 maintainer
Release files for interaction-check 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| interaction_check-1.0.0.tar.gz | 72.1 kB | With provenance | Details for interaction_check-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| interaction_check-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for interaction_check-1.0.0-py3-none-any.whl |
Total release size: 85.6 kB
Release files / interaction_check-1.0.0.tar.gz
| Download URL | interaction_check-1.0.0.tar.gz |
|---|---|
| Size | 72.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2539094bebf83fa9b6d6f75bde70aa93dd48e6631ec9dd576335dfce1ff26f55
|
|
BLAKE2b-256 checksum How to use checksums |
6ed803c3a2439d47fe5634762eba9907672a446b2220c30dfde12b2412a10f97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logRelease files / interaction_check-1.0.0-py3-none-any.whl
| Download URL | interaction_check-1.0.0-py3-none-any.whl |
|---|---|
| Size | 13.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3b5076832bbcbb0eae9129296ec8392ee19a98f1900e2eee1e8edc9e5f894a96
|
|
BLAKE2b-256 checksum How to use checksums |
8083b53ba8ba3e583ada7eaa1d34b35bed61fe4dc93f793384217375557a0de7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logSecurity for interaction-check 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for interaction_check-1.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
