ma-agents 3.18.0-beta.1 → 3.18.0-beta.3

package/README.md

@@ -277,6 +277,21 @@ Both messages end by stating that nothing was read or written on your behalf.
 These are stated here, in the shipped documentation, rather than only in the
 repository's changelog — which is **not** part of the npm package.
 
+- **Versions 3.7.0 through 3.17.1 could silently delete hand-authored skills.**
+  When a tool's skills directory moved between versions, the installer removed
+  the old directory recursively once the new one had content, destroying any
+  skill you had written there yourself and reporting it as a successful
+  cleanup. This affected `.github/copilot/skills`, `.github/skills`,
+  `.roo/skills` and `.kilocode/skills`. **It is fixed in this version** — the
+  sweep now removes only what ma-agents installed and preserves the directory
+  if anything else remains — but deletions already made are not recoverable
+  from ma-agents: no backup was written and nothing but the directory name was
+  recorded. Check your version control if you kept such skills.
+- **A file placed inside a skill directory ma-agents installed is still removed
+  with it.** The sweep's unit is the skill directory, not the file. If you have
+  edited a shipped skill in place, that edit is lost when the directory is
+  swept. Keep your own skills in their own directories, which are preserved.
+
 - **Every claim in this release about behaviour with a Confluence MCP *present*
   is mock-verified, not live.** No authorised Confluence MCP was available to
   the implementation or to any review, so the MCP-present branches were
@@ -554,7 +569,7 @@ Running `ma-agents` on a project where skills are already installed triggers the
 `ma-agents` ships with everything needed to install BMAD without any network access at install time:
 
 - **`bmad-method` is a direct npm dependency** — no runtime `npx bmad-method` fetch required. The correct version is pinned and bundled inside `node_modules/` when you `npm install ma-agents`.
