[Docs] Clarify stable release version lane after prereleases

[roomote]

Opened on behalf of Elliott de Launay. View the task or mention @roomote for follow-up asks.

Related GitHub Issue

This docs follow-up does not map to a single approved GitHub issue.

Linked issue: None for this release workflow update.

Description

This updates .roo/commands/release.md so the release flow uses generic even/odd placeholder guidance for the nightly pre-release lane versus the stable lane.

Reviewers should focus on whether the new guidance matches the current nightly publish workflow and clearly communicates major.ODD_NUMBER.patch for pre-releases versus major.EVEN_NUMBER.patch for stable releases without tying the rule to one specific version pair.

Test Procedure

• Review .github/workflows/nightly-publish.yml and confirm the documented rule matches the existing prerelease version rewrite logic.
• Review .roo/commands/release.md and confirm the release flow now uses generic even/odd placeholder guidance instead of a hard-coded version example.
• No runtime or UI validation was needed for this docs-only workflow update.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Not applicable for this docs-only workflow update.

Documentation Updates

• No documentation updates are required.
• Yes, documentation updates are required. Updated .roo/commands/release.md to document the generic even/odd version-lane rule for prereleases versus stable releases.

Additional Notes

This is meant to prevent future release prep from reusing a prerelease version lane for a stable tag while keeping the rule generic.

Get in Touch

Discord username not provided in this task context.

[roomote]

1 issue outstanding. Action required. See task

• The new even-minor stable-release rule conflicts with the current v3.55.0 release state and points the next release prep at the wrong version lane.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!