Metadata-Version: 2.5
Name: catapult-verifiers
Version: 0.1.0
Summary: Stateful Verifiers environment for Catapult games
Project-URL: Homepage, https://github.com/origami-research/catapult-research
Project-URL: Repository, https://github.com/origami-research/catapult-research
Project-URL: Issues, https://github.com/origami-research/catapult-research/issues
License-Expression: LicenseRef-Proprietary
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: License :: Other/Proprietary License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Requires-Python: >=3.11
Requires-Dist: datasets>=2.0
Requires-Dist: verifiers<0.2,>=0.1.9
Provides-Extra: tinker
Requires-Dist: tinker-cookbook[verifiers]>=0.5; extra == 'tinker'
Requires-Dist: tinker>=0.23; extra == 'tinker'
Description-Content-Type: text/markdown

# catapult-verifiers

```bash
# 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:

```bash
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:

```text
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:

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