[FEATURE] Introduce stable versioning and braveheart for unstable auto updates

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Please separate stable versions from "braveheart" versions.

Currently we are getting auto updates into what would be called braveheart versions that regularly break, with issues like core functionality like sub-agents not working: Task agent fails with 'tools: Tool names must be unique' when parent has many MCP tools · Issue #10668 · anthropics/claude-code

Proposed Solution

Introduce braveheart version releases that would be akin to what we have as the main releases right now, quick releases with questionable stability.

Once a braveheart release has been in use and has not generated blocking issues from community only then promote it to a "stable" version.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_