chore(release): bump to v0.32.0

[avrabe]

Summary

Release v0.32.0 — ships #337 (#343): C-style radix literals (0x…/0b…/0o…) are now rejected with a parse diagnostic instead of silently parsing to integer 0.

Changes

• Cargo.toml — [workspace.package] version 0.31.0 → 0.32.0
• Cargo.lock — cargo update --workspace --offline (all spar-* crates → 0.32.0)
• vscode-spar/package.json — version 0.31.0 → 0.32.0

REQ-PARSER-003 is already verified with release: v0.32.0 on main (landed in #343), so no requirements change is needed here.

Release contents

Issue	PR	Requirement
#337 — 0x… hex literal silently parses to 0	#343	REQ-PARSER-003

🤖 Generated with Claude Code

---

Generated by Claude Code

[github-actions]

Rivet verification gate

✅ 20/20 passed

	count
Passed	20
Failed	0
Skipped (no steps)	0

Filter: (and (= type "feature") (or (has-tag "v093") (has-tag "v0100")))

Failed artifacts

(none)

_{Updated automatically by tools/post_verification_comment.py. Source of truth: artifacts/verification.yaml.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[avrabe]

Status: this v0.32.0 bump is code-complete and 12 of 14 required checks are green on HEAD 4e8b2d7 (Format, Clippy, Test, Miri, Proptest, Fuzz smoke, Bench compile smoke, Cargo Deny, Supply Chain, Rivet validate, Code Coverage, Mutation Testing — plus the Verification Gate).

The only two outstanding required checks — Security Audit (RustSec) and Lean proof typecheck (lake build) — have been queued for a self-hosted runner since ~19:50 UTC (>4h) without ever starting. No failures; this is a runner-availability backlog for their labels, not a problem with the change. I'll merge automatically as soon as both pick up a runner and pass. If the queue doesn't drain, a maintainer may want to check runner capacity for those job labels.

---

Generated by Claude Code