Separate example setup from synthetic test releases

docs/roadmap/next-release-notes.md

@@ -64,6 +64,13 @@ Update callers, profiles, receipts, and CI declarations together for this
 clean interface cutover; compatibility shims and legacy receipt readers are
 not provided.
 
+Select this feature's ReleaseKit release in each consumer module before adopting
+the new profiles and workflows. Upgrade its tool declaration and workflow
+together: pre-feature tools through v0.3.0 require their historical profiles and
+flags. Historical tag retries use the workflow matching the tool recorded at
+that tag. Preserve the immutable
+tag and module files when retrying.
+
 - Set `ModuleDir` in Go requests or `module_dir` in profiles for a nested
   module. The selected directory must contain its own `go.mod`; module paths
   and release tags are read from that declaration, not inferred from a folder
@@ -102,3 +109,11 @@ For current behavior, see the [API and consumer guides](../consumers/),
 [CLI contract](../cli.md), [configuration reference](../config.md),
 [Gitea integration](../integrations/gitea.md), and
 [ReleaseKit release procedure](../release.md).
+
+## Release preparation
+
+Once this release's version is selected, record it in the maintained multi-module
+example's tool and require directives, and move these notes to its release-note
+path. Example setup currently selects a compatible version explicitly; disposable
+fixtures can verify current source before publication. Synthetic dependency
+versions belong to generated test metadata and local fixture proxies.