docs(remote-mcp): restamp the commit the #956 anchors resolve at

The execution-authorization gate shifted two cited lines in mcp_daemon_guard.py, so the fixture and the document must name the commit where the re-anchored citations actually resolve. Both still named c1626081, where the two moved anchors no longer point at the claimed code. Point both at a143cd06. This commit changes no .py file, so every anchor that resolves at a143cd06 resolves here too. The historical note about #930's drift between 7bf4f125 and aad5c8b4 stays as written. Refs #931, #956. Addresses review 635. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
2026-07-28 11:17:47 -05:00
parent a143cd065b
commit 0104a76eea
2 changed files with 3 additions and 3 deletions
@@ -5,7 +5,7 @@ What the adversary is, what each boundary protects, and which services may share
 - **Issue:** #956 (Remote-MCP threat model), child of epic #929, cross-linked to #955.
 - **Depends on:** #930 (closed) — `docs/remote-mcp/coupling-inventory.md`.
 - **Blocks:** #932, #933, #934, #938.
- **Generated against commit:** `c1626081757dff76ea49fcb1869fc0362dea45b1` (#931's transport
+- **Generated against commit:** `a143cd065ba06e1a2bdc5143a19ec156e53650ef` (#931's transport
  bind seam). Originally generated against `aad5c8b42361d380a8eeb07b94b90815e594c2c5`
  (`master`) and re-anchored when #931 shifted the cited lines.
 - **Scope:** documentation only. This child changes no server behavior. It adds one
@@ -73,7 +73,7 @@ authenticate the *caller*, not the *intent*.
 ## 3. Trust boundaries

 "Crossing requires today" is what the code actually enforces at
-`c1626081757dff76ea49fcb1869fc0362dea45b1`, not what the design intends.
+`a143cd065ba06e1a2bdc5143a19ec156e53650ef`, not what the design intends.

 | ID | Boundary | Protects | Crossing requires today | Crossing must require remotely |
 | -- | -------- | -------- | ----------------------- | ------------------------------ |