[BUG] Respect SemVer (not a duplicate - please read)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Claude Code versions do not follow Semantic Versioning. Every release appears to be tagged as 1.0.(x+1), regardless of whether the change is a bugfix, a new feature, or a breaking change. This makes it impossible to know if upgrading is safe, or if it might introduce new functionality or breaking behaviour. This is helpful for security (users can feel free to always update to the latest patch version) as well as user experience (I will read patch notes on minor releases to see what new capabilities are available).

There have already been two issues raised about this, namely #5869 and #7153. However, they were simultaneously closed as duplicates of _each other_, which leaves the concern unresolved and no open issue to track this. So please do not close this as a duplicate, as there is no such open issue at the moment. Other related issues include #5770 and #5735 although these ones are specifically about the CHANGELOG, not SemVer.

(I'm hoping by explicitly tagging this as "not duplicate", the automatic issue sorting tool won't close this... 🤞 cc @mathiaswillburger)

What Should Happen?

Releases should follow SemVer so that:

• x.y.(z+1) = bugfix (safe to update)
• x.(y+1).0 = new feature (safe to update, but might introduce new bugs)
• (x+1).0.0 = breaking change.

If SemVer is not respected, there should at least be clear documentation of what versioning scheme is being used. If following this is not desired, I recommend doing (x+1).0.0 at the very least, or x.(y+1).0 if it's possible to commit to non-breaking changes between releases.