[mrz1836]

What Changed

• GOVULNCHECK_GO_VERSION: 1.27.2 → 1.27.3 (.github/env/00-core.env)
• The pull-request-management.yml workflow now also triggers on the synchronize event for same-repo PRs, so the "🔧 PR Management (Same Repo)" job runs on every new head commit.
• On synchronize runs, the label and default-assignee steps are skipped, and the step summary reports "None: new commits only". Concurrency for these runs uses a separate -push group, so a push right after a PR opens cannot cancel the run that labels it.
• Header comments and the "Trigger Configuration" notes were updated to explain the new behavior. Fork PR management through the workflow_run path still fires only on opened, reopened, ready_for_review and closed.

Why It Was Necessary

• A check run belongs to a single commit. A ruleset that requires the same-repo PR management check would block any PR pushed to after it was opened, because the new head never received the check.
• Running the job on synchronize without re-applying labels or the assignee reports the check on each new head. Maintainers can still override auto-applied labels without the workflow overwriting them on the next push.

Testing Performed

• No automated tests are included in this sync. The change is limited to workflow configuration and an env value.
• Validate by pushing a new commit to an open same-repo PR and confirming that the "🔧 PR Management (Same Repo)" check appears on the new head and that labels and assignee are unchanged.
• Also confirm that opened, reopened, ready_for_review and closed events behave as before, and that fork PRs still go through the workflow_run path.

Impact / Risk

• Risk: Low. The same-repo job now runs on each push, which adds a short run per push (10-minute timeout) but does no label or assignee work.
• Concurrency: Newer pushes cancel older synchronize runs in the -push group, which is acceptable because the older commit is no longer the head. Runs for the other events keep their original group and are not affected.
• Breaking changes: None expected. Required-check behavior for PRs pushed to after opening should improve.