docs: surface the committed reproducible receipt and add a CI badge

Add a fourth Try it yourself path that reproduces a committed sealed report
byte for byte and fails the gate on a committed broken bundle, so a judge can
see both PASS and BROKEN_PROMISE on files that ship in the repo, with no init,
scaffolding, or key. Document the committed artifacts/verify set and honest
programmatic use of the evaluatePromise function in ADOPTION. Add a CI status
badge to the README.

No product, verifier, evaluator, evidence, or model-boundary behavior changed.

Author: AlexPaiva

ADOPTION.md

@@ -124,6 +124,37 @@ npm run promiseproof -- check \
 
 `check` also accepts a single report with `--report ... --evidence ...`.
 
+## Committed examples
+
+The repository ships a ready evidence set under `artifacts/verify/`, so you can reproduce a result without scaffolding anything first:
+
+- `passing-off.example.json`, `passing-on.example.json`: a passing OFF and ON pair.
+- `passing-gate.report.json`, `passing-gate.report.md`: the sealed gate report for that pair.
+- `broken-off.example.json`: an OFF bundle that breaks the promise.
+
+```bash
+# Regenerate the sealed report byte for byte:
+npm run promiseproof -- check \
+  --report artifacts/verify/passing-gate.report.json \
+  --off artifacts/verify/passing-off.example.json \
+  --on artifacts/verify/passing-on.example.json   # BOUND_AND_REPRODUCED (exit 0)
+
+# Watch a broken bundle fail the gate:
+npm run promiseproof -- gate \
+  --off artifacts/verify/broken-off.example.json \
+  --on artifacts/verify/passing-on.example.json   # BROKEN_PROMISE (exit 2)
+```
+
+## Programmatic use
+
+PromiseProof does not publish an npm package, and the verdict is not hidden behind a service. Inside a checkout, the entire verdict comes from one pure function, `evaluatePromise(evidence)` in `src/shared/evaluator.ts`: no network, no state, no model. This deterministic function is the authority that owns the verdict. The CLI, the GitHub Action, and the hosted browser verifier all call it, which is why their results are identical, and the models never call it or produce its output.
+
+```ts
+import { evaluatePromise } from "./src/shared/evaluator";
+
+const evaluation = evaluatePromise(evidence); // deterministic verdict, clause results, and violations
+```
+
 ## Reports
 
 `verify` and `gate` write two files to `--out`:

README.md

@@ -8,6 +8,7 @@
 
 A human approves the exact patch. An unchanged deterministic verifier decides whether the promise is actually fixed.
 
+[![CI](https://github.com/AlexPaiva/PromiseProof/actions/workflows/submission-hardening.yml/badge.svg)](https://github.com/AlexPaiva/PromiseProof/actions/workflows/submission-hardening.yml)
 [![OpenAI Build Week 2026](https://img.shields.io/badge/OpenAI-Build_Week_2026-10a37f)](https://openai.com)
 [![License: MIT](https://img.shields.io/badge/License-MIT-3f6bf0.svg)](LICENSE)
 [![TypeScript](https://img.shields.io/badge/TypeScript-strict-3178c6)](https://www.typescriptlang.org/)
@@ -116,7 +117,19 @@ Three ways in, none of them require an API key.
     output_directory: artifacts/promiseproof
 ```
 
-The step fails on `BROKEN_PROMISE` (exit 2) and still leaves `report.json` and `report.md` behind. Full CLI, exit codes, and exact scope are in [PromiseProof Verify](#try-promiseproof-verify) below.
+The step fails on `BROKEN_PROMISE` (exit 2) and still leaves `report.json` and `report.md` behind.
+
+**4. Reproduce a sealed receipt, with nothing to generate first.** The repo ships a committed report and the evidence it was computed from. After `npm ci`, regenerate that report byte for byte:
+
+```bash
+npm run promiseproof -- check \
+  --report artifacts/verify/passing-gate.report.json \
+  --off artifacts/verify/passing-off.example.json \
+  --on artifacts/verify/passing-on.example.json
+# BOUND_AND_REPRODUCED (exit 0)
+```
+
+Swap in the committed `artifacts/verify/broken-off.example.json` and `gate` returns `BROKEN_PROMISE` (exit 2). No `init`, no scaffolding, no key. Full CLI, exit codes, and exact scope are in [PromiseProof Verify](#try-promiseproof-verify) below.
 
 ## What was built in one Build Week