changelog

1# Changelog
2 
3Update the top `Unreleased` list in `CHANGELOG.md` from commits after the latest release.
4 
5## Workflow
6 
71. Find the latest release base:
8   - Prefer the latest reachable tag: `git describe --tags --abbrev=0`.
9   - If there are no tags, search recent history for a release commit and use that hash.
102. Get commits: `git log <base>..HEAD --reverse --format='%H%x09%s'`.
113. Derive the GitHub repo URL from `git remote get-url origin`.
124. For each commit, add one concise changelog line:
13   - Format: `- [<short-hash>](<url>) <one-line summary>`
14   - If the commit clearly relates to a PR, link the hash to the PR URL instead of the commit URL.
15   - Detect PRs from subjects like `(#123)`, merge commits, or `gh pr list --search <hash> --state all --json number,url`.
165. Insert the new lines into the top `Unreleased` section/list in `CHANGELOG.md`.
17   - If no `Unreleased` section exists, create one at the top.
18   - Do not create a dated release heading unless the user asks for a release.
19 
20## Rules
21 
22- Keep one line per commit.
23- Preserve the existing changelog style when obvious.
24- Always add entries to the top `Unreleased` list.
25- Skip noisy commits only when clearly non-user-facing and explain what was skipped.
26- Do not invent PR links; use commit links when PR evidence is missing.