[Sync] Update project files from source repository (c748998)

[mrz1836]

What Changed

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

Directory Synchronization Details

The following directories were synchronized:

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

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

.github/ISSUE_TEMPLATE → .github/ISSUE_TEMPLATE

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

.github/workflows → .github/workflows

• Files synced: 7
• Files examined: 26
• Files excluded: 0
• Processing time: 4913ms

.github/actions → .github/actions

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

.vscode → .vscode

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

Performance Metrics

• Files processed: 84 (8 changed, 0 deleted, 76 skipped)
• Files attempted to change: 8 (go-broadcast processing)
• File processing time: 7484ms

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

Here are some automated review suggestions for this pull request.

ℹ️ 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".

[chatgpt-codex-connector]

Don’t classify every advisory as a security PR

The new security check sets is_security=true whenever GitHub reports any advisory for the package, without checking whether the PR’s version change actually falls into a vulnerable range. securityVulnerabilities returns historic advisories for the package, so any dependency with a past CVE now gets marked as a security update and routed through the auto-merge-security path even for routine patch/minor bumps, bypassing the normal manual-review rules for those update types. This is a regression from the previous label/title-based detection and will auto‑merge non‑security Dependabot PRs for packages with existing advisories.

Useful? React with 👍 / 👎.