fix: ship the migration-acceptance agent with the addon - #14
Open
gkastanis wants to merge 1 commit into
Open
Conversation
.claude/agents/migration-acceptance.md exists in the repo since 30 Jun but was never listed in install.yaml project_files, and the post-install move only carried .claude/skills - so no installed project ever received the agent the workflow's Step 10 dispatches. Add the agents dir to project_files and extend the move action to carry it.
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
.claude/agents/migration-acceptance.mdhas been in DDEV-migration-addon since 30 June, butinstall.yamlnever ships it: the agents directory is not inproject_files, and the post-install move only carries.claude/skills. So every installed project gets the workflow's Step 10 instruction (dispatch the migration-acceptance agent) with no agent to dispatch.This adds
.claude/agentstoproject_filesand extends the existing move action to carry the agents directory to the project root alongside the skills.How I verified
I instrument migration runs with an eval harness (transcripts included). Across every instrumented run of the addon-installed flow, the acceptance agent was dispatched zero times, because it does not exist on the installed project. After installing this fix's layout manually on a fresh bed, the agent registers and is visible to Claude Code.
One caveat worth its own look: even with the agent installed and registered, a full migration run of a real site still ended with no Step 10 dispatch and no findings file. So this fix is necessary but the workflow step itself may also need attention - happy to share the run transcript.