compare-harnesses

# compare-harnesses > Codex skill: diff two scaffolded harnesses — the ADR-031 Bundle JSON > Pattern surfaced through Codex (iter 105 → iter 109). ## What it does Two-harness diff. Useful when you've forked an upstream template, when a support ticket says "mine and theirs scaffolded different things", or when a CI script wants a byte-equality check between a candidate scaffold and a known-good baseline. Reports three sections: 1. **Manifest meta** — same name? same kernel? same surface? 2. **Hosts** — which host adapters each side ships (`claude-code` / `codex` / `pi-dev` / `hermes` / `openclaw` / `rvm`) 3. **Files** — added / removed / changed (per-file SHA-256 fingerprints; the cheapest possible byte-equality test) | Verdict | Exit | Meaning | |---|---|---| | `IDENTICAL` | 0 | meta + hosts + every file fingerprint matches | | `DRIFT` | 1 | at least one of meta / hosts / files differs | | `no-manifest-in-a` | 2 | `a/.harness/manifest.json` missing | | `no-manifest-in-b` | 2 | `b/.harness/manifest.json` missing | | `no-manifest-in-either` | 2 | both sides missing manifest | ## Usage from Codex ``` /compare-harnesses a=./my-fork b=./upstream /compare-harnesses a=./my-fork b=./upstream bundle=true ``` ## Equivalent CLI ```bash harness compare ./my-fork ./upstream # text output harness compare ./my-fork ./upstream --bundle # ADR-031 schema-1 JSON ``` The `--bundle` form (ADR-031) emits a schema-1 JSON envelope so CI scripts can json-pars...