From 4219721b774d1f911756aee4f7662c3780c11611 Mon Sep 17 00:00:00 2001
From: carlos-alm <contato@carlosalmeida.com>
Date: Sun, 16 Aug 2026 23:01:01 -0600
Subject: [PATCH] docs: fix stale references to retired entrypoint-attribution
 functions (#2437)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

#2434 retired markEntrypointTargets/mark_entrypoint_targets and
clearEntrypointAttributionForRemovedFiles/clear_entrypoint_attribution_for_removed_files
in favor of persistEntrypointCalls + projectEntrypointAttribution
(apply_entrypoint_attribution on the Rust side), but left two comments
pointing readers at the removed names — verified via grep across src/,
crates/, tests/ that no other references remain besides the one in
issue-2428-watch-python-entrypoints.test.ts's header, which intentionally
describes the historical bug being fixed and should stay as-is.

roles.rs's comment just needed the name swapped. The issue-2392 test's
comment needed more than that: it described a dedicated "pre-purge
capture" step for deleted guard files that the current evidence+projection
design doesn't have — deletion is now handled by the same generic
per-file purge every other per-file table uses, with projection re-deriving
the flag afterward. Rewrote it to describe the actual current mechanism
rather than mechanically substituting names for a step that no longer
exists.

docs check acknowledged: comment-only fix inside source files, no README/
CLAUDE.md/ROADMAP.md surface affected.
---
 crates/codegraph-core/src/graph/classifiers/roles.rs    | 2 +-
 tests/integration/issue-2392-python-entrypoints.test.ts | 8 +++++---
 2 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/crates/codegraph-core/src/graph/classifiers/roles.rs b/crates/codegraph-core/src/graph/classifiers/roles.rs
index cd9cb3ddc..9a535c0ba 100644
--- a/crates/codegraph-core/src/graph/classifiers/roles.rs
+++ b/crates/codegraph-core/src/graph/classifiers/roles.rs
@@ -451,7 +451,7 @@ pub(crate) fn do_classify_full(conn: &Connection) -> rusqlite::Result<RoleSummar
         return Ok(summary);
     }
 
-    // 2b. Program-entrypoint IDs (#2392) — set by `mark_entrypoint_targets`
+    // 2b. Program-entrypoint IDs (#2392) — set by `apply_entrypoint_attribution`
     // from an extractor-flagged call site (Python's `__main__` guard and
     // `__main__.py` module level). Mirrors the `entrypoint` column read by
     // `buildClassifierInput` in features/structure.ts.
diff --git a/tests/integration/issue-2392-python-entrypoints.test.ts b/tests/integration/issue-2392-python-entrypoints.test.ts
index 12eb10208..170517336 100644
--- a/tests/integration/issue-2392-python-entrypoints.test.ts
+++ b/tests/integration/issue-2392-python-entrypoints.test.ts
@@ -245,9 +245,11 @@ describe.each(ENGINES)(
       // Greptile finding on this PR's own fix (#2425): deleting the guard's
       // *file* is a different code path than editing it — the removed file
       // is never a member of fileSymbols (the reparsed-files set
-      // markEntrypointTargets iterates), so only the detect-changes stage's
-      // pre-purge capture (clearEntrypointAttributionForRemovedFiles /
-      // clear_entrypoint_attribution_for_removed_files) can catch this.
+      // persistEntrypointCalls iterates), so its entrypoint_calls evidence
+      // row can only be cleared via the generic per-file purge
+      // (preparePurgeStmts's entrypointCalls statement, the same path every
+      // other per-file table uses for a deleted file) — projectEntrypointAttribution
+      // then re-derives the flag from whatever evidence remains, clearing it.
       const dir = fs.mkdtempSync(path.join(os.tmpdir(), `cg-2425-stale-${engine}-`));
       try {
         const guardFile = path.join(dir, 'run.py');