chore: apply plugin version discipline

[intel352]

Part of GoCodeAlone/workflow#760.

Changes:

• keep committed plugin.json.version at the 0.0.0 development sentinel
• add post-build release validation so the shipped manifest is checked against the tag

Verification:

• wfctl plugin validate-contract .
• wfctl plugin validate-contract --for-publish --tag v9.9.9 .
• GOWORK=off go test ./...

[Copilot]

Pull request overview

This PR enforces “version discipline” for the plugin manifest by keeping the committed plugin.json at a development sentinel version while adding CI validation to ensure the release artifacts’ manifest matches the Git tag.

Changes:

• Set the committed plugin.json.version to the 0.0.0 development sentinel.
• Add a post-build wfctl plugin validate-contract --for-publish check in the release workflow to validate the shipped manifest against the tag.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
plugin.json	Keeps the repository manifest at the 0.0.0 development sentinel.
.github/workflows/release.yml	Adds a post-build validation step intended to verify the release artifact’s manifest matches the tag.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.