Precise Code Navigation

User clicks go-to-definition on `applyPatch` in a TS file. The popup shows three candidate definitions across the repo, two from node_modules. No precise (SCIP) badge appears.

Per docs/code_navigation, when a SCIP index is present for the commit + language, the navigation returns a single precise definition. The multi-candidate UI indicates Sourcegraph fell back to search-based heuristics — i.e., no fresh SCIP index. Trigger or wait for `scip-typescript` upload for this …

Operator wants every caller of public API `acme/lib.Sanitize` across the entire instance, not just within the defining repo.

With cross-repo SCIP indexes uploaded (matching SCIP symbol moniker scheme per docs/code_navigation/explanations/uploads), Find References returns callers across repos. If only the defining repo is indexed precisely, callers in other repos surface via search-based fallback — clearly flagged in the …

Repo has a SCIP index uploaded for commit ABC. User navigates on branch `feature/x` whose latest commit XYZ has refactored `applyPatch` into `applyDelta`. Hover shows the old signature.

Per docs/code_navigation, indexes are commit-scoped; on a non-indexed commit Sourcegraph falls back to the nearest-ancestor indexed commit and surfaces a 'stale data' indicator. Treat hover details as approximate until the auto-indexer (or user-triggered upload) catches up to XYZ.