chore: release v0.6.29 — ship pipeline auto-commit

[githubrobbi]

Summary

just ship Phase 2 auto-commit for v0.6.29 — the [workspace.package].version bump in Cargo.toml. This PR routes that commit through branch-protection rules. Once it merges to main, run just release-tag to cut the signed v0.6.29 tag, which fires release.yml and builds the cross-platform binaries + GitHub Release v0.6.29. (No auto-tag on merge — the tag step is manual on-demand, Path B.)

Auto-merge

--auto --squash is queued — GitHub will merge as soon as the required status checks pass. Squash is required because main-protection mandates signed commits, and GitHub's rebase-auto-merge cannot sign the rebased commit; the squash-merge commit is signed by GitHub's own key, which satisfies required_signatures: true. The original author's signed commit remains verifiable in the PR branch history.

After merge

The auto-commit lived only on release/v0.6.29, so local main never drifted — sync it with a plain git pull --ff-only origin main (no reset --hard needed).