From 8da3a21e13f421bfef1b757b31d9e378d3e3a10a Mon Sep 17 00:00:00 2001
From: Cipher208 <269750686+Cipher208@users.noreply.github.com>
Date: Sun, 1 Nov 2026 16:19:57 +0100
Subject: [PATCH] docs(graph): drop a wrong finding id from the edge-scope
 comment

The comment labelled the target-side layer predicate F105, but F105 is a
different audit item (layer in episode_get, raw connections, cluster mixing).
A reader searching that id would land on the wrong finding.
---
 mcp_server/tools/graph.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/mcp_server/tools/graph.py b/mcp_server/tools/graph.py
index c707531..3b0e054 100644
--- a/mcp_server/tools/graph.py
+++ b/mcp_server/tools/graph.py
@@ -182,8 +182,8 @@ async def memory_graph_edges(
     graph = _get_graph(app, layer)
     dispatch = get_write_dispatch(graph._cm)
     # F54: the edge is scoped on BOTH endpoints — a join on one side alone
-    # pulls a foreign node's content into the answer. F105: the layer is scoped
-    # the same way, on the target as well as the source.
+    # pulls a foreign node's content into the answer. The layer is scoped the
+    # same way, on the target as well as the source, for the same reason.
     user_clause = ""
     user_params: tuple[Any, ...] = ()
     if user_id: