cd5b5c2a31
Keep customModules in the generated main manifest so local custom module source paths survive update runs. Load those preserved source paths during stock quick update before falling back to the custom cache directory. This fixes the case where BMAD would drop customModules, lose the original source path for a local module, and then skip the module or try to re-cache from _bmad/_config/custom/<module>, which could fail with ENOENT after the cache directory was removed. Also adds an installation component regression test to verify customModules and sourcePath are preserved in manifest generation. Fixes #1582 |
||
|---|---|---|
| .. | ||
| config.js | ||
| custom-module-cache.js | ||
| existing-install.js | ||
| install-paths.js | ||
| installer.js | ||
| manifest-generator.js | ||
| manifest.js | ||