docs(ci): line anchors generated or pinned by tooling, against the anchor-by-name rule #2165

What: three tools produce or require file:line anchors, which the anchor-by-name rule forbids.

1. util/update_python_versions.py. COMPAT_ROW, rewrite_compat_rows and two python-versions.toml:(\d+)-(\d+) claims write .github/python-versions.toml:N into workflows.rst. test_the_workflows_page_cites_each_version_on_its_line in tests/project/test_python_versions_1660.py pins that form. Cite the "3.11" = … keys instead.

2. The recorded-defect contract. It asks for "the file:line that causes it" in:

   • test_option_roundtrip_unit.py (the defect field and its failure message);
   • tests/{corekit,foundation}/_roundtrip.py and tests/protocols/_edge_roundtrip.py;
   • test_dispatch_registry_unit.py's message;
   • test-coverage.rst.

   No current entry uses one, so only the contract needs to change.

3. test_resource_monitor_1740.TestTheDocsSayIt. It pins src/Runner.Worker/StepsRunner.cs:205-208 in workflows.rst. That range is the shutdown check in StepsRunner.RunAsync at actions/runner 796cc18ff. Its sibling :322-353 was renamed to StepsRunner.RunStepAsync in round 5 (docs(tests): fifth whole-repo pass over tests (#1103) #2159, docs(docs): fifth whole-repo pass over the non-API docs, with issue/PR roles (#1103) #2161).

Needs a ruling (my recommendation in brackets):

• Part 1: these anchors are regenerated and test-checked, so they can't drift, which is the rule's stated reason. [Cite by name anyway: a reader can't follow :19 without opening the file.]
• Part 3: is it the same question as docs: #719-style prose sweep after the #1090–#1102 defect wave #1103's ruling 4, on third-party citations pinned to a commit? [Yes, so it follows that ruling.]

Part 2 is a plain fix.