Scope PageRank fallback to repo and collection

[m1rl0k]

Updated Cypher queries in Neo4jGraphBackend and Neo4jKnowledgeGraph to ensure PageRank fallback logic only considers CALLS and IMPORTS relationships within the same collection and/or repo. This prevents cross-repo or cross-collection influence when calculating in-degree approximations.

[augmentcode]

🤖 Augment PR Summary

Summary: Scopes the PageRank fallback (in-degree approximation) to avoid cross-repo/cross-collection influence.
Changes: Updates Neo4j Cypher in Neo4jGraphBackend and Neo4jKnowledgeGraph to constrain CALLS/IMPORTS relationships by collection and/or repo when computing fallback ranks.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

Because this WHERE caller.repo = $repo is applied after an OPTIONAL MATCH, rows where no caller exists will be filtered out (since caller is null), so symbols with zero incoming edges may not get the intended base pagerank. Consider making the repo predicate null-safe or pushing it into the OPTIONAL MATCH pattern so unmatched rows are preserved.

_{🤖 Was this useful? React with 👍 or 👎}

[augmentcode]

Same OPTIONAL MATCH + WHERE caller.repo = $repo interaction here: nodes with no incoming CALLS/IMPORTS will be dropped, which contradicts the comment about giving all nodes a base rank. This could cause some symbols in the repo to never have pagerank set in the fallback path.

_{🤖 Was this useful? React with 👍 or 👎}