investigate: sync-plugin-version.yml did not trigger on v1.2.0 tag push

[intel352]

Symptom

The sync-plugin-version.yml workflow has trigger on: push: tags: ['v*'] and is in "active" state, but it did not fire when the v1.2.0 tag was pushed at 2026-05-16T21:15:50Z.

Evidence

• v1.2.0 tag push fired the Release workflow successfully (run 25973143798, completed 21:16:01Z)
• v1.2.0 tag push did NOT fire the Sync plugin.json version workflow — no run logged in GitHub Actions UI or via gh run list --workflow=sync-plugin-version.yml
• Same workflow fired correctly on v1.1.0 yesterday (run 25939862148, 10s, succeeded)
• Workflow file unchanged between v1.1.0 and v1.2.0 tag pushes
• gh workflow list shows the workflow as active
• Manual dispatch rejected (no workflow_dispatch trigger in the file)

Workaround applied

Manual sync PR #17 (one-line plugin.json version bump) opened and admin-merged at 21:47:28Z. plugin.json on main now matches the v1.2.0 release.

Investigation candidates

• GitHub Actions backend hiccup specific to this tag/repo (unlikely to be reproducible)
• Some interaction between the Release workflow's GoReleaser run and the Sync workflow's checkout step (race?)
• Branch-protection or permissions changes between yesterday and today
• Add a workflow_dispatch trigger so the workflow can be manually re-fired in future when this recurs

Priority

Low — the manifest hygiene issue is fixed for v1.2.0. Want to understand the failure mode before the next plugin tag (v1.2.1 / v1.3.0 will hit the same path).