Description
A clean install of the WDS community module selects/offers wds stable v0.3.1, but the completed installation records and reports WDS: Whiteport Design Studio (v0.1.0, installed).
During installation, the installer also emits warnings that it cannot locate module.yaml for wds:
[warn] collectAgentsFromModuleYaml: could not locate module.yaml for 'wds'. Agents declared by this module will not be written to config.toml.
[warn] writeCentralConfig: could not locate module.yaml for 'wds'. Answers from this module will default to team scope — user-scoped keys may mis-file into config.toml.
Community Modules
wds v0.1.0 ✓
All modules are up to date
Why this looks wrong
The installer flow offers:
wds: choose a channel
stable v0.3.1 (released version)
But the final output says:
WDS: Whiteport Design Studio (v0.1.0, installed)
The generated _bmad/_config/manifest.yaml records WDS as:
- name: wds
version: v0.1.0
source: community
npmPackage: bmad-method-wds-expansion
repoUrl: https://github.com/bmad-code-org/bmad-method-wds-expansion
channel: stable
registryApprovedTag: v0.1.0
However, WDS v0.3.1 exists as the current released version, and the repository tag v0.3.1 contains src/module.yaml.
wds: choose a channel
stable v0.3.1 (released version)
cd D:\tmp
mkdir bmad-wds-smoke-test
cd .\bmad-wds-smoke-test\
npx bmad-method install --modules wds
---
BMAD 6.5.0 clean install with:
npx bmad-method install --modules wds
Interactive flow offers:
wds stable v0.3.1
But final output reports:
WDS: Whiteport Design Studio (v0.1.0, installed)
`npx bmad-method status` also reports:
Community Modules
[WDS-installation-0.3.1.log](https://github.com/user-attachments/files/27103621/WDS-installation-0.3.1.log)
[bmad-wds-smoke-test.zip](https://github.com/user-attachments/files/27103632/bmad-wds-smoke-test.zip)
wds v0.1.0
During install there are warnings:
collectAgentsFromModuleYaml: could not locate module.yaml for 'wds'
writeCentralConfig: could not locate module.yaml for 'wds'
The generated `.agents/skills` and `.agent/skills` contain 24 skills total, including 12 WDS skills, so the skill payload seems installed. However `_bmad/_config/manifest.yaml` records WDS as community v0.1.0, not v0.3.1, and config.toml generation cannot read WDS module.yaml.
Expected:
WDS v0.3.1 should be reflected in manifest/status, and module.yaml should be found during config generation.
Description
A clean install of the WDS community module selects/offers
wds stable v0.3.1, but the completed installation records and reportsWDS: Whiteport Design Studio (v0.1.0, installed).During installation, the installer also emits warnings that it cannot locate
module.yamlforwds: