build: scope changelog lint depth past pre-SemVer patch history

.changelog-reader.yml

@@ -0,0 +1,12 @@
+# Configuration for mindsers/changelog-reader-action (see .github/workflows
+# and the org's reusable powershell-ci.yml, which sets validation_level but
+# not validation_depth).
+#
+# Releases 0.65.1-0.66.2 predate this org's Keep a Changelog / SemVer
+# patch-section convention: those patch versions genuinely shipped
+# Added/Changed content alongside fixes (verified against their git tags),
+# so recategorizing them as Fixed-only would misrepresent what shipped.
+# Scoping validation to the most recent released entries keeps the linter
+# enforcing the convention on new work without rewriting that history.
+# See #499.
+validation_depth: 2

CHANGELOG.md

@@ -5,12 +5,19 @@
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+> Releases `0.65.1`-`0.66.2` predate this project's adoption of the
+> Keep a Changelog patch-release convention (only `Fixed`/`Security` entries)
+> and genuinely shipped `Added`/`Changed` content in what were nominally
+> patch versions; those historical entries are left as-is rather than
+> recategorized to avoid misrepresenting what actually shipped. CI changelog
+> validation is scoped to recent releases via `.changelog-reader.yml` (#499).
+
 ## [Unreleased]
 
 ### Changed
 
 - Build system rewritten on top of `psake` + `PowerShellBuild`, mirroring
   PSDepend's convention (`requirements.psd1`, `build.ps1`, `psakeFile.ps1`
   at the repo root with `Init`/`Clean`/`StageFiles`/`Build`/`Analyze`/
   `Pester`/`Test`/`BuildHelp`/`Publish` tasks). Tests now build and import
   the staged module from `Output\` instead of requiring `PSKoans` to
@@ -29,12 +36,12 @@
   `(Get-PSKoan -Scope Module).Path` directly from test scope, bypassing
   module-scoped mocks, which let the real cmdlet run and `Set-Content`
   overwrite every staged koan file with fixture content.
 - `build.ps1` now resolves `requirements.psd1` / `psakeFile.ps1` against
   `$PSScriptRoot` instead of the caller's working directory.
 - Test files that bootstrap a nested `build.ps1 -Task Build` now run it
   in a child `pwsh` process instead of in-process, since `build.ps1` ends
   with `exit` and was terminating the hosting Pester process.
 - `psakeFile.ps1` resolves `Test.RootDir` from `$PSScriptRoot` instead of
   `$env:BHProjectPath`, which required `Set-BuildEnvironment` to already
   have run.
 
@@ -49,7 +56,7 @@
   module files when module parameters are specified (#399).
 - `Invoke-Koan` fixed for the case where PSKoans is not on
   `$env:PSModulePath`: the module path is now copied into the new
   runspace, and runspace errors now propagate back to the calling
   session (#399).
 - `Show-Karma -Meditate` now passes `-NoNewWindow` to `Start-Process`, so
   the configured editor no longer opens in a new console window (#397,