docs(remote-mcp): stamp the commit the #956 anchors were re-derived at

The anchor fixture records the commit its anchors were taken at, and the threat model must state the same commit, so a reviewer can resolve every cited line at a named revision. Both still named aad5c8b4, where the anchors no longer resolve after the transport seam shifted the lines they point at. Point both at c1626081, the seam commit whose tree the anchors were re-derived from. This commit changes no .py file, so every anchor that resolves at c1626081 resolves here too. The historical note about #930's drift between 7bf4f125 and aad5c8b4 stays as written -- it is the reason the guard exists. Refs #931, #956. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
2026-07-28 10:01:01 -05:00
parent c162608175
commit 2fb835a1aa
2 changed files with 5 additions and 3 deletions
@@ -8,7 +8,7 @@
    "document. #930's inventory had no such guard and its gitea_mcp_server.py",
    "anchors drifted between 7bf4f125 and aad5c8b4."
  ],
-  "generated_against_commit": "aad5c8b42361d380a8eeb07b94b90815e594c2c5",
+  "generated_against_commit": "c1626081757dff76ea49fcb1869fc0362dea45b1",
  "anchors": [
    {"anchor": "gitea_mcp_server.py:24728", "expect": "mcp_daemon_guard.bind_native_mcp_transport()"},
    {"anchor": "mcp_daemon_guard.py:49", "expect": "_PRODUCTION_TRANSPORTS = mcp_transport_config.SUPPORTED_TRANSPORTS"},