What Changed

• Added new parse-test-label.sh script in .github/scripts/ to provide consistent test labeling from artifact names
• Modified .github/.env.base with 502 line changes updating environment variable configurations
• Updated four GitHub Actions workflow files (fortress-completion-tests.yml, fortress-completion-statistics.yml, fortress-test-matrix.yml, fortress-test-validation.yml) with comprehensive line-by-line synchronization totaling over 2,400 line changes
• The new bash script implements parsing logic to extract test type, OS name, and Go version from artifact names to generate human-readable labels like "Unit Tests (Ubuntu, Go 1.22)"

Why It Was Necessary

• Synchronizes CI/CD workflow infrastructure with upstream improvements and standardizations
• Introduces centralized test labeling logic to ensure consistent reporting across different test execution contexts (unit tests, fuzz tests, CI results)
• Updates environment configurations to maintain compatibility with latest workflow requirements and improve test result presentation
• Ensures all Fortress testing workflows share consistent behavior and reporting formats

Testing Performed

• Validated YAML syntax of all four modified workflow files to ensure no parse errors
• Reviewed bash script for proper shell escaping and regex pattern matching
• Verified environment variable changes in .env.base maintain expected key-value formats
• Confirmed workflow file changes preserve existing job dependencies and artifact handling logic
• Checked that the new script helper integrates correctly with existing workflow calling patterns

Impact / Risk

• Low to Medium Risk: Changes affect CI/CD infrastructure but maintain backward compatibility with existing workflow structures
• No Breaking Changes: Workflow modifications are additive and improve existing functionality without removing features
• Testing Impact: Improved test result labeling will enhance visibility in CI reporting and make debugging easier
• Migration: No action required for developers; changes are transparent to local development workflows