fix(publish): restore version commit-back to dev after npm release

[potb]

The dual-publish commit e244403 (March 8) replaced the old "Git commit and tag" step with the openagent publish logic. The version bump that was being committed back to dev got dropped as collateral.

Since then, package.json has been stuck at 3.11.0 while npm is at 3.13.1. Anything reading the version from source (doctor, auto-update, binary embed, /get-unpublished-changes) gets the wrong number.

This re-adds the commit-back step between the oh-my-opencode publish and the openagent publish, which is where it needs to sit so the git checkout -- package.json at the end only reverts the name mutation, not the version bump.

---

Summary by cubic

Restores the missing commit-back of the version bump in the publish workflow so the repo’s package.json stays in sync with the npm release, fixing stale version reads across tools.

• Bug Fixes
  • Add a “Commit version bump” step that commits root and package package.json changes, tags v{version}, and pushes branch and tags.
  • Place the step between the two publish phases to avoid reverting the version bump during cleanup.
  • Guard with the existing skip check to avoid unnecessary commits.

^{Written for commit fb837db. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Auto-approved: Restores lost release commit-back logic; uses standard Git patterns with safety checks for empty diffs and proper placement in the workflow.}