What Changed

• Added a new pull request template file (.github/pull_request_template.md) that provides a standardized four-section structure for PR descriptions
• Reformatted whitespace and line endings across multiple GitHub workflow files including fortress completion tests, statistics, fuzz testing, and validation workflows
• Updated the parse-test-label shell script with normalized formatting while preserving all functional logic
• Synchronized 6 total files to ensure consistent formatting and structure across the CI/CD pipeline configuration

Why It Was Necessary

• Establishes a consistent pull request documentation standard with required sections (What Changed, Why It Was Necessary, Testing Performed, Impact/Risk) to improve review quality and accountability
• Normalizes line endings and formatting across workflow files to prevent diff noise and ensure consistent behavior across different development environments
• Brings GitHub Actions workflow configurations and scripts into alignment with standardized formatting conventions used in related projects
• Improves maintainability by applying uniform code style across all automation and CI/CD configuration files

Testing Performed

• Validated YAML syntax of all modified GitHub workflow files to ensure no parsing errors were introduced
• Verified the pull request template renders correctly in GitHub's PR creation interface
• Confirmed shell script functionality remains unchanged after formatting updates by reviewing the logical structure
• Cross-referenced workflow file changes to ensure no semantic modifications were made, only formatting adjustments
• Tested that the new PR template appears automatically when creating new pull requests

Impact / Risk

• Low Risk: Changes are primarily cosmetic formatting updates and addition of a documentation template
• No Breaking Changes: All workflow logic and script functionality remains identical
• Developer Experience: Improved through standardized PR template that guides contributors toward complete, well-documented pull requests
• CI/CD Stability: No impact to pipeline execution as workflow definitions maintain identical behavior despite formatting changes