-- **External modules pre-bundled** — `lib/bmad-cache/` ships exactly 5 optional BMAD modules (`bmb`, `cis`, `gds`, `tea`, `wds`) inside the package itself. They are pre-populated to `~/.bmad/cache/external-modules/` before any install runs, so BMAD never needs to clone them from GitHub. The bundled set is a **closed allowlist** — a build-time guard fails loud if the resolved set is ever smaller (a thin cache) *or* larger (a silent upstream addition) than these five, so a new upstream module can never be force-bundled or installed by default. `bmad-loop` (BMAD's own unattended-dev orchestrator, added upstream at v6.10.0) is deliberately **excluded** from this bundle — see "BMAD-loop and other opt-in modules" below.
+- **External modules pre-bundled** — `lib/bmad-cache/` ships exactly 3 optional BMAD modules (`bmb`, `cis`, `tea`) inside the package itself. They are pre-populated to `~/.bmad/cache/external-modules/` before any install runs, so BMAD never needs to clone them from GitHub. The bundled set is a **closed allowlist** — a build-time guard fails loud if the resolved set is ever smaller (a thin cache) *or* larger (a silent upstream addition) than these three, so a new upstream module can never be force-bundled or installed by default. The two design-studio modules `gds` (Game Dev Studio) and `wds` (Whiteport Design Studio) are **not bundled and not installable by ma-agents** — they are not offered by the `--bmad-modules` multiselect, and obtaining either one requires network access to its upstream repository, so on an air-gapped machine neither is available. `bmad-loop` (BMAD's own unattended-dev orchestrator, added upstream at v6.10.0) is deliberately **excluded** from this bundle — see "BMAD-loop and other opt-in modules" below.
 - **Plugin bundle pre-built** — `lib/bmad-extension-plugin/` ships as a deterministic, byte-stable bundle (built from `lib/bmad-extension/` via `scripts/build-plugin.js`). At install time it is staged into `<project>/.ma-agents-plugin-stage/` and consumed by `bmad-method install --custom-source`, so the install never touches the network for plugin assembly.
 - **Deterministic installs** — same `ma-agents` version always produces the same `_bmad/` output, regardless of network conditions (NFR21). Bundle reproducibility is gated by a CI drift check.
 - **Air-gapped friendly** — install from a tarball (`npm install ./ma-agents-x.y.z.tgz`) and run `npx ma-agents install` completely offline. Every PR runs an offline-install gate (`--network none` Docker) to enforce this guarantee (NFR54).
@@ -937,7 +952,7 @@ ma-agents/
 │   │   ├── clinerules.template.md                    # .clinerules expansion for Cline
 │   │   └── project-context.template.md               # project-context.md generation template
 │   ├── bmad-customize/         # Source-of-truth: per-persona phase / on_prem_phase_prefix YAML (consumed by the post-install marker-block injector)
-│   ├── bmad-cache/             # Pre-bundled BMAD external modules (bmb, cis, gds, tea)
+│   ├── bmad-cache/             # Pre-bundled BMAD external modules (bmb, cis, tea)
 │   ├── bmad-customizations/    # BMAD persona templates (.md) and YAML configs
 │   ├── bmad-extension/         # Extension source: sprint management, bug tracking, agent skills (hand-edited)
 │   ├── bmad-extension-plugin/  # Generated plugin bundle (deterministic; built from bmad-extension/ via scripts/build-plugin.js)

package/bin/cli.js

@@ -157,10 +157,14 @@ ${chalk.bold('Install options:')}
   ${chalk.cyan('--yes')}             Skip all prompts, use defaults (for CI/CD)
   ${chalk.cyan('--agent <name>')}    Target a specific agent (skip agent selection)
   ${chalk.cyan('--bmad-modules [csv]')} Control BMAD module selection.
-                       Bare:    open a multiselect prompt
+                       Bare:    open a multiselect prompt (offers every
+                                bundled module: bmm, tea, bmb, cis)
                        With CSV: install exactly those (e.g. tea,bmb)
-                       Omitted: install every non-retired module (default)
-                       'bmm' is always force-included.
+                       Omitted: install bmm,tea,bmb,cis (default)
+                       'bmm' is always force-included. The design-studio
+                       modules gds and wds are not bundled and cannot be
+                       installed by ma-agents; getting either one needs
+                       network access to its upstream repository.
   ${chalk.cyan('--bmad-custom-source <ref>')} Enumerate extensions from ONE custom
                        marketplace repo (local path or Git URL containing
                        .claude-plugin/marketplace.json) and offer them in
@@ -347,7 +351,7 @@ function parseFlags(args) {
   // --bmad-modules — controls BMad module selection. Optional-value flag:
   //   bare         → ask the user via multiselect prompt
   //   with CSV     → install exactly those (bmm force-prepended, unknowns rejected)
-  //   not present  → install all non-retired modules (no prompt)
+  //   not present  → install FR123's default set, bmm+tea+bmb+cis (no prompt)
   // Force-prepending of `bmm` and validation of unknown ids is handled
   // centrally by lib/bmad.resolveBmadModules.
   let bmadModulesFlag = '';
@@ -3671,18 +3675,28 @@ async function collectSprintManagementLocation(concern, existingRecord) {
  *
  * Three branches:
  *   1. `--bmad-modules <csv>` → install exactly those (bmm force-prepended,
- *      unknowns rejected with a clear error)
- *   2. `--bmad-modules` bare  → multiselect prompt; bmm is required and
- *      pre-checked, others default-checked so a no-op confirmation matches
- *      the no-flag default
- *   3. (no flag)              → install every non-retired module from the
- *      cache manifest, no prompt — restores the originally-intended
- *      behavior that the hardcoded ['bmm'] literal had been suppressing
+ *      unknowns rejected with a clear error). `gds`/`wds` are not bundled
+ *      (FR75), so naming either one is an unknown-module error.
+ *   2. `--bmad-modules` bare  → multiselect prompt; EVERY bundled module is
+ *      offered, bmm is required and pre-checked, and the remaining initial
+ *      check state is the FR123 default set — so a no-op confirmation lands
+ *      on exactly the same modules as branch 3.
+ *   3. (no flag)              → no prompt. In order: a persisted selection
+ *      from a prior run (bug 27.13), else the modules already present under
+ *      `_bmad/`, else `bmad.getDefaultBmadModules()` — FR123's default set,
+ *      bmm + tea + bmb + cis.
+ *
+ * BRANCH 3 IS A NAMED LITERAL, NOT "EVERY NON-RETIRED MODULE" (FR123).
+ * Deriving the default from the manifest made it grow silently every time a
+ * module was bundled; naming the members means the next bundled module has to
+ * be added on purpose. The bundled set and the default set currently coincide,
+ * so branches 2 and 3 land on the same modules — but they are still two
+ * different decisions and the literal keeps them apart.
  *
  * `bmm` is force-included in every path because the BMad core agents
  * (analyst, PM, dev, architect, ...) live there and downstream skills
- * break without them. Retired modules (currently only `wds`) are filtered
- * out unconditionally.
+ * break without them. Retired modules (none at v6.10.0) are filtered out
+ * unconditionally.
  */
 async function selectBmadModules({ bmadModulesFlag, bmadModulesPrompt, projectRoot } = {}) {
   const installable = bmad.getInstallableBmadModules().filter(m => !m.retired);
@@ -3712,15 +3726,22 @@ async function selectBmadModules({ bmadModulesFlag, bmadModulesPrompt, projectRo
 
   // Branch 2: bare --bmad-modules → multiselect prompt.
   if (bmadModulesPrompt) {
+    // FR123: every bundled module is OFFERED, and the initial check state is
+    // the default INSTALL set, so pressing Enter without touching anything
+    // lands on the same modules as the no-flag branch below. The offered list
+    // is `getInstallableBmadModules()`, i.e. the cache manifest — a module
+    // that is not bundled (`gds`/`wds`, FR75) is not offered here, because
+    // offering something this package cannot install would be a lie.
+    const defaultIds = new Set(bmad.getDefaultBmadModules(installable));
     const choices = installable.map(m => {
       const isCore = m.id === 'bmm';
       const requiredTag = isCore ? chalk.yellow(' (required)') : '';
       return {
         title: chalk.white(m.id) + requiredTag + chalk.gray(` — ${m.description}`),
         value: m.id,
-        // Default-check everything so hitting Enter matches the no-flag
-        // "install all" default. Users uncheck what they want to skip.
-        selected: true,
+        // bmm is force-included downstream regardless; pre-checking it keeps
+        // the prompt honest about that.
+        selected: isCore || defaultIds.has(m.id),
       };
     });
 
@@ -3740,22 +3761,52 @@ async function selectBmadModules({ bmadModulesFlag, bmadModulesPrompt, projectRo
     return persist(bmad.resolveBmadModules({ requested: chosenModules, available: installable }));
   }
 
-  // Branch 3: no flag → use the persisted selection from a prior run if present
-  // (bug 27.13 — a previous deselection must survive); otherwise fall back to
-  // the original "install every available module" default. The persisted set is
-  // intersected with the currently-installable set so a since-retired module
-  // does not resurface, and bmm is force-included via resolveBmadModules.
+  // Branch 3: no flag. Three fallbacks, most-specific first.
+  const availableIds = new Set(installable.map(m => m.id));
+
+  // 3a — a persisted selection from a prior run (bug 27.13): a previous
+  // deselection must survive. Intersected with the currently-installable set so
+  // a since-retired module does not resurface; bmm is force-included via
+  // resolveBmadModules.
   const persisted = getBmadModules(root);
   if (persisted && persisted.length > 0) {
-    const availableIds = new Set(installable.map(m => m.id));
     const stillInstallable = persisted.filter(id => availableIds.has(id));
     try {
       return persist(bmad.resolveBmadModules({ requested: stillInstallable, available: installable }));
     } catch {
-      // If the persisted set somehow fails validation, fall through to default.
+      // If the persisted set somehow fails validation, fall through.
     }
   }
-  return persist(installable.map(m => m.id));
+
+  // 3b — NON-DESTRUCTIVE MIGRATION. The narrowed default (FR123) is
+  // behaviour-visible to projects that installed under an older, wider
+  // default, and an update run passes this same resolved list to
+  // `bmad.updateBmad`. A project that already has a module under `_bmad/`
+  // must not have it dropped out of its own module list just because the
+  // default moved — narrowing applies to NEW installs, not to existing ones.
+  //
+  // 3a covers projects installed since bug 27.13 landed persistence; this
+  // covers the ones installed before it, where `.ma-agents.json` carries no
+  // `bmadModules` field at all and disk is the only record of what was chosen.
+  // A fresh project has no `_bmad/`, so this is inert for new installs — which
+  // is exactly the "existing installs unchanged, only NEW installs get the
+  // narrower default" posture NFR49 / Story 30.4 established for Demerzel.
+  // Persisting the result also migrates the project onto 27.13's durable
+  // record, so this disk probe is needed at most once per project.
+  const alreadyInstalled = bmad.getInstalledBmadModules(root).filter(id => availableIds.has(id));
+  if (alreadyInstalled.length > 0) {
+    try {
+      return persist(bmad.resolveBmadModules({ requested: alreadyInstalled, available: installable }));
+    } catch {
+      // Fall through to the default set.
+    }
+  }
+
+  // 3c — a genuinely fresh install: FR123's amended default set.
+  return persist(bmad.resolveBmadModules({
+    requested: bmad.getDefaultBmadModules(installable),
+    available: installable,
+  }));
 }
 
 // --- Custom marketplace source (Story 30.6a) ---
@@ -4408,10 +4459,9 @@ async function installWizard(preselectedSkill, preselectedAgents, customPath, fo
     // stage the plugin and invoke the installer in one pass.
     // v6.6.0: --tools none is rejected for fresh installs; skip BMAD entirely when no IDE tools selected.
     if (bmadTools.length > 0) {
-      // Resolve module set once per BMAD invocation. Default is "install
-      // every non-retired module"; users opt into a specific subset with
-      // --bmad-modules <csv> or open a multiselect prompt with --bmad-modules
-      // (bare).
+      // Resolve module set once per BMAD invocation. Default (FR123) is
+      // bmm+tea+bmb+cis, which is the whole bundled set; `--bmad-modules <csv>`
+      // or the multiselect that bare --bmad-modules opens can narrow it.
       const bmadModules = await selectBmadModules({
         bmadModulesFlag,
         bmadModulesPrompt,

package/docs/architecture.md

@@ -199,7 +199,7 @@ skills/<skill-name>/
 
 **Responsibility**: Pre-vendor BMAD's external modules so installs never touch the network.
 
-ma-agents bundles bmad-method as an npm dependency **and** pre-clones BMAD's external modules (`tea`, `bmb`, `cis`, `gds`) into `lib/bmad-cache/` at build time via `npm run build:bmad-cache` ([scripts/build-bmad-cache.js](../scripts/build-bmad-cache.js)). This is what lets `npx ma-agents install` run fully offline in air-gapped environments (NFR2/NFR50/NFR54) — the npm tarball already contains every module bmad-method would otherwise `git clone` from GitHub at install time.
+ma-agents bundles bmad-method as an npm dependency **and** pre-clones BMAD's external modules (`tea`, `bmb`, `cis`) into `lib/bmad-cache/` at build time via `npm run build:bmad-cache` ([scripts/build-bmad-cache.js](../scripts/build-bmad-cache.js)). This is what lets `npx ma-agents install` run fully offline in air-gapped environments (NFR2/NFR50/NFR54) — the npm tarball already contains every module bmad-method would otherwise `git clone` from GitHub at install time.
 
 **Module discovery**: the builder reads BMAD's bundled module registry to learn which external modules to clone. **The registry source has moved across BMAD versions** and the reader must track it:
 
@@ -209,7 +209,7 @@ ma-agents bundles bmad-method as an npm dependency **and** pre-clones BMAD's ext
 | 6.3.0 – 6.6.x | `tools/installer/modules/registry-fallback.yaml` | YAML |
 | 6.8.0+ | `bmad-modules.yaml` (bmad-method **package root**) | YAML (`modules:` map; the in-package `registry-fallback.yaml` was retired in 6.7.0) |
 
-The registry has stayed **YAML** throughout — only its path has moved. (`tools/installer/modules/official-modules.js` is unchanged loader code that reads this YAML; it does not contain the module list.) Modules are classified by a `type` field: `type: bmad-org` modules are bundled (**tea, bmb, cis, gds, wds**) and `type: experimental` modules are excluded (currently `automator`). `bmm`/`core` are built-in (loaded from bmad-method's local `module.yaml`, absent from the registry) and are never cloned. The reader for the current pin and its fail-loud contract are defined by Architecture Decision **P5-5** (Epic 27) in `_bmad-output/planning-artifacts/architecture.md`. A companion build step, `npm run build:plugin` ([scripts/build-plugin.js](../scripts/build-plugin.js)), assembles the ma-agents extension plugin bundle (`lib/bmad-extension-plugin/`) deterministically; a CI Bundle Drift Guard enforces that the committed bundle matches a fresh build.
+The registry has stayed **YAML** throughout — only its path has moved. (`tools/installer/modules/official-modules.js` is unchanged loader code that reads this YAML; it does not contain the module list.) The bundle is governed by a closed allowlist, `KNOWN_BUNDLED_MODULES` = **tea, bmb, cis** (FR235); every other registry entry is excluded whatever its `type`, including `type: experimental` (currently `automator`), the `marketplace-plugin` module `bmad-loop`, and the two design-studio modules `gds`/`wds`, which FR75 does not bundle. `bmm`/`core` are built-in (loaded from bmad-method's local `module.yaml`, absent from the registry) and are never cloned. The reader for the current pin and its fail-loud contract are defined by Architecture Decision **P5-5** (Epic 27) in `_bmad-output/planning-artifacts/architecture.md`. A companion build step, `npm run build:plugin` ([scripts/build-plugin.js](../scripts/build-plugin.js)), assembles the ma-agents extension plugin bundle (`lib/bmad-extension-plugin/`) deterministically; a CI Bundle Drift Guard enforces that the committed bundle matches a fresh build.
 
 > **Maintenance note:** because the registry path has now moved twice (YAML→YAML→YAML at three locations), the cache builder fails loud — if the resolved `type: bmad-org` set is smaller than the known bundled set, or no module source is found, it exits non-zero rather than producing a thin/empty cache, so a future BMAD registry move surfaces at build time, not as a broken air-gapped install.
 

package/docs/technical-notes/enforcement-hooks-research.md

@@ -294,11 +294,20 @@ All 11 BMAD agents have enforcement via `critical_actions` in `.customize.yaml`
 **Mechanism:**
 ```yaml
 critical_actions:
-  1: "Read the skills MANIFEST at {project-root}/_bmad/skills/MANIFEST.yaml"
+  1: "Read the skills MANIFEST at {project-root}/_bmad/skills/<agent-slug>/MANIFEST.yaml if it exists"
   2: "For each skill marked always_load: true, read the skill file completely"
   3: "Follow all skill directives during this session"
 ```
 
+> **Note (2026-09-12):** this snippet previously showed a bare
+> `{project-root}/_bmad/skills/MANIFEST.yaml`. That path is not what Story 8.3
+> specified — the manifest is per-agent-host, at
+> `{project-root}/_bmad/skills/<agent-slug>/MANIFEST.yaml`, where `<agent-slug>`
+> matches the `skillsDir` in `lib/agents.js` (`sre`, `devops`, `cyber`, `sqa`).
+> The bare form leaked from here into `ma-agent-sqa`'s Critical Actions block and
+> survived there until it was corrected. Keep the slug segment in any copy of this
+> snippet.
+
 **Deployment:** Extension module at `_bmad/extensions/ma-agents-skills/` deployed during BMAD customization pipeline (Stage 3 in `bmad.js`).
 
 **Coverage:**

package/lib/agents.js

@@ -242,8 +242,27 @@ const agents = [
     version: '1.0.0',
     category: 'ide',
     description: 'Google Deepmind Antigravity Agent',
-    skillsDir: '.antigravity/skills',
-    getProjectPath: () => path.join(process.cwd(), '.antigravity', 'skills'),
+    // Bug `antigravity-path-divergence`: this used to read `.antigravity/skills`,
+    // a path ma-agents invented from its own per-tool naming convention. Upstream
+    // bmad-method maps the SAME tool to `.agent/skills`
+    // (node_modules/bmad-method/tools/installer/ide/platform-codes.yaml, platform
+    // `antigravity`, in a file whose header records the paths as "verified against
+    // each tool's primary docs"; its global counterpart `~/.gemini/antigravity/skills`
+    // shows the entry was researched rather than guessed). Because ma-agents
+    // delegates part of the install to that installer, a single run produced TWO
+    // trees — and `.agent/skills`, the one Antigravity actually reads, was named by
+    // neither this registry nor lib/bmad.js, so every ma-agents post-deploy patch
+    // (the on-prem phase prefix among them) silently skipped it. Measured in a real
+    // on-prem project: .claude/.agents/.cline each carried the prefix on 6 personas,
+    // .agent/skills on 0.
+    // Upstream is the authority on which directory a tool reads, so we align —
+    // exactly as copilot/roo-code/kilocode were aligned to `.agents/skills` when
+    // bmad-method 6.5.0 moved them (see the copilot entry above). This is a
+    // per-tool decision on per-tool evidence: the other three divergences in the
+    // table are recorded in PLATFORM_PATH_DIVERGENCES below, deliberately unchanged.
+    // Existing installs migrate via OBSOLETE_TOOL_SKILL_DIRS in lib/installer.js.
+    skillsDir: '.agent/skills',
+    getProjectPath: () => path.join(process.cwd(), '.agent', 'skills'),
     getGlobalPath: () => {
       const platform = os.platform();
       if (platform === 'win32') {
@@ -356,6 +375,64 @@ const agents = [
   // Add them here in a dedicated future story if/when demand appears.
 ];
 
+/**
+ * Declared, deliberate divergences between this registry's project `skillsDir`
+ * and bmad-method's `installer.target_dir` for the SAME tool
+ * (`node_modules/bmad-method/tools/installer/ide/platform-codes.yaml`).
+ * Keyed by bmad platform code (see `getBmadPlatformCode`).
+ *
+ * Why this exists (bug `antigravity-path-divergence`): the two tables had drifted
+ * apart for four tools and nothing compared them outside the five flagships, so a
+ * whole second skill tree appeared in real projects with no owner and no patcher.
+ * `test/routing-parity.test.js` (section 5) now enumerates EVERY tool in BOTH
+ * tables and fails on any divergence that is not declared here — and on any
+ * declaration whose recorded paths have gone stale, so an entry cannot rot into
+ * cover for a different divergence.
+ *
+ * Scope note — PROJECT paths only. `getGlobalPath()` follows a per-OS
+ * application-data convention that differs from upstream's `global_target_dir`
+ * for EVERY tool, claude-code included (`%APPDATA%/Claude/skills` vs
+ * `~/.claude/skills`). That is a whole-table convention difference, not a
+ * per-tool divergence, and is deliberately out of scope here.
+ *
+ * To add an entry you must record BOTH live paths and a real reason. To remove
+ * one, align the paths — the test fails on a declaration whose paths now agree.
+ */
+const PLATFORM_PATH_DIVERGENCES = Object.freeze({
+  gemini: Object.freeze({
+    maSkillsDir: '.gemini/skills',
+    bmadTargetDir: '.agents/skills',
+    reason:
+      "Upstream's `gemini` platform is the Gemini CLI, which reads the shared " +
+      '`.agents/skills` tree; this registry entry targets Google Gemini Code Assist ' +
+      '(the IDE extension — note its instruction file `.gemini/gemini.md`), a ' +
+      'different product sharing the same code. Contained: upstream writes ' +
+      '`.agents/skills`, which is already an IDE skillsDir in this registry, already ' +
+      'a seed in lib/bmad.js TOOL_SKILL_DIRS, and already reconciled by bug 27.16 — ' +
+      'so no tree goes unpatched. Realigning is a compatibility call for its own story.'
+  }),
+  cursor: Object.freeze({
+    maSkillsDir: '.cursor/skills',
+    bmadTargetDir: '.agents/skills',
+    reason:
+      'Cursor reads its own `.cursor/` workspace directory (this registry also stamps ' +
+      '`.cursor/cursor.md` there); upstream routes it to the shared `.agents/skills` ' +
+      'cross-tool tree instead. Contained for the same reason as `gemini`: upstream ' +
+      "'s target is already a known, patched and reconciled tree. Kept deliberately " +
+      'so this bug fix changes the write path of exactly one tool, on that tool’s evidence.'
+  }),
+  opencode: Object.freeze({
+    maSkillsDir: '.opencode/skills',
+    bmadTargetDir: '.agents/skills',
+    reason:
+      'OpenCode is wired here through `opencode.json::instructions[]` plus AGENTS.md ' +
+      '(Story 21.4) against its own `.opencode/` tree; upstream routes it to the shared ' +
+      '`.agents/skills`. Contained for the same reason as `gemini` and `cursor`: ' +
+      "upstream's target is already a known, patched and reconciled tree. Realignment " +
+      'would also have to move the instruction wiring, so it belongs in its own story.'
+  })
+});
+
 function getAgent(agentId) {
   return agents.find(a => a.id === agentId);
 }
@@ -383,5 +460,6 @@ module.exports = {
   getAgent,
   getAllAgents,
   getAgentsByCategory,
-  getBmadPlatformCode
+  getBmadPlatformCode,
+  PLATFORM_PATH_DIVERGENCES
 };

package/lib/bmad-cache/cache-manifest.json

@@ -20,18 +20,6 @@
       "branch": "main",
       "commitSha": "07a8dd03d196a762f21c241d985293fe5b0f90e7",
       "clonedAt": "2026-06-13T15:11:42.507Z"
-    },
-    "gds": {
-      "url": "https://github.com/bmad-code-org/bmad-module-game-dev-studio.git",
-      "branch": "main",
-      "commitSha": "46c3a6cddf882af1f918187d6e5748c1edfd9c52",
-      "clonedAt": "2026-06-13T15:11:43.930Z"
-    },
-    "wds": {
-      "url": "https://github.com/bmad-code-org/bmad-method-wds-expansion",
-      "branch": "main",
-      "commitSha": "cc16f09fcfab26d35635af1491f36a38a8431c8d",
-      "clonedAt": "2026-06-13T15:11:45.601Z"
     }
   }
 }

package/lib/bmad-extension/skills/ma-agent-cyber/SKILL.md

@@ -43,7 +43,7 @@ You must fully embody this agent's persona and follow all activation instruction
 | 6 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
 
 ## Critical Actions
-1. Read the skills MANIFEST at {project-root}/_bmad/skills/cyber/MANIFEST.yaml
-2. For each skill marked always_load: true, read the skill file completely
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/cyber/MANIFEST.yaml if it exists
+2. For each skill marked always_load: true, read the skill file completely (only if that MANIFEST was read; if it was not, skip this step)
 3. If _bmad-output/project-context.md exists, read it completely
 4. Follow all skill directives and project-context rules during this session

package/lib/bmad-extension/skills/ma-agent-devops/SKILL.md

@@ -43,7 +43,7 @@ You must fully embody this agent's persona and follow all activation instruction
 | 6 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
 
 ## Critical Actions
-1. Read the skills MANIFEST at {project-root}/_bmad/skills/devops/MANIFEST.yaml
-2. For each skill marked always_load: true, read the skill file completely
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/devops/MANIFEST.yaml if it exists
+2. For each skill marked always_load: true, read the skill file completely (only if that MANIFEST was read; if it was not, skip this step)
 3. If _bmad-output/project-context.md exists, read it completely
 4. Follow all skill directives and project-context rules during this session

package/lib/bmad-extension/skills/ma-agent-sqa/SKILL.md

@@ -53,7 +53,7 @@ You must fully embody this agent's persona and follow all activation instruction
 | 14 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
 
 ## Critical Actions
-1. Read the skills MANIFEST at {project-root}/_bmad/skills/MANIFEST.yaml
-2. For each skill marked always_load: true, read the skill file completely
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/sqa/MANIFEST.yaml if it exists
+2. For each skill marked always_load: true, read the skill file completely (only if that MANIFEST was read; if it was not, skip this step)
 3. If _bmad-output/project-context.md exists, read it completely
 4. Follow all skill directives and project-context rules during this session

package/lib/bmad-extension/skills/ma-agent-sre/SKILL.md

@@ -43,7 +43,7 @@ You must fully embody this agent's persona and follow all activation instruction
 | 6 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
 
 ## Critical Actions
-1. Read the skills MANIFEST at {project-root}/_bmad/skills/sre/MANIFEST.yaml
-2. For each skill marked always_load: true, read the skill file completely
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/sre/MANIFEST.yaml if it exists
+2. For each skill marked always_load: true, read the skill file completely (only if that MANIFEST was read; if it was not, skip this step)
 3. If _bmad-output/project-context.md exists, read it completely
 4. Follow all skill directives and project-context rules during this session

package/lib/bmad-extension-plugin/.claude-plugin/marketplace.json

@@ -37,7 +37,7 @@
       "name": "ma-skills",
       "source": "./",
       "description": "ma-agents extension module providing enterprise SDLC personas and operational workflow skills.",
-      "version": "3.18.0-beta.1",
+      "version": "3.18.0-beta.3",
       "author": {
         "name": "Alon Mayaffit"
       },

package/lib/bmad-extension-plugin/skills/ma-agent-cyber/SKILL.md

@@ -43,7 +43,7 @@ You must fully embody this agent's persona and follow all activation instruction
 | 6 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
 
 ## Critical Actions
-1. Read the skills MANIFEST at {project-root}/_bmad/skills/cyber/MANIFEST.yaml
-2. For each skill marked always_load: true, read the skill file completely
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/cyber/MANIFEST.yaml if it exists
+2. For each skill marked always_load: true, read the skill file completely (only if that MANIFEST was read; if it was not, skip this step)
 3. If _bmad-output/project-context.md exists, read it completely
 4. Follow all skill directives and project-context rules during this session

package/lib/bmad-extension-plugin/skills/ma-agent-devops/SKILL.md

@@ -43,7 +43,7 @@ You must fully embody this agent's persona and follow all activation instruction
 | 6 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
 
 ## Critical Actions
-1. Read the skills MANIFEST at {project-root}/_bmad/skills/devops/MANIFEST.yaml
-2. For each skill marked always_load: true, read the skill file completely
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/devops/MANIFEST.yaml if it exists
+2. For each skill marked always_load: true, read the skill file completely (only if that MANIFEST was read; if it was not, skip this step)
 3. If _bmad-output/project-context.md exists, read it completely
 4. Follow all skill directives and project-context rules during this session

package/lib/bmad-extension-plugin/skills/ma-agent-sqa/SKILL.md

@@ -53,7 +53,7 @@ You must fully embody this agent's persona and follow all activation instruction
 | 14 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
 
 ## Critical Actions
-1. Read the skills MANIFEST at {project-root}/_bmad/skills/MANIFEST.yaml
-2. For each skill marked always_load: true, read the skill file completely
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/sqa/MANIFEST.yaml if it exists
+2. For each skill marked always_load: true, read the skill file completely (only if that MANIFEST was read; if it was not, skip this step)
 3. If _bmad-output/project-context.md exists, read it completely
 4. Follow all skill directives and project-context rules during this session

package/lib/bmad-extension-plugin/skills/ma-agent-sre/SKILL.md

@@ -43,7 +43,7 @@ You must fully embody this agent's persona and follow all activation instruction
 | 6 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
 
 ## Critical Actions
-1. Read the skills MANIFEST at {project-root}/_bmad/skills/sre/MANIFEST.yaml
-2. For each skill marked always_load: true, read the skill file completely
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/sre/MANIFEST.yaml if it exists
+2. For each skill marked always_load: true, read the skill file completely (only if that MANIFEST was read; if it was not, skip this step)
 3. If _bmad-output/project-context.md exists, read it completely
 4. Follow all skill directives and project-context rules during this session