Align pre-1.0 release guidance

Author: Ma11hewThomas

CONTRIBUTING.md

@@ -88,8 +88,10 @@ If the schema and specification disagree, the **written specification takes prec
 
 Backward compatibility is a core CTRF principle.
 
-- PATCH and MINOR releases MUST NOT introduce breaking changes
-- Breaking changes MUST be explicit and well-justified
+- PATCH releases MUST NOT introduce breaking changes
+- Before `1.0.0`, MINOR releases MAY introduce breaking contract changes
+- Breaking changes MUST be explicit, well-justified, and documented with
+  migration guidance when action is required
 
 ---
 

README.md

@@ -45,7 +45,8 @@ The written specification defines the semantics and rules.
 
 CTRF follows Semantic Versioning.
 
-Releases are defined in [Releases](https://github.com/ctrf-io/ctrf/releases).
+Published specification versions are defined by annotated Git tags. See the
+[release process](RELEASE.md) for the current pre-1.0 policy.
 
 ## Reference Implementation