jolt/test/conformance/README.md
Yogthos 45876998ad Docs: Chez-only, drop the Janet-era references and obsolete migration notes
Bring the docs in line with the actual implementation now that Chez is the sole
substrate.

Deleted the migration/spike/handoff artifacts that only documented the Janet
era or the port effort: the port plan, phase-0 and foundational-runtime spike
writeups (+ the stray root-level copy), the self-hosting design notes, the
architecture-refactor plan, and spike/chez/RESULTS.md.

Rewrote the current reference docs against the Chez facts: building-and-deps and
tools-deps (no jpm/build step — bin/joltc off the checked-in seed, deps via
jolt.deps into ~/.jolt/gitlibs), libraries (SQLite is built-in jdbc.core over
libsqlite3, not a Janet driver), the conformance/spec test-flow docs (the Chez
corpus runner + certify, no .janet harnesses), and the transient / type-hint /
seed-overlay design notes (Chez representations: mutable transients, flat
copy-on-write vectors, HAMT maps, the seed/overlay twin). Fixed the README
collections line (vectors aren't 32-way tries) and added the ffi/transient gate
targets. rfc 0001's numerics open-question is resolved (the Scheme tower).

Renamed the built-in HTTP adapter to jolt.http.server only (dropped the
ring-janet.adapter alias — a Janet-era name).
2026-06-22 09:05:35 -04:00

63 lines
3.2 KiB
Markdown

# Conformance: certifying the corpus against reference Clojure
> **See [SPEC.md](SPEC.md)** for the full host-neutral language-spec contract: the
> corpus schema, conformance levels, the feature profile, and how to host jolt on a
> new runtime. This README covers the certification tooling specifically.
The corpus (`test/chez/corpus.edn`) is jolt's host-neutral behavioral suite — one
row per case: `{:suite :label :expected :actual}`, where `:actual` is a Clojure
source expression and `:expected` its result (or `:throws`). The runtime harness
(`host/chez/run-corpus.ss`, invoked by `make corpus`) replays it on Chez and
compares by value-equality.
Every `:expected` is sourced from reference JVM Clojure, so the corpus is both a
regression suite and a *specification* certified against Clojure rather than
against its authors' beliefs. This directory holds the certification tooling that
closes that gap.
## What's here
- **`certify.clj`** — runs every corpus row's `:actual` and `:expected` through
**reference JVM Clojure** (each in a fresh `user` namespace, output/stdin sunk, a
5s per-case watchdog) and compares with Clojure's `=`. It buckets each row:
- `certified` / `certified-throws` — jolt's `:expected` matches real Clojure
- `divergent` — both evaluate but jolt's `:expected` disagrees with Clojure
- `throws-mismatch` — jolt and Clojure disagree on whether it throws
- `jvm-error``:actual` isn't runnable on vanilla Clojure (host-coupled /
jolt-specific) — informational, not certifiable
- `read-error` / `timeout` — won't read on the JVM reader, or ran too long
- **`known-divergences.edn`** — every current divergence, classified. Most are
**deliberate** jolt-specific or host-model deltas (see `:legend`): the all-double
numeric model, snapshot-heap concurrency, the no-JVM host model, jolt reader
features, the jolt printer, intentional strictness. A few are genuine **`:bug`**
entries with a tracked bead. These categories become the `:features` flags in
conformance inc3.
`make certify` is the gate wrapper. It skips cleanly when `clojure` (JVM) is not
installed; otherwise it runs `certify.clj` and fails the build on a **NEW**
(unclassified) divergence or a **stale** allowlist entry. Flaky entries (JVM
result is timing-dependent, e.g. `future-cancel`) are tolerated either way.
## Running
```sh
make certify # the gate wrapper (skips if clojure absent)
clojure -M test/conformance/certify.clj # gate directly (exit≠0 on new/stale)
clojure -M test/conformance/certify.clj test/chez/corpus.edn --edn /tmp/report.edn # full machine-readable report
```
## Current state
Of ~2487 vanilla-certifiable rows, **>2410 match reference Clojure exactly**; the
~70 divergences are all classified (deliberate deltas + 4 tracked bugs). The corpus
is trustworthy as a spec, with the host-specific deltas made explicit rather than
hidden.
## Adding / changing cases
When you add corpus rows or change behavior, re-run the certifier. A NEW divergence
means either a real bug (file it, tag the allowlist entry `:bug` + `:bead`) or a
deliberate delta (classify it). A stale entry means a divergence was fixed — remove
it from `known-divergences.edn`.