What Changed

• Created a new composite action .github/actions/upload-artifact-resilient/action.yml that wraps GitHub's artifact upload with step-level retry logic (3 attempts with escalating delays of 10s and 30s)
• Added inputs for artifact-name, artifact-path, retention-days, if-no-files-found, compression-level, and continue-on-error configuration
• Configured the action to use overwrite: true on all upload attempts to handle partially-finalized artifacts and sets ACTIONS_UPLOAD_RETRY_COUNT=3 for defense-in-depth
• Updated 7 workflow files (fortress-benchmarks.yml, fortress-completion-statistics.yml, fortress-code-quality.yml, fortress-coverage.yml, fortress-security-scans.yml, fortress-test-fuzz.yml, fortress-test-matrix.yml, fortress-test-validation.yml) to use the new resilient upload action
• Modified 2 environment files (.github/env/10-coverage.env and .github/env/10-pre-commit.env) with version updates

Why It Was Necessary

• Addresses transient GitHub infrastructure failures during artifact uploads, including non-retryable 403 errors from CDN/proxy intermediaries during finalization
• Provides centralized retry logic and error handling across all workflows to improve CI/CD reliability
• Reduces workflow failures caused by intermittent GitHub Actions artifact service issues

Testing Performed

• Verified the composite action syntax follows GitHub Actions composite action specifications
• Confirmed all workflow files correctly reference the new action with appropriate input parameters
• Validated that retry logic with escalating delays (10s, 30s) and overwrite behavior is properly configured

Impact / Risk

• Low Risk: Changes wrap existing upload functionality with additional resilience, no breaking changes to artifact behavior
• Improved Reliability: Step-level retries will reduce transient upload failures across all workflows
• Backwards Compatible: Workflows continue to produce the same artifacts with the same names and retention policies