Repository navigation
Fixes
-
All fifteen resolver call sites pass
--project-root(#44).resolve_customization.pyworked out the project root by itself when the flag was absent, walking up from the skill's installed directory. For a skill installed under your home directory that walk reaches~, and a user-level BMad install leaves a~/_bmadsitting there — so the resolver decided home was the project, found no override, and returned shipped defaults. A_bmad/custom/bmad-cis-*.tomlin the actual project was never opened, and nothing reported it.Whether an override took effect therefore depended on where its skill happened to be installed, which the override's author cannot see from the override. Two people with identical checkouts could get different behavior depending on whether either had ever run a user-level install.
The resolver itself is fixed upstream in BMAD-METHOD#2802, and that is what repairs an existing install — CIS ships no copy of the script and calls core's, so the fix arrives with your next core upgrade. Passing the root explicitly is the other half: nothing is left to infer, and it matches
resolve_config.py, which has always required the flag. Six agents, four workflows, and theworkflow.on_completeterminal hooks are covered.
Maintenance
- Marketplace plugin version synced to 0.3.2 — nothing in the release workflow touches
.claude-plugin/marketplace.json, so its version drifts frompackage.jsonunless bumped by hand.