Skip to content

Downstream Smoke Evidence

Stable-core claims need evidence that Entroping works outside its own checkout. The downstream smoke harness creates a temporary external API project, starts a local fixture server, and runs Entroping through the public CLI against that external project.

Run it from the Entroping repository:

uv run python scripts/downstream_smoke.py

The alpha release gate runs this smoke by default when Hurl is available:

scripts/release_check.sh --require-live-demo

Use scripts/release_check.sh --skip-downstream-smoke only for local diagnostics when the downstream fixture is not the target of the check.

For machine-readable output:

uv run python scripts/downstream_smoke.py --format json

To keep reviewed artifacts for a release or investigation:

uv run python scripts/downstream_smoke.py --artifact-dir /tmp/entroping-downstream-proof

The artifact directory receives:

  • downstream-smoke-evidence.json
  • run-latest.json
  • run-latest.html
  • junit.xml

What It Proves

  • Entroping can be invoked through uv run --project <repo-root> entroping ... while the current working directory is an external project.
  • The external project owns its own qanstitution.yaml, Hurl test, reports, and .entroping/ runtime state.
  • Hurl remains the API assertion executor.
  • QAnstitution gates are injected into temporary execution copies.

What It Does Not Prove

This harness does not satisfy real downstream user feedback. It is a local, maintainer-controlled integration proof. Stable-core remains blocked until at least one project outside this repository runs Entroping, reports friction, and that feedback is recorded as release evidence.

Use DOWNSTREAM_FEEDBACK_KIT.md to collect that external feedback without secrets, raw traffic, private URLs, or proprietary API payloads.

It also does not prove package-index installation. The package-index blocker still requires TestPyPI/PyPI Trusted Publishing proof.