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 |
||
|---|---|---|
| .. | ||
| agent | ||
| activation-builder.js | ||
| agent-analyzer.js | ||
| agent-party-generator.js | ||
| cli-utils.js | ||
| config.js | ||
| file-ops.js | ||
| platform-codes.js | ||
| project-root.js | ||
| prompts.js | ||
| ui.js | ||
| xml-handler.js | ||
| xml-to-markdown.js | ||
| yaml-format.js | ||
| yaml-xml-builder.js | ||