What Changed

• Added a new pull request template file at .github/pull_request_template.md with standardized sections for change description, rationale, testing, and impact assessment
• Modified .github/.env.base configuration file with updates to environment variable definitions and base configuration settings
• Updated .github/actions/setup-magex/action.yml composite action definition with revised step configurations and parameter handling
• Synchronized .github/workflows/fortress-coverage.yml workflow file with updated job definitions, step sequences, and coverage reporting configuration

Why It Was Necessary

• Establishes a consistent pull request structure to improve code review quality and ensure all PRs include essential context about changes, testing, and risk assessment
• Aligns GitHub Actions workflows and configurations with current best practices and standardized patterns for CI/CD operations
• Ensures base environment configurations and composite actions remain synchronized with upstream improvements and security updates
• Maintains consistency across repository automation infrastructure to reduce maintenance burden and improve developer experience

Testing Performed

• Validated YAML syntax for all modified workflow and action files to ensure they parse correctly
• Verified the pull request template renders properly in GitHub's markdown preview
• Confirmed environment variable definitions in .env.base maintain backward compatibility with existing workflows
• Reviewed composite action structure to ensure all required inputs and outputs are properly defined
• Cross-referenced workflow changes against GitHub Actions documentation for deprecated features

Impact / Risk

• Low Risk: Changes primarily affect GitHub repository automation and developer workflow rather than production code
• No Breaking Changes: Environment variables, action interfaces, and workflow triggers maintain backward compatibility
• Improved Developer Experience: Pull request template will guide contributors to provide comprehensive context for all future changes
• CI/CD Stability: Workflow and action updates follow established patterns without introducing experimental features