fix(ci): normalize Windows CRLF line endings in PR governance script

[Parideboy]

Description

The CODE_BLOCK_RE regex in scripts/pr-governance.py expects LF after the opening fenced code block. PR bodies authored on Windows can arrive with CRLF line endings, which leaves a \r before the \n and prevents has_test_output() from detecting a valid Test Output block.

This normalizes CRLF to LF once when loading the pull request body, before section extraction and code-block matching. A regression test now verifies that a valid PR body with CRLF line endings still passes governance.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• Tests only

Changes Made

• Normalize Windows CRLF line endings in scripts/pr-governance.py before regex-based validation runs.
• Added test_validate_pull_request_accepts_crlf_test_output_code_block to prevent regressions.

Testing

• Unit tests pass (pytest)
• Linting passes (ruff check)
• Formatting passes (ruff format --check)
• New tests added for new functionality

Test Output

python -m pytest scripts/tests/test_pr_governance.py scripts/tests/test_pr_health_labels.py scripts/tests/test_pr_health_workflow.py -q
8 passed in 0.06s

ruff check scripts/pr-governance.py scripts/tests/test_pr_governance.py scripts/tests/test_pr_health_labels.py scripts/tests/test_pr_health_workflow.py
All checks passed!

ruff format --check scripts/pr-governance.py scripts/tests/test_pr_governance.py scripts/tests/test_pr_health_labels.py scripts/tests/test_pr_health_workflow.py
4 files already formatted

Real Behavior Proof

• Environment: local Windows 11 checkout, Python 3.13.13.
• Exact command / steps: Converted the known-valid governance test body to CRLF line endings and passed it through validate_pull_request in the new regression test.
• Observed result: The report is valid with no problems, proving the fenced Test Output block is recognized after normalization.
• Not tested: GitHub-hosted Windows PR authoring path end to end; the unit test covers the exact CRLF body shape consumed by the validator.

Review Readiness

• I have performed a self-review
• This PR is ready for human review

[github-actions]

PR governance

This PR follows the template and is marked ready for human review.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[chopratejas]

Do you know why we have so many failures? Related to your fix? I dont think so - but want to check

[Parideboy]

Do you know why we have so many failures? Related to your fix? I dont think so - but want to check

No idea, I will take a closer look after work. But it's mostly related to torch installation issues:

Three test jobs are failing because of duplicate PyTorch CPU index URLs. The global PIP_EXTRA_INDEX_URL is already set, but individual jobs are passing --index-url again, creating duplicates.

Fixes needed in .github/workflows/ci.yml:

Line 185 (test job): Remove --index-url https://download.pytorch.org/whl/cpu
Line 247 (test-extras job): Remove --index-url https://download.pytorch.org/whl/cpu
Line 289 (test-agno job): Remove --index-url https://download.pytorch.org/whl/cpu
Line 315 (test-dashboard-ui job): Remove --index-url https://download.pytorch.org/whl/cpu

If index-url must be used, it can be replaced with --extra-index-url. Is there a reason why it was added in the first place? PyPI should handle this on it's own

[JerrettDavis]

Reviewed the CRLF normalization change and the added regression coverage. Focused governance tests passed locally and current checks are green.

[JerrettDavis]

This PR is not merge-ready because CI is currently red: test (3)=FAILURE, test (2)=FAILURE. Please fix or rerun the failing checks after updating from current main.