chore(release): bump version to 0.2.46

[fuller-stack-dev]

What Problem This Solves

Prepare OCM v0.2.46 so users can receive the native Claude login discovery fix merged in #222.

Why This Change Was Made

The release script changes the package version from 0.2.45 to 0.2.46 in Cargo.toml and Cargo.lock. After squash merge and successful CI on that exact main commit, the same script signs the release tag and dispatches the protected release workflow.

User Impact

The release includes the account-name preservation fix for background services and supervised gateways, allowing native CLI providers to find existing logins after service definitions and launch plans are refreshed.

Evidence

• Base: freshly fetched canonical main at c749b58c14fac479a1273e7a29842955be88aa16.
• Inspected the complete diff: two version replacements, with no source or dependency changes.
• fix: detect existing Claude logins in supervised gateways #222 passed all five required checks, Autoreview, and independent source-blind behavior validation.
• Used the release script’s --skip-checks option to avoid repeating local full-suite checks for a version-only change. This PR’s required CI and the exact-main release CI gate remain enforced.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed September 12, 2026, 3:50 AM ET / 07:50 UTC.

ClawSweeper review

What this changes

Updates OCM’s package version from 0.2.45 to 0.2.46 in Cargo.toml and Cargo.lock.

Merge readiness

✅ Ready for maintainer review

The release preparation remains necessary: current main and the latest published release are still at 0.2.45. The member-authored PR follows the established version-bump contract, with no actionable patch defects found.

Priority: P3
Reviewed head: 53690ced845f17ff13e95a45c686d7016bdcb6d0

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, consistent version bump matching the established release contract, with no correctness findings.
Proof confidence	🌊 off-meta tidepool	Not applicable: The MEMBER-authored PR only changes release metadata; the external-contributor runtime-proof gate does not apply, and no authority boundary changes.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: The MEMBER-authored PR only changes release metadata; the external-contributor runtime-proof gate does not apply, and no authority boundary changes.
Evidence reviewed	7 items	Complete introduced change: The pinned base-to-head diff contains exactly two version replacements; no dependencies, source code, or workflows change. Current main still needs the bump: Current main remains c749b58, whose package version is 0.2.45; the live PR remains open and unmerged. Published release check: GitHub reports v0.2.45 as the latest release, published September 11, 2026; the proposed version has not replaced it.
Findings	None	None.
Security	None	None.

How this fits together

OCM’s Cargo package metadata supplies the version used by its CLI and release packaging. The release process validates matching metadata before building and publishing signed release artifacts.

flowchart LR
  A[Cargo manifest] --> C[Matching version validation]
  B[Cargo lockfile] --> C
  C --> D[Release commit CI]
  D --> E[Signed release tag]
  E --> F[Platform builds and publication]

Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Use the existing two-file release preparation and preserve the separate exact-main CI, signed-tag, and protected publication stages.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this PR prepares a release version and introduces no behavioral bug claim.

Is this the best way to solve the issue?

Yes: synchronizing the two Cargo version records is the documented minimal release preparation, including for npm packaging.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against c749b58c14fa.

Labels

Label changes:

• add P3: This is routine release metadata preparation with two synchronized version edits and no runtime changes.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The MEMBER-authored PR only changes release metadata; the external-contributor runtime-proof gate does not apply, and no authority boundary changes.

Label justifications:

• P3: This is routine release metadata preparation with two synchronized version edits and no runtime changes.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The MEMBER-authored PR only changes release metadata; the external-contributor runtime-proof gate does not apply, and no authority boundary changes.

Evidence

What I checked:

• Complete introduced change: The pinned base-to-head diff contains exactly two version replacements; no dependencies, source code, or workflows change. (Cargo.toml:3, 53690ced845f)
• Current main still needs the bump: Current main remains c749b58, whose package version is 0.2.45; the live PR remains open and unmerged. (Cargo.toml:3, c749b58c14fa)
• Published release check: GitHub reports v0.2.45 as the latest release, published September 11, 2026; the proposed version has not replaced it.
• Established packaging contract: Release documentation explicitly derives npm versions from verified Cargo metadata and preserves the two-file version-bump contract. (docs/RELEASING.md:150, 53690ced845f)
• Publication safeguards remain intact: The unchanged release script checks exact-main CI before signing and verifies the tag before dispatch. Existing tests cover missing, pending, failed, and wrong-commit CI. These tests were inspected, not executed in this read-only review. (scripts/release.sh:417, 53690ced845f)
• Related fix and prior release ownership: GitHub verifies fix: detect existing Claude logins in supervised gateways #222 merged as the current base. It supplies the login-discovery fix this release intends to distribute. GitHub also verifies fuller-stack-dev authored the prior merged release preparation at chore(release): bump version to 0.2.45 #220. (c2c5590d5c6f)

Likely related people:

• fuller-stack-dev: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
• vincentkoc: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[fuller-stack-dev]

Merged as fc9f330 after all required checks and all npm jobs passed. The exact-main CI run is now the remaining gate before the signed v0.2.46 tag and protected release dispatch.

[fuller-stack-dev]

All CI jobs passed on the exact release commit fc9f330. Signed tag v0.2.46 was pushed and verified. Release publication is now queued: https://github.com/openclaw/ocm/actions/runs/34682686779.