Document release notes compare-link requirement

Author: pchalamet

AGENTS.md

@@ -37,6 +37,9 @@ Targeted test suites (when working on specific areas):
 - Each new feature/fix entry must be a short, single-line bullet.
 - Write entries in user-facing terms (what changed), not implementation detail.
 - At release time, move unreleased entries to the versioned section and reset `Unreleased`.
+- Each released version section should end with a compare link:
+  - `**Full Changelog**: https://github.com/MagnusOpera/FScript/compare/<previous-tag>...<new-tag>`
+- When publishing the GitHub release, include that same compare link in the release notes body.
 
 ## Specification Maintenance (Mandatory)
 

CHANGELOG.md

@@ -20,6 +20,8 @@ All notable changes to FScript are documented in this file.
 - LSP hover/signature for injected stdlib functions now shows named arguments (for example `Option.map` mapper/value labels).
 - LSP definition on injected stdlib functions now opens readonly virtual stdlib sources (`fscript-stdlib:///Option.fss`, `List.fss`, `Map.fss`).
 
+**Full Changelog**: https://github.com/MagnusOpera/FScript/compare/0.29.0...0.30.0
+
 ## [0.29.0]
 
 - Improved LSP inlay/type rendering for map-related inference (`int|string` map-key domain and `unknown map` display).