Cargo.lock records codegraph-core 3.16.0 while Cargo.toml says 3.17.0 #2596

Found while working on

#2593 — the first local cargo build in a fresh worktree dirtied Cargo.lock with an unrelated one-line change, which then shows up in every contributor's git status.

The problem

Cargo.lock pins the workspace's own crate at the previous version:

 [[package]]
 name = "codegraph-core"
-version = "3.16.0"
+version = "3.17.0"

crates/codegraph-core/Cargo.toml is at 3.17.0 (kept in sync with package.json by scripts/sync-native-versions.ts, run from the version npm script), but the lockfile was not regenerated when that bump landed, so cargo rewrites it on the next build.

Impact

Minor but persistent: every fresh worktree that runs any cargo command gets a spurious modified Cargo.lock. That is exactly the kind of unexplained dirty file this repo's parallel-session guidance tells contributors to ignore, which makes it slightly harder to notice a dirty file that does matter.

Suggested fix

Regenerate the lockfile (cargo update -p codegraph-core --precise 3.17.0, or just commit the result of a plain cargo build) in its own small PR.

Worth also checking whether scripts/sync-native-versions.ts should update Cargo.lock alongside Cargo.toml and stage it — the version script currently stages only package.json and crates/codegraph-core/Cargo.toml, which is why the lockfile drifts every release rather than just this once.