Clarify superseded actions during release replay

Author: Marius Storhaug

docs/content/guides/formatting-release-note-prs.md

@@ -24,6 +24,8 @@ services, infrastructure modules, and published guidance.
 Each release records its incremental change from a declared release/source baseline. Consumers compose the applicable
 records after their current baseline through their selected target. The newest note does not replace intervening
 instructions, and an individual note does not need a migration manual from every historical version.
+When later instructions supersede earlier edits, explain which actions remain for the target and preserve any
+explicitly required intermediate installation or run.
 
 | Surface | Content it owns |
 | --- | --- |

docs/content/guides/versioning-and-releases.md

@@ -20,6 +20,7 @@ Identify the consumer's current release/source baseline and selected target, the
 release record after that baseline through the target in order. Compose the stated prerequisites, adoption or
 migration actions, and verification for the consumer's starting state. Reading the intervening records does not
 require installing or running every intermediate version; do so only when a record explicitly requires it.
+Apply later supersession instructions while preserving any required intermediate operations.
 
 The notes provide the complete change, rationale, impact, and action or explicit no-action result. Pull requests and
 commit diffs provide optional depth. Missing required instructions are an evidence gap to resolve with the producer.