fix(installer): restore automator install compatibility#2390
Closed
dickymoore wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Superseded by #2391. This narrower draft only fixes the stale installed-module update failure ( retained in existing manifests) and leaves broader Automator installability work out of scope. |
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
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.
Summary
Restore BMad Automator install/update compatibility in the BMAD installer.
Problem
Current installer behavior has two linked problems:
baut, while the bundled BMAD module registry currently advertisesautomatorskills/module.yaml, butbmad-automatoris a pure-skill payload repo and does not ship that module definition pathThat combination makes
quick-update/ reinstall runs treat an installed Automator as having no source, producing:Skipping 1 module(s) - no source available: bautand then removing the existing Automator install as if it were deselected.
Scope
This PR is intentionally limited to the installer compatibility path for that failure:
bautfor compatibility with existing installsautomatorandbmad-automatoras CLI aliases forbaut--yesexisting-install runs onto the full update path when explicit module/channel/tool flags are present, so commands like--modules automator --next automatorare not silently downgraded to quick-updatesource-rootsupport to external official module resolutionpayload/.claude/skillssource/scripts,source/src) into the installedbmad-story-automatorskill during installOut of Scope
Validation
node test/test-installation-components.jsnpm run test:refsnpm run test:installnpm run test:urlsnpm run test:channelsnpm run lintnpm run lint:mdnpm run format:check