docs(563): anchor the measurements to the issue, which a squash merge cannot erase

The paragraph added a commit ago pointed at "the commit messages that ran them" as the home of the
binder and `trim` mutant outcomes. A squash merge writes its own message and drops the bodies it
squashes, so that pointer can go stale the moment this branch lands. The issue and its pull request
survive it, and #563 is where the round-by-round measurements already are.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015QqCpYFsKgnAnx6jVwrKiV

docs/decisions/records/testing/scripted-engine-in-process-net.md

@@ -57,7 +57,8 @@ admits a sentence asserting that a specific mutation reddens — or does not red
 a `CLAIMS` entry in `scripts/tests/mutation_manifest.py`, executed every run; otherwise it is not
 written. That harness resolves a proof to `scripts/tests/<node id>` and runs pytest, so an NUnit proof
 cannot be declared in it and this coverage is entirely NUnit. The binder and `trim` mutants run while
-building these tests therefore stay in the commit messages that ran them, dated. Durable prose carries
+building these tests therefore stay in ersatztv#563 — its pull request and the commit messages that
+ran them — dated. Durable prose carries
 the mechanism each test is built on instead — which serializer difference, which engine branch — because
 that is re-checkable by reading the code rather than by trusting a remembered outcome.
 

docs/testing.md

@@ -104,7 +104,7 @@ built to separate one of them:
 
 Both are statements about the serializer and stop there — what MVC validation does with such a body
 belongs to the wrapper named above. What each test does to a suite when the binder is actually swapped
-was measured while building it and is recorded in the commit that did so, not here: under
+was measured while building it and is recorded in ersatztv#563, not here: under
 `testing.mutation-claims-are-executed` such a sentence is a `CLAIMS` entry in
 `scripts/tests/mutation_manifest.py` that executes every run or it is not written, and that harness runs
 pytest, so an NUnit proof cannot be declared in it.