[Sync] Update project files from source repository (828bb48)

[mrz1836]

What Changed

• Updated 1 individual file(s) to synchronize with the source repository
• Synchronized 1 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 c8f1b74

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: 886ms

.github/workflows → .github/workflows

• Files synced: 1
• Files examined: 24
• Files excluded: 0
• Processing time: 4700ms

.github/actions → .github/actions

• Files synced: 0
• Files examined: 16
• Files excluded: 0
• Processing time: 3909ms

.vscode → .vscode

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

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

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

Performance Metrics

• Files processed: 82 (2 changed, 0 deleted, 80 skipped)
• Files attempted to change: 2 (go-broadcast processing)
• File processing time: 7198ms

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

[Copilot]

Pull Request Overview

Sync PR aligning workflow and devcontainer configuration with source repository changes.

• Replaces magex vet invocation in CI with a custom sequential go vet loop.
• Updates devcontainer to install magex from a different module path.
• Adjusts workflow summary text to reflect sequential execution.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
.github/workflows/fortress-code-quality.yml	Swaps magex vet for a manual per-package sequential go vet loop and updates execution description.
.devcontainer.json	Changes magex installation source module path.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Filtering with 'grep -v /vendor/' may inadvertently exclude legitimate packages whose import path contains '/vendor/' as a directory name, causing incomplete vet coverage. Also, with Go modules, 'go list ./...' already omits vendored dependency packages, making this filter unnecessary. Replace with: PACKAGES=$(go list ./... 2>/dev/null).

Suggested change

	PACKAGES=$(go list ./... 2>/dev/null | grep -v /vendor/)
	PACKAGES=$(go list ./... 2>/dev/null)