mirror of
https://github.com/bmad-code-org/BMAD-METHOD.git
synced 2026-11-02 13:01:59 +08:00
Murat K Ozcan
423690c3d7
* fix(skills): activation preflight checks required skills only against roots the caller names resolve_customization.py accepts repeated --root, in precedence order, and passes them to setup_check. Without roots, setup_check no longer claims a required skill or the module record is missing or outdated, since it cannot see the host's other active roots. Notes that need no root order stay. * fix(skills): report a tag-pinned install as pinned with the re-add command A module whose skills-lock entry carries a ref was reported newer-available, but npx skills update keeps the pin and cannot apply the newer version. Status now reports pinned with the command that adds the module again at the newer tag. * fix(skills): tickets find rejects a bare number that would fall back to the backlog With no folder, a bare number the initiative does not resolve was taken from the backlog file carrying that id. It now errors as ambiguous and lists the candidates. * fix(skills): preflight reads the record that wins the ordered roots and survives an unreadable file render_skill.py takes --root like the resolver. * fix(skills): only a version-tag ref counts as a pin A branch or commit ref is followed by npx skills update, so it stays newer-available. * fix(skills): a numeric tracker id still finds its backlog ticket and the bare-number error names the real case * fix(skills): pinned re-add command covers one scope; test the renderer preflight and pinned status The re-add command lists only the skills in the module record's scope. The renderer tests install setup_check and cover --root forwarding. Status tests cover pinned as a settled state. * fix(skills): a numeric tracker id wins over a backlog ticket's local id * feat(skills): build loads any run folder that names its ticket and container step-01 of bmad-build and bmad-build-auto reads the main document of any <type>-*/ run folder in the initiative or the ticket's epic folder whose ticket and container match. A document without container keeps the research rule. A loaded document that lists test files makes the plan include the work that turns them green. * feat(skills): retrospective gathers the epic's run folders and companions * fix(skills): migration rewrites a module config path that moves with the planning folder * fix(skills): match a run's container by the folder find names, carry test work into oneshot plans, align companions and the migration check * fix(skills): mirror leaves a bare number out of the backlog, and a pin needs the lock entry to name the module's repository * fix(skills): match a run's container by its last folder name and have the build run the listed tests * docs: describe v7 module install and the three-file config model * docs: mark the plugin marketplace route not v7-ready * docs(skills): core-tools help names how to add the Test Architect * docs: list external modules that restate the ticket tree rules * fix(skills): bmad-customize points to bmad-toolsmith for custom skills * docs: align the config and module pages with setup behavior * docs: call team settings defaults a personal file can override, and note single-skill modules * fix(skills): no re-add command for an untagged pre-release, and the backlog help names the tracker id exception * fix(skills): listed tests get a Verification command that blocks completion, and the migration rewrites each layer that holds the moved path * fix(skills): a released pinned module from a non-GitHub source says to re-add it from its source * fix(skills): bmad-build runs the plan's Verification commands before review * fix(skills): bmad-customize recommends bmad-toolsmith only when installed