docs(release): foreground v0.10 vocabulary break

[aaltshuler]

Summary

• state the public node/edge/type/entity/property vocabulary break in the coordinated-upgrade warning
• label the detailed compatibility entry as a breaking graph-vocabulary change
• remove the redundant internal development-line history from the public release note

The published GitHub v0.10.0 release body has already received the same correction. The immutable v0.10.0 tag is unchanged.

Validation

• python3 scripts/check-docs.py
• git diff --check

Greptile Summary

The PR clarifies that v0.10 introduces a breaking public graph-vocabulary change and strengthens the coordinated-upgrade warning.

• Foregrounds the node, edge, type, entity, and property terminology migration.
• Labels the detailed compatibility entry as breaking.
• Removes redundant history about unreleased experimental manifest formats.

Confidence Score: 5/5

The documentation-only PR appears safe to merge.

The revised compatibility warning is consistent with the public vocabulary contract, and the retained release text continues to identify storage format v6 and the supported v0.9 upgrade path.

Important Files Changed

Filename	Overview
docs/releases/v0.10.0.md	Clarifies the documented v0.10 vocabulary break and removes internal development-line history without introducing an actionable documentation defect.

_{Reviews (1): Last reviewed commit: "docs(release): foreground v0.10 vocabula..." | Re-trigger Greptile}

[ragnorc]

Checked against current main's v0.10.0.md — applies cleanly, foregrounds removals the Compatibility entry already stated (and the vocabulary guard actually enforces), and removing the development-line note orphans nothing: the v7–v19 refusal remains covered in versioning.md and RFCs 0024/0026, and the one inbound release-note link targets an anchor that survives. LGTM.