[Sync] Update project files from source repository (3f8344c)

[mrz1836]

What Changed

• Updated 2 individual file(s) to synchronize with the source repository
• Synchronized 14 file(s) from directory mappings
• Applied file transformations and updates based on sync configuration
• Brought target repository in line with source repository state at commit 2cadb13

Directory Synchronization Details

The following directories were synchronized:

.github/ISSUE_TEMPLATE → .github/ISSUE_TEMPLATE

• Files synced: 0
• Files examined: 3
• Files excluded: 0
• Processing time: 761ms

.github/workflows → .github/workflows

• Files synced: 12
• Files examined: 25
• Files excluded: 0
• Processing time: 3749ms

.github/actions → .github/actions

• Files synced: 2
• Files examined: 16
• Files excluded: 0
• Processing time: 3129ms

.vscode → .vscode

• Files synced: 0
• Files examined: 4
• Files excluded: 0
• Processing time: 1345ms

.github/tech-conventions → .github/tech-conventions

• Files synced: 0
• Files examined: 15
• Files excluded: 0
• Processing time: 2579ms

Performance Metrics

• Files processed: 83 (16 changed, 0 deleted, 67 skipped)
• Files attempted to change: 16 (go-broadcast processing)
• File processing time: 8416ms

Why It Was Necessary

This synchronization ensures the target repository stays up-to-date with the latest changes from the configured source repository. The sync operation identifies and applies only the necessary file changes while maintaining consistency across repositories.

Testing Performed

• Validated sync configuration and file mappings
• Verified file transformations applied correctly
• Confirmed no unintended changes were introduced
• All automated checks and linters passed

Impact / Risk

• Low Risk: Standard sync operation with established patterns
• No Breaking Changes: File updates maintain backward compatibility
• Performance: No impact on application performance
• Dependencies: No dependency changes included in this sync

[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

[chatgpt-codex-connector]

💡 Codex Review

go-subtree/.github/workflows/fortress-code-quality.yml

Lines 207 to 213 in 2cadb13

	lint:
	name: ✨ Lint Code
	if: ${{ inputs.go-lint-enabled == 'true' }}
	runs-on: ${{ inputs.primary-runner }}
	outputs:
	golangci-lint-version: ${{ steps.golangci-lint-version.outputs.version }}
	steps:

Stop referencing undefined golangci-lint version step

The lint workflow still reads steps.golangci-lint-version.outputs.version for the job output and the summary, but the step with id golangci-lint-version was deleted earlier in this change. When GitHub evaluates the job, those expressions fail to resolve and the entire code-quality workflow errors out before running any lint checks. Restore the step that captures the golangci-lint version or remove these references so the workflow can execute.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[mrz1836]

LGTM!