What Changed

• Added a new step "🎯 Enforce Coverage Threshold" to the fortress-coverage workflow that validates test coverage against the configured threshold
• The step locates the coverage file by searching three possible locations: coverage-artifacts/coverage-data/, coverage-artifacts/, and the repository root
• Uses the go-coverage parse command with --threshold flag to enforce minimum coverage requirements
• Fails the build with exit code if coverage drops below GO_COVERAGE_THRESHOLD, providing detailed error messages and remediation guidance
• The enforcement step only runs when GO_COVERAGE_THRESHOLD is set and not equal to '0' or '0.0'
• Includes informative output showing which coverage exclusions were applied during test generation (paths, files, tests, and generated code)

Why It Was Necessary

• Ensures that code coverage standards are automatically enforced during CI builds rather than relying on manual review
• Provides immediate feedback to developers when test coverage falls below acceptable thresholds
• Prevents regression in test coverage by failing builds that don't meet the minimum quality bar

Testing Performed

• The change adds enforcement logic that will be tested when the workflow runs with coverage data
• The step includes robust error handling for missing coverage files with clear diagnostic output
• Conditional logic ensures the threshold check only runs when explicitly configured

Impact / Risk

• Breaking Change: Builds may start failing if existing coverage is below the configured threshold
• Risk: Low - the enforcement is optional and only active when GO_COVERAGE_THRESHOLD is explicitly set to a non-zero value
• Developer Experience: Improved clarity on coverage requirements with actionable error messages explaining how to fix threshold failures