alexandre.azouri 8c0f856839 fix: resolve custom module.yaml from installed location during manifest generation ... - resolveInstalledModuleYaml now checks _bmad/<module>/module.yaml first so freshly-installed custom/community modules are found immediately - manifest-generator passes bmadDir to resolveInstalledModuleYaml for lookup - removes 'could not locate module.yaml' warnings during custom module install - allows agents declared in custom module.yaml to be registered in config.toml		2026-05-11 13:54:10 +02:00
..
config.js	feat(installer): add --set and --list-options for non-interactive config (#2354)	2026-04-28 20:15:57 -05:00
existing-install.js	fix(installer): replace fs-extra with native node:fs to prevent file loss	2026-04-13 00:44:28 -05:00
install-paths.js	refactor(skills): remove bmad-skill-manifest yaml; introduce central config.toml (#2285)	2026-04-19 23:11:44 -05:00
installer.js	refactor(catalog): rename after/before to preceded-by/followed-by (#2360)	2026-05-01 12:28:50 -07:00
legacy-warnings.js	feat(installer): expand to 42 platforms with shared target_dir coordination (#2313)	2026-04-25 21:14:00 -05:00
manifest-generator.js	fix: resolve custom module.yaml from installed location during manifest generation	2026-05-11 13:54:10 +02:00
manifest.js	fix: installer live version for external modules (#2307)	2026-04-24 13:13:56 -05:00