feat: import MyBMAD web dashboard alongside VS Code extension

[DevHDI]

Summary

Coordinates the BMAD UI ecosystem under one repository (per @bmadcode's Discord proposal) by importing the standalone Next.js dashboard from DevHDI/my-bmad@81b28ea into web/, side-by-side with the existing VS Code extension under src/.

This PR is intentionally a draft — it asks for approval on the structure before any merge. No src/ file is touched; @evie's extension is unchanged.

Scope (intentionally minimal)

• Exact verbatim import via git archive HEAD from DevHDI/my-bmad@81b28ea (the relicense-to-MIT commit on main)
• Zero changes inside src/ — extension build, lint, type-check, tests are unaffected
• Root eslint.config.mjs ignores web/** so the extension's strict TypeScript rules don't lint the Next.js code with extension-only policies
• Root .prettierignore ignores web/ for the same reason
• Root README.md updated with a Repository structure section documenting the side-by-side layout

Out of scope (deferred to follow-up PRs)

• pnpm workspace / monorepo restructuring
• A shared parser package extracted from both subprojects (the two implementations cover similar ground but have very different runtimes — VS Code extension vs. multi-user Next.js)
• CI for the web dashboard
• Preview deployment / hosting (needs Prisma DB, GitHub OAuth setup)

Note on web/.github/

The import is verbatim, so a nested .github/ folder is included for provenance. GitHub only executes workflows under the repository's top-level .github/workflows, so the nested ones at web/.github/workflows/ are imported as files but do not run as active GitHub Actions.

License

DevHDI/my-bmad was relicensed from AGPL-3.0 to MIT in DevHDI/my-bmad@81b28ea prior to this import, so the entire repository is now MIT-consistent. The imported web/LICENSE carries the standard MIT text.

Verification

Both subprojects pass all checks independently:

Extension (root) — unchanged:

• pnpm install --frozen-lockfile — clean
• pnpm typecheck (extension + webview) — clean
• pnpm test — 706/706
• pnpm build — produces extension + webview bundles
• pnpm lint — clean (only the 2 pre-existing no-console warnings; no web/ files scanned)

Web (web/) — newly imported:

• pnpm install --frozen-lockfile — clean
• pnpm tsc --noEmit — clean
• pnpm test — 151/151
• pnpm build — clean

Open questions for @bmadcode and @evie

1. Folder name: web/ (proposed), dashboard/, apps/web/?
2. Workspace: should we plan a follow-up PR introducing a pnpm-workspace.yaml and an apps/ + packages/ layout? Doing it now would be a single big move; doing it later as its own PR keeps this one focused on the import.
3. Shared parser: extracting a parser package from both src/extension/parsers/ and web/src/lib/bmad/ makes sense long-term, but it's a non-trivial refactor that touches both surfaces. Worth a dedicated discussion before any code change.
4. Review and merge ownership going forward on this repo.
5. DevHDI/my-bmad: archive after this lands, or keep it as a public mirror?

Note on review

216 files changed — most of them are an exact import. The history of those files lives at DevHDI/my-bmad and includes 5 already-reviewed-and-merged PRs. Please focus the review on:

• The 4 root-level changes (README.md, eslint.config.mjs, .prettierignore, the new web/ directory at the top)
• The folder name and the open questions above

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: df2eba83-35ea-4be3-8c5b-8f391bbfc1d2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/import-mybmad-web-app

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}