eeeea6f204
The non-interactive --custom-content CLI flag builds a customContentConfig object missing the `sources`, `selected`, and `selectedFiles` properties that the installer expects. This causes findModuleSource() to fail with "Source for module X is not available" because customModulePaths is never populated. Align both CLI code paths (modify and fresh install flows) with the config shape produced by the interactive promptCustomContentSource() method. Fixes #1623 |
||
|---|---|---|
| .. | ||
| cli | ||
| docs | ||
| lib | ||
| maintainer | ||
| schema | ||
| bmad-npx-wrapper.js | ||
| build-docs.mjs | ||
| fix-doc-links.js | ||
| format-workflow-md.js | ||
| migrate-custom-module-paths.js | ||
| platform-codes.yaml | ||
| validate-agent-schema.js | ||
| validate-doc-links.js | ||
| validate-file-refs.js | ||
| validate-svg-changes.sh | ||