docs: update line length and review guidelines for PR_DESCRIPTION.md

- Increased the line length limit from 100 to 120 characters in `AGENTS.md` and `AGENT_GUIDE.md` for better readability.
- Added exclusions for `PR_DESCRIPTION.md` in `review-implement.md`, `review-validate.md`, and `review.md` to clarify that this file should not be reviewed or flagged for issues.

These updates aim to enhance documentation clarity and improve the review process by clearly defining the scope of review files.

Author: raychrisgdp

.cursor/commands/review-implement.md

@@ -26,6 +26,7 @@ After a review has been validated via `/review-validate`, implement the remainin
    - Read the review file and extract: Review Summary, Metrics, and Findings grouped by severity.
    - **Include**: Critical and High severity findings with `file:line` references and explicit "Change:" recommendations.
    - **Exclude**: Findings marked as "Out of scope", "Deferred", or requiring external clarification ("NEEDS CLARIFICATION").
+   - **Exclude**: Findings related to `PR_DESCRIPTION.md` (this file is for PR authoring and should not be modified).
    - **User Override**: If `$ARGUMENTS` contains specific finding IDs (e.g., `--findings Spec-1`), implement only those.
 
 3. **Prioritize & Implement**

.cursor/commands/review-validate.md

@@ -29,6 +29,7 @@ After a review report exists in `reviews/`, re-check the current state, validate
    - Compare the current repo state to the review file contents.
    - Remove or downgrade findings that no longer apply.
    - Add new findings based on the current diff/state, using deterministic IDs that continue existing sequences.
+   - **Ignore `PR_DESCRIPTION.md`**: Do not flag issues in `PR_DESCRIPTION.md`; it is for PR authoring purposes only.
 5. **Update Review Report**
    - Keep the same template and formatting as `.cursor/commands/review.md`.
    - Update **Executive Summary**, **Findings**, **Strengths**, **Testing Results**, and **Metrics Summary**.

.cursor/commands/review.md

@@ -40,6 +40,7 @@ Provide clear, high-impact review findings that keep the implementation simple,
 
 4. **File Analysis**
    - List changed non-test files; note responsibility and trim opportunities.
+   - **Ignore `PR_DESCRIPTION.md`**: This file is for PR authoring and should not be reviewed. Do not flag issues in this file.
    - Apply language-specific review rules (Python 3.11+, FastAPI).
 
 ## Analysis Directives (CRITICAL FOCUS)
@@ -226,5 +227,6 @@ Use this format only in the optional appendix if needed for large change sets.
 - **Use Evidence**: Base findings on actual code analysis.
 - **Avoid Nitpicking**: Focus on substantive issues.
 - **Prefer minimal deltas**: Smallest viable change relative to main.
+- **Ignore PR_DESCRIPTION.md**: Do not review or flag issues in `PR_DESCRIPTION.md`; it is for PR authoring purposes only.
 
 Context: $ARGUMENTS

AGENTS.md

@@ -33,7 +33,7 @@ Prefer `uv run ...` when invoking project tooling directly (e.g., `uv run pytest
 
 - Type hints required for all functions (mypy strict-ish; see `[tool.mypy]`)
 - Docstrings: Google style (ruff pydocstyle)
-- Line length: 100 (ruff)
+- Line length: 120 (ruff)
 - Quotes: double quotes (ruff formatter)
 - Imports: standard → third-party → local; use `from __future__ import annotations`
 - **Mutable defaults**: Use `default_factory` for lists/dicts (e.g., `Field(default_factory=lambda: [])`)

docs/02-implementation/AGENT_GUIDE.md

@@ -78,7 +78,7 @@ personal-todo/
 
 ### Python Style
 
-- **Line length**: 100 characters (configured in `ruff`)
+- **Line length**: 120 characters (configured in `ruff`)
 - **Type hints**: Required for all functions (mypy strict mode)
 - **Docstrings**: Google style (configured in `ruff`)
 - **Imports**: Use `from __future__ import annotations` for forward references