bmad-method 6.9.1-next.21 → 6.9.1-next.23

package/bmad-modules.yaml

@@ -26,8 +26,39 @@
 # Interactive installs require the user to acknowledge it (press Enter);
 # non-interactive (--yes) installs print it and continue. Use for required
 # follow-up steps (e.g. "run the X setup skill").
+#
+# aliases (optional) — prior `code` values this module was registered under.
+# An existing install recorded under an alias resolves to this entry (source,
+# name, description, post-install message) instead of being orphaned as
+# "no source available" when the code changes. quick-update also migrates the
+# install to the new code and removes the stale `_bmad/<alias>/` directory.
 
 modules:
+  bmad-loop:
+    url: https://github.com/bmad-code-org/bmad-loop
+    module-definition: src/bmad_loop/data/skills/bmad-loop-setup/assets/module.yaml
+    code: bmad-loop
+    # bauto is the pre-rename code (module was bmad-auto before both the repo
+    # and its contents were renamed to bmad-loop); keeps existing bauto
+    # installs migrating forward instead of being orphaned.
+    aliases: [bauto]
+    name: "BMad Loop"
+    description: "Deterministic, Python-based unattended dev loop with adversarial review"
+    defaultSelected: false
+    type: bmad-org
+    default_channel: stable
+    # Skills live outside a single module.yaml dir; resolve them from
+    # .claude-plugin/marketplace.json via the plugin resolver (see external-manager).
+    marketplace-plugin: true
+    post-install-message: |
+      BMad Loop installed. To finish setup, run the bmad-loop-setup skill
+      from your agent:
+
+        > use the bmad-loop-setup skill
+
+      It installs the bmad-loop orchestrator tool and wires up the per-project
+      hooks and policy. The automation skills don't run until setup completes.
+
   bmad-method-test-architecture-enterprise:
     url: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise
     module-definition: src/module.yaml
@@ -61,28 +92,7 @@ modules:
     npmPackage: bmad-story-automator
     default_channel: next
     deprecated: true
-    deprecation-message: "BMad Automator has been deprecated and is replaced by BMad Auto (bmad-auto). Install BMad Auto instead."
-
-  bmad-auto:
-    url: https://github.com/bmad-code-org/bmad-auto
-    module-definition: src/automator/data/skills/bmad-auto-setup/assets/module.yaml
-    code: bauto
-    name: "BMad Auto"
-    description: "Automation-mode skills driven by the bmad-auto orchestrator: unattended dev, adversarial review, and deferred-work sweep triage"
-    defaultSelected: false
-    type: bmad-org
-    default_channel: stable
-    # Skills live outside a single module.yaml dir; resolve them from
-    # .claude-plugin/marketplace.json via the plugin resolver (see external-manager).
-    marketplace-plugin: true
-    post-install-message: |
-      BMad Auto installed. To finish setup, run the bmad-auto-setup skill
-      from your agent:
-
-        > use the bmad-auto-setup skill
-
-      It installs the bmad-auto orchestrator tool and wires up the per-project
-      hooks and policy. The automation skills don't run until setup completes.
+    deprecation-message: "BMad Automator has been deprecated and is replaced by BMad Loop (bmad-loop). Install BMad Loop instead."
 
   bmad-creative-intelligence-suite:
     url: https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.9.1-next.21",
+  "version": "6.9.1-next.23",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

package/removals.txt

@@ -63,3 +63,8 @@ bmad-create-ux-design
 # bmad-investigate: retired. Plain investigation reaches the same conclusions at
 # lower cost.
 bmad-investigate
+
+# Removed skills (v6.10.0)
+# bmad-auto-setup: renamed to bmad-loop-setup as part of the bmad-auto ->
+# bmad-loop module rename (BMad Automator's replacement).
+bmad-auto-setup

package/src/core-skills/bmad-help/SKILL.md

@@ -23,7 +23,7 @@ When this skill completes, the user should:
 ## Data Sources
 
 - **Catalog**: `{project-root}/_bmad/_config/bmad-help.csv` — assembled manifest of all installed module skills
