CI caught it: the fixture README added in bc0fb2a wrote the TestNet app id
literally, which is one more mention test_app_id_references_are_coherent.py
must classify. The README now points to DEFAULT_APP_ID instead, so no new
classification is needed. Local: that test 31 passed; the SDK wire-format
suite (pytest tests, dev extra, no native lib) 130 passed, 21 skipped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

The new Rust port's recorded response (application_recorded.json) mentions
TestNet app 770964251, and test_app_id_references_are_coherent.py fails on
any mention it cannot classify (verified: 1 failed before, 31 passed after,
pytest 9 in a scratch venv). It is a record of what the chain served on
2026-11-05, so it joins FROZEN with a comment saying why. This is a data
entry in an existing Python test's classification set, required by that
test's own instruction ("Decide which it is"); no Python logic changed.

tests/fixtures/README.md states how the responses were recorded (read-only)
and that params.global-state was removed from the application response
(gitleaks false positive on base64 state-variable names); the fields the
verifier reads are as served.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>