Decide handling for failed v0.1.12 release tag

[intel352]

During the #23/#24 release metadata work, the first post-merge release attempt created tag v0.1.12 but GoReleaser failed before publishing a GitHub release because plugin.json had been rewritten before GoReleaser's clean-tree validation.

#24 fixed the workflow by moving manifest generation into GoReleaser before hooks, and v0.1.13 was released successfully afterward. The repository still has a v0.1.12 tag with no corresponding release.

Options to decide explicitly:

• keep v0.1.12 as immutable failed-release history
• delete the tag because no release was published
• document v0.1.12 as intentionally skipped in release notes or registry metadata

Context:

• failed run: https://github.com/GoCodeAlone/workflow-plugin-product-capture/actions/runs/27070798168
• successful release: https://github.com/GoCodeAlone/workflow-plugin-product-capture/releases/tag/v0.1.13

[intel352]

Resolved by deleting the failed orphan tag v0.1.12 from the remote and local refs. There was no GitHub release for v0.1.12, and v0.1.13 is the published successor release with generated metadata verified in the archive.