-- **Config**: `config.yaml` and `user-config.yaml` files in `{project-root}/_bmad/` and its subfolders — resolve `output-location` variables, provide `communication_language` and `project_knowledge`
+- **Config**: Run `uv run --python 3.11 {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and use the merged JSON to resolve `output-location` variables and read `core.communication_language` and `modules.bmm.project_knowledge`. The resolver merges `_bmad/config.toml`, `_bmad/config.user.toml`, `_bmad/custom/config.toml`, and `_bmad/custom/config.user.toml` in that order.
 - **Artifacts**: Files matching `outputs` patterns at resolved `output-location` paths reveal which steps are possibly completed; their content may also provide grounding context for recommendations
 - **Project knowledge**: If `project_knowledge` resolves to an existing path, read it for grounding context. Never fabricate project-specific details.
 - **Module docs**: Rows with `_meta` in the `skill` column carry a URL or path in `output-location` pointing to the module's documentation (e.g., llms.txt). Fetch and use these to answer general questions about that module.

package/tools/installer/core/installer.js

@@ -1253,7 +1253,7 @@ class Installer {
 
   /**
    * Display registry-defined post-install messages for the modules installed in
-   * this run. These are "action needed" notices (e.g. "run the bmad-auto-setup
+   * this run. These are "action needed" notices (e.g. "run the bmad-loop-setup
    * skill") that the user must see to finish setup. They are defined via the
    * `post-install-message` property on a module's bmad-modules.yaml entry.
    *
@@ -1317,10 +1317,32 @@ class Installer {
 
     // Detect existing installation
     const existingInstall = await ExistingInstall.detect(bmadDir);
-    const installedModules = existingInstall.moduleIds;
     const configuredIdes = existingInstall.ides;
     const projectRoot = path.dirname(bmadDir);
 
+    // Resolve any legacy/aliased module codes (e.g. an install recorded as
+    // `bauto` before the registry renamed it to `bmad-loop`) to their current
+    // canonical code up front. Without this, a renamed module's old installs
+    // would fall out of `availableModuleIds` below and get silently frozen
+    // (see the `baut` → `automator` incident in CHANGELOG v6.7.1) instead of
+    // migrating forward.
+    const aliasMigrations = [];
+    const seenModuleIds = new Set();
+    const installedModules = [];
+    for (const rawId of existingInstall.moduleIds) {
+      const canonicalId = await this.externalModuleManager.resolveCanonicalCode(rawId);
+      if (canonicalId !== rawId) {
+        aliasMigrations.push({ from: rawId, to: canonicalId });
+      }
+      if (!seenModuleIds.has(canonicalId)) {
+        seenModuleIds.add(canonicalId);
+        installedModules.push(canonicalId);
+      }
+    }
+    for (const { from, to } of aliasMigrations) {
+      await prompts.log.info(`Migrating installed module '${from}' to its renamed successor '${to}'.`);
+    }
+
     // Get available modules (what we have source for)
     const availableModulesData = await new OfficialModules().listAvailable();
     const availableModules = [...availableModulesData.modules];
@@ -1465,6 +1487,18 @@ class Installer {
 
     await this.install(installConfig);
 
+    // Now that the canonical module has been installed successfully, remove
+    // the stale directory left behind under its old code so the two don't
+    // coexist (e.g. `_bmad/bauto/` once `_bmad/bmad-loop/` is in place).
+    for (const { from, to } of aliasMigrations) {
+      if (!modulesToUpdate.includes(to)) continue; // new code wasn't actually installed this run
+      const oldModuleDir = path.join(bmadDir, from);
+      if (await fs.pathExists(oldModuleDir)) {
+        await fs.remove(oldModuleDir);
+        await prompts.log.success(`Removed legacy '${from}' directory after migrating to '${to}'.`);
+      }
+    }
+
     return {
       success: true,
       moduleCount: modulesToUpdate.length,

package/tools/installer/core/uv-check.js

@@ -77,7 +77,7 @@ async function checkUvEnvironment() {
   const detected = module.exports.detectUv();
 
   if (detected) {
-    await prompts.log.success(`uv ${detected.version.raw} detected — ready to run BMAD's Python-powered scripts via \`uv run\`.`);
+    await prompts.log.success(`✅ Python UV check pass (uv ${detected.version.raw} detected).`);
     return { status: 'found', detected };
   }
 

