Repository navigation
feat: the packaged install is the default (decision 0018) - #31
Merged
Merged
Conversation
/aplyca-adf:adopt recommends the packaged install by default, and the committed install when the team also uses another AI tool for the framework's skills or needs Claude Code's cloud sessions; it still asks. The packaged paths have run end to end in real sessions — the plugin's hooks, adopting on it, switching to it — and the next adoption, a new project, starts on it. /aplyca-adf:upgrade recommends the switch to a committed project whose team works in Claude Code only. The committed install stays fully supported; the manual setup is the committed install. Decision 0018 amends 0016 (status line only). README, SETUP, UPGRADING, and the plugin README say which is the default. The adopt eval's new-project case asks for the committed install, so that path keeps its own eval; a static check holds /adopt's default. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mauricios
marked this pull request as ready for review
October 5, 2026 03:36
# Conflicts: # CHANGELOG.md
mauricios
added a commit
that referenced
this pull request
Oct 5, 2026
…al sessions (#32) A minor release: the packaged install becomes the default for new projects (decision 0018), with evals for its paths. Unreleased becomes v1.1.0, covering #29, #30, #31, and one more fix: /aplyca-adf:adopt took the skeleton from wherever the framework source was while pinning the newest release tag, so a project's committed files could be newer than its pinned plugin. It now finds the newest release tag, takes the framework at that tag (a shallow clone of it, or a worktree of a local checkout), and stamps that tag's commit; SETUP.md's manual copy says the same. The packaged adopt eval reran on Sonnet: 8/8, stamped ab56cb6 from a scratch worktree at v1.0.6. plugin.json 1.1.0; the README names the release. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
What changed and why
The packaged install becomes the default (decision 0018, amending 0016). 0016 kept the committed install the default because the packaged install was new and unproven. It has now run end to end in real sessions:
plugin-hookssuite;packagedcase;switch-to-packagedcase.The next adoption, a new project, starts on it.
/aplyca-adf:adoptlists packaged first, as the default. It recommends committed when the team also uses another AI tool for the framework's skills (Cursor, Copilot, Gemini, Antigravity) or needs Claude Code's cloud sessions. It still asks./aplyca-adf:upgraderecommends the switch to packaged to a committed project whose team works in Claude Code only.docs/SETUP.mdis the committed install.new-projectcase now asks for the committed install, so that path keeps its own eval whilepackagedcovers the default. A static check holds/adopt's default.Upgrade impact
None. Existing projects keep their install until they choose to switch.
/aplyca-adf:upgradeoffers the switch.How to verify
./evals/run-evals.sh.Verified / not verified
packagedandnew-projectevals weren't rerun on the new wording. Only the order and the recommendation changed.Merge danger
/upgrade's stamp. Merge feat: evals for the packaged install's two ways in; /upgrade stamps the release's commit #30 first; the two PRs' CHANGELOG entries sit next to each other.🤖 Generated with Claude Code