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

[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 7dbf7bf

Directory Synchronization Details

The following directories were synchronized:

.vscode → .vscode

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

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

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

.github/ISSUE_TEMPLATE → .github/ISSUE_TEMPLATE

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

.github/workflows → .github/workflows

• Files synced: 13
• Files examined: 26
• Files excluded: 0
• Processing time: 4505ms

.github/actions → .github/actions

• Files synced: 1
• Files examined: 16
• Files excluded: 0
• Processing time: 2646ms

Performance Metrics

• Files processed: 84 (16 changed, 0 deleted, 68 skipped)
• Files attempted to change: 16 (go-broadcast processing)
• File processing time: 7504ms

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
No data about Coverage
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]

Auto-merge command ignores configured PAT token

The auto‑merge job now runs gh pr merge with GH_TOKEN set to process.env.GITHUB_TOKEN and no longer injects secrets.GH_PAT_TOKEN. Repositories that relied on the PAT (e.g., to provide contents: write or use a maintainer identity) will now attempt to enable/disable auto‑merge with the default Actions token, which lacks those privileges and will return Resource not accessible by integration. The secret is still configured and the github-script step uses it, but the actual merge command cannot access it, so auto‑merge will silently stop working wherever the PAT was required.

Useful? React with 👍 / 👎.