Align licensing documentation and adopt MIT catalogs

docs/release.md

@@ -15,6 +15,21 @@ compatibility impact and consumer actions and update affected canonical docs.
 For catalog updates, record selected catalog versions and any consumer action,
 linking to the catalog policy rather than repeating its contracts.
 
+Follow the [OSS policy](policy/oss.md) when preparing licensing and attribution
+changes. Each new note must end with the following navigation, replacing
+`vMAJOR.MINOR.PATCH` with the selected release tag:
+
+```markdown
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/promptkit/src/tag/vMAJOR.MINOR.PATCH/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/promptkit/src/tag/vMAJOR.MINOR.PATCH/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/promptkit/src/tag/vMAJOR.MINOR.PATCH/docs/oss/attribution.md)
+```
+
+Check these file paths against the candidate; a future tag need not resolve
+remotely during preparation. The annotated tag derives from this same note,
+including its footer. Promptkit publishes no separate hosted release body or
+download page. If such a channel is deliberately introduced, reuse the note
+and preserve its footer. No extra network checks, artifacts, or approval gates
+are introduced, and published notes are not retrofitted.
+
 Retire completed roadmaps, preserving planned or deferred work and repairing
 links. This is housekeeping, not a separate approval gate. Review changes
 through the ordinary development workflow, commit them, and push main to