[bruno-archastro]

Summary

• Use the CLI release tag as the published OpenCode npm package version rather than requiring it to equal the generated plugin catalog version.
• Keep the main-ancestry guard, committed package/catalog consistency checks, and plugin test gate; stamp only the artifact's package.json after those checks pass.
• Add nine regression tests and document the release and dry-run behavior.

Why

CLI releases create v<version> tags at this repository's current main without updating the plugin catalog. The latest failed publication used v0.54.2 while the catalog and generated package remained 0.49.7:
https://github.com/ArchAstro/archdev/actions/runs/39069473389

A one-time catalog bump would fail again with the next independent CLI release. This separates the artifact version from the generated bundle version while preserving source validation.

Verification

On Node 24.16.0:

• npm --prefix tools/plugin-gen run typecheck
• npm --prefix tools/plugin-gen test — all 74 tests pass, including actual npm pack verification of the tag-derived artifact version.
• npm --prefix tools/plugin-gen run check — all 140 generated files match.

Also checked the resolver on Node 22.23.2, parsed the workflow YAML, and verified ancestry/test gates and preparation ordering.

Limitations

• This applies to release tags created after merge. Existing tags are unchanged; rerunning their old workflows will still fail.
• Local tests do not verify hosted npm OIDC/provenance. No npm publication was performed.

Agent session: 01a154a9-893f-70ea-a078-0be4e3af06c8