Scrubbed a write-time PII leak in the v3.0.8 CHANGELOG entry. The v3.0.8 entry as originally written named the maintainer in describing how the validator regression was caught. That violated the standing distribution requirement that release-bound files (anything in the shipped zip, including CHANGELOG.md which feeds the public GitHub Release body) be free of maintainer-name references — only the LICENSE MIT copyright holder and the preston-peterson GitHub username embedded in repository URLs are approved exceptions per the v2.97.7 PII review. The fix in v3.0.9 rewrites the offending sentence into actor-agnostic framing — same technical content, same explanatory voice, no named maintainer. The v3.0.8 commit and Release body on GitHub still contain the original phrasing in git log history; the v3.0.9 commit replaces it going forward. Maintainer can optionally edit the v3.0.8 Release body on GitHub to redact the leak from the Release-page surface separately if desired — Release body text isn't tied to commit history.
Root cause of the write-time miss: today's release cadence (nine releases in a single session) compressed the normal CHANGELOG-writing pass, and the actor-named phrasing slipped through. The standing rule is "PII discipline at write-time, not audit-time" — meaning the changelog should be written without maintainer names from the start, not scrubbed after the fact. The compressed cadence made me lean toward more conversational phrasing that names who-did-what; the fix going forward is to default to the actor-agnostic framing (use "the maintainer," "surfaced during," passive constructions) for every release-bound file regardless of how casually the session is moving.
No code change in v3.0.9. Pure CHANGELOG correction.