package/tools/installer/modules/external-manager.js

@@ -135,6 +135,10 @@ class ExternalModuleManager {
       postInstallMessage: mod.post_install_message || mod['post-install-message'] || mod.postInstallMessage || null,
       builtIn: mod.built_in === true,
       isExternal: mod.built_in !== true,
+      // Prior codes this module was registered under (e.g. `bmad-loop` was
+      // `bauto`). Lets a renamed module keep resolving existing installs
+      // instead of orphaning them — see getModuleByCode().
+      aliases: Array.isArray(mod.aliases) ? mod.aliases : [],
     };
   }
 
@@ -159,13 +163,27 @@ class ExternalModuleManager {
   }
 
   /**
-   * Get module info by code
-   * @param {string} code - The module code (e.g., 'cis')
+   * Get module info by code. Falls back to matching a registry entry's
+   * `aliases` list, so a module that was renamed (its `code` changed) still
+   * resolves for installs recorded under the prior code.
+   * @param {string} code - The module code (e.g., 'cis'), current or aliased
    * @returns {Object|null} Module info or null if not found
    */
   async getModuleByCode(code) {
     const modules = await this.listAvailable();
-    return modules.find((m) => m.code === code) || null;
+    return modules.find((m) => m.code === code) || modules.find((m) => m.aliases.includes(code)) || null;
+  }
+
+  /**
+   * Resolve a possibly-legacy module code to its current canonical code.
+   * Returns the input unchanged if it doesn't match any registry entry or
+   * alias (e.g. a custom/unknown module).
+   * @param {string} code
+   * @returns {Promise<string>}
+   */
+  async resolveCanonicalCode(code) {
+    const info = await this.getModuleByCode(code);
+    return info ? info.code : code;
   }
 
   /**
@@ -196,6 +214,11 @@ class ExternalModuleManager {
       throw new Error(`External module '${moduleCode}' not found in the BMad registry`);
     }
 
+    // Normalize to the canonical code so cache dir, in-memory resolutions,
+    // and log/error text stay consistent even when called with a renamed
+    // module's prior alias (getModuleByCode resolves aliases above).
+    moduleCode = moduleInfo.code;
+
     const cacheDir = this.getExternalCacheDir();
     const moduleCacheDir = path.join(cacheDir, moduleCode);
     const silent = options.silent || false;
@@ -488,6 +511,9 @@ class ExternalModuleManager {
       return null;
     }
 
+    // Normalize to the canonical code — see cloneExternalModule for why.
+    moduleCode = moduleInfo.code;
+
     // Marketplace-plugin modules (registry entries flagged `marketplace-plugin`)
     // ship a .claude-plugin/marketplace.json and keep their module.yaml inside a
     // skill's assets/ rather than in one directory alongside the skills. Resolve
@@ -573,6 +599,9 @@ class ExternalModuleManager {
       return null;
     }
 
+    // Normalize to the canonical code — see cloneExternalModule for why.
+    moduleCode = moduleInfo.code;
+
     const cloneDir = await this.cloneExternalModule(moduleCode, options);
 
     const marketplacePath = path.join(cloneDir, '.claude-plugin', 'marketplace.json');

package/tools/installer/ui.js

@@ -133,7 +133,12 @@ class UI {
     for (const moduleId of installedModuleIds) {
       if (moduleId === 'core') continue;
       if (!selectedSet.has(moduleId) && !options.preserveUnselected) continue;
-      if (officialCodes.has(moduleId)) continue;
+      // Resolve a possibly-renamed module code (e.g. `bauto` -> `bmad-loop`)
+      // before checking availability, so a registry rename doesn't freeze
+      // the install here the way it would have prior to the alias support
+      // in ExternalModuleManager.getModuleByCode().
+      const canonicalId = await externalManager.resolveCanonicalCode(moduleId);
+      if (officialCodes.has(canonicalId)) continue;
 
       const customSource = await customMgr.findModuleSourceByCode(moduleId, { bmadDir });
       if (!customSource) {