Validation procedures

Use an isolated environment. CI tests Windows/Linux with Python 3.12 and 3.14; local results cover only the actual interpreter/environment.

python -m pip install --require-hashes -r requirements-dev-lock.txt
python -m pip install --no-deps -e .
python -m ruff check src tests examples scripts
python -m ruff format --check src tests examples scripts
python -m pytest -q
python scripts/http_smoke.py
qinzora demo --present
qinzora demo --continuity

Coverage includes tenant boundaries, key roles, rate windows, replay/activation/expiry/revocation, idempotence, migrations, SDK failures, administration authority/transactions, monitor leases/checkpoints and continuity safeguards. Simulated providers do not prove inference quality. HTTP smoke/process demos exercise loopback services.

The 0.4.1 quality review records response correlation, contract-change races, malformed credential rejection, provider deadlines/output bounds and actual backup restoration checks, along with remaining production work.

Optional environment-specific checks:

python scripts/docker_smoke.py
python scripts/benchmark.py --help
python scripts/administration_smoke.py --model INSTALLED_MODEL

Docker requires an engine. Benchmarks describe only the tested host/workload. Abstention/rejection is not successful AI activation. Real-model continuity activation was verified in a bounded synthetic scenario; see recorded evidence. See distribution for package/docs builds. Passing tests are evidence for covered scenarios, not certification or complete protection.