docs(conformance): carry the two new fixtures into the arithmetic, not just the table

The totals table and the per-corpus heading were updated when the fixtures
landed; the "Orphaned fixtures" sentence that re-adds those same counts by hand
was not, so the page disagreed with itself — metamodel 329 vs 330 in the table,
and api-contract 50 vs 51.

Caught by `bun test scripts/site` (the site payload gate), which compares the
arithmetic against the table it sits under. Worth noting the gate is a chain —
`bun test scripts/site && build-site-payload --check` — so it reported as "site
payload is true FAILED" while the payload itself was perfectly fresh. The
failing half is the counts test, not staleness.

Also worth noting the shape: adding one fixture touches four places, and three
of them are prose that no compiler reads. The table, the per-corpus heading, the
hand-summed arithmetic, and the generated payload.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015NrWUxA6euwvnFcwKxcK6A

Author: dmealing

docs/CONFORMANCE.md

@@ -174,7 +174,7 @@ unit-test runners (`bun test`, `dotnet test`, `pytest`, `mvn test`) pull Docker.
 
 ## Fixture-to-doc mapping
 
-### `fixtures/conformance/` — metamodel loader + canonical serializer (329)
+### `fixtures/conformance/` — metamodel loader + canonical serializer (330)
 
 | Fixture prefix | Feature doc |
 |---|---|
@@ -328,8 +328,8 @@ Phase 1a is TypeScript + Python only; those three ports arrive in Phase 2.
 
 ## Orphaned fixtures (tested but not yet documented)
 
-The fixtures in the nine corpora mapped above (metamodel 329 + yaml 16 + verify 31
-+ render 15 + persistence 33 + api-contract 50 + source-resolution 25 + scope 10 +
+The fixtures in the nine corpora mapped above (metamodel 330 + yaml 16 + verify 31
++ render 15 + persistence 33 + api-contract 51 + source-resolution 25 + scope 10 +
 dependency 23) each map to a feature doc. None are orphaned today. The remaining
 corpora in the totals table gate tooling contracts (registry manifests, provider
 composition, agent context, docs emit) rather than user-facing metamodel behaviour,