DOC: Add git-commits and pull-requests context files with routing

Extract AI commit and PR guidelines from AGENTS.md inline content into
two focused on-demand context files:

- Documentation/AI/git-commits.md  — commit format, prefixes, hook
  behavior (clang-format re-staging), first-time setup, AI disclosure
- Documentation/AI/pull-requests.md — draft PR policy, ready-for-review
  checklist, AI transparency requirements, PR description template, CI

Update AGENTS.md routing table with task-scoped entries for both files
and remove the now-redundant inline AI policy section. Update README
index to list the new files.

Author: hjmjohnson

AGENTS.md

@@ -13,30 +13,10 @@ Load only what your task requires:
 | Understanding the codebase layout | `Documentation/AI/architecture.md` |
 | Building or configuring ITK | `Documentation/AI/building.md` |
 | Writing or running tests | `Documentation/AI/testing.md` |
-| Code style, commits, PRs | `Documentation/AI/style.md` |
+| Code style, naming conventions | `Documentation/AI/style.md` |
 | Writing ITK C++ or Python | `Documentation/AI/conventions.md` |
-
-## AI-Generated Commits and Pull Requests
-
-### Draft Pull Requests
-
-Open AI-agent-assisted PRs in **Draft mode**. Do not convert to *Ready for Review* until:
-
-- [ ] All automated CI tests pass.
-- [ ] The implementation is correct, complete, and fully understood.
-- [ ] The PR description accurately reflects the changes made.
-- [ ] You can explain every line to a reviewer — you are accountable for all code in the PR.
-- [ ] You have run relevant tests locally and confirmed they pass.
-- [ ] You have reviewed for security issues (buffer overflows, deprecated APIs, etc.).
-
-### Transparency Requirements
-
-- State clearly in the PR description how AI tools generated or assisted with the code.
-- Identify which portions are AI-generated and what modifications were made.
-- Include evidence of local testing — do not rely on AI assertions of correctness.
-- Commit messages must describe **what** changed and **why**, not merely that AI made the change.
-- Follow ITK's commit format: `PREFIX: Description (≤78 chars)` — enforced by hook.
-- Do not use a simple `Co-Authored-By: AI-Tool` tagline as the only disclosure.
+| Creating a git commit | `Documentation/AI/git-commits.md` |
+| Opening or updating a pull request | `Documentation/AI/pull-requests.md` |
 
 ## Critical Pitfalls
 

Documentation/AI/git-commits.md

@@ -0,0 +1,55 @@
+# ITK Git Commit Guidelines
+
+## Required Format
+
+Enforced by the `kw-commit-msg.py` pre-commit hook. Commits that violate the
+format will be rejected.
+
+```
+PREFIX: Brief description (≤78 chars on subject line)
+
+Longer explanation if needed. Describe *what* changed and *why*,
+not just that a tool made the change.
+```
+
+## Prefixes
+
+| Prefix | Use for |
+|--------|---------|
+| `ENH:` | New feature or enhancement |
+| `BUG:` | Bug fix |
+| `COMP:` | Compilation fix (warnings, errors) |
+| `DOC:` | Documentation only |
+| `STYLE:` | Formatting, naming, no logic change |
+| `PERF:` | Performance improvement |
+| `WIP:` | Work in progress (do not merge) |
+
+## Hook Behavior
+
+The pre-commit hook runs **clang-format** on staged C++ files and modifies
+them in place if formatting changes are needed. When this happens:
+
+1. The hook modifies the file(s)
+2. The original commit is aborted
+3. You must **re-stage** the modified files and **recommit**
+
+Do not use `--no-verify` to bypass hooks — the format check exists to keep
+CI green.
+
+## First-Time Setup
+
+Run once after cloning:
+
+```bash
+./Utilities/SetupForDevelopment.sh
+```
+
+This installs the commit-msg and pre-commit hooks. Without it, commits will
+not be validated locally.
+
+## AI-Assisted Commits
+
+Commit messages for AI-assisted changes must still describe **what** changed
+and **why** — not merely that an AI tool generated the change. A
+`Co-Authored-By: <AI TOOL>` should not be used in commit messages.
+See `Documentation/AI/pull-requests.md` for PR-level disclosure requirements.

Documentation/AI/pull-requests.md

@@ -0,0 +1,52 @@
+# ITK Pull Request Guidelines
+
+## Opening a PR
+
+All AI-agent-assisted PRs must be opened in **Draft mode**. Do not convert
+to *Ready for Review* until every item below is satisfied.
+
+## Ready-for-Review Checklist
+
+- [ ] All automated CI tests pass (Azure Pipelines, GitHub Actions).
+- [ ] The implementation is correct, complete, and fully understood.
+- [ ] The PR description accurately reflects the changes made.
+- [ ] You can explain every changed line to a reviewer — you are accountable
+      for all code in the PR, regardless of how it was generated.
+- [ ] The diff has been reviewed for security issues: buffer overflows,
+      deprecated APIs, injection vectors, license conflicts.
+
+## AI Disclosure Requirements
+
+State clearly in the PR description how AI tools contributed. Specifically:
+
+- Identify which portions are AI-generated and what modifications were made.
+- Include evidence of local testing — do not rely on AI assertions of correctness.
+- A bare `Co-Authored-By: AI-Tool` trailer is **not** sufficient disclosure.
+
+## PR Description Template
+
+```markdown
+## Summary
+
+<What this PR does and why>
+
+## AI Assistance
+
+<Which tool(s) were used, what they generated, what was manually reviewed
+or modified>
+
+## Testing
+
+<Commands run locally, test output, or baseline comparisons>
+```
+
+## Commit Format
+
+Each commit in the PR must follow ITK's required format. See
+`Documentation/AI/git-commits.md` for the full specification.
+
+## CI / CDash
+
+- **Azure Pipelines** — Linux, Windows, macOS (C++ and Python builds)
+- **GitHub Actions** — Pixi builds and Apple Silicon
+- **CDash** — https://open.cdash.org/index.php?project=Insight