docs: supercharge versioning.md — code-computed SemVer + zero-ambiguity cheat sheet
Now the canonical versioning reference, rewritten for an audience that already knows SemVer and cares about precision:
- New headline section: SemVer here is structurally computed, not a human promise. Documents the real pipeline (verified against muse/core/semver_classifier.py) — StructuredDelta -> invisible-rule filtering -> StabilityManifest -> ChangeClassifier -> SemVerAggregator -> SemVerClassification — with the exact bump matrix, the counter-intuitive "breaking-on-unstable = MINOR not MAJOR" rule and why it's correct, the exact pre-1.0 arithmetic from run_suggest(), a real .muse/stability.toml example, and a real `muse release suggest --json` output showing driver attribution (which commits/symbols caused the bump). - Ties this to muse code impact/gravity/deps: same symbol graph backs both the semver classifier and blast-radius queries — the version number and "who's affected" are two views into one fact, not two independently-maintained claims. - New cheat sheet up top: one-lookup table for which format/spec/example applies to which file, so the answer is never more than one glance away. Every internal anchor link verified against musehub's actual mistune-based heading-slug algorithm (ui_blob.py::_render_markdown), not assumed. - Updated the "known gap" section to "fixed" — the rc-channel bug this doc originally surfaced was already shipped in a prior commit. - Tightened all prior content (PEP 440 vs SemVer, channels, nightly pivot, numbering decision, terminology) for a reader who already knows what semver is — cut introductory explanation, kept verified specifics.
Semantic Changes
54 symbols
Files Changed
~1
1006 in snapshot
0 comments
muse hub commit comment sha256:5e375cfafa44dfd6feaec471380eb146dcad3653b204db30cba03543a3ccc8bc --body "your comment"
No comments yet. Be the first to start the discussion.