Skip to content

Package BMad Automator without installer runtime patches#2363

Closed
dickymoore wants to merge 1 commit intobmad-code-org:mainfrom
dickymoore:dicky/automator-codex-installer-boundary
Closed

Package BMad Automator without installer runtime patches#2363
dickymoore wants to merge 1 commit intobmad-code-org:mainfrom
dickymoore:dicky/automator-codex-installer-boundary

Conversation

@dickymoore
Copy link
Copy Markdown
Contributor

@dickymoore dickymoore commented May 1, 2026

Warning

These are LLM-authored changes and have not been human sanity-checked yet. This PR is intentionally draft I have double-checked the implementation.

Summary

Refactors the BMAD-METHOD side of Automator/Codex support so this repo only handles installer registration and packaging. Runtime behavior now belongs in the Automator source repo instead of being patched by the installer.

Key changes:

  • register BMad Automator as an experimental external module via fallback registry metadata
  • support external module source-root and target metadata in the installer
  • install Automator only for explicitly supported IDE targets
  • package Automator runtime source from the Automator repo into the installed skill without patching it
  • document the module boundary and experimental status
  • add deterministic installer tests for the source-root, target filtering, and packaging behavior

Why

The earlier approach changed BMAD-METHOD installer code to mutate an external module's runtime implementation. That blurred ownership between BMAD-METHOD and bmad-automator. This PR narrows BMAD-METHOD back to installer/package integration and leaves runtime support to Automator.

Companion PR

Tests

The repo pre-commit pipeline ran during commit and passed, including:

  • npm run test:refs
  • npm run test:install
    • 403 installation component tests passed
  • npm run test:urls
  • npm run test:channels
    • 83 channel resolution tests passed
  • npm run lint
  • npm run lint:md
  • npm run format:check
  • docs link validation and docs build

Notes

This intentionally avoids adding more Automator runtime behavior to BMAD-METHOD. If the companion Automator PR changes shape, this installer PR should follow that boundary rather than duplicating runtime logic here.

@dickymoore
Copy link
Copy Markdown
Contributor Author

Closing this draft because it targeted upstream main directly. The replacement is stacked onto the Automator branch it was based on: bma-d#2

@dickymoore dickymoore closed this May 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant