[emaarco]

Why

The marketplace entry "source": "./plugins/bpmn-cli" resolves against the marketplace clone, which is the tip of main. A fresh install can therefore get a skill ahead of its CLI (as between #15 and 0.5.0), or one that pins an npx version npm does not have yet (between the release PR merge and npm publish). A copy installed in such a window carries the release's version string, so claude plugin update keeps it until the next release.

What

• marketplace.json: the plugin comes from a git-subdir source on https://github.com/Miragon/bpmn-cli.git, path plugins/bpmn-cli, ref: release. The plugin id stays bpmn-cli@miragon-bpmn, so existing installs update without a reinstall.
• release-please.yml: new job plugin-release-branch, after publish. It fast-forwards release to the release tag through the GitHub API (force=false); contents: write is scoped to this job.
• docs/releasing.md: the new step, why the branch exists, and how to recover from a failed move.
• test/e2e/plugin.test.ts: checks the new entry and that its path holds the plugin.
• The branch release already exists at v0.8.0 (created through the API), so the entry resolves from the moment this is merged.

Verification

• claude plugin validate --strict . and plugins/bpmn-cli pass.
• vitest run test/e2e/plugin.test.ts -t "plugin metadata" passes.
• Install from this branch's marketplace with an empty CLAUDE_CONFIG_DIR: installs bpmn-cli@miragon-bpmn 0.8.0 from release.
• The job's API call against release: the same sha succeeds; moving it back to v0.7.0 is refused with 422 Update is not a fast forward.

Closes #19 together with #124.