[asgeirf]

Refs #1073 (D3). Companion to neokapi/okapi-bridge#29, which adds the suite to the bridge repository.

The Okapi parity suite now lives in the okapi-bridge repository as the parity/ module, compiles against a released github.com/neokapi/neokapi, and runs there weekly against the latest kapi release. This PR removes it from here and everything that built, ran or gated on the bridge.

Removed

• cli/parity/ (the suite), scripts/okapi-test-scan, scripts/testcompare (dropped from go.work), core/formats/*/parity-annotations.yaml (now parity/annotations/<format>.yaml in the bridge), docs/internals/roundtrip-testing.md (moved with the harness).
• .github/workflows/parity.yml, and the Parity Gate jobs plus their needs: edges in release.yml and release-bowrain.yml. No release waits on a parity run.
• contract-audit.yml no longer checks out okapi-bridge; BRIDGE_SCHEMAS and -parity-report are opt-in flags with empty defaults, so the audit needs only upstream Okapi and this repository. The dashboard's Bridge column is empty until a report is passed in by hand.
• Makefile: parity-sandbox, parity-test, parity-publish, parity-clean, regen-okapi-fixtures; scripts/fetch-okapi-bridge.sh, scripts/parity-sandbox.sh, scripts/run-bridge-tests.sh, scripts/start-bridge-pool.sh.
• bench/pseudobench: the kapi-bridge, kapi-bridge-daemon and okapi engines and the -okapi-bridge/-bridge-jar flags. The bench keeps the native engine and the corpus discovery; make bench-run now depends on build and a new fetch-okapi-testdata target instead of the parity sandbox. The full bench with the bridge engines is in the bridge repository.
• The parity build tag from .golangci.yml and scripts/fieldguard.

Kept and repointed

• core/formats/support.yaml: the 18 formats whose gate was parity.yml now name make test (the native spec suite); TestSupportYAML requires a gate file that exists.
• check-support-gates.mjs: a Supported format with an Okapi counterpart must have core/formats/<id>/spec_test.go. Route mode is unchanged and reads the bridge workflow's artifact.
• The format-ops parity-publish ritual now downloads the latest parity-report artifact from the bridge's Parity workflow instead of running a suite; the ledger fields are unchanged.
• The parity eval card reproduces through that ritual (make eval-index regenerated _index.json).
• A-02, the testing docs, format-engineering.md, format-maturity.md, format-ops.md, the skills and the code comments that named cli/parity/... now describe the bridge-side suite. Dossier divergences: entries link to the bridge's annotation files.

Not changed

• make generate-reference-docs WITH_BRIDGE=1 / BRIDGE_PLUGIN (opt-in local inspection, never in CI; check-reference-provenance.sh still rejects a committed bridge entry).
• scripts/fetch-okapi-testdata.sh and regen-srx-parity-golden: upstream Okapi data and tikal, no bridge bytes.
• The dated research notes under docs/internals/research/format-ops/eval/ still quote the old paths as the state they audited.

Verification

make ci-tidy, make audit-modules, GOWORK=off go build ./... in cli, go vet on every touched package, go test ./core/formats (support/dossier gates), ./scripts/evalindex, ./scripts/fieldguard, bench/pseudobench, check-support-gates.mjs, validate-ledger.mjs, check-abs-paths.sh, check-em-dashes.sh, check-vocabulary.sh, check-reference-provenance.sh; the three edited workflows parse and every needs: names an existing job.

🤖 Generated with Claude Code

[github-actions]

📚 Preview deployed (served from AWS S3 + CloudFront, not committed to git):

• neokapi site: https://preview.bowrain.cloud/web/prs/3207/neokapi/docs/
• bowrain landing: https://preview.bowrain.cloud/web/prs/3207/bowrain/
• bowrain docs: https://preview.bowrain.cloud/web/prs/3207/bowrain/docs/
• kapi storybook: https://preview.bowrain.cloud/storybook/prs/3207/kapi/
• bowrain storybook: https://preview.bowrain.cloud/storybook/prs/3207/bowrain/