chore(release): open dev at 2.82.0 before releasing 2.81.0

[github-actions]

Summary

2.81.0 is about to be released. Merging this first means dev already outranks the new tag when it lands, so neither dev nor any open pull request ever inherits the version-line failure. release.yml refuses to publish until this has merged.

This moves dev to 2.82.0 in package.json and the desktop version
sources (tauri.conf.json, Cargo.toml, and the opencodex-desktop entry of Cargo.lock).

Opened automatically by .github/workflows/dev-version-bump.yml. The same
version-line move was previously done by hand in 32529c2, e4a85d1, 076ad30, and
befcac3.

Verification

The workflow proved 2.81.0 has neither a Git tag nor an npm publication, and bun test tests/ci-workflows/release-version-line.test.ts proved the chosen development version is unused.

Maintainer integration evidence

Maintainer integration into dev (MAINTAINERS.md dev-only maintainer integration) as the 2.81.0 release pre-move; release authorization is the owner's 2026-10-08 request to finish the 2.81.0 train and deploy it.

• Exact head 8a1c2b71badc76852aa9e0f78c252c3a8327f43c, opened by dev-version-bump.yml run 37823731549 (intended-version=2.81.0, mode=pre-move). The diff moves only the four version sources from 2.81.0 to 2.82.0.
• The PR was opened with the workflow token, so its runs started as action_required; a maintainer approved them. Exact-head results: Cross-platform CI 37823857989 attempt 3 success, Service lifecycle 37823857959 attempt 2 success, React Doctor 37823857996 attempt 2 success.
• Attempt 2 of Cross-platform CI failed only windows 3/9, in claude-picker-ca-store.test.ts ("metadata replaced between lstat and open" did not throw). That file and the code it exercises are identical on the current dev head, so the version-only diff cannot cause it; the failed job alone was rerun and passed. The Windows file-identity comparison is tracked as a follow-up.
• Independent review: the diff is four version strings produced by the audited workflow; no code changes.

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults.

Review readiness checklist

This PR stays in draft until every box below is ticked. Tick all four boxes once the requirements are met:

• Required local validation passed; commands, results, and any full-suite exception are documented.

• I pushed my PR to a recent dev commit (at most 10 behind; a maintainer may still ask for the exact tip before merge).

• I resolved all correct Codex and CodeRabbit findings.

• My PR is ready for review.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: lidge-jun/opencodex/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: b152a4e6-4953-47a9-9d64-a65b9a94a9c3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

⏳ DRAFT

• hygiene: unsponsored_surface.

What to do

• Fix unsponsored_surface — This changes an authentication, workflow, release-automation, or dependency surface. MAINTAINERS.md requires security review for these; ask a maintainer to apply maintainer-sponsored once they have reviewed it. Paths: package.json.
• Tick all four boxes in the PR description once you're done (currently 0/4).

Review readiness checklist

• ⬜ Required local validation passed; commands, results, and any full-suite exception are documented.
• ⬜ I pushed my PR to a recent dev commit (at most 10 behind; a maintainer may still ask for the exact tip before merge).
• ⬜ I resolved all correct Codex and CodeRabbit findings.
• ⬜ My PR is ready for review.

0/4 boxes ticked.

Automatic draft conversion failed (token cannot change draft status). Please convert this pull request to a draft manually. The required enforce-target check will keep failing until every issue above is resolved.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.