What Changed

• Updated MAGE_X_VERSION from v1.13.0 to v1.15.0 in .github/.env.base
• Updated MAGE_X_GORELEASER_VERSION from v2.13.1 to v2.13.2 in .github/.env.base
• Updated MAGE_X_YAMLFMT_VERSION from v0.20.0 to v0.21.0 in .github/.env.base
• Added new MAGE_X_BENCHSTAT_VERSION=v0.0.0-20251208221838-04cf7a2dca90 configuration in .github/.env.base
• Added buy_me_a_coffee: mrz1818 funding option to .github/FUNDING.yml
• Updated Gitpod workspace configuration comments to be more generic (changed from "go-pre-commit" to "this project" and updated descriptions for magex usage)
• Added new GitHub Action for benchstat setup in .github/actions/setup-benchstat/action.yml
• Updated documentation in .github/tech-conventions/mage-x.md and .github/tech-conventions/README.md to reference benchstat functionality
• Added permissions: contents: read to .github/workflows/fortress-coverage.yml and .github/workflows/fortress-test-matrix.yml

Why It Was Necessary

• Updating mage-x and related tooling versions ensures the project benefits from latest bug fixes, features, and security improvements
• Adding benchstat support enables benchmark comparison and performance regression detection capabilities
• Adding explicit permissions to GitHub workflows follows security best practices by implementing least-privilege access

Testing Performed

• Version updates should be validated by CI pipeline executing successfully with new tool versions
• Benchstat action functionality should be verified through workflow runs that utilize the new setup action
• Updated GitHub workflow permissions should be confirmed to work correctly without breaking existing CI/CD operations

Impact / Risk

• Low Risk: Version bumps are incremental updates to build tooling that don't affect runtime code
• No Breaking Changes: Tool updates are contained to development/CI environment and don't affect application functionality
• Security Improvement: Explicit workflow permissions reduce potential attack surface by following principle of least privilege