catapult-verifiers

# From the Catapult repository checkout:
pip install ./packages/catapult-verifiers

# In another terminal, from the repository root. This prints the key once.
bun run dev

export FACADE_URL=http://127.0.0.1:8787
export FACADE_API_KEY='cgk_…'
vf-eval catapult-verifiers

bun run dev starts the local facade on port 8787 and prints a bootstrap API key. Set that key as FACADE_API_KEY. The default deterministic opponent makes local rollouts fully offline: no model-provider key or spend is required. The environment creates and cleans one room per rollout and never exposes operator results, seeds, or RNG data to the model.

Releases

Releases are deliberately tag-only. After a release PR updates version and is merged to main, create and push the corresponding v* tag:

git tag v0.1.0
git push origin v0.1.0

That tag starts .github/workflows/release.yml, which builds the source distribution and wheel and publishes them to PyPI. It has no manual or branch trigger and uses no package token or stored secret.

Before the first tag, an owner must create the catapult-verifiers project on PyPI (or configure the publisher during first publish) and add a Trusted Publisher with these exact values:

Owner: origami-research
Repository: catapult-research
Workflow: release.yml
Environment: pypi

GitHub must also have the pypi environment. Its protection rules are the approval gate for publication.

Optional: Verifiers Environments Hub

PyPI publication does not push to the Verifiers Environments Hub. To publish there separately, authenticate with the Prime CLI and push this package:

uv tool install prime
prime login
prime env push --path packages/catapult-verifiers