[mrz1836]

What Changed

• Added new t3.json configuration file with 11 script definitions for common development tasks (formatting, testing, linting, building, dependency management, and versioning)
• Updated runner OS from ubuntu-24.04 to ubuntu-26.04 in 2 workflow files and core environment configuration (PRIMARY_RUNNER and SECONDARY_RUNNER)
• Updated documentation in github-workflows.md to reference ubuntu-26.04 instead of ubuntu-latest in examples
• Bumped MAGE_X_VERSION from v1.27.2 to v1.27.3 in mage-x environment configuration
• Updated MAGE_X_GOLANGCI_LINT_VERSION and GO_PRE_COMMIT_GOLANGCI_LINT_VERSION from v2.13.2 to v2.14.0
• Updated CodeQL GitHub Action from commit 1c5b675653bb5c22dbe9b12b556ec555138e09fd (v4.38.1) to 2892aa5e19bbd11bc0cff5427e3b750a04d9e3c2 (v4.38.2) across 3 workflow files
• Changed matrix OS default in setup-redis-service action from ubuntu-24.04 to ubuntu-26.04
• Added new step in fortress-benchmarks.yml to redirect Go build temp directory from tmpfs /tmp to root disk on Linux runners to prevent "No space left on device" errors during benchmark binary linking

Why It Was Necessary

• The t3.json file provides a centralized task runner configuration for common development workflows, improving developer experience
• Migration to ubuntu-26.04 runners aligns with updated GitHub Actions infrastructure
• The Go temp directory redirect solves disk space issues on ubuntu-26.04 where /tmp is a small RAM-backed tmpfs that overflows when linking large cgo/sqlite binaries during benchmark runs
• Dependency version updates (mage-x, golangci-lint, CodeQL) incorporate latest bug fixes and improvements

Testing Performed

• Configuration file changes are declarative and will be validated by their respective workflow executions
• Runner OS changes maintain compatibility as ubuntu-26.04 is a GitHub-provided runner with consistent environment
• The benchmark temp directory fix addresses a specific observed failure mode ("disk quota exceeded" during linking) and includes disk space validation output
• Version bumps for development tools follow semantic versioning and are tested through CI pipeline execution

Impact / Risk

• Low Risk: Changes are primarily infrastructure and tooling updates that maintain existing functionality
• No Breaking Changes: All modifications preserve existing behavior while fixing resource constraints
• Improved Reliability: The benchmark disk space fix prevents spurious test failures that were occurring on ubuntu-26.04 runners
• Monitoring Required: First runs on ubuntu-26.04 runners should be monitored to ensure compatibility with all CI jobs

[mrz1836]

LGTM!