What Changed

• Added new pull request template file to establish consistent PR description standards across the repository
• Reformatted 3 GitHub Actions workflow files (fortress-completion-tests.yml, fortress-coverage.yml, fortress-test-validation.yml) with significant whitespace and structural changes totaling over 3,800 lines modified
• Synchronized workflow configurations to align with updated CI/CD standards and formatting conventions
• Updated workflow file indentation and YAML structure while preserving functional logic and test execution paths

Why It Was Necessary

• Establishes consistent PR documentation requirements to improve code review quality and team communication
• Ensures GitHub Actions workflows follow standardized formatting conventions for better maintainability and readability
• Aligns repository infrastructure files with current best practices and organizational standards
• Provides clear template structure requiring teams to document changes, rationale, testing, and impact for every pull request

Testing Performed

• Validated YAML syntax correctness for all modified workflow files using yamllint
• Verified workflow file structure maintains functional equivalence after reformatting
• Confirmed pull request template renders correctly in GitHub UI
• Reviewed diff output to ensure no unintended logic changes in workflow execution steps
• Validated that workflow triggers, job dependencies, and action versions remain unchanged

Impact / Risk

• Low Risk: Changes are primarily formatting and documentation infrastructure with no functional code modifications
• No Breaking Changes: Workflow logic and execution paths remain functionally identical
• CI/CD Impact: Workflows will continue to execute as before with improved readability
• Developer Experience: New PR template will require additional documentation effort but improves review quality and project maintainability