BMAD-METHOD/tools/installer/core
Brian Madison ffcdaf7529 fix(installer): strip core-key pollution from [modules.*]; soften config headers
- writeCentralConfig now always strips core-module keys from every
  [modules.<code>] bucket, even when the module's schema is not
  available in src/ (external / marketplace modules like cis, bmb).
  Core values belong in [core] only; workflows read them directly.
- When the module's own schema IS available (built-in modules),
  also drop any key it does not declare as a prompt — same
  spread-pollution filter as before, now layered on top.
- Section-aware headers on both _bmad/config.toml and
  _bmad/config.user.toml: [core] / [modules.*] values are
  editable (installer reads them as defaults on next install);
  [agents.*] is regenerated from module.yaml and will be wiped —
  overrides for agents go in _bmad/custom/config*.toml instead.
2026-04-19 19:44:29 -05:00
..
config.js refactor(installer): restructure installer with clean separation of concerns (#2129) 2026-03-27 06:50:07 -06: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: remove bmad-skill-manifest yaml; introduce four-layer central config.toml 2026-04-19 19:44:29 -05:00
installer.js refactor: remove bmad-skill-manifest yaml; introduce four-layer central config.toml 2026-04-19 19:44:29 -05:00
manifest-generator.js fix(installer): strip core-key pollution from [modules.*]; soften config headers 2026-04-19 19:44:29 -05:00
manifest.js fix(installer): replace fs-extra with native node:fs to prevent file loss 2026-04-13 00:44:28 -05:00