chore: 🤖 tweak AGENTS.md

Author: lrodrigues-newstore

AGENTS.md

@@ -19,7 +19,10 @@ TypeScript is the default; keep modules ESM-first with named exports. Biome enfo
 Always adopt test-driven development, following the red-green-refactor cycle. Only exercise the components publicly exposed by the module when testing, and do not couple tests to internal implementation details. Vitest drives unit tests. Place specs under `test/` mirroring `src/` paths and use descriptive `describe` blocks. Property-based checks with `fast-check` are encouraged where meaningful, and `msw` is available for network mocks. If necessary, verify coverage locally with `pnpm test:coverage`.
 
 ## Commit & Pull Request Guidelines
-Follow Conventional Commits; `pnpm commit` invokes Commitizen under `@commitlint/config-conventional`. Describe behaviour changes as new features or patches as appropriate. Breaking changes should be described in the commit body following Conventional Commit format. PRs should link issues and summarise package-level impact. Run `pnpm lint` and `pnpm test` before opening a PR. Include screenshots or API snippets when adjustments affect consumers.
+Follow Conventional Commits; `pnpm commit` invokes Commitizen under `@commitlint/config-conventional`. Describe behaviour changes as new features or patches as appropriate. PRs should link issues and summarise package-level impact. Run `pnpm lint` and `pnpm test` before opening a PR. Include screenshots or API snippets when adjustments affect consumers.
 
-## Security & Release Notes
-Avoid checking secrets into templates or generators. Releases run through `pnpm release` (Lerna publish), so keep semver changes scoped to the packages you touch and document compatibility notes in the PR.
+## Security
+Avoid checking secrets into templates or generators.
+
+## Release Guidelines
+Releases run through `pnpm release` (Lerna publish), so keep semver changes scoped to the packages you touch and document compatibility notes in the PR.