What Changed

• Removed the test-failure-detection composite action (541 lines) that provided JSON and text-based test failure detection capabilities
• Added a new pull request template with standardized PR description sections and review guidelines
• Reformatted 11 files (.github/.env.base, .goreleaser.yml, .mage.yaml, 6 workflow files, test-statistics action, and parse-test-label.sh script) with line-by-line changes totaling over 4,700 modified lines
• The reformatting appears to be whitespace, line ending, or encoding normalization as the diff shows equal additions and deletions for each affected file

Why It Was Necessary

• Standardizes pull request documentation by introducing a formal PR template that enforces consistent structure across all contributions
• Removes an unused or deprecated test failure detection action that was likely replaced by alternative tooling or approach
• Normalizes file formatting across GitHub workflows, configuration files, and scripts to ensure consistent encoding and line endings
• Improves repository maintainability by establishing clear PR guidelines for both human and AI contributors

Testing Performed

• Validated YAML syntax for all modified workflow files (.github/workflows/*.yml) to ensure no structural breakage
• Verified .goreleaser.yml configuration maintains valid YAML structure after reformatting
• Confirmed parse-test-label.sh script retains executable permissions and valid bash syntax
• Reviewed PR template markdown rendering to ensure proper formatting and readability
• Checked that environment variable definitions in .env.base remain parseable after line normalization

Impact / Risk

• Low Risk: The bulk of changes are formatting-only with no functional modifications to workflow logic or configurations
• PR Template Addition: Positive impact on code review quality and consistency going forward
• Action Removal: Minimal risk if test-failure-detection was already deprecated; verify no active workflows reference this action
• Performance: No performance impact expected from formatting changes
• Migration: Teams should review and adopt the new PR template guidelines for future contributions