style(docs): unwrap hard-wrapped paragraphs in new agent docs

The repository convention is unwrapped paragraphs (one line per logical paragraph) - see existing contributing.md and pull_request.md where lines run to ~150-250 chars. The newly added AGENTS.md, architecture.md, and docs/contributing/agents/ files were authored with a ~70-char hard wrap, breaking the convention. Unwrap them to match.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: bearomorphism

AGENTS.md

@@ -2,9 +2,7 @@
 
 ## Purpose
 
-This file is the auto-loaded entry point for AI agents working on the
-`commitizen` repository. It holds the rules an agent needs in **every**
-session. Deeper guidance lives in:
+This file is the auto-loaded entry point for AI agents working on the `commitizen` repository. It holds the rules an agent needs in **every** session. Deeper guidance lives in:
 
 - [Contributing](docs/contributing/contributing.md) — setup, dev workflow, PR lifecycle.
 - [Contributing TL;DR](docs/contributing/contributing_tldr.md) — poe command cheat sheet.
@@ -16,11 +14,9 @@ Follow these instructions in addition to any higher-level tool or system rules.
 
 ## Project at a glance
 
-- **Project**: `commitizen` — Python CLI for enforcing Conventional Commits,
-  automating version bumps, and generating changelogs.
+- **Project**: `commitizen` — Python CLI for enforcing Conventional Commits, automating version bumps, and generating changelogs.
 - **Library + CLI**: code is reachable both via `cz` and `import commitizen`.
-- **Cross-platform**: tests run on Linux/macOS/Windows × Python 3.10–3.14.
-  Avoid POSIX-only assumptions (paths, subprocesses, line endings).
+- **Cross-platform**: tests run on Linux/macOS/Windows × Python 3.10–3.14. Avoid POSIX-only assumptions (paths, subprocesses, line endings).
 - **Key entrypoints**:
     - `commitizen/cli.py` — CLI definition (decli + argparse).
     - `commitizen/commands/` — one module per `cz` subcommand.
@@ -41,57 +37,31 @@ Follow these instructions in addition to any higher-level tool or system rules.
 | Tag handling | `commitizen/tags.py`, `tests/test_tags.py` |
 | Pre-commit / CI | `.pre-commit-config.yaml`, `.github/workflows/`, `pyproject.toml` (poe tasks) |
 
