docs: clarify commit and tag conventions

Author: lemmon

AGENTS.md

@@ -82,7 +82,9 @@ A comprehensive, fluent validation library for PHP inspired by Valibot and Zod.
 - **Task Tracking** - Use GitHub-style checkboxes (`- [ ]` for pending, `- [x]` for completed) in ROADMAP.md for clear progress tracking
 - **Commit Standards** - Follow Conventional Commits spec (e.g., `fix:`, `refactor:`, `docs:`)
 - **Commit Scope** - Each commit should address a single concern; tests and implementation can ship together, but unrelated formatting belongs elsewhere
+- **Commit Format** - Use concise Conventional Commit summaries: `<type>(<scope>): <short action>`. Avoid verbose release blurbs in commit messages; keep release notes in CHANGELOG/release tagging.
 - **Git Tags** - Prefer annotated tags for releases (author, date, message/signing) over lightweight tags
+- **Tag Format** - Annotated tags should use `vX.Y.Z - <concise headline>`; keep detailed notes in CHANGELOG/releases
 
 ### Development Tools
 - **Debugging** - `symfony/var-dumper` integration