feat(release): include README.md updates and fix typo

Author: apiad

.gemini/commands/release.toml

@@ -12,17 +12,18 @@ Follow these steps precisely:
 4.  **Propose Version:**
     - Propose a new version number with a brief rationale.
     - Use `ask_user` to confirm the version.
-    = Update the version in `package.json`, `pyproject.toml` or any other dependency configuration file, if it exists.
+    - Update the version in `package.json`, `pyproject.toml` or any other dependency configuration file, if it exists.
     - Update the version in any relevant source files if necessary (e.g., `__version__.py`).
     - Update the version in any relevant documentation files if necessary (e.g., `README.md`).
-5.  **Update CHANGELOG.md:**
+5.  **Update CHANGELOG.md and README.md:**
     - **IMMEDIATELY** after the version is decided, update `CHANGELOG.md`.
     - Create a new entry for the version, summarizing all changes since the last release.
     - Follow the established format in `CHANGELOG.md`.
+    - Update the README.md if it contains a version badge or any version references, plus update any relevant documentation in this file if necessary.
 6.  **Finalize Release:**
     - Use `ask_user` to confirm the final release.
     - If confirmed:
-        - Create a commit for the release: `git add CHANGELOG.md && git commit -m "chore(release): version <new_version>"`.
+        - Create a commit for the release: `git add CHANGELOG.md README.md && git commit -m "chore(release): version <new_version>"` (include any other files updated during the version bump).
         - Create a git tag: `git tag -a "v<new_version>" -m "Release v<new_version>"`.
         - Push the tag to the remote if it exists.
         - Propose using `gh release create` for GitHub releases, including the changelog entry as the release notes.