Prepare source release validation

docs/adr/0001-separate-composition-and-overlay.md

@@ -20,8 +20,8 @@ Use distinct strict-composition and intentional-overlay operations. Composition
 rejects conflicting definitions; overlay provides explicit precedence. Keep the
 operations opinionated rather than adding arbitrary per-field merge strategies.
 The [architecture policy](../policy/architecture.md) owns the governing boundary;
-the [target design](../roadmap/initial.md#composition-and-overlay) owns the planned
-operation table until its current contract lands.
+the [current configuration contract](../config.md#strict-document-composition) owns
+the operation table and selected-profile overlay behavior.
 
 ## Alternatives considered