docs(remote-mcp): restamp the #956 threat-model anchors onto the commit they resolve at

The anchors and their citations moved in the previous commit because gitea_mcp_server.py gained the #948 worker-identity block. The fixture still named the commit the old line numbers resolved at, so the recorded provenance pointed at a tree where the new numbers do not hold. No anchor target or expectation changes; only the recorded commit does. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01F6Vomtndpq2gSBa88Tfcwy
2026-07-29 02:52:46 -04:00
parent 1dd30ecb15
commit fa510dd28d
2 changed files with 3 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": "ca5f078d8a575ea3e2991771f8b4ea85e3dcaaa0",
+  "generated_against_commit": "1dd30ecb1508b559868c2d5d94367bc055d5138e",
  "anchors": [
    {
      "anchor": "gitea_mcp_server.py:25087",