Repository navigation
Conversation
…mmands for each machine In an adopting project, an upgrade merged and nothing changed on the machines. Moving the pin updates no installed plugin unless the marketplace auto-updates, which a third-party one doesn't by default; SETUP's Updating section updated only adf; and a plugin the upgrade turned on (adf-dev) was never installed. - The aplyca marketplace entry carries "autoUpdate": true beside its ref. /adf:adopt writes it and /adf:upgrade adds it, so a merged pin change reaches every teammate's next session, never past the pin. - /adf:upgrade ends with the commands for each machine: refresh the marketplace, install each plugin it turned on, update the rest, then /reload-plugins. It still installs nothing itself. - docs/SETUP.md § Updating updates every plugin the project turns on. - Decision 0041 (amends 0016), the changelog entry, and a static check that fails when the snippets, /adopt, or /upgrade lose autoUpdate or the commands. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mauricios
marked this pull request as ready for review
October 16, 2026 01:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
In an adopting project, an upgrade merged and nothing changed on the machines:
refupdates no installed plugin unless the marketplace auto-updates, and a third-party marketplace doesn't by default.docs/SETUP.md§ Updating updated onlyadf, so an installedadf-devoradf-connectstayed behind.adf-dev) was written intoenabledPluginsbut never installed, and nothing told the developer to install it.What changes (decision 0041, amends 0016)
"autoUpdate": trueon theaplycaentry inextraKnownMarketplaces, beside itsref./adf:adoptwrites it;/adf:upgradeadds it. Once a pin change merges, each teammate's installed plugins move to it in their next session — never past the pin./adf:upgradestep 6.5: the report and PR body give the commands for each machine —claude plugin marketplace update aplyca,claude plugin install <plugin>@aplyca --scope projectfor each plugin it turned on,claude plugin update <plugin>@aplycafor the rest, then/reload-plugins. The upgrade still installs nothing itself: that would run an unreviewed release on the machine.docs/SETUP.md§ Updating updates every plugin the project turns on, and explains whatautoUpdatecovers.autoUpdate./adopt, or/upgradeloseautoUpdateor the commands (verified failing with the snippet line removed).Trade-off
Teammates get a release when its upgrade merges, not when each chooses to update — the pin's purpose already, reviewed in the pull request.
Checks
./evals/run-evals.sh: all suites pass (192 static skill checks);scripts/build-committed.py --checkround-trips.🤖 Generated with Claude Code