c0b9bada27
Workspace, all 9 path-pinned crate deps, and the npm wrapper's package.json all advance from 0.8.31 → 0.8.32. `scripts/release/ check-versions.sh` passes (workspace ↔ npm ↔ Cargo.lock all in sync). Auto-tag only fires on push-to-main, so this bump on `work/v0.8.32` doesn't accidentally cut a release; it just makes the in-development binary identify itself correctly. When this branch merges to main, the existing release pipeline takes over from here. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>