package-lock.json still read 0.1.122 (and 0.1.119 before that) — npm only rewrites it on install, so the field lags every hand version bump. Syncing it before publishing so the published tree does not carry a lockfile that disagrees with its own package.json. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>