[robzolkos]

Why

The basecamp-cli entry, and its basecamp alias, install whatever is on basecamp-cli's main (marketplace.json L10–L24 @ 663bcac). The plugin's skills run the basecamp command, which people install from releases. So between releases, a fresh install can get skills that call commands no released CLI has. 4, 5 and 8 commits touched basecamp-cli's skills/ in the last three release cycles.

What

• Both Basecamp entries get "ref": "stable". bin/check-marketplace requires the alias to share basecamp-cli's source, so they change together.
• basecamp-cli's release workflow fast-forwards stable to each stable release once it has published (basecamp/basecamp-cli#925). After that, a release changes nothing in this repo.
• The README says why the ref is there, and its basecamp-cli link points at stable.

HEY, Fizzy and the house-skills plugins are unchanged. HEY and Fizzy could do the same once their release workflows promote a stable branch.

This replaces #12, which pinned commit shas with an hourly workflow here. With a stable branch, nothing lags a release by up to an hour, and nobody has to merge a PR here for each release.

Ready to merge

stable already exists in basecamp-cli at v0.14.0 (2dbca87a), the latest release. That's also what main is today, so merging this changes nothing anyone installs until the next release.

Verified locally

• Validation: bin/check-marketplace passes, and so does claude plugin validate .. Its only warning, a missing marketplace description, is already on main.
• Claude Code, in a fresh CLAUDE_CONFIG_DIR with this branch as the marketplace: basecamp-cli and basecamp both installed 0.14.0 at 2dbca87a.
• Codex 0.163.0, in a fresh CODEX_HOME: basecamp-cli installed 0.14.0, and its basecamp-connect/SKILL.md is byte-identical to v0.14.0's.
• The ref is really followed. Since stable and main are the same commit today, I also pointed a scratch copy of this marketplace at v0.13.2. Claude Code installed 0.13.2 at d742884a, and Codex installed 0.13.2 with v0.13.2's basecamp-connect skill.
• stable only moves forward. On the new branch, setting it to the commit it already points at succeeds, which is what a re-run of the release job does. Setting it back to v0.13.2 with force=false was refused with Update is not a fast forward (HTTP 422), and stable stayed at v0.14.0.

Companion: basecamp/basecamp-cli#925. Card: https://app.basecamp.com/2914079/buckets/48521764/card_tables/cards/10423396016

[Copilot]

🟢 Approved

Both entries consistently select stable, the documentation matches, and no blocking issues were identified.

No open issues 🎉

What changed in this PR

Aligns Basecamp plugin skills with released CLI versions by installing from stable instead of main.

Changes:

• Sets ref: stable for both basecamp-cli and its basecamp alias.
• Updates the README link and explains release-driven branch promotion.

[!TIP]
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.

File	Description
README.md	Documents stable-branch installation and updates the plugin link.
.claude-plugin/​marketplace.json	Selects stable for both Basecamp entries.

_{Review effort: Balanced}