no-mistakes(document): Sync stale 249→258 conformance fixture counts in docs

Author: dmealing

README.md

@@ -166,7 +166,7 @@ metaobjects/
 ├── CLAUDE.md                       # project instructions for Claude
 ├── spec/                           # canonical metamodel docs, ADRs, roadmap
 ├── fixtures/                       # 19 cross-language conformance corpora — the oracle
-│   ├── conformance/                # metamodel (loader + serializer + navigation), 249 fixtures
+│   ├── conformance/                # metamodel (loader + serializer + navigation), 258 fixtures
 │   ├── yaml-conformance/           # YAML authoring desugar
 │   ├── render-conformance/         # FR-004 byte-identical render oracle
 │   ├── verify-conformance/         # FR-004 template-drift gate

spec/README.md

@@ -23,7 +23,7 @@ JSON. Metadata files live in `metaobjects/` at project root, organized by domain
 
 ## How parity is enforced
 
-Each implementation passes the same conformance fixtures under [`fixtures/conformance/`](../fixtures/conformance/) -- 249 shared test cases, plus a `CAPABILITIES.json` manifest (which optional behaviours a port declares) and an `ERROR-CODES.json` ledger (the shared error-code vocabulary). It is one of 19 shared corpora; the full corpus x port matrix is in [`docs/CONFORMANCE.md`](../docs/CONFORMANCE.md). Each fixture is a directory with `input/` metadata files and either an `expected.json` (happy-path canonical output) or `expected-errors.json` (error case). The Loader is expected to either produce byte-identical canonical output, or emit the exact set of expected error messages. Without this shared test surface, each language's Loader behavior would drift independently -- overlay merging working one way in TypeScript and a subtly different way in Java, and nobody noticing until a real consumer hit the mismatch. Conformance fixtures make parity testable, not aspirational. Format and contract in [`conformance-tests.md`](conformance-tests.md).
+Each implementation passes the same conformance fixtures under [`fixtures/conformance/`](../fixtures/conformance/) -- 258 shared test cases, plus a `CAPABILITIES.json` manifest (which optional behaviours a port declares) and an `ERROR-CODES.json` ledger (the shared error-code vocabulary). It is one of 19 shared corpora; the full corpus x port matrix is in [`docs/CONFORMANCE.md`](../docs/CONFORMANCE.md). Each fixture is a directory with `input/` metadata files and either an `expected.json` (happy-path canonical output) or `expected-errors.json` (error case). The Loader is expected to either produce byte-identical canonical output, or emit the exact set of expected error messages. Without this shared test surface, each language's Loader behavior would drift independently -- overlay merging working one way in TypeScript and a subtly different way in Java, and nobody noticing until a real consumer hit the mismatch. Conformance fixtures make parity testable, not aspirational. Format and contract in [`conformance-tests.md`](conformance-tests.md).
 
 ## Documents in this directory
 

spec/roadmap.md

@@ -75,7 +75,7 @@ _(FR-032 was developed under the working number "FR-026" — see commit history;
 
 ### Cross-port conformance corpora (every port runs the shared corpus)
 
-- **Metamodel conformance** — `fixtures/conformance/` (249 fixtures + CAPABILITIES + ERROR-CODES manifests). TS / C# / Java / Python all green; Kotlin inherits via `metadata-ktx`. Per-corpus counts: `docs/CONFORMANCE.md`.
+- **Metamodel conformance** — `fixtures/conformance/` (258 fixtures + CAPABILITIES + ERROR-CODES manifests). TS / C# / Java / Python all green; Kotlin inherits via `metadata-ktx`. Per-corpus counts: `docs/CONFORMANCE.md`.
 - **Render conformance** — `fixtures/render-conformance/`. TS / C# / Java / Kotlin / Python byte-identical.
 - **Persistence conformance** — `fixtures/persistence-conformance/` (24 query + 6 migration scenarios). Every port runs the **query** scenarios against Testcontainers Postgres, each provisioning its test DB from the committed, TS-produced `canonical/schema.postgres.sql` (Derby was dropped for the cross-port query corpus, ADR-0015). The **migration** scenarios are TS-only, since TS owns schema.
 - **API-contract conformance** — `fixtures/api-contract-conformance/` (26 core + tph/m2m/jsonb/write-through sub-corpora). All five ports run it in BOTH lanes — a hand-rolled reference server and the port's own GENERATED API artifact booted over HTTP.