[Sync] Update project files from source repository (16d1713)

[mrz1836]

What Changed

• Removed .github/.env.base - the monolithic 550+ line base configuration file
• Removed .github/.yamlfmt YAML formatting configuration file
• Removed .github/CODEOWNERS file defining code ownership
• Removed load-env composite GitHub Action (.github/actions/load-env/action.yml)
• Removed download-artifact-resilient composite GitHub Action (.github/actions/download-artifact-resilient/action.yml)
• Removed workflow documentation (.github/docs/workflows.md and .github/docs/repository-features.md)
• Removed all modular environment configuration files in .github/env/ directory:
  • 00-core.env, 10-pre-commit.env, 10-coverage.env, 10-mage-x.env, 10-security.env, 20-workflows.env, 20-redis.env
  • load-env.sh shell script for environment loading
  • README.md documentation for the env structure
• Removed technical convention documentation (.github/tech-conventions/commit-branch-conventions.md and .github/tech-conventions/pre-commit.md)
• Removed all GitHub workflow files:
  • dependabot-auto-merge.yml, auto-merge-on-approval.yml, codeql-analysis.yml, scorecard.yml, stale-check.yml, sync-labels.yml
  • fortress-*.yml workflows (coverage, completion-tests, setup-config, test-magex, warm-cache)
  • fortress.yml main workflow
  • pull-request-management.yml and pull-request-management-fork.yml

Why It Was Necessary

• Complete removal of GoFortress CI/CD infrastructure and related tooling configuration
• Elimination of the modular environment configuration system that replaced the monolithic .env.base approach
• Cleanup of all GitHub Actions workflows, composite actions, and associated documentation

Testing Performed

• Verify all .github/ directory files and subdirectories are properly removed
• Confirm no broken references to removed workflows or configuration files remain
• Validate repository can operate without the GoFortress CI/CD system

Impact / Risk

• Breaking Change: Complete removal of CI/CD infrastructure - all automated testing, security scanning, coverage reporting, and workflow automation will cease
• Risk: High - repository loses all GitHub Actions automation including PR management, dependency updates, security scanning, and test execution
• Migration: Projects depending on these workflows will need alternative CI/CD solutions configured

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Code Coverage Analysis

🟡 Overall Coverage: 88.7%
No Go files modified in this PR

Project coverage remains at 88.7% (1.7K/1.9K statements)

Changes: 30 config files

Coverage Metrics

Metric	Value	Grade	Trend
Percentage	88.7%	⭐ B+	📊
Statements	1.7K/1.9K	⭐ B+	No change
Quality Score	88.7/100	⭐ B+	📈

Coverage Breakdown

█████████████░░ 88.7%

Resources

• 📊 PR Coverage Report
• 🏷️ PR Coverage Badge

---

Generated via go-coverage • 2026-02-07 21:32:44 UTC