-For recurring task types (add a provider, deprecate an API, regenerate
-snapshots, ...), use the matching playbook in
-[For AI Agents § Playbooks](docs/contributing/agents/index.md#playbooks)
-instead of reinventing the workflow.
+For recurring task types (add a provider, deprecate an API, regenerate snapshots, ...), use the matching playbook in [For AI Agents § Playbooks](docs/contributing/agents/index.md#playbooks) instead of reinventing the workflow.
 
 ## Do not touch
 
-These files are generated, tracked, or otherwise managed automatically.
-Do not edit them directly:
-
-- `CHANGELOG.md` — produced by `cz changelog`. Hand-edits will be
-  overwritten on the next release.
-- `commitizen/__version__.py` — bumped by `cz bump` via the configured
-  version provider.
-- `.pre-commit-config.yaml:rev:` lines under the `Commitizen` repo —
-  bumped by `cz bump` (`version_files` in `pyproject.toml`).
-- `docs/images/cli_help/*.svg` and `docs/images/cli_interactive/*.gif` —
-  regenerated by `uv run poe doc:screenshots`. See the
-  [update-snapshots playbook](docs/contributing/agents/playbooks/update-snapshots.md).
-- `tests/**/*` snapshot files used by `pytest-regressions` — regenerated
-  via `uv run poe test:regen`.
-- `uv.lock` — only modify by changing dependencies in `pyproject.toml`
-  and running `uv sync`, never by hand-editing.
-- Anything under `__pycache__/`, `.mypy_cache/`, `.ruff_cache/`, `.venv/`,
-  `site/`, `coverage.xml`, `junit.xml`.
+These files are generated, tracked, or otherwise managed automatically. Do not edit them directly:
+
+- `CHANGELOG.md` — produced by `cz changelog`. Hand-edits will be overwritten on the next release.
+- `commitizen/__version__.py` — bumped by `cz bump` via the configured version provider.
+- `.pre-commit-config.yaml:rev:` lines under the `Commitizen` repo — bumped by `cz bump` (`version_files` in `pyproject.toml`).
+- `docs/images/cli_help/*.svg` and `docs/images/cli_interactive/*.gif` — regenerated by `uv run poe doc:screenshots`. See the [update-snapshots playbook](docs/contributing/agents/playbooks/update-snapshots.md).
+- `tests/**/*` snapshot files used by `pytest-regressions` — regenerated via `uv run poe test:regen`.
+- `uv.lock` — only modify by changing dependencies in `pyproject.toml` and running `uv sync`, never by hand-editing.
+- Anything under `__pycache__/`, `.mypy_cache/`, `.ruff_cache/`, `.venv/`, `site/`, `coverage.xml`, `junit.xml`.
 
 ## Mandatory PR reminders
 
-These are easy to miss when working from an agent and are required by
-the PR template:
-
-1. **Complete the AI disclosure**. Check
-   "Was generative AI tooling used to co-author this PR?" and fill in
-   the `Generated-by:` trailer with the tool name. Details:
-   [Pull Request Guidelines § AI-Assisted Contributions](docs/contributing/pull_request.md#ai-assisted-contributions).
-2. **Run `uv run poe all` before pushing**. This is the command named in
-   the PR template; it auto-formats then runs the same lint/check/test
-   pipeline as CI. To mirror CI exactly afterwards, run
-   `uv run poe ci` (uses `prek`, does not auto-format).
-3. **Fill in "Steps to Test This Pull Request"** with the exact commands
-   you ran locally — the maintainers re-run them.
-4. **Follow Conventional Commits** — the project uses itself to validate
-   commit messages.
+These are easy to miss when working from an agent and are required by the PR template:
+
+1. **Complete the AI disclosure**. Check "Was generative AI tooling used to co-author this PR?" and fill in the `Generated-by:` trailer with the tool name. Details: [Pull Request Guidelines § AI-Assisted Contributions](docs/contributing/pull_request.md#ai-assisted-contributions).
+2. **Run `uv run poe all` before pushing**. This is the command named in the PR template; it auto-formats then runs the same lint/check/test pipeline as CI. To mirror CI exactly afterwards, run `uv run poe ci` (uses `prek`, does not auto-format).
+3. **Fill in "Steps to Test This Pull Request"** with the exact commands you ran locally — the maintainers re-run them.
+4. **Follow Conventional Commits** — the project uses itself to validate commit messages.
 
 ## When unsure
 
-- Read the existing tests and user docs to understand the expected
-  behavior before changing code.
-- When behavior is ambiguous, assume **backward compatibility with
-  current tests and docs** is required. Add a deprecation window
-  instead of breaking it; see the
-  [deprecate-public-api playbook](docs/contributing/agents/playbooks/deprecate-public-api.md).
-- Cross-platform parity matters — if you cannot test on macOS or
-  Windows locally, surface that in the PR description.
+- Read the existing tests and user docs to understand the expected behavior before changing code.
+- When behavior is ambiguous, assume **backward compatibility with current tests and docs** is required. Add a deprecation window instead of breaking it; see the [deprecate-public-api playbook](docs/contributing/agents/playbooks/deprecate-public-api.md).
+- Cross-platform parity matters — if you cannot test on macOS or Windows locally, surface that in the PR description.

docs/contributing/agents/index.md

@@ -1,9 +1,6 @@
 # For AI Agents
 
-These pages are written for AI agents contributing to Commitizen. Human
-contributors may also find them useful as a quick reference. They
-**complement** the existing human-facing contributor docs rather than
-replace them — anything covered by the human docs is linked, not restated.
+These pages are written for AI agents contributing to Commitizen. Human contributors may also find them useful as a quick reference. They **complement** the existing human-facing contributor docs rather than replace them — anything covered by the human docs is linked, not restated.
 
 > If you are an AI agent looking to **use** Commitizen as a tool (validate
 > commit messages, bump versions in a downstream project), see the skill
@@ -12,9 +9,7 @@ replace them — anything covered by the human docs is linked, not restated.
 
 ## Source-of-truth map
 
-When two documents could host a piece of guidance, this table is the
-tie-breaker. Agent pages that drift from it should be fixed, not the
-human pages.
+When two documents could host a piece of guidance, this table is the tie-breaker. Agent pages that drift from it should be fixed, not the human pages.
 
 | Topic | Lives in | Why |
 |---|---|---|
@@ -38,34 +33,20 @@ human pages.
 | Recover from a CI failure | [Validation Guide](validation.md#ci-failure-recipes) |
 | Implement a recurring task type | [Playbooks](#playbooks) |
 
-The repo-root [`AGENTS.md`](https://github.com/commitizen-tools/commitizen/blob/master/AGENTS.md)
-is the auto-loaded entry point for most agent tools. It holds the rules an
-agent needs in every session; this page is the deeper reference.
+The repo-root [`AGENTS.md`](https://github.com/commitizen-tools/commitizen/blob/master/AGENTS.md) is the auto-loaded entry point for most agent tools. It holds the rules an agent needs in every session; this page is the deeper reference.
 
 ## Agent-specific deltas
 
 Humans absorb these rules through review; agents need them stated:
 
-1. **Complete the PR template fully**, including the AI-disclosure checkbox
-   and the `Generated-by:` trailer. The maintainers re-run the commands you
-   list under "Steps to Test This Pull Request" — make them exact.
-2. **`uv run poe all` is the pre-push verification command** named in the
-   PR template. `poe ci` is the CI-equivalent runner (uses `prek` and does
-   not auto-format); run it too if you want to mirror CI exactly. See the
-   [Validation Guide](validation.md#choosing-a-final-check) for the
-   distinction.
-3. **Do not touch generated artifacts.** See the do-not-touch list in
-   [`AGENTS.md`](https://github.com/commitizen-tools/commitizen/blob/master/AGENTS.md).
-4. **Prefer targeted test selectors during iteration** — see the
-   [targeted-test map](validation.md#targeted-test-map). The full suite
-   is fine for a final pre-push run.
+1. **Complete the PR template fully**, including the AI-disclosure checkbox and the `Generated-by:` trailer. The maintainers re-run the commands you list under "Steps to Test This Pull Request" — make them exact.
+2. **`uv run poe all` is the pre-push verification command** named in the PR template. `poe ci` is the CI-equivalent runner (uses `prek` and does not auto-format); run it too if you want to mirror CI exactly. See the [Validation Guide](validation.md#choosing-a-final-check) for the distinction.
+3. **Do not touch generated artifacts.** See the do-not-touch list in [`AGENTS.md`](https://github.com/commitizen-tools/commitizen/blob/master/AGENTS.md).
+4. **Prefer targeted test selectors during iteration** — see the [targeted-test map](validation.md#targeted-test-map). The full suite is fine for a final pre-push run.
 
 ## Playbooks
 
-Recipes for recurring task types. Each playbook is self-contained: trigger,
-files to read first, ordered steps, verification commands, and known
-pitfalls. They link out to the human-facing concept docs rather than
-restating concepts.
+Recipes for recurring task types. Each playbook is self-contained: trigger, files to read first, ordered steps, verification commands, and known pitfalls. They link out to the human-facing concept docs rather than restating concepts.
 
 - [Add a version provider](playbooks/add-version-provider.md)
 - [Add a changelog format](playbooks/add-changelog-format.md)
@@ -75,18 +56,12 @@ restating concepts.
 
 If your task does not match a playbook, fall back to the general flow:
 
-1. Read the [Architecture Overview](../architecture.md) for the relevant
-   subsystem.
-2. Read 1–2 existing examples in the same directory to match local
-   conventions.
+1. Read the [Architecture Overview](../architecture.md) for the relevant subsystem.
+2. Read 1–2 existing examples in the same directory to match local conventions.
 3. Make the change, plus tests, plus user-facing docs.
 4. Iterate with targeted tests; finish with `uv run poe all`.
 5. Open the PR using the template; check the AI-disclosure box.
 
 ## Updating these pages
 
-Treat these pages like any other code change: open a PR, follow the
-template, run `uv run poe doc:build` to verify the mkdocs build, and
-check internal links for breakage. If you find yourself restating
-something that already lives in a human-facing doc, link to it instead
-and shorten the agent doc.
+Treat these pages like any other code change: open a PR, follow the template, run `uv run poe doc:build` to verify the mkdocs build, and check internal links for breakage. If you find yourself restating something that already lives in a human-facing doc, link to it instead and shorten the agent doc.