refactor: sync version metadata from a single release source

[BraedenBDev]

Summary

Version metadata has drifted across the public surfaces of the project.

Current examples from main:

• package.json => 1.4.4
• .claude-plugin/plugin.json => 1.4.1
• .claude-plugin/marketplace.json => 1.4.1
• generate-compare-html.sh footer => v1.4.0
• compute-score.sh JSON output version => 0.2.0

This is not the most severe defect in the repo, but it is exactly the kind of release-hygiene problem that creates confusion for users, bug reports, and support.

Why this matters

When users report issues from the CLI, plugin installer, generated report, or JSON output, it should be obvious which release they are actually running.

Right now, different surfaces can claim different versions for the same checkout.

Suggested fix

1. Choose a single source of truth for the version.
2. Derive all secondary manifests and report strings from that source at release time.
3. Add a CI or release check that fails if public version surfaces drift.

Acceptance criteria

• Public version surfaces all agree for a release.
• Generated reports and JSON output identify the same release the package/plugin ships.
• CI or release automation detects future drift automatically.

[BraedenBDev]

Visible version drift was reduced in commit 4061b5b by syncing the current public manifests and generated-report version strings. I’m leaving this open because the stronger goal in this issue — deriving every surface from a single release source automatically — is still not implemented.

[BraedenBDev]

Visible version drift was reduced in commit 4061b5b by syncing the current public manifests and generated-report version strings. I am leaving this open because the stronger goal in this issue, deriving every surface from a single release source automatically, is still not implemented.