fix(locate): determinism layer 10 — total preference order for suffix path resolution

resolve_path_in_graph's fallback used .find() over tracked files in map
iteration order; with multiple suffix matches (vendored copies, e.g.
benchmark's test/CMakeLists.txt) the explicit-path +200 priority landed on a
per-process-random winner — when it hit the vendored copy it was then dropped
by vendored filtering, so the real file's priority flipped on/off across runs
(c5d5fa00 top-3 reorder). Preference: exact > shortest > lexicographic.

Author: troyjr4103

crates/kin-cli/src/commands/locate.rs

@@ -11921,10 +11921,15 @@ fn resolve_path_in_graph(graph: &kin_db::InMemoryGraph, partial_path: &str) -> O
             return Some(candidate.to_string());
         }
 
+        // Several tracked files can match one suffix (e.g. a vendored copy of
+        // test/CMakeLists.txt), and the tracked list iterates in map order —
+        // pick by a total preference (exact > shortest > lexicographic) so the
+        // winner never depends on per-process iteration order.
         if let Some(path) = tracked_non_entity_files(graph)
             .into_iter()
             .map(|tracked| tracked.path)
-            .find(|path| path == candidate || path.ends_with(&format!("/{}", candidate)))
+            .filter(|path| path == candidate || path.ends_with(&format!("/{}", candidate)))
+            .min_by_key(|path| (path != candidate, path.len(), path.clone()))
         {
             return Some(path);
         }