Summary

v0.31.1 was yanked from crates.io because aprender-mcp/build.rs panicked
on an out-of-crate path (../../contracts/…) at `cargo install` time.
PR #910 landed the fix + Poka-Yoke; this PR cuts v0.31.2 so the published
tarballs reflect it.

Verified locally:

• `cargo package -p aprender-mcp` now runs unpack+compile verify cleanly on v0.31.2 (same command failed on v0.31.1 with the documented panic).
• `bash scripts/check_build_rs_paths.sh` → OK: 22 build.rs checked.
• 71 Cargo.toml files bumped 0.31.1 → 0.31.2; 0 stale pins remain.
• Cargo.lock regenerated via `cargo update --workspace`.

Test plan

• Workspace grep: 0 files contain `"0.31.1"`
• `cargo package -p aprender-mcp` verify step passes
• `cargo fmt --all --check` clean
• CI green (`ci / gate` + `workspace-test`)

After merge

1. Tag `v0.31.2` at the merge commit and create GitHub Release.
2. Re-publish all 68 crates via the dep-ordered script at 40s/crate pacing (~45min, crates.io 30-per-10min window).
3. Wait ~2min for crates.io edge cache.
4. `cargo install aprender --version 0.31.2 --force` — must succeed.
5. Run `/dogfood` skill and require GO verdict (task chore(deps): Bump renacer from 0.6.1 to 0.6.2 in the production-dependencies group #68).

Refs: task #67, feedback_post_publish_qa_required.md

🤖 Generated with Claude Code