Release 0.0.9

AGENTS.md

@@ -105,6 +105,10 @@ If verification cannot be run, report exactly what was skipped and why.
 
 - Update `CHANGELOG.md` for every release with the release version, release
   date, Git tag, and a concise summary of notable changes.
+- Keep an `Unreleased` section at the top of `CHANGELOG.md` for changes that
+  have not been included in a tagged release yet.
+- Move relevant entries from `Unreleased` into the dated release section when
+  creating a release, and leave `Unreleased` present for future changes.
 - Use release headers in `YYYY-MM-DD vMAJOR.MINOR.PATCH` form.
 - Use version numbers in `MAJOR.MINOR.PATCH` form. Start this repository at
   `0.0.1`.
@@ -112,6 +116,9 @@ If verification cannot be run, report exactly what was skipped and why.
   exactly. For example, version `0.0.1` must be tagged as `v0.0.1`.
 - Create the Git tag only after the changelog and any release-related version
   changes are complete.
+- When the user requests creating a release, treat that as explicit permission
+  to commit the release changes, create the matching Git tag, and push both the
+  branch and tag.
 - Do not push release commits or tags unless the user explicitly requests it.
 
 ## Mandatory background review