bug: native binary optionalDependencies pinned to 3.1.3 after v3.1.4 release

[carlos-alm]

Found during dogfooding v3.1.4

Severity: Medium
Command: codegraph info

Reproduction

npm init -y && npm install @optave/codegraph@3.1.4
npx codegraph info

Expected behavior

optionalDependencies in package.json should pin all @optave/codegraph-* native binaries to 3.1.4.

Actual behavior

All native binary pins are 3.1.3:

"@optave/codegraph-darwin-arm64": "3.1.3",
"@optave/codegraph-darwin-x64": "3.1.3",
"@optave/codegraph-linux-arm64-gnu": "3.1.3",
"@optave/codegraph-linux-x64-gnu": "3.1.3",
"@optave/codegraph-linux-x64-musl": "3.1.3",
"@optave/codegraph-win32-x64-msvc": "3.1.3"

Despite this, the npm registry resolves 3.1.4 binaries because they exist, so the installed binary IS 3.1.4 (per npm package.json). But codegraph info shows:

Native version: 3.1.4 (binary reports 3.1.3 — stale)

The "stale" warning is misleading — the binary IS correct, the Rust-compiled version string just lags.

Root cause

The sync-native-versions.js script or release workflow didn't update the pins in package.json before publishing v3.1.4.

Suggested fix

Update optionalDependencies to pin all native packages to 3.1.4. Run scripts/sync-native-versions.js and verify it bumps correctly.