<!-- LLeMbas CLI. Keep a Changelog's own rules, and the tree's: kept as the work happens, entries
     say what changed for someone using the project, old entries are never rewritten. -->
Bring CHANGELOG.md's `## [Unreleased]` section up to date with the commits below, which are not in any release yet.

- Read CHANGELOG.md first. Keep its format, headings and voice exactly. If it has no Unreleased section, add `## [Unreleased]` above the newest release; if there is no CHANGELOG.md, create one in the Keep a Changelog format.
- Group entries under `### Added`, `### Changed`, `### Fixed`, `### Removed`, `### Security` — only the headings you need.
- One entry per change a user of the project would notice, in words they would use: what changed and, when it is not obvious, why. Not one entry per commit; not file names; no commit hashes.
- Leave out what nobody outside the code would notice (refactors, tests, formatting) unless it changes behaviour.
- Do not touch any released section below Unreleased. Do not add entries that are already there.
- Change only CHANGELOG.md, then say in two or three lines what you added.

{{scope}}

Commits:
{{log}}

Files changed:
{{stat}}