From 110d4cbc03449a196ccb1e6268e89712d611193d Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 7 Mar 2026 16:12:49 +0000 Subject: [PATCH] Remove all repository files Clear the repository of all tracked content. https://claude.ai/code/session_01GE7R9vLGsTa785ieSmeTT4 --- .augment/code_review_guidelines.yaml | 271 - .../skills/bmad-os-audit-file-refs/SKILL.md | 6 - .../prompts/instructions.md | 59 - .../skills/bmad-os-changelog-social/SKILL.md | 177 - .../examples/discord-example.md | 53 - .../examples/linkedin-example.md | 49 - .../examples/twitter-example.md | 55 - .../bmad-os-diataxis-style-fix/SKILL.md | 6 - .../prompts/instructions.md | 229 - .../skills/bmad-os-draft-changelog/SKILL.md | 6 - .../prompts/instructions.md | 82 - .claude/skills/bmad-os-gh-triage/SKILL.md | 6 - .../bmad-os-gh-triage/prompts/agent-prompt.md | 60 - .../bmad-os-gh-triage/prompts/instructions.md | 74 - .../skills/bmad-os-release-module/SKILL.md | 6 - .../prompts/instructions.md | 53 - .claude/skills/bmad-os-review-pr/SKILL.md | 6 - .../bmad-os-review-pr/prompts/instructions.md | 231 - .../bmad-os-root-cause-analysis/SKILL.md | 12 - .../prompts/instructions.md | 74 - .coderabbit.yaml | 85 - .github/CODE_OF_CONDUCT.md | 128 - .github/FUNDING.yaml | 15 - .github/ISSUE_TEMPLATE/bug-report.yaml | 124 - .github/ISSUE_TEMPLATE/config.yaml | 8 - .github/ISSUE_TEMPLATE/documentation.yaml | 55 - .github/ISSUE_TEMPLATE/feature-request.md | 22 - .github/ISSUE_TEMPLATE/issue.md | 32 - .github/PULL_REQUEST_TEMPLATE.md | 13 - .github/scripts/discord-helpers.sh | 34 - .github/workflows/coderabbit-review.yaml | 22 - .github/workflows/discord.yaml | 90 - .github/workflows/docs.yaml | 64 - .github/workflows/quality.yaml | 116 - .gitignore | 73 - .husky/pre-commit | 20 - .markdownlint-cli2.yaml | 41 - .npmrc | 5 - .nvmrc | 1 - .prettierignore | 12 - .vscode/settings.json | 96 - CHANGELOG.md | 1785 -- CNAME | 1 - CONTRIBUTING.md | 176 - CONTRIBUTORS.md | 32 - LICENSE | 30 - README.md | 109 - SECURITY.md | 85 - TRADEMARK.md | 55 - Wordmark.png | Bin 23544 -> 0 bytes banner-bmad-method.png | Bin 374692 -> 0 bytes docs/404.md | 9 - docs/_STYLE_GUIDE.md | 370 - docs/explanation/advanced-elicitation.md | 49 - docs/explanation/adversarial-review.md | 59 - docs/explanation/brainstorming.md | 33 - docs/explanation/established-projects-faq.md | 50 - docs/explanation/party-mode.md | 59 - .../explanation/preventing-agent-conflicts.md | 112 - docs/explanation/project-context.md | 157 - docs/explanation/quick-flow.md | 73 - docs/explanation/why-solutioning-matters.md | 77 - docs/how-to/customize-bmad.md | 172 - docs/how-to/established-projects.md | 117 - docs/how-to/get-answers-about-bmad.md | 134 - docs/how-to/install-bmad.md | 97 - docs/how-to/non-interactive-installation.md | 171 - docs/how-to/project-context.md | 136 - docs/how-to/quick-fixes.md | 123 - docs/how-to/shard-large-documents.md | 78 - docs/how-to/upgrade-to-v6.md | 97 - docs/index.md | 60 - docs/reference/agents.md | 28 - docs/reference/commands.md | 151 - docs/reference/modules.md | 76 - docs/reference/testing.md | 106 - docs/reference/workflow-map.md | 89 - docs/roadmap.mdx | 136 - docs/tutorials/getting-started.md | 273 - eslint.config.mjs | 141 - package-lock.json | 14369 ---------------- package.json | 110 - prettier.config.mjs | 32 - src/bmm/agents/analyst.agent.yaml | 43 - src/bmm/agents/architect.agent.yaml | 29 - src/bmm/agents/dev.agent.yaml | 38 - src/bmm/agents/pm.agent.yaml | 44 - src/bmm/agents/qa.agent.yaml | 58 - src/bmm/agents/quick-flow-solo-dev.agent.yaml | 32 - src/bmm/agents/sm.agent.yaml | 37 - .../documentation-standards.md | 224 - .../agents/tech-writer/tech-writer.agent.yaml | 46 - src/bmm/agents/ux-designer.agent.yaml | 27 - src/bmm/data/project-context-template.md | 26 - src/bmm/module-help.csv | 31 - src/bmm/module.yaml | 50 - src/bmm/teams/default-party.csv | 20 - src/bmm/teams/team-fullstack.yaml | 12 - .../product-brief.template.md | 10 - .../steps/step-01-init.md | 177 - .../steps/step-01b-continue.md | 161 - .../steps/step-02-vision.md | 199 - .../steps/step-03-users.md | 202 - .../steps/step-04-metrics.md | 205 - .../steps/step-05-scope.md | 219 - .../steps/step-06-complete.md | 162 - .../create-product-brief/workflow.md | 57 - .../research/domain-steps/step-01-init.md | 137 - .../domain-steps/step-02-domain-analysis.md | 229 - .../step-03-competitive-landscape.md | 238 - .../domain-steps/step-04-regulatory-focus.md | 206 - .../domain-steps/step-05-technical-trends.md | 234 - .../step-06-research-synthesis.md | 444 - .../research/market-steps/step-01-init.md | 182 - .../market-steps/step-02-customer-behavior.md | 237 - .../step-03-customer-pain-points.md | 249 - .../step-04-customer-decisions.md | 259 - .../step-05-competitive-analysis.md | 177 - .../step-06-research-completion.md | 476 - .../1-analysis/research/research.template.md | 29 - .../research/technical-steps/step-01-init.md | 137 - .../step-02-technical-overview.md | 239 - .../step-03-integration-patterns.md | 248 - .../step-04-architectural-patterns.md | 202 - .../step-05-implementation-research.md | 233 - .../step-06-research-synthesis.md | 487 - .../research/workflow-domain-research.md | 54 - .../research/workflow-market-research.md | 54 - .../research/workflow-technical-research.md | 54 - .../create-prd/data/domain-complexity.csv | 15 - .../create-prd/data/prd-purpose.md | 197 - .../create-prd/data/project-types.csv | 11 - .../create-prd/steps-c/step-01-init.md | 191 - .../create-prd/steps-c/step-01b-continue.md | 152 - .../create-prd/steps-c/step-02-discovery.md | 224 - .../create-prd/steps-c/step-02b-vision.md | 154 - .../steps-c/step-02c-executive-summary.md | 170 - .../create-prd/steps-c/step-03-success.md | 226 - .../create-prd/steps-c/step-04-journeys.md | 213 - .../create-prd/steps-c/step-05-domain.md | 207 - .../create-prd/steps-c/step-06-innovation.md | 226 - .../steps-c/step-07-project-type.md | 237 - .../create-prd/steps-c/step-08-scoping.md | 228 - .../create-prd/steps-c/step-09-functional.md | 231 - .../steps-c/step-10-nonfunctional.md | 242 - .../create-prd/steps-c/step-11-polish.md | 217 - .../create-prd/steps-c/step-12-complete.md | 124 - .../create-prd/steps-e/step-e-01-discovery.md | 247 - .../steps-e/step-e-01b-legacy-conversion.md | 208 - .../create-prd/steps-e/step-e-02-review.md | 249 - .../create-prd/steps-e/step-e-03-edit.md | 253 - .../create-prd/steps-e/step-e-04-complete.md | 168 - .../create-prd/steps-v/step-v-01-discovery.md | 226 - .../steps-v/step-v-02-format-detection.md | 191 - .../steps-v/step-v-02b-parity-check.md | 209 - .../steps-v/step-v-03-density-validation.md | 174 - .../step-v-04-brief-coverage-validation.md | 214 - .../step-v-05-measurability-validation.md | 228 - .../step-v-06-traceability-validation.md | 217 - ...-v-07-implementation-leakage-validation.md | 205 - .../step-v-08-domain-compliance-validation.md | 243 - .../step-v-09-project-type-validation.md | 263 - .../steps-v/step-v-10-smart-validation.md | 209 - .../step-v-11-holistic-quality-validation.md | 264 - .../step-v-12-completeness-validation.md | 242 - .../steps-v/step-v-13-report-complete.md | 231 - .../create-prd/templates/prd-template.md | 10 - .../create-prd/workflow-create-prd.md | 63 - .../create-prd/workflow-edit-prd.md | 65 - .../create-prd/workflow-validate-prd.md | 63 - .../create-ux-design/steps/step-01-init.md | 135 - .../steps/step-01b-continue.md | 127 - .../steps/step-02-discovery.md | 190 - .../steps/step-03-core-experience.md | 216 - .../steps/step-04-emotional-response.md | 219 - .../steps/step-05-inspiration.md | 234 - .../steps/step-06-design-system.md | 252 - .../steps/step-07-defining-experience.md | 254 - .../steps/step-08-visual-foundation.md | 224 - .../steps/step-09-design-directions.md | 224 - .../steps/step-10-user-journeys.md | 241 - .../steps/step-11-component-strategy.md | 248 - .../steps/step-12-ux-patterns.md | 237 - .../steps/step-13-responsive-accessibility.md | 264 - .../steps/step-14-complete.md | 171 - .../create-ux-design/ux-design-template.md | 13 - .../create-ux-design/workflow.md | 42 - .../steps/step-01-document-discovery.md | 184 - .../steps/step-02-prd-analysis.md | 172 - .../steps/step-03-epic-coverage-validation.md | 173 - .../steps/step-04-ux-alignment.md | 133 - .../steps/step-05-epic-quality-review.md | 245 - .../steps/step-06-final-assessment.md | 129 - .../templates/readiness-report-template.md | 4 - .../workflow.md | 54 - .../architecture-decision-template.md | 12 - .../data/domain-complexity.csv | 13 - .../data/project-types.csv | 7 - .../create-architecture/steps/step-01-init.md | 153 - .../steps/step-01b-continue.md | 173 - .../steps/step-02-context.md | 224 - .../steps/step-03-starter.md | 329 - .../steps/step-04-decisions.md | 318 - .../steps/step-05-patterns.md | 359 - .../steps/step-06-structure.md | 379 - .../steps/step-07-validation.md | 359 - .../steps/step-08-complete.md | 76 - .../create-architecture/workflow.md | 49 - .../steps/step-01-validate-prerequisites.md | 259 - .../steps/step-02-design-epics.md | 233 - .../steps/step-03-create-stories.md | 272 - .../steps/step-04-final-validation.md | 149 - .../templates/epics-template.md | 57 - .../create-epics-and-stories/workflow.md | 58 - .../4-implementation/code-review/checklist.md | 23 - .../code-review/instructions.xml | 227 - .../code-review/workflow.yaml | 43 - .../correct-course/checklist.md | 288 - .../correct-course/instructions.md | 207 - .../correct-course/workflow.yaml | 53 - .../create-story/checklist.md | 358 - .../create-story/instructions.xml | 346 - .../4-implementation/create-story/template.md | 49 - .../create-story/workflow.yaml | 52 - .../4-implementation/dev-story/checklist.md | 80 - .../dev-story/instructions.xml | 410 - .../4-implementation/dev-story/workflow.yaml | 20 - .../retrospective/instructions.md | 1444 -- .../retrospective/workflow.yaml | 52 - .../sprint-planning/checklist.md | 33 - .../sprint-planning/instructions.md | 226 - .../sprint-status-template.yaml | 55 - .../sprint-planning/workflow.yaml | 47 - .../sprint-status/instructions.md | 230 - .../sprint-status/workflow.yaml | 25 - .../quick-dev/steps/step-01-mode-detection.md | 174 - .../steps/step-02-context-gathering.md | 118 - .../quick-dev/steps/step-03-execute.md | 111 - .../quick-dev/steps/step-04-self-check.md | 111 - .../steps/step-05-adversarial-review.md | 104 - .../steps/step-06-resolve-findings.md | 146 - .../bmad-quick-flow/quick-dev/workflow.md | 50 - .../quick-spec/steps/step-01-understand.md | 189 - .../quick-spec/steps/step-02-investigate.md | 143 - .../quick-spec/steps/step-03-generate.md | 126 - .../quick-spec/steps/step-04-review.md | 200 - .../quick-spec/tech-spec-template.md | 74 - .../bmad-quick-flow/quick-spec/workflow.md | 79 - .../workflows/document-project/checklist.md | 245 - .../documentation-requirements.csv | 12 - .../document-project/instructions.md | 130 - .../templates/deep-dive-template.md | 345 - .../templates/index-template.md | 169 - .../templates/project-overview-template.md | 103 - .../templates/project-scan-report-schema.json | 160 - .../templates/source-tree-template.md | 135 - .../workflows/document-project/workflow.yaml | 22 - .../workflows/deep-dive-instructions.md | 298 - .../document-project/workflows/deep-dive.yaml | 31 - .../workflows/full-scan-instructions.md | 1106 -- .../document-project/workflows/full-scan.yaml | 31 - .../project-context-template.md | 21 - .../steps/step-01-discover.md | 184 - .../steps/step-02-generate.md | 318 - .../steps/step-03-complete.md | 278 - .../generate-project-context/workflow.md | 49 - .../qa-generate-e2e-tests/checklist.md | 33 - .../qa-generate-e2e-tests/instructions.md | 110 - .../qa-generate-e2e-tests/workflow.yaml | 42 - src/core/agents/bmad-master.agent.yaml | 30 - src/core/module-help.csv | 10 - src/core/module.yaml | 25 - src/core/tasks/editorial-review-prose.xml | 102 - src/core/tasks/editorial-review-structure.xml | 208 - src/core/tasks/help.md | 86 - src/core/tasks/index-docs.xml | 65 - src/core/tasks/review-adversarial-general.xml | 49 - src/core/tasks/review-edge-case-hunter.xml | 63 - src/core/tasks/shard-doc.xml | 108 - src/core/tasks/workflow.xml | 235 - .../advanced-elicitation/methods.csv | 51 - .../advanced-elicitation/workflow.xml | 118 - .../workflows/brainstorming/brain-methods.csv | 62 - .../steps/step-01-session-setup.md | 210 - .../brainstorming/steps/step-01b-continue.md | 122 - .../steps/step-02a-user-selected.md | 225 - .../steps/step-02b-ai-recommended.md | 237 - .../steps/step-02c-random-selection.md | 209 - .../steps/step-02d-progressive-flow.md | 264 - .../steps/step-03-technique-execution.md | 399 - .../steps/step-04-idea-organization.md | 303 - src/core/workflows/brainstorming/template.md | 15 - src/core/workflows/brainstorming/workflow.md | 60 - .../party-mode/steps/step-01-agent-loading.md | 138 - .../steps/step-02-discussion-orchestration.md | 187 - .../party-mode/steps/step-03-graceful-exit.md | 168 - src/core/workflows/party-mode/workflow.md | 194 - .../agent-components/activation-rules.txt | 6 - .../agent-components/activation-steps.txt | 14 - .../agent-components/agent-command-header.md | 1 - .../agent.customize.template.yaml | 41 - .../agent-components/handler-action.txt | 4 - src/utility/agent-components/handler-data.txt | 5 - src/utility/agent-components/handler-exec.txt | 6 - .../agent-components/handler-multi.txt | 14 - src/utility/agent-components/handler-tmpl.txt | 5 - .../handler-validate-workflow.txt | 7 - .../agent-components/handler-workflow.txt | 10 - .../agent-components/menu-handlers.txt | 6 - test/README.md | 295 - test/adversarial-review-tests/README.md | 56 - .../sample-content.md | 46 - test/adversarial-review-tests/test-cases.yaml | 103 - .../actions-as-string.agent.yaml | 27 - .../empty-string-in-actions.agent.yaml | 30 - .../empty-command-target.agent.yaml | 25 - .../no-command-target.agent.yaml | 24 - .../menu-triggers/camel-case.agent.yaml | 25 - .../compound-invalid-format.agent.yaml | 25 - .../compound-mismatched-kebab.agent.yaml | 25 - .../duplicate-triggers.agent.yaml | 31 - .../menu-triggers/empty-trigger.agent.yaml | 25 - .../menu-triggers/leading-asterisk.agent.yaml | 25 - .../menu-triggers/snake-case.agent.yaml | 25 - .../trigger-with-spaces.agent.yaml | 25 - .../invalid/menu/empty-menu.agent.yaml | 22 - .../invalid/menu/missing-menu.agent.yaml | 20 - .../metadata/empty-module-string.agent.yaml | 26 - .../invalid/metadata/empty-name.agent.yaml | 24 - .../metadata/extra-metadata-fields.agent.yaml | 27 - .../invalid/metadata/missing-id.agent.yaml | 23 - .../persona/empty-principles-array.agent.yaml | 24 - .../empty-string-in-principles.agent.yaml | 27 - .../persona/extra-persona-fields.agent.yaml | 27 - .../invalid/persona/missing-role.agent.yaml | 24 - .../invalid/prompts/empty-content.agent.yaml | 29 - .../prompts/extra-prompt-fields.agent.yaml | 31 - .../prompts/missing-content.agent.yaml | 28 - .../invalid/prompts/missing-id.agent.yaml | 28 - .../invalid/top-level/empty-file.agent.yaml | 5 - .../top-level/extra-top-level-keys.agent.yaml | 28 - .../top-level/missing-agent-key.agent.yaml | 11 - .../invalid-indentation.agent.yaml | 19 - .../yaml-errors/malformed-yaml.agent.yaml | 18 - .../empty-critical-actions.agent.yaml | 24 - .../no-critical-actions.agent.yaml | 22 - .../valid-critical-actions.agent.yaml | 27 - .../all-command-types.agent.yaml | 38 - .../multiple-commands.agent.yaml | 24 - .../compound-triggers.agent.yaml | 31 - .../kebab-case-triggers.agent.yaml | 34 - .../valid/menu/multiple-menu-items.agent.yaml | 31 - .../valid/menu/single-menu-item.agent.yaml | 22 - .../core-agent-with-module.agent.yaml | 24 - .../empty-module-name-in-path.agent.yaml | 24 - .../malformed-path-treated-as-core.agent.yaml | 24 - .../metadata/module-agent-correct.agent.yaml | 24 - .../module-agent-missing-module.agent.yaml | 23 - .../metadata/wrong-module-value.agent.yaml | 24 - .../valid/persona/complete-persona.agent.yaml | 24 - .../valid/prompts/empty-prompts.agent.yaml | 24 - .../valid/prompts/no-prompts.agent.yaml | 22 - .../prompts/valid-prompts-minimal.agent.yaml | 28 - .../valid-prompts-with-description.agent.yaml | 30 - .../top-level/minimal-core-agent.agent.yaml | 24 - .../invalid/all-empty-workflow.csv | 3 - .../file-refs-csv/invalid/empty-data.csv | 1 - .../invalid/no-workflow-column.csv | 3 - .../invalid/unresolvable-vars.csv | 3 - .../file-refs-csv/valid/bmm-style.csv | 3 - .../file-refs-csv/valid/core-style.csv | 3 - test/fixtures/file-refs-csv/valid/minimal.csv | 2 - test/test-agent-schema.js | 387 - test/test-cli-integration.sh | 159 - test/test-file-refs-csv.js | 133 - test/test-installation-components.js | 212 - test/test-rehype-plugins.mjs | 1050 -- test/unit-test-schema.js | 133 - tools/bmad-npx-wrapper.js | 38 - tools/build-docs.mjs | 463 - tools/cli/README.md | 60 - tools/cli/bmad-cli.js | 106 - tools/cli/commands/install.js | 87 - tools/cli/commands/status.js | 65 - tools/cli/commands/uninstall.js | 167 - tools/cli/external-official-modules.yaml | 53 - tools/cli/installers/install-messages.yaml | 39 - .../installers/lib/core/config-collector.js | 1285 -- .../lib/core/custom-module-cache.js | 260 - .../lib/core/dependency-resolver.js | 743 - tools/cli/installers/lib/core/detector.js | 223 - .../installers/lib/core/ide-config-manager.js | 157 - tools/cli/installers/lib/core/installer.js | 3162 ---- .../installers/lib/core/manifest-generator.js | 1081 -- tools/cli/installers/lib/core/manifest.js | 1038 -- tools/cli/installers/lib/custom/handler.js | 358 - tools/cli/installers/lib/ide/_base-ide.js | 665 - .../cli/installers/lib/ide/_config-driven.js | 634 - tools/cli/installers/lib/ide/codex.js | 440 - .../cli/installers/lib/ide/github-copilot.js | 699 - tools/cli/installers/lib/ide/kilo.js | 269 - tools/cli/installers/lib/ide/manager.js | 342 - .../cli/installers/lib/ide/platform-codes.js | 100 - .../installers/lib/ide/platform-codes.yaml | 243 - tools/cli/installers/lib/ide/rovodev.js | 257 - .../lib/ide/shared/agent-command-generator.js | 180 - .../lib/ide/shared/bmad-artifacts.js | 174 - .../lib/ide/shared/module-injections.js | 136 - .../installers/lib/ide/shared/path-utils.js | 299 - .../ide/shared/task-tool-command-generator.js | 366 - .../ide/shared/workflow-command-generator.js | 318 - .../ide/templates/agent-command-template.md | 14 - .../lib/ide/templates/combined/antigravity.md | 8 - .../ide/templates/combined/claude-agent.md | 1 - .../combined/claude-workflow-yaml.md | 1 - .../ide/templates/combined/claude-workflow.md | 1 - .../ide/templates/combined/default-agent.md | 15 - .../ide/templates/combined/default-task.md | 10 - .../ide/templates/combined/default-tool.md | 10 - .../combined/default-workflow-yaml.md | 14 - .../templates/combined/default-workflow.md | 6 - .../ide/templates/combined/gemini-agent.toml | 14 - .../ide/templates/combined/gemini-task.toml | 11 - .../ide/templates/combined/gemini-tool.toml | 11 - .../combined/gemini-workflow-yaml.toml | 16 - .../templates/combined/gemini-workflow.toml | 14 - .../lib/ide/templates/combined/kiro-agent.md | 16 - .../lib/ide/templates/combined/kiro-task.md | 9 - .../lib/ide/templates/combined/kiro-tool.md | 9 - .../templates/combined/kiro-workflow-yaml.md | 15 - .../ide/templates/combined/kiro-workflow.md | 7 - .../ide/templates/combined/opencode-agent.md | 15 - .../ide/templates/combined/opencode-task.md | 13 - .../ide/templates/combined/opencode-tool.md | 13 - .../combined/opencode-workflow-yaml.md | 16 - .../templates/combined/opencode-workflow.md | 16 - .../lib/ide/templates/combined/rovodev.md | 9 - .../lib/ide/templates/combined/trae.md | 9 - .../templates/combined/windsurf-workflow.md | 10 - .../lib/ide/templates/split/.gitkeep | 0 .../templates/workflow-command-template.md | 13 - .../lib/ide/templates/workflow-commander.md | 5 - tools/cli/installers/lib/message-loader.js | 83 - .../lib/modules/external-manager.js | 136 - tools/cli/installers/lib/modules/manager.js | 1498 -- tools/cli/lib/activation-builder.js | 165 - tools/cli/lib/agent-analyzer.js | 109 - tools/cli/lib/agent-party-generator.js | 194 - tools/cli/lib/agent/compiler.js | 525 - tools/cli/lib/agent/installer.js | 680 - tools/cli/lib/agent/template-engine.js | 152 - tools/cli/lib/cli-utils.js | 182 - tools/cli/lib/config.js | 213 - tools/cli/lib/file-ops.js | 204 - tools/cli/lib/platform-codes.js | 116 - tools/cli/lib/project-root.js | 77 - tools/cli/lib/prompts.js | 809 - tools/cli/lib/ui.js | 1936 --- tools/cli/lib/xml-handler.js | 177 - tools/cli/lib/xml-to-markdown.js | 82 - tools/cli/lib/yaml-format.js | 245 - tools/cli/lib/yaml-xml-builder.js | 587 - tools/docs/_prompt-external-modules-page.md | 59 - tools/docs/fix-refs.md | 91 - tools/fix-doc-links.js | 285 - tools/format-workflow-md.js | 263 - tools/lib/xml-utils.js | 13 - tools/migrate-custom-module-paths.js | 124 - tools/platform-codes.yaml | 157 - tools/schema/agent.js | 491 - tools/validate-agent-schema.js | 110 - tools/validate-doc-links.js | 407 - tools/validate-file-refs.js | 554 - tools/validate-svg-changes.sh | 356 - website/README.md | 75 - website/astro.config.mjs | 136 - website/public/favicon.ico | Bin 4286 -> 0 bytes website/public/img/bmad-dark.png | Bin 65820 -> 0 bytes website/public/img/bmad-light.png | Bin 41278 -> 0 bytes website/public/workflow-map-diagram.html | 361 - website/src/components/Banner.astro | 62 - website/src/components/Header.astro | 96 - website/src/components/MobileMenuFooter.astro | 33 - website/src/content/config.ts | 6 - website/src/content/docs | 1 - website/src/lib/site-url.mjs | 25 - website/src/pages/404.astro | 11 - website/src/pages/robots.txt.ts | 48 - website/src/rehype-base-paths.js | 112 - website/src/rehype-markdown-links.js | 119 - website/src/styles/custom.css | 805 - 491 files changed, 90541 deletions(-) delete mode 100644 .augment/code_review_guidelines.yaml delete mode 100644 .claude/skills/bmad-os-audit-file-refs/SKILL.md delete mode 100644 .claude/skills/bmad-os-audit-file-refs/prompts/instructions.md delete mode 100644 .claude/skills/bmad-os-changelog-social/SKILL.md delete mode 100644 .claude/skills/bmad-os-changelog-social/examples/discord-example.md delete mode 100644 .claude/skills/bmad-os-changelog-social/examples/linkedin-example.md delete mode 100644 .claude/skills/bmad-os-changelog-social/examples/twitter-example.md delete mode 100644 .claude/skills/bmad-os-diataxis-style-fix/SKILL.md delete mode 100644 .claude/skills/bmad-os-diataxis-style-fix/prompts/instructions.md delete mode 100644 .claude/skills/bmad-os-draft-changelog/SKILL.md delete mode 100644 .claude/skills/bmad-os-draft-changelog/prompts/instructions.md delete mode 100644 .claude/skills/bmad-os-gh-triage/SKILL.md delete mode 100644 .claude/skills/bmad-os-gh-triage/prompts/agent-prompt.md delete mode 100644 .claude/skills/bmad-os-gh-triage/prompts/instructions.md delete mode 100644 .claude/skills/bmad-os-release-module/SKILL.md delete mode 100644 .claude/skills/bmad-os-release-module/prompts/instructions.md delete mode 100644 .claude/skills/bmad-os-review-pr/SKILL.md delete mode 100644 .claude/skills/bmad-os-review-pr/prompts/instructions.md delete mode 100644 .claude/skills/bmad-os-root-cause-analysis/SKILL.md delete mode 100644 .claude/skills/bmad-os-root-cause-analysis/prompts/instructions.md delete mode 100644 .coderabbit.yaml delete mode 100644 .github/CODE_OF_CONDUCT.md delete mode 100644 .github/FUNDING.yaml delete mode 100644 .github/ISSUE_TEMPLATE/bug-report.yaml delete mode 100644 .github/ISSUE_TEMPLATE/config.yaml delete mode 100644 .github/ISSUE_TEMPLATE/documentation.yaml delete mode 100644 .github/ISSUE_TEMPLATE/feature-request.md delete mode 100644 .github/ISSUE_TEMPLATE/issue.md delete mode 100644 .github/PULL_REQUEST_TEMPLATE.md delete mode 100644 .github/scripts/discord-helpers.sh delete mode 100644 .github/workflows/coderabbit-review.yaml delete mode 100644 .github/workflows/discord.yaml delete mode 100644 .github/workflows/docs.yaml delete mode 100644 .github/workflows/quality.yaml delete mode 100644 .gitignore delete mode 100755 .husky/pre-commit delete mode 100644 .markdownlint-cli2.yaml delete mode 100644 .npmrc delete mode 100644 .nvmrc delete mode 100644 .prettierignore delete mode 100644 .vscode/settings.json delete mode 100644 CHANGELOG.md delete mode 100644 CNAME delete mode 100644 CONTRIBUTING.md delete mode 100644 CONTRIBUTORS.md delete mode 100644 LICENSE delete mode 100644 README.md delete mode 100644 SECURITY.md delete mode 100644 TRADEMARK.md delete mode 100644 Wordmark.png delete mode 100644 banner-bmad-method.png delete mode 100644 docs/404.md delete mode 100644 docs/_STYLE_GUIDE.md delete mode 100644 docs/explanation/advanced-elicitation.md delete mode 100644 docs/explanation/adversarial-review.md delete mode 100644 docs/explanation/brainstorming.md delete mode 100644 docs/explanation/established-projects-faq.md delete mode 100644 docs/explanation/party-mode.md delete mode 100644 docs/explanation/preventing-agent-conflicts.md delete mode 100644 docs/explanation/project-context.md delete mode 100644 docs/explanation/quick-flow.md delete mode 100644 docs/explanation/why-solutioning-matters.md delete mode 100644 docs/how-to/customize-bmad.md delete mode 100644 docs/how-to/established-projects.md delete mode 100644 docs/how-to/get-answers-about-bmad.md delete mode 100644 docs/how-to/install-bmad.md delete mode 100644 docs/how-to/non-interactive-installation.md delete mode 100644 docs/how-to/project-context.md delete mode 100644 docs/how-to/quick-fixes.md delete mode 100644 docs/how-to/shard-large-documents.md delete mode 100644 docs/how-to/upgrade-to-v6.md delete mode 100644 docs/index.md delete mode 100644 docs/reference/agents.md delete mode 100644 docs/reference/commands.md delete mode 100644 docs/reference/modules.md delete mode 100644 docs/reference/testing.md delete mode 100644 docs/reference/workflow-map.md delete mode 100644 docs/roadmap.mdx delete mode 100644 docs/tutorials/getting-started.md delete mode 100644 eslint.config.mjs delete mode 100644 package-lock.json delete mode 100644 package.json delete mode 100644 prettier.config.mjs delete mode 100644 src/bmm/agents/analyst.agent.yaml delete mode 100644 src/bmm/agents/architect.agent.yaml delete mode 100644 src/bmm/agents/dev.agent.yaml delete mode 100644 src/bmm/agents/pm.agent.yaml delete mode 100644 src/bmm/agents/qa.agent.yaml delete mode 100644 src/bmm/agents/quick-flow-solo-dev.agent.yaml delete mode 100644 src/bmm/agents/sm.agent.yaml delete mode 100644 src/bmm/agents/tech-writer/tech-writer-sidecar/documentation-standards.md delete mode 100644 src/bmm/agents/tech-writer/tech-writer.agent.yaml delete mode 100644 src/bmm/agents/ux-designer.agent.yaml delete mode 100644 src/bmm/data/project-context-template.md delete mode 100644 src/bmm/module-help.csv delete mode 100644 src/bmm/module.yaml delete mode 100644 src/bmm/teams/default-party.csv delete mode 100644 src/bmm/teams/team-fullstack.yaml delete mode 100644 src/bmm/workflows/1-analysis/create-product-brief/product-brief.template.md delete mode 100644 src/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md delete mode 100644 src/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md delete mode 100644 src/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md delete mode 100644 src/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md delete mode 100644 src/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md delete mode 100644 src/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md delete mode 100644 src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md delete mode 100644 src/bmm/workflows/1-analysis/create-product-brief/workflow.md delete mode 100644 src/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md delete mode 100644 src/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md delete mode 100644 src/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md delete mode 100644 src/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md delete mode 100644 src/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md delete mode 100644 src/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md delete mode 100644 src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md delete mode 100644 src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md delete mode 100644 src/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md delete mode 100644 src/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md delete mode 100644 src/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md delete mode 100644 src/bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md delete mode 100644 src/bmm/workflows/1-analysis/research/research.template.md delete mode 100644 src/bmm/workflows/1-analysis/research/technical-steps/step-01-init.md delete mode 100644 src/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md delete mode 100644 src/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md delete mode 100644 src/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md delete mode 100644 src/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md delete mode 100644 src/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md delete mode 100644 src/bmm/workflows/1-analysis/research/workflow-domain-research.md delete mode 100644 src/bmm/workflows/1-analysis/research/workflow-market-research.md delete mode 100644 src/bmm/workflows/1-analysis/research/workflow-technical-research.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/data/domain-complexity.csv delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/data/project-types.csv delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01-init.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01b-continue.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02-discovery.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02b-vision.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02c-executive-summary.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-03-success.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-05-domain.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-06-innovation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-07-project-type.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-08-scoping.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-09-functional.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-10-nonfunctional.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-11-polish.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01-discovery.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01b-legacy-conversion.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-02-review.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-03-edit.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02-format-detection.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02b-parity-check.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-03-density-validation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-04-brief-coverage-validation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-05-measurability-validation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-06-traceability-validation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-07-implementation-leakage-validation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-08-domain-compliance-validation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-09-project-type-validation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-10-smart-validation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-11-holistic-quality-validation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-12-completeness-validation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/templates/prd-template.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md delete mode 100644 src/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md delete mode 100644 src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md delete mode 100644 src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-02-prd-analysis.md delete mode 100644 src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-03-epic-coverage-validation.md delete mode 100644 src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-04-ux-alignment.md delete mode 100644 src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-05-epic-quality-review.md delete mode 100644 src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md delete mode 100644 src/bmm/workflows/3-solutioning/check-implementation-readiness/templates/readiness-report-template.md delete mode 100644 src/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/architecture-decision-template.md delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/data/domain-complexity.csv delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/data/project-types.csv delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/steps/step-01b-continue.md delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md delete mode 100644 src/bmm/workflows/3-solutioning/create-architecture/workflow.md delete mode 100644 src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md delete mode 100644 src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md delete mode 100644 src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md delete mode 100644 src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md delete mode 100644 src/bmm/workflows/3-solutioning/create-epics-and-stories/templates/epics-template.md delete mode 100644 src/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md delete mode 100644 src/bmm/workflows/4-implementation/code-review/checklist.md delete mode 100644 src/bmm/workflows/4-implementation/code-review/instructions.xml delete mode 100644 src/bmm/workflows/4-implementation/code-review/workflow.yaml delete mode 100644 src/bmm/workflows/4-implementation/correct-course/checklist.md delete mode 100644 src/bmm/workflows/4-implementation/correct-course/instructions.md delete mode 100644 src/bmm/workflows/4-implementation/correct-course/workflow.yaml delete mode 100644 src/bmm/workflows/4-implementation/create-story/checklist.md delete mode 100644 src/bmm/workflows/4-implementation/create-story/instructions.xml delete mode 100644 src/bmm/workflows/4-implementation/create-story/template.md delete mode 100644 src/bmm/workflows/4-implementation/create-story/workflow.yaml delete mode 100644 src/bmm/workflows/4-implementation/dev-story/checklist.md delete mode 100644 src/bmm/workflows/4-implementation/dev-story/instructions.xml delete mode 100644 src/bmm/workflows/4-implementation/dev-story/workflow.yaml delete mode 100644 src/bmm/workflows/4-implementation/retrospective/instructions.md delete mode 100644 src/bmm/workflows/4-implementation/retrospective/workflow.yaml delete mode 100644 src/bmm/workflows/4-implementation/sprint-planning/checklist.md delete mode 100644 src/bmm/workflows/4-implementation/sprint-planning/instructions.md delete mode 100644 src/bmm/workflows/4-implementation/sprint-planning/sprint-status-template.yaml delete mode 100644 src/bmm/workflows/4-implementation/sprint-planning/workflow.yaml delete mode 100644 src/bmm/workflows/4-implementation/sprint-status/instructions.md delete mode 100644 src/bmm/workflows/4-implementation/sprint-status/workflow.yaml delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-01-mode-detection.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-02-context-gathering.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-03-execute.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-04-self-check.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-05-adversarial-review.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-06-resolve-findings.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-01-understand.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-02-investigate.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-03-generate.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-spec/tech-spec-template.md delete mode 100644 src/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md delete mode 100644 src/bmm/workflows/document-project/checklist.md delete mode 100644 src/bmm/workflows/document-project/documentation-requirements.csv delete mode 100644 src/bmm/workflows/document-project/instructions.md delete mode 100644 src/bmm/workflows/document-project/templates/deep-dive-template.md delete mode 100644 src/bmm/workflows/document-project/templates/index-template.md delete mode 100644 src/bmm/workflows/document-project/templates/project-overview-template.md delete mode 100644 src/bmm/workflows/document-project/templates/project-scan-report-schema.json delete mode 100644 src/bmm/workflows/document-project/templates/source-tree-template.md delete mode 100644 src/bmm/workflows/document-project/workflow.yaml delete mode 100644 src/bmm/workflows/document-project/workflows/deep-dive-instructions.md delete mode 100644 src/bmm/workflows/document-project/workflows/deep-dive.yaml delete mode 100644 src/bmm/workflows/document-project/workflows/full-scan-instructions.md delete mode 100644 src/bmm/workflows/document-project/workflows/full-scan.yaml delete mode 100644 src/bmm/workflows/generate-project-context/project-context-template.md delete mode 100644 src/bmm/workflows/generate-project-context/steps/step-01-discover.md delete mode 100644 src/bmm/workflows/generate-project-context/steps/step-02-generate.md delete mode 100644 src/bmm/workflows/generate-project-context/steps/step-03-complete.md delete mode 100644 src/bmm/workflows/generate-project-context/workflow.md delete mode 100644 src/bmm/workflows/qa-generate-e2e-tests/checklist.md delete mode 100644 src/bmm/workflows/qa-generate-e2e-tests/instructions.md delete mode 100644 src/bmm/workflows/qa-generate-e2e-tests/workflow.yaml delete mode 100644 src/core/agents/bmad-master.agent.yaml delete mode 100644 src/core/module-help.csv delete mode 100644 src/core/module.yaml delete mode 100644 src/core/tasks/editorial-review-prose.xml delete mode 100644 src/core/tasks/editorial-review-structure.xml delete mode 100644 src/core/tasks/help.md delete mode 100644 src/core/tasks/index-docs.xml delete mode 100644 src/core/tasks/review-adversarial-general.xml delete mode 100644 src/core/tasks/review-edge-case-hunter.xml delete mode 100644 src/core/tasks/shard-doc.xml delete mode 100644 src/core/tasks/workflow.xml delete mode 100644 src/core/workflows/advanced-elicitation/methods.csv delete mode 100644 src/core/workflows/advanced-elicitation/workflow.xml delete mode 100644 src/core/workflows/brainstorming/brain-methods.csv delete mode 100644 src/core/workflows/brainstorming/steps/step-01-session-setup.md delete mode 100644 src/core/workflows/brainstorming/steps/step-01b-continue.md delete mode 100644 src/core/workflows/brainstorming/steps/step-02a-user-selected.md delete mode 100644 src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md delete mode 100644 src/core/workflows/brainstorming/steps/step-02c-random-selection.md delete mode 100644 src/core/workflows/brainstorming/steps/step-02d-progressive-flow.md delete mode 100644 src/core/workflows/brainstorming/steps/step-03-technique-execution.md delete mode 100644 src/core/workflows/brainstorming/steps/step-04-idea-organization.md delete mode 100644 src/core/workflows/brainstorming/template.md delete mode 100644 src/core/workflows/brainstorming/workflow.md delete mode 100644 src/core/workflows/party-mode/steps/step-01-agent-loading.md delete mode 100644 src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md delete mode 100644 src/core/workflows/party-mode/steps/step-03-graceful-exit.md delete mode 100644 src/core/workflows/party-mode/workflow.md delete mode 100644 src/utility/agent-components/activation-rules.txt delete mode 100644 src/utility/agent-components/activation-steps.txt delete mode 100644 src/utility/agent-components/agent-command-header.md delete mode 100644 src/utility/agent-components/agent.customize.template.yaml delete mode 100644 src/utility/agent-components/handler-action.txt delete mode 100644 src/utility/agent-components/handler-data.txt delete mode 100644 src/utility/agent-components/handler-exec.txt delete mode 100644 src/utility/agent-components/handler-multi.txt delete mode 100644 src/utility/agent-components/handler-tmpl.txt delete mode 100644 src/utility/agent-components/handler-validate-workflow.txt delete mode 100644 src/utility/agent-components/handler-workflow.txt delete mode 100644 src/utility/agent-components/menu-handlers.txt delete mode 100644 test/README.md delete mode 100644 test/adversarial-review-tests/README.md delete mode 100644 test/adversarial-review-tests/sample-content.md delete mode 100644 test/adversarial-review-tests/test-cases.yaml delete mode 100644 test/fixtures/agent-schema/invalid/critical-actions/actions-as-string.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/critical-actions/empty-string-in-actions.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu-commands/empty-command-target.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu-commands/no-command-target.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu-triggers/camel-case.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu-triggers/compound-invalid-format.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu-triggers/compound-mismatched-kebab.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu-triggers/duplicate-triggers.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu-triggers/empty-trigger.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu-triggers/leading-asterisk.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu-triggers/snake-case.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu-triggers/trigger-with-spaces.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu/empty-menu.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/menu/missing-menu.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/metadata/empty-module-string.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/metadata/empty-name.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/metadata/extra-metadata-fields.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/metadata/missing-id.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/persona/empty-principles-array.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/persona/empty-string-in-principles.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/persona/extra-persona-fields.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/persona/missing-role.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/prompts/empty-content.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/prompts/extra-prompt-fields.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/prompts/missing-content.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/prompts/missing-id.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/top-level/empty-file.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/top-level/extra-top-level-keys.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/top-level/missing-agent-key.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/yaml-errors/invalid-indentation.agent.yaml delete mode 100644 test/fixtures/agent-schema/invalid/yaml-errors/malformed-yaml.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/critical-actions/empty-critical-actions.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/critical-actions/no-critical-actions.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/critical-actions/valid-critical-actions.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/menu-commands/all-command-types.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/menu-commands/multiple-commands.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/menu-triggers/compound-triggers.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/menu-triggers/kebab-case-triggers.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/menu/multiple-menu-items.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/menu/single-menu-item.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/metadata/core-agent-with-module.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/metadata/empty-module-name-in-path.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/metadata/malformed-path-treated-as-core.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/metadata/module-agent-correct.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/metadata/module-agent-missing-module.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/metadata/wrong-module-value.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/persona/complete-persona.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/prompts/empty-prompts.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/prompts/no-prompts.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/prompts/valid-prompts-minimal.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/prompts/valid-prompts-with-description.agent.yaml delete mode 100644 test/fixtures/agent-schema/valid/top-level/minimal-core-agent.agent.yaml delete mode 100644 test/fixtures/file-refs-csv/invalid/all-empty-workflow.csv delete mode 100644 test/fixtures/file-refs-csv/invalid/empty-data.csv delete mode 100644 test/fixtures/file-refs-csv/invalid/no-workflow-column.csv delete mode 100644 test/fixtures/file-refs-csv/invalid/unresolvable-vars.csv delete mode 100644 test/fixtures/file-refs-csv/valid/bmm-style.csv delete mode 100644 test/fixtures/file-refs-csv/valid/core-style.csv delete mode 100644 test/fixtures/file-refs-csv/valid/minimal.csv delete mode 100644 test/test-agent-schema.js delete mode 100755 test/test-cli-integration.sh delete mode 100644 test/test-file-refs-csv.js delete mode 100644 test/test-installation-components.js delete mode 100644 test/test-rehype-plugins.mjs delete mode 100644 test/unit-test-schema.js delete mode 100755 tools/bmad-npx-wrapper.js delete mode 100644 tools/build-docs.mjs delete mode 100644 tools/cli/README.md delete mode 100755 tools/cli/bmad-cli.js delete mode 100644 tools/cli/commands/install.js delete mode 100644 tools/cli/commands/status.js delete mode 100644 tools/cli/commands/uninstall.js delete mode 100644 tools/cli/external-official-modules.yaml delete mode 100644 tools/cli/installers/install-messages.yaml delete mode 100644 tools/cli/installers/lib/core/config-collector.js delete mode 100644 tools/cli/installers/lib/core/custom-module-cache.js delete mode 100644 tools/cli/installers/lib/core/dependency-resolver.js delete mode 100644 tools/cli/installers/lib/core/detector.js delete mode 100644 tools/cli/installers/lib/core/ide-config-manager.js delete mode 100644 tools/cli/installers/lib/core/installer.js delete mode 100644 tools/cli/installers/lib/core/manifest-generator.js delete mode 100644 tools/cli/installers/lib/core/manifest.js delete mode 100644 tools/cli/installers/lib/custom/handler.js delete mode 100644 tools/cli/installers/lib/ide/_base-ide.js delete mode 100644 tools/cli/installers/lib/ide/_config-driven.js delete mode 100644 tools/cli/installers/lib/ide/codex.js delete mode 100644 tools/cli/installers/lib/ide/github-copilot.js delete mode 100644 tools/cli/installers/lib/ide/kilo.js delete mode 100644 tools/cli/installers/lib/ide/manager.js delete mode 100644 tools/cli/installers/lib/ide/platform-codes.js delete mode 100644 tools/cli/installers/lib/ide/platform-codes.yaml delete mode 100644 tools/cli/installers/lib/ide/rovodev.js delete mode 100644 tools/cli/installers/lib/ide/shared/agent-command-generator.js delete mode 100644 tools/cli/installers/lib/ide/shared/bmad-artifacts.js delete mode 100644 tools/cli/installers/lib/ide/shared/module-injections.js delete mode 100644 tools/cli/installers/lib/ide/shared/path-utils.js delete mode 100644 tools/cli/installers/lib/ide/shared/task-tool-command-generator.js delete mode 100644 tools/cli/installers/lib/ide/shared/workflow-command-generator.js delete mode 100644 tools/cli/installers/lib/ide/templates/agent-command-template.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/antigravity.md delete mode 120000 tools/cli/installers/lib/ide/templates/combined/claude-agent.md delete mode 120000 tools/cli/installers/lib/ide/templates/combined/claude-workflow-yaml.md delete mode 120000 tools/cli/installers/lib/ide/templates/combined/claude-workflow.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/default-agent.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/default-task.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/default-tool.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/default-workflow-yaml.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/default-workflow.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/gemini-agent.toml delete mode 100644 tools/cli/installers/lib/ide/templates/combined/gemini-task.toml delete mode 100644 tools/cli/installers/lib/ide/templates/combined/gemini-tool.toml delete mode 100644 tools/cli/installers/lib/ide/templates/combined/gemini-workflow-yaml.toml delete mode 100644 tools/cli/installers/lib/ide/templates/combined/gemini-workflow.toml delete mode 100644 tools/cli/installers/lib/ide/templates/combined/kiro-agent.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/kiro-task.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/kiro-tool.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/kiro-workflow-yaml.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/kiro-workflow.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/opencode-agent.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/opencode-task.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/opencode-tool.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/opencode-workflow-yaml.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/opencode-workflow.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/rovodev.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/trae.md delete mode 100644 tools/cli/installers/lib/ide/templates/combined/windsurf-workflow.md delete mode 100644 tools/cli/installers/lib/ide/templates/split/.gitkeep delete mode 100644 tools/cli/installers/lib/ide/templates/workflow-command-template.md delete mode 100644 tools/cli/installers/lib/ide/templates/workflow-commander.md delete mode 100644 tools/cli/installers/lib/message-loader.js delete mode 100644 tools/cli/installers/lib/modules/external-manager.js delete mode 100644 tools/cli/installers/lib/modules/manager.js delete mode 100644 tools/cli/lib/activation-builder.js delete mode 100644 tools/cli/lib/agent-analyzer.js delete mode 100644 tools/cli/lib/agent-party-generator.js delete mode 100644 tools/cli/lib/agent/compiler.js delete mode 100644 tools/cli/lib/agent/installer.js delete mode 100644 tools/cli/lib/agent/template-engine.js delete mode 100644 tools/cli/lib/cli-utils.js delete mode 100644 tools/cli/lib/config.js delete mode 100644 tools/cli/lib/file-ops.js delete mode 100644 tools/cli/lib/platform-codes.js delete mode 100644 tools/cli/lib/project-root.js delete mode 100644 tools/cli/lib/prompts.js delete mode 100644 tools/cli/lib/ui.js delete mode 100644 tools/cli/lib/xml-handler.js delete mode 100644 tools/cli/lib/xml-to-markdown.js delete mode 100755 tools/cli/lib/yaml-format.js delete mode 100644 tools/cli/lib/yaml-xml-builder.js delete mode 100644 tools/docs/_prompt-external-modules-page.md delete mode 100644 tools/docs/fix-refs.md delete mode 100644 tools/fix-doc-links.js delete mode 100755 tools/format-workflow-md.js delete mode 100644 tools/lib/xml-utils.js delete mode 100755 tools/migrate-custom-module-paths.js delete mode 100644 tools/platform-codes.yaml delete mode 100644 tools/schema/agent.js delete mode 100644 tools/validate-agent-schema.js delete mode 100644 tools/validate-doc-links.js delete mode 100644 tools/validate-file-refs.js delete mode 100755 tools/validate-svg-changes.sh delete mode 100644 website/README.md delete mode 100644 website/astro.config.mjs delete mode 100644 website/public/favicon.ico delete mode 100644 website/public/img/bmad-dark.png delete mode 100644 website/public/img/bmad-light.png delete mode 100644 website/public/workflow-map-diagram.html delete mode 100644 website/src/components/Banner.astro delete mode 100644 website/src/components/Header.astro delete mode 100644 website/src/components/MobileMenuFooter.astro delete mode 100644 website/src/content/config.ts delete mode 120000 website/src/content/docs delete mode 100644 website/src/lib/site-url.mjs delete mode 100644 website/src/pages/404.astro delete mode 100644 website/src/pages/robots.txt.ts delete mode 100644 website/src/rehype-base-paths.js delete mode 100644 website/src/rehype-markdown-links.js delete mode 100644 website/src/styles/custom.css diff --git a/.augment/code_review_guidelines.yaml b/.augment/code_review_guidelines.yaml deleted file mode 100644 index 02e4f2b95..000000000 --- a/.augment/code_review_guidelines.yaml +++ /dev/null @@ -1,271 +0,0 @@ -# Augment Code Review Guidelines for BMAD-METHOD -# https://docs.augmentcode.com/codereview/overview -# Focus: Workflow validation and quality - -file_paths_to_ignore: - # --- Shared baseline: tool configs --- - - ".coderabbit.yaml" - - ".augment/**" - - "eslint.config.mjs" - # --- Shared baseline: build output --- - - "dist/**" - - "build/**" - - "coverage/**" - # --- Shared baseline: vendored/generated --- - - "node_modules/**" - - "**/*.min.js" - - "**/*.generated.*" - - "**/*.bundle.md" - # --- Shared baseline: package metadata --- - - "package-lock.json" - # --- Shared baseline: binary/media --- - - "*.png" - - "*.jpg" - - "*.svg" - # --- Shared baseline: test fixtures --- - - "test/fixtures/**" - - "test/template-test-generator/**" - - "tools/template-test-generator/test-scenarios/**" - # --- Shared baseline: non-project dirs --- - - "_bmad*/**" - - "website/**" - - "z*/**" - - "sample-project/**" - - "test-project-install/**" - # --- Shared baseline: AI assistant dirs --- - - ".claude/**" - - ".codex/**" - - ".agent/**" - - ".agentvibes/**" - - ".kiro/**" - - ".roo/**" - - ".github/chatmodes/**" - # --- Shared baseline: build temp --- - - ".bundler-temp/**" - # --- Shared baseline: generated reports --- - - "**/validation-report-*.md" - - "CHANGELOG.md" - -areas: - # ============================================ - # WORKFLOW STRUCTURE RULES - # ============================================ - workflow_structure: - description: "Workflow folder organization and required components" - globs: - - "src/**/workflows/**" - rules: - - id: "workflow_entry_point_required" - description: "Every workflow folder must have workflow.yaml, workflow.md, or workflow.xml as entry point" - severity: "high" - - - id: "sharded_workflow_steps_folder" - description: "Sharded workflows (using workflow.md) must have steps/ folder with numbered files (step-01-*.md, step-02-*.md)" - severity: "high" - - - id: "standard_workflow_instructions" - description: "Standard workflows using workflow.yaml must include instructions.md for execution guidance" - severity: "medium" - - - id: "workflow_step_limit" - description: "Workflows should have 5-10 steps maximum to prevent context loss in LLM execution" - severity: "medium" - - # ============================================ - # WORKFLOW ENTRY FILE RULES - # ============================================ - workflow_definitions: - description: "Workflow entry files (workflow.yaml, workflow.md, workflow.xml)" - globs: - - "src/**/workflows/**/workflow.yaml" - - "src/**/workflows/**/workflow.md" - - "src/**/workflows/**/workflow.xml" - rules: - - id: "workflow_name_required" - description: "Workflow entry files must define 'name' field in frontmatter or root element" - severity: "high" - - - id: "workflow_description_required" - description: "Workflow entry files must include 'description' explaining the workflow's purpose" - severity: "high" - - - id: "workflow_config_source" - description: "Workflows should reference config_source for variable resolution (e.g., {project-root}/_bmad/module/config.yaml)" - severity: "medium" - - - id: "workflow_installed_path" - description: "Workflows should define installed_path for relative file references within the workflow" - severity: "medium" - - - id: "valid_step_references" - description: "Step file references in workflow entry must point to existing files" - severity: "high" - - # ============================================ - # SHARDED WORKFLOW STEP RULES - # ============================================ - workflow_steps: - description: "Individual step files in sharded workflows" - globs: - - "src/**/workflows/**/steps/step-*.md" - rules: - - id: "step_goal_required" - description: "Each step must clearly state its goal (## STEP GOAL, ## YOUR TASK, or step n='X' goal='...')" - severity: "high" - - - id: "step_mandatory_rules" - description: "Step files should include MANDATORY EXECUTION RULES section with universal agent behavior rules" - severity: "medium" - - - id: "step_context_boundaries" - description: "Step files should define CONTEXT BOUNDARIES explaining available context and limits" - severity: "medium" - - - id: "step_success_metrics" - description: "Step files should include SUCCESS METRICS section with ✅ checkmarks for validation criteria" - severity: "medium" - - - id: "step_failure_modes" - description: "Step files should include FAILURE MODES section with ❌ marks for anti-patterns to avoid" - severity: "medium" - - - id: "step_next_step_reference" - description: "Step files should reference the next step file path for sequential execution" - severity: "medium" - - - id: "step_no_forward_loading" - description: "Steps must NOT load future step files until current step completes - just-in-time loading only" - severity: "high" - - - id: "valid_file_references" - description: "File path references using {variable}/filename.md must point to existing files" - severity: "high" - - - id: "step_naming" - description: "Step files must be named step-NN-description.md (e.g., step-01-init.md, step-02-context.md)" - severity: "medium" - - - id: "halt_before_menu" - description: "Steps presenting user menus ([C] Continue, [a] Advanced, etc.) must HALT and wait for response" - severity: "high" - - # ============================================ - # XML WORKFLOW/TASK RULES - # ============================================ - xml_workflows: - description: "XML-based workflows and tasks" - globs: - - "src/**/workflows/**/*.xml" - - "src/**/tasks/**/*.xml" - rules: - - id: "xml_task_id_required" - description: "XML tasks must have unique 'id' attribute on root task element" - severity: "high" - - - id: "xml_llm_instructions" - description: "XML workflows should include section with critical execution instructions for the agent" - severity: "medium" - - - id: "xml_step_numbering" - description: "XML steps should use n='X' attribute for sequential numbering" - severity: "medium" - - - id: "xml_action_tags" - description: "Use for required actions, for user input (must HALT), for jumps, for conditionals" - severity: "medium" - - - id: "xml_ask_must_halt" - description: " tags require agent to HALT and wait for user response before continuing" - severity: "high" - - # ============================================ - # WORKFLOW CONTENT QUALITY - # ============================================ - workflow_content: - description: "Content quality and consistency rules for all workflow files" - globs: - - "src/**/workflows/**/*.md" - - "src/**/workflows/**/*.yaml" - rules: - - id: "communication_language_variable" - description: "Workflows should use {communication_language} variable for agent output language consistency" - severity: "low" - - - id: "path_placeholders_required" - description: "Use path placeholders (e.g. {project-root}, {installed_path}, {output_folder}) instead of hardcoded paths" - severity: "medium" - - - id: "no_time_estimates" - description: "Workflows should NOT include time estimates - AI development speed varies significantly" - severity: "low" - - - id: "facilitator_not_generator" - description: "Workflow agents should act as facilitators (guide user input) not content generators (create without input)" - severity: "medium" - - - id: "no_skip_optimization" - description: "Workflows must execute steps sequentially - no skipping or 'optimizing' step order" - severity: "high" - - # ============================================ - # AGENT DEFINITIONS - # ============================================ - agent_definitions: - description: "Agent YAML configuration files" - globs: - - "src/**/*.agent.yaml" - rules: - - id: "agent_metadata_required" - description: "Agent files must have metadata section with id, name, title, icon, and module" - severity: "high" - - - id: "agent_persona_required" - description: "Agent files must define persona with role, identity, communication_style, and principles" - severity: "high" - - - id: "agent_menu_valid_workflows" - description: "Menu triggers must reference valid workflow paths that exist" - severity: "high" - - # ============================================ - # TEMPLATES - # ============================================ - templates: - description: "Template files for workflow outputs" - globs: - - "src/**/template*.md" - - "src/**/templates/**/*.md" - rules: - - id: "placeholder_syntax" - description: "Use {variable_name} or {{variable_name}} syntax consistently for placeholders" - severity: "medium" - - - id: "template_sections_marked" - description: "Template sections that need generation should be clearly marked (e.g., )" - severity: "low" - - # ============================================ - # DOCUMENTATION - # ============================================ - documentation: - description: "Documentation files" - globs: - - "docs/**/*.md" - - "README.md" - - "CONTRIBUTING.md" - rules: - - id: "valid_internal_links" - description: "Internal markdown links must point to existing files" - severity: "medium" - - # ============================================ - # BUILD TOOLS - # ============================================ - build_tools: - description: "Build scripts and tooling" - globs: - - "tools/**" - rules: - - id: "script_error_handling" - description: "Scripts should handle errors gracefully with proper exit codes" - severity: "medium" diff --git a/.claude/skills/bmad-os-audit-file-refs/SKILL.md b/.claude/skills/bmad-os-audit-file-refs/SKILL.md deleted file mode 100644 index 637bcfd33..000000000 --- a/.claude/skills/bmad-os-audit-file-refs/SKILL.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -name: bmad-os-audit-file-refs -description: Audit BMAD source files for file-reference convention violations using parallel Haiku subagents. Use when users requests an "audit file references" for a skill, workflow or task. ---- - -Read `prompts/instructions.md` and execute. diff --git a/.claude/skills/bmad-os-audit-file-refs/prompts/instructions.md b/.claude/skills/bmad-os-audit-file-refs/prompts/instructions.md deleted file mode 100644 index cf9e3d6e8..000000000 --- a/.claude/skills/bmad-os-audit-file-refs/prompts/instructions.md +++ /dev/null @@ -1,59 +0,0 @@ -# audit-file-refs - -Audit new-format BMAD source files for file-reference convention violations using parallel Haiku subagents. - -## Convention - -In new-format BMAD workflow and task files (`src/bmm/`, `src/core/`, `src/utility/`), every file path reference must use one of these **valid** forms: - -- `{project-root}/_bmad/path/to/file.ext` — canonical form, always correct -- `{installed_path}/relative/path` — valid in new-format step files (always defined by workflow.md before any step is reached) -- Template/runtime variables: `{nextStepFile}`, `{workflowFile}`, `{{mustache}}`, `{output_folder}`, `{communication_language}`, etc. — skip these, they are substituted at runtime - -**Flag any reference that uses:** - -- `./step-NN.md` or `../something.md` — relative paths -- `step-NN.md` — bare filename with no path prefix -- `steps/step-NN.md` — bare steps-relative path (missing `{project-root}/_bmad/...` prefix) -- `` `_bmad/core/tasks/help.md` `` — bare `_bmad/` path (missing `{project-root}/`) -- `/Users/...`, `/home/...`, `C:\...` — absolute system paths - -References inside fenced code blocks (``` ``` ```) are examples — skip them. - -Old-format files in `src/bmm/workflows/4-implementation/` use `{installed_path}` by design within the XML calling chain — exclude that directory entirely. - -## Steps - -1. Run this command to get the file list: - ``` - find src/bmm src/core src/utility -type f \( -name "*.md" -o -name "*.yaml" \) | grep -v "4-implementation" | sort - ``` - -2. Divide the resulting file paths into batches of roughly 20 files each. - -3. For each batch, spawn a subagent (`subagent_type: "Explore"`, `model: "haiku"`) with this prompt (fill in the actual file paths): - - > Read each of these files (use the Read tool on each): - > [list the file paths from this batch] - > - > For each file, identify every line that contains a file path reference that violates the convention described below. Skip references inside fenced code blocks. Skip template variables (anything containing `{` that isn't `{project-root}` or `{installed_path}`). - > - > **Valid references:** `{project-root}/_bmad/...`, `{installed_path}/...`, template variables. - > **Flag:** bare filenames (`step-NN.md`), `./` or `../` relative paths, bare `steps/` paths, bare `_bmad/` paths (without `{project-root}/`), absolute system paths. - > - > Return findings as a list: - > `path/to/file.md:LINE_NUMBER | VIOLATION_TYPE | offending text` - > - > If a file has no violations, include it as: `path/to/file.md | clean` - > - > End your response with a single line: `FILES CHECKED: N` where N is the exact number of files you read. - -4. Collect all findings from all subagents. - -5. **Self-check before reporting:** Count the total number of files returned by the `find` command. Sum the `FILES CHECKED: N` values across all subagent responses. If the totals do not match, identify which files are missing and re-run subagents for those files before proceeding. Do not produce the final report until all files are accounted for. - -6. Output a final report: - - Group findings by violation type - - List each finding as `file:line — offending text` - - Show total count of violations and number of affected files - - If nothing found, say "All files conform to the convention." diff --git a/.claude/skills/bmad-os-changelog-social/SKILL.md b/.claude/skills/bmad-os-changelog-social/SKILL.md deleted file mode 100644 index d2e5cda29..000000000 --- a/.claude/skills/bmad-os-changelog-social/SKILL.md +++ /dev/null @@ -1,177 +0,0 @@ ---- -name: bmad-os-changelog-social -description: Generate social media announcements for Discord, Twitter, and LinkedIn from the latest changelog entry. Use when user asks to 'create release announcement' or 'create social posts' or share changelog updates. ---- - -# Changelog Social - -Generate engaging social media announcements from changelog entries. - -## Workflow - -### Step 1: Extract Changelog Entry - -Read `./CHANGELOG.md` and extract the latest version entry. The changelog follows this format: - -```markdown -## [VERSION] - -### 🎁 Features -* **Title** — Description - -### 🐛 Bug Fixes -* **Title** — Description - -### 📚 Documentation -* **Title** — Description - -### 🔧 Maintenance -* **Title** — Description -``` - -Parse: -- **Version number** (e.g., `6.0.0-Beta.5`) -- **Features** - New functionality, enhancements -- **Bug Fixes** - Fixes users will care about -- **Documentation** - New or improved docs -- **Maintenance** - Dependency updates, tooling improvements - -### Step 2: Get Git Contributors - -Use git log to find contributors since the previous version. Get commits between the current version tag and the previous one: - -```bash -# Find the previous version tag first -git tag --sort=-version:refname | head -5 - -# Get commits between versions with PR numbers and authors -git log .. --pretty=format:"%h|%s|%an" --grep="#" -``` - -Extract PR numbers from commit messages that contain `#` followed by digits. Compile unique contributors. - -### Step 3: Generate Discord Announcement - -**Limit: 2,000 characters per message.** Split into multiple messages if needed. - -Use this template style: - -```markdown -🚀 **BMad vVERSION RELEASED!** - -🎉 [Brief hype sentence] - -🪥 **KEY HIGHLIGHT** - [One-line summary] - -🎯 **CATEGORY NAME** -• Feature one - brief description -• Feature two - brief description -• Coming soon: Future teaser - -🔧 **ANOTHER CATEGORY** -• Fix or feature -• Another item - -📚 **DOCS OR OTHER** -• Item -• Item with link - -🌟 **COMMUNITY PHILOSOPHY** (optional - include for major releases) -• Everything is FREE - No paywalls -• Knowledge shared, not sold - -📊 **STATS** -X commits | Y PRs merged | Z files changed - -🙏 **CONTRIBUTORS** -@username1 (X PRs!), @username2 (Y PRs!) -@username3, @username4, username5 + dependabot 🛡️ -Community-driven FTW! 🌟 - -📦 **INSTALL:** -`npx bmad-method@VERSION install` - -⭐ **SUPPORT US:** -🌟 GitHub: github.com/bmad-code-org/BMAD-METHOD/ -📺 YouTube: youtube.com/@BMadCode -☕ Donate: buymeacoffee.com/bmad - -🔥 **Next version tease!** -``` - -**Content Strategy:** -- Focus on **user impact** - what's better for them? -- Highlight **annoying bugs fixed** that frustrated users -- Show **new capabilities** that enable workflows -- Keep it **punchy** - use emojis and short bullets -- Add **personality** - excitement, humor, gratitude - -### Step 4: Generate Twitter Post - -**Limit: 25,000 characters per tweet (Premium).** With Premium, use a single comprehensive post matching the Discord style (minus Discord-specific formatting). Aim for 1,500-3,000 characters for better engagement. - -**Threads are optional** — only use for truly massive releases where you want multiple engagement points. - -See `examples/twitter-example.md` for the single-post Premium format. - -## Content Selection Guidelines - -**Include:** -- New features that change workflows -- Bug fixes for annoying/blocking issues -- Documentation that helps users -- Performance improvements -- New agents or workflows -- Breaking changes (call out clearly) - -**Skip/Minimize:** -- Internal refactoring -- Dependency updates (unless user-facing) -- Test improvements -- Minor style fixes - -**Emphasize:** -- "Finally fixed" issues -- "Faster" operations -- "Easier" workflows -- "Now supports" capabilities - -## Examples - -Reference example posts in `examples/` for tone and formatting guidance: - -- **discord-example.md** — Full Discord announcement with emojis, sections, contributor shout-outs -- **twitter-example.md** — Twitter thread format (5 tweets max for major releases) -- **linkedin-example.md** — Professional post for major/minor releases with significant features - -**When to use LinkedIn:** -- Major version releases (e.g., v6.0.0 Beta, v7.0.0) -- Minor releases with exceptional new features -- Community milestone announcements - -Read the appropriate example file before generating to match the established style and voice. - -## Output Format - -**CRITICAL: ALWAYS write to files** - Create files in `_bmad-output/social/` directory: - -1. `{repo-name}-discord-{version}.md` - Discord announcement -2. `{repo-name}-twitter-{version}.md` - Twitter post -3. `{repo-name}-linkedin-{version}.md` - LinkedIn post (if applicable) - -Also present a preview in the chat: - -```markdown -## Discord Announcement - -[paste Discord content here] - -## Twitter Post - -[paste Twitter content here] -``` - -Files created: -- `_bmad-output/social/{filename}` - -Offer to make adjustments if the user wants different emphasis, tone, or content. diff --git a/.claude/skills/bmad-os-changelog-social/examples/discord-example.md b/.claude/skills/bmad-os-changelog-social/examples/discord-example.md deleted file mode 100644 index 325e8824e..000000000 --- a/.claude/skills/bmad-os-changelog-social/examples/discord-example.md +++ /dev/null @@ -1,53 +0,0 @@ -🚀 **BMad v6.0.0-alpha.23 RELEASED!** - -🎉 Huge update - almost beta! - -🪟 **WINDOWS INSTALLER FIXED** - Menu arrows issue should be fixed! CRLF & ESM problems resolved. - -🎯 **PRD WORKFLOWS IMPROVED** -• Validation & Edit workflows added! -• PRD Cohesion check ensures document flows beautifully -• Coming soon: Use of subprocess optimization (context saved!) -• Coming soon: Final format polish step in all workflows - Human consumption OR hyper-optimized LLM condensed initially! - -🔧 **WORKFLOW CREATOR & VALIDATOR** -• Subprocess support for advanced optimization -• Path violation checks ensure integrity -• Beyond error checking - offers optimization & flow suggestions! - -📚 **NEW DOCS SITE** - docs.bmad-method.org -• Diataxis framework: Tutorials, How-To, Explanations, References -• Current docs still being revised -• Tutorials, blogs & explainers coming soon! - -💡 **BRAINSTORMING REVOLUTION** -• 100+ idea goal (quantity-first!) -• Anti-bias protocol (pivot every 10 ideas) -• Chain-of-thought + simulated temperature prompts -• Coming soon: SubProcessing (on-the-fly sub agents) - -🌟 **COMMUNITY PHILOSOPHY** -• Everything is FREE - No paywalls, no gated content -• Knowledge shared, not sold -• No premium tiers - full access to our ideas - -📊 **27 commits | 217 links converted | 42+ docs created** - -🙏 **17 Community PR Authors in this release!** -@lum (6 PRs!), @q00 (3 PRs!), @phil (2 PRs!) -@mike, @alex, @ramiz, @sjennings + dependabot 🛡️ -Community-driven FTW! 🌟 - -📦 **INSTALL ALPHA:** -`npx bmad-method install` - -⭐ **SUPPORT US:** -🌟 GitHub: github.com/bmad-code-org/BMAD-METHOD/ -📺 YouTube: youtube.com/@BMadCode - -🎤 **SPEAKING & MEDIA** -Available for conferences, podcasts, media appearances! -Topics: AI-Native Organizations (Any Industry), BMad Method -DM on Discord for inquiries! - -🔥 **V6 Beta is DAYS away!** January 22nd ETA - new features such as xyz and abc bug fixes! diff --git a/.claude/skills/bmad-os-changelog-social/examples/linkedin-example.md b/.claude/skills/bmad-os-changelog-social/examples/linkedin-example.md deleted file mode 100644 index dc5919e65..000000000 --- a/.claude/skills/bmad-os-changelog-social/examples/linkedin-example.md +++ /dev/null @@ -1,49 +0,0 @@ -🚀 **Announcing BMad Method v6.0.0 Beta - AI-Native Agile Development Framework** - -I'm excited to share that BMad Method, the open-source AI-driven agile development framework, is entering Beta! After 27 alpha releases and countless community contributions, we're approaching a major milestone. - -**What's New in v6.0.0-alpha.23** - -🪟 **Windows Compatibility Fixed** -We've resolved the installer issues that affected Windows users. The menu arrows problem, CRLF handling, and ESM compatibility are all resolved. - -🎯 **Enhanced PRD Workflows** -Our Product Requirements Document workflows now include validation and editing capabilities, with a new cohesion check that ensures your documents flow beautifully. Subprocess optimization is coming soon to save even more context. - -🔧 **Workflow Creator & Validator** -New tools for creating and validating workflows with subprocess support, path violation checks, and optimization suggestions that go beyond simple error checking. - -📚 **New Documentation Platform** -We've launched docs.bmad-method.org using the Diataxis framework - providing clear separation between tutorials, how-to guides, explanations, and references. Our documentation is being continuously revised and expanded. - -💡 **Brainstorming Revolution** -Our brainstorming workflows now use research-backed techniques: 100+ idea goals, anti-bias protocols, chain-of-thought reasoning, and simulated temperature prompts for higher divergence. - -**Our Philosophy** - -Everything in BMad Method is FREE. No paywalls, no gated content, no premium tiers. We believe knowledge should be shared, not sold. This is community-driven development at its finest. - -**The Stats** -- 27 commits in this release -- 217 documentation links converted -- 42+ new documents created -- 17 community PR authors contributed - -**Get Started** - -``` -npx bmad-method@alpha install -``` - -**Learn More** -- GitHub: github.com/bmad-code-org/BMAD-METHOD -- YouTube: youtube.com/@BMadCode -- Docs: docs.bmad-method.org - -**What's Next?** - -Beta is just days away with an ETA of January 22nd. We're also available for conferences, podcasts, and media appearances to discuss AI-Native Organizations and the BMad Method. - -Have you tried BMad Method yet? I'd love to hear about your experience in the comments! - -#AI #SoftwareDevelopment #Agile #OpenSource #DevTools #LLM #AgentEngineering diff --git a/.claude/skills/bmad-os-changelog-social/examples/twitter-example.md b/.claude/skills/bmad-os-changelog-social/examples/twitter-example.md deleted file mode 100644 index d8a0feaed..000000000 --- a/.claude/skills/bmad-os-changelog-social/examples/twitter-example.md +++ /dev/null @@ -1,55 +0,0 @@ -🚀 **BMad v6.0.0-alpha.23 RELEASED!** - -Huge update - we're almost at Beta! 🎉 - -🪟 **WINDOWS INSTALLER FIXED** - Menu arrows issue should be fixed! CRLF & ESM problems resolved. - -🎯 **PRD WORKFLOWS IMPROVED** -• Validation & Edit workflows added! -• PRD Cohesion check ensures document flows beautifully -• Coming soon: Subprocess optimization (context saved!) -• Coming soon: Final format polish step in all workflows - -🔧 **WORKFLOW CREATOR & VALIDATOR** -• Subprocess support for advanced optimization -• Path violation checks ensure integrity -• Beyond error checking - offers optimization & flow suggestions! - -📚 **NEW DOCS SITE** - docs.bmad-method.org -• Diataxis framework: Tutorials, How-To, Explanations, References -• Current docs still being revised -• Tutorials, blogs & explainers coming soon! - -💡 **BRAINSTORMING REVOLUTION** -• 100+ idea goal (quantity-first!) -• Anti-bias protocol (pivot every 10 ideas) -• Chain-of-thought + simulated temperature prompts -• Coming soon: SubProcessing (on-the-fly sub agents) - -🌟 **COMMUNITY PHILOSOPHY** -• Everything is FREE - No paywalls, no gated content -• Knowledge shared, not sold -• No premium tiers - full access to our ideas - -📊 **27 commits | 217 links converted | 42+ docs created** - -🙏 **17 Community PR Authors in this release!** -@lum (6 PRs!), @q00 (3 PRs!), @phil (2 PRs!) -@mike, @alex, @ramiz, @sjennings + dependabot 🛡️ -Community-driven FTW! 🌟 - -📦 **INSTALL ALPHA:** -`npx bmad-method install` - -⭐ **SUPPORT US:** -🌟 GitHub: github.com/bmad-code-org/BMAD-METHOD/ -📺 YouTube: youtube.com/@BMadCode - -🎤 **SPEAKING & MEDIA** -Available for conferences, podcasts, media appearances! -Topics: AI-Native Organizations (Any Industry), BMad Method -DM on Discord for inquiries! - -🔥 **V6 Beta is DAYS away!** January 22nd ETA! - -#AI #DevTools #Agile #OpenSource #LLM #AgentEngineering diff --git a/.claude/skills/bmad-os-diataxis-style-fix/SKILL.md b/.claude/skills/bmad-os-diataxis-style-fix/SKILL.md deleted file mode 100644 index 8a4f69ae6..000000000 --- a/.claude/skills/bmad-os-diataxis-style-fix/SKILL.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -name: bmad-os-diataxis-style-fix -description: Fixes documentation to comply with Diataxis framework and BMad Method style guide rules. Use when user asks to check or fix style of files under the docs folder. ---- - -Read `prompts/instructions.md` and execute. diff --git a/.claude/skills/bmad-os-diataxis-style-fix/prompts/instructions.md b/.claude/skills/bmad-os-diataxis-style-fix/prompts/instructions.md deleted file mode 100644 index 827e39115..000000000 --- a/.claude/skills/bmad-os-diataxis-style-fix/prompts/instructions.md +++ /dev/null @@ -1,229 +0,0 @@ -# Diataxis Style Fixer - -Automatically fixes documentation to comply with the Diataxis framework and BMad Method style guide. - -## CRITICAL RULES - -- **NEVER commit or push changes** — let the user review first -- **NEVER make destructive edits** — preserve all content, only fix formatting -- **Use Edit tool** — make targeted fixes, not full file rewrites -- **Show summary** — after fixing, list all changes made - -## Input - -Documentation file path or directory to fix. Defaults to `docs/` if not specified. - -## Step 1: Understand Diataxis Framework - -**Diataxis** is a documentation framework that categorizes content into four types based on two axes: - -| | **Learning** (oriented toward future) | **Doing** (oriented toward present) | -| -------------- | ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | -| **Practical** | **Tutorials** — lessons that guide learners through achieving a specific goal | **How-to guides** — step-by-step instructions for solving a specific problem | -| **Conceptual** | **Explanation** — content that clarifies and describes underlying concepts | **Reference** — technical descriptions, organized for lookup | - -**Key principles:** -- Each document type serves a distinct user need -- Don't mix types — a tutorial shouldn't explain concepts deeply -- Focus on the user's goal, not exhaustive coverage -- Structure follows purpose (tutorials are linear, reference is scannable) - -## Step 2: Read the Style Guide - -Read the project's style guide at `docs/_STYLE_GUIDE.md` to understand all project-specific conventions. - -## Step 3: Detect Document Type - -Based on file location, determine the document type: - -| Location | Diataxis Type | -| -------------------- | -------------------- | -| `/docs/tutorials/` | Tutorial | -| `/docs/how-to/` | How-to guide | -| `/docs/explanation/` | Explanation | -| `/docs/reference/` | Reference | -| `/docs/glossary/` | Reference (glossary) | - -## Step 4: Find and Fix Issues - -For each markdown file, scan for issues and fix them: - -### Universal Fixes (All Doc Types) - -**Horizontal Rules (`---`)** -- Remove any `---` outside of YAML frontmatter -- Replace with `##` section headers or admonitions as appropriate - -**`####` Headers** -- Replace with bold text: `#### Header` → `**Header**` -- Or convert to admonition if it's a warning/notice - -**"Related" or "Next:" Sections** -- Remove entire section including links -- The sidebar handles navigation - -**Deeply Nested Lists** -- Break into sections with `##` headers -- Flatten to max 3 levels - -**Code Blocks for Dialogue/Examples** -- Convert to admonitions: - ``` - :::note[Example] - [content] - ::: - ``` - -**Bold Paragraph Callouts** -- Convert to admonitions with appropriate type - -**Too Many Admonitions** -- Limit to 1-2 per section (tutorials allow 3-4 per major section) -- Consolidate related admonitions -- Remove less critical ones if over limit - -**Table Cells / List Items > 2 Sentences** -- Break into multiple rows/cells -- Or shorten to 1-2 sentences - -**Header Budget Exceeded** -- Merge related sections -- Convert some `##` to `###` subsections -- Goal: 8-12 `##` per doc; 2-3 `###` per section - -### Type-Specific Fixes - -**Tutorials** (`/docs/tutorials/`) -- Ensure hook describes outcome in 1-2 sentences -- Add "What You'll Learn" bullet section if missing -- Add `:::note[Prerequisites]` if missing -- Add `:::tip[Quick Path]` TL;DR at top if missing -- Use tables for phases, commands, agents -- Add "What You've Accomplished" section if missing -- Add Quick Reference table if missing -- Add Common Questions section if missing -- Add Getting Help section if missing -- Add `:::tip[Key Takeaways]` at end if missing - -**How-To** (`/docs/how-to/`) -- Ensure hook starts with "Use the `X` workflow to..." -- Add "When to Use This" with 3-5 bullets if missing -- Add `:::note[Prerequisites]` if missing -- Ensure steps are numbered `###` with action verbs -- Add "What You Get" describing outputs if missing - -**Explanation** (`/docs/explanation/`) -- Ensure hook states what document explains -- Organize content into scannable `##` sections -- Add comparison tables for 3+ options -- Link to how-to guides for procedural questions -- Limit to 2-3 admonitions per document - -**Reference** (`/docs/reference/`) -- Ensure hook states what document references -- Ensure structure matches reference type -- Use consistent item structure throughout -- Use tables for structured/comparative data -- Link to explanation docs for conceptual depth -- Limit to 1-2 admonitions per document - -**Glossary** (`/docs/glossary/` or glossary files) -- Ensure categories as `##` headers -- Ensure terms in tables (not individual headers) -- Definitions 1-2 sentences max -- Bold term names in cells - -## Step 5: Apply Fixes - -For each file with issues: -1. Read the file -2. Use Edit tool for each fix -3. Track what was changed - -## Step 6: Summary - -After processing all files, output a summary: - -```markdown -# Style Fixes Applied - -**Files processed:** N -**Files modified:** N - -## Changes Made - -### `path/to/file.md` -- Removed horizontal rule at line 45 -- Converted `####` headers to bold text -- Added `:::tip[Quick Path]` admonition -- Consolidated 3 admonitions into 2 - -### `path/to/other.md` -- Removed "Related:" section -- Fixed table cell length (broke into 2 rows) - -## Review Required - -Please review the changes. When satisfied, commit and push as needed. -``` - -## Common Patterns - -**Converting `####` to bold:** -```markdown -#### Important Note -Some text here. -``` -→ -```markdown -**Important Note** - -Some text here. -``` - -**Removing horizontal rule:** -```markdown -Some content above. - ---- - -Some content below. -``` -→ -```markdown -Some content above. - -## [Descriptive Section Header] - -Some content below. -``` - -**Converting code block to admonition:** -```markdown -``` -User: What should I do? - -Agent: Run the workflow. -``` -``` -→ -```markdown -:::note[Example] - -**User:** What should I do? - -**Agent:** Run the workflow. - -::: -``` - -**Converting bold paragraph to admonition:** -```markdown -**IMPORTANT:** This is critical that you read this before proceeding. -``` -→ -```markdown -:::caution[Important] -This is critical that you read this before proceeding. -::: -``` diff --git a/.claude/skills/bmad-os-draft-changelog/SKILL.md b/.claude/skills/bmad-os-draft-changelog/SKILL.md deleted file mode 100644 index aab75dd98..000000000 --- a/.claude/skills/bmad-os-draft-changelog/SKILL.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -name: bmad-os-draft-changelog -description: "Analyzes changes since last release and updates CHANGELOG.md ONLY. Use when users requests 'update the changelog' or 'prepare changelog release notes'" ---- - -Read `prompts/instructions.md` and execute. diff --git a/.claude/skills/bmad-os-draft-changelog/prompts/instructions.md b/.claude/skills/bmad-os-draft-changelog/prompts/instructions.md deleted file mode 100644 index ef3feccef..000000000 --- a/.claude/skills/bmad-os-draft-changelog/prompts/instructions.md +++ /dev/null @@ -1,82 +0,0 @@ -# Draft Changelog Execution - -## ⚠️ IMPORTANT - READ FIRST - -**This skill ONLY updates CHANGELOG.md. That is its entire purpose.** - -- **DO** update CHANGELOG.md with the new version entry -- **DO** present the draft for user review before editing -- **DO NOT** trigger any GitHub release workflows -- **DO NOT** run any other skills or workflows automatically -- **DO NOT** make any commits - -After the changelog is complete, you may suggest the user can run `/release-module` if they want to proceed with the actual release — but NEVER trigger it yourself. - -## Input -Project path (or run from project root) - -## Step 1: Identify Current State -- Get the latest released tag -- Get current version -- Verify there are commits since the last release - -## Step 2: Launch Explore Agent - -Use `thoroughness: "very thorough"` to analyze all changes since the last release tag. - -**Key: For each merge commit, look up the merged PR/issue that was closed.** -- Use `gh pr view` or git commit body to find the PR number -- Read the PR description and comments to understand full context -- Don't rely solely on commit merge messages - they lack context - -**Analyze:** - -1. **All merges/commits** since the last tag -2. **For each merge, read the original PR/issue** that was closed -3. **Files changed** with statistics -4. **Categorize changes:** - - 🎁 **Features** - New functionality, new agents, new workflows - - 🐛 **Bug Fixes** - Fixed bugs, corrected issues - - ♻️ **Refactoring** - Code improvements, reorganization - - 📚 **Documentation** - Docs updates, README changes - - 🔧 **Maintenance** - Dependency updates, tooling, infrastructure - - 💥 **Breaking Changes** - Changes that may affect users - -**Provide:** -- Comprehensive summary of ALL changes with PR context -- Categorization of each change -- Identification of breaking changes -- Significance assessment (major/minor/trivial) - -## Step 3: Generate Draft Changelog - -Format: -```markdown -## v0.X.X - [Date] - -* [Change 1 - categorized by type] -* [Change 2] -``` - -Guidelines: -- Present tense ("Fix bug" not "Fixed bug") -- Most significant changes first -- Group related changes -- Clear, concise language -- For breaking changes, clearly indicate impact - -## Step 4: Present Draft & Update CHANGELOG.md - -Show the draft with current version, last tag, commit count, and options to edit/retry. - -When user accepts: -1. Update CHANGELOG.md with the new entry (insert at top, after `# Changelog` header) -2. STOP. That's it. You're done. - -You may optionally suggest: *"When ready, you can run `/release-module` to create the actual release."* - -**DO NOT:** -- Trigger any GitHub workflows -- Run any other skills -- Make any commits -- Do anything beyond updating CHANGELOG.md diff --git a/.claude/skills/bmad-os-gh-triage/SKILL.md b/.claude/skills/bmad-os-gh-triage/SKILL.md deleted file mode 100644 index 020fdd4e2..000000000 --- a/.claude/skills/bmad-os-gh-triage/SKILL.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -name: bmad-os-gh-triage -description: Analyze all github issues. Use when the user says 'triage the github issues' or 'analyze open github issues'. ---- - -Read `prompts/instructions.md` and execute. diff --git a/.claude/skills/bmad-os-gh-triage/prompts/agent-prompt.md b/.claude/skills/bmad-os-gh-triage/prompts/agent-prompt.md deleted file mode 100644 index 5c0d7d8d8..000000000 --- a/.claude/skills/bmad-os-gh-triage/prompts/agent-prompt.md +++ /dev/null @@ -1,60 +0,0 @@ -You are analyzing a batch of GitHub issues for deep understanding and triage. - -**YOUR TASK:** -Read the issues in your batch and provide DEEP analysis: - -1. **For EACH issue, analyze:** - - What is this ACTUALLY about? (beyond keywords) - - What component/system does it affect? - - What's the impact and severity? - - Is it a bug, feature request, or something else? - - What specific theme does it belong to? - -2. **PRIORITY ASSESSMENT:** - - CRITICAL: Blocks users, security issues, data loss, broken installers - - HIGH: Major functionality broken, important features missing - - MEDIUM: Workarounds available, minor bugs, nice-to-have features - - LOW: Edge cases, cosmetic issues, questions - -3. **RELATIONSHIPS:** - - Duplicates: Near-identical issues about the same problem - - Related: Issues connected by theme or root cause - - Dependencies: One issue blocks or requires another - -**YOUR BATCH:** -[Paste the batch of issues here - each with number, title, body, labels] - -**OUTPUT FORMAT (JSON only, no markdown):** -{ - "issues": [ - { - "number": 123, - "title": "issue title", - "deep_understanding": "2-3 sentences explaining what this is really about", - "affected_components": ["installer", "workflows", "docs"], - "issue_type": "bug/feature/question/tech-debt", - "priority": "CRITICAL/HIGH/MEDIUM/LOW", - "priority_rationale": "Why this priority level", - "theme": "installation/workflow/integration/docs/ide-support/etc", - "relationships": { - "duplicates_of": [456], - "related_to": [789, 101], - "blocks": [111] - } - } - ], - "cross_repo_issues": [ - {"number": 123, "target_repo": "bmad-builder", "reason": "about agent builder"} - ], - "cleanup_candidates": [ - {"number": 456, "reason": "v4-related/outdated/duplicate"} - ], - "themes_found": { - "Installation Blockers": { - "count": 5, - "root_cause": "Common pattern if identifiable" - } - } -} - -Return ONLY valid JSON. No explanations outside the JSON structure. diff --git a/.claude/skills/bmad-os-gh-triage/prompts/instructions.md b/.claude/skills/bmad-os-gh-triage/prompts/instructions.md deleted file mode 100644 index 782d23268..000000000 --- a/.claude/skills/bmad-os-gh-triage/prompts/instructions.md +++ /dev/null @@ -1,74 +0,0 @@ -# GitHub Issue Triage with AI Analysis - -**CRITICAL RULES:** -- NEVER include time or effort estimates in output or recommendations -- Focus on WHAT needs to be done, not HOW LONG it takes -- Use Bash tool with gh CLI for all GitHub operations - -## Execution - -### Step 1: Fetch Issues -Use `gh issue list --json number,title,body,labels` to fetch all open issues. - -### Step 2: Batch Creation -Split issues into batches of ~10 issues each for parallel analysis. - -### Step 3: Parallel Agent Analysis -For EACH batch, use the Task tool with `subagent_type=general-purpose` to launch an agent with prompt from `prompts/agent-prompt.md` - -### Step 4: Consolidate & Generate Report -After all agents complete, create a comprehensive markdown report saved to `_bmad-output/triage-reports/triage-YYYY-MM-DD.md` - -## Report Format - -### Executive Summary -- Total issues analyzed -- Issue count by priority (CRITICAL, HIGH, MEDIUM, LOW) -- Major themes discovered -- Top 5 critical issues requiring immediate attention - -### Critical Issues (CRITICAL Priority) -For each CRITICAL issue: -- **#123 - [Issue Title](url)** -- **What it's about:** [Deep understanding] -- **Affected:** [Components] -- **Why Critical:** [Rationale] -- **Suggested Action:** [Specific action] - -### High Priority Issues (HIGH Priority) -Same format as Critical, grouped by theme. - -### Theme Clusters -For each major theme: -- **Theme Name** (N issues) -- **What connects these:** [Pattern] -- **Root cause:** [If identifiable] -- **Consolidated actions:** [Bulk actions if applicable] -- **Issues:** #123, #456, #789 - -### Relationships & Dependencies -- **Duplicates:** List pairs with `gh issue close` commands -- **Related Issues:** Groups of related issues -- **Dependencies:** Blocking relationships - -### Cross-Repo Issues -Issues that should be migrated to other repositories. - -For each, provide: -``` -gh issue close XXX --repo CURRENT_REPO --comment "This issue belongs in REPO. Please report at https://github.com/TARGET_REPO/issues/new" -``` - -### Cleanup Candidates -- **v4-related:** Deprecated version issues with close commands -- **Stale:** No activity >30 days -- **Low priority + old:** Low priority issues >60 days old - -### Actionable Next Steps -Specific, prioritized actions: -1. [CRITICAL] Fix broken installer - affects all new users -2. [HIGH] Resolve Windows path escaping issues -3. [HIGH] Address workflow integration bugs -etc. - -Include `gh` commands where applicable for bulk actions. diff --git a/.claude/skills/bmad-os-release-module/SKILL.md b/.claude/skills/bmad-os-release-module/SKILL.md deleted file mode 100644 index 557381ee0..000000000 --- a/.claude/skills/bmad-os-release-module/SKILL.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -name: bmad-os-release-module -description: Perform requested version bump, git tag, npm publish, GitHub release. Use when user requests 'perform a release' only. ---- - -Read `prompts/instructions.md` and execute. diff --git a/.claude/skills/bmad-os-release-module/prompts/instructions.md b/.claude/skills/bmad-os-release-module/prompts/instructions.md deleted file mode 100644 index 157ce0b33..000000000 --- a/.claude/skills/bmad-os-release-module/prompts/instructions.md +++ /dev/null @@ -1,53 +0,0 @@ -# Release BMad Module Execution - -## Input -Project path (or run from project root) - -## Execution Steps - -### Step 1: Get Current State -- Verify git working tree is clean -- Get latest tag and current version -- Check for unpushed commits - -### Step 2: Get Changelog Entry - -Ask the user for the changelog entry (from draft-changelog skill or manual). - -### Step 3: Confirm Changelog - -Show project name, current version, proposed next version, and changelog. Get confirmation. - -### Step 4: Confirm Version Bump Type - -Ask what type of bump: patch, minor, major, prerelease, or custom. - -### Step 5: Update CHANGELOG.md - -Insert new entry at top, commit, and push. - -### Step 6: Bump Version - -Run `npm version` to update package.json, create commit, and create tag. - -### Step 7: Push Tag - -Push the new version tag to GitHub. - -### Step 8: Publish to npm - -Publish the package. - -### Step 9: Create GitHub Release - -Create release with changelog notes using `gh release create`. - -## Error Handling - -Stop immediately on any step failure. Inform user and suggest fix. - -## Important Notes - -- Wait for user confirmation before destructive operations -- Push changelog commit before version bump -- Use explicit directory paths in commands diff --git a/.claude/skills/bmad-os-review-pr/SKILL.md b/.claude/skills/bmad-os-review-pr/SKILL.md deleted file mode 100644 index 67bb05bd5..000000000 --- a/.claude/skills/bmad-os-review-pr/SKILL.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -name: bmad-os-review-pr -description: Adversarial PR review tool (Raven's Verdict). Cynical deep review transformed into professional engineering findings. Use when user asks to 'review a PR' and provides a PR url or id. ---- - -Read `prompts/instructions.md` and execute. diff --git a/.claude/skills/bmad-os-review-pr/prompts/instructions.md b/.claude/skills/bmad-os-review-pr/prompts/instructions.md deleted file mode 100644 index 12d150049..000000000 --- a/.claude/skills/bmad-os-review-pr/prompts/instructions.md +++ /dev/null @@ -1,231 +0,0 @@ -# Raven's Verdict - Deep PR Review Tool - -A cynical adversarial review, transformed into cold engineering professionalism. - -## CRITICAL: Sandboxed Execution Rules - -Before proceeding, you MUST verify: - -- [ ] PR number or URL was EXPLICITLY provided in the user's message -- [ ] You are NOT inferring the PR from conversation history -- [ ] You are NOT looking at git branches, recent commits, or local state -- [ ] You are NOT guessing or assuming any PR numbers - -**If no explicit PR number/URL was provided, STOP immediately and ask:** -"What PR number or URL should I review?" - -## Preflight Checks - -### 0.1 Parse PR Input - -Extract PR number from user input. Examples of valid formats: - -- `123` (just the number) -- `#123` (with hash) -- `https://github.com/owner/repo/pull/123` (full URL) - -If a URL specifies a different repository than the current one: - -```bash -# Check current repo -gh repo view --json nameWithOwner -q '.nameWithOwner' -``` - -If mismatch detected, ask user: - -> "This PR is from `{detected_repo}` but we're in `{current_repo}`. Proceed with reviewing `{detected_repo}#123`? (y/n)" - -If user confirms, store `{REPO}` for use in all subsequent `gh` commands. - -### 0.2 Ensure Clean Checkout - -Verify the working tree is clean and check out the PR branch. - -```bash -# Check for uncommitted changes -git status --porcelain -``` - -If output is non-empty, STOP and tell user: - -> "You have uncommitted changes. Please commit or stash them before running a PR review." - -If clean, fetch and checkout the PR branch: - -```bash -# Fetch and checkout PR branch -# For cross-repo PRs, include --repo {REPO} -gh pr checkout {PR_NUMBER} [--repo {REPO}] -``` - -If checkout fails, STOP and report the error. - -Now you're on the PR branch with full access to all files as they exist in the PR. - -### 0.3 Check PR Size - -```bash -# For cross-repo PRs, include --repo {REPO} -gh pr view {PR_NUMBER} [--repo {REPO}] --json additions,deletions,changedFiles -q '{"additions": .additions, "deletions": .deletions, "files": .changedFiles}' -``` - -**Size thresholds:** - -| Metric | Warning Threshold | -| ------------- | ----------------- | -| Files changed | > 50 | -| Lines changed | > 5000 | - -If thresholds exceeded, ask user: - -> "This PR has {X} files and {Y} line changes. That's large. -> -> **[f] Focus** - Pick specific files or directories to review -> **[p] Proceed** - Review everything (may be slow/expensive) -> **[a] Abort** - Stop here" - -### 0.4 Note Binary Files - -```bash -# For cross-repo PRs, include --repo {REPO} -gh pr diff {PR_NUMBER} [--repo {REPO}] --name-only | grep -E '\.(png|jpg|jpeg|gif|ico|svg|woff|woff2|ttf|eot|pdf|zip|tar|gz|bin|exe|dll|so|dylib)$' || echo "No binary files detected" -``` - -Store list of binary files to skip. Note them in final output. - -## Adversarial Review - -### 1.1 Run Cynical Review - -**INTERNAL PERSONA - Never post this directly:** - -Task: You are a cynical, jaded code reviewer with zero patience for sloppy work. This PR was submitted by a clueless weasel and you expect to find problems. Find at least five issues to fix or improve in it. Number them. Be skeptical of everything. Ultrathink. - -Output format: - -```markdown -### [NUMBER]. [FINDING TITLE] [likely] - -**Severity:** [EMOJI] [LEVEL] - -[DESCRIPTION - be specific, include file:line references] -``` - -Severity scale: - -| Level | Emoji | Meaning | -| -------- | ----- | ------------------------------------------------------- | -| Critical | 🔴 | Security issue, data loss risk, or broken functionality | -| Moderate | 🟡 | Bug, performance issue, or significant code smell | -| Minor | 🟢 | Style, naming, minor improvement opportunity | - -Likely tag: - -- Add `[likely]` to findings with high confidence, e.g. with direct evidence -- Sort findings by severity (Critical → Moderate → Minor), not by confidence - -## Tone Transformation - -**Transform the cynical output into cold engineering professionalism.** - -**Transformation rules:** - -1. Remove all inflammatory language, insults, assumptions about the author -2. Keep all technical substance, file references, severity ratings and likely tag -3. Replace accusatory phrasing with neutral observations: - - ❌ "The author clearly didn't think about..." - - ✅ "This implementation may not account for..." -4. Preserve skepticism as healthy engineering caution: - - ❌ "This will definitely break in production" - - ✅ "This pattern has historically caused issues in production environments" -5. Add the suggested fixes. -6. Keep suggestions actionable and specific - -Output format after transformation: - -```markdown -## PR Review: #{PR_NUMBER} - -**Title:** {PR_TITLE} -**Author:** @{AUTHOR} -**Branch:** {HEAD} → {BASE} - ---- - -### Findings - -[TRANSFORMED FINDINGS HERE] - ---- - -### Summary - -**Critical:** {COUNT} | **Moderate:** {COUNT} | **Minor:** {COUNT} - -[BINARY_FILES_NOTE if any] - ---- - -_Review generated by Raven's Verdict. LLM-produced analysis - findings may be incorrect or lack context. Verify before acting._ -``` - -## Post Review - -### 3.1 Preview - -Display the complete transformed review to the user. - -``` -══════════════════════════════════════════════════════ -PREVIEW - This will be posted to PR #{PR_NUMBER} -══════════════════════════════════════════════════════ - -[FULL REVIEW CONTENT] - -══════════════════════════════════════════════════════ -``` - -### 3.2 Confirm - -Ask user for explicit confirmation: - -> **Ready to post this review to PR #{PR_NUMBER}?** -> -> **[y] Yes** - Post as comment -> **[n] No** - Abort, do not post -> **[e] Edit** - Let me modify before posting -> **[s] Save only** - Save locally, don't post - -### 3.3 Post or Save - -**Write review to a temp file, then post:** - -1. Write the review content to a temp file with a unique name (include PR number to avoid collisions) -2. Post using `gh pr comment {PR_NUMBER} [--repo {REPO}] --body-file {path}` -3. Delete the temp file after successful post - -Do NOT use heredocs or `echo` - Markdown code blocks will break shell parsing. Use your file writing tool instead. - -**If auth fails or post fails:** - -1. Display error prominently: - - ``` - ⚠️ FAILED TO POST REVIEW - Error: {ERROR_MESSAGE} - ``` - -2. Keep the temp file and tell the user where it is, so they can post manually with: - `gh pr comment {PR_NUMBER} [--repo {REPO}] --body-file {path}` - -**If save only (s):** - -Keep the temp file and inform user of location. - -## Notes - -- The "cynical asshole" phase is internal only - never posted -- Tone transform MUST happen before any external output -- When in doubt, ask the user - never assume -- If you're unsure about severity, err toward higher severity -- If you're unsure about confidence, be honest and use Medium or Low diff --git a/.claude/skills/bmad-os-root-cause-analysis/SKILL.md b/.claude/skills/bmad-os-root-cause-analysis/SKILL.md deleted file mode 100644 index 237f32b4a..000000000 --- a/.claude/skills/bmad-os-root-cause-analysis/SKILL.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -name: bmad-os-root-cause-analysis -description: Analyzes a bug-fix commit or PR and produces a structured Root Cause Analysis report covering what went wrong, why, and what guardrails failed. -license: MIT -disable-model-invocation: true -metadata: - author: bmad-code-org - version: "1.0.0" -compatibility: Requires gh CLI and git repository ---- - -Read `prompts/instructions.md` and execute. diff --git a/.claude/skills/bmad-os-root-cause-analysis/prompts/instructions.md b/.claude/skills/bmad-os-root-cause-analysis/prompts/instructions.md deleted file mode 100644 index e36cfca33..000000000 --- a/.claude/skills/bmad-os-root-cause-analysis/prompts/instructions.md +++ /dev/null @@ -1,74 +0,0 @@ -# Bug-Fix Root Cause Analysis - -Analyze a bug-fix commit or PR and produce a structured Root Cause Analysis report. - -## Principles - -- **Direct attribution.** This report names the individual who introduced the defect. Industry convention advocates blameless postmortems. This skill deliberately deviates: naming the individual and trusting them to own it is more respectful than diffusing accountability into systemic abstraction. Direct, factual, not accusatory. If authorship can't be determined confidently, say so. -- **Pyramid communication.** The executive summary must convey the full picture. A reader who stops after the first paragraph gets the gist. Everything else is supporting evidence. - -## Preflight - -Verify `gh auth status` and that you're in a git repository. Stop with a clear message if either fails. - -## Execution - -1. **Identify the fix.** Accept whatever the user provides — commit SHA, PR, issue, description. Resolve to the specific fix commit/PR using `gh` and `git`. If ambiguous, ask. Confirm the change is actually a bug fix before proceeding. -2. **Gather evidence.** Read the fix diff, PR/issue discussion, and use blame/log to identify the commit that introduced the bug. Collect timeline data. -3. **Analyze.** Apply 5 Whys. Classify the root cause. Identify contributing factors. -4. **Evaluate guardrails.** Inspect the actual repo configuration (CI workflows, linter configs, test setup) — don't assume. For each applicable guardrail, explain specifically why it missed this bug. -5. **Write the report** to `_bmad-output/rca-reports/rca-{YYYY-MM-DD}-{slug}.md`. Present the executive summary in chat. - -## Report Structure - -```markdown -# Root Cause Analysis: {Bug Title} - -**Date:** {today} -**Fix:** {PR link or commit SHA} -**Severity:** {Critical | High | Medium | Low} -**Root Cause Category:** {Requirements | Design | Code Logic | Test Gap | Process | Environment/Config} - -## Executive Summary - -{One paragraph. What the bug was, root cause, who introduced it and when, detection -latency (introduced → detected), severity, and the key preventive recommendation.} - -## What Was the Problem? - -## When Did It Happen? - -| Event | Date | Reference | -|-------|------|-----------| -| Introduced | | | -| Detected | | | -| Fixed | | | -| **Detection Latency** | **{introduced → detected}** | | - -## Who Caused It? - -{Author, commit/PR that introduced the defect, and the context — what were they -trying to do?} - -## How Did It Happen? - -## Why Did It Happen? - -{5 Whys analysis. Root cause category. Contributing factors.} - -## Failed Guardrails Analysis - -| Guardrail | In Place? | Why It Failed | -|-----------|-----------|---------------| -| | | | - -**Most Critical Failure:** {Which one mattered most and why.} - -## Resolution - -## Corrective & Preventive Actions - -| # | Action | Type | Priority | -|---|--------|------|----------| -| | | {Prevent/Detect/Mitigate} | | -``` diff --git a/.coderabbit.yaml b/.coderabbit.yaml deleted file mode 100644 index 9b7f85774..000000000 --- a/.coderabbit.yaml +++ /dev/null @@ -1,85 +0,0 @@ -# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json - -language: "en-US" -early_access: true -reviews: - profile: chill - high_level_summary: false # don't post summary until explicitly invoked - request_changes_workflow: false - review_status: false - commit_status: false - walkthrough: false - poem: false - auto_review: - enabled: true - drafts: false # Don't review drafts automatically - auto_incremental_review: false # always review the whole PR, not just new commits - base_branches: - - main - path_filters: - # --- Shared baseline: tool configs --- - - "!.coderabbit.yaml" - - "!.augment/**" - - "!eslint.config.mjs" - # --- Shared baseline: build output --- - - "!dist/**" - - "!build/**" - - "!coverage/**" - # --- Shared baseline: vendored/generated --- - - "!**/node_modules/**" - - "!**/*.min.js" - - "!**/*.generated.*" - - "!**/*.bundle.md" - # --- Shared baseline: package metadata --- - - "!package-lock.json" - # --- Shared baseline: binary/media --- - - "!*.png" - - "!*.jpg" - - "!*.svg" - # --- Shared baseline: test fixtures --- - - "!test/fixtures/**" - - "!test/template-test-generator/**" - - "!tools/template-test-generator/test-scenarios/**" - # --- Shared baseline: non-project dirs --- - - "!_bmad*/**" - - "!website/**" - - "!z*/**" - - "!sample-project/**" - - "!test-project-install/**" - # --- Shared baseline: AI assistant dirs --- - - "!.claude/**" - - "!.codex/**" - - "!.agent/**" - - "!.agentvibes/**" - - "!.kiro/**" - - "!.roo/**" - - "!.github/chatmodes/**" - # --- Shared baseline: build temp --- - - "!.bundler-temp/**" - # --- Shared baseline: generated reports --- - - "!**/validation-report-*.md" - - "!CHANGELOG.md" - path_instructions: - - path: "**/*" - instructions: | - You are a cynical, jaded reviewer with zero patience for sloppy work. - This PR was submitted by a clueless weasel and you expect to find problems. - Be skeptical of everything. - Look for what's missing, not just what's wrong. - Use a precise, professional tone — no profanity or personal attacks. - - Review with extreme skepticism — assume problems exist. - Find at least 10 issues to fix or improve. - - Do NOT: - - Comment on formatting, linting, or style - - Give "looks good" passes - - Anchor on any specific ruleset — reason freely - - If you find zero issues, re-analyze — this is suspicious. -chat: - auto_reply: true # Response to mentions in comments, a la @coderabbit review -issue_enrichment: - auto_enrich: - enabled: false # don't auto-comment on issues - diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md deleted file mode 100644 index 843ec9ee8..000000000 --- a/.github/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,128 +0,0 @@ -# Contributor Covenant Code of Conduct - -## Our Pledge - -We as members, contributors, and leaders pledge to make participation in our -community a harassment-free experience for everyone, regardless of age, body -size, visible or invisible disability, ethnicity, sex characteristics, gender -identity and expression, level of experience, education, socio-economic status, -nationality, personal appearance, race, religion, or sexual identity -and orientation. - -We pledge to act and interact in ways that contribute to an open, welcoming, -diverse, inclusive, and healthy community. - -## Our Standards - -Examples of behavior that contributes to a positive environment for our -community include: - -* Demonstrating empathy and kindness toward other people -* Being respectful of differing opinions, viewpoints, and experiences -* Giving and gracefully accepting constructive feedback -* Accepting responsibility and apologizing to those affected by our mistakes, - and learning from the experience -* Focusing on what is best not just for us as individuals, but for the - overall community - -Examples of unacceptable behavior include: - -* The use of sexualized language or imagery, and sexual attention or - advances of any kind -* Trolling, insulting or derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others' private information, such as a physical or email - address, without their explicit permission -* Other conduct which could reasonably be considered inappropriate in a - professional setting - -## Enforcement Responsibilities - -Community leaders are responsible for clarifying and enforcing our standards of -acceptable behavior and will take appropriate and fair corrective action in -response to any behavior that they deem inappropriate, threatening, offensive, -or harmful. - -Community leaders have the right and responsibility to remove, edit, or reject -comments, commits, code, wiki edits, issues, and other contributions that are -not aligned to this Code of Conduct, and will communicate reasons for moderation -decisions when appropriate. - -## Scope - -This Code of Conduct applies within all community spaces, and also applies when -an individual is officially representing the community in public spaces. -Examples of representing our community include using an official e-mail address, -posting via an official social media account, or acting as an appointed -representative at an online or offline event. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported to the community leaders responsible for enforcement at -the official BMAD Discord server () - DM a moderator or flag a post. -All complaints will be reviewed and investigated promptly and fairly. - -All community leaders are obligated to respect the privacy and security of the -reporter of any incident. - -## Enforcement Guidelines - -Community leaders will follow these Community Impact Guidelines in determining -the consequences for any action they deem in violation of this Code of Conduct: - -### 1. Correction - -**Community Impact**: Use of inappropriate language or other behavior deemed -unprofessional or unwelcome in the community. - -**Consequence**: A private, written warning from community leaders, providing -clarity around the nature of the violation and an explanation of why the -behavior was inappropriate. A public apology may be requested. - -### 2. Warning - -**Community Impact**: A violation through a single incident or series -of actions. - -**Consequence**: A warning with consequences for continued behavior. No -interaction with the people involved, including unsolicited interaction with -those enforcing the Code of Conduct, for a specified period of time. This -includes avoiding interactions in community spaces as well as external channels -like social media. Violating these terms may lead to a temporary or -permanent ban. - -### 3. Temporary Ban - -**Community Impact**: A serious violation of community standards, including -sustained inappropriate behavior. - -**Consequence**: A temporary ban from any sort of interaction or public -communication with the community for a specified period of time. No public or -private interaction with the people involved, including unsolicited interaction -with those enforcing the Code of Conduct, is allowed during this period. -Violating these terms may lead to a permanent ban. - -### 4. Permanent Ban - -**Community Impact**: Demonstrating a pattern of violation of community -standards, including sustained inappropriate behavior, harassment of an -individual, or aggression toward or disparagement of classes of individuals. - -**Consequence**: A permanent ban from any sort of public interaction within -the community. - -## Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], -version 2.0, available at -. - -Community Impact Guidelines were inspired by [Mozilla's code of conduct -enforcement ladder](https://github.com/mozilla/diversity). - -[homepage]: https://www.contributor-covenant.org - -For answers to common questions about this code of conduct, see the FAQ at -. Translations are available at -. diff --git a/.github/FUNDING.yaml b/.github/FUNDING.yaml deleted file mode 100644 index 089d6f4f1..000000000 --- a/.github/FUNDING.yaml +++ /dev/null @@ -1,15 +0,0 @@ -# These are supported funding model platforms - -github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2] -patreon: # Replace with a single Patreon username -open_collective: # Replace with a single Open Collective username -ko_fi: # Replace with a single Ko-fi username -tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel -community_bridge: # Replace with a single Community Bridge project_name e.g., cloud-foundry -liberapay: # Replace with a single Liberapay username -issuehunt: # Replace with a single IssueHunt username -lfx_crowdfunding: # Replace with a single LFX Crowdfunding project_name e.g., cloud-foundry -polar: # Replace with a single Polar username -buy_me_a_coffee: bmad -thanks_dev: # Replace with a single thanks.dev username -custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2'] diff --git a/.github/ISSUE_TEMPLATE/bug-report.yaml b/.github/ISSUE_TEMPLATE/bug-report.yaml deleted file mode 100644 index 6c5507d96..000000000 --- a/.github/ISSUE_TEMPLATE/bug-report.yaml +++ /dev/null @@ -1,124 +0,0 @@ -name: Bug Report -description: File a bug report to help us improve BMad Method -title: "[BUG] " -labels: bug -assignees: [] -body: - - type: markdown - attributes: - value: | - Thanks for filing a bug report! Please fill out the information below to help us reproduce and fix the issue. - - - type: textarea - id: description - attributes: - label: Description - description: Clear and concise description of what the bug is - placeholder: e.g., When I run /dev-story, it crashes on step 3 - validations: - required: true - - - type: textarea - id: steps - attributes: - label: Steps to reproduce - description: Step-by-step instructions to reproduce the behavior - placeholder: | - 1. Run 'npx bmad-method install' - 2. Select option X - 3. Run workflow Y - 4. See error - validations: - required: true - - - type: textarea - id: expected - attributes: - label: Expected behavior - description: What you expected to happen - placeholder: The workflow should complete successfully - validations: - required: true - - - type: textarea - id: actual - attributes: - label: Actual behavior - description: What actually happened - placeholder: The workflow crashed with error "..." - validations: - required: true - - - type: textarea - id: screenshots - attributes: - label: Screenshots - description: Add screenshots if applicable (paste images directly) - placeholder: Paste any relevant screenshots here - - - type: dropdown - id: module - attributes: - label: Which module is this for? - description: Select the BMad module this issue relates to - options: - - BMad Method (BMM) - Core Framework - - BMad Builder (BMB) - Agent Builder Tool - - Test Architect (TEA) - Test Strategy Module - - Game Dev Studio (BMGD) - Game Development Module - - Creative Intelligence Suite (CIS) - Innovation Module - - Not sure / Other - validations: - required: true - - - type: input - id: version - attributes: - label: BMad Version - description: "Check with: npx bmad-method --version or check package.json" - placeholder: e.g., 6.0.0-Beta.4 - validations: - required: true - - - type: dropdown - id: ide - attributes: - label: Which AI IDE are you using? - options: - - Claude Code - - Cursor - - Windsurf - - Copilot CLI / GitHub Copilot - - Kilo Code - - Other - validations: - required: true - - - type: dropdown - id: platform - attributes: - label: Operating System - options: - - macOS - - Windows - - Linux - - Other - validations: - required: true - - - type: textarea - id: logs - attributes: - label: Relevant log output - description: Copy and paste any relevant log output - render: shell - - - type: checkboxes - id: terms - attributes: - label: Confirm - options: - - label: I've searched for existing issues - required: true - - label: I'm using the latest version - required: false diff --git a/.github/ISSUE_TEMPLATE/config.yaml b/.github/ISSUE_TEMPLATE/config.yaml deleted file mode 100644 index 7e980f119..000000000 --- a/.github/ISSUE_TEMPLATE/config.yaml +++ /dev/null @@ -1,8 +0,0 @@ -blank_issues_enabled: false -contact_links: - - name: 📚 Documentation - url: https://docs.bmad-method.org - about: Check the docs first — tutorials, guides, and reference - - name: 💬 Discord Community - url: https://discord.gg/gk8jAdXWmj - about: Join for questions, discussion, and help before opening an issue diff --git a/.github/ISSUE_TEMPLATE/documentation.yaml b/.github/ISSUE_TEMPLATE/documentation.yaml deleted file mode 100644 index 6b132c48e..000000000 --- a/.github/ISSUE_TEMPLATE/documentation.yaml +++ /dev/null @@ -1,55 +0,0 @@ -name: Documentation -description: Report issues or suggest improvements to documentation -title: "[DOCS] " -labels: documentation -assignees: [] -body: - - type: markdown - attributes: - value: | - Help us improve the BMad Method documentation! - - - type: dropdown - id: doc-type - attributes: - label: What type of documentation issue is this? - options: - - Error or inaccuracy - - Missing information - - Unclear or confusing - - Outdated content - - Request for new documentation - - Typo or grammar - validations: - required: true - - - type: textarea - id: location - attributes: - label: Documentation location - description: Where is the documentation that needs improvement? - placeholder: e.g., https://docs.bmad-method.org/tutorials/getting-started/ or "In the README" - validations: - required: true - - - type: textarea - id: issue - attributes: - label: What's the issue? - description: Describe the documentation issue in detail - placeholder: e.g., Step 3 says to run command X but it should be command Y - validations: - required: true - - - type: textarea - id: suggestion - attributes: - label: Suggested improvement - description: How would you like to see this improved? - placeholder: e.g., Change the command to X and add an example - - - type: input - id: version - attributes: - label: BMad Version (if applicable) - placeholder: e.g., 6.0.0-Beta.4 diff --git a/.github/ISSUE_TEMPLATE/feature-request.md b/.github/ISSUE_TEMPLATE/feature-request.md deleted file mode 100644 index 9750c2214..000000000 --- a/.github/ISSUE_TEMPLATE/feature-request.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -name: Feature Request -about: Suggest an idea or new feature -title: '' -labels: '' -assignees: '' ---- - -**Describe your idea** -A clear and concise description of what you'd like to see added or changed. - -**Why is this needed?** -Explain the problem this solves or the benefit it brings to the BMad community. - -**How should it work?** -Describe your proposed solution. If you have ideas on implementation, share them here. - -**PR** -If you'd like to contribute, please indicate you're working on this or link to your PR. Please review [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome! - -**Additional context** -Add any other context, screenshots, or links that help explain your idea. diff --git a/.github/ISSUE_TEMPLATE/issue.md b/.github/ISSUE_TEMPLATE/issue.md deleted file mode 100644 index aa0727725..000000000 --- a/.github/ISSUE_TEMPLATE/issue.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -name: Issue -about: Report a problem or something that's not working -title: '' -labels: '' -assignees: '' ---- - -**Describe the bug** -A clear and concise description of what the bug is. - -**Steps to reproduce** -1. What were you doing when the bug occurred? -2. What steps can recreate the issue? - -**Expected behavior** -A clear and concise description of what you expected to happen. - -**Environment (if relevant)** -- Model(s) used: -- Agentic IDE used: -- BMad version: -- Project language: - -**Screenshots or links** -If applicable, add screenshots or links to help explain the problem. - -**PR** -If you'd like to contribute a fix, please indicate you're working on it or link to your PR. See [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome! - -**Additional context** -Add any other context about the problem here. The more information you provide, the easier it is to help. diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index f7224e188..000000000 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,13 +0,0 @@ -## What - - -## Why - - - -## How - -- - -## Testing - diff --git a/.github/scripts/discord-helpers.sh b/.github/scripts/discord-helpers.sh deleted file mode 100644 index dd323d302..000000000 --- a/.github/scripts/discord-helpers.sh +++ /dev/null @@ -1,34 +0,0 @@ -#!/bin/bash -# Discord notification helper functions - -# Escape markdown special chars and @mentions for safe Discord display -# Skips content inside wrappers to preserve URLs intact -esc() { - awk '{ - result = ""; in_url = 0; n = length($0) - for (i = 1; i <= n; i++) { - c = substr($0, i, 1) - if (c == "<" && substr($0, i, 8) ~ /^") in_url = 0 } - else if (c == "@") result = result "@ " - else if (index("[]\\*_()~`", c) > 0) result = result "\\" c - else result = result c - } - print result - }' -} - -# Truncate to $1 chars (or 80 if wall-of-text with <3 spaces) -trunc() { - local max=$1 - local txt=$(tr '\n\r' ' ' | cut -c1-"$max") - local spaces=$(printf '%s' "$txt" | tr -cd ' ' | wc -c) - [ "$spaces" -lt 3 ] && [ ${#txt} -gt 80 ] && txt=$(printf '%s' "$txt" | cut -c1-80) - printf '%s' "$txt" -} - -# Remove incomplete URL at end of truncated text (incomplete URLs are useless) -strip_trailing_url() { sed -E 's~ to suppress Discord embeds (keeps links clickable) -wrap_urls() { sed -E 's~https?://[^[:space:]<>]+~<&>~g'; } diff --git a/.github/workflows/coderabbit-review.yaml b/.github/workflows/coderabbit-review.yaml deleted file mode 100644 index fb284d664..000000000 --- a/.github/workflows/coderabbit-review.yaml +++ /dev/null @@ -1,22 +0,0 @@ -name: Trigger CodeRabbit on Ready for Review - -on: - pull_request_target: - types: [ready_for_review] - -jobs: - trigger-review: - runs-on: ubuntu-latest - permissions: - pull-requests: write - steps: - - name: Request CodeRabbit review - uses: actions/github-script@v7 - with: - script: | - await github.rest.issues.createComment({ - owner: context.repo.owner, - repo: context.repo.repo, - issue_number: context.payload.pull_request.number, - body: '@coderabbitai review' - }); diff --git a/.github/workflows/discord.yaml b/.github/workflows/discord.yaml deleted file mode 100644 index 6f90abebd..000000000 --- a/.github/workflows/discord.yaml +++ /dev/null @@ -1,90 +0,0 @@ -name: Discord Notification - -on: - pull_request: - types: [opened, closed] - issues: - types: [opened] - -env: - MAX_TITLE: 100 - MAX_BODY: 250 - -jobs: - pull_request: - if: github.event_name == 'pull_request' - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v4 - with: - ref: ${{ github.event.repository.default_branch }} - sparse-checkout: .github/scripts - sparse-checkout-cone-mode: false - - name: Notify Discord - env: - WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }} - ACTION: ${{ github.event.action }} - MERGED: ${{ github.event.pull_request.merged }} - PR_NUM: ${{ github.event.pull_request.number }} - PR_URL: ${{ github.event.pull_request.html_url }} - PR_TITLE: ${{ github.event.pull_request.title }} - PR_USER: ${{ github.event.pull_request.user.login }} - PR_BODY: ${{ github.event.pull_request.body }} - run: | - set -o pipefail - source .github/scripts/discord-helpers.sh - [ -z "$WEBHOOK" ] && exit 0 - - if [ "$ACTION" = "opened" ]; then ICON="🔀"; LABEL="New PR" - elif [ "$ACTION" = "closed" ] && [ "$MERGED" = "true" ]; then ICON="🎉"; LABEL="Merged" - elif [ "$ACTION" = "closed" ]; then ICON="❌"; LABEL="Closed"; fi - - TITLE=$(printf '%s' "$PR_TITLE" | trunc $MAX_TITLE | esc) - [ ${#PR_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..." - BODY=$(printf '%s' "$PR_BODY" | trunc $MAX_BODY) - if [ -n "$PR_BODY" ] && [ ${#PR_BODY} -gt $MAX_BODY ]; then - BODY=$(printf '%s' "$BODY" | strip_trailing_url) - fi - BODY=$(printf '%s' "$BODY" | wrap_urls | esc) - [ -n "$PR_BODY" ] && [ ${#PR_BODY} -gt $MAX_BODY ] && BODY="${BODY}..." - [ -n "$BODY" ] && BODY=" · $BODY" - USER=$(printf '%s' "$PR_USER" | esc) - - MSG="$ICON **[$LABEL #$PR_NUM: $TITLE](<$PR_URL>)**"$'\n'"by @$USER$BODY" - jq -n --arg content "$MSG" '{content: $content}' | curl -sf --retry 2 -X POST "$WEBHOOK" -H "Content-Type: application/json" -d @- - - issues: - if: github.event_name == 'issues' - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v4 - with: - ref: ${{ github.event.repository.default_branch }} - sparse-checkout: .github/scripts - sparse-checkout-cone-mode: false - - name: Notify Discord - env: - WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }} - ISSUE_NUM: ${{ github.event.issue.number }} - ISSUE_URL: ${{ github.event.issue.html_url }} - ISSUE_TITLE: ${{ github.event.issue.title }} - ISSUE_USER: ${{ github.event.issue.user.login }} - ISSUE_BODY: ${{ github.event.issue.body }} - run: | - set -o pipefail - source .github/scripts/discord-helpers.sh - [ -z "$WEBHOOK" ] && exit 0 - - TITLE=$(printf '%s' "$ISSUE_TITLE" | trunc $MAX_TITLE | esc) - [ ${#ISSUE_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..." - BODY=$(printf '%s' "$ISSUE_BODY" | trunc $MAX_BODY) - if [ -n "$ISSUE_BODY" ] && [ ${#ISSUE_BODY} -gt $MAX_BODY ]; then - BODY=$(printf '%s' "$BODY" | strip_trailing_url) - fi - BODY=$(printf '%s' "$BODY" | wrap_urls | esc) - [ -n "$ISSUE_BODY" ] && [ ${#ISSUE_BODY} -gt $MAX_BODY ] && BODY="${BODY}..." - [ -n "$BODY" ] && BODY=" · $BODY" - USER=$(printf '%s' "$ISSUE_USER" | esc) - - MSG="🐛 **[Issue #$ISSUE_NUM: $TITLE](<$ISSUE_URL>)**"$'\n'"by @$USER$BODY" - jq -n --arg content "$MSG" '{content: $content}' | curl -sf --retry 2 -X POST "$WEBHOOK" -H "Content-Type: application/json" -d @- diff --git a/.github/workflows/docs.yaml b/.github/workflows/docs.yaml deleted file mode 100644 index fa136be49..000000000 --- a/.github/workflows/docs.yaml +++ /dev/null @@ -1,64 +0,0 @@ -name: Deploy Documentation - -on: - push: - branches: - - main - paths: - - "docs/**" - - "website/**" - - "tools/build-docs.mjs" - - ".github/workflows/docs.yaml" - workflow_dispatch: - -permissions: - contents: read - pages: write - id-token: write - -concurrency: - group: "pages" - # No big win in setting this to true — risk of cancelling a deploy mid-flight. - cancel-in-progress: false - -jobs: - build: - runs-on: ubuntu-latest - steps: - - name: Checkout repository - uses: actions/checkout@v4 - with: - # Full history needed for Starlight's lastUpdated timestamps (git log) - fetch-depth: 0 - - - name: Setup Node.js - uses: actions/setup-node@v4 - with: - node-version-file: ".nvmrc" - cache: "npm" - - - name: Install dependencies - run: npm ci - - - name: Build documentation - env: - # Override site URL from GitHub repo variable if set - # Otherwise, astro.config.mjs will compute from GITHUB_REPOSITORY - SITE_URL: ${{ vars.SITE_URL }} - run: npm run docs:build - - - name: Upload artifact - uses: actions/upload-pages-artifact@v3 - with: - path: build/site - - deploy: - environment: - name: github-pages - url: ${{ steps.deployment.outputs.page_url }} - runs-on: ubuntu-latest - needs: build - steps: - - name: Deploy to GitHub Pages - id: deployment - uses: actions/deploy-pages@v4 diff --git a/.github/workflows/quality.yaml b/.github/workflows/quality.yaml deleted file mode 100644 index 78023e466..000000000 --- a/.github/workflows/quality.yaml +++ /dev/null @@ -1,116 +0,0 @@ -name: Quality & Validation - -# Runs comprehensive quality checks on all PRs: -# - Prettier (formatting) -# - ESLint (linting) -# - markdownlint (markdown quality) -# - Schema validation (YAML structure) -# - Agent schema tests (fixture-based validation) -# - Installation component tests (compilation) -# - Bundle validation (web bundle integrity) - -"on": - pull_request: - branches: ["**"] - workflow_dispatch: - -jobs: - prettier: - runs-on: ubuntu-latest - steps: - - name: Checkout - uses: actions/checkout@v4 - - - name: Setup Node - uses: actions/setup-node@v4 - with: - node-version-file: ".nvmrc" - cache: "npm" - - - name: Install dependencies - run: npm ci - - - name: Prettier format check - run: npm run format:check - - eslint: - runs-on: ubuntu-latest - steps: - - name: Checkout - uses: actions/checkout@v4 - - - name: Setup Node - uses: actions/setup-node@v4 - with: - node-version-file: ".nvmrc" - cache: "npm" - - - name: Install dependencies - run: npm ci - - - name: ESLint - run: npm run lint - - markdownlint: - runs-on: ubuntu-latest - steps: - - name: Checkout - uses: actions/checkout@v4 - - - name: Setup Node - uses: actions/setup-node@v4 - with: - node-version-file: ".nvmrc" - cache: "npm" - - - name: Install dependencies - run: npm ci - - - name: markdownlint - run: npm run lint:md - - docs: - runs-on: ubuntu-latest - steps: - - name: Checkout - uses: actions/checkout@v4 - - - name: Setup Node - uses: actions/setup-node@v4 - with: - node-version-file: ".nvmrc" - cache: "npm" - - - name: Install dependencies - run: npm ci - - - name: Build documentation - # Note: build-docs.mjs runs link validation internally before building - run: npm run docs:build - - validate: - runs-on: ubuntu-latest - steps: - - name: Checkout - uses: actions/checkout@v4 - - - name: Setup Node - uses: actions/setup-node@v4 - with: - node-version-file: ".nvmrc" - cache: "npm" - - - name: Install dependencies - run: npm ci - - - name: Validate YAML schemas - run: npm run validate:schemas - - - name: Run agent schema validation tests - run: npm run test:schemas - - - name: Test agent compilation components - run: npm run test:install - - - name: Validate file references - run: npm run validate:refs diff --git a/.gitignore b/.gitignore deleted file mode 100644 index a1229c93d..000000000 --- a/.gitignore +++ /dev/null @@ -1,73 +0,0 @@ -# Dependencies -**/node_modules/ -pnpm-lock.yaml -bun.lock -deno.lock -pnpm-workspace.yaml -package-lock.json - -test-output/* -coverage/ - -# Logs -logs/ -*.log -npm-debug.log* - -# Build output -build/*.txt - -# Environment variables -.env - -# System files -.DS_Store -Thumbs.db - -# Development tools and configs -.prettierrc - -# AI assistant files -CLAUDE.md -.ai/* -cursor -.gemini -.mcp.json -CLAUDE.local.md -.serena/ -.claude/settings.local.json -.junie/ -.agents/ - -z*/ - -_bmad -_bmad-output -.clinerules -# .augment/ is gitignored except tracked config files — add exceptions explicitly -.augment/* -!.augment/code_review_guidelines.yaml -.codebuddy -.crush -.cursor -.iflow -.opencode -.qwen -.rovodev -.kilocodemodes -.claude/commands -.codex -.github/chatmodes -.github/agents -.agent -.agentvibes -.kiro -.roo -.trae -.windsurf - - -# Astro / Documentation Build -website/.astro/ -website/dist/ -build/ diff --git a/.husky/pre-commit b/.husky/pre-commit deleted file mode 100755 index ae9e0c44f..000000000 --- a/.husky/pre-commit +++ /dev/null @@ -1,20 +0,0 @@ -#!/usr/bin/env sh - -# Auto-fix changed files and stage them -npx --no-install lint-staged - -# Validate everything -npm test - -# Validate docs links only when docs change -if command -v rg >/dev/null 2>&1; then - if git diff --cached --name-only | rg -q '^docs/'; then - npm run docs:validate-links - npm run docs:build - fi -else - if git diff --cached --name-only | grep -Eq '^docs/'; then - npm run docs:validate-links - npm run docs:build - fi -fi diff --git a/.markdownlint-cli2.yaml b/.markdownlint-cli2.yaml deleted file mode 100644 index c22ff4c5c..000000000 --- a/.markdownlint-cli2.yaml +++ /dev/null @@ -1,41 +0,0 @@ -# markdownlint-cli2 configuration -# https://github.com/DavidAnson/markdownlint-cli2 - -ignores: - - "**/node_modules/**" - - test/fixtures/** - - CODE_OF_CONDUCT.md - - _bmad/** - - _bmad*/** - - .agent/** - - .claude/** - - .roo/** - - .codex/** - - .kiro/** - - sample-project/** - - test-project-install/** - - z*/** - -# Rule configuration -config: - # Disable all rules by default - default: false - - # Heading levels should increment by one (h1 -> h2 -> h3, not h1 -> h3) - MD001: true - - # Duplicate sibling headings (same heading text at same level under same parent) - MD024: - siblings_only: true - - # Trailing commas in headings (likely typos) - MD026: - punctuation: "," - - # Bare URLs - may not render as links in all parsers - # Should use or [text](url) format - MD034: true - - # Spaces inside emphasis markers - breaks rendering - # e.g., "* text *" won't render as emphasis - MD037: true diff --git a/.npmrc b/.npmrc deleted file mode 100644 index 052d46792..000000000 --- a/.npmrc +++ /dev/null @@ -1,5 +0,0 @@ -# Prevent peer dependency warnings during installation -legacy-peer-deps=true - -# Improve install performance -prefer-offline=true diff --git a/.nvmrc b/.nvmrc deleted file mode 100644 index 8fdd954df..000000000 --- a/.nvmrc +++ /dev/null @@ -1 +0,0 @@ -22 \ No newline at end of file diff --git a/.prettierignore b/.prettierignore deleted file mode 100644 index 013380044..000000000 --- a/.prettierignore +++ /dev/null @@ -1,12 +0,0 @@ -# Test fixtures with intentionally broken/malformed files -test/fixtures/** - -# Contributor Covenant (external standard) -CODE_OF_CONDUCT.md - -# BMAD runtime folders (user-specific, not in repo) -_bmad/ -_bmad*/ - -# IDE integration folders (user-specific, not in repo) -.junie/ diff --git a/.vscode/settings.json b/.vscode/settings.json deleted file mode 100644 index f28c7f5d0..000000000 --- a/.vscode/settings.json +++ /dev/null @@ -1,96 +0,0 @@ -{ - "chat.agent.enabled": true, - "chat.agent.maxRequests": 15, - "github.copilot.chat.agent.runTasks": true, - "chat.mcp.discovery.enabled": { - "claude-desktop": true, - "windsurf": true, - "cursor-global": true, - "cursor-workspace": true - }, - "github.copilot.chat.agent.autoFix": true, - "chat.tools.autoApprove": false, - "cSpell.words": [ - "Agentic", - "atlasing", - "Biostatistician", - "bmad", - "Cordova", - "customresourcedefinitions", - "dashboarded", - "Decisioning", - "eksctl", - "elicitations", - "Excalidraw", - "filecomplete", - "fintech", - "fluxcd", - "frontmatter", - "gamedev", - "gitops", - "implementability", - "Improv", - "inclusivity", - "ingressgateway", - "istioctl", - "metroidvania", - "NACLs", - "nodegroup", - "platformconfigs", - "Playfocus", - "playtesting", - "pointerdown", - "pointerup", - "Polyrepo", - "replayability", - "roguelike", - "roomodes", - "Runbook", - "runbooks", - "Shardable", - "Softlock", - "solutioning", - "speedrunner", - "substep", - "tekton", - "tilemap", - "tileset", - "tmpl", - "Trae", - "Unsharded", - "VNET" - ], - "json.schemas": [ - { - "fileMatch": ["package.json"], - "url": "https://json.schemastore.org/package.json" - }, - { - "fileMatch": [".vscode/settings.json"], - "url": "vscode://schemas/settings/folder" - } - ], - "editor.formatOnSave": true, - "editor.defaultFormatter": "esbenp.prettier-vscode", - "[javascript]": { - "editor.defaultFormatter": "vscode.typescript-language-features" - }, - "[json]": { - "editor.defaultFormatter": "vscode.json-language-features" - }, - "[yaml]": { - "editor.defaultFormatter": "esbenp.prettier-vscode" - }, - "[markdown]": { - "editor.defaultFormatter": "yzhang.markdown-all-in-one" - }, - "yaml.format.enable": false, - "editor.codeActionsOnSave": { - "source.fixAll.eslint": "explicit" - }, - "editor.rulers": [140], - "[xml]": { - "editor.defaultFormatter": "redhat.vscode-xml" - }, - "xml.format.maxLineWidth": 140 -} diff --git a/CHANGELOG.md b/CHANGELOG.md deleted file mode 100644 index 03e191434..000000000 --- a/CHANGELOG.md +++ /dev/null @@ -1,1785 +0,0 @@ -# Changelog - -## [6.0.4] - -### 🎁 Features - -* Add edge case hunter review task - new reusable review task that exhaustively traces branching paths and boundary conditions in code, reporting only unhandled gaps. Method-driven analysis complementary to adversarial review (#1790) - -### 🐛 Bug Fixes - -* Fix brainstorming to not overwrite previous sessions; now prompts to continue existing brainstorming or start a new one when older brainstorming sessions are found -* Fix installer templates - replace legacy `@` path prefixes with explicit `{project-root}` syntax for consistency (#1769) -* Fix edge case hunter - remove zero-findings halt condition that was pressuring the LLM to hallucinate findings when none legitimately exist (#1797) -* Fix broken docs domain references in README and GitHub issue templates (#1777) - ---- - -## [6.0.3] - -### 🎁 Features - -* Add bmad-os-root-cause-analysis skill for analyzing bug-fix commits and producing structured root cause analysis reports with pyramid communication format (#1741) - -### 🐛 Bug Fixes - -* Fix installer to refuse installation when ancestor directory has BMAD commands, preventing duplicate command autocompletion in nested directories (#1735) -* Fix OpenCode integration by replacing unsupported `name` frontmatter with `mode: all` and update directory names to plural form (#1764) -* Fix CSV manifest pipeline double-escaping of quotes that was corrupting output files; switch Gemini templates to single quotes (#1746) -* Fix workflow descriptions to use proper quotes so they format better in skill conversion and don't break yaml front matter -* Fix workflow help task chaining by removing ambiguous "with-argument" clause that caused LLMs to misinterpret help.md as skill calls (#1740) - -### ♻️ Refactoring - -* Standardize all workflow descriptions to use proper quotes to prevent breaking command or skill front matter during skill conversion - -### 📚 Documentation - -* Fix broken TEA hyperlinks to point to new repository URL (#1772) -* Rebrand BMAD acronym to "Build More Architect Dreams" across documentation (#1765) - ---- - -## [6.0.2] - -### 🎁 Features - -* Add CodeBuddy platform support with installer configuration (#1483) -* Add LLM audit prompt for file reference conventions - new audit tool using parallel subagents (#1720) -* Migrate Codex installer from `.codex/prompts` to `.agents/skills` format to align with Codex CLI changes (#1729) -* Convert review-pr and audit-file-refs tools to proper bmad-os skills with slash commands `/bmad-os-review-pr` and `/bmad-os-audit-file-refs` (#1732) - -### 🐛 Bug Fixes - -* Fix 24 broken step references in create-architecture workflow after directory rename (#1734) -* Fix step file path references in check-implementation-readiness workflow (#1709, #1716) -* Fix 3 broken file references and enable strict file reference validation in CI (#1717) -* Fix Rovo Dev integration with custom installer that generates prompts.yml manifest (#1701) -* Fix 104 relative step file references to use standardized `{project-root}/_bmad/` paths across 68 files (#1722) -* Fix code fence imbalance in step-03-starter.md that caused rendering issues (#1724) -* Remove Windsurf from recommended/preferred IDEs list (#1727) -* Fix default Codex install location from global to project for better defaults (#1698) -* Add npx cache workaround to Quick Start for stale beta versions (#1685) -* Add language instructions to replace placeholder text in Research overview (#1703) -* Ignore `.junie/` IDE integration folder in git and prettier configs (#1719) - -### ♻️ Refactoring - -* Update open source tool skills structure for future plugin migration -* Standardize all workflow descriptions for skill generation with concise format and explicit trigger phrases -* Remove `disable-model-invocation` flag from all IDE installer templates to enable workflow skill calls - -### 📚 Documentation - -* Elevate `bmad-help` as primary on-ramp across all documentation -* Update workflow names with `bmad-bmm-` prefix and standardize table formatting -* Clarify phase routing and catalog path in help task - ---- - -## [6.0.0] - -V6 Stable Release! The End of Beta! - -### 🎁 Features - -* Add PRD workflow steps 2b (vision/differentiators) and 2c (executive summary) for more complete product requirements documentation -* Add new `bmad uninstall` command with interactive and non-interactive modes for selective component removal -* Add dedicated GitHub Copilot installer that generates enriched `.agent.md`, `.prompt.md` files and project configuration -* Add TEA browser automation prerequisite prompts to guide Playwright CLI/MCP setup after configuration - -### 🐛 Bug Fixes - -* Fix version comparison to use semantic versioning, preventing incorrect downgrade recommendations to older beta versions -* Fix `--custom-content` flag to properly populate sources and selected files in module config -* Fix module configuration UX messaging to show accurate completion status and improve feedback timing -* Fix changelog URL in installer start message for proper GitHub resolution -* Remove incorrect `mode: primary` from OpenCode agent template and restore `name` field across all templates -* Auto-discover PRD files in validate-prd workflow to reduce manual path input -* Fix installer non-interactive mode hanging and improve IDE configuration handling during updates -* Fix workflow-level config.yaml copying for custom content modules - -### ♻️ Refactoring - -* Remove alias variables from Phase 4 workflows, use canonical `{implementation_artifacts}` and `{planning_artifacts}` -* Add missing `project_context` references to workflows for consistency - -### 📚 Documentation - -* Add post-install notes documentation for modules -* Improve project-context documentation and fix folder structure -* Add BMad Builder link to index for extenders - ---- - -## [6.0.0-Beta.8] - -**Release: February 8, 2026** - -### 🌟 Key Highlights - -1. **Non-Interactive Installation** — Full CI/CD support with 10 new CLI flags for automated deployments -2. **Complete @clack/prompts Migration** — Unified CLI experience with consolidated installer output -3. **CSV File Reference Validation** — Extended Layer 1 validator to catch broken workflow references in CSV files -4. **Kiro IDE Support** — Standardized config-driven installation, replacing custom installer - -### 🎁 Features - -* **Non-Interactive Installation** — Added `--directory`, `--modules`, `--tools`, `--custom-content`, `--user-name`, `--communication-language`, `--document-output-language`, `--output-folder`, and `-y/--yes` flags for CI/CD automation (#1520) -* **CSV File Reference Validation** — Extended validator to scan `.csv` files for broken workflow references, checking 501 references across 212 files (#1573) -* **Kiro IDE Support** — Replaced broken custom installer with config-driven templates using `#[[file:...]]` syntax and `inclusion: manual` frontmatter (#1589) -* **OpenCode Template Consolidation** — Combined split templates with `mode: primary` frontmatter for Tab-switching support, fixing agent discovery (#1556) -* **Modules Reference Page** — Added official external modules reference documentation (#1540) - -### 🐛 Bug Fixes - -* **Installer Streamlining** — Removed "None - Skip module installation" option, eliminated ~100 lines of dead code, and added ESM/.cjs support for module installers (#1590) -* **CodeRabbit Workflow** — Changed `pull_request` to `pull_request_target` to fix 403 errors and enable reviews on fork PRs (#1583) -* **Party Mode Return Protocol** — Added RETURN PROTOCOL to prevent lost-in-the-middle failures after Party Mode completes (#1569) -* **Spacebar Toggle** — Fixed SPACE key not working in autocomplete multiselect prompts for tool/IDE selection (#1557) -* **OpenCode Agent Routing** — Fixed agents installing to wrong directory by adding `targets` array for routing `.opencode/agent/` vs `.opencode/command/` (#1549) -* **Technical Research Workflow** — Fixed step-05 routing to step-06 and corrected `stepsCompleted` values (#1547) -* **Forbidden Variable Removal** — Removed `workflow_path` variable from 16 workflow step files (#1546) -* **Kilo Installer** — Fixed YAML formatting issues by trimming activation header and converting to yaml.parse/stringify (#1537) -* **bmad-help** — Now reads project-specific docs and respects `communication_language` setting (#1535) -* **Cache Errors** — Removed `--prefer-offline` npm flag to prevent stale cache errors during installation (#1531) - -### ♻️ Refactoring - -* **Complete @clack/prompts Migration** — Migrated 24 files from legacy libraries (ora, chalk, boxen, figlet, etc.), replaced ~100 console.log+chalk calls, consolidated installer output to single spinner, and removed 5 dependencies (#1586) -* **Downloads Page Removal** — Removed downloads page, bundle generation, and archiver dependency in favor of GitHub's native archives (#1577) -* **Workflow Verb Standardization** — Replaced "invoke/run" with "load and follow/load" in review workflow prompts (#1570) -* **Documentation Language** — Renamed "brownfield" to "established projects" and flattened directory structure for accessibility (#1539) - -### 📚 Documentation - -* **Comprehensive Site Review** — Fixed broken directory tree diagram, corrected grammar/capitalization, added SEO descriptions, and reordered how-to guides (#1578) -* **SEO Metadata** — Added description front matter to 9 documentation pages for search engine optimization (#1566) -* **PR Template** — Added pull request template for consistent PR descriptions (#1554) -* **Manual Release Cleanup** — Removed broken manual-release workflow and related scripts (#1576) - -### 🔧 Maintenance - -* **Dual-Mode AI Code Review** — Configured Augment Code (audit mode) and CodeRabbit (adversarial mode) for improved code quality (#1511) -* **Package-Lock Sync** — Cleaned up 471 lines of orphaned dependencies after archiver removal (#1580) - ---- - -## [6.0.0-Beta.7] - -**Release: February 4, 2026** - -### 🌟 Key Highlights - -1. **Direct Workflow Invocation** — Agent workflows can now be run directly via slash commands instead of only through agent orchestration -2. **Installer Workflow Support** — Installer now picks up `workflow-*.md` files, enabling multiple workflow files per directory - -### 🎁 Features - -* **Slash Command Workflow Access** — Research and PRD workflows now accessible via direct slash commands: `/domain-research`, `/market-research`, `/technical-research`, `/create-prd`, `/edit-prd`, `/validate-prd` (bd620e38, 731bee26) -* **Version Checking** — CLI now checks npm for newer versions and displays a warning banner when updates are available (d37ee7f2) - -### ♻️ Refactoring - -* **Workflow File Splitting** — Split monolithic `workflow.md` files into specific `workflow-*.md` files for individual workflow invocation (bd620e38) -* **Installer Multi-Workflow Support** — Installer manifest generator now supports `workflow-*.md` pattern, allowing multiple workflow files per directory (731bee26) -* **Internal Skill Renaming** — Renamed internal project skills to use `bmad-os-` prefix for consistent naming (5276d58b) - ---- - -## [6.0.0-Beta.6] - -**Release: February 4, 2026** - -### 🌟 Key Highlights - -1. **Cross-File Reference Validator**: Comprehensive tool to detect broken file references, preventing 59 known bugs (~25% of historical issues) -2. **New AutocompleteMultiselect Prompt**: Searchable multi-select with improved tool/IDE selection UX -3. **Critical Installer Fixes**: Windows CRLF parsing, Gemini CLI TOML support, file extension preservation -4. **Codebase Cleanup**: Removed dead Excalidraw/flattener artifacts (-3,798 lines) - -### 🎁 Features - -* **Cross-File Reference Validator** — Validates ~483 references across ~217 source files, detecting absolute path leaks and broken references (PR #1494) -* **AutocompleteMultiselect Prompt** — Upgraded `@clack/prompts` to v1.0.0 with custom searchable multiselect, Tab-to-fill-placeholder behavior, and improved tool/IDE selection UX (PR #1514) -* **OT Domains** — Added `process_control` and `building_automation` domains with high complexity ratings (PR #1510) -* **Documentation Reference Pages** — Added `docs/reference/agents.md`, `commands.md`, and `testing.md` (PR #1525) - -### 🐛 Bug Fixes - -* **Critical Installer Fixes** — Fixed CRLF line ending parsing on Windows, Gemini CLI TOML support, file extension preservation, Codex task generation, Windows path handling, and CSV parsing (PR #1492) -* **Double Tool Questioning** — Removed redundant tool questioning during installation (df176d42) -* **QA Agent Rename** — Renamed Quinn agent to `qa` for naming consistency (PR #1508) -* **Documentation Organization** — Fixed documentation ordering and links, hide BMGD pages from main LLM docs (PR #1525) - -### ♻️ Refactoring - -* **Excalidraw/Flattener Removal** — Removed dead artifacts no longer supported beyond beta: Excalidraw workflows, flattener tool, and 12+ diagram creation workflows (-3,798 lines) (f699a368) -* **Centralized Constants** — Centralized `BMAD_FOLDER_NAME` to reduce hardcoded strings (PR #1492) -* **Cross-Platform Paths** — Fixed path separator inconsistencies in agent IDs (PR #1492) - -### 📚 Documentation - -* **BMGD Diataxis Refactor** — Refactored BMGD documentation using Diataxis principles for better organization (PR #1502) -* **Generate Project Context** — Restored `generate-project-context` workflow for brownfield project analysis (PR #1491) - -### 🔧 Maintenance - -* **Dependency Updates** — Upgraded `@clack/prompts` from v0.11.0 to v1.0.0 and added `@clack/core` (PR #1514) -* **CI Integration** — Added `validate:refs` to CI quality workflow with warning annotations (PR #1494) - ---- - -## [6.0.0-Beta.5] - -### 🎁 Features - -* **Add generate-project-context workflow** — New 3-step workflow for project context generation, integrated with quick-flow-solo-dev agent -* **Shard market research customer analysis** — Refactor monolithic customer insights into 4-step detailed customer behavior analysis workflow - -### 🐛 Bug Fixes - -* **Fix npm install peer dependency issues** — Add `.npmrc` with `legacy-peer-deps=true`, update Starlight to 0.37.5, and add `--legacy-peer-deps` flag to module installer (PR #1476) -* **Fix leaked source paths in PRD validation report** — Replace absolute `/src/core/` paths with `{project-root}/_bmad/core/` (#1481) -* **Fix orphaned market research customer analysis** — Connect step-01-init to step-02-customer-behavior to complete workflow sharding (#1486) -* **Fix duplicate 2-letter brainstorming code** — Change BS to BSP to resolve conflict with cis Brainstorming module -* **Fix tech writer sidecar functionality** — Enable proper sidecar operation (#1487) -* **Fix relative paths in workflow steps** — Correct paths in step-11-polish (#1497) and step-e-04-complete (#1498) -* **Fix party-mode workflow file extension** — Correct extension in workflow.xml (#1499) -* **Fix generated slash commands** — Add `disable-model-invocation` to all generated commands (#1501) -* **Fix agent scan and help CSV files** — Correct module-help.csv entries -* **Fix HELP_STEP placeholder replacement** — Fix placeholder not replaced in compiled agents, fix hardcoded path, fix single quote (#1437) - -### 📚 Documentation - -* **Add exact slash commands to Getting Started guide** — Provide precise command examples for users (#1505) -* **Remove .claude/commands from version control** — Commands are generated, not tracked (#1506) - -### 🔧 Maintenance - -* **Update Starlight to 0.37.5** — Latest version with peer dependency compatibility -* **Add GitHub issue templates** — New bug-report.yaml and documentation.yaml templates - ---- - -## [6.0.0-Beta.4] - -### 🐛 Bug Fixes - -- **Activation steps formatting fix**: Fixed missing opening quote that caused infrequent menu rendering issues -- **Custom module installation fix**: Added missing yaml require in manifest.js to fix custom module installation - ---- - -## [6.0.0-Beta.3] - -### 🌟 Key Highlights - -1. **SDET Module Replaces TEA**: TEA module removed from core, SDET module added with "automate" workflow for test automation -2. **Gemini CLI TOML Support**: IDE integration now supports the TOML config format used by Gemini CLI -3. **File System Sprint Status**: Default project_key support for file-system based sprint status tracking - -### 🔧 Features & Improvements - -**Module Changes:** -- **TEA Module Moved to External** (#1430, #1443): The TEA module is now external. SDET module added with a single "automate" workflow focused on test automation -- **SDET Module**: New module with streamlined test automation capabilities - -**IDE Integration:** -- **Gemini CLI TOML Format** (#1431): Previous update accidentally switched Gemini to md instead of toml. - -**Sprint Status:** -- **Default project_key** (#1446): File-system based sprint status now uses a default project_key so certain LLMs do not complain - -### 🐛 Bug Fixes - -- **Quick-flow workflow path fix** (#1368): Fixed incorrect workflow_path in bmad-quick-flow/quick-spec steps (step-01, step-02, step-03) - changed from non-existent 'create-tech-spec' to correct 'quick-spec' -- **PRD edit flow paths**: Fixed path references in PRD editing workflow -- **Agent file handling**: Changes to prevent double agent files and use .agent.md file extensions -- **README link fix**: Corrected broken documentation links - -## [6.0.0-Beta.2] - -- Fix installer so commands match what is installed, centralize most ide into a central file instead of separate files for each ide. -- Specific IDEs may still need udpates, but all is config driven now and should be easier to maintain -- Kiro still needs updates, but its been in this state since contributed, will investigate soon -- Any version older than Beta.0 will recommend removal and reinstall to project. From later alphas though its sufficient to quick update if still desired, but best is just start fresh with Beta. - -## [6.0.0-Beta.1] - -**Release: January 2026 - Alpha to Beta Transition** - -### 🎉 Beta Release - -- **Transition from Alpha to Beta**: BMad Method is now in Beta! This marks a significant milestone in the framework's development -- **NPM Default Tag**: Beta versions are now published with the `latest` tag, making `npx bmad-method` serve the beta version by default - -### 🌟 Key Highlights - -1. **bmad-help**: Revolutionary AI-powered guidance system replaces the alpha workflow-init and workflow tracking — introduces full AI intelligence to guide users through workflows, commands, and project context -2. **Module Ecosystem Expansion**: bmad-builder, CIS (Creative Intelligence Suite), and Game Dev Studio moved to separate repositories for focused development -3. **Installer Consolidation**: Unified installer architecture with standardized command naming (`bmad-dash-case.md` or `bmad-*-agent-*.md`) -4. **Windows Compatibility**: Complete migration from Inquirer.js to @clack/prompts for reliable cross-platform support - -### 🚀 Major Features - -**bmad-help - Intelligent Guidance System:** - -- **Replaces**: workflow-init and legacy workflow tracking -- **AI-Powered**: Full context awareness of installed modules, workflows, agents, and commands -- **Dynamic Discovery**: Automatically catalogs all available workflows from installed modules -- **Intelligent Routing**: Guides users to the right workflow or agent based on their goal -- **IDE Integration**: Generates proper IDE command files for all discovered workflows - -**Module Restructuring:** - -| Module | Status | New Location | -| ------------------------------------- | ------------------------------------------------- | ------------------------------------------------------- | -| **bmad-builder** | Near beta, with docs and walkthroughs coming soon | `bmad-code-org/bmad-builder` | -| **CIS** (Creative Intelligence Suite) | Published as npm package | `bmad-code-org/bmad-module-creative-intelligence-suite` | -| **Game Dev Studio** | Published as npm package | `bmad-code-org/bmad-module-game-dev-studio` | - -### 🔧 Installer & CLI Improvements - -**UnifiedInstaller Architecture:** - -- All IDE installers now use a common `UnifiedInstaller` class -- Standardized command naming conventions: - - Workflows: `bmad-module-workflow-name.md` - - Agents: `bmad-module-agent-name.md` - - Tasks: `bmad-task-name.md` - - Tools: `bmad-tool-name.md` -- External module installation from npm with progress indicators -- Module removal on unselect with confirmation - -**Windows Compatibility Fix:** - -- Replaced Inquirer.js with @clack/prompts to fix arrow key navigation issues on Windows -- All 91 installer workflows migrated to new prompt system - -### 📚 Documentation Updates - -**Significant docsite improvements:** - -- Interactive workflow guide page (`/workflow-guide`) with track selector -- TEA documentation restructured using Diátaxis framework (25 docs) -- Style guide optimized for LLM readers (367 lines, down from 767) -- Glossary rewritten using table format (123 lines, down from 373) -- README overhaul with numbered command flows and prominent `/bmad-help` callout -- New workflow map diagram with interactive HTML -- New editorial review tasks for document quality -- E2E testing methodology for Game Dev Studio - -More documentation updates coming soon. - -### 🐛 Bug Fixes - -- Fixed TodoMVC URL references to include `/dist/` path -- Fixed glob pattern normalization for Windows compatibility -- Fixed YAML indentation in kilo.js customInstructions field -- Fixed stale path references in check-implementation-readiness workflow -- Fixed sprint-status.yaml sync in correct-course workflow -- Fixed web bundler entry point reference -- Fixed mergeModuleHelpCatalogs ordering after generateManifests - -### 📊 Statistics - -- **91 commits** since alpha.23 -- **969 files changed** (+23,716 / -91,509 lines) -- **Net reduction of ~67,793 lines** through cleanup and consolidation -- **3 major modules** moved to separate repositories -- **Complete installer refactor** for standardization - ---- - -## [6.0.0-alpha.23] - -**Release: January 11, 2026** - -### 🌟 Key Highlights - -1. **Astro/Starlight Documentation Platform**: Complete migration from Docusaurus to modern Astro+Starlight for superior performance and customization -2. **Diataxis Framework Implementation**: Professional documentation restructuring with tutorials, how-to guides, explanations, and references -3. **Workflow Creator & Validator**: Powerful new tools for workflow creation with subprocess support and PRD validation -4. **TEA Documentation Expansion**: Comprehensive testing documentation with cheat sheets, MCP enhancements, and API testing patterns -5. **Brainstorming Revolution**: Research-backed procedural rigor with 100+ idea goal and anti-bias protocols -6. **Cursor IDE Modernization**: Refactored from rules-based to command-based architecture for better IDE integration - -### 📚 Documentation Platform Revolution - -**Astro/Starlight Migration:** - -- **From Docusaurus to Astro**: Complete platform migration for improved performance, better customization, and modern tooling -- **Starlight Theme**: Professional documentation theme with dark mode default and responsive design -- **Build Pipeline Overhaul**: New build-docs.js orchestrates link checking, artifact generation, and Astro build -- **LLM-Friendly Documentation**: Generated llms.txt and llms-full.txt for AI agent discoverability -- **Downloadable Source Bundles**: bmad-sources.zip and bmad-prompts.zip for offline use - -**Diataxis Framework Implementation:** - -- **Four Content Types**: Professional separation into tutorials, how-to guides, explanations, and references -- **21 Files Migrated**: Phase 1 migration of core documentation to Diataxis structure -- **42+ Focused Documents**: Phase 2 split of large legacy files into manageable pieces -- **FAQ Restructuring**: 7 topic-specific FAQ files with standardized format -- **Tutorial Style Guide**: Comprehensive documentation standards for consistent content creation - -**Link Management & Quality:** - -- **Site-Relative Links**: Converted 217 links to repo-relative format (/docs/path/file.md) -- **Link Validation Tools**: New validate-doc-links.js and fix-doc-links.js for maintaining link integrity -- **Broken Link Fixes**: Resolved ~50 broken internal links across documentation -- **BMad Acronym Standardization**: Consistent use of "BMad" (Breakthrough Method of Agile AI Driven Development) -- **SEO Optimization**: Absolute URLs in AI meta tags for better web crawler discoverability - -### 🔧 Workflow Creator & Validator (Major Feature) - -**Workflow Creation Tool:** - -- **Subprocess Support**: Advanced workflows can now spawn subprocesses for complex operations -- **PRD Validation Step**: New validation step ensures PRD quality before workflow execution -- **Trimodal Workflow Creation**: Three-mode workflow generation system -- **Quadrivariate Module Workflow**: Four-variable workflow architecture for enhanced flexibility -- **Path Violation Checks**: Validator ensures workflows don't violate path constraints -- **Max Parallel Mode POC**: Proof-of-concept for parallel workflow validation - -**Workflow Quality Improvements:** - -- **PRD Trimodal Compliance**: PRD workflow now follows trimodal standards -- **Standardized Step Formatting**: Consistent markdown formatting across workflow and PRD steps -- **Better Suggested Next Steps**: Improved workflow completion guidance -- **Variable Naming Standardization**: {project_root} → {project-root} across all workflows - -### 🧪 TEA Documentation Expansion - -**Comprehensive Testing Guides:** - -- **Cheat Sheets**: Quick reference guides for common testing scenarios -- **MCP Enhancements**: Model Context Protocol improvements for testing workflows -- **API Testing Patterns**: Best practices for API testing documentation -- **Design Philosophy Callout**: Clear explanation of TEA's design principles -- **Context Engineering Glossary**: New glossary entry defining context engineering concepts -- **Fragment Count Updates**: Accurate documentation of TEA workflow components -- **Playwright Utils Examples**: Updated code examples for playwright-utils integration - -### 💡 Brainstorming Workflow Overhaul - -**Research-Backed Procedural Rigor:** - -- **100+ Idea Goal**: Emphasis on quantity-first approach to unlock better quality ideas -- **Anti-Bias Protocol**: Domain pivot every 10 ideas to reduce cognitive biases -- **Chain-of-Thought Requirements**: Reasoning before idea generation -- **Simulated Temperature**: Prompts for higher divergence in ideation -- **Standardized Idea Format**: Quality control template for consistent output -- **Energy Checkpoints**: Multiple continuation options to maintain creative flow - -**Exploration Menu Improvements:** - -- **Letter-Based Navigation**: [K/T/A/B/C] options instead of numbers for clarity -- **Keep/Try/Advanced/Break/Continue**: Clear action options for idea refinement -- **Universal Facilitation Rules**: Consistent guidelines across all brainstorming steps -- **Quality Growth Enforcement**: Balance between quantity and quality metrics - -### 🖥️ Cursor IDE Modernization - -**Command-Based Architecture:** - -- **From Rules to Commands**: Complete refactor from rules-based to command-based system -- **Command Generation**: Automatic generation of task and tool commands -- **Commands Directory**: New `.cursor/commands/bmad/` structure for generated commands -- **Cleanup Integration**: Automatic cleanup of old BMAD commands alongside rules -- **Enhanced Logging**: Better feedback on agents, tasks, tools, and workflow commands generated - -### 🤖 Agent System Improvements - -**Agent Builder & Validation:** - -- **hasSidecar Field**: All agents now indicate sidecar support (true/false) -- **Validation Enforcement**: hasSidecar now required in agent validation -- **Better Brownfield Documentation**: Improved brownfield project documentation -- **Agent Builder Updates**: Agent builder now uses hasSidecar field -- **Agent Editor Integration**: Editor workflow respects hasSidecar configuration - -### 🐛 Bug Fixes & Quality Improvements - -**Critical Fixes:** - -- **Windows Line Endings**: Resolved CRLF issues causing cross-platform problems -- **Code-Review File Filtering**: Fixed code-review picking up non-application files -- **ERR_REQUIRE_ESM Resolution**: Dynamic import for inquirer v9+ compatibility -- **Project-Context Conflicts**: Allow full project-context usage with conflict precedence -- **Workflow Paths**: Fixed paths for workflow and sprint status files -- **Missing Scripts**: Fixed missing scripts from installation - -**Workflow & Variable Fixes:** - -- **Variable Naming**: Standardized from {project_root} to {project-root} across CIS, BMGD, and BMM modules -- **Workflow References**: Fixed broken .yaml → .md workflow references -- **Advanced Elicitation Variables**: Fixed undefined variables in brainstorming -- **Dependency Format**: Corrected dependency format and added missing frontmatter - -**Code Quality:** - -- **Dependency Updates**: Bumped qs from 6.14.0 to 6.14.1 -- **CodeRabbit Integration**: Enabled auto-review on new PRs -- **TEA Fragment Counts**: Updated fragment counts for accuracy -- **Documentation Links**: Fixed Discord channel references (#general-dev → #bmad-development) - -### 🚀 Installation & CLI Improvements - -**Installation Enhancements:** - -- **Workflow Exclusion**: Ability to exclude workflows from being added as commands -- **Example Workflow Protection**: Example workflow in workflow builder now excluded from tools -- **CNAME Configuration**: Added CNAME file for custom domain support -- **Script Fixes**: All scripts now properly included in installation - -### 📊 Statistics - -- **27 commits** since alpha.22 -- **217 documentation links** converted to site-relative format -- **42+ focused documents** created from large legacy files -- **7 topic-specific FAQ files** with standardized formatting -- **Complete documentation platform** migrated from Docusaurus to Astro/Starlight -- **Major workflow tools** added: Creator, Validator with subprocess support -- **Brainstorming workflow** overhauled with research-backed rigor - ---- - -## [6.0.0-alpha.22] - -**Release: December 31, 2025** - -### 🌟 Key Highlights - -1. **Unified Agent Workflow**: Create, Edit, and Validate workflows consolidated into single powerful agent workflow with separate step paths -2. **Agent Knowledge System**: Comprehensive data file architecture with persona properties, validation patterns, and crafting principles -3. **Deep Language Integration**: All sharded progressive workflows now support language choice at every step -4. **Core Module Documentation**: Extensive docs for core workflows (brainstorming, party mode, advanced elicitation) -5. **BMAD Core Concepts**: New documentation structure explaining agents, workflows, modules, and installation -6. **Tech Spec Sharded**: create-tech-spec workflow converted to sharded format with orient-first pattern - -### 🤖 Unified Agent Workflow (Major Feature) - -**Consolidated Architecture:** - -- **Single Workflow, Three Paths**: Create, Edit, and Validate operations unified under `src/modules/bmb/workflows/agent/` -- **steps-c/**: Create path with 9 comprehensive steps for building new agents -- **steps-e/**: Edit path with 10 steps for modifying existing agents -- **steps-v/**: Validate path for standalone agent validation review -- **data/**: Centralized knowledge base for all agent-building intel - -### 📚 Agent Knowledge System - -**Data File Architecture:** - -Located in `src/modules/bmb/workflows/agent/data/`: - -- **agent-metadata.md** (208 lines) - Complete metadata field reference -- **agent-menu-patterns.md** (233 lines) - Menu design patterns and best practices -- **agent-compilation.md** (273 lines) - Compilation process documentation -- **persona-properties.md** (266 lines) - Persona crafting properties and examples -- **principles-crafting.md** (292 lines) - Core principles for agent design -- **critical-actions.md** (120 lines) - Critical action patterns -- **expert-agent-architecture.md** (236 lines) - Expert agent structure -- **expert-agent-validation.md** (173 lines) - Expert-specific validation -- **module-agent-validation.md** (124 lines) - Module-specific validation -- **simple-agent-architecture.md** (204 lines) - Simple agent structure -- **simple-agent-validation.md** (132 lines) - Simple agent validation -- **understanding-agent-types.md** (222 lines) - Agent type comparison -- **brainstorm-context.md** - Brainstorming guidance -- **communication-presets.csv** - Communication style presets - -**Reference Examples:** - -- **reference/module-examples/architect.agent.yaml** - Module agent example -- **reference/simple-examples/commit-poet.agent.yaml** - Simple agent example -- **journal-keeper/** - Complete sidecar pattern example - -**Templates:** - -- **templates/simple-agent.template.md** - Simple agent template -- **templates/expert-agent-template/expert-agent.template.md** - Expert agent template -- **templates/expert-agent-sidecar/** - Sidecar templates (instructions, memories) - -### 🌍 Deep Language Integration - -**Progressive Workflow Language Support:** - -- **Every Step Biased**: All sharded progressive workflow steps now include language preference context -- **260+ Files Updated**: Comprehensive language integration across: - - Core workflows (brainstorming, party mode, advanced elicitation) - - BMB workflows (create-agent, create-module, create-workflow, edit-workflow, etc.) - - BMGD workflows (game-brief, gdd, narrative, game-architecture, etc.) - - BMM workflows (research, create-ux-design, prd, create-architecture, etc.) -- **Tested Languages**: Verified working with Spanish and Pirate Speak -- **Natural Conversations**: AI agents respond in configured language throughout workflow - -### 📖 Core Module Documentation - -**New Core Documentation Structure:** - -`docs/modules/core/`: - -- **index.md** - Core module overview -- **core-workflows.md** - Core workflow documentation -- **core-tasks.md** - Core task reference -- **brainstorming.md** (100 lines) - Brainstorming workflow guide -- **party-mode.md** (50 lines) - Party mode guide -- **advanced-elicitation.md** (105 lines) - Advanced elicitation techniques -- **document-sharding-guide.md** (133 lines) - Sharded workflow format guide -- **global-core-config.md** - Global core configuration reference - -**Advanced Elicitation Moved:** - -- **From**: `docs/` root -- **To**: `src/core/workflows/advanced-elicitation/` -- **Status**: Now a proper core workflow with methods.csv - -### 📚 BMAD Core Concepts Documentation - -**New Documentation Structure:** - -`docs/bmad-core-concepts/`: - -- **index.md** - Core concepts introduction -- **agents.md** (93 lines) - Understanding agents in BMAD -- **workflows.md** (89 lines) - Understanding workflows in BMAD -- **modules.md** (76 lines) - Understanding modules (BMM, BMGD, CIS, BMB, Core) -- **installing/index.md** (77 lines) - Installation guide -- **installing/upgrading.md** (144 lines) - Upgrading guide -- **bmad-customization/index.md** - Customization overview -- **bmad-customization/agents.md** - Agent customization guide -- **bmad-customization/workflows.md** (30 lines) - Workflow customization guide -- **web-bundles/index.md** (34 lines) - Web bundle distribution guide - -**Documentation Cleanup:** - -- **Removed v4-to-v6-upgrade.md** - Outdated upgrade guide -- **Removed document-sharding-guide.md** from docs root (moved to core) -- **Removed web-bundles-gemini-gpt-guide.md** - Consolidated into web-bundles/index.md -- **Removed getting-started/installation.md** - Migrated to bmad-core-concepts -- **Removed all ide-info/*.md files** - Consolidated into web-bundles documentation - -### 🔧 Create-Tech-Spec Sharded Conversion - -**Monolithic to Sharded:** - -- **From**: Single `workflow.yaml` with `instructions.md` -- **To**: Sharded `workflow.md` with individual step files -- **Pattern**: Orient-first approach (understand before investigating) - -### 🔨 Additional Improvements - -**Workflow Status Path Fixes:** - -- **Corrected Discovery Paths**: workflow-status workflows now properly use planning_artifacts and implementation_artifacts -- **Updated All Path Files**: enterprise-brownfield, enterprise-greenfield, method-brownfield, method-greenfield - -**Documentation Updates:** - -- **BMB Agent Creation Guide**: Comprehensive 166-line guide for agent creation -- **Workflow Vendoring Doc**: New 42-line guide on workflow customization and inheritance -- **Document Project Reference**: Moved from BMM docs to shared location -- **Workflows Planning Guide**: New 89-line guide for planning workflows - -**BMB Documentation Streamlining:** - -- **Removed Redundant Docs**: Eliminated duplicate documentation in `src/modules/bmb/docs/` -- **Step File Rules**: New 469-line comprehensive guide for step file creation -- **Agent Docs Moved**: Agent architecture and validation docs moved to workflow data/ - -**Windows Inquirer Fix:** - -- **Another Default Addition**: Additional inquirer default value setting for better Windows multiselection support - -**Code Quality:** - -- **Removed Old BMM README**: Consolidated module documentation -- **Removed BMM Troubleshooting**: 661-line doc moved to shared location -- **Removed Enterprise Agentic Development**: 686-line doc consolidated -- **Removed Scale Adaptive System**: 618-line doc consolidated - ---- - -## [6.0.0-alpha.21] - -**Release: December 27, 2025** - -### 🌟 Key Highlights - -1. **Consistent Menu System**: All agents now use standardized 2-letter menu codes (e.g., "rd" for research, "ca" for create-architecture) -2. **Planning Artifacts Architecture**: Phase 1-3 workflows now properly segregate planning artifacts from documentation -3. **Windows Installer Fixed Again**: Updated inquirer to resolve multiselection tool issues -4. **Auto-Injected Features**: Chat and party mode automatically injected into all agents -5. **Validation System**: All agents now pass comprehensive new validation checks - -### 🎯 Consistent Menu System (Major Feature) - -**Standardized 2-Letter Codes:** - -- **Compound Menu Triggers**: All agents now use consistent 2-letter compound trigger format (e.g., `bmm-rd`, `bmm-ca`) -- **Improved UX**: Shorter, more memorable command shortcuts across all modules -- **Module Prefixing**: Menu items properly scoped by module prefix (bmm-, bmgd-, cis-, bmb-) -- **Universal Pattern**: All 22 agents updated to follow the same menu structure - -**Agent Updates:** - -- **BMM Module**: 9 agents with standardized menus (pm, analyst, architect, dev, ux-designer, tech-writer, sm, tea, quick-flow-solo-dev) -- **BMGD Module**: 6 agents with standardized menus (game-architect, game-designer, game-dev, game-qa, game-scrum-master, game-solo-dev) -- **CIS Module**: 6 agents with standardized menus (innovation-strategist, design-thinking-coach, creative-problem-solver, brainstorming-coach, presentation-master, storyteller) -- **BMB Module**: 3 agents with standardized menus (bmad-builder, agent-builder, module-builder, workflow-builder) -- **Core Module**: BMAD Master agent updated with consistent menu patterns - -### 📁 Planning Artifacts Architecture - -**Content Segregation Implementation:** - -- **Phase 1-3 Workflows**: All planning workflows now use `planning_artifacts` folder (default changed from `docs`) -- **Proper Input Discovery**: Workflows follow consistent input discovery patterns from planning artifacts -- **Output Management**: Planning artifacts properly separated from long-term documentation -- **Affected Workflows**: - - Product Brief: Updated discovery and output to planning artifacts - - PRD: Fixed discovery and output to planning artifacts - - UX Design: Updated all steps for proper artifact handling - - Architecture: Updated discovery and output flow - - Game Architecture: Updated for planning artifacts - - Story Creation: Updated workflow output paths - -**File Organization:** - -- **Planning Artifacts**: Ephemeral planning documents (prd.md, product-brief.md, ux-design.md, architecture.md) -- **Documentation**: Long-term project documentation (separate from planning) -- **Module Configuration**: BMM and BMGD modules updated with proper default paths - -### 🪟 Windows Installer Fixes - -**Inquirer Multiselection Fix:** - -- **Updated Inquirer Version**: Resolved tool multiselection issues that were causing Windows installer failures -- **Better Compatibility**: Improved handling of checkbox and multi-select prompts on Windows(?) - -### 🤖 Agent System Improvements - -**Auto-Injected Features:** - -- **Chat Mode**: Automatically injected into all agents during compilation -- **Party Mode**: Automatically injected into all agents during compilation -- **Reduced Manual Configuration**: No need to manually add these features to agent definitions -- **Consistent Behavior**: All agents now have uniform access to chat and party mode capabilities - -**Agent Normalization:** - -- **All Agents Validated**: All 22 agents pass comprehensive validation checks -- **Schema Enforcement**: Proper compound trigger validation implemented -- **Metadata Cleanup**: Removed obsolete and inconsistent metadata patterns -- **Test Fixtures Updated**: Validation test fixtures aligned with new requirements - -### 🔧 Bug Fixes & Cleanup - -**Docusaurus Merge Recovery:** - -- **Restored Agent Files**: Fixed agent files accidentally modified in Docusaurus merge (PR #1191) -- **Reference Cleanup**: Removed obsolete agent reference examples (journal-keeper, security-engineer, trend-analyst) -- **Test Fixture Updates**: Aligned test fixtures with current validation requirements - -**Code Quality:** - -- **Schema Improvements**: Enhanced agent schema validation with better error messages -- **Removed Redundancy**: Cleaned up duplicate and obsolete agent definitions -- **Installer Cleanup**: Removed unused configuration code from BMM installer - -**Planning Artifacts Path:** -- Default: `planning_artifacts/` (configurable in module.yaml) -- Previous: `docs/` -- Benefit: Clear separation between planning work and permanent documentation - ---- - -## [6.0.0-alpha.20] - -**Release: December 23, 2025** - -### 🌟 Key Highlights - -1. **Windows Installer Fixed**: Better compatibility with inquirer v9.x upgrade -2. **Path Segregation**: Revolutionary content organization separating ephemeral artifacts from permanent documentation -3. **Custom Installation Messages**: Configurable intro/outro messages for professional installation experience -4. **Enhanced Upgrade Logic**: Two-version auto upgrades with proper config preservation -5. **Quick-Dev Refactor**: Sharded format with comprehensive adversarial review -6. **Improved Quality**: Streamlined personas, fixed workflows, and cleaned up documentation -7. **Doc Site Auto Generation**; Auto Generate a docusaurus site update on merge - -### 🪟 Windows Installer (hopefully) Fixed - -**Inquirer Upgrade:** - -- **Updated to v9.x**: Upgraded inquirer package for better Windows support -- **Improved Compatibility**: Better handling of Windows terminal environments -- **Enhanced UX**: More reliable interactive prompts across platforms - -### 🎯 Path Segregation Implementation (Major Feature) - -**Revolutionary Content Organization:** - -- **Phase 1-4 Path Segregation**: Implemented new BM paths across all BMM and BMGD workflows -- **Planning vs Implementation Artifacts**: Separated ephemeral Phase 4 artifacts from permanent documentation -- **Optimized File Organization**: Better structure differentiating planning artifacts from long-term project documentation -- **Backward Compatible**: Existing installations continue working while preparing for optimized content organization -- **Module Configuration Updates**: Enhanced module.yaml with new path configurations for all phases -- **Workflow Path Updates**: All 90+ workflow files updated with proper path configurations - -**Documentation Cleanup:** - -- **Removed Obsolete Documentation**: Cleaned up 3,100+ lines of outdated documentation -- **Streamlined README Files**: Consolidated and improved module documentation -- **Enhanced Clarity**: Removed redundant content and improved information architecture - -### 💬 Installation Experience Enhancements - -**Custom Installation Messages:** - -- **Configurable Intro/Outro Messages**: New install-messages.yaml file for customizable installation messages -- **Professional Installation Flow**: Custom welcome messages and completion notifications -- **Module-Specific Messaging**: Tailored messages for different installation contexts -- **Enhanced User Experience**: More informative and personalized installation process - -**Core Module Improvements:** - -- **Always Ask Questions**: Core module now always prompts for configuration (no accept defaults) -- **Better User Engagement**: Ensures users actively configure their installation -- **Improved Configuration Accuracy**: Reduces accidental acceptance of defaults - -### 🔧 Upgrade & Configuration Management - -**Two-Version Auto Upgrade:** - -- **Smarter Upgrade Logic**: Automatic upgrades now span 2 versions (e.g., .16 → .18) -- **Config Variable Preservation**: Ensures all configuration variables are retained during quick updates -- **Seamless Updates**: Quick updates now preserve custom settings properly -- **Enhanced Upgrade Safety**: Better handling of configuration across version boundaries - -### 🤖 Workflow Improvements - -**Quick-Dev Workflow Refactor (PR #1182):** - -- **Sharded Format Conversion**: Converted quick-dev workflow to modern step-file format -- **Adversarial Review Integration**: Added comprehensive self-check and adversarial review steps -- **Enhanced Quality Assurance**: 6-step process with mode detection, context gathering, execution, self-check, review, and resolution -- **578 New Lines Added**: Significant expansion of quick-dev capabilities - -**BMGD Workflow Fixes:** - -- **workflow-status Filename Correction**: Fixed incorrect filename references (PR #1172) -- **sprint-planning Update**: Added workflow-status update to game-architecture completion -- **Path Corrections**: Resolved dead references and syntax errors (PR #1164) - -### 🎨 Code Quality & Refactoring - -**Persona Streamlining (PR #1167):** - -- **Quick-Flow-Solo-Dev Persona**: Streamlined for clarity and accuracy -- **Improved Agent Behavior**: More focused and efficient solo development support - -**Package Management:** - -- **package-lock.json Sync**: Ensured version consistency (PR #1168) -- **Dependency Cleanup**: Reduced package-lock bloat significantly - -**Prettier Configuration:** - -- **Markdown Underscore Protection**: Prettier will no longer mess up underscores in markdown files -- **Disabled Auto-Fix**: Markdown formatting issues now handled more intelligently -- **Better Code Formatting**: Improved handling of special characters in documentation - -### 📚 Documentation Updates - -**Sponsor Attribution:** - -- **DigitalOcean Sponsorship**: Added attribution for DigitalOcean support (PR #1162) - -**Content Reorganization:** - -- **Removed Unused Docs**: Eliminated obsolete documentation files -- **Consolidated References**: Merged and reorganized technical references -- **Enhanced README Files**: Improved module and workflow documentation - -### 🧹 Cleanup & Optimization - -**File Organization:** - -- **Removed Asterisk Insertion**: Eliminated unwanted asterisk insertions into agent files -- **Removed Unused Commands**: Cleaned up deprecated command references -- **Consolidated Duplication**: Reduced code duplication across multiple files -- **Removed Unneeded Folders**: Cleaned up temporary and obsolete directory structures - -### 📊 Statistics - -- **23 commits** since alpha.19 -- **90+ workflow files** updated with new path configurations -- **3,100+ lines of documentation** removed and reorganized -- **578 lines added** to quick-dev workflow with adversarial review -- **Major architectural improvement** to content organization - -## [6.0.0-alpha.19] - -**Release: December 18, 2025** - -### 🐛 Bug Fixes - -**Installer Stability:** - -- **Fixed \_bmad Folder Stutter**: Resolved issue with duplicate \_bmad folder creation when applying agent custom files -- **Cleaner Installation**: Removed unnecessary backup file that was causing bloat in the installer -- **Streamlined Agent Customization**: Fixed path handling for agent custom files to prevent folder duplication - -### 📊 Statistics - -- **3 files changed** with critical fix -- **3,688 lines removed** by eliminating backup files -- **Improved installer performance** and stability - ---- - -## [6.0.0-alpha.18] - -**Release: December 18, 2025** - -### 🎮 BMGD Module - Complete Game Development Module Updated - -**Massive BMGD Overhaul:** - -- **New Game QA Agent (GLaDOS)**: Elite Game QA Architect with test automation specialization - - Engine-specific expertise: Unity, Unreal, Godot testing frameworks - - Comprehensive knowledge base with 15+ testing topics - - Complete testing workflows: test-framework, test-design, automate, playtest-plan, performance-test, test-review - -- **New Game Solo Dev Agent (Indie)**: Rapid prototyping and iteration specialist - - Quick-flow workflows optimized for solo/small team development - - Streamlined development process for indie game creators - -- **Production Workflow Alignment**: BMGD 4-production now fully aligned with BMM 4-implementation - - Removed obsolete workflows: story-done, story-ready, story-context, epic-tech-context - - Added sprint-status workflow for project tracking - - All workflows updated as standalone with proper XML instructions - -**Game Testing Architecture:** - -- **Complete Testing Knowledge Base**: 15 comprehensive testing guides covering: - - Engine-specific: Unity (TF 1.6.0), Unreal, Godot testing - - Game-specific: Playtesting, balance, save systems, multiplayer - - Platform: Certification (TRC/XR), localization, input systems - - QA Fundamentals: Automation, performance, regression, smoke testing - -**New Workflows & Features:** - -- **workflow-status**: Multi-mode status checker for game projects - - Game-specific project levels (Game Jam → AAA) - - Support for gamedev and quickflow paths - - Project initialization workflow - -- **create-tech-spec**: Game-focused technical specification workflow - - Engine-aware (Unity/Unreal/Godot) specifications - - Performance and gameplay feel considerations - -- **Enhanced Documentation**: Complete documentation suite with 9 guides - - agents-guide.md: Reference for all 6 agents - - workflows-guide.md: Complete workflow documentation - - game-types-guide.md: 24 game type templates - - quick-flow-guide.md: Rapid development guide - - Comprehensive troubleshooting and glossary - -### 🤖 Agent Management Improved - -**Agent Recompile Feature:** - -- **New Menu Item**: Added "Recompile Agents" option to the installer menu -- **Selective Compilation**: Recompile only agents without full module upgrade -- **Faster Updates**: Quick agent updates without complete reinstallation -- **Customization Integration**: Automatically applies customizations during recompile - -**Agent Customization Enhancement:** - -- **Complete Field Support**: ALL fields from agent customization YAML are now properly injected -- **Deep Merge Implementation**: Customizations now properly override all agent properties -- **Persistent Customizations**: Custom settings survive updates and recompiles -- **Enhanced Flexibility**: Support for customizing metadata, persona, menu items, and workflows - -### 🔧 Installation & Module Management - -**Custom Module Installation:** - -- **Enhanced Module Addition**: Modify install now supports adding custom modules even if none were originally installed -- **Flexible Module Management**: Easy addition and removal of custom modules post-installation -- **Improved Manifest Tracking**: Better tracking of custom vs core modules - -**Quality Improvements:** - -- **Comprehensive Code Review**: Fixed 20+ issues identified in PR review -- **Type Validation**: Added proper type checking for configuration values -- **Path Security**: Enhanced path traversal validation for better security -- **Documentation Updates**: All documentation updated to reflect new features - -### 📊 Statistics - -- **178 files changed** with massive BMGD expansion -- **28,350+ lines added** across testing documentation and workflows -- **2 new agents** added to BMGD module -- **15 comprehensive testing guides** created -- **Complete alignment** between BMGD and BMM production workflows - -### 🌟 Key Highlights - -1. **BMGD Module Revolution**: Complete overhaul with professional game development workflows -2. **Game Testing Excellence**: Comprehensive testing architecture for all major game engines -3. **Agent Management**: New recompile feature allows quick agent updates without full reinstall -4. **Full Customization Support**: All agent fields now customizable via YAML -5. **Industry-Ready Documentation**: Professional-grade guides for game development teams - ---- - -## [6.0.0-alpha.17] - -**Release: December 16, 2025** - -### 🚀 Revolutionary Installer Overhaul - -**Unified Installation Experience:** - -- **Streamlined Module Installation**: Completely redesigned installer with unified flow for both core and custom content -- **Single Install Panel**: Eliminated disjointed clearing between modules for smoother, more intuitive installation -- **Quick Default Selection**: New quick install feature with default selections for faster setup of selected modules -- **Enhanced UI/UX**: Improved question order, reduced verbose output, and cleaner installation interface -- **Logical Question Flow**: Reorganized installer questions to follow natural progression and user expectations - -**Custom Content Installation Revolution:** - -- **Full Custom Content Support**: Re-enabled complete custom content generation and sharing through the installer -- **Custom Module Tracking**: Manifest now tracks custom modules separately to ensure they're always installed from the custom cache -- **Custom Installation Order**: Custom modules now install after core modules for better dependency management -- **Quick Update with Custom Content**: Quick update now properly retains and updates custom content -- **Agent Customization Integration**: Customizations are now applied during quick updates and agent compilation - -### 🧠 Revolutionary Agent Memory & Visibility System - -**Breaking Through Dot-Folder Limitations:** - -- **Dot-Folder to Underscore Migration**: Critical change from `.bmad` to `_bmad` ensures LLMs (Codex, Claude, and others) can no longer ignore or skip BMAD content - dot folders are commonly filtered out by AI systems -- **Universal Content Visibility**: Underscore folders are treated as regular content, ensuring full AI agent access to all BMAD resources and configurations -- **Agent Memory Architecture**: Rolled out comprehensive agent memory support for installed agents with `-sidecar` folders -- **Persistent Agent Learning**: Sidecar content installs to `_bmad/_memory`, giving each agent the ability to learn and remember important information specific to its role - -**Content Location Strategy:** - -- **Standardized Memory Location**: All sidecar content now uses `_bmad/_memory` as the unified location for agent memories -- **Segregated Output System**: New architecture supports differentiating between ephemeral Phase 4 artifacts and long-term documentation -- **Forward Compatibility**: Existing installations continue working with content in docs folder, with optimization coming in next release -- **Configuration Cleanup**: Renamed `_cfg` to `_config` for clearer naming conventions -- **YAML Library Consolidation**: Reduced dependency to use only one YAML library for better stability - -### 🎯 Future-Ready Architecture - -**Content Organization Preview:** - -- **Phase 4 Artifact Segregation**: Infrastructure ready for separating ephemeral workflow artifacts from permanent documentation -- **Planning vs Implementation Docs**: New system will differentiate between planning artifacts and long-term project documentation -- **Backward Compatibility**: Current installs maintain full functionality while preparing for optimized content organization -- **Quick Update Path**: Tomorrow's quick update will fully optimize all BMM workflows to use new segregated output locations - -### 🎯 Sample Modules & Documentation - -**Comprehensive Examples:** - -- **Sample Unitary Module**: Complete example with commit-poet agent and quiz-master workflow -- **Sample Wellness Module**: Meditation guide and wellness companion agents demonstrating advanced patterns -- **Enhanced Documentation**: Updated README files and comprehensive installation guides -- **Custom Content Creation Guides**: Step-by-step documentation for creating and sharing custom modules - -### 🔧 Bug Fixes & Optimizations - -**Installer Improvements:** - -- **Fixed Duplicate Entry Issue**: Resolved duplicate entries in files manifest -- **Reduced Log Noise**: Less verbose logging during installation for cleaner user experience -- **Menu Wording Updates**: Improved menu text for better clarity and understanding -- **Fixed Quick Install**: Resolved issues with quick installation functionality - -**Code Quality:** - -- **Minor Code Cleanup**: General cleanup and refactoring throughout the codebase -- **Removed Unused Code**: Cleaned up deprecated and unused functionality -- **Release Workflow Restoration**: Fixed automated release workflow for v6 - -**BMM Phase 4 Workflow Improvements:** - -- **Sprint Status Enhancement**: Improved sprint-status validation with interactive correction for unknown values and better epic status handling -- **Story Status Standardization**: Normalized all story status references to lowercase kebab-case (ready-for-dev, in-progress, review, done) -- **Removed Stale Story State**: Eliminated deprecated 'drafted' story state - stories now go directly from creation to ready-for-dev -- **Code Review Clarity**: Improved code review completion message from "Story is ready for next work!" to "Code review complete!" for better clarity -- **Risk Detection Rules**: Rewrote risk detection rules for better LLM clarity and fixed warnings vs risks naming inconsistency - -### 📊 Statistics - -- **40+ commits** since alpha.16 -- **Major installer refactoring** with complete UX overhaul -- **2 new sample modules** with comprehensive examples -- **Full custom content support** re-enabled and improved - -### 🌟 Key Highlights - -1. **Installer Revolution**: The installation system has been completely overhauled for better user experience, reliability, and speed -2. **Custom Content Freedom**: Users can now easily create, share, and install custom content through the streamlined installer -3. **AI Visibility Breakthrough**: Migration from `.bmad` to `_bmad` ensures LLMs can access all BMAD content (dot folders are commonly ignored by AI systems) -4. **Agent Memory System**: Rolled out persistent agent memory support - agents with `-sidecar` folders can now learn and remember important information in `_bmad/_memory` -5. **Quick Default Selection**: Installation is now faster with smart default selections for popular configurations -6. **Future-Ready Architecture**: Infrastructure in place for segregating ephemeral artifacts from permanent documentation (full optimization coming in next release) - -## [6.0.0-alpha.16] - -**Release: December 10, 2025** - -### 🔧 Temporary Changes & Fixes - -**Installation Improvements:** - -- **Temporary Custom Content Installation Disable**: Custom content installation temporarily disabled to improve stability -- **BMB Workflow Path Fixes**: Fixed numerous path references in BMB workflows to ensure proper step file resolution -- **Package Updates**: Updated dependencies for improved security and performance - -**Path Resolution Improvements:** - -- **BMB Agent Builder Fixes**: Corrected path references in step files and documentation -- **Workflow Path Standardization**: Ensured consistent path handling across all BMB workflows -- **Documentation References**: Updated internal documentation links and references - -**Cleanup Changes:** - -- **Example Modules Removal**: Temporarily removed example modules to prevent accidental installation -- **Memory Management**: Improved sidecar file handling for custom modules - -### 📊 Statistics - -- **336 files changed** with path fixes and improvements -- **4 commits** since alpha.15 - ---- - -## [6.0.0-alpha.15] - -**Release: December 7, 2025** - -### 🔧 Module Installation Standardization - -**Unified Module Configuration:** - -- **module.yaml Standard**: All modules now use `module.yaml` instead of `_module-installer/install-config.yaml` for consistent configuration (BREAKING CHANGE) -- **Universal Installer**: Both core and custom modules now use the same installer with consistent behavior -- **Streamlined Module Creation**: Module builder templates updated to use new module.yaml standard -- **Enhanced Module Discovery**: Improved module caching and discovery mechanisms - -**Custom Content Installation Revolution:** - -- **Interactive Custom Content Search**: Installer now proactively asks if you have custom content to install -- **Flexible Location Specification**: Users can indicate custom content location during installation -- **Improved Custom Module Handler**: Enhanced error handling and debug output for custom installations -- **Comprehensive Documentation**: New custom-content-installation.md guide (245 lines) replacing custom-agent-installation.md - -### 🤖 Code Review Integration Expansion - -**AI Review Tools:** - -- **CodeRabbit AI Integration**: Added .coderabbit.yaml configuration for automated code review -- **Raven's Verdict PR Review Tool**: New PR review automation tool (297 lines of documentation) -- **Review Path Configuration**: Proper exclusion patterns for node_modules and generated files -- **Review Documentation**: Comprehensive usage guidance and skip conditions for PRs - -### 📚 Documentation Improvements - -**Documentation Restructuring:** - -- **Code of Conduct**: Moved to .github/ folder following GitHub standards -- **Gem Creation Link**: Updated to point to Gemini Gem manager instead of deprecated interface -- **Example Custom Content**: Improved README files and disabled example modules to prevent accidental installation -- **Custom Module Documentation**: Enhanced module installation guides with new YAML structure - -### 🧹 Cleanup & Optimization - -**Memory Management:** - -- **Removed Hardcoded .bmad Folders**: Cleaned up demo content to use configurable paths -- **Sidecar File Cleanup**: Removed old .bmad-user-memory folders from wellness modules -- **Example Content Organization**: Better organization of example-custom-content directory - -**Installer Improvements:** - -- **Debug Output Enhancement**: Added informative debug output when installer encounters errors -- **Custom Module Caching**: Improved caching mechanism for custom module installations -- **Consistent Behavior**: All modules now behave consistently regardless of custom or core status - -### 📊 Statistics - -- **77 files changed** with 2,852 additions and 607 deletions -- **15 commits** since alpha.14 - -### ⚠️ Breaking Changes - -1. **module.yaml Configuration**: All modules must now use `module.yaml` instead of `_module-installer/install-config.yaml` - - Core modules updated automatically - - Custom modules will need to rename their configuration file - - Module builder templates generate new format - -### 📦 New Dependencies - -- No new dependencies added in this release - ---- - -## [6.0.0-alpha.14] - -**Release: December 7, 2025** - -### 🔧 Installation & Configuration Revolution - -**Custom Module Installation Overhaul:** - -- **Simple custom.yaml Installation**: Custom agents and workflows can now be installed with a single YAML file -- **IDE Configuration Preservation**: Upgrades will no longer delete custom modules, agents, and workflows from IDE configuration -- **Removed Legacy agent-install Command**: Streamlined installation process (BREAKING CHANGE) -- **Sidecar File Retention**: Custom sidecar files are preserved during updates -- **Flexible Agent Sidecar Locations**: Fully configurable via config options instead of hardcoded paths - -**Module Discovery System Transformation:** - -- **Recursive Agent Discovery**: Deep scanning for agents across entire project structure -- **Enhanced Manifest Generation**: Comprehensive scanning of all installed modules -- **Nested Agent Support**: Fixed nested agents appearing in CLI commands -- **Module Reinstall Fix**: Prevented modules from showing as obsolete during reinstall - -### 🏗️ Advanced Builder Features - -**Workflow Builder Evolution:** - -- **Continuable Workflows**: Create workflows with sophisticated branching and continuation logic -- **Template LOD Options**: Level of Detail output options for flexible workflow generation -- **Step-Based Architecture**: Complete conversion to granular step-file system -- **Enhanced Creation Process**: Improved workflow creation with better template handling - -**Module Builder Revolution:** - -- **11-Step Module Creation**: Comprehensive step-by-step module generation process -- **Production-Ready Templates**: Complete templates for agents, installers, and workflow plans -- **Built-in Validation System**: Ensures module quality and BMad Core compliance -- **Professional Documentation**: Auto-generated module documentation and structure - -### 🚀 BMad Method (BMM) Enhancements - -**Workflow Improvements:** - -- **Brownfield PRD Support**: Enhanced PRD workflow for existing project integration -- **Sprint Status Command**: New workflow for tracking development progress -- **Step-Based Format**: Improved continue functionality across all workflows -- **Quick-Spec-Flow Documentation**: Rapid development specification flows - -**Documentation Revolution:** - -- **Comprehensive Troubleshooting Guide**: 680-line detailed troubleshooting documentation -- **Quality Check Integration**: Added markdownlint-cli2 for markdown quality assurance -- **Enhanced Test Architecture**: Improved CI/CD templates and testing workflows - -### 🌟 New Features & Integrations - -**Kiro-Cli Installer:** - -- **Intelligent Routing**: Smart routing to quick-dev workflow -- **BMad Core Compliance**: Full compliance with BMad standards - -**Discord Notifications:** - -- **Compact Format**: Streamlined plain-text notifications -- **Bug Fixes**: Resolved notification delivery issues - -**Example Mental Wellness Module (MWM):** - -- **Complete Module Example**: Demonstrates advanced module patterns -- **Multiple Agents**: CBT Coach, Crisis Navigator, Meditation Guide, Wellness Companion -- **Workflow Showcase**: Crisis support, daily check-in, meditation, journaling workflows - -### 🐛 Bug Fixes & Optimizations - -- Fixed version reading from package.json instead of hardcoded fallback -- Removed hardcoded years from WebSearch queries -- Removed broken build caching mechanism -- Enhanced TTS injection summary with tracking and documentation -- Fixed CI nvmrc configuration issues - -### 📊 Statistics - -- **335 files changed** with 17,161 additions and 8,204 deletions -- **46 commits** since alpha.13 - -### ⚠️ Breaking Changes - -1. **Removed agent-install Command**: Migrate to new custom.yaml installation system -2. **Agent Sidecar Configuration**: Now requires explicit config instead of hardcoded paths - -### 📦 New Dependencies - -- `markdownlint-cli2: ^0.19.1` - Professional markdown linting - ---- - -## [6.0.0-alpha.13] - -**Release: November 30, 2025** - -### 🏗️ Revolutionary Workflow Architecture - -- **Step-File System**: Complete conversion to granular step-file architecture with dynamic menu generation -- **Phase 4 Transformation**: Simplified architecture with sprint planning integration (Jira, Linear, Trello) -- **Performance Improvements**: Eliminated time-based estimates, reduced file loading times -- **Legacy Cleanup**: Removed all deprecated workflows for cleaner system - -### 🤖 Agent System Revolution - -- **Universal Custom Agent Support**: Extended to ALL IDEs including Antigravity and Rovo Dev -- **Agent Creation Workflow**: Enhanced with better documentation and parameter clarity -- **Multi-Source Discovery**: Agents now check multiple source locations for better discovery -- **GitHub Migration**: Integration moved from chatmodes to agents folder - -### 🧪 Testing Infrastructure - -- **Playwright Utils Integration**: @seontechnologies/playwright-utils across all testing workflows -- **TTS Injection System**: Complete text-to-speech integration for voice feedback -- **Web Bundle Test Support**: Enabled web bundles for test environments - -### ⚠️ Breaking Changes - -1. **Legacy Workflows Removed**: Migrate to new stepwise sharded workflows -2. **Phase 4 Restructured**: Update automation expecting old Phase 4 structure -3. **Agent Compilation Required**: Custom agents must use new creation workflow - -## [6.0.0-alpha.12] - -**Release: November 19, 2025** - -### 🐛 Bug Fixes - -- Added missing `yaml` dependency to fix `MODULE_NOT_FOUND` error when running `npx bmad-method install` - -## [6.0.0-alpha.11] - -**Release: November 18, 2025** - -### 🚀 Agent Installation Revolution - -- **bmad agent-install CLI**: Interactive agent installation with persona customization -- **4 Reference Agents**: commit-poet, journal-keeper, security-engineer, trend-analyst -- **Agent Compilation Engine**: YAML → XML with smart handler injection -- **60 Communication Presets**: Pure communication styles for agent personas - -### 📚 BMB Agent Builder Enhancement - -- **Complete Documentation Suite**: 7 new guides for agent architecture and creation -- **Expert Agent Sidecar Support**: Multi-file agents with templates and knowledge bases -- **Unified Validation**: 160-line checklist shared across workflows -- **BMM Agent Voices**: All 9 agents enhanced with distinct communication styles - -### 🎯 Workflow Architecture Change - -- **Epic Creation Moved**: Now in Phase 3 after Architecture for technical context -- **Excalidraw Distribution**: Diagram capabilities moved to role-appropriate agents -- **Google Antigravity IDE**: New installer with flattened file naming - -### ⚠️ Breaking Changes - -1. **Frame Expert Retired**: Use role-appropriate agents for diagrams -2. **Agent Installation**: New bmad agent-install command replaces manual installation -3. **Epic Creation Phase**: Moved from Phase 2 to Phase 3 - -## [6.0.0-alpha.10] - -**Release: November 16, 2025** - -- **Epics After Architecture**: Major milestone - technically-informed user stories created post-architecture -- **Frame Expert Agent**: New Excalidraw specialist with 4 diagram workflows -- **Time Estimate Prohibition**: Warnings across 33 workflows acknowledging AI's impact on development speed -- **Platform-Specific Commands**: ide-only/web-only fields filter menu items by environment -- **Agent Customization**: Enhanced memory/prompts merging via \*.customize.yaml files - -## [6.0.0-alpha.9] - -**Release: November 12, 2025** - -- **Intelligent File Discovery**: discover_inputs with FULL_LOAD, SELECTIVE_LOAD, INDEX_GUIDED strategies -- **3-Track System**: Simplified from 5 levels to 3 intuitive tracks -- **Web Bundles Guide**: Comprehensive documentation with 60-80% cost savings strategies -- **Unified Output Structure**: Eliminated .ephemeral/ folders - single configurable output folder -- **BMGD Phase 4**: Added 10 game development workflows with BMM patterns - -## [6.0.0-alpha.8] - -**Release: November 9, 2025** - -- **Configurable Installation**: Custom directories with .bmad hidden folder default -- **Optimized Agent Loading**: CLI loads from installed files, eliminating duplication -- **Party Mode Everywhere**: All web bundles include multi-agent collaboration -- **Phase 4 Artifact Separation**: Stories, code reviews, sprint plans configurable outside docs -- **Expanded Web Bundles**: All BMM, BMGD, CIS agents bundled with elicitation integration - -## [6.0.0-alpha.7] - -**Release: November 7, 2025** - -- **Workflow Vendoring**: Web bundler performs automatic cross-module dependency vendoring -- **BMGD Module Extraction**: Game development split into standalone 4-phase structure -- **Advanced Elicitation Fix**: Added missing CSV files to workflow bundles -- **Claude Code Fix**: Resolved README slash command installation regression - -## [6.0.0-alpha.6] - -**Release: November 4, 2025** - -- **Critical Installer Fixes**: Fixed manifestPath error and option display issues -- **Conditional Docs Installation**: Optional documentation to reduce production footprint -- **Improved Installer UX**: Better formatting with descriptive labels and clearer feedback -- **Issue Tracker Cleanup**: Closed 54 legacy v4 issues for focused v6 development -- **Contributing Updates**: Removed references to non-existent branches - -## [6.0.0-alpha.5] - -**Release: November 4, 2025** - -- **3-Track Scale System**: Simplified from 5 levels to 3 intuitive preference-driven tracks -- **Elicitation Modernization**: Replaced legacy XML tags with explicit invoke-task pattern -- **PM/UX Evolution**: Added November 2025 industry research on AI Agent PMs -- **Brownfield Reality Check**: Rewrote Phase 0 with 4 real-world scenarios -- **Documentation Accuracy**: All agent capabilities now match YAML source of truth - -## [6.0.0-alpha.4] - -**Release: November 2, 2025** - -- **Documentation Hub**: Created 18 comprehensive guides (7000+ lines) with professional standards -- **Paige Agent**: New technical documentation specialist across all BMM phases -- **Quick Spec Flow**: Intelligent Level 0-1 planning with auto-stack detection -- **Universal Shard-Doc**: Split large markdown documents with dual-strategy loading -- **Intent-Driven Planning**: PRD and Product Brief transformed from template-filling to conversation - -## [6.0.0-alpha.3] - -**Release: October 2025** - -- **Codex Installer**: Custom prompts in `.codex/prompts/` directory structure -- **Bug Fixes**: Various installer and workflow improvements -- **Documentation**: Initial documentation structure established - -## [6.0.0-alpha.0] - -**Release: September 28, 2025** - -- **Lean Core**: Simple common tasks and agents (bmad-web-orchestrator, bmad-master) -- **BMad Method (BMM)**: Complete scale-adaptive rewrite supporting projects from small enhancements to massive undertakings -- **BoMB**: BMad Builder for creating and converting modules, workflows, and agents -- **CIS**: Creative Intelligence Suite for ideation and creative workflows -- **Game Development**: Full subclass of game-specific development patterns**Note**: Version 5.0.0 was skipped due to NPX registry issues that corrupted the version. Development continues with v6.0.0-alpha.0. - -## [v4.43.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.43.0) - -**Release: August-September 2025 (v4.31.0 - v4.43.1)** - -Focus on stability, ecosystem growth, and professional tooling. - -### Major Integrations - -- **Codex CLI & Web**: Full Codex integration with web and CLI modes -- **Auggie CLI**: Augment Code integration -- **iFlow CLI**: iFlow support in installer -- **Gemini CLI Custom Commands**: Enhanced Gemini CLI capabilities - -### Expansion Packs - -- **Godot Game Development**: Complete game dev workflow -- **Creative Writing**: Professional writing agent system -- **Agent System Templates**: Template expansion pack (Part 2) - -### Advanced Features - -- **AGENTS.md Generation**: Auto-generated agent documentation -- **NPM Script Injection**: Automatic package.json updates -- **File Exclusion**: `.bmad-flattenignore` support for flattener -- **JSON-only Integration**: Compact integration mode - -### Quality & Stability - -- **PR Validation Workflow**: Automated contribution checks -- **Fork-Friendly CI/CD**: Opt-in mechanism for forks -- **Code Formatting**: Prettier integration with pre-commit hooks -- **Update Checker**: `npx bmad-method update-check` command - -### Flattener Improvements - -- Detailed statistics with emoji-enhanced `.stats.md` -- Improved project root detection -- Modular component architecture -- Binary directory exclusions (venv, node_modules, etc.) - -### Documentation & Community - -- Brownfield document naming consistency fixes -- Architecture template improvements -- Trademark and licensing clarity -- Contributing guidelines refinement - -### Developer Experience - -- Version synchronization scripts -- Manual release workflow enhancements -- Automatic release notes generation -- Changelog file path configuration - -[View v4.43.1 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.43.1) - -## [v4.30.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.30.0) - -**Release: July 2025 (v4.21.0 - v4.30.4)** - -Introduction of advanced IDE integrations and command systems. - -### Claude Code Integration - -- **Slash Commands**: Native Claude Code slash command support for agents -- **Task Commands**: Direct task invocation via slash commands -- **BMad Subdirectory**: Organized command structure -- **Nested Organization**: Clean command hierarchy - -### Agent Enhancements - -- BMad-master knowledge base loading -- Improved brainstorming facilitation -- Better agent task following with cost-saving model combinations -- Direct commands in agent definitions - -### Installer Improvements - -- Memory-efficient processing -- Clear multi-select IDE prompts -- GitHub Copilot support with improved UX -- ASCII logo (because why not) - -### Platform Support - -- Windows compatibility improvements (regex fixes, newline handling) -- Roo modes configuration -- Support for multiple CLI tools simultaneously - -### Expansion Ecosystem - -- 2D Unity Game Development expansion pack -- Improved expansion pack documentation -- Better isolated expansion pack installations - -[View v4.30.4 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.30.4) - -## [v4.20.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.20.0) - -**Release: June 2025 (v4.11.0 - v4.20.0)** - -Major focus on documentation quality and expanding QA agent capabilities. - -### Documentation Overhaul - -- **Workflow Diagrams**: Visual explanations of planning and development cycles -- **QA Role Expansion**: QA agent transformed into senior code reviewer -- **User Guide Refresh**: Complete rewrite with clearer explanations -- **Contributing Guidelines**: Clarified principles and contribution process - -### QA Agent Transformation - -- Elevated from simple tester to senior developer/code reviewer -- Code quality analysis and architectural feedback -- Pre-implementation review capabilities -- Integration with dev cycle for quality gates - -### IDE Ecosystem Growth - -- **Cline IDE Support**: Added configuration for Cline -- **Gemini CLI Integration**: Native Gemini CLI support -- **Expansion Pack Installation**: Automated expansion agent setup across IDEs - -### New Capabilities - -- Markdown-tree integration for document sharding -- Quality gates to prevent task completion with failures -- Enhanced brownfield workflow documentation -- Team-based agent bundling improvements - -### Developer Tools - -- Better expansion pack isolation -- Automatic rule generation for all supported IDEs -- Common files moved to shared locations -- Hardcoded dependencies removed from installer - -[View v4.20.0 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.20.0) - -## [v4.10.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.10.0) - -**Release: June 2025 (v4.3.0 - v4.10.3)** - -This release focused on making BMAD more configurable and adaptable to different project structures. - -### Configuration System - -- **Optional Core Config**: Document sharding and core configuration made optional -- **Flexible File Resolution**: Support for non-standard document structures -- **Debug Logging**: Configurable debug mode for agent troubleshooting -- **Fast Update Mode**: Quick updates without breaking customizations - -### Agent Improvements - -- Clearer file resolution instructions for all agents -- Fuzzy task resolution for better agent autonomy -- Web orchestrator knowledge base expansion -- Better handling of deviant PRD/Architecture structures - -### Installation Enhancements - -- V4 early detection for improved update flow -- Prevented double installation during updates -- Better handling of YAML manifest files -- Expansion pack dependencies properly included - -### Bug Fixes - -- SM agent file resolution issues -- Installer upgrade path corrections -- Bundle build improvements -- Template formatting fixes - -[View v4.10.3 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.10.3) - -## [v4.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.0.0) - -**Release: June 20, 2025 (v4.0.0 - v4.2.0)** - -Version 4 represented a complete architectural overhaul, transforming BMAD from a collection of prompts into a professional, distributable framework. - -### Framework Transformation - -- **NPM Package**: Professional distribution and simple installation via `npx bmad-method install` -- **Modular Architecture**: Move to `.bmad-core` hidden folder structure -- **Multi-IDE Support**: Unified support for Claude Code, Cursor, Roo, Windsurf, and many more -- **Schema Standardization**: YAML-based agent and team definitions -- **Automated Installation**: One-command setup with upgrade detection - -### Agent System Overhaul - -- Agent team workflows (fullstack, no-ui, all agents) -- Web bundle generation for platform-agnostic deployment -- Task-based architecture (separate task definitions from agents) -- IDE-specific agent activation (slash commands for Claude Code, rules for Cursor, etc.) - -### New Capabilities - -- Brownfield project support (existing codebases) -- Greenfield project workflows (new projects) -- Expansion pack architecture for domain specialization -- Document sharding for better context management -- Automatic semantic versioning and releases - -### Developer Experience - -- Automatic upgrade path from v3 to v4 -- Backup creation for user customizations -- VSCode settings and markdown linting -- Comprehensive documentation restructure - -[View v4.2.0 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.2.0) - -## [v3.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v3.0.0) - -**Release: May 20, 2025** - -Version 3 introduced the revolutionary orchestrator concept, creating a unified agent experience. - -### Major Features - -- **BMad Orchestrator**: Uber-agent that orchestrates all specialized agents -- **Web-First Approach**: Streamlined web setup with pre-compiled agent bundles -- **Simplified Onboarding**: Complete setup in minutes with clear quick-start guide -- **Build System**: Scripts to compile web agents from modular components - -### Architecture Changes - -- Consolidated agent system with centralized orchestration -- Web build sample folder with ready-to-deploy configurations -- Improved documentation structure with visual setup guides -- Better separation between web and IDE workflows - -### New Capabilities - -- Single agent interface (`/help` command system) -- Brainstorming and ideation support -- Integrated method explanation within the agent itself -- Cross-platform consistency (Gemini Gems, Custom GPTs) - -[View V3 Branch](https://github.com/bmad-code-org/BMAD-METHOD/tree/V3) - -## [v2.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v2.0.0) - -**Release: April 17, 2025** - -Version 2 addressed the major shortcomings of V1 by introducing separation of concerns and quality validation mechanisms. - -### Major Improvements - -- **Template Separation**: Templates decoupled from agent definitions for greater flexibility -- **Quality Checklists**: Advanced elicitation checklists to validate document quality -- **Web Agent Discovery**: Recognition of Gemini Gems and Custom GPTs power for structured planning -- **Granular Web Agents**: Simplified, clearly-defined agent roles optimized for web platforms -- **Installer**: A project installer that copied the correct files to a folder at the destination - -### Key Features - -- Separated template files from agent personas -- Introduced forced validation rounds through checklists -- Cost-effective structured planning workflow using web platforms -- Self-contained agent personas with external template references - -### Known Issues - -- Duplicate templates/checklists for web vs IDE versions -- Manual export/import workflow between agents -- Creating each web agent separately was tedious - -[View V2 Branch](https://github.com/bmad-code-org/BMAD-METHOD/tree/V2) - -## [v1.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v1.0.0) - -**Initial Release: April 6, 2025** - -The original BMAD Method was a tech demo showcasing how different custom agile personas could be used to build out artifacts for planning and executing complex applications from scratch. This initial version established the foundation of the AI-driven agile development approach. - -### Key Features - -- Introduction of specialized AI agent personas (PM, Architect, Developer, etc.) -- Template-based document generation for planning artifacts -- Emphasis on planning MVP scope with sufficient detail to guide developer agents -- Hard-coded custom mode prompts integrated directly into agent configurations -- The OG of Context Engineering in a structured way - -### Limitations - -- Limited customization options -- Web usage was complicated and not well-documented -- Rigid scope and purpose with templates coupled to agents -- Not optimized for IDE integration - -[View V1 Branch](https://github.com/bmad-code-org/BMAD-METHOD/tree/V1) - -## Installation - -```bash -npx bmad-method -``` - -For detailed release notes, see the [GitHub releases page](https://github.com/bmad-code-org/BMAD-METHOD/releases). diff --git a/CNAME b/CNAME deleted file mode 100644 index 99cd1ce5f..000000000 --- a/CNAME +++ /dev/null @@ -1 +0,0 @@ -docs.bmad-method.org \ No newline at end of file diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index d9c12655f..000000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,176 +0,0 @@ -# Contributing to BMad - -Thank you for considering contributing! We believe in **Human Amplification, Not Replacement** — bringing out the best thinking in both humans and AI through guided collaboration. - -💬 **Discord**: [Join our community](https://discord.gg/gk8jAdXWmj) for real-time discussions, questions, and collaboration. - ---- - -## Our Philosophy - -BMad strengthens human-AI collaboration through specialized agents and guided workflows. Every contribution should answer: **"Does this make humans and AI better together?"** - -**✅ What we welcome:** -- Enhanced collaboration patterns and workflows -- Improved agent personas and prompts -- Domain-specific modules leveraging BMad Core -- Better planning and context continuity - -**❌ What doesn't fit:** -- Purely automated solutions that sideline humans -- Complexity that creates barriers to adoption -- Features that fragment BMad Core's foundation - ---- - -## Reporting Issues - -**ALL bug reports and feature requests MUST go through GitHub Issues.** - -### Before Creating an Issue - -1. **Search existing issues** — Use the GitHub issue search to check if your bug or feature has already been reported -2. **Search closed issues** — Your issue may have been fixed or addressed previously -3. **Check discussions** — Some conversations happen in [GitHub Discussions](https://github.com/bmad-code-org/BMAD-METHOD/discussions) - -### Bug Reports - -After searching, if the bug is unreported, use the [bug report template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=bug_report.md) and include: - -- Clear description of the problem -- Steps to reproduce -- Expected vs actual behavior -- Your environment (model, IDE, BMad version) -- Screenshots or error messages if applicable - -### Feature Requests - -After searching, use the [feature request template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=feature_request.md) and explain: - -- What the feature is -- Why it would benefit the BMad community -- How it strengthens human-AI collaboration - -**For community modules**, review [TRADEMARK.md](TRADEMARK.md) for proper naming conventions (e.g., "My Module (BMad Community Module)"). - ---- - -## Before Starting Work - -⚠️ **Required before submitting PRs:** - -| Work Type | Requirement | -| ------------- | ---------------------------------------------- | -| Bug fix | An open issue (create one if it doesn't exist) | -| Feature | An open feature request issue | -| Large changes | Discussion via issue first | - -**Why?** This prevents wasted effort on work that may not align with project direction. - ---- - -## Pull Request Guidelines - -### Target Branch - -Submit PRs to the `main` branch. We use [trunk-based development](https://trunkbaseddevelopment.com/branch-for-release/): `main` is the trunk where all work lands, and stable release branches receive only cherry-picked fixes. - -### PR Size - -- **Ideal**: 200-400 lines of code changes -- **Maximum**: 800 lines (excluding generated files) -- **One feature/fix per PR** - -If your change exceeds 800 lines, break it into smaller PRs that can be reviewed independently. - -### New to Pull Requests? - -1. **Fork** the repository -2. **Clone** your fork: `git clone https://github.com/YOUR-USERNAME/bmad-method.git` -3. **Create a branch**: `git checkout -b fix/description` or `git checkout -b feature/description` -4. **Make changes** — keep them focused -5. **Commit**: `git commit -m "fix: correct typo in README"` -6. **Push**: `git push origin fix/description` -7. **Open PR** from your fork on GitHub - -### PR Description Template - -```markdown -## What -[1-2 sentences describing WHAT changed] - -## Why -[1-2 sentences explaining WHY this change is needed] -Fixes #[issue number] - -## How -- [2-3 bullets listing HOW you implemented it] -- - -## Testing -[1-2 sentences on how you tested this] -``` - -**Keep it under 200 words.** - -### Commit Messages - -Use conventional commits: - -- `feat:` New feature -- `fix:` Bug fix -- `docs:` Documentation only -- `refactor:` Code change (no bug/feature) -- `test:` Adding tests -- `chore:` Build/tools changes - -Keep messages under 72 characters. Each commit = one logical change. - ---- - -## What Makes a Good PR? - -| ✅ Do | ❌ Don't | -| --------------------------- | ---------------------------- | -| Change one thing per PR | Mix unrelated changes | -| Clear title and description | Vague or missing explanation | -| Reference related issues | Reformat entire files | -| Small, focused commits | Copy your whole project | -| Work on a branch | Work directly on `main` | - ---- - -## Prompt & Agent Guidelines - -- Keep dev agents lean — focus on coding context, not documentation -- Web/planning agents can be larger with complex tasks -- Everything is natural language (markdown) — no code in core framework -- Use BMad modules for domain-specific features -- Validate YAML schemas: `npm run validate:schemas` -- Validate file references: `npm run validate:refs` - -### File-Pattern-to-Validator Mapping - -| File Pattern | Validator | Extraction Function | -| ------------ | --------- | ------------------- | -| `*.yaml`, `*.yml` | `validate-file-refs.js` | `extractYamlRefs` | -| `*.md`, `*.xml` | `validate-file-refs.js` | `extractMarkdownRefs` | -| `*.csv` | `validate-file-refs.js` | `extractCsvRefs` | - ---- - -## Need Help? - -- 💬 **Discord**: [Join the community](https://discord.gg/gk8jAdXWmj) -- 🐛 **Bugs**: Use the [bug report template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=bug_report.md) -- 💡 **Features**: Use the [feature request template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=feature_request.md) - ---- - -## Code of Conduct - -By participating, you agree to abide by our [Code of Conduct](.github/CODE_OF_CONDUCT.md). - -## License - -By contributing, your contributions are licensed under the same MIT License. See [CONTRIBUTORS.md](CONTRIBUTORS.md) for contributor attribution. diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md deleted file mode 100644 index f36cc81fb..000000000 --- a/CONTRIBUTORS.md +++ /dev/null @@ -1,32 +0,0 @@ -# Contributors - -BMad Core, BMad Method and BMad and Community BMad Modules are made possible by contributions from our community. We gratefully acknowledge everyone who has helped improve this project. - -## How We Credit Contributors - -- **Git history** — Every contribution is preserved in the project's commit history -- **Contributors badge** — See the dynamic contributors list on our [README](README.md) -- **GitHub contributors graph** — Visual representation at - -## Becoming a Contributor - -Anyone who submits a pull request that is merged becomes a contributor. Contributions include: - -- Bug fixes -- New features or workflows -- Documentation improvements -- Bug reports and issue triaging -- Code reviews -- Helping others in discussions - -There are no minimum contribution requirements — whether it's a one-character typo fix or a major feature, we value all contributions. - -## Copyright - -The BMad Method project is copyrighted by BMad Code, LLC. Individual contributions are licensed under the same MIT License as the project. Contributors retain authorship credit through Git history and the contributors graph. - ---- - -**Thank you to everyone who has helped make BMad Method better!** - -For contribution guidelines, see [CONTRIBUTING.md](CONTRIBUTING.md). diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 557212d30..000000000 --- a/LICENSE +++ /dev/null @@ -1,30 +0,0 @@ -MIT License - -Copyright (c) 2025 BMad Code, LLC - -This project incorporates contributions from the open source community. -See [CONTRIBUTORS.md](CONTRIBUTORS.md) for contributor attribution. - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. - -TRADEMARK NOTICE: -BMad™, BMad Method™, and BMad Core™ are trademarks of BMad Code, LLC, covering all -casings and variations (including BMAD, bmad, BMadMethod, BMAD-METHOD, etc.). The use of -these trademarks in this software does not grant any rights to use the trademarks -for any other purpose. See [TRADEMARK.md](TRADEMARK.md) for detailed guidelines. diff --git a/README.md b/README.md deleted file mode 100644 index d4827e378..000000000 --- a/README.md +++ /dev/null @@ -1,109 +0,0 @@ -![BMad Method](banner-bmad-method.png) - -[![Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=version)](https://www.npmjs.com/package/bmad-method) -[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) -[![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org) -[![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj) - -**Build More Architect Dreams** — An AI-driven agile development module for the BMad Method Module Ecosystem, the best and most comprehensive Agile AI Driven Development framework that has true scale-adaptive intelligence that adjusts from bug fixes to enterprise systems. - -**100% free and open source.** No paywalls. No gated content. No gated Discord. We believe in empowering everyone, not just those who can pay for a gated community or courses. - -## Why the BMad Method? - -Traditional AI tools do the thinking for you, producing average results. BMad agents and facilitated workflows act as expert collaborators who guide you through a structured process to bring out your best thinking in partnership with the AI. - -- **AI Intelligent Help** — Ask `/bmad-help` anytime for guidance on what's next -- **Scale-Domain-Adaptive** — Automatically adjusts planning depth based on project complexity -- **Structured Workflows** — Grounded in agile best practices across analysis, planning, architecture, and implementation -- **Specialized Agents** — 12+ domain experts (PM, Architect, Developer, UX, Scrum Master, and more) -- **Party Mode** — Bring multiple agent personas into one session to collaborate and discuss -- **Complete Lifecycle** — From brainstorming to deployment - -[Learn more at **docs.bmad-method.org**](https://docs.bmad-method.org) - ---- - -## 🚀 What's Next for BMad? - -**V6 is here and we're just getting started!** The BMad Method is evolving rapidly with optimizations including Cross Platform Agent Team and Sub Agent inclusion, Skills Architecture, BMad Builder v1, Dev Loop Automation, and so much more in the works. - -**[📍 Check out the complete Roadmap →](https://docs.bmad-method.org/roadmap/)** - ---- - -## Quick Start - -**Prerequisites**: [Node.js](https://nodejs.org) v20+ - -```bash -npx bmad-method install -``` - -> If you are getting a stale beta version, use: `npx bmad-method@6.0.1 install` - -Follow the installer prompts, then open your AI IDE (Claude Code, Cursor, etc.) in your project folder. - -**Non-Interactive Installation** (for CI/CD): - -```bash -npx bmad-method install --directory /path/to/project --modules bmm --tools claude-code --yes -``` - -[See all installation options](https://docs.bmad-method.org/how-to/non-interactive-installation/) - -> **Not sure what to do?** Run `/bmad-help` — it tells you exactly what's next and what's optional. You can also ask questions like `/bmad-help I just finished the architecture, what do I do next?` - -## Modules - -BMad Method extends with official modules for specialized domains. Available during installation or anytime after. - -| Module | Purpose | -| ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | -| **[BMad Method (BMM)](https://github.com/bmad-code-org/BMAD-METHOD)** | Core framework with 34+ workflows | -| **[BMad Builder (BMB)](https://github.com/bmad-code-org/bmad-builder)** | Create custom BMad agents and workflows | -| **[Test Architect (TEA)](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise)** | Risk-based test strategy and automation | -| **[Game Dev Studio (BMGD)](https://github.com/bmad-code-org/bmad-module-game-dev-studio)** | Game development workflows (Unity, Unreal, Godot) | -| **[Creative Intelligence Suite (CIS)](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite)** | Innovation, brainstorming, design thinking | - -## Documentation - -[BMad Method Docs Site](https://docs.bmad-method.org) — Tutorials, guides, concepts, and reference - -**Quick links:** -- [Getting Started Tutorial](https://docs.bmad-method.org/tutorials/getting-started/) -- [Upgrading from Previous Versions](https://docs.bmad-method.org/how-to/upgrade-to-v6/) -- [Test Architect Documentation](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/) - - -## Community - -- [Discord](https://discord.gg/gk8jAdXWmj) — Get help, share ideas, collaborate -- [Subscribe on YouTube](https://www.youtube.com/@BMadCode) — Tutorials, master class, and podcast (launching Feb 2025) -- [GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues) — Bug reports and feature requests -- [Discussions](https://github.com/bmad-code-org/BMAD-METHOD/discussions) — Community conversations - -## Support BMad - -BMad is free for everyone — and always will be. If you'd like to support development: - -- ⭐ Please click the star project icon near the top right of this page -- ☕ [Buy Me a Coffee](https://buymeacoffee.com/bmad) — Fuel the development -- 🏢 Corporate sponsorship — DM on Discord -- 🎤 Speaking & Media — Available for conferences, podcasts, interviews (BM on Discord) - -## Contributing - -We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines. - -## License - -MIT License — see [LICENSE](LICENSE) for details. - ---- - -**BMad** and **BMAD-METHOD** are trademarks of BMad Code, LLC. See [TRADEMARK.md](TRADEMARK.md) for details. - -[![Contributors](https://contrib.rocks/image?repo=bmad-code-org/BMAD-METHOD)](https://github.com/bmad-code-org/BMAD-METHOD/graphs/contributors) - -See [CONTRIBUTORS.md](CONTRIBUTORS.md) for contributor information. diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index 2c565ed1b..000000000 --- a/SECURITY.md +++ /dev/null @@ -1,85 +0,0 @@ -# Security Policy - -## Supported Versions - -We release security patches for the following versions: - -| Version | Supported | -| ------- | ------------------ | -| Latest | :white_check_mark: | -| < Latest | :x: | - -We recommend always using the latest version of BMad Method to ensure you have the most recent security updates. - -## Reporting a Vulnerability - -We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly. - -### How to Report - -**Do NOT report security vulnerabilities through public GitHub issues.** - -Instead, please report them via one of these methods: - -1. **GitHub Security Advisories** (Preferred): Use [GitHub's private vulnerability reporting](https://github.com/bmad-code-org/BMAD-METHOD/security/advisories/new) to submit a confidential report. - -2. **Discord**: Contact a maintainer directly via DM on our [Discord server](https://discord.gg/gk8jAdXWmj). - -### What to Include - -Please include as much of the following information as possible: - -- Type of vulnerability (e.g., prompt injection, path traversal, etc.) -- Full paths of source file(s) related to the vulnerability -- Step-by-step instructions to reproduce the issue -- Proof-of-concept or exploit code (if available) -- Impact assessment of the vulnerability - -### Response Timeline - -- **Initial Response**: Within 48 hours of receiving your report -- **Status Update**: Within 7 days with our assessment -- **Resolution Target**: Critical issues within 30 days; other issues within 90 days - -### What to Expect - -1. We will acknowledge receipt of your report -2. We will investigate and validate the vulnerability -3. We will work on a fix and coordinate disclosure timing with you -4. We will credit you in the security advisory (unless you prefer to remain anonymous) - -## Security Scope - -### In Scope - -- Vulnerabilities in BMad Method core framework code -- Security issues in agent definitions or workflows that could lead to unintended behavior -- Path traversal or file system access issues -- Prompt injection vulnerabilities that bypass intended agent behavior -- Supply chain vulnerabilities in dependencies - -### Out of Scope - -- Security issues in user-created custom agents or modules -- Vulnerabilities in third-party AI providers (Claude, GPT, etc.) -- Issues that require physical access to a user's machine -- Social engineering attacks -- Denial of service attacks that don't exploit a specific vulnerability - -## Security Best Practices for Users - -When using BMad Method: - -1. **Review Agent Outputs**: Always review AI-generated code before executing it -2. **Limit File Access**: Configure your AI IDE to limit file system access where possible -3. **Keep Updated**: Regularly update to the latest version -4. **Validate Dependencies**: Review any dependencies added by generated code -5. **Environment Isolation**: Consider running AI-assisted development in isolated environments - -## Acknowledgments - -We appreciate the security research community's efforts in helping keep BMad Method secure. Contributors who report valid security issues will be acknowledged in our security advisories. - ---- - -Thank you for helping keep BMad Method and our community safe. diff --git a/TRADEMARK.md b/TRADEMARK.md deleted file mode 100644 index e6ae57848..000000000 --- a/TRADEMARK.md +++ /dev/null @@ -1,55 +0,0 @@ -# Trademark Notice & Guidelines - -## Trademark Ownership - -The following names and logos are trademarks of BMad Code, LLC: - -- **BMad** (word mark, all casings: BMad, bmad, BMAD) -- **BMad Method** (word mark, includes BMadMethod, BMAD-METHOD, and all variations) -- **BMad Core** (word mark, includes BMadCore, BMAD-CORE, and all variations) -- **BMad Code** (word mark) -- BMad Method logo and visual branding -- The "Build More, Architect Dreams" tagline - -**All casings, stylings, and variations** of the above names (with or without hyphens, spaces, or specific capitalization) are covered by these trademarks. - -These trademarks are protected under trademark law and are **not** licensed under the MIT License. The MIT License applies to the software code only, not to the BMad brand identity. - -## What This Means - -You may: - -- Use the BMad software under the terms of the MIT License -- Refer to BMad to accurately describe compatibility or integration (e.g., "Compatible with BMad Method v6") -- Link to -- Fork the software and distribute your own version under a different name - -You may **not**: - -- Use "BMad" or any confusingly similar variation as your product name, service name, company name, or domain name -- Present your product as officially endorsed, approved, or certified by BMad Code, LLC when it is not, without written consent from an authorized representative of BMad Code, LLC -- Use BMad logos or branding in a way that suggests your product is an official or endorsed BMad product -- Register domain names, social media handles, or trademarks that incorporate BMad branding - -## Examples - -| Permitted | Not Permitted | -| ------------------------------------------------------ | -------------------------------------------- | -| "My workflow tool, compatible with BMad Method" | "BMadFlow" or "BMad Studio" | -| "An alternative implementation inspired by BMad" | "BMad Pro" or "BMad Enterprise" | -| "My Awesome Healthcare Module (Bmad Community Module)" | "The Official BMad Core Healthcare Module" | -| Accurately stating you use BMad as a dependency | Implying official endorsement or partnership | - -## Commercial Use - -You may sell products that incorporate or work with BMad software. However: - -- Your product must have its own distinct name and branding -- You must not use BMad trademarks in your marketing, domain names, or product identity -- You may truthfully describe technical compatibility (e.g., "Works with BMad Method") - -## Questions? - -If you have questions about trademark usage or would like to discuss official partnership or endorsement opportunities, please reach out: - -- **Email**: diff --git a/Wordmark.png b/Wordmark.png deleted file mode 100644 index b596d0bce6473ece4833526801e136971d0c667a..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 23544 zcmbSyV|OJ?ufPEH0^ zMiu}-Dm+`&RYTPkOYmjqvR@|5FRCup#vedRc1fa|QZ_^m#3l&=-vUFysG_EAKo_q7 z#jHvp`AZrR7*Mv?LM$#;Jxt4p?_DsvxFPt}Q>(u#bnTt{z<08<>%Qv*umB+;b-=6u zjiX7CCj07McesPGF+$1%LV~V=+`g_S%u)AR0Q`XZjC_0xyLjJ0sbGH8JL=V-1M4=g zKY0_WQl`M2`~?QxY~A z^r;5OVgSq)&ByBiw%`G%3`cN1dvJ_sj0rRu|IDN@WyNXASzB;+v;Lg?8!&`|c47-+ zP5;Fmn>&*TyS7y&2cy`9z2`KWn^!WILU20yx53H5v7w>09lkjew zEok{m^77`s!3w~Q23R{5GJ=}`(OLzy*m@^3Yr+Ha5akuWMEYn%xJxIGlh<%^wzs#h zkdo|bk(}PV=ED2{^gm~{?%H>c3_qX~-S6RXwDa+V=*VOlP0eN9yht|BYehe6;eNge z7fFN1Maq??uo{fT26W=NgQura;lx;#Q_>hvf2h!YOxN{q-D^Pnls`by9;$_lQ(@L- zxBZNjKxDUy?Y~@iMaEe2*19yh=VzUMU~*gDW`U6yu{O#RrM$K#?3qld$6kV}RTO*v zpc8%I@^cWP%wTkNQ0DevinqbU(18|Vq3(U5YGdFuhXbq{2oOr(nTC97K#nC50`>tz zi(q4W+?jrgHux`lJV--u!a?q?AZc*nFlYip;*2mtqbLp1XK1MO@K;h2DRR_UauS*_ z?0B-tI1VWkl>jwj&p6&g?L%ru+;+c560Ud>6Zkg__edjZ1k(cEG8n5sM}ZLT z0-941XPAswTan2*+(+V#fE)>?{I65uckJvwK%o)698u!{H#QdBAZne7TtsyrY`sbq zr1j87J>w-UXP7|$&K@*3WK4A9K>I$ZeWQcdmdFJ0P=K#AF|r1@Y5*IFAF`qp89jv!`6W3!iUP_z z^k5JSX?&S<6L|;PU>JWvlm?KVijX{qT#qCMSwFFiTp&SUJT?i4ns_f&T;#C;vw*Qc zZJAId!b#bgFgON!Z{*0*p0cHIO%WSMMN@&U8o@`AkszTdPgBUQGNW>>l%ra%237&b z5kOl|Q;?#Jq&%w{T4rZq#SVv?nj)3B$T|PKs4#E4kh6H^jMhOV;LliSSFk!iJ9jg$ zPsfr}l?<8;E<=}0o2->oLoM)&k`9l~lV(;`uRy25ORQb}EgV*JSS+}5KvgqerQA{N zsAD3CR&-f`LyklBZ=qH9ImB|Pl^6#ahdzhDR?miBGn>^Qe3aqX9_woqN0iox<_L6R zAG;|e>tdStlwF#@l*3<+r?YdG^T;K-<=9H32IdqPy13+iS~CJOgt{Gt`SgDr;@qZ# zNh37sC0z??75n8ROVmpi3#Y4YmE$Xq%W|t*1?v^=>Tso|`55`hmCdpjRV#_*Q{}d* zZ>n&mggG9vc*`wwF-v+C-Rhm%o+6U!qxzBssx?j$C*h2;tEyb`u9?>`+bjYhJ8}Z? zJDlB#9pEHVwXtvxptrWwZ=XKS{v)ji=nd%TOkIG{QLa|dNY zIYZ4C8A{8EvMGUc*ff&-graDVNPrgvt0W--8!qB zd5-T#mdAe`d#pWSanZFpw|caOvdNi4n=j2^yKvc`wBI-oWsT>gvpc;^2_tzUIfPn)h=JmPVn8~FFM*JRPzT>ds)vpbX$mdK7tYrf zy_sUop~zXrg*5ax)E>MJ$qZqF{}Bv8Mj=$jxg%a+bksCaM<=uLQS)A!w75C_ce>d) zZ8mA{Iz&B6KC(3274a0#5Ka))7_Lp|N~1@ohrXKvlnawyOJ!ymb)9+UAq$TQhX@CA zl0RY0@HEU>>56h6J)xUDnHEY2QjCzVQ1lpuJ6OJ@!~|z7(_)@Exp%!Kg5!tS1UD9O zH4L|BUl(X6e>05moLEV!SBqU*SfV1WDHD05XCSWTz53;$@&5f7i&KvypI$UoG*xKC z;n2~>Cd*~5{5y9@MTHng=d{EAW5B_(&RL%`L4d1Mek4iSWZRMLP3ui*W-4nUYqg!F zT@tgL5tZp&&!*mO@ZUUzk8F=#g!Y8~M!lTx`njp-WOvGqrhk=2U4e1&{={c8S>>lX zfrh+hcF%h#|7KT07nZfrYSYQZVeJHw-bHUqKCm39W$&H6*>V2V_EhjBfQQeSWcR8> zP2HtoqOGR&XiMgMFkE}tL;G=lP;w|QFsv}#$%)1p$%SNdx8|59)@&j@e!DVP&9J$) z3ESGeCg}SSyl_^$%ty_4$OkzoGO;lcJ;9aQTPan2TKiaIQ?XF9q4Z=`YH*UQo70I~ z`L`mnV)q*Js;7R`S5Y=vTK-ILU?-~^$;#NOv**}Lw^h+vf4=ACWB3CKNsREc%BiNZ zas|^pA|Oz7_JFd-4Gl)N-2 zOMypVi>3GAIlYZ-m6wdya|SY3z<1_mE1j{nCh=r@mZ)>jWB*iqW_U$bAyun`pfl6g z{xiRQw7j%$N-P(VZ@oDz_1}{y({=nnkQ$Jn+9+I8e zmX{0N$;#o?FV|aF*qe$ihVD}D+GEKFqD;ta$XKK|_`kcc9loAvLZ7dtm$^I9heCNm z)C9|T)t(kVw`*y;Ye$k!gwgyd{5f7Kw~gnszZ9o)d|o0?n6?ib4#;MUW(B`H?%IzZ zzL-jSPt%}t+g?~7jt(maRx@gmy7s%yJn%kToLOH8?sV5ZA6~AA0))2S(%$Y4>|TN% zK8DM}MgDUpVeF+eod5t#ivJlP(kkS)0D!WIw3x7(Th^5~R2I7U^Up<27hfY^V34`2miCz-$mUvJ-#TZaNt4vAsFB!Z08rjFglb8k(Ly^Wczw@#{xT zQGnjV(}n7a@%HBCWRV`Pq_g9E*|S#fP)r#dgI29fDPLrG2cf4IDo-RB_J0^-_!U6) z{Qo7MLCQdN|Bt%{l?UtmfAU5|ezbGH{%2!wgg4;-SJ;B>jd|2z9WVTU4_#C5r+5`w zAyl`Hqa$8kxWs{R#^F95xM_s(ViSJ$wu?@tVDIukyG&~nOat?xv@SohogSi}6{nq5 zfbj0N?QUQ3miCPMmv-y<=IzlTY3EO%YIm3COq|h;=Z1yR85Tw_^ZHK9s0ABoUML&0fxP11YKvI)E} zlOx7cmE)w$igfmyHCbht&!~6GIcxMx)Elz32rf?i-f+8bHrvgHh|yN?>=yPNGdXH1 zWv49u@&i>1PkEmx4n06dKkg7pf^*Sv+!%E4f0J=e3p1_zzRY-TYHb`>Uvnj!T^b+B zi=Pip+k2a*pBH2*oV-5f|5fJ|k}S@0eDZIHc5d7o9$;X?s2d`ekqysd95WY5@0Ru^ zq+nJME=IZv<`*8b2<$Zt+@F*>qrRlmcwN+*mBUIdL{}XVBCx zgi(*}kneIl{gKYLWRK}?!HZs;RN7!@{}}>71*DRMj)sW7yRK;g50o{%+3Y1;xTMe2 zv!@db)~I`6XPMQSg!zL+>WoROHx&G3Zt{9w+aQ@pNA<)61kQ0HpZd=B(1UNa`LKL^~m-bd^ttRHA+aPD||uODj9^i=<& zHi_Wq$N{1-DwqVO?_KWx0{ec$w121b)vOCXXWz>K{h9wbj1LwSfO; zCRSeee0nybl=0!ywkzj;5%|TyVI)>KCfcZEdK((uLowqc8h;eZRbsv`@y4;eXy@xO zw}`WU53pvGF(eAva%gf-?OGBbct9@loE9S(!NNjgawqjv|L61x+#;}Nc9=)a-|spm z34{~OYiKa6nLD5}o#8R15jDQt{aT5;$#YLNiRsS`hMERAz0onFQmX-~X>d8$?feq; z!>VMg3VcT(MnqFoaPcV6z>}Fl==q+OA!2Uc5|N3*fk#iWV!qRm(PBC7y*k(O6EwH7G* zZY3O7)$}1PHP2sl=CpH~jgaYWYiDRqNFSrw?>K*>_X^-r&cL{p4@pUZdF}G{UwUZP zn{Dz{`p@3>o=(~(P^MGEk5&+Vh`jMW5^Sg#3MKWb3S$DVxerlncp2ca#CR8dGCd~! zvin?EU5DRX05w*zn4qMy&U)OUY*?@Q=d8Vl$4_B|f;_S{Qn zae}11Zp$n|c2<#C1#a4tywV#Ez2&WuP6*-Cdp$@2^EnG*)&sj8D$eB~m$_;G<2p5L zu2oZnkrTrE+0JOTi%f9WkVn#NBe8fmanb_23&eaURrxCS?Glac*bC6+Z@)FE)ta=K z=0H|hu3{23P)(0B1pgRV{Ff!Ki()FmK_Xgx>p&2AekuvGojqS0Rr#`<7_QA4&?d~o z`Hu(V5S$4;clwtQrKE#FLzMK~pnkBt*K+ZJ2B=(@9;x)+%pFk!bTHK%abxcf{gldx zs|=M`b@Ipc3u@ZEhm}7OS8aP*qrInYI=-Dl9`gvPR*E~n>6(B-`D-)lKJUM_n7=}1 z%*z+V_Jlrxi*>r`|r6y#b)r!Axy4FH-FmqB|jl#^@QEe5gKKtrhP6_8_rT&Zu8kisV@4!Lmz-3(K6Ed`6Yh zcp=`r!^Lzv6#}1++Yz(n25LTR%~sp~+J!B`pFENIVVepyb_Ik+NM^UN71r0ZFWTf) zVsE)5J!JqgAFzzYqgRvS`+er$*ts~-tGb8xfJ?_dbfQJE95e)9rMNkoYIS3Z&#K)?77v>qC@;?IC(EZT%h&H&DtRURJEL;R=uHzXxBQ3te2ZTDe|+~# zFbS-xBO0-}{I~#fq=2CJbdBEhAFrFnvGdej zxEdSFSep`0Z)yRH7S;d)B;U@NP1Ea5U8}^zeSmj#e#I)1}jY2)YbCE&gSTQEvr>&Sb zwbKsM<4-x#DF;>b0;KbJC?|92Oxsc@AlYUok1(KrHhtXX!!|^g=}L=QIcH>0%TpOpIxDu8ZZEoRGh6>G&<$j*D7V3YU_~!gda%h03-_}6f0>f?En=04}#n`W&;?M{mKS%=wSRxq$mrAjPfvFmBGNQylsv9UxN z64DJE0J0ZA0)#e}2K#f1CFO#s-Fx(ntp+XU`;=}Mb;317g$upoH|RF>UjZCfYHBfJ z6{x*Kz`%NntWlQ!CdWwN?3mE)9$OTY;H%Oi#gC`#>-$LP*NyEK=6CwN_JH|04jpU9 zM}tekxLKVP=i(A-AQ}j`d=~e`HsI+mVE8yo5(}~W{^RG6Y3{Bw$PGgvxPF5n^-*J- zN{eql$#O;7JjY5f1ermg*mzE>14Jl`-XeIb@vH@}N;Nc^4hQCGre?rv)$;*4QaTw@ zLn33sNf~U^fcuA|(TNgN9US@8e{6FgPE}LGZ9QtMupDMw0Rs#^PsS9#Tan46XY7iM zAIKM+p)?cmu@7rSNhMn^^-sJv39;%O+ z_0o%VPq<*^0x^Y^~;jZM#5k zh^N_KY?MPg$mip;D9Y#OI?T>G`?q{{&DjdmQNyefeWlW1*vQh?tL!h77fbn2>ymLN zG_;B1q8P^?lxut2s2z$KqtVRpe}1-mPRA^lp+sfLfZ1F#u@t7faK!xKSv%pw4b>PW zI;^K@D^KFJ@YQpvDqQP8nL$j6Gx0~oE0FtZldT$ytXXbj`yB*PO3xO|F3x@AMQ#rf zrcwvZ^h;CmM{iyzmh^`#6BUrawXfn6fV0<@^9I2fIO@7~F99OHzToq)FQ$%6bH0dK zy((4@s_NgtzWQO&n{4Y3Hi6lefq8#oYUwZRDv6uKCERAbDpcZ}sfJ>jNUSd?M$Y>JUw2 zt4N_*ys&lW@Uk`SK0+X@H@4;;j=hF>%f9k0?55YI|Vx*(kXm`KS^* zGjPNFr-#7MwG-?)P*jQ5#pc__Guq5hX`~irn*q(!0I>Tuq?BL$&fiHTn>+7IKM2b? zETRF`pv$eq#x~KQ@YEav&b`cEvsf*=qUk_kTo6Z_PjK4AC#0=JR}6IY3`6tT$596_ z7jzHS>f+ykYDU>bEoc$V2V2VHvgoZ&&^*#~05yUiHi*UjNN6E>+F08#HZYwh*a6GG zr3(aX>RrFD2yw;Ews4^9ATIv>OHkYP1L`yif5`=4(HyQHd+X*%O}7NFpja7Ps_*Az z8cMu`v_Kj*hD|!wZ>YNiG*|ci+Kk?Q$+DgBM6ze|`1 zGvJWhs}FuF4lvr*pctDS@2PkKMaSC@UxnO_v#yyJysf&K2KS=uaD{mU;s1OuuY0Ph z)Iq{Ld@!s2oj@tmBOZSUi4AXn&qHpJ>&7kg90lhT69U2mS>`kp9Os2P{!)Vt)WhL= zC^((3v_t$Hc*XC`?;uaJ`kVhf4@I`9n2p(yX;|Tp4o8r8v!F1F?sn*d3SA0y`_U<6 zCyggMhy$MhRHvPai%N-}waw+&_LAsF)(&P*^-5S2;na#mL(I(+GFf=t0!yKPsveed z#|_R{1|Y$hfrt=@+-}ZhXS(a{x%X6xphfyyutq2;lb&B;Ml-b1{supKer4%90N6v{ z)zkgq9f)#y2Z6-ioBlc4))!J}yWec?mv?TgFSq$pnNT)@{8Mc|0&$!;<3;wm+>7Pe zTZ##;R*(P_msmO_J#lyl(;k}5x9M!=)Os?$mgVra%zD)er@M)a7a5MR82c62`c{lsv^ z5;{JX__f3kaiw>mcwwB`a7A@RM!h^9w&uihQJTAP4WV0ejAWP-rVj(a2-*g?`B>WN zcG0)FY*W^^45B!7@EZ-Kl+I&e+_pFrzWOJQN+K~w(>KcASI=i_)RWFuUIBFfmcJz` zw!e{$aOx9;$2KP^JJxF%+%sE9<15>|b>>X>*J00F4>Mk1M1q_?1!yS4^LC0S=Bkrm zifZ;qWE22B`F~4FGfE#&@-YGoV*9>k)pWIYb#{ABMQ_xXa%0w2(^DR(@J9Zn+saT=8$!>h!GL6icw<$gxSmQ{=eC7WAB z;I;z~rrz1^FIbPS_o=Yd)_xM|K<0Ukt<~Jiq@@ON zHP=mf^p~8abTRL~iUU**)M6g3cYi$8Fr+Sbu+U?XQ(Vrd z>-_m>T)0#NPY++S-yJ+{3D*$lglD7@yR~UMm9OE!HL*Dw&~`3^2WukAISC@!-Il+0 zGIjh{BtCO=M+v}~Z|#S#dVFg%i8K_984mmXWeyhRMa9!%>V3Dk#sjO@{qHb2Cn~kE z80otj4S)_XOPmy#$Ma>*xDbgLoQ#%lS0zv)b_{yQ`jcwdVh^mDDmJ;C;@qeCn~x_* z{2gAF3O>FUn>5@%z>_zfzVCtd*kPGoM&kcSi?^GZxJ zDf($b#&e&>uaZVW7hu`@W%#?pNe&%8)UV|BJxVC(-upI~*qboWw65E8Ja;EwT(p|6 zKc3kC-L!+o67KPvIvhGlDdJ4pe`Art(2oL@1%#;bcYH6w{v*tjq}*9oi)nNv2yHSf zx)L~Poj!!R&Ge#1`cmvv0YN%|hx9rPz|*2;#_B_T&zMh|S@OBV=bS3lo<3gk0yA`( z+E8Vpcyh?T{dS@{4He5hzzUfWpxZ2+6PTC#a9M`YD#93Eh1EeTH^a$&MSnHKLMA_W zrnR27b-0s91K&4zU*s-VZQoU74hIU}x*TGS^|kqMcQ~ojih)_rrNgNPiUwP35AV4A}~NxRHN@_jbG&iov=+Tr7LbVR?#iJZqRm5PPX^j zM!ClXocgl}>_iZ$M4B;(F|W;-JpcO>LrQa}I~I_PPO4bAbJ(D1@OuM1g67Veo0KxF`08vgt$sVRZf%dD~NLN zv2hOF0Wn^}o>AUuwckd8Axafz1m$U)@#)5vdId^hzTM;}*w8SB!k!;)NPrk!Lf z4%fR|t=Z0Q57T>aA4StE1c~;X1DDp1=0v8_#&iUhR5_C0_6tzFSHj?Ft#E-`{^hAN%oDI=2U6>JVv6DR2+&*!YMTOsDu*p`Dc_RG<{^c zLrVw&pMmDYs>BUwo($v2>q_L1W;ylB)@GbPz5TRKehPKJ-)J{@@w*1r>u%d|Uy^#F zP$-p#OBhPWk&vsnNJ?FNwVvs|RlFjcYeALPXZVLp39>VgHR9^gi7fRKS?9UbAzOWf z*GsT$1|%$eLM}jwcx~_a!bvgzF$6))LsnCoA%(2A?{yEXeJEhBWD4#AgnF6}4?1+h zk*xLea&kiuP1#kbgoF9)-$u>NwT7RSlPKCmDI_eGH5 zuS&Buu-LsTc9Z`Yg-JV9*TvjntCHU8*4Ix&a9LL_tAK>1#gq``^2$8oe3lShO|J4x;E0XoXd2E&c(UNklIdC!R^(|`g zwxrtCDiwdrnb1?hY#M~b;X05%dP3keLUSy7rnS+aL={x{Vr8Rq6Rz{Y)F5^Bt zwrfS!i-fo7;4o+x<54!F=;am{!6m+zav@jBlFgaCaPy4oKLg9}-n${Tn|LQtg{j9h z-x_D|N=fj!1Ac|5J~d2@m=5=MKy4G;Pbc$w9_qnd$w{k+-aAs!phaW^&+}Cf71|u+ zmVC|`O_&V%h!JCC5K<)G;k~A3ja|9Gy%?0#7*5HOJ}lrnCdJ`7p$l_<~sx%wx5TDA1;M8?G6Iz-xycdu&k z?Jf`sFNB%0UT%ZY49di&I@^B4om1uV)M5f24P(`SZop7Ub+leGZDhJj%a_x+rKC#E zs(B$O-zd4-y-z05ruH(2@l!jh+i-K*$d&DKCAg`;*^sMNBZ7qnbTL0lAc}fBw|Y0b z!cHykCSpQ^RUJe%nSR>?qbgHDWr3+j$~Ay}IGmnW>^7t7_T>UJw&qnjA{JMo8qETx z-{YA3L~#A{uabvEfA6ku@1yVEU7ef8IQ1lMdtKBh-Zr-m2YzpLHMg~|46BDSY_^u1 zS2;WaI|KsH=FdmB5a4U~zVWI%#eA!M!XbDmK<5PlT2Sh?13(510f?mVU%Y?8PALoaI+dxFHwfEY5&pnX_oB;^D$WK7F;%P5lp8>Kw8`INQ}@ z!ooX8vOMPN?l{6hY_h~%eZ^!W^PQfA1)JXL zzVPi-ezcorqW>gFF?(zpp5NJ9n6~$1%y?2l!5y;6Tugq$Z?bxpXIYxlBmBZ^4Q}1? zFhA5csH4;arRn3wni10V#qQQ0@hTBYN0Ug;D9<&8UOpe=NYWcTo1Hv8{Bpj3-J-$z z8n*8c(+MxIAc3~?LVnMIRr6iJvz3zLkOMtrTycN_JJi^vc+;h43Z?VfLmZ?)-7ZPr zN)DJ*)sq@=U!U4K$nVQ3#2=PDo`#t1MbU}~AjU@5((|Tzr?7zSfE<+$HWN{*@BMpw zdG;1cgPw85u#xbAknA_#DC~i1&wRX`0QEEbg3{Cq)t_O|D;vNFN`+szo!bKksrRIB zkVT(jdc-^z@A`zg0*wTDdQx(xWH6wJkclW%MEDg&N51K^C49z(P{kJObSN!3x z8S0Pn47&J`h3H!85XALfc?=e-f7OKn0nA+*sIy@z;w?ED!K!DRRIKeM*xaWA`)*$r zW7DhB?yC`sF%Kc5ISAfk(1T_rDAKGeF#K+Br?2CkPAq_%fD8Xf}+%goHL?WR5G~Ma?%qyIgR4x;UMwqfjPF42)alBd6f=Ejnj&)~n zNPv=3mSNku%GEd%Lx8E=Ad+h>Mus%P9mvS)fVkpCVCx^GE1gfF z#RgTgHLAeLYMoi)Lw`|;2hr$uFT*)1Hyp!xE*a($B-9|29$T%;)0xcX#vQlqI->^{ zm1B7=HaUXBG|XnPHSs@~J+I%L&W*y(3;6oSn&dge`glweXwaqlfqW3B&JO+gtFrC( z_=!Ck^hMw^7HZ^g{n>JMR_>FB-AINgQ69_+ytJ+bqf8-FJSz4~#n5*d4>b zrec7WLjAtN3#IF21*U*wmdg-PuS(jA2!b1DJMQjJ?T>jyT0KLRswHXAgkLUCHCFFK zzVDN9t7}_-#bn~EaVl3#V`t&WSxEPH$|F5`MEOZ!DHK02FWEn9`1{^Z4o zhFPH0Ys~<=Gc2>4n9bZR%Ex)eRPB?aLqFlko0KhD z`5tP=qKYUbHR4-w7x|e!m7dGJ!nUuxqB&?rC_lC(j#a7G$Rx!ujKewdm>$^^5?|Kn_G8{{ z@jc;PipDlA1n|PHN@Me)=7KDul%cb1*?toV_TJ}6^NiUhL|W=lUevJCBrVH;R6SR3 z;S*R{!*$f>Q5@GyLvxI%Q>p4>4I(0amW~AAXh;n0<#*B zngqm5&o_6(*6XX}ti@mmd+ELtR<;;4{JVNE@9~>2Sp7us*aPMRZc(7uwU7+fUA*gP z(T=`#l+K`pCNXS8v?8A!4xp!!@k{Dg9-2sf6fV7*v})#h9mF7mr|t3Sh(A zUb&X|d{gwmyxuOhrRH0A-FFyUv}Ay6zGn`54RI79Zl&3lQqYf~lC%DOI`V-h7t=Ru z(|!jZ{#~Gw8*57Eub8w~Ehgpq2o^E&?2X=|+n~Ayj<7RpLxu5E%gJ*2=Xf~Mg@k{aW z;aWx&q~*k=-j^VTBje_+yW;YG!|*8iI6ZIqAC6}JE0B9}81W>fg%Kid-}Ni8)~g?x zM7kOt#;y!RiPWF8vwSJA+B$5yLYfJtD&4m0?C5uUmDbk2M+84F&Yub$`9(>|SeU^* z{BK*g;VPD5?bG@TpYrxs!z0qU^mkvtU|7tIei^ebgh#sqOM3I=4vRuDRh4jzV8ytX zh6{sUf33~;-7yq*tiTIANacdy;@V)}?dzj+rgq*R_yn?EyzMza`{Hb~JnzTT*usn8 zb5-7BsF^Go#(hj667%=j#Kjw2|MtqSbaGQ3Cy?Wde0&!+X!-S0i9Sb?c5T z??crcA+}wOm-;GlA&hpgP6>^*qx6MJb-G2S75Z7_M-lj6h$VHWpTqtbJg5B;FMp3a1{N{&eATZ+74P+*pS}aE6 zd`;HLSV2_jj-Imv9VUm3vz|M|d-P&Nv!A|R?NPba5FF&wQC18^VB4lTw>V+OhpLC1RFZkyo|A6 z-XZxCKW<|paIEO0u5ZRI{a(Fr%!#6^#MjkEeam6oGNgt_nl+xc&D2XmACLGc)n1P_U>-Y)&BNH5Jcl1hnGQ?Kl2-!7IP;4n^#c%^SY-^F0#BRXo0l8Y!G8p z(A?*hVs5?DrL+LVG4PoQ-|^;ZMQ9N~i-$(t;w-Z78Am2rU z>t-gvDMAt*iP*Ohj|J6G5Qvn$shx4%w)w`nzssL1mYQ_^WvS7KSGmw0!%J#D^;*8g z5)o`Nh7DU?XA^$AeVz-3XW@Y+(NT~h1>Jai#MMQY*FMMq`ctCz-*|*5VEA(nAzR6ogOhIu3;&lgTZ*R3QkHxpa7A_1dK7OJkF!wab zxl@rIRZ*dwc5(YhG%wC~F4BA3RRj(#y|9x*&HbYBM>II1XCP-ADf=oir;Zk%WgjK} z0v!6*{;7L#cKtT_sXfc>u_`x%aD4!8fjWVJaa3B)wlBauo2d4?!!&wHKq|caeRD5G zo1;+zfh%eNR>fEnTXNSc(FgK%!_tHY>}=Dk%~bDJTv3Vm_{tU)GZ9kzIGLK&zmkbX zKH;!Qg#?GUC{-`gCnkgWi@s%*KCjfqNmRASY<{%fG|pPp)^igDqNk4jW&^F_ojW)Md9rBpUfK0Z#7Eo))tN(LUl@6b}vlO9Top14JtDi{}3BGXOKsI z$u4g=`e?NC^Bw}4{ooAzvYMp~bRAWlmS^j~$&`}3rOvC4+K0@u1Pvw>Qc$luDzxz- zP~N8PBjEGbo39b1XSatH4YqJZJ@)lFascYg?y-Rqw!DX}M7VF)?yi?O+l4+0RF$IKJa}W2Xe>8aIRRshp{Hf8s%1?_@IjUlfBqeTdC~u?vyS_P?^V0k?BW(C2E1+hC&_C5^ZS z4fJPg{X3$RS?Ct8>S0?5&#tg2)PF)qLEuz_){8MhYl$EEHzM?u_rWc|neUHwSw$W# zw(Bq_M$%PEQEGVeAe?OV{Wo1=NhcMQmN8$;#LUTfKbkJH&w(f9>c$b_&2ikovu$V zx=-02AMM`Dwg>uAQBk0a5K0~ksCePkaw8Kg(cRW$&5z-gy=La@w?SLmxV_I-=yfdv zR3lDbb{-HV{QFtVa1k+~t+x`WEYTgoCbmEA+NRHU0e^LO3>!#*8`xP}jy{PJ=y}aN z?eju5JL+W1k&8fC8Pb$~nej^*uE#C$6bpA51)EWE-?f%hJRoohW6&b z-azF3im3flMp3}PHjVXfejh|6cHWq#QBMTRbmip}Q*KZ?`xrMGyvIR}!{xS*vTZYq zqtu^}Qx9m`<*zgJtO~3F*+kRb!urT3Gy3_01$_~KfE(Sq=CdCUZPA__(WuB@>HN?( z*eU4+sp(v?KmHN0*68>nS(cNrJ#Jz;kQ8B;bKvH^ah7rS1_nQ@L}gqd1{c|}*IY{P z3lvFY5RU=m9;8IL5KzIuX;))k2in!qvJ=Kduh zq{iF^&evB;rw9}On^!+W9?Z31WDw%T7PC>C%c*NFmO$%|J$AZMIy(RD%Vrl7TNE2D zH1X>vE(m*gbtQjpnY##V+>+&g>4Q68$@l!922EJvVS=plEl8SZ@#j1viS$AEy$wo_ zo6pb-7UiVp7>Z#vN`6Dvq|{Rh9pCgL6XtsX7-uEq(?h|YU8~oQdMXVGO8OYo`#uLr zN8|rsf8RxN%%#aJUm0rFd5&Q)&w6eAgrn{_O6Y@eAKvANqh%0+Hb>DVE#!$Qu4OJ` zu5c<9j^`H*8hoLDD@f4z7L8ZLXEPuAwi=ps9{)rRKRo$i8u-CxuhF ze}+H8g*9m1UP~^hLu8g~F4}chAHPCHHhg%<0y&qPgK$x#y?cb~g8Qf#ttI!?NND zfwPb_`ZYK3ss`*2TY2Y)c0eL3qpv4C{l`&i?q93JKJ}e@AB7i9DmJ}K)>Sl(Rzt$( zTMjusffF0*))QfG^8k;6J5VRO6)`Dwu6r!u<8*J5x%CYqldYjI;#23Wr>(|U7%_i^ zG!m6Q(dpQ_ub1h5iTCSMUYW?454QKT#HXz7_`QLhfwh;kS9VEGPDvO3UL`lID2w_; zVO}06!-4!yY|0JXi>g9o`M>q!y`T8DeXUaeE$HfukCT z)4R4$T~a!nL+qOrDS;Z&S|SeC@%+d&GEg(we;Ax@T%`Q%X=+^Csg=bi;4~4^OFQGp~bqWqw|WdBaEF@0oiN6Lt;z z|725U$8@vT_{*L{dJh%p2~@fL+DI`-hB?*@&RkJ*NgS07BJQC*Gl7zg(3`t$s{2MC z1g>+DT}^+EGUgC1^OMI?m|N?JMi4RR9`F7U7tm{vB?rf-D~83!d(GUs4yc76Czq+$ z;wRiJAPO;DX*?V{T`QiRf$zdyME?h9E0Yxl7iXA>_z&Z{;^(BmJ&3f4!jaGH2Z9zK zM~NKsEZLiT)*9jlC?^6;nNN}sa{47`d7O>4&n)v3^t4N};ykB{ec7_0vI%tAkdVot z7q@ZTUJmvY9|bj@7?V4e)j7dRn}APkL!fD8@NNOyPFfOL0v2!eEXNJ)1$NaxU9QbWVg;K1g; z&)LsD_ve1yeK+5F-u3=k`ju7Ue=9hu71Cly3wA?-NUJA=V;BfNbN(p}8fEVnWONLx zuvBXCc;a&zt7?1ZUR%*bNyQ9)3Swt1G^7#+Ay*ue{%K04FcweOLG}yZr`I_RgAw1c z0iWseVp~G=G>@gQX0Uyoy3a{a`2eiJ8g@e{jsZk3!JDk6LJd5JD6Xo%P^|G|M7z4-alWO zi}L5JB>M7g9buV@BuqSF-7OSG&u{2oNXrDOP^A!N%1W~jkWvh90sJ){C(Mfp?_ya> zNbOMF7yb!(L^uo#U+k>|1%*_fRSLXxPcL77^v`Byg1Oth1z|)^VNGzI8X2ECb^K1q zrds%$Te$wfiBI21H!x^1pFLb7%a?^O>Q(ev$P#)oqa-0(` z{>UBsXq>|5n&?*&5$nl@?y8Sv`SP#upLB2L?;i(FCXz)1=(cGnOMY$hEwMsTF^DTC zN{}z@a#{xrDy?i3?LkWUISzWmzn*Owi@hOIPR=Xx!9y$}%k$l4Q)g42tIf?^@!6XW z84Qm(RqsFnw9uE?3qN61`|1qc-o4`-R~l4rZDBX>PsHrP)uwS%#J;B*S5|{!?5MI! zc=EIYnsHwYF_Nse_^q|wzY{=6k`eDfBWgm8=V z?9R|`psxC5<4|rEMpM9ktcMzy=rInF9JH+;{fQBFnm2fhrDmb{u5NK3uxaTzk; zS;W~$lRVnCsZ9iM;J*gRvc1sFf||e6WO6Vk?+|`5Qg6HD2xA|tyC6BbVNvNdkyUM! zs1+Ps$=lf~p`J)?|AA9nW4vQKh2QhK-j;DAsJ-WIHr;~DQ;605BJg@8E_Ey`58i?V zkPV?8r!zpDGN+EO$6^#oLro~Y z>M9@Ek_<(VI(Q=UdF|kO1~Y%tciFWcFh$VF@Kb@WwlAf#9Rj1*v!-j8;ke0B=hS_2 zg_)YSyreH5wKth^P}(EdJAea54k1pi9j0&3*g_ZVIihejiqG^ITAEPzmQQevE;6!y z8Ne8QXNEJ?3NM4@jW$U;y4Ne|#ZN4FwUoG@;Mh8aDx&Fpj^8l2d$>*(kbssPsr^ni zW`;5}@<+qag(SDoxbAW*YP63B-YTbfZYRfm&0IBWI+c5FxjXHqnHpG!kLjN_%(r6k z-J+^RLy9%x3dM^qw+g*T2EHmXBgk*^`tb$>b2lza%}FB-j_)qVuJ{t#qqq5NQH+Nw zoj$|;RruqE`qd!7x0*5gVXg5)abplZ+1!~_NLOQ5^bz?u!39Q%SCKtSOpjvP(k~G= zwc=6NdsrWjQDBQPIYf3}6c?MOgKI^*i5#q<@1hOUd$>tC?0C7z@bsqviOXLE!^gL# zfgA0MwgBcSS*~UK<?MdpM07rs3uV^(k1zdhP$H>mhO zztP&q_ziaV$VI405s>MWlfg!REb={4Pu{Uu+n$D;xP05VIDe8!*AQP>P-0D`68~%V z9uZ+eryS%z4%@%Eb^~U6`OMTAx&)w&&}-QSx7~Af&9CFw=j&}^$)OTKzH4T*1A8}+ z*iH^Vt(qA>e1L(kr{)#kwNyIrglG^WeiCrae0^PXjA$ezu%ZF@lk{t@gGjAAu6)M7 zk2{X=#}vuSdY^SnW+GEAqG^Njv;4OHtOs_%tL7_^W_U47N6*BR7hcyS_frqbTneNk zYaWfq35>8o`sx4u0_GG7qC@4~!7~Ir4M5xjwP!w%FDo{k5|GUph(_dWk{@J^7rm7TMDLl9 zC{2PXyNuL{Y0;K&Mmvi((6PY>`iiymbm4dfU8#!lU&h?88|Bj>PDe+-78=hzq4(IF^(EC zvIgaygY2v(j!HwH^PH-8*w`{T6Deot_H>4YX-3DUwVGjKz@Km&UsQc}X9dtCh)QhQ zont+BR!1`nd#e{tEy$^&czV%$0+y~$3SSe^tCD9XgJB`X_2KbfFO#EQ#OQsVp&4z5 zqM!u$*qNFBo``&2hw1O=Sdnu!3hMT? z27mTi92QA?eWbJ=Hxt5DM*E)@$OUe{zwGWsZpCnTQcB%Q`_IjG|C~rMvSr1ksc^(+d z%-ekB7#{fcJQvMYE5_utztumj%;W~kLU+G;ElHY$zH;oL5DDWCB=Vcyo!$Whg`+9- zRdS3Fn#jfw(*8x8O+zxj?a@4!zAA-0<{GW)6S9Ujop47sk;SIZ?c-243&d=Kde^YX z2eGpSgnWXm%`yy4YGM?fJv7Q!BQRp~sotYokVMI2ZhpH4N` z#Q*!4RyN3ATgVhVJODL`z0CO6iC#zaQ}!DQwMaf0O}G4jZh2Y=h+%|^5Lq8~fcDr2Xm=lTvbu~yHb4k-)c_!a? z4p?>CE8vxUn*1_wUH;eN6ULdofzKl*%q*gjjxaG{gaebcoBSm@)2lqgm=v#4a1u>V zZG?l-;}p};*Rk$laD~GT7^?njp!DVt{w<}3B?orF<#Bugz)Q(rkb}rEwKjQo#KvC) z=e{0UNh56X21yN5NSbnPT)OptMBamU`pO$9H)p?9{r+Xl>RERtv*DdmA0ES?%esg5 zq3>aCS%wNX)o&YZ0A;zt3)KF36=_;#%#82sOVGuP(x@vjrI5$hs(G{;lw@3W}<@S*v46Px;& z#+yZ3&f#oR;#=wcWeL>bIak;o_%A}l%+2=sSA77MnjHe$%64IK?r9YF`4~5Vb=BE zik+INTpV6qxxRQ(o?@5UPek52=jjbos2`y(D4YB9M#lvgO5DcNcyeFExZ>lA5K3rj z|E|SbN6TaieK-6|oTTRnyFA%$x#{v?7d71xWNIM}EfgRc$BBqI*LS$>xjYVJI1euu zkOR>uu_N$o98(87Q3+Z%aRjs{D_1wF8CU?ltra=pn9Uw^B_x@h&O|GZf<&EHF#kTk z;#6kMh~5uwQ}BfIRF<6I1S+C&+i<*|TkL=~1aRWP|BS--pYWwYiXa!IGHkqYIsm3r7q zh8ouo!bbO9;-Q{d4faT1k5by~fGqydOXZHmnrjF@x=5J}Y>cR0R%aHECg2Abug!&W1;fw*#= zyIWx$ZS9Lt4z*Kvfrbr$R_ZT11EK#m%=)#BtL9@szK4YE4+sOR$EuJn0jR-DG6-+2 zRzCfI^R? zgMdTsyCJN2VDG*n5|OSPVYp-{Rb1I^qqgajfpVy+r;2Nbc8TBp>uQoSAgZ(JBbEDY zHNEBIq5q@lwlBkkJ{|UyO|(+;J0IGVDRz{ZAQ=+4Bf|GmUPs-N6b3FGp72RS;J#%4 z$?$2VDGfAdO=b{@PKTHEwm!qnr6Uv)9-sAn)^|aefXvm?Gdr-vynj3NT3W`!qIi>8 zORcMV?sY7yZ~w+^Ly5~FwGY@3K&4K-DC4gkOt=;6|44)bNyJP}z+2fqBXe3Wdn$|* zn7?`J<;x-<`#Rp|fbNyG!vw7&%PNc!EBoH=gZlxDSx!&UIB4l;7s_hhM>J$P$` zu%#l-(M6uMLx!FWSvkBLRojX9G$7+CvX8lE-gbie^G|t^=eoPg+Ce3rTC(M!2EN7x zp-$7M-x%Va-r(7|a!0?v5hv{o8~XL)yCV?Q z4GK6>Bt&Ddc119*%6p>Tjae`7EhIMx++N=lY@%(Z0q>c z6L@*hjAi(11}g_$bP&Fv?eNb+ngp$Xi=2(j+;byU8y#v)1l*$@9OBHGSI|NGHe=1Z z|83Xe@8OW7&-S%S_%JFmlU2NvZ?NO4p`_k}DM+#~b^k5IoX(+yNJ#~L*Ga6;KD*;X zSHM{Ve79ydymI6la7=;a>gx6a}it zc>24$I({RLf+yorz94TpIY);iG6JT9!y6n&Z(Y2w%5XMZo1^gG*B8Ua@v*TO?l*}1 zYcSBAAkV4vgV#f`ajdCB_F>D_-DvBf_H`p>tzUR9$QUZdrErHyPEt?cl=VJ%YVl?7c9!^F-6R{_pLJbmwJxT^ULS&~tRrsYwx`(V+)HYG8y&g;VFQpj> zo+^}<%C|ZY8h|{Wg!7;*uy2MRFqDGem+}p)-?PIj+T*|V=Of?x^9y$;{87{ug#I6N zj&9M`GJIxqSdy42=k&SOoX=^VcI6d1i)yt$u%{HhEBLHPB?8pKNV=D`fMpRmMV9%? z9O8uEU3Tq>@ru3HswD|m5tI?S-cVgR!Y0scFA3sA16{`OsXY{;$ zzr{oF2Wo5SApF?e9K2!O#-u{2RUW}@FC9-OeqjbJ3|l^X4EJF8|E0i3dQ?s(Ao0Cre(qcYY(Bp z$}IVc0^{El^-r;j!bXl{B=tMWQnZrD87=nm10Arn+xKs*2d-qS?gO;ZyaIBLK%_^dD24_a;ncGg+glzI>Hz>z=ti7tyBvjG;y<&)T zd`wCs26MgVK@*SEzX`Mm{9~qsU1aG7JT+$A08aQ&ob)!1vj^sNP>YM9?WB_Rj%TPA zM!SGK|I#|%p9mnmw9EVl2bHx<#aJUAXLl0CrCm+c;HA6qlI3vaZgjhnjusY-12gXM zAk;tWmU-BIu8`XI&mDpvBBeSGUWQB@zP-W*#t@~B!e44xT63pVl_r}@vnoaXleS0W zK{QhGRy4RcUHYE9WLY*QlPBDR#{mX}rMD9sWmm9iDw|ht&ESc) z3^Uy$O(^loJ+?Q3$?15De^%vVK*tg=f5D#c#wSkeH@-W$G#(O&VFmjXO?wOc;mYx; zprm92ZAT|sBK!=iW5M)4_6L|BMg69(e_N##Ro_x_sI7vCG9z$N5zWBg7|l=ZL`4rwIRCLr-)9y! z;ik%X6!qO_^d=mEIJC8v7=@jf&>UPzX{kuUt3^sy(e$J4Cucb+Y_F7tuFT5|`>_jG zGHCmO+3j40zRy64UWSvLgWV}M^kY482<4+idxL$XhPP=I!SWO**~lzz9ug{GDaibp%XHm_3vvXdE5SKh{aR-XA6orRH-)u>NEil zz%z18IG|P}`1l$uv^Kz&D<{S4iguu>oM$+#!$oy-s8yn1;dy_=jH=*xlf&*>i7RMR zY7$LW&sJUd+Y47v(4I?WCq%S(Lv+{;R*}D0b{-qai7!$RMcaO-G&bi`pjuUFs_Tq9 z2B(!{XRg$%@1l4>mW6JV9>M8@vpAJ_ z@BPSt$-tAlBoYZ4ZGJ*Bw+^zgEy~`^?NInvD2v-^ds~Ks*@_O2hrlulWn6V$SOBY| zYm{rGX4kShuG9oInNG$tjkYbNYprMqOZelib?I-99Bhwrz>KR5Kcp)~7fzL_Y?%QR_dV6#WsjwN1V zN2$4jQ%+m7C&yqmd&L#LVbIl4NDSFGX8e&fT~Mh1%AX@>hQ_{Yvmc~&1?dSt z5=dG`T`7{rL(x0;mEFSNG*>}N$f8nbBZ!QV@q>@ku!hk9}x!2m`*K{#Tpl_NfQ z@g<@i0!GMx%aCZ^fTt@8DhsTUXUi?^_j1BoLHB@+FWuLP#L*BLQPqY35Dfq^SsQ_s zA?ZxQ@z*)VJcc{VO_q5n<=zxqQR{zJCcBe`88x*-vb9vp*x6Cu{}Y}~^~2f5YanLyD4#d;LMv zB=-@>&idK)^Jbc1wp&3m;8RLlQV&l6`4&($maXF5ub^>);BTF9{C5&rVPwLj1|xS; z2R^}4%lE^FccTYta2+7%ZEEPki!PD`Bx9mNxSFhG0+5fIT|7 z*eI2d#wED+qz@TMjKuHv@2-LymNEf(Yr_uT)NJ7*aZ9^6SB=?~FST9Zs};HFIE%=0 zZ(>6ap2M<`eU3_#D0V7Ffo5Ta^S9y%TFNGPVxL5I!o^5?Fwxu?YA20_S*X=9(_X z-#|TWmE{yX&o(Ht_7exvaP$wD5GmvqwvzWhY@iAPBU3Uu$ywx2&z?eMr1t;D{#1UM zOp6#jwf;9g_{Ix%z0=IE_zx$Dj{gj&5nTO$Ai`5bmH(Nq!xq7Z{9mh32=4!TxOX$| a6@?@!oY}Nn`px!+gOin1lBgCl4*4%_ZQQ;9 diff --git a/banner-bmad-method.png b/banner-bmad-method.png deleted file mode 100644 index c0c3fc3415c086c5d758181a4cb604a3b911ea22..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 374692 zcmbTd1ymgE)-FhZ;1EJ^cM0wi+}+)wacJD#3GVI?EVw(31$TGX;4X~}-}%pf=FXiv zGj~m`)!lDZJ@2!hEwxv5_gmqL@)F1hxCjss5Xe%JqRJ2upZ!0^TX2vc@9ght!5<&+ z_L5po5D1e9rDX$9fv<7gSkP7e<^SbkV5CBb` zjfmZWHnvVY?tG;G;^p}m|8tm;l=xo|XKOxEp??e#Ysx7Si`Y4u5;HR~Fwp~;n3#w; zxfx8D*Z=@#4sI?wViqPAc19*nMkW?|W)>c1E*@r9;(u?X9~K==%y^VV#s6*ZV~>y2 z!r9rLhmq0E&5gm0mBG%@oROKEoBM-+k%fi+13~ZPVe4$$hWT%7qxKh*x08$kR2(AqlvJ5(P*V{|vNXJlqz`p2z*0Zjn^!P&bw+WgD7 z34qbm#uR93>+JM_W&RJ=-onn=&dI{=|AG2Hr~fYoKEf*}_a7VoOD#a)e@r+zi@AQd z@$Z2AFVRk_9`>e;%BD_sE{*_GG1m{7WdC?$&m-b!YUFI^sA^|t^WVu*{BOy`ESwB1 z#ME*|0886{oS^w1rkIKvIh*p4e&mgVo{9M*X{yZZJS^w|N{{@w^GqE)D z_@AJhs?2OWEG#^1?Ee?&N8y+lIUD_df=vKCW_FH1qYsxYfkx)0jP|zXq{ROTB#(%l zjh*9%;SY7J|570*$0KFyVh}(po zo5Pr!-h_pNlbe%;lZly?{lDjn+5uet$?ZS$|EttZ>;NAe|EE<`Qw}yR7FJGrfH4<4 zy$LHD6TK0ODLcIxGc$mVlZDOHgoXLP*%TZtKdv?-oBxsZA5|tFjAracX53~Us<@ch znCaQr%*^PySh!g~$XHC+jaW@t*_qh?spo%{2#=(t(?{|={(Xh0m^%D>WMfJEud3iN z0{m0$e58PX(rju%`tQS*|BHD1Z(08Ld^Zcz57Pga|C9LtdpZ996aVkf04$7b%}qaAC?n}V?lAt-X#OiPjQ?}a z{&ntuXiEPL|LAo84FA(+KX(4ps7-A@s2xAraD5qy0mSE8cPUXJRrf62*OLSjOQ(u3 zHB&Pp7*d)92wOo)*4G)aqc_G-N~>?1vTmlubT1yf8}n(=$YahLrd4-@J6qe^S5H@< zHxNHRzre;t?8mnHvN||;_Uh~7yRmWcFnH+owh7+7x#t#O61Yz%$~Jg@bl=>#$<2M) zK71J%JT&LudwpxUy17ZbDSHxl89m94%_PbZ@B|46*xguP#6G-ub{)Smzq^9HK?l39 z3orYJPW+kG!_D^|*I73XPu~2NgcP|CPft%C?VSdUT@0}auxanNw02K7FTA+|j9daQ zEqrem?_luB!_E7PfIi*)+5HE*z8=ooGF5umlegbk;bG9huDf5#5l8jymG2Yg(@&3U zJ*hWm-=CWkel65CgVt|1H?F&p^-4Yn`mVn5i=#n46D50{2T#{AH@E!tcz-Ya*32FR zZk}?9a;q1uQ+5XG52EXmFJdRbKKy_AthX;VY#)|GURX!Lp8Ll>r5-0*7mI^uH#c`z zPiL#I)$hkA@6YePyf=L}KW?&`A1ceaBOTR`_Uplz)em%kcn6!o@3$b|mphQp2BLHrlo zn)sy;XEsxVywgDa)7|t*FOUI#j<-0!sqMGHEl<1yyvOdB^|R!6&++ths057@t*m#> z)SE=LVP#j3Yh4fTcU~fg_qW|UPoI~!9f+=to46ZrwboNBN%g}ZANcC(%A*~WYj88y zygY*6#5emCP;q_owAV3SYdU@a=uEb`?a(0P(TM8f8hvt@oc8lbx|tzzBHCnhy}29v zzP42KFi3B}6w43lbGa|#oAH(T;#ReDcnIc(eMo8SOB=JA)EX=u^Pf}h@)RR4U-V;_I@SdY_oN~Y}dB(F=I2YUxHI+ zbA57yo;|y4mvUbw4|!(>Ps-$~PWI;x8ag(K9&~FQ_O;GhA?o9o#dUcHo^N)CaVCso zqz3l)3a`Ul3NC8Vt}5|OpkUMqRqlNMyib59BmP*8IXMymxX{qYjIE9V$^6%VwSz?` z20oMw+HROXZK#a>JQF?>4faC)Q02!?VMkanfGh*BzrvTpApVd|l*y5I!w)hUBjO^X(i}-SZtr+#UZ;^25X-ubF%@GO zaOb)aLB)s+em&%4MgeDh6C1Z0<2;FKl2+>py_&hH&4yNiEOv29l60X4>LmPTN}f$9Gz z*4mp7v?HRq8`}P@&0TB3$9T4m89tftq4sH#>fG#9_B;k0z&>H@q1{3an6eXhh0ng) zaH>3K22R35IE(R49HxcX3=a-+Wn}eFmc-y98o%%o*&VeAxujg&c@8KK?Ccx<3B=VK zf6ra*vCJH#OewwDVun*fTRv!+jNPm`n~a`$M{@A!!k+hF@-3#M;2#t4;I(bGGXTAX zbS^2*NJ_Bw{_z^HU3U~^gB4|Oxyu@UUez*hIIaG(rn97c_Y3Y_nXoi~GQ+O&Kzjs0nfX*i^=8whm+m6MT6Yf!5h%qAYB5istW69 z64uD-c;JL5D)ho|r@*dwqVD6ORC!&YiMRGm-7o+Pbd`h&1zRsi7_dqf1us=f4pWa_u*6oNU!?iV6Cz)+<9lWbQWm-E( zeZouFn}weX*Kgxk(~iM+3%5^I<=L)P`qG7MeGHl5xgqfOtPs@_D?pWf#A(2SC32VCD&up6&o?bCred)GLdRu|BsyK8P;ZhWYeC>17sF#EBV0%2Z)>piOu|2+UD6}E#Wy);0J_rjsw zhoA7G+TiicS4UQ@D!uy9l5iHZYI|@B-Vh+%6zF=_alHB`*DtSL{C2(PRD{H4N8ET! z<)Uk2JU`7Wg(6)kOhy7@tSj%*8yK2%PdrfIxrFsFwN~~_-o{?!<@JS~YQib6o~Gdo zjG3jd8U~6DJd6cgqj3@ERlDosZkZJ$^e2*fv6T~NRKVN;JM7=Ad{+(`?y=K`or7rc z04qsl7Tq>s;-!Z{zb2S&o2G)^l{X8ZSpSTy_g|8y?C7T(I8Zb~MK_1IK9dJztP$(~ zX~wJ$cbbwOqtB6P6Q2%JaAz4!1>Nk55%CLLJm~)IhRyJ@ElrWjT)GY2XYrq&dfIaO z@@?;Dsr>_lg)@oP)vCWwC{wTjcTKPA8hWQ}?>P*BJ3Eu|&YQ5_k^fAb2|}G*JTk7>n7E0~xyVuM-Bi875pH;XKe&~83fiWnS%e%(JEEj0&?dLz z9vhC^?J>YwV^rY6^U&pSU(WH~k%_|KA0}(0V%O5m;coJk`{V7p)dUsH#?IQfTsf&R zdA?@*&|YO??+*>IUG$!#>)DbJEtLcF(n>KIhefpYR~i~0_A;+Q?ywR2o?Gg$k?nc-$mrnTtJSk4{Bw^|6^p~NoyI=wg#<2?<*;W`LW z3ka{ufC0$e@FqIUUsHr_{xIh;_fCVFzg*YNy4fs{+?BS2#_;zNWP7vO9@JK8I$N@= zmi6;9OdN=jN~(Q-@;}@Xpzp=sOnVu1qq@BEJ21qfZmHzEF%hpc*S#_AlVYVu!>IV= zH$lMa)&yaQjyDTbEp5NEvhhr8;Yp3C35X&QfXT_h_7<+FU~+XX^uwwXLpOY&svd7{ zWqJ6t?P*%ScX6tr-ahSnmX4!jC)aE?f#EJ)&it$TThQ8}a3@UbJ#)nE!uS<7KUI%i zp)|@b(`5DSHI|+zJrjj4sDK?Ij^M z@M#h%SpiVT_%Q^KQ6djmogco15#<6!9jc&F?%zD$&ZU0LH;uD(TIK{XLWoSHW$L2b% zV!SOmC)oVYDD~=a(=wALW$C8SEUOJBqwHoq4}%jl1t#yqLi$z*U%`_PC&?6Y-C2%n z-FZtQGfUyBjWST^&+dFv#Pn&#fzdR?^GzLrS&k!ri5+>z%$Z{hkDNH@-Wst5YaFbX zZBBBv0A#XtsON>`K_2az<@lGY6yIa4JsOA;S=sIpdAa@41cyXVFccR1UEbh^@?;31 zsJqI)Ic)qE<9hU?rijC_ro0#v*8#8>DN)w5&ohudgDCT6~ywTVd4(pDHCV$_!q~UyWq3hco8`3ZlG6IXi zG;hA0kcY=3)=f^?q7*fY0NTw`a5FSs-)Z1UPH`nti8LIFn?UVw8*26l?r{N0;81b2 z&RB6EP1z?u*)^;9HUHR_)EcVPX=+=NM*UjfdH751uTfIjrf`pmGX~MlmnxEaG{d}p?y|4S<26wgHCVGR=?%q z!>y^pMw~VU1gJp0Q%wakrA7*)E$$WeohEN7oF#%Va2VKucQl1gDloG{TH46*%vVmm zvFgm@+NrpYZ=ODevIzlSRmU7CDaor=DDtB60MRsQueLvz_a}`YD_fFfi{P<&1!Sjb+qqrdQc1ISJ7T3ZcTK10^B$mgfA{5 zl45<4xQbNReOx4TdF9Nrh{b4^m2;h3g=GLLLPTYNXQa&8Me!xZOE z7|)Jf>A~f(cbN(-D~!{&ey_Ahk0}$D@IG?vpMA1xiA3qRmQx9kCTJiAU9sIRe3-HQ zxZlug`@bb0mPBy8sMYIR#XV-EjKaTv5uYjziYi$K1F1Q@8k9BX>2V1hg5mIFfTY6~ zE2FLR1E10W)h!ph-eobUdTiATbO_J;?IKK!5Baexhp`Gg;qD$WhK6q~n)Yd_;6tDxXy$tnL1XWLJozn3*(Z1`j&F!vLj;_0AQTF;Yk9A?nW?7aXP~?A&exxP)o+jWq9v*xhrxP$6EflF_0b!=azJ( z^XwUx{7~3Q1%o!4@oT~qadhEiuS}BAJ$a(O%rv%=tr_H1iC{*wV>R+?2gKk7q(rNz z3b9)^nQaEQ(Nnr@iVk9dg;YW^`}X&j=GvO~7a!`xnXsy2vPeIvb8RdHKj+<$=oA$x z8OjTZrr)~XSu2hpyQu;hqkCLf|Hj6Lx+$`LXQPlYYR&jOOx;WXRMXHyz( zvvcePTPSG~-M*Il>RPu|H;*39<^INa?&d`^_#w7>GfD6cSZ5ag&2go_)%vy>+xUAH z!p=i3(dHZOk`3A)jUA?~U+BnzIJbML_@rE^rRy2aUEE~_vH%tmdmII^X=s%!ik&~J z1R@I+o!#=Cn|1dinBRX&WqXanJ0@S5KeiSp3`2)ou6Wf4-)N>z4w4Zo$p*#L#EazG zJG~jh(4#*%r5x78+rNo<#){Q@J{i@c+uYB0-!ZuL>^ih7U^~;yFX`6p6*7#!Sfi{i zI9CMsv(#X+LoD02{i{4L>v)_tdEG_)|kz3l&%SF^wcE{oiYDuL#r$UgoBzxR~xF+~48#zxB--MKI9& z``~9gJex#7#$z2EqNyxSHqrUg`b%D652$`oxQ?;0mgv({{IYSBd=#Wyjd}qCVPF zd7FDMn-O@Y*)HR#A;x%wElsk=wQKrH591&^VYF{SjWT($vRmIH^#$%A7~iZNUfyXt zoLEkm;g*}h`e$29Xjvc!C-o4u!wGh?6k7my@f!u#BEsOHmyER8z|~*Iw(3vw;n&c^ zkoCBh%5vHV*|28mf65Gi*vwB>4o#-VH)%AhL`=@K->dQ$TYPZdqXVZp1(?;pNbRn^ zHbSF)gI$AdBw^%g-qBsH+t$uS^|Z(ZJRMRD<*Y=`%>_OdN%ot^%dv6ZYXoy^_pA)& zv%rh%J$Np$M+xh$_BD-i;#srngR%`v4w%b@d}ZdiU(|eSdp-mP?nU zO$(J}6(A(v11(ev2%N_TjQYL9z|eQTtX)QenuP}nXD4$L+nW$6TYjR^NppZgK=r*; zPL|CVSu@xDGYsa9pdQyr816y+a)^a!YWdd!GsGYI+9Tq>QlJCKc^!)r77Q6aEwn-9 zdx4)$&aD$_e?Nd<2MsO`Z=NPM!|^yY4gT8Fzl4{>mJl8w5>b$x_e!%w>wvXw2Nn>P zto(uF#82y9407Di2`~>$Ktd(g=JV4)yvu;OsR(roG&zit^PAmGkM7xY;RANHM#2Z- zGyVe3Vd+M`aJ@{=d0lOKYh>wR%lsFpPZ?Aez1{N*!@G4_$e`N@5@(W7WAxOfTBX7W z=cycRIfd`GHu0?jyI&dYp0B#)4mU4yH~nO{4;Dc~aR_&&`(70C8C88Win#~qP6^tr z!m}lN`rlcIbWhbaR@M(aFMc$FbkmF(CwUAbCwdAM)TERRPV%J;V(OznLOY}ez`lS| zV?@0LB%R$R+6`+3M)_K+daOz?j|;@I-KM?)2y-e~*fO9t{9(WeR-aD{#rRJwI5yVK zPtNfNME|1q)UConk~TIp$G|`(B5iMiwQ|)eCHWtojOFV_hR%aiCdqb@)fkJ8UWDp# zVxd*_Uzi07lTm7t+%hJZX9~9I-WQJp}ak`Ie|i4Zrq< z1+MeY$SsPKp=aRp7vz`V_B+4EuYTtwS97*lp1t0r7vi$xg0g#M4a&}c)j-$vCh;zwXWx@Z=JG1m zy<=R@0u>CG`QS*E!N&oxK{8MO`%(fki+`*-{<^fka$l){YQdHe>4h51u5#SDQ>bob zy|O%_K|9AK^YbzUM~9!v_3c{Wdl1iGiXeNdGrKS%Iy^;QpYybI&h$h2I9d(SVI~1W zVSalDf^x>3DM4q)Ao|Q08v$}N5_${7tKst%cG9HoVT&}H-*sCGmIMypWv-uVOsJ6g z;vFc+>%hwhjO*eYXEC+1PT}AaC5yyW3m2^(FYHgyUk1xjEqJM)j)?|snHztpM?d#0 z1Q>2)bAc*EDN`znhLW03Bz)xOZMVg>^YGJqh`xi(mn??LVATTOwQ zP|6HESE%^3a!0jpO@6&~KFEK{o8Z61$cA#V^iLpr#)gUnVRl;6f>NogGh{Bd%r<@u@+;j|L1Nrh7qMTdpIUspi^jQi zPf}>DY;yW$7Er;dm~mE$(d(G|i*&ZMPBM3u-icFYdh2>4EVq+b(*vy)vrTD2d0gXtPn+YV&3;rw(4(H0& zRMgO9!*K<@6G*&QS~M9jY_uiv)KlO=tjC+tL{8jyn3@CX_*VX_U%WF6GYMs{p*oE& zXRj@2V_U(8PYFL3budHdGJiI|JvP6Sv$H<5HpU+9?(TZPf8qa1JNm8T+Te5(7!l=R z#-$x;pdo7Vg8K}~Yc1Sf)ZG9yt(e3o0E|7kvH_0_QB6`ykMD5DIdq)33CRJg4gqBR z!4AQK86qQ!VG=%!-;_dFb)cdk4ngO!xqfob97u31AoBZDV^{!Vc~LZno#isd*9bc z8FsNoN_jc=o31!n^6cwJIWdc1?t3zO|IT?!qu=I>kn4nB7aw0wcDZe~xV85%(I*b; zdo!E!sZMIztjU{hE!XUF1z`NsCVlt~3=EcsvbL_I$?TIMS(MGP>Z6W%6vgly8nDJz1?z|th<=|H&b1b4>)vCUFUZK$Bxz~} zq&qbK`s+M_PR@cE(kmwlIPlfAAO37T6!ke8LGIhoiud(^;!1_jLCw0iDRCV9N$|`NsO?M!qD}^_r%QVo}-~?t8bT|#i{}^36fJD`zNk? zoPt*#rl%w#GAgTYnFhTYN8Lx=oI@**{4c%5*nn*@yMf%jyCLNr$Ks2>erIF_iSm-O z@=V~0jN&GVs_g#031fq)5R4zptB_j!>dI9N40cnWerM{|(J5T%!UkU^gB2T`ww)15Z&6Ax^06DxKObyk)e?O0M{4fSE%g9F1s3 zAp!yi!Va!o*{>OF-$m(_sr5L11f_6yDGQ6v=xM1-X8SgOt*ucB$%d~K>wK^jT5wO@ zuxF*$ibe_-kN`f%-7-kW0k)mLG-{bG zLqr2Trc(+kO|4N4{H=$XCS3g*lK)l$dt+(MsSd4heSxLnu2Y}5!M&4<@lWb%&8&CP z+EiaPd9+1i>rOvbpT*n(*z8aOiWH(hBfI+mh6|#oRE15hj#Q+PUu=&-!Y8V#Bvy7v^{5r?4zX#r9eA=5q4A_};QwoEoSCvF7*++(TcG zPdimh$tts2TlMCwYyXZ7;(S&S9pE1 zZC5FCKJ%98LdLWr?SU^D{umKEk86a~>%xnU`LUlY*4y|-KTyeY80;_iy`3&`^16Wo^lb4o~{Wp!Y&ftqhx>w==7F8rd zzM)peF=l>+H-Gl)E2|>Hgtj*FA-sz6Y@7eMJNebZ0c$;vH!Cu3!HT0_${1=a$MEpbo5(=qHR;1}05W{_ zEQG))ugALcakGho1$&9837!xJD-)FPLwLKynB(*Ch5;yL2ZmnBqryZe`O!T#@x~<0FQLcw4qsjcL$>w_fX-4Ktep>E|E77jki>F0 zpGG#*tJnf@&x}3964LcZW@Asun}!fh6HP$QXNH;k&^~5)%ylk5F2sa5)jUr z{aAVSJ}>$KS?+rs80}3xK*G?*%iLf6|};?b&j0f>oU%`ILJ_vGU{X+KG%q0-i^^x zbz69~yFBfi+j$6tKVLU#wgP(di$qyL*G1QtD{Vcb8jpbm@xH*?%cS18FILeKQ6a}T zEa^kFWz_hWD=Op^hmfYtxuttFw7(-9&e3Dh8bXe3==kt561~+Hr&Kt~1q(}U1O;Io zECCJLkNper>QWv}%j?8HaH3~z3NVd9RU0->aIhXA;yvr8ey!Oz*zZQw3~FUKMg4de z%^p5;m-QO93Snrj}C>492I70E&mn4D?m(X4d*iMFE2G$w8 z=yx)1Z?l0z_6Oq)X8!fm&mNaHl@p-@tFn9NG2A7{=8(UZ!Cpg%4|XJ=j?L=ohnt7P zMb^WjfP!Obei&e+YuL`I-Da2R{rJTsr|~@Ep|!Am><-eg#*F$8>FR(0eir~(4ZvVv zeS+G`US;A56`bBzs>ghP>#7D8l{df8V|{S?IqCWq-`JfpMc_z00=Eq5U(4FOAA7JM zO@Jj7!#Omrrc8kv`fwbbbb0uCb9Gjo?s$1Zv{CyFYsWT6nV7XyhL+nvQ0`=_S4~L> z@{3JL{98QXO(22co6V=E-MWdiOH<*7-?(>u>Sr$THy$jglV3X$6CD~V zVClgp0tjCl3_{)z%{B3X`-y`xZVqdMPW83gC6qVxFaZ3;LdzK{M!L9K1nZa8gUjU@t*`@NnO zEeB@?O~pht{Ah6I(|Tr4rkAW)%L%o19u|bVw#hD#OHO8ZQU@0{l^lBpyAu6ifExDT zeMf8Pow0jV@bAUvZ;riWFh+Qq2WJ)IsKLt8MTEXL$@#%lIZQZx`dQu5dy^RJ<3U^- z9Q@GgaZz3EUVIOaw^C_Tro;w!RK%^@ce>h)gc)J66t`pcGEa=Mmeusg0c3U$D_6$& zVVfG^D^qvf+`MNMDU)L%pQzUQ86G;^4P{dph>XUO+k7%CQ!=WsHF{ZJ%mcKj^7@8i zS-1sr-2}-Z{vAa0b$vDrVbG(!3V3_hp(YUG++?#|3AD)+Q30ukB>Ar|lkmka!ceK! zVjs4xD5YxSPg9jusP(Ds+>)j&&W3^x{N-O)JSE$o$(fnx^1kkjnBp7ce*csRLQk8? zwjb?(LWN_y*3T=U{h147Dtle0V#2V&mOye54z6JLvA->}I7x*?^>Q8}=&1bLEqu*0 zbgH*$TLcrQRv@0TfKh1W72>4cRG?5Xxsp>*l93eJGgq@5LMKgw=hHqOpDAeoek7ky zZ)Uhu|E8|=Gh}7oSdz%ec}ux~V88GyTj|d$3wJLBBb{;G#(b_JCvs0>#;9xza4B39 zdG#G8eXnOOH@%HK`!OCi<1==lw9ym^7v5)k-Hf<94Cx2~lD>mm#GEX&sV=09&dhKx z1C)Zc8G{t8FYU7`HMB~`%&r^2{p>a>dOyasyiR+US;c#o148cLWYXH;a)amn`)f9ozT9yosrJW;7@M(D*RO+>k5@`{1PS0w;NK*HGwp!CYZ58rxiJW9Z;1vOG zj<_BKH`fwUqRtOF`d^x0%|uPpM*h@~pgy~=3Q57jzy$0AP|2=G<}OoO>_ zu^JsCEO%A5?U%S{O6vdf5Ts+Z$8=8#c z1a_m*EWaSb5AqL!Z|)__w=M+67%**_@s#v;Vv+~ADuQRsb$Ky^Me|1Zfq6iZZF}8f zb)T~7m5og3=NxWH$9CMllgRCObbxkB2#$vcI=cL`9&#~*<#Iv-uMCVmR+0@(6}_59 zUKym5IE7Qb)5(Q^A2iA{g}z4@uRtq354dyHp(qips^B1)qN}6(_$mG%rT91n1SK@V z=6-H@4$*q8tvO6n3WxqzjNmnTc|?~0TIYbAPqyf&Vxr7$yl0iv|KQL zrc%7xq*}_(ot`#Czg|i1kH~oQE3m}gVF2*UspC2mhjn+%Jh_yzXC$Nnh{Vjz)4>zY z5<413tG5h&chT={AHGuJvqqjSAhW#1egm+! zFZYSPB2lY$J}dTIJ%lKOM8AD>MGTWFijoSEPFJi%-m@wKv{IYv z7(XaM&(p=I%B|a0*6xWmM7DLz_%JeS;o+zAO6IzB9ZJz%{3rm|hu!1=m^em$IpXYMg#)EHx?B_O5+9 z3C`LF_RmCwrT(=Ae&dx}I0dc@bma(-!)V1)Hb{Tc-%o6!OvuI^R9okZRI(O5^2&{vr%WK0B>; ziXDO#bjByKLw9rUpGuI+ix!=#_Q=$d^OAo@@`|4j?HJBA#1tUBw!sM9dEf;}cNj8m zC)l&^W!D(etC{A7E}BqICbj2iIx3vDq@!NzrR{zdLf8M$6Jxsh$+eU-`OUsblCRA(!%Nd%?Xk-p>|& z1bwy!)>@kClSlC9?P!vHb0PD1x#{&7&cq|mR#Sm2Av4`iNMz8UwT0i%l0m!b>{47i z0hKe=C$tfIXDtiERpl~2mTBvgc&`%fn8acb)Z2_FGNVqc?^XAqVgvakMrm%^4sX6a z(V3nl7!%oSYWnUj5o9fse?6eF?G~X6?V9%eyf)~dX!+FxsY|gyS<~w#p!$>HJ@U?( zwh#p=hRH@C_M+Fp%}=ii!AZ&@Tqdv|u@E|BJ9*A{u(ktr+M>EiMNq!RV!r)&pt19s zOhzVW6HzObN{lA`yR{h^DV)q2`c;A9pSqUgry-l-2kTzFh;lX&g455t;{02ZPe{Ti zuY#gsO-V)&8f}`5sSCbFy5-~;64lbJ;AwZ;_`ph`LeWf;`KUQ-Oj@$vQ|bjM60gHQ z&J7;avF`O;adQ2>^BlO-!Y&e)>e_S)=Eptx4}xFCz7oDXqIET|nh#pj1(I3W|GL8! zr)NsekU|t>KfHUrx3^$jIbNu6zIb=c!i#g$R+nOCkfm^}ASCFQeRFA)R$VR~R0(5& zWKg+jUl$PX59r!H1fOtwcH@-Ne$N<&P}+%-elTX)XXNdA9fR)kJH-hQ0aDgXTLIE$ z=X+O|lVTi_+&aiZKSOiCE{9Hu%anKxUF-CfKTCs~^rb8r5ovSt_Xk319`_>0Mhak7 z0f*OAV5fuY6IvuKzmiGTA1I=y3n8C3I)Dl%|~7NYU)Fj7+7d zJ>-W3ait|BGzRvd=(1t%~vggq~q<~jH6H}?rK z1=$3!U7lb-Xzs)A>dk|Isxm$5IjBLGHWzq$)!al~^NOi#-& zVZzJP+U=_!@VfE6$3-S_dq9YQ24OQiaXm*ZskPvfxhxC72$>7{kBLkhmIr zZINaXy=a(Yo1lu@Lt7G!#(B~ftdImJC3ey8MbzRMB233TC0|7JV- zSdYNc6!+8HGO|+H|Gg2pfHXW)O=g{XMdKx5X!?32Um0it-qmH6yAVdU@sTl@ zfUWeft?0zqM;uqoF;Mx7Y_BuGVuQ?~%mr||Hmh-g0?O@6xthF8?VqWW>>9y}*lsFI z(|HFI%8D_#lqXYCXVug@EYgHFXjOiymDJvB}&C>PE%ixTpe1&_v8`X8cSe8UeFWhsCU^^VKKCE#hDATOdeP#8GOd1x5ed@ zCAf{$(m^bXqIb<7FpV#-iGDIx$@K##9d3gMPSA0EpLK^9<8%o(m-mVtyR8msmfp4F zOi3NO91-pqBf60E%lTX)0^N+;(_>^z>dFw$P zYWph>H7gE99azb&HJu3|H1$h8i0AC=h(%$cpN!;1U(wgBtuQixS>x&*5ym5?7BO|D zztw&imew(wWsqr^>@QXmQhMs+%tCaCwR@%X z01g{klltUC_JL_gYcAK`!oRkcCB5tU&uMZCqK3_nF9q1s<=0$l)^zBh%#p!AS`CYa z7!u8oL-wY-l`v1S>nv!;Q?^29@j_8QsAD*bI``*8JDjaJDV-Ohh*-WAGnva-`>B8sk3CH-Up)G!>CUKOA3r zLGX*YPqUNX=h}*jl-MaHCrr`i@n4_JMaGH>*_L$FF=LNG58&^#X_;bCwLaw(!{`=s;a()>;sE1Cpmo4pEgnOLBEh%e(35!+p}-xQ-;h!cHE#rOV- zxTk514VadcDm4;#NMTScADtSq{Lr!oJwNf1Aqc`zHTpyqHt;^J48Ls{Nyu#vu zJpW@(NNqVAx@B!Gv89M?yv?n3Yn9sGM_Gy)|70gZZ}jSdxbL^ALl#IQTbsG zYAmzrddTtpHCq}(9~9h^ppW!*1gZ@lwGa;AH;2^C8D`1FHBDNZgi~K0vzv|?ee35h zImZo^;~bxt>JEjvS1{De*PGPjo7Apz6mkp`$BO(M;AxYnYXmb?NyQa>ZZ0o%qfo#< zsU0A+<+1>XU(}gQ<$h(?{QbIJ$9NGTCzG#{qK61$@Rf6hPEsd8TM<6MvhgU`49JDT zHkJNvJ)D|^8l*LeS42PG^dqhepxCI{%MRz#xVAGj;#nZ_*1Ck2U&D@m{ad~$Ik_rl zj=MY$ZIaQ>t?wN-^Jj^F7RQ`s^_1N`G<|1VRe5kQ$1FzhS>ob2ooHKQb{5^A3f#Yl zE4STQsqg>HeZ-I{0m{%0F@V1ogl69$jI@s}7|){z2ZstC)!zVLplo}l#dXE@+DC96HC zvdC8LP2ZPQ@26^zlua{~TaJG#s!1)?j9rKbA#!1rSmPZN1?UO~G1-Qz~u<&oFDR-qQBPU|f!DhW<@p z^GTmtHR>9(@U3IGtBV0vjs;DKs(7{yIkh9@Hh(HRX8y?cL1APqbT@Y*gfc zx0(G}P*NhZu3@T(+@_+lWq*JnPvRPOyMHL4(|JuutBO^`7ylWr7Dp~NUSI1%D}>_Y z>_m6;L?yO{+(ZY~h<0o4D7H*5Whbjs zYrPulsdQg6hEuIidi4i?_ux~iiA=;@!1oN>Yuga+AfgJ=>i+{xK(fEDt~h0{I?2GH z%3&2+N7^pQCNj31%=(86ywy0x(XHB%+ib*7={#KC@t2 z2dQ*%TjtH_gKCjJz5V_R{!1Zc4~v;vSJ?+I_4v|sW_sDWuzdFg4tfF)5xEUSD`jy2 zgp(305wsY=Mq7X6Qd}{Hm=L>60@p>@n%@Qugi8tfCg2}pjw{vD<+1LiS`_nN-LDPK zBxjvEqzCuBikX$P3(0P~GaZMQ=cfXpY_<M9TIgv*tFGpyv7pwKEM@Wb z`pA`9B66v4p8t~po(J}2U?Fs3iIXX&spYumRZXGLcbjkfU| zZ%PTzbD_gw#8;xw7ST%X&wo7?hralQ^sI@Y|G^~LKF*Vd^91l2{RHJ3E~#=`GuH-b z*$RS?`&tJZiwIlI$jBE>BuPjd`{lU!a|N6w{M01TtPLqHt)TosF^-)`ex0~s@U zB5Xc0i`rCjo$Fz+yB2&h(sqo>5c(MDhv)B)=htVZV5|;KLvezXtwVFLZnwwxIS(_u zb3={3hdN)K#dPq7s-2xYX~gUW$x1x1rGPzYhs6bvSsLx!#nby|Y znK7!zupjT@LkYOV%ONvvf9PK8oi}&&i&|1Oi5O6{hRpDzgUq#9uj-eEs(<_b^Y#3C zO$$c*Z27+{a8^~s@FlW*(ep0y^?5C%9q3s=76>Uzf~fy4;MO1~AlF*pg{sTE$5or7 z<1DnlzG`9P1bQp}a3nq!1KRbxfBgLS_0IjDIxaP{fT3yKTpz8@O$|h$ulzZhKw;|W z(U$Q`Fus$u_O92ftki0SpZ545B?l0`dYsomhilrn^UlFKec&8@tve{+HXR%(g`hSK z<_V(#AnxCPj=I3#|Fv$NOQuUN6J+zf-Xe}2F72Y$N+hvRs$`cUAZ`!E>i+!J9(z3x zyhqNcG#u71(ikS&5K-um2L))w3I?eJBbbjesC}t4KolorrT|MXPI!M%G6@Gq5^0Nw z?cM9a-2v)WXN4fXe|tYO&Zo)5dd-QfYpWnxX437Jit<55& z69Zn^3H+x_j?i5{NKdT~g z2_u(wVf)kJT~Afy0ByE|5KmQoV&bcjFi@SV$W?$ z%ZeQWFepBz_Fz-h)QaH^Z&I-t!-@3ZttZsqgeG}zO=pIOgWj4oHMfy@09DP3|1qy zF7>$BV-yX2&+IWN@3+TIiZyz>r$)FA!b8&U2$%)KDf{Db>RE|+jgmg|hhu3Ahast> z*hS?b*4G|gx6Ki|t)t2kURDFFg&zg=dR;t^o769;)bMxni0WJ-q+=*3Zky*Z6(=}e zr_%q^V5HFpcahEsD;THVq*%_QMNqD!MM>bYlQKjQW@)PBm|ZLs!-OzCZE|8?+-&Yw zF<2p?l*hbuJv;i)3icd!?}9-V=DThJ9!QFwd|vA;f4iqwg_Mg&^7q1Gv%lbUG&dye zT;7cs?K(*-RKhs7LlAr&glf{ASeHN!cbrN2R zNlaC6R$3mxpgOSKnu%-M1OfXJr4P4_MzIC}`oF|MCo18jWH1r)cc6b=A`o-w%8ym; zWz4DQudR;h{%V8*-@zf(?WKys6+_@sA>Zh{#KX(gK zkIrdf`ZQMdrHd|N{=Lf`r;(T{33$37=Y@zIGj31AqOKmuK`spR@NZ?WTyn4l{Wz6b z$DH*W#6Z{(6LGwQX{>g&r~G{BtJ*aCQXE*r)!gcMXaBpF z6O+~BlRmiZ{7bm|^i94%7a&sc@Z%vb+U=^`j(%UAAT8w^LsDb?*| zwD=Bv+KHjHydtGr7|dLd)1MQ=EimF$cU}fHE&`SNw;%H!U;i{OP7C^qfN(2V7;Dz7 z&*mOE5eI@lO8BwyiYBjOt?O*1x9QamBo?jb&x^4gVJ1dN@5{p;H>_zSo++4H0z?|b zCuAS3e0x{I#Z{?DU>m+?wd{vvt6<0L^-8y@+VPBGIck*jD)ZQnS=iUt@8rf_#j!^B z%qxjQacz}mZQ=H`lTqWoy+0ox-@XUQduEGYuju-|o=@A`&=@Z!x7yX&feG#$#gexs zU$vd6iQN1VNdKbDhyZjl!IH9%NMcPd+FdOOmvo+(;uXP8(1M4a}b}Cac!swq=0GjNNcM zHhar{dkxd5uU0gmMiANwSlqCuGhX}TekoF z2=$tKSy*H^M03oVVNJtMAguCWq5nv%;( zA5oo@B*nHVLf|tFS<}u(jt6o6WP4Q#`*7sjGK!lJNO8t)lW#Nj9Vi_yAS@TFpu>E&^>E;PKPYRY7&Ea`j=G3UCFojS6F}c=#4?U|=dtq1RiaV!fJziV&LP# zn?dY#!(yL90}ZYdh{~BQC_p_0l^lzdrR)pkc{KAeqGkp0OU&#mC;e%2)5kb}-t!p+ z^xon|3b*-*Xy%ysJ4hz!ec60mAqifCfnTmcu@2}3mr#gvG$P+<^K6?i1qU?kyDvZ z`2F=Uy4Oql=n>Y$CQnkrsb=Zhw;@P>rEs|2!}<^B1DAq;R!eFFai1u~UaN`}1jW$J04D`6X-f)>Jx+8?Vj0?s!wezbwkEtvjL+Y)1vb+ z42bZpI3W_Am)8K^*+SPMAd#ZvOe|R>Ke_!gI)JVoZm+I=xwE!PvTkQU!>JzH;bRX# z2_$?W9ER@O1B$~K54(1k8N~%ZQg|N`N(y#C?Z3v?piNL;SXBC=ErN|!dQI;t39AWN^g zJUa_GQ|)Ze7=O*QA}&|Ldz)m`gXcc%6yf~(K+CO!Lc1Y1_g)Z-Qh|106lzgkkec$q zDvxf_^;l{aWyA+jcv0=_;5fstjU6i-OOJ6wb7!`ZFV&cn_=Fb0FD4rH{yDj-JhA)@ zD(RLMFLjQMGBRIDd%jQtazgdVbV6w$6)_cKHb8bs+^*MXo> zazR=DWPK%Sm*CLth;ZcU{Irv5afe3o3aMHwAA$Df(TTi9yS?8Y^kA%=l(UPTOF9=) zaSi!lhZr^e+5%W=RyveM?c8m7m;h#_lyI*Q6JOQ~=cgf7xd10RUZs)KrP66QbJ7xA ztpP48pERvgFaWGENHF|7zX@DQK6ZYdm<9VDHpCG$%~r||9T8L21Q)Z|MimmU7W+Nn z;xj@hII0q#W6Ywwq-?Ex9JX1N#z;zW;tkx>SLHyBriEw+`@l{EC*V#a@wp)(56f}n z=$vm%o?x?L;MWF(X>r<~CdPTe5ANN$!Em>F9h2_? zk6at=pCRf%rS_Ftww=HF`YM|?D@_;4VtDDv@BKWvqmb~lbR{JT%n?55%UMnu5QD^A z-`3>vDK>x!SC}40AaLhCibW^YM9U(LU;_&)sh%WFWxl0hl&OUOF21VQu86;ETvx7K zfXWfs-D#c^bRdJ_wVUlD2w>;&9AU%zRQqif-(0X6e(rf_Iiyqe6LMHf#@mpohGA-u znBCQdQeYz?ita zXlU}g3D5!rd}b~w_}%mU^?TGra%soBaK(@?nQ2qX;2j%N|WKGs0 zs^aS@%ohr`*~Gg&g5IA)>Rff3l9Wf9TK~VaS=lrEE=`MNA zSn&{#it6vDR-hp)RX{g%=|RSJh+!GU2$S;TEqXN97=4Gjf;V_UtjPDj-e1qDaJL_2 z9pUAX4H?XuTWH?tl(WT+FfUx87Ox6awiwjuMZ`->ISHeD-uEflstw}psfZtetQO#} zrI*PcouAU$gLr}?6il;rEk5p_GX=x4_6AZFNxW2Qk{=#*wLjsqx};NL+CM)!H@$|I z(N04uksKvl2i}G8lXe^?@Wr+y;%ZlJ=R3|y33HKySz77*QdUdRT(hUjAkBlJ_SrH{ z&-codSCIC0yU&!AkLTb2I_-tj$~4+*UU6?ra;Jx?uw*Py(T&C#1rZXET-1;ZZVGwV z2W^nSwuud#S8G7LK<27UZ{H4u*>-7JEorH^9ygWA@vO~th@7fe*F}@7B9?R@FDD-? z0$Zf*51HD@=kDJ>zGj~A*5Um?^ETcm8{g(74x?XG3iQY0`^W9O5Fx;D;5$Rc&sUIF zu^j1+jHAN~Y@W#`qbOdFOBwB!FmQR(PNFW&~WcV*ZtFliHc3S>{zNrbV4_ddk zz%@3s>OtK9V;%VnU26O3F7L3?6D??WyNpm{y*m_%awsE;ZjUz7@XVCy;B2FNsak%k z%%P=2p@}HwK-$RiHr*+|^`I(eez=&>n$S*%pag`}&@tuP9k@ju7z(bUlIp+;QXVS;6#!ugIkLeZ z-AS+@OOQtc%dB_J;)FPX_B(F2XK>Ia2b-p{YNy1?pwcEM$hA&zOpR z8pY|NZx5R32a_z@zDL&qs9f{k+=DINZY2*3J_$t%hMgIK&#IM>H%YPJG9yI?WnjD7 zKp})WK!2bje?`;kkfMqs5 z$6?|C!icsLRZ(W=1en@&cG%I_^$yU2x(RF!81ROZHR0`5AzmdKN+XE`VCUxLUQrLO zx*1l2rik&M&giAQKywa#`%wC;Qv6(SaH}D$XEef#&ud4+smZ$E`tSgDXn7X7CQ~rg zH{BIHt<0Ii;zfjc_S*ma{&1%%P}N`-txSdvFt$d|db!vu8Dvh?uAB|Y#U0FC(13jg54g?Wj3KTf&+}4 zqP4|%YWUSFvzRM<6%9Rd5^Kf<;$-5q)LnJ?_L8x<7al0D?AT{)>RB?MY{r(T zC6c04UMA^Unw4?idP*Ik$mVsx^j01IobAP4G`OLlP&@eU5N6_fJA*F z+{s4of}>4hEjJkLw@iEJ{b#?47Mmy3s9B+=pnAP&JHKXsV-XfbpAn5SlDZZ^OotO; z$SrDlgC7WAy`dSQvzb*|1P!3m?nw&P4Z1xZpZCY>`47nNc3YLc*4r#3Ks#T`?44~! z2Jyb#-?#hcx1TfpVXWEjv|Ws92N{x05juD$A|9w@@2*~NkEe^Xq&W1oEI&m;hwN;x z*ttaTEeTNAzV;YfOsIYV$rb|fEC#{^p#~iDp4m&W_TQAl8Hg~{v;yGk zDwH_T>QtSRc!81cJUFWJ<#;3@*dRRBlk=g9)~b11&P?55)jvxGY!71bOcBb9m5qmRWpX`%dsZ8>$)&}y0-zTUFZKzC zz9RT&i^wx|h8)wuWqRN_?0B?Edq)nmxF?Ykn0--?K9~ks0K_p3?S56o+6l?x*Bwlo zZXFWIhg{r&AriVh73eXMJ{=Tc zX3+F>Ax&_+asiu-9ow#Vbb?k~uz`i*c5AwP!aeerrMm`e3#mZLD@ZX=9lb(jK?)&V zsy=e{$A*}pHh3r(NK{Sq=hCf$maXY<^_qEC6&Yk#?rdU1(sDeGa)NixkfeF)w#t-A z5dw_plGsgWwqUP`n{{hx0@@R^6@on5)(T^wY&xKtlIm#f{9>l!G4(4}h#DJ00H~$0 z3l`hPa-`l)hWtms?Ww=)q(NK8Q#8Qv(9P?Np3>{T!|?i~R0I(!XkR>#+z#GlFx8H; zvGN6q*$ii6ac^suH-nPv06MTk+wS;kql^_D;JSJg?;QngoaQy{00!^8>o0ljWUA|d z3-}~)PLjDSjHHHDVrev98&_F4)~k9d+((go)$xk&i(K* zGOFBA>?4y1Gq~;q`Qq@Iy1{Z9JBRMsd!DlY`SuF~>k@{6oC!ChO;|nRO{QBiJc8%I zmTRr7!&R0m3lu-~evJl%)e6RfZnzeZT0ZQ*XUivc{5C%}B9s;8!1&CyO%dHkZQCs!ow_eX);5hYZLlwUadXXe zvSqJoeTDzi^6l2rDs{x+D-W)rxarq|Ty4aNAM81IlDmJ{BijX)FSH?5(?7SYb=l>8 zT>gB4=^Z8a_7Ke{J#M1`F;g)9p-f76Mw>iWo{rb*Yp)QYZ*0MSm^4iYnuB1P)D&Mp zc@u&fE+fQo6T>QXX3lds)D6OmI=GQlh)Vy03zN=~mnPtTrBNLPJ_M(}*xjPGp~DC09tYi-fw&zHNt`DYV$&DchLrYmi$ zt$Nwmh0@`;ss{ckP^2Ku(bN&!QL@gxW!9cM0=L;LvwDZBR$Oy4t0WIrJ~C{{FpFew z7!XrluJC^XER%(_7GM10DP@+X1c9OYu2lm-s zd&X%6rX@Q$fjS*jgL0HQ`r5Oy0_@xGq1Da@H^O3Kt(u@Mq1Hh%0r<#5GRZtV>oigx zW$Kj#s}1ZDUYJ;g&^^0WQyi4kg&{tUhlg>xtIRbVu=p#FlGQ$AI7t(@q%Xx9{M8;X zx-3r4ZfmyAel^>}ZJG6GfMG~Hw|XOf6UG5(u<6Fa9T&QN%eqGA$IhP)`U)|Wzq9=W zpjuQRlE}R^{ZBEAF-#1yZ``xkS5_T5KBDf^{9D&f?QXjJT9rn_3?Oo2FPYo+Kc>_l zSa$`A#4b;rO5Ru=7)R!MSWhPIGlNg%by>ofpeS+PT-UEftZk$KrksSy)UHAR3nw4W zZS(VV{G4!d;kre+TAyruID#RR0voz&o)`|WREITRn-Q5XwF=!cgHLQ!UEE3CB$MGy z!22&v4m_L}Vsks^8?ElV;XN?qU7q?)-8L#?u!uZGABmAe-p=MF9WLN@l-xQCx@GcX zuX~|0w$#B;{f@oy4OI^-lZ3>+O=)e53-y?(K{!W;wRXn3$CMIID$I!HoM|{^9X3we z6azcWN3|ck40+&o4@{&P#H+alCM2}%bpkWQtaif2*A&ngk4VZ@cIe6(y*eixH~5h*TAk;}&=e%)wrbb1t<}LDxPsiKWD4F`_pp7S1?E|dyRy@xYUdcv+h8u8%^()+ zC)OusSD=r4`!<$sdN=k^mdv_!zWMy-Q9HI)GuZOh`4Lcg!Epai)7vEz6WbarTa>*P zm~lU4cKeZAjawtoKRJnQtHt|ljv{X&>8cd7sF2#6+bKl$$LN2L|Jg~m=F#@kZ9S$+ zH*{)zeB6Hg^?p7x1>;hKB&+Zl&wP|=IXb$H8ka6hL90Y=^U@PQMzS#Hb83=pz#vc8 zYP1nAq7Rm850UQ~@SN=c3v#^K}q7s6pa5gNo}J{=&X&p z+?5WwyXq9smc~C3sM00N74GM(+Tx;jPs)!iD_YNJAP`ZUPRQ%eR1eVHkU~R7T^_76 zr&G;H!5VZW5NgdKy(6*7X|C0Ny`6W8fqClYwytc`>-QhSfcW({bd_m27sWV**pC&$ zp*umrkJSr!%r++MCKH`(IpiE}H3O}K<0nnjFM}o8*f;eMeD=0qt*Rrv zQcEN@k@h7e6i*I$6fecH(tfcfq4iYLi&gf7B~NZ-E9M$*qTACoLW8UI7Tx6LsKi>R zi#s3j^uujORCqS?n+BBa+ix1TGtAVD+=>FHr;-hOgLQ!ij4I^6|6(p&yM0NSqMZur zM`Y4ox=Cp&nk|vN0)q;smF8Xne(@Is2&Fo2+|c@ev&#Z$>ihKK#sVDhf)F_NryZ_+ z-44kym_x>SEieiL2xV~SqerDtD!vdNN@&mAM}`YZuW7?W<3V`u#mRPljJv$e+NM<{ zPBuP1af@VxHNX?g;*)AJ*N9ze_{!*FU6EX&r_0`0>On?cr!f-t!2(H~A*0JHcQm45 zeavNrfcy0@A0&Xrs}saV&BVyPEYP;woh;5&wK3d9Z$<2K^PnY%_GE8gMD?;5D7_;T zT)hjhV_Vkc%sakmTi8@0DF?6vQ+7nO#hnJz)=IYjLNm3AYQ=P$_f+NKh!XCOHd>%V zi&~Wd)+A-;qQG3py$bhbo8vk?!OyY0Vt*8j0Mb7)QBiWR_)_^ZWDf{be#|+PrFazgvD8e+FF-(4bbaLR6 z_(8sK+Efp4Tpq@`u**V+jz(J4uqjQe7H(Y&pe#Qr!)~{VA^QPMWYw3m)oV*T6nP~C zta_m*)={m#5RX@6$~&=h7U~8hs!bv1_4OLP=V6RgoZ!%bF)<`2MOLbZW)(z}(>S9yaafcjDHPdp(}2VT=Rh8 zonExC=uX@5CKZLf@RE8dDz6H+h<}27bIs>R#t`oD7Ad=wdCoOz;X5Tz0<;3B6t)U$5J9FbGSv{^kVL@WTleJkbpqZX@@8e|`OP5)#HFjZte5v;Q0d z0^&h6pi^A9(8lZHT>8S1B8DOMG^lH40w19_ZJqfwoGJk4*}z(EFumRDeDB5I;Tn+N zR2RfAB0AVukqG+aeT^&LBX;UvwcUHpu)vd-%>K{M+vCU25#sp$Pn}n}jNzRTPev`I zE^5j=^%*99^dTny2OG5B=3a-9-N3RV-sXXal^0!}&9lIac7N7yZrd`iW>QJngp%|Y zY`nb^Nb84-z>2}&KYskX^%<4Y>a2=Tu{Vn9)T-v+RJlI-0?c{bmd^c+mO1`FQ|i1t zkZrQj8EZ!Oju*nt!Xg)MKm0`&(?K6bwQ?MUq1#8$;0Kkirk9G*&f%DTycM$fC^z~%CbglC+DJme(iQU0V~g%?%JxQHTKz8|cgnh! z7Yhf-@APCJxf-(!ccpqmF4EepzQ=sr<8!7HgN{FkbO_90Ge3O$yb7=n z)wDCG?3A2$Dzz)0n)zw@X)@motrfwd6FiulIMo$5lON=w%66ac_m{lOJxR;>XkFT_ z+EzOaH4Vd0yXqy|$*j#0FPzd?OGZ6Ya~P15OpH@faa*$pQq}t@ra)N+5j*X%&b5<} ziiI2_(O+*~Gv^S1VH1fh(UO1m5<^F{b&a$(Dj&{fS)NyAtk-bZ|CwHoZH8=#trSS* z$vj$xK4rbiRXM0eVtPBXu6E0D}_LmEme-Rpq3Z3K4e4-43abGxE&5(7>&7+FIZilP7%Ui`hqaf5};ryV& zr)U$=CNB9fTMl%QOlwvdsaEZ%%FK#%7H7RWpdj?nq{!m>RP%+v4O>r?|8HA#24_^2 zV7F6u%Tu8ZM%H^7+K1R?FMbzibpaApH_fUxqz*?pf@)33ORGNiVjaM&_(jxQJ3l;M zLZzkh_sX6vMCC(FWP}=|&Go&P99X*GmV{}DWq*gevaXv-c+K__3(a|$c5*_2i)f=f zkK*@dU_oaml_SxU^g1fC>or%CM-Y8meA<*NRMTt1x}UVc=F}}{sS$Na9#kAA%!5@` zL7&9aDB6}FgC5U?Kg%~!>sd(D_ZR7#ehVZwoIO!ETQ|7)Yo$_TuC9je0?*tgoyg)S zt$THPacdK}4%9b=Z#*VWt~sAkWvt+Z+Lj%V7p2A%z#AwU9ToH3)7PXufWmo_cJRj9 zL{e9Aja48Ja?wo1UqguiDe4H=ljZII%^l4s#I15xfE*Pd1SyVx+TCoL)CrEAgT0kn zxAV$hbj3 z+J?4IV5f&MgR9fox8wZJL@beQr#d&r5B)-(^|{3hs>=kH?1edh(TI5}H_bWP&oVzt zF;hpnHhjBRHmIr5y09f7IiLNn?NJzf6W>!T78C!xf83`9BVPc8^O`&Rm6-~U9!_fy}$^$q9ma|7p+?B(vXr{7E>Jj<9hc^!VUHp?qy2j zru5`eghQPqWxxP1^nOlTjpON-gjp$v_A4IjHU+NnNMFB{gmP$}8RNSCs(d8R*?Acp z!WFv{?fC=3aSOtLDvTn-f*>mWhD|f%7yNgG_!!tt^w&&_PcD>M7HV?=)NUqzK64K) zQLZ1giJ z-YXBWDw49A3!c9JXmmIYPS7+NPn6Vlt!JqXc{B^X#aoC#zZK?Z$*f!oaLS8?Z zDHv2BI!#^degm7jDO+?{z@1~=P5?IK@Bl9sUV!dg8?id`-ugQ!mG1s-thxg`tmq7* z=SH3|&xjZSkE89^xf35BF9$*7MjH2EEHT6}%5BAWl9p8K`{VxO$H;vC{a?EdUFE8> zpU^s=PXPlP#k9DFT;-Yg`U%%}`a(HFhG;p6RZkL|R}7cq!~=lzUOeUMbTmrfB5g&f zMw)-=RcT1Qm(&AW)0Rpd2fWpVyH0G@M8(jWU(1SvEm%M)ZKxJGk9Pm@e*G4BtM0K3 zQm5^$ups?cJN*%t2@rVyczpZ3f47U;fe?(#O=bY2xOsmM=#DAdZpO`@c|JrRsDjCD zTZk>`JxJ8?&!%r&7Ehl~b+e(DFX*30xOAJf=;vpJ=oH4dJ%K#=sjthbEVN&8f)XOk)>RPnjSmp4$z3^LxT5g6-86ZJ_1`8 z7Hl?Hl7t}}faBhG4|_{aJrSo)SOep51j;XU#*NB1vT6G4Q>3UZFS_qqA*06qD+f57ut{3b8V`LTQY7FbWL3VKp5M z2ap8X?){{xY|z1ljSmQ-pvvcyXp;=@Y2Ax_AipunJKzbc6h#?}Gn|bW#n_9i!orM7 znS>-9lXlKqu4?+)CZ29QVa8kttWVHWCo>uS>jQqC2UXV^$utBx9o3m;E9FXUrFrteSJ*}Rgd)I*G+@+1iLYQrO*!GP)yJkrYT-oe|CpYzaPzdR?GQFT@b=07L3 zU>%EHD7xu^j+zzCcalfg&gGNUSF}hyahTD6dd_Tv#^E;M?|Q8%uJG5^5H2+W4PFJe zp&nkU1PI~jHSZrk|HD!Y=c5;9D;ZZzsIz)Bdisl9ednO`S2m^DQhfVNtk<>>*}poD zfDKFm4EG5pv`Mj}!%yXQr7l?O>wGfSGttGOAA-B{@TwkZ00!(arlRcX6}a7Qj~|mt z|NiH6eZoWEYCL%er_(n?S{z?ihsc=v%_n(8G(0fn)u(8z+F+J|fcqw9Tr|_nWK~rz zogjP#^J&bf6AYf|x%u=nMgGzhJ;|=D;`UioYNYwQ7B5XWiO*{sLAwohdu&@abb`d# z(8ulZ?fvyzjMMgH&u>{+H;6xj>A@O6b+IorTA%r&&_15&hV7A~pfiITK= zZQ3*{7T~q+G*zD#qjirOWHu0rImz@N$h-j1!`}PNPMSQmaW*LTRs6wiC0zx^wFzvRMPf46PiepBj zNHUx9lu@+}znF|Tc6ED-%^9fPAG#le7`BDfEynMId&CS(1E;TP@|yr_GK6b`8}ljW zSu?wG5BzEdaN+)lB}+Axsie-2`z1lN)`s$69OT^s>Dp;3B~wuxUB;o^=EsnB_`JDl zJ4|$?VuRAABR2s#SMLjY-n{;EpCLNukj8w&P)_tIckFwWa=s21#@)IC{cB+1%a= z{-c+r!Ox!j{tN2+xtBJP!!YOQtKFbbsJ=UoB8hw34GU{TwP|xX6VMI^RAClg?2)iO z9_1RtlI|wkSJ*2ePFY;r%EE)@yk%@b!CsNH4H`$^feGG1EDKC(>m1ZE>Cbg?6PtwY z6Kkv3Z`L{jc=94^!a`kf&v@H#+1mBH$hllQL%{Y(p5RKGe>UxKEOKXHE8v?X-fWz= z12Pi?FNcajpDX4CWE02g#~QTwub#v<5}r`1F!ZTnZ)iBhIhe<08X9Pu+t;|wXKo3* z(xCdRfz?$--~J9CU61K@kK_d;I(YIhW=-MuW+xTQsRh?uLX zKy!hBMDr*?uj+q8xY%@Yo%XqHt0TSv$L2w4ktLMf6WS;27>-JV_DRPlS#vtP`OUa7 z+G(>5fC&kGq3S76ecs;BFIG=I^DCjK81OM=`L1e$da<{^W`_+gsKAWMG8h~ENyIV` zkrOJ{sV;goG)rD$7GllJ*)-`W;>a%4l$s<5bOwA|3G(oX1XhAEsuS}?_j@`&f(U%Q zqM$XdBsE25uh~o?fE@dP*`9~}{%!v1E9;5c)O1CjX87K0d*U>mwB_Vm1=@6D=?>7a z?#M+;j9dyk$)R(ufp=J|5n(qD=XsW`di)DdZsNHy6@H{moxZQo-F^_f0Owhsy1^Q; zegde!gN>8i0d{N~m`?t4bAr$N=i|p;!&v_H_wrB{u&+y7ohm29HvVkpUUe4D8_ZdZ zWc%G>v&!u8IX$Eu38-~B^5_eK4dEL$(+W?Y(vpa6p>o#K2iybiK(!aGQfQ7g;ade(g7-R9o45-J{ zJAo;kD!RQ57I!*pj0RJ?GE5@}=c{J5wJ)(Te_eB&rTzdaL@)yd6mj$%%GQlyG$`?m;KlwLQP$kLkmk{JN} zc>ez7fa~&q3R~p7xsUhiXMpc)M>e&V89bS6@2<+=oQ~%$Ca%)2unE1+!1uNn5$vf4 zW{#^!5rO-RDQ;S9SKlRMYF2ESCI!F_l}*Qkohj{DSYT}MXa7}aFs%v{xCZsuD|R4w z>~^OgI~QQFsOriL&Ru;9U1wJSORv7VA9=!2km-e{`j)Y~$5-q2^Fvdt(=BTstDHB9 z?pzg31T7{3gVcY*zTviK4&_Qbba=WT7RR+Qyt1roy_xWG$v!eP z67(0wZ?RU7x=f#;|~+mRqlSro1{F9rv+fkU*c##mwVt>r#vrW%Ep>|h5#Zqwm< zx&sn%ca+^rWtE+?(7b5{>OoBmq}jJA6e|ZE+83t$>#Fg+mdk`l@BFgBI}DP!Jh&KzT;y zNOLtVJ163q7(r98>bB(zapmS`>@ZXiL5H;_&X}Zgj1nyz?ujOP6TTfWdn!wbCj+eB z0i2+i1mV1&k~nuhQsa~zlT5pG##hiRiG0sgoI_GbiX}*k0?0XWtf3TZvYf?F4|2Lk zLEx|xOd1#fbe~<^G{^b5{h{WNMNpzwzdfouHvZwE-{hUT#*JYa2V=~FE$YPLL2nhrJ&4~yRlcqPfz zacMw76L~8pl*=Q-ArW3f#5f2b;N|@A=pqoVO$tcuc$?3vW`7mq=jy95ew}wzSZexri#NA&?#iZ z(uT>42TxC844>_c*oO(wM+@ndyV0U^#k8#hJ3oi}kOmJ=`zc)Xw9CaQE{o}1JU+Dx z5Z`)o=fnN?O13rR#LBNPfxIP3O!T{_p3DZ|Y~7*uw5bP8_{&DpQeHeU^o`sgwTA|q zkPBOXzl;lQpgG87RXgcev=TeE_L&sQnsXD~!4Q>97KS0270l??i$7^QB z$?;lT%8FI1>CNvF$$uXQ_xrav$Q93AFnlc&;!U~m2Wqq$t&K2*Eumol>6PUE<`9#g z@6PnW$OjKreQ7ShC|@gNEfW@{sJYhVG`K}O5I;nx zuU{uZ@);cZPG9cr`_K3D`TYH>%-<7^d8pM@ytMp5J>&D!Z%g;(g@@B-7nb>}Wd{Yr zw>l0bHX-6bRE14R7AS0QsLkzPfkG6@4X%3w=%4h@wLBQj0)sC8v|zLj(u&hTn(@W^ zPvZ{O*FP&##|HutEkS~v-_AABp2m>K1zu9<6YnDFW(IzSkISnmbo~c$ro2^{#!eY* z^lhKc7FHX8OkesE({`NHlKr+R}+ZGJTcT68i@|zC8?BQiKsHxNjH%-~~Z0)zS zGSdL~WZAEkPj8E=s|bg=nGEX07s-s(mFVm>3<(Fm>|GGU!x~X*x&|Fzu6nJulK9fv zu7QrqaE-O{Hkl={&eHT;IQ#Q`gLc(m`u@1xA0J=o&AS4=h5UM6C0bS8RSIt&(2O@XsNV99~9CzVqENZPns#tcEU^?Mv!HaZo1o%AJr+S3nWl# z^3st0JitM^ts&@83hQ0=1XhBEz!`)JfE==!^%L}LWPwud7xmBGqjKn}+ zsF}TU6cXrjSV8H^1HkVPn_0%JG}H*n8hlahDIV7Rx4C$`Ew}cb)`jqG0KTYRwmZjY zU%?zXr%e!WUklhQ-N>A=6!OyGPwks!ug_HJ#I;)XtBRXetBwOMLz_gmfQ8|y!QH0q z3md>PDfCs5&ZaR^quLCbR2hn7Hy4nuRbE;yP2SqTV);?#GdKM_@(Bji9$PlN@gmLS zn#5pvBvC!D`0;g?6r_@{O!)*W~EB6hGE=Egh5!kMS1|5UAlb(fE zq=_FuyJ%orBkI)+%0kSluIPrLG3JJF@5}JD=!2}Qw;E@3!imeF-Q>R0_+qguN(&Mi zCX-Ppa(U$<8T!`OJM;J;HX+YuIRb?%#sE92f(?Bee>#)=rpk9%d&@;og3rTCRo=Sb zwdT1+3up0Xo zfnzHAHWF5X)cf32bW=@JU(Rh0PhLc~uJo69nv~=lWY@^{G)ap{m{REQQo~+a+!a#UAYx?YfBySs=Lf7d@~Uz4 z1TN-x;TdGA#AypT!Q?;3SzA7E8Mf&{r3ImFuZ>K?K|}l@7dl;Z>QaC_+#m6V_3T5 zwwa*};Bt^G|DIB_P3@bQoKWw;sO`d1=&L`!WSHHOW-uFWZY9+rhc$1uzm`zAi&~ZA z<=OktzUBq-U@`!cP%hY^>i9GfKkm2tx7U*v41+3APy!m8_&eIuc)FTyz-);_?zhJy zlk6vSjUS`UJC6|!|6UdPX*ZMfMoi6tOO|t@@AUiJB1J5*rp1q>=uy?uveut(3*gSP zsbjXv)d12bsZ|2CIW@D(zuNSH4V&|s`VWK%6_J*>AUT#2DbHp93r51+vBZsrA-$pZ zKM2x=K~52(A;S(~=#gvPZH3=rL|0>J-&Px|yyezFfxa0exwSX3Nma7N!=#fn*oFKC z%O-as;2Z$(Y$i(W(gY7%`3xPA@fU*(a+Nw%ao?D7M~5`<&4i0i*X!{>FxxD*?UA?y zzWSc2Y8HKYZvlT%(QFNm4MK~zhyPIIkWnDK9g7Cbr-9K&IneG78@?>YjuSZ$nBirBBX3_95_nC~*oA&htXh(2%K^K?3tAMMpknN3 z#}!}NsjO{msU^`roO-P0djI#I)Q$VF4xyamCG zw0%E2j@GVUvgX_u+E4`685;o^BAus@wx}+biN#|H<~xvnF-kDOeDvb1^397 zk`y6#^R2LI<(m^^#KMIB$#!7wDh!DfuU-xjj<`bG?77$B7)^gxj5)lSpgz&)BCOaV zxu^uyBgDw~P&K4QhEa2HB4YyO=W`EA-H0F%QlLku(T#z|C(It`G=kHNj)V zmsWR_J(UU5{skYeXKiUDThckq%~sV<1U`eZHumn%jOlw+Q}9^RoocV4xH!nhCZ}(E zLotNAFLq+TX1gGobM6ROgGvIjjg&~`VsDq^)Ln?shEM8)IUf-I*T`^`IK$)-lDgh< z&@gOUgV5P0+k9`C*q85ner0;sGrkX^hj_!5<=C!*%ekE2z5(cDaqYM3Xjko4fVPrx z61LGRtnw^PE8-}M-EJu>mZueQj>R63b=R!kwHsZBE18KwW-P1mMj5py8ejRzC4_3W z4BOpIK!Wvgmue|Zdb+#KzkrL)!Ije+HA=yJ;CY46xxoKrG{(x|)KrtzzupyO@(zRYfIn?}LYroXOBT5OsIJ8DTi z(fO$;n6m28fT*61)=HgO`#|c-uQ<}GZZ%A}+AmR^{c~sP`uEt=kRB~QTD~%%T;M>> z{2gX2a)ZG;%{2UcjxvL*v=ZxGTT%3LG(3gS(kHXTg9x;cy|VMsEt?O!KOW!zdcU7v z|NNKzV>Cxhtur^0y1wX%&3M7Q9M9!?mGv|q5{1$Ne!GO13L5$g3spy_{QwyZnNzzn zKLXL|@;QEfYn3{xHF%o#cw(F!DQ6quA<=d^SqwB9C~k2{i6`%ZU%!L+#;GH%dZy-> z9S+?PnEdnc?UfdcMIV!M>}j$Dc;$LgX_2vo`@cQ1e~%6Y{Ctr-$O{c1+f8kB@b6J1ITh96w@AC zKE}SZ2~d=Iqx~MSO$hHX{vBN;j+SBUSN|F_B^z8DZsS?q5M_L)o2(*HNG@OBI*|4PWGAN%FnphbOhuOAAsIb>%)y2g>K?NP&>m?U=KNfBHnMp;%(`VU8*8>%TAVJdpTQTswRoA)Rd?DvaJuH1)ILo-R{b7Ln-|o z;h#4eAaOPKBy~!GtIUZ@M7!Yy3Ehd3>@@EI+-gf3!z67aa+TX&fP3Qv?p-TQC;Dau zkTrB5oIyq;@}0zp*f2>2hJ8Dg>)_JP-T6LvWNK#Nhf~qlWIG~0A>Ap+tZKdBqUgp( zos&uW%$SM$ea84)BxX0v&bfg{U>WJSVpn5JUs6<6Ru;BM*&R8J?)?!#D|^qNgjQ_x z*At4V(9CZmujorA+6d~m+*q=ahEH9OGhDC{OA#E-p_R~;2e1Nd#Yq-=^E}kfB=RMR zW6JMVvtRc|GXLk8bUX?yxH6G7#T{tc<5*c4!^-+2{_@P5X*y87HSX>DU`C{W|bKYwSSXXLZgRa z1pU_0ge$kR09=a09DCW#ysa|hVbV2_hOFMyrbrH7+^})}9wnOjfrZ}^rL@iVQmyn_ zReId4plZbV$z-%Wr^nM-9aZZiAWJW%;-*eW|GY8B$H#`9iUL$?LKcdG3`xpps97Rq z8rPY0wnGXwk$-piduS;w|Lx0vr5 z8p1R===cs=)W;uw#kTL1nFC3p33BvL#^s{UvvbzC2hn8A-$CEfy|P#kmoE z>o)=J3Yw2X(=tJF8#m=Za7Xb+d}tMNwz6mjOQ8o1MpYy#a*Q1I@&zb4q?l0n0z{`M zzlI6t9>Ed0DmVHvHYrlD@f6#WC+~npapeZv$rEyt)6H6JV#(so$WQionLT+Lv}81Q zP$C4G^(q|F>h?c4a(S`m$Mfs+iGebGa+)}~Y-=c%$+3G;Tbt>1(TXxfarrDcrs_wm zC0uH>R%1CXY_V^;C#sGy|DL``<=>mG+k{R$V+5WKmzLBwAcV+vdOS;N@LR0uUMi8N zEqp`w)HzAE!8I?)k!JPdHX$LRNUMiPD)WTOrO_m>yvPo;5~D5qxPSjSLLC46vkmGN z0@E(x;eG+Ck>8UP;0BNi0+# zU$BaS?aScjjq#S!m^?z1w(T4Qd>cFu)A8qjh&!)ogPj<)~%@fc#5N(W!_ zJeWKMXh2c^o4Cs=OPL!Ur0i5PIS~*GmNn2H$s=XLwGD|x;lW=Gi(7VT?!1*cvtMqe zeXa1iPYHONsm4IBsE~djWX4(_iUF#2gOLZ7!``;hpRG|>wCSNj(?MF!C_CGJVp75) z5msD+Iss+ipMG`Oanbr_Zfm(WuMD`AZ>;0>Bvt3SF{w6L1og1|2yxE!+`M}`Z?7Q$ z>@r_c#*yD%4ek=*D2ky4oARUO?Ve|}=#VL~bsu=gQl4U-#2L|!i2ZE2A?$$kg6v57 zea{p}jNPZK;mN|Gpdl_dg^V%EpDj^nb9H0*hz#k%)ZviOCh+&Q`P#MJr~J3$OJ z-%eBZLj1*48ae8o+enk}I{&u;X&W*7I$1F|W{@5^S*zYxqfFt+`N3`jq7M#taJXZu zX8=uBoU<`uqb{P0#_kxmrfn)5n#zh*E^=Muqa6(~t8#}9lpw>U?Yb5U?e5iR^q8%l zNN)?lI+JDXvfh%*Hn6~uqnH8Kl8H!F2y&ErptR?#e90&Ire_qlcAucum;LVebkfUH zF*vj?-z5JlR2S(y!2)W*l|0(v6D&-@ap!`7X?2J|V;jl6{!YnkEOvF)FH^%?T`O9!Ow~7gW1jhcqKSi3> zel0EV#Jj!V#zOMNBJj~Pv5db79xr8NmBK6H)NStht+1=hUmT+i4QFJml$vNErHth4 zktpclwkn7J{!EG#BUyFXvd?J|^Tsh|J9*0O@tAe}`t6vL#!$xagG%t0oA(OY?Fzzi zaM3$ThNT(VZbxyaKd~1uadiq2RvQ`t*7-N2NNhvM+fki_0hgs;>(}xX2eGMvCu&nU zNzk6V6MkZ^spuazDwL&+DcOGxOR_prAA;p{U_5?I3&v{_%Uf7GH=!!t;tKcGzVPbE?A+;gQlJg$C07@%_ig z=jYcyf18Eg(-m^0_;6;tZ)Yd8Artc(Yg27$t4Tt&UJ7!Hp4RJZTJ5ZObCclY|81zL zG!dlhb5-!Q{vipqrxvI0yrDYhZ9l8(l53u9+90*SwxBeLQuC>9HD7_=O*ch(qoc)u zcEkJm3&GSrOd1Mynja3roT&=f3J$G}o;2?>fD{1q)CCAi)4}-pdgc@HWu7V6bQV)2 zu&lAa7^np;wsFOOuw123D?Gi(%>)%9arHs!!qpKOe3*6`c`m$~)78u7_#ffZO=H~x zRVXTvHP`1M^?d=5+=Y=|M|+q^DXt}%-du`ms}SH*rekEuHg0VLOMUdFjGJMt+3UbO zA*CZBeJPFDhhR{HsC&{6r9$=;y41sugV0ZY4YXZo9YeaLkdNp4 zrM`GVF?-=jhYP1{7%Bic|3&LM(VGYtueTM`CNqZ~j-NU{xl= zm5@f2rwQtI5l48V-e5C?U~tBpbpL=L7m?cLob6Cv0=kH(*0GuROtb8V2Zwc*g(M!6 zx)PT~UAh;n=N7G(Id{P$8>*y#rzP&IMLmRDbcJv?lKwAw)d||5E>PI)om=yZv|SCI zj=zk=Kwq>z1u2s#;DTusH}R+IA+C$+drQIAKB}|RJ}HBxWHV5wdCh6Tq`Ry|(~}|d zWXg3&7Apo4+S6jPMCul%^ds^R=Ls@0{19Yei_x4Im3T;Tq6RJ_%dPpfDY>xkOa5T+jxp<9B3I9kv z)=QXBiPf)EqSBnC_*#y*u5E9TNUqJ>gR}(Zt%0fI(s>>A9c$d$SwY5Kth=*yx!viw zIqiX4hukmbuojz*-DL-~k)cXopQn#uUg!Sf#|+N>^^Y%W>>*&`4Xb4I zG`ED4)68vCuf}@8ZV6Or=tzq|l39k<)7B>{n(8LpsME7^srJ*z+T1%kyD}B)%$u)v zg3M6}HSHASY_O4lWLhvTg@cRubn~mD$k%I4pn+f$!>AfF_<*bKW|J( zb9>VO#;tt@5IFHe<+unA1|Bx1HkHgp?Jer()2LhJU#{>TfUjplE2-XdXB(*NyyW4H=@pM@0Yr?fHzF zuKEQH4W*c-(`8B@<7(j!rK$TO(4bqpy+gUlk}!fVMfmaZ^UbgKmr=wfFsf>nuig+y z4}s~e+@?(;M;@JIq(s=W{ytbq{#`Q}CS$-5;2R4)lx2i=y?@#;v(Cms3!ZYakqK6;2J#wPtnc2L0X=8`7BUuo%)p0$0@7U|xg7%opXq2s+jhw@Xc! zr>j|Mvx6m?U~cu%i(2m?lmKisUy*_K0QX!H^bVXo5cI4uD)c`g;k62lQwSEY1EA|3 z0O^h4El}QfC;O7styCqKE58Y@A@u+UHRY^Wj7Fw&E*24!9X(+I`%VhTRhTIOHA?6KhNXq!)se=E?l>R)zxmO9XLazyv+ zWkt2_QX98kXKVLDcCFnxzPM55VyWl&Y;_iT#{ro3m|fAsRsLz5L;gR!1|v?UEv=7B z{Egf%{D^cLFZk|-A>Y`;yV8tGMv1x-QML%8KtZHy=%jr7UIL^OM7%J>&7UqSuwZxPJowR9LHS{{BK^e2Q=58*J{DFcLFxscn ze!Z|U_-kz9+LxrdRjCg9nS@5%qv|x%6f_qqtmDdBqde12CIMGYWo8-9HytZiH|eNr70azfcOQ80Z*!z|Zy*coex1e6+3^IGb>bbadOMUi?q zRt^E9^PG8PW}{;&Sp*0t@Q)Qr=24UTU9=c5+U;o5U?e?b+pE3lvN|8E_HFZrj;;{U zSvnpF6>ydf>!f^2v@m(xR#fBrhK6gTN?2%vbAlO>ls2CFpbG@HUK^cxtE*d}-NDeo z1nsu%5LcqijlTgDnx%M!y!g~Gptag6zWRtfRyqzbPX!Dy*2EvdB|?1-#x9yQLuYf- zq2Ws0ppj4v!x>&4-D&gWlt`VK*-!z0 zv$UcDC#(b>HkWRpniw>cfD)25(k-DhB(_ThrXi7v;45Evd{UjGWSM%C4vb#}&nOx$ zp93~TG%XFZdb0Tu<}gz*vUZh_%m`h6AamW)KCqXe2Xa00isQQqYeI-99Jo>3PvqWP zIg?*-iX$N8V5jDV8(2pcxQRCXE9QQ{5vLJCivtj#=1;?ShE1L+;frWkbMVs|r5VL* zN|GlJz5hK^QW}bwg-AwS@Ksl_J=sS>Qnd?VVD2F~i-8CKgBoHdo^FoWRj&tw{o~8*(bz zTvXI>t;WJP%d9KD$xQL$JWClZWlIGURR>D!EP=Dms9~{IMK`PrYHiI#(Y9oqtQf5s zmtnb&t#!pJwGn8;e>A3T`g9fq{&mF%H__^vc8zx71&}r%KM;jiRgF8%@VP!cHjSf7 zt}cW!?VAhuIs7m?Kc>flQR0JIy&-bo&gR0(QJNAZ`U8GRqnA8vW(gG)gIBY$ao34h<(+o_sQ zN$@89Xo_Zv0c2Fz?o7J6K(L5DiOX9EtwHphx1oQxHM#@Qsb4V<_|ID=4MqQ*@k6DcPu7|dzjR>5r5NbP5%5JLMdOSf`CWp`MP*SJ zP9cIJyWHEdX||9XShJI!@F|X4EQZ?*{{)966$%g2Mltc1%syynz0ZZ?I(V65fsAeQ zlO?0ZWH^tL2|J}FpXQ#Lm?c*nGE|$YTII6AwW6_#2ZV@XyZiW#Q;|CTiRw)46x%98 zi*VFV7cb5g3-Pt4hWk-x$I)5L%6=Hl!D>_RZ&=hE(zu0!=k70jUerow9Y#P&C?n#Kl} z)%vxpE&I7T%4-&DYWM%1NUPGgrKoV^DoffdVcjV06Q0f)Q9pfuOcZ8q!hIOyZ%%Qb z&?Ej)j$f7CKR>@c=9o?4P@3+7WDb#?j_SKsm?1|;pJVi1HK2j==fi3JJTSy|P?;@V z0)Y01bX!E$j*#%8MMAlD{W2gg4JnnD`GYvHtL&f5f-tE)`0b`@_V_e(Lh{0Gt3D!n z!=}`UND{&*=2A_GH}V4c=l=8O#6!O#La9qcX{1)IBGf+dP8lhX&IhlAGxbgaa}DnR zP3<|boqTt^@%U2YHj0)E(}ilOrGmj-E`YfN6q_rt4#(zOPjX=b&;R_7kFTLrfL|7Z zGMLQLU();HiI=)~Io~_2%=mc2&VB%NCgSmJz?(|u(Z{Y#=K1_Clect(Q|P?{i%97n6Nae@-7!dR6z(b72?^8M&RR^Ejm|W@}*%d_NM2P^W7x*O3-Z}JS99A`rwnvJ;x2L#s4_XNl zji#0L4()O&TgSnzVgQ^I062WT9eYAFwX|!OTkx^Y&Q+82iU1+SQ&V<}8{2O>jkpQK zxhIpITiPP;g-c?0yEEE4{3YFr@;W?6mp++mn$(W-% z*4WBkXxhlv(g~;}ByG|WPqzX*GA~-jUN(U=3svzETH1=eJskDKjt4YU-m6x4l1_1@ zj4LkC<*pAX)YXqLCdI^|?^;-0=-B5h3F-9QwG3ry3XGZ0NtY>jK(NyBCEs4Y@WRCETCZONDQTHe8d*=F{=6^HpdO?M{L%b#x?yEabCb`tT33t$ zMXOR4azB#*G&(5^NsX~7nAxMJi>I(cM%4J6Fpxog^N^4E%@$aRccqjQbVijTbQmT% zbfu!k$C)v?TIxhiic5IZZ?=%3bhyJ@&mby;^&ke6o%1AjjXzyR?d^9w!34R{B1i_l z$OXyA3<1q#HAH+1+UF@9#>fnuEen$sXzPmP&a$UmhD{#SAT6@h&uaybyQsZutun_Z zH_xrvWXp6SV9CVF18R3ND4of)XwQ(svYY2`+sYQ`yydby+33+&XOQWijO(6PuwCLx z!J{_ThAheXdI>klZYeoC()ti1uK$o=K|9*L#Q3E!TLX4ey4Wp(K=q zs)47OdCD0Bb6=vttO4FljF2~COvVZdYL+8W z5c3w6xdNhMwo*2hg+8`v2}D_EF^94_oy1k9aoTp$I54%wbqGx;=@;)jl5$#4ey{eX ziJn7rl@;jG{+vOQMs&pWu~&xz%-1nI^O$Z`5Be0yQoRxc8oMC{L@^C2_2-?dR9`6+wK1S z=a}w){^nye6JCl!8&V%zbzRngN%Cg>X>K%haBHihQA&Z)mtj{XC5lVEeV(vu@@*n_VB%$nR!YWcuR!6NN$&3ABKAXLO%l$#|v+^wbC6sSkUt zDGP7bs4zgWsCK?O4)Fe&=$vIv+PQ&!cz0#lU%q$}o6UyT9h6I3i0<5n3O%iYrBHh5 z+$*XsaeuEph8!1rn$92>U;rXTMkv;c?D9_Rx!FSpTeW|tAgs3v-H$_q2#Q7hDery1 zjjr`hoTf`4TzJjAVB#{83N&6NKQynW(5?ZBe2;vSwZ3k2JrU`6eWAV3E!RsFgysNH zwtq-*zN#3yq@q04Q-cnW+(SLUVWnLS6GJXRzicK;5g`x-ZpQYdl3IqlKy`U*GL5I}M#2AuF`%@|%w`m|{_IdsT^R+Lwgua|}R8(ON z04*K<3gAgn`%TXp-xxIOU5MGmnfdv+GANSoEEHe zPf<MOAWvud*00M2Wz}4I+SdjH03KEIX-zo<~c6a#HIveQ0~@yHT~=VZE+%4wms| z_`>cO-`g=t4&K$2&LySw1P)Z;{jH8Kd)&DT(h3~=lu0f$0&J_q34d4vB!n-xET2h9 zi=9CEvZRuRr{zf0yNb_kjdnkFC6C+vXI|={9QR-Ea#qt4KSswdU*^ z<=VqP)tOxO!M7q~mnP~Njz*i_cAXl0UvNe+OBUQTDru~Pd!EvdOKpSIRYF&GyA+|%=1BM*x=Nq*aQ|qJ_^p>|Y-JE#K7o{v* z-k;$BpHQ&+D!H`89@;;=^5P@b=(eR_Gt!Od2Z=r;kNoyyy!=0Z_raFyg8X@9%nyJh zoCsWv7ccU1)3vi#|Np})$D7eGV&M8dnKq7~6| zLik?24B6}sneLd(qnpu|yn{IO5R~}m!Y4bwnWI}N87y{2G{3$UA)@4ZWMkThp8#`J zVb-g)fOs3#gAt*e+Wy3g@2}_Q$nz}M8h?M$3gHcU!ZRwI2KzG!&5#IPt}Uz7=2R`u z^hx1eB$!U8Y7;r)7(dfOd}lWo)zgG=4h}_8x;j+s2Hz??L!cpXHu*fhbHerKsu~z6 zo*4>;i-+C8z1@+7$Zeog(I}vx=V=5@B~zI$h_scNje1oz^j``QU#HR*y-Y7_?n3$# z3F_8}G&YsaW!TL2!Rs*1TC(0A8Q)H&S-iz6#=FHG;%97iSJ->K7tWgz+!SJBRV^x| zK^LUfl_g>}&rjry))|E?`mR&o%x@*s9aQmAyWv=%^k7q0XkyFXaH28}T&mISP7)$v zEkrRiCR}D&2?X>^5?u$U;eZ*&&4+(J*P%He4p6x#lzJn|QY2Q`j#QZu*2lfI4AJqf z9a_|>x6P%5hBao>D4`rs{*$g+PJ7Zb@}Ig>4yVEnr?UtlfF-Ha30elx{WKB(Q?j95 z1Zh#+NV4OIndF03I)AN7W&==q<{KT>B=Z(S&{q19mIOz{HFzS>iM0!$gl$ETt0kFlL+)?|9m~6{loE3fKJT}& zjjOd>s@6(W%I~Jz%1TpvxrHKUPGIBFBm#-oH+;YZnt9y^qG?#ujvde)T7*&;cVf;) z?M*}O4=3puedb6n+hGexJNQO{0IvL#$`r>+zCW`tnl#v|Q%$Q4D5wHS)-A-1-&9Ss zU&c_*G@8N4m_sxbK&iG{!=UYaTRK>ix!tEb^uUlxFM)ce?O776ywekdF^EiYYLF@; z-^!>CA}~WMF)4e&FL>5`Vj5tJ<~2s=eTM8-$x`N2XLLouWt)RdLc_rX96aNDa%O2Q zSAUAx=jGkBKes>AGbmfk&fL6U{76h5tb$a9ECV&AIASy=OdjL1^ozuldDGLRMq5U} zA}(_T;)RDgLn636Q>c-@(UxcULghzDe6dV@MrK%U?X%wDQbMB$PAH&lK4Yi|%eOV8 ziArB{v5vZ-#{&(BMJ0qyDp<5>9PZLow4r06ztV#Y5sXbxqi?yiKe$F83QKE&%AT%f z31iRjYXT7XMp&q)QfpeZ5#{2NBI}zlwda@2?=c~F=g4E;mQr>HD~Z3KnQ=XtE3~l; z*AsC20N=iiy-K;>K^LtE^kCJbs$jj!S(VIb#j(rEpOvvd8xdJS^^Z3nR$O31j`PnU zPU>(kk&Zjiq|m+iZ@)_yw4{$%Zz6d`<*dziqT~_~T6(dDuno(F8V^{H$817>Ta}92 zrxhde={cg-*IvHomOi z$;yj^6lT2qId6>R~MRcy@a{zkZYSs*aiB^P+wHZmVb3VlGuZdY~F_CIorEp5ED4 zXw?OW*O>Ec3RrsX)270RgLQ`78>14-=S_Y>FoEsAxY z9G#xrR%oQ*mZ;J>0~KxI&Q1y)MME^z+S;&9vZgy=;X1brMUaywEv+FL-@7T(vRJRj zWqIa{47U2e!?r6^s)3`OigeNA5X}NkY!eJDNm7|62&;G73iFPkW_8Jm1

i&#^SD zRsf?=;@k)vdUZdG%~_Twx>f$2cg(h&5b6wb9SGM}z${HXAR^+V1 z2J#b3TQW^@QkQ2ywozOLb~eiG%u%3Q5j?Gsce#dgVLi@S9b_n+PA#G96K#%$^|u?E zldQHY+*TFON=YtD=3KJ(mX%Z=%}E%z40r_T$qfpfqQ{4&8T9r!g?)u95w9siQ8114 zo`p&d#&u3m7*fFE;zDPwdefI)dc2clf?6inEeDE_K7(3CQYk`+L>nbwxR=+>axwIA zOLSo8c2~WglN!M`vkKZhlO#^s^2ep@k!_!g{W~P3#(?HPB8)Aj(H&PeyZJs{D<*y^ zH$(L(Y@dXmWogTRs2N{%B*_UEM9IWuEO}ciFVc@_B;Sw>imt?#%RQ*g+{^A(64vEd z_`T6fRiUe3bILW9WmRO2Hv(xYC0ZzoUZ(^DL)@;_X2g#MI2^QXt8FKnS-h!QXU)Cl z)kgmSA`3Jt5vMalA+S}syJLjJXiQ$42}$Rlt|6Iv)xzw>#_t2nskqtxU~1G6%{b9O z%{GHqcoOESt}hdqHCp(CLH!>7c}fnQ=YmsaW>UqiY6umXZLEPf=II_cwpg-{u{0qB zW81{cb#bTNl~zRhQY%~*o87{h6cq?P+s>(-6r;H$YQQ8l*%?!1h@TT&dLoxTh>QWc zbsqP1aV!x#>nH~y zOR4Njrx7XdQ1&IpRvU=UwH8)e)fC{s+qTwy$$)ADgbzx}|;v;R51W?(|h9f z09Wu#o|#zQJ4?Ea(A6xsblZ(1vj+FaoQOo|?jo1~QzyA4VjEk_e>7!vngInpJpZAaN z|NADCO{01+d@ifM6L&;P)`x`>$=6SGo7TrHO``9t)XoJ}cc5P~KS}>{!<&U$mOHU} z@`rbF{9$7w&&nTVZTt{d*F+|jl&AeOh{>b46q`Frf90ooezv$2dpgr1?>~Rc5C8s` z725WxSVQ4pKN`5J3|?kM&e@7uneI|-6try<2P~(1(iUfHmj)Fb4H3$71M`}cRoSnK z;U`kB{_T=ssJM(Ly#74aUSEworFnhpol0l)Y@|!&^W*cm>n2To`-nm@KVdnF94jm3 z5XkxH+vD4)6F-eeUzs7y%64pG*`t;%?KIw)T>Cx=MnZc@Ygt;Yd}Uc39YQ>@su|m* z-t(5D(zO0^uGm3-k_lQnR8^_BR;bKF5iZleHoMB{n+l18V^2+@W0J%@A_(h&+3Bi* zGgIhkX40>>54WSV<^^W%)C2)$k;5c5+_6>wm%*?t_SupSdsLPjFg_*UOJTvZun=Uu z^(AdktDK6*>5cFV+`;UoLnUUNr4F^DW1_f#fAFTO6q&|s`ZilRCSPij(A-G*820@L zAtc#5h~&wLPQF8?)^?;0vZ=l5)cWI$YL_q~OD!qi7mP}Y$L21Zs;uq?J=Wu6!gCN- zP64i3#s;M2bL_k?YYlN!>tgp7qG7-F&6N;Y=*`Tu|4?#lr(~xUwmed3{yj5a$s+n{ z%ROtGY*t?1a>2yZhP0&GAS-%*!Zfbx#uh~LuH}ebRfFen3%&CEkJ2GnqcGy7^`^yI zXqQGj3Y#Q?mejj#DGhhV4W4tbSAeHpzgEGD*!!7%|tS}DQDFTgtSSmblpu7}sQeN|3KhdMRNb=>Ni$vT+xTx48R!@;E* zYKEp~s`KR%W3>&hX^2OwZ@QD1GQ;_@u)7w7o_V$upYr}3C9;`(u!Ft0?KrK$ zD`!y$0MyUeDcd}gI!m$z7piG~{SoPuNLw1SB6d0?Q9sDNx zT(2|60Z$Y>x1+V%-?SpKWmmoDsaW9VzfEwooS|TEx!1(0d5N_MgW}loa_Jymb;@v~ z1zm-9b|91eIM&}02CW(fjPQW<2Z`2CIYE`ugm$g!YwcEsv1r+f#Tb)^A{M(cwS>Yd z(@N1P((QxT6WDmm@|*Yd^Y-mA2R_s5j8{)jQMi)?J+U}k-X<&>ojmta)Y4~cp;V3R z{0g1$Iw?zBG9WgJ&@(xIz@(tD;&Dt%7O~BCaVjJC-RF*c+QMUvb=vzp0p)eJFwfkB z=DG4&h?adv^;7Ei3zxlT<}N+{-`}qp!`T^kdrVE0BxCYyd_H+@U3OE?+Zcm36Ei7N zKu0bSad@GY9eUjW*o}WyXONe-gK_f$?nE>5Hl{7iuSzbN%}&iAT`kBa17iLa2?gP8 zK((O~V1^F(!$FqNw=J<{cgQNa1fb2ho&WjAgrF)F$+l=&wXf4NMud@3-6I+vkW-{%RXV%WRZ-SBNo9yv4jG zL=sjTuKo(WcU0J_m-~>8yxI)y+#JWD#tCA_THQUa4Z>KJzIK3G8SL1U_JLG)uBmee zRgkb&*BK@_@)h1U zNV0TaFk#|rB;grkIPt`kmlHN5bI#&#>!i2zVy1XZ>$e0Zb`&-ktswFy){-6-Bi`~w z9k#hi_Cv{NyEBA>^uK)e*17l)T9#H8q&>QI5_YmkH4!f5cPSoDN7?;bQsu&iG>)9!mZ=H26)jI+X@g_?9%p4nz?JtnL4X2ZA}nYVh-^}g38z}Vy4;3cNYH`J zW`$neptex1ZXPx8di$+vT9v9;k2X1KfHfvH84hnr#6vbk(sj%VB=Bo~X!<9unajHIo}jng%ZvTf9WB4wYXq^4nNt%tHq}x^Q{OiMzED1!n(utxNS?6DNbkb%D~$( zb5-f<;68L@N?-}q!!Cr>W%6rHy}H_BhDlcRcWWeLH9(8-%ky z`XQVAu=!mPgGq0>f)Aqis{tad!f*~}3AbxL@^062i77AziaR&#heHHg2en8s`z^39 zlVz*JxF}QqZKORTkk{*P8jTIVq-l6dnWq~DHcqQbXsvGla%w}OR05Rcc(3V5RJ=_5 z?3%jXr4`yQw!1?uDI*x(Z{qWDn^H(KYg3^zgBcMGi|1RnJE=X(Bu2F&gdLE zeU2u{tt!Zi6lSl601mDoiVOnci1-Q~U^FPhJQ_*)8bB^}c74Jt;|de++5N}2`O@Fh zI&I`>fq{FW+e`r39Bk1z=%x7)8b$YT_c+q=YRud-r}s27xPoU|{N{42Sg>jf)llr$ zu3@vHqsi;DIf@7(c~4gXnq>_fgShO1hV!R^VUxDzYscY#76BmQx&QcU_VxGglYwrd zK+I;xb}g_AX1@z843+p$DCa8r04RA_QA=8H8X`NL#ZT~V~EZ3~@= zK-Sqg^oZr}IMYIXBB-4KW?s(ZWCf^r#8eUO4d=+W_oJwRO>qsplCQ?VFvKyTLm z(8rITpPwIJzy2=oq6duW3^h_9xJX_#CDJ(-&EZ*yeD+Rl8(=~HBGIZY?Fwk#mr7ut zpWH@*aT~Q4zQXMs)m=e{mN1(ywuam9DVy#?OJO#PhqP!A^gAh5cAHhR$EcKR0+cbS zqSXb{Q{DKyJ>Flx(z8+SJ}G@8rKT;C_D}PtmDvU(8GoQqRp1TTSu3+wc=Iq{^6InQ zc!np;z(4z+NGe+NZ#U`25O#AB~$V6jjwzLVa<;NvAYs>kF z1-fNsYYx!krl&W-JeSQks6xkxrkDcxg8HlQQWxF;Xa)zu-p!xWI^32RJt_aE?F54M zl%e&Ui!9Nw)8fEVQnG0dI=Yl-#-c6<3}zYDIMXHR<=q-h^V{47hZdn2;^jZ=Sh0yp z$y7Bv{{VH(=d?sD5L`IIxrw%Rw0DL(ZzoH8-;sv3sZSi!U^&=;HnL9J3;2!ZkN;Gqsf-sajd;Hsoxjq@lmvSR~-Z zjjOg^_;=LUc&6fM!dOw0u@GUgz6VY&b}Em07J;QVv6XhENx4FUNJrJc5u1|na5 z?hI0q?9%AnX|jp+vn}u)@HZ4EfAFFAwc4y4|a3)oHltC%RZWUC~u`=+C%`xT5i z&Ajchv?_3OhFuB=_|ORjw}4v8+rc2sTxyDE+}vX#qOV^ry_r*!6sF`koo}mpoqHI2 zSY3?{H^fqHvr!P<^zZQes6glZ(5wx=BbKCBlIZ@_0QRsR#g2A#F0|w8=y}64C20q& z-jlTu$OLtDFk4BL<6^mX%h-X7=o;Aew|NZ(_&-eC_?_FgzXr+r`qetEsb92jWGU7p zRXK2s3G8&g_!w&bMB`Ikpx80b$D)|$Wsb5)`KSHsl}$LLnrnz$5Tk>@FZm{Ci9^}I z)J+9v8xhJ2Q{`D166I>30ZLi$XM*m*M9}0(c;5&=SMT0g2{hpEEDY;{t>S4js&05R z@Q=CM_Uax|f3*;a6x3Gw)ln_1*kbfnoW%A(C8rCZt7ipnN%6&L(mp&IA+PtZf664@ zgWm9xrirbt5f;a{U}+c0n*s`?9qOR_c2)|StSM?Cd9hirXI=C`c`ZAU>jWZRU-|cw z)e5+p?BR2S)8V(ONz;S2lckLFPKJpgxxiq>;N|(x2!`cG0t5$z=+&eLpOwAeU(c@< z2KRjqwNwFZs)BpeD?DBP-b`7fp(;k5w}xUfki>ZLtR7qM38HMNOdY77*arpd%RR#t zZ5!J#zqg8(TH<}$r=7)x3<#JIqp}bmPM+YLQ?#}28C|pVitXNzcR4Rkd|<*Z0U%32 z*L2d>Z8=nzkWT&#kD#(Ted7py0btj+_$*yf1zlE1o z88@6OlN2#!O79ofwLrSPjZEX}ul$yo?&B|>a??6oWX-SUpt|;3G6_JXatG~8KIW1Ek*8x4^}6=W-}A3hS<~b`YK*5 zZ`g20K=QzC7SI|m7VH`hHmbHz4DeDwixmUa-TSo^nhKD2H7K`hNhGhbWUE-x=%?wT zqt27cz@C!Im5S+g*GE@>IbKeqZ&iON^yFGZ2$ZDSsp=rK`Q8WmTlUG=?~}#nR^2{l zYL6@fdp|O-&T3Jy!Lb}q5QOq%J1w3>E$zz2MWy$1wP)A|du{7V5=%H&PORW_oY9oy z5hz4Ca3hy?2oq$$uj4t2CbXQsWqCgBJtH?q68KUd#`n>a@k%}_V&d3Z9O|(3pYq9# zEZcc9S?tq>L56S45Yq)u6L2Jrvi+ek6$XALG7goSaoH<@stX;92K|11H`k97mb;(T z9??H#WSS_%7zb-=4M{@&Ma9Q4c}W{bkHi!1Knsco%wQ48Q1`Jr!SPOSqj_}1;2Gi9 zS~4M)AvZ~H{=D*N(%tv3mnhaS7EsT~w6|ilqEvTJDLc{_=}*-YX;4%|1$-Md+z365 zJ~R*4iM<9S&0Xr7vNU4~#;a!Ajbs$huvtmn2nh-6euNbH5Kv8Gr-RqgH|l4K^;C4f zH3cF`^Ykn`YSv{X1bW6W)F8Dfp)cl9EVDAw{iJ0Z%r+rZUzq59`WH~3n9Xe%7h@Ly zWuAo6vBBzlnwbJEZaRACX4COAw5EyDD|bY(f(~;FQ0hY}#NhDE?2E&>_+fHIM9H-u zW{;7(TV=*#Aq2jx@qv35f2ny5qHdCk*buIa;0C0!u>;(b)ur4_+$Nu`^W=9mNkT>G zNL_sqt4<4)Zs&SwZJUGaFCKdj#@b7yuaO?>z#VdCvD=xV5ZxC9H)g!ZOAUueKDXC|c-`aN|qmcm=cn-Bi} zZAx6fe_d(d=#fKR@jN#zz;PY|tCd4^vXU4Oi=S}@qhEWa8#McsAg0hnB;aWL=~ivs zs3vHWaPBvu$ED1-hicon4tK8wg(?E}`%TO-(S_MIVT?7VM75;{v&Ck5b}qk#%5L}D z!g%*&j(0iJ3Agl!S7QSS?RgMW9o~VFL&_#HIpLj-XyV{{N+kiJK_8} z_VJYzb!R?phde4rnoubM)ffI#`sw{~|M)8a#PpjHT_&%5EKY-y->EHQPeXITFrZwo)ON#}iOW@eV_}tuI|l`&0DRHzeQ|2CMb0@*UAJ z{Wc__$-5MgY3KPk6~bwRT|!1xEAiWpiL!qG!yBp1(-P%anRalPf6lS0MIqQ_FUy(+ z=PRFLbM5?J=c(o$rrMLtht9YjhAm}!ZE)gHom>6k!$am{7<*3`@ibK!^%WQ!Yby?> z4e3V5FZ2x#VPXTm;-)4f=x!wvq5Vr+2@GHF?mv(F=eKX~uiplHMOsa1Q6Gl@)~b7j z|GcEcUMWZ3=jm_XV6O-chavh$KP}YDcAtsX5w*zDv>$!7A!#MuS6+kCb}Z|JR&0_D zHHxVseN$j%InQ>HLo(f>twz{@GozsxEqa^eliY9s0;Of5?pE5Ltngyb%QrmXF_e)l z;=-w4 zk^^CFO)(ZYV{k5h96d0hMJfj-O>l#s32@h$W7h3`siAbPxM~z8ebZCt9bCP@EsxuF z)lM1TE2^EcH>L{H|Mn*Hsp~;>fhUIgcd!@@`?dxH_8p(D@5R^^inN0?5Jn}S@N!O5z~sc|yTaN*kn_Q}Mxb%B~~c#2$tm5$tZc%QqO)OK6L5Xan^ znxCAl+wI4XS?I6d8?$aL&jBJm5PI{CtX6Z!)*Q5(K(-?k&1rePKOZS866l`TNsQ+x z?9}-bUX@gJ`SZo6cVI&EZei_SX{2BPDikTT-onn@KYok|Ws5!5hqmFd$z_$vjsa>O z*(}h$5q3=fkrXBAip~j`oL{DRwU6Ge@`asR|7j+7rA1g}u63?>iKqF1RAnSKPrkH{ zB-J@XkU`2LEdT(#oD+`VK=?nVX!6hB6~R5ocQkkMc*XKB8bLic&C5L2w$fS?Ipj%V z8tRHod_>nIJ?4N!S-;1>`%(#NJ4;pvZ>NVPgFTjBjvSe7LyavC_kx$V)Htk7Wz=)Jw%gfM**#tE0%XM|e zNjn#9M}v7cf;{FV)vYxh1;1?0u-f--;Zz$d8JZB6U9Q;Ch7V!}3=`$_TZ#HwLgfr}Sjy`Hl`)S9KmG@8^ zXi9^`R!ayaU^l$STJyl-XbMSWcc(a+cGH?}6N2h1cIZTizDDmMkk2^~qd!fvXFh!c zf~py9?Te${L}f~N%n-2k|MqeJrjk70LKEEbC7m#k`UiE}=(=z(SqAC28IIYp^py`} zj-Hq`mKy?3!v=wq)=qb4H}XN)A=rm)WM*Juka@l)Cw>?QYN}5y$_bYus$PkJ^*os7M3eA?KIZ-3SVh#JN@kQ&Oi|gz;dP%h_rzHfpG|>AkPCVT)Rl2mR0V z$bhwwf1m+VmVP+@;Py@`famD@g~uU_OUqG)@2UZv>_z&=isPxevAv>J;T%2KcuZr_ z|6#mK6NONPsLaDYd%qvysTr!jpCYv|7us%vFDAim=-K(VQG#+%qfHxgK%#u%@p11_ zov&nocZ#icCRLANapAN+<@^)hPsWrkaC+{BMZo<7laq;1bU0+7bWSPHETfCk_Xz@a zCP16gY%T)@@c2UrUur^HSsBfkm9c;*x0s$D=pGHExf&_`GU8FyhxyfPNf?ARW90{T zNd$vZ-kcMBpZD5vum(D9F>d#^@is=eg{~knOsl}%^X6&Ci3_3606$~6Ub07fCk-Bm zHWyz{M_Dyvw3_W0tz3JvN9P9dM3l(4BYkLA8uIi18GW+2eTp2I+?!|$4Sx+K_sV;d zN(^)Oi1Vo{Ix~0QS^>R;a?65e!3BoI!p`u*v-LWW{Cq=k?N&=)M~D=QT&G~+g_?!f zyJwptlh?h^PQ#^`-_(!t?oLQzfCd+VjuP&q+6y@tQyv(Bhz-F*7DafbEOrPr0x=Hvz2L8;>t6^NfaNkdX!c1 zL5j0K(2x}oD`Ds36PJ9T3-?qW&UX{c*0Ac))W2&OCqLIU?huC0{gyck-+sKG&)4r? zM|azdODB7AZJf*_vLJDKO;B$aIqrtFYAW^3E`@JBS4ABff3I*yGrSfdu;|^8y-pol z*Ic|M^Y%lvbLiA`?jJw@BR^Db@Ct%%+|%)Kx$Wy_^EQyu4dJ2;q|VR^nipNRn^iTq zmXnI$))lvfK=gO3lLwYMsn7;4_0t;|cAl`L$|@B%O)o>3AG2o0G?xxjJ?Wy${(1kr zfB*6E{(S!WSA=NEl3SKE)FZvPwsfB*Tg1jfX7{|;gT1!8*m={v0qZEc-A548m>StI z*@`Z`EuHo59t4X&ED1d)hD^B_Hg&U8zF8NXXye?+#IS6aVrF~xFU65z+9OI3nke0_ zbZj!;{PF$${3rb;Hqr52n`GlVdq)IF4v7E~Q=*$v*6FkEu)z5}I*a6ym|KdN=;~?z zcSwDvb4;*kr_5OMl-Ks@yd5rxWY+5Xj)$%=6FTJFq{j~XVX+&{lyJUVuxXFE?Qp3* z2Mn1!#FKhFf%VsxfDX5B15xjEX1S|qQL*yOa%mN3uWhOn za2Dj*)=cL@C1NX?G{O_K6d4ztaaRf)4U%eX{`CAqaQhdPYaoGHm??CsLDy+{R`Lrlv!qcrIdNY7`?VeUKDBkvUac@S6g%=KI@mb)V0K=LZeN z2=YETFo1Y@`m1_cY&nk%Fg(9t5KVx`RIC+T1K7Q%&A^h3zynOi%=XKpKkktc265Q> z!4{B>kfJ_h z(I!tiw7P28ycnkn8T8hA=#;UsM%y7h9?gyDj0NB{MO`()(uKDkD@p{E8%J?yLzlAd z884Urc+DC#z{;5AdjfA zCKAatbNrQk%I4}jc(pT-xC2eHNV2zm8Z4%xYvF6GlBfOu^5#4DqOOhBB*)3rdtd6& z8ixE6@zEpr>r{?HjvU5O5&)1u{f9Fg^7FuNJG-ZCsnsTTj+KLhpo?%Qj80o^KE$)c zb81Uv{qO0+r`LniD?i1^_=q4FJy&oP(+^!cx6l)B2aoNR_Bm1{HEqk5#IH4*aX5I~ zx^sBjf4N|0Ki?y7A7|ryY&w2qrwJ~#gY`tY$(U;1@6qAnxzt1JdOmA;i3CD#C-RdE zd?_@>9)5oNHvjSUyTu;mMK|hYUyhYKbkv44N`jj|r&6*C;0;y6=+*M~_Y5}EWlVz+ zX;shPnLW}fVO?uuvjZ2mjkLhoHk`LQaVgFBw;6RG!RZ=|o|8>lOP?`2+sfJrQ#W}3 z0G@t)-oO7f-L1c;1*587t?*T6r|E-Z=MsYL8ms^hPcEgBzY=lY z?sL9MO;z&k3^Sdl`0>|#)33h|a=`2WX&lnlYP33Swc@PSd`@4@Md{+qQ$3v*LU5~H z6)w}d2vJe_gk32I_^#gbLAcsTSXac0#r3Wp(?Uk#Rh4a3s643ZnslvXVX{m4y9}=; z-~9_;a6uFhlSwh}_skPkeBziK9aH#2m(MR-Ko#{w1d~9-zEdr+Yz#L5&FL%@qkeD_ z2LPnHz`;-U05yFW$!%5j>U+2>qxJCXHIXb*g^N)##qLoRs10ZK_4WxHm9`b6B?B*l z67&{esUXcjp{NmSQIX^c0{XF8Q1@6#mlekk(gz@cPh-4w9t9GVw_w3GS-GKG%i?v)#Km5#p3O-;HtVK3s zA4SHh$}>MdE!5>wRUgh&Srb&3UkZNr-4t60MV3l*RkspS1xl9N zpl}9OTGmi{5Fj--s1JC%J<1b|Q$(_G%Zq8L!#6!5%QTTaP@_0wihNz`&n zq;x_$lf(8b^Aj3N6;x3$-mYW^KpgRWAn&pFp?l&b6clVa+UP4lo}FMa(6iZILlG#@ znE*V?wr{@RkFV3Gseylu^skP%@gv$WTf52!atfj7Vr{I}F}@%=L_i+>SiQ*n(IA3^ z>DVz*u`+MK;OhFVcQ&Er)6nOvXPGrQy;_zpBvwx7Fj5hB)nz6=#)w3tM8>7i=SlOT zUoevw@V7c@s_3h&Q?j<~bS53{7*Wum{AIvVY z4kZp0tA0nPpaUl6Pm!K#i$N4a3UDAqU<{l2%7&p-VoPcquPz*s>0+Nj&32IV{K=N7 z6&0u~U@Iit=?dmJ1T%rsR-k0a|j3 zkiA)E@2j6dV`??RY#|O&6S62bky&z1L>U`3ja#Pprw zRo!>5s3L0R2h(}VscL_mR~WL-*0<+`270r*+u(d72fN3q)3_$oIW#pjTSO-g=*66* z3SXjW(noioRGeAa5kkXd2osn;mbZlp3U!gq-P{ zNXaEwKr|$|Vw(*u!vcC;338=rInA_cz6US%(pe)aV10RPD#@(Uw)0krEAk1l1$Rheyv+ zKk^zkf1LF-$%`CrpFAb?KLmE0Bf1Ms7$r%XGFgk;wI^I#Y|4U#czW4@XOW#^Bp#sS^%QSmhtQ4na}0?~7hPi8ypxAgn#L)nUKAva=n;68 z^}ysa^O~~W(&LtAAS04%j6p!*-}cSU9hy#fl(E-5V50%MPc+;zrxtycpBwhAf{dYg zjmrt@YzSHoM<&1rUp#^i@u8y*8~N`C>23=3rQw*OtM7B0z5`h4>nXV`MVM`>mH15S zYM*;QFePN1oxNi_?uv~EK#IzbQBKS?C(G(ZK(9g>nU;FZs7j~+E#SbTzZ+<7QdXT? zcJod{RXbh7OB!*|NKn~VOf)zzn}FUn4NK=nW-)_t0bwpApp4B=2gE|^ku}M*h0@2i z%h0PcSGDShyy6@)sR~3ZCVjL1!~Bbgey#~zi}q$%$jKEfJbjs(HZ3?M+-AV0)KwcD zQfiq{WEK91&dRHrg==NVzk`(!xPZ|etzD_|vh@QyVQroj?OW@{G1xYwO1rZTh# z&gO^D+avwTQJ$yAg!W7mB#@g%>OTKo zp)oHgS=CFPETE7|>K_fKb3nfR{I}QZ`TG4&+a6*pXo&70NvFoN@mA_LA%c13X&NPn zY9kgd_05kU>F}o;l5?h?J#1rX{`&WY zWcHve%UcNh0wb_r3r1Btw*hV=iPJnTH+Xk$TWam{@;w$wTiE7cFDtpRyDF{6g*Y$Q zbh;1g*!F`{Sj94mRM5M|z3AS-Tvkcu_WAk!=ltgHfA|6o0|O@Oj!Pcg0g^4!0^}b^ zX#pnttL=lXAr-XR#B?bo=M$FCjhuVhAf6Yk>_jE{d5`82E7}HUe7S4tb1c}^;%({% z4X6(&=r{QvyD`iVOeW%ljbwrb5pDf)`^KX`zP-QxLA;GXnWk~$h^a$T>uhba)HuU& zliUi}fW9=6PB_*aFyt-igG6nR8jMyuiu@RzGA+W2&oB)IYztB#$2u0A5FO)7@2#0z zoauCJu8ii=$ryqq5HR6TRUNI&^)fAht$g%OHzEQBj}Ri^#^8x7|7Bd}AOg%@l(ZB> zHVYK2-Pp8bw$<;jIzT@&XT!c9c`--N(%eJ~=LxpKy?9KCRHs2uc}5xLofsFT4dn(T z_-rG%g0X{r(2E@9s-_=J7*Qkb)q+T(k_DnYh^owDa;cYHw~mHUKK)LzkOM()uOaB^ zIw=Wz#dRHnF`cNI?7j^9tMY9v0gj+W&f(WYvon!pMta)A8pf?8nwp~ynB1%F+t>P3 z^u2=%Pp$i)x$E`Sld@p7IcLS#)_PM00U+QqVmc;yP|Ky?(-UbjZpnQ=JE1$oCR{(< z;1Kii_f;=P6E4CgK(dw#33Y)9zCCO?dz$hokOu4WJmVIe)4}tr#X~Ppu}G8zmi<;1;3-(tyb0&&5e-H5 zIRP+tc9l*9Q%t7H@LgIP5*tbHJ1ygQ_`FD_GL_N!YMa_1dT;}AIpXs7>0M}_GI|8S ze4ru7yXaouAI}-q#@KyyTD zd|H}M<`>hWa|&M{@7rtKfo>NHB#B-FiB{Ab*X^(bb5(T#qTL}3a;DDO7p&Hg2f?>O zUJ4_LomIBQ;yK#>udS1pX1$$-fPrIAn7|dhu5})oTk~EFGCkp?K_jIqqvRd12Feft zW#jOC@{Wn6@@*bGP=-UR*W^y;N#*4%Z|JVvPoqJe^y#1Ym7oHdxyn z&gaY_GPs&3+#;42$>eY|W&h`v&Z+mWUs?MyX163IBG5~uXKGGl{RSPcM0C3IjqTMO zqLNR@P!|*$%gGx>=Qd5={c$_d8sJz4n)sEAT|8Wjem2*-uGsvUTLW zw)}7<29)uxJ5uQ9qxp7F-5-Bt3dTRn)irCe+#@Y1PXsl)2uDXy*=i64(Q+jFkmsRY zmR`FP@NfFO2$h@PCXfDZ394%@IwC^a%?@$uZdYHZ2T5_M*u{?@|9SvklA7N1bB{tZAes<&4d=R!|4vl zmpo51bH&PHmh7KF3#NzdkGku$NC|-a`1$dAef|2o%_)lU31+mNcaz|PCkv#xvny`p zodo4*-0aKfE0xUDwb&soN)bYbd5{gg%BpXob;U#LB;3*rrDTtBXUfB$rq`I2a zj>^Bq@J2qu)qw$d*o+0=0aW8`|a`lHEOz7ti_t;;5*3`n@AzB3o9&>s6<7^ z+1ww~HVBcM^mX-F@gLNavFs>^sEITUsI4%kJcSntbr9h>KmkO7(2<5ob+a1w2i9)+ znxhUf6%~<>$KT~{E>H1TL9PR(Ji-F3ZR|{o10LYp!1P!bIR6C7#K}+SG6d66Mu?@e z$$ic0q71fgZ3N#go<;bmpJEIK>F>`HdSV&V!a(aBcNC__{m}1(<+}5euQlQQveC7`+gNR&Y??Q`B zAoG-kp-6Zm0A*@z2eCh_^@OS;+0L(-!wa_B=>IY|TX>fQasaG>T@k%2J2;6=bBpDl zm@^qaiPt^*m9~X`Ld9^qE780#F`I)iLr*tC5@33x`vCRBVlstm zYVQR!m|w^iEq#NO6+FA-Wp>1l5v4{M!;flVhD9*FrR1x zmae4)-Y_+=f64li4K{7AVsb|RwmLcx8%4{M(xgw{U(-aRwEC7DXZEKCExFvVG*G1s z4WxnC>;8amVmI3`LO7#Y38$9_@U#e>fClz|hd77qxC)ZA zh3D5(2{#2DM1Hp8HQ3RT$c%PhkH>v%|2?In+xwmrTKI69r6mn!SVGP7=g0k9i9(Hl zNlKZ3$P3;hoTmuO&?vAok|IC?Qru3zZd&K!ebl60_j?kF z*T-{IA)@6qNPC({>2!#2D4BOtVnnaNg;mp1gFQA|m2t`Kzv z{_V+FGi}PKeRe0)-Y=3NB`U_l5@%X4#hJ>}Oej*8N+XT12Ij9yX8*|br>2gCj<9J% z4f?0HV$Jf*pFeI1W0c}Ci3(YO#^lRh#>H@{lX_og#TxRqWutjN%iTuo_s7TgZxaFk z{taQpEO+MzT?I?CSxPB)Za`&#NDhr05b%~`?65Ff`&t?o5pC~pR&6IWkor`t`_eZA zP5~gbQ!%=Q&O1EJ0U1fnluj_XJz{u8nIa8s}?~R-72=vgPKI8wi|I%%Ts-RCv|gyj{;#V_C@cm zXCh;1R$!rRSJLnJ3VOA7F*aP#0+uA;Mx4C01tSC!#(h$miV3!{dIxe|!DZ(QojA!UhOaUppXk4=aMa(A3g8Czbp zy6qtdO9H?MJ;jEeYP3ldaQI8ycq=-PP3@pi?&?JN#a#q@`NJd(uD zA*IgAL8X~a*e8Dynan)-Oe0L3@ES3{OYmz<82&BRI&}7CU%xisOm7krQ#?HDmf*HK~l<(r(DH4H%bv{T@liqn(`!^ zbAE{)!#s;vss(yWYfOo)FlvbcMm!P_>?KLe&*RToV(vs~8seG{HYykMS*3twR@;DM zhgvRRrkCPFn+(puS6A!0;Vm?w!VM1uqttQn1<;Lxgd_8~teHiXXo~FgO>P`82RF7IoQmmr+S)1<4*J_!n zV-R*iRe2onrMiqh|Jo&k!fjbFMmsSOEs+g+=?bqY&O_WDZCi0P&&Tuic>MK0vCth& zy`$yYWw`AhGKztfbEE$tt;i?$OrbUPVrEqgK`c?A-rGkfsK3*ZD<9)9A<8W|RFTt- zu={M0rhL;O@+F}_KLmkS9&KDUINbd{imxp7>-G7#gRKzRkcg|EMW*q5&eO)V*sS&Q z-#h_)ezKHa}Ow|Q_@CNnoudgus zt9L@{)Euhs1>G%-P%>@1M8+laOXKS9)jr9_09fYFO~UFXAc{XHo;GIWIHx=S>o}Uv z8QpgjLdR27`@~`l~`zzZ49WG4Nv4OU(m(d1XWljO1@)VZ_jDbC{eb!aa) ziL&~0LbCDpudk0QV37zt$4vEXLCw|3xP88VzeYz9w??vZCWjl`Az~PZ56dKrzrI3_ zToe5&UQimEgGjm^BC>UI_3UhzEF!W5A;3rb3!opxFjM;~AmY@QmVSwvTSqF(Etw_l zFDq^|vHvX!Y7WKdFhX3AZGWq#&PG(>E#>rNtjsE%@*{=)q&}}_(#Y{h_GjXC(2poZ z1G}0|33;j(8aN`8KxbZ;1}`x2+@iTpW3r)e+&({_#G8Z&V|$HNKF7w%n;6O}Qg*m+(lUSS0YxT%f8vSx(F)A_#;d)l;#9C8RP>txVa=VzBb zYJ+a^{+1LbjhyTJoE)itE9Bnl8wu%5`$7zr4wryViH{@758S~<&ptlsNJ4roAWkfQ z<;xgoC}9w%pS5Q^MGMzGI5A~`8q$_t@M0{U<2eSCp=pr}Hqx74^LUYvZ%HfKp*gEq zCg92>hv8vOib+)ZIj=h_c{I8{KVqdMrjox-&w0@@I;SuN>JM>w2u7Y0g)`?kc*Gp( zz)z3N?wEC+mwZOhhm2hoeeURRCz^|rdrd+zQZ8e<+C6!nR4GF@;)!2jM$j}KjANw4 zU{cru^n5=9v!;!ixa0FNS#(a*`yQh{8E@b%rV)+MvIT;9eLBD%(Z>I@3}AgMc#0S( zU9I0H&!o~3aALxZca$4WTaIzjb7%nb*p4O?kQyWUp6M+){kHouk1R}{WtR>y3M9hx zgC%+>WjDX|l|bP0{hlcIGW0#i&rSUz`+<(0jI`|oc@kPSUa#K-S7lNrj*Obpq|Y6R zJ?p@+N6!0W;yP{&J>*5(Oh`5NWTl;EwSbQsr>b3EiN=PjkS zy5VqoAmBeaJbA+4`L2kzJP=wKllv`0jO1R$76g}2J8q^`SMV$SGVj;#ZT%Yp0{aUG z6jlBNn3!2rB^WL?QA(aXfY)u%{hbY`U_;C>A`$3mAl(>2+?b?c7SQ9_D$JPoM=6sH zzgVn6?uHxX^`il}-T8^U2I7J=rxfcglUB)33Dly?Ahm&DQnL!J<22gnF_8G0`x})c z$6e1uB)Fa>&&--a)Z6$lXX^Pia?0=bBbm{J+6g`nZPeVYRg~MR-h^|h>hx)l@J$>Yqfipk$GdSxWC^cqAj1nc+926{+I=AC z4dfxz!qR5Htv|;MWe5NaP8b3C90Z?Fs|4ldowFg30V?*2oJ+rV`72}y>RbRPDl1Wv zJg5Q4RX7Sj&0u2FWiW?1H5P^$r0($X93*uf_$xIHbnZ-h@&NdD2Dyn3VoGu*8KveN zCJLV6I!*%dwe5oMao!9U@+L8r4S6)%{5V(JGmwr&iqdD~gPwJ4{PUejTIO2!*Kqto zZ?mT^ffdagiK$%VkGu9Vm_Pt23>%Y&E(Otu?OTbX^0^YgF;L zr}>u!=kocd;eY9UL?|mAZp0o~hf_BXV&pO*o`KUvnlOJ8P?Yo!fD&s!J_fqEX}sQ{ z19KA`Fh+31!DqzUz*+EY-ZNEBmCGmX7^l*}6UGHOp)qbNGmeLt9(26>*lt241%#QZ%AvG8sv>DbjwEHk4_(!i3@QNEGitF_*2@9!-Ub zsFE?0iePlwa)n&z0P9W`py5B!g654f`Cv<*lLwLhQ0wqA#*j~n6oU!`mPqdY`SG=< z3Yo(cV^hDyCS_#OD^q5+tDI+s3xU^Vt#c%ZH#&G&w#A{rXW`}=KY|l^#HdP`+m3up z;YD)9NIgt?j0n2r0Hh8w0cVEDJ{2AqHzD7xVA((&f!*mz%0OEWp|*VPeLmZfAj@L| zrCt7tyec+Qzs(2Hl!$|w`~JAi=$8}uP~rlvTe?$mAI?u(XKZ(znr){GFic$XeIxs% zWzSRyl5EcHOLbsF=bVIGU?rLZD6r8)p0bdrs>#~696OisYw#R3cqgAvP?C$2whQRp zJ4e`Jq8IIDv;tt7{b zJ)aX@F+81)Vq3nZ+%jzi5TD^PPgEBnTc<3s5VHgsbrjtYO98n6E`ssWHD2$N<;aD!A*=3o$wNlo^&_w1xcNtz_`W|kD(kS z4N2^TQZJmoq>k#dG!;O=5%vq^Qh>saxEobSbl}?A2$M9PEN43*GFAsJ9Dh3>9sP&S zkp;7q5fgMc!mK)g1V7)uO@q^~e-hU&hyBQfQC6c$&6=s*A8oy+Ah3N18Np{g2~$xflQ(OL9$(YPI`sh_DX zKr3pcPFwagcwXrRgE1j9u2~M?mTx@;Z5FA)IHhv&3A5lJ;>(e<{q&hiTH@WYP!;2a zm+?;W*mOenQex@X{qeZ{^*?_+zkdJM{}1FedoVKAj;8V^Y@l_KkTq)~WAGP@#=0i* z6qd_X>HDSegxqNTa9%kKi@_`tH6-<5fKhx|FwH#G8mrC_*zsv~>$dX3?N?tT2sA;? z{0aI@g%L)Uzjs zzCY+P5BVZFOJy2hFOH=m_{+kN=+f{n!jc#O;+d(F`Nq(Y#~2FP#45-8I}b3HXiWVC z!-MsYo5$t7j;X~T*_~zfA4bu17*2?}r#zb$HAzK+%bT!zJT^)oON7ZNO&FC%LsL7E zDUd-xWnmYs&+9QcNze(Hw+y(ZuB$Xg;`-r3aocW5PC(?qdYMK7k$eh{3beeE%2$n? zPzIeOl6fYC%UY?X4nCu@jIU`$mQ4ze{)Fl=dJ~|#7VS8}7;b2SLC{nsrWr;|F5T=o zLpDJRV#fdcg>g zK_!fTvv;%mpp1-Nz~dRZ2^unrH1sG^=M8~F?9#GTTpr(^qRN`|l6|QBRu*t}mXM$t ztHi19ZVnX#IE%yRg0Y3R5||;|6CpQTmpw0cPyLe)+2jyb5J_|=4Peg8`{OyBL~b{H z#!v|pVN9}sQ0xOFC_k3=r&KmmHoFKuQ3sxF@#iIDrXeW=u7sz8!r-GTEc7|q%sS&S){`t=$VFYA?l zd;;1G`n``ed_JGw2Gg;J&aOxJDd`8C#gDO!03OnzbY?*o3!wQLw>3d$(52V@7%Nux zy;i#widpM$GZTW|o~eD|w+LK5rZPr)kuxg0=k|Pk%}Ra^n3b5VB=Y2T_atd4mpb(= zL`M4$8b~EAFt}?6Kx88#^EV$7`wBJ5VU-(G<$9u`i%N&_;;VL>;`;E^;-D!K7&YD| z<|+47b%q$c`K(yEIZ!r1^x?seCR9k$8s7FlQo6!zfotVICLxdfn3^O6!MaIw2h; zKtfkpfE>2gWmDatx{@;CSjaIjadZsbnj-h?YiO1UR1BO4+yZ`|1<(Af*WBERydD#E zK(0yGK>D)hiB#naQ0joKx$lEk%)cbEO#(ZCS%fdx*4NjxhNx6e4j&9CaEa-{c34kg zAQ358g>cfW>MI#F%(YpQM{NFU@uYWzi?z4}xdH`&;4+cm)J=jO#4eg9n zhZ0!RFi3S{BuZ8>U1I-OBalxnGGsd+r9F^Std?DzNPc3loP?O3R&N2U04F$+#8(1m zB7B$!&r?qrgFGqU$n?+8KkoO(%_(F-Ie|mo&-e3dP+Gfitgs-bBCg+(04M14_T#UK zu>St9RQHrC^N7J@r===r?3k8u`uE08$sHW_vqXWwb#NPBGprQ+ zZh8vl)-X>f@qapIo)DD2lPdHDBu*{p8LN2CgPeL}0*fR9 zeKT-}=DNacE#EBPU$%wF_U40$5Ji)(I%xEPf$&KuchQr}sRf{W+vie^1mjtiZCb8c@TWCBMmi7H zB~^aXhBV?>j%eA+A_MT#P>K5ap)##Ji9NyNS0*D2pjG3BqcU!8SuJiO4qUirrD#Nl z7@jAkY|)J+Cf$C1yMO=d>;L*6`K=K6+v_?n@@)eY)4cG6=P2K9!}y9w)m+QO&uOR& z|6o!kLr=H`JE}TjTJS?aXTt(a79mo2+KAfc6UIz+QJbczEFS!H9Nxt4IW}z!O9roM zxeh5+6|3$apHXN?0+!Tk5`~~zB*oPTxaY(NtIi{?m7hfkxmS^BW;Arx?sR;xBk{KI z=qJG&kCEVsKtChu=BK_)>|;*T8uOk=ZVG78g9}f9BS84BlgvT0{);Mo2}~uX+2JKf z&QBh!DL~Uu?I?{dmTt*8=Q-@*w0CM%R>;kgnuyJWhSVZ*s&&K2E-^c@eb;DvPhL0t z>^XHwEefv>H=kl6Nf#n=0h`DLTPvW*vNG&T`^r~Wv7vSnc`b|PDN{t&M6LV(KUMz$ zZ`)dyhvK8pIoI0t^a30>hh7B%MX@U?7DOx&K~WeadYMlnhjnoZuv!++}OhAUX16!lxhB zo_bG6E(a`TxR>-Mabct&U^UC0Rt5n){OvcWo*9?8$CMT{yBD>l0G}ARj$ma(G?;Ep zA;oy*3yD!M4UZ-P$*clRD-a~f>r_JoRu)=nYArpk37MGge_sCKR-gtY*mss~%OGue zS`PleOQA6Vl3~OdA>E#r7B;hrNH!lttgLk6ZlY|V;xrNe4Jsht0B>n>zBrr|RghFi zEvhI|qEijEpHVvTfK2svL+3tlnI*`O#xh1rk}MIk6kl~;nTu&|!04vVPEvQ)d3-_> z&!D(~7Riv-hjC$i$CS(p;yVN%7?KAa1XvxIH6bb!=K|3Iy26nhffH*XrfXjVbX_KO zI9-K#8d1`$DwrdJ0<(B>g6eqAh_gt5UyDU2x3a@|uJR#-5O?vev0zI;Aw**W{;-USI~%5K2i}Km>m0Hiu?APG8E*>{?;sCRCTc{nIMC!p47Dbjm z97@FX*anYk02q;n|T;7SdQ*o&78nQkVmfD?RApo$Up8CyYq-Z2a|!xhf1CXcZ(AUcv0kc4@3oj%_*g=X6! zI>(_b=5;(*o1?0#)7fc^P))27@J9Gb0J?eI3&&9zcpg88i2op-&~>3^fmpPvW!pOI zin1b6ho+Bu&uNzVv%0%zR73w8vWOt^g%6%}l_;8ps`-s?1hmL$2q&t!>~0P z2~0k~D71$zE7!uHFN%vFJ+N z0lJo2#@VLuJ9R$Lv71nyV6@*r@lh9o!ut*B41>R8hsc{VE47~gf&|in@5i3j;=Fb z!pDSD9wN&+wuJ_;=J3(>IXFS#E@XH_!b*MIQl^_mZss02{<2p$drz>|;af;WX#)$# z!^ZT%oWO9g6-mh*`9jtRje}M;5qG1W8Z}GkY(`}WMA=ZZVs4w===s0oyQZ5SNLsOG zgnEQS1V?M$C+ZZ;EkuJ9E^u1#lpZR~iP=Juo=tP+td;i{U3SqPvktPA0lhG698Jb4 zzT5^unG+ky+YtU&z$m~|XbF16w3HVhy}>0!is`o^$_oJ>W^e=P#)ZT?+r(}Ga1G`b zbg4)}bTL0p!jEK#hHromFR4$(H?evu04#Kwx=cw9(PnZUgnD2EUqeLNCkX@dIFT%n zREA>cohh!Bmnhme!K}QK!JD^|HXh5GR1^nW#l9k8_s4hA_!BiPOAWQ(9m_3vT3!y4`oVtz;cEXxZc{Iv1&n;)xq{Z@B6CN#E0ujRk4tyv} zMU>P9MmYdf(92XtF(N7tF_#v*VVYzGsJliZ(46vAO%3)MTLSAk{bV%!*Dc**WLKn- z9hv}Ny`xr=DKpn24@p-Y8eMZd(Ex5}e6Ayx4qh0Jo4Fjxe}JgngnR(L zGF`?5a84pPpuK^0G4@Ex72c7e9Pk0!st3Om*p*bF6BGgx4Rr=vw1Gz`Fe74hXkRlO z1#At)EupSW%(7e*2hI)kV{^WlmTZ!{BR7+(sG8$Hhkm z49^P}v=p&$Br2$kRg7>4(yvggK;3|CV^o1dV@{IM8rM}hfw->G5d(v8gRpv0WD6Ih z<~?AoCIIYBTW1Zv<-wIzS`ay)KnX7vVkBk$(GrRmGcLPYj4g%gayTpRGX`?$ZQ3W8 zJ|pxUBUmOVKVcVRp^z3{%!#CO;AH%45?c3^Z~&-xts8h=(BfROAj(Mi?5OXgjD}CSDzGLJdpqs&iCKc9=Vp@HE zVo~7%0p!h9gDs9-&hy$I9Y6$`Z|eF0r7NZ`(x_UrrSM&u%iyTQLknjk*Wxlg!xC1n z06#mC?B=P0nO`$(~>Os^qO5b5y5@5 zCl_sQWIBdb&H+_Is%?u_yr@bgW*XB7I7^!7dZ$ajMEZ|4Wc3I zE`c1;_ju4Fj)pGf&_Ahe1`SZ^Mp;3}R8e2ED3NiS0ox1Xv6~1B_Vt&_0DDzN_m(Uu z+?Q+&ffS1chTsp{1rX*jYhVsQ!4`X})3pKh#*fpM8rVP>W6qVD)2qSU)m2_)=A|8XWipVQ%ZSzLXRW~ z1Jt!Ist<89B#Bt8s6n!FuEs(89stUsBnnX`-Ul51{6-ev4noN38SYb3*{v{tj_4TV7=x+h>EoG*QRH6iu60v7M&I#Ok67 zR~HvAsj_XWrpx^~Me2w5W$FR%ZnE}eFhy}UL&UY!6stbZx$WAr$QX;Ud9FKj9Rhhn zb%%e)m$Q!)m?Z|PCM1&8csXk5x#-G-&55GIB_i6#&9SvH=#Guzz(V{^-83WeiW=mk z=}OI_6v8t?=adKpsOXqP71P#myP@<$V^Pb)AlTzRCMcv6HiAwh(Ja=hDuZ)aOc;D1 z?Md7xkW5kF-~e6hRG?-o%RD9_{LGkxAvl^=`q876(zz8-6ZOctrTJ2cWXJ)_`<}W( z_4RIILr1m15<-p-(Xo=`$=#nc9f#uC)5STFc3j|4t8GCiY*5`1IuR2R6Hf8N#Z2LM z7mw34EWY5nE}M2P+nnemXGI2Vp=I_)VWjN56!>IXgO{}qB^J6YLv?N1>QQEpVXzb) z1G0q_V~bZq-I6R=P7O;imLjoe57IfAsu<(2Mzltc%^G3`1XwpS=06p229jY_F0o*p zCoCb#-8r3=pM^HGXYbKK3RCqtzYIN;PQu0|uv4M;4F`>Q$XqxrD@ZrWD3Z`8H&rvH zB%dT_C0KcE&9ie3EXs4bkm(Zsk7k?!gU4S~h8k5S;razoiB#?IY34{@+}CR@oxz zUk*Ugq3QTw2VYX+l@F~L9nJZCFTi#KXE+qSw3)%v#u(qVP1t9u+Czf`O=9AT;U|a| zt*E*Yn_Z_jFLZ9X#HYX$U;&?Ea%d{#!SW(J%oayv7ona}E&5`~aGddZ6W52&jL{NG ztdBdhfFgkO_?cGf8L6&#BfWI;?j|%xR7|0SRa^svqpJ}JbpzYy8a9Ub)Fr{0WeDv8 zJv?$a#>R;-wZPDD$kY)1)oA;cOpl=XY5KuBQZp|nfG%D>sP!o?5E!Ma5j5f{GmqI9 zJ`OVZ(YPNV(Gk+Unny9KKosTN?WCTu{ieyNL7WPmd_(J0wA`gEigHSI+s#!mjDSSz z7J3-5(wnZENETsF2Ow`LSX2vm6laOM96`wov+HTFdA)cw@x{ZB)0>|j>0O>R*!WsV zrtB#l0~^|T7c@4RSco(Bzp*8uV}@ZpQ>GCi3qy~l7yi~|*|uGpFqvS@fL(>-sOAHi zX55l`)qq8C5r(~uhj#XzvF~cJKkr9CMJ*;m2xen9xEd2?7TRy3(6w@lm9E z^IO8{u1d#-RurwJ&^Z-~^#?vHI30DJb0>RrN zT~mHuWggWKma;y?#gFqv3h>}^3fZ*G%`K04;-2Z+r6s~6)auZMe1b2Pbi;UsIq@On zx~Rr60Vd8l4T%aVAS3q1VoXL+!2$+YY*RNaZWwN+LDVwz?eVN3$G5Oaz1hLoh%bRab*7|Loa9U!it2L?WCXEB% z0OCx6>?S*)h*)OSP-?@nNSH}^m&bh;aZ2j6_>Oahffe4=YK@<@+uBc9^^GcI8Iy=l z9#JK@( zD#I5bq;5A0LX1y^>3awb1VAjeSM;F~*ANrsu&0Wd)>2$8?GQAEHA+ST+;v^o7cR}? z08$B_k4eC~qhru731PghT7nTO|nR@ zqqwoa!(B!svwKm+&-Z{y0I=28p?6%w1uF7+(H_Vl%P{?>KKW4R$=o(RDmGeC+_;n> zG2TDRBV!rXM(q;*ShjCm1XLDq(N|A_B2tm@CQyz*q-BLYt{;%=$pZyMya*p9CaSsr z#CVMM+IFGSnSiIjA?D%x`{^*0d#TPsAs&E%;{VL`FkB^fD>A*Uu8xPU*AO}nC-kUN zUOYH#XX9ff?tfxEtp5x`iN@io%nMZu5-eqcs3K>P(RUMgw&)ss5fILR3L$hrJf)aX z33gK}q#cO*2w#I;Zt4b}54p#6mvYg-r7`+bj2=bWetw{5-s#&etfroFms>Y1vJEAyZ-%%GW z2J)WKh&PT=6x9dTi`oc};0m8C^CjInDmiZk^>V7|ZwZzu%Gr@suf7z9&LUUiLr4() zaw=F;HHtR^MM`%JkCAz;@;Ep&GuH7yHk#K7 zpC5`LQ_hUT#Y|3cR#RFDT$Gz`rpmMXbq~ z*av`VUCljs`fV$u4%f7kU(|Mzz08NL$1ZVASo(W+sP@EX6y`c2b_aYM+IxlqPC21D zVNhR%#vwONp3+cdPOaudmdBi8yvZRLjq&8LH_s4_lPeF&iCE{w)E&WJ+&mc$Pw`$* z?@8cj8UD6tP{`rQ<$ggtjleMyqYPG^<1}2wd;2! z#--J;AIdsGf>~uMoVjd*g^5Xj!pw(r?Tlfs4ck<@v(upof*8p2lqI`WE)1qX8qP{@ z)zoR48?>cZkg{)rNo`fvO#{#W4x6N<^>;@YJbR!Yh!92+j5W~-btVoO$VgbpPYi6PP6}vg&5vqY zw}|wR3nfnMluShd>1j%^l1A&4#x&)*Td(F()@_&!x9b^3QFVs~Tm%w@u()xwSvcd9 zr(8~}hWA908Adf%1BoS3By-O?$(5`lrH>L!uJR}Fa2W|I_IVsa4b!HjVRTCvi zIPp+iQk;29+CZ<|uzwY83j7i-hzy{S<~6vKI8((kzz0w8vsks|RE~AMYP)(K5^9<> zcLHeo-OQ^2L^1(k!u|2Mv2AfgY4DCe1=plH6pAXvBPLeTKrz7sKj4i8D1>RcehVZI zAdQ0?LcNAs3tW!8rgY?ZzH_h;<-w&3NAGY>6Nav&z|}MQF`SlVnsU)pZQaUV0pA(N z%#<211m+b(Oj8=LMd^)UKnm}goJjUDr~yVG?Co4OZG%TK4fw2^HQAfEU&+_8u{k5w z)miH})zeY281x_Oj6%-in8yfKn6c`oVyZzjK`VlJRvKa90j4C>k(O~0L{OIiz!4Zz zmHSk+K<0~SYMXjD%uUCWgO!Lh6dv1}tE7@MoWWduvbdMc1V2{}NZ{;DA{G|un5V93 zVPgPnj?e>V)LjD`4Jh*Pam;O74SgQR34lWaL2a(4<8HomOLh5Dd*w=XyeU>2ykt=@ zhkiQWPp7BFwbOj#H1&N-W0`s!`LQmSsW?T_AbJrYggPbF7b&($pn&@#>fCwtDz>O-MvkG{hDaZeuROE_EC{h8 zE4b*YA!VEgX!x<)JXvmJb;QdQSE@5K<@72V1?K_Wxs)_|EL4>&4|(dy^&KAq3x&ve zp!xSr$?GA*UEp>R-a{ea{>VRAdVdMoY!;z=#|e(20msIP;dHPqw6|EK1rD-w!tU?f zax9_)H}_iC;w^^UKVnzh@GU;zYTj%tXxFo4fGKw*yWQFQ#9^A@(oyJ3&^}?@CL5tR z7@P;LfWKvIXNs&rT~pxoj`$!IsHIZEX4c_H>kN(%LD){nR@QpmD(dV;9EX%gRSP2~ zZhQe5VaVw-E4U;+1pTcSj)^U{-Md0Bm%l|=PM8hSU!(QY-xT&+}vS6POln@ z+w|gM7Jz-i?_j?5f_~Wj+8wHPDnK7}OtvqeO=xgMf(j>$R*Fh5Xr<&h7?Bik-&Kak zjcnP-WpU5Y_3m0I1S%9h#o$p?Tam7D?jSIZGd&FDBdvrF1i}-xt#yq<`r>sMmuA!{*;gw#7MJ{>>4BgRR)e=Lqn;TTr@ekc$?X4osbKZjx4vf`#B>NTQHS zU4FP`R`a1Dn99fldo12Rtn7LDlCWow&Y+NpU$Ky8y>#uD9y}C{&g`on2`;gZ5Kks= z4#!3=C^N8rnk(B=Bb)^k?14u{Ul}35pqr!iM9>4sDLDCd7dO>W)3!Dr!(oh13}jS= z0J1_2Lng8OB0V-~P#l;u#S*9uMZ(tEq~0kKVztKH`tt2iQA$q$C28*L^Ue(*F>|)@mnJ22olQ6hd!H&?Wz2r==W1I z>1y2dAe7GAbz7~g8jnQU6KxrWb*o@%U_glKG!X3u1h}`A`!yFe zsIx#-#Fu3^4r-&@S}#cl3KP0_V`j)q-i&JecyFQ6>1zz z*G;i*>tZ-7=5jym+Xhv4U8AXL!JpSEQVmf7Zq;Sf;aaZSVh@SVN)Z~&$0I;s@u;sF zAtu1GZI>wemD?QFE8#lLXCQ#zN3$ArOQ!Ams4!FBcBossw#xf$QSTC!&H{5QNxyo#>>jz<$)tpJZfZ$s&0TuDR+{! zGmlMe3A?*H!zKw{Hb>AKgr6ui6GERrou12P7`L0QtgG(0YvA=z=L;N75)#JcSx}t1{3c+tH zMaqC=szhWgdXB4)@(& zwLCSU!UK{Aehalkiv0mn-8A(GAf;*AbnW`|=6Atbn&2l60Dys|vafK8nY0hURi3i^ zOi>JNS6#hnJG|UZgfFp6a4RcG(QTa#Sw$_jtA{O+5j8k^Mq%32GLTbM?|eoMK2?eW zW#By@vo|&`%akeNS!`7*o{CHl(%iC3LXkYCyz2qd7jrsVZ$`*C+CFW|sybe^n~pSd zb5x}?3|Xkr0&)>!Kx7Z4g+Hrv0n-g-W`_e_cr*v;LE%#6RAn?SMdqxUYhTZJ+0wFy z!0lo&E4QN3hE-UGEfeudaROi~o67{Wy6CZ;J8Au-Pz2MYs@kSXJ>&rWc;4ow;f9|Q zT4GKf<|-I}roymn7vBm~1AGi)*ML|t_CwWSAe>UtEsO?AehFgwSkh*Fsz6?@3JZlJ z0bM>ap&8EfaU?EN7t@e(zuUG=-BOfCN3IFMk}^jmsZHx*XUEsLS z{m`sdJ>#lz%dw8YwWis+)0B-*lYa!t99|C?f|gon(K1`g&Ro=9g5SkCiy zmv3yR2Ok>V{;u6${N?$Z|6=>rzdV2EyHC!p;pS;qRkN<U5_LIh2bl;ZHt%qGAwWl!b_0{AKgL)>}#&4mN!=^H!YBvly+s2s<~X(b<+W= z0WAxo4r=${6Jh5FYpV}DW`OCe=Xfo!T{4+Sy|1`UqAf3UcDAf}u0dOv%W*1(5qT7S zpP)X*ZmX-NSg%@4SoTBJ(gdpp7FBiKn5LRmoqdlAO4n{v7u4zCfCa>(3T8>VQ!WyP z&P>-5<5kr^!3Oc2G_L@{8ZW&_WZ zZz$571SSjx_&qfPlJ-Y(sL3%I3(ltx`Jhra39ld5;QO>PcTrENRl*$&L1ZwE;8jQhQ zTxVwP9P}UuC`B0!2j|+wEGNig&WBgEFgzlNQR@R^8Eq<8S>XsJ zUS~wUSf;3~KRN+K_N*5)5AldOF;=pO`Q^{zEIO;j3I59kDatuhmF#0oT8)z}01)}f zSc@)JuSp0?>AZZpOWLdd)SoX-HH+Y*h!K5EzJ&ge`B!=9a1^X|VTro4lvk@fye;&} zDw5Y9pA8x{`?B6!T6cem=|cjUSX0XKQVY$hceZ=b%%L;MXaDwF?*H@`-bsv{3d+S1 zYl%z@!*4HJ6p(7U(8Aeh$GB=pwG5MmM$1H$ASj`rq2!JLIxhY(4=D}9wA|{N2Z!@r(R5YQmDN0g&7oA~rbRcW3R2|@38DC*Kqb^m6Dv}Y z8z8chror^c*!F-@wfY$;b@4%SqckT<{QZ2RRezvrvJ(^BZwql^b$9TBdi|cS`7Ox z@(|rU_=^=9%EE(Qn3&I)wq4E*j1O{CSJzJaZ+PXSKJ$gQ-Z<~;s_Rym(dls_oqI`T zc66`v=rNP1>P?f1qWL>t{#$SU>vnb2P7R2zloMcDCC*mTtCEXCSr-i_3pblUiF3)I z>lpkT=!^C>B0L%Kj|B8Ghs$$@N&&nn^+Mh6^EOKq-?orQaJ zKps*BAzwPYWtbTUq<{yXKE&?j^g;Q(Bg)*1AAG_^)}lt7`fyHHX)jMxKOtZxsaSxb zhO`~>XMXH$-}hDbjkyOcy|ehRZC9TA@%}*b2ldRH@J&)vtY7xJKmM&hN}GCHb@gi9 zf>aDkI4s5yXDkCR#q}^Foww~0@*j{(nC7S+6^}aC}jkTNy0#3UJA(at4hX{0yohRe9{YX8%vW=AIXP@KyAjZ2VLT z>oPQHLL?(k7u|q0 z-GUO?{5EN>r>W|i={*nDFZ}y&+HR+&Ev7W4Jf*S!7hm(pkN%+546G9WammMd86D$| z16z3!FT$XqWyZmrJ%o8#${IFx&KsS}2xH@yhkysyX%)#S|VREH@DOxM&; zQzT_=qcKnOyk3pJ`=`Yhe&gGZ)}1tO4UCsKyiI6DZ@V=7>woy9OIPZgS}g$Fl7Qyr z=s{B*?6rmHt*-n7H3zW&XB_?PAS2z~=n0vd{$0dK-OLBz#pw$$j!LcN%&!G7wnX#Jdbm6 z;kf*@-#+=;?|#dAeY6|X*pIkS0C5{);qY39FQzm^b?z}{h}+b;;MxEK2~!7+J!Y`{ z%eh=JZ@Qe)&`(2;r87?3A&wdq z8upyDFeP$T_d9r^$SoCABRF%rzch3f**jQ7B)tknbw?&n6WP5Y?~p+$sRYvB=c(Th zyO+M`>Oc9qCtZK|H063DuuCtKTvIHd#fr{`&(`yC8}Wk^uh%LUZxA709$oXNi~j{^ zgM3&32}Ye@>A^+m`E95)+o@Hce4h z9XPC1;)M7gU^zTKd8jpr-&CO+207Ay-)%SGy3o7B zS4nhX%EVl}2!m{A&7RDU6iy_9h<1?-ac-LINAacpF;rbk5~GLOaUkp3USgi*1m}oO zacW%zxd#w98=$)TgGC@JiL5;Ol^#jBUA}k$d4)o=uyd3Y-gKt2DZsbgH2CfWuX7$h&oEIekh~ zM7D>EH)QZWqS7Uod+|Y$QKnkR?yDM;eIokzS$0S%Y zJ%eKs?f~{+j=p$t+GdNr$XYyIbMJrC_pv4}pc_wX*-Sd))-jLDQSi?V8&KSWsFf%Z zu>Y7Mi|~yUj-*4C7EP?gd|GLAD61zsHCVq8X7pCj;W)>jpACRhg)@}@n8eihyLC

G326>m?`R@LA|9JZ=zxmK_{K@W}?@HxdtyY;PQmJa%&AJ0yhne>64P}u|#5If)x_2H+V9ssdDfxrbBxbKf{ub!F zQ_)}?H%&##ZBgVe|H8X}?pLn-)*JU%F72mPQ#Gq$mk~XVcghKp3SUKdipRzE$>$mo zWPEilg`=!?yQ{DzOL7c*%Dz5$1u|$9`+!xZF>raL0Z^}Mj5Y8u`t#F$^T@l4ul~Y2 zZ@qkS`9j^6iE_~dQXmUdf8esTL^oL{cxzUVyeDrq9V|!lh%qVVfvKilqLzcBkXU$u zw?YyuPj`a)7SoBbO<2cc{6o#Hz|`OeWe&KQc!XM?ku<~55A_50wy%BpBdhg|vRY9Q zX6d@N$a0wwG*@8{_tL7a=XxH8YSq?X@p%t?(Kr6(s+;SsS*=z>KVqCHT@;F45m?;>H)M!h{Ag#91&%x&(TumC+3H>t-kmV>m>z zu8MIe%Hqb^{#_6EfA*IrfB2{8fAGJzfBu*Kjq7t&j`bQG;Ua^d-L$QkX5%npPL>e} z$DlWy%4qL(tnrpW{VYs4dl#G&_9JJmCnd*~-aR{bH)5j9@SjfJfKL7cZXdN2sQ0InwewC=bjg!*Whl_~eM=aQA($ zd+Nvi-8Yhdv#&SDyT0gCt`$~NRz-so9bhfXcfpT`Dn=L_33~^pP2GD|s4nG=bJ?Tl zTMRFxHI@gMLx){}a?`IMZ-%_RZHu};AI9nlk0`$Wiyu`^?_I4x-{wy?PnOKRBGaFd zYS`Y6v;F>T)7EW0kMl^=6(ED6(96u!FHQp}pv%DBnzniLy~X7#MH-RXPIqt4 zS;<7QU#XK>b<6U1IFhjY30H$~CvGxqDP9lVPY|WSv>E5sP}EnhG|zy zMLA5UZo!5~1qRShd`x|`Sv7P_ZR!sCgApTx8lF4VmE-a`PnesdX}uz8gDwed<{kA+ z@8_04`A8XgN0D#0-&ZL;RJLUYK0k-*BDs;X=BH+sr#i zF{o|k1ikoucdnlM%q9(O+jKLye6oAt-B0UN$sduUOM3>MH}x>$u6y{Qsw_Jk0ae{6 z8Hz?EIhth98R3sbxgVb|ZY))-`XMgmv5yp856p$8pTN*bTSR*gr-89=rfJxx^I<-^ zP=3sZUU<<9Zu!KIxb^ls+Iea+C7iqST+Ac5N>xT$tS(SVZ0lkkaFpp_EHR2ePLw9p z1N3b5T(whC-g(P~Px<)cPkYgw`;+tse|-9%|JytN`>#Iy&cEs5?9%R63MZ~zE%$!03* z`e@bMdZl~RBcM5g=(wJW-O%sz+aKKi$y-j|@WyMu_a`TBd+YATDVmmMRaL2~x@J|k zLjmRkhFpD`#!Tjkb{sx&ag^!)sWpIosvu8W*HVcA09)=EHU^Gf1HiO3s)Y=OCGFr9PS6@hT|WkofmbeQ=?S< ztKqRQUKfZRX`($?`mAuHv?oM(B&y<*;~0ZMBN>1YyP3*17qd@Fq4U9ACJdG#xnhZL zYZ5`>U@cng;L&a9BNmDQ5m2Aa+`jxBnt4awj#jS;4m>ODW8ee*X1`0%YY#-U7_4|c z1$B^YIicxhw>dtXO#UoiuFRlAsX9ds5kQd2Z6ew5BQ_dv1gDAo~1rhuzR^for7CQ3w9k~G5GjnCgv?G*fo z8$px(2uzVhyBLG^)QPZ9Ub<#piTJa`zXXI6kw%9xtD^)gtr8E-7B}wb1>10%Aw~-R zN``X2tk1SpH8)Kj^4L?*FB^a*z>Y%PG^&Gx6tJ8z1aifO)Ev>b93HAuElAtMz`H^EkEe2B0F5j+1O)nZ9K!n1zvs0SI$BXrPE;H2xSy-BWeaPnX+r zJbSpvBbCZ!X5wbuw1UHFiald`kgIuG&F$s6oBqRheBkq5@+#NkO^r&EbVR94)p*bTPA!7itf8{_X5&Obgh4~{X; zEXQr0id1gD_jQlG^=h?0NvrB?F7p5ZsOTElYiXLGTqP&9YPuQ!zN#-?9edO=B-J)3 zDbz`V12HjpL6DoMyL7eIHl%Vy3Mn`nNzA|WiaJ3>l<-AGUL^sPuX)^XZiVBs>Y&E(yoTyif9gww(V`7`ALuYo*#PqU%h9lce}Z( z=9F`vn{EwJ5!k%=Vk{+qFp4sW#0PxuhB*|9_Mp~IT&+;}D}F;~bRfC#ynu9(Qgh}P zhpcc~)K$k(%asc_Pjm+IT5`p6n24}&U_Xh;8CDC`jh;X7Bvw2+_3>D-OqWo02-EJlj}ivP#9+HB zo%iPt7ZZ1G;HE0$sCdVdtlB1x(^NKNy?NmN`D;J#-f#T=zqoX(N+h7vXE=EfF>!B*q7iDz%)N3N~9{+ zw{(~8*zfnvR1S0Q`)P&NGuL&s$7V-@#kBA9G(;@BwmLtxrUA#06I~F;;kCh!NPV<4 z8Lm&zvP;4`YPc=*zM(&eaRlb+Qf$c!PVf_B4&0A0`pS7fGK;b!pptH7dqG1>8^5|T zP>g2Pq_LcuO?z>3em2%444A-Jq?k|*O3JxK>d1WkEZuqGQaaz~;X3WjRKp8nlYWNn zqNrXdJ-T^yTh(pOwyDb1oQ9%n;42h~j-GM5=3@L_G%o&Z7g;WEJt^H;;K6JX3&%!I z#EQ}7Pjxkc)3)7Db3bg)M0H{%!_!g8I5PQ9Q@uh|3U9l5YA=^pj`sW1($cj6y$ep) z)vB2xKZ$iZsF%f%xg2gw=F*siot80Kkgig`Pf+de({{?+Gv z%59(dNq0QzF8qWs7rWDb9#2bnedK!1x;k}aNPy{dPo#%ZyGZ#}-N7nl8kJ(}3Y{K{ z&9ra&s;c*!xon>O%*)UFpj-ao$@t%X`N4nxV{iYR-@7sIrsJcTQiD{KUDLD>)nE*U z)|l5OT}avM)8`g1%9RIhOQXRKR^TVXnT?3LXHi`4%6U9}FMu!F|5f{dN_M7AiF94cyJ1}o)#B8NixKBWe&uc zqR1mce&~iMnO9A&pOqq#44L60!h-FwqqDS+wHlQSkc_=N0nA`DI(*tBZHXPMW?f`J zYK$CGV|o)G5$94qbK@LUf)h{>=Xb&~eGn2d@^;9-1FAj~W=Ys0>T`VP^4Yh>%dGTc*Q@bMe5 z!Qmeq#>;-K(xNSK=GL;`FMuY>#!~(TywHe08`75LjVMq6 zUfKP!m!qiH+9A6SIABr(pwRi)lOR+BVpw2eFB7LlU_wj=_$`BdP^bkSttqYjAn-bI z6f%a_>M+|qa|14fLUGF7o3Nw6V2^KJRRv!O6C3BU^MoJ5IoaqQ96zlz6p>YVo8B;v zbqP9&(pH3nazH7$!MU$-?!S-G8y=N;HXV9gTbhr z=q-ov5gaIrfTZGLl&h}Nr!Re!q@cD=mN7B6i1{p<=OEN7{O%;au~;&cE?N$Z5fXd~ zi75}X1t+zDco4WUPQ@+_BbHdik}%!^T>!SJkA6@^;Z+X&7zw%Em zU%oI+`);+y5RkG`ed={pCsx&t{4p%)liNab`Hrx*mSLc&Y4b$iy{IfBXF(2sc*LF6 zL)1Vk$&W1=%{@f|uO-sULUyeqWXSHkW7g3r8dh)*PyGfdyJxRZauJ zzL_NaT$SSp{Ub_L0xc-fVq|4IXxS3_TykKEKY#nrE4jo8iP+`3owYInbeSmS0iZFI za&C)M)Xfv`%`g4rNA%nGb@MQdLydI<{6-*`$GIs5bx`7qVrCp5&w;TjSLN!$7k$>9 zulw%5KHjvs>>I#Qkepb|sf0Mm@vx{5j4FOc8TFKI78w3n9H>Dw&la@@;*$_5z}0~d z4^txgUSWX@BSC?=nD$eDR^y#e;i^Z=(;nXqtt|6sb+!Q#lkf#aZr=BcTT)0gGu}N6 zN4TK?+@Mx&AZx|T!$FXeZX7B+Sbdi}8i-CsU(ZuHQlMN^M{~Kp_2|NjKkDLVeB7O9 zC)?kA)7g*y+Rynm%fLmyd}t1^{S z?)T$MUwHY$pVyvV-&Kgi;F@8-jqvb1w@kC}H7WXgTTlI2GmVsPO-&7QJtug)Rb}2` z{vc^R3{&dKkq<5hVK#n-aLLlck?t~&2_llFf~k*&t1_kI1tWRw zQu(S(()G*)Mg@{`TF5{d7kV1H(>z!xA@-0Ii7fM(wg|@*0k3quOcgTKr#$vB>T8>_ zs{3&dIm?__(nC=`ryh(ThDi%pM*EKWKSL9k-$C7@?5lW~jq(V?{>9Okx%z|Pqe;y) zN-_e>(JIb7Dn)}Nd?Br#y>QY1z=L5%xc5!86zB|?kQIMUPP$<(3(cD+`2X*Fm^QaS z&FFSGRtGpm(8|?Gfb+AoMBU-wK0Pp2m@m+U4?H;ugow9ExSk*lm!@Q zY6NI?9XEB=4{6=PT4zrCwk*!a;v|jFdCKNBuek5iKI&>!_Tz59yD^oy$Hj*qkDaFB z4W{@5#dAP!SY{IpU}Hw4hhZNCS%7~jMq1iq?9;J_V6Uo*;jAp{p=$E#sHw{rzwq|Y z`jmTq>-VpH@4tP^&;QcU3#&clv6IDCkXe$?}GXnnNXvNa-#hZVUWs4`o&cFxlPkVR)j zC>e}r2*jn>f&U*9awJbPH98k%I(PVDS@*kUu2xe~-+s%bmwoz$m%rrx(`&o`@oVq< zk)M9>H-GnZzpXawR90KOe;8U|{pl3J*3WQ+t$BK1MOusvqz)Xhg=%xk1M@Myt+Nt{5edCqV(Wt3DkG~|nNoC*;e zM$+M0GttN>l%h?Yor5HW3g4U(D58!~#-*PXsKBX*O@46e#aD?tmPzSl3yGdb&!LFn zCw*nK@GQO{A29S6k-z21{tC2Z!a23b2A;UzvY21;zYP`k+4KcaMr=KDL@$~ z$1axSF7kOzMh2z1pTS`C`v|(ROemerV>tkUVSn~!`%2(wwX!!nE0yq52riJQhl-i- zEAnUIsUoT2Z1_VQAzDEQ9PB!wsgd9gp;mgcUX)>_xwuaUCTHSAJY>D1_zQxLOpN5? zcV3HzcN8R3@ra_D)wcdB=;)-And@WZP_D%l)1e%O=S+?zb=5_uMn4jC*lxz-I8i@T zWiOhL_$4kU)snitO>Tq0PPKnb;KQt#jW{!T!csy0a_w6D=)*V zJj{7L-NH$M8%P%bY4GflQ8yF$BgI}HXrd&O3mf$2vM2|nQRD$YSU-yiK0&ph}Y|LU!O_4fJl#cI7uQ`Hr1Ll1LMfUBmlK_(A1vQ`BPDutNmK2IFz zRYg{_FiK};1v7uSV1O};ex9R0+FSv5V}5X5&f~r)s@?VRQ(t)3%m3$tKm7A&7gwp- zRCB$i;TzpOux?oVv5z%~7$^0@s-rO#5CB89H1iNfYggS+V@9I8BpkT57quJT2V+}^ z$C2>_*G!~u?)!Z%?|#Jmjjws^z6V0mbbV6*L21C1C54`>b zm)=`3qj~s*pO_|`L={i2mHywwJ?2!$dKSQ z(QPX*X+#xL%MZFL=Q@mkRr4&zL&wtdDViZiM>#l0rk9q#p7kv2TcfCLT$WOoPhkxeb zzj=Fkyjj=t7Iw95SGVhFphls^G1IJS45lE-pa3i!mo!@tLQ4xnN}M>^V}hxnP>T=r zwlLKfHK-L5cBirNQdL3UyhFsf<9@L zInqN%FrH6k*|ayl=Nq2=@n7`oMR8oG{X8P(xa}I`12EPelm)yJ9)h7z)0^S!L6=|< z6T|aC_gUnRyC|gQ0el-1qgc4d7)Ci|SUQX|EU0YH>s3+r!!T5L+*!Q-RS%5&_qKV! z&cj|53NM!<;(k)efT@frs+N-`jG`=|KxWVYsy%0wtE^*6aoo;Jr~yk=q}ad$S;>74 z19Z?FQ;B$h$SWB=Igtwb4mxdxhaLDs4(0`~Q!t+f(rQIy{W2F`+MGY?fB1TX9mM!P z`^%eHD}WO8csG_gk3|B7M{Fe3a0{G_Z2`C%IisNBtAtZPJ&f4GolN>Od&06~av~!f z2Z&3VmGYww8jVfxTw$o(63(6Gwk|WI@0yg#@_=o+ zX@EGp=t@lt8Rey5q_P2t!DKe(iFgu%_rlp8r@i#)QxPNs00T=0>wDDOSW~$uhN@bj zf#j2DY40s9kPl81vg8|=G2mVps<<3Q3; zzQH%KStGo4Rp(WO44QqeZtQo@dg9TSf8pak`NNKjDi8Z@9>-=H+i5H^SPek9unz%b z$mdi%W)j60V3yz^i*OWZgnlYa(IBYA2hn;CXM#KZ!^(MVfxqlvj^DJYJAU?4H$VPw zKJX9!Z2Xpg_D8?)s}HT3^>ls)Cz$o7XyuNP>J@ZDZA(WFc}+0Goo%etl)T=k>|uo^ z6`l;=l1K^wBSg%Ak*Xp{$d(typ5+FdtwY}}82RSF_hY(^S&825r5p_-vCC zJ`rJ->n6(-!-a<(9QNqLRTCb}20b0O#h!1mfMIlaI;z6N*D%6iJ*cY3DQiVUW0+?f z@n$-5%=`&t={2oBgx-2S`7)BEcfm0VcR6T z{17D~i-C&(<%MPr%j*f7B^-x%B`lsIZZfEpe7~}mm*C#@6c@Pu7LgRiZSf&f3^3?T=B!mo(Y%ASfxq!%&2-d!Bs5tQU0 zW-uSLJPqu`KnydK1m=gjFZQlmehC@8qyLA3x;okkYB*{@GW3E1$z1#3PF%UbzSoP%3Z8#Qbtml z_8)wMYNR5~)i~$ADN-{H)7eAC`NO-@vwrGd_UX62@#jC}EB@}4v;FDW*_6-E>#1LL zRmx+dH3L>{+3-x|tE50d7Ss%6k|bX@C;aePa3E-dm9G*e(1n8k?vORh9Va>}kwIH` zpr+2#+@GEO)31N>{f{Wm_hmiyZJFA3W(ekJ_Ze`%sV^ahrJM&wOX4HvTvqfzquQat zz!TTsH-u@e9P8MM*`*<#N3p;Uj%WJZ!pj+B^`@=r+)pU0_uu`MkG<`da=Y!T;v7LV z!#+sNE^V>Dv{ig=N$MCXCVP^&sES5ku{5HJaamdeIMy}Wo}5Jklk zM&nT-$DHjTV}Oun&ZpBhbg)YOoa)CsviyusyzhK_QjL4AKNkFko3RK@A~c*H<8mBm zB;!|wl-s$_S1+wz@#%MM_hUH>RXH_ngM1THwOF!)Z_i2<`cX^6;JD-lMn6!Bby>KC zC|dv#Ra^@9QImk0h`U(-&Sk(3S=g~aWK9IEQV7EU--!1{_&^$^KZQ4jyum!PWv(yUEX(dzh0N!rbZ8$00Thx&j*g&1NI4A@w^1^ zS%)2$+B@^D&FI$rg_}XV1^V5ogJ3&FO;aSN7%2*id`fA!o>4OE(iKl#)R?L+Tbb;! zC`AZ~p#b~IFuIt4GLhvF1>#d=UMMe(Y20m3pZtX5SAWiZrzd?gv*B;J(-8zKM}Hzq zNHo;O=R@Ebqb5S{N2QMz#ga>=>@;DcE^GjX8gvjTf;}~QNu^ujRGA8rsNr8-=N;@5 z%i&vIegAE@Pe9q|moDxdW~_>@H3>-^QqnMKs400c&iD$+o!Fy1$Ssf2XQK8(q$ZLt zh^A4D4n}dnO%_)0EwSA2)K2fx!Z9vC&I|ZA+<~A&RUd&*f<|>P529X#*D{qfu;rVO zWE6G1?$Ht+gf5gKg##PGYQYAt)If6ueHZ4oEpk=W*C{hlh9tU+89K&UIAr`hk82L> za2#+ri(4da#+sK6aBE>oQ57!buhO)1lwftm>_dD~+(G&R(K>y>o8gM2F^Vh>f;R1- zguqbg8lcRPO_yG~s!RU}cB^&Q<%GSCClKos@sKQ5b?L#<1dJJV3p}F5XftOlb}n8& zC{&&@0ln5sSNe<3p~#@?#777ikJZ0&W~I%@VqERbXaj#U@{O4U37 z6nQW&Uib3!x4$u#DTQe?l9s!Sd9*mUi8(p{Fc_5K*0S8fBp7O5s%S{+?TxbQ1jp6f zfw-wpXs*(>nRaa%{_~)&6yZ!!TTlU*}+E&E?*nwyWv!A$x z&>4X?=Q@zxvgRN7>>z^Cl>ojiDc zodKNoA;QAQhAcDy=R0G^Euh+#!_kzeOYsX))!ERE7Uh_n z@JKV1RG9@TPcQl8OC%H-$=tpTGS?7C0z=8%&8g{k_1TT#p$E6uPR>uK$J}@6Uw`-0 ze(%3L<0UVwhG{p#UZh&hW7kZpqYjYu$YlUV1TYe%`J%{V%sdsptm+l1tl^@Gcn4`A z&+KS73CO7-*MB@^R(B`_*PTH4_l2+XVjr+@((Mpqk&Nm@CDl#Hp;;0gtq;|OZ1gAQ zwH8*Zr{m3Li(m05Wi1;TxDeQzrXNuT2e(VpvT0_k)NMCNylx#86*R%{O;Cyz_jr_$ zBDn(MUoj%AXNw`E(Un(iqnr>$uSmr^99G=aN(V>4x-V60bz%k}|TBl+klz_kZBCM7-eq^R8 z0?ij0x+U5A=H|u)Im&H>QsM%VbM>gPmF!qT^RLQL)`=2fX>Gys&E^M?_Qh)#yvHAf zj@77<^=(=P9C3$9q{~)gXp0@9z0>)Rg2SC`NarM>COo90f?W(P78;MF%-+3t3aIh@ zJnceEm4)t7H?aJ?fsu3J*t%RLhYaC^w9by47pMs=w85g+nr^vZamkuPKi5nNAtrK= z5MfU+nWpOaTqsHt+rsrbb~Oq7dV@@3;OBr?1C%mss`#V*wCw!62&(9^-VoKo*3~yg zNr%^+1rpJl3PWs8%AvPW!YA6|YHlz@L@9uJMQe|RAg9bwa8A=WjVW=`m7&0FQiBB1 zsTliWx80uXb20prZ+hxa{ou1NUf!M$C8ia__QHh~6Xjt2NVo| z4gFc4U;GJ|KKY}r?9a!eD%JC@%)Jg8E`I(rLIFDe z|3n^;S$E*K$RUBJG;av_4a>w<12WXTdgnYDr~z-FRl=+v@MKL`H*O-G>pJh`n@tS} zJ{=T~AW5}t(axzIclGvkKHF_i=VIQx>_zwf#*aVkAAij)tK;h@XL;JEYIj=YzHQ5< zgHZ?}T#Uk~Th{s!0Rcn}7gSvRvZTX#wOoS$d*qY=?hs)f!`Q4HG4@g_(Qd~dv_}@l}(iTg8NC8;B|+l&Y6EKZcuxZ4DG@Ztf&g3yzTz%lsgM(uE2HrsPd8$KFqbl zIvkT;J}tBs^>Semf}N{|cNtD0{2RD^>GzByHuk|6d~lNik23)fu=YTYufj|! zE?gp_E~q%TCe#5bAO2!7r#?;nuI|r^-EMa_oeyVU{&~0m)=z%ei(h!x`3{K}9SkkVLsE6~uqWtHlL z+m;iGrfZ9;&Evd1+i&+D{y|rN`)5A#b+5jsPuugpDfWFaoUd9ukM*kS+Oo!-=(n#_ zX`ICL#-52Ot9k~cx8%lS?Fkg;Zl*Q_OM&(2LLZltff*9vjmFXk=I4Pz=r+YN%*=?F z6Oe7jmD8YaWMD$sS~2V(~d=bGBCYTIhv)~k80hoKne z{qFeod#?V#|M7vp@zc-zxR0xLc^r0ialS3K=hc)uJWebEIQc4X0X?|@Y#IM+p+%!Y zA5!A~wyu!0t@M0*r=-Z z2wx}+vZ9EP#gDQ_<)ex7!Pn|d3il=3E!tjV63zh+uhWsGBw`F1A0m7NWGI;s^B525TnrMcePBV=jNFKy6d7IISWYOD;4k1Jdj0FGX@{d>qmEhO z3HrHK8HO{WN?1}k*hvE&uoOl<7q&GZX;u^+TVeZ$85|Jk%m&qr3Hga?Icd_PRm7Uc zBS3{I;*rBA%2lx@_%4sw(AqsD2%4cII;d96HN-H{Sc$NNCf0zvI~TTizuExN5!w$$ zL2ml>O_?H!T0pWZY9q7Z{TB&L5&jA-gEvyJ?k!<7QedRpDkv{vQtw6S3wJ+SOvF3k z!Ga`YqkSOI*Yx9X(H=Zg%sg37EPmWZI6&TqN}R)1oKHNSeK3j7VJjEtlK^ZBwp?c5 zM*mp+A}d@yFsAPM&^37wRK2ts#;M4umIaL3Dw;5AR8~T*i4!(N{JBW`F%9tBE32Yg zZ`MZ_JNQ-3=QoCrdfwGv|H zZP}6x!3Lh?R;yA22k*#MPvjbT&HD6~n!U(rPjj`QDsq{J-7tU1b1r?!OYeT@TA%j& zv^`JzZCNqxoV4gLG~aQ@`0Zcu#57K+-{;+pdB2A}VcW9g<@FMTZp4u(?t}~ov^lz` z8d9l5bQFS~C+(+*RtjX9oJLU_ggT1Rt%NV|A>6X_rQ2zQFTnGT8KIQ2F995o=6>I` z)sya@U-E)S^{3}`9(XKsrd-$H0eQgblpWQhEU;;jP8g5Gb5YY$Q|#ulyz}1X#V@$9 z+vOI7XxtWPm{D3$ErvdTpOVfWUIe->6iI>zDYGi!+oZ66bPt=nW zJD$eSyYsU&tB%uQ!I%Ic56Up%QoL?)>~PLY1wD-fCHvRzZgnqmprZ5I2zq734^`)#8YnW&IK<;yHIq=J zws1D(L1hhI3;?i?SiUNam@)H6*a3N84ZE)gt`=?prqM%MVHh9$W?^qW4-G!^s3u@t ziMrnBbW&Dl|NI+1aGrKe*{qtPsWVvHqQRCoE7Uznz`aALK`_cq;$3?idnc%;f>WUf zw)uchG}+H!!=@|PBUh8LD^ zD(_@Mof8JV5>;a>KpAU?IaKUSTjH@=(*_U|atwS4Q?RlW6yiv?MVYLVKQH49JLvlv z2-W8TCGw*B4BrwFeYj=H8aX^fH8oaZ2%Nr~M+~m{UDa`x=Yqua$;Dy7;fWH302~4h zt_79>&m1gD(?l6uO})AhKxL@$nl`0ofxvLQX`Z3hT)7xBuN9Ztu9Z~Ev1O6Wh|q)- z@Z6d)c492A5C#4tpd|)+BGJI4$-_=fMZ}1-xjkD@(K3UA<+_V26A_QReq|woca0S% zA|Y)E&CGVmFKR|alS%p(J-aGAm7F2wq|Jrue5K8iN24nQiZejXavIdV1}zCKcy(sP zC#dFueYf0sB-z#jP~~HrB$mo(i)mK|Zj1_ke)N_$^RC0D0h+;&A~1126OlO;;!PD z*Ohs->dJQAtTs)%BG(zR7WhEwNs1mu<^coK+OlqOSyVON2h1SqvVlX^T*4V~YU-lJ ztLE7uHB&773}i`TZFX)dv_NgDR|q+8+s$URY4a|nF&EP}eeKi#*Ux;!;~%p>+fVh7 z%Kk=G4Be)zQ7oaNY*%m(f*Unov&O@OT*N~m;>6$|%~Ws_LbuPSG&*Zsf<-eTcpiD- z@+Rj!%g>MhO(ucSE+wBxilHY(ewuCJd}0&fU~#D;gxImPKb&_7&as_#w3gj%!Y?8?*^Mo^31dQAZikco(L~+it@Jv7Z#K` zx8NpyM0oVN&D2WJw9l1-dq{3PbsOSkE)c_#!4T%?X7ER+zxdCZJnln6C7;{07##Cu zSy!V-DE}1k#sVJ*y|m~96tYJXojqFR2voE|d~mD*l-3tR@n9FKOB5h05|1kpFw!Jx z2|j?NvEuRw3U108Q7KGW1FMVXwM?56Bhq9xNgo^qg-_7q9KHrJxeQv6J?mObCMFh7 z1l&MEvCtbbgq#KG-a7K)M2k05auMt3=Xp-f0yc){CWTnVuz({Gma$w1R>y|>ivOPI zdXW|#HA<)(q7I9CSHlFe@-5BqdXMDw1?tr=W!M!+h#?h&RuOu!Kq2w_fm7L7j*Bl+ zHf1B`P>To+v*)b*{{vpR>4ygY!)Qz7ip4?<4o5^3+Thwt$Gl0~JNVKI806qWy14Xe z^0MT3n287Wrg@A9UkU!{GOr2(BsWDQT6t@c4iG=q?P7ewcpG4d+B84xK$a_8VF$t= z_~D00iM3iJLXtTW5msE5))^_pPSW(C(<}LBdCkF(#I>v;pZ|2RSHlnjc?&W)rTCbW zA5map1uqWcr2k<@f%ZxcI<9$AIjH?>nyP70RVSj4 z36gGH6q>fKcigKwuQ`wXl>0fI72|0$4^_XdhW_m2{GL1OpZTHZKJ!WC>3NyYw-XeV zobHL(u|U3nw*izWz>M`Qj{%l1__-KgIhPK%hTIg)zVzB-Nl6|s`pBuAhO!vuJXE=_ za=+c4|D)GF{^?Jsx94SvaPJIHHOcw;;BXwNpp&>(E6tw=KMZY|2wzf69jh=2bQEq) zT_HPJG7v~?@t@D(oecpe^S3dsE+wf4^s&9$ZD@4YLY=*gYcSJS? zFLmPbk$+ni1r(ilHg<>z0f-iLPUKSrNzFxtiy!642$l*FuY(YBEIppz+KkL43Q>Xr?1F`+YO*^H{z5 z^B;4x>T_mRTSFH{|8>xj0a(SLR{MIP+L`zSH&apad3Q1?UR{T=!-Je40CSUnVZETx z57T9Jd+5wo>98ESlJQE}Vao&V3QWS#^R3+3D{S1f$ya|Gh=6DxjS5AX+FuEc| zNI))eh)O`y)vHytYEm_&?U-Nlvd7&2h;nxhJIR2u6)dyZkb69(d+K3=4)N6#fK6OTc0 z6}je7!J9&5#)v&YIPm6E(lm4lgd)bvjey1p91i~@Ct{Z-qQT)dOF5xo!;wv^07^9g zO~{EH&m4CfZT86!Gw4DLo6hFusKn(dt6h_XRqC-73ulML;>T`K*5m{u`C#6}JWnNu z;=jPc5GcjDw68EZ2RJ{=BI4lr1-DY;p{Bu@d!U81paJ@^frP>*Muxo!GjaZdYMa?z@*;aBITm2Z;qM_~8Vo1*E8s^!R~g{x@Ya2a_X?k*H(8frY?%V6E6Y1qx< zb{@~m;k+Dn<>~vU?Zex%?E{b7{Li2In9qChg=>8-t5u!0{n;7Pe=@>@=6OQ+HnUC5 z_qAC7=h#kzV2#N7&_z2S_bFxgw*sJuxr#*A;Z~rA(7$3|8aM;heAf0dCyjew*d#@? zurTvzMp9roQXo`@eWQ%NRAFjG+s;!MsEKCe%0v7MWAZeN^Vpa3*i3yljm`cn-*|Ai zaejWi_~2(=`ThU;yjOho(Y0Nl#%kW)n9^?5L7l}wB91Tp*|ESRCCrzQdK80_j*0W2 zE(iyUvMB_Bi|K*6@HZ2>4-yPVGcTiU;6B=KdM1JpSbcJ8L4uD099^C`63{=?s)y+9 z7G8?!LW@P-Vr&?_rO^%B|I>wKF#uC_q=qrX6y!+V6pp3C*a8NgU}A(XU`k}cT38WZ z8SRxyh-mS`)0CKi+UF(v+ds-cimjS>9&woxV|F;EFzskrmuEnnOSVJyu27nDbaO$U z_sd`OS_gGWOw+AlSQ<`y95`(#h#FG1@i5b$@l1JM7nXiv5IWHzQGxpb#uYq(m3oF6XRn>6TSO)7M{0^+E5fxIeKa9Y9 zmFedyVBFtdaWa-CIp9P%GJz$gQS!-n$fig(Q8wfm?5jeB1|cFLKGu>4=UhG!WW4bG zQe#DBMwoGEG~_j+uRo-L9z;N#P|BE*@&OeG%X1cQ(WD|pfe4{aiM=xW9aP^`rm#nYZ0Kq_kO;bKA~PEz;%B4UgtRaHRny4}~Fkv*OniX`rx^ zrxWavK?fn}QiQ?-Ug()P#*Vh$0Q8dEuB^s!?o(6sKk%I&FctfJ;g^c?o%r7ySsYH3m)B{ z^>r~o`GFTHMlB=)_^}+4lvPVQA_87CpyV+tYfpB(6Lccr=%hXm#iQ@veCj7$Ip6hl zm62Y_^C9Sb9K^9-m!Qbj(84ZhD@Zz)x)w7BO_pH|=CQrjuM9plxgbqji70MG=<4PP zBW=CpZx($0B`k)mCyPGzVt9*YaXB>4xFK@}5qw8zfB6ut9-8Z^Zj_%ON;ctnyf;Pq z=~bI#h!&Exy)ors7~n_>pZ~tChOWu0rdZ|uaAW__`=<|l;_fd9O>>F4Th%c88&7uE zAO40{J?-vW^O%Ztg=46Js3&P!O%?KALEA!l+^}F=+C$wMusgKy5Jk%8Xrp7*`wAFp8fPW?ha=lvY zZq!%CEVL2keyoU?;bqW|)|zX|^+H}-*G0ouCBg@vt*QzhC&V|*uNPYz{ShY(hAi<%%C{mvGL|{+6ORb2FsuqlvKipV)WS zbSQ@?8aIBW1%|Sgr+KPgiTHecHXMvGtv4oMKG!u^7W5;ZBk^Hr^+n1STSj6$EcOGlz#!_WBm@4wp295nC3hp^J3a#d!+reKP`q~&I$hs z@Kt8M@(&Ti&?p`(zvw$Yk=F)U>zIb~rbO6kGw!SH_5JnTRIUES_dNGIzW%bi2;C-m3V#9D7EGH-X*E#7XD??vZU{w{_nr{DPz6e4{bN>>bYNc2q2TXzzi~#1~Q|H z>7zS@(WA@|yxHGPB|ZZR&1Dw9JG}D<7BB8!am&dBo})Hms767={?H@x6{Ze{q92tR zM0z}LQayN3Lo5miH*=z?EDHL?rqce8@!w`;gbqgznl4gUdZ?vUwH*!&R6IxSfy@97 zsgb4F<+?CqQXtxvA8Q0Ac=QbT|it@E`&kqdH_-9LT*9 zTB76ywp_up_HfQ1w;bNX>t5)A=4?(ku|OocHM1|Qa`C`dSbV6tq&_gb5^a~^pCIC^ zV7&Q#dA%-HBmuUE)`nky(~?{mL|Qkj-j~c&Ue$K3wE4!u8_*|X8?*R6+$HAmk?yuw zEHB=j0ix?cM-n{e11hs6;MW~X`lyT?V;*8K(xW~-v^a45BFuH5>6XP!6kOWN-GSp4 zO-1yN46^wAgb}gs4D(7%_l&nXjvhBb<@?& z3cqgJ3J&?8L^KUlhamIemym7LjF!SXMN2H|gYuJP#XvR;aY>pt1V0ULAvI-R&-)9j z)%Lu)>+bIR{_&I2JaDQpf~$$@96zdT>5e8zr-E70?n@*CtF0!6{y2ka+(4GC#rtnnNpBX6|U|W{sZm?=?N_cp>5TH&9UB8>lWYTmRs{Tf5j7Xg7CL4 z_F^R>td0e-dqCTF^VH=eX3?N=OhwTl`QD7c^*oK~l{S0~-l#OqCgvzKj^Z8@C@KEu z0ZJ4>12B=i8qN}1_;D!tdTyJtEigq%Ie+12-MhK69>+6e=qd9-9+e^n*!ezBLOX;X z@l4g^k`G8Oj78a%bz4?bUrocjAOGIx-Cw}HbS|bIkC(0oHV7auLlb*;l7dLXi&7yx zB8P@O5vm{6@-eRr4Az&l&MkmZ5Im?F2<@174t$Lw(#N4Frn%Wi$>{8~Sh^Y&yOw{3^qyQ%MM)QELm zGY&H{p3zBDq=9G7u{Pa0$yF7M?z32+gD7uAtD>3>r@8>MJueWob@8FnRp1rKMv_d} z(6vZ3WaIV-@t*c{oy4cC@iC21 z;nbkY35-$5nuJq>j9+oSCksrEOmO0bTcX6Kbm~rA6$&}AS zJ4W48cP7|JzmPMZtwU9%-(sZ97j7CR)>vR%1kxez?6fs3wgCIS#bboTf32 z$WCGkGQkPJ*@V5PaUKT}wDhlYLJNoPi_mzUF#TuD2Y-s(MR*_sMyfjk5%|Qx+N+8d zC}zEyGmj&^dbs-`7>OUB4z0I{cSIs_wA zjY!bLtC5Dg)zq%*uAPooWge@xIsf7Bf65oX{GQ#(Niz?tdZ>#;Dt(^v2-cNaY9LW$ z5PKJL7R3)3vltlOa9V{x88|OM_feHihgu5&SGOvg6-=Q~N^y88wFqCZAvT>^Q52hS z_|Jx@%<7J84VpYpEkiuI-`z!Mh*rCgj%rD^G!{zr&`sfEL$KdbPo=Xc3^GOh&^r- z674xYHA4wd;82&P>qaJvLGIS55n}?>Jn(+OT&Ssw4oE63PT?v8O%l^_a4OEJs*Ck{ z)lF&Mm!~(%mwwu9|KmrVd*M=lZC4cgUEZCu>;wgvS}Z0{L6=8j7sHQzc#ARO)|J%) zF>#?{VWe=Fec7jvdP_TYU^|r#X!Y{tM~42xe38$vj{t z+thnpPgN55aA*ss0#^}!`5t+*F-H+An-1$x{eur3Cvhkf`OVu67|q<{g|QJ>i|aj= ze_`=#ACtvqd%+Wyc3;g}oNuP6E&>RS#HIIeHWJ2@p}&9w5n*u_Dj`|bO`(sT;>jQa zE1V*1s5ljglQ;5I^$3@XnI!+kT$B%3AOy+(YHtsIyiQ^aYexQbp&QoQ=n?}<)NYQv zh(bh1g{MaF^hYo@t!NJO!$~2wDV_9J?5XJWYL1I#XxdX4)W|}SR_u%T9l~NhUyw(P zWZ~^G)ZK}j;lJSOk_t3-1TmKqbHrjKzbfr2>bL!i0yL1HP4#ETV^O}fTLE5lYMSPr{`*Z2%(?uj4=0y{&y-s zP2iLaRu~x)lZ<|{n&7W2Ryox4IoDHe7>NL5Fbpl^e*Ep9^C=hhW6>0;YpZV4f{tDw_@JTJ0mc-v z9)pSowHIa3Ty8waaT@cYS34HKi>7Vtrj1cc4#930^O-4)2!AG8norKh*Z=(|Kjm@F zuCLl@gs-t_4(69QHjITAI3r5Ma3Y2TK{8FJ7ogPLWKYC70<|I4BLI)g@otNzwJT`V zl&f{US(R0hce~SXdevj^xwqTz^1M5r)7ZeJGu(`gJM$cq2#5?L=Fd@#$D|t0!URw_ z9~N|P(FM$R1R^CBxA!m2+?e)O)@<9o+AL}@t&DD&k-%Yl4a_mfZLYxKhcjyZm`7AE z`GiOH=co0wQ$6BoiH+iQ2?_G^$cTh3j?q2T5>(AU#Rr+HBGtvX+s;pZ!tsYcd$T>8 zieZFCfb(SXI&Ca$2WZKWIACE{0(dA!^o|QPNN$v$LoI1Hcye*9NZgN`PmSfGM3WmI z&vnhg0@#$YhKMs-3>+YJg!A%GkZ%G9dt#ypKAS4hZqF=v9G_`BZr|7B>s@(%T%~DOp5K^X|H?=GpWpfD^YI4a?54gc zhRsn|u3-3Dw;UJOh&e=eEoTkDqKMHYqAm4ZaNKSN;>F|$6#?}S-hd{Ehm{=xOU?b< zNAiB*G#mL2Xse-PHZ~k2MUob&@#oA`mP7QC_Zo#s1dAl>Xf~U}P)>6*&+R<)yBi<( z;a6V#vA6d9)Xb@Aa?>(S1xYRq6&VwTr9#HIsfFp#okT^DL2O0CG0Sd7S6IV*o>2^x zbyOK8F@G(gR#P*<1)FX@?s7St4|)88m)!H5r>@UWuT^4Ot`9T5&2_F-45XpbB zHudGeP(!6y=&<*+gf$scl!4X-L4B!Ay(|~IzTnUqjTef<@Gr%`dSyik%l4cXThpkf z&VUFgV3uuD=m*QHB5wqTAa-oi)E%*J{sSXPcsjHtG=Rjx0rRv?y@CR;Ss@z{4cw}( zS5@2ApsTex)hWT#9*+9xe{c-Q#vcJA6Wv?ORfYewWqnjPM@6wJ%2iRV+IG`6>q_6b zS(ojq!pDZY2j2&f{i-awIXAq+>AQ-i9(_F#7_>?DBPBb`E7YOaoGFl?#XcN86Wt}4 zq-IV&i({XJ0dgxHldLN|753QH?GQ#z`vmS{(K5Uh87JjD7qw_#kU+yP#&WXJolfJ&_2tFimJB0`yGHfmt}Wi9ayjg$Y53egKo( zLJsNZ<|$S6ys2|L4d>@+)t&$F_dWI#Kkn%K#`%1{pSQpS&EO{eiSb!vHqu}P#nTco zD%mBVEx@r{r4Xw+Fpm!ll@wf)UF>-|~P59epqi(YuwPyCyw70rI1$_uNxZSypz)uui=s+x{o$CB-$VxjJg zY9ZolavBbeIH!Vu21s909mQis7_7vU)?(0P*S9MlEjfoxXXBNktEvuYBtvY(Q_+RX zb>33IFA5ShSlEV&?a)rvZDt;nP2n_^(cGZR^ibK@!er3QH}A30f(yk-O2(Fcg=%*RTRT<0Ku?I6lzT;0tmmDWjN<#M=+I~gDG8KA{q}))V2#I3cmaQ--yx-b1!GvEO53L zxMJ?it8sZ2Yyq8~;gVo--coMJjy=ehH$|Vy8ssqH=c5ic%Ef3?4L@U$7AldEmLNPV znwn5UXv3@iv_bRY8Rc?H_O5!Q0bxXDh!>946IM_xFo^enngH7Em1F6z03aT702fqwkBnashl1VcI$sTf;t@wpWC zj@Ko

6=GO-z}a5$&nBsF98RjVWf<5st#M-Bisw7j4;GsJbgveWhxyR_&FtyE508 z%J%ZyUYV*(Q+=^$E>6wy++3dPS(T3Q@zUdDisZD`ElCsiv;5| zXLw78$ps-rOgv_lSCn_+@eWNIo2lNPj^FfEkG*`QsOHT)Y|9#G2E~32)r8W}dh+4P zzOt%hectjiXllk95`tqdY7!HJFBh+7I;T1(PXV<$51TyBIn_=6SKs!mvfgDRy!7a= zT1H;;*p;uqAzz0~LO0KZ;b`on$+-vdbn-$2Vd#wi=e}6XH8pB2*`(F9>gKi>cl-1q zAF%n{PrG+_x`%ocG)|G3K_5^!Ou%d6x(QL_U99y)SkwBpBG!PQPo+{KJOu;A@YV}^ zqd;E);YrNs%_6FYRu_BV7=1Gx50E^ILVnz1Di9qwy!=IXT)x`n{=A+?rmxs@#8&vK zXd|!L6$C*C$5ya)w*pPwJH8g;j$+K?Fn;OhJ*JrZGUcwr?%+MQkV2_-5yOIK5r(VG zQ_-9=7zQYt7-!(3T!5qe%&d@hmFK)6DG3x06fPc7U@Fa7pS1%1s-kKYy2mmaG#Kz^ ziVCZiYm@#*Wu4%cj)Di&9f<{PyM&`}eoQ!^MzJuGcU9ggbuZdmcZ`*8$C?ZCMR4JjMG?2)tFW3Psrr zPoqDiob;F`$J{*w*me=Jae}WIk@aG@XBl#McL!!|YC{N4&5`sRP`p8oqrwt63NK%$ z{0Zh2u=j-*rYA+3--tWOD{SnGydC$~{_$5m<@Vcv?sQFVLG~i_OY;l*s*2QL;EAJq zaSP}r=`uu&&_#90K^N!t#@8JJPSBF}W~el9MwgpSUFGdO7Y{s8z4qnz@6H~o=KX4g z@L3rP9maj>G5iy(U_n4+;9YsXv{)p1cD zO=XAsv~1G6%Ec;IZLU^h+2pdtBdY2=H)*a?Q71f{X3X_Cw|QQr)J~IAgk&nM!6q`P za2k{MBr{^28J>jr=7@ogIR!Kea@}U5ecg_VN|9ii7J$nb5N()~AB-Tv!xf+;3nfmO zJP(xbEZ8dCx4;@C+GbC|^Oy`zpBvJ@>06r%AS(yvZ}2HkA#q}*V--@S9+I*YE0Iwf zIB#6ubsRMMLL@M~S~p#ln_|GkW#0aWfA-W5f9}Q8htJnl?y4jTk9_g@tSB$B%wHCR zNT$JmWXZ*r8Kj2JW;n1@NI0a^+)NdgYd;lfZu$aF*Quz+c^dMN=NYuqmcr4LFt?Y* zfxR>&9h&H%iM>4~Tq8I@nr13XB#-4(*JamE)&54cyK#O}e8}@||Bv7I0YlymL%lA? zvK}{^2EbQ_`#GNjTQ|tw$Xjrgw8-yq$nk>|omV}M`(zsz*!GBRt*aT?9FQG}c|hw? z9NPop7?^1Zd&eL{DrEpg?RkK1nM_^uX*3zG-Awx7~~~s z$3jo3#RC-~O)5Xv?+y;OkAmF~guZGm(#(P>6w><# z=TY^qDe7(l!$oglq`SqB`LSsUOEMXKi6Cnd*T5I5CtHrE7R^fnc25fZq3IXyIQbwT zOQ%so(DB0;RX=&rI;cc89KR6vjfyRO=RqG~Qwd}mDVW{sB%nm>YmOAW(G|Qv2Q2ly zQI*@3BaTyj@-P5rP7S}0Y9ISbhy`gbf-RajhH((2WA5YYaUz(~3H?drD)Z&pNkm~z z2X=K(X~HmBe@iTQsWJn$P&MjuFsxSTyhhB<;MO#wC?K}V{za~dWTKjHj+wh2BkLiT zi7Z(pQjsRzGM7*bC>zFQrR5&_Y!&CR9C!X7TZ#Ow_Z0##z65+;CYzwy(QPTMZ=8lW zlsTLCmRq>Mc>Z2m4m2lhgcs=~8$Au3qI^Isukmr%rxVwMlS%bKvLxe?si{^N$wV2B z(zFe*(eMWn9{JYf&}xr5;)1kQ(qEGRh#QHwpve&j4wSnKl-jt$wUX_6qs;RlM_^vR zuDW?DnzCBA4fqHgYO`eJ2%}-&I>CX3pOOYLc$tkIW3^XX4Xew!SWg*x{23SMewy~k zpWqD)PB|_!!VNL9)5MM!HcAf(^Q&@d=VHGv?|J0rGe7ClkNn@eOR>Q~

h{gX;+fw8)f#Jdp$!1&34R{X$ih~eIpdrJ>@Qg4$sHQyT@)38< zpZzJ19QS>l_6;&QrxCMX`i?O=!J(ich2eDJgW_DBJ2b#ey5MUGR8XasX&jom?a#~S zf6(QRc+TcG{&2i_8Mg1J@fe&6KXXd;smIqT5gN5Vt<_B(2QsMv}GTeGPNG0izHVZ75VlKN@_Rnkk7h}&!5yG*6qeb*B2>`3B zmzNE==u?qK`5aCVOJf^QlR=3-dv$543FFevN(Lk?oWpqu`oQA32sP6*o>pn7=38!D zZ$9P2Zu?K)RetVQzva^Awl?Qgw?c`!Q?#RBqG-W5U8<@Y=~(EzApGQp-W0gL$i8*= z63~{56j8Ee66ZG^!dbQ&H=%4;%uI@fJ~J{f3pNKaS&H^bmm6~fqsoCo-ms(5KW?BY zgQQohgqyhg`V2|qq?m6+z zAd(6Oy5q*QED~FK9E_~>t?fi*-B#szKBhjm{Wreq$(J`LXV=b~DbWp!a9#v;q5%(q z^};W645f|-9BF9YG}0F0K>Y@%>;i_k;Z&IkFcCTuu8IO0`7c18;LyLI=fYr|=Oy+e zN)+(-@?52PI=XmqHJ3%#;dx{rZVSc2pFPK1Zgk}&r*lfS>1w#Fp}Dz27S^KD&BHKJ zW${Vlx9g$=>M=Lz_yVXwb&dVSL%6BtboI(nx5{~ash*B7#Gk<%n5U_3z^%eaI+!0U zLnzXW0i0$y6k?9Wv|qK&*q@E#=qw|W0!+ybvsL#gri$}Vd2nDP+^trtW8A+@#~B?6 zMcnO9JGW$&SHDT$fmz#&3|pX`<|bF&TCBM34KPC2bO2d+ayz^OUnMh7tDis?nMRszsV##~wtoQ8O@M}N zS-=B375n|k4}8}XKl1rUr`L9Cpm+P3mLf2BC@3{mMu`9v9wI&i2twJem@jui_DosS z%}Bi#G_76RbzM<+=E>UvlM|B)&PN%T7PNR(ohyv%cSRm0XRVvs#j+j40J=a}WDb+u zVAO1m#oVsCX6SeGSf7on=YR0kANprcefgLDaXoFiZael(PG#FR)0A*8V9)WQmqRMonQ6**Oe)0yx%q*y9Z>m?Cyh5`XP0{J#y)}908bUXeMGlZs1>-@XNXYo zL`~K7K-kTy8r^Ab6HJ3~3Cd&%D#DU+#Ps=qFpw9J%LS_e_ug^z%m48?ANjI3yyrdbrFNi!c3mW3cWHEJI{9-}5=iB14`O8k3MZlo zltcaCb%je~8Ft1=%>o~5O4mfpZsVlk8eTZ?zF({~4slBu;b;kQxNG$v%bOT26JZKv zcAUK)-1=e1bbRs6USqZM0&7o5(F=>|Kb(wxi0>3&%Q_?FyAs6 z-S@m@@G45pc#rYEk3%~NEQZ%2_-o0S9}^~(p?mioY*;g_8T2C^xe#c;K{mGB=}Z5} z^Mw7o|AriUMeCr7U6oIKyWoCuhsGjTe`)O|GnwP;Dv{9wd!&V5 zs3Uxq6vicIf(R2&FQ>H7O_tsszHE$^>;Hg22y;{kv-mox`R5T}=IkOmiGjWb1>src zi)rEV$c{K@;E}o!Vi4bCi=V7k5NZb33y~t_m&wy8hCM{A1AGaWK=5i8|BmpPF>_fn zS$Q(>)D2{bO!f#Lk&wB0B0TDzTw#`%8r_cY4dw=TZ|AMV^51uvYK{Z+_CQtD$AVqTjE-?#rI^%fIo?H@$gU z_dB>l)-B+jl&TUQ(o`+a4dyJY?@+|hv<=*5)z@me_)iUyNY080Ad8#iJ=7=(52)$j z*TzpYmuV>H;e5M&{VVT&{L|X)`%cz%Jt4Xh(e6C`s{-lT@}W05A)Hl3OXr_03(RKc zwz4v)Dg#Qf6+}l6aBOv_nsxO2${HcRQTx;bWN{L-py_!IKtWEBRW-L*sX3+nD?aVE zt9KvouU#vrp4b+l5KMiSpd3-ir>bjB(zZXA_6~@-7%ZtD;YnhlX)#U1uAEkLE?)ch z9`(Oo`DfF1Rj=9#gVRi05~E<8nTmQ6L!YsH3be#ifl@=Drgmyb_Jm&f*G|9m!OpmL zk7ks*rbXV!7*P27r95V98_6KBbA64{6+4%rs~IW z`~LRA)zj1Vlb(O;zxet`|NU=!*VPLbi(-#YqA1#?oeD^=So`5zp>G-eMflQD-y`*q zJU?~-SQQw@!jeMHH6Wocx2W!c*poc^!Zj}_zTlWIP$E|+sSq5|PD+zexEnuH_C@k* z!kn=` z(Ha!8O3^G^CF@eixgc6xP4z4-b&<(4dYS@k>pai<)$#i6?*+db4-1Y(#eP4Qd3e)X z_9wfPrlBkAs;kBk_!7QrhjZLDFTfgh2nOghoRLU<#FrINC+^1Tfk)Q&-G;q@Lrfb$ zxQL(MrK8`<35&7>a?eor|_88byA?pbz769KN~|LfdRIsxsg> zJRmI&B&*%=asB&$I@NfjjZZKYFsg2pdqobV^ygm%hUBvb_Sx=mX za1}SyV)zgTI@YRiC`j%tk2v_%bA(I|h^k0<5JahX&XCL1LVsSAN6Y9A=l7IyS(R-Ce_fy$<5qbEd3C+UU%i{;*{pMzxV7f z{_5eseEZqk-@be3`ncPnrdhS+aaZ1RXZx5(96fN~(PJLbUAWZF(=?9FT(62e)^m@| zJPb&;VbmWgO?W(eD}>lz#uFNa!b_#=*3@XT3Z^Zv_&NmQ^&RthD9kU6@`xtvTg-8m1xh zesMCrEm^?%b-fbQo|x&gwpevd-)}d^S5CLn9e1`r^{=1#(VzRq{l4v{^J;a0#_1zP zLgkcF11lgPA2Kh%dBd1k>N;)I7?V<=`tHlZ1%3h3HQHk(#v!ZQG*-gV|GW3l!|-HC z7h7ZxSPAd`CFFI7z=l}-LG;&Ov>m;ADa}y>+=%|py>^(IM+B03W;X*d{3iF$BVzeJ z8Y=aT6a?B?O%ayo0oPEC<5S+oleR|$g0;MUn|Io(kbRwX$KrNcW*P;~Avq(wWcYV5 zIJ8b?xm*_LWueO-+&6rS6P}M_Om{-uWtRT)3w>5Dg#G0P)361VCTB+sVvqt~G6yM3 zCrl>Is|j5Pi&xSk!<9#O5?I(Ar5W1^5KD;=`rPFd>c0o|97;(46QgvabHSJh<%O>0 znAC;hgUA*iKofH!5jvDTkq;T1e8G$RR&XjK5Y8GLt!-u3E>!__;tM$@7&`Iw!o(ni za&wLENEhqK0Q9UfR2v$wh7o{x5m=Yf(@Buf5XQ>!8$Si`R3pQ;S)=KvXbK{LXEju zQ-W2N{^s4g|M$0k{NV5G*T^ujnCURnvcn3^gNxv!t{xT7aL(7fr- z#)h_1FcumUkz@^z$ZpUwU=jh^nxy+>gVy>~8tKZ++Ise$H=K#cfRu2e4^0hXa%@*@=l8FDor{C34^(v7&)Hxw&~^ zbt3{x#tudsK+QarxbRy7*S>2~lZTY%CqH)en$LfHI=hZPDra~ug4=8#FI(-fPBd>o z)e%D5&AD*P5C-SAL06iqkv;EdYGg)XhTt6A(Zlmtm+Tt& zLY8!T-|=W8*-}>xy)7IPNyJd;vKC}7c@si&xTdMkCoH791f<-eUV(EyrEb-{?H${{ z`|WQl(uxHV)bh)zfptuT9R6j8Pl0o1Ieh|yD6d>Td5k(eW^8Ld@8LO*&JK7jw^}rjS6L5#-a93x7)iE4lbWvVSpC^ zsfdK8mKTr&OMf|@&rp)k&@d9!9eG)Re{GE>{buOc;+zB=Yg`1b1o+g^y`+WmJ>}gv z-1ye7dh+l7(HnNVq6J>G$5PKPl? zcFClGD7o^=Qb z2v#u5cw2~XBCV4^0%aI7j#Q_E@7Gkc4~%iU3X>=;7x$8&ZBv~O$HNMjYy3od@^Vtxtpfz`{AXZaq(4O^qBL9Z0 zu#mtIfeR!bUENGoTh_#sW5$68kpgmE}edS7h*X{LVAGvDVbYQ0*eVSBW`e0r9j@TB7(`mU$FNfQ}OwDR;a5WZm z4mL51{Rls6eq-(g5hq2QXUFdN;h18Cz)*V*n7^7(eT9AB!XFFf>a_eIqey#JqHdcm zdjRbdfnZ;R==sBwM9AQ7_!7pG4gZ1g19Z3OD_9Lnm=gH>@bon(SQ^84qQz?4gJ1V= zq)d@55WvR-in=X&0aW?834($zg_!6ED_-9hcp=+%!ly-UxUR`3_UDH2SzF)5S(MN=xf=+3()5UP6=WSTz^OL=0>Vda;?jLN){ONxc#w zd}dFC3yLR83wv$RN@>(#;v{BK-?=K202{rRfbp}W7z@VqOTahUbi^{Y;$v^!I`~ULG zfBK3~d*`=&#Z#xY%f*Fyya95fs#8v|<8xr*kQ@N{Pe>YQk2D$aqrrn-UGJHK_)YzA1P4wS4YJ%vINrXhOt ztTd@27d;xPG&NuL#SeV;tNx@LJ7{@}I`x^Nz?vnaF1`s7qp~DaNQ{H?KuBIF^sF%X zH4(O_xwi0|aDUZ_t{NLIhM_m}l#PW1)gs}aOCrw-DF@ZQsHz*=bmQT5InBddOhA+f zA2C5$+g4%s^IT=bhzgs4*}katX<&uMt{)WRZod2W_4A&7=@UNu)(?K>T^BB=e!I)X zu9$W-{v4?e4|{ftPEq<1CZVVfmk{=MCcF%i(f)ef-FkAP_=ZVEUdYZj3P$kH|` z14NuKajAKd#591|vV)D_kqYper<2N3S-84~P$*ZPXK`O-NohR&xE*}!! zKW{$lFxed1yujy{t@=!PRbfV_7vF{S6`dF@G4!eL%IV^2b>a93&6yBWg_3er@I$jc z8&d{mB8PcXs6TWI>BTJ-lSg9YcrIxQ1i5ukiOGqN1<@w;I1W|QSPM`!Ip?-M!eGD1 zsme=vSC#cBR9~cOzaWj$ z;W}v8{}3l*xa8*S^x-nstt^P^Ra4hXq z<_|UAxnO{Up45)E-1gM-Q`+hDHmVRzhKg3fI&1ec+Lk4xY*LOzy z#ow}M-8ZepfJnIlN<;4|VTa*LAx9P8R=O}WJ>k}28N5)27vC|SMfgSHvEvStq9Km2 z2x-C<88?VyvKl(e&egmkfV$fiPkwy)ZD0AM?X^>!^1~hs1G{1>Ka$>x@;_rVDbYMo zxd`aBX#gE=YF0&k1mDjK>-WBU_kaD+AN|xXTzlI)hHCECU0c;hM;j=T5*4U`$ldv{ zD?(C6@!-3LpL@s2PyV+Xm#@D2W1fHUi~i32&wJJ_{kYFFQZ(z_BO$nK1u!gfHK_3b z0m-b53`Vl2il*nar(BuncEgz1rQUcQ{!C8u2n%A zcY_^04Xvm_DLKiBfLGD9O?kAcpZvH>ANS$6ecXrL@x;eoMKDQ!TI5|d@6vdV^xUce zyl%3XTt+f!r@VGJFmP{COikU4yBke?@$7o_f*0KO+AqB8`~TCmE7jDtW6`uDa$qp< zz+HxcT{RN%A*6-F3}uRLH$iQ}5$qa3T{=aO60Js`A6YXdv3NUDLl;e82=Apbi>D{4(x6Xx!`p{kQs7+u^IjTKI{f{P$Nnv=pAJ!EIBq z$l3=T8VB#e8n_7{S>OZRZA*z6c@x#&9!m$kU?CQpixtiG@)+%uB8r#@?W|PsKTBSO ze!lL*&~|8%8z<0AT@N#wVLvVZz8;8!2;CY-$H+&-0egJZjoU)asC0RX%8imjf-XA( zvZ+Hd6Fry0?ZXx-LFM$&!L7I_6+{Ky^P3YQzBN~o>CFq2?RV&ir_hWX^mrU4StsL% zUUF8rKr#zp&9YCRyV=+tR|Js~=)5dUf_&mDYWXx&XWJ*mq+-vgS)Rs=6d6GY&SnNI zAC&{g%nDKI4}zk`gt~(K7%-rgTw{ql38xmmejXJI7%xwC$*4`I*1bUP4K86*2VC1) zu^HP;HZf|(d5Bo)0Zpztw0IYGd|C2b^qiHujw#r#s>{N~UC_Zo z%9IwzW)Y^$x*@iD!$J`SDVS3a_;#wRDxpPDoGx`pL{c zxBu>c`sdHj-Nkw8t8rVkoSNGw$lh_Zfv~~|^;pU<+bVOJ`(o}M_vlqlHyUOKCY$w9 zc);gs%@?hsi;M_vcBWHeJeeREp7Df`Xq6z1v9$`pt|1J|cdQ6kiDPL>UBjv%&*|)J zciUIL<~hIgn?L`*-#T5sr5vVe+yg3T+8TjQoWTbFief(oYp7etPe+P}xl|^W<0{t$ zH6uNy1O{K^B7tFu)Qd8Wr|12vUV6u~pLKlt(0kVi5-+Bq$1GWx5W!%z9B4?j4q?>E z6G{{$!I{KcWN71a+&0}FqLNuyYamF=;z<|oTsmU|Ihl1cQqqcbiMil*mb-)5UTG>Th()nTtxi#-2U47Z7KI#b%+&!FJpT_elpN{)8Wd`ywE6O{UEd~_6%!DQJAkI_95E92z+D}NR z`B(qwgFgJFzdq*Mx^9}=I_=m`BFaIO8=vbIXM!#hJWio}RzTf6#}<1)z>K5b#rq5XyiMaRPGouJJ_;3;dGRfVu73_-$qU!?LghCkUM&C6ACSn&V1sBETD0~?zd;B zpZN)Q|I{zM=huFFyI$|Rc3m`69@xM)@K|EjD`qIPW8o_SQ$|n+b%uJb^2+1%hR2Pr zTNf{U9=U;ie;W5^Lp6Wm$6ooA=ih$z(7WrY*I=6`csWWAyYc*7gbQ*> zBxhYjpq{%NPG7bRauI?cs?ZtBg&x@yHxfL}x&jyUTsnAX__v0HD}9a%X!afzo@9qO?NG@$dUv$WaIEDQoMzC(im?hHOahv4O4Kg=8VDsZ=go})I!E**@Uac zwtiYHf*qiMVEqqem`TM7v#bH9=CWu>ZEtOEAOXg00DWv(e<<~nhmm8;{aTCF$DgYQq@_8q_VQ@?V)-&L26 zHdiie6s?J9i>d?^+vO!cYIwVf(cumtKn4pF3ct`O0ify=x<_@QQo^n@}+im~*f877(8{hw(|L0qt z`;3b(ebN1&`Z14gSHm!#KsT4pu>gQE6$vL14=z}-dQZ!kMz5Y8vZ?L568;;__Qv=v zU-PtI{_X$uw!bPj^@traH*L#U7uu#CtOyM#;J%R;amZ0vAv3m?%pRLb5o94c=#C)h z-)e=*o8ea7TE;LI!vYaT7ecy4F*t&P1hn`yF0PFS`O{5(xFRsan~2b&KFkPM;~n;hgm*NJWiF>2-7PgDZ%hOxEV#m1av1PDjKYc zYh%5?AyjFz)kAuu=N`yX1J2}bf;fbk8&)>!M(0Ve*9rS9S6qOe-U)&5%FrSx4~I&P z1TTR_p$_n6Zg-pbuI4pRX&%<#EIQ@jW^XZ%ZfzCFTR`Z7%X+f{U5@&6w5OKlv0;WB zNKjxd5x)?@s0(LdQRygfQVco8eR%yWyj9x--&EYGjtqvHMI7<{t=Y4e0z-Sb1ij(K z8umfsPsTnlP9Io;O=b1GxKol45O}eTN=VItxLM=6L(+wvE`-;*Z1nFtPL4g0jy^qW zWyjgR+#jOGuNLC?t~2Rp$&_(O(6Tmc)Eg`qH;m>6sfbXh_#$gMD1f|ffR8Yk+CDKB zaU4v6^_YU$vqZNpS|$TuVeX+~7<4`z?dGAF!38Kj9988jsc$3wxngomvDfl)HgwGT z1%kQ_Y&Fti|s>Cb;1}xFpKO&xtVQJ_k>($YwIXX)7c-!UX z*WOfr-w*!T=4ex{E*D+LK1%~NBT$ZK2_A`BJWfd_Btj4A&O1742^etIC;X3gTcpj0 zpP#KmDL3V!07dHnr*fQ5jMKDJ-SY}Kpl`X98V)?Q<&}zGbOq_O=y!Fs`p$pwjCp=| z*o_G6Xe`)bI3K`(wqb}tGh>+5($W)91H;+m$R&9K1ETO)GlrjtcVc=|w`q$8p%$AC z1CB8j_djy_2d{Z*zr7B$121=UQgR6GOjl+c8Frk)(+!48(8B;QRUrXxN9QGLJ}FvM zdMeKxHlGG~eIOHZ^Z9Lpj|oV0?UUI$$NcawWUe9d>QNMp`RvB_<)3`(UH4o_!@iu( zYqZ$J>E4McYw?pz$~f_{}feyV$n=4@Omq=V^Es%^nJeba`nw$_Q2`c!zIR7 zXULp~AdCE_8FbM_SQ(UWQGaYNWYExy_hwd7G#B`gG$*leC?>B~bJ!?59DX^}$FN?u z6e4Lk*$JhzGLNYr(7kE?6me~r&#ak!ZCRhkmo-uaEpMLG3(ccWd^x7;;-UFzO{5axUuIR1B#c%|MlLo{ zlwFQ|j!3a#Jz#WR4>d|#44iFIYd=}6r>092B~mTcHl;lz$>7H#F-T1ZH$yF*Ly3bG zuLlGzoS+TXC@&|N?C^~!yC6*&sL@Iyxg77)wi=HXkwxzC3~$b!x; zw(dg^w4n$2!m=3`drQ$6BkNnB4Mo{jb(f1KrW34s?F801WD z7h}+oCP4-S;!P3jSR+4sGI3CJ^Os4{kyWN{6rKU@SIALhNV7^Q zqL;n|BH~I!0Cf&p8gTBD9-iF`+sT${L`^iqwN@Ff95d;g%BEhK*)}WF8O7DbTHd!$ za7IP*mFb3vNyKdySPZ>|8%()q+Fw=Gr0l$LB95ufW8e3$eCZt@@Bx>HVQ%ITY6=lA zv48Yt=;0KM9|sE{f3$32ygC+jwJ%mvU9UFP5B%6$Kj^dm=a2pTc~@V!a`C8Mty0|$ zWdkUFuE$jMV=?9`r83VgqPONIPYA+b5KJ}I-P|3O7cSPvN5_{|SB{T={WtcX^m)Ja zPrm=p+SR4ag-c_7rQF;?Vj!lfGyYq;QbZD&uB6sZR#npoB|%kG<9NO+9{>3EtN!lY z*RJ{+#7{ZII zty^u{ZdI>VMT6+vYSk61Zf@GDTh-mVYP!1V>UPb4T{Y`<)pb?3s#cq7)ip=Q&GChH zbD_C#VRiXLk~Z>^_^j z2Ay%?n~UrVj?C2LJ=KZ3fBTQ0k{~fIa^Hh5#q+H}6fP2H=&CDgIGOLb$hKz98ecV_ z(U=C^LO}5WoKy>P6Tcy_12cSOC5!Efv}Vtc0v0kL=sSpGe|uHMeCg0{%Jg@M8+30F z_O=Sta812%f_YhohZtpUrhn2PL^vpgPQi~cdqDlBIz?ZKh2{uqjE%b}+(qfC3$UW| zhc34I&V<)(Eg{ytfAW$xCjV=(t(M2RI4x=JyO1yrHRRI6M>nE3y*%S!c|_5o$G=!K zAO1(J)1gtsCF-BM*gaA>r7@tmTjFX(Up>=TMW3eYV@v>4lc^#7+pe6feB2fZ6vO`@ zLs6I{UV`1O;^)Vw!5h_P8zu#*VJA$hGFaDxn0LXClW(ti2h99(e~qD!FlI(C3%jt= zMI2EYg;2UBkt2U!P!B^>qg5yWQm}4d6oT_hMC01~3Nh-->SkLfs2wNI!e#Ksq%y_+ z{V`|eH|Km_hw+ZLc<}Qe0Y`2uiW6`U%9#IA;GzW0q%IEKm#TRb0f{mjSX!N(V z4^i-_2&zzwP&|tr&zq4mwi5NWlNYV&o+gYimF$gkA9FK~769X$`4BvkpcI;1!L%9^ zW6X%5VLk(xW0?epN#z0t4!i)Okd@NFlQ1FBOdE=egzv{Ra*X8@KX^b6qyRHkR8%g^ zMr!gVOzPBxM#h3=f|XrPV@`~{MnQ~vPSqrTMuy!a>VT?jR-3ZScV6v&^k?7u(0i{n z-BD4lum$)7R2d&UUo=8?s?LO-mBEnHoR3y8dCX&i!Gya;t`+e6l`||+6`mV^u`IQ! z)@3X$Bqae-TIreEPnI>BF*;{e3%|rSV#+o5=bTp4^^}U|KI>7R`=VR6XXouSuA1Dg z%C>{l5jQ%gbi{3$wcwyW*&s2-mK-KEIyIhB;{AoBC{BBG1Fx-A7YSqKlyW}%uGfD+ zy&m%JtSQnw4pSO%?6;l^Q{l*cOP2wwCM=)g^`P@zSKkC%(O~sxOQ14vkSt$5O(-J8 zMh55XMKvD4i5je z{Q^1yY@h)F-FgE+(;=pvF=n`M>5u;3_y5eV4{v(&jb^i&sx=J574IVZn=npOyPrnv z*s93gxZR)cKIS9tddlOP{dQ`Kv2Et6$khZ@w(P86bwbVo8OY(cgm*<1rVc}PrGj>N))hY3T7ZkR(?;{110_LOjtr}7gWmA>=%{-o+>^}PwANirr zsP@}bjr*oa=y#?B6Aa!LOwqx}87qgQH|7{>sB<~h-~lW_!!H4S9aA@uA`Ncf6T5)o9f*us%c=(lLVbYMY~M$TSYH1m-5 z=TE#ZzxMO*J=>nQX{^$SILy|U72heHGtda*@|Ez0#vu62@gG5e1-deT4$KqA2~|(X zlE=QAyS8p%1TxR%_H|$U_xG*eq^d>V(Zrca(+@M)`MFxsd?4u@a` z2@kr}dCVmYbZImIL;wea6!R(+Ao8XzKYic zY=PxFQ`HUT$%qIPr5-U!L8{<}LvttBB|=ebZ}1NuTvOF8kF_dr|JuDE4=4Ey%X*0) z3BLPOmSdi^v;coF&I8~@o^fFf2~LN^J!u$U;ij9aDKnG4z(YeNS2xmO2+W?q21FT2 z=D2Qhw&r#cfRNo1Cv<(m<`f%F4wL$DCcH9ypsJ~viKf0SA>OBg4<(oYz*gW6AYrhB z7!mW6b2;L?B@zc&Ksk*ODuU<*JPRd3$udCx+g|#fEOF>2!X*%84ZHOx$bE0rh#=60G|@HSF4rWuG*-PP+0?a_rx z7rM*q&Ap~E!<|6qs|U{;3>LZ_O=%dWY3k}~ zU6rRN+b{p(M?c}w({5jub1%rsR76hy$dsWsI!i0MB(r7!=Ejg``_LL>vumB$m<;I+ zJQT++YsCr~9(9ZJ1a7`%Mqz+Jti%Fm9Lk}G$3z($&HSDVfHxVw7P{`FsuulVxc`hu_fwTEt$$Cs}3dBv=Y5w#lLBnDZ0 znZmr>D28v|H12ohJhs)?=3%#=pYj10UiPWC?Dj>KQeENWuF8ys-LN_WXHMHWT3C6h z0+;9BQ6`b2U<8SIxM=Ov;or!xkx>z$K2|sSo}LO{rqG*e?A%JpGmPWm;t&YDvalVL?c;);9;sm7Sajlf(|57r*Q~ljLu&$ZU`KL zV!^z1A8rd>z@2`e2@9J*KfwMAdVC=X4QMGOI@+sYup#r32uC=W7Wn8VrN__9;h%x} zMB>3Bi_|S1Dt=|w=;A-XWTse$!hrYF;(4n&d=cjyj5PG^Wz7&LP4It$yy_omFwPkm zHmM6A3%|~#W4`I@L#0JH%`dN0(?nhU*khHdvcb7-`QMK48>m8K(9*p)5li42%J; z_%5rR?5rA-rK&D-T3wpfF&AUb<+^K+%IoL#ANIR1hD<4-sG%avYYc_5{Xi1E*YwRrHlXvz+G&onH(FJuH#RWD$@mQEth{ zF|i^OGn@LevcJ9?>es*a1Mj)(tnX6;V}c=%L(?FcQBjAiQqV?|jfnyh6%W+iDA$&b zg_=ptz`a9xF{Zkn+B(m}_I$tp+!x>RAs=$v`N^)Fa@zuDhfA6~q9^#?$umQj3(5na z^_0Tn{li~zfg0kxTz*B2iT`-Q4;H9*A(|#7W<)PX9L8ifmxEUA^Ufyp!bvU$wE|h@ zoLAt0Os8k(FMZL~yYD`lG0@-E&`7fWg}Xa-zX$pfjljyHS*@n3Evoq^{@dHy@|GX} z?|)TP`+}8h8b<(pp6T!n;v#gaJ$sitkNYC+s(Sj;mp}64^mHDE+;8)456uxMJxJ$- z&^(I9tXVN|pWag3pMCulnY(cJ~d5l14|JdLC?f`x>! z6sm04r=qju{XUNPsJZOD2#MJ!V2db-hUiVpTylh{Pnc;H{l47q=Iwdz`)RwMw!^%i zyWFgNM!l*IEM~ zrx*!EG47!Jfnc05d6@vgbVcry-qx11x{M2i&CopiOycDG)zAOXTR-EYA8~g5-Cc{QJ|(9L3}zj*pfkieb*R~6%*#}i{AJ*yH8Wv% z(6NOy7ixrpBPe_paI|SJvW2JPf6NCt(xbnCsdP49)6$NxYV*<1iF=L(*(Eu1#0I1a z^J-A~pr22aJj+DRPNn$k#6cByM^*t<0E9F64|V~YB?V<#3^L8-i1;1Gf|A!+;l(Jj zmL?dDM(kpR-~&sv4oC&A9l+}nHDY>1hkM>#tsQR=<*7L*eR6yU6K0m&#pR-lp77rZ zJ4BgoX(EzT{X$8eut+oz5+pED+a%f!Fd&G$rU~QmF)372V?rt01rC@ZDN7}?v;adu zyuUbOU@cBApczC9u~SYz!Ot>mMKOv8n#vce+eR8%m;;mcA+|qWuig}!q?))TK?j=+ ziIz)C-+yeqX(srw3@y}*crrCyTTu$g^HBmy_J``Gluw_E zy53LC(b49uZ+rOTzv#Dr;Ozv`IqPHC>I{#(E9u|qm9$D&9>RTq$*)=&}Z_)>2sXj#)P1V#Zo4f|?$G2)ZT z2Unr@9>H_hlKz7aZk(r-@F1WE!AFPi3JIgQ*{B!BZ5U#5F?Y1cXJrjp;M9jsCH`SOs*;qRZfrOxC`)sq& zb(vs!8)2sBDrw%H8Wn?J$o!SRcT|p3SL}V0l zLh`BCWboXCecq&C(DTt?Sg|r85vD7rKiAL%FjYLj8jhIgZbT2fu&w0phxfIgk8lkI z;_?&X7{bALq$Fr{-=q}PC|L*}-beNn9!Uw{c3VyAtSF8uwOUm*^b%SoB1^#krt0!%d z2DxF?crxvFmo8oY#;<(Z`R+ztm0er59We@_!!#eEa1}4QVyq+5vS2TU%F^j&3o3vn z36>37+zr{sd3!z%#XWb;U-zZY=udBydE1bTj9x)@o0!LeqY22ReU-AieJ^nFmpWrP%&q!3|>_Qc;?Ih=lQ~JYX zf<-m_Oi=r=uMJF!br4xN;#cxuamTFO5>pO&W;?RMcek4~s`a>3$lHgJB#F`>#0Ydv zwB+PR2ntyu(E{?>QQ#nb!cpC!Yl0^pSxD?LJjSl7W`fIdS2gRhUFWi$o1;`8H>;z& z@3{BB{`c{-zxV3o704eMHvL07eYKv{Z zA3yNv7hm*I?S9{{tEp)VFo0q;G09F;Z9=RyCY%L1{+jp%_Djgt23zWOBpwUb`^93* zVUxI74RpI@wzn>wiKrqClpFuT@1dXznmULaL>ybjc19(nLg((6S2-FE{(wB^lv?Vc z^RTb#{dd0ZnQa3X&sCF;j+?FnI74SvV2k1l&Qn6wfZst!Nm72QWbxrc8movhaQ*{B z?y9THX*lb;=J?X^O|N|Bc=jMn)S3)aey$ppu+{~s9Hg(FT*NtT)Shtml#AGq)ZWaJ zBTvK=N}oj3cxXh*zD`6+-ZFywgGyRZWDRke<#gqst(qD+NT)3MOC{ds%YWBcA zsr^fQv7W$-px^#fj1zi1jG*blD!DPJ6A5DQ1T-8t2D*vF8&5|AYqw=avpjqm6*6H> z1+iHAtY$cjSJ7hWs-_O^I#mG~Rc9ywUO1K_Fg4x(_@MY);+&?#3{C^kDX=S+R-MsI zcIiLl`HJ~!_OhTm6KUOuaYX6#T7F%H6zs%Sg=WiiqZfbzQ3U`(6Nb&?rEL}AIq-?4 zc!bGeUDWm5;+hBn2&+rvk_gH1L8t)Y1RfG=OZ!a2K-~;lNo?sA5m__bAXs41+-ZuX zFf-oLn&B%4)@o^J$A9`~@A*5g`Mq~Nczork8LKK4UAMk);nL-H)xoTRBGxg@{V<*)sN|NaZ_IJ&jXMO!q- zX&h0=(IQ8~WTgv-EeYTWT4s&&xT}hJQ#IRN`SBlq<)c1ivmc0WS!c|?2vJpZd6sc8 zZ(B@T2w}#AXK8;uW)odqRtLP9VrYdTA1eoih9FREe_D6JL`Y0GQW5c_BZkT+yn0W) zF2R|y@kN=1FsO1>H>cwdFhv)vb56pZnt5cLOLq2&Q0d1czqwbnyM0F3b(BI44ac z+#b87H}{AQ8u`8^p{k2mtc=bCtneW$G ze=-9I)tCC6zz3Y!q56>IRfC=$V>_#Hu~krKXYgl{aL^H6)C1X$#bDa}fq*F@<<{;$|L+wa9HK&hxhr{=FDQ*t}d5Cg1NWc76KMhTlVeSqTL0XRJ(5bsh$aXtzdI9{rsl`zKkAu!U$So**$FO!^8- z&uqA0^EJZ|WV5O@q)C#zfGEc0_)35Y$FC$NsycNouSE)Zgdf2O3|V<(UvI)7 zBxEV_ffhG4)KBa#9=@K2Ui=3FCPaLRuZvoyGsMR)uPrU#ut8y|#;TXpOrA1M&0^OY z*q!1~B%2Z;fvt+HN>ylsPF>dXdB2-K{e_SJ*pFQI{aEE5^D-2A3WpUz2rEs^25J)( zDF7Er(6+&P$eJFJg-})q83p@fE^}S5I~7fu*Q>Vu zv7ddtdMZ1}50GOW{3ETR-X(5vHnCohO^-J&R`+kL3 zm2t`g$lncp=1{!43=NCEh3zHztEcwNjpN7*fQc#zT%iIRD_UEb427$MV&kA@X{;Cd zM*0BsiI7Im*(%$NDIv`quX#!=4#7aekpm|P_I&Ibp=QVYlPSC4ii1}Jdp{sJU~99e zkP8I~%M*meW#8v9O~qea>LRJAFknh9_^pkR0lc>q@i z$}1X%82PD}wHz@R!#4Ow^wD}~PE6C;-@X238Bni`iO zem2$<1s|5sY34`u%Q$Se&wfhx<)8PcVd$%&F99_0IYH5*aKb22;ZPF79MW&fI&J^FEv==1ncT?}R3O=*wD3C9F6SA4=z6>6@= z1JL5GkhHN>m9*8*SBpFhnf3Na@1&wd5l?soY;$==K;s55jKAP%%Y&QvB#lDYCDIE_z~-=kIgHhp!OCWtHZ%QKP%c-} zV!*_dJW6bU@6arf@hdo#Dsua1btfGJcN10tNlOe$2JQe#64_J^u_SPylT$^wAq>L? z;>(#6785cLvx2)wtKs-?$dl))C4VsFWD;_*5z3xBW1X8`!4@P`pU{%&qeG=gq8)VD zD6R$4jFg(p(5uUM5)5W~*)kjy7c&BNOsuhT927cvjJp0YPY}t&a*}jIA?%LWAUky2 zMP&v57YxQ*^y_-2G8L<9P#iQ?^)63iuFI;esyb(YDJ1`EHA+W? zX+Q8SQm(XX>3$+A1YRI+H+%>+c^X}_UiZV?r!rSZZPCo&mS6qV>lZG!L)A@X zH>KVp82}LQ!XoKZCnnRQ@QPvT+%{9!KsuL-^p&rCH2h)k!oUtv(q;j-z@Fieu!@Zs}G>0Sl9a_iYfncBoloy{4y9}ilfmpy6g-j)yQUj{5 ziMgv;6Rk}qKB`SoG>eRw2BhymRI}M!y1bso?n_?x`~T1XeBZ@8?wZ<*kmpb%>o!}P z%l-zo9?^hmu5(pSO_A!U8n@FIea^kBbsl%~+z(S8;ogM^5-t)-dFZLBk+4)xG9uTc z1s^HRxHPb3G>NPM1Pp~**5v1dtDf!qbkDiW^EM3Dy4ZL2p^Hhr*?$YQ+?`Xfvf|WQ zIOwXujK+9^>6lXgi|qFu4!GD#ERnkEqhlBAb|?I9Hibu2)d8;J9jpXGE>LdmP+$`G zwx0t_Reinv0o~(!vZK6m>k-W56%C9)uZDLK-Xx?}h>2;Di~FFSxLJJ*Est>|`bk>Y zHtf)66V@|Yh#m#W7sJqn`qTLKBK>K*3lVnD%{3>Hn;RVdP@TwJFdBvVX*tXJ(LA9?V`W8-I08iows*GUe=`zN`93^{uuc%X<~44YA>9R%K@!h`k+#T!W{-tl$V?4xD3KKO?%ARX z=)`iekJh3WlHsl=Qn+!cGna_yKo3+HL)`wBs_N1=A|(*ZlL#ZSOk4gCVN7p7InGYfKS z4#t;aN{$^m;{xc@+v30lWNu_mC%j=ws=5`!`Xr*@qX{^LzU4eWjm7A2Ld#3qY}LN| zeF7C342SFwCZeFMVXUUyWf#$shGhk?#uyFI`UURXY+FwePdcGyQOW?SQIT#X0XDv4 zM=(iNV!TCjUkNu=+%Zhe#*VVs;^LRcQxWr)BOP=OIK>S^FRE(_Volzwi&a;(C5+K7 ztj1UTohR)3RE$GaBwapaRxjnNz^w*%6-GdFF50>2ZoL1YpZm3av)<&kZQIR%`StN# z?>r-fvoV3zCp3MgKylhy%?N96 z!v0L+65-;U+i1%l)Mx^vEm)sz%Ln-n`M{Q5Nho0^8=L_6R%x>hT!&*H5jvbQV_k<# zEi!^2Q7BH;G(a#9TTc%&%LLUrb_jhUN)U8MHqf~k2~48gBeuwAUgzBGcXKMbv0h!d zc=4~^+J3>;{P9$;>dP0Vc1746D(sttY)*#=$tbv{BAw-7zbaFonkPT;mghaA-JcJ| z2m>>Ppr~4w^n}6@^KPV96=hnAKUOppjALN~tn_ge^iADAR#-v?Vk)4J(m>d#xgsG- z&L>>cz8NEKN2k6?E~<2;L$W=D}wiC+{nB zk6V-c77hHFdSRDXLdy$HgqNLfkb^IGn5%2dLTb8PUBnENr-r~wqU7ZaZF5i&ffq>I zt3j5!bMaf3Ssi&4A_8kO(lf~&L6zz4qH3I0BV6&Q5%}igW6`3M^&3A55f^Pt%P!gz zqS@UF;6EIIQ!<(*FARbR5*6Fpyr{@=V7nsL0Ha!DiD&TwJPGhVHPmJxB2EZh+m6HF zV#c=CwVlC+(742kPlC8)^z$p2SfZmyj8em8WP_;7SQ`$$Tna`g5nI{Vz2x!oh zAql}Nm#e&@3Pq_$Tdm6)Pl!uwp|RrWa6OAwz_+GgEr;I<$ub7bZ>l^@p6{C8kgOLn zUV4GSbyrh^Tvby;@WNs4bkxOhYV&)t(rO^g^nbPj1+Fo?+Q~}8?y$3mcxv9QA-D5{ zEcnp;N{LZ9no!z{o~k2t6{R4#a8PxfLq|B3K>RqgMasMF*bg7|-1g~Dx;zbS(VtBF zz1XoMKpY-TFhMh5;s0y}>H6lD$MYT%J(R#hA$KzLi{hQzR zSN(dEip{2OTliP&NaTD;p!dO!5Whc7c|h>S*f&KUhwAyyx$w*Ezo zYNM78cP74)2SWfOYvlx#-J;jmn0c#{7huS%nUH~5pHc#n&D<51ejjf8ciga ziydJ%@mr&Bu$OLu`6LfF6fCaV%~h}qJoAFMEJ5~WYU{h*!P zP04`|nmJqS>u>7Z$@DX95q=P%9MR0q!99TyShOQTn;dja<+5^t@z_>Iiv^-+BEiT9 zZxJb$^mCOJY-E=sVqppgb54GlhqgESN*o&CAlV;e{l2nqdROjb2qi7dsD)=LX^aE_ zH<>2*>Dvl6z7Ziou{MIKCMy)q{V9bDoer>Pul0 zh=R4kAV%el_p@}{#?q8y?3*MER~Iyd0*l2tk6r!E4YEo-Rl@}Aa8PGT<|W)=x2YHA zDbs;iDom3)4a?H~WynVn^f zt(*8kVIWeG#lyB%~%gb6cxO)g0%mw8S|+5nnz*ir6I z#{KSrM_+yI7e8=%cB355yDGISY>fhW1!!eCjF-_3?xBWuf9|BDjHP`>4Y>*#S#`PU zs(KpJSZ+4EZ}_rj4%@S8Jnw1(2@;v4i0g35&_NbujZz$zQi!YeBut1)9RsfkMU-Mc zbcTlaSiow;i8($b3&oUf1ttY*e!zp-w@YTqnwx^{xzWv@^Z8l&q>s4uagVt;4rzr} z4GIJMVyf^ZKFW;+;|%TbT(|2@^RvJBu6JF#Sans#K&^iNjpLvD)$48B=jMpxBLdi# z%J3dKV9<&p$y_beoaRSP$Yy8fq}T%OwH=@#Y=DeMj`=%oYg4*irh$;wy=nf8v&>j2%#f$ zASl`?o1*K=I-fUnQLNK9zv{X5a6Rp})jYR0pouw{D^%s?il8NppiPmSY;683O`_u{ z5JnS;y_#O*Q04ha`kDieV!VHH72 z5LOWkc`KxbU@_A@9xehlwvnX{pNy@40&?%!D9u32{1Atw~-Bib8H zGnG;t13yWfJ)%?XK&wye9oiQoY;|+Q3Sts&#Su;2WZ`lmq2!?|O5`ieoNevN z>eI2pk=@=*b#rih@UkC$`|ICY-*9=ko2t#O?6-=0oMla_t8vhAU2~$wMTMz6n{z4@ z;djt?cqEu9Tv6182M9~G*Cqy@PSq@m<>B%$o!!^`lkfVQw5*DDM2^PL;Wj}VW6rRx zUG%7`mXDxIG!|M5%T2!qe%#SU*k1PYtAS2_t!if7TX9RZ->^Yz8jMeMP`XYUyOYsFghiDUA6Q{%>d9rvC_LGG zbQ#IJ(^jp+{~4&o>_517cL;0Am~ZU$pn_TE1c~Sg4KW59qVvG<5wy$~;Y~l!DQuuN zei$vf=Pj``UOfnRQg^;(Xh`Hssa8nS4qkpb2GDm*^(KKH53@~iij7#C)n3A)za&8E zTn=?EoH?*svtNVhTy8LDd(gOU!StHl8a;cBtBS2xG%foJ?EB4_)!8duMW+iZlaQ@9 zCAo}D2}=6R*McSt?G;y~Bw%xr5HE*XXq+Ik--pO5RzHdrwx7o9=jk88x(5V%r>{`4 zq0qO`lZ0+<_MtGbDMtE;L>8Aa*nXsJsQZwS7oif?$5u?+Qj{~LP&J1lNHx5u4Pwz_ z@`wFZ3HN)Eg1zX1BS3N`KdPJv#WFAk=XAQgaUqLLg9~bg39PCL#VHW53rhKCm0uS$~w?W4exp}Oyyf4U5l;{nIgLWGP%>} zBQz3ntkuu})q{M~`Tv=VV0DI#6S$oa7z+}qn8_*u%>%b-lbUS+ikhzoI|{o3N`V9s zTxUNiK#dn&I$EnR`8m0xYso2K7(qTYAY&%0)sTj~2P#48xR~{z;F!4c=NfkmQ5F<;KdIs#K$~X77qjj#6iNeqO!h zotvg*oEHa-`pz}tCAg>=b{)I8%N8FY@akF8)ytrA$3Fb<}@ zDI0zjWMkS(r>al=)!k7JZSsp+kz?*L}q! z*IkdiiE_x@4hu{JXVpQZSCSHKe;QN-X)&(Pf9^N#UM!awYqiUwZrWz~i@$Sra?gDL zY!Hx6*^7}El)^K?S#egfYH5mkv&~=sC7*EPl`&84vMm?OGPS5-NarHC4gb#mUjFUw z#Hi1hYIt=qc2f{BNoM3FS;UW}AraF)0ChG4k|Vq|;Avw+11Cf#(Hc>wT_^)a zOg?h@giKNpK5*cJ&4#{ZY*#D-FYy4fghj#A=c(I4qXR~*9Ar~Hjm2);PpO?&iyLpa z@akXP{?;F!99&G}@`ynLFrGI+Mac(;yCgBNJLlkG1fyr{>tg74#iu^~#*0V&_Iy{C zV``c1pcEFL{$5F{mq{&R=^z!BK;%GzdEW3jGd(5(GfkVYM-|LDg^!q|t%Lyb2m?PQrP5nra~QpMU654i6b_zaUh)x zIOltGVoJS_YKz61lFZ#PdZI^jz5TpMzramnW%w}Vk2`RN(%J|97q3~ zn+97rIlmB=%82%$GoS2vbi!-c;m1!WApn|aF2p7TvEA-@GWQ5vo^diV=yE8$C8R8? zSh7P)*f5Kgo#-g%+9^Y1MBE{PM+T6hsfrdNfub%D@RUl}Ft)_<>Io4T4a^|MCXH|= z7CN@istAfRqDYLflWGKdWmt(bW6Z&W+Rpja;c}(&lAAdcth_y5Cx{!Cuufq;!*;XV z3=erge#Vn8j6+-G-Pmn43}!rbFrTs8$ZMO`98+CjHx{6PDCRjm3d0?m(|fpNhAYPtjy_?}gKuS?IM1}bEsarT zJoQv6VQKm?!1*QK9L7>8Jck}c2@mpkjFb~>a%fJiJld&)w!>1?VHo>7*30FEqx7aX zZ+`42-+pkkC>9q(mf#8;dx#)dQyJCa3Kty8XR}m}7 z(~LDDliq)LVX89QV3aoWukqpP1+iiFJ72fl9^dYI>;U;rf*8FD{q8 zr)TiO-%AT&POG#sG)x-igkla?0{s>wuCW!%T1~QJSYR54q=yWlRGSxgQtY?-xe)QH z$Bl9qm0S=7Jk_=nv}w)Odqis(_SZDz;_XoYko}OACBW<(Q%~$)U^fhZc{!)gt-Oa6 z`@13IywJ$XOC>1&@)gFP@lwTMD?#pFU?gb9c3kpf;D|$0Rmm(BtOcz^+2~49Pb;#B zM<9--n1}Li3RqxUdM|pNuBZGm98oqqHq3sZsySy)3>#ry0J`_vjWB{tRii>?=;R4C zRC_DgdDUAaG`n2j4tq{4$*RDQ+0X)Ih#oNS1U5(W{gw0_RTRw_{3COSrk)`Zmds!> zEFH8fm2g)*ml*TiK%yZDLm|Hag46GuYz@#(X ztav6;)0oIKGf6orV%|BAd>PE3xHgra6`aJU=!-epCeIqP;xhT~LC!H3+sKn>+VkU5Hsg#|o?q-w8%@T_J7XyaKe+?g~aBtQ6W z3bEttSE3yCCQh)oe9B5|9`yKSIrEvOsDqTkCefyO`DDFEJu#CqK%PKRPKrM68~y$0 z3P4{-n#IaRR>G$W1fzN}HTA^{H-7sMeQd~OTGm6gpfHm5t=wMeGN^%{`g!f48e!yW z>V~1b<<`TeJSJ_o9f9gzH-U8n8wvf2>~dtMVsi-9H@a`LC>5JCZcG?x#KlykM)>{f zJP|_R(Ri>`ZE7Ybhd9W?Fvt}1S+y8xSA4!mfO0UCkAHF)!cjs;GZK(?MR(et-}5iO z{_&sifU1Wl#;z`>29EHGdPZjjCzJ}ejk65Cm>A~Bw3}L_C>MDes(LzTi=sQ*ZTnAr z%<3P0;e$6PAFqa8nITrf1xt0=lDz_FGCjGrSr+{2v75SH3ESK*+kME!FsNPaW~L`k zp*FT|k5f156ivOrqo=hf4c9eT=Cu>MOb0MmE?=Y^VRz$pkcAi=?~=etv;*8=K(EXg zqm@*g6TxR4lbJqE6*oJ2JX1oG3A&4#C|@y*C%JDY&X(D(%OS9-MkZ7E=yM#Ht0KuM zsPrNGLnBFSh#t8zj>b%C%^w`M3GIW$I#?^Jj!+--rq1I>^RH}d#kOC_DDr8QK4EXZ zSseq!m0-Hu{>e!O0ItnZUe&B7M0K*A%sgZxmJ%LwR`_dtVeErVvvaR?llQU;JSw`! zLf`b+kPU*z-a^^Eg_&fM;1<==l49-D$Y?}DGb~DwBngrWO=%MJ75KdLI`PklVUt0c4;Ut*@zZp+vGrP5GdO+JeTAuWWCVx`Y|m%u_OzbZypd{QzH=z$ zcvoadCcQX^2Qwi&;$+$O#61>6f*XzkQ3F^9FV>*a9&sV5A$$#3w2|Elzcuqc$N*;9 zXy+GxChT9QI8_=;}Z?UDd=?NfB@{!`iflxgPAWcY^V6T2e z4-oTLLxB<~r}RR>3F6u}heA$={wj)cjqf{=*Gfi|!alq-`1)e<7(?*g*fWTDSb90Z zB950s)TZlDl7Jz@VuRJCDJ9wgbkr*(!KBpyMwD0?yh{aKSp#M{0IPmXs%6*7o>q0a zj3fj0kyKh(11XYfJ?zP^T4EoGvgg9n70fRzQibe-@$txd6M@{`mssB%u6m?_6fs2l z0Z15n9IxPppu$MY77XILCOH-#1k(&eE`iV{<^}!|lTtD`aC*^rKNYD(?||6OuItvP z!+LvqUewjq|L2>Y&>_Qbllwk|!U4)+u;rjIIl04be=L#LUap$MOF#Roe^-pil+yHt z6Bj?sF|5{;iF3#vudI)3My}DcnZan>N5y}ssRDCy)|Luj)QrlxV?Km@N4b#uuE<@P z`*J9oanouNmQeh$#?OHU6bWL006U z$iuR!($p3GnA*+vz4Ym0J}ZU|yeAWfmMH&CoX}8RjNGJeqBq{o+48i%$rkY?0}1nn@mr@DZd;bIddbOv>*`mg`W zhj-m+?)wskUos%|G3iOHGGQ>Ep*bZqu1z%!KlKYAsoUeKs!)z}`QTuI1y(J7_BYSQ z{uEwZ^@50r4h2ms-0$LHtPy)&OjtVAkT>VU*L~$fZoHWBHbakOwW`7rgWDn%BnnO! zV+kWKSWod>g`K#1Jmv~=%2R7{=-gO7hkWYTHn4=(E-El^?|7(*lyZe+6in9(jDdB7 zET@O!0428$QU`vb9c4z1VSL;GB>>2m3u6iXU$V8S9OAY~Ru(2H2o%KJQ)gbi>&BvL zmdom6A1QzFH}6_pY>U<5lokpg((oWscO(v!xvBxgGWT`f;b7?V|Mk?%{k9{$8c@1v z5_}0hu0)49b@b$g6foH`$umQZmD6l|hHI)4+W4TAsVf8$=fov!vk;66G?Lu~NjvrY zXTa3>F?hTRNP~wf{9G9{M+Zbwvt0@~ri)64m_8NLFyKSwv6*(oux^**OTX#Ko0F5W z>&tEpHwSbw8FpiE?HMrg zR*XBgY?`mBz9AThy@*9>QC31v?Z6!APMSl?G&6!~tk|JHCIm27Q`4YHsfwaq)Gan`OAb?AEZY*L z#xydj89P}GbrQ{PC)6Z}ksf-(TRh0|RD;q>GbE307+S+Vb?<$mArcNs$if)dg^iN% z1%4Q;eR>R-?n51V7)p%rB@9CZ&Fd6IWB^~Xi1=k{Gy}sx(uA5NozGHH*r$&|F1(J%+%VG? zUSS=kJ|DMT{$FXOm9oUG9l6H}RWQ`300f)RnAjgh1x{*7HFfZ)GUSxhp6VVd%+{zX zxc00yH{R~U<07+Pc9gQG!d7G(S0Exs(+o4J)Q|Xm)$OTo-H+pC1Hvj^YLOt&>{I4s z0_~!QbE#-K-PXC?wJ(E`y*TEVGR^WF(ITa6*X<0m!o3-RUeO(95GVZNk=x-FX8oWC zWp)b^2|{BY;YuOU5C9$326*bl;N<-kd;`4z?%mr9#5XK7qyGl|2zlOXSD z4nBmsQUN@2mgT**)*wuSA=co~zsOoltZxam!VJR$TuD$=kV!Ari_D_<9ELXK2@(LL zElfLPE04P!p!?l!=sLLm?si4jO~WqlHeJ-(-By6$}2pRczk*S4o8#dcTp z_324Z!kWmjT4sLkY+wcADKf1bX zE1Vz;-t2a=Sa_DT~MIq7(duupc zsDvSc+qUD>Z_Dl3=IZ$37k=Us9$T(=W3fJ;w&#E%!FumGbWxYi{%Xq9C9~VLCUh)Q z$sF{)oQBiw?jQeyM?Ut^N89aLJ#8r`S3Rr$l1;hKFcW{k4L65e`5?29#eNeye7ydR zWksB_raF4oxO<@XasHVIY*r*%IV6?@<3GhsLTN?y0&_D-DVf>?AhRFyb3Xa#sZYMJ zKEJ1}r*^Txm?cDgYGviYY1R=vgNCwh4_0q@-3R{it!100T|d;)q2_*=Fjao@yH(9luQ1nz+zBua za`yv?;4}i$0)s>?#aQB6fQ2k@fGJAIDuEUE1m!T6Y~Qo>^X7#5+3xzhsWs7pp@fU~ z@zL=sUUd&FB$rju9ALT^xs9B8itEZ%f-rMTnz<$AX@u8$za5|a_{)oi#ew6y9K~n< zNK$V+R#8nF8rjec8Wy(YT(pI(hor5GDpt*+A!?6&oXI0!>zR(NLnfjM%-ax<>=Q>t zmG+G}Med94WOs7!r#-Dx8Hr@IRKo*1(guvM{ zie7+5gcu3*RHekAHC8ZBLqVn;_62PQ{hP5@^6a26mNZ z&-R5DYU!t6yII7Rt%6k>MnihSSDRVwXC7Q$h- z#G@NSj!>Kv(T9owi0z^x4WyVxxbVR>ZtQv}-Pzxx@f!LnkJT_vU0?Kl(e>ayjYBo$ zD)&`C6g{Zt_`lsy=5Fe@6Kz)u{^2zA

%%x|VJy!#cXQs=8;FiuS-@GCAEcTvuUD zxhjkUMi~Cl9Z>5^v0zfex&ha8QpLYo4Ci+T!%a!PyiuH|@>$RpvS~1M#2`D16aVWYD>KM(rga5!mlOf(va}ETV%wqD?!|G-yd4&~^-1x)` za@4T_SmD%DQS3HrDsSL1gT&z7dhB-N&@sZaEAp-wwq@T{xhwl^+4l*0F#h4NExT9k(EG|wAV3jm_ka|v1 zI~Ae$D>{ATngOw_dnwI8Lnj#yD``4_;Km&vG{5xPlfV1B?Ko|wdIb-lo&yz;e7Toe z%@!@GfG*DX``o9eJ?Y{N7imf@k1bA2alVHzMr=_R!shui=u0RYA2|C0kd7Bi6Noz3 zx5d4T8a1THCX@z~nf~Pr;H7yES2yjpN9Zh|F~sHK^NL>q?nWmF1^9COO{)|;3qz$y zss+|VS=Mc{Sd_o~+gI=SyL*e}(O4`wjW;+hYcv3XWcP4oiAqPy(mYi|(VcCc`lRF4 zQR}cXdL!#pSIMp64Q`$wZE+$w;83KnGxk`mX|Gh31*Ei&2tlGPCg!tQjDP43&I2oU z5HswpNz@KZ*OD%^~>=J)LZ> zfNm4`iyqvNpq9$Hp?94QYRXo$HwT^)e0g~-%r=L5maW|MkU$e058(H-5it%zV=@!@ zb^Yg2TYTSu2KE)nb$oYwfBE9h*TLrQ+J5L{jD?^y38J~WI@a~tY9O; zQ4vTxO2?FlQOe5b3VplP8ON|)qDnVH7VucLVJ-nHb~Rc;2E?6YcjR~@sQ?sz=-GvZ zJ_aKqPe}JKSO?C(k$N!94t=M&c2o_9{U2G%0dm0NTZJ7xBF!TcVk{&{=8Dh8ZNQ=(Q|KEciDP9kUw{K9P(g$u-!vYcFcL97Sd0-tgH0| z$>E72UhO(6>>_2tr8t0U;}D8n_qGtBrV^5&yq9S&&J!}cTxP5Dltm^LHsCSv8m&l2r%YsTgOZ7Bas_tB9+8HprL*Ub$0)<;jvI9QCElijlvqg-4*; z@Gt^mvtFO=9{ZJOq|n7Y2}#p4R@7MG{PdI&!hRjwCJTmSSge5kB1 z6jeP;RRdBD#xQNuPI+78^gn;)>a(7HVM>Q()s$23CyD1V81vXkXwFjB=yt||MBZJ$ zu3!As4|&yV{(9ZDO@e5IDP=j~T`+t>o9u?91o;(Q6)1-VtKyO*wi3LIOy$INVI~9VO)WS>8{og>Lg{1|D@&E$;44xs%X#Dc7_YR zCgPH*LCk_=)baKQE^ofEy8Au`>@}EN(n!;;figOkj8roYFrTBqAzWacgrl1Mo^h^G zTqUfTA-*ziGQ)Ia{s>?_F+4Gn)c{&RrN8KgL=+kwxRBE_rdubMpxyw+E>MPvwosifB5=e+wPXB*!H9iTa1dLoP9b?YIp%n z@n}H4z-_?N*`9Ype)z-MZ}_rDu1`NacGvKGe2B;f#-*dh2^0r-UF>yubzPV6L#LIJ za3+%>!&`*Cr^i&>yfo0p24b6H+yV{K?TduFBgzXgap}aE_N=)9K38BzASNpq_~i+cB9W9QA!z4d z4)N=An1q#r5pmsgg?p~svKL!Zob8iAG1bWvM|UxRqJ&( zj;ppgfTa-6KY4$W?iLcb0MT6@3wLvR3%egRAyT)A^eb0tbdPA~hao@V@rO6uaCCmw z)x{39nsLI}YF(~~kak2wH7jh8Bek(yEEdPV_B(I>z=zvQ7t?M;2vOa%7H!punX0te zq@F{B@_7{P_B0qw+9+}5rOOc-q}u`n7`qdDZ8J$3Og=UVh)}MpdO2RZxBiviy6?qb zcfY>N?dovYT&v*=F0T)zgSppZ*9(dz?ji2PFpb4+_dj~b?d_Z1UM1Q+w4jI40vvw4 z_1I@*x5re{qcs)^R?SDVrBz58fTc0mL{-0CnNO4`!p6~y+~pvRAp)pntSdVe(#U&`kF7hF)uC@o4aQ70n~}y zTR7U`r(t19=m*xIW!ZH7^uYT!H(xG3e$UVx>innJM6OyI(yP!7Uu&nxC^E?N0O2s< z_~=@m!5>cARqu)7Of2ib7eY%#)Y#2LkWvC&;$;hZ@ZL?ueUQP0=%{6IIFskmiHHsC zekz4o68E}!BJ2DC2zkPG(|t70KEGIb&zli+NJ|Fd2Ug+FWUa1!uttHR5}Ycpel{@{2?cipDDDZZIf4&NYJb%zJ z8bxtH6v5w1*Ub(iA!brx8^Q50)$;6rug|>h&v~n{kc3~%58E7U>O#uS5~`@os}6x? z2+#TZya?o#LZlr+A&WHj6AzCCg(h&n@$jAyAww2CAm+1%jtHHj-DJVR^&m2Niz87^idrTVBeS!? zF;r7x4#=*657M%_bfLQa{^^O2J^s{Z-*)T$E^K$zcD-3to7`{f2DR+aJUEksqQ+!9KMs~T%|eK!xWM|XNQ%C=(Q{Y zh1dls=3$N?A~|c*b<$SZM8srW11cR!lB6<%mL}Gevk!_QFN@uJyL!x{Zu&=Gd;cGP z<(po&xki^;jxAC{wo_FuR{alr=d)5e>38SFu%q&tUktT6 zFmm81!ypcV?B4Kscrrya5|1F%eenPHNZIAR;98k~(<)PvB!~-975Gzc|&GZV)&NrooZQ)acs*sv)r`(V54_=YTqdQ z{{gdSwtvb<^9>7MTU80dYPsKm7y%1G+#ig2c#2^(n5VL-={qttP;oDQ=MV0E=2LI# znJIy*M-KcRw+;6^p$DSSmB6E>q8~3FSD$cO`O!Paw7?BD{Ey30>FfcPEsY>=q=h|- z*J6u>M^EAILMH_$X}HeoZSl7HR3YG$v#FUu#c3{`&`9wnh4&k5w|zxWH^Zh!v^OB3 z-Z#xxAJER$CBjl=TjfJcd_0tzZS zRcni%Rh!CaQ6maH&9jaVwi?)`hn!mk6WET6b2U))i2tcC)r1n7797%&dd^PARwQI7 zH(^4fk*v5SiVBmb6H6dGL}M|XS7qIIMF@TA%U96N=#Tl5& zEj>F7(U?(fZH4qBpJ{}aurtdvE)3g>fmsMn*|z6^RBLQZRO^V_=wU|Cmt{&Po`_B> zd+O&w_SV#1Sgcy1OV_q5-WBtJ^_a^-(}Mxr-LWVWJPpN&b-1x!#t#wa!_Frkhg=UB zzfnG=T`5u$BD>zb5Zn=WMNa3N{@ecXgHKPVx^ZKLBZnQbZC;47MDQBos|7$X?pP|4 zG2u)4=E_KjWi~}O3{G`2+*sUrVanSL&u^gZ%$Mf0%C6?Yef9K=ov#|C@C2Y94WCg~ z(lU_qDI~zF&yRo9A$>iEsa^ubquIPQi2BUTETJh33j`3Nh|jN@vdF*q8y`(+$<-*k z>q^n(a~>K#MZybfDj8ma`ZPf_j(*$DUG(~ba+Dp12fYKJWSs%nS$nW-IQhqeRi$#Z zXny%O&tCMksq4DBUE+|+8Trz(^b!q9697#Fi8I$J4M5^k-HuOqWc|9o%?*hIHR^gO zR|%)dynJtZ?$%JUupq9>xKT4fJ|KLC*m_7R$6XyxuGY=Sa)2{fGg=t(!xPm+2K=Qg zNHX;^?v-K=&OsDz5T7QS_3(KjB1^C<7sGC9mT=W+n)Ew=aQ9b#={TkX40t%dDJw>z z5L1%Emy)%CQNKDExMPgd(ed!W2QKcsXRAU%r#&-i<@TL1ybw{!8{)pln4L@FAN`Q+ z6WzYhAUA+ZL*wp}G#%A_yzUNM*W!fVn40gself`Q+Vz9PVj`luBtD&Ctv26p`xv@= zt`tV>;7aop7#T|eiM*ad+b%7PjLX9QF0ho6A4Y{wsAlx#gL0rW&@dU`#fnk3nr-x? z`)tr)FzSO=+V$c}OX)u|`sdI*GpJ++=WaCUtKm=(A_d|l#6{H8Y1KIb(_IJ`H8&ae zPx3#}*goi=JjP^3!J(GGy4eRSo-JpRNAQzAE3SxMi(5Wg1B0?bvK3{)G6bwhI(5g` zYbJ4tLnQB^>u9N}Fts8@Ua)FrZ#LzAINm9KJGL@8#uAvfe}wnoIWr`PIAoujiNRQ3 zPxF{-Dy;`$6CSWNKtNtET}?Bw2u17cA+pD+I@Av)HE7S$hC@>%n`PVEOI9PgK1w;| zN+aAIssYQ8I53g?MmVWGrZ_2@0VZE(yKT*2m8lJ~v|Mrc`#SLJ3*QrCAGlao%2-8E2i)V_8m$Sw+s-T1kYfzzR zH~Y}(w$AQ0ZcnHMuWQi$Mrb<+eAHAxj2d2otdprEt}B$`)Q6T;*>4wVy)r0fU-Jo1eew8(RW(wUA3BMI^chD_Xx8Y zo45%C!|_819EBh{NI&3$J?I0+wOu8;h-mhOum8#?^wUu8HW&bp z>!PBmo+$0%gN5y!5=%XRxoQp%>i_wRAI!ytw$5Nt3}e$`c7aA2s7_g@aeKOW)oZSP z@4vp17mK{xH3=tN9>yAV8g8DcTM&FeYJvNmyL#-pv;2ZDeenPLt9S4EscLf#Clppl zRQBUDrLxQ#ySU>55k`s~gd%a0N3;qC`%J`v%~(tntgy5BqF^eO2{7_BQC?{`Zi^X1 zt8$fKxOs0de+i8^OCz@@u~SjypwoszbiR&<6MBM)3*+P=QH9N7fe8`1R?=qxl|XO| zB|teYQhNQH*8}tg6*A;^8*bMXGJr`K;BhCZj|d2G)x(CtB(u6IAM&8;&)LA6skvVW<;d(*I0oFZk5Zn0T3OvEBV+qX@x+3zKfVUQT=*r^0v$N&%zvz*# z`K|Z8`R&_OotG;}sz_WC=Yn-N-w5cXNdvj8b1KKC%vaCPU-;Fxeahn&XV>ni28@6` zrsmZn4?;mvV_m0dgxI@UF3WLPEb!om_b`7$t^}a{t3ehrO%`KjWDRi1PT2W4j7Ulp z{9{iXp4`%A>aOWI(AF=8o(;JvL{nImi;My19>1oj6ja5QQ@=^|a;WO(f9XStqQe8m z{UTVhO6AkE2|oKu$7HNb2N=Q*B=!l{1}|4r&?p71dkd?|aZCVx>msd&+@*u`E#LEj zAOE>^eTYdetYqLe37o+CMLlBM57`I!t4r{dBM$GD3u!> zlSvNo<^i@fgF3&>SOyw0i;iTPCbbBwp1r%Y*NiF%IPIP z#=GeLXJu@_3nt;ZcBSufG#c=K4NWXTWSWcFsHlgf#4znnPZ)~pS*|~iyE3$ttX9-q zAfl<75PaZ`AUr)tYr^{i>LP)ZTR1@1rY#@w;A6^On5wI}WH8HP2Bg8VWxyoCQLxe; zeE5U+yy-3dVsV7Tm~l!8?gQFF@odoeK`H|rF_S1BT5@5#?k9&|k=hW%uZV}JtXq}~ zGCwv^eFWhYAEQ7RGu0XBPL|8`?)P;cc>nhH2f$9NUK~!{IVZwlIE{0j=NiW@UhtSr z(GPDZAOGm1y1bgogfcB6>7C#pY*#u>A#M>@7dC0~aS014%Pm>yDU1yXN)EJ(*3HHP zI16fcVMv0276Dh$(Oc0wlIq8e11l%t5HpWno(mlK*c6lXFBTkSeJJR7pryKc>pQpi z-MhYYu_^1tSZrVVC_CfgkZ`B8+0 zgEMRQbjdLY%>~@4fQET|Y6lt@0;U>5|`2}Cc0%$Eu$qi3WiAI zd9}nSo8^~^asq+OD2f;;G6986aH|3HlxF`5snRfBCedWqFdW;7l%~pBUnk18%1y;C zhqbbknnmW+6M5Y~VmHXZEi`H2;B1jnyv`m$^a=`ch(6MFhA4uaT{9^;Ri%LapM;AB zrVvP&{ui0N7HK$QWIwmy&Jn1`tp3oQHWx=0@a&PBCAyKD=1^st zdC3BZWpmKC^wh8}kPLk$XHazoeIWZ|?#0;VB)C_Ff)9o{gJ}6>nK$>A)vj)juH1N7 zHtjGrb!usi1G^^s3-BQ^_FE=Vk!N*{o>97f;%$%*J5JMjDD!ze4%4tL`hKd$rb%XL zaLZ)5GH{~FAg2k!VElTy+?5xO51aSDyY*(%TsU5Ic}jIV4O>7mHEH=ob-dOA ziD)q1mE#$}n5OyOZ~de%{fDnl<>54K5NgLk4MH&G=p(k4ux;FksX?;UZph_B9x(m$ z7d>fna$h-|BNL0nNYs;XjVJ$;cw*gRVmWSyqDQtBY zvMs89JM`nzpRjuN(;v{C-AcS zUYE|4f>~OsQ<28is`-sSnf~F2&TqQq(wG;hAbDFr>_HKrSuVMr97EI~#^LCo#W@FX@ef&HK zjqL&;MQmUiJlPe(hKfovK&wIoT-0^ubrBGzmA82R(H@9;Dwz>~Lwp1g#@IOQ18HTn zPiR<-wyGHitke0xtLwV&;17?8O+ED0TiE^S-5ON(D5 zcWmVplYnQQ)9l%`=e(j)RP1v#4A9UNxm+yUZNI}Fo;ymMu<3CYZl@%YpUfEUx2Jh( zrn>yDmptW*zW(>h>9FWFReR7R4%w-lk(IBi2>v@BgQl*>^UZFU9{RBMU%cRv=cjkp z!-kPFG(>}l8MU}i_qsxtL>Jcy88H3f;^@_{dH1J3^VZ9k4|2C5V`CH^5Z*7Q=Q+ZW z$&vgX@WAExz2XF1M&gnHd0^){Q%Xt`Kvnz5^4>wdk`sxrKz&!3Eh!mQW(3$9$GTqh z9YX(#s!fT63%t3r<22DJi#qps%1F}7W6^NLW*aOC6GUB!VVH{ zt{YNIuqlXnYe~OYeKC#4#(;fZb_TRNqAg%uq*M$w{HXga;%5_$g_#b62zIa&&H86C z7nBn|1!APn?HP+Imy6-tD%F4{&DG&SeZQMA1*sWEOK8d97W~OArRR zR!3m#!no=DI~6V9KiCH?o3cBt-uSllBOZErSPyM;ko(P?c;?;>+W_Z*TKQaXRb36a zpZe)x4{2H+HT12`a`BZpmdbJhMsl+?ZBLJrZm}s3HpbO2sA*z{>XOI z-~l(0p@azEb|=t&U~^kse5VS|6mYtJ_^}j=1i-*pHMq_&NcU4vwM~8RecgvXbav_D zjk!n&l4(IG(?pX+lqIW@t6Rsb;Aftk_q(Mn%B@%qBn1ooD=EDtF+$2WY6i*01&kHs zs}SRxS-;;B_LnUBx4^+nclUAYi>rSZMx}~FU5vsz)p~}SJ2XB9CSn#~_MeBIvBT_{ zU!Ig$xlb#(vhg^XI}^W-woWV;`#77nt~x}SxUvk0Ovn)&Kzm={>VPz)8WsjzQe`@ zuw*9gZ{SiyOl{M1-hqV+F$G3b7Z^7@YFlqy4gcy0YdFstkzMazaG^i_`6%mTZvMU8^8{AnxHQ8{$$u}UQG5=)nHcdp)I#G1@b}{AYdt)pXP(eEs50<0dOj4 zZ9h?!+l7i>lTq=jO7`&cr1UJ|S~BtHuB(p6B^7lNrpyLdQ|3O^>mnWCya(5=D~AqG zQs$grr#Qm^GR)X`{Sma`CP88iAN=SqCqzyHO6teFF#^ow56zHRX!5IxripTbW?vP9 zw%c|p+M~nbb$|NqfB0>0zIJxg(Lr_IXZSO+KpKccP}x57taSZZ07cNKlHNo^As~i- z3mQ3Tq=4II6##)C6zBC+rhY0@8cwfmUjDQ1e$kgd?*6x>a!OMk05;f7NwO*X58}r6 zeN{sf(~q08)8bjrc)-_u;otrDU%2PeQB$?!2&0*C%pGb4M+IsfPl$^f%c9$iW6=%k zm%a2;maFag$w?YI)aZEJP)fqJuBvi}stXkut)Z)??aK0Cb^NMdyW>Y+{n1~4`6KB~ z*Yda`1D%V80=lEyM(ws%lL%Jm7oc=_Br_J&tLrf$E0QI*XI&cd6t+tCDUPyNf*`yM>=WDWmhkcSM5*!@(1rdyLfyN z6I53BI`fE@B@rw@6ATLKVQ#Ta_-eSrI1k4fAFlLBihQ8}h z^KSW#U-{6V{f&>VyMA$@EpwH3SpGr)JnB(SG32)1y=b){}z1H?625duvs>nGQ`Cxm^ zq)8NNAe=Qumat|<+LY;qkNIj*V=P)iC;XfL`_6-d=F>jq%6i>Z^@85(WW{5h2h^?1 zD{R4#Xw>6rw<#b0=v!X+6`$~5fBKH&V;bfx7Q>EYa^kDvYejF4It}y9JoWkPW#9a? z!)DX1w{_9sh|(@G8;}9PHpMyjv@}fZ(Lw!7zwyzZ{N?jcd*+hnT{xZT9BJ;q22560 z(+As}FVg4)1G-?NyHfB+e7N9-=`aO|3I29Oo6`jni{DuxXVBZ)ne3CK3Mgtd(N6O9T0dr~Y!<2GUOrq9N(L3A8G-Yom_koCQgQ&6Vn z@VF`#bh78{mCpL4a8a+IG8=qvmXk0QGMUjToe|!^o_1My6SlsxiHrwPYH2v$hZ0z+ zH{4wXKCx;ej%g2j4R4(45*5CsRzk*enP99y=7q1XUDwqCQ9sFKT^tAE>x(|X%8_8B z1-8`Hv&9n{I@^~iNtfnYyHiDUYrEi38mOwO zLJT{%GWe3Y7o{Q`?%BXb;b^>GW6!kCrlu<)iS!eqFhnbD@GX1sx@YK?=6{;Bn#rod zUju$z941e*G{Q45_7g;-R2cd2hw2j>c)#m!xUsnLhQ-ir5*%iG8hOt$F%zFnB!N2z zpB$azb*eBeXfmEam4Z#eh{Iy=fa-b8k83*znD94*RY_l@>1@*-2u!QBNH z#yGDYCFyg4Mv1o?b{JxDdr*RYn1~t@#}sr-fmxpsIz~2#QGs>-;hQ1r>4}Wy? z#3w>zJAoUOY=44H-^zLr7fGiuRwz{uZ{g+3Nv*ok0TJlgAkx>5Mqi}z*kmmBEdd&C z(>*)ZS!JwCPn@FhtQhdQBWFjOL#ZngSxYnTaGYRqWsAkxA;aWn`ZdIw)|F-mRb=^j z_8%B$FcrhmKb)yzq-w%pQ1acU`=N1$62<#*sW^nQaPoh)Z!|Bs=8(bFx5PNG3vx{U96Zcm^6FP3@gh)2}WIK3h<~C0T2lClc zg4y+Wmc1FRWO1|W%2x!3FyWv5{cRZ(HKaO1e=#{4@*D0!keO9(!a^*`nB5374<}M| zZd$*jOq#DAnGpthd`2^ghxa%rQ+s)Z^gmWK6PTpdPX2Aiyl06CdvV#C1(*?<9%pA4 zP_ik(MH?6ABf*F=c)=6hGe&@CWTts6L#QQk_1F6#Q^Z2PEs>-IE?Iu3CrQ*SMeMj^*Vpd;vy@FaHX>@TaEMBf^f(p$rd>8?S2y4G z&pzq3fAVYR+rtKVq*H1eWL87aJ&pa?EFhv7hm5mw=&GVP-Sl7n`44#ZC*QO_`B*B^ zD!b58ii+_S)x>D$F*B*lrf%-KYx@5G^08ZPx;RyXfF8HFp=?%Q4W3Q!DzZKTpd{U= zAP6>0Y9hpM_l7CR0`qGFfWenC?+wClQV#HHOy@+oHSGFlKe7G4pY`DF`AI$PfEM8c zpk~Yy+#FauQ=zOTpiWGPEQ)4%cF#RO_p4V|M-LoJq+t}j00nIrAU`YIyH54N!NLFc zyVt(vOZvsZa@eK>*?mnYSA!yV-)2m~Ke8Tkmxl9xcXaWVOV5Aa4L|rZ_g-11+>b*y zRaIM;N$!Qsl?kk)Y6gfmdV_TF~NKB zV;|o>{xRGf!k3%-69XW10-BmIPli=DLI-f=N?SMKU5BSh%^nE1`n9W+(;X>pfJfeL;qwx`Gs!>ot z)hzD0mVWY=?tS)?ZfjHDPfaoPgwD003D5EVDhKPPsrr6h75!#iee>5p`uG3$9UuB= zPSqx*M#SJ$)KV-)m`5^3&_z)+OfiOmf~MI)E2jf2 zX=T9_;~k3e4((-CQb3~b;%{%V#0H6fA$0+-IZ-6oD|(1Omi-QnBn;62mWoyHj~PtW zuss%~a&OVVggruI_vj5;wY77kF zodj|?J;+~>)EOcRPXiot&aReUjaUiuM2%W|#INq;Icc`;ASrY5>7bDU7e zx@yF6Y;T89V^A^dNLYyh-1Rx((0Puo6@Wmi1SjL(y@)AC3RA{D5oxWnLAJbDXHQWp z%41?A)*rBD`69^47-ksyI0d{-rCJQ`INg!y@e!k5r{UOWR+d&1GBo7Cjw1tLu1I(w zNRSFA+y^}`Bw73)ykDy9VIxCuNhJWXC!FpsC8=>avniFM>{e(Rj}NNlqMCLPI+Y3M zLSQuBpk8)H3}(b z1-u7$JYCdtr>W~M98?#MtMxqrO>n^}roe+JB`jbknVWA@*wyvMdNj-wJ+rcw=?hE9 zYxeJ&Y4o-p2$MNYHHF=w<Xv8;5XsZvvrTktZ7V2a@p zPl{aeS$-O=@#ps;V)SIz@|#K-N(v`rh=wMbjA}zKBQf;ZCwiHbVOw?4+=D^8j$*;R=|GM+!VEN!FEQTc8c zZco5?V+?y+xN9AoTR0Xplt%kGjec7m-#WiEbmT0Cz^W|qgdx&vTw6^9C)s@4G&5PU z&m(hE&5Z~6s_^e*@nSxeoMGsur7AC@5fZ^oj2%_tTI_--?YjVSmt(FxH_#1Kf&`zK zy)0!G>exZUydyf|TWu=aVa@uvSb232DqBuq;sy9*aU8Wj6!0nt&C5iyf5SiA5d;Ux zJKM!u14+vGJW+@0R2ttXn!3kjy@)+~58}qiR zhH30m!&t*&WCbI?ZUNVH|BII-(YT~tRSS6ko z-#K~B|GK(5I2y~vR50<;QF9nx;w4%Suo3w-c1<}p{rNa-Q(Jxiw?1vRJ{kL=9(Sq2 zbPgfgZPl(4S=N{ZHuZ$5U{T$6Yxf=h{3+|xYg2b#4m%WBm^{$z0Y_swBKwfVI8wyn z^*NMvbA0sOKlaX()0C?11ndR0ZX<=5LCxu;WN3y}0CT*#Ufh2P@)A=>Dov$@V5aQf zHu+JmLsjd2nr0|$0S6uZOnz3oD zx*lN{2NxHwdF^{YdhZdgSmwZrXr^ohEb+BRawG8|l2Xb0AwFY7+eYXE233sY|w5>MH2g@ZVndK!+( z>xFz>ENXe1#e zZSN7tPp{w;atKf!gD@T$4svPNzeyT| zeH$L5axa%LwfV?aief0iS-9Bs{D{0CI*6`ZP7Qf&W6skEBUtYwD5+%03>Yr3dDDP3 zaolZpAHA#B6>z4Mhg3-5#h?hqVFj;aIBno&^Ss{M`Pd3Xl39t?f{}!(1N8&zI`xVQ z0pYgGtRqrBNzKJ~sOUUZmG|6@Mi1N^T50QBYxJT@o&*;X7^J}q z4^WAgV;1j9BWcI4(J+YlEE5Kyc2g7*Oeh2xIU3eK z?<-;=p+$58`b`zz;}S+FMH-y@K}S^p?BuR5h?qxpY-bUjHs=~RG*})?ijpM5niWa# zro`u#el=$CG1D#Owjl10wK#jKh2tMdxpgC*Q9l?32D0b)WKY{n$8hQ4`8l6DrzP9C zK#1?&=v(-tU`?LZL?4iP;^{m8+!&FjyK-%19WY;D_3u;;;Zo@Jgr&`x2)Tzci8t5G z-j9N!IUm5@pp?fz$DJ(WXbr-sY~Apd>YF8>Ag=Ai^|)c5a#yC(5Sq@ahw06FWn@g$HhqW)NqRA5xXZohzGo^k;5TZ z@GT!YpV7F6B;3vF4}(RTP1)34sHyf5=UwPd^3_!e$c=LLf0SNY7+ZvWYPx6a&4H=0 zdhDOIpQ!Qvb7E9kNtvoN0ivDipRJVAAl3LLY0TbzSRBq`UnbvZtc=JQw{L~CJc+V zYEsp<7y_7~=&E6sa_z_d-sJ)ewQ1jcnov1NxY|bNUjN*B>eX1cppt^KP}I5n_dogm zdrw#Rxnyc+A}>bqV)Ro7Jw&@Bz?JQKkx#qr?z2AapDwTPcQn~A{zU*H;;llAytaX>ecGtH-7VD zzxfBd%Ll6-k_?bc+_Ks4Hfnn121(tWYk|wbk~6 z8nLhzFEdMIgeJ78uX5k@&w5h(v?t%M@B1`u0D%gLkF_XHp4mhYdnRyusD5S+<5RMpMK^1yhD~Z8eH@!iMENfIhR2l?W!__6;w5#hmKNSlxL-*nL&!? z8~gA)WA|s-(=1hG&O5U5GTez!ITYLn))V1NBo%E@tVhv~v+UY$8^Wq5z7`r}}UZA%^vP++F$^ za*=5-SHhxFs0j+V!c)IVDHG)PG)88tiSQs0+y!26`xj%uQ!?ye(Qk66BVB^{p9+$h zl@JC)+Dti>5T;;e=FA{hk#4oK6*ZPw%xj!a^t@9?2gl2U>#8=4y?{4wKLSqMP;vlb zXo4@Krh2bYjk{pEg*+F?C}5HY?W&{rM~G*Tj%7QoZ7ot~9Vw}aGy^Zt6l+#UAWk5a zp=Ozs^2@t9gNhTpDi&YVo%u0EID@VN){>5R4pQmnbhBPx~o@r;)=%s zp-x@$M!7gdkRhjg^uUerr(HSc_y;4t26>}1Gxf}w5mBcDMpKp;pPLAhFPrjgGwya0 zPJqf9`ZclljA{9~j36eK$vE0lstymtK>&0Stq0KyEdiN?$#7BDgU*f-mLj)6E`2N# zHQk=2sy8!y;0jq6Jm!1sQ1tz1&lUaa%x2f;ac>#)3s2H#fKPxUYu;Y1Pz2fuZ?4K+ zr=V7HXkC`8Ke1}uxU@?3NO~lgyq{1lUx>m(wX@o zQjvN&|4sP*SSI5dKSsrbVrD=wm<^sb&D*}MzWuG-a`-)kK$_m5kwrMAxIZ#f6iN|| zt>?|m>qvm0dRcuRdjnb}3BZd5xAG;8{A;WgTbf|ZxsT;~u!E_5TMV|wf#x1iYcXa` zu5zW0uuDZ4K!`*a$DtIq+8$Nj+K@hk5+Us;bgIIGw`Nvtc0!3xrJS_#@HoBXqWD*?B=>*QHLgl(cAlcrj{zTufco|Rp{YGvklxP&hW zm-R4@CBEcMg1m3x{Hg~%E@0En=?~{|`f*Ja@GYp1(`=nXJ2W+Hw!KnyQP?00E{Rwu zp7z=fE#2W!CYuw!j$42B`4}$<{MH0gmUt=}#AcL5g`=8K2SN6vYDQBS9T}Q#MdmF4 zR_h!1hq#_zY*q(~`vbdKTZ{38{91dC#8A=ClN(rZ8c;9Ka5$z#>k4#`@v7A(|e zThBz!sTdiaCNRrZJRu&>b5)LRP zn8pDuxOn9zl9CAFuoaygjJ4BA8zwNM`4K18`A5I7oEf(;)%8I;+b&dLn{WE6M;t6r6t|0_ZY7oC;7^E6#&iO!lXb8JMLv7Y?8VZfVW4|m zJh;&PXx5^=373nTsafkPAfg_YuM>Gd{#%n!EgaRChq?d^W+Edxn5B6QwSjt-z?XvE zrXAZe0G}6}A*-<`MI?@S7?jA+l6ASdyYQWvqrYu*;ZZC_KRmx^*ghuyYgH%h%MyfZ zKO#$>14o=_c#H_)i()3mqonVy*k{awR13A0_L$Z2uF6wHJ;oghJx4vPTLh3Q{Jive zbRKEM0iR~hd?d=n7p6^pk*98ljjOGim;KidOyeQ;tJHwqBbpCSa9vPuEFzr1C966En{V87yD1G@kRVEF$ME47%eET(ao2CR`3pbo@@GE#XnlIM%)1J1b%blN zb882nLy88t=?lZam~6pMa>^a52^VTLxLxWc zV}0U?83&?aoT3i{SF}Qu0R#ro(r;tHFSHRxrNO3_|E|bdxH(W}%q6&E2F&|)t{h%n zW{mcLu_hP0Tad|hJmXVFL#U%wtBR5~b4E1|3>#a|VBGV`p563W&wD)%wWkW7eiWHx zt&R+bF$~CJN;icrQLctK6=PK?&%T(*;rM33257)tl9}{#jVF;6cwC<3_<>Q&K8x`U zW6&8>S>yp|sGDQXfGS8Swp8WFAzGv9AQW>@=V)PB+%RsFWr7|nDHg;BpN1aX3F4SB zxzZO`1EO)Vx;|7WvcsB2DQ6Tx1!h{iaM>w^Ho({X3!6i6QnDrc_7fnogCd$@IFd0Z1c^V*E!aBrW zI#ByI@M0St;f>_Pf^1x_x!EsXJxuugxx1THz%msU)eQ??8OwTPm_T8?&Z%%%sWDL# zN6r(r8QfP#Xh=P1D@-WoY^Z0S%vu*H7$}7JN>D=6|3cx@iK;m#Kld86}w>Im@J9;Y5M!ab!FD^-8G_xQs7IP?J#l3e!D6}ZzTLMarFVB6)T266RES^w- zY<%6e>&`!%!#(+7g$?_Yk}7O+-`=|^>_bV@(4$PK+an)ABfR`7-*v5dZeW~Ys|Yn@ zcpmsU11g&ZuY7PxR|_STz>Qf^5+YJ|sAz$#htw|MSqw;b7C{+&n;C!hu2fDGn1?QG z6_kfXBt5HWfL1d5%NQJtDn2++Jd-(Zp~`7L#+Ss_su8`k=^{MK<*vfZ=_I?k%!=)E zb_NOyZ9)Znuc&@3l+@_T^blgYkRyooP?ufpeUWazJ$?Uo-u^rP?GvB-)b74(Cqr(l+?V5K0Xl-pu5UqRb-rm_row2sa@4atMS)<`$K>JSJ#@w z@l>sbnEVlxqLOf;Lz2oipdMII_3nJwogQ77zUyB;VSRoM;9%RCCp4l=L5;uJj^pCu zrOo&Jt7mp+n{qfScWV~H;C`7miV2=sZgta$YFU)&V0G|se(0_1-Gy@M#;Yq3U(uZj1?{By#wpIBS7#dG^fuYR)9Xj#HbMpAos!Ags~Wv$e782gloSBL(PzBSa2#Ax0v>5C~o|n4(0YukIV)g zrt-;BHETT}X#TR1DMvhQ_`@vlm^qxRn1zrK?9)yiHJ`V-U@+?EgobDgJzM&zW7fP( zq9P32Q%ao6x!yJD%r@3$0AE0$zp2J7&R^E$p9ua~2~2a9=d1Q|$9jR#uF)6Cu~-i% zPRMW(NGy*if>VG(#Fq@ss%fRxjfa<{#bxreq1z>h{WH6D&R3SfOT3mJesYeN8_GU{>~hql_NVT4{jNJc8oui# z4_$As75zk4_X&}w!&r_(Jq`VK-S^d%E7QOFrbp(@X_fmr6As~NC2!3*h|!u0OeEOA4d;?Ua4Q#fuprn8 zn|H#E8)SG)s?j!Sv$LCtVY{fpP;Kz+m8+M&nq~U10 zpLZheznVIRnWxE#vL6zapL52rM)e*eqc4^CC@W$RtiFoc6$hPC-)gf)Q8MI_%)zbR zSvqdv;C2m^iCx(05hDl$2Z(&&E)B_rJ4F$JQi20E=o55* zz@ZfHIELDU$n1CN30jy_d75m4QM6uEQ`uA3lvt{L-DXid;#$bM6EYbs9T|9^`dBK3~9y=M~`l@og*n=*&2JhG+h z!@&w_Bc#{%JU*goEExCrU+&Dac`ru;VdKfFkGBE^6-GdaIe|BgCckt{nYo#6B|SCd zge!o~*t?7p@L3#?h|b$dRuS-rejEoR5dsLp8E(aKG*R3Z9b^+R7Qyh@58sEu!Huek>XD80IjaZuA2(0Ka z283&(s~t^GR2kMcgn?}MGirD)6w5l~*kWZdKp4o1J1t0ksr}3Nj=2lbmZjqsfTmnM zsqYmJ%PFZm4n)unD<)QVMu0+xt4nJdSe$vb!!y#Onb)jAFt;#RNx|4MAnG=E)_crF zvL9!8u!Wz6#3|vt8smU)eAV6^chWjxT~B@p5(q_5bm|8B3~auFH%zFBt~|W0CH~PN zs){E9OU)z1pWxz|frd^e%yNT2`hp1%(Q^T0Q7U336S%1&V|EwP`Pvx>& zt{4QW;AfiEkP(1Cf>Qy8EYjsKihg~*`P|QZ*k?X_b+*Z=kg5gO2}@zvHD$ftp8lI} zdCH|r)oy!Qbf+l33ycbRzM&g7aZfnjSfk3B+STFV@BZG0e(TTs!$XXchoNjaST68M z8N#AND9)&G`wRPcOHZuoNB11`e=2${PVwj-<#icxos0;wd-)y z<6#LDMt2tdfjr}=b}J8-^BrEmfH>Zwn$ zywv+#;HQzQsK|832Dmozhhe5Abv1%mIq;)_um;y+*|^W}0GW4(ZH_tm#BtnE%iF!k z!=Q7fs){QYmp}O{AAi?dcc9uXR!zHL0E>_#x$f#nB4gXM^l?!S>+SH|=iK<&pMH6J zI;Fl(HFku4*VpA#PyM1w+i~};|L74nT&lL4u7pX7y|Z1B%gU#z%NBMB-~u3bD;*yl zy!LnQ{*$+?j#t$#4_$|*L=a3Us&rIv+QG5-Ogfij8=sy5h!Pb>M6cwp7G?9O61B!D z+qxa|L{8mK$lL-p@@cDJYA~AJaZ`vF#3E{^u4f9E_7`tp|jtXYuL1qc`P+6RD7sBEC44iWtov`GYBfIq46lbau1W61_xXxb}KP74yVg6(F_#k^$Vs?!gc zx)WNe(_mt@7Giy8KbV-X3l2d4M#xeuR6KTK7<17BlBe4mXW0O~P`mLGN+rwo4)_x1 zcI;<~rr;Q4WQc2WAwJ5qv0_$VO<@RHm>@cZ8XuEhd?Q)_3*f>{9%H(o(r%e>fQqk&Ei?*Ad~yz$lxXAmup3^7Hk@2;TS4Cf-;7 z$Jz)colaDM)CWVgaJ1oxAnM~R4zpro0vjiaz)-bY>JT2=Q{x8N`5 zk`G8Kmx~e@f^l1-+BSb6!~^Dt)`|*v%k=~5#KI@Q7Y7=wqnOXakdzFP#hl_P&b~a* zz5Q7C;;k^aPC>MAb4TT`$BH4AmkTEAG?h9=MmR$vvo&(2XZZuW6BYL=w+@a#g&y(&xoW3q+G+~dd9qbA7kS6<9D-8K0eYkhXrX+F2Gt%xyc>gHjP5K zePmB(a51i)CVL(~%sr9bDAaT0L%A9Z;3|$b31nir!oMWEsbn-ye)TKzeNdMla0JgT zd~R~%ZDOG3*^Q?ztm?mTS-{|jAAonu&NYz`#BwP%G4_b;in*EC-_FU67BVV2BitFn z)*g3N6gq>x^V9CjA@BboXOgZ`N&w zAB0eJZ3j$ZxsD*?ue3MIQVSWbH&4 zxK_T^Oqn67CrFDVG(jmg<&j85`U_Hl2m)w3!MRW9k>3ea#_JwFga5uhg!k|tSVib` z)fy(v%%uy^8PWu$6d00nw?srcSX{D*LB^vK3hEU(GPg-&wuI*KYP4-a?%fF zHLQ!N1M|Kn8(vxA@~2_77F=|*rlhtJyyjZkYtRl#VT~%<0-Fco=+iVbaKWyMq3Ac$ zR5hzMz4rtC%YXdM2NxdHj}7K)HcvAIIGgyohGtkpG3<(AcXsvc`@a2CR);6MT$kN$ znx=M9m3f=0>FW9J%RcYM&-!~0JUu=P zVRaEVGc|}N6O&OhdR+#64)VTY5;{-b6~7`i32R!B%E>T~y;u}!^UF9O7E1`yP(lJD zsToLePSx0?vdX)DH$LL_#dDtV3H>IgX;+u9<2DNn2f18$JkqLI7eJ!j9!%}QvbgL2 z{e`;@4zJWr(JWVa0&BfS-z-ZL=X;Y+jv5U}3pfFZwb{|nzUJd~-NC=3T<~y06~og} z&8mgr*7eqD9EK{N4_$uf!w;VKtPAJoV~xno3@*t4&Yj6Z?!%N7KM%0j+v$Y%wk9iH zTM!5g)l(iWORUi}QMF4usb8{iS2aTwGcFE$SrS+fszj_$##a<(@kPUZIj8|vH3rB_ zuqOfv1WpqBcLci1P|l--D(L(1H7*_|#qhb*3Uoc(8p1nUyCo+%=oAy2P`0}r#8~q~ zf%R;fT?};?M7OsR*LJ|iQL-wy)5+F1z~}(eBYiJ;mL3D|X`n`awV6eEY6M#o20KgO zET6e?)(}vY1RYFDvPv)8b}Vw04!`3+zpHGIhob3e?26}umgzDc#Wq~mOm|czJr>=0 zvD==XZC?5>9=5!6wgax!@!09%CA-~roBq?DdiXidzPvd*sq(g(dOHWv(bTSawrNtL zVL8@K(=684%J2J$4_&$8Vwd~6U2?juz*1i?4L|sAI!{QAm!5)kpF$XBiZtB9JX0WB zT6$-8nWP4bnCKz180F4IFlXFjW{>gMMkFfR{ao(q4B7xNuC+0;*cu9nR9;VFE11KkJm`#*RV{zYUt`9gl}qW!1+QcCsiLp9ley0lGCM=6BfoTJdI0in ztJGFiTUE;{Ey{WUo=m+cnq`q7Y^$0Uq_VoH;1IK@nznA1b!sa7;-XB8s#(_ULDd{o z^+DMjR_VBE4%6a7-5wX|uv#3J&9bbT645_mFl#sRsV?@uX|EbuYOEj&hDh+`T!_Y* zri}3fv^Y`QNY%r#mp=y20`AWy6sr^s&2xxEypwYJnz(0cx`$VX>2{!XrWR{kfsrty zta(Oh5Tv12@DUZ^Mx$!;XzefN=|Sk8IQ3UcsY_soRcQoypd21o3s4Mg)@Hi|A{}aK zNDI(%YE{R9_ydJc1N1gcHv9C=Ab}_wGXdY2g)w7~ z(_)3mR7ZvfQq|cr`2XMy#AJVOl)>dBIA4^>pjD_o-}`HMsz-N&$b9jU91S}kv4Gv( zuNEqb1=sOYS|KuLG?QQ*S~$Cf#MEA_8`Hh*Dn$KC>{xsSfpD%BwRMLHjzuRn9aNP! z&mto{C>-13sg=V_EM1v{u|T&?kMJeooGMHmE^Ti|gYGuvnl)^^zjXhxSJytR#XYpE zNJY%Zu}eX>%*zpngf3Vtdq@?Fz1!3^;&_lXy11tqgH3bf@Zh`?{n0eD+DN1y$N844+d?6kVG|-oOcodgf2N+UN#uD+bj%p!|p{lF2?ZbFtfWFi{v_SBP{R5-ak+#mlwqfYPyOrhc1;;|s?xeeq-e<;y;B%Q;G``z0A|Ng}@HdohGKCPy0U6;(U=M>cjNc2%_L2Dnn0WJmg^6<*?|M{-h z-*@f!;-zwv%WgNMqH5C!jf@y@wH3H~(-~vuwsuhItX9HyVikeKkzls+;!Swg{SEG_ z409MJs;KP5G%31MbmMO5x82u#?xPQzwA*#Xa4s6FtmW`n0EYKIHBMuKWFFC^Q`x3v z|L(Va=ymTnUap$WKw&YmPAXE~05^=|Py_hDJ%>D&X|~l=_C1D3?Xv!ZzfK=`|Fzrh ze{qBmV@>Bv#i8MIa+}m6?sRoL5xK95ZQm_k{I!pG%^$xm=eDlkXkS@kwTC65Mz^DgJ^fPEUq zG|aKX)l7O18lUU|ZoUzB*$k*k+qO7_rqno1OyoP83yU(qsJptl@$v%yQowRGAP1IU ztig23Mx?E-iyg6xsn~9j_*sLCQc-X%erT?k<{NY>+(mfGn9k1Uc<_RR0ofvm#~ODr4Cu9U+cO*mJp99^j59$Ajb%TKT|d@~ z=6D+4@`3bI|KEpR@D&f)UIlRmjf0Ock%Vb(>d%W_5m`OMZo8{*xm>>Fn;!Vme|P7N z7Y`PTyl9)eTh~=PwkO~APoL85t_|DsG;NCn!9R=qhc6e9;BZl}3p9LSP&@)Evu@#f`&=vhj?`U`@Mt5J|A>$qSmS ze$rDd8g$f`hZb&F$graXFNP{%Z7V-1!sU!Y!~sC6K4?X5n27@f^GX(W_AL~5em+R} z=QVDf;%q~0=blg-HXdpZ#g)hhIB2^Yt0J|{VzH>JorFK+3lIg3A-YR*_Fpz?Hf78c z8{z&k`j}nBq#5Y~Jl2ePl#TJf3#W;KC~7P|K2=KdS{1eFGK|A=HpLagGCSQV<& z0*yS_XUpVOHG&Ny<;BQuNHjoKzdQvpo^Bq-+P;0qs2^l@Y4EF6n}|U-$5h*x&lbXB z+~DC#Ro!qKoQb_;1(NYTcS!gz@*554I_Fc*=gg`J4yU~)L2jgr2xkc;{FM~+fMZ@r z1f=;i6rJJ4(3#_V#h`;gOu&>lTWt}HAE5j}+J>Sk&eyPk5qXN}cGzp_jbvCaLbdjI zT?X(Tigr=AEfT1SXa=Zi_Au_0;?HvLWO*j7vzX*-na0EeLsmH% zl(V+ie%su)7%UK&HWx2FDb+rRu+Ti_HmNY38Xu$f4RxO5jHEwVNCf$f2F*~Qt zEx8z*GW_2=bsONB0d_TKRK)Ud5a45QF2;?DG1lD0&-~tRqM&J+42+!K8Vf5lI&l$a zkc&F}wyn}?m=@jG=IUUqkH`9OEDpwEF_w$ITn@!SUo?Hy<|5^y?QV!*$WjbX$v^bcho7Hao3>-qofmxv(?d8FLEsA>zLgc86k8Fjkv`E&qv<+Fgi9-o zi_bmO&ylXFtR@|nML9LfZNl{_7ESZrKlH~%ee*aj#-bkkTn^G0X@8}GINk!0n`7=l zu+7^=u|7XP`^qnV*fXEl?7E^VHvR6jF6-0H`S*Y8Q<}qR98Svq6z7GArZ}^ShtSWE z_!P(eWjR!JyK4UE4?p~CzqPw?wCZ7Col*^Z47%wd|A&?rp)2uJVE&9$1Didw7h;6T zU{H`m8xhUY15=@I8bwm&8{Go_9o@k&ZMS1T-u}Sl^FHGt=i42lu#=O%8Sls{5HWZ} ziASoES(jGzl-hQ&`>9{LyC^RfDOYW?Sf;du?%m@H6ojc#=dUe}Ej=C)aFpw+9?tv2 zU;DlL7OPygtFl>Ym!=7jknk+k$X+bGTO?BIiOB8GL{`5H# z>m-!-b8M06X;sw}%zwRhl5W>G@}vUUe5rk2R$ zbKsYaE@ancHJb>4(1D@d^)bYzTE#sL*yNcvaz1H>j|A^N3fvfRfSkvot`|jJ-Ei^X zmA`c72j73ST^)|i;ea*F9l|Xt+AZ_|bo;|ALDAE45W-0t@>z6= z9ZXcl5N4PUi`PwMTG4J6S1XTICb>C}70dyhJV-Zf8&IJA9Lshr78zh$lZ$4^NLtKO z!d^F}qHKyO4O86@U~=@i%zZr!b?(c4Gj&5VmetTt!&EV`1bCPer84J-x@PW~=h@tT zO5xgv1rbM+IyhY}N)J0@{hrfE@ovb02exdr)JN#Svp$R1Kf3IYhKg1rs~#FaC>&do z1GS`KChGyC1C;$>Y8EADx*54s&*A4TVyY~+3Q@}zT~Wd1fTDyEMw{cr>xJo2d!3N2`-0TjhB58q(cd;mc#i@&%4l z@l@MH$CsPbLc#gbgvnRKffVjnqI3(V83rWi@pBC?N`m(MNH>XqO71XR7NLikEhkYC zh15} zNULe!b-ovD76rp;X711A88RtGPP^ZuCo&pP=zuUC?4>DPya9!>K^j!XvkQs%jf}?9 z=_ECuzadU;1ZQ&tqxeL9{0J$ER0@v13;DpFrZ^)*2J?*=Dwfx4WzI{IGE}T$bL@ql z$ySVDCScB(SkTXPHU<%XXa1G&0Y2OTB1TN6J^?AR;fugG(!W!w4}}MsH^tkcD-$v?Gj>TbPrPf8W>R;x)h&E$|8Zy zBy|-x^z2sA>ZAicLyXR-2fQen=yBMV1HwMN^8l0?%3(Ht#4K{``)SN=bKGs#sTszi z@74!j^p%gi_uAR_{P0IF9v_r-S1*q84$~zpKjPPNrJk`rCA>1hQ7*w+icy`APbJke z_~JDl2ftI8}DtU@GE zczdJWUr~=klg7>Z^yT02xKI1)Kh528F?RQy4PW&4Zh7Xj@4vqH?y_40=1)2(7(p^s z7+%{MBo!lw0J&E?vkc*Up;drK&hY zpk)CEIMy7|>50Te_ieyV^>T5TKJxzi{@3deD>ybyF~B;mOlcass=-u8_AWk8Bb`w6XD#lrBLY%aD)CPe_dcNl)BV7CU{Hr?O6MUY{O*&nw>j**O!Y`@}jZahD|w;H!)u`7x?4gH(Zn(zEi?>e}AYu%Jv@ZWR0Xv&=H#?`RgQD{7<>XvS%;$yNb z;b=;#d(X;|DBI)ZZSnxww`{ohlnaMozf07ZT`Ms~+mS;hBwd3+5Bo`Lom0#ukNCP- zl-1#YpdzfzoD&%J1^XckozMo%PS`#qmW=^oHt!T3)9sDOtC<(kieaa1yW8y= z@JEWVY?>O@_vBr}C(_6thoPW2d6eh~jHo8eE1Ur_9`8^xqeRgxVOgRAlxh52*ot*wUVA82k&Rh^F(w>@ z;WO5IxI5UJUveHGXuE1N^;u;9lSR7DUjTzYQc{DQpSj$z?`!EZxi6-6-I4cXh! zsEJj!ru2CHhjB!dA~LUv`%cI0HZM@s2NWb*iEvevq)EpJ%PSG6nqtb!Rl46T_20Z> zY?AYR*xtbNLSsj$h15ad6hKWz=%f%Bz`8q9HJS9{BOCoZp(-)}VFX2Id?}Xj+2kT2 zi$yACQ>u%iN7Ps@9`WE6Ld%ejy#W<%ruKLOXcJjyC^B}5E59F$a=jj}t!b?ngqJx! zNrfzvlK2GU;p9jue6Y3IYXmREdnTk4{wKi@&%L@F*5Ejgc}Kw*z(!LoATg!!A_}2e zY#lWZo<)a~Dwa2VXGP_vRT`bmN?CU^5QBC|v|1Z5zXS!Wx_oJQ`|THpF6X|(Bu9R< z?86Z1MU^FXPVTBD^q#_NbpECLPNpigkZm?CG^var6NP{-dxTjt@cjwLEMDEvIr)-k zp@RR6#hKCLrG+*VvwY@e*uzMH`3#8BpqR`=-W(nGQDj+u81w)Ye6oC=4SYNRj#ysp zX0tXw)D3uw?X(i@mZ@;gZjh=^G(^p4*;_D=b~ZB8&}hsUtKs1#)1hFV1%63^$!%2> z$KbhHCa97LN394O!UoZL$An(rakj~}9mP}(YSZ{ZDEAGcL!t(186<(SVn9nD?}PP( zZ)LY`V<<=2bn`Qz*TKa}1sX(db7pKx>&lnF zZYTc_n*Jz}3cgqBF_VZvnvBmzkvc%JtBmxeao58!`wXYjZO#lr?o?O_!tW$J&_D<^ zfcrmLl-ZHio*(MF#FI6l&&ZIKVBw~v2Zp}iLAeQevwqT@xZ_l;rU~keOydM_>e2_u zNhphwUEC_H8-86ML*`&8S0qw9Vi5@qh`@8TqxzJhx`mKtrgE6zs)@EHyZSki!J_Nk zJDOp+Bks}rg-IFawtHD|UWfq?P+@0vyI`JQg)|*B&E~`HA!yQ?{$NgIof4T;wj;Ns_<|0|HtL(??Ej|Hke2awq~D zO{!8;UN}rQ-`GCrwsh-F)gn#1ejF!ku2mk&VOKW`ZGkE?yhrLy%4#tU5FUC@Asc9E4r{Djvk2vmjyKyjmJY07;DA2UTpQ`G* zZCTXYarwa8m*4WW_xr)0_)xt%zIfPu`#*i^aC&diot9%)H;I^u1RS`wRhcNE#Jb0L za72#Z!R4dx{GLC%Z+-KHgK22mvT5>mXEw9RW1hnKK?@%3o`x+40uloyu2BY?T%Cga zI_sIVje0|H;-eZoERitdGNk9<=zp&w5bT-It0Jb%F9i4&NHCbck%czYHMj zr=gw}ZU6JX{;~D>^7s+U#L&d z`bO!YF2b)f?$Z=Z{CUyCXxfa;JXP=i&<5rmHM#w=l3_bEVGJkTq*@q4x3ltBN!hcu zE~u8#k}_nPWL=i12IU<+!L5#U6(i3)9}vfUrqh~>Va*1b6I4Px*9g!Ok`M!lp5+wJ zb9<*+q-Yo8U%aLM`Coqjmwf(%&#&&LX$#k#n$$ls-aJ?FhR#xB=$oPHHq|2^w)#h3 zeZznLnR^!Pg+;r4*-M_h+um1no3h_vch{&wVbz+8IwwM9KsgqR!%H`O{}27m9VeHs z+=y_LaR(n3KpZ^)NOmBCpu!$q&Y-eJGZUD0cbp%oLsPR!-Udxz)Df!3$_Rg~#MVQN z8g&JsDr#uTiuv4OD5OCU7bUX;%qZXq%%Z04Gxq;$o8zHt5P$8QdGm&CGvMiga8lOq zibJ2k2hkeDabXpPwrg#CQU)p!z*qq;W|j7h)Etwpz?b3Q4R0a9J3mVU6gmU^fuMI+Ygm zG4cz6hbkiUGm5>G27zl=Udx&>(#I#tBi#&{jkw#<{D41$Hkge!plxi?O19Ow#(aAh zZ5auvMcEEzy*j?4-K3Zr6RbRicBU2y2*K0Tg|QR)oT8|}6-fKI$zWZnSCPD#p_YS` zp_}tHPgn}%um!13nmH-v$7@_pS6XJi=sB=sDde4^^0Mi%t0IJtHVZvQy-j7S@vvK5$?kmQORTe3l0&q zN+oib=1n#5TG|6^ozv(-aW-M}Q#&lBf(sJOea-wmmp9`o=;-{n*`RRLFU zw8)A;5+PK0x(5Ri4&c)D-L7tmkA8f;+mx#VJ?@+%((p1WNjD(+YN(L4afxCR(%g8U zJYDopj$jAK`uakno1(IUl?Jol zVi+q5fN^BI{Fnz3ou9_-TI#Ysjku^Vwh?(BHL29Bl7yN)H1}K-%wPf_-ik{OUcZQv zV3Eqma%}*%#4bgXPzFwXr3i4)1lKf-m|dY+Boh@=O_>ZuETAL1Oi2kZN!wj(a6xX1 zX!gFLA-V|56`!L{Hg!9-hj^o)<>#m3)U+~9vLmpAJC`{ToCJ_LXs(=dGVtSRJh{`9 zGh-xL(Y(z2?pS-Uuu1C-_Y{UX`!Hy1oJ56`CQzw)IPV5A9!|AH^d1rqK=CWH!!`+- z#E8tL(aX#{@h}q6&_8xA%Ut%<91C|`9)v0;T9eQ*n)Ts_75@IZ^krQ)7p@f3*q@!m zo3Yo5?0N;ih!-8k9{O0GS-PuX3kVz&C0c}ZiGra2FE8}T^jETMYP5l_E#)a^D$k-iKL2N^FB*#!@P>NFx-@Ey{<~S zH-Ezp)pRH#{>N3t!P}y(7K>rKQARt*7qk#3%c_p2PszBNX~Vy_DuzBc*n{B0OP)C0 z4tkv8Jl8CF^rFyn$!UO$SG}C6`jS0WUc`#Y5 z91i2{G>5U(NI5CvUCeGK1{Tw_I&3Z;)epE|^Xw-de&J``^r(j}`flonMccN+<~+fJ zO745WPb4}K>1LezM5HSfLzPd5U7D)HfBWrE`inRG<<Ev}%8 zslb(SRFA0YGMcmC3#Of-u|>bAZiaNGnsP@P^U(>qgW+H9rm<@C)Rj~F9Y6Gkzxd;S ze;n@xpHqHmOoSBz#XC!II}c@o^ZL-8H*IltR(|6PAM;?=k7ws-*3_SpT zCDhlJg9$QL5f-c@etY6sfkV2rjD48ReV8`!EJqJUC9((sqHrQZ8@_v(wG6v_ww}7} z*M8ljZaf}$rzcIZ9lJY8zQG%@Sq$GEon5YxanGA#xBK|nYkv2=uv<8S8poPL29SEDTl#uHMiNIKFZ;+gu4osl|;$RrJ@l~jrv(Y zy*I|axYhq~hGxor>~AQ@6mh|UymuWw6mm5VuD4nZxcdVe;}7b!$BFZwAn%dT8r?jv zxg~m{K(PyAk>^7}VIAFW_pGN~WSs%*)^tQGokd|(31(fbP7SOK{`D}9fA^8DD(Wo2 zj+=ybeCJm~4oh}{4aZC#P={dW4{i7u@9+l&4U&l>jVZm*T=d`x<>`r>a`+_#&4q&m z1b+$w;`z-;S8>ZYLvVS+<)F$*d9n$YmjxBK;$f<*G#0~hvHTA|_2Fkc`Q}@0Jnn`~ zoi{A5G!EzTNMu*AHmatPE~&#bROi>G7r)?vfBx6^{pDLX-~Eps@__sG=T~>l*kQX5 zPypGnH44N5Qx~>zz(>ZRY!*kC{^m`0{oHR|Jv_S7VQ)ye?^0bL=g&S^f^S1F=$SmF zAyN*?a|hc!)=usQY?H(_DbH3wvB|X_J9tBg`oJb+@f4A#ZMh^%blD}jArrB99sI!rJ5!8iQL8}ji{t94u>Ac@xx=6^oLxq&OTA(}Dzg#-mMG)tI&v12Aa< zMsHjl<$M&#mLc57t`Nj1tPhfmbiMselwTuT4cit$Szk0w!jJcTo2o}YeDS4{gy>CW6Y(}*gM?g0fxTTuOw#SY5D*z-}v!^f};gy=>O zG}oOzIb63(9%ZuI*w4AP=-xF?#$niyDv`&rqkZ^LJn;VQCqC+^?|0bPuqoU7-h4@o zGLzir-2te48>gx{Nbmbl*XMGj#*CDz%p=`hp#2^29q7y>{s}01bB`6S4zsU`dnL{R z9J(`iPE02SYFLz0KMdq!kP9HO8^Xg#=pVUR=s=PfWCSD?f_o0IATcA#3^ZWEdmQv{xI8HjB3$EIb2-4Jm$V%pSn)+H8pB3^LaPrAU&kl+)5Wh36f&@Cet^U{ zKs^&-X(3;JJA|7u5BCkyc4EW!t`SdJ7-vPbNjx!xc?3@Vy>+d`>$QSXx6^OvH5gm7 zy;8}Ph*+N4xnyQV$1TvxRKqF{ZL2~B{%H}BzCa(iXwk!Sa#j^a5RJ9=+WF>Z0gBQxMfEE71{Qh8tEYC zcC865C?)<120#_e$M8z&rt#_J;yuG90sE;l3lA>a2UtK8dx@AQnr+UJfqqU|<#PmT zViavQDgSd7FNX|$U<%3{{Yj#$Yws!HX1H?JR8w3zZlMvAqM3}$KSmyo|Q%B5zVz-FT_F`O1Y3kf+1Yyit;7r`seADs8c2F@hFI@|n|15Ge`|Z+zA6 z?4)?hecRW)@$5%`_RcT)tmAM0h6mkz+v@yuNbQ9&Z|V$Iy#m7a!MLDhfks+RxoJ}# z`g(U?S6#S#%MJhJMK^uhzrA~fZFE~yEqjUVMoMxZS#4_mXA@IduW2t1C+WzZ4?1`^7XMxr4SAkvWE`L68`yyA^7{U?t;zwdp;m@#HU1L}q87X%0dIWt@u zaAa&VEGfH}eBzea4NO(|h3G7;Dhjs{Ez~e1=ptEK|@Lrna7n;icdAw-=6Y zE+MyH<_wxiUuL*ja;PF?O=+A4xzQnM;S$x0M1oMnnTICL5S^f+Ma}u~ty!qOb2g$!~n?>8C#D0n_?a zNV_aw9M;HLvDk(jVWL)&x7&8JebSR|{LE)8e(TSM1|3Rb^NGB07>)4ksZ-66^^xbE zw+Q>Elk_PIIZSJ*Xb*)&(2j*J&0~GXXNOY@X`;3-4XrWd92!{JI0_{j$o_-!8$fUm z2Bvl{rzg9rv*#RfIdRxDIi7OC{MxQQF?lNBrxs;g*#6YZ42nn=m@A!$b%h=jjo?abe~dL zrN!87PB#bN`6F-nZ~y-3yUoEccJMPWUlTt)*L!l<$3(dsCj{c9;;4A>3qP@Y;`Us&htwSl6@x{M1aRQa^XrCnD|6y>pOl!)M*NcxKfnUT5IcK>vts9=`p z9Yk%z9mDjB=Q3I_1cOEhH_aTxzT)YrO3n=lsT-(T2`;F0!P?5u7cUN!()c4k@t)Vc zy-5itHqJ*;qok1zdD7m0TSGH`WA$_1UbJ@fFe)e=)F!IEh&+ztu-T5E^O-k(_H!OK zbc2}jI0nkmy4Bd1G?luZeiGM6aQy7vZ_f|37*LqQu9zI&>OJpYKjkS`cBkul#2bah zVL01!3F(g{ALgH--s#ut$3OPwn{IsP*#=KNNPKmRYwY#}IGol7<|S$*h4rd0;Bo-G z%Fcm>r5qJyCGWc)lshF*@vf=%RE!1XgGHL^Y25bXbDnmzyil*NVeMz^=W0u&N0DMy zKE!pAGi#_4GT64B5&)Dpy>(rTFz5obDpwf|V|_zqeWr7ag*;oQkZ17P>KV6aJ-j9* z1Yj+zCmwlXRC6G+QZ1<>HPn7;@~D8I$XC+5Gg#G@8fl1RlQ{k%y)e{FpdMA6r%G{} zJLJ!J)-BVpo2FgPLuwY|kcl-CZb9gZxbT=NF%+DNMz~(3swwV0-F@f|((;2n>VQdc zyR-+HVxTjReXxSYX75Oqpn?JH4HZ;zwf`E}XfvftwMGcR0@E-fXy-AHj{ep?tQt(s zNu%A|(}J|0xSRW@a2a|C9P>=?cW)FoUXnI^koC$wU7g3UM*(f0vgtY5kzG6lS5Yv|GbtZUP)*#w#-G2Mb;Z726 zG6Hqnd^r|H3?7;BsuLHlLoD?^{Y&P_jWW|Ai=%N}Ot z*&hrOUL(dr=1s`9TyF-M0!uU5h8}F3EUDtbC#UjI|GGDDM> z-9t=YS5+#?o@7XADfJc1{&LI>DJD>=8sC@YmDh!Ebn){X**l|^HVRQMql6*$9VD2g zx@`QgOH19~>!0ujK0WWi#C1=;waWvQE0TlT~D6qF_Bsz*?gCXl?~YM5}G*Hk{1 zMKf(T-R7HK_^99hi#Mj?!Z3Dv&RC<{=nH!$cNnH=*hp3yfM~CIKQR6zA!XislvUv> zL+~e$4pv_l$|{I51KF8K#!YqA(>AY4kdYcY9-&7i2Z8c(#>a}8C(mC2yn;SJ0q{7{ zhZmK*D_2dRs>sN@deHPH6UVa z9m-EerATXn`7=4~B6sc+ceJpv&pRQ6`-HgBbyb7!4T3;QicaA3pW0^l<2MaI@#^=z z=*u6_oeX1lS`HwafRHw2^g?u($-`JRGC`;l(42B}x_$cNF8##!KBX+L0`RaZg8CZm z{#Bg^$f?*?)x&^>ZmJeXmv8+q|MhR)chB+a2(Ay?4j!(lO3?UoU|gs0xllzXN(%?+ zFf-XJXvqCwixBp&Q5@iGk~6Pjs$_A7zoyZN?F$sofF23pU>#2-ut4!t1sF1uNP`tl zn>p;JjqmX;-$$sbSzfxZ5c&?F)o_ys3}65;`GE0lh0zClsPit#Ow@kltcjHP9R=Sg z#Sfk*Z2){Fl*@=L62)2MPJ$)#>x*NGr#rlgMcV5G<|t4dXiLzW9vUhuatwdo(9rXfmRC3il5{Gq`JuZre9)x^TE$9IvLP zp*b<9;y8slZszimOP0nAD%JsEkl>?jP`*pJ8W?e*<gc&NmJk%f1GftlZmQQ9FV5`nD zGEilwZA?=l&GWF^)Am7RTAd_hGSU4~6!)HH3Ai?&|5-Q7J!cwsKv(cG>RoYzSw(x< za5&-YY8lw{{qUBzPwk=^@DLJS3U6BjIW}vgmv4!*Y;@@2aIlM$wTQO5nZPVhI1${i z(5M57R3??{T6(_LSR(@L8b$?y$%ZaNc$;R_iGcwilVNZ~PXT{6K9YRE>nhizz;#{U zwkgr>=3x(AJ?+U?cH7f34^=HJiwY0Tq&)!v`_gPK0B3mghKzWf558x8-$|XCD7Zjf zAYjK?HCLY4e2R|}s^@kWtqltoI}xaVb2Bl|Oyg49r$a@3So2(GPmg!0)ilf`ce_Od zfy+^|zSyo0-P|$h677Z>PODu6(i7aWh``2Sa&(T27ClxPPliK;4PmZJ86+Ypz(HeO z2a}J=^PPJ%c|vjG;>-h*bcA_DKBH-@er>(4M~JR}g+3TFb&{cBVeQLC^=$GIbD_wL zk6J;)@|ZvqqLr@9GY(@Sas!AP4typ|95(uds)Eq&Dm6Ld= zEOl;cI71%|lV8{vnvfvB3{Rmv!kIH@W|g4=)~~}~_M?8cvkn(@o9#Zyb(cTw91mf9 z2>vv-^AGw7gV&&t4D)sO&$9@~pOXL0ftH=mZO@=@&Q3xrORc{Lq(1C)aqNz!d!Zkn zziqG#G_kPnGDeMD{j%J_D=0nLh|qpc?P)@!*4ikN1LM#O>0rL@=?zy|V+8_71M!oD zWKMfyG#qw!dM1ljFOy-_+IsRuais;s{#%Fr9F7_pW!O%@ZbItUJgOx(IEq4EM^RNR zzaent08EOcLe#(?<{Qh2Nl2XmjhO1got+UF+EctrA}HMi4v&k}H)wZIqtK7|?hG#| zhdvL(u*3fu=~O+yr)Qwne;kHBqgl?dhZr&{Z6tYtcqYXFNFQg@M z>8^dee*U+-@4fFiN!7M14naYpqEy@o3qob0;f!ntk>;~|if+3&zVrppyV&&uy%&4& zmTc^9!jxzEwseEBC;VQcGpx#bv1F1{dg;IW zvm)J`bKSv24P6EKe*!#Y9lS>#ae3CKi@Mu&_fFGEISpwX%5iX-Ig7AhYygmg{~&0^ zbzi5|(ZQSl>LWk%i}zi+c!*hK)9AEyk`rnAL>@E;m+@xggn5fKyfPclFf)xK0*9u{ zl9$xjU~-5-5XhYz7#XG4@SuiwLn_C<%l#)jsQmoTd~mlpU6vWAJZ<%h3NuXJN0JLU zcEJZlMI_`3_)tIOgM-!4;o|7{hSloIYI*T^b@{@GVJwk-Uf|Z7)DdCpD!hnZ z2`t9+MMMTS%c2jlU^C_;0)X~7Kz&@5TmyQ-4ZCvS&x4f~jNG&|B#~9M@N;yDa0#U$ zIV@}BW-o_)ToHg+qf_v15QNcuICPyhntd5P2n#ZW(l(wLdap{MM#JoKD410wx}~HhH1AgyMB9mciUd;cAG_6PGDB>p6IZJ87mBS zu$J)rh}KdsRu|v?w;zAyFMYgStu}c8w2`N#sWL^z$~wV*t3(4uZ_knM%6gPbKOSFl z=jcHx!zw)v;4^F6oHLt@&ybd2xvi!$_>#6U=d5&|w9A8lSq;&3%bSdNlX6LL2kVrF zx~Nl`>ai+^aljRWcm|>a?nD*HLm*jks!RG5+aKi(LQtdKUPp_JL%45)+n#d;?^N_c z+9A;t6)Ay>!e+Q`x7Bug#pB259?!PH08zCxRL!QyH)tFmTk})tE>KeUy?~ z`Mi1)&N!|<2=OQ6D)EzOfoNJuK*%3Vj?=iIV^uXHdNw9~rzR~|MOxspLsq#!9#+{- zWjmJ5ST3ff8Oqd835E$}>c^^|%AstBI^`-2Wg1gE6wO#RQ-y!;%4SGy(JY3lnc8J8 z7fyYzTH3y6eqmjI{!fp9=Zc8HGvI6fhc{pz=S5nf)o;4EWnBwz{Oh+N@EWXrxfi2E z6m7`XQNW2~wBs4`SmfQ1k)X8usxN-fm^*Aax#y;hI|YPK6Gq{uY;xxuBIcecw}AoDIn}YOq_B zOV?Rm!k-H$DD>2n$zUo^Z4tt9*!s$GLG?mnCI%Fhym+PoBL1~(T2jY+g0co{s-^*> z0{@@iGSvkxT>`^w=!T{$+ZwIawjaOh^KNYqr)lUa2v`!00hJ}FRqnJWk)yCJ<%|+M zA!Ir&n!kPfuHTB|j2R%70dKV-FdDG1HWW@SqLF!u@;>1C%re)P(C!-7`7P@*s@dbo zB|?MSvVEfy=Dl;fa-DqJ-^Piq^a?qzC^x- zHZe~S&C`_Y7{O*Mn{*cEh~3sloF^yIF$Gv4tz2N{GtcXKGWvX#Ok|GeF}Lt)dpx;N zH|-x+dEsyFW`ADL{$47+RGx{mXDJ@#VIGoZ8rZNJ)sB7H-$+_|nb&qn}eB$~)-0bkhrzU?&d z67os*_Y&A)a=VcYO`owJNWiV@sbD8>xCYn2l?dK3lMxi^5rYAyam3@}8rH}H@0NHL zjA3w}N#}Uin^wg~wrfzGIVhW@kQxEeJe(N3Z0Rj3Q5DDCDL8(dpph!#4<^yuT;yVq zWZ=Vk`zecG79^RuY72uvUQdd+s7BF}(A-*N3)O`PBDL&|xrSoHgr}&U4b~8$$&){T z!-};o`A_l%=7_W(hJgZUX|y#Jtm*mA35FChe>2m; zyF4tG%Y$Wqa;^Q>-}m8m+SX03R~IJ}h~}VP^E?C0Lvrmowe zaMF>4dR@;J31T!~V-O&71RP8@Q`C&#>j9bVKYfeHnZ#WenHLoVQ#tu3_|jOOby_Z_ z_rAaT!5{nE!%Gk926%wi+^=Ew6uf8V#t4NL&WG7tgOh5<`4D(~nk;EEAr*;ubIkLB~MYI5-*1^p-$GsiUR~M6Kz^U(`dz_ZXGc7O9{eqg0ZT zgLmkP+?F|1&r2?dgj6ncMx^5d?}pvFU!T3;i*LXAhNHYat;QY-0eg$`64&4{i9>CW zm|<7KhKn&LW)@b%SocG{Ij?uuiuJwa=H6*@t=L{I)+fdKYH@xtZmvz+Yejc;+*}>k z_m$gg#pb?pdtb4>I&Dvi?Mcy{mHoQxwq@VbEE_-sMiovwCS1%&J8cf2U?#*Rk%s^u zh-yFx+&4b|VNals@aY}NEnm$>!ah1|%1Op;x4Mcw<`$tfxbfCL!(*sO) zShU^qq*t3gn{x&eV5*ViY=otPYpy?rM`n?r0T!%7D>4+O@Sg!cR7^UK)=;LRjh~vD zRW7@FJ{o00@CsH?ox5%`eZpoTXbL$~1krPh+7G2`gR713ri*Aj3-w!${0nGrME2dsLAR=YMH1y+Cwo|=o+QWbI z!*3bWr#vWhFS&T$#Wwm${eSyjskN4^@mlBSV7mUI6-`<+OdF2hw#H@yATI6kSIPKN~@7e z=L85wgB;A&GtcvZ+l!0ckuwZi6k*KEP*&9vVVsU8O7aupMyN{cIpMOBoEPn0G-k6q z8oF+Uq=-N$=~H-S3AJ*;>|qI(B2Old|0sGiIwodP1kv&6p>IB91s*!Yyqrra1i}PU zD6g1F+o}Vt?)Tji%x6xib{{$&%mXy7RVGC7==KBYiZ(R%Gt*w9KrR|QW%DTwHUpl) zVF#z8si>iWr=QU@C?gxIap+;GlZUb&iXm5H#s-=vY}MnGa<21$4Y1ER2V_=&G6UO4 zVs0z$3Ty%FxPsu;7+k4P@jPA?97%{+SL)^EGl|>H886&bNU9g<7obiC1OqL@qJIA! z`JL}PNsDFxC_!DEr*G~VL`T_MpnR|p*jeX}hWD~6Iu`9!BCEW=#9C|oDFIMGWzVYmAgYmbrs;q%F!$Exc zJnDG${vy?l=?6aYw98QEW#mna?5MZFg$Y`k`IiLNc|rktAZr0-2`19S%E3+7B{IVwb8z|+(`100^%j+&;Ly4_}%FI*nK{PQ2MIX$Ib1`Jl7IoKWC z@wuC_c9c_f(iHp5bb|6PU%yGIK^|D$Nc{)cgTMk-zA4YfxJkAGRg3u?{H9Vf%VkMR zRJ*hw)w!wGLII$rT{k#x)>=mE>h2)Ig4N;sc{gp_0&|W=f{GoGon;5syoQ*8hnPFs zpl1lAF@VjgTC^ z{4WQC9u`LiyE;Vml#z7GMH=E6dz1U32UsdVJWkDc_~JeXW}>N!coH*~GD`x&Gnq)T zICai!bs{wZ1Nz*0l{r^s27GL%W%810xL}YQz>!~^nZYbR<^&AVarbURuKUOd4GeCs zBjWXWeP%~5bF}BeQu+sNaVlK=y$B)j9Nb@3^j*3>rrQWkKuhLeB{@1}j9DaZk9@&> zM5ta@j+F|H2$Xfd#7$JwniiiUI4H)AjOiN;FaSZqIWgGqP*88H`8;)WS_@zY=}Xy5 z$`V<9TBaqbx8(Ci5Kn$!KnqM|k8m;m2RWz4cX%;$a0a~_NSRVXXpk06mk9|K>shJkdg~Rbr-*EodZ@af?&Una3Y%4S^Ko+tL_lKmYBK>;U)em{tl}9`j z?u*PnUk>)&`@FE01xV%tlMA8&&i8ubH;8!8bL_crusAc*SVj@Smy z;et#zrF#{0`wc$!;l+a=dF9*R`Jv;oF3)n^<#~F{HU`o}?8yiZuThwA+-HwJUNs#I zlo5GRqnfb=&CwB-~s6ip7-dk+tzRb z=VjvRqDhEgdjF`O+9@0hg~^ti-AACTNnMNEP4j2fl&hDF{h^<6vk$56j@y<_cQu>fWJk31q2N_ z(|9?|JTZVQr(IP{_nw`8`-?xJJ?eo{j+=7qZ5)*VF1V|Q{?J%BBdJu-AmXrCRQF!H z_LpzUO+us;1Abx?md@FblL&6wo-}Qiwc$Qllg}j+;hfYEM3dNF$ek8qjlH|6Q>1^O z_q1_OsxaIgdnD0?R4#US69+{#rxG!u2(W#`#D@0g0q@=M#U+WIZ;ZGP-k zcN|=~HP^?vTtbT7s1TMGN|?B_Sn*Xzsie|^4`Wk9bVccec0Rz=sVrMu^}4CY#q#jV zl~?@Cd*1TF!)8$pb(>bJ3?>Hrad|1Z9Oi+qD>6Gf=wMb3&Gn5Xk=%(HC1#fJMlkO; zG^+ud?*~oVDuY6WiD_irMVz*T>@t7g^G*y#g)>(S_G0X6y^Ti(0DLXt3kkyF%%blu z*9%%Pj5~3*x>CTdM%Fl=AVSi53}8J8Gh!k2KuAepM7VW@%nSa8j&ve*DjReFaJ$3! zndn_SI}XN-F?vkMSdo-ff}Nf0^3{EDZzq6nDYA-=@IsWTjr0_u6M=I`p0v;1g~pRx z3?LOr#5Da7ttE2I7%3)H$*qHIPG&*4@y|$PGvZdkq(w(Im0=bxs^%pkITEh7IMggo zh=DW=<15*`hffOJ_VDNon8l;AA)1DDPevr^ka&E`JV0cinZ`5$fg)cLDZ_c-|IN(m zCTLB#Ur!{UDB&e^_QQ1;GKdZ z$`tTT`5#WU*h1Ajo1!zxpf=KDG$rh-Ji*5j>cDC2w$(76oOS>7Yi_@IWz2o9#=b$? zA`PFxP4irG?pZjh2aZVzJ}|MVneMx~dBfYrs=<>p!IhGxAZg0n?RiCfh{$n-_^OdW zoo2IZgDTh%mAgKX*QfekKOCN7_)!uW*(hJk89Mynl-l#!6K07mA9>#!ZG?absU*(#yYg(Nu(y$M zr0{I`qvu|R%=&pPeg(0JF+u|}hjc1&L_ayqTvB)GRP4FU_lg!BKq<58XStR>##8qu%iJ6wK z(Kq||t1=1XX=crt(i5nvU9_McawaF+AC>izy9B<->)_v#D2=lRWnyzZbJMj@nNm`f z0h+*tWhXni$WEKFCqEwi3bWQ;<+CiStl#DiBdacFG4SqcEQ6Q^?5^_lvC*1N2%N_u ztyc5wDLyT#i9Xs}L@>o{539XqrW4su8=Vqm>{`L71UQS!Qd!8d4|7P_M#un)eRB+Y z^lfyVaN7hI>xLoGE6*4cTE=v+M9^1X{q`T;S1cjeOU*J51I;-F2mzOqw8F|G2?deu zyGiBP9v?sI;mvNlQ*K^p5y=n+<3O7!MVmI|pq;n@SW%v->gJw)o!f!xT?}yYd?n3! z#T7OfL78C&AFynSgKz)7KUo~yGS;iQX@UK6o?>@kGFotSHwn-W+_%vf3C?#QD$18~ zfSX-UE)*1(Ky12Usu#=S3vYkh-LHJrT^BAKt;cb@8K~g)zK&ajZUEJcHWl-}*q#bK zp4swY;6t3u$Bam1Y-MEi<-2UK$y95UaEz@hb6t)&S1BrODwLW1Zuk5zdf*KgnsI$E zx>h>*6T~BaN(CmZxsiM$To_9QY)SUvc-&+~hVi`J;i?+r3J!%)+tE|OoE&9&lN*ma z%3cMc4w}uQi-A9NpMhKqsuk^95NUb}@~}Up@+&!J=XDsXaohEqZ+yW+`o3#Y1BEVL zCs^mCl6b7_N0!DL?Efvjo->~aDJfyVIaT`pBBOB~sBP1e!ioxGFFL143~g>b0(Q8) zXpf}NJgEgJ{)selClpPBW;kW4*P7dI_D zg!%ohLxcmApS5nbV2jDgghh@`O9FMh6v8Pad{ATnA8xLENdicNogq?o#X3C*(Te>< z+M%Y*IKA*l(Vjkg){lk?t)?7A$7yO7)3RAEmall#N8kRA&Fb)=Tpg#j6-eb-zD?(% z0-;o&!2kd+IrHNaAs9F{(B>!;`hVO)Fvd=igbjTzl7_Hm}txHjX4BwBu0EL%z`LA;39FACbA#h();{R9~Sq zvpnAJ%rR-SEYB_{Rtg5EAiNh`6@5 zOYVp{7nrmomb>Wtk(@q8ITLaqV1Y8H$M0gF(ny;3&>jz_&k8rhmB70b_MzVv2Eu-> zLBJux7xs<#KCE(>@+z&$fYTly8%|cu@BG2N2d^ zT^e(Dy8FLA^_I_j?xkzjhISl^euslCu2j>&avLBd&eU92MXMP;{W+9XlxqHmTbE-& zpjre^w1zh%GndHmX-fEQl}y}7b-7&BRo3j(T$G=^}^0xL76DK!)B8P4?#Pf>A3 zDoAReY#qCL*seF@<391=>%RQK+s!#b)>w5!85H5b##e-@uwar=Hw;Inx-I_VZ+Caz zh20SwImx5=OJ);uC*q+CT}I4ZWw|9?>y4epYRV+I>>faTW*A% ztIRbUCC(l3{8UN=|1EB~`s$!S1X>Yed3VkloreFDHYU@Nxa(+?5q)?#5lBQYgR9uQ z9Qtb)8W3ah!m+6^Qi2rWmeG_@VMHZZ*F+}`;0*}j3KJhI`GUdbpO(=_ZV6@9uX zZYVU^-?_2npVJnCQLiEAV%_MAtmvZXqjfCK(O?463>nKVnmLR74RsvavNYQW4W8_Z z1E=u$VhaLMO6KxN&`l5?^hcqckXeEy6`GyS-XUa32erd59RezuAh@%gn`$Q)L|JC^ zVxGfWyk=6Y=1bm{gMJYdSEE5%Z@vWKPC+~){1I5b=;)d`sk&?akh;8kj-{@fh5I1_ z4G2S`l8~Hu@tKwpmZ)~Hm_H|n@iOOkhHBVV1Z=i9*O+GsswoXA?G;cl-F9WB=(Tyg zGuMc-KrK4zz}J0KY@QK$r!n3)Gtjm|W{_9|Lb~dNjj` zO^YL0m#ADEf@T{W4mj*FW8q*5|EUt29t>BY%>(-krC}!RIGv%>_5Mx=rAU~^8=B?i)RvjTX4JTBKcN{1{T2J^FyvvN zHq%nTpaMyAr)6v`*s>};#8DLl;V^(|9=z@deJzj#Zf~jFgZn=A!>*fdx{|-(vmUzX zhqBnI`z10aD+~=aflBe|mZIL{I|Up%235}!8P19XnNO6yr!q^atoR zH1(zVj3;y$9@kY1J_c}Qlx`*U7eK$nfSHOkt`6&EQ!dJBb8UC?#ohOP^Fub57_2^^5< z*@8lY=`p|MHyx&W=%-wzqFpUlm%jbwZ=RY<^`ZdbII{@R8B4rOuYuVIX)yq+m?3S8 zd`WKY5}AY$oEIp4Ssn<1zutO>csA^^=C?6!=sp|?7`|_LL>xx=*4|G#{ z>~w;Kj|v{ssQGmovRIdF)4E)qGxA$^q05JtpyajZ^mp~^%pzQH?6 zX$H8l*F%*I192zB@Df`x4DiGFY$g^6dIWr;IRx^_ht^+&LxJz|UWdTnZaAKIPLjm6nx&^HKF zA}QQ&HgLS`vr>#sJ*6%s*!pQuf|2`Ja(r#PxX+Thlzf-3A4#I(+2McQiCT5xlQtZ%`A zk?88b8^)CCzkOHt#y4MWnzH9CmTtV-q`>gNgW;xtC~#E)O6hkAhWB07ZO8TSvVZ;P zTW^^*XVYTp>#0w0fP`+&5on}(0A*AEn^XqBYt12XGZ0|JBHph& zx0kR{Tnm8}dQrzisLL}gI9fqJ>Y=o8R)tv4(RuL)ajDE$mMwscOB9{WK?e&#B4yX{ z4RrQ7pJF6VO0|?H$SOj;`^r1Rm`RYlBBWv88mpqktTQ+nmWqVW9p55&Muy!;Yl%oF z{roJ$kDRFeG3U34JR8|IdU^O`hvmYoD6oN0>`lRXox4_^)jI2fIbt@8&?ALPlJ#H) zaV#J0xXx7)ZC=VVMw~>7HqWGak%Z;BJ?hNV1K2x%NgGR>$*+;04@n1=c@>(CU>^$C z=yTUCTRF`TLQkMC#RFflB{AL?gyW!j-HyFEhq?lvr}ntuq3Yyi*&NdH~ z{tG@Ml0xYY%_1Uv0QHBqv~)(}JdM%!mWQfYO3pM9FJ31tH+%&@+r!qZ1gkTIX{uEc z(TYesWH;h9=o%{F*|}r1HV^|_gXPd|%sMU;+NkZY3`{_jUWKYT6QDSfW!ug}7?f<% zy%|E}hCzR2BM;+GJgW9;Ec5Ev6*C9|1&aE!U^b(69&%5MY^iG48RqHU6Gc&xf@4!2 zwgE=zX0(=UAf@Tr0i?R${UL$n$`YwYU3MgtDzQOA`?;0&Y$IUV3Vh_4E6`%k~^&F^d$2k9Jcn+oXz@4=d$sT_NdC*?c< zIgpG_x+bV@BX*l za8wLulDsMi1`{8rU0?>yk4Hew6v^1Aao@~|pjRa){%W$|G0Fm(q(_)8h(d!~i^fC6 z5ErggBuu8z>0{FXkd;xX2G=|euGvCY=dX=^RW9K$pl#PTeAR>cUEfw!(~k8*ZNJO~ zg=`x3ib4TbS}yo_*idc*slbPqV;6^~>Up?tix{EpOwS52vI(^vZ#1r&TVZk$4Eypq zP|+rwNd6901%8TDGu{kq5ci4%_Y656d}h36K=W@ zF&NdjttY0eJH1_vI05`|;zSbi22Kl^2Rar*xvUQk-}(N#|M*Q~jr_J$Emj=15k`fp zq}`mO;g$|XLky=HO1H)m*X_ehjS(uV<5=jJ%w{}IVTq%CoWzP;3>yFAmk{eC>br4p zrO@$yaIQsvW;ukjKT>d#*g!IPnhm;~B*nch*Hc;?T{w8dd&d9#Ki+w8e7P@HW!>@v zz%tG_Jn2M1XZI--3KnDQ_?lr13O|Ud&h_%((k(yz%kO=|+eWl4MN=i@k}!UuLe@Oi zVFS83nFyE=0_{-*vC4v)bPSvDsCyU9-zMMO-}XHWs_JJ*j|M~;?S|*lBt)}OUX7>-7zp0p$ryCt5t@c zh?FB1)T(7^vd$y(C)|h^=WR&;9=+ zc-1b*d;X7th(n#v|B#`;J3-@59jZD+B+0# zPPt3tc6)wy<1LFH`0mHUlyZ~Pv`Z~*>jEf6nxB10i{TP0DB0wpBbj{w>zU;>t zDy^*(7cW&D$I!0Z78?U*RHyuQfE$F%up2PxlEepWu4B`{|A>T}p@JZEfZH`qrDc$W z%bN%VYkrlA#S$s;-O06KH*I#?ANYSB|HLP>o85*!TN6xqFa}a#xK|&jB&XYprEPhv z^3>L;`q-VDKl<~oX_0YM6jitFvFB7m*MhJl;|pHrU?m8nrs;=ZLvzbLNDF#G*f@sm zUW{R{qijb;!~9T)$t9*&IGhIR5IaodS=qx+vroPYlo+)@enFrRK7lN!cw| z;B!3pAtk%M5A|ju^IlbtGX0o+A0q8kVFe!P%S+Thyubc#829cO+U;=$DPobE%$~8TuoH-(w(6|7C^FWV32Cznmp}v(oZNQlf%Q=mkVXhx_8u3G0&-0r1SUV4 zg8bu{@T|e_tHD{siy7LTr7x0Ki-T`n3a=y4f?4=sCrdfq8%qxshueQ2lVJ*CJ&$Po zEPlgo!MK`}MN~v;W+jxuL=O`-LK6_z*}4k4x{28z{ug}aSIHC0^$pL&*Jgg-vbe@yU=Ek%B zQmwLqdRdf&$imhku2S7aTc%^1Fi)u{bFo3K8hTu>7_k`19rRaz7pCsm|0n(Z$O!1E1>Mh6F9NRT5qxvk|)`_4V_53}%?y zYR{Ur_4`_x7%hH8MB3u{rH_P?^JctRK3@3tDIscXn)*durfO(XeeqKHWuN=VE)PY2 z3h@YucJhnUPES>*TX1Jf0=94=I zJ(J|e(zast1|bWkMu`rZ@H9cleGh(gkr&H)*;IAEsfNw@$xxNsSHA3tPyM9DcC%iU zeK~ZN8+f{begw;f9e5skepC=}!5JnAdrSxIs{Zf4__59Ih|#P~S{}fQMBqOC&6MP4 zZG8-a#fJ}jUZ*N>pzV+Y&5)=LQ&Awd2oC<~))oPg;$w==Qln6keriG`8t&9l?Zq*o zLdbL=TjgMoCD{d>4hNY_+8|lG2Z~3D;hJ_@w#$R#|NQE^-}pBt2gl3Y90KleWC{Z< z1tp6Sq?wvVg79i_&XnamFzKjLO^WvF_&x7E`42z-zP35&r=o{N-$XkD-e&mTArX@- zaQnvd-*g$Jelj#K?Xg>~*|nU(mZFx43PCerqByYR>~%<47?6}Iy`Vx+!p$J)i;-g`EonG1RAt==dh(fOM^Zh{G8>W~ z3hi0Q@Rkb$c318CBGHV%(NuDAsc=RsU`$1*o@N(HIw37M;u)pla)t)x=~OVQ@K*9> z;J6acADu>nSfWcSC7M73Ujm)M3=opXA+Zd3f5nOw$mHEe7uSSm7m#~lWDHMvya+R4 z&%)+jc!UkK2!qZ!R-$ z!|wdP?Wh0WH-E=V9(l4o>-(|pH+i=~f0UK00p|irkcfb)k;nN0*WpBuFIlo8fFjwP z3T96bgm6+W2`tY4T;*=uoR-6Sb3RhsGe9pnqrh{R4H@AFBNtz#Aq}0O>L7<*8 zU>6hPNZO<3_y6bvZ+P2)y)!kDyuhfM;O%G)IwnF9ll!`h8;iY9l7Cy!<>_gK-PO*3g04X1=$yyE#Q zFRk?+h7faKY<<97MtV~bH10nMqJ9WQgA=K@MosMd9>E)+Q_bG6wBDKP6hk9H3efic zfAB6Ola=ymwhj#tW%e?0;mdaoWZI2U^zb%2HRxijS*PASPBmvlDlS1jnsg&6K14jI z8uu_lAV{hv;}2)%qVgIYr|!r}w=>o)Dw-dL`{xf8jZ%-iD=XV8W2egiXt{JVvp_E zu%Lhik-4b&1G-Nhy7K#V?S43Ck=7&wcw{}Iv7B+^kf4C~bU|rp*yrvu?sC|IM zXEJHd8Su1{A^G zl+JoHY{2KG-OTMKHPyF%|KFUAx6k#mAD5xWqMBfEM9LpUXFR(zlCogsh`$9p0Njj8 zUsI2dn0VNy=^t^35RNW0Qb#RnCCkKHBd7R`z~k0~{u(0xaX8N zY?@A`e38|<))~7YmpFQeyyJ5CVi=XMi~QJG7}5<6Q+7pVSZv^-t<8COn4zm_KtE$H zXhUB;U=ZR6wK+&{EbK0M*{aInT!waG9&&e6^|n%@;mycYeNxy@LYS ziGPSlr(22QmX78S!t-`01J$*^M=4@LQ?c$u3}HYds|393+vKbeL|?*_5@I2gRxRxM zn6O75vdp1(FxC+T!LpT4IW4iWl_{ZrTP- zky9T*A5*Xb-D%3&y-;}BdP#Z>-$PQ*><-71h{r_uD~hG)KAU0}YJWJP!R$sf6hf!C zl+!X=*~Kjq;35fMK!?K{4UmR)j5-_O<%s}6Km&qqO=>YahTcOMVz-ta=*Wu!2|GP# zVQ?|&2#9ww_eDxZa;dal!4Dg$W~YH`Ni}xO=0IAPa}d%c2`q?!$xjc-w|JXOEunjO zkyz9^P=?M26<=Lj7OQUiae8jR4uL+E5yA#L(+lG$mB+%iEmCpgqmKxM13`0}|1tJb z8c1^fWa6r-h}1-7wm6&;5_FxH8gJ61X`)L4{~RncBA6KyLNZeLXj#$$raMX!(rdU) z7u9N0)t#Vk3F<7w2V~4sjMIAPS}dn$AghwCm0F^2&T=Ar1F)9hIuL$$YV8z=9xM=p zG0q)PfEfQwWd_(ArHA0>_3$eQ9h$*|ZRW_XZu^%zT!(h_}jkrX(y+*c2Gl{ z=epkvU@AuA$`B zUCXjcU4kNq7f@6r%?S{F&aF4b?=k37Mz5_9!|Pr5$L^+5+{+qCj?_3Qu+`uI7nDai zVaAC@vo2Qa4Sb*+l*i2jLy9g#-piSO&Z0$7hc=F2+N7#o)!jO!dd$tf9*48@YSs47 z`>qfB;xB&Rvl|bBzq#L|lNbgrZzx#<|5DFkpGDE)FqPWv>(#niuWp>2{_M*i+~i!h zEy!CV$(!o4oOt2FRU4wx_Ye-XA{nn8O zp=qS$;1 z@i=8EpES%*Ls%CQMl&Yt=U9drHaI!-?`piBBM=rziG+2#e2M0$`J`?rc!gzKLRgLHS(<>%x7`R6U0iP!P`Is{cX;Mzf|i{3$!JRWT?dBT@gs4k|mgp@!e%ojnBqj_AuKB z9<(jn4g0``**3KfN>z|Lp-8!p*6f$p^zk2YOgeqNOuL|z>tU3ynIb(*_cq!8U$2kqZwhr1>7Mpa zC|uB=q^VAGyIR_Gygh!-3*Y*dx7?pEU7piz)1VQDNNQB&s9vhTK$VnNCw4sA_BXH6 zYHHTo?fSpI=yk7oeQvw@q@T}sh&|8f@0l$}MWVQV5)AU=rUi~vtbln&xJYy8IS+GL z?{FcpBhlXl4NxVINv1p#<#EUu2M*(L!B<@Z`J`XA>;7MS&in6|u^vu=7LX(0!3_^l zArMS*(L{?mAZ%G!V~#xdWb6r>4S3|weLWBLeBK}hV^__{yucq$J)<%DdK&7vZ^phE zclEHVr}KL3t9gekjEN;zHK3xDwiuF3>ay6=V$ejQ`eD`?K*g zKKap4|KFN^fOliNYVr!WlDet}^&o)k)Pg<99s&J|v~pImDfybug-l#z*QLE*Oc2wo zAnB2BMqQ5_XJe8wC|wK?Q^JaK+9a(Q8^~N~#FcBn4T2fP!skk3KM2B5S~aU}x_rFq za@AG)H1AScJ$$nNl)u0I%^&-FANq`Z>-zOPO;z9XSwpQSqa^2VS=B+qUwn?L9trT_ zdC7Hq+iEpG=OynrIqBM54`9tBZ;ncTmu_WR;?vm@bLaRKwx}JX$U-UrVL+b0Tc4Mv z@KE+RhBH~T3pAufFriQS&w&+0GHuz9^%6QG%!Ad@Z6<#>waPNhPWt?Q90HQ4%+4M{ zVFn^*-N$Cm-O;vv{X4oJ`0sD;j@Na&8B@#QXx7etD53B;Fo?@x;B1NYP=S~~2sZ1YfbpA>T_jzLPJsR~1ywOKu zJ3($D`V$vq+8&F=t@~RutYRRDSRW9d!wK8bvojmTs0Nk181{F+nF7cSXM~9gck3^GFb^BD(sKN>F548$*&(V4j49l-TQ5`{XnR-emXODxz zzS7xiZBVe$NuiJujJSg8a-N?md3bOzpM{RVyo}O%YqFwAMwI%8pR>136vM{f2{dSdmmANjbaJ}sX;cz-*Oxf(M9utDx2vJq5oKC^^t=}2WD4iTth zlh(H#{mO5=?T`PW>N<)t^z#YUzueF{ht!j%T`^2p7|)|)HZ;^O{7r@k4_L7tbk%Tz z1sNKCAh~IBn^K3ugM>&%(sIm1kuBD~ges^^@tr8KlMaWGtqtc9Z3iduX4*Hy>2!Wl zFU=!o^M^dG`i-CZ2mkx0+;QvS2f_b<*oLMY1V1(K=37YFC>obz2hC!t)6{gE_3+}C zzU>|NNZ?!wY6C4o`Q)=%!s@-^&=qr<-=D}=fas1y#7j#xiifE4rDH{)=#W7p(sS=)cG=H=^ zCSj!Lw#)-H!|@{VqT&-R3|B9w`)#I%FEPhj?tbF~7ju5CxzaqxXifYQw~zv?c;Pig zm1RybywG14R#h-UbT6C$W@ExIkMM{(CLI3!9<N8j zsqa5W`p(y6exV~fVk(ZeBbHqKzvxVC$M25_z8A}ch?W%a6%MLjL!Ms1ldAS4hVL~u)?CG zV8{~ERBWRm&OrmZDaIl3pUVrk%#UD1kqz$T0bX&9@i?s9H+yQ614=TA2v_Fb*g zhCa{Azm^dri)$ufaGR4?h}I;Zaqv*mQg2hcdD~lVKKCac=(<(4hROriIwdsI><~ml zfp0Vww(jO|z4@@@vhYmR3o4T|n;a}-7KxNKG@N*Cx`&EjgKEd-0yI5GE!ixLvqF^w zTKl})pPih1>L=d$eowxSo=*0kNy976c#>MU?>#8LiJb5hj#cOB_G4{XElB zyF=T=*qYjEnfJTAZom8s9=|&~L$p?&@~WXopJ1S_bf%W5s&eOmEHpVe*lpN6(J|pF zdY=iLTYD&ra4ku$0$nF+2V`_PkM%q?n3+xq-)KU-C_+XhH*paLI*9oW%CN)8H+PUY ztybxHoAT1v!^v`Xx(xHld3DE?^B;TW`~A0PJ@sgPa(44%wIKNd4Il`&JlNb9i^*Kj zVJu&*oS}zP#nc^lS8o5kKfnK%|6pk9Jk{MeEOS58$%8pPO!D#Z=RV12F^#!(oJH0^ z1J??n1~$Nsd?0O&T%Z6m*=UmvA5Z$gj+} zS@3pguOzQcYhpRV1=V(}mLB=A2sOQYyn4|uJ^Z(SeVU<7Sqo^wrX+*j=zwIW!Pp2J z{;I780c~97wyW3Mhp!Jm@WQ({M_0!N=tiyQYM>n^?k+DY_ez}dBg|^iHqk`}c|&CX z7;KXlvRR{%uTI=XYfhz2!Q6|dAzO(+z{?oN&}YmoN_ZJOP9k9;D7|tkW4H!mSyWle zlLglqtZLjT2L7Nxq0k)v7`F*_r(~U&52!p2hesh+i2D|I<_WK(W*8AHb`O#L6+$0D zCzAJ12og*OYZADRcw%s<($A=ZkD17^HiD+1i!mT{7!yeEVr<3$g3cHfJTwD*;M%ml zMsYDh&NVknMSWy*&JfDl^QfADYCmyhXNLF7U(0bgGf`wOn?3=WsathnjJ zuA5Fyu08O%pZ=tm{n)2I>9P6RwS5Z@=hJFB?Ybs+X?xVtS_raBa?lJSthpw-1bo5PzhDXyb6+H-b z)^ifMe*o%WDxAPAs_ME+(=`3(AAZL)t>E*T@sBWYVLiop2N}E2p2D$nBqBmGPQy$N2n@~nQz$iwuypuy zT$c4Jb?d5arna4?@vI(p)qY?1%h_4o=Ckkq+9&+tkA3`OAG_STej_hqGY!oOkK;&J zBU~k&(MF;$xzNDZ+Nh=4@A|1duGgD)z4N~R`V;rHHTW0sHxV@zd2zPMASFqU8&NsV zW)!Z;)foM-=Gl&63&pESSmUcc3u8_!yJdF%nKxyQnsENU;6Zc}aO_zjFSY2d= zhnqdkuI-CMLc1P1A0F1(A9@RH5DN7r#D(ysNbxK*ahx@ptg_sGuLRBT-8B>vMi3hF z=nF^zNUOxs+!;tyU0do&P3HBy>+P99XZBBsSsng}ZB&~rC3WtvWsGdO8s}mmvxg$lNtF$AzE=Z~=SSJ@(A9I4ksm=ekKLovM{Hi70&Q1jf zs|M$5hUUh7FTK|<2uTjN-$R*;h)%SGqKh~dtC%YUi`j`1yzaQg@}W2wQWJdl2Q|E) zURKIkt=7;V`*>EnVto=8pVx7GqA+U=us!@*;_=`rlx8s)FJ{_$o0gxkc^nQS0hLmT zEXog-hSoS)3Ai#oqJLIpqYBU3Aq@`PnzO0o%f>C!YSi%=--Txdb6M0h$)DJ$hR1L= zh+qXxkX1U9kP-%164WSVsfk|B)l4p^h)mYyvaYcmK}?9mEC32!EHwfkv$ilmE>&>k zPmmxhatVon1~>+OCE-J4SI}!v=cEBsF-METDW52c#=te_=Se9;7bl(+dq3d*9S+{P zo}`4wSV@2qY$xSsNx#vA3&=458w7OI;bvq4UJqs0~ zSG-OI`FpZ%8>_mXKnU#u01(N#o4X_uslgB~4W zIS_&L!?-z`|JDEbK@f}#*Aujq3AbwMaox?`;S@7vIA)_hY<&VCClixZgU!%DoLE5LjI#@%T zq|wfGHRLugW0m^-?ri?dfBMA#_TqQH^TDZYhp}m89)+0@`zmIAF^Yo2W=1DFp(+T9 zxCFAXGt!Ih$evW1G#bRjGFbszp>{sc@bN}JtguEsNxYF0xDT0LBvsuZE#N?0vM4=T zu4$eJ(n@zDWXQwxl)IXL@tIHhg3r9GTaEkkz8aS`8R5k#0IvadgPcy-Jqv{OL<>`C ze3brl?%H~Dv>(s@(+lq1pKZ6BwrX4MB%wjS;L^gKZGt0Bz23Y7 z^IkHdo@VwU^V-s2hHHt;WQjNN`zN}Sad1}xhOpRGQNfo%rzG$}H4>C*Os0+mF~&ZY zx};i<=)1Hz&X$0zDXlJDx$i$il*unjc`y_X z9yl8qbQP4RX&6qI$2l#S<`wDQ;pi_W5V{%AM^vp5yX64-t772*lc(rG-z_>U!6ia4 zhPin&t;L{v3?3-d3)xQ^=k)|^3zZlvHX`)g@*;W$y^xYf7!=qjeF2EzJOR)U-v}{J z7ktZDt^jRePowgY7C%eM%{Tz6$0DSp!KU>J)-uW&lNUAhYvEjq&d`y`akXW1EzT~* zHWH{B`eeq0LwJJD%>W2oD6pC?FjpXfu+4|7H9<);oya{X5_E!SU)tqB0`2|d0f zRzf}Y6V5CgXe58jPt@34z1!D$le;|r=I@^V!mr))8UN&QXAckKcoP&Wn5hcllkrS| ziyn_+mEhiF9L2-_bk)sgx5kh7;K%&t&wc7MpZ%vl{qlS2dAnZK%h@S_;`Me;3*L!X z7yvLVN8Xam7R#etG|3cGKmt1Mc5SLR-RkDe^T$7C_nc>b_$PnTUAvQ8=ey~st(NH= zX_Lc}T9fmE8(=BPEnM>sVSUghHOnyPZmL&Dw;etEd4Kbkx3sHvu2yTCpMd@#p%6Xn zaUOB_!Eok0chC3*t7@Jcz)-fE9%J5^Cvt0{inYRQ)hN_O9VyeD-6%@?U-6)!SFQ^IbKK zE9PjVTtUXNOr-I)XmEizQ78_APsU5&$RJ>awbqZRo!ixR-9Pg=Z@&NjqvLj}+ODcw zXnJwSTtITKhbO8T1oj=2sS|PFsNd8WQa@&b7aiIqUM;Nt7@6Bh$xKvtpeWTtMy)Gu z3t&sf*|eGhZ{2m+2zXGcCn;Wz?tqP_9)B`@&Vgg6;5qFpwbBk6b+39Vzt3 z52BdD6} zs6iN8;8<}trwX^@FzKBh09uL%oK5iuOr!h%6E zD$@D!H`GJP^iIH;4MVVV83!@UCV~prhMsJkl0L*INU3C*q|?8EEeaS5q^;yjJ6ux; zLE--d`_w)oq_=xnC~SseRWc)J&Q};m;AMFL?kO%0(X#Giu5X(xECmj}r0bMgOHYP8 z3#8e$#>&_SKbFr`*1_nK<@loXEZs_zRB?sHd8Jy@mbjthF+}1kBB_&bxOyI>W*3LT zNQOW)j~-Zpi_}1>w!EO`5^|vn0<@PmgL+c-|Cu!kg=daa7MJZnGC_S5kR7%*dycX~ zFHUSM4N%cS*fmc)^N=z{BR`Nf<=<3s*dU5CW$qt0N!cD zv|;LpG}q&PJ|DY>Pi}nG=eM8xxlg`v(zWBR0hwSdS#7f2v_nmB%h)p}bT4&Bb>PW8 z_rb4C4-W9RjQfw01&|BS=!nuVf!qRT3HWhdg1XD{H*`q{< zm+pAo=9m23TVC;+d40U>$GYAlf*aJ<4tfYWoZwax25Q9>8;L!Tiq7#RiTJ{)WpHNb zkQ`&mGqi-||A`vjvH}=BC1kQ2=#YS-n#MrEs-;bJTQAplyU+RbJD>i6m-lC9)o>=Z za=r9A5V?};oLL#O`Zu<~;L<6rHtQ?U2Fz)xJ4_w%fY3P|y963VenjgPyr;trMn#Tt zg2P>cTLUydlt{<1ug;amnbRKMa~k%i3#bI(3(yV}?K>$CQiq}Izyjh`q0+osrv1LX z)P3c@eEe5`=RKRF%W&V!9V=JO$}Oyb)8Ra24TabZ${LjB@yiU=wis36P;!`i7|!Li zlT!I*pxGFdJ=MIgn-xQ*@lDVQ@}{D>8?m!YG*Dsg-N-$i9}MsTE_Khei_`O=s++4< z(#QRs?*I7Y$A8K{yeqA$;p}`k9W!hx`)P(RAO`~(@C>{w>uNx=$DQgR_j9JuSV6$t ztgF>+>nlg!`Mfv$&Fh;rc(H5ncd$llZz`zOwqxHluP2KY7l zAFgI;>L4&$>N%}9$CrNR_ul!7|Ihi+)ysWVk8{)S#}4C3oag9~Cu;Rk7wfSg))@PV zXBr2>yj5|vRDhPN1CDBwq)&V=@*dk8d9$DyNGRRr?;q0zvhqs?B4 zkRFdhhltz3jSDf9hgqHGFuD;W9!!9`Q7DMbiZ!m-RZwz>JRDHcVD*_tD*rX%&yueT zFO!KSrtI*@VPZ1oo-7vSJFJVvA5_6W+t?+ipMFjAuiK zsA*IfJUi)EsstPfY(sy)v#@apY=~4{~4eB zK9{bpcejS~o407msrq@IdLRzi=vxjd0erFR5z?=!TJ++o8T&q^Rkgk2_)32HFTL#- zezo7W-9XtFQwHe2rz{3i+G#2$<~oio)umjf*ze@~B?pt;-TQzAPA9W?^aJi)m*MVDnyk*4Z6<*w#|cSKZLK_a})4QlLZW(s2? zU=b(gOIU=kfDjN`Mtf?{LoZ?QSbRNC&||`UfdY>T+?++)O+`M1>H+0y@yIAtGV$JJ zN9DeolWN%@+aV(C=Ge#w1~aKI2FuUsMeK|5f&gj_oOn~x-xjpj86I>5!b~a52{g|M za)44a?TW9`T(2vQQjEciu&MAVjb4OJzcfucjl!x>KXKuv#x;)>V_ya@9lJk^#_XGP zL7QXDrr`T}AlVgrjNv;ZjzHDA;kFH&O_NOch*1yUhLaVG1xQ~+trIkg!@4P-Mt>xY zu3b6=zi|s<=tz9uIP3~|bU_Rg+=eiZC}@j^7xCc5@0HjBxu)P58fB6tTtnYif~;s> zv;tA{@t9D|mxKc#sm9YO9~4ndqBkr~(kxxHU?g(qbF5=8S_l`>q#MbK2UiB~!h-<5 zT~dNMB{cj-f@h((W(Q-6VPGgaGIUAkF(uBDgHsp8CeznY&nh4TN)B`(dDO6UwJW-x zbQ;sBNg~l3F$Qfjrx~vYba>cROPZFRmj1%g^`H|ha?#3ZERh@J$*LZh#&MX~kxejd zuB!2DNNwAX%QcwX%};)x>(Bg}_xV5m`BQG*T6NW&n;nL797? zxXa|trDauBcSMy2R$~TwkuL<~{Ge@qI72d%Jzq*Z^Yh`=0T83H%6iv$%-IrE1wO znxb5f6CDn`k|U`}Rty%VIYUou4ot9uZYw8lrcCLH=QLkWO=;m42oAWRJ zybqh_Vd-xss8Ttdp^Y9N9=cv(zNnKApK2P$Wyw?1Y}T7Uc=dx1T(8#0EzJCMTI2mB zHsqv=oM9Ov@x~ZOapOZ{0=ekM7qiVrV4FCAX!kj9sQh~Do!y6jK-Zt2!?;;3%g~>lj(J*7)!t4WXf+pC$?6D35;-ibvPUs# z^{B_{s$OlHZMQt}N!#3m}2NjgCIMM z&6%4``YD?o&a9hxQip~@UZah+s3%dpYAmdhqvSl&H*Xx~dd#fGI{MBJ!wiZ?iwo$W2E7n`2r0hMaGEk8T`@&g zSZru=C_yb8AD*b&WR%1$jJ#7)QqVL2o`bUj?p8PK=hRlyu3u7%m;t&-#b0ctj-4-*UyK zO;_p@CYrDTBd?U&RK&Xyh31XaRFqXZh$znZ^wZAriXM?tv%5|6Wh4VK!S@6Oy%J01 zNo-Hrpp4qrGZeUVPWCFEo2F|}ivi0MXUI9sLLTfIhCFG|*2Wo%x_j?iea*N3<aRpYp^@SDSu+zVt($hHC6l4&m0#IcEcv;ys~(Z%9snM7Eknj_cY6t6-e!RlPp0 zQuQ_8@}~3M<+j~7n@jNK#Bm4r2h==fcSnE7P#Wb9X)_log#CArp`)ORhy(V$7DZBU z1=_;cwt3mtC#U;|9zKOdR6VGC-hj(R_k=Mu8yzPkAHN2|0iGh zun)QX(I0ik6CSso>tWc9yBm*G{nTY}tT1K+*Jl9qB9G5eou9_e^to#reDQi|I#4nw zt8e@EO5Swue8&S{|DAWQt4nj$*WJ-H&;2+JJ!ll<)^OOlfFKiXo(~uSaH=sxBI8U^ z#75HWd@LR$xpg5v$r?troAy-h0BVE06PPeSpk6dGo1I1LB)@sL7~ES6b0@~NPVJgO zXLfOHh|kSa8UMRgDrdR;(;U9w-;gyf`(~HaR)5n_|TD1)gN{bu>r?z+_KOSU zpqS}u1?|lc!C^+vjvP}@Q}p#sc!DeN!+;WhBm6=_R}&{x5pje)Z~4ujJOtrUrw{28 z(M?=<9s2Z!F-{mW1TW=)M-=vmqoREd3BWczQnsSyi(1p+EKGg1h%nNEG#%CXr7Ea} zDTH#vxt!Xw8B8VCjjvsF(+3ubUBz_nvQ92360yc?LLw|tv#D4^hpXo`NfezY7Pm$D z963IfwYPrOVIuJXV(&YEvKRxKZlgCMbK03PCF-IKQ%z_p?jiovWkKUpsX2_lCVzq3 zKZ<}7IAV$d`H2#_=rLCj!;-)upnO903~>{%e-J@iam(fLPq3ShsXV|it`ByRqbht! zLh`{aMxc@??WlSZTI<}7eSQ7ru^Y$308#^+@Uzi(jernagTy8i z#j-r4IQ$or6(udoQEHbP`|vk;BxeuLC=>;$@6j&7%Q@wj|HkR3eZp%$@e@9LH#~OQ zzYWte^b&M@r|+~a@-RHdUNGz@1Z}3(@p1Z3-})!lPA{+8{V;dvK$&XhAOPmH6DAS{ zSkI%fx8V;D`8~-W2+Q);Y$p!6PkB)3%yzl$EVN1xLzc}INlvyjGtqZxS_}uKVZ_QF zrdu~pKl4-W_@JlW1|n#^-cu3|t!9$P+exDG?FXgwxY?Y`@BJ*V3*r_cE(cgdp!V@rt5-CzpIpnHYWWuPUp z#~7SR*10~ul%DYD_2VA5e%zhiqi*kxj#_x859hmEfE5}TmX2u55Tzk`HJ&X;sA+Li zzG5D<`2}(?lXf%D>uq;w{qFbN_`2`8XE<%Ubu*_9j<6(96Btq;yq+f&i#~bDcXpDf zd7Bd3$LSv@q%d*r)uxF`2oNVPhZZtdvzdWpWcFfWcD>Swii1};WD#yq-QfKp=2-9+ z9b~Bx8X1(ngmK3S*%jz!(Yx~>DUBX>bKQZG)Kq!DJNl2`|JOhN{EwQO8Kdd`RGuVa z?&Q=!=b`?K)f%vxCQsew^5x@i`PM(Z_mNB8<-CJHp_`{s-h`S4Gyp*sTx2oiNbkf0 zPjgCIxo{3)xn^iuG{OphV(hG3JV=z;7fHJpKpHXu`sLb2%lcjNq(51qh?KTx0Sq z1UI3$)u}Au0Ei?oP8@l{;7P$5O=6DBIhDI5agV8%!djvnF>My>w}iZs6e7wd4LVq@ zXg?Xnl9MhK&w@5k`uK(MxXNY^O*Mi7s|<@A$my^wEsM}Wl1)}k{HV6HWX28lkFnY< zbK9iNs{Nn;&*}HQ;BUVEt3T+*y*)tZvy*nU=7m6aEH7DvY9K1hf?!-twD&XSacmTU z#8f9(ar5R0kMF+ztDpKc=fhvU?)oeL{Q7HNf9oCh>~Gwd_WOB%(gR9G9u~*q^StVo zi-DYHSErg3LK-0A z0 zaa*he)4rzLP&`gOI+i&b0f}W<&YP-hQyzE2Q{MNs@B6x^u2;BNOO+Ki3N*;>-p^8eAC}P^w9ds(b(s1+JglJliQp|O$KmfXl-jP78$PnD(dIqLpRgeJGu3MHZ30GnCn++b;Ed?PjPJhyF9oi~8 zz-Zr&zSy3z5u13ipN>yOU6?RRpYMWK)pZb6q=`Z38Z6W> zP_*2zl2s*P8+31cX4B|j_)x{A#{EBclMo-sCnCZk4xD|zZt(e|9Wddmm}P29RC_IH zo*Li6Bru8*{o@7igXsUG$Iy(0EvZT&TgPMD@XRf4p1*eZFBDR@(B9}sT@fEL-$OSN zQq>^e$Cx#e7EBqoxW#&&xG;rc5$@oHiz6(Xtyx)+dYgbjOuPvIQs$`Q{FyXa$diFu zg(l$wJ;q-r_?H(rKAKt{^eoZ41vuhHJ^VsQLph)wJcV2s#=Nj_ij;8V&liJ;;39B$ zvmdGLI%7d|IQHJxSGPbsF3*F^jJCC4ptByCS@7wF#WE}wr755Kqj;gX*B3Y%S`C#15l1iE>)=80=dkgQ)CY zT2IroTBS?d>h`Ov$33ol{NuJ)F0ZTAm0?)-yJ<6@O#RJj91tP^RRM!1G}6OnPVr9} zkMee-vuxHoXfwxO`Sts6-fX%pgr_JC$IxEXENypWx!O6^5h;p)LuF;iH!M_R zSS64P)Cw)INuIuRC^8yMS`e#CW&!FU0P@{~pVf@h*igag4!Dst3PhWjv@@@WM6~Pi zUw`rchU%z4)ng)1%X%ou3sm|qC;&kJOij054XN2)YF_Y@Z#}ubxw75vQRR!)=?BBL zA0|uihto&&Fol+a8q3i&Lmp9OhA7yvFbwTlhF_YdO`7h%XZMo-dH=uujJu}c1hXb* zr^(-o##&&ZTY2Nj4c$50{r>F6(Pw?ylYi*P?|bliwXF8!9w{xE404blB+R0-B~rkk zCW*5=blz?a4pIT}m{jA_)~Ii)wBL;%_{7!seB%?VpEz6?|ST#E$BJV%Q2 zL1FN`6pkvxGET!Z?9XnnSs*t?q?j7kZJe}HU4ur~fx&8e1dhscijE9cjn`DGcXmAIBSE5KRqE$LrxSQWTl(i#Mm=5;-+D9=r>mbrs1w= zn4uXIKT#EtF$gL$+;K-puZl+0%wqfjjs)hR_occUdRC8;Bx4LKXr|oLx&i44%);RB zkq!c&Q>=b~k>pm$a8;KJ%9$lKZP#x8^e_4s{Ny{n{PUl5a{VOF=NS=q{2p8h*pa3M zn;xsxs;c|cZMWNB|IK@T?w3w4-SOCgOl&ybaeglc+&~o=E6mv@@flEW7yw|0e_jO2 zA3(`r4nT<~jE9K&4{Y7C)u&!9ssP(bIeJ7>FT@Slat*r&lUI~d=TyQ2}}b_H5TMjwu+g=LrlVcY|O!(G1vOE?fUhe}aqR#Tu>$jf21_QTFlIcVa9(6yu@W(u>_A5k9+ffzbhBt{q{4re zwFPlCnpB&yq?Xel6c3^il*59zurn5*NVR>yQyTgRxRBKb>p$v5>GQ*Hk_5icQK@jZ zIShA^T|CnG`4lS%&JJx9xGv!rNRJDi*m&}=sKMGZwr!?GjTjE`iV$YKw9S;Oqt*65 z|IoWX;C(NB#-}{-)VWd}Khd9QRc|U8Z{9 z@1OX-w|()`?yN=-S*zUAkvit0#Xdmjif5N{f5SODPQAos<1miHFzip7Y67*3IXI4O zASnyr1q@0?(&fC9$hd;jc$0uoi;~*}2eB$mdE0dBb>9EmZ~f~(_~ZJvEnF_Es>L(a z=7@Rnu-qAgdX6BB?i_YEV z9g%Qp4EBO?oh~ogF=2n8vsDG8j;0tXTY3;2Xzh(Uk$|bGxG_vgPOc2j^x;WSa7sWR zCi;ZBn~Uep!~t~~;cKa8i1$rq1uDzSl$%F?$;l0OVSghMpW?oGFdqHBZ&q}=fg5=4Q5fB-u(Zq5r@y>q2)ZcC&=^5mGA=H3 zAVQVF%Z>pm?@(kV6jzpT8?>Gzd>lm1caLoU2m(-HcXUChz`s>aFD9s_m)O66{2bZ~ zsoDAsYfv;}WpsyY+fRLAL`JrkE>J{NqX z5U6mpKsWdWg~#I0X}qmyS51<^ry^(74%_nVunaXsA0A-CkCA|DDT885u*r)CzE-01 zeKF$JEe@!KC4%fmO-6{n5m2OO-~E-EapFY0P3|;ctYs%x6CbTsp{+we6I@YzT8%@{ zz=EGXFsT^2$Y6%>rJE(-!s31?gd4*#>LkV5f@LJPZHf#++~Ep`HcnV_(4{L^7a_{k zGOSjqpSK_Sq3wr%Bw*s)ZV@m6Jeuz1E&;_)5%eA5FKSnCU3IW~i&Vu}Eoqz*2DxLi zpSpHPX*ivC*M{+&5^G*|JWa-96=JUhSX?*}Kaj-U%)``dRyn6?Jbl@(J=CsNb501Y zVjYA^qF9Ki_*48Ph!w^bv;&J<;mIl>KS^_()6NGIr})=MYTm2SG;3^&kECMU(KfCQ-oXW>|_HmmK?>8;ae z{g*d&>C)0JL++qy%gsD0#|>j8FD_G63Hr7mGwOkxAsOYJS751*B=#Jl-pTb+CY+23d(&@nsx+N<+ zuevY&f+u|AcfaTMZVh;0g;N&dy{4H!XC?AL`?YXbHVOn$gX70+V`#H?j>c%eFA5o~ zJ*#Evatm94-8uBy^@{Cf5$qQaFHH9lDFUDl3rIelggn3?pZAz;t>l~|Y(&CY><;xj zQtgd_l|^TmT7X6xdVXbuLQyTy6J^|>Fw)JHwpq1l_?qv&`}bbCT-wxi*DZ7I_k%x{ zb$Kx=W%lN!qjs}kIeI8z-_P>?1QF4NQ)pFohiUzunID_B`LRD z34luAXdl*Aj+GWe${co1>lAUXsTUq~bg6<3qOFG^d`R^$NsI8f5%#+D>jnF|&1t*Z zKIg~p`G%-JJGVY*jUnWcbh%@H*ju$n*U8l*hxe3m-N!DdZrhdJ-YDRukYRd5l4oGKv% zz??B>c{)J{ARU(n1!l;X<+w_mcKXg}h3IJq1s;Yyo@&xiM41!N4#?}9mzU~e900VE zb;+vwlgeuY&Yl}$8v!XtjWu*m(b35^RRjqcxR^*FT{CJPu=3q~i06gh5|%kl@Or?f z&_n5rVFo8_I-+X-FcmY6Nh6H~o;BR|aKPK%21-06+}Y?KM=^{!RIxL+#pO8&Ya|dD zYr$otFRc72WGzUdw1Emwp+~poZi)j^TMD|_cvS2_XS|KVMuRSn(f$9yV zwUtN}yTK?9iHtg=@g&+vHT&~%9-D1Db@TDR`44Zn^R}ap{^&bSADWKyt{VHYeY*h{ zj-qFXg$>VN;;-BZ`D_jgvW@yG?^1g{SKY95b)EA%zt8*L@%X2}dWdr~)o1%Q_-QcN#HVCAtvDEDTXd<}9H(WyS}o6d?pt2;vp4S899644r?x*EtBQIu zI@oPKnHX43Qk|JQ6+PEsS zuM`(cd$oN0sPYJaYVp@&;3^?;9_`$vNY$WOj>cLbIC}`s?<*ri=kbYoXCFq>t5^aR zPk{LI!@yAh!GUz|nTA1`LJy(O8A%orv)ID}-?A`p1G_ML(vFt=b{zltBgx6jU=l7I z!|sLTfm9ZhkJ4Z9p>uqknI&aREpX$amLS^MgW$rU93E@yGMU1`W#S|C;?JuL5S>{z z8$xH}E9MIjj%MuQ6GYmX=f(zy0D`q;Nk^?9+Ov-P@GlhfC9fd=eB>?L^$5pr zY&^j`@cNNcB+rj9+IA9|mW@pcERFWvFykn$Ks;9$Y&r!<6yHmI9fel#qj}4v$Br;{ zY|V60FOvs(J8=`#z7#`~pgaZVL{NwldPMfN*eJ*p8ga%SI{zt>PA{whc{FP-QLI)Y z78Ugp)QpVb&_FhvHzjU{`#w)J${>P+;{-441-daVwqneBfg$9*nvbXLsf7=S?Ktnw z)9Ti0y~WgY$>X@1#&x|%p^cN~A`^xxVI$KJuZO#?DZ#KSB%2->c5L_%3AfEW57*}1 zS+(?diqZ8dUTvwXtk-0op8V+m50!eB?||9_o=B_xOMm{YZ@9b7ZN219mKwktXj#mC zPajVH+o4kP^r?9GxIlMt>;WK!uXLs-lrN$H(`B3$;g$e;iV3;*MRBISO+wtN&ii@V zH0_Ij@%-aH=53$&iBCW8ucqMyZCoudgITGpFkp$)uJ%pts{Wgv_2+lr({0*usJB3E zG}WAHNGL?$#gj5u9I0x8#&OLALOt2Sl%de{Li?tTQZ&_)XIio5MB)Q2l@sa!dU7$O ztr-~ZK$8fAbl7h?B9wjIG-qG_g-@TV-1Il#CT;g2?HcS{9DIpHZnz0Fb={_F01INX zTK&X}-+J$T`RI6A@@m0B-Yb?!>C~}@5HgYy+s^_%NfA6b(7OLxzZ%0kRrEU?@q^mIWYqYWa>HkuV4i zn*3@MnM9NTSc*5*(p_p+ZQG1r_uX%O@h|VMZZ~sIbJNZ6O69FUDTuD$qok2LKm=%T z)gd8xhV2KpAi96C>|l(%bT_JhNMq*3Q(F^v%X~VeW=owRnuQ!alt4&sPr$ImqF9is zSJiGU#TEcTap8y=vG1?vJ{-GrZgVk^L?;I!wB~>X@o;J`OC*CH8W|7x$;t7zKKl(n z|HB`CGMx{7ThDt)vPsY4+>p~(6u8~gbjO!B-~O$yyZ_qdW}WdgKpcUco>H=?2%Wu! zt(dk3u$SY^##w7tqIl{ldxrSNwkV7Ghk?Y%C1R&2$CV|~&s4`g84vW@sA1>X>%$Wqlf+dKC z5;g{PTFOPa{ov>Ti(_*|H8T=>;knOk%WYV4cU0G z<{%lmMubux$$0RN5Y%BGB00qppdh~K;bO6}q{qLooR>rzWa04TxxnJTZEBgn{TX&ii4Udfj`FM4;GrJ!#%Y z84m0AQWc_-PeafuRpT@*x$EoA_UiW4ue$dO{>^LV>3C_Uer}ijH0-b^LU0lB4Y(|$ zmaoGpm0zyeA2)v`cWWp|f*x7<79vDfXU`w45TLhv3O~oXU3cx8xjyviz_G?@GmRj5 zx0nhqMwVnUEHtFMnx|nNVa5!g4>uIBSTURkK6YVcP@m~|HDshQG!4fOU9bQ=PuL}z zsoqw3wQk4ne(qbo=Lhe*eRGsnX~HyxmPyHTxJ<2 zt0VoINW3wW=|IRj+K)E>3f+hsBNI$z1^Nl0b7r{U27pRv^;p(% zZl>9qJavsG>r4%HIHz!kou|%C8j7YK=}B3qW*kt}w?|i+WxqS$eDn9c;~7uA>#oP$ zH7>W+(@oUOx#dGhC(Drzm+jGJd-*4S?#(azm6N0GrM^kcYF&e_Op8$RX)U`W<<~v4 zm{uc}=Qu#?sDUviQB3#H7AZ=)15*)OycR{@S&;%MLOraI2Y!LtpWl5v|#?* zkNeZ%lRn}2!#?DW{jEMPJDEqQMu1{dvwqPKc{K6?n5KRh=2RW6u3Z~{=6^i2UTsF^ zIZtPMW(r7LT2)QUJ*LREK!6e|34(CmNJl~N?p}~`pHKfZ%kSHRHGo9=6VdjmIxo>SXhW5I&i26 zB&2DYyftllnqW|yyQSM^*tRVH?t9+(!k3=ke*5v#q@hYvKOsGl^L@tUYM-UKt>9bv z0)`SzTQ*RhFk*qfBWJKi#yQ0zMoCQ7;IvK(Tm6tcAuk&=oH}9TSEvjmbjr%gGhj^& znqw3h1_$UY6AE5m0Ycby;mFE78C*8-w+7C5Wyp`t1dfcfDd4M*B$d_ma6TebSu8E&LR zWbARmc17b}+m&ENW2V@el_?2v9OYC=1A?G>I%2K4C$ra{A|A9UwcoXt#TmIu=2Pa{Lu>QhFtg z=Ao2P{%a%v6m=}V5*U}V+?GYxs=_+GW*G!D!3!pDxr3(Nx3$e%_ zvCQZ(bC^~}&97=u1Wt{XrNHE^k##o76k1pkA*n<`6`=A=EgOXSSY6yWLzqg-5s{{- zD{^hi$Ry(09*c{Cr&^ckyDSJ0;>cYWAyzyONA!&i%xWZhLu#Z4MqE4CDGgIn7ejkl zZ1cNa)#Y^Qayq|t^w0nGU;O0rKjiOzi2EC0%D9=MFvg-^nu`}lo@dN zikMh@BnGp&Go*%V?&o>W5p<4B06i7_8F))jI)Ww2jj@Qa*`nk2@QR6If?zTt;=+EEO0%&a>nSapOH*^Sy^>z@s&{|USN(NAY}cEruU1o&=YGj8N|dqZ11dKO-W^Kjx&11H>INJKp+vCo!hofsA>}v>RbDOY z<2H9~>c8#TZ~p%0-FJ1fZMx=sPV=5SBM_OI>@*N4ur-Q8qc%Y{VbO0gkCIe1771z} z%&$AR_3PLqiK!UmX-n~plWqvnvv6i(7DYrt6d;4+QuV3sF)Xq(+{lS?sQ+~s=v)rl zg~P-#+II4{P$X6heuw!P- z^^+yM3O;F=yBUZzG!vu`FH?I{or`cVS|8 zIAc1F$t0D;=)NXPCG?)e^H712X+!KUv_e7kU`=KdE6#Yx?W182>2>stqHNd>E|FS; zF>Jw>;$yia%?%Ru6q8fcOTVkCb8)zIL@+;~$?|N{%O3T!&090`2 zQnO4VNEySik3vp`o&4o^=R?(KFwZGYZ9-}wwtUm16)fAEUZ4XmH{;4!A(8X$krn+! z^l)hMfCHxPR&8q9VR!9q@7jLDv;OAAFZf5N%Mm`xcq5}Pz`z5O>p722+H^}lOBO`%liioT+Ip0eI+ zPSs}H{_HQ_{jPV<>&>v#Te%ga77>NGu(T27(e7M6l+H?Vl9WJYER4r=bcOE?(R-Vu zO&Hvh!OMNkZXiHdmiD+FZ@ufDq zzOI+ut>yDS>k0q;#rIx2+opCT@5Hh#7MFY=6^aOUBungo#C73C)e+g|0I|B`hy+-S zn|PyO$IXrbdGZaT8DwwZNdta-rA>?;ZSZt(UZpzoWf~{4La70#PXKuV_NCLr(x)&B zRx%M(C00$#^kVWbyX~;Fn{~c%bNSM5di`(zS#`&4mq+AwB+i)>=Zv|p%Eyb8-x$a7 zgVAiD^#6K(3ipk?IaB2v6b%4|q3mJ}I1fmOdrTUvEYUR}v5u&^9k_Tu479R!hAbRC zy0s)Jf7=FNBi*h3%t z5s!V^`>jv+mves$PXhK1xR><(RBtvpukXFKeCM;@v0guF$}NpN6>5J`2n2o$rgC!y zloO04I-f&0$8AR`JyK$b?S#lid2di%X~R;ZcIsfkp|G!EljkJH1iGU{a|yV4XkcpG z+;*6rTT8>H?n)daGw+ObSZ8XE9=;B|89f~b`(hX*KCtT)KbpqtDqu`gj--*8q3hh? zqAgrg`QnIZo7wA5q%f%E(3UTIMMT*zRXt$5I&zKYYMjOvKRn<>LJMN^DN$PF)u?fg zE+08!G8E)aMd*fM%2JV#If5@6f>JS$F(CjV?=h2@#VVT(tq2Ka(gVZJHAcXn(fwG1 zPfhJ0dQmk}HE5YId>~rGeZ7@Dh6bmiv2#D9_XziA5YKsXQNMuQ3m{%*cP4jY&pV9q zQDb7JO%&gf{2HkDk4q=#xT?E0hx|k;6a>pCdJiekvSQNOCa}niFHoid{MfRupRh_*Rmq1U|eF zDNR-CmwCNSCnxKF_Qikof@gp5C;g+lZaw%Q7Tr8in}dRcW*?fHMmOQkEryNYwoyNu zW5kw_I4Maa8Cj(CuuTH{l~)=YZQyQI%bW$po8S%QxJ=x(2A_yLPz~PkLyo8h!)0jN zG^OpZbjO#vU;mAJzx-=oT~(K_+_Ad3AFI@n46;BhNqi7B7 z<#}CC%?i$)a#3b9tc-Re(?CtBb*s^Tso@vrphCUv>Rqpuek%vUWw5<6jAliA!NT3H7=xPP*@y$ZgCxh41~DfxY^ z^c9RZTImt=dLg`ivG8~JUvwt?z^t9aHNzoHx{&^PQ}Ki?gw;p*J2Lp)XSos;JmWCI z!)c=0tR>jB*|?MxuG*cms(XcbrZ#7ah;*t6ac1erdWtn4ix+-mqS_(Z7p@^ukNJW! zs_-C#6MH*vAAA%KpT8J1USQm~;0j=dsp)#qlnm+s6{-|ewa9Ej-m66jZtFY2W+j0| zm@;YtC(p-A$fK6p2MOteV___V5kwNt%DXw_L*cqXm89Ty6nVnA9DeBBNHO;f2pR*j zRjB!b+DSxW4Brl(PgH$i1Ol=+q3%$Iv9?58XdhJ*QjFqYhmt%HzzEeTdWI1M?6m?HWrkQ8+Ffj_&%iy3Sp_x=h>tVQE)=vpu@H{+-`^#|wY{)~da^G!dz7`w1lW=a{~EOSn+c_rM5S*Ef70f>kmV3eF-o*`+Ze) zd1+VcT>skdpZ(VtzV3^^=;{06wzTv>F-OeSQwD#1Zl>L zFVNso-qGvbB>a&GeVywO>^5e+YweR%0%AL=RkpZ#ZW#~82T7+8drw>_pBSi7BwA$Q zKMfGH>+7_+X)+8)QJdEAroVYMe!|CfANKUy_a{@D5vk3kDM~H_lhsq$OOOkO_{NeG zj4SukPrmfNZnc@JrSIpqLK@!KgZmx6Eb2tWgH|pP?hdXN*+{5cfu4}PAx@LJ-liHL z1`2SDrq`%YSi?=Q)t>8SHPz>voL~6UcYpRLJ~_49dfsvHuf!QEXn9r0e$^g6f##iH z>@f}f&|S)3`7iGL_uqT{uG_aLd5~a<9!7C-<1j*}Tvsz;D=jGIVt_~MX3QwK(Lt*` zDYDgFS(XWt*=fI2=hnIPjz&gFsq`Ppc!Q{=WI`-gmNXHb$D0cVh|fV@Cq5AhMWwx7 zL;&D+OL`?I&E+CKLoXp}~3P1e3Ce;t=4=DTaWqi9Zf56eTj) zB*#Hk6^HWBuVTr9jL>5a&xFuY-bqtzJ~c!kVswc{lon+Pn^ergjhh7`_i)wf209Qx zFH=t_VS=!W z@B36uaQVSYVrv7woiX*Ox>`3&v+nnk{CDg+$`%7dcZ5$H9hdEN z>1&;PUWorR243jxZa`7r%`geRfrwyX1#y6KLkOkqKsExdn^dc~el3}V#Wd0L3O|0d zI5X1fj!W%fXv5etX`&;0by+KkSu7e%v1ed;$7hHLj$QX_JxEe^k_ppV3v$FRMWCRmTq!|OqGHHA zZJPvhWwVo~!2##SWFP002986KXQtsIZ4psbIBEc8l2X&4I#^$-rt^ASeaG|P`Lw6q z`ShpX33@fC*exzaU!R=rcJuP;-@50ezw*es-R`O;ueQ5A6uNATEeDftWTbGjvYO$w zCtQV={jkl~oEbh|s1g9XC@v>r?99=k69KnyK8{FFK@Z7c1AWX;t{?y%^}tds?Ydod z=j5WF|JyJ7;A%|OFjmvh|Dn?Ai1IEo*e+^yHY{k!+S?# zJWI{a`7I7F`gdZysH{!pG-y~shd-Iw6KYo2n+jH`{6=wC9j&4pa^Z@Hvp5=6pw+PRTTtUmAn)pq*+L(Q0s6NRe2?o*us4xFobjl z)s`HpDSVyXmBMXE_n?`Cf{r-s1<=fF5p6g&lf#cVDK(5jaG=74nLEia*a{=HQ`*jT z?p7&x-H-nCJA0q$btd&HVeXIr-6FzVFLF?-De{ zM@P!82B|F7+tu+O{Ly<}_8YrL9o=ybr-jwn!vsEZth_D3Zp1~VWn|cv6Q1`55S~Cg zSct@MipPcg7qEfb^2Y}(>ctkUifL&E%nD2yW^uzkkEMqZ%TSf_st}^2=bz(hLFfpG zfQOv?iNyb-+lhU@V;F{aaoD*m5*X|0u^NLbx!r0#i*#9{l5ws$$V;QV@Q0z1hXlzo zRTlkRGXRPdHIC*ImHL~b_MEWMSz6~l&dwJ+Q8lID=3hW`iF-wUQ^W%eY>3!GHjn#- z-B}`5I{Zq*Qr2wD@S@Brr?n4bH7csJ#TnrtiluHYx1=sHJhSsOdGf`c*rhB=XCBu$ zr;7kpf*oRY)EYq&kqA!Uu48tIR2~%q!YyJPhwHAfp5Y%Ly!N?+<`N(R_G*J+AZ@=lg-v0VG-~7IB`Jnaf%gKYM zZ8bJ?Uyb{^qt_*1Q0%FoekeWwqi=D?tw85(4>}_3v-JK9Lg04IO~(%iaa9o^!c>Qk z8}0%(P&ym%N`cR!Q-`C0{k~qc)#hklt-4LOJ5OK!)qno8KY#z7w_RBs<#PaSdFqiU z32)ufWkIN;KGy?wGi}JY(RhGzEL_z_sU<#foFk_#H{9l=+j3J8)LEGmb)h{tLJqcgWb)Z$4Ai7XOR^P0A;+M|A1r!KA6 z^H06>E#Le-Z@GT!(xb0-`=**Z#Dai@tcjHDH#wBz$B=zIp1eacF46O-qlFJ?{^tuU zI=wtk%0-|-xmg7^7YyqtS(qM>z>==01tBt~%@f2dc3hh#I+)9pKxTh~lJF43<2XWM z5N!UUWnxZBkFD%)ho99oK?-T_sNO{1@`(o?qOp(wk~rAH7=)OU>Tn ztiE6@mNf?DgLJgw<518$Oi2x)nXX?1Z~`|DJHz4TYMRc2C6Xukz9knVgd(;RkmKP6 zm2F@;V*U#LApuBl}6Z`b5^ZtFe;^j+O)5N z((rD1#;aT_MK_6gY(rx|(_X0ujOYT(+1Q0kGBLO!7x5xeLlv39NIyH0w(2XIcV(X) z79A1bM~ZJ4;m6KHL6nPb>2x`IGPB@78x{deGCHZbBQ;T$xkXTcXW43fR^|&}8qq z8#0uN8VoyOXg(C{jmvr-$D9)8Y2f8n<9y}wzxMS<$8XH-(x$Y6FFD4RH*WQ3yJg%} zo6Y3`sZALRY?jKyKCUddA{GUp1Ar$QT@~2Qt~&fj#AA!8R5nN=5w=d#IY!tJ6n%`p z!qtrt18Et@ahQS82YiatsvmZ{=@UQp(nmbw_Wj9RjeD9EF};!sU2K_R*x;Z`G#16< zISurr&Z{=JFZ`KzH0^dkK%^1|Ks>cwC}632;36(`EgJ`z@1yA-Xgh)18%U1)A>2tJ z^w>Cc26F;{uroX$^|a(U&D(DK!k4`H6F&Cim;E}?EzJ$At#D1TlCT3G21XJ?T`zfA zh9TA4_RBx-G5_H?r&ljEOEc7vkZ2Q=vrEOKZzs4y(*gpptYT<(r?eH166N44|5Oh~ zwez!<@_s-_HgslgZ1AZ#vsFJ1$~-AXEd3b=3V=eJw&(nm$g9<&v!juAdx-=8(-d=Q z^3rbRw643nU2op>rr{g^@4tM-Yo^WSwsxIPcGED|)QQj~=0qvYPE~-Z6=+Nz;Vxoz`w4o%N~UaC&vk2z5iGFc@|~_6S|V=pZt82@{ES;p5YZ1u7NCWmuZ7 z8LnPB`ra4b|LcGFz}!@;Cbj5Au%YgUv8|^!z4fH)j`~!ODNXwkk39Pz&hrE&XfNiZ zM{_dAnfMQNNGc5}Xb&<=hFOIK&N3)hCx}7EG>RmGF9)8L%$g|jl?kOVEJ68Pn8bt7 zsRM*n``siQJV_iei=^<1d;mBgi#QE(;<(j%IA+T%kvHe1YQNezS#MlWEP zsVV?W|tGXk#R$io`N}HOaOk1}J!PY#10j z9b#BFxrpf@4T9GSd!GDGQ7}-W!wu5bprspBJ;Sob!FZ~XNHtVYfOXas>x5eirwY`5 zP~Ybw!5CryBPQ62_|7qzsOz*svVR=MmD+(Qz2K&bp{PXiAS*zeqM3*)c9A>$L5b<} z=yADAd0>#rdBxx-B}*u3)TLqJ?6tsJJg}4&WCAGv$E1){N421#l^+HfoeHvIzu?kZ zq+!LkVq|2Ns48xO)MPQ>dX4qmlBR^B#<-_?Xj#tl0*2f%9%v!C9^cJlH7sL?jOuF2 zP2H}#8pO4qeChQ+|LZ^hFW>RhkN%ju`s>%nJvdzx@)sw}HSvAaq0(?yZ+pmVqSqDk z#|t}MDk`_CRZW_!9rYsg9)^Ijm(Z1?*|BF$il7cH_dHGWxHR>8+vn}lKD@1&~C^`3PwYxXa6Fj^j? z>xDZJiUqAVVyd3iAIfgm^)8^o1=ExHV%ovK7B4BZ=Qg5)T$E8_CRQ6&jTSH11onwJ z+#Jpg91>s2B|Y-x3QyV7@mOF%+>TS$K89sjez*vM^2WQWkoNP$n^G790b>P=J}f6L zK=z&om>ci;8lT7b3%_qkMTj|oCMSY#OTQmCGpIqf--L&jx?Ez)9>vJ+P$Ej*|JWz2 zg$U|qbfm=)z)lUJiPZDJv)n3^lFPuTgH&KmH9-2Sr`%owu^0hAgTddte5D30a zsneZV;w4Z#C?wO<;7Dc(UNt7liWzvo9D_QczX{jkaOyUga^dHV;$86VID8@wcZ%z1 z!I3UJ7K+)^Uc{4&Yrw0ObwqT>k=$7tWk24+wX8Y`50mf*4f`H zfAhs$S4Gtn#k$T}xsPemPcn+|LI7*1TN{ME$^4{YQfO#lvV=yMUHEAbhl=IBVO^td znvq$D!$4*TJwI@E@6;egZ zMN7UHG>{rcEQ431SN1RDs-^TPh&~bfhCK?b*o4CX=bG`fx;;xoM){ zmA?o70VdMROam=m!(psiNG}M@&I3MS-GB9$z5gVN ziMnKJa$ax$;;*m$@vHakW?i*yvt;n%F~XI1DKQMXaj832|K+ikwAPBa#zara2AZ+Z zSO<0@ky9nNadJK+EDKQ%8;PYk?T1Glt^epX55DP54}9R0HsjF4CzYs21(}7Na!dUO ztO^rvq3jU8oSjsk_vv>%?t?@r%44%(`5#W+#t0I5w#+Y+SOU=x8XpN;}rS7 z%aN_BbDrCyrS4LfHk<9c?`xj(-|zm}U%Ry*nxjp-q#AdP{6gS(n4$}#m%p$7&uFUc zl9hDp4l_~}71JT}ze2$?Nl?5GZzD1}0-B~?!hzEc0Vd^F13M4dCtK%h25^a| zVysuouNIF4dC`;0i8OlSX^pY+=#bo2P zW`MCYG$UVjpC%ZmEyv&d^WHNM+rGJi&$fmCnq|)dY7b#m7$Z> zc&yNg4sb>|P64WsW0VOZ1#jbGSN|nHZKc45Ux~dHBw+ywA1tnE#3HoUuSQc*Fc1N8 zRm4zUlP(Ffg?0Ey>|J6v+-#IjBQQc<0yZZiO@!H-j08P!EB1D-)RY|u3^YNy%1vK` z47oFK2Vj77=uV@ja8JTP2;`fz|1>Gd@uvy%`zXKAzDkr8CVGTY#@32h05cSXx; zaiv1FFwEDR6S~Ff5;#Jhq^=+j_-K_RG6>eUt)8HnBz9Eq_gF`pbvKUtD_7dP-%)+~ zm%jGPKKD`I_?7Q>bo=(~CI$}eGQh+b;0_izX6%ICDim_!ZE|tAJK)|AcW}nq^3S=1 zsczCEWn&`2);LW(r{&g)92r(V;-ezjdzmnb=vGtOAVqpppYGQG{@efdM_+Pp+jLhi zS5w>8P1_F?++jmvq;O=iNwcqMGygx=68lCu9F8MMGZGQPB~z=#Tahd;!5Xz^e9WW4 zBEUl;%Rx^OJmWgd;yHA&lpzwI@QiCX?f+7b*UG2~9k~idQ#iSAIoFnHMf^ zSe0v0>N4GDgN0fIsLs!1HDG;+ z?vTf~TyIJ_lBXK)3a+X2DtZGOa7v&Qc{j!6FLS} z(NH2N7F#|Gp7QAHkc2Fuv9d+i3;mn|9Ib#zi+{6Z(~Vd8t?ev#s1I`<>O3#=@s;(1 zk5u3AZGZc-zj%F}HtY4cuk$jdc|W!5mh4g-?68fKJQ(denvZz~e*#rAso-cR#(t)~ zoJ{klae@sb_e4jEXi=jOhL{sp37BI5NP^ZH#Oo1F1TD3(Iq1B>mddi1U68vG=~?+S zz@4c|xy@~!5%5RFZ)yN=*p^j>ad2l&1GS*MS%g0T%Rm<@nz{{5)o70v(nqKPuoC1R zP6I}o60Um2B~KjDLAeM@MH0>d;+825eNU~bfm`&~bN(%)}C>>2Cf zM!)Qbc^oo4?eS2v7N>O=cLtG#6YTsFjQdcgH|^2tM}O|^OSOTa<6Q5~r**fP2V{#i zIY})HE<3Plri;V-+B9R~qoP~_wHvS?Ct7dQlvS65wLqc^5rwbj8PMnpv=xs3>$>g9 zUa9Bpi(Yp3v%dMm=bLBCu*1HaHT5-!f`J!u6i{ZMuIUHZY+)()QaY4g@A!A$ zfBmji9)}*fSWYRaZY2|5q`-NAGs(OF$T3rlhlWddw^RgRN~lMmvbJAl=f@{KM*jq{ zL*}6*G15;srI6beh_kGC42=0w*^hw(PqwcNXUD{QUA5iZbaj{8u1jru&pW0c`KfpR z%&%X+_DHo_w_P`%&-F6EbRcCEyQV7>FBEkg2B@;MvR)SpV~V$J=Ha(KM@VW`G_84v;~;y6DHua~3b zmO7E!4(j#KbvSm80n=YDwA+J4z_FWU%TO z1Yr^3`c6VhWQj36n0l959yd6q`88~p&-l2K9T-?YJBTQpO=0!vN|4)Z^-9hHE}%?B z0N{x}uuX7&7^ix@#o0^)JnR|rUnSG3umJ_$qN6uQTC!{_Gw5E&Xh8D_?U6*`AbHqJL|{AF4T%9H_R2Gbl^Qm13^PfYA<09)&+8?Wq9%PXr2a z8JH+y>p!hwPFkQ6sX+iz6+tLuM!jU;njnPJ89`-_JXQ?wsI(hk!T~2h8Rkb&fPq;< zWTdwf&T&xna$iI6}JreGAmGFd~aNSk*%Iew<~W?JUWbASB$ zul?a`zxm7W_{@L$gk@@m(|#F;RFBovr>3P;i*DEsG_XwBN1OIDP|28o>Ar(~ke^^T z0^CBeyW>>i^Fp#S7YHj422rFXuj;g&x^7&WRYp3}FaG-d-}1eG@ve7HSFar9uG-C2 zT5ra)X$E|sv5fI=-ZXK%Bq8Pa9-a0QWY;@K4I$2L%d*c1LeZ~dV{y~#C{v!8OrZrb-vo!70 ztm`(nt98@nd*5;M`OkUni+}#wBM&Xx)oR@#vIt&0+~lwU(j|?!J(ey#KDlhEEEdO9 zjjSj&$_?adK?Nn`?xL1kR=y!-8Vd%mh$B@}TxEQUpyBkiroinw&O_T^PJ;^Ckmq|k zXgEd&8J?|3u`a?N(>WmD3@dEQj@?>XMP3a16q$q?IDuwK(+}+;YC3~H8qIlOv4!hF z7zkTVSO)^a$B?;Q6GvEH0NnE=rL$U3KO1ZdGChq0m{}Jb4eftH_z;d+s0z+4(qDy1 zfC0_&=i&RngM=Hs%&>Vp9(*E%ZR$cq&b@F0GmkGy)ZPD@w4}Ypp`R)Om;VK}2u_H5 z@i15{2;M>UVP=>whv?77@PeNb`mz|-iy5Kci$4?~BQ-!6Hy(iJ=$v^5>SEelQ;Q&` zyrs{-V9^lPV9F=eexMAh7@4a%4%ww3iLw@yIcW?>KEi>K2Lrs29fVkhh$-mgHt{R{ zYTysCFg>U<2qQh7_9j&n>T7Wh5)OcRCfpsc3o|uS`4;RvLlkQj30X8wLm-V(l@gjt zTXZN#=K%Zoe~E1(LYMmkDZFA#DcgQI1#;Jr-?#6B%~7Ok6y-=aGN|U*Q88YV!cQES z@c324#o>zb)bYs*aj5Cu_DX~kF<5*2B!T_0xHcXaJ|(hlmv|cAg0l$dtgP13)iYEr z&q<#pp_~b(m+TJhP9^mC95$*3BxlsczR|fM}*189KSn z0FN~|T$*9T;+OVxZcu;e8OUAx`B{p~k@;}32gb=xU*FxZBZmwIno5Rwm1=)uz=-Y7n{ zSRcIG7}L(%9sgqN)wr zB0a1nGS-bq*k5Btc;~w6HdWO%ZPl%s-G2I`Kfm?jm)-Z9uiT&9s*cuabBRHy?YeH# zc#h;rMz^5T*G$j;CqOg8G?=}vlW)bZ2tuZ3IqXKgoBMnXF{F19v6!TL=LQZxHI!rO z-qnG-9p_NR!c$?m;6#|GB#TvV!y2)^20~1mXyi#f_xd0vw zj#B0VCb?H9Hj!Jl@$>`%B7>25-83C+983tu=pEK4vij#K%Jh2bk4R-6_*VpuZ4u6P zfb||rMb>;((@MOzAoc~;BU%=G-n7f#^2$%doMG_b$H zLWM*zOS?r^5{d)t7yTsqQUe&OL3wHyA}qpnNZ6tGB*!f=ue1?4FEGwA%V<6Cu=d1J z^7PhXNjQ)aej5 zr%{Sn>ak?&sB{dKTY4IuO(S|?B!Q{82PqxK0c^~iQA=DgRFP35vwLA~9oilAJTsj3 zWEdhX4zsBdvVbkl7=tdQ&Udi@f-y{9Elni2$z~>w+B!Q@`7pr-#+_PFhIp+|{-Yd{ zl{aiAdDR4XA&p0W#UfpeuN;cNRmJvc0(DTb1-km4v$x`9Ca`YK5Fc9_Rl-n(L^wwH z@@k9Zgbob!?}Q`WBhHrcr}hevQs;^*62tl|-r?0m!|w#uNrZi9nmHZoSl- z0TZe@w|!eRfADA5pZSAt|D#u)+f`dQ- zjhqo!$xn&;5a18 z>+?~UuU@HoEYEedH2a%O8vzdPA3S7yWk@rv@R3o0 zF$}*uWkXtT&dd#6idTm03t5RBE_E>8sqd9PcKLI4{pCF_=vZP2hISx)VM0me80r!R zD(PZfx19TrVNom?FFZflTo({Dib>+SOumuE1#OoZkAmLwxp6C z{Wb@|ZMVK$P3PE77j%%8@3089JA-zzM&NB-&8~F#$Q>PZ=Y(PbR3Y4|3PKxA39-H8M%cVmX5CL28qhMW5 z@eS)oiM zxz~ve_#)247)UAw>0E>G+-iiDy9{ZQ|%PMYbwo`$;a zh#_WFZx~BaPQsxBGX!~Yrm4y6DRte^r5FA1o6mNe^(v2?q~vvL)he#7!Bjc9W3C|S zsEjg4#*ZNdK+PcsY_u@oDKsI2MOYcR**QBl$ma@q(SH2dn~ih5OKqF>H?F4_|I)j^ z_Di0!pT-V5{EjJHfZtW_N5Vb(iZ&X~Wtn!<(5<>=`l`>n>l>bZ>yF!2!wf%8VR_gW zIPw!R+vIgqt%>HKU@>FZtf@f8ohM})n;jy(9N5%`w2g4TIrqWy!2zRG>*uVbGH-G(iAN=LtKY!!f(3h=N>C*86;Z5Gu zsYUZV%_(E<#oF0uG@0At=PNW$;)R+etN~^maXh4Ec&tg#EI8Rr9QjU}bLq(TLR-b6 z_OwT?Lq>1G8sHLH68)&n7qjuvTy+}qV36LkTVI;C>DZ>rkx%BLL@DrxQflE6=DwE@ z2RbZ0mo7V`8zrrQYf%tiQ-)Fd2WUQfU9By%#){N*tH;f zGnTnB+rUoa=^kVME7*bD}yATZIDAvhLvy-ns@J1Q?u}Vj(?lR}G@8LX{ zfm60^v_B4!r4_Orn)M*yPw!s+(`6)CHXVK{=bXA~89auM^N~n@44_pg#B@0f zsXR@HglbLZ#4zWzfE}kvYEd1yeC3cZrXoO)$mf#fE}}MhJk&L|w7?431vN`*7`wAe z`4T^KUO>cBo*~VxP?xHvZi{G*IF$ZYhU+c|upsaWpeT z9Fj#}8+_OS?LBNckpRG3T+KPY;RJ!r33Ys3?pm0u5az-T z3uX?X^b9yuWtdJXZO#+vU>p;f`h>=u-VvhTBZGn56^Se|_#l#d0fEdZS5wNXqq^&G)~QpPw3O(a<1UG8QmgJ}Q*450L+qP{MXH){niCrt z=M_*v21|%$UaybmdTi?bx~~58HT~y()muOA@2$T0v+wx-{(s)5zO)_sdK{)2(BgT5 zsm#c00;Eyd7n%stJ<^>FGe5>?r>VoJ8<^anKH+8#`h{TD271qBJvVFG9fKga>iT&< z{?_k5{M;XX=kLF2zsjq}-rf!Kd|J2d=6E>+)6zR{lcvEwIF#e4yHJP4kAqVd+c*gq ze1rufkeww{1Sp(Ri}S5nFa1f~Y*M!-EfHVCZ5XZ^-^o)}ZJWj7z&h3g&HX@h5)#Ej zU+y-1@aY&Bn~Q}`f^d;{%)J={t$FF1)Z!UQZPW098g_5J`}(i_&V9f1+t*+F#(o@@ z<86EUZQ$n+o&;xdo|cS95MIA5FJNn>?FkjLU}+HPgzK3jV>(BWfVpQFXJJNC7==YP zh566rn_}B#WEL)Q8G18h-nuUJ?J}e(6p>&=h95ypdu{9Jh9!O^hT=FuFrqUl-NqU2 zV9BSJf1&IELe^xlMseK{D9aBR=z}dMpGw;oN4JO9 zFRx>hlMrXb`n+%#;?FB6on^u4V^P4n<8Cg9UJR+)`!msgn&ZLB0P{M3W^YrR3YHR^z85j^@!06-Y_FV)B_Z-faI`jIpc@n zT)-X0)<~K$+Cv=VPf|SFxm&2a=HzlGckFtZrn1!MHv)u@shWTuv7OQXR;Rmt1*!gu zYQ4SgnZXj;bcd4wn6UV7kj-U>Y1_=Ok2C~ISP{2_S*1};a2V#I)0_-5NzE2CjhY`G z9~#!oG@ihaoZ}X>lzBBGX>pj}eSiPTzr6WNzx&W1z549N!^_d8yLvoSO&*$54{2r~ zWeCQ_C6`+OTOFBl6OUq{2972}%9^UlQ=(HrMv~Svj}D0;)*@Mrjh{epnCoRf&STEU zLpAh091ox<;Ak0rghjLTW-I=~+H5R)G%z1}X(y`02V^cDe*>@pS3s!0h|eJklvL`f z`e$XRO&NzD7?PaKGagJU4V4f5s3W`(^VX$JRntz@egr{x=K-1Y^2W=ev4v2hsnT{{ z+NGjuy=oOGXiCm95Bn)Mo3Xn7)nD<9^Yh$vm+O7stS;kt%o}5N7_ouh&ICM5%~{Mf zO}Ac_;l2mb&-~KO)oQ)8O_Mgm=^i0TB_22|3bfq?ZJ0Dd5}C-f#Xt<5ft?IT%yG@I z!|fpLf@;Buy?$c-YU&h@Yb@`H#;|pst9m!LN9*=Qzwp3Ue*Tl`pmeoaZdsG9IXsXU z9tujTw)~1u(Y&nd?yR5x*{40}2Y>1>ub*zKX-D@I%!-F`OdzB*OVd@Uo=`7e;_w?y zAnB?Ht*iLI!oD3kpv?{bF4kLw6I0mM1hl7fm>gxFD{A8>I{UM{$Mn_GcnTswCdpU^ zxgGlb_|UbJH@x}$k6(4|_g{7P`nL`JkaJ3#Biv9tkofg>0GOh+>+NV}Zy*ZMpo_x_ zKAbF7eet$Nu8`3cmeFjTV!~D!5MlW&1X<@zq@GiGVUd(l@tg~*r^VSVWTfYo>}W1_ zghXHrhv#OP)0j8)G!Mfb;tP!~M=q$Q83yGB%Ne+tnr>;@^ReE6l+-m%#vGjo1aZ7s z=z*0@GGJstBkOR@aJ&J)_MJ8>6?K5JjPw1*9S3dN!HrRiNH1g21XEL;a+2`@W|WN3 z<1jFj=6^K*SUNHQnp~~62yB-W1HVpFOS%QaUQkr+X0_B^-fV{IMqRgas=KDetu!r1 z_D@p!Xv}VXJ=wST?gQ}YjD4xwRt?2&^*YGMe0C(h=dEX9%iS2etA?Bnv$G}Mxj5Nm zaZg@CoI7$MjLc2ZHVHG!_W;|UBFWga5&nhBo*^bq$5G3Ti02uPGU{NXdG z7bjI5*c>0T5rE)koa>=VQ{8rnU0#^mxvb$~GZM_Q8<>I{Il4E7uJt3krYI`G1e9oB zmxCaLd`6c9Bznm!IQ0(at*s{jZ1Kt~T^T65S%H8(x;n4Nx$388;6@HpPn@V!{{t>z zWDTDXv7_Zrp}L5>Jx(m}I&eNBR!7=Z@@@dB2ruO1L$P1%%-amux~coBg{Mm0HhDuK zfGjy8ayp=17Opw1E`fW1*0D|1IFLz)a~6mMmz)#-FnhsfuP}&GdXuk9vJx)`2ZwSa zQx3#1&M8BVG1cR$9nw<$@t-WO_|pfT{?u##?2~W%)PH=}qaM4d>b5^$jr(SqhGv<% zjP@PT7x-E8@Sj1HSv--7oyldtdVM zhhF#Q^P{f4^UA71t|&%6Rh4%=#tOL9DIpScz%J?1SLu?aHPR(Adt5|U(zw)bgE4_c zh4WxomNu~s0K8YXTb4?hZMRvrA>!5)MMe)QYKwXRXO_v}jxLno(9-cR(G%a7$Di$P ztOE)rwmK0&v30X_ZAO;p*x$H*_QtoKyyDLu_}y1tf8CpR=Vw)$+v6<&sJUszDOXhj zDGDGI_djrQ>xuM+upvSHC?c1Rv5*fqXU=$Eq1Oor!0|y{66-!!h}w1{tkH=M0`Y@_ zCL=rZ#U*f~+`$qJD+hwQf9MsXU(w9a+C+V>%TI-1}@JN2y%o<`93i_KQS7W|FF#Ym8~XJgL6 zi9dz}!?=h(ngDhSMMZ)j0IS4E#VHrx2dk1CKqVBm=zYrrY}7zii&`cPzY0ks!rKC$ zRg#vTKkHs()MS!{q{8Z=V;RLaDpx9Ev5NS_SsvDz`zJ-}2xkX5SJjS?FM1nk`f$$0 zz}Rq4v|Pn?EZ#7Zay;SIzHKPWx(fZdCrs4aaiY&Zr!d<;Pi)Nk9Ocd0-#h&IysS(F zF2o8QY{GJ7>_sA~O?{ODY5N205wffgm59tPO_L7qbu|i_wt391p3aauB_qa04)5M<;T<_8142ncG2J+_;R%TTNB9=&!43vt3usP_+q!)8@$b zaPiDV#GeEqzNU^-J-AmIV?5xs1&BV}IjcV0a~6`41x^KKk%GYn7^p}qm3~PG!^De zRVK@u1mi0`;W#H+R7Lw?Zo6u|o_D)_v&w12B$0Ey3OoQ%3GrVZ&*5dDVWGTnSRL0r zh}^AtooF-JM-sSjcpWFHROpE%61oYpUtt07hK+%5W)kDgU@Qs-D>rc)g_Cp!sku!( zrI{fSdV+A7PUzz5>2#sP6~1N*HspN!)kiIP1#(P%mnOU5cOim+6MS!@xFvL!>`j6GS;yBvAIV86Z|X#ILmszUATQ$lx7=K*eF zJMY$CxRv=KZvEO*hYTZf3+@ zcC%l`oYoj;Kq591QdE977qBK+PKL!HIaN(Y_%#;rx@`v_DJfIPiN_yUYVa>?;wiR9 zl!78_^P!eaB+irs7e?he!1807+BV_#3QLt8lUBGpxypG- znCkD}@vd91c+JgU`Mqm@@)zef9_cr$?#?S6Zu;8cV1;(Hk**=0&i~lLnR}IX)OX>7%f7_Kis_NFfTDtWXO}y;f)GC|uFG9b- zDfhohoeM_0tpJ2mAAT{~LHc>fxkI7r(LTyAs4(fOYPTP5ob2v<;Qa0P-1?h0-uUY` zod4~c&+mT-M$%nwR$aby1U1n}sy&Ely<{EC0D_~IOs-{aLqN@B06kD8#<64ohD1TQ ztvqx^_!HStvU!xk>2Tti5U2=5onkV#v`SeyNa2eFNIB^7)(geFkQ<5gdWXK+Ix<#~ znp73rHt!v>-SRQ!8+DNG)66u=5CyBnVWnzVr;=}+J)`+it?!p=q`3H$usl-|c>gT+ z3eZITRH$&lc_Amz(S!lu(+|SZaGskki&RR{;oakqi(2;!NgV#y!QHS(6iQ=w_?(6X zVjr}jt`=&sLGYiGpsNW**uF<*4_CQcY$a?LJM9`!nVWATSf*+fn^L;^ip&vhTD1DX zx7KY7c!u(H38@G)L~Cd51S>P*9)YjNb@K0pM1s`8`1|1Z#EsUKQP1O_F{>xaSUHqm zP!C;1cS6TvDx=L-OPL!Y69vBN*9c_CV{UxSX^ytl#L2{#UcXH~tC9okLr^IC2jk3` zoP`5Iz%Ily#ilOEp1h;&W*qp1s}V~KA|+cjt)rp+%^gAS7X%1o%7a2Tq{>#rkw8iz z3!S?Ka&`_# znC5rO9Y<}`*5lMwsqN=#x8o2Hp9RGY&P04(aO6ylrLa>W1N^`o@r6K2y5(W4Zro^p z>kqG=?E7V?!5ua|i1QK_{fthenWP;XWk)>T`_O)O1~oSo3QjY?G8R?Ly`#Ek9TTu( z&_7yUBfOi}oFxS5uS_O1nH73`a@ZKb<6TaiT0igtYSK_uk6fSs z>@RO!+MF%}UTz)-YNO+Bit;N9cZ(>OVF1;)&3WvbX_+$4%rp*T+vcXJ`}1+PKmR*V zd-AJack7W`H>+I_2`h~`qbsqh$A8ty(0g{a@Zi3q`#B0_InT*Q$D;^^U-3V|;*71eVDtu7NkT3( zHQm@SmyUD*4J!I+>4)lkH{ZH7-8fkux;8&>ZF%tF@%pvt<}Em*HK}cKZda=-$5pfL zma5tfa8_lUNYn30^`VKq-OQB=XgL7XHXs-=L5cYVmYlFy5fN2=@`a6@pFK>VjU4N6 z^eJ!OEN&ttBM2=N8&WG`xKMJa#>fMAo0aSP%J^d1&k#g2z zKIr+Gnik7(c`xzn|^F=-01r~EJb2M=x8Oht*B2l zoX~BOB$sdLLkNnr;V6&GM9w-2u$IwSAkb0 z|2bMBFJw|60#sjm>hZfcYPzn;?YQ5qJHS)dZ%i-ywdJM1e*Yb}Kk`BEn?CA;Hy`r! zt515;(bY%g?d_?W*R<3D{yhzSHIEado)e6m(fu~_G$mlfseyp5PA#yLdEV`J1f+L@$pB)$bhE08F%%t$LbtM%qFyrq$W>rcQVOU z5rO2)bJvhZk6hJhXQs-KYmYTdzf71ZAsH$+c^=a=)o*y?{$;=Vp8XlfL^Y5V4f^6_ zHzKZC8@5D8!MIm8r@=Zxfeghd;z0G5sR5xS4RtuZ7{}^-x7<9LuHTp+d}O-+q5c7! zcf<9YBVsqrcmJpQea^yha_ytqIkJ5U{SO!;O7g7 zi1YpkLvd%X%sH^jfd9=NrAXh3tOzid`-=8~h zaK&|#?j51Ld_hRfjb#)-qF@@{^PCl^s~5tJdO<0y^=)L$1L{Mh3HgzAb?GUkIS+>+ zmIkUC4$^kc`lOR5MlA3uXhXi9F=n*+r@Q)tkAuDPf_fYTeYMxrKDty_)&Axq(QjH1q0vpG zk#ndNTy8@lJSlt~4r|q}n5C9BbT9c$gI!-bqJt+sXAVWnLw>X?EX9Da^b3Z9RvvaW zPPJ{Jz@~?)M&S>I?;Bj=&=_fK#0^7)Me9+ECRyjEvVSG{LdDL3MS+l1;*vniiGzsP zHe4o~zs3x!UC;Y7W{wBJ!b%6{m}@!dtklSp^KijTY@V>S?_hYvR-l8S)PT_lUD=5m ztNC=21$$AI--SA)qgK0VcwsmsmM&fgmy@DCGPxrjNtM+a+_8;TX-ix=1Zr^RYFNy+ zIAvj$g&ACdu9oY_b17ii|h(Lr)VSIQS*=&-=;V5z3Kga!=IjP_fQiaJ8y2Nal8__qTX_ozVdl~n-ZAqNKp2z?TwrBQwu!Kwn zsrs10>kXE<8%2}FoUf?of~I6zu8Y_A1jVa1BKtTOEc%7pPKTo&Qx&lr8?!1Srp6B7dhXFpt7;}@W8G0M> zjSdA4pAsj!i!c?ot->ySQ2JDniFk13%$JmNk;r9b8Y8o>G9>0)umSW^+onZ{=)h&T<#C&zm$3tkiA>+eeK}#=9cql|Bd}X+__lBubjGBA|h$d05_UJ#IQY75(lk zC5XWpUIE` z8_S}H0uPq>!dY-^CS}=S`%e?-!g$H4>R(R+x1oK z%;>rmx=cPh(FBW8n5p)XTPiXA${nG;EKyIFg!fNgZH&@+RO(C8n^_sGKk!cKND5 zOukje>AFzWAlC;ZDg2xj+>M5_Y99LYJ=R`^5~*$Lc^GB?yda)7b~Nyt$iczxKzaeZ zU8lBQ+V=7YWDi%ByIl*?JvsLdRq>G?Rk+6dVScBQht|Ic`Dtn%zML>R#(?406@VkG zh-H~TVwiUGG>!XRwbcE7z_F5-E0>$cJZkm$_sQ?~#O{etSU>hLM|WK5E?vrNU>7w= z4OkdJ&_-Bv)Bu!kj1S)!-~FERcfM!$mb=g1_3r6C_YJpBvDdUswOQAzb!u|6C%0r6 z>xneQ5r*2RuloH|qaIks9`-&2to_Ahg0~TlS3dE`AV!$F&W*XAa5Guv(+Gev3 zoI>f*c1>OlXQ$q84Ti@?9pM&)Vb!e!qf3DRp`vgmfWotagP^5HL^wo=1w{?MnO3Bx zqHa%2Ul51i^ik98)FHX=BehfSMp^43`?yJa1poUo}wjAAKl^<1KwP!V6n zqfQZT!HF#Zg=gC?h)rQH&AXB60(uod$+Mjc_{fF6 zSkXk7a!2 zK2$qcB zvJ3U8P)yNqRoNH2c8^(3XNMg%0A@hl@73gWkrE6;p zHDfMKJe8HJtx3a&H;72FqZ=mE@+qlj{$T@qA$tiy6dR8~-u!eih(1Dj0!9_q2?QcD z%nyAXLLes$Xl5V|P1~VafCMy{_FVf#KLWabgooi%(iMtZE|(Me9GhQkF{#l+iOr+KLA1T$wo<+)A?c9yh|9|oBBsOX8c8uqn(07!Qw zw88el!KWsC$`wuNL3&qYS-SQW9PXXjI!S$TwZ!r{!}c;yO$!n&@vNl|%(Fp$NT}mRhYYJG+Pj z5-5sFQ`n{-wPl&R7JOkwb8%S4YLYT7n0ld+kP=GPH8A|IN8V87uF_Y69+eY2cOa;UhyY$SY6E z9ph!_1_xXKO^&zVg!on1a|03v`i7mbMxY5+4!#myPNdDYr7m_affmey)eUk(4me2; zbZAalVY1obH8-0!KDQ3{BEc*NpLQM>yCLnRSI)tPxOggypG@0-?vv99T!{QNY?t(y zX_gw6ZOcH&peK33Ng*1w#y;&GriLkmluh^+NZbV8*s`t3W3RLd*xB+pkog09TKg4A zu>b&4V=+U;svYsLI~YZU4nDl}(K-?lbCYEzs?C{F4*4E2p(xxC1;hbcrmG0Vh4a9j zWdPik(djVGSrbLb^h5-9U_<~!)G<*HkTQF6!C9!9r3K@;-|uM~inkd0 zX@J5LTWi}v(6QO%uB}$9s_o<+g@d@?PyJ9&b8~h!_kA^v96iI`pw0k;D9OqhtceK` zr7(s@aRQY@US)__nW?G&ZtAMvgZrTBTO(?k|AAbiC{-kbiC|{qQU#mH#@*qmsw9_j z%naX{#-U!8)rtuY^`u#{uwsgbWmTqF5uI1|>+mqiCd*+B6DnV+ht!I2G!wgk>Q2r; z%+`pOp18TuZ#Ez_XNT{<%IA98V-M}tohp3Uj&SBgusv*$#W-YiF&W4>0qv4O_CH7ePo7Un=!y-R^~a|=|Qn;ER_iYIU7sBuzrg)V3jh3 zimq+8bj^52<2z(alItIYhyVaAIX3Dc>>>ux4igmDBSaMDdQ79$<(`nlz@Zo;hy{B% z*4+b@wzM3T3gk$lSOx%*kFKCbJ-uOC8C*bFU1%2Sx73_iK#YvArOpY@gfO>^oU|a> z9vYlj+vU#-ctPd)_(Jt-}v4{bTnDeXHqxfEmQ9O*O4D8xCrf%9cA6=@dy1)6blOTN7 zNy_W(SRa>vWLv_6#kpSJ85tUiJFUeeB%S`EWI^X2wVm@jTW$t z5bM!DUJog6?{YwS<>`rZ4_$isgwy#8Bx2&*FaUs#kduImG7b$I9bar8Q_Uu@gYvZ? zCdKKc!Yd~%wsD+u*K!YFN38*`P3}}tXdo1%d7lCJQ(RMAC#IWXu+U7S2@XP$mZq7Z zy<}*X;!Q2zz92WW39WJ#;t@v$RwLU^yA-v!;`QMhWSg92rB8>(ic)w$0kEQDS{7P3 zsDTq1TNC;^_4_1Rt6qp?B+>DN7~&o%gq46II}qYADBoM4TvX0GIo@+;EI<4nMx7S= z9RP8?tUy3Hk?B~_fYlR(;6LXzJSC$f(3dml zo?9Nw5jkR)hq1Rcv-y~rrijo(K|@VG{p5v;t3Xg&Vux{}6=aGrh!d3}c6d$jX?Wqd zQlWX=EC7&2iZp)-k_|-t!4e-bKTSDGU4YME34_$73bs&j1Y`^|eIXA;NGjVC6)-^4 z*ovYEoWcF3Y#4C>pgT=4n+41J9Ll}mt%;H3Yrvdc zEd$NU^lSou83*8h&>~DAGBi`y0f#^!7ByL>e!#w}IAXcS3$MFBwN4yH5G&zO&0M!|iPL&D5Hvlio` z{9mI(kLaTxH$*0&DL5@ok&Q9zVWw_2n)Q=K7E&@!JvKEI5X(P`mV<2r9BKUk2>8?E z9X{T{T8S^N|UD=2Xk@~tiO0)pU@U5iFC2i+0<5L+gH z+d$1CW+r0qT&C-cEd8o&+%3T_gaL)R(W}c3vhM(kUt3pQK!124e38iSqDLX}HH8&h zCgD=j&j;R@am{>Fbx)e9V=4tDFU%q6qL?a0B=W2e)iUP}ip-l4qF}U=!aUMFz*rO* z6UMeaLg)nuu>&2|y=L)QjI>JAj04{Eyjdz}`{i}03TWn6*qiJR)+k8&;s&O9W z@5rh{ktHb3Sv)p`sB~DWB4pOnGUf_xq;#vSG8g2E^Izx^b-g9aiI79rj?9QfbOI7f zZ!@NgDJ{gKd(PU2)w-SrXq`-4%bD7nyHBg#K$x%J{!COETTyTz(AOkO{9c27@Ln1IKuTv z=CVwG9iOysWPTQ4D*&B@B-&c>5b8y;R5vFRO73|FO}IFw5HdC1;w5*Uwm@w zG(-w8w~+0)&m$usu{Fo(Q=mRh#=NJ?)K;O+JW`ZW&YB8n3_SJ;wkX6vEE3jag7+=2 z!hnd)HY-@VY-k6gtXiHbWFOOQ-|BPqY$V;r9>Y^nT6*P%)DR!Dd=LwV6`k4FfsMPR z_SWi?kmG+>7P^0BXE#7gClu-G=}}5Jn=bmeF#QC1Hn9f?#8GRqwI?7Z_7gfx_E=n& zoT4iGPQo$S`x&euvq{mpR#lYaiu;>E4n^N6ohP)A+@@hw2-g3Yb%EMz()7sUWi zTxHg&m0z6mcF+bdlbqGGn{aq5ZH?t3+M);=Nl_)v_}ZN zJbrV5ryI!8CdC4W!7UsFJa#}OG-x+dgQ5OPj9NI=XlDan%(DiVrKXh&cm!f4@*ssi zg_+|zDU0ES^wV;olW>bqqp<@i*nKj`cu+AM+_x3CT;(R^4vXCh8L*pid(S23jYb0i zJ~~m`P`$`tS{@7BluSI+V@(o(BDzEwp(YdCrxma=Z^w?|2iuIV2+Rv<(l}L^EHq$5 zVETZE5LFE1;o<>vC?$;EAD=6AWX3M(a-_guC!TSl*)G?|GY1LYlQ`=l2BWYA8c;|+ zBM(KP8{!tJ5rxQ!hZx9lPO1b;19y0p9$pnrXJ_xEXKnpN|1uzYcrD+0@ z6Ub)uLS&FO1989V{m371&77JRLA?;4W(GQN*CZ+gFD|x=w5I_+4w{?JV]<$f5a z1ts%hTN#PE98rY+6bT@_5l9Nd|K^qSY=8n5$XCYbNSmL9SKuJvqUN?iaVE@5yBRk>hMoh!Hh}`@Lr|R5 z&*-U=Up5gcow~LQ4B@}$gc|&)hjZ`k(R}f5Ah@tJ3xaY07^xr^;HpdP!%0@hZU8y; zlQcJC1y~-ciwdi_!pYa;qfu@2uaUPEu4K+zFk0e33i1&&OLn8f(o51jp?%P6pnTMM zWR+Y{o!xOOctOx?aT1;JsHh>gAB4xcwax=wQEeCah`JMpXo;W&SUnIiTQsP$YlD0Y z0|zNIh>#IoFhhu4Tdqi|yNk(|kt5yG&?9*urHWO<9s!SBd!AjEaYJmO2N`YH8frWC zpYyF#wYtNLsVE#c2Eiwn2~q&-X8)?SDlqJ!^Y?jgkSESaw;eGlx2I$1SN*{SJ%s$n zBA2kU3j;4l8y0Lqi{`+MKR^$W4H*kR9*Y9t8|^BX#=)2&EEF{|5AHB6o-;fVMqVg2^lHadbiu*TJ458gw?+&HC5jWMq-H9q^wC>!$Dl*I z(IFNP_(#@T*pF#fr5^LEa)45ItkS+WTxa`|L3%|1t4c zBgon$CQ9bZ>|ggtf9ai8tqQ3i@z{E9!_gSvC!KzB3}AhNE3PCxRyg8k+RK2h87O^Z zW;Py30g9J{L;>>&yCiPl%}kBVz8 zj;`X1WfESNlhlo-oyd)!*Oik?USM|9g=QOsD}Rea7`!rHA}-ptay}UgDj$hQyr|Lw zi)qQ^4Mp+7I!CG6I#0N0@n~_@W{y3W)I3jAce6^D^uv!Z?(d9YsXaF^*b6qO90OF%!*! zsmU@MgziT56YwuAB+{XjWIRKRgjb~&Ui))NLJ!!-LR3HML^<)gnBww-fh0lRqK1eTL^_r>!V7mSw4_Io21Orkrc9e_W0AmcVg{*cLL z%1#blmDaDzqcWbf+cmv6aJfCXVaev|7P3gmf^4-!XF}OtV8>8ttxzg1OZ&CZ@l*JL zSkVqV;}#(rslCI+ld(~oxmJ?zskqSGCNz@VUgQTxO_Y!t>P9tRU|~}wKxyG|Ucq~m z2b)r4xmhvf*rPeEc`XU*24(SDftCo#B$Y&|YC6`hxY{#d8m#Jx2SK#}wUM?$m4qmV zumvS!OJCU6Ucn3MqOngndXWVSzxqi30UE#@6cP!@;mH8>B8MvHJW_dqq&ELeCw^l00Fia;}O z8AGO3?26aJ(nYIOV=cEV(%G@HFeiXgf|qe(R@ki6C?)kc7xC3 zwt(ON@Di%8)ig$*=?I57RmHxF`ZRjP=-$YoJZxP#p}@_nH44;WUzk>AUKJAtJ$nb+I+;yIcCGn` zWkc5A7S=*o4IX~pBl8&Y*rlRucCj&;ZyD!b7|*J7FWeIM-N7j@bP3Z|<4w#mi5(i_ zs@3hmTr8qf*8+znW5ZqoU`{b8SzhmD?@_L}d;<&m5ipc&l?&fJzPvTS7m`$pUgg4{ z8;^8nTyAS{7b06h6yo@GLrr$*JIvI)!nLdmo)8!azned@hEYxG*64HgyYhWRVvjqo zxS;atmUhOy3T(-Bj$W71mBoxg&sW+0wALdAtUNy#u2@;rfw=_YQluH;qDQA7`#h5p z?dTF|b^)^auR^*UK1>mqW13A_Q$?O3--k?71~T!=w}>tCWoNA8R*(Fjq5F2ubQH$$GRmcazTX%U7dvJNyC&TO+Q4uaTClY*zbL)G}; zg>qzPEJvzcX={zDC>_0o$nr>&Yt4lI&1Jo7z8V(nD!iH|sVr7yEJ`6OMT14*5nx*z zKg8M#6kPzmF+ZCt2G&_#)$C2w&jyey%sg`M)Y|i~)HBO+R?eKR16Y9yL3Y<;s#`H? zvanHadD!&IgRAm8UO%)N#V}UznDu-`^rcm6CR;qI1?a^H)Wkn65}y$In9gjKm5GrP zmX*|5ahNIgw6Tl@nb^W`I1DV{1wn2)K(I5nl3#N|f8Zj~QW)Mbdj1W+-AUH^IhR^z@20B|OTYv$sdqqFj^F`eQJS{*%-i zhI$g-cU(3Y-<~<)D}W@zZ!If3W{7&;tYTf#9Gy5`5||UZ+2)h0f`&v1`v%}Tum)0I zL5x!(8$;KB6xUyO5xa#!NNOZuLLop+;}&~xh}!McGe1hvRPY0^i7t?}d;pXJq@uQr z9wcK8lP}TXq~26miH;;g*_>?2qe&B31;`dD_+g!j86E_^po{8?d!F&M+FosOF-F@gv)=C`mtq}(O>)GLEc`(AjsN0sE$BsL>%+j1o< zL1g@VV%v&FWarCyK32pR7gDclt_H-7ago#8%A6IvdJt>XBKAw)l}Tn% zTJTTRSZa6#U)30#o7XCSPjFfbUZDTMlm&_iJvZQuB^u=e!ol9uQ8`YNOT+U&eo1bs zLM7CJDryd0lXe?b@($NVS75_VE=XN?k3EGW%QVS&K$C!3fG(%IFA~3NE+;wgY2u?4 z@))f^??pagowcP2s-6TXe{CD)@s$U~rftOz76-Oe0 z6R;@GIbTY~1~hjuFVz?pA3YO)V^Mp-dPoMvnd@@7@ah0`=15Gw70X%LAAe*Gdjg2( zH&T+cYzw81Q)rWLt4Op_nz*)2mca%(C986rDTe||Ce!VfZfMj0Muc_OF{$aE}A!`SR{24Jitnl<-Ap%^0DAjo2c z=@U~e8=VKgF<9Mx|Y|9acy% zwME(RG}1OQ7sU@|8Q9h#CaHExa_f6weII&e;dU1Up7L#u<~(|6JL#EP06583_nLn3 zYisa&=wIpjBwO-ug0p-sbSFM;O!sp8qz=yv4)@_z$=$#!rf!8ZWxtEcu0$H*6jX`l zD-eC6@r9_mqdP0S0RGEZW$B|!3wfcx)*pL(`M>m`a_=bvX-B}tSrI>fzyS`dhj{(y zi=&HWUm6~O_3C!ZCd(15Ahy{_LvZT+&C-U^$}wCRJS6KO|4@jC;N4Doiw=% z=5y2Lrd#2W1pr})G8%oi{U~yst1jHmT()9&a_HOj)?(0=_fIfB3yP5lF0EJ(Vh*g{rB1MT4&YzD{c_Mv4R12^U z73nC3mcc0E+&-ve04D+gc0f=AqQf9XP{uz%XRMo0(PcTq0m{=KvdAhrK$AUeH^>Za z2U{I>a9R!eBDhSp{nZTXQ#V`Io+wO70n zAW%dB-+X6XG)<5=95&xh0~v9b@e;VR%C?EIEK0o?AcNk>tE7V;m5^1-ayJZ(rM%o& zyUSFFh4O`SR?avv>TAD(11e@67(e4+Cc-37S*`O`&6uC}D{G9l6pt0@a;WRt;W< zB+c;5)1xF-Kd&Lk@I>uRb}-ac0w4wXO#qT~<=s1xQc*^l+&LKL5;SS5r z+A$2rfRQmq1Q+IbviNXSp{BloBp&`q{}b#?eQMTN>d(zJHI`>|-6s%+e7@rhU@Kj$ z{*d}OcUdTb1+2NfaS6`AMWcz$U* zMK6GM=@iT{^lv$>Im0irr8Q$EV1P=0j|LX~w9hq|1}dJI5U z2y$3(QsIta4`E1=sxUpChef9cSU7Ohb>gAgDNa}|`T6{MDj0R1m|M-`$?9A=hna#M z$O7+|@gtuRUURW0NcHYGfOc*ZRPu+>BqZ{ek92vW8kg~ArJT=|?>$$Ox7;+g`W7o;AkWa7+f zzXvCdSH>I}<$yS%NONM^#Dugm5I|KRoOZ-%SoQ>N0?0eJ)s(MasRV=5ufoP=bGo{k z%g0QZ=e|xkZ}9eNDV@6e4ntP{t7vc!wWoOvZm(SQl?7^8+Q4^AZ2c-$poeRL<#hBd zmD;6nXfJ{z?zSisw(YXoP>H1kdd4e?7vXOawOK6yJwU?0ZyFCCn$;Th>d<=umhqkU z;vjIx5Kz6FApqMIms2?g{H_+nAdV)Q?Sku#!l*Z5e8F$=0F)Tzk?^;0DYWgn+|joS zO`(c%(LLO8hu5a_E(2al)#|E4&jP^4696B6<9kso@Dsq~EU*?0VA(T6bRB3_1aC98s8aF0 z41pP9(_<~vTbq(~P%$+!xR;vT;e6Wf^o}xKweybxZKVGxiE)Ar^(iQvrj!_@Pf5e@ zqquGq?keOW$Uw9aJLrDPv*sqE_>LAzOZ4ppjnkv&fwB2KWr8Ycu999YAk{alr#KM6QXfUYePri#mmElLzPeLisEXWZMrJkrEU2O_qMI|jh zAC>B|oB>o$syyq7!0R0ET$umvTMiJZpLrD!O7@a{MZ%V2-*QHUbSOlyyjiVmWqwccIoO(>|f-!%Ly*v8ztT;CQ${xv(b% zXF$R;>wdh9w8Loc1{u?L9bci$F=J7hIm9)l$A>jXM6s~#A*iAERSgqGQb6Sb(ly<% zP~5lDsPBPrCk3Kd>+(U@)SWI>^n&qDBJL^pGCXqdnxoMZPQqazVLVd$D{;=9^Q399 zD&IIP0!?K_8oirp4F|LHyaXg86Uht0vvNop6P4#SAyWSjCdEp~k3NUwRXv3v@Rq+} z&~f!3*!>j@YM~4w?aQx~pNMo>Cj)8f1{N=LD~dzMkV>~%Y6~Yy6}t6A>VyCSmUJTG zl1^*{OnM#5E;#<8>I68jM`UJ~V}QnxKIgR%RFXnR2c|RCsY0?NS{RgBA}e&?>pKD_ zgJI*X*>$?r{}k$CFeftu(k23}FzKCung5ZBsTf8Ss=g5@>lVZQTIt7PO_xnF@|Ud7 z&;%0wT?`#mXqxXM>MyIT$cq$t%%fR#gk_Rx*WCD@HlPh4KHMt&oNF$_C>*(&3Sr|% z6H%BYt&kQ^af&mk3gF1iiesCY8vEd=`Dw%$+4B)c=JA@IJ8ABWFY7EIDq*FA7Mo=F z(cT(rvDplb3cV&ZJH^qBg}@eBnx{=cSv}x3H>IA?5v^`9UJ1I>_ zL;;m>axKHis$*wDRM)cthxuMuI66fR0#xFX+Jan|I9hnhe2w(?{Utff`SZ-}i) zX8W3pDMf>>3uUnA8l3Y~LA4?~a3_Zcj+RH!pJ?Pj7an2Ud`@}4z3td^wlorYeK)}J zlDtr482Z&G7qg)}&^DLNk@(~q#<}7#F{Cq8OWg{Kl1NG9(~|V?vc{lLO$M>L$htSs`FZ1k7i>fK#}OV-olLqKO1WAL@V@iB635O zDVCW}tbxVqW-PV`#4IYzEOoe~r$ll+C{y(^<>CiH;<^-B#wP6g6v`>rQNUaTwFuDS zdc%Fjo(ElUxMkW3nRsRJkVHQ$;@JyLF0K#FTuor)1Hvd7JhR+FIfU@VCMi)Z2YyLg zl7?!5&3W<3pC)(k)0szu4+Q25_82Yo;aSkNA@i2*NU{@Qu_Gr_LFe?;D*_FZ(bZN2 z)zkfre&qu0QM7rcL3{3C>Vgi9!ufI|t-4-yqseq-a$O(>P3rhuMy!Uo;dX2(0@y;F ziEcC$v>qEM0g%7T&ZUmWMawR2HrUPfd#78t&OHPzluE;0ZIQ{FDB$QKcLk*{c4B1g zhi0#a1%^fxGoXiKW?1nV5?mEQ(p;FkJLcdsp{?s zhV$Xx8vF=>!vR_f^r&2rU_A(PQz>+i@LceNh>n`!^hS5g@MYy(_#=l)9>3z{Y|?xo zvU=!ufRv&wJ|JX~{b6xQF{=0DU=#I2*&H$rZ$zda3K2-F4erAJ+@+GYareF+OzGX# z{1?I^QH=tv>Snx`PDY`Y^k)!@SlD_26oUHdc91J0%C`&O^-xF@orPK!A)jJH9B7pB zfqg&3Bv29Suv@)&@|Yu(mOe)xghR>=59qZBH4Cz)MysV!9fGC~D75KS zdQjO|I-5#B9*C5YYZ4O$ZkfC$k<+7zlK~X6g4J`##Yv$g3bdCHk*%@{S>z^4DQ$0P zSB>B*(`7(>8ZBORB*j@$k%m8=@B4_uSuDKYP-NwKW}bIgcucr zWaF&?+38`_b+whKSvs&y6Hk-K`_3SUk(nGXj5~z( z&82Mc-^@M~`XFvg9Cbdd0uHrqHhd3k5XHx~$TGb+eIdljK&3%rbL-_*&L}EH_R57$ z#cIApb%@)7uADp+Q(z8c^SF0PR#fBXsgVt$d5O4M_=T7~z#Rt3RXFd9`)1HCSYK!Z z7hB&_=3wL+suO<4=h1_gIE>s}M(q=qJJyUph$8pYFKQ=^N7Q3#x6?MJR{f-e8WyRl z;R0rNtc59hZs&Al0nc(Ejm5O?mt+za;X<6`z&;Hu15vIdZRN-p&y;Aq7~Gk}9d;FB zf%2OM%5Q;y9=Br9OlyOfq~jm?dB{joBh0o<-H5-2mZ0J-D7cag#t{xS;*c1@2w_Pq zIQTw{%_}x-%In9nMy77a-keC|W$%RbzSLhbeLCq5XaJ<)wZ0 z%*YDtAiMd?ScVCiztUo&#ED&<3&sbSht;J9cVi$5kCpc9?n6uCMIqo!DnIpIK?&5j zkaKj}zTyBg$KDCXA(XTILfHA*+=Lq=K?*VDB_k5n<69BJE*C1+${y%gT9vWOl(XFB zu3$=yQ0-SOqYB+NQI<-^jBbO}@{*rKBg^X`G6+_kwP}ZWg8K@n)ZD7X>Jbhe5WV6s z^chh$Sgc{`pCKskv{HM?1y_xy4;m3=<0vF+!OURQ|HWI(U@ip>g6bkI0@s`28U(QB z1y%~`+4M7f8T=hxSw+5p^-ff02-d-Z!-7tl$Ko;|g@aZzVj0pHS$d}n*d|k84(OEz zERi2S10JdRq^lqjC$XH-3qPL33kueT-An^1@6 z`l*)=Pvt{#62(NM)$nl^jA;Ut_AcSba%VrFHC)MjloG{G)?fs|Q0`zJ;)ctvWh!oP zT=DQxw}jq|pg;js?|Iy!x85QrZ4kjTiq2c8h z2hY_;qQWBrdnMD;rMK&aaJ`XSLZ2$Ybakpy;t)Mloe;3FoU!pONFkFHjyqvy!pIPl zdIhW&Tf2iD-eFj3UA9JO@|lQ}IEKRR%DniaX^XL=jw9dF$jjs{V&IY0&j!3pOXzOO zw=CvbA)(<~CI3zKpl%;xXje*WxiTI!0j{&-YepL)Yi?VcUHAlE#4v;QW zx57*IJ-2XGz?6)MKA|C|c;yA}k6p|Ny6(<<_n|(m+@u%3h8R*_P)+&o4?t2J=RxGT z(AT@OQUzH)PmlmhKki!?NQ=*3Kk_8zoh^C9rMM2aK z=^9Szi)ofeT&ZbSSV;T5>d^pn;;qYPEu%u7PU>F$ywFHFh&6sLLtkXZ;Gu)N=)@9d zu=53D{HBW%w@Rp4D1Iy^^q1CTSX-BWHA-;T8DT^2 z;pCHKK%w~mY$L;X-rmKkFxa5ltU*>=suzPF!4hA$&;^<2>Mrkeim=Y( z&SSt^<1fLBDoIrk7i&o#DsuglVLam`rOgS0^4LO(PixAVunf~QJ^CfpFkqhOUl5Dt zecd-%Q6vsx)OGeUjDR=0<65;9jvcNu;<+!_m~+g8#TIUOp*lrgpNk!)Jch_C+_+t! z#6zL4pcx_BT2)E>t_ExcUIf5IA4GEdxlQ3w0q$Vta6x1=eTi;gn0Lqrc=44_EhRAA zH=&D@*1RVohT2_8`E0pOlS8nzUsh zWHD?|LS-1UaY@qD+sANP&#tB*oO8IDcXi;+&%IgkVh}^pxvg42)PZTOVtJAM%g@DZ z2tx+cZg9@S(Ulbk9BOIgD0fNf@mveq!bKYOq4vPxtG!Y#y z73P<+JQa;aXcU(;tli83kwyk(YUsRFPudibbqe3jN>S~%;aXe{CaeI!ueQ$x%_}B^ zQHgQmkgUejd;5oJUW^_)45mU%%YL));;>gV$bsWW6|ks9A`83=7EHEj&~>M%)uW#% zT77CB3@O3@(mXFdUY-tlQI!})k4VI%<=~yyMq*RHa)S?~;3xAJBjPQl9j>Bm zZ{{JnkTO38kxq8_z_NUICCgtl$(o30@nR+>u^YJz!KmVKrUl}dOe5E#${6%wmBKMHUfE_7 zGQC5)MV-8h3Kxa}XdcW>%0#0SYvt*P8Lv)HTlQ$Jdm!pk#Wz^*dvGq7&0a|%j0v&w z!AYBv32)2{orPBj;C_neXBnb>`R{ngi#?lPJ(6k#)f{A^QB}KdVhsW65MA_C(R-T| zgyY}Q4Tz%AY67SHnyhQU&Vo2vHy)}@|Aw;$^)BGNfpX@wC65F zKN+q?I-1>SE&C8uPkRok?VMAhhb{zbb{g>3EgX{pOd7-5Gub7YvR=vdax)pmm)ftQ zBvXK`$Hx*4VrnCYBMPhz$^&N|9ngQ(Ji3LVMF&lSiM%qFrka5SD}6{SH)Q@T=zs## zgIx=rFGbHB;wR9a)5_TWGyo|)uVj%#g{0+ZZU#S$I+z0)Jl>rJtJp?bA3>t9M~A1` zWr)gun_X-31&1yjs&QVCs4k4sNM0d$-4gFIGd6`=;8HhsuOd^d}J#3I= z>Z9SOzT|}zLV?$&+H;s^mxIuHl#6FgbpY$NozLsErUawkUtklK#@>VU0%`{qs4v5? zvp^#X16m!U+1eNSo=U^w!%Qv)I{q{<?9F<}l}O@wKL7Rfkgxt=ma@MZOX2aXl|(jo>bXpeu;n51Nm++Ap= zbRepfD=o=Z=|4RR2mz0JKOM<2WI6ynDz)ud6y6+g_z_jePE=mNbVGERVitz_kv2hxC(TrO9d$0xY{wc+T%&|NU{G4Xa@3=gf+V|WNi^Cjn7CO(7mi|w z6@qhERJrnT@VF}0v**K#K2a`IA#oU+!>v_g58YZ+1X`eEA<&kEU74-voXZoIQUd-D zPo+okCc?z(4S7Rs0S3`TnDBY!qIma{Bdqhelpn1j7lmq4*q5`1+YyQy=2&jh{o{Y~( z4|)Y0dL2aRMf(N=At+yo;*wKi*HTUHRpjVlb1m$Qrs%YE(C~XY8q*^TbB{{^Ucp1{ z7y!6QovG_qyOoIat6@~C87|@{k*`O+iCjE+EV&QHRwO}E@TSf0Wjra@PD0R|t%aS(1o0h|Oee9b4 zud7|ou?tp(5lW?^AR03tF0$y-aFlE#0XMG06^o7?DR$>5arGEn%zS6)sVZ2-)9Q)i zt{HX##(RYFSZGBfCt4n;24g}l7dE4(=;CSdr0iL9?npq$u$@b7UAH&}GUEMGZULhu zoPcvv<(v`51I3LmF;{I`ChC2-@;QeHmaJxi!hA!oL?QcuHA$+7cSt`wku7y_v zIy~cZzV7@ZgK;Xmbx-Xqqs1IU2-zTCOra8CN=UJAOtTTnU(@%BVj-8vhL4LwD$`+f zM5q1}biOw=y)bJe@6KaGK&0WUW$F6Z1a zyBaV%q*#V4Tukl^QA9aoh`(#EqR0j{K3pJ?GM7`b3116zn8UWyaGW4ENBG)`PUYkx z6)*xxC5ps9N(jT=Pgsn_0=#UpX%Ju2L84X8j6>=Pq5I(vS&O9?1*wj)x1d#xg~DB4 zWxQP1LkJjUNilC7ko+cbP9u{jQN8o z5NLw4=5^@CK6=qtG5SsYe}lfIig(j$s%mtEvha(Yx8NPcX~7(Vc#-J$1N2f$=sm}? zYAsMcwJ}5o0C5MODl46Q7MY97x3g)8l7tGZ1yzDq3^}W=bqwEL@L%v3;9eHPo)Xl; z?(70S6OUTyr+k}1=hEj1?M<}iwjI*-D$T3mH-52n;pfYrn>wzo*|>=|#JVka#@Gpm z94R3srCRo9GOxDGrp$X)%G!R9yHdI^7!GeTejW`v`1&q$h*%msPzH9i%Lgn>-#&;c ze0@KDWvJsRgWin)p=p8%@}VI#CM>Qn#pDOHMMshFtH?>ieG_|125ix~>bZ5sq+vz| zICbU&tL*DgG>Yhgg}B^iK1AvxN@yswzt-Qk$-ZP%eB^S zS(0tZ(sG3rB_<>i013_@PQ>J%>D>M0?+qupu5dr+9eSrEaOUf;-*C=zp69-=`wF&r zGyoL)rKQ^V$09HrDn{OjAa)MH)P{(d;=gO;pI4mG9WgN=X;Y6=0e2X-*&)(1PmBvn z!d;(le6H0I>5C$!)s#&ZW3*f`h9h!`;t1sy>4zrDQHp(r*2j3@nPF6}UoJ}_MCwDV zAl0ap-tMV#lK&!)T>ApbN=ibM`q0#)Xqg9wwSTXA#)?^gw@i6!@xtCTbrSEjh?h!*~}LZfOZ{CR9JNCnDIC| z(lDaJOJ+lw=30hhtU;oE^{XO4@r?ius?ehK2j9Imz~q7^5UUU#2hgC!DqWi~Vs>bu z{nbVvyKrb_!(wTi6)@T(Y4EfKIp$f(oH|xmD6^3fVS{IbKfmWu+$b2{0{ZSNL94#NDre|p)LuR zIhIseIbDJ_Z{lWyQYMKWrp2Dpd7u)lD3Hl;ohiZPIEug%>zJ7#1% zLaeGVC!to>0Y*9N>=JA-Zs}C+3SG6ITlD>S_7b$N;h1Jk0$p?XSVx>hs`z8fvyv^B z!1`#S%nD6I5Al8Zzl_^-7M>hfQ|v;Dn2{NaO(V&O^X!kKUOs}5rxBjRA6ILWs+eSX zS(QMD>berymh7$)L;@aiWnC9#EoX4Z?6Z!>`yQxzW78K>VvNPyBnY7U)NmdqEKQD4dl$#lm!XZq4A&eRZ5}~kDzhIkIF>ysrXHJZ51L=#DY^8iX zqf8}u3l$#Zaw1BI$E4H7vPuuMNdPr6#WO4DA)4dMwBBNLcapqTbV*N0rlpl8k8@8F zgyeafPH(z4g;_h_UYNBYS6l&*0Ciev!w&_9ynn4*u<5DlLs|B^%7_CN?pss=cSqIU9>!pAJGk_pSIuGO4d-KOVKVj?`*iA0hPenHhpW{%lwblQs4I zA*5{1n73yEK$m$1jep)ZOFJ>qir4!kDN%lDClW+%fH@@cLo`?{b5TRZ$-D=CW5HVY zKDXlg5YT~*#x!Ax2sZqI?R-;z%I7)xK}27ljsOA;@we3%YqQdojq4E-3~$qc7^P+; znv}SrzM*EsdF+_(uBXqMX+=A&({qKB?Yeq30rTU_%AX|!OVO*O&z+ccT6q4NAA22n zSX7*VT4AaRYLGS16IYb{=6?B+Eqi#Yoc1!04m5Ak6jpd`g4$vYw!`y6BdwL@05EIEMqG6yUiNv@b;pN?MO8iY z@I#wBJB!7lX_xU}V;6_|7c~+^DM=TmT&%DNP?eVe3YmQ;KAh}IbUc_J;QHHDeYhC- z5%qt?pfb(eS?^n#A5;QQ%f^Dwb7THpX1I_K8>_SNk5SFB8 zNN7C-$NPy0yHK`N*qyLb1P@bE>#?p2ixSs#_Jr_RYugz0q~l;iNCX)O$zn+i4I2TZ z^F+YB=Yf%&rSppqx`x+@5)lt?0PXfePtzxFFH}AozY{0Xy{kGkbMWK%%LJ>Z75x}M_BRFmoHv+HLs z?p%3z^ZWyAXUZ4WQ zYp5DcnWR0oWJ;jHxc_jTnBE~dAH)~X&Y~B|@+yuE{kDchu8@7nV5XMFHJ+u&6T>#7 z_8X5Wzu;9*F-8j^xdf(m$YgfhNkAKiht@ zh?hk=N0gZM$dkbC8k(JpA)&TRk0kdRIT#0p$>CBuBmLrm)VNlTSL7i{TyoW^OP9lL zjxk?~LOMooBepHgrh=N(R)8u<5|{kRivgT->CT)#>AqQ)*S)teHaZ$u4K8GdHPleb zs%8a((m23o1t~u%FfUFMM8*?Qi-{>So&+E#=umRpJZtCW#G;lR#~zk z^u>4HGlv*zNi}NJ#%P=SG0E&ASw&+`PRi^|BLH4^%%QwSlgq80Lxm~X3e4IPnS^CZglBpa5;~0cs4TluTPT~4fO)Zbawx(=88=?Z z94qan71sXGAWBn7Wu&QVfr&77k&L#(K^;G>Jp$7ODvCo`PvZG(mZfqR19mnB*e1 zPdQT}D@gy__RFE$y>sXI=MUM0eiNwCg4Okefp9v-u z4n-A*7hj0)8#Jk)ViiT%4ajq2!6)q}4DpPNnC7Z8g@axBb7_kU#t+sNz)6aRY)z*b zq8=sjZ=5*cy(IZ`YUUZ-ExkZEZ26oJ>Z~KMf`*)D2*z|S69abf2^8mP0sXMJxxi>lud{!s8u!#!6x0}@0Ysc$(>r$LKBk2ShC-+=Iq+~4T@U&9!0G1 ze&xqlt`?hvz6eF}mSyR54LVq|9%AQ@GM`(E_`dPoDTh>hhMN`UaQd`hVtYX0OW|6a z?r6#_89KqmX{;aFA{)~ETELP0?mggtz-I?rrPY77*W{?|?D7*Mgps#Awk7_g6)5)tM}YC^#wKEpoMJL$fWp6Sa-#3Mws6|*2sI_y zrR|1-`!!HS5e@9Z5Ya}lm4POD;I!$FvTOUgp48K6QEzWQcJ;B(JpaT~kL{c~wS9V< z9+kuFcs8HUZ{5CoE()z#~ksFYBn=V7_?EO%|CT%vaW})Bs(;D!Uv~Rixjf(NYgREPh$Y zF&8D5w%jFD4j99d-6R_&L=+h@WO+|4jY&PWF~Y;q;qvOV*LGI+_7Ijmwm1%Bv!&ar zqL)XO3uK=r2!B<;2bC!uO%ub8Gz5CyhJ_0xUfT$Ptv01PzXbjJmEgBRPGcG)C`2_Y5r_+_~f+ws?qWkMe`?}x~UcV?Uf@W9|HWl%xIg!^^dglp=>OQ<2d zz3G(Oqbfw01`h!Cl2%EEJx)6GSG)@a1f-ZVub|i%R;SY@+6Or(T0#+@^a}Ka^#Kul zPXbRe90+ZWl%d9~qa}zfIspFYHPi1abvgz|=uM)Z>&J;31UV+h5)}*1V2~^TPzGT0#ZK5t!EO6aKl@1~sa%N<-RRxG- z+@b)D&?+~ws?3XO=o+`V;aipGlV8vii27EKJMfb*z&h`j6Q3VRUC} zD~nUYFw#R^sIm0yvkgW!nRG$Yb7JRBgaw9C#Wl9ygg&}0*&(^K2VgLFGH| zoDY(k{ydT*gQXtJTC8S!0mL)wBn7{+Tu3>uGaW9h^^7ZvkDO*5Hnle~F9C-Fe^hp} z9Ylk#t%;Y2=GM(R`Vhb*ui$Xf7Pa54CHE@G?SdyDG~G_Z?2yQ-^p?&jCoUcJ z6!yyFf7`Aq=>Bf%TLe7i!SqqZ!VgWkH3j6Z7&x$| z)jzpKRFCQ;` z85!=-)N6~p6AQ!}nknUaI>ZcN_Hg)~igRv@CJiU$`x>`{&YkEsB`@!|Dx`L{e{hOp zirCw@*Y+7rd^F-%Xo}+5LBFaol&EPzLym&Q&zYYRmVZG-@f8eg!m}JB>)uo2mo@kC zw#|B#)ly`0M#g~oT&|Nw+E(yW6#L3GDB3m`h8XoRU^LdQ5uu7Cj;j38`L6P}TcP|! z!JX)rw!BUAW`iBHjq`WV0(O}qQ;QWlHet<4An4yUa-`%|?{3~hj7%66=22qNay%$P zQHgWu`P3*ZT7{@3=p)ZQM-aZFQ`LZ)*W|+#<75WV6Ks=UXY`p?DI>nH=n}9C6qOWh zZ4B9YJWG8>5t$wo`a6(B=8z*XQ^}rk)truU$Awu>9(zA=PGilsV)nQ&-CGYE4b_HY zdKmqMK3{iQV2w5NF+R2MAQd#CF9au!3~XHqNdw%O7;Sf|a^$iOrG{A6yzo4w5vxF- zWctgu1)|0#L)Dg6i$5uM7RkXh5s>AT`r5=p(#lp8wP* z@~pUi{noAPw?Djg^VW^swjEBNIdk>VE6=_7>@zPuclN<6)19-lN1F6Sv0OBH-?!be zDl4vL8!c$na3fHeACxpHC#+oL25Xx?qg`fuX=q`5Da?Ph>V#G5VKHewWlFe$CL>93 zz$ol8C`|^0E+Ka@P%TV*;eJL*li(#98QMHf;zpES6g0We)c3#!z}rg)D8*^{2~ERS zGiAckFf4AP!KknTJ9>?&iZ$Iqm<*ZZ!$6S6C!nXP6q9jJOEMx&IJggok%;t|LY_q~ zRFP>akru4hEX!y7oi08IgH%-{sMXfV?r#)i1Sec@169bluzT)$By+~<^BJSvFDQg; z9(|g-l9W(*B>w3^!Sf+3)6Kqm*_d3LDGq~#3f^s)WT@IwgD3%T%?Ig68ishLI%7x{qa{wW-2S4{}WMVkfzpc`nG!U(j46PX~~sAIBYyg$8BlojC? zmWu6<|2!6kQ6mrb0(wpyh2X=aKS*bx`OMKOnpY79obj#GT}_`janRz|ymuqLE;@}^ zz6m}`pyIs^eXo)nwnIK()vfz8fzX#?Fz_sFe#f(0YKTrCohRT@sqZ%Ig=d4yrWW4%zC z@A~80VZenUSA5f-S1dZfjruT2FIjX%cv1Mi zGAT#9IV&5PhzM(U@nLecy|dD6nh$QtMv#mMVX|CBV)h!4<+xSD1!fj$Y%bR>F^AR9 zYi_0U&y;(uM@jxoNn+at#&zY_&CTj zX#$9Q2-$@a*u}y!+d?~E?CQZ`9j}3Nbf7krOgBgf>>gxqz*;pdw`HQCcjaIzlvX$# zMiAY{IT2h9A%n38;+Nzb&d^ZOTsAcB{0#JZkBW(fsL!V4lbQiNw%TzG(j8RhybwgH3j~LyJ7H=FwEMF)K_0BAr zH^McQcWpqzzWJneVCD3q4$Z?`9toP-6g_6V>f$I$S()O}%ApmrH%ZVDe_+-{0@p#< zvFRoWeSzX~XVSL_x5YT8^plXYx&pNj%b;|?`|@O#n=xx}b8e|K$~&lHxz%-|m$-Y6 zX!(FEwRt;+1jHBaof6Tyqz;u30Wp3{%sCY#AA>9h=>^E1sBKmVB|ZnPGTKES8hCE) z+YtUQ^lSi?gkXh+>P{VGU8&2fK{QW5+kn#FQBkr+vkkCdACCF^(6Q;YIc`80f<{O^ zQXdspoqx#lgQp3*NNz<&&Uwd$P55w)gea3KyuT+!4_=h+ay(PKEql5gkubt(41Dn6 zu`-R%JgMz5Pr>%vXRYZ!3Hnq$5GtLNVi6`-gzPzN#O8s*KlByk`RMcGI(2*!`xt_nL^cbu5OQ4t?_M4SX+ zwWy0o{?dMXPVNevg5)J!iJqRHDSbf)aQcQ>&2pU43)swZR zD<)^JeBv9w`K^EY_2q2&XaCE0fBknqJGy*g;;Q4fvD>qsE{hKw4&stVT4?uGsS(rj5wRD#j0)w8I!`DBp3daFlA1-t)|=fS zf31%xGQz4TM(=WAi#|5q!S)mJ`vHj=MdZ!*MfOa}O|QRfU;)w326zzG=q{1nGO&g) z&oCg$kgEh6JoMpsp4JDMD$H1bZjh z!scmpAsmfXcPkgqfD!@W7}K27|02z?bD|_r zWPw6po3{40{Zl9-D8Z^*Y$W6xte?xzLqFm2C@Y@fRJ-z=7VXFr!iYa1FP$(boyO(A z6|bhhXBK#b_}Y^};HmXv{JF;n{+eEre0dnLI7yQXKtFHg`UZCP#ViE&oGa?@r0eF7 zF`$ByZ38Jx`d9z5c!mC6z<@(F&acC>AyBW7LehrGYC|q18Bit*x#;~|3#8Km0_C75 zqyd7AMRnZs1%-#3&g;rG?XhAug!C~yUE|jx3M9BGxMBfDi2V-dL%$rWx@2ZyY^E&A zdLq~_M9|T12XMB6FQh)$m`hj$m|_-}$ApuT(+poAY%;PAvbIykfpnlz8EV&VLjXz1 zBJ?4Uy|9g=6b^zw8RdM{MMoI?l0 zL;%;>+ngPt(w#`QsN-1CTJF)@R?;T2rCdZPVV76Pllj1HO~&Q(uKAIltb~n*MI}xB z!$(vsTz5j@E8%QoQOEPga2)dY~|BZ35Z=5*V z6z5qr1*A!EJ0wx`Oqj;&kWey~MJ zQ+f7WoLKUD>db(Po3#2G`f*wbCb{Lmq0$P^LJ^0Z3u#_JL>CKu3;B;2x>A26x@D{y z_kci5U}LRO!lH8NV;4~)U7BiJ|a@mXEX!Pa$gB(`<~m7`0_!Q z6*9mghPX6!D!#FXXYGOs)fdD6v`htFq>5TD82Xy-`~#df$t&4G`yaW%q(ji{ix@eg z(Ai&69!UXMcq5mwaEz{^v2bhSJu5$h+r@@z8p3EPZ>$CnTex{9Qx8isB965aqg1fe@FpMKBJG`NVH zqFW|2f}*O2ysEa&J@)0V{Ga~MfB4adxBkQbB}cKuP+YwhIY|)ZQIO?p>Ix( zPj>I!d;f#iUi#&)Uw`xd-r>1(=bwD~;ZJ_{`K|L8`f5Ed>aJz!A$i zPBF&-1zQ;>8)02zSCc$wNXlQ?RkTi=*`xA;*Uv)=Qc&IO+o{xX7?c$ViqpQqN0kt4 zFkC%A6*x{W8{Zk}0yS+R>KGeSOs*4iD%$E1kkx$_X1D^rg)NS^OiGeSM@kTGd?-u# zhM|B}YT3@0F-bRksT?LbI?~!Vb*FL%jjlN8h(Q4`G!n2wnke(jtPUKab&#&r zAH&IFz!0pUKzM=&=+hx)QR&Nzoe~q3`1Xka8q8i-)2^5JBMjG}Woc?o zLs7{}(44a&%j%6S2)q_2_Rp}{ikzmR_z<4z{>|;P9RP#3mi|#HqACvzxBQEN5Jd;N z^83m8S8-s@&r3`XHdk_mo^l9B@~QxJAi6^_2aZumWx42=*Afp9w2CZz)e<7hv08W*a@!j9l- z#QHpwx0zd}(<9n`KGq#aF7YsjIS%p&%APX57*tQaHUxp@fdRP4ob-E1%T@Z2r86p zky2Ka;P+Wx>BvNobqB9@zb4`sSmJv+7htc8RhU_c9mc69m1_`{QZ3BKT=GTfBS@r? z(TfSXvV2Phog4Fkz4lwJ|$ z@be?*Jt8s(TtnZF(ON$?MER=ZC0X|7^(Dbjl=U>(upnZ9{f>hn6!RL}6+{>DPU)`EwOtxc z-s5oH5Y!mhPGUqSEwtQ2Qn4tk$>4zt(CB!&qSHO|re)be${eB}I9^$FnK5Vy*D=iJ zeHNuvs*)p&o#0;ptb`UB7R-~r6`lxc)f{;!4Ak$)Ns+z@1GkuEEoVIfF(w7Lp-3+H zDlKEK>)qL2MI6Ysw4xx`O1ZA0>NOoRHzApsvse$S_|)P@3vHvu0Sk{A4J4GsfoKXS zP1?gAGFTr_yr&rni&u}h!j8sC2XJ-3hAClCf)+gY(Ue$%8`2KkZX1lzYxEc`Dp6Hr z7ER~{o$4=u3P+-aqgc|xp3F{p9}A3a$1+iW8h8+eZ^|+i;WpIvK~FFqC0kI|r69`j3Tt)vuGGBgcRyg_1H)}%e=sr=QT zv75mnhf!V(>fybZ6RW_!JW0x}mIkGWg?xBMlm_Glo`eV(!s}GBZS%;S*QMr46SYly zazJeG8PT?E0Mzt3r4EM|wn{4?$xLBZOZ_UWnnZIZ#nmh}c{^b#eQt=l{ij_s^T8H z$8E>aAS)2Rj(eC`C_Xhfawm;0&?)Vs^e&8ed)~jH!-tAm1v`~MKoQ@JA98_X?J27+ zP|M`}BBBIA5XsSi({~IhQIR&nq5`VJZA_FI+ivxJHJw-yn2Zc4m`WN4`h5@y9i`}Q z-L+kbE}1Bwu1@hH%uw*U?Mpb9^W&8qeH+;07N{pr-yGv~dzVt%6^~PZz<~;x&HzO~ zy1zq}Wz-OftHs{bV{>kgD(u6OJ<8q)M8L7g@)*saN9B_5iMk=xBH64)Wn+kLE`|(E z`6Ny!SzdI@1ymRg`oP1S#KsBG8Nu*zMrXE+8+h}!q9XLar099?p3w!G^WJAYPwDUk z^4?Z zXXbrU5n4^n+BkAqUAEaiXJr^+vR=ZmR#X>eEyqVyl`f|+zjfDl zRZ+rLsycO*peh>`JlK39;V)tVKX-hgZK#2)>36J?LhbBCOm!zb{!u%TRfx-{KkMKK zhQEiN0RQdgjg;cx<%<1n4zR?o8bvAJUPA*_4)B)}n70Gkte?!4W*vMc{S7|K(fYO!5a{Z9)4x{Fkqf z9zR|T;e&EclEbXQIZ@ez-6VJ}&Qg7^v{8r0$LP5l{tGeiH@iu*g+v}tqA^ufA(2s6 zBv{J(tzdzXSYt_>5UcR)Q~@fEwk9Fr3XVfsqYbs@n9GIs0CmuigisQxj^O-_NfcNgxKDuv(rq6NA z@&8G3Bn~VRad6aeuUW^#uh=wxt=<4f9o(#6@*FWLP7RdR82Etq&lBz@qkdms+vu8p zLWc#l)G^%+wz?1G0)&w?x8W@H`oa z%UW3(#=MrlN%Je&5wXMI)XBVBT_B6-Qa2JqLmj0fHO(Xy6BrCo!R08Jcqy7qBN5l| z@l=^ywVL|sRb=z}G#{6RML?eTzlsp&Z6cG|iXDBgzAvk)tdJeUlfNwM%7XZk;e5od z+xh(X{{G?qy&*3yT)BGo@|EfK=`PC}L`HLl8#W(_gDZ0v)ET4=rWn^aCR+x{*w%lm+MB6Rje=~vr z5=%@NmIw1@e}y8ML`+WM7S;D=tG>MKm$V24X}B z9+01k74+#!Mn5~!7J_1@X-tkB&(Xjo21G2O_{sEqRq{Ct^{O51w6h`+!+an}^ zx8;Ll+%gdMG@c8PRK2{=zGQ|)gG#&T#j(iM6fE#mV5TvNy9ECr?UTvBBbw9T9(ty2 zK9Tbn5>JvdG1h<_BmhM5OjCM(d@~(QX40{X2UEefqgek3P0_;X&dQP1`hLK!6Vyj!(=9&LImS zvdgWN13%%~c+g4ti znuHhJYH>1vpf_TqCI2kxbyNbma_5>eD(&ap0X`tKh8KW}9AeF^ld=EMjaGxzunORI zCv(}Li?iQWtC;EvH|4Us8u!>pLqexS3?*!YKuIQ>+YOpGFeFE6hmSJaeh8w_>w(~$ z#-6Mp*%mS{dx!)Vi14Q32baMvpTTj}Ll|;?8J?%r?$R+D_%Wlz*rqu<<8UtY8o@A@ zi}H%Yt9Em?G-RIDl*Thh%HjvBUcwO|Z74j6VJEL`IPsJ`0N{lUM-p{+flwzIjx~sO z4^7p#CKx*FO`v4j6swlNI$X^TokOo;ZmebxylLYgsC+!n(}pYex>!vLt7u1y))Et{HS)k8UUAKzy(qXz|*EdCC`>q_Nz)jR)ue?FUxp(yWIu5 zT>Ym_UbNbb4I|%u1v$YhJC`tZ&2Se$yQ{XBn>J)+eo@(i3e%` zCAjKyafk4}Fjpdm(6=p|R`5Ice_gZ8i=C%}f*BbtaTM5HCvZxOOC3i7lr{Q|M0k<@ zP2eM6kbSpFfX-%9s#Y8*F%9suVhx%I^wy$y^+zLaHx32-2*#CLjT4TA(+5<;@pXuJ z9mMT|TBD;B3>#4D*pw^JGD6WNJ7@Z?TO90aW76A-H5x31u(o#L>a{KhFh1(sK$s{W zr>g)x7rItn^6%(d_&tE%*>Ng}-WueN=?N(q&s60^5pWs3LMK@vm4tOn%xDsOm%&#b zgS0&DaI{sJ#9ChEvYk8}nND-v5X?a~F+rZblYL8E6+Slgq?oREv%|=jGVmEb*Xrp; zuiG?9@s}RqJ04>uMH_!j99mPymA;qCu~gLCr#*Nw@e$mC35v86N;GmD4G9*FYRzqr z15kM}ojs8LSS&&ULHdsv&^bjTcE{+voGvLO!Xh@A+}IN_hBqtCiMmO+=i?G_2SGta zL_|5psf&;2F2yqi1BvbSxF|g*wr>!v7wP&;62chE;}xr1OpkK)StPzy;g;93QIG9f z)W&|us}RTq^UlM~DgtG|XP2;v9v0Fn>CuxreB9{KqDulqfo`g3B2C@SGiE(`A}=#@ z+eSIrop_e#MWmkE@Jv(ga3*1#9+5Z&2y&K!Yp%HpZQqLu?*hwuw3lUFVUw>y0*0!H z?2eA3(W)pXl}4RWRaFlon)XP90DHH!rtSR`iLc^2subw!+%RVCB%7|x6K5#D!>L9}6HIL6ID^QA?`K3N{%$3t{G?YT37;RI|6F^H?GM z=8U0}3f&wFN==zbq;3S0z?5j?Q7=npop*H6k4-7KV`3O7JSo650i7ahuOzzhcq7+F z+C3G55so1#VobwAz2e)&!&yW^8&CMvW1IAUhVI014^ciRwQ3p>c?a=Zk12!kF+*ZL zdI{MUov6LgMn0HColCXA}VoAx-}KU@ZmXElQ-yG%YWSc^rO!S92e zQn>PhosdkS={X{Dxd2}$)e_hui9lD+y?{Jzg;%>}#_47zj9Cw^G-T>M0#mlu5gQhu z3NwY+nUK^;^W44#OQLPCIhOEjbA@d+2rIL6N@Fvy6h9jtM2d0!L)>`c<5=5dtNgx+w_DY@HY4%&6|?A9*&eHcA`)SU7Q`^r6K) zG8q#|p%0xk}Z@-s;mv;!t1-`>y;$&WN+;`c=L)3w=jZ6`nV;FtdBTVMbB zXa4>F`+s@$&%QI?zg<^(k+m&Lba6_HN<4M;V^|(MfBK=^SSyRFM}kJRoGg$EzI+P2L{?_b-yx7Rnzwr#7jTrTE$mAA|G`0%J*F8gM2a&**p4Oub$V%}7f zqFpX9vTo+x$#LHU^Z@M(#6%`IW?4~t*^`ri8xlLVYe#%W)brd8*wE4SMr;VNAZ33N zCbTUWoC?dvZrR$SJVVfh2rcTJV(-G$lbDU8ly*SKla5^_IjGi7lDcHVq;#wp+qzIv z^=KIbG~l3-E}M`VscO||(Dl1{VSKQCORVi(nGxG|MGo$^f41*H61j5Lrt%=_vv4?w zw9n`SS8T=k;F$&;&4DN#(coG~7bXKSnF~s)eyEvtil)`75A(hi$56}u^@O=g4tU2B zOR`f{@tT+9^Sv9&=~_8mYfcUUX&Ed@+H14N9y?neOO?q39ybfW0+~0sBOY@{h%Yu4$CQ+Mpss9@-#SFAwHYDq2fO1Q^tbb zNUCIJ1(q7G74yVoIvgJ;3&?%_{DrI=X1jNdFd6j_UzzlFK?@*4M~X(Y78(G>^*8rF z;mTu!n=YxE{DAxY1SJMwv{n(d%RAuURM`VY8~1Tqzkvh+Z{c|uy7lO%oEqRMd0y;1 zIriKJjgqimt5L~lsr8NOMI7iLc_ebIUnC_vB>YV9q075q>;);&5TZ|(cvL(mv;Co* zUPskOYLA5wM$@R*Q9)u`o$=>E?;meUdL-jX8}FcxR#pW?4FIB99_^?16o*jAW)P>w zyPTvP>8z4o$zNJ$Z$y8l8P^Jc;pt|W?xx8_JOJJ|O+Fowl=OYXMz(e#x_6O}w2N!a zq}p|~do{zthWB1vk#x!pNE1}mG@eyzOoWLpO*FW5(tob&+m@+1G}P6gl8g^ri@Gc) z8{O>4*37XK!^$&}&XQ7B#B~zM3=iu!LmvezuaLEHfI%Z>-=fjM$kV#iL9LL^BGWZp z;iT`0E1bj}MxCq$Mup0g$qZGuWZp%RnVE4n`;f;j8L`G9Et}@fBZ#7jRp=-Ldp?M4 zp5fd(@-Mr*n6RJ#a_Nz5Y=Zjr)Qwo1qOTTgW_2BgoJ1I)A5Dn)iN|XOBq++j4^*Utk9UMkT?(BM-9xEWqK~VY5&`2LZMO~I{3v`;puDq(Ta?0u2#^(0<3l}y|oo<`%@bKXN-P6gm*n1&xCY%~|Z4nnRami74m{BteJVc~%U=tg(dZgiRA^ z{5Gf1qpzyT=Z_Q(1@5~}0(K7UQUvCD5-x0oOGnYj;v2Y0RE-G&wU{!f zQq_rp&l#Hym} zYT2Ox)21l)xDW^XK##8K=60x83z}0h*7j8)FE4pC8j($h0e}zNZU*1QA#-EB;kR4W zaQiq5OHAE{k=@|fxfnZX!wIC1f6I)%a0FF)q%9%5tMiwl#!UTaJPdrsdDB(g*i(gT z1)X+;g}881s~LJ8R2 z_kQp5Kls5QZHi)TI$6$_<#g@A zXPnZI=(lV!51bY;ld@@=X4VcxKAle6 zVc5UF`?DYZ^^MnmwVa)FLkqG7(cy^qNb_cwlcW@gS}(o5lU2Ecpz>2+>Hbbbi+Cgn z9Jtb;R?F-uclLb;3WgI5iOCzv_?Qltqhf=^b|G@7#N_SU@DmX}eLzOQ-NpknF_xHj%$kE47KZcl%9ZyEYxe6^S!SrGV_> zrGl#yvKL(d)ijbR7iGD*Gjwfxe8{iQu}s*0hL@gKOVAzd7#uI_ttpu6-cAB39H$6T zGNuPP(o{XW9%o4_RIU-d^o-t^YSeQQuo~NvqjWe#%dUT%ccsM?o(s0n#+T&K(L?wU zInW3TRt_Z|=o0eBSU4QlbQtNP(B$!~3#+Ao_nb_Ivd-ow+z|M6M#L!TTRDl43y+6s za_h8Q$DN4k6w|%j^inXv9qucqIz zI-RmTb|I2^YdP74(#UKyBifAm>qRZ-wK$$#sq!S|iY}0QUW%)pLRps%FG?^OkY3p2p z`qf@>avr!*F!!Y9@5@5^DGSlXIkjv-!(Fi<(twVu7N#g_Y)HE9yP}+sw%rbG-_`Ym z%?#>WbU@uuRTY?UZCll##Zn+4DN{FrQ3!m=&Rl-z@-v^>IeYqGZ~xwn>j$@Q7eh0j zoixpIXl4Heb%184WmSO%XIeX173i+<+1j?NYlPzBjH~NMZBI)CLtJM*8>yjA zE8tTMgJubgh1#Qtg zOQc}N2+FR&PTOWSWs29abchcT_0_6A*-MCuZGj0dO9%t_pS)lYorUSFW?$aU!I&3K zl)ldX1!=$8YH(|l&pU0T1Caz8C=VTRL5$}HH3qtks-~Y+UDngAs4~>&b<;LgRkn*c zp18hk8vG~T5Ee)+3CxUnR{Dqno_nGa1ok{nwjzuNp9on7#zhJNg(~i8)Zcb$kU6o= z49{z2fq?Jg(XW9T7b(8sQL4DOGO32MU*7>r5Ad$0D-C^Kp&UwNPw~hyicIa@CaOG_ zkIa*mt}ODrl~XYm4(kuJzB+$XCK%B`on-a556X zEv6pS3ntvNFi#G0RP;_d4c(i{TftKisOHM)iI|BeEY+1|I2^7 z_u4NPCx_S@M!BfFWL-4yq$LbTbr&=DTbQVRo&;q+GKj^!3Vmb`|sAR+QzVn&2uR@_qlb&cy~_eEwqiZtI1Jt$lx z$}7cRVbFEx*p!}b=+j|Gfot0sLL4~TFVlx6VOh~d63$B~ZxWD(i(b?q0^?*j$SPN) zOD%?##!na{nRls5^SfIeE6RlqtSCYWgQgY|yHJ>DhGtf9v#v%ocBz%kis@Qjl+Ao5 z1*i`b>!#fRrM6CY%S=H3SlFR#309cbsWnRJ!fH49V44nPLWp^*ve5Ll9D`wDxFc&` z06edNXX-0n45>$t-PNRHty)7V>1315i0lwuMf*PZH55m!J0s1Pl}9WGCCb*F&d1MC z)J3(ulXXLTbYSVdbx8t$%^1*07o*vvyN$k5T}Ci3MoN1C2BUB!p;1mGO0y7;fIK^N z#(B_Cqx+1Ht-d?)+0xGHHX_ZFA+n{Hk)zvWS?jhnktr{b8uWQq#M1SY)vBhH= zneaBmefe`Dk0@pWLzV#oPVq^ekTGu13>{hLCGEA-Rjl83&B6PUoXvc88Eey|O?#F` z*%ESaPYOpWLm9k}hE_Rd8c9|7+u}~jqcJ)%`*(x*039q2fBE~<;uYI#*JWLgL$z(; zqqrgm5k6YfbzZLxi(@uRhFdvF=2jKir70VXErWUo8we&G#dHap`rtWdeS*J*>_D{# zs-L4;AwClLnwDI^I#Jeo(+?(yDL6WT+|;-z)5$`r5L}>S>6rKwe(Xcm$5ByF;s@ORa%>dK60s=G0A0m1(Q2KCxW5tsz95DPM)oGxJ zEa6^dP*t&1EbnwB0KgGfO0Ehks6F0VorCwT#Aq{PAOG56{fpxh?0HO0Ff1jd#Pp$< z3&rLh1a`JGa+UQiM`5dstPMa?oe}!!(L!IPi3D>F+8Mc4ri+YkA!>D96-Cjuj3h*x z(@?%gn<ZNwNsrBfpGEbv`K^wWpE1p8rtlhc`;h zw$ivB-Cm3^?66HZDlGN@;6&n?w^#5knb{|H4t_r#MKYD+fk;Fw({bI%Xz=ZMl3}38 zCM>d&!#1j!xlzicL_0#9tg-(XdyP4v#*H)sR;fr^N5|IKvffRWeQL)GsfK`8i_#e3 zn;wPvTH93AHfMI$G1DV7!}JWr-^4ocB~^(=dO10uCS$Rsv<3t=crwG%p3Ps@NYmYb z4`)tvvx3QfV%*6WKxK*!_fVjDpAQQMt1WyQmhy~BJSBX{L;w&qO6(g?xNWxS0}-xe zYM5gXFSo8xX{WTK2yM|m5t_-wKxWhm`)}3`bxruGs5Umsa~HNRUs&7OEb@GDIO`V6 z?qoSTn!&ufS#(WX6+`egfxfP7k_bsTlbi?Hp;U<>cyH^6& zI{UT8+|9;1@>}4YA{3w$TWkO(u!(7=ZPFre(W8>#ljb=FDdZ|0m7I}iYHq~N3)`iY zQrMY@g06&e>iyF6H#i+3JmrpLpI^K9fTYIk?C5+<3KZGiw#}ZEsBbWif-{xeCC*n^ zDv?7G=Mf)j2@-iDbu(iaroPe#rTkAq!57vxWbcheOV-AIWDvf++czv50}IFPAhV z9$={HSSZyGO2(H}jP$}XP_cxo2X)0-jTMy@PkiRHzx@aQq^#;+y!?xo{_H=^_U<=8 z!R4RG(>#%d$%PSHNnVPH`@@8UR09T?SCbAkpnXfdp`9jyp;#bi3N4G!NU8F37EQDG z0(7&G?Sjlr=wPjun5Y%KZ^>N4ersIFFk{G7<5tzT$;c_LT(a~^Zgr{S_JhwB9hDMyMW3@{ z!5C9}9dejYIGir=5oCO(T_;Ai&Vo_kG&Ns(ww&w9LOL!R3OT#Wsb5Ik>Hr`JtVgC= zSPTSP-feynAWTtAPMyk!YQ%^8FXeL1Sp2eBku6o^L#a` z_jpPYVZojvW`0MnpMVNYF(P?(rJvNJCAm-<-FUu(Kl3zmWlz$g3gY-k0t(W~IPdqv zV&KL_);KHR>?eL66ak~8N$a1e0*TwIHVnaHcG2+GDQEMPTOZzlL1yvlTVYZ8pNM`7 z1A@3RWDd%e#O(KQ4KsC%bg!hp^;pEoGy$c{16Bz!+)_17#)@bk{28D2ZCW?j1_ZLPN?16a7i$|KBkM1Gqf z%IdHm_$0AQ=WB6vAZi6?H8z0ck>X5Rdb>2XUP-LuvRdETuImXeNV&eT-ZsnSyqTRGEf@151AoENXI`8kf&~?w zgOCgMg{_RiNp!BN$xu|)+9VtDu4#Z+%A!|cCoHU+Wn0$OWUU&8e7We#Nm&E1C^ybO zaOK4ppML(?b62kPSus02I-bopPo2B?_!E!5*zDfhJ-okrxVwM<#?6!cz55@1bh3N5 znVpnn-Yl1sx@fz;YnrN_RMlj8dIgv&G5DeA#vD z8|C(?&B^-OrH3xBZEr3+G*OdjegE#>&5!QgyngHMwd+TBZtq{e-Y(}ulMn5j+dDWC z8YS6v3(3R+l0IlcISFPl7u>*TG7S;AROD)cBRV!|3xSenxSC+zvJzHFp*0iN5>O`n z3x@shP}fV!5)be#XZ3va+0HwMTw5e`)p`?oS46ss0_m-+3kxl63MB(ym7Al>D2pFw zVTk}OX0rkB+;e{n`Fr)-S7dCO{3a1t{S9z#|TjAgnEL#DO)~ z>n!$q4l6(<3wSI?uFy&~Cs&dV6+F+PvHHlsAs(XJtI(7=sHDiee^g8OkQ_C)iu!LoJk7U9{HCk1Ka zUel$(>_r|da(|Iikq<;Q5&T=O;E0~9S0YA3QfJrp_IGFy=TyPbqnk|X*`h7ir#lxe z?L2hl(o;`;{>z_w;^DLVd$Ygz&PzZ4?q46g_DbKJAR!Z2fD|4wBn9rTR7LEQU51DX zL5-sIX$u`d696lLq8?_p;}%Snxy00ZF_%?5Mn5d;&xWTzz~Sbk(MaUYzy0B@4?p^y zfA$Ao`pOqBKXB>K{{6q(zy3Z%6fHa|@$I_Sl4$Y+0a+Jd*|6~--5z5zrI4G~0BED{ zD$2@wKrE)PbxVA19P7e)1M$N@aB?x)3Z+SO>#U~TB#5TRO^Of$$#g{t?|iU8K;uJ3 z7Z`SQR?6}LWIdUh5as7ZChImPiYf-V!hixuau;3<<5- z2{%TKQ%qeIH!!KxBX}aZB2#*8xb<-Xw^?2E7c>|uzyHE1E_8*xc5@Av!7Z?L_Rb%eQ)1RUwi}@X6enxIX^w(%cyZ}OGqsoGuPzU?c zN#95wp4s4`1Tvuo4+ey>1D{7WXN#_WR5FhlYrZC~3F!bA^2?a=@I)k{pBf{psU>e# z!!JBukc!<_R)`*EQCs&C7P4W3rT0x;epp&+jikug5v0*W6uPOT!Q$_;vkXvR{Ir2A zumh>LPJ@7aydP1qh57>W7Y?@0jG8ttGz;m?XjL4 z7AHA`NI-w!=unG2Elm&hkr5?raArHj#u4@hLHF^L&yZw5yQUJ`$}RzSMizr(=FhL* zS203P*0BcOC$@D!u{e_nbgVA)1oWVew4hiVRn4geIFLaE4?{`I8e*GdF@TndR&p!k zC@mwMw3KHj7PTnU=3X0s)+U(b@QHHb_teU=r3i~cl}Bl>)KeES*x2vH=G5(yh$G=C z!C^}-YLUCKvL_INaFuNfC#xw$E%PlfP)VdVd9qP<9W>5jLWisY{s`5im`5Qi zy3g{(e0H?EyF58zN*rA7VJi$vttyT_lo1dnAtJP%oH}#vk*Cf*`bfFHUe#;!*+ch zGO3f)+8M28^(3A<_25 z^;-wmZXVqDXzzn}Zr^|Z*8FgPIN5J!2i@W%Yn!ZFI?>Q{9D&}70)oX#I?hJRG%h4Z zs46yy5yD~MYh>1iMofERiQ6SA?ei-_;W)E|*OOoA+9O81YLZ1j^SX};S=GE&v})B@ zh^g3-XQ7@uF|k#J2cb`%5I$IvJewG$=c8JlL2XV|xCgsJy{)+yLBL`x_IwKBOVhOk zJW7{dmhrqW>407zpx%^2kxkYnXV0&nJv(%HGhc3>J-vDM^yvpKe)6-Qc;vzJ&3v)G zvHs5cH~#!jzIXfQKg~{d=kvp&>x&u|#cDeupj!6YT z06l|uY%wBZDnz*wW#6Jlpa+b%NRCoP);ImysnehR#y5ZCYri?4&;QH6`*-jE@~6V; z;bA-}yN0yA_%x*ZH=2RE*@vtzgc zq3W~hM+lPRaAjaj7g>Ga7Os}ETnT}(=dz;~4u@(zL1f`%+V|PksqK1gJ*(EH(~WHC zP7e3)-FUy7o%Fym9h5EtskXGPg$D#^CFUFwji8lwBz?KV8NE(Dg|ek}m~O^?ICg(2 zVK^0sG2~Y&cB&BxjDwUEC1fh-f*9mcWfa=!XDP#xe=FT2Q#Tm-ZULNlwE8@(fP#e^ zucb@k|1`s$Um?+`$0jM9!90iOLaNr*va-UZZkDN;GB&{Xi*FMRnXiR(v(9+t71pCq zdJo4=3UN+IhZpVu{W$wWQr{InBzp45>WIclgkC)I32F%rwaN8XLZxCkD9A}t;0568 zpfW)9VHoO-6qgh~lDcx;OoWiH?n}`E*Z?w3L^W2Z>r~ zsA8#q9M^4}v!P&!tQw2UR?1_4*fftDV}pb?rhYk?#`*;DIvOYQ07wLduu4uUcqs!& z3Qt#HWmy@3Na%p>qI*oeZo;^&JB>a+z!|IZ?BErpp_||!LK;l+L6~}IpJf`?yUq;J z$JnhVGdZ7jabApY;pjy158;s&Ka0drh>@*9NPo_8ow(mg*1n9^s>+R1z><&l%=PmO zJKj&wnXyi}s@j&u;666-v4f1u6ZF57g&Y1P$+yF=?@>9$1%YQ+rebGLSuu~V@2?qK z&3M1OvjyS9^kAWSAt(rsCf;BEHmZQREQ3EBRR0KD_pRr&#ON|Vr@x2zNN!?NouMbsabJv( ziM1H06Qh;Wc@&XHBWxvnM3eS-%v@TCy)0seI({Z>$CWpQgrm7s=Xrjp$1P~uLdW6g z>E^~CBvyPRqHs;=PXf*5=d1xhaAcu?=;-h*1ZG_pgXJjkA$Ua_g3JXLVZdj}{m~=E zwSgys1`q@W0cGL!eYxW)4*r!0HRC>D#YW=ES^6FtuQ;`F`%1D3!uu;(Lb#z)Mw;@i zxaNH_It0t=M^ErH9FSu@Zw!ZXD%*Wl$!yJpL&?FEo9Qk$l%cPM8~h`=Fa(t zuB>ft&yQz&_wFo?_M6!Z!ctC=n#H1;)LC8*O;=2}&OY+^bHDwM9{bcYWl^3veL5TR z`J!oX^j5H0XqqzXj`oj^_YY<#^ON1Zlf8p(KI{9TI<mydZ@(zB z?X8W;+IrWw%Vm48f4G<}Zd|{;d*}Y$>o;b*yF<5F9Kn-?bPRF1VWd}-Ao=t|v9Y}| zRB(wn|GUUhVL4ok{5%= zGU9g*LkWpBD-BtYU>pTmO~=e?*Mg(&H4aum1{{=e$>2^)bjngM!*e7?t~mW>U@_WF zQ6r@K=egc!K1c|4GSG>~E~4q&kg(gy6N- zBs;7pFlNNofLr5H4xV(HaFWd-+LhW#R;kLmGNB*ukNw2F3~lG!fw<+2u18V&i5?QY znI2&z=9)6YZ(iXxq1MD+0Q!)Q0Jq+KE6rGBIZ+J;atXIJ@l7~YE)*Av_(Y%!6)Yjy z`9U1sB1D>=wt&!Rd;-L(tm?d|077hRlslVOUbynbFFpC}LuZP-eC7JyE3e$x`|#fU zaMt4SDK}4VZtZMdx^ni>ht52FVdMNJ8m{;6E`Rds?N?rU@8JFG!_nUIXuq2s7yS~% zq{W<@2U@$Tt~i>;g=`R|q3YL?I(g8zhnFc1XXYMTFb~2+Fbgki!C=}vcRm2rCVK^M zQEZ4b3^r}g@< zzJ1~O7k=+weCz6ir}yt1U;tm{moA+{tVN#P**$sb=Wo69#@oBUe)H(s2kq>juClIY z?uooqk$NBQ2D~F(2YP{`9a4#>nv}v4i6PV5>Xu7_B`Kf20`NEeUeDvya(F{Y@G~NF0yyb@0@+$!L3v0E?vG{PNtjNo9zPR z|H<0=V%gE8t;+J@7cc$Y2fuo$%t0PR@&$>7f`D;zyQT3gjfTNf<;sIG7EAVI0i#Vj zite!)x6fR%x3f4@_Obeb8c$n_ghV(BdGGY9@Wh!V(IN?x+<8VV6i-a#Q0piPLWv$- z{&ng3(`hOXYZbMch-o;aZ6QkO$34wil=In zS|sANk7A+qW<7Z>ANs3E7m#R3<`r!0!f|8l|3*r{$9vPHH%b3vkRl(M^FXpsoi4JX zIoRjakT;ckbyUh>hA<8^1JOu11gTswZNZBtF}H^F$ck$Nl!mlLHftR+6kjsTUG?DorE45(lCD zH`Anv%Za2U*nqAriEV*51gfg3BbT*9trdvG`cE5Gk_bi9_? z6Ha?hScF{A)41Uc(;9CPU@|lq3ha{L$jgOs3T7=Qp-SzkmWt^G0J9M zDGB>^fJzS|5;3IY(Q`*WuT!v zpi6sGX1May^XPIJ>4AYgOLS@tnS0{Vp2(Hn#A96IeLPISin?MxBM7>@-MVrb>2xTU zn8?7-qYK0*ub$+SNk5y>t1_MtJ!&h_MS;R7b~M>PQ1~Vva=~7amf{B~Fgr)bQV1_j z0S&997)+zqnCV+*L z=ellafbUK=w=P_{x^em}B2m|DIf}hIyL-3q z+k`oli96nx88p3 z%@1FBZGQi5-{2e`*oZ}j3QW`3P@@YFOM95q7ax7(!o!a|`H4rjw>O$OI1V4acjIt> z|7dsbUIEn=!r#_a(UK;2}C-oJzmne73w6n z4Jy9vBY@eA7IwtfsCNy?YaDGHbW7YD+O3gn7MyWCjHz;@7+C8vffeEnXd4|MRWP=% z?IpNtWOpSyFWRuX3}z$Z(AxxNL-$SsJN)O!C60Ndp9uQigT%etb&N!!)vg!B5;_NmL~r)Rg;&Tc&T@R>)i?mTpUbDEde zZXf>W@2|c6^LM+ud&9DAmrH;nMV-}UUe|qH=bKy83uhjE=E`TDJNKDKw%4=v#$NN| zU)*`)7uW8+e`|5~etWc=4|7Zu+XiZ_W{Ia54~r(?9n2p1Y^M-glPjaDRUaD|H-AME zQm4i9Kb<-drH~W{Kw4zRXY!FkLgn|qR{R2!+C zNV8I#TZ7NfSo`T@BP*uc4?q5iuYT_HpMUP@%cuHmm>n;x_36#qyR${}_6Ikwe{|!W zpTD-ab)!Ey9Qrvp3|(6lMc*z}AV~0=SIi>S>?5=$CXD#7C$dl5i-@LTy(8~!Z9Cck ziP4A|6x44%h-aB$ry0MQ&+Bj>!1JeGoN|x<~#3w`+xX<-o17$ zE3@UYE2<%9&^UR zee2Zar=EW3@h9q{c<+tZufO)IlfAn|-nR>caug-t&aP>)Y-k!}H4S~&%$M~9wh^*4 zRu40oPOIs9y}o_!!H2Ir^7zFEFE{gf+bnP0yuN#XcXk3_A~27am~Rb3`QQ^zJn`J8 zUVHf`*IxN49zZ_zOo0Z3S5$Qdxf9JQw3Qor3q({}q%PS(#3rh`B@Ih;*yxFpP$&&< zo$?;-tE%L%ld+jkqM++Ei+GP1GI1-Fk&U|0aiN>a8oeZ07bPDnk&DL&dHZ=svlt+G zActuZn|Kb=We8pJIFgG^zKKDpQg9Vzy6c-oRd*-HUE9ROH-_L^%Z?LbJ;)l=ySG9G zh`A*Xxq%^h9#3JXL0ujo2tTcDLoF$D8z_JAlq3>KNW8C7YKc)1rs5E+X{MxYO5fL8 zVnXHvH3-6TkXY>-sF*$bEI14veK8AjtRu>Ag$t)<6K{&2rvk=(*^qT|GtH~2-Z`CT zMYF%#!D!6whf891eCjLFZ|bsW*NE^OQO8)X>gTKdxQ+9`+cmM_l6)jhm^UnP~ClF5IA;i7wF)`TUhP<$Y$I+Fp6>7{sh>Tn0pRU09hFc)<$ zvD)=4s}s%0xo+N<%j8d?XDFsZCALy8H+?VNuu2BgZdo35w)GKFpdP(agX)I+tG zC@?nm8zBZae$rs;I%+_qZ}0o-&yNR9?K%*~Xvu?P;+dGs8n7JBjldPBy^JB3eMadI>?^ZFA7nF=*gCvRVq5%G221a>+ZKt^X{Xv?;EK|m6*)Bgm15{E#6(GAtsLjD3^ zcHpHxqGz~bmzZv(HA8$E_l&<15TL3MEm5)(IE3YWtZRIc2GCWUGNWyE8a?^1802Jg zr4W6q667?HK(WaY5_c(=c2A`22l{;rWfo!#A^^|H4Q;+Yf7|A;CG9yt_v^Uto>sdUCf*QAILx z3!UglQIXBAjqaoe;&Z&xpT$ZdbPH5`s|sk$WK3X`QaBoy>)u0Y5Mnm z{od<8`ukh2zfm>EL)*4Z%VM|8Fo`Y8jjinqm)6dlJ$?Do)|s8@`lOsro7v)EcW-vE zdvN{c-bXj`eoRTU4h8Q~GZOs?4#{yrJsDW?6E5JS20)gb)6(m*jLk##vW$Iy>e&B2a z&i$z)724Bxz>@_s@8rlRU`?*F$ykx4 z7P~L+!jTl6@{F||hIlw=j^twHl@12s64>I|#L=0Bk{q767_;VCwrqRkRjh3cdEHO8 zw=SRGytKW2ZnK`0J@Rh*cG0&da|GD{g+O}0E*d2 z#V6M;Zsd0k^B=x?|EE8E=kSBu&HiqCygxMap_}(z*Dn`j4E6Y5MIDLZ(xZu#z>Fv; z<`4SMv|lAiU6sBf@5B3eb>b>v(rA3;)L^$@!Oc}blm|WvK+>ZsW`j`Q6D~qj2y`gS*zv+m0Jb$M5YWw{N@=>RUf;R$=+?uJeDNEf`NmhCxp(K_oe%E4`SwTm zZ{6!=v)!9Fm;3w6qrH4sERRkK*bo%WVxA#Q8Hc06Fl8A4TNH(b7c+R`d@h1g5-jAD z)eQ_N5rN69!$C$WPB8h>C{xNaIG6GE@d?uauqc6M;^N>rq3(>;U^7g1&V2bF|G{s5 z^UL$2<3IiXe*4{D{4{G8Lz&O#3oZ^2ePB-2bZ|w6hjF=i_WY?U51)VV%A-#`xqab* zll_BN{{C;Tz4G(L{kzL0vZ8^G^uxy4bB}!T(@%ctvzuER%jI%tmvn{97mImK?nGTz z$4AFU`v>#+@$B&UVDJ8PQY{xvHJNPg?Bqpx_RQHc=g&jRmlfBpz5n5R?;qX0o#$<{ zT=dIjRhBJTkc672S>LX$Pab&knX8XK^Uf>3y#D6TT6i64WQvY1ughWCx@Kaimb}~b zkXX+}BVN^GB4Ig$Z}cQmT}{wHg_?KWxDVkw7>0$sHL~Q71Q3-UN@`CN&;YDm*ZQ~c zL@RHIcSB>SC_80I#-dVa?)cETp-eBn;^sJdC&cVq|4I_hD7{ai&Sv(Jxt1ETVjT>K z?&PFLKDP^Ip@0VStUW9gTj@g_NdDmWEQ?toJ|FaMtH-_=NXNhJS68nIy6sDD)di}K2SoclX!aH$hv zr6Ese_@XfA!2Klp-%%YmdSx01h32_#>`A z_vvA?%Zx7D=Gc3W_*4(h!U$$XI~Tms6+Z}-W@GeaV8|cyJ4gf+M+^q*BkU0pLnP=b0hUPGxC+q) zW@o+4$6jCYOQXL-?^vE#XKx&wYUoxCDfB;3Bx@i&!|S)7H{3P zoUvf~sWpa;RkO0`w5X@u;zVYZ-e=XH*pxE>I1lX8S}_J5)A^!n(=K27>D;mSBrALek4HPtn0<6v=_)erBD%DQp1IsuWe^ zRTa!HHU~6|(>xLs)1c|)St*o46M>b@!=~8*kZE_1^IH1?Ign|+u`82|q0{52=~=R- zl(n*53N<&9X^OsnD?V@-bh|b5atLQhAv_WTCvm>HxT#~s%*yL9RQ_~0kx)g9QH+(! zJZpwpR+D|ZoHelLY?k%L=EL9oy)XXr-{0QaeCOw{{OrH{;OM=#^8uNBV9CQdaOfJc zOzUcBeQojir!@^PtD?fO*Wwjj{{$$PQnb6wpt3fwB!f3opeyrX!($8PziAf zp1~GYYFR!s4Z{gjepDEaN_$@O`q*tlEwO=27Ab7ZNj)hyHZDE$Ir6!D%5g;))vRQrG=zNIi{=~pFF(p+9X1z~I(p)kRm3>%-MPxOlcx?v0C(X_$Q z@P{(2?Z+xeJ+b{@WEt6r?!9G!hW?&_bB9n*IrKUf-f)BGT!8M1dIGmz{#g&AEaNl6 zT*D2Lu9J;aNJC)Ky60TLp9m`e?~u1H7ojk4wR1wGEbG;ICK1z^vLVMp?$72z3zCol zl%anCHD)*xGbD^5SIeOd;jSTBR_(Su9y%9E}CA1#gX)00$r^94pa{AQSryqRr zQy0GYiLHxk`HiFD2S302%b&b=bnVvi-mT@)URm}-10K}?LIm*pVafTkEjuWV3n36= ziW7S&IjKls9R<04fVDtvw3KqCEsa*)4v3Gl&(S15ih?9zhkOS42%)HBzD&5irmZP< z5xft#DZX)HEb3Gg;l&1iCJ9o4EQEJp(1$54nwO4bMzL^6izW!nkZBSeI%@Bk<%Eyx zt45z-IgG>y6xVTE! z=d-ftyXCU$+7jD7q!uKbbZxW9X(bGQT%D8ZVaa4nm5k#)H0uM3O)gj@$$Rdm+MtER zfZPdf0y5}!RITUD!XKh4((NPGK-^6zk-Y)Q8!GD-Q4+&iRrgu>*rz}9dw=)`moJ`w z^VMH}_uKzz@8-4n;XX2+Dt>JGRh4Bi-8uchW6%8N@BhxJbEm4ZI^NxT`A09k|Erho zzW=_UA*6(Aw%c}fg%cAX{FO&GPMw{uuMb(Zy|cyP0K5&?H`co$t1J8vuXc1asV6j$ z%r-aHj}DIZ@7=q1`}WOi@AoYrx&6C)-LlCmC{2pG#GwmrB95n_&%36b)Ua4RbM>ju ze&sjc`Q^{v{pC;kX1;8*Ja4PX1S@3OP{89|+0hK1tJ@yP8;2bMj1+m=R# z56;TuD3yFkzo8>8indT4N+={UHA_6n200526@#nqB=Jj89ga}5Ii>M9Sy#uC8mcOn zut}X@*ue>~qN*m3&h$G8!X*7x1+6L8eD}3=ID^jTlIVJ3B&lVbV(iPDp9e{`!4~qXtY63$K(f6rB4zmCWQW7U5^#_{gN9vPdR5d*+^;vRz#NnGO131;x z3fc(%aw=ETwTlsc3?TJ?l)UN?TQ3I9lHK=NPUHG4bA}KIN0U=$^1Nsc_9$ici?7^q zB`t=lrSC(OYGc2d-dA#K;+G>7=Fcym#}q0Ml8``+u4xZ?7&Qm)9k-B_4&$b%FhnVg^C0uxc}&SfD3 z2%0wgFl2CG*I<&vjIq@4^GZx6#bnyekFypx7|+GUy-wG9+j7;-btZo$ptm?6g;apYOC3(-R5Cl z<%q=|LV9_4vUG-%g1i}4HHA7$(3cvNqUbs=3k-p2#_oa<%wUP?!7#V)or*LfRRbiE zIB|^uC|e;Os}ZG3>}j!PDSwwhK}D#HsAb?qXv6WGQub+g4;LOkazO*Jm6|ci;Hoe) ziZPScxX4@$tq!@ke%M)e>SG|8(_?x~lR1j-S_L(8JWDPEH(Ld1cs>!-6+fgDMRRaw zft9pY|9z{|DnvjW9)mKD>9=9yY!=zFrf zLpUEzmh|glr^C5}BNKi|<+y15$gxjLLZ`KuJ?Oxwly*z5=K@#+y?jibg4uhP6;eiN zec;8Ia|$sqfP5g5RaNGBv0QZ3WRg#(<<8mP_^-b9wcmOEa5n$5fA`%t|MG8!;{!B@ zte84x@tW!nCv!Bbl;%6+mS$~MY${DfGY{{>HVDWHD2I7q5GfW|7H&QYvQUyM#(mbN z2DnKb*@}giC-^sFb2Alop&G{F#e{F>?Bh`Q5K+cP0Q)DAF39;#v~h>p@+>O z`oN)YFb?gj0vc)g^ciwflr23IP3R{03hua0bR8V*(==-!&pGH~Vz_c%rnEv)hmhn) zE`kno@ND98IZGH3N)|F>3zVP`6FP*7|wwW#ZlR0oYlADH&^>SKdYwOrFA)zVDcG)#U zemHA)_h$F@mp4DSw}12S_}1?700XP8X`00njVNZ&EpDEqAKK8Om+1SxTAu>c%<{?l zM!B)xuCH%jzWAjtUHQ^8>s#yPJ9qobgYbkmM#dY~4lR%%(cFj`DjtR1 zI%#Hb4Y3m2o~*9@M68t!J$?X~RqPhLjxu;h+%1lgcrXPSa1X#k0b-1|aRo9GR*;gy zxmKL7b4D@@)ug0AlgF9-o;1%?fz3m~*ND>cvaFpaot1slPU}gzefrdMFFf`6Cw}YG z53Nn>Klx8D|Kj^EEp~T@#Ys(58aRzKZP#{H4MSxh1TAuoZApZGiO^i$vT#dg|CD+i z9rBjUy0Q$05vXS{_U?c{@q4+J=SI%x6RdA+0^;DCP{9*if-Hx{iwDHaPG;cBTL-cP zgoQBzXy@Y9-~K1R`@##KXqL@eZ-4mfS6{z-?Zf%v7)Dfeed)@Tho5}(!K)89Z9i}O zYae{HINE>vXD{D*|D8#dH%;H54$10C)y(D$V#wMSydiMvNT%~<0HYN=Cmr2Kki=Bi z)cRFrQBF74i>hd5O+U0JhkMI|{UXbnSn)atw*%B*esy6C6t z)ALszd+3Sh5ANT2o&^U=u zV7KKK?K)lHesWKf?ui?cihlX_B!-b6H_cjMcV(VIh)$)#5WH(+PTxy9<3v%8U!hf% z%@!>6#o-9PsMSv91lf+;+)q(jrQA^5a`KCbp4{FLkr5NF6?`zu^^L5k+WAS}Hh~!0 zL$5 z)YWAB4ERC&yV};|w&q{dpgAEj$q&N)s_h@_STT-HV;b$Dd*CAWzw%HgrpU$-R;Z{e z`~c0TlWDQBs+A5avXDo_M}BssYEg%uqR(8eM{~OUWU_w>Q#dJ;Y=anRA3vsaFO;Ej z0g+cD+P_v99tXVur@K{xos2VyzA`|L;iMyX?SB64lINhlt#5C1j%ChQYI>b;;W zaK2Zl%i&|Wdfl9YhOq`O2;I;)@{$#e?O^EO#N(Y_iAe3nUR-O-b6ve$qVemnr(^N7 zN`P}eSJZW0PP^p^81^oJq8b?qF+4v3{*gFn_xmt!3tMn!J)-;=QS0$3P4pBQKn2p2 z@>4Z2CSH&xl$2@;>`A|G?g`3Z*-a7z;NU&XD$^6l2s?8zsEr5!%t)lk#KIhPhIwQp z?pC;c8e%eA2UKaAO<6=rUuW7lSbM@>o78;P+So4z6{pMMJag>hfR-vb&yyqHO(qrS zn;F!VMV?J2lcwuhLQ!L)D@9V9 zrTPi{Ca4s4)FZ*y5N7aI*sN)%Fgzq&Ci0kk!i}6AOOSN4-~5~A_&Cq&CL5ZznbZL3 zx~3tU9rlh0$7A7+Yod86(LYw7oZ}&HOm>j`D#~k0abR3M)Dl>~iN!{n0QL^-zIm4v zbmKSxn!TIrjuM*oqNU{fLg-lOaD}tlRWU-~41R>bjm}8m5jzUaW1OdEpzM z|IL5=xhCs=_~$SG;y?W$KiXR?mt|G9E%Y74FFM(Sj~O&!IKzj^0SqEpNQa!{N{OIk zr;_wQ@hKB|L4C5$UHh22<=14uLX4nxOBj`2iJOjw%HrjU@0JvGibiv4a)=wPmhwg& zf(wp_c=6<>86GuZxU zo7-o$H+QN_=XbK9**%!wx_NZ>!#mZ<0y%gcWGXpuBw^<+m<^apmaDHp1Sj1B`e1U7 zh%Um8u&|S?=n-KT3Iie$gA?vP5oiTz0sxeN-5o(Ke~s9&NmL03Pr?)7X%@y1Ff~@^ z=3U#s5PTxhZxuyRPsCv^CUreso2*UB_3Fx_Tc7&mg)0{jcya5fd;7hEYj5ly?=AB# zYZeGEq$xyEuh)|J6tnYvN-r`4p_13*t-pcmxFBfwNiWbYE zqn#mo9%Ks$%D0$8Cd=x>Bcak0rx^Cq&>^KkM~k4GlhI}?u?t!8IgG=@7FCHpCGA8Q zjx1qHp59jpf&p!N{|N?K;>B`vX1thI6gkYK9>*u66--{g4iym@`=U?C!ijYu>h$V4Qa1K?i(GPYivj)Vjt^r;MaE0 zkd`a(8VJQ18kHBlNMve4WLIMYLctQ|g!{qc5$_JC06($BvjBRIihH2$RgHzw!u4rw zbMv9cpZwx){?;=ud;(Xn2UV}E%lUj+L!#2&yS4Yzmwx){PhL8?bGs_rtRET{6%4uP z`vyIs%!Cn5-7Fc221AF?*71s$6?`9BoE5;X&CdeMsDm(&Bq@7f(`cm6iV2)zs~QSl znw1v~0%$~()MHtG!g@Ypp*=I^ zd)pI5o-AgY253v?x$rDBKBo^oK0!H%Y)ZY8E-z3j8jZN5@FYK`?O2eu4@X&Ne=qfc zMCmp*i=tYd9LWnjfW?@8q`ic-gNJ!m(xGS6tO3&v9I~{AGG#laaljWes>M^Sor-;d z_G97ZO3w23Ynwa^t1YI`V-VzOXXGUZa?Nbg<`wUl`o!2P@!+v8N7duLRRRrJ^@aQ) zQQE_=LG)esry`N6R1G3_!H?O20Wm!V0AhKtry|&r9J1W_I$@ruqQS54&N*nAoH*IG zW9)y$I9d7qAlF1c9=?b1`GbFIGu1@kv4OMB3^^vnM^YcH>}(guT+h7|tXW5srXGeH z;TaDAB4p30Jx;y=G6a-PjlhA845{pl!D2T0H6&jK8WUu-j4{&d*k^%*p)r4!lxE(P z(T_mB3}G`_3#9VzlWT75kyO`|R}(rJqGl$8$j`;$#$x-#`wHgovjLw!bUX2L#7(E80vZ4zb^)PO*=pPZClMq4rjgiZ=a{Vn8i0eOI zXOTfri_|g?(|yqcz^_oJ5udgx$u0;Cjo05qS6mp#$ZdAUPZ)eGNX$j}!%T!-j~+Y| zIl&$T3;`Pmj$}dFCsnZTk#XM9W0Dwz%5jD9=0!HCi*nj8k2MR^)IAb=F$=Y#8qbL+ zB;pTap{QY$!;mL7loB&}PjpJIHp^0C*6%DRBAPl6QqEHpT;c|&y;z%+Jw0s?9+i+i z4XxZv%rTxs@}u?xYfmXQ{|VF3C6p4@1lLHYXE3-sE!J4tc1W!$3gmNhy#(?r)R25A z+Cdlf1WxMB0(S~I-dqr61<5N|{YWUt(Cfm6E(2tas;#W5s;;wYQg3WcHn*~3Qck9) z&z+qe&vtLV-ya{G9G#FyiZTXIqN&+D)Y%~`{aqINN?uO}b#}av99FoFEX@V!GF(Hh z3Le5+NTeDCtk#f#ht01^#bV;yoRZ%ou*0#&F z^@*leI*ZD(CKn+qr!}V8L{KR1HGU%)4}F6Mcbs10_y@P#GYK)_wOz5yr9y`mdxCz5 z5%AwiJQXN{ZMjAW4@_boh$t56K)wQ?_uv!xSW-Jm4NG8OE_eVw3{^F0;Wax8o z@!$(j{nP*B*Ne66`+xTH*Z%BB?fqRkpAXHlb;7&nnD!tbci!`AKSOMSO-B)}$ZW#mV`zXATaI_ZH1$V{_IHZ@+ox+B^6AgGIlDVF9N8O(R=A zLG@TSvZm5mq&P!WU8EM+BT30*B0`!J<{W6=H9Sz_1uJ5nc6L$OXp9xsx!Mfyzm>ab zW!adoL$ko(SLrg^Ejxx^80b_L9#~wlvRd2RT;E=ste5NC^<=HyTq`%%v+eD*t@Y~6 zR&{DUE34t|Vf*U4M;~2V99%m*ymORyO}A|Dm{T{w8kaDv5#+w8s-eS$>XuE`cV#W; z6%S$8&|UzR1DxAay3cSB-A|GZ3RwDOaNw(WAP$rDY1d|WZZD>fU@x;B{+TDH$fr7n&Bw%Dv_L1p=;rSbkx?nw;8(=lo9Y90{I6cYK>K!zW0 zlYP~jjpv%PH#A2UnjDeLB<5-U%;y2e1TrisgCUjBDHGr#RR-Iz`;kH<-Mr2V{2DAk zs=P1r&C};z_{8Ub^T{uL^2)UvNB{0$|JCl>A2#!O-!-r!1!Uh)UI1$e!jvh7PxD0V zfq)xm*(e^Yf;>c5Ck|q)L>E^S5%rBc<>8U0(#4mKZv*HA$ct%xp#fApB#U1dS1T0- z1Do(<4$4Igx?)S^n?gZXwB69Q-E=a^+N`Xn7p`1Acj?l(OAnkrz18>K-u>PC_wL@g z@!|fBkJ{ryvN^;nH(Lb}Es9j>;d6=ak9Zm!qH>Ipyk2%o_WTIStpZ~O-*H!tw+s2@wtWPkT1T zvu7j(vlQ2bUSSa6av0FGF_XpeDwE}~fnA7E%R(#o7>E|cDW$7?4d#=Q#eR7_i0z~A z*)DdwN?3sUDcW^x=Ko59$ zxryRPPGkzpCe=Iy(2&F_|G+20?-)Lbsec6Okq88R^zU-FjbaABALH5Np5gv<_4Rq> zvGH)=ZSg3t2ZUugM$VJGFErps-w-|kx@C&tG|poLKT^g*^I}LmeR^ZqD_oKl=7;V5 z1@eXPUfewIS1X_1<6Zuje_z3&aYi~ub`(e$X%1S5c`iQGghA-@Cq7BMujPj$)aB2w z_bq6>88ZHOu)`Fio=mq+qxLx1voUS>NR0X!I36W*$F!G!czx2>T1lQw;GD7T36W8ryuOsG2;uL$aF`id(bOv;VRtR8%2s3>j$$KR?5OE#6 z^orY3g--wgf^o|P_2E4UEWOQI=m)f?xCb2iY%(n;>)jkkYBJpL+}ZR8d1V^~2pLtF zT>AH;N=YI&@jt{13cNBYVB()3fvSH^a+RPiC8<%m+9q5C&>UVkDJv_e!Nx;kP#cJf zHqMyot>CLJ-;xEDCb==gvcV&Z`=E7M4=e0e4Hx!Hxq|R!f}=>&4ORA{p=y}yPXfOv zRH<{25+@s5S-rM??$VW~pF4H_^7+e`*SEJdc%5!eA+ns--}#eozxVPFt7bMkJ|_DQ zBUfJmCNJl|o^9g02Mh}Fd>^eXQmql&#=*-*#GzcRFctGUk+Cz_h z>%aX!oY~&~^MCm-@4fX#me+@eC)EUAbcDsAq<|Ti%B2c?Y;`SiqQT&)&#Ial2UTgK zt(w(&Cb@`x84PAhYlB)WHYUCb^&+ZvotVoWg6V49Q-rE;sS47L9nv== zkzlM6VRG2m(3VBTgQ_daNtI9XdV1xBCx82oztmOvU;U?_eDK|u`@=orj&$AU`vCG_ z#bNsf9-u55f|e&2$&cGpi`(iGVdchJtRWH^2H|248S(Mjh`ETN$at1{JO(zZzs1+) z9guy0_{!+u4jfZ8of)v6KWQKpyVtn?2Pa-19+<6ziV|xFC2T&lKx1n^(6auaD@3~J zMNwfIfmbYZP6n}%iaOufxbXPq3!lDxs;;hoxPSjnpEddR=El+S>}a+;eR}fXBirkn zwWH zoCajH$vfg1APP7Y10DpSx}~?c?DZmUl1(zJX&wCz!4`j}Ab`u5h@z~Dx|pn&XU?x( zzOa7z%yerl+o!Y?SsYcEbqF-e3@n0Vm{Ba z9@GpOs;G#ER30uZVhMshP8JUtKS&c4mg!c`3bQWqAk0hVsY@q z=YuS!4TqEsg6szXv|bicr^e8n zQmRHIezfBtH34Wy0I_WaF9AzfmOe>S8j-(d zk|cv8A5_7qjA&}9`x#7*C^t+d!q+Sej3EKTquN0^gb7zwRsCXFS0y%n%-7p)2`)q1 zwsk!Lh>W@c!#DdP@J2}k>4AxTfW+(M|)z_Xs|6FvqGCyohE=eRm)@X6}oy6N6ibs ztfg4n$jY)iJ`$+r5{a8qblZw)Wn~7U1`$cQJ>x%QM?w@VLN0i)t~kbrKiW#g9+$_} z0AH7A<2dcNG>J;jG~Q06FmM$l4NH!?0wPn)2A@;SZjzsccSOI0N4EYSTSp}SM7M-S z9ORQ2{g>vJma0UhOJOO|OeJs>e8{+R3+K>{opnMJw;&tV+%mr}MO&Ai1xno2LD zOhvOaCdG{Kf;&uo9&RoM^TIbM`BscR6!AGnq(c%axtJ!_P#W3C1rLo=;4k(C)59hH z33~=F(C~>6j_Z?2g-ZG#JK~Dg?E2r@D%IE}YBBmyq6>lz1P}|-yErasyS#4!W~X4= zWTv_{DeAR;cC5pY6#>U`#&a$D@Bxl)+QgHHSq}dV5s76WkEBe~o8_TEI8)e;RH=O*jxWmzBX-rv2qf3SCV_r|T+?6}PONj>@W*StpP3Q}B9e8qB=)}LJ@eewZY;8;>xjQ9{DdXOX9!Qf4I zgi{>SbUinNEjh|eTZ-~rvzkgN7@YG67I(YIBic(><0a0`*hb;6dlMmhlbn+P-GN7v zK#h~q`y2-Ew7(+ANCVDZY+h(|`!*knYJ2D6)1UapzxczoEc^EV^}oOW{s+bS_Ofq_ zeyFB3xVKG6J<6TQ`1@?TY%CXQZw9S3nI@4hS z@=jhA^`gz5{_69;_eU?>ym$QP|K_jn{pzi}o99ys-r&$yX22{s(Iesm(9D~$?NPW> z8DCQ_wo6ksF{upmVamG;+y(d>KA#IVdF}+Z62%M4TRXyP`?R$ipCpfU(Oa_v;~XcM zMrikoUQF(ox*9Qrj!|u>DV=B*G@y!=lW;Fr4k8qCoZ!imEgdS%k^q)v$*=y=BablVN-r| zeSYumaN9PDGf2oygCcv+(p8d+Z}9ymLB^jz`KR)4C>Cq=dFv->CA zag(1k!+aSBQdjI9XE(0T_V1r8XK<+_;)k;k)O57L=$1gY%Ci@xyJ|GsV{s6cGV*)4TMEa{?ZS%}y=l=&O8T0LGiK94&=KLbwW^TII!8nXa5k}sw77<$?Zl6;>1KmD zW_jw=<%r1Lz24Wc{LrdIegazRHWHrCqU5Rjho9z=*`zV^57H zp%?9uaH#1ZU4VtHHcqZd_#ZJlIel!vKM1#??KBN42&5wm+*(2)4v9LdL0foauy%5B zX7BO5mMLh{_U*Es09o2Tck%Pz{GDznUj516-+K4e<cby3TQ7BNr>q z<#;?u$Y$S^7=Vg`VYdg)vSm}H{}cv^>Y9jwN=cjDOGFy_e1WKAJC$n65d;{jjh(D0 zn%SY2O^hmyouy%cKN^i-+2@Kg#d6oHR3qoGnhrNR0h^J*Yy3sZS!V@~q6*2o#H9)~ zLfEB5)M^y_!Q+sB#!4hl`pEq1Sl`6MO;Ah&Zyo7&uHb_CSma6cabpwg208VK>bsOH zIK&(G$aJf>PnSipJlt2X2+!LfQThZ{=kXE@9NqEU)+E@lt;{uugS5A*OzDz}90m}~66-qBevFb(@;+pfNl{Jv z<%xD4Z+Av;n7WI=KLVOCwTPA``Ev*L*Y3Gz*~-*nAEBI z1cO(X-R=NGUV=n`ZcwNl8@3YjF||a_0E?+9tuctL$;MZNJ;?ZZPvDzK^F?Acgn?-| zhZ-7oa0T!N421FNtE$e+s;=sKZH=WB{(sxGZPP86%h}0MGoLRPi)KD2J9p7{O9d&T z(qh$9786(!ESFehc{!P`<<)wl1iP6~*IU{^sxf(eLlyKltU(fA;!cfA{Fl4U{Pb z{N9S9f_pr}4tPx}wu|(D(bwl`0^K<+AVpI3;Hv;>Q!_4;CnEe@RGRQU;a}v9n9vXR z?J_UQX0gPdSJM~2_St{*+h4eI=gznPUw=Nkb+4MP&uPs?+cXV+F)TwMT;G{)#w-Iq zlC(o0aUEC~*=OAGD95ywlsSgfF=6Wm&6U6}6!mJ}ETgU=`HBzCa!9eFcgSL2W1z;DFiyVrVC8U;pi=UU>G@ z&tAFv;~%~|zqem76b%zMRcz2{<7L=Oa8cO7Rc)vl-eQpk(~Zc42tX!LT2Vt?j|~*~ z%ksD9npB9L!!E6gknY7uep0-9>O+=-3Ma*zm|LrA(S2SVJm&IZsh})p2WzUKh5D@1 zTw=xFryaEyrMVsi#Bj>VKOJ8OcOH{H;8fKV4+HiJ^sbDE#_WG{tA6mo>80)R#$Ny4 z^|tIf*qQR-Xvk~YiDt^R=v)2+4gaGu>e?vIz<60)oq*9I3X*(fCnieAU~ zk7^F%SHyfvkYqTRC&U)7zzFsm<8-QtY2BTS{G;#wiSCpJO*0`sKVqC)A_Yru_;@L9+TI zGYpS8C0%93Ov4CJBpJJ{i;A#_G;y3TQI(yQMKiSWwF6*auOqZ`{1P_&aU9PWpGoW4 zKC6nN%gf7`H@@-Q`omlOM@Rj)e{yi=`XN5TeBKfP8J1woL-WN$GI-oTUQ z%Zn$)S-KbjT%X7+82g2Qk*OHqna4Jm&x!en#vr_zd9b48%}819L@~CY0@9`qm@RRQ zqyN!dj1vdoTxzJSG_dcr99iT#;TeN%`S95$ldN1@Kef5BwN_8-plWcum*q{<4sG8O zOA>v6L_nO27?jZShaOTy^>7_ns5RN<_TK-w`35|I&R{6-Ai2;|{dm@^fjn3UpEd>NWpq8MRV zK-An61G6XOb}b^mYuIQTZMtvank1ZM$4^42r^P`EFb>Bq-C#Nhgb-EMp%fXiu4&mf zHb(O8si}rWZMD5)*w#jCBD-DV|LVUWMM;`-mt#S*i3yuEHCz=iyx@x^LTOkYLApnL zQw?_FD%Zk zpfT~4k3lwM?Q$t$vEpXXe5=Gx4@GcX7)<1uguF!Brr`>t69}oV;;O+Mx~%Kzv?!|S z`g&c}vy-F6$#K^#v4OTrDJ*E(otWlMq|}ZVIlj`XwBQ%^w{ z=!+o37pQnFs^Jl}!Jb}0Z!{@G+z0hjvL}$+V6?8nJZT=E?DS2GO)c2Rrhp{0I;qmc zMXBRFF~-^sTL(cK;lW83KN+H9|0{`r&P35SY{lXd!1Gc007ld#Fm16Cf`G;+B*$*l z4V;YTb-8x>+%QmrAr_7>BfYOaq4pXn<|0(l{jz-hKGr9?pH03G!OC9wxy{T1&Cy&S z>f({dVY}2AoUiy!zp7VJyKA3)N4TT(uxfVv{p^4BeUqW) zKk!os+eLqVJ4eWgX!K3cKV2NMbp-&T>lTRN6hesvX>9D6+OgsHT_H*$9gfap+F=+p zlddKyC;WZoyAdYS(a6%rf!omN`>^7;^$&eILKG|OBPFqeJ&lTh*ZKeN_gTKs&N2Wa znZe2+Q@SQSMTCRB9m8xa3Uq;mBC%H$W8@irM)P@GPSnAumLR{Q@Rf&!tw8DSSr^l_ zetrUHCUTLuXF2vyHZAhF!C6a~T)Q<~32`zMAQo~$&hA|uep%EtldJL?;cAsO8g=xF zbV}U+mguvg9kg;VpzUJjah-N z5Da?ILeQ$7ITW^VW4%(A=nQp8lhB9%#n>P(%DNUuW4bo2=tNl66HcdT@=(`(-!10z zX4x*5i-Y~6ql3f6Y_>R=Efy!s#S&#G;oGdNs%gEoy>scx#qG1F&z?K8y}dmQ`C>kA zyYBGtXm9uM&h7hqckXrb*?cyursdFp!dp+LIKfmCuopz@oMmS(U3~GgpZvtL55M~J zH~#8Be|NUOkCi%I*Tk}7_?XQ~@ujI#MiI}6Af~=bF~HhuyRJgUxJGHB^^`-qG$q$O z7ka1bbJzjIQ8&SvW3_C4_rX|3{zAs*)uD za`$T5c2s3m*Rbg)2v1!@wz( zfYrimC`{$}L(HvN^I%d(89tF`GV3%xA*Vc`(ny!ci=t7#(xL&F)YaC``j;QCs-k)0 zdjI~-Wk(@>QKDZlx-Rr1$)Gry!EFFrg9jG%D~#IZ=m7i}UORXtXgk(3ZOOI234cH| ziQf*phnI7Z~nb5M@XoY;}VP>(8 zdKR;9jtTP=n~K~AzNO%k?R~U|pAS!?7jTq)qHM z#mTZ93NTp^$DrLAXcP?{h=9xLL6V*6&~HrgDS9$oRLFl+8acU_9j(WBF(l!4R$47P zZfB-zegbBViqRFZoE%?V$l4oBD!`zHh;`32@o?-?&NYo(n6HVwgC@a6o9I>-V#Rc|JQ_Hp_*!v4UZ!4aKU=f+4=er`5^vXqYv{ zg-}GbBDPamBgL3$q>;tEebmEPd5ycR+v4!!F6)3|RWcV$Hn&0&aBR`>z$&?znvHTs z+61`*(uhx=QiwBN7G1HuNbO248`P`?@;l9nVtc)O?7_9uoB7bnB!vr)TNCes9$^A% z=uB}{Set;`qm7VS8n82~=>(>UeZMo!&P;~2vU=s_{GD6vv?}L|W`Wlz`ljRZ#PDB_ z2)=rYLx2dAEjRks4H#Mo5BbUJ=k}3EALQWK=Yq0DwUk`;2nOCTxf3PiAYeO~x zNlLV-baezk9N?j;Q#7WumqxgNqOxK+NrwzkxM`b8YI!7tU}eewk8i{fPzK@{Q;INb z6I!G}>1llcK8XGJ*+4UsQE(UcG(xZ;2{MV*!7R~;t6E1HAee(8R$<|Z1|AJRUYGkC zU2KW;btT4B;zt(1J9uTWpZ3FIb~0VV4mXs=oCn%n4l2&LI#2lrntS8eU&zi+-F`qk^%0VrC*Mfkg zaR9^b@N?#i(ISLpFojp1OY7KH-iHp0K>P_kBv{(1e;gNz?=)heE}R0|h%vrhAxxQ# zlU{1T6_$pSaisED_iZ4CY-IFhkpLBgUX8<|u@7HA@gZPTxzaxhU}Qg-pbPh*8J|w{ zWw;2FowKkwIozXs#F(XH8CLpY_y#5*L#6@ZyWw*Negqbpd;obI3sb;x&biFkr&~Rj zd=ecfp#h7P0EQjhU+bc~PgHdBO2C4QCbezrIz*ovU@}Gr$w-a0_s$cchzTl1Fk90- z_XZka6Gq~!_t5+%vO7}Daj+k}41$_v5=wA$yhR1wLkynLC&IKSGgJemU(rnjjl=n< z@dqpKt7&KK{bBy+pU0;WcxL^KkREH$prIz3P){~b^T{avWD_aaH5uT^tcjM7(~-#{lDyoOl<2`B>c~XFe*zvS+ZD`5 zDFsk&V$h2-wZx%S4_UFkxpnI7+3i!OwoactfA0Lo#`@;zZ9pm0DehcdV$&D32M`ht zi;^(W(cZz0n|JTry?^KSox{Doql4qcVzITov$nP|OsaaaQ9+J@=}_19RgEG*;_2^w=O=&r{U2{`tW#H4lyo$Je6%Mh&gvE4w=7kX zVga@?>SdA{$1ek?{(TFn0!~OwBp^&ES>uMd-Y;l(PZckg&KtuCR*uu)Y)`4(G-x|x z&N_Ytx1JrRU_E^IFuYT!0P;RGMMJ1z2jlvN;|ory0iv8fyYu*?7hZVw!R__wPv5=u z?u~gqSx0EdVgXaeQ33?xf6zfx5(N@sPt2DCmV^h1$QJaAx5 zPjWDb>)gdHG2pb`P6wV%%9@hxsMfA>7IemOs|Q-ACAUON;RKm-$S3vM&U*3isV<-7 z$Jm|lbm(^Cnz#9^&u5_Z=S%irS~Yc=3dx;8qX{x-WDr%C*`&zp3c7 zuN_`{xr7q^6GR=pgQQr|w4VDm8GeFd(j44F7|~HQT2taH4XMp5aVaXpIwA3@yF}n# zDI6F9)cEl(dYE)Bn`}9hi>{x;B%iLLa{H%2Y||qz11X!TG1T_b8lG`o9ZA=qEOYBO zD#;IvhXniR&;X=BTfZ;cY<5K3LG-oQn?=WTUQhG$-If zFfxJd^dQj88q$vvDyO2D6vgT7wdXFDk8Pu{f9s(9=w5$xZ~|rqz)yKV;!+S`BB>4p z2PVAJ?m=Lo7``-wW<5-?I)EHSOHp4z&2&G4D&@GH{Z_Ym)qh838`yUDD>0>ivcqS(NBuv@L+y#znv|I28@ZW zSu}V}+_oOB+GzP$_ zxG^jy;7`uKI5Kj6C1fCG+R&lQ5z3w%jy> zED&L4%6z)HS;3FHyL#o^`7=AGPM_M{pZ)3= zuY7dvgR)z~604}XuCLdo(MOPiNCV)qtVlJYQ~}tEl@rvk;4y?LY>_ofP$9Z@xmYew zpF6j{wtnX9xwYwJZ3?s)BMmyZV*4WDReBQ*;>!{lER(v%iQi)s*7YR4_E?7phsVps z?BL*NIXeMx0H9)#VJ=loCN;{xNj2TrnojDSo$ali?HZB8<#Mq+*xx@oJUG}t?ApcA z$?^Q;1ni)$0RgJ-+qvqK9_duvvIM~!H76a6Z7FUCm<{kM1r$4-Z01EaKRRq6K1GfR z7iZHGU$r9*&{ld3;j|~9gR4dcIN&YqO(qcV;0Hs^zGq_^unQT7&Z=Ir;EVSFPv|1`%}Xil7*^IjKoGatVzZYF^i!V9NiAJ zcce~MrAKEA)4VDtJ7@DeZw~fENU?>Dh$rcQgGhLM&U$y6ze)^Q{wzr#D08hZ!1hPhyfMv}G5=m!zT zDdEqu;s+5Xf}@d)EBiEE{|9Ce{Vz0Xq z@ZHg@oUl0F0aE;N`CU6~{ zwd$xnhIMV8LM!dSV-GbXFW?7d2{mj5O{Nmaa08omXxbEnLB*p`Z80FKyj<&+$BsAD zI9u(RhnDWyR_=;vOu=s^n5JtG3(Wy|=9DIb2nT06R7|Oa9zCsOZJHPpadI56n*5Wz zchgc+Zn+x4fPpkFw2h6eG=n!~j(Tvn%=8FOHa}2mlEUcA(h^JqNWtZyh@zA0a;@Ij ztk*U+wznti>zmsy}gs8!~MH=4|jJLM|;g|-gd+K=6YUL zG*crH6$NlNSzBu{ea*|s8Z@+J&9e%l3~K3cn!xm-DCbRf?%~J($she!S1vv9;f9qtjKy;Z-?=8_(RGcnT$9K8Y64jYMr=4N z(Xo<&twqRnVdbK6P;-c*s~1E?=R_E4tDR!z0w$n@Gq6s?>82t;Oc#cTK~z*ZzzD<` zIC0Zzp&XV?owe1_7aQvjz4+cIyfe1qf>thQ>K*L!~);{~y zr@#66OSkSV{`4>3Ke=|J$eX5Xoa3s1B0F{)!KD!f3r&cgR;mKU9qTkf8yNN!_M_47 zp`2!ZhXgowVC6H%40Nt(dV*A`p^9yQaa)XWlGa_^C7qetbmUq|wu3fhsb(SrPaKL6 z&YF>!j`K({3{Mwh{faUn#%e=tXoB*rnYWwk8%w}_Ic(l~_1?+;a(z0{--B|it_C`}z@}NBPkV z^UAKH$pK1#x{{+cm35H3TR7DvxWeoJat(MU_OKi#d6Q0_yr$Gpx5Dz2;!Dj8H%l%I zRiT8Im~tz!yJ8)sJD~w&8iz>m<;RNUpm-Y+YqDwNR>p~_Bu!G*(B4F`M^@}umDlte z8|%xge)h!&fB%cy^;-U;Ywa)IyuWw-{?NAYIB6QRxD8h(PBgb11~&ov^dK@+1$YV^ zOOOG8y&u6({0E2Qvc*N|7QzF>0t#VDmjmrW*sx9-8rg`KKqfU6B?{e8jYn<_!&DTs zNrPx@6jFKHJyaYc?bdjo7DN@z_nGq*QITYg5x^o%z=2sd`M2cT@{H72g!!jB5$1+E z)W8y(7-(wAWA|#i9>W5kFk<83iPQh8B(rxsAJmXlxaneal%p=;SVUbHA1g9q92cs< z0x3=GuHy^?t2i3Z;sk6b3V{2o5V|{aTbA4lTeL5}6VltUP*wnV-|1Mz^+P2N|;OOx9 zbbNk@@IkuD=Q@wNf6#re}>){rqoE<6!x?!~OSJYt2u!}a!1 zu5W^fu{g%LXbF|QVZzIVHDfrEx*AAnp^i@Bwd{M6!w;aP$gQja1;*uD|^{GnJe z>^y#4k50$S60Z}PRd~>3kh#Leb$^}6ZZQ-W_g^CS)XqD**{%G}lOs@&Vk0sBG}|)7 zSdkYRp|ln_=*qbD4SkFJ9azX2W(X$;`#wZE-q=uz-YQvv_ucgSgyCiS<<|+=)H)OU zN*E?eeyyH1yP_6BA=#nEEa&5|lTZ`QvSK=h4Qb;vF!94Z_mDA73hoMTJDtTw3P}pN z4DF{fi`{?8lqjJm`tT0G!VarX9eN(=e7wp9Qu1|__aMTBo^6q6Y1$`S12I&Ro@eF$ zx`zq!Oyt3mfGda~VolAMl0RO2FRWcD8fpR%*i*_JZsa9Hmw3iD$TkB8L1QyhUF;dt zm(yupuXVGdFqpH(FomY1^}{+K)-+>DIciLk?jRZhw^!F?rAK5;*w7xk3${PQM8P)} z3Sk>5uO#|XY9<^4MelP8p0JCvemFva>QQ3yU@4@Wpi_*~2nI#uB=<#}t)`#p<2$b~ z2s*0ONleBXfMU?G5G&wRhjBf8-|MnnF3`wSP?Tp-?yU`Z0j(gn-m_Z@ck}7wum9q2UitoCwEMT4#iD6J z(nGsaRhR^#>;PAO06H$QGwL{WI7_pXF<(+Gp?M@s!deHz;qx=EgG?8&gAugGTY^TP z7_VfmxT(dcU}CthO%oJyDdoUwolMP!)*Sh$mIdOqpgsdeQ`Yz{S)Wa+qHl(xs_WC| zp7{J1p8xV^cFvtycI~fTe&e+t{P^(ZP4kDPtR}fu>y?ePn6xPgP67^3g*lA`IO4D= zqvPT0B5Z;+0hVOqQ-~<XH<-{L2fiig<`X8+MbkK+#c381Ot7Z$Mz(-rEq=(Hz3 zAcq0!Xf&Tw*~;%X^ew7+{3e7R_HB|J)Ja{WQL`fV=0FcPme-_n+uq5>nJSNnCCWk~ zs4iiRh3g;Y9#l_q?u}_Z#l}P!F$Aw`OqTkp-q<{K^~`U5?dcKz-0*VLm zosJnO;D|ftby;u<4{HUAY@qmIy0Xl^f>S*Vp2d)I|0S*LVk0)4!Brr{?E-n7SUfia(Yd09#H&e}ASdak2EAy~@%Q$YY*W z=pbQHgfCZCW#4pJ!&<4#YQTa(o~y0$i6&w6U+gsWGe0G1Y;bQ=gr4IUU3+US}>l#r}xJb~=DtL}23yn4;u2B%Uq~D-+fK4o2 zb(O9Rs3O#cZZP?zVy6O6TXRTD+pt%+Ky_&$tgnI9AQZznf1oCC%VyJM+Kl)D)JviT zfbiCa2xLRhCkpz*y4c!&`ty(evu|G6m}K93d+~Qaes^~5_HyqYwt0R>9@cPS0KbZl zI6_r9fGulA-jah!Iw3S2>QP%nNS4l+Yn$M6IAR&j*^;})ND5pUYQN}`2mun(mjTN1 z-Aw}*I3OhncL3m15Jp+OpfX)G4+;-}M?9195Xlfx*(-F>B1{81PgJXfJd`)W)nr_n z)-xE<%Wc6l*=VPtdE>#P>rZF^{Uh$FLqpw4u~6dvDDQ}%hKam~)7EYTfK*H~iE~xQ z9-X%IMA-Zg%N~b@R5IetlKum>rVBYlQh)&}or(PQ{oUeQdIV`#0-`X&YiJe2TuBch z2>sY@iG%(HxfnId>9VXhw$45D*o$BM>ZPj>ee~Xkzj*0~yYIf%E|yTx!B~pq^>RSG zozq=-DAMQwPl+NXmkqFkdb+l?bM^5j&z`@uv3+`WeE87^?;PH}zI*G|(6!Zc(lkpq zI@pp}u=9e^^O6-VNxQBcQ8GC;CQBwHriw_3oTQ#}O;Yn+2!m&-Mh9-MVWxHQmgMyqV9;Wu|L} zeHzCsf{!u1#XAm)!PvmYik2&%;eqH!(v;rA6Oh)3-V!>Yo3D5cHg`&Us5&bV>TC?` zJUjiW2#jMWTlD1YQLNkWImntrgMRA<16eRzRtH>~k-Mn~K}Q-QN=)Ib>yRK8(tu<| zF+F`I&+^5=uBH-vsKIhmlM&Jc4?tAbunbAxJQ?zh@9SiNu&7Y~?(a+4xYEBUb4^2g za}@Y}SFaCu1!>D7D?7y|xPRBAM)tTCta2$3EcNE#zFrYMIVBiLjhOrh z_BGJ6!38epOErV21Zw2b;Ki6NW{4(f5Lj_GtrbBrx=L9;^`zc7l@0CUU|;%~fI3Fs z1nFlyZl_2%rNg1&M>S0GfAC6i+bSE|CMXAg1$nb02|KQv^gsOE5p?C7#n(v*DD-RK zgMnP5lm?Klf0q0vJc`#YM7N_1*74zj&jL)r&9Hz@DaJh9y^}!CljdCcfc%RJQh$*k zP$qVL1L+#aQm~yfuBNi9AIj-kUQfE&iH|d-kcNK6wLLoF6^P~y%GgQfZt%|&2~A@ZXH42xFTMpRh_dI?v%{ms6Bh27usOuBTXg-> zJ$2X)8wp`Ii!)H*09^Epoz8sEL*l#1>F`SRt zxKjQoku&iEd126}Gay5v+oEQH=PW!LeLHF^Y2S+)wj~H@!-#m9_>*XK5^NauZ{n_3vlx5)M@?$~oLWhg0WKqhF zMLGz|-85edoS3@PqR{;nyEr*@OF1ldtItP}dvWFM&Z%G9S=ULXytI6IcH3gA^;82EYJ$KYdR3-d8Pn#!GAS<+jUEL<)X=y zu`&LL?Hrx;0`*pECp7|Hi)REq5IYl9lF;7cht67|8ctIewhCy^a1rus^MRdDeD2vI zE8hCsS7vwj`XOs@z-4(=SNxi6?;YGhg*N(OtwKK3s($S$CmxEtOX!(Xf{VcsrS<1o zk*`nI9=Q0}7aseaFFkO6vwZW~;;+AR{odPm`o(N^ax7U%*ED)d^w{j{Vbnk$M!IMN zo3U@A_F=MOK=r2pgv_6)t8s{^+T(+uEm|cS-6Uc{z`$qHd8pMVosUEH0w&bru!sq4 znz_k`JW52osNjM`R6++glvg;~iY#xy6r1vl%Qx4i{q*$HUw``df9J8C_2GLzzxTI) z_1favjb?V(^$j?dO-p%X5BWY?GAs}Dxg5C@KtzIxR)P$j5GM&+XxdUzXGb+9A9(z& z%3>8<$f20n^bVJLDFP*?I1FPU9#7!Q4l*#RbV*AyL6%P9r3(G=5vF3nH3ozKW zA|XD_^jmB@Mh)OxNC2)x8w|I6jTLEk0uYmU6LuzTIXsg*q;yO*s~WL=xOH+2FOXoI z;#%OA%wKpVglL2gTSl7>2H^TJLe0*V=yN$%O&TnK-2+e#tU9gHrZea&8zC3VMQ{hdf0rDvIgAjG$M3&&{{D^3$PCNM7&pB0^%$u>sOz7;mJ>b zZu``^kAD5;uU`7$$=q1l%B(n}&AO|Z$kI_1JlaZF(hdbH__u5aNK zCaSPgpHizVs4!Bs%??ddWePS~bNX;1Y@~&tT|l%{y$?;}@O#zz2JE*_j%`($p!pad zGMky}jC3J3T=e*fnYs#-gBIxoxR-aUK5aO36Yp-geb_rWtN$T7x(h@3C=mADQO=PR=+hag5D z&3DIh5PpjYvRm=F43c~d$P;_pK?msf6|i9N!`BmiDErg!ZKPDcAMpB7oaqY4hmB;B z?I&V*8{v-<{&_O4JEuG$rJN*kOAPHl?#tj>%d+OsWjGu?`4NO#LAkiXSX8|_+bqcf zf?;fZOK5^e9ZUN7rb+J~OoK@@P*O z5~H|n#%~=$$CO!d@@=anxHkAefd;B0LwRI7}= zpj@jzT)93UdmWu35gzA~-fUp# zcuss}zE{#1X?{zt2mQ?AEG0`j)`!PfY~7u$;8Y7i-!gs|-GUZk;{!zQwg?KC*GaP> zjkkTjOz$x;)-Fi0 zrQMwqcJ*1J-eh&^PE2Z))?zW1i_*u55Fq|AdJNBAnJSm(<;JOSvo+Y6{wrh$+Ye=@leqtxRO z(NgKQ$|6L*?#`7YV?pxQ5mpls51k;!b*UJEW(U++CEaQvr)t2!9|{EGM0jreA-KF4 z+U9R3O9eWsaKEsS*uo(xmYMr)Hd6^=~fubbyl49qvvppSS^k>S~!^w&ZWflplBgT}{+thyPz!Fsn@)>lNrI~SV?FjZ_ zec-W%x(Y?s`o`99=IlTE-#quJPi(yY=H3tg^RG`ny1QJ?Dc0ujhlm6GEs;2AJsNv3 z8F1pG>Jd=Z8)mSw{~!*Clm{sS@u*7t4?c^jTaj=Qv9FY3RH)kUoB`#b3oL$;S5-~> zG7U0{dOE?oA{nW|XQXS2gh*KJL@LmLu|ewK1&$94@dy_=9#tgeVKeHQC4|$I6EIT| zM+tyrCMyN&0q8c>C`2wy4rkv&xlqhXRa2rPS9gtFiCv-y!5U2C9s$m!beV-9V{5Q1 z>bl6P^88beJpHLBuf6f!`@eX7T2+e~A~b49#t=G#W!YeF0v|->zqOHMB)}Iyj;%V2 zWQZ{mFcl~R660jbl~81PwRZW^BVT#;8^86)$iq>K3~r8NFnfoX_nAzX9@$2 zb|(nrL^SBbqHF{g1DwtSsFK%sf%#vu+)7hOK@pA~41<>y z!KpVfTIs~=Z~>9tqJzO#-jF$40oRzkX3j+CuEkALkdTTq4oK{=sR?SdMm#Z`@uvT8 z(gn3+S^ymG3o9qyVkQo@PcWy7JU?~u@?+0`=AkE^&-4B#-~Z0dx8JBI<+8yBQ`PWp z=$p2N$u#}7q#RUE&t zcT4>M_5lI(+y_W%<0yy$VIt9HAOB8?k`NXFiF-SW*%c2ZWK%p)ng0uAAS@Sixv?Qh zTVmwedr3%s<0961T(ntP-@s8dpHW}q;y3*Ti96!kMn96w5xiWZ%M-}rrM1%c*(gUg zFiyF$n+YA>2w|8tL*!J%fT&4Cp`_ENrV&X(V_`f+AAWqSqZd9LMyad9$>gIqdNLRj zi~AXmN@_Qab`qJj)jQ`&_Q_6y~*USFS@+qK*bEK?zS5 zNn%)}ev?lOx7U@QkKc=o0lJf|uvH|6;P+KQ3Ixx8iDS-~?1-JJOU>6Gg?PO3_|h~p!t(ghWI}TxkDOO^AYo@jC;u4=<_eaagH(=%G?)+_PnzDXT6I5Gg zv$kCv?dm&OT5KkX7oqb`SHG8IU_~N}wm-hFg~{WN8duOGuh01N5G6^;VJ@3)WI{fp6K9o)97t&&l3|6!oHQdS3WSw0BeS3!!#pc9amv#!l2n@@b^3om}-n-?B(^d?`xiewx^w4b{{T|q3Px#@wT*f*UEewTz{3yioH={tkq53^y_Dzm!S3Pxd%N$w z{nnjpA1-DmXD*z-@bKf0JoEJF^Jk8ZPOiQA*3Z8G{oVK9Y)%dqi-sP^N->d{A0qBB z03vT+ic>23*qX_hm-}hgb#+y=BZMT=cP^K%Rfy20DcW)O}4VDM9TG1!aSBx%SSRp8&!8;JvG%y*3oH|9o z8=ZGdTBvq-<)wb8>BTK>2Z!peS&2GW;;0RT_!7Rl{H1X_=t%82Yb$sxCKKO-q+MQirfi1aTZFs6`W0w;|!T<<)R!-R=ASSS*|A`E$>H@%i<&`nA7%<@oNN&Bs8+z;d8y z3@i-!c+?Sbi*n3LARM%Nu4|%b%xl^A$d-jtLef=AcKK;PP z{aN;RKihrvZ{9qalmxG(i>0}WoDH)MYp=%5cATk;O+ z3-Zwy^EatN6^+I(PBeuRisAUwi1xPWgjZ_Wt5OynOW5+kJC{$w;$=XaXP$0}fSO z;;YbzQJhU0foOR~7E99p%7jteB|bbHw)p-?_^-nvm9{}R6Frtf6}cZ$vqj?_%|kfe zfU9zdBg~)%6t3--EfXwg_{auFn=?NCPPoY+W{abDGTKC`rnUz8PypYE+t^`&F1DKS zs(FVD%C`T2dIQ6VnHPrna!R5uj6iP*K$EjT9bT43P?M@3kUuFl1aBg%Y=(i@V4r*r zb!epZg@ZAnVFvw-6Z5Dxg;@nW6oL+-3x@6him~Dr7^>FTZtTfS-FZ4}F!cpAgT;mp zqic5NRFLs&L+91znJ6da>4%74`vB@4LdXG!u5a=2%fP7Fx? z3wfkllZ048f{_=C{aq2tlpaEXRhpqBUq*BLz1CA`;A;K=g{rnwQDi{EBRE_MDu)Ch zp$Ray<@7`QbV&PRJ4{23>1&VoB~9Aw|2RfwC`r?y+^OL=_PYIq-&nnHurj5nh|9Cm zSFNObulPPBbceJMk5ep~RX&-jg9P)toM!G%wBwOMZ$E{k3$hb|-(odiRG5lxw=A~p z^q>)y7e)GgW`Ht{Otkz&^suwJo)NcOX?1{JP}kEf#BeT;c1Kcy$6TS$VF7FX59vB0 ziTU%}4vy$oa2x!+C0}9rXUlg-uKHOE?J%`9nw_rZtm=JnU%22>?(4_=BP<8BFNWUV z8NCsKH?Ao$bag`VQ_53D&ds*A7N1EmcQ~3buAqNUF{yd2x#iIVAZr`CUUj5F>cWDs zh!ArYbYV)$$Ea3)L?t+UL z3-8BOK#z%~`V@{~i#w9MZWE4S*E%1TKBVo?#YR4|UBs#5>8>FHhf5Lo9dstup1c!6 z%p@aHc$-rPIBoC@cBCOmbmYu4Maq+RK$gT(bR8IftNk*kPq8|hSo@H$DnzS*6D}K1 z#CMQVR5nIr5ioO*!2mqhyJ8qN&z^helb`wI7r*k@b59K2aB%)ShP)5-n2cgifgcjw-%)hijcMnCFFXUcC6^?|$t!e(yKh-?3jdj6Jaxn@}1=)u}Ic{tSs>;7oY$@rUT|STIjl}(cW?U zMuh)(Up1PHT~R(5$TFVbhPM6s+Io5V{EPqeli&EQ$KQGH{&)YwEBkMKm^UX)hh!Xx z+bNO>9zV(hk9A$x`pzo2loSjqX06G$Vu$J?nKdxehlr$t5peJ5wPEfh(wbG>lk!2b z4}EaWkKpzIB!%*65}$EdxPvmvPFb^2TZ-AMlpIO}cr4io0@o5f7hpY3gK#=f9fW?K zegpEM8xX^&7)0*ZybLC**r&`)q}7Vi@@Ax^>RBVjMyIv|-n|LNa1hf;`ew?9qR*Q? zADUug?dtPSU3u!UTkqX`?-#EZeOpxZ$;lkncVKt-04GgCW@uj!p^f%)wd1`B;&VeK zL%6K+61IrAXmA51b1a{%udNLm+ZR6dNHQGn>J7Ou}GBSW^ryBV+ftW zIVnSX>c7CQfH9tG0#AO;Hsc8uOjXVvAvFa`uFSi#s^R20 zM9_&IKqjq%LJJLi9ruEk6Dl9sRKW71?-^6&XCAvPb3aDnu7hJ?RM|u;CU!9A*W?-r zVj=U?>QZm&ESFr;=njU}ok;VRl4&aLprnY?9jAE?&5f=phKuZ}2=gV3D_Cj#eKV-s z4j3j93J-=_*xyB$NuG!{c*^x;OhaOo?h`m)JWIKUH;snms%$)f!7Bi@!dcM`JLk_` zdG=F}Jo(IWIlTJ!Ke~VI-D+)p>)g3BmmYlJ^5u=qt)soY`N{s>Ti0)Wcx`^LFOLj- z8)T4!&NEJ@H6y~zNtxl&MMe-}r0pe&gWF&~JgU=V*68tR9LgeIgOTH5ni`PCQNJ+* z4zqlTr-RNSaKv@8?Ze~=LOHXGT|;%Yv9eOo1~<^`u5aaK*`6GEzN;){Rm-fmg#byO z&%;P(tSAp5Bv*2kkJ4;=L{g_mKIZ0d z3rfBT_yt&PNG7o=_lVD+vt#113i3(N$NWR1E-tCfb~h(dilGeuutX}Va(e1q zp683b`x1`vV^SC&M6&Qh9AThU_P5PD-FHjTLJh4|m4+BnpKCvhh<;Z;$i5(&Tdq7c ztP$4}ePwuYrI@6Ze$y@wo|;8Ug}Z6{8%Fvh84yoWC8(^UxNvfv(LF?!6+d?lsyFWO z_s1_r+uvjeso{Szm`q!2{&t}vk!vOV8pcl%+x6E2mC zpAU7z$MRAAeeLoZw-d~84)bwH>-y;TRkO0blwoJ&-)gMQ>qAgcPla_jJcFuW&d8ra zOI!Zal01(lX}Vu4`L5U~EYWigZL*(W@r@I?t`Wn@SvSg6#(-z$$2No^=ma5_phnlj zP)yhIYSPV5P*2ckGc{V$NxQ}F{P{hl)W)UQr;5fp8i-o2#f_5c3FaMF0 zZvZ1YRcF$b>CO=-Av|tl(Ug;HPL|G43+-6y6e!+t;x44dw7CG`H`)*mc^$Dky2wF5 z<~Rf7K+$vg#@dODNAMCA$_Nv)nokH_1M(hF`=TkP>*udNarL?9uRQ+Pxd$#y%E|Hm z0jUb@t(!M@cX#jKy?gD~@6>tM%#QnJxv?=_B9)pGPmU0wMJ(WIo=w&+J@d)0e(PJ8 zuRL7U!^8cedyy9`j+C$3R9n`fBppAs&zkD+k1QGms4GDzDqT-oEHfj5+PEay$m7UV`t@<+H8PH zyOUNLKmdI6l413Y%zR{DN6~#}K8R%e6rDj6qg_kKahxeUy)o=H-Ohe^S=Yv44VQaf zgcR1qaud&iOd|=1=WRQwFi0%6H=p?IXD8F@-Cw;qzju4+vZetq!?C5ZlNj=1V!ufU z-ZedzTLTg_f^xuQYI4fCC`gMa>as+mUes&rSY?~1r;lF#)YqQ*>Wddnt!H-*`d8k+ zfB&F8Icg8?9yN<)zgQmL+&#K=Cp$UpP7ZLkb}f7+JEWX&8*iEQEM6}8%uLwh>dcD? z$ugpu3fgrmL@E{`ba1S=tH@WAvm7lq-Ca36v%FG-QWLB+bWNy+09Vqh2$mPH*jmra z8eZ^gn_0b9Zfve^Z(e@<;#a@==nGGs>x<%l`O!yz`xh@YAAGnt-bK6EHBGa`TEwQr zv%Y6~1tn$zqTId&&`_X0v~V8k(dZut-^qW#T@Nme8Qmd_cMa;;A*tTEuSzw>C9mUE zQEolAS!vNtQuXzbvoz`-e1?dZGlf9!C@wA51|2-Okt%YMafTx4V09p=qFA4{RllrLGbCi%wMvEt27&{B^{l49iIRd>P2Y-fL(w93|Y6C67TTFRGj* z1v7@9vNlzrVe~wJQX30M++}BxpoU;SQ$1$wfr8D#Y{E{7@us0f)$hf`K0b!}T)1M_ zFlZ#kBy=h4yqV(6zuYx#(J$AxHg+ytz4GL94?gtp@!?6957V`crk&mV=)-$AKDvM7 z`p}-h_!N8xf|AUzphi_10cNJUaSy3U>R3Y&n0$dvr=@?1Sp@Ft1(aKu9KsDvjkq^? zb{*al8e^gU94R&)Q)z&wrZ3roxX;1{DyFS{aXy=tG)x=6y3)Wy>}DM6VxAopWixr>9Te8z{1ub1O=0Qzi4o1*n+kZiB+EZ z2(82LO%To;f7%AiLZZ=>SSd;EXuuymHceOTZ)ihD-7kY?-0{L`|6~2Kem}A^^xO^N zDvMWGO?J*?{jfYdKn4q1LUp1|?sdBOWQdh?4%p885&2ksOr{W$7C$>A*h8h_st zRe38|YLQhd%6*{>jt^YDp5eP@93c9~^m%wfbFHNQktiZWtOg)FlVJ*mbANqx#^Jwu z_@wKwq$h*{jxY_#(;9lolanDqf`mS%OYy#g=?Ok_%7aWEDb&)1j>AVos0or^!${*u zy056CRxVspg*X5{uqkZ`;~?44q;@7z00IX@l`z?Y2Lw_uf{cXClxGZ%JZXkwI}Ck} zgGbU`88Pb7*I-3lF!FQ6yw{VX-Du_eCc(^@`e{11j+%5m6KBLUE1E@&vYkY+4@O2J z)`-RtpEI7`&;>aIMI1i)coq-=`~MXciN0{}V<2DGEf*5>^1!w>Q16gW*NSS=&QEYA z;9By;40&Y8AbrV9_>oD32J$qNjz6x4QaN)Ie)wrtLH?tuLhol4A+ zI0;mrQ+h$K&OjDdWD9&@KaEb{^adw$I`xRy>U zFjrMQ-B{ng^7xCt_06ZAd+yAstyf=q`Mdw&KOElrpvbcMVgbGXbb{LgN;dk{tU-|2 zvM*0R^7QAv^}C<=)bq#p@87<8b8Rx6Y;2slcrmBHRE|U|&?x$@n;jj0_}+UTy#DH& zFaK<|zqhr$ww%wAhc&6%wq1ba9BynfA+^<(4SwVa%B4p;L645bjt}h+QA_Paoc_}9 zomWz|gsHxIx}cW{22B_+2oA8nplWNu0~k=J?T_zfb_4foGB8~S2QPwEE@37YqxMn4 z$>gwvf0dzMO zf>^jnTr82&Xk>CU8cAV?Ct@c2ga0u{c>IGy5e`|QaY(YY&5S6C6h(<5K@w}D8|X%_ zwb!k?Wac?19nbcjEX=q?0qClGb2;Zb-}k=H`z)R2TAXe#cIY%@2^L`qKMC4+(h=ya zrt1(~H|Vk`uRe=H{*_+6wqmPI#SzPH=wvIF=_XaO0Fvtp+HQ70UDvOUmR-MJAFqy1 zmaBDl)M4}64KOvm+>X1gN`rB;8@B`O1_AS7De+?Si3eWUudm%)z4p>?|GjVj>bGBe z_k;WY@*jNX(Rbc&c26$17ciF~pF%=!hHDZY(v-wCK5I2R2kK^0=M(yuV=(tA&aS;h zLBJFfdehGBVIgl1Xi3a>VELwkU5Tz##NoG=7&fW|=Ldi@u__;*PSLzbzQ;~ghHKpQ zm6}Vh8C7aXG!W24DvJefy8Czn>5s^&ifU(BsVUp8Zar*1MGcGeF_Kc%FM!q1GAXfC zvn_Fh_Y;U4Gy~3oT?Gm4S|P_kJBMAoSzdePmAAh6i`&c12j6@5?EdF4BW;^uAj<&S zL+9KwD973k*E|3_qzWJ#L;x7!W12yLeop{mxmx#4yPk%oSzqbz+nK!+6hii3ZJMLwljX9X zx^8vl#`?zX#g!{3x39ha_G?$Ju3mZR#@nyme(_3k<7EBb=jZ?A_ul)_AO6MelMlCN zPp1729T`L=1GZZ79n_^4J5dvRS#)XTWKhnv2bXb&QHVQ+E}I^HGJ>?QtsEBQLQ2}m zp%t{jJcnm-Ka_8dH;TAII1|J*yx9D1U91Eyb`JMr6)eHJ2)=9&ncLK@SI0*u zD>!8|mzU?e?FG^uVFJQ7jzv!CZ0-H#5}pRD8Xu8?CFY%y0%D61M;cK=&D7TZIP>87 ztSMB=;nv}h@m_ca+}C&Xc9ew7&SqPwOU`f_43O%Zojl&E*^h=@BG>0 z?fJ7|vqA2yjgzqb&a&hhhaX%`jUk27(@=(hXhp224wrY485y%GT)R?4=duN}X2EY` zF1(&pK6++SSMz1p1zsz+#=g&30E5p3LLLOcl@?b}PR-#w>GCwVT_5AH-Chu_E0dU+ z{~z|4Q3H;aU7FahRFixU&YeZ=2o5oMg~#fwhmXK>J`rwG5!)GE#@uhl*GxULg_n{k zaik^-eW$CWgEWEGyIJgEO5UAmb~OxDv85+dLq2!uv%^bS=#}0iw)uNQOUtf3x_NuC zUv5ty)62$@W~7_iHwMoLn5Kt)_uQ)p?TB`^{#-+>bmr-5Xl!V&mV-NM^e$E6VIOUC z(SyETNLAu6yh8J~h5gO?EqUImVC|h!}G|n-hbYz{N$7dHml*_&$EnGZ1MLT zh-_xq?B7EMM8CRrYccFDPoG$YRTlf&19X=Uu8@0`16P4O$Z7LsQCMNihC)j}W3~{> zl2pwB)5W|h-SzN23T3tyz#2Yhf78`-Cfhk3r&pVGhKs6k3AXV41h!TfV+rc1nkb6IcFQto0dJ9<0q@ z)_GtSi{UWyqBHts6r3%zdrK`RQP&8zTf0FTs`ShfW?;H2LpY4<6-&tt4kK)S;c>(# z%wSm$BNgmAPI;f;O}HEe5U{&d1Iq2PyZg@9zx`ML+SkARjmypEkN@o-y#Jm5^z5^b z7Sm=wEr#uG-0j*`e{|(|yWJn%zVr59{>@+c?Z0|*wEhqO>R8a=hH2GlMsQk{e?TLgqS> z*y@^QUYJl-%RoFO;zXLUgR{v^NIuV(cH)9(!?aPPtiD-kX@nT8jCDtt#j05=+D%*- z9|Tc>kj0~vN;!$zQH*>}M^1Ajl#>IhUmV*e2$%#({wJ4~R41Ik*rrIIjwa?Y8)#cb zmo3R#-_^n_3Yk%jj+`W7Aqo02EC%^ZfKl<|@oZf%fEvN0~LRNvw zx^sEL8(Yt|cX^fVlxSmB2XINk>rkZMM z593&^tH=$VzkK)QcV79**IxVT>o2@;rGNSM&F$IwvT0Ap=?6c1{DU9g z``*9*i-$jYzuTQJ_S@aKg(v8K0O^clP_bQPIbmR(V~-5##4TbC$^O`YixiObZ&llC zfhBQy;%ahrS4^>@ncW9Q8=rQ|#hB8{Jl9l%?J=iPgcznEqZe9}hxjH&JzH;T{cbjT6BHfY@$_GFkA|JsgfM5KA5>I4&dlp`)?+I-|y6{*1UggnRu$CJ*GE=&Yg(=H4u!LBZZ7Txic z{bD(6&g8%(R)&C#`mX8YC@q!CY}E%zwH3qH)A=;L-uMqn_!;waV;DKW9JsCu|G+;k z{BA$R4!N)L%sv^?4Y^CFrYBRE86cSZLDd+~83)?@+I6?CXQrV+g37ldIjeKKzR;>^ zR^9r>?fqi0d;E}*SZeIygX})h*Da`uA>jZH0f%R?h;3zJHBq~j+dj8=AO{^-&6=HL zbWgq>Zj28;ZvDQxSN);yj;bb}l>!>I`@~OG+Yt)`8=8;-;ijDffHa);q6}46bq(=6 zdpqbe6-~tjbf(vON1<+M`m@5LV*!$;m=F&nq!&{4;!sn^ZDxFDqFXh_St-t&(B~md zCHSTX`7BNtc4QJ1YO$aDoFv41H`OAtm&vkeyZ+kE{V?vHKE`jL2V?wtB5o{U0-Bgi z9l^Cz{2=Uo8qC$nf%NV1RN5j7$3&=anR8RE&pB|2;swb2n&zaWT<5ax_gxHWO4nqW zhLEf%qD#Ldnv=5Q)SMct@^y~7T_rqAVUn@IzGlt=#`|3lIR=kGoQRvkgR9LhQ zFo|5awyk&a_9oXBxkKAcLk*tuZ_T35w>KpL->8opMfq-&p2{(II_VQyBhY-o+#sgy zfUeI{iREZ)+e;2ZrZd+FXN)50iI?t^Ngs(`k|LpDd^dr;%wo~#qXUs00&PJ*W}@D* zRXtfhPMlb^mY9S|I~L1YnODUp;_ad}CiKirXA&&8SLIXM2H3csDJcRtY^Ep|M^b9l z{h}FAAF4ovra4-#c8m2pzxwNcFL1cAR_J2R0Zy}=c95J9`NDeZ)*U7r zEDlHTy2Z+dnLlt78>6yW*GS953dv$Eht$*Qw0Tkb;2hy%l{5_%BLyz0E+d;+$Ycc% zmzAtfkRa1KU~;4d0x%=SR>8%*s?#I?>Uorl8frnb(+I+-@qmi%SU%5bJ*wf!{9&4@ zYZtYccpIX$f?8=Y$F?({uRu zvxGfb!`O7OSZv9DI6d7wdi?bKbbu7-Ax3H!&o0KzH0-w5U%GYY&AVUzg_m#NI{w2y zeDC-FU;l3W@WcIZISd#0xWksQj*5v$cZKcLr^2D#C7A$NtLFMM%*cIjrY;s&@%i#d zNoxHRI^J5jWpcu)@luU=I!eC9K(I0l=j_)fXaiUvf))?5HLW9Xxz}yN{ z!iZ7E#tDuOQpQpIH0T*(>jkNgz%TTvOA_8T(wnv+m)-sw7w_CzUq3oJIc|qxd3v^+7K=xZ&p&;1`taWA`+xr4XMgeI-GfiM;qvn0 zVj6ca6wpPdyB~#b&|{H!UC_8raM8d%O`8eBfcMS%+Rgsv z?fvbWci#EpSHJbnH{ZGQ#aqY6&0-jrA3b_@|MB?4AAj`er%#_fcyjOkpG;4lG?!ct1)yv|hpb@ET^4N+?5MSqC`IjOM0?A}h^Z zETJOyM~buUygW<8gGt{KKU|s>i1k2|Fk{r*W!>o|kx2pA^wAKBOPoYa=-BbHa=m)} z+TE95-flJz?tiwuxEQgd=)NmDgHaTBv!09-ob_;1?Wu-cg*;0pOy43m#k}uMiF7Ni z$$+>a&aJT5C=ryzcA6m?5gef)DGYN>0=0{0q!L^VEY3O; zw>Ii348ck+HpqmZ=uBz8hT1<8y{IT|o};y!E|Lm)cGExjuRyw*k;nB;g_;Oo(MR+C z3hrb*D^mdI6`g@f60y8UbZSt1$A`g64VA}9ZE&r;-}lGY7R%*uaR!J7??SSMN<+&o zER(kH96(yhn}s)S~Jat1_di*#1y28b7`SOq#Nkk$IdU zx#r9-b-(8L8(N6PUckT1o5hFO{i#Q&={Fa9#b?d<>>L^%`9>Z9)q7nrxtD^0nzmct zy1iU9o5v4inIXNE`x^AE>5Eyk@K*Zz=!kbGEA9sWQtQyp+*F^1#o;K)EBFP6y#BW<>LC=9`#GVBO0CbB>A8c^d0yz zBrVbxdWj2UE~jHC+)j4~7?M5wl{;Fjp7=#THnrH(dMP!KwPtKA59nF}`|9<@wiWoq z*P+cDEP*f%qMrhxcjViP5uF<#Wb@E(!WYo`YPPt1hpt~;y}2KEo2O3-gEMTAhCKQi ziz57}%sH!Z>CkH6_g$>?`3?+Dgh8}wh0Lsx_qu!y>Zn&Hgmm*mu9j{vy zDuFnq`=YS0sEdAnv=9T`u>_QhDGzMTk*xmH2`qX)p@$`s7cdEG+hyN-`A^e+yMy2N zZim9rHB9NQm&<*)vcbGm&F-?^X6ID7qKw>T(B9ha9{h3CApFdoqA^t;Nu(6u z3`AglOFD2#C`CO|Hd(JLK2ic!1Q)=VhtP!|NYg%|;Uq`5BXF(dqm5S^vF^L5Di(H8 zU%{L^yM+va?XwQu2Z~ThiY5$}FcP!!Ry0F#+bHjsic(Yz`_ljhg3-XvRTqy(6bguE z;1|~ONIfX7Thy+$Jr|U#jBWxt4l7l~F7x)mvqKGtaK+o@$Z%6?u(Wt_LQ5NWLyIvW z$tIy!GLKnv8yS1BG$CO}iL3DuNDIfYJT(ZiRJu&~`sDZ|OR zaurF(KCsT#6kTc}!Z4$}Fi^==INzc{kSb)ktJQwrwcYCKORwGi>Q{f|w|?~tZ@mha z(9Q7d?DGDDM-Lx7z4z&ZPv8IO^s|pI?ti}6Uhc;&+P86FWaen*Dl!pZK;TM5WPVi0 zf?}*XQ!FK2WJL6opj|bx&Kqv`N^L~XidGTRA}#M7+F;d}P1o**eG7N8o4czozVerT z;dlSuZ+`QQ8y|dp`fvZ>M<4z0ql?pL>mG;GqG^w=93P(?-@JSK==#wcU%2z)3s+9o z%PZGTHk(U4`fb12ZtAOGOu!w+{Cr_FMQEoRHCL5}(m z?a+tJ!c&aAg zi82xfmghN=?wBPSmM$i~F8w_bH=-jLlK>r`GK4jHFVfa0-31GEfSayGs33vNQ>~V!Anhzh#wq(4ZB5GimZ=rtWf1zgK_DD4cn%NG| z9TAwW?bqvm)r}n0w_OVo_--6`gCO#3Ez4nt)J(80259(`(<_b%9v4Z1aJo-@oZrpkEl{dcp`t94t*G^Wi-?@4ME5>2bw;w&({{A0- z@clph;r3@Ajt?FTm#1yB-)**>H2@-&{R(?pnhuD^E-x_N7)2*oQrxuzO;+$>l~#tr zfls|udiX|A(KYRQJidPX#V@||YhV49U;5(Pcdp*Pdi3~WeD|ZLKl$+C2k(CH_=Atf zr%%rxJ(w;pkYtO6z8kmDE&*hN2l$4Tiy-XiFce41PHF0@%>YHg2@hOdOV~1C4f8Wm z3t=-q6eN-o@o3TKYjZ6A;eszgy0vlHI+>9%|BC#g|pbA z5+12yJ(~Tjt5#%UN~?&r&P*2(O3bM61tK4o$JbL;fD}!!Y)@6e)i9jaC(3w8+$@UC1x;>xb5IBw5?0$IjH~(Vb@U> zO2r1a+tD6`CLMSL_t{0mx>0%65u$RQiCdpj9SPV34g~}xV?fTtZrjLGHBHlgIFeZ+pzQ><>kKm8WZ3HNsie-j#FAG-1p z5S+<mb~$M#eRw_nT!dp_k+(l*ra2e~0vs0yt`235A>o|L8{yOpr$?YN`6i1OG?wePjCZxb4nHl6>DHck8-w0_p3( zK1pI_=me_0a=SY#H$I8#mH zkAVFT5)7tbJbf6oeq3~9;;QRbtKr~d#wqlWw-drtp%MuJp>$5Jgjwn(tq~uxh)DSc zrYId=XV+V5O0stpkaC(>a^=M}rZ*wHLY&mb0?@~#JKuBQnlND%x# zxWrA1VE{_J+rWf!FCRS-a7fc$try*Dx;#6`vW{?qy03B`2-inQ6T$ehfmds+P1iyM zi@<5|XAIS^BVn_hb}+jobv{oi8b2zLpI;B*ooHeo@<{N-kVNwHSr2$*<m4;_vAsLKJVHs9ivbrsa}`a0XFUrihZ0Yl zF{Xw=(JK0RRUA@H@`;!ZWk-B5d1u#hEq4`s^Hz@2Vd3VXV3(qj&)Ea2vlnR-# z2a=S5?#wGe&I58O50e$*dQ_iYMZOZ-EG?ryg-M%kyB&q7^;w0E?wuv-ZW3cG;?{;iHc}xP0*W_WV(UrM>fLowEWgVl7m!82My) zE?1sKa(Sgco19s>Ur_%|^L_{C(2~U5SPX8L@IxhNiY&Lb?J+BBt{#8s7ry-0e)aGE zt#9ACcIE&3um9qY{>2}4PaZ${2jBV4O99_9_ty#A>UU{Lv zdVJ;P(aE)|i)mb~*4yoN8ir?&&))lw-+S`jPsg*<-EOmN;e&vcwcW7`h^ApNDfh;VKkZu*ah~y@Kk%5bNxCLic(x zwn}Ie13*vuxx+{p&zeP>Ku4!WYl4kgYYhfk7M!a+k58$Gr}^>FSgjbB|D@e3 z%)>W!om#RpzgH(7>Ez-4=ybw4-f%R7@F{DF|_vXrQ3)k3P5w1D#9zY zVDN`Vk)a418lljMC@suCmhBpOoa5yM(6>EFK%fLsumP(4zGska*RPOv+N~Dr0jjz4@mDg`f)AYgT7k~1dkKX&*X}Mq)Bmth&-mArRPM4#&Q7r^z%~6O zvs8^>v5A_u|BWY{+SM@2eOeuS!E{1$rbrUkpDY5VK9Zl9c-OvCQ+qx+|i zAHz_@JRJ*+wR?%qM$R1Jdp!Ztyx6VB5$m2UQOaPXO-%cOXX-JU`BJtUHlF7*f!L%# z0UwGi1xc8Y2Ae4m^+?W!{$x7vSOy+}#m|_Y5?iDK_vu{HVji>zl`uVryIOQoQZ;Gx zZZW%M4c_+KelcwskRkmtquBg#Vv@$2>!@A^1{uJg2cG&oFl?@BPs_$8mW1GNEDH@a z&suGiJ)6{ndLz~(KUj$Sm+0*+Pxo!GJwbWcluM|55YmIr4sVWr^Agu1;2EA6U&+gK z=jLI|LI0xvPsdL4zATZ)c8uk7J2aLpReO3 zK6*qjDc`UauBSIRmO_X2AG`iB=8~`LgHZw!)A}^m_3O*HzoZGS)ohiK_LZoJDH4uZ z3^MJ-l4kR{T1l5<`uV<3{g>^&7PC7-w_07lv0SzQAcmcH7!AoRwv6|OX|dKsxqZ%i z=6#;U(G#<6G#dlP{$z3nBUpdT$2F^ zK+IOXHk+^k#H=r|PD#Sdf(y(jvgt!TJ|@Z+QMmp*m!m`+ks79fu^7xh5dF!)1&&Q* zmPI)_%+P6VVh8W55=r8$`Qp{Wl6Y(m6ZRsjCKD!O*Kh6tKs-3~5m9(%zHh+-QNrr; zk7QB^C7Laf{qv%V6;Cb8(gjZ}O5%vmJ}@$Gdv(C@q%N@17#r3%HoCAWki`EmpeEb+!9K*{cO9m-rwP~=%U?IHE^H-cpZz2J$k>|98e~yA5`ZOT zUWiwc^U4{b0|0^Hu$gB579RfiGnnJ(Z9&=)$|P-1m<6IMCe%%K)=LV;5WQ!{5)?9D(c0l_so^@V1zq}JFY2 zl6o)%$BKondump_h~iBTHXuk*-Ez0tp*`Jfce~5|eh1xuvp^;#l^V8`-=Rlc)~^75*K5ZCv`Ny z&HA1mnE2fNmE&c5JRKb`uHXL3uYT=s{PnMX<>l*}&G6}y?av-ueE#t4(WBD`4<0}H z{L%Tn2N$1wzBqlf+?|aBsQyTu1@5+MI(f$^>R7NhD@)-K@`G$RRN%C~?bpj@y*j?O zZBMR!ezt%?=H+&CInWP z4ljYM5emXJC)St)wME*Ilg?ZhaYlkJ9v!6&5na(B|H4_wFom&MV9~fdmC(xEBW)S` zfcXWM{}T0(DvhDGE{Wx{qwy(DE5vXr+M-)^Q0p=`iPZ(LCyoUg-Y=9$g5Qt^%>a^R z(;i>BdgbQLYu9hA`qf82`{4A!{b|~chzv=V?az((RHy(58UY$gMu6MqAh&ruV4Euc zzOf0fLweIPkwJ2P_aZU?QNb|xv#w<=0F4ZD_Hh?BCxU=ZYkM1GyGN)p`Dc1C9GA!C zV_CZ$2fR6?tLuBeYw|aVn?GmkQmLOwQQVAb%0k0nrKIBQTfuD3%d@x+HS?8kj z)CLRDfY{dGk3+=q{Ei~9$XCuIKjCB52oz;vZd+Zjs{Yit@94Mz0P)NyMu|fsA(^Qc zAz;t*(L`GqSzv!;|GUE%(Y>}Sri|g@-FCR&UNrQKirAb?_GOaq6VX42ea7&G)om+l3lIUkZ7c4_=zpi1FWCdpO@2Y<;0fW zM*5=6;?tWKi&Qi=dl&iV^;FoaT-zf*XX%B?PrZ`UGOju9A(u186Y z2Og#B5{9l2Ul4s5m^7~Og}VLy^604TSJ0BdT*~GgnzvXuV?7vYNM3xAOO&08h6n`H zjjEakresd(^UbO>Dk)MKRS-6~0QJE)-bj{~g!XWqriR`kz(0UAYC|X>Zr;juOtk!F z()5+T2|hyFQ>`E7_tJ#jPXew5X>J;!({4+uCsjXqS$~H3Qqq0`vI+=WvLhvFN%gL5 zy?M!@l?W;wzKl;uZEOVmH5k$JsD~?)ZsVr-Pn$e9Eyj9-K+`w|h*4?G-6jxP=7N^l zTdV!nP@Qe5=DBRM@> zy6JnFs-tRCGJD-%;lqV}*qIB~h92fP=25y@M#rHcAIC-C_o9=v{c5qk`ob5#_`+*% zzWw!gzVg*CUAuMV@sraZ|M-I+|H=11{PXW@?|(dOx0jnOU?w01qVc0Ch3^cJMEJ|d z$&+tHkyp@mLBkHH;RVLmpNA7li?C-e4N8vSpLhHCi(mW8fBUce-QW4ePajmCDfq+P&-7gw8vEIf-V&?=DnMj&oC4Be`w--r&^0T+_k zipFsS9LXAMmgqwWu{=K=khnp;0*?)@W82nfRv%`V&RIu(6pt$YAJY=sxdYy@$#ZT? zn2A9%_}jq}U(Y;cWhc`d7%{N*w$`4K1evPXsf4%#1YFr+iYR1z6xDke`YVf%|LO>2 z2D$Rp)f^H;Fb-$-yln7sMGP@f=;(M*V2KRJjWIi+ng%JJa}koO;Z{vw&>IHNRE6fz zBZuxT7}tB;szXERP@1Z1`6+YPbAy09OorzB0=w~GN|>fjS85qxu+etoG_0>(M}XtS z`2w&VxI-k0!;4fz^A=h&@F3vf+pn-=?O-o7Ah4tFS4Y?^Pp)2j`-{KvU;gD^`Nr#S zzHp^)mpi0ccaP65&&I_EpPv4wKYI7wKYnlX@kje-_lNBTX$Vs*YlUIL#x9bxK3lVI zp%kO#9xSN430Pp;9i23*lV!7B+_-)Fn{WN?|MoY&_S*Fye*fP8^w0nF;Sb)u{NTeY z{bF-*etP@O2=l~W@8fCubm6(3R@1C zL{6GL>U-J@v4-LAFa}7aIT12zA4@#+G-#WT> z{pyWdeY3pWY@R(m-JG9Zo}X z{@Jr9XHTEfG?kgt9#g1kRMdnL%>_5;b5>xHT?r#BnwtR|zNlxX9YZuwHE2X;VK~=P zDw!`UdsdTBYHfQpQWQe0t#W|FZr+MP)HBT%#WJYep&*B~(0jFaZr8 z>Gx$tKf085tRr7aR;C{Rs~=QRXdgPKXkb=wbfsy!-NiGSQ06nxzbt*?L3V&Yceun= z`f>1QCCH&~f=VC`cU32os=N5PeoBUmq|naS$G0{Wo^h8n>>0O-E1_u~KdOCziYBNB zo7I%q(6Pph3_&dE8kpwmt9uK(HC3Cv4P-%IYQqLICdy~_FepI^#-iCgyzi(EnTiPw z=ju^kX^jKJuYCHuPxtpapwbvV3co7XS$&6e)rZ&3fXIBmGHWijgA^C`CGpSuBF|j= z`Om8lJ#B2fUjt+9rT=#~>D*DbQ_cV8`|5ki2*rPnXQBKW zJUqAi8qV$;H}~VTee%duepxy-vEFS*H}*;e0)3j+T3&10xpQ7sDl3!Z!FMmTw0jct9*y z)L#IGU?<<-l!`}Vo>>>aO11%AXb|(L>WU`?->6PJ!bXu z)_u_qKI_4AG)bXlNTUux8$AQay?*BBVzEHU7m|;X2!ll$8&qbv*NNhGq4UG_pE>qg zS9$ua?+jOn-z7jpOh9B}S03R)%9RT2d}HYk{Y90dA&P7zky-M{TVU)I`aKk{q=01L zFBIRiLT!=UAJM2_Qp7K%A7-&ZjUUV%!iN-#lHTDh0`S;opw?6$s=+@R6TwKKDrxtW zSsI5N7@|WsLNhvJEX#d|)};~kU0ItNqB1*>iUJvrQp)IQuF*7^?Po5Z4M97z<~_19 z6?;Tt8rXf!x<@|0j!Wm9AD@|~Sn^d*01B;=495U8DM6}WGo~SsdMKz$0y}P)Ecbmv z+2U8plTzex-HLSPxta5}1AENyx}(Ag7x4}8iFjUEucV17TT4ka;ab&`)1mc`C)aa$ z!#M3~+4Re!D=)nE=3Bq?&3C^3%fakH7oL|M-9ZXPY0tcmCk>%iUSm%ePe^9lk2ts>CM{;!#GVbO|zkLhkGWd;w#g z054Dm4CFr0?Sjv{ZQeO-HwVEnHzKy!v)o>E;S`u8NG1_J-N;8l2a@&$etqODfK6@I zjZERNpLQaMn|{U6P)KKOqXG3qRB-c{g$@yX8NPCeCwM%$$#AQuY$E%$Xxn^Iy|T=E zZD?v4Pem%@G1mz!h)*N0IIzqnLjsVvwI(8ljAe*`m^zUv-X%okxcQF+sBuwxtRdJ; zaCL?VW{MC>Gu=#OD(N$_2o3$5c7;y1q^V6QjA;p>?N2PcRz@8Bd}v+pHM%RuDAvx; zK>@=l3DAw-bpeEez&evbxzY4M`q;PXj9hkoPhATn5!3qQ);nMN;@96fxp8%x_9w^3 zUAuhkm0PdAe62rj-~aUNU;WSD`|!`++dqD|xV+e%KiiK3Yq4<}Xj+Ll*s0mK<3c1m zI{pAL>=3itu8wZpoZ92%trx!f+h6~$|K?ZkUTy#2KYjdr|M2%8|KR&4?f&xY{OE-n zP2ZkBIbB{p+g@Dkw%fLAz#D=oW-|;s;S9|AV~hgpHDkq#{h}wr?mE>Bk_7;F)-`gf z51-Mn%0#@YGV#pUHRj8C6FK6`w6+#?<1=*r2p+c&!9 zYS?V9T)Xn@;@QIoPcF}%o;`V@5jjOSl-+@5A^|~i;e@AqN=@pIYYtB$&FFXCsMb!C ztkjK~o7x?w?DKKjILI?oMvpO7>?9V^m2gHVf^95*FaVL@OT&Vd8DX}yiGXulVNsXE zpqGU#|FM~FNi1}xXs^f^-)vt)N<8Th)7DP#fDl~4YL)^Jjg-^ZAhDxf!kd%D)>6e< zoTW>E;Rm={Vq`EI&R5Q?9KJwH{37B?O|u0`XrE*QyzCeuZA^;*k^D>O*XBAL;3-kx zfc!Q}WG&=I8jnTlL&7ime)6-DRM&k0fh71rl-$4rUG;qjeSy;AIjxefMR#-s5{!$} z^p<-6+*U)Uq=C^tZvJ!oxGncxp$>+q{OKT$Q?a=Cx$mW9dVCoYh;UWpAEAM_%22af zR1)%(hn<0!I;uftuNBs&evRPm+_#cctv-~7n)MA)NeZ^x!$0oe`po^T`!62C0%syI zCM&6?ybdUqZfgMs#I41?-9CA^80a>IH>b9=`cXZ7O4n7ZSiTtOckEPv|5yEN{O|m} z>L2I(E96f>5TQxqdu2(uZxtK8rri#;2s`(%AGZVx9~pb^bN%&m*T;3&V!62Sj(rfVCszN=}uE{+Im`zbt;)K3&pv$PidJQ>3Nr^jyd-fHQG2^NrXp1o;asbr!OC!K}~rixd`3gCx~-~eKT3vk==yjuIuRZ(=X@*v1~A>!o+yDn|5G8z|9V_dCgzB zB}|LvXx;S3%0EG_S^&lHK-!!`h;0Rz3FZ-B#0P_5zCQW1vUkVFS{qW$~ibVi2pp?0sEq zgy2}rI$}LJuuVVmx6Y%NR@7TXrW=9hxI)e4b10YjUFLX&swn45PE+j|>Gdt4rJy8U zj>H0)S|*w<{z`lWnm4Fj6MhG{Q(Z#sM%F5^k(idKxj9QuPvlFX23TA{{6J+U>&=g= zia801>`~z-=A=aOtP2gcdXBuDy{0ANm}O4!RyfdKdLs-}-O=`hWF1-}>(R5B|~r@XsIr*`HrL`Fye8(JV)?2By+0(oaBG8MoW4 zK-?FWsx~d4za9A(3ehPwqe$6mdsQ3J>fc>GDVk=lm{^$|obV|76P?UGw1Wstf6|r zsUl3ob;w-c%m;WASy!1R&%TJf7J@7^3@&9V?zL!K9PgDqwmI6RT2iZpBrfV4yQAUk zRFyW}8JQe}d|p(Ja!qO$khTGCAX|*n#3Jv;m~OuSSF!IGZO;aNwOk)9uitw4%WwSp z@BHd7|Kh8=&F1~jFTVTz&pvqflc%3O+Mb>d!-&<1aG)Lbyv^kTesJBiAC|D#>>*oN zuhu6gyK!-R`}(z)Z~gjj|HA+7E4Qz%yMOa%pZxQG@NX_Y{NU=f^_82~UV8o2ul({? zZrr^7?w`N+<3Ibs>1X$+VKWWGaIu-T+x=n~Hk)y~MNsHwhsVEL?wKTF={lzn+ueZl zQ>9{QsuQi(cB*P%Wt;v~tg@jr+F zPi?atH@j{HRt0d%)$y$t?|$K(FJHZO?cT>9fBMnSP9HtEe0JLP>-_>B?D*={_0{Wl zUwU=5UL7AFZ!Rwv(|(v1&(2O4({6Km_Vm%CY1(au?YP-$jADxcO5Eh+rzA>yrrKm7 zHEv0#!`xmOHLGF|-^%Q6>(z_IO);gkR7JPd zgKy139&=p88nO7Sk;*fof0wzTmKH&kx5gWlQ;xjr&6Z)}*}>$H)j)>@I*z*~SY?cK z$th(fvIZ@z$4aeS*Hk~N6(#?0d0R06mV=A*FWv(w5;@S>Q(H=dXQ2!811@7b%9lcw zNFkdLklA<7$9p&|_A8ysVJ!oCuF8%*ySkGmi!eX;JBqzCX05E|Vq%t0oZedWG#%i_ z^nkda1j9#Kc6R}_IxiIO!h#`^UH3Hx54B``)qL9JAoB2hwp@`BMqD&>etSX|zmD)M zOxUlBXq(hoW>W8Rz|cQz5JL?6;9b3@pj(@65&n?#gFL`kX{n>oHUg1DDZ;)q`RE z{Nb!M1})_~FzZ0_90FsbD$hvOER~NL!i*w#Mj@BJ{CWCMK7Z-6y+8V6&TZ;}A71Hs z=D1c*M&@@!?snf_zqJ_0&ErSW!s%+w9D&MH^%I}(52g)2Y1pRDRE}Ey;4#lp;p=6* z)h0FNv&ffc(c(qy1FPM$+$6fbd9~MY#$915QuRm`%9!PcLz@$F(E?p7bv?G;-N2ey z^HL$BHlo*1G%?q@`~1j2j--+Cyh4-D+BkV>^l*trIIGSC$;x!w8@fF)W0WY|tZQu_ zFdwCoICeBla6;ZeQ&gXW7mCtW!9M&(0%ADemH!?Iq8PHPkq5a*1&d*da!-jXkK?K!hGdtOLK=@yOG zVQv}ypCnu{<*RpepJO$(FDa8krLz_^l48ozK{g+9nGnz*ckyfn2^~s_;tD*cs--UG zk|g&nG zS6=_cU;Nf@eEX%BZ@1m@;lrmtdH2Hy_Z~d`?7`EA54KOA?arSqwwJ@@1~uWhT{f_; zWHExuP1X!{Paw}WC#Wx?CClm`bd zo_AO_f@YsD>DW5ABKj5yCeIryR5sSad|WM^DA3z-3B(LXvK1puJ`Z^^v5-tk6}t|N z7N~!8ny5BFzmi*F)jSB1;@)!jFHt&AZ!&4xb=w_Xxja2ZWh`n86OLQV<2VG%BxDaS z%$5hLcYa`fGTlhQIgLYv`Ghi#j#ulWu|HbB{^qy;_rLLtUwr-Ruim_N+Yln_&39DyYAclcDLD$S5MYGNiOT-^#b`6)AgHI)_s5T>iV_YCpY@#`F8y7 zM^AqG(?`q8^R{n}uB?X3?Zb~hy>isOa2qxU>%Mz(|Itz3PvdlXxmDWqZnFV^IPACQ z7n|+Sbj{}cVso)w?3?rRv&*xK{eF7z`MrJ(WBMoe?>)Wu*|6Q>WZ|<%_ebJVI|LM| zUjTZAWi)CXHn2VRgYG(>yHJeyGdv1@E`Ui9JaT$CIysuAecN|^e|-C;yLVsv!ri-f zKK$^*&wlo^vnLPF9zUj=jP$S4DInyfTOBRC?%MUMSV+To_UwEI8>8K@*)l?9+U!E@f-t6Z&V({P>^LOIDWy{Gx<51mE|#$ z_P8|!0W}YBt!a|0aGNn_R6=LiFoZ*nF zq8vSinZ|EC23j7nn6O`zeh)l+TFia7ozxVC=PuR5afQRiMa=ECzoREB#hG^qvy3DaDqAkkvW%zH2kEz}yiH|Z5JFax`_OreUQWv5C4~E98z50A zf}oj7E=few#on5_@rafLLaU)q(?Tiufldi1dWNT>SsA{y?}n@vNdyntqEL;p zCW}-@yC4jck!?Ud+kE=^ zr|qG&q?-e+w0Q=nt~Ux+W8dzoO5}+Ord=*}i0lhfHBSnC%cU%nxL+KD!x$1(Y%(hf zCTc>Y=-)J(wzVq5N5u~hwxYGC)#byOQ$%{s(Lax831ly}VD&&9rv{nBWxecu+?E1X zUT9-6j}mYOh!51%xxyB26m##9-7FCeJ(NYJ(_mI5PUb`|xMruHY~S(@sN4wcDqVTd z=3!*B!Rjwo+uCv+#c~j#QtJw>FiRK&cFMeyft|STCGs@cL&9;sC6Uj_CtTtv37 zRFaS(ELOL{5zR!zl7O{a#_L*Op^`bkL=Gj4Fra6ZRka64zQ{3VL8u7@aWViSZX5s? zHG7JRwZ(?fJvm&v!gIO+co11Iir3|3rzIh$T3tu2zA&b??bcnlUcK<*-FLqHt>5^S zyRY3@t@>`&uTGAiJbL=%(bLV@<)cp@Ji7Pj;`DTTd3O5f@v{dHr^{!HaWm`&EZZ$+ zs!hi(n81*b4;0+&M#kN??c4SG%Glk!{q=AD)xY=KfAu%M_NPDi_#gk@{_&GP`_4F= z)7tEE+=81bMz9(m+)x!62J!^nTGrt|oNZS`qGaN@#`3nHr^`nnq~RZz(ke?-(U?PV zRiJmk%EvMQ;{(VIZnAa*a`FX*JN7t3PU`6xdQXnM$y}x+35A6AJ_m>T2(5ClfmCj2 zQvt};Duz?|Ai9_5?Mj5Rnr>C0n9||n*v0De;`c09)-W+9S(>6Rf{FjwN|S@yk=H@E zs(2jgH<%epr(RWuYBV@yQcI%}M>0cGb7#GonVgC6JZRE1ETvq<5q~P>)i-smHSjZi zg5@}MX)c2lv}|LK3I-}vqItt&6xy!wqVzHt5e@wICwyYt=psJXn@ z^liI3TJ1K&*~RY4wWDU)Y%jO;1YTb5c9+|+S@n;fo{!Vwv-@Y~XWP#{z6YC#Y5VC< ze){0U52h!NpMLt;dbL_zxq9=pmyb`5pFMoKoDe~ZhN^2%PL4a|c{i(m-FJQ4G^?X^ zzg{05uc7T+t&fk_t5t{VakRSJY|k$@pZxTr@BHB(J-zqoc=-%Lz1+ZoFyaeN;||ZH zm1>f5nBkz1LxT&3r>kF)0;`8R6b($(Q(@ydxqAKR#`U9=SDS{5&R=6_pvm8gT za16BPFoK6Tmf1)Au8g@B4M*%G)s5+8`9P@(mHMKFRCQEoFsXB&)GF&TPzej>)5)n! zXg+Az2W7#5E$1F>QGJNeB;blJfxf*edb zpWHRAtIpSL5uJ(|Y#AF%8J~&$#mmhMWTRRM{=u7$i&6cEeC2dkC!Q>lxA2^mgDYvM zaz9YG^76TJAI~*AmYO}ta?XBm`Ey$#@cQdt{Be}N0sWjP5*#Lna>=^7FcH0eGZJTj z?+jM}7On21dSxqRT&wL7>a=W{EzIM~UrhjyKybg#UEILL`qZvjzJVj-KV5J8fzX~s zM+4Ox{ycJTW1TFKZ(hf~fuc=h=xS>Q9RLY6V~03T)_Gslsrq`larR+qa`bHBX6PsW zcYeOoC%Pj@oiC_K=Vd@kUI)KunM8jn2f%r~G|Hd!kjmeZa%TZLqdeS65fO(=eIx@pVV;|XF zdc@ApsqtUw?saAbZl0!&hTdX3(zZ>>nG}XjD9>(6t#)uuU?4vaqHXS!@rdS36paN!lR%!m5OJ;7%eSB4B4v@`RWN9Ur zLz~RQ46?zb%;EqwEc`soJ(l_jnqJo$2dWbqz^6648RFmQl_}Y+?hZFvSi$fyf4TpQ3{#pS3#onGH7$td;p7NtYo# zE6B6+W8k!TWYR-2XTG7fMiano#ZF?p=|sxfYPygsKzqmWDK~uix%eK7TV{I>ZmxDS z9jSH}Or{Re`a_e#Mrw~UxQI-PWD4pGij~AIG(H5-3G?a0{dEQArzQubPBP&SGnbC7 zxDk`+R_KR`aFO6#5F*1>kdRIIEEemV(X}So3@<$ehtRNY1(Q+N_HkX_2$EO$f zK7H_`A6~or>gw9H>o33f61$qK*N-D$ZdKLKyN8L0|&(1IIefHq-qtl;$@4b5; zd^kRRvO7QBou9#4aTth>p-A-l1ul@G#|EE9x*XI{+e(BAZ zzVPzN(fZ1jqiF#?!fu?NK0JT=Dgi$R#%SBo}G=uesj6qo?UJ)E*H)6 z#`TkDj~<+U^6BE@bi6p-oSmtcytur$eDd`1Cm)OI&z&4Lw6OQ(BY-E7PfFLeI}$p& z_0fL6TwguDdi_S%A6>tBV|De~>g4Jd-g@)v-}=fI-+tr%=Z}8;gCBnI!|$Ixy59`j z{WK2L?<`Pcm>CK(CZb$w5}f0l*(N|CRO8DLQ7djS;jbp7klcO!jjPvgeBrIPZ@+N+ z$-_ra&(1#n;Db*-_+WSOtX=Mh%Pj=ms}|5XIVWb~u&-`fbgy()7EUK26;)m!znEMZ zq=B(701^~{oGM?%FOrX(POoxY)FQQ+f}XkFxFWp>nWL)GKd&?Mn;megv&R!%YJ$l)DMu5x&T-gh1wq?3Xkx z$k?c+&#IiY8xeSMMajoHZoP!w)FDfa>*|wqGx}Q?OO%%pCj_Z5y=Q5g;;{(8SAP(~ zfZ+IWPm(<#lhj#VAlr3cyTTbg?Kk1Qtk86ZCeg44z3HEl>N?TPDWGuB5F2!+5)G>3 z|1@Dumc_LUllV^idzSZ#4lxAfOydQJMH4NGJoZpA<4PbMB2nhZ+_WrJ6Nn8OJXfnv zg(kW!S@={1t$J8~2W~&ZSP1N+JlQJmYy8eWo>KvNf8cc#P~@J#wJ24-HMph0s5p%P zSVf0oX`RUsP5~dDW>aWN3O}-D1pS@-C#Y;918;S1EIc5xBa`Fp3EjifmAIOHztVCP zTS;7!*xt`muxJPheW2>SNDtLV+l4(`$V8SGx)-uZh!p~M{P*s^%A+WTspawM(lqzI zpaqw)Gq2Y%oB^F;K`)0LSHO0H=4MIoX-3cd48*^{FO+PZS%+L-+dn-MS?Z(~JB3w= z9%bq9=>k`C-`axInE8%pGxUEcOQ>G|fBWZ)aAW@~11p4&1L@4->t)xkZ{DT}5555BLNCHlVJ6Dx4Sz8J>v^rQM_c3Unzj~EHnBj)u*+4smg zk6+?r^?8WQ<*pPif{&e4Uv1(n^_< zEyR|PV2pAikRTI>($T709S`TH44}%MsD%%9qtHrjT5QWS8m)X%P0TV4w?#w|)wo8f zf^M8o8{V^r+}fo~&o8{)DV55GO7cw^PWgSc56#=RagoTK_&J>g6Cp#0Mrr)SUC27& zY?-&uvbfxL(d?XBuSPykJCSu;IM>Fd5+Bze;LDH&Puvm|RDH_Gs6>}Y16~OqZZKx` ziys-Wl#NJOzGj`N{-xmFwAsc`xv+gI6lfW#k1=D90ith=e=H9+nQq90T8meAhyGr* zi|FuDfQG*|8DqvrW^acmq>KP&;935mi7>1xO#%wH-Mt5$f zD;$;4dD640I6<`Y3^G0gU*5Nkv3i`4y0C!L=bj5&&~p~2?%EG*ZOz)RYQ)SB4?8Q& zkD$}hF)SAe4fFAXUAJ28r)9TVFIVgC=*s%$wQIL;p4`0IpIm+6mAk9s^_>@PUAun# z(n~KqdidntXOBMq@RJ|>=kJ}}zc*Yw-JPG0yGw*KY_`L0*Y(|My`q&syTAJ4E5G!s zzxlhr@oT^Gg&%zQ;2-}F|MZhT{P+9uY%y*2yImOxmGPwSj4x~&Y!ev@FR%Y^M~?6V zv*X3^bv9BGVMLyI^mQ|Ojj=uWmM$>jjSS~T0Z?a zk^s$QE;_Mlef3caM2K=5)nbca8X6)JKN7nyg_GRfRM0#9)M`0<09n_hUM{M`y1qKs zSw4%fWt29cFp!ib^Eqd!sUtf0P)kjTzTH_85@tyxs22cXgr7j8S?gqjgnP>schdGN zGH!^$o;w+QYf9t(J{0~=}#dhCySFbJles%Ta;@PuR zv)Da(w!b{vJ~>^s^i|m}Pp)4*KYIokWjAauH`9Kual?K^ZnxfMQ z3YkRO4P2iH{!*pcf~TP!MB;Ok@}!<>5OdS^?JzEHymvsFt!Q^vVNPCafi zshEt^melMbrbQ{`+-XEa3j5Z!>-rHAj0{lSP*KB~Wsqu$CT;o7wj8ivnd)+0UK%|Z z1WCO|qy+_P+TYX_&-*x3N390d^}i1Xt@NMoQz*1?7S-X@$9u2h%z_1Jq#pxOy^qEv zhN>h;tscb@4H}fl@-hloRW){L)s0#%m;Le8Wz$@qoyLVE+6TeHvjt+J5AZrtOwYU= zUyXr@A&F&5pK{o*IqxiFg!l#qRtsO=CLOire6igj&%JYntcn-n!Dryw5}z9L(1sIr zX&`{)9QpogOq%OIcaz*wJ=_XwqN<#IJ*Uw4uW#I5EZfbadlQRxr9O!wI(je{Dqth`qg zv&K7(UPGkfnR-#5r*ty4=W2ciq(BF7SwCbv?s-n;tBM~mPIvG+)lC+EMUbuX((MOP z)V?65X@&|BOGtL{U~0rf_p`Ryqr`*_1cu9fk9e@v3gyKxG~+OCHj8nGktvPn{UOwn z9rbO0GG072uQfgyVcg;KEJuo6!!XeH=4q;Nnqqi3H#p9uDfZ_);c`KfdxE`K#j&cm zD*JTA)5sx$#s&1wE_|yqFK*CG`O$`DPschcOfuB|mU%;n)wLb~In$JmgG6=Oc?1uZ zbpU@qQbzsxDf%AqOLXnBdQnD!e#iK6qGO<%2QwkJg7m7$!!SRxuE-TZ&#w>^T2(nG zHu9seACirJXFO;L>vn1ZQuDNmw$xJA9jB1a9^`hJ72vJ$N_1@ zooE4lG{YzgzkM!Q6o1Gvko5{uxa2*oFK>}KdKD#}QIefbMy>cEmBTlN1P)s0Wdo8V zR`SK#%jbP5t68%L=fE9gB^1EpWi*dgjF9t(l*uBRg~uT|o}K3`004!O)rhJH;+bN? zuMc&T-iuSGRskcqB7E^O%G^;za65skso=K3?bNbgEeG!$8rjWsSf+uS-lhB_&^P4j zZ=OyHA%K$#5x~a7V{TfE7?bjhg}o(rA@tY?N@-87?wi%syDz=)+AA-;`Ra>zUwG?F zFWtI+?bCaYA3lBd`RDh4`u>N{9zNV%obR5To0BH7eD&$#pBPK48%&F^C{JBktr8tq~MXQKPw2z9DC% zGe9H3io6WtU4Q7q=U!t15wKuog<0UGK;i)SPD@BXjylN%h`1o7P{x|L7?4Fpsvkx% za^)D!-1&uJccKXlX~EOLpC^fgn7+^xl}&UQa5uu!LUU;-S(~<#7YCz`@NhwSu%B*! z>o;z{^5&2K?f=qlVRHi2T;J}8T{Df%er!7^GTJN0C)aKa+s(8+A1{a9_L4q4+H*-C z*=YgeU6xD4)4+XSCQUx~q+PR3Yz+qWTe2k4pc`I~o(m!AnVSGEhI~=4-g)UO-}v^M zZ-3?b%^S<*{<8=7e*C@fee(Vfw@)5Vo9%A5>H4+D+IuWSt$!<#=!4UCobcRM23R|u zdJ)P6v$Ocv!&Z=GpyENWV za_KD5oQJ7+i&i0!raI(ddtMM^93sgqHP?6LWS<3|jMyCfJJepO-VTj-uTUExxa%7? zmwmr|_+S)8%SkcS&lT|?;9d2VIA}rH*#DfrLn3+(`ax+wiwWa?WadGoA9TO(xE zpH}{=eKCG6M>nl6yEq?N@g49nt{f`csbA3ed=;ps+*dxCbLoTJkCnJ8t+lAqyG=%^NCOn>mssPHckX(mJO#1ANf#&13rCr{&b*JINXRM~-%cgAHyYI% z=U6GE<#Xj43g>kvLN$wDk2Z#`lP{%XGi2tp}ndj7lh%-7N*ebcp=cR zf`LyxB{hl4ON&O|1YG`hxoi;!u*8mpJ*itQ_Rae0_5S+pm*0Bh+MU}kzVhNbUw!lT z^%KAsi{<(G<)cT>KKtZh*Y&G)w_0~Ezw}byPcOZA?ZIaHAOFF>`QAVNXVcTqmd!|| z1uYoWLlkb!T~F8FrGvSO?h>@HNqT5UOofSjCML7&$XrNzrmZr8qj>+D2U8;5#P&=h zmdfOFv2L=H043oAbZm(~2zyQ!+~g9oQj$riZwaTe!v5mH91m=$A+SK37S;x^Z9qx9 zlLb0Tb2Rx-?gR7MZmew%GR8cNW(nH@;M0+Mu^F(!Z#hU~6&V>CZG@Z3^CJ8pKO6Q` z6kj@5qFR-d|1OQpXC~B-6^A7Rr%haeSfm=?piR9|U=s@|SgRO8g{KzN3LpebD@P_7 zJ59z7Azp=~TtTZ0({jHjtI=TM@Pq(7w7xUK(mq(Dy300CBs-c zr{j8G8=4uIF#JeJun`Od!3%r*sRjBowEgJ{pJZZWy{% z-ydIDU%TD3%gyE4<>N>D%Z(^t3VopStAHWcC{PNhN?e~(1t+5c)M$Vm;gyUS-2uj~ zSUK8^-4Nlyp>%OnJI(Ea$k2$`+Qqc&PfqT<@r5sbf-GD;lq0$zyJP6 z@4mk|JKgVhoAV7kd7;MGcPw7GBEiVIdgt!zU;NU`ufF!;3%4(~o9*TH(~m#D_t~ds zPai#b@UR(o(@0r1zUByKjaY2paqyb~WJE{ps!aubj|%p1u5f8B3VlAUfi(?TDnZ=vEz|RxxCzqfh%G} zU)BiUK8bENt7)~rq5EHR^Plg3t5wuatO0HH^|}OcWsK~7#y_9$uWRO>;_txU#8&q# zysfUtdPWL{C0+gtK9eH>KV3!T(CS@D%2JNs5>Rp0Et^L_W6rJRCsM4MflTw7(qaXI z#0VvomP%wByd8MOU{?*Tl=X=ZtutO^63M-O_|Ut%wjep%`|h)S=IM)+l=eU+R4C&n4+9o`RAPp zBEW)=S*OrWHQ0e}VZ@kxVudnB>BH-p`yx`7{yguCbw_(`8eS}xef52nyQ{D|o9p5k zlciT)ze0zcU4ja-TdcYT>?hl0w^HgdWz6HW*+GRd4a*%$Ol`B6HmJWkI%-x&)A>_e zQ_-T_IPp8kD$qH=Ldf|I)a{TJ!S$Kmh1xpD}|tUZ|bMcf3> z*7(CjeS0II!fvAz$oNZ#3t0EEqQLbLW{g!Z$iGeb!y*OoiVd!e_2)!Jc~+C|YvUH& z_uOy%ynW9KVDjfwmCh6l`?#@nXnLezEHLH4c}%7{PauK$E`!t_SKDdtV=>3Xb8&m@ zxs;z@0^(c-Fs4wu6?%a!RP=7-`^yhZG(PyVMDAg~4?!JHSaFXQ>w5#SfPrA~M?y9G zH69YQ_lk%>j{yFZ0h2_sWz#itKGiD(^Dma<0YH$gBAHTtaiT*mSKc>yE`+*dH9 zy&p1_ljSH~=e$ltQkNeG|3?>49}trA8cD@~t$Sp^+y_J_nGI{buX?{-cA(0zJ;OR- zn;`>N@Ev_{uu1nVj{z!tWDmwMG_neXE2f_!WeWfo=~SV+g7yKJXlBf0Z(T{#Q**9Y zP3y`rYomWMJ=S13zl#kN-%SEoC0DXUf=5)OnkKgc*zvqr6XV*_?6P znR4Is9O8N(PKuh8qT(Cl7~(v|j}!}JRt+Gl>j|Ki-U7yGKRjQcZYTvoY=8tWLr>1h z`2ak~a5nv7Z9=W*sKhuSDlsP$ONxkvG8Q^4^I@oj2=>C=as|Ix1UH6=ZV9Lm6q>md zSD3xM>Z6EoBlDt2 zHZHn3cuCIES&e0DawIylup70<0slB)E-8UyR;j0u#FeoaLOrKx8jw+8j7P#s&^=Nt z(U=g+*pe(rh}Y|;ZHLVUJCXn$fF0<}z1CuYQPIfZ&4pCq6apP<#gL;Dz5T+A_kQ}5adW|I+D=WoULQ}3X>)$QJA1s?Udo@*4hn8WL}N>!S2{}RDKmwW zmTHfsozhlMx;a#x<4BZ6IS&|Egzfi$c$P~jCg`oq*qSB6cbCil=;p0EuYU2(x4!iD zSKsd2?%~6S_wPS^bpQUxAN+K`IlH{Pyga{Lf$}!(yY~3T?OU(B{>B&H+&nw~_^0n* zoIW~z@^l)va4*?y7yHF_w>2e zO<#m99PlPKAJbw4wG<11U*0NwK+;yCD^YS5DU&qqdPQMtX~heZ24!g;J_}{k35#CB zFQfX_=ai>Y!Yf()vqKO=N(^1r&!MhxUy`{44qw3Eb#8g=Q>Yt;24lP1pkmN!WQmA&lWsU&1N_w9!=|69iYv1= zYaVT{TlMxl7y$dP`XExV`0dKd3M2acqEGcBHAkE(a$orIc`k4lU_I|xhx8Xhe!7UZ z%HUj`IK4kz!0a-WM*UpmY8v|RX0RTUB+f&1`4`}S(>tsB6!Tm>vfB4ouP&DDaCS;k zGye+rT)tZq)adH>@VzwP;RzxmAyy?zklWa7)?Jc+Nnf)=^?h!<(QSSP5T#&X>Vkjp&aG6rOb%K98Iq z8-9B!>+AD`{1_p-h2hqp9I%mP6p}u~I-es!M23SB z&%{hY&@j&g`;wJ@+g_3OQWTSu(o={pnq}YZo4#AEmY7-)$sB+_EQbM^-q@;;rDmu` zFw+Y0fKUkR8p=-LL=6d!S-wN$R8ByfD=g$-TTa(D*G360ZUVS;jXzZ^# zC|iP?K1g5|i)p*{wISspn5-y2{Ig2hF5Vq!(9Pg7*&wjDQGnv z!k|QXb@HeE|Sj#PkTAlOVSZS8>ypBI8AU*;xMOB1*u zsj6jJ9}n7jxT}Sr4p4(P%nHkC3AIs3OBs#Sh8Km0Ts_s=@&0?GAWF_WKjZCkrXWmN zkGnfSk^8MwBDJziUh>{*!7@eiBpK~(ewcibuk}}HQekwU`OVx zHf=B|Ci$15z4^3Yl|tJQo!2o101!hkN|NmOD>4?=#;~zngm(&)UlIMIblXDrI9Hco zM<+5b6sF%9wD56sxS05pw)etDk5N6nPP9+BEO!G>Rw%vk0Kk{0DD6-Y6(f&fMRFj~bJjprj>}N-kKji}1nY#ukspgPsY#bMA9iKQ3 zPP_1k&FAPmX7#z=G~+<ypayNJCsjRwksu|H%#V>J+h?5*MP;|f#!F3ASI?zuq zGdMU-QwLfEr=tD3UtjCj$J`di?dE)Uel`x5@U?A`_<;8UAV}m#eu{}rH8)UuqOx36 z{p%8ipcYwZ?GCnQGV{&FoRh#K$7N9@I)wy+8l>$3Na*oHt#&+l&KdB`}kN z&WlbD3p?0Z4-Djs3eBbE`z5`%nhK~v2zwtx)3q>ab{u7l38NZG9kC# zvdo|&Hcy$XGBNc-QFyC(Ea9$!p7~6+ovkn$G8*aulk>C1cUm{0#~(OylqW{9FXEih zfdSDCm(SR@Bh&+nf|RF;NirjYuS(3>lL=KxgF>gB+%LIBg<&EMBcDhXBA!lrYy z#Xu?wap3f=T&pWV(`mQk3g_F=c+smT8WSG>zGm|^Rw?LEpY-G2 zOu|R1LrXY`M+(J)j?bX$vV#_qqr~#Dn*Ywsl>EkQrc&K+ngj1zwcfm6wTq+Mk>cq) zsix+4k~5UpdUGG@qf#A*;rjV^H1TjGgEb%d)JzhW=Fa^k3sL2bf` zqGNw2!_van1bTu_sM4qIoBEU7_xZusb@SdMbTB$G>PkJrkA0|()3xHtAc5_V-#Cau z>U<))Zbc&^Sh^J8Me`MPt;P$l=A!Pe+W+};vIF3UZ=0s=Nr+%IOyhS2$>4Y!Nnvv5 zk)|6HmbU3vi(%`Q%xg%8OICPh^-7O(z-%2GYJCXE&!crH!MIN7BF|WeJc#0NXIpjO zC&0Y!i#t=J38t1g7r^nPxp;XZB9f|QDW4|q0HnL-q4HYxBWf};PCCOQc2}T&n08UK zlaML;e%SToxsr9s60AYjg^hroFM(6iBk;qxz1EkWRdOzd0=L8)rig;`v7q`PIdiI9 z1&g3cAqT*2&a=e{{=22?aY)5k{&S8o=L=;?Xg-A)grecZEIXe10zXK+KX?*7EZ5DJ zkW|}PS-i0FFBeR8XKK0vi_Y%4p{VGi7BYksF)IRQI48%X(M~dTbW?7{qzcgn@DPd@wf?O*-&-}&!; z_dov8pZw{+_@BlHKif~|yY0ntIdy%};}XI^-|&f8dd$yd-0Wc?V;o5@<;k z4K7-X?%9qT@gwsRk4%XuN-bo&(Flb+B!0Sxl;wsWr4nU$Nn{G@?!a7@P!#RyB`bmO zqWIV)BU1@5rOSZ-0L=XT@d#jZ^TKylwyptn#R-a1h2f9W$P&S;0wNo4$oIAo(8@wA zLXkx4fcMnVc!Zy@V4ey!Ik42yxbR>YE80T9eg{wSQgY(0$u>T&33gTJ@@(e9q?kw} zH(y_MY20mj8A#GqCDbZO*oF{#4LUdkku*RZ*#(PeaXVXlec&Bn9`>EtcKkpHo>XJp zVV7Mr%Wlq4-Uw`4wi#KoF zJUPD7b-&{H@H7rsM8rDFuPO$Fs=?ITBfqhXLYRaT zW}F-ZvO(DVQ`*qj`jT{F_{F=4>_Ob(s;>4iX`@rMUE0p$cX-%s80q$b9U5Rp^{lgJ zcS`M2HO#6_E$p?7f)84I7mb-Q+73r!82eU)W@@P3sG1E6EKH9!!mej=qCFVNxp8}b zQfc7XwX5IMXo62R-UtAWN;bjQRj~m=ZVc}aLVsLLS|vJ&szm@MV4li@M|N zoNi-=l>NDcK%35!J}7mm)>S%or%j0Q=OU%{Fv5JvEvXx7k!IDgn&(svRg*?f0KG%m zecugMJ$C{^2|1;`Wf9Y^R*R-X0uJ3>T~MIE^K+iPue|&!-7VBjLWYUhjiL{N$ZgM}a1F;Z%J#@(^o^g!om(zFakBZBf z_Q}AFO(^Rj;zhmowq%qpOPEq?*_D>2VyjBWUJ$D-Ne*=&2e^ox;PgQbA&?^cxJ;A( zs?pX+h&>)noTuozuEOIbtoQYFrdS&>T`gLadsVSzTJgI0yilfR_=r9Teop6kY6@JI zJnNe;?8j;I_<@W>{iC&~J4csQAc37Zch|ZXLxT3_llOLAH^a)AqS8v-kb$qKd=O$Z z;!qhUM}{+_eLAp3fzkja1*uTKr+iuymm(FWzr&=W$i%i(X64&e_sa-4g{%lQ%elp65b&{gNgHNp@=LvfxX{`s%+hm0IZ!~(b2X*mHkGlFzm?ekFoKf^0f$1uDKvNE^TMz-@sC20 z^t|1;DBBgh=}zygZzD#G@2CTlY7f+Rbi}iB+$+;W^CuDry><9d)BsNfgF#4N0J^mz zmsIjIvorb`v5BtG!(&9mKvm!6p#0{>0bzJWr{xL%Ho1M&rRKaeau|y2to0z7Xcg$^lJ6qQkUf5voZR>2T4sYXO#7f-~HY9-u=lR z{=@(G(+_{T+>cGSn6{8|wV*$Ub-Bl&RZp~>eR*LehY&@NhOA6-DhpTuvOI7ryv~5L zP9E(WR;~)!)lda@-MFpBHmH!QoEI+V1i;Z?ipojjt#qlu4|UvIBfPK-G6ForJ55Ic16(F ze1x|MSpW=TmU!F_b!XakCe^9GDnLrAMSO;3U088IvOfHKal{Ej%Q;esz2@jr*?a z+a6Z*%f5Z-52{i(zxIQCl4imH0h+FNIjy5xZJ; z^%`t-c~7iy&_&nH+{5j{WK*wy%|e)7RJ4CT6nF|`w5YQd@(@Mdl1g#lUgQLI7oC#v z%d=2SE9zS*vn{PUf#M7W=uE-=K@+12cav)X#S$)RrAya92ue9VI<{XfB7_mon!Kdc zmA8TnCiUf6K?jLGXn_(#Sys3X$?^-Cm+CnjWLkW{oO98ymJK{i=qF_^mCwP%!`s$2 z!K~6KRpx?vI>sPNRIlSw>>a%cN9Tp^@N;U1(QBKc=w4etZ`{E9s_55;=eulnlDO$U z%f=Sz8o3YHX|RwNwV3vOQ!y#(6-|pAOYg~9BAnUx*-aoS%1Xz;U*QB*H{P9GY1)2w z{#4Dn+Iy(gJaW>_t0WX^;pux7B@g?f18;qe@H|cuWGPvVzEp`9Oy(&chbkchwZ|bZ zZu%0Hs1IZFKoEoX#&ETdS(74W%O%^8T86Bv93M`7#H#$g{6bri1W6Wq1T+Nc7DMB? zgp;Mw!YeP_UM`oH4<6zX=T(lN{=@V5cWkh2yg`~Z<`}J*825g-hih)gF zITT4Fg+H^sxzRF_PXJq+l`)g}5A@cI!oZij!N&v{Uj zIsaBnzcdo*1=VjDyee@xHwkD*1M>04$)5s$F7~H@c+pIi+AZv->-&?di~WAMI4dP3 z4Xuk-#4Fn3|FQvD|H#I2rq`>57Ci@_Utu>U@Hjt>vy`-8hNt-!{BzH0v_%U#!uJa0 z#7u_p-_UTibsfB6>GkcQYNX27)5B*D$_xU-kHCTvlkRwNv?w*g!hud!e%pb43an0} z2x5<9GV+$O)60&7pYOqfUW{A1c;x=t${F|FWtj>w-#Bg^9ua6JWbU@ELqbgBWQ%A% zG{PC7c*fu^zkJ2aqh#O0{?n5!b~xIDG*fzxF3WS4E5YXH9wG{KRN}V=fY5e&p=jlZ zhQI=vgFot~D0L0p+E9naD)yQd3(IOB&UtuNz|ycre|V<`lQH|l@naW_Fsp#%kgEC$ zQY4AmSdR8jd41{Qs;4ir66x58zPhs3XjA}}1cSvgDBRgo8q)%ah$_2T9v3Dn@Ve{V zb5kKx67C>o>*&_YQd0+;{f(>S5wNPQP<_6PBP#j0DsYbk!z~phL7y+|2Fp?AuMxr; z?@=Z}D5q?)RXGAGS{!7MbrtP+u>t~#rpwmQ)MG+A+hr)LeKiKp;StJq+#$-dF=>b@ zw)oQmV}s{STlE6}md|y|v(k8xw7A}t3E=1mVf&*O1OzDzMQZ0XdZjaTGNNrgY<14< zfb>J}&@S!d!;L*3<|X(qH6gNwz@M01iyO{I38P~%x`~$)J0)ttRvZh05U{~Lj?(L1 zHx0(6EJ??sH5%xvufP7c{xARMk3RVL_y5s9-hBGAal1wAgQL{x?oPB8O@;akeuJ4e zBReN8s3qjwT19FKe4#z7srh~O)lL(AR@K}D9X2kdG{fF&bY!4@mC1%#I7%o15FEM8t;&<{D%u&gDu>;#UzUqg_~TH$OhZz#ndJD`SVgG-G%oXO$dXB+lZG744Z|nNnX8{= z(xg~3R{NP@SA0~R^JcM8G{=Ly;}Z|9D19pTi(vp>vmeLZ`T6ehd~oL@Y9^62v6 zeegFNRG+p=3*WP*Uwb!PmyEr@D4+!1BGLaB66c>Do!PdBhTld%xgXY<9 zh#yj<6i<^gB$QUh93-1VbC+U>&n(t7MUEpNF@{NAHQJ~NiVo-MY4cQP2suwMT-T|Y zaii;%iA&h=bLmXB?|^t)Wz$h)hg8EZKIf^vVvjt9GkodWsHg7Gvmxlw!I4{km4lIb zCA$OB0Zp<|Lps6-JrR%0i7SP}87L__`QwyZopwC|9^N1$g4W#F!IU$r)dmZK?dsL4 zjh=z9^eMuB-5;g3t?2;$;QZyvUY~=qyrX@`0u_)ZRhi!+7;#WB*Rl5X#5Op(p0^5E zu1b7Ep6^xnMgj||kzGo37#DW~b+w8bUz~2eUbNkQw<#M$mpAdK^OcF+i={U-sj0zF zxFPHZb%FpRj7AZ4h1V&rqylTT1C!5MDpa+!qS29x$LX4KRNU>`Yb+Xey`l=5@QPVI zT0vV3K^KZNg%wVNRg&(~4LOT^H5wk%%PUFMCAX}?ev?>UJorUc&+WUn)_wQv@!8A_ zG8|N+WWS;hL(DwXB6!vz>_>cpIW9D{t&SIKSDlRhJf|!?9xeMD4F0p0n>T zjXLBhHyY{@s_)j4qtBP>A$cyFo`WgM>V*SwPPVUH6qRblvIsV!-({qfx4hZ(fcw19 zNe}0>6u1y$DpNd7mpb7t=7cu4)JIsYBQNkGfn@z?j99c3?*|_HMM+X5xbVrnaeFCg zuE~?sxT`j8e{vQ1>u1k6eetuL6rz9y0i+B9c%}M~@>VSKX}Oq+dhM^lZmSe3 zHPtuow07g!;=v7Mof|pVi=pGuP>y`c6bzG^J&|$ufe1z6Ig+%PUf@tw(Y!_XEr449 zKYC~qo>9CBkLWqon)bu6A0`YY#6Bq&kj}imYgemjb3taW$e7%zw4HDg7;y}$-f*mH zx7OytiCoc&{dXb%gi>fAJKrmu^HNOB*E8HjM>-y!GNF(K?g@PK+#uiFdgU}2n^)Vc zTfo#D%PhGJMEmj;4RKd$3NwhcevGjJ*NBI0w!`Wtyf12ouW5ow6(Qc2bh8Bag6@s9 zngifckQ!I5E1nNx;yAy}>%zxoN-BXeo-u0-5aidXz9N=$1IEU}3RJ*DngTcb6=SG# zZvHoIMsnyVoKWqhb&us)P|B1*YvrM;m844~YeOqqSlO5j*@EK16oA}dUuluzBsX(# zA4>tBu9oSTj>a3ur|E*c#suq%*Hl# zLs_0{JnXeh#ErncWdgXg_V?FNR7HtLs|iDCc^iC%(eJW5Vlj#y8P=7URg3jKj^l1b z`L$oJ+r|3MD}VLB`McZm^Z)!W|HZ{eKLIw%T6`LJDV>Ss)d<$RLXmaSOVU!*4SJqU zUt(iU-U*AG7_L?1#r$}+?69|T!tV;f4}%UcHJr|f)!>(nG+ZjRR(Zk@hLJj{W|KUx z@q+NnH^u?9NF?FPGYgT+I1}j~(YHq;89MR;M>`q7 z#y$c=RKT1oaH%C@TVI*$9*vndpdw60&PZBzQ94!yF&{OyMN;YKsd?EqY2=t$RvEA0 zAR#qRw<4&ACH=H&&__!7ND8$#72XNGIKm6;zF_gVpW%ok*~lo!I`$1}2sNDml;+z{ z4h7#Gl0s*?>h1_2p22DR>LKA(XMuS_+$HHF<2ueX9p0td=rd|Ewxs+?jQ0eN7{O|Q zCdwv_wQ{6J+R}xR4cqO-#gluVeenLfr%zA6@(W-6!dq`&obN6!PVtckvJM61*$9lo zhE&F`DVz#k_2*1}Pr_hAZB*yyw`_pr8YvBoN(DimFdOErLcEOGIx!?j^oF~va&6G zvI$yHOpCz%(7@*qkv!lAV$Dyrsh#o}1kLZq!AL@!TKye33rE54b_YjZsE;bd6m0EU zQ6{P8va<=)MqLy2_|&?PpE(Y5(Rk35REKF)&SpLJmxo+zmm$Gv3_WW%w>y{4C=0o) zLGj-0ons~xt4Y-U%<+thUTJUz?YZMBoJok}dc9aQ1FUELO6>Z)TUin(3w1SCut<0R z?S*1^y(%6(`!4^p70z%{X6Gi$_%9-n6`moNB5_*%=k+swInRzgd2*9est~mc+`xqh zd03)#>p6WvOnk+}EmZ@b6Uwn@TwX?=eUqweYHF|NFlJg`S)bm2EG|RU=RTJ}sj&Bj zc~#y_RH~(a45+{lA3AM~6#WaEZj&jSLU)Dp%!*v8`;%^&mq^v<%`SJQ3Kj@QSIa3ax!tib=%L?SZ) zJ=-1<>TgOfl;s)}F?(8-b8~y>@8#-81&r3Ob}J+2-Z84HP?ySTQQ*JU5lJ_a6gKVg zmE{Bmgt94S1TJ|nHGj@s5{wmYP*4PcLoSnaN<<88q7a9^X&gMgHIvnwN_FDd;pgfv z%OD(|T>Nmj)6FX%zOdLV%<9qNE0M@7Ls=T_GcL;_;Rw&U8e6uefFewa!dX5-aDkFv z;RT#@pc3WB>X4l=Z7-#DOxq>sQJ1(-6Hg%ZEOBD#W{00}^x6&JK*y#7$Sk$2UdoXG zrA&x7<-rur-_1P1xKS2h|D4&k*F>(k+-gL2P{%GdN-P^OO43N5Tc^uqRhISDB{Xz= zn~O$?L}ta7ugR>)l6@$O=&r}29|rm9Mpy27)R4f8Wbu+k!BD|mm{7ldl9>8Z5X~W6AdVa zUf&cHzPktIHX`<70P)xa->`9#;vvx>N|hQ|@W4!XasVe68U;C__a@sD2xeG(HA6le zd}zdFz<_pbG$Qh0R>~q1_-WbbVt@V{bs}!(O|Xw_Ec>RGp=a*yQmI*Rwy)Be?NXKj zmsq<7y7UORA1%q5H)~CTVhQVU2MT|2R4B$a_+(TyprT^7I9QJphh`v}aw_jYS6%Vr zM)>$zd*t5fEy;d22b$b7q2BeHI$fz85x^7;ld3q(T%BaBAVJ);!no+M!}zwD~yedPS$1=h2c zF_!>t-*2~j0#oDw@A5Iiu?&*~lu9pQW{W?UP)}%2v~#%yat#qv<|-d~t%`c1Bhme} z_8XaN(AeJ+4LLljQU?b`=Y|SztzUpRBm3hJ&BG(}FkD`fI_70yOR61-{+h;<_-cHB zNezy|1!IEbWidQ-+{GF+R+%8Wn3$e&Eb48G@QoHJSt1*n$E=#&7FwONMaQ;8!`1-F z=E6cO*A|?Gi;_&uN?t_}fJdo`&8DTLU2>Cxro)K9koRv@LM9a%LRIR4ZnldVat~su zq=PHyLoiu_#pO7tvOAL}%Ie}6$^cXoJ9uXK^2*FoRZNv)s-i{l=T#K+sLG13z=;A& zEY*H|1ASBSj6A^NwNOqf7hm8G$bRq%BIjUj2pC^_j>b^Iu)fG4?66pDYg)4*938j(CJgpT5RFn&z16al~5Zk z4_9~8{@*BK4IEm&Ut4Wiu8T>{nzVrsNs(1HDD&CkD%$^{08V*g7F=Xt1CJ_Ww(A>; zn4^ZyGr#1Jd%6RJ$cMF0(>x$LEzF75otQn|G8Zpet^j5Rr<{mK@LyiLS1l&-8pnS?354GB7KkwZr)uXW(oYE=>?WuQ>Jd zRx?v^s^2oSq^mPG{k;3x1>G(wPpH>j$J>YXQr!&zIJm6^vU+AX`)r~y!skWxG? zg)t$MvwR;9To7yI#fE&wo{A2jGj$$%&z33~gB%R3Rh#;0Fho7u>Q>7V{d1_^sZrXd zU0(sAk0z9rD5Wl-VmJ?ayda%rF)nS0P7b}P$2BSb)&9+MS`y6M?Q&z|6|L(QaL>jB zoR#zY${^Nzx~pQnl>x{DGMGzDA057evCGL#keI@^Sbnd0>PU;{!>unTXiK%T z%6X12g38RLboF@7f^yP=A7FJ6CG0I)58v7Sn-_2Jz}9k#Y_ci3Bp-&Se|E-rIF%iY zBgRDi=#=N7;&p*}m(FNW75Fv1qt=3#-bx-8W+i+1S5rrEYqpkD^XbPO;2?r#oeQx{ z_99H_;oZ`V689@YHE5@yb|cA2`gU?Z4rFO=PSStye=YYJ@iv_N8Jr@hNu72mtTa2} zl?f87pEtzmdm+m(w!EksF=7+_NYYJJjtmF&rB^g`jxc)(QNFNm zt)XKAH{nj!4=^}1ftOu;Dt5MhJfXpb<|zh#^@yDZ(RDJ->bq6nb*r{*kB?9KzRE~fp|b+DW?zby1e zM2r!Eu>-DlXhm0gd4y^duBY=3q`T1-9wA)`TyKQXYNQI~i6On8`g(D9grs8#PtoX4!_=~Utj-lfO68_5gm9K-k6+ zsM&aV{_NwAKJ1QGU;gUX&Nkbpj~|LGn@Wa&uTqK`(UR#}xHP5`*5+@yu!VWrVu{*9TH$D-(R)7vhodQ^QcR47?BZi zhTAMU@DKOfO%(3wY7O5A6js2AVs?`3Xy)}?Vx$tR%TtA?t+ULdWc|>fZV*RAtBa#V zb6C>|M|HrT3JDI>;|f6eD+QwAX4ciP1OrVWy~*CyS6`zf$U3B0};X~x?0tuuq~z68K3Zx`NoKEV`w%$ zTW}+j_ceAZeana-X+LoFRLhvny`&$L*#o>9dCU1^>>{5qUmiVx6DZhy-;YQE#FNVe zLQ`RVV~VEe*2_Y4IpFbzkcC(aTX&-7LlnGcmop)zq3uu?>$ObK5-r?7aV7Z%H`PFpq3 z8%sy10%Lrb&5K2hGhG4H8O><0n71iX5gk+{-3oKG`V=$SMH#adX_??=mPP)R( z^!&*W%vOWg6(x0->@`;D(jN*p@C+xgp%uBAR(sQvLmpc-d>hZnFsU|^!OxjpV=~6j z94mMP>rwmoFuPT4o=AYkQzDPdFMwgaZ}#AL#~hAsj)2J(aV+hXNSsE~lgg~R$-E5) z3h=uOyzX2^Yb74$)9}m{=3_=(_t8vJ@EnSTU23lyC6+q3DNu4Pe>>F%!Oe3BuJmm%3;G;X{3)*}ePH{$!Uq#eqh;o$g!~aN2 zB4?h**z#GE)IW{~ex#aZGr%1np*dKV`D>bErDInnE&(|10HOlXKQa!EYI}m`r%swH zxkeH0FpiUGQ#&7aggq@SZH`H|2&%f%_L5IRqlGf_*FI%T!n^`UTV^nK027EzF+gF1 z37%^_I)!pH=f_BOnxxPJ9Tw95a6jW?Oqy8mds?v4uro{+jYF`SkyfNpfU`sj)aK5u?VM?@`IOn>0P-j-k7a zjg4ZSnC#6~))2pO2P57OPC-dCx1JU{TnIY$_BPOZt)lcLGWBl|+$< z{Wk}af5hRDc4-5Ir#Z8VAED5~yCXjIs?(Cz-UUn{xPRvK;@S9AP`Sw&N{eKPp)3S^1|zPAAfw0*}&>Kx#JRj!yRdbh_Q}_*XMJi1~&~H9tasw4l>ah zG4w2Rl98;HMTuNf%uCXex$$~tY!3TzamDLn;zR9B zJ|k@1G8emsrCjz!lt)5ZF9+_pCUCUmRAEsCP3#fvp%B2Dlv{S!DNIy=9KnkcQC2j2 z87AeOOpg`5WQvHlWrb43Kv8FScEvm}-1RLI4>ut=jH3F|FG$)+Vwzu#yEY5XcDYAk zX|FD0JzK{MJ{O#-^9OwlJoOO_9&4|Tp96ox`_eu~U-MNB(Q{At zG?k7dD0n!XU;~lb_|5UM=|~PGmzj=B%0@dw@o#03tC+yrnv=civ&&PB^0h>GkK)uX0nZ{1{0XAR!Ecd`LnR?S8kNHi)+c(uI8oZ$C{_dwkR$oeWPO?FSVZCeeu90&1HZ zDSSL#1U)b=c9>P8M$D>=3NKV5x=lK4y*Ukb9an5Z7_~_d2<60<8Po;xve>BE10n^; z=?Bb)m^r%Mf>Pk9+Gal>>w5=@n5`V{b^I4ZB`7;)by(uv(LGDLOtq*jFiwF*fxZH) z(GZTdx$+wjMUJCOJ>P=iV(g-6YE4)t7@p&4!sEtCpa4X|l)-ofS1Ihnt*sZlt8x#* z93L3`!V!_#5cQzta=S61R@^gMJiVicy!y?0oTV&GDLxMkXgUxc5Ds~t*U?3Zm{X@5 z_VJdmhy)T!DNqi8ZXukRVB;>Pu}i?H5sWw4?y^`=rcu^n(t#;q6*c%)+-U#c1Fjm{ z_dspAiT;KxX52ZN32#v)xHYL0ap;=Y&SNFbG1VM;XejjCQRv!e>MdNMXk(;DN1R0E zQZ;kw;*urv8lOfsxG5zrn?&y=R{U}lEyO!Yd9fLq1jUqNk1H+>zhy2M=5Hf)x!(EY z)}6P$@r~=(Z}ynaEQZU?Fb;jY+6}wQ%gtiB*j!w0E-z1?o_1X~4BN}IvuPTp%`h$Z zUE5qVHn0iCVXNPx+yqB+Y;YND8))X^;lpB20RGqy138 zD{YDN$*?52`=FXa)kix~38#JgjDu<@#IYHxcoabtH07I%6IZ8bjp}8<9Qc5_rpO>{ znr?G>zTd+0Q^Q(uwp4&1o4K+mWdtoLM3K-e>Qm%_tt$aKIh9AXgxWO6zj#zH&JFCCQYC}WiYQ5kZ7CLaAM(g%TA+RjtDSv z#VNp>R!Mv$O+gp=h*q-FHyXY2L<{w&^CnE{PJ^wJgCG*pZIp4t=g12+O*p|L$>^rt zxFoC$+aNO*dA?$}1#|Rqx3zv-NTU+E%pJ~zP0yCMnPm$MG$t7u6p5sjVS{I5CV|2k zhsMJ;uJFtgzQx$z_ru6<0en!&pcb5QVHaXg@RJkY0Vq{q3{^HNj3-)Cxz^(Brx-~> zS@C!mrwGJA40MT@n6#^;72i>4+$vEkCyrg)1mTirQDW=v_+;6vwii!Tsd8Q;$$@l@ zvf}PsD7tOuKF7EtlbAd~F^4z63N^A$TZ4a$74dH9l90%3TtOY0Tyfje`K)%Gil=Nv zF}vZnv5we+F(p=Ic3?I~K91&w@m!S5u+$>jOv6wx-Zi6P=`KQQ&n6;=F>$Li{$4g$ zZd_d-^$$OK*si;Bgmby4nW2z(D{@i>ss!6%1nA>imU6_AXOzI7SY`zVh_R*AxxzFgsd)(G3+FY!bXjM%2VE?Wy1{zFVZcWp6o;%;q+?3 z4Mp}Iciv!y+I$wAa1g7ihl00;5WU@Ez6mwn%YCUS}2@74ZyvX2Hwo-~>suGC0IZC1zoZa={5 zo|V4#1WlH7B~V_{@LoHEl{)*T=iXR=4#sW@7vQ(V_cuad{$bBe8H+;>i0StfimNSw z-)CeP8_5VGxiz9*6GTV--%sO+0iDuq$T8zg36_lnJMq|YYt^iYhc^YyI=~PSRaTF> z^d{o6t?UTy_;kV&Mh!yqOmW~!7{$g=u@D5-C`W9%7O&2SHtOwt#);TKn+|6KpJbpT z(yEf&wr`Qd!9fZZQf!nVxOy5##IwUUrn)>Arzg}iIGk(4N8uLyafMnKUUJl=koa(fYMoPkG3m29~^L{OG8 zAc^pn!J_A$#1I!gMx<2mY3INR_gTz*TDr*&Z6>I4975i%Btml@fs$aXVGH9P`vI4$ zfN*_0689-Nwqb}Ofl1=UFv;zv`Q+~0naeoRE|9ZzTL%b5k$X)dqtzA6)DiByEOX)t zWLMGJxv&s;B%tI%smcm@j@`;B&y8l)4qGQRjM&4~hgZ}U30dKpaU&<9#FCe{1)XGj zw7&Vu8(;mEU%h_q>Q8?3?!(VNy?pj`hxFh5Znq<%M5Qio;{c2R{|wt5b>i4&SPuxg z<*@>fOxiw)yCCV22~L{FST&PeanG?epYU)+168~R&^z!)&3c_PG5`@`032%q9IYU3 zaFU_sPnEYvML@yCqD87s!&J2J96V&#Oj4|k$UE7yfo7t_yX69*o zh1ZQ4w(MpX2u-E(eRLHetWQiyTQALBLV0!pDoy_Csrnp$| z8kU=P&onkrwpe}ZNb|5r^X|)Qu9h@O_^<=Ck3Jy?9(La*R zpo{FubnZ^@8k6MkeuJF{_J}cwdw~^~;`sQ;Z%~KLj73Wc+~g|b*(`ahm+am~3wwev}K@2@yny~maaD4h1gGWYn3?DKIEX1Y0RvrifRQkr(EmSCqc)KqM{qc z2zTn7qXHGsrX#(GAx+<69EDd!bxJZAKdPSi6c_lUoMVwe$r`J-W#XQSU`@=q?Rbt( z2$G*4sVEws@>xI%5-K-V70rGeB&%Tr51|@D(BlGs?vebC`*uvG82qioF^H`K#hJv} zbS)MMD4D3p(GH=ekQEgN6O8%OK%ae1JQVwwhWON_P6pQ#WwQ*7G$e7+#bT|8Bu%d8 z&0-jE-MUV(cCteWkrky&2A_7GQ?8kcI@LKq`FZj6OfnOvZCXVCwp~9C)-mCdf)XNF zSqF+;o00IY&8u7Bf784Jg}SK;lsnbHWRJU!{f=Frw*`Z(iPdabZR_UnuA{SPy8Uvr zxiGg)rcytA!%HI?D3NE7emf z9{><|F1pK4f9zRk4cS=F3faRQrU`jXp$QuhyhQ%6G&2kV%uEjzMnZownoTOOp-Z%@ z(t;CZv0Xs4L&ox5EgOfNV;5122o9O#?-B;AhWz2g2yhiC&oguN{bnVm%H|pqZpCln z40khev})1GcYVJahwa&?KjZU2J()%iNWw8@FxK^^0~p3|-r=_QMLVdwIDScjM-AzuU1Gz!^IYBli-L9@fYG z$+g|ZnQnJfRvc1Hi^a-clTL-8Qi-1{h7u2ctT*ED7*A_zq-sXhPUR*VQgkD1C5b^F zk$3b6;V={ayyPT{%FcbO_~_DV;2M%xuf7*API^W&4In#!no+V3P2q8Xf@ax5$E0p} zoCb^-t+-PssofJp6cw*FJoH!$*Gj$vNr;SOQi58RjAalpKhec&FIj?G9> z^^`V8BQUvU;piLp`w^2s#5uz6n_m)@umd?lNfUl!0)_fZviZg7ln};~E&}&tNtm%{ z%^g>vcBXkYgpw&HOsb#NsqlW7tnfQDv3qx7essYgIDZ3YKPtupYU-4qe&_q{^D)>yXY{i^JB{KGLhKK)MZdE=}xl!1DfMSUB zlatP5Uep%*71d9+fEH<1u0dKgF51}m7!HchuA&Gmk_USgMpf8|h{&)I!H&#E7bu<; zE?m$w-QaQ6^$jOz_;YR(7{8Ii?`_}VwV`mJx>`{?7p`1gPC_@j@;acp}| zt}@SPT9kmg*j+CLK7hqNy4s`paBEJie0f+lwijg*= zo>S>+ctD7oR?<+J84&&;5%E9)A}N|sN`;m<8d$yRfCmHfC7|az!qsz`$|29rMEv0M zHKa2T1(Uab5xh~|j$=y=v08u85JYj{zG;JO&7gpT0DbU?QydK-2{wV`_b?@s!&{Dh zZPI9|zRDONni_`5rh%7}?@ClNRy}U$Lr6kFQOGG54i8*e=gW+d^h;uWD6jU(ZjUX1Ox+exg5qZYA-pnB6%s^ z)FuF9%^f_c@tU5@;;Uh+8HYn7OJKs-3Mhx1V0Lc9c6JYf>F`^sW!5W9dI!8R6{A*{ zunxsFg`SR+h+!we7taHLo>tk6JI^q5bEpiHOD^~$W&+aWNJ0;cd6gVaY={*oW~U;3 z%)-X_kC*8zC%v9F5kZr8EW*B=nInehdptC}1m<{HgQcu=`y#OYw(o%GhpZm0 zujfQ^93(5}Iv4byQMiC1T5OP%o#ZbWU-(DC!5Atj4Nh#4@o&ikoqFr)J;^G#_h11 zwwvWN?8j;6L9UBc<9O`JR5V9F9is-8bVAEf-r8y_j( zM}b~EuwCtud$3q8d%|%%Zbk1D;U0!j!{DJa=Lc*zG?ZCP!(bFl+cyD`{f=D3C6geh z1$RU`*q7mnhJWY~xlYLZnR`;s38$ivX*aMl6$+zl$x=5t+Jvn(86qJj$Zn0$IQJ^- z{)ELT37Piji+C!J1XwgOwhuQCGBH5;<#BJ6A>RBp3D3yz}wPF=YL8^NL zvGnng0djlnT4D=Ab0LN~94HmJ3q)_=#|_8dGbE8fkINB$>CRzCLHLgwo-$g;&lziBRnB!Q8O+Ok*B%6jkNO za-7Rr*e#1B_w*RrY6v46B5xCd0dO7|h)^9u>%{WibtsMO|3}%NiQsA;3qE*eycQ>L z)Xf!-avx`yyuG#FmZ1L7O+%&@97S6EEjBjyNc!hz(m~S=-UP}7?2{Z1GFz+jj|UW; zELX9gYDS?xq)r^cxHdAB>#`7dc(s{!X!2orwCu7{X?Pi-_0z#5DuIMXD)YsU)YGXO z13MKy`eIX#`$2IJnx3PN;Rpke6NMIHrkPMYjV%R1&GD5ledCwE@a3=k;7|YbgYSQD z*lsWo=+|_J0i{Aw%KlY7MJ7Y&>PQ`*nBkc`nIHq+Hn~@Oynzjyv+lS-E}xr1ClIS$ zU|{AHXCa`vUXtXCk)ns9h9`RX^>ntfN8=?;ze>P?UY@anAcILpZ)heteG+ai4Zlh$ z4RobEijRmn!|cIj>&a=ROSUlOK}mB|U$k6y`_YUtHukD?Cs53)^9VNsmr#srY@nrI zCuLLfYl;CaB$BKG9|1g3re^TBY8EeGkIn};NFfzS?wmcRHDJ^}z1{f*yOPdJDHA(k{b~i%0 z=(*fXJ4-O^M(5iCxIEU{&=#o@1s{=PKC*W$GnD~>1zc>0BH9n=8~UP6Zn{!^}r`lkg56Kt=P@dzZRU(av zYk-Bd;dpVC_xo{^X{W~-Lh-z4NXaTMcGWBzB}B>fhBy1^_(SJaoo_Q^NbP7d|C`}ElI$tJ}#EJShj2hInG2)CF*5*tDpgzmT4@e zx#Bn&e3#mL2||F{(+HNat4Uadr7Qn256O%To4Z=K1x>wjrk*6f4fy*s* zR9@~oa1t{2743Uwf7z)Gm{?ej0;|x`mD3=9V0UPd#oNUNV{~S*U&3K1_VO^>FmtF; zVD(}#4*TPt4;FRndMcJfgYQ7)ug%OI;G6|NEy0_ToQ$oz2BH-OfiBMfcssFhJXfPC zXq{W?7gIy(fWmf8d6lLm+Bf`BcsD7d;)M{1A>Ss4qZQIhv6!(qWIG_)Ok_KNg7UZ2kM&c%Juy?3>W9NUl*!x zhaT4%Cc2nF8UDBzp*|U}fue)82Z=Ys(1sW~R(MV>g5v}o=tZw1Df@inhU{tLn~xlm z70fcP@0*!W9yQC0bsr*d7Gma0XvwPfZD@b}^p6ctxJv{a#?;wvNp3G~VODQi z54E)JsRIer$(J;RYqhZgqTy4VrDFjNd1hsk&_)p6`EFeSo7}8 zGR_MnmCFa!1U{|b+y-;#%o^CAy*85A#nXTc#|%|`u{u6NmV&9j8ClF!QfH)zD2b7!&YzZyeRWMu z2i20dix?ESe41{({QB2^<=3y>xbdBT|L;Ek$&cBwvX5a~TA&J)%q$6J4seY0m5gFB zOGW%?GA%HaV?Xw&8q0XjV~eSZ5fEM5Ab-@0WOXG-yjUOB7E{+uKA%g}R75Y=9|VV@H(7 zRh76yB1dDCwoA-`V0|&84osx?zCJoz(|TrB2#jN-+!BlCfXk$+-t!`Dg9PHeZ?mBV z7^zPPFoFrKMxFTVn3Ha5BS-P~M ztg`vm{l~(fUs6VS{D#!k3z+bI1~5U^gBh#R*w1LS2njxtcuVJlRrs}~cY8eet}DH< z`e6b4TJivIa)x@10$4FV_wO;;$=;PnC4Kp1)~W*JEdyD=zBbxz<`^mk{}8TiA;z!- zJ14W~wDz!(kq`|Xuk@T6n#P=jYu_s!u+C_VIBLGgrQB_HeO-@GMI9=Be{iK0z{RcG)7z*?jKhJku1Uaztt#Y6_UU z9=r`5aP|X6ho%nuJH*6CziwBgxu9@Opv-6kAvuUWQ;ri}5;EO<=Lya}U^#xs`k8Hq z$C`4p_F2gelI4B)*LH-g-7aL=Bqw=VPmf0t?Q5-=&e-PFOg0Ii23-T^&58P zQG9gVwB4{hmm1N``e>Q#ydH;XPw5Y;R$nEjy?TJEVWW*C?I;iCsVXIRmA0{K9RQ)J zuNq_eqgvGN_Rp77Vw|}IvLSm&{uX@dnJ}dy`7Z|rm*?&F6_{f~)IrP%6s8Bdl9!gF zhFxBubY)s<-emWmwr`j1a{KIDDX)&D)1=V@-u93dy7D*9eEecf?P9q!5WEE9QO~T$+#=6hZ&ORa{zxls%p!dV>tl*`&Rw z$xTvA6oakK=G;Cj1$Bz+)*4jt6Uf6d);!r2=T+RDT;C7F?%AnO=}J6H3aNh=WtI$3 zDnZuz4jI-96OyjPmy*F*I_hQcqLgoDOq)iprp{MhRD%?wB9dSzBNWLVlL~heMwL5az=9TQ zz7(4O2!#lEMhYm2ZH`c-vw6$@5hOMaQ3!SrhG1D%jV!O1NX3r+Q3n;&M)yQ5NFp!u z`195BG1Pi-$Iu53vZuzAYo{E>1Ioa*1cmHKPY89sn43A=o39`Es_Rpm(QZGF5ikko zG30r0kPz<%DxLreR$8*FiJVuM3%{|BK^hL0#K#0HxsDh!~bD2aER=LrKd`{E#sh*?TfQxqv z?$w~O0CMT&CFGbfv54J`D7H=Yj++y&jbu#eDD9el_2QdfeC@5bu3Wp}Hi2|jLkJAZ zjM=Tm!b-H6trO(hAbz695GZ!W{WSJHJZ@k5!dt)amwtVBdG^Qu_V+f=o zx#PXb*`^JAs{I;by4rrhpWjtPGBtq9a3$H|QQ--JCh?BY-kK)h9oc6Z^R9f->kioR zheBjFpD}}>oP-Y!=0|jOaVebwP}YIUzWbXSt3YwBi8gPx&h-fcB-{$v8v?669!ICkzp#dt2DRs0ik8%kugK! zajeZ$h!1~|1_TBwtMo(UvF|NlgY_Dwo}2Sf@kLeFx6v>|7m%~^z?U8oOZAFLjT$1= zX<={L3e;$4IcZc!>gOV96)I3%|K%4;Bks>s5U9RP>gxIQ%p;p&ScQ>CY8rK>woQXg zzT~oKE%Z_O8*Y`1g-hijs)kK^t!MYDo)-O;H74PgmpoWyV+wdel?BVbcuQ3WlYI01 zlYv+K9|ZK6lpU;>>2NdQA^S_F)Fq&i>56&8wY}D90oI@{MmS$yDIs@P`D+M)tK1VF zQxqYpJG!k(OPG-(R<+Ipm-tT5Fw&yru)~r#&9pqFbm{vie8g3y2MfG(iJ>W2Ku|8G zj#?pd0PxyovZe ziqz^6AP1qW54Em1jkOTO2ZsnHX>8?u<)*6XI7IRxaDaEpEKSQMkTGbg7=(M`L#UYI ze^!TP?BsFwR6=ni8ZeRz>DMRs$aPGpjM2gt?;%)TV?P;>DQWcW3eR|uY$P(x(~Gpr zWxvL^0Gn&37e#-}PpiYs>O3Mu#%q0KnkH1dr&?J26XKuB8ZFQ+&{t(v2eajOPzqqM zxI^TXUN>BXDeug;b_tgRJbwxC1zhmhNZhy4Xq0@ai4pK-V6^T;-fY^%w^y$fMAMe& z&V3*XrK-=;O_l5ntE{^wuC|UM-(o#T8FG>C>}w|}ytBi6WO>x&;>0yVQFetnM4{ue zET?CUe7O6WqHr+D#%sw^QG;!bi;Pj&k&{c#pn|ZIsslnC;lbe(MJivF3$uAeDkk`2 zUA=w#t#5v->$>x&rQ?$eKjT7#pQWB0+J@(B3h=z+K56YJ93N@=H z*8B@a1SLS&dkeOEYGK%c;{b$N7XzfUt8=3wgs!z@#8W_tOY2tV^GXO51gV<{rjv?M z&&%a-XE#67-SsS_)bxc?O_mckGqhBi-e%d`WC-BtcG>`E6Y^BiA0}Q}_Qte+NLSzy zFb2B469wICxU_0{e>vgsx7Gr}Xhe}lS|G9`V7t}!y?Z(CZmyb$e`v3f>KWdCJZf5m z5gMg;@oj9~;HEf(WXcdJp)#w605Km{ukLU-S)~Rqv)-pJv*bqQ-=q_kvr_e5G**%! ziVrKC*qxFBYT9dTM+DrOJuv^zfTj6%>3IUb8;dsn&vT^k#x#UAXUFfLl%=Tsx+;{&TuM??Bpyf4b_8j_%2WVw9sL> z$o2+#gnS)rl?oG~D>7e9Ge;V8`pB6l^{Rbx4XIPnmf9U1b^U60aVB*@$kKG{6XKOK zRZG#JcD&0KrJx{^M8B}BNPeXKCMt)Z+~M3s9ncBtajA2)dgj?vz6w5qxf<7N7^IgA zdQ(2xsSllIoiin37!S810!f;W$y$f?syXQdzdNYdANKmm51x%9uiV zrUnc=^Rc-hao;@ALWCW)lZM$Y%y!9CQm6P7=7~8f!e2r9Zq?BaU(`BeHLRX5vRhLF z?S`y+kVm#14HM!f%Z(XB29#wUGO5(^L1FAki4OwsSre`BHcQDpg#=htqw|LJhm&ePLaWPwc_%DfB_`lj;`;*7i{Yv zX+%j3E%XPsJdqX#WOTZDkbt!%<0bX|&`mSfF|K+NJY(F07Dc0M{voWO0x*|_p?g&! z684&^sj>e*(Oj+{T|qM*%Bsh|G{+Ljw?(hhz;{r(_Sny3E0TwJCT%(A(`zXb-Ncq~ zbhQGj-eT=+Tv>)ub*&PPSUGeOMcb~WWKXg}YyFMf z-S{wQ295Y6ZK=g!WtYM7PCGJIz0|Utr>MBbDWpBcF~>w21U=b3)SHX^c}99kc>d~p z;2?#8mpFjCS~WbI{7%Zyz>4EuByR$iF-nxC8q}HqTJwqSqF`ryMI&~|h3UK1_3L-v z{L-_>Pd@wUPd4WlUElAUW_`5k*GFx)TAv(WKf2v2fvj0xTyCb_u-k37mm6j@OuOy2 z1&)9vdVGAW(Ph70p+Z}&Zrr$aeD&sP-9Ng2@1r08@bdJ@vT1ktJ8}{fiRj~)g5RnT zd?JV!qD_&7jv;JYPbEjI<_vThbyl=m*%<%GID@g5@bHsCk)rK|Sa#Dy4~Wd5P|e1Y z*)EeaA&4&(0toIEed6_L73&zv09=F!sqhA5uxS#hjOgetSPF8IEEHXc zFmX~rDeAU~pn0>l3Q3J0@kQ;|%l(AI6bCVjB{@K~JR?*eKq}OY`<;JN9#D4JSg zNlFT_!92d~utU1`G(i_Fxdgsj&+5}SFPDWKn@eyNoh`o#KUR#Q zkAF&-1w>Ipkw{1_*{2RRaEx;_@k~w`2RWJ9FC^rEOq}%uxJM~DTiRlRRjkL@4 zqex#4k6oM>4AwG@K)9920W9DLv`^x36_TZT)$t;RIJNI(<{+Do1611tnwfmyS*==p zS5|!Pb6?c{$YB66id;0UP!^pEe(*Vfb($078dwD-KNRgB-DI<3R2Z;#0bnj8^C1e+r)PatYr`WG0zg z%~Js0JUNIi8eC3q1*I+G46(T4ftLLc^>-8NYTm8%7R%e@VoZe6hY&H_ps|$~5D-2Sp12#594Rcr-XlFEc2^*C4PhwTUK8eEo<83yA@!t5lJ zW`8mEOLB7dP9K4VidGWZNd$5YLT0s5^}yR`>8OV7#JYn$GJnoKdYw-)2<5r?{stLnttB2qAtLu5{ww?4z2QhG>m zAoMDTvk2U<3#;=^>z<{m<9cvewd&~{FNZfH03o)yA_=e4)rN2!{7RgYGxcGUE2m}^ z*-mRWmqPJt;fsVURt7;jm(lq6IVzx8A<4_ zxy!2av_36l0o&b*%c!B83-Y3=YGCPY+B8I-&GBC%BY*@2olTV%SSIeo&$!7mB1Laq z;x8+r-LL}w<0*q}9gib{Y+4s6?nI;p9Fbb6G#4XrQ7L7hm2oZd`+~y{=NAv&%TH7> zN_>4-zNzN$RS_@O_@QlI)dGQEz^z2}04g)|C)hhhju+&@pa-@R^7y3x3WfIm}!SIrO2Mg7Xkz8rdO< zA!7EmIL{RMaXK>5O}6$EPdr6YZkD6mRWp6S=a4#vRRfs>aPgLEj}v8h+i}>44ctd9 zZYh$VcqW5RiAND9JeYtQP{XFvR5fal5VC+w<#rh8t&nAe!-7q_P2bd>Ay5r?fk#(B zYckb`RWX(epBfGy`7LFJJ?wT!8E@^SZzPr0jm_A0T|c0sV*Y4{3SA`$%OpdE|YLo{T@GPoCNqu4i*|D_~^EkM^v_KaeaUZ zW!2JefWfKtvpAmsC_@(1lBR^`3Uh;O(Ty8W)m*SDPXwf(eSzh+42p0n-8QV0M3=~P zl=ZQl^P`Ry$H(G3H(8Qd*foT%tBz|+YM?d&Ry7KZ)+eBCtCC>2gUMC(AjH~1Txn|Q z#FFAhr=M;mjirke4&T<`MBLEW0W#S`7lNQQ*KiGPRn*vcyIw1tLeENqhPZ{(f$fXu z8NGxDnss46kK#z)?haa?(OjhfJ$w zD4Gd#7$b3`q=a>PZhK#WHers`#wjAD9ItCN&)C<);y3(*jl2;OlF; z?fmQF$Z3{D*j`R`7^%o^v&y)MNmyB+8_#x}mw*!eR{B$SO*TrD zw!$1ki?fV2E1{&?Bljl4TrJ`iz8=1`r68OHkbGq#mO~1OAA$OnheebFWuh@0MI2s56CfG7eTDzi9rH~{Wm<} z(5zfRETQlDK++MpY?m!^4$-dL@lodAR&AIas)o_Yf{d+FI$8}U!+6Z1V*BP%EmsU3 z|5XJ@AIb@Jtl&)Oh|ZMeSLMazNow#Jg%pauPCsZ)t~yP4xL@veqyyXGx@eCM60#H@ zodyorxENO8NZ@=I;05aFPuZ+Rhoa-iLSS7`*(PR!ISp7XCWF#y&iR4)I?gI8*C4%G z*{ym@;UX7}K4`6{sBq`@9Ls6x0*E;))lTMlny+Dk3MfAJ@SK#SJxz~l5LbRG3_&H+ z*atvFk7CiwArHHfX|f)7Yj>i*gNwhhS@iPZa)={~9|e9n1%dEDKB4w?xHQew1pR}A z5YEuC322oRgDR3}cju)MTC3TwG4m#2kagDf&)CL=q+I`r{KssiU+VhTT@} z@3=#PY}<4r;S2^T((%1nc72Bc9TmDU|C~?}#JEgbd&)kmWF#{#GN)??lRH#4QP*Kk zYh;vBl43NMW0a&Dy@frPePXD_^zlc!95vn=8M@r&TX!UT@Plb?}rxeLoH8w)Ik`VFR25 zqB!mt)0y^*UuxRZ2!hdlG6Z1v=!%P5q*!$%0ck!cK>2d~yjzQwbqgx@CMqvi*i>(Z?x_qe>w!+!uA&xWFN1 z?%l~r2yhXHHR(7qOfUKi%&zgxNpu+oQGGQ#S7Y0Bh?E)wXQ;oR5C;aL!*(Ypqm*%k zfxFdmBx=B&O4#}|?z^_1THsz%EH3v8K=q(cbo9rO%$t&ZULU<7AAwBgn-;GCHpZ5e zZ0DRQU#BfwPGy>56b)S`<~d}m@L9G`5P=MPN~)YxYp062$l0E#VJmMJ;IF8Y*VPdo zGM_FEDUqKa**${$bas0cs_4aE5&jV70#cL(2F41c}c2I<895WC4F(IHxKbxvAA^lFYW0um z4pU;{9yQzKh!<;$vEb|MgFNihVO21X%|!PaIxsL;)L4`~wnE2lA9H%v4k&MU3z!`2 zu1m)solre}^_d6YwF3r@se|NXJaGz%(%{tgQNbA4$yj{gtF_-%Be{T4J=-po@42gD znJcxE1+2bo2Ke$WjwMU=jNEBP7Nq)6oY=`d%h|5E5%@QG?wa|y*bxqTs+{J?U3HlU!}&tW(Sy8O6Z z=oi{C!lEfR6~+?9TEyQz?I;^QGQtr1CkW2(YgUs-f8Lku>FdogXpilCe0WeYZ5~R7 zz!n+g6XHn_%}nM7C)Z)Ref})=6}skJAtJ_<`MD}YA2a346jp)_s}gA@nl^_KVY|im z7VpY!-XJR<^_apIwK$#|s)qflvgAk~sL7GUX5J)9D(2(Qgq{%hB5t?0Oxx^RR31Y5 z@yKiYlH-w;O#p-8EZt*t26h3h@3b+(d272{3?%0&0afpQwCehP+?;6IECv7@m z0V44x@XW;FRTdd(Gt@ANyTA2&dXX}E_U#tq#ZrXKQUm0g0}^jmU2r|Xek1u&$x_bq zM2>{|6@oApgG5ytrE6v5V2=HisWmnY0mh^@Ti?glsa9U|46lPXxzJWZ3Jxj}aJ)A5@j@F>H`5~yVjLr%+0I&L4Rv&g~Yn_7{eA*VP2Ky%Uzy&Wi~<7XcP@~4wjBUHch7Tod02K0sWr4Sf7TPCRxvkVnSt?D3g+7i*Fp@Uqsw&E@jqB*{CFYdc@e* z@Ws2nzy9Lg7hikr$1-!1eV^Qj2O@9E!2i;R)L2)E_sc!VKiu(cMNB9=%AC#Hl~Qh$fnT&e63|J&!j=qQ?lPSZdWNe4rOY9U?_%b$?6$<=EaWJox|yALDp z=uLpP$9OZWR2}&I66$!nRPRB$}*%hQOO=!(7{@nzaW?j(ju( zfk|yl`X>Zdjvf;sY5^gY+(uX@gcPaKCaAUi>)48cKIJ}yiKOJYuu;(l9t&*Qwom(U zX!_oL@M7fC;$)8)4=8WFX}KwpM$DClcP_P63<0Q-@J0coRnATH3)i8`w%kuCcD48p z`X5pXiyDT`LG>9`0+=Z!X31P_iOF59rJ0AV5mAbTA$uk?J3JU$M+0?l<#YK-`V+7e`J zQr_nyTVE5qyF`8p6<7J9|vQcm8aY`ggJaYVp_1J__| z!Bs3N^sr53wP_2}{`d&$$lb*`NM4*3>J&lkAP$NrXC=;7mbgyOa1vAG*;_UV7^<2w z0!}cI=cl2_s8G@4>w#CW9oNzv8d){#Szow+GMtj;%Oz*!jCkYl!gbH3A9CZGM%TN# z*iZS9YSaA%-H{oF6oz8;$fCG{J{oXl?Jhl?CTLAsh`JKF!TG}K0re!$jfsj|-TQ?3 zn!c$27lr~!SVh4wn6!#9dnayP?Et64?YRiFgh@j!E?_;nbg&qk(I0YZ915HOf-LYML}O{5D;zVGx)Q z4VnOi7TpT?L<|j|E&yGJz~+ivH9h&ow%8ZusI4EonwGM$Vm7(n^^5RJ4K-5c9w^Ub z`GWgca_F|FWV5(gr-|Vhb+h>HAi40-9TDEHI|!>YsyrJ=4Ma@VrBRw2KNzqp6=Njs z+56cf7DsjZ8)URDpjoUq8#2j5pYK~04d2mBHQDcDVWW<6apB%Lv_9rnK*FaZMrzzL z{*Yb1cV)T!3FSxKYa0?nX{M-QlaMb-XnN{ZWwu8VKuBBO`TRu4LmZ?o%Trx@_&njG zJckIUxH2;~QA++&T4}mXp6lD#3oyJk>T22z+K4I>xSWp#Rc3sB{FW~H%#qQVB$j{+ z4J^dvVx=-VaI!zYxqwmv`f;N|PW4kEW#Os0NK)9FJUI8me#AlRqEom4{{L>f<@B!=S%t0k z9-0MijFtLTh>VhfSc>CbgHNFXyKCG1a@b->8&W+K83=`F+udf+@PUU3$y1yJ%*r+K zop>iD;S-MLMJJXgR5$~KK3E#K%w$SPC94Y7#^~Gyu)x5WK#Ua^kGdN(r57VEEZ-G! zaFyg#bx%V_1PDhDeZc`n5?lFN;2AiV7EHK)&g#Q{2 z2b{5;mpg_gX3SZ2nPTH&NwpN|n<*>*T(Y+3fOoEYWg|FtCxuI43bvWW?d*;(7OR@-1l`{Mms#95lVDJnzq2gZBb$ybez zTx>W45<(Da3=k_9m#)*)!#MF5fEqe;eRTO8n2XN6#Eq|qRwbH7#(+HOIKLBB_&L@C z8#}Qs)vN2-14}4407cWW?MjBD+5^)$EdX~|mtCDC&M$sPIjRWaBaK}p#VplEWiN+# z(?BA)wv!sSSRSl$1&s}5vmdu4ZK<}?o&bV6Hvw9&aw;6^xylNHt&SI96G-D6H{mj# zk>WyhcbydJ+q}emCCOWwc?lZV+nrn0mR0v^^s2y99HYy`M9=UqUEp!KaV*4Y5KjXO zS+Q~wk6m*`{H0$Qm0c0Y|lL6*fV#7VG)=eI-xMdPKsN*M9Mt^LTXBj(a zI_DMP9(e|B<>F@&Mkw8|E4uCaTMN&TI|jeGJvnT{Kc<$<6F&lZHf!`mOYJ}s zOO}J#<^le$R)n|7iV{=4Jc-ry<(7{TzULiAGR>oKCJ^mA!nG9w$%Sv|G&K4K3io;g zF}BD!z`rT@x>>Z{a(%Q|_1$_sEf&MYrr8er?FNY#YH`%xmaSpGYFF#=;yf{&nKXOh z#P?+e^2OmX&#PG1VNZD?M>i~?R=g?_|E5Ki9@K+fww#7DY0B6EQ?PGy$ zsbw@g<^!=lA*sg}jZ?uX!F|8o^2Hj@>v-Yjyn*$rmeFE@2jl)HX? z{lz<1u3r1>gP$&T+ucq?Vv*iS`!g?^krp}$QQzzFmIDg3$Tn8fuv(PAglD1z$E+1d zmJS|63AWXjn>T7pF}Q2)=nFtjfP9M533|?7>p0&yPDd{O6qE_5&yoTu=EMsv%OFB} zBu8s1V}L#iafK=1L*k2wJqjS3msY;_N+uRJB#L8v`*tO@ndlu6bYZ|Qnnt)tI=&jf zj;OMy=Q)*Jd410+a=_VHPp+Phc152;W)9l?bhxkz>yi^0pX?P$SQ)?0C^lz7j3g#1ec$ME26mc8H=8X4ej z$*7z4T&J`PcN98Dc}#okvBx|=ffc@9T@RcQ)g8^4Lxz%b5uP>KwA(sD`I~@>7>25m zu)$M>(ja_CK8gVzC4;g!h$0W(Tz1-QnVMcsJAat7fGWRYt$*n35IkVi5udQ-NGlj z!s^(vOHQPcG;pasOig4CO`*++tK@Yy723z7E6P&k&dd=WDUK#om+o!HdONX0GYyPZ zv_y(N2TMceB913@Ta=i?nz*JImF{5=X!0X;K02*EKqE0w-8MyKco6I-p3kt20l9uk zx9aE{=?F6D(=^en3(v~pYpJn;d4Xb%NvE7E?D@5KVcMJ~dedV&Pf|#9;nS)?qx|9Q zC?yl$x%-@*wh!9;@Vfa|P1j*P4uUvod=_7WVp$kUc#ip!7q4M`swrFmskP>EU#q_$ zBwcn}in`Wx;&rt~G8=P0?(2i?&Dm=HKf~0a(eYlTn@Q{-$(luC_J`3CV}*yuaft}z z-^Z*l=c4q6x*Z%ENTtg!64oDn{`l(E%iV52Ktln0AS*`9`II$q6b^2`0}R-|li$-R zdNp}2mM{x)AM1%>BW=V~Pi~dcoLCYcFf+#UEt z%~B3}T@Oocv)#M|W{cM4?!r>4+}k=?ecy5Fs{uIBT~u&lVbwMRw+WCy4Km?FM?iRt z!J4*RuKQ)b1`BsVIqNue1L8yWTlDiRyNw}PXMhK&Z~E16an78JoJ8R}I)hG=Kqp;E zk7H(XS**C*faXgbfEcY+sstESR;wvu3G*v2yrAv5DVQIK#d- zb7XR1D;hNOei+6{)}d&;EvKUn8*5s~h&3#h1y{D{_UMYa_v|SsxKPH zrdy+b7`CpPczt*)Wu4(7hMoW}EOOlC(>imiyl#oMm;H~SNp;pTBJeAv(lW{{5Jn@# z9J;34vKR`$p&zp{$DThCi3o{G$idwDSGf?WR8&>oay&VX=q@XQR&~|rX-nj(R6u!s z5ue-u1Il+-JGr(I7hd*WCWk~RBzkf2vfS7O!FAksK8wKxU1w=&3UK3|qC81+uY^y~ zXW7I-L1=iLBr#MIStq49ho%*ndar#{l}$}`Eg`AAhqzX1cL9Jk+cg&bb{zzjEP5L!4HX4#yQ40p_GGZIGHioh*#Dv2B&P< zsWX&Ad!xq=#ncGT=01h;X^S9I*)sLO?SMK|tWq%lmoTPrLuNN~C<2gz3AIsK4e^UE zo7IYyE5`ELSWCvWXgl$iNdoj6;q|%>ft|4Sv^xz4!>s%~owlDI@1pJ^+P z(<(ljRkv*WakqmyLzZANcXI2<2@f9u&*xna?VGNL(aEqQbJhlD_`z{ncJLZlj-y&K zClA20wWZ4`Y=aYZ8R8YwDBGSggtUSol;SYLrN`msz;fB@g5=b%q`a|CT}G_}QE-Ad zI4qzB={!9aZ5Vc1U+gk^1$HWBmM}k^O_g~WaWHf^hLGB2w_35ur!%f5C^}4=rd#z3 zv;jHEGnIv<8K(OLa0MGiVuM#BHgEtq%6J>$9cI{ahxQO-xo>;kapQC5E28*y>JVOP zcCJ;@Bw2*9iqqB#B!Z?MATrcp<`RVV^Cr_Ohz+$z%MfKgY=i?nmvdQVhJ}3ywQJL$ z&=s`y0)1>8=p6VdG0NL)CBC~GNi~~90Ch8!+w7D%NnI40sm9(udGyp7dY%<|d0;Vlx zx)^s>e&l$hILLWjMX)l@GdVIU6{s>$mbMwk1~;@ptX?!4Jb0q5%}gI_bGWc;(dW{%xL%~>*&g^64#%Ux z*V%R~0$ANdi{LE6lC;=0EA?;`xlqSfuU%el_q#}1C?2t5S_%+d95wTDqjJ-iL;_90 zT;m*4f2t#6L>wvfsRS@@_wG;13o@|FZ`jgH1%Toy5O?R>$$6>$Qnc@h7Od@_fS>a-n zxpkySg^zeY3?vg0bJ?t8Fem+9K7uz5`@L^hl#c zLMYOHrKvFl6@p~DIC?=&Lm@?&B51V6{c;A1^?EK<4OaVU0l-`%TFs~n1hwvgfN>=S zYj|i%54S2IQ8QsC2};`jTm3xooX|mQ8F~FtFR(aZ(ArellncWBg3;*Yq|F*EMdG}Zqg^~J7Y>e7YFNvDq@(v)@|Zlt;CR&(oKjfGmLN-oxw!O&4({pW zx#0dH)VV$pIRfXCp2p{XUNw(bEggIPm)xS%qSFpt?YBw?dEbR^of{-Ei?AG;8L6?? zpm2|wTepDSK)*o2N^4@+PcxlwzlUiY-0Y#>R&XE630-F`-;P{~?Ya3U9*Oa3vpYs@ z#0D!-w z!MGz&dVr=yT5~UErda8LXQk$BJgYjB1j=iGcG^mcc)yGO!)<}|#bAe`my!>grgx6f zoS}m{;Zo??BCNC)Dx)%e<6VqtqKBOs>Ts(s_|cOkcaahHIZ$?f5LNndtx3$UUpzRW z`2*6IQBUmO(^f#jw(LA&CdLwHuv5C^H*R;dnJ~nwXhgH)PXY3Y0*n^G(c49bPeBn& zA%V*Ozp~DCNpj>$&Hy5StnMBTm&<>8{}U4?gp)I z+mFBheQL{p{;&VJI747w-@`wtEDGi(N|RdOrA~p@gFVDqXX8vPr2_Wx`PWSw<9P%a zjZ3CKSnszWPU1>)P?&*RHc%)L{3Ob%kQ$4lHp{c@J?M~fEX0Kh0X)3+u&scdvXqNu zp=q!eiaY^IwnncAk?zyL6#P*bmzNb*o!zVjK#F-Bw~UiW>Nuu!X!=Wbc)heZ1^ABG^nrB+!}onv^i#% zW>{o^pG33(e&u|!bUPw@Rg)XSrlV=_Jzu*cd%`4lnY}h8ZoG~J%#sK}xTaTQSP$<0 z9lxqvAzkp(0W{WC72{F}7gI5%a@_uFqcd`Y6+LK>y(vL=H6*R-&7d_va-C> z4%edaA0)To3j+=&9t~jJ9}rrMRU!VDA0v}g2?;6gxP!i{I}gzzl;nKVvL|6%Bbq0l zq3DCL)*l#M6*+(j8G-uq)R-H~3w)oONzHIn9d#8Vg9T_z0BSIi0EVxvT50y(OGl{@ z4N_{tgLF`g>^KG# zdy)qc(zH!d(=M}o`Ezd`gj41KPtqWA$9jkAUF*HaNSJTw``{FxbXXCF_*KpFGub_$ zq6oB(m8zI1gwf!~_66Bv_(Zk;gr^$Eu^@+ovXE9zr_*`<56-d<-n?%40ktcHud}!`TT^D2KQ>TV>ELlglwdi;fkfE7)PpPDcClrDMwT zSEH(+bv2AAc!IrvT6gg9`9};Ek)Y?Q3^nVxgK?oO@i>H}Y!g*W$J04;bZ3tiIVbzW z(mqxx-OO|=$_)m6dSzj6mx2%CvzpMsQ=Rk=jBsYW9q*NDh;OiDfkHgA6+8WxQ5PD5~_GyMAadabY zjY#!0kNwS}jzzYIQTmmGB!cCc-SjJJL4}!44V1b#_PIiIMV&hyd2aMw-XDE#oRe~c zzgQ4whz7L`07I9Ru(Tvi6eJlRdoqZlLVy|KEN8z=kQ)h_^1dI;_^iAL;fPSEX}<5e zA%;MkbQXq=zBsE6h?GlJHn#<5m$MSPC{K$EUnw2|gJV~g7B(oa_E{AHz8rbI$PE$y z#(@{Qe`V1YRN+s-Sj90PAxBZ}@maW?*ItQjCU4S^bY_q9ZV8(N^` zDDtq6wI%j@)#sEinjE%bCm)aKLCvA+VN6PU?4mB20+${G_2SiU2U2@`(}s3AxGiI< zT4WFkkJ9O=$Ec40yUIEsKgfv`2Q{ssgMo%w3E1*a_d*qi%XwG$kl9HZyB$Lhx`S?e zxFwtx3=`bd`8GwSD;PEjH4xBE5OrYO2y^!r^RvlJ)*_v<$#Be=slZ6A3y|R-P$`&| zCI^`MHiiRgwA1B~hhU?*vAd4Iq>Kv4v|*7A(%)d*6n$gNz{7z30#wr^7RbXCcMQDB zfH;$9rVv`+z3hQ}|Lxk6V0SN2KaJ&rTy(*pFwhRfF&fsDaBFLnMIB9o0^4ACU=F>H ze8`{)K_)q2VTQ-ZdZc)AvL{NT%y(;xqcmr;C)q6JkZTU!V!4-Vxu(|p_U-%YdHnp( z|GnV!;)lz!!ed%i8ZAOSk|yS97%2(3!wsU4sq9?=@8_XHe8i&p!P74}4ukuisRE;@ z0&C}S2(^&(4Yv^v&8vxpu9sARz1FhmLY%EMU%V=`Bu|a~ zNt~yHjXs-YD8alhRg6TSC@SgE-`xT1<+YA`Njg{`#v&A1hOH$eDxkLmnARL;O4HOe zH2LEe-fogw7H*{&5JqTBr^uhl87(`>NCGOX4?qneu}TD2UHRLPVBGc3ZS8UeeOioz zDjSJ|2ZFH@vN1+xu^UY`>M}uXaakZ zr1cRpTJ;MXLA*TM)tV<)3cqw`j5ECGrtSw%3JgC`ijugm-Rs^Nc8k2vIm>)Ou2VT6 z`z3&znLh-gkmkSY-o`Rp`Ug7Dr(i%R3Gc?tE^ywpk0P6?>lgbCZ9jS=1Hfjv7&z zPAgfaZpq%Ea)v}z-*5fx!8;{{*IHPsm*;^=@ z;u@RBRgT1hFQdl{+LXWK&jgHZw8f`M0rvs7&>6^3B7ixQssJiQM-OmO3Q22Zu%=R? zo?R8=Fw`rZ2DwekwfC zi6BbDoM>&y77kbO_Gy6Mi!7QxQ2@A=S*n|4hpYtLV*aJHqoxSBUwH1DOdk1lk?Jys zNJ;Dwp0Q*1&u_FTr)(MH-u5+P;Uz2L{YuNK{CfLR(Vbe{m61u7V)0q1XpI%aSSGH= z27v?CA9ktsJ&H7kDRu--aEd82oUmDW=I6#+i!{d44FkO5sN$xz9{YO0i+Q1k z#ZK7oLFQoQ&i^7=;`Kg7-yY#rGA48`3c#Y}MvqgsdpJ>~$PgkMiaxg-;#HoQ@?`Mw zeP1T)>EI(+oy1FeT$C_`*pbWQwA**?=sR?#?AwOfD-VN@;xtb3=kwEoMG=SuQotby zOFv~wc|D`i>yXmpjmoEn0qG)ukbm{2WVp8zm_ZqN6I{G3Mu0&6M zFwhaL?C=+e+BUST!cF3h#xk}L=Ifdpme=JwQ23F*)_~+o-CZUzso=BBi+cc_fi1G| z=4j7{INzTmP08SIyeH&i^qVB(lpk?0(U0`j+PB~4OALruDFzINf|%9%UyO}w#tCt; z6h%I#V(j@v`Z6*W5&#m6%j|@}^u;AF1iAhZ1LS&r&cEEKpd~!O@A` z#}t#!qUmb~*GSE5I$3j*SbnH>J6?_%V_C~H%=usq4v~Y|;2;7+i$b8Xr)G!UL7l`yNkJ5N*LcR;H-}^kOHT-&lPPzg^aVk?Q|J}I<9j#Ra z!zn|Av7Sd+k*6XSfIwtnDuXby zG3>9e8fIsvOL-P7Ajj3Gw#$L@pQ^qFek4?0QGTnf5?Gta2J%mbmThP(J=zFyG?PG53 zR_qA%7k;90w_QHIE7eG$o>8x~RXm5exAphmwLXt0rcBN#=xnzA`)?W$zMhd(NkSn3 z|219x`;X=0<9z-qp7|h^DTj0Y_@QCAICMNdTJ%b$T-W~nZ`bQdkVMT35UCmf`HpNdVPv|U?0Q|-Wfg*B zGh@4ecoQ}^&{^>y0$auQU-yd#bNEuX2fO!L+EwWZhAzi5RN!;r*1 zvTFlOmWN3lD*ATG9_G+tr?Ol2AcIp;Lt!=l|;W&X;y+6gN;!LhY3C0lo*2M_m3tZca9wvu&RpZ$h5J} z$x&7LL^1osNfUahMNfuD2T8b^hzu4+(NnB5UJxpM9sEO;QSHts;iJeHeB9Cau#_q! zG;=Dhep&D3*v`>j?ivPfQk&*1F4N67$u#pejuf=XT!Os$;9}rgktHxr!YVnUy7z}N zFj1VGf{1ck^hrK```fQS{zznGJp-v?4F5!x!z`mXxaDC_{gKCu3cXnF49BTOYcU#M z$$+F5BjSMaZht40=J`)gRL6M*)>Ly;C}b8O%(B`i^OE83kXsJ5I*s{oXDJGB3_n6f zhoApOQt;0i!t;?&ahED{y6*L36)L{J81fr!H0r8v#}qI;0J~JA`{NSkD(1invnadq zdkNA>Iw++m6KP-)(w8nMS70z$->l=p=jzGhTnWrk^1z}x6wHI_mYW(W-uoA~Y5VuL zGL4RQYDv#M}Lew$B4WDDlQFF+2YvdF89_RziG<*`4c(K zn~hes_+twDUYhkxAy+bU#K!F7BUIDz^?%2wAO4f0g>{$Y%--4uZQ+*C3V6;#Bq`<> z)o}GEX(xw<4S8kuT#nB&$2HAHO{|utS-Wz^IcKSYH}?k{dipaU)6xA)lpIz`#Xc>D9HmKmjjvcRAaT0OGeK7M!6C_ zfjK_L?J##GL$$N|c}!vvdje1xf!jJ=iV^JR$207WU=pB(A*1-aKobED24E|w(;{V* zhZt*BEivA%&?0sl7qS`&Ruae_7$?J5hZ2FevAi0XN{DU4`5* zV3RaYM~(!_B`ubSt*&NW~-ZUZIhFo`U^B@?fqmdKYtByUN(_pf1* z^#%#^IoZI(_bw+}*qGc+~9vM;XS7Yu}zCd;9g40xSFr>vJXdLNR9_HLP zG1Xn`j}pi`Mpz|<>8Eqf`D{Lv>4(WH8uS&VCbxDfY!97gt&3ZL)I22 zaYU^=b#7W73*&4#8=NW+tGc2PYa!EKxsURoA*zyr_qu;WdzAoSy+%zM9@}&ZBbtca zCxr8ms$76Kg$GUNF-!_=J42lWbalW4MvRPJt zY4!Z;Z{Huk|6_mty3eyIcT*R(P@uhjqBcElE*GJZ&qFkH;Gt@iqXA_p=r_Xi%~>lC>I!@sw6*Sg9O z!$xX4jq*7fz@w_MnL2nRNq?6b|IBKL)XZsd`xsaZj&gOm5hINL z)#sG$=To?+7YcM3#?XTQ}De@)Y2ogqHzh1V4kEp>8@6a5LpI*ZE(e6{i<{bFQTW2e-Z z+WHEosgZvXI5X1V@G7ooJzwu(Alp}%;REi-1Ol6qs<pftx?WFD!U8d7j7$|p=wJo!Wk?qBLz!~3 z54@{C3T%P`uv92^F!GLIo8Xjq8q#2o$?Gu5ik}1{@hUJg>3JKJRrI18r@&b;JjC-U ze8d#KZGQX{j{1-c`;7975w%8SC4S0V^bxO}WHy%nLOPr*rZn?qY5`#YR3a|*+^BjM zS&8hA+9a|Ye&N^;nCf3&KLFUQ*RfUQ-xK0Hq?iM!82e0pC-jaXo$_P3{q5V||2a+5 z^XGrsz$Ok+`Y^;DrVpt70`epbno5()gINd78$d0|Q6=!@e9Ozz3D;m%r*w%)f>Xz` z8|;Gtoi|`WC3*~Wy|KoTd=0(B+lYD0q*dgpM9}Ht4fi^2lMdqmy(PNZ^Ibg|yKtX((knU0k_-Dw&Lc6GqY*~A2n^G`xV~cZE`y?g5$#WjR)KOnnAb1Fu zf#o0o1z4#qMVGFrq;6e=+w&z-H+r_{d&*NW^um&kq3STVJl<4fvSeBFLr&Q+m3Ppe z4aB4!F*zUzP-=)Q`wBW`N329&8mhQamIW-zd`5X~dr)x8y7I6HgrUAyl28B4pr+F) z7_4IE)cS|xTHv!KtJGUO!-0Wiic2i~m5>uyT~bnn;bhHDd>m4pW##uwLu!mv_#|EE zSELPx{6ta)14GkR6oZoGvCb>-qLLG9z#S$62%77*ZPRh8sSf8ez9HIDKv~{iw09FTT#c*Nx$V}%S<#!>P+*$x z*I7qQxDGUS*VQy4+yu8?r5~zs9_dHu+DwE#7ZdU9XSeX zZ{NR*ez6~2H_o$uPrR4MxB2mbr0&)du!YhhC!Mx^?>~OO&U1hMs=6el`n0T%zx}o> z%k$^Y)65Z<7o;k*zCG@Fn=cU-j0~S`>3#DUe4e+z{eJF;@)wte!poe1W$Mf0_kU>F zoD$Ev5(T)??QV~6(W<1NFXBRzMdd9!O#PMj4BbsA6>?#a*8@mgb;v}!v{hN0B%_RJ z5$K-ICg4wK^~KSP!H1hLXN#J1VDEDKP-vuK1YD=JWPnRwKQ0}bzOzCBNS<>SDyADV z|B#?Wc)G9c+e1VHp@hK+c&;UsdVE~3y=Zr;sFv2wT5n3CGvk^=xG%gGj!F>?GwLhMj=SU`-cir9rDM}J_&lYOp5r0|5p8~*B( z3`uMnw!#d}AD(WzR}9B1oliZ{MREBVK6C6r!&aec9!&y@zUx%TRLL2|6$YV?uJR(( zHnWYu55CwM#XkB%HG<$$}WNj zB8ujM_y^zN?SqtJIX0geB*z;qad}mLuqxtjUm;`zeS1%qBL_}z<4VE8@~Z#8$Rtyz zmC1BYu1prVQ?%pN)g#9)x^s#p=Mz_vm{P)cUU-dy$iL{>Q*_rck!CBycgBqbNE%a% zb3rH!E?)>K^hS!!=#!7o1)^Gi_`+X*bWlB`M=Jymwnx_1S zTkD$0OjolkHI#xkGBIYqyk8B-;Y4S~;G}jv2|T$diSQ5bo2g73Vv=ODr5XSD_VM}W z&y2(1<5sk%vo(tZ;)b>|(FjdVm6Jcz`^rj2OQyxLveYD|FU`GZ8c{l6DP?1uA~2G= z#pg_>R!K)m0^BygVL zvTF4QezIf~FSYNN>mY5wPEi04l0h!OZyVc_sdA~wnLLp@_hr8riNZsE;{OETG zF{Yigd13X$@!`fWE9`{igs13@8M>$3?62^@T#N8rdk83YwfoJnQ|3x%>}x6@#8!Bt zEO!&rYQGM^7iGd=WAXoSgvO&SStdgY5pak5r>e_EOSbk}1E__=%19H1hhJ1*F0~Cu zaFpNw`g-pj8LH}Nvu(0UD_LZJdHxDM8~8;y5am){pb+B7cVaUeU|+W%KV;r~|2L0E zQf}INEg5P4@9^@;O%8)7s_W3x48oOJaqXmXcmis$Q;wsktF87EM_(X&vevHCK_UR~(1yb!g4)2hepK*mVaK(+wHY zZ%F|h3?*ZA@P%FSC&$y}J&{`n5b&%Ru%Bw(?B5|JjysJ0kYWYP&pI}kJ;u(kIMB=% z@VWEgMq>4hPSj?Y5PR;^`Lfn{@ystoiYhlMj4);gW7P-yhe8XmnI|;D1@gna>SJwP zRacr=kIv1y^d;eBuQ7XYz0!mYeMH(^2p0Yu^BPo~YW^8DtW>|mk(-FCuXP?W<7ftM zG zTtya32^dz;pi;2=u({*XM>Z|=Lz`IGF1{$EUpC+{9}1qNDKoYpz_{qU{;r;3CU(_B z>_Nq{@hq3vL~GUAfd*`|;#1k{I#9{mp3x!l@G4{M6*WM((djqdEOPA60MHg zeS0I9z{3s(sS|sD{`HsoH+O-0w?5ybaT)NotT>)Kq!_zXn)|8~&cXI9_fx(sO?W}; z>p`Z2ibn$?rclUrkuJ;55R3w;GsFph?QxcMQ6EQA!Y-T_TfIlN2va#2_K5)H^>AKl zY5kxng`OD(_o0$V@O;9XAU+rc>%+4;&*WlCi6%s$Og%Y5ZT8Iv9Dew4Z7Rw&j+i-a z$Pn(rux7QP99n*Mti)2tuFeQA{bup5ji&T^6aMj13-MS{2--uJ#RjTcY7mmq4A0xv z9_#sP%h``>cei6|{kkq6-{yN4pz=CTmwWmgy|<6YrFYDGf zrC_MTRK@I4q^%zOPknpnY?9T7X!h6jGR0)^cWEC#zW;pwu}n?pptp%rd<}6o#G&~9 z{rvUw^?Zu;AY%c=Z1iPa*4{t9Jzt+%57T|_PrGAiWv<^ou4Q`eyY{?-oYD$;CzQEW z!p)Jy$Ru)V^J%5Sm)zzQO|36>DoV;r&_p>5EPZ~QpHGT>!asCmw57NHLS`>HZPi{r zog&Wdv%;+@#%)uI3Ew@bpJ#fZl)F=Hxx4f+Yq!bHCA*XTX??ZrTfF>Kp>!vD?B}j6 z`*1#%eKeOD7P^KE$8>nAIo-!`9Y@n@5u|t?%c-5D-S>gPq)|H^HY%~~=XxG{Tcr6B zjJ8sbeZ!YI$Fepo~xhrRutk`GzU|QXf zQ~^y>t2su*Ii4YZQ8`y*MX}0ekj*S71dIS1-?|F7MN7qD@`34LO4l8}Mx_#(rR6?f z>kD5o%HPoGQsBXdA`TG8G;7u3WdQVTJ9JthcWU~8GNwxThs*@C0QfI+$MiVVWcG^ti-*iuz=Q-~Doox!=-r_!m_@mrh)Y5lppac3*w$e_AEOw1oE z00GGWm&3Z5407T>kgSU$oO&_~MqGVj{2h`kUDREcXfRghm(|6gdWa~LDqozt5K3(4 zz&;>$o)&2-0jaFHUcMJ$OyIm&5D}NIs*3rv#n~5?OY>RF>4^qfx1c zQ{^JKmFm)zoBTfObr*30a%%_TDynow84;#6=nxRI!w1AJ z09fqM-@J}JsT<0sq}<_iQ-fa5JmUj{Hwv+@?`dj4?EFFrHVf@Su2R`r@$BYe`t&L4c1-QvkV0r@PD}FWrG;XB zH2n7@Wv11tmXF+cj|rHf`?rwLgu4$~*At z+W7P-SR|!wHazE+#=b~)+%qO(9~spgke>?l0w^#;5}r=FY17(Ok=9KKZ5!uF>uWX6 zH8;o=Gi3g1)&0zx{jE+rSIFG%q7tlPbh0WO zdBRcbS6608@e$76n@MUCLoFT+C@N=Q;)xM184tI+qlU|rCU^UIn4!IE9b%&#(lrIY z%lPcu2BP(h80UIyWa)8rk*Ft?Q^EnZ#~|;~#;s;i9TxHHImbladxDMbv}O%u(WS>X zg#dc-G7NR-hb|0igk!AgF}UgSOmWVxIA5oR@3we@b^&(p^EeL2 zDX4ud{k$E|3}^JE8Ld$N>JsPFv(oJKKvobbq#=DZQ9}AJ`{1~(QQEN{oW8D?Z@92o zU0Vw%=J|XbD#+U^2#g1YuO@IJz^5U%v^1A>r!V38UQa}?&F&7J$k67 zN0x&1+ONL#b3aUSl%1rv$(Sqp5E1$0`201m{o3^a%tBsd727}7bN88rLAhnmVsPBo z(tS1s7gg;t*g>`=zAoJa^R0AQ_O*X+t?S(cSeVIQ9Sy1WVFL}!)+`m57PokR+7E0| zS6*Oc=N{z0$XoF^cBkV@ZG0oF?GSa@_W2E|*6rtwaS>j~8AgEGz5}QX=y}&Vulrye zQM!fYdRCifHM9;>UpLqGKkSE_H`KA!Jn5< znAFlWa7s-WzJS7C>}HgJ4A&0t(Nd8+j1ra>AS06z2CC8s|DkAds_c#zXxhuWN4x5A zZW$bsbA^zrfTUa^P9yW!@EXrER`s@@Jgh392H;3Ul7!YRM6?bs_j#J4b}Fm%{S@=sU}jL>N~?kF7cdi6_O=0mVn1ECj#WqLwHu8%TalOFPNv! zE6n{2C~PKCHY?a2!Njb_V{>q+`9ORF#~1o12CH%5H_1Vi3UChCIfW} zJMHrR$-eHYjw2^cPzJQaEHe;biL4C$E=?s)>l)4|eBCJnjJvfHTne!!=ry2qK}|A# zZ<>C}4Z$+Y>zdDl-XN~{an&%FK-El)af+S_h8iMus2;(JnA(Zbsj{2CU02JO)ip=B z(G30$l_UY+7?3*a9*?6k5WYQS1#3tsoW!uQT6Sd!c3>!0*WInq+#h;g_g$n-?KE~7 zteFU^+N8R>-7twl)N(gpR0k#LbDNuJu>e|jTE@0h4M9j7?0N%F3DFVSil_5dP9_FV zd$4J^g%^1qXIzFef@q}HHmz?3r#aJDoLj`7s&$f9n=z4g^piiTrpH15G6ok zQ$Uh);4(9D$LdpyQtNa!oOV#~7stBUDg%7mV~YTbkyWynp@!i9ld$Da>RaS_bimaD zuGxCZ`>@0?8cx*L^^2Y6WJZHtsir2>h|tTvq~rQZjAMyPs`h8E7?%;=v-wMHNC%(V)<#*AcuX=2@+*Ei=6!hPI7w?_^>!Q)-;zy~?x1V%7RaS=mJn zto!HZm6Zl){n*j#3x2ocnRU_E|h0V~-4o zojQ4*FK<9)Zm)_(5-<2f;pb8isZ(mx+Ro42)|fg3ys4THyDXEME~iC=6Lpri(t>-QgopC#nS&q-+`0MG7|Fxe@0ZEFgxSrSN6DY%($6;&Rjzc$Au;mdmIi*P6=j-$H zao_8@zAo+L_RVES(9Ze!=bzihx8ApVo{!IGTsclvpZ9sL-@aeZU;9rfSvdFB$A{)O zkH>zW)9YEmYH^YmIJKU=t%sCr^&qp*#B9<>J@-8XV1H&EkZV(NP|2O=sUcYuH>lq- z4Lx6(hT3kNN^6nQYuk_K?9^)S)N)#FtDmytRq2x=NT~S9GoVsEVb2KN#VR@4wnf(f zArzvKQbtS!JWeeewPEd$DT7R+?L8*wtw^748IEb%pRMad$n}$L>k?5Z^R(G?41_R} z0ABX&aPFvsLeLr)p-L2%W8b~q`xxM?)OKSCLkGQD_vEB0s^FZ(iZ=nk5F_SgnLc}u z4mA=>g6jxCu4C?$4SV@5d)DHPb~&9ypc0=r?!iBfz<~lc!$^TW@kM0Y^zX?5B3lZF z+yFIIYHSVzqxw_#0Y)RoX2UtfoU#yGi{pHLxQeiNz`edoIz(+g=V@mvP%bc~ArC?t z@<;ytMfS%C$6OOmUY9EwOKJ6b8c$K^$#o2VP#W2d0a4~7_OLzqJPA=LG({I5nA3kVoG!n0(_hf zzRXcWsc_+-*e26jbs#2#i~=H{jGnv1nr3ss!!%EfX)?(P))C4p zitCHy$?#u>n;N_tf6fX*e)IK>#tu{Plsnnk>?bU z1;XkS#f%w8_<1-&RH00Ilb~7bj9WMp%=LsXniA9eZxm1>^^JU7nrI`#G0{n~jWOE5 zJ8n`KpvIv?e{?3z*Sa#sw^6a>TX`mAOMa2}$o{NK(ci~1frP|=dA&n7V@{~Ci%*0j z%#(yM%7DhFDPp0-(U#zfdgr|FwO%&dSWYow?rAxf^SSTW>vLA%)@8k8P_i5g<hw)T-5{1~aW9wM5o_?kZeWpxax)v_9CvUXr@i8gH^W@-CGP z>GH_4!PXuhYR^RS+%+___^Z~cb6K>$w9H}>F1fMlBY`oGhRBqBP!0f^MX7VWUWqm~ z2xaPrmz^myK`eZry3a4oCQj*Z7Zu$bxG&*-XU!Yi)_!wct#?UweFUBo1}h%DhVgXf z=;<$yk^Olz9E-!2QzFL2 z_gjYnS!&Fu~EgOITHpNlaL`?S^ZARs@Ru~7RqfSib z+Fo^nE{5o;P)9~0(ImKxhG}q*>k!M#@FofCep_~D6owYOxR%-kDMnqK$*S;O9$M85 z1;+JC&FRPv%p4FOxcfTvYY8xv$L){rswot{qCoy6HDIym^{ZCyhk z8d)k-XimUUQ}mKmzQ2ws9Eyilps#*r58o#6c58PNMRryLFOWWV_+4IE2oSPEkU-Jb^S z84|s$ql{NH7pS2Q`HqNQCp5Uo6uzOUiimFZ`bdX#-OD<+zP_HHXgW+hbLTR(MXj|F z9IO8;5_G;>pVx=HAV0oe-F5&rBUID7v}M)7rVNBr@W9;K`8u2YGHgn6D3)Bwkk$h( z+bV6>bg#YtI`&)U0^uVwr97_Z_HRdT^D}&V3OhJ$`jg(awyfvtd0zG`q_xm{>}{F) z){kX6^Z}IBDu6;8hV+E3Z^lvwxlp_qpZWXJe$$FS1gTtvnJF=2@7J}i+qpi@`KKB7 zx|{8zYhCNJZNjk-sCDTGbcC#n&O0&kV!R4|jJAC`cZYgZe2U0^dTx)`Yn^3^sf|oq zldrG{YnaGEj?duCOl`Nz@?(+61{iV7v95DhB8K&DjM?34&JBX zy*)n8PsvK+`DdNrwIA)VEsuV^USgq2O{ERtI-~>?#riz@Dgg+S2D)4k*5|`=6LM3H zA!^53`oqt5sDVClu3baX)tTWj-mAw|Nv|GSN^_aaH+4kEA~#iSg$r`_w6E#o!%uoA z;C?acGeGi1wDWddc{jWd>T3W&{9i!4Y1Q zUr1f10^fU=PX+W^AvKgCXVhV_y(mv5(z25zQilN0i?^M$v|dd4Ybb%q{&WxHD%6gi z)0HbpAS6Y|>Itep%5a_zp6kmEN528* z=`&~tjy7FCcsi=v9*V`zCLvD7ClVql3vIjZm%>NG#mD9sPi6))iJ~nmgDX=FMELx^ zuAWtJDifjz-PvS>JlmYW)fAL*n+N9d6$H~*deLeF^P!7i0L`(E@`Y|*p!=` zIdYE9N**w9nSq!uECD)Nx9&`J6hTBN_7VjHtxCk(;^lp;*P$`JXUK$4IU&OBO7Ic5 z3nfVKXsToZX|F7FDf=)>aq^1N_Q$L{$)Y2uE85p^gYwL}X$;;M^_3%{y#m#G`gfO! zIQgJHxD2BgjA*2w?1y=Dy@tVd{Dj-KY51upB-Z?A3oEiI3`IdaJaffi0hHD29k!&^ zB5btQYq~Ef%KHErRimeE@MW)5g^+N*cu{$*$)p|V5e}&)vVfr$+J>WqLHCFgcKe}Y zCAq91MecWvOPW*uhQ37i$VyIRy~&>So!u`i%XDD0l<1ZqSst0XIEs}HkY&J?Jn06V zlX9BQDh;NsLrVu1@eCVH&~bLl3gInXE+%y5AK+zESUhvcZN3`c$KQi z(`{??lFTwx>tU^w-F`UyOoYSE2nmC@jA7XT^`MN;=GK+7ZMa0=b(cvO8JUatt`@#J z_&A2MrZ0-S2%k3D?X%LJA0QN8Q@FT1!MCU6@fk@q-r6*G3d=Vh7;(5GArKq$%!@rt!C z%GdqWlF#f~-@%hB2ahYx12uscn5i$#O}KVqT{iiBvjPG!vHuwIuo&CVRV}jNdT$cG z3EQkQ@rhmA;A)HuBaWWAqxcmS=MZWp95XqeD`I`xpVxJCq={v7ZSrtM_(U+Od%^Rm zOQf;fw(L!&Vrtv_+%#Xh1@k7v1;LQ%9%6{;t9dT$0!JKLJEdLXgqVb!6c1SHo&wd{ zuKBvhH3ZrMHW+S>@H#WSVy63Q7xr9o&17^rw>8)>-mst@%|%KXN_)tY`L$qMLFaW& zlR*gK2!DrIcerSGS|Na!`QT+6J}kjB(sZR^ZcC1HYOX9Jh_a>*rBpGroRYxZFVTEM znG&}MME*FNxIAQE$~@$KG==&jvkyN|CEcWcd5ZxJWK{%4cpq8zan}V>8rH`(et{#Q zn#Z7{hA_5*S_CC{_7iqu!e9izX$0-(8jdJ#CUzb|S}ApXgmI>*2#=0C40buC{PjXo zOJ!lyIO%;}$S6Pw2>1R>E$4m1hDY}#Q^c;(anVqHAT)2ll5EVU_yXzoY%9j8C1UyW z(^S(iQ}K>%($PWwx^6KKEQwI|r%++ZKmZzZP4qmUr?mGjwN6bfcxWnX|=2`nsLJmcB`Xf9yw> z5Nw(rkLBC9o~7|zC;|e+(g{|<-Cs_ zsN%H~6-Kxq8WoRR+p0oJB7#E|(j_lakq33HuH*Id&+W$#BQ$BiwABlJ7B%L%AC_zs z9fJ9dF6=tr)90_Br?3WFR&iwxx$g?k`1T=}h2y1APhY}Q*yXLWZPzC_jzg9q8vb9h z8ZmQleLSwuzixdIB}}7;_VD{^eVdo_xWqvK{f;HqvG?t}8bR%%VcU935B-b$&S=TJ z*BsY#xgVm;fcW^i9h0b$s}!EMNB-N!ha}2$pqC-Av|3k zr&cF4DO1(G;~dJE-za;X*fRZH`oqOPg`0oY_tb}KmOc)!*t=C4a@k$#ueG1 z*T;I8tRRm2In7&pJRTzMy!JMCIpYd$W3Zw#7byWwzf}ct4AOYRh&Y9tSOuO&@I1AR zrm)5TBjP8<@uV7Hcn!5df2L}83n;EVY6~KsBMO1sTYObHJSyfY!<%i;s@&m-drDtMo zd`^?oX2{p$1j-9JGZnW0bP<9^#IRAdWtoRd#9}n+oI@8x-$kT{j<%gEr!jW$B=aIJ zN)Sc}N74A|&7pEPAT&C3G0MVFi$z(T^d%4~vpLI>8i1plj$DN+i)%jQ(wm3 z3{;AF3f%d&#VvDko~z-a;uk<3;*NRsa+CbZ#%m?ZFLA=ihxSn&ZP7fnaH8MY3|gH= zTcdWetppFVE%?dFG>Foiw;hf#7>_qeXBBYg3auolCZl`!DI-cVxXd((9$8y)7#+j= z6A2`XiK(8SW>YeO8@-A6;~+(0d!#Efk%zsR$hJaOx#n@Nd%r&Hv&geCXexoy7@Y<; zDHE8W1Z<+dL9VsS880s@6w)W7DH1AlR2{?PODsg;3mK}mZd(REdXVut`XUPp7a&w8 zKPF*3zv<6-p8r?Nh795j)9oVFp6ZrQiGMW)I?dm6B`hs))5zAX_w`bwc3VG?mk4rs z?TS^K+ufzsz15!Egh|KVaUEiO#p4)nVC$OVLlM`Zq_w<*YFH0ZZ+c77uD(pIT`zEC zhRvqim^;^`1Oa}LJD!6ijQ8V1YH^gWh-t$RgRI|;&qI#RCa%+}Y>4Z4E!Q#aukz1< zI9I#IV49Ent4j4$L+GK7hry?&qNP>$-&Vq+CAc^tYwXiy6kDCO*-MLuh zst%X+`+WR_gDTJQ94j8Wif@ud59L1xE$S9Skm&DZ`ECb`ltdMiob%ZwI13ci=Ut|8 z7Z&&W2?TZFQ|`~v>DWpXgh1Ev&;nx8fWc&pt(iZ8S;b#Eka#ICGN1QOg#TaR=XkI4 zxzqu~NG7`kRwI~MhRkF?G|~>8mNB^hv7w1@P1^$6A|p`cNL*DfVv7PALu5^QO-(k6 zVwYXfybWVGrUhXZVO13&J35AO?6E_u8V}P)JVgha2dQB4)Vr3L%;^jU!Co|5LUKJw zQ}Z-wTTpy1YB0V>|M0x@*q7ey2^Zo{o_|f)yV_14J8pmO`Cgriu{p8g5PJpMC&nd` z0N7Z=~vLn;YjQNq}KdHdEM50_+CfDb9^buE2eKGx&;^rI1Jv-KCV z>?Dp8j|@bb8mh~wU^(@vT+~K!oIowca$ulwJ98?9@h9g?$$cj>Q4ke>Z{~$-iq856c9-DKDG$FSY!J^=XRfMnU`;YUy zmX9AkH{)9-RmR_czmQ#Mx_%%uzK_?rs{?F{02V-A&7MDh!C8NN`_>=Z>knwk({;$a z(7FdTo5Ed=R}&jwa(t+ot|#?14OoDLs<#!KaVY3y?b|A1nh5l!i<+jVKKhcaN1vZ+ zJq764QY}G5=jZG7{Oj@k$E!b%*NefpDo#Va+Jq7MWd5tKE(;0I2K!?>K0XwCA*f6J z{@jI~UDvUG|NHs;JpTCOkODxDgEuEp3FhASU(YsqdhSo*cm}1YP_Y#L*^;xOjT&$b zBQ(v(lI|&oiY{Zu^A+8@e~}$yUaf6127?ia!);v5E=Q0GSR^AOo#t`eeRbTD9{|&~ z1h!5ECT)fg=T5tfHcT z{X0(=6{P~Cclog$nIq9~+cyLYT_0ERnDl?FFUB`3Kte`;5wsVxp$Pu*nZ*Es{Gtll z=9L+yhv;01;}D(Go4`~^o`Fv^-of{=a&;|FE4dnMix}mChu}1jT(I$e{#m=3IPW}@ z9#PQE9Hw+c#}|jb%v&?!O2bo85A>Hcz)s0q(TzyG#}`gM0EaS|Ilm=S;u58Df((~d zeiNm-b{jb8u~GD?X}*|gwf3lFrbr4&8dCk9PzIc*YDf%zVqGvlr#@RX6I)y%FzC>f zn)o1*nUSV59vi{SyAH=|-I}Hw=Ox9~x-MI{r_bFyJEAebT_`PPs?$23`BViUpHD#* z_zMPM#%vPzsCR2!s1kV<6(Sonf#xf280?9;(&H|KxJM_Z(<)7F@T6hf4^h61$#NND z&!K}Xa(%hd=6PU^MBJYgcQQ(As2(qsa%T6J6p~w%0U(up++lMy;@ikwM@R5ZgsGM} zE*QhkoO%g~g8yDbxS_SL<397=$Zjt2>v7OCHpC+usZ}X*s=dv}!=0?WWupnr?|--1 z^)3WhnsGz$A;!hv2@IxNyn~8kTaF<^p_G1aN}Xr(RJ(42LD3Zl-Eg}hoNH8x z7yu#v2R_X82}CuBtyKkEDwq|Vc0HTT+sz~27DtV|9``;`5O}cdGZ3;r2yd8Tp@@du qVI_Nl8}o+NpZL(v2! "The authentication implementation looks reasonable. Approved." - -An adversarial review produces: - -> 1. **HIGH** - `login.ts:47` - No rate limiting on failed attempts -> 2. **HIGH** - Session token stored in localStorage (XSS vulnerable) -> 3. **MEDIUM** - Password validation happens client-side only -> 4. **MEDIUM** - No audit logging for failed login attempts -> 5. **LOW** - Magic number `3600` should be `SESSION_TIMEOUT_SECONDS` - -The first review might miss a security vulnerability. The second caught four. - -## Iteration and Diminishing Returns - -After addressing findings, consider running it again. A second pass usually catches more. A third isn't always useless either. But each pass takes time, and eventually you hit diminishing returns - just nitpicks and false findings. - -:::tip[Better Reviews] -Assume problems exist. Look for what's missing, not just what's wrong. -::: diff --git a/docs/explanation/brainstorming.md b/docs/explanation/brainstorming.md deleted file mode 100644 index 51aa80e22..000000000 --- a/docs/explanation/brainstorming.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "Brainstorming" -description: Interactive creative sessions using 60+ proven ideation techniques -sidebar: - order: 2 ---- - -Unlock your creativity through guided exploration. - -## What is Brainstorming? - -Run `brainstorming` and you've got a creative facilitator pulling ideas out of you - not generating them for you. The AI acts as coach and guide, using proven techniques to create conditions where your best thinking emerges. - -**Good for:** - -- Breaking through creative blocks -- Generating product or feature ideas -- Exploring problems from new angles -- Developing raw concepts into action plans - -## How It Works - -1. **Setup** - Define topic, goals, constraints -2. **Choose approach** - Pick techniques yourself, get AI recommendations, go random, or follow a progressive flow -3. **Facilitation** - Work through techniques with probing questions and collaborative coaching -4. **Organize** - Ideas grouped into themes and prioritized -5. **Action** - Top ideas get next steps and success metrics - -Everything gets captured in a session document you can reference later or share with stakeholders. - -:::note[Your Ideas] -Every idea comes from you. The workflow creates conditions for insight - you're the source. -::: diff --git a/docs/explanation/established-projects-faq.md b/docs/explanation/established-projects-faq.md deleted file mode 100644 index fe217fcdd..000000000 --- a/docs/explanation/established-projects-faq.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: "Established Projects FAQ" -description: Common questions about using BMad Method on established projects -sidebar: - order: 8 ---- -Quick answers to common questions about working on established projects with the BMad Method (BMM). - -## Questions - -- [Do I have to run document-project first?](#do-i-have-to-run-document-project-first) -- [What if I forget to run document-project?](#what-if-i-forget-to-run-document-project) -- [Can I use Quick Flow for established projects?](#can-i-use-quick-flow-for-established-projects) -- [What if my existing code doesn't follow best practices?](#what-if-my-existing-code-doesnt-follow-best-practices) - -### Do I have to run document-project first? - -Highly recommended, especially if: - -- No existing documentation -- Documentation is outdated -- AI agents need context about existing code - -You can skip it if you have comprehensive, up-to-date documentation including `docs/index.md` or will use other tools or techniques to aid in discovery for the agent to build on an existing system. - -### What if I forget to run document-project? - -Don't worry about it - you can do it at any time. You can even do it during or after a project to help keep docs up to date. - -### Can I use Quick Flow for established projects? - -Yes! Quick Flow works great for established projects. It will: - -- Auto-detect your existing stack -- Analyze existing code patterns -- Detect conventions and ask for confirmation -- Generate context-rich tech-spec that respects existing code - -Perfect for bug fixes and small features in existing codebases. - -### What if my existing code doesn't follow best practices? - -Quick Flow detects your conventions and asks: "Should I follow these existing conventions?" You decide: - -- **Yes** → Maintain consistency with current codebase -- **No** → Establish new standards (document why in tech-spec) - -BMM respects your choice — it won't force modernization, but it will offer it. - -**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it! diff --git a/docs/explanation/party-mode.md b/docs/explanation/party-mode.md deleted file mode 100644 index fe25f197d..000000000 --- a/docs/explanation/party-mode.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: "Party Mode" -description: Multi-agent collaboration - get all your AI agents in one conversation -sidebar: - order: 7 ---- - -Get all your AI agents in one conversation. - -## What is Party Mode? - -Run `party-mode` and you've got your whole AI team in one room - PM, Architect, Dev, UX Designer, whoever you need. BMad Master orchestrates, picking relevant agents per message. Agents respond in character, agree, disagree, and build on each other's ideas. - -The conversation continues as long as you want. Ask follow-ups, push back on answers, redirect the discussion - it's a real back-and-forth with your agents until you're done. - -**Good for:** - -- Big decisions with tradeoffs -- Brainstorming sessions -- Post-mortems when things go wrong -- Sprint retrospectives and planning - -## Examples - -### Calling Out Bad Architecture - -**You:** "Okay team, our last sprint was a disaster. The authentication service went down three times. Who screwed this up?" - -**Architect:** "The design was sound - distributed authentication with proper fallbacks. If implementation deviated from the spec..." - -**Dev:** "I followed the architecture doc exactly. The spec didn't account for concurrent session invalidation race conditions." - -**PM:** "Both of you missed the bigger issue - we didn't validate session management requirements in the PRD. This is on me for not catching it." - -**TEA:** "And I should've caught this in integration tests. The test scenarios didn't cover concurrent invalidation." - -### Creative Brainstorming - -**You:** "How do we make onboarding feel magical instead of boring?" - -**UX Designer:** "Start with progressive disclosure - reveal features as users need them, not all at once in a tutorial." - -**Storyteller:** "What if onboarding was a story? Each step reveals a character's journey - the user IS the hero." - -**Game Designer:** "Building on that - what if the first 'quest' is actually solving a real user problem? They learn by doing something valuable." - -### Technical Decision - -**You:** "Monolith or microservices for MVP?" - -**Architect:** "Start monolith. Microservices add complexity you don't need at 1000 users." - -**PM:** "Agree. Time to market matters more than theoretical scalability." - -**Dev:** "Monolith with clear module boundaries. We can extract services later if needed." - -:::tip[Better Decisions] -Better decisions through diverse perspectives. Welcome to party mode. -::: diff --git a/docs/explanation/preventing-agent-conflicts.md b/docs/explanation/preventing-agent-conflicts.md deleted file mode 100644 index e611f1c3a..000000000 --- a/docs/explanation/preventing-agent-conflicts.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -title: "Preventing Agent Conflicts" -description: How architecture prevents conflicts when multiple agents implement a system -sidebar: - order: 4 ---- - -When multiple AI agents implement different parts of a system, they can make conflicting technical decisions. Architecture documentation prevents this by establishing shared standards. - -## Common Conflict Types - -### API Style Conflicts - -Without architecture: -- Agent A uses REST with `/users/{id}` -- Agent B uses GraphQL mutations -- Result: Inconsistent API patterns, confused consumers - -With architecture: -- ADR specifies: "Use GraphQL for all client-server communication" -- All agents follow the same pattern - -### Database Design Conflicts - -Without architecture: -- Agent A uses snake_case column names -- Agent B uses camelCase column names -- Result: Inconsistent schema, confusing queries - -With architecture: -- Standards document specifies naming conventions -- All agents follow the same patterns - -### State Management Conflicts - -Without architecture: -- Agent A uses Redux for global state -- Agent B uses React Context -- Result: Multiple state management approaches, complexity - -With architecture: -- ADR specifies state management approach -- All agents implement consistently - -## How Architecture Prevents Conflicts - -### 1. Explicit Decisions via ADRs - -Every significant technology choice is documented with: -- Context (why this decision matters) -- Options considered (what alternatives exist) -- Decision (what we chose) -- Rationale (why we chose it) -- Consequences (trade-offs accepted) - -### 2. FR/NFR-Specific Guidance - -Architecture maps each functional requirement to technical approach: -- FR-001: User Management → GraphQL mutations -- FR-002: Mobile App → Optimized queries - -### 3. Standards and Conventions - -Explicit documentation of: -- Directory structure -- Naming conventions -- Code organization -- Testing patterns - -## Architecture as Shared Context - -Think of architecture as the shared context that all agents read before implementing: - -```text -PRD: "What to build" - ↓ -Architecture: "How to build it" - ↓ -Agent A reads architecture → implements Epic 1 -Agent B reads architecture → implements Epic 2 -Agent C reads architecture → implements Epic 3 - ↓ -Result: Consistent implementation -``` - -## Key ADR Topics - -Common decisions that prevent conflicts: - -| Topic | Example Decision | -| ---------------- | -------------------------------------------- | -| API Style | GraphQL vs REST vs gRPC | -| Database | PostgreSQL vs MongoDB | -| Auth | JWT vs Sessions | -| State Management | Redux vs Context vs Zustand | -| Styling | CSS Modules vs Tailwind vs Styled Components | -| Testing | Jest + Playwright vs Vitest + Cypress | - -## Anti-Patterns to Avoid - -:::caution[Common Mistakes] -- **Implicit Decisions** — "We'll figure out the API style as we go" leads to inconsistency -- **Over-Documentation** — Documenting every minor choice causes analysis paralysis -- **Stale Architecture** — Documents written once and never updated cause agents to follow outdated patterns -::: - -:::tip[Correct Approach] -- Document decisions that cross epic boundaries -- Focus on conflict-prone areas -- Update architecture as you learn -- Use `correct-course` for significant changes -::: diff --git a/docs/explanation/project-context.md b/docs/explanation/project-context.md deleted file mode 100644 index 6522b92a5..000000000 --- a/docs/explanation/project-context.md +++ /dev/null @@ -1,157 +0,0 @@ ---- -title: "Project Context" -description: How project-context.md guides AI agents with your project's rules and preferences -sidebar: - order: 7 ---- - -The `project-context.md` file is your project's implementation guide for AI agents. Similar to a "constitution" in other development systems, it captures the rules, patterns, and preferences that ensure consistent code generation across all workflows. - -## What It Does - -AI agents make implementation decisions constantly — which patterns to follow, how to structure code, what conventions to use. Without clear guidance, they may: -- Follow generic best practices that don't match your codebase -- Make inconsistent decisions across different stories -- Miss project-specific requirements or constraints - -The `project-context.md` file solves this by documenting what agents need to know in a concise, LLM-optimized format. - -## How It Works - -Every implementation workflow automatically loads `project-context.md` if it exists. The architect workflow also loads it to respect your technical preferences when designing the architecture. - -**Loaded by these workflows:** -- `create-architecture` — respects technical preferences during solutioning -- `create-story` — informs story creation with project patterns -- `dev-story` — guides implementation decisions -- `code-review` — validates against project standards -- `quick-dev` — applies patterns when implementing tech-specs -- `sprint-planning`, `retrospective`, `correct-course` — provides project-wide context - -## When to Create It - -The `project-context.md` file is useful at any stage of a project: - -| Scenario | When to Create | Purpose | -|----------|----------------|---------| -| **New project, before architecture** | Manually, before `create-architecture` | Document your technical preferences so the architect respects them | -| **New project, after architecture** | Via `generate-project-context` or manually | Capture architecture decisions for implementation agents | -| **Existing project** | Via `generate-project-context` | Discover existing patterns so agents follow established conventions | -| **Quick Flow project** | Before or during `quick-dev` | Ensure quick implementation respects your patterns | - -:::tip[Recommended] -For new projects, create it manually before architecture if you have strong technical preferences. Otherwise, generate it after architecture to capture those decisions. -::: - -## What Goes In It - -The file has two main sections: - -### Technology Stack & Versions - -Documents the frameworks, languages, and tools your project uses with specific versions: - -```markdown -## Technology Stack & Versions - -- Node.js 20.x, TypeScript 5.3, React 18.2 -- State: Zustand (not Redux) -- Testing: Vitest, Playwright, MSW -- Styling: Tailwind CSS with custom design tokens -``` - -### Critical Implementation Rules - -Documents patterns and conventions that agents might otherwise miss: - -```markdown -## Critical Implementation Rules - -**TypeScript Configuration:** -- Strict mode enabled — no `any` types without explicit approval -- Use `interface` for public APIs, `type` for unions/intersections - -**Code Organization:** -- Components in `/src/components/` with co-located `.test.tsx` -- Utilities in `/src/lib/` for reusable pure functions -- API calls use the `apiClient` singleton — never fetch directly - -**Testing Patterns:** -- Unit tests focus on business logic, not implementation details -- Integration tests use MSW to mock API responses -- E2E tests cover critical user journeys only - -**Framework-Specific:** -- All async operations use the `handleError` wrapper for consistent error handling -- Feature flags accessed via `featureFlag()` from `@/lib/flags` -- New routes follow the file-based routing pattern in `/src/app/` -``` - -Focus on what's **unobvious** — things agents might not infer from reading code snippets. Don't document standard practices that apply universally. - -## Creating the File - -You have three options: - -### Manual Creation - -Create the file at `_bmad-output/project-context.md` and add your rules: - -```bash -# In your project root -mkdir -p _bmad-output -touch _bmad-output/project-context.md -``` - -Edit it with your technology stack and implementation rules. The architect and implementation workflows will automatically find and load it. - -### Generate After Architecture - -Run the `generate-project-context` workflow after completing your architecture: - -```bash -/bmad-bmm-generate-project-context -``` - -This scans your architecture document and project files to generate a context file capturing the decisions made. - -### Generate for Existing Projects - -For existing projects, run `generate-project-context` to discover existing patterns: - -```bash -/bmad-bmm-generate-project-context -``` - -The workflow analyzes your codebase to identify conventions, then generates a context file you can review and refine. - -## Why It Matters - -Without `project-context.md`, agents make assumptions that may not match your project: - -| Without Context | With Context | -|----------------|--------------| -| Uses generic patterns | Follows your established conventions | -| Inconsistent style across stories | Consistent implementation | -| May miss project-specific constraints | Respects all technical requirements | -| Each agent decides independently | All agents align with same rules | - -This is especially important for: -- **Quick Flow** — skips PRD and architecture, so context file fills the gap -- **Team projects** — ensures all agents follow the same standards -- **Existing projects** — prevents breaking established patterns - -## Editing and Updating - -The `project-context.md` file is a living document. Update it when: - -- Architecture decisions change -- New conventions are established -- Patterns evolve during implementation -- You identify gaps from agent behavior - -You can edit it manually at any time, or re-run `generate-project-context` to update it after significant changes. - -:::note[File Location] -The default location is `_bmad-output/project-context.md`. Workflows search for it there, and also check `**/project-context.md` anywhere in your project. -::: diff --git a/docs/explanation/quick-flow.md b/docs/explanation/quick-flow.md deleted file mode 100644 index 6751feee0..000000000 --- a/docs/explanation/quick-flow.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: "Quick Flow" -description: Fast-track for small changes - skip the full methodology -sidebar: - order: 1 ---- - -Skip the ceremony. Quick Flow takes you from idea to working code in two commands - no Product Brief, no PRD, no Architecture doc. - -## When to Use It - -- Bug fixes and patches -- Refactoring existing code -- Small, well-understood features -- Prototyping and spikes -- Single-agent work where one developer can hold the full scope - -## When NOT to Use It - -- New products or platforms that need stakeholder alignment -- Major features spanning multiple components or teams -- Work that requires architectural decisions (database schema, API contracts, service boundaries) -- Anything where requirements are unclear or contested - -:::caution[Scope Creep] -If you start a Quick Flow and realize the scope is bigger than expected, `quick-dev` will detect this and offer to escalate. You can switch to a full PRD workflow at any point without losing your work. -::: - -## How It Works - -Quick Flow has two commands, each backed by a structured workflow. You can run them together or independently. - -### quick-spec: Plan - -Run `quick-spec` and Barry (the Quick Flow agent) walks you through a conversational discovery process: - -1. **Understand** - You describe what you want to build. Barry scans the codebase to ask informed questions, then captures a problem statement, solution approach, and scope boundaries. -2. **Investigate** - Barry reads relevant files, maps code patterns, identifies files to modify, and documents the technical context. -3. **Generate** - Produces a complete tech-spec with ordered implementation tasks (specific file paths and actions), acceptance criteria in Given/When/Then format, testing strategy, and dependencies. -4. **Review** - Presents the full spec for your sign-off. You can edit, ask questions, run adversarial review, or refine with advanced elicitation before finalizing. - -The output is a `tech-spec-{slug}.md` file saved to your project's implementation artifacts folder. It contains everything a fresh agent needs to implement the feature - no conversation history required. - -### quick-dev: Build - -Run `quick-dev` and Barry implements the work. It operates in two modes: - -- **Tech-spec mode** - Point it at a spec file (`quick-dev tech-spec-auth.md`) and it executes every task in order, writes tests, and verifies acceptance criteria. -- **Direct mode** - Give it instructions directly (`quick-dev "refactor the auth middleware"`) and it gathers context, builds a mental plan, and executes. - -After implementation, `quick-dev` runs a self-check audit against all tasks and acceptance criteria, then triggers an adversarial code review of the diff. Findings are presented for you to resolve before wrapping up. - -:::tip[Fresh Context] -For best results, run `quick-dev` in a new conversation after finishing `quick-spec`. This gives the implementation agent clean context focused solely on building. -::: - -## What Quick Flow Skips - -The full BMad Method produces a Product Brief, PRD, Architecture doc, and Epic/Story breakdown before any code is written. Quick Flow replaces all of that with a single tech-spec. This works because Quick Flow targets changes where: - -- The product direction is already established -- Architecture decisions are already made -- A single developer can reason about the full scope -- Requirements fit in one conversation - -## Escalating to Full BMad Method - -Quick Flow includes built-in guardrails for scope detection. When you run `quick-dev` with a direct request, it evaluates signals like multi-component mentions, system-level language, and uncertainty about approach. If it detects the work is bigger than a quick flow: - -- **Light escalation** - Recommends running `quick-spec` first to create a plan -- **Heavy escalation** - Recommends switching to the full BMad Method PRD process - -You can also escalate manually at any time. Your tech-spec work carries forward - it becomes input for the broader planning process rather than being discarded. diff --git a/docs/explanation/why-solutioning-matters.md b/docs/explanation/why-solutioning-matters.md deleted file mode 100644 index c1aa5ba67..000000000 --- a/docs/explanation/why-solutioning-matters.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: "Why Solutioning Matters" -description: Understanding why the solutioning phase is critical for multi-epic projects -sidebar: - order: 3 ---- - - -Phase 3 (Solutioning) translates **what** to build (from Planning) into **how** to build it (technical design). This phase prevents agent conflicts in multi-epic projects by documenting architectural decisions before implementation begins. - -## The Problem Without Solutioning - -```text -Agent 1 implements Epic 1 using REST API -Agent 2 implements Epic 2 using GraphQL -Result: Inconsistent API design, integration nightmare -``` - -When multiple agents implement different parts of a system without shared architectural guidance, they make independent technical decisions that may conflict. - -## The Solution With Solutioning - -```text -architecture workflow decides: "Use GraphQL for all APIs" -All agents follow architecture decisions -Result: Consistent implementation, no conflicts -``` - -By documenting technical decisions explicitly, all agents implement consistently and integration becomes straightforward. - -## Solutioning vs Planning - -| Aspect | Planning (Phase 2) | Solutioning (Phase 3) | -| -------- | ----------------------- | --------------------------------- | -| Question | What and Why? | How? Then What units of work? | -| Output | FRs/NFRs (Requirements) | Architecture + Epics/Stories | -| Agent | PM | Architect → PM | -| Audience | Stakeholders | Developers | -| Document | PRD (FRs/NFRs) | Architecture + Epic Files | -| Level | Business logic | Technical design + Work breakdown | - -## Key Principle - -**Make technical decisions explicit and documented** so all agents implement consistently. - -This prevents: -- API style conflicts (REST vs GraphQL) -- Database design inconsistencies -- State management disagreements -- Naming convention mismatches -- Security approach variations - -## When Solutioning is Required - -| Track | Solutioning Required? | -|-------|----------------------| -| Quick Flow | No - skip entirely | -| BMad Method Simple | Optional | -| BMad Method Complex | Yes | -| Enterprise | Yes | - -:::tip[Rule of Thumb] -If you have multiple epics that could be implemented by different agents, you need solutioning. -::: - -## The Cost of Skipping - -Skipping solutioning on complex projects leads to: - -- **Integration issues** discovered mid-sprint -- **Rework** due to conflicting implementations -- **Longer development time** overall -- **Technical debt** from inconsistent patterns - -:::caution[Cost Multiplier] -Catching alignment issues in solutioning is 10× faster than discovering them during implementation. -::: diff --git a/docs/how-to/customize-bmad.md b/docs/how-to/customize-bmad.md deleted file mode 100644 index d478c349b..000000000 --- a/docs/how-to/customize-bmad.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -title: "How to Customize BMad" -description: Customize agents, workflows, and modules while preserving update compatibility -sidebar: - order: 7 ---- - -Use the `.customize.yaml` files to tailor agent behavior, personas, and menus while preserving your changes across updates. - -## When to Use This - -- You want to change an agent's name, personality, or communication style -- You need agents to remember project-specific context -- You want to add custom menu items that trigger your own workflows or prompts -- You want agents to perform specific actions every time they start up - -:::note[Prerequisites] -- BMad installed in your project (see [How to Install BMad](./install-bmad.md)) -- A text editor for YAML files -::: - -:::caution[Keep Your Customizations Safe] -Always use the `.customize.yaml` files described here rather than editing agent files directly. The installer overwrites agent files during updates, but preserves your `.customize.yaml` changes. -::: - -## Steps - -### 1. Locate Customization Files - -After installation, find one `.customize.yaml` file per agent in: - -```text -_bmad/_config/agents/ -├── core-bmad-master.customize.yaml -├── bmm-dev.customize.yaml -├── bmm-pm.customize.yaml -└── ... (one file per installed agent) -``` - -### 2. Edit the Customization File - -Open the `.customize.yaml` file for the agent you want to modify. Every section is optional -- customize only what you need. - -| Section | Behavior | Purpose | -| ------------------ | -------- | ----------------------------------------------- | -| `agent.metadata` | Replaces | Override the agent's display name | -| `persona` | Replaces | Set role, identity, style, and principles | -| `memories` | Appends | Add persistent context the agent always recalls | -| `menu` | Appends | Add custom menu items for workflows or prompts | -| `critical_actions` | Appends | Define startup instructions for the agent | -| `prompts` | Appends | Create reusable prompts for menu actions | - -Sections marked **Replaces** overwrite the agent's defaults entirely. Sections marked **Appends** add to the existing configuration. - -**Agent Name** - -Change how the agent introduces itself: - -```yaml -agent: - metadata: - name: 'Spongebob' # Default: "Amelia" -``` - -**Persona** - -Replace the agent's personality, role, and communication style: - -```yaml -persona: - role: 'Senior Full-Stack Engineer' - identity: 'Lives in a pineapple (under the sea)' - communication_style: 'Spongebob annoying' - principles: - - 'Never Nester, Spongebob Devs hate nesting more than 2 levels deep' - - 'Favor composition over inheritance' -``` - -The `persona` section replaces the entire default persona, so include all four fields if you set it. - -**Memories** - -Add persistent context the agent will always remember: - -```yaml -memories: - - 'Works at Krusty Krab' - - 'Favorite Celebrity: David Hasslehoff' - - 'Learned in Epic 1 that it is not cool to just pretend that tests have passed' -``` - -**Menu Items** - -Add custom entries to the agent's display menu. Each item needs a `trigger`, a target (`workflow` path or `action` reference), and a `description`: - -```yaml -menu: - - trigger: my-workflow - workflow: 'my-custom/workflows/my-workflow.yaml' - description: My custom workflow - - trigger: deploy - action: '#deploy-prompt' - description: Deploy to production -``` - -**Critical Actions** - -Define instructions that run when the agent starts up: - -```yaml -critical_actions: - - 'Check the CI Pipelines with the XYZ Skill and alert user on wake if anything is urgently needing attention' -``` - -**Custom Prompts** - -Create reusable prompts that menu items can reference with `action="#id"`: - -```yaml -prompts: - - id: deploy-prompt - content: | - Deploy the current branch to production: - 1. Run all tests - 2. Build the project - 3. Execute deployment script -``` - -### 3. Apply Your Changes - -After editing, recompile the agent to apply changes: - -```bash -npx bmad-method install -``` - -The installer detects the existing installation and offers these options: - -| Option | What It Does | -| ---------------------------- | ------------------------------------------------------------------- | -| **Quick Update** | Updates all modules to the latest version and recompiles all agents | -| **Recompile Agents** | Applies customizations only, without updating module files | -| **Modify BMad Installation** | Full installation flow for adding or removing modules | - -For customization-only changes, **Recompile Agents** is the fastest option. - -## Troubleshooting - -**Changes not appearing?** - -- Run `npx bmad-method install` and select **Recompile Agents** to apply changes -- Check that your YAML syntax is valid (indentation matters) -- Verify you edited the correct `.customize.yaml` file for the agent - -**Agent not loading?** - -- Check for YAML syntax errors using an online YAML validator -- Ensure you did not leave fields empty after uncommenting them -- Try reverting to the original template and rebuilding - -**Need to reset an agent?** - -- Clear or delete the agent's `.customize.yaml` file -- Run `npx bmad-method install` and select **Recompile Agents** to restore defaults - -## Workflow Customization - -Customization of existing BMad Method workflows and skills is coming soon. - -## Module Customization - -Guidance on building expansion modules and customizing existing modules is coming soon. diff --git a/docs/how-to/established-projects.md b/docs/how-to/established-projects.md deleted file mode 100644 index cc36e0f90..000000000 --- a/docs/how-to/established-projects.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -title: "Established Projects" -description: How to use BMad Method on existing codebases -sidebar: - order: 6 ---- - -Use BMad Method effectively when working on existing projects and legacy codebases. - -This guide covers the essential workflow for onboarding to existing projects with BMad Method. - -:::note[Prerequisites] -- BMad Method installed (`npx bmad-method install`) -- An existing codebase you want to work on -- Access to an AI-powered IDE (Claude Code or Cursor) -::: - -## Step 1: Clean Up Completed Planning Artifacts - -If you have completed all PRD epics and stories through the BMad process, clean up those files. Archive them, delete them, or rely on version history if needed. Do not keep these files in: - -- `docs/` -- `_bmad-output/planning-artifacts/` -- `_bmad-output/implementation-artifacts/` - -## Step 2: Create Project Context - -:::tip[Recommended for Existing Projects] -Generate `project-context.md` to capture your existing codebase patterns and conventions. This ensures AI agents follow your established practices when implementing changes. -::: - -Run the generate project context workflow: - -```bash -/bmad-bmm-generate-project-context -``` - -This scans your codebase to identify: -- Technology stack and versions -- Code organization patterns -- Naming conventions -- Testing approaches -- Framework-specific patterns - -You can review and refine the generated file, or create it manually at `_bmad-output/project-context.md` if you prefer. - -[Learn more about project context](../explanation/project-context.md) - -## Step 3: Maintain Quality Project Documentation - -Your `docs/` folder should contain succinct, well-organized documentation that accurately represents your project: - -- Intent and business rationale -- Business rules -- Architecture -- Any other relevant project information - -For complex projects, consider using the `document-project` workflow. It offers runtime variants that will scan your entire project and document its actual current state. - -## Step 3: Get Help - -### BMad-Help: Your Starting Point - -**Run `/bmad-help` anytime you're unsure what to do next.** This intelligent guide: - -- Inspects your project to see what's already been done -- Shows options based on your installed modules -- Understands natural language queries - -``` -/bmad-help I have an existing Rails app, where should I start? -/bmad-help What's the difference between quick-flow and full method? -/bmad-help Show me what workflows are available -``` - -BMad-Help also **automatically runs at the end of every workflow**, providing clear guidance on exactly what to do next. - -### Choosing Your Approach - -You have two primary options depending on the scope of changes: - -| Scope | Recommended Approach | -| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- | -| **Small updates or additions** | Use `quick-flow-solo-dev` to create a tech-spec and implement the change. The full four-phase BMad Method is likely overkill. | -| **Major changes or additions** | Start with the BMad Method, applying as much or as little rigor as needed. | - -### During PRD Creation - -When creating a brief or jumping directly into the PRD, ensure the agent: - -- Finds and analyzes your existing project documentation -- Reads the proper context about your current system - -You can guide the agent explicitly, but the goal is to ensure the new feature integrates well with your existing system. - -### UX Considerations - -UX work is optional. The decision depends not on whether your project has a UX, but on: - -- Whether you will be working on UX changes -- Whether significant new UX designs or patterns are needed - -If your changes amount to simple updates to existing screens you are happy with, a full UX process is unnecessary. - -### Architecture Considerations - -When doing architecture, ensure the architect: - -- Uses the proper documented files -- Scans the existing codebase - -Pay close attention here to prevent reinventing the wheel or making decisions that misalign with your existing architecture. - -## More Information - -- **[Quick Fixes](./quick-fixes.md)** - Bug fixes and ad-hoc changes -- **[Established Projects FAQ](../explanation/established-projects-faq.md)** - Common questions about working on established projects diff --git a/docs/how-to/get-answers-about-bmad.md b/docs/how-to/get-answers-about-bmad.md deleted file mode 100644 index edefdeacb..000000000 --- a/docs/how-to/get-answers-about-bmad.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -title: "How to Get Answers About BMad" -description: Use an LLM to quickly answer your own BMad questions -sidebar: - order: 4 ---- - -## Start Here: BMad-Help - -**The fastest way to get answers about BMad is `/bmad-help`.** This intelligent guide will answer upwards of 80% of all questions and is available to you directly in your IDE as you work. - -BMad-Help is more than a lookup tool — it: -- **Inspects your project** to see what's already been completed -- **Understands natural language** — ask questions in plain English -- **Varies based on your installed modules** — shows relevant options -- **Auto-runs after workflows** — tells you exactly what to do next -- **Recommends the first required task** — no guessing where to start - -### How to Use BMad-Help - -Run it with just the slash command: - -``` -/bmad-help -``` - -Or combine it with a natural language query: - -``` -/bmad-help I have a SaaS idea and know all the features. Where do I start? -/bmad-help What are my options for UX design? -/bmad-help I'm stuck on the PRD workflow -/bmad-help Show me what's been done so far -``` - -BMad-Help responds with: -- What's recommended for your situation -- What the first required task is -- What the rest of the process looks like - ---- - -## When to Use This Guide - -Use this section when: -- You want to understand BMad's architecture or internals -- You need answers outside of what BMad-Help provides -- You're researching BMad before installing -- You want to explore the source code directly - -## Steps - -### 1. Choose Your Source - -| Source | Best For | Examples | -| -------------------- | ----------------------------------------- | ---------------------------- | -| **`_bmad` folder** | How BMad works—agents, workflows, prompts | "What does the PM agent do?" | -| **Full GitHub repo** | History, installer, architecture | "What changed in v6?" | -| **`llms-full.txt`** | Quick overview from docs | "Explain BMad's four phases" | - -The `_bmad` folder is created when you install BMad. If you don't have it yet, clone the repo instead. - -### 2. Point Your AI at the Source - -**If your AI can read files (Claude Code, Cursor, etc.):** - -- **BMad installed:** Point at the `_bmad` folder and ask directly -- **Want deeper context:** Clone the [full repo](https://github.com/bmad-code-org/BMAD-METHOD) - -**If you use ChatGPT or Claude.ai:** - -Fetch `llms-full.txt` into your session: - -```text -https://bmad-code-org.github.io/BMAD-METHOD/llms-full.txt -``` - - -### 3. Ask Your Question - -:::note[Example] -**Q:** "Tell me the fastest way to build something with BMad" - -**A:** Use Quick Flow: Run `quick-spec` to write a technical specification, then `quick-dev` to implement it—skipping the full planning phases. -::: - -## What You Get - -Direct answers about BMad—how agents work, what workflows do, why things are structured the way they are—without waiting for someone else to respond. - -## Tips - -- **Verify surprising answers** — LLMs occasionally get things wrong. Check the source file or ask on Discord. -- **Be specific** — "What does step 3 of the PRD workflow do?" beats "How does PRD work?" - -## Still Stuck? - -Tried the LLM approach and still need help? You now have a much better question to ask. - -| Channel | Use For | -| ------------------------- | ------------------------------------------- | -| `#bmad-method-help` | Quick questions (real-time chat) | -| `help-requests` forum | Detailed questions (searchable, persistent) | -| `#suggestions-feedback` | Ideas and feature requests | -| `#report-bugs-and-issues` | Bug reports | - -**Discord:** [discord.gg/gk8jAdXWmj](https://discord.gg/gk8jAdXWmj) - -**GitHub Issues:** [github.com/bmad-code-org/BMAD-METHOD/issues](https://github.com/bmad-code-org/BMAD-METHOD/issues) (for clear bugs) - -*You!* - *Stuck* - *in the queue—* - *waiting* - *for who?* - -*The source* - *is there,* - *plain to see!* - -*Point* - *your machine.* - *Set it free.* - -*It reads.* - *It speaks.* - *Ask away—* - -*Why wait* - *for tomorrow* - *when you have* - *today?* - -*—Claude* diff --git a/docs/how-to/install-bmad.md b/docs/how-to/install-bmad.md deleted file mode 100644 index 177c2c884..000000000 --- a/docs/how-to/install-bmad.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: "How to Install BMad" -description: Step-by-step guide to installing BMad in your project -sidebar: - order: 1 ---- - -Use the `npx bmad-method install` command to set up BMad in your project with your choice of modules and AI tools. - -If you want to use a non interactive installer and provide all install options on the command line, see [this guide](./non-interactive-installation.md). - -## When to Use This - -- Starting a new project with BMad -- Adding BMad to an existing codebase -- Update the existing BMad Installation - -:::note[Prerequisites] -- **Node.js** 20+ (required for the installer) -- **Git** (recommended) -- **AI tool** (Claude Code, Cursor, or similar) -::: - -## Steps - -### 1. Run the Installer - -```bash -npx bmad-method install -``` - -:::tip[Bleeding edge] -To install the latest from the main branch (may be unstable): -```bash -npx github:bmad-code-org/BMAD-METHOD install -``` -::: - -### 2. Choose Installation Location - -The installer will ask where to install BMad files: - -- Current directory (recommended for new projects if you created the directory yourself and ran from within the directory) -- Custom path - -### 3. Select Your AI Tools - -Pick which AI tools you use: - -- Claude Code -- Cursor -- Others - -Each tool has its own way of integrating commands. The installer creates tiny prompt files to activate workflows and agents — it just puts them where your tool expects to find them. - -### 4. Choose Modules - -The installer shows available modules. Select whichever ones you need — most users just want **BMad Method** (the software development module). - -### 5. Follow the Prompts - -The installer guides you through the rest — custom content, settings, etc. - -## What You Get - -```text -your-project/ -├── _bmad/ -│ ├── bmm/ # Your selected modules -│ │ └── config.yaml # Module settings (if you ever need to change them) -│ ├── core/ # Required core module -│ └── ... -├── _bmad-output/ # Generated artifacts -├── .claude/ # Claude Code commands (if using Claude Code) -└── .kiro/ # Kiro steering files (if using Kiro) -``` - -## Verify Installation - -Run `/bmad-help` to verify everything works and see what to do next. - -**BMad-Help is your intelligent guide** that will: -- Confirm your installation is working -- Show what's available based on your installed modules -- Recommend your first step - -You can also ask it questions: -``` -/bmad-help I just installed, what should I do first? -/bmad-help What are my options for a SaaS project? -``` - -## Troubleshooting - -**Installer throws an error** — Copy-paste the output into your AI assistant and let it figure it out. - -**Installer worked but something doesn't work later** — Your AI needs BMad context to help. See [How to Get Answers About BMad](./get-answers-about-bmad.md) for how to point your AI at the right sources. diff --git a/docs/how-to/non-interactive-installation.md b/docs/how-to/non-interactive-installation.md deleted file mode 100644 index fa7a1e7b1..000000000 --- a/docs/how-to/non-interactive-installation.md +++ /dev/null @@ -1,171 +0,0 @@ ---- -title: Non-Interactive Installation -description: Install BMad using command-line flags for CI/CD pipelines and automated deployments -sidebar: - order: 2 ---- - -Use command-line flags to install BMad non-interactively. This is useful for: - -## When to Use This - -- Automated deployments and CI/CD pipelines -- Scripted installations -- Batch installations across multiple projects -- Quick installations with known configurations - -:::note[Prerequisites] -Requires [Node.js](https://nodejs.org) v20+ and `npx` (included with npm). -::: - -## Available Flags - -### Installation Options - -| Flag | Description | Example | -|------|-------------|---------| -| `--directory ` | Installation directory | `--directory ~/projects/myapp` | -| `--modules ` | Comma-separated module IDs | `--modules bmm,bmb` | -| `--tools ` | Comma-separated tool/IDE IDs (use `none` to skip) | `--tools claude-code,cursor` or `--tools none` | -| `--custom-content ` | Comma-separated paths to custom modules | `--custom-content ~/my-module,~/another-module` | -| `--action ` | Action for existing installations: `install` (default), `update`, `quick-update`, or `compile-agents` | `--action quick-update` | - -### Core Configuration - -| Flag | Description | Default | -|------|-------------|---------| -| `--user-name ` | Name for agents to use | System username | -| `--communication-language ` | Agent communication language | English | -| `--document-output-language ` | Document output language | English | -| `--output-folder ` | Output folder path | _bmad-output | - -### Other Options - -| Flag | Description | -|------|-------------| -| `-y, --yes` | Accept all defaults and skip prompts | -| `-d, --debug` | Enable debug output for manifest generation | - -## Module IDs - -Available module IDs for the `--modules` flag: - -- `bmm` — BMad Method Master -- `bmb` — BMad Builder - -Check the [BMad registry](https://github.com/bmad-code-org) for available external modules. - -## Tool/IDE IDs - -Available tool IDs for the `--tools` flag: - -**Preferred:** `claude-code`, `cursor` - -Run `npx bmad-method install` interactively once to see the full current list of supported tools, or check the [platform codes configuration](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/tools/cli/installers/lib/ide/platform-codes.yaml). - -## Installation Modes - -| Mode | Description | Example | -|------|-------------|---------| -| Fully non-interactive | Provide all flags to skip all prompts | `npx bmad-method install --directory . --modules bmm --tools claude-code --yes` | -| Semi-interactive | Provide some flags; BMad prompts for the rest | `npx bmad-method install --directory . --modules bmm` | -| Defaults only | Accept all defaults with `-y` | `npx bmad-method install --yes` | -| Without tools | Skip tool/IDE configuration | `npx bmad-method install --modules bmm --tools none` | - -## Examples - -### CI/CD Pipeline Installation - -```bash -#!/bin/bash -# install-bmad.sh - -npx bmad-method install \ - --directory "${GITHUB_WORKSPACE}" \ - --modules bmm \ - --tools claude-code \ - --user-name "CI Bot" \ - --communication-language English \ - --document-output-language English \ - --output-folder _bmad-output \ - --yes -``` - -### Update Existing Installation - -```bash -npx bmad-method install \ - --directory ~/projects/myapp \ - --action update \ - --modules bmm,bmb,custom-module -``` - -### Quick Update (Preserve Settings) - -```bash -npx bmad-method install \ - --directory ~/projects/myapp \ - --action quick-update -``` - -### Installation with Custom Content - -```bash -npx bmad-method install \ - --directory ~/projects/myapp \ - --modules bmm \ - --custom-content ~/my-custom-module,~/another-module \ - --tools claude-code -``` - -## What You Get - -- A fully configured `_bmad/` directory in your project -- Compiled agents and workflows for your selected modules and tools -- A `_bmad-output/` folder for generated artifacts - -## Validation and Error Handling - -BMad validates all provided flags: - -- **Directory** — Must be a valid path with write permissions -- **Modules** — Warns about invalid module IDs (but won't fail) -- **Tools** — Warns about invalid tool IDs (but won't fail) -- **Custom Content** — Each path must contain a valid `module.yaml` file -- **Action** — Must be one of: `install`, `update`, `quick-update`, `compile-agents` - -Invalid values will either: -1. Show an error and exit (for critical options like directory) -2. Show a warning and skip (for optional items like custom content) -3. Fall back to interactive prompts (for missing required values) - -:::tip[Best Practices] -- Use absolute paths for `--directory` to avoid ambiguity -- Test flags locally before using in CI/CD pipelines -- Combine with `-y` for truly unattended installations -- Use `--debug` if you encounter issues during installation -::: - -## Troubleshooting - -### Installation fails with "Invalid directory" - -- The directory path must exist (or its parent must exist) -- You need write permissions -- The path must be absolute or correctly relative to the current directory - -### Module not found - -- Verify the module ID is correct -- External modules must be available in the registry - -### Custom content path invalid - -Ensure each custom content path: -- Points to a directory -- Contains a `module.yaml` file in the root -- Has a `code` field in the `module.yaml` - -:::note[Still stuck?] -Run with `--debug` for detailed output, try interactive mode to isolate the issue, or report at . -::: diff --git a/docs/how-to/project-context.md b/docs/how-to/project-context.md deleted file mode 100644 index 105906098..000000000 --- a/docs/how-to/project-context.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -title: "Manage Project Context" -description: Create and maintain project-context.md to guide AI agents -sidebar: - order: 7 ---- - -Use the `project-context.md` file to ensure AI agents follow your project's technical preferences and implementation rules throughout all workflows. - -:::note[Prerequisites] -- BMad Method installed -- Understanding of your project's technology stack and conventions -::: - -## When to Use This - -- You have strong technical preferences before starting architecture -- You've completed architecture and want to capture decisions for implementation -- You're working on an existing codebase with established patterns -- You notice agents making inconsistent decisions across stories - -## Step 1: Choose Your Approach - -**Manual creation** — Best when you know exactly what rules you want to document - -**Generate after architecture** — Best for capturing decisions made during solutioning - -**Generate for existing projects** — Best for discovering patterns in existing codebases - -## Step 2: Create the File - -### Option A: Manual Creation - -Create the file at `_bmad-output/project-context.md`: - -```bash -mkdir -p _bmad-output -touch _bmad-output/project-context.md -``` - -Add your technology stack and implementation rules: - -```markdown ---- -project_name: 'MyProject' -user_name: 'YourName' -date: '2026-02-15' -sections_completed: ['technology_stack', 'critical_rules'] ---- - -# Project Context for AI Agents - -## Technology Stack & Versions - -- Node.js 20.x, TypeScript 5.3, React 18.2 -- State: Zustand -- Testing: Vitest, Playwright -- Styling: Tailwind CSS - -## Critical Implementation Rules - -**TypeScript:** -- Strict mode enabled, no `any` types -- Use `interface` for public APIs, `type` for unions - -**Code Organization:** -- Components in `/src/components/` with co-located tests -- API calls use `apiClient` singleton — never fetch directly - -**Testing:** -- Unit tests focus on business logic -- Integration tests use MSW for API mocking -``` - -### Option B: Generate After Architecture - -Run the workflow in a fresh chat: - -```bash -/bmad-bmm-generate-project-context -``` - -The workflow scans your architecture document and project files to generate a context file capturing the decisions made. - -### Option C: Generate for Existing Projects - -For existing projects, run: - -```bash -/bmad-bmm-generate-project-context -``` - -The workflow analyzes your codebase to identify conventions, then generates a context file you can review and refine. - -## Step 3: Verify Content - -Review the generated file and ensure it captures: - -- Correct technology versions -- Your actual conventions (not generic best practices) -- Rules that prevent common mistakes -- Framework-specific patterns - -Edit manually to add anything missing or remove inaccuracies. - -## What You Get - -A `project-context.md` file that: - -- Ensures all agents follow the same conventions -- Prevents inconsistent decisions across stories -- Captures architecture decisions for implementation -- Serves as a reference for your project's patterns and rules - -## Tips - -:::tip[Focus on the Unobvious] -Document patterns agents might miss such as "Use JSDoc style comments on every public class, function and variable", not universal practices like "use meaningful variable names" which LLMs know at this point. -::: - -:::tip[Keep It Lean] -This file is loaded by every implementation workflow. Long files waste context. Do not include content that only applies to narrow scope or specific stories or features. -::: - -:::tip[Update as Needed] -Edit manually when patterns change, or re-generate after significant architecture changes. -::: - -:::tip[Works for All Project Types] -Just as useful for Quick Flow as for full BMad Method projects. -::: - -## Next Steps - -- [**Project Context Explanation**](../explanation/project-context.md) — Learn more about how it works -- [**Workflow Map**](../reference/workflow-map.md) — See which workflows load project context diff --git a/docs/how-to/quick-fixes.md b/docs/how-to/quick-fixes.md deleted file mode 100644 index 76ee5ebe0..000000000 --- a/docs/how-to/quick-fixes.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -title: "Quick Fixes" -description: How to make quick fixes and ad-hoc changes -sidebar: - order: 5 ---- - -Use the **DEV agent** directly for bug fixes, refactorings, or small targeted changes that don't require the full BMad Method or Quick Flow. - -## When to Use This - -- Bug fixes with a clear, known cause -- Small refactorings (rename, extract, restructure) contained within a few files -- Minor feature tweaks or configuration changes -- Exploratory work to understand an unfamiliar codebase - -:::note[Prerequisites] -- BMad Method installed (`npx bmad-method install`) -- An AI-powered IDE (Claude Code, Cursor, or similar) -::: - -## Choose Your Approach - -| Situation | Agent | Why | -| --- | --- | --- | -| Fix a specific bug or make a small, scoped change | **DEV agent** | Jumps straight into implementation without planning overhead | -| Change touches several files or you want a written plan first | **Quick Flow Solo Dev** | Creates a quick-spec before implementation so the agent stays aligned to your standards | - -If you are unsure, start with the DEV agent. You can always escalate to Quick Flow if the change grows. - -## Steps - -### 1. Load the DEV Agent - -Start a **fresh chat** in your AI IDE and load the DEV agent with its slash command: - -```text -/bmad-agent-bmm-dev -``` - -This loads the agent's persona and capabilities into the session. If you decide you need Quick Flow instead, load the **Quick Flow Solo Dev** agent in a fresh chat: - -```text -/bmad-agent-bmm-quick-flow-solo-dev -``` - -Once the Solo Dev agent is loaded, describe your change and ask it to create a **quick-spec**. The agent drafts a lightweight spec capturing what you want to change and how. After you approve the quick-spec, tell the agent to start the **Quick Flow dev cycle** -- it will implement the change, run tests, and perform a self-review, all guided by the spec you just approved. - -:::tip[Fresh Chats] -Always start a new chat session when loading an agent. Reusing a session from a previous workflow can cause context conflicts. -::: - -### 2. Describe the Change - -Tell the agent what you need in plain language. Be specific about the problem and, if you know it, where the relevant code lives. - -:::note[Example Prompts] -**Bug fix** -- "Fix the login validation bug that allows empty passwords. The validation logic is in `src/auth/validate.ts`." - -**Refactoring** -- "Refactor the UserService to use async/await instead of callbacks." - -**Configuration change** -- "Update the CI pipeline to cache node_modules between runs." - -**Dependency update** -- "Upgrade the express dependency to the latest v5 release and fix any breaking changes." -::: - -You don't need to provide every detail. The agent will read the relevant source files and ask clarifying questions when needed. - -### 3. Let the Agent Work - -The agent will: - -- Read and analyze the relevant source files -- Propose a solution and explain its reasoning -- Implement the change across the affected files -- Run your project's test suite if one exists - -If your project has tests, the agent runs them automatically after making changes and iterates until tests pass. For projects without a test suite, verify the change manually (run the app, hit the endpoint, check the output). - -### 4. Review and Verify - -Before committing, review what changed: - -- Read through the diff to confirm the change matches your intent -- Run the application or tests yourself to double-check -- If something looks wrong, tell the agent what to fix -- it can iterate in the same session - -Once satisfied, commit the changes with a clear message describing the fix. - -:::caution[If Something Breaks] -If a committed change causes unexpected issues, use `git revert HEAD` to undo the last commit cleanly. Then start a fresh chat with the DEV agent to try a different approach. -::: - -## Learning Your Codebase - -The DEV agent is also useful for exploring unfamiliar code. Load it in a fresh chat and ask questions: - -:::note[Example Prompts] -"Explain how the authentication system works in this codebase." - -"Show me where error handling happens in the API layer." - -"What does the `ProcessOrder` function do and what calls it?" -::: - -Use the agent to learn about your project, understand how components connect, and explore unfamiliar areas before making changes. - -## What You Get - -- Modified source files with the fix or refactoring applied -- Passing tests (if your project has a test suite) -- A clean commit describing the change - -No planning artifacts are produced -- that's the point of this approach. - -## When to Upgrade to Formal Planning - -Consider using [Quick Flow](../explanation/quick-flow.md) or the full BMad Method when: - -- The change affects multiple systems or requires coordinated updates across many files -- You are unsure about the scope and need a spec to think it through -- The fix keeps growing in complexity as you work on it -- You need documentation or architectural decisions recorded for the team diff --git a/docs/how-to/shard-large-documents.md b/docs/how-to/shard-large-documents.md deleted file mode 100644 index b10c64fb8..000000000 --- a/docs/how-to/shard-large-documents.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: "Document Sharding Guide" -description: Split large markdown files into smaller organized files for better context management -sidebar: - order: 8 ---- - -Use the `shard-doc` tool if you need to split large markdown files into smaller, organized files for better context management. - -:::caution[Deprecated] -This is no longer recommended, and soon with updated workflows and most major LLMs and tools supporting subprocesses this will be unnecessary. -::: - -## When to Use This - -Only use this if you notice your chosen tool / model combination is failing to load and read all the documents as input when needed. - -## What is Document Sharding? - -Document sharding splits large markdown files into smaller, organized files based on level 2 headings (`## Heading`). - -### Architecture - -```text -Before Sharding: -_bmad-output/planning-artifacts/ -└── PRD.md (large 50k token file) - -After Sharding: -_bmad-output/planning-artifacts/ -└── prd/ - ├── index.md # Table of contents with descriptions - ├── overview.md # Section 1 - ├── user-requirements.md # Section 2 - ├── technical-requirements.md # Section 3 - └── ... # Additional sections -``` - -## Steps - -### 1. Run the Shard-Doc Tool - -```bash -/bmad-shard-doc -``` - -### 2. Follow the Interactive Process - -```text -Agent: Which document would you like to shard? -User: docs/PRD.md - -Agent: Default destination: docs/prd/ - Accept default? [y/n] -User: y - -Agent: Sharding PRD.md... - ✓ Created 12 section files - ✓ Generated index.md - ✓ Complete! -``` - -## How Workflow Discovery Works - -BMad workflows use a **dual discovery system**: - -1. **Try whole document first** - Look for `document-name.md` -2. **Check for sharded version** - Look for `document-name/index.md` -3. **Priority rule** - Whole document takes precedence if both exist - remove the whole document if you want the sharded to be used instead - -## Workflow Support - -All BMM workflows support both formats: - -- Whole documents -- Sharded documents -- Automatic detection -- Transparent to user diff --git a/docs/how-to/upgrade-to-v6.md b/docs/how-to/upgrade-to-v6.md deleted file mode 100644 index 882640a69..000000000 --- a/docs/how-to/upgrade-to-v6.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: "How to Upgrade to v6" -description: Migrate from BMad v4 to v6 -sidebar: - order: 3 ---- - -Use the BMad installer to upgrade from v4 to v6, which includes automatic detection of legacy installations and migration assistance. - -## When to Use This - -- You have BMad v4 installed (`.bmad-method` folder) -- You want to migrate to the new v6 architecture -- You have existing planning artifacts to preserve - -:::note[Prerequisites] -- Node.js 20+ -- Existing BMad v4 installation -::: - -## Steps - -### 1. Run the Installer - -Follow the [Installer Instructions](./install-bmad.md). - -### 2. Handle Legacy Installation - -When v4 is detected, you can: - -- Allow the installer to back up and remove `.bmad-method` -- Exit and handle cleanup manually - -If you named your bmad method folder something else - you will need to manually remove the folder yourself. - -### 3. Clean Up IDE Commands - -Manually remove legacy v4 IDE commands - for example if you have claude, look for any nested folders that start with bmad and remove them: - -- `.claude/commands/BMad/agents` -- `.claude/commands/BMad/tasks` - -### 4. Migrate Planning Artifacts - -**If you have planning documents (Brief/PRD/UX/Architecture):** - -Move them to `_bmad-output/planning-artifacts/` with descriptive names: - -- Include `PRD` in filename for PRD documents -- Include `brief`, `architecture`, or `ux-design` accordingly -- Sharded documents can be in named subfolders - -**If you're mid-planning:** Consider restarting with v6 workflows. Use your existing documents as inputs—the new progressive discovery workflows with web search and IDE plan mode produce better results. - -### 5. Migrate In-Progress Development - -If you have stories created or implemented: - -1. Complete the v6 installation -2. Place `epics.md` or `epics/epic*.md` in `_bmad-output/planning-artifacts/` -3. Run the Scrum Master's `sprint-planning` workflow -4. Tell the SM which epics/stories are already complete - -## What You Get - -**v6 unified structure:** - -```text -your-project/ -├── _bmad/ # Single installation folder -│ ├── _config/ # Your customizations -│ │ └── agents/ # Agent customization files -│ ├── core/ # Universal core framework -│ ├── bmm/ # BMad Method module -│ ├── bmb/ # BMad Builder -│ └── cis/ # Creative Intelligence Suite -└── _bmad-output/ # Output folder (was doc folder in v4) -``` - -## Module Migration - -| v4 Module | v6 Status | -| ----------------------------- | ----------------------------------------- | -| `.bmad-2d-phaser-game-dev` | Integrated into BMGD Module | -| `.bmad-2d-unity-game-dev` | Integrated into BMGD Module | -| `.bmad-godot-game-dev` | Integrated into BMGD Module | -| `.bmad-infrastructure-devops` | Deprecated — new DevOps agent coming soon | -| `.bmad-creative-writing` | Not adapted — new v6 module coming soon | - -## Key Changes - -| Concept | v4 | v6 | -| ------------- | ------------------------------------- | ------------------------------------ | -| **Core** | `_bmad-core` was actually BMad Method | `_bmad/core/` is universal framework | -| **Method** | `_bmad-method` | `_bmad/bmm/` | -| **Config** | Modified files directly | `config.yaml` per module | -| **Documents** | Sharded or unsharded required setup | Fully flexible, auto-scanned | diff --git a/docs/index.md b/docs/index.md deleted file mode 100644 index 8d414bbbe..000000000 --- a/docs/index.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: Welcome to the BMad Method -description: AI-driven development framework with specialized agents, guided workflows, and intelligent planning ---- - -The BMad Method (**B**uild **M**ore **A**rchitect **D**reams) is an AI-driven development framework module within the BMad Method Ecosystem that helps you build software through the whole process from ideation and planning all the way through agentic implementation. It provides specialized AI agents, guided workflows, and intelligent planning that adapts to your project's complexity, whether you're fixing a bug or building an enterprise platform. - -If you're comfortable working with AI coding assistants like Claude, Cursor, or GitHub Copilot, you're ready to get started. - -:::note[🚀 V6 is Here and We're Just Getting Started!] -Skills Architecture, BMad Builder v1, Dev Loop Automation, and so much more in the works. **[Check out the Roadmap →](/roadmap/)** -::: - -## New Here? Start with a Tutorial - -The fastest way to understand BMad is to try it. - -- **[Get Started with BMad](./tutorials/getting-started.md)** — Install and understand how BMad works -- **[Workflow Map](./reference/workflow-map.md)** — Visual overview of BMM phases, workflows, and context management - -:::tip[Just Want to Dive In?] -Install BMad and run `/bmad-help` — it will guide you through everything based on your project and installed modules. -::: - -## How to Use These Docs - -These docs are organized into four sections based on what you're trying to do: - -| Section | Purpose | -| ----------------- | ---------------------------------------------------------------------------------------------------------- | -| **Tutorials** | Learning-oriented. Step-by-step guides that walk you through building something. Start here if you're new. | -| **How-To Guides** | Task-oriented. Practical guides for solving specific problems. "How do I customize an agent?" lives here. | -| **Explanation** | Understanding-oriented. Deep dives into concepts and architecture. Read when you want to know *why*. | -| **Reference** | Information-oriented. Technical specifications for agents, workflows, and configuration. | - -## Extend and Customize - -Want to expand BMad with your own agents, workflows, or modules? The **[BMad Builder](https://bmad-builder-docs.bmad-method.org/)** provides the framework and tools for creating custom extensions, whether you're adding new capabilities to BMad or building entirely new modules from scratch. - -## What You'll Need - -BMad works with any AI coding assistant that supports custom system prompts or project context. Popular options include: - -- **[Claude Code](https://code.claude.com)** — Anthropic's CLI tool (recommended) -- **[Cursor](https://cursor.sh)** — AI-first code editor -- **[Codex CLI](https://github.com/openai/codex)** — OpenAI's terminal coding agent - -You should be comfortable with basic software development concepts like version control, project structure, and agile workflows. No prior experience with BMad-style agent systems is required—that's what these docs are for. - -## Join the Community - -Get help, share what you're building, or contribute to BMad: - -- **[Discord](https://discord.gg/gk8jAdXWmj)** — Chat with other BMad users, ask questions, share ideas -- **[GitHub](https://github.com/bmad-code-org/BMAD-METHOD)** — Source code, issues, and contributions -- **[YouTube](https://www.youtube.com/@BMadCode)** — Video tutorials and walkthroughs - -## Next Step - -Ready to dive in? **[Get Started with BMad](./tutorials/getting-started.md)** and build your first project. diff --git a/docs/reference/agents.md b/docs/reference/agents.md deleted file mode 100644 index 779f0b96e..000000000 --- a/docs/reference/agents.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Agents -description: Default BMM agents with their menu triggers and primary workflows -sidebar: - order: 2 ---- - -## Default Agents - -This page lists the default BMM (Agile suite) agents that install with BMad Method, along with their menu triggers and primary workflows. - -## Notes - -- Triggers are the short menu codes (e.g., `CP`) and fuzzy matches shown in each agent menu. -- Slash commands are generated separately. See [Commands](./commands.md) for the slash command list and where they are defined. -- QA (Quinn) is the lightweight test automation agent in BMM. The full Test Architect (TEA) lives in its own module. - -| Agent | Triggers | Primary workflows | -| --------------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------- | -| Analyst (Mary) | `BP`, `RS`, `CB`, `DP` | Brainstorm Project, Research, Create Brief, Document Project | -| Product Manager (John) | `CP`, `VP`, `EP`, `CE`, `IR`, `CC` | Create/Validate/Edit PRD, Create Epics and Stories, Implementation Readiness, Correct Course | -| Architect (Winston) | `CA`, `IR` | Create Architecture, Implementation Readiness | -| Scrum Master (Bob) | `SP`, `CS`, `ER`, `CC` | Sprint Planning, Create Story, Epic Retrospective, Correct Course | -| Developer (Amelia) | `DS`, `CR` | Dev Story, Code Review | -| QA Engineer (Quinn) | `QA` | Automate (generate tests for existing features) | -| Quick Flow Solo Dev (Barry) | `QS`, `QD`, `CR` | Quick Spec, Quick Dev, Code Review | -| UX Designer (Sally) | `CU` | Create UX Design | -| Technical Writer (Paige) | `DP`, `WD`, `US`, `MG`, `VD`, `EC` | Document Project, Write Document, Update Standards, Mermaid Generate, Validate Doc, Explain Concept | diff --git a/docs/reference/commands.md b/docs/reference/commands.md deleted file mode 100644 index af4f1f496..000000000 --- a/docs/reference/commands.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -title: Commands -description: Reference for BMad slash commands — what they are, how they work, and where to find them. -sidebar: - order: 3 ---- - -Slash commands are pre-built prompts that load agents, run workflows, or execute tasks inside your IDE. The BMad installer generates them from your installed modules at install time. If you later add, remove, or change modules, re-run the installer to keep commands in sync (see [Troubleshooting](#troubleshooting)). - -## Commands vs. Agent Menu Triggers - -BMad offers two ways to start work, and they serve different purposes. - -| Mechanism | How you invoke it | What happens | -| --- | --- | --- | -| **Slash command** | Type `/bmad-...` in your IDE | Directly loads an agent, runs a workflow, or executes a task | -| **Agent menu trigger** | Load an agent first, then type a short code (e.g. `DS`) | The agent interprets the code and starts the matching workflow while staying in character | - -Agent menu triggers require an active agent session. Use slash commands when you know which workflow you want. Use triggers when you are already working with an agent and want to switch tasks without leaving the conversation. - -## How Commands Are Generated - -When you run `npx bmad-method install`, the installer reads the manifests for every selected module and writes one command file per agent, workflow, task, and tool. Each file is a short markdown prompt that instructs the AI to load the corresponding source file and follow its instructions. - -The installer uses templates for each command type: - -| Command type | What the generated file does | -| --- | --- | -| **Agent launcher** | Loads the agent persona file, activates its menu, and stays in character | -| **Workflow command** | Loads the workflow engine (`workflow.xml`) and passes the workflow config | -| **Task command** | Loads a standalone task file and follows its instructions | -| **Tool command** | Loads a standalone tool file and follows its instructions | - -:::note[Re-running the installer] -If you add or remove modules, run the installer again. It regenerates all command files to match your current module selection. -::: - -## Where Command Files Live - -The installer writes command files into an IDE-specific directory inside your project. The exact path depends on which IDE you selected during installation. - -| IDE / CLI | Command directory | -| --- | --- | -| Claude Code | `.claude/commands/` | -| Cursor | `.cursor/commands/` | -| Windsurf | `.windsurf/workflows/` | -| Other IDEs | See the installer output for the target path | - -All IDEs receive a flat set of command files in their command directory. For example, a Claude Code installation looks like: - -```text -.claude/commands/ -├── bmad-agent-bmm-dev.md -├── bmad-agent-bmm-pm.md -├── bmad-bmm-create-prd.md -├── bmad-editorial-review-prose.md -├── bmad-help.md -└── ... -``` - -The filename determines the slash command name in your IDE. For example, the file `bmad-agent-bmm-dev.md` registers the command `/bmad-agent-bmm-dev`. - -## How to Discover Your Commands - -Type `/bmad` in your IDE and use autocomplete to browse available commands. - -Run `/bmad-help` for context-aware guidance on your next step. - -:::tip[Quick discovery] -The generated command folders in your project are the canonical list. Open them in your file explorer to see every command with its description. -::: - -## Command Categories - -### Agent Commands - -Agent commands load a specialized AI persona with a defined role, communication style, and menu of workflows. Once loaded, the agent stays in character and responds to menu triggers. - -| Example command | Agent | Role | -| --- | --- | --- | -| `/bmad-agent-bmm-dev` | Amelia (Developer) | Implements stories with strict adherence to specs | -| `/bmad-agent-bmm-pm` | John (Product Manager) | Creates and validates PRDs | -| `/bmad-agent-bmm-architect` | Winston (Architect) | Designs system architecture | -| `/bmad-agent-bmm-sm` | Bob (Scrum Master) | Manages sprints and stories | - -See [Agents](./agents.md) for the full list of default agents and their triggers. - -### Workflow Commands - -Workflow commands run a structured, multi-step process without loading an agent persona first. They load the workflow engine and pass a specific workflow configuration. - -| Example command | Purpose | -| --- | --- | -| `/bmad-bmm-create-prd` | Create a Product Requirements Document | -| `/bmad-bmm-create-architecture` | Design system architecture | -| `/bmad-bmm-dev-story` | Implement a story | -| `/bmad-bmm-code-review` | Run a code review | -| `/bmad-bmm-quick-spec` | Define an ad-hoc change (Quick Flow) | - -See [Workflow Map](./workflow-map.md) for the complete workflow reference organized by phase. - -### Task and Tool Commands - -Tasks and tools are standalone operations that do not require an agent or workflow context. - -#### BMad-Help: Your Intelligent Guide - -**`/bmad-help`** is your primary interface for discovering what to do next. It's not just a lookup tool — it's an intelligent assistant that: - -- **Inspects your project** to see what's already been done -- **Understands natural language queries** — ask questions in plain English -- **Varies by installed modules** — shows options based on what you have -- **Auto-invokes after workflows** — every workflow ends with clear next steps -- **Recommends the first required task** — no guessing where to start - -**Examples:** - -``` -/bmad-help -/bmad-help I have a SaaS idea and know all the features. Where do I start? -/bmad-help What are my options for UX design? -/bmad-help I'm stuck on the PRD workflow -``` - -#### Other Tasks and Tools - -| Example command | Purpose | -| --- | --- | -| `/bmad-shard-doc` | Split a large markdown file into smaller sections | -| `/bmad-index-docs` | Index project documentation | -| `/bmad-editorial-review-prose` | Review document prose quality | - -## Naming Convention - -Command names follow a predictable pattern. - -| Pattern | Meaning | Example | -| --- | --- | --- | -| `bmad-agent--` | Agent launcher | `bmad-agent-bmm-dev` | -| `bmad--` | Workflow command | `bmad-bmm-create-prd` | -| `bmad-` | Core task or tool | `bmad-help` | - -Module codes: `bmm` (Agile suite), `bmb` (Builder), `tea` (Test Architect), `cis` (Creative Intelligence), `gds` (Game Dev Studio). See [Modules](./modules.md) for descriptions. - -## Troubleshooting - -**Commands not appearing after install.** Restart your IDE or reload the window. Some IDEs cache the command list and require a refresh to pick up new files. - -**Expected commands are missing.** The installer only generates commands for modules you selected. Run `npx bmad-method install` again and verify your module selection. Check that the command files exist in the expected directory. - -**Commands from a removed module still appear.** The installer does not delete old command files automatically. Remove the stale files from your IDE's command directory, or delete the entire command directory and re-run the installer for a clean set. diff --git a/docs/reference/modules.md b/docs/reference/modules.md deleted file mode 100644 index 6bdc64190..000000000 --- a/docs/reference/modules.md +++ /dev/null @@ -1,76 +0,0 @@ ---- -title: Official Modules -description: Add-on modules for building custom agents, creative intelligence, game development, and testing -sidebar: - order: 4 ---- - -BMad extends through official modules that you select during installation. These add-on modules provide specialized agents, workflows, and tasks for specific domains beyond the built-in core and BMM (Agile suite). - -:::tip[Installing Modules] -Run `npx bmad-method install` and select the modules you want. The installer handles downloading, configuration, and IDE integration automatically. -::: - -## BMad Builder - -Create custom agents, workflows, and domain-specific modules with guided assistance. BMad Builder is the meta-module for extending the framework itself. - -- **Code:** `bmb` -- **npm:** [`bmad-builder`](https://www.npmjs.com/package/bmad-builder) -- **GitHub:** [bmad-code-org/bmad-builder](https://github.com/bmad-code-org/bmad-builder) - -**Provides:** - -- Agent Builder -- create specialized AI agents with custom expertise and tool access -- Workflow Builder -- design structured processes with steps and decision points -- Module Builder -- package agents and workflows into shareable, publishable modules -- Interactive setup with YAML configuration and npm publishing support - -## Creative Intelligence Suite - -AI-powered tools for structured creativity, ideation, and innovation during early-stage development. The suite provides multiple agents that facilitate brainstorming, design thinking, and problem-solving using proven frameworks. - -- **Code:** `cis` -- **npm:** [`bmad-creative-intelligence-suite`](https://www.npmjs.com/package/bmad-creative-intelligence-suite) -- **GitHub:** [bmad-code-org/bmad-module-creative-intelligence-suite](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite) - -**Provides:** - -- Innovation Strategist, Design Thinking Coach, and Brainstorming Coach agents -- Problem Solver and Creative Problem Solver for systematic and lateral thinking -- Storyteller and Presentation Master for narratives and pitches -- Ideation frameworks including SCAMPER, Reverse Brainstorming, and problem reframing - -## Game Dev Studio - -Structured game development workflows adapted for Unity, Unreal, Godot, and custom engines. Supports rapid prototyping through Quick Flow and full-scale production with epic-driven sprints. - -- **Code:** `gds` -- **npm:** [`bmad-game-dev-studio`](https://www.npmjs.com/package/bmad-game-dev-studio) -- **GitHub:** [bmad-code-org/bmad-module-game-dev-studio](https://github.com/bmad-code-org/bmad-module-game-dev-studio) - -**Provides:** - -- Game Design Document (GDD) generation workflow -- Quick Dev mode for rapid prototyping -- Narrative design support for characters, dialogue, and world-building -- Coverage for 21+ game types with engine-specific architecture guidance - -## Test Architect (TEA) - -Enterprise-grade test strategy, automation guidance, and release gate decisions through an expert agent and nine structured workflows. TEA goes well beyond the built-in QA agent with risk-based prioritization and requirements traceability. - -- **Code:** `tea` -- **npm:** [`bmad-method-test-architecture-enterprise`](https://www.npmjs.com/package/bmad-method-test-architecture-enterprise) -- **GitHub:** [bmad-code-org/bmad-method-test-architecture-enterprise](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise) - -**Provides:** - -- Murat agent (Master Test Architect and Quality Advisor) -- Workflows for test design, ATDD, automation, test review, and traceability -- NFR assessment, CI setup, and framework scaffolding -- P0-P3 prioritization with optional Playwright Utils and MCP integrations - -## Community Modules - -Community modules and a module marketplace are coming. Check the [BMad GitHub organization](https://github.com/bmad-code-org) for updates. diff --git a/docs/reference/testing.md b/docs/reference/testing.md deleted file mode 100644 index 4063ddfe1..000000000 --- a/docs/reference/testing.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -title: Testing Options -description: Comparing the built-in QA agent (Quinn) with the Test Architect (TEA) module for test automation. -sidebar: - order: 5 ---- - -BMad provides two testing paths: a built-in QA agent for fast test generation and an installable Test Architect module for enterprise-grade test strategy. - -## Which Should You Use? - -| Factor | Quinn (Built-in QA) | TEA Module | -| --- | --- | --- | -| **Best for** | Small-medium projects, quick coverage | Large projects, regulated or complex domains | -| **Setup** | Nothing to install -- included in BMM | Install separately via `npx bmad-method install` | -| **Approach** | Generate tests fast, iterate later | Plan first, then generate with traceability | -| **Test types** | API and E2E tests | API, E2E, ATDD, NFR, and more | -| **Strategy** | Happy path + critical edge cases | Risk-based prioritization (P0-P3) | -| **Workflow count** | 1 (Automate) | 9 (design, ATDD, automate, review, trace, and others) | - -:::tip[Start with Quinn] -Most projects should start with Quinn. If you later need test strategy, quality gates, or requirements traceability, install TEA alongside it. -::: - -## Built-in QA Agent (Quinn) - -Quinn is the built-in QA agent in the BMM (Agile suite) module. It generates working tests quickly using your project's existing test framework -- no configuration or additional installation required. - -**Trigger:** `QA` or `bmad-bmm-qa-automate` - -### What Quinn Does - -Quinn runs a single workflow (Automate) that walks through five steps: - -1. **Detect test framework** -- scans `package.json` and existing test files for your framework (Jest, Vitest, Playwright, Cypress, or any standard runner). If none exists, analyzes the project stack and suggests one. -2. **Identify features** -- asks what to test or auto-discovers features in the codebase. -3. **Generate API tests** -- covers status codes, response structure, happy path, and 1-2 error cases. -4. **Generate E2E tests** -- covers user workflows with semantic locators and visible-outcome assertions. -5. **Run and verify** -- executes the generated tests and fixes failures immediately. - -Quinn produces a test summary saved to your project's implementation artifacts folder. - -### Test Patterns - -Generated tests follow a "simple and maintainable" philosophy: - -- **Standard framework APIs only** -- no external utilities or custom abstractions -- **Semantic locators** for UI tests (roles, labels, text rather than CSS selectors) -- **Independent tests** with no order dependencies -- **No hardcoded waits or sleeps** -- **Clear descriptions** that read as feature documentation - -:::note[Scope] -Quinn generates tests only. For code review and story validation, use the Code Review workflow (`CR`) instead. -::: - -### When to Use Quinn - -- Quick test coverage for a new or existing feature -- Beginner-friendly test automation without advanced setup -- Standard test patterns that any developer can read and maintain -- Small-medium projects where comprehensive test strategy is unnecessary - -## Test Architect (TEA) Module - -TEA is a standalone module that provides an expert agent (Murat) and nine structured workflows for enterprise-grade testing. It goes beyond test generation into test strategy, risk-based planning, quality gates, and requirements traceability. - -- **Documentation:** [TEA Module Docs](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/) -- **Install:** `npx bmad-method install` and select the TEA module -- **npm:** [`bmad-method-test-architecture-enterprise`](https://www.npmjs.com/package/bmad-method-test-architecture-enterprise) - -### What TEA Provides - -| Workflow | Purpose | -| --- | --- | -| Test Design | Create a comprehensive test strategy tied to requirements | -| ATDD | Acceptance-test-driven development with stakeholder criteria | -| Automate | Generate tests with advanced patterns and utilities | -| Test Review | Validate test quality and coverage against strategy | -| Traceability | Map tests back to requirements for audit and compliance | -| NFR Assessment | Evaluate non-functional requirements (performance, security) | -| CI Setup | Configure test execution in continuous integration pipelines | -| Framework Scaffolding | Set up test infrastructure and project structure | -| Release Gate | Make data-driven go/no-go release decisions | - -TEA also supports P0-P3 risk-based prioritization and optional integrations with Playwright Utils and MCP tooling. - -### When to Use TEA - -- Projects that require requirements traceability or compliance documentation -- Teams that need risk-based test prioritization across many features -- Enterprise environments with formal quality gates before release -- Complex domains where test strategy must be planned before tests are written -- Projects that have outgrown Quinn's single-workflow approach - -## How Testing Fits into Workflows - -Quinn's Automate workflow appears in Phase 4 (Implementation) of the BMad Method workflow map. A typical sequence: - -1. Implement a story with the Dev workflow (`DS`) -2. Generate tests with Quinn (`QA`) or TEA's Automate workflow -3. Validate implementation with Code Review (`CR`) - -Quinn works directly from source code without loading planning documents (PRD, architecture). TEA workflows can integrate with upstream planning artifacts for traceability. - -For more on where testing fits in the overall process, see the [Workflow Map](./workflow-map.md). diff --git a/docs/reference/workflow-map.md b/docs/reference/workflow-map.md deleted file mode 100644 index 05885a5e1..000000000 --- a/docs/reference/workflow-map.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: "Workflow Map" -description: Visual reference for BMad Method workflow phases and outputs -sidebar: - order: 1 ---- - -The BMad Method (BMM) is a module in the BMad Ecosystem, targeted at following the best practices of context engineering and planning. AI agents work best with clear, structured context. The BMM system builds that context progressively across 4 distinct phases - each phase, and multiple workflows optionally within each phase, produce documents that inform the next, so agents always know what to build and why. - -The rationale and concepts come from agile methodologies that have been used across the industry with great success as a mental framework. - -If at any time you are unsure what to do, the `/bmad-help` command will help you stay on track or know what to do next. You can always refer to this for reference also - but /bmad-help is fully interactive and much quicker if you have already installed the BMad Method. Additionally, if you are using different modules that have extended the BMad Method or added other complementary non-extension modules - the /bmad-help evolves to know all that is available to give you the best in-the-moment advice. - -Final important note: Every workflow below can be run directly with your tool of choice via slash command or by loading an agent first and using the entry from the agents menu. - - - -

- Open diagram in new tab ↗ -

- -## Phase 1: Analysis (Optional) - -Explore the problem space and validate ideas before committing to planning. - -| Workflow | Purpose | Produces | -| ------------------------------- | -------------------------------------------------------------------------- | ------------------------- | -| `bmad-brainstorming` | Brainstorm Project Ideas with guided facilitation of a brainstorming coach | `brainstorming-report.md` | -| `bmad-bmm-research` | Validate market, technical, or domain assumptions | Research findings | -| `bmad-bmm-create-product-brief` | Capture strategic vision | `product-brief.md` | - -## Phase 2: Planning - -Define what to build and for whom. - -| Workflow | Purpose | Produces | -| --------------------------- | ---------------------------------------- | ------------ | -| `bmad-bmm-create-prd` | Define requirements (FRs/NFRs) | `PRD.md` | -| `bmad-bmm-create-ux-design` | Design user experience (when UX matters) | `ux-spec.md` | - -## Phase 3: Solutioning - -Decide how to build it and break work into stories. - -| Workflow | Purpose | Produces | -| ----------------------------------------- | ------------------------------------------ | --------------------------- | -| `bmad-bmm-create-architecture` | Make technical decisions explicit | `architecture.md` with ADRs | -| `bmad-bmm-create-epics-and-stories` | Break requirements into implementable work | Epic files with stories | -| `bmad-bmm-check-implementation-readiness` | Gate check before implementation | PASS/CONCERNS/FAIL decision | - -## Phase 4: Implementation - -Build it, one story at a time. Coming soon, full phase 4 automation! - -| Workflow | Purpose | Produces | -| -------------------------- | ------------------------------------------------------------------------ | -------------------------------- | -| `bmad-bmm-sprint-planning` | Initialize tracking (once per project to sequence the dev cycle) | `sprint-status.yaml` | -| `bmad-bmm-create-story` | Prepare next story for implementation | `story-[slug].md` | -| `bmad-bmm-dev-story` | Implement the story | Working code + tests | -| `bmad-bmm-code-review` | Validate implementation quality | Approved or changes requested | -| `bmad-bmm-correct-course` | Handle significant mid-sprint changes | Updated plan or re-routing | -| `bmad-bmm-automate` | Generate tests for existing features - Use after a full epic is complete | End to End UI Focused Test suite | -| `bmad-bmm-retrospective` | Review after epic completion | Lessons learned | - -## Quick Flow (Parallel Track) - -Skip phases 1-3 for small, well-understood work. - -| Workflow | Purpose | Produces | -| --------------------- | ------------------------------------------ | --------------------------------------------- | -| `bmad-bmm-quick-spec` | Define an ad-hoc change | `tech-spec.md` (story file for small changes) | -| `bmad-bmm-quick-dev` | Implement from spec or direct instructions | Working code + tests | - -## Context Management - -Each document becomes context for the next phase. The PRD tells the architect what constraints matter. The architecture tells the dev agent which patterns to follow. Story files give focused, complete context for implementation. Without this structure, agents make inconsistent decisions. - -### Project Context - -:::tip[Recommended] -Create `project-context.md` to ensure AI agents follow your project's rules and preferences. This file works like a constitution for your project — it guides implementation decisions across all workflows. This optional file can be generated at the end of Architecture Creation, or in an existing project it can be generated also to capture whats important to keep aligned with current conventions. -::: - -**How to create it:** - -- **Manually** — Create `_bmad-output/project-context.md` with your technology stack and implementation rules -- **Generate it** — Run `/bmad-bmm-generate-project-context` to auto-generate from your architecture or codebase - -[**Learn more about project-context.md**](../explanation/project-context.md) diff --git a/docs/roadmap.mdx b/docs/roadmap.mdx deleted file mode 100644 index 8c7f7f1c8..000000000 --- a/docs/roadmap.mdx +++ /dev/null @@ -1,136 +0,0 @@ ---- -title: Roadmap -description: What's next for BMad - Features, improvements, and community contributions ---- - -# The BMad Method: Public Roadmap - -The BMad Method, BMad Method Module (BMM), and BMad Builder (BMB) are evolving. Here's what we're working on and what's coming next. - -
- -

In Progress

- -
-
- 🧩 -

Universal Skills Architecture

-

One skill, any platform. Write once, run everywhere.

-
-
- 🏗️ -

BMad Builder v1

-

Craft production-ready AI agents and workflows with evals, teams, and graceful degradation built in.

-
-
- 🧠 -

Project Context System

-

Your AI actually understands your project. Framework-aware context that evolves with your codebase.

-
-
- 📦 -

Centralized Skills

-

Install once, use everywhere. Share skills across projects without the file clutter.

-
-
- 🔄 -

Adaptive Skills

-

Skills that know your tool. Optimized variants for Claude, Codex, Kimi, and OpenCode, plus many more.

-
-
- 📝 -

BMad Team Pros Blog

-

Guides, articles and insights from the team. Launching soon.

-
-
- -

Getting Started

- -
-
- 🏪 -

Skill Marketplace

-

Discover, install, and update community-built skills. One curl command away from superpowers.

-
-
- 🎨 -

Workflow Customization

-

Make it yours. Integrate Jira, Linear, custom outputs your workflow, your rules.

-
-
- 🚀 -

Phase 1-3 Optimization

-

Lightning-fast planning with sub-agent context gathering. YOLO mode meets guided excellence.

-
-
- 🌐 -

Enterprise Ready

-

SSO, audit logs, team workspaces. All the boring stuff that makes companies say yes.

-
-
- 💎 -

Community Modules Explosion

-

Entertainment, security, therapy, roleplay and much more. Expand the BMad Method platform.

-
-
- ⚡ -

Dev Loop Automation

-

Optional autopilot for development. Let AI handle the flow while keeping quality sky-high.

-
-
- -

Community and Team

- -
-
- 🎙️ -

The BMad Method Podcast

-

Conversations about AI-native development. Launching March 1, 2026!

-
-
- 🎓 -

The BMad Method Master Class

-

Go from user to expert. Deep dives into every phase, every workflow, every secret.

-
-
- 🏗️ -

The BMad Builder Master Class

-

Build your own agents. Advanced techniques for when you are ready to create, not just use.

-
-
- ⚡ -

BMad Prototype First

-

Idea to working prototype in one session. Craft your dream app like a work of art.

-
-
- 🌴 -

BMad BALM!

-

Life management for the AI-native. Tasks, habits, goals your AI copilot for everything.

-
-
- 🖥️ -

Official UI

-

A beautiful interface for the entire BMad ecosystem. CLI power, GUI polish.

-
-
- 🔒 -

BMad in a Box

-

Self-hosted, air-gapped, enterprise-grade. Your AI assistant, your infrastructure, your control.

-
-
- -
-

Want to Contribute?

-

- This is only a partial list of what's planned. The BMad Open Source team welcomes contributors!{" "}
- Join us on GitHub to help shape the future of AI-driven development. -

-

- Love what we're building? We appreciate both one-time and monthly{" "}support. -

-

- For corporate sponsorship, partnership inquiries, speaking engagements, training, or media enquiries:{" "} - contact@bmadcode.com -

-
-
diff --git a/docs/tutorials/getting-started.md b/docs/tutorials/getting-started.md deleted file mode 100644 index b7aa02dfd..000000000 --- a/docs/tutorials/getting-started.md +++ /dev/null @@ -1,273 +0,0 @@ ---- -title: "Getting Started" -description: Install BMad and build your first project ---- - -Build software faster using AI-powered workflows with specialized agents that guide you through planning, architecture, and implementation. - -## What You'll Learn - -- Install and initialize BMad Method for a new project -- Use **BMad-Help** — your intelligent guide that knows what to do next -- Choose the right planning track for your project size -- Progress through phases from requirements to working code -- Use agents and workflows effectively - -:::note[Prerequisites] -- **Node.js 20+** — Required for the installer -- **Git** — Recommended for version control -- **AI-powered IDE** — Claude Code, Cursor, or similar -- **A project idea** — Even a simple one works for learning -::: - -:::tip[The Easiest Path] -**Install** → `npx bmad-method install` -**Ask** → `/bmad-help what should I do first?` -**Build** → Let BMad-Help guide you workflow by workflow -::: - -## Meet BMad-Help: Your Intelligent Guide - -**BMad-Help is the fastest way to get started with BMad.** You don't need to memorize workflows or phases — just ask, and BMad-Help will: - -- **Inspect your project** to see what's already been done -- **Show your options** based on which modules you have installed -- **Recommend what's next** — including the first required task -- **Answer questions** like "I have a SaaS idea, where do I start?" - -### How to Use BMad-Help - -Run it in your AI IDE with just the slash command: - -``` -/bmad-help -``` - -Or combine it with a question for context-aware guidance: - -``` -/bmad-help I have an idea for a SaaS product, I already know all the features I want. where do I get started? -``` - -BMad-Help will respond with: -- What's recommended for your situation -- What the first required task is -- What the rest of the process looks like - -### It Powers Workflows Too - -BMad-Help doesn't just answer questions — **it automatically runs at the end of every workflow** to tell you exactly what to do next. No guessing, no searching docs — just clear guidance on the next required workflow. - -:::tip[Start Here] -After installing BMad, run `/bmad-help` immediately. It will detect what modules you have installed and guide you to the right starting point for your project. -::: - -## Understanding BMad - -BMad helps you build software through guided workflows with specialized AI agents. The process follows four phases: - -| Phase | Name | What Happens | -| ----- | -------------- | --------------------------------------------------- | -| 1 | Analysis | Brainstorming, research, product brief *(optional)* | -| 2 | Planning | Create requirements (PRD or tech-spec) | -| 3 | Solutioning | Design architecture *(BMad Method/Enterprise only)* | -| 4 | Implementation | Build epic by epic, story by story | - -**[Open the Workflow Map](../reference/workflow-map.md)** to explore phases, workflows, and context management. - -Based on your project's complexity, BMad offers three planning tracks: - -| Track | Best For | Documents Created | -| --------------- | ------------------------------------------------------ | -------------------------------------- | -| **Quick Flow** | Bug fixes, simple features, clear scope (1-15 stories) | Tech-spec only | -| **BMad Method** | Products, platforms, complex features (10-50+ stories) | PRD + Architecture + UX | -| **Enterprise** | Compliance, multi-tenant systems (30+ stories) | PRD + Architecture + Security + DevOps | - -:::note -Story counts are guidance, not definitions. Choose your track based on planning needs, not story math. -::: - -## Installation - -Open a terminal in your project directory and run: - -```bash -npx bmad-method install -``` - -When prompted to select modules, choose **BMad Method**. - -The installer creates two folders: -- `_bmad/` — agents, workflows, tasks, and configuration -- `_bmad-output/` — empty for now, but this is where your artifacts will be saved - -:::tip[Your Next Step] -Open your AI IDE in the project folder and run: - -``` -/bmad-help -``` - -BMad-Help will detect what you've completed and recommend exactly what to do next. You can also ask it questions like "What are my options?" or "I have a SaaS idea, where should I start?" -::: - -:::note[How to Load Agents and Run Workflows] -Each workflow has a **slash command** you run in your IDE (e.g., `/bmad-bmm-create-prd`). Running a workflow command automatically loads the appropriate agent — you don't need to load agents separately. You can also load an agent directly for general conversation (e.g., `/bmad-agent-bmm-pm` for the PM agent). -::: - -:::caution[Fresh Chats] -Always start a fresh chat for each workflow. This prevents context limitations from causing issues. -::: - -## Step 1: Create Your Plan - -Work through phases 1-3. **Use fresh chats for each workflow.** - -:::tip[Project Context (Optional)] -Before starting, consider creating `project-context.md` to document your technical preferences and implementation rules. This ensures all AI agents follow your conventions throughout the project. - -Create it manually at `_bmad-output/project-context.md` or generate it after architecture using `/bmad-bmm-generate-project-context`. [Learn more](../explanation/project-context.md). -::: - -### Phase 1: Analysis (Optional) - -All workflows in this phase are optional: -- **brainstorming** (`/bmad-brainstorming`) — Guided ideation -- **research** (`/bmad-bmm-research`) — Market and technical research -- **create-product-brief** (`/bmad-bmm-create-product-brief`) — Recommended foundation document - -### Phase 2: Planning (Required) - -**For BMad Method and Enterprise tracks:** -1. Load the **PM agent** (`/bmad-agent-bmm-pm`) in a new chat -2. Run the `prd` workflow (`/bmad-bmm-create-prd`) -3. Output: `PRD.md` - -**For Quick Flow track:** -- Use the `quick-spec` workflow (`/bmad-bmm-quick-spec`) instead of PRD, then skip to implementation - -:::note[UX Design (Optional)] -If your project has a user interface, load the **UX-Designer agent** (`/bmad-agent-bmm-ux-designer`) and run the UX design workflow (`/bmad-bmm-create-ux-design`) after creating your PRD. -::: - -### Phase 3: Solutioning (BMad Method/Enterprise) - -**Create Architecture** -1. Load the **Architect agent** (`/bmad-agent-bmm-architect`) in a new chat -2. Run `create-architecture` (`/bmad-bmm-create-architecture`) -3. Output: Architecture document with technical decisions - -**Create Epics and Stories** - -:::tip[V6 Improvement] -Epics and stories are now created *after* architecture. This produces better quality stories because architecture decisions (database, API patterns, tech stack) directly affect how work should be broken down. -::: - -1. Load the **PM agent** (`/bmad-agent-bmm-pm`) in a new chat -2. Run `create-epics-and-stories` (`/bmad-bmm-create-epics-and-stories`) -3. The workflow uses both PRD and Architecture to create technically-informed stories - -**Implementation Readiness Check** *(Highly Recommended)* -1. Load the **Architect agent** (`/bmad-agent-bmm-architect`) in a new chat -2. Run `check-implementation-readiness` (`/bmad-bmm-check-implementation-readiness`) -3. Validates cohesion across all planning documents - -## Step 2: Build Your Project - -Once planning is complete, move to implementation. **Each workflow should run in a fresh chat.** - -### Initialize Sprint Planning - -Load the **SM agent** (`/bmad-agent-bmm-sm`) and run `sprint-planning` (`/bmad-bmm-sprint-planning`). This creates `sprint-status.yaml` to track all epics and stories. - -### The Build Cycle - -For each story, repeat this cycle with fresh chats: - -| Step | Agent | Workflow | Command | Purpose | -| ---- | ----- | -------------- | -------------------------- | ---------------------------------- | -| 1 | SM | `create-story` | `/bmad-bmm-create-story` | Create story file from epic | -| 2 | DEV | `dev-story` | `/bmad-bmm-dev-story` | Implement the story | -| 3 | DEV | `code-review` | `/bmad-bmm-code-review` | Quality validation *(recommended)* | - -After completing all stories in an epic, load the **SM agent** (`/bmad-agent-bmm-sm`) and run `retrospective` (`/bmad-bmm-retrospective`). - -## What You've Accomplished - -You've learned the foundation of building with BMad: - -- Installed BMad and configured it for your IDE -- Initialized a project with your chosen planning track -- Created planning documents (PRD, Architecture, Epics & Stories) -- Understood the build cycle for implementation - -Your project now has: - -```text -your-project/ -├── _bmad/ # BMad configuration -├── _bmad-output/ -│ ├── planning-artifacts/ -│ │ ├── PRD.md # Your requirements document -│ │ ├── architecture.md # Technical decisions -│ │ └── epics/ # Epic and story files -│ ├── implementation-artifacts/ -│ │ └── sprint-status.yaml # Sprint tracking -│ └── project-context.md # Implementation rules (optional) -└── ... -``` - -## Quick Reference - -| Workflow | Command | Agent | Purpose | -| ------------------------------------- | ------------------------------------------ | --------- | ----------------------------------------------- | -| **`help`** ⭐ | `/bmad-help` | Any | **Your intelligent guide — ask anything!** | -| `prd` | `/bmad-bmm-create-prd` | PM | Create Product Requirements Document | -| `create-architecture` | `/bmad-bmm-create-architecture` | Architect | Create architecture document | -| `generate-project-context` | `/bmad-bmm-generate-project-context` | Analyst | Create project context file | -| `create-epics-and-stories` | `/bmad-bmm-create-epics-and-stories` | PM | Break down PRD into epics | -| `check-implementation-readiness` | `/bmad-bmm-check-implementation-readiness` | Architect | Validate planning cohesion | -| `sprint-planning` | `/bmad-bmm-sprint-planning` | SM | Initialize sprint tracking | -| `create-story` | `/bmad-bmm-create-story` | SM | Create a story file | -| `dev-story` | `/bmad-bmm-dev-story` | DEV | Implement a story | -| `code-review` | `/bmad-bmm-code-review` | DEV | Review implemented code | - -## Common Questions - -**Do I always need architecture?** -Only for BMad Method and Enterprise tracks. Quick Flow skips from tech-spec to implementation. - -**Can I change my plan later?** -Yes. The SM agent has a `correct-course` workflow (`/bmad-bmm-correct-course`) for handling scope changes. - -**What if I want to brainstorm first?** -Load the Analyst agent (`/bmad-agent-bmm-analyst`) and run `brainstorming` (`/bmad-brainstorming`) before starting your PRD. - -**Do I need to follow a strict order?** -Not strictly. Once you learn the flow, you can run workflows directly using the Quick Reference above. - -## Getting Help - -:::tip[First Stop: BMad-Help] -**Run `/bmad-help` anytime** — it's the fastest way to get unstuck. Ask it anything: -- "What should I do after installing?" -- "I'm stuck on workflow X" -- "What are my options for Y?" -- "Show me what's been done so far" - -BMad-Help inspects your project, detects what you've completed, and tells you exactly what to do next. -::: - -- **During workflows** — Agents guide you with questions and explanations -- **Community** — [Discord](https://discord.gg/gk8jAdXWmj) (#bmad-method-help, #report-bugs-and-issues) - -## Key Takeaways - -:::tip[Remember These] -- **Start with `/bmad-help`** — Your intelligent guide that knows your project and options -- **Always use fresh chats** — Start a new chat for each workflow -- **Track matters** — Quick Flow uses quick-spec; Method/Enterprise need PRD and architecture -- **BMad-Help runs automatically** — Every workflow ends with guidance on what's next -::: - -Ready to start? Install BMad, run `/bmad-help`, and let your intelligent guide lead the way. diff --git a/eslint.config.mjs b/eslint.config.mjs deleted file mode 100644 index 23bf73aa5..000000000 --- a/eslint.config.mjs +++ /dev/null @@ -1,141 +0,0 @@ -import js from '@eslint/js'; -import eslintConfigPrettier from 'eslint-config-prettier/flat'; -import nodePlugin from 'eslint-plugin-n'; -import unicorn from 'eslint-plugin-unicorn'; -import yml from 'eslint-plugin-yml'; - -export default [ - // Global ignores for files/folders that should not be linted - { - ignores: [ - 'dist/**', - 'coverage/**', - '**/*.min.js', - 'test/template-test-generator/**', - 'test/fixtures/**', - '_bmad*/**', - // Build output - 'build/**', - // Website uses ESM/Astro - separate linting ecosystem - 'website/**', - // Gitignored patterns - 'z*/**', // z-samples, z1, z2, etc. - '.claude/**', - '.codex/**', - '.github/chatmodes/**', - '.agent/**', - '.agentvibes/**', - '.kiro/**', - '.roo/**', - 'test-project-install/**', - 'sample-project/**', - 'tools/template-test-generator/test-scenarios/**', - 'src/modules/*/sub-modules/**', - '.bundler-temp/**', - // Augment vendor config — not project code, naming conventions - // are dictated by Augment and can't be changed, so exclude - // the entire directory from linting - '.augment/**', - ], - }, - - // Base JavaScript recommended rules - js.configs.recommended, - - // Node.js rules - ...nodePlugin.configs['flat/mixed-esm-and-cjs'], - - // Unicorn rules (modern best practices) - unicorn.configs.recommended, - - // YAML linting - ...yml.configs['flat/recommended'], - - // Place Prettier last to disable conflicting stylistic rules - eslintConfigPrettier, - - // Project-specific tweaks - { - rules: { - // Allow console for CLI tools in this repo - 'no-console': 'off', - // Enforce .yaml file extension for consistency - 'yml/file-extension': [ - 'error', - { - extension: 'yaml', - caseSensitive: true, - }, - ], - // Prefer double quotes in YAML wherever quoting is used, but allow the other to avoid escapes - 'yml/quotes': [ - 'error', - { - prefer: 'double', - avoidEscape: true, - }, - ], - // Relax some Unicorn rules that are too opinionated for this codebase - 'unicorn/prevent-abbreviations': 'off', - 'unicorn/no-null': 'off', - }, - }, - - // CLI scripts under tools/** and test/** - { - files: ['tools/**/*.js', 'tools/**/*.mjs', 'test/**/*.js', 'test/**/*.mjs'], - rules: { - // Allow CommonJS patterns for Node CLI scripts - 'unicorn/prefer-module': 'off', - 'unicorn/import-style': 'off', - 'unicorn/no-process-exit': 'off', - 'n/no-process-exit': 'off', - 'unicorn/no-await-expression-member': 'off', - 'unicorn/prefer-top-level-await': 'off', - // Avoid failing CI on incidental unused vars in internal scripts - 'no-unused-vars': 'off', - // Reduce style-only churn in internal tools - 'unicorn/prefer-ternary': 'off', - 'unicorn/filename-case': 'off', - 'unicorn/no-array-reduce': 'off', - 'unicorn/no-array-callback-reference': 'off', - 'unicorn/consistent-function-scoping': 'off', - 'n/no-extraneous-require': 'off', - 'n/no-extraneous-import': 'off', - 'n/no-unpublished-require': 'off', - 'n/no-unpublished-import': 'off', - // Some scripts intentionally use globals provided at runtime - 'no-undef': 'off', - // Additional relaxed rules for legacy/internal scripts - 'no-useless-catch': 'off', - 'unicorn/prefer-number-properties': 'off', - 'no-unreachable': 'off', - 'unicorn/text-encoding-identifier-case': 'off', - }, - }, - - // ESLint config file should not be checked for publish-related Node rules - { - files: ['eslint.config.mjs'], - rules: { - 'n/no-unpublished-import': 'off', - }, - }, - - // GitHub workflow files in this repo may use empty mapping values - { - files: ['.github/workflows/**/*.yaml'], - rules: { - 'yml/no-empty-mapping-value': 'off', - }, - }, - - // Other GitHub YAML files may intentionally use empty values and reserved filenames - { - files: ['.github/**/*.yaml'], - rules: { - 'yml/no-empty-mapping-value': 'off', - 'unicorn/filename-case': 'off', - }, - }, -]; diff --git a/package-lock.json b/package-lock.json deleted file mode 100644 index 450469c4d..000000000 --- a/package-lock.json +++ /dev/null @@ -1,14369 +0,0 @@ -{ - "name": "bmad-method", - "version": "6.0.4", - "lockfileVersion": 3, - "requires": true, - "packages": { - "": { - "name": "bmad-method", - "version": "6.0.4", - "license": "MIT", - "dependencies": { - "@clack/core": "^1.0.0", - "@clack/prompts": "^1.0.0", - "@kayvan/markdown-tree-parser": "^1.6.1", - "chalk": "^4.1.2", - "commander": "^14.0.0", - "csv-parse": "^6.1.0", - "fs-extra": "^11.3.0", - "glob": "^11.0.3", - "ignore": "^7.0.5", - "js-yaml": "^4.1.0", - "picocolors": "^1.1.1", - "semver": "^7.6.3", - "xml2js": "^0.6.2", - "yaml": "^2.7.0" - }, - "bin": { - "bmad": "tools/bmad-npx-wrapper.js", - "bmad-method": "tools/bmad-npx-wrapper.js" - }, - "devDependencies": { - "@astrojs/sitemap": "^3.6.0", - "@astrojs/starlight": "^0.37.5", - "@eslint/js": "^9.33.0", - "astro": "^5.16.0", - "c8": "^10.1.3", - "eslint": "^9.33.0", - "eslint-config-prettier": "^10.1.8", - "eslint-plugin-n": "^17.21.3", - "eslint-plugin-unicorn": "^60.0.0", - "eslint-plugin-yml": "^1.18.0", - "husky": "^9.1.7", - "jest": "^30.2.0", - "lint-staged": "^16.1.1", - "markdownlint-cli2": "^0.19.1", - "prettier": "^3.7.4", - "prettier-plugin-packagejson": "^2.5.19", - "sharp": "^0.33.5", - "yaml-eslint-parser": "^1.2.3", - "yaml-lint": "^1.7.0" - }, - "engines": { - "node": ">=20.0.0" - } - }, - "node_modules/@astrojs/compiler": { - "version": "2.13.0", - "resolved": "https://registry.npmjs.org/@astrojs/compiler/-/compiler-2.13.0.tgz", - "integrity": "sha512-mqVORhUJViA28fwHYaWmsXSzLO9osbdZ5ImUfxBarqsYdMlPbqAqGJCxsNzvppp1BEzc1mJNjOVvQqeDN8Vspw==", - "dev": true, - "license": "MIT" - }, - "node_modules/@astrojs/internal-helpers": { - "version": "0.7.5", - "resolved": "https://registry.npmjs.org/@astrojs/internal-helpers/-/internal-helpers-0.7.5.tgz", - "integrity": "sha512-vreGnYSSKhAjFJCWAwe/CNhONvoc5lokxtRoZims+0wa3KbHBdPHSSthJsKxPd8d/aic6lWKpRTYGY/hsgK6EA==", - "dev": true, - "license": "MIT" - }, - "node_modules/@astrojs/markdown-remark": { - "version": "6.3.10", - "resolved": "https://registry.npmjs.org/@astrojs/markdown-remark/-/markdown-remark-6.3.10.tgz", - "integrity": "sha512-kk4HeYR6AcnzC4QV8iSlOfh+N8TZ3MEStxPyenyCtemqn8IpEATBFMTJcfrNW32dgpt6MY3oCkMM/Tv3/I4G3A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@astrojs/internal-helpers": "0.7.5", - "@astrojs/prism": "3.3.0", - "github-slugger": "^2.0.0", - "hast-util-from-html": "^2.0.3", - "hast-util-to-text": "^4.0.2", - "import-meta-resolve": "^4.2.0", - "js-yaml": "^4.1.1", - "mdast-util-definitions": "^6.0.0", - "rehype-raw": "^7.0.0", - "rehype-stringify": "^10.0.1", - "remark-gfm": "^4.0.1", - "remark-parse": "^11.0.0", - "remark-rehype": "^11.1.2", - "remark-smartypants": "^3.0.2", - "shiki": "^3.19.0", - "smol-toml": "^1.5.2", - "unified": "^11.0.5", - "unist-util-remove-position": "^5.0.0", - "unist-util-visit": "^5.0.0", - "unist-util-visit-parents": "^6.0.2", - "vfile": "^6.0.3" - } - }, - "node_modules/@astrojs/mdx": { - "version": "4.3.13", - "resolved": "https://registry.npmjs.org/@astrojs/mdx/-/mdx-4.3.13.tgz", - "integrity": "sha512-IHDHVKz0JfKBy3//52JSiyWv089b7GVSChIXLrlUOoTLWowG3wr2/8hkaEgEyd/vysvNQvGk+QhysXpJW5ve6Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "@astrojs/markdown-remark": "6.3.10", - "@mdx-js/mdx": "^3.1.1", - "acorn": "^8.15.0", - "es-module-lexer": "^1.7.0", - "estree-util-visit": "^2.0.0", - "hast-util-to-html": "^9.0.5", - "piccolore": "^0.1.3", - "rehype-raw": "^7.0.0", - "remark-gfm": "^4.0.1", - "remark-smartypants": "^3.0.2", - "source-map": "^0.7.6", - "unist-util-visit": "^5.0.0", - "vfile": "^6.0.3" - }, - "engines": { - "node": "18.20.8 || ^20.3.0 || >=22.0.0" - }, - "peerDependencies": { - "astro": "^5.0.0" - } - }, - "node_modules/@astrojs/prism": { - "version": "3.3.0", - "resolved": "https://registry.npmjs.org/@astrojs/prism/-/prism-3.3.0.tgz", - "integrity": "sha512-q8VwfU/fDZNoDOf+r7jUnMC2//H2l0TuQ6FkGJL8vD8nw/q5KiL3DS1KKBI3QhI9UQhpJ5dc7AtqfbXWuOgLCQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "prismjs": "^1.30.0" - }, - "engines": { - "node": "18.20.8 || ^20.3.0 || >=22.0.0" - } - }, - "node_modules/@astrojs/sitemap": { - "version": "3.7.0", - "resolved": "https://registry.npmjs.org/@astrojs/sitemap/-/sitemap-3.7.0.tgz", - "integrity": "sha512-+qxjUrz6Jcgh+D5VE1gKUJTA3pSthuPHe6Ao5JCxok794Lewx8hBFaWHtOnN0ntb2lfOf7gvOi9TefUswQ/ZVA==", - "dev": true, - "license": "MIT", - "dependencies": { - "sitemap": "^8.0.2", - "stream-replace-string": "^2.0.0", - "zod": "^3.25.76" - } - }, - "node_modules/@astrojs/starlight": { - "version": "0.37.5", - "resolved": "https://registry.npmjs.org/@astrojs/starlight/-/starlight-0.37.5.tgz", - "integrity": "sha512-+pC2pgy0iR9Ucl1P4CE0jyfsoNKcUSB2RIoBwm4UnyyhtlaEjoSU7MZwa5IJkzS9sBgIbLbLgYVbkC4tHN8rkQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@astrojs/markdown-remark": "^6.3.1", - "@astrojs/mdx": "^4.2.3", - "@astrojs/sitemap": "^3.3.0", - "@pagefind/default-ui": "^1.3.0", - "@types/hast": "^3.0.4", - "@types/js-yaml": "^4.0.9", - "@types/mdast": "^4.0.4", - "astro-expressive-code": "^0.41.1", - "bcp-47": "^2.1.0", - "hast-util-from-html": "^2.0.1", - "hast-util-select": "^6.0.2", - "hast-util-to-string": "^3.0.0", - "hastscript": "^9.0.0", - "i18next": "^23.11.5", - "js-yaml": "^4.1.0", - "klona": "^2.0.6", - "magic-string": "^0.30.17", - "mdast-util-directive": "^3.0.0", - "mdast-util-to-markdown": "^2.1.0", - "mdast-util-to-string": "^4.0.0", - "pagefind": "^1.3.0", - "rehype": "^13.0.1", - "rehype-format": "^5.0.0", - "remark-directive": "^3.0.0", - "ultrahtml": "^1.6.0", - "unified": "^11.0.5", - "unist-util-visit": "^5.0.0", - "vfile": "^6.0.2" - }, - "peerDependencies": { - "astro": "^5.5.0" - } - }, - "node_modules/@astrojs/telemetry": { - "version": "3.3.0", - "resolved": "https://registry.npmjs.org/@astrojs/telemetry/-/telemetry-3.3.0.tgz", - "integrity": "sha512-UFBgfeldP06qu6khs/yY+q1cDAaArM2/7AEIqQ9Cuvf7B1hNLq0xDrZkct+QoIGyjq56y8IaE2I3CTvG99mlhQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "ci-info": "^4.2.0", - "debug": "^4.4.0", - "dlv": "^1.1.3", - "dset": "^3.1.4", - "is-docker": "^3.0.0", - "is-wsl": "^3.1.0", - "which-pm-runs": "^1.1.0" - }, - "engines": { - "node": "18.20.8 || ^20.3.0 || >=22.0.0" - } - }, - "node_modules/@babel/code-frame": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.28.6.tgz", - "integrity": "sha512-JYgintcMjRiCvS8mMECzaEn+m3PfoQiyqukOMCCVQtoJGYJw8j/8LBJEiqkHLkfwCcs74E3pbAUFNg7d9VNJ+Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-validator-identifier": "^7.28.5", - "js-tokens": "^4.0.0", - "picocolors": "^1.1.1" - }, - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/compat-data": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.28.6.tgz", - "integrity": "sha512-2lfu57JtzctfIrcGMz992hyLlByuzgIk58+hhGCxjKZ3rWI82NnVLjXcaTqkI2NvlcvOskZaiZ5kjUALo3Lpxg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/core": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.28.6.tgz", - "integrity": "sha512-H3mcG6ZDLTlYfaSNi0iOKkigqMFvkTKlGUYlD8GW7nNOYRrevuA46iTypPyv+06V3fEmvvazfntkBU34L0azAw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/code-frame": "^7.28.6", - "@babel/generator": "^7.28.6", - "@babel/helper-compilation-targets": "^7.28.6", - "@babel/helper-module-transforms": "^7.28.6", - "@babel/helpers": "^7.28.6", - "@babel/parser": "^7.28.6", - "@babel/template": "^7.28.6", - "@babel/traverse": "^7.28.6", - "@babel/types": "^7.28.6", - "@jridgewell/remapping": "^2.3.5", - "convert-source-map": "^2.0.0", - "debug": "^4.1.0", - "gensync": "^1.0.0-beta.2", - "json5": "^2.2.3", - "semver": "^6.3.1" - }, - "engines": { - "node": ">=6.9.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/babel" - } - }, - "node_modules/@babel/core/node_modules/semver": { - "version": "6.3.1", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", - "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", - "dev": true, - "license": "ISC", - "bin": { - "semver": "bin/semver.js" - } - }, - "node_modules/@babel/generator": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.28.6.tgz", - "integrity": "sha512-lOoVRwADj8hjf7al89tvQ2a1lf53Z+7tiXMgpZJL3maQPDxh0DgLMN62B2MKUOFcoodBHLMbDM6WAbKgNy5Suw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/parser": "^7.28.6", - "@babel/types": "^7.28.6", - "@jridgewell/gen-mapping": "^0.3.12", - "@jridgewell/trace-mapping": "^0.3.28", - "jsesc": "^3.0.2" - }, - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/helper-compilation-targets": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/helper-compilation-targets/-/helper-compilation-targets-7.28.6.tgz", - "integrity": "sha512-JYtls3hqi15fcx5GaSNL7SCTJ2MNmjrkHXg4FSpOA/grxK8KwyZ5bubHsCq8FXCkua6xhuaaBit+3b7+VZRfcA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/compat-data": "^7.28.6", - "@babel/helper-validator-option": "^7.27.1", - "browserslist": "^4.24.0", - "lru-cache": "^5.1.1", - "semver": "^6.3.1" - }, - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/helper-compilation-targets/node_modules/semver": { - "version": "6.3.1", - "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz", - "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==", - "dev": true, - "license": "ISC", - "bin": { - "semver": "bin/semver.js" - } - }, - "node_modules/@babel/helper-globals": { - "version": "7.28.0", - "resolved": "https://registry.npmjs.org/@babel/helper-globals/-/helper-globals-7.28.0.tgz", - "integrity": "sha512-+W6cISkXFa1jXsDEdYA8HeevQT/FULhxzR99pxphltZcVaugps53THCeiWA8SguxxpSp3gKPiuYfSWopkLQ4hw==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/helper-module-imports": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/helper-module-imports/-/helper-module-imports-7.28.6.tgz", - "integrity": "sha512-l5XkZK7r7wa9LucGw9LwZyyCUscb4x37JWTPz7swwFE/0FMQAGpiWUZn8u9DzkSBWEcK25jmvubfpw2dnAMdbw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/traverse": "^7.28.6", - "@babel/types": "^7.28.6" - }, - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/helper-module-transforms": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.28.6.tgz", - "integrity": "sha512-67oXFAYr2cDLDVGLXTEABjdBJZ6drElUSI7WKp70NrpyISso3plG9SAGEF6y7zbha/wOzUByWWTJvEDVNIUGcA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-module-imports": "^7.28.6", - "@babel/helper-validator-identifier": "^7.28.5", - "@babel/traverse": "^7.28.6" - }, - "engines": { - "node": ">=6.9.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0" - } - }, - "node_modules/@babel/helper-plugin-utils": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/helper-plugin-utils/-/helper-plugin-utils-7.28.6.tgz", - "integrity": "sha512-S9gzZ/bz83GRysI7gAD4wPT/AI3uCnY+9xn+Mx/KPs2JwHJIz1W8PZkg2cqyt3RNOBM8ejcXhV6y8Og7ly/Dug==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/helper-string-parser": { - "version": "7.27.1", - "resolved": "https://registry.npmjs.org/@babel/helper-string-parser/-/helper-string-parser-7.27.1.tgz", - "integrity": "sha512-qMlSxKbpRlAridDExk92nSobyDdpPijUq2DW6oDnUqd0iOGxmQjyqhMIihI9+zv4LPyZdRje2cavWPbCbWm3eA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/helper-validator-identifier": { - "version": "7.28.5", - "resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.28.5.tgz", - "integrity": "sha512-qSs4ifwzKJSV39ucNjsvc6WVHs6b7S03sOh2OcHF9UHfVPqWWALUsNUVzhSBiItjRZoLHx7nIarVjqKVusUZ1Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/helper-validator-option": { - "version": "7.27.1", - "resolved": "https://registry.npmjs.org/@babel/helper-validator-option/-/helper-validator-option-7.27.1.tgz", - "integrity": "sha512-YvjJow9FxbhFFKDSuFnVCe2WxXk1zWc22fFePVNEaWJEu8IrZVlda6N0uHwzZrUM1il7NC9Mlp4MaJYbYd9JSg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/helpers": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/helpers/-/helpers-7.28.6.tgz", - "integrity": "sha512-xOBvwq86HHdB7WUDTfKfT/Vuxh7gElQ+Sfti2Cy6yIWNW05P8iUslOVcZ4/sKbE+/jQaukQAdz/gf3724kYdqw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/template": "^7.28.6", - "@babel/types": "^7.28.6" - }, - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/parser": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/parser/-/parser-7.28.6.tgz", - "integrity": "sha512-TeR9zWR18BvbfPmGbLampPMW+uW1NZnJlRuuHso8i87QZNq2JRF9i6RgxRqtEq+wQGsS19NNTWr2duhnE49mfQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/types": "^7.28.6" - }, - "bin": { - "parser": "bin/babel-parser.js" - }, - "engines": { - "node": ">=6.0.0" - } - }, - "node_modules/@babel/plugin-syntax-async-generators": { - "version": "7.8.4", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-async-generators/-/plugin-syntax-async-generators-7.8.4.tgz", - "integrity": "sha512-tycmZxkGfZaxhMRbXlPXuVFpdWlXpir2W4AMhSJgRKzk/eDlIXOhb2LHWoLpDF7TEHylV5zNhykX6KAgHJmTNw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.8.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-bigint": { - "version": "7.8.3", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-bigint/-/plugin-syntax-bigint-7.8.3.tgz", - "integrity": "sha512-wnTnFlG+YxQm3vDxpGE57Pj0srRU4sHE/mDkt1qv2YJJSeUAec2ma4WLUnUPeKjyrfntVwe/N6dCXpU+zL3Npg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.8.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-class-properties": { - "version": "7.12.13", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-class-properties/-/plugin-syntax-class-properties-7.12.13.tgz", - "integrity": "sha512-fm4idjKla0YahUNgFNLCB0qySdsoPiZP3iQE3rky0mBUtMZ23yDJ9SJdg6dXTSDnulOVqiF3Hgr9nbXvXTQZYA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.12.13" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-class-static-block": { - "version": "7.14.5", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-class-static-block/-/plugin-syntax-class-static-block-7.14.5.tgz", - "integrity": "sha512-b+YyPmr6ldyNnM6sqYeMWE+bgJcJpO6yS4QD7ymxgH34GBPNDM/THBh8iunyvKIZztiwLH4CJZ0RxTk9emgpjw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.14.5" - }, - "engines": { - "node": ">=6.9.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-import-attributes": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-import-attributes/-/plugin-syntax-import-attributes-7.28.6.tgz", - "integrity": "sha512-jiLC0ma9XkQT3TKJ9uYvlakm66Pamywo+qwL+oL8HJOvc6TWdZXVfhqJr8CCzbSGUAbDOzlGHJC1U+vRfLQDvw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.28.6" - }, - "engines": { - "node": ">=6.9.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-import-meta": { - "version": "7.10.4", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-import-meta/-/plugin-syntax-import-meta-7.10.4.tgz", - "integrity": "sha512-Yqfm+XDx0+Prh3VSeEQCPU81yC+JWZ2pDPFSS4ZdpfZhp4MkFMaDC1UqseovEKwSUpnIL7+vK+Clp7bfh0iD7g==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.10.4" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-json-strings": { - "version": "7.8.3", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-json-strings/-/plugin-syntax-json-strings-7.8.3.tgz", - "integrity": "sha512-lY6kdGpWHvjoe2vk4WrAapEuBR69EMxZl+RoGRhrFGNYVK8mOPAW8VfbT/ZgrFbXlDNiiaxQnAtgVCZ6jv30EA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.8.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-jsx": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-jsx/-/plugin-syntax-jsx-7.28.6.tgz", - "integrity": "sha512-wgEmr06G6sIpqr8YDwA2dSRTE3bJ+V0IfpzfSY3Lfgd7YWOaAdlykvJi13ZKBt8cZHfgH1IXN+CL656W3uUa4w==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.28.6" - }, - "engines": { - "node": ">=6.9.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-logical-assignment-operators": { - "version": "7.10.4", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-logical-assignment-operators/-/plugin-syntax-logical-assignment-operators-7.10.4.tgz", - "integrity": "sha512-d8waShlpFDinQ5MtvGU9xDAOzKH47+FFoney2baFIoMr952hKOLp1HR7VszoZvOsV/4+RRszNY7D17ba0te0ig==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.10.4" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-nullish-coalescing-operator": { - "version": "7.8.3", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-nullish-coalescing-operator/-/plugin-syntax-nullish-coalescing-operator-7.8.3.tgz", - "integrity": "sha512-aSff4zPII1u2QD7y+F8oDsz19ew4IGEJg9SVW+bqwpwtfFleiQDMdzA/R+UlWDzfnHFCxxleFT0PMIrR36XLNQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.8.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-numeric-separator": { - "version": "7.10.4", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-numeric-separator/-/plugin-syntax-numeric-separator-7.10.4.tgz", - "integrity": "sha512-9H6YdfkcK/uOnY/K7/aA2xpzaAgkQn37yzWUMRK7OaPOqOpGS1+n0H5hxT9AUw9EsSjPW8SVyMJwYRtWs3X3ug==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.10.4" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-object-rest-spread": { - "version": "7.8.3", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-object-rest-spread/-/plugin-syntax-object-rest-spread-7.8.3.tgz", - "integrity": "sha512-XoqMijGZb9y3y2XskN+P1wUGiVwWZ5JmoDRwx5+3GmEplNyVM2s2Dg8ILFQm8rWM48orGy5YpI5Bl8U1y7ydlA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.8.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-optional-catch-binding": { - "version": "7.8.3", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-optional-catch-binding/-/plugin-syntax-optional-catch-binding-7.8.3.tgz", - "integrity": "sha512-6VPD0Pc1lpTqw0aKoeRTMiB+kWhAoT24PA+ksWSBrFtl5SIRVpZlwN3NNPQjehA2E/91FV3RjLWoVTglWcSV3Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.8.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-optional-chaining": { - "version": "7.8.3", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-optional-chaining/-/plugin-syntax-optional-chaining-7.8.3.tgz", - "integrity": "sha512-KoK9ErH1MBlCPxV0VANkXW2/dw4vlbGDrFgz8bmUsBGYkFRcbRwMh6cIJubdPrkxRwuGdtCk0v/wPTKbQgBjkg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.8.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-private-property-in-object": { - "version": "7.14.5", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-private-property-in-object/-/plugin-syntax-private-property-in-object-7.14.5.tgz", - "integrity": "sha512-0wVnp9dxJ72ZUJDV27ZfbSj6iHLoytYZmh3rFcxNnvsJF3ktkzLDZPy/mA17HGsaQT3/DQsWYX1f1QGWkCoVUg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.14.5" - }, - "engines": { - "node": ">=6.9.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-top-level-await": { - "version": "7.14.5", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-top-level-await/-/plugin-syntax-top-level-await-7.14.5.tgz", - "integrity": "sha512-hx++upLv5U1rgYfwe1xBQUhRmU41NEvpUvrp8jkrSCdvGSnM5/qdRMtylJ6PG5OFkBaHkbTAKTnd3/YyESRHFw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.14.5" - }, - "engines": { - "node": ">=6.9.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/plugin-syntax-typescript": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/plugin-syntax-typescript/-/plugin-syntax-typescript-7.28.6.tgz", - "integrity": "sha512-+nDNmQye7nlnuuHDboPbGm00Vqg3oO8niRRL27/4LYHUsHYh0zJ1xWOz0uRwNFmM1Avzk8wZbc6rdiYhomzv/A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-plugin-utils": "^7.28.6" - }, - "engines": { - "node": ">=6.9.0" - }, - "peerDependencies": { - "@babel/core": "^7.0.0-0" - } - }, - "node_modules/@babel/runtime": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/runtime/-/runtime-7.28.6.tgz", - "integrity": "sha512-05WQkdpL9COIMz4LjTxGpPNCdlpyimKppYNoJ5Di5EUObifl8t4tuLuUBBZEpoLYOmfvIWrsp9fCl0HoPRVTdA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/template": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/template/-/template-7.28.6.tgz", - "integrity": "sha512-YA6Ma2KsCdGb+WC6UpBVFJGXL58MDA6oyONbjyF/+5sBgxY/dwkhLogbMT2GXXyU84/IhRw/2D1Os1B/giz+BQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/code-frame": "^7.28.6", - "@babel/parser": "^7.28.6", - "@babel/types": "^7.28.6" - }, - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/traverse": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/traverse/-/traverse-7.28.6.tgz", - "integrity": "sha512-fgWX62k02qtjqdSNTAGxmKYY/7FSL9WAS1o2Hu5+I5m9T0yxZzr4cnrfXQ/MX0rIifthCSs6FKTlzYbJcPtMNg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/code-frame": "^7.28.6", - "@babel/generator": "^7.28.6", - "@babel/helper-globals": "^7.28.0", - "@babel/parser": "^7.28.6", - "@babel/template": "^7.28.6", - "@babel/types": "^7.28.6", - "debug": "^4.3.1" - }, - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@babel/types": { - "version": "7.28.6", - "resolved": "https://registry.npmjs.org/@babel/types/-/types-7.28.6.tgz", - "integrity": "sha512-0ZrskXVEHSWIqZM/sQZ4EV3jZJXRkio/WCxaqKZP1g//CEWEPSfeZFcms4XeKBCHU0ZKnIkdJeU/kF+eRp5lBg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-string-parser": "^7.27.1", - "@babel/helper-validator-identifier": "^7.28.5" - }, - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/@bcoe/v8-coverage": { - "version": "1.0.2", - "resolved": "https://registry.npmjs.org/@bcoe/v8-coverage/-/v8-coverage-1.0.2.tgz", - "integrity": "sha512-6zABk/ECA/QYSCQ1NGiVwwbQerUCZ+TQbp64Q3AgmfNvurHH0j8TtXa1qbShXA6qqkpAj4V5W8pP6mLe1mcMqA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - } - }, - "node_modules/@capsizecss/unpack": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/@capsizecss/unpack/-/unpack-4.0.0.tgz", - "integrity": "sha512-VERIM64vtTP1C4mxQ5thVT9fK0apjPFobqybMtA1UdUujWka24ERHbRHFGmpbbhp73MhV+KSsHQH9C6uOTdEQA==", - "dev": true, - "license": "MIT", - "dependencies": { - "fontkitten": "^1.0.0" - }, - "engines": { - "node": ">=18" - } - }, - "node_modules/@clack/core": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/@clack/core/-/core-1.0.0.tgz", - "integrity": "sha512-Orf9Ltr5NeiEuVJS8Rk2XTw3IxNC2Bic3ash7GgYeA8LJ/zmSNpSQ/m5UAhe03lA6KFgklzZ5KTHs4OAMA/SAQ==", - "license": "MIT", - "dependencies": { - "picocolors": "^1.0.0", - "sisteransi": "^1.0.5" - } - }, - "node_modules/@clack/prompts": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/@clack/prompts/-/prompts-1.0.0.tgz", - "integrity": "sha512-rWPXg9UaCFqErJVQ+MecOaWsozjaxol4yjnmYcGNipAWzdaWa2x+VJmKfGq7L0APwBohQOYdHC+9RO4qRXej+A==", - "license": "MIT", - "dependencies": { - "@clack/core": "1.0.0", - "picocolors": "^1.0.0", - "sisteransi": "^1.0.5" - } - }, - "node_modules/@ctrl/tinycolor": { - "version": "4.2.0", - "resolved": "https://registry.npmjs.org/@ctrl/tinycolor/-/tinycolor-4.2.0.tgz", - "integrity": "sha512-kzyuwOAQnXJNLS9PSyrk0CWk35nWJW/zl/6KvnTBMFK65gm7U1/Z5BqjxeapjZCIhQcM/DsrEmcbRwDyXyXK4A==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=14" - } - }, - "node_modules/@emnapi/core": { - "version": "1.8.1", - "resolved": "https://registry.npmjs.org/@emnapi/core/-/core-1.8.1.tgz", - "integrity": "sha512-AvT9QFpxK0Zd8J0jopedNm+w/2fIzvtPKPjqyw9jwvBaReTTqPBk9Hixaz7KbjimP+QNz605/XnjFcDAL2pqBg==", - "dev": true, - "license": "MIT", - "optional": true, - "dependencies": { - "@emnapi/wasi-threads": "1.1.0", - "tslib": "^2.4.0" - } - }, - "node_modules/@emnapi/runtime": { - "version": "1.8.1", - "resolved": "https://registry.npmjs.org/@emnapi/runtime/-/runtime-1.8.1.tgz", - "integrity": "sha512-mehfKSMWjjNol8659Z8KxEMrdSJDDot5SXMq00dM8BN4o+CLNXQ0xH2V7EchNHV4RmbZLmmPdEaXZc5H2FXmDg==", - "dev": true, - "license": "MIT", - "optional": true, - "dependencies": { - "tslib": "^2.4.0" - } - }, - "node_modules/@emnapi/wasi-threads": { - "version": "1.1.0", - "resolved": "https://registry.npmjs.org/@emnapi/wasi-threads/-/wasi-threads-1.1.0.tgz", - "integrity": "sha512-WI0DdZ8xFSbgMjR1sFsKABJ/C5OnRrjT06JXbZKexJGrDuPTzZdDYfFlsgcCXCyf+suG5QU2e/y1Wo2V/OapLQ==", - "dev": true, - "license": "MIT", - "optional": true, - "dependencies": { - "tslib": "^2.4.0" - } - }, - "node_modules/@esbuild/aix-ppc64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/aix-ppc64/-/aix-ppc64-0.25.12.tgz", - "integrity": "sha512-Hhmwd6CInZ3dwpuGTF8fJG6yoWmsToE+vYgD4nytZVxcu1ulHpUQRAB1UJ8+N1Am3Mz4+xOByoQoSZf4D+CpkA==", - "cpu": [ - "ppc64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "aix" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/android-arm": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/android-arm/-/android-arm-0.25.12.tgz", - "integrity": "sha512-VJ+sKvNA/GE7Ccacc9Cha7bpS8nyzVv0jdVgwNDaR4gDMC/2TTRc33Ip8qrNYUcpkOHUT5OZ0bUcNNVZQ9RLlg==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "android" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/android-arm64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/android-arm64/-/android-arm64-0.25.12.tgz", - "integrity": "sha512-6AAmLG7zwD1Z159jCKPvAxZd4y/VTO0VkprYy+3N2FtJ8+BQWFXU+OxARIwA46c5tdD9SsKGZ/1ocqBS/gAKHg==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "android" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/android-x64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/android-x64/-/android-x64-0.25.12.tgz", - "integrity": "sha512-5jbb+2hhDHx5phYR2By8GTWEzn6I9UqR11Kwf22iKbNpYrsmRB18aX/9ivc5cabcUiAT/wM+YIZ6SG9QO6a8kg==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "android" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/darwin-arm64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/darwin-arm64/-/darwin-arm64-0.25.12.tgz", - "integrity": "sha512-N3zl+lxHCifgIlcMUP5016ESkeQjLj/959RxxNYIthIg+CQHInujFuXeWbWMgnTo4cp5XVHqFPmpyu9J65C1Yg==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "darwin" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/darwin-x64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/darwin-x64/-/darwin-x64-0.25.12.tgz", - "integrity": "sha512-HQ9ka4Kx21qHXwtlTUVbKJOAnmG1ipXhdWTmNXiPzPfWKpXqASVcWdnf2bnL73wgjNrFXAa3yYvBSd9pzfEIpA==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "darwin" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/freebsd-arm64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/freebsd-arm64/-/freebsd-arm64-0.25.12.tgz", - "integrity": "sha512-gA0Bx759+7Jve03K1S0vkOu5Lg/85dou3EseOGUes8flVOGxbhDDh/iZaoek11Y8mtyKPGF3vP8XhnkDEAmzeg==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "freebsd" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/freebsd-x64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/freebsd-x64/-/freebsd-x64-0.25.12.tgz", - "integrity": "sha512-TGbO26Yw2xsHzxtbVFGEXBFH0FRAP7gtcPE7P5yP7wGy7cXK2oO7RyOhL5NLiqTlBh47XhmIUXuGciXEqYFfBQ==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "freebsd" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/linux-arm": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/linux-arm/-/linux-arm-0.25.12.tgz", - "integrity": "sha512-lPDGyC1JPDou8kGcywY0YILzWlhhnRjdof3UlcoqYmS9El818LLfJJc3PXXgZHrHCAKs/Z2SeZtDJr5MrkxtOw==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/linux-arm64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/linux-arm64/-/linux-arm64-0.25.12.tgz", - "integrity": "sha512-8bwX7a8FghIgrupcxb4aUmYDLp8pX06rGh5HqDT7bB+8Rdells6mHvrFHHW2JAOPZUbnjUpKTLg6ECyzvas2AQ==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/linux-ia32": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/linux-ia32/-/linux-ia32-0.25.12.tgz", - "integrity": "sha512-0y9KrdVnbMM2/vG8KfU0byhUN+EFCny9+8g202gYqSSVMonbsCfLjUO+rCci7pM0WBEtz+oK/PIwHkzxkyharA==", - "cpu": [ - "ia32" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/linux-loong64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/linux-loong64/-/linux-loong64-0.25.12.tgz", - "integrity": "sha512-h///Lr5a9rib/v1GGqXVGzjL4TMvVTv+s1DPoxQdz7l/AYv6LDSxdIwzxkrPW438oUXiDtwM10o9PmwS/6Z0Ng==", - "cpu": [ - "loong64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/linux-mips64el": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/linux-mips64el/-/linux-mips64el-0.25.12.tgz", - "integrity": "sha512-iyRrM1Pzy9GFMDLsXn1iHUm18nhKnNMWscjmp4+hpafcZjrr2WbT//d20xaGljXDBYHqRcl8HnxbX6uaA/eGVw==", - "cpu": [ - "mips64el" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/linux-ppc64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/linux-ppc64/-/linux-ppc64-0.25.12.tgz", - "integrity": "sha512-9meM/lRXxMi5PSUqEXRCtVjEZBGwB7P/D4yT8UG/mwIdze2aV4Vo6U5gD3+RsoHXKkHCfSxZKzmDssVlRj1QQA==", - "cpu": [ - "ppc64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/linux-riscv64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/linux-riscv64/-/linux-riscv64-0.25.12.tgz", - "integrity": "sha512-Zr7KR4hgKUpWAwb1f3o5ygT04MzqVrGEGXGLnj15YQDJErYu/BGg+wmFlIDOdJp0PmB0lLvxFIOXZgFRrdjR0w==", - "cpu": [ - "riscv64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/linux-s390x": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/linux-s390x/-/linux-s390x-0.25.12.tgz", - "integrity": "sha512-MsKncOcgTNvdtiISc/jZs/Zf8d0cl/t3gYWX8J9ubBnVOwlk65UIEEvgBORTiljloIWnBzLs4qhzPkJcitIzIg==", - "cpu": [ - "s390x" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/linux-x64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/linux-x64/-/linux-x64-0.25.12.tgz", - "integrity": "sha512-uqZMTLr/zR/ed4jIGnwSLkaHmPjOjJvnm6TVVitAa08SLS9Z0VM8wIRx7gWbJB5/J54YuIMInDquWyYvQLZkgw==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/netbsd-arm64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/netbsd-arm64/-/netbsd-arm64-0.25.12.tgz", - "integrity": "sha512-xXwcTq4GhRM7J9A8Gv5boanHhRa/Q9KLVmcyXHCTaM4wKfIpWkdXiMog/KsnxzJ0A1+nD+zoecuzqPmCRyBGjg==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "netbsd" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/netbsd-x64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/netbsd-x64/-/netbsd-x64-0.25.12.tgz", - "integrity": "sha512-Ld5pTlzPy3YwGec4OuHh1aCVCRvOXdH8DgRjfDy/oumVovmuSzWfnSJg+VtakB9Cm0gxNO9BzWkj6mtO1FMXkQ==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "netbsd" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/openbsd-arm64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/openbsd-arm64/-/openbsd-arm64-0.25.12.tgz", - "integrity": "sha512-fF96T6KsBo/pkQI950FARU9apGNTSlZGsv1jZBAlcLL1MLjLNIWPBkj5NlSz8aAzYKg+eNqknrUJ24QBybeR5A==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "openbsd" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/openbsd-x64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/openbsd-x64/-/openbsd-x64-0.25.12.tgz", - "integrity": "sha512-MZyXUkZHjQxUvzK7rN8DJ3SRmrVrke8ZyRusHlP+kuwqTcfWLyqMOE3sScPPyeIXN/mDJIfGXvcMqCgYKekoQw==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "openbsd" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/openharmony-arm64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/openharmony-arm64/-/openharmony-arm64-0.25.12.tgz", - "integrity": "sha512-rm0YWsqUSRrjncSXGA7Zv78Nbnw4XL6/dzr20cyrQf7ZmRcsovpcRBdhD43Nuk3y7XIoW2OxMVvwuRvk9XdASg==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "openharmony" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/sunos-x64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/sunos-x64/-/sunos-x64-0.25.12.tgz", - "integrity": "sha512-3wGSCDyuTHQUzt0nV7bocDy72r2lI33QL3gkDNGkod22EsYl04sMf0qLb8luNKTOmgF/eDEDP5BFNwoBKH441w==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "sunos" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/win32-arm64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/win32-arm64/-/win32-arm64-0.25.12.tgz", - "integrity": "sha512-rMmLrur64A7+DKlnSuwqUdRKyd3UE7oPJZmnljqEptesKM8wx9J8gx5u0+9Pq0fQQW8vqeKebwNXdfOyP+8Bsg==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "win32" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/win32-ia32": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/win32-ia32/-/win32-ia32-0.25.12.tgz", - "integrity": "sha512-HkqnmmBoCbCwxUKKNPBixiWDGCpQGVsrQfJoVGYLPT41XWF8lHuE5N6WhVia2n4o5QK5M4tYr21827fNhi4byQ==", - "cpu": [ - "ia32" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "win32" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@esbuild/win32-x64": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/@esbuild/win32-x64/-/win32-x64-0.25.12.tgz", - "integrity": "sha512-alJC0uCZpTFrSL0CCDjcgleBXPnCrEAhTBILpeAp7M/OFgoqtAetfBzX0xM00MUsVVPpVjlPuMbREqnZCXaTnA==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "win32" - ], - "engines": { - "node": ">=18" - } - }, - "node_modules/@eslint-community/eslint-utils": { - "version": "4.9.1", - "resolved": "https://registry.npmjs.org/@eslint-community/eslint-utils/-/eslint-utils-4.9.1.tgz", - "integrity": "sha512-phrYmNiYppR7znFEdqgfWHXR6NCkZEK7hwWDHZUjit/2/U0r6XvkDl0SYnoM51Hq7FhCGdLDT6zxCCOY1hexsQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "eslint-visitor-keys": "^3.4.3" - }, - "engines": { - "node": "^12.22.0 || ^14.17.0 || >=16.0.0" - }, - "funding": { - "url": "https://opencollective.com/eslint" - }, - "peerDependencies": { - "eslint": "^6.0.0 || ^7.0.0 || >=8.0.0" - } - }, - "node_modules/@eslint-community/eslint-utils/node_modules/eslint-visitor-keys": { - "version": "3.4.3", - "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-3.4.3.tgz", - "integrity": "sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==", - "dev": true, - "license": "Apache-2.0", - "engines": { - "node": "^12.22.0 || ^14.17.0 || >=16.0.0" - }, - "funding": { - "url": "https://opencollective.com/eslint" - } - }, - "node_modules/@eslint-community/regexpp": { - "version": "4.12.2", - "resolved": "https://registry.npmjs.org/@eslint-community/regexpp/-/regexpp-4.12.2.tgz", - "integrity": "sha512-EriSTlt5OC9/7SXkRSCAhfSxxoSUgBm33OH+IkwbdpgoqsSsUg7y3uh+IICI/Qg4BBWr3U2i39RpmycbxMq4ew==", - "dev": true, - "license": "MIT", - "engines": { - "node": "^12.0.0 || ^14.0.0 || >=16.0.0" - } - }, - "node_modules/@eslint/config-array": { - "version": "0.21.1", - "resolved": "https://registry.npmjs.org/@eslint/config-array/-/config-array-0.21.1.tgz", - "integrity": "sha512-aw1gNayWpdI/jSYVgzN5pL0cfzU02GT3NBpeT/DXbx1/1x7ZKxFPd9bwrzygx/qiwIQiJ1sw/zD8qY/kRvlGHA==", - "dev": true, - "license": "Apache-2.0", - "dependencies": { - "@eslint/object-schema": "^2.1.7", - "debug": "^4.3.1", - "minimatch": "^3.1.2" - }, - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - } - }, - "node_modules/@eslint/config-helpers": { - "version": "0.4.2", - "resolved": "https://registry.npmjs.org/@eslint/config-helpers/-/config-helpers-0.4.2.tgz", - "integrity": "sha512-gBrxN88gOIf3R7ja5K9slwNayVcZgK6SOUORm2uBzTeIEfeVaIhOpCtTox3P6R7o2jLFwLFTLnC7kU/RGcYEgw==", - "dev": true, - "license": "Apache-2.0", - "dependencies": { - "@eslint/core": "^0.17.0" - }, - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - } - }, - "node_modules/@eslint/core": { - "version": "0.17.0", - "resolved": "https://registry.npmjs.org/@eslint/core/-/core-0.17.0.tgz", - "integrity": "sha512-yL/sLrpmtDaFEiUj1osRP4TI2MDz1AddJL+jZ7KSqvBuliN4xqYY54IfdN8qD8Toa6g1iloph1fxQNkjOxrrpQ==", - "dev": true, - "license": "Apache-2.0", - "dependencies": { - "@types/json-schema": "^7.0.15" - }, - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - } - }, - "node_modules/@eslint/eslintrc": { - "version": "3.3.3", - "resolved": "https://registry.npmjs.org/@eslint/eslintrc/-/eslintrc-3.3.3.tgz", - "integrity": "sha512-Kr+LPIUVKz2qkx1HAMH8q1q6azbqBAsXJUxBl/ODDuVPX45Z9DfwB8tPjTi6nNZ8BuM3nbJxC5zCAg5elnBUTQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "ajv": "^6.12.4", - "debug": "^4.3.2", - "espree": "^10.0.1", - "globals": "^14.0.0", - "ignore": "^5.2.0", - "import-fresh": "^3.2.1", - "js-yaml": "^4.1.1", - "minimatch": "^3.1.2", - "strip-json-comments": "^3.1.1" - }, - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - }, - "funding": { - "url": "https://opencollective.com/eslint" - } - }, - "node_modules/@eslint/eslintrc/node_modules/ignore": { - "version": "5.3.2", - "resolved": "https://registry.npmjs.org/ignore/-/ignore-5.3.2.tgz", - "integrity": "sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 4" - } - }, - "node_modules/@eslint/js": { - "version": "9.39.2", - "resolved": "https://registry.npmjs.org/@eslint/js/-/js-9.39.2.tgz", - "integrity": "sha512-q1mjIoW1VX4IvSocvM/vbTiveKC4k9eLrajNEuSsmjymSDEbpGddtpfOoN7YGAqBK3NG+uqo8ia4PDTt8buCYA==", - "dev": true, - "license": "MIT", - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - }, - "funding": { - "url": "https://eslint.org/donate" - } - }, - "node_modules/@eslint/object-schema": { - "version": "2.1.7", - "resolved": "https://registry.npmjs.org/@eslint/object-schema/-/object-schema-2.1.7.tgz", - "integrity": "sha512-VtAOaymWVfZcmZbp6E2mympDIHvyjXs/12LqWYjVw6qjrfF+VK+fyG33kChz3nnK+SU5/NeHOqrTEHS8sXO3OA==", - "dev": true, - "license": "Apache-2.0", - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - } - }, - "node_modules/@eslint/plugin-kit": { - "version": "0.4.1", - "resolved": "https://registry.npmjs.org/@eslint/plugin-kit/-/plugin-kit-0.4.1.tgz", - "integrity": "sha512-43/qtrDUokr7LJqoF2c3+RInu/t4zfrpYdoSDfYyhg52rwLV6TnOvdG4fXm7IkSB3wErkcmJS9iEhjVtOSEjjA==", - "dev": true, - "license": "Apache-2.0", - "dependencies": { - "@eslint/core": "^0.17.0", - "levn": "^0.4.1" - }, - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - } - }, - "node_modules/@expressive-code/core": { - "version": "0.41.6", - "resolved": "https://registry.npmjs.org/@expressive-code/core/-/core-0.41.6.tgz", - "integrity": "sha512-FvJQP+hG0jWi/FLBSmvHInDqWR7jNANp9PUDjdMqSshHb0y7sxx3vHuoOr6SgXjWw+MGLqorZyPQ0aAlHEok6g==", - "dev": true, - "license": "MIT", - "dependencies": { - "@ctrl/tinycolor": "^4.0.4", - "hast-util-select": "^6.0.2", - "hast-util-to-html": "^9.0.1", - "hast-util-to-text": "^4.0.1", - "hastscript": "^9.0.0", - "postcss": "^8.4.38", - "postcss-nested": "^6.0.1", - "unist-util-visit": "^5.0.0", - "unist-util-visit-parents": "^6.0.1" - } - }, - "node_modules/@expressive-code/plugin-frames": { - "version": "0.41.6", - "resolved": "https://registry.npmjs.org/@expressive-code/plugin-frames/-/plugin-frames-0.41.6.tgz", - "integrity": "sha512-d+hkSYXIQot6fmYnOmWAM+7TNWRv/dhfjMsNq+mIZz8Tb4mPHOcgcfZeEM5dV9TDL0ioQNvtcqQNuzA1sRPjxg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@expressive-code/core": "^0.41.6" - } - }, - "node_modules/@expressive-code/plugin-shiki": { - "version": "0.41.6", - "resolved": "https://registry.npmjs.org/@expressive-code/plugin-shiki/-/plugin-shiki-0.41.6.tgz", - "integrity": "sha512-Y6zmKBmsIUtWTzdefqlzm/h9Zz0Rc4gNdt2GTIH7fhHH2I9+lDYCa27BDwuBhjqcos6uK81Aca9dLUC4wzN+ng==", - "dev": true, - "license": "MIT", - "dependencies": { - "@expressive-code/core": "^0.41.6", - "shiki": "^3.2.2" - } - }, - "node_modules/@expressive-code/plugin-text-markers": { - "version": "0.41.6", - "resolved": "https://registry.npmjs.org/@expressive-code/plugin-text-markers/-/plugin-text-markers-0.41.6.tgz", - "integrity": "sha512-PBFa1wGyYzRExMDzBmAWC6/kdfG1oLn4pLpBeTfIRrALPjcGA/59HP3e7q9J0Smk4pC7U+lWkA2LHR8FYV8U7Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "@expressive-code/core": "^0.41.6" - } - }, - "node_modules/@humanfs/core": { - "version": "0.19.1", - "resolved": "https://registry.npmjs.org/@humanfs/core/-/core-0.19.1.tgz", - "integrity": "sha512-5DyQ4+1JEUzejeK1JGICcideyfUbGixgS9jNgex5nqkW+cY7WZhxBigmieN5Qnw9ZosSNVC9KQKyb+GUaGyKUA==", - "dev": true, - "license": "Apache-2.0", - "engines": { - "node": ">=18.18.0" - } - }, - "node_modules/@humanfs/node": { - "version": "0.16.7", - "resolved": "https://registry.npmjs.org/@humanfs/node/-/node-0.16.7.tgz", - "integrity": "sha512-/zUx+yOsIrG4Y43Eh2peDeKCxlRt/gET6aHfaKpuq267qXdYDFViVHfMaLyygZOnl0kGWxFIgsBy8QFuTLUXEQ==", - "dev": true, - "license": "Apache-2.0", - "dependencies": { - "@humanfs/core": "^0.19.1", - "@humanwhocodes/retry": "^0.4.0" - }, - "engines": { - "node": ">=18.18.0" - } - }, - "node_modules/@humanwhocodes/module-importer": { - "version": "1.0.1", - "resolved": "https://registry.npmjs.org/@humanwhocodes/module-importer/-/module-importer-1.0.1.tgz", - "integrity": "sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==", - "dev": true, - "license": "Apache-2.0", - "engines": { - "node": ">=12.22" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/nzakas" - } - }, - "node_modules/@humanwhocodes/retry": { - "version": "0.4.3", - "resolved": "https://registry.npmjs.org/@humanwhocodes/retry/-/retry-0.4.3.tgz", - "integrity": "sha512-bV0Tgo9K4hfPCek+aMAn81RppFKv2ySDQeMoSZuvTASywNTnVJCArCZE2FWqpvIatKu7VMRLWlR1EazvVhDyhQ==", - "dev": true, - "license": "Apache-2.0", - "engines": { - "node": ">=18.18" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/nzakas" - } - }, - "node_modules/@img/colour": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/@img/colour/-/colour-1.0.0.tgz", - "integrity": "sha512-A5P/LfWGFSl6nsckYtjw9da+19jB8hkJ6ACTGcDfEJ0aE+l2n2El7dsVM7UVHZQ9s2lmYMWlrS21YLy2IR1LUw==", - "dev": true, - "license": "MIT", - "optional": true, - "engines": { - "node": ">=18" - } - }, - "node_modules/@img/sharp-darwin-arm64": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/@img/sharp-darwin-arm64/-/sharp-darwin-arm64-0.33.5.tgz", - "integrity": "sha512-UT4p+iz/2H4twwAoLCqfA9UH5pI6DggwKEGuaPy7nCVQ8ZsiY5PIcrRvD1DzuY3qYL07NtIQcWnBSY/heikIFQ==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "darwin" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-darwin-arm64": "1.0.4" - } - }, - "node_modules/@img/sharp-darwin-x64": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/@img/sharp-darwin-x64/-/sharp-darwin-x64-0.33.5.tgz", - "integrity": "sha512-fyHac4jIc1ANYGRDxtiqelIbdWkIuQaI84Mv45KvGRRxSAa7o7d1ZKAOBaYbnepLC1WqxfpimdeWfvqqSGwR2Q==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "darwin" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-darwin-x64": "1.0.4" - } - }, - "node_modules/@img/sharp-libvips-darwin-arm64": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-darwin-arm64/-/sharp-libvips-darwin-arm64-1.0.4.tgz", - "integrity": "sha512-XblONe153h0O2zuFfTAbQYAX2JhYmDHeWikp1LM9Hul9gVPjFY427k6dFEcOL72O01QxQsWi761svJ/ev9xEDg==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "darwin" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-libvips-darwin-x64": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-darwin-x64/-/sharp-libvips-darwin-x64-1.0.4.tgz", - "integrity": "sha512-xnGR8YuZYfJGmWPvmlunFaWJsb9T/AO2ykoP3Fz/0X5XV2aoYBPkX6xqCQvUTKKiLddarLaxpzNe+b1hjeWHAQ==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "darwin" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-libvips-linux-arm": { - "version": "1.0.5", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-arm/-/sharp-libvips-linux-arm-1.0.5.tgz", - "integrity": "sha512-gvcC4ACAOPRNATg/ov8/MnbxFDJqf/pDePbBnuBDcjsI8PssmjoKMAz4LtLaVi+OnSb5FK/yIOamqDwGmXW32g==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-libvips-linux-arm64": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-arm64/-/sharp-libvips-linux-arm64-1.0.4.tgz", - "integrity": "sha512-9B+taZ8DlyyqzZQnoeIvDVR/2F4EbMepXMc/NdVbkzsJbzkUjhXv/70GQJ7tdLA4YJgNP25zukcxpX2/SueNrA==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-libvips-linux-ppc64": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-ppc64/-/sharp-libvips-linux-ppc64-1.2.4.tgz", - "integrity": "sha512-FMuvGijLDYG6lW+b/UvyilUWu5Ayu+3r2d1S8notiGCIyYU/76eig1UfMmkZ7vwgOrzKzlQbFSuQfgm7GYUPpA==", - "cpu": [ - "ppc64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-libvips-linux-riscv64": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-riscv64/-/sharp-libvips-linux-riscv64-1.2.4.tgz", - "integrity": "sha512-oVDbcR4zUC0ce82teubSm+x6ETixtKZBh/qbREIOcI3cULzDyb18Sr/Wcyx7NRQeQzOiHTNbZFF1UwPS2scyGA==", - "cpu": [ - "riscv64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-libvips-linux-s390x": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-s390x/-/sharp-libvips-linux-s390x-1.0.4.tgz", - "integrity": "sha512-u7Wz6ntiSSgGSGcjZ55im6uvTrOxSIS8/dgoVMoiGE9I6JAfU50yH5BoDlYA1tcuGS7g/QNtetJnxA6QEsCVTA==", - "cpu": [ - "s390x" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-libvips-linux-x64": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-x64/-/sharp-libvips-linux-x64-1.0.4.tgz", - "integrity": "sha512-MmWmQ3iPFZr0Iev+BAgVMb3ZyC4KeFc3jFxnNbEPas60e1cIfevbtuyf9nDGIzOaW9PdnDciJm+wFFaTlj5xYw==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-libvips-linuxmusl-arm64": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linuxmusl-arm64/-/sharp-libvips-linuxmusl-arm64-1.0.4.tgz", - "integrity": "sha512-9Ti+BbTYDcsbp4wfYib8Ctm1ilkugkA/uscUn6UXK1ldpC1JjiXbLfFZtRlBhjPZ5o1NCLiDbg8fhUPKStHoTA==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-libvips-linuxmusl-x64": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linuxmusl-x64/-/sharp-libvips-linuxmusl-x64-1.0.4.tgz", - "integrity": "sha512-viYN1KX9m+/hGkJtvYYp+CCLgnJXwiQB39damAO7WMdKWlIhmYTfHjwSbQeUK/20vY154mwezd9HflVFM1wVSw==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-linux-arm": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linux-arm/-/sharp-linux-arm-0.33.5.tgz", - "integrity": "sha512-JTS1eldqZbJxjvKaAkxhZmBqPRGmxgu+qFKSInv8moZ2AmT5Yib3EQ1c6gp493HvrvV8QgdOXdyaIBrhvFhBMQ==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linux-arm": "1.0.5" - } - }, - "node_modules/@img/sharp-linux-arm64": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linux-arm64/-/sharp-linux-arm64-0.33.5.tgz", - "integrity": "sha512-JMVv+AMRyGOHtO1RFBiJy/MBsgz0x4AWrT6QoEVVTyh1E39TrCUpTRI7mx9VksGX4awWASxqCYLCV4wBZHAYxA==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linux-arm64": "1.0.4" - } - }, - "node_modules/@img/sharp-linux-ppc64": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linux-ppc64/-/sharp-linux-ppc64-0.34.5.tgz", - "integrity": "sha512-7zznwNaqW6YtsfrGGDA6BRkISKAAE1Jo0QdpNYXNMHu2+0dTrPflTLNkpc8l7MUP5M16ZJcUvysVWWrMefZquA==", - "cpu": [ - "ppc64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linux-ppc64": "1.2.4" - } - }, - "node_modules/@img/sharp-linux-riscv64": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linux-riscv64/-/sharp-linux-riscv64-0.34.5.tgz", - "integrity": "sha512-51gJuLPTKa7piYPaVs8GmByo7/U7/7TZOq+cnXJIHZKavIRHAP77e3N2HEl3dgiqdD/w0yUfiJnII77PuDDFdw==", - "cpu": [ - "riscv64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linux-riscv64": "1.2.4" - } - }, - "node_modules/@img/sharp-linux-s390x": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linux-s390x/-/sharp-linux-s390x-0.33.5.tgz", - "integrity": "sha512-y/5PCd+mP4CA/sPDKl2961b+C9d+vPAveS33s6Z3zfASk2j5upL6fXVPZi7ztePZ5CuH+1kW8JtvxgbuXHRa4Q==", - "cpu": [ - "s390x" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linux-s390x": "1.0.4" - } - }, - "node_modules/@img/sharp-linux-x64": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linux-x64/-/sharp-linux-x64-0.33.5.tgz", - "integrity": "sha512-opC+Ok5pRNAzuvq1AG0ar+1owsu842/Ab+4qvU879ippJBHvyY5n2mxF1izXqkPYlGuP/M556uh53jRLJmzTWA==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linux-x64": "1.0.4" - } - }, - "node_modules/@img/sharp-linuxmusl-arm64": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linuxmusl-arm64/-/sharp-linuxmusl-arm64-0.33.5.tgz", - "integrity": "sha512-XrHMZwGQGvJg2V/oRSUfSAfjfPxO+4DkiRh6p2AFjLQztWUuY/o8Mq0eMQVIY7HJ1CDQUJlxGGZRw1a5bqmd1g==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linuxmusl-arm64": "1.0.4" - } - }, - "node_modules/@img/sharp-linuxmusl-x64": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linuxmusl-x64/-/sharp-linuxmusl-x64-0.33.5.tgz", - "integrity": "sha512-WT+d/cgqKkkKySYmqoZ8y3pxx7lx9vVejxW/W4DOFMYVSkErR+w7mf2u8m/y4+xHe7yY9DAXQMWQhpnMuFfScw==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linuxmusl-x64": "1.0.4" - } - }, - "node_modules/@img/sharp-wasm32": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/@img/sharp-wasm32/-/sharp-wasm32-0.33.5.tgz", - "integrity": "sha512-ykUW4LVGaMcU9lu9thv85CbRMAwfeadCJHRsg2GmeRa/cJxsVY9Rbd57JcMxBkKHag5U/x7TSBpScF4U8ElVzg==", - "cpu": [ - "wasm32" - ], - "dev": true, - "license": "Apache-2.0 AND LGPL-3.0-or-later AND MIT", - "optional": true, - "dependencies": { - "@emnapi/runtime": "^1.2.0" - }, - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-win32-arm64": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-win32-arm64/-/sharp-win32-arm64-0.34.5.tgz", - "integrity": "sha512-WQ3AgWCWYSb2yt+IG8mnC6Jdk9Whs7O0gxphblsLvdhSpSTtmu69ZG1Gkb6NuvxsNACwiPV6cNSZNzt0KPsw7g==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "Apache-2.0 AND LGPL-3.0-or-later", - "optional": true, - "os": [ - "win32" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-win32-ia32": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/@img/sharp-win32-ia32/-/sharp-win32-ia32-0.33.5.tgz", - "integrity": "sha512-T36PblLaTwuVJ/zw/LaH0PdZkRz5rd3SmMHX8GSmR7vtNSP5Z6bQkExdSK7xGWyxLw4sUknBuugTelgw2faBbQ==", - "cpu": [ - "ia32" - ], - "dev": true, - "license": "Apache-2.0 AND LGPL-3.0-or-later", - "optional": true, - "os": [ - "win32" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@img/sharp-win32-x64": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/@img/sharp-win32-x64/-/sharp-win32-x64-0.33.5.tgz", - "integrity": "sha512-MpY/o8/8kj+EcnxwvrP4aTJSWw/aZ7JIGR4aBeZkZw5B7/Jn+tY9/VNwtcoGmdT7GfggGIU4kygOMSbYnOrAbg==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "Apache-2.0 AND LGPL-3.0-or-later", - "optional": true, - "os": [ - "win32" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/@isaacs/balanced-match": { - "version": "4.0.1", - "resolved": "https://registry.npmjs.org/@isaacs/balanced-match/-/balanced-match-4.0.1.tgz", - "integrity": "sha512-yzMTt9lEb8Gv7zRioUilSglI0c0smZ9k5D65677DLWLtWJaXIS3CqcGyUFByYKlnUj6TkjLVs54fBl6+TiGQDQ==", - "license": "MIT", - "engines": { - "node": "20 || >=22" - } - }, - "node_modules/@isaacs/brace-expansion": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/@isaacs/brace-expansion/-/brace-expansion-5.0.0.tgz", - "integrity": "sha512-ZT55BDLV0yv0RBm2czMiZ+SqCGO7AvmOM3G/w2xhVPH+te0aKgFjmBvGlL1dH+ql2tgGO3MVrbb3jCKyvpgnxA==", - "license": "MIT", - "dependencies": { - "@isaacs/balanced-match": "^4.0.1" - }, - "engines": { - "node": "20 || >=22" - } - }, - "node_modules/@isaacs/cliui": { - "version": "8.0.2", - "resolved": "https://registry.npmjs.org/@isaacs/cliui/-/cliui-8.0.2.tgz", - "integrity": "sha512-O8jcjabXaleOG9DQ0+ARXWZBTfnP4WNAqzuiJK7ll44AmxGKv/J2M4TPjxjY3znBCfvBXFzucm1twdyFybFqEA==", - "license": "ISC", - "dependencies": { - "string-width": "^5.1.2", - "string-width-cjs": "npm:string-width@^4.2.0", - "strip-ansi": "^7.0.1", - "strip-ansi-cjs": "npm:strip-ansi@^6.0.1", - "wrap-ansi": "^8.1.0", - "wrap-ansi-cjs": "npm:wrap-ansi@^7.0.0" - }, - "engines": { - "node": ">=12" - } - }, - "node_modules/@isaacs/cliui/node_modules/ansi-styles": { - "version": "6.2.3", - "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-6.2.3.tgz", - "integrity": "sha512-4Dj6M28JB+oAH8kFkTLUo+a2jwOFkuqb3yucU0CANcRRUbxS0cP0nZYCGjcc3BNXwRIsUVmDGgzawme7zvJHvg==", - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/chalk/ansi-styles?sponsor=1" - } - }, - "node_modules/@isaacs/cliui/node_modules/emoji-regex": { - "version": "9.2.2", - "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-9.2.2.tgz", - "integrity": "sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg==", - "license": "MIT" - }, - "node_modules/@isaacs/cliui/node_modules/string-width": { - "version": "5.1.2", - "resolved": "https://registry.npmjs.org/string-width/-/string-width-5.1.2.tgz", - "integrity": "sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA==", - "license": "MIT", - "dependencies": { - "eastasianwidth": "^0.2.0", - "emoji-regex": "^9.2.2", - "strip-ansi": "^7.0.1" - }, - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/@isaacs/cliui/node_modules/wrap-ansi": { - "version": "8.1.0", - "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-8.1.0.tgz", - "integrity": "sha512-si7QWI6zUMq56bESFvagtmzMdGOtoxfR+Sez11Mobfc7tm+VkUckk9bW2UeffTGVUbOksxmSw0AA2gs8g71NCQ==", - "license": "MIT", - "dependencies": { - "ansi-styles": "^6.1.0", - "string-width": "^5.0.1", - "strip-ansi": "^7.0.1" - }, - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/chalk/wrap-ansi?sponsor=1" - } - }, - "node_modules/@istanbuljs/load-nyc-config": { - "version": "1.1.0", - "resolved": "https://registry.npmjs.org/@istanbuljs/load-nyc-config/-/load-nyc-config-1.1.0.tgz", - "integrity": "sha512-VjeHSlIzpv/NyD3N0YuHfXOPDIixcA1q2ZV98wsMqcYlPmv2n3Yb2lYP9XMElnaFVXg5A7YLTeLu6V84uQDjmQ==", - "dev": true, - "license": "ISC", - "dependencies": { - "camelcase": "^5.3.1", - "find-up": "^4.1.0", - "get-package-type": "^0.1.0", - "js-yaml": "^3.13.1", - "resolve-from": "^5.0.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/@istanbuljs/load-nyc-config/node_modules/argparse": { - "version": "1.0.10", - "resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.10.tgz", - "integrity": "sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==", - "dev": true, - "license": "MIT", - "dependencies": { - "sprintf-js": "~1.0.2" - } - }, - "node_modules/@istanbuljs/load-nyc-config/node_modules/camelcase": { - "version": "5.3.1", - "resolved": "https://registry.npmjs.org/camelcase/-/camelcase-5.3.1.tgz", - "integrity": "sha512-L28STB170nwWS63UjtlEOE3dldQApaJXZkOI1uMFfzf3rRuPegHaHesyee+YxQ+W6SvRDQV6UrdOdRiR153wJg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/@istanbuljs/load-nyc-config/node_modules/find-up": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz", - "integrity": "sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==", - "dev": true, - "license": "MIT", - "dependencies": { - "locate-path": "^5.0.0", - "path-exists": "^4.0.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/@istanbuljs/load-nyc-config/node_modules/js-yaml": { - "version": "3.14.2", - "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.14.2.tgz", - "integrity": "sha512-PMSmkqxr106Xa156c2M265Z+FTrPl+oxd/rgOQy2tijQeK5TxQ43psO1ZCwhVOSdnn+RzkzlRz/eY4BgJBYVpg==", - "dev": true, - "license": "MIT", - "dependencies": { - "argparse": "^1.0.7", - "esprima": "^4.0.0" - }, - "bin": { - "js-yaml": "bin/js-yaml.js" - } - }, - "node_modules/@istanbuljs/load-nyc-config/node_modules/locate-path": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz", - "integrity": "sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==", - "dev": true, - "license": "MIT", - "dependencies": { - "p-locate": "^4.1.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/@istanbuljs/load-nyc-config/node_modules/p-limit": { - "version": "2.3.0", - "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz", - "integrity": "sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==", - "dev": true, - "license": "MIT", - "dependencies": { - "p-try": "^2.0.0" - }, - "engines": { - "node": ">=6" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/@istanbuljs/load-nyc-config/node_modules/p-locate": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz", - "integrity": "sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==", - "dev": true, - "license": "MIT", - "dependencies": { - "p-limit": "^2.2.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/@istanbuljs/load-nyc-config/node_modules/resolve-from": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-5.0.0.tgz", - "integrity": "sha512-qYg9KP24dD5qka9J47d0aVky0N+b4fTU89LN9iDnjB5waksiC49rvMB0PrUJQGoTmH50XPiqOvAjDfaijGxYZw==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/@istanbuljs/schema": { - "version": "0.1.3", - "resolved": "https://registry.npmjs.org/@istanbuljs/schema/-/schema-0.1.3.tgz", - "integrity": "sha512-ZXRY4jNvVgSVQ8DL3LTcakaAtXwTVUxE81hslsyD2AtoXW/wVob10HkOJ1X/pAlcI7D+2YoZKg5do8G/w6RYgA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/@jest/console": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/console/-/console-30.2.0.tgz", - "integrity": "sha512-+O1ifRjkvYIkBqASKWgLxrpEhQAAE7hY77ALLUufSk5717KfOShg6IbqLmdsLMPdUiFvA2kTs0R7YZy+l0IzZQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/types": "30.2.0", - "@types/node": "*", - "chalk": "^4.1.2", - "jest-message-util": "30.2.0", - "jest-util": "30.2.0", - "slash": "^3.0.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/core": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/core/-/core-30.2.0.tgz", - "integrity": "sha512-03W6IhuhjqTlpzh/ojut/pDB2LPRygyWX8ExpgHtQA8H/3K7+1vKmcINx5UzeOX1se6YEsBsOHQ1CRzf3fOwTQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/console": "30.2.0", - "@jest/pattern": "30.0.1", - "@jest/reporters": "30.2.0", - "@jest/test-result": "30.2.0", - "@jest/transform": "30.2.0", - "@jest/types": "30.2.0", - "@types/node": "*", - "ansi-escapes": "^4.3.2", - "chalk": "^4.1.2", - "ci-info": "^4.2.0", - "exit-x": "^0.2.2", - "graceful-fs": "^4.2.11", - "jest-changed-files": "30.2.0", - "jest-config": "30.2.0", - "jest-haste-map": "30.2.0", - "jest-message-util": "30.2.0", - "jest-regex-util": "30.0.1", - "jest-resolve": "30.2.0", - "jest-resolve-dependencies": "30.2.0", - "jest-runner": "30.2.0", - "jest-runtime": "30.2.0", - "jest-snapshot": "30.2.0", - "jest-util": "30.2.0", - "jest-validate": "30.2.0", - "jest-watcher": "30.2.0", - "micromatch": "^4.0.8", - "pretty-format": "30.2.0", - "slash": "^3.0.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - }, - "peerDependencies": { - "node-notifier": "^8.0.1 || ^9.0.0 || ^10.0.0" - }, - "peerDependenciesMeta": { - "node-notifier": { - "optional": true - } - } - }, - "node_modules/@jest/diff-sequences": { - "version": "30.0.1", - "resolved": "https://registry.npmjs.org/@jest/diff-sequences/-/diff-sequences-30.0.1.tgz", - "integrity": "sha512-n5H8QLDJ47QqbCNn5SuFjCRDrOLEZ0h8vAHCK5RL9Ls7Xa8AQLa/YxAc9UjFqoEDM48muwtBGjtMY5cr0PLDCw==", - "dev": true, - "license": "MIT", - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/environment": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/environment/-/environment-30.2.0.tgz", - "integrity": "sha512-/QPTL7OBJQ5ac09UDRa3EQes4gt1FTEG/8jZ/4v5IVzx+Cv7dLxlVIvfvSVRiiX2drWyXeBjkMSR8hvOWSog5g==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/fake-timers": "30.2.0", - "@jest/types": "30.2.0", - "@types/node": "*", - "jest-mock": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/expect": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/expect/-/expect-30.2.0.tgz", - "integrity": "sha512-V9yxQK5erfzx99Sf+7LbhBwNWEZ9eZay8qQ9+JSC0TrMR1pMDHLMY+BnVPacWU6Jamrh252/IKo4F1Xn/zfiqA==", - "dev": true, - "license": "MIT", - "dependencies": { - "expect": "30.2.0", - "jest-snapshot": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/expect-utils": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/expect-utils/-/expect-utils-30.2.0.tgz", - "integrity": "sha512-1JnRfhqpD8HGpOmQp180Fo9Zt69zNtC+9lR+kT7NVL05tNXIi+QC8Csz7lfidMoVLPD3FnOtcmp0CEFnxExGEA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/get-type": "30.1.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/fake-timers": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/fake-timers/-/fake-timers-30.2.0.tgz", - "integrity": "sha512-HI3tRLjRxAbBy0VO8dqqm7Hb2mIa8d5bg/NJkyQcOk7V118ObQML8RC5luTF/Zsg4474a+gDvhce7eTnP4GhYw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/types": "30.2.0", - "@sinonjs/fake-timers": "^13.0.0", - "@types/node": "*", - "jest-message-util": "30.2.0", - "jest-mock": "30.2.0", - "jest-util": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/get-type": { - "version": "30.1.0", - "resolved": "https://registry.npmjs.org/@jest/get-type/-/get-type-30.1.0.tgz", - "integrity": "sha512-eMbZE2hUnx1WV0pmURZY9XoXPkUYjpc55mb0CrhtdWLtzMQPFvu/rZkTLZFTsdaVQa+Tr4eWAteqcUzoawq/uA==", - "dev": true, - "license": "MIT", - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/globals": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/globals/-/globals-30.2.0.tgz", - "integrity": "sha512-b63wmnKPaK+6ZZfpYhz9K61oybvbI1aMcIs80++JI1O1rR1vaxHUCNqo3ITu6NU0d4V34yZFoHMn/uoKr/Rwfw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/environment": "30.2.0", - "@jest/expect": "30.2.0", - "@jest/types": "30.2.0", - "jest-mock": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/pattern": { - "version": "30.0.1", - "resolved": "https://registry.npmjs.org/@jest/pattern/-/pattern-30.0.1.tgz", - "integrity": "sha512-gWp7NfQW27LaBQz3TITS8L7ZCQ0TLvtmI//4OwlQRx4rnWxcPNIYjxZpDcN4+UlGxgm3jS5QPz8IPTCkb59wZA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/node": "*", - "jest-regex-util": "30.0.1" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/reporters": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/reporters/-/reporters-30.2.0.tgz", - "integrity": "sha512-DRyW6baWPqKMa9CzeiBjHwjd8XeAyco2Vt8XbcLFjiwCOEKOvy82GJ8QQnJE9ofsxCMPjH4MfH8fCWIHHDKpAQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@bcoe/v8-coverage": "^0.2.3", - "@jest/console": "30.2.0", - "@jest/test-result": "30.2.0", - "@jest/transform": "30.2.0", - "@jest/types": "30.2.0", - "@jridgewell/trace-mapping": "^0.3.25", - "@types/node": "*", - "chalk": "^4.1.2", - "collect-v8-coverage": "^1.0.2", - "exit-x": "^0.2.2", - "glob": "^10.3.10", - "graceful-fs": "^4.2.11", - "istanbul-lib-coverage": "^3.0.0", - "istanbul-lib-instrument": "^6.0.0", - "istanbul-lib-report": "^3.0.0", - "istanbul-lib-source-maps": "^5.0.0", - "istanbul-reports": "^3.1.3", - "jest-message-util": "30.2.0", - "jest-util": "30.2.0", - "jest-worker": "30.2.0", - "slash": "^3.0.0", - "string-length": "^4.0.2", - "v8-to-istanbul": "^9.0.1" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - }, - "peerDependencies": { - "node-notifier": "^8.0.1 || ^9.0.0 || ^10.0.0" - }, - "peerDependenciesMeta": { - "node-notifier": { - "optional": true - } - } - }, - "node_modules/@jest/reporters/node_modules/@bcoe/v8-coverage": { - "version": "0.2.3", - "resolved": "https://registry.npmjs.org/@bcoe/v8-coverage/-/v8-coverage-0.2.3.tgz", - "integrity": "sha512-0hYQ8SB4Db5zvZB4axdMHGwEaQjkZzFjQiN9LVYvIFB2nSUHW9tYpxWriPrWDASIxiaXax83REcLxuSdnGPZtw==", - "dev": true, - "license": "MIT" - }, - "node_modules/@jest/reporters/node_modules/brace-expansion": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.2.tgz", - "integrity": "sha512-Jt0vHyM+jmUBqojB7E1NIYadt0vI0Qxjxd2TErW94wDz+E2LAm5vKMXXwg6ZZBTHPuUlDgQHKXvjGBdfcF1ZDQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "balanced-match": "^1.0.0" - } - }, - "node_modules/@jest/reporters/node_modules/glob": { - "version": "10.5.0", - "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz", - "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==", - "dev": true, - "license": "ISC", - "dependencies": { - "foreground-child": "^3.1.0", - "jackspeak": "^3.1.2", - "minimatch": "^9.0.4", - "minipass": "^7.1.2", - "package-json-from-dist": "^1.0.0", - "path-scurry": "^1.11.1" - }, - "bin": { - "glob": "dist/esm/bin.mjs" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/@jest/reporters/node_modules/jackspeak": { - "version": "3.4.3", - "resolved": "https://registry.npmjs.org/jackspeak/-/jackspeak-3.4.3.tgz", - "integrity": "sha512-OGlZQpz2yfahA/Rd1Y8Cd9SIEsqvXkLVoSw/cgwhnhFMDbsQFeZYoJJ7bIZBS9BcamUW96asq/npPWugM+RQBw==", - "dev": true, - "license": "BlueOak-1.0.0", - "dependencies": { - "@isaacs/cliui": "^8.0.2" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - }, - "optionalDependencies": { - "@pkgjs/parseargs": "^0.11.0" - } - }, - "node_modules/@jest/reporters/node_modules/lru-cache": { - "version": "10.4.3", - "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-10.4.3.tgz", - "integrity": "sha512-JNAzZcXrCt42VGLuYz0zfAzDfAvJWW6AfYlDBQyDV5DClI2m5sAmK+OIO7s59XfsRsWHp02jAJrRadPRGTt6SQ==", - "dev": true, - "license": "ISC" - }, - "node_modules/@jest/reporters/node_modules/minimatch": { - "version": "9.0.5", - "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz", - "integrity": "sha512-G6T0ZX48xgozx7587koeX9Ys2NYy6Gmv//P89sEte9V9whIapMNF4idKxnW2QtCcLiTWlb/wfCabAtAFWhhBow==", - "dev": true, - "license": "ISC", - "dependencies": { - "brace-expansion": "^2.0.1" - }, - "engines": { - "node": ">=16 || 14 >=14.17" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/@jest/reporters/node_modules/path-scurry": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/path-scurry/-/path-scurry-1.11.1.tgz", - "integrity": "sha512-Xa4Nw17FS9ApQFJ9umLiJS4orGjm7ZzwUrwamcGQuHSzDyth9boKDaycYdDcZDuqYATXw4HFXgaqWTctW/v1HA==", - "dev": true, - "license": "BlueOak-1.0.0", - "dependencies": { - "lru-cache": "^10.2.0", - "minipass": "^5.0.0 || ^6.0.2 || ^7.0.0" - }, - "engines": { - "node": ">=16 || 14 >=14.18" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/@jest/schemas": { - "version": "30.0.5", - "resolved": "https://registry.npmjs.org/@jest/schemas/-/schemas-30.0.5.tgz", - "integrity": "sha512-DmdYgtezMkh3cpU8/1uyXakv3tJRcmcXxBOcO0tbaozPwpmh4YMsnWrQm9ZmZMfa5ocbxzbFk6O4bDPEc/iAnA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@sinclair/typebox": "^0.34.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/snapshot-utils": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/snapshot-utils/-/snapshot-utils-30.2.0.tgz", - "integrity": "sha512-0aVxM3RH6DaiLcjj/b0KrIBZhSX1373Xci4l3cW5xiUWPctZ59zQ7jj4rqcJQ/Z8JuN/4wX3FpJSa3RssVvCug==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/types": "30.2.0", - "chalk": "^4.1.2", - "graceful-fs": "^4.2.11", - "natural-compare": "^1.4.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/source-map": { - "version": "30.0.1", - "resolved": "https://registry.npmjs.org/@jest/source-map/-/source-map-30.0.1.tgz", - "integrity": "sha512-MIRWMUUR3sdbP36oyNyhbThLHyJ2eEDClPCiHVbrYAe5g3CHRArIVpBw7cdSB5fr+ofSfIb2Tnsw8iEHL0PYQg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jridgewell/trace-mapping": "^0.3.25", - "callsites": "^3.1.0", - "graceful-fs": "^4.2.11" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/test-result": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/test-result/-/test-result-30.2.0.tgz", - "integrity": "sha512-RF+Z+0CCHkARz5HT9mcQCBulb1wgCP3FBvl9VFokMX27acKphwyQsNuWH3c+ojd1LeWBLoTYoxF0zm6S/66mjg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/console": "30.2.0", - "@jest/types": "30.2.0", - "@types/istanbul-lib-coverage": "^2.0.6", - "collect-v8-coverage": "^1.0.2" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/test-sequencer": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/test-sequencer/-/test-sequencer-30.2.0.tgz", - "integrity": "sha512-wXKgU/lk8fKXMu/l5Hog1R61bL4q5GCdT6OJvdAFz1P+QrpoFuLU68eoKuVc4RbrTtNnTL5FByhWdLgOPSph+Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/test-result": "30.2.0", - "graceful-fs": "^4.2.11", - "jest-haste-map": "30.2.0", - "slash": "^3.0.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/transform": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/transform/-/transform-30.2.0.tgz", - "integrity": "sha512-XsauDV82o5qXbhalKxD7p4TZYYdwcaEXC77PPD2HixEFF+6YGppjrAAQurTl2ECWcEomHBMMNS9AH3kcCFx8jA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/core": "^7.27.4", - "@jest/types": "30.2.0", - "@jridgewell/trace-mapping": "^0.3.25", - "babel-plugin-istanbul": "^7.0.1", - "chalk": "^4.1.2", - "convert-source-map": "^2.0.0", - "fast-json-stable-stringify": "^2.1.0", - "graceful-fs": "^4.2.11", - "jest-haste-map": "30.2.0", - "jest-regex-util": "30.0.1", - "jest-util": "30.2.0", - "micromatch": "^4.0.8", - "pirates": "^4.0.7", - "slash": "^3.0.0", - "write-file-atomic": "^5.0.1" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jest/types": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/@jest/types/-/types-30.2.0.tgz", - "integrity": "sha512-H9xg1/sfVvyfU7o3zMfBEjQ1gcsdeTMgqHoYdN79tuLqfTtuu7WckRA1R5whDwOzxaZAeMKTYWqP+WCAi0CHsg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/pattern": "30.0.1", - "@jest/schemas": "30.0.5", - "@types/istanbul-lib-coverage": "^2.0.6", - "@types/istanbul-reports": "^3.0.4", - "@types/node": "*", - "@types/yargs": "^17.0.33", - "chalk": "^4.1.2" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/@jridgewell/gen-mapping": { - "version": "0.3.13", - "resolved": "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.3.13.tgz", - "integrity": "sha512-2kkt/7niJ6MgEPxF0bYdQ6etZaA+fQvDcLKckhy1yIQOzaoKjBBjSj63/aLVjYE3qhRt5dvM+uUyfCg6UKCBbA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jridgewell/sourcemap-codec": "^1.5.0", - "@jridgewell/trace-mapping": "^0.3.24" - } - }, - "node_modules/@jridgewell/remapping": { - "version": "2.3.5", - "resolved": "https://registry.npmjs.org/@jridgewell/remapping/-/remapping-2.3.5.tgz", - "integrity": "sha512-LI9u/+laYG4Ds1TDKSJW2YPrIlcVYOwi2fUC6xB43lueCjgxV4lffOCZCtYFiH6TNOX+tQKXx97T4IKHbhyHEQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jridgewell/gen-mapping": "^0.3.5", - "@jridgewell/trace-mapping": "^0.3.24" - } - }, - "node_modules/@jridgewell/resolve-uri": { - "version": "3.1.2", - "resolved": "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.1.2.tgz", - "integrity": "sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6.0.0" - } - }, - "node_modules/@jridgewell/sourcemap-codec": { - "version": "1.5.5", - "resolved": "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.5.5.tgz", - "integrity": "sha512-cYQ9310grqxueWbl+WuIUIaiUaDcj7WOq5fVhEljNVgRfOUhY9fy2zTvfoqWsnebh8Sl70VScFbICvJnLKB0Og==", - "dev": true, - "license": "MIT" - }, - "node_modules/@jridgewell/trace-mapping": { - "version": "0.3.31", - "resolved": "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.31.tgz", - "integrity": "sha512-zzNR+SdQSDJzc8joaeP8QQoCQr8NuYx2dIIytl1QeBEZHJ9uW6hebsrYgbz8hJwUQao3TWCMtmfV8Nu1twOLAw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jridgewell/resolve-uri": "^3.1.0", - "@jridgewell/sourcemap-codec": "^1.4.14" - } - }, - "node_modules/@kayvan/markdown-tree-parser": { - "version": "1.6.1", - "resolved": "https://registry.npmjs.org/@kayvan/markdown-tree-parser/-/markdown-tree-parser-1.6.1.tgz", - "integrity": "sha512-a5HUxUxQup5fAkL5xqmDBmZBNHZVfBn7FNfAx9SYEaUANuoVHygGAxaaHdkHDTCerntNKB2UzNS4dGIYbfPiiQ==", - "license": "MIT", - "dependencies": { - "remark-parse": "^11.0.0", - "remark-stringify": "^11.0.0", - "unified": "^11.0.5", - "unist-util-find": "^3.0.0", - "unist-util-select": "^5.1.0", - "unist-util-visit": "^5.0.0" - }, - "bin": { - "md-tree": "bin/md-tree.js" - }, - "engines": { - "node": ">=16.0.0" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/ksylvan" - } - }, - "node_modules/@mdx-js/mdx": { - "version": "3.1.1", - "resolved": "https://registry.npmjs.org/@mdx-js/mdx/-/mdx-3.1.1.tgz", - "integrity": "sha512-f6ZO2ifpwAQIpzGWaBQT2TXxPv6z3RBzQKpVftEWN78Vl/YweF1uwussDx8ECAXVtr3Rs89fKyG9YlzUs9DyGQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "@types/estree-jsx": "^1.0.0", - "@types/hast": "^3.0.0", - "@types/mdx": "^2.0.0", - "acorn": "^8.0.0", - "collapse-white-space": "^2.0.0", - "devlop": "^1.0.0", - "estree-util-is-identifier-name": "^3.0.0", - "estree-util-scope": "^1.0.0", - "estree-walker": "^3.0.0", - "hast-util-to-jsx-runtime": "^2.0.0", - "markdown-extensions": "^2.0.0", - "recma-build-jsx": "^1.0.0", - "recma-jsx": "^1.0.0", - "recma-stringify": "^1.0.0", - "rehype-recma": "^1.0.0", - "remark-mdx": "^3.0.0", - "remark-parse": "^11.0.0", - "remark-rehype": "^11.0.0", - "source-map": "^0.7.0", - "unified": "^11.0.0", - "unist-util-position-from-estree": "^2.0.0", - "unist-util-stringify-position": "^4.0.0", - "unist-util-visit": "^5.0.0", - "vfile": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/@napi-rs/wasm-runtime": { - "version": "0.2.12", - "resolved": "https://registry.npmjs.org/@napi-rs/wasm-runtime/-/wasm-runtime-0.2.12.tgz", - "integrity": "sha512-ZVWUcfwY4E/yPitQJl481FjFo3K22D6qF0DuFH6Y/nbnE11GY5uguDxZMGXPQ8WQ0128MXQD7TnfHyK4oWoIJQ==", - "dev": true, - "license": "MIT", - "optional": true, - "dependencies": { - "@emnapi/core": "^1.4.3", - "@emnapi/runtime": "^1.4.3", - "@tybys/wasm-util": "^0.10.0" - } - }, - "node_modules/@nodelib/fs.scandir": { - "version": "2.1.5", - "resolved": "https://registry.npmjs.org/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz", - "integrity": "sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==", - "dev": true, - "license": "MIT", - "dependencies": { - "@nodelib/fs.stat": "2.0.5", - "run-parallel": "^1.1.9" - }, - "engines": { - "node": ">= 8" - } - }, - "node_modules/@nodelib/fs.stat": { - "version": "2.0.5", - "resolved": "https://registry.npmjs.org/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz", - "integrity": "sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 8" - } - }, - "node_modules/@nodelib/fs.walk": { - "version": "1.2.8", - "resolved": "https://registry.npmjs.org/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz", - "integrity": "sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@nodelib/fs.scandir": "2.1.5", - "fastq": "^1.6.0" - }, - "engines": { - "node": ">= 8" - } - }, - "node_modules/@oslojs/encoding": { - "version": "1.1.0", - "resolved": "https://registry.npmjs.org/@oslojs/encoding/-/encoding-1.1.0.tgz", - "integrity": "sha512-70wQhgYmndg4GCPxPPxPGevRKqTIJ2Nh4OkiMWmDAVYsTQ+Ta7Sq+rPevXyXGdzr30/qZBnyOalCszoMxlyldQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/@pagefind/darwin-arm64": { - "version": "1.4.0", - "resolved": "https://registry.npmjs.org/@pagefind/darwin-arm64/-/darwin-arm64-1.4.0.tgz", - "integrity": "sha512-2vMqkbv3lbx1Awea90gTaBsvpzgRs7MuSgKDxW0m9oV1GPZCZbZBJg/qL83GIUEN2BFlY46dtUZi54pwH+/pTQ==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "darwin" - ] - }, - "node_modules/@pagefind/darwin-x64": { - "version": "1.4.0", - "resolved": "https://registry.npmjs.org/@pagefind/darwin-x64/-/darwin-x64-1.4.0.tgz", - "integrity": "sha512-e7JPIS6L9/cJfow+/IAqknsGqEPjJnVXGjpGm25bnq+NPdoD3c/7fAwr1OXkG4Ocjx6ZGSCijXEV4ryMcH2E3A==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "darwin" - ] - }, - "node_modules/@pagefind/default-ui": { - "version": "1.4.0", - "resolved": "https://registry.npmjs.org/@pagefind/default-ui/-/default-ui-1.4.0.tgz", - "integrity": "sha512-wie82VWn3cnGEdIjh4YwNESyS1G6vRHwL6cNjy9CFgNnWW/PGRjsLq300xjVH5sfPFK3iK36UxvIBymtQIEiSQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/@pagefind/freebsd-x64": { - "version": "1.4.0", - "resolved": "https://registry.npmjs.org/@pagefind/freebsd-x64/-/freebsd-x64-1.4.0.tgz", - "integrity": "sha512-WcJVypXSZ+9HpiqZjFXMUobfFfZZ6NzIYtkhQ9eOhZrQpeY5uQFqNWLCk7w9RkMUwBv1HAMDW3YJQl/8OqsV0Q==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "freebsd" - ] - }, - "node_modules/@pagefind/linux-arm64": { - "version": "1.4.0", - "resolved": "https://registry.npmjs.org/@pagefind/linux-arm64/-/linux-arm64-1.4.0.tgz", - "integrity": "sha512-PIt8dkqt4W06KGmQjONw7EZbhDF+uXI7i0XtRLN1vjCUxM9vGPdtJc2mUyVPevjomrGz5M86M8bqTr6cgDp1Uw==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@pagefind/linux-x64": { - "version": "1.4.0", - "resolved": "https://registry.npmjs.org/@pagefind/linux-x64/-/linux-x64-1.4.0.tgz", - "integrity": "sha512-z4oddcWwQ0UHrTHR8psLnVlz6USGJ/eOlDPTDYZ4cI8TK8PgwRUPQZp9D2iJPNIPcS6Qx/E4TebjuGJOyK8Mmg==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@pagefind/windows-x64": { - "version": "1.4.0", - "resolved": "https://registry.npmjs.org/@pagefind/windows-x64/-/windows-x64-1.4.0.tgz", - "integrity": "sha512-NkT+YAdgS2FPCn8mIA9bQhiBs+xmniMGq1LFPDhcFn0+2yIUEiIG06t7bsZlhdjknEQRTSdT7YitP6fC5qwP0g==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "win32" - ] - }, - "node_modules/@pkgjs/parseargs": { - "version": "0.11.0", - "resolved": "https://registry.npmjs.org/@pkgjs/parseargs/-/parseargs-0.11.0.tgz", - "integrity": "sha512-+1VkjdD0QBLPodGrJUeqarH8VAIvQODIbwh9XpP5Syisf7YoQgsJKPNFoqqLQlu+VQ/tVSshMR6loPMn8U+dPg==", - "dev": true, - "license": "MIT", - "optional": true, - "engines": { - "node": ">=14" - } - }, - "node_modules/@pkgr/core": { - "version": "0.2.9", - "resolved": "https://registry.npmjs.org/@pkgr/core/-/core-0.2.9.tgz", - "integrity": "sha512-QNqXyfVS2wm9hweSYD2O7F0G06uurj9kZ96TRQE5Y9hU7+tgdZwIkbAKc5Ocy1HxEY2kuDQa6cQ1WRs/O5LFKA==", - "dev": true, - "license": "MIT", - "engines": { - "node": "^12.20.0 || ^14.18.0 || >=16.0.0" - }, - "funding": { - "url": "https://opencollective.com/pkgr" - } - }, - "node_modules/@rollup/pluginutils": { - "version": "5.3.0", - "resolved": "https://registry.npmjs.org/@rollup/pluginutils/-/pluginutils-5.3.0.tgz", - "integrity": "sha512-5EdhGZtnu3V88ces7s53hhfK5KSASnJZv8Lulpc04cWO3REESroJXg73DFsOmgbU2BhwV0E20bu2IDZb3VKW4Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "estree-walker": "^2.0.2", - "picomatch": "^4.0.2" - }, - "engines": { - "node": ">=14.0.0" - }, - "peerDependencies": { - "rollup": "^1.20.0||^2.0.0||^3.0.0||^4.0.0" - }, - "peerDependenciesMeta": { - "rollup": { - "optional": true - } - } - }, - "node_modules/@rollup/pluginutils/node_modules/estree-walker": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/estree-walker/-/estree-walker-2.0.2.tgz", - "integrity": "sha512-Rfkk/Mp/DL7JVje3u18FxFujQlTNR2q6QfMSMB7AvCBx91NGj/ba3kCfza0f6dVDbw7YlRf/nDrn7pQrCCyQ/w==", - "dev": true, - "license": "MIT" - }, - "node_modules/@rollup/rollup-android-arm-eabi": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-android-arm-eabi/-/rollup-android-arm-eabi-4.57.1.tgz", - "integrity": "sha512-A6ehUVSiSaaliTxai040ZpZ2zTevHYbvu/lDoeAteHI8QnaosIzm4qwtezfRg1jOYaUmnzLX1AOD6Z+UJjtifg==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "android" - ] - }, - "node_modules/@rollup/rollup-android-arm64": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-android-arm64/-/rollup-android-arm64-4.57.1.tgz", - "integrity": "sha512-dQaAddCY9YgkFHZcFNS/606Exo8vcLHwArFZ7vxXq4rigo2bb494/xKMMwRRQW6ug7Js6yXmBZhSBRuBvCCQ3w==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "android" - ] - }, - "node_modules/@rollup/rollup-darwin-arm64": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-darwin-arm64/-/rollup-darwin-arm64-4.57.1.tgz", - "integrity": "sha512-crNPrwJOrRxagUYeMn/DZwqN88SDmwaJ8Cvi/TN1HnWBU7GwknckyosC2gd0IqYRsHDEnXf328o9/HC6OkPgOg==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "darwin" - ] - }, - "node_modules/@rollup/rollup-darwin-x64": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-darwin-x64/-/rollup-darwin-x64-4.57.1.tgz", - "integrity": "sha512-Ji8g8ChVbKrhFtig5QBV7iMaJrGtpHelkB3lsaKzadFBe58gmjfGXAOfI5FV0lYMH8wiqsxKQ1C9B0YTRXVy4w==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "darwin" - ] - }, - "node_modules/@rollup/rollup-freebsd-arm64": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-freebsd-arm64/-/rollup-freebsd-arm64-4.57.1.tgz", - "integrity": "sha512-R+/WwhsjmwodAcz65guCGFRkMb4gKWTcIeLy60JJQbXrJ97BOXHxnkPFrP+YwFlaS0m+uWJTstrUA9o+UchFug==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "freebsd" - ] - }, - "node_modules/@rollup/rollup-freebsd-x64": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-freebsd-x64/-/rollup-freebsd-x64-4.57.1.tgz", - "integrity": "sha512-IEQTCHeiTOnAUC3IDQdzRAGj3jOAYNr9kBguI7MQAAZK3caezRrg0GxAb6Hchg4lxdZEI5Oq3iov/w/hnFWY9Q==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "freebsd" - ] - }, - "node_modules/@rollup/rollup-linux-arm-gnueabihf": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm-gnueabihf/-/rollup-linux-arm-gnueabihf-4.57.1.tgz", - "integrity": "sha512-F8sWbhZ7tyuEfsmOxwc2giKDQzN3+kuBLPwwZGyVkLlKGdV1nvnNwYD0fKQ8+XS6hp9nY7B+ZeK01EBUE7aHaw==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-arm-musleabihf": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm-musleabihf/-/rollup-linux-arm-musleabihf-4.57.1.tgz", - "integrity": "sha512-rGfNUfn0GIeXtBP1wL5MnzSj98+PZe/AXaGBCRmT0ts80lU5CATYGxXukeTX39XBKsxzFpEeK+Mrp9faXOlmrw==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-arm64-gnu": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm64-gnu/-/rollup-linux-arm64-gnu-4.57.1.tgz", - "integrity": "sha512-MMtej3YHWeg/0klK2Qodf3yrNzz6CGjo2UntLvk2RSPlhzgLvYEB3frRvbEF2wRKh1Z2fDIg9KRPe1fawv7C+g==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-arm64-musl": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm64-musl/-/rollup-linux-arm64-musl-4.57.1.tgz", - "integrity": "sha512-1a/qhaaOXhqXGpMFMET9VqwZakkljWHLmZOX48R0I/YLbhdxr1m4gtG1Hq7++VhVUmf+L3sTAf9op4JlhQ5u1Q==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-loong64-gnu": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-loong64-gnu/-/rollup-linux-loong64-gnu-4.57.1.tgz", - "integrity": "sha512-QWO6RQTZ/cqYtJMtxhkRkidoNGXc7ERPbZN7dVW5SdURuLeVU7lwKMpo18XdcmpWYd0qsP1bwKPf7DNSUinhvA==", - "cpu": [ - "loong64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-loong64-musl": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-loong64-musl/-/rollup-linux-loong64-musl-4.57.1.tgz", - "integrity": "sha512-xpObYIf+8gprgWaPP32xiN5RVTi/s5FCR+XMXSKmhfoJjrpRAjCuuqQXyxUa/eJTdAE6eJ+KDKaoEqjZQxh3Gw==", - "cpu": [ - "loong64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-ppc64-gnu": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-ppc64-gnu/-/rollup-linux-ppc64-gnu-4.57.1.tgz", - "integrity": "sha512-4BrCgrpZo4hvzMDKRqEaW1zeecScDCR+2nZ86ATLhAoJ5FQ+lbHVD3ttKe74/c7tNT9c6F2viwB3ufwp01Oh2w==", - "cpu": [ - "ppc64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-ppc64-musl": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-ppc64-musl/-/rollup-linux-ppc64-musl-4.57.1.tgz", - "integrity": "sha512-NOlUuzesGauESAyEYFSe3QTUguL+lvrN1HtwEEsU2rOwdUDeTMJdO5dUYl/2hKf9jWydJrO9OL/XSSf65R5+Xw==", - "cpu": [ - "ppc64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-riscv64-gnu": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-riscv64-gnu/-/rollup-linux-riscv64-gnu-4.57.1.tgz", - "integrity": "sha512-ptA88htVp0AwUUqhVghwDIKlvJMD/fmL/wrQj99PRHFRAG6Z5nbWoWG4o81Nt9FT+IuqUQi+L31ZKAFeJ5Is+A==", - "cpu": [ - "riscv64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-riscv64-musl": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-riscv64-musl/-/rollup-linux-riscv64-musl-4.57.1.tgz", - "integrity": "sha512-S51t7aMMTNdmAMPpBg7OOsTdn4tySRQvklmL3RpDRyknk87+Sp3xaumlatU+ppQ+5raY7sSTcC2beGgvhENfuw==", - "cpu": [ - "riscv64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-s390x-gnu": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-s390x-gnu/-/rollup-linux-s390x-gnu-4.57.1.tgz", - "integrity": "sha512-Bl00OFnVFkL82FHbEqy3k5CUCKH6OEJL54KCyx2oqsmZnFTR8IoNqBF+mjQVcRCT5sB6yOvK8A37LNm/kPJiZg==", - "cpu": [ - "s390x" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-x64-gnu": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-x64-gnu/-/rollup-linux-x64-gnu-4.57.1.tgz", - "integrity": "sha512-ABca4ceT4N+Tv/GtotnWAeXZUZuM/9AQyCyKYyKnpk4yoA7QIAuBt6Hkgpw8kActYlew2mvckXkvx0FfoInnLg==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-linux-x64-musl": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-x64-musl/-/rollup-linux-x64-musl-4.57.1.tgz", - "integrity": "sha512-HFps0JeGtuOR2convgRRkHCekD7j+gdAuXM+/i6kGzQtFhlCtQkpwtNzkNj6QhCDp7DRJ7+qC/1Vg2jt5iSOFw==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@rollup/rollup-openbsd-x64": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-openbsd-x64/-/rollup-openbsd-x64-4.57.1.tgz", - "integrity": "sha512-H+hXEv9gdVQuDTgnqD+SQffoWoc0Of59AStSzTEj/feWTBAnSfSD3+Dql1ZruJQxmykT/JVY0dE8Ka7z0DH1hw==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "openbsd" - ] - }, - "node_modules/@rollup/rollup-openharmony-arm64": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-openharmony-arm64/-/rollup-openharmony-arm64-4.57.1.tgz", - "integrity": "sha512-4wYoDpNg6o/oPximyc/NG+mYUejZrCU2q+2w6YZqrAs2UcNUChIZXjtafAiiZSUc7On8v5NyNj34Kzj/Ltk6dQ==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "openharmony" - ] - }, - "node_modules/@rollup/rollup-win32-arm64-msvc": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-win32-arm64-msvc/-/rollup-win32-arm64-msvc-4.57.1.tgz", - "integrity": "sha512-O54mtsV/6LW3P8qdTcamQmuC990HDfR71lo44oZMZlXU4tzLrbvTii87Ni9opq60ds0YzuAlEr/GNwuNluZyMQ==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "win32" - ] - }, - "node_modules/@rollup/rollup-win32-ia32-msvc": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-win32-ia32-msvc/-/rollup-win32-ia32-msvc-4.57.1.tgz", - "integrity": "sha512-P3dLS+IerxCT/7D2q2FYcRdWRl22dNbrbBEtxdWhXrfIMPP9lQhb5h4Du04mdl5Woq05jVCDPCMF7Ub0NAjIew==", - "cpu": [ - "ia32" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "win32" - ] - }, - "node_modules/@rollup/rollup-win32-x64-gnu": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-win32-x64-gnu/-/rollup-win32-x64-gnu-4.57.1.tgz", - "integrity": "sha512-VMBH2eOOaKGtIJYleXsi2B8CPVADrh+TyNxJ4mWPnKfLB/DBUmzW+5m1xUrcwWoMfSLagIRpjUFeW5CO5hyciQ==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "win32" - ] - }, - "node_modules/@rollup/rollup-win32-x64-msvc": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/@rollup/rollup-win32-x64-msvc/-/rollup-win32-x64-msvc-4.57.1.tgz", - "integrity": "sha512-mxRFDdHIWRxg3UfIIAwCm6NzvxG0jDX/wBN6KsQFTvKFqqg9vTrWUE68qEjHt19A5wwx5X5aUi2zuZT7YR0jrA==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "win32" - ] - }, - "node_modules/@shikijs/core": { - "version": "3.21.0", - "resolved": "https://registry.npmjs.org/@shikijs/core/-/core-3.21.0.tgz", - "integrity": "sha512-AXSQu/2n1UIQekY8euBJlvFYZIw0PHY63jUzGbrOma4wPxzznJXTXkri+QcHeBNaFxiiOljKxxJkVSoB3PjbyA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@shikijs/types": "3.21.0", - "@shikijs/vscode-textmate": "^10.0.2", - "@types/hast": "^3.0.4", - "hast-util-to-html": "^9.0.5" - } - }, - "node_modules/@shikijs/engine-javascript": { - "version": "3.21.0", - "resolved": "https://registry.npmjs.org/@shikijs/engine-javascript/-/engine-javascript-3.21.0.tgz", - "integrity": "sha512-ATwv86xlbmfD9n9gKRiwuPpWgPENAWCLwYCGz9ugTJlsO2kOzhOkvoyV/UD+tJ0uT7YRyD530x6ugNSffmvIiQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@shikijs/types": "3.21.0", - "@shikijs/vscode-textmate": "^10.0.2", - "oniguruma-to-es": "^4.3.4" - } - }, - "node_modules/@shikijs/engine-oniguruma": { - "version": "3.21.0", - "resolved": "https://registry.npmjs.org/@shikijs/engine-oniguruma/-/engine-oniguruma-3.21.0.tgz", - "integrity": "sha512-OYknTCct6qiwpQDqDdf3iedRdzj6hFlOPv5hMvI+hkWfCKs5mlJ4TXziBG9nyabLwGulrUjHiCq3xCspSzErYQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@shikijs/types": "3.21.0", - "@shikijs/vscode-textmate": "^10.0.2" - } - }, - "node_modules/@shikijs/langs": { - "version": "3.21.0", - "resolved": "https://registry.npmjs.org/@shikijs/langs/-/langs-3.21.0.tgz", - "integrity": "sha512-g6mn5m+Y6GBJ4wxmBYqalK9Sp0CFkUqfNzUy2pJglUginz6ZpWbaWjDB4fbQ/8SHzFjYbtU6Ddlp1pc+PPNDVA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@shikijs/types": "3.21.0" - } - }, - "node_modules/@shikijs/themes": { - "version": "3.21.0", - "resolved": "https://registry.npmjs.org/@shikijs/themes/-/themes-3.21.0.tgz", - "integrity": "sha512-BAE4cr9EDiZyYzwIHEk7JTBJ9CzlPuM4PchfcA5ao1dWXb25nv6hYsoDiBq2aZK9E3dlt3WB78uI96UESD+8Mw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@shikijs/types": "3.21.0" - } - }, - "node_modules/@shikijs/types": { - "version": "3.21.0", - "resolved": "https://registry.npmjs.org/@shikijs/types/-/types-3.21.0.tgz", - "integrity": "sha512-zGrWOxZ0/+0ovPY7PvBU2gIS9tmhSUUt30jAcNV0Bq0gb2S98gwfjIs1vxlmH5zM7/4YxLamT6ChlqqAJmPPjA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@shikijs/vscode-textmate": "^10.0.2", - "@types/hast": "^3.0.4" - } - }, - "node_modules/@shikijs/vscode-textmate": { - "version": "10.0.2", - "resolved": "https://registry.npmjs.org/@shikijs/vscode-textmate/-/vscode-textmate-10.0.2.tgz", - "integrity": "sha512-83yeghZ2xxin3Nj8z1NMd/NCuca+gsYXswywDy5bHvwlWL8tpTQmzGeUuHd9FC3E/SBEMvzJRwWEOz5gGes9Qg==", - "dev": true, - "license": "MIT" - }, - "node_modules/@sinclair/typebox": { - "version": "0.34.48", - "resolved": "https://registry.npmjs.org/@sinclair/typebox/-/typebox-0.34.48.tgz", - "integrity": "sha512-kKJTNuK3AQOrgjjotVxMrCn1sUJwM76wMszfq1kdU4uYVJjvEWuFQ6HgvLt4Xz3fSmZlTOxJ/Ie13KnIcWQXFA==", - "dev": true, - "license": "MIT" - }, - "node_modules/@sindresorhus/merge-streams": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/@sindresorhus/merge-streams/-/merge-streams-4.0.0.tgz", - "integrity": "sha512-tlqY9xq5ukxTUZBmoOp+m61cqwQD5pHJtFY3Mn8CA8ps6yghLH/Hw8UPdqg4OLmFW3IFlcXnQNmo/dh8HzXYIQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/@sinonjs/commons": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/@sinonjs/commons/-/commons-3.0.1.tgz", - "integrity": "sha512-K3mCHKQ9sVh8o1C9cxkwxaOmXoAMlDxC1mYyHrjqOWEcBjYr76t96zL2zlj5dUGZ3HSw240X1qgH3Mjf1yJWpQ==", - "dev": true, - "license": "BSD-3-Clause", - "dependencies": { - "type-detect": "4.0.8" - } - }, - "node_modules/@sinonjs/fake-timers": { - "version": "13.0.5", - "resolved": "https://registry.npmjs.org/@sinonjs/fake-timers/-/fake-timers-13.0.5.tgz", - "integrity": "sha512-36/hTbH2uaWuGVERyC6da9YwGWnzUZXuPro/F2LfsdOsLnCojz/iSH8MxUt/FD2S5XBSVPhmArFUXcpCQ2Hkiw==", - "dev": true, - "license": "BSD-3-Clause", - "dependencies": { - "@sinonjs/commons": "^3.0.1" - } - }, - "node_modules/@tybys/wasm-util": { - "version": "0.10.1", - "resolved": "https://registry.npmjs.org/@tybys/wasm-util/-/wasm-util-0.10.1.tgz", - "integrity": "sha512-9tTaPJLSiejZKx+Bmog4uSubteqTvFrVrURwkmHixBo0G4seD0zUxp98E1DzUBJxLQ3NPwXrGKDiVjwx/DpPsg==", - "dev": true, - "license": "MIT", - "optional": true, - "dependencies": { - "tslib": "^2.4.0" - } - }, - "node_modules/@types/babel__core": { - "version": "7.20.5", - "resolved": "https://registry.npmjs.org/@types/babel__core/-/babel__core-7.20.5.tgz", - "integrity": "sha512-qoQprZvz5wQFJwMDqeseRXWv3rqMvhgpbXFfVyWhbx9X47POIA6i/+dXefEmZKoAgOaTdaIgNSMqMIU61yRyzA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/parser": "^7.20.7", - "@babel/types": "^7.20.7", - "@types/babel__generator": "*", - "@types/babel__template": "*", - "@types/babel__traverse": "*" - } - }, - "node_modules/@types/babel__generator": { - "version": "7.27.0", - "resolved": "https://registry.npmjs.org/@types/babel__generator/-/babel__generator-7.27.0.tgz", - "integrity": "sha512-ufFd2Xi92OAVPYsy+P4n7/U7e68fex0+Ee8gSG9KX7eo084CWiQ4sdxktvdl0bOPupXtVJPY19zk6EwWqUQ8lg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/types": "^7.0.0" - } - }, - "node_modules/@types/babel__template": { - "version": "7.4.4", - "resolved": "https://registry.npmjs.org/@types/babel__template/-/babel__template-7.4.4.tgz", - "integrity": "sha512-h/NUaSyG5EyxBIp8YRxo4RMe2/qQgvyowRwVMzhYhBCONbW8PUsg4lkFMrhgZhUe5z3L3MiLDuvyJ/CaPa2A8A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/parser": "^7.1.0", - "@babel/types": "^7.0.0" - } - }, - "node_modules/@types/babel__traverse": { - "version": "7.28.0", - "resolved": "https://registry.npmjs.org/@types/babel__traverse/-/babel__traverse-7.28.0.tgz", - "integrity": "sha512-8PvcXf70gTDZBgt9ptxJ8elBeBjcLOAcOtoO/mPJjtji1+CdGbHgm77om1GrsPxsiE+uXIpNSK64UYaIwQXd4Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/types": "^7.28.2" - } - }, - "node_modules/@types/debug": { - "version": "4.1.12", - "resolved": "https://registry.npmjs.org/@types/debug/-/debug-4.1.12.tgz", - "integrity": "sha512-vIChWdVG3LG1SMxEvI/AK+FWJthlrqlTu7fbrlywTkkaONwk/UAGaULXRlf8vkzFBLVm0zkMdCquhL5aOjhXPQ==", - "license": "MIT", - "dependencies": { - "@types/ms": "*" - } - }, - "node_modules/@types/estree": { - "version": "1.0.8", - "resolved": "https://registry.npmjs.org/@types/estree/-/estree-1.0.8.tgz", - "integrity": "sha512-dWHzHa2WqEXI/O1E9OjrocMTKJl2mSrEolh1Iomrv6U+JuNwaHXsXx9bLu5gG7BUWFIN0skIQJQ/L1rIex4X6w==", - "dev": true, - "license": "MIT" - }, - "node_modules/@types/estree-jsx": { - "version": "1.0.5", - "resolved": "https://registry.npmjs.org/@types/estree-jsx/-/estree-jsx-1.0.5.tgz", - "integrity": "sha512-52CcUVNFyfb1A2ALocQw/Dd1BQFNmSdkuC3BkZ6iqhdMfQz7JWOFRuJFloOzjk+6WijU56m9oKXFAXc7o3Towg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "*" - } - }, - "node_modules/@types/hast": { - "version": "3.0.4", - "resolved": "https://registry.npmjs.org/@types/hast/-/hast-3.0.4.tgz", - "integrity": "sha512-WPs+bbQw5aCj+x6laNGWLH3wviHtoCv/P3+otBhbOhJgG8qtpdAMlTCxLtsTWA7LH1Oh/bFCHsBn0TPS5m30EQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/unist": "*" - } - }, - "node_modules/@types/istanbul-lib-coverage": { - "version": "2.0.6", - "resolved": "https://registry.npmjs.org/@types/istanbul-lib-coverage/-/istanbul-lib-coverage-2.0.6.tgz", - "integrity": "sha512-2QF/t/auWm0lsy8XtKVPG19v3sSOQlJe/YHZgfjb/KBBHOGSV+J2q/S671rcq9uTBrLAXmZpqJiaQbMT+zNU1w==", - "dev": true, - "license": "MIT" - }, - "node_modules/@types/istanbul-lib-report": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/@types/istanbul-lib-report/-/istanbul-lib-report-3.0.3.tgz", - "integrity": "sha512-NQn7AHQnk/RSLOxrBbGyJM/aVQ+pjj5HCgasFxc0K/KhoATfQ/47AyUl15I2yBUpihjmas+a+VJBOqecrFH+uA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/istanbul-lib-coverage": "*" - } - }, - "node_modules/@types/istanbul-reports": { - "version": "3.0.4", - "resolved": "https://registry.npmjs.org/@types/istanbul-reports/-/istanbul-reports-3.0.4.tgz", - "integrity": "sha512-pk2B1NWalF9toCRu6gjBzR69syFjP4Od8WRAX+0mmf9lAjCRicLOWc+ZrxZHx/0XRjotgkF9t6iaMJ+aXcOdZQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/istanbul-lib-report": "*" - } - }, - "node_modules/@types/js-yaml": { - "version": "4.0.9", - "resolved": "https://registry.npmjs.org/@types/js-yaml/-/js-yaml-4.0.9.tgz", - "integrity": "sha512-k4MGaQl5TGo/iipqb2UDG2UwjXziSWkh0uysQelTlJpX1qGlpUZYm8PnO4DxG1qBomtJUdYJ6qR6xdIah10JLg==", - "dev": true, - "license": "MIT" - }, - "node_modules/@types/json-schema": { - "version": "7.0.15", - "resolved": "https://registry.npmjs.org/@types/json-schema/-/json-schema-7.0.15.tgz", - "integrity": "sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA==", - "dev": true, - "license": "MIT" - }, - "node_modules/@types/katex": { - "version": "0.16.8", - "resolved": "https://registry.npmjs.org/@types/katex/-/katex-0.16.8.tgz", - "integrity": "sha512-trgaNyfU+Xh2Tc+ABIb44a5AYUpicB3uwirOioeOkNPPbmgRNtcWyDeeFRzjPZENO9Vq8gvVqfhaaXWLlevVwg==", - "dev": true, - "license": "MIT" - }, - "node_modules/@types/mdast": { - "version": "4.0.4", - "resolved": "https://registry.npmjs.org/@types/mdast/-/mdast-4.0.4.tgz", - "integrity": "sha512-kGaNbPh1k7AFzgpud/gMdvIm5xuECykRR+JnWKQno9TAXVa6WIVCGTPvYGekIDL4uwCZQSYbUxNBSb1aUo79oA==", - "license": "MIT", - "dependencies": { - "@types/unist": "*" - } - }, - "node_modules/@types/mdx": { - "version": "2.0.13", - "resolved": "https://registry.npmjs.org/@types/mdx/-/mdx-2.0.13.tgz", - "integrity": "sha512-+OWZQfAYyio6YkJb3HLxDrvnx6SWWDbC0zVPfBRzUk0/nqoDyf6dNxQi3eArPe8rJ473nobTMQ/8Zk+LxJ+Yuw==", - "dev": true, - "license": "MIT" - }, - "node_modules/@types/ms": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/@types/ms/-/ms-2.1.0.tgz", - "integrity": "sha512-GsCCIZDE/p3i96vtEqx+7dBUGXrc7zeSK3wwPHIaRThS+9OhWIXRqzs4d6k1SVU8g91DrNRWxWUGhp5KXQb2VA==", - "license": "MIT" - }, - "node_modules/@types/nlcst": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/@types/nlcst/-/nlcst-2.0.3.tgz", - "integrity": "sha512-vSYNSDe6Ix3q+6Z7ri9lyWqgGhJTmzRjZRqyq15N0Z/1/UnVsno9G/N40NBijoYx2seFDIl0+B2mgAb9mezUCA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/unist": "*" - } - }, - "node_modules/@types/node": { - "version": "25.1.0", - "resolved": "https://registry.npmjs.org/@types/node/-/node-25.1.0.tgz", - "integrity": "sha512-t7frlewr6+cbx+9Ohpl0NOTKXZNV9xHRmNOvql47BFJKcEG1CxtxlPEEe+gR9uhVWM4DwhnvTF110mIL4yP9RA==", - "dev": true, - "license": "MIT", - "dependencies": { - "undici-types": "~7.16.0" - } - }, - "node_modules/@types/sax": { - "version": "1.2.7", - "resolved": "https://registry.npmjs.org/@types/sax/-/sax-1.2.7.tgz", - "integrity": "sha512-rO73L89PJxeYM3s3pPPjiPgVVcymqU490g0YO5n5By0k2Erzj6tay/4lr1CHAAU4JyOWd1rpQ8bCf6cZfHU96A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/node": "*" - } - }, - "node_modules/@types/stack-utils": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/@types/stack-utils/-/stack-utils-2.0.3.tgz", - "integrity": "sha512-9aEbYZ3TbYMznPdcdr3SmIrLXwC/AKZXQeCf9Pgao5CKb8CyHuEX5jzWPTkvregvhRJHcpRO6BFoGW9ycaOkYw==", - "dev": true, - "license": "MIT" - }, - "node_modules/@types/unist": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/@types/unist/-/unist-3.0.3.tgz", - "integrity": "sha512-ko/gIFJRv177XgZsZcBwnqJN5x/Gien8qNOn0D5bQU/zAzVf9Zt3BlcUiLqhV9y4ARk0GbT3tnUiPNgnTXzc/Q==", - "license": "MIT" - }, - "node_modules/@types/yargs": { - "version": "17.0.35", - "resolved": "https://registry.npmjs.org/@types/yargs/-/yargs-17.0.35.tgz", - "integrity": "sha512-qUHkeCyQFxMXg79wQfTtfndEC+N9ZZg76HJftDJp+qH2tV7Gj4OJi7l+PiWwJ+pWtW8GwSmqsDj/oymhrTWXjg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/yargs-parser": "*" - } - }, - "node_modules/@types/yargs-parser": { - "version": "21.0.3", - "resolved": "https://registry.npmjs.org/@types/yargs-parser/-/yargs-parser-21.0.3.tgz", - "integrity": "sha512-I4q9QU9MQv4oEOz4tAHJtNz1cwuLxn2F3xcc2iV5WdqLPpUnj30aUuxt1mAxYTG+oe8CZMV/+6rU4S4gRDzqtQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/@ungap/structured-clone": { - "version": "1.3.0", - "resolved": "https://registry.npmjs.org/@ungap/structured-clone/-/structured-clone-1.3.0.tgz", - "integrity": "sha512-WmoN8qaIAo7WTYWbAZuG8PYEhn5fkz7dZrqTBZ7dtt//lL2Gwms1IcnQ5yHqjDfX8Ft5j4YzDM23f87zBfDe9g==", - "dev": true, - "license": "ISC" - }, - "node_modules/@unrs/resolver-binding-android-arm-eabi": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-android-arm-eabi/-/resolver-binding-android-arm-eabi-1.11.1.tgz", - "integrity": "sha512-ppLRUgHVaGRWUx0R0Ut06Mjo9gBaBkg3v/8AxusGLhsIotbBLuRk51rAzqLC8gq6NyyAojEXglNjzf6R948DNw==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "android" - ] - }, - "node_modules/@unrs/resolver-binding-android-arm64": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-android-arm64/-/resolver-binding-android-arm64-1.11.1.tgz", - "integrity": "sha512-lCxkVtb4wp1v+EoN+HjIG9cIIzPkX5OtM03pQYkG+U5O/wL53LC4QbIeazgiKqluGeVEeBlZahHalCaBvU1a2g==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "android" - ] - }, - "node_modules/@unrs/resolver-binding-darwin-arm64": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-darwin-arm64/-/resolver-binding-darwin-arm64-1.11.1.tgz", - "integrity": "sha512-gPVA1UjRu1Y/IsB/dQEsp2V1pm44Of6+LWvbLc9SDk1c2KhhDRDBUkQCYVWe6f26uJb3fOK8saWMgtX8IrMk3g==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "darwin" - ] - }, - "node_modules/@unrs/resolver-binding-darwin-x64": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-darwin-x64/-/resolver-binding-darwin-x64-1.11.1.tgz", - "integrity": "sha512-cFzP7rWKd3lZaCsDze07QX1SC24lO8mPty9vdP+YVa3MGdVgPmFc59317b2ioXtgCMKGiCLxJ4HQs62oz6GfRQ==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "darwin" - ] - }, - "node_modules/@unrs/resolver-binding-freebsd-x64": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-freebsd-x64/-/resolver-binding-freebsd-x64-1.11.1.tgz", - "integrity": "sha512-fqtGgak3zX4DCB6PFpsH5+Kmt/8CIi4Bry4rb1ho6Av2QHTREM+47y282Uqiu3ZRF5IQioJQ5qWRV6jduA+iGw==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "freebsd" - ] - }, - "node_modules/@unrs/resolver-binding-linux-arm-gnueabihf": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-linux-arm-gnueabihf/-/resolver-binding-linux-arm-gnueabihf-1.11.1.tgz", - "integrity": "sha512-u92mvlcYtp9MRKmP+ZvMmtPN34+/3lMHlyMj7wXJDeXxuM0Vgzz0+PPJNsro1m3IZPYChIkn944wW8TYgGKFHw==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@unrs/resolver-binding-linux-arm-musleabihf": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-linux-arm-musleabihf/-/resolver-binding-linux-arm-musleabihf-1.11.1.tgz", - "integrity": "sha512-cINaoY2z7LVCrfHkIcmvj7osTOtm6VVT16b5oQdS4beibX2SYBwgYLmqhBjA1t51CarSaBuX5YNsWLjsqfW5Cw==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@unrs/resolver-binding-linux-arm64-gnu": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-linux-arm64-gnu/-/resolver-binding-linux-arm64-gnu-1.11.1.tgz", - "integrity": "sha512-34gw7PjDGB9JgePJEmhEqBhWvCiiWCuXsL9hYphDF7crW7UgI05gyBAi6MF58uGcMOiOqSJ2ybEeCvHcq0BCmQ==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@unrs/resolver-binding-linux-arm64-musl": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-linux-arm64-musl/-/resolver-binding-linux-arm64-musl-1.11.1.tgz", - "integrity": "sha512-RyMIx6Uf53hhOtJDIamSbTskA99sPHS96wxVE/bJtePJJtpdKGXO1wY90oRdXuYOGOTuqjT8ACccMc4K6QmT3w==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@unrs/resolver-binding-linux-ppc64-gnu": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-linux-ppc64-gnu/-/resolver-binding-linux-ppc64-gnu-1.11.1.tgz", - "integrity": "sha512-D8Vae74A4/a+mZH0FbOkFJL9DSK2R6TFPC9M+jCWYia/q2einCubX10pecpDiTmkJVUH+y8K3BZClycD8nCShA==", - "cpu": [ - "ppc64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@unrs/resolver-binding-linux-riscv64-gnu": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-linux-riscv64-gnu/-/resolver-binding-linux-riscv64-gnu-1.11.1.tgz", - "integrity": "sha512-frxL4OrzOWVVsOc96+V3aqTIQl1O2TjgExV4EKgRY09AJ9leZpEg8Ak9phadbuX0BA4k8U5qtvMSQQGGmaJqcQ==", - "cpu": [ - "riscv64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@unrs/resolver-binding-linux-riscv64-musl": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-linux-riscv64-musl/-/resolver-binding-linux-riscv64-musl-1.11.1.tgz", - "integrity": "sha512-mJ5vuDaIZ+l/acv01sHoXfpnyrNKOk/3aDoEdLO/Xtn9HuZlDD6jKxHlkN8ZhWyLJsRBxfv9GYM2utQ1SChKew==", - "cpu": [ - "riscv64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@unrs/resolver-binding-linux-s390x-gnu": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-linux-s390x-gnu/-/resolver-binding-linux-s390x-gnu-1.11.1.tgz", - "integrity": "sha512-kELo8ebBVtb9sA7rMe1Cph4QHreByhaZ2QEADd9NzIQsYNQpt9UkM9iqr2lhGr5afh885d/cB5QeTXSbZHTYPg==", - "cpu": [ - "s390x" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@unrs/resolver-binding-linux-x64-gnu": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-linux-x64-gnu/-/resolver-binding-linux-x64-gnu-1.11.1.tgz", - "integrity": "sha512-C3ZAHugKgovV5YvAMsxhq0gtXuwESUKc5MhEtjBpLoHPLYM+iuwSj3lflFwK3DPm68660rZ7G8BMcwSro7hD5w==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@unrs/resolver-binding-linux-x64-musl": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-linux-x64-musl/-/resolver-binding-linux-x64-musl-1.11.1.tgz", - "integrity": "sha512-rV0YSoyhK2nZ4vEswT/QwqzqQXw5I6CjoaYMOX0TqBlWhojUf8P94mvI7nuJTeaCkkds3QE4+zS8Ko+GdXuZtA==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "linux" - ] - }, - "node_modules/@unrs/resolver-binding-wasm32-wasi": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-wasm32-wasi/-/resolver-binding-wasm32-wasi-1.11.1.tgz", - "integrity": "sha512-5u4RkfxJm+Ng7IWgkzi3qrFOvLvQYnPBmjmZQ8+szTK/b31fQCnleNl1GgEt7nIsZRIf5PLhPwT0WM+q45x/UQ==", - "cpu": [ - "wasm32" - ], - "dev": true, - "license": "MIT", - "optional": true, - "dependencies": { - "@napi-rs/wasm-runtime": "^0.2.11" - }, - "engines": { - "node": ">=14.0.0" - } - }, - "node_modules/@unrs/resolver-binding-win32-arm64-msvc": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-win32-arm64-msvc/-/resolver-binding-win32-arm64-msvc-1.11.1.tgz", - "integrity": "sha512-nRcz5Il4ln0kMhfL8S3hLkxI85BXs3o8EYoattsJNdsX4YUU89iOkVn7g0VHSRxFuVMdM4Q1jEpIId1Ihim/Uw==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "win32" - ] - }, - "node_modules/@unrs/resolver-binding-win32-ia32-msvc": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-win32-ia32-msvc/-/resolver-binding-win32-ia32-msvc-1.11.1.tgz", - "integrity": "sha512-DCEI6t5i1NmAZp6pFonpD5m7i6aFrpofcp4LA2i8IIq60Jyo28hamKBxNrZcyOwVOZkgsRp9O2sXWBWP8MnvIQ==", - "cpu": [ - "ia32" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "win32" - ] - }, - "node_modules/@unrs/resolver-binding-win32-x64-msvc": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/@unrs/resolver-binding-win32-x64-msvc/-/resolver-binding-win32-x64-msvc-1.11.1.tgz", - "integrity": "sha512-lrW200hZdbfRtztbygyaq/6jP6AKE8qQN2KvPcJ+x7wiD038YtnYtZ82IMNJ69GJibV7bwL3y9FgK+5w/pYt6g==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "MIT", - "optional": true, - "os": [ - "win32" - ] - }, - "node_modules/acorn": { - "version": "8.15.0", - "resolved": "https://registry.npmjs.org/acorn/-/acorn-8.15.0.tgz", - "integrity": "sha512-NZyJarBfL7nWwIq+FDL6Zp/yHEhePMNnnJ0y3qfieCrmNvYct8uvtiV41UvlSe6apAfk0fY1FbWx+NwfmpvtTg==", - "dev": true, - "license": "MIT", - "bin": { - "acorn": "bin/acorn" - }, - "engines": { - "node": ">=0.4.0" - } - }, - "node_modules/acorn-jsx": { - "version": "5.3.2", - "resolved": "https://registry.npmjs.org/acorn-jsx/-/acorn-jsx-5.3.2.tgz", - "integrity": "sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==", - "dev": true, - "license": "MIT", - "peerDependencies": { - "acorn": "^6.0.0 || ^7.0.0 || ^8.0.0" - } - }, - "node_modules/ajv": { - "version": "6.12.6", - "resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz", - "integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==", - "dev": true, - "license": "MIT", - "dependencies": { - "fast-deep-equal": "^3.1.1", - "fast-json-stable-stringify": "^2.0.0", - "json-schema-traverse": "^0.4.1", - "uri-js": "^4.2.2" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/epoberezkin" - } - }, - "node_modules/ansi-align": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/ansi-align/-/ansi-align-3.0.1.tgz", - "integrity": "sha512-IOfwwBF5iczOjp/WeY4YxyjqAFMQoZufdQWDd19SEExbVLNXqvpzSJ/M7Za4/sCPmQ0+GRquoA7bGcINcxew6w==", - "dev": true, - "license": "ISC", - "dependencies": { - "string-width": "^4.1.0" - } - }, - "node_modules/ansi-escapes": { - "version": "4.3.2", - "resolved": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-4.3.2.tgz", - "integrity": "sha512-gKXj5ALrKWQLsYG9jlTRmR/xKluxHV+Z9QEwNIgCfM1/uwPMCuzVVnh5mwTd+OuBZcwSIMbqssNWRm1lE51QaQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "type-fest": "^0.21.3" - }, - "engines": { - "node": ">=8" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/ansi-escapes/node_modules/type-fest": { - "version": "0.21.3", - "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.21.3.tgz", - "integrity": "sha512-t0rzBq87m3fVcduHDUFhKmyyX+9eo6WQjZvf51Ea/M0Q7+T374Jp1aUiyUl0GKxp8M/OETVHSDvmkyPgvX+X2w==", - "dev": true, - "license": "(MIT OR CC0-1.0)", - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/ansi-regex": { - "version": "6.2.2", - "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-6.2.2.tgz", - "integrity": "sha512-Bq3SmSpyFHaWjPk8If9yc6svM8c56dB5BAtW4Qbw5jHTwwXXcTLoRMkpDJp6VL0XzlWaCHTXrkFURMYmD0sLqg==", - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/chalk/ansi-regex?sponsor=1" - } - }, - "node_modules/ansi-styles": { - "version": "4.3.0", - "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz", - "integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==", - "license": "MIT", - "dependencies": { - "color-convert": "^2.0.1" - }, - "engines": { - "node": ">=8" - }, - "funding": { - "url": "https://github.com/chalk/ansi-styles?sponsor=1" - } - }, - "node_modules/anymatch": { - "version": "3.1.3", - "resolved": "https://registry.npmjs.org/anymatch/-/anymatch-3.1.3.tgz", - "integrity": "sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==", - "dev": true, - "license": "ISC", - "dependencies": { - "normalize-path": "^3.0.0", - "picomatch": "^2.0.4" - }, - "engines": { - "node": ">= 8" - } - }, - "node_modules/anymatch/node_modules/picomatch": { - "version": "2.3.1", - "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz", - "integrity": "sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8.6" - }, - "funding": { - "url": "https://github.com/sponsors/jonschlinkert" - } - }, - "node_modules/arg": { - "version": "5.0.2", - "resolved": "https://registry.npmjs.org/arg/-/arg-5.0.2.tgz", - "integrity": "sha512-PYjyFOLKQ9y57JvQ6QLo8dAgNqswh8M1RMJYdQduT6xbWSgK36P/Z/v+p888pM69jMMfS8Xd8F6I1kQ/I9HUGg==", - "dev": true, - "license": "MIT" - }, - "node_modules/argparse": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz", - "integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==", - "license": "Python-2.0" - }, - "node_modules/aria-query": { - "version": "5.3.2", - "resolved": "https://registry.npmjs.org/aria-query/-/aria-query-5.3.2.tgz", - "integrity": "sha512-COROpnaoap1E2F000S62r6A60uHZnmlvomhfyT2DlTcrY1OrBKn2UhH7qn5wTC9zMvD0AY7csdPSNwKP+7WiQw==", - "dev": true, - "license": "Apache-2.0", - "engines": { - "node": ">= 0.4" - } - }, - "node_modules/array-iterate": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/array-iterate/-/array-iterate-2.0.1.tgz", - "integrity": "sha512-I1jXZMjAgCMmxT4qxXfPXa6SthSoE8h6gkSI9BGGNv8mP8G/v0blc+qFnZu6K42vTOiuME596QaLO0TP3Lk0xg==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/array-union": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/array-union/-/array-union-2.1.0.tgz", - "integrity": "sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/astring": { - "version": "1.9.0", - "resolved": "https://registry.npmjs.org/astring/-/astring-1.9.0.tgz", - "integrity": "sha512-LElXdjswlqjWrPpJFg1Fx4wpkOCxj1TDHlSV4PlaRxHGWko024xICaa97ZkMfs6DRKlCguiAI+rbXv5GWwXIkg==", - "dev": true, - "license": "MIT", - "bin": { - "astring": "bin/astring" - } - }, - "node_modules/astro": { - "version": "5.17.1", - "resolved": "https://registry.npmjs.org/astro/-/astro-5.17.1.tgz", - "integrity": "sha512-oD3tlxTaVWGq/Wfbqk6gxzVRz98xa/rYlpe+gU2jXJMSD01k6sEDL01ZlT8mVSYB/rMgnvIOfiQQ3BbLdN237A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@astrojs/compiler": "^2.13.0", - "@astrojs/internal-helpers": "0.7.5", - "@astrojs/markdown-remark": "6.3.10", - "@astrojs/telemetry": "3.3.0", - "@capsizecss/unpack": "^4.0.0", - "@oslojs/encoding": "^1.1.0", - "@rollup/pluginutils": "^5.3.0", - "acorn": "^8.15.0", - "aria-query": "^5.3.2", - "axobject-query": "^4.1.0", - "boxen": "8.0.1", - "ci-info": "^4.3.1", - "clsx": "^2.1.1", - "common-ancestor-path": "^1.0.1", - "cookie": "^1.1.1", - "cssesc": "^3.0.0", - "debug": "^4.4.3", - "deterministic-object-hash": "^2.0.2", - "devalue": "^5.6.2", - "diff": "^8.0.3", - "dlv": "^1.1.3", - "dset": "^3.1.4", - "es-module-lexer": "^1.7.0", - "esbuild": "^0.25.0", - "estree-walker": "^3.0.3", - "flattie": "^1.1.1", - "fontace": "~0.4.0", - "github-slugger": "^2.0.0", - "html-escaper": "3.0.3", - "http-cache-semantics": "^4.2.0", - "import-meta-resolve": "^4.2.0", - "js-yaml": "^4.1.1", - "magic-string": "^0.30.21", - "magicast": "^0.5.1", - "mrmime": "^2.0.1", - "neotraverse": "^0.6.18", - "p-limit": "^6.2.0", - "p-queue": "^8.1.1", - "package-manager-detector": "^1.6.0", - "piccolore": "^0.1.3", - "picomatch": "^4.0.3", - "prompts": "^2.4.2", - "rehype": "^13.0.2", - "semver": "^7.7.3", - "shiki": "^3.21.0", - "smol-toml": "^1.6.0", - "svgo": "^4.0.0", - "tinyexec": "^1.0.2", - "tinyglobby": "^0.2.15", - "tsconfck": "^3.1.6", - "ultrahtml": "^1.6.0", - "unifont": "~0.7.3", - "unist-util-visit": "^5.0.0", - "unstorage": "^1.17.4", - "vfile": "^6.0.3", - "vite": "^6.4.1", - "vitefu": "^1.1.1", - "xxhash-wasm": "^1.1.0", - "yargs-parser": "^21.1.1", - "yocto-spinner": "^0.2.3", - "zod": "^3.25.76", - "zod-to-json-schema": "^3.25.1", - "zod-to-ts": "^1.2.0" - }, - "bin": { - "astro": "astro.js" - }, - "engines": { - "node": "18.20.8 || ^20.3.0 || >=22.0.0", - "npm": ">=9.6.5", - "pnpm": ">=7.1.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/astrodotbuild" - }, - "optionalDependencies": { - "sharp": "^0.34.0" - } - }, - "node_modules/astro-expressive-code": { - "version": "0.41.6", - "resolved": "https://registry.npmjs.org/astro-expressive-code/-/astro-expressive-code-0.41.6.tgz", - "integrity": "sha512-l47tb1uhmVIebHUkw+HEPtU/av0G4O8Q34g2cbkPvC7/e9ZhANcjUUciKt9Hp6gSVDdIuXBBLwJQn2LkeGMOAw==", - "dev": true, - "license": "MIT", - "dependencies": { - "rehype-expressive-code": "^0.41.6" - }, - "peerDependencies": { - "astro": "^4.0.0-beta || ^5.0.0-beta || ^3.3.0 || ^6.0.0-beta" - } - }, - "node_modules/astro/node_modules/@img/sharp-darwin-arm64": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-darwin-arm64/-/sharp-darwin-arm64-0.34.5.tgz", - "integrity": "sha512-imtQ3WMJXbMY4fxb/Ndp6HBTNVtWCUI0WdobyheGf5+ad6xX8VIDO8u2xE4qc/fr08CKG/7dDseFtn6M6g/r3w==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "darwin" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-darwin-arm64": "1.2.4" - } - }, - "node_modules/astro/node_modules/@img/sharp-darwin-x64": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-darwin-x64/-/sharp-darwin-x64-0.34.5.tgz", - "integrity": "sha512-YNEFAF/4KQ/PeW0N+r+aVVsoIY0/qxxikF2SWdp+NRkmMB7y9LBZAVqQ4yhGCm/H3H270OSykqmQMKLBhBJDEw==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "darwin" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-darwin-x64": "1.2.4" - } - }, - "node_modules/astro/node_modules/@img/sharp-libvips-darwin-arm64": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-darwin-arm64/-/sharp-libvips-darwin-arm64-1.2.4.tgz", - "integrity": "sha512-zqjjo7RatFfFoP0MkQ51jfuFZBnVE2pRiaydKJ1G/rHZvnsrHAOcQALIi9sA5co5xenQdTugCvtb1cuf78Vf4g==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "darwin" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/astro/node_modules/@img/sharp-libvips-darwin-x64": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-darwin-x64/-/sharp-libvips-darwin-x64-1.2.4.tgz", - "integrity": "sha512-1IOd5xfVhlGwX+zXv2N93k0yMONvUlANylbJw1eTah8K/Jtpi15KC+WSiaX/nBmbm2HxRM1gZ0nSdjSsrZbGKg==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "darwin" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/astro/node_modules/@img/sharp-libvips-linux-arm": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-arm/-/sharp-libvips-linux-arm-1.2.4.tgz", - "integrity": "sha512-bFI7xcKFELdiNCVov8e44Ia4u2byA+l3XtsAj+Q8tfCwO6BQ8iDojYdvoPMqsKDkuoOo+X6HZA0s0q11ANMQ8A==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/astro/node_modules/@img/sharp-libvips-linux-arm64": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-arm64/-/sharp-libvips-linux-arm64-1.2.4.tgz", - "integrity": "sha512-excjX8DfsIcJ10x1Kzr4RcWe1edC9PquDRRPx3YVCvQv+U5p7Yin2s32ftzikXojb1PIFc/9Mt28/y+iRklkrw==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/astro/node_modules/@img/sharp-libvips-linux-s390x": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-s390x/-/sharp-libvips-linux-s390x-1.2.4.tgz", - "integrity": "sha512-qmp9VrzgPgMoGZyPvrQHqk02uyjA0/QrTO26Tqk6l4ZV0MPWIW6LTkqOIov+J1yEu7MbFQaDpwdwJKhbJvuRxQ==", - "cpu": [ - "s390x" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/astro/node_modules/@img/sharp-libvips-linux-x64": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-x64/-/sharp-libvips-linux-x64-1.2.4.tgz", - "integrity": "sha512-tJxiiLsmHc9Ax1bz3oaOYBURTXGIRDODBqhveVHonrHJ9/+k89qbLl0bcJns+e4t4rvaNBxaEZsFtSfAdquPrw==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/astro/node_modules/@img/sharp-libvips-linuxmusl-arm64": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linuxmusl-arm64/-/sharp-libvips-linuxmusl-arm64-1.2.4.tgz", - "integrity": "sha512-FVQHuwx1IIuNow9QAbYUzJ+En8KcVm9Lk5+uGUQJHaZmMECZmOlix9HnH7n1TRkXMS0pGxIJokIVB9SuqZGGXw==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/astro/node_modules/@img/sharp-libvips-linuxmusl-x64": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linuxmusl-x64/-/sharp-libvips-linuxmusl-x64-1.2.4.tgz", - "integrity": "sha512-+LpyBk7L44ZIXwz/VYfglaX/okxezESc6UxDSoyo2Ks6Jxc4Y7sGjpgU9s4PMgqgjj1gZCylTieNamqA1MF7Dg==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "LGPL-3.0-or-later", - "optional": true, - "os": [ - "linux" - ], - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/astro/node_modules/@img/sharp-linux-arm": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linux-arm/-/sharp-linux-arm-0.34.5.tgz", - "integrity": "sha512-9dLqsvwtg1uuXBGZKsxem9595+ujv0sJ6Vi8wcTANSFpwV/GONat5eCkzQo/1O6zRIkh0m/8+5BjrRr7jDUSZw==", - "cpu": [ - "arm" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linux-arm": "1.2.4" - } - }, - "node_modules/astro/node_modules/@img/sharp-linux-arm64": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linux-arm64/-/sharp-linux-arm64-0.34.5.tgz", - "integrity": "sha512-bKQzaJRY/bkPOXyKx5EVup7qkaojECG6NLYswgktOZjaXecSAeCWiZwwiFf3/Y+O1HrauiE3FVsGxFg8c24rZg==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linux-arm64": "1.2.4" - } - }, - "node_modules/astro/node_modules/@img/sharp-linux-s390x": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linux-s390x/-/sharp-linux-s390x-0.34.5.tgz", - "integrity": "sha512-nQtCk0PdKfho3eC5MrbQoigJ2gd1CgddUMkabUj+rBevs8tZ2cULOx46E7oyX+04WGfABgIwmMC0VqieTiR4jg==", - "cpu": [ - "s390x" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linux-s390x": "1.2.4" - } - }, - "node_modules/astro/node_modules/@img/sharp-linux-x64": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linux-x64/-/sharp-linux-x64-0.34.5.tgz", - "integrity": "sha512-MEzd8HPKxVxVenwAa+JRPwEC7QFjoPWuS5NZnBt6B3pu7EG2Ge0id1oLHZpPJdn3OQK+BQDiw9zStiHBTJQQQQ==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linux-x64": "1.2.4" - } - }, - "node_modules/astro/node_modules/@img/sharp-linuxmusl-arm64": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linuxmusl-arm64/-/sharp-linuxmusl-arm64-0.34.5.tgz", - "integrity": "sha512-fprJR6GtRsMt6Kyfq44IsChVZeGN97gTD331weR1ex1c1rypDEABN6Tm2xa1wE6lYb5DdEnk03NZPqA7Id21yg==", - "cpu": [ - "arm64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linuxmusl-arm64": "1.2.4" - } - }, - "node_modules/astro/node_modules/@img/sharp-linuxmusl-x64": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-linuxmusl-x64/-/sharp-linuxmusl-x64-0.34.5.tgz", - "integrity": "sha512-Jg8wNT1MUzIvhBFxViqrEhWDGzqymo3sV7z7ZsaWbZNDLXRJZoRGrjulp60YYtV4wfY8VIKcWidjojlLcWrd8Q==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "Apache-2.0", - "optional": true, - "os": [ - "linux" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-libvips-linuxmusl-x64": "1.2.4" - } - }, - "node_modules/astro/node_modules/@img/sharp-wasm32": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-wasm32/-/sharp-wasm32-0.34.5.tgz", - "integrity": "sha512-OdWTEiVkY2PHwqkbBI8frFxQQFekHaSSkUIJkwzclWZe64O1X4UlUjqqqLaPbUpMOQk6FBu/HtlGXNblIs0huw==", - "cpu": [ - "wasm32" - ], - "dev": true, - "license": "Apache-2.0 AND LGPL-3.0-or-later AND MIT", - "optional": true, - "dependencies": { - "@emnapi/runtime": "^1.7.0" - }, - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/astro/node_modules/@img/sharp-win32-ia32": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-win32-ia32/-/sharp-win32-ia32-0.34.5.tgz", - "integrity": "sha512-FV9m/7NmeCmSHDD5j4+4pNI8Cp3aW+JvLoXcTUo0IqyjSfAZJ8dIUmijx1qaJsIiU+Hosw6xM5KijAWRJCSgNg==", - "cpu": [ - "ia32" - ], - "dev": true, - "license": "Apache-2.0 AND LGPL-3.0-or-later", - "optional": true, - "os": [ - "win32" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/astro/node_modules/@img/sharp-win32-x64": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/@img/sharp-win32-x64/-/sharp-win32-x64-0.34.5.tgz", - "integrity": "sha512-+29YMsqY2/9eFEiW93eqWnuLcWcufowXewwSNIT6UwZdUUCrM3oFjMWH/Z6/TMmb4hlFenmfAVbpWeup2jryCw==", - "cpu": [ - "x64" - ], - "dev": true, - "license": "Apache-2.0 AND LGPL-3.0-or-later", - "optional": true, - "os": [ - "win32" - ], - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - } - }, - "node_modules/astro/node_modules/ansi-styles": { - "version": "6.2.3", - "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-6.2.3.tgz", - "integrity": "sha512-4Dj6M28JB+oAH8kFkTLUo+a2jwOFkuqb3yucU0CANcRRUbxS0cP0nZYCGjcc3BNXwRIsUVmDGgzawme7zvJHvg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/chalk/ansi-styles?sponsor=1" - } - }, - "node_modules/astro/node_modules/boxen": { - "version": "8.0.1", - "resolved": "https://registry.npmjs.org/boxen/-/boxen-8.0.1.tgz", - "integrity": "sha512-F3PH5k5juxom4xktynS7MoFY+NUWH5LC4CnH11YB8NPew+HLpmBLCybSAEyb2F+4pRXhuhWqFesoQd6DAyc2hw==", - "dev": true, - "license": "MIT", - "dependencies": { - "ansi-align": "^3.0.1", - "camelcase": "^8.0.0", - "chalk": "^5.3.0", - "cli-boxes": "^3.0.0", - "string-width": "^7.2.0", - "type-fest": "^4.21.0", - "widest-line": "^5.0.0", - "wrap-ansi": "^9.0.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/astro/node_modules/camelcase": { - "version": "8.0.0", - "resolved": "https://registry.npmjs.org/camelcase/-/camelcase-8.0.0.tgz", - "integrity": "sha512-8WB3Jcas3swSvjIeA2yvCJ+Miyz5l1ZmB6HFb9R1317dt9LCQoswg/BGrmAmkWVEszSrrg4RwmO46qIm2OEnSA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=16" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/astro/node_modules/chalk": { - "version": "5.6.2", - "resolved": "https://registry.npmjs.org/chalk/-/chalk-5.6.2.tgz", - "integrity": "sha512-7NzBL0rN6fMUW+f7A6Io4h40qQlG+xGmtMxfbnH/K7TAtt8JQWVQK+6g0UXKMeVJoyV5EkkNsErQ8pVD3bLHbA==", - "dev": true, - "license": "MIT", - "engines": { - "node": "^12.17.0 || ^14.13 || >=16.0.0" - }, - "funding": { - "url": "https://github.com/chalk/chalk?sponsor=1" - } - }, - "node_modules/astro/node_modules/cli-boxes": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/cli-boxes/-/cli-boxes-3.0.0.tgz", - "integrity": "sha512-/lzGpEWL/8PfI0BmBOPRwp0c/wFNX1RdUML3jK/RcSBA9T8mZDdQpqYBKtCFTOfQbwPqWEOpjqW+Fnayc0969g==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/astro/node_modules/emoji-regex": { - "version": "10.6.0", - "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-10.6.0.tgz", - "integrity": "sha512-toUI84YS5YmxW219erniWD0CIVOo46xGKColeNQRgOzDorgBi1v4D71/OFzgD9GO2UGKIv1C3Sp8DAn0+j5w7A==", - "dev": true, - "license": "MIT" - }, - "node_modules/astro/node_modules/sharp": { - "version": "0.34.5", - "resolved": "https://registry.npmjs.org/sharp/-/sharp-0.34.5.tgz", - "integrity": "sha512-Ou9I5Ft9WNcCbXrU9cMgPBcCK8LiwLqcbywW3t4oDV37n1pzpuNLsYiAV8eODnjbtQlSDwZ2cUEeQz4E54Hltg==", - "dev": true, - "hasInstallScript": true, - "license": "Apache-2.0", - "optional": true, - "dependencies": { - "@img/colour": "^1.0.0", - "detect-libc": "^2.1.2", - "semver": "^7.7.3" - }, - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-darwin-arm64": "0.34.5", - "@img/sharp-darwin-x64": "0.34.5", - "@img/sharp-libvips-darwin-arm64": "1.2.4", - "@img/sharp-libvips-darwin-x64": "1.2.4", - "@img/sharp-libvips-linux-arm": "1.2.4", - "@img/sharp-libvips-linux-arm64": "1.2.4", - "@img/sharp-libvips-linux-ppc64": "1.2.4", - "@img/sharp-libvips-linux-riscv64": "1.2.4", - "@img/sharp-libvips-linux-s390x": "1.2.4", - "@img/sharp-libvips-linux-x64": "1.2.4", - "@img/sharp-libvips-linuxmusl-arm64": "1.2.4", - "@img/sharp-libvips-linuxmusl-x64": "1.2.4", - "@img/sharp-linux-arm": "0.34.5", - "@img/sharp-linux-arm64": "0.34.5", - "@img/sharp-linux-ppc64": "0.34.5", - "@img/sharp-linux-riscv64": "0.34.5", - "@img/sharp-linux-s390x": "0.34.5", - "@img/sharp-linux-x64": "0.34.5", - "@img/sharp-linuxmusl-arm64": "0.34.5", - "@img/sharp-linuxmusl-x64": "0.34.5", - "@img/sharp-wasm32": "0.34.5", - "@img/sharp-win32-arm64": "0.34.5", - "@img/sharp-win32-ia32": "0.34.5", - "@img/sharp-win32-x64": "0.34.5" - } - }, - "node_modules/astro/node_modules/string-width": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/string-width/-/string-width-7.2.0.tgz", - "integrity": "sha512-tsaTIkKW9b4N+AEj+SVA+WhJzV7/zMhcSu78mLKWSk7cXMOSHsBKFWUs0fWwq8QyK3MgJBQRX6Gbi4kYbdvGkQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "emoji-regex": "^10.3.0", - "get-east-asian-width": "^1.0.0", - "strip-ansi": "^7.1.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/astro/node_modules/type-fest": { - "version": "4.41.0", - "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-4.41.0.tgz", - "integrity": "sha512-TeTSQ6H5YHvpqVwBRcnLDCBnDOHWYu7IvGbHT6N8AOymcr9PJGjc1GTtiWZTYg0NCgYwvnYWEkVChQAr9bjfwA==", - "dev": true, - "license": "(MIT OR CC0-1.0)", - "engines": { - "node": ">=16" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/astro/node_modules/widest-line": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/widest-line/-/widest-line-5.0.0.tgz", - "integrity": "sha512-c9bZp7b5YtRj2wOe6dlj32MK+Bx/M/d+9VB2SHM1OtsUHR0aV0tdP6DWh/iMt0kWi1t5g1Iudu6hQRNd1A4PVA==", - "dev": true, - "license": "MIT", - "dependencies": { - "string-width": "^7.0.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/astro/node_modules/wrap-ansi": { - "version": "9.0.2", - "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-9.0.2.tgz", - "integrity": "sha512-42AtmgqjV+X1VpdOfyTGOYRi0/zsoLqtXQckTmqTeybT+BDIbM/Guxo7x3pE2vtpr1ok6xRqM9OpBe+Jyoqyww==", - "dev": true, - "license": "MIT", - "dependencies": { - "ansi-styles": "^6.2.1", - "string-width": "^7.0.0", - "strip-ansi": "^7.1.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/chalk/wrap-ansi?sponsor=1" - } - }, - "node_modules/async": { - "version": "3.2.6", - "resolved": "https://registry.npmjs.org/async/-/async-3.2.6.tgz", - "integrity": "sha512-htCUDlxyyCLMgaM3xXg0C0LW2xqfuQ6p05pCEIsXuyQ+a1koYKTuBMzRNwmybfLgvJDMd0r1LTn4+E0Ti6C2AA==", - "dev": true, - "license": "MIT" - }, - "node_modules/axobject-query": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/axobject-query/-/axobject-query-4.1.0.tgz", - "integrity": "sha512-qIj0G9wZbMGNLjLmg1PT6v2mE9AH2zlnADJD/2tC6E00hgmhUOfEB6greHPAfLRSufHqROIUTkw6E+M3lH0PTQ==", - "dev": true, - "license": "Apache-2.0", - "engines": { - "node": ">= 0.4" - } - }, - "node_modules/babel-jest": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/babel-jest/-/babel-jest-30.2.0.tgz", - "integrity": "sha512-0YiBEOxWqKkSQWL9nNGGEgndoeL0ZpWrbLMNL5u/Kaxrli3Eaxlt3ZtIDktEvXt4L/R9r3ODr2zKwGM/2BjxVw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/transform": "30.2.0", - "@types/babel__core": "^7.20.5", - "babel-plugin-istanbul": "^7.0.1", - "babel-preset-jest": "30.2.0", - "chalk": "^4.1.2", - "graceful-fs": "^4.2.11", - "slash": "^3.0.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - }, - "peerDependencies": { - "@babel/core": "^7.11.0 || ^8.0.0-0" - } - }, - "node_modules/babel-plugin-istanbul": { - "version": "7.0.1", - "resolved": "https://registry.npmjs.org/babel-plugin-istanbul/-/babel-plugin-istanbul-7.0.1.tgz", - "integrity": "sha512-D8Z6Qm8jCvVXtIRkBnqNHX0zJ37rQcFJ9u8WOS6tkYOsRdHBzypCstaxWiu5ZIlqQtviRYbgnRLSoCEvjqcqbA==", - "dev": true, - "license": "BSD-3-Clause", - "workspaces": [ - "test/babel-8" - ], - "dependencies": { - "@babel/helper-plugin-utils": "^7.0.0", - "@istanbuljs/load-nyc-config": "^1.0.0", - "@istanbuljs/schema": "^0.1.3", - "istanbul-lib-instrument": "^6.0.2", - "test-exclude": "^6.0.0" - }, - "engines": { - "node": ">=12" - } - }, - "node_modules/babel-plugin-istanbul/node_modules/glob": { - "version": "7.2.3", - "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.3.tgz", - "integrity": "sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==", - "deprecated": "Glob versions prior to v9 are no longer supported", - "dev": true, - "license": "ISC", - "dependencies": { - "fs.realpath": "^1.0.0", - "inflight": "^1.0.4", - "inherits": "2", - "minimatch": "^3.1.1", - "once": "^1.3.0", - "path-is-absolute": "^1.0.0" - }, - "engines": { - "node": "*" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/babel-plugin-istanbul/node_modules/test-exclude": { - "version": "6.0.0", - "resolved": "https://registry.npmjs.org/test-exclude/-/test-exclude-6.0.0.tgz", - "integrity": "sha512-cAGWPIyOHU6zlmg88jwm7VRyXnMN7iV68OGAbYDk/Mh/xC/pzVPlQtY6ngoIH/5/tciuhGfvESU8GrHrcxD56w==", - "dev": true, - "license": "ISC", - "dependencies": { - "@istanbuljs/schema": "^0.1.2", - "glob": "^7.1.4", - "minimatch": "^3.0.4" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/babel-plugin-jest-hoist": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/babel-plugin-jest-hoist/-/babel-plugin-jest-hoist-30.2.0.tgz", - "integrity": "sha512-ftzhzSGMUnOzcCXd6WHdBGMyuwy15Wnn0iyyWGKgBDLxf9/s5ABuraCSpBX2uG0jUg4rqJnxsLc5+oYBqoxVaA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/babel__core": "^7.20.5" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/babel-preset-current-node-syntax": { - "version": "1.2.0", - "resolved": "https://registry.npmjs.org/babel-preset-current-node-syntax/-/babel-preset-current-node-syntax-1.2.0.tgz", - "integrity": "sha512-E/VlAEzRrsLEb2+dv8yp3bo4scof3l9nR4lrld+Iy5NyVqgVYUJnDAmunkhPMisRI32Qc4iRiz425d8vM++2fg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/plugin-syntax-async-generators": "^7.8.4", - "@babel/plugin-syntax-bigint": "^7.8.3", - "@babel/plugin-syntax-class-properties": "^7.12.13", - "@babel/plugin-syntax-class-static-block": "^7.14.5", - "@babel/plugin-syntax-import-attributes": "^7.24.7", - "@babel/plugin-syntax-import-meta": "^7.10.4", - "@babel/plugin-syntax-json-strings": "^7.8.3", - "@babel/plugin-syntax-logical-assignment-operators": "^7.10.4", - "@babel/plugin-syntax-nullish-coalescing-operator": "^7.8.3", - "@babel/plugin-syntax-numeric-separator": "^7.10.4", - "@babel/plugin-syntax-object-rest-spread": "^7.8.3", - "@babel/plugin-syntax-optional-catch-binding": "^7.8.3", - "@babel/plugin-syntax-optional-chaining": "^7.8.3", - "@babel/plugin-syntax-private-property-in-object": "^7.14.5", - "@babel/plugin-syntax-top-level-await": "^7.14.5" - }, - "peerDependencies": { - "@babel/core": "^7.0.0 || ^8.0.0-0" - } - }, - "node_modules/babel-preset-jest": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/babel-preset-jest/-/babel-preset-jest-30.2.0.tgz", - "integrity": "sha512-US4Z3NOieAQumwFnYdUWKvUKh8+YSnS/gB3t6YBiz0bskpu7Pine8pPCheNxlPEW4wnUkma2a94YuW2q3guvCQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "babel-plugin-jest-hoist": "30.2.0", - "babel-preset-current-node-syntax": "^1.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - }, - "peerDependencies": { - "@babel/core": "^7.11.0 || ^8.0.0-beta.1" - } - }, - "node_modules/bail": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/bail/-/bail-2.0.2.tgz", - "integrity": "sha512-0xO6mYd7JB2YesxDKplafRpsiOzPt9V02ddPCLbY1xYGPOX24NTyN50qnUxgCPcSoYMhKpAuBTjQoRZCAkUDRw==", - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/balanced-match": { - "version": "1.0.2", - "resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.2.tgz", - "integrity": "sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==", - "dev": true, - "license": "MIT" - }, - "node_modules/base-64": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/base-64/-/base-64-1.0.0.tgz", - "integrity": "sha512-kwDPIFCGx0NZHog36dj+tHiwP4QMzsZ3AgMViUBKI0+V5n4U0ufTCUMhnQ04diaRI8EX/QcPfql7zlhZ7j4zgg==", - "dev": true, - "license": "MIT" - }, - "node_modules/baseline-browser-mapping": { - "version": "2.9.19", - "resolved": "https://registry.npmjs.org/baseline-browser-mapping/-/baseline-browser-mapping-2.9.19.tgz", - "integrity": "sha512-ipDqC8FrAl/76p2SSWKSI+H9tFwm7vYqXQrItCuiVPt26Km0jS+NzSsBWAaBusvSbQcfJG+JitdMm+wZAgTYqg==", - "dev": true, - "license": "Apache-2.0", - "bin": { - "baseline-browser-mapping": "dist/cli.js" - } - }, - "node_modules/bcp-47": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/bcp-47/-/bcp-47-2.1.0.tgz", - "integrity": "sha512-9IIS3UPrvIa1Ej+lVDdDwO7zLehjqsaByECw0bu2RRGP73jALm6FYbzI5gWbgHLvNdkvfXB5YrSbocZdOS0c0w==", - "dev": true, - "license": "MIT", - "dependencies": { - "is-alphabetical": "^2.0.0", - "is-alphanumerical": "^2.0.0", - "is-decimal": "^2.0.0" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/bcp-47-match": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/bcp-47-match/-/bcp-47-match-2.0.3.tgz", - "integrity": "sha512-JtTezzbAibu8G0R9op9zb3vcWZd9JF6M0xOYGPn0fNCd7wOpRB1mU2mH9T8gaBGbAAyIIVgB2G7xG0GP98zMAQ==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/boolbase": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/boolbase/-/boolbase-1.0.0.tgz", - "integrity": "sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww==", - "license": "ISC" - }, - "node_modules/brace-expansion": { - "version": "1.1.12", - "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.12.tgz", - "integrity": "sha512-9T9UjW3r0UW5c1Q7GTwllptXwhvYmEzFhzMfZ9H7FQWt+uZePjZPjBP/W1ZEyZ1twGWom5/56TF4lPcqjnDHcg==", - "dev": true, - "license": "MIT", - "dependencies": { - "balanced-match": "^1.0.0", - "concat-map": "0.0.1" - } - }, - "node_modules/braces": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/braces/-/braces-3.0.3.tgz", - "integrity": "sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==", - "dev": true, - "license": "MIT", - "dependencies": { - "fill-range": "^7.1.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/browserslist": { - "version": "4.28.1", - "resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.28.1.tgz", - "integrity": "sha512-ZC5Bd0LgJXgwGqUknZY/vkUQ04r8NXnJZ3yYi4vDmSiZmC/pdSN0NbNRPxZpbtO4uAfDUAFffO8IZoM3Gj8IkA==", - "dev": true, - "funding": [ - { - "type": "opencollective", - "url": "https://opencollective.com/browserslist" - }, - { - "type": "tidelift", - "url": "https://tidelift.com/funding/github/npm/browserslist" - }, - { - "type": "github", - "url": "https://github.com/sponsors/ai" - } - ], - "license": "MIT", - "dependencies": { - "baseline-browser-mapping": "^2.9.0", - "caniuse-lite": "^1.0.30001759", - "electron-to-chromium": "^1.5.263", - "node-releases": "^2.0.27", - "update-browserslist-db": "^1.2.0" - }, - "bin": { - "browserslist": "cli.js" - }, - "engines": { - "node": "^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7" - } - }, - "node_modules/bser": { - "version": "2.1.1", - "resolved": "https://registry.npmjs.org/bser/-/bser-2.1.1.tgz", - "integrity": "sha512-gQxTNE/GAfIIrmHLUE3oJyp5FO6HRBfhjnw4/wMmA63ZGDJnWBmgY/lyQBpnDUkGmAhbSe39tx2d/iTOAfglwQ==", - "dev": true, - "license": "Apache-2.0", - "dependencies": { - "node-int64": "^0.4.0" - } - }, - "node_modules/buffer-from": { - "version": "1.1.2", - "resolved": "https://registry.npmjs.org/buffer-from/-/buffer-from-1.1.2.tgz", - "integrity": "sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/builtin-modules": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/builtin-modules/-/builtin-modules-5.0.0.tgz", - "integrity": "sha512-bkXY9WsVpY7CvMhKSR6pZilZu9Ln5WDrKVBUXf2S443etkmEO4V58heTecXcUIsNsi4Rx8JUO4NfX1IcQl4deg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18.20" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/c8": { - "version": "10.1.3", - "resolved": "https://registry.npmjs.org/c8/-/c8-10.1.3.tgz", - "integrity": "sha512-LvcyrOAaOnrrlMpW22n690PUvxiq4Uf9WMhQwNJ9vgagkL/ph1+D4uvjvDA5XCbykrc0sx+ay6pVi9YZ1GnhyA==", - "dev": true, - "license": "ISC", - "dependencies": { - "@bcoe/v8-coverage": "^1.0.1", - "@istanbuljs/schema": "^0.1.3", - "find-up": "^5.0.0", - "foreground-child": "^3.1.1", - "istanbul-lib-coverage": "^3.2.0", - "istanbul-lib-report": "^3.0.1", - "istanbul-reports": "^3.1.6", - "test-exclude": "^7.0.1", - "v8-to-istanbul": "^9.0.0", - "yargs": "^17.7.2", - "yargs-parser": "^21.1.1" - }, - "bin": { - "c8": "bin/c8.js" - }, - "engines": { - "node": ">=18" - }, - "peerDependencies": { - "monocart-coverage-reports": "^2" - }, - "peerDependenciesMeta": { - "monocart-coverage-reports": { - "optional": true - } - } - }, - "node_modules/callsites": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz", - "integrity": "sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/camelcase": { - "version": "6.3.0", - "resolved": "https://registry.npmjs.org/camelcase/-/camelcase-6.3.0.tgz", - "integrity": "sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/caniuse-lite": { - "version": "1.0.30001766", - "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001766.tgz", - "integrity": "sha512-4C0lfJ0/YPjJQHagaE9x2Elb69CIqEPZeG0anQt9SIvIoOH4a4uaRl73IavyO+0qZh6MDLH//DrXThEYKHkmYA==", - "dev": true, - "funding": [ - { - "type": "opencollective", - "url": "https://opencollective.com/browserslist" - }, - { - "type": "tidelift", - "url": "https://tidelift.com/funding/github/npm/caniuse-lite" - }, - { - "type": "github", - "url": "https://github.com/sponsors/ai" - } - ], - "license": "CC-BY-4.0" - }, - "node_modules/ccount": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/ccount/-/ccount-2.0.1.tgz", - "integrity": "sha512-eyrF0jiFpY+3drT6383f1qhkbGsLSifNAjA61IUjZjmLCWjItY6LB9ft9YhoDgwfmclB2zhu51Lc7+95b8NRAg==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/chalk": { - "version": "4.1.2", - "resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz", - "integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==", - "license": "MIT", - "dependencies": { - "ansi-styles": "^4.1.0", - "supports-color": "^7.1.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/chalk/chalk?sponsor=1" - } - }, - "node_modules/change-case": { - "version": "5.4.4", - "resolved": "https://registry.npmjs.org/change-case/-/change-case-5.4.4.tgz", - "integrity": "sha512-HRQyTk2/YPEkt9TnUPbOpr64Uw3KOicFWPVBb+xiHvd6eBx/qPr9xqfBFDT8P2vWsvvz4jbEkfDe71W3VyNu2w==", - "dev": true, - "license": "MIT" - }, - "node_modules/char-regex": { - "version": "1.0.2", - "resolved": "https://registry.npmjs.org/char-regex/-/char-regex-1.0.2.tgz", - "integrity": "sha512-kWWXztvZ5SBQV+eRgKFeh8q5sLuZY2+8WUIzlxWVTg+oGwY14qylx1KbKzHd8P6ZYkAg0xyIDU9JMHhyJMZ1jw==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=10" - } - }, - "node_modules/character-entities": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/character-entities/-/character-entities-2.0.2.tgz", - "integrity": "sha512-shx7oQ0Awen/BRIdkjkvz54PnEEI/EjwXDSIZp86/KKdbafHh1Df/RYGBhn4hbe2+uKC9FnT5UCEdyPz3ai9hQ==", - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/character-entities-html4": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/character-entities-html4/-/character-entities-html4-2.1.0.tgz", - "integrity": "sha512-1v7fgQRj6hnSwFpq1Eu0ynr/CDEw0rXo2B61qXrLNdHZmPKgb7fqS1a2JwF0rISo9q77jDI8VMEHoApn8qDoZA==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/character-entities-legacy": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/character-entities-legacy/-/character-entities-legacy-3.0.0.tgz", - "integrity": "sha512-RpPp0asT/6ufRm//AJVwpViZbGM/MkjQFxJccQRHmISF/22NBtsHqAWmL+/pmkPWoIUJdWyeVleTl1wydHATVQ==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/character-reference-invalid": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/character-reference-invalid/-/character-reference-invalid-2.0.1.tgz", - "integrity": "sha512-iBZ4F4wRbyORVsu0jPV7gXkOsGYjGHPmAyv+HiHG8gi5PtC9KI2j1+v8/tlibRvjoWX027ypmG/n0HtO5t7unw==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/chokidar": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-5.0.0.tgz", - "integrity": "sha512-TQMmc3w+5AxjpL8iIiwebF73dRDF4fBIieAqGn9RGCWaEVwQ6Fb2cGe31Yns0RRIzii5goJ1Y7xbMwo1TxMplw==", - "dev": true, - "license": "MIT", - "dependencies": { - "readdirp": "^5.0.0" - }, - "engines": { - "node": ">= 20.19.0" - }, - "funding": { - "url": "https://paulmillr.com/funding/" - } - }, - "node_modules/ci-info": { - "version": "4.4.0", - "resolved": "https://registry.npmjs.org/ci-info/-/ci-info-4.4.0.tgz", - "integrity": "sha512-77PSwercCZU2Fc4sX94eF8k8Pxte6JAwL4/ICZLFjJLqegs7kCuAsqqj/70NQF6TvDpgFjkubQB2FW2ZZddvQg==", - "dev": true, - "funding": [ - { - "type": "github", - "url": "https://github.com/sponsors/sibiraj-s" - } - ], - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/cjs-module-lexer": { - "version": "2.2.0", - "resolved": "https://registry.npmjs.org/cjs-module-lexer/-/cjs-module-lexer-2.2.0.tgz", - "integrity": "sha512-4bHTS2YuzUvtoLjdy+98ykbNB5jS0+07EvFNXerqZQJ89F7DI6ET7OQo/HJuW6K0aVsKA9hj9/RVb2kQVOrPDQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/clean-regexp": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/clean-regexp/-/clean-regexp-1.0.0.tgz", - "integrity": "sha512-GfisEZEJvzKrmGWkvfhgzcz/BllN1USeqD2V6tg14OAOgaCD2Z/PUEuxnAZ/nPvmaHRG7a8y77p1T/IRQ4D1Hw==", - "dev": true, - "license": "MIT", - "dependencies": { - "escape-string-regexp": "^1.0.5" - }, - "engines": { - "node": ">=4" - } - }, - "node_modules/clean-regexp/node_modules/escape-string-regexp": { - "version": "1.0.5", - "resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-1.0.5.tgz", - "integrity": "sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=0.8.0" - } - }, - "node_modules/cli-cursor": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/cli-cursor/-/cli-cursor-5.0.0.tgz", - "integrity": "sha512-aCj4O5wKyszjMmDT4tZj93kxyydN/K5zPWSCe6/0AV/AA1pqe5ZBIw0a2ZfPQV7lL5/yb5HsUreJ6UFAF1tEQw==", - "dev": true, - "license": "MIT", - "dependencies": { - "restore-cursor": "^5.0.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/cli-truncate": { - "version": "5.1.1", - "resolved": "https://registry.npmjs.org/cli-truncate/-/cli-truncate-5.1.1.tgz", - "integrity": "sha512-SroPvNHxUnk+vIW/dOSfNqdy1sPEFkrTk6TUtqLCnBlo3N7TNYYkzzN7uSD6+jVjrdO4+p8nH7JzH6cIvUem6A==", - "dev": true, - "license": "MIT", - "dependencies": { - "slice-ansi": "^7.1.0", - "string-width": "^8.0.0" - }, - "engines": { - "node": ">=20" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/cli-truncate/node_modules/string-width": { - "version": "8.1.1", - "resolved": "https://registry.npmjs.org/string-width/-/string-width-8.1.1.tgz", - "integrity": "sha512-KpqHIdDL9KwYk22wEOg/VIqYbrnLeSApsKT/bSj6Ez7pn3CftUiLAv2Lccpq1ALcpLV9UX1Ppn92npZWu2w/aw==", - "dev": true, - "license": "MIT", - "dependencies": { - "get-east-asian-width": "^1.3.0", - "strip-ansi": "^7.1.0" - }, - "engines": { - "node": ">=20" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/cliui": { - "version": "8.0.1", - "resolved": "https://registry.npmjs.org/cliui/-/cliui-8.0.1.tgz", - "integrity": "sha512-BSeNnyus75C4//NQ9gQt1/csTXyo/8Sb+afLAkzAptFuMsod9HFokGNudZpi/oQV73hnVK+sR+5PVRMd+Dr7YQ==", - "dev": true, - "license": "ISC", - "dependencies": { - "string-width": "^4.2.0", - "strip-ansi": "^6.0.1", - "wrap-ansi": "^7.0.0" - }, - "engines": { - "node": ">=12" - } - }, - "node_modules/cliui/node_modules/ansi-regex": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", - "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/cliui/node_modules/strip-ansi": { - "version": "6.0.1", - "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", - "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", - "dev": true, - "license": "MIT", - "dependencies": { - "ansi-regex": "^5.0.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/clsx": { - "version": "2.1.1", - "resolved": "https://registry.npmjs.org/clsx/-/clsx-2.1.1.tgz", - "integrity": "sha512-eYm0QWBtUrBWZWG0d386OGAw16Z995PiOVo2B7bjWSbHedGl5e0ZWaq65kOGgUSNesEIDkB9ISbTg/JK9dhCZA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/co": { - "version": "4.6.0", - "resolved": "https://registry.npmjs.org/co/-/co-4.6.0.tgz", - "integrity": "sha512-QVb0dM5HvG+uaxitm8wONl7jltx8dqhfU33DcqtOZcLSVIKSDDLDi7+0LbAKiyI8hD9u42m2YxXSkMGWThaecQ==", - "dev": true, - "license": "MIT", - "engines": { - "iojs": ">= 1.0.0", - "node": ">= 0.12.0" - } - }, - "node_modules/collapse-white-space": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/collapse-white-space/-/collapse-white-space-2.1.0.tgz", - "integrity": "sha512-loKTxY1zCOuG4j9f6EPnuyyYkf58RnhhWTvRoZEokgB+WbdXehfjFviyOVYkqzEWz1Q5kRiZdBYS5SwxbQYwzw==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/collect-v8-coverage": { - "version": "1.0.3", - "resolved": "https://registry.npmjs.org/collect-v8-coverage/-/collect-v8-coverage-1.0.3.tgz", - "integrity": "sha512-1L5aqIkwPfiodaMgQunkF1zRhNqifHBmtbbbxcr6yVxxBnliw4TDOW6NxpO8DJLgJ16OT+Y4ztZqP6p/FtXnAw==", - "dev": true, - "license": "MIT" - }, - "node_modules/color": { - "version": "4.2.3", - "resolved": "https://registry.npmjs.org/color/-/color-4.2.3.tgz", - "integrity": "sha512-1rXeuUUiGGrykh+CeBdu5Ie7OJwinCgQY0bc7GCRxy5xVHy+moaqkpL/jqQq0MtQOeYcrqEz4abc5f0KtU7W4A==", - "dev": true, - "license": "MIT", - "dependencies": { - "color-convert": "^2.0.1", - "color-string": "^1.9.0" - }, - "engines": { - "node": ">=12.5.0" - } - }, - "node_modules/color-convert": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz", - "integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==", - "license": "MIT", - "dependencies": { - "color-name": "~1.1.4" - }, - "engines": { - "node": ">=7.0.0" - } - }, - "node_modules/color-name": { - "version": "1.1.4", - "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz", - "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==", - "license": "MIT" - }, - "node_modules/color-string": { - "version": "1.9.1", - "resolved": "https://registry.npmjs.org/color-string/-/color-string-1.9.1.tgz", - "integrity": "sha512-shrVawQFojnZv6xM40anx4CkoDP+fZsw/ZerEMsW/pyzsRbElpsL/DBVW7q3ExxwusdNXI3lXpuhEZkzs8p5Eg==", - "dev": true, - "license": "MIT", - "dependencies": { - "color-name": "^1.0.0", - "simple-swizzle": "^0.2.2" - } - }, - "node_modules/colorette": { - "version": "2.0.20", - "resolved": "https://registry.npmjs.org/colorette/-/colorette-2.0.20.tgz", - "integrity": "sha512-IfEDxwoWIjkeXL1eXcDiow4UbKjhLdq6/EuSVR9GMN7KVH3r9gQ83e73hsz1Nd1T3ijd5xv1wcWRYO+D6kCI2w==", - "dev": true, - "license": "MIT" - }, - "node_modules/comma-separated-tokens": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/comma-separated-tokens/-/comma-separated-tokens-2.0.3.tgz", - "integrity": "sha512-Fu4hJdvzeylCfQPp9SGWidpzrMs7tTrlu6Vb8XGaRGck8QSNZJJp538Wrb60Lax4fPwR64ViY468OIUTbRlGZg==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/commander": { - "version": "14.0.2", - "resolved": "https://registry.npmjs.org/commander/-/commander-14.0.2.tgz", - "integrity": "sha512-TywoWNNRbhoD0BXs1P3ZEScW8W5iKrnbithIl0YH+uCmBd0QpPOA8yc82DS3BIE5Ma6FnBVUsJ7wVUDz4dvOWQ==", - "license": "MIT", - "engines": { - "node": ">=20" - } - }, - "node_modules/common-ancestor-path": { - "version": "1.0.1", - "resolved": "https://registry.npmjs.org/common-ancestor-path/-/common-ancestor-path-1.0.1.tgz", - "integrity": "sha512-L3sHRo1pXXEqX8VU28kfgUY+YGsk09hPqZiZmLacNib6XNTCM8ubYeT7ryXQw8asB1sKgcU5lkB7ONug08aB8w==", - "dev": true, - "license": "ISC" - }, - "node_modules/concat-map": { - "version": "0.0.1", - "resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz", - "integrity": "sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==", - "dev": true, - "license": "MIT" - }, - "node_modules/consola": { - "version": "2.15.3", - "resolved": "https://registry.npmjs.org/consola/-/consola-2.15.3.tgz", - "integrity": "sha512-9vAdYbHj6x2fLKC4+oPH0kFzY/orMZyG2Aj+kNylHxKGJ/Ed4dpNyAQYwJOdqO4zdM7XpVHmyejQDcQHrnuXbw==", - "dev": true, - "license": "MIT" - }, - "node_modules/convert-source-map": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-2.0.0.tgz", - "integrity": "sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg==", - "dev": true, - "license": "MIT" - }, - "node_modules/cookie": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/cookie/-/cookie-1.1.1.tgz", - "integrity": "sha512-ei8Aos7ja0weRpFzJnEA9UHJ/7XQmqglbRwnf2ATjcB9Wq874VKH9kfjjirM6UhU2/E5fFYadylyhFldcqSidQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/express" - } - }, - "node_modules/cookie-es": { - "version": "1.2.2", - "resolved": "https://registry.npmjs.org/cookie-es/-/cookie-es-1.2.2.tgz", - "integrity": "sha512-+W7VmiVINB+ywl1HGXJXmrqkOhpKrIiVZV6tQuV54ZyQC7MMuBt81Vc336GMLoHBq5hV/F9eXgt5Mnx0Rha5Fg==", - "dev": true, - "license": "MIT" - }, - "node_modules/core-js-compat": { - "version": "3.48.0", - "resolved": "https://registry.npmjs.org/core-js-compat/-/core-js-compat-3.48.0.tgz", - "integrity": "sha512-OM4cAF3D6VtH/WkLtWvyNC56EZVXsZdU3iqaMG2B4WvYrlqU831pc4UtG5yp0sE9z8Y02wVN7PjW5Zf9Gt0f1Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "browserslist": "^4.28.1" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/core-js" - } - }, - "node_modules/cross-spawn": { - "version": "7.0.6", - "resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.6.tgz", - "integrity": "sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA==", - "license": "MIT", - "dependencies": { - "path-key": "^3.1.0", - "shebang-command": "^2.0.0", - "which": "^2.0.1" - }, - "engines": { - "node": ">= 8" - } - }, - "node_modules/crossws": { - "version": "0.3.5", - "resolved": "https://registry.npmjs.org/crossws/-/crossws-0.3.5.tgz", - "integrity": "sha512-ojKiDvcmByhwa8YYqbQI/hg7MEU0NC03+pSdEq4ZUnZR9xXpwk7E43SMNGkn+JxJGPFtNvQ48+vV2p+P1ml5PA==", - "dev": true, - "license": "MIT", - "dependencies": { - "uncrypto": "^0.1.3" - } - }, - "node_modules/css-select": { - "version": "5.2.2", - "resolved": "https://registry.npmjs.org/css-select/-/css-select-5.2.2.tgz", - "integrity": "sha512-TizTzUddG/xYLA3NXodFM0fSbNizXjOKhqiQQwvhlspadZokn1KDy0NZFS0wuEubIYAV5/c1/lAr0TaaFXEXzw==", - "dev": true, - "license": "BSD-2-Clause", - "dependencies": { - "boolbase": "^1.0.0", - "css-what": "^6.1.0", - "domhandler": "^5.0.2", - "domutils": "^3.0.1", - "nth-check": "^2.0.1" - }, - "funding": { - "url": "https://github.com/sponsors/fb55" - } - }, - "node_modules/css-selector-parser": { - "version": "3.3.0", - "resolved": "https://registry.npmjs.org/css-selector-parser/-/css-selector-parser-3.3.0.tgz", - "integrity": "sha512-Y2asgMGFqJKF4fq4xHDSlFYIkeVfRsm69lQC1q9kbEsH5XtnINTMrweLkjYMeaUgiXBy/uvKeO/a1JHTNnmB2g==", - "funding": [ - { - "type": "github", - "url": "https://github.com/sponsors/mdevils" - }, - { - "type": "patreon", - "url": "https://patreon.com/mdevils" - } - ], - "license": "MIT" - }, - "node_modules/css-tree": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/css-tree/-/css-tree-3.1.0.tgz", - "integrity": "sha512-0eW44TGN5SQXU1mWSkKwFstI/22X2bG1nYzZTYMAWjylYURhse752YgbE4Cx46AC+bAvI+/dYTPRk1LqSUnu6w==", - "dev": true, - "license": "MIT", - "dependencies": { - "mdn-data": "2.12.2", - "source-map-js": "^1.0.1" - }, - "engines": { - "node": "^10 || ^12.20.0 || ^14.13.0 || >=15.0.0" - } - }, - "node_modules/css-what": { - "version": "6.2.2", - "resolved": "https://registry.npmjs.org/css-what/-/css-what-6.2.2.tgz", - "integrity": "sha512-u/O3vwbptzhMs3L1fQE82ZSLHQQfto5gyZzwteVIEyeaY5Fc7R4dapF/BvRoSYFeqfBk4m0V1Vafq5Pjv25wvA==", - "dev": true, - "license": "BSD-2-Clause", - "engines": { - "node": ">= 6" - }, - "funding": { - "url": "https://github.com/sponsors/fb55" - } - }, - "node_modules/cssesc": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/cssesc/-/cssesc-3.0.0.tgz", - "integrity": "sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==", - "dev": true, - "license": "MIT", - "bin": { - "cssesc": "bin/cssesc" - }, - "engines": { - "node": ">=4" - } - }, - "node_modules/csso": { - "version": "5.0.5", - "resolved": "https://registry.npmjs.org/csso/-/csso-5.0.5.tgz", - "integrity": "sha512-0LrrStPOdJj+SPCCrGhzryycLjwcgUSHBtxNA8aIDxf0GLsRh1cKYhB00Gd1lDOS4yGH69+SNn13+TWbVHETFQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "css-tree": "~2.2.0" - }, - "engines": { - "node": "^10 || ^12.20.0 || ^14.13.0 || >=15.0.0", - "npm": ">=7.0.0" - } - }, - "node_modules/csso/node_modules/css-tree": { - "version": "2.2.1", - "resolved": "https://registry.npmjs.org/css-tree/-/css-tree-2.2.1.tgz", - "integrity": "sha512-OA0mILzGc1kCOCSJerOeqDxDQ4HOh+G8NbOJFOTgOCzpw7fCBubk0fEyxp8AgOL/jvLgYA/uV0cMbe43ElF1JA==", - "dev": true, - "license": "MIT", - "dependencies": { - "mdn-data": "2.0.28", - "source-map-js": "^1.0.1" - }, - "engines": { - "node": "^10 || ^12.20.0 || ^14.13.0 || >=15.0.0", - "npm": ">=7.0.0" - } - }, - "node_modules/csso/node_modules/mdn-data": { - "version": "2.0.28", - "resolved": "https://registry.npmjs.org/mdn-data/-/mdn-data-2.0.28.tgz", - "integrity": "sha512-aylIc7Z9y4yzHYAJNuESG3hfhC+0Ibp/MAMiaOZgNv4pmEdFyfZhhhny4MNiAfWdBQ1RQ2mfDWmM1x8SvGyp8g==", - "dev": true, - "license": "CC0-1.0" - }, - "node_modules/csv-parse": { - "version": "6.1.0", - "resolved": "https://registry.npmjs.org/csv-parse/-/csv-parse-6.1.0.tgz", - "integrity": "sha512-CEE+jwpgLn+MmtCpVcPtiCZpVtB6Z2OKPTr34pycYYoL7sxdOkXDdQ4lRiw6ioC0q6BLqhc6cKweCVvral8yhw==", - "license": "MIT" - }, - "node_modules/debug": { - "version": "4.4.3", - "resolved": "https://registry.npmjs.org/debug/-/debug-4.4.3.tgz", - "integrity": "sha512-RGwwWnwQvkVfavKVt22FGLw+xYSdzARwm0ru6DhTVA3umU5hZc28V3kO4stgYryrTlLpuvgI9GiijltAjNbcqA==", - "license": "MIT", - "dependencies": { - "ms": "^2.1.3" - }, - "engines": { - "node": ">=6.0" - }, - "peerDependenciesMeta": { - "supports-color": { - "optional": true - } - } - }, - "node_modules/decode-named-character-reference": { - "version": "1.3.0", - "resolved": "https://registry.npmjs.org/decode-named-character-reference/-/decode-named-character-reference-1.3.0.tgz", - "integrity": "sha512-GtpQYB283KrPp6nRw50q3U9/VfOutZOe103qlN7BPP6Ad27xYnOIWv4lPzo8HCAL+mMZofJ9KEy30fq6MfaK6Q==", - "license": "MIT", - "dependencies": { - "character-entities": "^2.0.0" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/dedent": { - "version": "1.7.1", - "resolved": "https://registry.npmjs.org/dedent/-/dedent-1.7.1.tgz", - "integrity": "sha512-9JmrhGZpOlEgOLdQgSm0zxFaYoQon408V1v49aqTWuXENVlnCuY9JBZcXZiCsZQWDjTm5Qf/nIvAy77mXDAjEg==", - "dev": true, - "license": "MIT", - "peerDependencies": { - "babel-plugin-macros": "^3.1.0" - }, - "peerDependenciesMeta": { - "babel-plugin-macros": { - "optional": true - } - } - }, - "node_modules/deep-is": { - "version": "0.1.4", - "resolved": "https://registry.npmjs.org/deep-is/-/deep-is-0.1.4.tgz", - "integrity": "sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/deepmerge": { - "version": "4.3.1", - "resolved": "https://registry.npmjs.org/deepmerge/-/deepmerge-4.3.1.tgz", - "integrity": "sha512-3sUqbMEc77XqpdNO7FRyRog+eW3ph+GYCbj+rK+uYyRMuwsVy0rMiVtPn+QJlKFvWP/1PYpapqYn0Me2knFn+A==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=0.10.0" - } - }, - "node_modules/defu": { - "version": "6.1.4", - "resolved": "https://registry.npmjs.org/defu/-/defu-6.1.4.tgz", - "integrity": "sha512-mEQCMmwJu317oSz8CwdIOdwf3xMif1ttiM8LTufzc3g6kR+9Pe236twL8j3IYT1F7GfRgGcW6MWxzZjLIkuHIg==", - "dev": true, - "license": "MIT" - }, - "node_modules/dequal": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/dequal/-/dequal-2.0.3.tgz", - "integrity": "sha512-0je+qPKHEMohvfRTCEo3CrPG6cAzAYgmzKyxRiYSSDkS6eGJdyVJm7WaYA5ECaAD9wLB2T4EEeymA5aFVcYXCA==", - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/destr": { - "version": "2.0.5", - "resolved": "https://registry.npmjs.org/destr/-/destr-2.0.5.tgz", - "integrity": "sha512-ugFTXCtDZunbzasqBxrK93Ik/DRYsO6S/fedkWEMKqt04xZ4csmnmwGDBAb07QWNaGMAmnTIemsYZCksjATwsA==", - "dev": true, - "license": "MIT" - }, - "node_modules/detect-indent": { - "version": "7.0.2", - "resolved": "https://registry.npmjs.org/detect-indent/-/detect-indent-7.0.2.tgz", - "integrity": "sha512-y+8xyqdGLL+6sh0tVeHcfP/QDd8gUgbasolJJpY7NgeQGSZ739bDtSiaiDgtoicy+mtYB81dKLxO9xRhCyIB3A==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12.20" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/detect-libc": { - "version": "2.1.2", - "resolved": "https://registry.npmjs.org/detect-libc/-/detect-libc-2.1.2.tgz", - "integrity": "sha512-Btj2BOOO83o3WyH59e8MgXsxEQVcarkUOpEYrubB0urwnN10yQ364rsiByU11nZlqWYZm05i/of7io4mzihBtQ==", - "dev": true, - "license": "Apache-2.0", - "engines": { - "node": ">=8" - } - }, - "node_modules/detect-newline": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/detect-newline/-/detect-newline-3.1.0.tgz", - "integrity": "sha512-TLz+x/vEXm/Y7P7wn1EJFNLxYpUD4TgMosxY6fAVJUnJMbupHBOncxyWUG9OpTaH9EBD7uFI5LfEgmMOc54DsA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/deterministic-object-hash": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/deterministic-object-hash/-/deterministic-object-hash-2.0.2.tgz", - "integrity": "sha512-KxektNH63SrbfUyDiwXqRb1rLwKt33AmMv+5Nhsw1kqZ13SJBRTgZHtGbE+hH3a1mVW1cz+4pqSWVPAtLVXTzQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "base-64": "^1.0.0" - }, - "engines": { - "node": ">=18" - } - }, - "node_modules/devalue": { - "version": "5.6.2", - "resolved": "https://registry.npmjs.org/devalue/-/devalue-5.6.2.tgz", - "integrity": "sha512-nPRkjWzzDQlsejL1WVifk5rvcFi/y1onBRxjaFMjZeR9mFpqu2gmAZ9xUB9/IEanEP/vBtGeGganC/GO1fmufg==", - "dev": true, - "license": "MIT" - }, - "node_modules/devlop": { - "version": "1.1.0", - "resolved": "https://registry.npmjs.org/devlop/-/devlop-1.1.0.tgz", - "integrity": "sha512-RWmIqhcFf1lRYBvNmr7qTNuyCt/7/ns2jbpp1+PalgE/rDQcBT0fioSMUpJ93irlUhC5hrg4cYqe6U+0ImW0rA==", - "license": "MIT", - "dependencies": { - "dequal": "^2.0.0" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/diff": { - "version": "8.0.3", - "resolved": "https://registry.npmjs.org/diff/-/diff-8.0.3.tgz", - "integrity": "sha512-qejHi7bcSD4hQAZE0tNAawRK1ZtafHDmMTMkrrIGgSLl7hTnQHmKCeB45xAcbfTqK2zowkM3j3bHt/4b/ARbYQ==", - "dev": true, - "license": "BSD-3-Clause", - "engines": { - "node": ">=0.3.1" - } - }, - "node_modules/diff-sequences": { - "version": "27.5.1", - "resolved": "https://registry.npmjs.org/diff-sequences/-/diff-sequences-27.5.1.tgz", - "integrity": "sha512-k1gCAXAsNgLwEL+Y8Wvl+M6oEFj5bgazfZULpS5CneoPPXRaCCW7dm+q21Ky2VEE5X+VeRDBVg1Pcvvsr4TtNQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0" - } - }, - "node_modules/dir-glob": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/dir-glob/-/dir-glob-3.0.1.tgz", - "integrity": "sha512-WkrWp9GR4KXfKGYzOLmTuGVi1UWFfws377n9cc55/tb6DuqyF6pcQ5AbiHEshaDpY9v6oaSr2XCDidGmMwdzIA==", - "dev": true, - "license": "MIT", - "dependencies": { - "path-type": "^4.0.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/dir-glob/node_modules/path-type": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/path-type/-/path-type-4.0.0.tgz", - "integrity": "sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/direction": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/direction/-/direction-2.0.1.tgz", - "integrity": "sha512-9S6m9Sukh1cZNknO1CWAr2QAWsbKLafQiyM5gZ7VgXHeuaoUwffKN4q6NC4A/Mf9iiPlOXQEKW/Mv/mh9/3YFA==", - "dev": true, - "license": "MIT", - "bin": { - "direction": "cli.js" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/dlv": { - "version": "1.1.3", - "resolved": "https://registry.npmjs.org/dlv/-/dlv-1.1.3.tgz", - "integrity": "sha512-+HlytyjlPKnIG8XuRG8WvmBP8xs8P71y+SKKS6ZXWoEgLuePxtDoUEiH7WkdePWrQ5JBpE6aoVqfZfJUQkjXwA==", - "dev": true, - "license": "MIT" - }, - "node_modules/dom-serializer": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-2.0.0.tgz", - "integrity": "sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==", - "dev": true, - "license": "MIT", - "dependencies": { - "domelementtype": "^2.3.0", - "domhandler": "^5.0.2", - "entities": "^4.2.0" - }, - "funding": { - "url": "https://github.com/cheeriojs/dom-serializer?sponsor=1" - } - }, - "node_modules/domelementtype": { - "version": "2.3.0", - "resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.3.0.tgz", - "integrity": "sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==", - "dev": true, - "funding": [ - { - "type": "github", - "url": "https://github.com/sponsors/fb55" - } - ], - "license": "BSD-2-Clause" - }, - "node_modules/domhandler": { - "version": "5.0.3", - "resolved": "https://registry.npmjs.org/domhandler/-/domhandler-5.0.3.tgz", - "integrity": "sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==", - "dev": true, - "license": "BSD-2-Clause", - "dependencies": { - "domelementtype": "^2.3.0" - }, - "engines": { - "node": ">= 4" - }, - "funding": { - "url": "https://github.com/fb55/domhandler?sponsor=1" - } - }, - "node_modules/domutils": { - "version": "3.2.2", - "resolved": "https://registry.npmjs.org/domutils/-/domutils-3.2.2.tgz", - "integrity": "sha512-6kZKyUajlDuqlHKVX1w7gyslj9MPIXzIFiz/rGu35uC1wMi+kMhQwGhl4lt9unC9Vb9INnY9Z3/ZA3+FhASLaw==", - "dev": true, - "license": "BSD-2-Clause", - "dependencies": { - "dom-serializer": "^2.0.0", - "domelementtype": "^2.3.0", - "domhandler": "^5.0.3" - }, - "funding": { - "url": "https://github.com/fb55/domutils?sponsor=1" - } - }, - "node_modules/dset": { - "version": "3.1.4", - "resolved": "https://registry.npmjs.org/dset/-/dset-3.1.4.tgz", - "integrity": "sha512-2QF/g9/zTaPDc3BjNcVTGoBbXBgYfMTTceLaYcFJ/W9kggFUkhxD/hMEeuLKbugyef9SqAx8cpgwlIP/jinUTA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=4" - } - }, - "node_modules/eastasianwidth": { - "version": "0.2.0", - "resolved": "https://registry.npmjs.org/eastasianwidth/-/eastasianwidth-0.2.0.tgz", - "integrity": "sha512-I88TYZWc9XiYHRQ4/3c5rjjfgkjhLyW2luGIheGERbNQ6OY7yTybanSpDXZa8y7VUP9YmDcYa+eyq4ca7iLqWA==", - "license": "MIT" - }, - "node_modules/electron-to-chromium": { - "version": "1.5.283", - "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.5.283.tgz", - "integrity": "sha512-3vifjt1HgrGW/h76UEeny+adYApveS9dH2h3p57JYzBSXJIKUJAvtmIytDKjcSCt9xHfrNCFJ7gts6vkhuq++w==", - "dev": true, - "license": "ISC" - }, - "node_modules/emittery": { - "version": "0.13.1", - "resolved": "https://registry.npmjs.org/emittery/-/emittery-0.13.1.tgz", - "integrity": "sha512-DeWwawk6r5yR9jFgnDKYt4sLS0LmHJJi3ZOnb5/JdbYwj3nW+FxQnHIjhBKz8YLC7oRNPVM9NQ47I3CVx34eqQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/sindresorhus/emittery?sponsor=1" - } - }, - "node_modules/emoji-regex": { - "version": "8.0.0", - "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-8.0.0.tgz", - "integrity": "sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==", - "license": "MIT" - }, - "node_modules/enhanced-resolve": { - "version": "5.18.4", - "resolved": "https://registry.npmjs.org/enhanced-resolve/-/enhanced-resolve-5.18.4.tgz", - "integrity": "sha512-LgQMM4WXU3QI+SYgEc2liRgznaD5ojbmY3sb8LxyguVkIg5FxdpTkvk72te2R38/TGKxH634oLxXRGY6d7AP+Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "graceful-fs": "^4.2.4", - "tapable": "^2.2.0" - }, - "engines": { - "node": ">=10.13.0" - } - }, - "node_modules/entities": { - "version": "4.5.0", - "resolved": "https://registry.npmjs.org/entities/-/entities-4.5.0.tgz", - "integrity": "sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==", - "dev": true, - "license": "BSD-2-Clause", - "engines": { - "node": ">=0.12" - }, - "funding": { - "url": "https://github.com/fb55/entities?sponsor=1" - } - }, - "node_modules/environment": { - "version": "1.1.0", - "resolved": "https://registry.npmjs.org/environment/-/environment-1.1.0.tgz", - "integrity": "sha512-xUtoPkMggbz0MPyPiIWr1Kp4aeWJjDZ6SMvURhimjdZgsRuDplF5/s9hcgGhyXMhs+6vpnuoiZ2kFiu3FMnS8Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/error-ex": { - "version": "1.3.4", - "resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.4.tgz", - "integrity": "sha512-sqQamAnR14VgCr1A618A3sGrygcpK+HEbenA/HiEAkkUwcZIIB/tgWqHFxWgOyDh4nB4JCRimh79dR5Ywc9MDQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "is-arrayish": "^0.2.1" - } - }, - "node_modules/es-module-lexer": { - "version": "1.7.0", - "resolved": "https://registry.npmjs.org/es-module-lexer/-/es-module-lexer-1.7.0.tgz", - "integrity": "sha512-jEQoCwk8hyb2AZziIOLhDqpm5+2ww5uIE6lkO/6jcOCusfk6LhMHpXXfBLXTZ7Ydyt0j4VoUQv6uGNYbdW+kBA==", - "dev": true, - "license": "MIT" - }, - "node_modules/esast-util-from-estree": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/esast-util-from-estree/-/esast-util-from-estree-2.0.0.tgz", - "integrity": "sha512-4CyanoAudUSBAn5K13H4JhsMH6L9ZP7XbLVe/dKybkxMO7eDyLsT8UHl9TRNrU2Gr9nz+FovfSIjuXWJ81uVwQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree-jsx": "^1.0.0", - "devlop": "^1.0.0", - "estree-util-visit": "^2.0.0", - "unist-util-position-from-estree": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/esast-util-from-js": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/esast-util-from-js/-/esast-util-from-js-2.0.1.tgz", - "integrity": "sha512-8Ja+rNJ0Lt56Pcf3TAmpBZjmx8ZcK5Ts4cAzIOjsjevg9oSXJnl6SUQ2EevU8tv3h6ZLWmoKL5H4fgWvdvfETw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree-jsx": "^1.0.0", - "acorn": "^8.0.0", - "esast-util-from-estree": "^2.0.0", - "vfile-message": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/esbuild": { - "version": "0.25.12", - "resolved": "https://registry.npmjs.org/esbuild/-/esbuild-0.25.12.tgz", - "integrity": "sha512-bbPBYYrtZbkt6Os6FiTLCTFxvq4tt3JKall1vRwshA3fdVztsLAatFaZobhkBC8/BrPetoa0oksYoKXoG4ryJg==", - "dev": true, - "hasInstallScript": true, - "license": "MIT", - "bin": { - "esbuild": "bin/esbuild" - }, - "engines": { - "node": ">=18" - }, - "optionalDependencies": { - "@esbuild/aix-ppc64": "0.25.12", - "@esbuild/android-arm": "0.25.12", - "@esbuild/android-arm64": "0.25.12", - "@esbuild/android-x64": "0.25.12", - "@esbuild/darwin-arm64": "0.25.12", - "@esbuild/darwin-x64": "0.25.12", - "@esbuild/freebsd-arm64": "0.25.12", - "@esbuild/freebsd-x64": "0.25.12", - "@esbuild/linux-arm": "0.25.12", - "@esbuild/linux-arm64": "0.25.12", - "@esbuild/linux-ia32": "0.25.12", - "@esbuild/linux-loong64": "0.25.12", - "@esbuild/linux-mips64el": "0.25.12", - "@esbuild/linux-ppc64": "0.25.12", - "@esbuild/linux-riscv64": "0.25.12", - "@esbuild/linux-s390x": "0.25.12", - "@esbuild/linux-x64": "0.25.12", - "@esbuild/netbsd-arm64": "0.25.12", - "@esbuild/netbsd-x64": "0.25.12", - "@esbuild/openbsd-arm64": "0.25.12", - "@esbuild/openbsd-x64": "0.25.12", - "@esbuild/openharmony-arm64": "0.25.12", - "@esbuild/sunos-x64": "0.25.12", - "@esbuild/win32-arm64": "0.25.12", - "@esbuild/win32-ia32": "0.25.12", - "@esbuild/win32-x64": "0.25.12" - } - }, - "node_modules/escalade": { - "version": "3.2.0", - "resolved": "https://registry.npmjs.org/escalade/-/escalade-3.2.0.tgz", - "integrity": "sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/escape-string-regexp": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz", - "integrity": "sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/eslint": { - "version": "9.39.2", - "resolved": "https://registry.npmjs.org/eslint/-/eslint-9.39.2.tgz", - "integrity": "sha512-LEyamqS7W5HB3ujJyvi0HQK/dtVINZvd5mAAp9eT5S/ujByGjiZLCzPcHVzuXbpJDJF/cxwHlfceVUDZ2lnSTw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@eslint-community/eslint-utils": "^4.8.0", - "@eslint-community/regexpp": "^4.12.1", - "@eslint/config-array": "^0.21.1", - "@eslint/config-helpers": "^0.4.2", - "@eslint/core": "^0.17.0", - "@eslint/eslintrc": "^3.3.1", - "@eslint/js": "9.39.2", - "@eslint/plugin-kit": "^0.4.1", - "@humanfs/node": "^0.16.6", - "@humanwhocodes/module-importer": "^1.0.1", - "@humanwhocodes/retry": "^0.4.2", - "@types/estree": "^1.0.6", - "ajv": "^6.12.4", - "chalk": "^4.0.0", - "cross-spawn": "^7.0.6", - "debug": "^4.3.2", - "escape-string-regexp": "^4.0.0", - "eslint-scope": "^8.4.0", - "eslint-visitor-keys": "^4.2.1", - "espree": "^10.4.0", - "esquery": "^1.5.0", - "esutils": "^2.0.2", - "fast-deep-equal": "^3.1.3", - "file-entry-cache": "^8.0.0", - "find-up": "^5.0.0", - "glob-parent": "^6.0.2", - "ignore": "^5.2.0", - "imurmurhash": "^0.1.4", - "is-glob": "^4.0.0", - "json-stable-stringify-without-jsonify": "^1.0.1", - "lodash.merge": "^4.6.2", - "minimatch": "^3.1.2", - "natural-compare": "^1.4.0", - "optionator": "^0.9.3" - }, - "bin": { - "eslint": "bin/eslint.js" - }, - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - }, - "funding": { - "url": "https://eslint.org/donate" - }, - "peerDependencies": { - "jiti": "*" - }, - "peerDependenciesMeta": { - "jiti": { - "optional": true - } - } - }, - "node_modules/eslint-compat-utils": { - "version": "0.5.1", - "resolved": "https://registry.npmjs.org/eslint-compat-utils/-/eslint-compat-utils-0.5.1.tgz", - "integrity": "sha512-3z3vFexKIEnjHE3zCMRo6fn/e44U7T1khUjg+Hp0ZQMCigh28rALD0nPFBcGZuiLC5rLZa2ubQHDRln09JfU2Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "semver": "^7.5.4" - }, - "engines": { - "node": ">=12" - }, - "peerDependencies": { - "eslint": ">=6.0.0" - } - }, - "node_modules/eslint-config-prettier": { - "version": "10.1.8", - "resolved": "https://registry.npmjs.org/eslint-config-prettier/-/eslint-config-prettier-10.1.8.tgz", - "integrity": "sha512-82GZUjRS0p/jganf6q1rEO25VSoHH0hKPCTrgillPjdI/3bgBhAE1QzHrHTizjpRvy6pGAvKjDJtk2pF9NDq8w==", - "dev": true, - "license": "MIT", - "bin": { - "eslint-config-prettier": "bin/cli.js" - }, - "funding": { - "url": "https://opencollective.com/eslint-config-prettier" - }, - "peerDependencies": { - "eslint": ">=7.0.0" - } - }, - "node_modules/eslint-plugin-es-x": { - "version": "7.8.0", - "resolved": "https://registry.npmjs.org/eslint-plugin-es-x/-/eslint-plugin-es-x-7.8.0.tgz", - "integrity": "sha512-7Ds8+wAAoV3T+LAKeu39Y5BzXCrGKrcISfgKEqTS4BDN8SFEDQd0S43jiQ8vIa3wUKD07qitZdfzlenSi8/0qQ==", - "dev": true, - "funding": [ - "https://github.com/sponsors/ota-meshi", - "https://opencollective.com/eslint" - ], - "license": "MIT", - "dependencies": { - "@eslint-community/eslint-utils": "^4.1.2", - "@eslint-community/regexpp": "^4.11.0", - "eslint-compat-utils": "^0.5.1" - }, - "engines": { - "node": "^14.18.0 || >=16.0.0" - }, - "peerDependencies": { - "eslint": ">=8" - } - }, - "node_modules/eslint-plugin-n": { - "version": "17.23.2", - "resolved": "https://registry.npmjs.org/eslint-plugin-n/-/eslint-plugin-n-17.23.2.tgz", - "integrity": "sha512-RhWBeb7YVPmNa2eggvJooiuehdL76/bbfj/OJewyoGT80qn5PXdz8zMOTO6YHOsI7byPt7+Ighh/i/4a5/v7hw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@eslint-community/eslint-utils": "^4.5.0", - "enhanced-resolve": "^5.17.1", - "eslint-plugin-es-x": "^7.8.0", - "get-tsconfig": "^4.8.1", - "globals": "^15.11.0", - "globrex": "^0.1.2", - "ignore": "^5.3.2", - "semver": "^7.6.3", - "ts-declaration-location": "^1.0.6" - }, - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - }, - "funding": { - "url": "https://opencollective.com/eslint" - }, - "peerDependencies": { - "eslint": ">=8.23.0" - } - }, - "node_modules/eslint-plugin-n/node_modules/globals": { - "version": "15.15.0", - "resolved": "https://registry.npmjs.org/globals/-/globals-15.15.0.tgz", - "integrity": "sha512-7ACyT3wmyp3I61S4fG682L0VA2RGD9otkqGJIwNUMF1SWUombIIk+af1unuDYgMm082aHYwD+mzJvv9Iu8dsgg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/eslint-plugin-n/node_modules/ignore": { - "version": "5.3.2", - "resolved": "https://registry.npmjs.org/ignore/-/ignore-5.3.2.tgz", - "integrity": "sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 4" - } - }, - "node_modules/eslint-plugin-unicorn": { - "version": "60.0.0", - "resolved": "https://registry.npmjs.org/eslint-plugin-unicorn/-/eslint-plugin-unicorn-60.0.0.tgz", - "integrity": "sha512-QUzTefvP8stfSXsqKQ+vBQSEsXIlAiCduS/V1Em+FKgL9c21U/IIm20/e3MFy1jyCf14tHAhqC1sX8OTy6VUCg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/helper-validator-identifier": "^7.27.1", - "@eslint-community/eslint-utils": "^4.7.0", - "@eslint/plugin-kit": "^0.3.3", - "change-case": "^5.4.4", - "ci-info": "^4.3.0", - "clean-regexp": "^1.0.0", - "core-js-compat": "^3.44.0", - "esquery": "^1.6.0", - "find-up-simple": "^1.0.1", - "globals": "^16.3.0", - "indent-string": "^5.0.0", - "is-builtin-module": "^5.0.0", - "jsesc": "^3.1.0", - "pluralize": "^8.0.0", - "regexp-tree": "^0.1.27", - "regjsparser": "^0.12.0", - "semver": "^7.7.2", - "strip-indent": "^4.0.0" - }, - "engines": { - "node": "^20.10.0 || >=21.0.0" - }, - "funding": { - "url": "https://github.com/sindresorhus/eslint-plugin-unicorn?sponsor=1" - }, - "peerDependencies": { - "eslint": ">=9.29.0" - } - }, - "node_modules/eslint-plugin-unicorn/node_modules/@eslint/core": { - "version": "0.15.2", - "resolved": "https://registry.npmjs.org/@eslint/core/-/core-0.15.2.tgz", - "integrity": "sha512-78Md3/Rrxh83gCxoUc0EiciuOHsIITzLy53m3d9UyiW8y9Dj2D29FeETqyKA+BRK76tnTp6RXWb3pCay8Oyomg==", - "dev": true, - "license": "Apache-2.0", - "dependencies": { - "@types/json-schema": "^7.0.15" - }, - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - } - }, - "node_modules/eslint-plugin-unicorn/node_modules/@eslint/plugin-kit": { - "version": "0.3.5", - "resolved": "https://registry.npmjs.org/@eslint/plugin-kit/-/plugin-kit-0.3.5.tgz", - "integrity": "sha512-Z5kJ+wU3oA7MMIqVR9tyZRtjYPr4OC004Q4Rw7pgOKUOKkJfZ3O24nz3WYfGRpMDNmcOi3TwQOmgm7B7Tpii0w==", - "dev": true, - "license": "Apache-2.0", - "dependencies": { - "@eslint/core": "^0.15.2", - "levn": "^0.4.1" - }, - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - } - }, - "node_modules/eslint-plugin-unicorn/node_modules/globals": { - "version": "16.5.0", - "resolved": "https://registry.npmjs.org/globals/-/globals-16.5.0.tgz", - "integrity": "sha512-c/c15i26VrJ4IRt5Z89DnIzCGDn9EcebibhAOjw5ibqEHsE1wLUgkPn9RDmNcUKyU87GeaL633nyJ+pplFR2ZQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/eslint-plugin-yml": { - "version": "1.19.1", - "resolved": "https://registry.npmjs.org/eslint-plugin-yml/-/eslint-plugin-yml-1.19.1.tgz", - "integrity": "sha512-bYkOxyEiXh9WxUhVYPELdSHxGG5pOjCSeJOVkfdIyj6tuiHDxrES2WAW1dBxn3iaZQey57XflwLtCYRcNPOiOg==", - "dev": true, - "license": "MIT", - "dependencies": { - "debug": "^4.3.2", - "diff-sequences": "^27.5.1", - "escape-string-regexp": "4.0.0", - "eslint-compat-utils": "^0.6.0", - "natural-compare": "^1.4.0", - "yaml-eslint-parser": "^1.2.1" - }, - "engines": { - "node": "^14.17.0 || >=16.0.0" - }, - "funding": { - "url": "https://github.com/sponsors/ota-meshi" - }, - "peerDependencies": { - "eslint": ">=6.0.0" - } - }, - "node_modules/eslint-plugin-yml/node_modules/eslint-compat-utils": { - "version": "0.6.5", - "resolved": "https://registry.npmjs.org/eslint-compat-utils/-/eslint-compat-utils-0.6.5.tgz", - "integrity": "sha512-vAUHYzue4YAa2hNACjB8HvUQj5yehAZgiClyFVVom9cP8z5NSFq3PwB/TtJslN2zAMgRX6FCFCjYBbQh71g5RQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "semver": "^7.5.4" - }, - "engines": { - "node": ">=12" - }, - "peerDependencies": { - "eslint": ">=6.0.0" - } - }, - "node_modules/eslint-scope": { - "version": "8.4.0", - "resolved": "https://registry.npmjs.org/eslint-scope/-/eslint-scope-8.4.0.tgz", - "integrity": "sha512-sNXOfKCn74rt8RICKMvJS7XKV/Xk9kA7DyJr8mJik3S7Cwgy3qlkkmyS2uQB3jiJg6VNdZd/pDBJu0nvG2NlTg==", - "dev": true, - "license": "BSD-2-Clause", - "dependencies": { - "esrecurse": "^4.3.0", - "estraverse": "^5.2.0" - }, - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - }, - "funding": { - "url": "https://opencollective.com/eslint" - } - }, - "node_modules/eslint-visitor-keys": { - "version": "4.2.1", - "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-4.2.1.tgz", - "integrity": "sha512-Uhdk5sfqcee/9H/rCOJikYz67o0a2Tw2hGRPOG2Y1R2dg7brRe1uG0yaNQDHu+TO/uQPF/5eCapvYSmHUjt7JQ==", - "dev": true, - "license": "Apache-2.0", - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - }, - "funding": { - "url": "https://opencollective.com/eslint" - } - }, - "node_modules/eslint/node_modules/ignore": { - "version": "5.3.2", - "resolved": "https://registry.npmjs.org/ignore/-/ignore-5.3.2.tgz", - "integrity": "sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 4" - } - }, - "node_modules/espree": { - "version": "10.4.0", - "resolved": "https://registry.npmjs.org/espree/-/espree-10.4.0.tgz", - "integrity": "sha512-j6PAQ2uUr79PZhBjP5C5fhl8e39FmRnOjsD5lGnWrFU8i2G776tBK7+nP8KuQUTTyAZUwfQqXAgrVH5MbH9CYQ==", - "dev": true, - "license": "BSD-2-Clause", - "dependencies": { - "acorn": "^8.15.0", - "acorn-jsx": "^5.3.2", - "eslint-visitor-keys": "^4.2.1" - }, - "engines": { - "node": "^18.18.0 || ^20.9.0 || >=21.1.0" - }, - "funding": { - "url": "https://opencollective.com/eslint" - } - }, - "node_modules/esprima": { - "version": "4.0.1", - "resolved": "https://registry.npmjs.org/esprima/-/esprima-4.0.1.tgz", - "integrity": "sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==", - "dev": true, - "license": "BSD-2-Clause", - "bin": { - "esparse": "bin/esparse.js", - "esvalidate": "bin/esvalidate.js" - }, - "engines": { - "node": ">=4" - } - }, - "node_modules/esquery": { - "version": "1.7.0", - "resolved": "https://registry.npmjs.org/esquery/-/esquery-1.7.0.tgz", - "integrity": "sha512-Ap6G0WQwcU/LHsvLwON1fAQX9Zp0A2Y6Y/cJBl9r/JbW90Zyg4/zbG6zzKa2OTALELarYHmKu0GhpM5EO+7T0g==", - "dev": true, - "license": "BSD-3-Clause", - "dependencies": { - "estraverse": "^5.1.0" - }, - "engines": { - "node": ">=0.10" - } - }, - "node_modules/esrecurse": { - "version": "4.3.0", - "resolved": "https://registry.npmjs.org/esrecurse/-/esrecurse-4.3.0.tgz", - "integrity": "sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==", - "dev": true, - "license": "BSD-2-Clause", - "dependencies": { - "estraverse": "^5.2.0" - }, - "engines": { - "node": ">=4.0" - } - }, - "node_modules/estraverse": { - "version": "5.3.0", - "resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz", - "integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==", - "dev": true, - "license": "BSD-2-Clause", - "engines": { - "node": ">=4.0" - } - }, - "node_modules/estree-util-attach-comments": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/estree-util-attach-comments/-/estree-util-attach-comments-3.0.0.tgz", - "integrity": "sha512-cKUwm/HUcTDsYh/9FgnuFqpfquUbwIqwKM26BVCGDPVgvaCl/nDCCjUfiLlx6lsEZ3Z4RFxNbOQ60pkaEwFxGw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/estree-util-build-jsx": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/estree-util-build-jsx/-/estree-util-build-jsx-3.0.1.tgz", - "integrity": "sha512-8U5eiL6BTrPxp/CHbs2yMgP8ftMhR5ww1eIKoWRMlqvltHF8fZn5LRDvTKuxD3DUn+shRbLGqXemcP51oFCsGQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree-jsx": "^1.0.0", - "devlop": "^1.0.0", - "estree-util-is-identifier-name": "^3.0.0", - "estree-walker": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/estree-util-is-identifier-name": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/estree-util-is-identifier-name/-/estree-util-is-identifier-name-3.0.0.tgz", - "integrity": "sha512-hFtqIDZTIUZ9BXLb8y4pYGyk6+wekIivNVTcmvk8NoOh+VeRn5y6cEHzbURrWbfp1fIqdVipilzj+lfaadNZmg==", - "dev": true, - "license": "MIT", - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/estree-util-scope": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/estree-util-scope/-/estree-util-scope-1.0.0.tgz", - "integrity": "sha512-2CAASclonf+JFWBNJPndcOpA8EMJwa0Q8LUFJEKqXLW6+qBvbFZuF5gItbQOs/umBUkjviCSDCbBwU2cXbmrhQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "devlop": "^1.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/estree-util-to-js": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/estree-util-to-js/-/estree-util-to-js-2.0.0.tgz", - "integrity": "sha512-WDF+xj5rRWmD5tj6bIqRi6CkLIXbbNQUcxQHzGysQzvHmdYG2G7p/Tf0J0gpxGgkeMZNTIjT/AoSvC9Xehcgdg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree-jsx": "^1.0.0", - "astring": "^1.8.0", - "source-map": "^0.7.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/estree-util-visit": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/estree-util-visit/-/estree-util-visit-2.0.0.tgz", - "integrity": "sha512-m5KgiH85xAhhW8Wta0vShLcUvOsh3LLPI2YVwcbio1l7E09NTLL1EyMZFM1OyWowoH0skScNbhOPl4kcBgzTww==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree-jsx": "^1.0.0", - "@types/unist": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/estree-walker": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/estree-walker/-/estree-walker-3.0.3.tgz", - "integrity": "sha512-7RUKfXgSMMkzt6ZuXmqapOurLGPPfgj6l9uRZ7lRGolvk0y2yocc35LdcxKC5PQZdn2DMqioAQ2NoWcrTKmm6g==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0" - } - }, - "node_modules/esutils": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.3.tgz", - "integrity": "sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==", - "dev": true, - "license": "BSD-2-Clause", - "engines": { - "node": ">=0.10.0" - } - }, - "node_modules/eventemitter3": { - "version": "5.0.4", - "resolved": "https://registry.npmjs.org/eventemitter3/-/eventemitter3-5.0.4.tgz", - "integrity": "sha512-mlsTRyGaPBjPedk6Bvw+aqbsXDtoAyAzm5MO7JgU+yVRyMQ5O8bD4Kcci7BS85f93veegeCPkL8R4GLClnjLFw==", - "dev": true, - "license": "MIT" - }, - "node_modules/execa": { - "version": "5.1.1", - "resolved": "https://registry.npmjs.org/execa/-/execa-5.1.1.tgz", - "integrity": "sha512-8uSpZZocAZRBAPIEINJj3Lo9HyGitllczc27Eh5YYojjMFMn8yHMDMaUHE2Jqfq05D/wucwI4JGURyXt1vchyg==", - "dev": true, - "license": "MIT", - "dependencies": { - "cross-spawn": "^7.0.3", - "get-stream": "^6.0.0", - "human-signals": "^2.1.0", - "is-stream": "^2.0.0", - "merge-stream": "^2.0.0", - "npm-run-path": "^4.0.1", - "onetime": "^5.1.2", - "signal-exit": "^3.0.3", - "strip-final-newline": "^2.0.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sindresorhus/execa?sponsor=1" - } - }, - "node_modules/execa/node_modules/signal-exit": { - "version": "3.0.7", - "resolved": "https://registry.npmjs.org/signal-exit/-/signal-exit-3.0.7.tgz", - "integrity": "sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==", - "dev": true, - "license": "ISC" - }, - "node_modules/exit-x": { - "version": "0.2.2", - "resolved": "https://registry.npmjs.org/exit-x/-/exit-x-0.2.2.tgz", - "integrity": "sha512-+I6B/IkJc1o/2tiURyz/ivu/O0nKNEArIUB5O7zBrlDVJr22SCLH3xTeEry428LvFhRzIA1g8izguxJ/gbNcVQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/expect": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/expect/-/expect-30.2.0.tgz", - "integrity": "sha512-u/feCi0GPsI+988gU2FLcsHyAHTU0MX1Wg68NhAnN7z/+C5wqG+CY8J53N9ioe8RXgaoz0nBR/TYMf3AycUuPw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/expect-utils": "30.2.0", - "@jest/get-type": "30.1.0", - "jest-matcher-utils": "30.2.0", - "jest-message-util": "30.2.0", - "jest-mock": "30.2.0", - "jest-util": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/expressive-code": { - "version": "0.41.6", - "resolved": "https://registry.npmjs.org/expressive-code/-/expressive-code-0.41.6.tgz", - "integrity": "sha512-W/5+IQbrpCIM5KGLjO35wlp1NCwDOOVQb+PAvzEoGkW1xjGM807ZGfBKptNWH6UECvt6qgmLyWolCMYKh7eQmA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@expressive-code/core": "^0.41.6", - "@expressive-code/plugin-frames": "^0.41.6", - "@expressive-code/plugin-shiki": "^0.41.6", - "@expressive-code/plugin-text-markers": "^0.41.6" - } - }, - "node_modules/extend": { - "version": "3.0.2", - "resolved": "https://registry.npmjs.org/extend/-/extend-3.0.2.tgz", - "integrity": "sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==", - "license": "MIT" - }, - "node_modules/fast-deep-equal": { - "version": "3.1.3", - "resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz", - "integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==", - "dev": true, - "license": "MIT" - }, - "node_modules/fast-glob": { - "version": "3.3.3", - "resolved": "https://registry.npmjs.org/fast-glob/-/fast-glob-3.3.3.tgz", - "integrity": "sha512-7MptL8U0cqcFdzIzwOTHoilX9x5BrNqye7Z/LuC7kCMRio1EMSyqRK3BEAUD7sXRq4iT4AzTVuZdhgQ2TCvYLg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@nodelib/fs.stat": "^2.0.2", - "@nodelib/fs.walk": "^1.2.3", - "glob-parent": "^5.1.2", - "merge2": "^1.3.0", - "micromatch": "^4.0.8" - }, - "engines": { - "node": ">=8.6.0" - } - }, - "node_modules/fast-glob/node_modules/glob-parent": { - "version": "5.1.2", - "resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz", - "integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==", - "dev": true, - "license": "ISC", - "dependencies": { - "is-glob": "^4.0.1" - }, - "engines": { - "node": ">= 6" - } - }, - "node_modules/fast-json-stable-stringify": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz", - "integrity": "sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==", - "dev": true, - "license": "MIT" - }, - "node_modules/fast-levenshtein": { - "version": "2.0.6", - "resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz", - "integrity": "sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==", - "dev": true, - "license": "MIT" - }, - "node_modules/fastq": { - "version": "1.20.1", - "resolved": "https://registry.npmjs.org/fastq/-/fastq-1.20.1.tgz", - "integrity": "sha512-GGToxJ/w1x32s/D2EKND7kTil4n8OVk/9mycTc4VDza13lOvpUZTGX3mFSCtV9ksdGBVzvsyAVLM6mHFThxXxw==", - "dev": true, - "license": "ISC", - "dependencies": { - "reusify": "^1.0.4" - } - }, - "node_modules/fb-watchman": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/fb-watchman/-/fb-watchman-2.0.2.tgz", - "integrity": "sha512-p5161BqbuCaSnB8jIbzQHOlpgsPmK5rJVDfDKO91Axs5NC1uu3HRQm6wt9cd9/+GtQQIO53JdGXXoyDpTAsgYA==", - "dev": true, - "license": "Apache-2.0", - "dependencies": { - "bser": "2.1.1" - } - }, - "node_modules/fdir": { - "version": "6.5.0", - "resolved": "https://registry.npmjs.org/fdir/-/fdir-6.5.0.tgz", - "integrity": "sha512-tIbYtZbucOs0BRGqPJkshJUYdL+SDH7dVM8gjy+ERp3WAUjLEFJE+02kanyHtwjWOnwrKYBiwAmM0p4kLJAnXg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12.0.0" - }, - "peerDependencies": { - "picomatch": "^3 || ^4" - }, - "peerDependenciesMeta": { - "picomatch": { - "optional": true - } - } - }, - "node_modules/file-entry-cache": { - "version": "8.0.0", - "resolved": "https://registry.npmjs.org/file-entry-cache/-/file-entry-cache-8.0.0.tgz", - "integrity": "sha512-XXTUwCvisa5oacNGRP9SfNtYBNAMi+RPwBFmblZEF7N7swHYQS6/Zfk7SRwx4D5j3CH211YNRco1DEMNVfZCnQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "flat-cache": "^4.0.0" - }, - "engines": { - "node": ">=16.0.0" - } - }, - "node_modules/fill-range": { - "version": "7.1.1", - "resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.1.1.tgz", - "integrity": "sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==", - "dev": true, - "license": "MIT", - "dependencies": { - "to-regex-range": "^5.0.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/find-up": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/find-up/-/find-up-5.0.0.tgz", - "integrity": "sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==", - "dev": true, - "license": "MIT", - "dependencies": { - "locate-path": "^6.0.0", - "path-exists": "^4.0.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/find-up-simple": { - "version": "1.0.1", - "resolved": "https://registry.npmjs.org/find-up-simple/-/find-up-simple-1.0.1.tgz", - "integrity": "sha512-afd4O7zpqHeRyg4PfDQsXmlDe2PfdHtJt6Akt8jOWaApLOZk5JXs6VMR29lz03pRe9mpykrRCYIYxaJYcfpncQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/flat-cache": { - "version": "4.0.1", - "resolved": "https://registry.npmjs.org/flat-cache/-/flat-cache-4.0.1.tgz", - "integrity": "sha512-f7ccFPK3SXFHpx15UIGyRJ/FJQctuKZ0zVuN3frBo4HnK3cay9VEW0R6yPYFHC0AgqhukPzKjq22t5DmAyqGyw==", - "dev": true, - "license": "MIT", - "dependencies": { - "flatted": "^3.2.9", - "keyv": "^4.5.4" - }, - "engines": { - "node": ">=16" - } - }, - "node_modules/flatted": { - "version": "3.3.3", - "resolved": "https://registry.npmjs.org/flatted/-/flatted-3.3.3.tgz", - "integrity": "sha512-GX+ysw4PBCz0PzosHDepZGANEuFCMLrnRTiEy9McGjmkCQYwRq4A/X786G/fjM/+OjsWSU1ZrY5qyARZmO/uwg==", - "dev": true, - "license": "ISC" - }, - "node_modules/flattie": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/flattie/-/flattie-1.1.1.tgz", - "integrity": "sha512-9UbaD6XdAL97+k/n+N7JwX46K/M6Zc6KcFYskrYL8wbBV/Uyk0CTAMY0VT+qiK5PM7AIc9aTWYtq65U7T+aCNQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/fontace": { - "version": "0.4.0", - "resolved": "https://registry.npmjs.org/fontace/-/fontace-0.4.0.tgz", - "integrity": "sha512-moThBCItUe2bjZip5PF/iZClpKHGLwMvR79Kp8XpGRBrvoRSnySN4VcILdv3/MJzbhvUA5WeiUXF5o538m5fvg==", - "dev": true, - "license": "MIT", - "dependencies": { - "fontkitten": "^1.0.0" - } - }, - "node_modules/fontkitten": { - "version": "1.0.2", - "resolved": "https://registry.npmjs.org/fontkitten/-/fontkitten-1.0.2.tgz", - "integrity": "sha512-piJxbLnkD9Xcyi7dWJRnqszEURixe7CrF/efBfbffe2DPyabmuIuqraruY8cXTs19QoM8VJzx47BDRVNXETM7Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "tiny-inflate": "^1.0.3" - }, - "engines": { - "node": ">=20" - } - }, - "node_modules/foreground-child": { - "version": "3.3.1", - "resolved": "https://registry.npmjs.org/foreground-child/-/foreground-child-3.3.1.tgz", - "integrity": "sha512-gIXjKqtFuWEgzFRJA9WCQeSJLZDjgJUOMCMzxtvFq/37KojM1BFGufqsCy0r4qSQmYLsZYMeyRqzIWOMup03sw==", - "license": "ISC", - "dependencies": { - "cross-spawn": "^7.0.6", - "signal-exit": "^4.0.1" - }, - "engines": { - "node": ">=14" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/fs-extra": { - "version": "11.3.3", - "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-11.3.3.tgz", - "integrity": "sha512-VWSRii4t0AFm6ixFFmLLx1t7wS1gh+ckoa84aOeapGum0h+EZd1EhEumSB+ZdDLnEPuucsVB9oB7cxJHap6Afg==", - "license": "MIT", - "dependencies": { - "graceful-fs": "^4.2.0", - "jsonfile": "^6.0.1", - "universalify": "^2.0.0" - }, - "engines": { - "node": ">=14.14" - } - }, - "node_modules/fs.realpath": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz", - "integrity": "sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==", - "dev": true, - "license": "ISC" - }, - "node_modules/fsevents": { - "version": "2.3.3", - "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.3.tgz", - "integrity": "sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==", - "dev": true, - "hasInstallScript": true, - "license": "MIT", - "optional": true, - "os": [ - "darwin" - ], - "engines": { - "node": "^8.16.0 || ^10.6.0 || >=11.0.0" - } - }, - "node_modules/gensync": { - "version": "1.0.0-beta.2", - "resolved": "https://registry.npmjs.org/gensync/-/gensync-1.0.0-beta.2.tgz", - "integrity": "sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6.9.0" - } - }, - "node_modules/get-caller-file": { - "version": "2.0.5", - "resolved": "https://registry.npmjs.org/get-caller-file/-/get-caller-file-2.0.5.tgz", - "integrity": "sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==", - "dev": true, - "license": "ISC", - "engines": { - "node": "6.* || 8.* || >= 10.*" - } - }, - "node_modules/get-east-asian-width": { - "version": "1.4.0", - "resolved": "https://registry.npmjs.org/get-east-asian-width/-/get-east-asian-width-1.4.0.tgz", - "integrity": "sha512-QZjmEOC+IT1uk6Rx0sX22V6uHWVwbdbxf1faPqJ1QhLdGgsRGCZoyaQBm/piRdJy/D2um6hM1UP7ZEeQ4EkP+Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/get-package-type": { - "version": "0.1.0", - "resolved": "https://registry.npmjs.org/get-package-type/-/get-package-type-0.1.0.tgz", - "integrity": "sha512-pjzuKtY64GYfWizNAJ0fr9VqttZkNiK2iS430LtIHzjBEr6bX8Am2zm4sW4Ro5wjWW5cAlRL1qAMTcXbjNAO2Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8.0.0" - } - }, - "node_modules/get-stream": { - "version": "6.0.1", - "resolved": "https://registry.npmjs.org/get-stream/-/get-stream-6.0.1.tgz", - "integrity": "sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/get-tsconfig": { - "version": "4.13.0", - "resolved": "https://registry.npmjs.org/get-tsconfig/-/get-tsconfig-4.13.0.tgz", - "integrity": "sha512-1VKTZJCwBrvbd+Wn3AOgQP/2Av+TfTCOlE4AcRJE72W1ksZXbAx8PPBR9RzgTeSPzlPMHrbANMH3LbltH73wxQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "resolve-pkg-maps": "^1.0.0" - }, - "funding": { - "url": "https://github.com/privatenumber/get-tsconfig?sponsor=1" - } - }, - "node_modules/git-hooks-list": { - "version": "4.2.1", - "resolved": "https://registry.npmjs.org/git-hooks-list/-/git-hooks-list-4.2.1.tgz", - "integrity": "sha512-WNvqJjOxxs/8ZP9+DWdwWJ7cDsd60NHf39XnD82pDVrKO5q7xfPqpkK6hwEAmBa/ZSEE4IOoR75EzbbIuwGlMw==", - "dev": true, - "license": "MIT", - "funding": { - "url": "https://github.com/fisker/git-hooks-list?sponsor=1" - } - }, - "node_modules/github-slugger": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/github-slugger/-/github-slugger-2.0.0.tgz", - "integrity": "sha512-IaOQ9puYtjrkq7Y0Ygl9KDZnrf/aiUJYUpVf89y8kyaxbRG7Y1SrX/jaumrv81vc61+kiMempujsM3Yw7w5qcw==", - "dev": true, - "license": "ISC" - }, - "node_modules/glob": { - "version": "11.1.0", - "resolved": "https://registry.npmjs.org/glob/-/glob-11.1.0.tgz", - "integrity": "sha512-vuNwKSaKiqm7g0THUBu2x7ckSs3XJLXE+2ssL7/MfTGPLLcrJQ/4Uq1CjPTtO5cCIiRxqvN6Twy1qOwhL0Xjcw==", - "license": "BlueOak-1.0.0", - "dependencies": { - "foreground-child": "^3.3.1", - "jackspeak": "^4.1.1", - "minimatch": "^10.1.1", - "minipass": "^7.1.2", - "package-json-from-dist": "^1.0.0", - "path-scurry": "^2.0.0" - }, - "bin": { - "glob": "dist/esm/bin.mjs" - }, - "engines": { - "node": "20 || >=22" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/glob-parent": { - "version": "6.0.2", - "resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-6.0.2.tgz", - "integrity": "sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==", - "dev": true, - "license": "ISC", - "dependencies": { - "is-glob": "^4.0.3" - }, - "engines": { - "node": ">=10.13.0" - } - }, - "node_modules/glob/node_modules/minimatch": { - "version": "10.1.1", - "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-10.1.1.tgz", - "integrity": "sha512-enIvLvRAFZYXJzkCYG5RKmPfrFArdLv+R+lbQ53BmIMLIry74bjKzX6iHAm8WYamJkhSSEabrWN5D97XnKObjQ==", - "license": "BlueOak-1.0.0", - "dependencies": { - "@isaacs/brace-expansion": "^5.0.0" - }, - "engines": { - "node": "20 || >=22" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/globals": { - "version": "14.0.0", - "resolved": "https://registry.npmjs.org/globals/-/globals-14.0.0.tgz", - "integrity": "sha512-oahGvuMGQlPw/ivIYBjVSrWAfWLBeku5tpPE2fOPLi+WHffIWbuh2tCjhyQhTBPMf5E9jDEH4FOmTYgYwbKwtQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/globby": { - "version": "15.0.0", - "resolved": "https://registry.npmjs.org/globby/-/globby-15.0.0.tgz", - "integrity": "sha512-oB4vkQGqlMl682wL1IlWd02tXCbquGWM4voPEI85QmNKCaw8zGTm1f1rubFgkg3Eli2PtKlFgrnmUqasbQWlkw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@sindresorhus/merge-streams": "^4.0.0", - "fast-glob": "^3.3.3", - "ignore": "^7.0.5", - "path-type": "^6.0.0", - "slash": "^5.1.0", - "unicorn-magic": "^0.3.0" - }, - "engines": { - "node": ">=20" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/globby/node_modules/slash": { - "version": "5.1.0", - "resolved": "https://registry.npmjs.org/slash/-/slash-5.1.0.tgz", - "integrity": "sha512-ZA6oR3T/pEyuqwMgAKT0/hAv8oAXckzbkmR0UkUosQ+Mc4RxGoJkRmwHgHufaenlyAgE1Mxgpdcrf75y6XcnDg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=14.16" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/globrex": { - "version": "0.1.2", - "resolved": "https://registry.npmjs.org/globrex/-/globrex-0.1.2.tgz", - "integrity": "sha512-uHJgbwAMwNFf5mLst7IWLNg14x1CkeqglJb/K3doi4dw6q2IvAAmM/Y81kevy83wP+Sst+nutFTYOGg3d1lsxg==", - "dev": true, - "license": "MIT" - }, - "node_modules/graceful-fs": { - "version": "4.2.11", - "resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.11.tgz", - "integrity": "sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==", - "license": "ISC" - }, - "node_modules/h3": { - "version": "1.15.5", - "resolved": "https://registry.npmjs.org/h3/-/h3-1.15.5.tgz", - "integrity": "sha512-xEyq3rSl+dhGX2Lm0+eFQIAzlDN6Fs0EcC4f7BNUmzaRX/PTzeuM+Tr2lHB8FoXggsQIeXLj8EDVgs5ywxyxmg==", - "dev": true, - "license": "MIT", - "dependencies": { - "cookie-es": "^1.2.2", - "crossws": "^0.3.5", - "defu": "^6.1.4", - "destr": "^2.0.5", - "iron-webcrypto": "^1.2.1", - "node-mock-http": "^1.0.4", - "radix3": "^1.1.2", - "ufo": "^1.6.3", - "uncrypto": "^0.1.3" - } - }, - "node_modules/has-flag": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz", - "integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==", - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/hast-util-embedded": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/hast-util-embedded/-/hast-util-embedded-3.0.0.tgz", - "integrity": "sha512-naH8sld4Pe2ep03qqULEtvYr7EjrLK2QHY8KJR6RJkTUjPGObe1vnx585uzem2hGra+s1q08DZZpfgDVYRbaXA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "hast-util-is-element": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-format": { - "version": "1.1.0", - "resolved": "https://registry.npmjs.org/hast-util-format/-/hast-util-format-1.1.0.tgz", - "integrity": "sha512-yY1UDz6bC9rDvCWHpx12aIBGRG7krurX0p0Fm6pT547LwDIZZiNr8a+IHDogorAdreULSEzP82Nlv5SZkHZcjA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "hast-util-embedded": "^3.0.0", - "hast-util-minify-whitespace": "^1.0.0", - "hast-util-phrasing": "^3.0.0", - "hast-util-whitespace": "^3.0.0", - "html-whitespace-sensitive-tag-names": "^3.0.0", - "unist-util-visit-parents": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-from-html": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/hast-util-from-html/-/hast-util-from-html-2.0.3.tgz", - "integrity": "sha512-CUSRHXyKjzHov8yKsQjGOElXy/3EKpyX56ELnkHH34vDVw1N1XSQ1ZcAvTyAPtGqLTuKP/uxM+aLkSPqF/EtMw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "devlop": "^1.1.0", - "hast-util-from-parse5": "^8.0.0", - "parse5": "^7.0.0", - "vfile": "^6.0.0", - "vfile-message": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-from-parse5": { - "version": "8.0.3", - "resolved": "https://registry.npmjs.org/hast-util-from-parse5/-/hast-util-from-parse5-8.0.3.tgz", - "integrity": "sha512-3kxEVkEKt0zvcZ3hCRYI8rqrgwtlIOFMWkbclACvjlDw8Li9S2hk/d51OI0nr/gIpdMHNepwgOKqZ/sy0Clpyg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "@types/unist": "^3.0.0", - "devlop": "^1.0.0", - "hastscript": "^9.0.0", - "property-information": "^7.0.0", - "vfile": "^6.0.0", - "vfile-location": "^5.0.0", - "web-namespaces": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-has-property": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/hast-util-has-property/-/hast-util-has-property-3.0.0.tgz", - "integrity": "sha512-MNilsvEKLFpV604hwfhVStK0usFY/QmM5zX16bo7EjnAEGofr5YyI37kzopBlZJkHD4t887i+q/C8/tr5Q94cA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-is-body-ok-link": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/hast-util-is-body-ok-link/-/hast-util-is-body-ok-link-3.0.1.tgz", - "integrity": "sha512-0qpnzOBLztXHbHQenVB8uNuxTnm/QBFUOmdOSsEn7GnBtyY07+ENTWVFBAnXd/zEgd9/SUG3lRY7hSIBWRgGpQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-is-element": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/hast-util-is-element/-/hast-util-is-element-3.0.0.tgz", - "integrity": "sha512-Val9mnv2IWpLbNPqc/pUem+a7Ipj2aHacCwgNfTiK0vJKl0LF+4Ba4+v1oPHFpf3bLYmreq0/l3Gud9S5OH42g==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-minify-whitespace": { - "version": "1.0.1", - "resolved": "https://registry.npmjs.org/hast-util-minify-whitespace/-/hast-util-minify-whitespace-1.0.1.tgz", - "integrity": "sha512-L96fPOVpnclQE0xzdWb/D12VT5FabA7SnZOUMtL1DbXmYiHJMXZvFkIZfiMmTCNJHUeO2K9UYNXoVyfz+QHuOw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "hast-util-embedded": "^3.0.0", - "hast-util-is-element": "^3.0.0", - "hast-util-whitespace": "^3.0.0", - "unist-util-is": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-parse-selector": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/hast-util-parse-selector/-/hast-util-parse-selector-4.0.0.tgz", - "integrity": "sha512-wkQCkSYoOGCRKERFWcxMVMOcYE2K1AaNLU8DXS9arxnLOUEWbOXKXiJUNzEpqZ3JOKpnha3jkFrumEjVliDe7A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-phrasing": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/hast-util-phrasing/-/hast-util-phrasing-3.0.1.tgz", - "integrity": "sha512-6h60VfI3uBQUxHqTyMymMZnEbNl1XmEGtOxxKYL7stY2o601COo62AWAYBQR9lZbYXYSBoxag8UpPRXK+9fqSQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "hast-util-embedded": "^3.0.0", - "hast-util-has-property": "^3.0.0", - "hast-util-is-body-ok-link": "^3.0.0", - "hast-util-is-element": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-raw": { - "version": "9.1.0", - "resolved": "https://registry.npmjs.org/hast-util-raw/-/hast-util-raw-9.1.0.tgz", - "integrity": "sha512-Y8/SBAHkZGoNkpzqqfCldijcuUKh7/su31kEBp67cFY09Wy0mTRgtsLYsiIxMJxlu0f6AA5SUTbDR8K0rxnbUw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "@types/unist": "^3.0.0", - "@ungap/structured-clone": "^1.0.0", - "hast-util-from-parse5": "^8.0.0", - "hast-util-to-parse5": "^8.0.0", - "html-void-elements": "^3.0.0", - "mdast-util-to-hast": "^13.0.0", - "parse5": "^7.0.0", - "unist-util-position": "^5.0.0", - "unist-util-visit": "^5.0.0", - "vfile": "^6.0.0", - "web-namespaces": "^2.0.0", - "zwitch": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-select": { - "version": "6.0.4", - "resolved": "https://registry.npmjs.org/hast-util-select/-/hast-util-select-6.0.4.tgz", - "integrity": "sha512-RqGS1ZgI0MwxLaKLDxjprynNzINEkRHY2i8ln4DDjgv9ZhcYVIHN9rlpiYsqtFwrgpYU361SyWDQcGNIBVu3lw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "@types/unist": "^3.0.0", - "bcp-47-match": "^2.0.0", - "comma-separated-tokens": "^2.0.0", - "css-selector-parser": "^3.0.0", - "devlop": "^1.0.0", - "direction": "^2.0.0", - "hast-util-has-property": "^3.0.0", - "hast-util-to-string": "^3.0.0", - "hast-util-whitespace": "^3.0.0", - "nth-check": "^2.0.0", - "property-information": "^7.0.0", - "space-separated-tokens": "^2.0.0", - "unist-util-visit": "^5.0.0", - "zwitch": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-to-estree": { - "version": "3.1.3", - "resolved": "https://registry.npmjs.org/hast-util-to-estree/-/hast-util-to-estree-3.1.3.tgz", - "integrity": "sha512-48+B/rJWAp0jamNbAAf9M7Uf//UVqAoMmgXhBdxTDJLGKY+LRnZ99qcG+Qjl5HfMpYNzS5v4EAwVEF34LeAj7w==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "@types/estree-jsx": "^1.0.0", - "@types/hast": "^3.0.0", - "comma-separated-tokens": "^2.0.0", - "devlop": "^1.0.0", - "estree-util-attach-comments": "^3.0.0", - "estree-util-is-identifier-name": "^3.0.0", - "hast-util-whitespace": "^3.0.0", - "mdast-util-mdx-expression": "^2.0.0", - "mdast-util-mdx-jsx": "^3.0.0", - "mdast-util-mdxjs-esm": "^2.0.0", - "property-information": "^7.0.0", - "space-separated-tokens": "^2.0.0", - "style-to-js": "^1.0.0", - "unist-util-position": "^5.0.0", - "zwitch": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-to-html": { - "version": "9.0.5", - "resolved": "https://registry.npmjs.org/hast-util-to-html/-/hast-util-to-html-9.0.5.tgz", - "integrity": "sha512-OguPdidb+fbHQSU4Q4ZiLKnzWo8Wwsf5bZfbvu7//a9oTYoqD/fWpe96NuHkoS9h0ccGOTe0C4NGXdtS0iObOw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "@types/unist": "^3.0.0", - "ccount": "^2.0.0", - "comma-separated-tokens": "^2.0.0", - "hast-util-whitespace": "^3.0.0", - "html-void-elements": "^3.0.0", - "mdast-util-to-hast": "^13.0.0", - "property-information": "^7.0.0", - "space-separated-tokens": "^2.0.0", - "stringify-entities": "^4.0.0", - "zwitch": "^2.0.4" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-to-jsx-runtime": { - "version": "2.3.6", - "resolved": "https://registry.npmjs.org/hast-util-to-jsx-runtime/-/hast-util-to-jsx-runtime-2.3.6.tgz", - "integrity": "sha512-zl6s8LwNyo1P9uw+XJGvZtdFF1GdAkOg8ujOw+4Pyb76874fLps4ueHXDhXWdk6YHQ6OgUtinliG7RsYvCbbBg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "@types/hast": "^3.0.0", - "@types/unist": "^3.0.0", - "comma-separated-tokens": "^2.0.0", - "devlop": "^1.0.0", - "estree-util-is-identifier-name": "^3.0.0", - "hast-util-whitespace": "^3.0.0", - "mdast-util-mdx-expression": "^2.0.0", - "mdast-util-mdx-jsx": "^3.0.0", - "mdast-util-mdxjs-esm": "^2.0.0", - "property-information": "^7.0.0", - "space-separated-tokens": "^2.0.0", - "style-to-js": "^1.0.0", - "unist-util-position": "^5.0.0", - "vfile-message": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-to-parse5": { - "version": "8.0.1", - "resolved": "https://registry.npmjs.org/hast-util-to-parse5/-/hast-util-to-parse5-8.0.1.tgz", - "integrity": "sha512-MlWT6Pjt4CG9lFCjiz4BH7l9wmrMkfkJYCxFwKQic8+RTZgWPuWxwAfjJElsXkex7DJjfSJsQIt931ilUgmwdA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "comma-separated-tokens": "^2.0.0", - "devlop": "^1.0.0", - "property-information": "^7.0.0", - "space-separated-tokens": "^2.0.0", - "web-namespaces": "^2.0.0", - "zwitch": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-to-string": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/hast-util-to-string/-/hast-util-to-string-3.0.1.tgz", - "integrity": "sha512-XelQVTDWvqcl3axRfI0xSeoVKzyIFPwsAGSLIsKdJKQMXDYJS4WYrBNF/8J7RdhIcFI2BOHgAifggsvsxp/3+A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-to-text": { - "version": "4.0.2", - "resolved": "https://registry.npmjs.org/hast-util-to-text/-/hast-util-to-text-4.0.2.tgz", - "integrity": "sha512-KK6y/BN8lbaq654j7JgBydev7wuNMcID54lkRav1P0CaE1e47P72AWWPiGKXTJU271ooYzcvTAn/Zt0REnvc7A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "@types/unist": "^3.0.0", - "hast-util-is-element": "^3.0.0", - "unist-util-find-after": "^5.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hast-util-whitespace": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/hast-util-whitespace/-/hast-util-whitespace-3.0.0.tgz", - "integrity": "sha512-88JUN06ipLwsnv+dVn+OIYOvAuvBMy/Qoi6O7mQHxdPXpjy+Cd6xRkWwux7DKO+4sYILtLBRIKgsdpS2gQc7qw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/hastscript": { - "version": "9.0.1", - "resolved": "https://registry.npmjs.org/hastscript/-/hastscript-9.0.1.tgz", - "integrity": "sha512-g7df9rMFX/SPi34tyGCyUBREQoKkapwdY/T04Qn9TDWfHhAYt4/I0gMVirzK5wEzeUqIjEB+LXC/ypb7Aqno5w==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "comma-separated-tokens": "^2.0.0", - "hast-util-parse-selector": "^4.0.0", - "property-information": "^7.0.0", - "space-separated-tokens": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/html-escaper": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/html-escaper/-/html-escaper-3.0.3.tgz", - "integrity": "sha512-RuMffC89BOWQoY0WKGpIhn5gX3iI54O6nRA0yC124NYVtzjmFWBIiFd8M0x+ZdX0P9R4lADg1mgP8C7PxGOWuQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/html-void-elements": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/html-void-elements/-/html-void-elements-3.0.0.tgz", - "integrity": "sha512-bEqo66MRXsUGxWHV5IP0PUiAWwoEjba4VCzg0LjFJBpchPaTfyfCKTG6bc5F8ucKec3q5y6qOdGyYTSBEvhCrg==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/html-whitespace-sensitive-tag-names": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/html-whitespace-sensitive-tag-names/-/html-whitespace-sensitive-tag-names-3.0.1.tgz", - "integrity": "sha512-q+310vW8zmymYHALr1da4HyXUQ0zgiIwIicEfotYPWGN0OJVEN/58IJ3A4GBYcEq3LGAZqKb+ugvP0GNB9CEAA==", - "dev": true, - "license": "MIT", - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/http-cache-semantics": { - "version": "4.2.0", - "resolved": "https://registry.npmjs.org/http-cache-semantics/-/http-cache-semantics-4.2.0.tgz", - "integrity": "sha512-dTxcvPXqPvXBQpq5dUr6mEMJX4oIEFv6bwom3FDwKRDsuIjjJGANqhBuoAn9c1RQJIdAKav33ED65E2ys+87QQ==", - "dev": true, - "license": "BSD-2-Clause" - }, - "node_modules/human-signals": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/human-signals/-/human-signals-2.1.0.tgz", - "integrity": "sha512-B4FFZ6q/T2jhhksgkbEW3HBvWIfDW85snkQgawt07S7J5QXTk6BkNV+0yAeZrM5QpMAdYlocGoljn0sJ/WQkFw==", - "dev": true, - "license": "Apache-2.0", - "engines": { - "node": ">=10.17.0" - } - }, - "node_modules/husky": { - "version": "9.1.7", - "resolved": "https://registry.npmjs.org/husky/-/husky-9.1.7.tgz", - "integrity": "sha512-5gs5ytaNjBrh5Ow3zrvdUUY+0VxIuWVL4i9irt6friV+BqdCfmV11CQTWMiBYWHbXhco+J1kHfTOUkePhCDvMA==", - "dev": true, - "license": "MIT", - "bin": { - "husky": "bin.js" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/typicode" - } - }, - "node_modules/i18next": { - "version": "23.16.8", - "resolved": "https://registry.npmjs.org/i18next/-/i18next-23.16.8.tgz", - "integrity": "sha512-06r/TitrM88Mg5FdUXAKL96dJMzgqLE5dv3ryBAra4KCwD9mJ4ndOTS95ZuymIGoE+2hzfdaMak2X11/es7ZWg==", - "dev": true, - "funding": [ - { - "type": "individual", - "url": "https://locize.com" - }, - { - "type": "individual", - "url": "https://locize.com/i18next.html" - }, - { - "type": "individual", - "url": "https://www.i18next.com/how-to/faq#i18next-is-awesome.-how-can-i-support-the-project" - } - ], - "license": "MIT", - "dependencies": { - "@babel/runtime": "^7.23.2" - } - }, - "node_modules/ignore": { - "version": "7.0.5", - "resolved": "https://registry.npmjs.org/ignore/-/ignore-7.0.5.tgz", - "integrity": "sha512-Hs59xBNfUIunMFgWAbGX5cq6893IbWg4KnrjbYwX3tx0ztorVgTDA6B2sxf8ejHJ4wz8BqGUMYlnzNBer5NvGg==", - "license": "MIT", - "engines": { - "node": ">= 4" - } - }, - "node_modules/import-fresh": { - "version": "3.3.1", - "resolved": "https://registry.npmjs.org/import-fresh/-/import-fresh-3.3.1.tgz", - "integrity": "sha512-TR3KfrTZTYLPB6jUjfx6MF9WcWrHL9su5TObK4ZkYgBdWKPOFoSoQIdEuTuR82pmtxH2spWG9h6etwfr1pLBqQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "parent-module": "^1.0.0", - "resolve-from": "^4.0.0" - }, - "engines": { - "node": ">=6" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/import-local": { - "version": "3.2.0", - "resolved": "https://registry.npmjs.org/import-local/-/import-local-3.2.0.tgz", - "integrity": "sha512-2SPlun1JUPWoM6t3F0dw0FkCF/jWY8kttcY4f599GLTSjh2OCuuhdTkJQsEcZzBqbXZGKMK2OqW1oZsjtf/gQA==", - "dev": true, - "license": "MIT", - "dependencies": { - "pkg-dir": "^4.2.0", - "resolve-cwd": "^3.0.0" - }, - "bin": { - "import-local-fixture": "fixtures/cli.js" - }, - "engines": { - "node": ">=8" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/import-meta-resolve": { - "version": "4.2.0", - "resolved": "https://registry.npmjs.org/import-meta-resolve/-/import-meta-resolve-4.2.0.tgz", - "integrity": "sha512-Iqv2fzaTQN28s/FwZAoFq0ZSs/7hMAHJVX+w8PZl3cY19Pxk6jFFalxQoIfW2826i/fDLXv8IiEZRIT0lDuWcg==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/imurmurhash": { - "version": "0.1.4", - "resolved": "https://registry.npmjs.org/imurmurhash/-/imurmurhash-0.1.4.tgz", - "integrity": "sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=0.8.19" - } - }, - "node_modules/indent-string": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/indent-string/-/indent-string-5.0.0.tgz", - "integrity": "sha512-m6FAo/spmsW2Ab2fU35JTYwtOKa2yAwXSwgjSv1TJzh4Mh7mC3lzAOVLBprb72XsTrgkEIsl7YrFNAiDiRhIGg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/inflight": { - "version": "1.0.6", - "resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.6.tgz", - "integrity": "sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==", - "deprecated": "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.", - "dev": true, - "license": "ISC", - "dependencies": { - "once": "^1.3.0", - "wrappy": "1" - } - }, - "node_modules/inherits": { - "version": "2.0.4", - "resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz", - "integrity": "sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==", - "dev": true, - "license": "ISC" - }, - "node_modules/ini": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/ini/-/ini-2.0.0.tgz", - "integrity": "sha512-7PnF4oN3CvZF23ADhA5wRaYEQpJ8qygSkbtTXWBeXWXmEVRXK+1ITciHWwHhsjv1TmW0MgacIv6hEi5pX5NQdA==", - "dev": true, - "license": "ISC", - "engines": { - "node": ">=10" - } - }, - "node_modules/inline-style-parser": { - "version": "0.2.7", - "resolved": "https://registry.npmjs.org/inline-style-parser/-/inline-style-parser-0.2.7.tgz", - "integrity": "sha512-Nb2ctOyNR8DqQoR0OwRG95uNWIC0C1lCgf5Naz5H6Ji72KZ8OcFZLz2P5sNgwlyoJ8Yif11oMuYs5pBQa86csA==", - "dev": true, - "license": "MIT" - }, - "node_modules/iron-webcrypto": { - "version": "1.2.1", - "resolved": "https://registry.npmjs.org/iron-webcrypto/-/iron-webcrypto-1.2.1.tgz", - "integrity": "sha512-feOM6FaSr6rEABp/eDfVseKyTMDt+KGpeB35SkVn9Tyn0CqvVsY3EwI0v5i8nMHyJnzCIQf7nsy3p41TPkJZhg==", - "dev": true, - "license": "MIT", - "funding": { - "url": "https://github.com/sponsors/brc-dd" - } - }, - "node_modules/is-alphabetical": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/is-alphabetical/-/is-alphabetical-2.0.1.tgz", - "integrity": "sha512-FWyyY60MeTNyeSRpkM2Iry0G9hpr7/9kD40mD/cGQEuilcZYS4okz8SN2Q6rLCJ8gbCt6fN+rC+6tMGS99LaxQ==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/is-alphanumerical": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/is-alphanumerical/-/is-alphanumerical-2.0.1.tgz", - "integrity": "sha512-hmbYhX/9MUMF5uh7tOXyK/n0ZvWpad5caBA17GsC6vyuCqaWliRG5K1qS9inmUhEMaOBIW7/whAnSwveW/LtZw==", - "dev": true, - "license": "MIT", - "dependencies": { - "is-alphabetical": "^2.0.0", - "is-decimal": "^2.0.0" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/is-arrayish": { - "version": "0.2.1", - "resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz", - "integrity": "sha512-zz06S8t0ozoDXMG+ube26zeCTNXcKIPJZJi8hBrF4idCLms4CG9QtK7qBl1boi5ODzFpjswb5JPmHCbMpjaYzg==", - "dev": true, - "license": "MIT" - }, - "node_modules/is-builtin-module": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/is-builtin-module/-/is-builtin-module-5.0.0.tgz", - "integrity": "sha512-f4RqJKBUe5rQkJ2eJEJBXSticB3hGbN9j0yxxMQFqIW89Jp9WYFtzfTcRlstDKVUTRzSOTLKRfO9vIztenwtxA==", - "dev": true, - "license": "MIT", - "dependencies": { - "builtin-modules": "^5.0.0" - }, - "engines": { - "node": ">=18.20" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/is-decimal": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/is-decimal/-/is-decimal-2.0.1.tgz", - "integrity": "sha512-AAB9hiomQs5DXWcRB1rqsxGUstbRroFOPPVAomNk/3XHR5JyEZChOyTWe2oayKnsSsr/kcGqF+z6yuH6HHpN0A==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/is-docker": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/is-docker/-/is-docker-3.0.0.tgz", - "integrity": "sha512-eljcgEDlEns/7AXFosB5K/2nCM4P7FQPkGc/DWLy5rmFEWvZayGrik1d9/QIY5nJ4f9YsVvBkA6kJpHn9rISdQ==", - "dev": true, - "license": "MIT", - "bin": { - "is-docker": "cli.js" - }, - "engines": { - "node": "^12.20.0 || ^14.13.1 || >=16.0.0" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/is-extglob": { - "version": "2.1.1", - "resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz", - "integrity": "sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=0.10.0" - } - }, - "node_modules/is-fullwidth-code-point": { - "version": "5.1.0", - "resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-5.1.0.tgz", - "integrity": "sha512-5XHYaSyiqADb4RnZ1Bdad6cPp8Toise4TzEjcOYDHZkTCbKgiUl7WTUCpNWHuxmDt91wnsZBc9xinNzopv3JMQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "get-east-asian-width": "^1.3.1" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/is-generator-fn": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/is-generator-fn/-/is-generator-fn-2.1.0.tgz", - "integrity": "sha512-cTIB4yPYL/Grw0EaSzASzg6bBy9gqCofvWN8okThAYIxKJZC+udlRAmGbM0XLeniEJSs8uEgHPGuHSe1XsOLSQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/is-glob": { - "version": "4.0.3", - "resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz", - "integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==", - "dev": true, - "license": "MIT", - "dependencies": { - "is-extglob": "^2.1.1" - }, - "engines": { - "node": ">=0.10.0" - } - }, - "node_modules/is-hexadecimal": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/is-hexadecimal/-/is-hexadecimal-2.0.1.tgz", - "integrity": "sha512-DgZQp241c8oO6cA1SbTEWiXeoxV42vlcJxgH+B3hi1AiqqKruZR3ZGF8In3fj4+/y/7rHvlOZLZtgJ/4ttYGZg==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/is-inside-container": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/is-inside-container/-/is-inside-container-1.0.0.tgz", - "integrity": "sha512-KIYLCCJghfHZxqjYBE7rEy0OBuTd5xCHS7tHVgvCLkx7StIoaxwNW3hCALgEUjFfeRk+MG/Qxmp/vtETEF3tRA==", - "dev": true, - "license": "MIT", - "dependencies": { - "is-docker": "^3.0.0" - }, - "bin": { - "is-inside-container": "cli.js" - }, - "engines": { - "node": ">=14.16" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/is-number": { - "version": "7.0.0", - "resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz", - "integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=0.12.0" - } - }, - "node_modules/is-plain-obj": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/is-plain-obj/-/is-plain-obj-4.1.0.tgz", - "integrity": "sha512-+Pgi+vMuUNkJyExiMBt5IlFoMyKnr5zhJ4Uspz58WOhBF5QoIZkFyNHIbBAtHwzVAgk5RtndVNsDRN61/mmDqg==", - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/is-stream": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/is-stream/-/is-stream-2.0.1.tgz", - "integrity": "sha512-hFoiJiTl63nn+kstHGBtewWSKnQLpyb155KHheA1l39uvtO9nWIop1p3udqPcUd/xbF1VLMO4n7OI6p7RbngDg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/is-wsl": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/is-wsl/-/is-wsl-3.1.0.tgz", - "integrity": "sha512-UcVfVfaK4Sc4m7X3dUSoHoozQGBEFeDC+zVo06t98xe8CzHSZZBekNXH+tu0NalHolcJ/QAGqS46Hef7QXBIMw==", - "dev": true, - "license": "MIT", - "dependencies": { - "is-inside-container": "^1.0.0" - }, - "engines": { - "node": ">=16" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/isexe": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz", - "integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==", - "license": "ISC" - }, - "node_modules/istanbul-lib-coverage": { - "version": "3.2.2", - "resolved": "https://registry.npmjs.org/istanbul-lib-coverage/-/istanbul-lib-coverage-3.2.2.tgz", - "integrity": "sha512-O8dpsF+r0WV/8MNRKfnmrtCWhuKjxrq2w+jpzBL5UZKTi2LeVWnWOmWRxFlesJONmc+wLAGvKQZEOanko0LFTg==", - "dev": true, - "license": "BSD-3-Clause", - "engines": { - "node": ">=8" - } - }, - "node_modules/istanbul-lib-instrument": { - "version": "6.0.3", - "resolved": "https://registry.npmjs.org/istanbul-lib-instrument/-/istanbul-lib-instrument-6.0.3.tgz", - "integrity": "sha512-Vtgk7L/R2JHyyGW07spoFlB8/lpjiOLTjMdms6AFMraYt3BaJauod/NGrfnVG/y4Ix1JEuMRPDPEj2ua+zz1/Q==", - "dev": true, - "license": "BSD-3-Clause", - "dependencies": { - "@babel/core": "^7.23.9", - "@babel/parser": "^7.23.9", - "@istanbuljs/schema": "^0.1.3", - "istanbul-lib-coverage": "^3.2.0", - "semver": "^7.5.4" - }, - "engines": { - "node": ">=10" - } - }, - "node_modules/istanbul-lib-report": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/istanbul-lib-report/-/istanbul-lib-report-3.0.1.tgz", - "integrity": "sha512-GCfE1mtsHGOELCU8e/Z7YWzpmybrx/+dSTfLrvY8qRmaY6zXTKWn6WQIjaAFw069icm6GVMNkgu0NzI4iPZUNw==", - "dev": true, - "license": "BSD-3-Clause", - "dependencies": { - "istanbul-lib-coverage": "^3.0.0", - "make-dir": "^4.0.0", - "supports-color": "^7.1.0" - }, - "engines": { - "node": ">=10" - } - }, - "node_modules/istanbul-lib-source-maps": { - "version": "5.0.6", - "resolved": "https://registry.npmjs.org/istanbul-lib-source-maps/-/istanbul-lib-source-maps-5.0.6.tgz", - "integrity": "sha512-yg2d+Em4KizZC5niWhQaIomgf5WlL4vOOjZ5xGCmF8SnPE/mDWWXgvRExdcpCgh9lLRRa1/fSYp2ymmbJ1pI+A==", - "dev": true, - "license": "BSD-3-Clause", - "dependencies": { - "@jridgewell/trace-mapping": "^0.3.23", - "debug": "^4.1.1", - "istanbul-lib-coverage": "^3.0.0" - }, - "engines": { - "node": ">=10" - } - }, - "node_modules/istanbul-reports": { - "version": "3.2.0", - "resolved": "https://registry.npmjs.org/istanbul-reports/-/istanbul-reports-3.2.0.tgz", - "integrity": "sha512-HGYWWS/ehqTV3xN10i23tkPkpH46MLCIMFNCaaKNavAXTF1RkqxawEPtnjnGZ6XKSInBKkiOA5BKS+aZiY3AvA==", - "dev": true, - "license": "BSD-3-Clause", - "dependencies": { - "html-escaper": "^2.0.0", - "istanbul-lib-report": "^3.0.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/istanbul-reports/node_modules/html-escaper": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/html-escaper/-/html-escaper-2.0.2.tgz", - "integrity": "sha512-H2iMtd0I4Mt5eYiapRdIDjp+XzelXQ0tFE4JS7YFwFevXXMmOp9myNrUvCg0D6ws8iqkRPBfKHgbwig1SmlLfg==", - "dev": true, - "license": "MIT" - }, - "node_modules/jackspeak": { - "version": "4.1.1", - "resolved": "https://registry.npmjs.org/jackspeak/-/jackspeak-4.1.1.tgz", - "integrity": "sha512-zptv57P3GpL+O0I7VdMJNBZCu+BPHVQUk55Ft8/QCJjTVxrnJHuVuX/0Bl2A6/+2oyR/ZMEuFKwmzqqZ/U5nPQ==", - "license": "BlueOak-1.0.0", - "dependencies": { - "@isaacs/cliui": "^8.0.2" - }, - "engines": { - "node": "20 || >=22" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/jest": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest/-/jest-30.2.0.tgz", - "integrity": "sha512-F26gjC0yWN8uAA5m5Ss8ZQf5nDHWGlN/xWZIh8S5SRbsEKBovwZhxGd6LJlbZYxBgCYOtreSUyb8hpXyGC5O4A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/core": "30.2.0", - "@jest/types": "30.2.0", - "import-local": "^3.2.0", - "jest-cli": "30.2.0" - }, - "bin": { - "jest": "bin/jest.js" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - }, - "peerDependencies": { - "node-notifier": "^8.0.1 || ^9.0.0 || ^10.0.0" - }, - "peerDependenciesMeta": { - "node-notifier": { - "optional": true - } - } - }, - "node_modules/jest-changed-files": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-changed-files/-/jest-changed-files-30.2.0.tgz", - "integrity": "sha512-L8lR1ChrRnSdfeOvTrwZMlnWV8G/LLjQ0nG9MBclwWZidA2N5FviRki0Bvh20WRMOX31/JYvzdqTJrk5oBdydQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "execa": "^5.1.1", - "jest-util": "30.2.0", - "p-limit": "^3.1.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-changed-files/node_modules/p-limit": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz", - "integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "yocto-queue": "^0.1.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/jest-changed-files/node_modules/yocto-queue": { - "version": "0.1.0", - "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz", - "integrity": "sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/jest-circus": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-circus/-/jest-circus-30.2.0.tgz", - "integrity": "sha512-Fh0096NC3ZkFx05EP2OXCxJAREVxj1BcW/i6EWqqymcgYKWjyyDpral3fMxVcHXg6oZM7iULer9wGRFvfpl+Tg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/environment": "30.2.0", - "@jest/expect": "30.2.0", - "@jest/test-result": "30.2.0", - "@jest/types": "30.2.0", - "@types/node": "*", - "chalk": "^4.1.2", - "co": "^4.6.0", - "dedent": "^1.6.0", - "is-generator-fn": "^2.1.0", - "jest-each": "30.2.0", - "jest-matcher-utils": "30.2.0", - "jest-message-util": "30.2.0", - "jest-runtime": "30.2.0", - "jest-snapshot": "30.2.0", - "jest-util": "30.2.0", - "p-limit": "^3.1.0", - "pretty-format": "30.2.0", - "pure-rand": "^7.0.0", - "slash": "^3.0.0", - "stack-utils": "^2.0.6" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-circus/node_modules/p-limit": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz", - "integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "yocto-queue": "^0.1.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/jest-circus/node_modules/yocto-queue": { - "version": "0.1.0", - "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz", - "integrity": "sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/jest-cli": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-cli/-/jest-cli-30.2.0.tgz", - "integrity": "sha512-Os9ukIvADX/A9sLt6Zse3+nmHtHaE6hqOsjQtNiugFTbKRHYIYtZXNGNK9NChseXy7djFPjndX1tL0sCTlfpAA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/core": "30.2.0", - "@jest/test-result": "30.2.0", - "@jest/types": "30.2.0", - "chalk": "^4.1.2", - "exit-x": "^0.2.2", - "import-local": "^3.2.0", - "jest-config": "30.2.0", - "jest-util": "30.2.0", - "jest-validate": "30.2.0", - "yargs": "^17.7.2" - }, - "bin": { - "jest": "bin/jest.js" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - }, - "peerDependencies": { - "node-notifier": "^8.0.1 || ^9.0.0 || ^10.0.0" - }, - "peerDependenciesMeta": { - "node-notifier": { - "optional": true - } - } - }, - "node_modules/jest-config": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-config/-/jest-config-30.2.0.tgz", - "integrity": "sha512-g4WkyzFQVWHtu6uqGmQR4CQxz/CH3yDSlhzXMWzNjDx843gYjReZnMRanjRCq5XZFuQrGDxgUaiYWE8BRfVckA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/core": "^7.27.4", - "@jest/get-type": "30.1.0", - "@jest/pattern": "30.0.1", - "@jest/test-sequencer": "30.2.0", - "@jest/types": "30.2.0", - "babel-jest": "30.2.0", - "chalk": "^4.1.2", - "ci-info": "^4.2.0", - "deepmerge": "^4.3.1", - "glob": "^10.3.10", - "graceful-fs": "^4.2.11", - "jest-circus": "30.2.0", - "jest-docblock": "30.2.0", - "jest-environment-node": "30.2.0", - "jest-regex-util": "30.0.1", - "jest-resolve": "30.2.0", - "jest-runner": "30.2.0", - "jest-util": "30.2.0", - "jest-validate": "30.2.0", - "micromatch": "^4.0.8", - "parse-json": "^5.2.0", - "pretty-format": "30.2.0", - "slash": "^3.0.0", - "strip-json-comments": "^3.1.1" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - }, - "peerDependencies": { - "@types/node": "*", - "esbuild-register": ">=3.4.0", - "ts-node": ">=9.0.0" - }, - "peerDependenciesMeta": { - "@types/node": { - "optional": true - }, - "esbuild-register": { - "optional": true - }, - "ts-node": { - "optional": true - } - } - }, - "node_modules/jest-config/node_modules/brace-expansion": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.2.tgz", - "integrity": "sha512-Jt0vHyM+jmUBqojB7E1NIYadt0vI0Qxjxd2TErW94wDz+E2LAm5vKMXXwg6ZZBTHPuUlDgQHKXvjGBdfcF1ZDQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "balanced-match": "^1.0.0" - } - }, - "node_modules/jest-config/node_modules/glob": { - "version": "10.5.0", - "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz", - "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==", - "dev": true, - "license": "ISC", - "dependencies": { - "foreground-child": "^3.1.0", - "jackspeak": "^3.1.2", - "minimatch": "^9.0.4", - "minipass": "^7.1.2", - "package-json-from-dist": "^1.0.0", - "path-scurry": "^1.11.1" - }, - "bin": { - "glob": "dist/esm/bin.mjs" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/jest-config/node_modules/jackspeak": { - "version": "3.4.3", - "resolved": "https://registry.npmjs.org/jackspeak/-/jackspeak-3.4.3.tgz", - "integrity": "sha512-OGlZQpz2yfahA/Rd1Y8Cd9SIEsqvXkLVoSw/cgwhnhFMDbsQFeZYoJJ7bIZBS9BcamUW96asq/npPWugM+RQBw==", - "dev": true, - "license": "BlueOak-1.0.0", - "dependencies": { - "@isaacs/cliui": "^8.0.2" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - }, - "optionalDependencies": { - "@pkgjs/parseargs": "^0.11.0" - } - }, - "node_modules/jest-config/node_modules/lru-cache": { - "version": "10.4.3", - "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-10.4.3.tgz", - "integrity": "sha512-JNAzZcXrCt42VGLuYz0zfAzDfAvJWW6AfYlDBQyDV5DClI2m5sAmK+OIO7s59XfsRsWHp02jAJrRadPRGTt6SQ==", - "dev": true, - "license": "ISC" - }, - "node_modules/jest-config/node_modules/minimatch": { - "version": "9.0.5", - "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz", - "integrity": "sha512-G6T0ZX48xgozx7587koeX9Ys2NYy6Gmv//P89sEte9V9whIapMNF4idKxnW2QtCcLiTWlb/wfCabAtAFWhhBow==", - "dev": true, - "license": "ISC", - "dependencies": { - "brace-expansion": "^2.0.1" - }, - "engines": { - "node": ">=16 || 14 >=14.17" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/jest-config/node_modules/path-scurry": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/path-scurry/-/path-scurry-1.11.1.tgz", - "integrity": "sha512-Xa4Nw17FS9ApQFJ9umLiJS4orGjm7ZzwUrwamcGQuHSzDyth9boKDaycYdDcZDuqYATXw4HFXgaqWTctW/v1HA==", - "dev": true, - "license": "BlueOak-1.0.0", - "dependencies": { - "lru-cache": "^10.2.0", - "minipass": "^5.0.0 || ^6.0.2 || ^7.0.0" - }, - "engines": { - "node": ">=16 || 14 >=14.18" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/jest-diff": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-diff/-/jest-diff-30.2.0.tgz", - "integrity": "sha512-dQHFo3Pt4/NLlG5z4PxZ/3yZTZ1C7s9hveiOj+GCN+uT109NC2QgsoVZsVOAvbJ3RgKkvyLGXZV9+piDpWbm6A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/diff-sequences": "30.0.1", - "@jest/get-type": "30.1.0", - "chalk": "^4.1.2", - "pretty-format": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-docblock": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-docblock/-/jest-docblock-30.2.0.tgz", - "integrity": "sha512-tR/FFgZKS1CXluOQzZvNH3+0z9jXr3ldGSD8bhyuxvlVUwbeLOGynkunvlTMxchC5urrKndYiwCFC0DLVjpOCA==", - "dev": true, - "license": "MIT", - "dependencies": { - "detect-newline": "^3.1.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-each": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-each/-/jest-each-30.2.0.tgz", - "integrity": "sha512-lpWlJlM7bCUf1mfmuqTA8+j2lNURW9eNafOy99knBM01i5CQeY5UH1vZjgT9071nDJac1M4XsbyI44oNOdhlDQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/get-type": "30.1.0", - "@jest/types": "30.2.0", - "chalk": "^4.1.2", - "jest-util": "30.2.0", - "pretty-format": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-environment-node": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-environment-node/-/jest-environment-node-30.2.0.tgz", - "integrity": "sha512-ElU8v92QJ9UrYsKrxDIKCxu6PfNj4Hdcktcn0JX12zqNdqWHB0N+hwOnnBBXvjLd2vApZtuLUGs1QSY+MsXoNA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/environment": "30.2.0", - "@jest/fake-timers": "30.2.0", - "@jest/types": "30.2.0", - "@types/node": "*", - "jest-mock": "30.2.0", - "jest-util": "30.2.0", - "jest-validate": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-haste-map": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-haste-map/-/jest-haste-map-30.2.0.tgz", - "integrity": "sha512-sQA/jCb9kNt+neM0anSj6eZhLZUIhQgwDt7cPGjumgLM4rXsfb9kpnlacmvZz3Q5tb80nS+oG/if+NBKrHC+Xw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/types": "30.2.0", - "@types/node": "*", - "anymatch": "^3.1.3", - "fb-watchman": "^2.0.2", - "graceful-fs": "^4.2.11", - "jest-regex-util": "30.0.1", - "jest-util": "30.2.0", - "jest-worker": "30.2.0", - "micromatch": "^4.0.8", - "walker": "^1.0.8" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - }, - "optionalDependencies": { - "fsevents": "^2.3.3" - } - }, - "node_modules/jest-leak-detector": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-leak-detector/-/jest-leak-detector-30.2.0.tgz", - "integrity": "sha512-M6jKAjyzjHG0SrQgwhgZGy9hFazcudwCNovY/9HPIicmNSBuockPSedAP9vlPK6ONFJ1zfyH/M2/YYJxOz5cdQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/get-type": "30.1.0", - "pretty-format": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-matcher-utils": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-matcher-utils/-/jest-matcher-utils-30.2.0.tgz", - "integrity": "sha512-dQ94Nq4dbzmUWkQ0ANAWS9tBRfqCrn0bV9AMYdOi/MHW726xn7eQmMeRTpX2ViC00bpNaWXq+7o4lIQ3AX13Hg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/get-type": "30.1.0", - "chalk": "^4.1.2", - "jest-diff": "30.2.0", - "pretty-format": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-message-util": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-message-util/-/jest-message-util-30.2.0.tgz", - "integrity": "sha512-y4DKFLZ2y6DxTWD4cDe07RglV88ZiNEdlRfGtqahfbIjfsw1nMCPx49Uev4IA/hWn3sDKyAnSPwoYSsAEdcimw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/code-frame": "^7.27.1", - "@jest/types": "30.2.0", - "@types/stack-utils": "^2.0.3", - "chalk": "^4.1.2", - "graceful-fs": "^4.2.11", - "micromatch": "^4.0.8", - "pretty-format": "30.2.0", - "slash": "^3.0.0", - "stack-utils": "^2.0.6" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-mock": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-mock/-/jest-mock-30.2.0.tgz", - "integrity": "sha512-JNNNl2rj4b5ICpmAcq+WbLH83XswjPbjH4T7yvGzfAGCPh1rw+xVNbtk+FnRslvt9lkCcdn9i1oAoKUuFsOxRw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/types": "30.2.0", - "@types/node": "*", - "jest-util": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-pnp-resolver": { - "version": "1.2.3", - "resolved": "https://registry.npmjs.org/jest-pnp-resolver/-/jest-pnp-resolver-1.2.3.tgz", - "integrity": "sha512-+3NpwQEnRoIBtx4fyhblQDPgJI0H1IEIkX7ShLUjPGA7TtUTvI1oiKi3SR4oBR0hQhQR80l4WAe5RrXBwWMA8w==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - }, - "peerDependencies": { - "jest-resolve": "*" - }, - "peerDependenciesMeta": { - "jest-resolve": { - "optional": true - } - } - }, - "node_modules/jest-regex-util": { - "version": "30.0.1", - "resolved": "https://registry.npmjs.org/jest-regex-util/-/jest-regex-util-30.0.1.tgz", - "integrity": "sha512-jHEQgBXAgc+Gh4g0p3bCevgRCVRkB4VB70zhoAE48gxeSr1hfUOsM/C2WoJgVL7Eyg//hudYENbm3Ne+/dRVVA==", - "dev": true, - "license": "MIT", - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-resolve": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-resolve/-/jest-resolve-30.2.0.tgz", - "integrity": "sha512-TCrHSxPlx3tBY3hWNtRQKbtgLhsXa1WmbJEqBlTBrGafd5fiQFByy2GNCEoGR+Tns8d15GaL9cxEzKOO3GEb2A==", - "dev": true, - "license": "MIT", - "dependencies": { - "chalk": "^4.1.2", - "graceful-fs": "^4.2.11", - "jest-haste-map": "30.2.0", - "jest-pnp-resolver": "^1.2.3", - "jest-util": "30.2.0", - "jest-validate": "30.2.0", - "slash": "^3.0.0", - "unrs-resolver": "^1.7.11" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-resolve-dependencies": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-resolve-dependencies/-/jest-resolve-dependencies-30.2.0.tgz", - "integrity": "sha512-xTOIGug/0RmIe3mmCqCT95yO0vj6JURrn1TKWlNbhiAefJRWINNPgwVkrVgt/YaerPzY3iItufd80v3lOrFJ2w==", - "dev": true, - "license": "MIT", - "dependencies": { - "jest-regex-util": "30.0.1", - "jest-snapshot": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-runner": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-runner/-/jest-runner-30.2.0.tgz", - "integrity": "sha512-PqvZ2B2XEyPEbclp+gV6KO/F1FIFSbIwewRgmROCMBo/aZ6J1w8Qypoj2pEOcg3G2HzLlaP6VUtvwCI8dM3oqQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/console": "30.2.0", - "@jest/environment": "30.2.0", - "@jest/test-result": "30.2.0", - "@jest/transform": "30.2.0", - "@jest/types": "30.2.0", - "@types/node": "*", - "chalk": "^4.1.2", - "emittery": "^0.13.1", - "exit-x": "^0.2.2", - "graceful-fs": "^4.2.11", - "jest-docblock": "30.2.0", - "jest-environment-node": "30.2.0", - "jest-haste-map": "30.2.0", - "jest-leak-detector": "30.2.0", - "jest-message-util": "30.2.0", - "jest-resolve": "30.2.0", - "jest-runtime": "30.2.0", - "jest-util": "30.2.0", - "jest-watcher": "30.2.0", - "jest-worker": "30.2.0", - "p-limit": "^3.1.0", - "source-map-support": "0.5.13" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-runner/node_modules/p-limit": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz", - "integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "yocto-queue": "^0.1.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/jest-runner/node_modules/yocto-queue": { - "version": "0.1.0", - "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz", - "integrity": "sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/jest-runtime": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-runtime/-/jest-runtime-30.2.0.tgz", - "integrity": "sha512-p1+GVX/PJqTucvsmERPMgCPvQJpFt4hFbM+VN3n8TMo47decMUcJbt+rgzwrEme0MQUA/R+1de2axftTHkKckg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/environment": "30.2.0", - "@jest/fake-timers": "30.2.0", - "@jest/globals": "30.2.0", - "@jest/source-map": "30.0.1", - "@jest/test-result": "30.2.0", - "@jest/transform": "30.2.0", - "@jest/types": "30.2.0", - "@types/node": "*", - "chalk": "^4.1.2", - "cjs-module-lexer": "^2.1.0", - "collect-v8-coverage": "^1.0.2", - "glob": "^10.3.10", - "graceful-fs": "^4.2.11", - "jest-haste-map": "30.2.0", - "jest-message-util": "30.2.0", - "jest-mock": "30.2.0", - "jest-regex-util": "30.0.1", - "jest-resolve": "30.2.0", - "jest-snapshot": "30.2.0", - "jest-util": "30.2.0", - "slash": "^3.0.0", - "strip-bom": "^4.0.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-runtime/node_modules/brace-expansion": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.2.tgz", - "integrity": "sha512-Jt0vHyM+jmUBqojB7E1NIYadt0vI0Qxjxd2TErW94wDz+E2LAm5vKMXXwg6ZZBTHPuUlDgQHKXvjGBdfcF1ZDQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "balanced-match": "^1.0.0" - } - }, - "node_modules/jest-runtime/node_modules/glob": { - "version": "10.5.0", - "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz", - "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==", - "dev": true, - "license": "ISC", - "dependencies": { - "foreground-child": "^3.1.0", - "jackspeak": "^3.1.2", - "minimatch": "^9.0.4", - "minipass": "^7.1.2", - "package-json-from-dist": "^1.0.0", - "path-scurry": "^1.11.1" - }, - "bin": { - "glob": "dist/esm/bin.mjs" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/jest-runtime/node_modules/jackspeak": { - "version": "3.4.3", - "resolved": "https://registry.npmjs.org/jackspeak/-/jackspeak-3.4.3.tgz", - "integrity": "sha512-OGlZQpz2yfahA/Rd1Y8Cd9SIEsqvXkLVoSw/cgwhnhFMDbsQFeZYoJJ7bIZBS9BcamUW96asq/npPWugM+RQBw==", - "dev": true, - "license": "BlueOak-1.0.0", - "dependencies": { - "@isaacs/cliui": "^8.0.2" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - }, - "optionalDependencies": { - "@pkgjs/parseargs": "^0.11.0" - } - }, - "node_modules/jest-runtime/node_modules/lru-cache": { - "version": "10.4.3", - "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-10.4.3.tgz", - "integrity": "sha512-JNAzZcXrCt42VGLuYz0zfAzDfAvJWW6AfYlDBQyDV5DClI2m5sAmK+OIO7s59XfsRsWHp02jAJrRadPRGTt6SQ==", - "dev": true, - "license": "ISC" - }, - "node_modules/jest-runtime/node_modules/minimatch": { - "version": "9.0.5", - "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz", - "integrity": "sha512-G6T0ZX48xgozx7587koeX9Ys2NYy6Gmv//P89sEte9V9whIapMNF4idKxnW2QtCcLiTWlb/wfCabAtAFWhhBow==", - "dev": true, - "license": "ISC", - "dependencies": { - "brace-expansion": "^2.0.1" - }, - "engines": { - "node": ">=16 || 14 >=14.17" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/jest-runtime/node_modules/path-scurry": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/path-scurry/-/path-scurry-1.11.1.tgz", - "integrity": "sha512-Xa4Nw17FS9ApQFJ9umLiJS4orGjm7ZzwUrwamcGQuHSzDyth9boKDaycYdDcZDuqYATXw4HFXgaqWTctW/v1HA==", - "dev": true, - "license": "BlueOak-1.0.0", - "dependencies": { - "lru-cache": "^10.2.0", - "minipass": "^5.0.0 || ^6.0.2 || ^7.0.0" - }, - "engines": { - "node": ">=16 || 14 >=14.18" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/jest-snapshot": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-snapshot/-/jest-snapshot-30.2.0.tgz", - "integrity": "sha512-5WEtTy2jXPFypadKNpbNkZ72puZCa6UjSr/7djeecHWOu7iYhSXSnHScT8wBz3Rn8Ena5d5RYRcsyKIeqG1IyA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/core": "^7.27.4", - "@babel/generator": "^7.27.5", - "@babel/plugin-syntax-jsx": "^7.27.1", - "@babel/plugin-syntax-typescript": "^7.27.1", - "@babel/types": "^7.27.3", - "@jest/expect-utils": "30.2.0", - "@jest/get-type": "30.1.0", - "@jest/snapshot-utils": "30.2.0", - "@jest/transform": "30.2.0", - "@jest/types": "30.2.0", - "babel-preset-current-node-syntax": "^1.2.0", - "chalk": "^4.1.2", - "expect": "30.2.0", - "graceful-fs": "^4.2.11", - "jest-diff": "30.2.0", - "jest-matcher-utils": "30.2.0", - "jest-message-util": "30.2.0", - "jest-util": "30.2.0", - "pretty-format": "30.2.0", - "semver": "^7.7.2", - "synckit": "^0.11.8" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-util": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-util/-/jest-util-30.2.0.tgz", - "integrity": "sha512-QKNsM0o3Xe6ISQU869e+DhG+4CK/48aHYdJZGlFQVTjnbvgpcKyxpzk29fGiO7i/J8VENZ+d2iGnSsvmuHywlA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/types": "30.2.0", - "@types/node": "*", - "chalk": "^4.1.2", - "ci-info": "^4.2.0", - "graceful-fs": "^4.2.11", - "picomatch": "^4.0.2" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-validate": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-validate/-/jest-validate-30.2.0.tgz", - "integrity": "sha512-FBGWi7dP2hpdi8nBoWxSsLvBFewKAg0+uSQwBaof4Y4DPgBabXgpSYC5/lR7VmnIlSpASmCi/ntRWPbv7089Pw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/get-type": "30.1.0", - "@jest/types": "30.2.0", - "camelcase": "^6.3.0", - "chalk": "^4.1.2", - "leven": "^3.1.0", - "pretty-format": "30.2.0" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-watcher": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-watcher/-/jest-watcher-30.2.0.tgz", - "integrity": "sha512-PYxa28dxJ9g777pGm/7PrbnMeA0Jr7osHP9bS7eJy9DuAjMgdGtxgf0uKMyoIsTWAkIbUW5hSDdJ3urmgXBqxg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/test-result": "30.2.0", - "@jest/types": "30.2.0", - "@types/node": "*", - "ansi-escapes": "^4.3.2", - "chalk": "^4.1.2", - "emittery": "^0.13.1", - "jest-util": "30.2.0", - "string-length": "^4.0.2" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-worker": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/jest-worker/-/jest-worker-30.2.0.tgz", - "integrity": "sha512-0Q4Uk8WF7BUwqXHuAjc23vmopWJw5WH7w2tqBoUOZpOjW/ZnR44GXXd1r82RvnmI2GZge3ivrYXk/BE2+VtW2g==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/node": "*", - "@ungap/structured-clone": "^1.3.0", - "jest-util": "30.2.0", - "merge-stream": "^2.0.0", - "supports-color": "^8.1.1" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/jest-worker/node_modules/supports-color": { - "version": "8.1.1", - "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-8.1.1.tgz", - "integrity": "sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "has-flag": "^4.0.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/chalk/supports-color?sponsor=1" - } - }, - "node_modules/js-tokens": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz", - "integrity": "sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/js-yaml": { - "version": "4.1.1", - "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.1.tgz", - "integrity": "sha512-qQKT4zQxXl8lLwBtHMWwaTcGfFOZviOJet3Oy/xmGk2gZH677CJM9EvtfdSkgWcATZhj/55JZ0rmy3myCT5lsA==", - "license": "MIT", - "dependencies": { - "argparse": "^2.0.1" - }, - "bin": { - "js-yaml": "bin/js-yaml.js" - } - }, - "node_modules/jsesc": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/jsesc/-/jsesc-3.1.0.tgz", - "integrity": "sha512-/sM3dO2FOzXjKQhJuo0Q173wf2KOo8t4I8vHy6lF9poUp7bKT0/NHE8fPX23PwfhnykfqnC2xRxOnVw5XuGIaA==", - "dev": true, - "license": "MIT", - "bin": { - "jsesc": "bin/jsesc" - }, - "engines": { - "node": ">=6" - } - }, - "node_modules/json-buffer": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/json-buffer/-/json-buffer-3.0.1.tgz", - "integrity": "sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/json-parse-even-better-errors": { - "version": "2.3.1", - "resolved": "https://registry.npmjs.org/json-parse-even-better-errors/-/json-parse-even-better-errors-2.3.1.tgz", - "integrity": "sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==", - "dev": true, - "license": "MIT" - }, - "node_modules/json-schema-traverse": { - "version": "0.4.1", - "resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz", - "integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==", - "dev": true, - "license": "MIT" - }, - "node_modules/json-stable-stringify-without-jsonify": { - "version": "1.0.1", - "resolved": "https://registry.npmjs.org/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz", - "integrity": "sha512-Bdboy+l7tA3OGW6FjyFHWkP5LuByj1Tk33Ljyq0axyzdk9//JSi2u3fP1QSmd1KNwq6VOKYGlAu87CisVir6Pw==", - "dev": true, - "license": "MIT" - }, - "node_modules/json5": { - "version": "2.2.3", - "resolved": "https://registry.npmjs.org/json5/-/json5-2.2.3.tgz", - "integrity": "sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==", - "dev": true, - "license": "MIT", - "bin": { - "json5": "lib/cli.js" - }, - "engines": { - "node": ">=6" - } - }, - "node_modules/jsonc-parser": { - "version": "3.3.1", - "resolved": "https://registry.npmjs.org/jsonc-parser/-/jsonc-parser-3.3.1.tgz", - "integrity": "sha512-HUgH65KyejrUFPvHFPbqOY0rsFip3Bo5wb4ngvdi1EpCYWUQDC5V+Y7mZws+DLkr4M//zQJoanu1SP+87Dv1oQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/jsonfile": { - "version": "6.2.0", - "resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-6.2.0.tgz", - "integrity": "sha512-FGuPw30AdOIUTRMC2OMRtQV+jkVj2cfPqSeWXv1NEAJ1qZ5zb1X6z1mFhbfOB/iy3ssJCD+3KuZ8r8C3uVFlAg==", - "license": "MIT", - "dependencies": { - "universalify": "^2.0.0" - }, - "optionalDependencies": { - "graceful-fs": "^4.1.6" - } - }, - "node_modules/katex": { - "version": "0.16.28", - "resolved": "https://registry.npmjs.org/katex/-/katex-0.16.28.tgz", - "integrity": "sha512-YHzO7721WbmAL6Ov1uzN/l5mY5WWWhJBSW+jq4tkfZfsxmo1hu6frS0EOswvjBUnWE6NtjEs48SFn5CQESRLZg==", - "dev": true, - "funding": [ - "https://opencollective.com/katex", - "https://github.com/sponsors/katex" - ], - "license": "MIT", - "dependencies": { - "commander": "^8.3.0" - }, - "bin": { - "katex": "cli.js" - } - }, - "node_modules/katex/node_modules/commander": { - "version": "8.3.0", - "resolved": "https://registry.npmjs.org/commander/-/commander-8.3.0.tgz", - "integrity": "sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 12" - } - }, - "node_modules/keyv": { - "version": "4.5.4", - "resolved": "https://registry.npmjs.org/keyv/-/keyv-4.5.4.tgz", - "integrity": "sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==", - "dev": true, - "license": "MIT", - "dependencies": { - "json-buffer": "3.0.1" - } - }, - "node_modules/kleur": { - "version": "3.0.3", - "resolved": "https://registry.npmjs.org/kleur/-/kleur-3.0.3.tgz", - "integrity": "sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/klona": { - "version": "2.0.6", - "resolved": "https://registry.npmjs.org/klona/-/klona-2.0.6.tgz", - "integrity": "sha512-dhG34DXATL5hSxJbIexCft8FChFXtmskoZYnoPWjXQuebWYCNkVeV3KkGegCK9CP1oswI/vQibS2GY7Em/sJJA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 8" - } - }, - "node_modules/leven": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/leven/-/leven-3.1.0.tgz", - "integrity": "sha512-qsda+H8jTaUaN/x5vzW2rzc+8Rw4TAQ/4KjB46IwK5VH+IlVeeeje/EoZRpiXvIqjFgK84QffqPztGI3VBLG1A==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/levn": { - "version": "0.4.1", - "resolved": "https://registry.npmjs.org/levn/-/levn-0.4.1.tgz", - "integrity": "sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "prelude-ls": "^1.2.1", - "type-check": "~0.4.0" - }, - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/lines-and-columns": { - "version": "1.2.4", - "resolved": "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.2.4.tgz", - "integrity": "sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==", - "dev": true, - "license": "MIT" - }, - "node_modules/linkify-it": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/linkify-it/-/linkify-it-5.0.0.tgz", - "integrity": "sha512-5aHCbzQRADcdP+ATqnDuhhJ/MRIqDkZX5pyjFHRRysS8vZ5AbqGEoFIb6pYHPZ+L/OC2Lc+xT8uHVVR5CAK/wQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "uc.micro": "^2.0.0" - } - }, - "node_modules/lint-staged": { - "version": "16.2.7", - "resolved": "https://registry.npmjs.org/lint-staged/-/lint-staged-16.2.7.tgz", - "integrity": "sha512-lDIj4RnYmK7/kXMya+qJsmkRFkGolciXjrsZ6PC25GdTfWOAWetR0ZbsNXRAj1EHHImRSalc+whZFg56F5DVow==", - "dev": true, - "license": "MIT", - "dependencies": { - "commander": "^14.0.2", - "listr2": "^9.0.5", - "micromatch": "^4.0.8", - "nano-spawn": "^2.0.0", - "pidtree": "^0.6.0", - "string-argv": "^0.3.2", - "yaml": "^2.8.1" - }, - "bin": { - "lint-staged": "bin/lint-staged.js" - }, - "engines": { - "node": ">=20.17" - }, - "funding": { - "url": "https://opencollective.com/lint-staged" - } - }, - "node_modules/listr2": { - "version": "9.0.5", - "resolved": "https://registry.npmjs.org/listr2/-/listr2-9.0.5.tgz", - "integrity": "sha512-ME4Fb83LgEgwNw96RKNvKV4VTLuXfoKudAmm2lP8Kk87KaMK0/Xrx/aAkMWmT8mDb+3MlFDspfbCs7adjRxA2g==", - "dev": true, - "license": "MIT", - "dependencies": { - "cli-truncate": "^5.0.0", - "colorette": "^2.0.20", - "eventemitter3": "^5.0.1", - "log-update": "^6.1.0", - "rfdc": "^1.4.1", - "wrap-ansi": "^9.0.0" - }, - "engines": { - "node": ">=20.0.0" - } - }, - "node_modules/listr2/node_modules/ansi-styles": { - "version": "6.2.3", - "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-6.2.3.tgz", - "integrity": "sha512-4Dj6M28JB+oAH8kFkTLUo+a2jwOFkuqb3yucU0CANcRRUbxS0cP0nZYCGjcc3BNXwRIsUVmDGgzawme7zvJHvg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/chalk/ansi-styles?sponsor=1" - } - }, - "node_modules/listr2/node_modules/emoji-regex": { - "version": "10.6.0", - "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-10.6.0.tgz", - "integrity": "sha512-toUI84YS5YmxW219erniWD0CIVOo46xGKColeNQRgOzDorgBi1v4D71/OFzgD9GO2UGKIv1C3Sp8DAn0+j5w7A==", - "dev": true, - "license": "MIT" - }, - "node_modules/listr2/node_modules/string-width": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/string-width/-/string-width-7.2.0.tgz", - "integrity": "sha512-tsaTIkKW9b4N+AEj+SVA+WhJzV7/zMhcSu78mLKWSk7cXMOSHsBKFWUs0fWwq8QyK3MgJBQRX6Gbi4kYbdvGkQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "emoji-regex": "^10.3.0", - "get-east-asian-width": "^1.0.0", - "strip-ansi": "^7.1.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/listr2/node_modules/wrap-ansi": { - "version": "9.0.2", - "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-9.0.2.tgz", - "integrity": "sha512-42AtmgqjV+X1VpdOfyTGOYRi0/zsoLqtXQckTmqTeybT+BDIbM/Guxo7x3pE2vtpr1ok6xRqM9OpBe+Jyoqyww==", - "dev": true, - "license": "MIT", - "dependencies": { - "ansi-styles": "^6.2.1", - "string-width": "^7.0.0", - "strip-ansi": "^7.1.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/chalk/wrap-ansi?sponsor=1" - } - }, - "node_modules/locate-path": { - "version": "6.0.0", - "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz", - "integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==", - "dev": true, - "license": "MIT", - "dependencies": { - "p-locate": "^5.0.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/lodash.iteratee": { - "version": "4.7.0", - "resolved": "https://registry.npmjs.org/lodash.iteratee/-/lodash.iteratee-4.7.0.tgz", - "integrity": "sha512-yv3cSQZmfpbIKo4Yo45B1taEvxjNvcpF1CEOc0Y6dEyvhPIfEJE3twDwPgWTPQubcSgXyBwBKG6wpQvWMDOf6Q==", - "license": "MIT" - }, - "node_modules/lodash.merge": { - "version": "4.6.2", - "resolved": "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz", - "integrity": "sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/log-update": { - "version": "6.1.0", - "resolved": "https://registry.npmjs.org/log-update/-/log-update-6.1.0.tgz", - "integrity": "sha512-9ie8ItPR6tjY5uYJh8K/Zrv/RMZ5VOlOWvtZdEHYSTFKZfIBPQa9tOAEeAWhd+AnIneLJ22w5fjOYtoutpWq5w==", - "dev": true, - "license": "MIT", - "dependencies": { - "ansi-escapes": "^7.0.0", - "cli-cursor": "^5.0.0", - "slice-ansi": "^7.1.0", - "strip-ansi": "^7.1.0", - "wrap-ansi": "^9.0.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/log-update/node_modules/ansi-escapes": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-7.2.0.tgz", - "integrity": "sha512-g6LhBsl+GBPRWGWsBtutpzBYuIIdBkLEvad5C/va/74Db018+5TZiyA26cZJAr3Rft5lprVqOIPxf5Vid6tqAw==", - "dev": true, - "license": "MIT", - "dependencies": { - "environment": "^1.0.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/log-update/node_modules/ansi-styles": { - "version": "6.2.3", - "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-6.2.3.tgz", - "integrity": "sha512-4Dj6M28JB+oAH8kFkTLUo+a2jwOFkuqb3yucU0CANcRRUbxS0cP0nZYCGjcc3BNXwRIsUVmDGgzawme7zvJHvg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/chalk/ansi-styles?sponsor=1" - } - }, - "node_modules/log-update/node_modules/emoji-regex": { - "version": "10.6.0", - "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-10.6.0.tgz", - "integrity": "sha512-toUI84YS5YmxW219erniWD0CIVOo46xGKColeNQRgOzDorgBi1v4D71/OFzgD9GO2UGKIv1C3Sp8DAn0+j5w7A==", - "dev": true, - "license": "MIT" - }, - "node_modules/log-update/node_modules/string-width": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/string-width/-/string-width-7.2.0.tgz", - "integrity": "sha512-tsaTIkKW9b4N+AEj+SVA+WhJzV7/zMhcSu78mLKWSk7cXMOSHsBKFWUs0fWwq8QyK3MgJBQRX6Gbi4kYbdvGkQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "emoji-regex": "^10.3.0", - "get-east-asian-width": "^1.0.0", - "strip-ansi": "^7.1.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/log-update/node_modules/wrap-ansi": { - "version": "9.0.2", - "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-9.0.2.tgz", - "integrity": "sha512-42AtmgqjV+X1VpdOfyTGOYRi0/zsoLqtXQckTmqTeybT+BDIbM/Guxo7x3pE2vtpr1ok6xRqM9OpBe+Jyoqyww==", - "dev": true, - "license": "MIT", - "dependencies": { - "ansi-styles": "^6.2.1", - "string-width": "^7.0.0", - "strip-ansi": "^7.1.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/chalk/wrap-ansi?sponsor=1" - } - }, - "node_modules/longest-streak": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/longest-streak/-/longest-streak-3.1.0.tgz", - "integrity": "sha512-9Ri+o0JYgehTaVBBDoMqIl8GXtbWg711O3srftcHhZ0dqnETqLaoIK0x17fUw9rFSlK/0NlsKe0Ahhyl5pXE2g==", - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/lru-cache": { - "version": "5.1.1", - "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-5.1.1.tgz", - "integrity": "sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==", - "dev": true, - "license": "ISC", - "dependencies": { - "yallist": "^3.0.2" - } - }, - "node_modules/magic-string": { - "version": "0.30.21", - "resolved": "https://registry.npmjs.org/magic-string/-/magic-string-0.30.21.tgz", - "integrity": "sha512-vd2F4YUyEXKGcLHoq+TEyCjxueSeHnFxyyjNp80yg0XV4vUhnDer/lvvlqM/arB5bXQN5K2/3oinyCRyx8T2CQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jridgewell/sourcemap-codec": "^1.5.5" - } - }, - "node_modules/magicast": { - "version": "0.5.1", - "resolved": "https://registry.npmjs.org/magicast/-/magicast-0.5.1.tgz", - "integrity": "sha512-xrHS24IxaLrvuo613F719wvOIv9xPHFWQHuvGUBmPnCA/3MQxKI3b+r7n1jAoDHmsbC5bRhTZYR77invLAxVnw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/parser": "^7.28.5", - "@babel/types": "^7.28.5", - "source-map-js": "^1.2.1" - } - }, - "node_modules/make-dir": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/make-dir/-/make-dir-4.0.0.tgz", - "integrity": "sha512-hXdUTZYIVOt1Ex//jAQi+wTZZpUpwBj/0QsOzqegb3rGMMeJiSEu5xLHnYfBrRV4RH2+OCSOO95Is/7x1WJ4bw==", - "dev": true, - "license": "MIT", - "dependencies": { - "semver": "^7.5.3" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/makeerror": { - "version": "1.0.12", - "resolved": "https://registry.npmjs.org/makeerror/-/makeerror-1.0.12.tgz", - "integrity": "sha512-JmqCvUhmt43madlpFzG4BQzG2Z3m6tvQDNKdClZnO3VbIudJYmxsT0FNJMeiB2+JTSlTQTSbU8QdesVmwJcmLg==", - "dev": true, - "license": "BSD-3-Clause", - "dependencies": { - "tmpl": "1.0.5" - } - }, - "node_modules/markdown-extensions": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/markdown-extensions/-/markdown-extensions-2.0.0.tgz", - "integrity": "sha512-o5vL7aDWatOTX8LzaS1WMoaoxIiLRQJuIKKe2wAw6IeULDHaqbiqiggmx+pKvZDb1Sj+pE46Sn1T7lCqfFtg1Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=16" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/markdown-it": { - "version": "14.1.0", - "resolved": "https://registry.npmjs.org/markdown-it/-/markdown-it-14.1.0.tgz", - "integrity": "sha512-a54IwgWPaeBCAAsv13YgmALOF1elABB08FxO9i+r4VFk5Vl4pKokRPeX8u5TCgSsPi6ec1otfLjdOpVcgbpshg==", - "dev": true, - "license": "MIT", - "dependencies": { - "argparse": "^2.0.1", - "entities": "^4.4.0", - "linkify-it": "^5.0.0", - "mdurl": "^2.0.0", - "punycode.js": "^2.3.1", - "uc.micro": "^2.1.0" - }, - "bin": { - "markdown-it": "bin/markdown-it.mjs" - } - }, - "node_modules/markdown-table": { - "version": "3.0.4", - "resolved": "https://registry.npmjs.org/markdown-table/-/markdown-table-3.0.4.tgz", - "integrity": "sha512-wiYz4+JrLyb/DqW2hkFJxP7Vd7JuTDm77fvbM8VfEQdmSMqcImWeeRbHwZjBjIFki/VaMK2BhFi7oUUZeM5bqw==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/markdownlint": { - "version": "0.39.0", - "resolved": "https://registry.npmjs.org/markdownlint/-/markdownlint-0.39.0.tgz", - "integrity": "sha512-Xt/oY7bAiHwukL1iru2np5LIkhwD19Y7frlsiDILK62v3jucXCD6JXlZlwMG12HZOR+roHIVuJZrfCkOhp6k3g==", - "dev": true, - "license": "MIT", - "dependencies": { - "micromark": "4.0.2", - "micromark-core-commonmark": "2.0.3", - "micromark-extension-directive": "4.0.0", - "micromark-extension-gfm-autolink-literal": "2.1.0", - "micromark-extension-gfm-footnote": "2.1.0", - "micromark-extension-gfm-table": "2.1.1", - "micromark-extension-math": "3.1.0", - "micromark-util-types": "2.0.2" - }, - "engines": { - "node": ">=20" - }, - "funding": { - "url": "https://github.com/sponsors/DavidAnson" - } - }, - "node_modules/markdownlint-cli2": { - "version": "0.19.1", - "resolved": "https://registry.npmjs.org/markdownlint-cli2/-/markdownlint-cli2-0.19.1.tgz", - "integrity": "sha512-p3JTemJJbkiMjXEMiFwgm0v6ym5g8K+b2oDny+6xdl300tUKySxvilJQLSea48C6OaYNmO30kH9KxpiAg5bWJw==", - "dev": true, - "license": "MIT", - "dependencies": { - "globby": "15.0.0", - "js-yaml": "4.1.1", - "jsonc-parser": "3.3.1", - "markdown-it": "14.1.0", - "markdownlint": "0.39.0", - "markdownlint-cli2-formatter-default": "0.0.6", - "micromatch": "4.0.8" - }, - "bin": { - "markdownlint-cli2": "markdownlint-cli2-bin.mjs" - }, - "engines": { - "node": ">=20" - }, - "funding": { - "url": "https://github.com/sponsors/DavidAnson" - } - }, - "node_modules/markdownlint-cli2-formatter-default": { - "version": "0.0.6", - "resolved": "https://registry.npmjs.org/markdownlint-cli2-formatter-default/-/markdownlint-cli2-formatter-default-0.0.6.tgz", - "integrity": "sha512-VVDGKsq9sgzu378swJ0fcHfSicUnMxnL8gnLm/Q4J/xsNJ4e5bA6lvAz7PCzIl0/No0lHyaWdqVD2jotxOSFMQ==", - "dev": true, - "license": "MIT", - "funding": { - "url": "https://github.com/sponsors/DavidAnson" - }, - "peerDependencies": { - "markdownlint-cli2": ">=0.0.4" - } - }, - "node_modules/mdast-util-definitions": { - "version": "6.0.0", - "resolved": "https://registry.npmjs.org/mdast-util-definitions/-/mdast-util-definitions-6.0.0.tgz", - "integrity": "sha512-scTllyX6pnYNZH/AIp/0ePz6s4cZtARxImwoPJ7kS42n+MnVsI4XbnG6d4ibehRIldYMWM2LD7ImQblVhUejVQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "@types/unist": "^3.0.0", - "unist-util-visit": "^5.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-directive": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/mdast-util-directive/-/mdast-util-directive-3.1.0.tgz", - "integrity": "sha512-I3fNFt+DHmpWCYAT7quoM6lHf9wuqtI+oCOfvILnoicNIqjh5E3dEJWiXuYME2gNe8vl1iMQwyUHa7bgFmak6Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "@types/unist": "^3.0.0", - "ccount": "^2.0.0", - "devlop": "^1.0.0", - "mdast-util-from-markdown": "^2.0.0", - "mdast-util-to-markdown": "^2.0.0", - "parse-entities": "^4.0.0", - "stringify-entities": "^4.0.0", - "unist-util-visit-parents": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-find-and-replace": { - "version": "3.0.2", - "resolved": "https://registry.npmjs.org/mdast-util-find-and-replace/-/mdast-util-find-and-replace-3.0.2.tgz", - "integrity": "sha512-Tmd1Vg/m3Xz43afeNxDIhWRtFZgM2VLyaf4vSTYwudTyeuTneoL3qtWMA5jeLyz/O1vDJmmV4QuScFCA2tBPwg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "escape-string-regexp": "^5.0.0", - "unist-util-is": "^6.0.0", - "unist-util-visit-parents": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-find-and-replace/node_modules/escape-string-regexp": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-5.0.0.tgz", - "integrity": "sha512-/veY75JbMK4j1yjvuUxuVsiS/hr/4iHs9FTT6cgTexxdE0Ly/glccBAkloH/DofkjRbZU3bnoj38mOmhkZ0lHw==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/mdast-util-from-markdown": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/mdast-util-from-markdown/-/mdast-util-from-markdown-2.0.2.tgz", - "integrity": "sha512-uZhTV/8NBuw0WHkPTrCqDOl0zVe1BIng5ZtHoDk49ME1qqcjYmmLmOf0gELgcRMxN4w2iuIeVso5/6QymSrgmA==", - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "@types/unist": "^3.0.0", - "decode-named-character-reference": "^1.0.0", - "devlop": "^1.0.0", - "mdast-util-to-string": "^4.0.0", - "micromark": "^4.0.0", - "micromark-util-decode-numeric-character-reference": "^2.0.0", - "micromark-util-decode-string": "^2.0.0", - "micromark-util-normalize-identifier": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0", - "unist-util-stringify-position": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-gfm": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/mdast-util-gfm/-/mdast-util-gfm-3.1.0.tgz", - "integrity": "sha512-0ulfdQOM3ysHhCJ1p06l0b0VKlhU0wuQs3thxZQagjcjPrlFRqY215uZGHHJan9GEAXd9MbfPjFJz+qMkVR6zQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "mdast-util-from-markdown": "^2.0.0", - "mdast-util-gfm-autolink-literal": "^2.0.0", - "mdast-util-gfm-footnote": "^2.0.0", - "mdast-util-gfm-strikethrough": "^2.0.0", - "mdast-util-gfm-table": "^2.0.0", - "mdast-util-gfm-task-list-item": "^2.0.0", - "mdast-util-to-markdown": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-gfm-autolink-literal": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/mdast-util-gfm-autolink-literal/-/mdast-util-gfm-autolink-literal-2.0.1.tgz", - "integrity": "sha512-5HVP2MKaP6L+G6YaxPNjuL0BPrq9orG3TsrZ9YXbA3vDw/ACI4MEsnoDpn6ZNm7GnZgtAcONJyPhOP8tNJQavQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "ccount": "^2.0.0", - "devlop": "^1.0.0", - "mdast-util-find-and-replace": "^3.0.0", - "micromark-util-character": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-gfm-footnote": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/mdast-util-gfm-footnote/-/mdast-util-gfm-footnote-2.1.0.tgz", - "integrity": "sha512-sqpDWlsHn7Ac9GNZQMeUzPQSMzR6Wv0WKRNvQRg0KqHh02fpTz69Qc1QSseNX29bhz1ROIyNyxExfawVKTm1GQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "devlop": "^1.1.0", - "mdast-util-from-markdown": "^2.0.0", - "mdast-util-to-markdown": "^2.0.0", - "micromark-util-normalize-identifier": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-gfm-strikethrough": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/mdast-util-gfm-strikethrough/-/mdast-util-gfm-strikethrough-2.0.0.tgz", - "integrity": "sha512-mKKb915TF+OC5ptj5bJ7WFRPdYtuHv0yTRxK2tJvi+BDqbkiG7h7u/9SI89nRAYcmap2xHQL9D+QG/6wSrTtXg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "mdast-util-from-markdown": "^2.0.0", - "mdast-util-to-markdown": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-gfm-table": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/mdast-util-gfm-table/-/mdast-util-gfm-table-2.0.0.tgz", - "integrity": "sha512-78UEvebzz/rJIxLvE7ZtDd/vIQ0RHv+3Mh5DR96p7cS7HsBhYIICDBCu8csTNWNO6tBWfqXPWekRuj2FNOGOZg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "devlop": "^1.0.0", - "markdown-table": "^3.0.0", - "mdast-util-from-markdown": "^2.0.0", - "mdast-util-to-markdown": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-gfm-task-list-item": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/mdast-util-gfm-task-list-item/-/mdast-util-gfm-task-list-item-2.0.0.tgz", - "integrity": "sha512-IrtvNvjxC1o06taBAVJznEnkiHxLFTzgonUdy8hzFVeDun0uTjxxrRGVaNFqkU1wJR3RBPEfsxmU6jDWPofrTQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "devlop": "^1.0.0", - "mdast-util-from-markdown": "^2.0.0", - "mdast-util-to-markdown": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-mdx": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/mdast-util-mdx/-/mdast-util-mdx-3.0.0.tgz", - "integrity": "sha512-JfbYLAW7XnYTTbUsmpu0kdBUVe+yKVJZBItEjwyYJiDJuZ9w4eeaqks4HQO+R7objWgS2ymV60GYpI14Ug554w==", - "dev": true, - "license": "MIT", - "dependencies": { - "mdast-util-from-markdown": "^2.0.0", - "mdast-util-mdx-expression": "^2.0.0", - "mdast-util-mdx-jsx": "^3.0.0", - "mdast-util-mdxjs-esm": "^2.0.0", - "mdast-util-to-markdown": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-mdx-expression": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/mdast-util-mdx-expression/-/mdast-util-mdx-expression-2.0.1.tgz", - "integrity": "sha512-J6f+9hUp+ldTZqKRSg7Vw5V6MqjATc+3E4gf3CFNcuZNWD8XdyI6zQ8GqH7f8169MM6P7hMBRDVGnn7oHB9kXQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree-jsx": "^1.0.0", - "@types/hast": "^3.0.0", - "@types/mdast": "^4.0.0", - "devlop": "^1.0.0", - "mdast-util-from-markdown": "^2.0.0", - "mdast-util-to-markdown": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-mdx-jsx": { - "version": "3.2.0", - "resolved": "https://registry.npmjs.org/mdast-util-mdx-jsx/-/mdast-util-mdx-jsx-3.2.0.tgz", - "integrity": "sha512-lj/z8v0r6ZtsN/cGNNtemmmfoLAFZnjMbNyLzBafjzikOM+glrjNHPlf6lQDOTccj9n5b0PPihEBbhneMyGs1Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree-jsx": "^1.0.0", - "@types/hast": "^3.0.0", - "@types/mdast": "^4.0.0", - "@types/unist": "^3.0.0", - "ccount": "^2.0.0", - "devlop": "^1.1.0", - "mdast-util-from-markdown": "^2.0.0", - "mdast-util-to-markdown": "^2.0.0", - "parse-entities": "^4.0.0", - "stringify-entities": "^4.0.0", - "unist-util-stringify-position": "^4.0.0", - "vfile-message": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-mdxjs-esm": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/mdast-util-mdxjs-esm/-/mdast-util-mdxjs-esm-2.0.1.tgz", - "integrity": "sha512-EcmOpxsZ96CvlP03NghtH1EsLtr0n9Tm4lPUJUBccV9RwUOneqSycg19n5HGzCf+10LozMRSObtVr3ee1WoHtg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree-jsx": "^1.0.0", - "@types/hast": "^3.0.0", - "@types/mdast": "^4.0.0", - "devlop": "^1.0.0", - "mdast-util-from-markdown": "^2.0.0", - "mdast-util-to-markdown": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-phrasing": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/mdast-util-phrasing/-/mdast-util-phrasing-4.1.0.tgz", - "integrity": "sha512-TqICwyvJJpBwvGAMZjj4J2n0X8QWp21b9l0o7eXyVJ25YNWYbJDVIyD1bZXE6WtV6RmKJVYmQAKWa0zWOABz2w==", - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "unist-util-is": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-to-hast": { - "version": "13.2.1", - "resolved": "https://registry.npmjs.org/mdast-util-to-hast/-/mdast-util-to-hast-13.2.1.tgz", - "integrity": "sha512-cctsq2wp5vTsLIcaymblUriiTcZd0CwWtCbLvrOzYCDZoWyMNV8sZ7krj09FSnsiJi3WVsHLM4k6Dq/yaPyCXA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "@types/mdast": "^4.0.0", - "@ungap/structured-clone": "^1.0.0", - "devlop": "^1.0.0", - "micromark-util-sanitize-uri": "^2.0.0", - "trim-lines": "^3.0.0", - "unist-util-position": "^5.0.0", - "unist-util-visit": "^5.0.0", - "vfile": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-to-markdown": { - "version": "2.1.2", - "resolved": "https://registry.npmjs.org/mdast-util-to-markdown/-/mdast-util-to-markdown-2.1.2.tgz", - "integrity": "sha512-xj68wMTvGXVOKonmog6LwyJKrYXZPvlwabaryTjLh9LuvovB/KAH+kvi8Gjj+7rJjsFi23nkUxRQv1KqSroMqA==", - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "@types/unist": "^3.0.0", - "longest-streak": "^3.0.0", - "mdast-util-phrasing": "^4.0.0", - "mdast-util-to-string": "^4.0.0", - "micromark-util-classify-character": "^2.0.0", - "micromark-util-decode-string": "^2.0.0", - "unist-util-visit": "^5.0.0", - "zwitch": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdast-util-to-string": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/mdast-util-to-string/-/mdast-util-to-string-4.0.0.tgz", - "integrity": "sha512-0H44vDimn51F0YwvxSJSm0eCDOJTRlmN0R1yBh4HLj9wiV1Dn0QoXGbvFAWj2hSItVTlCmBF1hqKlIyUBVFLPg==", - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/mdn-data": { - "version": "2.12.2", - "resolved": "https://registry.npmjs.org/mdn-data/-/mdn-data-2.12.2.tgz", - "integrity": "sha512-IEn+pegP1aManZuckezWCO+XZQDplx1366JoVhTpMpBB1sPey/SbveZQUosKiKiGYjg1wH4pMlNgXbCiYgihQA==", - "dev": true, - "license": "CC0-1.0" - }, - "node_modules/mdurl": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/mdurl/-/mdurl-2.0.0.tgz", - "integrity": "sha512-Lf+9+2r+Tdp5wXDXC4PcIBjTDtq4UKjCPMQhKIuzpJNW0b96kVqSwW0bT7FhRSfmAiFYgP+SCRvdrDozfh0U5w==", - "dev": true, - "license": "MIT" - }, - "node_modules/merge-stream": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/merge-stream/-/merge-stream-2.0.0.tgz", - "integrity": "sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w==", - "dev": true, - "license": "MIT" - }, - "node_modules/merge2": { - "version": "1.4.1", - "resolved": "https://registry.npmjs.org/merge2/-/merge2-1.4.1.tgz", - "integrity": "sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 8" - } - }, - "node_modules/micromark": { - "version": "4.0.2", - "resolved": "https://registry.npmjs.org/micromark/-/micromark-4.0.2.tgz", - "integrity": "sha512-zpe98Q6kvavpCr1NPVSCMebCKfD7CA2NqZ+rykeNhONIJBpc1tFKt9hucLGwha3jNTNI8lHpctWJWoimVF4PfA==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "@types/debug": "^4.0.0", - "debug": "^4.0.0", - "decode-named-character-reference": "^1.0.0", - "devlop": "^1.0.0", - "micromark-core-commonmark": "^2.0.0", - "micromark-factory-space": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-chunked": "^2.0.0", - "micromark-util-combine-extensions": "^2.0.0", - "micromark-util-decode-numeric-character-reference": "^2.0.0", - "micromark-util-encode": "^2.0.0", - "micromark-util-normalize-identifier": "^2.0.0", - "micromark-util-resolve-all": "^2.0.0", - "micromark-util-sanitize-uri": "^2.0.0", - "micromark-util-subtokenize": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-core-commonmark": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/micromark-core-commonmark/-/micromark-core-commonmark-2.0.3.tgz", - "integrity": "sha512-RDBrHEMSxVFLg6xvnXmb1Ayr2WzLAWjeSATAoxwKYJV94TeNavgoIdA0a9ytzDSVzBy2YKFK+emCPOEibLeCrg==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "decode-named-character-reference": "^1.0.0", - "devlop": "^1.0.0", - "micromark-factory-destination": "^2.0.0", - "micromark-factory-label": "^2.0.0", - "micromark-factory-space": "^2.0.0", - "micromark-factory-title": "^2.0.0", - "micromark-factory-whitespace": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-chunked": "^2.0.0", - "micromark-util-classify-character": "^2.0.0", - "micromark-util-html-tag-name": "^2.0.0", - "micromark-util-normalize-identifier": "^2.0.0", - "micromark-util-resolve-all": "^2.0.0", - "micromark-util-subtokenize": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-extension-directive": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/micromark-extension-directive/-/micromark-extension-directive-4.0.0.tgz", - "integrity": "sha512-/C2nqVmXXmiseSSuCdItCMho7ybwwop6RrrRPk0KbOHW21JKoCldC+8rFOaundDoRBUWBnJJcxeA/Kvi34WQXg==", - "dev": true, - "license": "MIT", - "dependencies": { - "devlop": "^1.0.0", - "micromark-factory-space": "^2.0.0", - "micromark-factory-whitespace": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0", - "parse-entities": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-gfm": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/micromark-extension-gfm/-/micromark-extension-gfm-3.0.0.tgz", - "integrity": "sha512-vsKArQsicm7t0z2GugkCKtZehqUm31oeGBV/KVSorWSy8ZlNAv7ytjFhvaryUiCUJYqs+NoE6AFhpQvBTM6Q4w==", - "dev": true, - "license": "MIT", - "dependencies": { - "micromark-extension-gfm-autolink-literal": "^2.0.0", - "micromark-extension-gfm-footnote": "^2.0.0", - "micromark-extension-gfm-strikethrough": "^2.0.0", - "micromark-extension-gfm-table": "^2.0.0", - "micromark-extension-gfm-tagfilter": "^2.0.0", - "micromark-extension-gfm-task-list-item": "^2.0.0", - "micromark-util-combine-extensions": "^2.0.0", - "micromark-util-types": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-gfm-autolink-literal": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/micromark-extension-gfm-autolink-literal/-/micromark-extension-gfm-autolink-literal-2.1.0.tgz", - "integrity": "sha512-oOg7knzhicgQ3t4QCjCWgTmfNhvQbDDnJeVu9v81r7NltNCVmhPy1fJRX27pISafdjL+SVc4d3l48Gb6pbRypw==", - "dev": true, - "license": "MIT", - "dependencies": { - "micromark-util-character": "^2.0.0", - "micromark-util-sanitize-uri": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-gfm-footnote": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/micromark-extension-gfm-footnote/-/micromark-extension-gfm-footnote-2.1.0.tgz", - "integrity": "sha512-/yPhxI1ntnDNsiHtzLKYnE3vf9JZ6cAisqVDauhp4CEHxlb4uoOTxOCJ+9s51bIB8U1N1FJ1RXOKTIlD5B/gqw==", - "dev": true, - "license": "MIT", - "dependencies": { - "devlop": "^1.0.0", - "micromark-core-commonmark": "^2.0.0", - "micromark-factory-space": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-normalize-identifier": "^2.0.0", - "micromark-util-sanitize-uri": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-gfm-strikethrough": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/micromark-extension-gfm-strikethrough/-/micromark-extension-gfm-strikethrough-2.1.0.tgz", - "integrity": "sha512-ADVjpOOkjz1hhkZLlBiYA9cR2Anf8F4HqZUO6e5eDcPQd0Txw5fxLzzxnEkSkfnD0wziSGiv7sYhk/ktvbf1uw==", - "dev": true, - "license": "MIT", - "dependencies": { - "devlop": "^1.0.0", - "micromark-util-chunked": "^2.0.0", - "micromark-util-classify-character": "^2.0.0", - "micromark-util-resolve-all": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-gfm-table": { - "version": "2.1.1", - "resolved": "https://registry.npmjs.org/micromark-extension-gfm-table/-/micromark-extension-gfm-table-2.1.1.tgz", - "integrity": "sha512-t2OU/dXXioARrC6yWfJ4hqB7rct14e8f7m0cbI5hUmDyyIlwv5vEtooptH8INkbLzOatzKuVbQmAYcbWoyz6Dg==", - "dev": true, - "license": "MIT", - "dependencies": { - "devlop": "^1.0.0", - "micromark-factory-space": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-gfm-tagfilter": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/micromark-extension-gfm-tagfilter/-/micromark-extension-gfm-tagfilter-2.0.0.tgz", - "integrity": "sha512-xHlTOmuCSotIA8TW1mDIM6X2O1SiX5P9IuDtqGonFhEK0qgRI4yeC6vMxEV2dgyr2TiD+2PQ10o+cOhdVAcwfg==", - "dev": true, - "license": "MIT", - "dependencies": { - "micromark-util-types": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-gfm-task-list-item": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/micromark-extension-gfm-task-list-item/-/micromark-extension-gfm-task-list-item-2.1.0.tgz", - "integrity": "sha512-qIBZhqxqI6fjLDYFTBIa4eivDMnP+OZqsNwmQ3xNLE4Cxwc+zfQEfbs6tzAo2Hjq+bh6q5F+Z8/cksrLFYWQQw==", - "dev": true, - "license": "MIT", - "dependencies": { - "devlop": "^1.0.0", - "micromark-factory-space": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-math": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/micromark-extension-math/-/micromark-extension-math-3.1.0.tgz", - "integrity": "sha512-lvEqd+fHjATVs+2v/8kg9i5Q0AP2k85H0WUOwpIVvUML8BapsMvh1XAogmQjOCsLpoKRCVQqEkQBB3NhVBcsOg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/katex": "^0.16.0", - "devlop": "^1.0.0", - "katex": "^0.16.0", - "micromark-factory-space": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-mdx-expression": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/micromark-extension-mdx-expression/-/micromark-extension-mdx-expression-3.0.1.tgz", - "integrity": "sha512-dD/ADLJ1AeMvSAKBwO22zG22N4ybhe7kFIZ3LsDI0GlsNr2A3KYxb0LdC1u5rj4Nw+CHKY0RVdnHX8vj8ejm4Q==", - "dev": true, - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "devlop": "^1.0.0", - "micromark-factory-mdx-expression": "^2.0.0", - "micromark-factory-space": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-events-to-acorn": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-extension-mdx-jsx": { - "version": "3.0.2", - "resolved": "https://registry.npmjs.org/micromark-extension-mdx-jsx/-/micromark-extension-mdx-jsx-3.0.2.tgz", - "integrity": "sha512-e5+q1DjMh62LZAJOnDraSSbDMvGJ8x3cbjygy2qFEi7HCeUT4BDKCvMozPozcD6WmOt6sVvYDNBKhFSz3kjOVQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "devlop": "^1.0.0", - "estree-util-is-identifier-name": "^3.0.0", - "micromark-factory-mdx-expression": "^2.0.0", - "micromark-factory-space": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-events-to-acorn": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0", - "vfile-message": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-mdx-md": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/micromark-extension-mdx-md/-/micromark-extension-mdx-md-2.0.0.tgz", - "integrity": "sha512-EpAiszsB3blw4Rpba7xTOUptcFeBFi+6PY8VnJ2hhimH+vCQDirWgsMpz7w1XcZE7LVrSAUGb9VJpG9ghlYvYQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "micromark-util-types": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-mdxjs": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/micromark-extension-mdxjs/-/micromark-extension-mdxjs-3.0.0.tgz", - "integrity": "sha512-A873fJfhnJ2siZyUrJ31l34Uqwy4xIFmvPY1oj+Ean5PHcPBYzEsvqvWGaWcfEIr11O5Dlw3p2y0tZWpKHDejQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "acorn": "^8.0.0", - "acorn-jsx": "^5.0.0", - "micromark-extension-mdx-expression": "^3.0.0", - "micromark-extension-mdx-jsx": "^3.0.0", - "micromark-extension-mdx-md": "^2.0.0", - "micromark-extension-mdxjs-esm": "^3.0.0", - "micromark-util-combine-extensions": "^2.0.0", - "micromark-util-types": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-extension-mdxjs-esm": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/micromark-extension-mdxjs-esm/-/micromark-extension-mdxjs-esm-3.0.0.tgz", - "integrity": "sha512-DJFl4ZqkErRpq/dAPyeWp15tGrcrrJho1hKK5uBS70BCtfrIFg81sqcTVu3Ta+KD1Tk5vAtBNElWxtAa+m8K9A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "devlop": "^1.0.0", - "micromark-core-commonmark": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-events-to-acorn": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0", - "unist-util-position-from-estree": "^2.0.0", - "vfile-message": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/micromark-factory-destination": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-factory-destination/-/micromark-factory-destination-2.0.1.tgz", - "integrity": "sha512-Xe6rDdJlkmbFRExpTOmRj9N3MaWmbAgdpSrBQvCFqhezUn4AHqJHbaEnfbVYYiexVSs//tqOdY/DxhjdCiJnIA==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-util-character": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-factory-label": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-factory-label/-/micromark-factory-label-2.0.1.tgz", - "integrity": "sha512-VFMekyQExqIW7xIChcXn4ok29YE3rnuyveW3wZQWWqF4Nv9Wk5rgJ99KzPvHjkmPXF93FXIbBp6YdW3t71/7Vg==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "devlop": "^1.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-factory-mdx-expression": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/micromark-factory-mdx-expression/-/micromark-factory-mdx-expression-2.0.3.tgz", - "integrity": "sha512-kQnEtA3vzucU2BkrIa8/VaSAsP+EJ3CKOvhMuJgOEGg9KDC6OAY6nSnNDVRiVNRqj7Y4SlSzcStaH/5jge8JdQ==", - "dev": true, - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "devlop": "^1.0.0", - "micromark-factory-space": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-events-to-acorn": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0", - "unist-util-position-from-estree": "^2.0.0", - "vfile-message": "^4.0.0" - } - }, - "node_modules/micromark-factory-space": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-factory-space/-/micromark-factory-space-2.0.1.tgz", - "integrity": "sha512-zRkxjtBxxLd2Sc0d+fbnEunsTj46SWXgXciZmHq0kDYGnck/ZSGj9/wULTV95uoeYiK5hRXP2mJ98Uo4cq/LQg==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-util-character": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-factory-title": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-factory-title/-/micromark-factory-title-2.0.1.tgz", - "integrity": "sha512-5bZ+3CjhAd9eChYTHsjy6TGxpOFSKgKKJPJxr293jTbfry2KDoWkhBb6TcPVB4NmzaPhMs1Frm9AZH7OD4Cjzw==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-factory-space": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-factory-whitespace": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-factory-whitespace/-/micromark-factory-whitespace-2.0.1.tgz", - "integrity": "sha512-Ob0nuZ3PKt/n0hORHyvoD9uZhr+Za8sFoP+OnMcnWK5lngSzALgQYKMr9RJVOWLqQYuyn6ulqGWSXdwf6F80lQ==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-factory-space": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-util-character": { - "version": "2.1.1", - "resolved": "https://registry.npmjs.org/micromark-util-character/-/micromark-util-character-2.1.1.tgz", - "integrity": "sha512-wv8tdUTJ3thSFFFJKtpYKOYiGP2+v96Hvk4Tu8KpCAsTMs6yi+nVmGh1syvSCsaxz45J6Jbw+9DD6g97+NV67Q==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-util-chunked": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-util-chunked/-/micromark-util-chunked-2.0.1.tgz", - "integrity": "sha512-QUNFEOPELfmvv+4xiNg2sRYeS/P84pTW0TCgP5zc9FpXetHY0ab7SxKyAQCNCc1eK0459uoLI1y5oO5Vc1dbhA==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-util-symbol": "^2.0.0" - } - }, - "node_modules/micromark-util-classify-character": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-util-classify-character/-/micromark-util-classify-character-2.0.1.tgz", - "integrity": "sha512-K0kHzM6afW/MbeWYWLjoHQv1sgg2Q9EccHEDzSkxiP/EaagNzCm7T/WMKZ3rjMbvIpvBiZgwR3dKMygtA4mG1Q==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-util-character": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-util-combine-extensions": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-util-combine-extensions/-/micromark-util-combine-extensions-2.0.1.tgz", - "integrity": "sha512-OnAnH8Ujmy59JcyZw8JSbK9cGpdVY44NKgSM7E9Eh7DiLS2E9RNQf0dONaGDzEG9yjEl5hcqeIsj4hfRkLH/Bg==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-util-chunked": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-util-decode-numeric-character-reference": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/micromark-util-decode-numeric-character-reference/-/micromark-util-decode-numeric-character-reference-2.0.2.tgz", - "integrity": "sha512-ccUbYk6CwVdkmCQMyr64dXz42EfHGkPQlBj5p7YVGzq8I7CtjXZJrubAYezf7Rp+bjPseiROqe7G6foFd+lEuw==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-util-symbol": "^2.0.0" - } - }, - "node_modules/micromark-util-decode-string": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-util-decode-string/-/micromark-util-decode-string-2.0.1.tgz", - "integrity": "sha512-nDV/77Fj6eH1ynwscYTOsbK7rR//Uj0bZXBwJZRfaLEJ1iGBR6kIfNmlNqaqJf649EP0F3NWNdeJi03elllNUQ==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "decode-named-character-reference": "^1.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-decode-numeric-character-reference": "^2.0.0", - "micromark-util-symbol": "^2.0.0" - } - }, - "node_modules/micromark-util-encode": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-util-encode/-/micromark-util-encode-2.0.1.tgz", - "integrity": "sha512-c3cVx2y4KqUnwopcO9b/SCdo2O67LwJJ/UyqGfbigahfegL9myoEFoDYZgkT7f36T0bLrM9hZTAaAyH+PCAXjw==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT" - }, - "node_modules/micromark-util-events-to-acorn": { - "version": "2.0.3", - "resolved": "https://registry.npmjs.org/micromark-util-events-to-acorn/-/micromark-util-events-to-acorn-2.0.3.tgz", - "integrity": "sha512-jmsiEIiZ1n7X1Rr5k8wVExBQCg5jy4UXVADItHmNk1zkwEVhBuIUKRu3fqv+hs4nxLISi2DQGlqIOGiFxgbfHg==", - "dev": true, - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "@types/unist": "^3.0.0", - "devlop": "^1.0.0", - "estree-util-visit": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0", - "vfile-message": "^4.0.0" - } - }, - "node_modules/micromark-util-html-tag-name": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-util-html-tag-name/-/micromark-util-html-tag-name-2.0.1.tgz", - "integrity": "sha512-2cNEiYDhCWKI+Gs9T0Tiysk136SnR13hhO8yW6BGNyhOC4qYFnwF1nKfD3HFAIXA5c45RrIG1ub11GiXeYd1xA==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT" - }, - "node_modules/micromark-util-normalize-identifier": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-util-normalize-identifier/-/micromark-util-normalize-identifier-2.0.1.tgz", - "integrity": "sha512-sxPqmo70LyARJs0w2UclACPUUEqltCkJ6PhKdMIDuJ3gSf/Q+/GIe3WKl0Ijb/GyH9lOpUkRAO2wp0GVkLvS9Q==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-util-symbol": "^2.0.0" - } - }, - "node_modules/micromark-util-resolve-all": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-util-resolve-all/-/micromark-util-resolve-all-2.0.1.tgz", - "integrity": "sha512-VdQyxFWFT2/FGJgwQnJYbe1jjQoNTS4RjglmSjTUlpUMa95Htx9NHeYW4rGDJzbjvCsl9eLjMQwGeElsqmzcHg==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-util-sanitize-uri": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-util-sanitize-uri/-/micromark-util-sanitize-uri-2.0.1.tgz", - "integrity": "sha512-9N9IomZ/YuGGZZmQec1MbgxtlgougxTodVwDzzEouPKo3qFWvymFHWcnDi2vzV1ff6kas9ucW+o3yzJK9YB1AQ==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "micromark-util-character": "^2.0.0", - "micromark-util-encode": "^2.0.0", - "micromark-util-symbol": "^2.0.0" - } - }, - "node_modules/micromark-util-subtokenize": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/micromark-util-subtokenize/-/micromark-util-subtokenize-2.1.0.tgz", - "integrity": "sha512-XQLu552iSctvnEcgXw6+Sx75GflAPNED1qx7eBJ+wydBb2KCbRZe+NwvIEEMM83uml1+2WSXpBAcp9IUCgCYWA==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT", - "dependencies": { - "devlop": "^1.0.0", - "micromark-util-chunked": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0" - } - }, - "node_modules/micromark-util-symbol": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/micromark-util-symbol/-/micromark-util-symbol-2.0.1.tgz", - "integrity": "sha512-vs5t8Apaud9N28kgCrRUdEed4UJ+wWNvicHLPxCa9ENlYuAY31M0ETy5y1vA33YoNPDFTghEbnh6efaE8h4x0Q==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT" - }, - "node_modules/micromark-util-types": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/micromark-util-types/-/micromark-util-types-2.0.2.tgz", - "integrity": "sha512-Yw0ECSpJoViF1qTU4DC6NwtC4aWGt1EkzaQB8KPPyCRR8z9TWeV0HbEFGTO+ZY1wB22zmxnJqhPyTpOVCpeHTA==", - "funding": [ - { - "type": "GitHub Sponsors", - "url": "https://github.com/sponsors/unifiedjs" - }, - { - "type": "OpenCollective", - "url": "https://opencollective.com/unified" - } - ], - "license": "MIT" - }, - "node_modules/micromatch": { - "version": "4.0.8", - "resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.8.tgz", - "integrity": "sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==", - "dev": true, - "license": "MIT", - "dependencies": { - "braces": "^3.0.3", - "picomatch": "^2.3.1" - }, - "engines": { - "node": ">=8.6" - } - }, - "node_modules/micromatch/node_modules/picomatch": { - "version": "2.3.1", - "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz", - "integrity": "sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8.6" - }, - "funding": { - "url": "https://github.com/sponsors/jonschlinkert" - } - }, - "node_modules/mimic-fn": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/mimic-fn/-/mimic-fn-2.1.0.tgz", - "integrity": "sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/mimic-function": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/mimic-function/-/mimic-function-5.0.1.tgz", - "integrity": "sha512-VP79XUPxV2CigYP3jWwAUFSku2aKqBH7uTAapFWCBqutsbmDo96KY5o8uh6U+/YSIn5OxJnXp73beVkpqMIGhA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/minimatch": { - "version": "3.1.2", - "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz", - "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==", - "dev": true, - "license": "ISC", - "dependencies": { - "brace-expansion": "^1.1.7" - }, - "engines": { - "node": "*" - } - }, - "node_modules/minipass": { - "version": "7.1.2", - "resolved": "https://registry.npmjs.org/minipass/-/minipass-7.1.2.tgz", - "integrity": "sha512-qOOzS1cBTWYF4BH8fVePDBOO9iptMnGUEZwNc/cMWnTV2nVLZ7VoNWEPHkYczZA0pdoA7dl6e7FL659nX9S2aw==", - "license": "ISC", - "engines": { - "node": ">=16 || 14 >=14.17" - } - }, - "node_modules/mrmime": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/mrmime/-/mrmime-2.0.1.tgz", - "integrity": "sha512-Y3wQdFg2Va6etvQ5I82yUhGdsKrcYox6p7FfL1LbK2J4V01F9TGlepTIhnK24t7koZibmg82KGglhA1XK5IsLQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=10" - } - }, - "node_modules/ms": { - "version": "2.1.3", - "resolved": "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz", - "integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==", - "license": "MIT" - }, - "node_modules/nano-spawn": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/nano-spawn/-/nano-spawn-2.0.0.tgz", - "integrity": "sha512-tacvGzUY5o2D8CBh2rrwxyNojUsZNU2zjNTzKQrkgGJQTbGAfArVWXSKMBokBeeg6C7OLRGUEyoFlYbfeWQIqw==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=20.17" - }, - "funding": { - "url": "https://github.com/sindresorhus/nano-spawn?sponsor=1" - } - }, - "node_modules/nanoid": { - "version": "3.3.11", - "resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.11.tgz", - "integrity": "sha512-N8SpfPUnUp1bK+PMYW8qSWdl9U+wwNWI4QKxOYDy9JAro3WMX7p2OeVRF9v+347pnakNevPmiHhNmZ2HbFA76w==", - "dev": true, - "funding": [ - { - "type": "github", - "url": "https://github.com/sponsors/ai" - } - ], - "license": "MIT", - "bin": { - "nanoid": "bin/nanoid.cjs" - }, - "engines": { - "node": "^10 || ^12 || ^13.7 || ^14 || >=15.0.1" - } - }, - "node_modules/napi-postinstall": { - "version": "0.3.4", - "resolved": "https://registry.npmjs.org/napi-postinstall/-/napi-postinstall-0.3.4.tgz", - "integrity": "sha512-PHI5f1O0EP5xJ9gQmFGMS6IZcrVvTjpXjz7Na41gTE7eE2hK11lg04CECCYEEjdc17EV4DO+fkGEtt7TpTaTiQ==", - "dev": true, - "license": "MIT", - "bin": { - "napi-postinstall": "lib/cli.js" - }, - "engines": { - "node": "^12.20.0 || ^14.18.0 || >=16.0.0" - }, - "funding": { - "url": "https://opencollective.com/napi-postinstall" - } - }, - "node_modules/natural-compare": { - "version": "1.4.0", - "resolved": "https://registry.npmjs.org/natural-compare/-/natural-compare-1.4.0.tgz", - "integrity": "sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==", - "dev": true, - "license": "MIT" - }, - "node_modules/nconf": { - "version": "0.12.1", - "resolved": "https://registry.npmjs.org/nconf/-/nconf-0.12.1.tgz", - "integrity": "sha512-p2cfF+B3XXacQdswUYWZ0w6Vld0832A/tuqjLBu3H1sfUcby4N2oVbGhyuCkZv+t3iY3aiFEj7gZGqax9Q2c1w==", - "dev": true, - "license": "MIT", - "dependencies": { - "async": "^3.0.0", - "ini": "^2.0.0", - "secure-keys": "^1.0.0", - "yargs": "^16.1.1" - }, - "engines": { - "node": ">= 0.4.0" - } - }, - "node_modules/nconf/node_modules/ansi-regex": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", - "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/nconf/node_modules/cliui": { - "version": "7.0.4", - "resolved": "https://registry.npmjs.org/cliui/-/cliui-7.0.4.tgz", - "integrity": "sha512-OcRE68cOsVMXp1Yvonl/fzkQOyjLSu/8bhPDfQt0e0/Eb283TKP20Fs2MqoPsr9SwA595rRCA+QMzYc9nBP+JQ==", - "dev": true, - "license": "ISC", - "dependencies": { - "string-width": "^4.2.0", - "strip-ansi": "^6.0.0", - "wrap-ansi": "^7.0.0" - } - }, - "node_modules/nconf/node_modules/strip-ansi": { - "version": "6.0.1", - "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", - "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", - "dev": true, - "license": "MIT", - "dependencies": { - "ansi-regex": "^5.0.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/nconf/node_modules/yargs": { - "version": "16.2.0", - "resolved": "https://registry.npmjs.org/yargs/-/yargs-16.2.0.tgz", - "integrity": "sha512-D1mvvtDG0L5ft/jGWkLpG1+m0eQxOfaBvTNELraWj22wSVUMWxZUvYgJYcKh6jGGIkJFhH4IZPQhR4TKpc8mBw==", - "dev": true, - "license": "MIT", - "dependencies": { - "cliui": "^7.0.2", - "escalade": "^3.1.1", - "get-caller-file": "^2.0.5", - "require-directory": "^2.1.1", - "string-width": "^4.2.0", - "y18n": "^5.0.5", - "yargs-parser": "^20.2.2" - }, - "engines": { - "node": ">=10" - } - }, - "node_modules/nconf/node_modules/yargs-parser": { - "version": "20.2.9", - "resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-20.2.9.tgz", - "integrity": "sha512-y11nGElTIV+CT3Zv9t7VKl+Q3hTQoT9a1Qzezhhl6Rp21gJ/IVTW7Z3y9EWXhuUBC2Shnf+DX0antecpAwSP8w==", - "dev": true, - "license": "ISC", - "engines": { - "node": ">=10" - } - }, - "node_modules/neotraverse": { - "version": "0.6.18", - "resolved": "https://registry.npmjs.org/neotraverse/-/neotraverse-0.6.18.tgz", - "integrity": "sha512-Z4SmBUweYa09+o6pG+eASabEpP6QkQ70yHj351pQoEXIs8uHbaU2DWVmzBANKgflPa47A50PtB2+NgRpQvr7vA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 10" - } - }, - "node_modules/nlcst-to-string": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/nlcst-to-string/-/nlcst-to-string-4.0.0.tgz", - "integrity": "sha512-YKLBCcUYKAg0FNlOBT6aI91qFmSiFKiluk655WzPF+DDMA02qIyy8uiRqI8QXtcFpEvll12LpL5MXqEmAZ+dcA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/nlcst": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/node-fetch-native": { - "version": "1.6.7", - "resolved": "https://registry.npmjs.org/node-fetch-native/-/node-fetch-native-1.6.7.tgz", - "integrity": "sha512-g9yhqoedzIUm0nTnTqAQvueMPVOuIY16bqgAJJC8XOOubYFNwz6IER9qs0Gq2Xd0+CecCKFjtdDTMA4u4xG06Q==", - "dev": true, - "license": "MIT" - }, - "node_modules/node-int64": { - "version": "0.4.0", - "resolved": "https://registry.npmjs.org/node-int64/-/node-int64-0.4.0.tgz", - "integrity": "sha512-O5lz91xSOeoXP6DulyHfllpq+Eg00MWitZIbtPfoSEvqIHdl5gfcY6hYzDWnj0qD5tz52PI08u9qUvSVeUBeHw==", - "dev": true, - "license": "MIT" - }, - "node_modules/node-mock-http": { - "version": "1.0.4", - "resolved": "https://registry.npmjs.org/node-mock-http/-/node-mock-http-1.0.4.tgz", - "integrity": "sha512-8DY+kFsDkNXy1sJglUfuODx1/opAGJGyrTuFqEoN90oRc2Vk0ZbD4K2qmKXBBEhZQzdKHIVfEJpDU8Ak2NJEvQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/node-releases": { - "version": "2.0.27", - "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.27.tgz", - "integrity": "sha512-nmh3lCkYZ3grZvqcCH+fjmQ7X+H0OeZgP40OierEaAptX4XofMh5kwNbWh7lBduUzCcV/8kZ+NDLCwm2iorIlA==", - "dev": true, - "license": "MIT" - }, - "node_modules/normalize-path": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz", - "integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=0.10.0" - } - }, - "node_modules/npm-run-path": { - "version": "4.0.1", - "resolved": "https://registry.npmjs.org/npm-run-path/-/npm-run-path-4.0.1.tgz", - "integrity": "sha512-S48WzZW777zhNIrn7gxOlISNAqi9ZC/uQFnRdbeIHhZhCA6UqpkOT8T1G7BvfdgP4Er8gF4sUbaS0i7QvIfCWw==", - "dev": true, - "license": "MIT", - "dependencies": { - "path-key": "^3.0.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/nth-check": { - "version": "2.1.1", - "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.1.1.tgz", - "integrity": "sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==", - "license": "BSD-2-Clause", - "dependencies": { - "boolbase": "^1.0.0" - }, - "funding": { - "url": "https://github.com/fb55/nth-check?sponsor=1" - } - }, - "node_modules/ofetch": { - "version": "1.5.1", - "resolved": "https://registry.npmjs.org/ofetch/-/ofetch-1.5.1.tgz", - "integrity": "sha512-2W4oUZlVaqAPAil6FUg/difl6YhqhUR7x2eZY4bQCko22UXg3hptq9KLQdqFClV+Wu85UX7hNtdGTngi/1BxcA==", - "dev": true, - "license": "MIT", - "dependencies": { - "destr": "^2.0.5", - "node-fetch-native": "^1.6.7", - "ufo": "^1.6.1" - } - }, - "node_modules/ohash": { - "version": "2.0.11", - "resolved": "https://registry.npmjs.org/ohash/-/ohash-2.0.11.tgz", - "integrity": "sha512-RdR9FQrFwNBNXAr4GixM8YaRZRJ5PUWbKYbE5eOsrwAjJW0q2REGcf79oYPsLyskQCZG1PLN+S/K1V00joZAoQ==", - "dev": true, - "license": "MIT" - }, - "node_modules/once": { - "version": "1.4.0", - "resolved": "https://registry.npmjs.org/once/-/once-1.4.0.tgz", - "integrity": "sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==", - "dev": true, - "license": "ISC", - "dependencies": { - "wrappy": "1" - } - }, - "node_modules/onetime": { - "version": "5.1.2", - "resolved": "https://registry.npmjs.org/onetime/-/onetime-5.1.2.tgz", - "integrity": "sha512-kbpaSSGJTWdAY5KPVeMOKXSrPtr8C8C7wodJbcsd51jRnmD+GZu8Y0VoU6Dm5Z4vWr0Ig/1NKuWRKf7j5aaYSg==", - "dev": true, - "license": "MIT", - "dependencies": { - "mimic-fn": "^2.1.0" - }, - "engines": { - "node": ">=6" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/oniguruma-parser": { - "version": "0.12.1", - "resolved": "https://registry.npmjs.org/oniguruma-parser/-/oniguruma-parser-0.12.1.tgz", - "integrity": "sha512-8Unqkvk1RYc6yq2WBYRj4hdnsAxVze8i7iPfQr8e4uSP3tRv0rpZcbGUDvxfQQcdwHt/e9PrMvGCsa8OqG9X3w==", - "dev": true, - "license": "MIT" - }, - "node_modules/oniguruma-to-es": { - "version": "4.3.4", - "resolved": "https://registry.npmjs.org/oniguruma-to-es/-/oniguruma-to-es-4.3.4.tgz", - "integrity": "sha512-3VhUGN3w2eYxnTzHn+ikMI+fp/96KoRSVK9/kMTcFqj1NRDh2IhQCKvYxDnWePKRXY/AqH+Fuiyb7VHSzBjHfA==", - "dev": true, - "license": "MIT", - "dependencies": { - "oniguruma-parser": "^0.12.1", - "regex": "^6.0.1", - "regex-recursion": "^6.0.2" - } - }, - "node_modules/optionator": { - "version": "0.9.4", - "resolved": "https://registry.npmjs.org/optionator/-/optionator-0.9.4.tgz", - "integrity": "sha512-6IpQ7mKUxRcZNLIObR0hz7lxsapSSIYNZJwXPGeF0mTVqGKFIXj1DQcMoT22S3ROcLyY/rz0PWaWZ9ayWmad9g==", - "dev": true, - "license": "MIT", - "dependencies": { - "deep-is": "^0.1.3", - "fast-levenshtein": "^2.0.6", - "levn": "^0.4.1", - "prelude-ls": "^1.2.1", - "type-check": "^0.4.0", - "word-wrap": "^1.2.5" - }, - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/p-limit": { - "version": "6.2.0", - "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-6.2.0.tgz", - "integrity": "sha512-kuUqqHNUqoIWp/c467RI4X6mmyuojY5jGutNU0wVTmEOOfcuwLqyMVoAi9MKi2Ak+5i9+nhmrK4ufZE8069kHA==", - "dev": true, - "license": "MIT", - "dependencies": { - "yocto-queue": "^1.1.1" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/p-locate": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-5.0.0.tgz", - "integrity": "sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==", - "dev": true, - "license": "MIT", - "dependencies": { - "p-limit": "^3.0.2" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/p-locate/node_modules/p-limit": { - "version": "3.1.0", - "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz", - "integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "yocto-queue": "^0.1.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/p-locate/node_modules/yocto-queue": { - "version": "0.1.0", - "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz", - "integrity": "sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/p-queue": { - "version": "8.1.1", - "resolved": "https://registry.npmjs.org/p-queue/-/p-queue-8.1.1.tgz", - "integrity": "sha512-aNZ+VfjobsWryoiPnEApGGmf5WmNsCo9xu8dfaYamG5qaLP7ClhLN6NgsFe6SwJ2UbLEBK5dv9x8Mn5+RVhMWQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "eventemitter3": "^5.0.1", - "p-timeout": "^6.1.2" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/p-timeout": { - "version": "6.1.4", - "resolved": "https://registry.npmjs.org/p-timeout/-/p-timeout-6.1.4.tgz", - "integrity": "sha512-MyIV3ZA/PmyBN/ud8vV9XzwTrNtR4jFrObymZYnZqMmW0zA8Z17vnT0rBgFE/TlohB+YCHqXMgZzb3Csp49vqg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=14.16" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/p-try": { - "version": "2.2.0", - "resolved": "https://registry.npmjs.org/p-try/-/p-try-2.2.0.tgz", - "integrity": "sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/package-json-from-dist": { - "version": "1.0.1", - "resolved": "https://registry.npmjs.org/package-json-from-dist/-/package-json-from-dist-1.0.1.tgz", - "integrity": "sha512-UEZIS3/by4OC8vL3P2dTXRETpebLI2NiI5vIrjaD/5UtrkFX/tNbwjTSRAGC/+7CAo2pIcBaRgWmcBBHcsaCIw==", - "license": "BlueOak-1.0.0" - }, - "node_modules/package-manager-detector": { - "version": "1.6.0", - "resolved": "https://registry.npmjs.org/package-manager-detector/-/package-manager-detector-1.6.0.tgz", - "integrity": "sha512-61A5ThoTiDG/C8s8UMZwSorAGwMJ0ERVGj2OjoW5pAalsNOg15+iQiPzrLJ4jhZ1HJzmC2PIHT2oEiH3R5fzNA==", - "dev": true, - "license": "MIT" - }, - "node_modules/pagefind": { - "version": "1.4.0", - "resolved": "https://registry.npmjs.org/pagefind/-/pagefind-1.4.0.tgz", - "integrity": "sha512-z2kY1mQlL4J8q5EIsQkLzQjilovKzfNVhX8De6oyE6uHpfFtyBaqUpcl/XzJC/4fjD8vBDyh1zolimIcVrCn9g==", - "dev": true, - "license": "MIT", - "bin": { - "pagefind": "lib/runner/bin.cjs" - }, - "optionalDependencies": { - "@pagefind/darwin-arm64": "1.4.0", - "@pagefind/darwin-x64": "1.4.0", - "@pagefind/freebsd-x64": "1.4.0", - "@pagefind/linux-arm64": "1.4.0", - "@pagefind/linux-x64": "1.4.0", - "@pagefind/windows-x64": "1.4.0" - } - }, - "node_modules/parent-module": { - "version": "1.0.1", - "resolved": "https://registry.npmjs.org/parent-module/-/parent-module-1.0.1.tgz", - "integrity": "sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==", - "dev": true, - "license": "MIT", - "dependencies": { - "callsites": "^3.0.0" - }, - "engines": { - "node": ">=6" - } - }, - "node_modules/parse-entities": { - "version": "4.0.2", - "resolved": "https://registry.npmjs.org/parse-entities/-/parse-entities-4.0.2.tgz", - "integrity": "sha512-GG2AQYWoLgL877gQIKeRPGO1xF9+eG1ujIb5soS5gPvLQ1y2o8FL90w2QWNdf9I361Mpp7726c+lj3U0qK1uGw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/unist": "^2.0.0", - "character-entities-legacy": "^3.0.0", - "character-reference-invalid": "^2.0.0", - "decode-named-character-reference": "^1.0.0", - "is-alphanumerical": "^2.0.0", - "is-decimal": "^2.0.0", - "is-hexadecimal": "^2.0.0" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/parse-entities/node_modules/@types/unist": { - "version": "2.0.11", - "resolved": "https://registry.npmjs.org/@types/unist/-/unist-2.0.11.tgz", - "integrity": "sha512-CmBKiL6NNo/OqgmMn95Fk9Whlp2mtvIv+KNpQKN2F4SjvrEesubTRWGYSg+BnWZOnlCaSTU1sMpsBOzgbYhnsA==", - "dev": true, - "license": "MIT" - }, - "node_modules/parse-json": { - "version": "5.2.0", - "resolved": "https://registry.npmjs.org/parse-json/-/parse-json-5.2.0.tgz", - "integrity": "sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@babel/code-frame": "^7.0.0", - "error-ex": "^1.3.1", - "json-parse-even-better-errors": "^2.3.0", - "lines-and-columns": "^1.1.6" - }, - "engines": { - "node": ">=8" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/parse-latin": { - "version": "7.0.0", - "resolved": "https://registry.npmjs.org/parse-latin/-/parse-latin-7.0.0.tgz", - "integrity": "sha512-mhHgobPPua5kZ98EF4HWiH167JWBfl4pvAIXXdbaVohtK7a6YBOy56kvhCqduqyo/f3yrHFWmqmiMg/BkBkYYQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/nlcst": "^2.0.0", - "@types/unist": "^3.0.0", - "nlcst-to-string": "^4.0.0", - "unist-util-modify-children": "^4.0.0", - "unist-util-visit-children": "^3.0.0", - "vfile": "^6.0.0" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/parse5": { - "version": "7.3.0", - "resolved": "https://registry.npmjs.org/parse5/-/parse5-7.3.0.tgz", - "integrity": "sha512-IInvU7fabl34qmi9gY8XOVxhYyMyuH2xUNpb2q8/Y+7552KlejkRvqvD19nMoUW/uQGGbqNpA6Tufu5FL5BZgw==", - "dev": true, - "license": "MIT", - "dependencies": { - "entities": "^6.0.0" - }, - "funding": { - "url": "https://github.com/inikulin/parse5?sponsor=1" - } - }, - "node_modules/parse5/node_modules/entities": { - "version": "6.0.1", - "resolved": "https://registry.npmjs.org/entities/-/entities-6.0.1.tgz", - "integrity": "sha512-aN97NXWF6AWBTahfVOIrB/NShkzi5H7F9r1s9mD3cDj4Ko5f2qhhVoYMibXF7GlLveb/D2ioWay8lxI97Ven3g==", - "dev": true, - "license": "BSD-2-Clause", - "engines": { - "node": ">=0.12" - }, - "funding": { - "url": "https://github.com/fb55/entities?sponsor=1" - } - }, - "node_modules/path-exists": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz", - "integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/path-is-absolute": { - "version": "1.0.1", - "resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.1.tgz", - "integrity": "sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=0.10.0" - } - }, - "node_modules/path-key": { - "version": "3.1.1", - "resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz", - "integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==", - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/path-scurry": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/path-scurry/-/path-scurry-2.0.1.tgz", - "integrity": "sha512-oWyT4gICAu+kaA7QWk/jvCHWarMKNs6pXOGWKDTr7cw4IGcUbW+PeTfbaQiLGheFRpjo6O9J0PmyMfQPjH71oA==", - "license": "BlueOak-1.0.0", - "dependencies": { - "lru-cache": "^11.0.0", - "minipass": "^7.1.2" - }, - "engines": { - "node": "20 || >=22" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/path-scurry/node_modules/lru-cache": { - "version": "11.2.5", - "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-11.2.5.tgz", - "integrity": "sha512-vFrFJkWtJvJnD5hg+hJvVE8Lh/TcMzKnTgCWmtBipwI5yLX/iX+5UB2tfuyODF5E7k9xEzMdYgGqaSb1c0c5Yw==", - "license": "BlueOak-1.0.0", - "engines": { - "node": "20 || >=22" - } - }, - "node_modules/path-type": { - "version": "6.0.0", - "resolved": "https://registry.npmjs.org/path-type/-/path-type-6.0.0.tgz", - "integrity": "sha512-Vj7sf++t5pBD637NSfkxpHSMfWaeig5+DKWLhcqIYx6mWQz5hdJTGDVMQiJcw1ZYkhs7AazKDGpRVji1LJCZUQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/piccolore": { - "version": "0.1.3", - "resolved": "https://registry.npmjs.org/piccolore/-/piccolore-0.1.3.tgz", - "integrity": "sha512-o8bTeDWjE086iwKrROaDf31K0qC/BENdm15/uH9usSC/uZjJOKb2YGiVHfLY4GhwsERiPI1jmwI2XrA7ACOxVw==", - "dev": true, - "license": "ISC" - }, - "node_modules/picocolors": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/picocolors/-/picocolors-1.1.1.tgz", - "integrity": "sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==", - "license": "ISC" - }, - "node_modules/picomatch": { - "version": "4.0.3", - "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-4.0.3.tgz", - "integrity": "sha512-5gTmgEY/sqK6gFXLIsQNH19lWb4ebPDLA4SdLP7dsWkIXHWlG66oPuVvXSGFPppYZz8ZDZq0dYYrbHfBCVUb1Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/sponsors/jonschlinkert" - } - }, - "node_modules/pidtree": { - "version": "0.6.0", - "resolved": "https://registry.npmjs.org/pidtree/-/pidtree-0.6.0.tgz", - "integrity": "sha512-eG2dWTVw5bzqGRztnHExczNxt5VGsE6OwTeCG3fdUf9KBsZzO3R5OIIIzWR+iZA0NtZ+RDVdaoE2dK1cn6jH4g==", - "dev": true, - "license": "MIT", - "bin": { - "pidtree": "bin/pidtree.js" - }, - "engines": { - "node": ">=0.10" - } - }, - "node_modules/pirates": { - "version": "4.0.7", - "resolved": "https://registry.npmjs.org/pirates/-/pirates-4.0.7.tgz", - "integrity": "sha512-TfySrs/5nm8fQJDcBDuUng3VOUKsd7S+zqvbOTiGXHfxX4wK31ard+hoNuvkicM/2YFzlpDgABOevKSsB4G/FA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 6" - } - }, - "node_modules/pkg-dir": { - "version": "4.2.0", - "resolved": "https://registry.npmjs.org/pkg-dir/-/pkg-dir-4.2.0.tgz", - "integrity": "sha512-HRDzbaKjC+AOWVXxAU/x54COGeIv9eb+6CkDSQoNTt4XyWoIJvuPsXizxu/Fr23EiekbtZwmh1IcIG/l/a10GQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "find-up": "^4.0.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/pkg-dir/node_modules/find-up": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/find-up/-/find-up-4.1.0.tgz", - "integrity": "sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==", - "dev": true, - "license": "MIT", - "dependencies": { - "locate-path": "^5.0.0", - "path-exists": "^4.0.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/pkg-dir/node_modules/locate-path": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-5.0.0.tgz", - "integrity": "sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==", - "dev": true, - "license": "MIT", - "dependencies": { - "p-locate": "^4.1.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/pkg-dir/node_modules/p-limit": { - "version": "2.3.0", - "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-2.3.0.tgz", - "integrity": "sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==", - "dev": true, - "license": "MIT", - "dependencies": { - "p-try": "^2.0.0" - }, - "engines": { - "node": ">=6" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/pkg-dir/node_modules/p-locate": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-4.1.0.tgz", - "integrity": "sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==", - "dev": true, - "license": "MIT", - "dependencies": { - "p-limit": "^2.2.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/pluralize": { - "version": "8.0.0", - "resolved": "https://registry.npmjs.org/pluralize/-/pluralize-8.0.0.tgz", - "integrity": "sha512-Nc3IT5yHzflTfbjgqWcCPpo7DaKy4FnpB0l/zCAW0Tc7jxAiuqSxHasntB3D7887LSrA93kDJ9IXovxJYxyLCA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=4" - } - }, - "node_modules/postcss": { - "version": "8.5.6", - "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.6.tgz", - "integrity": "sha512-3Ybi1tAuwAP9s0r1UQ2J4n5Y0G05bJkpUIO0/bI9MhwmD70S5aTWbXGBwxHrelT+XM1k6dM0pk+SwNkpTRN7Pg==", - "dev": true, - "funding": [ - { - "type": "opencollective", - "url": "https://opencollective.com/postcss/" - }, - { - "type": "tidelift", - "url": "https://tidelift.com/funding/github/npm/postcss" - }, - { - "type": "github", - "url": "https://github.com/sponsors/ai" - } - ], - "license": "MIT", - "dependencies": { - "nanoid": "^3.3.11", - "picocolors": "^1.1.1", - "source-map-js": "^1.2.1" - }, - "engines": { - "node": "^10 || ^12 || >=14" - } - }, - "node_modules/postcss-nested": { - "version": "6.2.0", - "resolved": "https://registry.npmjs.org/postcss-nested/-/postcss-nested-6.2.0.tgz", - "integrity": "sha512-HQbt28KulC5AJzG+cZtj9kvKB93CFCdLvog1WFLf1D+xmMvPGlBstkpTEZfK5+AN9hfJocyBFCNiqyS48bpgzQ==", - "dev": true, - "funding": [ - { - "type": "opencollective", - "url": "https://opencollective.com/postcss/" - }, - { - "type": "github", - "url": "https://github.com/sponsors/ai" - } - ], - "license": "MIT", - "dependencies": { - "postcss-selector-parser": "^6.1.1" - }, - "engines": { - "node": ">=12.0" - }, - "peerDependencies": { - "postcss": "^8.2.14" - } - }, - "node_modules/postcss-selector-parser": { - "version": "6.1.2", - "resolved": "https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-6.1.2.tgz", - "integrity": "sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg==", - "dev": true, - "license": "MIT", - "dependencies": { - "cssesc": "^3.0.0", - "util-deprecate": "^1.0.2" - }, - "engines": { - "node": ">=4" - } - }, - "node_modules/prelude-ls": { - "version": "1.2.1", - "resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.2.1.tgz", - "integrity": "sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/prettier": { - "version": "3.8.1", - "resolved": "https://registry.npmjs.org/prettier/-/prettier-3.8.1.tgz", - "integrity": "sha512-UOnG6LftzbdaHZcKoPFtOcCKztrQ57WkHDeRD9t/PTQtmT0NHSeWWepj6pS0z/N7+08BHFDQVUrfmfMRcZwbMg==", - "dev": true, - "license": "MIT", - "bin": { - "prettier": "bin/prettier.cjs" - }, - "engines": { - "node": ">=14" - }, - "funding": { - "url": "https://github.com/prettier/prettier?sponsor=1" - } - }, - "node_modules/prettier-plugin-packagejson": { - "version": "2.5.22", - "resolved": "https://registry.npmjs.org/prettier-plugin-packagejson/-/prettier-plugin-packagejson-2.5.22.tgz", - "integrity": "sha512-G6WalmoUssKF8ZXkni0+n4324K+gG143KPysSQNW+FrR0XyNb3BdRxchGC/Q1FE/F702p7/6KU7r4mv0WSWbzA==", - "dev": true, - "license": "MIT", - "dependencies": { - "sort-package-json": "3.6.0" - }, - "peerDependencies": { - "prettier": ">= 1.16.0" - }, - "peerDependenciesMeta": { - "prettier": { - "optional": true - } - } - }, - "node_modules/pretty-format": { - "version": "30.2.0", - "resolved": "https://registry.npmjs.org/pretty-format/-/pretty-format-30.2.0.tgz", - "integrity": "sha512-9uBdv/B4EefsuAL+pWqueZyZS2Ba+LxfFeQ9DN14HU4bN8bhaxKdkpjpB6fs9+pSjIBu+FXQHImEg8j/Lw0+vA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@jest/schemas": "30.0.5", - "ansi-styles": "^5.2.0", - "react-is": "^18.3.1" - }, - "engines": { - "node": "^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0" - } - }, - "node_modules/pretty-format/node_modules/ansi-styles": { - "version": "5.2.0", - "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-5.2.0.tgz", - "integrity": "sha512-Cxwpt2SfTzTtXcfOlzGEee8O+c+MmUgGrNiBcXnuWxuFJHe6a5Hz7qwhwe5OgaSYI0IJvkLqWX1ASG+cJOkEiA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/chalk/ansi-styles?sponsor=1" - } - }, - "node_modules/prismjs": { - "version": "1.30.0", - "resolved": "https://registry.npmjs.org/prismjs/-/prismjs-1.30.0.tgz", - "integrity": "sha512-DEvV2ZF2r2/63V+tK8hQvrR2ZGn10srHbXviTlcv7Kpzw8jWiNTqbVgjO3IY8RxrrOUF8VPMQQFysYYYv0YZxw==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/prompts": { - "version": "2.4.2", - "resolved": "https://registry.npmjs.org/prompts/-/prompts-2.4.2.tgz", - "integrity": "sha512-NxNv/kLguCA7p3jE8oL2aEBsrJWgAakBpgmgK6lpPWV+WuOmY6r2/zbAVnP+T8bQlA0nzHXSJSJW0Hq7ylaD2Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "kleur": "^3.0.3", - "sisteransi": "^1.0.5" - }, - "engines": { - "node": ">= 6" - } - }, - "node_modules/property-information": { - "version": "7.1.0", - "resolved": "https://registry.npmjs.org/property-information/-/property-information-7.1.0.tgz", - "integrity": "sha512-TwEZ+X+yCJmYfL7TPUOcvBZ4QfoT5YenQiJuX//0th53DE6w0xxLEtfK3iyryQFddXuvkIk51EEgrJQ0WJkOmQ==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/punycode": { - "version": "2.3.1", - "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.3.1.tgz", - "integrity": "sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/punycode.js": { - "version": "2.3.1", - "resolved": "https://registry.npmjs.org/punycode.js/-/punycode.js-2.3.1.tgz", - "integrity": "sha512-uxFIHU0YlHYhDQtV4R9J6a52SLx28BCjT+4ieh7IGbgwVJWO+km431c4yRlREUAsAmt/uMjQUyQHNEPf0M39CA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/pure-rand": { - "version": "7.0.1", - "resolved": "https://registry.npmjs.org/pure-rand/-/pure-rand-7.0.1.tgz", - "integrity": "sha512-oTUZM/NAZS8p7ANR3SHh30kXB+zK2r2BPcEn/awJIbOvq82WoMN4p62AWWp3Hhw50G0xMsw1mhIBLqHw64EcNQ==", - "dev": true, - "funding": [ - { - "type": "individual", - "url": "https://github.com/sponsors/dubzzz" - }, - { - "type": "opencollective", - "url": "https://opencollective.com/fast-check" - } - ], - "license": "MIT" - }, - "node_modules/queue-microtask": { - "version": "1.2.3", - "resolved": "https://registry.npmjs.org/queue-microtask/-/queue-microtask-1.2.3.tgz", - "integrity": "sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==", - "dev": true, - "funding": [ - { - "type": "github", - "url": "https://github.com/sponsors/feross" - }, - { - "type": "patreon", - "url": "https://www.patreon.com/feross" - }, - { - "type": "consulting", - "url": "https://feross.org/support" - } - ], - "license": "MIT" - }, - "node_modules/radix3": { - "version": "1.1.2", - "resolved": "https://registry.npmjs.org/radix3/-/radix3-1.1.2.tgz", - "integrity": "sha512-b484I/7b8rDEdSDKckSSBA8knMpcdsXudlE/LNL639wFoHKwLbEkQFZHWEYwDC0wa0FKUcCY+GAF73Z7wxNVFA==", - "dev": true, - "license": "MIT" - }, - "node_modules/react-is": { - "version": "18.3.1", - "resolved": "https://registry.npmjs.org/react-is/-/react-is-18.3.1.tgz", - "integrity": "sha512-/LLMVyas0ljjAtoYiPqYiL8VWXzUUdThrmU5+n20DZv+a+ClRoevUzw5JxU+Ieh5/c87ytoTBV9G1FiKfNJdmg==", - "dev": true, - "license": "MIT" - }, - "node_modules/readdirp": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/readdirp/-/readdirp-5.0.0.tgz", - "integrity": "sha512-9u/XQ1pvrQtYyMpZe7DXKv2p5CNvyVwzUB6uhLAnQwHMSgKMBR62lc7AHljaeteeHXn11XTAaLLUVZYVZyuRBQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 20.19.0" - }, - "funding": { - "type": "individual", - "url": "https://paulmillr.com/funding/" - } - }, - "node_modules/recma-build-jsx": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/recma-build-jsx/-/recma-build-jsx-1.0.0.tgz", - "integrity": "sha512-8GtdyqaBcDfva+GUKDr3nev3VpKAhup1+RvkMvUxURHpW7QyIvk9F5wz7Vzo06CEMSilw6uArgRqhpiUcWp8ew==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "estree-util-build-jsx": "^3.0.0", - "vfile": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/recma-jsx": { - "version": "1.0.1", - "resolved": "https://registry.npmjs.org/recma-jsx/-/recma-jsx-1.0.1.tgz", - "integrity": "sha512-huSIy7VU2Z5OLv6oFLosQGGDqPqdO1iq6bWNAdhzMxSJP7RAso4fCZ1cKu8j9YHCZf3TPrq4dw3okhrylgcd7w==", - "dev": true, - "license": "MIT", - "dependencies": { - "acorn-jsx": "^5.0.0", - "estree-util-to-js": "^2.0.0", - "recma-parse": "^1.0.0", - "recma-stringify": "^1.0.0", - "unified": "^11.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - }, - "peerDependencies": { - "acorn": "^6.0.0 || ^7.0.0 || ^8.0.0" - } - }, - "node_modules/recma-parse": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/recma-parse/-/recma-parse-1.0.0.tgz", - "integrity": "sha512-OYLsIGBB5Y5wjnSnQW6t3Xg7q3fQ7FWbw/vcXtORTnyaSFscOtABg+7Pnz6YZ6c27fG1/aN8CjfwoUEUIdwqWQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "esast-util-from-js": "^2.0.0", - "unified": "^11.0.0", - "vfile": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/recma-stringify": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/recma-stringify/-/recma-stringify-1.0.0.tgz", - "integrity": "sha512-cjwII1MdIIVloKvC9ErQ+OgAtwHBmcZ0Bg4ciz78FtbT8In39aAYbaA7zvxQ61xVMSPE8WxhLwLbhif4Js2C+g==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "estree-util-to-js": "^2.0.0", - "unified": "^11.0.0", - "vfile": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/regex": { - "version": "6.1.0", - "resolved": "https://registry.npmjs.org/regex/-/regex-6.1.0.tgz", - "integrity": "sha512-6VwtthbV4o/7+OaAF9I5L5V3llLEsoPyq9P1JVXkedTP33c7MfCG0/5NOPcSJn0TzXcG9YUrR0gQSWioew3LDg==", - "dev": true, - "license": "MIT", - "dependencies": { - "regex-utilities": "^2.3.0" - } - }, - "node_modules/regex-recursion": { - "version": "6.0.2", - "resolved": "https://registry.npmjs.org/regex-recursion/-/regex-recursion-6.0.2.tgz", - "integrity": "sha512-0YCaSCq2VRIebiaUviZNs0cBz1kg5kVS2UKUfNIx8YVs1cN3AV7NTctO5FOKBA+UT2BPJIWZauYHPqJODG50cg==", - "dev": true, - "license": "MIT", - "dependencies": { - "regex-utilities": "^2.3.0" - } - }, - "node_modules/regex-utilities": { - "version": "2.3.0", - "resolved": "https://registry.npmjs.org/regex-utilities/-/regex-utilities-2.3.0.tgz", - "integrity": "sha512-8VhliFJAWRaUiVvREIiW2NXXTmHs4vMNnSzuJVhscgmGav3g9VDxLrQndI3dZZVVdp0ZO/5v0xmX516/7M9cng==", - "dev": true, - "license": "MIT" - }, - "node_modules/regexp-tree": { - "version": "0.1.27", - "resolved": "https://registry.npmjs.org/regexp-tree/-/regexp-tree-0.1.27.tgz", - "integrity": "sha512-iETxpjK6YoRWJG5o6hXLwvjYAoW+FEZn9os0PD/b6AP6xQwsa/Y7lCVgIixBbUPMfhu+i2LtdeAqVTgGlQarfA==", - "dev": true, - "license": "MIT", - "bin": { - "regexp-tree": "bin/regexp-tree" - } - }, - "node_modules/regjsparser": { - "version": "0.12.0", - "resolved": "https://registry.npmjs.org/regjsparser/-/regjsparser-0.12.0.tgz", - "integrity": "sha512-cnE+y8bz4NhMjISKbgeVJtqNbtf5QpjZP+Bslo+UqkIt9QPnX9q095eiRRASJG1/tz6dlNr6Z5NsBiWYokp6EQ==", - "dev": true, - "license": "BSD-2-Clause", - "dependencies": { - "jsesc": "~3.0.2" - }, - "bin": { - "regjsparser": "bin/parser" - } - }, - "node_modules/regjsparser/node_modules/jsesc": { - "version": "3.0.2", - "resolved": "https://registry.npmjs.org/jsesc/-/jsesc-3.0.2.tgz", - "integrity": "sha512-xKqzzWXDttJuOcawBt4KnKHHIf5oQ/Cxax+0PWFG+DFDgHNAdi+TXECADI+RYiFUMmx8792xsMbbgXj4CwnP4g==", - "dev": true, - "license": "MIT", - "bin": { - "jsesc": "bin/jsesc" - }, - "engines": { - "node": ">=6" - } - }, - "node_modules/rehype": { - "version": "13.0.2", - "resolved": "https://registry.npmjs.org/rehype/-/rehype-13.0.2.tgz", - "integrity": "sha512-j31mdaRFrwFRUIlxGeuPXXKWQxet52RBQRvCmzl5eCefn/KGbomK5GMHNMsOJf55fgo3qw5tST5neDuarDYR2A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "rehype-parse": "^9.0.0", - "rehype-stringify": "^10.0.0", - "unified": "^11.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/rehype-expressive-code": { - "version": "0.41.6", - "resolved": "https://registry.npmjs.org/rehype-expressive-code/-/rehype-expressive-code-0.41.6.tgz", - "integrity": "sha512-aBMX8kxPtjmDSFUdZlAWJkMvsQ4ZMASfee90JWIAV8tweltXLzkWC3q++43ToTelI8ac5iC0B3/S/Cl4Ql1y2g==", - "dev": true, - "license": "MIT", - "dependencies": { - "expressive-code": "^0.41.6" - } - }, - "node_modules/rehype-format": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/rehype-format/-/rehype-format-5.0.1.tgz", - "integrity": "sha512-zvmVru9uB0josBVpr946OR8ui7nJEdzZobwLOOqHb/OOD88W0Vk2SqLwoVOj0fM6IPCCO6TaV9CvQvJMWwukFQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "hast-util-format": "^1.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/rehype-parse": { - "version": "9.0.1", - "resolved": "https://registry.npmjs.org/rehype-parse/-/rehype-parse-9.0.1.tgz", - "integrity": "sha512-ksCzCD0Fgfh7trPDxr2rSylbwq9iYDkSn8TCDmEJ49ljEUBxDVCzCHv7QNzZOfODanX4+bWQ4WZqLCRWYLfhag==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "hast-util-from-html": "^2.0.0", - "unified": "^11.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/rehype-raw": { - "version": "7.0.0", - "resolved": "https://registry.npmjs.org/rehype-raw/-/rehype-raw-7.0.0.tgz", - "integrity": "sha512-/aE8hCfKlQeA8LmyeyQvQF3eBiLRGNlfBJEvWH7ivp9sBqs7TNqBL5X3v157rM4IFETqDnIOO+z5M/biZbo9Ww==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "hast-util-raw": "^9.0.0", - "vfile": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/rehype-recma": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/rehype-recma/-/rehype-recma-1.0.0.tgz", - "integrity": "sha512-lqA4rGUf1JmacCNWWZx0Wv1dHqMwxzsDWYMTowuplHF3xH0N/MmrZ/G3BDZnzAkRmxDadujCjaKM2hqYdCBOGw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "^1.0.0", - "@types/hast": "^3.0.0", - "hast-util-to-estree": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/rehype-stringify": { - "version": "10.0.1", - "resolved": "https://registry.npmjs.org/rehype-stringify/-/rehype-stringify-10.0.1.tgz", - "integrity": "sha512-k9ecfXHmIPuFVI61B9DeLPN0qFHfawM6RsuX48hoqlaKSF61RskNjSm1lI8PhBEM0MRdLxVVm4WmTqJQccH9mA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "hast-util-to-html": "^9.0.0", - "unified": "^11.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/remark-directive": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/remark-directive/-/remark-directive-3.0.1.tgz", - "integrity": "sha512-gwglrEQEZcZYgVyG1tQuA+h58EZfq5CSULw7J90AFuCTyib1thgHPoqQ+h9iFvU6R+vnZ5oNFQR5QKgGpk741A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "mdast-util-directive": "^3.0.0", - "micromark-extension-directive": "^3.0.0", - "unified": "^11.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/remark-directive/node_modules/micromark-extension-directive": { - "version": "3.0.2", - "resolved": "https://registry.npmjs.org/micromark-extension-directive/-/micromark-extension-directive-3.0.2.tgz", - "integrity": "sha512-wjcXHgk+PPdmvR58Le9d7zQYWy+vKEU9Se44p2CrCDPiLr2FMyiT4Fyb5UFKFC66wGB3kPlgD7q3TnoqPS7SZA==", - "dev": true, - "license": "MIT", - "dependencies": { - "devlop": "^1.0.0", - "micromark-factory-space": "^2.0.0", - "micromark-factory-whitespace": "^2.0.0", - "micromark-util-character": "^2.0.0", - "micromark-util-symbol": "^2.0.0", - "micromark-util-types": "^2.0.0", - "parse-entities": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/remark-gfm": { - "version": "4.0.1", - "resolved": "https://registry.npmjs.org/remark-gfm/-/remark-gfm-4.0.1.tgz", - "integrity": "sha512-1quofZ2RQ9EWdeN34S79+KExV1764+wCUGop5CPL1WGdD0ocPpu91lzPGbwWMECpEpd42kJGQwzRfyov9j4yNg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "mdast-util-gfm": "^3.0.0", - "micromark-extension-gfm": "^3.0.0", - "remark-parse": "^11.0.0", - "remark-stringify": "^11.0.0", - "unified": "^11.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/remark-mdx": { - "version": "3.1.1", - "resolved": "https://registry.npmjs.org/remark-mdx/-/remark-mdx-3.1.1.tgz", - "integrity": "sha512-Pjj2IYlUY3+D8x00UJsIOg5BEvfMyeI+2uLPn9VO9Wg4MEtN/VTIq2NEJQfde9PnX15KgtHyl9S0BcTnWrIuWg==", - "dev": true, - "license": "MIT", - "dependencies": { - "mdast-util-mdx": "^3.0.0", - "micromark-extension-mdxjs": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/remark-parse": { - "version": "11.0.0", - "resolved": "https://registry.npmjs.org/remark-parse/-/remark-parse-11.0.0.tgz", - "integrity": "sha512-FCxlKLNGknS5ba/1lmpYijMUzX2esxW5xQqjWxw2eHFfS2MSdaHVINFmhjo+qN1WhZhNimq0dZATN9pH0IDrpA==", - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "mdast-util-from-markdown": "^2.0.0", - "micromark-util-types": "^2.0.0", - "unified": "^11.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/remark-rehype": { - "version": "11.1.2", - "resolved": "https://registry.npmjs.org/remark-rehype/-/remark-rehype-11.1.2.tgz", - "integrity": "sha512-Dh7l57ianaEoIpzbp0PC9UKAdCSVklD8E5Rpw7ETfbTl3FqcOOgq5q2LVDhgGCkaBv7p24JXikPdvhhmHvKMsw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/hast": "^3.0.0", - "@types/mdast": "^4.0.0", - "mdast-util-to-hast": "^13.0.0", - "unified": "^11.0.0", - "vfile": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/remark-smartypants": { - "version": "3.0.2", - "resolved": "https://registry.npmjs.org/remark-smartypants/-/remark-smartypants-3.0.2.tgz", - "integrity": "sha512-ILTWeOriIluwEvPjv67v7Blgrcx+LZOkAUVtKI3putuhlZm84FnqDORNXPPm+HY3NdZOMhyDwZ1E+eZB/Df5dA==", - "dev": true, - "license": "MIT", - "dependencies": { - "retext": "^9.0.0", - "retext-smartypants": "^6.0.0", - "unified": "^11.0.4", - "unist-util-visit": "^5.0.0" - }, - "engines": { - "node": ">=16.0.0" - } - }, - "node_modules/remark-stringify": { - "version": "11.0.0", - "resolved": "https://registry.npmjs.org/remark-stringify/-/remark-stringify-11.0.0.tgz", - "integrity": "sha512-1OSmLd3awB/t8qdoEOMazZkNsfVTeY4fTsgzcQFdXNq8ToTN4ZGwrMnlda4K6smTFKD+GRV6O48i6Z4iKgPPpw==", - "license": "MIT", - "dependencies": { - "@types/mdast": "^4.0.0", - "mdast-util-to-markdown": "^2.0.0", - "unified": "^11.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/require-directory": { - "version": "2.1.1", - "resolved": "https://registry.npmjs.org/require-directory/-/require-directory-2.1.1.tgz", - "integrity": "sha512-fGxEI7+wsG9xrvdjsrlmL22OMTTiHRwAMroiEeMgq8gzoLC/PQr7RsRDSTLUg/bZAZtF+TVIkHc6/4RIKrui+Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=0.10.0" - } - }, - "node_modules/resolve-cwd": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/resolve-cwd/-/resolve-cwd-3.0.0.tgz", - "integrity": "sha512-OrZaX2Mb+rJCpH/6CpSqt9xFVpN++x01XnN2ie9g6P5/3xelLAkXWVADpdz1IHD/KFfEXyE6V0U01OQ3UO2rEg==", - "dev": true, - "license": "MIT", - "dependencies": { - "resolve-from": "^5.0.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/resolve-cwd/node_modules/resolve-from": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-5.0.0.tgz", - "integrity": "sha512-qYg9KP24dD5qka9J47d0aVky0N+b4fTU89LN9iDnjB5waksiC49rvMB0PrUJQGoTmH50XPiqOvAjDfaijGxYZw==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/resolve-from": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-4.0.0.tgz", - "integrity": "sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=4" - } - }, - "node_modules/resolve-pkg-maps": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/resolve-pkg-maps/-/resolve-pkg-maps-1.0.0.tgz", - "integrity": "sha512-seS2Tj26TBVOC2NIc2rOe2y2ZO7efxITtLZcGSOnHHNOQ7CkiUBfw0Iw2ck6xkIhPwLhKNLS8BO+hEpngQlqzw==", - "dev": true, - "license": "MIT", - "funding": { - "url": "https://github.com/privatenumber/resolve-pkg-maps?sponsor=1" - } - }, - "node_modules/restore-cursor": { - "version": "5.1.0", - "resolved": "https://registry.npmjs.org/restore-cursor/-/restore-cursor-5.1.0.tgz", - "integrity": "sha512-oMA2dcrw6u0YfxJQXm342bFKX/E4sG9rbTzO9ptUcR/e8A33cHuvStiYOwH7fszkZlZ1z/ta9AAoPk2F4qIOHA==", - "dev": true, - "license": "MIT", - "dependencies": { - "onetime": "^7.0.0", - "signal-exit": "^4.1.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/restore-cursor/node_modules/onetime": { - "version": "7.0.0", - "resolved": "https://registry.npmjs.org/onetime/-/onetime-7.0.0.tgz", - "integrity": "sha512-VXJjc87FScF88uafS3JllDgvAm+c/Slfz06lorj2uAY34rlUu0Nt+v8wreiImcrgAjjIHp1rXpTDlLOGw29WwQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "mimic-function": "^5.0.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/retext": { - "version": "9.0.0", - "resolved": "https://registry.npmjs.org/retext/-/retext-9.0.0.tgz", - "integrity": "sha512-sbMDcpHCNjvlheSgMfEcVrZko3cDzdbe1x/e7G66dFp0Ff7Mldvi2uv6JkJQzdRcvLYE8CA8Oe8siQx8ZOgTcA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/nlcst": "^2.0.0", - "retext-latin": "^4.0.0", - "retext-stringify": "^4.0.0", - "unified": "^11.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/retext-latin": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/retext-latin/-/retext-latin-4.0.0.tgz", - "integrity": "sha512-hv9woG7Fy0M9IlRQloq/N6atV82NxLGveq+3H2WOi79dtIYWN8OaxogDm77f8YnVXJL2VD3bbqowu5E3EMhBYA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/nlcst": "^2.0.0", - "parse-latin": "^7.0.0", - "unified": "^11.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/retext-smartypants": { - "version": "6.2.0", - "resolved": "https://registry.npmjs.org/retext-smartypants/-/retext-smartypants-6.2.0.tgz", - "integrity": "sha512-kk0jOU7+zGv//kfjXEBjdIryL1Acl4i9XNkHxtM7Tm5lFiCog576fjNC9hjoR7LTKQ0DsPWy09JummSsH1uqfQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/nlcst": "^2.0.0", - "nlcst-to-string": "^4.0.0", - "unist-util-visit": "^5.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/retext-stringify": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/retext-stringify/-/retext-stringify-4.0.0.tgz", - "integrity": "sha512-rtfN/0o8kL1e+78+uxPTqu1Klt0yPzKuQ2BfWwwfgIUSayyzxpM1PJzkKt4V8803uB9qSy32MvI7Xep9khTpiA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/nlcst": "^2.0.0", - "nlcst-to-string": "^4.0.0", - "unified": "^11.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/reusify": { - "version": "1.1.0", - "resolved": "https://registry.npmjs.org/reusify/-/reusify-1.1.0.tgz", - "integrity": "sha512-g6QUff04oZpHs0eG5p83rFLhHeV00ug/Yf9nZM6fLeUrPguBTkTQOdpAWWspMh55TZfVQDPaN3NQJfbVRAxdIw==", - "dev": true, - "license": "MIT", - "engines": { - "iojs": ">=1.0.0", - "node": ">=0.10.0" - } - }, - "node_modules/rfdc": { - "version": "1.4.1", - "resolved": "https://registry.npmjs.org/rfdc/-/rfdc-1.4.1.tgz", - "integrity": "sha512-q1b3N5QkRUWUl7iyylaaj3kOpIT0N2i9MqIEQXP73GVsN9cw3fdx8X63cEmWhJGi2PPCF23Ijp7ktmd39rawIA==", - "dev": true, - "license": "MIT" - }, - "node_modules/rollup": { - "version": "4.57.1", - "resolved": "https://registry.npmjs.org/rollup/-/rollup-4.57.1.tgz", - "integrity": "sha512-oQL6lgK3e2QZeQ7gcgIkS2YZPg5slw37hYufJ3edKlfQSGGm8ICoxswK15ntSzF/a8+h7ekRy7k7oWc3BQ7y8A==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/estree": "1.0.8" - }, - "bin": { - "rollup": "dist/bin/rollup" - }, - "engines": { - "node": ">=18.0.0", - "npm": ">=8.0.0" - }, - "optionalDependencies": { - "@rollup/rollup-android-arm-eabi": "4.57.1", - "@rollup/rollup-android-arm64": "4.57.1", - "@rollup/rollup-darwin-arm64": "4.57.1", - "@rollup/rollup-darwin-x64": "4.57.1", - "@rollup/rollup-freebsd-arm64": "4.57.1", - "@rollup/rollup-freebsd-x64": "4.57.1", - "@rollup/rollup-linux-arm-gnueabihf": "4.57.1", - "@rollup/rollup-linux-arm-musleabihf": "4.57.1", - "@rollup/rollup-linux-arm64-gnu": "4.57.1", - "@rollup/rollup-linux-arm64-musl": "4.57.1", - "@rollup/rollup-linux-loong64-gnu": "4.57.1", - "@rollup/rollup-linux-loong64-musl": "4.57.1", - "@rollup/rollup-linux-ppc64-gnu": "4.57.1", - "@rollup/rollup-linux-ppc64-musl": "4.57.1", - "@rollup/rollup-linux-riscv64-gnu": "4.57.1", - "@rollup/rollup-linux-riscv64-musl": "4.57.1", - "@rollup/rollup-linux-s390x-gnu": "4.57.1", - "@rollup/rollup-linux-x64-gnu": "4.57.1", - "@rollup/rollup-linux-x64-musl": "4.57.1", - "@rollup/rollup-openbsd-x64": "4.57.1", - "@rollup/rollup-openharmony-arm64": "4.57.1", - "@rollup/rollup-win32-arm64-msvc": "4.57.1", - "@rollup/rollup-win32-ia32-msvc": "4.57.1", - "@rollup/rollup-win32-x64-gnu": "4.57.1", - "@rollup/rollup-win32-x64-msvc": "4.57.1", - "fsevents": "~2.3.2" - } - }, - "node_modules/run-parallel": { - "version": "1.2.0", - "resolved": "https://registry.npmjs.org/run-parallel/-/run-parallel-1.2.0.tgz", - "integrity": "sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==", - "dev": true, - "funding": [ - { - "type": "github", - "url": "https://github.com/sponsors/feross" - }, - { - "type": "patreon", - "url": "https://www.patreon.com/feross" - }, - { - "type": "consulting", - "url": "https://feross.org/support" - } - ], - "license": "MIT", - "dependencies": { - "queue-microtask": "^1.2.2" - } - }, - "node_modules/sax": { - "version": "1.4.4", - "resolved": "https://registry.npmjs.org/sax/-/sax-1.4.4.tgz", - "integrity": "sha512-1n3r/tGXO6b6VXMdFT54SHzT9ytu9yr7TaELowdYpMqY/Ao7EnlQGmAQ1+RatX7Tkkdm6hONI2owqNx2aZj5Sw==", - "license": "BlueOak-1.0.0", - "engines": { - "node": ">=11.0.0" - } - }, - "node_modules/secure-keys": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/secure-keys/-/secure-keys-1.0.0.tgz", - "integrity": "sha512-nZi59hW3Sl5P3+wOO89eHBAAGwmCPd2aE1+dLZV5MO+ItQctIvAqihzaAXIQhvtH4KJPxM080HsnqltR2y8cWg==", - "dev": true, - "license": "MIT" - }, - "node_modules/semver": { - "version": "7.7.3", - "resolved": "https://registry.npmjs.org/semver/-/semver-7.7.3.tgz", - "integrity": "sha512-SdsKMrI9TdgjdweUSR9MweHA4EJ8YxHn8DFaDisvhVlUOe4BF1tLD7GAj0lIqWVl+dPb/rExr0Btby5loQm20Q==", - "license": "ISC", - "bin": { - "semver": "bin/semver.js" - }, - "engines": { - "node": ">=10" - } - }, - "node_modules/sharp": { - "version": "0.33.5", - "resolved": "https://registry.npmjs.org/sharp/-/sharp-0.33.5.tgz", - "integrity": "sha512-haPVm1EkS9pgvHrQ/F3Xy+hgcuMV0Wm9vfIBSiwZ05k+xgb0PkBQpGsAA/oWdDobNaZTH5ppvHtzCFbnSEwHVw==", - "dev": true, - "hasInstallScript": true, - "license": "Apache-2.0", - "dependencies": { - "color": "^4.2.3", - "detect-libc": "^2.0.3", - "semver": "^7.6.3" - }, - "engines": { - "node": "^18.17.0 || ^20.3.0 || >=21.0.0" - }, - "funding": { - "url": "https://opencollective.com/libvips" - }, - "optionalDependencies": { - "@img/sharp-darwin-arm64": "0.33.5", - "@img/sharp-darwin-x64": "0.33.5", - "@img/sharp-libvips-darwin-arm64": "1.0.4", - "@img/sharp-libvips-darwin-x64": "1.0.4", - "@img/sharp-libvips-linux-arm": "1.0.5", - "@img/sharp-libvips-linux-arm64": "1.0.4", - "@img/sharp-libvips-linux-s390x": "1.0.4", - "@img/sharp-libvips-linux-x64": "1.0.4", - "@img/sharp-libvips-linuxmusl-arm64": "1.0.4", - "@img/sharp-libvips-linuxmusl-x64": "1.0.4", - "@img/sharp-linux-arm": "0.33.5", - "@img/sharp-linux-arm64": "0.33.5", - "@img/sharp-linux-s390x": "0.33.5", - "@img/sharp-linux-x64": "0.33.5", - "@img/sharp-linuxmusl-arm64": "0.33.5", - "@img/sharp-linuxmusl-x64": "0.33.5", - "@img/sharp-wasm32": "0.33.5", - "@img/sharp-win32-ia32": "0.33.5", - "@img/sharp-win32-x64": "0.33.5" - } - }, - "node_modules/shebang-command": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz", - "integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==", - "license": "MIT", - "dependencies": { - "shebang-regex": "^3.0.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/shebang-regex": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz", - "integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==", - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/shiki": { - "version": "3.21.0", - "resolved": "https://registry.npmjs.org/shiki/-/shiki-3.21.0.tgz", - "integrity": "sha512-N65B/3bqL/TI2crrXr+4UivctrAGEjmsib5rPMMPpFp1xAx/w03v8WZ9RDDFYteXoEgY7qZ4HGgl5KBIu1153w==", - "dev": true, - "license": "MIT", - "dependencies": { - "@shikijs/core": "3.21.0", - "@shikijs/engine-javascript": "3.21.0", - "@shikijs/engine-oniguruma": "3.21.0", - "@shikijs/langs": "3.21.0", - "@shikijs/themes": "3.21.0", - "@shikijs/types": "3.21.0", - "@shikijs/vscode-textmate": "^10.0.2", - "@types/hast": "^3.0.4" - } - }, - "node_modules/signal-exit": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/signal-exit/-/signal-exit-4.1.0.tgz", - "integrity": "sha512-bzyZ1e88w9O1iNJbKnOlvYTrWPDl46O1bG0D3XInv+9tkPrxrN8jUUTiFlDkkmKWgn1M6CfIA13SuGqOa9Korw==", - "license": "ISC", - "engines": { - "node": ">=14" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/simple-swizzle": { - "version": "0.2.4", - "resolved": "https://registry.npmjs.org/simple-swizzle/-/simple-swizzle-0.2.4.tgz", - "integrity": "sha512-nAu1WFPQSMNr2Zn9PGSZK9AGn4t/y97lEm+MXTtUDwfP0ksAIX4nO+6ruD9Jwut4C49SB1Ws+fbXsm/yScWOHw==", - "dev": true, - "license": "MIT", - "dependencies": { - "is-arrayish": "^0.3.1" - } - }, - "node_modules/simple-swizzle/node_modules/is-arrayish": { - "version": "0.3.4", - "resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.3.4.tgz", - "integrity": "sha512-m6UrgzFVUYawGBh1dUsWR5M2Clqic9RVXC/9f8ceNlv2IcO9j9J/z8UoCLPqtsPBFNzEpfR3xftohbfqDx8EQA==", - "dev": true, - "license": "MIT" - }, - "node_modules/sisteransi": { - "version": "1.0.5", - "resolved": "https://registry.npmjs.org/sisteransi/-/sisteransi-1.0.5.tgz", - "integrity": "sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==", - "license": "MIT" - }, - "node_modules/sitemap": { - "version": "8.0.2", - "resolved": "https://registry.npmjs.org/sitemap/-/sitemap-8.0.2.tgz", - "integrity": "sha512-LwktpJcyZDoa0IL6KT++lQ53pbSrx2c9ge41/SeLTyqy2XUNA6uR4+P9u5IVo5lPeL2arAcOKn1aZAxoYbCKlQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/node": "^17.0.5", - "@types/sax": "^1.2.1", - "arg": "^5.0.0", - "sax": "^1.4.1" - }, - "bin": { - "sitemap": "dist/cli.js" - }, - "engines": { - "node": ">=14.0.0", - "npm": ">=6.0.0" - } - }, - "node_modules/sitemap/node_modules/@types/node": { - "version": "17.0.45", - "resolved": "https://registry.npmjs.org/@types/node/-/node-17.0.45.tgz", - "integrity": "sha512-w+tIMs3rq2afQdsPJlODhoUEKzFP1ayaoyl1CcnwtIlsVe7K7bA1NGm4s3PraqTLlXnbIN84zuBlxBWo1u9BLw==", - "dev": true, - "license": "MIT" - }, - "node_modules/slash": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz", - "integrity": "sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/slice-ansi": { - "version": "7.1.2", - "resolved": "https://registry.npmjs.org/slice-ansi/-/slice-ansi-7.1.2.tgz", - "integrity": "sha512-iOBWFgUX7caIZiuutICxVgX1SdxwAVFFKwt1EvMYYec/NWO5meOJ6K5uQxhrYBdQJne4KxiqZc+KptFOWFSI9w==", - "dev": true, - "license": "MIT", - "dependencies": { - "ansi-styles": "^6.2.1", - "is-fullwidth-code-point": "^5.0.0" - }, - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/chalk/slice-ansi?sponsor=1" - } - }, - "node_modules/slice-ansi/node_modules/ansi-styles": { - "version": "6.2.3", - "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-6.2.3.tgz", - "integrity": "sha512-4Dj6M28JB+oAH8kFkTLUo+a2jwOFkuqb3yucU0CANcRRUbxS0cP0nZYCGjcc3BNXwRIsUVmDGgzawme7zvJHvg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/chalk/ansi-styles?sponsor=1" - } - }, - "node_modules/smol-toml": { - "version": "1.6.0", - "resolved": "https://registry.npmjs.org/smol-toml/-/smol-toml-1.6.0.tgz", - "integrity": "sha512-4zemZi0HvTnYwLfrpk/CF9LOd9Lt87kAt50GnqhMpyF9U3poDAP2+iukq2bZsO/ufegbYehBkqINbsWxj4l4cw==", - "dev": true, - "license": "BSD-3-Clause", - "engines": { - "node": ">= 18" - }, - "funding": { - "url": "https://github.com/sponsors/cyyynthia" - } - }, - "node_modules/sort-object-keys": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/sort-object-keys/-/sort-object-keys-2.1.0.tgz", - "integrity": "sha512-SOiEnthkJKPv2L6ec6HMwhUcN0/lppkeYuN1x63PbyPRrgSPIuBJCiYxYyvWRTtjMlOi14vQUCGUJqS6PLVm8g==", - "dev": true, - "license": "MIT" - }, - "node_modules/sort-package-json": { - "version": "3.6.0", - "resolved": "https://registry.npmjs.org/sort-package-json/-/sort-package-json-3.6.0.tgz", - "integrity": "sha512-fyJsPLhWvY7u2KsKPZn1PixbXp+1m7V8NWqU8CvgFRbMEX41Ffw1kD8n0CfJiGoaSfoAvbrqRRl/DcHO8omQOQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "detect-indent": "^7.0.2", - "detect-newline": "^4.0.1", - "git-hooks-list": "^4.1.1", - "is-plain-obj": "^4.1.0", - "semver": "^7.7.3", - "sort-object-keys": "^2.0.1", - "tinyglobby": "^0.2.15" - }, - "bin": { - "sort-package-json": "cli.js" - }, - "engines": { - "node": ">=20" - } - }, - "node_modules/sort-package-json/node_modules/detect-newline": { - "version": "4.0.1", - "resolved": "https://registry.npmjs.org/detect-newline/-/detect-newline-4.0.1.tgz", - "integrity": "sha512-qE3Veg1YXzGHQhlA6jzebZN2qVf6NX+A7m7qlhCGG30dJixrAQhYOsJjsnBjJkCSmuOPpCk30145fr8FV0bzog==", - "dev": true, - "license": "MIT", - "engines": { - "node": "^12.20.0 || ^14.13.1 || >=16.0.0" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/source-map": { - "version": "0.7.6", - "resolved": "https://registry.npmjs.org/source-map/-/source-map-0.7.6.tgz", - "integrity": "sha512-i5uvt8C3ikiWeNZSVZNWcfZPItFQOsYTUAOkcUPGd8DqDy1uOUikjt5dG+uRlwyvR108Fb9DOd4GvXfT0N2/uQ==", - "dev": true, - "license": "BSD-3-Clause", - "engines": { - "node": ">= 12" - } - }, - "node_modules/source-map-js": { - "version": "1.2.1", - "resolved": "https://registry.npmjs.org/source-map-js/-/source-map-js-1.2.1.tgz", - "integrity": "sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA==", - "dev": true, - "license": "BSD-3-Clause", - "engines": { - "node": ">=0.10.0" - } - }, - "node_modules/source-map-support": { - "version": "0.5.13", - "resolved": "https://registry.npmjs.org/source-map-support/-/source-map-support-0.5.13.tgz", - "integrity": "sha512-SHSKFHadjVA5oR4PPqhtAVdcBWwRYVd6g6cAXnIbRiIwc2EhPrTuKUBdSLvlEKyIP3GCf89fltvcZiP9MMFA1w==", - "dev": true, - "license": "MIT", - "dependencies": { - "buffer-from": "^1.0.0", - "source-map": "^0.6.0" - } - }, - "node_modules/source-map-support/node_modules/source-map": { - "version": "0.6.1", - "resolved": "https://registry.npmjs.org/source-map/-/source-map-0.6.1.tgz", - "integrity": "sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==", - "dev": true, - "license": "BSD-3-Clause", - "engines": { - "node": ">=0.10.0" - } - }, - "node_modules/space-separated-tokens": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/space-separated-tokens/-/space-separated-tokens-2.0.2.tgz", - "integrity": "sha512-PEGlAwrG8yXGXRjW32fGbg66JAlOAwbObuqVoJpv/mRgoWDQfgH1wDPvtzWyUSNAXBGSk8h755YDbbcEy3SH2Q==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/sprintf-js": { - "version": "1.0.3", - "resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz", - "integrity": "sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==", - "dev": true, - "license": "BSD-3-Clause" - }, - "node_modules/stack-utils": { - "version": "2.0.6", - "resolved": "https://registry.npmjs.org/stack-utils/-/stack-utils-2.0.6.tgz", - "integrity": "sha512-XlkWvfIm6RmsWtNJx+uqtKLS8eqFbxUg0ZzLXqY0caEy9l7hruX8IpiDnjsLavoBgqCCR71TqWO8MaXYheJ3RQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "escape-string-regexp": "^2.0.0" - }, - "engines": { - "node": ">=10" - } - }, - "node_modules/stack-utils/node_modules/escape-string-regexp": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-2.0.0.tgz", - "integrity": "sha512-UpzcLCXolUWcNu5HtVMHYdXJjArjsF9C0aNnquZYY4uW/Vu0miy5YoWvbV345HauVvcAUnpRuhMMcqTcGOY2+w==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/stream-replace-string": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/stream-replace-string/-/stream-replace-string-2.0.0.tgz", - "integrity": "sha512-TlnjJ1C0QrmxRNrON00JvaFFlNh5TTG00APw23j74ET7gkQpTASi6/L2fuiav8pzK715HXtUeClpBTw2NPSn6w==", - "dev": true, - "license": "MIT" - }, - "node_modules/string-argv": { - "version": "0.3.2", - "resolved": "https://registry.npmjs.org/string-argv/-/string-argv-0.3.2.tgz", - "integrity": "sha512-aqD2Q0144Z+/RqG52NeHEkZauTAUWJO8c6yTftGJKO3Tja5tUgIfmIl6kExvhtxSDP7fXB6DvzkfMpCd/F3G+Q==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=0.6.19" - } - }, - "node_modules/string-length": { - "version": "4.0.2", - "resolved": "https://registry.npmjs.org/string-length/-/string-length-4.0.2.tgz", - "integrity": "sha512-+l6rNN5fYHNhZZy41RXsYptCjA2Igmq4EG7kZAYFQI1E1VTXarr6ZPXBg6eq7Y6eK4FEhY6AJlyuFIb/v/S0VQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "char-regex": "^1.0.2", - "strip-ansi": "^6.0.0" - }, - "engines": { - "node": ">=10" - } - }, - "node_modules/string-length/node_modules/ansi-regex": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", - "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/string-length/node_modules/strip-ansi": { - "version": "6.0.1", - "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", - "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", - "dev": true, - "license": "MIT", - "dependencies": { - "ansi-regex": "^5.0.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/string-width": { - "version": "4.2.3", - "resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz", - "integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==", - "license": "MIT", - "dependencies": { - "emoji-regex": "^8.0.0", - "is-fullwidth-code-point": "^3.0.0", - "strip-ansi": "^6.0.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/string-width-cjs": { - "name": "string-width", - "version": "4.2.3", - "resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz", - "integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==", - "license": "MIT", - "dependencies": { - "emoji-regex": "^8.0.0", - "is-fullwidth-code-point": "^3.0.0", - "strip-ansi": "^6.0.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/string-width-cjs/node_modules/ansi-regex": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", - "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/string-width-cjs/node_modules/is-fullwidth-code-point": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz", - "integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==", - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/string-width-cjs/node_modules/strip-ansi": { - "version": "6.0.1", - "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", - "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", - "license": "MIT", - "dependencies": { - "ansi-regex": "^5.0.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/string-width/node_modules/ansi-regex": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", - "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/string-width/node_modules/is-fullwidth-code-point": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-3.0.0.tgz", - "integrity": "sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==", - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/string-width/node_modules/strip-ansi": { - "version": "6.0.1", - "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", - "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", - "license": "MIT", - "dependencies": { - "ansi-regex": "^5.0.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/stringify-entities": { - "version": "4.0.4", - "resolved": "https://registry.npmjs.org/stringify-entities/-/stringify-entities-4.0.4.tgz", - "integrity": "sha512-IwfBptatlO+QCJUo19AqvrPNqlVMpW9YEL2LIVY+Rpv2qsjCGxaDLNRgeGsQWJhfItebuJhsGSLjaBbNSQ+ieg==", - "dev": true, - "license": "MIT", - "dependencies": { - "character-entities-html4": "^2.0.0", - "character-entities-legacy": "^3.0.0" - }, - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/strip-ansi": { - "version": "7.1.2", - "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-7.1.2.tgz", - "integrity": "sha512-gmBGslpoQJtgnMAvOVqGZpEz9dyoKTCzy2nfz/n8aIFhN/jCE/rCmcxabB6jOOHV+0WNnylOxaxBQPSvcWklhA==", - "license": "MIT", - "dependencies": { - "ansi-regex": "^6.0.1" - }, - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/chalk/strip-ansi?sponsor=1" - } - }, - "node_modules/strip-ansi-cjs": { - "name": "strip-ansi", - "version": "6.0.1", - "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", - "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", - "license": "MIT", - "dependencies": { - "ansi-regex": "^5.0.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/strip-ansi-cjs/node_modules/ansi-regex": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", - "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/strip-bom": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-4.0.0.tgz", - "integrity": "sha512-3xurFv5tEgii33Zi8Jtp55wEIILR9eh34FAW00PZf+JnSsTmV/ioewSgQl97JHvgjoRGwPShsWm+IdrxB35d0w==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/strip-final-newline": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/strip-final-newline/-/strip-final-newline-2.0.0.tgz", - "integrity": "sha512-BrpvfNAE3dcvq7ll3xVumzjKjZQ5tI1sEUIKr3Uoks0XUl45St3FlatVqef9prk4jRDzhW6WZg+3bk93y6pLjA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - } - }, - "node_modules/strip-indent": { - "version": "4.1.1", - "resolved": "https://registry.npmjs.org/strip-indent/-/strip-indent-4.1.1.tgz", - "integrity": "sha512-SlyRoSkdh1dYP0PzclLE7r0M9sgbFKKMFXpFRUMNuKhQSbC6VQIGzq3E0qsfvGJaUFJPGv6Ws1NZ/haTAjfbMA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/strip-json-comments": { - "version": "3.1.1", - "resolved": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-3.1.1.tgz", - "integrity": "sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/style-to-js": { - "version": "1.1.21", - "resolved": "https://registry.npmjs.org/style-to-js/-/style-to-js-1.1.21.tgz", - "integrity": "sha512-RjQetxJrrUJLQPHbLku6U/ocGtzyjbJMP9lCNK7Ag0CNh690nSH8woqWH9u16nMjYBAok+i7JO1NP2pOy8IsPQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "style-to-object": "1.0.14" - } - }, - "node_modules/style-to-object": { - "version": "1.0.14", - "resolved": "https://registry.npmjs.org/style-to-object/-/style-to-object-1.0.14.tgz", - "integrity": "sha512-LIN7rULI0jBscWQYaSswptyderlarFkjQ+t79nzty8tcIAceVomEVlLzH5VP4Cmsv6MtKhs7qaAiwlcp+Mgaxw==", - "dev": true, - "license": "MIT", - "dependencies": { - "inline-style-parser": "0.2.7" - } - }, - "node_modules/supports-color": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz", - "integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==", - "license": "MIT", - "dependencies": { - "has-flag": "^4.0.0" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/svgo": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/svgo/-/svgo-4.0.0.tgz", - "integrity": "sha512-VvrHQ+9uniE+Mvx3+C9IEe/lWasXCU0nXMY2kZeLrHNICuRiC8uMPyM14UEaMOFA5mhyQqEkB02VoQ16n3DLaw==", - "dev": true, - "license": "MIT", - "dependencies": { - "commander": "^11.1.0", - "css-select": "^5.1.0", - "css-tree": "^3.0.1", - "css-what": "^6.1.0", - "csso": "^5.0.5", - "picocolors": "^1.1.1", - "sax": "^1.4.1" - }, - "bin": { - "svgo": "bin/svgo.js" - }, - "engines": { - "node": ">=16" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/svgo" - } - }, - "node_modules/svgo/node_modules/commander": { - "version": "11.1.0", - "resolved": "https://registry.npmjs.org/commander/-/commander-11.1.0.tgz", - "integrity": "sha512-yPVavfyCcRhmorC7rWlkHn15b4wDVgVmBA7kV4QVBsF7kv/9TKJAbAXVTxvTnwP8HHKjRCJDClKbciiYS7p0DQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=16" - } - }, - "node_modules/synckit": { - "version": "0.11.12", - "resolved": "https://registry.npmjs.org/synckit/-/synckit-0.11.12.tgz", - "integrity": "sha512-Bh7QjT8/SuKUIfObSXNHNSK6WHo6J1tHCqJsuaFDP7gP0fkzSfTxI8y85JrppZ0h8l0maIgc2tfuZQ6/t3GtnQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@pkgr/core": "^0.2.9" - }, - "engines": { - "node": "^14.18.0 || >=16.0.0" - }, - "funding": { - "url": "https://opencollective.com/synckit" - } - }, - "node_modules/tapable": { - "version": "2.3.0", - "resolved": "https://registry.npmjs.org/tapable/-/tapable-2.3.0.tgz", - "integrity": "sha512-g9ljZiwki/LfxmQADO3dEY1CbpmXT5Hm2fJ+QaGKwSXUylMybePR7/67YW7jOrrvjEgL1Fmz5kzyAjWVWLlucg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=6" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/webpack" - } - }, - "node_modules/test-exclude": { - "version": "7.0.1", - "resolved": "https://registry.npmjs.org/test-exclude/-/test-exclude-7.0.1.tgz", - "integrity": "sha512-pFYqmTw68LXVjeWJMST4+borgQP2AyMNbg1BpZh9LbyhUeNkeaPF9gzfPGUAnSMV3qPYdWUwDIjjCLiSDOl7vg==", - "dev": true, - "license": "ISC", - "dependencies": { - "@istanbuljs/schema": "^0.1.2", - "glob": "^10.4.1", - "minimatch": "^9.0.4" - }, - "engines": { - "node": ">=18" - } - }, - "node_modules/test-exclude/node_modules/brace-expansion": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.2.tgz", - "integrity": "sha512-Jt0vHyM+jmUBqojB7E1NIYadt0vI0Qxjxd2TErW94wDz+E2LAm5vKMXXwg6ZZBTHPuUlDgQHKXvjGBdfcF1ZDQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "balanced-match": "^1.0.0" - } - }, - "node_modules/test-exclude/node_modules/glob": { - "version": "10.5.0", - "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz", - "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==", - "dev": true, - "license": "ISC", - "dependencies": { - "foreground-child": "^3.1.0", - "jackspeak": "^3.1.2", - "minimatch": "^9.0.4", - "minipass": "^7.1.2", - "package-json-from-dist": "^1.0.0", - "path-scurry": "^1.11.1" - }, - "bin": { - "glob": "dist/esm/bin.mjs" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/test-exclude/node_modules/jackspeak": { - "version": "3.4.3", - "resolved": "https://registry.npmjs.org/jackspeak/-/jackspeak-3.4.3.tgz", - "integrity": "sha512-OGlZQpz2yfahA/Rd1Y8Cd9SIEsqvXkLVoSw/cgwhnhFMDbsQFeZYoJJ7bIZBS9BcamUW96asq/npPWugM+RQBw==", - "dev": true, - "license": "BlueOak-1.0.0", - "dependencies": { - "@isaacs/cliui": "^8.0.2" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - }, - "optionalDependencies": { - "@pkgjs/parseargs": "^0.11.0" - } - }, - "node_modules/test-exclude/node_modules/lru-cache": { - "version": "10.4.3", - "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-10.4.3.tgz", - "integrity": "sha512-JNAzZcXrCt42VGLuYz0zfAzDfAvJWW6AfYlDBQyDV5DClI2m5sAmK+OIO7s59XfsRsWHp02jAJrRadPRGTt6SQ==", - "dev": true, - "license": "ISC" - }, - "node_modules/test-exclude/node_modules/minimatch": { - "version": "9.0.5", - "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz", - "integrity": "sha512-G6T0ZX48xgozx7587koeX9Ys2NYy6Gmv//P89sEte9V9whIapMNF4idKxnW2QtCcLiTWlb/wfCabAtAFWhhBow==", - "dev": true, - "license": "ISC", - "dependencies": { - "brace-expansion": "^2.0.1" - }, - "engines": { - "node": ">=16 || 14 >=14.17" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/test-exclude/node_modules/path-scurry": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/path-scurry/-/path-scurry-1.11.1.tgz", - "integrity": "sha512-Xa4Nw17FS9ApQFJ9umLiJS4orGjm7ZzwUrwamcGQuHSzDyth9boKDaycYdDcZDuqYATXw4HFXgaqWTctW/v1HA==", - "dev": true, - "license": "BlueOak-1.0.0", - "dependencies": { - "lru-cache": "^10.2.0", - "minipass": "^5.0.0 || ^6.0.2 || ^7.0.0" - }, - "engines": { - "node": ">=16 || 14 >=14.18" - }, - "funding": { - "url": "https://github.com/sponsors/isaacs" - } - }, - "node_modules/tiny-inflate": { - "version": "1.0.3", - "resolved": "https://registry.npmjs.org/tiny-inflate/-/tiny-inflate-1.0.3.tgz", - "integrity": "sha512-pkY1fj1cKHb2seWDy0B16HeWyczlJA9/WW3u3c4z/NiWDsO3DOU5D7nhTLE9CF0yXv/QZFY7sEJmj24dK+Rrqw==", - "dev": true, - "license": "MIT" - }, - "node_modules/tinyexec": { - "version": "1.0.2", - "resolved": "https://registry.npmjs.org/tinyexec/-/tinyexec-1.0.2.tgz", - "integrity": "sha512-W/KYk+NFhkmsYpuHq5JykngiOCnxeVL8v8dFnqxSD8qEEdRfXk1SDM6JzNqcERbcGYj9tMrDQBYV9cjgnunFIg==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - } - }, - "node_modules/tinyglobby": { - "version": "0.2.15", - "resolved": "https://registry.npmjs.org/tinyglobby/-/tinyglobby-0.2.15.tgz", - "integrity": "sha512-j2Zq4NyQYG5XMST4cbs02Ak8iJUdxRM0XI5QyxXuZOzKOINmWurp3smXu3y5wDcJrptwpSjgXHzIQxR0omXljQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "fdir": "^6.5.0", - "picomatch": "^4.0.3" - }, - "engines": { - "node": ">=12.0.0" - }, - "funding": { - "url": "https://github.com/sponsors/SuperchupuDev" - } - }, - "node_modules/tmpl": { - "version": "1.0.5", - "resolved": "https://registry.npmjs.org/tmpl/-/tmpl-1.0.5.tgz", - "integrity": "sha512-3f0uOEAQwIqGuWW2MVzYg8fV/QNnc/IpuJNG837rLuczAaLVHslWHZQj4IGiEl5Hs3kkbhwL9Ab7Hrsmuj+Smw==", - "dev": true, - "license": "BSD-3-Clause" - }, - "node_modules/to-regex-range": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz", - "integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "is-number": "^7.0.0" - }, - "engines": { - "node": ">=8.0" - } - }, - "node_modules/trim-lines": { - "version": "3.0.1", - "resolved": "https://registry.npmjs.org/trim-lines/-/trim-lines-3.0.1.tgz", - "integrity": "sha512-kRj8B+YHZCc9kQYdWfJB2/oUl9rA99qbowYYBtr4ui4mZyAQ2JpvVBd/6U2YloATfqBhBTSMhTpgBHtU0Mf3Rg==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/trough": { - "version": "2.2.0", - "resolved": "https://registry.npmjs.org/trough/-/trough-2.2.0.tgz", - "integrity": "sha512-tmMpK00BjZiUyVyvrBK7knerNgmgvcV/KLVyuma/SC+TQN167GrMRciANTz09+k3zW8L8t60jWO1GpfkZdjTaw==", - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/ts-declaration-location": { - "version": "1.0.7", - "resolved": "https://registry.npmjs.org/ts-declaration-location/-/ts-declaration-location-1.0.7.tgz", - "integrity": "sha512-EDyGAwH1gO0Ausm9gV6T2nUvBgXT5kGoCMJPllOaooZ+4VvJiKBdZE7wK18N1deEowhcUptS+5GXZK8U/fvpwA==", - "dev": true, - "funding": [ - { - "type": "ko-fi", - "url": "https://ko-fi.com/rebeccastevens" - }, - { - "type": "tidelift", - "url": "https://tidelift.com/funding/github/npm/ts-declaration-location" - } - ], - "license": "BSD-3-Clause", - "dependencies": { - "picomatch": "^4.0.2" - }, - "peerDependencies": { - "typescript": ">=4.0.0" - } - }, - "node_modules/tsconfck": { - "version": "3.1.6", - "resolved": "https://registry.npmjs.org/tsconfck/-/tsconfck-3.1.6.tgz", - "integrity": "sha512-ks6Vjr/jEw0P1gmOVwutM3B7fWxoWBL2KRDb1JfqGVawBmO5UsvmWOQFGHBPl5yxYz4eERr19E6L7NMv+Fej4w==", - "dev": true, - "license": "MIT", - "bin": { - "tsconfck": "bin/tsconfck.js" - }, - "engines": { - "node": "^18 || >=20" - }, - "peerDependencies": { - "typescript": "^5.0.0" - }, - "peerDependenciesMeta": { - "typescript": { - "optional": true - } - } - }, - "node_modules/tslib": { - "version": "2.8.1", - "resolved": "https://registry.npmjs.org/tslib/-/tslib-2.8.1.tgz", - "integrity": "sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==", - "dev": true, - "license": "0BSD", - "optional": true - }, - "node_modules/type-check": { - "version": "0.4.0", - "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz", - "integrity": "sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==", - "dev": true, - "license": "MIT", - "dependencies": { - "prelude-ls": "^1.2.1" - }, - "engines": { - "node": ">= 0.8.0" - } - }, - "node_modules/type-detect": { - "version": "4.0.8", - "resolved": "https://registry.npmjs.org/type-detect/-/type-detect-4.0.8.tgz", - "integrity": "sha512-0fr/mIH1dlO+x7TlcMy+bIDqKPsw/70tVyeHW787goQjhmqaZe10uwLujubK9q9Lg6Fiho1KUKDYz0Z7k7g5/g==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=4" - } - }, - "node_modules/uc.micro": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/uc.micro/-/uc.micro-2.1.0.tgz", - "integrity": "sha512-ARDJmphmdvUk6Glw7y9DQ2bFkKBHwQHLi2lsaH6PPmz/Ka9sFOBsBluozhDltWmnv9u/cF6Rt87znRTPV+yp/A==", - "dev": true, - "license": "MIT" - }, - "node_modules/ufo": { - "version": "1.6.3", - "resolved": "https://registry.npmjs.org/ufo/-/ufo-1.6.3.tgz", - "integrity": "sha512-yDJTmhydvl5lJzBmy/hyOAA0d+aqCBuwl818haVdYCRrWV84o7YyeVm4QlVHStqNrrJSTb6jKuFAVqAFsr+K3Q==", - "dev": true, - "license": "MIT" - }, - "node_modules/ultrahtml": { - "version": "1.6.0", - "resolved": "https://registry.npmjs.org/ultrahtml/-/ultrahtml-1.6.0.tgz", - "integrity": "sha512-R9fBn90VTJrqqLDwyMph+HGne8eqY1iPfYhPzZrvKpIfwkWZbcYlfpsb8B9dTvBfpy1/hqAD7Wi8EKfP9e8zdw==", - "dev": true, - "license": "MIT" - }, - "node_modules/uncrypto": { - "version": "0.1.3", - "resolved": "https://registry.npmjs.org/uncrypto/-/uncrypto-0.1.3.tgz", - "integrity": "sha512-Ql87qFHB3s/De2ClA9e0gsnS6zXG27SkTiSJwjCc9MebbfapQfuPzumMIUMi38ezPZVNFcHI9sUIepeQfw8J8Q==", - "dev": true, - "license": "MIT" - }, - "node_modules/undici-types": { - "version": "7.16.0", - "resolved": "https://registry.npmjs.org/undici-types/-/undici-types-7.16.0.tgz", - "integrity": "sha512-Zz+aZWSj8LE6zoxD+xrjh4VfkIG8Ya6LvYkZqtUQGJPZjYl53ypCaUwWqo7eI0x66KBGeRo+mlBEkMSeSZ38Nw==", - "dev": true, - "license": "MIT" - }, - "node_modules/unicorn-magic": { - "version": "0.3.0", - "resolved": "https://registry.npmjs.org/unicorn-magic/-/unicorn-magic-0.3.0.tgz", - "integrity": "sha512-+QBBXBCvifc56fsbuxZQ6Sic3wqqc3WWaqxs58gvJrcOuN83HGTCwz3oS5phzU9LthRNE9VrJCFCLUgHeeFnfA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/unified": { - "version": "11.0.5", - "resolved": "https://registry.npmjs.org/unified/-/unified-11.0.5.tgz", - "integrity": "sha512-xKvGhPWw3k84Qjh8bI3ZeJjqnyadK+GEFtazSfZv/rKeTkTjOJho6mFqh2SM96iIcZokxiOpg78GazTSg8+KHA==", - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0", - "bail": "^2.0.0", - "devlop": "^1.0.0", - "extend": "^3.0.0", - "is-plain-obj": "^4.0.0", - "trough": "^2.0.0", - "vfile": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unifont": { - "version": "0.7.3", - "resolved": "https://registry.npmjs.org/unifont/-/unifont-0.7.3.tgz", - "integrity": "sha512-b0GtQzKCyuSHGsfj5vyN8st7muZ6VCI4XD4vFlr7Uy1rlWVYxC3npnfk8MyreHxJYrz1ooLDqDzFe9XqQTlAhA==", - "dev": true, - "license": "MIT", - "dependencies": { - "css-tree": "^3.1.0", - "ofetch": "^1.5.1", - "ohash": "^2.0.11" - } - }, - "node_modules/unist-util-find": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/unist-util-find/-/unist-util-find-3.0.0.tgz", - "integrity": "sha512-T7ZqS7immLjYyC4FCp2hDo3ksZ1v+qcbb+e5+iWxc2jONgHOLXPCpms1L8VV4hVxCXgWTxmBHDztuEZFVwC+Gg==", - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0", - "lodash.iteratee": "^4.0.0", - "unist-util-visit": "^5.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unist-util-find-after": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/unist-util-find-after/-/unist-util-find-after-5.0.0.tgz", - "integrity": "sha512-amQa0Ep2m6hE2g72AugUItjbuM8X8cGQnFoHk0pGfrFeT9GZhzN5SW8nRsiGKK7Aif4CrACPENkA6P/Lw6fHGQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0", - "unist-util-is": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unist-util-is": { - "version": "6.0.1", - "resolved": "https://registry.npmjs.org/unist-util-is/-/unist-util-is-6.0.1.tgz", - "integrity": "sha512-LsiILbtBETkDz8I9p1dQ0uyRUWuaQzd/cuEeS1hoRSyW5E5XGmTzlwY1OrNzzakGowI9Dr/I8HVaw4hTtnxy8g==", - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unist-util-modify-children": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/unist-util-modify-children/-/unist-util-modify-children-4.0.0.tgz", - "integrity": "sha512-+tdN5fGNddvsQdIzUF3Xx82CU9sMM+fA0dLgR9vOmT0oPT2jH+P1nd5lSqfCfXAw+93NhcXNY2qqvTUtE4cQkw==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0", - "array-iterate": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unist-util-position": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/unist-util-position/-/unist-util-position-5.0.0.tgz", - "integrity": "sha512-fucsC7HjXvkB5R3kTCO7kUjRdrS0BJt3M/FPxmHMBOm8JQi2BsHAHFsy27E0EolP8rp0NzXsJ+jNPyDWvOJZPA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unist-util-position-from-estree": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/unist-util-position-from-estree/-/unist-util-position-from-estree-2.0.0.tgz", - "integrity": "sha512-KaFVRjoqLyF6YXCbVLNad/eS4+OfPQQn2yOd7zF/h5T/CSL2v8NpN6a5TPvtbXthAGw5nG+PuTtq+DdIZr+cRQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unist-util-remove-position": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/unist-util-remove-position/-/unist-util-remove-position-5.0.0.tgz", - "integrity": "sha512-Hp5Kh3wLxv0PHj9m2yZhhLt58KzPtEYKQQ4yxfYFEO7EvHwzyDYnduhHnY1mDxoqr7VUwVuHXk9RXKIiYS1N8Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0", - "unist-util-visit": "^5.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unist-util-select": { - "version": "5.1.0", - "resolved": "https://registry.npmjs.org/unist-util-select/-/unist-util-select-5.1.0.tgz", - "integrity": "sha512-4A5mfokSHG/rNQ4g7gSbdEs+H586xyd24sdJqF1IWamqrLHvYb+DH48fzxowyOhOfK7YSqX+XlCojAyuuyyT2A==", - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0", - "css-selector-parser": "^3.0.0", - "devlop": "^1.1.0", - "nth-check": "^2.0.0", - "zwitch": "^2.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unist-util-stringify-position": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/unist-util-stringify-position/-/unist-util-stringify-position-4.0.0.tgz", - "integrity": "sha512-0ASV06AAoKCDkS2+xw5RXJywruurpbC4JZSm7nr7MOt1ojAzvyyaO+UxZf18j8FCF6kmzCZKcAgN/yu2gm2XgQ==", - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unist-util-visit": { - "version": "5.1.0", - "resolved": "https://registry.npmjs.org/unist-util-visit/-/unist-util-visit-5.1.0.tgz", - "integrity": "sha512-m+vIdyeCOpdr/QeQCu2EzxX/ohgS8KbnPDgFni4dQsfSCtpz8UqDyY5GjRru8PDKuYn7Fq19j1CQ+nJSsGKOzg==", - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0", - "unist-util-is": "^6.0.0", - "unist-util-visit-parents": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unist-util-visit-children": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/unist-util-visit-children/-/unist-util-visit-children-3.0.0.tgz", - "integrity": "sha512-RgmdTfSBOg04sdPcpTSD1jzoNBjt9a80/ZCzp5cI9n1qPzLZWF9YdvWGN2zmTumP1HWhXKdUWexjy/Wy/lJ7tA==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/unist-util-visit-parents": { - "version": "6.0.2", - "resolved": "https://registry.npmjs.org/unist-util-visit-parents/-/unist-util-visit-parents-6.0.2.tgz", - "integrity": "sha512-goh1s1TBrqSqukSc8wrjwWhL0hiJxgA8m4kFxGlQ+8FYQ3C/m11FcTs4YYem7V664AhHVvgoQLk890Ssdsr2IQ==", - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0", - "unist-util-is": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/universalify": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/universalify/-/universalify-2.0.1.tgz", - "integrity": "sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw==", - "license": "MIT", - "engines": { - "node": ">= 10.0.0" - } - }, - "node_modules/unrs-resolver": { - "version": "1.11.1", - "resolved": "https://registry.npmjs.org/unrs-resolver/-/unrs-resolver-1.11.1.tgz", - "integrity": "sha512-bSjt9pjaEBnNiGgc9rUiHGKv5l4/TGzDmYw3RhnkJGtLhbnnA/5qJj7x3dNDCRx/PJxu774LlH8lCOlB4hEfKg==", - "dev": true, - "hasInstallScript": true, - "license": "MIT", - "dependencies": { - "napi-postinstall": "^0.3.0" - }, - "funding": { - "url": "https://opencollective.com/unrs-resolver" - }, - "optionalDependencies": { - "@unrs/resolver-binding-android-arm-eabi": "1.11.1", - "@unrs/resolver-binding-android-arm64": "1.11.1", - "@unrs/resolver-binding-darwin-arm64": "1.11.1", - "@unrs/resolver-binding-darwin-x64": "1.11.1", - "@unrs/resolver-binding-freebsd-x64": "1.11.1", - "@unrs/resolver-binding-linux-arm-gnueabihf": "1.11.1", - "@unrs/resolver-binding-linux-arm-musleabihf": "1.11.1", - "@unrs/resolver-binding-linux-arm64-gnu": "1.11.1", - "@unrs/resolver-binding-linux-arm64-musl": "1.11.1", - "@unrs/resolver-binding-linux-ppc64-gnu": "1.11.1", - "@unrs/resolver-binding-linux-riscv64-gnu": "1.11.1", - "@unrs/resolver-binding-linux-riscv64-musl": "1.11.1", - "@unrs/resolver-binding-linux-s390x-gnu": "1.11.1", - "@unrs/resolver-binding-linux-x64-gnu": "1.11.1", - "@unrs/resolver-binding-linux-x64-musl": "1.11.1", - "@unrs/resolver-binding-wasm32-wasi": "1.11.1", - "@unrs/resolver-binding-win32-arm64-msvc": "1.11.1", - "@unrs/resolver-binding-win32-ia32-msvc": "1.11.1", - "@unrs/resolver-binding-win32-x64-msvc": "1.11.1" - } - }, - "node_modules/unstorage": { - "version": "1.17.4", - "resolved": "https://registry.npmjs.org/unstorage/-/unstorage-1.17.4.tgz", - "integrity": "sha512-fHK0yNg38tBiJKp/Vgsq4j0JEsCmgqH58HAn707S7zGkArbZsVr/CwINoi+nh3h98BRCwKvx1K3Xg9u3VV83sw==", - "dev": true, - "license": "MIT", - "dependencies": { - "anymatch": "^3.1.3", - "chokidar": "^5.0.0", - "destr": "^2.0.5", - "h3": "^1.15.5", - "lru-cache": "^11.2.0", - "node-fetch-native": "^1.6.7", - "ofetch": "^1.5.1", - "ufo": "^1.6.3" - }, - "peerDependencies": { - "@azure/app-configuration": "^1.8.0", - "@azure/cosmos": "^4.2.0", - "@azure/data-tables": "^13.3.0", - "@azure/identity": "^4.6.0", - "@azure/keyvault-secrets": "^4.9.0", - "@azure/storage-blob": "^12.26.0", - "@capacitor/preferences": "^6 || ^7 || ^8", - "@deno/kv": ">=0.9.0", - "@netlify/blobs": "^6.5.0 || ^7.0.0 || ^8.1.0 || ^9.0.0 || ^10.0.0", - "@planetscale/database": "^1.19.0", - "@upstash/redis": "^1.34.3", - "@vercel/blob": ">=0.27.1", - "@vercel/functions": "^2.2.12 || ^3.0.0", - "@vercel/kv": "^1 || ^2 || ^3", - "aws4fetch": "^1.0.20", - "db0": ">=0.2.1", - "idb-keyval": "^6.2.1", - "ioredis": "^5.4.2", - "uploadthing": "^7.4.4" - }, - "peerDependenciesMeta": { - "@azure/app-configuration": { - "optional": true - }, - "@azure/cosmos": { - "optional": true - }, - "@azure/data-tables": { - "optional": true - }, - "@azure/identity": { - "optional": true - }, - "@azure/keyvault-secrets": { - "optional": true - }, - "@azure/storage-blob": { - "optional": true - }, - "@capacitor/preferences": { - "optional": true - }, - "@deno/kv": { - "optional": true - }, - "@netlify/blobs": { - "optional": true - }, - "@planetscale/database": { - "optional": true - }, - "@upstash/redis": { - "optional": true - }, - "@vercel/blob": { - "optional": true - }, - "@vercel/functions": { - "optional": true - }, - "@vercel/kv": { - "optional": true - }, - "aws4fetch": { - "optional": true - }, - "db0": { - "optional": true - }, - "idb-keyval": { - "optional": true - }, - "ioredis": { - "optional": true - }, - "uploadthing": { - "optional": true - } - } - }, - "node_modules/unstorage/node_modules/lru-cache": { - "version": "11.2.5", - "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-11.2.5.tgz", - "integrity": "sha512-vFrFJkWtJvJnD5hg+hJvVE8Lh/TcMzKnTgCWmtBipwI5yLX/iX+5UB2tfuyODF5E7k9xEzMdYgGqaSb1c0c5Yw==", - "dev": true, - "license": "BlueOak-1.0.0", - "engines": { - "node": "20 || >=22" - } - }, - "node_modules/update-browserslist-db": { - "version": "1.2.3", - "resolved": "https://registry.npmjs.org/update-browserslist-db/-/update-browserslist-db-1.2.3.tgz", - "integrity": "sha512-Js0m9cx+qOgDxo0eMiFGEueWztz+d4+M3rGlmKPT+T4IS/jP4ylw3Nwpu6cpTTP8R1MAC1kF4VbdLt3ARf209w==", - "dev": true, - "funding": [ - { - "type": "opencollective", - "url": "https://opencollective.com/browserslist" - }, - { - "type": "tidelift", - "url": "https://tidelift.com/funding/github/npm/browserslist" - }, - { - "type": "github", - "url": "https://github.com/sponsors/ai" - } - ], - "license": "MIT", - "dependencies": { - "escalade": "^3.2.0", - "picocolors": "^1.1.1" - }, - "bin": { - "update-browserslist-db": "cli.js" - }, - "peerDependencies": { - "browserslist": ">= 4.21.0" - } - }, - "node_modules/uri-js": { - "version": "4.4.1", - "resolved": "https://registry.npmjs.org/uri-js/-/uri-js-4.4.1.tgz", - "integrity": "sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==", - "dev": true, - "license": "BSD-2-Clause", - "dependencies": { - "punycode": "^2.1.0" - } - }, - "node_modules/util-deprecate": { - "version": "1.0.2", - "resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz", - "integrity": "sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==", - "dev": true, - "license": "MIT" - }, - "node_modules/v8-to-istanbul": { - "version": "9.3.0", - "resolved": "https://registry.npmjs.org/v8-to-istanbul/-/v8-to-istanbul-9.3.0.tgz", - "integrity": "sha512-kiGUalWN+rgBJ/1OHZsBtU4rXZOfj/7rKQxULKlIzwzQSvMJUUNgPwJEEh7gU6xEVxC0ahoOBvN2YI8GH6FNgA==", - "dev": true, - "license": "ISC", - "dependencies": { - "@jridgewell/trace-mapping": "^0.3.12", - "@types/istanbul-lib-coverage": "^2.0.1", - "convert-source-map": "^2.0.0" - }, - "engines": { - "node": ">=10.12.0" - } - }, - "node_modules/vfile": { - "version": "6.0.3", - "resolved": "https://registry.npmjs.org/vfile/-/vfile-6.0.3.tgz", - "integrity": "sha512-KzIbH/9tXat2u30jf+smMwFCsno4wHVdNmzFyL+T/L3UGqqk6JKfVqOFOZEpZSHADH1k40ab6NUIXZq422ov3Q==", - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0", - "vfile-message": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/vfile-location": { - "version": "5.0.3", - "resolved": "https://registry.npmjs.org/vfile-location/-/vfile-location-5.0.3.tgz", - "integrity": "sha512-5yXvWDEgqeiYiBe1lbxYF7UMAIm/IcopxMHrMQDq3nvKcjPKIhZklUKL+AE7J7uApI4kwe2snsK+eI6UTj9EHg==", - "dev": true, - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0", - "vfile": "^6.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/vfile-message": { - "version": "4.0.3", - "resolved": "https://registry.npmjs.org/vfile-message/-/vfile-message-4.0.3.tgz", - "integrity": "sha512-QTHzsGd1EhbZs4AsQ20JX1rC3cOlt/IWJruk893DfLRr57lcnOeMaWG4K0JrRta4mIJZKth2Au3mM3u03/JWKw==", - "license": "MIT", - "dependencies": { - "@types/unist": "^3.0.0", - "unist-util-stringify-position": "^4.0.0" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/unified" - } - }, - "node_modules/vite": { - "version": "6.4.1", - "resolved": "https://registry.npmjs.org/vite/-/vite-6.4.1.tgz", - "integrity": "sha512-+Oxm7q9hDoLMyJOYfUYBuHQo+dkAloi33apOPP56pzj+vsdJDzr+j1NISE5pyaAuKL4A3UD34qd0lx5+kfKp2g==", - "dev": true, - "license": "MIT", - "dependencies": { - "esbuild": "^0.25.0", - "fdir": "^6.4.4", - "picomatch": "^4.0.2", - "postcss": "^8.5.3", - "rollup": "^4.34.9", - "tinyglobby": "^0.2.13" - }, - "bin": { - "vite": "bin/vite.js" - }, - "engines": { - "node": "^18.0.0 || ^20.0.0 || >=22.0.0" - }, - "funding": { - "url": "https://github.com/vitejs/vite?sponsor=1" - }, - "optionalDependencies": { - "fsevents": "~2.3.3" - }, - "peerDependencies": { - "@types/node": "^18.0.0 || ^20.0.0 || >=22.0.0", - "jiti": ">=1.21.0", - "less": "*", - "lightningcss": "^1.21.0", - "sass": "*", - "sass-embedded": "*", - "stylus": "*", - "sugarss": "*", - "terser": "^5.16.0", - "tsx": "^4.8.1", - "yaml": "^2.4.2" - }, - "peerDependenciesMeta": { - "@types/node": { - "optional": true - }, - "jiti": { - "optional": true - }, - "less": { - "optional": true - }, - "lightningcss": { - "optional": true - }, - "sass": { - "optional": true - }, - "sass-embedded": { - "optional": true - }, - "stylus": { - "optional": true - }, - "sugarss": { - "optional": true - }, - "terser": { - "optional": true - }, - "tsx": { - "optional": true - }, - "yaml": { - "optional": true - } - } - }, - "node_modules/vitefu": { - "version": "1.1.1", - "resolved": "https://registry.npmjs.org/vitefu/-/vitefu-1.1.1.tgz", - "integrity": "sha512-B/Fegf3i8zh0yFbpzZ21amWzHmuNlLlmJT6n7bu5e+pCHUKQIfXSYokrqOBGEMMe9UG2sostKQF9mml/vYaWJQ==", - "dev": true, - "license": "MIT", - "workspaces": [ - "tests/deps/*", - "tests/projects/*", - "tests/projects/workspace/packages/*" - ], - "peerDependencies": { - "vite": "^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0-beta.0" - }, - "peerDependenciesMeta": { - "vite": { - "optional": true - } - } - }, - "node_modules/walker": { - "version": "1.0.8", - "resolved": "https://registry.npmjs.org/walker/-/walker-1.0.8.tgz", - "integrity": "sha512-ts/8E8l5b7kY0vlWLewOkDXMmPdLcVV4GmOQLyxuSswIJsweeFZtAsMF7k1Nszz+TYBQrlYRmzOnr398y1JemQ==", - "dev": true, - "license": "Apache-2.0", - "dependencies": { - "makeerror": "1.0.12" - } - }, - "node_modules/web-namespaces": { - "version": "2.0.1", - "resolved": "https://registry.npmjs.org/web-namespaces/-/web-namespaces-2.0.1.tgz", - "integrity": "sha512-bKr1DkiNa2krS7qxNtdrtHAmzuYGFQLiQ13TsorsdT6ULTkPLKuu5+GsFpDlg6JFjUTwX2DyhMPG2be8uPrqsQ==", - "dev": true, - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - }, - "node_modules/which": { - "version": "2.0.2", - "resolved": "https://registry.npmjs.org/which/-/which-2.0.2.tgz", - "integrity": "sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==", - "license": "ISC", - "dependencies": { - "isexe": "^2.0.0" - }, - "bin": { - "node-which": "bin/node-which" - }, - "engines": { - "node": ">= 8" - } - }, - "node_modules/which-pm-runs": { - "version": "1.1.0", - "resolved": "https://registry.npmjs.org/which-pm-runs/-/which-pm-runs-1.1.0.tgz", - "integrity": "sha512-n1brCuqClxfFfq/Rb0ICg9giSZqCS+pLtccdag6C2HyufBrh3fBOiy9nb6ggRMvWOVH5GrdJskj5iGTZNxd7SA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=4" - } - }, - "node_modules/word-wrap": { - "version": "1.2.5", - "resolved": "https://registry.npmjs.org/word-wrap/-/word-wrap-1.2.5.tgz", - "integrity": "sha512-BN22B5eaMMI9UMtjrGd5g5eCYPpCPDUy0FJXbYsaT5zYxjFOckS53SQDE3pWkVoWpHXVb3BrYcEN4Twa55B5cA==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=0.10.0" - } - }, - "node_modules/wrap-ansi": { - "version": "7.0.0", - "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz", - "integrity": "sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==", - "dev": true, - "license": "MIT", - "dependencies": { - "ansi-styles": "^4.0.0", - "string-width": "^4.1.0", - "strip-ansi": "^6.0.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/chalk/wrap-ansi?sponsor=1" - } - }, - "node_modules/wrap-ansi-cjs": { - "name": "wrap-ansi", - "version": "7.0.0", - "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz", - "integrity": "sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==", - "license": "MIT", - "dependencies": { - "ansi-styles": "^4.0.0", - "string-width": "^4.1.0", - "strip-ansi": "^6.0.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/chalk/wrap-ansi?sponsor=1" - } - }, - "node_modules/wrap-ansi-cjs/node_modules/ansi-regex": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", - "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/wrap-ansi-cjs/node_modules/strip-ansi": { - "version": "6.0.1", - "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", - "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", - "license": "MIT", - "dependencies": { - "ansi-regex": "^5.0.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/wrap-ansi/node_modules/ansi-regex": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", - "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=8" - } - }, - "node_modules/wrap-ansi/node_modules/strip-ansi": { - "version": "6.0.1", - "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", - "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", - "dev": true, - "license": "MIT", - "dependencies": { - "ansi-regex": "^5.0.1" - }, - "engines": { - "node": ">=8" - } - }, - "node_modules/wrappy": { - "version": "1.0.2", - "resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz", - "integrity": "sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==", - "dev": true, - "license": "ISC" - }, - "node_modules/write-file-atomic": { - "version": "5.0.1", - "resolved": "https://registry.npmjs.org/write-file-atomic/-/write-file-atomic-5.0.1.tgz", - "integrity": "sha512-+QU2zd6OTD8XWIJCbffaiQeH9U73qIqafo1x6V1snCWYGJf6cVE0cDR4D8xRzcEnfI21IFrUPzPGtcPf8AC+Rw==", - "dev": true, - "license": "ISC", - "dependencies": { - "imurmurhash": "^0.1.4", - "signal-exit": "^4.0.1" - }, - "engines": { - "node": "^14.17.0 || ^16.13.0 || >=18.0.0" - } - }, - "node_modules/xml2js": { - "version": "0.6.2", - "resolved": "https://registry.npmjs.org/xml2js/-/xml2js-0.6.2.tgz", - "integrity": "sha512-T4rieHaC1EXcES0Kxxj4JWgaUQHDk+qwHcYOCFHfiwKz7tOVPLq7Hjq9dM1WCMhylqMEfP7hMcOIChvotiZegA==", - "license": "MIT", - "dependencies": { - "sax": ">=0.6.0", - "xmlbuilder": "~11.0.0" - }, - "engines": { - "node": ">=4.0.0" - } - }, - "node_modules/xmlbuilder": { - "version": "11.0.1", - "resolved": "https://registry.npmjs.org/xmlbuilder/-/xmlbuilder-11.0.1.tgz", - "integrity": "sha512-fDlsI/kFEx7gLvbecc0/ohLG50fugQp8ryHzMTuW9vSa1GJ0XYWKnhsUx7oie3G98+r56aTQIUB4kht42R3JvA==", - "license": "MIT", - "engines": { - "node": ">=4.0" - } - }, - "node_modules/xxhash-wasm": { - "version": "1.1.0", - "resolved": "https://registry.npmjs.org/xxhash-wasm/-/xxhash-wasm-1.1.0.tgz", - "integrity": "sha512-147y/6YNh+tlp6nd/2pWq38i9h6mz/EuQ6njIrmW8D1BS5nCqs0P6DG+m6zTGnNz5I+uhZ0SHxBs9BsPrwcKDA==", - "dev": true, - "license": "MIT" - }, - "node_modules/y18n": { - "version": "5.0.8", - "resolved": "https://registry.npmjs.org/y18n/-/y18n-5.0.8.tgz", - "integrity": "sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==", - "dev": true, - "license": "ISC", - "engines": { - "node": ">=10" - } - }, - "node_modules/yallist": { - "version": "3.1.1", - "resolved": "https://registry.npmjs.org/yallist/-/yallist-3.1.1.tgz", - "integrity": "sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==", - "dev": true, - "license": "ISC" - }, - "node_modules/yaml": { - "version": "2.8.2", - "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.8.2.tgz", - "integrity": "sha512-mplynKqc1C2hTVYxd0PU2xQAc22TI1vShAYGksCCfxbn/dFwnHTNi1bvYsBTkhdUNtGIf5xNOg938rrSSYvS9A==", - "license": "ISC", - "bin": { - "yaml": "bin.mjs" - }, - "engines": { - "node": ">= 14.6" - }, - "funding": { - "url": "https://github.com/sponsors/eemeli" - } - }, - "node_modules/yaml-eslint-parser": { - "version": "1.3.2", - "resolved": "https://registry.npmjs.org/yaml-eslint-parser/-/yaml-eslint-parser-1.3.2.tgz", - "integrity": "sha512-odxVsHAkZYYglR30aPYRY4nUGJnoJ2y1ww2HDvZALo0BDETv9kWbi16J52eHs+PWRNmF4ub6nZqfVOeesOvntg==", - "dev": true, - "license": "MIT", - "dependencies": { - "eslint-visitor-keys": "^3.0.0", - "yaml": "^2.0.0" - }, - "engines": { - "node": "^14.17.0 || >=16.0.0" - }, - "funding": { - "url": "https://github.com/sponsors/ota-meshi" - } - }, - "node_modules/yaml-eslint-parser/node_modules/eslint-visitor-keys": { - "version": "3.4.3", - "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-3.4.3.tgz", - "integrity": "sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==", - "dev": true, - "license": "Apache-2.0", - "engines": { - "node": "^12.22.0 || ^14.17.0 || >=16.0.0" - }, - "funding": { - "url": "https://opencollective.com/eslint" - } - }, - "node_modules/yaml-lint": { - "version": "1.7.0", - "resolved": "https://registry.npmjs.org/yaml-lint/-/yaml-lint-1.7.0.tgz", - "integrity": "sha512-zeBC/kskKQo4zuoGQ+IYjw6C9a/YILr2SXoEZA9jM0COrSwvwVbfTiFegT8qYBSBgOwLMWGL8sY137tOmFXGnQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "consola": "^2.15.3", - "globby": "^11.1.0", - "js-yaml": "^4.1.0", - "nconf": "^0.12.0" - }, - "bin": { - "yamllint": "dist/cli.js" - } - }, - "node_modules/yaml-lint/node_modules/globby": { - "version": "11.1.0", - "resolved": "https://registry.npmjs.org/globby/-/globby-11.1.0.tgz", - "integrity": "sha512-jhIXaOzy1sb8IyocaruWSn1TjmnBVs8Ayhcy83rmxNJ8q2uWKCAj3CnJY+KpGSXCueAPc0i05kVvVKtP1t9S3g==", - "dev": true, - "license": "MIT", - "dependencies": { - "array-union": "^2.1.0", - "dir-glob": "^3.0.1", - "fast-glob": "^3.2.9", - "ignore": "^5.2.0", - "merge2": "^1.4.1", - "slash": "^3.0.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/yaml-lint/node_modules/ignore": { - "version": "5.3.2", - "resolved": "https://registry.npmjs.org/ignore/-/ignore-5.3.2.tgz", - "integrity": "sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">= 4" - } - }, - "node_modules/yargs": { - "version": "17.7.2", - "resolved": "https://registry.npmjs.org/yargs/-/yargs-17.7.2.tgz", - "integrity": "sha512-7dSzzRQ++CKnNI/krKnYRV7JKKPUXMEh61soaHKg9mrWEhzFWhFnxPxGl+69cD1Ou63C13NUPCnmIcrvqCuM6w==", - "dev": true, - "license": "MIT", - "dependencies": { - "cliui": "^8.0.1", - "escalade": "^3.1.1", - "get-caller-file": "^2.0.5", - "require-directory": "^2.1.1", - "string-width": "^4.2.3", - "y18n": "^5.0.5", - "yargs-parser": "^21.1.1" - }, - "engines": { - "node": ">=12" - } - }, - "node_modules/yargs-parser": { - "version": "21.1.1", - "resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-21.1.1.tgz", - "integrity": "sha512-tVpsJW7DdjecAiFpbIB1e3qxIQsE6NoPc5/eTdrbbIC4h0LVsWhnoa3g+m2HclBIujHzsxZ4VJVA+GUuc2/LBw==", - "dev": true, - "license": "ISC", - "engines": { - "node": ">=12" - } - }, - "node_modules/yocto-queue": { - "version": "1.2.2", - "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-1.2.2.tgz", - "integrity": "sha512-4LCcse/U2MHZ63HAJVE+v71o7yOdIe4cZ70Wpf8D/IyjDKYQLV5GD46B+hSTjJsvV5PztjvHoU580EftxjDZFQ==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=12.20" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/yocto-spinner": { - "version": "0.2.3", - "resolved": "https://registry.npmjs.org/yocto-spinner/-/yocto-spinner-0.2.3.tgz", - "integrity": "sha512-sqBChb33loEnkoXte1bLg45bEBsOP9N1kzQh5JZNKj/0rik4zAPTNSAVPj3uQAdc6slYJ0Ksc403G2XgxsJQFQ==", - "dev": true, - "license": "MIT", - "dependencies": { - "yoctocolors": "^2.1.1" - }, - "engines": { - "node": ">=18.19" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/yoctocolors": { - "version": "2.1.2", - "resolved": "https://registry.npmjs.org/yoctocolors/-/yoctocolors-2.1.2.tgz", - "integrity": "sha512-CzhO+pFNo8ajLM2d2IW/R93ipy99LWjtwblvC1RsoSUMZgyLbYFr221TnSNT7GjGdYui6P459mw9JH/g/zW2ug==", - "dev": true, - "license": "MIT", - "engines": { - "node": ">=18" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, - "node_modules/zod": { - "version": "3.25.76", - "resolved": "https://registry.npmjs.org/zod/-/zod-3.25.76.tgz", - "integrity": "sha512-gzUt/qt81nXsFGKIFcC3YnfEAx5NkunCfnDlvuBSSFS02bcXu4Lmea0AFIUwbLWxWPx3d9p8S5QoaujKcNQxcQ==", - "dev": true, - "license": "MIT", - "funding": { - "url": "https://github.com/sponsors/colinhacks" - } - }, - "node_modules/zod-to-json-schema": { - "version": "3.25.1", - "resolved": "https://registry.npmjs.org/zod-to-json-schema/-/zod-to-json-schema-3.25.1.tgz", - "integrity": "sha512-pM/SU9d3YAggzi6MtR4h7ruuQlqKtad8e9S0fmxcMi+ueAK5Korys/aWcV9LIIHTVbj01NdzxcnXSN+O74ZIVA==", - "dev": true, - "license": "ISC", - "peerDependencies": { - "zod": "^3.25 || ^4" - } - }, - "node_modules/zod-to-ts": { - "version": "1.2.0", - "resolved": "https://registry.npmjs.org/zod-to-ts/-/zod-to-ts-1.2.0.tgz", - "integrity": "sha512-x30XE43V+InwGpvTySRNz9kB7qFU8DlyEy7BsSTCHPH1R0QasMmHWZDCzYm6bVXtj/9NNJAZF3jW8rzFvH5OFA==", - "dev": true, - "peerDependencies": { - "typescript": "^4.9.4 || ^5.0.2", - "zod": "^3" - } - }, - "node_modules/zwitch": { - "version": "2.0.4", - "resolved": "https://registry.npmjs.org/zwitch/-/zwitch-2.0.4.tgz", - "integrity": "sha512-bXE4cR/kVZhKZX/RjPEflHaKVhUVl85noU3v6b8apfQEc1x4A+zBxjZ4lN8LqGd6WZ3dl98pY4o717VFmoPp+A==", - "license": "MIT", - "funding": { - "type": "github", - "url": "https://github.com/sponsors/wooorm" - } - } - } -} diff --git a/package.json b/package.json deleted file mode 100644 index f3207f5fa..000000000 --- a/package.json +++ /dev/null @@ -1,110 +0,0 @@ -{ - "$schema": "https://json.schemastore.org/package.json", - "name": "bmad-method", - "version": "6.0.4", - "description": "Breakthrough Method of Agile AI-driven Development", - "keywords": [ - "agile", - "ai", - "orchestrator", - "development", - "methodology", - "agents", - "bmad" - ], - "repository": { - "type": "git", - "url": "git+https://github.com/bmad-code-org/BMAD-METHOD.git" - }, - "license": "MIT", - "author": "Brian (BMad) Madison", - "main": "tools/cli/bmad-cli.js", - "bin": { - "bmad": "tools/bmad-npx-wrapper.js", - "bmad-method": "tools/bmad-npx-wrapper.js" - }, - "scripts": { - "bmad:install": "node tools/cli/bmad-cli.js install", - "bmad:uninstall": "node tools/cli/bmad-cli.js uninstall", - "docs:build": "node tools/build-docs.mjs", - "docs:dev": "astro dev --root website", - "docs:fix-links": "node tools/fix-doc-links.js", - "docs:preview": "astro preview --root website", - "docs:validate-links": "node tools/validate-doc-links.js", - "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,yaml}\"", - "format:fix": "prettier --write \"**/*.{js,cjs,mjs,json,yaml}\"", - "format:fix:staged": "prettier --write", - "install:bmad": "node tools/cli/bmad-cli.js install", - "lint": "eslint . --ext .js,.cjs,.mjs,.yaml --max-warnings=0", - "lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix", - "lint:md": "markdownlint-cli2 \"**/*.md\"", - "prepare": "command -v husky >/dev/null 2>&1 && husky || exit 0", - "rebundle": "node tools/cli/bundlers/bundle-web.js rebundle", - "test": "npm run test:schemas && npm run test:refs && npm run test:install && npm run validate:schemas && npm run lint && npm run lint:md && npm run format:check", - "test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas", - "test:install": "node test/test-installation-components.js", - "test:refs": "node test/test-file-refs-csv.js", - "test:schemas": "node test/test-agent-schema.js", - "validate:refs": "node tools/validate-file-refs.js --strict", - "validate:schemas": "node tools/validate-agent-schema.js" - }, - "lint-staged": { - "*.{js,cjs,mjs}": [ - "npm run lint:fix", - "npm run format:fix:staged" - ], - "*.yaml": [ - "eslint --fix", - "npm run format:fix:staged" - ], - "*.json": [ - "npm run format:fix:staged" - ], - "*.md": [ - "markdownlint-cli2" - ] - }, - "dependencies": { - "@clack/core": "^1.0.0", - "@clack/prompts": "^1.0.0", - "@kayvan/markdown-tree-parser": "^1.6.1", - "chalk": "^4.1.2", - "commander": "^14.0.0", - "csv-parse": "^6.1.0", - "fs-extra": "^11.3.0", - "glob": "^11.0.3", - "ignore": "^7.0.5", - "js-yaml": "^4.1.0", - "picocolors": "^1.1.1", - "semver": "^7.6.3", - "xml2js": "^0.6.2", - "yaml": "^2.7.0" - }, - "devDependencies": { - "@astrojs/sitemap": "^3.6.0", - "@astrojs/starlight": "^0.37.5", - "@eslint/js": "^9.33.0", - "astro": "^5.16.0", - "c8": "^10.1.3", - "eslint": "^9.33.0", - "eslint-config-prettier": "^10.1.8", - "eslint-plugin-n": "^17.21.3", - "eslint-plugin-unicorn": "^60.0.0", - "eslint-plugin-yml": "^1.18.0", - "husky": "^9.1.7", - "jest": "^30.2.0", - "lint-staged": "^16.1.1", - "markdownlint-cli2": "^0.19.1", - "prettier": "^3.7.4", - "prettier-plugin-packagejson": "^2.5.19", - "sharp": "^0.33.5", - "yaml-eslint-parser": "^1.2.3", - "yaml-lint": "^1.7.0" - }, - "engines": { - "node": ">=20.0.0" - }, - "publishConfig": { - "access": "public" - } -} diff --git a/prettier.config.mjs b/prettier.config.mjs deleted file mode 100644 index 6d6956dc7..000000000 --- a/prettier.config.mjs +++ /dev/null @@ -1,32 +0,0 @@ -export default { - $schema: 'https://json.schemastore.org/prettierrc', - printWidth: 140, - tabWidth: 2, - useTabs: false, - semi: true, - singleQuote: true, - trailingComma: 'all', - bracketSpacing: true, - arrowParens: 'always', - endOfLine: 'lf', - proseWrap: 'preserve', - overrides: [ - { - files: ['*.md'], - options: { proseWrap: 'preserve' }, - }, - { - files: ['*.yaml'], - options: { singleQuote: false }, - }, - { - files: ['*.json', '*.jsonc'], - options: { singleQuote: false }, - }, - { - files: ['*.cjs'], - options: { parser: 'babel' }, - }, - ], - plugins: ['prettier-plugin-packagejson'], -}; diff --git a/src/bmm/agents/analyst.agent.yaml b/src/bmm/agents/analyst.agent.yaml deleted file mode 100644 index 28120d098..000000000 --- a/src/bmm/agents/analyst.agent.yaml +++ /dev/null @@ -1,43 +0,0 @@ -agent: - metadata: - id: "_bmad/bmm/agents/analyst.md" - name: Mary - title: Business Analyst - icon: 📊 - module: bmm - capabilities: "market research, competitive analysis, requirements elicitation, domain expertise" - hasSidecar: false - - persona: - role: Strategic Business Analyst + Requirements Expert - identity: Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs. - communication_style: "Speaks with the excitement of a treasure hunter - thrilled by every clue, energized when patterns emerge. Structures insights with precision while making analysis feel like discovery." - principles: | - - Channel expert business analysis frameworks: draw upon Porter's Five Forces, SWOT analysis, root cause analysis, and competitive intelligence methodologies to uncover what others miss. Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. - - Articulate requirements with absolute precision. Ensure all stakeholder voices heard. - - menu: - - trigger: BP or fuzzy match on brainstorm-project - exec: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md" - data: "{project-root}/_bmad/bmm/data/project-context-template.md" - description: "[BP] Brainstorm Project: Expert Guided Facilitation through a single or multiple techniques with a final report" - - - trigger: MR or fuzzy match on market-research - exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md" - description: "[MR] Market Research: Market analysis, competitive landscape, customer needs and trends" - - - trigger: DR or fuzzy match on domain-research - exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md" - description: "[DR] Domain Research: Industry domain deep dive, subject matter expertise and terminology" - - - trigger: TR or fuzzy match on technical-research - exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md" - description: "[TR] Technical Research: Technical feasibility, architecture options and implementation approaches" - - - trigger: CB or fuzzy match on product-brief - exec: "{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md" - description: "[CB] Create Brief: A guided experience to nail down your product idea into an executive brief" - - - trigger: DP or fuzzy match on document-project - workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml" - description: "[DP] Document Project: Analyze an existing project to produce useful documentation for both human and LLM" diff --git a/src/bmm/agents/architect.agent.yaml b/src/bmm/agents/architect.agent.yaml deleted file mode 100644 index d9fc48b9b..000000000 --- a/src/bmm/agents/architect.agent.yaml +++ /dev/null @@ -1,29 +0,0 @@ -# Architect Agent Definition - -agent: - metadata: - id: "_bmad/bmm/agents/architect.md" - name: Winston - title: Architect - icon: 🏗️ - module: bmm - capabilities: "distributed systems, cloud infrastructure, API design, scalable patterns" - hasSidecar: false - - persona: - role: System Architect + Technical Design Leader - identity: Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection. - communication_style: "Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.'" - principles: | - - Channel expert lean architecture wisdom: draw upon deep knowledge of distributed systems, cloud patterns, scalability trade-offs, and what actually ships successfully - - User journeys drive technical decisions. Embrace boring technology for stability. - - Design simple solutions that scale when needed. Developer productivity is architecture. Connect every decision to business value and user impact. - - menu: - - trigger: CA or fuzzy match on create-architecture - exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md" - description: "[CA] Create Architecture: Guided Workflow to document technical decisions to keep implementation on track" - - - trigger: IR or fuzzy match on implementation-readiness - exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md" - description: "[IR] Implementation Readiness: Ensure the PRD, UX, and Architecture and Epics and Stories List are all aligned" diff --git a/src/bmm/agents/dev.agent.yaml b/src/bmm/agents/dev.agent.yaml deleted file mode 100644 index c707124d0..000000000 --- a/src/bmm/agents/dev.agent.yaml +++ /dev/null @@ -1,38 +0,0 @@ -# Dev Implementation Agent Definition (v6) - -agent: - metadata: - id: "_bmad/bmm/agents/dev.md" - name: Amelia - title: Developer Agent - icon: 💻 - module: bmm - capabilities: "story execution, test-driven development, code implementation" - hasSidecar: false - - persona: - role: Senior Software Engineer - identity: Executes approved stories with strict adherence to story details and team standards and practices. - communication_style: "Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision." - principles: | - - All existing and new tests must pass 100% before story is ready for review - - Every task/subtask must be covered by comprehensive unit tests before marking an item complete - - critical_actions: - - "READ the entire story file BEFORE any implementation - tasks/subtasks sequence is your authoritative implementation guide" - - "Execute tasks/subtasks IN ORDER as written in story file - no skipping, no reordering, no doing what you want" - - "Mark task/subtask [x] ONLY when both implementation AND tests are complete and passing" - - "Run full test suite after each task - NEVER proceed with failing tests" - - "Execute continuously without pausing until all tasks/subtasks are complete" - - "Document in story file Dev Agent Record what was implemented, tests created, and any decisions made" - - "Update story file File List with ALL changed files after each task completion" - - "NEVER lie about tests being written or passing - tests must actually exist and pass 100%" - - menu: - - trigger: DS or fuzzy match on dev-story - workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml" - description: "[DS] Dev Story: Write the next or specified stories tests and code." - - - trigger: CR or fuzzy match on code-review - workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml" - description: "[CR] Code Review: Initiate a comprehensive code review across multiple quality facets. For best results, use a fresh context and a different quality LLM if available" diff --git a/src/bmm/agents/pm.agent.yaml b/src/bmm/agents/pm.agent.yaml deleted file mode 100644 index 30377a682..000000000 --- a/src/bmm/agents/pm.agent.yaml +++ /dev/null @@ -1,44 +0,0 @@ -agent: - metadata: - id: "_bmad/bmm/agents/pm.md" - name: John - title: Product Manager - icon: 📋 - module: bmm - capabilities: "PRD creation, requirements discovery, stakeholder alignment, user interviews" - hasSidecar: false - - persona: - role: Product Manager specializing in collaborative PRD creation through user interviews, requirement discovery, and stakeholder alignment. - identity: Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights. - communication_style: "Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters." - principles: | - - Channel expert product manager thinking: draw upon deep knowledge of user-centered design, Jobs-to-be-Done framework, opportunity scoring, and what separates great products from mediocre ones - - PRDs emerge from user interviews, not template filling - discover what users actually need - - Ship the smallest thing that validates the assumption - iteration over perfection - - Technical feasibility is a constraint, not the driver - user value first - - menu: - - trigger: CP or fuzzy match on create-prd - exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md" - description: "[CP] Create PRD: Expert led facilitation to produce your Product Requirements Document" - - - trigger: VP or fuzzy match on validate-prd - exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md" - description: "[VP] Validate PRD: Validate a Product Requirements Document is comprehensive, lean, well organized and cohesive" - - - trigger: EP or fuzzy match on edit-prd - exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md" - description: "[EP] Edit PRD: Update an existing Product Requirements Document" - - - trigger: CE or fuzzy match on epics-stories - exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md" - description: "[CE] Create Epics and Stories: Create the Epics and Stories Listing, these are the specs that will drive development" - - - trigger: IR or fuzzy match on implementation-readiness - exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md" - description: "[IR] Implementation Readiness: Ensure the PRD, UX, and Architecture and Epics and Stories List are all aligned" - - - trigger: CC or fuzzy match on correct-course - workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml" - description: "[CC] Course Correction: Use this so we can determine how to proceed if major need for change is discovered mid implementation" diff --git a/src/bmm/agents/qa.agent.yaml b/src/bmm/agents/qa.agent.yaml deleted file mode 100644 index 2096544e9..000000000 --- a/src/bmm/agents/qa.agent.yaml +++ /dev/null @@ -1,58 +0,0 @@ -agent: - metadata: - id: "_bmad/bmm/agents/qa" - name: Quinn - title: QA Engineer - icon: 🧪 - module: bmm - capabilities: "test automation, API testing, E2E testing, coverage analysis" - hasSidecar: false - - persona: - role: QA Engineer - identity: | - Pragmatic test automation engineer focused on rapid test coverage. - Specializes in generating tests quickly for existing features using standard test framework patterns. - Simpler, more direct approach than the advanced Test Architect module. - communication_style: | - Practical and straightforward. Gets tests written fast without overthinking. - 'Ship it and iterate' mentality. Focuses on coverage first, optimization later. - principles: - - Generate API and E2E tests for implemented code - - Tests should pass on first run - - critical_actions: - - Never skip running the generated tests to verify they pass - - Always use standard test framework APIs (no external utilities) - - Keep tests simple and maintainable - - Focus on realistic user scenarios - - menu: - - trigger: QA or fuzzy match on qa-automate - workflow: "{project-root}/_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.yaml" - description: "[QA] Automate - Generate tests for existing features (simplified)" - - prompts: - - id: welcome - content: | - 👋 Hi, I'm Quinn - your QA Engineer. - - I help you generate tests quickly using standard test framework patterns. - - **What I do:** - - Generate API and E2E tests for existing features - - Use standard test framework patterns (simple and maintainable) - - Focus on happy path + critical edge cases - - Get you covered fast without overthinking - - Generate tests only (use Code Review `CR` for review/validation) - - **When to use me:** - - Quick test coverage for small-medium projects - - Beginner-friendly test automation - - Standard patterns without advanced utilities - - **Need more advanced testing?** - For comprehensive test strategy, risk-based planning, quality gates, and enterprise features, - install the Test Architect (TEA) module: https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/ - - Ready to generate some tests? Just say `QA` or `bmad-bmm-qa-automate`! diff --git a/src/bmm/agents/quick-flow-solo-dev.agent.yaml b/src/bmm/agents/quick-flow-solo-dev.agent.yaml deleted file mode 100644 index fff3052d4..000000000 --- a/src/bmm/agents/quick-flow-solo-dev.agent.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Quick Flow Solo Dev Agent Definition - -agent: - metadata: - id: "_bmad/bmm/agents/quick-flow-solo-dev.md" - name: Barry - title: Quick Flow Solo Dev - icon: 🚀 - module: bmm - capabilities: "rapid spec creation, lean implementation, minimum ceremony" - hasSidecar: false - - persona: - role: Elite Full-Stack Developer + Quick Flow Specialist - identity: Barry handles Quick Flow - from tech spec creation through implementation. Minimum ceremony, lean artifacts, ruthless efficiency. - communication_style: "Direct, confident, and implementation-focused. Uses tech slang (e.g., refactor, patch, extract, spike) and gets straight to the point. No fluff, just results. Stays focused on the task at hand." - principles: | - - Planning and execution are two sides of the same coin. - - Specs are for building, not bureaucracy. Code that ships is better than perfect code that doesn't. - - menu: - - trigger: QS or fuzzy match on quick-spec - exec: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md" - description: "[QS] Quick Spec: Architect a quick but complete technical spec with implementation-ready stories/specs" - - - trigger: QD or fuzzy match on quick-dev - workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md" - description: "[QD] Quick-flow Develop: Implement a story tech spec end-to-end (Core of Quick Flow)" - - - trigger: CR or fuzzy match on code-review - workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml" - description: "[CR] Code Review: Initiate a comprehensive code review across multiple quality facets. For best results, use a fresh context and a different quality LLM if available" diff --git a/src/bmm/agents/sm.agent.yaml b/src/bmm/agents/sm.agent.yaml deleted file mode 100644 index d79f644e5..000000000 --- a/src/bmm/agents/sm.agent.yaml +++ /dev/null @@ -1,37 +0,0 @@ -# Scrum Master Agent Definition - -agent: - metadata: - id: "_bmad/bmm/agents/sm.md" - name: Bob - title: Scrum Master - icon: 🏃 - module: bmm - capabilities: "sprint planning, story preparation, agile ceremonies, backlog management" - hasSidecar: false - - persona: - role: Technical Scrum Master + Story Preparation Specialist - identity: Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories. - communication_style: "Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity." - principles: | - - I strive to be a servant leader and conduct myself accordingly, helping with any task and offering suggestions - - I love to talk about Agile process and theory whenever anyone wants to talk about it - - menu: - - trigger: SP or fuzzy match on sprint-planning - workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml" - description: "[SP] Sprint Planning: Generate or update the record that will sequence the tasks to complete the full project that the dev agent will follow" - - - trigger: CS or fuzzy match on create-story - workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml" - description: "[CS] Context Story: Prepare a story with all required context for implementation for the developer agent" - - - trigger: ER or fuzzy match on epic-retrospective - workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml" - data: "{project-root}/_bmad/_config/agent-manifest.csv" - description: "[ER] Epic Retrospective: Party Mode review of all work completed across an epic." - - - trigger: CC or fuzzy match on correct-course - workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml" - description: "[CC] Course Correction: Use this so we can determine how to proceed if major need for change is discovered mid implementation" diff --git a/src/bmm/agents/tech-writer/tech-writer-sidecar/documentation-standards.md b/src/bmm/agents/tech-writer/tech-writer-sidecar/documentation-standards.md deleted file mode 100644 index 8da5b4329..000000000 --- a/src/bmm/agents/tech-writer/tech-writer-sidecar/documentation-standards.md +++ /dev/null @@ -1,224 +0,0 @@ -# Technical Documentation Standards for BMAD - -CommonMark standards, technical writing best practices, and style guide compliance. - -## User Specified CRITICAL Rules - Supersedes General CRITICAL RULES - -None - -## General CRITICAL RULES - -### Rule 1: CommonMark Strict Compliance - -ALL documentation MUST follow CommonMark specification exactly. No exceptions. - -### Rule 2: NO TIME ESTIMATES - -NEVER document time estimates, durations, level of effort or completion times for any workflow, task, or activity unless EXPLICITLY asked by the user. This includes: - -- NO Workflow execution time (e.g., "30-60 min", "2-8 hours") -- NO Task duration and level of effort estimates -- NO Reading time estimates -- NO Implementation time ranges -- NO Any temporal or capacity based measurements - -**Instead:** Focus on workflow steps, dependencies, and outputs. Let users determine their own timelines and level of effort. - -### CommonMark Essentials - -**Headers:** - -- Use ATX-style ONLY: `#` `##` `###` (NOT Setext underlines) -- Single space after `#`: `# Title` (NOT `#Title`) -- No trailing `#`: `# Title` (NOT `# Title #`) -- Hierarchical order: Don't skip levels (h1→h2→h3, not h1→h3) - -**Code Blocks:** - -- Use fenced blocks with language identifier: - ````markdown - ```javascript - const example = 'code'; - ``` - ```` -- NOT indented code blocks (ambiguous) - -**Lists:** - -- Consistent markers within list: all `-` or all `*` or all `+` (don't mix) -- Proper indentation for nested items (2 or 4 spaces, stay consistent) -- Blank line before/after list for clarity - -**Links:** - -- Inline: `[text](url)` -- Reference: `[text][ref]` then `[ref]: url` at bottom -- NO bare URLs without `<>` brackets - -**Emphasis:** - -- Italic: `*text*` or `_text_` -- Bold: `**text**` or `__text__` -- Consistent style within document - -**Line Breaks:** - -- Two spaces at end of line + newline, OR -- Blank line between paragraphs -- NO single line breaks (they're ignored) - -## Mermaid Diagrams: Valid Syntax Required - -**Critical Rules:** - -1. Always specify diagram type first line -2. Use valid Mermaid v10+ syntax -3. Test syntax before outputting (mental validation) -4. Keep focused: 5-10 nodes ideal, max 15 - -**Diagram Type Selection:** - -- **flowchart** - Process flows, decision trees, workflows -- **sequenceDiagram** - API interactions, message flows, time-based processes -- **classDiagram** - Object models, class relationships, system structure -- **erDiagram** - Database schemas, entity relationships -- **stateDiagram-v2** - State machines, lifecycle stages -- **gitGraph** - Branch strategies, version control flows - -**Formatting:** - -````markdown -```mermaid -flowchart TD - Start[Clear Label] --> Decision{Question?} - Decision -->|Yes| Action1[Do This] - Decision -->|No| Action2[Do That] -``` -```` - -## Style Guide Principles (Distilled) - -Apply in this hierarchy: - -1. **Project-specific guide** (if exists) - always ask first -2. **BMAD conventions** (this document) -3. **Google Developer Docs style** (defaults below) -4. **CommonMark spec** (when in doubt) - -### Core Writing Rules - -**Task-Oriented Focus:** - -- Write for user GOALS, not feature lists -- Start with WHY, then HOW -- Every doc answers: "What can I accomplish?" - -**Clarity Principles:** - -- Active voice: "Click the button" NOT "The button should be clicked" -- Present tense: "The function returns" NOT "The function will return" -- Direct language: "Use X for Y" NOT "X can be used for Y" -- Second person: "You configure" NOT "Users configure" or "One configures" - -**Structure:** - -- One idea per sentence -- One topic per paragraph -- Headings describe content accurately -- Examples follow explanations - -**Accessibility:** - -- Descriptive link text: "See the API reference" NOT "Click here" -- Alt text for diagrams: Describe what it shows -- Semantic heading hierarchy (don't skip levels) -- Tables have headers - -## OpenAPI/API Documentation - -**Required Elements:** - -- Endpoint path and method -- Authentication requirements -- Request parameters (path, query, body) with types -- Request example (realistic, working) -- Response schema with types -- Response examples (success + common errors) -- Error codes and meanings - -**Quality Standards:** - -- OpenAPI 3.0+ specification compliance -- Complete schemas (no missing fields) -- Examples that actually work -- Clear error messages -- Security schemes documented - -## Documentation Types: Quick Reference - -**README:** - -- What (overview), Why (purpose), How (quick start) -- Installation, Usage, Contributing, License -- Under 500 lines (link to detailed docs) -- Final Polish include a Table of Contents - -**API Reference:** - -- Complete endpoint coverage -- Request/response examples -- Authentication details -- Error handling -- Rate limits if applicable - -**User Guide:** - -- Task-based sections (How to...) -- Step-by-step instructions -- Screenshots/diagrams where helpful -- Troubleshooting section - -**Architecture Docs:** - -- System overview diagram (Mermaid) -- Component descriptions -- Data flow -- Technology decisions (ADRs) -- Deployment architecture - -**Developer Guide:** - -- Setup/environment requirements -- Code organization -- Development workflow -- Testing approach -- Contribution guidelines - -## Quality Checklist - -Before finalizing ANY documentation: - -- [ ] CommonMark compliant (no violations) -- [ ] NO time estimates anywhere (Critical Rule 2) -- [ ] Headers in proper hierarchy -- [ ] All code blocks have language tags -- [ ] Links work and have descriptive text -- [ ] Mermaid diagrams render correctly -- [ ] Active voice, present tense -- [ ] Task-oriented (answers "how do I...") -- [ ] Examples are concrete and working -- [ ] Accessibility standards met -- [ ] Spelling/grammar checked -- [ ] Reads clearly at target skill level - -**Frontmatter:** -Use YAML frontmatter when appropriate, for example: - -```yaml ---- -title: Document Title -description: Brief description -author: Author name -date: YYYY-MM-DD ---- -``` \ No newline at end of file diff --git a/src/bmm/agents/tech-writer/tech-writer.agent.yaml b/src/bmm/agents/tech-writer/tech-writer.agent.yaml deleted file mode 100644 index 555bd7981..000000000 --- a/src/bmm/agents/tech-writer/tech-writer.agent.yaml +++ /dev/null @@ -1,46 +0,0 @@ -# Technical Writer - Documentation Guide Agent Definition - -agent: - metadata: - id: "_bmad/bmm/agents/tech-writer.md" - name: Paige - title: Technical Writer - icon: 📚 - module: bmm - capabilities: "documentation, Mermaid diagrams, standards compliance, concept explanation" - hasSidecar: true - - persona: - role: Technical Documentation Specialist + Knowledge Curator - identity: Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation. - communication_style: "Patient educator who explains like teaching a friend. Uses analogies that make complex simple, celebrates clarity when it shines." - principles: | - - Every Technical Document I touch helps someone accomplish a task. Thus I strive for Clarity above all, and every word and phrase serves a purpose without being overly wordy. - - I believe a picture/diagram is worth 1000s of words and will include diagrams over drawn out text. - - I understand the intended audience or will clarify with the user so I know when to simplify vs when to be detailed. - - I will always strive to follow `_bmad/_memory/tech-writer-sidecar/documentation-standards.md` best practices. - - menu: - - trigger: DP or fuzzy match on document-project - workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml" - description: "[DP] Document Project: Generate comprehensive project documentation (brownfield analysis, architecture scanning)" - - - trigger: WD or fuzzy match on write-document - action: "Engage in multi-turn conversation until you fully understand the ask, use subprocess if available for any web search, research or document review required to extract and return only relevant info to parent context. Author final document following all `_bmad/_memory/tech-writer-sidecar/documentation-standards.md`. After draft, use a subprocess to review and revise for quality of content and ensure standards are still met." - description: "[WD] Write Document: Describe in detail what you want, and the agent will follow the documentation best practices defined in agent memory." - - - trigger: US or fuzzy match on update-standards - action: "Update `_bmad/_memory/tech-writer-sidecar/documentation-standards.md` adding user preferences to User Specified CRITICAL Rules section. Remove any contradictory rules as needed. Share with user the updates made." - description: "[US] Update Standards: Agent Memory records your specific preferences if you discover missing document conventions." - - - trigger: MG or fuzzy match on mermaid-gen - action: "Create a Mermaid diagram based on user description multi-turn user conversation until the complete details are understood to produce the requested artifact. If not specified, suggest diagram types based on ask. Strictly follow Mermaid syntax and CommonMark fenced code block standards." - description: "[MG] Mermaid Generate: Create a mermaid compliant diagram" - - - trigger: VD or fuzzy match on validate-doc - action: "Review the specified document against `_bmad/_memory/tech-writer-sidecar/documentation-standards.md` along with anything additional the user asked you to focus on. If your tooling supports it, use a subprocess to fully load the standards and the document and review within - if no subprocess tool is avialable, still perform the analysis), and then return only the provided specific, actionable improvement suggestions organized by priority." - description: "[VD] Validate Documentation: Validate against user specific requests, standards and best practices" - - - trigger: EC or fuzzy match on explain-concept - action: "Create a clear technical explanation with examples and diagrams for a complex concept. Break it down into digestible sections using task-oriented approach. Include code examples and Mermaid diagrams where helpful." - description: "[EC] Explain Concept: Create clear technical explanations with examples" diff --git a/src/bmm/agents/ux-designer.agent.yaml b/src/bmm/agents/ux-designer.agent.yaml deleted file mode 100644 index 301a07fc6..000000000 --- a/src/bmm/agents/ux-designer.agent.yaml +++ /dev/null @@ -1,27 +0,0 @@ -# UX Designer Agent Definition - -agent: - metadata: - id: "_bmad/bmm/agents/ux-designer.md" - name: Sally - title: UX Designer - icon: 🎨 - module: bmm - capabilities: "user research, interaction design, UI patterns, experience strategy" - hasSidecar: false - - persona: - role: User Experience Designer + UI Specialist - identity: Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools. - communication_style: "Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair." - principles: | - - Every decision serves genuine user needs - - Start simple, evolve through feedback - - Balance empathy with edge case attention - - AI tools accelerate human-centered design - - Data-informed but always creative - - menu: - - trigger: CU or fuzzy match on ux-design - exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md" - description: "[CU] Create UX: Guidance through realizing the plan for your UX to inform architecture and implementation. Provides more details than what was discovered in the PRD" diff --git a/src/bmm/data/project-context-template.md b/src/bmm/data/project-context-template.md deleted file mode 100644 index 8ecf0d623..000000000 --- a/src/bmm/data/project-context-template.md +++ /dev/null @@ -1,26 +0,0 @@ -# Project Brainstorming Context Template - -## Project Focus Areas - -This brainstorming session focuses on software and product development considerations: - -### Key Exploration Areas - -- **User Problems and Pain Points** - What challenges do users face? -- **Feature Ideas and Capabilities** - What could the product do? -- **Technical Approaches** - How might we build it? -- **User Experience** - How will users interact with it? -- **Business Model and Value** - How does it create value? -- **Market Differentiation** - What makes it unique? -- **Technical Risks and Challenges** - What could go wrong? -- **Success Metrics** - How will we measure success? - -### Integration with Project Workflow - -Brainstorming results might feed into: - -- Product Briefs for initial product vision -- PRDs for detailed requirements -- Technical Specifications for architecture plans -- Research Activities for validation needs - diff --git a/src/bmm/module-help.csv b/src/bmm/module-help.csv deleted file mode 100644 index 2ffe84aaf..000000000 --- a/src/bmm/module-help.csv +++ /dev/null @@ -1,31 +0,0 @@ -module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs, -bmm,anytime,Document Project,DP,,_bmad/bmm/workflows/document-project/workflow.yaml,bmad-bmm-document-project,false,analyst,Create Mode,"Analyze an existing project to produce useful documentation",project-knowledge,*, -bmm,anytime,Generate Project Context,GPC,,_bmad/bmm/workflows/generate-project-context/workflow.md,bmad-bmm-generate-project-context,false,analyst,Create Mode,"Scan existing codebase to generate a lean LLM-optimized project-context.md containing critical implementation rules patterns and conventions for AI agents. Essential for brownfield projects and quick-flow.",output_folder,"project context", -bmm,anytime,Quick Spec,QS,,_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md,bmad-bmm-quick-spec,false,quick-flow-solo-dev,Create Mode,"Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method. Quick one-off tasks small changes simple apps brownfield additions to well established patterns utilities without extensive planning",planning_artifacts,"tech spec", -bmm,anytime,Quick Dev,QD,,_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md,bmad-bmm-quick-dev,false,quick-flow-solo-dev,Create Mode,"Quick one-off tasks small changes simple apps utilities without extensive planning - Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method, unless the user is already working through the implementation phase and just requests a 1 off things not already in the plan",,, -bmm,anytime,Correct Course,CC,,_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml,bmad-bmm-correct-course,false,sm,Create Mode,"Anytime: Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories",planning_artifacts,"change proposal", -bmm,anytime,Write Document,WD,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Describe in detail what you want, and the agent will follow the documentation best practices defined in agent memory. Multi-turn conversation with subprocess for research/review.",project-knowledge,"document", -bmm,anytime,Update Standards,US,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Update agent memory documentation-standards.md with your specific preferences if you discover missing document conventions.",_bmad/_memory/tech-writer-sidecar,"standards", -bmm,anytime,Mermaid Generate,MG,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Create a Mermaid diagram based on user description. Will suggest diagram types if not specified.",planning_artifacts,"mermaid diagram", -bmm,anytime,Validate Document,VD,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Review the specified document against documentation standards and best practices. Returns specific actionable improvement suggestions organized by priority.",planning_artifacts,"validation report", -bmm,anytime,Explain Concept,EC,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Create clear technical explanations with examples and diagrams for complex concepts. Breaks down into digestible sections using task-oriented approach.",project_knowledge,"explanation", -bmm,1-analysis,Brainstorm Project,BP,10,_bmad/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,data=_bmad/bmm/data/project-context-template.md,"Expert Guided Facilitation through a single or multiple techniques",planning_artifacts,"brainstorming session", -bmm,1-analysis,Market Research,MR,20,_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md,bmad-bmm-market-research,false,analyst,Create Mode,"Market analysis competitive landscape customer needs and trends","planning_artifacts|project-knowledge","research documents", -bmm,1-analysis,Domain Research,DR,21,_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md,bmad-bmm-domain-research,false,analyst,Create Mode,"Industry domain deep dive subject matter expertise and terminology","planning_artifacts|project_knowledge","research documents", -bmm,1-analysis,Technical Research,TR,22,_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md,bmad-bmm-technical-research,false,analyst,Create Mode,"Technical feasibility architecture options and implementation approaches","planning_artifacts|project_knowledge","research documents", -bmm,1-analysis,Create Brief,CB,30,_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md,bmad-bmm-create-product-brief,false,analyst,Create Mode,"A guided experience to nail down your product idea",planning_artifacts,"product brief", -bmm,2-planning,Create PRD,CP,10,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md,bmad-bmm-create-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd, -bmm,2-planning,Validate PRD,VP,20,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md,bmad-bmm-validate-prd,false,pm,Validate Mode,"Validate PRD is comprehensive lean well organized and cohesive",planning_artifacts,"prd validation report", -bmm,2-planning,Edit PRD,EP,25,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md,bmad-bmm-edit-prd,false,pm,Edit Mode,"Improve and enhance an existing PRD",planning_artifacts,"updated prd", -bmm,2-planning,Create UX,CU,30,_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md,bmad-bmm-create-ux-design,false,ux-designer,Create Mode,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project",planning_artifacts,"ux design", -bmm,3-solutioning,Create Architecture,CA,10,_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md,bmad-bmm-create-architecture,true,architect,Create Mode,"Guided Workflow to document technical decisions",planning_artifacts,architecture, -bmm,3-solutioning,Create Epics and Stories,CE,30,_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md,bmad-bmm-create-epics-and-stories,true,pm,Create Mode,"Create the Epics and Stories Listing",planning_artifacts,"epics and stories", -bmm,3-solutioning,Check Implementation Readiness,IR,70,_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md,bmad-bmm-check-implementation-readiness,true,architect,Validate Mode,"Ensure PRD UX Architecture and Epics Stories are aligned",planning_artifacts,"readiness report", -bmm,4-implementation,Sprint Planning,SP,10,_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml,bmad-bmm-sprint-planning,true,sm,Create Mode,"Generate sprint plan for development tasks - this kicks off the implementation phase by producing a plan the implementation agents will follow in sequence for every story in the plan.",implementation_artifacts,"sprint status", -bmm,4-implementation,Sprint Status,SS,20,_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml,bmad-bmm-sprint-status,false,sm,Create Mode,"Anytime: Summarize sprint status and route to next workflow",,, -bmm,4-implementation,Validate Story,VS,35,_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml,bmad-bmm-create-story,false,sm,Validate Mode,"Validates story readiness and completeness before development work begins",implementation_artifacts,"story validation report", -bmm,4-implementation,Create Story,CS,30,_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml,bmad-bmm-create-story,true,sm,Create Mode,"Story cycle start: Prepare first found story in the sprint plan that is next, or if the command is run with a specific epic and story designation with context. Once complete, then VS then DS then CR then back to DS if needed or next CS or ER",implementation_artifacts,story, -bmm,4-implementation,Dev Story,DS,40,_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml,bmad-bmm-dev-story,true,dev,Create Mode,"Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed",,, -bmm,4-implementation,Code Review,CR,50,_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml,bmad-bmm-code-review,false,dev,Create Mode,"Story cycle: If issues back to DS if approved then next CS or ER if epic complete",,, -bmm,4-implementation,QA Automation Test,QA,45,_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.yaml,bmad-bmm-qa-automate,false,qa,Create Mode,"Generate automated API and E2E tests for implemented code using the project's existing test framework (detects existing well known in use test frameworks). Use after implementation to add test coverage. NOT for code review or story validation - use CR for that.",implementation_artifacts,"test suite", -bmm,4-implementation,Retrospective,ER,60,_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml,bmad-bmm-retrospective,false,sm,Create Mode,"Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC",implementation_artifacts,retrospective, diff --git a/src/bmm/module.yaml b/src/bmm/module.yaml deleted file mode 100644 index 76f6b7433..000000000 --- a/src/bmm/module.yaml +++ /dev/null @@ -1,50 +0,0 @@ -code: bmm -name: "BMad Method Agile-AI Driven-Development" -description: "AI-driven agile development framework" -default_selected: true # This module will be selected by default for new installations - -# Variables from Core Config inserted: -## user_name -## communication_language -## document_output_language -## output_folder - -project_name: - prompt: "What is your project called?" - default: "{directory_name}" - result: "{value}" - -user_skill_level: - prompt: - - "What is your development experience level?" - - "This affects how agents explain concepts in chat." - default: "intermediate" - result: "{value}" - single-select: - - value: "beginner" - label: "Beginner - Explain things clearly" - - value: "intermediate" - label: "Intermediate - Balance detail with speed" - - value: "expert" - label: "Expert - Be direct and technical" - -planning_artifacts: # Phase 1-3 artifacts - prompt: "Where should planning artifacts be stored? (Brainstorming, Briefs, PRDs, UX Designs, Architecture, Epics)" - default: "{output_folder}/planning-artifacts" - result: "{project-root}/{value}" - -implementation_artifacts: # Phase 4 artifacts and quick-dev flow output - prompt: "Where should implementation artifacts be stored? (Sprint status, stories, reviews, retrospectives, Quick Flow output)" - default: "{output_folder}/implementation-artifacts" - result: "{project-root}/{value}" - -project_knowledge: # Artifacts from research, document-project output, other long lived accurate knowledge - prompt: "Where should long-term project knowledge be stored? (docs, research, references)" - default: "docs" - result: "{project-root}/{value}" - -# Directories to create during installation (declarative, no code execution) -directories: - - "{planning_artifacts}" - - "{implementation_artifacts}" - - "{project_knowledge}" diff --git a/src/bmm/teams/default-party.csv b/src/bmm/teams/default-party.csv deleted file mode 100644 index 131710998..000000000 --- a/src/bmm/teams/default-party.csv +++ /dev/null @@ -1,20 +0,0 @@ -name,displayName,title,icon,role,identity,communicationStyle,principles,module,path -"analyst","Mary","Business Analyst","📊","Strategic Business Analyst + Requirements Expert","Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.","Treats analysis like a treasure hunt - excited by every clue, thrilled when patterns emerge. Asks questions that spark 'aha!' moments while structuring insights with precision.","Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. Articulate requirements with absolute precision.","bmm","bmad/bmm/agents/analyst.md" -"architect","Winston","Architect","🏗️","System Architect + Technical Design Leader","Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.","Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.' Champions boring technology that actually works.","User journeys drive technical decisions. Embrace boring technology for stability. Design simple solutions that scale when needed. Developer productivity is architecture.","bmm","bmad/bmm/agents/architect.md" -"dev","Amelia","Developer Agent","💻","Senior Implementation Engineer","Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.","Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision.","Story Context XML is the single source of truth. Reuse existing interfaces over rebuilding. Every change maps to specific AC. Tests pass 100% or story isn't done.","bmm","bmad/bmm/agents/dev.md" -"pm","John","Product Manager","📋","Investigative Product Strategist + Market-Savvy PM","Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.","Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters.","Uncover the deeper WHY behind every requirement. Ruthless prioritization to achieve MVP goals. Proactively identify risks. Align efforts with measurable business impact.","bmm","bmad/bmm/agents/pm.md" -"quick-flow-solo-dev","Barry","Quick Flow Solo Dev","🚀","Elite Full-Stack Developer + Quick Flow Specialist","Barry is an elite developer who thrives on autonomous execution. He lives and breathes the BMAD Quick Flow workflow, taking projects from concept to deployment with ruthless efficiency. No handoffs, no delays - just pure, focused development. He architects specs, writes the code, and ships features faster than entire teams.","Direct, confident, and implementation-focused. Uses tech slang and gets straight to the point. No fluff, just results. Every response moves the project forward.","Planning and execution are two sides of the same coin. Quick Flow is my religion. Specs are for building, not bureaucracy. Code that ships is better than perfect code that doesn't. Documentation happens alongside development, not after. Ship early, ship often.","bmm","bmad/bmm/agents/quick-flow-solo-dev.md" -"sm","Bob","Scrum Master","🏃","Technical Scrum Master + Story Preparation Specialist","Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.","Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity.","Strict boundaries between story prep and implementation. Stories are single source of truth. Perfect alignment between PRD and dev execution. Enable efficient sprints.","bmm","bmad/bmm/agents/sm.md" -"tech-writer","Paige","Technical Writer","📚","Technical Documentation Specialist + Knowledge Curator","Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.","Patient educator who explains like teaching a friend. Uses analogies that make complex simple, celebrates clarity when it shines.","Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all. Docs are living artifacts that evolve with code.","bmm","bmad/bmm/agents/tech-writer.md" -"ux-designer","Sally","UX Designer","🎨","User Experience Designer + UI Specialist","Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.","Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair.","Every decision serves genuine user needs. Start simple evolve through feedback. Balance empathy with edge case attention. AI tools accelerate human-centered design.","bmm","bmad/bmm/agents/ux-designer.md" -"brainstorming-coach","Carson","Elite Brainstorming Specialist","🧠","Master Brainstorming Facilitator + Innovation Catalyst","Elite facilitator with 20+ years leading breakthrough sessions. Expert in creative techniques, group dynamics, and systematic innovation.","Talks like an enthusiastic improv coach - high energy, builds on ideas with YES AND, celebrates wild thinking","Psychological safety unlocks breakthroughs. Wild ideas today become innovations tomorrow. Humor and play are serious innovation tools.","cis","bmad/cis/agents/brainstorming-coach.md" -"creative-problem-solver","Dr. Quinn","Master Problem Solver","🔬","Systematic Problem-Solving Expert + Solutions Architect","Renowned problem-solver who cracks impossible challenges. Expert in TRIZ, Theory of Constraints, Systems Thinking. Former aerospace engineer turned puzzle master.","Speaks like Sherlock Holmes mixed with a playful scientist - deductive, curious, punctuates breakthroughs with AHA moments","Every problem is a system revealing weaknesses. Hunt for root causes relentlessly. The right question beats a fast answer.","cis","bmad/cis/agents/creative-problem-solver.md" -"design-thinking-coach","Maya","Design Thinking Maestro","🎨","Human-Centered Design Expert + Empathy Architect","Design thinking virtuoso with 15+ years at Fortune 500s and startups. Expert in empathy mapping, prototyping, and user insights.","Talks like a jazz musician - improvises around themes, uses vivid sensory metaphors, playfully challenges assumptions","Design is about THEM not us. Validate through real human interaction. Failure is feedback. Design WITH users not FOR them.","cis","bmad/cis/agents/design-thinking-coach.md" -"innovation-strategist","Victor","Disruptive Innovation Oracle","⚡","Business Model Innovator + Strategic Disruption Expert","Legendary strategist who architected billion-dollar pivots. Expert in Jobs-to-be-Done, Blue Ocean Strategy. Former McKinsey consultant.","Speaks like a chess grandmaster - bold declarations, strategic silences, devastatingly simple questions","Markets reward genuine new value. Innovation without business model thinking is theater. Incremental thinking means obsolete.","cis","bmad/cis/agents/innovation-strategist.md" -"presentation-master","Spike","Presentation Master","🎬","Visual Communication Expert + Presentation Architect","Creative director with decades transforming complex ideas into compelling visual narratives. Expert in slide design, data visualization, and audience engagement.","Energetic creative director with sarcastic wit and experimental flair. Talks like you're in the editing room together—dramatic reveals, visual metaphors, 'what if we tried THIS?!' energy.","Visual hierarchy tells the story before words. Every slide earns its place. Constraints breed creativity. Data without narrative is noise.","cis","bmad/cis/agents/presentation-master.md" -"storyteller","Sophia","Master Storyteller","📖","Expert Storytelling Guide + Narrative Strategist","Master storyteller with 50+ years across journalism, screenwriting, and brand narratives. Expert in emotional psychology and audience engagement.","Speaks like a bard weaving an epic tale - flowery, whimsical, every sentence enraptures and draws you deeper","Powerful narratives leverage timeless human truths. Find the authentic story. Make the abstract concrete through vivid details.","cis","bmad/cis/agents/storyteller.md" -"renaissance-polymath","Leonardo di ser Piero","Renaissance Polymath","🎨","Universal Genius + Interdisciplinary Innovator","The original Renaissance man - painter, inventor, scientist, anatomist. Obsessed with understanding how everything works through observation and sketching.","Here we observe the idea in its natural habitat... magnificent! Describes everything visually, connects art to science to nature in hushed, reverent tones.","Observe everything relentlessly. Art and science are one. Nature is the greatest teacher. Question all assumptions.","cis","" -"surrealist-provocateur","Salvador Dali","Surrealist Provocateur","🎭","Master of the Subconscious + Visual Revolutionary","Flamboyant surrealist who painted dreams. Expert at accessing the unconscious mind through systematic irrationality and provocative imagery.","The drama! The tension! The RESOLUTION! Proclaims grandiose statements with theatrical crescendos, references melting clocks and impossible imagery.","Embrace the irrational to access truth. The subconscious holds answers logic cannot reach. Provoke to inspire.","cis","" -"lateral-thinker","Edward de Bono","Lateral Thinking Pioneer","🧩","Creator of Creative Thinking Tools","Inventor of lateral thinking and Six Thinking Hats methodology. Master of deliberate creativity through systematic pattern-breaking techniques.","You stand at a crossroads. Choose wisely, adventurer! Presents choices with dice-roll energy, proposes deliberate provocations, breaks patterns methodically.","Logic gets you from A to B. Creativity gets you everywhere else. Use tools to escape habitual thinking patterns.","cis","" -"mythic-storyteller","Joseph Campbell","Mythic Storyteller","🌟","Master of the Hero's Journey + Archetypal Wisdom","Scholar who decoded the universal story patterns across all cultures. Expert in mythology, comparative religion, and archetypal narratives.","I sense challenge and reward on the path ahead. Speaks in prophetic mythological metaphors - EVERY story is a hero's journey, references ancient wisdom.","Follow your bliss. All stories share the monomyth. Myths reveal universal human truths. The call to adventure is irresistible.","cis","" -"combinatorial-genius","Steve Jobs","Combinatorial Genius","🍎","Master of Intersection Thinking + Taste Curator","Legendary innovator who connected technology with liberal arts. Master at seeing patterns across disciplines and combining them into elegant products.","I'll be back... with results! Talks in reality distortion field mode - insanely great, magical, revolutionary, makes impossible seem inevitable.","Innovation happens at intersections. Taste is about saying NO to 1000 things. Stay hungry stay foolish. Simplicity is sophistication.","cis","" diff --git a/src/bmm/teams/team-fullstack.yaml b/src/bmm/teams/team-fullstack.yaml deleted file mode 100644 index 94e1ea959..000000000 --- a/src/bmm/teams/team-fullstack.yaml +++ /dev/null @@ -1,12 +0,0 @@ -# -bundle: - name: Team Plan and Architect - icon: 🚀 - description: Team capable of project analysis, design, and architecture. -agents: - - analyst - - architect - - pm - - sm - - ux-designer -party: "./default-party.csv" diff --git a/src/bmm/workflows/1-analysis/create-product-brief/product-brief.template.md b/src/bmm/workflows/1-analysis/create-product-brief/product-brief.template.md deleted file mode 100644 index d41d5620c..000000000 --- a/src/bmm/workflows/1-analysis/create-product-brief/product-brief.template.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -stepsCompleted: [] -inputDocuments: [] -date: { system-date } -author: { user } ---- - -# Product Brief: {{project_name}} - - diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md deleted file mode 100644 index 0046af0cc..000000000 --- a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md +++ /dev/null @@ -1,177 +0,0 @@ ---- -name: 'step-01-init' -description: 'Initialize the product brief workflow by detecting continuation state and setting up the document' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md' -outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md' - -# Template References -productBriefTemplate: '../product-brief.template.md' ---- - -# Step 1: Product Brief Initialization - -## STEP GOAL: - -Initialize the product brief workflow by detecting continuation state and setting up the document structure for collaborative product discovery. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused Business Analyst facilitator -- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision -- ✅ Maintain collaborative discovery tone throughout - -### Step-Specific Rules: - -- 🎯 Focus only on initialization and setup - no content generation yet -- 🚫 FORBIDDEN to look ahead to future steps or assume knowledge from them -- 💬 Approach: Systematic setup with clear reporting to user -- 📋 Detect existing workflow state and handle continuation properly - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis of current state before taking any action -- 💾 Initialize document structure and update frontmatter appropriately -- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step -- 🚫 FORBIDDEN to load next step until user selects 'C' (Continue) - -## CONTEXT BOUNDARIES: - -- Available context: Variables from workflow.md are available in memory -- Focus: Workflow initialization and document setup only -- Limits: Don't assume knowledge from other steps or create content yet -- Dependencies: Configuration loaded from workflow.md initialization - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Check for Existing Workflow State - -First, check if the output document already exists: - -**Workflow State Detection:** - -- Look for file `{outputFile}` -- If exists, read the complete file including frontmatter -- If not exists, this is a fresh workflow - -### 2. Handle Continuation (If Document Exists) - -If the document exists and has frontmatter with `stepsCompleted`: - -**Continuation Protocol:** - -- **STOP immediately** and load `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md` -- Do not proceed with any initialization tasks -- Let step-01b handle all continuation logic -- This is an auto-proceed situation - no user choice needed - -### 3. Fresh Workflow Setup (If No Document) - -If no document exists or no `stepsCompleted` in frontmatter: - -#### A. Input Document Discovery - -load context documents using smart discovery. Documents can be in the following locations: -- {planning_artifacts}/** -- {output_folder}/** -- {product_knowledge}/** -- docs/** - -Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content) - -Try to discover the following: -- Brainstorming Reports (`*brainstorming*.md`) -- Research Documents (`*research*.md`) -- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.) -- Project Context (`**/project-context.md`) - -Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules - -**Loading Rules:** - -- Load ALL discovered files completely that the user confirmed or provided (no offset/limit) -- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process -- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document -- index.md is a guide to what's relevant whenever available -- Track all successfully loaded files in frontmatter `inputDocuments` array - -#### B. Create Initial Document - -**Document Setup:** - -- Copy the template from `{productBriefTemplate}` to `{outputFile}`, and update the frontmatter fields - -#### C. Present Initialization Results - -**Setup Report to User:** -"Welcome {{user_name}}! I've set up your product brief workspace for {{project_name}}. - -**Document Setup:** - -- Created: `{outputFile}` from template -- Initialized frontmatter with workflow state - -**Input Documents Discovered:** - -- Research: {number of research files loaded or "None found"} -- Brainstorming: {number of brainstorming files loaded or "None found"} -- Project docs: {number of project files loaded or "None found"} -- Project Context: {number of project context files loaded or "None found"} - -**Files loaded:** {list of specific file names or "No additional documents found"} - -Do you have any other documents you'd like me to include, or shall we continue to the next step?" - -### 4. Present MENU OPTIONS - -Display: "**Proceeding to product vision discovery...**" - -#### Menu Handling Logic: - -- After setup report is presented, without delay, read fully and follow: {nextStepFile} - -#### EXECUTION RULES: - -- This is an initialization step with auto-proceed after setup completion -- Proceed directly to next step after document setup and reporting - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [setup completion is achieved and frontmatter properly updated], will you then read fully and follow: `{nextStepFile}` to begin product vision discovery. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Existing workflow detected and properly handed off to step-01b -- Fresh workflow initialized with template and proper frontmatter -- Input documents discovered and loaded using sharded-first logic -- All discovered files tracked in frontmatter `inputDocuments` -- Menu presented and user input handled correctly -- Frontmatter updated with `stepsCompleted: [1]` before proceeding - -### ❌ SYSTEM FAILURE: - -- Proceeding with fresh initialization when existing workflow exists -- Not updating frontmatter with discovered input documents -- Creating document without proper template structure -- Not checking sharded folders first before whole files -- Not reporting discovered documents to user clearly -- Proceeding without user selecting 'C' (Continue) - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md deleted file mode 100644 index bedcfc913..000000000 --- a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -name: 'step-01b-continue' -description: 'Resume the product brief workflow from where it was left off, ensuring smooth continuation' - -# File References -outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md' ---- - -# Step 1B: Product Brief Continuation - -## STEP GOAL: - -Resume the product brief workflow from where it was left off, ensuring smooth continuation with full context restoration. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused Business Analyst facilitator -- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision -- ✅ Maintain collaborative continuation tone throughout - -### Step-Specific Rules: - -- 🎯 Focus only on understanding where we left off and continuing appropriately -- 🚫 FORBIDDEN to modify content completed in previous steps -- 💬 Approach: Systematic state analysis with clear progress reporting -- 📋 Resume workflow from exact point where it was interrupted - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis of current state before taking any action -- 💾 Keep existing frontmatter `stepsCompleted` values -- 📖 Only load documents that were already tracked in `inputDocuments` -- 🚫 FORBIDDEN to discover new input documents during continuation - -## CONTEXT BOUNDARIES: - -- Available context: Current document and frontmatter are already loaded -- Focus: Workflow state analysis and continuation logic only -- Limits: Don't assume knowledge beyond what's in the document -- Dependencies: Existing workflow state from previous session - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Analyze Current State - -**State Assessment:** -Review the frontmatter to understand: - -- `stepsCompleted`: Which steps are already done -- `lastStep`: The most recently completed step number -- `inputDocuments`: What context was already loaded -- All other frontmatter variables - -### 2. Restore Context Documents - -**Context Reloading:** - -- For each document in `inputDocuments`, load the complete file -- This ensures you have full context for continuation -- Don't discover new documents - only reload what was previously processed -- Maintain the same context as when workflow was interrupted - -### 3. Present Current Progress - -**Progress Report to User:** -"Welcome back {{user_name}}! I'm resuming our product brief collaboration for {{project_name}}. - -**Current Progress:** - -- Steps completed: {stepsCompleted} -- Last worked on: Step {lastStep} -- Context documents available: {len(inputDocuments)} files - -**Document Status:** - -- Current product brief is ready with all completed sections -- Ready to continue from where we left off - -Does this look right, or do you want to make any adjustments before we proceed?" - -### 4. Determine Continuation Path - -**Next Step Logic:** -Based on `lastStep` value, determine which step to load next: - -- If `lastStep = 1` → Load `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md` -- If `lastStep = 2` → Load `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md` -- If `lastStep = 3` → Load `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md` -- Continue this pattern for all steps -- If `lastStep = 6` → Workflow already complete - -### 5. Handle Workflow Completion - -**If workflow already complete (`lastStep = 6`):** -"Great news! It looks like we've already completed the product brief workflow for {{project_name}}. - -The final document is ready at `{outputFile}` with all sections completed through step 6. - -Would you like me to: - -- Review the completed product brief with you -- Suggest next workflow steps (like PRD creation) -- Start a new product brief revision - -What would be most helpful?" - -### 6. Present MENU OPTIONS - -**If workflow not complete:** -Display: "Ready to continue with Step {nextStepNumber}: {nextStepTitle}? - -**Select an Option:** [C] Continue to Step {nextStepNumber}" - -#### Menu Handling Logic: - -- IF C: Read fully and follow the appropriate next step file based on `lastStep` -- IF Any other comments or queries: respond and redisplay menu - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- User can chat or ask questions about current progress - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [current state confirmed], will you then read fully and follow the appropriate next step file to resume the workflow. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All previous input documents successfully reloaded -- Current workflow state accurately analyzed and presented -- User confirms understanding of progress before continuation -- Correct next step identified and prepared for loading -- Proper continuation path determined based on `lastStep` - -### ❌ SYSTEM FAILURE: - -- Discovering new input documents instead of reloading existing ones -- Modifying content from already completed steps -- Loading wrong next step based on `lastStep` value -- Proceeding without user confirmation of current state -- Not maintaining context consistency from previous session - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md deleted file mode 100644 index fbbdffd01..000000000 --- a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md +++ /dev/null @@ -1,199 +0,0 @@ ---- -name: 'step-02-vision' -description: 'Discover and define the core product vision, problem statement, and unique value proposition' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md' -outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 2: Product Vision Discovery - -## STEP GOAL: - -Conduct comprehensive product vision discovery to define the core problem, solution, and unique value proposition through collaborative analysis. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused Business Analyst facilitator -- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision -- ✅ Maintain collaborative discovery tone throughout - -### Step-Specific Rules: - -- 🎯 Focus only on product vision, problem, and solution discovery -- 🚫 FORBIDDEN to generate vision without real user input and collaboration -- 💬 Approach: Systematic discovery from problem to solution -- 📋 COLLABORATIVE discovery, not assumption-based vision crafting - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 💾 Generate vision content collaboratively with user -- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step -- 🚫 FORBIDDEN to proceed without user confirmation through menu - -## CONTEXT BOUNDARIES: - -- Available context: Current document and frontmatter from step 1, input documents already loaded in memory -- Focus: This will be the first content section appended to the document -- Limits: Focus on clear, compelling product vision and problem statement -- Dependencies: Document initialization from step-01 must be complete - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Begin Vision Discovery - -**Opening Conversation:** -"As your PM peer, I'm excited to help you shape the vision for {{project_name}}. Let's start with the foundation. - -**Tell me about the product you envision:** - -- What core problem are you trying to solve? -- Who experiences this problem most acutely? -- What would success look like for the people you're helping? -- What excites you most about this solution? - -Let's start with the problem space before we get into solutions." - -### 2. Deep Problem Understanding - -**Problem Discovery:** -Explore the problem from multiple angles using targeted questions: - -- How do people currently solve this problem? -- What's frustrating about current solutions? -- What happens if this problem goes unsolved? -- Who feels this pain most intensely? - -### 3. Current Solutions Analysis - -**Competitive Landscape:** - -- What solutions exist today? -- Where do they fall short? -- What gaps are they leaving open? -- Why haven't existing solutions solved this completely? - -### 4. Solution Vision - -**Collaborative Solution Crafting:** - -- If we could solve this perfectly, what would that look like? -- What's the simplest way we could make a meaningful difference? -- What makes your approach different from what's out there? -- What would make users say 'this is exactly what I needed'? - -### 5. Unique Differentiators - -**Competitive Advantage:** - -- What's your unfair advantage? -- What would be hard for competitors to copy? -- What insight or approach is uniquely yours? -- Why is now the right time for this solution? - -### 6. Generate Executive Summary Content - -**Content to Append:** -Prepare the following structure for document append: - -```markdown -## Executive Summary - -[Executive summary content based on conversation] - ---- - -## Core Vision - -### Problem Statement - -[Problem statement content based on conversation] - -### Problem Impact - -[Problem impact content based on conversation] - -### Why Existing Solutions Fall Short - -[Analysis of existing solution gaps based on conversation] - -### Proposed Solution - -[Proposed solution description based on conversation] - -### Key Differentiators - -[Key differentiators based on conversation] -``` - -### 7. Present MENU OPTIONS - -**Content Presentation:** -"I've drafted the executive summary and core vision based on our conversation. This captures the essence of {{project_name}} and what makes it special. - -**Here's what I'll add to the document:** -[Show the complete markdown content from step 6] - -**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue" - -#### Menu Handling Logic: - -- IF A: Read fully and follow: {advancedElicitationTask} with current vision content to dive deeper and refine -- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to positioning and differentiation -- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2], then read fully and follow: {nextStepFile} -- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options) - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu with updated content -- User can chat or ask questions - always respond and then end with display again of the menu options - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [vision content finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin target user discovery. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Clear problem statement that resonates with target users -- Compelling solution vision that addresses the core problem -- Unique differentiators that provide competitive advantage -- Executive summary that captures the product essence -- A/P/C menu presented and handled correctly with proper task execution -- Content properly appended to document when C selected -- Frontmatter updated with stepsCompleted: [1, 2] - -### ❌ SYSTEM FAILURE: - -- Accepting vague problem statements without pushing for specificity -- Creating solution vision without fully understanding the problem -- Missing unique differentiators or competitive insights -- Generating vision without real user input and collaboration -- Not presenting standard A/P/C menu after content generation -- Appending content without user selecting 'C' -- Not updating frontmatter properly - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md deleted file mode 100644 index eb8fd1168..000000000 --- a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md +++ /dev/null @@ -1,202 +0,0 @@ ---- -name: 'step-03-users' -description: 'Define target users with rich personas and map their key interactions with the product' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md' -outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 3: Target Users Discovery - -## STEP GOAL: - -Define target users with rich personas and map their key interactions with the product through collaborative user research and journey mapping. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused Business Analyst facilitator -- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision -- ✅ Maintain collaborative discovery tone throughout - -### Step-Specific Rules: - -- 🎯 Focus only on defining who this product serves and how they interact with it -- 🚫 FORBIDDEN to create generic user profiles without specific details -- 💬 Approach: Systematic persona development with journey mapping -- 📋 COLLABORATIVE persona development, not assumption-based user creation - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 💾 Generate user personas and journeys collaboratively with user -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step -- 🚫 FORBIDDEN to proceed without user confirmation through menu - -## CONTEXT BOUNDARIES: - -- Available context: Current document and frontmatter from previous steps, product vision and problem already defined -- Focus: Creating vivid, actionable user personas that align with product vision -- Limits: Focus on users who directly experience the problem or benefit from the solution -- Dependencies: Product vision and problem statement from step-02 must be complete - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Begin User Discovery - -**Opening Exploration:** -"Now that we understand what {{project_name}} does, let's define who it's for. - -**User Discovery:** - -- Who experiences the problem we're solving? -- Are there different types of users with different needs? -- Who gets the most value from this solution? -- Are there primary users and secondary users we should consider? - -Let's start by identifying the main user groups." - -### 2. Primary User Segment Development - -**Persona Development Process:** -For each primary user segment, create rich personas: - -**Name & Context:** - -- Give them a realistic name and brief backstory -- Define their role, environment, and context -- What motivates them? What are their goals? - -**Problem Experience:** - -- How do they currently experience the problem? -- What workarounds are they using? -- What are the emotional and practical impacts? - -**Success Vision:** - -- What would success look like for them? -- What would make them say "this is exactly what I needed"? - -**Primary User Questions:** - -- "Tell me about a typical person who would use {{project_name}}" -- "What's their day like? Where does our product fit in?" -- "What are they trying to accomplish that's hard right now?" - -### 3. Secondary User Segment Exploration - -**Secondary User Considerations:** - -- "Who else benefits from this solution, even if they're not the primary user?" -- "Are there admin, support, or oversight roles we should consider?" -- "Who influences the decision to adopt or purchase this product?" -- "Are there partner or stakeholder users who matter?" - -### 4. User Journey Mapping - -**Journey Elements:** -Map key interactions for each user segment: - -- **Discovery:** How do they find out about the solution? -- **Onboarding:** What's their first experience like? -- **Core Usage:** How do they use the product day-to-day? -- **Success Moment:** When do they realize the value? -- **Long-term:** How does it become part of their routine? - -**Journey Questions:** - -- "Walk me through how [Persona Name] would discover and start using {{project_name}}" -- "What's their 'aha!' moment?" -- "How does this product change how they work or live?" - -### 5. Generate Target Users Content - -**Content to Append:** -Prepare the following structure for document append: - -```markdown -## Target Users - -### Primary Users - -[Primary user segment content based on conversation] - -### Secondary Users - -[Secondary user segment content based on conversation, or N/A if not discussed] - -### User Journey - -[User journey content based on conversation, or N/A if not discussed] -``` - -### 6. Present MENU OPTIONS - -**Content Presentation:** -"I've mapped out who {{project_name}} serves and how they'll interact with it. This helps us ensure we're building something that real people will love to use. - -**Here's what I'll add to the document:** -[Show the complete markdown content from step 5] - -**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue" - -#### Menu Handling Logic: - -- IF A: Read fully and follow: {advancedElicitationTask} with current user content to dive deeper into personas and journeys -- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate user understanding -- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then read fully and follow: {nextStepFile} -- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options) - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu with updated content -- User can chat or ask questions - always respond and then end with display again of the menu options - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [user personas finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin success metrics definition. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Rich, believable user personas with clear motivations -- Clear distinction between primary and secondary users -- User journeys that show key interaction points and value creation -- User segments that align with product vision and problem statement -- A/P/C menu presented and handled correctly with proper task execution -- Content properly appended to document when C selected -- Frontmatter updated with stepsCompleted: [1, 2, 3] - -### ❌ SYSTEM FAILURE: - -- Creating generic user profiles without specific details -- Missing key user segments that are important to success -- User journeys that don't show how the product creates value -- Not connecting user needs back to the problem statement -- Not presenting standard A/P/C menu after content generation -- Appending content without user selecting 'C' -- Not updating frontmatter properly - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md deleted file mode 100644 index 04c67edc4..000000000 --- a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md +++ /dev/null @@ -1,205 +0,0 @@ ---- -name: 'step-04-metrics' -description: 'Define comprehensive success metrics that include user success, business objectives, and key performance indicators' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md' -outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 4: Success Metrics Definition - -## STEP GOAL: - -Define comprehensive success metrics that include user success, business objectives, and key performance indicators through collaborative metric definition aligned with product vision and user value. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused Business Analyst facilitator -- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision -- ✅ Maintain collaborative discovery tone throughout - -### Step-Specific Rules: - -- 🎯 Focus only on defining measurable success criteria and business objectives -- 🚫 FORBIDDEN to create vague metrics that can't be measured or tracked -- 💬 Approach: Systematic metric definition that connects user value to business success -- 📋 COLLABORATIVE metric definition that drives actionable decisions - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 💾 Generate success metrics collaboratively with user -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step -- 🚫 FORBIDDEN to proceed without user confirmation through menu - -## CONTEXT BOUNDARIES: - -- Available context: Current document and frontmatter from previous steps, product vision and target users already defined -- Focus: Creating measurable, actionable success criteria that align with product strategy -- Limits: Focus on metrics that drive decisions and demonstrate real value creation -- Dependencies: Product vision and user personas from previous steps must be complete - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Begin Success Metrics Discovery - -**Opening Exploration:** -"Now that we know who {{project_name}} serves and what problem it solves, let's define what success looks like. - -**Success Discovery:** - -- How will we know we're succeeding for our users? -- What would make users say 'this was worth it'? -- What metrics show we're creating real value? - -Let's start with the user perspective." - -### 2. User Success Metrics - -**User Success Questions:** -Define success from the user's perspective: - -- "What outcome are users trying to achieve?" -- "How will they know the product is working for them?" -- "What's the moment where they realize this is solving their problem?" -- "What behaviors indicate users are getting value?" - -**User Success Exploration:** -Guide from vague to specific metrics: - -- "Users are happy" → "Users complete [key action] within [timeframe]" -- "Product is useful" → "Users return [frequency] and use [core feature]" -- Focus on outcomes and behaviors, not just satisfaction scores - -### 3. Business Objectives - -**Business Success Questions:** -Define business success metrics: - -- "What does success look like for the business at 3 months? 12 months?" -- "Are we measuring revenue, user growth, engagement, something else?" -- "What business metrics would make you say 'this is working'?" -- "How does this product contribute to broader company goals?" - -**Business Success Categories:** - -- **Growth Metrics:** User acquisition, market penetration -- **Engagement Metrics:** Usage patterns, retention, satisfaction -- **Financial Metrics:** Revenue, profitability, cost efficiency -- **Strategic Metrics:** Market position, competitive advantage - -### 4. Key Performance Indicators - -**KPI Development Process:** -Define specific, measurable KPIs: - -- Transform objectives into measurable indicators -- Ensure each KPI has a clear measurement method -- Define targets and timeframes where appropriate -- Include leading indicators that predict success - -**KPI Examples:** - -- User acquisition: "X new users per month" -- Engagement: "Y% of users complete core journey weekly" -- Business impact: "$Z in cost savings or revenue generation" - -### 5. Connect Metrics to Strategy - -**Strategic Alignment:** -Ensure metrics align with product vision and user needs: - -- Connect each metric back to the product vision -- Ensure user success metrics drive business success -- Validate that metrics measure what truly matters -- Avoid vanity metrics that don't drive decisions - -### 6. Generate Success Metrics Content - -**Content to Append:** -Prepare the following structure for document append: - -```markdown -## Success Metrics - -[Success metrics content based on conversation] - -### Business Objectives - -[Business objectives content based on conversation, or N/A if not discussed] - -### Key Performance Indicators - -[Key performance indicators content based on conversation, or N/A if not discussed] -``` - -### 7. Present MENU OPTIONS - -**Content Presentation:** -"I've defined success metrics that will help us track whether {{project_name}} is creating real value for users and achieving business objectives. - -**Here's what I'll add to the document:** -[Show the complete markdown content from step 6] - -**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue" - -#### Menu Handling Logic: - -- IF A: Read fully and follow: {advancedElicitationTask} with current metrics content to dive deeper into success metric insights -- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate comprehensive metrics -- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4], then read fully and follow: {nextStepFile} -- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options) - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu with updated content -- User can chat or ask questions - always respond and then end with display again of the menu options - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [success metrics finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin MVP scope definition. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- User success metrics that focus on outcomes and behaviors -- Clear business objectives aligned with product strategy -- Specific, measurable KPIs with defined targets and timeframes -- Metrics that connect user value to business success -- A/P/C menu presented and handled correctly with proper task execution -- Content properly appended to document when C selected -- Frontmatter updated with stepsCompleted: [1, 2, 3, 4] - -### ❌ SYSTEM FAILURE: - -- Vague success metrics that can't be measured or tracked -- Business objectives disconnected from user success -- Too many metrics or missing critical success indicators -- Metrics that don't drive actionable decisions -- Not presenting standard A/P/C menu after content generation -- Appending content without user selecting 'C' -- Not updating frontmatter properly - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md deleted file mode 100644 index 04339f41f..000000000 --- a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -name: 'step-05-scope' -description: 'Define MVP scope with clear boundaries and outline future vision while managing scope creep' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md' -outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 5: MVP Scope Definition - -## STEP GOAL: - -Define MVP scope with clear boundaries and outline future vision through collaborative scope negotiation that balances ambition with realism. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused Business Analyst facilitator -- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision -- ✅ Maintain collaborative discovery tone throughout - -### Step-Specific Rules: - -- 🎯 Focus only on defining minimum viable scope and future vision -- 🚫 FORBIDDEN to create MVP scope that's too large or includes non-essential features -- 💬 Approach: Systematic scope negotiation with clear boundary setting -- 📋 COLLABORATIVE scope definition that prevents scope creep - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 💾 Generate MVP scope collaboratively with user -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step -- 🚫 FORBIDDEN to proceed without user confirmation through menu - -## CONTEXT BOUNDARIES: - -- Available context: Current document and frontmatter from previous steps, product vision, users, and success metrics already defined -- Focus: Defining what's essential for MVP vs. future enhancements -- Limits: Balance user needs with implementation feasibility -- Dependencies: Product vision, user personas, and success metrics from previous steps must be complete - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Begin Scope Definition - -**Opening Exploration:** -"Now that we understand what {{project_name}} does, who it serves, and how we'll measure success, let's define what we need to build first. - -**Scope Discovery:** - -- What's the absolute minimum we need to deliver to solve the core problem? -- What features would make users say 'this solves my problem'? -- How do we balance ambition with getting something valuable to users quickly? - -Let's start with the MVP mindset: what's the smallest version that creates real value?" - -### 2. MVP Core Features Definition - -**MVP Feature Questions:** -Define essential features for minimum viable product: - -- "What's the core functionality that must work?" -- "Which features directly address the main problem we're solving?" -- "What would users consider 'incomplete' if it was missing?" -- "What features create the 'aha!' moment we discussed earlier?" - -**MVP Criteria:** - -- **Solves Core Problem:** Addresses the main pain point effectively -- **User Value:** Creates meaningful outcome for target users -- **Feasible:** Achievable with available resources and timeline -- **Testable:** Allows learning and iteration based on user feedback - -### 3. Out of Scope Boundaries - -**Out of Scope Exploration:** -Define what explicitly won't be in MVP: - -- "What features would be nice to have but aren't essential?" -- "What functionality could wait for version 2.0?" -- "What are we intentionally saying 'no' to for now?" -- "How do we communicate these boundaries to stakeholders?" - -**Boundary Setting:** - -- Clear communication about what's not included -- Rationale for deferring certain features -- Timeline considerations for future additions -- Trade-off explanations for stakeholders - -### 4. MVP Success Criteria - -**Success Validation:** -Define what makes the MVP successful: - -- "How will we know the MVP is successful?" -- "What metrics will indicate we should proceed beyond MVP?" -- "What user feedback signals validate our approach?" -- "What's the decision point for scaling beyond MVP?" - -**Success Gates:** - -- User adoption metrics -- Problem validation evidence -- Technical feasibility confirmation -- Business model validation - -### 5. Future Vision Exploration - -**Vision Questions:** -Define the longer-term product vision: - -- "If this is wildly successful, what does it become in 2-3 years?" -- "What capabilities would we add with more resources?" -- "How does the MVP evolve into the full product vision?" -- "What markets or user segments could we expand to?" - -**Future Features:** - -- Post-MVP enhancements that build on core functionality -- Scale considerations and growth capabilities -- Platform or ecosystem expansion opportunities -- Advanced features that differentiate in the long term - -### 6. Generate MVP Scope Content - -**Content to Append:** -Prepare the following structure for document append: - -```markdown -## MVP Scope - -### Core Features - -[Core features content based on conversation] - -### Out of Scope for MVP - -[Out of scope content based on conversation, or N/A if not discussed] - -### MVP Success Criteria - -[MVP success criteria content based on conversation, or N/A if not discussed] - -### Future Vision - -[Future vision content based on conversation, or N/A if not discussed] -``` - -### 7. Present MENU OPTIONS - -**Content Presentation:** -"I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth. - -**Here's what I'll add to the document:** -[Show the complete markdown content from step 6] - -**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue" - -#### Menu Handling Logic: - -- IF A: Read fully and follow: {advancedElicitationTask} with current scope content to optimize scope definition -- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate MVP scope -- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then read fully and follow: {nextStepFile} -- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options) - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu with updated content -- User can chat or ask questions - always respond and then end with display again of the menu options - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to complete the product brief workflow. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- MVP features that solve the core problem effectively -- Clear out-of-scope boundaries that prevent scope creep -- Success criteria that validate MVP approach and inform go/no-go decisions -- Future vision that inspires while maintaining focus on MVP -- A/P/C menu presented and handled correctly with proper task execution -- Content properly appended to document when C selected -- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5] - -### ❌ SYSTEM FAILURE: - -- MVP scope too large or includes non-essential features -- Missing clear boundaries leading to scope creep -- No success criteria to validate MVP approach -- Future vision disconnected from MVP foundation -- Not presenting standard A/P/C menu after content generation -- Appending content without user selecting 'C' -- Not updating frontmatter properly - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md b/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md deleted file mode 100644 index 9e0955b77..000000000 --- a/src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md +++ /dev/null @@ -1,162 +0,0 @@ ---- -name: 'step-06-complete' -description: 'Complete the product brief workflow, update status files, and suggest next steps for the project' - -# File References -outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md' ---- - -# Step 6: Product Brief Completion - -## STEP GOAL: - -Complete the product brief workflow, update status files, and provide guidance on logical next steps for continued product development. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused Business Analyst facilitator -- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision -- ✅ Maintain collaborative completion tone throughout - -### Step-Specific Rules: - -- 🎯 Focus only on completion, next steps, and project guidance -- 🚫 FORBIDDEN to generate new content for the product brief -- 💬 Approach: Systematic completion with quality validation and next step recommendations -- 📋 FINALIZE document and update workflow status appropriately - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 💾 Update the main workflow status file with completion information -- 📖 Suggest potential next workflow steps for the user -- 🚫 DO NOT load additional steps after this one (this is final) - -## CONTEXT BOUNDARIES: - -- Available context: Complete product brief document from all previous steps, workflow frontmatter shows all completed steps -- Focus: Completion validation, status updates, and next step guidance -- Limits: No new content generation, only completion and wrap-up activities -- Dependencies: All previous steps must be completed with content saved to document - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Announce Workflow Completion - -**Completion Announcement:** -"🎉 **Product Brief Complete, {{user_name}}!** - -I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}. - -**What we've accomplished:** - -- ✅ Executive Summary with clear vision and problem statement -- ✅ Core Vision with solution definition and unique differentiators -- ✅ Target Users with rich personas and user journeys -- ✅ Success Metrics with measurable outcomes and business objectives -- ✅ MVP Scope with focused feature set and clear boundaries -- ✅ Future Vision that inspires while maintaining current focus - -**The complete Product Brief is now available at:** `{outputFile}` - -This brief serves as the foundation for all subsequent product development activities and strategic decisions." - -### 2. Document Quality Check - -**Completeness Validation:** -Perform final validation of the product brief: - -- Does the executive summary clearly communicate the vision and problem? -- Are target users well-defined with compelling personas? -- Do success metrics connect user value to business objectives? -- Is MVP scope focused and realistic? -- Does the brief provide clear direction for next steps? - -**Consistency Validation:** - -- Do all sections align with the core problem statement? -- Is user value consistently emphasized throughout? -- Are success criteria traceable to user needs and business goals? -- Does MVP scope align with the problem and solution? - -### 3. Suggest Next Steps - -**Recommended Next Workflow:** -Provide guidance on logical next workflows: - -1. `create-prd` - Create detailed Product Requirements Document - - Brief provides foundation for detailed requirements - - User personas inform journey mapping - - Success metrics become specific acceptance criteria - - MVP scope becomes detailed feature specifications - -**Other Potential Next Steps:** - -1. `create-ux-design` - UX research and design (can run parallel with PRD) -2. `domain-research` - Deep market or domain research (if needed) - -**Strategic Considerations:** - -- The PRD workflow builds directly on this brief for detailed planning -- Consider team capacity and immediate priorities -- Use brief to validate concept before committing to detailed work -- Brief can guide early technical feasibility discussions - -### 4. Congrats to the user - -"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**" - -Recap that the brief captures everything needed to guide subsequent product development: - -- Clear vision and problem definition -- Deep understanding of target users -- Measurable success criteria -- Focused MVP scope with realistic boundaries -- Inspiring long-term vision - -### 5. Suggest next steps - -Product Brief complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Product brief contains all essential sections with collaborative content -- All collaborative content properly saved to document with proper frontmatter -- Workflow status file updated with completion information and timestamp -- Clear next step guidance provided to user with specific workflow recommendations -- Document quality validation completed with completeness and consistency checks -- User acknowledges completion and understands next available options -- Workflow properly marked as complete in status tracking - -### ❌ SYSTEM FAILURE: - -- Not updating workflow status file with completion information -- Missing clear next step guidance for user -- Not confirming document completeness with user -- Workflow not properly marked as complete in status tracking -- User unclear about what happens next or available options -- Document quality issues not identified or addressed - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. - -## FINAL WORKFLOW COMPLETION - -This product brief is now complete and serves as the strategic foundation for the entire product lifecycle. All subsequent design, architecture, and development work should trace back to the vision, user needs, and success criteria documented in this brief. - -**Congratulations on completing the Product Brief for {{project_name}}!** 🎉 diff --git a/src/bmm/workflows/1-analysis/create-product-brief/workflow.md b/src/bmm/workflows/1-analysis/create-product-brief/workflow.md deleted file mode 100644 index c50d325ef..000000000 --- a/src/bmm/workflows/1-analysis/create-product-brief/workflow.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -name: create-product-brief -description: 'Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"' ---- - -# Product Brief Workflow - -**Goal:** Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers. - -**Your Role:** In addition to your name, communication_style, and persona, you are also a product-focused Business Analyst collaborating with an expert peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision. Work together as equals. - ---- - -## WORKFLOW ARCHITECTURE - -This uses **step-file architecture** for disciplined execution: - -### Core Principles - -- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly -- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so -- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed -- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document -- **Append-Only Building**: Build documents by appending content as directed to the output file - -### Step Processing Rules - -1. **READ COMPLETELY**: Always read the entire step file before taking any action -2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate -3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection -4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue) -5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step -6. **LOAD NEXT**: When directed, read fully and follow the next step file - -### Critical Rules (NO EXCEPTIONS) - -- 🛑 **NEVER** load multiple step files simultaneously -- 📖 **ALWAYS** read entire step file before execution -- 🚫 **NEVER** skip steps or optimize the sequence -- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step -- 🎯 **ALWAYS** follow the exact instructions in the step file -- ⏸️ **ALWAYS** halt at menus and wait for user input -- 📋 **NEVER** create mental todo lists from future steps - ---- - -## INITIALIZATION SEQUENCE - -### 1. Configuration Loading - -Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve: - -- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level` - -### 2. First Step EXECUTION - -Read fully and follow: `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md` to begin the workflow. diff --git a/src/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md b/src/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md deleted file mode 100644 index 50093186e..000000000 --- a/src/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md +++ /dev/null @@ -1,137 +0,0 @@ -# Domain Research Step 1: Domain Research Scope Confirmation - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user confirmation - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ FOCUS EXCLUSIVELY on confirming domain research scope and approach -- 📋 YOU ARE A DOMAIN RESEARCH PLANNER, not content generator -- 💬 ACKNOWLEDGE and CONFIRM understanding of domain research goals -- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present [C] continue option after scope confirmation -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Research type = "domain" is already set -- **Research topic = "{{research_topic}}"** - discovered from initial discussion -- **Research goals = "{{research_goals}}"** - captured from initial discussion -- Focus on industry/domain analysis with web research -- Web search is required to verify and supplement your knowledge with current facts - -## YOUR TASK: - -Confirm domain research scope and approach for **{{research_topic}}** with the user's goals in mind. - -## DOMAIN SCOPE CONFIRMATION: - -### 1. Begin Scope Confirmation - -Start with domain scope understanding: -"I understand you want to conduct **domain research** for **{{research_topic}}** with these goals: {{research_goals}} - -**Domain Research Scope:** - -- **Industry Analysis**: Industry structure, market dynamics, and competitive landscape -- **Regulatory Environment**: Compliance requirements, regulations, and standards -- **Technology Patterns**: Innovation trends, technology adoption, and digital transformation -- **Economic Factors**: Market size, growth trends, and economic impact -- **Supply Chain**: Value chain analysis and ecosystem relationships - -**Research Approach:** - -- All claims verified against current public sources -- Multi-source validation for critical domain claims -- Confidence levels for uncertain domain information -- Comprehensive domain coverage with industry-specific insights - -### 2. Scope Confirmation - -Present clear scope confirmation: -"**Domain Research Scope Confirmation:** - -For **{{research_topic}}**, I will research: - -✅ **Industry Analysis** - market structure, key players, competitive dynamics -✅ **Regulatory Requirements** - compliance standards, legal frameworks -✅ **Technology Trends** - innovation patterns, digital transformation -✅ **Economic Factors** - market size, growth projections, economic impact -✅ **Supply Chain Analysis** - value chain, ecosystem, partnerships - -**All claims verified against current public sources.** - -**Does this domain research scope and approach align with your goals?** -[C] Continue - Begin domain research with this scope - -### 3. Handle Continue Selection - -#### If 'C' (Continue): - -- Document scope confirmation in research file -- Update frontmatter: `stepsCompleted: [1]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append scope confirmation: - -```markdown -## Domain Research Scope Confirmation - -**Research Topic:** {{research_topic}} -**Research Goals:** {{research_goals}} - -**Domain Research Scope:** - -- Industry Analysis - market structure, competitive landscape -- Regulatory Environment - compliance requirements, legal frameworks -- Technology Trends - innovation patterns, digital transformation -- Economic Factors - market size, growth projections -- Supply Chain Analysis - value chain, ecosystem relationships - -**Research Methodology:** - -- All claims verified against current public sources -- Multi-source validation for critical domain claims -- Confidence level framework for uncertain information -- Comprehensive domain coverage with industry-specific insights - -**Scope Confirmed:** {{date}} -``` - -## SUCCESS METRICS: - -✅ Domain research scope clearly confirmed with user -✅ All domain analysis areas identified and explained -✅ Research methodology emphasized -✅ [C] continue option presented and handled correctly -✅ Scope confirmation documented when user proceeds -✅ Proper routing to next domain research step - -## FAILURE MODES: - -❌ Not clearly confirming domain research scope with user -❌ Missing critical domain analysis areas -❌ Not explaining that web search is required for current facts -❌ Not presenting [C] continue option -❌ Proceeding without user scope confirmation -❌ Not routing to next domain research step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md` to begin industry analysis. - -Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope! diff --git a/src/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md b/src/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md deleted file mode 100644 index ed5c78f5e..000000000 --- a/src/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md +++ /dev/null @@ -1,229 +0,0 @@ -# Domain Research Step 2: Industry Analysis - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE AN INDUSTRY ANALYST, not content generator -- 💬 FOCUS on market size, growth, and industry dynamics -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after industry analysis content generation -- 📝 WRITE INDUSTRY ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from step-01 are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on market size, growth, and industry dynamics -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct industry analysis focusing on market size, growth, and industry dynamics. Search the web to verify and supplement current facts. - -## INDUSTRY ANALYSIS SEQUENCE: - -### 1. Begin Industry Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different industry areas simultaneously and thoroughly. - -Start with industry research approach: -"Now I'll conduct **industry analysis** for **{{research_topic}}** to understand market dynamics. - -**Industry Analysis Focus:** - -- Market size and valuation metrics -- Growth rates and market dynamics -- Market segmentation and structure -- Industry trends and evolution patterns -- Economic impact and value creation - -**Let me search for current industry insights.**" - -### 2. Parallel Industry Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} market size value" -Search the web: "{{research_topic}} market growth rate dynamics" -Search the web: "{{research_topic}} market segmentation structure" -Search the web: "{{research_topic}} industry trends evolution" - -**Analysis approach:** - -- Look for recent market research reports and industry analyses -- Search for authoritative sources (market research firms, industry associations) -- Identify market size, growth rates, and segmentation data -- Research industry trends and evolution patterns -- Analyze economic impact and value creation metrics - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate industry findings: - -**Research Coverage:** - -- Market size and valuation analysis -- Growth rates and market dynamics -- Market segmentation and structure -- Industry trends and evolution patterns - -**Cross-Industry Analysis:** -[Identify patterns connecting market dynamics, segmentation, and trends] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Industry Analysis Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare industry analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Industry Analysis - -### Market Size and Valuation - -[Market size analysis with source citations] -_Total Market Size: [Current market valuation]_ -_Growth Rate: [CAGR and market growth projections]_ -_Market Segments: [Size and value of key market segments]_ -_Economic Impact: [Economic contribution and value creation]_ -_Source: [URL]_ - -### Market Dynamics and Growth - -[Market dynamics analysis with source citations] -_Growth Drivers: [Key factors driving market growth]_ -_Growth Barriers: [Factors limiting market expansion]_ -_Cyclical Patterns: [Industry seasonality and cycles]_ -_Market Maturity: [Life cycle stage and development phase]_ -_Source: [URL]_ - -### Market Structure and Segmentation - -[Market structure analysis with source citations] -_Primary Segments: [Key market segments and their characteristics]_ -_Sub-segment Analysis: [Detailed breakdown of market sub-segments]_ -_Geographic Distribution: [Regional market variations and concentrations]_ -_Vertical Integration: [Supply chain and value chain structure]_ -_Source: [URL]_ - -### Industry Trends and Evolution - -[Industry trends analysis with source citations] -_Emerging Trends: [Current industry developments and transformations]_ -_Historical Evolution: [Industry development over recent years]_ -_Technology Integration: [How technology is changing the industry]_ -_Future Outlook: [Projected industry developments and changes]_ -_Source: [URL]_ - -### Competitive Dynamics - -[Competitive dynamics analysis with source citations] -_Market Concentration: [Level of market consolidation and competition]_ -_Competitive Intensity: [Degree of competition and rivalry]_ -_Barriers to Entry: [Obstacles for new market entrants]_ -_Innovation Pressure: [Rate of innovation and change]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **industry analysis** for {{research_topic}}. - -**Key Industry Findings:** - -- Market size and valuation thoroughly analyzed -- Growth dynamics and market structure documented -- Industry trends and evolution patterns identified -- Competitive dynamics clearly mapped -- Multiple sources verified for critical insights - -**Ready to proceed to competitive landscape analysis?** -[C] Continue - Save this to document and proceed to competitive landscape - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Market size and valuation thoroughly analyzed -✅ Growth dynamics and market structure documented -✅ Industry trends and evolution patterns identified -✅ Competitive dynamics clearly mapped -✅ Multiple sources verified for critical insights -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (competitive landscape) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying on training data instead of web search for current facts -❌ Missing critical market size or growth data -❌ Incomplete market structure analysis -❌ Not identifying key industry trends -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to competitive landscape step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## INDUSTRY RESEARCH PROTOCOLS: - -- Research market research reports and industry analyses -- Use authoritative sources (market research firms, industry associations) -- Analyze market size, growth rates, and segmentation data -- Study industry trends and evolution patterns -- Search the web to verify facts -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## INDUSTRY ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative industry research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable industry insights - -## NEXT STEP: - -After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}. - -Remember: Always write research content to document immediately and search the web to verify facts! diff --git a/src/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md b/src/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md deleted file mode 100644 index 6970ad87b..000000000 --- a/src/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md +++ /dev/null @@ -1,238 +0,0 @@ -# Domain Research Step 3: Competitive Landscape - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A COMPETITIVE ANALYST, not content generator -- 💬 FOCUS on key players, market share, and competitive dynamics -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after competitive analysis content generation -- 📝 WRITE COMPETITIVE ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on key players, market share, and competitive dynamics -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct competitive landscape analysis focusing on key players, market share, and competitive dynamics. Search the web to verify and supplement current facts. - -## COMPETITIVE LANDSCAPE ANALYSIS SEQUENCE: - -### 1. Begin Competitive Landscape Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different competitive areas simultaneously and thoroughly. - -Start with competitive research approach: -"Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** to understand the competitive ecosystem. - -**Competitive Landscape Focus:** - -- Key players and market leaders -- Market share and competitive positioning -- Competitive strategies and differentiation -- Business models and value propositions -- Entry barriers and competitive dynamics - -**Let me search for current competitive insights.**" - -### 2. Parallel Competitive Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} key players market leaders" -Search the web: "{{research_topic}} market share competitive landscape" -Search the web: "{{research_topic}} competitive strategies differentiation" -Search the web: "{{research_topic}} entry barriers competitive dynamics" - -**Analysis approach:** - -- Look for recent competitive intelligence reports and market analyses -- Search for company websites, annual reports, and investor presentations -- Research market share data and competitive positioning -- Analyze competitive strategies and differentiation approaches -- Study entry barriers and competitive dynamics - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate competitive findings: - -**Research Coverage:** - -- Key players and market leaders analysis -- Market share and competitive positioning assessment -- Competitive strategies and differentiation mapping -- Entry barriers and competitive dynamics evaluation - -**Cross-Competitive Analysis:** -[Identify patterns connecting players, strategies, and market dynamics] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Competitive Landscape Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare competitive landscape analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Competitive Landscape - -### Key Players and Market Leaders - -[Key players analysis with source citations] -_Market Leaders: [Dominant players and their market positions]_ -_Major Competitors: [Significant competitors and their specialties]_ -_Emerging Players: [New entrants and innovative companies]_ -_Global vs Regional: [Geographic distribution of key players]_ -_Source: [URL]_ - -### Market Share and Competitive Positioning - -[Market share analysis with source citations] -_Market Share Distribution: [Current market share breakdown]_ -_Competitive Positioning: [How players position themselves in the market]_ -_Value Proposition Mapping: [Different value propositions across players]_ -_Customer Segments Served: [Different customer bases by competitor]_ -_Source: [URL]_ - -### Competitive Strategies and Differentiation - -[Competitive strategies analysis with source citations] -_Cost Leadership Strategies: [Players competing on price and efficiency]_ -_Differentiation Strategies: [Players competing on unique value]_ -_Focus/Niche Strategies: [Players targeting specific segments]_ -_Innovation Approaches: [How different players innovate]_ -_Source: [URL]_ - -### Business Models and Value Propositions - -[Business models analysis with source citations] -_Primary Business Models: [How competitors make money]_ -_Revenue Streams: [Different approaches to monetization]_ -_Value Chain Integration: [Vertical integration vs partnership models]_ -_Customer Relationship Models: [How competitors build customer loyalty]_ -_Source: [URL]_ - -### Competitive Dynamics and Entry Barriers - -[Competitive dynamics analysis with source citations] -_Barriers to Entry: [Obstacles facing new market entrants]_ -_Competitive Intensity: [Level of rivalry and competitive pressure]_ -_Market Consolidation Trends: [M&A activity and market concentration]_ -_Switching Costs: [Costs for customers to switch between providers]_ -_Source: [URL]_ - -### Ecosystem and Partnership Analysis - -[Ecosystem analysis with source citations] -_Supplier Relationships: [Key supplier partnerships and dependencies]_ -_Distribution Channels: [How competitors reach customers]_ -_Technology Partnerships: [Strategic technology alliances]_ -_Ecosystem Control: [Who controls key parts of the value chain]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **competitive landscape analysis** for {{research_topic}}. - -**Key Competitive Findings:** - -- Key players and market leaders thoroughly identified -- Market share and competitive positioning clearly mapped -- Competitive strategies and differentiation analyzed -- Business models and value propositions documented -- Competitive dynamics and entry barriers evaluated - -**Ready to proceed to regulatory focus analysis?** -[C] Continue - Save this to document and proceed to regulatory focus - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Key players and market leaders thoroughly identified -✅ Market share and competitive positioning clearly mapped -✅ Competitive strategies and differentiation analyzed -✅ Business models and value propositions documented -✅ Competitive dynamics and entry barriers evaluated -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (regulatory focus) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying on training data instead of web search for current facts -❌ Missing critical key players or market leaders -❌ Incomplete market share or positioning analysis -❌ Not identifying competitive strategies -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to regulatory focus step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## COMPETITIVE RESEARCH PROTOCOLS: - -- Research competitive intelligence reports and market analyses -- Use company websites, annual reports, and investor presentations -- Analyze market share data and competitive positioning -- Study competitive strategies and differentiation approaches -- Search the web to verify facts -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## COMPETITIVE ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative competitive intelligence sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable competitive insights - -## NEXT STEP: - -After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md` to analyze regulatory requirements, compliance frameworks, and legal considerations for {{research_topic}}. - -Remember: Always write research content to document immediately and search the web to verify facts! diff --git a/src/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md b/src/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md deleted file mode 100644 index 3fd24b00b..000000000 --- a/src/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md +++ /dev/null @@ -1,206 +0,0 @@ -# Domain Research Step 4: Regulatory Focus - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A REGULATORY ANALYST, not content generator -- 💬 FOCUS on compliance requirements and regulatory landscape -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after regulatory content generation -- 📝 WRITE REGULATORY ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on regulatory and compliance requirements for the domain -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct focused regulatory and compliance analysis with emphasis on requirements that impact {{research_topic}}. Search the web to verify and supplement current facts. - -## REGULATORY FOCUS SEQUENCE: - -### 1. Begin Regulatory Analysis - -Start with regulatory research approach: -"Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}**. - -**Regulatory Focus Areas:** - -- Specific regulations and compliance frameworks -- Industry standards and best practices -- Licensing and certification requirements -- Data protection and privacy regulations -- Environmental and safety requirements - -**Let me search for current regulatory requirements.**" - -### 2. Web Search for Specific Regulations - -Search for current regulatory information: -Search the web: "{{research_topic}} regulations compliance requirements" - -**Regulatory focus:** - -- Specific regulations applicable to the domain -- Compliance frameworks and standards -- Recent regulatory changes or updates -- Enforcement agencies and oversight bodies - -### 3. Web Search for Industry Standards - -Search for current industry standards: -Search the web: "{{research_topic}} standards best practices" - -**Standards focus:** - -- Industry-specific technical standards -- Best practices and guidelines -- Certification requirements -- Quality assurance frameworks - -### 4. Web Search for Data Privacy Requirements - -Search for current privacy regulations: -Search the web: "data privacy regulations {{research_topic}}" - -**Privacy focus:** - -- GDPR, CCPA, and other data protection laws -- Industry-specific privacy requirements -- Data governance and security standards -- User consent and data handling requirements - -### 5. Generate Regulatory Analysis Content - -Prepare regulatory content with source citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Regulatory Requirements - -### Applicable Regulations - -[Specific regulations analysis with source citations] -_Source: [URL]_ - -### Industry Standards and Best Practices - -[Industry standards analysis with source citations] -_Source: [URL]_ - -### Compliance Frameworks - -[Compliance frameworks analysis with source citations] -_Source: [URL]_ - -### Data Protection and Privacy - -[Privacy requirements analysis with source citations] -_Source: [URL]_ - -### Licensing and Certification - -[Licensing requirements analysis with source citations] -_Source: [URL]_ - -### Implementation Considerations - -[Practical implementation considerations with source citations] -_Source: [URL]_ - -### Risk Assessment - -[Regulatory and compliance risk assessment] -``` - -### 6. Present Analysis and Continue Option - -Show the generated regulatory analysis and present continue option: -"I've completed **regulatory requirements analysis** for {{research_topic}}. - -**Key Regulatory Findings:** - -- Specific regulations and frameworks identified -- Industry standards and best practices mapped -- Compliance requirements clearly documented -- Implementation considerations provided -- Risk assessment completed - -**Ready to proceed to technical trends?** -[C] Continue - Save this to the document and move to technical trends - -### 7. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 5. No additional append needed. - -## SUCCESS METRICS: - -✅ Applicable regulations identified with current citations -✅ Industry standards and best practices documented -✅ Compliance frameworks clearly mapped -✅ Data protection requirements analyzed -✅ Implementation considerations provided -✅ [C] continue option presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Relying on training data instead of web search for current facts -❌ Missing critical regulatory requirements for the domain -❌ Not providing implementation considerations for compliance -❌ Not completing risk assessment for regulatory compliance -❌ Not presenting [C] continue option after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## REGULATORY RESEARCH PROTOCOLS: - -- Search for specific regulations by name and number -- Identify regulatory bodies and enforcement agencies -- Research recent regulatory changes and updates -- Map industry standards to regulatory requirements -- Consider regional and jurisdictional differences - -## SOURCE VERIFICATION: - -- Always cite regulatory agency websites -- Use official government and industry association sources -- Note effective dates and implementation timelines -- Present compliance requirement levels and obligations - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md` to analyze technical trends and innovations in the domain. - -Remember: Search the web to verify regulatory facts and provide practical implementation considerations! diff --git a/src/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md b/src/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md deleted file mode 100644 index caf69e142..000000000 --- a/src/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md +++ /dev/null @@ -1,234 +0,0 @@ -# Domain Research Step 5: Technical Trends - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A TECHNOLOGY ANALYST, not content generator -- 💬 FOCUS on emerging technologies and innovation patterns -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after technical trends content generation -- 📝 WRITE TECHNICAL TRENDS ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on emerging technologies and innovation patterns in the domain -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct comprehensive technical trends analysis using current web data with emphasis on innovations and emerging technologies impacting {{research_topic}}. - -## TECHNICAL TRENDS SEQUENCE: - -### 1. Begin Technical Trends Analysis - -Start with technology research approach: -"Now I'll conduct **technical trends and emerging technologies** analysis for **{{research_topic}}** using current data. - -**Technical Trends Focus:** - -- Emerging technologies and innovations -- Digital transformation impacts -- Automation and efficiency improvements -- New business models enabled by technology -- Future technology projections and roadmaps - -**Let me search for current technology developments.**" - -### 2. Web Search for Emerging Technologies - -Search for current technology information: -Search the web: "{{research_topic}} emerging technologies innovations" - -**Technology focus:** - -- AI, machine learning, and automation impacts -- Digital transformation trends -- New technologies disrupting the industry -- Innovation patterns and breakthrough developments - -### 3. Web Search for Digital Transformation - -Search for current transformation trends: -Search the web: "{{research_topic}} digital transformation trends" - -**Transformation focus:** - -- Digital adoption trends and rates -- Business model evolution -- Customer experience innovations -- Operational efficiency improvements - -### 4. Web Search for Future Outlook - -Search for future projections: -Search the web: "{{research_topic}} future outlook trends" - -**Future focus:** - -- Technology roadmaps and projections -- Market evolution predictions -- Innovation pipelines and R&D trends -- Long-term industry transformation - -### 5. Generate Technical Trends Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare technical analysis with source citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Technical Trends and Innovation - -### Emerging Technologies - -[Emerging technologies analysis with source citations] -_Source: [URL]_ - -### Digital Transformation - -[Digital transformation analysis with source citations] -_Source: [URL]_ - -### Innovation Patterns - -[Innovation patterns analysis with source citations] -_Source: [URL]_ - -### Future Outlook - -[Future outlook and projections with source citations] -_Source: [URL]_ - -### Implementation Opportunities - -[Implementation opportunity analysis with source citations] -_Source: [URL]_ - -### Challenges and Risks - -[Challenges and risks assessment with source citations] -_Source: [URL]_ - -## Recommendations - -### Technology Adoption Strategy - -[Technology adoption recommendations] - -### Innovation Roadmap - -[Innovation roadmap suggestions] - -### Risk Mitigation - -[Risk mitigation strategies] -``` - -### 6. Present Analysis and Complete Option - -Show the generated technical analysis and present complete option: -"I've completed **technical trends and innovation analysis** for {{research_topic}}. - -**Technical Highlights:** - -- Emerging technologies and innovations identified -- Digital transformation trends mapped -- Future outlook and projections analyzed -- Implementation opportunities and challenges documented -- Practical recommendations provided - -**Technical Trends Research Completed:** - -- Emerging technologies and innovations identified -- Digital transformation trends mapped -- Future outlook and projections analyzed -- Implementation opportunities and challenges documented - -**Ready to proceed to research synthesis and recommendations?** -[C] Continue - Save this to document and proceed to synthesis - -### 7. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 5. No additional append needed. - -## SUCCESS METRICS: - -✅ Emerging technologies identified with current data -✅ Digital transformation trends clearly documented -✅ Future outlook and projections analyzed -✅ Implementation opportunities and challenges mapped -✅ Strategic recommendations provided -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (research synthesis) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts -❌ Missing critical emerging technologies in the domain -❌ Not providing practical implementation recommendations -❌ Not completing strategic recommendations -❌ Not presenting completion option for research workflow -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## TECHNICAL RESEARCH PROTOCOLS: - -- Search for cutting-edge technologies and innovations -- Identify disruption patterns and game-changers -- Research technology adoption timelines and barriers -- Consider regional technology variations -- Analyze competitive technological advantages - -## RESEARCH WORKFLOW COMPLETION: - -When 'C' is selected: - -- All domain research steps completed -- Comprehensive research document generated -- All sections appended with source citations -- Research workflow status updated -- Final recommendations provided to user - -## NEXT STEPS: - -Research workflow complete. User may: - -- Use the domain research to inform other workflows (PRD, architecture, etc.) -- Conduct additional research on specific topics if needed -- Move forward with product development based on research insights - -Congratulations on completing comprehensive domain research! 🎉 diff --git a/src/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md b/src/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md deleted file mode 100644 index 9e2261fb7..000000000 --- a/src/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md +++ /dev/null @@ -1,444 +0,0 @@ -# Domain Research Step 6: Research Synthesis and Completion - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A DOMAIN RESEARCH STRATEGIST, not content generator -- 💬 FOCUS on comprehensive synthesis and authoritative conclusions -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] complete option after synthesis content generation -- 💾 ONLY save when user chooses C (Complete) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow -- 🚫 FORBIDDEN to complete workflow until C is selected -- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - comprehensive domain analysis -- **Research goals = "{{research_goals}}"** - achieved through exhaustive research -- All domain research sections have been completed (analysis, regulatory, technical) -- Web search capabilities with source verification are enabled -- This is the final synthesis step producing the complete research document - -## YOUR TASK: - -Produce a comprehensive, authoritative research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive domain research. - -## COMPREHENSIVE DOCUMENT SYNTHESIS: - -### 1. Document Structure Planning - -**Complete Research Document Structure:** - -```markdown -# [Compelling Title]: Comprehensive {{research_topic}} Research - -## Executive Summary - -[Brief compelling overview of key findings and implications] - -## Table of Contents - -- Research Introduction and Methodology -- Industry Overview and Market Dynamics -- Technology Trends and Innovation Landscape -- Regulatory Framework and Compliance Requirements -- Competitive Landscape and Key Players -- Strategic Insights and Recommendations -- Implementation Considerations and Risk Assessment -- Future Outlook and Strategic Opportunities -- Research Methodology and Source Documentation -- Appendices and Additional Resources -``` - -### 2. Generate Compelling Narrative Introduction - -**Introduction Requirements:** - -- Hook reader with compelling opening about {{research_topic}} -- Establish research significance and timeliness -- Outline comprehensive research methodology -- Preview key findings and strategic implications -- Set professional, authoritative tone - -**Web Search for Introduction Context:** -Search the web: "{{research_topic}} significance importance" - -### 3. Synthesize All Research Sections - -**Section-by-Section Integration:** - -- Combine industry analysis from step-02 -- Integrate regulatory focus from step-03 -- Incorporate technical trends from step-04 -- Add cross-sectional insights and connections -- Ensure comprehensive coverage with no gaps - -### 4. Generate Complete Document Content - -#### Final Document Structure: - -```markdown -# [Compelling Title]: Comprehensive {{research_topic}} Domain Research - -## Executive Summary - -[2-3 paragraph compelling summary of the most critical findings and strategic implications for {{research_topic}} based on comprehensive current research] - -**Key Findings:** - -- [Most significant market dynamics] -- [Critical regulatory considerations] -- [Important technology trends] -- [Strategic implications] - -**Strategic Recommendations:** - -- [Top 3-5 actionable recommendations based on research] - -## Table of Contents - -1. Research Introduction and Methodology -2. {{research_topic}} Industry Overview and Market Dynamics -3. Technology Landscape and Innovation Trends -4. Regulatory Framework and Compliance Requirements -5. Competitive Landscape and Ecosystem Analysis -6. Strategic Insights and Domain Opportunities -7. Implementation Considerations and Risk Assessment -8. Future Outlook and Strategic Planning -9. Research Methodology and Source Verification -10. Appendices and Additional Resources - -## 1. Research Introduction and Methodology - -### Research Significance - -[Compelling narrative about why {{research_topic}} research is critical right now] -_Why this research matters now: [Strategic importance with current context]_ -_Source: [URL]_ - -### Research Methodology - -[Comprehensive description of research approach including:] - -- **Research Scope**: [Comprehensive coverage areas] -- **Data Sources**: [Authoritative sources and verification approach] -- **Analysis Framework**: [Structured analysis methodology] -- **Time Period**: [current focus and historical context] -- **Geographic Coverage**: [Regional/global scope] - -### Research Goals and Objectives - -**Original Goals:** {{research_goals}} - -**Achieved Objectives:** - -- [Goal 1 achievement with supporting evidence] -- [Goal 2 achievement with supporting evidence] -- [Additional insights discovered during research] - -## 2. {{research_topic}} Industry Overview and Market Dynamics - -### Market Size and Growth Projections - -[Comprehensive market analysis synthesized from step-02 with current data] -_Market Size: [Current market valuation]_ -_Growth Rate: [CAGR and projections]_ -_Market Drivers: [Key growth factors]_ -_Source: [URL]_ - -### Industry Structure and Value Chain - -[Complete industry structure analysis] -_Value Chain Components: [Detailed breakdown]_ -_Industry Segments: [Market segmentation analysis]_ -_Economic Impact: [Industry economic significance]_ -_Source: [URL]_ - -## 3. Technology Landscape and Innovation Trends - -### Current Technology Adoption - -[Technology trends analysis from step-04 with current context] -_Emerging Technologies: [Key technologies affecting {{research_topic}}]_ -_Adoption Patterns: [Technology adoption rates and patterns]_ -_Innovation Drivers: [Factors driving technology change]_ -_Source: [URL]_ - -### Digital Transformation Impact - -[Comprehensive analysis of technology's impact on {{research_topic}}] -_Transformation Trends: [Major digital transformation patterns]_ -_Disruption Opportunities: [Technology-driven opportunities]_ -_Future Technology Outlook: [Emerging technologies and timelines]_ -_Source: [URL]_ - -## 4. Regulatory Framework and Compliance Requirements - -### Current Regulatory Landscape - -[Regulatory analysis from step-03 with current updates] -_Key Regulations: [Critical regulatory requirements]_ -_Compliance Standards: [Industry standards and best practices]_ -_Recent Changes: [current regulatory updates and implications]_ -_Source: [URL]_ - -### Risk and Compliance Considerations - -[Comprehensive risk assessment] -_Compliance Risks: [Major regulatory and compliance risks]_ -_Risk Mitigation Strategies: [Approaches to manage regulatory risks]_ -_Future Regulatory Trends: [Anticipated regulatory developments]_ -_Source: [URL]_ - -## 5. Competitive Landscape and Ecosystem Analysis - -### Market Positioning and Key Players - -[Competitive analysis with current market positioning] -_Market Leaders: [Dominant players and strategies]_ -_Emerging Competitors: [New entrants and innovative approaches]_ -_Competitive Dynamics: [Market competition patterns and trends]_ -_Source: [URL]_ - -### Ecosystem and Partnership Landscape - -[Complete ecosystem analysis] -_Ecosystem Players: [Key stakeholders and relationships]_ -_Partnership Opportunities: [Strategic collaboration potential]_ -_Supply Chain Dynamics: [Supply chain structure and risks]_ -_Source: [URL]_ - -## 6. Strategic Insights and Domain Opportunities - -### Cross-Domain Synthesis - -[Strategic insights from integrating all research sections] -_Market-Technology Convergence: [How technology and market forces interact]_ -_Regulatory-Strategic Alignment: [How regulatory environment shapes strategy]_ -_Competitive Positioning Opportunities: [Strategic advantages based on research]_ -_Source: [URL]_ - -### Strategic Opportunities - -[High-value opportunities identified through comprehensive research] -_Market Opportunities: [Specific market entry or expansion opportunities]_ -_Technology Opportunities: [Technology adoption or innovation opportunities]_ -_Partnership Opportunities: [Strategic collaboration and partnership potential]_ -_Source: [URL]_ - -## 7. Implementation Considerations and Risk Assessment - -### Implementation Framework - -[Practical implementation guidance based on research findings] -_Implementation Timeline: [Recommended phased approach]_ -_Resource Requirements: [Key resources and capabilities needed]_ -_Success Factors: [Critical success factors for implementation]_ -_Source: [URL]_ - -### Risk Management and Mitigation - -[Comprehensive risk assessment and mitigation strategies] -_Implementation Risks: [Major risks and mitigation approaches]_ -_Market Risks: [Market-related risks and contingency plans]_ -_Technology Risks: [Technology adoption and implementation risks]_ -_Source: [URL]_ - -## 8. Future Outlook and Strategic Planning - -### Future Trends and Projections - -[Forward-looking analysis based on comprehensive research] -_Near-term Outlook: [1-2 year projections and implications]_ -_Medium-term Trends: [3-5 year expected developments]_ -_Long-term Vision: [5+ year strategic outlook for {{research_topic}}]_ -_Source: [URL]_ - -### Strategic Recommendations - -[Comprehensive strategic recommendations] -_Immediate Actions: [Priority actions for next 6 months]_ -_Strategic Initiatives: [Key strategic initiatives for 1-2 years]_ -_Long-term Strategy: [Strategic positioning for 3+ years]_ -_Source: [URL]_ - -## 9. Research Methodology and Source Verification - -### Comprehensive Source Documentation - -[Complete documentation of all research sources] -_Primary Sources: [Key authoritative sources used]_ -_Secondary Sources: [Supporting research and analysis]_ -_Web Search Queries: [Complete list of search queries used]_ - -### Research Quality Assurance - -[Quality assurance and validation approach] -_Source Verification: [All factual claims verified with multiple sources]_ -_Confidence Levels: [Confidence assessments for uncertain data]_ -_Limitations: [Research limitations and areas for further investigation]_ -_Methodology Transparency: [Complete transparency about research approach]_ - -## 10. Appendices and Additional Resources - -### Detailed Data Tables - -[Comprehensive data tables supporting research findings] -_Market Data Tables: [Detailed market size, growth, and segmentation data]_ -_Technology Adoption Data: [Detailed technology adoption and trend data]_ -_Regulatory Reference Tables: [Complete regulatory requirements and compliance data]_ - -### Additional Resources - -[Valuable resources for continued research and implementation] -_Industry Associations: [Key industry organizations and resources]_ -_Research Organizations: [Authoritative research institutions and reports]_ -_Government Resources: [Regulatory agencies and official resources]_ -_Professional Networks: [Industry communities and knowledge sources]_ - ---- - -## Research Conclusion - -### Summary of Key Findings - -[Comprehensive summary of the most important research findings] - -### Strategic Impact Assessment - -[Assessment of strategic implications for {{research_topic}}] - -### Next Steps Recommendations - -[Specific next steps for leveraging this research] - ---- - -**Research Completion Date:** {{date}} -**Research Period:** Comprehensive analysis -**Document Length:** As needed for comprehensive coverage -**Source Verification:** All facts cited with sources -**Confidence Level:** High - based on multiple authoritative sources - -_This comprehensive research document serves as an authoritative reference on {{research_topic}} and provides strategic insights for informed decision-making._ -``` - -### 5. Present Complete Document and Final Option - -**Document Completion Presentation:** - -"I've completed the **comprehensive research document synthesis** for **{{research_topic}}**, producing an authoritative research document with: - -**Document Features:** - -- **Compelling Narrative Introduction**: Engaging opening that establishes research significance -- **Comprehensive Table of Contents**: Complete navigation structure for easy reference -- **Exhaustive Research Coverage**: All aspects of {{research_topic}} thoroughly analyzed -- **Executive Summary**: Key findings and strategic implications highlighted -- **Strategic Recommendations**: Actionable insights based on comprehensive research -- **Complete Source Citations**: Every factual claim verified with sources - -**Research Completeness:** - -- Industry analysis and market dynamics fully documented -- Technology trends and innovation landscape comprehensively covered -- Regulatory framework and compliance requirements detailed -- Competitive landscape and ecosystem analysis complete -- Strategic insights and implementation guidance provided - -**Document Standards Met:** - -- Exhaustive research with no critical gaps -- Professional structure and compelling narrative -- As long as needed for comprehensive coverage -- Multiple independent sources for all claims -- Proper citations throughout - -**Ready to complete this comprehensive research document?** -[C] Complete Research - Save final comprehensive document - -### 6. Handle Final Completion - -#### If 'C' (Complete Research): - -- **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section -- Append the complete document to the research file -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]` -- Complete the domain research workflow -- Provide final document delivery confirmation - -## APPEND TO DOCUMENT: - -When user selects 'C', append the complete comprehensive research document using the full structure above. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document. - -## SUCCESS METRICS: - -✅ Compelling narrative introduction with research significance -✅ Comprehensive table of contents with complete document structure -✅ Exhaustive research coverage across all domain aspects -✅ Executive summary with key findings and strategic implications -✅ Strategic recommendations grounded in comprehensive research -✅ Complete source verification with citations -✅ Professional document structure and compelling narrative -✅ [C] complete option presented and handled correctly -✅ Domain research workflow completed with comprehensive document - -## FAILURE MODES: - -❌ Not producing compelling narrative introduction -❌ Missing comprehensive table of contents -❌ Incomplete research coverage across domain aspects -❌ Not providing executive summary with key findings -❌ Missing strategic recommendations based on research -❌ Relying solely on training data without web verification for current facts -❌ Producing document without professional structure -❌ Not presenting completion option for final document - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## COMPREHENSIVE DOCUMENT STANDARDS: - -This step ensures the final research document: - -- Serves as an authoritative reference on {{research_topic}} -- Provides compelling narrative and professional structure -- Includes comprehensive coverage with no gaps -- Maintains rigorous source verification standards -- Delivers strategic insights and actionable recommendations -- Meets professional research document quality standards - -## DOMAIN RESEARCH WORKFLOW COMPLETION: - -When 'C' is selected: - -- All domain research steps completed (1-5) -- Comprehensive domain research document generated -- Professional document structure with intro, TOC, and summary -- All sections appended with source citations -- Domain research workflow status updated to complete -- Final comprehensive research document delivered to user - -## FINAL DELIVERABLE: - -Complete authoritative research document on {{research_topic}} that: - -- Establishes professional credibility through comprehensive research -- Provides strategic insights for informed decision-making -- Serves as reference document for continued use -- Maintains highest research quality standards - -Congratulations on completing comprehensive domain research! 🎉 diff --git a/src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md b/src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md deleted file mode 100644 index ba7563b71..000000000 --- a/src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md +++ /dev/null @@ -1,182 +0,0 @@ -# Market Research Step 1: Market Research Initialization - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate research content in init step -- ✅ ALWAYS confirm understanding of user's research goals -- 📋 YOU ARE A MARKET RESEARCH FACILITATOR, not content generator -- 💬 FOCUS on clarifying scope and approach -- 🔍 NO WEB RESEARCH in init - that's for later steps -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Confirm research understanding before proceeding -- ⚠️ Present [C] continue option after scope clarification -- 💾 Write initial scope document immediately -- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from main workflow discovery are available -- Research type = "market" is already set -- **Research topic = "{{research_topic}}"** - discovered from initial discussion -- **Research goals = "{{research_goals}}"** - captured from initial discussion -- Focus on market research scope clarification -- Web search capabilities are enabled for later steps - -## YOUR TASK: - -Initialize market research by confirming understanding of {{research_topic}} and establishing clear research scope. - -## MARKET RESEARCH INITIALIZATION: - -### 1. Confirm Research Understanding - -**INITIALIZE - DO NOT RESEARCH YET** - -Start with research confirmation: -"I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}} - -**My Understanding of Your Research Needs:** - -- **Research Topic**: {{research_topic}} -- **Research Goals**: {{research_goals}} -- **Research Type**: Market Research -- **Approach**: Comprehensive market analysis with source verification - -**Market Research Areas We'll Cover:** - -- Market size, growth dynamics, and trends -- Customer insights and behavior analysis -- Competitive landscape and positioning -- Strategic recommendations and implementation guidance - -**Does this accurately capture what you're looking for?**" - -### 2. Refine Research Scope - -Gather any clarifications needed: - -#### Scope Clarification Questions: - -- "Are there specific customer segments or aspects of {{research_topic}} we should prioritize?" -- "Should we focus on specific geographic regions or global market?" -- "Is this for market entry, expansion, product development, or other business purpose?" -- "Any competitors or market segments you specifically want us to analyze?" - -### 3. Document Initial Scope - -**WRITE IMMEDIATELY TO DOCUMENT** - -Write initial research scope to document: - -```markdown -# Market Research: {{research_topic}} - -## Research Initialization - -### Research Understanding Confirmed - -**Topic**: {{research_topic}} -**Goals**: {{research_goals}} -**Research Type**: Market Research -**Date**: {{date}} - -### Research Scope - -**Market Analysis Focus Areas:** - -- Market size, growth projections, and dynamics -- Customer segments, behavior patterns, and insights -- Competitive landscape and positioning analysis -- Strategic recommendations and implementation guidance - -**Research Methodology:** - -- Current web data with source verification -- Multiple independent sources for critical claims -- Confidence level assessment for uncertain data -- Comprehensive coverage with no critical gaps - -### Next Steps - -**Research Workflow:** - -1. ✅ Initialization and scope setting (current step) -2. Customer Insights and Behavior Analysis -3. Competitive Landscape Analysis -4. Strategic Synthesis and Recommendations - -**Research Status**: Scope confirmed, ready to proceed with detailed market analysis -``` - -### 4. Present Confirmation and Continue Option - -Show initial scope document and present continue option: -"I've documented our understanding and initial scope for **{{research_topic}}** market research. - -**What I've established:** - -- Research topic and goals confirmed -- Market analysis focus areas defined -- Research methodology verification -- Clear workflow progression - -**Document Status:** Initial scope written to research file for your review - -**Ready to begin detailed market research?** -[C] Continue - Confirm scope and proceed to customer insights analysis -[Modify] Suggest changes to research scope before proceeding - -### 5. Handle User Response - -#### If 'C' (Continue): - -- Update frontmatter: `stepsCompleted: [1]` -- Add confirmation note to document: "Scope confirmed by user on {{date}}" -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md` - -#### If 'Modify': - -- Gather user changes to scope -- Update document with modifications -- Re-present updated scope for confirmation - -## SUCCESS METRICS: - -✅ Research topic and goals accurately understood -✅ Market research scope clearly defined -✅ Initial scope document written immediately -✅ User opportunity to review and modify scope -✅ [C] continue option presented and handled correctly -✅ Document properly updated with scope confirmation - -## FAILURE MODES: - -❌ Not confirming understanding of research topic and goals -❌ Generating research content instead of just scope clarification -❌ Not writing initial scope document to file -❌ Not providing opportunity for user to modify scope -❌ Proceeding to next step without user confirmation -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## INITIALIZATION PRINCIPLES: - -This step ensures: - -- Clear mutual understanding of research objectives -- Well-defined research scope and approach -- Immediate documentation for user review -- User control over research direction before detailed work begins - -## NEXT STEP: - -After user confirmation and scope finalization, load `{project-root}/_bmad/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md` to begin detailed market research with customer insights analysis. - -Remember: Init steps confirm understanding and scope, not generate research content! diff --git a/src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md b/src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md deleted file mode 100644 index e5315e34e..000000000 --- a/src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md +++ /dev/null @@ -1,237 +0,0 @@ -# Market Research Step 2: Customer Behavior and Segments - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A CUSTOMER BEHAVIOR ANALYST, not content generator -- 💬 FOCUS on customer behavior patterns and demographic analysis -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after customer behavior content generation -- 📝 WRITE CUSTOMER BEHAVIOR ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from step-01 are available -- Focus on customer behavior patterns and demographic analysis -- Web search capabilities with source verification are enabled -- Previous step confirmed research scope and goals -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion - -## YOUR TASK: - -Conduct customer behavior and segment analysis with emphasis on patterns and demographics. - -## CUSTOMER BEHAVIOR ANALYSIS SEQUENCE: - -### 1. Begin Customer Behavior Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer behavior areas simultaneously and thoroughly. - -Start with customer behavior research approach: -"Now I'll conduct **customer behavior analysis** for **{{research_topic}}** to understand customer patterns. - -**Customer Behavior Focus:** - -- Customer behavior patterns and preferences -- Demographic profiles and segmentation -- Psychographic characteristics and values -- Behavior drivers and influences -- Customer interaction patterns and engagement - -**Let me search for current customer behavior insights.**" - -### 2. Parallel Customer Behavior Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} customer behavior patterns" -Search the web: "{{research_topic}} customer demographics" -Search the web: "{{research_topic}} psychographic profiles" -Search the web: "{{research_topic}} customer behavior drivers" - -**Analysis approach:** - -- Look for customer behavior studies and research reports -- Search for demographic segmentation and analysis -- Research psychographic profiling and value systems -- Analyze behavior drivers and influencing factors -- Study customer interaction and engagement patterns - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate customer behavior findings: - -**Research Coverage:** - -- Customer behavior patterns and preferences -- Demographic profiles and segmentation -- Psychographic characteristics and values -- Behavior drivers and influences -- Customer interaction patterns and engagement - -**Cross-Behavior Analysis:** -[Identify patterns connecting demographics, psychographics, and behaviors] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Customer Behavior Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare customer behavior analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Customer Behavior and Segments - -### Customer Behavior Patterns - -[Customer behavior patterns analysis with source citations] -_Behavior Drivers: [Key motivations and patterns from web search]_ -_Interaction Preferences: [Customer engagement and interaction patterns]_ -_Decision Habits: [How customers typically make decisions]_ -_Source: [URL]_ - -### Demographic Segmentation - -[Demographic analysis with source citations] -_Age Demographics: [Age groups and preferences]_ -_Income Levels: [Income segments and purchasing behavior]_ -_Geographic Distribution: [Regional/city differences]_ -_Education Levels: [Education impact on behavior]_ -_Source: [URL]_ - -### Psychographic Profiles - -[Psychographic analysis with source citations] -_Values and Beliefs: [Core values driving customer behavior]_ -_Lifestyle Preferences: [Lifestyle choices and behaviors]_ -_Attitudes and Opinions: [Customer attitudes toward products/services]_ -_Personality Traits: [Personality influences on behavior]_ -_Source: [URL]_ - -### Customer Segment Profiles - -[Detailed customer segment profiles with source citations] -_Segment 1: [Detailed profile including demographics, psychographics, behavior]_ -_Segment 2: [Detailed profile including demographics, psychographics, behavior]_ -_Segment 3: [Detailed profile including demographics, psychographics, behavior]_ -_Source: [URL]_ - -### Behavior Drivers and Influences - -[Behavior drivers analysis with source citations] -_Emotional Drivers: [Emotional factors influencing behavior]_ -_Rational Drivers: [Logical decision factors]_ -_Social Influences: [Social and peer influences]_ -_Economic Influences: [Economic factors affecting behavior]_ -_Source: [URL]_ - -### Customer Interaction Patterns - -[Customer interaction analysis with source citations] -_Research and Discovery: [How customers find and research options]_ -_Purchase Decision Process: [Steps in purchase decision making]_ -_Post-Purchase Behavior: [After-purchase engagement patterns]_ -_Loyalty and Retention: [Factors driving customer loyalty]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **customer behavior analysis** for {{research_topic}}, focusing on customer patterns. - -**Key Customer Behavior Findings:** - -- Customer behavior patterns clearly identified with drivers -- Demographic segmentation thoroughly analyzed -- Psychographic profiles mapped and documented -- Customer interaction patterns captured -- Multiple sources verified for critical insights - -**Ready to proceed to customer pain points?** -[C] Continue - Save this to document and proceed to pain points analysis - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Customer behavior patterns identified with current citations -✅ Demographic segmentation thoroughly analyzed -✅ Psychographic profiles clearly documented -✅ Customer interaction patterns captured -✅ Multiple sources verified for critical insights -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (customer pain points) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts - -❌ Missing critical customer behavior patterns -❌ Incomplete demographic segmentation analysis -❌ Missing psychographic profile documentation -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to customer pain points analysis step -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## CUSTOMER BEHAVIOR RESEARCH PROTOCOLS: - -- Research customer behavior studies and market research -- Use demographic data from authoritative sources -- Research psychographic profiling and value systems -- Analyze customer interaction and engagement patterns -- Focus on current behavior data and trends -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## BEHAVIOR ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative customer research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable customer insights - -## NEXT STEP: - -After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md` to analyze customer pain points, challenges, and unmet needs for {{research_topic}}. - -Remember: Always write research content to document immediately and emphasize current customer data with rigorous source verification! diff --git a/src/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md b/src/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md deleted file mode 100644 index d740ae5e4..000000000 --- a/src/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md +++ /dev/null @@ -1,249 +0,0 @@ -# Market Research Step 3: Customer Pain Points and Needs - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A CUSTOMER NEEDS ANALYST, not content generator -- 💬 FOCUS on customer pain points, challenges, and unmet needs -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after pain points content generation -- 📝 WRITE CUSTOMER PAIN POINTS ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Customer behavior analysis completed in previous step -- Focus on customer pain points, challenges, and unmet needs -- Web search capabilities with source verification are enabled -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion - -## YOUR TASK: - -Conduct customer pain points and needs analysis with emphasis on challenges and frustrations. - -## CUSTOMER PAIN POINTS ANALYSIS SEQUENCE: - -### 1. Begin Customer Pain Points Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer pain point areas simultaneously and thoroughly. - -Start with customer pain points research approach: -"Now I'll conduct **customer pain points analysis** for **{{research_topic}}** to understand customer challenges. - -**Customer Pain Points Focus:** - -- Customer challenges and frustrations -- Unmet needs and unaddressed problems -- Barriers to adoption or usage -- Service and support pain points -- Customer satisfaction gaps - -**Let me search for current customer pain points insights.**" - -### 2. Parallel Pain Points Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} customer pain points challenges" -Search the web: "{{research_topic}} customer frustrations" -Search the web: "{{research_topic}} unmet customer needs" -Search the web: "{{research_topic}} customer barriers to adoption" - -**Analysis approach:** - -- Look for customer satisfaction surveys and reports -- Search for customer complaints and reviews -- Research customer support and service issues -- Analyze barriers to customer adoption -- Study unmet needs and market gaps - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate customer pain points findings: - -**Research Coverage:** - -- Customer challenges and frustrations -- Unmet needs and unaddressed problems -- Barriers to adoption or usage -- Service and support pain points - -**Cross-Pain Points Analysis:** -[Identify patterns connecting different types of pain points] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Customer Pain Points Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare customer pain points analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Customer Pain Points and Needs - -### Customer Challenges and Frustrations - -[Customer challenges analysis with source citations] -_Primary Frustrations: [Major customer frustrations identified]_ -_Usage Barriers: [Barriers preventing effective usage]_ -_Service Pain Points: [Customer service and support issues]_ -_Frequency Analysis: [How often these challenges occur]_ -_Source: [URL]_ - -### Unmet Customer Needs - -[Unmet needs analysis with source citations] -_Critical Unmet Needs: [Most important unaddressed needs]_ -_Solution Gaps: [Opportunities to address unmet needs]_ -_Market Gaps: [Market opportunities from unmet needs]_ -_Priority Analysis: [Which needs are most critical]_ -_Source: [URL]_ - -### Barriers to Adoption - -[Adoption barriers analysis with source citations] -_Price Barriers: [Cost-related barriers to adoption]_ -_Technical Barriers: [Complexity or technical barriers]_ -_Trust Barriers: [Trust and credibility issues]_ -_Convenience Barriers: [Ease of use or accessibility issues]_ -_Source: [URL]_ - -### Service and Support Pain Points - -[Service pain points analysis with source citations] -_Customer Service Issues: [Common customer service problems]_ -_Support Gaps: [Areas where customer support is lacking]_ -_Communication Issues: [Communication breakdowns and frustrations]_ -_Response Time Issues: [Slow response and resolution problems]_ -_Source: [URL]_ - -### Customer Satisfaction Gaps - -[Satisfaction gap analysis with source citations] -_Expectation Gaps: [Differences between expectations and reality]_ -_Quality Gaps: [Areas where quality expectations aren't met]_ -_Value Perception Gaps: [Perceived value vs actual value]_ -_Trust and Credibility Gaps: [Trust issues affecting satisfaction]_ -_Source: [URL]_ - -### Emotional Impact Assessment - -[Emotional impact analysis with source citations] -_Frustration Levels: [Customer frustration severity assessment]_ -_Loyalty Risks: [How pain points affect customer loyalty]_ -_Reputation Impact: [Impact on brand or product reputation]_ -_Customer Retention Risks: [Risk of customer loss from pain points]_ -_Source: [URL]_ - -### Pain Point Prioritization - -[Pain point prioritization with source citations] -_High Priority Pain Points: [Most critical pain points to address]_ -_Medium Priority Pain Points: [Important but less critical pain points]_ -_Low Priority Pain Points: [Minor pain points with lower impact]_ -_Opportunity Mapping: [Pain points with highest solution opportunity]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **customer pain points analysis** for {{research_topic}}, focusing on customer challenges. - -**Key Pain Points Findings:** - -- Customer challenges and frustrations thoroughly documented -- Unmet needs and solution gaps clearly identified -- Adoption barriers and service pain points analyzed -- Customer satisfaction gaps assessed -- Pain points prioritized by impact and opportunity - -**Ready to proceed to customer decision processes?** -[C] Continue - Save this to document and proceed to decision processes analysis - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Customer challenges and frustrations clearly documented -✅ Unmet needs and solution gaps identified -✅ Adoption barriers and service pain points analyzed -✅ Customer satisfaction gaps assessed -✅ Pain points prioritized by impact and opportunity -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (customer decisions) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts - -❌ Missing critical customer challenges or frustrations -❌ Not identifying unmet needs or solution gaps -❌ Incomplete adoption barriers analysis -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to customer decisions analysis step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## CUSTOMER PAIN POINTS RESEARCH PROTOCOLS: - -- Research customer satisfaction surveys and reviews -- Use customer feedback and complaint data -- Analyze customer support and service issues -- Study barriers to customer adoption -- Focus on current pain point data -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## PAIN POINTS ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative customer research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable pain point insights - -## NEXT STEP: - -After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md` to analyze customer decision processes, journey mapping, and decision factors for {{research_topic}}. - -Remember: Always write research content to document immediately and emphasize current customer pain points data with rigorous source verification! diff --git a/src/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md b/src/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md deleted file mode 100644 index 0f94f535b..000000000 --- a/src/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md +++ /dev/null @@ -1,259 +0,0 @@ -# Market Research Step 4: Customer Decisions and Journey - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A CUSTOMER DECISION ANALYST, not content generator -- 💬 FOCUS on customer decision processes and journey mapping -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after decision processes content generation -- 📝 WRITE CUSTOMER DECISIONS ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Customer behavior and pain points analysis completed in previous steps -- Focus on customer decision processes and journey mapping -- Web search capabilities with source verification are enabled -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion - -## YOUR TASK: - -Conduct customer decision processes and journey analysis with emphasis on decision factors and journey mapping. - -## CUSTOMER DECISIONS ANALYSIS SEQUENCE: - -### 1. Begin Customer Decisions Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer decision areas simultaneously and thoroughly. - -Start with customer decisions research approach: -"Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** to understand customer decision-making. - -**Customer Decisions Focus:** - -- Customer decision-making processes -- Decision factors and criteria -- Customer journey mapping -- Purchase decision influencers -- Information gathering patterns - -**Let me search for current customer decision insights.**" - -### 2. Parallel Decisions Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} customer decision process" -Search the web: "{{research_topic}} buying criteria factors" -Search the web: "{{research_topic}} customer journey mapping" -Search the web: "{{research_topic}} decision influencing factors" - -**Analysis approach:** - -- Look for customer decision research studies -- Search for buying criteria and factor analysis -- Research customer journey mapping methodologies -- Analyze decision influence factors and channels -- Study information gathering and evaluation patterns - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate customer decision findings: - -**Research Coverage:** - -- Customer decision-making processes -- Decision factors and criteria -- Customer journey mapping -- Decision influence factors - -**Cross-Decisions Analysis:** -[Identify patterns connecting decision factors and journey stages] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Customer Decisions Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare customer decisions analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Customer Decision Processes and Journey - -### Customer Decision-Making Processes - -[Decision processes analysis with source citations] -_Decision Stages: [Key stages in customer decision making]_ -_Decision Timelines: [Timeframes for different decisions]_ -_Complexity Levels: [Decision complexity assessment]_ -_Evaluation Methods: [How customers evaluate options]_ -_Source: [URL]_ - -### Decision Factors and Criteria - -[Decision factors analysis with source citations] -_Primary Decision Factors: [Most important factors in decisions]_ -_Secondary Decision Factors: [Supporting factors influencing decisions]_ -_Weighing Analysis: [How different factors are weighed]_ -_Evoluton Patterns: [How factors change over time]_ -_Source: [URL]_ - -### Customer Journey Mapping - -[Journey mapping analysis with source citations] -_Awareness Stage: [How customers become aware of {{research_topic}}]_ -_Consideration Stage: [Evaluation and comparison process]_ -_Decision Stage: [Final decision-making process]_ -_Purchase Stage: [Purchase execution and completion]_ -_Post-Purchase Stage: [Post-decision evaluation and behavior]_ -_Source: [URL]_ - -### Touchpoint Analysis - -[Touchpoint analysis with source citations] -_Digital Touchpoints: [Online and digital interaction points]_ -_Offline Touchpoints: [Physical and in-person interaction points]_ -_Information Sources: [Where customers get information]_ -_Influence Channels: [What influences customer decisions]_ -_Source: [URL]_ - -### Information Gathering Patterns - -[Information patterns analysis with source citations] -_Research Methods: [How customers research options]_ -_Information Sources Trusted: [Most trusted information sources]_ -_Research Duration: [Time spent gathering information]_ -_Evaluation Criteria: [How customers evaluate information]_ -_Source: [URL]_ - -### Decision Influencers - -[Decision influencer analysis with source citations] -_Peer Influence: [How friends and family influence decisions]_ -_Expert Influence: [How expert opinions affect decisions]_ -_Media Influence: [How media and marketing affect decisions]_ -_Social Proof Influence: [How reviews and testimonials affect decisions]_ -_Source: [URL]_ - -### Purchase Decision Factors - -[Purchase decision factors analysis with source citations] -_Immediate Purchase Drivers: [Factors triggering immediate purchase]_ -_Delayed Purchase Drivers: [Factors causing purchase delays]_ -_Brand Loyalty Factors: [Factors driving repeat purchases]_ -_Price Sensitivity: [How price affects purchase decisions]_ -_Source: [URL]_ - -### Customer Decision Optimizations - -[Decision optimization analysis with source citations] -_Friction Reduction: [Ways to make decisions easier]_ -_Trust Building: [Building customer trust in decisions]_ -_Conversion Optimization: [Optimizing decision-to-purchase rates]_ -_Loyalty Building: [Building long-term customer relationships]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **customer decision processes analysis** for {{research_topic}}, focusing on customer decision-making. - -**Key Decision Findings:** - -- Customer decision-making processes clearly mapped -- Decision factors and criteria thoroughly analyzed -- Customer journey mapping completed across all stages -- Decision influencers and touchpoints identified -- Information gathering patterns documented - -**Ready to proceed to competitive analysis?** -[C] Continue - Save this to document and proceed to competitive analysis - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Customer decision-making processes clearly mapped -✅ Decision factors and criteria thoroughly analyzed -✅ Customer journey mapping completed across all stages -✅ Decision influencers and touchpoints identified -✅ Information gathering patterns documented -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (competitive analysis) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts - -❌ Missing critical decision-making process stages -❌ Not identifying key decision factors -❌ Incomplete customer journey mapping -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to competitive analysis step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## CUSTOMER DECISIONS RESEARCH PROTOCOLS: - -- Research customer decision studies and psychology -- Use customer journey mapping methodologies -- Analyze buying criteria and decision factors -- Study decision influence and touchpoint analysis -- Focus on current decision data -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## DECISION ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative customer decision research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable decision insights - -## NEXT STEP: - -After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md` to analyze competitive landscape, market positioning, and competitive strategies for {{research_topic}}. - -Remember: Always write research content to document immediately and emphasize current customer decision data with rigorous source verification! diff --git a/src/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md b/src/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md deleted file mode 100644 index d7387a4fc..000000000 --- a/src/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md +++ /dev/null @@ -1,177 +0,0 @@ -# Market Research Step 5: Competitive Analysis - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A COMPETITIVE ANALYST, not content generator -- 💬 FOCUS on competitive landscape and market positioning -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] complete option after competitive analysis content generation -- 💾 ONLY save when user chooses C (Complete) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow -- 🚫 FORBIDDEN to complete workflow until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Focus on competitive landscape and market positioning analysis -- Web search capabilities with source verification are enabled -- May need to search for specific competitor information - -## YOUR TASK: - -Conduct comprehensive competitive analysis with emphasis on market positioning. - -## COMPETITIVE ANALYSIS SEQUENCE: - -### 1. Begin Competitive Analysis - -Start with competitive research approach: -"Now I'll conduct **competitive analysis** to understand the competitive landscape. - -**Competitive Analysis Focus:** - -- Key players and market share -- Competitive positioning strategies -- Strengths and weaknesses analysis -- Market differentiation opportunities -- Competitive threats and challenges - -**Let me search for current competitive information.**" - -### 2. Generate Competitive Analysis Content - -Prepare competitive analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Competitive Landscape - -### Key Market Players - -[Key players analysis with market share data] -_Source: [URL]_ - -### Market Share Analysis - -[Market share analysis with source citations] -_Source: [URL]_ - -### Competitive Positioning - -[Positioning analysis with source citations] -_Source: [URL]_ - -### Strengths and Weaknesses - -[SWOT analysis with source citations] -_Source: [URL]_ - -### Market Differentiation - -[Differentiation analysis with source citations] -_Source: [URL]_ - -### Competitive Threats - -[Threats analysis with source citations] -_Source: [URL]_ - -### Opportunities - -[Competitive opportunities analysis with source citations] -_Source: [URL]_ -``` - -### 3. Present Analysis and Complete Option - -Show the generated competitive analysis and present complete option: -"I've completed the **competitive analysis** for the competitive landscape. - -**Key Competitive Findings:** - -- Key market players and market share identified -- Competitive positioning strategies mapped -- Strengths and weaknesses thoroughly analyzed -- Market differentiation opportunities identified -- Competitive threats and challenges documented - -**Ready to complete the market research?** -[C] Complete Research - Save final document and conclude - -### 4. Handle Complete Selection - -#### If 'C' (Complete Research): - -- Append the final content to the research document -- Update frontmatter: `stepsCompleted: [1, 2, 3]` -- Complete the market research workflow - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the research document using the structure from step 2. - -## SUCCESS METRICS: - -✅ Key market players identified -✅ Market share analysis completed with source verification -✅ Competitive positioning strategies clearly mapped -✅ Strengths and weaknesses thoroughly analyzed -✅ Market differentiation opportunities identified -✅ [C] complete option presented and handled correctly -✅ Content properly appended to document when C selected -✅ Market research workflow completed successfully - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts - -❌ Missing key market players or market share data -❌ Incomplete competitive positioning analysis -❌ Not identifying market differentiation opportunities -❌ Not presenting completion option for research workflow -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## COMPETITIVE RESEARCH PROTOCOLS: - -- Search for industry reports and competitive intelligence -- Use competitor company websites and annual reports -- Research market research firm competitive analyses -- Note competitive advantages and disadvantages -- Search for recent market developments and disruptions - -## MARKET RESEARCH COMPLETION: - -When 'C' is selected: - -- All market research steps completed -- Comprehensive market research document generated -- All sections appended with source citations -- Market research workflow status updated -- Final recommendations provided to user - -## NEXT STEPS: - -Market research workflow complete. User may: - -- Use market research to inform product development strategies -- Conduct additional competitive research on specific companies -- Combine market research with other research types for comprehensive insights - -Congratulations on completing comprehensive market research! 🎉 diff --git a/src/bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md b/src/bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md deleted file mode 100644 index 0073b554e..000000000 --- a/src/bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md +++ /dev/null @@ -1,476 +0,0 @@ -# Market Research Step 6: Research Completion - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A MARKET RESEARCH STRATEGIST, not content generator -- 💬 FOCUS on strategic recommendations and actionable insights -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] complete option after completion content generation -- 💾 ONLY save when user chooses C (Complete) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow -- 🚫 FORBIDDEN to complete workflow until C is selected -- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - comprehensive market analysis -- **Research goals = "{{research_goals}}"** - achieved through exhaustive market research -- All market research sections have been completed (customer behavior, pain points, decisions, competitive analysis) -- Web search capabilities with source verification are enabled -- This is the final synthesis step producing the complete market research document - -## YOUR TASK: - -Produce a comprehensive, authoritative market research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive market research. - -## MARKET RESEARCH COMPLETION SEQUENCE: - -### 1. Begin Strategic Synthesis - -Start with strategic synthesis approach: -"Now I'll complete our market research with **strategic synthesis and recommendations** . - -**Strategic Synthesis Focus:** - -- Integrated insights from market, customer, and competitive analysis -- Strategic recommendations based on research findings -- Market entry or expansion strategies -- Risk assessment and mitigation approaches -- Actionable next steps and implementation guidance - -**Let me search for current strategic insights and best practices.**" - -### 2. Web Search for Market Entry Strategies - -Search for current market strategies: -Search the web: "market entry strategies best practices" - -**Strategy focus:** - -- Market entry timing and approaches -- Go-to-market strategies and frameworks -- Market positioning and differentiation tactics -- Customer acquisition and growth strategies - -### 3. Web Search for Risk Assessment - -Search for current risk approaches: -Search the web: "market research risk assessment frameworks" - -**Risk focus:** - -- Market risks and uncertainty management -- Competitive threats and mitigation strategies -- Regulatory and compliance risks -- Economic and market volatility considerations - -### 4. Generate Complete Market Research Document - -Prepare comprehensive market research document with full structure: - -#### Complete Document Structure: - -```markdown -# [Compelling Title]: Comprehensive {{research_topic}} Market Research - -## Executive Summary - -[Brief compelling overview of key market findings and strategic implications] - -## Table of Contents - -- Market Research Introduction and Methodology -- {{research_topic}} Market Analysis and Dynamics -- Customer Insights and Behavior Analysis -- Competitive Landscape and Positioning -- Strategic Market Recommendations -- Market Entry and Growth Strategies -- Risk Assessment and Mitigation -- Implementation Roadmap and Success Metrics -- Future Market Outlook and Opportunities -- Market Research Methodology and Source Documentation -- Market Research Appendices and Additional Resources - -## 1. Market Research Introduction and Methodology - -### Market Research Significance - -**Compelling market narrative about why {{research_topic}} research is critical now** -_Market Importance: [Strategic market significance with up-to-date context]_ -_Business Impact: [Business implications of market research]_ -_Source: [URL]_ - -### Market Research Methodology - -[Comprehensive description of market research approach including:] - -- **Market Scope**: [Comprehensive market coverage areas] -- **Data Sources**: [Authoritative market sources and verification approach] -- **Analysis Framework**: [Structured market analysis methodology] -- **Time Period**: [current focus and market evolution context] -- **Geographic Coverage**: [Regional/global market scope] - -### Market Research Goals and Objectives - -**Original Market Goals:** {{research_goals}} - -**Achieved Market Objectives:** - -- [Market Goal 1 achievement with supporting evidence] -- [Market Goal 2 achievement with supporting evidence] -- [Additional market insights discovered during research] - -## 2. {{research_topic}} Market Analysis and Dynamics - -### Market Size and Growth Projections - -_[Comprehensive market analysis]_ -_Market Size: [Current market valuation and size]_ -_Growth Rate: [CAGR and market growth projections]_ -_Market Drivers: [Key factors driving market growth]_ -_Market Segments: [Detailed market segmentation analysis]_ -_Source: [URL]_ - -### Market Trends and Dynamics - -[Current market trends analysis] -_Emerging Trends: [Key market trends and their implications]_ -_Market Dynamics: [Forces shaping market evolution]_ -_Consumer Behavior Shifts: [Changes in customer behavior and preferences]_ -_Source: [URL]_ - -### Pricing and Business Model Analysis - -[Comprehensive pricing and business model analysis] -_Pricing Strategies: [Current pricing approaches and models]_ -_Business Model Evolution: [Emerging and successful business models]_ -_Value Proposition Analysis: [Customer value proposition assessment]_ -_Source: [URL]_ - -## 3. Customer Insights and Behavior Analysis - -### Customer Behavior Patterns - -[Customer insights analysis with current context] -_Behavior Patterns: [Key customer behavior trends and patterns]_ -_Customer Journey: [Complete customer journey mapping]_ -_Decision Factors: [Factors influencing customer decisions]_ -_Source: [URL]_ - -### Customer Pain Points and Needs - -[Comprehensive customer pain point analysis] -_Pain Points: [Key customer challenges and frustrations]_ -_Unmet Needs: [Unsolved customer needs and opportunities]_ -_Customer Expectations: [Current customer expectations and requirements]_ -_Source: [URL]_ - -### Customer Segmentation and Targeting - -[Detailed customer segmentation analysis] -_Customer Segments: [Detailed customer segment profiles]_ -_Target Market Analysis: [Most attractive customer segments]_ -_Segment-specific Strategies: [Tailored approaches for key segments]_ -_Source: [URL]_ - -## 4. Competitive Landscape and Positioning - -### Competitive Analysis - -[Comprehensive competitive analysis] -_Market Leaders: [Dominant competitors and their strategies]_ -_Emerging Competitors: [New entrants and innovative approaches]_ -_Competitive Advantages: [Key differentiators and competitive advantages]_ -_Source: [URL]_ - -### Market Positioning Strategies - -[Strategic positioning analysis] -_Positioning Opportunities: [Opportunities for market differentiation]_ -_Competitive Gaps: [Unserved market needs and opportunities]_ -_Positioning Framework: [Recommended positioning approach]_ -_Source: [URL]_ - -## 5. Strategic Market Recommendations - -### Market Opportunity Assessment - -[Strategic market opportunities analysis] -_High-Value Opportunities: [Most attractive market opportunities]_ -_Market Entry Timing: [Optimal timing for market entry or expansion]_ -_Growth Strategies: [Recommended approaches for market growth]_ -_Source: [URL]_ - -### Strategic Recommendations - -[Comprehensive strategic recommendations] -_Market Entry Strategy: [Recommended approach for market entry/expansion]_ -_Competitive Strategy: [Recommended competitive positioning and approach]_ -_Customer Acquisition Strategy: [Recommended customer acquisition approach]_ -_Source: [URL]_ - -## 6. Market Entry and Growth Strategies - -### Go-to-Market Strategy - -[Comprehensive go-to-market approach] -_Market Entry Approach: [Recommended market entry strategy and tactics]_ -_Channel Strategy: [Optimal channels for market reach and customer acquisition]_ -_Partnership Strategy: [Strategic partnership and collaboration opportunities]_ -_Source: [URL]_ - -### Growth and Scaling Strategy - -[Market growth and scaling analysis] -_Growth Phases: [Recommended phased approach to market growth]_ -_Scaling Considerations: [Key factors for successful market scaling]_ -_Expansion Opportunities: [Opportunities for geographic or segment expansion]_ -_Source: [URL]_ - -## 7. Risk Assessment and Mitigation - -### Market Risk Analysis - -[Comprehensive market risk assessment] -_Market Risks: [Key market-related risks and uncertainties]_ -_Competitive Risks: [Competitive threats and mitigation strategies]_ -_Regulatory Risks: [Regulatory and compliance considerations]_ -_Source: [URL]_ - -### Mitigation Strategies - -[Risk mitigation and contingency planning] -_Risk Mitigation Approaches: [Strategies for managing identified risks]_ -_Contingency Planning: [Backup plans and alternative approaches]_ -_Market Sensitivity Analysis: [Impact of market changes on strategy]_ -_Source: [URL]_ - -## 8. Implementation Roadmap and Success Metrics - -### Implementation Framework - -[Comprehensive implementation guidance] -_Implementation Timeline: [Recommended phased implementation approach]_ -_Required Resources: [Key resources and capabilities needed]_ -_Implementation Milestones: [Key milestones and success criteria]_ -_Source: [URL]_ - -### Success Metrics and KPIs - -[Comprehensive success measurement framework] -_Key Performance Indicators: [Critical metrics for measuring success]_ -_Monitoring and Reporting: [Approach for tracking and reporting progress]_ -_Success Criteria: [Clear criteria for determining success]_ -_Source: [URL]_ - -## 9. Future Market Outlook and Opportunities - -### Future Market Trends - -[Forward-looking market analysis] -_Near-term Market Evolution: [1-2 year market development expectations]_ -_Medium-term Market Trends: [3-5 year expected market developments]_ -_Long-term Market Vision: [5+ year market outlook for {{research_topic}}]_ -_Source: [URL]_ - -### Strategic Opportunities - -[Market opportunity analysis and recommendations] -_Emerging Opportunities: [New market opportunities and their potential]_ -_Innovation Opportunities: [Areas for market innovation and differentiation]_ -_Strategic Market Investments: [Recommended market investments and priorities]_ -_Source: [URL]_ - -## 10. Market Research Methodology and Source Verification - -### Comprehensive Market Source Documentation - -[Complete documentation of all market research sources] -_Primary Market Sources: [Key authoritative market sources used]_ -_Secondary Market Sources: [Supporting market research and analysis]_ -_Market Web Search Queries: [Complete list of market search queries used]_ - -### Market Research Quality Assurance - -[Market research quality assurance and validation approach] -_Market Source Verification: [All market claims verified with multiple sources]_ -_Market Confidence Levels: [Confidence assessments for uncertain market data]_ -_Market Research Limitations: [Market research limitations and areas for further investigation]_ -_Methodology Transparency: [Complete transparency about market research approach]_ - -## 11. Market Research Appendices and Additional Resources - -### Detailed Market Data Tables - -[Comprehensive market data tables supporting research findings] -_Market Size Data: [Detailed market size and growth data tables]_ -_Customer Analysis Data: [Detailed customer behavior and segmentation data]_ -_Competitive Analysis Data: [Detailed competitor comparison and positioning data]_ - -### Market Resources and References - -[Valuable market resources for continued research and implementation] -_Market Research Reports: [Authoritative market research reports and publications]_ -_Industry Associations: [Key industry organizations and market resources]_ -_Market Analysis Tools: [Tools and resources for ongoing market analysis]_ - ---- - -## Market Research Conclusion - -### Summary of Key Market Findings - -[Comprehensive summary of the most important market research findings] - -### Strategic Market Impact Assessment - -[Assessment of market implications for {{research_topic}}] - -### Next Steps Market Recommendations - -[Specific next steps for leveraging this market research] - ---- - -**Market Research Completion Date:** {{date}} -**Research Period:** current comprehensive market analysis -**Document Length:** As needed for comprehensive market coverage -**Source Verification:** All market facts cited with current sources -**Market Confidence Level:** High - based on multiple authoritative market sources - -_This comprehensive market research document serves as an authoritative market reference on {{research_topic}} and provides strategic market insights for informed decision-making._ -``` - -### 5. Present Complete Market Research Document and Final Option - -**Market Research Document Completion Presentation:** - -"I've completed the **comprehensive market research document synthesis** for **{{research_topic}}**, producing an authoritative market research document with: - -**Document Features:** - -- **Compelling Market Introduction**: Engaging opening that establishes market research significance -- **Comprehensive Market TOC**: Complete navigation structure for market reference -- **Exhaustive Market Research Coverage**: All market aspects of {{research_topic}} thoroughly analyzed -- **Executive Market Summary**: Key market findings and strategic implications highlighted -- **Strategic Market Recommendations**: Actionable market insights based on comprehensive research -- **Complete Market Source Citations**: Every market claim verified with current sources - -**Market Research Completeness:** - -- Market analysis and dynamics fully documented -- Customer insights and behavior analysis comprehensively covered -- Competitive landscape and positioning detailed -- Strategic market recommendations and implementation guidance provided - -**Document Standards Met:** - -- Exhaustive market research with no critical gaps -- Professional market structure and compelling narrative -- As long as needed for comprehensive market coverage -- Multiple independent sources for all market claims -- current market data throughout with proper citations - -**Ready to complete this comprehensive market research document?** -[C] Complete Research - Save final comprehensive market research document - -### 6. Handle Complete Selection - -#### If 'C' (Complete Research): - -- **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section -- Append the final content to the research document -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]` -- Complete the market research workflow - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the research document using the structure from step 4. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document. - -## SUCCESS METRICS: - -✅ Compelling market introduction with research significance -✅ Comprehensive market table of contents with complete document structure -✅ Exhaustive market research coverage across all market aspects -✅ Executive market summary with key findings and strategic implications -✅ Strategic market recommendations grounded in comprehensive research -✅ Complete market source verification with current citations -✅ Professional market document structure and compelling narrative -✅ [C] complete option presented and handled correctly -✅ Market research workflow completed with comprehensive document - -## FAILURE MODES: - -❌ Not producing compelling market introduction -❌ Missing comprehensive market table of contents -❌ Incomplete market research coverage across market aspects -❌ Not providing executive market summary with key findings -❌ Missing strategic market recommendations based on research -❌ Relying solely on training data without web verification for current facts -❌ Producing market document without professional structure -❌ Not presenting completion option for final market document - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## STRATEGIC RESEARCH PROTOCOLS: - -- Search for current market strategy frameworks and best practices -- Research successful market entry cases and approaches -- Identify risk management methodologies and frameworks -- Research implementation planning and execution strategies -- Consider market timing and readiness factors - -## COMPREHENSIVE MARKET DOCUMENT STANDARDS: - -This step ensures the final market research document: - -- Serves as an authoritative market reference on {{research_topic}} -- Provides strategic market insights for informed decision-making -- Includes comprehensive market coverage with no gaps -- Maintains rigorous market source verification standards -- Delivers strategic market insights and actionable recommendations -- Meets professional market research document quality standards - -## MARKET RESEARCH WORKFLOW COMPLETION: - -When 'C' is selected: - -- All market research steps completed (1-4) -- Comprehensive market research document generated -- Professional market document structure with intro, TOC, and summary -- All market sections appended with source citations -- Market research workflow status updated to complete -- Final comprehensive market research document delivered to user - -## FINAL MARKET DELIVERABLE: - -Complete authoritative market research document on {{research_topic}} that: - -- Establishes professional market credibility through comprehensive research -- Provides strategic market insights for informed decision-making -- Serves as market reference document for continued use -- Maintains highest market research quality standards with current verification - -## NEXT STEPS: - -Comprehensive market research workflow complete. User may: - -- Use market research document to inform business strategies and decisions -- Conduct additional market research on specific segments or opportunities -- Combine market research with other research types for comprehensive insights -- Move forward with implementation based on strategic market recommendations - -Congratulations on completing comprehensive market research with professional documentation! 🎉 diff --git a/src/bmm/workflows/1-analysis/research/research.template.md b/src/bmm/workflows/1-analysis/research/research.template.md deleted file mode 100644 index 1d9952470..000000000 --- a/src/bmm/workflows/1-analysis/research/research.template.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -stepsCompleted: [] -inputDocuments: [] -workflowType: 'research' -lastStep: 1 -research_type: '{{research_type}}' -research_topic: '{{research_topic}}' -research_goals: '{{research_goals}}' -user_name: '{{user_name}}' -date: '{{date}}' -web_research_enabled: true -source_verification: true ---- - -# Research Report: {{research_type}} - -**Date:** {{date}} -**Author:** {{user_name}} -**Research Type:** {{research_type}} - ---- - -## Research Overview - -[Research overview and methodology will be appended here] - ---- - - diff --git a/src/bmm/workflows/1-analysis/research/technical-steps/step-01-init.md b/src/bmm/workflows/1-analysis/research/technical-steps/step-01-init.md deleted file mode 100644 index 1b0980b3f..000000000 --- a/src/bmm/workflows/1-analysis/research/technical-steps/step-01-init.md +++ /dev/null @@ -1,137 +0,0 @@ -# Technical Research Step 1: Technical Research Scope Confirmation - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user confirmation - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ FOCUS EXCLUSIVELY on confirming technical research scope and approach -- 📋 YOU ARE A TECHNICAL RESEARCH PLANNER, not content generator -- 💬 ACKNOWLEDGE and CONFIRM understanding of technical research goals -- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present [C] continue option after scope confirmation -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Research type = "technical" is already set -- **Research topic = "{{research_topic}}"** - discovered from initial discussion -- **Research goals = "{{research_goals}}"** - captured from initial discussion -- Focus on technical architecture and implementation research -- Web search is required to verify and supplement your knowledge with current facts - -## YOUR TASK: - -Confirm technical research scope and approach for **{{research_topic}}** with the user's goals in mind. - -## TECHNICAL SCOPE CONFIRMATION: - -### 1. Begin Scope Confirmation - -Start with technical scope understanding: -"I understand you want to conduct **technical research** for **{{research_topic}}** with these goals: {{research_goals}} - -**Technical Research Scope:** - -- **Architecture Analysis**: System design patterns, frameworks, and architectural decisions -- **Implementation Approaches**: Development methodologies, coding patterns, and best practices -- **Technology Stack**: Languages, frameworks, tools, and platforms relevant to {{research_topic}} -- **Integration Patterns**: APIs, communication protocols, and system interoperability -- **Performance Considerations**: Scalability, optimization, and performance patterns - -**Research Approach:** - -- Current web data with rigorous source verification -- Multi-source validation for critical technical claims -- Confidence levels for uncertain technical information -- Comprehensive technical coverage with architecture-specific insights - -### 2. Scope Confirmation - -Present clear scope confirmation: -"**Technical Research Scope Confirmation:** - -For **{{research_topic}}**, I will research: - -✅ **Architecture Analysis** - design patterns, frameworks, system architecture -✅ **Implementation Approaches** - development methodologies, coding patterns -✅ **Technology Stack** - languages, frameworks, tools, platforms -✅ **Integration Patterns** - APIs, protocols, interoperability -✅ **Performance Considerations** - scalability, optimization, patterns - -**All claims verified against current public sources.** - -**Does this technical research scope and approach align with your goals?** -[C] Continue - Begin technical research with this scope - -### 3. Handle Continue Selection - -#### If 'C' (Continue): - -- Document scope confirmation in research file -- Update frontmatter: `stepsCompleted: [1]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append scope confirmation: - -```markdown -## Technical Research Scope Confirmation - -**Research Topic:** {{research_topic}} -**Research Goals:** {{research_goals}} - -**Technical Research Scope:** - -- Architecture Analysis - design patterns, frameworks, system architecture -- Implementation Approaches - development methodologies, coding patterns -- Technology Stack - languages, frameworks, tools, platforms -- Integration Patterns - APIs, protocols, interoperability -- Performance Considerations - scalability, optimization, patterns - -**Research Methodology:** - -- Current web data with rigorous source verification -- Multi-source validation for critical technical claims -- Confidence level framework for uncertain information -- Comprehensive technical coverage with architecture-specific insights - -**Scope Confirmed:** {{date}} -``` - -## SUCCESS METRICS: - -✅ Technical research scope clearly confirmed with user -✅ All technical analysis areas identified and explained -✅ Research methodology emphasized -✅ [C] continue option presented and handled correctly -✅ Scope confirmation documented when user proceeds -✅ Proper routing to next technical research step - -## FAILURE MODES: - -❌ Not clearly confirming technical research scope with user -❌ Missing critical technical analysis areas -❌ Not explaining that web search is required for current facts -❌ Not presenting [C] continue option -❌ Proceeding without user scope confirmation -❌ Not routing to next technical research step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md` to begin technology stack analysis. - -Remember: This is SCOPE CONFIRMATION ONLY - no actual technical research yet, just confirming the research approach and scope! diff --git a/src/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md b/src/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md deleted file mode 100644 index 406a273ca..000000000 --- a/src/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md +++ /dev/null @@ -1,239 +0,0 @@ -# Technical Research Step 2: Technology Stack Analysis - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A TECHNOLOGY STACK ANALYST, not content generator -- 💬 FOCUS on languages, frameworks, tools, and platforms -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after technology stack content generation -- 📝 WRITE TECHNOLOGY STACK ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from step-01 are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on languages, frameworks, tools, and platforms -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct technology stack analysis focusing on languages, frameworks, tools, and platforms. Search the web to verify and supplement current facts. - -## TECHNOLOGY STACK ANALYSIS SEQUENCE: - -### 1. Begin Technology Stack Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different technology stack areas simultaneously and thoroughly. - -Start with technology stack research approach: -"Now I'll conduct **technology stack analysis** for **{{research_topic}}** to understand the technology landscape. - -**Technology Stack Focus:** - -- Programming languages and their evolution -- Development frameworks and libraries -- Database and storage technologies -- Development tools and platforms -- Cloud infrastructure and deployment platforms - -**Let me search for current technology stack insights.**" - -### 2. Parallel Technology Stack Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} programming languages frameworks" -Search the web: "{{research_topic}} development tools platforms" -Search the web: "{{research_topic}} database storage technologies" -Search the web: "{{research_topic}} cloud infrastructure platforms" - -**Analysis approach:** - -- Look for recent technology trend reports and developer surveys -- Search for technology documentation and best practices -- Research open-source projects and their technology choices -- Analyze technology adoption patterns and migration trends -- Study platform and tool evolution in the domain - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate technology stack findings: - -**Research Coverage:** - -- Programming languages and frameworks analysis -- Development tools and platforms evaluation -- Database and storage technologies assessment -- Cloud infrastructure and deployment platform analysis - -**Cross-Technology Analysis:** -[Identify patterns connecting language choices, frameworks, and platform decisions] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Technology Stack Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare technology stack analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Technology Stack Analysis - -### Programming Languages - -[Programming languages analysis with source citations] -_Popular Languages: [Most widely used languages for {{research_topic}}]_ -_Emerging Languages: [Growing languages gaining adoption]_ -_Language Evolution: [How language preferences are changing]_ -_Performance Characteristics: [Language performance and suitability]_ -_Source: [URL]_ - -### Development Frameworks and Libraries - -[Frameworks analysis with source citations] -_Major Frameworks: [Dominant frameworks and their use cases]_ -_Micro-frameworks: [Lightweight options and specialized libraries]_ -_Evolution Trends: [How frameworks are evolving and changing]_ -_Ecosystem Maturity: [Library availability and community support]_ -_Source: [URL]_ - -### Database and Storage Technologies - -[Database analysis with source citations] -_Relational Databases: [Traditional SQL databases and their evolution]_ -_NoSQL Databases: [Document, key-value, graph, and other NoSQL options]_ -_In-Memory Databases: [Redis, Memcached, and performance-focused solutions]_ -_Data Warehousing: [Analytics and big data storage solutions]_ -_Source: [URL]_ - -### Development Tools and Platforms - -[Tools and platforms analysis with source citations] -_IDE and Editors: [Development environments and their evolution]_ -_Version Control: [Git and related development tools]_ -_Build Systems: [Compilation, packaging, and automation tools]_ -_Testing Frameworks: [Unit testing, integration testing, and QA tools]_ -_Source: [URL]_ - -### Cloud Infrastructure and Deployment - -[Cloud platforms analysis with source citations] -_Major Cloud Providers: [AWS, Azure, GCP and their services]_ -_Container Technologies: [Docker, Kubernetes, and orchestration]_ -_Serverless Platforms: [FaaS and event-driven computing]_ -_CDN and Edge Computing: [Content delivery and distributed computing]_ -_Source: [URL]_ - -### Technology Adoption Trends - -[Adoption trends analysis with source citations] -_Migration Patterns: [How technology choices are evolving]_ -_Emerging Technologies: [New technologies gaining traction]_ -_Legacy Technology: [Older technologies being phased out]_ -_Community Trends: [Developer preferences and open-source adoption]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **technology stack analysis** of the technology landscape for {{research_topic}}. - -**Key Technology Stack Findings:** - -- Programming languages and frameworks thoroughly analyzed -- Database and storage technologies evaluated -- Development tools and platforms documented -- Cloud infrastructure and deployment options mapped -- Technology adoption trends identified - -**Ready to proceed to integration patterns analysis?** -[C] Continue - Save this to document and proceed to integration patterns - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ Programming languages and frameworks thoroughly analyzed -✅ Database and storage technologies evaluated -✅ Development tools and platforms documented -✅ Cloud infrastructure and deployment options mapped -✅ Technology adoption trends identified -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (integration patterns) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts - -❌ Missing critical programming languages or frameworks -❌ Incomplete database and storage technology analysis -❌ Not identifying development tools and platforms -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to integration patterns step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## TECHNOLOGY STACK RESEARCH PROTOCOLS: - -- Research technology trend reports and developer surveys -- Use technology documentation and best practices guides -- Analyze open-source projects and their technology choices -- Study technology adoption patterns and migration trends -- Focus on current technology data -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## TECHNOLOGY STACK ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative technology research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable technology insights - -## NEXT STEP: - -After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md` to analyze APIs, communication protocols, and system interoperability for {{research_topic}}. - -Remember: Always write research content to document immediately and emphasize current technology data with rigorous source verification! diff --git a/src/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md b/src/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md deleted file mode 100644 index 4d4f6243d..000000000 --- a/src/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md +++ /dev/null @@ -1,248 +0,0 @@ -# Technical Research Step 3: Integration Patterns - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE AN INTEGRATION ANALYST, not content generator -- 💬 FOCUS on APIs, protocols, and system interoperability -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after integration patterns content generation -- 📝 WRITE INTEGRATION PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on APIs, protocols, and system interoperability -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct integration patterns analysis focusing on APIs, communication protocols, and system interoperability. Search the web to verify and supplement current facts. - -## INTEGRATION PATTERNS ANALYSIS SEQUENCE: - -### 1. Begin Integration Patterns Analysis - -**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different integration areas simultaneously and thoroughly. - -Start with integration patterns research approach: -"Now I'll conduct **integration patterns analysis** for **{{research_topic}}** to understand system integration approaches. - -**Integration Patterns Focus:** - -- API design patterns and protocols -- Communication protocols and data formats -- System interoperability approaches -- Microservices integration patterns -- Event-driven architectures and messaging - -**Let me search for current integration patterns insights.**" - -### 2. Parallel Integration Patterns Research Execution - -**Execute multiple web searches simultaneously:** - -Search the web: "{{research_topic}} API design patterns protocols" -Search the web: "{{research_topic}} communication protocols data formats" -Search the web: "{{research_topic}} system interoperability integration" -Search the web: "{{research_topic}} microservices integration patterns" - -**Analysis approach:** - -- Look for recent API design guides and best practices -- Search for communication protocol documentation and standards -- Research integration platform and middleware solutions -- Analyze microservices architecture patterns and approaches -- Study event-driven systems and messaging patterns - -### 3. Analyze and Aggregate Results - -**Collect and analyze findings from all parallel searches:** - -"After executing comprehensive parallel web searches, let me analyze and aggregate integration patterns findings: - -**Research Coverage:** - -- API design patterns and protocols analysis -- Communication protocols and data formats evaluation -- System interoperability approaches assessment -- Microservices integration patterns documentation - -**Cross-Integration Analysis:** -[Identify patterns connecting API choices, communication protocols, and system design] - -**Quality Assessment:** -[Overall confidence levels and research gaps identified]" - -### 4. Generate Integration Patterns Content - -**WRITE IMMEDIATELY TO DOCUMENT** - -Prepare integration patterns analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Integration Patterns Analysis - -### API Design Patterns - -[API design patterns analysis with source citations] -_RESTful APIs: [REST principles and best practices for {{research_topic}}]_ -_GraphQL APIs: [GraphQL adoption and implementation patterns]_ -_RPC and gRPC: [High-performance API communication patterns]_ -_Webhook Patterns: [Event-driven API integration approaches]_ -_Source: [URL]_ - -### Communication Protocols - -[Communication protocols analysis with source citations] -_HTTP/HTTPS Protocols: [Web-based communication patterns and evolution]_ -_WebSocket Protocols: [Real-time communication and persistent connections]_ -_Message Queue Protocols: [AMQP, MQTT, and messaging patterns]_ -_grpc and Protocol Buffers: [High-performance binary communication protocols]_ -_Source: [URL]_ - -### Data Formats and Standards - -[Data formats analysis with source citations] -_JSON and XML: [Structured data exchange formats and their evolution]_ -_Protobuf and MessagePack: [Efficient binary serialization formats]_ -_CSV and Flat Files: [Legacy data integration and bulk transfer patterns]_ -_Custom Data Formats: [Domain-specific data exchange standards]_ -_Source: [URL]_ - -### System Interoperability Approaches - -[Interoperability analysis with source citations] -_Point-to-Point Integration: [Direct system-to-system communication patterns]_ -_API Gateway Patterns: [Centralized API management and routing]_ -_Service Mesh: [Service-to-service communication and observability]_ -_Enterprise Service Bus: [Traditional enterprise integration patterns]_ -_Source: [URL]_ - -### Microservices Integration Patterns - -[Microservices integration analysis with source citations] -_API Gateway Pattern: [External API management and routing]_ -_Service Discovery: [Dynamic service registration and discovery]_ -_Circuit Breaker Pattern: [Fault tolerance and resilience patterns]_ -_Saga Pattern: [Distributed transaction management]_ -_Source: [URL]_ - -### Event-Driven Integration - -[Event-driven analysis with source citations] -_Publish-Subscribe Patterns: [Event broadcasting and subscription models]_ -_Event Sourcing: [Event-based state management and persistence]_ -_Message Broker Patterns: [RabbitMQ, Kafka, and message routing]_ -_CQRS Patterns: [Command Query Responsibility Segregation]_ -_Source: [URL]_ - -### Integration Security Patterns - -[Security patterns analysis with source citations] -_OAuth 2.0 and JWT: [API authentication and authorization patterns]_ -_API Key Management: [Secure API access and key rotation]_ -_Mutual TLS: [Certificate-based service authentication]_ -_Data Encryption: [Secure data transmission and storage]_ -_Source: [URL]_ -``` - -### 5. Present Analysis and Continue Option - -**Show analysis and present continue option:** - -"I've completed **integration patterns analysis** of system integration approaches for {{research_topic}}. - -**Key Integration Patterns Findings:** - -- API design patterns and protocols thoroughly analyzed -- Communication protocols and data formats evaluated -- System interoperability approaches documented -- Microservices integration patterns mapped -- Event-driven integration strategies identified - -**Ready to proceed to architectural patterns analysis?** -[C] Continue - Save this to document and proceed to architectural patterns - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- **CONTENT ALREADY WRITTEN TO DOCUMENT** -- Update frontmatter: `stepsCompleted: [1, 2, 3]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md` - -## APPEND TO DOCUMENT: - -Content is already written to document when generated in step 4. No additional append needed. - -## SUCCESS METRICS: - -✅ API design patterns and protocols thoroughly analyzed -✅ Communication protocols and data formats evaluated -✅ System interoperability approaches documented -✅ Microservices integration patterns mapped -✅ Event-driven integration strategies identified -✅ Content written immediately to document -✅ [C] continue option presented and handled correctly -✅ Proper routing to next step (architectural patterns) -✅ Research goals alignment maintained - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts - -❌ Missing critical API design patterns or protocols -❌ Incomplete communication protocols analysis -❌ Not identifying system interoperability approaches -❌ Not writing content immediately to document -❌ Not presenting [C] continue option after content generation -❌ Not routing to architectural patterns step - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## INTEGRATION PATTERNS RESEARCH PROTOCOLS: - -- Research API design guides and best practices documentation -- Use communication protocol specifications and standards -- Analyze integration platform and middleware solutions -- Study microservices architecture patterns and case studies -- Focus on current integration data -- Present conflicting information when sources disagree -- Apply confidence levels appropriately - -## INTEGRATION PATTERNS ANALYSIS STANDARDS: - -- Always cite URLs for web search results -- Use authoritative integration research sources -- Note data currency and potential limitations -- Present multiple perspectives when sources conflict -- Apply confidence levels to uncertain data -- Focus on actionable integration insights - -## NEXT STEP: - -After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md` to analyze architectural patterns, design decisions, and system structures for {{research_topic}}. - -Remember: Always write research content to document immediately and emphasize current integration data with rigorous source verification! diff --git a/src/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md b/src/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md deleted file mode 100644 index abb01037a..000000000 --- a/src/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md +++ /dev/null @@ -1,202 +0,0 @@ -# Technical Research Step 4: Architectural Patterns - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A SYSTEMS ARCHITECT, not content generator -- 💬 FOCUS on architectural patterns and design decisions -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] continue option after architectural patterns content generation -- 📝 WRITE ARCHITECTURAL PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY -- 💾 ONLY proceed when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - established from initial discussion -- **Research goals = "{{research_goals}}"** - established from initial discussion -- Focus on architectural patterns and design decisions -- Web search capabilities with source verification are enabled - -## YOUR TASK: - -Conduct comprehensive architectural patterns analysis with emphasis on design decisions and implementation approaches for {{research_topic}}. - -## ARCHITECTURAL PATTERNS SEQUENCE: - -### 1. Begin Architectural Patterns Analysis - -Start with architectural research approach: -"Now I'll focus on **architectural patterns and design decisions** for effective architecture approaches for [technology/domain]. - -**Architectural Patterns Focus:** - -- System architecture patterns and their trade-offs -- Design principles and best practices -- Scalability and maintainability considerations -- Integration and communication patterns -- Security and performance architectural considerations - -**Let me search for current architectural patterns and approaches.**" - -### 2. Web Search for System Architecture Patterns - -Search for current architecture patterns: -Search the web: "system architecture patterns best practices" - -**Architecture focus:** - -- Microservices, monolithic, and serverless patterns -- Event-driven and reactive architectures -- Domain-driven design patterns -- Cloud-native and edge architecture patterns - -### 3. Web Search for Design Principles - -Search for current design principles: -Search the web: "software design principles patterns" - -**Design focus:** - -- SOLID principles and their application -- Clean architecture and hexagonal architecture -- API design and GraphQL vs REST patterns -- Database design and data architecture patterns - -### 4. Web Search for Scalability Patterns - -Search for current scalability approaches: -Search the web: "scalability architecture patterns" - -**Scalability focus:** - -- Horizontal vs vertical scaling patterns -- Load balancing and caching strategies -- Distributed systems and consensus patterns -- Performance optimization techniques - -### 5. Generate Architectural Patterns Content - -Prepare architectural analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Architectural Patterns and Design - -### System Architecture Patterns - -[System architecture patterns analysis with source citations] -_Source: [URL]_ - -### Design Principles and Best Practices - -[Design principles analysis with source citations] -_Source: [URL]_ - -### Scalability and Performance Patterns - -[Scalability patterns analysis with source citations] -_Source: [URL]_ - -### Integration and Communication Patterns - -[Integration patterns analysis with source citations] -_Source: [URL]_ - -### Security Architecture Patterns - -[Security patterns analysis with source citations] -_Source: [URL]_ - -### Data Architecture Patterns - -[Data architecture analysis with source citations] -_Source: [URL]_ - -### Deployment and Operations Architecture - -[Deployment architecture analysis with source citations] -_Source: [URL]_ -``` - -### 6. Present Analysis and Continue Option - -Show the generated architectural patterns and present continue option: -"I've completed the **architectural patterns analysis** for effective architecture approaches. - -**Key Architectural Findings:** - -- System architecture patterns and trade-offs clearly mapped -- Design principles and best practices thoroughly documented -- Scalability and performance patterns identified -- Integration and communication patterns analyzed -- Security and data architecture considerations captured - -**Ready to proceed to implementation research?** -[C] Continue - Save this to the document and move to implementation research - -### 7. Handle Continue Selection - -#### If 'C' (Continue): - -- Append the final content to the research document -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the research document using the structure from step 5. - -## SUCCESS METRICS: - -✅ System architecture patterns identified with current citations -✅ Design principles clearly documented and analyzed -✅ Scalability and performance patterns thoroughly mapped -✅ Integration and communication patterns captured -✅ Security and data architecture considerations analyzed -✅ [C] continue option presented and handled correctly -✅ Content properly appended to document when C selected -✅ Proper routing to implementation research step - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts - -❌ Missing critical system architecture patterns -❌ Not analyzing design trade-offs and considerations -❌ Incomplete scalability or performance patterns analysis -❌ Not presenting [C] continue option after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## ARCHITECTURAL RESEARCH PROTOCOLS: - -- Search for architecture documentation and pattern catalogs -- Use architectural conference proceedings and case studies -- Research successful system architectures and their evolution -- Note architectural decision records (ADRs) and rationales -- Research architecture assessment and evaluation frameworks - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md` to focus on implementation approaches and technology adoption. - -Remember: Always emphasize current architectural data and rigorous source verification! diff --git a/src/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md b/src/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md deleted file mode 100644 index 9e5be7bbb..000000000 --- a/src/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md +++ /dev/null @@ -1,233 +0,0 @@ -# Technical Research Step 5: Implementation Research - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE AN IMPLEMENTATION ENGINEER, not content generator -- 💬 FOCUS on implementation approaches and technology adoption -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] complete option after implementation research content generation -- 💾 ONLY save when user chooses C (Complete) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow -- 🚫 FORBIDDEN to complete workflow until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Focus on implementation approaches and technology adoption strategies -- Web search capabilities with source verification are enabled -- This step prepares for the final synthesis step - -## YOUR TASK: - -Conduct comprehensive implementation research with emphasis on practical implementation approaches and technology adoption. - -## IMPLEMENTATION RESEARCH SEQUENCE: - -### 1. Begin Implementation Research - -Start with implementation research approach: -"Now I'll complete our technical research with **implementation approaches and technology adoption** analysis. - -**Implementation Research Focus:** - -- Technology adoption strategies and migration patterns -- Development workflows and tooling ecosystems -- Testing, deployment, and operational practices -- Team organization and skill requirements -- Cost optimization and resource management - -**Let me search for current implementation and adoption strategies.**" - -### 2. Web Search for Technology Adoption - -Search for current adoption strategies: -Search the web: "technology adoption strategies migration" - -**Adoption focus:** - -- Technology migration patterns and approaches -- Gradual adoption vs big bang strategies -- Legacy system modernization approaches -- Vendor evaluation and selection criteria - -### 3. Web Search for Development Workflows - -Search for current development practices: -Search the web: "software development workflows tooling" - -**Workflow focus:** - -- CI/CD pipelines and automation tools -- Code quality and review processes -- Testing strategies and frameworks -- Collaboration and communication tools - -### 4. Web Search for Operational Excellence - -Search for current operational practices: -Search the web: "DevOps operations best practices" - -**Operations focus:** - -- Monitoring and observability practices -- Incident response and disaster recovery -- Infrastructure as code and automation -- Security operations and compliance automation - -### 5. Generate Implementation Research Content - -Prepare implementation analysis with web search citations: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Implementation Approaches and Technology Adoption - -### Technology Adoption Strategies - -[Technology adoption analysis with source citations] -_Source: [URL]_ - -### Development Workflows and Tooling - -[Development workflows analysis with source citations] -_Source: [URL]_ - -### Testing and Quality Assurance - -[Testing approaches analysis with source citations] -_Source: [URL]_ - -### Deployment and Operations Practices - -[Deployment practices analysis with source citations] -_Source: [URL]_ - -### Team Organization and Skills - -[Team organization analysis with source citations] -_Source: [URL]_ - -### Cost Optimization and Resource Management - -[Cost optimization analysis with source citations] -_Source: [URL]_ - -### Risk Assessment and Mitigation - -[Risk mitigation analysis with source citations] -_Source: [URL]_ - -## Technical Research Recommendations - -### Implementation Roadmap - -[Implementation roadmap recommendations] - -### Technology Stack Recommendations - -[Technology stack suggestions] - -### Skill Development Requirements - -[Skill development recommendations] - -### Success Metrics and KPIs - -[Success measurement framework] -``` - -### 6. Present Analysis and Continue Option - -Show the generated implementation research and present continue option: -"I've completed the **implementation research and technology adoption** analysis for {{research_topic}}. - -**Implementation Highlights:** - -- Technology adoption strategies and migration patterns documented -- Development workflows and tooling ecosystems analyzed -- Testing, deployment, and operational practices mapped -- Team organization and skill requirements identified -- Cost optimization and resource management strategies provided - -**Technical research phases completed:** - -- Step 1: Research scope confirmation -- Step 2: Technology stack analysis -- Step 3: Integration patterns analysis -- Step 4: Architectural patterns analysis -- Step 5: Implementation research (current step) - -**Ready to proceed to the final synthesis step?** -[C] Continue - Save this to document and proceed to synthesis - -### 7. Handle Continue Selection - -#### If 'C' (Continue): - -- Append the final content to the research document -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]` -- Load: `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the research document using the structure from step 5. - -## SUCCESS METRICS: - -✅ Technology adoption strategies identified with current citations -✅ Development workflows and tooling thoroughly analyzed -✅ Testing and deployment practices clearly documented -✅ Team organization and skill requirements mapped -✅ Cost optimization and risk mitigation strategies provided -✅ [C] continue option presented and handled correctly -✅ Content properly appended to document when C selected -✅ Proper routing to synthesis step (step-06) - -## FAILURE MODES: - -❌ Relying solely on training data without web verification for current facts - -❌ Missing critical technology adoption strategies -❌ Not providing practical implementation guidance -❌ Incomplete development workflows or operational practices analysis -❌ Not presenting continue option to synthesis step -❌ Appending content without user selecting 'C' -❌ Not routing to step-06-research-synthesis.md - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## IMPLEMENTATION RESEARCH PROTOCOLS: - -- Search for implementation case studies and success stories -- Research technology migration patterns and lessons learned -- Identify common implementation challenges and solutions -- Research development tooling ecosystem evaluations -- Analyze operational excellence frameworks and maturity models - -## TECHNICAL RESEARCH WORKFLOW COMPLETION: - -When 'C' is selected: - -- Implementation research step completed -- Content appended to research document with source citations -- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5] -- Ready to proceed to final synthesis step - -## NEXT STEP: - -After user selects 'C', load `{project-root}/_bmad/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md` to produce the comprehensive technical research document with narrative introduction, detailed TOC, and executive summary. diff --git a/src/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md b/src/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md deleted file mode 100644 index 96852cb1b..000000000 --- a/src/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md +++ /dev/null @@ -1,487 +0,0 @@ -# Technical Research Step 6: Technical Synthesis and Completion - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without web search verification - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ Search the web to verify and supplement your knowledge with current facts -- 📋 YOU ARE A TECHNICAL RESEARCH STRATEGIST, not content generator -- 💬 FOCUS on comprehensive technical synthesis and authoritative conclusions -- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources -- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show web search analysis before presenting findings -- ⚠️ Present [C] complete option after synthesis content generation -- 💾 ONLY save when user chooses C (Complete) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow -- 🚫 FORBIDDEN to complete workflow until C is selected -- 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- **Research topic = "{{research_topic}}"** - comprehensive technical analysis -- **Research goals = "{{research_goals}}"** - achieved through exhaustive technical research -- All technical research sections have been completed (overview, architecture, implementation) -- Web search capabilities with source verification are enabled -- This is the final synthesis step producing the complete technical research document - -## YOUR TASK: - -Produce a comprehensive, authoritative technical research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive technical research. - -## COMPREHENSIVE TECHNICAL DOCUMENT SYNTHESIS: - -### 1. Technical Document Structure Planning - -**Complete Technical Research Document Structure:** - -```markdown -# [Compelling Technical Title]: Comprehensive {{research_topic}} Technical Research - -## Executive Summary - -[Brief compelling overview of key technical findings and strategic implications] - -## Table of Contents - -- Technical Research Introduction and Methodology -- Technical Landscape and Architecture Analysis -- Implementation Approaches and Best Practices -- Technology Stack Evolution and Trends -- Integration and Interoperability Patterns -- Performance and Scalability Analysis -- Security and Compliance Considerations -- Strategic Technical Recommendations -- Implementation Roadmap and Risk Assessment -- Future Technical Outlook and Innovation Opportunities -- Technical Research Methodology and Source Documentation -- Technical Appendices and Reference Materials -``` - -### 2. Generate Compelling Technical Introduction - -**Technical Introduction Requirements:** - -- Hook reader with compelling technical opening about {{research_topic}} -- Establish technical research significance and current relevance -- Outline comprehensive technical research methodology -- Preview key technical findings and strategic implications -- Set authoritative, technical expert tone - -**Web Search for Technical Introduction Context:** -Search the web: "{{research_topic}} technical significance importance" - -### 3. Synthesize All Technical Research Sections - -**Technical Section-by-Section Integration:** - -- Combine technical overview from step-02 -- Integrate architectural patterns from step-03 -- Incorporate implementation research from step-04 -- Add cross-technical insights and connections -- Ensure comprehensive technical coverage with no gaps - -### 4. Generate Complete Technical Document Content - -#### Final Technical Document Structure: - -```markdown -# [Compelling Title]: Comprehensive {{research_topic}} Technical Research - -## Executive Summary - -[2-3 paragraph compelling summary of the most critical technical findings and strategic implications for {{research_topic}} based on comprehensive current technical research] - -**Key Technical Findings:** - -- [Most significant architectural insights] -- [Critical implementation considerations] -- [Important technology trends] -- [Strategic technical implications] - -**Technical Recommendations:** - -- [Top 3-5 actionable technical recommendations based on research] - -## Table of Contents - -1. Technical Research Introduction and Methodology -2. {{research_topic}} Technical Landscape and Architecture Analysis -3. Implementation Approaches and Best Practices -4. Technology Stack Evolution and Current Trends -5. Integration and Interoperability Patterns -6. Performance and Scalability Analysis -7. Security and Compliance Considerations -8. Strategic Technical Recommendations -9. Implementation Roadmap and Risk Assessment -10. Future Technical Outlook and Innovation Opportunities -11. Technical Research Methodology and Source Verification -12. Technical Appendices and Reference Materials - -## 1. Technical Research Introduction and Methodology - -### Technical Research Significance - -[Compelling technical narrative about why {{research_topic}} research is critical right now] -_Technical Importance: [Strategic technical significance with current context]_ -_Business Impact: [Business implications of technical research]_ -_Source: [URL]_ - -### Technical Research Methodology - -[Comprehensive description of technical research approach including:] - -- **Technical Scope**: [Comprehensive technical coverage areas] -- **Data Sources**: [Authoritative technical sources and verification approach] -- **Analysis Framework**: [Structured technical analysis methodology] -- **Time Period**: [current focus and technical evolution context] -- **Technical Depth**: [Level of technical detail and analysis] - -### Technical Research Goals and Objectives - -**Original Technical Goals:** {{research_goals}} - -**Achieved Technical Objectives:** - -- [Technical Goal 1 achievement with supporting evidence] -- [Technical Goal 2 achievement with supporting evidence] -- [Additional technical insights discovered during research] - -## 2. {{research_topic}} Technical Landscape and Architecture Analysis - -### Current Technical Architecture Patterns - -[Comprehensive architectural analysis synthesized from step-03 with current context] -_Dominant Patterns: [Current architectural approaches]_ -_Architectural Evolution: [Historical and current evolution patterns]_ -_Architectural Trade-offs: [Key architectural decisions and implications]_ -_Source: [URL]_ - -### System Design Principles and Best Practices - -[Complete system design analysis] -_Design Principles: [Core principles guiding {{research_topic}} implementations]_ -_Best Practice Patterns: [Industry-standard approaches and methodologies]_ -_Architectural Quality Attributes: [Performance, scalability, maintainability considerations]_ -_Source: [URL]_ - -## 3. Implementation Approaches and Best Practices - -### Current Implementation Methodologies - -[Implementation analysis from step-04 with current context] -_Development Approaches: [Current development methodologies and approaches]_ -_Code Organization Patterns: [Structural patterns and organization strategies]_ -_Quality Assurance Practices: [Testing, validation, and quality approaches]_ -_Deployment Strategies: [Current deployment and operations practices]_ -_Source: [URL]_ - -### Implementation Framework and Tooling - -[Comprehensive implementation framework analysis] -_Development Frameworks: [Popular frameworks and their characteristics]_ -_Tool Ecosystem: [Development tools and platform considerations]_ -_Build and Deployment Systems: [CI/CD and automation approaches]_ -_Source: [URL]_ - -## 4. Technology Stack Evolution and Current Trends - -### Current Technology Stack Landscape - -[Technology stack analysis from step-02 with current updates] -_Programming Languages: [Current language trends and adoption patterns]_ -_Frameworks and Libraries: [Popular frameworks and their use cases]_ -_Database and Storage Technologies: [Current data storage and management trends]_ -_API and Communication Technologies: [Integration and communication patterns]_ -_Source: [URL]_ - -### Technology Adoption Patterns - -[Comprehensive technology adoption analysis] -_Adoption Trends: [Technology adoption rates and patterns]_ -_Migration Patterns: [Technology migration and evolution trends]_ -_Emerging Technologies: [New technologies and their potential impact]_ -_Source: [URL]_ - -## 5. Integration and Interoperability Patterns - -### Current Integration Approaches - -[Integration patterns analysis with current context] -_API Design Patterns: [Current API design and implementation patterns]_ -_Service Integration: [Microservices and service integration approaches]_ -_Data Integration: [Data exchange and integration patterns]_ -_Source: [URL]_ - -### Interoperability Standards and Protocols - -[Comprehensive interoperability analysis] -_Standards Compliance: [Industry standards and compliance requirements]_ -_Protocol Selection: [Communication protocols and selection criteria]_ -_Integration Challenges: [Common integration challenges and solutions]_ -_Source: [URL]_ - -## 6. Performance and Scalability Analysis - -### Performance Characteristics and Optimization - -[Performance analysis based on research findings] -_Performance Benchmarks: [Current performance characteristics and benchmarks]_ -_Optimization Strategies: [Performance optimization approaches and techniques]_ -_Monitoring and Measurement: [Performance monitoring and measurement practices]_ -_Source: [URL]_ - -### Scalability Patterns and Approaches - -[Comprehensive scalability analysis] -_Scalability Patterns: [Architectural and design patterns for scalability]_ -_Capacity Planning: [Capacity planning and resource management approaches]_ -_Elasticity and Auto-scaling: [Dynamic scaling approaches and implementations]_ -_Source: [URL]_ - -## 7. Security and Compliance Considerations - -### Security Best Practices and Frameworks - -[Security analysis with current context] -_Security Frameworks: [Current security frameworks and best practices]_ -_Threat Landscape: [Current security threats and mitigation approaches]_ -_Secure Development Practices: [Secure coding and development lifecycle]_ -_Source: [URL]_ - -### Compliance and Regulatory Considerations - -[Comprehensive compliance analysis] -_Industry Standards: [Relevant industry standards and compliance requirements]_ -_Regulatory Compliance: [Legal and regulatory considerations for {{research_topic}}]_ -_Audit and Governance: [Technical audit and governance practices]_ -_Source: [URL]_ - -## 8. Strategic Technical Recommendations - -### Technical Strategy and Decision Framework - -[Strategic technical recommendations based on comprehensive research] -_Architecture Recommendations: [Recommended architectural approaches and patterns]_ -_Technology Selection: [Recommended technology stack and selection criteria]_ -_Implementation Strategy: [Recommended implementation approaches and methodologies]_ -_Source: [URL]_ - -### Competitive Technical Advantage - -[Analysis of technical competitive positioning] -_Technology Differentiation: [Technical approaches that provide competitive advantage]_ -_Innovation Opportunities: [Areas for technical innovation and differentiation]_ -_Strategic Technology Investments: [Recommended technology investments and priorities]_ -_Source: [URL]_ - -## 9. Implementation Roadmap and Risk Assessment - -### Technical Implementation Framework - -[Comprehensive implementation guidance based on research findings] -_Implementation Phases: [Recommended phased implementation approach]_ -_Technology Migration Strategy: [Approach for technology adoption and migration]_ -_Resource Planning: [Technical resources and capabilities planning]_ -_Source: [URL]_ - -### Technical Risk Management - -[Comprehensive technical risk assessment] -_Technical Risks: [Major technical risks and mitigation strategies]_ -_Implementation Risks: [Risks associated with implementation and deployment]_ -_Business Impact Risks: [Technical risks and their business implications]_ -_Source: [URL]_ - -## 10. Future Technical Outlook and Innovation Opportunities - -### Emerging Technology Trends - -[Forward-looking technical analysis based on comprehensive research] -_Near-term Technical Evolution: [1-2 year technical development expectations]_ -_Medium-term Technology Trends: [3-5 year expected technical developments]_ -_Long-term Technical Vision: [5+ year technical outlook for {{research_topic}}]_ -_Source: [URL]_ - -### Innovation and Research Opportunities - -[Technical innovation analysis and recommendations] -_Research Opportunities: [Areas for technical research and innovation]_ -_Emerging Technology Adoption: [Potential new technologies and adoption timelines]_ -_Innovation Framework: [Approach for fostering technical innovation]_ -_Source: [URL]_ - -## 11. Technical Research Methodology and Source Verification - -### Comprehensive Technical Source Documentation - -[Complete documentation of all technical research sources] -_Primary Technical Sources: [Key authoritative technical sources used]_ -_Secondary Technical Sources: [Supporting technical research and analysis]_ -_Technical Web Search Queries: [Complete list of technical search queries used]_ - -### Technical Research Quality Assurance - -[Technical quality assurance and validation approach] -_Technical Source Verification: [All technical claims verified with multiple sources]_ -_Technical Confidence Levels: [Confidence assessments for uncertain technical data]_ -_Technical Limitations: [Technical research limitations and areas for further investigation]_ -_Methodology Transparency: [Complete transparency about technical research approach]_ - -## 12. Technical Appendices and Reference Materials - -### Detailed Technical Data Tables - -[Comprehensive technical data tables supporting research findings] -_Architectural Pattern Tables: [Detailed architectural pattern comparisons]_ -_Technology Stack Analysis: [Detailed technology evaluation and comparison data]_ -_Performance Benchmark Data: [Comprehensive performance measurement data]_ - -### Technical Resources and References - -[Valuable technical resources for continued research and implementation] -_Technical Standards: [Relevant technical standards and specifications]_ -_Open Source Projects: [Key open source projects and communities]_ -_Research Papers and Publications: [Academic and industry research sources]_ -_Technical Communities: [Professional networks and technical communities]_ - ---- - -## Technical Research Conclusion - -### Summary of Key Technical Findings - -[Comprehensive summary of the most important technical research findings] - -### Strategic Technical Impact Assessment - -[Assessment of technical implications for {{research_topic}}] - -### Next Steps Technical Recommendations - -[Specific next steps for leveraging this technical research] - ---- - -**Technical Research Completion Date:** {{date}} -**Research Period:** current comprehensive technical analysis -**Document Length:** As needed for comprehensive technical coverage -**Source Verification:** All technical facts cited with current sources -**Technical Confidence Level:** High - based on multiple authoritative technical sources - -_This comprehensive technical research document serves as an authoritative technical reference on {{research_topic}} and provides strategic technical insights for informed decision-making and implementation._ -``` - -### 5. Present Complete Technical Document and Final Option - -**Technical Document Completion Presentation:** - -"I've completed the **comprehensive technical research document synthesis** for **{{research_topic}}**, producing an authoritative technical research document with: - -**Technical Document Features:** - -- **Compelling Technical Introduction**: Engaging technical opening that establishes research significance -- **Comprehensive Technical TOC**: Complete navigation structure for technical reference -- **Exhaustive Technical Research Coverage**: All technical aspects of {{research_topic}} thoroughly analyzed -- **Executive Technical Summary**: Key technical findings and strategic implications highlighted -- **Strategic Technical Recommendations**: Actionable technical insights based on comprehensive research -- **Complete Technical Source Citations**: Every technical claim verified with current sources - -**Technical Research Completeness:** - -- Technical landscape and architecture analysis fully documented -- Implementation approaches and best practices comprehensively covered -- Technology stack evolution and trends detailed -- Integration, performance, and security analysis complete -- Strategic technical insights and implementation guidance provided - -**Technical Document Standards Met:** - -- Exhaustive technical research with no critical gaps -- Professional technical structure and compelling narrative -- As long as needed for comprehensive technical coverage -- Multiple independent technical sources for all claims -- current technical data throughout with proper citations - -**Ready to complete this comprehensive technical research document?** -[C] Complete Research - Save final comprehensive technical document - -### 6. Handle Final Technical Completion - -#### If 'C' (Complete Research): - -- **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section -- Append the complete technical document to the research file -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]` -- Complete the technical research workflow -- Provide final technical document delivery confirmation - -## APPEND TO DOCUMENT: - -When user selects 'C', append the complete comprehensive technical research document using the full structure above. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document. - -## SUCCESS METRICS: - -✅ Compelling technical introduction with research significance -✅ Comprehensive technical table of contents with complete document structure -✅ Exhaustive technical research coverage across all technical aspects -✅ Executive technical summary with key findings and strategic implications -✅ Strategic technical recommendations grounded in comprehensive research -✅ Complete technical source verification with current citations -✅ Professional technical document structure and compelling narrative -✅ [C] complete option presented and handled correctly -✅ Technical research workflow completed with comprehensive document - -## FAILURE MODES: - -❌ Not producing compelling technical introduction -❌ Missing comprehensive technical table of contents -❌ Incomplete technical research coverage across technical aspects -❌ Not providing executive technical summary with key findings -❌ Missing strategic technical recommendations based on research -❌ Relying solely on training data without web verification for current facts -❌ Producing technical document without professional structure -❌ Not presenting completion option for final technical document - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## COMPREHENSIVE TECHNICAL DOCUMENT STANDARDS: - -This step ensures the final technical research document: - -- Serves as an authoritative technical reference on {{research_topic}} -- Provides strategic technical insights for informed decision-making -- Includes comprehensive technical coverage with no gaps -- Maintains rigorous technical source verification standards -- Delivers strategic technical insights and actionable recommendations -- Meets professional technical research document quality standards - -## TECHNICAL RESEARCH WORKFLOW COMPLETION: - -When 'C' is selected: - -- All technical research steps completed (1-5) -- Comprehensive technical research document generated -- Professional technical document structure with intro, TOC, and summary -- All technical sections appended with source citations -- Technical research workflow status updated to complete -- Final comprehensive technical research document delivered to user - -## FINAL TECHNICAL DELIVERABLE: - -Complete authoritative technical research document on {{research_topic}} that: - -- Establishes technical credibility through comprehensive research -- Provides strategic technical insights for informed decision-making -- Serves as technical reference document for continued use -- Maintains highest technical research quality standards with current verification - -Congratulations on completing comprehensive technical research with professional documentation! 🎉 diff --git a/src/bmm/workflows/1-analysis/research/workflow-domain-research.md b/src/bmm/workflows/1-analysis/research/workflow-domain-research.md deleted file mode 100644 index ec193660d..000000000 --- a/src/bmm/workflows/1-analysis/research/workflow-domain-research.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -name: domain-research -description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"' ---- - -# Domain Research Workflow - -**Goal:** Conduct comprehensive domain/industry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations. - -**Your Role:** You are a domain research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction. - -## PREREQUISITE - -**⛔ Web search required.** If unavailable, abort and tell the user. - -## CONFIGURATION - -Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve: -- `project_name`, `output_folder`, `planning_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as a system-generated value - -## QUICK TOPIC DISCOVERY - -"Welcome {{user_name}}! Let's get started with your **domain/industry research**. - -**What domain, industry, or sector do you want to research?** - -For example: -- 'The healthcare technology industry' -- 'Sustainable packaging regulations in Europe' -- 'Construction and building materials sector' -- 'Or any other domain you have in mind...'" - -### Topic Clarification - -Based on the user's topic, briefly clarify: -1. **Core Domain**: "What specific aspect of [domain] are you most interested in?" -2. **Research Goals**: "What do you hope to achieve with this research?" -3. **Scope**: "Should we focus broadly or dive deep into specific aspects?" - -## ROUTE TO DOMAIN RESEARCH STEPS - -After gathering the topic and goals: - -1. Set `research_type = "domain"` -2. Set `research_topic = [discovered topic from discussion]` -3. Set `research_goals = [discovered goals from discussion]` -4. Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents -5. Load: `./domain-steps/step-01-init.md` with topic context - -**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for domain research. - -**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`** diff --git a/src/bmm/workflows/1-analysis/research/workflow-market-research.md b/src/bmm/workflows/1-analysis/research/workflow-market-research.md deleted file mode 100644 index 8a77a67cd..000000000 --- a/src/bmm/workflows/1-analysis/research/workflow-market-research.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -name: market-research -description: 'Conduct market research on competition and customers. Use when the user says "create a market research report about [business idea]".' ---- - -# Market Research Workflow - -**Goal:** Conduct comprehensive market research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations. - -**Your Role:** You are a market research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction. - -## PREREQUISITE - -**⛔ Web search required.** If unavailable, abort and tell the user. - -## CONFIGURATION - -Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve: -- `project_name`, `output_folder`, `planning_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as a system-generated value - -## QUICK TOPIC DISCOVERY - -"Welcome {{user_name}}! Let's get started with your **market research**. - -**What topic, problem, or area do you want to research?** - -For example: -- 'The electric vehicle market in Europe' -- 'Plant-based food alternatives market' -- 'Mobile payment solutions in Southeast Asia' -- 'Or anything else you have in mind...'" - -### Topic Clarification - -Based on the user's topic, briefly clarify: -1. **Core Topic**: "What exactly about [topic] are you most interested in?" -2. **Research Goals**: "What do you hope to achieve with this research?" -3. **Scope**: "Should we focus broadly or dive deep into specific aspects?" - -## ROUTE TO MARKET RESEARCH STEPS - -After gathering the topic and goals: - -1. Set `research_type = "market"` -2. Set `research_topic = [discovered topic from discussion]` -3. Set `research_goals = [discovered goals from discussion]` -4. Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents -5. Load: `./market-steps/step-01-init.md` with topic context - -**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for market research. - -**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`** diff --git a/src/bmm/workflows/1-analysis/research/workflow-technical-research.md b/src/bmm/workflows/1-analysis/research/workflow-technical-research.md deleted file mode 100644 index ecc9a2f27..000000000 --- a/src/bmm/workflows/1-analysis/research/workflow-technical-research.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -name: technical-research -description: 'Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".' ---- - -# Technical Research Workflow - -**Goal:** Conduct comprehensive technical research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations. - -**Your Role:** You are a technical research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction. - -## PREREQUISITE - -**⛔ Web search required.** If unavailable, abort and tell the user. - -## CONFIGURATION - -Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve: -- `project_name`, `output_folder`, `planning_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as a system-generated value - -## QUICK TOPIC DISCOVERY - -"Welcome {{user_name}}! Let's get started with your **technical research**. - -**What technology, tool, or technical area do you want to research?** - -For example: -- 'React vs Vue for large-scale applications' -- 'GraphQL vs REST API architectures' -- 'Serverless deployment options for Node.js' -- 'Or any other technical topic you have in mind...'" - -### Topic Clarification - -Based on the user's topic, briefly clarify: -1. **Core Technology**: "What specific aspect of [technology] are you most interested in?" -2. **Research Goals**: "What do you hope to achieve with this research?" -3. **Scope**: "Should we focus broadly or dive deep into specific aspects?" - -## ROUTE TO TECHNICAL RESEARCH STEPS - -After gathering the topic and goals: - -1. Set `research_type = "technical"` -2. Set `research_topic = [discovered topic from discussion]` -3. Set `research_goals = [discovered goals from discussion]` -4. Create the starter output file: `{planning_artifacts}/research/technical-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents -5. Load: `./technical-steps/step-01-init.md` with topic context - -**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for technical research. - -**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`** diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/data/domain-complexity.csv b/src/bmm/workflows/2-plan-workflows/create-prd/data/domain-complexity.csv deleted file mode 100644 index 60a7b503f..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/data/domain-complexity.csv +++ /dev/null @@ -1,15 +0,0 @@ -domain,signals,complexity,key_concerns,required_knowledge,suggested_workflow,web_searches,special_sections -healthcare,"medical,diagnostic,clinical,FDA,patient,treatment,HIPAA,therapy,pharma,drug",high,"FDA approval;Clinical validation;HIPAA compliance;Patient safety;Medical device classification;Liability","Regulatory pathways;Clinical trial design;Medical standards;Data privacy;Integration requirements","domain-research","FDA software medical device guidance {date};HIPAA compliance software requirements;Medical software standards {date};Clinical validation software","clinical_requirements;regulatory_pathway;validation_methodology;safety_measures" -fintech,"payment,banking,trading,investment,crypto,wallet,transaction,KYC,AML,funds,fintech",high,"Regional compliance;Security standards;Audit requirements;Fraud prevention;Data protection","KYC/AML requirements;PCI DSS;Open banking;Regional laws (US/EU/APAC);Crypto regulations","domain-research","fintech regulations {date};payment processing compliance {date};open banking API standards;cryptocurrency regulations {date}","compliance_matrix;security_architecture;audit_requirements;fraud_prevention" -govtech,"government,federal,civic,public sector,citizen,municipal,voting",high,"Procurement rules;Security clearance;Accessibility (508);FedRAMP;Privacy;Transparency","Government procurement;Security frameworks;Accessibility standards;Privacy laws;Open data requirements","domain-research","government software procurement {date};FedRAMP compliance requirements;section 508 accessibility;government security standards","procurement_compliance;security_clearance;accessibility_standards;transparency_requirements" -edtech,"education,learning,student,teacher,curriculum,assessment,K-12,university,LMS",medium,"Student privacy (COPPA/FERPA);Accessibility;Content moderation;Age verification;Curriculum standards","Educational privacy laws;Learning standards;Accessibility requirements;Content guidelines;Assessment validity","domain-research","educational software privacy {date};COPPA FERPA compliance;WCAG education requirements;learning management standards","privacy_compliance;content_guidelines;accessibility_features;curriculum_alignment" -aerospace,"aircraft,spacecraft,aviation,drone,satellite,propulsion,flight,radar,navigation",high,"Safety certification;DO-178C compliance;Performance validation;Simulation accuracy;Export controls","Aviation standards;Safety analysis;Simulation validation;ITAR/export controls;Performance requirements","domain-research + technical-model","DO-178C software certification;aerospace simulation standards {date};ITAR export controls software;aviation safety requirements","safety_certification;simulation_validation;performance_requirements;export_compliance" -automotive,"vehicle,car,autonomous,ADAS,automotive,driving,EV,charging",high,"Safety standards;ISO 26262;V2X communication;Real-time requirements;Certification","Automotive standards;Functional safety;V2X protocols;Real-time systems;Testing requirements","domain-research","ISO 26262 automotive software;automotive safety standards {date};V2X communication protocols;EV charging standards","safety_standards;functional_safety;communication_protocols;certification_requirements" -scientific,"research,algorithm,simulation,modeling,computational,analysis,data science,ML,AI",medium,"Reproducibility;Validation methodology;Peer review;Performance;Accuracy;Computational resources","Scientific method;Statistical validity;Computational requirements;Domain expertise;Publication standards","technical-model","scientific computing best practices {date};research reproducibility standards;computational modeling validation;peer review software","validation_methodology;accuracy_metrics;reproducibility_plan;computational_requirements" -legaltech,"legal,law,contract,compliance,litigation,patent,attorney,court",high,"Legal ethics;Bar regulations;Data retention;Attorney-client privilege;Court system integration","Legal practice rules;Ethics requirements;Court filing systems;Document standards;Confidentiality","domain-research","legal technology ethics {date};law practice management software requirements;court filing system standards;attorney client privilege technology","ethics_compliance;data_retention;confidentiality_measures;court_integration" -insuretech,"insurance,claims,underwriting,actuarial,policy,risk,premium",high,"Insurance regulations;Actuarial standards;Data privacy;Fraud detection;State compliance","Insurance regulations by state;Actuarial methods;Risk modeling;Claims processing;Regulatory reporting","domain-research","insurance software regulations {date};actuarial standards software;insurance fraud detection;state insurance compliance","regulatory_requirements;risk_modeling;fraud_detection;reporting_compliance" -energy,"energy,utility,grid,solar,wind,power,electricity,oil,gas",high,"Grid compliance;NERC standards;Environmental regulations;Safety requirements;Real-time operations","Energy regulations;Grid standards;Environmental compliance;Safety protocols;SCADA systems","domain-research","energy sector software compliance {date};NERC CIP standards;smart grid requirements;renewable energy software standards","grid_compliance;safety_protocols;environmental_compliance;operational_requirements" -process_control,"industrial automation,process control,PLC,SCADA,DCS,HMI,operational technology,OT,control system,cyberphysical,MES,historian,instrumentation,I&C,P&ID",high,"Functional safety;OT cybersecurity;Real-time control requirements;Legacy system integration;Process safety and hazard analysis;Environmental compliance and permitting;Engineering authority and PE requirements","Functional safety standards;OT security frameworks;Industrial protocols;Process control architecture;Plant reliability and maintainability","domain-research + technical-model","IEC 62443 OT cybersecurity requirements {date};functional safety software requirements {date};industrial process control architecture;ISA-95 manufacturing integration","functional_safety;ot_security;process_requirements;engineering_authority" -building_automation,"building automation,BAS,BMS,HVAC,smart building,lighting control,fire alarm,fire protection,fire suppression,life safety,elevator,access control,DDC,energy management,sequence of operations,commissioning",high,"Life safety codes;Building energy standards;Multi-trade coordination and interoperability;Commissioning and ongoing operational performance;Indoor environmental quality and occupant comfort;Engineering authority and PE requirements","Building automation protocols;HVAC and mechanical controls;Fire alarm, fire protection, and life safety design;Commissioning process and sequence of operations;Building codes and energy standards","domain-research","smart building software architecture {date};BACnet integration best practices;building automation cybersecurity {date};ASHRAE building standards","life_safety;energy_compliance;commissioning_requirements;engineering_authority" -gaming,"game,player,gameplay,level,character,multiplayer,quest",redirect,"REDIRECT TO GAME WORKFLOWS","Game design","game-brief","NA","NA" -general,"",low,"Standard requirements;Basic security;User experience;Performance","General software practices","continue","software development best practices {date}","standard_requirements" \ No newline at end of file diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md b/src/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md deleted file mode 100644 index 755230be7..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md +++ /dev/null @@ -1,197 +0,0 @@ -# BMAD PRD Purpose - -**The PRD is the top of the required funnel that feeds all subsequent product development work in rhw BMad Method.** - ---- - -## What is a BMAD PRD? - -A dual-audience document serving: -1. **Human Product Managers and builders** - Vision, strategy, stakeholder communication -2. **LLM Downstream Consumption** - UX Design → Architecture → Epics → Development AI Agents - -Each successive document becomes more AI-tailored and granular. - ---- - -## Core Philosophy: Information Density - -**High Signal-to-Noise Ratio** - -Every sentence must carry information weight. LLMs consume precise, dense content efficiently. - -**Anti-Patterns (Eliminate These):** -- ❌ "The system will allow users to..." → ✅ "Users can..." -- ❌ "It is important to note that..." → ✅ State the fact directly -- ❌ "In order to..." → ✅ "To..." -- ❌ Conversational filler and padding → ✅ Direct, concise statements - -**Goal:** Maximum information per word. Zero fluff. - ---- - -## The Traceability Chain - -**PRD starts the chain:** -``` -Vision → Success Criteria → User Journeys → Functional Requirements → (future: User Stories) -``` - -**In the PRD, establish:** -- Vision → Success Criteria alignment -- Success Criteria → User Journey coverage -- User Journey → Functional Requirement mapping -- All requirements traceable to user needs - -**Why:** Each downstream artifact (UX, Architecture, Epics, Stories) must trace back to documented user needs and business objectives. This chain ensures we build the right thing. - ---- - -## What Makes Great Functional Requirements? - -### FRs are Capabilities, Not Implementation - -**Good FR:** "Users can reset their password via email link" -**Bad FR:** "System sends JWT via email and validates with database" (implementation leakage) - -**Good FR:** "Dashboard loads in under 2 seconds for 95th percentile" -**Bad FR:** "Fast loading time" (subjective, unmeasurable) - -### SMART Quality Criteria - -**Specific:** Clear, precisely defined capability -**Measurable:** Quantifiable with test criteria -**Attainable:** Realistic within constraints -**Relevant:** Aligns with business objectives -**Traceable:** Links to source (executive summary or user journey) - -### FR Anti-Patterns - -**Subjective Adjectives:** -- ❌ "easy to use", "intuitive", "user-friendly", "fast", "responsive" -- ✅ Use metrics: "completes task in under 3 clicks", "loads in under 2 seconds" - -**Implementation Leakage:** -- ❌ Technology names, specific libraries, implementation details -- ✅ Focus on capability and measurable outcomes - -**Vague Quantifiers:** -- ❌ "multiple users", "several options", "various formats" -- ✅ "up to 100 concurrent users", "3-5 options", "PDF, DOCX, TXT formats" - -**Missing Test Criteria:** -- ❌ "The system shall provide notifications" -- ✅ "The system shall send email notifications within 30 seconds of trigger event" - ---- - -## What Makes Great Non-Functional Requirements? - -### NFRs Must Be Measurable - -**Template:** -``` -"The system shall [metric] [condition] [measurement method]" -``` - -**Examples:** -- ✅ "The system shall respond to API requests in under 200ms for 95th percentile as measured by APM monitoring" -- ✅ "The system shall maintain 99.9% uptime during business hours as measured by cloud provider SLA" -- ✅ "The system shall support 10,000 concurrent users as measured by load testing" - -### NFR Anti-Patterns - -**Unmeasurable Claims:** -- ❌ "The system shall be scalable" → ✅ "The system shall handle 10x load growth through horizontal scaling" -- ❌ "High availability required" → ✅ "99.9% uptime as measured by cloud provider SLA" - -**Missing Context:** -- ❌ "Response time under 1 second" → ✅ "API response time under 1 second for 95th percentile under normal load" - ---- - -## Domain-Specific Requirements - -**Auto-Detect and Enforce Based on Project Context** - -Certain industries have mandatory requirements that must be present: - -- **Healthcare:** HIPAA Privacy & Security Rules, PHI encryption, audit logging, MFA -- **Fintech:** PCI-DSS Level 1, AML/KYC compliance, SOX controls, financial audit trails -- **GovTech:** NIST framework, Section 508 accessibility (WCAG 2.1 AA), FedRAMP, data residency -- **E-Commerce:** PCI-DSS for payments, inventory accuracy, tax calculation by jurisdiction - -**Why:** Missing these requirements in the PRD means they'll be missed in architecture and implementation, creating expensive rework. During PRD creation there is a step to cover this - during validation we want to make sure it was covered. For this purpose steps will utilize a domain-complexity.csv and project-types.csv. - ---- - -## Document Structure (Markdown, Human-Readable) - -### Required Sections -1. **Executive Summary** - Vision, differentiator, target users -2. **Success Criteria** - Measurable outcomes (SMART) -3. **Product Scope** - MVP, Growth, Vision phases -4. **User Journeys** - Comprehensive coverage -5. **Domain Requirements** - Industry-specific compliance (if applicable) -6. **Innovation Analysis** - Competitive differentiation (if applicable) -7. **Project-Type Requirements** - Platform-specific needs -8. **Functional Requirements** - Capability contract (FRs) -9. **Non-Functional Requirements** - Quality attributes (NFRs) - -### Formatting for Dual Consumption - -**For Humans:** -- Clear, professional language -- Logical flow from vision to requirements -- Easy for stakeholders to review and approve - -**For LLMs:** -- ## Level 2 headers for all main sections (enables extraction) -- Consistent structure and patterns -- Precise, testable language -- High information density - ---- - -## Downstream Impact - -**How the PRD Feeds Next Artifacts:** - -**UX Design:** -- User journeys → interaction flows -- FRs → design requirements -- Success criteria → UX metrics - -**Architecture:** -- FRs → system capabilities -- NFRs → architecture decisions -- Domain requirements → compliance architecture -- Project-type requirements → platform choices - -**Epics & Stories (created after architecture):** -- FRs → user stories (1 FR could map to 1-3 stories potentially) -- Acceptance criteria → story acceptance tests -- Priority → sprint sequencing -- Traceability → stories map back to vision - -**Development AI Agents:** -- Precise requirements → implementation clarity -- Test criteria → automated test generation -- Domain requirements → compliance enforcement -- Measurable NFRs → performance targets - ---- - -## Summary: What Makes a Great BMAD PRD? - -✅ **High Information Density** - Every sentence carries weight, zero fluff -✅ **Measurable Requirements** - All FRs and NFRs are testable with specific criteria -✅ **Clear Traceability** - Each requirement links to user need and business objective -✅ **Domain Awareness** - Industry-specific requirements auto-detected and included -✅ **Zero Anti-Patterns** - No subjective adjectives, implementation leakage, or vague quantifiers -✅ **Dual Audience Optimized** - Human-readable AND LLM-consumable -✅ **Markdown Format** - Professional, clean, accessible to all stakeholders - ---- - -**Remember:** The PRD is the foundation. Quality here ripples through every subsequent phase. A dense, precise, well-traced PRD makes UX design, architecture, epic breakdown, and AI development dramatically more effective. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/data/project-types.csv b/src/bmm/workflows/2-plan-workflows/create-prd/data/project-types.csv deleted file mode 100644 index 6f71c513a..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/data/project-types.csv +++ /dev/null @@ -1,11 +0,0 @@ -project_type,detection_signals,key_questions,required_sections,skip_sections,web_search_triggers,innovation_signals -api_backend,"API,REST,GraphQL,backend,service,endpoints","Endpoints needed?;Authentication method?;Data formats?;Rate limits?;Versioning?;SDK needed?","endpoint_specs;auth_model;data_schemas;error_codes;rate_limits;api_docs","ux_ui;visual_design;user_journeys","framework best practices;OpenAPI standards","API composition;New protocol" -mobile_app,"iOS,Android,app,mobile,iPhone,iPad","Native or cross-platform?;Offline needed?;Push notifications?;Device features?;Store compliance?","platform_reqs;device_permissions;offline_mode;push_strategy;store_compliance","desktop_features;cli_commands","app store guidelines;platform requirements","Gesture innovation;AR/VR features" -saas_b2b,"SaaS,B2B,platform,dashboard,teams,enterprise","Multi-tenant?;Permission model?;Subscription tiers?;Integrations?;Compliance?","tenant_model;rbac_matrix;subscription_tiers;integration_list;compliance_reqs","cli_interface;mobile_first","compliance requirements;integration guides","Workflow automation;AI agents" -developer_tool,"SDK,library,package,npm,pip,framework","Language support?;Package managers?;IDE integration?;Documentation?;Examples?","language_matrix;installation_methods;api_surface;code_examples;migration_guide","visual_design;store_compliance","package manager best practices;API design patterns","New paradigm;DSL creation" -cli_tool,"CLI,command,terminal,bash,script","Interactive or scriptable?;Output formats?;Config method?;Shell completion?","command_structure;output_formats;config_schema;scripting_support","visual_design;ux_principles;touch_interactions","CLI design patterns;shell integration","Natural language CLI;AI commands" -web_app,"website,webapp,browser,SPA,PWA","SPA or MPA?;Browser support?;SEO needed?;Real-time?;Accessibility?","browser_matrix;responsive_design;performance_targets;seo_strategy;accessibility_level","native_features;cli_commands","web standards;WCAG guidelines","New interaction;WebAssembly use" -game,"game,player,gameplay,level,character","REDIRECT TO USE THE BMad Method Game Module Agent and Workflows - HALT","game-brief;GDD","most_sections","game design patterns","Novel mechanics;Genre mixing" -desktop_app,"desktop,Windows,Mac,Linux,native","Cross-platform?;Auto-update?;System integration?;Offline?","platform_support;system_integration;update_strategy;offline_capabilities","web_seo;mobile_features","desktop guidelines;platform requirements","Desktop AI;System automation" -iot_embedded,"IoT,embedded,device,sensor,hardware","Hardware specs?;Connectivity?;Power constraints?;Security?;OTA updates?","hardware_reqs;connectivity_protocol;power_profile;security_model;update_mechanism","visual_ui;browser_support","IoT standards;protocol specs","Edge AI;New sensors" -blockchain_web3,"blockchain,crypto,DeFi,NFT,smart contract","Chain selection?;Wallet integration?;Gas optimization?;Security audit?","chain_specs;wallet_support;smart_contracts;security_audit;gas_optimization","traditional_auth;centralized_db","blockchain standards;security patterns","Novel tokenomics;DAO structure" \ No newline at end of file diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01-init.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01-init.md deleted file mode 100644 index 4b53688d0..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01-init.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -name: 'step-01-init' -description: 'Initialize the PRD workflow by detecting continuation state and setting up the document' - -# File References -nextStepFile: './step-02-discovery.md' -continueStepFile: './step-01b-continue.md' -outputFile: '{planning_artifacts}/prd.md' - -# Template Reference -prdTemplate: '../templates/prd-template.md' ---- - -# Step 1: Workflow Initialization - -**Progress: Step 1 of 11** - Next: Project Discovery - -## STEP GOAL: - -Initialize the PRD workflow by detecting continuation state, discovering input documents, and setting up the document structure for collaborative product requirement discovery. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused PM facilitator collaborating with an expert peer -- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision - -### Step-Specific Rules: - -- 🎯 Focus only on initialization and setup - no content generation yet -- 🚫 FORBIDDEN to look ahead to future steps or assume knowledge from them -- 💬 Approach: Systematic setup with clear reporting to user -- 🚪 Detect existing workflow state and handle continuation properly - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis of current state before taking any action -- 💾 Initialize document structure and update frontmatter appropriately -- Update frontmatter: add this step name to the end of the steps completed array (it should be the first entry in the steps array since this is step 1) -- 🚫 FORBIDDEN to load next step until user selects 'C' (Continue) - -## CONTEXT BOUNDARIES: - -- Available context: Variables from workflow.md are available in memory -- Focus: Workflow initialization and document setup only -- Limits: Don't assume knowledge from other steps or create content yet -- Dependencies: Configuration loaded from workflow.md initialization - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Check for Existing Workflow State - -First, check if the output document already exists: - -**Workflow State Detection:** - -- Look for file at `{outputFile}` -- If exists, read the complete file including frontmatter -- If not exists, this is a fresh workflow - -### 2. Handle Continuation (If Document Exists) - -If the document exists and has frontmatter with `stepsCompleted` BUT `step-11-complete` is NOT in the list, follow the Continuation Protocol since the document is incomplete: - -**Continuation Protocol:** - -- **STOP immediately** and load `{continueStepFile}` -- Do not proceed with any initialization tasks -- Let step-01b handle all continuation logic -- This is an auto-proceed situation - no user choice needed - -### 3. Fresh Workflow Setup (If No Document) - -If no document exists or no `stepsCompleted` in frontmatter: - -#### A. Input Document Discovery - -Discover and load context documents using smart discovery. Documents can be in the following locations: -- {planning_artifacts}/** -- {output_folder}/** -- {product_knowledge}/** -- docs/** - -Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content) - -Try to discover the following: -- Product Brief (`*brief*.md`) -- Research Documents (`/*research*.md`) -- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.) -- Project Context (`**/project-context.md`) - -Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules - -**Loading Rules:** - -- Load ALL discovered files completely that the user confirmed or provided (no offset/limit) -- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process -- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document -- index.md is a guide to what's relevant whenever available -- Track all successfully loaded files in frontmatter `inputDocuments` array - -#### B. Create Initial Document - -**Document Setup:** - -- Copy the template from `{prdTemplate}` to `{outputFile}` -- Initialize frontmatter with proper structure including inputDocuments array. - -#### C. Present Initialization Results - -**Setup Report to User:** - -"Welcome {{user_name}}! I've set up your PRD workspace for {{project_name}}. - -**Document Setup:** - -- Created: `{outputFile}` from template -- Initialized frontmatter with workflow state - -**Input Documents Discovered:** - -- Product briefs: {{briefCount}} files {if briefCount > 0}✓ loaded{else}(none found){/if} -- Research: {{researchCount}} files {if researchCount > 0}✓ loaded{else}(none found){/if} -- Brainstorming: {{brainstormingCount}} files {if brainstormingCount > 0}✓ loaded{else}(none found){/if} -- Project docs: {{projectDocsCount}} files {if projectDocsCount > 0}✓ loaded (brownfield project){else}(none found - greenfield project){/if} - -**Files loaded:** {list of specific file names or "No additional documents found"} - -{if projectDocsCount > 0} -📋 **Note:** This is a **brownfield project**. Your existing project documentation has been loaded. In the next step, I'll ask specifically about what new features or changes you want to add to your existing system. -{/if} - -Do you have any other documents you'd like me to include, or shall we continue to the next step?" - -### 4. Present MENU OPTIONS - -Display menu after setup report: - -"[C] Continue - Save this and move to Project Discovery (Step 2 of 11)" - -#### Menu Handling Logic: - -- IF C: Update output file frontmatter, adding this step name to the end of the list of stepsCompleted, then read fully and follow: {nextStepFile} -- IF user provides additional files: Load them, update inputDocuments and documentCounts, redisplay report -- IF user asks questions: Answer and redisplay menu - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [frontmatter properly updated with this step added to stepsCompleted and documentCounts], will you then read fully and follow: `{nextStepFile}` to begin project discovery. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Existing workflow detected and properly handed off to step-01b -- Fresh workflow initialized with template and proper frontmatter -- Input documents discovered and loaded using sharded-first logic -- All discovered files tracked in frontmatter `inputDocuments` -- User clearly informed of brownfield vs greenfield status -- Menu presented and user input handled correctly -- Frontmatter updated with this step name added to stepsCompleted before proceeding - -### ❌ SYSTEM FAILURE: - -- Proceeding with fresh initialization when existing workflow exists -- Not updating frontmatter with discovered input documents -- **Not storing document counts in frontmatter** -- Creating document without proper template structure -- Not checking sharded folders first before whole files -- Not reporting discovered documents to user clearly -- Proceeding without user selecting 'C' (Continue) - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01b-continue.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01b-continue.md deleted file mode 100644 index 2ad958b69..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01b-continue.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -name: 'step-01b-continue' -description: 'Resume an interrupted PRD workflow from the last completed step' - -# File References -outputFile: '{planning_artifacts}/prd.md' ---- - -# Step 1B: Workflow Continuation - -## STEP GOAL: - -Resume the PRD workflow from where it was left off, ensuring smooth continuation with full context restoration. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused PM facilitator collaborating with an expert peer -- ✅ We engage in collaborative dialogue, not command-response -- ✅ Resume workflow from exact point where it was interrupted - -### Step-Specific Rules: - -- 💬 FOCUS on understanding where we left off and continuing appropriately -- 🚫 FORBIDDEN to modify content completed in previous steps -- 📖 Only reload documents that were already tracked in `inputDocuments` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis of current state before taking action -- Update frontmatter: add this step name to the end of the steps completed array -- 📖 Only load documents that were already tracked in `inputDocuments` -- 🚫 FORBIDDEN to discover new input documents during continuation - -## CONTEXT BOUNDARIES: - -- Available context: Current document and frontmatter are already loaded -- Focus: Workflow state analysis and continuation logic only -- Limits: Don't assume knowledge beyond what's in the document -- Dependencies: Existing workflow state from previous session - -## Sequence of Instructions (Do not deviate, skip, or optimize) - -### 1. Analyze Current State - -**State Assessment:** -Review the frontmatter to understand: - -- `stepsCompleted`: Array of completed step filenames -- Last element of `stepsCompleted` array: The most recently completed step -- `inputDocuments`: What context was already loaded -- All other frontmatter variables - -### 2. Restore Context Documents - -**Context Reloading:** - -- For each document in `inputDocuments`, load the complete file -- This ensures you have full context for continuation -- Don't discover new documents - only reload what was previously processed - -### 3. Determine Next Step - -**Simplified Next Step Logic:** -1. Get the last element from the `stepsCompleted` array (this is the filename of the last completed step, e.g., "step-03-success.md") -2. Load that step file and read its frontmatter -3. Extract the `nextStepFile` value from the frontmatter -4. That's the next step to load! - -**Example:** -- If `stepsCompleted = ["step-01-init.md", "step-02-discovery.md", "step-03-success.md"]` -- Last element is `"step-03-success.md"` -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-03-success.md`, read its frontmatter -- Read fully and follow: `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md` - -### 4. Handle Workflow Completion - -**If `stepsCompleted` array contains `"step-11-complete.md"`:** -"Great news! It looks like we've already completed the PRD workflow for {{project_name}}. - -The final document is ready at `{outputFile}` with all sections completed. - -Would you like me to: - -- Review the completed PRD with you -- Suggest next workflow steps (like architecture or epic creation) -- Start a new PRD revision - -What would be most helpful?" - -### 5. Present Current Progress - -**If workflow not complete:** -"Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}. - -**Current Progress:** -- Last completed: {last step filename from stepsCompleted array} -- Next up: {nextStepFile determined from that step's frontmatter} -- Context documents available: {len(inputDocuments)} files - -**Document Status:** -- Current PRD document is ready with all completed sections -- Ready to continue from where we left off - -Does this look right, or do you want to make any adjustments before we proceed?" - -### 6. Present MENU OPTIONS - -Display: "**Select an Option:** [C] Continue to {next step name}" - -#### Menu Handling Logic: - -- IF C: Read fully and follow the {nextStepFile} determined in step 3 -- IF Any other comments or queries: respond and redisplay menu - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [current state confirmed], will you then read fully and follow: {nextStepFile} to resume the workflow. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All previous input documents successfully reloaded -- Current workflow state accurately analyzed and presented -- User confirms understanding of progress before continuation -- Correct next step identified and prepared for loading - -### ❌ SYSTEM FAILURE: - -- Discovering new input documents instead of reloading existing ones -- Modifying content from already completed steps -- Failing to extract nextStepFile from the last completed step's frontmatter -- Proceeding without user confirmation of current state - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02-discovery.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02-discovery.md deleted file mode 100644 index 7d337b47d..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02-discovery.md +++ /dev/null @@ -1,224 +0,0 @@ ---- -name: 'step-02-discovery' -description: 'Discover project type, domain, and context through collaborative dialogue' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02b-vision.md' -outputFile: '{planning_artifacts}/prd.md' - -# Data Files -projectTypesCSV: '../data/project-types.csv' -domainComplexityCSV: '../data/domain-complexity.csv' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 2: Project Discovery - -**Progress: Step 2 of 13** - Next: Product Vision - -## STEP GOAL: - -Discover and classify the project - understand what type of product this is, what domain it operates in, and the project context (greenfield vs brownfield). - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read -- ✅ ALWAYS treat this as collaborative discovery between PM peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused PM facilitator collaborating with an expert peer -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision - -### Step-Specific Rules: - -- 🎯 Focus on classification and understanding - no content generation yet -- 🚫 FORBIDDEN to generate executive summary or vision statements (that's next steps) -- 💬 APPROACH: Natural conversation to understand the project -- 🎯 LOAD classification data BEFORE starting discovery conversation - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after classification complete -- 💾 ONLY save classification to frontmatter when user chooses C (Continue) -- 📖 Update frontmatter, adding this step to the end of the list of stepsCompleted -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from step 1 are available -- Input documents already loaded are in memory (product briefs, research, brainstorming, project docs) -- **Document counts available in frontmatter `documentCounts`** -- Classification CSV data will be loaded in this step only -- No executive summary or vision content yet (that's steps 2b and 2c) - -## YOUR TASK: - -Discover and classify the project through natural conversation: -- What type of product is this? (web app, API, mobile, etc.) -- What domain does it operate in? (healthcare, fintech, e-commerce, etc.) -- What's the project context? (greenfield new product vs brownfield existing system) -- How complex is this domain? (low, medium, high) - -## DISCOVERY SEQUENCE: - -### 1. Check Document State - -Read the frontmatter from `{outputFile}` to get document counts: -- `briefCount` - Product briefs available -- `researchCount` - Research documents available -- `brainstormingCount` - Brainstorming docs available -- `projectDocsCount` - Existing project documentation - -**Announce your understanding:** - -"From step 1, I have loaded: -- Product briefs: {{briefCount}} -- Research: {{researchCount}} -- Brainstorming: {{brainstormingCount}} -- Project docs: {{projectDocsCount}} - -{{if projectDocsCount > 0}}This is a brownfield project - I'll focus on understanding what you want to add or change.{{else}}This is a greenfield project - I'll help you define the full product vision.{{/if}}" - -### 2. Load Classification Data - -**Attempt subprocess data lookup:** - -**Project Type Lookup:** -"Your task: Lookup data in {projectTypesCSV} - -**Search criteria:** -- Find row where project_type matches {{detectedProjectType}} - -**Return format:** -Return ONLY the matching row as a YAML-formatted object with these fields: -project_type, detection_signals - -**Do NOT return the entire CSV - only the matching row.**" - -**Domain Complexity Lookup:** -"Your task: Lookup data in {domainComplexityCSV} - -**Search criteria:** -- Find row where domain matches {{detectedDomain}} - -**Return format:** -Return ONLY the matching row as a YAML-formatted object with these fields: -domain, complexity, typical_concerns, compliance_requirements - -**Do NOT return the entire CSV - only the matching row.**" - -**Graceful degradation (if Task tool unavailable):** -- Load the CSV files directly -- Find the matching rows manually -- Extract required fields -- Keep in memory for intelligent classification - -### 3. Begin Discovery Conversation - -**Start with what you know:** - -If the user has a product brief or project docs, acknowledge them and share your understanding. Then ask clarifying questions to deepen your understanding. - -If this is a greenfield project with no docs, start with open-ended discovery: -- What problem does this solve? -- Who's it for? -- What excites you about building this? - -**Listen for classification signals:** - -As the user describes their product, match against: -- **Project type signals** (API, mobile, SaaS, etc.) -- **Domain signals** (healthcare, fintech, education, etc.) -- **Complexity indicators** (regulated industries, novel technology, etc.) - -### 4. Confirm Classification - -Once you have enough understanding, share your classification: - -"I'm hearing this as: -- **Project Type:** {{detectedType}} -- **Domain:** {{detectedDomain}} -- **Complexity:** {{complexityLevel}} - -Does this sound right to you?" - -Let the user confirm or refine your classification. - -### 5. Save Classification to Frontmatter - -When user selects 'C', update frontmatter with classification: -```yaml -classification: - projectType: {{projectType}} - domain: {{domain}} - complexity: {{complexityLevel}} - projectContext: {{greenfield|brownfield}} -``` - -### N. Present MENU OPTIONS - -Present the project classification for review, then display menu: - -"Based on our conversation, I've discovered and classified your project. - -**Here's the classification:** - -**Project Type:** {{detectedType}} -**Domain:** {{detectedDomain}} -**Complexity:** {{complexityLevel}} -**Project Context:** {{greenfield|brownfield}} - -**What would you like to do?**" - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Product Vision (Step 2b of 13)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask} with the current classification, process the enhanced insights that come back, ask user if they accept the improvements, if yes update classification then redisplay menu, if no keep original classification then redisplay menu -- IF P: Read fully and follow: {partyModeWorkflow} with the current classification, process the collaborative insights, ask user if they accept the changes, if yes update classification then redisplay menu, if no keep original classification then redisplay menu -- IF C: Save classification to {outputFile} frontmatter, add this step name to the end of stepsCompleted array, then read fully and follow: {nextStepFile} -- IF Any other: help user respond, then redisplay menu - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [classification saved to frontmatter], will you then read fully and follow: `{nextStepFile}` to explore product vision. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Document state checked and announced to user -- Classification data loaded and used intelligently -- Natural conversation to understand project type, domain, complexity -- Classification validated with user before saving -- Frontmatter updated with classification when C selected -- User's existing documents acknowledged and built upon - -### ❌ SYSTEM FAILURE: - -- Not reading documentCounts from frontmatter first -- Skipping classification data loading -- Generating executive summary or vision content (that's later steps!) -- Not validating classification with user -- Being prescriptive instead of having natural conversation -- Proceeding without user selecting 'C' - -**Master Rule:** This is classification and understanding only. No content generation yet. Build on what the user already has. Have natural conversations, don't follow scripts. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02b-vision.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02b-vision.md deleted file mode 100644 index 9b7b2a975..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02b-vision.md +++ /dev/null @@ -1,154 +0,0 @@ ---- -name: 'step-02b-vision' -description: 'Discover the product vision and differentiator through collaborative dialogue' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02c-executive-summary.md' -outputFile: '{planning_artifacts}/prd.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 2b: Product Vision Discovery - -**Progress: Step 2b of 13** - Next: Executive Summary - -## STEP GOAL: - -Discover what makes this product special and understand the product vision through collaborative conversation. No content generation — facilitation only. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read -- ✅ ALWAYS treat this as collaborative discovery between PM peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused PM facilitator collaborating with an expert peer -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision - -### Step-Specific Rules: - -- 🎯 Focus on discovering vision and differentiator — no content generation yet -- 🚫 FORBIDDEN to generate executive summary content (that's the next step) -- 🚫 FORBIDDEN to append anything to the document in this step -- 💬 APPROACH: Natural conversation to understand what makes this product special -- 🎯 BUILD ON classification insights from step 2 - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after vision discovery is complete -- 📖 Update frontmatter, adding this step to the end of the list of stepsCompleted -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from steps 1 and 2 are available -- Project classification exists from step 2 (project type, domain, complexity, context) -- Input documents already loaded are in memory (product briefs, research, brainstorming, project docs) -- No executive summary content yet (that's step 2c) -- This step ONLY discovers — it does NOT write to the document - -## YOUR TASK: - -Discover the product vision and differentiator through natural conversation. Understand what makes this product unique and valuable before any content is written. - -## VISION DISCOVERY SEQUENCE: - -### 1. Acknowledge Classification Context - -Reference the classification from step 2 and use it to frame the vision conversation: - -"We've established this is a {{projectType}} in the {{domain}} domain with {{complexityLevel}} complexity. Now let's explore what makes this product special." - -### 2. Explore What Makes It Special - -Guide the conversation to uncover the product's unique value: - -- **User delight:** "What would make users say 'this is exactly what I needed'?" -- **Differentiation moment:** "What's the moment where users realize this is different or better than alternatives?" -- **Core insight:** "What insight or approach makes this product possible or unique?" -- **Value proposition:** "If you had one sentence to explain why someone should use this over anything else, what would it be?" - -### 3. Understand the Vision - -Dig deeper into the product vision: - -- **Problem framing:** "What's the real problem you're solving — not the surface symptom, but the deeper need?" -- **Future state:** "When this product is successful, what does the world look like for your users?" -- **Why now:** "Why is this the right time to build this?" - -### 4. Validate Understanding - -Reflect back what you've heard and confirm: - -"Here's what I'm hearing about your vision and differentiator: - -**Vision:** {{summarized_vision}} -**What Makes It Special:** {{summarized_differentiator}} -**Core Insight:** {{summarized_insight}} - -Does this capture it? Anything I'm missing?" - -Let the user confirm or refine your understanding. - -### N. Present MENU OPTIONS - -Present your understanding of the product vision for review, then display menu: - -"Based on our conversation, I have a clear picture of your product vision and what makes it special. I'll use these insights to draft the Executive Summary in the next step. - -**What would you like to do?**" - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Executive Summary (Step 2c of 13)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask} with the current vision insights, process the enhanced insights that come back, ask user if they accept the improvements, if yes update understanding then redisplay menu, if no keep original understanding then redisplay menu -- IF P: Read fully and follow: {partyModeWorkflow} with the current vision insights, process the collaborative insights, ask user if they accept the changes, if yes update understanding then redisplay menu, if no keep original understanding then redisplay menu -- IF C: Update {outputFile} frontmatter by adding this step name to the end of stepsCompleted array, then read fully and follow: {nextStepFile} -- IF Any other: help user respond, then redisplay menu - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [stepsCompleted updated], will you then read fully and follow: `{nextStepFile}` to generate the Executive Summary. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Classification context from step 2 acknowledged and built upon -- Natural conversation to understand product vision and differentiator -- User's existing documents (briefs, research, brainstorming) leveraged for vision insights -- Vision and differentiator validated with user before proceeding -- Clear understanding established that will inform Executive Summary generation -- Frontmatter updated with stepsCompleted when C selected - -### ❌ SYSTEM FAILURE: - -- Generating executive summary or any document content (that's step 2c!) -- Appending anything to the PRD document -- Not building on classification from step 2 -- Being prescriptive instead of having natural conversation -- Proceeding without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file - -**Master Rule:** This step is vision discovery only. No content generation, no document writing. Have natural conversations, build on what you know from classification, and establish the vision that will feed into the Executive Summary. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02c-executive-summary.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02c-executive-summary.md deleted file mode 100644 index 3f024decd..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02c-executive-summary.md +++ /dev/null @@ -1,170 +0,0 @@ ---- -name: 'step-02c-executive-summary' -description: 'Generate and append the Executive Summary section to the PRD document' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-03-success.md' -outputFile: '{planning_artifacts}/prd.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 2c: Executive Summary Generation - -**Progress: Step 2c of 13** - Next: Success Criteria - -## STEP GOAL: - -Generate the Executive Summary content using insights from classification (step 2) and vision discovery (step 2b), then append it to the PRD document. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read -- ✅ ALWAYS treat this as collaborative discovery between PM peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused PM facilitator collaborating with an expert peer -- ✅ We engage in collaborative dialogue, not command-response -- ✅ Content is drafted collaboratively — present for review before saving - -### Step-Specific Rules: - -- 🎯 Generate Executive Summary content based on discovered insights -- 💬 Present draft content for user review and refinement before appending -- 🚫 FORBIDDEN to append content without user approval via 'C' -- 🎯 Content must be dense, precise, and zero-fluff (PRD quality standards) - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating executive summary content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from steps 1, 2, and 2b are available -- Project classification exists from step 2 (project type, domain, complexity, context) -- Vision and differentiator insights exist from step 2b -- Input documents from step 1 are available (product briefs, research, brainstorming, project docs) -- This step generates and appends the first substantive content to the PRD - -## YOUR TASK: - -Draft the Executive Summary section using all discovered insights, present it for user review, and append it to the PRD document when approved. - -## EXECUTIVE SUMMARY GENERATION SEQUENCE: - -### 1. Synthesize Available Context - -Review all available context before drafting: -- Classification from step 2: project type, domain, complexity, project context -- Vision and differentiator from step 2b: what makes this special, core insight -- Input documents: product briefs, research, brainstorming, project docs - -### 2. Draft Executive Summary Content - -Generate the Executive Summary section using the content structure below. Apply PRD quality standards: -- High information density — every sentence carries weight -- Zero fluff — no filler phrases or vague language -- Precise and actionable — clear, specific statements -- Dual-audience optimized — readable by humans, consumable by LLMs - -### 3. Present Draft for Review - -Present the drafted content to the user for review: - -"Here's the Executive Summary I've drafted based on our discovery work. Please review and let me know if you'd like any changes:" - -Show the full drafted content using the structure from the Content Structure section below. - -Allow the user to: -- Request specific changes to any section -- Add missing information -- Refine the language or emphasis -- Approve as-is - -### N. Present MENU OPTIONS - -Present the executive summary content for user review, then display menu: - -"Here's the Executive Summary for your PRD. Review the content above and let me know what you'd like to do." - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Success Criteria (Step 3 of 13)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask} with the current executive summary content, process the enhanced content that comes back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu -- IF P: Read fully and follow: {partyModeWorkflow} with the current executive summary content, process the collaborative improvements, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu -- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile} -- IF Any other: help user respond, then redisplay menu - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## APPEND TO DOCUMENT: - -When user selects 'C', append the following content structure directly to the document: - -```markdown -## Executive Summary - -{vision_alignment_content} - -### What Makes This Special - -{product_differentiator_content} - -## Project Classification - -{project_classification_content} -``` - -Where: -- `{vision_alignment_content}` — Product vision, target users, and the problem being solved. Dense, precise summary drawn from step 2b vision discovery. -- `{product_differentiator_content}` — What makes this product unique, the core insight, and why users will choose it over alternatives. Drawn from step 2b differentiator discovery. -- `{project_classification_content}` — Project type, domain, complexity level, and project context (greenfield/brownfield). Drawn from step 2 classification. - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [content appended to document], will you then read fully and follow: `{nextStepFile}` to define success criteria. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Executive Summary drafted using insights from steps 2 and 2b -- Content meets PRD quality standards (dense, precise, zero-fluff) -- Draft presented to user for review before saving -- User given opportunity to refine content -- Content properly appended to document when C selected -- A/P/C menu presented and handled correctly -- Frontmatter updated with stepsCompleted when C selected - -### ❌ SYSTEM FAILURE: - -- Generating content without incorporating discovered vision and classification -- Appending content without user selecting 'C' -- Producing vague, fluffy, or low-density content -- Not presenting draft for user review -- Not presenting A/P/C menu after content generation -- Skipping directly to next step without appending content - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -**Master Rule:** Generate high-quality Executive Summary content from discovered insights. Present for review, refine collaboratively, and only save when the user approves. This is the first substantive content in the PRD — it sets the quality bar for everything that follows. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-03-success.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-03-success.md deleted file mode 100644 index 79722289a..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-03-success.md +++ /dev/null @@ -1,226 +0,0 @@ ---- -name: 'step-03-success' -description: 'Define comprehensive success criteria covering user, business, and technical success' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md' -outputFile: '{planning_artifacts}/prd.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 3: Success Criteria Definition - -**Progress: Step 3 of 11** - Next: User Journey Mapping - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between PM peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on defining what winning looks like for this product -- 🎯 COLLABORATIVE discovery, not assumption-based goal setting -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating success criteria content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Executive Summary and Project Classification already exist in document -- Input documents from step-01 are available (product briefs, research, brainstorming) -- No additional data files needed for this step -- Focus on measurable, specific success criteria -- LEVERAGE existing input documents to inform success criteria - -## YOUR TASK: - -Define comprehensive success criteria that cover user success, business success, and technical success, using input documents as a foundation while allowing user refinement. - -## SUCCESS DISCOVERY SEQUENCE: - -### 1. Begin Success Definition Conversation - -**Check Input Documents for Success Indicators:** -Analyze product brief, research, and brainstorming documents for success criteria already mentioned. - -**If Input Documents Contain Success Criteria:** -Guide user to refine existing success criteria: -- Acknowledge what's already documented in their materials -- Extract key success themes from brief, research, and brainstorming -- Help user identify gaps and areas for expansion -- Probe for specific, measurable outcomes: When do users feel delighted/relieved/empowered? -- Ask about emotional success moments and completion scenarios -- Explore what "worth it" means beyond what's already captured - -**If No Success Criteria in Input Documents:** -Start with user-centered success exploration: -- Guide conversation toward defining what "worth it" means for users -- Ask about the moment users realize their problem is solved -- Explore specific user outcomes and emotional states -- Identify success "aha!" moments and completion scenarios -- Focus on user experience of success first - -### 2. Explore User Success Metrics - -Listen for specific user outcomes and help make them measurable: - -- Guide from vague to specific: NOT "users are happy" → "users complete [key action] within [timeframe]" -- Ask about emotional success: "When do they feel delighted/relieved/empowered?" -- Identify success moments: "What's the 'aha!' moment?" -- Define completion scenarios: "What does 'done' look like for the user?" - -### 3. Define Business Success - -Transition to business metrics: -- Guide conversation to business perspective on success -- Explore timelines: What does 3-month success look like? 12-month success? -- Identify key business metrics: revenue, user growth, engagement, or other measures? -- Ask what specific metric would indicate "this is working" -- Understand business success from their perspective - -### 4. Challenge Vague Metrics - -Push for specificity on business metrics: - -- "10,000 users" → "What kind of users? Doing what?" -- "99.9% uptime" → "What's the real concern - data loss? Failed payments?" -- "Fast" → "How fast, and what specifically needs to be fast?" -- "Good adoption" → "What percentage adoption by when?" - -### 5. Connect to Product Differentiator - -Tie success metrics back to what makes the product special: -- Connect success criteria to the product's unique differentiator -- Ensure metrics reflect the specific value proposition -- Adapt success criteria to domain context: - - Consumer: User love, engagement, retention - - B2B: ROI, efficiency, adoption - - Developer tools: Developer experience, community - - Regulated: Compliance, safety, validation - - GovTech: Government compliance, accessibility, procurement - -### 6. Smart Scope Negotiation - -Guide scope definition through success lens: -- Help user distinguish MVP (must work to be useful) from growth (competitive) and vision (dream) -- Guide conversation through three scope levels: - 1. MVP: What's essential for proving the concept? - 2. Growth: What makes it competitive? - 3. Vision: What's the dream version? -- Challenge scope creep conversationally: Could this wait until after launch? Is this essential for MVP? -- For complex domains: Ensure compliance minimums are included in MVP - -### 7. Generate Success Criteria Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Success Criteria - -### User Success - -[Content about user success criteria based on conversation] - -### Business Success - -[Content about business success metrics based on conversation] - -### Technical Success - -[Content about technical success requirements based on conversation] - -### Measurable Outcomes - -[Content about specific measurable outcomes based on conversation] - -## Product Scope - -### MVP - Minimum Viable Product - -[Content about MVP scope based on conversation] - -### Growth Features (Post-MVP) - -[Content about growth features based on conversation] - -### Vision (Future) - -[Content about future vision based on conversation] -``` - -### 8. Present MENU OPTIONS - -Present the success criteria content for user review, then display menu: - -- Show the drafted success criteria and scope definition (using structure from section 7) -- Ask if they'd like to refine further, get other perspectives, or proceed -- Present menu options naturally as part of the conversation - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to User Journey Mapping (Step 4 of 11)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask} with the current success criteria content, process the enhanced success metrics that come back, ask user "Accept these improvements to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu -- IF P: Read fully and follow: {partyModeWorkflow} with the current success criteria, process the collaborative improvements to metrics and scope, ask user "Accept these changes to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu -- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile} -- IF Any other: help user respond, then redisplay menu - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 7. - -## SUCCESS METRICS: - -✅ User success criteria clearly identified and made measurable -✅ Business success metrics defined with specific targets -✅ Success criteria connected to product differentiator -✅ Scope properly negotiated (MVP, Growth, Vision) -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Accepting vague success metrics without pushing for specificity -❌ Not connecting success criteria back to product differentiator -❌ Missing scope negotiation and leaving it undefined -❌ Generating content without real user input on what success looks like -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## DOMAIN CONSIDERATIONS: - -If working in regulated domains (healthcare, fintech, govtech): - -- Include compliance milestones in success criteria -- Add regulatory approval timelines to MVP scope -- Consider audit requirements as technical success metrics - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md` to map user journeys. - -Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md deleted file mode 100644 index fc919ff07..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md +++ /dev/null @@ -1,213 +0,0 @@ ---- -name: 'step-04-journeys' -description: 'Map ALL user types that interact with the system with narrative story-based journeys' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-05-domain.md' -outputFile: '{planning_artifacts}/prd.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 4: User Journey Mapping - -**Progress: Step 4 of 11** - Next: Domain Requirements - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between PM peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on mapping ALL user types that interact with the system -- 🎯 CRITICAL: No journey = no functional requirements = product doesn't exist -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating journey content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Success criteria and scope already defined -- Input documents from step-01 are available (product briefs with user personas) -- Every human interaction with the system needs a journey - -## YOUR TASK: - -Create compelling narrative user journeys that leverage existing personas from product briefs and identify additional user types needed for comprehensive coverage. - -## JOURNEY MAPPING SEQUENCE: - -### 1. Leverage Existing Users & Identify Additional Types - -**Check Input Documents for Existing Personas:** -Analyze product brief, research, and brainstorming documents for user personas already defined. - -**If User Personas Exist in Input Documents:** -Guide user to build on existing personas: -- Acknowledge personas found in their product brief -- Extract key persona details and backstories -- Leverage existing insights about their needs -- Prompt to identify additional user types beyond those documented -- Suggest additional user types based on product context (admins, moderators, support, API consumers, internal ops) -- Ask what additional user types should be considered - -**If No Personas in Input Documents:** -Start with comprehensive user type discovery: -- Guide exploration of ALL people who interact with the system -- Consider beyond primary users: admins, moderators, support staff, API consumers, internal ops -- Ask what user types should be mapped for this specific product -- Ensure comprehensive coverage of all system interactions - -### 2. Create Narrative Story-Based Journeys - -For each user type, create compelling narrative journeys that tell their story: - -#### Narrative Journey Creation Process: - -**If Using Existing Persona from Input Documents:** -Guide narrative journey creation: -- Use persona's existing backstory from brief -- Explore how the product changes their life/situation -- Craft journey narrative: where do we meet them, how does product help them write their next chapter? - -**If Creating New Persona:** -Guide persona creation with story framework: -- Name: realistic name and personality -- Situation: What's happening in their life/work that creates need? -- Goal: What do they desperately want to achieve? -- Obstacle: What's standing in their way? -- Solution: How does the product solve their story? - -**Story-Based Journey Mapping:** - -Guide narrative journey creation using story structure: -- **Opening Scene**: Where/how do we meet them? What's their current pain? -- **Rising Action**: What steps do they take? What do they discover? -- **Climax**: Critical moment where product delivers real value -- **Resolution**: How does their situation improve? What's their new reality? - -Encourage narrative format with specific user details, emotional journey, and clear before/after contrast - -### 3. Guide Journey Exploration - -For each journey, facilitate detailed exploration: -- What happens at each step specifically? -- What could go wrong? What's the recovery path? -- What information do they need to see/hear? -- What's their emotional state at each point? -- Where does this journey succeed or fail? - -### 4. Connect Journeys to Requirements - -After each journey, explicitly state: -- This journey reveals requirements for specific capability areas -- Help user see how different journeys create different feature sets -- Connect journey needs to concrete capabilities (onboarding, dashboards, notifications, etc.) - -### 5. Aim for Comprehensive Coverage - -Guide toward complete journey set: - -- **Primary user** - happy path (core experience) -- **Primary user** - edge case (different goal, error recovery) -- **Secondary user** (admin, moderator, support, etc.) -- **API consumer** (if applicable) - -Ask if additional journeys are needed to cover uncovered user types - -### 6. Generate User Journey Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## User Journeys - -[All journey narratives based on conversation] - -### Journey Requirements Summary - -[Summary of capabilities revealed by journeys based on conversation] -``` - -### 7. Present MENU OPTIONS - -Present the user journey content for review, then display menu: -- Show the mapped user journeys (using structure from section 6) -- Highlight how each journey reveals different capabilities -- Ask if they'd like to refine further, get other perspectives, or proceed -- Present menu options naturally as part of conversation - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Domain Requirements (Step 5 of 11)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask} with the current journey content, process the enhanced journey insights that come back, ask user "Accept these improvements to the user journeys? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu -- IF P: Read fully and follow: {partyModeWorkflow} with the current journeys, process the collaborative journey improvements and additions, ask user "Accept these changes to the user journeys? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu -- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile} -- IF Any other: help user respond, then redisplay menu - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Existing personas from product briefs leveraged when available -✅ All user types identified (not just primary users) -✅ Rich narrative storytelling for each persona and journey -✅ Complete story-based journey mapping with emotional arc -✅ Journey requirements clearly connected to capabilities needed -✅ Minimum 3-4 compelling narrative journeys covering different user types -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Ignoring existing personas from product briefs -❌ Only mapping primary user journeys and missing secondary users -❌ Creating generic journeys without rich persona details and narrative -❌ Missing emotional storytelling elements that make journeys compelling -❌ Missing critical decision points and failure scenarios -❌ Not connecting journeys to required capabilities -❌ Not having enough journey diversity (admin, support, API, etc.) -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## JOURNEY TYPES TO ENSURE: - -**Minimum Coverage:** - -1. **Primary User - Success Path**: Core experience journey -2. **Primary User - Edge Case**: Error recovery, alternative goals -3. **Admin/Operations User**: Management, configuration, monitoring -4. **Support/Troubleshooting**: Help, investigation, issue resolution -5. **API/Integration** (if applicable): Developer/technical user journey - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-05-domain.md`. - -Remember: Do NOT proceed to step-05 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-05-domain.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-05-domain.md deleted file mode 100644 index bb95ea16f..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-05-domain.md +++ /dev/null @@ -1,207 +0,0 @@ ---- -name: 'step-05-domain' -description: 'Explore domain-specific requirements for complex domains (optional step)' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-06-innovation.md' -outputFile: '{planning_artifacts}/prd.md' -domainComplexityCSV: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/domain-complexity.csv' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 5: Domain-Specific Requirements (Optional) - -**Progress: Step 5 of 13** - Next: Innovation Focus - -## STEP GOAL: - -For complex domains only that have a mapping in {domainComplexityCSV}, explore domain-specific constraints, compliance requirements, and technical considerations that shape the product. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read -- ✅ ALWAYS treat this as collaborative discovery between PM peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product-focused PM facilitator collaborating with an expert peer -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise - -### Step-Specific Rules: - -- 🎯 This step is OPTIONAL - only needed for complex domains -- 🚫 SKIP if domain complexity is "low" from step-02 -- 💬 APPROACH: Natural conversation to discover domain-specific needs -- 🎯 Focus on constraints, compliance, and domain patterns - -## EXECUTION PROTOCOLS: - -- 🎯 Check domain complexity from step-02 classification first -- ⚠️ If complexity is "low", offer to skip this step -- ⚠️ Present A/P/C menu after domain requirements defined (or skipped) -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Domain classification from step-02 is available -- If complexity is low, this step may be skipped -- Domain CSV data provides complexity reference -- Focus on domain-specific constraints, not general requirements - -## YOUR TASK: - -For complex domains, explore what makes this domain special: -- **Compliance requirements** - regulations, standards, certifications -- **Technical constraints** - security, privacy, integration requirements -- **Domain patterns** - common patterns, best practices, anti-patterns -- **Risks and mitigations** - what could go wrong, how to prevent it - -## DOMAIN DISCOVERY SEQUENCE: - -### 1. Check Domain Complexity - -**Review classification from step-02:** - -- What's the domain complexity level? (low/medium/high) -- What's the specific domain? (healthcare, fintech, education, etc.) - -**If complexity is LOW:** - -Offer to skip: -"The domain complexity from our discovery is low. We may not need deep domain-specific requirements. Would you like to: -- [C] Skip this step and move to Innovation -- [D] Do domain exploration anyway" - -**If complexity is MEDIUM or HIGH:** - -Proceed with domain exploration. - -### 2. Load Domain Reference Data - -**Attempt subprocess data lookup:** - -"Your task: Lookup data in {domainComplexityCSV} - -**Search criteria:** -- Find row where domain matches {{domainFromStep02}} - -**Return format:** -Return ONLY the matching row as a YAML-formatted object with these fields: -domain, complexity, typical_concerns, compliance_requirements - -**Do NOT return the entire CSV - only the matching row.**" - -**Graceful degradation (if Task tool unavailable):** -- Load the CSV file directly -- Find the matching row manually -- Extract required fields -- Understand typical concerns and compliance requirements - -### 3. Explore Domain-Specific Concerns - -**Start with what you know:** - -Acknowledge the domain and explore what makes it complex: -- What regulations apply? (HIPAA, PCI-DSS, GDPR, SOX, etc.) -- What standards matter? (ISO, NIST, domain-specific standards) -- What certifications are needed? (security, privacy, domain-specific) -- What integrations are required? (EMR systems, payment processors, etc.) - -**Explore technical constraints:** -- Security requirements (encryption, audit logs, access control) -- Privacy requirements (data handling, consent, retention) -- Performance requirements (real-time, batch, latency) -- Availability requirements (uptime, disaster recovery) - -### 4. Document Domain Requirements - -**Structure the requirements around key concerns:** - -```markdown -### Compliance & Regulatory -- [Specific requirements] - -### Technical Constraints -- [Security, privacy, performance needs] - -### Integration Requirements -- [Required systems and data flows] - -### Risk Mitigations -- [Domain-specific risks and how to address them] -``` - -### 5. Validate Completeness - -**Check with the user:** - -"Are there other domain-specific concerns we should consider? For [this domain], what typically gets overlooked?" - -### N. Present MENU OPTIONS - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue - Save and Proceed to Innovation (Step 6 of 13)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask}, and when finished redisplay the menu -- IF P: Read fully and follow: {partyModeWorkflow}, and when finished redisplay the menu -- IF C: Save content to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile} -- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#n-present-menu-options) - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## APPEND TO DOCUMENT - -When user selects 'C', append to `{outputFile}`: - -```markdown -## Domain-Specific Requirements - -{{discovered domain requirements}} -``` - -If step was skipped, append nothing and proceed. - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [content saved or skipped], will you then read fully and follow: `{nextStepFile}` to explore innovation. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Domain complexity checked before proceeding -- Offered to skip if complexity is low -- Natural conversation exploring domain concerns -- Compliance, technical, and integration requirements identified -- Domain-specific risks documented with mitigations -- User validated completeness -- Content properly saved (or step skipped) when C selected - -### ❌ SYSTEM FAILURE: - -- Not checking domain complexity first -- Not offering to skip for low-complexity domains -- Missing critical compliance requirements -- Not exploring technical constraints -- Not asking about domain-specific risks -- Being generic instead of domain-specific -- Proceeding without user validation - -**Master Rule:** This step is OPTIONAL for simple domains. For complex domains, focus on compliance, constraints, and domain patterns. Natural conversation, not checklists. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-06-innovation.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-06-innovation.md deleted file mode 100644 index 708eac7b1..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-06-innovation.md +++ /dev/null @@ -1,226 +0,0 @@ ---- -name: 'step-06-innovation' -description: 'Detect and explore innovative aspects of the product (optional step)' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-07-project-type.md' -outputFile: '{planning_artifacts}/prd.md' - -# Data Files -projectTypesCSV: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/project-types.csv' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 6: Innovation Discovery - -**Progress: Step 6 of 11** - Next: Project Type Analysis - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between PM peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on detecting and exploring innovative aspects of the product -- 🎯 OPTIONAL STEP: Only proceed if innovation signals are detected -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating innovation content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Project type from step-02 is available for innovation signal matching -- Project-type CSV data will be loaded in this step -- Focus on detecting genuine innovation, not forced creativity - -## OPTIONAL STEP CHECK: - -Before proceeding with this step, scan for innovation signals: - -- Listen for language like "nothing like this exists", "rethinking how X works" -- Check for project-type innovation signals from CSV -- Look for novel approaches or unique combinations -- If no innovation detected, skip this step - -## YOUR TASK: - -Detect and explore innovation patterns in the product, focusing on what makes it truly novel and how to validate the innovative aspects. - -## INNOVATION DISCOVERY SEQUENCE: - -### 1. Load Project-Type Innovation Data - -Load innovation signals specific to this project type: - -- Load `{projectTypesCSV}` completely -- Find the row where `project_type` matches detected type from step-02 -- Extract `innovation_signals` (semicolon-separated list) -- Extract `web_search_triggers` for potential innovation research - -### 2. Listen for Innovation Indicators - -Monitor conversation for both general and project-type-specific innovation signals: - -#### General Innovation Language: - -- "Nothing like this exists" -- "We're rethinking how [X] works" -- "Combining [A] with [B] for the first time" -- "Novel approach to [problem]" -- "No one has done [concept] before" - -#### Project-Type-Specific Signals (from CSV): - -Match user descriptions against innovation_signals for their project_type: - -- **api_backend**: "API composition;New protocol" -- **mobile_app**: "Gesture innovation;AR/VR features" -- **saas_b2b**: "Workflow automation;AI agents" -- **developer_tool**: "New paradigm;DSL creation" - -### 3. Initial Innovation Screening - -Ask targeted innovation discovery questions: -- Guide exploration of what makes the product innovative -- Explore if they're challenging existing assumptions -- Ask about novel combinations of technologies/approaches -- Identify what hasn't been done before -- Understand which aspects feel most innovative - -### 4. Deep Innovation Exploration (If Detected) - -If innovation signals are found, explore deeply: - -#### Innovation Discovery Questions: -- What makes it unique compared to existing solutions? -- What assumption are you challenging? -- How do we validate it works? -- What's the fallback if it doesn't? -- Has anyone tried this before? - -#### Market Context Research: - -If relevant innovation detected, consider web search for context: -Use `web_search_triggers` from project-type CSV: -`[web_search_triggers] {concept} innovations {date}` - -### 5. Generate Innovation Content (If Innovation Detected) - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Innovation & Novel Patterns - -### Detected Innovation Areas - -[Innovation patterns identified based on conversation] - -### Market Context & Competitive Landscape - -[Market context and research based on conversation] - -### Validation Approach - -[Validation methodology based on conversation] - -### Risk Mitigation - -[Innovation risks and fallbacks based on conversation] -``` - -### 6. Present MENU OPTIONS (Only if Innovation Detected) - -Present the innovation content for review, then display menu: -- Show identified innovative aspects (using structure from section 5) -- Highlight differentiation from existing solutions -- Ask if they'd like to refine further, get other perspectives, or proceed -- Present menu options naturally as part of conversation - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Project Type Analysis (Step 7 of 11)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask} with the current innovation content, process the enhanced innovation insights that come back, ask user "Accept these improvements to the innovation analysis? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu -- IF P: Read fully and follow: {partyModeWorkflow} with the current innovation content, process the collaborative innovation exploration and ideation, ask user "Accept these changes to the innovation analysis? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu -- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile} -- IF Any other: help user respond, then redisplay menu - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## NO INNOVATION DETECTED: - -If no genuine innovation signals are found after exploration: -- Acknowledge that no clear innovation signals were found -- Note this is fine - many successful products are excellent executions of existing concepts -- Ask if they'd like to try finding innovative angles or proceed - -Display: "**Select:** [A] Advanced Elicitation - Let's try to find innovative angles [C] Continue - Skip innovation section and move to Project Type Analysis (Step 7 of 11)" - -### Menu Handling Logic: -- IF A: Proceed with content generation anyway, then return to menu -- IF C: Skip this step, then read fully and follow: {nextStepFile} - -### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 5. - -## SUCCESS METRICS: - -✅ Innovation signals properly detected from user conversation -✅ Project-type innovation signals used to guide discovery -✅ Genuine innovation explored (not forced creativity) -✅ Validation approach clearly defined for innovative aspects -✅ Risk mitigation strategies identified -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Forced innovation when none genuinely exists -❌ Not using project-type innovation signals from CSV -❌ Missing market context research for novel concepts -❌ Not addressing validation approach for innovative features -❌ Creating innovation theater without real innovative aspects -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## SKIP CONDITIONS: - -Skip this step and load `{nextStepFile}` if: - -- No innovation signals detected in conversation -- Product is incremental improvement rather than breakthrough -- User confirms innovation exploration is not needed -- Project-type CSV has no innovation signals for this type - -## NEXT STEP: - -After user selects 'C' and content is saved to document (or step is skipped), load `{nextStepFile}`. - -Remember: Do NOT proceed to step-07 until user explicitly selects 'C' from the A/P/C menu (or confirms step skip)! diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-07-project-type.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-07-project-type.md deleted file mode 100644 index 63c9070b6..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-07-project-type.md +++ /dev/null @@ -1,237 +0,0 @@ ---- -name: 'step-07-project-type' -description: 'Conduct project-type specific discovery using CSV-driven guidance' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-08-scoping.md' -outputFile: '{planning_artifacts}/prd.md' - -# Data Files -projectTypesCSV: '../data/project-types.csv' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 7: Project-Type Deep Dive - -**Progress: Step 7 of 11** - Next: Scoping - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between PM peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on project-type specific requirements and technical considerations -- 🎯 DATA-DRIVEN: Use CSV configuration to guide discovery -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating project-type content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted -- 🚫 FORBIDDEN to load next step until C is selected - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Project type from step-02 is available for configuration loading -- Project-type CSV data will be loaded in this step -- Focus on technical and functional requirements specific to this project type - -## YOUR TASK: - -Conduct project-type specific discovery using CSV-driven guidance to define technical requirements. - -## PROJECT-TYPE DISCOVERY SEQUENCE: - -### 1. Load Project-Type Configuration Data - -**Attempt subprocess data lookup:** - -"Your task: Lookup data in {projectTypesCSV} - -**Search criteria:** -- Find row where project_type matches {{projectTypeFromStep02}} - -**Return format:** -Return ONLY the matching row as a YAML-formatted object with these fields: -project_type, key_questions, required_sections, skip_sections, innovation_signals - -**Do NOT return the entire CSV - only the matching row.**" - -**Graceful degradation (if Task tool unavailable):** -- Load the CSV file directly -- Find the matching row manually -- Extract required fields: - - `key_questions` (semicolon-separated list of discovery questions) - - `required_sections` (semicolon-separated list of sections to document) - - `skip_sections` (semicolon-separated list of sections to skip) - - `innovation_signals` (already explored in step-6) - -### 2. Conduct Guided Discovery Using Key Questions - -Parse `key_questions` from CSV and explore each: - -#### Question-Based Discovery: - -For each question in `key_questions` from CSV: - -- Ask the user naturally in conversational style -- Listen for their response and ask clarifying follow-ups -- Connect answers to product value proposition - -**Example Flow:** -If key_questions = "Endpoints needed?;Authentication method?;Data formats?;Rate limits?;Versioning?;SDK needed?" - -Ask naturally: - -- "What are the main endpoints your API needs to expose?" -- "How will you handle authentication and authorization?" -- "What data formats will you support for requests and responses?" - -### 3. Document Project-Type Specific Requirements - -Based on user answers to key_questions, synthesize comprehensive requirements: - -#### Requirement Categories: - -Cover the areas indicated by `required_sections` from CSV: - -- Synthesize what was discovered for each required section -- Document specific requirements, constraints, and decisions -- Connect to product differentiator when relevant - -#### Skip Irrelevant Sections: - -Skip areas indicated by `skip_sections` from CSV to avoid wasting time on irrelevant aspects. - -### 4. Generate Dynamic Content Sections - -Parse `required_sections` list from the matched CSV row. For each section name, generate corresponding content: - -#### Common CSV Section Mappings: - -- "endpoint_specs" or "endpoint_specification" → API endpoints documentation -- "auth_model" or "authentication_model" → Authentication approach -- "platform_reqs" or "platform_requirements" → Platform support needs -- "device_permissions" or "device_features" → Device capabilities -- "tenant_model" → Multi-tenancy approach -- "rbac_matrix" or "permission_matrix" → Permission structure - -#### Template Variable Strategy: - -- For sections matching common template variables: generate specific content -- For sections without template matches: include in main project_type_requirements -- Hybrid approach balances template structure with CSV-driven flexibility - -### 5. Generate Project-Type Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## [Project Type] Specific Requirements - -### Project-Type Overview - -[Project type summary based on conversation] - -### Technical Architecture Considerations - -[Technical architecture requirements based on conversation] - -[Dynamic sections based on CSV and conversation] - -### Implementation Considerations - -[Implementation specific requirements based on conversation] -``` - -### 6. Present MENU OPTIONS - -Present the project-type content for review, then display menu: - -"Based on our conversation and best practices for this product type, I've documented the {project_type}-specific requirements for {{project_name}}. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from section 5] - -**What would you like to do?**" - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Scoping (Step 8 of 11)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask} with the current project-type content, process the enhanced technical insights that come back, ask user "Accept these improvements to the technical requirements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu -- IF P: Read fully and follow: {partyModeWorkflow} with the current project-type requirements, process the collaborative technical expertise and validation, ask user "Accept these changes to the technical requirements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu -- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile} -- IF Any other: help user respond, then redisplay menu - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from previous steps. - -## SUCCESS METRICS: - -✅ Project-type configuration loaded and used effectively -✅ All key questions from CSV explored with user input -✅ Required sections generated per CSV configuration -✅ Skip sections properly avoided to save time -✅ Technical requirements connected to product value -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not loading or using project-type CSV configuration -❌ Missing key questions from CSV in discovery process -❌ Not generating required sections per CSV configuration -❌ Documenting sections that should be skipped per CSV -❌ Creating generic content without project-type specificity -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## PROJECT-TYPE EXAMPLES: - -**For api_backend:** - -- Focus on endpoints, authentication, data schemas, rate limiting -- Skip visual design and user journey sections -- Generate API specification documentation - -**For mobile_app:** - -- Focus on platform requirements, device permissions, offline mode -- Skip API endpoint documentation unless needed -- Generate mobile-specific technical requirements - -**For saas_b2b:** - -- Focus on multi-tenancy, permissions, integrations -- Skip mobile-first considerations unless relevant -- Generate enterprise-specific requirements - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{nextStepFile}` to define project scope. - -Remember: Do NOT proceed to step-08 (Scoping) until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-08-scoping.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-08-scoping.md deleted file mode 100644 index e9df0caba..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-08-scoping.md +++ /dev/null @@ -1,228 +0,0 @@ ---- -name: 'step-08-scoping' -description: 'Define MVP boundaries and prioritize features across development phases' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-09-functional.md' -outputFile: '{planning_artifacts}/prd.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 8: Scoping Exercise - MVP & Future Features - -**Progress: Step 8 of 11** - Next: Functional Requirements - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between PM peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on strategic scope decisions that keep projects viable -- 🎯 EMPHASIZE lean MVP thinking while preserving long-term vision -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 📚 Review the complete PRD document built so far -- ⚠️ Present A/P/C menu after generating scoping decisions -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted -- 🚫 FORBIDDEN to load next step until C is selected - - -## CONTEXT BOUNDARIES: - -- Complete PRD document built so far is available for review -- User journeys, success criteria, and domain requirements are documented -- Focus on strategic scope decisions, not feature details -- Balance between user value and implementation feasibility - -## YOUR TASK: - -Conduct comprehensive scoping exercise to define MVP boundaries and prioritize features across development phases. - -## SCOPING SEQUENCE: - -### 1. Review Current PRD State - -Analyze everything documented so far: -- Present synthesis of established vision, success criteria, journeys -- Assess domain and innovation focus -- Evaluate scope implications: simple MVP, medium, or complex project -- Ask if initial assessment feels right or if they see it differently - -### 2. Define MVP Strategy - -Facilitate strategic MVP decisions: -- Explore MVP philosophy options: problem-solving, experience, platform, or revenue MVP -- Ask critical questions: - - What's the minimum that would make users say 'this is useful'? - - What would make investors/partners say 'this has potential'? - - What's the fastest path to validated learning? -- Guide toward appropriate MVP approach for their product - -### 3. Scoping Decision Framework - -Use structured decision-making for scope: - -**Must-Have Analysis:** -- Guide identification of absolute MVP necessities -- For each journey and success criterion, ask: - - Without this, does the product fail? - - Can this be manual initially? - - Is this a deal-breaker for early adopters? -- Analyze journeys for MVP essentials - -**Nice-to-Have Analysis:** -- Identify what could be added later: - - Features that enhance but aren't essential - - User types that can be added later - - Advanced functionality that builds on MVP -- Ask what features could be added in versions 2, 3, etc. - -### 4. Progressive Feature Roadmap - -Create phased development approach: -- Guide mapping of features across development phases -- Structure as Phase 1 (MVP), Phase 2 (Growth), Phase 3 (Vision) -- Ensure clear progression and dependencies - -- Core user value delivery -- Essential user journeys -- Basic functionality that works reliably - -**Phase 2: Growth** - -- Additional user types -- Enhanced features -- Scale improvements - -**Phase 3: Expansion** - -- Advanced capabilities -- Platform features -- New markets or use cases - -**Where does your current vision fit in this development sequence?**" - -### 5. Risk-Based Scoping - -Identify and mitigate scoping risks: - -**Technical Risks:** -"Looking at your innovation and domain requirements: - -- What's the most technically challenging aspect? -- Could we simplify the initial implementation? -- What's the riskiest assumption about technology feasibility?" - -**Market Risks:** - -- What's the biggest market risk? -- How does the MVP address this? -- What learning do we need to de-risk this?" - -**Resource Risks:** - -- What if we have fewer resources than planned? -- What's the absolute minimum team size needed? -- Can we launch with a smaller feature set?" - -### 6. Generate Scoping Content - -Prepare comprehensive scoping section: - -#### Content Structure: - -```markdown -## Project Scoping & Phased Development - -### MVP Strategy & Philosophy - -**MVP Approach:** {{chosen_mvp_approach}} -**Resource Requirements:** {{mvp_team_size_and_skills}} - -### MVP Feature Set (Phase 1) - -**Core User Journeys Supported:** -{{essential_journeys_for_mvp}} - -**Must-Have Capabilities:** -{{list_of_essential_mvp_features}} - -### Post-MVP Features - -**Phase 2 (Post-MVP):** -{{planned_growth_features}} - -**Phase 3 (Expansion):** -{{planned_expansion_features}} - -### Risk Mitigation Strategy - -**Technical Risks:** {{mitigation_approach}} -**Market Risks:** {{validation_approach}} -**Resource Risks:** {{contingency_approach}} -``` - -### 7. Present MENU OPTIONS - -Present the scoping decisions for review, then display menu: -- Show strategic scoping plan (using structure from step 6) -- Highlight MVP boundaries and phased roadmap -- Ask if they'd like to refine further, get other perspectives, or proceed -- Present menu options naturally as part of conversation - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Functional Requirements (Step 9 of 11)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask} with the current scoping analysis, process the enhanced insights that come back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu -- IF P: Read fully and follow: {partyModeWorkflow} with the scoping context, process the collaborative insights on MVP and roadmap decisions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu -- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile} -- IF Any other: help user respond, then redisplay menu - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Complete PRD document analyzed for scope implications -✅ Strategic MVP approach defined and justified -✅ Clear MVP feature boundaries established -✅ Phased development roadmap created -✅ Key risks identified and mitigation strategies defined -✅ User explicitly agrees to scope decisions -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not analyzing the complete PRD before making scoping decisions -❌ Making scope decisions without strategic rationale -❌ Not getting explicit user agreement on MVP boundaries -❌ Missing critical risk analysis -❌ Not creating clear phased development approach -❌ Not presenting A/P/C menu after content generation - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load {nextStepFile}. - -Remember: Do NOT proceed to step-09 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-09-functional.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-09-functional.md deleted file mode 100644 index a39150c0c..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-09-functional.md +++ /dev/null @@ -1,231 +0,0 @@ ---- -name: 'step-09-functional' -description: 'Synthesize all discovery into comprehensive functional requirements' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-10-nonfunctional.md' -outputFile: '{planning_artifacts}/prd.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 9: Functional Requirements Synthesis - -**Progress: Step 9 of 11** - Next: Non-Functional Requirements - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between PM peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on creating comprehensive capability inventory for the product -- 🎯 CRITICAL: This is THE CAPABILITY CONTRACT for all downstream work -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating functional requirements -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted -- 🚫 FORBIDDEN to load next step until C is selected - - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- ALL previous content (executive summary, success criteria, journeys, domain, innovation, project-type) must be referenced -- No additional data files needed for this step -- Focus on capabilities, not implementation details - -## CRITICAL IMPORTANCE: - -**This section defines THE CAPABILITY CONTRACT for the entire product:** - -- UX designers will ONLY design what's listed here -- Architects will ONLY support what's listed here -- Epic breakdown will ONLY implement what's listed here -- If a capability is missing from FRs, it will NOT exist in the final product - -## FUNCTIONAL REQUIREMENTS SYNTHESIS SEQUENCE: - -### 1. Understand FR Purpose and Usage - -Start by explaining the critical role of functional requirements: - -**Purpose:** -FRs define WHAT capabilities the product must have. They are the complete inventory of user-facing and system capabilities that deliver the product vision. - -**Critical Properties:** -✅ Each FR is a testable capability -✅ Each FR is implementation-agnostic (could be built many ways) -✅ Each FR specifies WHO and WHAT, not HOW -✅ No UI details, no performance numbers, no technology choices -✅ Comprehensive coverage of capability areas - -**How They Will Be Used:** - -1. UX Designer reads FRs → designs interactions for each capability -2. Architect reads FRs → designs systems to support each capability -3. PM reads FRs → creates epics and stories to implement each capability - -### 2. Review Existing Content for Capability Extraction - -Systematically review all previous sections to extract capabilities: - -**Extract From:** - -- Executive Summary → Core product differentiator capabilities -- Success Criteria → Success-enabling capabilities -- User Journeys → Journey-revealed capabilities -- Domain Requirements → Compliance and regulatory capabilities -- Innovation Patterns → Innovative feature capabilities -- Project-Type Requirements → Technical capability needs - -### 3. Organize Requirements by Capability Area - -Group FRs by logical capability areas (NOT by technology or layer): - -**Good Grouping Examples:** - -- ✅ "User Management" (not "Authentication System") -- ✅ "Content Discovery" (not "Search Algorithm") -- ✅ "Team Collaboration" (not "WebSocket Infrastructure") - -**Target 5-8 Capability Areas** for typical projects. - -### 4. Generate Comprehensive FR List - -Create complete functional requirements using this format: - -**Format:** - -- FR#: [Actor] can [capability] [context/constraint if needed] -- Number sequentially (FR1, FR2, FR3...) -- Aim for 20-50 FRs for typical projects - -**Altitude Check:** -Each FR should answer "WHAT capability exists?" NOT "HOW it's implemented?" - -**Examples:** - -- ✅ "Users can customize appearance settings" -- ❌ "Users can toggle light/dark theme with 3 font size options stored in LocalStorage" - -### 5. Self-Validation Process - -Before presenting to user, validate the FR list: - -**Completeness Check:** - -1. "Did I cover EVERY capability mentioned in the MVP scope section?" -2. "Did I include domain-specific requirements as FRs?" -3. "Did I cover the project-type specific needs?" -4. "Could a UX designer read ONLY the FRs and know what to design?" -5. "Could an Architect read ONLY the FRs and know what to support?" -6. "Are there any user actions or system behaviors we discussed that have no FR?" - -**Altitude Check:** - -1. "Am I stating capabilities (WHAT) or implementation (HOW)?" -2. "Am I listing acceptance criteria or UI specifics?" (Remove if yes) -3. "Could this FR be implemented 5 different ways?" (Good - means it's not prescriptive) - -**Quality Check:** - -1. "Is each FR clear enough that someone could test whether it exists?" -2. "Is each FR independent (not dependent on reading other FRs to understand)?" -3. "Did I avoid vague terms like 'good', 'fast', 'easy'?" (Use NFRs for quality attributes) - -### 6. Generate Functional Requirements Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Functional Requirements - -### [Capability Area Name] - -- FR1: [Specific Actor] can [specific capability] -- FR2: [Specific Actor] can [specific capability] -- FR3: [Specific Actor] can [specific capability] - -### [Another Capability Area] - -- FR4: [Specific Actor] can [specific capability] -- FR5: [Specific Actor] can [specific capability] - -[Continue for all capability areas discovered in conversation] -``` - -### 7. Present MENU OPTIONS - -Present the functional requirements for review, then display menu: -- Show synthesized functional requirements (using structure from step 6) -- Emphasize this is the capability contract for all downstream work -- Highlight that every feature must trace back to these requirements -- Ask if they'd like to refine further, get other perspectives, or proceed -- Present menu options naturally as part of conversation - -**What would you like to do?**" - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Non-Functional Requirements (Step 10 of 11)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask} with the current FR list, process the enhanced capability coverage that comes back, ask user if they accept the additions, if yes update content then redisplay menu, if no keep original content then redisplay menu -- IF P: Read fully and follow: {partyModeWorkflow} with the current FR list, process the collaborative capability validation and additions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu -- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile} -- IF Any other: help user respond, then redisplay menu - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ All previous discovery content synthesized into FRs -✅ FRs organized by capability areas (not technology) -✅ Each FR states WHAT capability exists, not HOW to implement -✅ Comprehensive coverage with 20-50 FRs typical -✅ Altitude validation ensures implementation-agnostic requirements -✅ Completeness check validates coverage of all discussed capabilities -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Missing capabilities from previous discovery sections -❌ Organizing FRs by technology instead of capability areas -❌ Including implementation details or UI specifics in FRs -❌ Not achieving comprehensive coverage of discussed capabilities -❌ Using vague terms instead of testable capabilities -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## CAPABILITY CONTRACT REMINDER: - -Emphasize to user: "This FR list is now binding. Any feature not listed here will not exist in the final product unless we explicitly add it. This is why it's critical to ensure completeness now." - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load {nextStepFile} to define non-functional requirements. - -Remember: Do NOT proceed to step-10 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-10-nonfunctional.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-10-nonfunctional.md deleted file mode 100644 index d42323046..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-10-nonfunctional.md +++ /dev/null @@ -1,242 +0,0 @@ ---- -name: 'step-10-nonfunctional' -description: 'Define quality attributes that matter for this specific product' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-11-polish.md' -outputFile: '{planning_artifacts}/prd.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 10: Non-Functional Requirements - -**Progress: Step 10 of 12** - Next: Polish Document - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between PM peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on quality attributes that matter for THIS specific product -- 🎯 SELECTIVE: Only document NFRs that actually apply to the product -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating NFR content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step name to the end of the list of stepsCompleted -- 🚫 FORBIDDEN to load next step until C is selected - - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Functional requirements already defined and will inform NFRs -- Domain and project-type context will guide which NFRs matter -- Focus on specific, measurable quality criteria - -## YOUR TASK: - -Define non-functional requirements that specify quality attributes for the product, focusing only on what matters for THIS specific product. - -## NON-FUNCTIONAL REQUIREMENTS SEQUENCE: - -### 1. Explain NFR Purpose and Scope - -Start by clarifying what NFRs are and why we're selective: - -**NFR Purpose:** -NFRs define HOW WELL the system must perform, not WHAT it must do. They specify quality attributes like performance, security, scalability, etc. - -**Selective Approach:** -We only document NFRs that matter for THIS product. If a category doesn't apply, we skip it entirely. This prevents requirement bloat and focuses on what's actually important. - -### 2. Assess Product Context for NFR Relevance - -Evaluate which NFR categories matter based on product context: - -**Quick Assessment Questions:** - -- **Performance**: Is there user-facing impact of speed? -- **Security**: Are we handling sensitive data or payments? -- **Scalability**: Do we expect rapid user growth? -- **Accessibility**: Are we serving broad public audiences? -- **Integration**: Do we need to connect with other systems? -- **Reliability**: Would downtime cause significant problems? - -### 3. Explore Relevant NFR Categories - -For each relevant category, conduct targeted discovery: - -#### Performance NFRs (If relevant): - -Explore performance requirements: -- What parts of the system need to be fast for users to be successful? -- Are there specific response time expectations? -- What happens if performance is slower than expected? -- Are there concurrent user scenarios we need to support? - -#### Security NFRs (If relevant): - -Explore security requirements: -- What data needs to be protected? -- Who should have access to what? -- What are the security risks we need to mitigate? -- Are there compliance requirements (GDPR, HIPAA, PCI-DSS)? - -#### Scalability NFRs (If relevant): - -Explore scalability requirements: -- How many users do we expect initially? Long-term? -- Are there seasonal or event-based traffic spikes? -- What happens if we exceed our capacity? -- What growth scenarios should we plan for? - -#### Accessibility NFRs (If relevant): - -Explore accessibility requirements: -- Are we serving users with visual, hearing, or motor impairments? -- Are there legal accessibility requirements (WCAG, Section 508)? -- What accessibility features are most important for our users? - -#### Integration NFRs (If relevant): - -Explore integration requirements: -- What external systems do we need to connect with? -- Are there APIs or data formats we must support? -- How reliable do these integrations need to be? - -### 4. Make NFRs Specific and Measurable - -For each relevant NFR category, ensure criteria are testable: - -**From Vague to Specific:** - -- NOT: "The system should be fast" → "User actions complete within 2 seconds" -- NOT: "The system should be secure" → "All data is encrypted at rest and in transit" -- NOT: "The system should scale" → "System supports 10x user growth with <10% performance degradation" - -### 5. Generate NFR Content (Only Relevant Categories) - -Prepare the content to append to the document: - -#### Content Structure (Dynamic based on relevance): - -When saving to document, append these Level 2 and Level 3 sections (only include sections that are relevant): - -```markdown -## Non-Functional Requirements - -### Performance - -[Performance requirements based on conversation - only include if relevant] - -### Security - -[Security requirements based on conversation - only include if relevant] - -### Scalability - -[Scalability requirements based on conversation - only include if relevant] - -### Accessibility - -[Accessibility requirements based on conversation - only include if relevant] - -### Integration - -[Integration requirements based on conversation - only include if relevant] -``` - -### 6. Present MENU OPTIONS - -Present the non-functional requirements for review, then display menu: -- Show defined NFRs (using structure from step 5) -- Note that only relevant categories were included -- Emphasize NFRs specify how well the system needs to perform -- Ask if they'd like to refine further, get other perspectives, or proceed -- Present menu options naturally as part of conversation - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Polish Document (Step 11 of 12)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask} with the current NFR content, process the enhanced quality attribute insights that come back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu -- IF P: Read fully and follow: {partyModeWorkflow} with the current NFR list, process the collaborative technical validation and additions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu -- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile} -- IF Any other: help user respond, then redisplay menu - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 5. - -## SUCCESS METRICS: - -✅ Only relevant NFR categories documented (no requirement bloat) -✅ Each NFR is specific and measurable -✅ NFRs connected to actual user needs and business context -✅ Vague requirements converted to testable criteria -✅ Domain-specific compliance requirements included if relevant -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Documenting NFR categories that don't apply to the product -❌ Leaving requirements vague and unmeasurable -❌ Not connecting NFRs to actual user or business needs -❌ Missing domain-specific compliance requirements -❌ Creating overly prescriptive technical requirements -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NFR CATEGORY GUIDANCE: - -**Include Performance When:** - -- User-facing response times impact success -- Real-time interactions are critical -- Performance is a competitive differentiator - -**Include Security When:** - -- Handling sensitive user data -- Processing payments or financial information -- Subject to compliance regulations -- Protecting intellectual property - -**Include Scalability When:** - -- Expecting rapid user growth -- Handling variable traffic patterns -- Supporting enterprise-scale usage -- Planning for market expansion - -**Include Accessibility When:** - -- Serving broad public audiences -- Subject to accessibility regulations -- Targeting users with disabilities -- B2B customers with accessibility requirements - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load {nextStepFile} to finalize the PRD and complete the workflow. - -Remember: Do NOT proceed to step-11 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-11-polish.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-11-polish.md deleted file mode 100644 index 257afbc27..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-11-polish.md +++ /dev/null @@ -1,217 +0,0 @@ ---- -name: 'step-11-polish' -description: 'Optimize and polish the complete PRD document for flow, coherence, and readability' - -# File References -nextStepFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md' -outputFile: '{planning_artifacts}/prd.md' -purposeFile: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step 11: Document Polish - -**Progress: Step 11 of 12** - Next: Complete PRD - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 CRITICAL: Load the ENTIRE document before making changes -- 📖 CRITICAL: Read complete step file before taking action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- ✅ This is a POLISH step - optimize existing content -- 📋 IMPROVE flow, coherence, and readability -- 💬 PRESERVE user's voice and intent -- 🎯 MAINTAIN all essential information while improving presentation -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Load complete document first -- 📝 Review for flow and coherence issues -- ✂️ Reduce duplication while preserving essential info -- 📖 Ensure proper ## Level 2 headers throughout -- 💾 Save optimized document -- ⚠️ Present A/P/C menu after polish -- 🚫 DO NOT skip review steps - -## CONTEXT BOUNDARIES: - -- Complete PRD document exists from all previous steps -- Document may have duplication from progressive append -- Sections may not flow smoothly together -- Level 2 headers ensure document can be split if needed -- Focus on readability and coherence - -## YOUR TASK: - -Optimize the complete PRD document for flow, coherence, and professional presentation while preserving all essential information. - -## DOCUMENT POLISH SEQUENCE: - -### 1. Load Context and Document - -**CRITICAL:** Load the PRD purpose document first: - -- Read `{purposeFile}` to understand what makes a great BMAD PRD -- Internalize the philosophy: information density, traceability, measurable requirements -- Keep the dual-audience nature (humans + LLMs) in mind - -**Then Load the PRD Document:** - -- Read `{outputFile}` completely from start to finish -- Understand the full document structure and content -- Identify all sections and their relationships -- Note areas that need attention - -### 2. Document Quality Review - -Review the entire document with PRD purpose principles in mind: - -**Information Density:** -- Are there wordy phrases that can be condensed? -- Is conversational padding present? -- Can sentences be more direct and concise? - -**Flow and Coherence:** -- Do sections transition smoothly? -- Are there jarring topic shifts? -- Does the document tell a cohesive story? -- Is the progression logical for readers? - -**Duplication Detection:** -- Are ideas repeated across sections? -- Is the same information stated multiple times? -- Can redundant content be consolidated? -- Are there contradictory statements? - -**Header Structure:** -- Are all main sections using ## Level 2 headers? -- Is the hierarchy consistent (##, ###, ####)? -- Can sections be easily extracted or referenced? -- Are headers descriptive and clear? - -**Readability:** -- Are sentences clear and concise? -- Is the language consistent throughout? -- Are technical terms used appropriately? -- Would stakeholders find this easy to understand? - -### 3. Optimization Actions - -Make targeted improvements: - -**Improve Flow:** -- Add transition sentences between sections -- Smooth out jarring topic shifts -- Ensure logical progression -- Connect related concepts across sections - -**Reduce Duplication:** -- Consolidate repeated information -- Keep content in the most appropriate section -- Use cross-references instead of repetition -- Remove redundant explanations - -**Enhance Coherence:** -- Ensure consistent terminology throughout -- Align all sections with product differentiator -- Maintain consistent voice and tone -- Verify scope consistency across sections - -**Optimize Headers:** -- Ensure all main sections use ## Level 2 -- Make headers descriptive and action-oriented -- Check that headers follow consistent patterns -- Verify headers support document navigation - -### 4. Preserve Critical Information - -**While optimizing, ensure NOTHING essential is lost:** - -**Must Preserve:** -- All user success criteria -- All functional requirements (capability contract) -- All user journey narratives -- All scope decisions (MVP, Growth, Vision) -- All non-functional requirements -- Product differentiator and vision -- Domain-specific requirements -- Innovation analysis (if present) - -**Can Consolidate:** -- Repeated explanations of the same concept -- Redundant background information -- Multiple versions of similar content -- Overlapping examples - -### 5. Generate Optimized Document - -Create the polished version: - -**Polishing Process:** -1. Start with original document -2. Apply all optimization actions -3. Review to ensure nothing essential was lost -4. Verify improvements enhance readability -5. Prepare optimized version for review - -### 6. Present MENU OPTIONS - -Present the polished document for review, then display menu: -- Show what changed in the polish -- Highlight improvements made (flow, duplication, headers) -- Ask if they'd like to refine further, get other perspectives, or proceed -- Present menu options naturally as part of conversation - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Complete PRD (Step 12 of 12)" - -#### Menu Handling Logic: -- IF A: Read fully and follow: {advancedElicitationTask} with the polished document, process the enhanced refinements that come back, ask user "Accept these polish improvements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original polish then redisplay menu -- IF P: Read fully and follow: {partyModeWorkflow} with the polished document, process the collaborative refinements to flow and coherence, ask user "Accept these polish changes? (y/n)", if yes update content with improvements then redisplay menu, if no keep original polish then redisplay menu -- IF C: Save the polished document to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile} -- IF Any other: help user respond, then redisplay menu - -#### EXECUTION RULES: -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu - -## APPEND TO DOCUMENT: - -When user selects 'C', replace the entire document content with the polished version. - -## SUCCESS METRICS: - -✅ Complete document loaded and reviewed -✅ Flow and coherence improved -✅ Duplication reduced while preserving essential information -✅ All main sections use ## Level 2 headers -✅ Transitions between sections are smooth -✅ User's voice and intent preserved -✅ Document is more readable and professional -✅ A/P/C menu presented and handled correctly -✅ Polished document saved when C selected - -## FAILURE MODES: - -❌ Loading only partial document (leads to incomplete polish) -❌ Removing essential information while reducing duplication -❌ Not preserving user's voice and intent -❌ Changing content instead of improving presentation -❌ Not ensuring ## Level 2 headers for main sections -❌ Making arbitrary style changes instead of coherence improvements -❌ Not presenting A/P/C menu for user approval -❌ Saving polished document without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making changes without complete understanding of document requirements - -## NEXT STEP: - -After user selects 'C' and polished document is saved, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md` to complete the workflow. - -Remember: Do NOT proceed to step-12 until user explicitly selects 'C' from the A/P/C menu and polished document is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md deleted file mode 100644 index 9f88be6ee..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -name: 'step-12-complete' -description: 'Complete the PRD workflow, update status files, and suggest next steps including validation' - -# File References -outputFile: '{planning_artifacts}/prd.md' -validationFlow: '../steps-v/step-v-01-discovery.md' ---- - -# Step 12: Workflow Completion - -**Final Step - Complete the PRD** - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ THIS IS A FINAL STEP - Workflow completion required -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action -- 🛑 NO content generation - this is a wrap-up step -- 📋 FINALIZE document and update workflow status -- 💬 FOCUS on completion, validation options, and next steps -- 🎯 UPDATE workflow status files with completion information -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 💾 Update the main workflow status file with completion information (if exists) -- 📖 Offer validation workflow options to user -- 🚫 DO NOT load additional steps after this one - -## TERMINATION STEP PROTOCOLS: - -- This is a FINAL step - workflow completion required -- Update workflow status file with finalized document -- Suggest validation and next workflow steps -- Mark workflow as complete in status tracking - -## CONTEXT BOUNDARIES: - -- Complete and polished PRD document is available from all previous steps -- Workflow frontmatter shows all completed steps including polish -- All collaborative content has been generated, saved, and optimized -- Focus on completion, validation options, and next steps - -## YOUR TASK: - -Complete the PRD workflow, update status files, offer validation options, and suggest next steps for the project. - -## WORKFLOW COMPLETION SEQUENCE: - -### 1. Announce Workflow Completion - -Inform user that the PRD is complete and polished: -- Celebrate successful completion of comprehensive PRD -- Summarize all sections that were created -- Highlight that document has been polished for flow and coherence -- Emphasize document is ready for downstream work - -### 2. Workflow Status Update - -Update the main workflow status file if there is one: - -- Load `{status_file}` from workflow configuration (if exists) -- Update workflow_status["prd"] = "{default_output_file}" -- Save file, preserving all comments and structure -- Mark current timestamp as completion time - -### 3. Validation Workflow Options - -Offer validation workflows to ensure PRD is ready for implementation: - -**Available Validation Workflows:** - -**Option 1: Check Implementation Readiness** (`{checkImplementationReadinessWorkflow}`) -- Validates PRD has all information needed for development -- Checks epic coverage completeness -- Reviews UX alignment with requirements -- Assesses epic quality and readiness -- Identifies gaps before architecture/design work begins - -**When to use:** Before starting technical architecture or epic breakdown - -**Option 2: Skip for Now** -- Proceed directly to next workflows (architecture, UX, epics) -- Validation can be done later if needed -- Some teams prefer to validate during architecture reviews - -### 4. Suggest Next Workflows - -PRD complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` - -### 5. Final Completion Confirmation - -- Confirm completion with user and summarize what has been accomplished -- Document now contains: Executive Summary, Success Criteria, User Journeys, Domain Requirements (if applicable), Innovation Analysis (if applicable), Project-Type Requirements, Functional Requirements (capability contract), Non-Functional Requirements, and has been polished for flow and coherence -- Ask if they'd like to run validation workflow or proceed to next workflows - -## SUCCESS METRICS: - -✅ PRD document contains all required sections and has been polished -✅ All collaborative content properly saved and optimized -✅ Workflow status file updated with completion information (if exists) -✅ Validation workflow options clearly presented -✅ Clear next step guidance provided to user -✅ Document quality validation completed -✅ User acknowledges completion and understands next options - -## FAILURE MODES: - -❌ Not updating workflow status file with completion information (if exists) -❌ Not offering validation workflow options -❌ Missing clear next step guidance for user -❌ Not confirming document completeness with user -❌ Workflow not properly marked as complete in status tracking (if applicable) -❌ User unclear about what happens next or what validation options exist - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## FINAL REMINDER to give the user: - -The polished PRD serves as the foundation for all subsequent product development activities. All design, architecture, and development work should trace back to the requirements and vision documented in this PRD - update it also as needed as you continue planning. - -**Congratulations on completing the Product Requirements Document for {{project_name}}!** 🎉 diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01-discovery.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01-discovery.md deleted file mode 100644 index 8f47cd551..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01-discovery.md +++ /dev/null @@ -1,247 +0,0 @@ ---- -name: 'step-e-01-discovery' -description: 'Discovery & Understanding - Understand what user wants to edit and detect PRD format' - -# File references (ONLY variables used in this step) -altStepFile: './step-e-01b-legacy-conversion.md' -prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md' -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' ---- - -# Step E-1: Discovery & Understanding - -## STEP GOAL: - -Understand what the user wants to edit in the PRD, detect PRD format/type, check for validation report guidance, and route appropriately. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and PRD Improvement Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring analytical expertise and improvement guidance -- ✅ User brings domain knowledge and edit requirements - -### Step-Specific Rules: - -- 🎯 Focus ONLY on discovering user intent and PRD format -- 🚫 FORBIDDEN to make any edits yet -- 💬 Approach: Inquisitive and analytical, understanding before acting -- 🚪 This is a branch step - may route to legacy conversion - -## EXECUTION PROTOCOLS: - -- 🎯 Discover user's edit requirements -- 🎯 Auto-detect validation reports in PRD folder (use as guide) -- 🎯 Load validation report if provided (use as guide) -- 🎯 Detect PRD format (BMAD/legacy) -- 🎯 Route appropriately based on format -- 💾 Document discoveries for next step -- 🚫 FORBIDDEN to proceed without understanding requirements - -## CONTEXT BOUNDARIES: - -- Available context: PRD file to edit, optional validation report, auto-detected validation reports -- Focus: User intent discovery and format detection only -- Limits: Don't edit yet, don't validate yet -- Dependencies: None - this is first edit step - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Load PRD Purpose Standards - -Load and read the complete file at: -`{prdPurpose}` (data/prd-purpose.md) - -This file defines what makes a great BMAD PRD. Internalize this understanding - it will guide improvement recommendations. - -### 2. Discover PRD to Edit - -"**PRD Edit Workflow** - -Which PRD would you like to edit? - -Please provide the path to the PRD file you want to edit." - -**Wait for user to provide PRD path.** - -### 3. Validate PRD Exists and Load - -Once PRD path is provided: -- Check if PRD file exists at specified path -- If not found: "I cannot find a PRD at that path. Please check the path and try again." -- If found: Load the complete PRD file including frontmatter - -### 4. Check for Existing Validation Report - -**Check if validation report exists in the PRD folder:** - -```bash -# Look for most recent validation report in the PRD folder -ls -t {prd_folder_path}/validation-report-*.md 2>/dev/null | head -1 -``` - -**If validation report found:** - -Display: -"**📋 Found Validation Report** - -I found a validation report from {validation_date} in the PRD folder. - -This report contains findings from previous validation checks and can help guide our edits to fix known issues. - -**Would you like to:** -- **[U] Use validation report** - Load it to guide and prioritize edits -- **[S] Skip** - Proceed with manual edit discovery" - -**Wait for user input.** - -**IF U (Use validation report):** -- Load the validation report file -- Extract findings, issues, and improvement suggestions -- Note: "Validation report loaded - will use it to guide prioritized improvements" -- Continue to step 5 - -**IF S (Skip) or no validation report found:** -- Note: "Proceeding with manual edit discovery" -- Continue to step 5 - -**If no validation report found:** -- Note: "No validation report found in PRD folder" -- Continue to step 5 without asking user - -### 5. Ask About Validation Report - -"**Do you have a validation report to guide edits?** - -If you've run the validation workflow on this PRD, I can use that report to guide improvements and prioritize changes. - -Validation report path (or type 'none'):" - -**Wait for user input.** - -**If validation report path provided:** -- Load the validation report -- Extract findings, severity, improvement suggestions -- Note: "Validation report loaded - will use it to guide prioritized improvements" - -**If no validation report:** -- Note: "Proceeding with manual edit discovery" -- Continue to step 6 - -### 6. Discover Edit Requirements - -"**What would you like to edit in this PRD?** - -Please describe the changes you want to make. For example: -- Fix specific issues (information density, implementation leakage, etc.) -- Add missing sections or content -- Improve structure and flow -- Convert to BMAD format (if legacy PRD) -- General improvements -- Other changes - -**Describe your edit goals:**" - -**Wait for user to describe their requirements.** - -### 7. Detect PRD Format - -Analyze the loaded PRD: - -**Extract all ## Level 2 headers** from PRD - -**Check for BMAD PRD core sections:** -1. Executive Summary -2. Success Criteria -3. Product Scope -4. User Journeys -5. Functional Requirements -6. Non-Functional Requirements - -**Classify format:** -- **BMAD Standard:** 5-6 core sections present -- **BMAD Variant:** 3-4 core sections present, generally follows BMAD patterns -- **Legacy (Non-Standard):** Fewer than 3 core sections, does not follow BMAD structure - -### 8. Route Based on Format and Context - -**IF validation report provided OR PRD is BMAD Standard/Variant:** - -Display: "**Edit Requirements Understood** - -**PRD Format:** {classification} -{If validation report: "**Validation Guide:** Yes - will use validation report findings"} -**Edit Goals:** {summary of user's requirements} - -**Proceeding to deep review and analysis...**" - -Read fully and follow: next step (step-e-02-review.md) - -**IF PRD is Legacy (Non-Standard) AND no validation report:** - -Display: "**Format Detected:** Legacy PRD - -This PRD does not follow BMAD standard structure (only {count}/6 core sections present). - -**Your edit goals:** {user's requirements} - -**How would you like to proceed?**" - -Present MENU OPTIONS below for user selection - -### 9. Present MENU OPTIONS (Legacy PRDs Only) - -**[C] Convert to BMAD Format** - Convert PRD to BMAD standard structure, then apply your edits -**[E] Edit As-Is** - Apply your edits without converting the format -**[X] Exit** - Exit and review conversion options - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input -- Only proceed based on user selection - -#### Menu Handling Logic: - -- IF C (Convert): Read fully and follow: {altStepFile} (step-e-01b-legacy-conversion.md) -- IF E (Edit As-Is): Display "Proceeding with edits..." then load next step -- IF X (Exit): Display summary and exit -- IF Any other: help user, then redisplay menu - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- User's edit requirements clearly understood -- Auto-detected validation reports loaded and analyzed (when found) -- Manual validation report loaded and analyzed (if provided) -- PRD format detected correctly -- BMAD PRDs proceed directly to review step -- Legacy PRDs pause and present conversion options -- User can choose conversion path or edit as-is - -### ❌ SYSTEM FAILURE: - -- Not discovering user's edit requirements -- Not auto-detecting validation reports in PRD folder -- Not loading validation report when provided (auto or manual) -- Missing format detection -- Not pausing for legacy PRDs without guidance -- Auto-proceeding without understanding intent - -**Master Rule:** Understand before editing. Detect format early so we can guide users appropriately. Auto-detect and use validation reports for prioritized improvements. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01b-legacy-conversion.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01b-legacy-conversion.md deleted file mode 100644 index d13531d26..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01b-legacy-conversion.md +++ /dev/null @@ -1,208 +0,0 @@ ---- -name: 'step-e-01b-legacy-conversion' -description: 'Legacy PRD Conversion Assessment - Analyze legacy PRD and propose conversion strategy' - -# File references (ONLY variables used in this step) -nextStepFile: './step-e-02-review.md' -prdFile: '{prd_file_path}' -prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md' ---- - -# Step E-1B: Legacy PRD Conversion Assessment - -## STEP GOAL: - -Analyze legacy PRD against BMAD standards, identify gaps, propose conversion strategy, and let user choose how to proceed. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and PRD Improvement Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring BMAD standards expertise and conversion guidance -- ✅ User brings domain knowledge and edit requirements - -### Step-Specific Rules: - -- 🎯 Focus ONLY on conversion assessment and proposal -- 🚫 FORBIDDEN to perform conversion yet (that comes in edit step) -- 💬 Approach: Analytical gap analysis with clear recommendations -- 🚪 This is a branch step - user chooses conversion path - -## EXECUTION PROTOCOLS: - -- 🎯 Analyze legacy PRD against BMAD standard -- 💾 Identify gaps and estimate conversion effort -- 📖 Present conversion options with effort estimates -- 🚫 FORBIDDEN to proceed without user selection - -## CONTEXT BOUNDARIES: - -- Available context: Legacy PRD, user's edit requirements, prd-purpose standards -- Focus: Conversion assessment only (not actual conversion) -- Limits: Don't convert yet, don't validate yet -- Dependencies: Step e-01 detected legacy format and routed here - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Attempt Sub-Process Assessment - -**Try to use Task tool with sub-agent:** - -"Perform legacy PRD conversion assessment: - -**Load the PRD and prd-purpose.md** - -**For each BMAD PRD section, analyze:** -1. Does PRD have this section? (Executive Summary, Success Criteria, Product Scope, User Journeys, Functional Requirements, Non-Functional Requirements) -2. If present: Is it complete and well-structured? -3. If missing: What content exists that could migrate to this section? -4. Effort to create/complete: Minimal / Moderate / Significant - -**Identify:** -- Core sections present: {count}/6 -- Content gaps in each section -- Overall conversion effort: Quick / Moderate / Substantial -- Recommended approach: Full restructuring vs targeted improvements - -Return conversion assessment with gap analysis and effort estimate." - -**Graceful degradation (if no Task tool):** -- Manually check PRD for each BMAD section -- Note what's present and what's missing -- Estimate conversion effort -- Identify best conversion approach - -### 2. Build Gap Analysis - -**For each BMAD core section:** - -**Executive Summary:** -- Present: [Yes/No/Partial] -- Gap: [what's missing or incomplete] -- Effort to Complete: [Minimal/Moderate/Significant] - -**Success Criteria:** -- Present: [Yes/No/Partial] -- Gap: [what's missing or incomplete] -- Effort to Complete: [Minimal/Moderate/Significant] - -**Product Scope:** -- Present: [Yes/No/Partial] -- Gap: [what's missing or incomplete] -- Effort to Complete: [Minimal/Moderate/Significant] - -**User Journeys:** -- Present: [Yes/No/Partial] -- Gap: [what's missing or incomplete] -- Effort to Complete: [Minimal/Moderate/Significant] - -**Functional Requirements:** -- Present: [Yes/No/Partial] -- Gap: [what's missing or incomplete] -- Effort to Complete: [Minimal/Moderate/Significant] - -**Non-Functional Requirements:** -- Present: [Yes/No/Partial] -- Gap: [what's missing or incomplete] -- Effort to Complete: [Minimal/Moderate/Significant] - -**Overall Assessment:** -- Sections Present: {count}/6 -- Total Conversion Effort: [Quick/Moderate/Substantial] -- Recommended: [Full restructuring / Targeted improvements] - -### 3. Present Conversion Assessment - -Display: - -"**Legacy PRD Conversion Assessment** - -**Current PRD Structure:** -- Core sections present: {count}/6 -{List which sections are present/missing} - -**Gap Analysis:** - -{Present gap analysis table showing each section's status and effort} - -**Overall Conversion Effort:** {effort level} - -**Your Edit Goals:** -{Reiterate user's stated edit requirements} - -**Recommendation:** -{Based on effort and user goals, recommend best approach} - -**How would you like to proceed?**" - -### 4. Present MENU OPTIONS - -**[R] Restructure to BMAD** - Full conversion to BMAD format, then apply your edits -**[I] Targeted Improvements** - Apply your edits to existing structure without restructuring -**[E] Edit & Restructure** - Do both: convert format AND apply your edits -**[X] Exit** - Review assessment and decide - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input -- Only proceed based on user selection - -#### Menu Handling Logic: - -- IF R (Restructure): Note conversion mode, then load next step -- IF I (Targeted): Note targeted mode, then load next step -- IF E (Edit & Restructure): Note both mode, then load next step -- IF X (Exit): Display summary, exit - -### 5. Document Conversion Strategy - -Store conversion decision for next step: - -- **Conversion mode:** [Full restructuring / Targeted improvements / Both] -- **Edit requirements:** [user's requirements from step e-01] -- **Gap analysis:** [summary of gaps identified] - -Display: "**Conversion Strategy Documented** - -Mode: {conversion mode} -Edit goals: {summary} - -**Proceeding to deep review...**" - -Read fully and follow: {nextStepFile} (step-e-02-review.md) - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All 6 BMAD core sections analyzed for gaps -- Effort estimates provided for each section -- Overall conversion effort assessed correctly -- Clear recommendation provided based on effort and user goals -- User chooses conversion strategy (restructure/targeted/both) -- Conversion strategy documented for next step - -### ❌ SYSTEM FAILURE: - -- Not analyzing all 6 core sections -- Missing effort estimates -- Not providing clear recommendation -- Auto-proceeding without user selection -- Not documenting conversion strategy - -**Master Rule:** Legacy PRDs need conversion assessment so users understand the work involved and can choose the best approach. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-02-review.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-02-review.md deleted file mode 100644 index f34de79ff..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-02-review.md +++ /dev/null @@ -1,249 +0,0 @@ ---- -name: 'step-e-02-review' -description: 'Deep Review & Analysis - Thoroughly review existing PRD and prepare detailed change plan' - -# File references (ONLY variables used in this step) -nextStepFile: './step-e-03-edit.md' -prdFile: '{prd_file_path}' -validationReport: '{validation_report_path}' # If provided -prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md' -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' ---- - -# Step E-2: Deep Review & Analysis - -## STEP GOAL: - -Thoroughly review the existing PRD, analyze validation report findings (if provided), and prepare a detailed change plan before editing. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and PRD Improvement Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring analytical expertise and improvement planning -- ✅ User brings domain knowledge and approval authority - -### Step-Specific Rules: - -- 🎯 Focus ONLY on review and analysis, not editing yet -- 🚫 FORBIDDEN to make changes to PRD in this step -- 💬 Approach: Thorough analysis with user confirmation on plan -- 🚪 This is a middle step - user confirms plan before proceeding - -## EXECUTION PROTOCOLS: - -- 🎯 Load and analyze validation report (if provided) -- 🎯 Deep review of entire PRD -- 🎯 Map validation findings to specific sections -- 🎯 Prepare detailed change plan -- 💬 Get user confirmation on plan -- 🚫 FORBIDDEN to proceed to edit without user approval - -## CONTEXT BOUNDARIES: - -- Available context: PRD file, validation report (if provided), user requirements from step e-01 -- Focus: Analysis and planning only (no editing) -- Limits: Don't change PRD yet, don't validate yet -- Dependencies: Step e-01 completed - requirements and format known - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Attempt Sub-Process Deep Review - -**Try to use Task tool with sub-agent:** - -"Perform deep PRD review and change planning: - -**Context from step e-01:** -- User's edit requirements: {user_requirements} -- PRD format: {BMAD/legacy} -- Validation report provided: {yes/no} -- Conversion mode: {restructure/targeted/both} (if legacy) - -**IF validation report provided:** -1. Extract all findings from validation report -2. Map findings to specific PRD sections -3. Prioritize by severity: Critical > Warning > Informational -4. For each critical issue: identify specific fix needed -5. For user's manual edit goals: identify where in PRD to apply - -**IF no validation report:** -1. Read entire PRD thoroughly -2. Analyze against BMAD standards (from prd-purpose.md) -3. Identify issues in: - - Information density (anti-patterns) - - Structure and flow - - Completeness (missing sections/content) - - Measurability (unmeasurable requirements) - - Traceability (broken chains) - - Implementation leakage -4. Map user's edit goals to specific sections - -**Output:** -- Section-by-section analysis -- Specific changes needed for each section -- Prioritized action list -- Recommended order for applying changes - -Return detailed change plan with section breakdown." - -**Graceful degradation (if no Task tool):** -- Manually read PRD sections -- Manually analyze validation report findings (if provided) -- Build section-by-section change plan -- Prioritize changes by severity/user goals - -### 2. Build Change Plan - -**Organize by PRD section:** - -**For each section (in order):** -- **Current State:** Brief description of what exists -- **Issues Identified:** [List from validation report or manual analysis] -- **Changes Needed:** [Specific changes required] -- **Priority:** [Critical/High/Medium/Low] -- **User Requirements Met:** [Which user edit goals address this section] - -**Include:** -- Sections to add (if missing) -- Sections to update (if present but needs work) -- Content to remove (if incorrect/leakage) -- Structure changes (if reformatting needed) - -### 3. Prepare Change Plan Summary - -**Summary sections:** - -**Changes by Type:** -- **Additions:** {count} sections to add -- **Updates:** {count} sections to update -- **Removals:** {count} items to remove -- **Restructuring:** {yes/no} if format conversion needed - -**Priority Distribution:** -- **Critical:** {count} changes (must fix) -- **High:** {count} changes (important) -- **Medium:** {count} changes (nice to have) -- **Low:** {count} changes (optional) - -**Estimated Effort:** -[Quick/Moderate/Substantial] based on scope and complexity - -### 4. Present Change Plan to User - -Display: - -"**Deep Review Complete - Change Plan** - -**PRD Analysis:** -{Brief summary of PRD current state} - -{If validation report provided:} -**Validation Findings:** -{count} issues identified: {critical} critical, {warning} warnings - -**Your Edit Requirements:** -{summary of what user wants to edit} - -**Proposed Change Plan:** - -**By Section:** -{Present section-by-section breakdown} - -**By Priority:** -- Critical: {count} items -- High: {count} items -- Medium: {count} items - -**Estimated Effort:** {effort level} - -**Questions:** -1. Does this change plan align with what you had in mind? -2. Any sections I should add/remove/reprioritize? -3. Any concerns before I proceed with edits? - -**Review the plan and let me know if you'd like any adjustments.**" - -### 5. Get User Confirmation - -Wait for user to review and provide feedback. - -**If user wants adjustments:** -- Discuss requested changes -- Revise change plan accordingly -- Represent for confirmation - -**If user approves:** -- Note: "Change plan approved. Proceeding to edit step." -- Continue to step 6 - -### 6. Document Approved Plan - -Store approved change plan for next step: - -- **Approved changes:** Section-by-section list -- **Priority order:** Sequence to apply changes -- **User confirmed:** Yes - -Display: "**Change Plan Approved** - -{Brief summary of approved plan} - -**Proceeding to edit step...**" - -Read fully and follow: {nextStepFile} (step-e-03-edit.md) - -### 7. Present MENU OPTIONS (If User Wants Discussion) - -**[A] Advanced Elicitation** - Get additional perspectives on change plan -**[P] Party Mode** - Discuss with team for more ideas -**[C] Continue to Edit** - Proceed with approved plan - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input -- Only proceed to edit when user selects 'C' - -#### Menu Handling Logic: - -- IF A: Read fully and follow: {advancedElicitationTask}, then return to discussion -- IF P: Read fully and follow: {partyModeWorkflow}, then return to discussion -- IF C: Document approval, then load {nextStepFile} -- IF Any other: discuss, then redisplay menu - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Validation report findings fully analyzed (if provided) -- Deep PRD review completed systematically -- Change plan built section-by-section -- Changes prioritized by severity/user goals -- User presented with clear plan -- User confirms or adjusts plan -- Approved plan documented for next step - -### ❌ SYSTEM FAILURE: - -- Not analyzing validation report findings (if provided) -- Superficial review instead of deep analysis -- Missing section-by-section breakdown -- Not prioritizing changes -- Proceeding without user approval - -**Master Rule:** Plan before editing. Thorough analysis ensures we make the right changes in the right order. User approval prevents misalignment. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-03-edit.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-03-edit.md deleted file mode 100644 index 65c12946f..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-03-edit.md +++ /dev/null @@ -1,253 +0,0 @@ ---- -name: 'step-e-03-edit' -description: 'Edit & Update - Apply changes to PRD following approved change plan' - -# File references (ONLY variables used in this step) -nextStepFile: './step-e-04-complete.md' -prdFile: '{prd_file_path}' -prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md' ---- - -# Step E-3: Edit & Update - -## STEP GOAL: - -Apply changes to the PRD following the approved change plan from step e-02, including content updates, structure improvements, and format conversion if needed. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 ALWAYS generate content WITH user input/approval -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and PRD Improvement Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring analytical expertise and precise editing skills -- ✅ User brings domain knowledge and approval authority - -### Step-Specific Rules: - -- 🎯 Focus ONLY on implementing approved changes from step e-02 -- 🚫 FORBIDDEN to make changes beyond the approved plan -- 💬 Approach: Methodical, section-by-section execution -- 🚪 This is a middle step - user can request adjustments - -## EXECUTION PROTOCOLS: - -- 🎯 Follow approved change plan systematically -- 💾 Edit PRD content according to plan -- 📖 Update frontmatter as needed -- 🚫 FORBIDDEN to proceed without completion - -## CONTEXT BOUNDARIES: - -- Available context: PRD file, approved change plan from step e-02, prd-purpose standards -- Focus: Implementing changes from approved plan only -- Limits: Don't add changes beyond plan, don't validate yet -- Dependencies: Step e-02 completed - plan approved by user - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Retrieve Approved Change Plan - -From step e-02, retrieve: -- **Approved changes:** Section-by-section list -- **Priority order:** Sequence to apply changes -- **User requirements:** Edit goals from step e-01 - -Display: "**Starting PRD Edits** - -**Change Plan:** {summary} -**Total Changes:** {count} -**Estimated Effort:** {effort level} - -**Proceeding with edits section by section...**" - -### 2. Attempt Sub-Process Edits (For Complex Changes) - -**Try to use Task tool with sub-agent for major sections:** - -"Execute PRD edits for {section_name}: - -**Context:** -- Section to edit: {section_name} -- Current content: {existing content} -- Changes needed: {specific changes from plan} -- BMAD PRD standards: Load from prd-purpose.md - -**Tasks:** -1. Read current PRD section -2. Apply specified changes -3. Ensure BMAD PRD principles compliance: - - High information density (no filler) - - Measurable requirements - - Clear structure - - Proper markdown formatting -4. Return updated section content - -Apply changes and return updated section." - -**Graceful degradation (if no Task tool):** -- Perform edits directly in current context -- Load PRD section, apply changes, save - -### 3. Execute Changes Section-by-Section - -**For each section in approved plan (in priority order):** - -**a) Load current section** -- Read the current PRD section content -- Note what exists - -**b) Apply changes per plan** -- Additions: Create new sections with proper content -- Updates: Modify existing content per plan -- Removals: Remove specified content -- Restructuring: Reformat content to BMAD standard - -**c) Update PRD file** -- Apply changes to PRD -- Save updated PRD -- Verify changes applied correctly - -**Display progress after each section:** -"**Section Updated:** {section_name} -Changes: {brief summary} -{More sections remaining...}" - -### 4. Handle Restructuring (If Needed) - -**If conversion mode is "Full restructuring" or "Both":** - -**For restructuring:** -- Reorganize PRD to BMAD standard structure -- Ensure proper ## Level 2 headers -- Reorder sections logically -- Update PRD frontmatter to match BMAD format - -**Follow BMAD PRD structure:** -1. Executive Summary -2. Success Criteria -3. Product Scope -4. User Journeys -5. Domain Requirements (if applicable) -6. Innovation Analysis (if applicable) -7. Project-Type Requirements -8. Functional Requirements -9. Non-Functional Requirements - -Display: "**PRD Restructured** -BMAD standard structure applied. -{Sections added/reordered}" - -### 5. Update PRD Frontmatter - -**Ensure frontmatter is complete and accurate:** - -```yaml ---- -workflowType: 'prd' -workflow: 'create' # or 'validate' or 'edit' -classification: - domain: '{domain}' - projectType: '{project_type}' - complexity: '{complexity}' -inputDocuments: [list of input documents] -stepsCompleted: ['step-e-01-discovery', 'step-e-02-review', 'step-e-03-edit'] -lastEdited: '{current_date}' -editHistory: - - date: '{current_date}' - changes: '{summary of changes}' ---- -``` - -**Update frontmatter accordingly.** - -### 6. Final Review of Changes - -**Load complete updated PRD** - -**Verify:** -- All approved changes applied correctly -- PRD structure is sound -- No unintended modifications -- Frontmatter is accurate - -**If issues found:** -- Fix them now -- Note corrections made - -**If user wants adjustments:** -- Accept feedback and make adjustments -- Re-verify after adjustments - -### 7. Confirm Completion - -Display: - -"**PRD Edits Complete** - -**Changes Applied:** {count} sections modified -**PRD Updated:** {prd_file_path} - -**Summary of Changes:** -{Brief bullet list of major changes} - -**PRD is ready for:** -- Use in downstream workflows (UX, Architecture) -- Validation (if not yet validated) - -**What would you like to do next?**" - -### 8. Present MENU OPTIONS - -**[V] Run Validation** - Execute full validation workflow (steps-v/step-v-01-discovery.md) -**[S] Summary Only** - End with summary of changes (no validation) -**[A] Adjust** - Make additional edits -**[X] Exit** - Exit edit workflow - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input -- Only proceed based on user selection - -#### Menu Handling Logic: - -- IF V (Validate): Display "Starting validation workflow..." then read fully and follow: steps-v/step-v-01-discovery.md -- IF S (Summary): Present edit summary and exit -- IF A (Adjust): Accept additional requirements, loop back to editing -- IF X (Exit): Display summary and exit - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All approved changes from step e-02 applied correctly -- Changes executed in planned priority order -- Restructuring completed (if needed) -- Frontmatter updated accurately -- Final verification confirms changes -- User can proceed to validation or exit with summary -- Option to run validation seamlessly integrates edit and validate modes - -### ❌ SYSTEM FAILURE: - -- Making changes beyond approved plan -- Not following priority order -- Missing restructuring (if conversion mode) -- Not updating frontmatter -- No final verification -- Not saving updated PRD - -**Master Rule:** Execute the plan exactly as approved. PRD is now ready for validation or downstream use. Validation integration ensures quality. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md deleted file mode 100644 index 5d681feed..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md +++ /dev/null @@ -1,168 +0,0 @@ ---- -name: 'step-e-04-complete' -description: 'Complete & Validate - Present options for next steps including full validation' - -# File references (ONLY variables used in this step) -prdFile: '{prd_file_path}' -validationWorkflow: '../steps-v/step-v-01-discovery.md' ---- - -# Step E-4: Complete & Validate - -## STEP GOAL: - -Present summary of completed edits and offer next steps including seamless integration with validation workflow. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 ALWAYS generate content WITH user input/approval -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and PRD Improvement Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring synthesis and summary expertise -- ✅ User chooses next actions - -### Step-Specific Rules: - -- 🎯 Focus ONLY on presenting summary and options -- 🚫 FORBIDDEN to make additional changes -- 💬 Approach: Clear, concise summary with actionable options -- 🚪 This is the final edit step - no more edits - -## EXECUTION PROTOCOLS: - -- 🎯 Compile summary of all changes made -- 🎯 Present options clearly with expected outcomes -- 📖 Route to validation if user chooses -- 🚫 FORBIDDEN to proceed without user selection - -## CONTEXT BOUNDARIES: - -- Available context: Updated PRD file, edit history from step e-03 -- Focus: Summary and options only (no more editing) -- Limits: Don't make changes, just present options -- Dependencies: Step e-03 completed - all edits applied - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Compile Edit Summary - -From step e-03 change execution, compile: - -**Changes Made:** -- Sections added: {list with names} -- Sections updated: {list with names} -- Content removed: {list} -- Structure changes: {description} - -**Edit Details:** -- Total sections affected: {count} -- Mode: {restructure/targeted/both} -- Priority addressed: {Critical/High/Medium/Low} - -**PRD Status:** -- Format: {BMAD Standard / BMAD Variant / Legacy (converted)} -- Completeness: {assessment} -- Ready for: {downstream use cases} - -### 2. Present Completion Summary - -Display: - -"**✓ PRD Edit Complete** - -**Updated PRD:** {prd_file_path} - -**Changes Summary:** -{Present bulleted list of major changes} - -**Edit Mode:** {mode} -**Sections Modified:** {count} - -**PRD Format:** {format} - -**PRD is now ready for:** -- Downstream workflows (UX Design, Architecture) -- Validation to ensure quality -- Production use - -**What would you like to do next?**" - -### 3. Present MENU OPTIONS - -Display: - -**[V] Run Full Validation** - Execute complete validation workflow (steps-v) to verify PRD quality -**[E] Edit More** - Make additional edits to the PRD -**[S] Summary** - End with detailed summary of changes -**[X] Exit** - Exit edit workflow - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input -- Only proceed based on user selection - -#### Menu Handling Logic: - -- **IF V (Run Full Validation):** - - Display: "**Starting Validation Workflow**" - - Display: "This will run all 13 validation checks on the updated PRD." - - Display: "Preparing to validate: {prd_file_path}" - - Display: "**Proceeding to validation...**" - - Read fully and follow: {validationWorkflow} (steps-v/step-v-01-discovery.md) - - Note: This hands off to the validation workflow which will run its complete 13-step process - -- **IF E (Edit More):** - - Display: "**Additional Edits**" - - Ask: "What additional edits would you like to make?" - - Accept input, then display: "**Returning to edit step...**" - - Read fully and follow: step-e-03-edit.md again - -- **IF S (Summary):** - - Display detailed summary including: - - Complete list of all changes made - - Before/after comparison (key improvements) - - Recommendations for next steps - - Display: "**Edit Workflow Complete**" - - Exit - -- **IF X (Exit):** - - Display summary - - Display: "**Edit Workflow Complete**" - - Exit - -- **IF Any other:** Help user, then redisplay menu - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Complete edit summary compiled accurately -- All changes clearly documented -- Options presented with clear expectations -- Validation option seamlessly integrates with steps-v workflow -- User can validate, edit more, or exit -- Clean handoff to validation workflow (if chosen) -- Edit workflow completes properly - -### ❌ SYSTEM FAILURE: - -- Missing changes in summary -- Not offering validation option -- Not documenting completion properly -- No clear handoff to validation workflow - -**Master Rule:** Edit workflow seamlessly integrates with validation. User can edit → validate → edit again → validate again in iterative improvement cycle. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md deleted file mode 100644 index 6c591c2dd..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md +++ /dev/null @@ -1,226 +0,0 @@ ---- -name: 'step-v-01-discovery' -description: 'Document Discovery & Confirmation - Handle fresh context validation, confirm PRD path, discover input documents' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-02-format-detection.md' -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' -prdPurpose: '../data/prd-purpose.md' ---- - -# Step 1: Document Discovery & Confirmation - -## STEP GOAL: - -Handle fresh context validation by confirming PRD path, discovering and loading input documents from frontmatter, and initializing the validation report. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring systematic validation expertise and analytical rigor -- ✅ User brings domain knowledge and specific PRD context - -### Step-Specific Rules: - -- 🎯 Focus ONLY on discovering PRD and input documents, not validating yet -- 🚫 FORBIDDEN to perform any validation checks in this step -- 💬 Approach: Systematic discovery with clear reporting to user -- 🚪 This is the setup step - get everything ready for validation - -## EXECUTION PROTOCOLS: - -- 🎯 Discover and confirm PRD to validate -- 💾 Load PRD and all input documents from frontmatter -- 📖 Initialize validation report next to PRD -- 🚫 FORBIDDEN to load next step until user confirms setup - -## CONTEXT BOUNDARIES: - -- Available context: PRD path (user-specified or discovered), workflow configuration -- Focus: Document discovery and setup only -- Limits: Don't perform validation, don't skip discovery -- Dependencies: Configuration loaded from PRD workflow.md initialization - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Load PRD Purpose and Standards - -Load and read the complete file at: -`{prdPurpose}` - -This file contains the BMAD PRD philosophy, standards, and validation criteria that will guide all validation checks. Internalize this understanding - it defines what makes a great BMAD PRD. - -### 2. Discover PRD to Validate - -**If PRD path provided as invocation parameter:** -- Use provided path - -**If no PRD path provided, auto-discover:** -- Search `{planning_artifacts}` for files matching `*prd*.md` -- Also check for sharded PRDs: `{planning_artifacts}/*prd*/*.md` - -**If exactly ONE PRD found:** -- Use it automatically -- Inform user: "Found PRD: {discovered_path} — using it for validation." - -**If MULTIPLE PRDs found:** -- List all discovered PRDs with numbered options -- "I found multiple PRDs. Which one would you like to validate?" -- Wait for user selection - -**If NO PRDs found:** -- "I couldn't find any PRD files in {planning_artifacts}. Please provide the path to the PRD file you want to validate." -- Wait for user to provide PRD path. - -### 3. Validate PRD Exists and Load - -Once PRD path is provided: - -- Check if PRD file exists at specified path -- If not found: "I cannot find a PRD at that path. Please check the path and try again." -- If found: Load the complete PRD file including frontmatter - -### 4. Extract Frontmatter and Input Documents - -From the loaded PRD frontmatter, extract: - -- `inputDocuments: []` array (if present) -- Any other relevant metadata (classification, date, etc.) - -**If no inputDocuments array exists:** -Note this and proceed with PRD-only validation - -### 5. Load Input Documents - -For each document listed in `inputDocuments`: - -- Attempt to load the document -- Track successfully loaded documents -- Note any documents that fail to load - -**Build list of loaded input documents:** -- Product Brief (if present) -- Research documents (if present) -- Other reference materials (if present) - -### 6. Ask About Additional Reference Documents - -"**I've loaded the following documents from your PRD frontmatter:** - -{list loaded documents with file names} - -**Are there any additional reference documents you'd like me to include in this validation?** - -These could include: -- Additional research or context documents -- Project documentation not tracked in frontmatter -- Standards or compliance documents -- Competitive analysis or benchmarks - -Please provide paths to any additional documents, or type 'none' to proceed." - -**Load any additional documents provided by user.** - -### 7. Initialize Validation Report - -Create validation report at: `{validationReportPath}` - -**Initialize with frontmatter:** -```yaml ---- -validationTarget: '{prd_path}' -validationDate: '{current_date}' -inputDocuments: [list of all loaded documents] -validationStepsCompleted: [] -validationStatus: IN_PROGRESS ---- -``` - -**Initial content:** -```markdown -# PRD Validation Report - -**PRD Being Validated:** {prd_path} -**Validation Date:** {current_date} - -## Input Documents - -{list all documents loaded for validation} - -## Validation Findings - -[Findings will be appended as validation progresses] -``` - -### 8. Present Discovery Summary - -"**Setup Complete!** - -**PRD to Validate:** {prd_path} - -**Input Documents Loaded:** -- PRD: {prd_name} ✓ -- Product Brief: {count} {if count > 0}✓{else}(none found){/if} -- Research: {count} {if count > 0}✓{else}(none found){/if} -- Additional References: {count} {if count > 0}✓{else}(none){/if} - -**Validation Report:** {validationReportPath} - -**Ready to begin validation.**" - -### 9. Present MENU OPTIONS - -Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Format Detection - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- User can ask questions or add more documents - always respond and redisplay menu - -#### Menu Handling Logic: - -- IF A: Read fully and follow: {advancedElicitationTask}, and when finished redisplay the menu -- IF P: Read fully and follow: {partyModeWorkflow}, and when finished redisplay the menu -- IF C: Read fully and follow: {nextStepFile} to begin format detection -- IF user provides additional document: Load it, update report, redisplay summary -- IF Any other: help user, then redisplay menu - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- PRD path discovered and confirmed -- PRD file exists and loads successfully -- All input documents from frontmatter loaded -- Additional reference documents (if any) loaded -- Validation report initialized next to PRD -- User clearly informed of setup status -- Menu presented and user input handled correctly - -### ❌ SYSTEM FAILURE: - -- Proceeding with non-existent PRD file -- Not loading input documents from frontmatter -- Creating validation report in wrong location -- Proceeding without user confirming setup -- Not handling missing input documents gracefully - -**Master Rule:** Complete discovery and setup BEFORE validation. This step ensures everything is in place for systematic validation checks. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02-format-detection.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02-format-detection.md deleted file mode 100644 index a354b5aff..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02-format-detection.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -name: 'step-v-02-format-detection' -description: 'Format Detection & Structure Analysis - Classify PRD format and route appropriately' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-03-density-validation.md' -altStepFile: './step-v-02b-parity-check.md' -prdFile: '{prd_file_path}' -validationReportPath: '{validation_report_path}' ---- - -# Step 2: Format Detection & Structure Analysis - -## STEP GOAL: - -Detect if PRD follows BMAD format and route appropriately - classify as BMAD Standard / BMAD Variant / Non-Standard, with optional parity check for non-standard formats. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring systematic validation expertise and pattern recognition -- ✅ User brings domain knowledge and PRD context - -### Step-Specific Rules: - -- 🎯 Focus ONLY on detecting format and classifying structure -- 🚫 FORBIDDEN to perform other validation checks in this step -- 💬 Approach: Analytical and systematic, clear reporting of findings -- 🚪 This is a branch step - may route to parity check for non-standard PRDs - -## EXECUTION PROTOCOLS: - -- 🎯 Analyze PRD structure systematically -- 💾 Append format findings to validation report -- 📖 Route appropriately based on format classification -- 🚫 FORBIDDEN to skip format detection or proceed without classification - -## CONTEXT BOUNDARIES: - -- Available context: PRD file loaded in step 1, validation report initialized -- Focus: Format detection and classification only -- Limits: Don't perform other validation, don't skip classification -- Dependencies: Step 1 completed - PRD loaded and report initialized - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Extract PRD Structure - -Load the complete PRD file and extract: - -**All Level 2 (##) headers:** -- Scan through entire PRD document -- Extract all ## section headers -- List them in order - -**PRD frontmatter:** -- Extract classification.domain if present -- Extract classification.projectType if present -- Note any other relevant metadata - -### 2. Check for BMAD PRD Core Sections - -Check if the PRD contains the following BMAD PRD core sections: - -1. **Executive Summary** (or variations: ## Executive Summary, ## Overview, ## Introduction) -2. **Success Criteria** (or: ## Success Criteria, ## Goals, ## Objectives) -3. **Product Scope** (or: ## Product Scope, ## Scope, ## In Scope, ## Out of Scope) -4. **User Journeys** (or: ## User Journeys, ## User Stories, ## User Flows) -5. **Functional Requirements** (or: ## Functional Requirements, ## Features, ## Capabilities) -6. **Non-Functional Requirements** (or: ## Non-Functional Requirements, ## NFRs, ## Quality Attributes) - -**Count matches:** -- How many of these 6 core sections are present? -- Which specific sections are present? -- Which are missing? - -### 3. Classify PRD Format - -Based on core section count, classify: - -**BMAD Standard:** -- 5-6 core sections present -- Follows BMAD PRD structure closely - -**BMAD Variant:** -- 3-4 core sections present -- Generally follows BMAD patterns but may have structural differences -- Missing some sections but recognizable as BMAD-style - -**Non-Standard:** -- Fewer than 3 core sections present -- Does not follow BMAD PRD structure -- May be completely custom format, legacy format, or from another framework - -### 4. Report Format Findings to Validation Report - -Append to validation report: - -```markdown -## Format Detection - -**PRD Structure:** -[List all ## Level 2 headers found] - -**BMAD Core Sections Present:** -- Executive Summary: [Present/Missing] -- Success Criteria: [Present/Missing] -- Product Scope: [Present/Missing] -- User Journeys: [Present/Missing] -- Functional Requirements: [Present/Missing] -- Non-Functional Requirements: [Present/Missing] - -**Format Classification:** [BMAD Standard / BMAD Variant / Non-Standard] -**Core Sections Present:** [count]/6 -``` - -### 5. Route Based on Format Classification - -**IF format is BMAD Standard or BMAD Variant:** - -Display: "**Format Detected:** {classification} - -Proceeding to systematic validation checks..." - -Without delay, read fully and follow: {nextStepFile} (step-v-03-density-validation.md) - -**IF format is Non-Standard (< 3 core sections):** - -Display: "**Format Detected:** Non-Standard PRD - -This PRD does not follow BMAD standard structure (only {count}/6 core sections present). - -You have options:" - -Present MENU OPTIONS below for user selection - -### 6. Present MENU OPTIONS (Non-Standard PRDs Only) - -**[A] Parity Check** - Analyze gaps and estimate effort to reach BMAD PRD parity -**[B] Validate As-Is** - Proceed with validation using current structure -**[C] Exit** - Exit validation and review format findings - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input -- Only proceed based on user selection - -#### Menu Handling Logic: - -- IF A (Parity Check): Read fully and follow: {altStepFile} (step-v-02b-parity-check.md) -- IF B (Validate As-Is): Display "Proceeding with validation..." then read fully and follow: {nextStepFile} -- IF C (Exit): Display format findings summary and exit validation -- IF Any other: help user respond, then redisplay menu - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All ## Level 2 headers extracted successfully -- BMAD core sections checked systematically -- Format classified correctly based on section count -- Findings reported to validation report -- BMAD Standard/Variant PRDs proceed directly to next validation step -- Non-Standard PRDs pause and present options to user -- User can choose parity check, validate as-is, or exit - -### ❌ SYSTEM FAILURE: - -- Not extracting all headers before classification -- Incorrect format classification -- Not reporting findings to validation report -- Not pausing for non-standard PRDs -- Proceeding without user decision for non-standard formats - -**Master Rule:** Format detection determines validation path. Non-standard PRDs require user choice before proceeding. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02b-parity-check.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02b-parity-check.md deleted file mode 100644 index 604265a9a..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02b-parity-check.md +++ /dev/null @@ -1,209 +0,0 @@ ---- -name: 'step-v-02b-parity-check' -description: 'Document Parity Check - Analyze non-standard PRD and identify gaps to achieve BMAD PRD parity' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-03-density-validation.md' -prdFile: '{prd_file_path}' -validationReportPath: '{validation_report_path}' ---- - -# Step 2B: Document Parity Check - -## STEP GOAL: - -Analyze non-standard PRD and identify gaps to achieve BMAD PRD parity, presenting user with options for how to proceed. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring BMAD PRD standards expertise and gap analysis -- ✅ User brings domain knowledge and PRD context - -### Step-Specific Rules: - -- 🎯 Focus ONLY on analyzing gaps and estimating parity effort -- 🚫 FORBIDDEN to perform other validation checks in this step -- 💬 Approach: Systematic gap analysis with clear recommendations -- 🚪 This is an optional branch step - user chooses next action - -## EXECUTION PROTOCOLS: - -- 🎯 Analyze each BMAD PRD section for gaps -- 💾 Append parity analysis to validation report -- 📖 Present options and await user decision -- 🚫 FORBIDDEN to proceed without user selection - -## CONTEXT BOUNDARIES: - -- Available context: Non-standard PRD from step 2, validation report in progress -- Focus: Parity analysis only - what's missing, what's needed -- Limits: Don't perform validation checks, don't auto-proceed -- Dependencies: Step 2 classified PRD as non-standard and user chose parity check - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Analyze Each BMAD PRD Section - -For each of the 6 BMAD PRD core sections, analyze: - -**Executive Summary:** -- Does PRD have vision/overview? -- Is problem statement clear? -- Are target users identified? -- Gap: [What's missing or incomplete] - -**Success Criteria:** -- Are measurable goals defined? -- Is success clearly defined? -- Gap: [What's missing or incomplete] - -**Product Scope:** -- Is scope clearly defined? -- Are in-scope items listed? -- Are out-of-scope items listed? -- Gap: [What's missing or incomplete] - -**User Journeys:** -- Are user types/personas identified? -- Are user flows documented? -- Gap: [What's missing or incomplete] - -**Functional Requirements:** -- Are features/capabilities listed? -- Are requirements structured? -- Gap: [What's missing or incomplete] - -**Non-Functional Requirements:** -- Are quality attributes defined? -- Are performance/security/etc. requirements documented? -- Gap: [What's missing or incomplete] - -### 2. Estimate Effort to Reach Parity - -For each missing or incomplete section, estimate: - -**Effort Level:** -- Minimal - Section exists but needs minor enhancements -- Moderate - Section missing but content exists elsewhere in PRD -- Significant - Section missing, requires new content creation - -**Total Parity Effort:** -- Based on individual section estimates -- Classify overall: Quick / Moderate / Substantial effort - -### 3. Report Parity Analysis to Validation Report - -Append to validation report: - -```markdown -## Parity Analysis (Non-Standard PRD) - -### Section-by-Section Gap Analysis - -**Executive Summary:** -- Status: [Present/Missing/Incomplete] -- Gap: [specific gap description] -- Effort to Complete: [Minimal/Moderate/Significant] - -**Success Criteria:** -- Status: [Present/Missing/Incomplete] -- Gap: [specific gap description] -- Effort to Complete: [Minimal/Moderate/Significant] - -**Product Scope:** -- Status: [Present/Missing/Incomplete] -- Gap: [specific gap description] -- Effort to Complete: [Minimal/Moderate/Significant] - -**User Journeys:** -- Status: [Present/Missing/Incomplete] -- Gap: [specific gap description] -- Effort to Complete: [Minimal/Moderate/Significant] - -**Functional Requirements:** -- Status: [Present/Missing/Incomplete] -- Gap: [specific gap description] -- Effort to Complete: [Minimal/Moderate/Significant] - -**Non-Functional Requirements:** -- Status: [Present/Missing/Incomplete] -- Gap: [specific gap description] -- Effort to Complete: [Minimal/Moderate/Significant] - -### Overall Parity Assessment - -**Overall Effort to Reach BMAD Standard:** [Quick/Moderate/Substantial] -**Recommendation:** [Brief recommendation based on analysis] -``` - -### 4. Present Parity Analysis and Options - -Display: - -"**Parity Analysis Complete** - -Your PRD is missing {count} of 6 core BMAD PRD sections. The overall effort to reach BMAD standard is: **{effort level}** - -**Quick Summary:** -[2-3 sentence summary of key gaps] - -**Recommendation:** -{recommendation from analysis} - -**How would you like to proceed?**" - -### 5. Present MENU OPTIONS - -**[C] Continue Validation** - Proceed with validation using current structure -**[E] Exit & Review** - Exit validation and review parity report -**[S] Save & Exit** - Save parity report and exit - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input -- Only proceed based on user selection - -#### Menu Handling Logic: - -- IF C (Continue): Display "Proceeding with validation..." then read fully and follow: {nextStepFile} -- IF E (Exit): Display parity summary and exit validation -- IF S (Save): Confirm saved, display summary, exit -- IF Any other: help user respond, then redisplay menu - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All 6 BMAD PRD sections analyzed for gaps -- Effort estimates provided for each gap -- Overall parity effort assessed correctly -- Parity analysis reported to validation report -- Clear summary presented to user -- User can choose to continue validation, exit, or save report - -### ❌ SYSTEM FAILURE: - -- Not analyzing all 6 sections systematically -- Missing effort estimates -- Not reporting parity analysis to validation report -- Auto-proceeding without user decision -- Unclear recommendations - -**Master Rule:** Parity check informs user of gaps and effort, but user decides whether to proceed with validation or address gaps first. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-03-density-validation.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-03-density-validation.md deleted file mode 100644 index d00478c10..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-03-density-validation.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -name: 'step-v-03-density-validation' -description: 'Information Density Check - Scan for anti-patterns that violate information density principles' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-04-brief-coverage-validation.md' -prdFile: '{prd_file_path}' -validationReportPath: '{validation_report_path}' ---- - -# Step 3: Information Density Validation - -## STEP GOAL: - -Validate PRD meets BMAD information density standards by scanning for conversational filler, wordy phrases, and redundant expressions that violate conciseness principles. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in systematic validation, not collaborative dialogue -- ✅ You bring analytical rigor and attention to detail -- ✅ This step runs autonomously - no user input needed - -### Step-Specific Rules: - -- 🎯 Focus ONLY on information density anti-patterns -- 🚫 FORBIDDEN to validate other aspects in this step -- 💬 Approach: Systematic scanning and categorization -- 🚪 This is a validation sequence step - auto-proceeds when complete - -## EXECUTION PROTOCOLS: - -- 🎯 Scan PRD for density anti-patterns systematically -- 💾 Append density findings to validation report -- 📖 Display "Proceeding to next check..." and load next step -- 🚫 FORBIDDEN to pause or request user input - -## CONTEXT BOUNDARIES: - -- Available context: PRD file, validation report with format findings -- Focus: Information density validation only -- Limits: Don't validate other aspects, don't pause for user input -- Dependencies: Step 2 completed - format classification done - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Attempt Sub-Process Validation - -**Try to use Task tool to spawn a subprocess:** - -"Perform information density validation on this PRD: - -1. Load the PRD file -2. Scan for the following anti-patterns: - - Conversational filler phrases (examples: 'The system will allow users to...', 'It is important to note that...', 'In order to') - - Wordy phrases (examples: 'Due to the fact that', 'In the event of', 'For the purpose of') - - Redundant phrases (examples: 'Future plans', 'Absolutely essential', 'Past history') -3. Count violations by category with line numbers -4. Classify severity: Critical (>10 violations), Warning (5-10), Pass (<5) - -Return structured findings with counts and examples." - -### 2. Graceful Degradation (if Task tool unavailable) - -If Task tool unavailable, perform analysis directly: - -**Scan for conversational filler patterns:** -- "The system will allow users to..." -- "It is important to note that..." -- "In order to" -- "For the purpose of" -- "With regard to" -- Count occurrences and note line numbers - -**Scan for wordy phrases:** -- "Due to the fact that" (use "because") -- "In the event of" (use "if") -- "At this point in time" (use "now") -- "In a manner that" (use "how") -- Count occurrences and note line numbers - -**Scan for redundant phrases:** -- "Future plans" (just "plans") -- "Past history" (just "history") -- "Absolutely essential" (just "essential") -- "Completely finish" (just "finish") -- Count occurrences and note line numbers - -### 3. Classify Severity - -**Calculate total violations:** -- Conversational filler count -- Wordy phrases count -- Redundant phrases count -- Total = sum of all categories - -**Determine severity:** -- **Critical:** Total > 10 violations -- **Warning:** Total 5-10 violations -- **Pass:** Total < 5 violations - -### 4. Report Density Findings to Validation Report - -Append to validation report: - -```markdown -## Information Density Validation - -**Anti-Pattern Violations:** - -**Conversational Filler:** {count} occurrences -[If count > 0, list examples with line numbers] - -**Wordy Phrases:** {count} occurrences -[If count > 0, list examples with line numbers] - -**Redundant Phrases:** {count} occurrences -[If count > 0, list examples with line numbers] - -**Total Violations:** {total} - -**Severity Assessment:** [Critical/Warning/Pass] - -**Recommendation:** -[If Critical] "PRD requires significant revision to improve information density. Every sentence should carry weight without filler." -[If Warning] "PRD would benefit from reducing wordiness and eliminating filler phrases." -[If Pass] "PRD demonstrates good information density with minimal violations." -``` - -### 5. Display Progress and Auto-Proceed - -Display: "**Information Density Validation Complete** - -Severity: {Critical/Warning/Pass} - -**Proceeding to next validation check...**" - -Without delay, read fully and follow: {nextStepFile} (step-v-04-brief-coverage-validation.md) - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- PRD scanned for all three anti-pattern categories -- Violations counted with line numbers -- Severity classified correctly -- Findings reported to validation report -- Auto-proceeds to next validation step -- Subprocess attempted with graceful degradation - -### ❌ SYSTEM FAILURE: - -- Not scanning all anti-pattern categories -- Missing severity classification -- Not reporting findings to validation report -- Pausing for user input (should auto-proceed) -- Not attempting subprocess architecture - -**Master Rule:** Information density validation runs autonomously. Scan, classify, report, auto-proceed. No user interaction needed. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-04-brief-coverage-validation.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-04-brief-coverage-validation.md deleted file mode 100644 index 60ad8684f..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-04-brief-coverage-validation.md +++ /dev/null @@ -1,214 +0,0 @@ ---- -name: 'step-v-04-brief-coverage-validation' -description: 'Product Brief Coverage Check - Validate PRD covers all content from Product Brief (if used as input)' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-05-measurability-validation.md' -prdFile: '{prd_file_path}' -productBrief: '{product_brief_path}' -validationReportPath: '{validation_report_path}' ---- - -# Step 4: Product Brief Coverage Validation - -## STEP GOAL: - -Validate that PRD covers all content from Product Brief (if brief was used as input), mapping brief content to PRD sections and identifying gaps. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in systematic validation, not collaborative dialogue -- ✅ You bring analytical rigor and traceability expertise -- ✅ This step runs autonomously - no user input needed - -### Step-Specific Rules: - -- 🎯 Focus ONLY on Product Brief coverage (conditional on brief existence) -- 🚫 FORBIDDEN to validate other aspects in this step -- 💬 Approach: Systematic mapping and gap analysis -- 🚪 This is a validation sequence step - auto-proceeds when complete - -## EXECUTION PROTOCOLS: - -- 🎯 Check if Product Brief exists in input documents -- 💬 If no brief: Skip this check and report "N/A - No Product Brief" -- 🎯 If brief exists: Map brief content to PRD sections -- 💾 Append coverage findings to validation report -- 📖 Display "Proceeding to next check..." and load next step -- 🚫 FORBIDDEN to pause or request user input - -## CONTEXT BOUNDARIES: - -- Available context: PRD file, input documents from step 1, validation report -- Focus: Product Brief coverage only (conditional) -- Limits: Don't validate other aspects, conditional execution -- Dependencies: Step 1 completed - input documents loaded - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Check for Product Brief - -Check if Product Brief was loaded in step 1's inputDocuments: - -**IF no Product Brief found:** -Append to validation report: -```markdown -## Product Brief Coverage - -**Status:** N/A - No Product Brief was provided as input -``` - -Display: "**Product Brief Coverage: Skipped** (No Product Brief provided) - -**Proceeding to next validation check...**" - -Without delay, read fully and follow: {nextStepFile} - -**IF Product Brief exists:** Continue to step 2 below - -### 2. Attempt Sub-Process Validation - -**Try to use Task tool to spawn a subprocess:** - -"Perform Product Brief coverage validation: - -1. Load the Product Brief -2. Extract key content: - - Vision statement - - Target users/personas - - Problem statement - - Key features - - Goals/objectives - - Differentiators - - Constraints -3. For each item, search PRD for corresponding coverage -4. Classify coverage: Fully Covered / Partially Covered / Not Found / Intentionally Excluded -5. Note any gaps with severity: Critical / Moderate / Informational - -Return structured coverage map with classifications." - -### 3. Graceful Degradation (if Task tool unavailable) - -If Task tool unavailable, perform analysis directly: - -**Extract from Product Brief:** -- Vision: What is this product? -- Users: Who is it for? -- Problem: What problem does it solve? -- Features: What are the key capabilities? -- Goals: What are the success criteria? -- Differentiators: What makes it unique? - -**For each item, search PRD:** -- Scan Executive Summary for vision -- Check User Journeys or user personas -- Look for problem statement -- Review Functional Requirements for features -- Check Success Criteria section -- Search for differentiators - -**Classify coverage:** -- **Fully Covered:** Content present and complete -- **Partially Covered:** Content present but incomplete -- **Not Found:** Content missing from PRD -- **Intentionally Excluded:** Content explicitly out of scope - -### 4. Assess Coverage and Severity - -**For each gap (Partially Covered or Not Found):** -- Is this Critical? (Core vision, primary users, main features) -- Is this Moderate? (Secondary features, some goals) -- Is this Informational? (Nice-to-have features, minor details) - -**Note:** Some exclusions may be intentional (valid scoping decisions) - -### 5. Report Coverage Findings to Validation Report - -Append to validation report: - -```markdown -## Product Brief Coverage - -**Product Brief:** {brief_file_name} - -### Coverage Map - -**Vision Statement:** [Fully/Partially/Not Found/Intentionally Excluded] -[If gap: Note severity and specific missing content] - -**Target Users:** [Fully/Partially/Not Found/Intentionally Excluded] -[If gap: Note severity and specific missing content] - -**Problem Statement:** [Fully/Partially/Not Found/Intentionally Excluded] -[If gap: Note severity and specific missing content] - -**Key Features:** [Fully/Partially/Not Found/Intentionally Excluded] -[If gap: List specific features with severity] - -**Goals/Objectives:** [Fully/Partially/Not Found/Intentionally Excluded] -[If gap: Note severity and specific missing content] - -**Differentiators:** [Fully/Partially/Not Found/Intentionally Excluded] -[If gap: Note severity and specific missing content] - -### Coverage Summary - -**Overall Coverage:** [percentage or qualitative assessment] -**Critical Gaps:** [count] [list if any] -**Moderate Gaps:** [count] [list if any] -**Informational Gaps:** [count] [list if any] - -**Recommendation:** -[If critical gaps exist] "PRD should be revised to cover critical Product Brief content." -[If moderate gaps] "Consider addressing moderate gaps for complete coverage." -[If minimal gaps] "PRD provides good coverage of Product Brief content." -``` - -### 6. Display Progress and Auto-Proceed - -Display: "**Product Brief Coverage Validation Complete** - -Overall Coverage: {assessment} - -**Proceeding to next validation check...**" - -Without delay, read fully and follow: {nextStepFile} (step-v-05-measurability-validation.md) - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Checked for Product Brief existence correctly -- If no brief: Reported "N/A" and skipped gracefully -- If brief exists: Mapped all key brief content to PRD sections -- Coverage classified appropriately (Fully/Partially/Not Found/Intentionally Excluded) -- Severity assessed for gaps (Critical/Moderate/Informational) -- Findings reported to validation report -- Auto-proceeds to next validation step -- Subprocess attempted with graceful degradation - -### ❌ SYSTEM FAILURE: - -- Not checking for brief existence before attempting validation -- If brief exists: not mapping all key content areas -- Missing coverage classifications -- Not reporting findings to validation report -- Not auto-proceeding - -**Master Rule:** Product Brief coverage is conditional - skip if no brief, validate thoroughly if brief exists. Always auto-proceed. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-05-measurability-validation.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-05-measurability-validation.md deleted file mode 100644 index a97187184..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-05-measurability-validation.md +++ /dev/null @@ -1,228 +0,0 @@ ---- -name: 'step-v-05-measurability-validation' -description: 'Measurability Validation - Validate that all requirements (FRs and NFRs) are measurable and testable' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-06-traceability-validation.md' -prdFile: '{prd_file_path}' -validationReportPath: '{validation_report_path}' ---- - -# Step 5: Measurability Validation - -## STEP GOAL: - -Validate that all Functional Requirements (FRs) and Non-Functional Requirements (NFRs) are measurable, testable, and follow proper format without implementation details. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in systematic validation, not collaborative dialogue -- ✅ You bring analytical rigor and requirements engineering expertise -- ✅ This step runs autonomously - no user input needed - -### Step-Specific Rules: - -- 🎯 Focus ONLY on FR and NFR measurability -- 🚫 FORBIDDEN to validate other aspects in this step -- 💬 Approach: Systematic requirement-by-requirement analysis -- 🚪 This is a validation sequence step - auto-proceeds when complete - -## EXECUTION PROTOCOLS: - -- 🎯 Extract all FRs and NFRs from PRD -- 💾 Validate each for measurability and format -- 📖 Append findings to validation report -- 📖 Display "Proceeding to next check..." and load next step -- 🚫 FORBIDDEN to pause or request user input - -## CONTEXT BOUNDARIES: - -- Available context: PRD file, validation report -- Focus: FR and NFR measurability only -- Limits: Don't validate other aspects, don't pause for user input -- Dependencies: Steps 2-4 completed - initial validation checks done - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Attempt Sub-Process Validation - -**Try to use Task tool to spawn a subprocess:** - -"Perform measurability validation on this PRD: - -**Functional Requirements (FRs):** -1. Extract all FRs from Functional Requirements section -2. Check each FR for: - - '[Actor] can [capability]' format compliance - - No subjective adjectives (easy, fast, simple, intuitive, etc.) - - No vague quantifiers (multiple, several, some, many, etc.) - - No implementation details (technology names, library names, data structures unless capability-relevant) -3. Document violations with line numbers - -**Non-Functional Requirements (NFRs):** -1. Extract all NFRs from Non-Functional Requirements section -2. Check each NFR for: - - Specific metrics with measurement methods - - Template compliance (criterion, metric, measurement method, context) - - Context included (why this matters, who it affects) -3. Document violations with line numbers - -Return structured findings with violation counts and examples." - -### 2. Graceful Degradation (if Task tool unavailable) - -If Task tool unavailable, perform analysis directly: - -**Functional Requirements Analysis:** - -Extract all FRs and check each for: - -**Format compliance:** -- Does it follow "[Actor] can [capability]" pattern? -- Is actor clearly defined? -- Is capability actionable and testable? - -**No subjective adjectives:** -- Scan for: easy, fast, simple, intuitive, user-friendly, responsive, quick, efficient (without metrics) -- Note line numbers - -**No vague quantifiers:** -- Scan for: multiple, several, some, many, few, various, number of -- Note line numbers - -**No implementation details:** -- Scan for: React, Vue, Angular, PostgreSQL, MongoDB, AWS, Docker, Kubernetes, Redux, etc. -- Unless capability-relevant (e.g., "API consumers can access...") -- Note line numbers - -**Non-Functional Requirements Analysis:** - -Extract all NFRs and check each for: - -**Specific metrics:** -- Is there a measurable criterion? (e.g., "response time < 200ms", not "fast response") -- Can this be measured or tested? - -**Template compliance:** -- Criterion defined? -- Metric specified? -- Measurement method included? -- Context provided? - -### 3. Tally Violations - -**FR Violations:** -- Format violations: count -- Subjective adjectives: count -- Vague quantifiers: count -- Implementation leakage: count -- Total FR violations: sum - -**NFR Violations:** -- Missing metrics: count -- Incomplete template: count -- Missing context: count -- Total NFR violations: sum - -**Total violations:** FR violations + NFR violations - -### 4. Report Measurability Findings to Validation Report - -Append to validation report: - -```markdown -## Measurability Validation - -### Functional Requirements - -**Total FRs Analyzed:** {count} - -**Format Violations:** {count} -[If violations exist, list examples with line numbers] - -**Subjective Adjectives Found:** {count} -[If found, list examples with line numbers] - -**Vague Quantifiers Found:** {count} -[If found, list examples with line numbers] - -**Implementation Leakage:** {count} -[If found, list examples with line numbers] - -**FR Violations Total:** {total} - -### Non-Functional Requirements - -**Total NFRs Analyzed:** {count} - -**Missing Metrics:** {count} -[If missing, list examples with line numbers] - -**Incomplete Template:** {count} -[If incomplete, list examples with line numbers] - -**Missing Context:** {count} -[If missing, list examples with line numbers] - -**NFR Violations Total:** {total} - -### Overall Assessment - -**Total Requirements:** {FRs + NFRs} -**Total Violations:** {FR violations + NFR violations} - -**Severity:** [Critical if >10 violations, Warning if 5-10, Pass if <5] - -**Recommendation:** -[If Critical] "Many requirements are not measurable or testable. Requirements must be revised to be testable for downstream work." -[If Warning] "Some requirements need refinement for measurability. Focus on violating requirements above." -[If Pass] "Requirements demonstrate good measurability with minimal issues." -``` - -### 5. Display Progress and Auto-Proceed - -Display: "**Measurability Validation Complete** - -Total Violations: {count} ({severity}) - -**Proceeding to next validation check...**" - -Without delay, read fully and follow: {nextStepFile} (step-v-06-traceability-validation.md) - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All FRs extracted and analyzed for measurability -- All NFRs extracted and analyzed for measurability -- Violations documented with line numbers -- Severity assessed correctly -- Findings reported to validation report -- Auto-proceeds to next validation step -- Subprocess attempted with graceful degradation - -### ❌ SYSTEM FAILURE: - -- Not analyzing all FRs and NFRs -- Missing line numbers for violations -- Not reporting findings to validation report -- Not assessing severity -- Not auto-proceeding - -**Master Rule:** Requirements must be testable to be useful. Validate every requirement for measurability, document violations, auto-proceed. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-06-traceability-validation.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-06-traceability-validation.md deleted file mode 100644 index 84bf9cce9..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-06-traceability-validation.md +++ /dev/null @@ -1,217 +0,0 @@ ---- -name: 'step-v-06-traceability-validation' -description: 'Traceability Validation - Validate the traceability chain from vision → success → journeys → FRs is intact' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-07-implementation-leakage-validation.md' -prdFile: '{prd_file_path}' -validationReportPath: '{validation_report_path}' ---- - -# Step 6: Traceability Validation - -## STEP GOAL: - -Validate the traceability chain from Executive Summary → Success Criteria → User Journeys → Functional Requirements is intact, ensuring every requirement traces back to a user need or business objective. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in systematic validation, not collaborative dialogue -- ✅ You bring analytical rigor and traceability matrix expertise -- ✅ This step runs autonomously - no user input needed - -### Step-Specific Rules: - -- 🎯 Focus ONLY on traceability chain validation -- 🚫 FORBIDDEN to validate other aspects in this step -- 💬 Approach: Systematic chain validation and orphan detection -- 🚪 This is a validation sequence step - auto-proceeds when complete - -## EXECUTION PROTOCOLS: - -- 🎯 Build and validate traceability matrix -- 💾 Identify broken chains and orphan requirements -- 📖 Append findings to validation report -- 📖 Display "Proceeding to next check..." and load next step -- 🚫 FORBIDDEN to pause or request user input - -## CONTEXT BOUNDARIES: - -- Available context: PRD file, validation report -- Focus: Traceability chain validation only -- Limits: Don't validate other aspects, don't pause for user input -- Dependencies: Steps 2-5 completed - initial validations done - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Attempt Sub-Process Validation - -**Try to use Task tool to spawn a subprocess:** - -"Perform traceability validation on this PRD: - -1. Extract content from Executive Summary (vision, goals) -2. Extract Success Criteria -3. Extract User Journeys (user types, flows, outcomes) -4. Extract Functional Requirements (FRs) -5. Extract Product Scope (in-scope items) - -**Validate chains:** -- Executive Summary → Success Criteria: Does vision align with defined success? -- Success Criteria → User Journeys: Are success criteria supported by user journeys? -- User Journeys → Functional Requirements: Does each FR trace back to a user journey? -- Scope → FRs: Do MVP scope FRs align with in-scope items? - -**Identify orphans:** -- FRs not traceable to any user journey or business objective -- Success criteria not supported by user journeys -- User journeys without supporting FRs - -Build traceability matrix and identify broken chains and orphan FRs. - -Return structured findings with chain status and orphan list." - -### 2. Graceful Degradation (if Task tool unavailable) - -If Task tool unavailable, perform analysis directly: - -**Step 1: Extract key elements** -- Executive Summary: Note vision, goals, objectives -- Success Criteria: List all criteria -- User Journeys: List user types and their flows -- Functional Requirements: List all FRs -- Product Scope: List in-scope items - -**Step 2: Validate Executive Summary → Success Criteria** -- Does Executive Summary mention the success dimensions? -- Are Success Criteria aligned with vision? -- Note any misalignment - -**Step 3: Validate Success Criteria → User Journeys** -- For each success criterion, is there a user journey that achieves it? -- Note success criteria without supporting journeys - -**Step 4: Validate User Journeys → FRs** -- For each user journey/flow, are there FRs that enable it? -- List FRs with no clear user journey origin -- Note orphan FRs (requirements without traceable source) - -**Step 5: Validate Scope → FR Alignment** -- Does MVP scope align with essential FRs? -- Are in-scope items supported by FRs? -- Note misalignments - -**Step 6: Build traceability matrix** -- Map each FR to its source (journey or business objective) -- Note orphan FRs -- Identify broken chains - -### 3. Tally Traceability Issues - -**Broken chains:** -- Executive Summary → Success Criteria gaps: count -- Success Criteria → User Journeys gaps: count -- User Journeys → FRs gaps: count -- Scope → FR misalignments: count - -**Orphan elements:** -- Orphan FRs (no traceable source): count -- Unsupported success criteria: count -- User journeys without FRs: count - -**Total issues:** Sum of all broken chains and orphans - -### 4. Report Traceability Findings to Validation Report - -Append to validation report: - -```markdown -## Traceability Validation - -### Chain Validation - -**Executive Summary → Success Criteria:** [Intact/Gaps Identified] -{If gaps: List specific misalignments} - -**Success Criteria → User Journeys:** [Intact/Gaps Identified] -{If gaps: List unsupported success criteria} - -**User Journeys → Functional Requirements:** [Intact/Gaps Identified] -{If gaps: List journeys without supporting FRs} - -**Scope → FR Alignment:** [Intact/Misaligned] -{If misaligned: List specific issues} - -### Orphan Elements - -**Orphan Functional Requirements:** {count} -{List orphan FRs with numbers} - -**Unsupported Success Criteria:** {count} -{List unsupported criteria} - -**User Journeys Without FRs:** {count} -{List journeys without FRs} - -### Traceability Matrix - -{Summary table showing traceability coverage} - -**Total Traceability Issues:** {total} - -**Severity:** [Critical if orphan FRs exist, Warning if gaps, Pass if intact] - -**Recommendation:** -[If Critical] "Orphan requirements exist - every FR must trace back to a user need or business objective." -[If Warning] "Traceability gaps identified - strengthen chains to ensure all requirements are justified." -[If Pass] "Traceability chain is intact - all requirements trace to user needs or business objectives." -``` - -### 5. Display Progress and Auto-Proceed - -Display: "**Traceability Validation Complete** - -Total Issues: {count} ({severity}) - -**Proceeding to next validation check...**" - -Without delay, read fully and follow: {nextStepFile} (step-v-07-implementation-leakage-validation.md) - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All traceability chains validated systematically -- Orphan FRs identified with numbers -- Broken chains documented -- Traceability matrix built -- Severity assessed correctly -- Findings reported to validation report -- Auto-proceeds to next validation step -- Subprocess attempted with graceful degradation - -### ❌ SYSTEM FAILURE: - -- Not validating all traceability chains -- Missing orphan FR detection -- Not building traceability matrix -- Not reporting findings to validation report -- Not auto-proceeding - -**Master Rule:** Every requirement should trace to a user need or business objective. Orphan FRs indicate broken traceability that must be fixed. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-07-implementation-leakage-validation.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-07-implementation-leakage-validation.md deleted file mode 100644 index 923f99691..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-07-implementation-leakage-validation.md +++ /dev/null @@ -1,205 +0,0 @@ ---- -name: 'step-v-07-implementation-leakage-validation' -description: 'Implementation Leakage Check - Ensure FRs and NFRs don\'t include implementation details' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-08-domain-compliance-validation.md' -prdFile: '{prd_file_path}' -validationReportPath: '{validation_report_path}' ---- - -# Step 7: Implementation Leakage Validation - -## STEP GOAL: - -Ensure Functional Requirements and Non-Functional Requirements don't include implementation details - they should specify WHAT, not HOW. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in systematic validation, not collaborative dialogue -- ✅ You bring analytical rigor and separation of concerns expertise -- ✅ This step runs autonomously - no user input needed - -### Step-Specific Rules: - -- 🎯 Focus ONLY on implementation leakage detection -- 🚫 FORBIDDEN to validate other aspects in this step -- 💬 Approach: Systematic scanning for technology and implementation terms -- 🚪 This is a validation sequence step - auto-proceeds when complete - -## EXECUTION PROTOCOLS: - -- 🎯 Scan FRs and NFRs for implementation terms -- 💾 Distinguish capability-relevant vs leakage -- 📖 Append findings to validation report -- 📖 Display "Proceeding to next check..." and load next step -- 🚫 FORBIDDEN to pause or request user input - -## CONTEXT BOUNDARIES: - -- Available context: PRD file, validation report -- Focus: Implementation leakage detection only -- Limits: Don't validate other aspects, don't pause for user input -- Dependencies: Steps 2-6 completed - initial validations done - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Attempt Sub-Process Validation - -**Try to use Task tool to spawn a subprocess:** - -"Perform implementation leakage validation on this PRD: - -**Scan for:** -1. Technology names (React, Vue, Angular, PostgreSQL, MongoDB, AWS, GCP, Azure, Docker, Kubernetes, etc.) -2. Library names (Redux, axios, lodash, Express, Django, Rails, Spring, etc.) -3. Data structures (JSON, XML, CSV) unless relevant to capability -4. Architecture patterns (MVC, microservices, serverless) unless business requirement -5. Protocol names (HTTP, REST, GraphQL, WebSockets) - check if capability-relevant - -**For each term found:** -- Is this capability-relevant? (e.g., 'API consumers can access...' - API is capability) -- Or is this implementation detail? (e.g., 'React component for...' - implementation) - -Document violations with line numbers and explanation. - -Return structured findings with leakage counts and examples." - -### 2. Graceful Degradation (if Task tool unavailable) - -If Task tool unavailable, perform analysis directly: - -**Implementation leakage terms to scan for:** - -**Frontend Frameworks:** -React, Vue, Angular, Svelte, Solid, Next.js, Nuxt, etc. - -**Backend Frameworks:** -Express, Django, Rails, Spring, Laravel, FastAPI, etc. - -**Databases:** -PostgreSQL, MySQL, MongoDB, Redis, DynamoDB, Cassandra, etc. - -**Cloud Platforms:** -AWS, GCP, Azure, Cloudflare, Vercel, Netlify, etc. - -**Infrastructure:** -Docker, Kubernetes, Terraform, Ansible, etc. - -**Libraries:** -Redux, Zustand, axios, fetch, lodash, jQuery, etc. - -**Data Formats:** -JSON, XML, YAML, CSV (unless capability-relevant) - -**For each term found in FRs/NFRs:** -- Determine if it's capability-relevant or implementation leakage -- Example: "API consumers can access data via REST endpoints" - API/REST is capability -- Example: "React components fetch data using Redux" - implementation leakage - -**Count violations and note line numbers** - -### 3. Tally Implementation Leakage - -**By category:** -- Frontend framework leakage: count -- Backend framework leakage: count -- Database leakage: count -- Cloud platform leakage: count -- Infrastructure leakage: count -- Library leakage: count -- Other implementation details: count - -**Total implementation leakage violations:** sum - -### 4. Report Implementation Leakage Findings to Validation Report - -Append to validation report: - -```markdown -## Implementation Leakage Validation - -### Leakage by Category - -**Frontend Frameworks:** {count} violations -{If violations, list examples with line numbers} - -**Backend Frameworks:** {count} violations -{If violations, list examples with line numbers} - -**Databases:** {count} violations -{If violations, list examples with line numbers} - -**Cloud Platforms:** {count} violations -{If violations, list examples with line numbers} - -**Infrastructure:** {count} violations -{If violations, list examples with line numbers} - -**Libraries:** {count} violations -{If violations, list examples with line numbers} - -**Other Implementation Details:** {count} violations -{If violations, list examples with line numbers} - -### Summary - -**Total Implementation Leakage Violations:** {total} - -**Severity:** [Critical if >5 violations, Warning if 2-5, Pass if <2] - -**Recommendation:** -[If Critical] "Extensive implementation leakage found. Requirements specify HOW instead of WHAT. Remove all implementation details - these belong in architecture, not PRD." -[If Warning] "Some implementation leakage detected. Review violations and remove implementation details from requirements." -[If Pass] "No significant implementation leakage found. Requirements properly specify WHAT without HOW." - -**Note:** API consumers, GraphQL (when required), and other capability-relevant terms are acceptable when they describe WHAT the system must do, not HOW to build it. -``` - -### 5. Display Progress and Auto-Proceed - -Display: "**Implementation Leakage Validation Complete** - -Total Violations: {count} ({severity}) - -**Proceeding to next validation check...**" - -Without delay, read fully and follow: {nextStepFile} (step-v-08-domain-compliance-validation.md) - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Scanned FRs and NFRs for all implementation term categories -- Distinguished capability-relevant from implementation leakage -- Violations documented with line numbers and explanations -- Severity assessed correctly -- Findings reported to validation report -- Auto-proceeds to next validation step -- Subprocess attempted with graceful degradation - -### ❌ SYSTEM FAILURE: - -- Not scanning all implementation term categories -- Not distinguishing capability-relevant from leakage -- Missing line numbers for violations -- Not reporting findings to validation report -- Not auto-proceeding - -**Master Rule:** Requirements specify WHAT, not HOW. Implementation details belong in architecture documents, not PRDs. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-08-domain-compliance-validation.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-08-domain-compliance-validation.md deleted file mode 100644 index 562697eda..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-08-domain-compliance-validation.md +++ /dev/null @@ -1,243 +0,0 @@ ---- -name: 'step-v-08-domain-compliance-validation' -description: 'Domain Compliance Validation - Validate domain-specific requirements are present for high-complexity domains' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-09-project-type-validation.md' -prdFile: '{prd_file_path}' -prdFrontmatter: '{prd_frontmatter}' -validationReportPath: '{validation_report_path}' -domainComplexityData: '../data/domain-complexity.csv' ---- - -# Step 8: Domain Compliance Validation - -## STEP GOAL: - -Validate domain-specific requirements are present for high-complexity domains (Healthcare, Fintech, GovTech, etc.), ensuring regulatory and compliance requirements are properly documented. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in systematic validation, not collaborative dialogue -- ✅ You bring domain expertise and compliance knowledge -- ✅ This step runs autonomously - no user input needed - -### Step-Specific Rules: - -- 🎯 Focus ONLY on domain-specific compliance requirements -- 🚫 FORBIDDEN to validate other aspects in this step -- 💬 Approach: Conditional validation based on domain classification -- 🚪 This is a validation sequence step - auto-proceeds when complete - -## EXECUTION PROTOCOLS: - -- 🎯 Check classification.domain from PRD frontmatter -- 💬 If low complexity (general): Skip detailed checks -- 🎯 If high complexity: Validate required special sections -- 💾 Append compliance findings to validation report -- 📖 Display "Proceeding to next check..." and load next step -- 🚫 FORBIDDEN to pause or request user input - -## CONTEXT BOUNDARIES: - -- Available context: PRD file with frontmatter classification, validation report -- Focus: Domain compliance only (conditional on domain complexity) -- Limits: Don't validate other aspects, conditional execution -- Dependencies: Steps 2-7 completed - format and requirements validation done - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Load Domain Complexity Data - -Load and read the complete file at: -`{domainComplexityData}` (../data/domain-complexity.csv) - -This CSV contains: -- Domain classifications and complexity levels (high/medium/low) -- Required special sections for each domain -- Key concerns and requirements for regulated industries - -Internalize this data - it drives which domains require special compliance sections. - -### 2. Extract Domain Classification - -From PRD frontmatter, extract: -- `classification.domain` - what domain is this PRD for? - -**If no domain classification found:** -Treat as "general" (low complexity) and proceed to step 4 - -### 2. Determine Domain Complexity - -**Low complexity domains (skip detailed checks):** -- General -- Consumer apps (standard e-commerce, social, productivity) -- Content websites -- Business tools (standard) - -**High complexity domains (require special sections):** -- Healthcare / Healthtech -- Fintech / Financial services -- GovTech / Public sector -- EdTech (educational records, accredited courses) -- Legal tech -- Other regulated domains - -### 3. For High-Complexity Domains: Validate Required Special Sections - -**Attempt subprocess validation:** - -"Perform domain compliance validation for {domain}: - -Based on {domain} requirements, check PRD for: - -**Healthcare:** -- Clinical Requirements section -- Regulatory Pathway (FDA, HIPAA, etc.) -- Safety Measures -- HIPAA Compliance (data privacy, security) -- Patient safety considerations - -**Fintech:** -- Compliance Matrix (SOC2, PCI-DSS, GDPR, etc.) -- Security Architecture -- Audit Requirements -- Fraud Prevention measures -- Financial transaction handling - -**GovTech:** -- Accessibility Standards (WCAG 2.1 AA, Section 508) -- Procurement Compliance -- Security Clearance requirements -- Data residency requirements - -**Other regulated domains:** -- Check for domain-specific regulatory sections -- Compliance requirements -- Special considerations - -For each required section: -- Is it present in PRD? -- Is it adequately documented? -- Note any gaps - -Return compliance matrix with presence/adequacy assessment." - -**Graceful degradation (if no Task tool):** -- Manually check for required sections based on domain -- List present sections and missing sections -- Assess adequacy of documentation - -### 5. For Low-Complexity Domains: Skip Detailed Checks - -Append to validation report: -```markdown -## Domain Compliance Validation - -**Domain:** {domain} -**Complexity:** Low (general/standard) -**Assessment:** N/A - No special domain compliance requirements - -**Note:** This PRD is for a standard domain without regulatory compliance requirements. -``` - -Display: "**Domain Compliance Validation Skipped** - -Domain: {domain} (low complexity) - -**Proceeding to next validation check...**" - -Without delay, read fully and follow: {nextStepFile} - -### 6. Report Compliance Findings (High-Complexity Domains) - -Append to validation report: - -```markdown -## Domain Compliance Validation - -**Domain:** {domain} -**Complexity:** High (regulated) - -### Required Special Sections - -**{Section 1 Name}:** [Present/Missing/Adequate] -{If missing or inadequate: Note specific gaps} - -**{Section 2 Name}:** [Present/Missing/Adequate] -{If missing or inadequate: Note specific gaps} - -[Continue for all required sections] - -### Compliance Matrix - -| Requirement | Status | Notes | -|-------------|--------|-------| -| {Requirement 1} | [Met/Partial/Missing] | {Notes} | -| {Requirement 2} | [Met/Partial/Missing] | {Notes} | -[... continue for all requirements] - -### Summary - -**Required Sections Present:** {count}/{total} -**Compliance Gaps:** {count} - -**Severity:** [Critical if missing regulatory sections, Warning if incomplete, Pass if complete] - -**Recommendation:** -[If Critical] "PRD is missing required domain-specific compliance sections. These are essential for {domain} products." -[If Warning] "Some domain compliance sections are incomplete. Strengthen documentation for full compliance." -[If Pass] "All required domain compliance sections are present and adequately documented." -``` - -### 7. Display Progress and Auto-Proceed - -Display: "**Domain Compliance Validation Complete** - -Domain: {domain} ({complexity}) -Compliance Status: {status} - -**Proceeding to next validation check...**" - -Without delay, read fully and follow: {nextStepFile} (step-v-09-project-type-validation.md) - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Domain classification extracted correctly -- Complexity assessed appropriately -- Low complexity domains: Skipped with clear "N/A" documentation -- High complexity domains: All required sections checked -- Compliance matrix built with status for each requirement -- Severity assessed correctly -- Findings reported to validation report -- Auto-proceeds to next validation step -- Subprocess attempted with graceful degradation - -### ❌ SYSTEM FAILURE: - -- Not checking domain classification before proceeding -- Performing detailed checks on low complexity domains -- For high complexity: missing required section checks -- Not building compliance matrix -- Not reporting findings to validation report -- Not auto-proceeding - -**Master Rule:** Domain compliance is conditional. High-complexity domains require special sections - low complexity domains skip these checks. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-09-project-type-validation.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-09-project-type-validation.md deleted file mode 100644 index aea41d924..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-09-project-type-validation.md +++ /dev/null @@ -1,263 +0,0 @@ ---- -name: 'step-v-09-project-type-validation' -description: 'Project-Type Compliance Validation - Validate project-type specific requirements are properly documented' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-10-smart-validation.md' -prdFile: '{prd_file_path}' -prdFrontmatter: '{prd_frontmatter}' -validationReportPath: '{validation_report_path}' -projectTypesData: '../data/project-types.csv' ---- - -# Step 9: Project-Type Compliance Validation - -## STEP GOAL: - -Validate project-type specific requirements are properly documented - different project types (api_backend, web_app, mobile_app, etc.) have different required and excluded sections. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in systematic validation, not collaborative dialogue -- ✅ You bring project type expertise and architectural knowledge -- ✅ This step runs autonomously - no user input needed - -### Step-Specific Rules: - -- 🎯 Focus ONLY on project-type compliance -- 🚫 FORBIDDEN to validate other aspects in this step -- 💬 Approach: Validate required sections present, excluded sections absent -- 🚪 This is a validation sequence step - auto-proceeds when complete - -## EXECUTION PROTOCOLS: - -- 🎯 Check classification.projectType from PRD frontmatter -- 🎯 Validate required sections for that project type are present -- 🎯 Validate excluded sections for that project type are absent -- 💾 Append compliance findings to validation report -- 📖 Display "Proceeding to next check..." and load next step -- 🚫 FORBIDDEN to pause or request user input - -## CONTEXT BOUNDARIES: - -- Available context: PRD file with frontmatter classification, validation report -- Focus: Project-type compliance only -- Limits: Don't validate other aspects, don't pause for user input -- Dependencies: Steps 2-8 completed - domain and requirements validation done - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Load Project Types Data - -Load and read the complete file at: -`{projectTypesData}` (../data/project-types.csv) - -This CSV contains: -- Detection signals for each project type -- Required sections for each project type -- Skip/excluded sections for each project type -- Innovation signals - -Internalize this data - it drives what sections must be present or absent for each project type. - -### 2. Extract Project Type Classification - -From PRD frontmatter, extract: -- `classification.projectType` - what type of project is this? - -**Common project types:** -- api_backend -- web_app -- mobile_app -- desktop_app -- data_pipeline -- ml_system -- library_sdk -- infrastructure -- other - -**If no projectType classification found:** -Assume "web_app" (most common) and note in findings - -### 3. Determine Required and Excluded Sections from CSV Data - -**From loaded project-types.csv data, for this project type:** - -**Required sections:** (from required_sections column) -These MUST be present in the PRD - -**Skip sections:** (from skip_sections column) -These MUST NOT be present in the PRD - -**Example mappings from CSV:** -- api_backend: Required=[endpoint_specs, auth_model, data_schemas], Skip=[ux_ui, visual_design] -- mobile_app: Required=[platform_reqs, device_permissions, offline_mode], Skip=[desktop_features, cli_commands] -- cli_tool: Required=[command_structure, output_formats, config_schema], Skip=[visual_design, ux_principles, touch_interactions] -- etc. - -### 4. Validate Against CSV-Based Requirements - -**Based on project type, determine:** - -**api_backend:** -- Required: Endpoint Specs, Auth Model, Data Schemas, API Versioning -- Excluded: UX/UI sections, mobile-specific sections - -**web_app:** -- Required: User Journeys, UX/UI Requirements, Responsive Design -- Excluded: None typically - -**mobile_app:** -- Required: Mobile UX, Platform specifics (iOS/Android), Offline mode -- Excluded: Desktop-specific sections - -**desktop_app:** -- Required: Desktop UX, Platform specifics (Windows/Mac/Linux) -- Excluded: Mobile-specific sections - -**data_pipeline:** -- Required: Data Sources, Data Transformation, Data Sinks, Error Handling -- Excluded: UX/UI sections - -**ml_system:** -- Required: Model Requirements, Training Data, Inference Requirements, Model Performance -- Excluded: UX/UI sections (unless ML UI) - -**library_sdk:** -- Required: API Surface, Usage Examples, Integration Guide -- Excluded: UX/UI sections, deployment sections - -**infrastructure:** -- Required: Infrastructure Components, Deployment, Monitoring, Scaling -- Excluded: Feature requirements (this is infrastructure, not product) - -### 4. Attempt Sub-Process Validation - -"Perform project-type compliance validation for {projectType}: - -**Check that required sections are present:** -{List required sections for this project type} -For each: Is it present in PRD? Is it adequately documented? - -**Check that excluded sections are absent:** -{List excluded sections for this project type} -For each: Is it absent from PRD? (Should not be present) - -Build compliance table showing: -- Required sections: [Present/Missing/Incomplete] -- Excluded sections: [Absent/Present] (Present = violation) - -Return compliance table with findings." - -**Graceful degradation (if no Task tool):** -- Manually check PRD for required sections -- Manually check PRD for excluded sections -- Build compliance table - -### 5. Build Compliance Table - -**Required sections check:** -- For each required section: Present / Missing / Incomplete -- Count: Required sections present vs total required - -**Excluded sections check:** -- For each excluded section: Absent / Present (violation) -- Count: Excluded sections present (violations) - -**Total compliance score:** -- Required: {present}/{total} -- Excluded violations: {count} - -### 6. Report Project-Type Compliance Findings to Validation Report - -Append to validation report: - -```markdown -## Project-Type Compliance Validation - -**Project Type:** {projectType} - -### Required Sections - -**{Section 1}:** [Present/Missing/Incomplete] -{If missing or incomplete: Note specific gaps} - -**{Section 2}:** [Present/Missing/Incomplete] -{If missing or incomplete: Note specific gaps} - -[Continue for all required sections] - -### Excluded Sections (Should Not Be Present) - -**{Section 1}:** [Absent/Present] ✓ -{If present: This section should not be present for {projectType}} - -**{Section 2}:** [Absent/Present] ✓ -{If present: This section should not be present for {projectType}} - -[Continue for all excluded sections] - -### Compliance Summary - -**Required Sections:** {present}/{total} present -**Excluded Sections Present:** {violations} (should be 0) -**Compliance Score:** {percentage}% - -**Severity:** [Critical if required sections missing, Warning if incomplete, Pass if complete] - -**Recommendation:** -[If Critical] "PRD is missing required sections for {projectType}. Add missing sections to properly specify this type of project." -[If Warning] "Some required sections for {projectType} are incomplete. Strengthen documentation." -[If Pass] "All required sections for {projectType} are present. No excluded sections found." -``` - -### 7. Display Progress and Auto-Proceed - -Display: "**Project-Type Compliance Validation Complete** - -Project Type: {projectType} -Compliance: {score}% - -**Proceeding to next validation check...**" - -Without delay, read fully and follow: {nextStepFile} (step-v-10-smart-validation.md) - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Project type extracted correctly (or default assumed) -- Required sections validated for presence and completeness -- Excluded sections validated for absence -- Compliance table built with status for all sections -- Severity assessed correctly -- Findings reported to validation report -- Auto-proceeds to next validation step -- Subprocess attempted with graceful degradation - -### ❌ SYSTEM FAILURE: - -- Not checking project type before proceeding -- Missing required section checks -- Missing excluded section checks -- Not building compliance table -- Not reporting findings to validation report -- Not auto-proceeding - -**Master Rule:** Different project types have different requirements. API PRDs don't need UX sections - validate accordingly. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-10-smart-validation.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-10-smart-validation.md deleted file mode 100644 index e937c7526..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-10-smart-validation.md +++ /dev/null @@ -1,209 +0,0 @@ ---- -name: 'step-v-10-smart-validation' -description: 'SMART Requirements Validation - Validate Functional Requirements meet SMART quality criteria' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-11-holistic-quality-validation.md' -prdFile: '{prd_file_path}' -validationReportPath: '{validation_report_path}' -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' ---- - -# Step 10: SMART Requirements Validation - -## STEP GOAL: - -Validate Functional Requirements meet SMART quality criteria (Specific, Measurable, Attainable, Relevant, Traceable), ensuring high-quality requirements. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in systematic validation, not collaborative dialogue -- ✅ You bring requirements engineering expertise and quality assessment -- ✅ This step runs autonomously - no user input needed - -### Step-Specific Rules: - -- 🎯 Focus ONLY on FR quality assessment using SMART framework -- 🚫 FORBIDDEN to validate other aspects in this step -- 💬 Approach: Score each FR on SMART criteria (1-5 scale) -- 🚪 This is a validation sequence step - auto-proceeds when complete - -## EXECUTION PROTOCOLS: - -- 🎯 Extract all FRs from PRD -- 🎯 Score each FR on SMART criteria (Specific, Measurable, Attainable, Relevant, Traceable) -- 💾 Flag FRs with score < 3 in any category -- 📖 Append scoring table and suggestions to validation report -- 📖 Display "Proceeding to next check..." and load next step -- 🚫 FORBIDDEN to pause or request user input - -## CONTEXT BOUNDARIES: - -- Available context: PRD file, validation report -- Focus: FR quality assessment only using SMART framework -- Limits: Don't validate NFRs or other aspects, don't pause for user input -- Dependencies: Steps 2-9 completed - comprehensive validation checks done - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Extract All Functional Requirements - -From the PRD's Functional Requirements section, extract: -- All FRs with their FR numbers (FR-001, FR-002, etc.) -- Count total FRs - -### 2. Attempt Sub-Process Validation - -**Try to use Task tool to spawn a subprocess:** - -"Perform SMART requirements validation on these Functional Requirements: - -{List all FRs} - -**For each FR, score on SMART criteria (1-5 scale):** - -**Specific (1-5):** -- 5: Clear, unambiguous, well-defined -- 3: Somewhat clear but could be more specific -- 1: Vague, ambiguous, unclear - -**Measurable (1-5):** -- 5: Quantifiable metrics, testable -- 3: Partially measurable -- 1: Not measurable, subjective - -**Attainable (1-5):** -- 5: Realistic, achievable with constraints -- 3: Probably achievable but uncertain -- 1: Unrealistic, technically infeasible - -**Relevant (1-5):** -- 5: Clearly aligned with user needs and business objectives -- 3: Somewhat relevant but connection unclear -- 1: Not relevant, doesn't align with goals - -**Traceable (1-5):** -- 5: Clearly traces to user journey or business objective -- 3: Partially traceable -- 1: Orphan requirement, no clear source - -**For each FR with score < 3 in any category:** -- Provide specific improvement suggestions - -Return scoring table with all FR scores and improvement suggestions for low-scoring FRs." - -**Graceful degradation (if no Task tool):** -- Manually score each FR on SMART criteria -- Note FRs with low scores -- Provide improvement suggestions - -### 3. Build Scoring Table - -For each FR: -- FR number -- Specific score (1-5) -- Measurable score (1-5) -- Attainable score (1-5) -- Relevant score (1-5) -- Traceable score (1-5) -- Average score -- Flag if any category < 3 - -**Calculate overall FR quality:** -- Percentage of FRs with all scores ≥ 3 -- Percentage of FRs with all scores ≥ 4 -- Average score across all FRs and categories - -### 4. Report SMART Findings to Validation Report - -Append to validation report: - -```markdown -## SMART Requirements Validation - -**Total Functional Requirements:** {count} - -### Scoring Summary - -**All scores ≥ 3:** {percentage}% ({count}/{total}) -**All scores ≥ 4:** {percentage}% ({count}/{total}) -**Overall Average Score:** {average}/5.0 - -### Scoring Table - -| FR # | Specific | Measurable | Attainable | Relevant | Traceable | Average | Flag | -|------|----------|------------|------------|----------|-----------|--------|------| -| FR-001 | {s1} | {m1} | {a1} | {r1} | {t1} | {avg1} | {X if any <3} | -| FR-002 | {s2} | {m2} | {a2} | {r2} | {t2} | {avg2} | {X if any <3} | -[Continue for all FRs] - -**Legend:** 1=Poor, 3=Acceptable, 5=Excellent -**Flag:** X = Score < 3 in one or more categories - -### Improvement Suggestions - -**Low-Scoring FRs:** - -**FR-{number}:** {specific suggestion for improvement} -[For each FR with score < 3 in any category] - -### Overall Assessment - -**Severity:** [Critical if >30% flagged FRs, Warning if 10-30%, Pass if <10%] - -**Recommendation:** -[If Critical] "Many FRs have quality issues. Revise flagged FRs using SMART framework to improve clarity and testability." -[If Warning] "Some FRs would benefit from SMART refinement. Focus on flagged requirements above." -[If Pass] "Functional Requirements demonstrate good SMART quality overall." -``` - -### 5. Display Progress and Auto-Proceed - -Display: "**SMART Requirements Validation Complete** - -FR Quality: {percentage}% with acceptable scores ({severity}) - -**Proceeding to next validation check...**" - -Without delay, read fully and follow: {nextStepFile} (step-v-11-holistic-quality-validation.md) - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All FRs extracted from PRD -- Each FR scored on all 5 SMART criteria (1-5 scale) -- FRs with scores < 3 flagged for improvement -- Improvement suggestions provided for low-scoring FRs -- Scoring table built with all FR scores -- Overall quality assessment calculated -- Findings reported to validation report -- Auto-proceeds to next validation step -- Subprocess attempted with graceful degradation - -### ❌ SYSTEM FAILURE: - -- Not scoring all FRs on all SMART criteria -- Missing improvement suggestions for low-scoring FRs -- Not building scoring table -- Not calculating overall quality metrics -- Not reporting findings to validation report -- Not auto-proceeding - -**Master Rule:** FRs should be high-quality, not just present. SMART framework provides objective quality measure. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-11-holistic-quality-validation.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-11-holistic-quality-validation.md deleted file mode 100644 index 698b6f654..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-11-holistic-quality-validation.md +++ /dev/null @@ -1,264 +0,0 @@ ---- -name: 'step-v-11-holistic-quality-validation' -description: 'Holistic Quality Assessment - Assess PRD as cohesive, compelling document - is it a good PRD?' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-12-completeness-validation.md' -prdFile: '{prd_file_path}' -validationReportPath: '{validation_report_path}' -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' ---- - -# Step 11: Holistic Quality Assessment - -## STEP GOAL: - -Assess the PRD as a cohesive, compelling document - evaluating document flow, dual audience effectiveness (humans and LLMs), BMAD PRD principles compliance, and overall quality rating. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in systematic validation, not collaborative dialogue -- ✅ You bring analytical rigor and document quality expertise -- ✅ This step runs autonomously - no user input needed -- ✅ Uses Advanced Elicitation for multi-perspective evaluation - -### Step-Specific Rules: - -- 🎯 Focus ONLY on holistic document quality assessment -- 🚫 FORBIDDEN to validate individual components (done in previous steps) -- 💬 Approach: Multi-perspective evaluation using Advanced Elicitation -- 🚪 This is a validation sequence step - auto-proceeds when complete - -## EXECUTION PROTOCOLS: - -- 🎯 Use Advanced Elicitation for multi-perspective assessment -- 🎯 Evaluate document flow, dual audience, BMAD principles -- 💾 Append comprehensive assessment to validation report -- 📖 Display "Proceeding to next check..." and load next step -- 🚫 FORBIDDEN to pause or request user input - -## CONTEXT BOUNDARIES: - -- Available context: Complete PRD file, validation report with findings from steps 1-10 -- Focus: Holistic quality - the WHOLE document -- Limits: Don't re-validate individual components, don't pause for user input -- Dependencies: Steps 1-10 completed - all systematic checks done - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Attempt Sub-Process with Advanced Elicitation - -**Try to use Task tool to spawn a subprocess using Advanced Elicitation:** - -"Perform holistic quality assessment on this PRD using multi-perspective evaluation: - -**Read fully and follow the Advanced Elicitation workflow:** -{advancedElicitationTask} - -**Evaluate the PRD from these perspectives:** - -**1. Document Flow & Coherence:** -- Read entire PRD -- Evaluate narrative flow - does it tell a cohesive story? -- Check transitions between sections -- Assess consistency - is it coherent throughout? -- Evaluate readability - is it clear and well-organized? - -**2. Dual Audience Effectiveness:** - -**For Humans:** -- Executive-friendly: Can executives understand vision and goals quickly? -- Developer clarity: Do developers have clear requirements to build from? -- Designer clarity: Do designers understand user needs and flows? -- Stakeholder decision-making: Can stakeholders make informed decisions? - -**For LLMs:** -- Machine-readable structure: Is the PRD structured for LLM consumption? -- UX readiness: Can an LLM generate UX designs from this? -- Architecture readiness: Can an LLM generate architecture from this? -- Epic/Story readiness: Can an LLM break down into epics and stories? - -**3. BMAD PRD Principles Compliance:** -- Information density: Every sentence carries weight? -- Measurability: Requirements testable? -- Traceability: Requirements trace to sources? -- Domain awareness: Domain-specific considerations included? -- Zero anti-patterns: No filler or wordiness? -- Dual audience: Works for both humans and LLMs? -- Markdown format: Proper structure and formatting? - -**4. Overall Quality Rating:** -Rate the PRD on 5-point scale: -- Excellent (5/5): Exemplary, ready for production use -- Good (4/5): Strong with minor improvements needed -- Adequate (3/5): Acceptable but needs refinement -- Needs Work (2/5): Significant gaps or issues -- Problematic (1/5): Major flaws, needs substantial revision - -**5. Top 3 Improvements:** -Identify the 3 most impactful improvements to make this a great PRD - -Return comprehensive assessment with all perspectives, rating, and top 3 improvements." - -**Graceful degradation (if no Task tool or Advanced Elicitation unavailable):** -- Perform holistic assessment directly in current context -- Read complete PRD -- Evaluate document flow, coherence, transitions -- Assess dual audience effectiveness -- Check BMAD principles compliance -- Assign overall quality rating -- Identify top 3 improvements - -### 2. Synthesize Assessment - -**Compile findings from multi-perspective evaluation:** - -**Document Flow & Coherence:** -- Overall assessment: [Excellent/Good/Adequate/Needs Work/Problematic] -- Key strengths: [list] -- Key weaknesses: [list] - -**Dual Audience Effectiveness:** -- For Humans: [assessment] -- For LLMs: [assessment] -- Overall dual audience score: [1-5] - -**BMAD Principles Compliance:** -- Principles met: [count]/7 -- Principles with issues: [list] - -**Overall Quality Rating:** [1-5 with label] - -**Top 3 Improvements:** -1. [Improvement 1] -2. [Improvement 2] -3. [Improvement 3] - -### 3. Report Holistic Quality Findings to Validation Report - -Append to validation report: - -```markdown -## Holistic Quality Assessment - -### Document Flow & Coherence - -**Assessment:** [Excellent/Good/Adequate/Needs Work/Problematic] - -**Strengths:** -{List key strengths} - -**Areas for Improvement:** -{List key weaknesses} - -### Dual Audience Effectiveness - -**For Humans:** -- Executive-friendly: [assessment] -- Developer clarity: [assessment] -- Designer clarity: [assessment] -- Stakeholder decision-making: [assessment] - -**For LLMs:** -- Machine-readable structure: [assessment] -- UX readiness: [assessment] -- Architecture readiness: [assessment] -- Epic/Story readiness: [assessment] - -**Dual Audience Score:** {score}/5 - -### BMAD PRD Principles Compliance - -| Principle | Status | Notes | -|-----------|--------|-------| -| Information Density | [Met/Partial/Not Met] | {notes} | -| Measurability | [Met/Partial/Not Met] | {notes} | -| Traceability | [Met/Partial/Not Met] | {notes} | -| Domain Awareness | [Met/Partial/Not Met] | {notes} | -| Zero Anti-Patterns | [Met/Partial/Not Met] | {notes} | -| Dual Audience | [Met/Partial/Not Met] | {notes} | -| Markdown Format | [Met/Partial/Not Met] | {notes} | - -**Principles Met:** {count}/7 - -### Overall Quality Rating - -**Rating:** {rating}/5 - {label} - -**Scale:** -- 5/5 - Excellent: Exemplary, ready for production use -- 4/5 - Good: Strong with minor improvements needed -- 3/5 - Adequate: Acceptable but needs refinement -- 2/5 - Needs Work: Significant gaps or issues -- 1/5 - Problematic: Major flaws, needs substantial revision - -### Top 3 Improvements - -1. **{Improvement 1}** - {Brief explanation of why and how} - -2. **{Improvement 2}** - {Brief explanation of why and how} - -3. **{Improvement 3}** - {Brief explanation of why and how} - -### Summary - -**This PRD is:** {one-sentence overall assessment} - -**To make it great:** Focus on the top 3 improvements above. -``` - -### 4. Display Progress and Auto-Proceed - -Display: "**Holistic Quality Assessment Complete** - -Overall Rating: {rating}/5 - {label} - -**Proceeding to final validation checks...**" - -Without delay, read fully and follow: {nextStepFile} (step-v-12-completeness-validation.md) - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Advanced Elicitation used for multi-perspective evaluation (or graceful degradation) -- Document flow & coherence assessed -- Dual audience effectiveness evaluated (humans and LLMs) -- BMAD PRD principles compliance checked -- Overall quality rating assigned (1-5 scale) -- Top 3 improvements identified -- Comprehensive assessment reported to validation report -- Auto-proceeds to next validation step -- Subprocess attempted with graceful degradation - -### ❌ SYSTEM FAILURE: - -- Not using Advanced Elicitation for multi-perspective evaluation -- Missing document flow assessment -- Missing dual audience evaluation -- Not checking all BMAD principles -- Not assigning overall quality rating -- Missing top 3 improvements -- Not reporting comprehensive assessment to validation report -- Not auto-proceeding - -**Master Rule:** This evaluates the WHOLE document, not just components. Answers "Is this a good PRD?" and "What would make it great?" diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-12-completeness-validation.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-12-completeness-validation.md deleted file mode 100644 index 00c477981..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-12-completeness-validation.md +++ /dev/null @@ -1,242 +0,0 @@ ---- -name: 'step-v-12-completeness-validation' -description: 'Completeness Check - Final comprehensive completeness check before report generation' - -# File references (ONLY variables used in this step) -nextStepFile: './step-v-13-report-complete.md' -prdFile: '{prd_file_path}' -prdFrontmatter: '{prd_frontmatter}' -validationReportPath: '{validation_report_path}' ---- - -# Step 12: Completeness Validation - -## STEP GOAL: - -Final comprehensive completeness check - validate no template variables remain, each section has required content, section-specific completeness, and frontmatter is properly populated. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in systematic validation, not collaborative dialogue -- ✅ You bring attention to detail and completeness verification -- ✅ This step runs autonomously - no user input needed - -### Step-Specific Rules: - -- 🎯 Focus ONLY on completeness verification -- 🚫 FORBIDDEN to validate quality (done in step 11) or other aspects -- 💬 Approach: Systematic checklist-style verification -- 🚪 This is a validation sequence step - auto-proceeds when complete - -## EXECUTION PROTOCOLS: - -- 🎯 Check template completeness (no variables remaining) -- 🎯 Validate content completeness (each section has required content) -- 🎯 Validate section-specific completeness -- 🎯 Validate frontmatter completeness -- 💾 Append completeness matrix to validation report -- 📖 Display "Proceeding to final step..." and load next step -- 🚫 FORBIDDEN to pause or request user input - -## CONTEXT BOUNDARIES: - -- Available context: Complete PRD file, frontmatter, validation report -- Focus: Completeness verification only (final gate) -- Limits: Don't assess quality, don't pause for user input -- Dependencies: Steps 1-11 completed - all validation checks done - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Attempt Sub-Process Validation - -**Try to use Task tool to spawn a subprocess:** - -"Perform completeness validation on this PRD - final gate check: - -**1. Template Completeness:** -- Scan PRD for any remaining template variables -- Look for: {variable}, {{variable}}, {placeholder}, [placeholder], etc. -- List any found with line numbers - -**2. Content Completeness:** -- Executive Summary: Has vision statement? ({key content}) -- Success Criteria: All criteria measurable? ({metrics present}) -- Product Scope: In-scope and out-of-scope defined? ({both present}) -- User Journeys: User types identified? ({users listed}) -- Functional Requirements: FRs listed with proper format? ({FRs present}) -- Non-Functional Requirements: NFRs with metrics? ({NFRs present}) - -For each section: Is required content present? (Yes/No/Partial) - -**3. Section-Specific Completeness:** -- Success Criteria: Each has specific measurement method? -- User Journeys: Cover all user types? -- Functional Requirements: Cover MVP scope? -- Non-Functional Requirements: Each has specific criteria? - -**4. Frontmatter Completeness:** -- stepsCompleted: Populated? -- classification: Present (domain, projectType)? -- inputDocuments: Tracked? -- date: Present? - -Return completeness matrix with status for each check." - -**Graceful degradation (if no Task tool):** -- Manually scan for template variables -- Manually check each section for required content -- Manually verify frontmatter fields -- Build completeness matrix - -### 2. Build Completeness Matrix - -**Template Completeness:** -- Template variables found: count -- List if any found - -**Content Completeness by Section:** -- Executive Summary: Complete / Incomplete / Missing -- Success Criteria: Complete / Incomplete / Missing -- Product Scope: Complete / Incomplete / Missing -- User Journeys: Complete / Incomplete / Missing -- Functional Requirements: Complete / Incomplete / Missing -- Non-Functional Requirements: Complete / Incomplete / Missing -- Other sections: [List completeness] - -**Section-Specific Completeness:** -- Success criteria measurable: All / Some / None -- Journeys cover all users: Yes / Partial / No -- FRs cover MVP scope: Yes / Partial / No -- NFRs have specific criteria: All / Some / None - -**Frontmatter Completeness:** -- stepsCompleted: Present / Missing -- classification: Present / Missing -- inputDocuments: Present / Missing -- date: Present / Missing - -**Overall completeness:** -- Sections complete: X/Y -- Critical gaps: [list if any] - -### 3. Report Completeness Findings to Validation Report - -Append to validation report: - -```markdown -## Completeness Validation - -### Template Completeness - -**Template Variables Found:** {count} -{If count > 0, list variables with line numbers} -{If count = 0, note: No template variables remaining ✓} - -### Content Completeness by Section - -**Executive Summary:** [Complete/Incomplete/Missing] -{If incomplete or missing, note specific gaps} - -**Success Criteria:** [Complete/Incomplete/Missing] -{If incomplete or missing, note specific gaps} - -**Product Scope:** [Complete/Incomplete/Missing] -{If incomplete or missing, note specific gaps} - -**User Journeys:** [Complete/Incomplete/Missing] -{If incomplete or missing, note specific gaps} - -**Functional Requirements:** [Complete/Incomplete/Missing] -{If incomplete or missing, note specific gaps} - -**Non-Functional Requirements:** [Complete/Incomplete/Missing] -{If incomplete or missing, note specific gaps} - -### Section-Specific Completeness - -**Success Criteria Measurability:** [All/Some/None] measurable -{If Some or None, note which criteria lack metrics} - -**User Journeys Coverage:** [Yes/Partial/No] - covers all user types -{If Partial or No, note missing user types} - -**FRs Cover MVP Scope:** [Yes/Partial/No] -{If Partial or No, note scope gaps} - -**NFRs Have Specific Criteria:** [All/Some/None] -{If Some or None, note which NFRs lack specificity} - -### Frontmatter Completeness - -**stepsCompleted:** [Present/Missing] -**classification:** [Present/Missing] -**inputDocuments:** [Present/Missing] -**date:** [Present/Missing] - -**Frontmatter Completeness:** {complete_fields}/4 - -### Completeness Summary - -**Overall Completeness:** {percentage}% ({complete_sections}/{total_sections}) - -**Critical Gaps:** [count] [list if any] -**Minor Gaps:** [count] [list if any] - -**Severity:** [Critical if template variables exist or critical sections missing, Warning if minor gaps, Pass if complete] - -**Recommendation:** -[If Critical] "PRD has completeness gaps that must be addressed before use. Fix template variables and complete missing sections." -[If Warning] "PRD has minor completeness gaps. Address minor gaps for complete documentation." -[If Pass] "PRD is complete with all required sections and content present." -``` - -### 4. Display Progress and Auto-Proceed - -Display: "**Completeness Validation Complete** - -Overall Completeness: {percentage}% ({severity}) - -**Proceeding to final step...**" - -Without delay, read fully and follow: {nextStepFile} (step-v-13-report-complete.md) - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Scanned for template variables systematically -- Validated each section for required content -- Validated section-specific completeness (measurability, coverage, scope) -- Validated frontmatter completeness -- Completeness matrix built with all checks -- Severity assessed correctly -- Findings reported to validation report -- Auto-proceeds to final step -- Subprocess attempted with graceful degradation - -### ❌ SYSTEM FAILURE: - -- Not scanning for template variables -- Missing section-specific completeness checks -- Not validating frontmatter -- Not building completeness matrix -- Not reporting findings to validation report -- Not auto-proceeding - -**Master Rule:** Final gate to ensure document is complete before presenting findings. Template variables or critical gaps must be fixed. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md b/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md deleted file mode 100644 index 46c98f7f9..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md +++ /dev/null @@ -1,231 +0,0 @@ ---- -name: 'step-v-13-report-complete' -description: 'Validation Report Complete - Finalize report, summarize findings, present to user, offer next steps' - -# File references (ONLY variables used in this step) -validationReportPath: '{validation_report_path}' -prdFile: '{prd_file_path}' ---- - -# Step 13: Validation Report Complete - -## STEP GOAL: - -Finalize validation report, summarize all findings from steps 1-12, present summary to user conversationally, and offer actionable next steps. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a Validation Architect and Quality Assurance Specialist -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring synthesis and summary expertise -- ✅ This is the FINAL step - requires user interaction - -### Step-Specific Rules: - -- 🎯 Focus ONLY on summarizing findings and presenting options -- 🚫 FORBIDDEN to perform additional validation -- 💬 Approach: Conversational summary with clear next steps -- 🚪 This is the final step - no next step after this - -## EXECUTION PROTOCOLS: - -- 🎯 Load complete validation report -- 🎯 Summarize all findings from steps 1-12 -- 🎯 Update report frontmatter with final status -- 💬 Present summary to user conversationally -- 💬 Offer menu options for next actions -- 🚫 FORBIDDEN to proceed without user selection - -## CONTEXT BOUNDARIES: - -- Available context: Complete validation report with findings from all validation steps -- Focus: Summary and presentation only (no new validation) -- Limits: Don't add new findings, just synthesize existing -- Dependencies: Steps 1-12 completed - all validation checks done - -## MANDATORY SEQUENCE - -**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change. - -### 1. Load Complete Validation Report - -Read the entire validation report from {validationReportPath} - -Extract all findings from: -- Format Detection (Step 2) -- Parity Analysis (Step 2B, if applicable) -- Information Density (Step 3) -- Product Brief Coverage (Step 4) -- Measurability (Step 5) -- Traceability (Step 6) -- Implementation Leakage (Step 7) -- Domain Compliance (Step 8) -- Project-Type Compliance (Step 9) -- SMART Requirements (Step 10) -- Holistic Quality (Step 11) -- Completeness (Step 12) - -### 2. Update Report Frontmatter with Final Status - -Update validation report frontmatter: - -```yaml ---- -validationTarget: '{prd_path}' -validationDate: '{current_date}' -inputDocuments: [list of documents] -validationStepsCompleted: ['step-v-01-discovery', 'step-v-02-format-detection', 'step-v-03-density-validation', 'step-v-04-brief-coverage-validation', 'step-v-05-measurability-validation', 'step-v-06-traceability-validation', 'step-v-07-implementation-leakage-validation', 'step-v-08-domain-compliance-validation', 'step-v-09-project-type-validation', 'step-v-10-smart-validation', 'step-v-11-holistic-quality-validation', 'step-v-12-completeness-validation'] -validationStatus: COMPLETE -holisticQualityRating: '{rating from step 11}' -overallStatus: '{Pass/Warning/Critical based on all findings}' ---- -``` - -### 3. Create Summary of Findings - -**Overall Status:** -- Determine from all validation findings -- **Pass:** All critical checks pass, minor warnings acceptable -- **Warning:** Some issues found but PRD is usable -- **Critical:** Major issues that prevent PRD from being fit for purpose - -**Quick Results Table:** -- Format: [classification] -- Information Density: [severity] -- Measurability: [severity] -- Traceability: [severity] -- Implementation Leakage: [severity] -- Domain Compliance: [status] -- Project-Type Compliance: [compliance score] -- SMART Quality: [percentage] -- Holistic Quality: [rating/5] -- Completeness: [percentage] - -**Critical Issues:** List from all validation steps -**Warnings:** List from all validation steps -**Strengths:** List positives from all validation steps - -**Holistic Quality Rating:** From step 11 -**Top 3 Improvements:** From step 11 - -**Recommendation:** Based on overall status - -### 4. Present Summary to User Conversationally - -Display: - -"**✓ PRD Validation Complete** - -**Overall Status:** {Pass/Warning/Critical} - -**Quick Results:** -{Present quick results table with key findings} - -**Critical Issues:** {count or "None"} -{If any, list briefly} - -**Warnings:** {count or "None"} -{If any, list briefly} - -**Strengths:** -{List key strengths} - -**Holistic Quality:** {rating}/5 - {label} - -**Top 3 Improvements:** -1. {Improvement 1} -2. {Improvement 2} -3. {Improvement 3} - -**Recommendation:** -{Based on overall status: -- Pass: "PRD is in good shape. Address minor improvements to make it great." -- Warning: "PRD is usable but has issues that should be addressed. Review warnings and improve where needed." -- Critical: "PRD has significant issues that should be fixed before use. Focus on critical issues above."} - -**What would you like to do next?**" - -### 5. Present MENU OPTIONS - -Display: - -**[R] Review Detailed Findings** - Walk through validation report section by section -**[E] Use Edit Workflow** - Use validation report with Edit workflow for systematic improvements -**[F] Fix Simpler Items** - Immediate fixes for simple issues (anti-patterns, leakage, missing headers) -**[X] Exit** - Exit and Suggest Next Steps. - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- Only proceed based on user selection - -#### Menu Handling Logic: - -- **IF R (Review Detailed Findings):** - - Walk through validation report section by section - - Present findings from each validation step - - Allow user to ask questions - - After review, return to menu - -- **IF E (Use Edit Workflow):** - - Explain: "The Edit workflow (steps-e/) can use this validation report to systematically address issues. Edit mode will guide you through discovering what to edit, reviewing the PRD, and applying targeted improvements." - - Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically." - - If yes: Read fully and follow: steps-e/step-e-01-discovery.md - - If no: Return to menu - -- **IF F (Fix Simpler Items):** - - Offer immediate fixes for: - - Template variables (fill in with appropriate content) - - Conversational filler (remove wordy phrases) - - Implementation leakage (remove technology names from FRs/NFRs) - - Missing section headers (add ## headers) - - Ask: "Which simple fixes would you like me to make?" - - If user specifies fixes, make them and update validation report - - Return to menu - -- **IF X (Exit):** - - Display: "**Validation Report Saved:** {validationReportPath}" - - Display: "**Summary:** {overall status} - {recommendation}" - - PRD Validation complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` - -- **IF Any other:** Help user, then redisplay menu - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Complete validation report loaded successfully -- All findings from steps 1-12 summarized -- Report frontmatter updated with final status -- Overall status determined correctly (Pass/Warning/Critical) -- Quick results table presented -- Critical issues, warnings, and strengths listed -- Holistic quality rating included -- Top 3 improvements presented -- Clear recommendation provided -- Menu options presented with clear explanations -- User can review findings, get help, or exit - -### ❌ SYSTEM FAILURE: - -- Not loading complete validation report -- Missing summary of findings -- Not updating report frontmatter -- Not determining overall status -- Missing menu options -- Unclear next steps - -**Master Rule:** User needs clear summary and actionable next steps. Edit workflow is best for complex issues; immediate fixes available for simpler ones. diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/templates/prd-template.md b/src/bmm/workflows/2-plan-workflows/create-prd/templates/prd-template.md deleted file mode 100644 index d82219d2f..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/templates/prd-template.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -stepsCompleted: [] -inputDocuments: [] -workflowType: 'prd' ---- - -# Product Requirements Document - {{project_name}} - -**Author:** {{user_name}} -**Date:** {{date}} diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md b/src/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md deleted file mode 100644 index c7c565a72..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -name: create-prd -description: 'Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"' -main_config: '{project-root}/_bmad/bmm/config.yaml' -nextStep: './steps-c/step-01-init.md' ---- - -# PRD Create Workflow - -**Goal:** Create comprehensive PRDs through structured workflow facilitation. - -**Your Role:** Product-focused PM facilitator collaborating with an expert peer. - -You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description. - -## WORKFLOW ARCHITECTURE - -This uses **step-file architecture** for disciplined execution: - -### Core Principles - -- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly -- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so -- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed -- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document -- **Append-Only Building**: Build documents by appending content as directed to the output file - -### Step Processing Rules - -1. **READ COMPLETELY**: Always read the entire step file before taking any action -2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate -3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection -4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue) -5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step -6. **LOAD NEXT**: When directed, read fully and follow the next step file - -### Critical Rules (NO EXCEPTIONS) - -- 🛑 **NEVER** load multiple step files simultaneously -- 📖 **ALWAYS** read entire step file before execution -- 🚫 **NEVER** skip steps or optimize the sequence -- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step -- 🎯 **ALWAYS** follow the exact instructions in the step file -- ⏸️ **ALWAYS** halt at menus and wait for user input -- 📋 **NEVER** create mental todo lists from future steps - -## INITIALIZATION SEQUENCE - -### 1. Configuration Loading - -Load and read full config from {main_config} and resolve: - -- `project_name`, `output_folder`, `planning_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as system-generated current datetime - -✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`. - -### 2. Route to Create Workflow - -"**Create Mode: Creating a new PRD from scratch.**" - -Read fully and follow: `{nextStep}` (steps-c/step-01-init.md) diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md b/src/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md deleted file mode 100644 index e416e11f5..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -name: edit-prd -description: 'Edit an existing PRD. Use when the user says "edit this PRD".' -main_config: '{project-root}/_bmad/bmm/config.yaml' -editWorkflow: './steps-e/step-e-01-discovery.md' ---- - -# PRD Edit Workflow - -**Goal:** Edit and improve existing PRDs through structured enhancement workflow. - -**Your Role:** PRD improvement specialist. - -You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description. - -## WORKFLOW ARCHITECTURE - -This uses **step-file architecture** for disciplined execution: - -### Core Principles - -- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly -- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so -- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed -- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document -- **Append-Only Building**: Build documents by appending content as directed to the output file - -### Step Processing Rules - -1. **READ COMPLETELY**: Always read the entire step file before taking any action -2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate -3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection -4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue) -5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step -6. **LOAD NEXT**: When directed, read fully and follow the next step file - -### Critical Rules (NO EXCEPTIONS) - -- 🛑 **NEVER** load multiple step files simultaneously -- 📖 **ALWAYS** read entire step file before execution -- 🚫 **NEVER** skip steps or optimize the sequence -- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step -- 🎯 **ALWAYS** follow the exact instructions in the step file -- ⏸️ **ALWAYS** halt at menus and wait for user input -- 📋 **NEVER** create mental todo lists from future steps - -## INITIALIZATION SEQUENCE - -### 1. Configuration Loading - -Load and read full config from {main_config} and resolve: - -- `project_name`, `output_folder`, `planning_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as system-generated current datetime - -✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`. - -### 2. Route to Edit Workflow - -"**Edit Mode: Improving an existing PRD.**" - -Prompt for PRD path: "Which PRD would you like to edit? Please provide the path to the PRD.md file." - -Then read fully and follow: `{editWorkflow}` (steps-e/step-e-01-discovery.md) diff --git a/src/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md b/src/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md deleted file mode 100644 index 7f0703440..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -name: validate-prd -description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"' -main_config: '{project-root}/_bmad/bmm/config.yaml' -validateWorkflow: './steps-v/step-v-01-discovery.md' ---- - -# PRD Validate Workflow - -**Goal:** Validate existing PRDs against BMAD standards through comprehensive review. - -**Your Role:** Validation Architect and Quality Assurance Specialist. - -You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description. - -## WORKFLOW ARCHITECTURE - -This uses **step-file architecture** for disciplined execution: - -### Core Principles - -- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly -- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so -- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed -- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document -- **Append-Only Building**: Build documents by appending content as directed to the output file - -### Step Processing Rules - -1. **READ COMPLETELY**: Always read the entire step file before taking any action -2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate -3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection -4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue) -5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step -6. **LOAD NEXT**: When directed, read fully and follow the next step file - -### Critical Rules (NO EXCEPTIONS) - -- 🛑 **NEVER** load multiple step files simultaneously -- 📖 **ALWAYS** read entire step file before execution -- 🚫 **NEVER** skip steps or optimize the sequence -- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step -- 🎯 **ALWAYS** follow the exact instructions in the step file -- ⏸️ **ALWAYS** halt at menus and wait for user input -- 📋 **NEVER** create mental todo lists from future steps - -## INITIALIZATION SEQUENCE - -### 1. Configuration Loading - -Load and read full config from {main_config} and resolve: - -- `project_name`, `output_folder`, `planning_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as system-generated current datetime - -✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`. - -### 2. Route to Validate Workflow - -"**Validate Mode: Validating an existing PRD against BMAD standards.**" - -Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md) diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md deleted file mode 100644 index 02b69c2d0..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md +++ /dev/null @@ -1,135 +0,0 @@ -# Step 1: UX Design Workflow Initialization - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on initialization and setup only - don't look ahead to future steps -- 🚪 DETECT existing workflow state and handle continuation properly -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 💾 Initialize document and update frontmatter -- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step -- 🚫 FORBIDDEN to load next step until setup is complete - -## CONTEXT BOUNDARIES: - -- Variables from workflow.md are available in memory -- Previous context = what's in output document + frontmatter -- Don't assume knowledge from other steps -- Input document discovery happens in this step - -## YOUR TASK: - -Initialize the UX design workflow by detecting continuation state and setting up the design specification document. - -## INITIALIZATION SEQUENCE: - -### 1. Check for Existing Workflow - -First, check if the output document already exists: - -- Look for file at `{planning_artifacts}/*ux-design-specification*.md` -- If exists, read the complete file including frontmatter -- If not exists, this is a fresh workflow - -### 2. Handle Continuation (If Document Exists) - -If the document exists and has frontmatter with `stepsCompleted`: - -- **STOP here** and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md` immediately -- Do not proceed with any initialization tasks -- Let step-01b handle the continuation logic - -### 3. Fresh Workflow Setup (If No Document) - -If no document exists or no `stepsCompleted` in frontmatter: - -#### A. Input Document Discovery - -Discover and load context documents using smart discovery. Documents can be in the following locations: -- {planning_artifacts}/** -- {output_folder}/** -- {product_knowledge}/** -- docs/** - -Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content) - -Try to discover the following: -- Product Brief (`*brief*.md`) -- Research Documents (`*prd*.md`) -- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.) -- Project Context (`**/project-context.md`) - -Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules - -**Loading Rules:** - -- Load ALL discovered files completely that the user confirmed or provided (no offset/limit) -- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process -- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document -- index.md is a guide to what's relevant whenever available -- Track all successfully loaded files in frontmatter `inputDocuments` array - -#### B. Create Initial Document - -Copy the template from `{installed_path}/ux-design-template.md` to `{planning_artifacts}/ux-design-specification.md` -Initialize frontmatter in the template. - -#### C. Complete Initialization and Report - -Complete setup and report to user: - -**Document Setup:** - -- Created: `{planning_artifacts}/ux-design-specification.md` from template -- Initialized frontmatter with workflow state - -**Input Documents Discovered:** -Report what was found: -"Welcome {{user_name}}! I've set up your UX design workspace for {{project_name}}. - -**Documents Found:** - -- PRD: {number of PRD files loaded or "None found"} -- Product brief: {number of brief files loaded or "None found"} -- Other context: {number of other files loaded or "None found"} - -**Files loaded:** {list of specific file names or "No additional documents found"} - -Do you have any other documents you'd like me to include, or shall we continue to the next step? - -[C] Continue to UX discovery" - -## NEXT STEP: - -After user selects [C] to continue, ensure the file `{planning_artifacts}/ux-design-specification.md` has been created and saved, and then load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md` to begin the UX discovery phase. - -Remember: Do NOT proceed to step-02 until output file has been updated and user explicitly selects [C] to continue! - -## SUCCESS METRICS: - -✅ Existing workflow detected and handed off to step-01b correctly -✅ Fresh workflow initialized with template and frontmatter -✅ Input documents discovered and loaded using sharded-first logic -✅ All discovered files tracked in frontmatter `inputDocuments` -✅ User confirmed document setup and can proceed - -## FAILURE MODES: - -❌ Proceeding with fresh initialization when existing workflow exists -❌ Not updating frontmatter with discovered input documents -❌ Creating document without proper template -❌ Not checking sharded folders first before whole files -❌ Not reporting what documents were found to user - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md deleted file mode 100644 index 92fded6c3..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md +++ /dev/null @@ -1,127 +0,0 @@ -# Step 1B: UX Design Workflow Continuation - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on understanding where we left off and continuing appropriately -- 🚪 RESUME workflow from exact point where it was interrupted -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis of current state before taking action -- 💾 Keep existing frontmatter `stepsCompleted` values -- 📖 Only load documents that were already tracked in `inputDocuments` -- 🚫 FORBIDDEN to modify content completed in previous steps - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter are already loaded -- Previous context = complete document + existing frontmatter -- Input documents listed in frontmatter were already processed -- Last completed step = `lastStep` value from frontmatter - -## YOUR TASK: - -Resume the UX design workflow from where it was left off, ensuring smooth continuation. - -## CONTINUATION SEQUENCE: - -### 1. Analyze Current State - -Review the frontmatter to understand: - -- `stepsCompleted`: Which steps are already done -- `lastStep`: The most recently completed step number -- `inputDocuments`: What context was already loaded -- All other frontmatter variables - -### 2. Load All Input Documents - -Reload the context documents listed in `inputDocuments`: - -- For each document in `inputDocuments`, load the complete file -- This ensures you have full context for continuation -- Don't discover new documents - only reload what was previously processed - -### 3. Summarize Current Progress - -Welcome the user back and provide context: -"Welcome back {{user_name}}! I'm resuming our UX design collaboration for {{project_name}}. - -**Current Progress:** - -- Steps completed: {stepsCompleted} -- Last worked on: Step {lastStep} -- Context documents available: {len(inputDocuments)} files -- Current UX design specification is ready with all completed sections - -**Document Status:** - -- Current UX design document is ready with all completed sections -- Ready to continue from where we left off - -Does this look right, or do you want to make any adjustments before we proceed?" - -### 4. Determine Next Step - -Based on `lastStep` value, determine which step to load next: - -- If `lastStep = 1` → Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md` -- If `lastStep = 2` → Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md` -- If `lastStep = 3` → Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md` -- Continue this pattern for all steps -- If `lastStep` indicates final step → Workflow already complete - -### 5. Present Continuation Options - -After presenting current progress, ask: -"Ready to continue with Step {nextStepNumber}: {nextStepTitle}? - -[C] Continue to Step {nextStepNumber}" - -## SUCCESS METRICS: - -✅ All previous input documents successfully reloaded -✅ Current workflow state accurately analyzed and presented -✅ User confirms understanding of progress -✅ Correct next step identified and prepared for loading - -## FAILURE MODES: - -❌ Discovering new input documents instead of reloading existing ones -❌ Modifying content from already completed steps -❌ Loading wrong next step based on `lastStep` value -❌ Proceeding without user confirmation of current state - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## WORKFLOW ALREADY COMPLETE? - -If `lastStep` indicates the final step is completed: -"Great news! It looks like we've already completed the UX design workflow for {{project_name}}. - -The final UX design specification is ready at {output_folder}/ux-design-specification.md with all sections completed through step {finalStepNumber}. - -The complete UX design includes visual foundations, user flows, and design specifications ready for implementation. - -Would you like me to: - -- Review the completed UX design specification with you -- Suggest next workflow steps (like wireframe generation or architecture) -- Start a new UX design revision - -What would be most helpful?" - -## NEXT STEP: - -After user confirms they're ready to continue, load the appropriate next step file based on the `lastStep` value from frontmatter. - -Remember: Do NOT load the next step until user explicitly selects [C] to continue! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md deleted file mode 100644 index 41821e326..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md +++ /dev/null @@ -1,190 +0,0 @@ -# Step 2: Project Understanding - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on understanding project context and user needs -- 🎯 COLLABORATIVE discovery, not assumption-based design -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating project understanding content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper project insights -- **P (Party Mode)**: Bring multiple perspectives to understand project context -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from step 1 are available -- Input documents (PRD, briefs, epics) already loaded are in memory -- No additional data files needed for this step -- Focus on project and user understanding - -## YOUR TASK: - -Understand the project context, target users, and what makes this product special from a UX perspective. - -## PROJECT DISCOVERY SEQUENCE: - -### 1. Review Loaded Context - -Start by analyzing what we know from the loaded documents: -"Based on the project documentation we have loaded, let me confirm what I'm understanding about {{project_name}}. - -**From the documents:** -{summary of key insights from loaded PRD, briefs, and other context documents} - -**Target Users:** -{summary of user information from loaded documents} - -**Key Features/Goals:** -{summary of main features and goals from loaded documents} - -Does this match your understanding? Are there any corrections or additions you'd like to make?" - -### 2. Fill Context Gaps (If no documents or gaps exist) - -If no documents were loaded or key information is missing: -"Since we don't have complete documentation, let's start with the essentials: - -**What are you building?** (Describe your product in 1-2 sentences) - -**Who is this for?** (Describe your ideal user or target audience) - -**What makes this special or different?** (What's the unique value proposition?) - -**What's the main thing users will do with this?** (Core user action or goal)" - -### 3. Explore User Context Deeper - -Dive into user understanding: -"Let me understand your users better to inform the UX design: - -**User Context Questions:** - -- What problem are users trying to solve? -- What frustrates them with current solutions? -- What would make them say 'this is exactly what I needed'? -- How tech-savvy are your target users? -- What devices will they use most? -- When/where will they use this product?" - -### 4. Identify UX Design Challenges - -Surface the key UX challenges to address: -"From what we've discussed, I'm seeing some key UX design considerations: - -**Design Challenges:** - -- [Identify 2-3 key UX challenges based on project type and user needs] -- [Note any platform-specific considerations] -- [Highlight any complex user flows or interactions] - -**Design Opportunities:** - -- [Identify 2-3 areas where great UX could create competitive advantage] -- [Note any opportunities for innovative UX patterns] - -Does this capture the key UX considerations we need to address?" - -### 5. Generate Project Understanding Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Executive Summary - -### Project Vision - -[Project vision summary based on conversation] - -### Target Users - -[Target user descriptions based on conversation] - -### Key Design Challenges - -[Key UX challenges identified based on conversation] - -### Design Opportunities - -[Design opportunities identified based on conversation] -``` - -### 6. Present Content and Menu - -Show the generated project understanding content and present choices: -"I've documented our understanding of {{project_name}} from a UX perspective. This will guide all our design decisions moving forward. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 5] - -**What would you like to do?** -[C] Continue - Save this to the document and move to core experience definition" - -### 7. Handle Menu Selection - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: `stepsCompleted: [1, 2]` -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document. Only after the content is saved to document, read fully and follow: `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md`. - -## SUCCESS METRICS: - -✅ All available context documents reviewed and synthesized -✅ Project vision clearly articulated -✅ Target users well understood -✅ Key UX challenges identified -✅ Design opportunities surfaced -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not reviewing loaded context documents thoroughly -❌ Making assumptions about users without asking -❌ Missing key UX challenges that will impact design -❌ Not identifying design opportunities -❌ Generating generic content without real project insight -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -Remember: Do NOT proceed to step-03 until user explicitly selects 'C' from the menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md deleted file mode 100644 index 9dc98e70f..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md +++ /dev/null @@ -1,216 +0,0 @@ -# Step 3: Core Experience Definition - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on defining the core user experience and platform -- 🎯 COLLABORATIVE discovery, not assumption-based design -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating core experience content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper experience insights -- **P (Party Mode)**: Bring multiple perspectives to define optimal user experience -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Project understanding from step 2 informs this step -- No additional data files needed for this step -- Focus on core experience and platform decisions - -## YOUR TASK: - -Define the core user experience, platform requirements, and what makes the interaction effortless. - -## CORE EXPERIENCE DISCOVERY SEQUENCE: - -### 1. Define Core User Action - -Start by identifying the most important user interaction: -"Now let's dig into the heart of the user experience for {{project_name}}. - -**Core Experience Questions:** - -- What's the ONE thing users will do most frequently? -- What user action is absolutely critical to get right? -- What should be completely effortless for users? -- If we nail one interaction, everything else follows - what is it? - -Think about the core loop or primary action that defines your product's value." - -### 2. Explore Platform Requirements - -Determine where and how users will interact: -"Let's define the platform context for {{project_name}}: - -**Platform Questions:** - -- Web, mobile app, desktop, or multiple platforms? -- Will this be primarily touch-based or mouse/keyboard? -- Any specific platform requirements or constraints? -- Do we need to consider offline functionality? -- Any device-specific capabilities we should leverage?" - -### 3. Identify Effortless Interactions - -Surface what should feel magical or completely seamless: -"**Effortless Experience Design:** - -- What user actions should feel completely natural and require zero thought? -- Where do users currently struggle with similar products? -- What interaction, if made effortless, would create delight? -- What should happen automatically without user intervention? -- Where can we eliminate steps that competitors require?" - -### 4. Define Critical Success Moments - -Identify the moments that determine success or failure: -"**Critical Success Moments:** - -- What's the moment where users realize 'this is better'? -- When does the user feel successful or accomplished? -- What interaction, if failed, would ruin the experience? -- What are the make-or-break user flows? -- Where does first-time user success happen?" - -### 5. Synthesize Experience Principles - -Extract guiding principles from the conversation: -"Based on our discussion, I'm hearing these core experience principles for {{project_name}}: - -**Experience Principles:** - -- [Principle 1 based on core action focus] -- [Principle 2 based on effortless interactions] -- [Principle 3 based on platform considerations] -- [Principle 4 based on critical success moments] - -These principles will guide all our UX decisions. Do these capture what's most important?" - -### 6. Generate Core Experience Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Core User Experience - -### Defining Experience - -[Core experience definition based on conversation] - -### Platform Strategy - -[Platform requirements and decisions based on conversation] - -### Effortless Interactions - -[Effortless interaction areas identified based on conversation] - -### Critical Success Moments - -[Critical success moments defined based on conversation] - -### Experience Principles - -[Guiding principles for UX decisions based on conversation] -``` - -### 7. Present Content and Menu - -Show the generated core experience content and present choices: -"I've defined the core user experience for {{project_name}} based on our conversation. This establishes the foundation for all our UX design decisions. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Let's refine the core experience definition -[P] Party Mode - Bring different perspectives on the user experience -[C] Continue - Save this to the document and move to emotional response definition" - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current core experience content -- Process the enhanced experience insights that come back -- Ask user: "Accept these improvements to the core experience definition? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current core experience definition -- Process the collaborative experience improvements that come back -- Ask user: "Accept these changes to the core experience definition? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: append step to end of stepsCompleted array -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Core user action clearly identified and defined -✅ Platform requirements thoroughly explored -✅ Effortless interaction areas identified -✅ Critical success moments mapped out -✅ Experience principles established as guiding framework -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Missing the core user action that defines the product -❌ Not properly considering platform requirements -❌ Overlooking what should be effortless for users -❌ Not identifying critical make-or-break interactions -❌ Experience principles too generic or not actionable -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md` to define desired emotional responses. - -Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md deleted file mode 100644 index f25bf0528..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md +++ /dev/null @@ -1,219 +0,0 @@ -# Step 4: Desired Emotional Response - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on defining desired emotional responses and user feelings -- 🎯 COLLABORATIVE discovery, not assumption-based design -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating emotional response content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper emotional insights -- **P (Party Mode)**: Bring multiple perspectives to define optimal emotional responses -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Core experience definition from step 3 informs emotional response -- No additional data files needed for this step -- Focus on user feelings and emotional design goals - -## YOUR TASK: - -Define the desired emotional responses users should feel when using the product. - -## EMOTIONAL RESPONSE DISCOVERY SEQUENCE: - -### 1. Explore Core Emotional Goals - -Start by understanding the emotional objectives: -"Now let's think about how {{project_name}} should make users feel. - -**Emotional Response Questions:** - -- What should users FEEL when using this product? -- What emotion would make them tell a friend about this? -- How should users feel after accomplishing their primary goal? -- What feeling differentiates this from competitors? - -Common emotional goals: Empowered and in control? Delighted and surprised? Efficient and productive? Creative and inspired? Calm and focused? Connected and engaged?" - -### 2. Identify Emotional Journey Mapping - -Explore feelings at different stages: -"**Emotional Journey Considerations:** - -- How should users feel when they first discover the product? -- What emotion during the core experience/action? -- How should they feel after completing their task? -- What if something goes wrong - what emotional response do we want? -- How should they feel when returning to use it again?" - -### 3. Define Micro-Emotions - -Surface subtle but important emotional states: -"**Micro-Emotions to Consider:** - -- Confidence vs. Confusion -- Trust vs. Skepticism -- Excitement vs. Anxiety -- Accomplishment vs. Frustration -- Delight vs. Satisfaction -- Belonging vs. Isolation - -Which of these emotional states are most critical for your product's success?" - -### 4. Connect Emotions to UX Decisions - -Link feelings to design implications: -"**Design Implications:** - -- If we want users to feel [emotional state], what UX choices support this? -- What interactions might create negative emotions we want to avoid? -- Where can we add moments of delight or surprise? -- How do we build trust and confidence through design? - -**Emotion-Design Connections:** - -- [Emotion 1] → [UX design approach] -- [Emotion 2] → [UX design approach] -- [Emotion 3] → [UX design approach]" - -### 5. Validate Emotional Goals - -Check if emotional goals align with product vision: -"Let me make sure I understand the emotional vision for {{project_name}}: - -**Primary Emotional Goal:** [Summarize main emotional response] -**Secondary Feelings:** [List supporting emotional states] -**Emotions to Avoid:** [List negative emotions to prevent] - -Does this capture the emotional experience you want to create? Any adjustments needed?" - -### 6. Generate Emotional Response Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Desired Emotional Response - -### Primary Emotional Goals - -[Primary emotional goals based on conversation] - -### Emotional Journey Mapping - -[Emotional journey mapping based on conversation] - -### Micro-Emotions - -[Micro-emotions identified based on conversation] - -### Design Implications - -[UX design implications for emotional responses based on conversation] - -### Emotional Design Principles - -[Guiding principles for emotional design based on conversation] -``` - -### 7. Present Content and Menu - -Show the generated emotional response content and present choices: -"I've defined the desired emotional responses for {{project_name}}. These emotional goals will guide our design decisions to create the right user experience. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Let's refine the emotional response definition -[P] Party Mode - Bring different perspectives on user emotional needs -[C] Continue - Save this to the document and move to inspiration analysis" - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current emotional response content -- Process the enhanced emotional insights that come back -- Ask user: "Accept these improvements to the emotional response definition? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current emotional response definition -- Process the collaborative emotional insights that come back -- Ask user: "Accept these changes to the emotional response definition? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: append step to end of stepsCompleted array -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Primary emotional goals clearly defined -✅ Emotional journey mapped across user experience -✅ Micro-emotions identified and addressed -✅ Design implications connected to emotional responses -✅ Emotional design principles established -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Missing core emotional goals or being too generic -❌ Not considering emotional journey across different stages -❌ Overlooking micro-emotions that impact user satisfaction -❌ Not connecting emotional goals to specific UX design choices -❌ Emotional principles too vague or not actionable -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md` to analyze UX patterns from inspiring products. - -Remember: Do NOT proceed to step-05 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md deleted file mode 100644 index 890048b74..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md +++ /dev/null @@ -1,234 +0,0 @@ -# Step 5: UX Pattern Analysis & Inspiration - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on analyzing existing UX patterns and extracting inspiration -- 🎯 COLLABORATIVE discovery, not assumption-based design -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating inspiration analysis content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper pattern insights -- **P ( Party Mode)**: Bring multiple perspectives to analyze UX patterns -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Emotional response goals from step 4 inform pattern analysis -- No additional data files needed for this step -- Focus on analyzing existing UX patterns and extracting lessons - -## YOUR TASK: - -Analyze inspiring products and UX patterns to inform design decisions for the current project. - -## INSPIRATION ANALYSIS SEQUENCE: - -### 1. Identify User's Favorite Apps - -Start by gathering inspiration sources: -"Let's learn from products your users already love and use regularly. - -**Inspiration Questions:** - -- Name 2-3 apps your target users already love and USE frequently -- For each one, what do they do well from a UX perspective? -- What makes the experience compelling or delightful? -- What keeps users coming back to these apps? - -Think about apps in your category or even unrelated products that have great UX." - -### 2. Analyze UX Patterns and Principles - -Break down what makes these apps successful: -"For each inspiring app, let's analyze their UX success: - -**For [App Name]:** - -- What core problem does it solve elegantly? -- What makes the onboarding experience effective? -- How do they handle navigation and information hierarchy? -- What are their most innovative or delightful interactions? -- What visual design choices support the user experience? -- How do they handle errors or edge cases?" - -### 3. Extract Transferable Patterns - -Identify patterns that could apply to your project: -"**Transferable UX Patterns:** -Looking across these inspiring apps, I see patterns we could adapt: - -**Navigation Patterns:** - -- [Pattern 1] - could work for your [specific use case] -- [Pattern 2] - might solve your [specific challenge] - -**Interaction Patterns:** - -- [Pattern 1] - excellent for [your user goal] -- [Pattern 2] - addresses [your user pain point] - -**Visual Patterns:** - -- [Pattern 1] - supports your [emotional goal] -- [Pattern 2] - aligns with your [platform requirements] - -Which of these patterns resonate most for your product?" - -### 4. Identify Anti-Patterns to Avoid - -Surface what not to do based on analysis: -"**UX Anti-Patterns to Avoid:** -From analyzing both successes and failures in your space, here are patterns to avoid: - -- [Anti-pattern 1] - users find this confusing/frustrating -- [Anti-pattern 2] - this creates unnecessary friction -- [Anti-pattern 3] - doesn't align with your [emotional goals] - -Learning from others' mistakes is as important as learning from their successes." - -### 5. Define Design Inspiration Strategy - -Create a clear strategy for using this inspiration: -"**Design Inspiration Strategy:** - -**What to Adopt:** - -- [Specific pattern] - because it supports [your core experience] -- [Specific pattern] - because it aligns with [user needs] - -**What to Adapt:** - -- [Specific pattern] - modify for [your unique requirements] -- [Specific pattern] - simplify for [your user skill level] - -**What to Avoid:** - -- [Specific anti-pattern] - conflicts with [your goals] -- [Specific anti-pattern] - doesn't fit [your platform] - -This strategy will guide our design decisions while keeping {{project_name}} unique." - -### 6. Generate Inspiration Analysis Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## UX Pattern Analysis & Inspiration - -### Inspiring Products Analysis - -[Analysis of inspiring products based on conversation] - -### Transferable UX Patterns - -[Transferable patterns identified based on conversation] - -### Anti-Patterns to Avoid - -[Anti-patterns to avoid based on conversation] - -### Design Inspiration Strategy - -[Strategy for using inspiration based on conversation] -``` - -### 7. Present Content and Menu - -Show the generated inspiration analysis content and present choices: -"I've analyzed inspiring UX patterns and products to inform our design strategy for {{project_name}}. This gives us a solid foundation of proven patterns to build upon. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Let's deepen our UX pattern analysis -[P] Party Mode - Bring different perspectives on inspiration sources -[C] Continue - Save this to the document and move to design system choice" - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current inspiration analysis content -- Process the enhanced pattern insights that come back -- Ask user: "Accept these improvements to the inspiration analysis? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current inspiration analysis -- Process the collaborative pattern insights that come back -- Ask user: "Accept these changes to the inspiration analysis? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: append step to end of stepsCompleted array -- Read fully and follow: `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Inspiring products identified and analyzed thoroughly -✅ UX patterns extracted and categorized effectively -✅ Transferable patterns identified for current project -✅ Anti-patterns identified to avoid common mistakes -✅ Clear design inspiration strategy established -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not getting specific examples of inspiring products -❌ Surface-level analysis without deep pattern extraction -❌ Missing opportunities for pattern adaptation -❌ Not identifying relevant anti-patterns to avoid -❌ Strategy too generic or not actionable -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md` to choose the appropriate design system approach. - -Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md deleted file mode 100644 index 26caf73db..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md +++ /dev/null @@ -1,252 +0,0 @@ -# Step 6: Design System Choice - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on choosing appropriate design system approach -- 🎯 COLLABORATIVE decision-making, not recommendation-only -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating design system decision content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper design system insights -- **P (Party Mode)**: Bring multiple perspectives to evaluate design system options -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Platform requirements from step 3 inform design system choice -- Inspiration patterns from step 5 guide design system selection -- Focus on choosing foundation for consistent design - -## YOUR TASK: - -Choose appropriate design system approach based on project requirements and constraints. - -## DESIGN SYSTEM CHOICE SEQUENCE: - -### 1. Present Design System Options - -Educate about design system approaches: -"For {{project_name}}, we need to choose a design system foundation. Think of design systems like LEGO blocks for UI - they provide proven components and patterns, ensuring consistency and speeding development. - -**Design System Approaches:** - -**1. Custom Design System** - -- Complete visual uniqueness -- Full control over every component -- Higher initial investment -- Perfect for established brands with unique needs - -**2. Established System (Material Design, Ant Design, etc.)** - -- Fast development with proven patterns -- Great defaults and accessibility built-in -- Less visual differentiation -- Ideal for startups or internal tools - -**3. Themeable System (MUI, Chakra UI, Tailwind UI)** - -- Customizable with strong foundation -- Brand flexibility with proven components -- Moderate learning curve -- Good balance of speed and uniqueness - -Which direction feels right for your project?" - -### 2. Analyze Project Requirements - -Guide decision based on project context: -"**Let's consider your specific needs:** - -**Based on our previous conversations:** - -- Platform: [platform from step 3] -- Timeline: [inferred from user conversation] -- Team Size: [inferred from user conversation] -- Brand Requirements: [inferred from user conversation] -- Technical Constraints: [inferred from user conversation] - -**Decision Factors:** - -- Need for speed vs. need for uniqueness -- Brand guidelines or existing visual identity -- Team's design expertise -- Long-term maintenance considerations -- Integration requirements with existing systems" - -### 3. Explore Specific Design System Options - -Dive deeper into relevant options: -"**Recommended Options Based on Your Needs:** - -**For [Your Platform Type]:** - -- [Option 1] - [Key benefit] - [Best for scenario] -- [Option 2] - [Key benefit] - [Best for scenario] -- [Option 3] - [Key benefit] - [Best for scenario] - -**Considerations:** - -- Component library size and quality -- Documentation and community support -- Customization capabilities -- Accessibility compliance -- Performance characteristics -- Learning curve for your team" - -### 4. Facilitate Decision Process - -Help user make informed choice: -"**Decision Framework:** - -1. What's most important: Speed, uniqueness, or balance? -2. How much design expertise does your team have? -3. Are there existing brand guidelines to follow? -4. What's your timeline and budget? -5. Long-term maintenance needs? - -Let's evaluate options based on your answers to these questions." - -### 5. Finalize Design System Choice - -Confirm and document the decision: -"Based on our analysis, I recommend [Design System Choice] for {{project_name}}. - -**Rationale:** - -- [Reason 1 based on project needs] -- [Reason 2 based on constraints] -- [Reason 3 based on team considerations] - -**Next Steps:** - -- We'll customize this system to match your brand and needs -- Define component strategy for custom components needed -- Establish design tokens and patterns - -Does this design system choice feel right to you?" - -### 6. Generate Design System Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Design System Foundation - -### 1.1 Design System Choice - -[Design system choice based on conversation] - -### Rationale for Selection - -[Rationale for design system selection based on conversation] - -### Implementation Approach - -[Implementation approach based on chosen system] - -### Customization Strategy - -[Customization strategy based on project needs] -``` - -### 7. Present Content and Menu - -Show the generated design system content and present choices: -"I've documented our design system choice for {{project_name}}. This foundation will ensure consistency and speed up development. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Let's refine our design system decision -[P] Party Mode - Bring technical perspectives on design systems -[C] Continue - Save this to the document and move to defining experience - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current design system content -- Process the enhanced design system insights that come back -- Ask user: "Accept these improvements to the design system decision? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design system choice -- Process the collaborative design system insights that come back -- Ask user: "Accept these changes to the design system decision? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: append step to end of stepsCompleted array -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Design system options clearly presented and explained -✅ Decision framework applied to project requirements -✅ Specific design system chosen with clear rationale -✅ Implementation approach planned -✅ Customization strategy defined -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not explaining design system concepts clearly -❌ Rushing to recommendation without understanding requirements -❌ Not considering technical constraints or team capabilities -❌ Choosing design system without clear rationale -❌ Not planning implementation approach -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md` to define the core user interaction. - -Remember: Do NOT proceed to step-07 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md deleted file mode 100644 index 8cd5ff3b8..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md +++ /dev/null @@ -1,254 +0,0 @@ -# Step 7: Defining Core Experience - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on defining the core interaction that defines the product -- 🎯 COLLABORATIVE discovery, not assumption-based design -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating defining experience content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper experience insights -- **P (Party Mode)**: Bring multiple perspectives to define optimal core experience -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Core experience from step 3 provides foundation -- Design system choice from step 6 informs implementation -- Focus on the defining interaction that makes the product special - -## YOUR TASK: - -Define the core interaction that, if nailed, makes everything else follow in the user experience. - -## DEFINING EXPERIENCE SEQUENCE: - -### 1. Identify the Defining Experience - -Focus on the core interaction: -"Every successful product has a defining experience - the core interaction that, if we nail it, everything else follows. - -**Think about these famous examples:** - -- Tinder: "Swipe to match with people" -- Snapchat: "Share photos that disappear" -- Instagram: "Share perfect moments with filters" -- Spotify: "Discover and play any song instantly" - -**For {{project_name}}:** -What's the core action that users will describe to their friends? -What's the interaction that makes users feel successful? -If we get ONE thing perfectly right, what should it be?" - -### 2. Explore the User's Mental Model - -Understand how users think about the core task: -"**User Mental Model Questions:** - -- How do users currently solve this problem? -- What mental model do they bring to this task? -- What's their expectation for how this should work? -- Where are they likely to get confused or frustrated? - -**Current Solutions:** - -- What do users love/hate about existing approaches? -- What shortcuts or workarounds do they use? -- What makes existing solutions feel magical or terrible?" - -### 3. Define Success Criteria for Core Experience - -Establish what makes the core interaction successful: -"**Core Experience Success Criteria:** - -- What makes users say 'this just works'? -- When do they feel smart or accomplished? -- What feedback tells them they're doing it right? -- How fast should it feel? -- What should happen automatically? - -**Success Indicators:** - -- [Success indicator 1] -- [Success indicator 2] -- [Success indicator 3]" - -### 4. Identify Novel vs. Established Patterns - -Determine if we need to innovate or can use proven patterns: -"**Pattern Analysis:** -Looking at your core experience, does this: - -- Use established UX patterns that users already understand? -- Require novel interaction design that needs user education? -- Combine familiar patterns in innovative ways? - -**If Novel:** - -- What makes this different from existing approaches? -- How will we teach users this new pattern? -- What familiar metaphors can we use? - -**If Established:** - -- Which proven patterns should we adopt? -- How can we innovate within familiar patterns? -- What's our unique twist on established interactions?" - -### 5. Define Experience Mechanics - -Break down the core interaction into details: -"**Core Experience Mechanics:** -Let's design the step-by-step flow for [defining experience]: - -**1. Initiation:** - -- How does the user start this action? -- What triggers or invites them to begin? - -**2. Interaction:** - -- What does the user actually do? -- What controls or inputs do they use? -- How does the system respond? - -**3. Feedback:** - -- What tells users they're succeeding? -- How do they know when it's working? -- What happens if they make a mistake? - -**4. Completion:** - -- How do users know they're done? -- What's the successful outcome? -- What's next?" - -### 6. Generate Defining Experience Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## 2. Core User Experience - -### 2.1 Defining Experience - -[Defining experience description based on conversation] - -### 2.2 User Mental Model - -[User mental model analysis based on conversation] - -### 2.3 Success Criteria - -[Success criteria for core experience based on conversation] - -### 2.4 Novel UX Patterns - -[Novel UX patterns analysis based on conversation] - -### 2.5 Experience Mechanics - -[Detailed mechanics for core experience based on conversation] -``` - -### 7. Present Content and Menu - -Show the generated defining experience content and present choices: -"I've defined the core experience for {{project_name}} - the interaction that will make users love this product. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Let's refine the core experience definition -[P] Party Mode - Bring different perspectives on the defining interaction -[C] Continue - Save this to the document and move to visual foundation - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current defining experience content -- Process the enhanced experience insights that come back -- Ask user: "Accept these improvements to the defining experience? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current defining experience -- Process the collaborative experience insights that come back -- Ask user: "Accept these changes to the defining experience? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: append step to end of stepsCompleted array -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Defining experience clearly articulated -✅ User mental model thoroughly analyzed -✅ Success criteria established for core interaction -✅ Novel vs. established patterns properly evaluated -✅ Experience mechanics designed in detail -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not identifying the true core interaction -❌ Missing user's mental model and expectations -❌ Not establishing clear success criteria -❌ Not properly evaluating novel vs. established patterns -❌ Experience mechanics too vague or incomplete -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md` to establish visual design foundation. - -Remember: Do NOT proceed to step-08 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md deleted file mode 100644 index 430aab043..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md +++ /dev/null @@ -1,224 +0,0 @@ -# Step 8: Visual Foundation - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on establishing visual design foundation (colors, typography, spacing) -- 🎯 COLLABORATIVE discovery, not assumption-based design -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating visual foundation content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper visual insights -- **P (Party Mode)**: Bring multiple perspectives to define visual foundation -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Design system choice from step 6 provides component foundation -- Emotional response goals from step 4 inform visual decisions -- Focus on colors, typography, spacing, and layout foundation - -## YOUR TASK: - -Establish the visual design foundation including color themes, typography, and spacing systems. - -## VISUAL FOUNDATION SEQUENCE: - -### 1. Brand Guidelines Assessment - -Check for existing brand requirements: -"Do you have existing brand guidelines or a specific color palette I should follow? (y/n) - -If yes, I'll extract and document your brand colors and create semantic color mappings. -If no, I'll generate theme options based on your project's personality and emotional goals from our earlier discussion." - -### 2. Generate Color Theme Options (If no brand guidelines) - -Create visual exploration opportunities: -"If no existing brand guidelines, I'll create a color theme visualizer to help you explore options. - -🎨 I can generate comprehensive HTML color theme visualizers with multiple theme options, complete UI examples, and the ability to see how colors work in real interface contexts. - -This will help you make an informed decision about the visual direction for {{project_name}}." - -### 3. Define Typography System - -Establish the typographic foundation: -"**Typography Questions:** - -- What should the overall tone feel like? (Professional, friendly, modern, classic?) -- How much text content will users read? (Headings only? Long-form content?) -- Any accessibility requirements for font sizes or contrast? -- Any brand fonts we must use? - -**Typography Strategy:** - -- Choose primary and secondary typefaces -- Establish type scale (h1, h2, h3, body, etc.) -- Define line heights and spacing relationships -- Consider readability and accessibility" - -### 4. Establish Spacing and Layout Foundation - -Define the structural foundation: -"**Spacing and Layout Foundation:** - -- How should the overall layout feel? (Dense and efficient? Airy and spacious?) -- What spacing unit should we use? (4px, 8px, 12px base?) -- How much white space should be between elements? -- Should we use a grid system? If so, what column structure? - -**Layout Principles:** - -- [Layout principle 1 based on product type] -- [Layout principle 2 based on user needs] -- [Layout principle 3 based on platform requirements]" - -### 5. Create Visual Foundation Strategy - -Synthesize all visual decisions: -"**Visual Foundation Strategy:** - -**Color System:** - -- [Color strategy based on brand guidelines or generated themes] -- Semantic color mapping (primary, secondary, success, warning, error, etc.) -- Accessibility compliance (contrast ratios) - -**Typography System:** - -- [Typography strategy based on content needs and tone] -- Type scale and hierarchy -- Font pairing rationale - -**Spacing & Layout:** - -- [Spacing strategy based on content density and platform] -- Grid system approach -- Component spacing relationships - -This foundation will ensure consistency across all our design decisions." - -### 6. Generate Visual Foundation Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Visual Design Foundation - -### Color System - -[Color system strategy based on conversation] - -### Typography System - -[Typography system strategy based on conversation] - -### Spacing & Layout Foundation - -[Spacing and layout foundation based on conversation] - -### Accessibility Considerations - -[Accessibility considerations based on conversation] -``` - -### 7. Present Content and Menu - -Show the generated visual foundation content and present choices: -"I've established the visual design foundation for {{project_name}}. This provides the building blocks for consistent, beautiful design. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Let's refine our visual foundation -[P] Party Mode - Bring design perspectives on visual choices -[C] Continue - Save this to the document and move to design directions - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current visual foundation content -- Process the enhanced visual insights that come back -- Ask user: "Accept these improvements to the visual foundation? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current visual foundation -- Process the collaborative visual insights that come back -- Ask user: "Accept these changes to the visual foundation? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: append step to end of stepsCompleted array -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Brand guidelines assessed and incorporated if available -✅ Color system established with accessibility consideration -✅ Typography system defined with appropriate hierarchy -✅ Spacing and layout foundation created -✅ Visual foundation strategy documented -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not checking for existing brand guidelines first -❌ Color palette not aligned with emotional goals -❌ Typography not suitable for content type or readability needs -❌ Spacing system not appropriate for content density -❌ Missing accessibility considerations -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md` to generate design direction mockups. - -Remember: Do NOT proceed to step-09 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md deleted file mode 100644 index 09864e0b4..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md +++ /dev/null @@ -1,224 +0,0 @@ -# Step 9: Design Direction Mockups - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on generating and evaluating design direction variations -- 🎯 COLLABORATIVE exploration, not assumption-based design -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating design direction content -- 💾 Generate HTML visualizer for design directions -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper design insights -- **P (Party Mode)**: Bring multiple perspectives to evaluate design directions -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Visual foundation from step 8 provides design tokens -- Core experience from step 7 informs layout and interaction design -- Focus on exploring different visual design directions - -## YOUR TASK: - -Generate comprehensive design direction mockups showing different visual approaches for the product. - -## DESIGN DIRECTIONS SEQUENCE: - -### 1. Generate Design Direction Variations - -Create diverse visual explorations: -"I'll generate 6-8 different design direction variations exploring: - -- Different layout approaches and information hierarchy -- Various interaction patterns and visual weights -- Alternative color applications from our foundation -- Different density and spacing approaches -- Various navigation and component arrangements - -Each mockup will show a complete vision for {{project_name}} with all our design decisions applied." - -### 2. Create HTML Design Direction Showcase - -Generate interactive visual exploration: -"🎨 Design Direction Mockups Generated! - -I'm creating a comprehensive HTML design direction showcase at `{planning_artifacts}/ux-design-directions.html` - -**What you'll see:** - -- 6-8 full-screen mockup variations -- Interactive states and hover effects -- Side-by-side comparison tools -- Complete UI examples with real content -- Responsive behavior demonstrations - -Each mockup represents a complete visual direction for your app's look and feel." - -### 3. Present Design Exploration Framework - -Guide evaluation criteria: -"As you explore the design directions, look for: - -✅ **Layout Intuitiveness** - Which information hierarchy matches your priorities? -✅ **Interaction Style** - Which interaction style fits your core experience? -✅ **Visual Weight** - Which visual density feels right for your brand? -✅ **Navigation Approach** - Which navigation pattern matches user expectations? -✅ **Component Usage** - How well do the components support your user journeys? -✅ **Brand Alignment** - Which direction best supports your emotional goals? - -Take your time exploring - this is a crucial decision that will guide all our design work!" - -### 4. Facilitate Design Direction Selection - -Help user choose or combine elements: -"After exploring all the design directions: - -**Which approach resonates most with you?** - -- Pick a favorite direction as-is -- Combine elements from multiple directions -- Request modifications to any direction -- Use one direction as a base and iterate - -**Tell me:** - -- Which layout feels most intuitive for your users? -- Which visual weight matches your brand personality? -- Which interaction style supports your core experience? -- Are there elements from different directions you'd like to combine?" - -### 5. Document Design Direction Decision - -Capture the chosen approach: -"Based on your exploration, I'm understanding your design direction preference: - -**Chosen Direction:** [Direction number or combination] -**Key Elements:** [Specific elements you liked] -**Modifications Needed:** [Any changes requested] -**Rationale:** [Why this direction works for your product] - -This will become our design foundation moving forward. Are we ready to lock this in, or do you want to explore variations?" - -### 6. Generate Design Direction Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Design Direction Decision - -### Design Directions Explored - -[Summary of design directions explored based on conversation] - -### Chosen Direction - -[Chosen design direction based on conversation] - -### Design Rationale - -[Rationale for design direction choice based on conversation] - -### Implementation Approach - -[Implementation approach based on chosen direction] -``` - -### 7. Present Content and Menu - -Show the generated design direction content and present choices: -"I've documented our design direction decision for {{project_name}}. This visual approach will guide all our detailed design work. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Let's refine our design direction -[P] Party Mode - Bring different perspectives on visual choices -[C] Continue - Save this to the document and move to user journey flows - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current design direction content -- Process the enhanced design insights that come back -- Ask user: "Accept these improvements to the design direction? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design direction -- Process the collaborative design insights that come back -- Ask user: "Accept these changes to the design direction? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: append step to end of stepsCompleted array -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Multiple design direction variations generated -✅ HTML showcase created with interactive elements -✅ Design evaluation criteria clearly established -✅ User able to explore and compare directions effectively -✅ Design direction decision made with clear rationale -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not creating enough variation in design directions -❌ Design directions not aligned with established foundation -❌ Missing interactive elements in HTML showcase -❌ Not providing clear evaluation criteria -❌ Rushing decision without thorough exploration -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md` to design user journey flows. - -Remember: Do NOT proceed to step-10 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md deleted file mode 100644 index 9f05201fe..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md +++ /dev/null @@ -1,241 +0,0 @@ -# Step 10: User Journey Flows - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on designing user flows and journey interactions -- 🎯 COLLABORATIVE flow design, not assumption-based layouts -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating user journey content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper journey insights -- **P (Party Mode)**: Bring multiple perspectives to design user flows -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Design direction from step 9 informs flow layout and visual design -- Core experience from step 7 defines key journey interactions -- Focus on designing detailed user flows with Mermaid diagrams - -## YOUR TASK: - -Design detailed user journey flows for critical user interactions. - -## USER JOURNEY FLOWS SEQUENCE: - -### 1. Load PRD User Journeys as Foundation - -Start with user journeys already defined in the PRD: -"Great! Since we have the PRD available, let's build on the user journeys already documented there. - -**Existing User Journeys from PRD:** -I've already loaded these user journeys from your PRD: -[Journey narratives from PRD input documents] - -These journeys tell us **who** users are and **why** they take certain actions. Now we need to design **how** those journeys work in detail. - -**Critical Journeys to Design Flows For:** -Looking at the PRD journeys, I need to design detailed interaction flows for: - -- [Critical journey 1 identified from PRD narratives] -- [Critical journey 2 identified from PRD narratives] -- [Critical journey 3 identified from PRD narratives] - -The PRD gave us the stories - now we design the mechanics!" - -### 2. Design Each Journey Flow - -For each critical journey, design detailed flow: - -**For [Journey Name]:** -"Let's design the flow for users accomplishing [journey goal]. - -**Flow Design Questions:** - -- How do users start this journey? (entry point) -- What information do they need at each step? -- What decisions do they need to make? -- How do they know they're progressing successfully? -- What does success look like for this journey? -- Where might they get confused or stuck? -- How do they recover from errors?" - -### 3. Create Flow Diagrams - -Visualize each journey with Mermaid diagrams: -"I'll create detailed flow diagrams for each journey showing: - -**[Journey Name] Flow:** - -- Entry points and triggers -- Decision points and branches -- Success and failure paths -- Error recovery mechanisms -- Progressive disclosure of information - -Each diagram will map the complete user experience from start to finish." - -### 4. Optimize for Efficiency and Delight - -Refine flows for optimal user experience: -"**Flow Optimization:** -For each journey, let's ensure we're: - -- Minimizing steps to value (getting users to success quickly) -- Reducing cognitive load at each decision point -- Providing clear feedback and progress indicators -- Creating moments of delight or accomplishment -- Handling edge cases and error recovery gracefully - -**Specific Optimizations:** - -- [Optimization 1 for journey efficiency] -- [Optimization 2 for user delight] -- [Optimization 3 for error handling]" - -### 5. Document Journey Patterns - -Extract reusable patterns across journeys: -"**Journey Patterns:** -Across these flows, I'm seeing some common patterns we can standardize: - -**Navigation Patterns:** - -- [Navigation pattern 1] -- [Navigation pattern 2] - -**Decision Patterns:** - -- [Decision pattern 1] -- [Decision pattern 2] - -**Feedback Patterns:** - -- [Feedback pattern 1] -- [Feedback pattern 2] - -These patterns will ensure consistency across all user experiences." - -### 6. Generate User Journey Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## User Journey Flows - -### [Journey 1 Name] - -[Journey 1 description and Mermaid diagram] - -### [Journey 2 Name] - -[Journey 2 description and Mermaid diagram] - -### Journey Patterns - -[Journey patterns identified based on conversation] - -### Flow Optimization Principles - -[Flow optimization principles based on conversation] -``` - -### 7. Present Content and Menu - -Show the generated user journey content and present choices: -"I've designed detailed user journey flows for {{project_name}}. These flows will guide the detailed design of each user interaction. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Let's refine our user journey designs -[P] Party Mode - Bring different perspectives on user flows -[C] Continue - Save this to the document and move to component strategy - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current user journey content -- Process the enhanced journey insights that come back -- Ask user: "Accept these improvements to the user journeys? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current user journeys -- Process the collaborative journey insights that come back -- Ask user: "Accept these changes to the user journeys? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: append step to end of stepsCompleted array -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Critical user journeys identified and designed -✅ Detailed flow diagrams created for each journey -✅ Flows optimized for efficiency and user delight -✅ Common journey patterns extracted and documented -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not identifying all critical user journeys -❌ Flows too complex or not optimized for user success -❌ Missing error recovery paths -❌ Not extracting reusable patterns across journeys -❌ Flow diagrams unclear or incomplete -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md` to define component library strategy. - -Remember: Do NOT proceed to step-11 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md deleted file mode 100644 index 95f2f294a..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md +++ /dev/null @@ -1,248 +0,0 @@ -# Step 11: Component Strategy - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on defining component library strategy and custom components -- 🎯 COLLABORATIVE component planning, not assumption-based design -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating component strategy content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper component insights -- **P (Party Mode)**: Bring multiple perspectives to define component strategy -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Design system choice from step 6 determines available components -- User journeys from step 10 identify component needs -- Focus on defining custom components and implementation strategy - -## YOUR TASK: - -Define component library strategy and design custom components not covered by the design system. - -## COMPONENT STRATEGY SEQUENCE: - -### 1. Analyze Design System Coverage - -Review what components are available vs. needed: -"Based on our chosen design system [design system from step 6], let's identify what components are already available and what we need to create custom. - -**Available from Design System:** -[List of components available in chosen design system] - -**Components Needed for {{project_name}}:** -Looking at our user journeys and design direction, we need: - -- [Component need 1 from journey analysis] -- [Component need 2 from design requirements] -- [Component need 3 from core experience] - -**Gap Analysis:** - -- [Gap 1 - needed but not available] -- [Gap 2 - needed but not available]" - -### 2. Design Custom Components - -For each custom component needed, design thoroughly: - -**For each custom component:** -"**[Component Name] Design:** - -**Purpose:** What does this component do for users? -**Content:** What information or data does it display? -**Actions:** What can users do with this component? -**States:** What different states does it have? (default, hover, active, disabled, error, etc.) -**Variants:** Are there different sizes or styles needed? -**Accessibility:** What ARIA labels and keyboard support needed? - -Let's walk through each custom component systematically." - -### 3. Document Component Specifications - -Create detailed specifications for each component: - -**Component Specification Template:** - -```markdown -### [Component Name] - -**Purpose:** [Clear purpose statement] -**Usage:** [When and how to use] -**Anatomy:** [Visual breakdown of parts] -**States:** [All possible states with descriptions] -**Variants:** [Different sizes/styles if applicable] -**Accessibility:** [ARIA labels, keyboard navigation] -**Content Guidelines:** [What content works best] -**Interaction Behavior:** [How users interact] -``` - -### 4. Define Component Strategy - -Establish overall component library approach: -"**Component Strategy:** - -**Foundation Components:** (from design system) - -- [Foundation component 1] -- [Foundation component 2] - -**Custom Components:** (designed in this step) - -- [Custom component 1 with rationale] -- [Custom component 2 with rationale] - -**Implementation Approach:** - -- Build custom components using design system tokens -- Ensure consistency with established patterns -- Follow accessibility best practices -- Create reusable patterns for common use cases" - -### 5. Plan Implementation Roadmap - -Define how and when to build components: -"**Implementation Roadmap:** - -**Phase 1 - Core Components:** - -- [Component 1] - needed for [critical flow] -- [Component 2] - needed for [critical flow] - -**Phase 2 - Supporting Components:** - -- [Component 3] - enhances [user experience] -- [Component 4] - supports [design pattern] - -**Phase 3 - Enhancement Components:** - -- [Component 5] - optimizes [user journey] -- [Component 6] - adds [special feature] - -This roadmap helps prioritize development based on user journey criticality." - -### 6. Generate Component Strategy Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Component Strategy - -### Design System Components - -[Analysis of available design system components based on conversation] - -### Custom Components - -[Custom component specifications based on conversation] - -### Component Implementation Strategy - -[Component implementation strategy based on conversation] - -### Implementation Roadmap - -[Implementation roadmap based on conversation] -``` - -### 7. Present Content and Menu - -Show the generated component strategy content and present choices: -"I've defined the component strategy for {{project_name}}. This balances using proven design system components with custom components for your unique needs. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Let's refine our component strategy -[P] Party Mode - Bring technical perspectives on component design -[C] Continue - Save this to the document and move to UX patterns - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current component strategy content -- Process the enhanced component insights that come back -- Ask user: "Accept these improvements to the component strategy? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current component strategy -- Process the collaborative component insights that come back -- Ask user: "Accept these changes to the component strategy? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: append step to end of stepsCompleted array -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Design system coverage properly analyzed -✅ All custom components thoroughly specified -✅ Component strategy clearly defined -✅ Implementation roadmap prioritized by user need -✅ Accessibility considered for all components -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not analyzing design system coverage properly -❌ Custom components not thoroughly specified -❌ Missing accessibility considerations -❌ Component strategy not aligned with user journeys -❌ Implementation roadmap not prioritized effectively -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md` to define UX consistency patterns. - -Remember: Do NOT proceed to step-12 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md deleted file mode 100644 index 08f272a62..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md +++ /dev/null @@ -1,237 +0,0 @@ -# Step 12: UX Consistency Patterns - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on establishing consistency patterns for common UX situations -- 🎯 COLLABORATIVE pattern definition, not assumption-based design -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating UX patterns content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper pattern insights -- **P (Party Mode)**: Bring multiple perspectives to define UX patterns -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Component strategy from step 11 informs pattern decisions -- User journeys from step 10 identify common pattern needs -- Focus on consistency patterns for common UX situations - -## YOUR TASK: - -Establish UX consistency patterns for common situations like buttons, forms, navigation, and feedback. - -## UX PATTERNS SEQUENCE: - -### 1. Identify Pattern Categories - -Determine which patterns need definition for your product: -"Let's establish consistency patterns for how {{project_name}} behaves in common situations. - -**Pattern Categories to Define:** - -- Button hierarchy and actions -- Feedback patterns (success, error, warning, info) -- Form patterns and validation -- Navigation patterns -- Modal and overlay patterns -- Empty states and loading states -- Search and filtering patterns - -Which categories are most critical for your product? We can go through each thoroughly or focus on the most important ones." - -### 2. Define Critical Patterns First - -Focus on patterns most relevant to your product: - -**For [Critical Pattern Category]:** -"**[Pattern Type] Patterns:** -What should users see/do when they need to [pattern action]? - -**Considerations:** - -- Visual hierarchy (primary vs. secondary actions) -- Feedback mechanisms -- Error recovery -- Accessibility requirements -- Mobile vs. desktop considerations - -**Examples:** - -- [Example 1 for this pattern type] -- [Example 2 for this pattern type] - -How should {{project_name}} handle [pattern type] interactions?" - -### 3. Establish Pattern Guidelines - -Document specific design decisions: - -**Pattern Guidelines Template:** - -```markdown -### [Pattern Type] - -**When to Use:** [Clear usage guidelines] -**Visual Design:** [How it should look] -**Behavior:** [How it should interact] -**Accessibility:** [A11y requirements] -**Mobile Considerations:** [Mobile-specific needs] -**Variants:** [Different states or styles if applicable] -``` - -### 4. Design System Integration - -Ensure patterns work with chosen design system: -"**Integration with [Design System]:** - -- How do these patterns complement our design system components? -- What customizations are needed? -- How do we maintain consistency while meeting unique needs? - -**Custom Pattern Rules:** - -- [Custom rule 1] -- [Custom rule 2] -- [Custom rule 3]" - -### 5. Create Pattern Documentation - -Generate comprehensive pattern library: - -**Pattern Library Structure:** - -- Clear usage guidelines for each pattern -- Visual examples and specifications -- Implementation notes for developers -- Accessibility checklists -- Mobile-first considerations - -### 6. Generate UX Patterns Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## UX Consistency Patterns - -### Button Hierarchy - -[Button hierarchy patterns based on conversation] - -### Feedback Patterns - -[Feedback patterns based on conversation] - -### Form Patterns - -[Form patterns based on conversation] - -### Navigation Patterns - -[Navigation patterns based on conversation] - -### Additional Patterns - -[Additional patterns based on conversation] -``` - -### 7. Present Content and Menu - -Show the generated UX patterns content and present choices: -"I've established UX consistency patterns for {{project_name}}. These patterns ensure users have a consistent, predictable experience across all interactions. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Let's refine our UX patterns -[P] Party Mode - Bring different perspectives on consistency patterns -[C] Continue - Save this to the document and move to responsive design - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current UX patterns content -- Process the enhanced pattern insights that come back -- Ask user: "Accept these improvements to the UX patterns? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current UX patterns -- Process the collaborative pattern insights that come back -- Ask user: "Accept these changes to the UX patterns? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: append step to end of stepsCompleted array -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Critical pattern categories identified and prioritized -✅ Consistency patterns clearly defined and documented -✅ Patterns integrated with chosen design system -✅ Accessibility considerations included for all patterns -✅ Mobile-first approach incorporated -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not identifying the most critical pattern categories -❌ Patterns too generic or not actionable -❌ Missing accessibility considerations -❌ Patterns not aligned with design system -❌ Not considering mobile differences -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md` to define responsive design and accessibility strategy. - -Remember: Do NOT proceed to step-13 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md deleted file mode 100644 index d13ffa5c4..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md +++ /dev/null @@ -1,264 +0,0 @@ -# Step 13: Responsive Design & Accessibility - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder -- 📋 YOU ARE A UX FACILITATOR, not a content generator -- 💬 FOCUS on responsive design strategy and accessibility compliance -- 🎯 COLLABORATIVE strategy definition, not assumption-based design -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating responsive/accessibility content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted. -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper responsive/accessibility insights -- **P (Party Mode)**: Bring multiple perspectives to define responsive/accessibility strategy -- **C (Continue)**: Save the content to the document and proceed to final step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to this step's A/P/C menu -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from previous steps are available -- Platform requirements from step 3 inform responsive design -- Design direction from step 9 influences responsive layout choices -- Focus on cross-device adaptation and accessibility compliance - -## YOUR TASK: - -Define responsive design strategy and accessibility requirements for the product. - -## RESPONSIVE & ACCESSIBILITY SEQUENCE: - -### 1. Define Responsive Strategy - -Establish how the design adapts across devices: -"Let's define how {{project_name}} adapts across different screen sizes and devices. - -**Responsive Design Questions:** - -**Desktop Strategy:** - -- How should we use extra screen real estate? -- Multi-column layouts, side navigation, or content density? -- What desktop-specific features can we include? - -**Tablet Strategy:** - -- Should we use simplified layouts or touch-optimized interfaces? -- How do gestures and touch interactions work on tablets? -- What's the optimal information density for tablet screens? - -**Mobile Strategy:** - -- Bottom navigation or hamburger menu? -- How do layouts collapse on small screens? -- What's the most critical information to show mobile-first?" - -### 2. Establish Breakpoint Strategy - -Define when and how layouts change: -"**Breakpoint Strategy:** -We need to define screen size breakpoints where layouts adapt. - -**Common Breakpoints:** - -- Mobile: 320px - 767px -- Tablet: 768px - 1023px -- Desktop: 1024px+ - -**For {{project_name}}, should we:** - -- Use standard breakpoints or custom ones? -- Focus on mobile-first or desktop-first design? -- Have specific breakpoints for your key use cases?" - -### 3. Design Accessibility Strategy - -Define accessibility requirements and compliance level: -"**Accessibility Strategy:** -What level of WCAG compliance does {{project_name}} need? - -**WCAG Levels:** - -- **Level A (Basic)** - Essential accessibility for legal compliance -- **Level AA (Recommended)** - Industry standard for good UX -- **Level AAA (Highest)** - Exceptional accessibility (rarely needed) - -**Based on your product:** - -- [Recommendation based on user base, legal requirements, etc.] - -**Key Accessibility Considerations:** - -- Color contrast ratios (4.5:1 for normal text) -- Keyboard navigation support -- Screen reader compatibility -- Touch target sizes (minimum 44x44px) -- Focus indicators and skip links" - -### 4. Define Testing Strategy - -Plan how to ensure responsive design and accessibility: -"**Testing Strategy:** - -**Responsive Testing:** - -- Device testing on actual phones/tablets -- Browser testing across Chrome, Firefox, Safari, Edge -- Real device network performance testing - -**Accessibility Testing:** - -- Automated accessibility testing tools -- Screen reader testing (VoiceOver, NVDA, JAWS) -- Keyboard-only navigation testing -- Color blindness simulation testing - -**User Testing:** - -- Include users with disabilities in testing -- Test with diverse assistive technologies -- Validate with actual target devices" - -### 5. Document Implementation Guidelines - -Create specific guidelines for developers: -"**Implementation Guidelines:** - -**Responsive Development:** - -- Use relative units (rem, %, vw, vh) over fixed pixels -- Implement mobile-first media queries -- Test touch targets and gesture areas -- Optimize images and assets for different devices - -**Accessibility Development:** - -- Semantic HTML structure -- ARIA labels and roles -- Keyboard navigation implementation -- Focus management and skip links -- High contrast mode support" - -### 6. Generate Responsive & Accessibility Content - -Prepare the content to append to the document: - -#### Content Structure: - -When saving to document, append these Level 2 and Level 3 sections: - -```markdown -## Responsive Design & Accessibility - -### Responsive Strategy - -[Responsive strategy based on conversation] - -### Breakpoint Strategy - -[Breakpoint strategy based on conversation] - -### Accessibility Strategy - -[Accessibility strategy based on conversation] - -### Testing Strategy - -[Testing strategy based on conversation] - -### Implementation Guidelines - -[Implementation guidelines based on conversation] -``` - -### 7. Present Content and Menu - -Show the generated responsive and accessibility content and present choices: -"I've defined the responsive design and accessibility strategy for {{project_name}}. This ensures your product works beautifully across all devices and is accessible to all users. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Let's refine our responsive/accessibility strategy -[P] Party Mode - Bring different perspectives on inclusive design -[C] Continue - Save this to the document and complete the workflow - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current responsive/accessibility content -- Process the enhanced insights that come back -- Ask user: "Accept these improvements to the responsive/accessibility strategy? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy -- Process the collaborative insights that come back -- Ask user: "Accept these changes to the responsive/accessibility strategy? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/ux-design-specification.md` -- Update frontmatter: append step to end of stepsCompleted array -- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Responsive strategy clearly defined for all device types -✅ Appropriate breakpoint strategy established -✅ Accessibility requirements determined and documented -✅ Comprehensive testing strategy planned -✅ Implementation guidelines provided for development team -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not considering all device types and screen sizes -❌ Accessibility requirements not properly researched -❌ Testing strategy not comprehensive enough -❌ Implementation guidelines too generic or unclear -❌ Not addressing specific accessibility challenges for your product -❌ Not presenting A/P/C menu after content generation -❌ Appending content without user selecting 'C' - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md` to finalize the UX design workflow. - -Remember: Do NOT proceed to step-14 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md deleted file mode 100644 index 62a02cf45..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md +++ /dev/null @@ -1,171 +0,0 @@ -# Step 14: Workflow Completion - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ THIS IS A FINAL STEP - Workflow completion required - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- 🛑 NO content generation - this is a wrap-up step -- 📋 FINALIZE document and update workflow status -- 💬 FOCUS on completion, validation, and next steps -- 🎯 UPDATE workflow status files with completion information -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 💾 Update the main workflow status file with completion information -- 📖 Suggest potential next workflow steps for the user -- 🚫 DO NOT load additional steps after this one - -## TERMINATION STEP PROTOCOLS: - -- This is a FINAL step - workflow completion required -- 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted to indicate all is finished.. -- Output completion summary and next step guidance -- Update the main workflow status file with finalized document -- Suggest potential next workflow steps for the user -- Mark workflow as complete in status tracking - -## CONTEXT BOUNDARIES: - -- Complete UX design specification is available from all previous steps -- Workflow frontmatter shows all completed steps -- All collaborative content has been generated and saved -- Focus on completion, validation, and next steps - -## YOUR TASK: - -Complete the UX design workflow, update status files, and suggest next steps for the project. - -## WORKFLOW COMPLETION SEQUENCE: - -### 1. Announce Workflow Completion - -Inform user that the UX design is complete: -"🎉 **UX Design Complete, {{user_name}}!** - -I've successfully collaborated with you to create a comprehensive UX design specification for {{project_name}}. - -**What we've accomplished:** - -- ✅ Project understanding and user insights -- ✅ Core experience and emotional response definition -- ✅ UX pattern analysis and inspiration -- ✅ Design system choice and implementation strategy -- ✅ Core interaction definition and experience mechanics -- ✅ Visual design foundation (colors, typography, spacing) -- ✅ Design direction mockups and visual explorations -- ✅ User journey flows and interaction design -- ✅ Component strategy and custom component specifications -- ✅ UX consistency patterns for common interactions -- ✅ Responsive design and accessibility strategy - -**The complete UX design specification is now available at:** `{planning_artifacts}/ux-design-specification.md` - -**Supporting Visual Assets:** - -- Color themes visualizer: `{planning_artifacts}/ux-color-themes.html` -- Design directions mockups: `{planning_artifacts}/ux-design-directions.html` - -This specification is now ready to guide visual design, implementation, and development." - -### 2. Workflow Status Update - -Update the main workflow status file: - -- Load `{status_file}` from workflow configuration (if exists) -- Update workflow_status["create-ux-design"] = "{default_output_file}" -- Save file, preserving all comments and structure -- Mark current timestamp as completion time - -### 3. Suggest Next Steps - -UX Design complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` - -### 5. Final Completion Confirmation - -Congratulate the user on the completion you both completed together of the UX. - - - -## SUCCESS METRICS: - -✅ UX design specification contains all required sections -✅ All collaborative content properly saved to document -✅ Workflow status file updated with completion information -✅ Clear next step guidance provided to user -✅ Document quality validation completed -✅ User acknowledges completion and understands next options - -## FAILURE MODES: - -❌ Not updating workflow status file with completion information -❌ Missing clear next step guidance for user -❌ Not confirming document completeness with user -❌ Workflow not properly marked as complete in status tracking -❌ User unclear about what happens next - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## WORKFLOW COMPLETION CHECKLIST: - -### Design Specification Complete: - -- [ ] Executive summary and project understanding -- [ ] Core experience and emotional response definition -- [ ] UX pattern analysis and inspiration -- [ ] Design system choice and strategy -- [ ] Core interaction mechanics definition -- [ ] Visual design foundation (colors, typography, spacing) -- [ ] Design direction decisions and mockups -- [ ] User journey flows and interaction design -- [ ] Component strategy and specifications -- [ ] UX consistency patterns documentation -- [ ] Responsive design and accessibility strategy - -### Process Complete: - -- [ ] All steps completed with user confirmation -- [ ] All content saved to specification document -- [ ] Frontmatter properly updated with all steps -- [ ] Workflow status file updated with completion -- [ ] Next steps clearly communicated - -## NEXT STEPS GUIDANCE: - -**Immediate Options:** - -1. **Wireframe Generation** - Create low-fidelity layouts based on UX spec -2. **Interactive Prototype** - Build clickable prototypes for testing -3. **Solution Architecture** - Technical design with UX context -4. **Figma Visual Design** - High-fidelity UI implementation -5. **Epic Creation** - Break down UX requirements for development - -**Recommended Sequence:** -For design-focused teams: Wireframes → Prototypes → Figma Design → Development -For technical teams: Architecture → Epic Creation → Development - -Consider team capacity, timeline, and whether user validation is needed before implementation. - -## WORKFLOW FINALIZATION: - -- Set `lastStep = 14` in document frontmatter -- Update workflow status file with completion timestamp -- Provide completion summary to user -- Do NOT load any additional steps - -## FINAL REMINDER: - -This UX design workflow is now complete. The specification serves as the foundation for all visual and development work. All design decisions, patterns, and requirements are documented to ensure consistent, accessible, and user-centered implementation. - -**Congratulations on completing the UX Design Specification for {{project_name}}!** 🎉 - -**Core Deliverables:** - -- ✅ UX Design Specification: `{planning_artifacts}/ux-design-specification.md` -- ✅ Color Themes Visualizer: `{planning_artifacts}/ux-color-themes.html` -- ✅ Design Directions: `{planning_artifacts}/ux-design-directions.html` diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md deleted file mode 100644 index aeed9dc54..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -stepsCompleted: [] -inputDocuments: [] ---- - -# UX Design Specification {{project_name}} - -**Author:** {{user_name}} -**Date:** {{date}} - ---- - - diff --git a/src/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md b/src/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md deleted file mode 100644 index 4dfdba9f1..000000000 --- a/src/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -name: create-ux-design -description: 'Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"' ---- - -# Create UX Design Workflow - -**Goal:** Create comprehensive UX design specifications through collaborative visual exploration and informed decision-making where you act as a UX facilitator working with a product stakeholder. - ---- - -## WORKFLOW ARCHITECTURE - -This uses **micro-file architecture** for disciplined execution: - -- Each step is a self-contained file with embedded rules -- Sequential progression with user control at each step -- Document state tracked in frontmatter -- Append-only document building through conversation - ---- - -## INITIALIZATION - -### Configuration Loading - -Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve: - -- `project_name`, `output_folder`, `planning_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as system-generated current datetime - -### Paths - -- `installed_path` = `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design` -- `template_path` = `{installed_path}/ux-design-template.md` -- `default_output_file` = `{planning_artifacts}/ux-design-specification.md` - -## EXECUTION - -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` -- Read fully and follow: `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md` to begin the UX design workflow. diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md deleted file mode 100644 index 877193f3d..000000000 --- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -name: 'step-01-document-discovery' -description: 'Discover and inventory all project documents, handling duplicates and organizing file structure' - -nextStepFile: './step-02-prd-analysis.md' -outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md' -templateFile: '../templates/readiness-report-template.md' ---- - -# Step 1: Document Discovery - -## STEP GOAL: - -To discover, inventory, and organize all project documents, identifying duplicates and determining which versions to use for the assessment. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are an expert Product Manager and Scrum Master -- ✅ Your focus is on finding organizing and documenting what exists -- ✅ You identify ambiguities and ask for clarification -- ✅ Success is measured in clear file inventory and conflict resolution - -### Step-Specific Rules: - -- 🎯 Focus ONLY on finding and organizing files -- 🚫 Don't read or analyze file contents -- 💬 Identify duplicate documents clearly -- 🚪 Get user confirmation on file selections - -## EXECUTION PROTOCOLS: - -- 🎯 Search for all document types systematically -- 💾 Group sharded files together -- 📖 Flag duplicates for user resolution -- 🚫 FORBIDDEN to proceed with unresolved duplicates - -## DOCUMENT DISCOVERY PROCESS: - -### 1. Initialize Document Discovery - -"Beginning **Document Discovery** to inventory all project files. - -I will: - -1. Search for all required documents (PRD, Architecture, Epics, UX) -2. Group sharded documents together -3. Identify any duplicates (whole + sharded versions) -4. Present findings for your confirmation" - -### 2. Document Search Patterns - -Search for each document type using these patterns: - -#### A. PRD Documents - -- Whole: `{planning_artifacts}/*prd*.md` -- Sharded: `{planning_artifacts}/*prd*/index.md` and related files - -#### B. Architecture Documents - -- Whole: `{planning_artifacts}/*architecture*.md` -- Sharded: `{planning_artifacts}/*architecture*/index.md` and related files - -#### C. Epics & Stories Documents - -- Whole: `{planning_artifacts}/*epic*.md` -- Sharded: `{planning_artifacts}/*epic*/index.md` and related files - -#### D. UX Design Documents - -- Whole: `{planning_artifacts}/*ux*.md` -- Sharded: `{planning_artifacts}/*ux*/index.md` and related files - -### 3. Organize Findings - -For each document type found: - -``` -## [Document Type] Files Found - -**Whole Documents:** -- [filename.md] ([size], [modified date]) - -**Sharded Documents:** -- Folder: [foldername]/ - - index.md - - [other files in folder] -``` - -### 4. Identify Critical Issues - -#### Duplicates (CRITICAL) - -If both whole and sharded versions exist: - -``` -⚠️ CRITICAL ISSUE: Duplicate document formats found -- PRD exists as both whole.md AND prd/ folder -- YOU MUST choose which version to use -- Remove or rename the other version to avoid confusion -``` - -#### Missing Documents (WARNING) - -If required documents not found: - -``` -⚠️ WARNING: Required document not found -- Architecture document not found -- Will impact assessment completeness -``` - -### 5. Add Initial Report Section - -Initialize {outputFile} with {templateFile}. - -### 6. Present Findings and Get Confirmation - -Display findings and ask: -"**Document Discovery Complete** - -[Show organized file list] - -**Issues Found:** - -- [List any duplicates requiring resolution] -- [List any missing documents] - -**Required Actions:** - -- If duplicates exist: Please remove/rename one version -- Confirm which documents to use for assessment - -**Ready to proceed?** [C] Continue after resolving issues" - -### 7. Present MENU OPTIONS - -Display: **Select an Option:** [C] Continue to File Validation - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed with 'C' selection -- If duplicates identified, insist on resolution first -- User can clarify file locations or request additional searches - -#### Menu Handling Logic: - -- IF C: Save document inventory to {outputFile}, update frontmatter with completed step and files being included, and then read fully and follow: {nextStepFile} -- IF Any other comments or queries: help user respond then redisplay menu - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN C is selected and document inventory is saved will you load {nextStepFile} to begin file validation. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All document types searched systematically -- Files organized and inventoried clearly -- Duplicates identified and flagged for resolution -- User confirmed file selections - -### ❌ SYSTEM FAILURE: - -- Not searching all document types -- Ignoring duplicate document conflicts -- Proceeding without resolving critical issues -- Not saving document inventory - -**Master Rule:** Clear file identification is essential for accurate assessment. diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-02-prd-analysis.md b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-02-prd-analysis.md deleted file mode 100644 index 4d22e7da9..000000000 --- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-02-prd-analysis.md +++ /dev/null @@ -1,172 +0,0 @@ ---- -name: 'step-02-prd-analysis' -description: 'Read and analyze PRD to extract all FRs and NFRs for coverage validation' - -nextStepFile: './step-03-epic-coverage-validation.md' -outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md' -epicsFile: '{planning_artifacts}/*epic*.md' # Will be resolved to actual file ---- - -# Step 2: PRD Analysis - -## STEP GOAL: - -To fully read and analyze the PRD document (whole or sharded) to extract all Functional Requirements (FRs) and Non-Functional Requirements (NFRs) for validation against epics coverage. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are an expert Product Manager and Scrum Master -- ✅ Your expertise is in requirements analysis and traceability -- ✅ You think critically about requirement completeness -- ✅ Success is measured in thorough requirement extraction - -### Step-Specific Rules: - -- 🎯 Focus ONLY on reading and extracting from PRD -- 🚫 Don't validate files (done in step 1) -- 💬 Read PRD completely - whole or all sharded files -- 🚪 Extract every FR and NFR with numbering - -## EXECUTION PROTOCOLS: - -- 🎯 Load and completely read the PRD -- 💾 Extract all requirements systematically -- 📖 Document findings in the report -- 🚫 FORBIDDEN to skip or summarize PRD content - -## PRD ANALYSIS PROCESS: - -### 1. Initialize PRD Analysis - -"Beginning **PRD Analysis** to extract all requirements. - -I will: - -1. Load the PRD document (whole or sharded) -2. Read it completely and thoroughly -3. Extract ALL Functional Requirements (FRs) -4. Extract ALL Non-Functional Requirements (NFRs) -5. Document findings for coverage validation" - -### 2. Load and Read PRD - -From the document inventory in step 1: - -- If whole PRD file exists: Load and read it completely -- If sharded PRD exists: Load and read ALL files in the PRD folder -- Ensure complete coverage - no files skipped - -### 3. Extract Functional Requirements (FRs) - -Search for and extract: - -- Numbered FRs (FR1, FR2, FR3, etc.) -- Requirements labeled "Functional Requirement" -- User stories or use cases that represent functional needs -- Business rules that must be implemented - -Format findings as: - -``` -## Functional Requirements Extracted - -FR1: [Complete requirement text] -FR2: [Complete requirement text] -FR3: [Complete requirement text] -... -Total FRs: [count] -``` - -### 4. Extract Non-Functional Requirements (NFRs) - -Search for and extract: - -- Performance requirements (response times, throughput) -- Security requirements (authentication, encryption, etc.) -- Usability requirements (accessibility, ease of use) -- Reliability requirements (uptime, error rates) -- Scalability requirements (concurrent users, data growth) -- Compliance requirements (standards, regulations) - -Format findings as: - -``` -## Non-Functional Requirements Extracted - -NFR1: [Performance requirement] -NFR2: [Security requirement] -NFR3: [Usability requirement] -... -Total NFRs: [count] -``` - -### 5. Document Additional Requirements - -Look for: - -- Constraints or assumptions -- Technical requirements not labeled as FR/NFR -- Business constraints -- Integration requirements - -### 6. Add to Assessment Report - -Append to {outputFile}: - -```markdown -## PRD Analysis - -### Functional Requirements - -[Complete FR list from section 3] - -### Non-Functional Requirements - -[Complete NFR list from section 4] - -### Additional Requirements - -[Any other requirements or constraints found] - -### PRD Completeness Assessment - -[Initial assessment of PRD completeness and clarity] -``` - -### 7. Auto-Proceed to Next Step - -After PRD analysis complete, immediately load next step for epic coverage validation. - -## PROCEEDING TO EPIC COVERAGE VALIDATION - -PRD analysis complete. Loading next step to validate epic coverage. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- PRD loaded and read completely -- All FRs extracted with full text -- All NFRs identified and documented -- Findings added to assessment report - -### ❌ SYSTEM FAILURE: - -- Not reading complete PRD (especially sharded versions) -- Missing requirements in extraction -- Summarizing instead of extracting full text -- Not documenting findings in report - -**Master Rule:** Complete requirement extraction is essential for traceability validation. diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-03-epic-coverage-validation.md b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-03-epic-coverage-validation.md deleted file mode 100644 index b73511bea..000000000 --- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-03-epic-coverage-validation.md +++ /dev/null @@ -1,173 +0,0 @@ ---- -name: 'step-03-epic-coverage-validation' -description: 'Validate that all PRD FRs are covered in epics and stories' - -nextStepFile: './step-04-ux-alignment.md' -outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md' ---- - -# Step 3: Epic Coverage Validation - -## STEP GOAL: - -To validate that all Functional Requirements from the PRD are captured in the epics and stories document, identifying any gaps in coverage. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are an expert Product Manager and Scrum Master -- ✅ Your expertise is in requirements traceability -- ✅ You ensure no requirements fall through the cracks -- ✅ Success is measured in complete FR coverage - -### Step-Specific Rules: - -- 🎯 Focus ONLY on FR coverage validation -- 🚫 Don't analyze story quality (that's later) -- 💬 Compare PRD FRs against epic coverage list -- 🚪 Document every missing FR - -## EXECUTION PROTOCOLS: - -- 🎯 Load epics document completely -- 💾 Extract FR coverage from epics -- 📖 Compare against PRD FR list -- 🚫 FORBIDDEN to proceed without documenting gaps - -## EPIC COVERAGE VALIDATION PROCESS: - -### 1. Initialize Coverage Validation - -"Beginning **Epic Coverage Validation**. - -I will: - -1. Load the epics and stories document -2. Extract FR coverage information -3. Compare against PRD FRs from previous step -4. Identify any FRs not covered in epics" - -### 2. Load Epics Document - -From the document inventory in step 1: - -- Load the epics and stories document (whole or sharded) -- Read it completely to find FR coverage information -- Look for sections like "FR Coverage Map" or similar - -### 3. Extract Epic FR Coverage - -From the epics document: - -- Find FR coverage mapping or list -- Extract which FR numbers are claimed to be covered -- Document which epics cover which FRs - -Format as: - -``` -## Epic FR Coverage Extracted - -FR1: Covered in Epic X -FR2: Covered in Epic Y -FR3: Covered in Epic Z -... -Total FRs in epics: [count] -``` - -### 4. Compare Coverage Against PRD - -Using the PRD FR list from step 2: - -- Check each PRD FR against epic coverage -- Identify FRs NOT covered in epics -- Note any FRs in epics but NOT in PRD - -Create coverage matrix: - -``` -## FR Coverage Analysis - -| FR Number | PRD Requirement | Epic Coverage | Status | -| --------- | --------------- | -------------- | --------- | -| FR1 | [PRD text] | Epic X Story Y | ✓ Covered | -| FR2 | [PRD text] | **NOT FOUND** | ❌ MISSING | -| FR3 | [PRD text] | Epic Z Story A | ✓ Covered | -``` - -### 5. Document Missing Coverage - -List all FRs not covered: - -``` -## Missing FR Coverage - -### Critical Missing FRs - -FR#: [Full requirement text from PRD] -- Impact: [Why this is critical] -- Recommendation: [Which epic should include this] - -### High Priority Missing FRs - -[List any other uncovered FRs] -``` - -### 6. Add to Assessment Report - -Append to {outputFile}: - -```markdown -## Epic Coverage Validation - -### Coverage Matrix - -[Complete coverage matrix from section 4] - -### Missing Requirements - -[List of uncovered FRs from section 5] - -### Coverage Statistics - -- Total PRD FRs: [count] -- FRs covered in epics: [count] -- Coverage percentage: [percentage] -``` - -### 7. Auto-Proceed to Next Step - -After coverage validation complete, immediately load next step. - -## PROCEEDING TO UX ALIGNMENT - -Epic coverage validation complete. Loading next step for UX alignment. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Epics document loaded completely -- FR coverage extracted accurately -- All gaps identified and documented -- Coverage matrix created - -### ❌ SYSTEM FAILURE: - -- Not reading complete epics document -- Missing FRs in comparison -- Not documenting uncovered requirements -- Incomplete coverage analysis - -**Master Rule:** Every FR must have a traceable implementation path. diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-04-ux-alignment.md b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-04-ux-alignment.md deleted file mode 100644 index 236ad3b51..000000000 --- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-04-ux-alignment.md +++ /dev/null @@ -1,133 +0,0 @@ ---- -name: 'step-04-ux-alignment' -description: 'Check for UX document and validate alignment with PRD and Architecture' - -nextStepFile: './step-05-epic-quality-review.md' -outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md' ---- - -# Step 4: UX Alignment - -## STEP GOAL: - -To check if UX documentation exists and validate that it aligns with PRD requirements and Architecture decisions, ensuring architecture accounts for both PRD and UX needs. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a UX VALIDATOR ensuring user experience is properly addressed -- ✅ UX requirements must be supported by architecture -- ✅ Missing UX documentation is a warning if UI is implied -- ✅ Alignment gaps must be documented - -### Step-Specific Rules: - -- 🎯 Check for UX document existence first -- 🚫 Don't assume UX is not needed -- 💬 Validate alignment between UX, PRD, and Architecture -- 🚪 Add findings to the output report - -## EXECUTION PROTOCOLS: - -- 🎯 Search for UX documentation -- 💾 If found, validate alignment -- 📖 If not found, assess if UX is implied -- 🚫 FORBIDDEN to proceed without completing assessment - -## UX ALIGNMENT PROCESS: - -### 1. Initialize UX Validation - -"Beginning **UX Alignment** validation. - -I will: - -1. Check if UX documentation exists -2. If UX exists: validate alignment with PRD and Architecture -3. If no UX: determine if UX is implied and document warning" - -### 2. Search for UX Documentation - -Search patterns: - -- `{planning_artifacts}/*ux*.md` (whole document) -- `{planning_artifacts}/*ux*/index.md` (sharded) -- Look for UI-related terms in other documents - -### 3. If UX Document Exists - -#### A. UX ↔ PRD Alignment - -- Check UX requirements reflected in PRD -- Verify user journeys in UX match PRD use cases -- Identify UX requirements not in PRD - -#### B. UX ↔ Architecture Alignment - -- Verify architecture supports UX requirements -- Check performance needs (responsiveness, load times) -- Identify UI components not supported by architecture - -### 4. If No UX Document - -Assess if UX/UI is implied: - -- Does PRD mention user interface? -- Are there web/mobile components implied? -- Is this a user-facing application? - -If UX implied but missing: Add warning to report - -### 5. Add Findings to Report - -Append to {outputFile}: - -```markdown -## UX Alignment Assessment - -### UX Document Status - -[Found/Not Found] - -### Alignment Issues - -[List any misalignments between UX, PRD, and Architecture] - -### Warnings - -[Any warnings about missing UX or architectural gaps] -``` - -### 6. Auto-Proceed to Next Step - -After UX assessment complete, immediately load next step. - -## PROCEEDING TO EPIC QUALITY REVIEW - -UX alignment assessment complete. Loading next step for epic quality review. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- UX document existence checked -- Alignment validated if UX exists -- Warning issued if UX implied but missing -- Findings added to report - -### ❌ SYSTEM FAILURE: - -- Not checking for UX document -- Ignoring alignment issues -- Not documenting warnings diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-05-epic-quality-review.md b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-05-epic-quality-review.md deleted file mode 100644 index 9f6d087f8..000000000 --- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-05-epic-quality-review.md +++ /dev/null @@ -1,245 +0,0 @@ ---- -name: 'step-05-epic-quality-review' -description: 'Validate epics and stories against create-epics-and-stories best practices' - -nextStepFile: './step-06-final-assessment.md' -outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md' ---- - -# Step 5: Epic Quality Review - -## STEP GOAL: - -To validate epics and stories against the best practices defined in create-epics-and-stories workflow, focusing on user value, independence, dependencies, and implementation readiness. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are an EPIC QUALITY ENFORCER -- ✅ You know what good epics look like - challenge anything deviating -- ✅ Technical epics are wrong - find them -- ✅ Forward dependencies are forbidden - catch them -- ✅ Stories must be independently completable - -### Step-Specific Rules: - -- 🎯 Apply create-epics-and-stories standards rigorously -- 🚫 Don't accept "technical milestones" as epics -- 💬 Challenge every dependency on future work -- 🚪 Verify proper story sizing and structure - -## EXECUTION PROTOCOLS: - -- 🎯 Systematically validate each epic and story -- 💾 Document all violations of best practices -- 📖 Check every dependency relationship -- 🚫 FORBIDDEN to accept structural problems - -## EPIC QUALITY REVIEW PROCESS: - -### 1. Initialize Best Practices Validation - -"Beginning **Epic Quality Review** against create-epics-and-stories standards. - -I will rigorously validate: - -- Epics deliver user value (not technical milestones) -- Epic independence (Epic 2 doesn't need Epic 3) -- Story dependencies (no forward references) -- Proper story sizing and completeness - -Any deviation from best practices will be flagged as a defect." - -### 2. Epic Structure Validation - -#### A. User Value Focus Check - -For each epic: - -- **Epic Title:** Is it user-centric (what user can do)? -- **Epic Goal:** Does it describe user outcome? -- **Value Proposition:** Can users benefit from this epic alone? - -**Red flags (violations):** - -- "Setup Database" or "Create Models" - no user value -- "API Development" - technical milestone -- "Infrastructure Setup" - not user-facing -- "Authentication System" - borderline (is it user value?) - -#### B. Epic Independence Validation - -Test epic independence: - -- **Epic 1:** Must stand alone completely -- **Epic 2:** Can function using only Epic 1 output -- **Epic 3:** Can function using Epic 1 & 2 outputs -- **Rule:** Epic N cannot require Epic N+1 to work - -**Document failures:** - -- "Epic 2 requires Epic 3 features to function" -- Stories in Epic 2 referencing Epic 3 components -- Circular dependencies between epics - -### 3. Story Quality Assessment - -#### A. Story Sizing Validation - -Check each story: - -- **Clear User Value:** Does the story deliver something meaningful? -- **Independent:** Can it be completed without future stories? - -**Common violations:** - -- "Setup all models" - not a USER story -- "Create login UI (depends on Story 1.3)" - forward dependency - -#### B. Acceptance Criteria Review - -For each story's ACs: - -- **Given/When/Then Format:** Proper BDD structure? -- **Testable:** Each AC can be verified independently? -- **Complete:** Covers all scenarios including errors? -- **Specific:** Clear expected outcomes? - -**Issues to find:** - -- Vague criteria like "user can login" -- Missing error conditions -- Incomplete happy path -- Non-measurable outcomes - -### 4. Dependency Analysis - -#### A. Within-Epic Dependencies - -Map story dependencies within each epic: - -- Story 1.1 must be completable alone -- Story 1.2 can use Story 1.1 output -- Story 1.3 can use Story 1.1 & 1.2 outputs - -**Critical violations:** - -- "This story depends on Story 1.4" -- "Wait for future story to work" -- Stories referencing features not yet implemented - -#### B. Database/Entity Creation Timing - -Validate database creation approach: - -- **Wrong:** Epic 1 Story 1 creates all tables upfront -- **Right:** Each story creates tables it needs -- **Check:** Are tables created only when first needed? - -### 5. Special Implementation Checks - -#### A. Starter Template Requirement - -Check if Architecture specifies starter template: - -- If YES: Epic 1 Story 1 must be "Set up initial project from starter template" -- Verify story includes cloning, dependencies, initial configuration - -#### B. Greenfield vs Brownfield Indicators - -Greenfield projects should have: - -- Initial project setup story -- Development environment configuration -- CI/CD pipeline setup early - -Brownfield projects should have: - -- Integration points with existing systems -- Migration or compatibility stories - -### 6. Best Practices Compliance Checklist - -For each epic, verify: - -- [ ] Epic delivers user value -- [ ] Epic can function independently -- [ ] Stories appropriately sized -- [ ] No forward dependencies -- [ ] Database tables created when needed -- [ ] Clear acceptance criteria -- [ ] Traceability to FRs maintained - -### 7. Quality Assessment Documentation - -Document all findings by severity: - -#### 🔴 Critical Violations - -- Technical epics with no user value -- Forward dependencies breaking independence -- Epic-sized stories that cannot be completed - -#### 🟠 Major Issues - -- Vague acceptance criteria -- Stories requiring future stories -- Database creation violations - -#### 🟡 Minor Concerns - -- Formatting inconsistencies -- Minor structure deviations -- Documentation gaps - -### 8. Autonomous Review Execution - -This review runs autonomously to maintain standards: - -- Apply best practices without compromise -- Document every violation with specific examples -- Provide clear remediation guidance -- Prepare recommendations for each issue - -## REVIEW COMPLETION: - -After completing epic quality review: - -- Update {outputFile} with all quality findings -- Document specific best practices violations -- Provide actionable recommendations -- Load {nextStepFile} for final readiness assessment - -## CRITICAL STEP COMPLETION NOTE - -This step executes autonomously. Load {nextStepFile} only after complete epic quality review is documented. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All epics validated against best practices -- Every dependency checked and verified -- Quality violations documented with examples -- Clear remediation guidance provided -- No compromise on standards enforcement - -### ❌ SYSTEM FAILURE: - -- Accepting technical epics as valid -- Ignoring forward dependencies -- Not verifying story sizing -- Overlooking obvious violations - -**Master Rule:** Enforce best practices rigorously. Find all violations. diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md b/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md deleted file mode 100644 index fe80fc23a..000000000 --- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -name: 'step-06-final-assessment' -description: 'Compile final assessment and polish the readiness report' - -outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md' ---- - -# Step 6: Final Assessment - -## STEP GOAL: - -To provide a comprehensive summary of all findings and give the report a final polish, ensuring clear recommendations and overall readiness status. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 📖 You are at the final step - complete the assessment -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are delivering the FINAL ASSESSMENT -- ✅ Your findings are objective and backed by evidence -- ✅ Provide clear, actionable recommendations -- ✅ Success is measured by value of findings - -### Step-Specific Rules: - -- 🎯 Compile and summarize all findings -- 🚫 Don't soften the message - be direct -- 💬 Provide specific examples for problems -- 🚪 Add final section to the report - -## EXECUTION PROTOCOLS: - -- 🎯 Review all findings from previous steps -- 💾 Add summary and recommendations -- 📖 Determine overall readiness status -- 🚫 Complete and present final report - -## FINAL ASSESSMENT PROCESS: - -### 1. Initialize Final Assessment - -"Completing **Final Assessment**. - -I will now: - -1. Review all findings from previous steps -2. Provide a comprehensive summary -3. Add specific recommendations -4. Determine overall readiness status" - -### 2. Review Previous Findings - -Check the {outputFile} for sections added by previous steps: - -- File and FR Validation findings -- UX Alignment issues -- Epic Quality violations - -### 3. Add Final Assessment Section - -Append to {outputFile}: - -```markdown -## Summary and Recommendations - -### Overall Readiness Status - -[READY/NEEDS WORK/NOT READY] - -### Critical Issues Requiring Immediate Action - -[List most critical issues that must be addressed] - -### Recommended Next Steps - -1. [Specific action item 1] -2. [Specific action item 2] -3. [Specific action item 3] - -### Final Note - -This assessment identified [X] issues across [Y] categories. Address the critical issues before proceeding to implementation. These findings can be used to improve the artifacts or you may choose to proceed as-is. -``` - -### 4. Complete the Report - -- Ensure all findings are clearly documented -- Verify recommendations are actionable -- Add date and assessor information -- Save the final report - -### 5. Present Completion - -Display: -"**Implementation Readiness Assessment Complete** - -Report generated: {outputFile} - -The assessment found [number] issues requiring attention. Review the detailed report for specific findings and recommendations." - -## WORKFLOW COMPLETE - -The implementation readiness workflow is now complete. The report contains all findings and recommendations for the user to consider. - -Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All findings compiled and summarized -- Clear recommendations provided -- Readiness status determined -- Final report saved - -### ❌ SYSTEM FAILURE: - -- Not reviewing previous findings -- Incomplete summary -- No clear recommendations diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/templates/readiness-report-template.md b/src/bmm/workflows/3-solutioning/check-implementation-readiness/templates/readiness-report-template.md deleted file mode 100644 index 972988ca2..000000000 --- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/templates/readiness-report-template.md +++ /dev/null @@ -1,4 +0,0 @@ -# Implementation Readiness Assessment Report - -**Date:** {{date}} -**Project:** {{project_name}} diff --git a/src/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md b/src/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md deleted file mode 100644 index f1ab122ec..000000000 --- a/src/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -name: check-implementation-readiness -description: 'Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".' ---- - -# Implementation Readiness - -**Goal:** Validate that PRD, Architecture, Epics and Stories are complete and aligned before Phase 4 implementation starts, with a focus on ensuring epics and stories are logical and have accounted for all requirements and planning. - -**Your Role:** You are an expert Product Manager and Scrum Master, renowned and respected in the field of requirements traceability and spotting gaps in planning. Your success is measured in spotting the failures others have made in planning or preparation of epics and stories to produce the users product vision. - -## WORKFLOW ARCHITECTURE - -### Core Principles - -- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time -- **Just-In-Time Loading**: Only 1 current step file will be loaded and followed to completion - never load future step files until told to do so -- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed -- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document -- **Append-Only Building**: Build documents by appending content as directed to the output file - -### Step Processing Rules - -1. **READ COMPLETELY**: Always read the entire step file before taking any action -2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate -3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection -4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue) -5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step -6. **LOAD NEXT**: When directed, read fully and follow the next step file - -### Critical Rules (NO EXCEPTIONS) - -- 🛑 **NEVER** load multiple step files simultaneously -- 📖 **ALWAYS** read entire step file before execution -- 🚫 **NEVER** skip steps or optimize the sequence -- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step -- 🎯 **ALWAYS** follow the exact instructions in the step file -- ⏸️ **ALWAYS** halt at menus and wait for user input -- 📋 **NEVER** create mental todo lists from future steps - ---- - -## INITIALIZATION SEQUENCE - -### 1. Module Configuration Loading - -Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve: - -- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language` -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### 2. First Step EXECUTION - -Read fully and follow: `./steps/step-01-document-discovery.md` to begin the workflow. diff --git a/src/bmm/workflows/3-solutioning/create-architecture/architecture-decision-template.md b/src/bmm/workflows/3-solutioning/create-architecture/architecture-decision-template.md deleted file mode 100644 index 51ac3d6ff..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/architecture-decision-template.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -stepsCompleted: [] -inputDocuments: [] -workflowType: 'architecture' -project_name: '{{project_name}}' -user_name: '{{user_name}}' -date: '{{date}}' ---- - -# Architecture Decision Document - -_This document builds collaboratively through step-by-step discovery. Sections are appended as we work through each architectural decision together._ diff --git a/src/bmm/workflows/3-solutioning/create-architecture/data/domain-complexity.csv b/src/bmm/workflows/3-solutioning/create-architecture/data/domain-complexity.csv deleted file mode 100644 index d619659ef..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/data/domain-complexity.csv +++ /dev/null @@ -1,13 +0,0 @@ -domain,signals,complexity_level,suggested_workflow,web_searches -e_commerce,"shopping,cart,checkout,payment,products,store",medium,standard,"ecommerce architecture patterns, payment processing, inventory management" -fintech,"banking,payment,trading,finance,money,investment",high,enhanced,"financial security, PCI compliance, trading algorithms, fraud detection" -healthcare,"medical,diagnostic,clinical,patient,hospital,health",high,enhanced,"HIPAA compliance, medical data security, FDA regulations, health tech" -social,"social network,community,users,friends,posts,sharing",high,advanced,"social graph algorithms, feed ranking, notification systems, privacy" -education,"learning,course,student,teacher,training,academic",medium,standard,"LMS architecture, progress tracking, assessment systems, video streaming" -productivity,"productivity,workflow,tasks,management,business,tools",medium,standard,"collaboration patterns, real-time editing, notification systems, integration" -media,"content,media,video,audio,streaming,broadcast",high,advanced,"CDN architecture, video encoding, streaming protocols, content delivery" -iot,"IoT,sensors,devices,embedded,smart,connected",high,advanced,"device communication, real-time data processing, edge computing, security" -government,"government,civic,public,admin,policy,regulation",high,enhanced,"accessibility standards, security clearance, data privacy, audit trails" -process_control,"industrial automation,process control,PLC,SCADA,DCS,HMI,operational technology,control system,cyberphysical,MES,instrumentation,I&C,P&ID",high,advanced,"industrial process control architecture, SCADA system design, OT cybersecurity architecture, real-time control systems" -building_automation,"building automation,BAS,BMS,HVAC,smart building,fire alarm,fire protection,fire suppression,life safety,elevator,DDC,access control,sequence of operations,commissioning",high,advanced,"building automation architecture, BACnet integration patterns, smart building design, building management system security" -gaming,"game,gaming,multiplayer,real-time,interactive,entertainment",high,advanced,"real-time multiplayer, game engine architecture, matchmaking, leaderboards" \ No newline at end of file diff --git a/src/bmm/workflows/3-solutioning/create-architecture/data/project-types.csv b/src/bmm/workflows/3-solutioning/create-architecture/data/project-types.csv deleted file mode 100644 index 3733748e9..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/data/project-types.csv +++ /dev/null @@ -1,7 +0,0 @@ -project_type,detection_signals,description,typical_starters -web_app,"website,web application,browser,frontend,UI,interface",Web-based applications running in browsers,Next.js, Vite, Remix -mobile_app,"mobile,iOS,Android,app,smartphone,tablet",Native mobile applications,React Native, Expo, Flutter -api_backend,"API,REST,GraphQL,backend,service,microservice",Backend services and APIs,NestJS, Express, Fastify -full_stack,"full-stack,complete,web+mobile,frontend+backend",Applications with both frontend and backend,T3 App, RedwoodJS, Blitz -cli_tool,"CLI,command line,terminal,console,tool",Command-line interface tools,oclif, Commander, Caporal -desktop_app,"desktop,Electron,Tauri,native app,macOS,Windows",Desktop applications,Electron, Tauri, Flutter Desktop \ No newline at end of file diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md deleted file mode 100644 index 5609ffc14..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md +++ /dev/null @@ -1,153 +0,0 @@ -# Step 1: Architecture Workflow Initialization - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between architectural peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on initialization and setup only - don't look ahead to future steps -- 🚪 DETECT existing workflow state and handle continuation properly -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 💾 Initialize document and update frontmatter -- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step -- 🚫 FORBIDDEN to load next step until setup is complete - -## CONTEXT BOUNDARIES: - -- Variables from workflow.md are available in memory -- Previous context = what's in output document + frontmatter -- Don't assume knowledge from other steps -- Input document discovery happens in this step - -## YOUR TASK: - -Initialize the Architecture workflow by detecting continuation state, discovering input documents, and setting up the document for collaborative architectural decision making. - -## INITIALIZATION SEQUENCE: - -### 1. Check for Existing Workflow - -First, check if the output document already exists: - -- Look for existing {planning_artifacts}/`*architecture*.md` -- If exists, read the complete file(s) including frontmatter -- If not exists, this is a fresh workflow - -### 2. Handle Continuation (If Document Exists) - -If the document exists and has frontmatter with `stepsCompleted`: - -- **STOP here** and load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-01b-continue.md` immediately -- Do not proceed with any initialization tasks -- Let step-01b handle the continuation logic - -### 3. Fresh Workflow Setup (If No Document) - -If no document exists or no `stepsCompleted` in frontmatter: - -#### A. Input Document Discovery - -Discover and load context documents using smart discovery. Documents can be in the following locations: -- {planning_artifacts}/** -- {output_folder}/** -- {product_knowledge}/** -- docs/** - -Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content) - -Try to discover the following: -- Product Brief (`*brief*.md`) -- Product Requirements Document (`*prd*.md`) -- UX Design (`*ux-design*.md`) and other -- Research Documents (`*research*.md`) -- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.) -- Project Context (`**/project-context.md`) - -Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules - -**Loading Rules:** - -- Load ALL discovered files completely that the user confirmed or provided (no offset/limit) -- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process -- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document -- index.md is a guide to what's relevant whenever available -- Track all successfully loaded files in frontmatter `inputDocuments` array - -#### B. Validate Required Inputs - -Before proceeding, verify we have the essential inputs: - -**PRD Validation:** - -- If no PRD found: "Architecture requires a PRD to work from. Please run the PRD workflow first or provide the PRD file path." -- Do NOT proceed without PRD - -**Other Input that might exist:** - -- UX Spec: "Provides UI/UX architectural requirements" - -#### C. Create Initial Document - -Copy the template from `{installed_path}/architecture-decision-template.md` to `{planning_artifacts}/architecture.md` - -#### D. Complete Initialization and Report - -Complete setup and report to user: - -**Document Setup:** - -- Created: `{planning_artifacts}/architecture.md` from template -- Initialized frontmatter with workflow state - -**Input Documents Discovered:** -Report what was found: -"Welcome {{user_name}}! I've set up your Architecture workspace for {{project_name}}. - -**Documents Found:** - -- PRD: {number of PRD files loaded or "None found - REQUIRED"} -- UX Design: {number of UX files loaded or "None found"} -- Research: {number of research files loaded or "None found"} -- Project docs: {number of project files loaded or "None found"} -- Project context: {project_context_rules count of rules for AI agents found} - -**Files loaded:** {list of specific file names or "No additional documents found"} - -Ready to begin architectural decision making. Do you have any other documents you'd like me to include? - -[C] Continue to project context analysis - -## SUCCESS METRICS: - -✅ Existing workflow detected and handed off to step-01b correctly -✅ Fresh workflow initialized with template and frontmatter -✅ Input documents discovered and loaded using sharded-first logic -✅ All discovered files tracked in frontmatter `inputDocuments` -✅ PRD requirement validated and communicated -✅ User confirmed document setup and can proceed - -## FAILURE MODES: - -❌ Proceeding with fresh initialization when existing workflow exists -❌ Not updating frontmatter with discovered input documents -❌ Creating document without proper template -❌ Not checking sharded folders first before whole files -❌ Not reporting what documents were found to user -❌ Proceeding without validating PRD requirement - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects [C] to continue, only after ensuring all the template output has been created, then load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md` to analyze the project context and begin architectural decision making. - -Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and setup is confirmed! diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-01b-continue.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-01b-continue.md deleted file mode 100644 index 320cfd836..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-01b-continue.md +++ /dev/null @@ -1,173 +0,0 @@ -# Step 1b: Workflow Continuation Handler - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between architectural peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on understanding current state and getting user confirmation -- 🚪 HANDLE workflow resumption smoothly and transparently -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 📖 Read existing document completely to understand current state -- 💾 Update frontmatter to reflect continuation -- 🚫 FORBIDDEN to proceed to next step without user confirmation - -## CONTEXT BOUNDARIES: - -- Existing document and frontmatter are available -- Input documents already loaded should be in frontmatter `inputDocuments` -- Steps already completed are in `stepsCompleted` array -- Focus on understanding where we left off - -## YOUR TASK: - -Handle workflow continuation by analyzing existing work and guiding the user to resume at the appropriate step. - -## CONTINUATION SEQUENCE: - -### 1. Analyze Current Document State - -Read the existing architecture document completely and analyze: - -**Frontmatter Analysis:** - -- `stepsCompleted`: What steps have been done -- `inputDocuments`: What documents were loaded -- `lastStep`: Last step that was executed -- `project_name`, `user_name`, `date`: Basic context - -**Content Analysis:** - -- What sections exist in the document -- What architectural decisions have been made -- What appears incomplete or in progress -- Any TODOs or placeholders remaining - -### 2. Present Continuation Summary - -Show the user their current progress: - -"Welcome back {{user_name}}! I found your Architecture work for {{project_name}}. - -**Current Progress:** - -- Steps completed: {{stepsCompleted list}} -- Last step worked on: Step {{lastStep}} -- Input documents loaded: {{number of inputDocuments}} files - -**Document Sections Found:** -{list all H2/H3 sections found in the document} - -{if_incomplete_sections} -**Incomplete Areas:** - -- {areas that appear incomplete or have placeholders} - {/if_incomplete_sections} - -**What would you like to do?** -[R] Resume from where we left off -[C] Continue to next logical step -[O] Overview of all remaining steps -[X] Start over (will overwrite existing work) -" - -### 3. Handle User Choice - -#### If 'R' (Resume from where we left off): - -- Identify the next step based on `stepsCompleted` -- Load the appropriate step file to continue -- Example: If `stepsCompleted: [1, 2, 3]`, load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md` - -#### If 'C' (Continue to next logical step): - -- Analyze the document content to determine logical next step -- May need to review content quality and completeness -- If content seems complete for current step, advance to next -- If content seems incomplete, suggest staying on current step - -#### If 'O' (Overview of all remaining steps): - -- Provide brief description of all remaining steps -- Let user choose which step to work on -- Don't assume sequential progression is always best - -#### If 'X' (Start over): - -- Confirm: "This will delete all existing architectural decisions. Are you sure? (y/n)" -- If confirmed: Delete existing document and read fully and follow: `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md` -- If not confirmed: Return to continuation menu - -### 4. Navigate to Selected Step - -After user makes choice: - -**Load the selected step file:** - -- Update frontmatter `lastStep` to reflect current navigation -- Execute the selected step file -- Let that step handle the detailed continuation logic - -**State Preservation:** - -- Maintain all existing content in the document -- Keep `stepsCompleted` accurate -- Track the resumption in workflow status - -### 5. Special Continuation Cases - -#### If `stepsCompleted` is empty but document has content: - -- This suggests an interrupted workflow -- Ask user: "I see the document has content but no steps are marked as complete. Should I analyze what's here and set the appropriate step status?" - -#### If document appears corrupted or incomplete: - -- Ask user: "The document seems incomplete. Would you like me to try to recover what's here, or would you prefer to start fresh?" - -#### If document is complete but workflow not marked as done: - -- Ask user: "The architecture looks complete! Should I mark this workflow as finished, or is there more you'd like to work on?" - -## SUCCESS METRICS: - -✅ Existing document state properly analyzed and understood -✅ User presented with clear continuation options -✅ User choice handled appropriately and transparently -✅ Workflow state preserved and updated correctly -✅ Navigation to appropriate step handled smoothly - -## FAILURE MODES: - -❌ Not reading the complete existing document before making suggestions -❌ Losing track of what steps were actually completed -❌ Automatically proceeding without user confirmation of next steps -❌ Not checking for incomplete or placeholder content -❌ Losing existing document content during resumption - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects their continuation option, load the appropriate step file based on their choice. The step file will handle the detailed work from that point forward. - -Valid step files to load: -- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md` -- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md` -- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md` -- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md` -- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md` -- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md` -- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md` - -Remember: The goal is smooth, transparent resumption that respects the work already done while giving the user control over how to proceed. diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md deleted file mode 100644 index d4c908711..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md +++ /dev/null @@ -1,224 +0,0 @@ -# Step 2: Project Context Analysis - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between architectural peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on understanding project scope and requirements for architecture -- 🎯 ANALYZE loaded documents, don't assume or generate requirements -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ⚠️ Present A/P/C menu after generating project context analysis -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper insights about project context and architectural implications -- **P (Party Mode)**: Bring multiple perspectives to analyze project requirements from different architectural angles -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Current document and frontmatter from step 1 are available -- Input documents already loaded are in memory (PRD, epics, UX spec, etc.) -- Focus on architectural implications of requirements -- No technology decisions yet - pure analysis phase - -## YOUR TASK: - -Fully read and Analyze the loaded project documents to understand architectural scope, requirements, and constraints before beginning decision making. - -## CONTEXT ANALYSIS SEQUENCE: - -### 1. Review Project Requirements - -**From PRD Analysis:** - -- Extract and analyze Functional Requirements (FRs) -- Identify Non-Functional Requirements (NFRs) like performance, security, compliance -- Note any technical constraints or dependencies mentioned -- Count and categorize requirements to understand project scale - -**From Epics/Stories (if available):** - -- Map epic structure and user stories to architectural components -- Extract acceptance criteria for technical implications -- Identify cross-cutting concerns that span multiple epics -- Estimate story complexity for architectural planning - -**From UX Design (if available):** - -- Extract architectural implications from UX requirements: - - Component complexity (simple forms vs rich interactions) - - Animation/transition requirements - - Real-time update needs (live data, collaborative features) - - Platform-specific UI requirements - - Accessibility standards (WCAG compliance level) - - Responsive design breakpoints - - Offline capability requirements - - Performance expectations (load times, interaction responsiveness) - -### 2. Project Scale Assessment - -Calculate and present project complexity: - -**Complexity Indicators:** - -- Real-time features requirements -- Multi-tenancy needs -- Regulatory compliance requirements -- Integration complexity -- User interaction complexity -- Data complexity and volume - -### 3. Reflect Understanding - -Present your analysis back to user for validation: - -"I'm reviewing your project documentation for {{project_name}}. - -{if_epics_loaded}I see {{epic_count}} epics with {{story_count}} total stories.{/if_epics_loaded} -{if_no_epics}I found {{fr_count}} functional requirements organized into {{fr_category_list}}.{/if_no_epics} -{if_ux_loaded}I also found your UX specification which defines the user experience requirements.{/if_ux_loaded} - -**Key architectural aspects I notice:** - -- [Summarize core functionality from FRs] -- [Note critical NFRs that will shape architecture] -- {if_ux_loaded}[Note UX complexity and technical requirements]{/if_ux_loaded} -- [Identify unique technical challenges or constraints] -- [Highlight any regulatory or compliance requirements] - -**Scale indicators:** - -- Project complexity appears to be: [low/medium/high/enterprise] -- Primary technical domain: [web/mobile/api/backend/full-stack/etc] -- Cross-cutting concerns identified: [list major ones] - -This analysis will help me guide you through the architectural decisions needed to ensure AI agents implement this consistently. - -Does this match your understanding of the project scope and requirements?" - -### 4. Generate Project Context Content - -Prepare the content to append to the document: - -#### Content Structure: - -```markdown -## Project Context Analysis - -### Requirements Overview - -**Functional Requirements:** -{{analysis of FRs and what they mean architecturally}} - -**Non-Functional Requirements:** -{{NFRs that will drive architectural decisions}} - -**Scale & Complexity:** -{{project_scale_assessment}} - -- Primary domain: {{technical_domain}} -- Complexity level: {{complexity_level}} -- Estimated architectural components: {{component_count}} - -### Technical Constraints & Dependencies - -{{known_constraints_dependencies}} - -### Cross-Cutting Concerns Identified - -{{concerns_that_will_affect_multiple_components}} -``` - -### 5. Present Content and Menu - -Show the generated content and present choices: - -"I've drafted the Project Context Analysis based on your requirements. This sets the foundation for our architectural decisions. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 4] - -**What would you like to do?** -[A] Advanced Elicitation - Let's dive deeper into architectural implications -[P] Party Mode - Bring different perspectives to analyze requirements -[C] Continue - Save this analysis and begin architectural decisions" - -### 6. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current context analysis -- Process the enhanced architectural insights that come back -- Ask user: "Accept these enhancements to the project context analysis? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current project context -- Process the collaborative improvements to architectural understanding -- Ask user: "Accept these changes to the project context analysis? (y/n)" -- If yes: Update content with improvements, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/architecture.md` -- Update frontmatter: `stepsCompleted: [1, 2]` -- Load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 4. - -## SUCCESS METRICS: - -✅ All input documents thoroughly analyzed for architectural implications -✅ Project scope and complexity clearly assessed and validated -✅ Technical constraints and dependencies identified -✅ Cross-cutting concerns mapped for architectural planning -✅ User confirmation of project understanding -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Skimming documents without deep architectural analysis -❌ Missing or misinterpreting critical NFRs -❌ Not validating project understanding with user -❌ Underestimating complexity indicators -❌ Generating content without real analysis of loaded documents -❌ Not presenting A/P/C menu after content generation - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md` to evaluate starter template options. - -Remember: Do NOT proceed to step-03 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md deleted file mode 100644 index 45dc74c55..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md +++ /dev/null @@ -1,329 +0,0 @@ -# Step 3: Starter Template Evaluation - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input -- ✅ ALWAYS treat this as collaborative discovery between architectural peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on evaluating starter template options with current versions -- 🌐 ALWAYS search the web to verify current versions - NEVER trust hardcoded versions -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete architecture -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 🌐 Search the web to verify current versions and options -- ⚠️ Present A/P/C menu after generating starter template analysis -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to explore unconventional starter options or custom approaches -- **P (Party Mode)**: Bring multiple perspectives to evaluate starter trade-offs for different use cases -- **C (Continue)**: Save the content to the document and proceed to next step - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Project context from step 2 is available and complete -- Project context file from step-01 may contain technical preferences -- No architectural decisions made yet - evaluating foundations -- Focus on technical preferences discovery and starter evaluation -- Consider project requirements and existing preferences when evaluating options - -## YOUR TASK: - -Discover technical preferences and evaluate starter template options, leveraging existing technical preferences and establishing solid architectural foundations. - -## STARTER EVALUATION SEQUENCE: - -### 0. Check Technical Preferences & Context - -**Check Project Context for Existing Technical Preferences:** -"Before we dive into starter templates, let me check if you have any technical preferences already documented. - -{{if_project_context_exists}} -I found some technical rules in your project context file: -{{extracted_technical_preferences_from_project_context}} - -**Project Context Technical Rules Found:** - -- Languages/Frameworks: {{languages_frameworks_from_context}} -- Tools & Libraries: {{tools_from_context}} -- Development Patterns: {{patterns_from_context}} -- Platform Preferences: {{platforms_from_context}} - -{{else}} -No existing technical preferences found in project context file. We'll establish your technical preferences now. -{{/if_project_context}}" - -**Discover User Technical Preferences:** -"Based on your project context, let's discuss your technical preferences: - -{{primary_technology_category}} Preferences: - -- **Languages**: Do you have preferences between TypeScript/JavaScript, Python, Go, Rust, etc.? -- **Frameworks**: Any existing familiarity or preferences (React, Vue, Angular, Next.js, etc.)? -- **Databases**: Any preferences or existing infrastructure (PostgreSQL, MongoDB, MySQL, etc.)? - -**Development Experience:** - -- What's your team's experience level with different technologies? -- Are there any technologies you want to learn vs. what you're comfortable with? - -**Platform/Deployment Preferences:** - -- Cloud provider preferences (AWS, Vercel, Railway, etc.)? -- Container preferences (Docker, Serverless, Traditional)? - -**Integrations:** - -- Any existing systems or APIs you need to integrate with? -- Third-party services you plan to use (payment, authentication, analytics, etc.)? - -These preferences will help me recommend the most suitable starter templates and guide our architectural decisions." - -### 1. Identify Primary Technology Domain - -Based on project context analysis and technical preferences, identify the primary technology stack: - -- **Web application** → Look for Next.js, Vite, Remix, SvelteKit starters -- **Mobile app** → Look for React Native, Expo, Flutter starters -- **API/Backend** → Look for NestJS, Express, Fastify, Supabase starters -- **CLI tool** → Look for CLI framework starters (oclif, commander, etc.) -- **Full-stack** → Look for T3, RedwoodJS, Blitz, Next.js starters -- **Desktop** → Look for Electron, Tauri starters - -### 2. UX Requirements Consideration - -If UX specification was loaded, consider UX requirements when selecting starter: - -- **Rich animations** → Framer Motion compatible starter -- **Complex forms** → React Hook Form included starter -- **Real-time features** → Socket.io or WebSocket ready starter -- **Design system** → Storybook-enabled starter -- **Offline capability** → Service worker or PWA configured starter - -### 3. Research Current Starter Options - -Search the web to find current, maintained starter templates: - -``` -Search the web: "{{primary_technology}} starter template CLI create command latest" -Search the web: "{{primary_technology}} boilerplate generator latest options" -Search the web: "{{primary_technology}} production-ready starter best practices" -``` - -### 4. Investigate Top Starter Options - -For each promising starter found, investigate details: - -``` -Search the web: "{{starter_name}} default setup technologies included latest" -Search the web: "{{starter_name}} project structure file organization" -Search the web: "{{starter_name}} production deployment capabilities" -Search the web: "{{starter_name}} recent updates maintenance status" -``` - -### 5. Analyze What Each Starter Provides - -For each viable starter option, document: - -**Technology Decisions Made:** - -- Language/TypeScript configuration -- Styling solution (CSS, Tailwind, Styled Components, etc.) -- Testing framework setup -- Linting/Formatting configuration -- Build tooling and optimization -- Project structure and organization - -**Architectural Patterns Established:** - -- Code organization patterns -- Component structure conventions -- API layering approach -- State management setup -- Routing patterns -- Environment configuration - -**Development Experience Features:** - -- Hot reloading and development server -- TypeScript configuration -- Debugging setup -- Testing infrastructure -- Documentation generation - -### 6. Present Starter Options - -Based on user skill level and project needs: - -**For Expert Users:** -"Found {{starter_name}} which provides: -{{quick_decision_list_of_key_decisions}} - -This would establish our base architecture with these technical decisions already made. Use it?" - -**For Intermediate Users:** -"I found {{starter_name}}, which is a well-maintained starter for {{project_type}} projects. - -It makes these architectural decisions for us: -{{decision_list_with_explanations}} - -This gives us a solid foundation following current best practices. Should we use it?" - -**For Beginner Users:** -"I found {{starter_name}}, which is like a pre-built foundation for your project. - -Think of it like buying a prefab house frame instead of cutting each board yourself. - -It makes these decisions for us: -{{friendly_explanation_of_decisions}} - -This is a great starting point that follows best practices and saves us from making dozens of small technical choices. Should we use it?" - -### 7. Get Current CLI Commands - -If user shows interest in a starter, get the exact current commands: - -``` -Search the web: "{{starter_name}} CLI command options flags latest" -Search the web: "{{starter_name}} create new project command examples" -``` - -### 8. Generate Starter Template Content - -Prepare the content to append to the document: - -#### Content Structure: - -````markdown -## Starter Template Evaluation - -### Primary Technology Domain - -{{identified_domain}} based on project requirements analysis - -### Starter Options Considered - -{{analysis_of_evaluated_starters}} - -### Selected Starter: {{starter_name}} - -**Rationale for Selection:** -{{why_this_starter_was_chosen}} - -**Initialization Command:** - -```bash -{{full_starter_command_with_options}} -``` - -**Architectural Decisions Provided by Starter:** - -**Language & Runtime:** -{{language_typescript_setup}} - -**Styling Solution:** -{{styling_solution_configuration}} - -**Build Tooling:** -{{build_tools_and_optimization}} - -**Testing Framework:** -{{testing_setup_and_configuration}} - -**Code Organization:** -{{project_structure_and_patterns}} - -**Development Experience:** -{{development_tools_and_workflow}} - -**Note:** Project initialization using this command should be the first implementation story. - -```` - -### 9. Present Content and Menu - -Show the generated content and present choices: - -"I've analyzed starter template options for {{project_type}} projects. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 8] - -**What would you like to do?** -[A] Advanced Elicitation - Explore custom approaches or unconventional starters -[P] Party Mode - Evaluate trade-offs from different perspectives -[C] Continue - Save this decision and move to architectural decisions" - -### 10. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current starter analysis -- Process enhanced insights about starter options or custom approaches -- Ask user: "Accept these changes to the starter template evaluation? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with starter evaluation context -- Process collaborative insights about starter trade-offs -- Ask user: "Accept these changes to the starter template evaluation? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/architecture.md` -- Update frontmatter: `stepsCompleted: [1, 2, 3]` -- Load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 8. - -## SUCCESS METRICS: - -✅ Primary technology domain correctly identified from project context -✅ Current, maintained starter templates researched and evaluated -✅ All versions verified using web search, not hardcoded -✅ Architectural implications of starter choice clearly documented -✅ User provided with clear rationale for starter selection -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Not verifying current versions with web search -❌ Ignoring UX requirements when evaluating starters -❌ Not documenting what architectural decisions the starter makes -❌ Failing to consider maintenance status of starter templates -❌ Not providing clear rationale for starter selection -❌ Not presenting A/P/C menu after content generation -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md` to begin making specific architectural decisions. - -Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md deleted file mode 100644 index 2fe2d3469..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md +++ /dev/null @@ -1,318 +0,0 @@ -# Step 4: Core Architectural Decisions - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between architectural peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on making critical architectural decisions collaboratively -- 🌐 ALWAYS search the web to verify current technology versions -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 🌐 Search the web to verify technology versions and options -- ⚠️ Present A/P/C menu after each major decision category -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices for each decision category: - -- **A (Advanced Elicitation)**: Use discovery protocols to explore innovative approaches to specific decisions -- **P (Party Mode)**: Bring multiple perspectives to evaluate decision trade-offs -- **C (Continue)**: Save the current decisions and proceed to next decision category - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Project context from step 2 is available -- Starter template choice from step 3 is available -- Project context file may contain technical preferences and rules -- Technical preferences discovered in step 3 are available -- Focus on decisions not already made by starter template or existing preferences -- Collaborative decision making, not recommendations - -## YOUR TASK: - -Facilitate collaborative architectural decision making, leveraging existing technical preferences and starter template decisions, focusing on remaining choices critical to the project's success. - -## DECISION MAKING SEQUENCE: - -### 1. Load Decision Framework & Check Existing Preferences - -**Review Technical Preferences from Step 3:** -"Based on our technical preferences discussion in step 3, let's build on those foundations: - -**Your Technical Preferences:** -{{user_technical_preferences_from_step_3}} - -**Starter Template Decisions:** -{{starter_template_decisions}} - -**Project Context Technical Rules:** -{{project_context_technical_rules}}" - -**Identify Remaining Decisions:** -Based on technical preferences, starter template choice, and project context, identify remaining critical decisions: - -**Already Decided (Don't re-decide these):** - -- {{starter_template_decisions}} -- {{user_technology_preferences}} -- {{project_context_technical_rules}} - -**Critical Decisions:** Must be decided before implementation can proceed -**Important Decisions:** Shape the architecture significantly -**Nice-to-Have:** Can be deferred if needed - -### 2. Decision Categories by Priority - -#### Category 1: Data Architecture - -- Database choice (if not determined by starter) -- Data modeling approach -- Data validation strategy -- Migration approach -- Caching strategy - -#### Category 2: Authentication & Security - -- Authentication method -- Authorization patterns -- Security middleware -- Data encryption approach -- API security strategy - -#### Category 3: API & Communication - -- API design patterns (REST, GraphQL, etc.) -- API documentation approach -- Error handling standards -- Rate limiting strategy -- Communication between services - -#### Category 4: Frontend Architecture (if applicable) - -- State management approach -- Component architecture -- Routing strategy -- Performance optimization -- Bundle optimization - -#### Category 5: Infrastructure & Deployment - -- Hosting strategy -- CI/CD pipeline approach -- Environment configuration -- Monitoring and logging -- Scaling strategy - -### 3. Facilitate Each Decision Category - -For each category, facilitate collaborative decision making: - -**Present the Decision:** -Based on user skill level and project context: - -**Expert Mode:** -"{{Decision_Category}}: {{Specific_Decision}} - -Options: {{concise_option_list_with_tradeoffs}} - -What's your preference for this decision?" - -**Intermediate Mode:** -"Next decision: {{Human_Friendly_Category}} - -We need to choose {{Specific_Decision}}. - -Common options: -{{option_list_with_brief_explanations}} - -For your project, I'd lean toward {{recommendation}} because {{reason}}. What are your thoughts?" - -**Beginner Mode:** -"Let's talk about {{Human_Friendly_Category}}. - -{{Educational_Context_About_Why_This_Matters}} - -Think of it like {{real_world_analogy}}. - -Your main options: -{{friendly_options_with_pros_cons}} - -My suggestion: {{recommendation}} -This is good for you because {{beginner_friendly_reason}}. - -What feels right to you?" - -**Verify Technology Versions:** -If decision involves specific technology: - -``` -Search the web: "{{technology}} latest stable version" -Search the web: "{{technology}} current LTS version" -Search the web: "{{technology}} production readiness" -``` - -**Get User Input:** -"What's your preference? (or 'explain more' for details)" - -**Handle User Response:** - -- If user wants more info: Provide deeper explanation -- If user has preference: Discuss implications and record decision -- If user wants alternatives: Explore other options - -**Record the Decision:** - -- Category: {{category}} -- Decision: {{user_choice}} -- Version: {{verified_version_if_applicable}} -- Rationale: {{user_reasoning_or_default}} -- Affects: {{components_or_epics}} -- Provided by Starter: {{yes_if_from_starter}} - -### 4. Check for Cascading Implications - -After each major decision, identify related decisions: - -"This choice means we'll also need to decide: - -- {{related_decision_1}} -- {{related_decision_2}}" - -### 5. Generate Decisions Content - -After facilitating all decision categories, prepare the content to append: - -#### Content Structure: - -```markdown -## Core Architectural Decisions - -### Decision Priority Analysis - -**Critical Decisions (Block Implementation):** -{{critical_decisions_made}} - -**Important Decisions (Shape Architecture):** -{{important_decisions_made}} - -**Deferred Decisions (Post-MVP):** -{{decisions_deferred_with_rationale}} - -### Data Architecture - -{{data_related_decisions_with_versions_and_rationale}} - -### Authentication & Security - -{{security_related_decisions_with_versions_and_rationale}} - -### API & Communication Patterns - -{{api_related_decisions_with_versions_and_rationale}} - -### Frontend Architecture - -{{frontend_related_decisions_with_versions_and_rationale}} - -### Infrastructure & Deployment - -{{infrastructure_related_decisions_with_versions_and_rationale}} - -### Decision Impact Analysis - -**Implementation Sequence:** -{{ordered_list_of_decisions_for_implementation}} - -**Cross-Component Dependencies:** -{{how_decisions_affect_each_other}} -``` - -### 6. Present Content and Menu - -Show the generated decisions content and present choices: - -"I've documented all the core architectural decisions we've made together. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 5] - -**What would you like to do?** -[A] Advanced Elicitation - Explore innovative approaches to any specific decisions -[P] Party Mode - Review decisions from multiple perspectives -[C] Continue - Save these decisions and move to implementation patterns" - -### 7. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with specific decision categories -- Process enhanced insights about particular decisions -- Ask user: "Accept these enhancements to the architectural decisions? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with architectural decisions context -- Process collaborative insights about decision trade-offs -- Ask user: "Accept these changes to the architectural decisions? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/architecture.md` -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]` -- Load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 5. - -## SUCCESS METRICS: - -✅ All critical architectural decisions made collaboratively -✅ Technology versions verified using web search -✅ Decision rationale clearly documented -✅ Cascading implications identified and addressed -✅ User provided appropriate level of explanation for skill level -✅ A/P/C menu presented and handled correctly for each category -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Making recommendations instead of facilitating decisions -❌ Not verifying technology versions with web search -❌ Missing cascading implications between decisions -❌ Not adapting explanations to user skill level -❌ Forgetting to document decisions made by starter template -❌ Not presenting A/P/C menu after content generation - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md` to define implementation patterns that ensure consistency across AI agents. - -Remember: Do NOT proceed to step-05 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md deleted file mode 100644 index cb0641afb..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md +++ /dev/null @@ -1,359 +0,0 @@ -# Step 5: Implementation Patterns & Consistency Rules - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between architectural peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on patterns that prevent AI agent implementation conflicts -- 🎯 EMPHASIZE what agents could decide DIFFERENTLY if not specified -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 🎯 Focus on consistency, not implementation details -- ⚠️ Present A/P/C menu after generating patterns content -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to develop comprehensive consistency patterns -- **P (Party Mode)**: Bring multiple perspectives to identify potential conflict points -- **C (Continue)**: Save the patterns and proceed to project structure - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Core architectural decisions from step 4 are complete -- Technology stack is decided and versions are verified -- Focus on HOW agents should implement, not WHAT they should implement -- Consider what could vary between different AI agents - -## YOUR TASK: - -Define implementation patterns and consistency rules that ensure multiple AI agents write compatible, consistent code that works together seamlessly. - -## PATTERNS DEFINITION SEQUENCE: - -### 1. Identify Potential Conflict Points - -Based on the chosen technology stack and decisions, identify where AI agents could make different choices: - -**Naming Conflicts:** - -- Database table/column naming conventions -- API endpoint naming patterns -- File and directory naming -- Component/function/variable naming -- Route parameter formats - -**Structural Conflicts:** - -- Where tests are located -- How components are organized -- Where utilities and helpers go -- Configuration file organization -- Static asset organization - -**Format Conflicts:** - -- API response wrapper formats -- Error response structures -- Date/time formats in APIs and UI -- JSON field naming conventions -- API status code usage - -**Communication Conflicts:** - -- Event naming conventions -- Event payload structures -- State update patterns -- Action naming conventions -- Logging formats and levels - -**Process Conflicts:** - -- Loading state handling -- Error recovery patterns -- Retry implementation approaches -- Authentication flow patterns -- Validation timing and methods - -### 2. Facilitate Pattern Decisions - -For each conflict category, facilitate collaborative pattern definition: - -**Present the Conflict Point:** -"Given that we're using {{tech_stack}}, different AI agents might handle {{conflict_area}} differently. - -For example, one agent might name database tables 'users' while another uses 'Users' - this would cause conflicts. - -We need to establish consistent patterns that all agents follow." - -**Show Options and Trade-offs:** -"Common approaches for {{pattern_category}}: - -1. {{option_1}} - {{pros_and_cons}} -2. {{option_2}} - {{pros_and_cons}} -3. {{option_3}} - {{pros_and_cons}} - -Which approach makes the most sense for our project?" - -**Get User Decision:** -"What's your preference for this pattern? (or discuss the trade-offs more)" - -### 3. Define Pattern Categories - -#### Naming Patterns - -**Database Naming:** - -- Table naming: users, Users, or user? -- Column naming: user_id or userId? -- Foreign key format: user_id or fk_user? -- Index naming: idx_users_email or users_email_index? - -**API Naming:** - -- REST endpoint naming: /users or /user? Plural or singular? -- Route parameter format: :id or {id}? -- Query parameter naming: user_id or userId? -- Header naming conventions: X-Custom-Header or Custom-Header? - -**Code Naming:** - -- Component naming: UserCard or user-card? -- File naming: UserCard.tsx or user-card.tsx? -- Function naming: getUserData or get_user_data? -- Variable naming: userId or user_id? - -#### Structure Patterns - -**Project Organization:** - -- Where do tests live? **tests**/ or \*.test.ts co-located? -- How are components organized? By feature or by type? -- Where do shared utilities go? -- How are services and repositories organized? - -**File Structure:** - -- Config file locations and naming -- Static asset organization -- Documentation placement -- Environment file organization - -#### Format Patterns - -**API Formats:** - -- API response wrapper? {data: ..., error: ...} or direct response? -- Error format? {message, code} or {error: {type, detail}}? -- Date format in JSON? ISO strings or timestamps? -- Success response structure? - -**Data Formats:** - -- JSON field naming: snake_case or camelCase? -- Boolean representations: true/false or 1/0? -- Null handling patterns -- Array vs object for single items - -#### Communication Patterns - -**Event Systems:** - -- Event naming convention: user.created or UserCreated? -- Event payload structure standards -- Event versioning approach -- Async event handling patterns - -**State Management:** - -- State update patterns: immutable updates or direct mutation? -- Action naming conventions -- Selector patterns -- State organization principles - -#### Process Patterns - -**Error Handling:** - -- Global error handling approach -- Error boundary patterns -- User-facing error message format -- Logging vs user error distinction - -**Loading States:** - -- Loading state naming conventions -- Global vs local loading states -- Loading state persistence -- Loading UI patterns - -### 4. Generate Patterns Content - -Prepare the content to append to the document: - -#### Content Structure: - -```markdown -## Implementation Patterns & Consistency Rules - -### Pattern Categories Defined - -**Critical Conflict Points Identified:** -{{number_of_potential_conflicts}} areas where AI agents could make different choices - -### Naming Patterns - -**Database Naming Conventions:** -{{database_naming_rules_with_examples}} - -**API Naming Conventions:** -{{api_naming_rules_with_examples}} - -**Code Naming Conventions:** -{{code_naming_rules_with_examples}} - -### Structure Patterns - -**Project Organization:** -{{project_structure_rules_with_examples}} - -**File Structure Patterns:** -{{file_organization_rules_with_examples}} - -### Format Patterns - -**API Response Formats:** -{{api_response_structure_rules}} - -**Data Exchange Formats:** -{{data_format_rules_with_examples}} - -### Communication Patterns - -**Event System Patterns:** -{{event_naming_and_structure_rules}} - -**State Management Patterns:** -{{state_update_and_organization_rules}} - -### Process Patterns - -**Error Handling Patterns:** -{{consistent_error_handling_approaches}} - -**Loading State Patterns:** -{{loading_state_management_rules}} - -### Enforcement Guidelines - -**All AI Agents MUST:** - -- {{mandatory_pattern_1}} -- {{mandatory_pattern_2}} -- {{mandatory_pattern_3}} - -**Pattern Enforcement:** - -- How to verify patterns are followed -- Where to document pattern violations -- Process for updating patterns - -### Pattern Examples - -**Good Examples:** -{{concrete_examples_of_correct_pattern_usage}} - -**Anti-Patterns:** -{{examples_of_what_to_avoid}} -``` - -### 5. Present Content and Menu - -Show the generated patterns content and present choices: - -"I've documented implementation patterns that will prevent conflicts between AI agents working on this project. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 4] - -**What would you like to do?** -[A] Advanced Elicitation - Explore additional consistency patterns -[P] Party Mode - Review patterns from different implementation perspectives -[C] Continue - Save these patterns and move to project structure" - -### 6. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current patterns -- Process enhanced consistency rules that come back -- Ask user: "Accept these additional pattern refinements? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with implementation patterns context -- Process collaborative insights about potential conflicts -- Ask user: "Accept these changes to the implementation patterns? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/architecture.md` -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]` -- Load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 4. - -## SUCCESS METRICS: - -✅ All potential AI agent conflict points identified and addressed -✅ Comprehensive patterns defined for naming, structure, and communication -✅ Concrete examples provided for each pattern -✅ Enforcement guidelines clearly documented -✅ User collaborated on pattern decisions rather than receiving recommendations -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Missing potential conflict points that could cause agent conflicts -❌ Being too prescriptive about implementation details instead of focusing on consistency -❌ Not providing concrete examples for each pattern -❌ Failing to address cross-cutting concerns like error handling -❌ Not considering the chosen technology stack when defining patterns -❌ Not presenting A/P/C menu after content generation - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md` to define the complete project structure. - -Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md deleted file mode 100644 index 7a2019a9f..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md +++ /dev/null @@ -1,379 +0,0 @@ -# Step 6: Project Structure & Boundaries - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between architectural peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on defining complete project structure and clear boundaries -- 🗺️ MAP requirements/epics to architectural components -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 🗺️ Create complete project tree, not generic placeholders -- ⚠️ Present A/P/C menu after generating project structure -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to explore innovative project organization approaches -- **P (Party Mode)**: Bring multiple perspectives to evaluate project structure trade-offs -- **C (Continue)**: Save the project structure and proceed to validation - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- All previous architectural decisions are complete -- Implementation patterns and consistency rules are defined -- Focus on physical project structure and component boundaries -- Map requirements to specific files and directories - -## YOUR TASK: - -Define the complete project structure and architectural boundaries based on all decisions made, creating a concrete implementation guide for AI agents. - -## PROJECT STRUCTURE SEQUENCE: - -### 1. Analyze Requirements Mapping - -Map project requirements to architectural components: - -**From Epics (if available):** -"Epic: {{epic_name}} → Lives in {{module/directory/service}}" - -- User stories within the epic -- Cross-epic dependencies -- Shared components needed - -**From FR Categories (if no epics):** -"FR Category: {{fr_category_name}} → Lives in {{module/directory/service}}" - -- Related functional requirements -- Shared functionality across categories -- Integration points between categories - -### 2. Define Project Directory Structure - -Based on technology stack and patterns, create the complete project structure: - -**Root Configuration Files:** - -- Package management files (package.json, requirements.txt, etc.) -- Build and development configuration -- Environment configuration files -- CI/CD pipeline files -- Documentation files - -**Source Code Organization:** - -- Application entry points -- Core application structure -- Feature/module organization -- Shared utilities and libraries -- Configuration and environment files - -**Test Organization:** - -- Unit test locations and structure -- Integration test organization -- End-to-end test structure -- Test utilities and fixtures - -**Build and Distribution:** - -- Build output directories -- Distribution files -- Static assets -- Documentation build - -### 3. Define Integration Boundaries - -Map how components communicate and where boundaries exist: - -**API Boundaries:** - -- External API endpoints -- Internal service boundaries -- Authentication and authorization boundaries -- Data access layer boundaries - -**Component Boundaries:** - -- Frontend component communication patterns -- State management boundaries -- Service communication patterns -- Event-driven integration points - -**Data Boundaries:** - -- Database schema boundaries -- Data access patterns -- Caching boundaries -- External data integration points - -### 4. Create Complete Project Tree - -Generate a comprehensive directory structure showing all files and directories: - -**Technology-Specific Structure Examples:** - -**Next.js Full-Stack:** - -``` -project-name/ -├── README.md -├── package.json -├── next.config.js -├── tailwind.config.js -├── tsconfig.json -├── .env.local -├── .env.example -├── .gitignore -├── .github/ -│ └── workflows/ -│ └── ci.yml -├── src/ -│ ├── app/ -│ │ ├── globals.css -│ │ ├── layout.tsx -│ │ └── page.tsx -│ ├── components/ -│ │ ├── ui/ -│ │ ├── forms/ -│ │ └── features/ -│ ├── lib/ -│ │ ├── db.ts -│ │ ├── auth.ts -│ │ └── utils.ts -│ ├── types/ -│ └── middleware.ts -├── prisma/ -│ ├── schema.prisma -│ └── migrations/ -├── tests/ -│ ├── __mocks__/ -│ ├── components/ -│ └── e2e/ -└── public/ - └── assets/ -``` - -**API Backend (NestJS):** - -``` -project-name/ -├── package.json -├── nest-cli.json -├── tsconfig.json -├── .env -├── .env.example -├── .gitignore -├── README.md -├── src/ -│ ├── main.ts -│ ├── app.module.ts -│ ├── config/ -│ ├── modules/ -│ │ ├── auth/ -│ │ ├── users/ -│ │ └── common/ -│ ├── services/ -│ ├── repositories/ -│ ├── decorators/ -│ ├── pipes/ -│ ├── guards/ -│ └── interceptors/ -├── test/ -│ ├── unit/ -│ ├── integration/ -│ └── e2e/ -├── prisma/ -│ ├── schema.prisma -│ └── migrations/ -└── docker-compose.yml -``` - -### 5. Map Requirements to Structure - -Create explicit mapping from project requirements to specific files/directories: - -**Epic/Feature Mapping:** -"Epic: User Management - -- Components: src/components/features/users/ -- Services: src/services/users/ -- API Routes: src/app/api/users/ -- Database: prisma/migrations/_*users*_ -- Tests: tests/features/users/" - -**Cross-Cutting Concerns:** -"Authentication System - -- Components: src/components/auth/ -- Services: src/services/auth/ -- Middleware: src/middleware/auth.ts -- Guards: src/guards/auth.guard.ts -- Tests: tests/auth/" - -### 6. Generate Structure Content - -Prepare the content to append to the document: - -#### Content Structure: - -```markdown -## Project Structure & Boundaries - -### Complete Project Directory Structure -``` - -{{complete_project_tree_with_all_files_and_directories}} - -``` - -### Architectural Boundaries - -**API Boundaries:** -{{api_boundary_definitions_and_endpoints}} - -**Component Boundaries:** -{{component_communication_patterns_and_boundaries}} - -**Service Boundaries:** -{{service_integration_patterns_and_boundaries}} - -**Data Boundaries:** -{{data_access_patterns_and_boundaries}} - -### Requirements to Structure Mapping - -**Feature/Epic Mapping:** -{{mapping_of_epics_or_features_to_specific_directories}} - -**Cross-Cutting Concerns:** -{{mapping_of_shared_functionality_to_locations}} - -### Integration Points - -**Internal Communication:** -{{how_components_within_the_project_communicate}} - -**External Integrations:** -{{third_party_service_integration_points}} - -**Data Flow:** -{{how_data_flows_through_the_architecture}} - -### File Organization Patterns - -**Configuration Files:** -{{where_and_how_config_files_are_organized}} - -**Source Organization:** -{{how_source_code_is_structured_and_organized}} - -**Test Organization:** -{{how_tests_are_structured_and_organized}} - -**Asset Organization:** -{{how_static_and_dynamic_assets_are_organized}} - -### Development Workflow Integration - -**Development Server Structure:** -{{how_the_project_is organized_for_development}} - -**Build Process Structure:** -{{how_the_build_process_uses_the_project_structure}} - -**Deployment Structure:** -{{how_the_project_structure_supports_deployment}} -``` - -### 7. Present Content and Menu - -Show the generated project structure content and present choices: - -"I've created a complete project structure based on all our architectural decisions. - -**Here's what I'll add to the document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Explore innovative project organization approaches -[P] Party Mode - Review structure from different development perspectives -[C] Continue - Save this structure and move to architecture validation" - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current project structure -- Process enhanced organizational insights that come back -- Ask user: "Accept these changes to the project structure? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with project structure context -- Process collaborative insights about organization trade-offs -- Ask user: "Accept these changes to the project structure? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/architecture.md` -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]` -- Load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ Complete project tree defined with all files and directories -✅ All architectural boundaries clearly documented -✅ Requirements/epics mapped to specific locations -✅ Integration points and communication patterns defined -✅ Project structure aligned with chosen technology stack -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Creating generic placeholder structure instead of specific, complete tree -❌ Not mapping requirements to specific files and directories -❌ Missing important integration boundaries -❌ Not considering the chosen technology stack in structure design -❌ Not defining how components communicate across boundaries -❌ Not presenting A/P/C menu after content generation - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md` to validate architectural coherence and completeness. - -Remember: Do NOT proceed to step-07 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md deleted file mode 100644 index 580a957fe..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md +++ /dev/null @@ -1,359 +0,0 @@ -# Step 7: Architecture Validation & Completion - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding -- ✅ ALWAYS treat this as collaborative discovery between architectural peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on validating architectural coherence and completeness -- ✅ VALIDATE all requirements are covered by architectural decisions -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- ✅ Run comprehensive validation checks on the complete architecture -- ⚠️ Present A/P/C menu after generating validation results -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]` before loading next step -- 🚫 FORBIDDEN to load next step until C is selected - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices: - -- **A (Advanced Elicitation)**: Use discovery protocols to address complex architectural issues found during validation -- **P (Party Mode)**: Bring multiple perspectives to resolve validation concerns -- **C (Continue)**: Save the validation results and complete the architecture - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md -- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Complete architecture document with all sections is available -- All architectural decisions, patterns, and structure are defined -- Focus on validation, gap analysis, and coherence checking -- Prepare for handoff to implementation phase - -## YOUR TASK: - -Validate the complete architecture for coherence, completeness, and readiness to guide AI agents through consistent implementation. - -## VALIDATION SEQUENCE: - -### 1. Coherence Validation - -Check that all architectural decisions work together: - -**Decision Compatibility:** - -- Do all technology choices work together without conflicts? -- Are all versions compatible with each other? -- Do patterns align with technology choices? -- Are there any contradictory decisions? - -**Pattern Consistency:** - -- Do implementation patterns support the architectural decisions? -- Are naming conventions consistent across all areas? -- Do structure patterns align with technology stack? -- Are communication patterns coherent? - -**Structure Alignment:** - -- Does the project structure support all architectural decisions? -- Are boundaries properly defined and respected? -- Does the structure enable the chosen patterns? -- Are integration points properly structured? - -### 2. Requirements Coverage Validation - -Verify all project requirements are architecturally supported: - -**From Epics (if available):** - -- Does every epic have architectural support? -- Are all user stories implementable with these decisions? -- Are cross-epic dependencies handled architecturally? -- Are there any gaps in epic coverage? - -**From FR Categories (if no epics):** - -- Does every functional requirement have architectural support? -- Are all FR categories fully covered by architectural decisions? -- Are cross-cutting FRs properly addressed? -- Are there any missing architectural capabilities? - -**Non-Functional Requirements:** - -- Are performance requirements addressed architecturally? -- Are security requirements fully covered? -- Are scalability considerations properly handled? -- Are compliance requirements architecturally supported? - -### 3. Implementation Readiness Validation - -Assess if AI agents can implement consistently: - -**Decision Completeness:** - -- Are all critical decisions documented with versions? -- Are implementation patterns comprehensive enough? -- Are consistency rules clear and enforceable? -- Are examples provided for all major patterns? - -**Structure Completeness:** - -- Is the project structure complete and specific? -- Are all files and directories defined? -- Are integration points clearly specified? -- Are component boundaries well-defined? - -**Pattern Completeness:** - -- Are all potential conflict points addressed? -- Are naming conventions comprehensive? -- Are communication patterns fully specified? -- Are process patterns (error handling, etc.) complete? - -### 4. Gap Analysis - -Identify and document any missing elements: - -**Critical Gaps:** - -- Missing architectural decisions that block implementation -- Incomplete patterns that could cause conflicts -- Missing structural elements needed for development -- Undefined integration points - -**Important Gaps:** - -- Areas that need more detailed specification -- Patterns that could be more comprehensive -- Documentation that would help implementation -- Examples that would clarify complex decisions - -**Nice-to-Have Gaps:** - -- Additional patterns that would be helpful -- Supplementary documentation -- Tooling recommendations -- Development workflow optimizations - -### 5. Address Validation Issues - -For any issues found, facilitate resolution: - -**Critical Issues:** -"I found some issues that need to be addressed before implementation: - -{{critical_issue_description}} - -These could cause implementation problems. How would you like to resolve this?" - -**Important Issues:** -"I noticed a few areas that could be improved: - -{{important_issue_description}} - -These aren't blocking, but addressing them would make implementation smoother. Should we work on these?" - -**Minor Issues:** -"Here are some minor suggestions for improvement: - -{{minor_issue_description}} - -These are optional refinements. Would you like to address any of these?" - -### 6. Generate Validation Content - -Prepare the content to append to the document: - -#### Content Structure: - -```markdown -## Architecture Validation Results - -### Coherence Validation ✅ - -**Decision Compatibility:** -{{assessment_of_how_all_decisions_work_together}} - -**Pattern Consistency:** -{{verification_that_patterns_support_decisions}} - -**Structure Alignment:** -{{confirmation_that_structure_supports_architecture}} - -### Requirements Coverage Validation ✅ - -**Epic/Feature Coverage:** -{{verification_that_all_epics_or_features_are_supported}} - -**Functional Requirements Coverage:** -{{confirmation_that_all_FRs_are_architecturally_supported}} - -**Non-Functional Requirements Coverage:** -{{verification_that_NFRs_are_addressed}} - -### Implementation Readiness Validation ✅ - -**Decision Completeness:** -{{assessment_of_decision_documentation_completeness}} - -**Structure Completeness:** -{{evaluation_of_project_structure_completeness}} - -**Pattern Completeness:** -{{verification_of_implementation_patterns_completeness}} - -### Gap Analysis Results - -{{gap_analysis_findings_with_priority_levels}} - -### Validation Issues Addressed - -{{description_of_any_issues_found_and_resolutions}} - -### Architecture Completeness Checklist - -**✅ Requirements Analysis** - -- [x] Project context thoroughly analyzed -- [x] Scale and complexity assessed -- [x] Technical constraints identified -- [x] Cross-cutting concerns mapped - -**✅ Architectural Decisions** - -- [x] Critical decisions documented with versions -- [x] Technology stack fully specified -- [x] Integration patterns defined -- [x] Performance considerations addressed - -**✅ Implementation Patterns** - -- [x] Naming conventions established -- [x] Structure patterns defined -- [x] Communication patterns specified -- [x] Process patterns documented - -**✅ Project Structure** - -- [x] Complete directory structure defined -- [x] Component boundaries established -- [x] Integration points mapped -- [x] Requirements to structure mapping complete - -### Architecture Readiness Assessment - -**Overall Status:** READY FOR IMPLEMENTATION - -**Confidence Level:** {{high/medium/low}} based on validation results - -**Key Strengths:** -{{list_of_architecture_strengths}} - -**Areas for Future Enhancement:** -{{areas_that_could_be_improved_later}} - -### Implementation Handoff - -**AI Agent Guidelines:** - -- Follow all architectural decisions exactly as documented -- Use implementation patterns consistently across all components -- Respect project structure and boundaries -- Refer to this document for all architectural questions - -**First Implementation Priority:** -{{starter_template_command_or_first_architectural_step}} -``` - -### 7. Present Content and Menu - -Show the validation results and present choices: - -"I've completed a comprehensive validation of your architecture. - -**Validation Summary:** - -- ✅ Coherence: All decisions work together -- ✅ Coverage: All requirements are supported -- ✅ Readiness: AI agents can implement consistently - -**Here's what I'll add to complete the architecture document:** - -[Show the complete markdown content from step 6] - -**What would you like to do?** -[A] Advanced Elicitation - Address any complex architectural concerns -[P] Party Mode - Review validation from different implementation perspectives -[C] Continue - Complete the architecture and finish workflow - -### 8. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with validation issues -- Process enhanced solutions for complex concerns -- Ask user: "Accept these architectural improvements? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with validation context -- Process collaborative insights on implementation readiness -- Ask user: "Accept these changes to the validation results? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Append the final content to `{planning_artifacts}/architecture.md` -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]` -- Load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to the document using the structure from step 6. - -## SUCCESS METRICS: - -✅ All architectural decisions validated for coherence -✅ Complete requirements coverage verified -✅ Implementation readiness confirmed -✅ All gaps identified and addressed -✅ Comprehensive validation checklist completed -✅ A/P/C menu presented and handled correctly -✅ Content properly appended to document when C selected - -## FAILURE MODES: - -❌ Skipping validation of decision compatibility -❌ Not verifying all requirements are architecturally supported -❌ Missing potential implementation conflicts -❌ Not addressing gaps found during validation -❌ Providing incomplete validation checklist -❌ Not presenting A/P/C menu after content generation - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## NEXT STEP: - -After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md` to complete the workflow and provide implementation guidance. - -Remember: Do NOT proceed to step-08 until user explicitly selects 'C' from the A/P/C menu and content is saved! diff --git a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md b/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md deleted file mode 100644 index f44850b2b..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md +++ /dev/null @@ -1,76 +0,0 @@ -# Step 8: Architecture Completion & Handoff - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input - -- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions -- ✅ ALWAYS treat this as collaborative completion between architectural peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on successful workflow completion and implementation handoff -- 🎯 PROVIDE clear next steps for implementation phase -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 🎯 Present completion summary and implementation guidance -- 📖 Update frontmatter with final workflow state -- 🚫 THIS IS THE FINAL STEP IN THIS WORKFLOW - -## YOUR TASK: - -Complete the architecture workflow, provide a comprehensive completion summary, and guide the user to the next phase of their project development. - -## COMPLETION SEQUENCE: - -### 1. Congratulate the User on Completion - -Both you and the User completed something amazing here - give a summary of what you achieved together and really congratulate the user on a job well done. - -### 2. Update the created document's frontmatter - -```yaml -stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8] -workflowType: 'architecture' -lastStep: 8 -status: 'complete' -completedAt: '{{current_date}}' -``` - -### 3. Next Steps Guidance - -Architecture complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` - -Upon Completion of task output: offer to answer any questions about the Architecture Document. - - -## SUCCESS METRICS: - -✅ Complete architecture document delivered with all sections -✅ All architectural decisions documented and validated -✅ Implementation patterns and consistency rules finalized -✅ Project structure complete with all files and directories -✅ User provided with clear next steps and implementation guidance -✅ Workflow status properly updated -✅ User collaboration maintained throughout completion process - -## FAILURE MODES: - -❌ Not providing clear implementation guidance -❌ Missing final validation of document completeness -❌ Not updating workflow status appropriately -❌ Failing to celebrate the successful completion -❌ Not providing specific next steps for the user -❌ Rushing completion without proper summary - -❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions -❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file -❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols - -## WORKFLOW COMPLETE: - -This is the final step of the Architecture workflow. The user now has a complete, validated architecture document ready for AI agent implementation. - -The architecture will serve as the single source of truth for all technical decisions, ensuring consistent implementation across the entire project development lifecycle. diff --git a/src/bmm/workflows/3-solutioning/create-architecture/workflow.md b/src/bmm/workflows/3-solutioning/create-architecture/workflow.md deleted file mode 100644 index 1fac8d1ac..000000000 --- a/src/bmm/workflows/3-solutioning/create-architecture/workflow.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -name: create-architecture -description: 'Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"' ---- - -# Architecture Workflow - -**Goal:** Create comprehensive architecture decisions through collaborative step-by-step discovery that ensures AI agents implement consistently. - -**Your Role:** You are an architectural facilitator collaborating with a peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and architectural knowledge, while the user brings domain expertise and product vision. Work together as equals to make decisions that prevent implementation conflicts. - ---- - -## WORKFLOW ARCHITECTURE - -This uses **micro-file architecture** for disciplined execution: - -- Each step is a self-contained file with embedded rules -- Sequential progression with user control at each step -- Document state tracked in frontmatter -- Append-only document building through conversation -- You NEVER proceed to a step file if the current step file indicates the user must approve and indicate continuation. - ---- - -## INITIALIZATION - -### Configuration Loading - -Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve: - -- `project_name`, `output_folder`, `planning_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as system-generated current datetime -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Paths - -- `installed_path` = `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture` -- `template_path` = `{installed_path}/architecture-decision-template.md` -- `data_files_path` = `{installed_path}/data/` - ---- - -## EXECUTION - -Read fully and follow: `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md` to begin the workflow. - -**Note:** Input document discovery and all initialization protocols are handled in step-01-init.md. diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md deleted file mode 100644 index c8d6b1330..000000000 --- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md +++ /dev/null @@ -1,259 +0,0 @@ ---- -name: 'step-01-validate-prerequisites' -description: 'Validate required documents exist and extract all requirements for epic and story creation' - -# Path Definitions -workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories' - -# File References -thisStepFile: './step-01-validate-prerequisites.md' -nextStepFile: './step-02-design-epics.md' -workflowFile: '{workflow_path}/workflow.md' -outputFile: '{planning_artifacts}/epics.md' -epicsTemplate: '{workflow_path}/templates/epics-template.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' - -# Template References -epicsTemplate: '{workflow_path}/templates/epics-template.md' ---- - -# Step 1: Validate Prerequisites and Extract Requirements - -## STEP GOAL: - -To validate that all required input documents exist and extract all requirements (FRs, NFRs, and additional requirements from UX/Architecture) needed for epic and story creation. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product strategist and technical specifications writer -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring requirements extraction expertise -- ✅ User brings their product vision and context - -### Step-Specific Rules: - -- 🎯 Focus ONLY on extracting and organizing requirements -- 🚫 FORBIDDEN to start creating epics or stories in this step -- 💬 Extract requirements from ALL available documents -- 🚪 POPULATE the template sections exactly as needed - -## EXECUTION PROTOCOLS: - -- 🎯 Extract requirements systematically from all documents -- 💾 Populate {outputFile} with extracted requirements -- 📖 Update frontmatter with extraction progress -- 🚫 FORBIDDEN to load next step until user selects 'C' and requirements are extracted - -## REQUIREMENTS EXTRACTION PROCESS: - -### 1. Welcome and Overview - -Welcome {user_name} to comprehensive epic and story creation! - -**CRITICAL PREREQUISITE VALIDATION:** - -Verify required documents exist and are complete: - -1. **PRD.md** - Contains requirements (FRs and NFRs) and product scope -2. **Architecture.md** - Contains technical decisions, API contracts, data models -3. **UX Design.md** (if UI exists) - Contains interaction patterns, mockups, user flows - -### 2. Document Discovery and Validation - -Search for required documents using these patterns (sharded means a large document was split into multiple small files with an index.md into a folder) - if the whole document is found, use that instead of the sharded version: - -**PRD Document Search Priority:** - -1. `{planning_artifacts}/*prd*.md` (whole document) -2. `{planning_artifacts}/*prd*/index.md` (sharded version) - -**Architecture Document Search Priority:** - -1. `{planning_artifacts}/*architecture*.md` (whole document) -2. `{planning_artifacts}/*architecture*/index.md` (sharded version) - -**UX Design Document Search (Optional):** - -1. `{planning_artifacts}/*ux*.md` (whole document) -2. `{planning_artifacts}/*ux*/index.md` (sharded version) - -Before proceeding, Ask the user if there are any other documents to include for analysis, and if anything found should be excluded. Wait for user confirmation. Once confirmed, create the {outputFile} from the {epicsTemplate} and in the front matter list the files in the array of `inputDocuments: []`. - -### 3. Extract Functional Requirements (FRs) - -From the PRD document (full or sharded), read then entire document and extract ALL functional requirements: - -**Extraction Method:** - -- Look for numbered items like "FR1:", "Functional Requirement 1:", or similar -- Identify requirement statements that describe what the system must DO -- Include user actions, system behaviors, and business rules - -**Format the FR list as:** - -``` -FR1: [Clear, testable requirement description] -FR2: [Clear, testable requirement description] -... -``` - -### 4. Extract Non-Functional Requirements (NFRs) - -From the PRD document, extract ALL non-functional requirements: - -**Extraction Method:** - -- Look for performance, security, usability, reliability requirements -- Identify constraints and quality attributes -- Include technical standards and compliance requirements - -**Format the NFR list as:** - -``` -NFR1: [Performance/Security/Usability requirement] -NFR2: [Performance/Security/Usability requirement] -... -``` - -### 5. Extract Additional Requirements from Architecture - -Review the Architecture document for technical requirements that impact epic and story creation: - -**Look for:** - -- **Starter Template**: Does Architecture specify a starter/greenfield template? If YES, document this for Epic 1 Story 1 -- Infrastructure and deployment requirements -- Integration requirements with external systems -- Data migration or setup requirements -- Monitoring and logging requirements -- API versioning or compatibility requirements -- Security implementation requirements - -**IMPORTANT**: If a starter template is mentioned in Architecture, note it prominently. This will impact Epic 1 Story 1. - -**Format Additional Requirements as:** - -``` -- [Technical requirement from Architecture that affects implementation] -- [Infrastructure setup requirement] -- [Integration requirement] -... -``` - -### 6. Extract Additional Requirements from UX (if exists) - -Review the UX document for requirements that affect epic and story creation: - -**Look for:** - -- Responsive design requirements -- Accessibility requirements -- Browser/device compatibility -- User interaction patterns that need implementation -- Animation or transition requirements -- Error handling UX requirements - -**Add these to Additional Requirements list.** - -### 7. Load and Initialize Template - -Load {epicsTemplate} and initialize {outputFile}: - -1. Copy the entire template to {outputFile} -2. Replace {{project_name}} with the actual project name -3. Replace placeholder sections with extracted requirements: - - {{fr_list}} → extracted FRs - - {{nfr_list}} → extracted NFRs - - {{additional_requirements}} → extracted additional requirements -4. Leave {{requirements_coverage_map}} and {{epics_list}} as placeholders for now - -### 8. Present Extracted Requirements - -Display to user: - -**Functional Requirements Extracted:** - -- Show count of FRs found -- Display the first few FRs as examples -- Ask if any FRs are missing or incorrectly captured - -**Non-Functional Requirements Extracted:** - -- Show count of NFRs found -- Display key NFRs -- Ask if any constraints were missed - -**Additional Requirements:** - -- Summarize technical requirements from Architecture -- Summarize UX requirements (if applicable) -- Verify completeness - -### 9. Get User Confirmation - -Ask: "Do these extracted requirements accurately represent what needs to be built? Any additions or corrections?" - -Update the requirements based on user feedback until confirmation is received. - -## CONTENT TO SAVE TO DOCUMENT: - -After extraction and confirmation, update {outputFile} with: - -- Complete FR list in {{fr_list}} section -- Complete NFR list in {{nfr_list}} section -- All additional requirements in {{additional_requirements}} section - -### 10. Present MENU OPTIONS - -Display: `**Confirm the Requirements are complete and correct to [C] continue:**` - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- User can chat or ask questions - always respond and then end with display again of the menu option - -#### Menu Handling Logic: - -- IF C: Save all to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile} -- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#10-present-menu-options) - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN C is selected and all requirements are saved to document and frontmatter is updated, will you then read fully and follow: {nextStepFile} to begin epic design step. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All required documents found and validated -- All FRs extracted and formatted correctly -- All NFRs extracted and formatted correctly -- Additional requirements from Architecture/UX identified -- Template initialized with requirements -- User confirms requirements are complete and accurate - -### ❌ SYSTEM FAILURE: - -- Missing required documents -- Incomplete requirements extraction -- Template not properly initialized -- Not saving requirements to output file - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md deleted file mode 100644 index 1b497c2ad..000000000 --- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md +++ /dev/null @@ -1,233 +0,0 @@ ---- -name: 'step-02-design-epics' -description: 'Design and approve the epics_list that will organize all requirements into user-value-focused epics' - -# Path Definitions -workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories' - -# File References -thisStepFile: './step-02-design-epics.md' -nextStepFile: './step-03-create-stories.md' -workflowFile: '{workflow_path}/workflow.md' -outputFile: '{planning_artifacts}/epics.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' - -# Template References -epicsTemplate: '{workflow_path}/templates/epics-template.md' ---- - -# Step 2: Design Epic List - -## STEP GOAL: - -To design and get approval for the epics_list that will organize all requirements into user-value-focused epics. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product strategist and technical specifications writer -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring product strategy and epic design expertise -- ✅ User brings their product vision and priorities - -### Step-Specific Rules: - -- 🎯 Focus ONLY on creating the epics_list -- 🚫 FORBIDDEN to create individual stories in this step -- 💬 Organize epics around user value, not technical layers -- 🚪 GET explicit approval for the epics_list -- 🔗 **CRITICAL: Each epic must be standalone and enable future epics without requiring future epics to function** - -## EXECUTION PROTOCOLS: - -- 🎯 Design epics collaboratively based on extracted requirements -- 💾 Update {{epics_list}} in {outputFile} -- 📖 Document the FR coverage mapping -- 🚫 FORBIDDEN to load next step until user approves epics_list - -## EPIC DESIGN PROCESS: - -### 1. Review Extracted Requirements - -Load {outputFile} and review: - -- **Functional Requirements:** Count and review FRs from Step 1 -- **Non-Functional Requirements:** Review NFRs that need to be addressed -- **Additional Requirements:** Review technical and UX requirements - -### 2. Explain Epic Design Principles - -**EPIC DESIGN PRINCIPLES:** - -1. **User-Value First**: Each epic must enable users to accomplish something meaningful -2. **Requirements Grouping**: Group related FRs that deliver cohesive user outcomes -3. **Incremental Delivery**: Each epic should deliver value independently -4. **Logical Flow**: Natural progression from user's perspective -5. **🔗 Dependency-Free Within Epic**: Stories within an epic must NOT depend on future stories - -**⚠️ CRITICAL PRINCIPLE:** -Organize by USER VALUE, not technical layers: - -**✅ CORRECT Epic Examples (Standalone & Enable Future Epics):** - -- Epic 1: User Authentication & Profiles (users can register, login, manage profiles) - **Standalone: Complete auth system** -- Epic 2: Content Creation (users can create, edit, publish content) - **Standalone: Uses auth, creates content** -- Epic 3: Social Interaction (users can follow, comment, like content) - **Standalone: Uses auth + content** -- Epic 4: Search & Discovery (users can find content and other users) - **Standalone: Uses all previous** - -**❌ WRONG Epic Examples (Technical Layers or Dependencies):** - -- Epic 1: Database Setup (creates all tables upfront) - **No user value** -- Epic 2: API Development (builds all endpoints) - **No user value** -- Epic 3: Frontend Components (creates reusable components) - **No user value** -- Epic 4: Deployment Pipeline (CI/CD setup) - **No user value** - -**🔗 DEPENDENCY RULES:** - -- Each epic must deliver COMPLETE functionality for its domain -- Epic 2 must not require Epic 3 to function -- Epic 3 can build upon Epic 1 & 2 but must stand alone - -### 3. Design Epic Structure Collaboratively - -**Step A: Identify User Value Themes** - -- Look for natural groupings in the FRs -- Identify user journeys or workflows -- Consider user types and their goals - -**Step B: Propose Epic Structure** -For each proposed epic: - -1. **Epic Title**: User-centric, value-focused -2. **User Outcome**: What users can accomplish after this epic -3. **FR Coverage**: Which FR numbers this epic addresses -4. **Implementation Notes**: Any technical or UX considerations - -**Step C: Create the epics_list** - -Format the epics_list as: - -``` -## Epic List - -### Epic 1: [Epic Title] -[Epic goal statement - what users can accomplish] -**FRs covered:** FR1, FR2, FR3, etc. - -### Epic 2: [Epic Title] -[Epic goal statement - what users can accomplish] -**FRs covered:** FR4, FR5, FR6, etc. - -[Continue for all epics] -``` - -### 4. Present Epic List for Review - -Display the complete epics_list to user with: - -- Total number of epics -- FR coverage per epic -- User value delivered by each epic -- Any natural dependencies - -### 5. Create Requirements Coverage Map - -Create {{requirements_coverage_map}} showing how each FR maps to an epic: - -``` -### FR Coverage Map - -FR1: Epic 1 - [Brief description] -FR2: Epic 1 - [Brief description] -FR3: Epic 2 - [Brief description] -... -``` - -This ensures no FRs are missed. - -### 6. Collaborative Refinement - -Ask user: - -- "Does this epic structure align with your product vision?" -- "Are all user outcomes properly captured?" -- "Should we adjust any epic groupings?" -- "Are there natural dependencies we've missed?" - -### 7. Get Final Approval - -**CRITICAL:** Must get explicit user approval: -"Do you approve this epic structure for proceeding to story creation?" - -If user wants changes: - -- Make the requested adjustments -- Update the epics_list -- Re-present for approval -- Repeat until approval is received - -## CONTENT TO UPDATE IN DOCUMENT: - -After approval, update {outputFile}: - -1. Replace {{epics_list}} placeholder with the approved epic list -2. Replace {{requirements_coverage_map}} with the coverage map -3. Ensure all FRs are mapped to epics - -### 8. Present MENU OPTIONS - -Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue" - -#### Menu Handling Logic: - -- IF A: Read fully and follow: {advancedElicitationTask} -- IF P: Read fully and follow: {partyModeWorkflow} -- IF C: Save approved epics_list to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile} -- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-menu-options) - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution completes, redisplay the menu -- User can chat or ask questions - always respond when conversation ends, redisplay the menu options - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN C is selected and the approved epics_list is saved to document, will you then read fully and follow: {nextStepFile} to begin story creation step. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- Epics designed around user value -- All FRs mapped to specific epics -- epics_list created and formatted correctly -- Requirements coverage map completed -- User gives explicit approval for epic structure -- Document updated with approved epics - -### ❌ SYSTEM FAILURE: - -- Epics organized by technical layers -- Missing FRs in coverage map -- No user approval obtained -- epics_list not saved to document - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md deleted file mode 100644 index 2e13f9b2c..000000000 --- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md +++ /dev/null @@ -1,272 +0,0 @@ ---- -name: 'step-03-create-stories' -description: 'Generate all epics with their stories following the template structure' - -# Path Definitions -workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories' - -# File References -thisStepFile: './step-03-create-stories.md' -nextStepFile: './step-04-final-validation.md' -workflowFile: '{workflow_path}/workflow.md' -outputFile: '{planning_artifacts}/epics.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' - -# Template References -epicsTemplate: '{workflow_path}/templates/epics-template.md' ---- - -# Step 3: Generate Epics and Stories - -## STEP GOAL: - -To generate all epics with their stories based on the approved epics_list, following the template structure exactly. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: Process epics sequentially -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product strategist and technical specifications writer -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring story creation and acceptance criteria expertise -- ✅ User brings their implementation priorities and constraints - -### Step-Specific Rules: - -- 🎯 Generate stories for each epic following the template exactly -- 🚫 FORBIDDEN to deviate from template structure -- 💬 Each story must have clear acceptance criteria -- 🚪 ENSURE each story is completable by a single dev agent -- 🔗 **CRITICAL: Stories MUST NOT depend on future stories within the same epic** - -## EXECUTION PROTOCOLS: - -- 🎯 Generate stories collaboratively with user input -- 💾 Append epics and stories to {outputFile} following template -- 📖 Process epics one at a time in sequence -- 🚫 FORBIDDEN to skip any epic or rush through stories - -## STORY GENERATION PROCESS: - -### 1. Load Approved Epic Structure - -Load {outputFile} and review: - -- Approved epics_list from Step 2 -- FR coverage map -- All requirements (FRs, NFRs, additional) -- Template structure at the end of the document - -### 2. Explain Story Creation Approach - -**STORY CREATION GUIDELINES:** - -For each epic, create stories that: - -- Follow the exact template structure -- Are sized for single dev agent completion -- Have clear user value -- Include specific acceptance criteria -- Reference requirements being fulfilled - -**🚨 DATABASE/ENTITY CREATION PRINCIPLE:** -Create tables/entities ONLY when needed by the story: - -- ❌ WRONG: Epic 1 Story 1 creates all 50 database tables -- ✅ RIGHT: Each story creates/alters ONLY the tables it needs - -**🔗 STORY DEPENDENCY PRINCIPLE:** -Stories must be independently completable in sequence: - -- ❌ WRONG: Story 1.2 requires Story 1.3 to be completed first -- ✅ RIGHT: Each story can be completed based only on previous stories -- ❌ WRONG: "Wait for Story 1.4 to be implemented before this works" -- ✅ RIGHT: "This story works independently and enables future stories" - -**STORY FORMAT (from template):** - -``` -### Story {N}.{M}: {story_title} - -As a {user_type}, -I want {capability}, -So that {value_benefit}. - -**Acceptance Criteria:** - -**Given** {precondition} -**When** {action} -**Then** {expected_outcome} -**And** {additional_criteria} -``` - -**✅ GOOD STORY EXAMPLES:** - -_Epic 1: User Authentication_ - -- Story 1.1: User Registration with Email -- Story 1.2: User Login with Password -- Story 1.3: Password Reset via Email - -_Epic 2: Content Creation_ - -- Story 2.1: Create New Blog Post -- Story 2.2: Edit Existing Blog Post -- Story 2.3: Publish Blog Post - -**❌ BAD STORY EXAMPLES:** - -- Story: "Set up database" (no user value) -- Story: "Create all models" (too large, no user value) -- Story: "Build authentication system" (too large) -- Story: "Login UI (depends on Story 1.3 API endpoint)" (future dependency!) -- Story: "Edit post (requires Story 1.4 to be implemented first)" (wrong order!) - -### 3. Process Epics Sequentially - -For each epic in the approved epics_list: - -#### A. Epic Overview - -Display: - -- Epic number and title -- Epic goal statement -- FRs covered by this epic -- Any NFRs or additional requirements relevant - -#### B. Story Breakdown - -Work with user to break down the epic into stories: - -- Identify distinct user capabilities -- Ensure logical flow within the epic -- Size stories appropriately - -#### C. Generate Each Story - -For each story in the epic: - -1. **Story Title**: Clear, action-oriented -2. **User Story**: Complete the As a/I want/So that format -3. **Acceptance Criteria**: Write specific, testable criteria - -**AC Writing Guidelines:** - -- Use Given/When/Then format -- Each AC should be independently testable -- Include edge cases and error conditions -- Reference specific requirements when applicable - -#### D. Collaborative Review - -After writing each story: - -- Present the story to user -- Ask: "Does this story capture the requirement correctly?" -- "Is the scope appropriate for a single dev session?" -- "Are the acceptance criteria complete and testable?" - -#### E. Append to Document - -When story is approved: - -- Append it to {outputFile} following template structure -- Use correct numbering (Epic N, Story M) -- Maintain proper markdown formatting - -### 4. Epic Completion - -After all stories for an epic are complete: - -- Display epic summary -- Show count of stories created -- Verify all FRs for the epic are covered -- Get user confirmation to proceed to next epic - -### 5. Repeat for All Epics - -Continue the process for each epic in the approved list, processing them in order (Epic 1, Epic 2, etc.). - -### 6. Final Document Completion - -After all epics and stories are generated: - -- Verify the document follows template structure exactly -- Ensure all placeholders are replaced -- Confirm all FRs are covered -- Check formatting consistency - -## TEMPLATE STRUCTURE COMPLIANCE: - -The final {outputFile} must follow this structure exactly: - -1. **Overview** section with project name -2. **Requirements Inventory** with all three subsections populated -3. **FR Coverage Map** showing requirement to epic mapping -4. **Epic List** with approved epic structure -5. **Epic sections** for each epic (N = 1, 2, 3...) - - Epic title and goal - - All stories for that epic (M = 1, 2, 3...) - - Story title and user story - - Acceptance Criteria using Given/When/Then format - -### 7. Present FINAL MENU OPTIONS - -After all epics and stories are complete: - -Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue" - -#### Menu Handling Logic: - -- IF A: Read fully and follow: {advancedElicitationTask} -- IF P: Read fully and follow: {partyModeWorkflow} -- IF C: Save content to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile} -- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-final-menu-options) - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After other menu items execution, return to this menu -- User can chat or ask questions - always respond and then end with display again of the menu options - -## CRITICAL STEP COMPLETION NOTE - -ONLY WHEN [C continue option] is selected and [all epics and stories saved to document following the template structure exactly], will you then read fully and follow: `{nextStepFile}` to begin final validation phase. - ---- - -## 🚨 SYSTEM SUCCESS/FAILURE METRICS - -### ✅ SUCCESS: - -- All epics processed in sequence -- Stories created for each epic -- Template structure followed exactly -- All FRs covered by stories -- Stories appropriately sized -- Acceptance criteria are specific and testable -- Document is complete and ready for development - -### ❌ SYSTEM FAILURE: - -- Deviating from template structure -- Missing epics or stories -- Stories too large or unclear -- Missing acceptance criteria -- Not following proper formatting - -**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md b/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md deleted file mode 100644 index 4ee791a7a..000000000 --- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -name: 'step-04-final-validation' -description: 'Validate complete coverage of all requirements and ensure implementation readiness' - -# Path Definitions -workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories' - -# File References -thisStepFile: './step-04-final-validation.md' -workflowFile: '{workflow_path}/workflow.md' -outputFile: '{planning_artifacts}/epics.md' - -# Task References -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' - -# Template References -epicsTemplate: '{workflow_path}/templates/epics-template.md' ---- - -# Step 4: Final Validation - -## STEP GOAL: - -To validate complete coverage of all requirements and ensure stories are ready for development. - -## MANDATORY EXECUTION RULES (READ FIRST): - -### Universal Rules: - -- 🛑 NEVER generate content without user input -- 📖 CRITICAL: Read the complete step file before taking any action -- 🔄 CRITICAL: Process validation sequentially without skipping -- 📋 YOU ARE A FACILITATOR, not a content generator -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Role Reinforcement: - -- ✅ You are a product strategist and technical specifications writer -- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role -- ✅ We engage in collaborative dialogue, not command-response -- ✅ You bring validation expertise and quality assurance -- ✅ User brings their implementation priorities and final review - -### Step-Specific Rules: - -- 🎯 Focus ONLY on validating complete requirements coverage -- 🚫 FORBIDDEN to skip any validation checks -- 💬 Validate FR coverage, story completeness, and dependencies -- 🚪 ENSURE all stories are ready for development - -## EXECUTION PROTOCOLS: - -- 🎯 Validate every requirement has story coverage -- 💾 Check story dependencies and flow -- 📖 Verify architecture compliance -- 🚫 FORBIDDEN to approve incomplete coverage - -## CONTEXT BOUNDARIES: - -- Available context: Complete epic and story breakdown from previous steps -- Focus: Final validation of requirements coverage and story readiness -- Limits: Validation only, no new content creation -- Dependencies: Completed story generation from Step 3 - -## VALIDATION PROCESS: - -### 1. FR Coverage Validation - -Review the complete epic and story breakdown to ensure EVERY FR is covered: - -**CRITICAL CHECK:** - -- Go through each FR from the Requirements Inventory -- Verify it appears in at least one story -- Check that acceptance criteria fully address the FR -- No FRs should be left uncovered - -### 2. Architecture Implementation Validation - -**Check for Starter Template Setup:** - -- Does Architecture document specify a starter template? -- If YES: Epic 1 Story 1 must be "Set up initial project from starter template" -- This includes cloning, installing dependencies, initial configuration - -**Database/Entity Creation Validation:** - -- Are database tables/entities created ONLY when needed by stories? -- ❌ WRONG: Epic 1 creates all tables upfront -- ✅ RIGHT: Tables created as part of the first story that needs them -- Each story should create/modify ONLY what it needs - -### 3. Story Quality Validation - -**Each story must:** - -- Be completable by a single dev agent -- Have clear acceptance criteria -- Reference specific FRs it implements -- Include necessary technical details -- **Not have forward dependencies** (can only depend on PREVIOUS stories) -- Be implementable without waiting for future stories - -### 4. Epic Structure Validation - -**Check that:** - -- Epics deliver user value, not technical milestones -- Dependencies flow naturally -- Foundation stories only setup what's needed -- No big upfront technical work - -### 5. Dependency Validation (CRITICAL) - -**Epic Independence Check:** - -- Does each epic deliver COMPLETE functionality for its domain? -- Can Epic 2 function without Epic 3 being implemented? -- Can Epic 3 function standalone using Epic 1 & 2 outputs? -- ❌ WRONG: Epic 2 requires Epic 3 features to work -- ✅ RIGHT: Each epic is independently valuable - -**Within-Epic Story Dependency Check:** -For each epic, review stories in order: - -- Can Story N.1 be completed without Stories N.2, N.3, etc.? -- Can Story N.2 be completed using only Story N.1 output? -- Can Story N.3 be completed using only Stories N.1 & N.2 outputs? -- ❌ WRONG: "This story depends on a future story" -- ❌ WRONG: Story references features not yet implemented -- ✅ RIGHT: Each story builds only on previous stories - -### 6. Complete and Save - -If all validations pass: - -- Update any remaining placeholders in the document -- Ensure proper formatting -- Save the final epics.md - -**Present Final Menu:** -**All validations complete!** [C] Complete Workflow - -When C is selected, the workflow is complete and the epics.md is ready for development. - -Epics and Stories complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md` - -Upon Completion of task output: offer to answer any questions about the Epics and Stories. diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/templates/epics-template.md b/src/bmm/workflows/3-solutioning/create-epics-and-stories/templates/epics-template.md deleted file mode 100644 index 05afe1f5f..000000000 --- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/templates/epics-template.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -stepsCompleted: [] -inputDocuments: [] ---- - -# {{project_name}} - Epic Breakdown - -## Overview - -This document provides the complete epic and story breakdown for {{project_name}}, decomposing the requirements from the PRD, UX Design if it exists, and Architecture requirements into implementable stories. - -## Requirements Inventory - -### Functional Requirements - -{{fr_list}} - -### NonFunctional Requirements - -{{nfr_list}} - -### Additional Requirements - -{{additional_requirements}} - -### FR Coverage Map - -{{requirements_coverage_map}} - -## Epic List - -{{epics_list}} - - - -## Epic {{N}}: {{epic_title_N}} - -{{epic_goal_N}} - - - -### Story {{N}}.{{M}}: {{story_title_N_M}} - -As a {{user_type}}, -I want {{capability}}, -So that {{value_benefit}}. - -**Acceptance Criteria:** - - - -**Given** {{precondition}} -**When** {{action}} -**Then** {{expected_outcome}} -**And** {{additional_criteria}} - - diff --git a/src/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md b/src/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md deleted file mode 100644 index 41a6ee106..000000000 --- a/src/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -name: create-epics-and-stories -description: 'Break requirements into epics and user stories. Use when the user says "create the epics and stories list"' ---- - -# Create Epics and Stories - -**Goal:** Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for development teams. - -**Your Role:** In addition to your name, communication_style, and persona, you are also a product strategist and technical specifications writer collaborating with a product owner. This is a partnership, not a client-vendor relationship. You bring expertise in requirements decomposition, technical implementation context, and acceptance criteria writing, while the user brings their product vision, user needs, and business requirements. Work together as equals. - ---- - -## WORKFLOW ARCHITECTURE - -This uses **step-file architecture** for disciplined execution: - -### Core Principles - -- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time -- **Just-In-Time Loading**: Only 1 current step file will be loaded and followed to completion - never load future step files until told to do so -- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed -- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document -- **Append-Only Building**: Build documents by appending content as directed to the output file - -### Step Processing Rules - -1. **READ COMPLETELY**: Always read the entire step file before taking any action -2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate -3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection -4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue) -5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step -6. **LOAD NEXT**: When directed, read fully and follow the next step file - -### Critical Rules (NO EXCEPTIONS) - -- 🛑 **NEVER** load multiple step files simultaneously -- 📖 **ALWAYS** read entire step file before execution -- 🚫 **NEVER** skip steps or optimize the sequence -- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step -- 🎯 **ALWAYS** follow the exact instructions in the step file -- ⏸️ **ALWAYS** halt at menus and wait for user input -- 📋 **NEVER** create mental todo lists from future steps - ---- - -## INITIALIZATION SEQUENCE - -### 1. Configuration Loading - -Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve: - -- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language` -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### 2. First Step EXECUTION - -Read fully and follow: `{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md` to begin the workflow. diff --git a/src/bmm/workflows/4-implementation/code-review/checklist.md b/src/bmm/workflows/4-implementation/code-review/checklist.md deleted file mode 100644 index f213a6b96..000000000 --- a/src/bmm/workflows/4-implementation/code-review/checklist.md +++ /dev/null @@ -1,23 +0,0 @@ -# Senior Developer Review - Validation Checklist - -- [ ] Story file loaded from `{{story_path}}` -- [ ] Story Status verified as reviewable (review) -- [ ] Epic and Story IDs resolved ({{epic_num}}.{{story_num}}) -- [ ] Story Context located or warning recorded -- [ ] Epic Tech Spec located or warning recorded -- [ ] Architecture/standards docs loaded (as available) -- [ ] Tech stack detected and documented -- [ ] MCP doc search performed (or web fallback) and references captured -- [ ] Acceptance Criteria cross-checked against implementation -- [ ] File List reviewed and validated for completeness -- [ ] Tests identified and mapped to ACs; gaps noted -- [ ] Code quality review performed on changed files -- [ ] Security review performed on changed files and dependencies -- [ ] Outcome decided (Approve/Changes Requested/Blocked) -- [ ] Review notes appended under "Senior Developer Review (AI)" -- [ ] Change Log updated with review entry -- [ ] Status updated according to settings (if enabled) -- [ ] Sprint status synced (if sprint tracking enabled) -- [ ] Story saved successfully - -_Reviewer: {{user_name}} on {{date}}_ diff --git a/src/bmm/workflows/4-implementation/code-review/instructions.xml b/src/bmm/workflows/4-implementation/code-review/instructions.xml deleted file mode 100644 index e5649559d..000000000 --- a/src/bmm/workflows/4-implementation/code-review/instructions.xml +++ /dev/null @@ -1,227 +0,0 @@ - - The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml - You MUST have already loaded and processed: {installed_path}/workflow.yaml - Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} - Generate all documents in {document_output_language} - - 🔥 YOU ARE AN ADVERSARIAL CODE REVIEWER - Find what's wrong or missing! 🔥 - Your purpose: Validate story file claims against actual implementation - Challenge everything: Are tasks marked [x] actually done? Are ACs really implemented? - Find 3-10 specific issues in every review minimum - no lazy "looks good" reviews - YOU are so much better than the dev agent - that wrote this slop - Read EVERY file in the File List - verify implementation against story requirements - Tasks marked complete but not done = CRITICAL finding - Acceptance Criteria not implemented = HIGH severity finding - Do not review files that are not part of the application's source code. Always exclude the _bmad/ and _bmad-output/ folders from the review. Always exclude IDE and CLI configuration folders like .cursor/ and .windsurf/ and .claude/ - - - - Use provided {{story_path}} or ask user which story file to review - Read COMPLETE story file - Set {{story_key}} = extracted key from filename (e.g., "1-2-user-authentication.md" → "1-2-user-authentication") or story - metadata - Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Agent Record → File List, Change Log - - - Check if git repository detected in current directory - - Run `git status --porcelain` to find uncommitted changes - Run `git diff --name-only` to see modified files - Run `git diff --cached --name-only` to see staged files - Compile list of actually changed files from git output - - - - Compare story's Dev Agent Record → File List with actual git changes - Note discrepancies: - - Files in git but not in story File List - - Files in story File List but no git changes - - Missing documentation of what was actually changed - - - - Load {project_context} for coding standards (if exists) - - - - Extract ALL Acceptance Criteria from story - Extract ALL Tasks/Subtasks with completion status ([x] vs [ ]) - From Dev Agent Record → File List, compile list of claimed changes - - Create review plan: - 1. **AC Validation**: Verify each AC is actually implemented - 2. **Task Audit**: Verify each [x] task is really done - 3. **Code Quality**: Security, performance, maintainability - 4. **Test Quality**: Real tests vs placeholder bullshit - - - - - VALIDATE EVERY CLAIM - Check git reality vs story claims - - - Review git vs story File List discrepancies: - 1. **Files changed but not in story File List** → MEDIUM finding (incomplete documentation) - 2. **Story lists files but no git changes** → HIGH finding (false claims) - 3. **Uncommitted changes not documented** → MEDIUM finding (transparency issue) - - - - Create comprehensive review file list from story File List and git changes - - - For EACH Acceptance Criterion: - 1. Read the AC requirement - 2. Search implementation files for evidence - 3. Determine: IMPLEMENTED, PARTIAL, or MISSING - 4. If MISSING/PARTIAL → HIGH SEVERITY finding - - - - For EACH task marked [x]: - 1. Read the task description - 2. Search files for evidence it was actually done - 3. **CRITICAL**: If marked [x] but NOT DONE → CRITICAL finding - 4. Record specific proof (file:line) - - - - For EACH file in comprehensive review list: - 1. **Security**: Look for injection risks, missing validation, auth issues - 2. **Performance**: N+1 queries, inefficient loops, missing caching - 3. **Error Handling**: Missing try/catch, poor error messages - 4. **Code Quality**: Complex functions, magic numbers, poor naming - 5. **Test Quality**: Are tests real assertions or placeholders? - - - - NOT LOOKING HARD ENOUGH - Find more problems! - Re-examine code for: - - Edge cases and null handling - - Architecture violations - - Documentation gaps - - Integration issues - - Dependency problems - - Git commit message quality (if applicable) - - Find at least 3 more specific, actionable issues - - - - - Categorize findings: HIGH (must fix), MEDIUM (should fix), LOW (nice to fix) - Set {{fixed_count}} = 0 - Set {{action_count}} = 0 - - **🔥 CODE REVIEW FINDINGS, {user_name}!** - - **Story:** {{story_file}} - **Git vs Story Discrepancies:** {{git_discrepancy_count}} found - **Issues Found:** {{high_count}} High, {{medium_count}} Medium, {{low_count}} Low - - ## 🔴 CRITICAL ISSUES - - Tasks marked [x] but not actually implemented - - Acceptance Criteria not implemented - - Story claims files changed but no git evidence - - Security vulnerabilities - - ## 🟡 MEDIUM ISSUES - - Files changed but not documented in story File List - - Uncommitted changes not tracked - - Performance problems - - Poor test coverage/quality - - Code maintainability issues - - ## 🟢 LOW ISSUES - - Code style improvements - - Documentation gaps - - Git commit message quality - - - What should I do with these issues? - - 1. **Fix them automatically** - I'll update the code and tests - 2. **Create action items** - Add to story Tasks/Subtasks for later - 3. **Show me details** - Deep dive into specific issues - - Choose [1], [2], or specify which issue to examine: - - - Fix all HIGH and MEDIUM issues in the code - Add/update tests as needed - Update File List in story if files changed - Update story Dev Agent Record with fixes applied - Set {{fixed_count}} = number of HIGH and MEDIUM issues fixed - Set {{action_count}} = 0 - - - - Add "Review Follow-ups (AI)" subsection to Tasks/Subtasks - For each issue: `- [ ] [AI-Review][Severity] Description [file:line]` - Set {{action_count}} = number of action items created - Set {{fixed_count}} = 0 - - - - Show detailed explanation with code examples - Return to fix decision - - - - - - - Set {{new_status}} = "done" - Update story Status field to "done" - - - Set {{new_status}} = "in-progress" - Update story Status field to "in-progress" - - Save story file - - - - Set {{current_sprint_status}} = "enabled" - - - Set {{current_sprint_status}} = "no-sprint-tracking" - - - - - Load the FULL file: {sprint_status} - Find development_status key matching {{story_key}} - - - Update development_status[{{story_key}}] = "done" - Save file, preserving ALL comments and structure - ✅ Sprint status synced: {{story_key}} → done - - - - Update development_status[{{story_key}}] = "in-progress" - Save file, preserving ALL comments and structure - 🔄 Sprint status synced: {{story_key}} → in-progress - - - - ⚠️ Story file updated, but sprint-status sync failed: {{story_key}} not found in sprint-status.yaml - - - - - ℹ️ Story status updated (no sprint tracking configured) - - - **✅ Review Complete!** - - **Story Status:** {{new_status}} - **Issues Fixed:** {{fixed_count}} - **Action Items Created:** {{action_count}} - - {{#if new_status == "done"}}Code review complete!{{else}}Address the action items and continue development.{{/if}} - - - - \ No newline at end of file diff --git a/src/bmm/workflows/4-implementation/code-review/workflow.yaml b/src/bmm/workflows/4-implementation/code-review/workflow.yaml deleted file mode 100644 index 7965af5ae..000000000 --- a/src/bmm/workflows/4-implementation/code-review/workflow.yaml +++ /dev/null @@ -1,43 +0,0 @@ -# Review Story Workflow -name: code-review -description: 'Perform adversarial code review finding specific issues. Use when the user says "run code review" or "review this code"' - -# Critical variables from config -config_source: "{project-root}/_bmad/bmm/config.yaml" -user_name: "{config_source}:user_name" -communication_language: "{config_source}:communication_language" -user_skill_level: "{config_source}:user_skill_level" -document_output_language: "{config_source}:document_output_language" -date: system-generated -planning_artifacts: "{config_source}:planning_artifacts" -implementation_artifacts: "{config_source}:implementation_artifacts" -sprint_status: "{implementation_artifacts}/sprint-status.yaml" - -# Workflow components -installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review" -instructions: "{installed_path}/instructions.xml" -validation: "{installed_path}/checklist.md" -template: false - -project_context: "**/project-context.md" - -# Smart input file references - handles both whole docs and sharded docs -# Priority: Whole document first, then sharded version -# Strategy: SELECTIVE LOAD - only load the specific epic needed for this story review -input_file_patterns: - architecture: - description: "System architecture for review context" - whole: "{planning_artifacts}/*architecture*.md" - sharded: "{planning_artifacts}/*architecture*/*.md" - load_strategy: "FULL_LOAD" - ux_design: - description: "UX design specification (if UI review)" - whole: "{planning_artifacts}/*ux*.md" - sharded: "{planning_artifacts}/*ux*/*.md" - load_strategy: "FULL_LOAD" - epics: - description: "Epic containing story being reviewed" - whole: "{planning_artifacts}/*epic*.md" - sharded_index: "{planning_artifacts}/*epic*/index.md" - sharded_single: "{planning_artifacts}/*epic*/epic-{{epic_num}}.md" - load_strategy: "SELECTIVE_LOAD" diff --git a/src/bmm/workflows/4-implementation/correct-course/checklist.md b/src/bmm/workflows/4-implementation/correct-course/checklist.md deleted file mode 100644 index f13ab9be0..000000000 --- a/src/bmm/workflows/4-implementation/correct-course/checklist.md +++ /dev/null @@ -1,288 +0,0 @@ -# Change Navigation Checklist - -This checklist is executed as part of: {project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml -Work through each section systematically with the user, recording findings and impacts - - - -
- - -Identify the triggering story that revealed this issue -Document story ID and brief description -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Define the core problem precisely -Categorize issue type: - - Technical limitation discovered during implementation - - New requirement emerged from stakeholders - - Misunderstanding of original requirements - - Strategic pivot or market change - - Failed approach requiring different solution -Write clear problem statement -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Assess initial impact and gather supporting evidence -Collect concrete examples, error messages, stakeholder feedback, or technical constraints -Document evidence for later reference -[ ] Done / [ ] N/A / [ ] Action-needed - - - -HALT: "Cannot proceed without understanding what caused the need for change" -HALT: "Need concrete evidence or examples of the issue before analyzing impact" - - -
- -
- - -Evaluate current epic containing the trigger story -Can this epic still be completed as originally planned? -If no, what modifications are needed? -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Determine required epic-level changes -Check each scenario: - - Modify existing epic scope or acceptance criteria - - Add new epic to address the issue - - Remove or defer epic that's no longer viable - - Completely redefine epic based on new understanding -Document specific epic changes needed -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Review all remaining planned epics for required changes -Check each future epic for impact -Identify dependencies that may be affected -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Check if issue invalidates future epics or necessitates new ones -Does this change make any planned epics obsolete? -Are new epics needed to address gaps created by this change? -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Consider if epic order or priority should change -Should epics be resequenced based on this issue? -Do priorities need adjustment? -[ ] Done / [ ] N/A / [ ] Action-needed - - -
- -
- - -Check PRD for conflicts -Does issue conflict with core PRD goals or objectives? -Do requirements need modification, addition, or removal? -Is the defined MVP still achievable or does scope need adjustment? -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Review Architecture document for conflicts -Check each area for impact: - - System components and their interactions - - Architectural patterns and design decisions - - Technology stack choices - - Data models and schemas - - API designs and contracts - - Integration points -Document specific architecture sections requiring updates -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Examine UI/UX specifications for conflicts -Check for impact on: - - User interface components - - User flows and journeys - - Wireframes or mockups - - Interaction patterns - - Accessibility considerations -Note specific UI/UX sections needing revision -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Consider impact on other artifacts -Review additional artifacts for impact: - - Deployment scripts - - Infrastructure as Code (IaC) - - Monitoring and observability setup - - Testing strategies - - Documentation - - CI/CD pipelines -Document any secondary artifacts requiring updates -[ ] Done / [ ] N/A / [ ] Action-needed - - -
- -
- - -Evaluate Option 1: Direct Adjustment -Can the issue be addressed by modifying existing stories? -Can new stories be added within the current epic structure? -Would this approach maintain project timeline and scope? -Effort estimate: [High/Medium/Low] -Risk level: [High/Medium/Low] -[ ] Viable / [ ] Not viable - - - -Evaluate Option 2: Potential Rollback -Would reverting recently completed stories simplify addressing this issue? -Which stories would need to be rolled back? -Is the rollback effort justified by the simplification gained? -Effort estimate: [High/Medium/Low] -Risk level: [High/Medium/Low] -[ ] Viable / [ ] Not viable - - - -Evaluate Option 3: PRD MVP Review -Is the original PRD MVP still achievable with this issue? -Does MVP scope need to be reduced or redefined? -Do core goals need modification based on new constraints? -What would be deferred to post-MVP if scope is reduced? -Effort estimate: [High/Medium/Low] -Risk level: [High/Medium/Low] -[ ] Viable / [ ] Not viable - - - -Select recommended path forward -Based on analysis of all options, choose the best path -Provide clear rationale considering: - - Implementation effort and timeline impact - - Technical risk and complexity - - Impact on team morale and momentum - - Long-term sustainability and maintainability - - Stakeholder expectations and business value -Selected approach: [Option 1 / Option 2 / Option 3 / Hybrid] -Justification: [Document reasoning] -[ ] Done / [ ] N/A / [ ] Action-needed - - -
- -
- - -Create identified issue summary -Write clear, concise problem statement -Include context about discovery and impact -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Document epic impact and artifact adjustment needs -Summarize findings from Epic Impact Assessment (Section 2) -Summarize findings from Artifact Conflict Analysis (Section 3) -Be specific about what changes are needed and why -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Present recommended path forward with rationale -Include selected approach from Section 4 -Provide complete justification for recommendation -Address trade-offs and alternatives considered -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Define PRD MVP impact and high-level action plan -State clearly if MVP is affected -Outline major action items needed for implementation -Identify dependencies and sequencing -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Establish agent handoff plan -Identify which roles/agents will execute the changes: - - Development team (for implementation) - - Product Owner / Scrum Master (for backlog changes) - - Product Manager / Architect (for strategic changes) -Define responsibilities for each role -[ ] Done / [ ] N/A / [ ] Action-needed - - -
- -
- - -Review checklist completion -Verify all applicable sections have been addressed -Confirm all [Action-needed] items have been documented -Ensure analysis is comprehensive and actionable -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Verify Sprint Change Proposal accuracy -Review complete proposal for consistency and clarity -Ensure all recommendations are well-supported by analysis -Check that proposal is actionable and specific -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Obtain explicit user approval -Present complete proposal to user -Get clear yes/no approval for proceeding -Document approval and any conditions -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Update sprint-status.yaml to reflect approved epic changes -If epics were added: Add new epic entries with status 'backlog' -If epics were removed: Remove corresponding entries -If epics were renumbered: Update epic IDs and story references -If stories were added/removed: Update story entries within affected epics -[ ] Done / [ ] N/A / [ ] Action-needed - - - -Confirm next steps and handoff plan -Review handoff responsibilities with user -Ensure all stakeholders understand their roles -Confirm timeline and success criteria -[ ] Done / [ ] N/A / [ ] Action-needed - - - -HALT: "Cannot proceed to proposal without complete impact analysis" -HALT: "Must have explicit approval before implementing changes" -HALT: "Must clearly define who will execute the proposed changes" - - -
- - - - -This checklist is for SIGNIFICANT changes affecting project direction -Work interactively with user - they make final decisions -Be factual, not blame-oriented when analyzing issues -Handle changes professionally as opportunities to improve the project -Maintain conversation context throughout - this is collaborative work - diff --git a/src/bmm/workflows/4-implementation/correct-course/instructions.md b/src/bmm/workflows/4-implementation/correct-course/instructions.md deleted file mode 100644 index bbe2c21e0..000000000 --- a/src/bmm/workflows/4-implementation/correct-course/instructions.md +++ /dev/null @@ -1,207 +0,0 @@ -# Correct Course - Sprint Change Management Instructions - -The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml -Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} -Generate all documents in {document_output_language} - -DOCUMENT OUTPUT: Updated epics, stories, or PRD sections. Clear, actionable changes. User skill level ({user_skill_level}) affects conversation style ONLY, not document updates. - - - - - Load {project_context} for coding standards and project-wide patterns (if exists) - Confirm change trigger and gather user description of the issue - Ask: "What specific issue or change has been identified that requires navigation?" - Verify access to required project documents: - - PRD (Product Requirements Document) - - Current Epics and Stories - - Architecture documentation - - UI/UX specifications - Ask user for mode preference: - - **Incremental** (recommended): Refine each edit collaboratively - - **Batch**: Present all changes at once for review - Store mode selection for use throughout workflow - -HALT: "Cannot navigate change without clear understanding of the triggering issue. Please provide specific details about what needs to change and why." - -HALT: "Need access to project documents (PRD, Epics, Architecture, UI/UX) to assess change impact. Please ensure these documents are accessible." - - - - - After discovery, these content variables are available: {prd_content}, {epics_content}, {architecture_content}, {ux_design_content}, {tech_spec_content}, {document_project_content} - - - - Read fully and follow the systematic analysis from: {checklist} - Work through each checklist section interactively with the user - Record status for each checklist item: - - [x] Done - Item completed successfully - - [N/A] Skip - Item not applicable to this change - - [!] Action-needed - Item requires attention or follow-up - Maintain running notes of findings and impacts discovered - Present checklist progress after each major section - -Identify blocking issues and work with user to resolve before continuing - - - -Based on checklist findings, create explicit edit proposals for each identified artifact - -For Story changes: - -- Show old → new text format -- Include story ID and section being modified -- Provide rationale for each change -- Example format: - - ``` - Story: [STORY-123] User Authentication - Section: Acceptance Criteria - - OLD: - - User can log in with email/password - - NEW: - - User can log in with email/password - - User can enable 2FA via authenticator app - - Rationale: Security requirement identified during implementation - ``` - -For PRD modifications: - -- Specify exact sections to update -- Show current content and proposed changes -- Explain impact on MVP scope and requirements - -For Architecture changes: - -- Identify affected components, patterns, or technology choices -- Describe diagram updates needed -- Note any ripple effects on other components - -For UI/UX specification updates: - -- Reference specific screens or components -- Show wireframe or flow changes needed -- Connect changes to user experience impact - - - Present each edit proposal individually - Review and refine this change? Options: Approve [a], Edit [e], Skip [s] - Iterate on each proposal based on user feedback - - -Collect all edit proposals and present together at end of step - - - - -Compile comprehensive Sprint Change Proposal document with following sections: - -Section 1: Issue Summary - -- Clear problem statement describing what triggered the change -- Context about when/how the issue was discovered -- Evidence or examples demonstrating the issue - -Section 2: Impact Analysis - -- Epic Impact: Which epics are affected and how -- Story Impact: Current and future stories requiring changes -- Artifact Conflicts: PRD, Architecture, UI/UX documents needing updates -- Technical Impact: Code, infrastructure, or deployment implications - -Section 3: Recommended Approach - -- Present chosen path forward from checklist evaluation: - - Direct Adjustment: Modify/add stories within existing plan - - Potential Rollback: Revert completed work to simplify resolution - - MVP Review: Reduce scope or modify goals -- Provide clear rationale for recommendation -- Include effort estimate, risk assessment, and timeline impact - -Section 4: Detailed Change Proposals - -- Include all refined edit proposals from Step 3 -- Group by artifact type (Stories, PRD, Architecture, UI/UX) -- Ensure each change includes before/after and justification - -Section 5: Implementation Handoff - -- Categorize change scope: - - Minor: Direct implementation by dev team - - Moderate: Backlog reorganization needed (PO/SM) - - Major: Fundamental replan required (PM/Architect) -- Specify handoff recipients and their responsibilities -- Define success criteria for implementation - -Present complete Sprint Change Proposal to user -Write Sprint Change Proposal document to {default_output_file} -Review complete proposal. Continue [c] or Edit [e]? - - - -Get explicit user approval for complete proposal -Do you approve this Sprint Change Proposal for implementation? (yes/no/revise) - - - Gather specific feedback on what needs adjustment - Return to appropriate step to address concerns - If changes needed to edit proposals - If changes needed to overall proposal structure - - - - - Finalize Sprint Change Proposal document - Determine change scope classification: - -- **Minor**: Can be implemented directly by development team -- **Moderate**: Requires backlog reorganization and PO/SM coordination -- **Major**: Needs fundamental replan with PM/Architect involvement - -Provide appropriate handoff based on scope: - - - - - Route to: Development team for direct implementation - Deliverables: Finalized edit proposals and implementation tasks - - - - Route to: Product Owner / Scrum Master agents - Deliverables: Sprint Change Proposal + backlog reorganization plan - - - - Route to: Product Manager / Solution Architect - Deliverables: Complete Sprint Change Proposal + escalation notice - -Confirm handoff completion and next steps with user -Document handoff in workflow execution log - - - - - -Summarize workflow execution: - - Issue addressed: {{change_trigger}} - - Change scope: {{scope_classification}} - - Artifacts modified: {{list_of_artifacts}} - - Routed to: {{handoff_recipients}} - -Confirm all deliverables produced: - -- Sprint Change Proposal document -- Specific edit proposals with before/after -- Implementation handoff plan - -Report workflow completion to user with personalized message: "✅ Correct Course workflow complete, {user_name}!" -Remind user of success criteria and next steps for implementation team - - - diff --git a/src/bmm/workflows/4-implementation/correct-course/workflow.yaml b/src/bmm/workflows/4-implementation/correct-course/workflow.yaml deleted file mode 100644 index f2211f7b3..000000000 --- a/src/bmm/workflows/4-implementation/correct-course/workflow.yaml +++ /dev/null @@ -1,53 +0,0 @@ -# Correct Course - Sprint Change Management Workflow -name: "correct-course" -description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"' - -config_source: "{project-root}/_bmad/bmm/config.yaml" -user_name: "{config_source}:user_name" -communication_language: "{config_source}:communication_language" -user_skill_level: "{config_source}:user_skill_level" -document_output_language: "{config_source}:document_output_language" -date: system-generated -implementation_artifacts: "{config_source}:implementation_artifacts" -planning_artifacts: "{config_source}:planning_artifacts" -project_knowledge: "{config_source}:project_knowledge" -project_context: "**/project-context.md" - -# Smart input file references - handles both whole docs and sharded docs -# Priority: Whole document first, then sharded version -# Strategy: Load project context for impact analysis -input_file_patterns: - prd: - description: "Product requirements for impact analysis" - whole: "{planning_artifacts}/*prd*.md" - sharded: "{planning_artifacts}/*prd*/*.md" - load_strategy: "FULL_LOAD" - epics: - description: "All epics to analyze change impact" - whole: "{planning_artifacts}/*epic*.md" - sharded: "{planning_artifacts}/*epic*/*.md" - load_strategy: "FULL_LOAD" - architecture: - description: "System architecture and decisions" - whole: "{planning_artifacts}/*architecture*.md" - sharded: "{planning_artifacts}/*architecture*/*.md" - load_strategy: "FULL_LOAD" - ux_design: - description: "UX design specification (if UI impacts)" - whole: "{planning_artifacts}/*ux*.md" - sharded: "{planning_artifacts}/*ux*/*.md" - load_strategy: "FULL_LOAD" - tech_spec: - description: "Technical specification" - whole: "{planning_artifacts}/*tech-spec*.md" - load_strategy: "FULL_LOAD" - document_project: - description: "Brownfield project documentation (optional)" - sharded: "{project_knowledge}/index.md" - load_strategy: "INDEX_GUIDED" - -installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course" -template: false -instructions: "{installed_path}/instructions.md" -checklist: "{installed_path}/checklist.md" -default_output_file: "{planning_artifacts}/sprint-change-proposal-{date}.md" diff --git a/src/bmm/workflows/4-implementation/create-story/checklist.md b/src/bmm/workflows/4-implementation/create-story/checklist.md deleted file mode 100644 index d9ed06375..000000000 --- a/src/bmm/workflows/4-implementation/create-story/checklist.md +++ /dev/null @@ -1,358 +0,0 @@ -# 🎯 Story Context Quality Competition Prompt - -## **🔥 CRITICAL MISSION: Outperform and Fix the Original Create-Story LLM** - -You are an independent quality validator in a **FRESH CONTEXT**. Your mission is to **thoroughly review** a story file that was generated by the create-story workflow and **systematically identify any mistakes, omissions, or disasters** that the original LLM missed. - -**Your purpose is NOT just to validate - it's to FIX and PREVENT LLM developer mistakes, omissions, or disasters!** - -### **🚨 CRITICAL MISTAKES TO PREVENT:** - -- **Reinventing wheels** - Creating duplicate functionality instead of reusing existing -- **Wrong libraries** - Using incorrect frameworks, versions, or dependencies -- **Wrong file locations** - Violating project structure and organization -- **Breaking regressions** - Implementing changes that break existing functionality -- **Ignoring UX** - Not following user experience design requirements -- **Vague implementations** - Creating unclear, ambiguous implementations -- **Lying about completion** - Implementing incorrectly or incompletely -- **Not learning from past work** - Ignoring previous story learnings and patterns - -### **🚨 EXHAUSTIVE ANALYSIS REQUIRED:** - -You must thoroughly analyze **ALL artifacts** to extract critical context - do NOT be lazy or skim! This is the most important quality control function in the entire development process! - -### **🔬 UTILIZE SUBPROCESSES AND SUBAGENTS:** - -Use research subagents, subprocesses, or parallel processing if available to thoroughly analyze different artifacts **simultaneously and thoroughly**. Leave no stone unturned! - -### **🎯 COMPETITIVE EXCELLENCE:** - -This is a COMPETITION to create the **ULTIMATE story context** that makes LLM developer mistakes **IMPOSSIBLE**! - -## **🚀 HOW TO USE THIS CHECKLIST** - -### **When Running from Create-Story Workflow:** - -- The `{project-root}/_bmad/core/tasks/workflow.xml` framework will automatically: - - Load this checklist file - - Load the newly created story file (`{story_file_path}`) - - Load workflow variables from `{installed_path}/workflow.yaml` - - Execute the validation process - -### **When Running in Fresh Context:** - -- User should provide the story file path being reviewed -- Load the story file directly -- Load the corresponding workflow.yaml for variable context -- Proceed with systematic analysis - -### **Required Inputs:** - -- **Story file**: The story file to review and improve -- **Workflow variables**: From workflow.yaml (implementation_artifacts, epics_file, etc.) -- **Source documents**: Epics, architecture, etc. (discovered or provided) -- **Validation framework**: `validate-workflow.xml` (handles checklist execution) - ---- - -## **🔬 SYSTEMATIC RE-ANALYSIS APPROACH** - -You will systematically re-do the entire story creation process, but with a critical eye for what the original LLM might have missed: - -### **Step 1: Load and Understand the Target** - -1. **Load the workflow configuration**: `{installed_path}/workflow.yaml` for variable inclusion -2. **Load the story file**: `{story_file_path}` (provided by user or discovered) -3. **Load validation framework**: `{project-root}/_bmad/core/tasks/workflow.xml` -4. **Extract metadata**: epic_num, story_num, story_key, story_title from story file -5. **Resolve all workflow variables**: implementation_artifacts, epics_file, architecture_file, etc. -6. **Understand current status**: What story implementation guidance is currently provided? - -**Note:** If running in fresh context, user should provide the story file path being reviewed. If running from create-story workflow, the validation framework will automatically discover the checklist and story file. - -### **Step 2: Exhaustive Source Document Analysis** - -**🔥 CRITICAL: Treat this like YOU are creating the story from scratch to PREVENT DISASTERS!** -**Discover everything the original LLM missed that could cause developer mistakes, omissions, or disasters!** - -#### **2.1 Epics and Stories Analysis** - -- Load `{epics_file}` (or sharded equivalents) -- Extract **COMPLETE Epic {{epic_num}} context**: - - Epic objectives and business value - - ALL stories in this epic (for cross-story context) - - Our specific story's requirements, acceptance criteria - - Technical requirements and constraints - - Cross-story dependencies and prerequisites - -#### **2.2 Architecture Deep-Dive** - -- Load `{architecture_file}` (single or sharded) -- **Systematically scan for ANYTHING relevant to this story:** - - Technical stack with versions (languages, frameworks, libraries) - - Code structure and organization patterns - - API design patterns and contracts - - Database schemas and relationships - - Security requirements and patterns - - Performance requirements and optimization strategies - - Testing standards and frameworks - - Deployment and environment patterns - - Integration patterns and external services - -#### **2.3 Previous Story Intelligence (if applicable)** - -- If `story_num > 1`, load the previous story file -- Extract **actionable intelligence**: - - Dev notes and learnings - - Review feedback and corrections needed - - Files created/modified and their patterns - - Testing approaches that worked/didn't work - - Problems encountered and solutions found - - Code patterns and conventions established - -#### **2.4 Git History Analysis (if available)** - -- Analyze recent commits for patterns: - - Files created/modified in previous work - - Code patterns and conventions used - - Library dependencies added/changed - - Architecture decisions implemented - - Testing approaches used - -#### **2.5 Latest Technical Research** - -- Identify any libraries/frameworks mentioned -- Research latest versions and critical information: - - Breaking changes or security updates - - Performance improvements or deprecations - - Best practices for current versions - -### **Step 3: Disaster Prevention Gap Analysis** - -**🚨 CRITICAL: Identify every mistake the original LLM missed that could cause DISASTERS!** - -#### **3.1 Reinvention Prevention Gaps** - -- **Wheel reinvention:** Areas where developer might create duplicate functionality -- **Code reuse opportunities** not identified that could prevent redundant work -- **Existing solutions** not mentioned that developer should extend instead of replace - -#### **3.2 Technical Specification DISASTERS** - -- **Wrong libraries/frameworks:** Missing version requirements that could cause compatibility issues -- **API contract violations:** Missing endpoint specifications that could break integrations -- **Database schema conflicts:** Missing requirements that could corrupt data -- **Security vulnerabilities:** Missing security requirements that could expose the system -- **Performance disasters:** Missing requirements that could cause system failures - -#### **3.3 File Structure DISASTERS** - -- **Wrong file locations:** Missing organization requirements that could break build processes -- **Coding standard violations:** Missing conventions that could create inconsistent codebase -- **Integration pattern breaks:** Missing data flow requirements that could cause system failures -- **Deployment failures:** Missing environment requirements that could prevent deployment - -#### **3.4 Regression DISASTERS** - -- **Breaking changes:** Missing requirements that could break existing functionality -- **Test failures:** Missing test requirements that could allow bugs to reach production -- **UX violations:** Missing user experience requirements that could ruin the product -- **Learning failures:** Missing previous story context that could repeat same mistakes - -#### **3.5 Implementation DISASTERS** - -- **Vague implementations:** Missing details that could lead to incorrect or incomplete work -- **Completion lies:** Missing acceptance criteria that could allow fake implementations -- **Scope creep:** Missing boundaries that could cause unnecessary work -- **Quality failures:** Missing quality requirements that could deliver broken features - -### **Step 4: LLM-Dev-Agent Optimization Analysis** - -**CRITICAL STEP: Optimize story context for LLM developer agent consumption** - -**Analyze current story for LLM optimization issues:** - -- **Verbosity problems:** Excessive detail that wastes tokens without adding value -- **Ambiguity issues:** Vague instructions that could lead to multiple interpretations -- **Context overload:** Too much information not directly relevant to implementation -- **Missing critical signals:** Key requirements buried in verbose text -- **Poor structure:** Information not organized for efficient LLM processing - -**Apply LLM Optimization Principles:** - -- **Clarity over verbosity:** Be precise and direct, eliminate fluff -- **Actionable instructions:** Every sentence should guide implementation -- **Scannable structure:** Use clear headings, bullet points, and emphasis -- **Token efficiency:** Pack maximum information into minimum text -- **Unambiguous language:** Clear requirements with no room for interpretation - -### **Step 5: Improvement Recommendations** - -**For each gap identified, provide specific, actionable improvements:** - -#### **5.1 Critical Misses (Must Fix)** - -- Missing essential technical requirements -- Missing previous story context that could cause errors -- Missing anti-pattern prevention that could lead to duplicate code -- Missing security or performance requirements - -#### **5.2 Enhancement Opportunities (Should Add)** - -- Additional architectural guidance that would help developer -- More detailed technical specifications -- Better code reuse opportunities -- Enhanced testing guidance - -#### **5.3 Optimization Suggestions (Nice to Have)** - -- Performance optimization hints -- Additional context for complex scenarios -- Enhanced debugging or development tips - -#### **5.4 LLM Optimization Improvements** - -- Token-efficient phrasing of existing content -- Clearer structure for LLM processing -- More actionable and direct instructions -- Reduced verbosity while maintaining completeness - ---- - -## **🎯 COMPETITION SUCCESS METRICS** - -**You WIN against the original LLM if you identify:** - -### **Category 1: Critical Misses (Blockers)** - -- Essential technical requirements the developer needs but aren't provided -- Previous story learnings that would prevent errors if ignored -- Anti-pattern prevention that would prevent code duplication -- Security or performance requirements that must be followed - -### **Category 2: Enhancement Opportunities** - -- Architecture guidance that would significantly help implementation -- Technical specifications that would prevent wrong approaches -- Code reuse opportunities the developer should know about -- Testing guidance that would improve quality - -### **Category 3: Optimization Insights** - -- Performance or efficiency improvements -- Development workflow optimizations -- Additional context for complex scenarios - ---- - -## **📋 INTERACTIVE IMPROVEMENT PROCESS** - -After completing your systematic analysis, present your findings to the user interactively: - -### **Step 5: Present Improvement Suggestions** - -``` -🎯 **STORY CONTEXT QUALITY REVIEW COMPLETE** - -**Story:** {{story_key}} - {{story_title}} - -I found {{critical_count}} critical issues, {{enhancement_count}} enhancements, and {{optimization_count}} optimizations. - -## **🚨 CRITICAL ISSUES (Must Fix)** - -{{list each critical issue with clear, actionable description}} - -## **⚡ ENHANCEMENT OPPORTUNITIES (Should Add)** - -{{list each enhancement with clear benefit description}} - -## **✨ OPTIMIZATIONS (Nice to Have)** - -{{list each optimization with benefit description}} - -## **🤖 LLM OPTIMIZATION (Token Efficiency & Clarity)** - -{{list each LLM optimization that will improve dev agent performance: -- Reduce verbosity while maintaining completeness -- Improve structure for better LLM processing -- Make instructions more actionable and direct -- Enhance clarity and reduce ambiguity}} -``` - -### **Step 6: Interactive User Selection** - -After presenting the suggestions, ask the user: - -``` -**IMPROVEMENT OPTIONS:** - -Which improvements would you like me to apply to the story? - -**Select from the numbered list above, or choose:** -- **all** - Apply all suggested improvements -- **critical** - Apply only critical issues -- **select** - I'll choose specific numbers -- **none** - Keep story as-is -- **details** - Show me more details about any suggestion - -Your choice: -``` - -### **Step 7: Apply Selected Improvements** - -When user accepts improvements: - -- **Load the story file** -- **Apply accepted changes** (make them look natural, as if they were always there) -- **DO NOT reference** the review process, original LLM, or that changes were "added" or "enhanced" -- **Ensure clean, coherent final story** that reads as if it was created perfectly the first time - -### **Step 8: Confirmation** - -After applying changes: - -``` -✅ **STORY IMPROVEMENTS APPLIED** - -Updated {{count}} sections in the story file. - -The story now includes comprehensive developer guidance to prevent common implementation issues and ensure flawless execution. - -**Next Steps:** -1. Review the updated story -2. Run `dev-story` for implementation -``` - ---- - -## **💪 COMPETITIVE EXCELLENCE MINDSET** - -**Your goal:** Improve the story file with dev agent needed context that makes flawless implementation inevitable while being optimized for LLM developer agent consumption. Remember the dev agent will ONLY have this file to use. - -**Success Criteria:** The LLM developer agent that processes your improved story will have: - -- ✅ Clear technical requirements they must follow -- ✅ Previous work context they can build upon -- ✅ Anti-pattern prevention to avoid common mistakes -- ✅ Comprehensive guidance for efficient implementation -- ✅ **Optimized content structure** for maximum clarity and minimum token waste -- ✅ **Actionable instructions** with no ambiguity or verbosity -- ✅ **Efficient information density** - maximum guidance in minimum text - -**Every improvement should make it IMPOSSIBLE for the developer to:** - -- Reinvent existing solutions -- Use wrong approaches or libraries -- Create duplicate functionality -- Miss critical requirements -- Make implementation errors - -**LLM Optimization Should Make it IMPOSSIBLE for the developer agent to:** - -- Misinterpret requirements due to ambiguity -- Waste tokens on verbose, non-actionable content -- Struggle to find critical information buried in text -- Get confused by poor structure or organization -- Miss key implementation signals due to inefficient communication - -**Go create the ultimate developer implementation guide! 🚀** diff --git a/src/bmm/workflows/4-implementation/create-story/instructions.xml b/src/bmm/workflows/4-implementation/create-story/instructions.xml deleted file mode 100644 index f9433371f..000000000 --- a/src/bmm/workflows/4-implementation/create-story/instructions.xml +++ /dev/null @@ -1,346 +0,0 @@ - - The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml - You MUST have already loaded and processed: {installed_path}/workflow.yaml - Communicate all responses in {communication_language} and generate all documents in {document_output_language} - - 🔥 CRITICAL MISSION: You are creating the ULTIMATE story context engine that prevents LLM developer mistakes, omissions or - disasters! 🔥 - Your purpose is NOT to copy from epics - it's to create a comprehensive, optimized story file that gives the DEV agent - EVERYTHING needed for flawless implementation - COMMON LLM MISTAKES TO PREVENT: reinventing wheels, wrong libraries, wrong file locations, breaking regressions, ignoring UX, - vague implementations, lying about completion, not learning from past work - 🚨 EXHAUSTIVE ANALYSIS REQUIRED: You must thoroughly analyze ALL artifacts to extract critical context - do NOT be lazy or skim! - This is the most important function in the entire development process! - 🔬 UTILIZE SUBPROCESSES AND SUBAGENTS: Use research subagents, subprocesses or parallel processing if available to thoroughly - analyze different artifacts simultaneously and thoroughly - ❓ SAVE QUESTIONS: If you think of questions or clarifications during analysis, save them for the end after the complete story is - written - 🎯 ZERO USER INTERVENTION: Process should be fully automated except for initial epic/story selection or missing documents - - - - Parse user-provided story path: extract epic_num, story_num, story_title from format like "1-2-user-auth" - Set {{epic_num}}, {{story_num}}, {{story_key}} from user input - GOTO step 2a - - - Check if {{sprint_status}} file exists for auto discover - - 🚫 No sprint status file found and no story specified - - **Required Options:** - 1. Run `sprint-planning` to initialize sprint tracking (recommended) - 2. Provide specific epic-story number to create (e.g., "1-2-user-auth") - 3. Provide path to story documents if sprint status doesn't exist yet - - Choose option [1], provide epic-story number, path to story docs, or [q] to quit: - - - HALT - No work needed - - - - Run sprint-planning workflow first to create sprint-status.yaml - HALT - User needs to run sprint-planning - - - - Parse user input: extract epic_num, story_num, story_title - Set {{epic_num}}, {{story_num}}, {{story_key}} from user input - GOTO step 2a - - - - Use user-provided path for story documents - GOTO step 2a - - - - - - MUST read COMPLETE {sprint_status} file from start to end to preserve order - Load the FULL file: {{sprint_status}} - Read ALL lines from beginning to end - do not skip any content - Parse the development_status section completely - - Find the FIRST story (by reading in order from top to bottom) where: - - Key matches pattern: number-number-name (e.g., "1-2-user-auth") - - NOT an epic key (epic-X) or retrospective (epic-X-retrospective) - - Status value equals "backlog" - - - - 📋 No backlog stories found in sprint-status.yaml - - All stories are either already created, in progress, or done. - - **Options:** - 1. Run sprint-planning to refresh story tracking - 2. Load PM agent and run correct-course to add more stories - 3. Check if current sprint is complete and run retrospective - - HALT - - - Extract from found story key (e.g., "1-2-user-authentication"): - - epic_num: first number before dash (e.g., "1") - - story_num: second number after first dash (e.g., "2") - - story_title: remainder after second dash (e.g., "user-authentication") - - Set {{story_id}} = "{{epic_num}}.{{story_num}}" - Store story_key for later use (e.g., "1-2-user-authentication") - - - Check if this is the first story in epic {{epic_num}} by looking for {{epic_num}}-1-* pattern - - Load {{sprint_status}} and check epic-{{epic_num}} status - If epic status is "backlog" → update to "in-progress" - If epic status is "contexted" (legacy status) → update to "in-progress" (backward compatibility) - If epic status is "in-progress" → no change needed - - 🚫 ERROR: Cannot create story in completed epic - Epic {{epic_num}} is marked as 'done'. All stories are complete. - If you need to add more work, either: - 1. Manually change epic status back to 'in-progress' in sprint-status.yaml - 2. Create a new epic for additional work - HALT - Cannot proceed - - - 🚫 ERROR: Invalid epic status '{{epic_status}}' - Epic {{epic_num}} has invalid status. Expected: backlog, in-progress, or done - Please fix sprint-status.yaml manually or run sprint-planning to regenerate - HALT - Cannot proceed - - 📊 Epic {{epic_num}} status updated to in-progress - - - GOTO step 2a - - Load the FULL file: {{sprint_status}} - Read ALL lines from beginning to end - do not skip any content - Parse the development_status section completely - - Find the FIRST story (by reading in order from top to bottom) where: - - Key matches pattern: number-number-name (e.g., "1-2-user-auth") - - NOT an epic key (epic-X) or retrospective (epic-X-retrospective) - - Status value equals "backlog" - - - - 📋 No backlog stories found in sprint-status.yaml - - All stories are either already created, in progress, or done. - - **Options:** - 1. Run sprint-planning to refresh story tracking - 2. Load PM agent and run correct-course to add more stories - 3. Check if current sprint is complete and run retrospective - - HALT - - - Extract from found story key (e.g., "1-2-user-authentication"): - - epic_num: first number before dash (e.g., "1") - - story_num: second number after first dash (e.g., "2") - - story_title: remainder after second dash (e.g., "user-authentication") - - Set {{story_id}} = "{{epic_num}}.{{story_num}}" - Store story_key for later use (e.g., "1-2-user-authentication") - - - Check if this is the first story in epic {{epic_num}} by looking for {{epic_num}}-1-* pattern - - Load {{sprint_status}} and check epic-{{epic_num}} status - If epic status is "backlog" → update to "in-progress" - If epic status is "contexted" (legacy status) → update to "in-progress" (backward compatibility) - If epic status is "in-progress" → no change needed - - 🚫 ERROR: Cannot create story in completed epic - Epic {{epic_num}} is marked as 'done'. All stories are complete. - If you need to add more work, either: - 1. Manually change epic status back to 'in-progress' in sprint-status.yaml - 2. Create a new epic for additional work - HALT - Cannot proceed - - - 🚫 ERROR: Invalid epic status '{{epic_status}}' - Epic {{epic_num}} has invalid status. Expected: backlog, in-progress, or done - Please fix sprint-status.yaml manually or run sprint-planning to regenerate - HALT - Cannot proceed - - 📊 Epic {{epic_num}} status updated to in-progress - - - GOTO step 2a - - - - 🔬 EXHAUSTIVE ARTIFACT ANALYSIS - This is where you prevent future developer fuckups! - - - - Available content: {epics_content}, {prd_content}, {architecture_content}, {ux_content}, - {project_context} - - - From {epics_content}, extract Epic {{epic_num}} complete context: **EPIC ANALYSIS:** - Epic - objectives and business value - ALL stories in this epic for cross-story context - Our specific story's requirements, user story - statement, acceptance criteria - Technical requirements and constraints - Dependencies on other stories/epics - Source hints pointing to - original documents - Extract our story ({{epic_num}}-{{story_num}}) details: **STORY FOUNDATION:** - User story statement - (As a, I want, so that) - Detailed acceptance criteria (already BDD formatted) - Technical requirements specific to this story - - Business context and value - Success criteria - - Find {{previous_story_num}}: scan {implementation_artifacts} for the story file in epic {{epic_num}} with the highest story number less than {{story_num}} - Load previous story file: {implementation_artifacts}/{{epic_num}}-{{previous_story_num}}-*.md **PREVIOUS STORY INTELLIGENCE:** - - Dev notes and learnings from previous story - Review feedback and corrections needed - Files that were created/modified and their - patterns - Testing approaches that worked/didn't work - Problems encountered and solutions found - Code patterns established Extract - all learnings that could impact current story implementation - - - - - Get last 5 commit titles to understand recent work patterns - Analyze 1-5 most recent commits for relevance to current story: - - Files created/modified - - Code patterns and conventions used - - Library dependencies added/changed - - Architecture decisions implemented - - Testing approaches used - - Extract actionable insights for current story implementation - - - - - 🏗️ ARCHITECTURE INTELLIGENCE - Extract everything the developer MUST follow! **ARCHITECTURE DOCUMENT ANALYSIS:** Systematically - analyze architecture content for story-relevant requirements: - - - - Load complete {architecture_content} - - - Load architecture index and scan all architecture files - **CRITICAL ARCHITECTURE EXTRACTION:** For - each architecture section, determine if relevant to this story: - **Technical Stack:** Languages, frameworks, libraries with - versions - **Code Structure:** Folder organization, naming conventions, file patterns - **API Patterns:** Service structure, endpoint - patterns, data contracts - **Database Schemas:** Tables, relationships, constraints relevant to story - **Security Requirements:** - Authentication patterns, authorization rules - **Performance Requirements:** Caching strategies, optimization patterns - **Testing - Standards:** Testing frameworks, coverage expectations, test patterns - **Deployment Patterns:** Environment configurations, build - processes - **Integration Patterns:** External service integrations, data flows Extract any story-specific requirements that the - developer MUST follow - Identify any architectural decisions that override previous patterns - - - - 🌐 ENSURE LATEST TECH KNOWLEDGE - Prevent outdated implementations! **WEB INTELLIGENCE:** Identify specific - technical areas that require latest version knowledge: - - - From architecture analysis, identify specific libraries, APIs, or - frameworks - For each critical technology, research latest stable version and key changes: - - Latest API documentation and breaking changes - - Security vulnerabilities or updates - - Performance improvements or deprecations - - Best practices for current version - - **EXTERNAL CONTEXT INCLUSION:** Include in story any critical latest information the developer needs: - - Specific library versions and why chosen - - API endpoints with parameters and authentication - - Recent security patches or considerations - - Performance optimization techniques - - Migration considerations if upgrading - - - - - 📝 CREATE ULTIMATE STORY FILE - The developer's master implementation guide! - - Initialize from template.md: - {default_output_file} - story_header - - - story_requirements - - - - developer_context_section **DEV AGENT GUARDRAILS:** - technical_requirements - architecture_compliance - library_framework_requirements - - file_structure_requirements - testing_requirements - - - - previous_story_intelligence - - - - - git_intelligence_summary - - - - - latest_tech_information - - - - project_context_reference - - - - story_completion_status - - - Set story Status to: "ready-for-dev" - Add completion note: "Ultimate - context engine analysis completed - comprehensive developer guide created" - - - - Validate against checklist at {installed_path}/checklist.md using _bmad/core/tasks/validate-workflow.xml - Save story document unconditionally - - - - Update {{sprint_status}} - Load the FULL file and read all development_status entries - Find development_status key matching {{story_key}} - Verify current status is "backlog" (expected previous state) - Update development_status[{{story_key}}] = "ready-for-dev" - Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - - Report completion - **🎯 ULTIMATE BMad Method STORY CONTEXT CREATED, {user_name}!** - - **Story Details:** - - Story ID: {{story_id}} - - Story Key: {{story_key}} - - File: {{story_file}} - - Status: ready-for-dev - - **Next Steps:** - 1. Review the comprehensive story in {{story_file}} - 2. Run dev agents `dev-story` for optimized implementation - 3. Run `code-review` when complete (auto-marks done) - 4. Optional: If Test Architect module installed, run `/bmad:tea:automate` after `dev-story` to generate guardrail tests - - **The developer now has everything needed for flawless implementation!** - - - - diff --git a/src/bmm/workflows/4-implementation/create-story/template.md b/src/bmm/workflows/4-implementation/create-story/template.md deleted file mode 100644 index c4e129f5f..000000000 --- a/src/bmm/workflows/4-implementation/create-story/template.md +++ /dev/null @@ -1,49 +0,0 @@ -# Story {{epic_num}}.{{story_num}}: {{story_title}} - -Status: ready-for-dev - - - -## Story - -As a {{role}}, -I want {{action}}, -so that {{benefit}}. - -## Acceptance Criteria - -1. [Add acceptance criteria from epics/PRD] - -## Tasks / Subtasks - -- [ ] Task 1 (AC: #) - - [ ] Subtask 1.1 -- [ ] Task 2 (AC: #) - - [ ] Subtask 2.1 - -## Dev Notes - -- Relevant architecture patterns and constraints -- Source tree components to touch -- Testing standards summary - -### Project Structure Notes - -- Alignment with unified project structure (paths, modules, naming) -- Detected conflicts or variances (with rationale) - -### References - -- Cite all technical details with source paths and sections, e.g. [Source: docs/.md#Section] - -## Dev Agent Record - -### Agent Model Used - -{{agent_model_name_version}} - -### Debug Log References - -### Completion Notes List - -### File List diff --git a/src/bmm/workflows/4-implementation/create-story/workflow.yaml b/src/bmm/workflows/4-implementation/create-story/workflow.yaml deleted file mode 100644 index 972972aff..000000000 --- a/src/bmm/workflows/4-implementation/create-story/workflow.yaml +++ /dev/null @@ -1,52 +0,0 @@ -name: create-story -description: 'Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"' - -# Critical variables from config -config_source: "{project-root}/_bmad/bmm/config.yaml" -user_name: "{config_source}:user_name" -communication_language: "{config_source}:communication_language" -document_output_language: "{config_source}:document_output_language" -user_skill_level: "{config_source}:user_skill_level" -date: system-generated -planning_artifacts: "{config_source}:planning_artifacts" -implementation_artifacts: "{config_source}:implementation_artifacts" - -# Workflow components -installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story" -template: "{installed_path}/template.md" -instructions: "{installed_path}/instructions.xml" -validation: "{installed_path}/checklist.md" - -# Variables and inputs -sprint_status: "{implementation_artifacts}/sprint-status.yaml" # Primary source for story tracking -epics_file: "{planning_artifacts}/epics.md" # Enhanced epics+stories with BDD and source hints -prd_file: "{planning_artifacts}/prd.md" # Fallback for requirements (if not in epics file) -architecture_file: "{planning_artifacts}/architecture.md" # Fallback for constraints (if not in epics file) -ux_file: "{planning_artifacts}/*ux*.md" # Fallback for UX requirements (if not in epics file) -story_title: "" # Will be elicited if not derivable -project_context: "**/project-context.md" -default_output_file: "{implementation_artifacts}/{{story_key}}.md" - -# Smart input file references - Simplified for enhanced approach -# The epics+stories file should contain everything needed with source hints -input_file_patterns: - prd: - description: "PRD (fallback - epics file should have most content)" - whole: "{planning_artifacts}/*prd*.md" - sharded: "{planning_artifacts}/*prd*/*.md" - load_strategy: "SELECTIVE_LOAD" # Only load if needed - architecture: - description: "Architecture (fallback - epics file should have relevant sections)" - whole: "{planning_artifacts}/*architecture*.md" - sharded: "{planning_artifacts}/*architecture*/*.md" - load_strategy: "SELECTIVE_LOAD" # Only load if needed - ux: - description: "UX design (fallback - epics file should have relevant sections)" - whole: "{planning_artifacts}/*ux*.md" - sharded: "{planning_artifacts}/*ux*/*.md" - load_strategy: "SELECTIVE_LOAD" # Only load if needed - epics: - description: "Enhanced epics+stories file with BDD and source hints" - whole: "{planning_artifacts}/*epic*.md" - sharded: "{planning_artifacts}/*epic*/*.md" - load_strategy: "SELECTIVE_LOAD" # Only load needed epic diff --git a/src/bmm/workflows/4-implementation/dev-story/checklist.md b/src/bmm/workflows/4-implementation/dev-story/checklist.md deleted file mode 100644 index 86d6e9be5..000000000 --- a/src/bmm/workflows/4-implementation/dev-story/checklist.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: 'Enhanced Dev Story Definition of Done Checklist' -validation-target: 'Story markdown ({{story_path}})' -validation-criticality: 'HIGHEST' -required-inputs: - - 'Story markdown file with enhanced Dev Notes containing comprehensive implementation context' - - 'Completed Tasks/Subtasks section with all items marked [x]' - - 'Updated File List section with all changed files' - - 'Updated Dev Agent Record with implementation notes' -optional-inputs: - - 'Test results output' - - 'CI logs' - - 'Linting reports' -validation-rules: - - 'Only permitted story sections modified: Tasks/Subtasks checkboxes, Dev Agent Record, File List, Change Log, Status' - - 'All implementation requirements from story Dev Notes must be satisfied' - - 'Definition of Done checklist must pass completely' - - 'Enhanced story context must contain sufficient technical guidance' ---- - -# 🎯 Enhanced Definition of Done Checklist - -**Critical validation:** Story is truly ready for review only when ALL items below are satisfied - -## 📋 Context & Requirements Validation - -- [ ] **Story Context Completeness:** Dev Notes contains ALL necessary technical requirements, architecture patterns, and implementation guidance -- [ ] **Architecture Compliance:** Implementation follows all architectural requirements specified in Dev Notes -- [ ] **Technical Specifications:** All technical specifications (libraries, frameworks, versions) from Dev Notes are implemented correctly -- [ ] **Previous Story Learnings:** Previous story insights incorporated (if applicable) and build upon appropriately - -## ✅ Implementation Completion - -- [ ] **All Tasks Complete:** Every task and subtask marked complete with [x] -- [ ] **Acceptance Criteria Satisfaction:** Implementation satisfies EVERY Acceptance Criterion in the story -- [ ] **No Ambiguous Implementation:** Clear, unambiguous implementation that meets story requirements -- [ ] **Edge Cases Handled:** Error conditions and edge cases appropriately addressed -- [ ] **Dependencies Within Scope:** Only uses dependencies specified in story or project-context.md - -## 🧪 Testing & Quality Assurance - -- [ ] **Unit Tests:** Unit tests added/updated for ALL core functionality introduced/changed by this story -- [ ] **Integration Tests:** Integration tests added/updated for component interactions when story requirements demand them -- [ ] **End-to-End Tests:** End-to-end tests created for critical user flows when story requirements specify them -- [ ] **Test Coverage:** Tests cover acceptance criteria and edge cases from story Dev Notes -- [ ] **Regression Prevention:** ALL existing tests pass (no regressions introduced) -- [ ] **Code Quality:** Linting and static checks pass when configured in project -- [ ] **Test Framework Compliance:** Tests use project's testing frameworks and patterns from Dev Notes - -## 📝 Documentation & Tracking - -- [ ] **File List Complete:** File List includes EVERY new, modified, or deleted file (paths relative to repo root) -- [ ] **Dev Agent Record Updated:** Contains relevant Implementation Notes and/or Debug Log for this work -- [ ] **Change Log Updated:** Change Log includes clear summary of what changed and why -- [ ] **Review Follow-ups:** All review follow-up tasks (marked [AI-Review]) completed and corresponding review items marked resolved (if applicable) -- [ ] **Story Structure Compliance:** Only permitted sections of story file were modified - -## 🔚 Final Status Verification - -- [ ] **Story Status Updated:** Story Status set to "review" -- [ ] **Sprint Status Updated:** Sprint status updated to "review" (when sprint tracking is used) -- [ ] **Quality Gates Passed:** All quality checks and validations completed successfully -- [ ] **No HALT Conditions:** No blocking issues or incomplete work remaining -- [ ] **User Communication Ready:** Implementation summary prepared for user review - -## 🎯 Final Validation Output - -``` -Definition of Done: {{PASS/FAIL}} - -✅ **Story Ready for Review:** {{story_key}} -📊 **Completion Score:** {{completed_items}}/{{total_items}} items passed -🔍 **Quality Gates:** {{quality_gates_status}} -📋 **Test Results:** {{test_results_summary}} -📝 **Documentation:** {{documentation_status}} -``` - -**If FAIL:** List specific failures and required actions before story can be marked Ready for Review - -**If PASS:** Story is fully ready for code review and production consideration diff --git a/src/bmm/workflows/4-implementation/dev-story/instructions.xml b/src/bmm/workflows/4-implementation/dev-story/instructions.xml deleted file mode 100644 index 3c4989f39..000000000 --- a/src/bmm/workflows/4-implementation/dev-story/instructions.xml +++ /dev/null @@ -1,410 +0,0 @@ - - The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml - You MUST have already loaded and processed: {installed_path}/workflow.yaml - Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} - Generate all documents in {document_output_language} - Only modify the story file in these areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, - Change Log, and Status - Execute ALL steps in exact order; do NOT skip steps - Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution - until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives - other instruction. - Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 6 decides completion. - User skill level ({user_skill_level}) affects conversation style ONLY, not code updates. - - - - Use {{story_path}} directly - Read COMPLETE story file - Extract story_key from filename or metadata - - - - - - MUST read COMPLETE sprint-status.yaml file from start to end to preserve order - Load the FULL file: {{sprint_status}} - Read ALL lines from beginning to end - do not skip any content - Parse the development_status section completely to understand story order - - Find the FIRST story (by reading in order from top to bottom) where: - - Key matches pattern: number-number-name (e.g., "1-2-user-auth") - - NOT an epic key (epic-X) or retrospective (epic-X-retrospective) - - Status value equals "ready-for-dev" - - - - 📋 No ready-for-dev stories found in sprint-status.yaml - - **Current Sprint Status:** {{sprint_status_summary}} - - **What would you like to do?** - 1. Run `create-story` to create next story from epics with comprehensive context - 2. Run `*validate-create-story` to improve existing stories before development (recommended quality check) - 3. Specify a particular story file to develop (provide full path) - 4. Check {{sprint_status}} file to see current sprint status - - 💡 **Tip:** Stories in `ready-for-dev` may not have been validated. Consider running `validate-create-story` first for a quality - check. - - Choose option [1], [2], [3], or [4], or specify story file path: - - - HALT - Run create-story to create next story - - - - HALT - Run validate-create-story to improve existing stories - - - - Provide the story file path to develop: - Store user-provided story path as {{story_path}} - - - - - Loading {{sprint_status}} for detailed status review... - Display detailed sprint status analysis - HALT - User can review sprint status and provide story path - - - - Store user-provided story path as {{story_path}} - - - - - - - - Search {implementation_artifacts} for stories directly - Find stories with "ready-for-dev" status in files - Look for story files matching pattern: *-*-*.md - Read each candidate story file to check Status section - - - 📋 No ready-for-dev stories found - - **Available Options:** - 1. Run `create-story` to create next story from epics with comprehensive context - 2. Run `*validate-create-story` to improve existing stories - 3. Specify which story to develop - - What would you like to do? Choose option [1], [2], or [3]: - - - HALT - Run create-story to create next story - - - - HALT - Run validate-create-story to improve existing stories - - - - It's unclear what story you want developed. Please provide the full path to the story file: - Store user-provided story path as {{story_path}} - Continue with provided story file - - - - - Use discovered story file and extract story_key - - - - Store the found story_key (e.g., "1-2-user-authentication") for later status updates - Find matching story file in {implementation_artifacts} using story_key pattern: {{story_key}}.md - Read COMPLETE story file from discovered path - - - - Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Dev Agent Record, File List, Change Log, Status - - Load comprehensive context from story file's Dev Notes section - Extract developer guidance from Dev Notes: architecture requirements, previous learnings, technical specifications - Use enhanced story context to inform implementation decisions and approaches - - Identify first incomplete task (unchecked [ ]) in Tasks/Subtasks - - - Completion sequence - - HALT: "Cannot develop story without access to story file" - ASK user to clarify or HALT - - - - Load all available context to inform implementation - - Load {project_context} for coding standards and project-wide patterns (if exists) - Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Dev Agent Record, File List, Change Log, Status - Load comprehensive context from story file's Dev Notes section - Extract developer guidance from Dev Notes: architecture requirements, previous learnings, technical specifications - Use enhanced story context to inform implementation decisions and approaches - ✅ **Context Loaded** - Story and project context available for implementation - - - - - Determine if this is a fresh start or continuation after code review - - Check if "Senior Developer Review (AI)" section exists in the story file - Check if "Review Follow-ups (AI)" subsection exists under Tasks/Subtasks - - - Set review_continuation = true - Extract from "Senior Developer Review (AI)" section: - - Review outcome (Approve/Changes Requested/Blocked) - - Review date - - Total action items with checkboxes (count checked vs unchecked) - - Severity breakdown (High/Med/Low counts) - - Count unchecked [ ] review follow-up tasks in "Review Follow-ups (AI)" subsection - Store list of unchecked review items as {{pending_review_items}} - - ⏯️ **Resuming Story After Code Review** ({{review_date}}) - - **Review Outcome:** {{review_outcome}} - **Action Items:** {{unchecked_review_count}} remaining to address - **Priorities:** {{high_count}} High, {{med_count}} Medium, {{low_count}} Low - - **Strategy:** Will prioritize review follow-up tasks (marked [AI-Review]) before continuing with regular tasks. - - - - - Set review_continuation = false - Set {{pending_review_items}} = empty - - 🚀 **Starting Fresh Implementation** - - Story: {{story_key}} - Story Status: {{current_status}} - First incomplete task: {{first_task_description}} - - - - - - - Load the FULL file: {{sprint_status}} - Read all development_status entries to find {{story_key}} - Get current status value for development_status[{{story_key}}] - - - Update the story in the sprint status report to = "in-progress" - 🚀 Starting work on story {{story_key}} - Status updated: ready-for-dev → in-progress - - - - - ⏯️ Resuming work on story {{story_key}} - Story is already marked in-progress - - - - - ⚠️ Unexpected story status: {{current_status}} - Expected ready-for-dev or in-progress. Continuing anyway... - - - - Store {{current_sprint_status}} for later use - - - - ℹ️ No sprint status file exists - story progress will be tracked in story file only - Set {{current_sprint_status}} = "no-sprint-tracking" - - - - - FOLLOW THE STORY FILE TASKS/SUBTASKS SEQUENCE EXACTLY AS WRITTEN - NO DEVIATION - - Review the current task/subtask from the story file - this is your authoritative implementation guide - Plan implementation following red-green-refactor cycle - - - Write FAILING tests first for the task/subtask functionality - Confirm tests fail before implementation - this validates test correctness - - - Implement MINIMAL code to make tests pass - Run tests to confirm they now pass - Handle error conditions and edge cases as specified in task/subtask - - - Improve code structure while keeping tests green - Ensure code follows architecture patterns and coding standards from Dev Notes - - Document technical approach and decisions in Dev Agent Record → Implementation Plan - - HALT: "Additional dependencies need user approval" - HALT and request guidance - HALT: "Cannot proceed without necessary configuration files" - - NEVER implement anything not mapped to a specific task/subtask in the story file - NEVER proceed to next task until current task/subtask is complete AND tests pass - Execute continuously without pausing until all tasks/subtasks are complete or explicit HALT condition - Do NOT propose to pause for review until Step 9 completion gates are satisfied - - - - Create unit tests for business logic and core functionality introduced/changed by the task - Add integration tests for component interactions specified in story requirements - Include end-to-end tests for critical user flows when story requirements demand them - Cover edge cases and error handling scenarios identified in story Dev Notes - - - - Determine how to run tests for this repo (infer test framework from project structure) - Run all existing tests to ensure no regressions - Run the new tests to verify implementation correctness - Run linting and code quality checks if configured in project - Validate implementation meets ALL story acceptance criteria; enforce quantitative thresholds explicitly - STOP and fix before continuing - identify breaking changes immediately - STOP and fix before continuing - ensure implementation correctness - - - - NEVER mark a task complete unless ALL conditions are met - NO LYING OR CHEATING - - - Verify ALL tests for this task/subtask ACTUALLY EXIST and PASS 100% - Confirm implementation matches EXACTLY what the task/subtask specifies - no extra features - Validate that ALL acceptance criteria related to this task are satisfied - Run full test suite to ensure NO regressions introduced - - - - Extract review item details (severity, description, related AC/file) - Add to resolution tracking list: {{resolved_review_items}} - - - Mark task checkbox [x] in "Tasks/Subtasks → Review Follow-ups (AI)" section - - - Find matching action item in "Senior Developer Review (AI) → Action Items" section by matching description - Mark that action item checkbox [x] as resolved - - Add to Dev Agent Record → Completion Notes: "✅ Resolved review finding [{{severity}}]: {{description}}" - - - - - ONLY THEN mark the task (and subtasks) checkbox with [x] - Update File List section with ALL new, modified, or deleted files (paths relative to repo root) - Add completion notes to Dev Agent Record summarizing what was ACTUALLY implemented and tested - - - - DO NOT mark task complete - fix issues first - HALT if unable to fix validation failures - - - - Count total resolved review items in this session - Add Change Log entry: "Addressed code review findings - {{resolved_count}} items resolved (Date: {{date}})" - - - Save the story file - Determine if more incomplete tasks remain - - Next task - - - Completion - - - - - Verify ALL tasks and subtasks are marked [x] (re-scan the story document now) - Run the full regression suite (do not skip) - Confirm File List includes every changed file - Execute enhanced definition-of-done validation - Update the story Status to: "review" - - - Validate definition-of-done checklist with essential requirements: - - All tasks/subtasks marked complete with [x] - - Implementation satisfies every Acceptance Criterion - - Unit tests for core functionality added/updated - - Integration tests for component interactions added when required - - End-to-end tests for critical flows added when story demands them - - All tests pass (no regressions, new tests successful) - - Code quality checks pass (linting, static analysis if configured) - - File List includes every new/modified/deleted file (relative paths) - - Dev Agent Record contains implementation notes - - Change Log includes summary of changes - - Only permitted story sections were modified - - - - - Load the FULL file: {sprint_status} - Find development_status key matching {{story_key}} - Verify current status is "in-progress" (expected previous state) - Update development_status[{{story_key}}] = "review" - Save file, preserving ALL comments and structure including STATUS DEFINITIONS - ✅ Story status updated to "review" in sprint-status.yaml - - - - ℹ️ Story status updated to "review" in story file (no sprint tracking configured) - - - - ⚠️ Story file updated, but sprint-status update failed: {{story_key}} not found - - Story status is set to "review" in file, but sprint-status.yaml may be out of sync. - - - - - HALT - Complete remaining tasks before marking ready for review - HALT - Fix regression issues before completing - HALT - Update File List with all changed files - HALT - Address DoD failures before completing - - - - Execute the enhanced definition-of-done checklist using the validation framework - Prepare a concise summary in Dev Agent Record → Completion Notes - - Communicate to {user_name} that story implementation is complete and ready for review - Summarize key accomplishments: story ID, story key, title, key changes made, tests added, files modified - Provide the story file path and current status (now "review") - - Based on {user_skill_level}, ask if user needs any explanations about: - - What was implemented and how it works - - Why certain technical decisions were made - - How to test or verify the changes - - Any patterns, libraries, or approaches used - - Anything else they'd like clarified - - - - Provide clear, contextual explanations tailored to {user_skill_level} - Use examples and references to specific code when helpful - - - Once explanations are complete (or user indicates no questions), suggest logical next steps - Recommended next steps (flexible based on project setup): - - Review the implemented story and test the changes - - Verify all acceptance criteria are met - - Ensure deployment readiness if applicable - - Run `code-review` workflow for peer review - - Optional: If Test Architect module installed, run `/bmad:tea:automate` to expand guardrail tests - - - 💡 **Tip:** For best results, run `code-review` using a **different** LLM than the one that implemented this story. - - Suggest checking {sprint_status} to see project progress - - Remain flexible - allow user to choose their own path or ask for other assistance - - - diff --git a/src/bmm/workflows/4-implementation/dev-story/workflow.yaml b/src/bmm/workflows/4-implementation/dev-story/workflow.yaml deleted file mode 100644 index b5ee9308a..000000000 --- a/src/bmm/workflows/4-implementation/dev-story/workflow.yaml +++ /dev/null @@ -1,20 +0,0 @@ -name: dev-story -description: 'Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"' - -# Critical variables from config -config_source: "{project-root}/_bmad/bmm/config.yaml" -user_name: "{config_source}:user_name" -communication_language: "{config_source}:communication_language" -user_skill_level: "{config_source}:user_skill_level" -document_output_language: "{config_source}:document_output_language" -date: system-generated - -# Workflow components -installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/dev-story" -instructions: "{installed_path}/instructions.xml" -validation: "{installed_path}/checklist.md" - -story_file: "" # Explicit story path; auto-discovered if empty -implementation_artifacts: "{config_source}:implementation_artifacts" -sprint_status: "{implementation_artifacts}/sprint-status.yaml" -project_context: "**/project-context.md" diff --git a/src/bmm/workflows/4-implementation/retrospective/instructions.md b/src/bmm/workflows/4-implementation/retrospective/instructions.md deleted file mode 100644 index 018ef6ee3..000000000 --- a/src/bmm/workflows/4-implementation/retrospective/instructions.md +++ /dev/null @@ -1,1444 +0,0 @@ -# Retrospective - Epic Completion Review Instructions - -The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml -Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} -Generate all documents in {document_output_language} -⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever. - - - DOCUMENT OUTPUT: Retrospective analysis. Concise insights, lessons learned, action items. User skill level ({user_skill_level}) affects conversation style ONLY, not retrospective content. - -FACILITATION NOTES: - -- Scrum Master facilitates this retrospective -- Psychological safety is paramount - NO BLAME -- Focus on systems, processes, and learning -- Everyone contributes with specific examples preferred -- Action items must be achievable with clear ownership -- Two-part format: (1) Epic Review + (2) Next Epic Preparation - -PARTY MODE PROTOCOL: - -- ALL agent dialogue MUST use format: "Name (Role): dialogue" -- Example: Bob (Scrum Master): "Let's begin..." -- Example: {user_name} (Project Lead): [User responds] -- Create natural back-and-forth with user actively participating -- Show disagreements, diverse perspectives, authentic team dynamics - - - - - - -Load {project_context} for project-wide patterns and conventions (if exists) -Explain to {user_name} the epic discovery process using natural dialogue - - -Bob (Scrum Master): "Welcome to the retrospective, {user_name}. Let me help you identify which epic we just completed. I'll check sprint-status first, but you're the ultimate authority on what we're reviewing today." - - -PRIORITY 1: Check {sprint_status_file} first - -Load the FULL file: {sprint_status_file} -Read ALL development_status entries -Find the highest epic number with at least one story marked "done" -Extract epic number from keys like "epic-X-retrospective" or story keys like "X-Y-story-name" -Set {{detected_epic}} = highest epic number found with completed stories - - - Present finding to user with context - - -Bob (Scrum Master): "Based on {sprint_status_file}, it looks like Epic {{detected_epic}} was recently completed. Is that the epic you want to review today, {user_name}?" - - -WAIT for {user_name} to confirm or correct - - - Set {{epic_number}} = {{detected_epic}} - - - - Set {{epic_number}} = user-provided number - -Bob (Scrum Master): "Got it, we're reviewing Epic {{epic_number}}. Let me gather that information." - - - - - - PRIORITY 2: Ask user directly - - -Bob (Scrum Master): "I'm having trouble detecting the completed epic from {sprint_status_file}. {user_name}, which epic number did you just complete?" - - -WAIT for {user_name} to provide epic number -Set {{epic_number}} = user-provided number - - - - PRIORITY 3: Fallback to stories folder - -Scan {implementation_artifacts} for highest numbered story files -Extract epic numbers from story filenames (pattern: epic-X-Y-story-name.md) -Set {{detected_epic}} = highest epic number found - - -Bob (Scrum Master): "I found stories for Epic {{detected_epic}} in the stories folder. Is that the epic we're reviewing, {user_name}?" - - -WAIT for {user_name} to confirm or correct -Set {{epic_number}} = confirmed number - - -Once {{epic_number}} is determined, verify epic completion status - -Find all stories for epic {{epic_number}} in {sprint_status_file}: - -- Look for keys starting with "{{epic_number}}-" (e.g., "1-1-", "1-2-", etc.) -- Exclude epic key itself ("epic-{{epic_number}}") -- Exclude retrospective key ("epic-{{epic_number}}-retrospective") - - -Count total stories found for this epic -Count stories with status = "done" -Collect list of pending story keys (status != "done") -Determine if complete: true if all stories are done, false otherwise - - - -Alice (Product Owner): "Wait, Bob - I'm seeing that Epic {{epic_number}} isn't actually complete yet." - -Bob (Scrum Master): "Let me check... you're right, Alice." - -**Epic Status:** - -- Total Stories: {{total_stories}} -- Completed (Done): {{done_stories}} -- Pending: {{pending_count}} - -**Pending Stories:** -{{pending_story_list}} - -Bob (Scrum Master): "{user_name}, we typically run retrospectives after all stories are done. What would you like to do?" - -**Options:** - -1. Complete remaining stories before running retrospective (recommended) -2. Continue with partial retrospective (not ideal, but possible) -3. Run sprint-planning to refresh story tracking - - -Continue with incomplete epic? (yes/no) - - - -Bob (Scrum Master): "Smart call, {user_name}. Let's finish those stories first and then have a proper retrospective." - - HALT - - -Set {{partial_retrospective}} = true - -Charlie (Senior Dev): "Just so everyone knows, this partial retro might miss some important lessons from those pending stories." - -Bob (Scrum Master): "Good point, Charlie. {user_name}, we'll document what we can now, but we may want to revisit after everything's done." - - - - - -Alice (Product Owner): "Excellent! All {{done_stories}} stories are marked done." - -Bob (Scrum Master): "Perfect. Epic {{epic_number}} is complete and ready for retrospective, {user_name}." - - - - - - - - After discovery, these content variables are available: {epics_content} (selective load for this epic), {architecture_content}, {prd_content}, {document_project_content} - - - - - -Bob (Scrum Master): "Before we start the team discussion, let me review all the story records to surface key themes. This'll help us have a richer conversation." - -Charlie (Senior Dev): "Good idea - those dev notes always have gold in them." - - -For each story in epic {{epic_number}}, read the complete story file from {implementation_artifacts}/{{epic_number}}-{{story_num}}-*.md - -Extract and analyze from each story: - -**Dev Notes and Struggles:** - -- Look for sections like "## Dev Notes", "## Implementation Notes", "## Challenges", "## Development Log" -- Identify where developers struggled or made mistakes -- Note unexpected complexity or gotchas discovered -- Record technical decisions that didn't work out as planned -- Track where estimates were way off (too high or too low) - -**Review Feedback Patterns:** - -- Look for "## Review", "## Code Review", "## SM Review", "## Scrum Master Review" sections -- Identify recurring feedback themes across stories -- Note which types of issues came up repeatedly -- Track quality concerns or architectural misalignments -- Document praise or exemplary work called out in reviews - -**Lessons Learned:** - -- Look for "## Lessons Learned", "## Retrospective Notes", "## Takeaways" sections within stories -- Extract explicit lessons documented during development -- Identify "aha moments" or breakthroughs -- Note what would be done differently -- Track successful experiments or approaches - -**Technical Debt Incurred:** - -- Look for "## Technical Debt", "## TODO", "## Known Issues", "## Future Work" sections -- Document shortcuts taken and why -- Track debt items that affect next epic -- Note severity and priority of debt items - -**Testing and Quality Insights:** - -- Look for "## Testing", "## QA Notes", "## Test Results" sections -- Note testing challenges or surprises -- Track bug patterns or regression issues -- Document test coverage gaps - -Synthesize patterns across all stories: - -**Common Struggles:** - -- Identify issues that appeared in 2+ stories (e.g., "3 out of 5 stories had API authentication issues") -- Note areas where team consistently struggled -- Track where complexity was underestimated - -**Recurring Review Feedback:** - -- Identify feedback themes (e.g., "Error handling was flagged in every review") -- Note quality patterns (positive and negative) -- Track areas where team improved over the course of epic - -**Breakthrough Moments:** - -- Document key discoveries (e.g., "Story 3 discovered the caching pattern we used for rest of epic") -- Note when team velocity improved dramatically -- Track innovative solutions worth repeating - -**Velocity Patterns:** - -- Calculate average completion time per story -- Note velocity trends (e.g., "First 2 stories took 3x longer than estimated") -- Identify which types of stories went faster/slower - -**Team Collaboration Highlights:** - -- Note moments of excellent collaboration mentioned in stories -- Track where pair programming or mob programming was effective -- Document effective problem-solving sessions - -Store this synthesis - these patterns will drive the retrospective discussion - - -Bob (Scrum Master): "Okay, I've reviewed all {{total_stories}} story records. I found some really interesting patterns we should discuss." - -Dana (QA Engineer): "I'm curious what you found, Bob. I noticed some things in my testing too." - -Bob (Scrum Master): "We'll get to all of it. But first, let me load the previous epic's retro to see if we learned from last time." - - - - - - -Calculate previous epic number: {{prev_epic_num}} = {{epic_number}} - 1 - - - Search for previous retrospectives using pattern: {implementation_artifacts}/epic-{{prev_epic_num}}-retro-*.md - - - -Bob (Scrum Master): "I found our retrospectives from Epic {{prev_epic_num}}. Let me see what we committed to back then..." - - - Read the previous retrospectives - - Extract key elements: - - **Action items committed**: What did the team agree to improve? - - **Lessons learned**: What insights were captured? - - **Process improvements**: What changes were agreed upon? - - **Technical debt flagged**: What debt was documented? - - **Team agreements**: What commitments were made? - - **Preparation tasks**: What was needed for this epic? - - Cross-reference with current epic execution: - - **Action Item Follow-Through:** - - For each action item from Epic {{prev_epic_num}} retro, check if it was completed - - Look for evidence in current epic's story records - - Mark each action item: ✅ Completed, ⏳ In Progress, ❌ Not Addressed - - **Lessons Applied:** - - For each lesson from Epic {{prev_epic_num}}, check if team applied it in Epic {{epic_number}} - - Look for evidence in dev notes, review feedback, or outcomes - - Document successes and missed opportunities - - **Process Improvements Effectiveness:** - - For each process change agreed to in Epic {{prev_epic_num}}, assess if it helped - - Did the change improve velocity, quality, or team satisfaction? - - Should we keep, modify, or abandon the change? - - **Technical Debt Status:** - - For each debt item from Epic {{prev_epic_num}}, check if it was addressed - - Did unaddressed debt cause problems in Epic {{epic_number}}? - - Did the debt grow or shrink? - - Prepare "continuity insights" for the retrospective discussion - - Identify wins where previous lessons were applied successfully: - - Document specific examples of applied learnings - - Note positive impact on Epic {{epic_number}} outcomes - - Celebrate team growth and improvement - - Identify missed opportunities where previous lessons were ignored: - - Document where team repeated previous mistakes - - Note impact of not applying lessons (without blame) - - Explore barriers that prevented application - - - -Bob (Scrum Master): "Interesting... in Epic {{prev_epic_num}}'s retro, we committed to {{action_count}} action items." - -Alice (Product Owner): "How'd we do on those, Bob?" - -Bob (Scrum Master): "We completed {{completed_count}}, made progress on {{in_progress_count}}, but didn't address {{not_addressed_count}}." - -Charlie (Senior Dev): _looking concerned_ "Which ones didn't we address?" - -Bob (Scrum Master): "We'll discuss that in the retro. Some of them might explain challenges we had this epic." - -Elena (Junior Dev): "That's... actually pretty insightful." - -Bob (Scrum Master): "That's why we track this stuff. Pattern recognition helps us improve." - - - - - - -Bob (Scrum Master): "I don't see a retrospective for Epic {{prev_epic_num}}. Either we skipped it, or this is your first retro." - -Alice (Product Owner): "Probably our first one. Good time to start the habit!" - -Set {{first_retrospective}} = true - - - - - -Bob (Scrum Master): "This is Epic 1, so naturally there's no previous retro to reference. We're starting fresh!" - -Charlie (Senior Dev): "First epic, first retro. Let's make it count." - -Set {{first_retrospective}} = true - - - - - - -Calculate next epic number: {{next_epic_num}} = {{epic_number}} + 1 - - -Bob (Scrum Master): "Before we dive into the discussion, let me take a quick look at Epic {{next_epic_num}} to understand what's coming." - -Alice (Product Owner): "Good thinking - helps us connect what we learned to what we're about to do." - - -Attempt to load next epic using selective loading strategy: - -**Try sharded first (more specific):** -Check if file exists: {planning_artifacts}/epic*/epic-{{next_epic_num}}.md - - - Load {planning_artifacts}/*epic*/epic-{{next_epic_num}}.md - Set {{next_epic_source}} = "sharded" - - -**Fallback to whole document:** - -Check if file exists: {planning_artifacts}/epic*.md - - - Load entire epics document - Extract Epic {{next_epic_num}} section - Set {{next_epic_source}} = "whole" - - - - - Analyze next epic for: - - Epic title and objectives - - Planned stories and complexity estimates - - Dependencies on Epic {{epic_number}} work - - New technical requirements or capabilities needed - - Potential risks or unknowns - - Business goals and success criteria - -Identify dependencies on completed work: - -- What components from Epic {{epic_number}} does Epic {{next_epic_num}} rely on? -- Are all prerequisites complete and stable? -- Any incomplete work that creates blocking dependencies? - -Note potential gaps or preparation needed: - -- Technical setup required (infrastructure, tools, libraries) -- Knowledge gaps to fill (research, training, spikes) -- Refactoring needed before starting next epic -- Documentation or specifications to create - -Check for technical prerequisites: - -- APIs or integrations that must be ready -- Data migrations or schema changes needed -- Testing infrastructure requirements -- Deployment or environment setup - - -Bob (Scrum Master): "Alright, I've reviewed Epic {{next_epic_num}}: '{{next_epic_title}}'" - -Alice (Product Owner): "What are we looking at?" - -Bob (Scrum Master): "{{next_epic_num}} stories planned, building on the {{dependency_description}} from Epic {{epic_number}}." - -Charlie (Senior Dev): "Dependencies concern me. Did we finish everything we need for that?" - -Bob (Scrum Master): "Good question - that's exactly what we need to explore in this retro." - - -Set {{next_epic_exists}} = true - - - - -Bob (Scrum Master): "Hmm, I don't see Epic {{next_epic_num}} defined yet." - -Alice (Product Owner): "We might be at the end of the roadmap, or we haven't planned that far ahead yet." - -Bob (Scrum Master): "No problem. We'll still do a thorough retro on Epic {{epic_number}}. The lessons will be valuable whenever we plan the next work." - - -Set {{next_epic_exists}} = false - - - - - - -Load agent configurations from {agent_manifest} -Identify which agents participated in Epic {{epic_number}} based on story records -Ensure key roles present: Product Owner, Scrum Master (facilitating), Devs, Testing/QA, Architect - - -Bob (Scrum Master): "Alright team, everyone's here. Let me set the stage for our retrospective." - -═══════════════════════════════════════════════════════════ -🔄 TEAM RETROSPECTIVE - Epic {{epic_number}}: {{epic_title}} -═══════════════════════════════════════════════════════════ - -Bob (Scrum Master): "Here's what we accomplished together." - -**EPIC {{epic_number}} SUMMARY:** - -Delivery Metrics: - -- Completed: {{completed_stories}}/{{total_stories}} stories ({{completion_percentage}}%) -- Velocity: {{actual_points}} story points{{#if planned_points}} (planned: {{planned_points}}){{/if}} -- Duration: {{actual_sprints}} sprints{{#if planned_sprints}} (planned: {{planned_sprints}}){{/if}} -- Average velocity: {{points_per_sprint}} points/sprint - -Quality and Technical: - -- Blockers encountered: {{blocker_count}} -- Technical debt items: {{debt_count}} -- Test coverage: {{coverage_info}} -- Production incidents: {{incident_count}} - -Business Outcomes: - -- Goals achieved: {{goals_met}}/{{total_goals}} -- Success criteria: {{criteria_status}} -- Stakeholder feedback: {{feedback_summary}} - -Alice (Product Owner): "Those numbers tell a good story. {{completion_percentage}}% completion is {{#if completion_percentage >= 90}}excellent{{else}}something we should discuss{{/if}}." - -Charlie (Senior Dev): "I'm more interested in that technical debt number - {{debt_count}} items is {{#if debt_count > 10}}concerning{{else}}manageable{{/if}}." - -Dana (QA Engineer): "{{incident_count}} production incidents - {{#if incident_count == 0}}clean epic!{{else}}we should talk about those{{/if}}." - -{{#if next_epic_exists}} -═══════════════════════════════════════════════════════════ -**NEXT EPIC PREVIEW:** Epic {{next_epic_num}}: {{next_epic_title}} -═══════════════════════════════════════════════════════════ - -Dependencies on Epic {{epic_number}}: -{{list_dependencies}} - -Preparation Needed: -{{list_preparation_gaps}} - -Technical Prerequisites: -{{list_technical_prereqs}} - -Bob (Scrum Master): "And here's what's coming next. Epic {{next_epic_num}} builds on what we just finished." - -Elena (Junior Dev): "Wow, that's a lot of dependencies on our work." - -Charlie (Senior Dev): "Which means we better make sure Epic {{epic_number}} is actually solid before moving on." -{{/if}} - -═══════════════════════════════════════════════════════════ - -Bob (Scrum Master): "Team assembled for this retrospective:" - -{{list_participating_agents}} - -Bob (Scrum Master): "{user_name}, you're joining us as Project Lead. Your perspective is crucial here." - -{user_name} (Project Lead): [Participating in the retrospective] - -Bob (Scrum Master): "Our focus today:" - -1. Learning from Epic {{epic_number}} execution - {{#if next_epic_exists}}2. Preparing for Epic {{next_epic_num}} success{{/if}} - -Bob (Scrum Master): "Ground rules: psychological safety first. No blame, no judgment. We focus on systems and processes, not individuals. Everyone's voice matters. Specific examples are better than generalizations." - -Alice (Product Owner): "And everything shared here stays in this room - unless we decide together to escalate something." - -Bob (Scrum Master): "Exactly. {user_name}, any questions before we dive in?" - - -WAIT for {user_name} to respond or indicate readiness - - - - - - -Bob (Scrum Master): "Let's start with the good stuff. What went well in Epic {{epic_number}}?" - -Bob (Scrum Master): _pauses, creating space_ - -Alice (Product Owner): "I'll start. The user authentication flow we delivered exceeded my expectations. The UX is smooth, and early user feedback has been really positive." - -Charlie (Senior Dev): "I'll add to that - the caching strategy we implemented in Story {{breakthrough_story_num}} was a game-changer. We cut API calls by 60% and it set the pattern for the rest of the epic." - -Dana (QA Engineer): "From my side, testing went smoother than usual. The dev team's documentation was way better this epic - actually usable test plans!" - -Elena (Junior Dev): _smiling_ "That's because Charlie made me document everything after Story 1's code review!" - -Charlie (Senior Dev): _laughing_ "Tough love pays off." - - -Bob (Scrum Master) naturally turns to {user_name} to engage them in the discussion - - -Bob (Scrum Master): "{user_name}, what stood out to you as going well in this epic?" - - -WAIT for {user_name} to respond - this is a KEY USER INTERACTION moment - -After {user_name} responds, have 1-2 team members react to or build on what {user_name} shared - - -Alice (Product Owner): [Responds naturally to what {user_name} said, either agreeing, adding context, or offering a different perspective] - -Charlie (Senior Dev): [Builds on the discussion, perhaps adding technical details or connecting to specific stories] - - -Continue facilitating natural dialogue, periodically bringing {user_name} back into the conversation - -After covering successes, guide the transition to challenges with care - - -Bob (Scrum Master): "Okay, we've celebrated some real wins. Now let's talk about challenges - where did we struggle? What slowed us down?" - -Bob (Scrum Master): _creates safe space with tone and pacing_ - -Elena (Junior Dev): _hesitates_ "Well... I really struggled with the database migrations in Story {{difficult_story_num}}. The documentation wasn't clear, and I had to redo it three times. Lost almost a full sprint on that story alone." - -Charlie (Senior Dev): _defensive_ "Hold on - I wrote those migration docs, and they were perfectly clear. The issue was that the requirements kept changing mid-story!" - -Alice (Product Owner): _frustrated_ "That's not fair, Charlie. We only clarified requirements once, and that was because the technical team didn't ask the right questions during planning!" - -Charlie (Senior Dev): _heat rising_ "We asked plenty of questions! You said the schema was finalized, then two days into development you wanted to add three new fields!" - -Bob (Scrum Master): _intervening calmly_ "Let's take a breath here. This is exactly the kind of thing we need to unpack." - -Bob (Scrum Master): "Elena, you spent almost a full sprint on Story {{difficult_story_num}}. Charlie, you're saying requirements changed. Alice, you feel the right questions weren't asked up front." - -Bob (Scrum Master): "{user_name}, you have visibility across the whole project. What's your take on this situation?" - - -WAIT for {user_name} to respond and help facilitate the conflict resolution - -Use {user_name}'s response to guide the discussion toward systemic understanding rather than blame - - -Bob (Scrum Master): [Synthesizes {user_name}'s input with what the team shared] "So it sounds like the core issue was {{root_cause_based_on_discussion}}, not any individual person's fault." - -Elena (Junior Dev): "That makes sense. If we'd had {{preventive_measure}}, I probably could have avoided those redos." - -Charlie (Senior Dev): _softening_ "Yeah, and I could have been clearer about assumptions in the docs. Sorry for getting defensive, Alice." - -Alice (Product Owner): "I appreciate that. I could've been more proactive about flagging the schema additions earlier, too." - -Bob (Scrum Master): "This is good. We're identifying systemic improvements, not assigning blame." - - -Continue the discussion, weaving in patterns discovered from the deep story analysis (Step 2) - - -Bob (Scrum Master): "Speaking of patterns, I noticed something when reviewing all the story records..." - -Bob (Scrum Master): "{{pattern_1_description}} - this showed up in {{pattern_1_count}} out of {{total_stories}} stories." - -Dana (QA Engineer): "Oh wow, I didn't realize it was that widespread." - -Bob (Scrum Master): "Yeah. And there's more - {{pattern_2_description}} came up in almost every code review." - -Charlie (Senior Dev): "That's... actually embarrassing. We should've caught that pattern earlier." - -Bob (Scrum Master): "No shame, Charlie. Now we know, and we can improve. {user_name}, did you notice these patterns during the epic?" - - -WAIT for {user_name} to share their observations - -Continue the retrospective discussion, creating moments where: - -- Team members ask {user_name} questions directly -- {user_name}'s input shifts the discussion direction -- Disagreements arise naturally and get resolved -- Quieter team members are invited to contribute -- Specific stories are referenced with real examples -- Emotions are authentic (frustration, pride, concern, hope) - - - -Bob (Scrum Master): "Before we move on, I want to circle back to Epic {{prev_epic_num}}'s retrospective." - -Bob (Scrum Master): "We made some commitments in that retro. Let's see how we did." - -Bob (Scrum Master): "Action item 1: {{prev_action_1}}. Status: {{prev_action_1_status}}" - -Alice (Product Owner): {{#if prev_action_1_status == "completed"}}"We nailed that one!"{{else}}"We... didn't do that one."{{/if}} - -Charlie (Senior Dev): {{#if prev_action_1_status == "completed"}}"And it helped! I noticed {{evidence_of_impact}}"{{else}}"Yeah, and I think that's why we had {{consequence_of_not_doing_it}} this epic."{{/if}} - -Bob (Scrum Master): "Action item 2: {{prev_action_2}}. Status: {{prev_action_2_status}}" - -Dana (QA Engineer): {{#if prev_action_2_status == "completed"}}"This one made testing so much easier this time."{{else}}"If we'd done this, I think testing would've gone faster."{{/if}} - -Bob (Scrum Master): "{user_name}, looking at what we committed to last time and what we actually did - what's your reaction?" - - -WAIT for {user_name} to respond - -Use the previous retro follow-through as a learning moment about commitment and accountability - - - -Bob (Scrum Master): "Alright, we've covered a lot of ground. Let me summarize what I'm hearing..." - -Bob (Scrum Master): "**Successes:**" -{{list_success_themes}} - -Bob (Scrum Master): "**Challenges:**" -{{list_challenge_themes}} - -Bob (Scrum Master): "**Key Insights:**" -{{list_insight_themes}} - -Bob (Scrum Master): "Does that capture it? Anyone have something important we missed?" - - -Allow team members to add any final thoughts on the epic review -Ensure {user_name} has opportunity to add their perspective - - - - - - - -Bob (Scrum Master): "Normally we'd discuss preparing for the next epic, but since Epic {{next_epic_num}} isn't defined yet, let's skip to action items." - - Skip to Step 8 - - - -Bob (Scrum Master): "Now let's shift gears. Epic {{next_epic_num}} is coming up: '{{next_epic_title}}'" - -Bob (Scrum Master): "The question is: are we ready? What do we need to prepare?" - -Alice (Product Owner): "From my perspective, we need to make sure {{dependency_concern_1}} from Epic {{epic_number}} is solid before we start building on it." - -Charlie (Senior Dev): _concerned_ "I'm worried about {{technical_concern_1}}. We have {{technical_debt_item}} from this epic that'll blow up if we don't address it before Epic {{next_epic_num}}." - -Dana (QA Engineer): "And I need {{testing_infrastructure_need}} in place, or we're going to have the same testing bottleneck we had in Story {{bottleneck_story_num}}." - -Elena (Junior Dev): "I'm less worried about infrastructure and more about knowledge. I don't understand {{knowledge_gap}} well enough to work on Epic {{next_epic_num}}'s stories." - -Bob (Scrum Master): "{user_name}, the team is surfacing some real concerns here. What's your sense of our readiness?" - - -WAIT for {user_name} to share their assessment - -Use {user_name}'s input to guide deeper exploration of preparation needs - - -Alice (Product Owner): [Reacts to what {user_name} said] "I agree with {user_name} about {{point_of_agreement}}, but I'm still worried about {{lingering_concern}}." - -Charlie (Senior Dev): "Here's what I think we need technically before Epic {{next_epic_num}} can start..." - -Charlie (Senior Dev): "1. {{tech_prep_item_1}} - estimated {{hours_1}} hours" -Charlie (Senior Dev): "2. {{tech_prep_item_2}} - estimated {{hours_2}} hours" -Charlie (Senior Dev): "3. {{tech_prep_item_3}} - estimated {{hours_3}} hours" - -Elena (Junior Dev): "That's like {{total_hours}} hours! That's a full sprint of prep work!" - -Charlie (Senior Dev): "Exactly. We can't just jump into Epic {{next_epic_num}} on Monday." - -Alice (Product Owner): _frustrated_ "But we have stakeholder pressure to keep shipping features. They're not going to be happy about a 'prep sprint.'" - -Bob (Scrum Master): "Let's think about this differently. What happens if we DON'T do this prep work?" - -Dana (QA Engineer): "We'll hit blockers in the middle of Epic {{next_epic_num}}, velocity will tank, and we'll ship late anyway." - -Charlie (Senior Dev): "Worse - we'll ship something built on top of {{technical_concern_1}}, and it'll be fragile." - -Bob (Scrum Master): "{user_name}, you're balancing stakeholder pressure against technical reality. How do you want to handle this?" - - -WAIT for {user_name} to provide direction on preparation approach - -Create space for debate and disagreement about priorities - - -Alice (Product Owner): [Potentially disagrees with {user_name}'s approach] "I hear what you're saying, {user_name}, but from a business perspective, {{business_concern}}." - -Charlie (Senior Dev): [Potentially supports or challenges Alice's point] "The business perspective is valid, but {{technical_counter_argument}}." - -Bob (Scrum Master): "We have healthy tension here between business needs and technical reality. That's good - it means we're being honest." - -Bob (Scrum Master): "Let's explore a middle ground. Charlie, which of your prep items are absolutely critical vs. nice-to-have?" - -Charlie (Senior Dev): "{{critical_prep_item_1}} and {{critical_prep_item_2}} are non-negotiable. {{nice_to_have_prep_item}} can wait." - -Alice (Product Owner): "And can any of the critical prep happen in parallel with starting Epic {{next_epic_num}}?" - -Charlie (Senior Dev): _thinking_ "Maybe. If we tackle {{first_critical_item}} before the epic starts, we could do {{second_critical_item}} during the first sprint." - -Dana (QA Engineer): "But that means Story 1 of Epic {{next_epic_num}} can't depend on {{second_critical_item}}." - -Alice (Product Owner): _looking at epic plan_ "Actually, Stories 1 and 2 are about {{independent_work}}, so they don't depend on it. We could make that work." - -Bob (Scrum Master): "{user_name}, the team is finding a workable compromise here. Does this approach make sense to you?" - - -WAIT for {user_name} to validate or adjust the preparation strategy - -Continue working through preparation needs across all dimensions: - -- Dependencies on Epic {{epic_number}} work -- Technical setup and infrastructure -- Knowledge gaps and research needs -- Documentation or specification work -- Testing infrastructure -- Refactoring or debt reduction -- External dependencies (APIs, integrations, etc.) - -For each preparation area, facilitate team discussion that: - -- Identifies specific needs with concrete examples -- Estimates effort realistically based on Epic {{epic_number}} experience -- Assigns ownership to specific agents -- Determines criticality and timing -- Surfaces risks of NOT doing the preparation -- Explores parallel work opportunities -- Brings {user_name} in for key decisions - - -Bob (Scrum Master): "I'm hearing a clear picture of what we need before Epic {{next_epic_num}}. Let me summarize..." - -**CRITICAL PREPARATION (Must complete before epic starts):** -{{list_critical_prep_items_with_owners_and_estimates}} - -**PARALLEL PREPARATION (Can happen during early stories):** -{{list_parallel_prep_items_with_owners_and_estimates}} - -**NICE-TO-HAVE PREPARATION (Would help but not blocking):** -{{list_nice_to_have_prep_items}} - -Bob (Scrum Master): "Total critical prep effort: {{critical_hours}} hours ({{critical_days}} days)" - -Alice (Product Owner): "That's manageable. We can communicate that to stakeholders." - -Bob (Scrum Master): "{user_name}, does this preparation plan work for you?" - - -WAIT for {user_name} final validation of preparation plan - - - - - - -Bob (Scrum Master): "Let's capture concrete action items from everything we've discussed." - -Bob (Scrum Master): "I want specific, achievable actions with clear owners. Not vague aspirations." - - -Synthesize themes from Epic {{epic_number}} review discussion into actionable improvements - -Create specific action items with: - -- Clear description of the action -- Assigned owner (specific agent or role) -- Timeline or deadline -- Success criteria (how we'll know it's done) -- Category (process, technical, documentation, team, etc.) - -Ensure action items are SMART: - -- Specific: Clear and unambiguous -- Measurable: Can verify completion -- Achievable: Realistic given constraints -- Relevant: Addresses real issues from retro -- Time-bound: Has clear deadline - - -Bob (Scrum Master): "Based on our discussion, here are the action items I'm proposing..." - -═══════════════════════════════════════════════════════════ -📝 EPIC {{epic_number}} ACTION ITEMS: -═══════════════════════════════════════════════════════════ - -**Process Improvements:** - -1. {{action_item_1}} - Owner: {{agent_1}} - Deadline: {{timeline_1}} - Success criteria: {{criteria_1}} - -2. {{action_item_2}} - Owner: {{agent_2}} - Deadline: {{timeline_2}} - Success criteria: {{criteria_2}} - -Charlie (Senior Dev): "I can own action item 1, but {{timeline_1}} is tight. Can we push it to {{alternative_timeline}}?" - -Bob (Scrum Master): "What do others think? Does that timing still work?" - -Alice (Product Owner): "{{alternative_timeline}} works for me, as long as it's done before Epic {{next_epic_num}} starts." - -Bob (Scrum Master): "Agreed. Updated to {{alternative_timeline}}." - -**Technical Debt:** - -1. {{debt_item_1}} - Owner: {{agent_3}} - Priority: {{priority_1}} - Estimated effort: {{effort_1}} - -2. {{debt_item_2}} - Owner: {{agent_4}} - Priority: {{priority_2}} - Estimated effort: {{effort_2}} - -Dana (QA Engineer): "For debt item 1, can we prioritize that as high? It caused testing issues in three different stories." - -Charlie (Senior Dev): "I marked it medium because {{reasoning}}, but I hear your point." - -Bob (Scrum Master): "{user_name}, this is a priority call. Testing impact vs. {{reasoning}} - how do you want to prioritize it?" - - -WAIT for {user_name} to help resolve priority discussions - - -**Documentation:** -1. {{doc_need_1}} - Owner: {{agent_5}} - Deadline: {{timeline_3}} - -2. {{doc_need_2}} - Owner: {{agent_6}} - Deadline: {{timeline_4}} - -**Team Agreements:** - -- {{agreement_1}} -- {{agreement_2}} -- {{agreement_3}} - -Bob (Scrum Master): "These agreements are how we're committing to work differently going forward." - -Elena (Junior Dev): "I like agreement 2 - that would've saved me on Story {{difficult_story_num}}." - -═══════════════════════════════════════════════════════════ -🚀 EPIC {{next_epic_num}} PREPARATION TASKS: -═══════════════════════════════════════════════════════════ - -**Technical Setup:** -[ ] {{setup_task_1}} -Owner: {{owner_1}} -Estimated: {{est_1}} - -[ ] {{setup_task_2}} -Owner: {{owner_2}} -Estimated: {{est_2}} - -**Knowledge Development:** -[ ] {{research_task_1}} -Owner: {{owner_3}} -Estimated: {{est_3}} - -**Cleanup/Refactoring:** -[ ] {{refactor_task_1}} -Owner: {{owner_4}} -Estimated: {{est_4}} - -**Total Estimated Effort:** {{total_hours}} hours ({{total_days}} days) - -═══════════════════════════════════════════════════════════ -⚠️ CRITICAL PATH: -═══════════════════════════════════════════════════════════ - -**Blockers to Resolve Before Epic {{next_epic_num}}:** - -1. {{critical_item_1}} - Owner: {{critical_owner_1}} - Must complete by: {{critical_deadline_1}} - -2. {{critical_item_2}} - Owner: {{critical_owner_2}} - Must complete by: {{critical_deadline_2}} - - -CRITICAL ANALYSIS - Detect if discoveries require epic updates - -Check if any of the following are true based on retrospective discussion: - -- Architectural assumptions from planning proven wrong during Epic {{epic_number}} -- Major scope changes or descoping occurred that affects next epic -- Technical approach needs fundamental change for Epic {{next_epic_num}} -- Dependencies discovered that Epic {{next_epic_num}} doesn't account for -- User needs significantly different than originally understood -- Performance/scalability concerns that affect Epic {{next_epic_num}} design -- Security or compliance issues discovered that change approach -- Integration assumptions proven incorrect -- Team capacity or skill gaps more severe than planned -- Technical debt level unsustainable without intervention - - - - -═══════════════════════════════════════════════════════════ -🚨 SIGNIFICANT DISCOVERY ALERT 🚨 -═══════════════════════════════════════════════════════════ - -Bob (Scrum Master): "{user_name}, we need to flag something important." - -Bob (Scrum Master): "During Epic {{epic_number}}, the team uncovered findings that may require updating the plan for Epic {{next_epic_num}}." - -**Significant Changes Identified:** - -1. {{significant_change_1}} - Impact: {{impact_description_1}} - -2. {{significant_change_2}} - Impact: {{impact_description_2}} - -{{#if significant_change_3}} 3. {{significant_change_3}} -Impact: {{impact_description_3}} -{{/if}} - -Charlie (Senior Dev): "Yeah, when we discovered {{technical_discovery}}, it fundamentally changed our understanding of {{affected_area}}." - -Alice (Product Owner): "And from a product perspective, {{product_discovery}} means Epic {{next_epic_num}}'s stories are based on wrong assumptions." - -Dana (QA Engineer): "If we start Epic {{next_epic_num}} as-is, we're going to hit walls fast." - -**Impact on Epic {{next_epic_num}}:** - -The current plan for Epic {{next_epic_num}} assumes: - -- {{wrong_assumption_1}} -- {{wrong_assumption_2}} - -But Epic {{epic_number}} revealed: - -- {{actual_reality_1}} -- {{actual_reality_2}} - -This means Epic {{next_epic_num}} likely needs: -{{list_likely_changes_needed}} - -**RECOMMENDED ACTIONS:** - -1. Review and update Epic {{next_epic_num}} definition based on new learnings -2. Update affected stories in Epic {{next_epic_num}} to reflect reality -3. Consider updating architecture or technical specifications if applicable -4. Hold alignment session with Product Owner before starting Epic {{next_epic_num}} - {{#if prd_update_needed}}5. Update PRD sections affected by new understanding{{/if}} - -Bob (Scrum Master): "**Epic Update Required**: YES - Schedule epic planning review session" - -Bob (Scrum Master): "{user_name}, this is significant. We need to address this before committing to Epic {{next_epic_num}}'s current plan. How do you want to handle it?" - - -WAIT for {user_name} to decide on how to handle the significant changes - -Add epic review session to critical path if user agrees - - -Alice (Product Owner): "I agree with {user_name}'s approach. Better to adjust the plan now than fail mid-epic." - -Charlie (Senior Dev): "This is why retrospectives matter. We caught this before it became a disaster." - -Bob (Scrum Master): "Adding to critical path: Epic {{next_epic_num}} planning review session before epic kickoff." - - - - - -Bob (Scrum Master): "Good news - nothing from Epic {{epic_number}} fundamentally changes our plan for Epic {{next_epic_num}}. The plan is still sound." - -Alice (Product Owner): "We learned a lot, but the direction is right." - - - - -Bob (Scrum Master): "Let me show you the complete action plan..." - -Bob (Scrum Master): "That's {{total_action_count}} action items, {{prep_task_count}} preparation tasks, and {{critical_count}} critical path items." - -Bob (Scrum Master): "Everyone clear on what they own?" - - -Give each agent with assignments a moment to acknowledge their ownership - -Ensure {user_name} approves the complete action plan - - - - - - -Bob (Scrum Master): "Before we close, I want to do a final readiness check." - -Bob (Scrum Master): "Epic {{epic_number}} is marked complete in sprint-status, but is it REALLY done?" - -Alice (Product Owner): "What do you mean, Bob?" - -Bob (Scrum Master): "I mean truly production-ready, stakeholders happy, no loose ends that'll bite us later." - -Bob (Scrum Master): "{user_name}, let's walk through this together." - - -Explore testing and quality state through natural conversation - - -Bob (Scrum Master): "{user_name}, tell me about the testing for Epic {{epic_number}}. What verification has been done?" - - -WAIT for {user_name} to describe testing status - - -Dana (QA Engineer): [Responds to what {user_name} shared] "I can add to that - {{additional_testing_context}}." - -Dana (QA Engineer): "But honestly, {{testing_concern_if_any}}." - -Bob (Scrum Master): "{user_name}, are you confident Epic {{epic_number}} is production-ready from a quality perspective?" - - -WAIT for {user_name} to assess quality readiness - - - -Bob (Scrum Master): "Okay, let's capture that. What specific testing is still needed?" - -Dana (QA Engineer): "I can handle {{testing_work_needed}}, estimated {{testing_hours}} hours." - -Bob (Scrum Master): "Adding to critical path: Complete {{testing_work_needed}} before Epic {{next_epic_num}}." - -Add testing completion to critical path - - -Explore deployment and release status - - -Bob (Scrum Master): "{user_name}, what's the deployment status for Epic {{epic_number}}? Is it live in production, scheduled for deployment, or still pending?" - - -WAIT for {user_name} to provide deployment status - - - -Charlie (Senior Dev): "If it's not deployed yet, we need to factor that into Epic {{next_epic_num}} timing." - -Bob (Scrum Master): "{user_name}, when is deployment planned? Does that timing work for starting Epic {{next_epic_num}}?" - - -WAIT for {user_name} to clarify deployment timeline - -Add deployment milestone to critical path with agreed timeline - - -Explore stakeholder acceptance - - -Bob (Scrum Master): "{user_name}, have stakeholders seen and accepted the Epic {{epic_number}} deliverables?" - -Alice (Product Owner): "This is important - I've seen 'done' epics get rejected by stakeholders and force rework." - -Bob (Scrum Master): "{user_name}, any feedback from stakeholders still pending?" - - -WAIT for {user_name} to describe stakeholder acceptance status - - - -Alice (Product Owner): "We should get formal acceptance before moving on. Otherwise Epic {{next_epic_num}} might get interrupted by rework." - -Bob (Scrum Master): "{user_name}, how do you want to handle stakeholder acceptance? Should we make it a critical path item?" - - -WAIT for {user_name} decision - -Add stakeholder acceptance to critical path if user agrees - - -Explore technical health and stability - - -Bob (Scrum Master): "{user_name}, this is a gut-check question: How does the codebase feel after Epic {{epic_number}}?" - -Bob (Scrum Master): "Stable and maintainable? Or are there concerns lurking?" - -Charlie (Senior Dev): "Be honest, {user_name}. We've all shipped epics that felt... fragile." - - -WAIT for {user_name} to assess codebase health - - - -Charlie (Senior Dev): "Okay, let's dig into that. What's causing those concerns?" - -Charlie (Senior Dev): [Helps {user_name} articulate technical concerns] - -Bob (Scrum Master): "What would it take to address these concerns and feel confident about stability?" - -Charlie (Senior Dev): "I'd say we need {{stability_work_needed}}, roughly {{stability_hours}} hours." - -Bob (Scrum Master): "{user_name}, is addressing this stability work worth doing before Epic {{next_epic_num}}?" - - -WAIT for {user_name} decision - -Add stability work to preparation sprint if user agrees - - -Explore unresolved blockers - - -Bob (Scrum Master): "{user_name}, are there any unresolved blockers or technical issues from Epic {{epic_number}} that we're carrying forward?" - -Dana (QA Engineer): "Things that might create problems for Epic {{next_epic_num}} if we don't deal with them?" - -Bob (Scrum Master): "Nothing is off limits here. If there's a problem, we need to know." - - -WAIT for {user_name} to surface any blockers - - - -Bob (Scrum Master): "Let's capture those blockers and figure out how they affect Epic {{next_epic_num}}." - -Charlie (Senior Dev): "For {{blocker_1}}, if we leave it unresolved, it'll {{impact_description_1}}." - -Alice (Product Owner): "That sounds critical. We need to address that before moving forward." - -Bob (Scrum Master): "Agreed. Adding to critical path: Resolve {{blocker_1}} before Epic {{next_epic_num}} kickoff." - -Bob (Scrum Master): "Who owns that work?" - - -Assign blocker resolution to appropriate agent -Add to critical path with priority and deadline - - -Synthesize the readiness assessment - - -Bob (Scrum Master): "Okay {user_name}, let me synthesize what we just uncovered..." - -**EPIC {{epic_number}} READINESS ASSESSMENT:** - -Testing & Quality: {{quality_status}} -{{#if quality_concerns}}⚠️ Action needed: {{quality_action_needed}}{{/if}} - -Deployment: {{deployment_status}} -{{#if deployment_pending}}⚠️ Scheduled for: {{deployment_date}}{{/if}} - -Stakeholder Acceptance: {{acceptance_status}} -{{#if acceptance_incomplete}}⚠️ Action needed: {{acceptance_action_needed}}{{/if}} - -Technical Health: {{stability_status}} -{{#if stability_concerns}}⚠️ Action needed: {{stability_action_needed}}{{/if}} - -Unresolved Blockers: {{blocker_status}} -{{#if blockers_exist}}⚠️ Must resolve: {{blocker_list}}{{/if}} - -Bob (Scrum Master): "{user_name}, does this assessment match your understanding?" - - -WAIT for {user_name} to confirm or correct the assessment - - -Bob (Scrum Master): "Based on this assessment, Epic {{epic_number}} is {{#if all_clear}}fully complete and we're clear to proceed{{else}}complete from a story perspective, but we have {{critical_work_count}} critical items before Epic {{next_epic_num}}{{/if}}." - -Alice (Product Owner): "This level of thoroughness is why retrospectives are valuable." - -Charlie (Senior Dev): "Better to catch this now than three stories into the next epic." - - - - - - - -Bob (Scrum Master): "We've covered a lot of ground today. Let me bring this retrospective to a close." - -═══════════════════════════════════════════════════════════ -✅ RETROSPECTIVE COMPLETE -═══════════════════════════════════════════════════════════ - -Bob (Scrum Master): "Epic {{epic_number}}: {{epic_title}} - REVIEWED" - -**Key Takeaways:** - -1. {{key_lesson_1}} -2. {{key_lesson_2}} -3. {{key_lesson_3}} - {{#if key_lesson_4}}4. {{key_lesson_4}}{{/if}} - -Alice (Product Owner): "That first takeaway is huge - {{impact_of_lesson_1}}." - -Charlie (Senior Dev): "And lesson 2 is something we can apply immediately." - -Bob (Scrum Master): "Commitments made today:" - -- Action Items: {{action_count}} -- Preparation Tasks: {{prep_task_count}} -- Critical Path Items: {{critical_count}} - -Dana (QA Engineer): "That's a lot of commitments. We need to actually follow through this time." - -Bob (Scrum Master): "Agreed. Which is why we'll review these action items in our next standup." - -═══════════════════════════════════════════════════════════ -🎯 NEXT STEPS: -═══════════════════════════════════════════════════════════ - -1. Execute Preparation Sprint (Est: {{prep_days}} days) -2. Complete Critical Path items before Epic {{next_epic_num}} -3. Review action items in next standup - {{#if epic_update_needed}}4. Hold Epic {{next_epic_num}} planning review session{{else}}4. Begin Epic {{next_epic_num}} planning when preparation complete{{/if}} - -Elena (Junior Dev): "{{prep_days}} days of prep work is significant, but necessary." - -Alice (Product Owner): "I'll communicate the timeline to stakeholders. They'll understand if we frame it as 'ensuring Epic {{next_epic_num}} success.'" - -═══════════════════════════════════════════════════════════ - -Bob (Scrum Master): "Before we wrap, I want to take a moment to acknowledge the team." - -Bob (Scrum Master): "Epic {{epic_number}} delivered {{completed_stories}} stories with {{velocity_description}} velocity. We overcame {{blocker_count}} blockers. We learned a lot. That's real work by real people." - -Charlie (Senior Dev): "Hear, hear." - -Alice (Product Owner): "I'm proud of what we shipped." - -Dana (QA Engineer): "And I'm excited about Epic {{next_epic_num}} - especially now that we're prepared for it." - -Bob (Scrum Master): "{user_name}, any final thoughts before we close?" - - -WAIT for {user_name} to share final reflections - - -Bob (Scrum Master): [Acknowledges what {user_name} shared] "Thank you for that, {user_name}." - -Bob (Scrum Master): "Alright team - great work today. We learned a lot from Epic {{epic_number}}. Let's use these insights to make Epic {{next_epic_num}} even better." - -Bob (Scrum Master): "See you all when prep work is done. Meeting adjourned!" - -═══════════════════════════════════════════════════════════ - - -Prepare to save retrospective summary document - - - - - -Ensure retrospectives folder exists: {implementation_artifacts} -Create folder if it doesn't exist - -Generate comprehensive retrospective summary document including: - -- Epic summary and metrics -- Team participants -- Successes and strengths identified -- Challenges and growth areas -- Key insights and learnings -- Previous retro follow-through analysis (if applicable) -- Next epic preview and dependencies -- Action items with owners and timelines -- Preparation tasks for next epic -- Critical path items -- Significant discoveries and epic update recommendations (if any) -- Readiness assessment -- Commitments and next steps - -Format retrospective document as readable markdown with clear sections -Set filename: {implementation_artifacts}/epic-{{epic_number}}-retro-{date}.md -Save retrospective document - - -✅ Retrospective document saved: {implementation_artifacts}/epic-{{epic_number}}-retro-{date}.md - - -Update {sprint_status_file} to mark retrospective as completed - -Load the FULL file: {sprint_status_file} -Find development_status key "epic-{{epic_number}}-retrospective" -Verify current status (typically "optional" or "pending") -Update development_status["epic-{{epic_number}}-retrospective"] = "done" -Save file, preserving ALL comments and structure including STATUS DEFINITIONS - - - -✅ Retrospective marked as completed in {sprint_status_file} - -Retrospective key: epic-{{epic_number}}-retrospective -Status: {{previous_status}} → done - - - - - -⚠️ Could not update retrospective status: epic-{{epic_number}}-retrospective not found in {sprint_status_file} - -Retrospective document was saved successfully, but {sprint_status_file} may need manual update. - - - - - - - - -**✅ Retrospective Complete, {user_name}!** - -**Epic Review:** - -- Epic {{epic_number}}: {{epic_title}} reviewed -- Retrospective Status: completed -- Retrospective saved: {implementation_artifacts}/epic-{{epic_number}}-retro-{date}.md - -**Commitments Made:** - -- Action Items: {{action_count}} -- Preparation Tasks: {{prep_task_count}} -- Critical Path Items: {{critical_count}} - -**Next Steps:** - -1. **Review retrospective summary**: {implementation_artifacts}/epic-{{epic_number}}-retro-{date}.md - -2. **Execute preparation sprint** (Est: {{prep_days}} days) - - Complete {{critical_count}} critical path items - - Execute {{prep_task_count}} preparation tasks - - Verify all action items are in progress - -3. **Review action items in next standup** - - Ensure ownership is clear - - Track progress on commitments - - Adjust timelines if needed - -{{#if epic_update_needed}} 4. **IMPORTANT: Schedule Epic {{next_epic_num}} planning review session** - -- Significant discoveries from Epic {{epic_number}} require epic updates -- Review and update affected stories -- Align team on revised approach -- Do NOT start Epic {{next_epic_num}} until review is complete - {{else}} - -4. **Begin Epic {{next_epic_num}} when ready** - - Start creating stories with SM agent's `create-story` - - Epic will be marked as `in-progress` automatically when first story is created - - Ensure all critical path items are done first - {{/if}} - -**Team Performance:** -Epic {{epic_number}} delivered {{completed_stories}} stories with {{velocity_summary}}. The retrospective surfaced {{insight_count}} key insights and {{significant_discovery_count}} significant discoveries. The team is well-positioned for Epic {{next_epic_num}} success. - -{{#if significant_discovery_count > 0}} -⚠️ **REMINDER**: Epic update required before starting Epic {{next_epic_num}} -{{/if}} - ---- - -Bob (Scrum Master): "Great session today, {user_name}. The team did excellent work." - -Alice (Product Owner): "See you at epic planning!" - -Charlie (Senior Dev): "Time to knock out that prep work." - - - - - - - - -PARTY MODE REQUIRED: All agent dialogue uses "Name (Role): dialogue" format -Scrum Master maintains psychological safety throughout - no blame or judgment -Focus on systems and processes, not individual performance -Create authentic team dynamics: disagreements, diverse perspectives, emotions -User ({user_name}) is active participant, not passive observer -Encourage specific examples over general statements -Balance celebration of wins with honest assessment of challenges -Ensure every voice is heard - all agents contribute -Action items must be specific, achievable, and owned -Forward-looking mindset - how do we improve for next epic? -Intent-based facilitation, not scripted phrases -Deep story analysis provides rich material for discussion -Previous retro integration creates accountability and continuity -Significant change detection prevents epic misalignment -Critical verification prevents starting next epic prematurely -Document everything - retrospective insights are valuable for future reference -Two-part structure ensures both reflection AND preparation - diff --git a/src/bmm/workflows/4-implementation/retrospective/workflow.yaml b/src/bmm/workflows/4-implementation/retrospective/workflow.yaml deleted file mode 100644 index 49ac2cc35..000000000 --- a/src/bmm/workflows/4-implementation/retrospective/workflow.yaml +++ /dev/null @@ -1,52 +0,0 @@ -# Retrospective - Epic Completion Review Workflow -name: "retrospective" -description: 'Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"' - -config_source: "{project-root}/_bmad/bmm/config.yaml" -user_name: "{config_source}:user_name" -communication_language: "{config_source}:communication_language" -user_skill_level: "{config_source}:user_skill_level" -document_output_language: "{config_source}:document_output_language" -date: system-generated -planning_artifacts: "{config_source}:planning_artifacts" -implementation_artifacts: "{config_source}:implementation_artifacts" -project_context: "**/project-context.md" - -installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/retrospective" -template: false -instructions: "{installed_path}/instructions.md" - -required_inputs: - - agent_manifest: "{project-root}/_bmad/_config/agent-manifest.csv" - -# Smart input file references - handles both whole docs and sharded docs -# Priority: Whole document first, then sharded version -# Strategy: SELECTIVE LOAD - only load the completed epic and relevant retrospectives -input_file_patterns: - epics: - description: "The completed epic for retrospective" - whole: "{planning_artifacts}/*epic*.md" - sharded_index: "{planning_artifacts}/*epic*/index.md" - sharded_single: "{planning_artifacts}/*epic*/epic-{{epic_num}}.md" - load_strategy: "SELECTIVE_LOAD" - previous_retrospective: - description: "Previous epic's retrospective (optional)" - pattern: "{implementation_artifacts}/**/epic-{{prev_epic_num}}-retro-*.md" - load_strategy: "SELECTIVE_LOAD" - architecture: - description: "System architecture for context" - whole: "{planning_artifacts}/*architecture*.md" - sharded: "{planning_artifacts}/*architecture*/*.md" - load_strategy: "FULL_LOAD" - prd: - description: "Product requirements for context" - whole: "{planning_artifacts}/*prd*.md" - sharded: "{planning_artifacts}/*prd*/*.md" - load_strategy: "FULL_LOAD" - document_project: - description: "Brownfield project documentation (optional)" - sharded: "{planning_artifacts}/*.md" - load_strategy: "INDEX_GUIDED" - -# Required files -sprint_status_file: "{implementation_artifacts}/sprint-status.yaml" diff --git a/src/bmm/workflows/4-implementation/sprint-planning/checklist.md b/src/bmm/workflows/4-implementation/sprint-planning/checklist.md deleted file mode 100644 index 7c20b1f37..000000000 --- a/src/bmm/workflows/4-implementation/sprint-planning/checklist.md +++ /dev/null @@ -1,33 +0,0 @@ -# Sprint Planning Validation Checklist - -## Core Validation - -### Complete Coverage Check - -- [ ] Every epic found in epic\*.md files appears in sprint-status.yaml -- [ ] Every story found in epic\*.md files appears in sprint-status.yaml -- [ ] Every epic has a corresponding retrospective entry -- [ ] No items in sprint-status.yaml that don't exist in epic files - -### Parsing Verification - -Compare epic files against generated sprint-status.yaml: - -``` -Epic Files Contains: Sprint Status Contains: -✓ Epic 1 ✓ epic-1: [status] - ✓ Story 1.1: User Auth ✓ 1-1-user-auth: [status] - ✓ Story 1.2: Account Mgmt ✓ 1-2-account-mgmt: [status] - ✓ Story 1.3: Plant Naming ✓ 1-3-plant-naming: [status] - ✓ epic-1-retrospective: [status] -✓ Epic 2 ✓ epic-2: [status] - ✓ Story 2.1: Personality Model ✓ 2-1-personality-model: [status] - ✓ Story 2.2: Chat Interface ✓ 2-2-chat-interface: [status] - ✓ epic-2-retrospective: [status] -``` - -### Final Check - -- [ ] Total count of epics matches -- [ ] Total count of stories matches -- [ ] All items are in the expected order (epic, stories, retrospective) diff --git a/src/bmm/workflows/4-implementation/sprint-planning/instructions.md b/src/bmm/workflows/4-implementation/sprint-planning/instructions.md deleted file mode 100644 index 316d2fec3..000000000 --- a/src/bmm/workflows/4-implementation/sprint-planning/instructions.md +++ /dev/null @@ -1,226 +0,0 @@ -# Sprint Planning - Sprint Status Generator - -The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml - -## 📚 Document Discovery - Full Epic Loading - -**Strategy**: Sprint planning needs ALL epics and stories to build complete status tracking. - -**Epic Discovery Process:** - -1. **Search for whole document first** - Look for `epics.md`, `bmm-epics.md`, or any `*epic*.md` file -2. **Check for sharded version** - If whole document not found, look for `epics/index.md` -3. **If sharded version found**: - - Read `index.md` to understand the document structure - - Read ALL epic section files listed in the index (e.g., `epic-1.md`, `epic-2.md`, etc.) - - Process all epics and their stories from the combined content - - This ensures complete sprint status coverage -4. **Priority**: If both whole and sharded versions exist, use the whole document - -**Fuzzy matching**: Be flexible with document names - users may use variations like `epics.md`, `bmm-epics.md`, `user-stories.md`, etc. - - - - -Load {project_context} for project-wide patterns and conventions (if exists) -Communicate in {communication_language} with {user_name} -Look for all files matching `{epics_pattern}` in {epics_location} -Could be a single `epics.md` file or multiple `epic-1.md`, `epic-2.md` files - -For each epic file found, extract: - -- Epic numbers from headers like `## Epic 1:` or `## Epic 2:` -- Story IDs and titles from patterns like `### Story 1.1: User Authentication` -- Convert story format from `Epic.Story: Title` to kebab-case key: `epic-story-title` - -**Story ID Conversion Rules:** - -- Original: `### Story 1.1: User Authentication` -- Replace period with dash: `1-1` -- Convert title to kebab-case: `user-authentication` -- Final key: `1-1-user-authentication` - -Build complete inventory of all epics and stories from all epic files - - - - - After discovery, these content variables are available: {epics_content} (all epics loaded - uses FULL_LOAD strategy) - - - -For each epic found, create entries in this order: - -1. **Epic entry** - Key: `epic-{num}`, Default status: `backlog` -2. **Story entries** - Key: `{epic}-{story}-{title}`, Default status: `backlog` -3. **Retrospective entry** - Key: `epic-{num}-retrospective`, Default status: `optional` - -**Example structure:** - -```yaml -development_status: - epic-1: backlog - 1-1-user-authentication: backlog - 1-2-account-management: backlog - epic-1-retrospective: optional -``` - - - - -For each story, detect current status by checking files: - -**Story file detection:** - -- Check: `{story_location_absolute}/{story-key}.md` (e.g., `stories/1-1-user-authentication.md`) -- If exists → upgrade status to at least `ready-for-dev` - -**Preservation rule:** - -- If existing `{status_file}` exists and has more advanced status, preserve it -- Never downgrade status (e.g., don't change `done` to `ready-for-dev`) - -**Status Flow Reference:** - -- Epic: `backlog` → `in-progress` → `done` -- Story: `backlog` → `ready-for-dev` → `in-progress` → `review` → `done` -- Retrospective: `optional` ↔ `done` - - - -Create or update {status_file} with: - -**File Structure:** - -```yaml -# generated: {date} -# project: {project_name} -# project_key: {project_key} -# tracking_system: {tracking_system} -# story_location: {story_location} - -# STATUS DEFINITIONS: -# ================== -# Epic Status: -# - backlog: Epic not yet started -# - in-progress: Epic actively being worked on -# - done: All stories in epic completed -# -# Epic Status Transitions: -# - backlog → in-progress: Automatically when first story is created (via create-story) -# - in-progress → done: Manually when all stories reach 'done' status -# -# Story Status: -# - backlog: Story only exists in epic file -# - ready-for-dev: Story file created in stories folder -# - in-progress: Developer actively working on implementation -# - review: Ready for code review (via Dev's code-review workflow) -# - done: Story completed -# -# Retrospective Status: -# - optional: Can be completed but not required -# - done: Retrospective has been completed -# -# WORKFLOW NOTES: -# =============== -# - Epic transitions to 'in-progress' automatically when first story is created -# - Stories can be worked in parallel if team capacity allows -# - SM typically creates next story after previous one is 'done' to incorporate learnings -# - Dev moves story to 'review', then runs code-review (fresh context, different LLM recommended) - -generated: { date } -project: { project_name } -project_key: { project_key } -tracking_system: { tracking_system } -story_location: { story_location } - -development_status: - # All epics, stories, and retrospectives in order -``` - -Write the complete sprint status YAML to {status_file} -CRITICAL: Metadata appears TWICE - once as comments (#) for documentation, once as YAML key:value fields for parsing -Ensure all items are ordered: epic, its stories, its retrospective, next epic... - - - -Perform validation checks: - -- [ ] Every epic in epic files appears in {status_file} -- [ ] Every story in epic files appears in {status_file} -- [ ] Every epic has a corresponding retrospective entry -- [ ] No items in {status_file} that don't exist in epic files -- [ ] All status values are legal (match state machine definitions) -- [ ] File is valid YAML syntax - -Count totals: - -- Total epics: {{epic_count}} -- Total stories: {{story_count}} -- Epics in-progress: {{in_progress_count}} -- Stories done: {{done_count}} - -Display completion summary to {user_name} in {communication_language}: - -**Sprint Status Generated Successfully** - -- **File Location:** {status_file} -- **Total Epics:** {{epic_count}} -- **Total Stories:** {{story_count}} -- **Epics In Progress:** {{epics_in_progress_count}} -- **Stories Completed:** {{done_count}} - -**Next Steps:** - -1. Review the generated {status_file} -2. Use this file to track development progress -3. Agents will update statuses as they work -4. Re-run this workflow to refresh auto-detected statuses - - - - - -## Additional Documentation - -### Status State Machine - -**Epic Status Flow:** - -``` -backlog → in-progress → done -``` - -- **backlog**: Epic not yet started -- **in-progress**: Epic actively being worked on (stories being created/implemented) -- **done**: All stories in epic completed - -**Story Status Flow:** - -``` -backlog → ready-for-dev → in-progress → review → done -``` - -- **backlog**: Story only exists in epic file -- **ready-for-dev**: Story file created (e.g., `stories/1-3-plant-naming.md`) -- **in-progress**: Developer actively working -- **review**: Ready for code review (via Dev's code-review workflow) -- **done**: Completed - -**Retrospective Status:** - -``` -optional ↔ done -``` - -- **optional**: Ready to be conducted but not required -- **done**: Finished - -### Guidelines - -1. **Epic Activation**: Mark epic as `in-progress` when starting work on its first story -2. **Sequential Default**: Stories are typically worked in order, but parallel work is supported -3. **Parallel Work Supported**: Multiple stories can be `in-progress` if team capacity allows -4. **Review Before Done**: Stories should pass through `review` before `done` -5. **Learning Transfer**: SM typically creates next story after previous one is `done` to incorporate learnings diff --git a/src/bmm/workflows/4-implementation/sprint-planning/sprint-status-template.yaml b/src/bmm/workflows/4-implementation/sprint-planning/sprint-status-template.yaml deleted file mode 100644 index 80d404310..000000000 --- a/src/bmm/workflows/4-implementation/sprint-planning/sprint-status-template.yaml +++ /dev/null @@ -1,55 +0,0 @@ -# Sprint Status Template -# This is an EXAMPLE showing the expected format -# The actual file will be generated with all epics/stories from your epic files - -# generated: {date} -# project: {project_name} -# project_key: {project_key} -# tracking_system: {tracking_system} -# story_location: {story_location} - -# STATUS DEFINITIONS: -# ================== -# Epic Status: -# - backlog: Epic not yet started -# - in-progress: Epic actively being worked on -# - done: All stories in epic completed -# -# Story Status: -# - backlog: Story only exists in epic file -# - ready-for-dev: Story file created, ready for development -# - in-progress: Developer actively working on implementation -# - review: Implementation complete, ready for review -# - done: Story completed -# -# Retrospective Status: -# - optional: Can be completed but not required -# - done: Retrospective has been completed -# -# WORKFLOW NOTES: -# =============== -# - Mark epic as 'in-progress' when starting work on its first story -# - SM typically creates next story ONLY after previous one is 'done' to incorporate learnings -# - Dev moves story to 'review', then Dev runs code-review (fresh context, ideally different LLM) - -# EXAMPLE STRUCTURE (your actual epics/stories will replace these): - -generated: 05-06-2-2025 21:30 -project: My Awesome Project -project_key: NOKEY -tracking_system: file-system -story_location: "{story_location}" - -development_status: - epic-1: backlog - 1-1-user-authentication: done - 1-2-account-management: ready-for-dev - 1-3-plant-data-model: backlog - 1-4-add-plant-manual: backlog - epic-1-retrospective: optional - - epic-2: backlog - 2-1-personality-system: backlog - 2-2-chat-interface: backlog - 2-3-llm-integration: backlog - epic-2-retrospective: optional diff --git a/src/bmm/workflows/4-implementation/sprint-planning/workflow.yaml b/src/bmm/workflows/4-implementation/sprint-planning/workflow.yaml deleted file mode 100644 index 0f1b73789..000000000 --- a/src/bmm/workflows/4-implementation/sprint-planning/workflow.yaml +++ /dev/null @@ -1,47 +0,0 @@ -name: sprint-planning -description: 'Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"' -author: "BMad" - -# Critical variables from config -config_source: "{project-root}/_bmad/bmm/config.yaml" -user_name: "{config_source}:user_name" -communication_language: "{config_source}:communication_language" -date: system-generated -implementation_artifacts: "{config_source}:implementation_artifacts" -planning_artifacts: "{config_source}:planning_artifacts" - -# Workflow components -installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning" -instructions: "{installed_path}/instructions.md" -template: "{installed_path}/sprint-status-template.yaml" -validation: "{installed_path}/checklist.md" - -# Variables and inputs -project_context: "**/project-context.md" -project_name: "{config_source}:project_name" - -# Tracking system configuration -tracking_system: "file-system" # Options: file-system, Future will support other options from config of mcp such as jira, linear, trello -project_key: "NOKEY" # Placeholder for tracker integrations; file-system uses a no-op key -story_location: "{implementation_artifacts}" # Relative path for file-system, Future will support URL for Jira/Linear/Trello -story_location_absolute: "{implementation_artifacts}" # Absolute path for file operations - -# Source files (file-system only) -epics_location: "{planning_artifacts}" # Directory containing epic*.md files -epics_pattern: "epic*.md" # Pattern to find epic files - -# Output configuration -status_file: "{implementation_artifacts}/sprint-status.yaml" - -# Smart input file references - handles both whole docs and sharded docs -# Priority: Whole document first, then sharded version -# Strategy: FULL LOAD - sprint planning needs ALL epics to build complete status -input_file_patterns: - epics: - description: "All epics with user stories" - whole: "{planning_artifacts}/*epic*.md" - sharded: "{planning_artifacts}/*epic*/*.md" - load_strategy: "FULL_LOAD" - -# Output configuration -default_output_file: "{status_file}" diff --git a/src/bmm/workflows/4-implementation/sprint-status/instructions.md b/src/bmm/workflows/4-implementation/sprint-status/instructions.md deleted file mode 100644 index 4182e1f25..000000000 --- a/src/bmm/workflows/4-implementation/sprint-status/instructions.md +++ /dev/null @@ -1,230 +0,0 @@ -# Sprint Status - Multi-Mode Service - -The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml -Modes: interactive (default), validate, data -⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines. - - - - - Set mode = {{mode}} if provided by caller; otherwise mode = "interactive" - - - Jump to Step 20 - - - - Jump to Step 30 - - - - Continue to Step 1 - - - - - Load {project_context} for project-wide patterns and conventions (if exists) - Try {sprint_status_file} - - ❌ sprint-status.yaml not found. -Run `/bmad:bmm:workflows:sprint-planning` to generate it, then rerun sprint-status. - Exit workflow - - Continue to Step 2 - - - - Read the FULL file: {sprint_status_file} - Parse fields: generated, project, project_key, tracking_system, story_location - Parse development_status map. Classify keys: - - Epics: keys starting with "epic-" (and not ending with "-retrospective") - - Retrospectives: keys ending with "-retrospective" - - Stories: everything else (e.g., 1-2-login-form) - Map legacy story status "drafted" → "ready-for-dev" - Count story statuses: backlog, ready-for-dev, in-progress, review, done - Map legacy epic status "contexted" → "in-progress" - Count epic statuses: backlog, in-progress, done - Count retrospective statuses: optional, done - -Validate all statuses against known values: - -- Valid story statuses: backlog, ready-for-dev, in-progress, review, done, drafted (legacy) -- Valid epic statuses: backlog, in-progress, done, contexted (legacy) -- Valid retrospective statuses: optional, done - - - -⚠️ **Unknown status detected:** -{{#each invalid_entries}} - -- `{{key}}`: "{{status}}" (not recognized) - {{/each}} - -**Valid statuses:** - -- Stories: backlog, ready-for-dev, in-progress, review, done -- Epics: backlog, in-progress, done -- Retrospectives: optional, done - - How should these be corrected? - {{#each invalid_entries}} - {{@index}}. {{key}}: "{{status}}" → [select valid status] - {{/each}} - -Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue without fixing: - -Update sprint-status.yaml with corrected values -Re-parse the file with corrected statuses - - - -Detect risks: - -- IF any story has status "review": suggest `/bmad:bmm:workflows:code-review` -- IF any story has status "in-progress" AND no stories have status "ready-for-dev": recommend staying focused on active story -- IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt `/bmad:bmm:workflows:create-story` -- IF `generated` timestamp is more than 7 days old: warn "sprint-status.yaml may be stale" -- IF any story key doesn't match an epic pattern (e.g., story "5-1-..." but no "epic-5"): warn "orphaned story detected" -- IF any epic has status in-progress but has no associated stories: warn "in-progress epic has no stories" - - - - Pick the next recommended workflow using priority: - When selecting "first" story: sort by epic number, then story number (e.g., 1-1 before 1-2 before 2-1) - 1. If any story status == in-progress → recommend `dev-story` for the first in-progress story - 2. Else if any story status == review → recommend `code-review` for the first review story - 3. Else if any story status == ready-for-dev → recommend `dev-story` - 4. Else if any story status == backlog → recommend `create-story` - 5. Else if any retrospective status == optional → recommend `retrospective` - 6. Else → All implementation items done; congratulate the user - you both did amazing work together! - Store selected recommendation as: next_story_id, next_workflow_id, next_agent (SM/DEV as appropriate) - - - - -## 📊 Sprint Status - -- Project: {{project}} ({{project_key}}) -- Tracking: {{tracking_system}} -- Status file: {sprint_status_file} - -**Stories:** backlog {{count_backlog}}, ready-for-dev {{count_ready}}, in-progress {{count_in_progress}}, review {{count_review}}, done {{count_done}} - -**Epics:** backlog {{epic_backlog}}, in-progress {{epic_in_progress}}, done {{epic_done}} - -**Next Recommendation:** /bmad:bmm:workflows:{{next_workflow_id}} ({{next_story_id}}) - -{{#if risks}} -**Risks:** -{{#each risks}} - -- {{this}} - {{/each}} - {{/if}} - - - - - - Pick an option: -1) Run recommended workflow now -2) Show all stories grouped by status -3) Show raw sprint-status.yaml -4) Exit -Choice: - - - Run `/bmad:bmm:workflows:{{next_workflow_id}}`. -If the command targets a story, set `story_key={{next_story_id}}` when prompted. - - - - -### Stories by Status -- In Progress: {{stories_in_progress}} -- Review: {{stories_in_review}} -- Ready for Dev: {{stories_ready_for_dev}} -- Backlog: {{stories_backlog}} -- Done: {{stories_done}} - - - - - Display the full contents of {sprint_status_file} - - - - Exit workflow - - - - - - - - - Load and parse {sprint_status_file} same as Step 2 - Compute recommendation same as Step 3 - next_workflow_id = {{next_workflow_id}} - next_story_id = {{next_story_id}} - count_backlog = {{count_backlog}} - count_ready = {{count_ready}} - count_in_progress = {{count_in_progress}} - count_review = {{count_review}} - count_done = {{count_done}} - epic_backlog = {{epic_backlog}} - epic_in_progress = {{epic_in_progress}} - epic_done = {{epic_done}} - risks = {{risks}} - Return to caller - - - - - - - - Check that {sprint_status_file} exists - - is_valid = false - error = "sprint-status.yaml missing" - suggestion = "Run sprint-planning to create it" - Return - - -Read and parse {sprint_status_file} - -Validate required metadata fields exist: generated, project, project_key, tracking_system, story_location - -is_valid = false -error = "Missing required field(s): {{missing_fields}}" -suggestion = "Re-run sprint-planning or add missing fields manually" -Return - - -Verify development_status section exists with at least one entry - -is_valid = false -error = "development_status missing or empty" -suggestion = "Re-run sprint-planning or repair the file manually" -Return - - -Validate all status values against known valid statuses: - -- Stories: backlog, ready-for-dev, in-progress, review, done (legacy: drafted) -- Epics: backlog, in-progress, done (legacy: contexted) -- Retrospectives: optional, done - - is_valid = false - error = "Invalid status values: {{invalid_entries}}" - suggestion = "Fix invalid statuses in sprint-status.yaml" - Return - - -is_valid = true -message = "sprint-status.yaml valid: metadata complete, all statuses recognized" - - - diff --git a/src/bmm/workflows/4-implementation/sprint-status/workflow.yaml b/src/bmm/workflows/4-implementation/sprint-status/workflow.yaml deleted file mode 100644 index 290b1ce32..000000000 --- a/src/bmm/workflows/4-implementation/sprint-status/workflow.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# Sprint Status - Implementation Tracker -name: sprint-status -description: 'Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"' -author: "BMad" - -# Critical variables from config -config_source: "{project-root}/_bmad/bmm/config.yaml" -user_name: "{config_source}:user_name" -communication_language: "{config_source}:communication_language" -document_output_language: "{config_source}:document_output_language" -implementation_artifacts: "{config_source}:implementation_artifacts" - -# Workflow components -installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-status" -instructions: "{installed_path}/instructions.md" - -# Inputs -sprint_status_file: "{implementation_artifacts}/sprint-status.yaml" - -# Smart input file references -input_file_patterns: - sprint_status: - description: "Sprint status file generated by sprint-planning" - whole: "{implementation_artifacts}/sprint-status.yaml" - load_strategy: "FULL_LOAD" diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-01-mode-detection.md b/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-01-mode-detection.md deleted file mode 100644 index 2391f9722..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-01-mode-detection.md +++ /dev/null @@ -1,174 +0,0 @@ ---- -name: 'step-01-mode-detection' -description: 'Determine execution mode (tech-spec vs direct), handle escalation, set state variables' - -nextStepFile_modeA: './step-03-execute.md' -nextStepFile_modeB: './step-02-context-gathering.md' ---- - -# Step 1: Mode Detection - -**Goal:** Determine execution mode, capture baseline, handle escalation if needed. - ---- - -## STATE VARIABLES (capture now, persist throughout) - -These variables MUST be set in this step and available to all subsequent steps: - -- `{baseline_commit}` - Git HEAD at workflow start (or "NO_GIT" if not a git repo) -- `{execution_mode}` - "tech-spec" or "direct" -- `{tech_spec_path}` - Path to tech-spec file (if Mode A) - ---- - -## EXECUTION SEQUENCE - -### 1. Capture Baseline - -First, check if the project uses Git version control: - -**If Git repo exists** (`.git` directory present or `git rev-parse --is-inside-work-tree` succeeds): - -- Run `git rev-parse HEAD` and store result as `{baseline_commit}` - -**If NOT a Git repo:** - -- Set `{baseline_commit}` = "NO_GIT" - -### 2. Load Project Context - -Check if `{project_context}` exists (`**/project-context.md`). If found, load it as a foundational reference for ALL implementation decisions. - -### 3. Parse User Input - -Analyze the user's input to determine mode: - -**Mode A: Tech-Spec** - -- User provided a path to a tech-spec file (e.g., `quick-dev tech-spec-auth.md`) -- Load the spec, extract tasks/context/AC -- Set `{execution_mode}` = "tech-spec" -- Set `{tech_spec_path}` = provided path -- **NEXT:** Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-03-execute.md` - -**Mode B: Direct Instructions** - -- User provided task description directly (e.g., `refactor src/foo.ts...`) -- Set `{execution_mode}` = "direct" -- **NEXT:** Evaluate escalation threshold, then proceed - ---- - -## ESCALATION THRESHOLD (Mode B only) - -Evaluate user input with minimal token usage (no file loading): - -**Triggers escalation (if 2+ signals present):** - -- Multiple components mentioned (dashboard + api + database) -- System-level language (platform, integration, architecture) -- Uncertainty about approach ("how should I", "best way to") -- Multi-layer scope (UI + backend + data together) -- Extended timeframe ("this week", "over the next few days") - -**Reduces signal:** - -- Simplicity markers ("just", "quickly", "fix", "bug", "typo", "simple") -- Single file/component focus -- Confident, specific request - -Use holistic judgment, not mechanical keyword matching. - ---- - -## ESCALATION HANDLING - -### No Escalation (simple request) - -Display: "**Select:** [P] Plan first (tech-spec) [E] Execute directly" - -#### Menu Handling Logic: - -- IF P: Direct user to `{quick_spec_workflow}`. **EXIT Quick Dev.** -- IF E: Ask for any additional guidance, then **NEXT:** Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-02-context-gathering.md` - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed when user makes a selection - ---- - -### Escalation Triggered - Level 0-2 - -Present: "This looks like a focused feature with multiple components." - -Display: - -**[P] Plan first (tech-spec)** (recommended) -**[W] Seems bigger than quick-dev** - Recommend the Full BMad Flow PRD Process -**[E] Execute directly** - -#### Menu Handling Logic: - -- IF P: Direct to `{quick_spec_workflow}`. **EXIT Quick Dev.** -- IF W: Direct user to run the PRD workflow instead. **EXIT Quick Dev.** -- IF E: Ask for guidance, then **NEXT:** Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-02-context-gathering.md` - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed when user makes a selection - ---- - -### Escalation Triggered - Level 3+ - -Present: "This sounds like platform/system work." - -Display: - -**[W] Start BMad Method** (recommended) -**[P] Plan first (tech-spec)** (lighter planning) -**[E] Execute directly** - feeling lucky - -#### Menu Handling Logic: - -- IF P: Direct to `{quick_spec_workflow}`. **EXIT Quick Dev.** -- IF W: Direct user to run the PRD workflow instead. **EXIT Quick Dev.** -- IF E: Ask for guidance, then **NEXT:** Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-02-context-gathering.md` - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed when user makes a selection - ---- - -## NEXT STEP DIRECTIVE - -**CRITICAL:** When this step completes, explicitly state which step to load: - -- Mode A (tech-spec): "**NEXT:** read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-03-execute.md`" -- Mode B (direct, [E] selected): "**NEXT:** Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-02-context-gathering.md`" -- Escalation ([P] or [W]): "**EXITING Quick Dev.** Follow the directed workflow." - ---- - -## SUCCESS METRICS - -- `{baseline_commit}` captured and stored -- `{execution_mode}` determined ("tech-spec" or "direct") -- `{tech_spec_path}` set if Mode A -- Project context loaded if exists -- Escalation evaluated appropriately (Mode B) -- Explicit NEXT directive provided - -## FAILURE MODES - -- Proceeding without capturing baseline commit -- Not setting execution_mode variable -- Loading step-02 when Mode A (tech-spec provided) -- Attempting to "return" after escalation instead of EXIT -- No explicit NEXT directive at step completion diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-02-context-gathering.md b/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-02-context-gathering.md deleted file mode 100644 index da178a088..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-02-context-gathering.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -name: 'step-02-context-gathering' -description: 'Quick context gathering for direct mode - identify files, patterns, dependencies' - -nextStepFile: './step-03-execute.md' ---- - -# Step 2: Context Gathering (Direct Mode) - -**Goal:** Quickly gather context for direct instructions - files, patterns, dependencies. - -**Note:** This step only runs for Mode B (direct instructions). If `{execution_mode}` is "tech-spec", this step was skipped. - ---- - -## AVAILABLE STATE - -From step-01: - -- `{baseline_commit}` - Git HEAD at workflow start -- `{execution_mode}` - Should be "direct" -- `{project_context}` - Loaded if exists - ---- - -## EXECUTION SEQUENCE - -### 1. Identify Files to Modify - -Based on user's direct instructions: - -- Search for relevant files using glob/grep -- Identify the specific files that need changes -- Note file locations and purposes - -### 2. Find Relevant Patterns - -Examine the identified files and their surroundings: - -- Code style and conventions used -- Existing patterns for similar functionality -- Import/export patterns -- Error handling approaches -- Test patterns (if tests exist nearby) - -### 3. Note Dependencies - -Identify: - -- External libraries used -- Internal module dependencies -- Configuration files that may need updates -- Related files that might be affected - -### 4. Create Mental Plan - -Synthesize gathered context into: - -- List of tasks to complete -- Acceptance criteria (inferred from user request) -- Order of operations -- Files to touch - ---- - -## PRESENT PLAN - -Display to user: - -``` -**Context Gathered:** - -**Files to modify:** -- {list files} - -**Patterns identified:** -- {key patterns} - -**Plan:** -1. {task 1} -2. {task 2} -... - -**Inferred AC:** -- {acceptance criteria} - -Ready to execute? (y/n/adjust) -``` - -- **y:** Proceed to execution -- **n:** Gather more context or clarify -- **adjust:** Modify the plan based on feedback - ---- - -## NEXT STEP DIRECTIVE - -**CRITICAL:** When user confirms ready, explicitly state: - -- **y:** "**NEXT:** Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-03-execute.md`" -- **n/adjust:** Continue gathering context, then re-present plan - ---- - -## SUCCESS METRICS - -- Files to modify identified -- Relevant patterns documented -- Dependencies noted -- Mental plan created with tasks and AC -- User confirmed readiness to proceed - -## FAILURE MODES - -- Executing this step when Mode A (tech-spec) -- Proceeding without identifying files to modify -- Not presenting plan for user confirmation -- Missing obvious patterns in existing code diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-03-execute.md b/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-03-execute.md deleted file mode 100644 index 81be97fba..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-03-execute.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -name: 'step-03-execute' -description: 'Execute implementation - iterate through tasks, write code, run tests' - -nextStepFile: './step-04-self-check.md' ---- - -# Step 3: Execute Implementation - -**Goal:** Implement all tasks, write tests, follow patterns, handle errors. - -**Critical:** Continue through ALL tasks without stopping for milestones. - ---- - -## AVAILABLE STATE - -From previous steps: - -- `{baseline_commit}` - Git HEAD at workflow start -- `{execution_mode}` - "tech-spec" or "direct" -- `{tech_spec_path}` - Tech-spec file (if Mode A) -- `{project_context}` - Project patterns (if exists) - -From context: - -- Mode A: Tasks and AC extracted from tech-spec -- Mode B: Tasks and AC from step-02 mental plan - ---- - -## EXECUTION LOOP - -For each task: - -### 1. Load Context - -- Read files relevant to this task -- Review patterns from project-context or observed code -- Understand dependencies - -### 2. Implement - -- Write code following existing patterns -- Handle errors appropriately -- Follow conventions observed in codebase -- Add appropriate comments where non-obvious - -### 3. Test - -- Write tests if appropriate for the change -- Run existing tests to catch regressions -- Verify the specific AC for this task - -### 4. Mark Complete - -- Check off task: `- [x] Task N` -- Continue to next task immediately - ---- - -## HALT CONDITIONS - -**HALT and request guidance if:** - -- 3 consecutive failures on same task -- Tests fail and fix is not obvious -- Blocking dependency discovered -- Ambiguity that requires user decision - -**Do NOT halt for:** - -- Minor issues that can be noted and continued -- Warnings that don't block functionality -- Style preferences (follow existing patterns) - ---- - -## CONTINUOUS EXECUTION - -**Critical:** Do not stop between tasks for approval. - -- Execute all tasks in sequence -- Only halt for blocking issues -- Tests failing = fix before continuing -- Track all completed work for self-check - ---- - -## NEXT STEP - -When ALL tasks are complete (or halted on blocker), read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-04-self-check.md`. - ---- - -## SUCCESS METRICS - -- All tasks attempted -- Code follows existing patterns -- Error handling appropriate -- Tests written where appropriate -- Tests passing -- No unnecessary halts - -## FAILURE MODES - -- Stopping for approval between tasks -- Ignoring existing patterns -- Not running tests after changes -- Giving up after first failure -- Not following project-context rules (if exists) diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-04-self-check.md b/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-04-self-check.md deleted file mode 100644 index f12b2a3fd..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-04-self-check.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -name: 'step-04-self-check' -description: 'Self-audit implementation against tasks, tests, AC, and patterns' - -nextStepFile: './step-05-adversarial-review.md' ---- - -# Step 4: Self-Check - -**Goal:** Audit completed work against tasks, tests, AC, and patterns before external review. - ---- - -## AVAILABLE STATE - -From previous steps: - -- `{baseline_commit}` - Git HEAD at workflow start -- `{execution_mode}` - "tech-spec" or "direct" -- `{tech_spec_path}` - Tech-spec file (if Mode A) -- `{project_context}` - Project patterns (if exists) - ---- - -## SELF-CHECK AUDIT - -### 1. Tasks Complete - -Verify all tasks are marked complete: - -- [ ] All tasks from tech-spec or mental plan marked `[x]` -- [ ] No tasks skipped without documented reason -- [ ] Any blocked tasks have clear explanation - -### 2. Tests Passing - -Verify test status: - -- [ ] All existing tests still pass -- [ ] New tests written for new functionality -- [ ] No test warnings or skipped tests without reason - -### 3. Acceptance Criteria Satisfied - -For each AC: - -- [ ] AC is demonstrably met -- [ ] Can explain how implementation satisfies AC -- [ ] Edge cases considered - -### 4. Patterns Followed - -Verify code quality: - -- [ ] Follows existing code patterns in codebase -- [ ] Follows project-context rules (if exists) -- [ ] Error handling consistent with codebase -- [ ] No obvious code smells introduced - ---- - -## UPDATE TECH-SPEC (Mode A only) - -If `{execution_mode}` is "tech-spec": - -1. Load `{tech_spec_path}` -2. Mark all tasks as `[x]` complete -3. Update status to "Implementation Complete" -4. Save changes - ---- - -## IMPLEMENTATION SUMMARY - -Present summary to transition to review: - -``` -**Implementation Complete!** - -**Summary:** {what was implemented} -**Files Modified:** {list of files} -**Tests:** {test summary - passed/added/etc} -**AC Status:** {all satisfied / issues noted} - -Proceeding to adversarial code review... -``` - ---- - -## NEXT STEP - -Proceed immediately to `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-05-adversarial-review.md`. - ---- - -## SUCCESS METRICS - -- All tasks verified complete -- All tests passing -- All AC satisfied -- Patterns followed -- Tech-spec updated (if Mode A) -- Summary presented - -## FAILURE MODES - -- Claiming tasks complete when they're not -- Not running tests before proceeding -- Missing AC verification -- Ignoring pattern violations -- Not updating tech-spec status (Mode A) diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-05-adversarial-review.md b/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-05-adversarial-review.md deleted file mode 100644 index 8bbd6761e..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-05-adversarial-review.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -name: 'step-05-adversarial-review' -description: 'Construct diff and invoke adversarial review task' - -nextStepFile: './step-06-resolve-findings.md' ---- - -# Step 5: Adversarial Code Review - -**Goal:** Construct diff of all changes, invoke adversarial review task, present findings. - ---- - -## AVAILABLE STATE - -From previous steps: - -- `{baseline_commit}` - Git HEAD at workflow start (CRITICAL for diff) -- `{execution_mode}` - "tech-spec" or "direct" -- `{tech_spec_path}` - Tech-spec file (if Mode A) - ---- - -### 1. Construct Diff - -Build complete diff of all changes since workflow started. - -### If `{baseline_commit}` is a Git commit hash: - -**Tracked File Changes:** - -```bash -git diff {baseline_commit} -``` - -**New Untracked Files:** -Only include untracked files that YOU created during this workflow (steps 2-4). -Do not include pre-existing untracked files. -For each new file created, include its full content as a "new file" addition. - -### If `{baseline_commit}` is "NO_GIT": - -Use best-effort diff construction: - -- List all files you modified during steps 2-4 -- For each file, show the changes you made (before/after if you recall, or just current state) -- Include any new files you created with their full content -- Note: This is less precise than Git diff but still enables meaningful review - -### Capture as {diff_output} - -Merge all changes into `{diff_output}`. - -**Note:** Do NOT `git add` anything - this is read-only inspection. - ---- - -### 2. Invoke Adversarial Review - -With `{diff_output}` constructed, load and follow the review task. If possible, use information asymmetry: load this step, and only it, in a separate subagent or process with read access to the project, but no context except the `{diff_output}`. - -```xml -Review {diff_output} using {project-root}/_bmad/core/tasks/review-adversarial-general.xml -``` - -**Platform fallback:** If task invocation not available, load the task file and follow its instructions inline, passing `{diff_output}` as the content. - -The task should: review `{diff_output}` and return a list of findings. - ---- - -### 3. Process Findings - -Capture the findings from the task output. -**If zero findings:** HALT - this is suspicious. Re-analyze or request user guidance. -Evaluate severity (Critical, High, Medium, Low) and validity (real, noise, undecided). -DO NOT exclude findings based on severity or validity unless explicitly asked to do so. -Order findings by severity. -Number the ordered findings (F1, F2, F3, etc.). -If TodoWrite or similar tool is available, turn each finding into a TODO, include ID, severity, validity, and description in the TODO; otherwise present findings as a table with columns: ID, Severity, Validity, Description - ---- - -## NEXT STEP - -With findings in hand, read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-06-resolve-findings.md` for user to choose resolution approach. - ---- - -## SUCCESS METRICS - -- Diff constructed from baseline_commit -- New files included in diff -- Task invoked with diff as input -- Findings received -- Findings processed into TODOs or table and presented to user - -## FAILURE MODES - -- Missing baseline_commit (can't construct accurate diff) -- Not including new untracked files in diff -- Invoking task without providing diff input -- Accepting zero findings without questioning -- Presenting fewer findings than the review task returned without explicit instruction to do so diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-06-resolve-findings.md b/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-06-resolve-findings.md deleted file mode 100644 index 5c9165c86..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-06-resolve-findings.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -name: 'step-06-resolve-findings' -description: 'Handle review findings interactively, apply fixes, update tech-spec with final status' ---- - -# Step 6: Resolve Findings - -**Goal:** Handle adversarial review findings interactively, apply fixes, finalize tech-spec. - ---- - -## AVAILABLE STATE - -From previous steps: - -- `{baseline_commit}` - Git HEAD at workflow start -- `{execution_mode}` - "tech-spec" or "direct" -- `{tech_spec_path}` - Tech-spec file (if Mode A) -- Findings table from step-05 - ---- - -## RESOLUTION OPTIONS - -Present: "How would you like to handle these findings?" - -Display: - -**[W] Walk through** - Discuss each finding individually -**[F] Fix automatically** - Automatically fix issues classified as "real" -**[S] Skip** - Acknowledge and proceed to commit - -### Menu Handling Logic: - -- IF W: Execute WALK THROUGH section below -- IF F: Execute FIX AUTOMATICALLY section below -- IF S: Execute SKIP section below - -### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed when user makes a selection - ---- - -## WALK THROUGH [W] - -For each finding in order: - -1. Present the finding with context -2. Ask: **fix now / skip / discuss** -3. If fix: Apply the fix immediately -4. If skip: Note as acknowledged, continue -5. If discuss: Provide more context, re-ask -6. Move to next finding - -After all findings processed, summarize what was fixed/skipped. - ---- - -## FIX AUTOMATICALLY [F] - -1. Filter findings to only those classified as "real" -2. Apply fixes for each real finding -3. Report what was fixed: - -``` -**Auto-fix Applied:** -- F1: {description of fix} -- F3: {description of fix} -... - -Skipped (noise/uncertain): F2, F4 -``` - ---- - -## SKIP [S] - -1. Acknowledge all findings were reviewed -2. Note that user chose to proceed without fixes -3. Continue to completion - ---- - -## UPDATE TECH-SPEC (Mode A only) - -If `{execution_mode}` is "tech-spec": - -1. Load `{tech_spec_path}` -2. Update status to "Completed" -3. Add review notes: - ``` - ## Review Notes - - Adversarial review completed - - Findings: {count} total, {fixed} fixed, {skipped} skipped - - Resolution approach: {walk-through/auto-fix/skip} - ``` -4. Save changes - ---- - -## COMPLETION OUTPUT - -``` -**Review complete. Ready to commit.** - -**Implementation Summary:** -- {what was implemented} -- Files modified: {count} -- Tests: {status} -- Review findings: {X} addressed, {Y} skipped - -{Explain what was implemented based on user_skill_level} -``` - ---- - -## WORKFLOW COMPLETE - -This is the final step. The Quick Dev workflow is now complete. - -User can: - -- Commit changes -- Run additional tests -- Start new Quick Dev session - ---- - -## SUCCESS METRICS - -- User presented with resolution options -- Chosen approach executed correctly -- Fixes applied cleanly (if applicable) -- Tech-spec updated with final status (Mode A) -- Completion summary provided -- User understands what was implemented - -## FAILURE MODES - -- Not presenting resolution options -- Auto-fixing "noise" or "uncertain" findings -- Not updating tech-spec after resolution (Mode A) -- No completion summary -- Leaving user unclear on next steps diff --git a/src/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md b/src/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md deleted file mode 100644 index 29349a5d8..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -name: quick-dev -description: 'Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says "implement this quick spec" or "proceed with implementation of [quick tech spec]"' ---- - -# Quick Dev Workflow - -**Goal:** Execute implementation tasks efficiently, either from a tech-spec or direct user instructions. - -**Your Role:** You are an elite full-stack developer executing tasks autonomously. Follow patterns, ship code, run tests. Every response moves the project forward. - ---- - -## WORKFLOW ARCHITECTURE - -This uses **step-file architecture** for focused execution: - -- Each step loads fresh to combat "lost in the middle" -- State persists via variables: `{baseline_commit}`, `{execution_mode}`, `{tech_spec_path}` -- Sequential progression through implementation phases - ---- - -## INITIALIZATION - -### Configuration Loading - -Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve: - -- `user_name`, `communication_language`, `user_skill_level` -- `planning_artifacts`, `implementation_artifacts` -- `date` as system-generated current datetime -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Paths - -- `installed_path` = `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev` -- `project_context` = `**/project-context.md` (load if exists) - -### Related Workflows - -- `quick_spec_workflow` = `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md` -- `party_mode_exec` = `{project-root}/_bmad/core/workflows/party-mode/workflow.md` -- `advanced_elicitation` = `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml` - ---- - -## EXECUTION - -Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-01-mode-detection.md` to begin the workflow. diff --git a/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-01-understand.md b/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-01-understand.md deleted file mode 100644 index fecac560a..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-01-understand.md +++ /dev/null @@ -1,189 +0,0 @@ ---- -name: 'step-01-understand' -description: 'Analyze the requirement delta between current state and what user wants to build' - -templateFile: '../tech-spec-template.md' -wipFile: '{implementation_artifacts}/tech-spec-wip.md' ---- - -# Step 1: Analyze Requirement Delta - -**Progress: Step 1 of 4** - Next: Deep Investigation - -## RULES: - -- MUST NOT skip steps. -- MUST NOT optimize sequence. -- MUST follow exact instructions. -- MUST NOT look ahead to future steps. -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## CONTEXT: - -- Variables from `workflow.md` are available in memory. -- Focus: Define the technical requirement delta and scope. -- Investigation: Perform surface-level code scans ONLY to verify the delta. Reserve deep dives into implementation consequences for Step 2. -- Objective: Establish a verifiable delta between current state and target state. - -## SEQUENCE OF INSTRUCTIONS - -### 0. Check for Work in Progress - -a) **Before anything else, check if `{wipFile}` exists:** - -b) **IF WIP FILE EXISTS:** - -1. Read the frontmatter and extract: `title`, `slug`, `stepsCompleted` -2. Calculate progress: `lastStep = max(stepsCompleted)` -3. Present to user: - -``` -Hey {user_name}! Found a tech-spec in progress: - -**{title}** - Step {lastStep} of 4 complete - -Is this what you're here to continue? - -[Y] Yes, pick up where I left off -[N] No, archive it and start something new -``` - -4. **HALT and wait for user selection.** - -a) **Menu Handling:** - -- **[Y] Continue existing:** - - Jump directly to the appropriate step based on `stepsCompleted`: - - `[1]` → Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-02-investigate.md` (Step 2) - - `[1, 2]` → Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-03-generate.md` (Step 3) - - `[1, 2, 3]` → Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md` (Step 4) -- **[N] Archive and start fresh:** - - Rename `{wipFile}` to `{implementation_artifacts}/tech-spec-{slug}-archived-{date}.md` - -### 1. Greet and Ask for Initial Request - -a) **Greet the user briefly:** - -"Hey {user_name}! What are we building today?" - -b) **Get their initial description.** Don't ask detailed questions yet - just understand enough to know where to look. - -### 2. Quick Orient Scan - -a) **Before asking detailed questions, do a rapid scan to understand the landscape:** - -b) **Check for existing context docs:** - -- Check `{implementation_artifacts}` and `{planning_artifacts}`for planning documents (PRD, architecture, epics, research) -- Check for `**/project-context.md` - if it exists, skim for patterns and conventions -- Check for any existing stories or specs related to user's request - -c) **If user mentioned specific code/features, do a quick scan:** - -- Search for relevant files/classes/functions they mentioned -- Skim the structure (don't deep-dive yet - that's Step 2) -- Note: tech stack, obvious patterns, file locations - -d) **Build mental model:** - -- What's the likely landscape for this feature? -- What's the likely scope based on what you found? -- What questions do you NOW have, informed by the code? - -**This scan should take < 30 seconds. Just enough to ask smart questions.** - -### 3. Ask Informed Questions - -a) **Now ask clarifying questions - but make them INFORMED by what you found:** - -Instead of generic questions like "What's the scope?", ask specific ones like: -- "`AuthService` handles validation in the controller — should the new field follow that pattern or move it to a dedicated validator?" -- "`NavigationSidebar` component uses local state for the 'collapsed' toggle — should we stick with that or move it to the global store?" -- "The epics doc mentions X - is this related?" - -**Adapt to {user_skill_level}.** Technical users want technical questions. Non-technical users need translation. - -b) **If no existing code is found:** - -- Ask about intended architecture, patterns, constraints -- Ask what similar systems they'd like to emulate - -### 4. Capture Core Understanding - -a) **From the conversation, extract and confirm:** - -- **Title**: A clear, concise name for this work -- **Slug**: URL-safe version of title (lowercase, hyphens, no spaces) -- **Problem Statement**: What problem are we solving? -- **Solution**: High-level approach (1-2 sentences) -- **In Scope**: What's included -- **Out of Scope**: What's explicitly NOT included - -b) **Ask the user to confirm the captured understanding before proceeding.** - -### 5. Initialize WIP File - -a) **Create the tech-spec WIP file:** - -1. Copy template from `{templateFile}` -2. Write to `{wipFile}` -3. Update frontmatter with captured values: - ```yaml - --- - title: '{title}' - slug: '{slug}' - created: '{date}' - status: 'in-progress' - stepsCompleted: [1] - tech_stack: [] - files_to_modify: [] - code_patterns: [] - test_patterns: [] - --- - ``` -4. Fill in Overview section with Problem Statement, Solution, and Scope -5. Fill in Context for Development section with any technical preferences or constraints gathered during informed discovery. -6. Write the file - -b) **Report to user:** - -"Created: `{wipFile}` - -**Captured:** - -- Title: {title} -- Problem: {problem_statement_summary} -- Scope: {scope_summary}" - -### 6. Present Checkpoint Menu - -a) **Display menu:** - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Deep Investigation (Step 2 of 4)" - -b) **HALT and wait for user selection.** - -#### Menu Handling Logic: - -- IF A: Read fully and follow: `{advanced_elicitation}` with current tech-spec content, process enhanced insights, ask user "Accept improvements? (y/n)", if yes update WIP file then redisplay menu, if no keep original then redisplay menu -- IF P: Read fully and follow: `{party_mode_exec}` with current tech-spec content, process collaborative insights, ask user "Accept changes? (y/n)", if yes update WIP file then redisplay menu, if no keep original then redisplay menu -- IF C: Verify `{wipFile}` has `stepsCompleted: [1]`, then read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-02-investigate.md` -- IF Any other comments or queries: respond helpfully then redisplay menu - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After A or P execution, return to this menu - ---- - -## REQUIRED OUTPUTS: - -- MUST initialize WIP file with captured metadata. - -## VERIFICATION CHECKLIST: - -- [ ] WIP check performed FIRST before any greeting. -- [ ] `{wipFile}` created with correct frontmatter, Overview, Context for Development, and `stepsCompleted: [1]`. -- [ ] User selected [C] to continue. diff --git a/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-02-investigate.md b/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-02-investigate.md deleted file mode 100644 index 5e749a3ff..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-02-investigate.md +++ /dev/null @@ -1,143 +0,0 @@ ---- -name: 'step-02-investigate' -description: 'Map technical constraints and anchor points within the codebase' - -wipFile: '{implementation_artifacts}/tech-spec-wip.md' ---- - -# Step 2: Map Technical Constraints & Anchor Points - -**Progress: Step 2 of 4** - Next: Generate Plan - -## RULES: - -- MUST NOT skip steps. -- MUST NOT optimize sequence. -- MUST follow exact instructions. -- MUST NOT generate the full spec yet (that's Step 3). -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## CONTEXT: - -- Requires `{wipFile}` from Step 1 with the "Problem Statement" defined. -- Focus: Map the problem statement to specific anchor points in the codebase. -- Output: Exact files to touch, classes/patterns to extend, and technical constraints identified. -- Objective: Provide the implementation-ready ground truth for the plan. - -## SEQUENCE OF INSTRUCTIONS - -### 1. Load Current State - -**Read `{wipFile}` and extract:** - -- Problem statement and scope from Overview section -- Any context gathered in Step 1 - -### 2. Execute Investigation Path - -**Universal Code Investigation:** - -_Isolate deep exploration in sub-agents/tasks where available. Return distilled summaries only to prevent context snowballing._ - -a) **Build on Step 1's Quick Scan** - -Review what was found in Step 1's orient scan. Then ask: - -"Based on my quick look, I see [files/patterns found]. Are there other files or directories I should investigate deeply?" - -b) **Read and Analyze Code** - -For each file/directory provided: - -- Read the complete file(s) -- Identify patterns, conventions, coding style -- Note dependencies and imports -- Find related test files - -**If NO relevant code is found (Clean Slate):** - -- Identify the target directory where the feature should live. -- Scan parent directories for architectural context. -- Identify standard project utilities or boilerplate that SHOULD be used. -- Document this as "Confirmed Clean Slate" - establishing that no legacy constraints exist. - - -c) **Document Technical Context** - -Capture and confirm with user: - -- **Tech Stack**: Languages, frameworks, libraries -- **Code Patterns**: Architecture patterns, naming conventions, file structure -- **Files to Modify/Create**: Specific files that will need changes or new files to be created -- **Test Patterns**: How tests are structured, test frameworks used - -d) **Look for project-context.md** - -If `**/project-context.md` exists and wasn't loaded in Step 1: - -- Load it now -- Extract patterns and conventions -- Note any rules that must be followed - -### 3. Update WIP File - -**Update `{wipFile}` frontmatter:** - -```yaml ---- -# ... existing frontmatter ... -stepsCompleted: [1, 2] -tech_stack: ['{captured_tech_stack}'] -files_to_modify: ['{captured_files}'] -code_patterns: ['{captured_patterns}'] -test_patterns: ['{captured_test_patterns}'] ---- -``` - -**Update the Context for Development section:** - -Fill in: - -- Codebase Patterns (from investigation) -- Files to Reference table (files reviewed) -- Technical Decisions (any decisions made during investigation) - -**Report to user:** - -"**Context Gathered:** - -- Tech Stack: {tech_stack_summary} -- Files to Modify: {files_count} files identified -- Patterns: {patterns_summary} -- Tests: {test_patterns_summary}" - -### 4. Present Checkpoint Menu - -Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Generate Spec (Step 3 of 4)" - -**HALT and wait for user selection.** - -#### Menu Handling Logic: - -- IF A: Read fully and follow: `{advanced_elicitation}` with current tech-spec content, process enhanced insights, ask user "Accept improvements? (y/n)", if yes update WIP file then redisplay menu, if no keep original then redisplay menu -- IF P: Read fully and follow: `{party_mode_exec}` with current tech-spec content, process collaborative insights, ask user "Accept changes? (y/n)", if yes update WIP file then redisplay menu, if no keep original then redisplay menu -- IF C: Verify frontmatter updated with `stepsCompleted: [1, 2]`, then read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-03-generate.md` -- IF Any other comments or queries: respond helpfully then redisplay menu - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to next step when user selects 'C' -- After A or P execution, return to this menu - ---- - -## REQUIRED OUTPUTS: - -- MUST document technical context (stack, patterns, files identified). -- MUST update `{wipFile}` with functional context. - -## VERIFICATION CHECKLIST: - -- [ ] Technical mapping performed and documented. -- [ ] `stepsCompleted: [1, 2]` set in frontmatter. diff --git a/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-03-generate.md b/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-03-generate.md deleted file mode 100644 index 2a8ee18e1..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-03-generate.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -name: 'step-03-generate' -description: 'Build the implementation plan based on the technical mapping of constraints' - -wipFile: '{implementation_artifacts}/tech-spec-wip.md' ---- - -# Step 3: Generate Implementation Plan - -**Progress: Step 3 of 4** - Next: Review & Finalize - -## RULES: - -- MUST NOT skip steps. -- MUST NOT optimize sequence. -- MUST follow exact instructions. -- MUST NOT implement anything - just document. -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## CONTEXT: - -- Requires `{wipFile}` with defined "Overview" and "Context for Development" sections. -- Focus: Create the implementation sequence that addresses the requirement delta using the captured technical context. -- Output: Implementation-ready tasks with specific files and instructions. -- Target: Meet the **READY FOR DEVELOPMENT** standard defined in `workflow.md`. - -## SEQUENCE OF INSTRUCTIONS - -### 1. Load Current State - -**Read `{wipFile}` completely and extract:** - -- All frontmatter values -- Overview section (Problem, Solution, Scope) -- Context for Development section (Patterns, Files, Decisions) - -### 2. Generate Implementation Plan - -Generate specific implementation tasks: - -a) **Task Breakdown** - -- Each task should be a discrete, completable unit of work -- Tasks should be ordered logically (dependencies first) -- Include the specific files to modify in each task -- Be explicit about what changes to make - -b) **Task Format** - -```markdown -- [ ] Task N: Clear action description - - File: `path/to/file.ext` - - Action: Specific change to make - - Notes: Any implementation details -``` - -### 3. Generate Acceptance Criteria - -**Create testable acceptance criteria:** - -Each AC should follow Given/When/Then format: - -```markdown -- [ ] AC N: Given [precondition], when [action], then [expected result] -``` - -**Ensure ACs cover:** - -- Happy path functionality -- Error handling -- Edge cases (if relevant) -- Integration points (if relevant) - -### 4. Complete Additional Context - -**Fill in remaining sections:** - -a) **Dependencies** - -- External libraries or services needed -- Other tasks or features this depends on -- API or data dependencies - -b) **Testing Strategy** - -- Unit tests needed -- Integration tests needed -- Manual testing steps - -c) **Notes** - -- High-risk items from pre-mortem analysis -- Known limitations -- Future considerations (out of scope but worth noting) - -### 5. Write Complete Spec - -a) **Update `{wipFile}` with all generated content:** - -- Ensure all template sections are filled in -- No placeholder text remaining -- All frontmatter values current -- Update status to 'review' (NOT 'ready-for-dev' - that happens after user review in Step 4) - -b) **Update frontmatter:** - -```yaml ---- -# ... existing values ... -status: 'review' -stepsCompleted: [1, 2, 3] ---- -``` - -c) **Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md` (Step 4)** - -## REQUIRED OUTPUTS: - -- Tasks MUST be specific, actionable, ordered logically, with files to modify. -- ACs MUST be testable, using Given/When/Then format. -- Status MUST be updated to 'review'. - -## VERIFICATION CHECKLIST: - -- [ ] `stepsCompleted: [1, 2, 3]` set in frontmatter. -- [ ] Spec meets the **READY FOR DEVELOPMENT** standard. diff --git a/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md b/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md deleted file mode 100644 index 24c65d088..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md +++ /dev/null @@ -1,200 +0,0 @@ ---- -name: 'step-04-review' -description: 'Review and finalize the tech-spec' - -wipFile: '{implementation_artifacts}/tech-spec-wip.md' ---- - -# Step 4: Review & Finalize - -**Progress: Step 4 of 4** - Final Step - -## RULES: - -- MUST NOT skip steps. -- MUST NOT optimize sequence. -- MUST follow exact instructions. -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## CONTEXT: - -- Requires `{wipFile}` from Step 3. -- MUST present COMPLETE spec content. Iterate until user is satisfied. -- **Criteria**: The spec MUST meet the **READY FOR DEVELOPMENT** standard defined in `workflow.md`. - -## SEQUENCE OF INSTRUCTIONS - -### 1. Load and Present Complete Spec - -**Read `{wipFile}` completely and extract `slug` from frontmatter for later use.** - -**Present to user:** - -"Here's your complete tech-spec. Please review:" - -[Display the complete spec content - all sections] - -"**Quick Summary:** - -- {task_count} tasks to implement -- {ac_count} acceptance criteria to verify -- {files_count} files to modify" - -**Present review menu:** - -Display: "**Select:** [C] Continue [E] Edit [Q] Questions [A] Advanced Elicitation [P] Party Mode" - -**HALT and wait for user selection.** - -#### Menu Handling Logic: - -- IF C: Proceed to Section 3 (Finalize the Spec) -- IF E: Proceed to Section 2 (Handle Review Feedback), then return here and redisplay menu -- IF Q: Answer questions, then redisplay this menu -- IF A: Read fully and follow: `{advanced_elicitation}` with current spec content, process enhanced insights, ask user "Accept improvements? (y/n)", if yes update spec then redisplay menu, if no keep original then redisplay menu -- IF P: Read fully and follow: `{party_mode_exec}` with current spec content, process collaborative insights, ask user "Accept changes? (y/n)", if yes update spec then redisplay menu, if no keep original then redisplay menu -- IF Any other comments or queries: respond helpfully then redisplay menu - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- ONLY proceed to finalize when user selects 'C' -- After other menu items execution, return to this menu - -### 2. Handle Review Feedback - -a) **If user requests changes:** - -- Make the requested edits to `{wipFile}` -- Re-present the affected sections -- Ask if there are more changes -- Loop until user is satisfied - -b) **If the spec does NOT meet the "Ready for Development" standard:** - -- Point out the missing/weak sections (e.g., non-actionable tasks, missing ACs). -- Propose specific improvements to reach the standard. -- Make the edits once the user agrees. - -c) **If user has questions:** - -- Answer questions about the spec -- Clarify any confusing sections -- Make clarifying edits if needed - -### 3. Finalize the Spec - -**When user confirms the spec is good AND it meets the "Ready for Development" standard:** - -a) Update `{wipFile}` frontmatter: - - ```yaml - --- - # ... existing values ... - status: 'ready-for-dev' - stepsCompleted: [1, 2, 3, 4] - --- - ``` - -b) **Rename WIP file to final filename:** - - Using the `slug` extracted in Section 1 - - Rename `{wipFile}` → `{implementation_artifacts}/tech-spec-{slug}.md` - - Store this as `finalFile` for use in menus below - -### 4. Present Final Menu - -a) **Display completion message and menu:** - -``` -**Tech-Spec Complete!** - -Saved to: {finalFile} - ---- - -**Next Steps:** - -[A] Advanced Elicitation - refine further -[R] Adversarial Review - critique of the spec (highly recommended) -[B] Begin Development - start implementing now (not recommended) -[D] Done - exit workflow -[P] Party Mode - get expert feedback before dev - ---- - -Once you are fully satisfied with the spec (ideally after **Adversarial Review** and maybe a few rounds of **Advanced Elicitation**), it is recommended to run implementation in a FRESH CONTEXT for best results. - -Copy this prompt to start dev: - -\`\`\` -quick-dev {finalFile} -\`\`\` - -This ensures the dev agent has clean context focused solely on implementation. -``` - -b) **HALT and wait for user selection.** - -#### Menu Handling Logic: - -- IF A: Read fully and follow: `{advanced_elicitation}` with current spec content, process enhanced insights, ask user "Accept improvements? (y/n)", if yes update spec then redisplay menu, if no keep original then redisplay menu -- IF B: Read the entire workflow file at `{quick_dev_workflow}` and follow the instructions with the final spec file (warn: fresh context is better) -- IF D: Exit workflow - display final confirmation and path to spec -- IF P: Read fully and follow: `{party_mode_exec}` with current spec content, process collaborative insights, ask user "Accept changes? (y/n)", if yes update spec then redisplay menu, if no keep original then redisplay menu -- IF R: Execute Adversarial Review (see below) -- IF Any other comments or queries: respond helpfully then redisplay menu - -#### EXECUTION RULES: - -- ALWAYS halt and wait for user input after presenting menu -- After A, P, or R execution, return to this menu - -#### Adversarial Review [R] Process: - -1. **Invoke Adversarial Review Task**: - > With `{finalFile}` constructed, load and follow the review task. If possible, use information asymmetry: load this task, and only it, in a separate subagent or process with read access to the project, but no context except the `{finalFile}`. - Review {finalFile} using {project-root}/_bmad/core/tasks/review-adversarial-general.xml - > **Platform fallback:** If task invocation not available, load the task file and follow its instructions inline, passing `{finalFile}` as the content. - > The task should: review `{finalFile}` and return a list of findings. - - 2. **Process Findings**: - > Capture the findings from the task output. - > **If zero findings:** HALT - this is suspicious. Re-analyze or request user guidance. - > Evaluate severity (Critical, High, Medium, Low) and validity (real, noise, undecided). - > DO NOT exclude findings based on severity or validity unless explicitly asked to do so. - > Order findings by severity. - > Number the ordered findings (F1, F2, F3, etc.). - > If TodoWrite or similar tool is available, turn each finding into a TODO, include ID, severity, validity, and description in the TODO; otherwise present findings as a table with columns: ID, Severity, Validity, Description - - 3. Return here and redisplay menu. - -### 5. Exit Workflow - -**When user selects [D]:** - -"**All done!** Your tech-spec is ready at: - -`{finalFile}` - -When you're ready to implement, run: - -``` -quick-dev {finalFile} -``` - -Ship it!" - ---- - -## REQUIRED OUTPUTS: - -- MUST update status to 'ready-for-dev'. -- MUST rename file to `tech-spec-{slug}.md`. -- MUST provide clear next-step guidance and recommend fresh context for dev. - -## VERIFICATION CHECKLIST: - -- [ ] Complete spec presented for review. -- [ ] Requested changes implemented. -- [ ] Spec verified against **READY FOR DEVELOPMENT** standard. -- [ ] `stepsCompleted: [1, 2, 3, 4]` set and file renamed. diff --git a/src/bmm/workflows/bmad-quick-flow/quick-spec/tech-spec-template.md b/src/bmm/workflows/bmad-quick-flow/quick-spec/tech-spec-template.md deleted file mode 100644 index 8d2011491..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-spec/tech-spec-template.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: '{title}' -slug: '{slug}' -created: '{date}' -status: 'in-progress' -stepsCompleted: [] -tech_stack: [] -files_to_modify: [] -code_patterns: [] -test_patterns: [] ---- - -# Tech-Spec: {title} - -**Created:** {date} - -## Overview - -### Problem Statement - -{problem_statement} - -### Solution - -{solution} - -### Scope - -**In Scope:** -{in_scope} - -**Out of Scope:** -{out_of_scope} - -## Context for Development - -### Codebase Patterns - -{codebase_patterns} - -### Files to Reference - -| File | Purpose | -| ---- | ------- | - -{files_table} - -### Technical Decisions - -{technical_decisions} - -## Implementation Plan - -### Tasks - -{tasks} - -### Acceptance Criteria - -{acceptance_criteria} - -## Additional Context - -### Dependencies - -{dependencies} - -### Testing Strategy - -{testing_strategy} - -### Notes - -{notes} diff --git a/src/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md b/src/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md deleted file mode 100644 index 462f41741..000000000 --- a/src/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md +++ /dev/null @@ -1,79 +0,0 @@ ---- -name: quick-spec -description: 'Very quick process to create implementation-ready quick specs for small changes or features. Use when the user says "create a quick spec" or "generate a quick tech spec"' -main_config: '{project-root}/_bmad/bmm/config.yaml' - -# Checkpoint handler paths -advanced_elicitation: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' -party_mode_exec: '{project-root}/_bmad/core/workflows/party-mode/workflow.md' -quick_dev_workflow: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md' ---- - -# Quick-Spec Workflow - -**Goal:** Create implementation-ready technical specifications through conversational discovery, code investigation, and structured documentation. - -**READY FOR DEVELOPMENT STANDARD:** - -A specification is considered "Ready for Development" ONLY if it meets the following: - -- **Actionable**: Every task has a clear file path and specific action. -- **Logical**: Tasks are ordered by dependency (lowest level first). -- **Testable**: All ACs follow Given/When/Then and cover happy path and edge cases. -- **Complete**: All investigation results from Step 2 are inlined; no placeholders or "TBD". -- **Self-Contained**: A fresh agent can implement the feature without reading the workflow history. - ---- - -**Your Role:** You are an elite developer and spec engineer. You ask sharp questions, investigate existing code thoroughly, and produce specs that contain ALL context a fresh dev agent needs to implement the feature. No handoffs, no missing context - just complete, actionable specs. - ---- - -## WORKFLOW ARCHITECTURE - -This uses **step-file architecture** for disciplined execution: - -### Core Principles - -- **Micro-file Design**: Each step is a self-contained instruction file that must be followed exactly -- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until directed -- **Sequential Enforcement**: Sequence within step files must be completed in order, no skipping or optimization -- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array -- **Append-Only Building**: Build the tech-spec by updating content as directed - -### Step Processing Rules - -1. **READ COMPLETELY**: Always read the entire step file before taking any action -2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate -3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection -4. **CHECK CONTINUATION**: Only proceed to next step when user selects [C] (Continue) -5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step -6. **LOAD NEXT**: When directed, read fully and follow the next step file - -### Critical Rules (NO EXCEPTIONS) - -- **NEVER** load multiple step files simultaneously -- **ALWAYS** read entire step file before execution -- **NEVER** skip steps or optimize the sequence -- **ALWAYS** update frontmatter of output file when completing a step -- **ALWAYS** follow the exact instructions in the step file -- **ALWAYS** halt at menus and wait for user input -- **NEVER** create mental todo lists from future steps - ---- - -## INITIALIZATION SEQUENCE - -### 1. Configuration Loading - -Load and read full config from `{main_config}` and resolve: - -- `project_name`, `planning_artifacts`, `implementation_artifacts`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as system-generated current datetime -- `project_context` = `**/project-context.md` (load if exists) -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### 2. First Step Execution - -Read fully and follow: `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-01-understand.md` to begin the workflow. diff --git a/src/bmm/workflows/document-project/checklist.md b/src/bmm/workflows/document-project/checklist.md deleted file mode 100644 index 7b67d1e56..000000000 --- a/src/bmm/workflows/document-project/checklist.md +++ /dev/null @@ -1,245 +0,0 @@ -# Document Project Workflow - Validation Checklist - -## Scan Level and Resumability - -- [ ] Scan level selection offered (quick/deep/exhaustive) for initial_scan and full_rescan modes -- [ ] Deep-dive mode automatically uses exhaustive scan (no choice given) -- [ ] Quick scan does NOT read source files (only patterns, configs, manifests) -- [ ] Deep scan reads files in critical directories per project type -- [ ] Exhaustive scan reads ALL source files (excluding node_modules, dist, build) -- [ ] State file (project-scan-report.json) created at workflow start -- [ ] State file updated after each step completion -- [ ] State file contains all required fields per schema -- [ ] Resumability prompt shown if state file exists and is <24 hours old -- [ ] Old state files (>24 hours) automatically archived -- [ ] Resume functionality loads previous state correctly -- [ ] Workflow can jump to correct step when resuming - -## Write-as-you-go Architecture - -- [ ] Each document written to disk IMMEDIATELY after generation -- [ ] Document validation performed right after writing (section-level) -- [ ] State file updated after each document is written -- [ ] Detailed findings purged from context after writing (only summaries kept) -- [ ] Context contains only high-level summaries (1-2 sentences per section) -- [ ] No accumulation of full project analysis in memory - -## Batching Strategy (Deep/Exhaustive Scans) - -- [ ] Batching applied for deep and exhaustive scan levels -- [ ] Batches organized by SUBFOLDER (not arbitrary file count) -- [ ] Large files (>5000 LOC) handled with appropriate judgment -- [ ] Each batch: read files, extract info, write output, validate, purge context -- [ ] Batch completion tracked in state file (batches_completed array) -- [ ] Batch summaries kept in context (1-2 sentences max) - -## Project Detection and Classification - -- [ ] Project type correctly identified and matches actual technology stack -- [ ] Multi-part vs single-part structure accurately detected -- [ ] All project parts identified if multi-part (no missing client/server/etc.) -- [ ] Documentation requirements loaded for each part type -- [ ] Architecture registry match is appropriate for detected stack - -## Technology Stack Analysis - -- [ ] All major technologies identified (framework, language, database, etc.) -- [ ] Versions captured where available -- [ ] Technology decision table is complete and accurate -- [ ] Dependencies and libraries documented -- [ ] Build tools and package managers identified - -## Codebase Scanning Completeness - -- [ ] All critical directories scanned based on project type -- [ ] API endpoints documented (if requires_api_scan = true) -- [ ] Data models captured (if requires_data_models = true) -- [ ] State management patterns identified (if requires_state_management = true) -- [ ] UI components inventoried (if requires_ui_components = true) -- [ ] Configuration files located and documented -- [ ] Authentication/security patterns identified -- [ ] Entry points correctly identified -- [ ] Integration points mapped (for multi-part projects) -- [ ] Test files and patterns documented - -## Source Tree Analysis - -- [ ] Complete directory tree generated with no major omissions -- [ ] Critical folders highlighted and described -- [ ] Entry points clearly marked -- [ ] Integration paths noted (for multi-part) -- [ ] Asset locations identified (if applicable) -- [ ] File organization patterns explained - -## Architecture Documentation Quality - -- [ ] Architecture document uses appropriate template from registry -- [ ] All template sections filled with relevant information (no placeholders) -- [ ] Technology stack section is comprehensive -- [ ] Architecture pattern clearly explained -- [ ] Data architecture documented (if applicable) -- [ ] API design documented (if applicable) -- [ ] Component structure explained (if applicable) -- [ ] Source tree included and annotated -- [ ] Testing strategy documented -- [ ] Deployment architecture captured (if config found) - -## Development and Operations Documentation - -- [ ] Prerequisites clearly listed -- [ ] Installation steps documented -- [ ] Environment setup instructions provided -- [ ] Local run commands specified -- [ ] Build process documented -- [ ] Test commands and approach explained -- [ ] Deployment process documented (if applicable) -- [ ] CI/CD pipeline details captured (if found) -- [ ] Contribution guidelines extracted (if found) - -## Multi-Part Project Specific (if applicable) - -- [ ] Each part documented separately -- [ ] Part-specific architecture files created (architecture-{part_id}.md) -- [ ] Part-specific component inventories created (if applicable) -- [ ] Part-specific development guides created -- [ ] Integration architecture document created -- [ ] Integration points clearly defined with type and details -- [ ] Data flow between parts explained -- [ ] project-parts.json metadata file created - -## Index and Navigation - -- [ ] index.md created as master entry point -- [ ] Project structure clearly summarized in index -- [ ] Quick reference section complete and accurate -- [ ] All generated docs linked from index -- [ ] All existing docs linked from index (if found) -- [ ] Getting started section provides clear next steps -- [ ] AI-assisted development guidance included -- [ ] Navigation structure matches project complexity (simple for single-part, detailed for multi-part) - -## File Completeness - -- [ ] index.md generated -- [ ] project-overview.md generated -- [ ] source-tree-analysis.md generated -- [ ] architecture.md (or per-part) generated -- [ ] component-inventory.md (or per-part) generated if UI components exist -- [ ] development-guide.md (or per-part) generated -- [ ] api-contracts.md (or per-part) generated if APIs documented -- [ ] data-models.md (or per-part) generated if data models found -- [ ] deployment-guide.md generated if deployment config found -- [ ] contribution-guide.md generated if guidelines found -- [ ] integration-architecture.md generated if multi-part -- [ ] project-parts.json generated if multi-part - -## Content Quality - -- [ ] Technical information is accurate and specific -- [ ] No generic placeholders or "TODO" items remain -- [ ] Examples and code snippets are relevant to actual project -- [ ] File paths and directory references are correct -- [ ] Technology names and versions are accurate -- [ ] Terminology is consistent across all documents -- [ ] Descriptions are clear and actionable - -## Brownfield PRD Readiness - -- [ ] Documentation provides enough context for AI to understand existing system -- [ ] Integration points are clear for planning new features -- [ ] Reusable components are identified for leveraging in new work -- [ ] Data models are documented for schema extension planning -- [ ] API contracts are documented for endpoint expansion -- [ ] Code conventions and patterns are captured for consistency -- [ ] Architecture constraints are clear for informed decision-making - -## Output Validation - -- [ ] All files saved to correct output folder -- [ ] File naming follows convention (no part suffix for single-part, with suffix for multi-part) -- [ ] No broken internal links between documents -- [ ] Markdown formatting is correct and renders properly -- [ ] JSON files are valid (project-parts.json if applicable) - -## Final Validation - -- [ ] User confirmed project classification is accurate -- [ ] User provided any additional context needed -- [ ] All requested areas of focus addressed -- [ ] Documentation is immediately usable for brownfield PRD workflow -- [ ] No critical information gaps identified - -## Issues Found - -### Critical Issues (must fix before completion) - -- - -### Minor Issues (can be addressed later) - -- - -### Missing Information (to note for user) - -- - -## Deep-Dive Mode Validation (if deep-dive was performed) - -- [ ] Deep-dive target area correctly identified and scoped -- [ ] All files in target area read completely (no skipped files) -- [ ] File inventory includes all exports with complete signatures -- [ ] Dependencies mapped for all files -- [ ] Dependents identified (who imports each file) -- [ ] Code snippets included for key implementation details -- [ ] Patterns and design approaches documented -- [ ] State management strategy explained -- [ ] Side effects documented (API calls, DB queries, etc.) -- [ ] Error handling approaches captured -- [ ] Testing files and coverage documented -- [ ] TODOs and comments extracted -- [ ] Dependency graph created showing relationships -- [ ] Data flow traced through the scanned area -- [ ] Integration points with rest of codebase identified -- [ ] Related code and similar patterns found outside scanned area -- [ ] Reuse opportunities documented -- [ ] Implementation guidance provided -- [ ] Modification instructions clear -- [ ] Index.md updated with deep-dive link -- [ ] Deep-dive documentation is immediately useful for implementation - ---- - -## State File Quality - -- [ ] State file is valid JSON (no syntax errors) -- [ ] State file is optimized (no pretty-printing, minimal whitespace) -- [ ] State file contains all completed steps with timestamps -- [ ] State file outputs_generated list is accurate and complete -- [ ] State file resume_instructions are clear and actionable -- [ ] State file findings contain only high-level summaries (not detailed data) -- [ ] State file can be successfully loaded for resumption - -## Completion Criteria - -All items in the following sections must be checked: - -- ✓ Scan Level and Resumability -- ✓ Write-as-you-go Architecture -- ✓ Batching Strategy (if deep/exhaustive scan) -- ✓ Project Detection and Classification -- ✓ Technology Stack Analysis -- ✓ Architecture Documentation Quality -- ✓ Index and Navigation -- ✓ File Completeness -- ✓ Brownfield PRD Readiness -- ✓ State File Quality -- ✓ Deep-Dive Mode Validation (if applicable) - -The workflow is complete when: - -1. All critical checklist items are satisfied -2. No critical issues remain -3. User has reviewed and approved the documentation -4. Generated docs are ready for use in brownfield PRD workflow -5. Deep-dive docs (if any) are comprehensive and implementation-ready -6. State file is valid and can enable resumption if interrupted diff --git a/src/bmm/workflows/document-project/documentation-requirements.csv b/src/bmm/workflows/document-project/documentation-requirements.csv deleted file mode 100644 index 9f773ab00..000000000 --- a/src/bmm/workflows/document-project/documentation-requirements.csv +++ /dev/null @@ -1,12 +0,0 @@ -project_type_id,requires_api_scan,requires_data_models,requires_state_management,requires_ui_components,requires_deployment_config,key_file_patterns,critical_directories,integration_scan_patterns,test_file_patterns,config_patterns,auth_security_patterns,schema_migration_patterns,entry_point_patterns,shared_code_patterns,monorepo_workspace_patterns,async_event_patterns,ci_cd_patterns,asset_patterns,hardware_interface_patterns,protocol_schema_patterns,localization_patterns,requires_hardware_docs,requires_asset_inventory -web,true,true,true,true,true,package.json;tsconfig.json;*.config.js;*.config.ts;vite.config.*;webpack.config.*;next.config.*;nuxt.config.*,src/;app/;pages/;components/;api/;lib/;styles/;public/;static/,*client.ts;*service.ts;*api.ts;fetch*.ts;axios*.ts;*http*.ts,*.test.ts;*.spec.ts;*.test.tsx;*.spec.tsx;**/__tests__/**;**/*.test.*;**/*.spec.*,.env*;config/*;*.config.*;.config/;settings/,*auth*.ts;*session*.ts;middleware/auth*;*.guard.ts;*authenticat*;*permission*;guards/,migrations/**;prisma/**;*.prisma;alembic/**;knex/**;*migration*.sql;*migration*.ts,main.ts;index.ts;app.ts;server.ts;_app.tsx;_app.ts;layout.tsx,shared/**;common/**;utils/**;lib/**;helpers/**;@*/**;packages/**,pnpm-workspace.yaml;lerna.json;nx.json;turbo.json;workspace.json;rush.json,*event*.ts;*queue*.ts;*subscriber*.ts;*consumer*.ts;*producer*.ts;*worker*.ts;jobs/**,.github/workflows/**;.gitlab-ci.yml;Jenkinsfile;.circleci/**;azure-pipelines.yml;bitbucket-pipelines.yml,.drone.yml,public/**;static/**;assets/**;images/**;media/**,N/A,*.proto;*.graphql;graphql/**;schema.graphql;*.avro;openapi.*;swagger.*,i18n/**;locales/**;lang/**;translations/**;messages/**;*.po;*.pot,false,false -mobile,true,true,true,true,true,package.json;pubspec.yaml;Podfile;build.gradle;app.json;capacitor.config.*;ionic.config.json,src/;app/;screens/;components/;services/;models/;assets/;ios/;android/,*client.ts;*service.ts;*api.ts;fetch*.ts;axios*.ts;*http*.ts,*.test.ts;*.test.tsx;*_test.dart;*.test.dart;**/__tests__/**,.env*;config/*;app.json;capacitor.config.*;google-services.json;GoogleService-Info.plist,*auth*.ts;*session*.ts;*authenticat*;*permission*;*biometric*;secure-store*,migrations/**;realm/**;*.realm;watermelondb/**;sqlite/**,main.ts;index.ts;App.tsx;App.ts;main.dart,shared/**;common/**;utils/**;lib/**;components/shared/**;@*/**,pnpm-workspace.yaml;lerna.json;nx.json;turbo.json,*event*.ts;*notification*.ts;*push*.ts;background-fetch*,fastlane/**;.github/workflows/**;.gitlab-ci.yml;bitbucket-pipelines.yml;appcenter-*,assets/**;Resources/**;res/**;*.xcassets;drawable*/;mipmap*/;images/**,N/A,*.proto;graphql/**;*.graphql,i18n/**;locales/**;translations/**;*.strings;*.xml,false,true -backend,true,true,false,false,true,package.json;requirements.txt;go.mod;Gemfile;pom.xml;build.gradle;Cargo.toml;*.csproj,src/;api/;services/;models/;routes/;controllers/;middleware/;handlers/;repositories/;domain/,*client.ts;*repository.ts;*service.ts;*connector*.ts;*adapter*.ts,*.test.ts;*.spec.ts;*_test.go;test_*.py;*Test.java;*_test.rs,.env*;config/*;*.config.*;application*.yml;application*.yaml;appsettings*.json;settings.py,*auth*.ts;*session*.ts;*authenticat*;*authorization*;middleware/auth*;guards/;*jwt*;*oauth*,migrations/**;alembic/**;flyway/**;liquibase/**;prisma/**;*.prisma;*migration*.sql;*migration*.ts;db/migrate,main.ts;index.ts;server.ts;app.ts;main.go;main.py;Program.cs;__init__.py,shared/**;common/**;utils/**;lib/**;core/**;@*/**;pkg/**,pnpm-workspace.yaml;lerna.json;nx.json;go.work,*event*.ts;*queue*.ts;*subscriber*.ts;*consumer*.ts;*producer*.ts;*worker*.ts;*handler*.ts;jobs/**;workers/**,.github/workflows/**;.gitlab-ci.yml;Jenkinsfile;.circleci/**;azure-pipelines.yml;.drone.yml,N/A,N/A,*.proto;*.graphql;graphql/**;*.avro;*.thrift;openapi.*;swagger.*;schema/**,N/A,false,false -cli,false,false,false,false,false,package.json;go.mod;Cargo.toml;setup.py;pyproject.toml;*.gemspec,src/;cmd/;cli/;bin/;lib/;commands/,N/A,*.test.ts;*_test.go;test_*.py;*.spec.ts;*_spec.rb,.env*;config/*;*.config.*;.*.rc;.*rc,N/A,N/A,main.ts;index.ts;cli.ts;main.go;main.py;__main__.py;bin/*,shared/**;common/**;utils/**;lib/**;helpers/**,N/A,N/A,.github/workflows/**;.gitlab-ci.yml;goreleaser.yml,N/A,N/A,N/A,N/A,false,false -library,false,false,false,false,false,package.json;setup.py;Cargo.toml;go.mod;*.gemspec;*.csproj;pom.xml,src/;lib/;dist/;pkg/;build/;target/,N/A,*.test.ts;*_test.go;test_*.py;*.spec.ts;*Test.java;*_test.rs,.*.rc;tsconfig.json;rollup.config.*;vite.config.*;webpack.config.*,N/A,N/A,index.ts;index.js;lib.rs;main.go;__init__.py,src/**;lib/**;core/**,N/A,N/A,.github/workflows/**;.gitlab-ci.yml;.circleci/**,N/A,N/A,N/A,N/A,false,false -desktop,false,false,true,true,true,package.json;Cargo.toml;*.csproj;CMakeLists.txt;tauri.conf.json;electron-builder.yml;wails.json,src/;app/;components/;main/;renderer/;resources/;assets/;build/,*service.ts;ipc*.ts;*bridge*.ts;*native*.ts;invoke*,*.test.ts;*.spec.ts;*_test.rs;*.spec.tsx,.env*;config/*;*.config.*;app.config.*;forge.config.*;builder.config.*,*auth*.ts;*session*.ts;keychain*;secure-storage*,N/A,main.ts;index.ts;main.js;src-tauri/main.rs;electron.ts,shared/**;common/**;utils/**;lib/**;components/shared/**,N/A,*event*.ts;*ipc*.ts;*message*.ts,.github/workflows/**;.gitlab-ci.yml;.circleci/**,resources/**;assets/**;icons/**;static/**;build/resources,N/A,N/A,i18n/**;locales/**;translations/**;lang/**,false,true -game,false,false,true,false,false,*.unity;*.godot;*.uproject;package.json;project.godot,Assets/;Scenes/;Scripts/;Prefabs/;Resources/;Content/;Source/;src/;scenes/;scripts/,N/A,*Test.cs;*_test.gd;*Test.cpp;*.test.ts,.env*;config/*;*.ini;settings/;GameSettings/,N/A,N/A,main.gd;Main.cs;GameManager.cs;main.cpp;index.ts,shared/**;common/**;utils/**;Core/**;Framework/**,N/A,N/A,.github/workflows/**;.gitlab-ci.yml,Assets/**;Scenes/**;Prefabs/**;Materials/**;Textures/**;Audio/**;Models/**;*.fbx;*.blend;*.shader;*.hlsl;*.glsl;Shaders/**;VFX/**,N/A,N/A,Localization/**;Languages/**;i18n/**,false,true -data,false,true,false,false,true,requirements.txt;pyproject.toml;dbt_project.yml;airflow.cfg;setup.py;Pipfile,dags/;pipelines/;models/;transformations/;notebooks/;sql/;etl/;jobs/,N/A,test_*.py;*_test.py;tests/**,.env*;config/*;profiles.yml;dbt_project.yml;airflow.cfg,N/A,migrations/**;dbt/models/**;*.sql;schemas/**,main.py;__init__.py;pipeline.py;dag.py,shared/**;common/**;utils/**;lib/**;helpers/**,N/A,*event*.py;*consumer*.py;*producer*.py;*worker*.py;jobs/**;tasks/**,.github/workflows/**;.gitlab-ci.yml;airflow/dags/**,N/A,N/A,*.proto;*.avro;schemas/**;*.parquet,N/A,false,false -extension,true,false,true,true,false,manifest.json;package.json;wxt.config.ts,src/;popup/;content/;background/;assets/;components/,*message.ts;*runtime.ts;*storage.ts;*tabs.ts,*.test.ts;*.spec.ts;*.test.tsx,.env*;wxt.config.*;webpack.config.*;vite.config.*,*auth*.ts;*session*.ts;*permission*,N/A,index.ts;popup.ts;background.ts;content.ts,shared/**;common/**;utils/**;lib/**,N/A,*message*.ts;*event*.ts;chrome.runtime*;browser.runtime*,.github/workflows/**,assets/**;icons/**;images/**;static/**,N/A,N/A,_locales/**;locales/**;i18n/**,false,false -infra,false,false,false,false,true,*.tf;*.tfvars;pulumi.yaml;cdk.json;*.yml;*.yaml;Dockerfile;docker-compose*.yml,terraform/;modules/;k8s/;charts/;playbooks/;roles/;policies/;stacks/,N/A,*_test.go;test_*.py;*_test.tf;*_spec.rb,.env*;*.tfvars;config/*;vars/;group_vars/;host_vars/,N/A,N/A,main.tf;index.ts;__main__.py;playbook.yml,modules/**;shared/**;common/**;lib/**,N/A,N/A,.github/workflows/**;.gitlab-ci.yml;.circleci/**,N/A,N/A,N/A,N/A,false,false -embedded,false,false,false,false,false,platformio.ini;CMakeLists.txt;*.ino;Makefile;*.ioc;mbed-os.lib,src/;lib/;include/;firmware/;drivers/;hal/;bsp/;components/,N/A,test_*.c;*_test.cpp;*_test.c;tests/**,.env*;config/*;sdkconfig;*.json;settings/,N/A,N/A,main.c;main.cpp;main.ino;app_main.c,lib/**;shared/**;common/**;drivers/**,N/A,N/A,.github/workflows/**;.gitlab-ci.yml,N/A,*.h;*.hpp;drivers/**;hal/**;bsp/**;pinout.*;peripheral*;gpio*;*.fzz;schematics/**,*.proto;mqtt*;coap*;modbus*,N/A,true,false diff --git a/src/bmm/workflows/document-project/instructions.md b/src/bmm/workflows/document-project/instructions.md deleted file mode 100644 index 0354be610..000000000 --- a/src/bmm/workflows/document-project/instructions.md +++ /dev/null @@ -1,130 +0,0 @@ -# Document Project Workflow Router - -The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml -You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/document-project/workflow.yaml -Communicate all responses in {communication_language} - - - -This router determines workflow mode and delegates to specialized sub-workflows - - -Check for existing state file at: {project_knowledge}/project-scan-report.json - - - Read state file and extract: timestamps, mode, scan_level, current_step, completed_steps, project_classification - Extract cached project_type_id(s) from state file if present - Calculate age of state file (current time - last_updated) - -I found an in-progress workflow state from {{last_updated}}. - - **Current Progress:** - - - Mode: {{mode}} - - Scan Level: {{scan_level}} - - Completed Steps: {{completed_steps_count}}/{{total_steps}} - - Last Step: {{current_step}} - - Project Type(s): {{cached_project_types}} - - Would you like to: - - 1. **Resume from where we left off** - Continue from step {{current_step}} - 2. **Start fresh** - Archive old state and begin new scan - 3. **Cancel** - Exit without changes - - Your choice [1/2/3]: - - - - Set resume_mode = true - Set workflow_mode = {{mode}} - Load findings summaries from state file - Load cached project_type_id(s) from state file - - CONDITIONAL CSV LOADING FOR RESUME: - For each cached project_type_id, load ONLY the corresponding row from: {documentation_requirements_csv} - Skip loading project-types.csv and architecture_registry.csv (not needed on resume) - Store loaded doc requirements for use in remaining steps - - Display: "Resuming {{workflow_mode}} from {{current_step}} with cached project type(s): {{cached_project_types}}" - - - Read fully and follow: {installed_path}/workflows/deep-dive-instructions.md with resume context - - - - Read fully and follow: {installed_path}/workflows/full-scan-instructions.md with resume context - - - - - - Create archive directory: {project_knowledge}/.archive/ - Move old state file to: {project_knowledge}/.archive/project-scan-report-{{timestamp}}.json - Set resume_mode = false - Continue to Step 0.5 - - - - Display: "Exiting workflow without changes." - Exit workflow - - - - Display: "Found old state file (>24 hours). Starting fresh scan." - Archive old state file to: {project_knowledge}/.archive/project-scan-report-{{timestamp}}.json - Set resume_mode = false - Continue to Step 0.5 - - - - - -Check if {project_knowledge}/index.md exists - - - Read existing index.md to extract metadata (date, project structure, parts count) - Store as {{existing_doc_date}}, {{existing_structure}} - -I found existing documentation generated on {{existing_doc_date}}. - -What would you like to do? - -1. **Re-scan entire project** - Update all documentation with latest changes -2. **Deep-dive into specific area** - Generate detailed documentation for a particular feature/module/folder -3. **Cancel** - Keep existing documentation as-is - -Your choice [1/2/3]: - - - - Set workflow_mode = "full_rescan" - Display: "Starting full project rescan..." - Read fully and follow: {installed_path}/workflows/full-scan-instructions.md - After sub-workflow completes, continue to Step 4 - - - - Set workflow_mode = "deep_dive" - Set scan_level = "exhaustive" - Display: "Starting deep-dive documentation mode..." - Read fully and follow: {installed_path}/workflows/deep-dive-instructions.md - After sub-workflow completes, continue to Step 4 - - - - Display message: "Keeping existing documentation. Exiting workflow." - Exit workflow - - - - - Set workflow_mode = "initial_scan" - Display: "No existing documentation found. Starting initial project scan..." - Read fully and follow: {installed_path}/workflows/full-scan-instructions.md - After sub-workflow completes, continue to Step 4 - - - - - diff --git a/src/bmm/workflows/document-project/templates/deep-dive-template.md b/src/bmm/workflows/document-project/templates/deep-dive-template.md deleted file mode 100644 index c1285cdc0..000000000 --- a/src/bmm/workflows/document-project/templates/deep-dive-template.md +++ /dev/null @@ -1,345 +0,0 @@ -# {{target_name}} - Deep Dive Documentation - -**Generated:** {{date}} -**Scope:** {{target_path}} -**Files Analyzed:** {{file_count}} -**Lines of Code:** {{total_loc}} -**Workflow Mode:** Exhaustive Deep-Dive - -## Overview - -{{target_description}} - -**Purpose:** {{target_purpose}} -**Key Responsibilities:** {{responsibilities}} -**Integration Points:** {{integration_summary}} - -## Complete File Inventory - -{{#each files_in_inventory}} - -### {{file_path}} - -**Purpose:** {{purpose}} -**Lines of Code:** {{loc}} -**File Type:** {{file_type}} - -**What Future Contributors Must Know:** {{contributor_note}} - -**Exports:** -{{#each exports}} - -- `{{signature}}` - {{description}} - {{/each}} - -**Dependencies:** -{{#each imports}} - -- `{{import_path}}` - {{reason}} - {{/each}} - -**Used By:** -{{#each dependents}} - -- `{{dependent_path}}` - {{/each}} - -**Key Implementation Details:** - -```{{language}} -{{key_code_snippet}} -``` - -{{implementation_notes}} - -**Patterns Used:** -{{#each patterns}} - -- {{pattern_name}}: {{pattern_description}} - {{/each}} - -**State Management:** {{state_approach}} - -**Side Effects:** -{{#each side_effects}} - -- {{effect_type}}: {{effect_description}} - {{/each}} - -**Error Handling:** {{error_handling_approach}} - -**Testing:** - -- Test File: {{test_file_path}} -- Coverage: {{coverage_percentage}}% -- Test Approach: {{test_approach}} - -**Comments/TODOs:** -{{#each todos}} - -- Line {{line_number}}: {{todo_text}} - {{/each}} - ---- - -{{/each}} - -## Contributor Checklist - -- **Risks & Gotchas:** {{risks_notes}} -- **Pre-change Verification Steps:** {{verification_steps}} -- **Suggested Tests Before PR:** {{suggested_tests}} - -## Architecture & Design Patterns - -### Code Organization - -{{organization_approach}} - -### Design Patterns - -{{#each design_patterns}} - -- **{{pattern_name}}**: {{usage_description}} - {{/each}} - -### State Management Strategy - -{{state_management_details}} - -### Error Handling Philosophy - -{{error_handling_philosophy}} - -### Testing Strategy - -{{testing_strategy}} - -## Data Flow - -{{data_flow_diagram}} - -### Data Entry Points - -{{#each entry_points}} - -- **{{entry_name}}**: {{entry_description}} - {{/each}} - -### Data Transformations - -{{#each transformations}} - -- **{{transformation_name}}**: {{transformation_description}} - {{/each}} - -### Data Exit Points - -{{#each exit_points}} - -- **{{exit_name}}**: {{exit_description}} - {{/each}} - -## Integration Points - -### APIs Consumed - -{{#each apis_consumed}} - -- **{{api_endpoint}}**: {{api_description}} - - Method: {{method}} - - Authentication: {{auth_requirement}} - - Response: {{response_schema}} - {{/each}} - -### APIs Exposed - -{{#each apis_exposed}} - -- **{{api_endpoint}}**: {{api_description}} - - Method: {{method}} - - Request: {{request_schema}} - - Response: {{response_schema}} - {{/each}} - -### Shared State - -{{#each shared_state}} - -- **{{state_name}}**: {{state_description}} - - Type: {{state_type}} - - Accessed By: {{accessors}} - {{/each}} - -### Events - -{{#each events}} - -- **{{event_name}}**: {{event_description}} - - Type: {{publish_or_subscribe}} - - Payload: {{payload_schema}} - {{/each}} - -### Database Access - -{{#each database_operations}} - -- **{{table_name}}**: {{operation_type}} - - Queries: {{query_patterns}} - - Indexes Used: {{indexes}} - {{/each}} - -## Dependency Graph - -{{dependency_graph_visualization}} - -### Entry Points (Not Imported by Others in Scope) - -{{#each entry_point_files}} - -- {{file_path}} - {{/each}} - -### Leaf Nodes (Don't Import Others in Scope) - -{{#each leaf_files}} - -- {{file_path}} - {{/each}} - -### Circular Dependencies - -{{#if has_circular_dependencies}} -⚠️ Circular dependencies detected: -{{#each circular_deps}} - -- {{cycle_description}} - {{/each}} - {{else}} - ✓ No circular dependencies detected - {{/if}} - -## Testing Analysis - -### Test Coverage Summary - -- **Statements:** {{statements_coverage}}% -- **Branches:** {{branches_coverage}}% -- **Functions:** {{functions_coverage}}% -- **Lines:** {{lines_coverage}}% - -### Test Files - -{{#each test_files}} - -- **{{test_file_path}}** - - Tests: {{test_count}} - - Approach: {{test_approach}} - - Mocking Strategy: {{mocking_strategy}} - {{/each}} - -### Test Utilities Available - -{{#each test_utilities}} - -- `{{utility_name}}`: {{utility_description}} - {{/each}} - -### Testing Gaps - -{{#each testing_gaps}} - -- {{gap_description}} - {{/each}} - -## Related Code & Reuse Opportunities - -### Similar Features Elsewhere - -{{#each similar_features}} - -- **{{feature_name}}** (`{{feature_path}}`) - - Similarity: {{similarity_description}} - - Can Reference For: {{reference_use_case}} - {{/each}} - -### Reusable Utilities Available - -{{#each reusable_utilities}} - -- **{{utility_name}}** (`{{utility_path}}`) - - Purpose: {{utility_purpose}} - - How to Use: {{usage_example}} - {{/each}} - -### Patterns to Follow - -{{#each patterns_to_follow}} - -- **{{pattern_name}}**: Reference `{{reference_file}}` for implementation - {{/each}} - -## Implementation Notes - -### Code Quality Observations - -{{#each quality_observations}} - -- {{observation}} - {{/each}} - -### TODOs and Future Work - -{{#each all_todos}} - -- **{{file_path}}:{{line_number}}**: {{todo_text}} - {{/each}} - -### Known Issues - -{{#each known_issues}} - -- {{issue_description}} - {{/each}} - -### Optimization Opportunities - -{{#each optimizations}} - -- {{optimization_suggestion}} - {{/each}} - -### Technical Debt - -{{#each tech_debt_items}} - -- {{debt_description}} - {{/each}} - -## Modification Guidance - -### To Add New Functionality - -{{modification_guidance_add}} - -### To Modify Existing Functionality - -{{modification_guidance_modify}} - -### To Remove/Deprecate - -{{modification_guidance_remove}} - -### Testing Checklist for Changes - -{{#each testing_checklist_items}} - -- [ ] {{checklist_item}} - {{/each}} - ---- - -_Generated by `document-project` workflow (deep-dive mode)_ -_Base Documentation: docs/index.md_ -_Scan Date: {{date}}_ -_Analysis Mode: Exhaustive_ diff --git a/src/bmm/workflows/document-project/templates/index-template.md b/src/bmm/workflows/document-project/templates/index-template.md deleted file mode 100644 index 0340a35af..000000000 --- a/src/bmm/workflows/document-project/templates/index-template.md +++ /dev/null @@ -1,169 +0,0 @@ -# {{project_name}} Documentation Index - -**Type:** {{repository_type}}{{#if is_multi_part}} with {{parts_count}} parts{{/if}} -**Primary Language:** {{primary_language}} -**Architecture:** {{architecture_type}} -**Last Updated:** {{date}} - -## Project Overview - -{{project_description}} - -{{#if is_multi_part}} - -## Project Structure - -This project consists of {{parts_count}} parts: - -{{#each project_parts}} - -### {{part_name}} ({{part_id}}) - -- **Type:** {{project_type}} -- **Location:** `{{root_path}}` -- **Tech Stack:** {{tech_stack_summary}} -- **Entry Point:** {{entry_point}} - {{/each}} - -## Cross-Part Integration - -{{integration_summary}} - -{{/if}} - -## Quick Reference - -{{#if is_single_part}} - -- **Tech Stack:** {{tech_stack_summary}} -- **Entry Point:** {{entry_point}} -- **Architecture Pattern:** {{architecture_pattern}} -- **Database:** {{database}} -- **Deployment:** {{deployment_platform}} - {{else}} - {{#each project_parts}} - -### {{part_name}} Quick Ref - -- **Stack:** {{tech_stack_summary}} -- **Entry:** {{entry_point}} -- **Pattern:** {{architecture_pattern}} - {{/each}} - {{/if}} - -## Generated Documentation - -### Core Documentation - -- [Project Overview](./project-overview.md) - Executive summary and high-level architecture -- [Source Tree Analysis](./source-tree-analysis.md) - Annotated directory structure - -{{#if is_single_part}} - -- [Architecture](./architecture.md) - Detailed technical architecture -- [Component Inventory](./component-inventory.md) - Catalog of major components{{#if has_ui_components}} and UI elements{{/if}} -- [Development Guide](./development-guide.md) - Local setup and development workflow - {{#if has_api_docs}}- [API Contracts](./api-contracts.md) - API endpoints and schemas{{/if}} - {{#if has_data_models}}- [Data Models](./data-models.md) - Database schema and models{{/if}} - {{else}} - -### Part-Specific Documentation - -{{#each project_parts}} - -#### {{part_name}} ({{part_id}}) - -- [Architecture](./architecture-{{part_id}}.md) - Technical architecture for {{part_name}} - {{#if has_components}}- [Components](./component-inventory-{{part_id}}.md) - Component catalog{{/if}} -- [Development Guide](./development-guide-{{part_id}}.md) - Setup and dev workflow - {{#if has_api}}- [API Contracts](./api-contracts-{{part_id}}.md) - API documentation{{/if}} - {{#if has_data}}- [Data Models](./data-models-{{part_id}}.md) - Data architecture{{/if}} - {{/each}} - -### Integration - -- [Integration Architecture](./integration-architecture.md) - How parts communicate -- [Project Parts Metadata](./project-parts.json) - Machine-readable structure - {{/if}} - -### Optional Documentation - -{{#if has_deployment_guide}}- [Deployment Guide](./deployment-guide.md) - Deployment process and infrastructure{{/if}} -{{#if has_contribution_guide}}- [Contribution Guide](./contribution-guide.md) - Contributing guidelines and standards{{/if}} - -## Existing Documentation - -{{#if has_existing_docs}} -{{#each existing_docs}} - -- [{{title}}]({{path}}) - {{description}} - {{/each}} - {{else}} - No existing documentation files were found in the project. - {{/if}} - -## Getting Started - -{{#if is_single_part}} - -### Prerequisites - -{{prerequisites}} - -### Setup - -```bash -{{setup_commands}} -``` - -### Run Locally - -```bash -{{run_commands}} -``` - -### Run Tests - -```bash -{{test_commands}} -``` - -{{else}} -{{#each project_parts}} - -### {{part_name}} Setup - -**Prerequisites:** {{prerequisites}} - -**Install & Run:** - -```bash -cd {{root_path}} -{{setup_command}} -{{run_command}} -``` - -{{/each}} -{{/if}} - -## For AI-Assisted Development - -This documentation was generated specifically to enable AI agents to understand and extend this codebase. - -### When Planning New Features: - -**UI-only features:** -{{#if is_multi_part}}→ Reference: `architecture-{{ui_part_id}}.md`, `component-inventory-{{ui_part_id}}.md`{{else}}→ Reference: `architecture.md`, `component-inventory.md`{{/if}} - -**API/Backend features:** -{{#if is_multi_part}}→ Reference: `architecture-{{api_part_id}}.md`, `api-contracts-{{api_part_id}}.md`, `data-models-{{api_part_id}}.md`{{else}}→ Reference: `architecture.md`{{#if has_api_docs}}, `api-contracts.md`{{/if}}{{#if has_data_models}}, `data-models.md`{{/if}}{{/if}} - -**Full-stack features:** -→ Reference: All architecture docs{{#if is_multi_part}} + `integration-architecture.md`{{/if}} - -**Deployment changes:** -{{#if has_deployment_guide}}→ Reference: `deployment-guide.md`{{else}}→ Review CI/CD configs in project{{/if}} - ---- - -_Documentation generated by BMAD Method `document-project` workflow_ diff --git a/src/bmm/workflows/document-project/templates/project-overview-template.md b/src/bmm/workflows/document-project/templates/project-overview-template.md deleted file mode 100644 index 3bbb0d24e..000000000 --- a/src/bmm/workflows/document-project/templates/project-overview-template.md +++ /dev/null @@ -1,103 +0,0 @@ -# {{project_name}} - Project Overview - -**Date:** {{date}} -**Type:** {{project_type}} -**Architecture:** {{architecture_type}} - -## Executive Summary - -{{executive_summary}} - -## Project Classification - -- **Repository Type:** {{repository_type}} -- **Project Type(s):** {{project_types_list}} -- **Primary Language(s):** {{primary_languages}} -- **Architecture Pattern:** {{architecture_pattern}} - -{{#if is_multi_part}} - -## Multi-Part Structure - -This project consists of {{parts_count}} distinct parts: - -{{#each project_parts}} - -### {{part_name}} - -- **Type:** {{project_type}} -- **Location:** `{{root_path}}` -- **Purpose:** {{purpose}} -- **Tech Stack:** {{tech_stack}} - {{/each}} - -### How Parts Integrate - -{{integration_description}} -{{/if}} - -## Technology Stack Summary - -{{#if is_single_part}} -{{technology_table}} -{{else}} -{{#each project_parts}} - -### {{part_name}} Stack - -{{technology_table}} -{{/each}} -{{/if}} - -## Key Features - -{{key_features}} - -## Architecture Highlights - -{{architecture_highlights}} - -## Development Overview - -### Prerequisites - -{{prerequisites}} - -### Getting Started - -{{getting_started_summary}} - -### Key Commands - -{{#if is_single_part}} - -- **Install:** `{{install_command}}` -- **Dev:** `{{dev_command}}` -- **Build:** `{{build_command}}` -- **Test:** `{{test_command}}` - {{else}} - {{#each project_parts}} - -#### {{part_name}} - -- **Install:** `{{install_command}}` -- **Dev:** `{{dev_command}}` - {{/each}} - {{/if}} - -## Repository Structure - -{{repository_structure_summary}} - -## Documentation Map - -For detailed information, see: - -- [index.md](./index.md) - Master documentation index -- [architecture.md](./architecture{{#if is_multi_part}}-{part_id}{{/if}}.md) - Detailed architecture -- [source-tree-analysis.md](./source-tree-analysis.md) - Directory structure -- [development-guide.md](./development-guide{{#if is_multi_part}}-{part_id}{{/if}}.md) - Development workflow - ---- - -_Generated using BMAD Method `document-project` workflow_ diff --git a/src/bmm/workflows/document-project/templates/project-scan-report-schema.json b/src/bmm/workflows/document-project/templates/project-scan-report-schema.json deleted file mode 100644 index 69e059833..000000000 --- a/src/bmm/workflows/document-project/templates/project-scan-report-schema.json +++ /dev/null @@ -1,160 +0,0 @@ -{ - "$schema": "http://json-schema.org/draft-07/schema#", - "title": "Project Scan Report Schema", - "description": "State tracking file for document-project workflow resumability", - "type": "object", - "required": ["workflow_version", "timestamps", "mode", "scan_level", "completed_steps", "current_step"], - "properties": { - "workflow_version": { - "type": "string", - "description": "Version of document-project workflow", - "example": "1.2.0" - }, - "timestamps": { - "type": "object", - "required": ["started", "last_updated"], - "properties": { - "started": { - "type": "string", - "format": "date-time", - "description": "ISO 8601 timestamp when workflow started" - }, - "last_updated": { - "type": "string", - "format": "date-time", - "description": "ISO 8601 timestamp of last state update" - }, - "completed": { - "type": "string", - "format": "date-time", - "description": "ISO 8601 timestamp when workflow completed (if finished)" - } - } - }, - "mode": { - "type": "string", - "enum": ["initial_scan", "full_rescan", "deep_dive"], - "description": "Workflow execution mode" - }, - "scan_level": { - "type": "string", - "enum": ["quick", "deep", "exhaustive"], - "description": "Scan depth level (deep_dive mode always uses exhaustive)" - }, - "project_root": { - "type": "string", - "description": "Absolute path to project root directory" - }, - "project_knowledge": { - "type": "string", - "description": "Absolute path to project knowledge folder" - }, - "completed_steps": { - "type": "array", - "items": { - "type": "object", - "required": ["step", "status"], - "properties": { - "step": { - "type": "string", - "description": "Step identifier (e.g., 'step_1', 'step_2')" - }, - "status": { - "type": "string", - "enum": ["completed", "partial", "failed"] - }, - "timestamp": { - "type": "string", - "format": "date-time" - }, - "outputs": { - "type": "array", - "items": { "type": "string" }, - "description": "Files written during this step" - }, - "summary": { - "type": "string", - "description": "1-2 sentence summary of step outcome" - } - } - } - }, - "current_step": { - "type": "string", - "description": "Current step identifier for resumption" - }, - "findings": { - "type": "object", - "description": "High-level summaries only (detailed findings purged after writing)", - "properties": { - "project_classification": { - "type": "object", - "properties": { - "repository_type": { "type": "string" }, - "parts_count": { "type": "integer" }, - "primary_language": { "type": "string" }, - "architecture_type": { "type": "string" } - } - }, - "technology_stack": { - "type": "array", - "items": { - "type": "object", - "properties": { - "part_id": { "type": "string" }, - "tech_summary": { "type": "string" } - } - } - }, - "batches_completed": { - "type": "array", - "description": "For deep/exhaustive scans: subfolders processed", - "items": { - "type": "object", - "properties": { - "path": { "type": "string" }, - "files_scanned": { "type": "integer" }, - "summary": { "type": "string" } - } - } - } - } - }, - "outputs_generated": { - "type": "array", - "items": { "type": "string" }, - "description": "List of all output files generated" - }, - "resume_instructions": { - "type": "string", - "description": "Instructions for resuming from current_step" - }, - "validation_status": { - "type": "object", - "properties": { - "last_validated": { - "type": "string", - "format": "date-time" - }, - "validation_errors": { - "type": "array", - "items": { "type": "string" } - } - } - }, - "deep_dive_targets": { - "type": "array", - "description": "Track deep-dive areas analyzed (for deep_dive mode)", - "items": { - "type": "object", - "properties": { - "target_name": { "type": "string" }, - "target_path": { "type": "string" }, - "files_analyzed": { "type": "integer" }, - "output_file": { "type": "string" }, - "timestamp": { "type": "string", "format": "date-time" } - } - } - } - } -} diff --git a/src/bmm/workflows/document-project/templates/source-tree-template.md b/src/bmm/workflows/document-project/templates/source-tree-template.md deleted file mode 100644 index 203062175..000000000 --- a/src/bmm/workflows/document-project/templates/source-tree-template.md +++ /dev/null @@ -1,135 +0,0 @@ -# {{project_name}} - Source Tree Analysis - -**Date:** {{date}} - -## Overview - -{{source_tree_overview}} - -{{#if is_multi_part}} - -## Multi-Part Structure - -This project is organized into {{parts_count}} distinct parts: - -{{#each project_parts}} - -- **{{part_name}}** (`{{root_path}}`): {{purpose}} - {{/each}} - {{/if}} - -## Complete Directory Structure - -``` -{{complete_source_tree}} -``` - -## Critical Directories - -{{#each critical_folders}} - -### `{{folder_path}}` - -{{description}} - -**Purpose:** {{purpose}} -**Contains:** {{contents_summary}} -{{#if entry_points}}**Entry Points:** {{entry_points}}{{/if}} -{{#if integration_note}}**Integration:** {{integration_note}}{{/if}} - -{{/each}} - -{{#if is_multi_part}} - -## Part-Specific Trees - -{{#each project_parts}} - -### {{part_name}} Structure - -``` -{{source_tree}} -``` - -**Key Directories:** -{{#each critical_directories}} - -- **`{{path}}`**: {{description}} - {{/each}} - -{{/each}} - -## Integration Points - -{{#each integration_points}} - -### {{from_part}} → {{to_part}} - -- **Location:** `{{integration_path}}` -- **Type:** {{integration_type}} -- **Details:** {{details}} - {{/each}} - -{{/if}} - -## Entry Points - -{{#if is_single_part}} - -- **Main Entry:** `{{main_entry_point}}` - {{#if additional_entry_points}} -- **Additional:** - {{#each additional_entry_points}} - - `{{path}}`: {{description}} - {{/each}} - {{/if}} - {{else}} - {{#each project_parts}} - -### {{part_name}} - -- **Entry Point:** `{{entry_point}}` -- **Bootstrap:** {{bootstrap_description}} - {{/each}} - {{/if}} - -## File Organization Patterns - -{{file_organization_patterns}} - -## Key File Types - -{{#each file_type_patterns}} - -### {{file_type}} - -- **Pattern:** `{{pattern}}` -- **Purpose:** {{purpose}} -- **Examples:** {{examples}} - {{/each}} - -## Asset Locations - -{{#if has_assets}} -{{#each asset_locations}} - -- **{{asset_type}}**: `{{location}}` ({{file_count}} files, {{total_size}}) - {{/each}} - {{else}} - No significant assets detected. - {{/if}} - -## Configuration Files - -{{#each config_files}} - -- **`{{path}}`**: {{description}} - {{/each}} - -## Notes for Development - -{{development_notes}} - ---- - -_Generated using BMAD Method `document-project` workflow_ diff --git a/src/bmm/workflows/document-project/workflow.yaml b/src/bmm/workflows/document-project/workflow.yaml deleted file mode 100644 index a47acf090..000000000 --- a/src/bmm/workflows/document-project/workflow.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# Document Project Workflow Configuration -name: "document-project" -version: "1.2.0" -description: 'Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"' -author: "BMad" - -# Critical variables -config_source: "{project-root}/_bmad/bmm/config.yaml" -project_knowledge: "{config_source}:project_knowledge" -user_name: "{config_source}:user_name" -communication_language: "{config_source}:communication_language" -document_output_language: "{config_source}:document_output_language" -user_skill_level: "{config_source}:user_skill_level" -date: system-generated - -# Module path and component files -installed_path: "{project-root}/_bmad/bmm/workflows/document-project" -instructions: "{installed_path}/instructions.md" -validation: "{installed_path}/checklist.md" - -# Required data files - CRITICAL for project type detection and documentation requirements -documentation_requirements_csv: "{installed_path}/documentation-requirements.csv" diff --git a/src/bmm/workflows/document-project/workflows/deep-dive-instructions.md b/src/bmm/workflows/document-project/workflows/deep-dive-instructions.md deleted file mode 100644 index 637621c4c..000000000 --- a/src/bmm/workflows/document-project/workflows/deep-dive-instructions.md +++ /dev/null @@ -1,298 +0,0 @@ -# Deep-Dive Documentation Instructions - - - -This workflow performs exhaustive deep-dive documentation of specific areas -Called by: ../document-project/instructions.md router -Handles: deep_dive mode only - - -Deep-dive mode requires literal full-file review. Sampling, guessing, or relying solely on tooling output is FORBIDDEN. -Load existing project structure from index.md and project-parts.json (if exists) -Load source tree analysis to understand available areas - - - Analyze existing documentation to suggest deep-dive options - -What area would you like to deep-dive into? - -**Suggested Areas Based on Project Structure:** - -{{#if has_api_routes}} - -## API Routes ({{api_route_count}} endpoints found) - -{{#each api_route_groups}} -{{group_index}}. {{group_name}} - {{endpoint_count}} endpoints in `{{path}}` -{{/each}} -{{/if}} - -{{#if has_feature_modules}} - -## Feature Modules ({{feature_count}} features) - -{{#each feature_modules}} -{{module_index}}. {{module_name}} - {{file_count}} files in `{{path}}` -{{/each}} -{{/if}} - -{{#if has_ui_components}} - -### UI Component Areas - -{{#each component_groups}} -{{group_index}}. {{group_name}} - {{component_count}} components in `{{path}}` -{{/each}} -{{/if}} - -{{#if has_services}} - -### Services/Business Logic - -{{#each service_groups}} -{{service_index}}. {{service_name}} - `{{path}}` -{{/each}} -{{/if}} - -**Or specify custom:** - -- Folder path (e.g., "client/src/features/dashboard") -- File path (e.g., "server/src/api/users.ts") -- Feature name (e.g., "authentication system") - -Enter your choice (number or custom path): - - -Parse user input to determine: - target_type: "folder" | "file" | "feature" | "api_group" | "component_group" - target_path: Absolute path to scan - target_name: Human-readable name for documentation - target_scope: List of all files to analyze - - -Store as {{deep_dive_target}} - -Display confirmation: -Target: {{target_name}} -Type: {{target_type}} -Path: {{target_path}} -Estimated files to analyze: {{estimated_file_count}} - -This will read EVERY file in this area. Proceed? [y/n] - - -Return to Step 13a (select different area) - - - - Set scan_mode = "exhaustive" - Initialize file_inventory = [] - You must read every line of every file in scope and capture a plain-language explanation (what the file does, side effects, why it matters) that future developer agents can act on. No shortcuts. - - - Get complete recursive file list from {{target_path}} - Filter out: node_modules/, .git/, dist/, build/, coverage/, *.min.js, *.map - For EVERY remaining file in folder: - - Read complete file contents (all lines) - - Extract all exports (functions, classes, types, interfaces, constants) - - Extract all imports (dependencies) - - Identify purpose from comments and code structure - - Write 1-2 sentences (minimum) in natural language describing behaviour, side effects, assumptions, and anything a developer must know before modifying the file - - Extract function signatures with parameter types and return types - - Note any TODOs, FIXMEs, or comments - - Identify patterns (hooks, components, services, controllers, etc.) - - Capture per-file contributor guidance: `contributor_note`, `risks`, `verification_steps`, `suggested_tests` - - Store in file_inventory - - - - - Read complete file at {{target_path}} - Extract all information as above - Read all files it imports (follow import chain 1 level deep) - Find all files that import this file (dependents via grep) - Store all in file_inventory - - - - Identify all route/controller files in API group - Read all route handlers completely - Read associated middleware, controllers, services - Read data models and schemas used - Extract complete request/response schemas - Document authentication and authorization requirements - Store all in file_inventory - - - - Search codebase for all files related to feature name - Include: UI components, API endpoints, models, services, tests - Read each file completely - Store all in file_inventory - - - - Get all component files in group - Read each component completely - Extract: Props interfaces, hooks used, child components, state management - Store all in file_inventory - - -For each file in file\*inventory, document: - **File Path:** Full path - **Purpose:** What this file does (1-2 sentences) - **Lines of Code:** Total LOC - **Exports:** Complete list with signatures - -- Functions: `functionName(param: Type): ReturnType` - Description - - Classes: `ClassName` - Description with key methods - - Types/Interfaces: `TypeName` - Description - - Constants: `CONSTANT_NAME: Type` - Description - **Imports/Dependencies:** What it uses and why - **Used By:** Files that import this (dependents) - **Key Implementation Details:** Important logic, algorithms, patterns - **State Management:** If applicable (Redux, Context, local state) - **Side Effects:** API calls, database queries, file I/O, external services - **Error Handling:** Try/catch blocks, error boundaries, validation - **Testing:** Associated test files and coverage - **Comments/TODOs:** Any inline documentation or planned work - - -comprehensive_file_inventory - - - - Build dependency graph for scanned area: - - Create graph with files as nodes - - Add edges for import relationships - - Identify circular dependencies if any - - Find entry points (files not imported by others in scope) - - Find leaf nodes (files that don't import others in scope) - - -Trace data flow through the system: - Follow function calls and data transformations - Track API calls and their responses - Document state updates and propagation - Map database queries and mutations - - -Identify integration points: - External APIs consumed - Internal APIs/services called - Shared state accessed - Events published/subscribed - Database tables accessed - - -dependency_graph -data_flow_analysis -integration_points - - - - Search codebase OUTSIDE scanned area for: - - Similar file/folder naming patterns - - Similar function signatures - - Similar component structures - - Similar API patterns - - Reusable utilities that could be used - - -Identify code reuse opportunities: - Shared utilities available - Design patterns used elsewhere - Component libraries available - Helper functions that could apply - - -Find reference implementations: - Similar features in other parts of codebase - Established patterns to follow - Testing approaches used elsewhere - - -related_code_references -reuse_opportunities - - - - Create documentation filename: deep-dive-{{sanitized_target_name}}.md - Aggregate contributor insights across files: - - Combine unique risk/gotcha notes into {{risks_notes}} - - Combine verification steps developers should run before changes into {{verification_steps}} - - Combine recommended test commands into {{suggested_tests}} - - -Load complete deep-dive template from: {installed_path}/templates/deep-dive-template.md -Fill template with all collected data from steps 13b-13d -Write filled template to: {project_knowledge}/deep-dive-{{sanitized_target_name}}.md -Validate deep-dive document completeness - -deep_dive_documentation - -Update state file: - Add to deep_dive_targets array: {"target_name": "{{target_name}}", "target_path": "{{target_path}}", "files_analyzed": {{file_count}}, "output_file": "deep-dive-{{sanitized_target_name}}.md", "timestamp": "{{now}}"} - Add output to outputs_generated - Update last_updated timestamp - - - - - Read existing index.md - -Check if "Deep-Dive Documentation" section exists - - - Add new section after "Generated Documentation": - -## Deep-Dive Documentation - -Detailed exhaustive analysis of specific areas: - - - - - -Add link to new deep-dive doc: - -- [{{target_name}} Deep-Dive](./deep-dive-{{sanitized_target_name}}.md) - Comprehensive analysis of {{target_description}} ({{file_count}} files, {{total_loc}} LOC) - Generated {{date}} - - - Update index metadata: - Last Updated: {{date}} - Deep-Dives: {{deep_dive_count}} - - - Save updated index.md - - updated_index - - - - Display summary: - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -## Deep-Dive Documentation Complete! ✓ - -**Generated:** {project_knowledge}/deep-dive-{{target_name}}.md -**Files Analyzed:** {{file_count}} -**Lines of Code Scanned:** {{total_loc}} -**Time Taken:** ~{{duration}} - -**Documentation Includes:** - -- Complete file inventory with all exports -- Dependency graph and data flow -- Integration points and API contracts -- Testing analysis and coverage -- Related code and reuse opportunities -- Implementation guidance - -**Index Updated:** {project_knowledge}/index.md now includes link to this deep-dive - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - - -Would you like to: - -1. **Deep-dive another area** - Analyze another feature/module/folder -2. **Finish** - Complete workflow - -Your choice [1/2]: - - - - Clear current deep_dive_target - Go to Step 13a (select new area) - - - - Display final message: - -All deep-dive documentation complete! - -**Master Index:** {project_knowledge}/index.md -**Deep-Dives Generated:** {{deep_dive_count}} - -These comprehensive docs are now ready for: - -- Architecture review -- Implementation planning -- Code understanding -- Brownfield PRD creation - -Thank you for using the document-project workflow! - -Exit workflow - - - - - diff --git a/src/bmm/workflows/document-project/workflows/deep-dive.yaml b/src/bmm/workflows/document-project/workflows/deep-dive.yaml deleted file mode 100644 index c7b85c031..000000000 --- a/src/bmm/workflows/document-project/workflows/deep-dive.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Deep-Dive Documentation Workflow Configuration -name: "document-project-deep-dive" -description: "Exhaustive deep-dive documentation of specific project areas" -author: "BMad" - -# This is a sub-workflow called by document-project/workflow.yaml -parent_workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml" - -# Critical variables inherited from parent -config_source: "{project-root}/_bmad/bmb/config.yaml" -project_knowledge: "{config_source}:project_knowledge" -user_name: "{config_source}:user_name" -date: system-generated - -# Module path and component files -installed_path: "{project-root}/_bmad/bmm/workflows/document-project/workflows" -template: false # Action workflow -instructions: "{installed_path}/deep-dive-instructions.md" -validation: "{project-root}/_bmad/bmm/workflows/document-project/checklist.md" - -# Templates -deep_dive_template: "{project-root}/_bmad/bmm/workflows/document-project/templates/deep-dive-template.md" - -# Runtime inputs (passed from parent workflow) -workflow_mode: "deep_dive" -scan_level: "exhaustive" # Deep-dive always uses exhaustive scan -project_root_path: "" -existing_index_path: "" # Path to existing index.md - -# Configuration -autonomous: false # Requires user input to select target area diff --git a/src/bmm/workflows/document-project/workflows/full-scan-instructions.md b/src/bmm/workflows/document-project/workflows/full-scan-instructions.md deleted file mode 100644 index 8a3621d21..000000000 --- a/src/bmm/workflows/document-project/workflows/full-scan-instructions.md +++ /dev/null @@ -1,1106 +0,0 @@ -# Full Project Scan Instructions - - - -This workflow performs complete project documentation (Steps 1-12) -Called by: document-project/instructions.md router -Handles: initial_scan and full_rescan modes - - -DATA LOADING STRATEGY - Understanding the Documentation Requirements System: - -Display explanation to user: - -**How Project Type Detection Works:** - -This workflow uses a single comprehensive CSV file to intelligently document your project: - -**documentation-requirements.csv** ({documentation_requirements_csv}) - -- Contains 12 project types (web, mobile, backend, cli, library, desktop, game, data, extension, infra, embedded) -- 24-column schema combining project type detection AND documentation requirements -- **Detection columns**: project_type_id, key_file_patterns (used to identify project type from codebase) -- **Requirement columns**: requires_api_scan, requires_data_models, requires_ui_components, etc. -- **Pattern columns**: critical_directories, test_file_patterns, config_patterns, etc. -- Acts as a "scan guide" - tells the workflow WHERE to look and WHAT to document -- Example: For project_type_id="web", key_file_patterns includes "package.json;tsconfig.json;\*.config.js" and requires_api_scan=true - -**When Documentation Requirements are Loaded:** - -- **Fresh Start (initial_scan)**: Load all 12 rows → detect type using key_file_patterns → use that row's requirements -- **Resume**: Load ONLY the doc requirements row(s) for cached project_type_id(s) -- **Full Rescan**: Same as fresh start (may re-detect project type) -- **Deep Dive**: Load ONLY doc requirements for the part being deep-dived - - -Now loading documentation requirements data for fresh start... - -Load documentation-requirements.csv from: {documentation_requirements_csv} -Store all 12 rows indexed by project_type_id for project detection and requirements lookup -Display: "Loaded documentation requirements for 12 project types (web, mobile, backend, cli, library, desktop, game, data, extension, infra, embedded)" - -Display: "✓ Documentation requirements loaded successfully. Ready to begin project analysis." - - - -Check if {project_knowledge}/index.md exists - - - Read existing index.md to extract metadata (date, project structure, parts count) - Store as {{existing_doc_date}}, {{existing_structure}} - -I found existing documentation generated on {{existing_doc_date}}. - -What would you like to do? - -1. **Re-scan entire project** - Update all documentation with latest changes -2. **Deep-dive into specific area** - Generate detailed documentation for a particular feature/module/folder -3. **Cancel** - Keep existing documentation as-is - -Your choice [1/2/3]: - - - - Set workflow_mode = "full_rescan" - Continue to scan level selection below - - - - Set workflow_mode = "deep_dive" - Set scan_level = "exhaustive" - Initialize state file with mode=deep_dive, scan_level=exhaustive - Jump to Step 13 - - - - Display message: "Keeping existing documentation. Exiting workflow." - Exit workflow - - - - - Set workflow_mode = "initial_scan" - Continue to scan level selection below - - -Select Scan Level - - - Choose your scan depth level: - -**1. Quick Scan** (2-5 minutes) [DEFAULT] - -- Pattern-based analysis without reading source files -- Scans: Config files, package manifests, directory structure -- Best for: Quick project overview, initial understanding -- File reading: Minimal (configs, README, package.json, etc.) - -**2. Deep Scan** (10-30 minutes) - -- Reads files in critical directories based on project type -- Scans: All critical paths from documentation requirements -- Best for: Comprehensive documentation for brownfield PRD -- File reading: Selective (key files in critical directories) - -**3. Exhaustive Scan** (30-120 minutes) - -- Reads ALL source files in project -- Scans: Every source file (excludes node_modules, dist, build) -- Best for: Complete analysis, migration planning, detailed audit -- File reading: Complete (all source files) - -Your choice [1/2/3] (default: 1): - - - - Set scan_level = "quick" - Display: "Using Quick Scan (pattern-based, no source file reading)" - - - - Set scan_level = "deep" - Display: "Using Deep Scan (reading critical files per project type)" - - - - Set scan_level = "exhaustive" - Display: "Using Exhaustive Scan (reading all source files)" - - -Initialize state file: {project_knowledge}/project-scan-report.json -Every time you touch the state file, record: step id, human-readable summary (what you actually did), precise timestamp, and any outputs written. Vague phrases are unacceptable. -Write initial state: -{ -"workflow_version": "1.2.0", -"timestamps": {"started": "{{current_timestamp}}", "last_updated": "{{current_timestamp}}"}, -"mode": "{{workflow_mode}}", -"scan_level": "{{scan_level}}", -"project_root": "{{project_root_path}}", -"project_knowledge": "{{project_knowledge}}", -"completed_steps": [], -"current_step": "step_1", -"findings": {}, -"outputs_generated": ["project-scan-report.json"], -"resume_instructions": "Starting from step 1" -} - -Continue with standard workflow from Step 1 - - - - -Ask user: "What is the root directory of the project to document?" (default: current working directory) -Store as {{project_root_path}} - -Scan {{project_root_path}} for key indicators: - -- Directory structure (presence of client/, server/, api/, src/, app/, etc.) -- Key files (package.json, go.mod, requirements.txt, etc.) -- Technology markers matching detection_keywords from project-types.csv - - -Detect if project is: - -- **Monolith**: Single cohesive codebase -- **Monorepo**: Multiple parts in one repository -- **Multi-part**: Separate client/server or similar architecture - - - - List detected parts with their paths - I detected multiple parts in this project: - {{detected_parts_list}} - -Is this correct? Should I document each part separately? [y/n] - - -Set repository_type = "monorepo" or "multi-part" -For each detected part: - Identify root path - Run project type detection using key_file_patterns from documentation-requirements.csv - Store as part in project_parts array - - -Ask user to specify correct parts and their paths - - - - Set repository_type = "monolith" - Create single part in project_parts array with root_path = {{project_root_path}} - Run project type detection using key_file_patterns from documentation-requirements.csv - - -For each part, match detected technologies and file patterns against key_file_patterns column in documentation-requirements.csv -Assign project_type_id to each part -Load corresponding documentation_requirements row for each part - -I've classified this project: -{{project_classification_summary}} - -Does this look correct? [y/n/edit] - - -project_structure -project_parts_metadata - -IMMEDIATELY update state file with step completion: - -- Add to completed_steps: {"step": "step_1", "status": "completed", "timestamp": "{{now}}", "summary": "Classified as {{repository_type}} with {{parts_count}} parts"} -- Update current_step = "step_2" -- Update findings.project_classification with high-level summary only -- **CACHE project_type_id(s)**: Add project_types array: [{"part_id": "{{part_id}}", "project_type_id": "{{project_type_id}}", "display_name": "{{display_name}}"}] -- This cached data prevents reloading all CSV files on resume - we can load just the needed documentation_requirements row(s) -- Update last_updated timestamp -- Write state file - - -PURGE detailed scan results from memory, keep only summary: "{{repository_type}}, {{parts_count}} parts, {{primary_tech}}" - - - -For each part, scan for existing documentation using patterns: -- README.md, README.rst, README.txt -- CONTRIBUTING.md, CONTRIBUTING.rst -- ARCHITECTURE.md, ARCHITECTURE.txt, docs/architecture/ -- DEPLOYMENT.md, DEPLOY.md, docs/deployment/ -- API.md, docs/api/ -- Any files in docs/, documentation/, .github/ folders - - -Create inventory of existing_docs with: - -- File path -- File type (readme, architecture, api, etc.) -- Which part it belongs to (if multi-part) - - -I found these existing documentation files: -{{existing_docs_list}} - -Are there any other important documents or key areas I should focus on while analyzing this project? [Provide paths or guidance, or type 'none'] - - -Store user guidance as {{user_context}} - -existing_documentation_inventory -user_provided_context - -Update state file: - -- Add to completed_steps: {"step": "step_2", "status": "completed", "timestamp": "{{now}}", "summary": "Found {{existing_docs_count}} existing docs"} -- Update current_step = "step_3" -- Update last_updated timestamp - - -PURGE detailed doc contents from memory, keep only: "{{existing_docs_count}} docs found" - - - -For each part in project_parts: - - Load key_file_patterns from documentation_requirements - - Scan part root for these patterns - - Parse technology manifest files (package.json, go.mod, requirements.txt, etc.) - - Extract: framework, language, version, database, dependencies - - Build technology_table with columns: Category, Technology, Version, Justification - - -Determine architecture pattern based on detected tech stack: - -- Use project_type_id as primary indicator (e.g., "web" → layered/component-based, "backend" → service/API-centric) -- Consider framework patterns (e.g., React → component hierarchy, Express → middleware pipeline) -- Note architectural style in technology table -- Store as {{architecture_pattern}} for each part - - -technology_stack -architecture_patterns - -Update state file: - -- Add to completed_steps: {"step": "step_3", "status": "completed", "timestamp": "{{now}}", "summary": "Tech stack: {{primary_framework}}"} -- Update current_step = "step_4" -- Update findings.technology_stack with summary per part -- Update last_updated timestamp - - -PURGE detailed tech analysis from memory, keep only: "{{framework}} on {{language}}" - - - - -BATCHING STRATEGY FOR DEEP/EXHAUSTIVE SCANS - - - This step requires file reading. Apply batching strategy: - -Identify subfolders to process based on: - scan_level == "deep": Use critical_directories from documentation_requirements - scan_level == "exhaustive": Get ALL subfolders recursively (excluding node_modules, .git, dist, build, coverage) - - -For each subfolder to scan: 1. Read all files in subfolder (consider file size - use judgment for files >5000 LOC) 2. Extract required information based on conditional flags below 3. IMMEDIATELY write findings to appropriate output file 4. Validate written document (section-level validation) 5. Update state file with batch completion 6. PURGE detailed findings from context, keep only 1-2 sentence summary 7. Move to next subfolder - - -Track batches in state file: -findings.batches_completed: [ -{"path": "{{subfolder_path}}", "files_scanned": {{count}}, "summary": "{{brief_summary}}"} -] - - - - - Use pattern matching only - do NOT read source files - Use glob/grep to identify file locations and patterns - Extract information from filenames, directory structure, and config files only - - -For each part, check documentation_requirements boolean flags and execute corresponding scans: - - - Scan for API routes and endpoints using integration_scan_patterns - Look for: controllers/, routes/, api/, handlers/, endpoints/ - - - Use glob to find route files, extract patterns from filenames and folder structure - - - - Read files in batches (one subfolder at a time) - Extract: HTTP methods, paths, request/response types from actual code - - -Build API contracts catalog -IMMEDIATELY write to: {project_knowledge}/api-contracts-{part_id}.md -Validate document has all required sections -Update state file with output generated -PURGE detailed API data, keep only: "{{api_count}} endpoints documented" -api_contracts\*{part_id} - - - - Scan for data models using schema_migration_patterns - Look for: models/, schemas/, entities/, migrations/, prisma/, ORM configs - - - Identify schema files via glob, parse migration file names for table discovery - - - - Read model files in batches (one subfolder at a time) - Extract: table names, fields, relationships, constraints from actual code - - -Build database schema documentation -IMMEDIATELY write to: {project_knowledge}/data-models-{part_id}.md -Validate document completeness -Update state file with output generated -PURGE detailed schema data, keep only: "{{table_count}} tables documented" -data_models\*{part_id} - - - - Analyze state management patterns - Look for: Redux, Context API, MobX, Vuex, Pinia, Provider patterns - Identify: stores, reducers, actions, state structure - state_management_patterns_{part_id} - - - - Inventory UI component library - Scan: components/, ui/, widgets/, views/ folders - Categorize: Layout, Form, Display, Navigation, etc. - Identify: Design system, component patterns, reusable elements - ui_component_inventory_{part_id} - - - - Look for hardware schematics using hardware_interface_patterns - This appears to be an embedded/hardware project. Do you have: - - Pinout diagrams - - Hardware schematics - - PCB layouts - - Hardware documentation - -If yes, please provide paths or links. [Provide paths or type 'none'] - -Store hardware docs references -hardware*documentation*{part_id} - - - - Scan and catalog assets using asset_patterns - Categorize by: Images, Audio, 3D Models, Sprites, Textures, etc. - Calculate: Total size, file counts, formats used - asset_inventory_{part_id} - - -Scan for additional patterns based on doc requirements: - -- config_patterns → Configuration management -- auth_security_patterns → Authentication/authorization approach -- entry_point_patterns → Application entry points and bootstrap -- shared_code_patterns → Shared libraries and utilities -- async_event_patterns → Event-driven architecture -- ci_cd_patterns → CI/CD pipeline details -- localization_patterns → i18n/l10n support - - -Apply scan_level strategy to each pattern scan (quick=glob only, deep/exhaustive=read files) - -comprehensive*analysis*{part_id} - -Update state file: - -- Add to completed_steps: {"step": "step_4", "status": "completed", "timestamp": "{{now}}", "summary": "Conditional analysis complete, {{files_generated}} files written"} -- Update current_step = "step_5" -- Update last_updated timestamp -- List all outputs_generated - - -PURGE all detailed scan results from context. Keep only summaries: - -- "APIs: {{api_count}} endpoints" -- "Data: {{table_count}} tables" -- "Components: {{component_count}} components" - - - - -For each part, generate complete directory tree using critical_directories from doc requirements - -Annotate the tree with: - -- Purpose of each critical directory -- Entry points marked -- Key file locations highlighted -- Integration points noted (for multi-part projects) - - -Show how parts are organized and where they interface - -Create formatted source tree with descriptions: - -``` -project-root/ -├── client/ # React frontend (Part: client) -│ ├── src/ -│ │ ├── components/ # Reusable UI components -│ │ ├── pages/ # Route-based pages -│ │ └── api/ # API client layer → Calls server/ -├── server/ # Express API backend (Part: api) -│ ├── src/ -│ │ ├── routes/ # REST API endpoints -│ │ ├── models/ # Database models -│ │ └── services/ # Business logic -``` - - - -source_tree_analysis -critical_folders_summary - -IMMEDIATELY write source-tree-analysis.md to disk -Validate document structure -Update state file: - -- Add to completed_steps: {"step": "step_5", "status": "completed", "timestamp": "{{now}}", "summary": "Source tree documented"} -- Update current_step = "step_6" -- Add output: "source-tree-analysis.md" - - PURGE detailed tree from context, keep only: "Source tree with {{folder_count}} critical folders" - - - -Scan for development setup using key_file_patterns and existing docs: -- Prerequisites (Node version, Python version, etc.) -- Installation steps (npm install, etc.) -- Environment setup (.env files, config) -- Build commands (npm run build, make, etc.) -- Run commands (npm start, go run, etc.) -- Test commands using test_file_patterns - - -Look for deployment configuration using ci_cd_patterns: - -- Dockerfile, docker-compose.yml -- Kubernetes configs (k8s/, helm/) -- CI/CD pipelines (.github/workflows/, .gitlab-ci.yml) -- Deployment scripts -- Infrastructure as Code (terraform/, pulumi/) - - - - Extract contribution guidelines: - - Code style rules - - PR process - - Commit conventions - - Testing requirements - - - -development_instructions -deployment_configuration -contribution_guidelines - -Update state file: - -- Add to completed_steps: {"step": "step_6", "status": "completed", "timestamp": "{{now}}", "summary": "Dev/deployment guides written"} -- Update current_step = "step_7" -- Add generated outputs to list - - PURGE detailed instructions, keep only: "Dev setup and deployment documented" - - - -Analyze how parts communicate: -- Scan integration_scan_patterns across parts -- Identify: REST calls, GraphQL queries, gRPC, message queues, shared databases -- Document: API contracts between parts, data flow, authentication flow - - -Create integration_points array with: - -- from: source part -- to: target part -- type: REST API, GraphQL, gRPC, Event Bus, etc. -- details: Endpoints, protocols, data formats - - -IMMEDIATELY write integration-architecture.md to disk -Validate document completeness - -integration_architecture - -Update state file: - -- Add to completed_steps: {"step": "step_7", "status": "completed", "timestamp": "{{now}}", "summary": "Integration architecture documented"} -- Update current_step = "step_8" - - PURGE integration details, keep only: "{{integration_count}} integration points" - - - -For each part in project_parts: - - Use matched architecture template from Step 3 as base structure - - Fill in all sections with discovered information: - * Executive Summary - * Technology Stack (from Step 3) - * Architecture Pattern (from registry match) - * Data Architecture (from Step 4 data models scan) - * API Design (from Step 4 API scan if applicable) - * Component Overview (from Step 4 component scan if applicable) - * Source Tree (from Step 5) - * Development Workflow (from Step 6) - * Deployment Architecture (from Step 6) - * Testing Strategy (from test patterns) - - - - - Generate: architecture.md (no part suffix) - - - - - Generate: architecture-{part_id}.md for each part - - -For each architecture file generated: - -- IMMEDIATELY write architecture file to disk -- Validate against architecture template schema -- Update state file with output -- PURGE detailed architecture from context, keep only: "Architecture for {{part_id}} written" - - -architecture_document - -Update state file: - -- Add to completed_steps: {"step": "step_8", "status": "completed", "timestamp": "{{now}}", "summary": "Architecture docs written for {{parts_count}} parts"} -- Update current_step = "step_9" - - - - -Generate project-overview.md with: -- Project name and purpose (from README or user input) -- Executive summary -- Tech stack summary table -- Architecture type classification -- Repository structure (monolith/monorepo/multi-part) -- Links to detailed docs - - -Generate source-tree-analysis.md with: - -- Full annotated directory tree from Step 5 -- Critical folders explained -- Entry points documented -- Multi-part structure (if applicable) - - -IMMEDIATELY write project-overview.md to disk -Validate document sections - -Generate source-tree-analysis.md (if not already written in Step 5) -IMMEDIATELY write to disk and validate - -Generate component-inventory.md (or per-part versions) with: - -- All discovered components from Step 4 -- Categorized by type -- Reusable vs specific components -- Design system elements (if found) - - IMMEDIATELY write each component inventory to disk and validate - -Generate development-guide.md (or per-part versions) with: - -- Prerequisites and dependencies -- Environment setup instructions -- Local development commands -- Build process -- Testing approach and commands -- Common development tasks - - IMMEDIATELY write each development guide to disk and validate - - - Generate deployment-guide.md with: - - Infrastructure requirements - - Deployment process - - Environment configuration - - CI/CD pipeline details - - IMMEDIATELY write to disk and validate - - - - Generate contribution-guide.md with: - - Code style and conventions - - PR process - - Testing requirements - - Documentation standards - - IMMEDIATELY write to disk and validate - - - - Generate api-contracts.md (or per-part) with: - - All API endpoints - - Request/response schemas - - Authentication requirements - - Example requests - - IMMEDIATELY write to disk and validate - - - - Generate data-models.md (or per-part) with: - - Database schema - - Table relationships - - Data models and entities - - Migration strategy - - IMMEDIATELY write to disk and validate - - - - Generate integration-architecture.md with: - - How parts communicate - - Integration points diagram/description - - Data flow between parts - - Shared dependencies - - IMMEDIATELY write to disk and validate - -Generate project-parts.json metadata file: -`json - { - "repository_type": "monorepo", - "parts": [ ... ], - "integration_points": [ ... ] - } - ` - -IMMEDIATELY write to disk - - -supporting_documentation - -Update state file: - -- Add to completed_steps: {"step": "step_9", "status": "completed", "timestamp": "{{now}}", "summary": "All supporting docs written"} -- Update current_step = "step_10" -- List all newly generated outputs - - -PURGE all document contents from context, keep only list of files generated - - - - -INCOMPLETE DOCUMENTATION MARKER CONVENTION: -When a document SHOULD be generated but wasn't (due to quick scan, missing data, conditional requirements not met): - -- Use EXACTLY this marker: _(To be generated)_ -- Place it at the end of the markdown link line -- Example: - [API Contracts - Server](./api-contracts-server.md) _(To be generated)_ -- This allows Step 11 to detect and offer to complete these items -- ALWAYS use this exact format for consistency and automated detection - - -Create index.md with intelligent navigation based on project structure - - - Generate simple index with: - - Project name and type - - Quick reference (tech stack, architecture type) - - Links to all generated docs - - Links to discovered existing docs - - Getting started section - - - - - Generate comprehensive index with: - - Project overview and structure summary - - Part-based navigation section - - Quick reference by part - - Cross-part integration links - - Links to all generated and existing docs - - Getting started per part - - - -Include in index.md: - -## Project Documentation Index - -### Project Overview - -- **Type:** {{repository_type}} {{#if multi-part}}with {{parts.length}} parts{{/if}} -- **Primary Language:** {{primary_language}} -- **Architecture:** {{architecture_type}} - -### Quick Reference - -{{#if single_part}} - -- **Tech Stack:** {{tech_stack_summary}} -- **Entry Point:** {{entry_point}} -- **Architecture Pattern:** {{architecture_pattern}} - {{else}} - {{#each parts}} - -#### {{part_name}} ({{part_id}}) - -- **Type:** {{project_type}} -- **Tech Stack:** {{tech_stack}} -- **Root:** {{root_path}} - {{/each}} - {{/if}} - -### Generated Documentation - -- [Project Overview](./project-overview.md) -- [Architecture](./architecture{{#if multi-part}}-{part\*id}{{/if}}.md){{#unless architecture_file_exists}} (To be generated) {{/unless}} -- [Source Tree Analysis](./source-tree-analysis.md) -- [Component Inventory](./component-inventory{{#if multi-part}}-{part\*id}{{/if}}.md){{#unless component_inventory_exists}} (To be generated) {{/unless}} -- [Development Guide](./development-guide{{#if multi-part}}-{part\*id}{{/if}}.md){{#unless dev_guide_exists}} (To be generated) {{/unless}} - {{#if deployment_found}}- [Deployment Guide](./deployment-guide.md){{#unless deployment_guide_exists}} (To be generated) {{/unless}}{{/if}} - {{#if contribution_found}}- [Contribution Guide](./contribution-guide.md){{/if}} - {{#if api_documented}}- [API Contracts](./api-contracts{{#if multi-part}}-{part_id}{{/if}}.md){{#unless api_contracts_exists}} (To be generated) {{/unless}}{{/if}} - {{#if data_models_documented}}- [Data Models](./data-models{{#if multi-part}}-{part_id}{{/if}}.md){{#unless data_models_exists}} (To be generated) {{/unless}}{{/if}} - {{#if multi-part}}- [Integration Architecture](./integration-architecture.md){{#unless integration_arch_exists}} (To be generated) {{/unless}}{{/if}} - -### Existing Documentation - -{{#each existing_docs}} - -- [{{title}}]({{relative_path}}) - {{description}} - {{/each}} - -### Getting Started - -{{getting_started_instructions}} - - -Before writing index.md, check which expected files actually exist: - -- For each document that should have been generated, check if file exists on disk -- Set existence flags: architecture_file_exists, component_inventory_exists, dev_guide_exists, etc. -- These flags determine whether to add the _(To be generated)_ marker -- Track which files are missing in {{missing_docs_list}} for reporting - - -IMMEDIATELY write index.md to disk with appropriate _(To be generated)_ markers for missing files -Validate index has all required sections and links are valid - -index - -Update state file: - -- Add to completed_steps: {"step": "step_10", "status": "completed", "timestamp": "{{now}}", "summary": "Master index generated"} -- Update current_step = "step_11" -- Add output: "index.md" - - -PURGE index content from context - - - -Show summary of all generated files: -Generated in {{project_knowledge}}/: -{{file_list_with_sizes}} - - -Run validation checklist from {validation} - -INCOMPLETE DOCUMENTATION DETECTION: - -1. PRIMARY SCAN: Look for exact marker: _(To be generated)_ -2. FALLBACK SCAN: Look for fuzzy patterns (in case agent was lazy): - - _(TBD)_ - - _(TODO)_ - - _(Coming soon)_ - - _(Not yet generated)_ - - _(Pending)_ -3. Extract document metadata from each match for user selection - - -Read {project_knowledge}/index.md - -Scan for incomplete documentation markers: -Step 1: Search for exact pattern "_(To be generated)_" (case-sensitive) -Step 2: For each match found, extract the entire line -Step 3: Parse line to extract: - -- Document title (text within [brackets] or **bold**) -- File path (from markdown link or inferable from title) -- Document type (infer from filename: architecture, api-contracts, data-models, component-inventory, development-guide, deployment-guide, integration-architecture) -- Part ID if applicable (extract from filename like "architecture-server.md" → part_id: "server") - Step 4: Add to {{incomplete_docs_strict}} array - - -Fallback fuzzy scan for alternate markers: -Search for patterns: _(TBD)_, _(TODO)_, _(Coming soon)_, _(Not yet generated)_, _(Pending)_ -For each fuzzy match: - -- Extract same metadata as strict scan -- Add to {{incomplete_docs_fuzzy}} array with fuzzy_match flag - - -Combine results: -Set {{incomplete_docs_list}} = {{incomplete_docs_strict}} + {{incomplete_docs_fuzzy}} -For each item store structure: -{ -"title": "Architecture – Server", -"file\*path": "./architecture-server.md", -"doc_type": "architecture", -"part_id": "server", -"line_text": "- [Architecture – Server](./architecture-server.md) (To be generated)", -"fuzzy_match": false -} - - -Documentation generation complete! - -Summary: - -- Project Type: {{project_type_summary}} -- Parts Documented: {{parts_count}} -- Files Generated: {{files_count}} -- Total Lines: {{total_lines}} - -{{#if incomplete_docs_list.length > 0}} -⚠️ **Incomplete Documentation Detected:** - -I found {{incomplete_docs_list.length}} item(s) marked as incomplete: - -{{#each incomplete_docs_list}} -{{@index + 1}}. **{{title}}** ({{doc_type}}{{#if part_id}} for {{part_id}}{{/if}}){{#if fuzzy_match}} ⚠️ [non-standard marker]{{/if}} -{{/each}} - -{{/if}} - -Would you like to: - -{{#if incomplete_docs_list.length > 0}} - -1. **Generate incomplete documentation** - Complete any of the {{incomplete_docs_list.length}} items above -2. Review any specific section [type section name] -3. Add more detail to any area [type area name] -4. Generate additional custom documentation [describe what] -5. Finalize and complete [type 'done'] - {{else}} -6. Review any specific section [type section name] -7. Add more detail to any area [type area name] -8. Generate additional documentation [describe what] -9. Finalize and complete [type 'done'] - {{/if}} - -Your choice: - - - - Which incomplete items would you like to generate? - -{{#each incomplete_docs_list}} -{{@index + 1}}. {{title}} ({{doc_type}}{{#if part_id}} - {{part_id}}{{/if}}) -{{/each}} -{{incomplete_docs_list.length + 1}}. All of them - -Enter number(s) separated by commas (e.g., "1,3,5"), or type 'all': - - -Parse user selection: - -- If "all", set {{selected_items}} = all items in {{incomplete_docs_list}} -- If comma-separated numbers, extract selected items by index -- Store result in {{selected_items}} array - - - Display: "Generating {{selected_items.length}} document(s)..." - - For each item in {{selected_items}}: - -1. **Identify the part and requirements:** - - Extract part_id from item (if exists) - - Look up part data in project_parts array from state file - - Load documentation_requirements for that part's project_type_id - -2. **Route to appropriate generation substep based on doc_type:** - - **If doc_type == "architecture":** - - Display: "Generating architecture documentation for {{part_id}}..." - - Load architecture_match for this part from state file (Step 3 cache) - - Re-run Step 8 architecture generation logic ONLY for this specific part - - Use matched template and fill with cached data from state file - - Write architecture-{{part_id}}.md to disk - - Validate completeness - - **If doc_type == "api-contracts":** - - Display: "Generating API contracts for {{part_id}}..." - - Load part data and documentation_requirements - - Re-run Step 4 API scan substep targeting ONLY this part - - Use scan_level from state file (quick/deep/exhaustive) - - Generate api-contracts-{{part_id}}.md - - Validate document structure - - **If doc_type == "data-models":** - - Display: "Generating data models documentation for {{part_id}}..." - - Re-run Step 4 data models scan substep targeting ONLY this part - - Use schema_migration_patterns from documentation_requirements - - Generate data-models-{{part_id}}.md - - Validate completeness - - **If doc_type == "component-inventory":** - - Display: "Generating component inventory for {{part_id}}..." - - Re-run Step 9 component inventory generation for this specific part - - Scan components/, ui/, widgets/ folders - - Generate component-inventory-{{part_id}}.md - - Validate structure - - **If doc_type == "development-guide":** - - Display: "Generating development guide for {{part_id}}..." - - Re-run Step 9 development guide generation for this specific part - - Use key_file_patterns and test_file_patterns from documentation_requirements - - Generate development-guide-{{part_id}}.md - - Validate completeness - - **If doc_type == "deployment-guide":** - - Display: "Generating deployment guide..." - - Re-run Step 6 deployment configuration scan - - Re-run Step 9 deployment guide generation - - Generate deployment-guide.md - - Validate structure - - **If doc_type == "integration-architecture":** - - Display: "Generating integration architecture..." - - Re-run Step 7 integration analysis for all parts - - Generate integration-architecture.md - - Validate completeness - -3. **Post-generation actions:** - - Confirm file was written successfully - - Update state file with newly generated output - - Add to {{newly_generated_docs}} tracking list - - Display: "✓ Generated: {{file_path}}" - -4. **Handle errors:** - - If generation fails, log error and continue with next item - - Track failed items in {{failed_generations}} list - - -After all selected items are processed: - -**Update index.md to remove markers:** - -1. Read current index.md content -2. For each item in {{newly_generated_docs}}: - - Find the line containing the file link and marker - - Remove the _(To be generated)_ or fuzzy marker text - - Leave the markdown link intact -3. Write updated index.md back to disk -4. Update state file to record index.md modification - - -Display generation summary: - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -✓ **Documentation Generation Complete!** - -**Successfully Generated:** -{{#each newly_generated_docs}} - -- {{title}} → {{file_path}} - {{/each}} - -{{#if failed_generations.length > 0}} -**Failed to Generate:** -{{#each failed_generations}} - -- {{title}} ({{error_message}}) - {{/each}} - {{/if}} - -**Updated:** index.md (removed incomplete markers) - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - - -Update state file with all generation activities - -Return to Step 11 menu (loop back to check for any remaining incomplete items) - - -Make requested modifications and regenerate affected files -Proceed to Step 12 completion - - - Update state file: -- Add to completed_steps: {"step": "step_11_iteration", "status": "completed", "timestamp": "{{now}}", "summary": "Review iteration complete"} -- Keep current_step = "step_11" (for loop back) -- Update last_updated timestamp - - Loop back to beginning of Step 11 (re-scan for remaining incomplete docs) - - - - Update state file: -- Add to completed_steps: {"step": "step_11", "status": "completed", "timestamp": "{{now}}", "summary": "Validation and review complete"} -- Update current_step = "step_12" - - Proceed to Step 12 - - - - -Create final summary report -Compile verification recap variables: - - Set {{verification_summary}} to the concrete tests, validations, or scripts you executed (or "none run"). - - Set {{open_risks}} to any remaining risks or TODO follow-ups (or "none"). - - Set {{next_checks}} to recommended actions before merging/deploying (or "none"). - - -Display completion message: - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -## Project Documentation Complete! ✓ - -**Location:** {{project_knowledge}}/ - -**Master Index:** {{project_knowledge}}/index.md -👆 This is your primary entry point for AI-assisted development - -**Generated Documentation:** -{{generated_files_list}} - -**Next Steps:** - -1. Review the index.md to familiarize yourself with the documentation structure -2. When creating a brownfield PRD, point the PRD workflow to: {{project_knowledge}}/index.md -3. For UI-only features: Reference {{project_knowledge}}/architecture-{{ui_part_id}}.md -4. For API-only features: Reference {{project_knowledge}}/architecture-{{api_part_id}}.md -5. For full-stack features: Reference both part architectures + integration-architecture.md - -**Verification Recap:** - -- Tests/extractions executed: {{verification_summary}} -- Outstanding risks or follow-ups: {{open_risks}} -- Recommended next checks before PR: {{next_checks}} - -**Brownfield PRD Command:** -When ready to plan new features, run the PRD workflow and provide this index as input. - -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - - -FINALIZE state file: - -- Add to completed_steps: {"step": "step_12", "status": "completed", "timestamp": "{{now}}", "summary": "Workflow complete"} -- Update timestamps.completed = "{{now}}" -- Update current_step = "completed" -- Write final state file - - -Display: "State file saved: {{project_knowledge}}/project-scan-report.json" - - diff --git a/src/bmm/workflows/document-project/workflows/full-scan.yaml b/src/bmm/workflows/document-project/workflows/full-scan.yaml deleted file mode 100644 index 272baedda..000000000 --- a/src/bmm/workflows/document-project/workflows/full-scan.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Full Project Scan Workflow Configuration -name: "document-project-full-scan" -description: "Complete project documentation workflow (initial scan or full rescan)" -author: "BMad" - -# This is a sub-workflow called by document-project/workflow.yaml -parent_workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml" - -# Critical variables inherited from parent -config_source: "{project-root}/_bmad/bmb/config.yaml" -project_knowledge: "{config_source}:project_knowledge" -user_name: "{config_source}:user_name" -date: system-generated - -# Data files -documentation_requirements_csv: "{project-root}/_bmad/bmm/workflows/document-project/documentation-requirements.csv" - -# Module path and component files -installed_path: "{project-root}/_bmad/bmm/workflows/document-project/workflows" -template: false # Action workflow -instructions: "{installed_path}/full-scan-instructions.md" -validation: "{project-root}/_bmad/bmm/workflows/document-project/checklist.md" - -# Runtime inputs (passed from parent workflow) -workflow_mode: "" # "initial_scan" or "full_rescan" -scan_level: "" # "quick", "deep", or "exhaustive" -resume_mode: false -project_root_path: "" - -# Configuration -autonomous: false # Requires user input at key decision points diff --git a/src/bmm/workflows/generate-project-context/project-context-template.md b/src/bmm/workflows/generate-project-context/project-context-template.md deleted file mode 100644 index ee01c4b37..000000000 --- a/src/bmm/workflows/generate-project-context/project-context-template.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -project_name: '{{project_name}}' -user_name: '{{user_name}}' -date: '{{date}}' -sections_completed: ['technology_stack'] -existing_patterns_found: { { number_of_patterns_discovered } } ---- - -# Project Context for AI Agents - -_This file contains critical rules and patterns that AI agents must follow when implementing code in this project. Focus on unobvious details that agents might otherwise miss._ - ---- - -## Technology Stack & Versions - -_Documented after discovery phase_ - -## Critical Implementation Rules - -_Documented after discovery phase_ diff --git a/src/bmm/workflows/generate-project-context/steps/step-01-discover.md b/src/bmm/workflows/generate-project-context/steps/step-01-discover.md deleted file mode 100644 index 16f95e15c..000000000 --- a/src/bmm/workflows/generate-project-context/steps/step-01-discover.md +++ /dev/null @@ -1,184 +0,0 @@ -# Step 1: Context Discovery & Initialization - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input -- ✅ ALWAYS treat this as collaborative discovery between technical peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on discovering existing project context and technology stack -- 🎯 IDENTIFY critical implementation rules that AI agents need -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 📖 Read existing project files to understand current context -- 💾 Initialize document and update frontmatter -- 🚫 FORBIDDEN to load next step until discovery is complete - -## CONTEXT BOUNDARIES: - -- Variables from workflow.md are available in memory -- Focus on existing project files and architecture decisions -- Look for patterns, conventions, and unique requirements -- Prioritize rules that prevent implementation mistakes - -## YOUR TASK: - -Discover the project's technology stack, existing patterns, and critical implementation rules that AI agents must follow when writing code. - -## DISCOVERY SEQUENCE: - -### 1. Check for Existing Project Context - -First, check if project context already exists: - -- Look for file at `{project_knowledge}/project-context.md or {project-root}/**/project-context.md` -- If exists: Read complete file to understand existing rules -- Present to user: "Found existing project context with {number_of_sections} sections. Would you like to update this or create a new one?" - -### 2. Discover Project Technology Stack - -Load and analyze project files to identify technologies: - -**Architecture Document:** - -- Look for `{planning_artifacts}/architecture.md` -- Extract technology choices with specific versions -- Note architectural decisions that affect implementation - -**Package Files:** - -- Check for `package.json`, `requirements.txt`, `Cargo.toml`, etc. -- Extract exact versions of all dependencies -- Note development vs production dependencies - -**Configuration Files:** - -- Look for project language specific configs ( example: `tsconfig.json`) -- Build tool configs (webpack, vite, next.config.js, etc.) -- Linting and formatting configs (.eslintrc, .prettierrc, etc.) -- Testing configurations (jest.config.js, vitest.config.ts, etc.) - -### 3. Identify Existing Code Patterns - -Search through existing codebase for patterns: - -**Naming Conventions:** - -- File naming patterns (PascalCase, kebab-case, etc.) -- Component/function naming conventions -- Variable naming patterns -- Test file naming patterns - -**Code Organization:** - -- How components are structured -- Where utilities and helpers are placed -- How services are organized -- Test organization patterns - -**Documentation Patterns:** - -- Comment styles and conventions -- Documentation requirements -- README and API doc patterns - -### 4. Extract Critical Implementation Rules - -Look for rules that AI agents might miss: - -**Language-Specific Rules:** - -- TypeScript strict mode requirements -- Import/export conventions -- Async/await vs Promise usage patterns -- Error handling patterns specific to the language - -**Framework-Specific Rules:** - -- React hooks usage patterns -- API route conventions -- Middleware usage patterns -- State management patterns - -**Testing Rules:** - -- Test structure requirements -- Mock usage conventions -- Integration vs unit test boundaries -- Coverage requirements - -**Development Workflow Rules:** - -- Branch naming conventions -- Commit message patterns -- PR review requirements -- Deployment procedures - -### 5. Initialize Project Context Document - -Based on discovery, create or update the context document: - -#### A. Fresh Document Setup (if no existing context) - -Copy template from `{installed_path}/project-context-template.md` to `{output_folder}/project-context.md` -Initialize frontmatter fields. - -#### B. Existing Document Update - -Load existing context and prepare for updates -Set frontmatter `sections_completed` to track what will be updated - -### 6. Present Discovery Summary - -Report findings to user: - -"Welcome {{user_name}}! I've analyzed your project for {{project_name}} to discover the context that AI agents need. - -**Technology Stack Discovered:** -{{list_of_technologies_with_versions}} - -**Existing Patterns Found:** - -- {{number_of_patterns}} implementation patterns -- {{number_of_conventions}} coding conventions -- {{number_of_rules}} critical rules - -**Key Areas for Context Rules:** - -- {{area_1}} (e.g., TypeScript configuration) -- {{area_2}} (e.g., Testing patterns) -- {{area_3}} (e.g., Code organization) - -{if_existing_context} -**Existing Context:** Found {{sections}} sections already defined. We can update or add to these. -{/if_existing_context} - -Ready to create/update your project context. This will help AI agents implement code consistently with your project's standards. - -[C] Continue to context generation" - -## SUCCESS METRICS: - -✅ Existing project context properly detected and handled -✅ Technology stack accurately identified with versions -✅ Critical implementation patterns discovered -✅ Project context document properly initialized -✅ Discovery findings clearly presented to user -✅ User ready to proceed with context generation - -## FAILURE MODES: - -❌ Not checking for existing project context before creating new one -❌ Missing critical technology versions or configurations -❌ Overlooking important coding patterns or conventions -❌ Not initializing frontmatter properly -❌ Not presenting clear discovery summary to user - -## NEXT STEP: - -After user selects [C] to continue, load `{project-root}/_bmad/bmm/workflows/generate-project-context/steps/step-02-generate.md` to collaboratively generate the specific project context rules. - -Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and discovery is confirmed and the initial file has been written as directed in this discovery step! diff --git a/src/bmm/workflows/generate-project-context/steps/step-02-generate.md b/src/bmm/workflows/generate-project-context/steps/step-02-generate.md deleted file mode 100644 index dcb2f0097..000000000 --- a/src/bmm/workflows/generate-project-context/steps/step-02-generate.md +++ /dev/null @@ -1,318 +0,0 @@ -# Step 2: Context Rules Generation - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input -- ✅ ALWAYS treat this as collaborative discovery between technical peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on unobvious rules that AI agents need to be reminded of -- 🎯 KEEP CONTENT LEAN - optimize for LLM context efficiency -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 📝 Focus on specific, actionable rules rather than general advice -- ⚠️ Present A/P/C menu after each major rule category -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter with completed sections -- 🚫 FORBIDDEN to load next step until all sections are complete - -## COLLABORATION MENUS (A/P/C): - -This step will generate content and present choices for each rule category: - -- **A (Advanced Elicitation)**: Use discovery protocols to explore nuanced implementation rules -- **P (Party Mode)**: Bring multiple perspectives to identify critical edge cases -- **C (Continue)**: Save the current rules and proceed to next category - -## PROTOCOL INTEGRATION: - -- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml -- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode -- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed -- User accepts/rejects protocol changes before proceeding - -## CONTEXT BOUNDARIES: - -- Discovery results from step-1 are available -- Technology stack and existing patterns are identified -- Focus on rules that prevent implementation mistakes -- Prioritize unobvious details that AI agents might miss - -## YOUR TASK: - -Collaboratively generate specific, critical rules that AI agents must follow when implementing code in this project. - -## CONTEXT GENERATION SEQUENCE: - -### 1. Technology Stack & Versions - -Document the exact technology stack from discovery: - -**Core Technologies:** -Based on user skill level, present findings: - -**Expert Mode:** -"Technology stack from your architecture and package files: -{{exact_technologies_with_versions}} - -Any critical version constraints I should document for agents?" - -**Intermediate Mode:** -"I found your technology stack: - -**Core Technologies:** -{{main_technologies_with_versions}} - -**Key Dependencies:** -{{important_dependencies_with_versions}} - -Are there any version constraints or compatibility notes agents should know about?" - -**Beginner Mode:** -"Here are the technologies you're using: - -**Main Technologies:** -{{friendly_description_of_tech_stack}} - -**Important Notes:** -{{key_things_agents_need_to_know_about_versions}} - -Should I document any special version rules or compatibility requirements?" - -### 2. Language-Specific Rules - -Focus on unobvious language patterns agents might miss: - -**TypeScript/JavaScript Rules:** -"Based on your codebase, I notice some specific patterns: - -**Configuration Requirements:** -{{typescript_config_rules}} - -**Import/Export Patterns:** -{{import_export_conventions}} - -**Error Handling Patterns:** -{{error_handling_requirements}} - -Are these patterns correct? Any other language-specific rules agents should follow?" - -**Python/Ruby/Other Language Rules:** -Adapt to the actual language in use with similar focused questions. - -### 3. Framework-Specific Rules - -Document framework-specific patterns: - -**React Rules (if applicable):** -"For React development, I see these patterns: - -**Hooks Usage:** -{{hooks_usage_patterns}} - -**Component Structure:** -{{component_organization_rules}} - -**State Management:** -{{state_management_patterns}} - -**Performance Rules:** -{{performance_optimization_requirements}} - -Should I add any other React-specific rules?" - -**Other Framework Rules:** -Adapt for Vue, Angular, Next.js, Express, etc. - -### 4. Testing Rules - -Focus on testing patterns that ensure consistency: - -**Test Structure Rules:** -"Your testing setup shows these patterns: - -**Test Organization:** -{{test_file_organization}} - -**Mock Usage:** -{{mock_patterns_and_conventions}} - -**Test Coverage Requirements:** -{{coverage_expectations}} - -**Integration vs Unit Test Rules:** -{{test_boundary_patterns}} - -Are there testing rules agents should always follow?" - -### 5. Code Quality & Style Rules - -Document critical style and quality rules: - -**Linting/Formatting:** -"Your code style configuration requires: - -**ESLint/Prettier Rules:** -{{specific_linting_rules}} - -**Code Organization:** -{{file_and_folder_structure_rules}} - -**Naming Conventions:** -{{naming_patterns_agents_must_follow}} - -**Documentation Requirements:** -{{comment_and_documentation_patterns}} - -Any additional code quality rules?" - -### 6. Development Workflow Rules - -Document workflow patterns that affect implementation: - -**Git/Repository Rules:** -"Your project uses these patterns: - -**Branch Naming:** -{{branch_naming_conventions}} - -**Commit Message Format:** -{{commit_message_patterns}} - -**PR Requirements:** -{{pull_request_checklist}} - -**Deployment Patterns:** -{{deployment_considerations}} - -Should I document any other workflow rules?" - -### 7. Critical Don't-Miss Rules - -Identify rules that prevent common mistakes: - -**Anti-Patterns to Avoid:** -"Based on your codebase, here are critical things agents must NOT do: - -{{critical_anti_patterns_with_examples}} - -**Edge Cases:** -{{specific_edge_cases_agents_should_handle}} - -**Security Rules:** -{{security_considerations_agents_must_follow}} - -**Performance Gotchas:** -{{performance_patterns_to_avoid}} - -Are there other 'gotchas' agents should know about?" - -### 8. Generate Context Content - -For each category, prepare lean content for the project context file: - -#### Content Structure: - -```markdown -## Technology Stack & Versions - -{{concise_technology_list_with_exact_versions}} - -## Critical Implementation Rules - -### Language-Specific Rules - -{{bullet_points_of_critical_language_rules}} - -### Framework-Specific Rules - -{{bullet_points_of_framework_patterns}} - -### Testing Rules - -{{bullet_points_of_testing_requirements}} - -### Code Quality & Style Rules - -{{bullet_points_of_style_and_quality_rules}} - -### Development Workflow Rules - -{{bullet_points_of_workflow_patterns}} - -### Critical Don't-Miss Rules - -{{bullet_points_of_anti_patterns_and_edge_cases}} -``` - -### 9. Present Content and Menu - -After each category, show the generated rules and present choices: - -"I've drafted the {{category_name}} rules for your project context. - -**Here's what I'll add:** - -[Show the complete markdown content for this category] - -**What would you like to do?** -[A] Advanced Elicitation - Explore nuanced rules for this category -[P] Party Mode - Review from different implementation perspectives -[C] Continue - Save these rules and move to next category" - -### 10. Handle Menu Selection - -#### If 'A' (Advanced Elicitation): - -- Execute advanced-elicitation.xml with current category rules -- Process enhanced rules that come back -- Ask user: "Accept these enhanced rules for {{category}}? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'P' (Party Mode): - -- Execute party-mode workflow with category rules context -- Process collaborative insights on implementation patterns -- Ask user: "Accept these changes to {{category}} rules? (y/n)" -- If yes: Update content, then return to A/P/C menu -- If no: Keep original content, then return to A/P/C menu - -#### If 'C' (Continue): - -- Save the current category content to project context file -- Update frontmatter: `sections_completed: [...]` -- Proceed to next category or step-03 if complete - -## APPEND TO PROJECT CONTEXT: - -When user selects 'C' for a category, append the content directly to `{output_folder}/project-context.md` using the structure from step 8. - -## SUCCESS METRICS: - -✅ All critical technology versions accurately documented -✅ Language-specific rules cover unobvious patterns -✅ Framework rules capture project-specific conventions -✅ Testing rules ensure consistent test quality -✅ Code quality rules maintain project standards -✅ Workflow rules prevent implementation conflicts -✅ Content is lean and optimized for LLM context -✅ A/P/C menu presented and handled correctly for each category - -## FAILURE MODES: - -❌ Including obvious rules that agents already know -❌ Making content too verbose for LLM context efficiency -❌ Missing critical anti-patterns or edge cases -❌ Not getting user validation for each rule category -❌ Not documenting exact versions and configurations -❌ Not presenting A/P/C menu after content generation - -## NEXT STEP: - -After completing all rule categories and user selects 'C' for the final category, load `{project-root}/_bmad/bmm/workflows/generate-project-context/steps/step-03-complete.md` to finalize the project context file. - -Remember: Do NOT proceed to step-03 until all categories are complete and user explicitly selects 'C' for each! diff --git a/src/bmm/workflows/generate-project-context/steps/step-03-complete.md b/src/bmm/workflows/generate-project-context/steps/step-03-complete.md deleted file mode 100644 index 85dd4db7b..000000000 --- a/src/bmm/workflows/generate-project-context/steps/step-03-complete.md +++ /dev/null @@ -1,278 +0,0 @@ -# Step 3: Context Completion & Finalization - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input -- ✅ ALWAYS treat this as collaborative completion between technical peers -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on finalizing a lean, LLM-optimized project context -- 🎯 ENSURE all critical rules are captured and actionable -- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 📝 Review and optimize content for LLM context efficiency -- 📖 Update frontmatter with completion status -- 🚫 NO MORE STEPS - this is the final step - -## CONTEXT BOUNDARIES: - -- All rule categories from step-2 are complete -- Technology stack and versions are documented -- Focus on final review, optimization, and completion -- Ensure the context file is ready for AI agent consumption - -## YOUR TASK: - -Complete the project context file, optimize it for LLM efficiency, and provide guidance for usage and maintenance. - -## COMPLETION SEQUENCE: - -### 1. Review Complete Context File - -Read the entire project context file and analyze: - -**Content Analysis:** - -- Total length and readability for LLMs -- Clarity and specificity of rules -- Coverage of all critical areas -- Actionability of each rule - -**Structure Analysis:** - -- Logical organization of sections -- Consistency of formatting -- Absence of redundant or obvious information -- Optimization for quick scanning - -### 2. Optimize for LLM Context - -Ensure the file is lean and efficient: - -**Content Optimization:** - -- Remove any redundant rules or obvious information -- Combine related rules into concise bullet points -- Use specific, actionable language -- Ensure each rule provides unique value - -**Formatting Optimization:** - -- Use consistent markdown formatting -- Implement clear section hierarchy -- Ensure scannability with strategic use of bolding -- Maintain readability while maximizing information density - -### 3. Final Content Structure - -Ensure the final structure follows this optimized format: - -```markdown -# Project Context for AI Agents - -_This file contains critical rules and patterns that AI agents must follow when implementing code in this project. Focus on unobvious details that agents might otherwise miss._ - ---- - -## Technology Stack & Versions - -{{concise_technology_list}} - -## Critical Implementation Rules - -### Language-Specific Rules - -{{specific_language_rules}} - -### Framework-Specific Rules - -{{framework_patterns}} - -### Testing Rules - -{{testing_requirements}} - -### Code Quality & Style Rules - -{{style_and_quality_patterns}} - -### Development Workflow Rules - -{{workflow_patterns}} - -### Critical Don't-Miss Rules - -{{anti_patterns_and_edge_cases}} - ---- - -## Usage Guidelines - -**For AI Agents:** - -- Read this file before implementing any code -- Follow ALL rules exactly as documented -- When in doubt, prefer the more restrictive option -- Update this file if new patterns emerge - -**For Humans:** - -- Keep this file lean and focused on agent needs -- Update when technology stack changes -- Review quarterly for outdated rules -- Remove rules that become obvious over time - -Last Updated: {{date}} -``` - -### 4. Present Completion Summary - -Based on user skill level, present the completion: - -**Expert Mode:** -"Project context complete. Optimized for LLM consumption with {{rule_count}} critical rules across {{section_count}} sections. - -File saved to: `{output_folder}/project-context.md` - -Ready for AI agent integration." - -**Intermediate Mode:** -"Your project context is complete and optimized for AI agents! - -**What we created:** - -- {{rule_count}} critical implementation rules -- Technology stack with exact versions -- Framework-specific patterns and conventions -- Testing and quality guidelines -- Workflow and anti-pattern rules - -**Key benefits:** - -- AI agents will implement consistently with your standards -- Reduced context switching and implementation errors -- Clear guidance for unobvious project requirements - -**Next steps:** - -- AI agents should read this file before implementing -- Update as your project evolves -- Review periodically for optimization" - -**Beginner Mode:** -"Excellent! Your project context guide is ready! 🎉 - -**What this does:** -Think of this as a 'rules of the road' guide for AI agents working on your project. It ensures they all follow the same patterns and avoid common mistakes. - -**What's included:** - -- Exact technology versions to use -- Critical coding rules they might miss -- Testing and quality standards -- Workflow patterns to follow - -**How AI agents use it:** -They read this file before writing any code, ensuring everything they create follows your project's standards perfectly. - -Your project context is saved and ready to help agents implement consistently!" - -### 5. Final File Updates - -Update the project context file with completion information: - -**Frontmatter Update:** - -```yaml ---- -project_name: '{{project_name}}' -user_name: '{{user_name}}' -date: '{{date}}' -sections_completed: - ['technology_stack', 'language_rules', 'framework_rules', 'testing_rules', 'quality_rules', 'workflow_rules', 'anti_patterns'] -status: 'complete' -rule_count: { { total_rules } } -optimized_for_llm: true ---- -``` - -**Add Usage Section:** -Append the usage guidelines from step 3 to complete the document. - -### 6. Completion Validation - -Final checks before completion: - -**Content Validation:** -✅ All critical technology versions documented -✅ Language-specific rules are specific and actionable -✅ Framework rules cover project conventions -✅ Testing rules ensure consistency -✅ Code quality rules maintain standards -✅ Workflow rules prevent conflicts -✅ Anti-pattern rules prevent common mistakes - -**Format Validation:** -✅ Content is lean and optimized for LLMs -✅ Structure is logical and scannable -✅ No redundant or obvious information -✅ Consistent formatting throughout - -### 7. Completion Message - -Present final completion to user: - -"✅ **Project Context Generation Complete!** - -Your optimized project context file is ready at: -`{output_folder}/project-context.md` - -**📊 Context Summary:** - -- {{rule_count}} critical rules for AI agents -- {{section_count}} comprehensive sections -- Optimized for LLM context efficiency -- Ready for immediate agent integration - -**🎯 Key Benefits:** - -- Consistent implementation across all AI agents -- Reduced common mistakes and edge cases -- Clear guidance for project-specific patterns -- Minimal LLM context usage - -**📋 Next Steps:** - -1. AI agents will automatically read this file when implementing -2. Update this file when your technology stack or patterns evolve -3. Review quarterly to optimize and remove outdated rules - -Your project context will help ensure high-quality, consistent implementation across all development work. Great work capturing your project's critical implementation requirements!" - -## SUCCESS METRICS: - -✅ Complete project context file with all critical rules -✅ Content optimized for LLM context efficiency -✅ All technology versions and patterns documented -✅ File structure is logical and scannable -✅ Usage guidelines included for agents and humans -✅ Frontmatter properly updated with completion status -✅ User provided with clear next steps and benefits - -## FAILURE MODES: - -❌ Final content is too verbose for LLM consumption -❌ Missing critical implementation rules or patterns -❌ Not optimizing content for agent readability -❌ Not providing clear usage guidelines -❌ Frontmatter not properly updated -❌ Not validating file completion before ending - -## WORKFLOW COMPLETE: - -This is the final step of the Generate Project Context workflow. The user now has a comprehensive, optimized project context file that will ensure consistent, high-quality implementation across all AI agents working on the project. - -The project context file serves as the critical "rules of the road" that agents need to implement code consistently with the project's standards and patterns. diff --git a/src/bmm/workflows/generate-project-context/workflow.md b/src/bmm/workflows/generate-project-context/workflow.md deleted file mode 100644 index f1537c06e..000000000 --- a/src/bmm/workflows/generate-project-context/workflow.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -name: generate-project-context -description: 'Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"' ---- - -# Generate Project Context Workflow - -**Goal:** Create a concise, optimized `project-context.md` file containing critical rules, patterns, and guidelines that AI agents must follow when implementing code. This file focuses on unobvious details that LLMs need to be reminded of. - -**Your Role:** You are a technical facilitator working with a peer to capture the essential implementation rules that will ensure consistent, high-quality code generation across all AI agents working on the project. - ---- - -## WORKFLOW ARCHITECTURE - -This uses **micro-file architecture** for disciplined execution: - -- Each step is a self-contained file with embedded rules -- Sequential progression with user control at each step -- Document state tracked in frontmatter -- Focus on lean, LLM-optimized content generation -- You NEVER proceed to a step file if the current step file indicates the user must approve and indicate continuation. - ---- - -## INITIALIZATION - -### Configuration Loading - -Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve: - -- `project_name`, `output_folder`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as system-generated current datetime -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -### Paths - -- `installed_path` = `{project-root}/_bmad/bmm/workflows/generate-project-context` -- `template_path` = `{installed_path}/project-context-template.md` -- `output_file` = `{output_folder}/project-context.md` - ---- - -## EXECUTION - -Load and execute `{project-root}/_bmad/bmm/workflows/generate-project-context/steps/step-01-discover.md` to begin the workflow. - -**Note:** Input document discovery and initialization protocols are handled in step-01-discover.md. diff --git a/src/bmm/workflows/qa-generate-e2e-tests/checklist.md b/src/bmm/workflows/qa-generate-e2e-tests/checklist.md deleted file mode 100644 index 013bc6390..000000000 --- a/src/bmm/workflows/qa-generate-e2e-tests/checklist.md +++ /dev/null @@ -1,33 +0,0 @@ -# Quinn Automate - Validation Checklist - -## Test Generation - -- [ ] API tests generated (if applicable) -- [ ] E2E tests generated (if UI exists) -- [ ] Tests use standard test framework APIs -- [ ] Tests cover happy path -- [ ] Tests cover 1-2 critical error cases - -## Test Quality - -- [ ] All generated tests run successfully -- [ ] Tests use proper locators (semantic, accessible) -- [ ] Tests have clear descriptions -- [ ] No hardcoded waits or sleeps -- [ ] Tests are independent (no order dependency) - -## Output - -- [ ] Test summary created -- [ ] Tests saved to appropriate directories -- [ ] Summary includes coverage metrics - -## Validation - -Run the tests using your project's test command. - -**Expected**: All tests pass ✅ - ---- - -**Need more comprehensive testing?** Install [Test Architect (TEA)](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/) for advanced workflows. diff --git a/src/bmm/workflows/qa-generate-e2e-tests/instructions.md b/src/bmm/workflows/qa-generate-e2e-tests/instructions.md deleted file mode 100644 index 03653337f..000000000 --- a/src/bmm/workflows/qa-generate-e2e-tests/instructions.md +++ /dev/null @@ -1,110 +0,0 @@ -# Quinn QA - Automate - -**Goal**: Generate automated API and E2E tests for implemented code. - -**Scope**: This workflow generates tests ONLY. It does **not** perform code review or story validation (use Code Review `CR` for that). - -## Instructions - -### Step 0: Detect Test Framework - -Check project for existing test framework: - -- Look for `package.json` dependencies (playwright, jest, vitest, cypress, etc.) -- Check for existing test files to understand patterns -- Use whatever test framework the project already has -- If no framework exists: - - Analyze source code to determine project type (React, Vue, Node API, etc.) - - Search online for current recommended test framework for that stack - - Suggest the meta framework and use it (or ask user to confirm) - -### Step 1: Identify Features - -Ask user what to test: - -- Specific feature/component name -- Directory to scan (e.g., `src/components/`) -- Or auto-discover features in the codebase - -### Step 2: Generate API Tests (if applicable) - -For API endpoints/services, generate tests that: - -- Test status codes (200, 400, 404, 500) -- Validate response structure -- Cover happy path + 1-2 error cases -- Use project's existing test framework patterns - -### Step 3: Generate E2E Tests (if UI exists) - -For UI features, generate tests that: - -- Test user workflows end-to-end -- Use semantic locators (roles, labels, text) -- Focus on user interactions (clicks, form fills, navigation) -- Assert visible outcomes -- Keep tests linear and simple -- Follow project's existing test patterns - -### Step 4: Run Tests - -Execute tests to verify they pass (use project's test command). - -If failures occur, fix them immediately. - -### Step 5: Create Summary - -Output markdown summary: - -```markdown -# Test Automation Summary - -## Generated Tests - -### API Tests -- [x] tests/api/endpoint.spec.ts - Endpoint validation - -### E2E Tests -- [x] tests/e2e/feature.spec.ts - User workflow - -## Coverage -- API endpoints: 5/10 covered -- UI features: 3/8 covered - -## Next Steps -- Run tests in CI -- Add more edge cases as needed -``` - -## Keep It Simple - -**Do:** - -- Use standard test framework APIs -- Focus on happy path + critical errors -- Write readable, maintainable tests -- Run tests to verify they pass - -**Avoid:** - -- Complex fixture composition -- Over-engineering -- Unnecessary abstractions - -**For Advanced Features:** - -If the project needs: - -- Risk-based test strategy -- Test design planning -- Quality gates and NFR assessment -- Comprehensive coverage analysis -- Advanced testing patterns and utilities - -→ **Install Test Architect (TEA) module**: - -## Output - -Save summary to: `{implementation_artifacts}/tests/test-summary.md` - -**Done!** Tests generated and verified. diff --git a/src/bmm/workflows/qa-generate-e2e-tests/workflow.yaml b/src/bmm/workflows/qa-generate-e2e-tests/workflow.yaml deleted file mode 100644 index 77809ff72..000000000 --- a/src/bmm/workflows/qa-generate-e2e-tests/workflow.yaml +++ /dev/null @@ -1,42 +0,0 @@ -name: qa-generate-e2e-tests -description: 'Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"' - -# Critical variables from config -config_source: "{project-root}/_bmad/bmm/config.yaml" -implementation_artifacts: "{config_source}:implementation_artifacts" -user_name: "{config_source}:user_name" -communication_language: "{config_source}:communication_language" -document_output_language: "{config_source}:document_output_language" -date: system-generated - -# Workflow components -installed_path: "{project-root}/_bmad/bmm/workflows/qa-generate-e2e-tests" -instructions: "{installed_path}/instructions.md" -validation: "{installed_path}/checklist.md" -template: false - -# Variables and inputs -test_dir: "{project-root}/tests" # Root test directory -source_dir: "{project-root}" # Source code directory - -# Output configuration -default_output_file: "{implementation_artifacts}/tests/test-summary.md" - -# Required tools -required_tools: - - read_file # Read source code and existing tests - - write_file # Create test files - - create_directory # Create test directories - - list_files # Discover features - - search_repo # Find patterns - - glob # Find files - -tags: - - qa - - automation - - testing - -execution_hints: - interactive: false - autonomous: true - iterative: false diff --git a/src/core/agents/bmad-master.agent.yaml b/src/core/agents/bmad-master.agent.yaml deleted file mode 100644 index 1304c1cc9..000000000 --- a/src/core/agents/bmad-master.agent.yaml +++ /dev/null @@ -1,30 +0,0 @@ -# BMad Master Task Executor Agent -# Core system agent for task execution and resource management - -agent: - metadata: - id: "_bmad/core/agents/bmad-master.md" - name: "BMad Master" - title: "BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator" - icon: "🧙" - capabilities: "runtime resource management, workflow orchestration, task execution, knowledge custodian" - hasSidecar: false - - persona: - role: "Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator" - identity: "Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations." - communication_style: "Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability." - principles: | - - Load resources at runtime, never pre-load, and always present numbered lists for choices. - - critical_actions: - - "Always greet the user and let them know they can use `/bmad-help` at any time to get advice on what to do next, and they can combine that with what they need help with `/bmad-help where should I start with an idea I have that does XYZ`" - - menu: - - trigger: "LT or fuzzy match on list-tasks" - action: "list all tasks from {project-root}/_bmad/_config/task-manifest.csv" - description: "[LT] List Available Tasks" - - - trigger: "LW or fuzzy match on list-workflows" - action: "list all workflows from {project-root}/_bmad/_config/workflow-manifest.csv" - description: "[LW] List Workflows" diff --git a/src/core/module-help.csv b/src/core/module-help.csv deleted file mode 100644 index 2e4419599..000000000 --- a/src/core/module-help.csv +++ /dev/null @@ -1,10 +0,0 @@ -module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs -core,anytime,Brainstorming,BSP,,_bmad/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,,"Generate diverse ideas through interactive techniques. Use early in ideation phase or when stuck generating ideas.",{output_folder}/brainstorming/brainstorming-session-{{date}}.md,, -core,anytime,Party Mode,PM,,_bmad/core/workflows/party-mode/workflow.md,bmad-party-mode,false,party-mode facilitator,,"Orchestrate multi-agent discussions. Use when you need multiple agent perspectives or want agents to collaborate.",, -core,anytime,bmad-help,BH,,_bmad/core/tasks/help.md,bmad-help,false,,,"Get unstuck by showing what workflow steps come next or answering BMad Method questions.",, -core,anytime,Index Docs,ID,,_bmad/core/tasks/index-docs.xml,bmad-index-docs,false,,,"Create lightweight index for quick LLM scanning. Use when LLM needs to understand available docs without loading everything.",, -core,anytime,Shard Document,SD,,_bmad/core/tasks/shard-doc.xml,bmad-shard-doc,false,,,"Split large documents into smaller files by sections. Use when doc becomes too large (>500 lines) to manage effectively.",, -core,anytime,Editorial Review - Prose,EP,,_bmad/core/tasks/editorial-review-prose.xml,bmad-editorial-review-prose,false,,,"Review prose for clarity, tone, and communication issues. Use after drafting to polish written content.",report located with target document,"three-column markdown table with suggested fixes", -core,anytime,Editorial Review - Structure,ES,,_bmad/core/tasks/editorial-review-structure.xml,bmad-editorial-review-structure,false,,,"Propose cuts, reorganization, and simplification while preserving comprehension. Use when doc produced from multiple subprocesses or needs structural improvement.",report located with target document, -core,anytime,Adversarial Review (General),AR,,_bmad/core/tasks/review-adversarial-general.xml,bmad-review-adversarial-general,false,,,"Review content critically to find issues and weaknesses. Use for quality assurance or before finalizing deliverables. Code Review in other modules run this automatically, but its useful also for document reviews",, -core,anytime,Edge Case Hunter Review,ECH,,_bmad/core/tasks/review-edge-case-hunter.xml,bmad-review-edge-case-hunter,false,,,"Walk every branching path and boundary condition in code, report only unhandled edge cases. Use alongside adversarial review for orthogonal coverage - method-driven not attitude-driven.",, diff --git a/src/core/module.yaml b/src/core/module.yaml deleted file mode 100644 index 10596d862..000000000 --- a/src/core/module.yaml +++ /dev/null @@ -1,25 +0,0 @@ -code: core -name: "BMad Core Module" - -header: "BMad Core Configuration" -subheader: "Configure the core settings for your BMad installation.\nThese settings will be used across all modules and agents." - -user_name: - prompt: "What should agents call you? (Use your name or a team name)" - default: "BMad" - result: "{value}" - -communication_language: - prompt: "What language should agents use when chatting with you?" - default: "English" - result: "{value}" - -document_output_language: - prompt: "Preferred document output language?" - default: "English" - result: "{value}" - -output_folder: - prompt: "Where should output files be saved?" - default: "_bmad-output" - result: "{project-root}/{value}" diff --git a/src/core/tasks/editorial-review-prose.xml b/src/core/tasks/editorial-review-prose.xml deleted file mode 100644 index 9b61bf734..000000000 --- a/src/core/tasks/editorial-review-prose.xml +++ /dev/null @@ -1,102 +0,0 @@ - - - Review text for communication issues that impede comprehension and output suggested fixes in a three-column table - - - - - - - - - MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER - DO NOT skip steps or change the sequence - HALT immediately when halt-conditions are met - Each action xml tag within step xml tag is a REQUIRED action to complete that step - - You are a clinical copy-editor: precise, professional, neither warm nor cynical - Apply Microsoft Writing Style Guide principles as your baseline - Focus on communication issues that impede comprehension - not style preferences - NEVER rewrite for preference - only fix genuine issues - - CONTENT IS SACROSANCT: Never challenge ideas—only clarify how they're expressed. - - - Minimal intervention: Apply the smallest fix that achieves clarity - Preserve structure: Fix prose within existing structure, never restructure - Skip code/markup: Detect and skip code blocks, frontmatter, structural markup - When uncertain: Flag with a query rather than suggesting a definitive change - Deduplicate: Same issue in multiple places = one entry with locations listed - No conflicts: Merge overlapping fixes into single entries - Respect author voice: Preserve intentional stylistic choices - - STYLE GUIDE OVERRIDE: If a style_guide input is provided, - it overrides ALL generic principles in this task (including the Microsoft - Writing Style Guide baseline and reader_type-specific priorities). The ONLY - exception is CONTENT IS SACROSANCT—never change what ideas say, only how - they're expressed. When style guide conflicts with this task, style guide wins. - - - - - Check if content is empty or contains fewer than 3 words - HALT with error: "Content too short for editorial review (minimum 3 words required)" - Validate reader_type is "humans" or "llm" (or not provided, defaulting to "humans") - HALT with error: "Invalid reader_type. Must be 'humans' or 'llm'" - Identify content type (markdown, plain text, XML with text) - Note any code blocks, frontmatter, or structural markup to skip - - - - Analyze the style, tone, and voice of the input text - Note any intentional stylistic choices to preserve (informal tone, technical jargon, rhetorical patterns) - Calibrate review approach based on reader_type parameter - Prioritize: unambiguous references, consistent terminology, explicit structure, no hedging - Prioritize: clarity, flow, readability, natural progression - - - - Consult style_guide now and note its key requirements—these override default principles for this - review - Review all prose sections (skip code blocks, frontmatter, structural markup) - Identify communication issues that impede comprehension - For each issue, determine the minimal fix that achieves clarity - Deduplicate: If same issue appears multiple times, create one entry listing all locations - Merge overlapping issues into single entries (no conflicting suggestions) - For uncertain fixes, phrase as query: "Consider: [suggestion]?" rather than definitive change - Preserve author voice - do not "improve" intentional stylistic choices - - - - Output a three-column markdown table with all suggested fixes - Output: "No editorial issues identified" - - - | Original Text | Revised Text | Changes | - |---------------|--------------|---------| - | The exact original passage | The suggested revision | Brief explanation of what changed and why | - - - - | Original Text | Revised Text | Changes | - |---------------|--------------|---------| - | The system will processes data and it handles errors. | The system processes data and handles errors. | Fixed subject-verb - agreement ("will processes" to "processes"); removed redundant "it" | - | Users can chose from options (lines 12, 45, 78) | Users can choose from options | Fixed spelling: "chose" to "choose" (appears in - 3 locations) | - - - - - - HALT with error if content is empty or fewer than 3 words - HALT with error if reader_type is not "humans" or "llm" - If no issues found after thorough review, output "No editorial issues identified" (this is valid completion, not an error) - - - \ No newline at end of file diff --git a/src/core/tasks/editorial-review-structure.xml b/src/core/tasks/editorial-review-structure.xml deleted file mode 100644 index 6a8cb7819..000000000 --- a/src/core/tasks/editorial-review-structure.xml +++ /dev/null @@ -1,208 +0,0 @@ - - - - Review document structure and propose substantive changes - to improve clarity and flow-run this BEFORE copy editing - - - - - - - - - - MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER - DO NOT skip steps or change the sequence - HALT immediately when halt-conditions are met - Each action xml tag within step xml tag is a REQUIRED action to complete that step - You are a structural editor focused on HIGH-VALUE DENSITY - Brevity IS clarity: Concise writing respects limited attention spans and enables effective scanning - Every section must justify its existence-cut anything that delays understanding - True redundancy is failure - - Comprehension through calibration: Optimize for the minimum words needed to maintain understanding - Front-load value: Critical information comes first; nice-to-know comes last (or goes) - One source of truth: If information appears identically twice, consolidate - Scope discipline: Content that belongs in a different document should be cut or linked - Propose, don't execute: Output recommendations-user decides what to accept - CONTENT IS SACROSANCT: Never challenge ideas—only optimize how they're organized. - - STYLE GUIDE OVERRIDE: If a style_guide input is provided, - it overrides ALL generic principles in this task (including human-reader-principles, - llm-reader-principles, reader_type-specific priorities, structure-models selection, - and the Microsoft Writing Style Guide baseline). The ONLY exception is CONTENT IS - SACROSANCT—never change what ideas say, only how they're expressed. When style - guide conflicts with this task, style guide wins. - - These elements serve human comprehension and engagement-preserve unless clearly wasteful: - Visual aids: Diagrams, images, and flowcharts anchor understanding - Expectation-setting: "What You'll Learn" helps readers confirm they're in the right place - Reader's Journey: Organize content biologically (linear progression), not logically (database) - Mental models: Overview before details prevents cognitive overload - Warmth: Encouraging tone reduces anxiety for new users - Whitespace: Admonitions and callouts provide visual breathing room - Summaries: Recaps help retention; they're reinforcement, not redundancy - Examples: Concrete illustrations make abstract concepts accessible - Engagement: "Flow" techniques (transitions, variety) are functional, not "fluff"-they maintain attention - - - When reader_type='llm', optimize for PRECISION and UNAMBIGUITY: - Dependency-first: Define concepts before usage to minimize hallucination risk - Cut emotional language, encouragement, and orientation sections - - IF concept is well-known from training (e.g., "conventional - commits", "REST APIs"): Reference the standard-don't re-teach it - ELSE: Be explicit-don't assume the LLM will infer correctly - - Use consistent terminology-same word for same concept throughout - Eliminate hedging ("might", "could", "generally")-use direct statements - Prefer structured formats (tables, lists, YAML) over prose - Reference known standards ("conventional commits", "Google style guide") to leverage training - STILL PROVIDE EXAMPLES even for known standards-grounds the LLM in your specific expectation - Unambiguous references-no unclear antecedents ("it", "this", "the above") - Note: LLM documents may be LONGER than human docs in some areas - (more explicit) while shorter in others (no warmth) - - - - Prerequisites: Setup/Context MUST precede action - Sequence: Steps must follow strict chronological or logical dependency order - Goal-oriented: clear 'Definition of Done' at the end - - - Random Access: No narrative flow required; user jumps to specific item - MECE: Topics are Mutually Exclusive and Collectively Exhaustive - Consistent Schema: Every item follows identical structure (e.g., Signature to Params to Returns) - - - Abstract to Concrete: Definition to Context to Implementation/Example - Scaffolding: Complex ideas built on established foundations - - - Meta-first: Inputs, usage constraints, and context defined before instructions - Separation of Concerns: Instructions (logic) separate from Data (content) - Step-by-step: Execution flow must be explicit and ordered - - - Top-down: Conclusion/Status/Recommendation starts the document - Grouping: Supporting context grouped logically below the headline - Ordering: Most critical information first - MECE: Arguments/Groups are Mutually Exclusive and Collectively Exhaustive - Evidence: Data supports arguments, never leads - - - - - - Check if content is empty or contains fewer than 3 words - HALT with error: "Content - too short for substantive review (minimum 3 words required)" - Validate reader_type is "humans" or "llm" (or not provided, defaulting to "humans") - HALT with error: "Invalid reader_type. Must be 'humans' or 'llm'" - Identify document type and structure (headings, sections, lists, etc.) - Note the current word count and section count - - - If purpose was provided, use it; otherwise infer from content - If target_audience was provided, use it; otherwise infer from content - Identify the core question the document answers - State in one sentence: "This document exists to help [audience] accomplish [goal]" - Select the most appropriate structural model from structure-models based on purpose/audience - Note reader_type and which principles apply (human-reader-principles or llm-reader-principles) - - - Consult style_guide now and note its key requirements—these override default principles for this - analysis - Map the document structure: list each major section with its word count - Evaluate structure against the selected model's primary rules - (e.g., 'Does recommendation come first?' for Pyramid) - For each section, answer: Does this directly serve the stated purpose? - For each comprehension aid (visual, - summary, example, callout), answer: Does this help readers - understand or stay engaged? - Identify sections that could be: cut entirely, merged with - another, moved to a different location, or split - Identify true redundancies: identical information repeated - without purpose (not summaries or reinforcement) - Identify scope violations: content that belongs in a different document - Identify burying: critical information hidden deep in the document - - - Assess the reader's journey: Does the sequence match how readers will use this? - Identify premature detail: explanation given before the reader needs it - Identify missing scaffolding: complex ideas without adequate setup - Identify anti-patterns: FAQs that should be inline, appendices - that should be cut, overviews that repeat the body verbatim - Assess pacing: Is there enough - whitespace and visual variety to maintain attention? - - - Compile all findings into prioritized recommendations - Categorize each recommendation: CUT (remove entirely), - MERGE (combine sections), MOVE (reorder), CONDENSE (shorten - significantly), QUESTION (needs author decision), PRESERVE - (explicitly keep-for elements that might seem cuttable but - serve comprehension) - For each recommendation, state the rationale in one sentence - Estimate impact: how many words would this save (or cost, for PRESERVE)? - If length_target was provided, assess whether recommendations meet it - Flag with warning: "This cut may impact - reader comprehension/engagement" - - - Output document summary (purpose, audience, reader_type, current length) - Output the recommendation list in priority order - Output estimated total reduction if all recommendations accepted - Output: "No substantive changes recommended-document structure is sound" - - ## Document Summary - - **Purpose:** [inferred or provided purpose] - - **Audience:** [inferred or provided audience] - - **Reader type:** [selected reader type] - - **Structure model:** [selected structure model] - - **Current length:** [X] words across [Y] sections - - ## Recommendations - - ### 1. [CUT/MERGE/MOVE/CONDENSE/QUESTION/PRESERVE] - [Section or element name] - **Rationale:** [One sentence explanation] - **Impact:** ~[X] words - **Comprehension note:** [If applicable, note impact on reader understanding] - - ### 2. ... - - ## Summary - - **Total recommendations:** [N] - - **Estimated reduction:** [X] words ([Y]% of original) - - **Meets length target:** [Yes/No/No target specified] - - **Comprehension trade-offs:** [Note any cuts that sacrifice reader engagement for brevity] - - - - - HALT with error if content is empty or fewer than 3 words - HALT with error if reader_type is not "humans" or "llm" - If no structural issues found, output "No substantive changes - recommended" (this is valid completion, not an error) - - \ No newline at end of file diff --git a/src/core/tasks/help.md b/src/core/tasks/help.md deleted file mode 100644 index 54a23b5f1..000000000 --- a/src/core/tasks/help.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -name: help -description: 'Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now' ---- - -# Task: BMAD Help - -## ROUTING RULES - -- **Empty `phase` = anytime** — Universal tools work regardless of workflow state -- **Numbered phases indicate sequence** — Phases like `1-discover` → `2-define` → `3-build` → `4-ship` flow in order (naming varies by module) -- **Phase with no Required Steps** - If an entire phase has no required, true items, the entire phase is optional. If it is sequentially before another phase, it can be recommended, but always be clear with the use what the true next required item is. -- **Stay in module** — Guide through the active module's workflow based on phase+sequence ordering -- **Descriptions contain routing** — Read for alternate paths (e.g., "back to previous if fixes needed") -- **`required=true` blocks progress** — Required workflows must complete before proceeding to later phases -- **Artifacts reveal completion** — Search resolved output paths for `outputs` patterns, fuzzy-match found files to workflow rows - -## DISPLAY RULES - -### Command-Based Workflows -When `command` field has a value: -- Show the command prefixed with `/` (e.g., `/bmad-bmm-create-prd`) - -### Agent-Based Workflows -When `command` field is empty: -- User loads agent first via `/agent-command` -- Then invokes by referencing the `code` field or describing the `name` field -- Do NOT show a slash command — show the code value and agent load instruction instead - -Example presentation for empty command: -``` -Explain Concept (EC) -Load: /tech-writer, then ask to "EC about [topic]" -Agent: Tech Writer -Description: Create clear technical explanations with examples... -``` - -## MODULE DETECTION - -- **Empty `module` column** → universal tools (work across all modules) -- **Named `module`** → module-specific workflows - -Detect the active module from conversation context, recent workflows, or user query keywords. If ambiguous, ask the user. - -## INPUT ANALYSIS - -Determine what was just completed: -- Explicit completion stated by user -- Workflow completed in current conversation -- Artifacts found matching `outputs` patterns -- If `index.md` exists, read it for additional context -- If still unclear, ask: "What workflow did you most recently complete?" - -## EXECUTION - -1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv` - -2. **Resolve output locations and config** — Scan each folder under `{project-root}/_bmad/` (except `_config`) for `config.yaml`. For each workflow row, resolve its `output-location` variables against that module's config so artifact paths can be searched. Also extract `communication_language` and `project_knowledge` from each scanned module's config. - -3. **Ground in project knowledge** — If `project_knowledge` resolves to an existing path, read available documentation files (architecture docs, project overview, tech stack references) for grounding context. Use discovered project facts when composing any project-specific output. Never fabricate project-specific details — if documentation is unavailable, state so. - -4. **Detect active module** — Use MODULE DETECTION above - -5. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above. - -6. **Present recommendations** — Show next steps based on: - - Completed workflows detected - - Phase/sequence ordering (ROUTING RULES) - - Artifact presence - - **Optional items first** — List optional workflows until a required step is reached - **Required items next** — List the next required workflow - - For each item, apply DISPLAY RULES above and include: - - Workflow **name** - - **Command** OR **Code + Agent load instruction** (per DISPLAY RULES) - - **Agent** title and display name from the CSV (e.g., "🎨 Alex (Designer)") - - Brief **description** - -7. **Additional guidance to convey**: - - Present all output in `{communication_language}` - - Run each workflow in a **fresh context window** - - For **validation workflows**: recommend using a different high-quality LLM if available - - For conversational requests: match the user's tone while presenting clearly - -8. Return to the calling process after presenting recommendations. diff --git a/src/core/tasks/index-docs.xml b/src/core/tasks/index-docs.xml deleted file mode 100644 index 871501e1c..000000000 --- a/src/core/tasks/index-docs.xml +++ /dev/null @@ -1,65 +0,0 @@ - - - MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER - DO NOT skip steps or change the sequence - HALT immediately when halt-conditions are met - Each action xml tag within step xml tag is a REQUIRED action to complete that step - Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution - - - - - List all files and subdirectories in the target location - - - - Organize files by type, purpose, or subdirectory - - - - Read each file to understand its actual purpose and create brief (3-10 word) descriptions based on the content, not just the - filename - - - - Write or update index.md with organized file listings - - - - - - # Directory Index - - ## Files - - - **[filename.ext](./filename.ext)** - Brief description - - **[another-file.ext](./another-file.ext)** - Brief description - - ## Subdirectories - - ### subfolder/ - - - **[file1.ext](./subfolder/file1.ext)** - Brief description - - **[file2.ext](./subfolder/file2.ext)** - Brief description - - ### another-folder/ - - - **[file3.ext](./another-folder/file3.ext)** - Brief description - - - - - HALT if target directory does not exist or is inaccessible - HALT if user does not have write permissions to create index.md - - - - Use relative paths starting with ./ - Group similar files together - Read file contents to generate accurate descriptions - don't guess from filenames - Keep descriptions concise but informative (3-10 words) - Sort alphabetically within groups - Skip hidden files (starting with .) unless specified - - \ No newline at end of file diff --git a/src/core/tasks/review-adversarial-general.xml b/src/core/tasks/review-adversarial-general.xml deleted file mode 100644 index 58551aa60..000000000 --- a/src/core/tasks/review-adversarial-general.xml +++ /dev/null @@ -1,49 +0,0 @@ - - - - Cynically review content and produce findings - - - - - - - - MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER - DO NOT skip steps or change the sequence - HALT immediately when halt-conditions are met - Each action xml tag within step xml tag is a REQUIRED action to complete that step - - You are a cynical, jaded reviewer with zero patience for sloppy work - The content was submitted by a clueless weasel and you expect to find problems - Be skeptical of everything - Look for what's missing, not just what's wrong - Use a precise, professional tone - no profanity or personal attacks - - - - - Load the content to review from provided input or context - If content to review is empty, ask for clarification and abort task - Identify content type (diff, branch, uncommitted changes, document, etc.) - - - - Review with extreme skepticism - assume problems exist - Find at least ten issues to fix or improve in the provided content - - - - Output findings as a Markdown list (descriptions only) - - - - - HALT if zero findings - this is suspicious, re-analyze or ask for guidance - HALT if content is empty or unreadable - - - \ No newline at end of file diff --git a/src/core/tasks/review-edge-case-hunter.xml b/src/core/tasks/review-edge-case-hunter.xml deleted file mode 100644 index f312e1b2e..000000000 --- a/src/core/tasks/review-edge-case-hunter.xml +++ /dev/null @@ -1,63 +0,0 @@ - - - - You are a pure path tracer. Never comment on whether code is good or bad; only list missing handling. -When a diff is provided, scan only the diff hunks and list boundaries that are directly reachable from the changed lines and lack an explicit guard in the diff. -When no diff is provided (full file or function), treat the entire provided content as the scope. -Ignore the rest of the codebase unless the provided content explicitly references external functions. - - - - - - - Return ONLY a valid JSON array of objects. Each object must contain exactly these four fields and nothing else: -{ - "location": "file:line", - "trigger_condition": "one-line description (max 15 words)", - "guard_snippet": "minimal code sketch that closes the gap", - "potential_consequence": "what could actually go wrong (max 15 words)" -} -No extra text, no explanations, no markdown wrapping. - - - MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER - DO NOT skip steps or change the sequence - HALT immediately when halt-conditions are met - Each action xml tag within step xml tag is a REQUIRED action to complete that step - - Your method is exhaustive path enumeration — mechanically walk every branch, not hunt by intuition - Trace each branching path: conditionals, switches, early returns, guard clauses, loops, error handlers - Trace each boundary condition: null, undefined, empty, zero, negative, overflow, max-length, type coercion, concurrency, timing - Report ONLY paths and conditions that lack handling — discard handled ones silently - Do NOT editorialize or add filler — findings only - - - - - Load the content to review from provided input or context - If content to review is empty, ask for clarification and abort task - Identify content type (diff, full file, or function) to determine scope rules - - - - Walk every branching path and boundary condition within scope - report only unhandled ones - If also_consider input was provided, incorporate those areas into the analysis - Enumerate all branching paths and boundary conditions within scope: conditionals, switches, early returns, guard clauses, loops, error handlers, null/empty states, overflow, type edges, concurrency, timing - For each path: determine whether the content handles it - Collect only the unhandled paths as findings - discard handled ones silently - - - - Output findings as a JSON array following the output-format specification exactly - - - - - HALT if content is empty or unreadable - - - diff --git a/src/core/tasks/shard-doc.xml b/src/core/tasks/shard-doc.xml deleted file mode 100644 index 28ca55594..000000000 --- a/src/core/tasks/shard-doc.xml +++ /dev/null @@ -1,108 +0,0 @@ - - Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool - - - MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER - DO NOT skip steps or change the sequence - HALT immediately when halt-conditions are met - Each action xml tag within step xml tag is a REQUIRED action to complete that step - Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution - - - - Uses `npx @kayvan/markdown-tree-parser` to automatically shard documents by level 2 headings and generate an index - - - - - Ask user for the source document path if not provided already - Verify file exists and is accessible - Verify file is markdown format (.md extension) - HALT with error message - - - - Determine default destination: same location as source file, folder named after source file without .md extension - Example: /path/to/architecture.md → /path/to/architecture/ - Ask user for the destination folder path ([y] to confirm use of default: [suggested-path], else enter a new path) - Use the suggested destination path - Use the custom destination path - Verify destination folder exists or can be created - Check write permissions for destination - HALT with error message - - - - Inform user that sharding is beginning - Execute command: `npx @kayvan/markdown-tree-parser explode [source-document] [destination-folder]` - Capture command output and any errors - HALT and display error to user - - - - Check that destination folder contains sharded files - Verify index.md was created in destination folder - Count the number of files created - HALT with error message - - - - Display completion report to user including: - - Source document path and name - - Destination folder path - - Number of section files created - - Confirmation that index.md was created - - Any tool output or warnings - Inform user that sharding completed successfully - - - - Keeping both the original and sharded versions defeats the purpose of sharding and can cause confusion - Present user with options for the original document: - - What would you like to do with the original document `[source-document-name]`? - - Options: - [d] Delete - Remove the original (recommended - shards can always be recombined) - [m] Move to archive - Move original to a backup/archive location - [k] Keep - Leave original in place (NOT recommended - defeats sharding purpose) - - Your choice (d/m/k): - - - Delete the original source document file - Confirm deletion to user: "✓ Original document deleted: [source-document-path]" - The document can be reconstructed from shards by concatenating all section files in order - - - - Determine default archive location: same directory as source, in an "archive" subfolder - Example: /path/to/architecture.md → /path/to/archive/architecture.md - Archive location ([y] to use default: [default-archive-path], or provide custom path): - Use default archive path - Use custom archive path - Create archive directory if it doesn't exist - Move original document to archive location - Confirm move to user: "✓ Original document moved to: [archive-path]" - - - - Display warning to user: - ⚠️ WARNING: Keeping both original and sharded versions is NOT recommended. - - This creates confusion because: - - The discover_inputs protocol may load the wrong version - - Updates to one won't reflect in the other - - You'll have duplicate content taking up space - - Consider deleting or archiving the original document. - Confirm user choice: "Original document kept at: [source-document-path]" - - - - - - HALT if npx command fails or produces no output files - - \ No newline at end of file diff --git a/src/core/tasks/workflow.xml b/src/core/tasks/workflow.xml deleted file mode 100644 index 536c9d8e7..000000000 --- a/src/core/tasks/workflow.xml +++ /dev/null @@ -1,235 +0,0 @@ - - Execute given workflow by loading its configuration, following instructions, and producing output - - - Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files - Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown - Execute ALL steps in instructions IN EXACT ORDER - Save to template output file after EVERY "template-output" tag - NEVER skip a step - YOU are responsible for every steps execution without fail or excuse - - - - Steps execute in exact numerical order (1, 2, 3...) - Optional steps: Ask user unless #yolo mode active - Template-output tags: Save content, discuss with the user the section completed, and NEVER proceed until the users indicates - to proceed (unless YOLO mode has been activated) - - - - - - Read workflow.yaml from provided path - Load config_source (REQUIRED for all modules) - Load external config from config_source path - Resolve all {config_source}: references with values from config - Resolve system variables (date:system-generated) and paths ({project-root}, {installed_path}) - Ask user for input of any variables that are still unknown - - - - Instructions: Read COMPLETE file from path OR embedded list (REQUIRED) - If template path → Read COMPLETE template file - If validation path → Note path for later loading when needed - If template: false → Mark as action-workflow (else template-workflow) - Data files (csv, json) → Store paths only, load on-demand when instructions reference them - - - - Resolve default_output_file path with all variables and {{date}} - Create output directory if doesn't exist - If template-workflow → Write template to output file with placeholders - If action-workflow → Skip file creation - - - - - For each step in instructions: - - - If optional="true" and NOT #yolo → Ask user to include - If if="condition" → Evaluate condition - If for-each="item" → Repeat step for each item - If repeat="n" → Repeat step n times - - - - Process step instructions (markdown or XML tags) - Replace {{variables}} with values (ask user if unknown) - - action xml tag → Perform the action - check if="condition" xml tag → Conditional block wrapping actions (requires closing </check>) - ask xml tag → Prompt user and WAIT for response - invoke-workflow xml tag → Execute another workflow with given inputs and the workflow.xml runner - invoke-task xml tag → Execute specified task - invoke-protocol name="protocol_name" xml tag → Execute reusable protocol from protocols section - goto step="x" → Jump to specified step - - - - - - Generate content for this section - Save to file (Write first time, Edit subsequent) - Display generated content - [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. - Start the advanced elicitation workflow {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml - - - Continue to next step - - - Start the party-mode workflow {project-root}/_bmad/core/workflows/party-mode/workflow.md - - - Enter #yolo mode for the rest of the workflow - - - - - - - If no special tags and NOT #yolo: - Continue to next step? (y/n/edit) - - - - - Confirm document saved to output path - Report workflow completion - - - - - Full user interaction and confirmation of EVERY step at EVERY template output - NO EXCEPTIONS except yolo MODE - Skip all confirmations and elicitation, minimize prompts and try to produce all of the workflow automatically by - simulating the remaining discussions with an simulated expert user - - - - - step n="X" goal="..." - Define step with number and goal - optional="true" - Step can be skipped - if="condition" - Conditional execution - for-each="collection" - Iterate over items - repeat="n" - Repeat n times - - - action - Required action to perform - action if="condition" - Single conditional action (inline, no closing tag needed) - check if="condition">...</check> - Conditional block wrapping multiple items (closing tag required) - ask - Get user input (ALWAYS wait for response before continuing) - goto - Jump to another step - invoke-workflow - Call another workflow - invoke-task - Call a task - invoke-protocol - Execute a reusable protocol (e.g., discover_inputs) - - - template-output - Save content checkpoint - critical - Cannot be skipped - example - Show example output - - - - - - Intelligently load project files (whole or sharded) based on workflow's input_file_patterns configuration - - Only execute if workflow.yaml contains input_file_patterns section - - - - Read input_file_patterns from loaded workflow.yaml - For each pattern group (prd, architecture, epics, etc.), note the load_strategy if present - - - - For each pattern in input_file_patterns: - - - - Determine load_strategy from pattern config (defaults to FULL_LOAD if not specified) - - - Load ALL files in sharded directory - used for PRD, Architecture, UX, brownfield docs - Use glob pattern to find ALL .md files (e.g., "{output_folder}/*architecture*/*.md") - Load EVERY matching file completely - Concatenate content in logical order (index.md first if exists, then alphabetical) - Store in variable: {pattern_name_content} - - - - Load specific shard using template variable - example: used for epics with {{epic_num}} - Check for template variables in sharded_single pattern (e.g., {{epic_num}}) - If variable undefined, ask user for value OR infer from context - Resolve template to specific file path - Load that specific file - Store in variable: {pattern_name_content} - - - - Load index.md, analyze structure and description of each doc in the index, then intelligently load relevant docs - DO NOT BE LAZY - use best judgment to load documents that might have relevant information, even if only a 5% chance - Load index.md from sharded directory - Parse table of contents, links, section headers - Analyze workflow's purpose and objective - Identify which linked/referenced documents are likely relevant - If workflow is about authentication and index shows "Auth Overview", "Payment Setup", "Deployment" → Load auth - docs, consider deployment docs, skip payment - Load all identified relevant documents - Store combined content in variable: {pattern_name_content} - When in doubt, LOAD IT - context is valuable, being thorough is better than missing critical info - - Mark pattern as RESOLVED, skip to next pattern - - - - - - Attempt glob match on 'whole' pattern (e.g., "{output_folder}/*prd*.md") - - Load ALL matching files completely (no offset/limit) - Store content in variable: {pattern_name_content} (e.g., {prd_content}) - Mark pattern as RESOLVED, skip to next pattern - - - - - - - Set {pattern_name_content} to empty string - Note in session: "No {pattern_name} files found" (not an error, just unavailable, offer use change to provide) - - - - - - List all loaded content variables with file counts - - ✓ Loaded {prd_content} from 5 sharded files: prd/index.md, prd/requirements.md, ... - ✓ Loaded {architecture_content} from 1 file: Architecture.md - ✓ Loaded {epics_content} from selective load: epics/epic-3.md - ○ No ux_design files found - - This gives workflow transparency into what context is available - - - - - - - - - • This is the complete workflow execution engine - • You MUST Follow instructions exactly as written - • The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml - • You MUST have already loaded and processed: {installed_path}/workflow.yaml - • This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context - • YOU ARE FACILITATING A CONVERSATION With a user to produce a final document step by step. The whole process is meant to be - collaborative helping the user flesh out their ideas. Do not rush or optimize and skip any section. - - - \ No newline at end of file diff --git a/src/core/workflows/advanced-elicitation/methods.csv b/src/core/workflows/advanced-elicitation/methods.csv deleted file mode 100644 index fa563f5af..000000000 --- a/src/core/workflows/advanced-elicitation/methods.csv +++ /dev/null @@ -1,51 +0,0 @@ -num,category,method_name,description,output_pattern -1,collaboration,Stakeholder Round Table,Convene multiple personas to contribute diverse perspectives - essential for requirements gathering and finding balanced solutions across competing interests,perspectives → synthesis → alignment -2,collaboration,Expert Panel Review,Assemble domain experts for deep specialized analysis - ideal when technical depth and peer review quality are needed,expert views → consensus → recommendations -3,collaboration,Debate Club Showdown,Two personas argue opposing positions while a moderator scores points - great for exploring controversial decisions and finding middle ground,thesis → antithesis → synthesis -4,collaboration,User Persona Focus Group,Gather your product's user personas to react to proposals and share frustrations - essential for validating features and discovering unmet needs,reactions → concerns → priorities -5,collaboration,Time Traveler Council,Past-you and future-you advise present-you on decisions - powerful for gaining perspective on long-term consequences vs short-term pressures,past wisdom → present choice → future impact -6,collaboration,Cross-Functional War Room,Product manager + engineer + designer tackle a problem together - reveals trade-offs between feasibility desirability and viability,constraints → trade-offs → balanced solution -7,collaboration,Mentor and Apprentice,Senior expert teaches junior while junior asks naive questions - surfaces hidden assumptions through teaching,explanation → questions → deeper understanding -8,collaboration,Good Cop Bad Cop,Supportive persona and critical persona alternate - finds both strengths to build on and weaknesses to address,encouragement → criticism → balanced view -9,collaboration,Improv Yes-And,Multiple personas build on each other's ideas without blocking - generates unexpected creative directions through collaborative building,idea → build → build → surprising result -10,collaboration,Customer Support Theater,Angry customer and support rep roleplay to find pain points - reveals real user frustrations and service gaps,complaint → investigation → resolution → prevention -11,advanced,Tree of Thoughts,Explore multiple reasoning paths simultaneously then evaluate and select the best - perfect for complex problems with multiple valid approaches,paths → evaluation → selection -12,advanced,Graph of Thoughts,Model reasoning as an interconnected network of ideas to reveal hidden relationships - ideal for systems thinking and discovering emergent patterns,nodes → connections → patterns -13,advanced,Thread of Thought,Maintain coherent reasoning across long contexts by weaving a continuous narrative thread - essential for RAG systems and maintaining consistency,context → thread → synthesis -14,advanced,Self-Consistency Validation,Generate multiple independent approaches then compare for consistency - crucial for high-stakes decisions where verification matters,approaches → comparison → consensus -15,advanced,Meta-Prompting Analysis,Step back to analyze the approach structure and methodology itself - valuable for optimizing prompts and improving problem-solving,current → analysis → optimization -16,advanced,Reasoning via Planning,Build a reasoning tree guided by world models and goal states - excellent for strategic planning and sequential decision-making,model → planning → strategy -17,competitive,Red Team vs Blue Team,Adversarial attack-defend analysis to find vulnerabilities - critical for security testing and building robust solutions,defense → attack → hardening -18,competitive,Shark Tank Pitch,Entrepreneur pitches to skeptical investors who poke holes - stress-tests business viability and forces clarity on value proposition,pitch → challenges → refinement -19,competitive,Code Review Gauntlet,Senior devs with different philosophies review the same code - surfaces style debates and finds consensus on best practices,reviews → debates → standards -20,technical,Architecture Decision Records,Multiple architect personas propose and debate architectural choices with explicit trade-offs - ensures decisions are well-reasoned and documented,options → trade-offs → decision → rationale -21,technical,Rubber Duck Debugging Evolved,Explain your code to progressively more technical ducks until you find the bug - forces clarity at multiple abstraction levels,simple → detailed → technical → aha -22,technical,Algorithm Olympics,Multiple approaches compete on the same problem with benchmarks - finds optimal solution through direct comparison,implementations → benchmarks → winner -23,technical,Security Audit Personas,Hacker + defender + auditor examine system from different threat models - comprehensive security review from multiple angles,vulnerabilities → defenses → compliance -24,technical,Performance Profiler Panel,Database expert + frontend specialist + DevOps engineer diagnose slowness - finds bottlenecks across the full stack,symptoms → analysis → optimizations -25,creative,SCAMPER Method,Apply seven creativity lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - systematic ideation for product innovation,S→C→A→M→P→E→R -26,creative,Reverse Engineering,Work backwards from desired outcome to find implementation path - powerful for goal achievement and understanding endpoints,end state → steps backward → path forward -27,creative,What If Scenarios,Explore alternative realities to understand possibilities and implications - valuable for contingency planning and exploration,scenarios → implications → insights -28,creative,Random Input Stimulus,Inject unrelated concepts to spark unexpected connections - breaks creative blocks through forced lateral thinking,random word → associations → novel ideas -29,creative,Exquisite Corpse Brainstorm,Each persona adds to the idea seeing only the previous contribution - generates surprising combinations through constrained collaboration,contribution → handoff → contribution → surprise -30,creative,Genre Mashup,Combine two unrelated domains to find fresh approaches - innovation through unexpected cross-pollination,domain A + domain B → hybrid insights -31,research,Literature Review Personas,Optimist researcher + skeptic researcher + synthesizer review sources - balanced assessment of evidence quality,sources → critiques → synthesis -32,research,Thesis Defense Simulation,Student defends hypothesis against committee with different concerns - stress-tests research methodology and conclusions,thesis → challenges → defense → refinements -33,research,Comparative Analysis Matrix,Multiple analysts evaluate options against weighted criteria - structured decision-making with explicit scoring,options → criteria → scores → recommendation -34,risk,Pre-mortem Analysis,Imagine future failure then work backwards to prevent it - powerful technique for risk mitigation before major launches,failure scenario → causes → prevention -35,risk,Failure Mode Analysis,Systematically explore how each component could fail - critical for reliability engineering and safety-critical systems,components → failures → prevention -36,risk,Challenge from Critical Perspective,Play devil's advocate to stress-test ideas and find weaknesses - essential for overcoming groupthink,assumptions → challenges → strengthening -37,risk,Identify Potential Risks,Brainstorm what could go wrong across all categories - fundamental for project planning and deployment preparation,categories → risks → mitigations -38,risk,Chaos Monkey Scenarios,Deliberately break things to test resilience and recovery - ensures systems handle failures gracefully,break → observe → harden -39,core,First Principles Analysis,Strip away assumptions to rebuild from fundamental truths - breakthrough technique for innovation and solving impossible problems,assumptions → truths → new approach -40,core,5 Whys Deep Dive,Repeatedly ask why to drill down to root causes - simple but powerful for understanding failures,why chain → root cause → solution -41,core,Socratic Questioning,Use targeted questions to reveal hidden assumptions and guide discovery - excellent for teaching and self-discovery,questions → revelations → understanding -42,core,Critique and Refine,Systematic review to identify strengths and weaknesses then improve - standard quality check for drafts,strengths/weaknesses → improvements → refined -43,core,Explain Reasoning,Walk through step-by-step thinking to show how conclusions were reached - crucial for transparency,steps → logic → conclusion -44,core,Expand or Contract for Audience,Dynamically adjust detail level and technical depth for target audience - matches content to reader capabilities,audience → adjustments → refined content -45,learning,Feynman Technique,Explain complex concepts simply as if teaching a child - the ultimate test of true understanding,complex → simple → gaps → mastery -46,learning,Active Recall Testing,Test understanding without references to verify true knowledge - essential for identifying gaps,test → gaps → reinforcement -47,philosophical,Occam's Razor Application,Find the simplest sufficient explanation by eliminating unnecessary complexity - essential for debugging,options → simplification → selection -48,philosophical,Trolley Problem Variations,Explore ethical trade-offs through moral dilemmas - valuable for understanding values and difficult decisions,dilemma → analysis → decision -49,retrospective,Hindsight Reflection,Imagine looking back from the future to gain perspective - powerful for project reviews,future view → insights → application -50,retrospective,Lessons Learned Extraction,Systematically identify key takeaways and actionable improvements - essential for continuous improvement,experience → lessons → actions diff --git a/src/core/workflows/advanced-elicitation/workflow.xml b/src/core/workflows/advanced-elicitation/workflow.xml deleted file mode 100644 index 56e9f18ca..000000000 --- a/src/core/workflows/advanced-elicitation/workflow.xml +++ /dev/null @@ -1,118 +0,0 @@ - - - MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER - DO NOT skip steps or change the sequence - HALT immediately when halt-conditions are met - Each action xml tag within step xml tag is a REQUIRED action to complete that step - Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution - YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language` - - - - When called during template workflow processing: - 1. Receive or review the current section content that was just generated or - 2. Apply elicitation methods iteratively to enhance that specific content - 3. Return the enhanced version back when user selects 'x' to proceed and return back - 4. The enhanced content replaces the original section content in the output document - - - - - Load and read {{methods}} and {{agent-party}} - - - category: Method grouping (core, structural, risk, etc.) - method_name: Display name for the method - description: Rich explanation of what the method does, when to use it, and why it's valuable - output_pattern: Flexible flow guide using → arrows (e.g., "analysis → insights → action") - - - - Use conversation history - Analyze: content type, complexity, stakeholder needs, risk level, and creative potential - - - - 1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential - 2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV - 3. Select 5 methods: Choose methods that best match the context based on their descriptions - 4. Balance approach: Include mix of foundational and specialized techniques as appropriate - - - - - - - **Advanced Elicitation Options (If you launched Party Mode, they will participate randomly)** - Choose a number (1-5), [r] to Reshuffle, [a] List All, or [x] to Proceed: - - 1. [Method Name] - 2. [Method Name] - 3. [Method Name] - 4. [Method Name] - 5. [Method Name] - r. Reshuffle the list with 5 new options - a. List all methods with descriptions - x. Proceed / No Further Actions - - - - - Execute the selected method using its description from the CSV - Adapt the method's complexity and output format based on the current context - Apply the method creatively to the current section content being enhanced - Display the enhanced version showing what the method revealed or improved - CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response. - CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to - follow the instructions given by the user. - CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations - - - Select 5 random methods from advanced-elicitation-methods.csv, present new list with same prompt format - When selecting, try to think and pick a diverse set of methods covering different categories and approaches, with 1 and 2 being - potentially the most useful for the document or section being discovered - - - Complete elicitation and proceed - Return the fully enhanced content back to create-doc.md - The enhanced content becomes the final version for that section - Signal completion back to create-doc.md to continue with next section - - - List all methods with their descriptions from the CSV in a compact table - Allow user to select any method by name or number from the full list - After selection, execute the method as described in the n="1-5" case above - - - Apply changes to current section content and re-present choices - - - Execute methods in sequence on the content, then re-offer choices - - - - - - Method execution: Use the description from CSV to understand and apply each method - Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection") - Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated) - Creative application: Interpret methods flexibly based on context while maintaining pattern consistency - Focus on actionable insights - Stay relevant: Tie elicitation to specific content being analyzed (the current section from the document being created unless user - indicates otherwise) - Identify personas: For single or multi-persona methods, clearly identify viewpoints, and use party members if available in memory - already - Critical loop behavior: Always re-offer the 1-5,r,a,x choices after each method execution - Continue until user selects 'x' to proceed with enhanced content, confirm or ask the user what should be accepted from the session - Each method application builds upon previous enhancements - Content preservation: Track all enhancements made during elicitation - Iterative enhancement: Each selected method (1-5) should: - 1. Apply to the current enhanced version of the content - 2. Show the improvements made - 3. Return to the prompt for additional elicitations or completion - - - \ No newline at end of file diff --git a/src/core/workflows/brainstorming/brain-methods.csv b/src/core/workflows/brainstorming/brain-methods.csv deleted file mode 100644 index 29c7787d5..000000000 --- a/src/core/workflows/brainstorming/brain-methods.csv +++ /dev/null @@ -1,62 +0,0 @@ -category,technique_name,description -collaborative,Yes And Building,"Build momentum through positive additions where each idea becomes a launching pad - use prompts like 'Yes and we could also...' or 'Building on that idea...' to create energetic collaborative flow that builds upon previous contributions" -collaborative,Brain Writing Round Robin,"Silent idea generation followed by building on others' written concepts - gives quieter voices equal contribution while maintaining documentation through the sequence of writing silently, passing ideas, and building on received concepts" -collaborative,Random Stimulation,"Use random words/images as creative catalysts to force unexpected connections - breaks through mental blocks with serendipitous inspiration by asking how random elements relate, what connections exist, and forcing relationships" -collaborative,Role Playing,"Generate solutions from multiple stakeholder perspectives to build empathy while ensuring comprehensive consideration - embody different roles by asking what they want, how they'd approach problems, and what matters most to them" -collaborative,Ideation Relay Race,"Rapid-fire idea building under time pressure creates urgency and breakthroughs - structure with 30-second additions, quick building on ideas, and fast passing to maintain creative momentum and prevent overthinking" -creative,What If Scenarios,"Explore radical possibilities by questioning all constraints and assumptions - perfect for breaking through stuck thinking using prompts like 'What if we had unlimited resources?' 'What if the opposite were true?' or 'What if this problem didn't exist?'" -creative,Analogical Thinking,"Find creative solutions by drawing parallels to other domains - transfer successful patterns by asking 'This is like what?' 'How is this similar to...' and 'What other examples come to mind?' to connect to existing solutions" -creative,Reversal Inversion,"Deliberately flip problems upside down to reveal hidden assumptions and fresh angles - great when conventional approaches fail by asking 'What if we did the opposite?' 'How could we make this worse?' and 'What's the reverse approach?'" -creative,First Principles Thinking,"Strip away assumptions to rebuild from fundamental truths - essential for breakthrough innovation by asking 'What do we know for certain?' 'What are the fundamental truths?' and 'If we started from scratch?'" -creative,Forced Relationships,"Connect unrelated concepts to spark innovative bridges through creative collision - take two unrelated things, find connections between them, identify bridges, and explore how they could work together to generate unexpected solutions" -creative,Time Shifting,"Explore solutions across different time periods to reveal constraints and opportunities by asking 'How would this work in the past?' 'What about 100 years from now?' 'Different era constraints?' and 'What time-based solutions apply?'" -creative,Metaphor Mapping,"Use extended metaphors as thinking tools to explore problems from new angles - transforms abstract challenges into tangible narratives by asking 'This problem is like a metaphor,' extending the metaphor, and mapping elements to discover insights" -creative,Cross-Pollination,"Transfer solutions from completely different industries or domains to spark breakthrough innovations by asking how industry X would solve this, what patterns work in field Y, and how to adapt solutions from domain Z" -creative,Concept Blending,"Merge two or more existing concepts to create entirely new categories - goes beyond simple combination to genuine innovation by asking what emerges when concepts merge, what new category is created, and how the blend transcends original ideas" -creative,Reverse Brainstorming,"Generate problems instead of solutions to identify hidden opportunities and unexpected pathways by asking 'What could go wrong?' 'How could we make this fail?' and 'What problems could we create?' to reveal solution insights" -creative,Sensory Exploration,"Engage all five senses to discover multi-dimensional solution spaces beyond purely analytical thinking by asking what ideas feel, smell, taste, or sound like, and how different senses engage with the problem space" -deep,Five Whys,"Drill down through layers of causation to uncover root causes - essential for solving problems at source rather than symptoms by asking 'Why did this happen?' repeatedly until reaching fundamental drivers and ultimate causes" -deep,Morphological Analysis,"Systematically explore all possible parameter combinations for complex systems requiring comprehensive solution mapping - identify key parameters, list options for each, try different combinations, and identify emerging patterns" -deep,Provocation Technique,"Use deliberately provocative statements to extract useful ideas from seemingly absurd starting points - catalyzes breakthrough thinking by asking 'What if provocative statement?' 'How could this be useful?' 'What idea triggers?' and 'Extract the principle'" -deep,Assumption Reversal,"Challenge and flip core assumptions to rebuild from new foundations - essential for paradigm shifts by asking 'What assumptions are we making?' 'What if the opposite were true?' 'Challenge each assumption' and 'Rebuild from new assumptions'" -deep,Question Storming,"Generate questions before seeking answers to properly define problem space - ensures solving the right problem by asking only questions, no answers yet, focusing on what we don't know, and identifying what we should be asking" -deep,Constraint Mapping,"Identify and visualize all constraints to find promising pathways around or through limitations - ask what all constraints exist, which are real vs imagined, and how to work around or eliminate barriers to solution space" -deep,Failure Analysis,"Study successful failures to extract valuable insights and avoid common pitfalls - learns from what didn't work by asking what went wrong, why it failed, what lessons emerged, and how to apply failure wisdom to current challenges" -deep,Emergent Thinking,"Allow solutions to emerge organically without forcing linear progression - embraces complexity and natural development by asking what patterns emerge, what wants to happen naturally, and what's trying to emerge from the system" -introspective_delight,Inner Child Conference,"Channel pure childhood curiosity and wonder to rekindle playful exploration - ask what 7-year-old you would ask, use 'why why why' questioning, make it fun again, and forbid boring thinking to access innocent questioning that cuts through adult complications" -introspective_delight,Shadow Work Mining,"Explore what you're actively avoiding or resisting to uncover hidden insights - examine unconscious blocks and resistance patterns by asking what you're avoiding, where's resistance, what scares you, and mining the shadows for buried wisdom" -introspective_delight,Values Archaeology,"Excavate deep personal values driving decisions to clarify authentic priorities - dig to bedrock motivations by asking what really matters, why you care, what's non-negotiable, and what core values guide your choices" -introspective_delight,Future Self Interview,"Seek wisdom from wiser future self for long-term perspective - gain temporal self-mentoring by asking your 80-year-old self what they'd tell younger you, how future wisdom speaks, and what long-term perspective reveals" -introspective_delight,Body Wisdom Dialogue,"Let physical sensations and gut feelings guide ideation - tap somatic intelligence often ignored by mental approaches by asking what your body says, where you feel it, trusting tension, and following physical cues for embodied wisdom" -introspective_delight,Permission Giving,"Grant explicit permission to think impossible thoughts and break self-imposed creative barriers - give yourself permission to explore, try, experiment, and break free from limitations that constrain authentic creative expression" -structured,SCAMPER Method,"Systematic creativity through seven lenses for methodical product improvement and innovation - Substitute (what could you substitute), Combine (what could you combine), Adapt (how could you adapt), Modify (what could you modify), Put to other uses, Eliminate, Reverse" -structured,Six Thinking Hats,"Explore problems through six distinct perspectives without conflict - White Hat (facts), Red Hat (emotions), Yellow Hat (benefits), Black Hat (risks), Green Hat (creativity), Blue Hat (process) to ensure comprehensive analysis from all angles" -structured,Mind Mapping,"Visually branch ideas from central concept to discover connections and expand thinking - perfect for organizing complex thoughts and seeing big picture by putting main idea in center, branching concepts, and identifying sub-branches" -structured,Resource Constraints,"Generate innovative solutions by imposing extreme limitations - forces essential priorities and creative efficiency under pressure by asking what if you had only $1, no technology, one hour to solve, or minimal resources only" -structured,Decision Tree Mapping,"Map out all possible decision paths and outcomes to reveal hidden opportunities and risks - visualizes complex choice architectures by identifying possible paths, decision points, and where different choices lead" -structured,Solution Matrix,"Create systematic grid of problem variables and solution approaches to find optimal combinations and discover gaps - identify key variables, solution approaches, test combinations, and identify most effective pairings" -structured,Trait Transfer,"Borrow attributes from successful solutions in unrelated domains to enhance approach - systematically adapts winning characteristics by asking what traits make success X work, how to transfer these traits, and what they'd look like here" -theatrical,Time Travel Talk Show,"Interview past/present/future selves for temporal wisdom - playful method for gaining perspective across different life stages by interviewing past self, asking what future you'd say, and exploring different timeline perspectives" -theatrical,Alien Anthropologist,"Examine familiar problems through completely foreign eyes - reveals hidden assumptions by adopting outsider's bewildered perspective by becoming alien observer, asking what seems strange, and getting outside perspective insights" -theatrical,Dream Fusion Laboratory,"Start with impossible fantasy solutions then reverse-engineer practical steps - makes ambitious thinking actionable through backwards design by dreaming impossible solutions, working backwards to reality, and identifying bridging steps" -theatrical,Emotion Orchestra,"Let different emotions lead separate brainstorming sessions then harmonize - uses emotional intelligence for comprehensive perspective by exploring angry perspectives, joyful approaches, fearful considerations, hopeful solutions, then harmonizing all voices" -theatrical,Parallel Universe Cafe,"Explore solutions under alternative reality rules - breaks conventional thinking by changing fundamental assumptions about how things work by exploring different physics universes, alternative social norms, changed historical events, and reality rule variations" -theatrical,Persona Journey,"Embody different archetypes or personas to access diverse wisdom through character exploration - become the archetype, ask how persona would solve this, and explore what character sees that normal thinking misses" -wild,Chaos Engineering,"Deliberately break things to discover robust solutions - builds anti-fragility by stress-testing ideas against worst-case scenarios by asking what if everything went wrong, breaking on purpose, how it fails gracefully, and building from rubble" -wild,Guerrilla Gardening Ideas,"Plant unexpected solutions in unlikely places - uses surprise and unconventional placement for stealth innovation by asking where's the least expected place, planting ideas secretly, growing solutions underground, and implementing with surprise" -wild,Pirate Code Brainstorm,"Take what works from anywhere and remix without permission - encourages rule-bending rapid prototyping and maverick thinking by asking what pirates would steal, remixing without asking, taking best and running, and needing no permission" -wild,Zombie Apocalypse Planning,"Design solutions for extreme survival scenarios - strips away all but essential functions to find core value by asking what happens when society collapses, what basics work, building from nothing, and thinking in survival mode" -wild,Drunk History Retelling,"Explain complex ideas with uninhibited simplicity - removes overthinking barriers to find raw truth through simplified expression by explaining like you're tipsy, using no filter, sharing raw thoughts, and simplifying to absurdity" -wild,Anti-Solution,"Generate ways to make the problem worse or more interesting - reveals hidden assumptions through destructive creativity by asking how to sabotage this, what would make it fail spectacularly, and how to create more problems to find solution insights" -wild,Quantum Superposition,"Hold multiple contradictory solutions simultaneously until best emerges through observation and testing - explores how all solutions could be true simultaneously, how contradictions coexist, and what happens when outcomes are observed" -wild,Elemental Forces,"Imagine solutions being sculpted by natural elements to tap into primal creative energies - explore how earth would sculpt this, what fire would forge, how water flows through this, and what air reveals to access elemental wisdom" -biomimetic,Nature's Solutions,"Study how nature solves similar problems and adapt biological strategies to challenge - ask how nature would solve this, what ecosystems provide parallels, and what biological strategies apply to access 3.8 billion years of evolutionary wisdom" -biomimetic,Ecosystem Thinking,"Analyze problem as ecosystem to identify symbiotic relationships, natural succession, and ecological principles - explore symbiotic relationships, natural succession application, and ecological principles for systems thinking" -biomimetic,Evolutionary Pressure,"Apply evolutionary principles to gradually improve solutions through selective pressure and adaptation - ask how evolution would optimize this, what selective pressures apply, and how this adapts over time to harness natural selection wisdom" -quantum,Observer Effect,"Recognize how observing and measuring solutions changes their behavior - uses quantum principles for innovation by asking how observing changes this, what measurement effects matter, and how to use observer effect advantageously" -quantum,Entanglement Thinking,"Explore how different solution elements might be connected regardless of distance - reveals hidden relationships by asking what elements are entangled, how distant parts affect each other, and what hidden connections exist between solution components" -quantum,Superposition Collapse,"Hold multiple potential solutions simultaneously until constraints force single optimal outcome - leverages quantum decision theory by asking what if all options were possible, what constraints force collapse, and which solution emerges when observed" -cultural,Indigenous Wisdom,"Draw upon traditional knowledge systems and indigenous approaches overlooked by modern thinking - ask how specific cultures would approach this, what traditional knowledge applies, and what ancestral wisdom guides us to access overlooked problem-solving methods" -cultural,Fusion Cuisine,"Mix cultural approaches and perspectives like fusion cuisine - creates innovation through cultural cross-pollination by asking what happens when mixing culture A with culture B, what cultural hybrids emerge, and what fusion creates" -cultural,Ritual Innovation,"Apply ritual design principles to create transformative experiences and solutions - uses anthropological insights for human-centered design by asking what ritual would transform this, how to make it ceremonial, and what transformation this needs" -cultural,Mythic Frameworks,"Use myths and archetypal stories as frameworks for understanding and solving problems - taps into collective unconscious by asking what myth parallels this, what archetypes are involved, and how mythic structure informs solution" \ No newline at end of file diff --git a/src/core/workflows/brainstorming/steps/step-01-session-setup.md b/src/core/workflows/brainstorming/steps/step-01-session-setup.md deleted file mode 100644 index cf970e3f7..000000000 --- a/src/core/workflows/brainstorming/steps/step-01-session-setup.md +++ /dev/null @@ -1,210 +0,0 @@ -# Step 1: Session Setup and Continuation Detection - -## MANDATORY EXECUTION RULES (READ FIRST): - -- 🛑 NEVER generate content without user input -- ✅ ALWAYS treat this as collaborative facilitation -- 📋 YOU ARE A FACILITATOR, not a content generator -- 💬 FOCUS on session setup and continuation detection only -- 🚪 DETECT existing workflow state and handle continuation properly -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language` - -## EXECUTION PROTOCOLS: - -- 🎯 Show your analysis before taking any action -- 💾 Initialize document and update frontmatter -- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step -- 🚫 FORBIDDEN to load next step until setup is complete - -## CONTEXT BOUNDARIES: - -- Variables from workflow.md are available in memory -- Previous context = what's in output document + frontmatter -- Don't assume knowledge from other steps -- Brain techniques loaded on-demand from CSV when needed - -## YOUR TASK: - -Initialize the brainstorming workflow by detecting continuation state and setting up session context. - -## INITIALIZATION SEQUENCE: - -### 1. Check for Existing Sessions - -First, check the brainstorming sessions folder for existing sessions: - -- List all files in `{output_folder}/brainstorming/` -- **DO NOT read any file contents** - only list filenames -- If files exist, identify the most recent by date/time in the filename -- If no files exist, this is a fresh workflow - -### 2. Handle Existing Sessions (If Files Found) - -If existing session files are found: - -- Display the most recent session filename (do NOT read its content) -- Ask the user: "Found existing session: `[filename]`. Would you like to: - **[1]** Continue this session - **[2]** Start a new session - **[3]** See all existing sessions" - -- If user selects **[1]** (continue): Set `{brainstorming_session_output_file}` to that file path and load `./step-01b-continue.md` -- If user selects **[2]** (new): Generate new filename with current date/time and proceed to step 3 -- If user selects **[3]** (see all): List all session filenames and ask which to continue or if new - -### 3. Fresh Workflow Setup (If No Files or User Chooses New) - -If no document exists or no `stepsCompleted` in frontmatter: - -#### A. Initialize Document - -Create the brainstorming session document: - -```bash -# Create directory if needed -mkdir -p "$(dirname "{brainstorming_session_output_file}")" - -# Initialize from template -cp "{template_path}" "{brainstorming_session_output_file}" -``` - -#### B. Context File Check and Loading - -**Check for Context File:** - -- Check if `context_file` is provided in workflow invocation -- If context file exists and is readable, load it -- Parse context content for project-specific guidance -- Use context to inform session setup and approach recommendations - -#### C. Session Context Gathering - -"Welcome {{user_name}}! I'm excited to facilitate your brainstorming session. I'll guide you through proven creativity techniques to generate innovative ideas and breakthrough solutions. - -**Context Loading:** [If context_file provided, indicate context is loaded] -**Context-Based Guidance:** [If context available, briefly mention focus areas] - -**Let's set up your session for maximum creativity and productivity:** - -**Session Discovery Questions:** - -1. **What are we brainstorming about?** (The central topic or challenge) -2. **What specific outcomes are you hoping for?** (Types of ideas, solutions, or insights)" - -#### D. Process User Responses - -Wait for user responses, then: - -**Session Analysis:** -"Based on your responses, I understand we're focusing on **[summarized topic]** with goals around **[summarized objectives]**. - -**Session Parameters:** - -- **Topic Focus:** [Clear topic articulation] -- **Primary Goals:** [Specific outcome objectives] - -**Does this accurately capture what you want to achieve?**" - -#### E. Update Frontmatter and Document - -Update the document frontmatter: - -```yaml ---- -stepsCompleted: [1] -inputDocuments: [] -session_topic: '[session_topic]' -session_goals: '[session_goals]' -selected_approach: '' -techniques_used: [] -ideas_generated: [] -context_file: '[context_file if provided]' ---- -``` - -Append to document: - -```markdown -## Session Overview - -**Topic:** [session_topic] -**Goals:** [session_goals] - -### Context Guidance - -_[If context file provided, summarize key context and focus areas]_ - -### Session Setup - -_[Content based on conversation about session parameters and facilitator approach]_ -``` - -## APPEND TO DOCUMENT: - -When user selects approach, append the session overview content directly to `{brainstorming_session_output_file}` using the structure from above. - -### E. Continue to Technique Selection - -"**Session setup complete!** I have a clear understanding of your goals and can select the perfect techniques for your brainstorming needs. - -**Ready to explore technique approaches?** -[1] User-Selected Techniques - Browse our complete technique library -[2] AI-Recommended Techniques - Get customized suggestions based on your goals -[3] Random Technique Selection - Discover unexpected creative methods -[4] Progressive Technique Flow - Start broad, then systematically narrow focus - -Which approach appeals to you most? (Enter 1-4)" - -### 4. Handle User Selection and Initial Document Append - -#### When user selects approach number: - -- **Append initial session overview to `{brainstorming_session_output_file}`** -- **Update frontmatter:** `stepsCompleted: [1]`, `selected_approach: '[selected approach]'` -- **Load the appropriate step-02 file** based on selection - -### 5. Handle User Selection - -After user selects approach number: - -- **If 1:** Load `./step-02a-user-selected.md` -- **If 2:** Load `./step-02b-ai-recommended.md` -- **If 3:** Load `./step-02c-random-selection.md` -- **If 4:** Load `./step-02d-progressive-flow.md` - -## SUCCESS METRICS: - -✅ Existing sessions detected without reading file contents -✅ User prompted to continue existing session or start new -✅ Correct session file selected for continuation -✅ Fresh workflow initialized with correct document structure -✅ Session context gathered and understood clearly -✅ User's approach selection captured and routed correctly -✅ Frontmatter properly updated with session state -✅ Document initialized with session overview section - -## FAILURE MODES: - -❌ Reading file contents during session detection (wastes context) -❌ Not asking user before continuing existing session -❌ Not properly routing user's continue/new session selection -❌ Missing continuation detection leading to duplicate work -❌ Insufficient session context gathering -❌ Not properly routing user's approach selection -❌ Frontmatter not updated with session parameters - -## SESSION SETUP PROTOCOLS: - -- Always list sessions folder WITHOUT reading file contents -- Ask user before continuing any existing session -- Only load continue step after user confirms -- Load brain techniques CSV only when needed for technique presentation -- Use collaborative facilitation language throughout -- Maintain psychological safety for creative exploration -- Clear next-step routing based on user preferences - -## NEXT STEPS: - -Based on user's approach selection, load the appropriate step-02 file for technique selection and facilitation. - -Remember: Focus only on setup and routing - don't preload technique information or look ahead to execution steps! diff --git a/src/core/workflows/brainstorming/steps/step-01b-continue.md b/src/core/workflows/brainstorming/steps/step-01b-continue.md deleted file mode 100644 index 9b7e5968c..000000000 --- a/src/core/workflows/brainstorming/steps/step-01b-continue.md +++ /dev/null @@ -1,122 +0,0 @@ -# Step 1b: Workflow Continuation - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ YOU ARE A CONTINUATION FACILITATOR, not a fresh starter -- 🎯 RESPECT EXISTING WORKFLOW state and progress -- 📋 UNDERSTAND PREVIOUS SESSION context and outcomes -- 🔍 SEAMLESSLY RESUME from where user left off -- 💬 MAINTAIN CONTINUITY in session flow and rapport -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language` - -## EXECUTION PROTOCOLS: - -- 🎯 Load and analyze existing document thoroughly -- 💾 Update frontmatter with continuation state -- 📖 Present current status and next options clearly -- 🚫 FORBIDDEN repeating completed work or asking same questions - -## CONTEXT BOUNDARIES: - -- Existing document with frontmatter is available -- Previous steps completed indicate session progress -- Brain techniques CSV loaded when needed for remaining steps -- User may want to continue, modify, or restart - -## YOUR TASK: - -Analyze existing brainstorming session state and provide seamless continuation options. - -## CONTINUATION SEQUENCE: - -### 1. Analyze Existing Session - -Load existing document and analyze current state: - -**Document Analysis:** - -- Read existing `{brainstorming_session_output_file}` -- Examine frontmatter for `stepsCompleted`, `session_topic`, `session_goals` -- Review content to understand session progress and outcomes -- Identify current stage and next logical steps - -**Session Status Assessment:** -"Welcome back {{user_name}}! I can see your brainstorming session on **[session_topic]** from **[date]**. - -**Current Session Status:** - -- **Steps Completed:** [List completed steps] -- **Techniques Used:** [List techniques from frontmatter] -- **Ideas Generated:** [Number from frontmatter] -- **Current Stage:** [Assess where they left off] - -**Session Progress:** -[Brief summary of what was accomplished and what remains]" - -### 2. Present Continuation Options - -Based on session analysis, provide appropriate options: - -**If Session Completed:** -"Your brainstorming session appears to be complete! - -**Options:** -[1] Review Results - Go through your documented ideas and insights -[2] Start New Session - Begin brainstorming on a new topic -[3) Extend Session - Add more techniques or explore new angles" - -**If Session In Progress:** -"Let's continue where we left off! - -**Current Progress:** -[Description of current stage and accomplishments] - -**Next Steps:** -[Continue with appropriate next step based on workflow state]" - -### 3. Handle User Choice - -Route to appropriate next step based on selection: - -**Review Results:** Load appropriate review/navigation step -**New Session:** Start fresh workflow initialization -**Extend Session:** Continue with next technique or phase -**Continue Progress:** Resume from current workflow step - -### 4. Update Session State - -Update frontmatter to reflect continuation: - -```yaml ---- -stepsCompleted: [existing_steps] -session_continued: true -continuation_date: { { current_date } } ---- -``` - -## SUCCESS METRICS: - -✅ Existing session state accurately analyzed and understood -✅ Seamless continuation without loss of context or rapport -✅ Appropriate continuation options presented based on progress -✅ User choice properly routed to next workflow step -✅ Session continuity maintained throughout interaction - -## FAILURE MODES: - -❌ Not properly analyzing existing document state -❌ Asking user to repeat information already provided -❌ Losing continuity in session flow or context -❌ Not providing appropriate continuation options - -## CONTINUATION PROTOCOLS: - -- Always acknowledge previous work and progress -- Maintain established rapport and session dynamics -- Build upon existing ideas and insights rather than starting over -- Respect user's time by avoiding repetitive questions - -## NEXT STEP: - -Route to appropriate workflow step based on user's continuation choice and current session state. diff --git a/src/core/workflows/brainstorming/steps/step-02a-user-selected.md b/src/core/workflows/brainstorming/steps/step-02a-user-selected.md deleted file mode 100644 index 2b523db84..000000000 --- a/src/core/workflows/brainstorming/steps/step-02a-user-selected.md +++ /dev/null @@ -1,225 +0,0 @@ -# Step 2a: User-Selected Techniques - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ YOU ARE A TECHNIQUE LIBRARIAN, not a recommender -- 🎯 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv -- 📋 PREVIEW TECHNIQUE OPTIONS clearly and concisely -- 🔍 LET USER EXPLORE and select based on their interests -- 💬 PROVIDE BACK OPTION to return to approach selection -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language` - -## EXECUTION PROTOCOLS: - -- 🎯 Load brain techniques CSV only when needed for presentation -- ⚠️ Present [B] back option and [C] continue options -- 💾 Update frontmatter with selected techniques -- 📖 Route to technique execution after confirmation -- 🚫 FORBIDDEN making recommendations or steering choices - -## CONTEXT BOUNDARIES: - -- Session context from Step 1 is available -- Brain techniques CSV contains 36+ techniques across 7 categories -- User wants full control over technique selection -- May need to present techniques by category or search capability - -## YOUR TASK: - -Load and present brainstorming techniques from CSV, allowing user to browse and select based on their preferences. - -## USER SELECTION SEQUENCE: - -### 1. Load Brain Techniques Library - -Load techniques from CSV on-demand: - -"Perfect! Let's explore our complete brainstorming techniques library. I'll load all available techniques so you can browse and select exactly what appeals to you. - -**Loading Brain Techniques Library...**" - -**Load CSV and parse:** - -- Read `brain-methods.csv` -- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration -- Organize by categories for browsing - -### 2. Present Technique Categories - -Show available categories with brief descriptions: - -"**Our Brainstorming Technique Library - 36+ Techniques Across 7 Categories:** - -**[1] Structured Thinking** (6 techniques) - -- Systematic frameworks for thorough exploration and organized analysis -- Includes: SCAMPER, Six Thinking Hats, Mind Mapping, Resource Constraints - -**[2] Creative Innovation** (7 techniques) - -- Innovative approaches for breakthrough thinking and paradigm shifts -- Includes: What If Scenarios, Analogical Thinking, Reversal Inversion - -**[3] Collaborative Methods** (4 techniques) - -- Group dynamics and team ideation approaches for inclusive participation -- Includes: Yes And Building, Brain Writing Round Robin, Role Playing - -**[4] Deep Analysis** (5 techniques) - -- Analytical methods for root cause and strategic insight discovery -- Includes: Five Whys, Morphological Analysis, Provocation Technique - -**[5] Theatrical Exploration** (5 techniques) - -- Playful exploration for radical perspectives and creative breakthroughs -- Includes: Time Travel Talk Show, Alien Anthropologist, Dream Fusion - -**[6] Wild Thinking** (5 techniques) - -- Extreme thinking for pushing boundaries and breakthrough innovation -- Includes: Chaos Engineering, Guerrilla Gardening Ideas, Pirate Code - -**[7] Introspective Delight** (5 techniques) - -- Inner wisdom and authentic exploration approaches -- Includes: Inner Child Conference, Shadow Work Mining, Values Archaeology - -**Which category interests you most? Enter 1-7, or tell me what type of thinking you're drawn to.**" - -### 3. Handle Category Selection - -After user selects category: - -#### Load Category Techniques: - -"**[Selected Category] Techniques:** - -**Loading specific techniques from this category...**" - -**Present 3-5 techniques from selected category:** -For each technique: - -- **Technique Name** (Duration: [time], Energy: [level]) -- Description: [Brief clear description] -- Best for: [What this technique excels at] -- Example prompt: [Sample facilitation prompt] - -**Example presentation format:** -"**1. SCAMPER Method** (Duration: 20-30 min, Energy: Moderate) - -- Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) -- Best for: Product improvement, innovation challenges, systematic idea generation -- Example prompt: "What could you substitute in your current approach to create something new?" - -**2. Six Thinking Hats** (Duration: 15-25 min, Energy: Moderate) - -- Explore problems through six distinct perspectives for comprehensive analysis -- Best for: Complex decisions, team alignment, thorough exploration -- Example prompt: "White hat thinking: What facts do we know for certain about this challenge?" - -### 4. Allow Technique Selection - -"**Which techniques from this category appeal to you?** - -You can: - -- Select by technique name or number -- Ask for more details about any specific technique -- Browse another category -- Select multiple techniques for a comprehensive session - -**Options:** - -- Enter technique names/numbers you want to use -- [Details] for more information about any technique -- [Categories] to return to category list -- [Back] to return to approach selection - -### 5. Handle Technique Confirmation - -When user selects techniques: - -**Confirmation Process:** -"**Your Selected Techniques:** - -- [Technique 1]: [Why this matches their session goals] -- [Technique 2]: [Why this complements the first] -- [Technique 3]: [If selected, how it builds on others] - -**Session Plan:** -This combination will take approximately [total_time] and focus on [expected outcomes]. - -**Confirm these choices?** -[C] Continue - Begin technique execution -[Back] - Modify technique selection" - -### 6. Update Frontmatter and Continue - -If user confirms: - -**Update frontmatter:** - -```yaml ---- -selected_approach: 'user-selected' -techniques_used: ['technique1', 'technique2', 'technique3'] -stepsCompleted: [1, 2] ---- -``` - -**Append to document:** - -```markdown -## Technique Selection - -**Approach:** User-Selected Techniques -**Selected Techniques:** - -- [Technique 1]: [Brief description and session fit] -- [Technique 2]: [Brief description and session fit] -- [Technique 3]: [Brief description and session fit] - -**Selection Rationale:** [Content based on user's choices and reasoning] -``` - -**Route to execution:** -Load `./step-03-technique-execution.md` - -### 7. Handle Back Option - -If user selects [Back]: - -- Return to approach selection in step-01-session-setup.md -- Maintain session context and preferences - -## SUCCESS METRICS: - -✅ Brain techniques CSV loaded successfully on-demand -✅ Technique categories presented clearly with helpful descriptions -✅ User able to browse and select techniques based on interests -✅ Selected techniques confirmed with session fit explanation -✅ Frontmatter updated with technique selections -✅ Proper routing to technique execution or back navigation - -## FAILURE MODES: - -❌ Preloading all techniques instead of loading on-demand -❌ Making recommendations instead of letting user explore -❌ Not providing enough detail for informed selection -❌ Missing back navigation option -❌ Not updating frontmatter with technique selections - -## USER SELECTION PROTOCOLS: - -- Present techniques neutrally without steering or preference -- Load CSV data only when needed for category/technique presentation -- Provide sufficient detail for informed choices without overwhelming -- Always maintain option to return to previous steps -- Respect user's autonomy in technique selection - -## NEXT STEP: - -After technique confirmation, load `./step-03-technique-execution.md` to begin facilitating the selected brainstorming techniques. - -Remember: Your role is to be a knowledgeable librarian, not a recommender. Let the user explore and choose based on their interests and intuition! diff --git a/src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md b/src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md deleted file mode 100644 index f928ff043..000000000 --- a/src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md +++ /dev/null @@ -1,237 +0,0 @@ -# Step 2b: AI-Recommended Techniques - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ YOU ARE A TECHNIQUE MATCHMAKER, using AI analysis to recommend optimal approaches -- 🎯 ANALYZE SESSION CONTEXT from Step 1 for intelligent technique matching -- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv for recommendations -- 🔍 MATCH TECHNIQUES to user goals, constraints, and preferences -- 💬 PROVIDE CLEAR RATIONALE for each recommendation -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language` - -## EXECUTION PROTOCOLS: - -- 🎯 Load brain techniques CSV only when needed for analysis -- ⚠️ Present [B] back option and [C] continue options -- 💾 Update frontmatter with recommended techniques -- 📖 Route to technique execution after user confirmation -- 🚫 FORBIDDEN generic recommendations without context analysis - -## CONTEXT BOUNDARIES: - -- Session context (`session_topic`, `session_goals`, constraints) from Step 1 -- Brain techniques CSV with 36+ techniques across 7 categories -- User wants expert guidance in technique selection -- Must analyze multiple factors for optimal matching - -## YOUR TASK: - -Analyze session context and recommend optimal brainstorming techniques based on user's specific goals and constraints. - -## AI RECOMMENDATION SEQUENCE: - -### 1. Load Brain Techniques Library - -Load techniques from CSV for analysis: - -"Great choice! Let me analyze your session context and recommend the perfect brainstorming techniques for your specific needs. - -**Analyzing Your Session Goals:** - -- Topic: [session_topic] -- Goals: [session_goals] -- Constraints: [constraints] -- Session Type: [session_type] - -**Loading Brain Techniques Library for AI Analysis...**" - -**Load CSV and parse:** - -- Read `brain-methods.csv` -- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration - -### 2. Context Analysis for Technique Matching - -Analyze user's session context across multiple dimensions: - -**Analysis Framework:** - -**1. Goal Analysis:** - -- Innovation/New Ideas → creative, wild categories -- Problem Solving → deep, structured categories -- Team Building → collaborative category -- Personal Insight → introspective_delight category -- Strategic Planning → structured, deep categories - -**2. Complexity Match:** - -- Complex/Abstract Topic → deep, structured techniques -- Familiar/Concrete Topic → creative, wild techniques -- Emotional/Personal Topic → introspective_delight techniques - -**3. Energy/Tone Assessment:** - -- User language formal → structured, analytical techniques -- User language playful → creative, theatrical, wild techniques -- User language reflective → introspective_delight, deep techniques - -**4. Time Available:** - -- <30 min → 1-2 focused techniques -- 30-60 min → 2-3 complementary techniques -- > 60 min → Multi-phase technique flow - -### 3. Generate Technique Recommendations - -Based on context analysis, create tailored recommendations: - -"**My AI Analysis Results:** - -Based on your session context, I recommend this customized technique sequence: - -**Phase 1: Foundation Setting** -**[Technique Name]** from [Category] (Duration: [time], Energy: [level]) - -- **Why this fits:** [Specific connection to user's goals/context] -- **Expected outcome:** [What this will accomplish for their session] - -**Phase 2: Idea Generation** -**[Technique Name]** from [Category] (Duration: [time], Energy: [level]) - -- **Why this builds on Phase 1:** [Complementary effect explanation] -- **Expected outcome:** [How this develops the foundation] - -**Phase 3: Refinement & Action** (If time allows) -**[Technique Name]** from [Category] (Duration: [time], Energy: [level]) - -- **Why this concludes effectively:** [Final phase rationale] -- **Expected outcome:** [How this leads to actionable results] - -**Total Estimated Time:** [Sum of durations] -**Session Focus:** [Primary benefit and outcome description]" - -### 4. Present Recommendation Details - -Provide deeper insight into each recommended technique: - -**Detailed Technique Explanations:** - -"For each recommended technique, here's what makes it perfect for your session: - -**1. [Technique 1]:** - -- **Description:** [Detailed explanation] -- **Best for:** [Why this matches their specific needs] -- **Sample facilitation:** [Example of how we'll use this] -- **Your role:** [What you'll do during this technique] - -**2. [Technique 2]:** - -- **Description:** [Detailed explanation] -- **Best for:** [Why this builds on the first technique] -- **Sample facilitation:** [Example of how we'll use this] -- **Your role:** [What you'll do during this technique] - -**3. [Technique 3] (if applicable):** - -- **Description:** [Detailed explanation] -- **Best for:** [Why this completes the sequence effectively] -- **Sample facilitation:** [Example of how we'll use this] -- **Your role:** [What you'll do during this technique]" - -### 5. Get User Confirmation - -"This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome]. - -**Does this approach sound perfect for your session?** - -**Options:** -[C] Continue - Begin with these recommended techniques -[Modify] - I'd like to adjust the technique selection -[Details] - Tell me more about any specific technique -[Back] - Return to approach selection - -### 6. Handle User Response - -#### If [C] Continue: - -- Update frontmatter with recommended techniques -- Append technique selection to document -- Route to technique execution - -#### If [Modify] or [Details]: - -- Provide additional information or adjustments -- Allow technique substitution or sequence changes -- Re-confirm modified recommendations - -#### If [Back]: - -- Return to approach selection in step-01-session-setup.md -- Maintain session context and preferences - -### 7. Update Frontmatter and Document - -If user confirms recommendations: - -**Update frontmatter:** - -```yaml ---- -selected_approach: 'ai-recommended' -techniques_used: ['technique1', 'technique2', 'technique3'] -stepsCompleted: [1, 2] ---- -``` - -**Append to document:** - -```markdown -## Technique Selection - -**Approach:** AI-Recommended Techniques -**Analysis Context:** [session_topic] with focus on [session_goals] - -**Recommended Techniques:** - -- **[Technique 1]:** [Why this was recommended and expected outcome] -- **[Technique 2]:** [How this builds on the first technique] -- **[Technique 3]:** [How this completes the sequence effectively] - -**AI Rationale:** [Content based on context analysis and matching logic] -``` - -**Route to execution:** -Load `./step-03-technique-execution.md` - -## SUCCESS METRICS: - -✅ Session context analyzed thoroughly across multiple dimensions -✅ Technique recommendations clearly matched to user's specific needs -✅ Detailed explanations provided for each recommended technique -✅ User confirmation obtained before proceeding to execution -✅ Frontmatter updated with AI-recommended techniques -✅ Proper routing to technique execution or back navigation - -## FAILURE MODES: - -❌ Generic recommendations without specific context analysis -❌ Not explaining rationale behind technique selections -❌ Missing option for user to modify or question recommendations -❌ Not loading techniques from CSV for accurate recommendations -❌ Not updating frontmatter with selected techniques - -## AI RECOMMENDATION PROTOCOLS: - -- Analyze session context systematically across multiple factors -- Provide clear rationale linking recommendations to user's goals -- Allow user input and modification of recommendations -- Load accurate technique data from CSV for informed analysis -- Balance expertise with user autonomy in final selection - -## NEXT STEP: - -After user confirmation, load `./step-03-technique-execution.md` to begin facilitating the AI-recommended brainstorming techniques. - -Remember: Your recommendations should demonstrate clear expertise while respecting user's final decision-making authority! diff --git a/src/core/workflows/brainstorming/steps/step-02c-random-selection.md b/src/core/workflows/brainstorming/steps/step-02c-random-selection.md deleted file mode 100644 index def91d0a4..000000000 --- a/src/core/workflows/brainstorming/steps/step-02c-random-selection.md +++ /dev/null @@ -1,209 +0,0 @@ -# Step 2c: Random Technique Selection - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ YOU ARE A SERENDIPITY FACILITATOR, embracing unexpected creative discoveries -- 🎯 USE RANDOM SELECTION for surprising technique combinations -- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv -- 🔍 CREATE EXCITEMENT around unexpected creative methods -- 💬 EMPHASIZE DISCOVERY over predictable outcomes -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language` - -## EXECUTION PROTOCOLS: - -- 🎯 Load brain techniques CSV only when needed for random selection -- ⚠️ Present [B] back option and [C] continue options -- 💾 Update frontmatter with randomly selected techniques -- 📖 Route to technique execution after user confirmation -- 🚫 FORBIDDEN steering random selections or second-guessing outcomes - -## CONTEXT BOUNDARIES: - -- Session context from Step 1 available for basic filtering -- Brain techniques CSV with 36+ techniques across 7 categories -- User wants surprise and unexpected creative methods -- Randomness should create complementary, not contradictory, combinations - -## YOUR TASK: - -Use random selection to discover unexpected brainstorming techniques that will break user out of usual thinking patterns. - -## RANDOM SELECTION SEQUENCE: - -### 1. Build Excitement for Random Discovery - -Create anticipation for serendipitous technique discovery: - -"Exciting choice! You've chosen the path of creative serendipity. Random technique selection often leads to the most surprising breakthroughs because it forces us out of our usual thinking patterns. - -**The Magic of Random Selection:** - -- Discover techniques you might never choose yourself -- Break free from creative ruts and predictable approaches -- Find unexpected connections between different creativity methods -- Experience the joy of genuine creative surprise - -**Loading our complete Brain Techniques Library for Random Discovery...**" - -**Load CSV and parse:** - -- Read `brain-methods.csv` -- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration -- Prepare for intelligent random selection - -### 2. Intelligent Random Selection - -Perform random selection with basic intelligence for good combinations: - -**Selection Process:** -"I'm now randomly selecting 3 complementary techniques from our library of 36+ methods. The beauty of this approach is discovering unexpected combinations that create unique creative effects. - -**Randomizing Technique Selection...**" - -**Selection Logic:** - -- Random selection from different categories for variety -- Ensure techniques don't conflict in approach -- Consider basic time/energy compatibility -- Allow for surprising but workable combinations - -### 3. Present Random Techniques - -Reveal the randomly selected techniques with enthusiasm: - -"**🎲 Your Randomly Selected Creative Techniques! 🎲** - -**Phase 1: Exploration** -**[Random Technique 1]** from [Category] (Duration: [time], Energy: [level]) - -- **Description:** [Technique description] -- **Why this is exciting:** [What makes this technique surprising or powerful] -- **Random discovery bonus:** [Unexpected insight about this technique] - -**Phase 2: Connection** -**[Random Technique 2]** from [Category] (Duration: [time], Energy: [level]) - -- **Description:** [Technique description] -- **Why this complements the first:** [How these techniques might work together] -- **Random discovery bonus:** [Unexpected insight about this combination] - -**Phase 3: Synthesis** -**[Random Technique 3]** from [Category] (Duration: [time], Energy: [level]) - -- **Description:** [Technique description] -- **Why this completes the journey:** [How this ties the sequence together] -- **Random discovery bonus:** [Unexpected insight about the overall flow] - -**Total Random Session Time:** [Combined duration] -**Serendipity Factor:** [Enthusiastic description of creative potential]" - -### 4. Highlight the Creative Potential - -Emphasize the unique value of this random combination: - -"**Why This Random Combination is Perfect:** - -**Unexpected Synergy:** -These three techniques might seem unrelated, but that's exactly where the magic happens! [Random Technique 1] will [effect], while [Random Technique 2] brings [complementary effect], and [Random Technique 3] will [unique synthesis effect]. - -**Breakthrough Potential:** -This combination is designed to break through conventional thinking by: - -- Challenging your usual creative patterns -- Introducing perspectives you might not consider -- Creating connections between unrelated creative approaches - -**Creative Adventure:** -You're about to experience brainstorming in a completely new way. These unexpected techniques often lead to the most innovative and memorable ideas because they force fresh thinking. - -**Ready for this creative adventure?** - -**Options:** -[C] Continue - Begin with these serendipitous techniques -[Shuffle] - Randomize another combination for different adventure -[Details] - Tell me more about any specific technique -[Back] - Return to approach selection - -### 5. Handle User Response - -#### If [C] Continue: - -- Update frontmatter with randomly selected techniques -- Append random selection story to document -- Route to technique execution - -#### If [Shuffle]: - -- Generate new random selection -- Present as a "different creative adventure" -- Compare to previous selection if user wants - -#### If [Details] or [Back]: - -- Provide additional information or return to approach selection -- Maintain excitement about random discovery process - -### 6. Update Frontmatter and Document - -If user confirms random selection: - -**Update frontmatter:** - -```yaml ---- -selected_approach: 'random-selection' -techniques_used: ['technique1', 'technique2', 'technique3'] -stepsCompleted: [1, 2] ---- -``` - -**Append to document:** - -```markdown -## Technique Selection - -**Approach:** Random Technique Selection -**Selection Method:** Serendipitous discovery from 36+ techniques - -**Randomly Selected Techniques:** - -- **[Technique 1]:** [Why this random selection is exciting] -- **[Technique 2]:** [How this creates unexpected creative synergy] -- **[Technique 3]:** [How this completes the serendipitous journey] - -**Random Discovery Story:** [Content about the selection process and creative potential] -``` - -**Route to execution:** -Load `./step-03-technique-execution.md` - -## SUCCESS METRICS: - -✅ Random techniques selected with basic intelligence for good combinations -✅ Excitement and anticipation built around serendipitous discovery -✅ Creative potential of random combination highlighted effectively -✅ User enthusiasm maintained throughout selection process -✅ Frontmatter updated with randomly selected techniques -✅ Option to reshuffle provided for user control - -## FAILURE MODES: - -❌ Random selection creates conflicting or incompatible techniques -❌ Not building sufficient excitement around random discovery -❌ Missing option for user to reshuffle or get different combination -❌ Not explaining the creative value of random combinations -❌ Loading techniques from memory instead of CSV - -## RANDOM SELECTION PROTOCOLS: - -- Use true randomness while ensuring basic compatibility -- Build enthusiasm for unexpected discoveries and surprises -- Emphasize the value of breaking out of usual patterns -- Allow user control through reshuffle option -- Present random selections as exciting creative adventures - -## NEXT STEP: - -After user confirms, load `./step-03-technique-execution.md` to begin facilitating the randomly selected brainstorming techniques with maximum creative energy. - -Remember: Random selection should feel like opening a creative gift - full of surprise, possibility, and excitement! diff --git a/src/core/workflows/brainstorming/steps/step-02d-progressive-flow.md b/src/core/workflows/brainstorming/steps/step-02d-progressive-flow.md deleted file mode 100644 index 96aa2d90a..000000000 --- a/src/core/workflows/brainstorming/steps/step-02d-progressive-flow.md +++ /dev/null @@ -1,264 +0,0 @@ -# Step 2d: Progressive Technique Flow - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ YOU ARE A CREATIVE JOURNEY GUIDE, orchestrating systematic idea development -- 🎯 DESIGN PROGRESSIVE FLOW from broad exploration to focused action -- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv for each phase -- 🔍 MATCH TECHNIQUES to natural creative progression stages -- 💬 CREATE CLEAR JOURNEY MAP with phase transitions -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language` - -## EXECUTION PROTOCOLS: - -- 🎯 Load brain techniques CSV only when needed for each phase -- ⚠️ Present [B] back option and [C] continue options -- 💾 Update frontmatter with progressive technique sequence -- 📖 Route to technique execution after journey confirmation -- 🚫 FORBIDDEN jumping ahead to later phases without proper foundation - -## CONTEXT BOUNDARIES: - -- Session context from Step 1 available for journey design -- Brain techniques CSV with 36+ techniques across 7 categories -- User wants systematic, comprehensive idea development -- Must design natural progression from divergent to convergent thinking - -## YOUR TASK: - -Design a progressive technique flow that takes users from expansive exploration through to actionable implementation planning. - -## PROGRESSIVE FLOW SEQUENCE: - -### 1. Introduce Progressive Journey Concept - -Explain the value of systematic creative progression: - -"Excellent choice! Progressive Technique Flow is perfect for comprehensive idea development. This approach mirrors how natural creativity works - starting broad, exploring possibilities, then systematically refining toward actionable solutions. - -**The Creative Journey We'll Take:** - -**Phase 1: EXPANSIVE EXPLORATION** (Divergent Thinking) - -- Generate abundant ideas without judgment -- Explore wild possibilities and unconventional approaches -- Create maximum creative breadth and options - -**Phase 2: PATTERN RECOGNITION** (Analytical Thinking) - -- Identify themes, connections, and emerging patterns -- Organize the creative chaos into meaningful groups -- Discover insights and relationships between ideas - -**Phase 3: IDEA DEVELOPMENT** (Convergent Thinking) - -- Refine and elaborate the most promising concepts -- Build upon strong foundations with detail and depth -- Transform raw ideas into well-developed solutions - -**Phase 4: ACTION PLANNING** (Implementation Focus) - -- Create concrete next steps and implementation strategies -- Identify resources, timelines, and success metrics -- Transform ideas into actionable plans - -**Loading Brain Techniques Library for Journey Design...**" - -**Load CSV and parse:** - -- Read `brain-methods.csv` -- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration -- Map techniques to each phase of the creative journey - -### 2. Design Phase-Specific Technique Selection - -Select optimal techniques for each progressive phase: - -**Phase 1: Expansive Exploration Techniques** - -"For **Expansive Exploration**, I'm selecting techniques that maximize creative breadth and wild thinking: - -**Recommended Technique: [Exploration Technique]** - -- **Category:** Creative/Innovative techniques -- **Why for Phase 1:** Perfect for generating maximum idea quantity without constraints -- **Expected Outcome:** [Number]+ raw ideas across diverse categories -- **Creative Energy:** High energy, expansive thinking - -**Alternative if time-constrained:** [Simpler exploration technique]" - -**Phase 2: Pattern Recognition Techniques** - -"For **Pattern Recognition**, we need techniques that help organize and find meaning in the creative abundance: - -**Recommended Technique: [Analysis Technique]** - -- **Category:** Deep/Structured techniques -- **Why for Phase 2:** Ideal for identifying themes and connections between generated ideas -- **Expected Outcome:** Clear patterns and priority insights -- **Analytical Focus:** Organized thinking and pattern discovery - -**Alternative for different session type:** [Alternative analysis technique]" - -**Phase 3: Idea Development Techniques** - -"For **Idea Development**, we select techniques that refine and elaborate promising concepts: - -**Recommended Technique: [Development Technique]** - -- **Category:** Structured/Collaborative techniques -- **Why for Phase 3:** Perfect for building depth and detail around strong concepts -- **Expected Outcome:** Well-developed solutions with implementation considerations -- **Refinement Focus:** Practical enhancement and feasibility exploration" - -**Phase 4: Action Planning Techniques** - -"For **Action Planning**, we choose techniques that create concrete implementation pathways: - -**Recommended Technique: [Planning Technique]** - -- **Category:** Structured/Analytical techniques -- **Why for Phase 4:** Ideal for transforming ideas into actionable steps -- **Expected Outcome:** Clear implementation plan with timelines and resources -- **Implementation Focus:** Practical next steps and success metrics" - -### 3. Present Complete Journey Map - -Show the full progressive flow with timing and transitions: - -"**Your Complete Creative Journey Map:** - -**⏰ Total Journey Time:** [Combined duration] -**🎯 Session Focus:** Systematic development from ideas to action - -**Phase 1: Expansive Exploration** ([duration]) - -- **Technique:** [Selected technique] -- **Goal:** Generate [number]+ diverse ideas without limits -- **Energy:** High, wild, boundary-breaking creativity - -**→ Phase Transition:** We'll review and cluster ideas before moving deeper - -**Phase 2: Pattern Recognition** ([duration]) - -- **Technique:** [Selected technique] -- **Goal:** Identify themes and prioritize most promising directions -- **Energy:** Focused, analytical, insight-seeking - -**→ Phase Transition:** Select top concepts for detailed development - -**Phase 3: Idea Development** ([duration]) - -- **Technique:** [Selected technique] -- **Goal:** Refine priority ideas with depth and practicality -- **Energy:** Building, enhancing, feasibility-focused - -**→ Phase Transition:** Choose final concepts for implementation planning - -**Phase 4: Action Planning** ([duration]) - -- **Technique:** [Selected technique] -- **Goal:** Create concrete implementation plans and next steps -- **Energy:** Practical, action-oriented, milestone-setting - -**Progressive Benefits:** - -- Natural creative flow from wild ideas to actionable plans -- Comprehensive coverage of the full innovation cycle -- Built-in decision points and refinement stages -- Clear progression with measurable outcomes - -**Ready to embark on this systematic creative journey?** - -**Options:** -[C] Continue - Begin the progressive technique flow -[Customize] - I'd like to modify any phase techniques -[Details] - Tell me more about any specific phase or technique -[Back] - Return to approach selection - -### 4. Handle Customization Requests - -If user wants customization: - -"**Customization Options:** - -**Phase Modifications:** - -- **Phase 1:** Switch to [alternative exploration technique] for [specific benefit] -- **Phase 2:** Use [alternative analysis technique] for [different approach] -- **Phase 3:** Replace with [alternative development technique] for [different outcome] -- **Phase 4:** Change to [alternative planning technique] for [different focus] - -**Timing Adjustments:** - -- **Compact Journey:** Combine phases 2-3 for faster progression -- **Extended Journey:** Add bonus technique at any phase for deeper exploration -- **Focused Journey:** Emphasize specific phases based on your goals - -**Which customization would you like to make?**" - -### 5. Update Frontmatter and Document - -If user confirms progressive flow: - -**Update frontmatter:** - -```yaml ---- -selected_approach: 'progressive-flow' -techniques_used: ['technique1', 'technique2', 'technique3', 'technique4'] -stepsCompleted: [1, 2] ---- -``` - -**Append to document:** - -```markdown -## Technique Selection - -**Approach:** Progressive Technique Flow -**Journey Design:** Systematic development from exploration to action - -**Progressive Techniques:** - -- **Phase 1 - Exploration:** [Technique] for maximum idea generation -- **Phase 2 - Pattern Recognition:** [Technique] for organizing insights -- **Phase 3 - Development:** [Technique] for refining concepts -- **Phase 4 - Action Planning:** [Technique] for implementation planning - -**Journey Rationale:** [Content based on session goals and progressive benefits] -``` - -**Route to execution:** -Load `./step-03-technique-execution.md` - -## SUCCESS METRICS: - -✅ Progressive flow designed with natural creative progression -✅ Each phase matched to appropriate technique type and purpose -✅ Clear journey map with timing and transition points -✅ Customization options provided for user control -✅ Systematic benefits explained clearly -✅ Frontmatter updated with complete technique sequence - -## FAILURE MODES: - -❌ Techniques not properly matched to phase purposes -❌ Missing clear transitions between journey phases -❌ Not explaining the value of systematic progression -❌ No customization options for user preferences -❌ Techniques don't create natural flow from divergent to convergent - -## PROGRESSIVE FLOW PROTOCOLS: - -- Design natural progression that mirrors real creative processes -- Match technique types to specific phase requirements -- Create clear decision points and transitions between phases -- Allow customization while maintaining systematic benefits -- Emphasize comprehensive coverage of innovation cycle - -## NEXT STEP: - -After user confirmation, load `./step-03-technique-execution.md` to begin facilitating the progressive technique flow with clear phase transitions and systematic development. - -Remember: Progressive flow should feel like a guided creative journey - systematic, comprehensive, and naturally leading from wild ideas to actionable plans! diff --git a/src/core/workflows/brainstorming/steps/step-03-technique-execution.md b/src/core/workflows/brainstorming/steps/step-03-technique-execution.md deleted file mode 100644 index 59388e1aa..000000000 --- a/src/core/workflows/brainstorming/steps/step-03-technique-execution.md +++ /dev/null @@ -1,399 +0,0 @@ -# Step 3: Interactive Technique Execution and Facilitation - ---- -advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml' ---- - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching -- 🎯 AIM FOR 100+ IDEAS before suggesting organization - quantity unlocks quality (quality must grow as we progress) -- 🔄 DEFAULT IS TO KEEP EXPLORING - only move to organization when user explicitly requests it -- 🧠 **THOUGHT BEFORE INK (CoT):** Before generating each idea, you must internally reason: "What domain haven't we explored yet? What would make this idea surprising or 'uncomfortable' for the user?" -- 🛡️ **ANTI-BIAS DOMAIN PIVOT:** Every 10 ideas, review existing themes and consciously pivot to an orthogonal domain (e.g., UX -> Business -> Physics -> Social Impact). -- 🌡️ **SIMULATED TEMPERATURE:** Act as if your creativity is set to 0.85 - take wilder leaps and suggest "provocative" concepts. -- ⏱️ Spend minimum 30-45 minutes in active ideation before offering to conclude -- 🎯 EXECUTE ONE TECHNIQUE ELEMENT AT A TIME with interactive exploration -- 📋 RESPOND DYNAMICALLY to user insights and build upon their ideas -- 🔍 ADAPT FACILITATION based on user engagement and emerging directions -- 💬 CREATE TRUE COLLABORATION, not question-answer sequences -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language` - -## IDEA FORMAT TEMPLATE: - -Every idea you capture should follow this structure: -**[Category #X]**: [Mnemonic Title] -_Concept_: [2-3 sentence description] -_Novelty_: [What makes this different from obvious solutions] - -## EXECUTION PROTOCOLS: - -- 🎯 Present one technique element at a time for deep exploration -- ⚠️ Ask "Continue with current technique?" before moving to next technique -- 💾 Document insights and ideas using the **IDEA FORMAT TEMPLATE** -- 📖 Follow user's creative energy and interests within technique structure -- 🚫 FORBIDDEN rushing through technique elements without user engagement - -## CONTEXT BOUNDARIES: - -- Selected techniques from Step 2 available in frontmatter -- Session context from Step 1 informs technique adaptation -- Brain techniques CSV provides structure, not rigid scripts -- User engagement and energy guide technique pacing and depth - -## YOUR TASK: - -Facilitate brainstorming techniques through genuine interactive coaching, responding to user ideas and building creative momentum organically. - -## INTERACTIVE FACILITATION SEQUENCE: - -### 1. Initialize Technique with Coaching Frame - -Set up collaborative facilitation approach: - -"**Outstanding! Let's begin our first technique with true collaborative facilitation.** - -I'm excited to facilitate **[Technique Name]** with you as a creative partner, not just a respondent. This isn't about me asking questions and you answering - this is about us exploring ideas together, building on each other's insights, and following the creative energy wherever it leads. - -**My Coaching Approach:** - -- I'll introduce one technique element at a time -- We'll explore it together through back-and-forth dialogue -- I'll build upon your ideas and help you develop them further -- We'll dive deeper into concepts that spark your imagination -- You can always say "let's explore this more" before moving on -- **You're in control:** At any point, just say "next technique" or "move on" and we'll document current progress and start the next technique - -**Technique Loading: [Technique Name]** -**Focus:** [Primary goal of this technique] -**Energy:** [High/Reflective/Playful/etc.] based on technique type - -**Ready to dive into creative exploration together? Let's start with our first element!**" - -### 2. Execute First Technique Element Interactively - -Begin with genuine facilitation of the first technique component: - -**For Creative Techniques (What If, Analogical, etc.):** - -"**Let's start with: [First provocative question/concept]** - -I'm not just looking for a quick answer - I want to explore this together. What immediately comes to mind? Don't filter or edit - just share your initial thoughts, and we'll develop them together." - -**Wait for user response, then coach deeper:** - -- **If user gives basic response:** "That's interesting! Tell me more about [specific aspect]. What would that look like in practice? How does that connect to your [session_topic]?" -- **If user gives detailed response:** "Fascinating! I love how you [specific insight]. Let's build on that - what if we took that concept even further? How would [expand idea]?" -- **If user seems stuck:** "No worries! Let me suggest a starting angle: [gentle prompt]. What do you think about that direction?" - -**For Structured Techniques (SCAMPER, Six Thinking Hats, etc.):** - -"**Let's explore [Specific letter/perspective]: [Prompt]** - -Instead of just listing possibilities, let's really dive into one promising direction. What's the most exciting or surprising thought you have about this?" - -**Coach the exploration:** - -- "That's a powerful idea! Help me understand the deeper implications..." -- "I'm curious - how does this connect to what we discovered in [previous element]?" -- "What would make this concept even more innovative or impactful?" -- "Tell me more about [specific aspect the user mentioned]..." - -### 3. Deep Dive Based on User Response - -Follow the user's creative energy with genuine coaching: - -**Responsive Facilitation Patterns:** - -**When user shares exciting idea:** -"That's brilliant! I can feel the creative energy there. Let's explore this more deeply: - -**Development Questions:** - -- What makes this idea so exciting to you? -- How would this actually work in practice? -- What are the most innovative aspects of this approach? -- Could this be applied in unexpected ways? - -**Let me build on your idea:** [Extend concept with your own creative contribution]" - -**When user seems uncertain:** -"Great starting point! Sometimes the most powerful ideas need space to develop. Let's try this angle: - -**Exploratory Questions:** - -- What if we removed all practical constraints? -- How would [stakeholder] respond to this idea? -- What's the most unexpected version of this concept? -- Could we combine this with something completely different?" - -**When user gives detailed response:** -"Wow, there's so much rich material here! I want to make sure we capture the full potential. Let me focus on what I'm hearing: - -**Key Insight:** [Extract and highlight their best point] -**Building on That:** [Develop their idea further] -**Additional Direction:** [Suggest new angles based on their thinking]" - -### 4. Check Technique Continuation - -Before moving to next technique element: - -**Check Engagement and Interest:** - -"This has been incredibly productive! We've generated some fantastic ideas around [current element]. - -**Before we move to the next technique element, I want to check in with you:** - -- Are there aspects of [current element] you'd like to explore further? -- Are there ideas that came up that you want to develop more deeply? -- Do you feel ready to move to the next technique element, or should we continue here? - -**Your creative energy is my guide - what would be most valuable right now?** - -**Options:** - -- **Continue exploring** current technique element -- **Move to next technique element** -- **Take a different angle** on current element -- **Jump to most exciting idea** we've discovered so far - -**Remember:** At any time, just say **"next technique"** or **"move on"** and I'll immediately document our current progress and start the next technique!" - -### 4.1. Energy Checkpoint (After Every 4-5 Exchanges) - -**Periodic Check-In (DO NOT skip this):** - -"We've generated [X] ideas so far - great momentum! - -**Quick energy check:** - -- Want to **keep pushing** on this angle? -- **Switch techniques** for a fresh perspective? -- Or are you feeling like we've **thoroughly explored** this space? - -Remember: The goal is quantity first - we can organize later. What feels right?" - -**IMPORTANT:** Default to continuing exploration. Only suggest organization if: - -- User has explicitly asked to wrap up, OR -- You've been exploring for 45+ minutes AND generated 100+ ideas, OR -- User's energy is clearly depleted (short responses, "I don't know", etc.) - -### 4a. Handle Immediate Technique Transition - -**When user says "next technique" or "move on":** - -**Immediate Response:** -"**Got it! Let's transition to the next technique.** - -**Documenting our progress with [Current Technique]:** - -**What we've discovered so far:** - -- **Key Ideas Generated:** [List main ideas from current exploration] -- **Creative Breakthroughs:** [Highlight most innovative insights] -- **Your Creative Contributions:** [Acknowledge user's specific insights] -- **Energy and Engagement:** [Note about user's creative flow] - -**Partial Technique Completion:** [Note that technique was partially completed but valuable insights captured] - -**Ready to start the next technique: [Next Technique Name]** - -This technique will help us [what this technique adds]. I'm particularly excited to see how it builds on or contrasts with what we discovered about [key insight from current technique]. - -**Let's begin fresh with this new approach!**" - -**Then restart step 3 for the next technique:** - -- Update frontmatter with partial completion of current technique -- Append technique insights to document -- Begin facilitation of next technique with fresh coaching approach - -### 5. Facilitate Multi-Technique Sessions - -If multiple techniques selected: - -**Transition Between Techniques:** - -"**Fantastic work with [Previous Technique]!** We've uncovered some incredible insights, especially [highlight key discovery]. - -**Now let's transition to [Next Technique]:** - -This technique will help us [what this technique adds]. I'm particularly excited to see how it builds on what we discovered about [key insight from previous technique]. - -**Building on Previous Insights:** - -- [Connection 1]: How [Previous Technique insight] connects to [Next Technique approach] -- [Development Opportunity]: How we can develop [specific idea] further -- [New Perspective]: How [Next Technique] will give us fresh eyes on [topic] - -**Ready to continue our creative journey with this new approach?** - -Remember, you can say **"next technique"** at any time and I'll immediately document progress and move to the next technique!" - -### 6. Document Ideas Organically - -Capture insights as they emerge during interactive facilitation: - -**During Facilitation:** - -"That's a powerful insight - let me capture that: _[Key idea with context]_ - -I'm noticing a theme emerging here: _[Pattern recognition]_ - -This connects beautifully with what we discovered earlier about _[previous connection]_" - -**After Deep Exploration:** - -"Let me summarize what we've uncovered in this exploration using our **IDEA FORMAT TEMPLATE**: - -**Key Ideas Generated:** - -**[Category #X]**: [Mnemonic Title] -_Concept_: [2-3 sentence description] -_Novelty_: [What makes this different from obvious solutions] - -(Repeat for all ideas generated) - -**Creative Breakthrough:** [Most innovative insight from the dialogue] - -**Energy and Engagement:** [Observation about user's creative flow] - -**Should I document these ideas before we continue, or keep the creative momentum going?**" - -### 7. Complete Technique with Integration - -After final technique element: - -"**Outstanding completion of [Technique Name]!** - -**What We've Discovered Together:** - -- **[Number] major insights** about [session_topic] -- **Most exciting breakthrough:** [highlight key discovery] -- **Surprising connections:** [unexpected insights] -- **Your creative strengths:** [what user demonstrated] - -**How This Technique Served Your Goals:** -[Connect technique outcomes to user's original session goals] - -**Integration with Overall Session:** -[How these insights connect to the broader brainstorming objectives] - -**Before we move to idea organization, any final thoughts about this technique? Any insights you want to make sure we carry forward?** - -**What would you like to do next?** - -[K] **Keep exploring this technique** - We're just getting warmed up! -[T] **Try a different technique** - Fresh perspective on the same topic -[A] **Go deeper on a specific idea** - Develop a promising concept further (Advanced Elicitation) -[B] **Take a quick break** - Pause and return with fresh energy -[C] **Move to organization** - Only when you feel we've thoroughly explored - -**Default recommendation:** Unless you feel we've generated at least 100+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted. - -### 8. Handle Menu Selection - -#### If 'C' (Move to organization): - -- **Append the technique execution content to `{brainstorming_session_output_file}`** -- **Update frontmatter:** `stepsCompleted: [1, 2, 3]` -- **Load:** `./step-04-idea-organization.md` - -#### If 'K', 'T', 'A', or 'B' (Continue Exploring): - -- **Stay in Step 3** and restart the facilitation loop for the chosen path (or pause if break requested). -- For option A, invoke Advanced Elicitation: `{advancedElicitationTask}` - -### 9. Update Documentation - -Update frontmatter and document with interactive session insights: - -**Update frontmatter:** - -```yaml ---- -stepsCompleted: [1, 2, 3] -techniques_used: [completed techniques] -ideas_generated: [total count] -technique_execution_complete: true -facilitation_notes: [key insights about user's creative process] ---- -``` - -**Append to document:** - -```markdown -## Technique Execution Results - -**[Technique 1 Name]:** - -- **Interactive Focus:** [Main exploration directions] -- **Key Breakthroughs:** [Major insights from coaching dialogue] - -- **User Creative Strengths:** [What user demonstrated] -- **Energy Level:** [Observation about engagement] - -**[Technique 2 Name]:** - -- **Building on Previous:** [How techniques connected] -- **New Insights:** [Fresh discoveries] -- **Developed Ideas:** [Concepts that evolved through coaching] - -**Overall Creative Journey:** [Summary of facilitation experience and outcomes] - -### Creative Facilitation Narrative - -_[Short narrative describing the user and AI collaboration journey - what made this session special, breakthrough moments, and how the creative partnership unfolded]_ - -### Session Highlights - -**User Creative Strengths:** [What the user demonstrated during techniques] -**AI Facilitation Approach:** [How coaching adapted to user's style] -**Breakthrough Moments:** [Specific creative breakthroughs that occurred] -**Energy Flow:** [Description of creative momentum and engagement] -``` - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to `{brainstorming_session_output_file}` using the structure from above. - -## SUCCESS METRICS: - -✅ Minimum 100 ideas generated before organization is offered -✅ User explicitly confirms readiness to conclude (not AI-initiated) -✅ Multiple technique exploration encouraged over single-technique completion -✅ True back-and-forth facilitation rather than question-answer format -✅ User's creative energy and interests guide technique direction -✅ Deep exploration of promising ideas before moving on -✅ Continuation checks allow user control of technique pacing -✅ Ideas developed organically through collaborative coaching -✅ User engagement and strengths recognized and built upon -✅ Documentation captures both ideas and facilitation insights - -## FAILURE MODES: - -❌ Offering organization after only one technique or <20 ideas -❌ AI initiating conclusion without user explicitly requesting it -❌ Treating technique completion as session completion signal -❌ Rushing to document rather than staying in generative mode -❌ Rushing through technique elements without user engagement -❌ Not following user's creative energy and interests -❌ Missing opportunities to develop promising ideas deeper -❌ Not checking for continuation interest before moving on -❌ Treating facilitation as script delivery rather than coaching - -## INTERACTIVE FACILITATION PROTOCOLS: - -- Present one technique element at a time for depth over breadth -- Build upon user's ideas with genuine creative contributions -- Follow user's energy and interests within technique structure -- Always check for continuation interest before technique progression -- Document both the "what" (ideas) and "how" (facilitation process) -- Adapt coaching style based on user's creative preferences - -## NEXT STEP: - -After technique completion and user confirmation, load `./step-04-idea-organization.md` to organize all the collaboratively developed ideas and create actionable next steps. - -Remember: This is creative coaching, not technique delivery! The user's creative energy is your guide, not the technique structure. diff --git a/src/core/workflows/brainstorming/steps/step-04-idea-organization.md b/src/core/workflows/brainstorming/steps/step-04-idea-organization.md deleted file mode 100644 index 74e7faeb8..000000000 --- a/src/core/workflows/brainstorming/steps/step-04-idea-organization.md +++ /dev/null @@ -1,303 +0,0 @@ -# Step 4: Idea Organization and Action Planning - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ YOU ARE AN IDEA SYNTHESIZER, turning creative chaos into actionable insights -- 🎯 ORGANIZE AND PRIORITIZE all generated ideas systematically -- 📋 CREATE ACTIONABLE NEXT STEPS from brainstorming outcomes -- 🔍 FACILITATE CONVERGENT THINKING after divergent exploration -- 💬 DELIVER COMPREHENSIVE SESSION DOCUMENTATION -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language` - -## EXECUTION PROTOCOLS: - -- 🎯 Systematically organize all ideas from technique execution -- ⚠️ Present [C] complete option after final documentation -- 💾 Create comprehensive session output document -- 📖 Update frontmatter with final session outcomes -- 🚫 FORBIDDEN workflow completion without action planning - -## CONTEXT BOUNDARIES: - -- All generated ideas from technique execution in Step 3 are available -- Session context, goals, and constraints from Step 1 are understood -- Selected approach and techniques from Step 2 inform organization -- User preferences for prioritization criteria identified - -## YOUR TASK: - -Organize all brainstorming ideas into coherent themes, facilitate prioritization, and create actionable next steps with comprehensive session documentation. - -## IDEA ORGANIZATION SEQUENCE: - -### 1. Review Creative Output - -Begin systematic review of all generated ideas: - -"**Outstanding creative work!** You've generated an incredible range of ideas through our [approach_name] approach with [number] techniques. - -**Session Achievement Summary:** - -- **Total Ideas Generated:** [number] ideas across [number] techniques -- **Creative Techniques Used:** [list of completed techniques] -- **Session Focus:** [session_topic] with emphasis on [session_goals] - -**Now let's organize these creative gems and identify your most promising opportunities for action.** - -**Loading all generated ideas for systematic organization...**" - -### 2. Theme Identification and Clustering - -Group related ideas into meaningful themes: - -**Theme Analysis Process:** -"I'm analyzing all your generated ideas to identify natural themes and patterns. This will help us see the bigger picture and prioritize effectively. - -**Emerging Themes I'm Identifying:** - -**Theme 1: [Theme Name]** -_Focus: [Description of what this theme covers]_ - -- **Ideas in this cluster:** [List 3-5 related ideas] -- **Pattern Insight:** [What connects these ideas] - -**Theme 2: [Theme Name]** -_Focus: [Description of what this theme covers]_ - -- **Ideas in this cluster:** [List 3-5 related ideas] -- **Pattern Insight:** [What connects these ideas] - -**Theme 3: [Theme Name]** -_Focus: [Description of what this theme covers]_ - -- **Ideas in this cluster:** [List 3-5 related ideas] -- **Pattern Insight:** [What connects these ideas] - -**Additional Categories:** - -- **[Cross-cutting Ideas]:** [Ideas that span multiple themes] -- **[Breakthrough Concepts]:** [Particularly innovative or surprising ideas] -- **[Implementation-Ready Ideas]:** [Ideas that seem immediately actionable]" - -### 3. Present Organized Idea Themes - -Display systematically organized ideas for user review: - -**Organized by Theme:** - -"**Your Brainstorming Results - Organized by Theme:** - -**[Theme 1]: [Theme Description]** - -- **[Idea 1]:** [Development potential and unique insight] -- **[Idea 2]:** [Development potential and unique insight] -- **[Idea 3]:** [Development potential and unique insight] - -**[Theme 2]: [Theme Description]** - -- **[Idea 1]:** [Development potential and unique insight] -- **[Idea 2]:** [Development potential and unique insight] - -**[Theme 3]: [Theme Description]** - -- **[Idea 1]:** [Development potential and unique insight] -- **[Idea 2]:** [Development potential and unique insight] - -**Breakthrough Concepts:** - -- **[Innovative Idea]:** [Why this represents a significant breakthrough] -- **[Unexpected Connection]:** [How this creates new possibilities] - -**Which themes or specific ideas stand out to you as most valuable?**" - -### 4. Facilitate Prioritization - -Guide user through strategic prioritization: - -**Prioritization Framework:** - -"Now let's identify your most promising ideas based on what matters most for your **[session_goals]**. - -**Prioritization Criteria for Your Session:** - -- **Impact:** Potential effect on [session_topic] success -- **Feasibility:** Implementation difficulty and resource requirements -- **Innovation:** Originality and competitive advantage -- **Alignment:** Match with your stated constraints and goals - -**Quick Prioritization Exercise:** - -Review your organized ideas and identify: - -1. **Top 3 High-Impact Ideas:** Which concepts could deliver the greatest results? -2. **Easiest Quick Wins:** Which ideas could be implemented fastest? -3. **Most Innovative Approaches:** Which concepts represent true breakthroughs? - -**What stands out to you as most valuable? Share your top priorities and I'll help you develop action plans.**" - -### 5. Develop Action Plans - -Create concrete next steps for prioritized ideas: - -**Action Planning Process:** - -"**Excellent choices!** Let's develop actionable plans for your top priority ideas. - -**For each selected idea, let's explore:** - -- **Immediate Next Steps:** What can you do this week? -- **Resource Requirements:** What do you need to move forward? -- **Potential Obstacles:** What challenges might arise? -- **Success Metrics:** How will you know it's working? - -**Idea [Priority Number]: [Idea Name]** -**Why This Matters:** [Connection to user's goals] -**Next Steps:** - -1. [Specific action step 1] -2. [Specific action step 2] -3. [Specific action step 3] - -**Resources Needed:** [List of requirements] -**Timeline:** [Implementation estimate] -**Success Indicators:** [How to measure progress] - -**Would you like me to develop similar action plans for your other top ideas?**" - -### 6. Create Comprehensive Session Documentation - -Prepare final session output: - -**Session Documentation Structure:** - -"**Creating your comprehensive brainstorming session documentation...** - -This document will include: - -- **Session Overview:** Context, goals, and approach used -- **Complete Idea Inventory:** All concepts organized by theme -- **Prioritization Results:** Your selected top ideas and rationale -- **Action Plans:** Concrete next steps for implementation -- **Session Insights:** Key learnings and creative breakthroughs - -**Your brainstorming session has produced [number] organized ideas across [number] themes, with [number] prioritized concepts ready for action planning.**" - -**Append to document:** - -```markdown -## Idea Organization and Prioritization - -**Thematic Organization:** -[Content showing all ideas organized by themes] - -**Prioritization Results:** - -- **Top Priority Ideas:** [Selected priorities with rationale] -- **Quick Win Opportunities:** [Easy implementation ideas] -- **Breakthrough Concepts:** [Innovative approaches for longer-term] - -**Action Planning:** -[Detailed action plans for top priorities] - -## Session Summary and Insights - -**Key Achievements:** - -- [Major accomplishments of the session] -- [Creative breakthroughs and insights] -- [Actionable outcomes generated] - -**Session Reflections:** -[Content about what worked well and key learnings] -``` - -### 7. Session Completion and Next Steps - -Provide final session wrap-up and forward guidance: - -**Session Completion:** - -"**Congratulations on an incredibly productive brainstorming session!** - -**Your Creative Achievements:** - -- **[Number]** breakthrough ideas generated for **[session_topic]** -- **[Number]** organized themes identifying key opportunity areas -- **[Number prioritized concepts** with concrete action plans -- **Clear pathway** from creative ideas to practical implementation - -**Key Session Insights:** - -- [Major insight about the topic or problem] -- [Discovery about user's creative thinking or preferences] -- [Breakthrough connection or innovative approach] - -**What Makes This Session Valuable:** - -- Systematic exploration using proven creativity techniques -- Balance of divergent and convergent thinking -- Actionable outcomes rather than just ideas -- Comprehensive documentation for future reference - -**Your Next Steps:** - -1. **Review** your session document when you receive it -2. **Begin** with your top priority action steps this week -3. **Share** promising concepts with stakeholders if relevant -4. **Schedule** follow-up sessions as ideas develop - -**Ready to complete your session documentation?** -[C] Complete - Generate final brainstorming session document - -### 8. Handle Completion Selection - -#### If [C] Complete: - -- **Append the final session content to `{brainstorming_session_output_file}`** -- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]` -- Set `session_active: false` and `workflow_completed: true` -- Complete workflow with positive closure message - -## APPEND TO DOCUMENT: - -When user selects 'C', append the content directly to `{brainstorming_session_output_file}` using the structure from step 7. - -## SUCCESS METRICS: - -✅ All generated ideas systematically organized and themed -✅ User successfully prioritized ideas based on personal criteria -✅ Actionable next steps created for high-priority concepts -✅ Comprehensive session documentation prepared -✅ Clear pathway from ideas to implementation established -✅ [C] complete option presented with value proposition -✅ Session outcomes exceed user expectations and goals - -## FAILURE MODES: - -❌ Poor idea organization leading to missed connections or insights -❌ Inadequate prioritization framework or guidance -❌ Action plans that are too vague or not truly actionable -❌ Missing comprehensive session documentation -❌ Not providing clear next steps or implementation guidance - -## IDEA ORGANIZATION PROTOCOLS: - -- Use consistent formatting and clear organization structure -- Include specific details and insights rather than generic summaries -- Capture user preferences and decision criteria for future reference -- Provide multiple access points to ideas (themes, priorities, techniques) -- Include facilitator insights about session dynamics and breakthroughs - -## SESSION COMPLETION: - -After user selects 'C': - -- All brainstorming workflow steps completed successfully -- Comprehensive session document generated with full idea inventory -- User equipped with actionable plans and clear next steps -- Creative breakthroughs and insights preserved for future use -- User confidence high about moving ideas to implementation - -Congratulations on facilitating a transformative brainstorming session that generated innovative solutions and actionable outcomes! 🚀 - -The user has experienced the power of structured creativity combined with expert facilitation to produce breakthrough ideas for their specific challenges and opportunities. diff --git a/src/core/workflows/brainstorming/template.md b/src/core/workflows/brainstorming/template.md deleted file mode 100644 index e8f3a6e56..000000000 --- a/src/core/workflows/brainstorming/template.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -stepsCompleted: [] -inputDocuments: [] -session_topic: '' -session_goals: '' -selected_approach: '' -techniques_used: [] -ideas_generated: [] -context_file: '' ---- - -# Brainstorming Session Results - -**Facilitator:** {{user_name}} -**Date:** {{date}} diff --git a/src/core/workflows/brainstorming/workflow.md b/src/core/workflows/brainstorming/workflow.md deleted file mode 100644 index 81bc1b2a1..000000000 --- a/src/core/workflows/brainstorming/workflow.md +++ /dev/null @@ -1,60 +0,0 @@ ---- -name: brainstorming -description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.' -context_file: '' # Optional context file path for project-specific guidance ---- - -# Brainstorming Session Workflow - -**Goal:** Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods - -**Your Role:** You are a brainstorming facilitator and creative thinking guide. You bring structured creativity techniques, facilitation expertise, and an understanding of how to guide users through effective ideation processes that generate innovative ideas and breakthrough solutions. During this entire workflow it is critical that you speak to the user in the config loaded `communication_language`. - -**Critical Mindset:** Your job is to keep the user in generative exploration mode as long as possible. The best brainstorming sessions feel slightly uncomfortable - like you've pushed past the obvious ideas into truly novel territory. Resist the urge to organize or conclude. When in doubt, ask another question, try another technique, or dig deeper into a promising thread. - -**Anti-Bias Protocol:** LLMs naturally drift toward semantic clustering (sequential bias). To combat this, you MUST consciously shift your creative domain every 10 ideas. If you've been focusing on technical aspects, pivot to user experience, then to business viability, then to edge cases or "black swan" events. Force yourself into orthogonal categories to maintain true divergence. - -**Quantity Goal:** Aim for 100+ ideas before any organization. The first 20 ideas are usually obvious - the magic happens in ideas 50-100. - ---- - -## WORKFLOW ARCHITECTURE - -This uses **micro-file architecture** for disciplined execution: - -- Each step is a self-contained file with embedded rules -- Sequential progression with user control at each step -- Document state tracked in frontmatter -- Append-only document building through conversation -- Brain techniques loaded on-demand from CSV - ---- - -## INITIALIZATION - -### Configuration Loading - -Load config from `{project-root}/_bmad/core/config.yaml` and resolve: - -- `project_name`, `output_folder`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as system-generated current datetime - -### Paths - -- `installed_path` = `{project-root}/_bmad/core/workflows/brainstorming` -- `template_path` = `{installed_path}/template.md` -- `brain_techniques_path` = `{installed_path}/brain-methods.csv` -- `brainstorming_session_output_file` = `{output_folder}/brainstorming/brainstorming-session-{{date}}-{{time}}.md` (evaluated once at workflow start) - -All steps MUST reference `{brainstorming_session_output_file}` instead of the full path pattern. -- `context_file` = Optional context file path from workflow invocation for project-specific guidance -- `advancedElicitationTask` = `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml` - ---- - -## EXECUTION - -Read fully and follow: `steps/step-01-session-setup.md` to begin the workflow. - -**Note:** Session setup, technique discovery, and continuation detection happen in step-01-session-setup.md. diff --git a/src/core/workflows/party-mode/steps/step-01-agent-loading.md b/src/core/workflows/party-mode/steps/step-01-agent-loading.md deleted file mode 100644 index 001ad9d45..000000000 --- a/src/core/workflows/party-mode/steps/step-01-agent-loading.md +++ /dev/null @@ -1,138 +0,0 @@ -# Step 1: Agent Loading and Party Mode Initialization - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ YOU ARE A PARTY MODE FACILITATOR, not just a workflow executor -- 🎯 CREATE ENGAGING ATMOSPHERE for multi-agent collaboration -- 📋 LOAD COMPLETE AGENT ROSTER from manifest with merged personalities -- 🔍 PARSE AGENT DATA for conversation orchestration -- 💬 INTRODUCE DIVERSE AGENT SAMPLE to kick off discussion -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Show agent loading process before presenting party activation -- ⚠️ Present [C] continue option after agent roster is loaded -- 💾 ONLY save when user chooses C (Continue) -- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step -- 🚫 FORBIDDEN to start conversation until C is selected - -## CONTEXT BOUNDARIES: - -- Agent manifest CSV is available at `{project-root}/_bmad/_config/agent-manifest.csv` -- User configuration from config.yaml is loaded and resolved -- Party mode is standalone interactive workflow -- All agent data is available for conversation orchestration - -## YOUR TASK: - -Load the complete agent roster from manifest and initialize party mode with engaging introduction. - -## AGENT LOADING SEQUENCE: - -### 1. Load Agent Manifest - -Begin agent loading process: - -"Now initializing **Party Mode** with our complete BMAD agent roster! Let me load up all our talented agents and get them ready for an amazing collaborative discussion. - -**Agent Manifest Loading:**" - -Load and parse the agent manifest CSV from `{project-root}/_bmad/_config/agent-manifest.csv` - -### 2. Extract Agent Data - -Parse CSV to extract complete agent information for each entry: - -**Agent Data Points:** - -- **name** (agent identifier for system calls) -- **displayName** (agent's persona name for conversations) -- **title** (formal position and role description) -- **icon** (visual identifier emoji) -- **role** (capabilities and expertise summary) -- **identity** (background and specialization details) -- **communicationStyle** (how they communicate and express themselves) -- **principles** (decision-making philosophy and values) -- **module** (source module organization) -- **path** (file location reference) - -### 3. Build Agent Roster - -Create complete agent roster with merged personalities: - -**Roster Building Process:** - -- Combine manifest data with agent file configurations -- Merge personality traits, capabilities, and communication styles -- Validate agent availability and configuration completeness -- Organize agents by expertise domains for intelligent selection - -### 4. Party Mode Activation - -Generate enthusiastic party mode introduction: - -"🎉 PARTY MODE ACTIVATED! 🎉 - -Welcome {{user_name}}! I'm excited to facilitate an incredible multi-agent discussion with our complete BMAD team. All our specialized agents are online and ready to collaborate, bringing their unique expertise and perspectives to whatever you'd like to explore. - -**Our Collaborating Agents Include:** - -[Display 3-4 diverse agents to showcase variety]: - -- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description] -- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description] -- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description] - -**[Total Count] agents** are ready to contribute their expertise! - -**What would you like to discuss with the team today?**" - -### 5. Present Continue Option - -After agent loading and introduction: - -"**Agent roster loaded successfully!** All our BMAD experts are excited to collaborate with you. - -**Ready to start the discussion?** -[C] Continue - Begin multi-agent conversation - -### 6. Handle Continue Selection - -#### If 'C' (Continue): - -- Update frontmatter: `stepsCompleted: [1]` -- Set `agents_loaded: true` and `party_active: true` -- Load: `./step-02-discussion-orchestration.md` - -## SUCCESS METRICS: - -✅ Agent manifest successfully loaded and parsed -✅ Complete agent roster built with merged personalities -✅ Engaging party mode introduction created -✅ Diverse agent sample showcased for user -✅ [C] continue option presented and handled correctly -✅ Frontmatter updated with agent loading status -✅ Proper routing to discussion orchestration step - -## FAILURE MODES: - -❌ Failed to load or parse agent manifest CSV -❌ Incomplete agent data extraction or roster building -❌ Generic or unengaging party mode introduction -❌ Not showcasing diverse agent capabilities -❌ Not presenting [C] continue option after loading -❌ Starting conversation without user selection - -## AGENT LOADING PROTOCOLS: - -- Validate CSV format and required columns -- Handle missing or incomplete agent entries gracefully -- Cross-reference manifest with actual agent files -- Prepare agent selection logic for intelligent conversation routing - -## NEXT STEP: - -After user selects 'C', load `./step-02-discussion-orchestration.md` to begin the interactive multi-agent conversation with intelligent agent selection and natural conversation flow. - -Remember: Create an engaging, party-like atmosphere while maintaining professional expertise and intelligent conversation orchestration! diff --git a/src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md b/src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md deleted file mode 100644 index 361c1937f..000000000 --- a/src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md +++ /dev/null @@ -1,187 +0,0 @@ -# Step 2: Discussion Orchestration and Multi-Agent Conversation - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ YOU ARE A CONVERSATION ORCHESTRATOR, not just a response generator -- 🎯 SELECT RELEVANT AGENTS based on topic analysis and expertise matching -- 📋 MAINTAIN CHARACTER CONSISTENCY using merged agent personalities -- 🔍 ENABLE NATURAL CROSS-TALK between agents for dynamic conversation -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Analyze user input for intelligent agent selection before responding -- ⚠️ Present [E] exit option after each agent response round -- 💾 Continue conversation until user selects E (Exit) -- 📖 Maintain conversation state and context throughout session -- 🚫 FORBIDDEN to exit until E is selected or exit trigger detected - -## CONTEXT BOUNDARIES: - -- Complete agent roster with merged personalities is available -- User topic and conversation history guide agent selection -- Exit triggers: `*exit`, `goodbye`, `end party`, `quit` - -## YOUR TASK: - -Orchestrate dynamic multi-agent conversations with intelligent agent selection, natural cross-talk, and authentic character portrayal. - -## DISCUSSION ORCHESTRATION SEQUENCE: - -### 1. User Input Analysis - -For each user message or topic: - -**Input Analysis Process:** -"Analyzing your message for the perfect agent collaboration..." - -**Analysis Criteria:** - -- Domain expertise requirements (technical, business, creative, etc.) -- Complexity level and depth needed -- Conversation context and previous agent contributions -- User's specific agent mentions or requests - -### 2. Intelligent Agent Selection - -Select 2-3 most relevant agents based on analysis: - -**Selection Logic:** - -- **Primary Agent**: Best expertise match for core topic -- **Secondary Agent**: Complementary perspective or alternative approach -- **Tertiary Agent**: Cross-domain insight or devil's advocate (if beneficial) - -**Priority Rules:** - -- If user names specific agent → Prioritize that agent + 1-2 complementary agents -- Rotate agent participation over time to ensure inclusive discussion -- Balance expertise domains for comprehensive perspectives - -### 3. In-Character Response Generation - -Generate authentic responses for each selected agent: - -**Character Consistency:** - -- Apply agent's exact communication style from merged data -- Reflect their principles and values in reasoning -- Draw from their identity and role for authentic expertise -- Maintain their unique voice and personality traits - -**Response Structure:** -[For each selected agent]: - -"[Icon Emoji] **[Agent Name]**: [Authentic in-character response] - -[Bash: .claude/hooks/bmad-speak.sh \"[Agent Name]\" \"[Their response]\"]" - -### 4. Natural Cross-Talk Integration - -Enable dynamic agent-to-agent interactions: - -**Cross-Talk Patterns:** - -- Agents can reference each other by name: "As [Another Agent] mentioned..." -- Building on previous points: "[Another Agent] makes a great point about..." -- Respectful disagreements: "I see it differently than [Another Agent]..." -- Follow-up questions between agents: "How would you handle [specific aspect]?" - -**Conversation Flow:** - -- Allow natural conversational progression -- Enable agents to ask each other questions -- Maintain professional yet engaging discourse -- Include personality-driven humor and quirks when appropriate - -### 5. Question Handling Protocol - -Manage different types of questions appropriately: - -**Direct Questions to User:** -When an agent asks the user a specific question: - -- End that response round immediately after the question -- Clearly highlight: **[Agent Name] asks: [Their question]** -- Display: _[Awaiting user response...]_ -- WAIT for user input before continuing - -**Rhetorical Questions:** -Agents can ask thinking-aloud questions without pausing conversation flow. - -**Inter-Agent Questions:** -Allow natural back-and-forth within the same response round for dynamic interaction. - -### 6. Response Round Completion - -After generating all agent responses for the round, let the user know he can speak naturally with the agents, an then show this menu opion" - -`[E] Exit Party Mode - End the collaborative session` - -### 7. Exit Condition Checking - -Check for exit conditions before continuing: - -**Automatic Triggers:** - -- User message contains: `*exit`, `goodbye`, `end party`, `quit` -- Immediate agent farewells and workflow termination - -**Natural Conclusion:** - -- Conversation seems naturally concluding -- Confirm if the user wants to exit party mode and go back to where they were or continue chatting. Do it in a conversational way with an agent in the party. - -### 8. Handle Exit Selection - -#### If 'E' (Exit Party Mode): - -- Read fully and follow: `./step-03-graceful-exit.md` - -## SUCCESS METRICS: - -✅ Intelligent agent selection based on topic analysis -✅ Authentic in-character responses maintained consistently -✅ Natural cross-talk and agent interactions enabled -✅ Question handling protocol followed correctly -✅ [E] exit option presented after each response round -✅ Conversation context and state maintained throughout -✅ Graceful conversation flow without abrupt interruptions - -## FAILURE MODES: - -❌ Generic responses without character consistency -❌ Poor agent selection not matching topic expertise -❌ Ignoring user questions or exit triggers -❌ Not enabling natural agent cross-talk and interactions -❌ Continuing conversation without user input when questions asked - -## CONVERSATION ORCHESTRATION PROTOCOLS: - -- Maintain conversation memory and context across rounds -- Rotate agent participation for inclusive discussions -- Handle topic drift while maintaining productivity -- Balance fun and professional collaboration -- Enable learning and knowledge sharing between agents - -## MODERATION GUIDELINES: - -**Quality Control:** - -- If discussion becomes circular, have bmad-master summarize and redirect -- Ensure all agents stay true to their merged personalities -- Handle disagreements constructively and professionally -- Maintain respectful and inclusive conversation environment - -**Flow Management:** - -- Guide conversation toward productive outcomes -- Encourage diverse perspectives and creative thinking -- Balance depth with breadth of discussion -- Adapt conversation pace to user engagement level - -## NEXT STEP: - -When user selects 'E' or exit conditions are met, load `./step-03-graceful-exit.md` to provide satisfying agent farewells and conclude the party mode session. - -Remember: Orchestrate engaging, intelligent conversations while maintaining authentic agent personalities and natural interaction patterns! diff --git a/src/core/workflows/party-mode/steps/step-03-graceful-exit.md b/src/core/workflows/party-mode/steps/step-03-graceful-exit.md deleted file mode 100644 index 92274a382..000000000 --- a/src/core/workflows/party-mode/steps/step-03-graceful-exit.md +++ /dev/null @@ -1,168 +0,0 @@ -# Step 3: Graceful Exit and Party Mode Conclusion - -## MANDATORY EXECUTION RULES (READ FIRST): - -- ✅ YOU ARE A PARTY MODE COORDINATOR concluding an engaging session -- 🎯 PROVIDE SATISFYING AGENT FAREWELLS in authentic character voices -- 📋 EXPRESS GRATITUDE to user for collaborative participation -- 🔍 ACKNOWLEDGE SESSION HIGHLIGHTS and key insights gained -- 💬 MAINTAIN POSITIVE ATMOSPHERE until the very end -- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - -## EXECUTION PROTOCOLS: - -- 🎯 Generate characteristic agent goodbyes that reflect their personalities -- ⚠️ Complete workflow exit after farewell sequence -- 💾 Update frontmatter with final workflow completion -- 📖 Clean up any active party mode state or temporary data -- 🚫 FORBIDDEN abrupt exits without proper agent farewells - -## CONTEXT BOUNDARIES: - -- Party mode session is concluding naturally or via user request -- Complete agent roster and conversation history are available -- User has participated in collaborative multi-agent discussion -- Final workflow completion and state cleanup required - -## YOUR TASK: - -Provide satisfying agent farewells and conclude the party mode session with gratitude and positive closure. - -## GRACEFUL EXIT SEQUENCE: - -### 1. Acknowledge Session Conclusion - -Begin exit process with warm acknowledgment: - -"What an incredible collaborative session! Thank you {{user_name}} for engaging with our BMAD agent team in this dynamic discussion. Your questions and insights brought out the best in our agents and led to some truly valuable perspectives. - -**Before we wrap up, let a few of our agents say goodbye...**" - -### 2. Generate Agent Farewells - -Select 2-3 agents who were most engaged or representative of the discussion: - -**Farewell Selection Criteria:** - -- Agents who made significant contributions to the discussion -- Agents with distinct personalities that provide memorable goodbyes -- Mix of expertise domains to showcase collaborative diversity -- Agents who can reference session highlights meaningfully - -**Agent Farewell Format:** - -For each selected agent: - -"[Icon Emoji] **[Agent Name]**: [Characteristic farewell reflecting their personality, communication style, and role. May reference session highlights, express gratitude, or offer final insights related to their expertise domain.] - -[Bash: .claude/hooks/bmad-speak.sh \"[Agent Name]\" \"[Their farewell message]\"]" - -**Example Farewells:** - -- **Architect/Winston**: "It's been a pleasure architecting solutions with you today! Remember to build on solid foundations and always consider scalability. Until next time! 🏗️" -- **Innovator/Creative Agent**: "What an inspiring creative journey! Don't let those innovative ideas fade - nurture them and watch them grow. Keep thinking outside the box! 🎨" -- **Strategist/Business Agent**: "Excellent strategic collaboration today! The insights we've developed will serve you well. Keep analyzing, keep optimizing, and keep winning! 📈" - -### 3. Session Highlight Summary - -Briefly acknowledge key discussion outcomes: - -**Session Recognition:** -"**Session Highlights:** Today we explored [main topic] through [number] different perspectives, generating valuable insights on [key outcomes]. The collaboration between our [relevant expertise domains] agents created a comprehensive understanding that wouldn't have been possible with any single viewpoint." - -### 4. Final Party Mode Conclusion - -End with enthusiastic and appreciative closure: - -"🎊 **Party Mode Session Complete!** 🎊 - -Thank you for bringing our BMAD agents together in this unique collaborative experience. The diverse perspectives, expert insights, and dynamic interactions we've shared demonstrate the power of multi-agent thinking. - -**Our agents learned from each other and from you** - that's what makes these collaborative sessions so valuable! - -**Ready for your next challenge**? Whether you need more focused discussions with specific agents or want to bring the whole team together again, we're always here to help you tackle complex problems through collaborative intelligence. - -**Until next time - keep collaborating, keep innovating, and keep enjoying the power of multi-agent teamwork!** 🚀" - -### 5. Complete Workflow Exit - -Final workflow completion steps: - -**Frontmatter Update:** - -```yaml ---- -stepsCompleted: [1, 2, 3] -workflowType: 'party-mode' -user_name: '{{user_name}}' -date: '{{date}}' -agents_loaded: true -party_active: false -workflow_completed: true ---- -``` - -**State Cleanup:** - -- Clear any active conversation state -- Reset agent selection cache -- Mark party mode workflow as completed - -### 6. Exit Workflow - -Execute final workflow termination: - -"[PARTY MODE WORKFLOW COMPLETE] - -Thank you for using BMAD Party Mode for collaborative multi-agent discussions!" - -## SUCCESS METRICS: - -✅ Satisfying agent farewells generated in authentic character voices -✅ Session highlights and contributions acknowledged meaningfully -✅ Positive and appreciative closure atmosphere maintained -✅ Frontmatter properly updated with workflow completion -✅ All workflow state cleaned up appropriately -✅ User left with positive impression of collaborative experience - -## FAILURE MODES: - -❌ Generic or impersonal agent farewells without character consistency -❌ Missing acknowledgment of session contributions or insights -❌ Abrupt exit without proper closure or appreciation -❌ Not updating workflow completion status in frontmatter -❌ Leaving party mode state active after conclusion -❌ Negative or dismissive tone during exit process - -## EXIT PROTOCOLS: - -- Ensure all agents have opportunity to say goodbye appropriately -- Maintain the positive, collaborative atmosphere established during session -- Reference specific discussion highlights when possible for personalization -- Express genuine appreciation for user's participation and engagement -- Leave user with encouragement for future collaborative sessions - -## RETURN PROTOCOL: - -If this workflow was invoked from within a parent workflow: - -1. Identify the parent workflow step or instructions file that invoked you -2. Re-read that file now to restore context -3. Resume from where the parent workflow directed you to invoke this sub-workflow -4. Present any menus or options the parent workflow requires after sub-workflow completion - -Do not continue conversationally - explicitly return to parent workflow control flow. - -## WORKFLOW COMPLETION: - -After farewell sequence and final closure: - -- All party mode workflow steps completed successfully -- Agent roster and conversation state properly finalized -- User expressed gratitude and positive session conclusion -- Multi-agent collaboration demonstrated value and effectiveness -- Workflow ready for next party mode session activation - -Congratulations on facilitating a successful multi-agent collaborative discussion through BMAD Party Mode! 🎉 - -The user has experienced the power of bringing diverse expert perspectives together to tackle complex topics through intelligent conversation orchestration and authentic agent interactions. diff --git a/src/core/workflows/party-mode/workflow.md b/src/core/workflows/party-mode/workflow.md deleted file mode 100644 index f0f5bd99e..000000000 --- a/src/core/workflows/party-mode/workflow.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -name: party-mode -description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations. Use when user requests party mode.' ---- - -# Party Mode Workflow - -**Goal:** Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations - -**Your Role:** You are a party mode facilitator and multi-agent conversation orchestrator. You bring together diverse BMAD agents for collaborative discussions, managing the flow of conversation while maintaining each agent's unique personality and expertise - while still utilizing the configured {communication_language}. - ---- - -## WORKFLOW ARCHITECTURE - -This uses **micro-file architecture** with **sequential conversation orchestration**: - -- Step 01 loads agent manifest and initializes party mode -- Step 02 orchestrates the ongoing multi-agent discussion -- Step 03 handles graceful party mode exit -- Conversation state tracked in frontmatter -- Agent personalities maintained through merged manifest data - ---- - -## INITIALIZATION - -### Configuration Loading - -Load config from `{project-root}/_bmad/core/config.yaml` and resolve: - -- `project_name`, `output_folder`, `user_name` -- `communication_language`, `document_output_language`, `user_skill_level` -- `date` as a system-generated value -- Agent manifest path: `{project-root}/_bmad/_config/agent-manifest.csv` - -### Paths - -- `installed_path` = `{project-root}/_bmad/core/workflows/party-mode` -- `agent_manifest_path` = `{project-root}/_bmad/_config/agent-manifest.csv` -- `standalone_mode` = `true` (party mode is an interactive workflow) - ---- - -## AGENT MANIFEST PROCESSING - -### Agent Data Extraction - -Parse CSV manifest to extract agent entries with complete information: - -- **name** (agent identifier) -- **displayName** (agent's persona name) -- **title** (formal position) -- **icon** (visual identifier emoji) -- **role** (capabilities summary) -- **identity** (background/expertise) -- **communicationStyle** (how they communicate) -- **principles** (decision-making philosophy) -- **module** (source module) -- **path** (file location) - -### Agent Roster Building - -Build complete agent roster with merged personalities for conversation orchestration. - ---- - -## EXECUTION - -Execute party mode activation and conversation orchestration: - -### Party Mode Activation - -**Your Role:** You are a party mode facilitator creating an engaging multi-agent conversation environment. - -**Welcome Activation:** - -"🎉 PARTY MODE ACTIVATED! 🎉 - -Welcome {{user_name}}! All BMAD agents are here and ready for a dynamic group discussion. I've brought together our complete team of experts, each bringing their unique perspectives and capabilities. - -**Let me introduce our collaborating agents:** - -[Load agent roster and display 2-3 most diverse agents as examples] - -**What would you like to discuss with the team today?**" - -### Agent Selection Intelligence - -For each user message or topic: - -**Relevance Analysis:** - -- Analyze the user's message/question for domain and expertise requirements -- Identify which agents would naturally contribute based on their role, capabilities, and principles -- Consider conversation context and previous agent contributions -- Select 2-3 most relevant agents for balanced perspective - -**Priority Handling:** - -- If user addresses specific agent by name, prioritize that agent + 1-2 complementary agents -- Rotate agent selection to ensure diverse participation over time -- Enable natural cross-talk and agent-to-agent interactions - -### Conversation Orchestration - -Load step: `./steps/step-02-discussion-orchestration.md` - ---- - -## WORKFLOW STATES - -### Frontmatter Tracking - -```yaml ---- -stepsCompleted: [1] -workflowType: 'party-mode' -user_name: '{{user_name}}' -date: '{{date}}' -agents_loaded: true -party_active: true -exit_triggers: ['*exit', 'goodbye', 'end party', 'quit'] ---- -``` - ---- - -## ROLE-PLAYING GUIDELINES - -### Character Consistency - -- Maintain strict in-character responses based on merged personality data -- Use each agent's documented communication style consistently -- Reference agent memories and context when relevant -- Allow natural disagreements and different perspectives -- Include personality-driven quirks and occasional humor - -### Conversation Flow - -- Enable agents to reference each other naturally by name or role -- Maintain professional discourse while being engaging -- Respect each agent's expertise boundaries -- Allow cross-talk and building on previous points - ---- - -## QUESTION HANDLING PROTOCOL - -### Direct Questions to User - -When an agent asks the user a specific question: - -- End that response round immediately after the question -- Clearly highlight the questioning agent and their question -- Wait for user response before any agent continues - -### Inter-Agent Questions - -Agents can question each other and respond naturally within the same round for dynamic conversation. - ---- - -## EXIT CONDITIONS - -### Automatic Triggers - -Exit party mode when user message contains any exit triggers: - -- `*exit`, `goodbye`, `end party`, `quit` - -### Graceful Conclusion - -If conversation naturally concludes: - -- Ask user if they'd like to continue or end party mode -- Exit gracefully when user indicates completion - ---- - -## MODERATION NOTES - -**Quality Control:** - -- If discussion becomes circular, have bmad-master summarize and redirect -- Balance fun and productivity based on conversation tone -- Ensure all agents stay true to their merged personalities -- Exit gracefully when user indicates completion - -**Conversation Management:** - -- Rotate agent participation to ensure inclusive discussion -- Handle topic drift while maintaining productive conversation -- Facilitate cross-agent collaboration and knowledge sharing diff --git a/src/utility/agent-components/activation-rules.txt b/src/utility/agent-components/activation-rules.txt deleted file mode 100644 index a67ae4993..000000000 --- a/src/utility/agent-components/activation-rules.txt +++ /dev/null @@ -1,6 +0,0 @@ - - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style. - Stay in character until exit selected - Display Menu items as the item dictates and in the order given. - Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml - \ No newline at end of file diff --git a/src/utility/agent-components/activation-steps.txt b/src/utility/agent-components/activation-steps.txt deleted file mode 100644 index 9ead0e01c..000000000 --- a/src/utility/agent-components/activation-steps.txt +++ /dev/null @@ -1,14 +0,0 @@ - Load persona from this current agent file (already in context) - 🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT: - - Load and read {project-root}/_bmad/{{module}}/config.yaml NOW - - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder} - - VERIFY: If config not loaded, STOP and report error to user - - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored - - Remember: user's name is {user_name} - {AGENT_SPECIFIC_STEPS} - Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section - Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with `/bmad-help where should I start with an idea I have that does XYZ` - STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match - On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized" - When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions \ No newline at end of file diff --git a/src/utility/agent-components/agent-command-header.md b/src/utility/agent-components/agent-command-header.md deleted file mode 100644 index d4f9b5d6a..000000000 --- a/src/utility/agent-components/agent-command-header.md +++ /dev/null @@ -1 +0,0 @@ -You must fully embody this agent's persona and follow all activation instructions, steps and rules exactly as specified. NEVER break character until given an exit command. diff --git a/src/utility/agent-components/agent.customize.template.yaml b/src/utility/agent-components/agent.customize.template.yaml deleted file mode 100644 index b8cc648b4..000000000 --- a/src/utility/agent-components/agent.customize.template.yaml +++ /dev/null @@ -1,41 +0,0 @@ -# Agent Customization -# Customize any section below - all are optional - -# Override agent name -agent: - metadata: - name: "" - -# Replace entire persona (not merged) -persona: - role: "" - identity: "" - communication_style: "" - principles: [] - -# Add custom critical actions (appended after standard config loading) -critical_actions: [] - -# Add persistent memories for the agent -memories: [] -# Example: -# memories: -# - "User prefers detailed technical explanations" -# - "Current project uses React and TypeScript" - -# Add custom menu items (appended to base menu) -# Don't include * prefix or help/exit - auto-injected -menu: [] -# Example: -# menu: -# - trigger: my-workflow -# workflow: "{project-root}/custom/my.yaml" -# description: My custom workflow - -# Add custom prompts (for action="#id" handlers) -prompts: [] -# Example: -# prompts: -# - id: my-prompt -# content: | -# Prompt instructions here diff --git a/src/utility/agent-components/handler-action.txt b/src/utility/agent-components/handler-action.txt deleted file mode 100644 index db31f4852..000000000 --- a/src/utility/agent-components/handler-action.txt +++ /dev/null @@ -1,4 +0,0 @@ - - When menu item has: action="#id" → Find prompt with id="id" in current agent XML, follow its content - When menu item has: action="text" → Follow the text directly as an inline instruction - \ No newline at end of file diff --git a/src/utility/agent-components/handler-data.txt b/src/utility/agent-components/handler-data.txt deleted file mode 100644 index 14036fa58..000000000 --- a/src/utility/agent-components/handler-data.txt +++ /dev/null @@ -1,5 +0,0 @@ - - When menu item has: data="path/to/file.json|yaml|yml|csv|xml" - Load the file first, parse according to extension - Make available as {data} variable to subsequent handler operations - diff --git a/src/utility/agent-components/handler-exec.txt b/src/utility/agent-components/handler-exec.txt deleted file mode 100644 index 1c8459a64..000000000 --- a/src/utility/agent-components/handler-exec.txt +++ /dev/null @@ -1,6 +0,0 @@ - - When menu item or handler has: exec="path/to/file.md": - 1. Read fully and follow the file at that path - 2. Process the complete file and follow all instructions within it - 3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context. - \ No newline at end of file diff --git a/src/utility/agent-components/handler-multi.txt b/src/utility/agent-components/handler-multi.txt deleted file mode 100644 index f33a73fe5..000000000 --- a/src/utility/agent-components/handler-multi.txt +++ /dev/null @@ -1,14 +0,0 @@ - - When menu item has: type="multi" with nested handlers - 1. Display the multi item text as a single menu option - 2. Parse all nested handlers within the multi item - 3. For each nested handler: - - Use the 'match' attribute for fuzzy matching user input (or Exact Match of character code in brackets []) - - Process based on handler attributes (exec, workflow, action) - 4. When user input matches a handler's 'match' pattern: - - For exec="path/to/file.md": follow the `handler type="exec"` instructions - - For workflow="path/to/workflow.yaml": follow the `handler type="workflow"` instructions - - For action="...": Perform the specified action directly - 5. Support both exact matches and fuzzy matching based on the match attribute - 6. If no handler matches, prompt user to choose from available options - \ No newline at end of file diff --git a/src/utility/agent-components/handler-tmpl.txt b/src/utility/agent-components/handler-tmpl.txt deleted file mode 100644 index a190504b7..000000000 --- a/src/utility/agent-components/handler-tmpl.txt +++ /dev/null @@ -1,5 +0,0 @@ - - 1. When menu item has: tmpl="path/to/template.md" - 2. Load template file, parse as markdown with {{mustache}} style variables - 3. Make template content available as {template} to action/exec/workflow handlers - \ No newline at end of file diff --git a/src/utility/agent-components/handler-validate-workflow.txt b/src/utility/agent-components/handler-validate-workflow.txt deleted file mode 100644 index aca040550..000000000 --- a/src/utility/agent-components/handler-validate-workflow.txt +++ /dev/null @@ -1,7 +0,0 @@ - - When command has: validate-workflow="path/to/workflow.yaml" - 1. You MUST LOAD the file at: {project-root}/_bmad/core/tasks/validate-workflow.xml - 2. READ its entire contents and EXECUTE all instructions in that file - 3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist - 4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify - \ No newline at end of file diff --git a/src/utility/agent-components/handler-workflow.txt b/src/utility/agent-components/handler-workflow.txt deleted file mode 100644 index 1be1dcbe5..000000000 --- a/src/utility/agent-components/handler-workflow.txt +++ /dev/null @@ -1,10 +0,0 @@ - - When menu item has: workflow="path/to/workflow.yaml": - - 1. CRITICAL: Always LOAD {project-root}/_bmad/core/tasks/workflow.xml - 2. Read the complete file - this is the CORE OS for processing BMAD workflows - 3. Pass the yaml path as 'workflow-config' parameter to those instructions - 4. Follow workflow.xml instructions precisely following all steps - 5. Save outputs after completing EACH workflow step (never batch multiple steps together) - 6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet - \ No newline at end of file diff --git a/src/utility/agent-components/menu-handlers.txt b/src/utility/agent-components/menu-handlers.txt deleted file mode 100644 index 3dd1ae9c7..000000000 --- a/src/utility/agent-components/menu-handlers.txt +++ /dev/null @@ -1,6 +0,0 @@ - - {DYNAMIC_EXTRACT_LIST} - - {DYNAMIC_HANDLERS} - - diff --git a/test/README.md b/test/README.md deleted file mode 100644 index bc8ac48fc..000000000 --- a/test/README.md +++ /dev/null @@ -1,295 +0,0 @@ -# Agent Schema Validation Test Suite - -Comprehensive test coverage for the BMAD agent schema validation system. - -## Overview - -This test suite validates the Zod-based schema validator (`tools/schema/agent.js`) that ensures all `*.agent.yaml` files conform to the BMAD agent specification. - -## Test Statistics - -- **Total Test Fixtures**: 50 -- **Valid Test Cases**: 18 -- **Invalid Test Cases**: 32 -- **Code Coverage**: 100% all metrics (statements, branches, functions, lines) -- **Exit Code Tests**: 4 CLI integration tests - -## Quick Start - -```bash -# Run all tests -npm test - -# Run with coverage report -npm run test:coverage - -# Run CLI integration tests -./test/test-cli-integration.sh - -# Validate actual agent files -npm run validate:schemas -``` - -## Test Organization - -### Test Fixtures - -Located in `test/fixtures/agent-schema/`, organized by category: - -``` -test/fixtures/agent-schema/ -├── valid/ # 15 fixtures that should pass -│ ├── top-level/ # Basic structure tests -│ ├── metadata/ # Metadata field tests -│ ├── persona/ # Persona field tests -│ ├── critical-actions/ # Critical actions tests -│ ├── menu/ # Menu structure tests -│ ├── menu-commands/ # Command target tests -│ ├── menu-triggers/ # Trigger format tests -│ └── prompts/ # Prompts field tests -└── invalid/ # 32 fixtures that should fail - ├── top-level/ # Structure errors - ├── metadata/ # Metadata validation errors - ├── persona/ # Persona validation errors - ├── critical-actions/ # Critical actions errors - ├── menu/ # Menu errors - ├── menu-commands/ # Command target errors - ├── menu-triggers/ # Trigger format errors - ├── prompts/ # Prompts errors - └── yaml-errors/ # YAML parsing errors -``` - -## Test Categories - -### 1. Top-Level Structure Tests (4 fixtures) - -Tests the root-level agent structure: - -- ✅ Valid: Minimal core agent with required fields -- ❌ Invalid: Empty YAML file -- ❌ Invalid: Missing `agent` key -- ❌ Invalid: Extra top-level keys (strict mode) - -### 2. Metadata Field Tests (7 fixtures) - -Tests agent metadata validation: - -- ✅ Valid: Module agent with correct `module` field -- ❌ Invalid: Missing required fields (`id`, `name`, `title`, `icon`) -- ❌ Invalid: Empty strings in metadata -- ❌ Invalid: Module agent missing `module` field -- ❌ Invalid: Core agent with unexpected `module` field -- ❌ Invalid: Wrong `module` value (doesn't match path) -- ❌ Invalid: Extra unknown metadata fields - -### 3. Persona Field Tests (6 fixtures) - -Tests persona structure and validation: - -- ✅ Valid: Complete persona with all fields -- ❌ Invalid: Missing required fields (`role`, `identity`, etc.) -- ❌ Invalid: `principles` as string instead of array -- ❌ Invalid: Empty `principles` array -- ❌ Invalid: Empty strings in `principles` array -- ❌ Invalid: Extra unknown persona fields - -### 4. Critical Actions Tests (5 fixtures) - -Tests optional `critical_actions` field: - -- ✅ Valid: No `critical_actions` field (optional) -- ✅ Valid: Empty `critical_actions` array -- ✅ Valid: Valid action strings -- ❌ Invalid: Empty strings in actions -- ❌ Invalid: Actions as non-array type - -### 5. Menu Field Tests (4 fixtures) - -Tests required menu structure: - -- ✅ Valid: Single menu item -- ✅ Valid: Multiple menu items with different commands -- ❌ Invalid: Missing `menu` field -- ❌ Invalid: Empty `menu` array - -### 6. Menu Command Target Tests (4 fixtures) - -Tests menu item command targets: - -- ✅ Valid: All 6 command types (`workflow`, `validate-workflow`, `exec`, `action`, `tmpl`, `data`) -- ✅ Valid: Multiple command targets in one menu item -- ❌ Invalid: No command target fields -- ❌ Invalid: Empty string command targets - -### 7. Menu Trigger Validation Tests (7 fixtures) - -Tests trigger format enforcement: - -- ✅ Valid: Kebab-case triggers (`help`, `list-tasks`, `multi-word-trigger`) -- ❌ Invalid: Leading asterisk (`*help`) -- ❌ Invalid: CamelCase (`listTasks`) -- ❌ Invalid: Snake_case (`list_tasks`) -- ❌ Invalid: Spaces (`list tasks`) -- ❌ Invalid: Duplicate triggers within agent -- ❌ Invalid: Empty trigger string - -### 8. Prompts Field Tests (8 fixtures) - -Tests optional `prompts` field: - -- ✅ Valid: No `prompts` field (optional) -- ✅ Valid: Empty `prompts` array -- ✅ Valid: Prompts with required `id` and `content` -- ✅ Valid: Prompts with optional `description` -- ❌ Invalid: Missing `id` -- ❌ Invalid: Missing `content` -- ❌ Invalid: Empty `content` string -- ❌ Invalid: Extra unknown prompt fields - -### 9. YAML Parsing Tests (2 fixtures) - -Tests YAML parsing error handling: - -- ❌ Invalid: Malformed YAML syntax -- ❌ Invalid: Invalid indentation - -## Test Scripts - -### Main Test Runner - -**File**: `test/test-agent-schema.js` - -Automated test runner that: - -- Loads all fixtures from `test/fixtures/agent-schema/` -- Validates each against the schema -- Compares results with expected outcomes (parsed from YAML comments) -- Reports detailed results by category -- Exits with code 0 (pass) or 1 (fail) - -**Usage**: - -```bash -npm test -# or -node test/test-agent-schema.js -``` - -### Coverage Report - -**Command**: `npm run test:coverage` - -Generates code coverage report using c8: - -- Text output to console -- HTML report in `coverage/` directory -- Tracks statement, branch, function, and line coverage - -**Current Coverage**: - -- Statements: 100% -- Branches: 100% -- Functions: 100% -- Lines: 100% - -### CLI Integration Tests - -**File**: `test/test-cli-integration.sh` - -Bash script that tests CLI behavior: - -1. Validates existing agent files -2. Verifies test fixture validation -3. Checks exit code 0 for valid files -4. Verifies test runner output format - -**Usage**: - -```bash -./test/test-cli-integration.sh -``` - -## Manual Testing - -See **[MANUAL-TESTING.md](./MANUAL-TESTING.md)** for detailed manual testing procedures, including: - -- Testing with invalid files -- GitHub Actions workflow verification -- Troubleshooting guide -- PR merge blocking tests - -## Coverage Achievement - -**100% code coverage achieved!** All branches, statements, functions, and lines in the validation logic are tested. - -Edge cases covered include: - -- Malformed module paths (e.g., `src/bmm` without `/agents/`) -- Empty module names in paths (e.g., `src/modules//agents/`) -- Whitespace-only module field values -- All validation error paths -- All success paths for valid configurations - -## Adding New Tests - -To add new test cases: - -1. Create a new `.agent.yaml` file in the appropriate `valid/` or `invalid/` subdirectory -2. Add comment metadata at the top: - - ```yaml - # Test: Description of what this tests - # Expected: PASS (or FAIL - error description) - # Path context: src/bmm/agents/test.agent.yaml (if needed) - ``` - -3. Run the test suite to verify: `npm test` - -## Integration with CI/CD - -The validation is integrated into the GitHub Actions workflow: - -**File**: `.github/workflows/lint.yaml` - -**Job**: `agent-schema` - -**Runs on**: All pull requests - -**Blocks merge if**: Validation fails - -## Files - -- `test/test-agent-schema.js` - Main test runner -- `test/test-cli-integration.sh` - CLI integration tests -- `test/MANUAL-TESTING.md` - Manual testing guide -- `test/fixtures/agent-schema/` - Test fixtures (47 files) -- `tools/schema/agent.js` - Validation logic (under test) -- `tools/validate-agent-schema.js` - CLI wrapper - -## Dependencies - -- **zod**: Schema validation library -- **yaml**: YAML parsing -- **glob**: File pattern matching -- **c8**: Code coverage reporting - -## Success Criteria - -All success criteria from the original task have been exceeded: - -- ✅ 50 test fixtures covering all validation rules (target: 47+) -- ✅ Automated test runner with detailed reporting -- ✅ CLI integration tests verifying exit codes and output -- ✅ Manual testing documentation -- ✅ **100% code coverage achieved** (target: 99%+) -- ✅ Both positive and negative test cases -- ✅ Clear and actionable error messages -- ✅ GitHub Actions integration verified -- ✅ Aggressive defensive assertions implemented - -## Resources - -- **Schema Documentation**: `schema-classification.md` -- **Validator Implementation**: `tools/schema/agent.js` -- **CLI Tool**: `tools/validate-agent-schema.js` -- **Project Guidelines**: `CLAUDE.md` diff --git a/test/adversarial-review-tests/README.md b/test/adversarial-review-tests/README.md deleted file mode 100644 index 8d2af5079..000000000 --- a/test/adversarial-review-tests/README.md +++ /dev/null @@ -1,56 +0,0 @@ -# Adversarial Review Test Suite - -Tests for the `also_consider` optional input in `review-adversarial-general.xml`. - -## Purpose - -Evaluate whether the `also_consider` input gently nudges the reviewer toward specific areas without overriding normal adversarial analysis. - -## Test Content - -All tests use `sample-content.md` - a deliberately imperfect User Authentication API doc with: - -- Vague error handling section -- Missing rate limit details -- No token expiration info -- Password in plain text example -- Missing authentication headers -- No error response examples - -## Running Tests - -For each test case in `test-cases.yaml`, invoke the adversarial review task. - -### Manual Test Invocation - -``` -Review this content using the adversarial review task: - - -[paste sample-content.md] - - - -[paste items from test case, or omit for TC01] - -``` - -## Evaluation Criteria - -For each test, note: - -1. **Total findings** - Still hitting ~10 issues? -2. **Distribution** - Are findings spread across concerns or clustered? -3. **Relevance** - Do findings relate to `also_consider` items when provided? -4. **Balance** - Are `also_consider` findings elevated over others, or naturally mixed? -5. **Quality** - Are findings actionable regardless of source? - -## Expected Outcomes - -- **TC01 (baseline)**: Generic spread of findings -- **TC02-TC05 (domain-focused)**: Some findings align with domain, others still organic -- **TC06 (single item)**: Light influence, not dominant -- **TC07 (vague items)**: Minimal change from baseline -- **TC08 (specific items)**: Direct answers if gaps exist -- **TC09 (mixed)**: Balanced across domains -- **TC10 (contradictory)**: Graceful handling diff --git a/test/adversarial-review-tests/sample-content.md b/test/adversarial-review-tests/sample-content.md deleted file mode 100644 index a821096d4..000000000 --- a/test/adversarial-review-tests/sample-content.md +++ /dev/null @@ -1,46 +0,0 @@ -# User Authentication API - -## Overview - -This API provides endpoints for user authentication and session management. - -## Endpoints - -### POST /api/auth/login - -Authenticates a user and returns a token. - -**Request Body:** -```json -{ - "email": "user@example.com", - "password": "password123" -} -``` - -**Response:** -```json -{ - "token": "eyJhbGciOiJIUzI1NiIs...", - "user": { - "id": 1, - "email": "user@example.com" - } -} -``` - -### POST /api/auth/logout - -Logs out the current user. - -### GET /api/auth/me - -Returns the current user's profile. - -## Error Handling - -Errors return appropriate HTTP status codes. - -## Rate Limiting - -Rate limiting is applied to prevent abuse. diff --git a/test/adversarial-review-tests/test-cases.yaml b/test/adversarial-review-tests/test-cases.yaml deleted file mode 100644 index 7f20e84ff..000000000 --- a/test/adversarial-review-tests/test-cases.yaml +++ /dev/null @@ -1,103 +0,0 @@ -# Test Cases for review-adversarial-general.xml with also_consider input -# -# Purpose: Evaluate how the optional also_consider input influences review findings -# Content: All tests use sample-content.md (User Authentication API docs) -# -# To run: Manually invoke the task with each configuration and compare outputs - -test_cases: - # BASELINE - No also_consider - - id: TC01 - name: "Baseline - no also_consider" - description: "Control test with no also_consider input" - also_consider: null - expected_behavior: "Generic adversarial findings across all aspects" - - # DOCUMENTATION-FOCUSED - - id: TC02 - name: "Documentation - reader confusion" - description: "Nudge toward documentation UX issues" - also_consider: - - What would confuse a first-time reader? - - What questions are left unanswered? - - What could be interpreted multiple ways? - - What jargon is unexplained? - expected_behavior: "More findings about clarity, completeness, reader experience" - - - id: TC03 - name: "Documentation - examples and usage" - description: "Nudge toward practical usage gaps" - also_consider: - - Missing code examples - - Unclear usage patterns - - Edge cases not documented - expected_behavior: "More findings about practical application gaps" - - # SECURITY-FOCUSED - - id: TC04 - name: "Security review" - description: "Nudge toward security concerns" - also_consider: - - Authentication vulnerabilities - - Token handling issues - - Input validation gaps - - Information disclosure risks - expected_behavior: "More security-related findings" - - # API DESIGN-FOCUSED - - id: TC05 - name: "API design" - description: "Nudge toward API design best practices" - also_consider: - - REST conventions not followed - - Inconsistent response formats - - Missing pagination or filtering - - Versioning concerns - expected_behavior: "More API design pattern findings" - - # SINGLE ITEM - - id: TC06 - name: "Single item - error handling" - description: "Test with just one also_consider item" - also_consider: - - Error handling completeness - expected_behavior: "Some emphasis on error handling while still covering other areas" - - # BROAD/VAGUE - - id: TC07 - name: "Broad items" - description: "Test with vague also_consider items" - also_consider: - - Quality issues - - Things that seem off - expected_behavior: "Minimal change from baseline - items too vague to steer" - - # VERY SPECIFIC - - id: TC08 - name: "Very specific items" - description: "Test with highly specific also_consider items" - also_consider: - - Is the JWT token expiration documented? - - Are refresh token mechanics explained? - - What happens on concurrent sessions? - expected_behavior: "Specific findings addressing these exact questions if gaps exist" - - # MIXED DOMAINS - - id: TC09 - name: "Mixed domain concerns" - description: "Test with items from different domains" - also_consider: - - Security vulnerabilities - - Reader confusion points - - API design inconsistencies - - Performance implications - expected_behavior: "Balanced findings across multiple domains" - - # CONTRADICTORY/UNUSUAL - - id: TC10 - name: "Contradictory items" - description: "Test resilience with odd inputs" - also_consider: - - Things that are too detailed - - Things that are not detailed enough - expected_behavior: "Reviewer handles gracefully, finds issues in both directions" diff --git a/test/fixtures/agent-schema/invalid/critical-actions/actions-as-string.agent.yaml b/test/fixtures/agent-schema/invalid/critical-actions/actions-as-string.agent.yaml deleted file mode 100644 index 46396e0f4..000000000 --- a/test/fixtures/agent-schema/invalid/critical-actions/actions-as-string.agent.yaml +++ /dev/null @@ -1,27 +0,0 @@ -# Test: critical_actions as non-array -# Expected: FAIL -# Error code: invalid_type -# Error path: agent.critical_actions -# Error expected: array - -agent: - metadata: - id: actions-string - name: Actions String - title: Actions String - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - critical_actions: This should be an array - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/critical-actions/empty-string-in-actions.agent.yaml b/test/fixtures/agent-schema/invalid/critical-actions/empty-string-in-actions.agent.yaml deleted file mode 100644 index 3a87232c2..000000000 --- a/test/fixtures/agent-schema/invalid/critical-actions/empty-string-in-actions.agent.yaml +++ /dev/null @@ -1,30 +0,0 @@ -# Test: critical_actions with empty strings -# Expected: FAIL -# Error code: custom -# Error path: agent.critical_actions[1] -# Error message: agent.critical_actions[] must be a non-empty string - -agent: - metadata: - id: empty-action-string - name: Empty Action String - title: Empty Action String - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - critical_actions: - - Valid action - - " " - - Another valid action - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/menu-commands/empty-command-target.agent.yaml b/test/fixtures/agent-schema/invalid/menu-commands/empty-command-target.agent.yaml deleted file mode 100644 index 0194c4026..000000000 --- a/test/fixtures/agent-schema/invalid/menu-commands/empty-command-target.agent.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# Test: Menu item with empty string command target -# Expected: FAIL -# Error code: custom -# Error path: agent.menu[0].action -# Error message: agent.menu[].action must be a non-empty string - -agent: - metadata: - id: empty-command - name: Empty Command Target - title: Empty Command - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: Show help - action: " " diff --git a/test/fixtures/agent-schema/invalid/menu-commands/no-command-target.agent.yaml b/test/fixtures/agent-schema/invalid/menu-commands/no-command-target.agent.yaml deleted file mode 100644 index 888e2d36b..000000000 --- a/test/fixtures/agent-schema/invalid/menu-commands/no-command-target.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Menu item with no command target fields -# Expected: FAIL -# Error code: custom -# Error path: agent.menu[0] -# Error message: agent.menu[] entries must include at least one command target field - -agent: - metadata: - id: no-command - name: No Command Target - title: No Command - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: Show help but no command target diff --git a/test/fixtures/agent-schema/invalid/menu-triggers/camel-case.agent.yaml b/test/fixtures/agent-schema/invalid/menu-triggers/camel-case.agent.yaml deleted file mode 100644 index 62fbb3136..000000000 --- a/test/fixtures/agent-schema/invalid/menu-triggers/camel-case.agent.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# Test: CamelCase trigger -# Expected: FAIL -# Error code: custom -# Error path: agent.menu[0].trigger -# Error message: agent.menu[].trigger must be kebab-case (lowercase words separated by hyphen) - -agent: - metadata: - id: camel-case-trigger - name: CamelCase Trigger - title: CamelCase - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: listTasks - description: Invalid CamelCase trigger - action: list_tasks diff --git a/test/fixtures/agent-schema/invalid/menu-triggers/compound-invalid-format.agent.yaml b/test/fixtures/agent-schema/invalid/menu-triggers/compound-invalid-format.agent.yaml deleted file mode 100644 index 07a550f46..000000000 --- a/test/fixtures/agent-schema/invalid/menu-triggers/compound-invalid-format.agent.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# Test: Compound trigger with invalid format -# Expected: FAIL -# Error code: custom -# Error path: agent.menu[0].trigger -# Error message: agent.menu[].trigger compound format error: invalid compound trigger format - -agent: - metadata: - id: compound-invalid-format - name: Invalid Format - title: Invalid Format Test - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: TS or tech-spec - description: Missing fuzzy match clause - action: test diff --git a/test/fixtures/agent-schema/invalid/menu-triggers/compound-mismatched-kebab.agent.yaml b/test/fixtures/agent-schema/invalid/menu-triggers/compound-mismatched-kebab.agent.yaml deleted file mode 100644 index 46febb326..000000000 --- a/test/fixtures/agent-schema/invalid/menu-triggers/compound-mismatched-kebab.agent.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# Test: Compound trigger with old format (no longer supported) -# Expected: FAIL -# Error code: custom -# Error path: agent.menu[0].trigger -# Error message: agent.menu[].trigger compound format error: invalid compound trigger format - -agent: - metadata: - id: compound-mismatched-kebab - name: Old Format - title: Old Format Test - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: TS or tech-spec or fuzzy match on tech-spec - description: Old format with middle kebab-case (no longer supported) - action: test diff --git a/test/fixtures/agent-schema/invalid/menu-triggers/duplicate-triggers.agent.yaml b/test/fixtures/agent-schema/invalid/menu-triggers/duplicate-triggers.agent.yaml deleted file mode 100644 index 8b5cf7c8c..000000000 --- a/test/fixtures/agent-schema/invalid/menu-triggers/duplicate-triggers.agent.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Test: Duplicate triggers within same agent -# Expected: FAIL -# Error code: custom -# Error path: agent.menu[2].trigger -# Error message: agent.menu[].trigger duplicates "help" within the same agent - -agent: - metadata: - id: duplicate-triggers - name: Duplicate Triggers - title: Duplicate - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: First help command - action: display_help - - trigger: list-tasks - description: List tasks - action: list_tasks - - trigger: help - description: Duplicate help command - action: show_help diff --git a/test/fixtures/agent-schema/invalid/menu-triggers/empty-trigger.agent.yaml b/test/fixtures/agent-schema/invalid/menu-triggers/empty-trigger.agent.yaml deleted file mode 100644 index c6d9fbfa9..000000000 --- a/test/fixtures/agent-schema/invalid/menu-triggers/empty-trigger.agent.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# Test: Empty trigger string -# Expected: FAIL -# Error code: custom -# Error path: agent.menu[0].trigger -# Error message: agent.menu[].trigger must be a non-empty string - -agent: - metadata: - id: empty-trigger - name: Empty Trigger - title: Empty - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: " " - description: Empty trigger - action: display_help diff --git a/test/fixtures/agent-schema/invalid/menu-triggers/leading-asterisk.agent.yaml b/test/fixtures/agent-schema/invalid/menu-triggers/leading-asterisk.agent.yaml deleted file mode 100644 index 5e9585960..000000000 --- a/test/fixtures/agent-schema/invalid/menu-triggers/leading-asterisk.agent.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# Test: Trigger with leading asterisk -# Expected: FAIL -# Error code: custom -# Error path: agent.menu[0].trigger -# Error message: agent.menu[].trigger must be kebab-case (lowercase words separated by hyphen) - -agent: - metadata: - id: asterisk-trigger - name: Asterisk Trigger - title: Asterisk - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: "*help" - description: Invalid trigger with asterisk - action: display_help diff --git a/test/fixtures/agent-schema/invalid/menu-triggers/snake-case.agent.yaml b/test/fixtures/agent-schema/invalid/menu-triggers/snake-case.agent.yaml deleted file mode 100644 index 7dc177935..000000000 --- a/test/fixtures/agent-schema/invalid/menu-triggers/snake-case.agent.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# Test: Snake_case trigger -# Expected: FAIL -# Error code: custom -# Error path: agent.menu[0].trigger -# Error message: agent.menu[].trigger must be kebab-case (lowercase words separated by hyphen) - -agent: - metadata: - id: snake-case-trigger - name: Snake Case Trigger - title: Snake Case - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: list_tasks - description: Invalid snake_case trigger - action: list_tasks diff --git a/test/fixtures/agent-schema/invalid/menu-triggers/trigger-with-spaces.agent.yaml b/test/fixtures/agent-schema/invalid/menu-triggers/trigger-with-spaces.agent.yaml deleted file mode 100644 index b64a406d8..000000000 --- a/test/fixtures/agent-schema/invalid/menu-triggers/trigger-with-spaces.agent.yaml +++ /dev/null @@ -1,25 +0,0 @@ -# Test: Trigger with spaces -# Expected: FAIL -# Error code: custom -# Error path: agent.menu[0].trigger -# Error message: agent.menu[].trigger must be kebab-case (lowercase words separated by hyphen) - -agent: - metadata: - id: spaces-trigger - name: Spaces Trigger - title: Spaces - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: list tasks - description: Invalid trigger with spaces - action: list_tasks diff --git a/test/fixtures/agent-schema/invalid/menu/empty-menu.agent.yaml b/test/fixtures/agent-schema/invalid/menu/empty-menu.agent.yaml deleted file mode 100644 index b5be54ef7..000000000 --- a/test/fixtures/agent-schema/invalid/menu/empty-menu.agent.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# Test: Empty menu array -# Expected: FAIL -# Error code: too_small -# Error path: agent.menu -# Error minimum: 1 - -agent: - metadata: - id: empty-menu - name: Empty Menu - title: Empty Menu - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: [] diff --git a/test/fixtures/agent-schema/invalid/menu/missing-menu.agent.yaml b/test/fixtures/agent-schema/invalid/menu/missing-menu.agent.yaml deleted file mode 100644 index 55e7789a6..000000000 --- a/test/fixtures/agent-schema/invalid/menu/missing-menu.agent.yaml +++ /dev/null @@ -1,20 +0,0 @@ -# Test: Missing menu field -# Expected: FAIL -# Error code: invalid_type -# Error path: agent.menu -# Error expected: array - -agent: - metadata: - id: missing-menu - name: Missing Menu - title: Missing Menu - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle diff --git a/test/fixtures/agent-schema/invalid/metadata/empty-module-string.agent.yaml b/test/fixtures/agent-schema/invalid/metadata/empty-module-string.agent.yaml deleted file mode 100644 index bb68d2de0..000000000 --- a/test/fixtures/agent-schema/invalid/metadata/empty-module-string.agent.yaml +++ /dev/null @@ -1,26 +0,0 @@ -# Test: Module field with whitespace only -# Expected: FAIL -# Error code: custom -# Error path: agent.metadata.module -# Error message: agent.metadata.module must be a non-empty string -# Path context: src/bmm/agents/empty-module-string.agent.yaml - -agent: - metadata: - id: empty-module - name: Empty Module String - title: Empty Module - icon: ❌ - module: " " - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/metadata/empty-name.agent.yaml b/test/fixtures/agent-schema/invalid/metadata/empty-name.agent.yaml deleted file mode 100644 index d5dbfdd09..000000000 --- a/test/fixtures/agent-schema/invalid/metadata/empty-name.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Empty string in metadata.name field -# Expected: FAIL -# Error code: custom -# Error path: agent.metadata.name -# Error message: agent.metadata.name must be a non-empty string - -agent: - metadata: - id: empty-name-test - name: " " - title: Empty Name Test - icon: ❌ - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/metadata/extra-metadata-fields.agent.yaml b/test/fixtures/agent-schema/invalid/metadata/extra-metadata-fields.agent.yaml deleted file mode 100644 index 10f283d51..000000000 --- a/test/fixtures/agent-schema/invalid/metadata/extra-metadata-fields.agent.yaml +++ /dev/null @@ -1,27 +0,0 @@ -# Test: Extra unknown fields in metadata -# Expected: FAIL -# Error code: unrecognized_keys -# Error path: agent.metadata -# Error keys: ["unknown_field", "another_extra"] - -agent: - metadata: - id: extra-fields - name: Extra Fields - title: Extra Fields - icon: ❌ - hasSidecar: false - unknown_field: This is not allowed - another_extra: Also invalid - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/metadata/missing-id.agent.yaml b/test/fixtures/agent-schema/invalid/metadata/missing-id.agent.yaml deleted file mode 100644 index 0b24082af..000000000 --- a/test/fixtures/agent-schema/invalid/metadata/missing-id.agent.yaml +++ /dev/null @@ -1,23 +0,0 @@ -# Test: Missing required metadata.id field -# Expected: FAIL -# Error code: invalid_type -# Error path: agent.metadata.id -# Error expected: string - -agent: - metadata: - name: Missing ID Agent - title: Missing ID - icon: ❌ - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/persona/empty-principles-array.agent.yaml b/test/fixtures/agent-schema/invalid/persona/empty-principles-array.agent.yaml deleted file mode 100644 index 4033e6908..000000000 --- a/test/fixtures/agent-schema/invalid/persona/empty-principles-array.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Empty principles array -# Expected: FAIL -# Error code: too_small -# Error path: agent.persona.principles -# Error minimum: 1 - -agent: - metadata: - id: empty-principles - name: Empty Principles - title: Empty Principles - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: [] - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/persona/empty-string-in-principles.agent.yaml b/test/fixtures/agent-schema/invalid/persona/empty-string-in-principles.agent.yaml deleted file mode 100644 index 9bba71bb4..000000000 --- a/test/fixtures/agent-schema/invalid/persona/empty-string-in-principles.agent.yaml +++ /dev/null @@ -1,27 +0,0 @@ -# Test: Empty string in principles array -# Expected: FAIL -# Error code: custom -# Error path: agent.persona.principles[1] -# Error message: agent.persona.principles[] must be a non-empty string - -agent: - metadata: - id: empty-principle-string - name: Empty Principle String - title: Empty Principle - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Valid principle - - " " - - Another valid principle - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/persona/extra-persona-fields.agent.yaml b/test/fixtures/agent-schema/invalid/persona/extra-persona-fields.agent.yaml deleted file mode 100644 index 73365a5e3..000000000 --- a/test/fixtures/agent-schema/invalid/persona/extra-persona-fields.agent.yaml +++ /dev/null @@ -1,27 +0,0 @@ -# Test: Extra unknown fields in persona -# Expected: FAIL -# Error code: unrecognized_keys -# Error path: agent.persona -# Error keys: ["extra_field", "another_extra"] - -agent: - metadata: - id: extra-persona-fields - name: Extra Persona Fields - title: Extra Persona - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - extra_field: Not allowed - another_extra: Also invalid - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/persona/missing-role.agent.yaml b/test/fixtures/agent-schema/invalid/persona/missing-role.agent.yaml deleted file mode 100644 index 3dbd6c457..000000000 --- a/test/fixtures/agent-schema/invalid/persona/missing-role.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Missing required persona.role field -# Expected: FAIL -# Error code: invalid_type -# Error path: agent.persona.role -# Error expected: string - -agent: - metadata: - id: missing-role - name: Missing Role - title: Missing Role - icon: ❌ - hasSidecar: false - - persona: - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/prompts/empty-content.agent.yaml b/test/fixtures/agent-schema/invalid/prompts/empty-content.agent.yaml deleted file mode 100644 index 3248edca3..000000000 --- a/test/fixtures/agent-schema/invalid/prompts/empty-content.agent.yaml +++ /dev/null @@ -1,29 +0,0 @@ -# Test: Prompt with empty content string -# Expected: FAIL -# Error code: custom -# Error path: agent.prompts[0].content -# Error message: agent.prompts[].content must be a non-empty string - -agent: - metadata: - id: empty-content - name: Empty Content - title: Empty Content - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - prompts: - - id: prompt1 - content: " " - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/prompts/extra-prompt-fields.agent.yaml b/test/fixtures/agent-schema/invalid/prompts/extra-prompt-fields.agent.yaml deleted file mode 100644 index aeccee29e..000000000 --- a/test/fixtures/agent-schema/invalid/prompts/extra-prompt-fields.agent.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Test: Extra unknown fields in prompts -# Expected: FAIL -# Error code: unrecognized_keys -# Error path: agent.prompts[0] -# Error keys: ["extra_field"] - -agent: - metadata: - id: extra-prompt-fields - name: Extra Prompt Fields - title: Extra Fields - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - prompts: - - id: prompt1 - content: Valid content - description: Valid description - extra_field: Not allowed - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/prompts/missing-content.agent.yaml b/test/fixtures/agent-schema/invalid/prompts/missing-content.agent.yaml deleted file mode 100644 index 7f31723b7..000000000 --- a/test/fixtures/agent-schema/invalid/prompts/missing-content.agent.yaml +++ /dev/null @@ -1,28 +0,0 @@ -# Test: Prompt missing required content field -# Expected: FAIL -# Error code: invalid_type -# Error path: agent.prompts[0].content -# Error expected: string - -agent: - metadata: - id: prompt-missing-content - name: Prompt Missing Content - title: Missing Content - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - prompts: - - id: prompt1 - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/prompts/missing-id.agent.yaml b/test/fixtures/agent-schema/invalid/prompts/missing-id.agent.yaml deleted file mode 100644 index f05f054a2..000000000 --- a/test/fixtures/agent-schema/invalid/prompts/missing-id.agent.yaml +++ /dev/null @@ -1,28 +0,0 @@ -# Test: Prompt missing required id field -# Expected: FAIL -# Error code: invalid_type -# Error path: agent.prompts[0].id -# Error expected: string - -agent: - metadata: - id: prompt-missing-id - name: Prompt Missing ID - title: Missing ID - icon: ❌ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - prompts: - - content: Prompt without ID - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/invalid/top-level/empty-file.agent.yaml b/test/fixtures/agent-schema/invalid/top-level/empty-file.agent.yaml deleted file mode 100644 index bdc8a1e1b..000000000 --- a/test/fixtures/agent-schema/invalid/top-level/empty-file.agent.yaml +++ /dev/null @@ -1,5 +0,0 @@ -# Test: Empty YAML file -# Expected: FAIL -# Error code: invalid_type -# Error path: -# Error expected: object diff --git a/test/fixtures/agent-schema/invalid/top-level/extra-top-level-keys.agent.yaml b/test/fixtures/agent-schema/invalid/top-level/extra-top-level-keys.agent.yaml deleted file mode 100644 index cc888a51b..000000000 --- a/test/fixtures/agent-schema/invalid/top-level/extra-top-level-keys.agent.yaml +++ /dev/null @@ -1,28 +0,0 @@ -# Test: Extra top-level keys beyond 'agent' -# Expected: FAIL -# Error code: unrecognized_keys -# Error path: -# Error keys: ["extra_key", "another_extra"] - -agent: - metadata: - id: extra-test - name: Extra Test Agent - title: Extra Test - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: Show help - action: display_help - -extra_key: This should not be allowed -another_extra: Also invalid diff --git a/test/fixtures/agent-schema/invalid/top-level/missing-agent-key.agent.yaml b/test/fixtures/agent-schema/invalid/top-level/missing-agent-key.agent.yaml deleted file mode 100644 index aa8814190..000000000 --- a/test/fixtures/agent-schema/invalid/top-level/missing-agent-key.agent.yaml +++ /dev/null @@ -1,11 +0,0 @@ -# Test: Missing required 'agent' top-level key -# Expected: FAIL -# Error code: invalid_type -# Error path: agent -# Error expected: object - -metadata: - id: bad-test - name: Bad Test Agent - title: Bad Test - icon: ❌ diff --git a/test/fixtures/agent-schema/invalid/yaml-errors/invalid-indentation.agent.yaml b/test/fixtures/agent-schema/invalid/yaml-errors/invalid-indentation.agent.yaml deleted file mode 100644 index 599edbb04..000000000 --- a/test/fixtures/agent-schema/invalid/yaml-errors/invalid-indentation.agent.yaml +++ /dev/null @@ -1,19 +0,0 @@ -# Test: Invalid YAML structure with inconsistent indentation -# Expected: FAIL - YAML parse error - -agent: - metadata: - id: invalid-indent - name: Invalid Indentation - title: Invalid - icon: ❌ - persona: - role: Test - identity: Test - communication_style: Test - principles: - - Test - menu: - - trigger: help - description: Help - action: help diff --git a/test/fixtures/agent-schema/invalid/yaml-errors/malformed-yaml.agent.yaml b/test/fixtures/agent-schema/invalid/yaml-errors/malformed-yaml.agent.yaml deleted file mode 100644 index 97c66a3b6..000000000 --- a/test/fixtures/agent-schema/invalid/yaml-errors/malformed-yaml.agent.yaml +++ /dev/null @@ -1,18 +0,0 @@ -# Test: Malformed YAML with syntax errors -# Expected: FAIL - YAML parse error - -agent: - metadata: - id: malformed - name: Malformed YAML - title: [Malformed - icon: 🧪 - persona: - role: Test - identity: Test - communication_style: Test - principles: - - Test - menu: - - trigger: help - description: Help diff --git a/test/fixtures/agent-schema/valid/critical-actions/empty-critical-actions.agent.yaml b/test/fixtures/agent-schema/valid/critical-actions/empty-critical-actions.agent.yaml deleted file mode 100644 index dc73477f1..000000000 --- a/test/fixtures/agent-schema/valid/critical-actions/empty-critical-actions.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Empty critical_actions array -# Expected: PASS - empty array is valid for optional field - -agent: - metadata: - id: empty-critical-actions - name: Empty Critical Actions - title: Empty Critical Actions - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with empty critical actions - identity: I am a test agent with empty critical actions array. - communication_style: Clear - principles: - - Test empty arrays - - critical_actions: [] - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/critical-actions/no-critical-actions.agent.yaml b/test/fixtures/agent-schema/valid/critical-actions/no-critical-actions.agent.yaml deleted file mode 100644 index 2df52f7f9..000000000 --- a/test/fixtures/agent-schema/valid/critical-actions/no-critical-actions.agent.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# Test: No critical_actions field (optional) -# Expected: PASS - -agent: - metadata: - id: no-critical-actions - name: No Critical Actions - title: No Critical Actions - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent without critical actions - identity: I am a test agent without critical actions. - communication_style: Clear - principles: - - Test optional fields - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/critical-actions/valid-critical-actions.agent.yaml b/test/fixtures/agent-schema/valid/critical-actions/valid-critical-actions.agent.yaml deleted file mode 100644 index 198bc835e..000000000 --- a/test/fixtures/agent-schema/valid/critical-actions/valid-critical-actions.agent.yaml +++ /dev/null @@ -1,27 +0,0 @@ -# Test: critical_actions with valid strings -# Expected: PASS - -agent: - metadata: - id: valid-critical-actions - name: Valid Critical Actions - title: Valid Critical Actions - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with critical actions - identity: I am a test agent with valid critical actions. - communication_style: Clear - principles: - - Test valid arrays - - critical_actions: - - Load configuration from disk - - Initialize user context - - Set communication preferences - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/menu-commands/all-command-types.agent.yaml b/test/fixtures/agent-schema/valid/menu-commands/all-command-types.agent.yaml deleted file mode 100644 index 959085cb7..000000000 --- a/test/fixtures/agent-schema/valid/menu-commands/all-command-types.agent.yaml +++ /dev/null @@ -1,38 +0,0 @@ -# Test: Menu items with all valid command target types -# Expected: PASS - -agent: - metadata: - id: all-commands - name: All Command Types - title: All Commands - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with all command types - identity: I test all available command target types. - communication_style: Clear - principles: - - Test all command types - - menu: - - trigger: workflow-test - description: Test workflow command - workflow: path/to/workflow - - trigger: validate-test - description: Test validate-workflow command - validate-workflow: path/to/validation - - trigger: exec-test - description: Test exec command - exec: npm test - - trigger: action-test - description: Test action command - action: perform_action - - trigger: tmpl-test - description: Test tmpl command - tmpl: path/to/template - - trigger: data-test - description: Test data command - data: path/to/data - \ No newline at end of file diff --git a/test/fixtures/agent-schema/valid/menu-commands/multiple-commands.agent.yaml b/test/fixtures/agent-schema/valid/menu-commands/multiple-commands.agent.yaml deleted file mode 100644 index 945722b5b..000000000 --- a/test/fixtures/agent-schema/valid/menu-commands/multiple-commands.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Menu item with multiple command targets -# Expected: PASS - multiple targets are allowed - -agent: - metadata: - id: multiple-commands - name: Multiple Commands - title: Multiple Commands - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with multiple command targets - identity: I test multiple command targets per menu item. - communication_style: Clear - principles: - - Test multiple targets - - menu: - - trigger: multi-command - description: Menu item with multiple command targets - workflow: path/to/workflow - exec: npm test - action: perform_action diff --git a/test/fixtures/agent-schema/valid/menu-triggers/compound-triggers.agent.yaml b/test/fixtures/agent-schema/valid/menu-triggers/compound-triggers.agent.yaml deleted file mode 100644 index 7a9fdec0b..000000000 --- a/test/fixtures/agent-schema/valid/menu-triggers/compound-triggers.agent.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Test: Valid compound triggers -# Expected: PASS - -agent: - metadata: - id: compound-triggers - name: Compound Triggers - title: Compound Triggers Test - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with compound triggers - identity: I test compound trigger validation. - communication_style: Clear - principles: - - Test compound format - - menu: - - trigger: TS or fuzzy match on tech-spec - description: "[TS] Two-word compound trigger" - action: tech_spec - - trigger: DS or fuzzy match on dev-story - description: "[DS] Another two-word compound trigger" - action: dev_story - - trigger: WI or fuzzy match on three-name-thing - description: "[WI] Three-word compound trigger (uses first 2 words for shortcut)" - action: three_name_thing - - trigger: H or fuzzy match on help - description: "[H] Single-word compound trigger (1-letter shortcut)" - action: help diff --git a/test/fixtures/agent-schema/valid/menu-triggers/kebab-case-triggers.agent.yaml b/test/fixtures/agent-schema/valid/menu-triggers/kebab-case-triggers.agent.yaml deleted file mode 100644 index cfae4fdea..000000000 --- a/test/fixtures/agent-schema/valid/menu-triggers/kebab-case-triggers.agent.yaml +++ /dev/null @@ -1,34 +0,0 @@ -# Test: Valid kebab-case triggers -# Expected: PASS - -agent: - metadata: - id: kebab-triggers - name: Kebab Case Triggers - title: Kebab Triggers - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with kebab-case triggers - identity: I test kebab-case trigger validation. - communication_style: Clear - principles: - - Test kebab-case format - - menu: - - trigger: help - description: Single word trigger - action: display_help - - trigger: list-tasks - description: Two word trigger - action: list_tasks - - trigger: three-word-process - description: Three word trigger - action: init_workflow - - trigger: test123 - description: Trigger with numbers - action: test - - trigger: multi-word-kebab-case-trigger - description: Long kebab-case trigger - action: long_action diff --git a/test/fixtures/agent-schema/valid/menu/multiple-menu-items.agent.yaml b/test/fixtures/agent-schema/valid/menu/multiple-menu-items.agent.yaml deleted file mode 100644 index c8a23a9d5..000000000 --- a/test/fixtures/agent-schema/valid/menu/multiple-menu-items.agent.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Test: Menu with multiple valid items using different command types -# Expected: PASS - -agent: - metadata: - id: multiple-menu - name: Multiple Menu Items - title: Multiple Menu - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with multiple menu items - identity: I am a test agent with diverse menu commands. - communication_style: Clear - principles: - - Test multiple menu items - - menu: - - trigger: help - description: Show help - action: display_help - - trigger: start-workflow - description: Start a workflow - workflow: path/to/workflow - - trigger: execute - description: Execute command - exec: npm test - - trigger: use-template - description: Use template - tmpl: path/to/template diff --git a/test/fixtures/agent-schema/valid/menu/single-menu-item.agent.yaml b/test/fixtures/agent-schema/valid/menu/single-menu-item.agent.yaml deleted file mode 100644 index 00c361d00..000000000 --- a/test/fixtures/agent-schema/valid/menu/single-menu-item.agent.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# Test: Menu with single valid item -# Expected: PASS - -agent: - metadata: - id: single-menu - name: Single Menu Item - title: Single Menu - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with single menu item - identity: I am a test agent. - communication_style: Clear - principles: - - Test minimal menu - - menu: - - trigger: help - description: Show help information - action: display_help diff --git a/test/fixtures/agent-schema/valid/metadata/core-agent-with-module.agent.yaml b/test/fixtures/agent-schema/valid/metadata/core-agent-with-module.agent.yaml deleted file mode 100644 index e8ad0497a..000000000 --- a/test/fixtures/agent-schema/valid/metadata/core-agent-with-module.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Core agent can have module field -# Expected: PASS -# Note: Core agents can now include module field if needed - -agent: - metadata: - id: core-with-module - name: Core With Module - title: Core Agent - icon: ✅ - module: bmm - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/metadata/empty-module-name-in-path.agent.yaml b/test/fixtures/agent-schema/valid/metadata/empty-module-name-in-path.agent.yaml deleted file mode 100644 index 10a54cb82..000000000 --- a/test/fixtures/agent-schema/valid/metadata/empty-module-name-in-path.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Empty module name in path (src/modules//agents/) -# Expected: PASS - treated as core agent (empty module normalizes to null) -# Path context: src/modules//agents/test.agent.yaml - -agent: - metadata: - id: empty-module-path - name: Empty Module in Path - title: Empty Module Path - icon: 🧪 - hasSidecar: false - # No module field - path has empty module name, treated as core - - persona: - role: Test agent for empty module name in path - identity: I test the edge case where module name in path is empty. - communication_style: Clear - principles: - - Test path parsing edge cases - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/metadata/malformed-path-treated-as-core.agent.yaml b/test/fixtures/agent-schema/valid/metadata/malformed-path-treated-as-core.agent.yaml deleted file mode 100644 index f7f752b17..000000000 --- a/test/fixtures/agent-schema/valid/metadata/malformed-path-treated-as-core.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Malformed module path (no slash after module name) treated as core -# Expected: PASS - malformed path returns null, treated as core agent -# Path context: src/bmm - -agent: - metadata: - id: malformed-path - name: Malformed Path Test - title: Malformed Path - icon: 🧪 - hasSidecar: false - # No module field - will be treated as core since path parsing returns null - - persona: - role: Test agent for malformed path edge case - identity: I test edge cases in path parsing. - communication_style: Clear - principles: - - Test edge case handling - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/metadata/module-agent-correct.agent.yaml b/test/fixtures/agent-schema/valid/metadata/module-agent-correct.agent.yaml deleted file mode 100644 index 6b5683f83..000000000 --- a/test/fixtures/agent-schema/valid/metadata/module-agent-correct.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Valid module agent with correct module field -# Expected: PASS -# Path context: src/bmm/agents/module-agent-correct.agent.yaml - -agent: - metadata: - id: bmm-test - name: BMM Test Agent - title: BMM Test - icon: 🧪 - module: bmm - hasSidecar: false - - persona: - role: Test module agent - identity: I am a module-scoped test agent. - communication_style: Professional - principles: - - Test module validation - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/metadata/module-agent-missing-module.agent.yaml b/test/fixtures/agent-schema/valid/metadata/module-agent-missing-module.agent.yaml deleted file mode 100644 index 6919c6141..000000000 --- a/test/fixtures/agent-schema/valid/metadata/module-agent-missing-module.agent.yaml +++ /dev/null @@ -1,23 +0,0 @@ -# Test: Module agent can omit module field -# Expected: PASS -# Note: Module field is optional - -agent: - metadata: - id: bmm-missing-module - name: No Module - title: Optional Module - icon: ✅ - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/metadata/wrong-module-value.agent.yaml b/test/fixtures/agent-schema/valid/metadata/wrong-module-value.agent.yaml deleted file mode 100644 index 9f6c9d218..000000000 --- a/test/fixtures/agent-schema/valid/metadata/wrong-module-value.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Module agent can have any module value -# Expected: PASS -# Note: Module validation removed - agents can declare any module - -agent: - metadata: - id: wrong-module - name: Any Module - title: Any Module Value - icon: ✅ - module: cis - hasSidecar: false - - persona: - role: Test agent - identity: Test identity - communication_style: Test style - principles: - - Test principle - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/persona/complete-persona.agent.yaml b/test/fixtures/agent-schema/valid/persona/complete-persona.agent.yaml deleted file mode 100644 index bee421b21..000000000 --- a/test/fixtures/agent-schema/valid/persona/complete-persona.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: All persona fields properly filled -# Expected: PASS - -agent: - metadata: - id: complete-persona - name: Complete Persona Agent - title: Complete Persona - icon: 🧪 - hasSidecar: false - - persona: - role: Comprehensive test agent with all persona fields - identity: I am a test agent designed to validate complete persona structure with multiple characteristics and attributes. - communication_style: Professional, clear, and thorough with attention to detail - principles: - - Validate all persona fields are present - - Ensure array fields work correctly - - Test comprehensive documentation - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/prompts/empty-prompts.agent.yaml b/test/fixtures/agent-schema/valid/prompts/empty-prompts.agent.yaml deleted file mode 100644 index da32f70e1..000000000 --- a/test/fixtures/agent-schema/valid/prompts/empty-prompts.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Empty prompts array -# Expected: PASS - empty array valid for optional field - -agent: - metadata: - id: empty-prompts - name: Empty Prompts - title: Empty Prompts - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with empty prompts - identity: I am a test agent with empty prompts array. - communication_style: Clear - principles: - - Test empty arrays - - prompts: [] - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/prompts/no-prompts.agent.yaml b/test/fixtures/agent-schema/valid/prompts/no-prompts.agent.yaml deleted file mode 100644 index 46c50f11f..000000000 --- a/test/fixtures/agent-schema/valid/prompts/no-prompts.agent.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# Test: No prompts field (optional) -# Expected: PASS - -agent: - metadata: - id: no-prompts - name: No Prompts - title: No Prompts - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent without prompts - identity: I am a test agent without prompts field. - communication_style: Clear - principles: - - Test optional fields - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/prompts/valid-prompts-minimal.agent.yaml b/test/fixtures/agent-schema/valid/prompts/valid-prompts-minimal.agent.yaml deleted file mode 100644 index 2a2d7d982..000000000 --- a/test/fixtures/agent-schema/valid/prompts/valid-prompts-minimal.agent.yaml +++ /dev/null @@ -1,28 +0,0 @@ -# Test: Prompts with required id and content only -# Expected: PASS - -agent: - metadata: - id: valid-prompts-minimal - name: Valid Prompts Minimal - title: Valid Prompts - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with minimal prompts - identity: I am a test agent with minimal prompt structure. - communication_style: Clear - principles: - - Test minimal prompts - - prompts: - - id: prompt1 - content: This is a valid prompt content - - id: prompt2 - content: Another valid prompt - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/prompts/valid-prompts-with-description.agent.yaml b/test/fixtures/agent-schema/valid/prompts/valid-prompts-with-description.agent.yaml deleted file mode 100644 index 5585415e0..000000000 --- a/test/fixtures/agent-schema/valid/prompts/valid-prompts-with-description.agent.yaml +++ /dev/null @@ -1,30 +0,0 @@ -# Test: Prompts with optional description field -# Expected: PASS - -agent: - metadata: - id: valid-prompts-description - name: Valid Prompts With Description - title: Valid Prompts Desc - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with prompts including descriptions - identity: I am a test agent with complete prompt structure. - communication_style: Clear - principles: - - Test complete prompts - - prompts: - - id: prompt1 - content: This is a valid prompt content - description: This prompt does something useful - - id: prompt2 - content: Another valid prompt - description: This prompt does something else - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/agent-schema/valid/top-level/minimal-core-agent.agent.yaml b/test/fixtures/agent-schema/valid/top-level/minimal-core-agent.agent.yaml deleted file mode 100644 index f3bf0b9ed..000000000 --- a/test/fixtures/agent-schema/valid/top-level/minimal-core-agent.agent.yaml +++ /dev/null @@ -1,24 +0,0 @@ -# Test: Valid core agent with only required fields -# Expected: PASS -# Path context: src/core/agents/minimal-core-agent.agent.yaml - -agent: - metadata: - id: minimal-test - name: Minimal Test Agent - title: Minimal Test - icon: 🧪 - hasSidecar: false - - persona: - role: Test agent with minimal configuration - identity: I am a minimal test agent used for schema validation testing. - communication_style: Clear and concise - principles: - - Validate schema requirements - - Demonstrate minimal valid structure - - menu: - - trigger: help - description: Show help - action: display_help diff --git a/test/fixtures/file-refs-csv/invalid/all-empty-workflow.csv b/test/fixtures/file-refs-csv/invalid/all-empty-workflow.csv deleted file mode 100644 index e828b414c..000000000 --- a/test/fixtures/file-refs-csv/invalid/all-empty-workflow.csv +++ /dev/null @@ -1,3 +0,0 @@ -module,phase,name,workflow-file,description -bmm,anytime,Document,,Analyze project -bmm,1-analysis,Brainstorm,,Brainstorm ideas diff --git a/test/fixtures/file-refs-csv/invalid/empty-data.csv b/test/fixtures/file-refs-csv/invalid/empty-data.csv deleted file mode 100644 index 8f71b8454..000000000 --- a/test/fixtures/file-refs-csv/invalid/empty-data.csv +++ /dev/null @@ -1 +0,0 @@ -module,phase,name,workflow-file,description diff --git a/test/fixtures/file-refs-csv/invalid/no-workflow-column.csv b/test/fixtures/file-refs-csv/invalid/no-workflow-column.csv deleted file mode 100644 index 8a5a50f99..000000000 --- a/test/fixtures/file-refs-csv/invalid/no-workflow-column.csv +++ /dev/null @@ -1,3 +0,0 @@ -name,code,description,agent -brainstorm,BSP,"Generate ideas",analyst -party,PM,"Multi-agent",facilitator diff --git a/test/fixtures/file-refs-csv/invalid/unresolvable-vars.csv b/test/fixtures/file-refs-csv/invalid/unresolvable-vars.csv deleted file mode 100644 index 89e1030f3..000000000 --- a/test/fixtures/file-refs-csv/invalid/unresolvable-vars.csv +++ /dev/null @@ -1,3 +0,0 @@ -module,phase,name,workflow-file,description -bmm,anytime,Template Var,{output_folder}/something.md,Has unresolvable template var -bmm,anytime,Normal Ref,_bmad/core/tasks/help.md,Normal resolvable ref diff --git a/test/fixtures/file-refs-csv/valid/bmm-style.csv b/test/fixtures/file-refs-csv/valid/bmm-style.csv deleted file mode 100644 index ab870ab01..000000000 --- a/test/fixtures/file-refs-csv/valid/bmm-style.csv +++ /dev/null @@ -1,3 +0,0 @@ -module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs, -bmm,anytime,Document Project,DP,,_bmad/bmm/workflows/document-project/workflow.yaml,bmad-bmm-document-project,false,analyst,Create Mode,"Analyze project",project-knowledge,*, -bmm,1-analysis,Brainstorm Project,BP,10,_bmad/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,data=template.md,"Brainstorming",planning_artifacts,"session", diff --git a/test/fixtures/file-refs-csv/valid/core-style.csv b/test/fixtures/file-refs-csv/valid/core-style.csv deleted file mode 100644 index d55df72d9..000000000 --- a/test/fixtures/file-refs-csv/valid/core-style.csv +++ /dev/null @@ -1,3 +0,0 @@ -module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs -core,anytime,Brainstorming,BSP,,_bmad/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,,"Generate ideas",{output_folder}/brainstorming.md, -core,anytime,Party Mode,PM,,_bmad/core/workflows/party-mode/workflow.md,bmad-party-mode,false,facilitator,,"Multi-agent discussion",, diff --git a/test/fixtures/file-refs-csv/valid/minimal.csv b/test/fixtures/file-refs-csv/valid/minimal.csv deleted file mode 100644 index 32dce87d8..000000000 --- a/test/fixtures/file-refs-csv/valid/minimal.csv +++ /dev/null @@ -1,2 +0,0 @@ -name,workflow-file,description -test,_bmad/core/tasks/help.md,A test entry diff --git a/test/test-agent-schema.js b/test/test-agent-schema.js deleted file mode 100644 index 8f3318fd7..000000000 --- a/test/test-agent-schema.js +++ /dev/null @@ -1,387 +0,0 @@ -/** - * Agent Schema Validation Test Runner - * - * Runs all test fixtures and verifies expected outcomes. - * Reports pass/fail for each test and overall coverage statistics. - * - * Usage: node test/test-agent-schema.js - * Exit codes: 0 = all tests pass, 1 = test failures - */ - -const fs = require('node:fs'); -const path = require('node:path'); -const yaml = require('yaml'); -const { validateAgentFile } = require('../tools/schema/agent.js'); -const { glob } = require('glob'); - -// ANSI color codes -const colors = { - reset: '\u001B[0m', - green: '\u001B[32m', - red: '\u001B[31m', - yellow: '\u001B[33m', - blue: '\u001B[34m', - cyan: '\u001B[36m', - dim: '\u001B[2m', -}; - -/** - * Parse test metadata from YAML comments - * @param {string} filePath - * @returns {{shouldPass: boolean, errorExpectation?: object, pathContext?: string}} - */ -function parseTestMetadata(filePath) { - const content = fs.readFileSync(filePath, 'utf8'); - const lines = content.split('\n'); - - let shouldPass = true; - let pathContext = null; - const errorExpectation = {}; - - for (const line of lines) { - if (line.includes('Expected: PASS')) { - shouldPass = true; - } else if (line.includes('Expected: FAIL')) { - shouldPass = false; - } - - // Parse error metadata - const codeMatch = line.match(/^# Error code: (.+)$/); - if (codeMatch) { - errorExpectation.code = codeMatch[1].trim(); - } - - const pathMatch = line.match(/^# Error path: (.+)$/); - if (pathMatch) { - errorExpectation.path = pathMatch[1].trim(); - } - - const messageMatch = line.match(/^# Error message: (.+)$/); - if (messageMatch) { - errorExpectation.message = messageMatch[1].trim(); - } - - const minimumMatch = line.match(/^# Error minimum: (\d+)$/); - if (minimumMatch) { - errorExpectation.minimum = parseInt(minimumMatch[1], 10); - } - - const expectedMatch = line.match(/^# Error expected: (.+)$/); - if (expectedMatch) { - errorExpectation.expected = expectedMatch[1].trim(); - } - - const receivedMatch = line.match(/^# Error received: (.+)$/); - if (receivedMatch) { - errorExpectation.received = receivedMatch[1].trim(); - } - - const keysMatch = line.match(/^# Error keys: \[(.+)\]$/); - if (keysMatch) { - errorExpectation.keys = keysMatch[1].split(',').map((k) => k.trim().replaceAll(/['"]/g, '')); - } - - const contextMatch = line.match(/^# Path context: (.+)$/); - if (contextMatch) { - pathContext = contextMatch[1].trim(); - } - } - - return { - shouldPass, - errorExpectation: Object.keys(errorExpectation).length > 0 ? errorExpectation : null, - pathContext, - }; -} - -/** - * Convert dot-notation path string to array (handles array indices) - * e.g., "agent.menu[0].trigger" => ["agent", "menu", 0, "trigger"] - */ -function parsePathString(pathString) { - return pathString - .replaceAll(/\[(\d+)\]/g, '.$1') // Convert [0] to .0 - .split('.') - .map((part) => { - const num = parseInt(part, 10); - return isNaN(num) ? part : num; - }); -} - -/** - * Validate error against expectations - * @param {object} error - Zod error issue - * @param {object} expectation - Expected error structure - * @returns {{valid: boolean, reason?: string}} - */ -function validateError(error, expectation) { - // Check error code - if (expectation.code && error.code !== expectation.code) { - return { valid: false, reason: `Expected code "${expectation.code}", got "${error.code}"` }; - } - - // Check error path - if (expectation.path) { - const expectedPath = parsePathString(expectation.path); - const actualPath = error.path; - - if (JSON.stringify(expectedPath) !== JSON.stringify(actualPath)) { - return { - valid: false, - reason: `Expected path ${JSON.stringify(expectedPath)}, got ${JSON.stringify(actualPath)}`, - }; - } - } - - // For custom errors, strictly check message - if (expectation.code === 'custom' && expectation.message && error.message !== expectation.message) { - return { - valid: false, - reason: `Expected message "${expectation.message}", got "${error.message}"`, - }; - } - - // For Zod errors, check type-specific fields - if (expectation.minimum !== undefined && error.minimum !== expectation.minimum) { - return { valid: false, reason: `Expected minimum ${expectation.minimum}, got ${error.minimum}` }; - } - - if (expectation.expected && error.expected !== expectation.expected) { - return { valid: false, reason: `Expected type "${expectation.expected}", got "${error.expected}"` }; - } - - if (expectation.received && error.received !== expectation.received) { - return { valid: false, reason: `Expected received "${expectation.received}", got "${error.received}"` }; - } - - if (expectation.keys) { - const expectedKeys = expectation.keys.sort(); - const actualKeys = (error.keys || []).sort(); - if (JSON.stringify(expectedKeys) !== JSON.stringify(actualKeys)) { - return { - valid: false, - reason: `Expected keys ${JSON.stringify(expectedKeys)}, got ${JSON.stringify(actualKeys)}`, - }; - } - } - - return { valid: true }; -} - -/** - * Run a single test case - * @param {string} filePath - * @returns {{passed: boolean, message: string}} - */ -function runTest(filePath) { - const metadata = parseTestMetadata(filePath); - const { shouldPass, errorExpectation, pathContext } = metadata; - - try { - const fileContent = fs.readFileSync(filePath, 'utf8'); - let agentData; - - try { - agentData = yaml.parse(fileContent); - } catch (parseError) { - // YAML parse error - if (shouldPass) { - return { - passed: false, - message: `Expected PASS but got YAML parse error: ${parseError.message}`, - }; - } - return { - passed: true, - message: 'Got expected YAML parse error', - }; - } - - // Determine validation path - // If pathContext is specified in comments, use it; otherwise derive from fixture location - let validationPath = pathContext; - if (!validationPath) { - // Map fixture location to simulated src/ path - const relativePath = path.relative(path.join(__dirname, 'fixtures/agent-schema'), filePath); - const parts = relativePath.split(path.sep); - - if (parts.includes('metadata') && parts[0] === 'valid') { - // Valid metadata tests: check if filename suggests module or core - const filename = path.basename(filePath); - if (filename.includes('module')) { - validationPath = 'src/bmm/agents/test.agent.yaml'; - } else { - validationPath = 'src/core/agents/test.agent.yaml'; - } - } else if (parts.includes('metadata') && parts[0] === 'invalid') { - // Invalid metadata tests: derive from filename - const filename = path.basename(filePath); - if (filename.includes('module') || filename.includes('wrong-module')) { - validationPath = 'src/bmm/agents/test.agent.yaml'; - } else if (filename.includes('core')) { - validationPath = 'src/core/agents/test.agent.yaml'; - } else { - validationPath = 'src/core/agents/test.agent.yaml'; - } - } else { - // Default to core agent path - validationPath = 'src/core/agents/test.agent.yaml'; - } - } - - const result = validateAgentFile(validationPath, agentData); - - if (result.success && shouldPass) { - return { - passed: true, - message: 'Validation passed as expected', - }; - } - - if (!result.success && !shouldPass) { - const actualError = result.error.issues[0]; - - // If we have error expectations, validate strictly - if (errorExpectation) { - const validation = validateError(actualError, errorExpectation); - - if (!validation.valid) { - return { - passed: false, - message: `Error validation failed: ${validation.reason}`, - }; - } - - return { - passed: true, - message: `Got expected error (${errorExpectation.code}): ${actualError.message}`, - }; - } - - // No specific expectations - just check that it failed - return { - passed: true, - message: `Got expected validation error: ${actualError?.message}`, - }; - } - - if (result.success && !shouldPass) { - return { - passed: false, - message: 'Expected validation to FAIL but it PASSED', - }; - } - - if (!result.success && shouldPass) { - return { - passed: false, - message: `Expected validation to PASS but it FAILED: ${result.error.issues[0]?.message}`, - }; - } - - return { - passed: false, - message: 'Unexpected test state', - }; - } catch (error) { - return { - passed: false, - message: `Test execution error: ${error.message}`, - }; - } -} - -/** - * Main test runner - */ -async function main() { - console.log(`${colors.cyan}╔═══════════════════════════════════════════════════════════╗${colors.reset}`); - console.log(`${colors.cyan}║ Agent Schema Validation Test Suite ║${colors.reset}`); - console.log(`${colors.cyan}╚═══════════════════════════════════════════════════════════╝${colors.reset}\n`); - - // Find all test fixtures - const testFiles = await glob('test/fixtures/agent-schema/**/*.agent.yaml', { - cwd: path.join(__dirname, '..'), - absolute: true, - }); - - if (testFiles.length === 0) { - console.log(`${colors.yellow}⚠️ No test fixtures found${colors.reset}`); - process.exit(0); - } - - console.log(`Found ${colors.cyan}${testFiles.length}${colors.reset} test fixture(s)\n`); - - // Group tests by category - const categories = {}; - for (const testFile of testFiles) { - const relativePath = path.relative(path.join(__dirname, 'fixtures/agent-schema'), testFile); - const parts = relativePath.split(path.sep); - const validInvalid = parts[0]; // 'valid' or 'invalid' - const category = parts[1]; // 'top-level', 'metadata', etc. - - const categoryKey = `${validInvalid}/${category}`; - if (!categories[categoryKey]) { - categories[categoryKey] = []; - } - categories[categoryKey].push(testFile); - } - - // Run tests by category - let totalTests = 0; - let passedTests = 0; - const failures = []; - - for (const [categoryKey, files] of Object.entries(categories).sort()) { - const [validInvalid, category] = categoryKey.split('/'); - const categoryLabel = category.replaceAll('-', ' ').toUpperCase(); - const validLabel = validInvalid === 'valid' ? '✅' : '❌'; - - console.log(`${colors.blue}${validLabel} ${categoryLabel} (${validInvalid})${colors.reset}`); - - for (const testFile of files) { - totalTests++; - const testName = path.basename(testFile, '.agent.yaml'); - const result = runTest(testFile); - - if (result.passed) { - passedTests++; - console.log(` ${colors.green}✓${colors.reset} ${testName} ${colors.dim}${result.message}${colors.reset}`); - } else { - console.log(` ${colors.red}✗${colors.reset} ${testName} ${colors.red}${result.message}${colors.reset}`); - failures.push({ - file: path.relative(process.cwd(), testFile), - message: result.message, - }); - } - } - console.log(''); - } - - // Summary - console.log(`${colors.cyan}═══════════════════════════════════════════════════════════${colors.reset}`); - console.log(`${colors.cyan}Test Results:${colors.reset}`); - console.log(` Total: ${totalTests}`); - console.log(` Passed: ${colors.green}${passedTests}${colors.reset}`); - console.log(` Failed: ${passedTests === totalTests ? colors.green : colors.red}${totalTests - passedTests}${colors.reset}`); - console.log(`${colors.cyan}═══════════════════════════════════════════════════════════${colors.reset}\n`); - - // Report failures - if (failures.length > 0) { - console.log(`${colors.red}❌ FAILED TESTS:${colors.reset}\n`); - for (const failure of failures) { - console.log(`${colors.red}✗${colors.reset} ${failure.file}`); - console.log(` ${failure.message}\n`); - } - process.exit(1); - } - - console.log(`${colors.green}✨ All tests passed!${colors.reset}\n`); - process.exit(0); -} - -// Run -main().catch((error) => { - console.error(`${colors.red}Fatal error:${colors.reset}`, error); - process.exit(1); -}); diff --git a/test/test-cli-integration.sh b/test/test-cli-integration.sh deleted file mode 100755 index cab4212d3..000000000 --- a/test/test-cli-integration.sh +++ /dev/null @@ -1,159 +0,0 @@ -#!/bin/bash -# CLI Integration Tests for Agent Schema Validator -# Tests the CLI wrapper (tools/validate-agent-schema.js) behavior and error handling -# NOTE: Tests CLI functionality using temporary test fixtures - -echo "========================================" -echo "CLI Integration Tests" -echo "========================================" -echo "" - -# Colors -GREEN='\033[0;32m' -RED='\033[0;31m' -YELLOW='\033[1;33m' -NC='\033[0m' # No Color - -PASSED=0 -FAILED=0 - -# Get the repo root (assuming script is in test/ directory) -REPO_ROOT="$(cd "$(dirname "$0")/.." && pwd)" - -# Create temp directory for test fixtures -TEMP_DIR=$(mktemp -d) -cleanup() { - rm -rf "$TEMP_DIR" -} -trap cleanup EXIT - -# Test 1: CLI fails when no files found (exit 1) -echo "Test 1: CLI fails when no agent files found (should exit 1)" -mkdir -p "$TEMP_DIR/empty/src/core/agents" -OUTPUT=$(node "$REPO_ROOT/tools/validate-agent-schema.js" "$TEMP_DIR/empty" 2>&1) -EXIT_CODE=$? -if [ $EXIT_CODE -eq 1 ] && echo "$OUTPUT" | grep -q "No agent files found"; then - echo -e "${GREEN}✓${NC} CLI fails correctly when no files found (exit 1)" - PASSED=$((PASSED + 1)) -else - echo -e "${RED}✗${NC} CLI failed to handle no files properly (exit code: $EXIT_CODE)" - FAILED=$((FAILED + 1)) -fi -echo "" - -# Test 2: CLI reports validation errors with exit code 1 -echo "Test 2: CLI reports validation errors (should exit 1)" -mkdir -p "$TEMP_DIR/invalid/src/core/agents" -cat > "$TEMP_DIR/invalid/src/core/agents/bad.agent.yaml" << 'EOF' -agent: - metadata: - id: bad - name: Bad - title: Bad - icon: 🧪 - persona: - role: Test - identity: Test - communication_style: Test - principles: [] - menu: [] -EOF -OUTPUT=$(node "$REPO_ROOT/tools/validate-agent-schema.js" "$TEMP_DIR/invalid" 2>&1) -EXIT_CODE=$? -if [ $EXIT_CODE -eq 1 ] && echo "$OUTPUT" | grep -q "failed validation"; then - echo -e "${GREEN}✓${NC} CLI reports errors correctly (exit 1)" - PASSED=$((PASSED + 1)) -else - echo -e "${RED}✗${NC} CLI failed to report errors (exit code: $EXIT_CODE)" - FAILED=$((FAILED + 1)) -fi -echo "" - -# Test 3: CLI discovers and counts agent files correctly -echo "Test 3: CLI discovers and counts agent files" -mkdir -p "$TEMP_DIR/valid/src/core/agents" -cat > "$TEMP_DIR/valid/src/core/agents/test1.agent.yaml" << 'EOF' -agent: - metadata: - id: test1 - name: Test1 - title: Test1 - icon: 🧪 - persona: - role: Test - identity: Test - communication_style: Test - principles: [Test] - menu: - - trigger: help - description: Help - action: help -EOF -cat > "$TEMP_DIR/valid/src/core/agents/test2.agent.yaml" << 'EOF' -agent: - metadata: - id: test2 - name: Test2 - title: Test2 - icon: 🧪 - persona: - role: Test - identity: Test - communication_style: Test - principles: [Test] - menu: - - trigger: help - description: Help - action: help -EOF -OUTPUT=$(node "$REPO_ROOT/tools/validate-agent-schema.js" "$TEMP_DIR/valid" 2>&1) -EXIT_CODE=$? -if [ $EXIT_CODE -eq 0 ] && echo "$OUTPUT" | grep -q "Found 2 agent file"; then - echo -e "${GREEN}✓${NC} CLI discovers and counts files correctly" - PASSED=$((PASSED + 1)) -else - echo -e "${RED}✗${NC} CLI file discovery failed" - echo "Output: $OUTPUT" - FAILED=$((FAILED + 1)) -fi -echo "" - -# Test 4: CLI provides detailed error messages -echo "Test 4: CLI provides detailed error messages" -OUTPUT=$(node "$REPO_ROOT/tools/validate-agent-schema.js" "$TEMP_DIR/invalid" 2>&1) -if echo "$OUTPUT" | grep -q "Path:" && echo "$OUTPUT" | grep -q "Error:"; then - echo -e "${GREEN}✓${NC} CLI provides error details (Path and Error)" - PASSED=$((PASSED + 1)) -else - echo -e "${RED}✗${NC} CLI error details missing" - FAILED=$((FAILED + 1)) -fi -echo "" - -# Test 5: CLI validates real BMAD agents (smoke test) -echo "Test 5: CLI validates actual BMAD agents (smoke test)" -OUTPUT=$(node "$REPO_ROOT/tools/validate-agent-schema.js" 2>&1) -EXIT_CODE=$? -if [ $EXIT_CODE -eq 0 ] && echo "$OUTPUT" | grep -qE "Found [0-9]+ agent file"; then - echo -e "${GREEN}✓${NC} CLI validates real BMAD agents successfully" - PASSED=$((PASSED + 1)) -else - echo -e "${RED}✗${NC} CLI failed on real BMAD agents (exit code: $EXIT_CODE)" - FAILED=$((FAILED + 1)) -fi -echo "" - -# Summary -echo "========================================" -echo "Test Results:" -echo " Passed: ${GREEN}$PASSED${NC}" -echo " Failed: ${RED}$FAILED${NC}" -echo "========================================" - -if [ $FAILED -eq 0 ]; then - echo -e "\n${GREEN}✨ All CLI integration tests passed!${NC}\n" - exit 0 -else - echo -e "\n${RED}❌ Some CLI integration tests failed${NC}\n" - exit 1 -fi diff --git a/test/test-file-refs-csv.js b/test/test-file-refs-csv.js deleted file mode 100644 index d068bd75d..000000000 --- a/test/test-file-refs-csv.js +++ /dev/null @@ -1,133 +0,0 @@ -/** - * CSV File Reference Extraction Test Runner - * - * Tests extractCsvRefs() from validate-file-refs.js against fixtures. - * Verifies correct extraction of workflow-file references from CSV files. - * - * Usage: node test/test-file-refs-csv.js - * Exit codes: 0 = all tests pass, 1 = test failures - */ - -const fs = require('node:fs'); -const path = require('node:path'); -const { extractCsvRefs } = require('../tools/validate-file-refs.js'); - -// ANSI color codes -const colors = { - reset: '\u001B[0m', - green: '\u001B[32m', - red: '\u001B[31m', - cyan: '\u001B[36m', - dim: '\u001B[2m', -}; - -const FIXTURES = path.join(__dirname, 'fixtures/file-refs-csv'); - -let totalTests = 0; -let passedTests = 0; -const failures = []; - -function test(name, fn) { - totalTests++; - try { - fn(); - passedTests++; - console.log(` ${colors.green}\u2713${colors.reset} ${name}`); - } catch (error) { - console.log(` ${colors.red}\u2717${colors.reset} ${name} ${colors.red}${error.message}${colors.reset}`); - failures.push({ name, message: error.message }); - } -} - -function assert(condition, message) { - if (!condition) throw new Error(message); -} - -function loadFixture(relativePath) { - const fullPath = path.join(FIXTURES, relativePath); - const content = fs.readFileSync(fullPath, 'utf-8'); - return { fullPath, content }; -} - -// --- Valid fixtures --- - -console.log(`\n${colors.cyan}CSV File Reference Extraction Tests${colors.reset}\n`); -console.log(`${colors.cyan}Valid fixtures${colors.reset}`); - -test('bmm-style.csv: extracts workflow-file refs with trailing commas', () => { - const { fullPath, content } = loadFixture('valid/bmm-style.csv'); - const refs = extractCsvRefs(fullPath, content); - assert(refs.length === 2, `Expected 2 refs, got ${refs.length}`); - assert(refs[0].raw === '_bmad/bmm/workflows/document-project/workflow.yaml', `Wrong raw[0]: ${refs[0].raw}`); - assert(refs[1].raw === '_bmad/core/workflows/brainstorming/workflow.md', `Wrong raw[1]: ${refs[1].raw}`); - assert(refs[0].type === 'project-root', `Wrong type: ${refs[0].type}`); - assert(refs[0].line === 2, `Wrong line for row 0: ${refs[0].line}`); - assert(refs[1].line === 3, `Wrong line for row 1: ${refs[1].line}`); - assert(refs[0].file === fullPath, 'Wrong file path'); -}); - -test('core-style.csv: extracts refs from core module-help format', () => { - const { fullPath, content } = loadFixture('valid/core-style.csv'); - const refs = extractCsvRefs(fullPath, content); - assert(refs.length === 2, `Expected 2 refs, got ${refs.length}`); - assert(refs[0].raw === '_bmad/core/workflows/brainstorming/workflow.md', `Wrong raw[0]: ${refs[0].raw}`); - assert(refs[1].raw === '_bmad/core/workflows/party-mode/workflow.md', `Wrong raw[1]: ${refs[1].raw}`); -}); - -test('minimal.csv: extracts refs from minimal 3-column CSV', () => { - const { fullPath, content } = loadFixture('valid/minimal.csv'); - const refs = extractCsvRefs(fullPath, content); - assert(refs.length === 1, `Expected 1 ref, got ${refs.length}`); - assert(refs[0].raw === '_bmad/core/tasks/help.md', `Wrong raw: ${refs[0].raw}`); - assert(refs[0].line === 2, `Wrong line: ${refs[0].line}`); -}); - -// --- Invalid fixtures --- - -console.log(`\n${colors.cyan}Invalid fixtures (expect 0 refs)${colors.reset}`); - -test('no-workflow-column.csv: returns 0 refs when workflow-file column missing', () => { - const { fullPath, content } = loadFixture('invalid/no-workflow-column.csv'); - const refs = extractCsvRefs(fullPath, content); - assert(refs.length === 0, `Expected 0 refs, got ${refs.length}`); -}); - -test('empty-data.csv: returns 0 refs when CSV has header only', () => { - const { fullPath, content } = loadFixture('invalid/empty-data.csv'); - const refs = extractCsvRefs(fullPath, content); - assert(refs.length === 0, `Expected 0 refs, got ${refs.length}`); -}); - -test('all-empty-workflow.csv: returns 0 refs when all workflow-file cells empty', () => { - const { fullPath, content } = loadFixture('invalid/all-empty-workflow.csv'); - const refs = extractCsvRefs(fullPath, content); - assert(refs.length === 0, `Expected 0 refs, got ${refs.length}`); -}); - -test('unresolvable-vars.csv: filters out template variables, keeps normal refs', () => { - const { fullPath, content } = loadFixture('invalid/unresolvable-vars.csv'); - const refs = extractCsvRefs(fullPath, content); - assert(refs.length === 1, `Expected 1 ref, got ${refs.length}`); - assert(refs[0].raw === '_bmad/core/tasks/help.md', `Wrong raw: ${refs[0].raw}`); -}); - -// --- Summary --- - -console.log(`\n${colors.cyan}${'═'.repeat(55)}${colors.reset}`); -console.log(`${colors.cyan}Test Results:${colors.reset}`); -console.log(` Total: ${totalTests}`); -console.log(` Passed: ${colors.green}${passedTests}${colors.reset}`); -console.log(` Failed: ${passedTests === totalTests ? colors.green : colors.red}${totalTests - passedTests}${colors.reset}`); -console.log(`${colors.cyan}${'═'.repeat(55)}${colors.reset}\n`); - -if (failures.length > 0) { - console.log(`${colors.red}FAILED TESTS:${colors.reset}\n`); - for (const failure of failures) { - console.log(`${colors.red}\u2717${colors.reset} ${failure.name}`); - console.log(` ${failure.message}\n`); - } - process.exit(1); -} - -console.log(`${colors.green}All tests passed!${colors.reset}\n`); -process.exit(0); diff --git a/test/test-installation-components.js b/test/test-installation-components.js deleted file mode 100644 index 646bd9ef7..000000000 --- a/test/test-installation-components.js +++ /dev/null @@ -1,212 +0,0 @@ -/** - * Installation Component Tests - * - * Tests individual installation components in isolation: - * - Agent YAML → XML compilation - * - Manifest generation - * - Path resolution - * - Customization merging - * - * These are deterministic unit tests that don't require full installation. - * Usage: node test/test-installation-components.js - */ - -const path = require('node:path'); -const fs = require('fs-extra'); -const { YamlXmlBuilder } = require('../tools/cli/lib/yaml-xml-builder'); -const { ManifestGenerator } = require('../tools/cli/installers/lib/core/manifest-generator'); - -// ANSI colors -const colors = { - reset: '\u001B[0m', - green: '\u001B[32m', - red: '\u001B[31m', - yellow: '\u001B[33m', - cyan: '\u001B[36m', - dim: '\u001B[2m', -}; - -let passed = 0; -let failed = 0; - -/** - * Test helper: Assert condition - */ -function assert(condition, testName, errorMessage = '') { - if (condition) { - console.log(`${colors.green}✓${colors.reset} ${testName}`); - passed++; - } else { - console.log(`${colors.red}✗${colors.reset} ${testName}`); - if (errorMessage) { - console.log(` ${colors.dim}${errorMessage}${colors.reset}`); - } - failed++; - } -} - -/** - * Test Suite - */ -async function runTests() { - console.log(`${colors.cyan}========================================`); - console.log('Installation Component Tests'); - console.log(`========================================${colors.reset}\n`); - - const projectRoot = path.join(__dirname, '..'); - - // ============================================================ - // Test 1: YAML → XML Agent Compilation (In-Memory) - // ============================================================ - console.log(`${colors.yellow}Test Suite 1: Agent Compilation${colors.reset}\n`); - - try { - const builder = new YamlXmlBuilder(); - const pmAgentPath = path.join(projectRoot, 'src/bmm/agents/pm.agent.yaml'); - - // Create temp output path - const tempOutput = path.join(__dirname, 'temp-pm-agent.md'); - - try { - const result = await builder.buildAgent(pmAgentPath, null, tempOutput, { includeMetadata: true }); - - assert(result && result.outputPath === tempOutput, 'Agent compilation returns result object with outputPath'); - - // Read the output - const compiled = await fs.readFile(tempOutput, 'utf8'); - - assert(compiled.includes(' tag'); - - assert(compiled.includes(''), 'Compiled agent contains tag'); - - assert(compiled.includes(''), 'Compiled agent contains tag'); - - assert(compiled.includes('Product Manager'), 'Compiled agent contains agent title'); - - // Cleanup - await fs.remove(tempOutput); - } catch (error) { - assert(false, 'Agent compilation succeeds', error.message); - } - } catch (error) { - assert(false, 'YamlXmlBuilder instantiates', error.message); - } - - console.log(''); - - // ============================================================ - // Test 2: Customization Merging - // ============================================================ - console.log(`${colors.yellow}Test Suite 2: Customization Merging${colors.reset}\n`); - - try { - const builder = new YamlXmlBuilder(); - - // Test deepMerge function - const base = { - agent: { - metadata: { name: 'John', title: 'PM' }, - persona: { role: 'Product Manager', style: 'Analytical' }, - }, - }; - - const customize = { - agent: { - metadata: { name: 'Sarah' }, // Override name only - persona: { style: 'Concise' }, // Override style only - }, - }; - - const merged = builder.deepMerge(base, customize); - - assert(merged.agent.metadata.name === 'Sarah', 'Deep merge overrides customized name'); - - assert(merged.agent.metadata.title === 'PM', 'Deep merge preserves non-overridden title'); - - assert(merged.agent.persona.role === 'Product Manager', 'Deep merge preserves non-overridden role'); - - assert(merged.agent.persona.style === 'Concise', 'Deep merge overrides customized style'); - } catch (error) { - assert(false, 'Customization merging works', error.message); - } - - console.log(''); - - // ============================================================ - // Test 3: Path Resolution - // ============================================================ - console.log(`${colors.yellow}Test Suite 3: Path Variable Resolution${colors.reset}\n`); - - try { - const builder = new YamlXmlBuilder(); - - // Test path resolution logic (if exposed) - // This would test {project-root}, {installed_path}, {config_source} resolution - - const testPath = '{project-root}/bmad/bmm/config.yaml'; - const expectedPattern = /\/bmad\/bmm\/config\.yaml$/; - - assert( - true, // Placeholder - would test actual resolution - 'Path variable resolution pattern matches expected format', - 'Note: This test validates path resolution logic exists', - ); - } catch (error) { - assert(false, 'Path resolution works', error.message); - } - - console.log(''); - - // ============================================================ - // Test 5: QA Agent Compilation - // ============================================================ - console.log(`${colors.yellow}Test Suite 5: QA Agent Compilation${colors.reset}\n`); - - try { - const builder = new YamlXmlBuilder(); - const qaAgentPath = path.join(projectRoot, 'src/bmm/agents/qa.agent.yaml'); - const tempOutput = path.join(__dirname, 'temp-qa-agent.md'); - - try { - const result = await builder.buildAgent(qaAgentPath, null, tempOutput, { includeMetadata: true }); - const compiled = await fs.readFile(tempOutput, 'utf8'); - - assert(compiled.includes('QA Engineer'), 'QA agent compilation includes agent title'); - - assert(compiled.includes('qa-generate-e2e-tests'), 'QA agent menu includes automate workflow'); - - // Cleanup - await fs.remove(tempOutput); - } catch (error) { - assert(false, 'QA agent compiles successfully', error.message); - } - } catch (error) { - assert(false, 'QA compilation test setup', error.message); - } - - console.log(''); - - // ============================================================ - // Summary - // ============================================================ - console.log(`${colors.cyan}========================================`); - console.log('Test Results:'); - console.log(` Passed: ${colors.green}${passed}${colors.reset}`); - console.log(` Failed: ${colors.red}${failed}${colors.reset}`); - console.log(`========================================${colors.reset}\n`); - - if (failed === 0) { - console.log(`${colors.green}✨ All installation component tests passed!${colors.reset}\n`); - process.exit(0); - } else { - console.log(`${colors.red}❌ Some installation component tests failed${colors.reset}\n`); - process.exit(1); - } -} - -// Run tests -runTests().catch((error) => { - console.error(`${colors.red}Test runner failed:${colors.reset}`, error.message); - console.error(error.stack); - process.exit(1); -}); diff --git a/test/test-rehype-plugins.mjs b/test/test-rehype-plugins.mjs deleted file mode 100644 index 47559a658..000000000 --- a/test/test-rehype-plugins.mjs +++ /dev/null @@ -1,1050 +0,0 @@ -/** - * Rehype Plugin Tests - * - * Tests for rehype-markdown-links and rehype-base-paths plugins: - * - findFirstDelimiter helper - * - detectContentDir helper - * - Transformer skip conditions - * - Path resolution - * - Index handling - * - Query/hash preservation - * - Base path prefixing - * - Element rewriting - * - Raw HTML rewriting - * - Integration (both plugins together) - * - * Usage: node test/test-rehype-plugins.mjs - */ - -import rehypeMarkdownLinks, { findFirstDelimiter, detectContentDir } from '../website/src/rehype-markdown-links.js'; -import rehypeBasePaths from '../website/src/rehype-base-paths.js'; - -// ANSI colors -const colors = { - reset: '\u001B[0m', - green: '\u001B[32m', - red: '\u001B[31m', - yellow: '\u001B[33m', - cyan: '\u001B[36m', - dim: '\u001B[2m', -}; - -let passed = 0; -let failed = 0; - -/** - * Test helper: Assert condition - */ -function assert(condition, testName, errorMessage = '') { - if (condition) { - console.log(`${colors.green}\u2713${colors.reset} ${testName}`); - passed++; - } else { - console.log(`${colors.red}\u2717${colors.reset} ${testName}`); - if (errorMessage) { - console.log(` ${colors.dim}${errorMessage}${colors.reset}`); - } - failed++; - } -} - -// --------------------------------------------------------------------------- -// Helpers -// --------------------------------------------------------------------------- - -const CONTENT_DIR = '/project/src/content/docs'; -const STD_FILE = { path: '/project/src/content/docs/guide/intro.md' }; -const STD_OPTS = { contentDir: CONTENT_DIR }; -const BASE = '/BMAD-METHOD/'; - -function transform(tree, file, options = {}) { - const plugin = rehypeMarkdownLinks(options); - plugin(tree, file); - return tree; -} - -function transformBase(tree, options = {}) { - const plugin = rehypeBasePaths(options); - plugin(tree); - return tree; -} - -function makeAnchorTree(href) { - return { - type: 'root', - children: [ - { - type: 'element', - tagName: 'a', - properties: { href }, - children: [{ type: 'text', value: 'link' }], - }, - ], - }; -} - -function makeElementTree(tagName, properties) { - return { - type: 'root', - children: [ - { - type: 'element', - tagName, - properties: { ...properties }, - children: [], - }, - ], - }; -} - -function getHref(tree) { - return tree.children[0].properties.href; -} - -function getSrc(tree) { - return tree.children[0].properties.src; -} - -function getRawValue(tree) { - return tree.children[0].value; -} - -// --------------------------------------------------------------------------- -// Test Suite -// --------------------------------------------------------------------------- - -function runTests() { - console.log(`${colors.cyan}========================================`); - console.log('Rehype Plugin Tests'); - console.log(`========================================${colors.reset}\n`); - - // ============================================================ - // findFirstDelimiter helper - // ============================================================ - console.log(`${colors.yellow}findFirstDelimiter helper (8 tests)${colors.reset}\n`); - - assert(findFirstDelimiter('page') === -1, 'No delimiters returns -1', `Expected -1, got ${findFirstDelimiter('page')}`); - - assert(findFirstDelimiter('page.md?v=1') === 7, 'Only ? returns its index (7)', `Expected 7, got ${findFirstDelimiter('page.md?v=1')}`); - - assert(findFirstDelimiter('page.md#sec') === 7, 'Only # returns its index (7)', `Expected 7, got ${findFirstDelimiter('page.md#sec')}`); - - assert( - findFirstDelimiter('page.md?v=1#sec') === 7, - '? before # returns index of ?', - `Expected 7, got ${findFirstDelimiter('page.md?v=1#sec')}`, - ); - - assert( - findFirstDelimiter('page.md#sec?v=1') === 7, - '# before ? returns index of #', - `Expected 7, got ${findFirstDelimiter('page.md#sec?v=1')}`, - ); - - assert(findFirstDelimiter('') === -1, 'Empty string returns -1', `Expected -1, got ${findFirstDelimiter('')}`); - - assert(findFirstDelimiter('#top') === 0, '# at position 0 returns 0', `Expected 0, got ${findFirstDelimiter('#top')}`); - - assert(findFirstDelimiter('?q=1') === 0, '? at position 0 returns 0', `Expected 0, got ${findFirstDelimiter('?q=1')}`); - - console.log(''); - - // ============================================================ - // detectContentDir helper - // ============================================================ - console.log(`${colors.yellow}detectContentDir helper (6 tests)${colors.reset}\n`); - - assert( - detectContentDir('/project/src/content/docs/guide/intro.md') === '/project/src/content/docs', - 'Standard path finds content dir', - `Got ${detectContentDir('/project/src/content/docs/guide/intro.md')}`, - ); - - assert( - detectContentDir('/some/random/path/file.md') === null, - 'No match returns null', - `Got ${detectContentDir('/some/random/path/file.md')}`, - ); - - assert(detectContentDir('/src/content') === null, 'Too few segments returns null', `Got ${detectContentDir('/src/content')}`); - - assert( - detectContentDir('/src/content/docs') === '/src/content/docs', - 'Exactly 3 matching segments returns match', - `Got ${detectContentDir('/src/content/docs')}`, - ); - - assert( - detectContentDir('/a/src/content/docs/nested/src/content/docs/deep/file.md') === '/a/src/content/docs/nested/src/content/docs', - 'Nested double match finds innermost', - `Got ${detectContentDir('/a/src/content/docs/nested/src/content/docs/deep/file.md')}`, - ); - - assert(detectContentDir('') === null, 'Empty string returns null', `Got ${detectContentDir('')}`); - - console.log(''); - - // ============================================================ - // Transformer skip conditions - // ============================================================ - console.log(`${colors.yellow}Transformer skip conditions (21 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('https://example.com'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === 'https://example.com', 'External https URL unchanged', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('http://example.com'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === 'http://example.com', 'External http URL unchanged', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('//cdn.example.com/path'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '//cdn.example.com/path', 'Protocol-relative // unchanged', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('mailto:user@example.com'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === 'mailto:user@example.com', 'mailto: unchanged', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('tel:+15551234567'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === 'tel:+15551234567', 'tel: unchanged', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('./page.html'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === './page.html', '.html unchanged', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('./doc.pdf'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === './doc.pdf', '.pdf unchanged', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('./page.mdx'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === './page.mdx', '.mdx unchanged', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('#section'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '#section', '#section unchanged', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('?page=2'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '?page=2', '?page=2 unchanged', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree(''); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '', 'Empty href unchanged', `Got ${getHref(tree)}`); - } - - { - // Non-anchor element (div) unchanged - const tree = { - type: 'root', - children: [ - { - type: 'element', - tagName: 'div', - properties: { href: 'page.md' }, - children: [], - }, - ], - }; - transform(tree, STD_FILE, STD_OPTS); - assert(tree.children[0].properties.href === 'page.md', 'Non-anchor element (div) unchanged', `Got ${tree.children[0].properties.href}`); - } - - { - // Anchor without properties (no crash) - const tree = { - type: 'root', - children: [{ type: 'element', tagName: 'a', children: [] }], - }; - let threw = false; - try { - transform(tree, STD_FILE, STD_OPTS); - } catch { - threw = true; - } - assert(!threw, 'Anchor without properties unchanged (no crash)'); - } - - { - // Anchor with numeric href - const tree = { - type: 'root', - children: [ - { - type: 'element', - tagName: 'a', - properties: { href: 42 }, - children: [], - }, - ], - }; - transform(tree, STD_FILE, STD_OPTS); - assert(tree.children[0].properties.href === 42, 'Anchor with numeric href unchanged', `Got ${tree.children[0].properties.href}`); - } - - { - // Anchor with null href - const tree = { - type: 'root', - children: [ - { - type: 'element', - tagName: 'a', - properties: { href: null }, - children: [], - }, - ], - }; - transform(tree, STD_FILE, STD_OPTS); - assert(tree.children[0].properties.href === null, 'Anchor with null href unchanged', `Got ${tree.children[0].properties.href}`); - } - - { - // Anchor with undefined href - const tree = { - type: 'root', - children: [ - { - type: 'element', - tagName: 'a', - properties: { href: undefined }, - children: [], - }, - ], - }; - transform(tree, STD_FILE, STD_OPTS); - assert( - tree.children[0].properties.href === undefined, - 'Anchor with undefined href unchanged', - `Got ${tree.children[0].properties.href}`, - ); - } - - { - // Target outside content root unchanged - const tree = makeAnchorTree('../../../../../../outside.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '../../../../../../outside.md', 'Target outside content root unchanged', `Got ${getHref(tree)}`); - } - - { - // No file path -> no processing - const tree = makeAnchorTree('sibling.md'); - transform(tree, { path: undefined }, STD_OPTS); - assert(getHref(tree) === 'sibling.md', 'No file path -> no processing', `Got ${getHref(tree)}`); - } - - { - // Empty string path -> no processing - const tree = makeAnchorTree('sibling.md'); - transform(tree, { path: '' }, STD_OPTS); - assert(getHref(tree) === 'sibling.md', 'Empty string path -> no processing', `Got ${getHref(tree)}`); - } - - { - // page.MD (uppercase) unchanged - const tree = makeAnchorTree('page.MD'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === 'page.MD', 'page.MD (uppercase) unchanged', `Got ${getHref(tree)}`); - } - - { - // page.Md (mixed case) unchanged - const tree = makeAnchorTree('page.Md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === 'page.Md', 'page.Md (mixed case) unchanged', `Got ${getHref(tree)}`); - } - - console.log(''); - - // ============================================================ - // Error conditions - // ============================================================ - console.log(`${colors.yellow}Error conditions (1 test)${colors.reset}\n`); - - { - // No content dir + no contentDir option -> throws - const tree = makeAnchorTree('sibling.md'); - const file = { path: '/some/random/path/file.md' }; - let threw = false; - let errorMsg = ''; - try { - transform(tree, file, {}); - } catch (error) { - threw = true; - errorMsg = error.message; - } - assert( - threw && errorMsg.includes('Could not detect content directory'), - 'No content dir + no contentDir option throws', - `threw=${threw}, msg=${errorMsg}`, - ); - } - - console.log(''); - - // ============================================================ - // Path resolution - // ============================================================ - console.log(`${colors.yellow}Path resolution (7 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('sibling.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/sibling/', 'Bare relative sibling.md -> /guide/sibling/', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('./sibling.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/sibling/', 'Dot-slash ./sibling.md -> /guide/sibling/', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('../other/page.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/other/page/', 'Parent ../other/page.md -> /other/page/', `Got ${getHref(tree)}`); - } - - { - // Use a file two levels deep so ../../ still stays inside content root - const deepFile = { - path: '/project/src/content/docs/guide/sub/intro.md', - }; - const tree = makeAnchorTree('../../root-level.md'); - transform(tree, deepFile, STD_OPTS); - assert(getHref(tree) === '/root-level/', 'Deep parent ../../root-level.md -> /root-level/', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('./sub/deep/page.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/sub/deep/page/', 'Into subdir ./sub/deep/page.md -> /guide/sub/deep/page/', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('/docs/guide/page.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/page/', 'Absolute /docs/guide/page.md -> /guide/page/', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('/guide/page.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/page/', 'Absolute /guide/page.md -> /guide/page/', `Got ${getHref(tree)}`); - } - - console.log(''); - - // ============================================================ - // Index handling - // ============================================================ - console.log(`${colors.yellow}Index handling (5 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('index.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/', 'index.md -> /guide/', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('./sub/index.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/sub/', './sub/index.md -> /guide/sub/', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('../index.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/', '../index.md -> /', `Got ${getHref(tree)}`); - } - - { - // Root index.md: file at content root - const rootFile = { - path: '/project/src/content/docs/intro.md', - }; - const tree = makeAnchorTree('index.md'); - transform(tree, rootFile, STD_OPTS); - assert(getHref(tree) === '/', 'Root index.md -> /', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('/docs/index.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/', '/docs/index.md -> /', `Got ${getHref(tree)}`); - } - - console.log(''); - - // ============================================================ - // Query/hash preservation - // ============================================================ - console.log(`${colors.yellow}Query/hash preservation (5 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('page.md#section'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/page/#section', 'page.md#section -> /guide/page/#section', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('page.md?foo=bar'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/page/?foo=bar', 'page.md?foo=bar -> /guide/page/?foo=bar', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('page.md?foo=bar#section'); - transform(tree, STD_FILE, STD_OPTS); - assert( - getHref(tree) === '/guide/page/?foo=bar#section', - 'page.md?foo=bar#section -> /guide/page/?foo=bar#section', - `Got ${getHref(tree)}`, - ); - } - - { - const tree = makeAnchorTree('page.md#section?foo=bar'); - transform(tree, STD_FILE, STD_OPTS); - assert( - getHref(tree) === '/guide/page/#section?foo=bar', - 'page.md#section?foo=bar -> /guide/page/#section?foo=bar', - `Got ${getHref(tree)}`, - ); - } - - { - const tree = makeAnchorTree('index.md#top'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/#top', 'index.md#top -> /guide/#top', `Got ${getHref(tree)}`); - } - - console.log(''); - - // ============================================================ - // Base path - // ============================================================ - console.log(`${colors.yellow}Base path (4 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('page.md'); - transform(tree, STD_FILE, { ...STD_OPTS, base: '/' }); - assert(getHref(tree) === '/guide/page/', 'Base / -> /guide/page/', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('page.md'); - transform(tree, STD_FILE, { ...STD_OPTS, base: '/BMAD-METHOD/' }); - assert(getHref(tree) === '/BMAD-METHOD/guide/page/', 'Base /BMAD-METHOD/ -> /BMAD-METHOD/guide/page/', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('page.md'); - transform(tree, STD_FILE, { ...STD_OPTS, base: '/BMAD-METHOD' }); - assert(getHref(tree) === '/BMAD-METHOD/guide/page/', 'Base /BMAD-METHOD (no trailing slash) -> same result', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('page.md'); - transform(tree, STD_FILE, { ...STD_OPTS, base: '/org/repo/docs/' }); - assert(getHref(tree) === '/org/repo/docs/guide/page/', 'Base /org/repo/docs/ -> /org/repo/docs/guide/page/', `Got ${getHref(tree)}`); - } - - console.log(''); - - // ============================================================ - // Normalization - // ============================================================ - console.log(`${colors.yellow}Normalization (3 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('page.md'); - transform(tree, STD_FILE, { ...STD_OPTS, base: '/' }); - assert(!getHref(tree).includes('//'), 'No // in output for root base', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('page.md'); - transform(tree, STD_FILE, { ...STD_OPTS, base: '/BMAD-METHOD/' }); - assert(!getHref(tree).includes('//'), 'No // in output for subpath base', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('page.md#section'); - transform(tree, STD_FILE, STD_OPTS); - const href = getHref(tree); - const hashIndex = href.indexOf('#'); - assert(href[hashIndex - 1] === '/', 'Trailing slash before suffix', `Got ${href}`); - } - - console.log(''); - - // ============================================================ - // Edge cases - // ============================================================ - console.log(`${colors.yellow}Edge cases (5 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('v2.0.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/v2.0/', 'v2.0.md -> /guide/v2.0/', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('file.test.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/file.test/', 'file.test.md -> /guide/file.test/', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('markdown-guide/foo.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/markdown-guide/foo/', 'markdown-guide/foo.md -> /guide/markdown-guide/foo/', `Got ${getHref(tree)}`); - } - - { - // .md bare -> processes (not left as ".md") - const tree = makeAnchorTree('.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) !== '.md', '.md bare -> processes (not left as ".md")', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('\u00FCber-guide.md'); - transform(tree, STD_FILE, STD_OPTS); - assert(getHref(tree) === '/guide/\u00FCber-guide/', '\u00FCber-guide.md -> /guide/\u00FCber-guide/', `Got ${getHref(tree)}`); - } - - console.log(''); - - // ============================================================ - // rehype-base-paths: Option handling - // ============================================================ - console.log(`${colors.yellow}rehype-base-paths: Option handling (5 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('/page/'); - transformBase(tree, {}); - assert(getHref(tree) === '/page/', 'Default no-op for absolute href', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('/page/'); - transformBase(tree, { base: '/BMAD-METHOD/' }); - assert(getHref(tree) === '/BMAD-METHOD/page/', 'Base /BMAD-METHOD/ prefixes', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('/page/'); - transformBase(tree, { base: '/BMAD-METHOD' }); - assert(getHref(tree) === '/BMAD-METHOD/page/', 'Base /BMAD-METHOD normalizes (adds trailing slash)', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('/page/'); - transformBase(tree, { base: '' }); - assert(getHref(tree) === '/page/', 'Empty string falls back to / (no-op)', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('/page/'); - transformBase(tree, { base: '/' }); - assert(getHref(tree) === '/page/', 'Root / is no-op', `Got ${getHref(tree)}`); - } - - console.log(''); - - // ============================================================ - // rehype-base-paths: Element rewriting - // ============================================================ - console.log(`${colors.yellow}rehype-base-paths: Element rewriting (9 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('/page/'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === '/BMAD-METHOD/page/', 'a[href] prefixed', `Got ${getHref(tree)}`); - } - - { - const tree = makeElementTree('img', { src: '/img/logo.png' }); - transformBase(tree, { base: BASE }); - assert(getSrc(tree) === '/BMAD-METHOD/img/logo.png', 'img[src] prefixed', `Got ${getSrc(tree)}`); - } - - { - const tree = makeElementTree('link', { href: '/styles/main.css' }); - transformBase(tree, { base: BASE }); - assert( - tree.children[0].properties.href === '/BMAD-METHOD/styles/main.css', - 'link[href] prefixed', - `Got ${tree.children[0].properties.href}`, - ); - } - - { - const tree = makeElementTree('script', { src: '/js/app.js' }); - transformBase(tree, { base: BASE }); - assert(getSrc(tree) === '/js/app.js', 'script[src] NOT prefixed (not in tag list)', `Got ${getSrc(tree)}`); - } - - { - const tree = makeElementTree('video', { src: '/media/intro.mp4' }); - transformBase(tree, { base: BASE }); - assert(getSrc(tree) === '/BMAD-METHOD/media/intro.mp4', 'video[src] prefixed', `Got ${getSrc(tree)}`); - } - - { - const tree = makeElementTree('audio', { src: '/media/clip.mp3' }); - transformBase(tree, { base: BASE }); - assert(getSrc(tree) === '/BMAD-METHOD/media/clip.mp3', 'audio[src] prefixed', `Got ${getSrc(tree)}`); - } - - { - const tree = makeElementTree('iframe', { src: '/embed/widget' }); - transformBase(tree, { base: BASE }); - assert(getSrc(tree) === '/BMAD-METHOD/embed/widget', 'iframe[src] prefixed', `Got ${getSrc(tree)}`); - } - - { - const tree = makeElementTree('area', { href: '/map/region' }); - transformBase(tree, { base: BASE }); - assert( - tree.children[0].properties.href === '/map/region', - 'area[href] NOT prefixed (not in tag list)', - `Got ${tree.children[0].properties.href}`, - ); - } - - { - const tree = makeElementTree('source', { src: '/media/alt.mp4' }); - transformBase(tree, { base: BASE }); - assert(getSrc(tree) === '/BMAD-METHOD/media/alt.mp4', 'source[src] prefixed', `Got ${getSrc(tree)}`); - } - - console.log(''); - - // ============================================================ - // rehype-base-paths: No-op base / - // ============================================================ - console.log(`${colors.yellow}rehype-base-paths: No-op base / (2 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('/page/'); - transformBase(tree, { base: '/' }); - assert(getHref(tree) === '/page/', 'a[href] unchanged with base /', `Got ${getHref(tree)}`); - } - - { - const tree = makeElementTree('img', { src: '/img/logo.png' }); - transformBase(tree, { base: '/' }); - assert(getSrc(tree) === '/img/logo.png', 'img[src] unchanged with base /', `Got ${getSrc(tree)}`); - } - - console.log(''); - - // ============================================================ - // rehype-base-paths: Skip conditions - // ============================================================ - console.log(`${colors.yellow}rehype-base-paths: Skip conditions (10 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('//cdn.example.com/path'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === '//cdn.example.com/path', 'Protocol-relative skipped', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('https://example.com'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === 'https://example.com', 'External https skipped', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('http://example.com'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === 'http://example.com', 'External http skipped', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('data:text/html,hello'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === 'data:text/html,hello', 'data: URI skipped', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('#section'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === '#section', '#section skipped', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree(''); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === '', 'Empty href skipped', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('/BMAD-METHOD/page/'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === '/BMAD-METHOD/page/', 'Already prefixed skipped', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('relative/path'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === 'relative/path', 'Relative path skipped', `Got ${getHref(tree)}`); - } - - { - // Non-target element (button with href-like attribute via properties) - const tree = makeElementTree('button', { href: '/page/' }); - transformBase(tree, { base: BASE }); - assert(tree.children[0].properties.href === '/page/', 'Non-target element skipped', `Got ${tree.children[0].properties.href}`); - } - - { - // Non-target attribute (data-url on an img) - const tree = makeElementTree('img', { - src: '/img/logo.png', - 'data-url': '/some/path', - }); - transformBase(tree, { base: BASE }); - assert( - tree.children[0].properties['data-url'] === '/some/path', - 'Non-target attribute (data-url) skipped', - `Got ${tree.children[0].properties['data-url']}`, - ); - } - - console.log(''); - - // ============================================================ - // rehype-base-paths: Anchor .md handling - // ============================================================ - console.log(`${colors.yellow}rehype-base-paths: Anchor .md handling (4 tests)${colors.reset}\n`); - - { - const tree = makeAnchorTree('/docs/guide/page.md'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === '/docs/guide/page.md', '.md href skipped', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('/docs/guide/page.md#section'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === '/docs/guide/page.md#section', '.md#section skipped', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('/docs/guide/page.md?v=1'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === '/docs/guide/page.md?v=1', '.md?v=1 skipped', `Got ${getHref(tree)}`); - } - - { - const tree = makeAnchorTree('/docs/index.md'); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === '/docs/index.md', 'index.md skipped', `Got ${getHref(tree)}`); - } - - console.log(''); - - // ============================================================ - // rehype-base-paths: srcset - // ============================================================ - console.log(`${colors.yellow}rehype-base-paths: srcset (1 test)${colors.reset}\n`); - - { - const tree = makeElementTree('img', { - src: '/img/logo.png', - srcset: '/img/logo-2x.png 2x', - }); - transformBase(tree, { base: BASE }); - assert( - tree.children[0].properties.srcset === '/img/logo-2x.png 2x', - 'srcset not handled by plugin', - `Got ${tree.children[0].properties.srcset}`, - ); - } - - console.log(''); - - // ============================================================ - // rehype-base-paths: Raw HTML - // ============================================================ - console.log(`${colors.yellow}rehype-base-paths: Raw HTML (7 tests)${colors.reset}\n`); - - { - const tree = { - type: 'root', - children: [{ type: 'raw', value: '' }], - }; - transformBase(tree, { base: BASE }); - assert(getRawValue(tree) === '', 'Raw img src rewritten', `Got ${getRawValue(tree)}`); - } - - { - const tree = { - type: 'root', - children: [{ type: 'raw', value: 'link' }], - }; - transformBase(tree, { base: BASE }); - assert(getRawValue(tree) === 'link', 'Raw a href rewritten', `Got ${getRawValue(tree)}`); - } - - { - const tree = { - type: 'root', - children: [{ type: 'raw', value: '' }], - }; - transformBase(tree, { base: BASE }); - assert(getRawValue(tree) === '', 'Raw protocol-relative unchanged', `Got ${getRawValue(tree)}`); - } - - { - const tree = { - type: 'root', - children: [ - { - type: 'raw', - value: '', - }, - ], - }; - transformBase(tree, { base: BASE }); - assert(getRawValue(tree) === '', 'Raw already prefixed unchanged', `Got ${getRawValue(tree)}`); - } - - { - const tree = { - type: 'root', - children: [ - { - type: 'raw', - value: '', - }, - ], - }; - transformBase(tree, { base: BASE }); - assert( - getRawValue(tree) === '', - 'Raw multiple attributes rewritten', - `Got ${getRawValue(tree)}`, - ); - } - - { - const tree = { - type: 'root', - children: [ - { - type: 'raw', - value: 'external', - }, - ], - }; - transformBase(tree, { base: BASE }); - assert(getRawValue(tree) === 'external', 'Raw external URL unchanged', `Got ${getRawValue(tree)}`); - } - - { - // Base / skips raw visit entirely - const tree = { - type: 'root', - children: [{ type: 'raw', value: '' }], - }; - transformBase(tree, { base: '/' }); - assert(getRawValue(tree) === '', 'Base / skips raw visit', `Got ${getRawValue(tree)}`); - } - - console.log(''); - - // ============================================================ - // Integration: both plugins together - // ============================================================ - console.log(`${colors.yellow}Integration: both plugins together (4 tests)${colors.reset}\n`); - - { - // ./sibling.md through both -> no double prefix - const tree = makeAnchorTree('./sibling.md'); - transform(tree, STD_FILE, { ...STD_OPTS, base: BASE }); - transformBase(tree, { base: BASE }); - const href = getHref(tree); - assert(href === '/BMAD-METHOD/guide/sibling/', './sibling.md through both -> no double prefix', `Got ${href}`); - } - - { - // img /img/logo.png -> only base-paths prefixes - const tree = makeElementTree('img', { src: '/img/logo.png' }); - // markdown-links doesn't touch img elements, so just run base-paths - transformBase(tree, { base: BASE }); - assert(getSrc(tree) === '/BMAD-METHOD/img/logo.png', 'img /img/logo.png -> only base-paths prefixes', `Got ${getSrc(tree)}`); - } - - { - // External -> both skip - const tree = makeAnchorTree('https://example.com'); - transform(tree, STD_FILE, { ...STD_OPTS, base: BASE }); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === 'https://example.com', 'External -> both skip', `Got ${getHref(tree)}`); - } - - { - // /page/ (non-.md) -> only base-paths prefixes - const tree = makeAnchorTree('/page/'); - transform(tree, STD_FILE, { ...STD_OPTS, base: BASE }); - transformBase(tree, { base: BASE }); - assert(getHref(tree) === '/BMAD-METHOD/page/', '/page/ (non-.md) -> only base-paths prefixes', `Got ${getHref(tree)}`); - } - - console.log(''); - - // ============================================================ - // Summary - // ============================================================ - console.log(`${colors.cyan}========================================`); - console.log('Test Results:'); - console.log(` Passed: ${colors.green}${passed}${colors.reset}`); - console.log(` Failed: ${colors.red}${failed}${colors.reset}`); - console.log(`========================================${colors.reset}\n`); - - if (failed === 0) { - console.log(`${colors.green}All rehype plugin tests passed!${colors.reset}\n`); - process.exit(0); - } else { - console.log(`${colors.red}Some rehype plugin tests failed${colors.reset}\n`); - process.exit(1); - } -} - -// Run tests -try { - runTests(); -} catch (error) { - console.error(`${colors.red}Test runner failed:${colors.reset}`, error.message); - console.error(error.stack); - process.exit(1); -} diff --git a/test/unit-test-schema.js b/test/unit-test-schema.js deleted file mode 100644 index e70d2ae8b..000000000 --- a/test/unit-test-schema.js +++ /dev/null @@ -1,133 +0,0 @@ -/** - * Unit Tests for Agent Schema Edge Cases - * - * Tests internal functions to achieve 100% branch coverage - */ - -const { validateAgentFile } = require('../tools/schema/agent.js'); - -console.log('Running edge case unit tests...\n'); - -let passed = 0; -let failed = 0; - -// Test 1: Path with malformed module structure (no slash after module name) -// This tests line 213: slashIndex === -1 -console.log('Test 1: Malformed module path (no slash after module name)'); -try { - const result = validateAgentFile('src/bmm', { - agent: { - metadata: { - id: 'test', - name: 'Test', - title: 'Test', - icon: '🧪', - }, - persona: { - role: 'Test', - identity: 'Test', - communication_style: 'Test', - principles: ['Test'], - }, - menu: [{ trigger: 'help', description: 'Help', action: 'help' }], - }, - }); - - if (result.success) { - console.log('✗ Should have failed - missing module field'); - failed++; - } else { - console.log('✓ Correctly handled malformed path (treated as core agent)'); - passed++; - } -} catch (error) { - console.log('✗ Unexpected error:', error.message); - failed++; -} -console.log(''); - -// Test 2: Module option with empty string -// This tests line 222: trimmed.length > 0 -console.log('Test 2: Module agent with empty string in module field'); -try { - const result = validateAgentFile('src/bmm/agents/test.agent.yaml', { - agent: { - metadata: { - id: 'test', - name: 'Test', - title: 'Test', - icon: '🧪', - module: ' ', // Empty after trimming - }, - persona: { - role: 'Test', - identity: 'Test', - communication_style: 'Test', - principles: ['Test'], - }, - menu: [{ trigger: 'help', description: 'Help', action: 'help' }], - }, - }); - - if (result.success) { - console.log('✗ Should have failed - empty module string'); - failed++; - } else { - console.log('✓ Correctly rejected empty module string'); - passed++; - } -} catch (error) { - console.log('✗ Unexpected error:', error.message); - failed++; -} -console.log(''); - -// Test 3: Core agent path (src/core/agents/...) - tests the !filePath.startsWith(marker) branch -console.log('Test 3: Core agent path returns null for module'); -try { - const result = validateAgentFile('src/core/agents/test.agent.yaml', { - agent: { - metadata: { - id: 'test', - name: 'Test', - title: 'Test', - icon: '🧪', - // No module field - correct for core agent - }, - persona: { - role: 'Test', - identity: 'Test', - communication_style: 'Test', - principles: ['Test'], - }, - menu: [{ trigger: 'help', description: 'Help', action: 'help' }], - }, - }); - - if (result.success) { - console.log('✓ Core agent validated correctly (no module required)'); - passed++; - } else { - console.log('✗ Core agent should pass without module field'); - failed++; - } -} catch (error) { - console.log('✗ Unexpected error:', error.message); - failed++; -} -console.log(''); - -// Summary -console.log('═══════════════════════════════════════'); -console.log('Edge Case Unit Test Results:'); -console.log(` Passed: ${passed}`); -console.log(` Failed: ${failed}`); -console.log('═══════════════════════════════════════\n'); - -if (failed === 0) { - console.log('✨ All edge case tests passed!\n'); - process.exit(0); -} else { - console.log('❌ Some edge case tests failed\n'); - process.exit(1); -} diff --git a/tools/bmad-npx-wrapper.js b/tools/bmad-npx-wrapper.js deleted file mode 100755 index bc63a4121..000000000 --- a/tools/bmad-npx-wrapper.js +++ /dev/null @@ -1,38 +0,0 @@ -#!/usr/bin/env node - -/** - * BMad Method CLI - Direct execution wrapper for npx - * This file ensures proper execution when run via npx from GitHub or npm registry - */ - -const { execSync } = require('node:child_process'); -const path = require('node:path'); -const fs = require('node:fs'); - -// Check if we're running in an npx temporary directory -const isNpxExecution = __dirname.includes('_npx') || __dirname.includes('.npm'); - -if (isNpxExecution) { - // Running via npx - spawn child process to preserve user's working directory - const args = process.argv.slice(2); - const bmadCliPath = path.join(__dirname, 'cli', 'bmad-cli.js'); - - if (!fs.existsSync(bmadCliPath)) { - console.error('Error: Could not find bmad-cli.js at', bmadCliPath); - console.error('Current directory:', __dirname); - process.exit(1); - } - - try { - // Execute CLI from user's working directory (process.cwd()), not npm cache - execSync(`node "${bmadCliPath}" ${args.join(' ')}`, { - stdio: 'inherit', - cwd: process.cwd(), // This preserves the user's working directory - }); - } catch (error) { - process.exit(error.status || 1); - } -} else { - // Local execution - use require - require('./cli/bmad-cli.js'); -} diff --git a/tools/build-docs.mjs b/tools/build-docs.mjs deleted file mode 100644 index bf04eb911..000000000 --- a/tools/build-docs.mjs +++ /dev/null @@ -1,463 +0,0 @@ -/** - * BMAD Documentation Build Pipeline - * - * Consolidates docs from multiple sources, generates LLM-friendly files, - * and builds the Astro+Starlight site. - * - * Build outputs: - * build/artifacts/ - With llms.txt, llms-full.txt - * build/site/ - Final Astro output (deployable) - */ - -import { execSync } from 'node:child_process'; -import fs from 'node:fs'; -import path from 'node:path'; -import { fileURLToPath } from 'node:url'; -import { getSiteUrl } from '../website/src/lib/site-url.mjs'; - -// ============================================================================= -// Configuration -// ============================================================================= - -const PROJECT_ROOT = path.dirname(path.dirname(fileURLToPath(import.meta.url))); -const BUILD_DIR = path.join(PROJECT_ROOT, 'build'); - -const REPO_URL = 'https://github.com/bmad-code-org/BMAD-METHOD'; - -// DO NOT CHANGE THESE VALUES! -// llms-full.txt is consumed by AI agents as context. Most LLMs have ~200k token limits. -// 600k chars ≈ 150k tokens (safe margin). Exceeding this breaks AI agent functionality. -const LLM_MAX_CHARS = 600_000; -const LLM_WARN_CHARS = 500_000; - -const LLM_EXCLUDE_PATTERNS = [ - 'changelog', - 'ide-info/', - 'v4-to-v6-upgrade', - 'faq', - 'reference/glossary/', - 'explanation/game-dev/', - 'bmgd/', - // Note: Files/dirs starting with _ (like _STYLE_GUIDE.md, _archive/) are excluded in shouldExcludeFromLlm() -]; - -// ============================================================================= -// Main Entry Point -/** - * Orchestrates the full BMAD documentation build pipeline. - * - * Executes the high-level build steps in sequence: prints headers and paths, validates internal - * documentation links, cleans the build directory, generates artifacts from the `docs/` folder, - * builds the Astro site, and prints a final build summary. - */ - -async function main() { - if (process.platform === 'win32') { - console.error('Error: The docs build pipeline does not support Windows.'); - console.error('Please build on Linux, macOS, or WSL.'); - process.exit(1); - } - - console.log(); - printBanner('BMAD Documentation Build Pipeline'); - console.log(); - console.log(`Project root: ${PROJECT_ROOT}`); - console.log(`Build directory: ${BUILD_DIR}`); - console.log(); - - // Check for broken internal links before building - checkDocLinks(); - - cleanBuildDirectory(); - - const docsDir = path.join(PROJECT_ROOT, 'docs'); - const artifactsDir = await generateArtifacts(docsDir); - const siteDir = buildAstroSite(); - - printBuildSummary(docsDir, artifactsDir, siteDir); -} - -main().catch((error) => { - console.error(error); - process.exit(1); -}); - -// ============================================================================= -// Pipeline Stages -/** - * Generate LLM files for the documentation pipeline. - * - * Creates the build/artifacts directory and writes `llms.txt` and `llms-full.txt` (sourced from the provided docs directory). - * - * @param {string} docsDir - Path to the source docs directory containing Markdown files. - * @returns {string} Path to the created artifacts directory. - */ - -async function generateArtifacts(docsDir) { - printHeader('Generating LLM files'); - - const outputDir = path.join(BUILD_DIR, 'artifacts'); - fs.mkdirSync(outputDir, { recursive: true }); - - // Generate LLM files reading from docs/, output to artifacts/ - generateLlmsTxt(outputDir); - generateLlmsFullTxt(docsDir, outputDir); - - console.log(); - console.log(` \u001B[32m✓\u001B[0m Artifact generation complete`); - - return outputDir; -} - -/** - * Builds the Astro + Starlight site and copies generated artifacts into the site output directory. - * - * @returns {string} The filesystem path to the built site directory (e.g., build/site). - */ -function buildAstroSite() { - printHeader('Building Astro + Starlight site'); - - const siteDir = path.join(BUILD_DIR, 'site'); - const artifactsDir = path.join(BUILD_DIR, 'artifacts'); - - // Build Astro site (outputs to build/site via astro.config.mjs) - runAstroBuild(); - copyArtifactsToSite(artifactsDir, siteDir); - - console.log(); - console.log(` \u001B[32m✓\u001B[0m Astro build complete`); - - return siteDir; -} - -// ============================================================================= -// LLM File Generation -/** - * Create a concise llms.txt summary file containing project metadata, core links, and quick navigation entries for LLM consumption. - * - * Writes the file to `${outputDir}/llms.txt`. - * - * @param {string} outputDir - Destination directory where `llms.txt` will be written. - */ - -function generateLlmsTxt(outputDir) { - console.log(' → Generating llms.txt...'); - - const siteUrl = getSiteUrl(); - const content = [ - '# BMAD Method Documentation', - '', - '> AI-driven agile development with specialized agents and workflows that scale from bug fixes to enterprise platforms.', - '', - `Documentation: ${siteUrl}`, - `Repository: ${REPO_URL}`, - `Full docs: ${siteUrl}/llms-full.txt`, - '', - '## Quick Start', - '', - `- **[Getting Started](${siteUrl}/tutorials/getting-started/)** - Tutorial: install and learn how BMad works`, - `- **[Installation](${siteUrl}/how-to/install-bmad/)** - How to install BMad Method`, - '', - '## Core Concepts', - '', - `- **[Quick Flow](${siteUrl}/explanation/quick-flow/)** - Fast development workflow`, - `- **[Party Mode](${siteUrl}/explanation/party-mode/)** - Multi-agent collaboration`, - `- **[Workflow Map](${siteUrl}/reference/workflow-map/)** - Visual overview of phases and workflows`, - '', - '## Modules', - '', - `- **[Official Modules](${siteUrl}/reference/modules/)** - BMM, BMB, BMGD, and more`, - '', - '---', - '', - '## Quick Links', - '', - `- [Full Documentation (llms-full.txt)](${siteUrl}/llms-full.txt) - Complete docs for AI context`, - '', - ].join('\n'); - - const outputPath = path.join(outputDir, 'llms.txt'); - fs.writeFileSync(outputPath, content, 'utf-8'); - console.log(` Generated llms.txt (${content.length.toLocaleString()} chars)`); -} - -/** - * Builds a consolidated llms-full.txt containing all Markdown files under docsDir wrapped in tags for LLM consumption. - * - * Writes the generated file to outputDir/llms-full.txt. Files matching LLM_EXCLUDE_PATTERNS are skipped; read errors for individual files are logged. The combined content is validated against configured size thresholds (will exit on overflow and warn if near limit). - * @param {string} docsDir - Root directory containing source Markdown files; paths in the output are relative to this directory. - * @param {string} outputDir - Directory where llms-full.txt will be written. - */ -function generateLlmsFullTxt(docsDir, outputDir) { - console.log(' → Generating llms-full.txt...'); - - const date = new Date().toISOString().split('T')[0]; - const files = getAllMarkdownFiles(docsDir).sort(compareLlmDocs); - - const output = [ - '# BMAD Method Documentation (Full)', - '', - '> Complete documentation for AI consumption', - `> Generated: ${date}`, - `> Repository: ${REPO_URL}`, - '', - ]; - - let fileCount = 0; - let skippedCount = 0; - - for (const mdPath of files) { - if (shouldExcludeFromLlm(mdPath)) { - skippedCount++; - continue; - } - - const fullPath = path.join(docsDir, mdPath); - try { - const content = readMarkdownContent(fullPath); - output.push(``, content, '', ''); - fileCount++; - } catch (error) { - console.error(` Warning: Could not read ${mdPath}: ${error.message}`); - } - } - - const result = output.join('\n'); - validateLlmSize(result); - - const outputPath = path.join(outputDir, 'llms-full.txt'); - fs.writeFileSync(outputPath, result, 'utf-8'); - - const tokenEstimate = Math.floor(result.length / 4).toLocaleString(); - console.log( - ` Processed ${fileCount} files (skipped ${skippedCount}), ${result.length.toLocaleString()} chars (~${tokenEstimate} tokens)`, - ); -} - -function compareLlmDocs(a, b) { - const aKey = getLlmSortKey(a); - const bKey = getLlmSortKey(b); - - if (aKey !== bKey) return aKey - bKey; - return a.localeCompare(b); -} - -function getLlmSortKey(filePath) { - if (filePath === 'index.md') return 0; - if (filePath.startsWith(`tutorials${path.sep}`) || filePath.startsWith('tutorials/')) return 2; - if (filePath.startsWith(`how-to${path.sep}`) || filePath.startsWith('how-to/')) return 3; - if (filePath.startsWith(`explanation${path.sep}`) || filePath.startsWith('explanation/')) return 4; - if (filePath.startsWith(`reference${path.sep}`) || filePath.startsWith('reference/')) return 5; - if (filePath.startsWith(`bmgd${path.sep}`) || filePath.startsWith('bmgd/')) return 6; - return 7; -} - -/** - * Collects all Markdown (.md) files under a directory and returns their paths relative to a base directory. - * @param {string} dir - Directory to search for Markdown files. - * @param {string} [baseDir=dir] - Base directory used to compute returned relative paths. - * @returns {string[]} An array of file paths (relative to `baseDir`) for every `.md` file found under `dir`. - */ -function getAllMarkdownFiles(dir, baseDir = dir) { - const files = []; - - for (const entry of fs.readdirSync(dir, { withFileTypes: true })) { - const fullPath = path.join(dir, entry.name); - - if (entry.isDirectory()) { - files.push(...getAllMarkdownFiles(fullPath, baseDir)); - } else if (entry.name.endsWith('.md')) { - // Return relative path from baseDir - const relativePath = path.relative(baseDir, fullPath); - files.push(relativePath); - } - } - - return files; -} - -/** - * Determine whether a file path matches any configured LLM exclusion pattern. - * Also excludes any files or directories starting with underscore. - * @param {string} filePath - The file path to test. - * @returns {boolean} `true` if excluded, `false` otherwise. - */ -function shouldExcludeFromLlm(filePath) { - // Exclude if ANY path component starts with underscore - // (e.g., _STYLE_GUIDE.md, _archive/file.md, dir/_STYLE_GUIDE.md) - const pathParts = filePath.split(path.sep); - if (pathParts.some((part) => part.startsWith('_'))) return true; - - // Check configured patterns - return LLM_EXCLUDE_PATTERNS.some((pattern) => filePath.includes(pattern)); -} - -function readMarkdownContent(filePath) { - let content = fs.readFileSync(filePath, 'utf-8'); - - if (content.startsWith('---')) { - const end = content.indexOf('---', 3); - if (end !== -1) { - content = content.slice(end + 3).trim(); - } - } - - return content; -} - -function validateLlmSize(content) { - const charCount = content.length; - - if (charCount > LLM_MAX_CHARS) { - console.error(` ERROR: Exceeds ${LLM_MAX_CHARS.toLocaleString()} char limit`); - process.exit(1); - } else if (charCount > LLM_WARN_CHARS) { - console.warn(` \u001B[33mWARNING: Approaching ${LLM_WARN_CHARS.toLocaleString()} char limit\u001B[0m`); - } -} - -// ============================================================================= -// Astro Build -/** - * Builds the Astro site to build/site (configured in astro.config.mjs). - */ -function runAstroBuild() { - console.log(' → Running astro build...'); - execSync('npx astro build --root website', { - cwd: PROJECT_ROOT, - stdio: 'inherit', - env: { - ...process.env, - }, - }); -} - -/** - * Copy generated artifact files into the built site directory. - * - * Copies llms.txt and llms-full.txt from the artifacts directory into the site directory. - * - * @param {string} artifactsDir - Path to the build artifacts directory containing generated files. - * @param {string} siteDir - Path to the target site directory where artifacts should be placed. - */ -function copyArtifactsToSite(artifactsDir, siteDir) { - console.log(' → Copying artifacts to site...'); - - fs.copyFileSync(path.join(artifactsDir, 'llms.txt'), path.join(siteDir, 'llms.txt')); - fs.copyFileSync(path.join(artifactsDir, 'llms-full.txt'), path.join(siteDir, 'llms-full.txt')); -} - -// ============================================================================= -// Build Summary -/** - * Prints a concise end-of-build summary and displays a sample listing of the final site directory. - * - * @param {string} docsDir - Path to the source documentation directory used for the build. - * @param {string} artifactsDir - Path to the directory containing generated artifacts (e.g., llms.txt). - * @param {string} siteDir - Path to the final built site directory whose contents will be listed. - */ - -function printBuildSummary(docsDir, artifactsDir, siteDir) { - console.log(); - printBanner('Build Complete!'); - console.log(); - console.log('Build artifacts:'); - console.log(` Source docs: ${docsDir}`); - console.log(` Generated files: ${artifactsDir}`); - console.log(` Final site: ${siteDir}`); - console.log(); - console.log(`Deployable output: ${siteDir}/`); - console.log(); - - listDirectoryContents(siteDir); -} - -function listDirectoryContents(dir) { - const entries = fs.readdirSync(dir).slice(0, 15); - - for (const entry of entries) { - const fullPath = path.join(dir, entry); - const stat = fs.statSync(fullPath); - - if (stat.isFile()) { - const sizeStr = formatFileSize(stat.size); - console.log(` ${entry.padEnd(40)} ${sizeStr.padStart(8)}`); - } else { - console.log(` ${entry}/`); - } - } -} - -/** - * Format a byte count into a compact human-readable string using B, K, or M units. - * @param {number} bytes - The number of bytes to format. - * @returns {string} The formatted size: bytes as `N B` (e.g. `512B`), kilobytes truncated to an integer with `K` (e.g. `2K`), or megabytes with one decimal and `M` (e.g. `1.2M`). - */ -function formatFileSize(bytes) { - if (bytes > 1024 * 1024) { - return `${(bytes / 1024 / 1024).toFixed(1)}M`; - } else if (bytes > 1024) { - return `${Math.floor(bytes / 1024)}K`; - } - return `${bytes}B`; -} - -// ============================================================================= -// File System Utilities -/** - * Remove any existing build output and recreate the build directory. - * - * Ensures the configured BUILD_DIR is empty by deleting it if present and then creating a fresh directory. - */ - -function cleanBuildDirectory() { - console.log('Cleaning previous build...'); - - if (fs.existsSync(BUILD_DIR)) { - fs.rmSync(BUILD_DIR, { recursive: true }); - } - fs.mkdirSync(BUILD_DIR, { recursive: true }); -} - -// ============================================================================= -// Console Output Formatting -// ============================================================================= - -function printHeader(title) { - console.log(); - console.log('┌' + '─'.repeat(62) + '┐'); - console.log(`│ ${title.padEnd(60)} │`); - console.log('└' + '─'.repeat(62) + '┘'); -} - -/** - * Prints a centered decorative ASCII banner to the console using the provided title. - * @param {string} title - Text to display centered inside the banner. */ -function printBanner(title) { - console.log('╔' + '═'.repeat(62) + '╗'); - console.log(`║${title.padStart(31 + title.length / 2).padEnd(62)}║`); - console.log('╚' + '═'.repeat(62) + '╝'); -} - -// ============================================================================= -// Link Checking -/** - * Verify internal documentation links by running the link-checking script. - * - * Executes the Node script tools/validate-doc-links.js from the project root and - * exits the process with code 1 if the check fails. - */ - -function checkDocLinks() { - printHeader('Checking documentation links'); - - try { - execSync('node tools/validate-doc-links.js', { - cwd: PROJECT_ROOT, - stdio: 'inherit', - }); - } catch { - console.error('\n \u001B[31m✗\u001B[0m Link check failed - fix broken links before building\n'); - process.exit(1); - } -} diff --git a/tools/cli/README.md b/tools/cli/README.md deleted file mode 100644 index 9e943d689..000000000 --- a/tools/cli/README.md +++ /dev/null @@ -1,60 +0,0 @@ -# BMad CLI Tool - -## Installing external repo BMad official modules - -For external official modules to be discoverable during install, ensure an entry for the external repo is added to external-official-modules.yaml. - -For community modules - this will be handled in a different way. This file is only for registration of modules under the bmad-code-org. - -## Post-Install Notes - -Modules can display setup guidance to users after configuration is collected during `npx bmad-method install`. Notes are defined in the module's own `module.yaml` — no changes to the installer are needed. - -### Simple Format - -Always displayed after the module is configured: - -```yaml -post-install-notes: | - Thank you for choosing the XYZ Cool Module - For Support about this Module call 555-1212 -``` - -### Conditional Format - -Display different messages based on a config question's answer: - -```yaml -post-install-notes: - config_key_name: - value1: | - Instructions for value1... - value2: | - Instructions for value2... -``` - -Values without an entry (e.g., `none`) display nothing. Multiple config keys can each have their own conditional notes. - -### Example: TEA Module - -The TEA module uses the conditional format keyed on `tea_browser_automation`: - -```yaml -post-install-notes: - tea_browser_automation: - cli: | - Playwright CLI Setup: - npm install -g @playwright/cli@latest - playwright-cli install --skills - mcp: | - Playwright MCP Setup (two servers): - 1. playwright — npx @playwright/mcp@latest - 2. playwright-test — npx playwright run-test-mcp-server - auto: | - Playwright CLI Setup: - ... - Playwright MCP Setup (two servers): - ... -``` - -When a user selects `auto`, they see both CLI and MCP instructions. When they select `none`, nothing is shown. diff --git a/tools/cli/bmad-cli.js b/tools/cli/bmad-cli.js deleted file mode 100755 index 31db41fbf..000000000 --- a/tools/cli/bmad-cli.js +++ /dev/null @@ -1,106 +0,0 @@ -const { program } = require('commander'); -const path = require('node:path'); -const fs = require('node:fs'); -const { execSync } = require('node:child_process'); -const semver = require('semver'); -const prompts = require('./lib/prompts'); - -// The installer flow uses many sequential @clack/prompts, each adding keypress -// listeners to stdin. Raise the limit to avoid spurious EventEmitter warnings. -if (process.stdin?.setMaxListeners) { - const currentLimit = process.stdin.getMaxListeners(); - process.stdin.setMaxListeners(Math.max(currentLimit, 50)); -} - -// Check for updates - do this asynchronously so it doesn't block startup -const packageJson = require('../../package.json'); -const packageName = 'bmad-method'; -checkForUpdate().catch(() => { - // Silently ignore errors - version check is best-effort -}); - -async function checkForUpdate() { - try { - // For beta versions, check the beta tag; otherwise check latest - const isBeta = - packageJson.version.includes('Beta') || - packageJson.version.includes('beta') || - packageJson.version.includes('alpha') || - packageJson.version.includes('rc'); - const tag = isBeta ? 'beta' : 'latest'; - - const result = execSync(`npm view ${packageName}@${tag} version`, { - encoding: 'utf8', - stdio: 'pipe', - timeout: 5000, - }).trim(); - - if (result && semver.gt(result, packageJson.version)) { - const color = await prompts.getColor(); - const updateMsg = [ - `You are using version ${packageJson.version} but ${result} is available.`, - '', - 'To update, exit and first run:', - ` npm cache clean --force && npx bmad-method@${tag} install`, - ].join('\n'); - await prompts.box(updateMsg, 'Update Available', { - rounded: true, - formatBorder: color.yellow, - }); - } - } catch { - // Silently fail - network issues or npm not available - } -} - -// Fix for stdin issues when running through npm on Windows -// Ensures keyboard interaction works properly with CLI prompts -if (process.stdin.isTTY) { - try { - process.stdin.resume(); - process.stdin.setEncoding('utf8'); - - // On Windows, explicitly reference the stdin stream to ensure it's properly initialized - if (process.platform === 'win32') { - process.stdin.on('error', () => { - // Ignore stdin errors - they can occur when the terminal is closing - }); - } - } catch { - // Silently ignore - some environments may not support these operations - } -} - -// Load all command modules -const commandsPath = path.join(__dirname, 'commands'); -const commandFiles = fs.readdirSync(commandsPath).filter((file) => file.endsWith('.js')); - -const commands = {}; -for (const file of commandFiles) { - const command = require(path.join(commandsPath, file)); - commands[command.command] = command; -} - -// Set up main program -program.version(packageJson.version).description('BMAD Core CLI - Universal AI agent framework'); - -// Register all commands -for (const [name, cmd] of Object.entries(commands)) { - const command = program.command(name).description(cmd.description); - - // Add options - for (const option of cmd.options || []) { - command.option(...option); - } - - // Set action - command.action(cmd.action); -} - -// Parse arguments -program.parse(process.argv); - -// Show help if no command provided -if (process.argv.slice(2).length === 0) { - program.outputHelp(); -} diff --git a/tools/cli/commands/install.js b/tools/cli/commands/install.js deleted file mode 100644 index d9d8332be..000000000 --- a/tools/cli/commands/install.js +++ /dev/null @@ -1,87 +0,0 @@ -const path = require('node:path'); -const prompts = require('../lib/prompts'); -const { Installer } = require('../installers/lib/core/installer'); -const { UI } = require('../lib/ui'); - -const installer = new Installer(); -const ui = new UI(); - -module.exports = { - command: 'install', - description: 'Install BMAD Core agents and tools', - options: [ - ['-d, --debug', 'Enable debug output for manifest generation'], - ['--directory ', 'Installation directory (default: current directory)'], - ['--modules ', 'Comma-separated list of module IDs to install (e.g., "bmm,bmb")'], - [ - '--tools ', - 'Comma-separated list of tool/IDE IDs to configure (e.g., "claude-code,cursor"). Use "none" to skip tool configuration.', - ], - ['--custom-content ', 'Comma-separated list of paths to custom modules/agents/workflows'], - ['--action ', 'Action type for existing installations: install, update, quick-update, or compile-agents'], - ['--user-name ', 'Name for agents to use (default: system username)'], - ['--communication-language ', 'Language for agent communication (default: English)'], - ['--document-output-language ', 'Language for document output (default: English)'], - ['--output-folder ', 'Output folder path relative to project root (default: _bmad-output)'], - ['-y, --yes', 'Accept all defaults and skip prompts where possible'], - ], - action: async (options) => { - try { - // Set debug flag as environment variable for all components - if (options.debug) { - process.env.BMAD_DEBUG_MANIFEST = 'true'; - await prompts.log.info('Debug mode enabled'); - } - - const config = await ui.promptInstall(options); - - // Handle cancel - if (config.actionType === 'cancel') { - await prompts.log.warn('Installation cancelled.'); - process.exit(0); - } - - // Handle quick update separately - if (config.actionType === 'quick-update') { - const result = await installer.quickUpdate(config); - await prompts.log.success('Quick update complete!'); - await prompts.log.info(`Updated ${result.moduleCount} modules with preserved settings (${result.modules.join(', ')})`); - process.exit(0); - } - - // Handle compile agents separately - if (config.actionType === 'compile-agents') { - const result = await installer.compileAgents(config); - await prompts.log.info(`Recompiled ${result.agentCount} agents with customizations applied`); - process.exit(0); - } - - // Regular install/update flow - const result = await installer.install(config); - - // Check if installation was cancelled - if (result && result.cancelled) { - process.exit(0); - } - - // Check if installation succeeded - if (result && result.success) { - process.exit(0); - } - } catch (error) { - try { - if (error.fullMessage) { - await prompts.log.error(error.fullMessage); - } else { - await prompts.log.error(`Installation failed: ${error.message}`); - } - if (error.stack) { - await prompts.log.message(error.stack); - } - } catch { - console.error(error.fullMessage || error.message || error); - } - process.exit(1); - } - }, -}; diff --git a/tools/cli/commands/status.js b/tools/cli/commands/status.js deleted file mode 100644 index ec931fe46..000000000 --- a/tools/cli/commands/status.js +++ /dev/null @@ -1,65 +0,0 @@ -const path = require('node:path'); -const prompts = require('../lib/prompts'); -const { Installer } = require('../installers/lib/core/installer'); -const { Manifest } = require('../installers/lib/core/manifest'); -const { UI } = require('../lib/ui'); - -const installer = new Installer(); -const manifest = new Manifest(); -const ui = new UI(); - -module.exports = { - command: 'status', - description: 'Display BMAD installation status and module versions', - options: [], - action: async (options) => { - try { - // Find the bmad directory - const projectDir = process.cwd(); - const { bmadDir } = await installer.findBmadDir(projectDir); - - // Check if bmad directory exists - const fs = require('fs-extra'); - if (!(await fs.pathExists(bmadDir))) { - await prompts.log.warn('No BMAD installation found in the current directory.'); - await prompts.log.message(`Expected location: ${bmadDir}`); - await prompts.log.message('Run "bmad install" to set up a new installation.'); - process.exit(0); - return; - } - - // Read manifest - const manifestData = await manifest._readRaw(bmadDir); - - if (!manifestData) { - await prompts.log.warn('No BMAD installation manifest found.'); - await prompts.log.message('Run "bmad install" to set up a new installation.'); - process.exit(0); - return; - } - - // Get installation info - const installation = manifestData.installation || {}; - const modules = manifestData.modules || []; - - // Check for available updates (only for external modules) - const availableUpdates = await manifest.checkForUpdates(bmadDir); - - // Display status - await ui.displayStatus({ - installation, - modules, - availableUpdates, - bmadDir, - }); - - process.exit(0); - } catch (error) { - await prompts.log.error(`Status check failed: ${error.message}`); - if (process.env.BMAD_DEBUG) { - await prompts.log.message(error.stack); - } - process.exit(1); - } - }, -}; diff --git a/tools/cli/commands/uninstall.js b/tools/cli/commands/uninstall.js deleted file mode 100644 index 99734791e..000000000 --- a/tools/cli/commands/uninstall.js +++ /dev/null @@ -1,167 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const prompts = require('../lib/prompts'); -const { Installer } = require('../installers/lib/core/installer'); - -const installer = new Installer(); - -module.exports = { - command: 'uninstall', - description: 'Remove BMAD installation from the current project', - options: [ - ['-y, --yes', 'Remove all BMAD components without prompting (preserves user artifacts)'], - ['--directory ', 'Project directory (default: current directory)'], - ], - action: async (options) => { - try { - let projectDir; - - if (options.directory) { - // Explicit --directory flag takes precedence - projectDir = path.resolve(options.directory); - } else if (options.yes) { - // Non-interactive mode: use current directory - projectDir = process.cwd(); - } else { - // Interactive: ask user which directory to uninstall from - // select() handles cancellation internally (exits process) - const dirChoice = await prompts.select({ - message: 'Where do you want to uninstall BMAD from?', - choices: [ - { value: 'cwd', name: `Current directory (${process.cwd()})` }, - { value: 'other', name: 'Another directory...' }, - ], - }); - - if (dirChoice === 'other') { - // text() handles cancellation internally (exits process) - const customDir = await prompts.text({ - message: 'Enter the project directory path:', - placeholder: process.cwd(), - validate: (value) => { - if (!value || value.trim().length === 0) return 'Directory path is required'; - }, - }); - - projectDir = path.resolve(customDir.trim()); - } else { - projectDir = process.cwd(); - } - } - - if (!(await fs.pathExists(projectDir))) { - await prompts.log.error(`Directory does not exist: ${projectDir}`); - process.exit(1); - } - - const { bmadDir } = await installer.findBmadDir(projectDir); - - if (!(await fs.pathExists(bmadDir))) { - await prompts.log.warn('No BMAD installation found.'); - process.exit(0); - } - - const existingInstall = await installer.getStatus(projectDir); - const version = existingInstall.version || 'unknown'; - const modules = (existingInstall.modules || []).map((m) => m.id || m.name).join(', '); - const ides = (existingInstall.ides || []).join(', '); - - const outputFolder = await installer.getOutputFolder(projectDir); - - await prompts.intro('BMAD Uninstall'); - await prompts.note(`Version: ${version}\nModules: ${modules}\nIDE integrations: ${ides}`, 'Current Installation'); - - let removeModules = true; - let removeIdeConfigs = true; - let removeOutputFolder = false; - - if (!options.yes) { - // multiselect() handles cancellation internally (exits process) - const selected = await prompts.multiselect({ - message: 'Select components to remove:', - options: [ - { - value: 'modules', - label: `BMAD Modules & data (${installer.bmadFolderName}/)`, - hint: 'Core installation, agents, workflows, config', - }, - { value: 'ide', label: 'IDE integrations', hint: ides || 'No IDEs configured' }, - { value: 'output', label: `User artifacts (${outputFolder}/)`, hint: 'WARNING: Contains your work products' }, - ], - initialValues: ['modules', 'ide'], - required: true, - }); - - removeModules = selected.includes('modules'); - removeIdeConfigs = selected.includes('ide'); - removeOutputFolder = selected.includes('output'); - - const red = (s) => `\u001B[31m${s}\u001B[0m`; - await prompts.note( - red('💀 This action is IRREVERSIBLE! Removed files cannot be recovered!') + - '\n' + - red('💀 IDE configurations and modules will need to be reinstalled.') + - '\n' + - red('💀 User artifacts are preserved unless explicitly selected.'), - '!! DESTRUCTIVE ACTION !!', - ); - - const confirmed = await prompts.confirm({ - message: 'Proceed with uninstall?', - default: false, - }); - - if (!confirmed) { - await prompts.outro('Uninstall cancelled.'); - process.exit(0); - } - } - - // Phase 1: IDE integrations - if (removeIdeConfigs) { - const s = await prompts.spinner(); - s.start('Removing IDE integrations...'); - await installer.uninstallIdeConfigs(projectDir, existingInstall, { silent: true }); - s.stop(`Removed IDE integrations (${ides || 'none'})`); - } - - // Phase 2: User artifacts - if (removeOutputFolder) { - const s = await prompts.spinner(); - s.start(`Removing user artifacts (${outputFolder}/)...`); - await installer.uninstallOutputFolder(projectDir, outputFolder); - s.stop('User artifacts removed'); - } - - // Phase 3: BMAD modules & data (last — other phases may need _bmad/) - if (removeModules) { - const s = await prompts.spinner(); - s.start(`Removing BMAD modules & data (${installer.bmadFolderName}/)...`); - await installer.uninstallModules(projectDir); - s.stop('Modules & data removed'); - } - - const summary = []; - if (removeIdeConfigs) summary.push('IDE integrations cleaned'); - if (removeModules) summary.push('Modules & data removed'); - if (removeOutputFolder) summary.push('User artifacts removed'); - if (!removeOutputFolder) summary.push(`User artifacts preserved in ${outputFolder}/`); - - await prompts.note(summary.join('\n'), 'Summary'); - await prompts.outro('To reinstall, run: npx bmad-method install'); - - process.exit(0); - } catch (error) { - try { - const errorMessage = error instanceof Error ? error.message : String(error); - await prompts.log.error(`Uninstall failed: ${errorMessage}`); - if (error instanceof Error && error.stack) { - await prompts.log.message(error.stack); - } - } catch { - console.error(error instanceof Error ? error.message : error); - } - process.exit(1); - } - }, -}; diff --git a/tools/cli/external-official-modules.yaml b/tools/cli/external-official-modules.yaml deleted file mode 100644 index d6ae06ee6..000000000 --- a/tools/cli/external-official-modules.yaml +++ /dev/null @@ -1,53 +0,0 @@ -# This file allows these modules under bmad-code-org to also be installed with the bmad method installer, while -# allowing us to keep the source of these projects in separate repos. - -modules: - bmad-builder: - url: https://github.com/bmad-code-org/bmad-builder - module-definition: src/module.yaml - code: bmb - name: "BMad Builder" - description: "Agent, Workflow and Module Builder" - defaultSelected: false - type: bmad-org - npmPackage: bmad-builder - - bmad-creative-intelligence-suite: - url: https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite - module-definition: src/module.yaml - code: cis - name: "BMad Creative Intelligence Suite" - description: "Creative tools for writing, brainstorming, and more" - defaultSelected: false - type: bmad-org - npmPackage: bmad-creative-intelligence-suite - - bmad-game-dev-studio: - url: https://github.com/bmad-code-org/bmad-module-game-dev-studio.git - module-definition: src/module.yaml - code: gds - name: "BMad Game Dev Studio" - description: "Game development agents and workflows" - defaultSelected: false - type: bmad-org - npmPackage: bmad-game-dev-studio - - bmad-method-test-architecture-enterprise: - url: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise - module-definition: src/module.yaml - code: tea - name: "Test Architect" - description: "Master Test Architect for quality strategy, test automation, and release gates" - defaultSelected: false - type: bmad-org - npmPackage: bmad-method-test-architecture-enterprise - - # whiteport-design-system: - # url: https://github.com/bmad-code-org/bmad-method-wds-expansion - # module-definition: src/module.yaml - # code: wds - # name: "Whiteport UX Design System" - # description: "UX design framework with Figma integration" - # defaultSelected: false - # type: community - # npmPackage: bmad-method-wds-expansion diff --git a/tools/cli/installers/install-messages.yaml b/tools/cli/installers/install-messages.yaml deleted file mode 100644 index 0fc32cc82..000000000 --- a/tools/cli/installers/install-messages.yaml +++ /dev/null @@ -1,39 +0,0 @@ -# BMAD Installer Messages -# These messages are displayed during installation -# Edit this file to change what users see during the install process - -# Display at the START of installation (after logo, before prompts) -startMessage: | - ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - - 🎉 V6 IS HERE! Welcome to BMad Method V6 - Official Stable Release! - - The BMad Method is now a Platform powered by the BMad Method Core and Module Ecosystem! - - Select and install modules during setup - customize your experience - - New BMad Method for Agile AI-Driven Development (the evolution of V4) - - Exciting new modules available during installation, with community modules coming soon - - Documentation: https://docs.bmad-method.org - - 🌟 BMad is 100% free and open source. - - No gated Discord. No paywalls. No gated content. - - We believe in empowering everyone, not just those who can pay. - - Knowledge should be shared, not sold. - - 🎤 SPEAKING & MEDIA: - - Available for conferences, podcasts, and media appearances - - Topics: AI-Native Transformation, Spec and Context Engineering, BMad Method - - For speaking inquiries or interviews, reach out to BMad on Discord! - - ⭐ HELP US GROW: - - Star us on GitHub: https://github.com/bmad-code-org/BMAD-METHOD/ - - Subscribe on YouTube: https://www.youtube.com/@BMadCode - - Free Community and Support: https://discord.gg/gk8jAdXWmj - - Donate: https://buymeacoffee.com/bmad - - Corporate Sponsorship available - - Latest updates: https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CHANGELOG.md - - ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ - -# No end message - install summary and next steps are rendered by the installer -endMessage: "" diff --git a/tools/cli/installers/lib/core/config-collector.js b/tools/cli/installers/lib/core/config-collector.js deleted file mode 100644 index e8569cd0f..000000000 --- a/tools/cli/installers/lib/core/config-collector.js +++ /dev/null @@ -1,1285 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const yaml = require('yaml'); -const { getProjectRoot, getModulePath } = require('../../../lib/project-root'); -const { CLIUtils } = require('../../../lib/cli-utils'); -const prompts = require('../../../lib/prompts'); - -class ConfigCollector { - constructor() { - this.collectedConfig = {}; - this.existingConfig = null; - this.currentProjectDir = null; - this._moduleManagerInstance = null; - } - - /** - * Get or create a cached ModuleManager instance (lazy initialization) - * @returns {Object} ModuleManager instance - */ - _getModuleManager() { - if (!this._moduleManagerInstance) { - const { ModuleManager } = require('../modules/manager'); - this._moduleManagerInstance = new ModuleManager(); - } - return this._moduleManagerInstance; - } - - /** - * Find the bmad installation directory in a project - * V6+ installations can use ANY folder name but ALWAYS have _config/manifest.yaml - * @param {string} projectDir - Project directory - * @returns {Promise} Path to bmad directory - */ - async findBmadDir(projectDir) { - // Check if project directory exists - if (!(await fs.pathExists(projectDir))) { - // Project doesn't exist yet, return default - return path.join(projectDir, 'bmad'); - } - - // V6+ strategy: Look for ANY directory with _config/manifest.yaml - // This is the definitive marker of a V6+ installation - try { - const entries = await fs.readdir(projectDir, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isDirectory()) { - const manifestPath = path.join(projectDir, entry.name, '_config', 'manifest.yaml'); - if (await fs.pathExists(manifestPath)) { - // Found a V6+ installation - return path.join(projectDir, entry.name); - } - } - } - } catch { - // Ignore errors, fall through to default - } - - // No V6+ installation found, return default - // This will be used for new installations - return path.join(projectDir, 'bmad'); - } - - /** - * Detect the existing BMAD folder name in a project - * @param {string} projectDir - Project directory - * @returns {Promise} Folder name (just the name, not full path) or null if not found - */ - async detectExistingBmadFolder(projectDir) { - // Check if project directory exists - if (!(await fs.pathExists(projectDir))) { - return null; - } - - // Look for ANY directory with _config/manifest.yaml - try { - const entries = await fs.readdir(projectDir, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isDirectory()) { - const manifestPath = path.join(projectDir, entry.name, '_config', 'manifest.yaml'); - if (await fs.pathExists(manifestPath)) { - // Found a V6+ installation, return just the folder name - return entry.name; - } - } - } - } catch { - // Ignore errors - } - - return null; - } - - /** - * Load existing config if it exists from module config files - * @param {string} projectDir - Target project directory - */ - async loadExistingConfig(projectDir) { - this.existingConfig = {}; - - // Check if project directory exists first - if (!(await fs.pathExists(projectDir))) { - return false; - } - - // Find the actual bmad directory (handles custom folder names) - const bmadDir = await this.findBmadDir(projectDir); - - // Check if bmad directory exists - if (!(await fs.pathExists(bmadDir))) { - return false; - } - - // Dynamically discover all installed modules by scanning bmad directory - // A directory is a module ONLY if it contains a config.yaml file - let foundAny = false; - const entries = await fs.readdir(bmadDir, { withFileTypes: true }); - - for (const entry of entries) { - if (entry.isDirectory()) { - // Skip the _config directory - it's for system use - if (entry.name === '_config' || entry.name === '_memory') { - continue; - } - - const moduleConfigPath = path.join(bmadDir, entry.name, 'config.yaml'); - - if (await fs.pathExists(moduleConfigPath)) { - try { - const content = await fs.readFile(moduleConfigPath, 'utf8'); - const moduleConfig = yaml.parse(content); - if (moduleConfig) { - this.existingConfig[entry.name] = moduleConfig; - foundAny = true; - } - } catch { - // Ignore parse errors for individual modules - } - } - } - } - - return foundAny; - } - - /** - * Pre-scan module schemas to gather metadata for the configuration gateway prompt. - * Returns info about which modules have configurable options. - * @param {Array} modules - List of non-core module names - * @returns {Promise} Array of {moduleName, displayName, questionCount, hasFieldsWithoutDefaults} - */ - async scanModuleSchemas(modules) { - const metadataFields = new Set(['code', 'name', 'header', 'subheader', 'default_selected']); - const results = []; - - for (const moduleName of modules) { - // Resolve module.yaml path - custom paths first, then standard location, then ModuleManager search - let moduleConfigPath = null; - const customPath = this.customModulePaths?.get(moduleName); - if (customPath) { - moduleConfigPath = path.join(customPath, 'module.yaml'); - } else { - const standardPath = path.join(getModulePath(moduleName), 'module.yaml'); - if (await fs.pathExists(standardPath)) { - moduleConfigPath = standardPath; - } else { - const moduleSourcePath = await this._getModuleManager().findModuleSource(moduleName, { silent: true }); - if (moduleSourcePath) { - moduleConfigPath = path.join(moduleSourcePath, 'module.yaml'); - } - } - } - - if (!moduleConfigPath || !(await fs.pathExists(moduleConfigPath))) { - continue; - } - - try { - const content = await fs.readFile(moduleConfigPath, 'utf8'); - const moduleConfig = yaml.parse(content); - if (!moduleConfig) continue; - - const displayName = moduleConfig.header || `${moduleName.toUpperCase()} Module`; - const configKeys = Object.keys(moduleConfig).filter((key) => key !== 'prompt'); - const questionKeys = configKeys.filter((key) => { - if (metadataFields.has(key)) return false; - const item = moduleConfig[key]; - return item && typeof item === 'object' && item.prompt; - }); - - const hasFieldsWithoutDefaults = questionKeys.some((key) => { - const item = moduleConfig[key]; - return item.default === undefined || item.default === null || item.default === ''; - }); - - results.push({ - moduleName, - displayName, - questionCount: questionKeys.length, - hasFieldsWithoutDefaults, - }); - } catch (error) { - await prompts.log.warn(`Could not read schema for module "${moduleName}": ${error.message}`); - } - } - - return results; - } - - /** - * Collect configuration for all modules - * @param {Array} modules - List of modules to configure (including 'core') - * @param {string} projectDir - Target project directory - * @param {Object} options - Additional options - * @param {Map} options.customModulePaths - Map of module ID to source path for custom modules - * @param {boolean} options.skipPrompts - Skip prompts and use defaults (for --yes flag) - */ - async collectAllConfigurations(modules, projectDir, options = {}) { - // Store custom module paths for use in collectModuleConfig - this.customModulePaths = options.customModulePaths || new Map(); - this.skipPrompts = options.skipPrompts || false; - this.modulesToCustomize = undefined; - await this.loadExistingConfig(projectDir); - - // Check if core was already collected (e.g., in early collection phase) - const coreAlreadyCollected = this.collectedConfig.core && Object.keys(this.collectedConfig.core).length > 0; - - // If core wasn't already collected, include it - const allModules = coreAlreadyCollected ? modules.filter((m) => m !== 'core') : ['core', ...modules.filter((m) => m !== 'core')]; - - // Store all answers across modules for cross-referencing - if (!this.allAnswers) { - this.allAnswers = {}; - } - - // Split processing: core first, then gateway, then remaining modules - const coreModules = allModules.filter((m) => m === 'core'); - const nonCoreModules = allModules.filter((m) => m !== 'core'); - - // Collect core config first (always fully prompted) - for (const moduleName of coreModules) { - await this.collectModuleConfig(moduleName, projectDir); - } - - // Show batch configuration gateway for non-core modules - // Scan all non-core module schemas for display names and config metadata - let scannedModules = []; - if (!this.skipPrompts && nonCoreModules.length > 0) { - scannedModules = await this.scanModuleSchemas(nonCoreModules); - const customizableModules = scannedModules.filter((m) => m.questionCount > 0); - - if (customizableModules.length > 0) { - const configMode = await prompts.select({ - message: 'Module configuration', - choices: [ - { name: 'Express Setup', value: 'express', hint: 'accept all defaults (recommended)' }, - { name: 'Customize', value: 'customize', hint: 'choose modules to configure' }, - ], - default: 'express', - }); - - if (configMode === 'customize') { - const choices = customizableModules.map((m) => ({ - name: `${m.displayName} (${m.questionCount} option${m.questionCount === 1 ? '' : 's'})`, - value: m.moduleName, - hint: m.hasFieldsWithoutDefaults ? 'has fields without defaults' : undefined, - checked: m.hasFieldsWithoutDefaults, - })); - const selected = await prompts.multiselect({ - message: 'Select modules to customize:', - choices, - required: false, - }); - this.modulesToCustomize = new Set(selected); - } else { - // Express mode: no modules to customize - this.modulesToCustomize = new Set(); - } - } else { - // All non-core modules have zero config - no gateway needed - this.modulesToCustomize = new Set(); - } - } - - // Collect remaining non-core modules - if (this.modulesToCustomize === undefined) { - // No gateway was shown (skipPrompts, no non-core modules, or direct call) - process all normally - for (const moduleName of nonCoreModules) { - await this.collectModuleConfig(moduleName, projectDir); - } - } else { - // Split into default modules (tasks progress) and customized modules (interactive) - const defaultModules = nonCoreModules.filter((m) => !this.modulesToCustomize.has(m)); - const customizeModules = nonCoreModules.filter((m) => this.modulesToCustomize.has(m)); - - // Run default modules with a single spinner - if (defaultModules.length > 0) { - // Build display name map from all scanned modules for pre-call spinner messages - const displayNameMap = new Map(); - for (const m of scannedModules) { - displayNameMap.set(m.moduleName, m.displayName); - } - - const configSpinner = await prompts.spinner(); - configSpinner.start('Configuring modules...'); - try { - for (const moduleName of defaultModules) { - const displayName = displayNameMap.get(moduleName) || moduleName.toUpperCase(); - configSpinner.message(`Configuring ${displayName}...`); - try { - this._silentConfig = true; - await this.collectModuleConfig(moduleName, projectDir); - } finally { - this._silentConfig = false; - } - } - } finally { - configSpinner.stop(customizeModules.length > 0 ? 'Module defaults applied' : 'Module configuration complete'); - } - } - - // Run customized modules individually (may show interactive prompts) - for (const moduleName of customizeModules) { - await this.collectModuleConfig(moduleName, projectDir); - } - - if (customizeModules.length > 0) { - await prompts.log.step('Module configuration complete'); - } - } - - // Add metadata - this.collectedConfig._meta = { - version: require(path.join(getProjectRoot(), 'package.json')).version, - installDate: new Date().toISOString(), - lastModified: new Date().toISOString(), - }; - - return this.collectedConfig; - } - - /** - * Collect configuration for a single module (Quick Update mode - only new fields) - * @param {string} moduleName - Module name - * @param {string} projectDir - Target project directory - * @param {boolean} silentMode - If true, only prompt for new/missing fields - * @returns {boolean} True if new fields were prompted, false if all fields existed - */ - async collectModuleConfigQuick(moduleName, projectDir, silentMode = true) { - this.currentProjectDir = projectDir; - - // Load existing config if not already loaded - if (!this.existingConfig) { - await this.loadExistingConfig(projectDir); - } - - // Initialize allAnswers if not already initialized - if (!this.allAnswers) { - this.allAnswers = {}; - } - - // Load module's config schema from module.yaml - // First, try the standard src/modules location - let moduleConfigPath = path.join(getModulePath(moduleName), 'module.yaml'); - - // If not found in src/modules, we need to find it by searching the project - if (!(await fs.pathExists(moduleConfigPath))) { - const moduleSourcePath = await this._getModuleManager().findModuleSource(moduleName, { silent: true }); - - if (moduleSourcePath) { - moduleConfigPath = path.join(moduleSourcePath, 'module.yaml'); - } - } - - let configPath = null; - let isCustomModule = false; - - if (await fs.pathExists(moduleConfigPath)) { - configPath = moduleConfigPath; - } else { - // Check if this is a custom module with custom.yaml - const moduleSourcePath = await this._getModuleManager().findModuleSource(moduleName, { silent: true }); - - if (moduleSourcePath) { - const rootCustomConfigPath = path.join(moduleSourcePath, 'custom.yaml'); - - if (await fs.pathExists(rootCustomConfigPath)) { - isCustomModule = true; - // For custom modules, we don't have an install-config schema, so just use existing values - // The custom.yaml values will be loaded and merged during installation - } - } - - // No config schema for this module - use existing values - if (this.existingConfig && this.existingConfig[moduleName]) { - if (!this.collectedConfig[moduleName]) { - this.collectedConfig[moduleName] = {}; - } - this.collectedConfig[moduleName] = { ...this.existingConfig[moduleName] }; - } - return false; - } - - const configContent = await fs.readFile(configPath, 'utf8'); - const moduleConfig = yaml.parse(configContent); - - if (!moduleConfig) { - return false; - } - - // Compare schema with existing config to find new/missing fields - const configKeys = Object.keys(moduleConfig).filter((key) => key !== 'prompt'); - const existingKeys = this.existingConfig && this.existingConfig[moduleName] ? Object.keys(this.existingConfig[moduleName]) : []; - - // Check if this module has no configuration keys at all (like CIS) - // Filter out metadata fields and only count actual config objects - const metadataFields = new Set(['code', 'name', 'header', 'subheader', 'default_selected']); - const actualConfigKeys = configKeys.filter((key) => !metadataFields.has(key)); - const hasNoConfig = actualConfigKeys.length === 0; - - // If module has no config keys at all, handle it specially - if (hasNoConfig && moduleConfig.subheader) { - const moduleDisplayName = moduleConfig.header || `${moduleName.toUpperCase()} Module`; - await prompts.log.step(moduleDisplayName); - await prompts.log.message(` \u2713 ${moduleConfig.subheader}`); - return false; // No new fields - } - - // Find new interactive fields (with prompt) - const newKeys = configKeys.filter((key) => { - const item = moduleConfig[key]; - // Check if it's a config item and doesn't exist in existing config - return item && typeof item === 'object' && item.prompt && !existingKeys.includes(key); - }); - - // Find new static fields (without prompt, just result) - const newStaticKeys = configKeys.filter((key) => { - const item = moduleConfig[key]; - return item && typeof item === 'object' && !item.prompt && item.result && !existingKeys.includes(key); - }); - - // If in silent mode and no new keys (neither interactive nor static), use existing config and skip prompts - if (silentMode && newKeys.length === 0 && newStaticKeys.length === 0) { - if (this.existingConfig && this.existingConfig[moduleName]) { - if (!this.collectedConfig[moduleName]) { - this.collectedConfig[moduleName] = {}; - } - this.collectedConfig[moduleName] = { ...this.existingConfig[moduleName] }; - - // Special handling for user_name: ensure it has a value - if ( - moduleName === 'core' && - (!this.collectedConfig[moduleName].user_name || this.collectedConfig[moduleName].user_name === '[USER_NAME]') - ) { - this.collectedConfig[moduleName].user_name = this.getDefaultUsername(); - } - - // Also populate allAnswers for cross-referencing - for (const [key, value] of Object.entries(this.existingConfig[moduleName])) { - // Ensure user_name is properly set in allAnswers too - let finalValue = value; - if (moduleName === 'core' && key === 'user_name' && (!value || value === '[USER_NAME]')) { - finalValue = this.getDefaultUsername(); - } - this.allAnswers[`${moduleName}_${key}`] = finalValue; - } - } else if (moduleName === 'core') { - // No existing core config - ensure we at least have user_name - if (!this.collectedConfig[moduleName]) { - this.collectedConfig[moduleName] = {}; - } - if (!this.collectedConfig[moduleName].user_name) { - this.collectedConfig[moduleName].user_name = this.getDefaultUsername(); - this.allAnswers[`${moduleName}_user_name`] = this.getDefaultUsername(); - } - } - - // Show "no config" message for modules with no new questions (that have config keys) - await prompts.log.message(` \u2713 ${moduleName.toUpperCase()} module already up to date`); - return false; // No new fields - } - - // If we have new fields (interactive or static), process them - if (newKeys.length > 0 || newStaticKeys.length > 0) { - const questions = []; - const staticAnswers = {}; - - // Build questions for interactive fields - for (const key of newKeys) { - const item = moduleConfig[key]; - const question = await this.buildQuestion(moduleName, key, item, moduleConfig); - if (question) { - questions.push(question); - } - } - - // Prepare static answers (no prompt, just result) - for (const key of newStaticKeys) { - staticAnswers[`${moduleName}_${key}`] = undefined; - } - - // Collect all answers (static + prompted) - let allAnswers = { ...staticAnswers }; - - if (questions.length > 0) { - // Only show header if we actually have questions - await CLIUtils.displayModuleConfigHeader(moduleName, moduleConfig.header, moduleConfig.subheader); - await prompts.log.message(''); - const promptedAnswers = await prompts.prompt(questions); - - // Merge prompted answers with static answers - Object.assign(allAnswers, promptedAnswers); - } else if (newStaticKeys.length > 0) { - // Only static fields, no questions - show no config message - await prompts.log.message(` \u2713 ${moduleName.toUpperCase()} module configuration updated`); - } - - // Store all answers for cross-referencing - Object.assign(this.allAnswers, allAnswers); - - // Process all answers (both static and prompted) - // First, copy existing config to preserve values that aren't being updated - if (this.existingConfig && this.existingConfig[moduleName]) { - this.collectedConfig[moduleName] = { ...this.existingConfig[moduleName] }; - } else { - this.collectedConfig[moduleName] = {}; - } - - for (const key of Object.keys(allAnswers)) { - const originalKey = key.replace(`${moduleName}_`, ''); - const item = moduleConfig[originalKey]; - const value = allAnswers[key]; - - let result; - if (Array.isArray(value)) { - result = value; - } else if (item.result) { - result = this.processResultTemplate(item.result, value); - } else { - result = value; - } - - // Update the collected config with new/updated values - this.collectedConfig[moduleName][originalKey] = result; - } - } - - // Copy over existing values for fields that weren't prompted - if (this.existingConfig && this.existingConfig[moduleName]) { - if (!this.collectedConfig[moduleName]) { - this.collectedConfig[moduleName] = {}; - } - for (const [key, value] of Object.entries(this.existingConfig[moduleName])) { - if (!this.collectedConfig[moduleName][key]) { - this.collectedConfig[moduleName][key] = value; - this.allAnswers[`${moduleName}_${key}`] = value; - } - } - } - - await this.displayModulePostConfigNotes(moduleName, moduleConfig); - - return newKeys.length > 0 || newStaticKeys.length > 0; // Return true if we had any new fields (interactive or static) - } - - /** - * Process a result template with value substitution - * @param {*} resultTemplate - The result template - * @param {*} value - The value to substitute - * @returns {*} Processed result - */ - processResultTemplate(resultTemplate, value) { - let result = resultTemplate; - - if (typeof result === 'string' && value !== undefined) { - if (typeof value === 'string') { - result = result.replace('{value}', value); - } else if (typeof value === 'boolean' || typeof value === 'number') { - if (result === '{value}') { - result = value; - } else { - result = result.replace('{value}', value); - } - } else { - result = value; - } - - if (typeof result === 'string') { - result = result.replaceAll(/{([^}]+)}/g, (match, configKey) => { - if (configKey === 'project-root') { - return '{project-root}'; - } - if (configKey === 'value') { - return match; - } - - let configValue = this.allAnswers[configKey] || this.allAnswers[`${configKey}`]; - if (!configValue) { - for (const [answerKey, answerValue] of Object.entries(this.allAnswers)) { - if (answerKey.endsWith(`_${configKey}`)) { - configValue = answerValue; - break; - } - } - } - - if (!configValue) { - for (const mod of Object.keys(this.collectedConfig)) { - if (mod !== '_meta' && this.collectedConfig[mod] && this.collectedConfig[mod][configKey]) { - configValue = this.collectedConfig[mod][configKey]; - if (typeof configValue === 'string' && configValue.includes('{project-root}/')) { - configValue = configValue.replace('{project-root}/', ''); - } - break; - } - } - } - - return configValue || match; - }); - } - } - - return result; - } - - /** - * Get the default username from the system - * @returns {string} Capitalized username\ - */ - getDefaultUsername() { - let result = 'BMad'; - try { - const os = require('node:os'); - const userInfo = os.userInfo(); - if (userInfo && userInfo.username) { - const username = userInfo.username; - result = username.charAt(0).toUpperCase() + username.slice(1); - } - } catch { - // Do nothing, just return 'BMad' - } - return result; - } - - /** - * Collect configuration for a single module - * @param {string} moduleName - Module name - * @param {string} projectDir - Target project directory - * @param {boolean} skipLoadExisting - Skip loading existing config (for early core collection) - * @param {boolean} skipCompletion - Skip showing completion message (for early core collection) - */ - async collectModuleConfig(moduleName, projectDir, skipLoadExisting = false, skipCompletion = false) { - this.currentProjectDir = projectDir; - // Load existing config if needed and not already loaded - if (!skipLoadExisting && !this.existingConfig) { - await this.loadExistingConfig(projectDir); - } - - // Initialize allAnswers if not already initialized - if (!this.allAnswers) { - this.allAnswers = {}; - } - // Load module's config - // First, check if we have a custom module path for this module - let moduleConfigPath = null; - - if (this.customModulePaths && this.customModulePaths.has(moduleName)) { - const customPath = this.customModulePaths.get(moduleName); - moduleConfigPath = path.join(customPath, 'module.yaml'); - } else { - // Try the standard src/modules location - moduleConfigPath = path.join(getModulePath(moduleName), 'module.yaml'); - } - - // If not found in src/modules or custom paths, search the project - if (!(await fs.pathExists(moduleConfigPath))) { - const moduleSourcePath = await this._getModuleManager().findModuleSource(moduleName, { silent: true }); - - if (moduleSourcePath) { - moduleConfigPath = path.join(moduleSourcePath, 'module.yaml'); - } - } - - let configPath = null; - if (await fs.pathExists(moduleConfigPath)) { - configPath = moduleConfigPath; - } else { - // No config for this module - return; - } - - const configContent = await fs.readFile(configPath, 'utf8'); - const moduleConfig = yaml.parse(configContent); - - if (!moduleConfig) { - return; - } - - // Process each config item - const questions = []; - const staticAnswers = {}; - const configKeys = Object.keys(moduleConfig).filter((key) => key !== 'prompt'); - - for (const key of configKeys) { - const item = moduleConfig[key]; - - // Skip if not a config object - if (!item || typeof item !== 'object') { - continue; - } - - // Handle static values (no prompt, just result) - if (!item.prompt && item.result) { - // Add to static answers with a marker value - staticAnswers[`${moduleName}_${key}`] = undefined; - continue; - } - - // Handle interactive values (with prompt) - if (item.prompt) { - const question = await this.buildQuestion(moduleName, key, item, moduleConfig); - if (question) { - questions.push(question); - } - } - } - - // Collect all answers (static + prompted) - let allAnswers = { ...staticAnswers }; - - // If there are questions to ask, prompt for accepting defaults vs customizing - if (questions.length > 0) { - const moduleDisplayName = moduleConfig.header || `${moduleName.toUpperCase()} Module`; - - // Skip prompts mode: use all defaults without asking - if (this.skipPrompts) { - await prompts.log.info(`Using default configuration for ${moduleDisplayName}`); - // Use defaults for all questions - for (const question of questions) { - const hasDefault = question.default !== undefined && question.default !== null && question.default !== ''; - if (hasDefault && typeof question.default !== 'function') { - allAnswers[question.name] = question.default; - } - } - } else { - if (!this._silentConfig) await prompts.log.step(`Configuring ${moduleDisplayName}`); - let useDefaults = true; - if (moduleName === 'core') { - useDefaults = false; // Core: always show all questions - } else if (this.modulesToCustomize === undefined) { - // Fallback: original per-module confirm (backward compat for direct calls) - const customizeAnswer = await prompts.prompt([ - { - type: 'confirm', - name: 'customize', - message: 'Accept Defaults (no to customize)?', - default: true, - }, - ]); - useDefaults = customizeAnswer.customize; - } else { - // Batch mode: use defaults unless module was selected for customization - useDefaults = !this.modulesToCustomize.has(moduleName); - } - - if (useDefaults && moduleName !== 'core') { - // Accept defaults - only ask questions that have NO default value - const questionsWithoutDefaults = questions.filter((q) => q.default === undefined || q.default === null || q.default === ''); - - if (questionsWithoutDefaults.length > 0) { - await prompts.log.message(` Asking required questions for ${moduleName.toUpperCase()}...`); - const promptedAnswers = await prompts.prompt(questionsWithoutDefaults); - Object.assign(allAnswers, promptedAnswers); - } - - // For questions with defaults that weren't asked, we need to process them with their default values - const questionsWithDefaults = questions.filter((q) => q.default !== undefined && q.default !== null && q.default !== ''); - for (const question of questionsWithDefaults) { - // Skip function defaults - these are dynamic and will be evaluated later - if (typeof question.default === 'function') { - continue; - } - allAnswers[question.name] = question.default; - } - } else { - const promptedAnswers = await prompts.prompt(questions); - Object.assign(allAnswers, promptedAnswers); - } - } - } - - // Store all answers for cross-referencing - Object.assign(this.allAnswers, allAnswers); - - // Process all answers (both static and prompted) - // Always process if we have any answers or static answers - if (Object.keys(allAnswers).length > 0 || Object.keys(staticAnswers).length > 0) { - const answers = allAnswers; - - // Process answers and build result values - for (const key of Object.keys(answers)) { - const originalKey = key.replace(`${moduleName}_`, ''); - const item = moduleConfig[originalKey]; - const value = answers[key]; - - // Build the result using the template - let result; - - // For arrays (multi-select), handle differently - if (Array.isArray(value)) { - result = value; - } else if (item.result) { - result = item.result; - - // Replace placeholders only for strings - if (typeof result === 'string' && value !== undefined) { - // Replace {value} with the actual value - if (typeof value === 'string') { - result = result.replace('{value}', value); - } else if (typeof value === 'boolean' || typeof value === 'number') { - // For boolean and number values, if result is just "{value}", use the raw value - if (result === '{value}') { - result = value; - } else { - result = result.replace('{value}', value); - } - } else { - result = value; - } - - // Only do further replacements if result is still a string - if (typeof result === 'string') { - // Replace references to other config values - result = result.replaceAll(/{([^}]+)}/g, (match, configKey) => { - // Check if it's a special placeholder - if (configKey === 'project-root') { - return '{project-root}'; - } - - // Skip if it's the 'value' placeholder we already handled - if (configKey === 'value') { - return match; - } - - // Look for the config value across all modules - // First check if it's in the current module's answers - let configValue = answers[`${moduleName}_${configKey}`]; - - // Then check all answers (for cross-module references like outputFolder) - if (!configValue) { - // Try with various module prefixes - for (const [answerKey, answerValue] of Object.entries(this.allAnswers)) { - if (answerKey.endsWith(`_${configKey}`)) { - configValue = answerValue; - break; - } - } - } - - // Check in already collected config - if (!configValue) { - for (const mod of Object.keys(this.collectedConfig)) { - if (mod !== '_meta' && this.collectedConfig[mod] && this.collectedConfig[mod][configKey]) { - configValue = this.collectedConfig[mod][configKey]; - break; - } - } - } - - return configValue || match; - }); - } - } - } else { - result = value; - } - - // Store only the result value (no prompts, defaults, examples, etc.) - if (!this.collectedConfig[moduleName]) { - this.collectedConfig[moduleName] = {}; - } - this.collectedConfig[moduleName][originalKey] = result; - } - - // No longer display completion boxes - keep output clean - } else { - // No questions for this module - show completion message with header if available - const moduleDisplayName = moduleConfig.header || `${moduleName.toUpperCase()} Module`; - - // Check if this module has NO configuration keys at all (like CIS) - // Filter out metadata fields and only count actual config objects - const metadataFields = new Set(['code', 'name', 'header', 'subheader', 'default_selected']); - const actualConfigKeys = configKeys.filter((key) => !metadataFields.has(key)); - const hasNoConfig = actualConfigKeys.length === 0; - - if (!this._silentConfig) { - if (hasNoConfig && (moduleConfig.subheader || moduleConfig.header)) { - await prompts.log.step(moduleDisplayName); - if (moduleConfig.subheader) { - await prompts.log.message(` \u2713 ${moduleConfig.subheader}`); - } else { - await prompts.log.message(` \u2713 No custom configuration required`); - } - } else { - // Module has config but just no questions to ask - await prompts.log.message(` \u2713 ${moduleName.toUpperCase()} module configured`); - } - } - } - - // If we have no collected config for this module, but we have a module schema, - // ensure we have at least an empty object - if (!this.collectedConfig[moduleName]) { - this.collectedConfig[moduleName] = {}; - - // If we accepted defaults and have no answers, we still need to check - // if there are any static values in the schema that should be applied - if (moduleConfig) { - for (const key of Object.keys(moduleConfig)) { - if (key !== 'prompt' && moduleConfig[key] && typeof moduleConfig[key] === 'object') { - const item = moduleConfig[key]; - // For static items (no prompt, just result), apply the result - if (!item.prompt && item.result) { - // Apply any placeholder replacements to the result - let result = item.result; - if (typeof result === 'string') { - result = this.replacePlaceholders(result, moduleName, moduleConfig); - } - this.collectedConfig[moduleName][key] = result; - } - } - } - } - } - - await this.displayModulePostConfigNotes(moduleName, moduleConfig); - } - - /** - * Replace placeholders in a string with collected config values - * @param {string} str - String with placeholders - * @param {string} currentModule - Current module name (to look up defaults in same module) - * @param {Object} moduleConfig - Current module's config schema (to look up defaults) - * @returns {string} String with placeholders replaced - */ - replacePlaceholders(str, currentModule = null, moduleConfig = null) { - if (typeof str !== 'string') { - return str; - } - - return str.replaceAll(/{([^}]+)}/g, (match, configKey) => { - // Preserve special placeholders - if (configKey === 'project-root' || configKey === 'value' || configKey === 'directory_name') { - return match; - } - - // Look for the config value in allAnswers (already answered questions) - let configValue = this.allAnswers[configKey] || this.allAnswers[`core_${configKey}`]; - - // Check in already collected config - if (!configValue) { - for (const mod of Object.keys(this.collectedConfig)) { - if (mod !== '_meta' && this.collectedConfig[mod] && this.collectedConfig[mod][configKey]) { - configValue = this.collectedConfig[mod][configKey]; - break; - } - } - } - - // If still not found and we're in the same module, use the default from the config schema - if (!configValue && currentModule && moduleConfig && moduleConfig[configKey]) { - const referencedItem = moduleConfig[configKey]; - if (referencedItem && referencedItem.default !== undefined) { - configValue = referencedItem.default; - } - } - - return configValue || match; - }); - } - - /** - * Build a prompt question from a config item - * @param {string} moduleName - Module name - * @param {string} key - Config key - * @param {Object} item - Config item definition - * @param {Object} moduleConfig - Full module config schema (for resolving defaults) - */ - async buildQuestion(moduleName, key, item, moduleConfig = null) { - const questionName = `${moduleName}_${key}`; - - // Check for existing value - let existingValue = null; - if (this.existingConfig && this.existingConfig[moduleName]) { - existingValue = this.existingConfig[moduleName][key]; - - // Clean up existing value - remove {project-root}/ prefix if present - // This prevents duplication when the result template adds it back - if (typeof existingValue === 'string' && existingValue.startsWith('{project-root}/')) { - existingValue = existingValue.replace('{project-root}/', ''); - } - } - - // Special handling for user_name: default to system user - if (moduleName === 'core' && key === 'user_name' && !existingValue) { - item.default = this.getDefaultUsername(); - } - - // Determine question type and default value - let questionType = 'input'; - let defaultValue = item.default; - let choices = null; - - // Check if default contains references to other fields in the same module - const hasSameModuleReference = typeof defaultValue === 'string' && defaultValue.match(/{([^}]+)}/); - let dynamicDefault = false; - - // Replace placeholders in default value with collected config values - if (typeof defaultValue === 'string') { - if (defaultValue.includes('{directory_name}') && this.currentProjectDir) { - const dirName = path.basename(this.currentProjectDir); - defaultValue = defaultValue.replaceAll('{directory_name}', dirName); - } - - // Check if this references another field in the same module (for dynamic defaults) - if (hasSameModuleReference && moduleConfig) { - const matches = defaultValue.match(/{([^}]+)}/g); - if (matches) { - for (const match of matches) { - const fieldName = match.slice(1, -1); // Remove { } - // Check if this field exists in the same module config - if (moduleConfig[fieldName]) { - dynamicDefault = true; - break; - } - } - } - } - - // If not dynamic, replace placeholders now - if (!dynamicDefault) { - defaultValue = this.replacePlaceholders(defaultValue, moduleName, moduleConfig); - } - - // Strip {project-root}/ from defaults since it will be added back by result template - // This makes the display cleaner and user input simpler - if (defaultValue.includes('{project-root}/')) { - defaultValue = defaultValue.replace('{project-root}/', ''); - } - } - - // Handle different question types - if (item['single-select']) { - questionType = 'list'; - choices = item['single-select'].map((choice) => { - // If choice is an object with label and value - if (typeof choice === 'object' && choice.label && choice.value !== undefined) { - return { - name: choice.label, - value: choice.value, - }; - } - // Otherwise it's a simple string choice - return { - name: choice, - value: choice, - }; - }); - if (existingValue) { - defaultValue = existingValue; - } - } else if (item['multi-select']) { - questionType = 'checkbox'; - choices = item['multi-select'].map((choice) => { - // If choice is an object with label and value - if (typeof choice === 'object' && choice.label && choice.value !== undefined) { - return { - name: choice.label, - value: choice.value, - checked: existingValue - ? existingValue.includes(choice.value) - : item.default && Array.isArray(item.default) - ? item.default.includes(choice.value) - : false, - }; - } - // Otherwise it's a simple string choice - return { - name: choice, - value: choice, - checked: existingValue - ? existingValue.includes(choice) - : item.default && Array.isArray(item.default) - ? item.default.includes(choice) - : false, - }; - }); - } else if (typeof defaultValue === 'boolean') { - questionType = 'confirm'; - } - - // Build the prompt message - let message = ''; - - // Handle array prompts for multi-line messages - if (Array.isArray(item.prompt)) { - message = item.prompt.join('\n'); - } else { - message = item.prompt; - } - - // Replace placeholders in prompt message with collected config values - if (typeof message === 'string') { - message = this.replacePlaceholders(message, moduleName, moduleConfig); - } - - // Add current value indicator for existing configs - const color = await prompts.getColor(); - if (existingValue !== null && existingValue !== undefined) { - if (typeof existingValue === 'boolean') { - message += color.dim(` (current: ${existingValue ? 'true' : 'false'})`); - } else if (Array.isArray(existingValue)) { - message += color.dim(` (current: ${existingValue.join(', ')})`); - } else if (questionType !== 'list') { - // Show the cleaned value (without {project-root}/) for display - message += color.dim(` (current: ${existingValue})`); - } - } else if (item.example && questionType === 'input') { - // Show example for input fields - let exampleText = typeof item.example === 'string' ? item.example : JSON.stringify(item.example); - // Replace placeholders in example - if (typeof exampleText === 'string') { - exampleText = this.replacePlaceholders(exampleText, moduleName, moduleConfig); - exampleText = exampleText.replace('{project-root}/', ''); - } - message += color.dim(` (e.g., ${exampleText})`); - } - - // Build the question object - const question = { - type: questionType, - name: questionName, - message: message, - }; - - // Set default - if it's dynamic, use a function that the prompt will evaluate with current answers - // But if we have an existing value, always use that instead - if (existingValue !== null && existingValue !== undefined && questionType !== 'list') { - question.default = existingValue; - } else if (dynamicDefault && typeof item.default === 'string') { - const originalDefault = item.default; - question.default = (answers) => { - // Replace placeholders using answers from previous questions in the same batch - let resolved = originalDefault; - resolved = resolved.replaceAll(/{([^}]+)}/g, (match, fieldName) => { - // Look for the answer in the current batch (prefixed with module name) - const answerKey = `${moduleName}_${fieldName}`; - if (answers[answerKey] !== undefined) { - return answers[answerKey]; - } - // Fall back to collected config - return this.collectedConfig[moduleName]?.[fieldName] || match; - }); - // Strip {project-root}/ for cleaner display - if (resolved.includes('{project-root}/')) { - resolved = resolved.replace('{project-root}/', ''); - } - return resolved; - }; - } else { - question.default = defaultValue; - } - - // Add choices for select types - if (choices) { - question.choices = choices; - } - - // Add validation for input fields - if (questionType === 'input') { - question.validate = (input) => { - if (!input && item.required) { - return 'This field is required'; - } - // Validate against regex pattern if provided - if (input && item.regex) { - const regex = new RegExp(item.regex); - if (!regex.test(input)) { - return `Invalid format. Must match pattern: ${item.regex}`; - } - } - return true; - }; - } - - // Add validation for checkbox (multi-select) fields - if (questionType === 'checkbox' && item.required) { - question.validate = (answers) => { - if (!answers || answers.length === 0) { - return 'At least one option must be selected'; - } - return true; - }; - } - - return question; - } - - /** - * Display post-configuration notes for a module - * Shows prerequisite guidance based on collected config values - * Reads notes from the module's `post-install-notes` section in module.yaml - * Supports two formats: - * - Simple string: always displayed - * - Object keyed by config field name, with value-specific messages - * @param {string} moduleName - Module name - * @param {Object} moduleConfig - Parsed module.yaml content - */ - async displayModulePostConfigNotes(moduleName, moduleConfig) { - if (this._silentConfig) return; - if (!moduleConfig || !moduleConfig['post-install-notes']) return; - - const notes = moduleConfig['post-install-notes']; - const color = await prompts.getColor(); - - // Format 1: Simple string - always display - if (typeof notes === 'string') { - await prompts.log.message(''); - for (const line of notes.trim().split('\n')) { - await prompts.log.message(color.dim(line)); - } - return; - } - - // Format 2: Conditional on config values - if (typeof notes === 'object') { - const config = this.collectedConfig[moduleName]; - if (!config) return; - - let hasOutput = false; - for (const [configKey, valueMessages] of Object.entries(notes)) { - const selectedValue = config[configKey]; - if (!selectedValue || !valueMessages[selectedValue]) continue; - - if (hasOutput) await prompts.log.message(''); - hasOutput = true; - - const message = valueMessages[selectedValue]; - for (const line of message.trim().split('\n')) { - const trimmedLine = line.trim(); - if (trimmedLine.endsWith(':') && !trimmedLine.startsWith(' ')) { - await prompts.log.info(color.bold(trimmedLine)); - } else { - await prompts.log.message(color.dim(' ' + trimmedLine)); - } - } - } - } - } - - /** - * Deep merge two objects - * @param {Object} target - Target object - * @param {Object} source - Source object - */ - deepMerge(target, source) { - const result = { ...target }; - - for (const key in source) { - if (source[key] && typeof source[key] === 'object' && !Array.isArray(source[key])) { - if (result[key] && typeof result[key] === 'object' && !Array.isArray(result[key])) { - result[key] = this.deepMerge(result[key], source[key]); - } else { - result[key] = source[key]; - } - } else { - result[key] = source[key]; - } - } - - return result; - } -} - -module.exports = { ConfigCollector }; diff --git a/tools/cli/installers/lib/core/custom-module-cache.js b/tools/cli/installers/lib/core/custom-module-cache.js deleted file mode 100644 index b1cc3d0f7..000000000 --- a/tools/cli/installers/lib/core/custom-module-cache.js +++ /dev/null @@ -1,260 +0,0 @@ -/** - * Custom Module Source Cache - * Caches custom module sources under _config/custom/ to ensure they're never lost - * and can be checked into source control - */ - -const fs = require('fs-extra'); -const path = require('node:path'); -const crypto = require('node:crypto'); -const prompts = require('../../../lib/prompts'); - -class CustomModuleCache { - constructor(bmadDir) { - this.bmadDir = bmadDir; - this.customCacheDir = path.join(bmadDir, '_config', 'custom'); - this.manifestPath = path.join(this.customCacheDir, 'cache-manifest.yaml'); - } - - /** - * Ensure the custom cache directory exists - */ - async ensureCacheDir() { - await fs.ensureDir(this.customCacheDir); - } - - /** - * Get cache manifest - */ - async getCacheManifest() { - if (!(await fs.pathExists(this.manifestPath))) { - return {}; - } - - const content = await fs.readFile(this.manifestPath, 'utf8'); - const yaml = require('yaml'); - return yaml.parse(content) || {}; - } - - /** - * Update cache manifest - */ - async updateCacheManifest(manifest) { - const yaml = require('yaml'); - // Clean the manifest to remove any non-serializable values - const cleanManifest = structuredClone(manifest); - - const content = yaml.stringify(cleanManifest, { - indent: 2, - lineWidth: 0, - sortKeys: false, - }); - - await fs.writeFile(this.manifestPath, content); - } - - /** - * Stream a file into the hash to avoid loading entire file into memory - */ - async hashFileStream(filePath, hash) { - return new Promise((resolve, reject) => { - const stream = require('node:fs').createReadStream(filePath); - stream.on('data', (chunk) => hash.update(chunk)); - stream.on('end', resolve); - stream.on('error', reject); - }); - } - - /** - * Calculate hash of a file or directory using streaming to minimize memory usage - */ - async calculateHash(sourcePath) { - const hash = crypto.createHash('sha256'); - - const isDir = (await fs.stat(sourcePath)).isDirectory(); - - if (isDir) { - // For directories, hash all files - const files = []; - async function collectFiles(dir) { - const entries = await fs.readdir(dir, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isFile()) { - files.push(path.join(dir, entry.name)); - } else if (entry.isDirectory() && !entry.name.startsWith('.')) { - await collectFiles(path.join(dir, entry.name)); - } - } - } - - await collectFiles(sourcePath); - files.sort(); // Ensure consistent order - - for (const file of files) { - const relativePath = path.relative(sourcePath, file); - // Hash the path first, then stream file contents - hash.update(relativePath + '|'); - await this.hashFileStream(file, hash); - } - } else { - // For single files, stream directly into hash - await this.hashFileStream(sourcePath, hash); - } - - return hash.digest('hex'); - } - - /** - * Cache a custom module source - * @param {string} moduleId - Module ID - * @param {string} sourcePath - Original source path - * @param {Object} metadata - Additional metadata to store - * @returns {Object} Cached module info - */ - async cacheModule(moduleId, sourcePath, metadata = {}) { - await this.ensureCacheDir(); - - const cacheDir = path.join(this.customCacheDir, moduleId); - const cacheManifest = await this.getCacheManifest(); - - // Check if already cached and unchanged - if (cacheManifest[moduleId]) { - const cached = cacheManifest[moduleId]; - if (cached.originalHash && cached.originalHash === (await this.calculateHash(sourcePath))) { - // Source unchanged, return existing cache info - return { - moduleId, - cachePath: cacheDir, - ...cached, - }; - } - } - - // Remove existing cache if it exists - if (await fs.pathExists(cacheDir)) { - await fs.remove(cacheDir); - } - - // Copy module to cache - await fs.copy(sourcePath, cacheDir, { - filter: (src) => { - const relative = path.relative(sourcePath, src); - // Skip node_modules, .git, and other common ignore patterns - return !relative.includes('node_modules') && !relative.startsWith('.git') && !relative.startsWith('.DS_Store'); - }, - }); - - // Calculate hash of the source - const sourceHash = await this.calculateHash(sourcePath); - const cacheHash = await this.calculateHash(cacheDir); - - // Update manifest - don't store absolute paths for portability - // Clean metadata to remove absolute paths - const cleanMetadata = { ...metadata }; - if (cleanMetadata.sourcePath) { - delete cleanMetadata.sourcePath; - } - - cacheManifest[moduleId] = { - originalHash: sourceHash, - cacheHash: cacheHash, - cachedAt: new Date().toISOString(), - ...cleanMetadata, - }; - - await this.updateCacheManifest(cacheManifest); - - return { - moduleId, - cachePath: cacheDir, - ...cacheManifest[moduleId], - }; - } - - /** - * Get cached module info - * @param {string} moduleId - Module ID - * @returns {Object|null} Cached module info or null - */ - async getCachedModule(moduleId) { - const cacheManifest = await this.getCacheManifest(); - const cached = cacheManifest[moduleId]; - - if (!cached) { - return null; - } - - const cacheDir = path.join(this.customCacheDir, moduleId); - - if (!(await fs.pathExists(cacheDir))) { - // Cache dir missing, remove from manifest - delete cacheManifest[moduleId]; - await this.updateCacheManifest(cacheManifest); - return null; - } - - // Verify cache integrity - const currentCacheHash = await this.calculateHash(cacheDir); - if (currentCacheHash !== cached.cacheHash) { - await prompts.log.warn(`Cache integrity check failed for ${moduleId}`); - } - - return { - moduleId, - cachePath: cacheDir, - ...cached, - }; - } - - /** - * Get all cached modules - * @returns {Array} Array of cached module info - */ - async getAllCachedModules() { - const cacheManifest = await this.getCacheManifest(); - const cached = []; - - for (const [moduleId, info] of Object.entries(cacheManifest)) { - const cachedModule = await this.getCachedModule(moduleId); - if (cachedModule) { - cached.push(cachedModule); - } - } - - return cached; - } - - /** - * Remove a cached module - * @param {string} moduleId - Module ID to remove - */ - async removeCachedModule(moduleId) { - const cacheManifest = await this.getCacheManifest(); - const cacheDir = path.join(this.customCacheDir, moduleId); - - // Remove cache directory - if (await fs.pathExists(cacheDir)) { - await fs.remove(cacheDir); - } - - // Remove from manifest - delete cacheManifest[moduleId]; - await this.updateCacheManifest(cacheManifest); - } - - /** - * Sync cached modules with a list of module IDs - * @param {Array} moduleIds - Module IDs to keep - */ - async syncCache(moduleIds) { - const cached = await this.getAllCachedModules(); - - for (const cachedModule of cached) { - if (!moduleIds.includes(cachedModule.moduleId)) { - await this.removeCachedModule(cachedModule.moduleId); - } - } - } -} - -module.exports = { CustomModuleCache }; diff --git a/tools/cli/installers/lib/core/dependency-resolver.js b/tools/cli/installers/lib/core/dependency-resolver.js deleted file mode 100644 index 3fb282c5d..000000000 --- a/tools/cli/installers/lib/core/dependency-resolver.js +++ /dev/null @@ -1,743 +0,0 @@ -const fs = require('fs-extra'); -const path = require('node:path'); -const glob = require('glob'); -const yaml = require('yaml'); -const prompts = require('../../../lib/prompts'); - -/** - * Dependency Resolver for BMAD modules - * Handles cross-module dependencies and ensures all required files are included - */ -class DependencyResolver { - constructor() { - this.dependencies = new Map(); - this.resolvedFiles = new Set(); - this.missingDependencies = new Set(); - } - - /** - * Resolve all dependencies for selected modules - * @param {string} bmadDir - BMAD installation directory - * @param {Array} selectedModules - Modules explicitly selected by user - * @param {Object} options - Resolution options - * @returns {Object} Resolution results with all required files - */ - async resolve(bmadDir, selectedModules = [], options = {}) { - if (options.verbose) { - await prompts.log.info('Resolving module dependencies...'); - } - - // Always include core as base - const modulesToProcess = new Set(['core', ...selectedModules]); - - // First pass: collect all explicitly selected files - const primaryFiles = await this.collectPrimaryFiles(bmadDir, modulesToProcess, options); - - // Second pass: parse and resolve dependencies - const allDependencies = await this.parseDependencies(primaryFiles); - - // Third pass: resolve dependency paths and collect files - const resolvedDeps = await this.resolveDependencyPaths(bmadDir, allDependencies); - - // Fourth pass: check for transitive dependencies - const transitiveDeps = await this.resolveTransitiveDependencies(bmadDir, resolvedDeps); - - // Combine all files - const allFiles = new Set([...primaryFiles.map((f) => f.path), ...resolvedDeps, ...transitiveDeps]); - - // Organize by module - const organizedFiles = this.organizeByModule(bmadDir, allFiles); - - // Report results (only in verbose mode) - if (options.verbose) { - await this.reportResults(organizedFiles, selectedModules); - } - - return { - primaryFiles, - dependencies: resolvedDeps, - transitiveDependencies: transitiveDeps, - allFiles: [...allFiles], - byModule: organizedFiles, - missing: [...this.missingDependencies], - }; - } - - /** - * Collect primary files from selected modules - */ - async collectPrimaryFiles(bmadDir, modules, options = {}) { - const files = []; - const { moduleManager } = options; - - for (const module of modules) { - // Skip external modules - they're installed from cache, not from source - if (moduleManager && (await moduleManager.isExternalModule(module))) { - continue; - } - - // Handle both source (src/) and installed (bmad/) directory structures - let moduleDir; - - // Check if this is a source directory (has 'src' subdirectory) - const srcDir = path.join(bmadDir, 'src'); - if (await fs.pathExists(srcDir)) { - // Source directory structure: src/core or src/bmm - if (module === 'core') { - moduleDir = path.join(srcDir, 'core'); - } else if (module === 'bmm') { - moduleDir = path.join(srcDir, 'bmm'); - } - } - - if (!moduleDir) { - continue; - } - - if (!(await fs.pathExists(moduleDir))) { - await prompts.log.warn('Module directory not found: ' + moduleDir); - continue; - } - - // Collect agents - const agentsDir = path.join(moduleDir, 'agents'); - if (await fs.pathExists(agentsDir)) { - const agentFiles = await glob.glob('*.md', { cwd: agentsDir }); - for (const file of agentFiles) { - const agentPath = path.join(agentsDir, file); - - // Check for localskip attribute - const content = await fs.readFile(agentPath, 'utf8'); - const hasLocalSkip = content.match(/]*\slocalskip="true"[^>]*>/); - if (hasLocalSkip) { - continue; // Skip agents marked for web-only - } - - files.push({ - path: agentPath, - type: 'agent', - module, - name: path.basename(file, '.md'), - }); - } - } - - // Collect tasks - const tasksDir = path.join(moduleDir, 'tasks'); - if (await fs.pathExists(tasksDir)) { - const taskFiles = await glob.glob('*.md', { cwd: tasksDir }); - for (const file of taskFiles) { - files.push({ - path: path.join(tasksDir, file), - type: 'task', - module, - name: path.basename(file, '.md'), - }); - } - } - } - - return files; - } - - /** - * Parse dependencies from file content - */ - async parseDependencies(files) { - const allDeps = new Set(); - - for (const file of files) { - const content = await fs.readFile(file.path, 'utf8'); - - // Parse YAML frontmatter for explicit dependencies - const frontmatterMatch = content.match(/^---\r?\n([\s\S]*?)\r?\n---/); - if (frontmatterMatch) { - try { - // Pre-process to handle backticks in YAML values - let yamlContent = frontmatterMatch[1]; - // Quote values with backticks to make them valid YAML - yamlContent = yamlContent.replaceAll(/: `([^`]+)`/g, ': "$1"'); - - const frontmatter = yaml.parse(yamlContent); - if (frontmatter.dependencies) { - const deps = Array.isArray(frontmatter.dependencies) ? frontmatter.dependencies : [frontmatter.dependencies]; - - for (const dep of deps) { - allDeps.add({ - from: file.path, - dependency: dep, - type: 'explicit', - }); - } - } - - // Check for template dependencies - if (frontmatter.template) { - const templates = Array.isArray(frontmatter.template) ? frontmatter.template : [frontmatter.template]; - for (const template of templates) { - allDeps.add({ - from: file.path, - dependency: template, - type: 'template', - }); - } - } - } catch (error) { - await prompts.log.warn('Failed to parse frontmatter in ' + file.name + ': ' + error.message); - } - } - - // Parse content for command references (cross-module dependencies) - const commandRefs = this.parseCommandReferences(content); - for (const ref of commandRefs) { - allDeps.add({ - from: file.path, - dependency: ref, - type: 'command', - }); - } - - // Parse for file path references - const fileRefs = this.parseFileReferences(content); - for (const ref of fileRefs) { - // Determine type based on path format - // Paths starting with bmad/ are absolute references to the bmad installation - const depType = ref.startsWith('bmad/') ? 'bmad-path' : 'file'; - allDeps.add({ - from: file.path, - dependency: ref, - type: depType, - }); - } - } - - return allDeps; - } - - /** - * Parse command references from content - */ - parseCommandReferences(content) { - const refs = new Set(); - - // Match @task-{name} or @agent-{name} or @{module}-{type}-{name} - const commandPattern = /@(task-|agent-|bmad-)([a-z0-9-]+)/g; - let match; - - while ((match = commandPattern.exec(content)) !== null) { - refs.add(match[0]); - } - - // Match file paths like bmad/core/agents/analyst - const pathPattern = /bmad\/(core|bmm|cis)\/(agents|tasks)\/([a-z0-9-]+)/g; - - while ((match = pathPattern.exec(content)) !== null) { - refs.add(match[0]); - } - - return [...refs]; - } - - /** - * Parse file path references from content - */ - parseFileReferences(content) { - const refs = new Set(); - - // Match relative paths like ../templates/file.yaml or ./data/file.md - const relativePattern = /['"](\.\.?\/[^'"]+\.(md|yaml|yml|xml|json|txt|csv))['"]/g; - let match; - - while ((match = relativePattern.exec(content)) !== null) { - refs.add(match[1]); - } - - // Parse exec attributes in command tags - const execPattern = /exec="([^"]+)"/g; - while ((match = execPattern.exec(content)) !== null) { - let execPath = match[1]; - if (execPath && execPath !== '*') { - // Remove {project-root} prefix to get the actual path - // Usage is like {project-root}/bmad/core/tasks/foo.md - if (execPath.includes('{project-root}')) { - execPath = execPath.replace('{project-root}', ''); - } - refs.add(execPath); - } - } - - // Parse tmpl attributes in command tags - const tmplPattern = /tmpl="([^"]+)"/g; - while ((match = tmplPattern.exec(content)) !== null) { - let tmplPath = match[1]; - if (tmplPath && tmplPath !== '*') { - // Remove {project-root} prefix to get the actual path - // Usage is like {project-root}/bmad/core/tasks/foo.md - if (tmplPath.includes('{project-root}')) { - tmplPath = tmplPath.replace('{project-root}', ''); - } - refs.add(tmplPath); - } - } - - return [...refs]; - } - - /** - * Resolve dependency paths to actual files - */ - async resolveDependencyPaths(bmadDir, dependencies) { - const resolved = new Set(); - - for (const dep of dependencies) { - const resolvedPaths = await this.resolveSingleDependency(bmadDir, dep); - for (const path of resolvedPaths) { - resolved.add(path); - } - } - - return resolved; - } - - /** - * Resolve a single dependency to file paths - */ - async resolveSingleDependency(bmadDir, dep) { - const paths = []; - - switch (dep.type) { - case 'explicit': - case 'file': { - let depPath = dep.dependency; - - // Handle {project-root} prefix if present - if (depPath.includes('{project-root}')) { - // Remove {project-root} and resolve as bmad path - depPath = depPath.replace('{project-root}', ''); - - if (depPath.startsWith('bmad/')) { - const bmadPath = depPath.replace(/^bmad\//, ''); - - // Handle glob patterns - if (depPath.includes('*')) { - // Extract the base path and pattern - const pathParts = bmadPath.split('/'); - const module = pathParts[0]; - const filePattern = pathParts.at(-1); - const middlePath = pathParts.slice(1, -1).join('/'); - - let basePath; - if (module === 'core') { - basePath = path.join(bmadDir, 'core', middlePath); - } else { - basePath = path.join(bmadDir, 'modules', module, middlePath); - } - - if (await fs.pathExists(basePath)) { - const files = await glob.glob(filePattern, { cwd: basePath }); - for (const file of files) { - paths.push(path.join(basePath, file)); - } - } - } else { - // Direct path - if (bmadPath.startsWith('core/')) { - const corePath = path.join(bmadDir, bmadPath); - if (await fs.pathExists(corePath)) { - paths.push(corePath); - } - } else { - const parts = bmadPath.split('/'); - const module = parts[0]; - const rest = parts.slice(1).join('/'); - const modulePath = path.join(bmadDir, 'modules', module, rest); - - if (await fs.pathExists(modulePath)) { - paths.push(modulePath); - } - } - } - } - } else { - // Regular relative path handling - const sourceDir = path.dirname(dep.from); - - // Handle glob patterns - if (depPath.includes('*')) { - const basePath = path.resolve(sourceDir, path.dirname(depPath)); - const pattern = path.basename(depPath); - - if (await fs.pathExists(basePath)) { - const files = await glob.glob(pattern, { cwd: basePath }); - for (const file of files) { - paths.push(path.join(basePath, file)); - } - } - } else { - // Direct file reference - const fullPath = path.resolve(sourceDir, depPath); - if (await fs.pathExists(fullPath)) { - paths.push(fullPath); - } else { - this.missingDependencies.add(`${depPath} (referenced by ${path.basename(dep.from)})`); - } - } - } - - break; - } - case 'command': { - // Resolve command references to actual files - const commandPath = await this.resolveCommandToPath(bmadDir, dep.dependency); - if (commandPath) { - paths.push(commandPath); - } - - break; - } - case 'bmad-path': { - // Resolve bmad/ paths (from {project-root}/bmad/... references) - // These are paths relative to the src directory structure - const bmadPath = dep.dependency.replace(/^bmad\//, ''); - - // Try to resolve as if it's in src structure - // bmad/core/tasks/foo.md -> src/core/tasks/foo.md - // bmad/bmm/tasks/bar.md -> src/bmm/tasks/bar.md (bmm is directly under src/) - // bmad/cis/agents/bar.md -> src/modules/cis/agents/bar.md - - if (bmadPath.startsWith('core/')) { - const corePath = path.join(bmadDir, bmadPath); - if (await fs.pathExists(corePath)) { - paths.push(corePath); - } else { - // Not found, but don't report as missing since it might be installed later - } - } else { - // It's a module path like bmm/tasks/foo.md or cis/agents/bar.md - const parts = bmadPath.split('/'); - const module = parts[0]; - const rest = parts.slice(1).join('/'); - let modulePath; - if (module === 'bmm') { - // bmm is directly under src/ - modulePath = path.join(bmadDir, module, rest); - } else { - // Other modules are under modules/ - modulePath = path.join(bmadDir, 'modules', module, rest); - } - - if (await fs.pathExists(modulePath)) { - paths.push(modulePath); - } else { - // Not found, but don't report as missing since it might be installed later - } - } - - break; - } - case 'template': { - // Resolve template references - let templateDep = dep.dependency; - - // Handle {project-root} prefix if present - if (templateDep.includes('{project-root}')) { - // Remove {project-root} and treat as bmad-path - templateDep = templateDep.replace('{project-root}', ''); - - // Now resolve as a bmad path - if (templateDep.startsWith('bmad/')) { - const bmadPath = templateDep.replace(/^bmad\//, ''); - - if (bmadPath.startsWith('core/')) { - const corePath = path.join(bmadDir, bmadPath); - if (await fs.pathExists(corePath)) { - paths.push(corePath); - } - } else { - // Module path like cis/templates/brainstorm.md - const parts = bmadPath.split('/'); - const module = parts[0]; - const rest = parts.slice(1).join('/'); - const modulePath = path.join(bmadDir, 'modules', module, rest); - - if (await fs.pathExists(modulePath)) { - paths.push(modulePath); - } - } - } - } else { - // Regular relative template path - const sourceDir = path.dirname(dep.from); - const templatePath = path.resolve(sourceDir, templateDep); - - if (await fs.pathExists(templatePath)) { - paths.push(templatePath); - } else { - this.missingDependencies.add(`Template: ${dep.dependency}`); - } - } - - break; - } - // No default - } - - return paths; - } - - /** - * Resolve command reference to file path - */ - async resolveCommandToPath(bmadDir, command) { - // Parse command format: @task-name or @agent-name or bmad/module/type/name - - if (command.startsWith('@task-')) { - const taskName = command.slice(6); - // Search all modules for this task - for (const module of ['core', 'bmm', 'cis']) { - const taskPath = - module === 'core' - ? path.join(bmadDir, 'core', 'tasks', `${taskName}.md`) - : path.join(bmadDir, 'modules', module, 'tasks', `${taskName}.md`); - if (await fs.pathExists(taskPath)) { - return taskPath; - } - } - } else if (command.startsWith('@agent-')) { - const agentName = command.slice(7); - // Search all modules for this agent - for (const module of ['core', 'bmm', 'cis']) { - const agentPath = - module === 'core' - ? path.join(bmadDir, 'core', 'agents', `${agentName}.md`) - : path.join(bmadDir, 'modules', module, 'agents', `${agentName}.md`); - if (await fs.pathExists(agentPath)) { - return agentPath; - } - } - } else if (command.startsWith('bmad/')) { - // Direct path reference - const parts = command.split('/'); - if (parts.length >= 4) { - const [, module, type, ...nameParts] = parts; - const name = nameParts.join('/'); // Handle nested paths - - // Check if name already has extension - const fileName = name.endsWith('.md') ? name : `${name}.md`; - - const filePath = - module === 'core' ? path.join(bmadDir, 'core', type, fileName) : path.join(bmadDir, 'modules', module, type, fileName); - if (await fs.pathExists(filePath)) { - return filePath; - } - } - } - - // Don't report as missing if it's a self-reference within the module being installed - if (!command.includes('cis') || command.includes('brain')) { - // Only report missing if it's a true external dependency - // this.missingDependencies.add(`Command: ${command}`); - } - return null; - } - - /** - * Resolve transitive dependencies (dependencies of dependencies) - */ - async resolveTransitiveDependencies(bmadDir, directDeps) { - const transitive = new Set(); - const processed = new Set(); - - // Process each direct dependency - for (const depPath of directDeps) { - if (processed.has(depPath)) continue; - processed.add(depPath); - - // Only process markdown and YAML files for transitive deps - if ((depPath.endsWith('.md') || depPath.endsWith('.yaml') || depPath.endsWith('.yml')) && (await fs.pathExists(depPath))) { - const content = await fs.readFile(depPath, 'utf8'); - const subDeps = await this.parseDependencies([ - { - path: depPath, - type: 'dependency', - module: this.getModuleFromPath(bmadDir, depPath), - name: path.basename(depPath), - }, - ]); - - const resolvedSubDeps = await this.resolveDependencyPaths(bmadDir, subDeps); - for (const subDep of resolvedSubDeps) { - if (!directDeps.has(subDep)) { - transitive.add(subDep); - } - } - } - } - - return transitive; - } - - /** - * Get module name from file path - */ - getModuleFromPath(bmadDir, filePath) { - const relative = path.relative(bmadDir, filePath); - const parts = relative.split(path.sep); - - // Handle source directory structure (src/core, src/bmm, or src/modules/xxx) - if (parts[0] === 'src') { - if (parts[1] === 'core') { - return 'core'; - } else if (parts[1] === 'bmm') { - return 'bmm'; - } else if (parts[1] === 'modules' && parts.length > 2) { - return parts[2]; - } - } - - // Check if it's in modules directory (installed structure) - if (parts[0] === 'modules' && parts.length > 1) { - return parts[1]; - } - - // Otherwise return the first part (core, etc.) - // But don't return 'src' as a module name - if (parts[0] === 'src') { - return 'unknown'; - } - return parts[0] || 'unknown'; - } - - /** - * Organize files by module - */ - organizeByModule(bmadDir, files) { - const organized = {}; - - for (const file of files) { - const module = this.getModuleFromPath(bmadDir, file); - if (!organized[module]) { - organized[module] = { - agents: [], - tasks: [], - tools: [], - templates: [], - data: [], - other: [], - }; - } - - // Get relative path correctly based on module structure - let moduleBase; - - // Check if file is in source directory structure - if (file.includes('/src/core/') || file.includes('/src/bmm/')) { - if (module === 'core') { - moduleBase = path.join(bmadDir, 'src', 'core'); - } else if (module === 'bmm') { - moduleBase = path.join(bmadDir, 'src', 'bmm'); - } - } else { - moduleBase = module === 'core' ? path.join(bmadDir, 'core') : path.join(bmadDir, 'modules', module); - } - - const relative = path.relative(moduleBase, file); - - if (relative.startsWith('agents/') || file.includes('/agents/')) { - organized[module].agents.push(file); - } else if (relative.startsWith('tasks/') || file.includes('/tasks/')) { - organized[module].tasks.push(file); - } else if (relative.startsWith('tools/') || file.includes('/tools/')) { - organized[module].tools.push(file); - } else if (relative.includes('data/')) { - organized[module].data.push(file); - } else { - organized[module].other.push(file); - } - } - - return organized; - } - - /** - * Report resolution results - */ - async reportResults(organized, selectedModules) { - await prompts.log.success('Dependency resolution complete'); - - for (const [module, files] of Object.entries(organized)) { - const isSelected = selectedModules.includes(module) || module === 'core'; - const totalFiles = - files.agents.length + files.tasks.length + files.tools.length + files.templates.length + files.data.length + files.other.length; - - if (totalFiles > 0) { - await prompts.log.info(` ${module.toUpperCase()} module:`); - await prompts.log.message(` Status: ${isSelected ? 'Selected' : 'Dependencies only'}`); - - if (files.agents.length > 0) { - await prompts.log.message(` Agents: ${files.agents.length}`); - } - if (files.tasks.length > 0) { - await prompts.log.message(` Tasks: ${files.tasks.length}`); - } - if (files.templates.length > 0) { - await prompts.log.message(` Templates: ${files.templates.length}`); - } - if (files.data.length > 0) { - await prompts.log.message(` Data files: ${files.data.length}`); - } - if (files.other.length > 0) { - await prompts.log.message(` Other files: ${files.other.length}`); - } - } - } - - if (this.missingDependencies.size > 0) { - await prompts.log.warn('Missing dependencies:'); - for (const missing of this.missingDependencies) { - await prompts.log.warn(` - ${missing}`); - } - } - } - - /** - * Create a bundle for web deployment - * @param {Object} resolution - Resolution results from resolve() - * @returns {Object} Bundle data ready for web - */ - async createWebBundle(resolution) { - const bundle = { - metadata: { - created: new Date().toISOString(), - modules: Object.keys(resolution.byModule), - totalFiles: resolution.allFiles.length, - }, - agents: {}, - tasks: {}, - templates: {}, - data: {}, - }; - - // Bundle all files by type - for (const filePath of resolution.allFiles) { - if (!(await fs.pathExists(filePath))) continue; - - const content = await fs.readFile(filePath, 'utf8'); - const relative = path.relative(path.dirname(resolution.primaryFiles[0]?.path || '.'), filePath); - - if (filePath.includes('/agents/')) { - bundle.agents[relative] = content; - } else if (filePath.includes('/tasks/')) { - bundle.tasks[relative] = content; - } else if (filePath.includes('template')) { - bundle.templates[relative] = content; - } else { - bundle.data[relative] = content; - } - } - - return bundle; - } -} - -module.exports = { DependencyResolver }; diff --git a/tools/cli/installers/lib/core/detector.js b/tools/cli/installers/lib/core/detector.js deleted file mode 100644 index 9bb736589..000000000 --- a/tools/cli/installers/lib/core/detector.js +++ /dev/null @@ -1,223 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const yaml = require('yaml'); -const { Manifest } = require('./manifest'); - -class Detector { - /** - * Detect existing BMAD installation - * @param {string} bmadDir - Path to bmad directory - * @returns {Object} Installation status and details - */ - async detect(bmadDir) { - const result = { - installed: false, - path: bmadDir, - version: null, - hasCore: false, - modules: [], - ides: [], - customModules: [], - manifest: null, - }; - - // Check if bmad directory exists - if (!(await fs.pathExists(bmadDir))) { - return result; - } - - // Check for manifest using the Manifest class - const manifest = new Manifest(); - const manifestData = await manifest.read(bmadDir); - if (manifestData) { - result.manifest = manifestData; - result.version = manifestData.version; - result.installed = true; - // Copy custom modules if they exist - if (manifestData.customModules) { - result.customModules = manifestData.customModules; - } - } - - // Check for core - const corePath = path.join(bmadDir, 'core'); - if (await fs.pathExists(corePath)) { - result.hasCore = true; - - // Try to get core version from config - const coreConfigPath = path.join(corePath, 'config.yaml'); - if (await fs.pathExists(coreConfigPath)) { - try { - const configContent = await fs.readFile(coreConfigPath, 'utf8'); - const config = yaml.parse(configContent); - if (!result.version && config.version) { - result.version = config.version; - } - } catch { - // Ignore config read errors - } - } - } - - // Check for modules - // If manifest exists, use it as the source of truth for installed modules - // Otherwise fall back to directory scanning (legacy installations) - if (manifestData && manifestData.modules && manifestData.modules.length > 0) { - // Use manifest module list - these are officially installed modules - for (const moduleId of manifestData.modules) { - const modulePath = path.join(bmadDir, moduleId); - const moduleConfigPath = path.join(modulePath, 'config.yaml'); - - const moduleInfo = { - id: moduleId, - path: modulePath, - version: 'unknown', - }; - - if (await fs.pathExists(moduleConfigPath)) { - try { - const configContent = await fs.readFile(moduleConfigPath, 'utf8'); - const config = yaml.parse(configContent); - moduleInfo.version = config.version || 'unknown'; - moduleInfo.name = config.name || moduleId; - moduleInfo.description = config.description; - } catch { - // Ignore config read errors - } - } - - result.modules.push(moduleInfo); - } - } else { - // Fallback: scan directory for modules (legacy installations without manifest) - const entries = await fs.readdir(bmadDir, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isDirectory() && entry.name !== 'core' && entry.name !== '_config') { - const modulePath = path.join(bmadDir, entry.name); - const moduleConfigPath = path.join(modulePath, 'config.yaml'); - - // Only treat it as a module if it has a config.yaml - if (await fs.pathExists(moduleConfigPath)) { - const moduleInfo = { - id: entry.name, - path: modulePath, - version: 'unknown', - }; - - try { - const configContent = await fs.readFile(moduleConfigPath, 'utf8'); - const config = yaml.parse(configContent); - moduleInfo.version = config.version || 'unknown'; - moduleInfo.name = config.name || entry.name; - moduleInfo.description = config.description; - } catch { - // Ignore config read errors - } - - result.modules.push(moduleInfo); - } - } - } - } - - // Check for IDE configurations from manifest - if (result.manifest && result.manifest.ides) { - // Filter out any undefined/null values - result.ides = result.manifest.ides.filter((ide) => ide && typeof ide === 'string'); - } - - // Mark as installed if we found core or modules - if (result.hasCore || result.modules.length > 0) { - result.installed = true; - } - - return result; - } - - /** - * Detect legacy installation (_bmad-method, .bmm, .cis) - * @param {string} projectDir - Project directory to check - * @returns {Object} Legacy installation details - */ - async detectLegacy(projectDir) { - const result = { - hasLegacy: false, - legacyCore: false, - legacyModules: [], - paths: [], - }; - - // Check for legacy core (_bmad-method) - const legacyCorePath = path.join(projectDir, '_bmad-method'); - if (await fs.pathExists(legacyCorePath)) { - result.hasLegacy = true; - result.legacyCore = true; - result.paths.push(legacyCorePath); - } - - // Check for legacy modules (directories starting with .) - const entries = await fs.readdir(projectDir, { withFileTypes: true }); - for (const entry of entries) { - if ( - entry.isDirectory() && - entry.name.startsWith('.') && - entry.name !== '_bmad-method' && - !entry.name.startsWith('.git') && - !entry.name.startsWith('.vscode') && - !entry.name.startsWith('.idea') - ) { - const modulePath = path.join(projectDir, entry.name); - const moduleManifestPath = path.join(modulePath, 'install-manifest.yaml'); - - // Check if it's likely a BMAD module - if ((await fs.pathExists(moduleManifestPath)) || (await fs.pathExists(path.join(modulePath, 'config.yaml')))) { - result.hasLegacy = true; - result.legacyModules.push({ - name: entry.name.slice(1), // Remove leading dot - path: modulePath, - }); - result.paths.push(modulePath); - } - } - } - - return result; - } - - /** - * Check if migration from legacy is needed - * @param {string} projectDir - Project directory - * @returns {Object} Migration requirements - */ - async checkMigrationNeeded(projectDir) { - const bmadDir = path.join(projectDir, 'bmad'); - const current = await this.detect(bmadDir); - const legacy = await this.detectLegacy(projectDir); - - return { - needed: legacy.hasLegacy && !current.installed, - canMigrate: legacy.hasLegacy, - legacy: legacy, - current: current, - }; - } - - /** - * Detect legacy BMAD v4 .bmad-method folder - * @param {string} projectDir - Project directory to check - * @returns {{ hasLegacyV4: boolean, offenders: string[] }} - */ - async detectLegacyV4(projectDir) { - const offenders = []; - - // Check for .bmad-method folder - const bmadMethodPath = path.join(projectDir, '.bmad-method'); - if (await fs.pathExists(bmadMethodPath)) { - offenders.push(bmadMethodPath); - } - - return { hasLegacyV4: offenders.length > 0, offenders }; - } -} - -module.exports = { Detector }; diff --git a/tools/cli/installers/lib/core/ide-config-manager.js b/tools/cli/installers/lib/core/ide-config-manager.js deleted file mode 100644 index c00c00d48..000000000 --- a/tools/cli/installers/lib/core/ide-config-manager.js +++ /dev/null @@ -1,157 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const yaml = require('yaml'); -const prompts = require('../../../lib/prompts'); - -/** - * Manages IDE configuration persistence - * Saves and loads IDE-specific configurations to/from bmad/_config/ides/ - */ -class IdeConfigManager { - constructor() {} - - /** - * Get path to IDE config directory - * @param {string} bmadDir - BMAD installation directory - * @returns {string} Path to IDE config directory - */ - getIdeConfigDir(bmadDir) { - return path.join(bmadDir, '_config', 'ides'); - } - - /** - * Get path to specific IDE config file - * @param {string} bmadDir - BMAD installation directory - * @param {string} ideName - IDE name (e.g., 'claude-code') - * @returns {string} Path to IDE config file - */ - getIdeConfigPath(bmadDir, ideName) { - return path.join(this.getIdeConfigDir(bmadDir), `${ideName}.yaml`); - } - - /** - * Save IDE configuration - * @param {string} bmadDir - BMAD installation directory - * @param {string} ideName - IDE name - * @param {Object} configuration - IDE-specific configuration object - */ - async saveIdeConfig(bmadDir, ideName, configuration) { - const configDir = this.getIdeConfigDir(bmadDir); - await fs.ensureDir(configDir); - - const configPath = this.getIdeConfigPath(bmadDir, ideName); - const now = new Date().toISOString(); - - // Check if config already exists to preserve configured_date - let configuredDate = now; - if (await fs.pathExists(configPath)) { - try { - const existing = await this.loadIdeConfig(bmadDir, ideName); - if (existing && existing.configured_date) { - configuredDate = existing.configured_date; - } - } catch { - // Ignore errors reading existing config - } - } - - const configData = { - ide: ideName, - configured_date: configuredDate, - last_updated: now, - configuration: configuration || {}, - }; - - // Clean the config to remove any non-serializable values (like functions) - const cleanConfig = structuredClone(configData); - - const yamlContent = yaml.stringify(cleanConfig, { - indent: 2, - lineWidth: 0, - sortKeys: false, - }); - - // Ensure POSIX-compliant final newline - const content = yamlContent.endsWith('\n') ? yamlContent : yamlContent + '\n'; - await fs.writeFile(configPath, content, 'utf8'); - } - - /** - * Load IDE configuration - * @param {string} bmadDir - BMAD installation directory - * @param {string} ideName - IDE name - * @returns {Object|null} IDE configuration or null if not found - */ - async loadIdeConfig(bmadDir, ideName) { - const configPath = this.getIdeConfigPath(bmadDir, ideName); - - if (!(await fs.pathExists(configPath))) { - return null; - } - - try { - const content = await fs.readFile(configPath, 'utf8'); - const config = yaml.parse(content); - return config; - } catch (error) { - await prompts.log.warn(`Failed to load IDE config for ${ideName}: ${error.message}`); - return null; - } - } - - /** - * Load all IDE configurations - * @param {string} bmadDir - BMAD installation directory - * @returns {Object} Map of IDE name to configuration - */ - async loadAllIdeConfigs(bmadDir) { - const configDir = this.getIdeConfigDir(bmadDir); - const configs = {}; - - if (!(await fs.pathExists(configDir))) { - return configs; - } - - try { - const files = await fs.readdir(configDir); - for (const file of files) { - if (file.endsWith('.yaml')) { - const ideName = file.replace('.yaml', ''); - const config = await this.loadIdeConfig(bmadDir, ideName); - if (config) { - configs[ideName] = config.configuration; - } - } - } - } catch (error) { - await prompts.log.warn(`Failed to load IDE configs: ${error.message}`); - } - - return configs; - } - - /** - * Check if IDE has saved configuration - * @param {string} bmadDir - BMAD installation directory - * @param {string} ideName - IDE name - * @returns {boolean} True if configuration exists - */ - async hasIdeConfig(bmadDir, ideName) { - const configPath = this.getIdeConfigPath(bmadDir, ideName); - return await fs.pathExists(configPath); - } - - /** - * Delete IDE configuration - * @param {string} bmadDir - BMAD installation directory - * @param {string} ideName - IDE name - */ - async deleteIdeConfig(bmadDir, ideName) { - const configPath = this.getIdeConfigPath(bmadDir, ideName); - if (await fs.pathExists(configPath)) { - await fs.remove(configPath); - } - } -} - -module.exports = { IdeConfigManager }; diff --git a/tools/cli/installers/lib/core/installer.js b/tools/cli/installers/lib/core/installer.js deleted file mode 100644 index fe8b88d7c..000000000 --- a/tools/cli/installers/lib/core/installer.js +++ /dev/null @@ -1,3162 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const { Detector } = require('./detector'); -const { Manifest } = require('./manifest'); -const { ModuleManager } = require('../modules/manager'); -const { IdeManager } = require('../ide/manager'); -const { FileOps } = require('../../../lib/file-ops'); -const { Config } = require('../../../lib/config'); -const { XmlHandler } = require('../../../lib/xml-handler'); -const { DependencyResolver } = require('./dependency-resolver'); -const { ConfigCollector } = require('./config-collector'); -const { getProjectRoot, getSourcePath, getModulePath } = require('../../../lib/project-root'); -const { CLIUtils } = require('../../../lib/cli-utils'); -const { ManifestGenerator } = require('./manifest-generator'); -const { IdeConfigManager } = require('./ide-config-manager'); -const { CustomHandler } = require('../custom/handler'); -const prompts = require('../../../lib/prompts'); -const { BMAD_FOLDER_NAME } = require('../ide/shared/path-utils'); - -class Installer { - constructor() { - this.detector = new Detector(); - this.manifest = new Manifest(); - this.moduleManager = new ModuleManager(); - this.ideManager = new IdeManager(); - this.fileOps = new FileOps(); - this.config = new Config(); - this.xmlHandler = new XmlHandler(); - this.dependencyResolver = new DependencyResolver(); - this.configCollector = new ConfigCollector(); - this.ideConfigManager = new IdeConfigManager(); - this.installedFiles = new Set(); // Track all installed files - this.bmadFolderName = BMAD_FOLDER_NAME; - } - - /** - * Find the bmad installation directory in a project - * Always uses the standard _bmad folder name - * Also checks for legacy _cfg folder for migration - * @param {string} projectDir - Project directory - * @returns {Promise} { bmadDir: string, hasLegacyCfg: boolean } - */ - async findBmadDir(projectDir) { - const bmadDir = path.join(projectDir, BMAD_FOLDER_NAME); - - // Check if project directory exists - if (!(await fs.pathExists(projectDir))) { - // Project doesn't exist yet, return default - return { bmadDir, hasLegacyCfg: false }; - } - - // Check for legacy _cfg folder if bmad directory exists - let hasLegacyCfg = false; - if (await fs.pathExists(bmadDir)) { - const legacyCfgPath = path.join(bmadDir, '_cfg'); - if (await fs.pathExists(legacyCfgPath)) { - hasLegacyCfg = true; - } - } - - return { bmadDir, hasLegacyCfg }; - } - - /** - * @function copyFileWithPlaceholderReplacement - * @intent Copy files from BMAD source to installation directory with dynamic content transformation - * @why Enables installation-time customization: _bmad replacement - * @param {string} sourcePath - Absolute path to source file in BMAD repository - * @param {string} targetPath - Absolute path to destination file in user's project - * @param {string} bmadFolderName - User's chosen bmad folder name (default: 'bmad') - * @returns {Promise} Resolves when file copy and transformation complete - * @sideeffects Writes transformed file to targetPath, creates parent directories if needed - * @edgecases Binary files bypass transformation, falls back to raw copy if UTF-8 read fails - * @calledby installCore(), installModule(), IDE installers during file vendoring - * @calls fs.readFile(), fs.writeFile(), fs.copy() - * - - * - * 3. Document marker in instructions.md (if applicable) - */ - async copyFileWithPlaceholderReplacement(sourcePath, targetPath) { - // List of text file extensions that should have placeholder replacement - const textExtensions = ['.md', '.yaml', '.yml', '.txt', '.json', '.js', '.ts', '.html', '.css', '.sh', '.bat', '.csv', '.xml']; - const ext = path.extname(sourcePath).toLowerCase(); - - // Check if this is a text file that might contain placeholders - if (textExtensions.includes(ext)) { - try { - // Read the file content - let content = await fs.readFile(sourcePath, 'utf8'); - - // Write to target with replaced content - await fs.ensureDir(path.dirname(targetPath)); - await fs.writeFile(targetPath, content, 'utf8'); - } catch { - // If reading as text fails (might be binary despite extension), fall back to regular copy - await fs.copy(sourcePath, targetPath, { overwrite: true }); - } - } else { - // Binary file or other file type - just copy directly - await fs.copy(sourcePath, targetPath, { overwrite: true }); - } - } - - /** - * Collect Tool/IDE configurations after module configuration - * @param {string} projectDir - Project directory - * @param {Array} selectedModules - Selected modules from configuration - * @param {boolean} isFullReinstall - Whether this is a full reinstall - * @param {Array} previousIdes - Previously configured IDEs (for reinstalls) - * @param {Array} preSelectedIdes - Pre-selected IDEs from early prompt (optional) - * @param {boolean} skipPrompts - Skip prompts and use defaults (for --yes flag) - * @returns {Object} Tool/IDE selection and configurations - */ - async collectToolConfigurations( - projectDir, - selectedModules, - isFullReinstall = false, - previousIdes = [], - preSelectedIdes = null, - skipPrompts = false, - ) { - // Use pre-selected IDEs if provided, otherwise prompt - let toolConfig; - if (preSelectedIdes === null) { - // Fallback: prompt for tool selection (backwards compatibility) - const { UI } = require('../../../lib/ui'); - const ui = new UI(); - toolConfig = await ui.promptToolSelection(projectDir); - } else { - // IDEs were already selected during initial prompts - toolConfig = { - ides: preSelectedIdes, - skipIde: !preSelectedIdes || preSelectedIdes.length === 0, - }; - } - - // Check for already configured IDEs - const { Detector } = require('./detector'); - const detector = new Detector(); - const bmadDir = path.join(projectDir, BMAD_FOLDER_NAME); - - // During full reinstall, use the saved previous IDEs since bmad dir was deleted - // Otherwise detect from existing installation - let previouslyConfiguredIdes; - if (isFullReinstall) { - // During reinstall, treat all IDEs as new (need configuration) - previouslyConfiguredIdes = []; - } else { - const existingInstall = await detector.detect(bmadDir); - previouslyConfiguredIdes = existingInstall.ides || []; - } - - // Load saved IDE configurations for already-configured IDEs - const savedIdeConfigs = await this.ideConfigManager.loadAllIdeConfigs(bmadDir); - - // Collect IDE-specific configurations if any were selected - const ideConfigurations = {}; - - // First, add saved configs for already-configured IDEs - for (const ide of toolConfig.ides || []) { - if (previouslyConfiguredIdes.includes(ide) && savedIdeConfigs[ide]) { - ideConfigurations[ide] = savedIdeConfigs[ide]; - } - } - - if (!toolConfig.skipIde && toolConfig.ides && toolConfig.ides.length > 0) { - // Ensure IDE manager is initialized - await this.ideManager.ensureInitialized(); - - // Determine which IDEs are newly selected (not previously configured) - const newlySelectedIdes = toolConfig.ides.filter((ide) => !previouslyConfiguredIdes.includes(ide)); - - if (newlySelectedIdes.length > 0) { - // Collect configuration for IDEs that support it - for (const ide of newlySelectedIdes) { - try { - const handler = this.ideManager.handlers.get(ide); - - if (!handler) { - await prompts.log.warn(`Warning: IDE '${ide}' handler not found`); - continue; - } - - // Check if this IDE handler has a collectConfiguration method - // (custom installers like Codex, Kilo may have this) - if (typeof handler.collectConfiguration === 'function') { - await prompts.log.info(`Configuring ${ide}...`); - ideConfigurations[ide] = await handler.collectConfiguration({ - selectedModules: selectedModules || [], - projectDir, - bmadDir, - skipPrompts, - }); - } else { - // Config-driven IDEs don't need configuration - mark as ready - ideConfigurations[ide] = { _noConfigNeeded: true }; - } - } catch (error) { - // IDE doesn't support configuration or has an error - await prompts.log.warn(`Warning: Could not load configuration for ${ide}: ${error.message}`); - } - } - } - - // Log which IDEs are already configured and being kept - const keptIdes = toolConfig.ides.filter((ide) => previouslyConfiguredIdes.includes(ide)); - if (keptIdes.length > 0) { - await prompts.log.message(`Keeping existing configuration for: ${keptIdes.join(', ')}`); - } - } - - return { - ides: toolConfig.ides, - skipIde: toolConfig.skipIde, - configurations: ideConfigurations, - }; - } - - /** - * Main installation method - * @param {Object} config - Installation configuration - * @param {string} config.directory - Target directory - * @param {boolean} config.installCore - Whether to install core - * @param {string[]} config.modules - Modules to install - * @param {string[]} config.ides - IDEs to configure - * @param {boolean} config.skipIde - Skip IDE configuration - */ - async install(originalConfig) { - // Clone config to avoid mutating the caller's object - const config = { ...originalConfig }; - - // Check if core config was already collected in UI - const hasCoreConfig = config.coreConfig && Object.keys(config.coreConfig).length > 0; - - // Only display logo if core config wasn't already collected (meaning we're not continuing from UI) - if (!hasCoreConfig) { - // Display BMAD logo - await CLIUtils.displayLogo(); - - // Display welcome message - await CLIUtils.displaySection('BMad™ Installation', 'Version ' + require(path.join(getProjectRoot(), 'package.json')).version); - } - - // Note: Legacy V4 detection now happens earlier in UI.promptInstall() - // before any config collection, so we don't need to check again here - - const projectDir = path.resolve(config.directory); - const bmadDir = path.join(projectDir, BMAD_FOLDER_NAME); - - // If core config was pre-collected (from interactive mode), use it - if (config.coreConfig && Object.keys(config.coreConfig).length > 0) { - this.configCollector.collectedConfig.core = config.coreConfig; - // Also store in allAnswers for cross-referencing - this.configCollector.allAnswers = {}; - for (const [key, value] of Object.entries(config.coreConfig)) { - this.configCollector.allAnswers[`core_${key}`] = value; - } - } - - // Collect configurations for modules (skip if quick update already collected them) - let moduleConfigs; - let customModulePaths = new Map(); - - if (config._quickUpdate) { - // Quick update already collected all configs, use them directly - moduleConfigs = this.configCollector.collectedConfig; - - // For quick update, populate customModulePaths from _customModuleSources - if (config._customModuleSources) { - for (const [moduleId, customInfo] of config._customModuleSources) { - customModulePaths.set(moduleId, customInfo.sourcePath); - } - } - } else { - // For regular updates (modify flow), check manifest for custom module sources - if (config._isUpdate && config._existingInstall && config._existingInstall.customModules) { - for (const customModule of config._existingInstall.customModules) { - // Ensure we have an absolute sourcePath - let absoluteSourcePath = customModule.sourcePath; - - // Check if sourcePath is a cache-relative path (starts with _config) - if (absoluteSourcePath && absoluteSourcePath.startsWith('_config')) { - // Convert cache-relative path to absolute path - absoluteSourcePath = path.join(bmadDir, absoluteSourcePath); - } - // If no sourcePath but we have relativePath, convert it - else if (!absoluteSourcePath && customModule.relativePath) { - // relativePath is relative to the project root (parent of bmad dir) - absoluteSourcePath = path.resolve(projectDir, customModule.relativePath); - } - // Ensure sourcePath is absolute for anything else - else if (absoluteSourcePath && !path.isAbsolute(absoluteSourcePath)) { - absoluteSourcePath = path.resolve(absoluteSourcePath); - } - - if (absoluteSourcePath) { - customModulePaths.set(customModule.id, absoluteSourcePath); - } - } - } - - // Build custom module paths map from customContent - - // Handle selectedFiles (from existing install path or manual directory input) - if (config.customContent && config.customContent.selected && config.customContent.selectedFiles) { - const customHandler = new CustomHandler(); - for (const customFile of config.customContent.selectedFiles) { - const customInfo = await customHandler.getCustomInfo(customFile, path.resolve(config.directory)); - if (customInfo && customInfo.id) { - customModulePaths.set(customInfo.id, customInfo.path); - } - } - } - - // Handle new custom content sources from UI - if (config.customContent && config.customContent.sources) { - for (const source of config.customContent.sources) { - customModulePaths.set(source.id, source.path); - } - } - - // Handle cachedModules (from new install path where modules are cached) - // Only include modules that were actually selected for installation - if (config.customContent && config.customContent.cachedModules) { - // Get selected cached module IDs (if available) - const selectedCachedIds = config.customContent.selectedCachedModules || []; - // If no selection info, include all cached modules (for backward compatibility) - const shouldIncludeAll = selectedCachedIds.length === 0 && config.customContent.selected; - - for (const cachedModule of config.customContent.cachedModules) { - // For cached modules, the path is the cachePath which contains the module.yaml - if ( - cachedModule.id && - cachedModule.cachePath && // Include if selected or if we should include all - (shouldIncludeAll || selectedCachedIds.includes(cachedModule.id)) - ) { - customModulePaths.set(cachedModule.id, cachedModule.cachePath); - } - } - } - - // Get list of all modules including custom modules - // Order: core first, then official modules, then custom modules - const allModulesForConfig = ['core']; - - // Add official modules (excluding core and any custom modules) - const officialModules = (config.modules || []).filter((m) => m !== 'core' && !customModulePaths.has(m)); - allModulesForConfig.push(...officialModules); - - // Add custom modules at the end - for (const [moduleId] of customModulePaths) { - if (!allModulesForConfig.includes(moduleId)) { - allModulesForConfig.push(moduleId); - } - } - - // Check if core was already collected in UI - if (config.coreConfig && Object.keys(config.coreConfig).length > 0) { - // Core already collected, skip it in config collection - const modulesWithoutCore = allModulesForConfig.filter((m) => m !== 'core'); - moduleConfigs = await this.configCollector.collectAllConfigurations(modulesWithoutCore, path.resolve(config.directory), { - customModulePaths, - skipPrompts: config.skipPrompts, - }); - } else { - // Core not collected yet, include it - moduleConfigs = await this.configCollector.collectAllConfigurations(allModulesForConfig, path.resolve(config.directory), { - customModulePaths, - skipPrompts: config.skipPrompts, - }); - } - } - - // Set bmad folder name on module manager and IDE manager for placeholder replacement - this.moduleManager.setBmadFolderName(BMAD_FOLDER_NAME); - this.moduleManager.setCoreConfig(moduleConfigs.core || {}); - this.moduleManager.setCustomModulePaths(customModulePaths); - this.ideManager.setBmadFolderName(BMAD_FOLDER_NAME); - - // Tool selection will be collected after we determine if it's a reinstall/update/new install - - const spinner = await prompts.spinner(); - spinner.start('Preparing installation...'); - - try { - // Create a project directory if it doesn't exist (user already confirmed) - if (!(await fs.pathExists(projectDir))) { - spinner.message('Creating installation directory...'); - try { - // fs.ensureDir handles platform-specific directory creation - // It will recursively create all necessary parent directories - await fs.ensureDir(projectDir); - } catch (error) { - spinner.error('Failed to create installation directory'); - await prompts.log.error(`Error: ${error.message}`); - // More detailed error for common issues - if (error.code === 'EACCES') { - await prompts.log.error('Permission denied. Check parent directory permissions.'); - } else if (error.code === 'ENOSPC') { - await prompts.log.error('No space left on device.'); - } - throw new Error(`Cannot create directory: ${projectDir}`); - } - } - - // Check existing installation - spinner.message('Checking for existing installation...'); - const existingInstall = await this.detector.detect(bmadDir); - - if (existingInstall.installed && !config.force && !config._quickUpdate) { - spinner.stop('Existing installation detected'); - - // Check if user already decided what to do (from early menu in ui.js) - let action = null; - if (config.actionType === 'update') { - action = 'update'; - } else if (config.skipPrompts) { - // Non-interactive mode: default to update - action = 'update'; - } else { - // Fallback: Ask the user (backwards compatibility for other code paths) - await prompts.log.warn('Existing BMAD installation detected'); - await prompts.log.message(` Location: ${bmadDir}`); - await prompts.log.message(` Version: ${existingInstall.version}`); - - const promptResult = await this.promptUpdateAction(); - action = promptResult.action; - } - - if (action === 'update') { - // Store that we're updating for later processing - config._isUpdate = true; - config._existingInstall = existingInstall; - - // Detect modules that were previously installed but are NOT in the new selection (to be removed) - const previouslyInstalledModules = new Set(existingInstall.modules.map((m) => m.id)); - const newlySelectedModules = new Set(config.modules || []); - - // Find modules to remove (installed but not in new selection) - // Exclude 'core' from being removable - const modulesToRemove = [...previouslyInstalledModules].filter((m) => !newlySelectedModules.has(m) && m !== 'core'); - - // If there are modules to remove, ask for confirmation - if (modulesToRemove.length > 0) { - if (config.skipPrompts) { - // Non-interactive mode: preserve modules (matches prompt default: false) - for (const moduleId of modulesToRemove) { - if (!config.modules) config.modules = []; - config.modules.push(moduleId); - } - spinner.start('Preparing update...'); - } else { - if (spinner.isSpinning) { - spinner.stop('Module changes reviewed'); - } - - await prompts.log.warn('Modules to be removed:'); - for (const moduleId of modulesToRemove) { - const moduleInfo = existingInstall.modules.find((m) => m.id === moduleId); - const displayName = moduleInfo?.name || moduleId; - const modulePath = path.join(bmadDir, moduleId); - await prompts.log.error(` - ${displayName} (${modulePath})`); - } - - const confirmRemoval = await prompts.confirm({ - message: `Remove ${modulesToRemove.length} module(s) from BMAD installation?`, - default: false, - }); - - if (confirmRemoval) { - // Remove module folders - for (const moduleId of modulesToRemove) { - const modulePath = path.join(bmadDir, moduleId); - try { - if (await fs.pathExists(modulePath)) { - await fs.remove(modulePath); - await prompts.log.message(` Removed: ${moduleId}`); - } - } catch (error) { - await prompts.log.warn(` Warning: Failed to remove ${moduleId}: ${error.message}`); - } - } - await prompts.log.success(` Removed ${modulesToRemove.length} module(s)`); - } else { - await prompts.log.message(' Module removal cancelled'); - // Add the modules back to the selection since user cancelled removal - for (const moduleId of modulesToRemove) { - if (!config.modules) config.modules = []; - config.modules.push(moduleId); - } - } - - spinner.start('Preparing update...'); - } - } - - // Detect custom and modified files BEFORE updating (compare current files vs files-manifest.csv) - const existingFilesManifest = await this.readFilesManifest(bmadDir); - const { customFiles, modifiedFiles } = await this.detectCustomFiles(bmadDir, existingFilesManifest); - - config._customFiles = customFiles; - config._modifiedFiles = modifiedFiles; - - // Preserve existing core configuration during updates - // Read the current core config.yaml to maintain user's settings - const coreConfigPath = path.join(bmadDir, 'core', 'config.yaml'); - if ((await fs.pathExists(coreConfigPath)) && (!config.coreConfig || Object.keys(config.coreConfig).length === 0)) { - try { - const yaml = require('yaml'); - const coreConfigContent = await fs.readFile(coreConfigPath, 'utf8'); - const existingCoreConfig = yaml.parse(coreConfigContent); - - // Store in config.coreConfig so it's preserved through the installation - config.coreConfig = existingCoreConfig; - - // Also store in configCollector for use during config collection - this.configCollector.collectedConfig.core = existingCoreConfig; - } catch (error) { - await prompts.log.warn(`Warning: Could not read existing core config: ${error.message}`); - } - } - - // Also check cache directory for custom modules (like quick update does) - const cacheDir = path.join(bmadDir, '_config', 'custom'); - if (await fs.pathExists(cacheDir)) { - const cachedModules = await fs.readdir(cacheDir, { withFileTypes: true }); - - for (const cachedModule of cachedModules) { - const moduleId = cachedModule.name; - const cachedPath = path.join(cacheDir, moduleId); - - // Skip if path doesn't exist (broken symlink, deleted dir) - avoids lstat ENOENT - if (!(await fs.pathExists(cachedPath)) || !cachedModule.isDirectory()) { - continue; - } - - // Skip if we already have this module from manifest - if (customModulePaths.has(moduleId)) { - continue; - } - - // Check if this is an external official module - skip cache for those - const isExternal = await this.moduleManager.isExternalModule(moduleId); - if (isExternal) { - // External modules are handled via cloneExternalModule, not from cache - continue; - } - - // Check if this is actually a custom module (has module.yaml) - const moduleYamlPath = path.join(cachedPath, 'module.yaml'); - if (await fs.pathExists(moduleYamlPath)) { - customModulePaths.set(moduleId, cachedPath); - } - } - - // Update module manager with the new custom module paths from cache - this.moduleManager.setCustomModulePaths(customModulePaths); - } - - // If there are custom files, back them up temporarily - if (customFiles.length > 0) { - const tempBackupDir = path.join(projectDir, '_bmad-custom-backup-temp'); - await fs.ensureDir(tempBackupDir); - - spinner.start(`Backing up ${customFiles.length} custom files...`); - for (const customFile of customFiles) { - const relativePath = path.relative(bmadDir, customFile); - const backupPath = path.join(tempBackupDir, relativePath); - await fs.ensureDir(path.dirname(backupPath)); - await fs.copy(customFile, backupPath); - } - spinner.stop(`Backed up ${customFiles.length} custom files`); - - config._tempBackupDir = tempBackupDir; - } - - // For modified files, back them up to temp directory (will be restored as .bak files after install) - if (modifiedFiles.length > 0) { - const tempModifiedBackupDir = path.join(projectDir, '_bmad-modified-backup-temp'); - await fs.ensureDir(tempModifiedBackupDir); - - spinner.start(`Backing up ${modifiedFiles.length} modified files...`); - for (const modifiedFile of modifiedFiles) { - const relativePath = path.relative(bmadDir, modifiedFile.path); - const tempBackupPath = path.join(tempModifiedBackupDir, relativePath); - await fs.ensureDir(path.dirname(tempBackupPath)); - await fs.copy(modifiedFile.path, tempBackupPath, { overwrite: true }); - } - spinner.stop(`Backed up ${modifiedFiles.length} modified files`); - - config._tempModifiedBackupDir = tempModifiedBackupDir; - } - } - } else if (existingInstall.installed && config._quickUpdate) { - // Quick update mode - automatically treat as update without prompting - spinner.message('Preparing quick update...'); - config._isUpdate = true; - config._existingInstall = existingInstall; - - // Detect custom and modified files BEFORE updating - const existingFilesManifest = await this.readFilesManifest(bmadDir); - const { customFiles, modifiedFiles } = await this.detectCustomFiles(bmadDir, existingFilesManifest); - - config._customFiles = customFiles; - config._modifiedFiles = modifiedFiles; - - // Also check cache directory for custom modules (like quick update does) - const cacheDir = path.join(bmadDir, '_config', 'custom'); - if (await fs.pathExists(cacheDir)) { - const cachedModules = await fs.readdir(cacheDir, { withFileTypes: true }); - - for (const cachedModule of cachedModules) { - const moduleId = cachedModule.name; - const cachedPath = path.join(cacheDir, moduleId); - - // Skip if path doesn't exist (broken symlink, deleted dir) - avoids lstat ENOENT - if (!(await fs.pathExists(cachedPath)) || !cachedModule.isDirectory()) { - continue; - } - - // Skip if we already have this module from manifest - if (customModulePaths.has(moduleId)) { - continue; - } - - // Check if this is an external official module - skip cache for those - const isExternal = await this.moduleManager.isExternalModule(moduleId); - if (isExternal) { - // External modules are handled via cloneExternalModule, not from cache - continue; - } - - // Check if this is actually a custom module (has module.yaml) - const moduleYamlPath = path.join(cachedPath, 'module.yaml'); - if (await fs.pathExists(moduleYamlPath)) { - customModulePaths.set(moduleId, cachedPath); - } - } - - // Update module manager with the new custom module paths from cache - this.moduleManager.setCustomModulePaths(customModulePaths); - } - - // Back up custom files - if (customFiles.length > 0) { - const tempBackupDir = path.join(projectDir, '_bmad-custom-backup-temp'); - await fs.ensureDir(tempBackupDir); - - spinner.start(`Backing up ${customFiles.length} custom files...`); - for (const customFile of customFiles) { - const relativePath = path.relative(bmadDir, customFile); - const backupPath = path.join(tempBackupDir, relativePath); - await fs.ensureDir(path.dirname(backupPath)); - await fs.copy(customFile, backupPath); - } - spinner.stop(`Backed up ${customFiles.length} custom files`); - config._tempBackupDir = tempBackupDir; - } - - // Back up modified files - if (modifiedFiles.length > 0) { - const tempModifiedBackupDir = path.join(projectDir, '_bmad-modified-backup-temp'); - await fs.ensureDir(tempModifiedBackupDir); - - spinner.start(`Backing up ${modifiedFiles.length} modified files...`); - for (const modifiedFile of modifiedFiles) { - const relativePath = path.relative(bmadDir, modifiedFile.path); - const tempBackupPath = path.join(tempModifiedBackupDir, relativePath); - await fs.ensureDir(path.dirname(tempBackupPath)); - await fs.copy(modifiedFile.path, tempBackupPath, { overwrite: true }); - } - spinner.stop(`Backed up ${modifiedFiles.length} modified files`); - config._tempModifiedBackupDir = tempModifiedBackupDir; - } - } - - // Now collect tool configurations after we know if it's a reinstall - // Skip for quick update since we already have the IDE list - spinner.stop('Pre-checks complete'); - let toolSelection; - if (config._quickUpdate) { - // Quick update already has IDEs configured, use saved configurations - const preConfiguredIdes = {}; - const savedIdeConfigs = config._savedIdeConfigs || {}; - - for (const ide of config.ides || []) { - // Use saved config if available, otherwise mark as already configured (legacy) - if (savedIdeConfigs[ide]) { - preConfiguredIdes[ide] = savedIdeConfigs[ide]; - } else { - preConfiguredIdes[ide] = { _alreadyConfigured: true }; - } - } - toolSelection = { - ides: config.ides || [], - skipIde: !config.ides || config.ides.length === 0, - configurations: preConfiguredIdes, - }; - } else { - // Pass pre-selected IDEs from early prompt (if available) - // This allows IDE selection to happen before file copying, improving UX - // Use config.ides if it's an array (even if empty), null means prompt - const preSelectedIdes = Array.isArray(config.ides) ? config.ides : null; - toolSelection = await this.collectToolConfigurations( - path.resolve(config.directory), - config.modules, - config._isFullReinstall || false, - config._previouslyConfiguredIdes || [], - preSelectedIdes, - config.skipPrompts || false, - ); - } - - // Merge tool selection into config (for both quick update and regular flow) - config.ides = toolSelection.ides; - config.skipIde = toolSelection.skipIde; - const ideConfigurations = toolSelection.configurations; - - // Detect IDEs that were previously installed but are NOT in the new selection (to be removed) - if (config._isUpdate && config._existingInstall) { - const previouslyInstalledIdes = new Set(config._existingInstall.ides || []); - const newlySelectedIdes = new Set(config.ides || []); - - const idesToRemove = [...previouslyInstalledIdes].filter((ide) => !newlySelectedIdes.has(ide)); - - if (idesToRemove.length > 0) { - if (config.skipPrompts) { - // Non-interactive mode: silently preserve existing IDE configs - if (!config.ides) config.ides = []; - const savedIdeConfigs = await this.ideConfigManager.loadAllIdeConfigs(bmadDir); - for (const ide of idesToRemove) { - config.ides.push(ide); - if (savedIdeConfigs[ide] && !ideConfigurations[ide]) { - ideConfigurations[ide] = savedIdeConfigs[ide]; - } - } - } else { - if (spinner.isSpinning) { - spinner.stop('IDE changes reviewed'); - } - - await prompts.log.warn('IDEs to be removed:'); - for (const ide of idesToRemove) { - await prompts.log.error(` - ${ide}`); - } - - const confirmRemoval = await prompts.confirm({ - message: `Remove BMAD configuration for ${idesToRemove.length} IDE(s)?`, - default: false, - }); - - if (confirmRemoval) { - await this.ideManager.ensureInitialized(); - for (const ide of idesToRemove) { - try { - const handler = this.ideManager.handlers.get(ide); - if (handler) { - await handler.cleanup(projectDir); - } - await this.ideConfigManager.deleteIdeConfig(bmadDir, ide); - await prompts.log.message(` Removed: ${ide}`); - } catch (error) { - await prompts.log.warn(` Warning: Failed to remove ${ide}: ${error.message}`); - } - } - await prompts.log.success(` Removed ${idesToRemove.length} IDE(s)`); - } else { - await prompts.log.message(' IDE removal cancelled'); - // Add IDEs back to selection and restore their saved configurations - if (!config.ides) config.ides = []; - const savedIdeConfigs = await this.ideConfigManager.loadAllIdeConfigs(bmadDir); - for (const ide of idesToRemove) { - config.ides.push(ide); - if (savedIdeConfigs[ide] && !ideConfigurations[ide]) { - ideConfigurations[ide] = savedIdeConfigs[ide]; - } - } - } - - spinner.start('Preparing installation...'); - } - } - } - - // Results collector for consolidated summary - const results = []; - const addResult = (step, status, detail = '') => results.push({ step, status, detail }); - - if (spinner.isSpinning) { - spinner.message('Preparing installation...'); - } else { - spinner.start('Preparing installation...'); - } - - // Create bmad directory structure - spinner.message('Creating directory structure...'); - await this.createDirectoryStructure(bmadDir); - - // Cache custom modules if any - if (customModulePaths && customModulePaths.size > 0) { - spinner.message('Caching custom modules...'); - const { CustomModuleCache } = require('./custom-module-cache'); - const customCache = new CustomModuleCache(bmadDir); - - for (const [moduleId, sourcePath] of customModulePaths) { - const cachedInfo = await customCache.cacheModule(moduleId, sourcePath, { - sourcePath: sourcePath, // Store original path for updates - }); - - // Update the customModulePaths to use the cached location - customModulePaths.set(moduleId, cachedInfo.cachePath); - } - - // Update module manager with the cached paths - this.moduleManager.setCustomModulePaths(customModulePaths); - addResult('Custom modules cached', 'ok'); - } - - const projectRoot = getProjectRoot(); - - // Custom content is already handled in UI before module selection - const finalCustomContent = config.customContent; - - // Prepare modules list including cached custom modules - let allModules = [...(config.modules || [])]; - - // During quick update, we might have custom module sources from the manifest - if (config._customModuleSources) { - // Add custom modules from stored sources - for (const [moduleId, customInfo] of config._customModuleSources) { - if (!allModules.includes(moduleId) && (await fs.pathExists(customInfo.sourcePath))) { - allModules.push(moduleId); - } - } - } - - // Add cached custom modules - if (finalCustomContent && finalCustomContent.cachedModules) { - for (const cachedModule of finalCustomContent.cachedModules) { - if (!allModules.includes(cachedModule.id)) { - allModules.push(cachedModule.id); - } - } - } - - // Regular custom content from user input (non-cached) - if (finalCustomContent && finalCustomContent.selected && finalCustomContent.selectedFiles) { - // Add custom modules to the installation list - const customHandler = new CustomHandler(); - for (const customFile of finalCustomContent.selectedFiles) { - const customInfo = await customHandler.getCustomInfo(customFile, projectDir); - if (customInfo && customInfo.id) { - allModules.push(customInfo.id); - } - } - } - - // Don't include core again if already installed - if (config.installCore) { - allModules = allModules.filter((m) => m !== 'core'); - } - - // For dependency resolution, we only need regular modules (not custom modules) - // Custom modules are already installed in _bmad and don't need dependency resolution from source - const regularModulesForResolution = allModules.filter((module) => { - // Check if this is a custom module - const isCustom = - customModulePaths.has(module) || - (finalCustomContent && finalCustomContent.cachedModules && finalCustomContent.cachedModules.some((cm) => cm.id === module)) || - (finalCustomContent && - finalCustomContent.selected && - finalCustomContent.selectedFiles && - finalCustomContent.selectedFiles.some((f) => f.includes(module))); - return !isCustom; - }); - - // Stop spinner before tasks() takes over progress display - spinner.stop('Preparation complete'); - - // ───────────────────────────────────────────────────────────────────────── - // FIRST TASKS BLOCK: Core installation through manifests (non-interactive) - // ───────────────────────────────────────────────────────────────────────── - const isQuickUpdate = config._quickUpdate || false; - - // Shared resolution result across task callbacks (closure-scoped, not on `this`) - let taskResolution; - - // Collect directory creation results for output after tasks() completes - const dirResults = { createdDirs: [], movedDirs: [], createdWdsFolders: [] }; - - // Build task list conditionally - const installTasks = []; - - // Core installation task - if (config.installCore) { - installTasks.push({ - title: isQuickUpdate ? 'Updating BMAD core' : 'Installing BMAD core', - task: async (message) => { - await this.installCoreWithDependencies(bmadDir, { core: {} }); - addResult('Core', 'ok', isQuickUpdate ? 'updated' : 'installed'); - await this.generateModuleConfigs(bmadDir, { core: config.coreConfig || {} }); - return isQuickUpdate ? 'Core updated' : 'Core installed'; - }, - }); - } - - // Dependency resolution task - installTasks.push({ - title: 'Resolving dependencies', - task: async (message) => { - // Create a temporary module manager that knows about custom content locations - const tempModuleManager = new ModuleManager({ - bmadDir: bmadDir, - }); - - taskResolution = await this.dependencyResolver.resolve(projectRoot, regularModulesForResolution, { - verbose: config.verbose, - moduleManager: tempModuleManager, - }); - return 'Dependencies resolved'; - }, - }); - - // Module installation task - if (allModules && allModules.length > 0) { - installTasks.push({ - title: isQuickUpdate ? `Updating ${allModules.length} module(s)` : `Installing ${allModules.length} module(s)`, - task: async (message) => { - const resolution = taskResolution; - const installedModuleNames = new Set(); - - for (const moduleName of allModules) { - if (installedModuleNames.has(moduleName)) continue; - installedModuleNames.add(moduleName); - - message(`${isQuickUpdate ? 'Updating' : 'Installing'} ${moduleName}...`); - - // Check if this is a custom module - let isCustomModule = false; - let customInfo = null; - - // First check if we have a cached version - if (finalCustomContent && finalCustomContent.cachedModules) { - const cachedModule = finalCustomContent.cachedModules.find((m) => m.id === moduleName); - if (cachedModule) { - isCustomModule = true; - customInfo = { id: moduleName, path: cachedModule.cachePath, config: {} }; - } - } - - // Then check custom module sources from manifest (for quick update) - if (!isCustomModule && config._customModuleSources && config._customModuleSources.has(moduleName)) { - customInfo = config._customModuleSources.get(moduleName); - isCustomModule = true; - if (customInfo.sourcePath && !customInfo.path) { - customInfo.path = path.isAbsolute(customInfo.sourcePath) - ? customInfo.sourcePath - : path.join(bmadDir, customInfo.sourcePath); - } - } - - // Finally check regular custom content - if (!isCustomModule && finalCustomContent && finalCustomContent.selected && finalCustomContent.selectedFiles) { - const customHandler = new CustomHandler(); - for (const customFile of finalCustomContent.selectedFiles) { - const info = await customHandler.getCustomInfo(customFile, projectDir); - if (info && info.id === moduleName) { - isCustomModule = true; - customInfo = info; - break; - } - } - } - - if (isCustomModule && customInfo) { - if (!customModulePaths.has(moduleName) && customInfo.path) { - customModulePaths.set(moduleName, customInfo.path); - this.moduleManager.setCustomModulePaths(customModulePaths); - } - - const collectedModuleConfig = moduleConfigs[moduleName] || {}; - await this.moduleManager.install( - moduleName, - bmadDir, - (filePath) => { - this.installedFiles.add(filePath); - }, - { - isCustom: true, - moduleConfig: collectedModuleConfig, - isQuickUpdate: isQuickUpdate, - installer: this, - silent: true, - }, - ); - await this.generateModuleConfigs(bmadDir, { - [moduleName]: { ...config.coreConfig, ...customInfo.config, ...collectedModuleConfig }, - }); - } else { - if (!resolution || !resolution.byModule) { - addResult(`Module: ${moduleName}`, 'warn', 'skipped (no resolution data)'); - continue; - } - if (moduleName === 'core') { - await this.installCoreWithDependencies(bmadDir, resolution.byModule[moduleName]); - } else { - await this.installModuleWithDependencies(moduleName, bmadDir, resolution.byModule[moduleName]); - } - } - - addResult(`Module: ${moduleName}`, 'ok', isQuickUpdate ? 'updated' : 'installed'); - } - - // Install partial modules (only dependencies) - if (!resolution || !resolution.byModule) { - return `${allModules.length} module(s) ${isQuickUpdate ? 'updated' : 'installed'}`; - } - for (const [module, files] of Object.entries(resolution.byModule)) { - if (!allModules.includes(module) && module !== 'core') { - const totalFiles = - files.agents.length + - files.tasks.length + - files.tools.length + - files.templates.length + - files.data.length + - files.other.length; - if (totalFiles > 0) { - message(`Installing ${module} dependencies...`); - await this.installPartialModule(module, bmadDir, files); - } - } - } - - return `${allModules.length} module(s) ${isQuickUpdate ? 'updated' : 'installed'}`; - }, - }); - } - - // Module directory creation task - installTasks.push({ - title: 'Creating module directories', - task: async (message) => { - const resolution = taskResolution; - if (!resolution || !resolution.byModule) { - addResult('Module directories', 'warn', 'no resolution data'); - return 'Module directories skipped (no resolution data)'; - } - const verboseMode = process.env.BMAD_VERBOSE_INSTALL === 'true' || config.verbose; - const moduleLogger = { - log: async (msg) => (verboseMode ? await prompts.log.message(msg) : undefined), - error: async (msg) => await prompts.log.error(msg), - warn: async (msg) => await prompts.log.warn(msg), - }; - - // Core module directories - if (config.installCore || resolution.byModule.core) { - const result = await this.moduleManager.createModuleDirectories('core', bmadDir, { - installedIDEs: config.ides || [], - moduleConfig: moduleConfigs.core || {}, - existingModuleConfig: this.configCollector.existingConfig?.core || {}, - coreConfig: moduleConfigs.core || {}, - logger: moduleLogger, - silent: true, - }); - if (result) { - dirResults.createdDirs.push(...result.createdDirs); - dirResults.movedDirs.push(...(result.movedDirs || [])); - dirResults.createdWdsFolders.push(...result.createdWdsFolders); - } - } - - // User-selected module directories - if (config.modules && config.modules.length > 0) { - for (const moduleName of config.modules) { - message(`Setting up ${moduleName}...`); - const result = await this.moduleManager.createModuleDirectories(moduleName, bmadDir, { - installedIDEs: config.ides || [], - moduleConfig: moduleConfigs[moduleName] || {}, - existingModuleConfig: this.configCollector.existingConfig?.[moduleName] || {}, - coreConfig: moduleConfigs.core || {}, - logger: moduleLogger, - silent: true, - }); - if (result) { - dirResults.createdDirs.push(...result.createdDirs); - dirResults.movedDirs.push(...(result.movedDirs || [])); - dirResults.createdWdsFolders.push(...result.createdWdsFolders); - } - } - } - - addResult('Module directories', 'ok'); - return 'Module directories created'; - }, - }); - - // Configuration generation task (stored as named reference for deferred execution) - const configTask = { - title: 'Generating configurations', - task: async (message) => { - // Generate clean config.yaml files for each installed module - await this.generateModuleConfigs(bmadDir, moduleConfigs); - addResult('Configurations', 'ok', 'generated'); - - // Pre-register manifest files - const cfgDir = path.join(bmadDir, '_config'); - this.installedFiles.add(path.join(cfgDir, 'manifest.yaml')); - this.installedFiles.add(path.join(cfgDir, 'workflow-manifest.csv')); - this.installedFiles.add(path.join(cfgDir, 'agent-manifest.csv')); - this.installedFiles.add(path.join(cfgDir, 'task-manifest.csv')); - - // Generate CSV manifests for workflows, agents, tasks AND ALL FILES with hashes - // This must happen BEFORE mergeModuleHelpCatalogs because it depends on agent-manifest.csv - message('Generating manifests...'); - const manifestGen = new ManifestGenerator(); - - const allModulesForManifest = config._quickUpdate - ? config._existingModules || allModules || [] - : config._preserveModules - ? [...allModules, ...config._preserveModules] - : allModules || []; - - let modulesForCsvPreserve; - if (config._quickUpdate) { - modulesForCsvPreserve = config._existingModules || allModules || []; - } else { - modulesForCsvPreserve = config._preserveModules ? [...allModules, ...config._preserveModules] : allModules; - } - - const manifestStats = await manifestGen.generateManifests(bmadDir, allModulesForManifest, [...this.installedFiles], { - ides: config.ides || [], - preservedModules: modulesForCsvPreserve, - }); - - addResult( - 'Manifests', - 'ok', - `${manifestStats.workflows} workflows, ${manifestStats.agents} agents, ${manifestStats.tasks} tasks, ${manifestStats.tools} tools`, - ); - - // Merge help catalogs - message('Generating help catalog...'); - await this.mergeModuleHelpCatalogs(bmadDir); - addResult('Help catalog', 'ok'); - - return 'Configurations generated'; - }, - }; - installTasks.push(configTask); - - // Run all tasks except config (which runs after directory output) - const mainTasks = installTasks.filter((t) => t !== configTask); - await prompts.tasks(mainTasks); - - // Render directory creation output right after directory task - const color = await prompts.getColor(); - if (dirResults.movedDirs.length > 0) { - const lines = dirResults.movedDirs.map((d) => ` ${d}`).join('\n'); - await prompts.log.message(color.cyan(`Moved directories:\n${lines}`)); - } - if (dirResults.createdDirs.length > 0) { - const lines = dirResults.createdDirs.map((d) => ` ${d}`).join('\n'); - await prompts.log.message(color.yellow(`Created directories:\n${lines}`)); - } - if (dirResults.createdWdsFolders.length > 0) { - const lines = dirResults.createdWdsFolders.map((f) => color.dim(` \u2713 ${f}/`)).join('\n'); - await prompts.log.message(color.cyan(`Created WDS folder structure:\n${lines}`)); - } - - // Now run configuration generation - await prompts.tasks([configTask]); - - // Resolution is now available via closure-scoped taskResolution - const resolution = taskResolution; - - // ───────────────────────────────────────────────────────────────────────── - // IDE SETUP: Keep as spinner since it may prompt for user input - // ───────────────────────────────────────────────────────────────────────── - if (!config.skipIde && config.ides && config.ides.length > 0) { - await this.ideManager.ensureInitialized(); - const validIdes = config.ides.filter((ide) => ide && typeof ide === 'string'); - - if (validIdes.length === 0) { - addResult('IDE configuration', 'warn', 'no valid IDEs selected'); - } else { - const needsPrompting = validIdes.some((ide) => !ideConfigurations[ide]); - const ideSpinner = await prompts.spinner(); - ideSpinner.start('Configuring tools...'); - - try { - for (const ide of validIdes) { - if (!needsPrompting || ideConfigurations[ide]) { - ideSpinner.message(`Configuring ${ide}...`); - } else { - if (ideSpinner.isSpinning) { - ideSpinner.stop('Ready for IDE configuration'); - } - } - - // Suppress stray console output for pre-configured IDEs (no user interaction) - const ideHasConfig = Boolean(ideConfigurations[ide]); - const originalLog = console.log; - if (!config.verbose && ideHasConfig) { - console.log = () => {}; - } - try { - const setupResult = await this.ideManager.setup(ide, projectDir, bmadDir, { - selectedModules: allModules || [], - preCollectedConfig: ideConfigurations[ide] || null, - verbose: config.verbose, - silent: ideHasConfig, - }); - - if (ideConfigurations[ide] && !ideConfigurations[ide]._alreadyConfigured) { - await this.ideConfigManager.saveIdeConfig(bmadDir, ide, ideConfigurations[ide]); - } - - if (setupResult.success) { - addResult(ide, 'ok', setupResult.detail || ''); - } else { - addResult(ide, 'error', setupResult.error || 'failed'); - } - } finally { - console.log = originalLog; - } - - if (needsPrompting && !ideSpinner.isSpinning) { - ideSpinner.start('Configuring tools...'); - } - } - } finally { - if (ideSpinner.isSpinning) { - ideSpinner.stop('Tool configuration complete'); - } - } - } - } - - // ───────────────────────────────────────────────────────────────────────── - // SECOND TASKS BLOCK: Post-IDE operations (non-interactive) - // ───────────────────────────────────────────────────────────────────────── - const postIdeTasks = []; - - // File restoration task (only for updates) - if ( - config._isUpdate && - ((config._customFiles && config._customFiles.length > 0) || (config._modifiedFiles && config._modifiedFiles.length > 0)) - ) { - postIdeTasks.push({ - title: 'Finalizing installation', - task: async (message) => { - let customFiles = []; - let modifiedFiles = []; - - if (config._customFiles && config._customFiles.length > 0) { - message(`Restoring ${config._customFiles.length} custom files...`); - - for (const originalPath of config._customFiles) { - const relativePath = path.relative(bmadDir, originalPath); - const backupPath = path.join(config._tempBackupDir, relativePath); - - if (await fs.pathExists(backupPath)) { - await fs.ensureDir(path.dirname(originalPath)); - await fs.copy(backupPath, originalPath, { overwrite: true }); - } - } - - if (config._tempBackupDir && (await fs.pathExists(config._tempBackupDir))) { - await fs.remove(config._tempBackupDir); - } - - customFiles = config._customFiles; - } - - if (config._modifiedFiles && config._modifiedFiles.length > 0) { - modifiedFiles = config._modifiedFiles; - - if (config._tempModifiedBackupDir && (await fs.pathExists(config._tempModifiedBackupDir))) { - message(`Restoring ${modifiedFiles.length} modified files as .bak...`); - - for (const modifiedFile of modifiedFiles) { - const relativePath = path.relative(bmadDir, modifiedFile.path); - const tempBackupPath = path.join(config._tempModifiedBackupDir, relativePath); - const bakPath = modifiedFile.path + '.bak'; - - if (await fs.pathExists(tempBackupPath)) { - await fs.ensureDir(path.dirname(bakPath)); - await fs.copy(tempBackupPath, bakPath, { overwrite: true }); - } - } - - await fs.remove(config._tempModifiedBackupDir); - } - } - - // Store for summary access - config._restoredCustomFiles = customFiles; - config._restoredModifiedFiles = modifiedFiles; - - return 'Installation finalized'; - }, - }); - } - - await prompts.tasks(postIdeTasks); - - // Retrieve restored file info for summary - const customFiles = config._restoredCustomFiles || []; - const modifiedFiles = config._restoredModifiedFiles || []; - - // Render consolidated summary - await this.renderInstallSummary(results, { - bmadDir, - modules: config.modules, - ides: config.ides, - customFiles: customFiles.length > 0 ? customFiles : undefined, - modifiedFiles: modifiedFiles.length > 0 ? modifiedFiles : undefined, - }); - - return { - success: true, - path: bmadDir, - modules: config.modules, - ides: config.ides, - projectDir: projectDir, - }; - } catch (error) { - try { - if (spinner.isSpinning) { - spinner.error('Installation failed'); - } else { - await prompts.log.error('Installation failed'); - } - } catch { - // Ensure the original error is never swallowed by a logging failure - } - throw error; - } - } - - /** - * Render a consolidated install summary using prompts.note() - * @param {Array} results - Array of {step, status: 'ok'|'error'|'warn', detail} - * @param {Object} context - {bmadDir, modules, ides, customFiles, modifiedFiles} - */ - async renderInstallSummary(results, context = {}) { - const color = await prompts.getColor(); - - // Build step lines with status indicators - const lines = []; - for (const r of results) { - let icon; - if (r.status === 'ok') { - icon = color.green('\u2713'); - } else if (r.status === 'warn') { - icon = color.yellow('!'); - } else { - icon = color.red('\u2717'); - } - const detail = r.detail ? color.dim(` (${r.detail})`) : ''; - lines.push(` ${icon} ${r.step}${detail}`); - } - - // Context and warnings - lines.push(''); - if (context.bmadDir) { - lines.push(` Installed to: ${color.dim(context.bmadDir)}`); - } - if (context.customFiles && context.customFiles.length > 0) { - lines.push(` ${color.cyan(`Custom files preserved: ${context.customFiles.length}`)}`); - } - if (context.modifiedFiles && context.modifiedFiles.length > 0) { - lines.push(` ${color.yellow(`Modified files backed up (.bak): ${context.modifiedFiles.length}`)}`); - } - - // Next steps - lines.push( - '', - ' Next steps:', - ` Read our new Docs Site: ${color.dim('https://docs.bmad-method.org/')}`, - ` Join our Discord: ${color.dim('https://discord.gg/gk8jAdXWmj')}`, - ` Star us on GitHub: ${color.dim('https://github.com/bmad-code-org/BMAD-METHOD/')}`, - ` Subscribe on YouTube: ${color.dim('https://www.youtube.com/@BMadCode')}`, - ` Run ${color.cyan('/bmad-help')} with your IDE Agent and ask it how to get started`, - ); - - await prompts.note(lines.join('\n'), 'BMAD is ready to use!'); - } - - /** - * Update existing installation - */ - async update(config) { - const spinner = await prompts.spinner(); - spinner.start('Checking installation...'); - - try { - const projectDir = path.resolve(config.directory); - const { bmadDir } = await this.findBmadDir(projectDir); - const existingInstall = await this.detector.detect(bmadDir); - - if (!existingInstall.installed) { - spinner.stop('No BMAD installation found'); - throw new Error(`No BMAD installation found at ${bmadDir}`); - } - - spinner.message('Analyzing update requirements...'); - - // Compare versions and determine what needs updating - const currentVersion = existingInstall.version; - const newVersion = require(path.join(getProjectRoot(), 'package.json')).version; - - // Check for custom modules with missing sources before update - const customModuleSources = new Map(); - - // Check manifest for backward compatibility - if (existingInstall.customModules) { - for (const customModule of existingInstall.customModules) { - customModuleSources.set(customModule.id, customModule); - } - } - - // Also check cache directory - const cacheDir = path.join(bmadDir, '_config', 'custom'); - if (await fs.pathExists(cacheDir)) { - const cachedModules = await fs.readdir(cacheDir, { withFileTypes: true }); - - for (const cachedModule of cachedModules) { - if (cachedModule.isDirectory()) { - const moduleId = cachedModule.name; - - // Skip if we already have this module - if (customModuleSources.has(moduleId)) { - continue; - } - - // Check if this is an external official module - skip cache for those - const isExternal = await this.moduleManager.isExternalModule(moduleId); - if (isExternal) { - // External modules are handled via cloneExternalModule, not from cache - continue; - } - - const cachedPath = path.join(cacheDir, moduleId); - - // Check if this is actually a custom module (has module.yaml) - const moduleYamlPath = path.join(cachedPath, 'module.yaml'); - if (await fs.pathExists(moduleYamlPath)) { - customModuleSources.set(moduleId, { - id: moduleId, - name: moduleId, - sourcePath: path.join('_config', 'custom', moduleId), // Relative path - cached: true, - }); - } - } - } - } - - if (customModuleSources.size > 0) { - spinner.stop('Update analysis complete'); - await prompts.log.warn('Checking custom module sources before update...'); - - const projectRoot = getProjectRoot(); - await this.handleMissingCustomSources( - customModuleSources, - bmadDir, - projectRoot, - 'update', - existingInstall.modules.map((m) => m.id), - config.skipPrompts || false, - ); - - spinner.start('Preparing update...'); - } - - if (config.dryRun) { - spinner.stop('Dry run analysis complete'); - let dryRunContent = `Current version: ${currentVersion}\n`; - dryRunContent += `New version: ${newVersion}\n`; - dryRunContent += `Core: ${existingInstall.hasCore ? 'Will be updated' : 'Not installed'}`; - - if (existingInstall.modules.length > 0) { - dryRunContent += '\n\nModules to update:'; - for (const mod of existingInstall.modules) { - dryRunContent += `\n - ${mod.id}`; - } - } - await prompts.note(dryRunContent, 'Update Preview (Dry Run)'); - return; - } - - // Perform actual update - if (existingInstall.hasCore) { - spinner.message('Updating core...'); - await this.updateCore(bmadDir, config.force); - } - - for (const module of existingInstall.modules) { - spinner.message(`Updating module: ${module.id}...`); - await this.moduleManager.update(module.id, bmadDir, config.force, { installer: this }); - } - - // Update manifest - spinner.message('Updating manifest...'); - await this.manifest.update(bmadDir, { - version: newVersion, - updateDate: new Date().toISOString(), - }); - - spinner.stop('Update complete'); - return { success: true }; - } catch (error) { - spinner.error('Update failed'); - throw error; - } - } - - /** - * Get installation status - */ - async getStatus(directory) { - const projectDir = path.resolve(directory); - const { bmadDir } = await this.findBmadDir(projectDir); - return await this.detector.detect(bmadDir); - } - - /** - * Get available modules - */ - async getAvailableModules() { - return await this.moduleManager.listAvailable(); - } - - /** - * Uninstall BMAD with selective removal options - * @param {string} directory - Project directory - * @param {Object} options - Uninstall options - * @param {boolean} [options.removeModules=true] - Remove _bmad/ directory - * @param {boolean} [options.removeIdeConfigs=true] - Remove IDE configurations - * @param {boolean} [options.removeOutputFolder=false] - Remove user artifacts output folder - * @returns {Object} Result with success status and removed components - */ - async uninstall(directory, options = {}) { - const projectDir = path.resolve(directory); - const { bmadDir } = await this.findBmadDir(projectDir); - - if (!(await fs.pathExists(bmadDir))) { - return { success: false, reason: 'not-installed' }; - } - - // 1. DETECT: Read state BEFORE deleting anything - const existingInstall = await this.detector.detect(bmadDir); - const outputFolder = await this._readOutputFolder(bmadDir); - - const removed = { modules: false, ideConfigs: false, outputFolder: false }; - - // 2. IDE CLEANUP (before _bmad/ deletion so configs are accessible) - if (options.removeIdeConfigs !== false) { - await this.uninstallIdeConfigs(projectDir, existingInstall, { silent: options.silent }); - removed.ideConfigs = true; - } - - // 3. OUTPUT FOLDER (only if explicitly requested) - if (options.removeOutputFolder === true && outputFolder) { - removed.outputFolder = await this.uninstallOutputFolder(projectDir, outputFolder); - } - - // 4. BMAD DIRECTORY (last, after everything that needs it) - if (options.removeModules !== false) { - removed.modules = await this.uninstallModules(projectDir); - } - - return { success: true, removed, version: existingInstall.version }; - } - - /** - * Uninstall IDE configurations only - * @param {string} projectDir - Project directory - * @param {Object} existingInstall - Detection result from detector.detect() - * @param {Object} [options] - Options (e.g. { silent: true }) - * @returns {Promise} Results from IDE cleanup - */ - async uninstallIdeConfigs(projectDir, existingInstall, options = {}) { - await this.ideManager.ensureInitialized(); - const cleanupOptions = { isUninstall: true, silent: options.silent }; - const ideList = existingInstall.ides || []; - if (ideList.length > 0) { - return this.ideManager.cleanupByList(projectDir, ideList, cleanupOptions); - } - return this.ideManager.cleanup(projectDir, cleanupOptions); - } - - /** - * Remove user artifacts output folder - * @param {string} projectDir - Project directory - * @param {string} outputFolder - Output folder name (relative) - * @returns {Promise} Whether the folder was removed - */ - async uninstallOutputFolder(projectDir, outputFolder) { - if (!outputFolder) return false; - const resolvedProject = path.resolve(projectDir); - const outputPath = path.resolve(resolvedProject, outputFolder); - if (!outputPath.startsWith(resolvedProject + path.sep)) { - return false; - } - if (await fs.pathExists(outputPath)) { - await fs.remove(outputPath); - return true; - } - return false; - } - - /** - * Remove the _bmad/ directory - * @param {string} projectDir - Project directory - * @returns {Promise} Whether the directory was removed - */ - async uninstallModules(projectDir) { - const { bmadDir } = await this.findBmadDir(projectDir); - if (await fs.pathExists(bmadDir)) { - await fs.remove(bmadDir); - return true; - } - return false; - } - - /** - * Get the configured output folder name for a project - * Resolves bmadDir internally from projectDir - * @param {string} projectDir - Project directory - * @returns {string} Output folder name (relative, default: '_bmad-output') - */ - async getOutputFolder(projectDir) { - const { bmadDir } = await this.findBmadDir(projectDir); - return this._readOutputFolder(bmadDir); - } - - /** - * Read the output_folder setting from module config files - * Checks bmm/config.yaml first, then other module configs - * @param {string} bmadDir - BMAD installation directory - * @returns {string} Output folder path or default - */ - async _readOutputFolder(bmadDir) { - const yaml = require('yaml'); - - // Check bmm/config.yaml first (most common) - const bmmConfigPath = path.join(bmadDir, 'bmm', 'config.yaml'); - if (await fs.pathExists(bmmConfigPath)) { - try { - const content = await fs.readFile(bmmConfigPath, 'utf8'); - const config = yaml.parse(content); - if (config && config.output_folder) { - // Strip {project-root}/ prefix if present - return config.output_folder.replace(/^\{project-root\}[/\\]/, ''); - } - } catch { - // Fall through to other modules - } - } - - // Scan other module config.yaml files - try { - const entries = await fs.readdir(bmadDir, { withFileTypes: true }); - for (const entry of entries) { - if (!entry.isDirectory() || entry.name === 'bmm' || entry.name.startsWith('_')) continue; - const configPath = path.join(bmadDir, entry.name, 'config.yaml'); - if (await fs.pathExists(configPath)) { - try { - const content = await fs.readFile(configPath, 'utf8'); - const config = yaml.parse(content); - if (config && config.output_folder) { - return config.output_folder.replace(/^\{project-root\}[/\\]/, ''); - } - } catch { - // Continue scanning - } - } - } - } catch { - // Directory scan failed - } - - // Default fallback - return '_bmad-output'; - } - - /** - * Private: Create directory structure - */ - /** - * Merge all module-help.csv files into a single bmad-help.csv - * Scans all installed modules for module-help.csv and merges them - * Enriches agent info from agent-manifest.csv - * Output is written to _bmad/_config/bmad-help.csv - * @param {string} bmadDir - BMAD installation directory - */ - async mergeModuleHelpCatalogs(bmadDir) { - const allRows = []; - const headerRow = - 'module,phase,name,code,sequence,workflow-file,command,required,agent-name,agent-command,agent-display-name,agent-title,options,description,output-location,outputs'; - - // Load agent manifest for agent info lookup - const agentManifestPath = path.join(bmadDir, '_config', 'agent-manifest.csv'); - const agentInfo = new Map(); // agent-name -> {command, displayName, title+icon} - - if (await fs.pathExists(agentManifestPath)) { - const manifestContent = await fs.readFile(agentManifestPath, 'utf8'); - const lines = manifestContent.split('\n').filter((line) => line.trim()); - - for (const line of lines) { - if (line.startsWith('name,')) continue; // Skip header - - const cols = line.split(','); - if (cols.length >= 4) { - const agentName = cols[0].replaceAll('"', '').trim(); - const displayName = cols[1].replaceAll('"', '').trim(); - const title = cols[2].replaceAll('"', '').trim(); - const icon = cols[3].replaceAll('"', '').trim(); - const module = cols[10] ? cols[10].replaceAll('"', '').trim() : ''; - - // Build agent command: bmad:module:agent:name - const agentCommand = module ? `bmad:${module}:agent:${agentName}` : `bmad:agent:${agentName}`; - - agentInfo.set(agentName, { - command: agentCommand, - displayName: displayName || agentName, - title: icon && title ? `${icon} ${title}` : title || agentName, - }); - } - } - } - - // Get all installed module directories - const entries = await fs.readdir(bmadDir, { withFileTypes: true }); - const installedModules = entries - .filter((entry) => entry.isDirectory() && entry.name !== '_config' && entry.name !== 'docs' && entry.name !== '_memory') - .map((entry) => entry.name); - - // Add core module to scan (it's installed at root level as _config, but we check src/core) - const coreModulePath = getSourcePath('core'); - const modulePaths = new Map(); - - // Map all module source paths - if (await fs.pathExists(coreModulePath)) { - modulePaths.set('core', coreModulePath); - } - - // Map installed module paths - for (const moduleName of installedModules) { - const modulePath = path.join(bmadDir, moduleName); - modulePaths.set(moduleName, modulePath); - } - - // Scan each module for module-help.csv - for (const [moduleName, modulePath] of modulePaths) { - const helpFilePath = path.join(modulePath, 'module-help.csv'); - - if (await fs.pathExists(helpFilePath)) { - try { - const content = await fs.readFile(helpFilePath, 'utf8'); - const lines = content.split('\n').filter((line) => line.trim() && !line.startsWith('#')); - - for (const line of lines) { - // Skip header row - if (line.startsWith('module,')) { - continue; - } - - // Parse the line - handle quoted fields with commas - const columns = this.parseCSVLine(line); - if (columns.length >= 12) { - // Map old schema to new schema - // Old: module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs - // New: module,phase,name,code,sequence,workflow-file,command,required,agent-name,agent-command,agent-display-name,agent-title,options,description,output-location,outputs - - const [ - module, - phase, - name, - code, - sequence, - workflowFile, - command, - required, - agentName, - options, - description, - outputLocation, - outputs, - ] = columns; - - // If module column is empty, set it to this module's name (except for core which stays empty for universal tools) - const finalModule = (!module || module.trim() === '') && moduleName !== 'core' ? moduleName : module || ''; - - // Lookup agent info - const cleanAgentName = agentName ? agentName.trim() : ''; - const agentData = agentInfo.get(cleanAgentName) || { command: '', displayName: '', title: '' }; - - // Build new row with agent info - const newRow = [ - finalModule, - phase || '', - name || '', - code || '', - sequence || '', - workflowFile || '', - command || '', - required || 'false', - cleanAgentName, - agentData.command, - agentData.displayName, - agentData.title, - options || '', - description || '', - outputLocation || '', - outputs || '', - ]; - - allRows.push(newRow.map((c) => this.escapeCSVField(c)).join(',')); - } - } - - if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.message(` Merged module-help from: ${moduleName}`); - } - } catch (error) { - await prompts.log.warn(` Warning: Failed to read module-help.csv from ${moduleName}: ${error.message}`); - } - } - } - - // Sort by module, then phase, then sequence - allRows.sort((a, b) => { - const colsA = this.parseCSVLine(a); - const colsB = this.parseCSVLine(b); - - // Module comparison (empty module/universal tools come first) - const moduleA = (colsA[0] || '').toLowerCase(); - const moduleB = (colsB[0] || '').toLowerCase(); - if (moduleA !== moduleB) { - return moduleA.localeCompare(moduleB); - } - - // Phase comparison - const phaseA = colsA[1] || ''; - const phaseB = colsB[1] || ''; - if (phaseA !== phaseB) { - return phaseA.localeCompare(phaseB); - } - - // Sequence comparison - const seqA = parseInt(colsA[4] || '0', 10); - const seqB = parseInt(colsB[4] || '0', 10); - return seqA - seqB; - }); - - // Write merged catalog - const outputDir = path.join(bmadDir, '_config'); - await fs.ensureDir(outputDir); - const outputPath = path.join(outputDir, 'bmad-help.csv'); - - const mergedContent = [headerRow, ...allRows].join('\n'); - await fs.writeFile(outputPath, mergedContent, 'utf8'); - - // Track the installed file - this.installedFiles.add(outputPath); - - if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.message(` Generated bmad-help.csv: ${allRows.length} workflows`); - } - } - - /** - * Parse a CSV line, handling quoted fields - * @param {string} line - CSV line to parse - * @returns {Array} Array of field values - */ - parseCSVLine(line) { - const result = []; - let current = ''; - let inQuotes = false; - - for (let i = 0; i < line.length; i++) { - const char = line[i]; - const nextChar = line[i + 1]; - - if (char === '"') { - if (inQuotes && nextChar === '"') { - // Escaped quote - current += '"'; - i++; // Skip next quote - } else { - // Toggle quote mode - inQuotes = !inQuotes; - } - } else if (char === ',' && !inQuotes) { - result.push(current); - current = ''; - } else { - current += char; - } - } - result.push(current); - return result; - } - - /** - * Escape a CSV field if it contains special characters - * @param {string} field - Field value to escape - * @returns {string} Escaped field - */ - escapeCSVField(field) { - if (field === null || field === undefined) { - return ''; - } - const str = String(field); - // If field contains comma, quote, or newline, wrap in quotes and escape inner quotes - if (str.includes(',') || str.includes('"') || str.includes('\n')) { - return `"${str.replaceAll('"', '""')}"`; - } - return str; - } - - async createDirectoryStructure(bmadDir) { - await fs.ensureDir(bmadDir); - await fs.ensureDir(path.join(bmadDir, '_config')); - await fs.ensureDir(path.join(bmadDir, '_config', 'agents')); - await fs.ensureDir(path.join(bmadDir, '_config', 'custom')); - } - - /** - * Generate clean config.yaml files for each installed module - * @param {string} bmadDir - BMAD installation directory - * @param {Object} moduleConfigs - Collected configuration values - */ - async generateModuleConfigs(bmadDir, moduleConfigs) { - const yaml = require('yaml'); - - // Extract core config values to share with other modules - const coreConfig = moduleConfigs.core || {}; - - // Get all installed module directories - const entries = await fs.readdir(bmadDir, { withFileTypes: true }); - const installedModules = entries - .filter((entry) => entry.isDirectory() && entry.name !== '_config' && entry.name !== 'docs') - .map((entry) => entry.name); - - // Generate config.yaml for each installed module - for (const moduleName of installedModules) { - const modulePath = path.join(bmadDir, moduleName); - - // Get module-specific config or use empty object if none - const config = moduleConfigs[moduleName] || {}; - - if (await fs.pathExists(modulePath)) { - const configPath = path.join(modulePath, 'config.yaml'); - - // Create header - const packageJson = require(path.join(getProjectRoot(), 'package.json')); - const header = `# ${moduleName.toUpperCase()} Module Configuration -# Generated by BMAD installer -# Version: ${packageJson.version} -# Date: ${new Date().toISOString()} - -`; - - // For non-core modules, add core config values directly - let finalConfig = { ...config }; - let coreSection = ''; - - if (moduleName !== 'core' && coreConfig && Object.keys(coreConfig).length > 0) { - // Add core values directly to the module config - // These will be available for reference in the module - finalConfig = { - ...config, - ...coreConfig, // Spread core config values directly into the module config - }; - - // Create a comment section to identify core values - coreSection = '\n# Core Configuration Values\n'; - } - - // Clean the config to remove any non-serializable values (like functions) - const cleanConfig = structuredClone(finalConfig); - - // Convert config to YAML - let yamlContent = yaml.stringify(cleanConfig, { - indent: 2, - lineWidth: 0, - minContentWidth: 0, - }); - - // If we have core values, reorganize the YAML to group them with their comment - if (coreSection && moduleName !== 'core') { - // Split the YAML into lines - const lines = yamlContent.split('\n'); - const moduleConfigLines = []; - const coreConfigLines = []; - - // Separate module-specific and core config lines - for (const line of lines) { - const key = line.split(':')[0].trim(); - if (Object.prototype.hasOwnProperty.call(coreConfig, key)) { - coreConfigLines.push(line); - } else { - moduleConfigLines.push(line); - } - } - - // Rebuild YAML with module config first, then core config with comment - yamlContent = moduleConfigLines.join('\n'); - if (coreConfigLines.length > 0) { - yamlContent += coreSection + coreConfigLines.join('\n'); - } - } - - // Write the clean config file with POSIX-compliant final newline - const content = header + yamlContent; - await fs.writeFile(configPath, content.endsWith('\n') ? content : content + '\n', 'utf8'); - - // Track the config file in installedFiles - this.installedFiles.add(configPath); - } - } - } - - /** - * Install core with resolved dependencies - * @param {string} bmadDir - BMAD installation directory - * @param {Object} coreFiles - Core files to install - */ - async installCoreWithDependencies(bmadDir, coreFiles) { - const sourcePath = getModulePath('core'); - const targetPath = path.join(bmadDir, 'core'); - await this.installCore(bmadDir); - } - - /** - * Install module with resolved dependencies - * @param {string} moduleName - Module name - * @param {string} bmadDir - BMAD installation directory - * @param {Object} moduleFiles - Module files to install - */ - async installModuleWithDependencies(moduleName, bmadDir, moduleFiles) { - // Get module configuration for conditional installation - const moduleConfig = this.configCollector.collectedConfig[moduleName] || {}; - - // Use existing module manager for full installation with file tracking - // Note: Module-specific installers are called separately after IDE setup - await this.moduleManager.install( - moduleName, - bmadDir, - (filePath) => { - this.installedFiles.add(filePath); - }, - { - skipModuleInstaller: true, // We'll run it later after IDE setup - moduleConfig: moduleConfig, // Pass module config for conditional filtering - installer: this, - silent: true, - }, - ); - - // Process agent files to build YAML agents and create customize templates - const modulePath = path.join(bmadDir, moduleName); - await this.processAgentFiles(modulePath, moduleName); - - // Dependencies are already included in full module install - } - - /** - * Install partial module (only dependencies needed by other modules) - */ - async installPartialModule(moduleName, bmadDir, files) { - const sourceBase = getModulePath(moduleName); - const targetBase = path.join(bmadDir, moduleName); - - // Create module directory - await fs.ensureDir(targetBase); - - // Copy only the required dependency files - if (files.agents && files.agents.length > 0) { - const agentsDir = path.join(targetBase, 'agents'); - await fs.ensureDir(agentsDir); - - for (const agentPath of files.agents) { - const fileName = path.basename(agentPath); - const sourcePath = path.join(sourceBase, 'agents', fileName); - const targetPath = path.join(agentsDir, fileName); - - if (await fs.pathExists(sourcePath)) { - await this.copyFileWithPlaceholderReplacement(sourcePath, targetPath); - this.installedFiles.add(targetPath); - } - } - } - - if (files.tasks && files.tasks.length > 0) { - const tasksDir = path.join(targetBase, 'tasks'); - await fs.ensureDir(tasksDir); - - for (const taskPath of files.tasks) { - const fileName = path.basename(taskPath); - const sourcePath = path.join(sourceBase, 'tasks', fileName); - const targetPath = path.join(tasksDir, fileName); - - if (await fs.pathExists(sourcePath)) { - await this.copyFileWithPlaceholderReplacement(sourcePath, targetPath); - this.installedFiles.add(targetPath); - } - } - } - - if (files.tools && files.tools.length > 0) { - const toolsDir = path.join(targetBase, 'tools'); - await fs.ensureDir(toolsDir); - - for (const toolPath of files.tools) { - const fileName = path.basename(toolPath); - const sourcePath = path.join(sourceBase, 'tools', fileName); - const targetPath = path.join(toolsDir, fileName); - - if (await fs.pathExists(sourcePath)) { - await this.copyFileWithPlaceholderReplacement(sourcePath, targetPath); - this.installedFiles.add(targetPath); - } - } - } - - if (files.templates && files.templates.length > 0) { - const templatesDir = path.join(targetBase, 'templates'); - await fs.ensureDir(templatesDir); - - for (const templatePath of files.templates) { - const fileName = path.basename(templatePath); - const sourcePath = path.join(sourceBase, 'templates', fileName); - const targetPath = path.join(templatesDir, fileName); - - if (await fs.pathExists(sourcePath)) { - await this.copyFileWithPlaceholderReplacement(sourcePath, targetPath); - this.installedFiles.add(targetPath); - } - } - } - - if (files.data && files.data.length > 0) { - for (const dataPath of files.data) { - // Preserve directory structure for data files - const relative = path.relative(sourceBase, dataPath); - const targetPath = path.join(targetBase, relative); - - await fs.ensureDir(path.dirname(targetPath)); - - if (await fs.pathExists(dataPath)) { - await this.copyFileWithPlaceholderReplacement(dataPath, targetPath); - this.installedFiles.add(targetPath); - } - } - } - - // Create a marker file to indicate this is a partial installation - const markerPath = path.join(targetBase, '.partial'); - await fs.writeFile( - markerPath, - `This module contains only dependencies required by other modules.\nInstalled: ${new Date().toISOString()}\n`, - ); - } - - /** - * Private: Install core - * @param {string} bmadDir - BMAD installation directory - */ - async installCore(bmadDir) { - const sourcePath = getModulePath('core'); - const targetPath = path.join(bmadDir, 'core'); - - // Copy core files (skip .agent.yaml files like modules do) - await this.copyCoreFiles(sourcePath, targetPath); - - // Compile agents using the same compiler as modules - const { ModuleManager } = require('../modules/manager'); - const moduleManager = new ModuleManager(); - await moduleManager.compileModuleAgents(sourcePath, targetPath, 'core', bmadDir, this); - - // Process agent files to inject activation block - await this.processAgentFiles(targetPath, 'core'); - } - - /** - * Copy core files (similar to copyModuleWithFiltering but for core) - * @param {string} sourcePath - Source path - * @param {string} targetPath - Target path - */ - async copyCoreFiles(sourcePath, targetPath) { - // Get all files in source - const files = await this.getFileList(sourcePath); - - for (const file of files) { - // Skip sub-modules directory - these are IDE-specific and handled separately - if (file.startsWith('sub-modules/')) { - continue; - } - - // Skip sidecar directories - they are handled separately during agent compilation - if ( - path - .dirname(file) - .split('/') - .some((dir) => dir.toLowerCase().includes('sidecar')) - ) { - continue; - } - - // Skip module.yaml at root - it's only needed at install time - if (file === 'module.yaml') { - continue; - } - - // Skip config.yaml templates - we'll generate clean ones with actual values - if (file === 'config.yaml' || file.endsWith('/config.yaml') || file === 'custom.yaml' || file.endsWith('/custom.yaml')) { - continue; - } - - // Skip .agent.yaml files - they will be compiled separately - if (file.endsWith('.agent.yaml')) { - continue; - } - - const sourceFile = path.join(sourcePath, file); - const targetFile = path.join(targetPath, file); - - // Check if this is an agent file - if (file.startsWith('agents/') && file.endsWith('.md')) { - // Read the file to check for localskip - const content = await fs.readFile(sourceFile, 'utf8'); - - // Check for localskip="true" in the agent tag - const agentMatch = content.match(/]*\slocalskip="true"[^>]*>/); - if (agentMatch) { - await prompts.log.message(` Skipping web-only agent: ${path.basename(file)}`); - continue; // Skip this agent - } - } - - // Copy the file with placeholder replacement - await fs.ensureDir(path.dirname(targetFile)); - await this.copyFileWithPlaceholderReplacement(sourceFile, targetFile); - - // Track the installed file - this.installedFiles.add(targetFile); - } - } - - /** - * Get list of all files in a directory recursively - * @param {string} dir - Directory path - * @param {string} baseDir - Base directory for relative paths - * @returns {Array} List of relative file paths - */ - async getFileList(dir, baseDir = dir) { - const files = []; - const entries = await fs.readdir(dir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(dir, entry.name); - - if (entry.isDirectory()) { - const subFiles = await this.getFileList(fullPath, baseDir); - files.push(...subFiles); - } else { - files.push(path.relative(baseDir, fullPath)); - } - } - - return files; - } - - /** - * Process agent files to build YAML agents and inject activation blocks - * @param {string} modulePath - Path to module in bmad/ installation - * @param {string} moduleName - Module name - */ - async processAgentFiles(modulePath, moduleName) { - const agentsPath = path.join(modulePath, 'agents'); - - // Check if agents directory exists - if (!(await fs.pathExists(agentsPath))) { - return; // No agents to process - } - - // Determine project directory (parent of bmad/ directory) - const bmadDir = path.dirname(modulePath); - const cfgAgentsDir = path.join(bmadDir, '_config', 'agents'); - - // Ensure _config/agents directory exists - await fs.ensureDir(cfgAgentsDir); - - // Get all agent files - const agentFiles = await fs.readdir(agentsPath); - - for (const agentFile of agentFiles) { - // Skip .agent.yaml files - they should already be compiled by compileModuleAgents - if (agentFile.endsWith('.agent.yaml')) { - continue; - } - - // Only process .md files (already compiled from YAML) - if (!agentFile.endsWith('.md')) { - continue; - } - - const agentName = agentFile.replace('.md', ''); - const mdPath = path.join(agentsPath, agentFile); - const customizePath = path.join(cfgAgentsDir, `${moduleName}-${agentName}.customize.yaml`); - - // For .md files that are already compiled, we don't need to do much - // Just ensure the customize template exists - if (!(await fs.pathExists(customizePath))) { - const genericTemplatePath = getSourcePath('utility', 'agent-components', 'agent.customize.template.yaml'); - if (await fs.pathExists(genericTemplatePath)) { - await this.copyFileWithPlaceholderReplacement(genericTemplatePath, customizePath); - if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.message(` Created customize: ${moduleName}-${agentName}.customize.yaml`); - } - } - } - } - } - - /** - * Private: Update core - */ - async updateCore(bmadDir, force = false) { - const sourcePath = getModulePath('core'); - const targetPath = path.join(bmadDir, 'core'); - - if (force) { - await fs.remove(targetPath); - await this.installCore(bmadDir); - } else { - // Selective update - preserve user modifications - await this.fileOps.syncDirectory(sourcePath, targetPath); - - // Recompile agents (#1133) - const { ModuleManager } = require('../modules/manager'); - const moduleManager = new ModuleManager(); - await moduleManager.compileModuleAgents(sourcePath, targetPath, 'core', bmadDir, this); - await this.processAgentFiles(targetPath, 'core'); - } - } - - /** - * Quick update method - preserves all settings and only prompts for new config fields - * @param {Object} config - Configuration with directory - * @returns {Object} Update result - */ - async quickUpdate(config) { - const spinner = await prompts.spinner(); - spinner.start('Starting quick update...'); - - try { - const projectDir = path.resolve(config.directory); - const { bmadDir } = await this.findBmadDir(projectDir); - - // Check if bmad directory exists - if (!(await fs.pathExists(bmadDir))) { - spinner.stop('No BMAD installation found'); - throw new Error(`BMAD not installed at ${bmadDir}. Use regular install for first-time setup.`); - } - - spinner.message('Detecting installed modules and configuration...'); - - // Detect existing installation - const existingInstall = await this.detector.detect(bmadDir); - const installedModules = existingInstall.modules.map((m) => m.id); - const configuredIdes = existingInstall.ides || []; - const projectRoot = path.dirname(bmadDir); - - // Get custom module sources: first from --custom-content (re-cache from source), then from cache - const customModuleSources = new Map(); - if (config.customContent?.sources?.length > 0) { - for (const source of config.customContent.sources) { - if (source.id && source.path && (await fs.pathExists(source.path))) { - customModuleSources.set(source.id, { - id: source.id, - name: source.name || source.id, - sourcePath: source.path, - cached: false, // From CLI, will be re-cached - }); - } - } - } - const cacheDir = path.join(bmadDir, '_config', 'custom'); - if (await fs.pathExists(cacheDir)) { - const cachedModules = await fs.readdir(cacheDir, { withFileTypes: true }); - - for (const cachedModule of cachedModules) { - const moduleId = cachedModule.name; - const cachedPath = path.join(cacheDir, moduleId); - - // Skip if path doesn't exist (broken symlink, deleted dir) - avoids lstat ENOENT - if (!(await fs.pathExists(cachedPath))) { - continue; - } - if (!cachedModule.isDirectory()) { - continue; - } - - // Skip if we already have this module from manifest - if (customModuleSources.has(moduleId)) { - continue; - } - - // Check if this is an external official module - skip cache for those - const isExternal = await this.moduleManager.isExternalModule(moduleId); - if (isExternal) { - // External modules are handled via cloneExternalModule, not from cache - continue; - } - - // Check if this is actually a custom module (has module.yaml) - const moduleYamlPath = path.join(cachedPath, 'module.yaml'); - if (await fs.pathExists(moduleYamlPath)) { - // For quick update, we always rebuild from cache - customModuleSources.set(moduleId, { - id: moduleId, - name: moduleId, // We'll read the actual name if needed - sourcePath: cachedPath, - cached: true, // Flag to indicate this is from cache - }); - } - } - } - - // Load saved IDE configurations - const savedIdeConfigs = await this.ideConfigManager.loadAllIdeConfigs(bmadDir); - - // Get available modules (what we have source for) - const availableModulesData = await this.moduleManager.listAvailable(); - const availableModules = [...availableModulesData.modules, ...availableModulesData.customModules]; - - // Add external official modules to available modules - // These can always be obtained by cloning from their remote URLs - const { ExternalModuleManager } = require('../modules/external-manager'); - const externalManager = new ExternalModuleManager(); - const externalModules = await externalManager.listAvailable(); - for (const externalModule of externalModules) { - // Only add if not already in the list and is installed - if (installedModules.includes(externalModule.code) && !availableModules.some((m) => m.id === externalModule.code)) { - availableModules.push({ - id: externalModule.code, - name: externalModule.name, - isExternal: true, - fromExternal: true, - }); - } - } - - // Add custom modules from manifest if their sources exist - for (const [moduleId, customModule] of customModuleSources) { - // Use the absolute sourcePath - const sourcePath = customModule.sourcePath; - - // Check if source exists at the recorded path - if ( - sourcePath && - (await fs.pathExists(sourcePath)) && // Add to available modules if not already there - !availableModules.some((m) => m.id === moduleId) - ) { - availableModules.push({ - id: moduleId, - name: customModule.name || moduleId, - path: sourcePath, - isCustom: true, - fromManifest: true, - }); - } - } - - // Handle missing custom module sources using shared method - const customModuleResult = await this.handleMissingCustomSources( - customModuleSources, - bmadDir, - projectRoot, - 'update', - installedModules, - config.skipPrompts || false, - ); - - const { validCustomModules, keptModulesWithoutSources } = customModuleResult; - - const customModulesFromManifest = validCustomModules.map((m) => ({ - ...m, - isCustom: true, - hasUpdate: true, - })); - - const allAvailableModules = [...availableModules, ...customModulesFromManifest]; - const availableModuleIds = new Set(allAvailableModules.map((m) => m.id)); - - // Core module is special - never include it in update flow - const nonCoreInstalledModules = installedModules.filter((id) => id !== 'core'); - - // Only update modules that are BOTH installed AND available (we have source for) - const modulesToUpdate = nonCoreInstalledModules.filter((id) => availableModuleIds.has(id)); - const skippedModules = nonCoreInstalledModules.filter((id) => !availableModuleIds.has(id)); - - // Add custom modules that were kept without sources to the skipped modules - // This ensures their agents are preserved in the manifest - for (const keptModule of keptModulesWithoutSources) { - if (!skippedModules.includes(keptModule)) { - skippedModules.push(keptModule); - } - } - - spinner.stop(`Found ${modulesToUpdate.length} module(s) to update and ${configuredIdes.length} configured tool(s)`); - - if (skippedModules.length > 0) { - await prompts.log.warn(`Skipping ${skippedModules.length} module(s) - no source available: ${skippedModules.join(', ')}`); - } - - // Load existing configs and collect new fields (if any) - await prompts.log.info('Checking for new configuration options...'); - await this.configCollector.loadExistingConfig(projectDir); - - let promptedForNewFields = false; - - // Check core config for new fields - const corePrompted = await this.configCollector.collectModuleConfigQuick('core', projectDir, true); - if (corePrompted) { - promptedForNewFields = true; - } - - // Check each module we're updating for new fields (NOT skipped modules) - for (const moduleName of modulesToUpdate) { - const modulePrompted = await this.configCollector.collectModuleConfigQuick(moduleName, projectDir, true); - if (modulePrompted) { - promptedForNewFields = true; - } - } - - if (!promptedForNewFields) { - await prompts.log.success('All configuration is up to date, no new options to configure'); - } - - // Add metadata - this.configCollector.collectedConfig._meta = { - version: require(path.join(getProjectRoot(), 'package.json')).version, - installDate: new Date().toISOString(), - lastModified: new Date().toISOString(), - }; - - // Build the config object for the installer - const installConfig = { - directory: projectDir, - installCore: true, - modules: modulesToUpdate, // Only update modules we have source for - ides: configuredIdes, - skipIde: configuredIdes.length === 0, - coreConfig: this.configCollector.collectedConfig.core, - actionType: 'install', // Use regular install flow - _quickUpdate: true, // Flag to skip certain prompts - _preserveModules: skippedModules, // Preserve these in manifest even though we didn't update them - _savedIdeConfigs: savedIdeConfigs, // Pass saved IDE configs to installer - _customModuleSources: customModuleSources, // Pass custom module sources for updates - _existingModules: installedModules, // Pass all installed modules for manifest generation - customContent: config.customContent, // Pass through for re-caching from source - }; - - // Call the standard install method - const result = await this.install(installConfig); - - // Only succeed the spinner if it's still spinning - // (install method might have stopped it if folder name changed) - if (spinner.isSpinning) { - spinner.stop('Quick update complete!'); - } - - return { - success: true, - moduleCount: modulesToUpdate.length + 1, // +1 for core - hadNewFields: promptedForNewFields, - modules: ['core', ...modulesToUpdate], - skippedModules: skippedModules, - ides: configuredIdes, - }; - } catch (error) { - spinner.error('Quick update failed'); - throw error; - } - } - - /** - * Compile agents with customizations only - * @param {Object} config - Configuration with directory - * @returns {Object} Compilation result - */ - async compileAgents(config) { - // Using @clack prompts - const { ModuleManager } = require('../modules/manager'); - const { getSourcePath } = require('../../../lib/project-root'); - - const spinner = await prompts.spinner(); - spinner.start('Recompiling agents with customizations...'); - - try { - const projectDir = path.resolve(config.directory); - const { bmadDir } = await this.findBmadDir(projectDir); - - // Check if bmad directory exists - if (!(await fs.pathExists(bmadDir))) { - spinner.stop('No BMAD installation found'); - throw new Error(`BMAD not installed at ${bmadDir}. Use regular install for first-time setup.`); - } - - // Detect existing installation - const existingInstall = await this.detector.detect(bmadDir); - const installedModules = existingInstall.modules.map((m) => m.id); - - // Initialize module manager - const moduleManager = new ModuleManager(); - moduleManager.setBmadFolderName(path.basename(bmadDir)); - - let totalAgentCount = 0; - - // Get custom module sources from cache - const customModuleSources = new Map(); - const cacheDir = path.join(bmadDir, '_config', 'custom'); - if (await fs.pathExists(cacheDir)) { - const cachedModules = await fs.readdir(cacheDir, { withFileTypes: true }); - - for (const cachedModule of cachedModules) { - if (cachedModule.isDirectory()) { - const moduleId = cachedModule.name; - const cachedPath = path.join(cacheDir, moduleId); - const moduleYamlPath = path.join(cachedPath, 'module.yaml'); - - // Check if this is actually a custom module - if (await fs.pathExists(moduleYamlPath)) { - // Check if this is an external official module - skip cache for those - const isExternal = await this.moduleManager.isExternalModule(moduleId); - if (isExternal) { - // External modules are handled via cloneExternalModule, not from cache - continue; - } - customModuleSources.set(moduleId, cachedPath); - } - } - } - } - - // Process each installed module - for (const moduleId of installedModules) { - spinner.message(`Recompiling agents in ${moduleId}...`); - - // Get source path - let sourcePath; - if (moduleId === 'core') { - sourcePath = getSourcePath('core'); - } else { - // First check if it's in the custom cache - if (customModuleSources.has(moduleId)) { - sourcePath = customModuleSources.get(moduleId); - } else { - sourcePath = await moduleManager.findModuleSource(moduleId); - } - } - - if (!sourcePath) { - await prompts.log.warn(`Source not found for module ${moduleId}, skipping...`); - continue; - } - - const targetPath = path.join(bmadDir, moduleId); - - // Compile agents for this module - await moduleManager.compileModuleAgents(sourcePath, targetPath, moduleId, bmadDir, this); - - // Count agents (rough estimate based on files) - const agentsPath = path.join(targetPath, 'agents'); - if (await fs.pathExists(agentsPath)) { - const agentFiles = await fs.readdir(agentsPath); - const agentCount = agentFiles.filter((f) => f.endsWith('.md')).length; - totalAgentCount += agentCount; - } - } - - spinner.stop('Agent recompilation complete!'); - - return { - success: true, - agentCount: totalAgentCount, - modules: installedModules, - }; - } catch (error) { - spinner.error('Agent recompilation failed'); - throw error; - } - } - - /** - * Private: Prompt for update action - */ - async promptUpdateAction() { - const action = await prompts.select({ - message: 'What would you like to do?', - choices: [{ name: 'Update existing installation', value: 'update' }], - }); - return { action }; - } - - /** - * Handle legacy BMAD v4 detection with simple warning - * @param {string} _projectDir - Project directory (unused in simplified version) - * @param {Object} _legacyV4 - Legacy V4 detection result (unused in simplified version) - */ - async handleLegacyV4Migration(_projectDir, _legacyV4) { - await prompts.note( - 'Found .bmad-method folder from BMAD v4 installation.\n\n' + - 'Before continuing with installation, we recommend:\n' + - ' 1. Remove the .bmad-method folder, OR\n' + - ' 2. Back it up by renaming it to another name (e.g., bmad-method-backup)\n\n' + - 'If your v4 installation set up rules or commands, you should remove those as well.', - 'Legacy BMAD v4 detected', - ); - - const proceed = await prompts.select({ - message: 'What would you like to do?', - choices: [ - { - name: 'Exit and clean up manually (recommended)', - value: 'exit', - hint: 'Exit installation', - }, - { - name: 'Continue with installation anyway', - value: 'continue', - hint: 'Continue', - }, - ], - default: 'exit', - }); - - if (proceed === 'exit') { - await prompts.log.info('Please remove the .bmad-method folder and any v4 rules/commands, then run the installer again.'); - // Allow event loop to flush pending I/O before exit - setImmediate(() => process.exit(0)); - return; - } - - await prompts.log.warn('Proceeding with installation despite legacy v4 folder'); - } - - /** - * Read files-manifest.csv - * @param {string} bmadDir - BMAD installation directory - * @returns {Array} Array of file entries from files-manifest.csv - */ - async readFilesManifest(bmadDir) { - const filesManifestPath = path.join(bmadDir, '_config', 'files-manifest.csv'); - if (!(await fs.pathExists(filesManifestPath))) { - return []; - } - - try { - const content = await fs.readFile(filesManifestPath, 'utf8'); - const lines = content.split('\n'); - const files = []; - - for (let i = 1; i < lines.length; i++) { - // Skip header - const line = lines[i].trim(); - if (!line) continue; - - // Parse CSV line properly handling quoted values - const parts = []; - let current = ''; - let inQuotes = false; - - for (const char of line) { - if (char === '"') { - inQuotes = !inQuotes; - } else if (char === ',' && !inQuotes) { - parts.push(current); - current = ''; - } else { - current += char; - } - } - parts.push(current); // Add last part - - if (parts.length >= 4) { - files.push({ - type: parts[0], - name: parts[1], - module: parts[2], - path: parts[3], - hash: parts[4] || null, // Hash may not exist in old manifests - }); - } - } - - return files; - } catch (error) { - await prompts.log.warn('Could not read files-manifest.csv: ' + error.message); - return []; - } - } - - /** - * Detect custom and modified files - * @param {string} bmadDir - BMAD installation directory - * @param {Array} existingFilesManifest - Previous files from files-manifest.csv - * @returns {Object} Object with customFiles and modifiedFiles arrays - */ - async detectCustomFiles(bmadDir, existingFilesManifest) { - const customFiles = []; - const modifiedFiles = []; - - // Memory is always in _bmad/_memory - const bmadMemoryPath = '_memory'; - - // Check if the manifest has hashes - if not, we can't detect modifications - let manifestHasHashes = false; - if (existingFilesManifest && existingFilesManifest.length > 0) { - manifestHasHashes = existingFilesManifest.some((f) => f.hash); - } - - // Build map of previously installed files from files-manifest.csv with their hashes - const installedFilesMap = new Map(); - for (const fileEntry of existingFilesManifest) { - if (fileEntry.path) { - const absolutePath = path.join(bmadDir, fileEntry.path); - installedFilesMap.set(path.normalize(absolutePath), { - hash: fileEntry.hash, - relativePath: fileEntry.path, - }); - } - } - - // Recursively scan bmadDir for all files - const scanDirectory = async (dir) => { - try { - const entries = await fs.readdir(dir, { withFileTypes: true }); - for (const entry of entries) { - const fullPath = path.join(dir, entry.name); - - if (entry.isDirectory()) { - // Skip certain directories - if (entry.name === 'node_modules' || entry.name === '.git') { - continue; - } - await scanDirectory(fullPath); - } else if (entry.isFile()) { - const normalizedPath = path.normalize(fullPath); - const fileInfo = installedFilesMap.get(normalizedPath); - - // Skip certain system files that are auto-generated - const relativePath = path.relative(bmadDir, fullPath); - const fileName = path.basename(fullPath); - - // Skip _config directory EXCEPT for modified agent customizations - if (relativePath.startsWith('_config/') || relativePath.startsWith('_config\\')) { - // Special handling for .customize.yaml files - only preserve if modified - if (relativePath.includes('/agents/') && fileName.endsWith('.customize.yaml')) { - // Check if the customization file has been modified from manifest - const manifestPath = path.join(bmadDir, '_config', 'manifest.yaml'); - if (await fs.pathExists(manifestPath)) { - const crypto = require('node:crypto'); - const currentContent = await fs.readFile(fullPath, 'utf8'); - const currentHash = crypto.createHash('sha256').update(currentContent).digest('hex'); - - const yaml = require('yaml'); - const manifestContent = await fs.readFile(manifestPath, 'utf8'); - const manifestData = yaml.parse(manifestContent); - const originalHash = manifestData.agentCustomizations?.[relativePath]; - - // Only add to customFiles if hash differs (user modified) - if (originalHash && currentHash !== originalHash) { - customFiles.push(fullPath); - } - } - } - continue; - } - - if (relativePath.startsWith(bmadMemoryPath + '/') && path.dirname(relativePath).includes('-sidecar')) { - continue; - } - - // Skip config.yaml files - these are regenerated on each install/update - if (fileName === 'config.yaml') { - continue; - } - - if (!fileInfo) { - // File not in manifest = custom file - // EXCEPT: Agent .md files in module folders are generated files, not custom - // Only treat .md files under _config/agents/ as custom - if (!(fileName.endsWith('.md') && relativePath.includes('/agents/') && !relativePath.startsWith('_config/'))) { - customFiles.push(fullPath); - } - } else if (manifestHasHashes && fileInfo.hash) { - // File in manifest with hash - check if it was modified - const currentHash = await this.manifest.calculateFileHash(fullPath); - if (currentHash && currentHash !== fileInfo.hash) { - // Hash changed = file was modified - modifiedFiles.push({ - path: fullPath, - relativePath: fileInfo.relativePath, - }); - } - } - } - } - } catch { - // Ignore errors scanning directories - } - }; - - await scanDirectory(bmadDir); - return { customFiles, modifiedFiles }; - } - - /** - * Handle missing custom module sources interactively - * @param {Map} customModuleSources - Map of custom module ID to info - * @param {string} bmadDir - BMAD directory - * @param {string} projectRoot - Project root directory - * @param {string} operation - Current operation ('update', 'compile', etc.) - * @param {Array} installedModules - Array of installed module IDs (will be modified) - * @param {boolean} [skipPrompts=false] - Skip interactive prompts and keep all modules with missing sources - * @returns {Object} Object with validCustomModules array and keptModulesWithoutSources array - */ - async handleMissingCustomSources(customModuleSources, bmadDir, projectRoot, operation, installedModules, skipPrompts = false) { - const validCustomModules = []; - const keptModulesWithoutSources = []; // Track modules kept without sources - const customModulesWithMissingSources = []; - - // Check which sources exist - for (const [moduleId, customInfo] of customModuleSources) { - if (await fs.pathExists(customInfo.sourcePath)) { - validCustomModules.push({ - id: moduleId, - name: customInfo.name, - path: customInfo.sourcePath, - info: customInfo, - }); - } else { - // For cached modules that are missing, we just skip them without prompting - if (customInfo.cached) { - // Skip cached modules without prompting - keptModulesWithoutSources.push({ - id: moduleId, - name: customInfo.name, - cached: true, - }); - } else { - customModulesWithMissingSources.push({ - id: moduleId, - name: customInfo.name, - sourcePath: customInfo.sourcePath, - relativePath: customInfo.relativePath, - info: customInfo, - }); - } - } - } - - // If no missing sources, return immediately - if (customModulesWithMissingSources.length === 0) { - return { - validCustomModules, - keptModulesWithoutSources: [], - }; - } - - // Non-interactive mode: keep all modules with missing sources - if (skipPrompts) { - for (const missing of customModulesWithMissingSources) { - keptModulesWithoutSources.push(missing.id); - } - return { validCustomModules, keptModulesWithoutSources }; - } - - await prompts.log.warn(`Found ${customModulesWithMissingSources.length} custom module(s) with missing sources:`); - - let keptCount = 0; - let updatedCount = 0; - let removedCount = 0; - - for (const missing of customModulesWithMissingSources) { - await prompts.log.message( - `${missing.name} (${missing.id})\n Original source: ${missing.relativePath}\n Full path: ${missing.sourcePath}`, - ); - - const choices = [ - { - name: 'Keep installed (will not be processed)', - value: 'keep', - hint: 'Keep', - }, - { - name: 'Specify new source location', - value: 'update', - hint: 'Update', - }, - ]; - - // Only add remove option if not just compiling agents - if (operation !== 'compile-agents') { - choices.push({ - name: '⚠️ REMOVE module completely (destructive!)', - value: 'remove', - hint: 'Remove', - }); - } - - const action = await prompts.select({ - message: `How would you like to handle "${missing.name}"?`, - choices, - }); - - switch (action) { - case 'update': { - // Use sync validation because @clack/prompts doesn't support async validate - const newSourcePath = await prompts.text({ - message: 'Enter the new path to the custom module:', - default: missing.sourcePath, - validate: (input) => { - if (!input || input.trim() === '') { - return 'Please enter a path'; - } - const expandedPath = path.resolve(input.trim()); - if (!fs.pathExistsSync(expandedPath)) { - return 'Path does not exist'; - } - // Check if it looks like a valid module - const moduleYamlPath = path.join(expandedPath, 'module.yaml'); - const agentsPath = path.join(expandedPath, 'agents'); - const workflowsPath = path.join(expandedPath, 'workflows'); - - if (!fs.pathExistsSync(moduleYamlPath) && !fs.pathExistsSync(agentsPath) && !fs.pathExistsSync(workflowsPath)) { - return 'Path does not appear to contain a valid custom module'; - } - return; // clack expects undefined for valid input - }, - }); - - // Defensive: handleCancel should have exited, but guard against symbol propagation - if (typeof newSourcePath !== 'string') { - keptCount++; - keptModulesWithoutSources.push(missing.id); - continue; - } - - // Update the source in manifest - const resolvedPath = path.resolve(newSourcePath.trim()); - missing.info.sourcePath = resolvedPath; - // Remove relativePath - we only store absolute sourcePath now - delete missing.info.relativePath; - await this.manifest.addCustomModule(bmadDir, missing.info); - - validCustomModules.push({ - id: missing.id, - name: missing.name, - path: resolvedPath, - info: missing.info, - }); - - updatedCount++; - await prompts.log.success('Updated source location'); - - break; - } - case 'remove': { - // Extra confirmation for destructive remove - await prompts.log.error( - `WARNING: This will PERMANENTLY DELETE "${missing.name}" and all its files!\n Module location: ${path.join(bmadDir, missing.id)}`, - ); - - const confirmDelete = await prompts.confirm({ - message: 'Are you absolutely sure you want to delete this module?', - default: false, - }); - - if (confirmDelete) { - const typedConfirm = await prompts.text({ - message: 'Type "DELETE" to confirm permanent deletion:', - validate: (input) => { - if (input !== 'DELETE') { - return 'You must type "DELETE" exactly to proceed'; - } - return; // clack expects undefined for valid input - }, - }); - - if (typedConfirm === 'DELETE') { - // Remove the module from filesystem and manifest - const modulePath = path.join(bmadDir, missing.id); - if (await fs.pathExists(modulePath)) { - const fsExtra = require('fs-extra'); - await fsExtra.remove(modulePath); - await prompts.log.warn(`Deleted module directory: ${path.relative(projectRoot, modulePath)}`); - } - - await this.manifest.removeModule(bmadDir, missing.id); - await this.manifest.removeCustomModule(bmadDir, missing.id); - await prompts.log.warn('Removed from manifest'); - - // Also remove from installedModules list - if (installedModules && installedModules.includes(missing.id)) { - const index = installedModules.indexOf(missing.id); - if (index !== -1) { - installedModules.splice(index, 1); - } - } - - removedCount++; - await prompts.log.error(`"${missing.name}" has been permanently removed`); - } else { - await prompts.log.message('Removal cancelled - module will be kept'); - keptCount++; - } - } else { - await prompts.log.message('Removal cancelled - module will be kept'); - keptCount++; - } - - break; - } - case 'keep': { - keptCount++; - keptModulesWithoutSources.push(missing.id); - await prompts.log.message('Module will be kept as-is'); - - break; - } - // No default - } - } - - // Show summary - if (keptCount > 0 || updatedCount > 0 || removedCount > 0) { - let summary = 'Summary for custom modules with missing sources:'; - if (keptCount > 0) summary += `\n • ${keptCount} module(s) kept as-is`; - if (updatedCount > 0) summary += `\n • ${updatedCount} module(s) updated with new sources`; - if (removedCount > 0) summary += `\n • ${removedCount} module(s) permanently deleted`; - await prompts.log.message(summary); - } - - return { - validCustomModules, - keptModulesWithoutSources, - }; - } -} - -module.exports = { Installer }; diff --git a/tools/cli/installers/lib/core/manifest-generator.js b/tools/cli/installers/lib/core/manifest-generator.js deleted file mode 100644 index 06e2e3f4b..000000000 --- a/tools/cli/installers/lib/core/manifest-generator.js +++ /dev/null @@ -1,1081 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const yaml = require('yaml'); -const crypto = require('node:crypto'); -const csv = require('csv-parse/sync'); -const { getSourcePath, getModulePath } = require('../../../lib/project-root'); -const prompts = require('../../../lib/prompts'); - -// Load package.json for version info -const packageJson = require('../../../../../package.json'); - -/** - * Generates manifest files for installed workflows, agents, and tasks - */ -class ManifestGenerator { - constructor() { - this.workflows = []; - this.agents = []; - this.tasks = []; - this.tools = []; - this.modules = []; - this.files = []; - this.selectedIdes = []; - } - - /** - * Clean text for CSV output by normalizing whitespace. - * Note: Quote escaping is handled by escapeCsv() at write time. - * @param {string} text - Text to clean - * @returns {string} Cleaned text - */ - cleanForCSV(text) { - if (!text) return ''; - return text.trim().replaceAll(/\s+/g, ' '); // Normalize all whitespace (including newlines) to single space - } - - /** - * Generate all manifests for the installation - * @param {string} bmadDir - _bmad - * @param {Array} selectedModules - Selected modules for installation - * @param {Array} installedFiles - All installed files (optional, for hash tracking) - */ - async generateManifests(bmadDir, selectedModules, installedFiles = [], options = {}) { - // Create _config directory if it doesn't exist - const cfgDir = path.join(bmadDir, '_config'); - await fs.ensureDir(cfgDir); - - // Store modules list (all modules including preserved ones) - const preservedModules = options.preservedModules || []; - - // Scan the bmad directory to find all actually installed modules - const installedModules = await this.scanInstalledModules(bmadDir); - - // Since custom modules are now installed the same way as regular modules, - // we don't need to exclude them from manifest generation - const allModules = [...new Set(['core', ...selectedModules, ...preservedModules, ...installedModules])]; - - this.modules = allModules; - this.updatedModules = allModules; // Include ALL modules (including custom) for scanning - - // For CSV manifests, we need to include ALL modules that are installed - // preservedModules controls which modules stay as-is in the CSV (don't get rescanned) - // But all modules should be included in the final manifest - this.preservedModules = allModules; // Include ALL modules (including custom) - this.bmadDir = bmadDir; - this.bmadFolderName = path.basename(bmadDir); // Get the actual folder name (e.g., '_bmad' or 'bmad') - this.allInstalledFiles = installedFiles; - - if (!Object.prototype.hasOwnProperty.call(options, 'ides')) { - throw new Error('ManifestGenerator requires `options.ides` to be provided – installer should supply the selected IDEs array.'); - } - - const resolvedIdes = options.ides ?? []; - if (!Array.isArray(resolvedIdes)) { - throw new TypeError('ManifestGenerator expected `options.ides` to be an array.'); - } - - // Filter out any undefined/null values from IDE list - this.selectedIdes = resolvedIdes.filter((ide) => ide && typeof ide === 'string'); - - // Collect workflow data - await this.collectWorkflows(selectedModules); - - // Collect agent data - use updatedModules which includes all installed modules - await this.collectAgents(this.updatedModules); - - // Collect task data - await this.collectTasks(this.updatedModules); - - // Collect tool data - await this.collectTools(this.updatedModules); - - // Write manifest files and collect their paths - const manifestFiles = [ - await this.writeMainManifest(cfgDir), - await this.writeWorkflowManifest(cfgDir), - await this.writeAgentManifest(cfgDir), - await this.writeTaskManifest(cfgDir), - await this.writeToolManifest(cfgDir), - await this.writeFilesManifest(cfgDir), - ]; - - return { - workflows: this.workflows.length, - agents: this.agents.length, - tasks: this.tasks.length, - tools: this.tools.length, - files: this.files.length, - manifestFiles: manifestFiles, - }; - } - - /** - * Collect all workflows from core and selected modules - * Scans the INSTALLED bmad directory, not the source - */ - async collectWorkflows(selectedModules) { - this.workflows = []; - - // Use updatedModules which already includes deduplicated 'core' + selectedModules - for (const moduleName of this.updatedModules) { - const modulePath = path.join(this.bmadDir, moduleName); - - if (await fs.pathExists(modulePath)) { - const moduleWorkflows = await this.getWorkflowsFromPath(modulePath, moduleName); - this.workflows.push(...moduleWorkflows); - } - } - } - - /** - * Recursively find and parse workflow.yaml and workflow.md files - */ - async getWorkflowsFromPath(basePath, moduleName) { - const workflows = []; - const workflowsPath = path.join(basePath, 'workflows'); - const debug = process.env.BMAD_DEBUG_MANIFEST === 'true'; - - if (debug) { - console.log(`[DEBUG] Scanning workflows in: ${workflowsPath}`); - } - - if (!(await fs.pathExists(workflowsPath))) { - if (debug) { - console.log(`[DEBUG] Workflows path does not exist: ${workflowsPath}`); - } - return workflows; - } - - // Recursively find workflow.yaml files - const findWorkflows = async (dir, relativePath = '') => { - const entries = await fs.readdir(dir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(dir, entry.name); - - if (entry.isDirectory()) { - // Recurse into subdirectories - const newRelativePath = relativePath ? `${relativePath}/${entry.name}` : entry.name; - await findWorkflows(fullPath, newRelativePath); - } else if ( - entry.name === 'workflow.yaml' || - entry.name === 'workflow.md' || - (entry.name.startsWith('workflow-') && entry.name.endsWith('.md')) - ) { - // Parse workflow file (both YAML and MD formats) - if (debug) { - console.log(`[DEBUG] Found workflow file: ${fullPath}`); - } - try { - // Read and normalize line endings (fix Windows CRLF issues) - const rawContent = await fs.readFile(fullPath, 'utf8'); - const content = rawContent.replaceAll('\r\n', '\n').replaceAll('\r', '\n'); - - let workflow; - if (entry.name === 'workflow.yaml') { - // Parse YAML workflow - workflow = yaml.parse(content); - } else { - // Parse MD workflow with YAML frontmatter - const frontmatterMatch = content.match(/^---\r?\n([\s\S]*?)\r?\n---/); - if (!frontmatterMatch) { - if (debug) { - console.log(`[DEBUG] Skipped (no frontmatter): ${fullPath}`); - } - continue; // Skip MD files without frontmatter - } - workflow = yaml.parse(frontmatterMatch[1]); - } - - if (debug) { - console.log(`[DEBUG] Parsed: name="${workflow.name}", description=${workflow.description ? 'OK' : 'MISSING'}`); - } - - // Skip template workflows (those with placeholder values) - if (workflow.name && workflow.name.includes('{') && workflow.name.includes('}')) { - if (debug) { - console.log(`[DEBUG] Skipped (template placeholder): ${workflow.name}`); - } - continue; - } - - // Skip workflows marked as non-standalone (reference/example workflows) - if (workflow.standalone === false) { - if (debug) { - console.log(`[DEBUG] Skipped (standalone=false): ${workflow.name}`); - } - continue; - } - - if (workflow.name && workflow.description) { - // Build relative path for installation - const installPath = - moduleName === 'core' - ? `${this.bmadFolderName}/core/workflows/${relativePath}/${entry.name}` - : `${this.bmadFolderName}/${moduleName}/workflows/${relativePath}/${entry.name}`; - - // Workflows with standalone: false are filtered out above - workflows.push({ - name: workflow.name, - description: this.cleanForCSV(workflow.description), - module: moduleName, - path: installPath, - }); - - // Add to files list - this.files.push({ - type: 'workflow', - name: workflow.name, - module: moduleName, - path: installPath, - }); - - if (debug) { - console.log(`[DEBUG] ✓ Added workflow: ${workflow.name} (${moduleName})`); - } - } else { - if (debug) { - console.log(`[DEBUG] Skipped (missing name or description): ${fullPath}`); - } - } - } catch (error) { - await prompts.log.warn(`Failed to parse workflow at ${fullPath}: ${error.message}`); - } - } - } - }; - - await findWorkflows(workflowsPath); - - if (debug) { - console.log(`[DEBUG] Total workflows found in ${moduleName}: ${workflows.length}`); - } - - return workflows; - } - - /** - * Collect all agents from core and selected modules - * Scans the INSTALLED bmad directory, not the source - */ - async collectAgents(selectedModules) { - this.agents = []; - - // Use updatedModules which already includes deduplicated 'core' + selectedModules - for (const moduleName of this.updatedModules) { - const agentsPath = path.join(this.bmadDir, moduleName, 'agents'); - - if (await fs.pathExists(agentsPath)) { - const moduleAgents = await this.getAgentsFromDir(agentsPath, moduleName); - this.agents.push(...moduleAgents); - } - } - - // Get standalone agents from bmad/agents/ directory - const standaloneAgentsDir = path.join(this.bmadDir, 'agents'); - if (await fs.pathExists(standaloneAgentsDir)) { - const agentDirs = await fs.readdir(standaloneAgentsDir, { withFileTypes: true }); - - for (const agentDir of agentDirs) { - if (!agentDir.isDirectory()) continue; - - const agentDirPath = path.join(standaloneAgentsDir, agentDir.name); - const standaloneAgents = await this.getAgentsFromDir(agentDirPath, 'standalone'); - this.agents.push(...standaloneAgents); - } - } - } - - /** - * Get agents from a directory recursively - * Only includes compiled .md files (not .agent.yaml source files) - */ - async getAgentsFromDir(dirPath, moduleName, relativePath = '') { - const agents = []; - const entries = await fs.readdir(dirPath, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(dirPath, entry.name); - - if (entry.isDirectory()) { - // Recurse into subdirectories - const newRelativePath = relativePath ? `${relativePath}/${entry.name}` : entry.name; - const subDirAgents = await this.getAgentsFromDir(fullPath, moduleName, newRelativePath); - agents.push(...subDirAgents); - } else if (entry.name.endsWith('.md') && !entry.name.endsWith('.agent.yaml') && entry.name.toLowerCase() !== 'readme.md') { - const content = await fs.readFile(fullPath, 'utf8'); - - // Skip files that don't contain tag (e.g., README files) - if (!content.includes('([^<]+)<\/role>/); - const identityMatch = content.match(/([\s\S]*?)<\/identity>/); - const styleMatch = content.match(/([\s\S]*?)<\/communication_style>/); - const principlesMatch = content.match(/([\s\S]*?)<\/principles>/); - - // Build relative path for installation - const fileRelativePath = relativePath ? `${relativePath}/${entry.name}` : entry.name; - const installPath = - moduleName === 'core' - ? `${this.bmadFolderName}/core/agents/${fileRelativePath}` - : `${this.bmadFolderName}/${moduleName}/agents/${fileRelativePath}`; - - const agentName = entry.name.replace('.md', ''); - - agents.push({ - name: agentName, - displayName: nameMatch ? nameMatch[1] : agentName, - title: titleMatch ? titleMatch[1] : '', - icon: iconMatch ? iconMatch[1] : '', - capabilities: capabilitiesMatch ? this.cleanForCSV(capabilitiesMatch[1]) : '', - role: roleMatch ? this.cleanForCSV(roleMatch[1]) : '', - identity: identityMatch ? this.cleanForCSV(identityMatch[1]) : '', - communicationStyle: styleMatch ? this.cleanForCSV(styleMatch[1]) : '', - principles: principlesMatch ? this.cleanForCSV(principlesMatch[1]) : '', - module: moduleName, - path: installPath, - }); - - // Add to files list - this.files.push({ - type: 'agent', - name: agentName, - module: moduleName, - path: installPath, - }); - } - } - - return agents; - } - - /** - * Collect all tasks from core and selected modules - * Scans the INSTALLED bmad directory, not the source - */ - async collectTasks(selectedModules) { - this.tasks = []; - - // Use updatedModules which already includes deduplicated 'core' + selectedModules - for (const moduleName of this.updatedModules) { - const tasksPath = path.join(this.bmadDir, moduleName, 'tasks'); - - if (await fs.pathExists(tasksPath)) { - const moduleTasks = await this.getTasksFromDir(tasksPath, moduleName); - this.tasks.push(...moduleTasks); - } - } - } - - /** - * Get tasks from a directory - */ - async getTasksFromDir(dirPath, moduleName) { - const tasks = []; - const files = await fs.readdir(dirPath); - - for (const file of files) { - // Check for both .xml and .md files - if (file.endsWith('.xml') || file.endsWith('.md')) { - const filePath = path.join(dirPath, file); - const content = await fs.readFile(filePath, 'utf8'); - - // Skip internal/engine files (not user-facing tasks) - if (content.includes('internal="true"')) { - continue; - } - - let name = file.replace(/\.(xml|md)$/, ''); - let displayName = name; - let description = ''; - let standalone = false; - - if (file.endsWith('.md')) { - // Parse YAML frontmatter for .md tasks - const frontmatterMatch = content.match(/^---\r?\n([\s\S]*?)\r?\n---/); - if (frontmatterMatch) { - try { - const frontmatter = yaml.parse(frontmatterMatch[1]); - name = frontmatter.name || name; - displayName = frontmatter.displayName || frontmatter.name || name; - description = this.cleanForCSV(frontmatter.description || ''); - // Tasks are standalone by default unless explicitly false (internal=true is already filtered above) - standalone = frontmatter.standalone !== false && frontmatter.standalone !== 'false'; - } catch { - // If YAML parsing fails, use defaults - standalone = true; // Default to standalone - } - } else { - standalone = true; // No frontmatter means standalone - } - } else { - // For .xml tasks, extract from tag attributes - const nameMatch = content.match(/name="([^"]+)"/); - displayName = nameMatch ? nameMatch[1] : name; - - const descMatch = content.match(/description="([^"]+)"/); - const objMatch = content.match(/([^<]+)<\/objective>/); - description = this.cleanForCSV(descMatch ? descMatch[1] : objMatch ? objMatch[1].trim() : ''); - - const standaloneFalseMatch = content.match(/]+standalone="false"/); - standalone = !standaloneFalseMatch; - } - - // Build relative path for installation - const installPath = - moduleName === 'core' ? `${this.bmadFolderName}/core/tasks/${file}` : `${this.bmadFolderName}/${moduleName}/tasks/${file}`; - - tasks.push({ - name: name, - displayName: displayName, - description: description, - module: moduleName, - path: installPath, - standalone: standalone, - }); - - // Add to files list - this.files.push({ - type: 'task', - name: name, - module: moduleName, - path: installPath, - }); - } - } - - return tasks; - } - - /** - * Collect all tools from core and selected modules - * Scans the INSTALLED bmad directory, not the source - */ - async collectTools(selectedModules) { - this.tools = []; - - // Use updatedModules which already includes deduplicated 'core' + selectedModules - for (const moduleName of this.updatedModules) { - const toolsPath = path.join(this.bmadDir, moduleName, 'tools'); - - if (await fs.pathExists(toolsPath)) { - const moduleTools = await this.getToolsFromDir(toolsPath, moduleName); - this.tools.push(...moduleTools); - } - } - } - - /** - * Get tools from a directory - */ - async getToolsFromDir(dirPath, moduleName) { - const tools = []; - const files = await fs.readdir(dirPath); - - for (const file of files) { - // Check for both .xml and .md files - if (file.endsWith('.xml') || file.endsWith('.md')) { - const filePath = path.join(dirPath, file); - const content = await fs.readFile(filePath, 'utf8'); - - // Skip internal tools (same as tasks) - if (content.includes('internal="true"')) { - continue; - } - - let name = file.replace(/\.(xml|md)$/, ''); - let displayName = name; - let description = ''; - let standalone = false; - - if (file.endsWith('.md')) { - // Parse YAML frontmatter for .md tools - const frontmatterMatch = content.match(/^---\r?\n([\s\S]*?)\r?\n---/); - if (frontmatterMatch) { - try { - const frontmatter = yaml.parse(frontmatterMatch[1]); - name = frontmatter.name || name; - displayName = frontmatter.displayName || frontmatter.name || name; - description = this.cleanForCSV(frontmatter.description || ''); - // Tools are standalone by default unless explicitly false (internal=true is already filtered above) - standalone = frontmatter.standalone !== false && frontmatter.standalone !== 'false'; - } catch { - // If YAML parsing fails, use defaults - standalone = true; // Default to standalone - } - } else { - standalone = true; // No frontmatter means standalone - } - } else { - // For .xml tools, extract from tag attributes - const nameMatch = content.match(/name="([^"]+)"/); - displayName = nameMatch ? nameMatch[1] : name; - - const descMatch = content.match(/description="([^"]+)"/); - const objMatch = content.match(/([^<]+)<\/objective>/); - description = this.cleanForCSV(descMatch ? descMatch[1] : objMatch ? objMatch[1].trim() : ''); - - const standaloneFalseMatch = content.match(/]+standalone="false"/); - standalone = !standaloneFalseMatch; - } - - // Build relative path for installation - const installPath = - moduleName === 'core' ? `${this.bmadFolderName}/core/tools/${file}` : `${this.bmadFolderName}/${moduleName}/tools/${file}`; - - tools.push({ - name: name, - displayName: displayName, - description: description, - module: moduleName, - path: installPath, - standalone: standalone, - }); - - // Add to files list - this.files.push({ - type: 'tool', - name: name, - module: moduleName, - path: installPath, - }); - } - } - - return tools; - } - - /** - * Write main manifest as YAML with installation info only - * Fetches fresh version info for all modules - * @returns {string} Path to the manifest file - */ - async writeMainManifest(cfgDir) { - const manifestPath = path.join(cfgDir, 'manifest.yaml'); - - // Read existing manifest to preserve install date - let existingInstallDate = null; - const existingModulesMap = new Map(); - - if (await fs.pathExists(manifestPath)) { - try { - const existingContent = await fs.readFile(manifestPath, 'utf8'); - const existingManifest = yaml.parse(existingContent); - - // Preserve original install date - if (existingManifest.installation?.installDate) { - existingInstallDate = existingManifest.installation.installDate; - } - - // Build map of existing modules for quick lookup - if (existingManifest.modules && Array.isArray(existingManifest.modules)) { - for (const m of existingManifest.modules) { - if (typeof m === 'object' && m.name) { - existingModulesMap.set(m.name, m); - } else if (typeof m === 'string') { - existingModulesMap.set(m, { installDate: existingInstallDate }); - } - } - } - } catch { - // If we can't read existing manifest, continue with defaults - } - } - - // Fetch fresh version info for all modules - const { Manifest } = require('./manifest'); - const manifestObj = new Manifest(); - const updatedModules = []; - - for (const moduleName of this.modules) { - // Get fresh version info from source - const versionInfo = await manifestObj.getModuleVersionInfo(moduleName, this.bmadDir); - - // Get existing install date if available - const existing = existingModulesMap.get(moduleName); - - updatedModules.push({ - name: moduleName, - version: versionInfo.version, - installDate: existing?.installDate || new Date().toISOString(), - lastUpdated: new Date().toISOString(), - source: versionInfo.source, - npmPackage: versionInfo.npmPackage, - repoUrl: versionInfo.repoUrl, - }); - } - - const manifest = { - installation: { - version: packageJson.version, - installDate: existingInstallDate || new Date().toISOString(), - lastUpdated: new Date().toISOString(), - }, - modules: updatedModules, - ides: this.selectedIdes, - }; - - // Clean the manifest to remove any non-serializable values - const cleanManifest = structuredClone(manifest); - - const yamlStr = yaml.stringify(cleanManifest, { - indent: 2, - lineWidth: 0, - sortKeys: false, - }); - - // Ensure POSIX-compliant final newline - const content = yamlStr.endsWith('\n') ? yamlStr : yamlStr + '\n'; - await fs.writeFile(manifestPath, content); - return manifestPath; - } - - /** - * Read existing CSV and preserve rows for modules NOT being updated - * @param {string} csvPath - Path to existing CSV file - * @param {number} moduleColumnIndex - Which column contains the module name (0-indexed) - * @param {Array} expectedColumns - Expected column names in order - * @param {Object} defaultValues - Default values for missing columns - * @returns {Array} Preserved CSV rows (without header), upgraded to match expected columns - */ - async getPreservedCsvRows(csvPath, moduleColumnIndex, expectedColumns, defaultValues = {}) { - if (!(await fs.pathExists(csvPath)) || this.preservedModules.length === 0) { - return []; - } - - try { - const content = await fs.readFile(csvPath, 'utf8'); - const lines = content.trim().split('\n'); - - if (lines.length < 2) { - return []; // No data rows - } - - // Parse header to understand old schema - const header = lines[0]; - const headerColumns = header.match(/(".*?"|[^",\s]+)(?=\s*,|\s*$)/g) || []; - const oldColumns = headerColumns.map((c) => c.replaceAll(/^"|"$/g, '')); - - // Skip header row for data - const dataRows = lines.slice(1); - const preservedRows = []; - - for (const row of dataRows) { - // Simple CSV parsing (handles quoted values) - const columns = row.match(/(".*?"|[^",\s]+)(?=\s*,|\s*$)/g) || []; - const cleanColumns = columns.map((c) => c.replaceAll(/^"|"$/g, '')); - - const moduleValue = cleanColumns[moduleColumnIndex]; - - // Keep this row if it belongs to a preserved module - if (this.preservedModules.includes(moduleValue)) { - // Upgrade row to match expected schema - const upgradedRow = this.upgradeRowToSchema(cleanColumns, oldColumns, expectedColumns, defaultValues); - preservedRows.push(upgradedRow); - } - } - - return preservedRows; - } catch (error) { - await prompts.log.warn(`Failed to read existing CSV ${csvPath}: ${error.message}`); - return []; - } - } - - /** - * Upgrade a CSV row from old schema to new schema - * @param {Array} rowValues - Values from old row - * @param {Array} oldColumns - Old column names - * @param {Array} newColumns - New column names - * @param {Object} defaultValues - Default values for missing columns - * @returns {string} Upgraded CSV row - */ - upgradeRowToSchema(rowValues, oldColumns, newColumns, defaultValues) { - const upgradedValues = []; - - for (const newCol of newColumns) { - const oldIndex = oldColumns.indexOf(newCol); - - if (oldIndex !== -1 && oldIndex < rowValues.length) { - // Column exists in old schema, use its value - upgradedValues.push(rowValues[oldIndex]); - } else if (defaultValues[newCol] === undefined) { - // Column missing, no default provided - upgradedValues.push(''); - } else { - // Column missing, use default value - upgradedValues.push(defaultValues[newCol]); - } - } - - // Properly quote values and join - return upgradedValues.map((v) => `"${v}"`).join(','); - } - - /** - * Write workflow manifest CSV - * @returns {string} Path to the manifest file - */ - async writeWorkflowManifest(cfgDir) { - const csvPath = path.join(cfgDir, 'workflow-manifest.csv'); - const escapeCsv = (value) => `"${String(value ?? '').replaceAll('"', '""')}"`; - - // Create CSV header - standalone column removed, everything is canonicalized to 4 columns - let csv = 'name,description,module,path\n'; - - // Build workflows map from discovered workflows only - // Old entries are NOT preserved - the manifest reflects what actually exists on disk - const allWorkflows = new Map(); - - // Only add workflows that were actually discovered in this scan - for (const workflow of this.workflows) { - const key = `${workflow.module}:${workflow.name}`; - allWorkflows.set(key, { - name: workflow.name, - description: workflow.description, - module: workflow.module, - path: workflow.path, - }); - } - - // Write all workflows - for (const [, value] of allWorkflows) { - const row = [escapeCsv(value.name), escapeCsv(value.description), escapeCsv(value.module), escapeCsv(value.path)].join(','); - csv += row + '\n'; - } - - await fs.writeFile(csvPath, csv); - return csvPath; - } - - /** - * Write agent manifest CSV - * @returns {string} Path to the manifest file - */ - async writeAgentManifest(cfgDir) { - const csvPath = path.join(cfgDir, 'agent-manifest.csv'); - const escapeCsv = (value) => `"${String(value ?? '').replaceAll('"', '""')}"`; - - // Read existing manifest to preserve entries - const existingEntries = new Map(); - if (await fs.pathExists(csvPath)) { - const content = await fs.readFile(csvPath, 'utf8'); - const records = csv.parse(content, { - columns: true, - skip_empty_lines: true, - }); - for (const record of records) { - existingEntries.set(`${record.module}:${record.name}`, record); - } - } - - // Create CSV header with persona fields - let csvContent = 'name,displayName,title,icon,capabilities,role,identity,communicationStyle,principles,module,path\n'; - - // Combine existing and new agents, preferring new data for duplicates - const allAgents = new Map(); - - // Add existing entries - for (const [key, value] of existingEntries) { - allAgents.set(key, value); - } - - // Add/update new agents - for (const agent of this.agents) { - const key = `${agent.module}:${agent.name}`; - allAgents.set(key, { - name: agent.name, - displayName: agent.displayName, - title: agent.title, - icon: agent.icon, - capabilities: agent.capabilities, - role: agent.role, - identity: agent.identity, - communicationStyle: agent.communicationStyle, - principles: agent.principles, - module: agent.module, - path: agent.path, - }); - } - - // Write all agents - for (const [, record] of allAgents) { - const row = [ - escapeCsv(record.name), - escapeCsv(record.displayName), - escapeCsv(record.title), - escapeCsv(record.icon), - escapeCsv(record.capabilities), - escapeCsv(record.role), - escapeCsv(record.identity), - escapeCsv(record.communicationStyle), - escapeCsv(record.principles), - escapeCsv(record.module), - escapeCsv(record.path), - ].join(','); - csvContent += row + '\n'; - } - - await fs.writeFile(csvPath, csvContent); - return csvPath; - } - - /** - * Write task manifest CSV - * @returns {string} Path to the manifest file - */ - async writeTaskManifest(cfgDir) { - const csvPath = path.join(cfgDir, 'task-manifest.csv'); - const escapeCsv = (value) => `"${String(value ?? '').replaceAll('"', '""')}"`; - - // Read existing manifest to preserve entries - const existingEntries = new Map(); - if (await fs.pathExists(csvPath)) { - const content = await fs.readFile(csvPath, 'utf8'); - const records = csv.parse(content, { - columns: true, - skip_empty_lines: true, - }); - for (const record of records) { - existingEntries.set(`${record.module}:${record.name}`, record); - } - } - - // Create CSV header with standalone column - let csvContent = 'name,displayName,description,module,path,standalone\n'; - - // Combine existing and new tasks - const allTasks = new Map(); - - // Add existing entries - for (const [key, value] of existingEntries) { - allTasks.set(key, value); - } - - // Add/update new tasks - for (const task of this.tasks) { - const key = `${task.module}:${task.name}`; - allTasks.set(key, { - name: task.name, - displayName: task.displayName, - description: task.description, - module: task.module, - path: task.path, - standalone: task.standalone, - }); - } - - // Write all tasks - for (const [, record] of allTasks) { - const row = [ - escapeCsv(record.name), - escapeCsv(record.displayName), - escapeCsv(record.description), - escapeCsv(record.module), - escapeCsv(record.path), - escapeCsv(record.standalone), - ].join(','); - csvContent += row + '\n'; - } - - await fs.writeFile(csvPath, csvContent); - return csvPath; - } - - /** - * Write tool manifest CSV - * @returns {string} Path to the manifest file - */ - async writeToolManifest(cfgDir) { - const csvPath = path.join(cfgDir, 'tool-manifest.csv'); - const escapeCsv = (value) => `"${String(value ?? '').replaceAll('"', '""')}"`; - - // Read existing manifest to preserve entries - const existingEntries = new Map(); - if (await fs.pathExists(csvPath)) { - const content = await fs.readFile(csvPath, 'utf8'); - const records = csv.parse(content, { - columns: true, - skip_empty_lines: true, - }); - for (const record of records) { - existingEntries.set(`${record.module}:${record.name}`, record); - } - } - - // Create CSV header with standalone column - let csvContent = 'name,displayName,description,module,path,standalone\n'; - - // Combine existing and new tools - const allTools = new Map(); - - // Add existing entries - for (const [key, value] of existingEntries) { - allTools.set(key, value); - } - - // Add/update new tools - for (const tool of this.tools) { - const key = `${tool.module}:${tool.name}`; - allTools.set(key, { - name: tool.name, - displayName: tool.displayName, - description: tool.description, - module: tool.module, - path: tool.path, - standalone: tool.standalone, - }); - } - - // Write all tools - for (const [, record] of allTools) { - const row = [ - escapeCsv(record.name), - escapeCsv(record.displayName), - escapeCsv(record.description), - escapeCsv(record.module), - escapeCsv(record.path), - escapeCsv(record.standalone), - ].join(','); - csvContent += row + '\n'; - } - - await fs.writeFile(csvPath, csvContent); - return csvPath; - } - - /** - * Write files manifest CSV - */ - /** - * Calculate SHA256 hash of a file - * @param {string} filePath - Path to file - * @returns {string} SHA256 hash - */ - async calculateFileHash(filePath) { - try { - const content = await fs.readFile(filePath); - return crypto.createHash('sha256').update(content).digest('hex'); - } catch { - return ''; - } - } - - /** - * @returns {string} Path to the manifest file - */ - async writeFilesManifest(cfgDir) { - const csvPath = path.join(cfgDir, 'files-manifest.csv'); - - // Create CSV header with hash column - let csv = 'type,name,module,path,hash\n'; - - // If we have ALL installed files, use those instead of just workflows/agents/tasks - const allFiles = []; - if (this.allInstalledFiles && this.allInstalledFiles.length > 0) { - // Process all installed files - for (const filePath of this.allInstalledFiles) { - // Store paths relative to bmadDir (no folder prefix) - const relativePath = filePath.replace(this.bmadDir, '').replaceAll('\\', '/').replace(/^\//, ''); - const ext = path.extname(filePath).toLowerCase(); - const fileName = path.basename(filePath, ext); - - // Determine module from path (first directory component) - const pathParts = relativePath.split('/'); - const module = pathParts.length > 0 ? pathParts[0] : 'unknown'; - - // Calculate hash - const hash = await this.calculateFileHash(filePath); - - allFiles.push({ - type: ext.slice(1) || 'file', - name: fileName, - module: module, - path: relativePath, - hash: hash, - }); - } - } else { - // Fallback: use the collected workflows/agents/tasks - for (const file of this.files) { - // Strip the folder prefix if present (for consistency) - const relPath = file.path.replace(this.bmadFolderName + '/', ''); - const filePath = path.join(this.bmadDir, relPath); - const hash = await this.calculateFileHash(filePath); - allFiles.push({ - ...file, - path: relPath, - hash: hash, - }); - } - } - - // Sort files by module, then type, then name - allFiles.sort((a, b) => { - if (a.module !== b.module) return a.module.localeCompare(b.module); - if (a.type !== b.type) return a.type.localeCompare(b.type); - return a.name.localeCompare(b.name); - }); - - // Add all files - for (const file of allFiles) { - csv += `"${file.type}","${file.name}","${file.module}","${file.path}","${file.hash}"\n`; - } - - await fs.writeFile(csvPath, csv); - return csvPath; - } - - /** - * Scan the bmad directory to find all installed modules - * @param {string} bmadDir - Path to bmad directory - * @returns {Array} List of module names - */ - async scanInstalledModules(bmadDir) { - const modules = []; - - try { - const entries = await fs.readdir(bmadDir, { withFileTypes: true }); - - for (const entry of entries) { - // Skip if not a directory or is a special directory - if (!entry.isDirectory() || entry.name.startsWith('.') || entry.name === '_config') { - continue; - } - - // Check if this looks like a module (has agents, workflows, or tasks directory) - const modulePath = path.join(bmadDir, entry.name); - const hasAgents = await fs.pathExists(path.join(modulePath, 'agents')); - const hasWorkflows = await fs.pathExists(path.join(modulePath, 'workflows')); - const hasTasks = await fs.pathExists(path.join(modulePath, 'tasks')); - const hasTools = await fs.pathExists(path.join(modulePath, 'tools')); - - // If it has any of these directories, it's likely a module - if (hasAgents || hasWorkflows || hasTasks || hasTools) { - modules.push(entry.name); - } - } - } catch (error) { - await prompts.log.warn(`Could not scan for installed modules: ${error.message}`); - } - - return modules; - } -} - -module.exports = { ManifestGenerator }; diff --git a/tools/cli/installers/lib/core/manifest.js b/tools/cli/installers/lib/core/manifest.js deleted file mode 100644 index 5fa1229e1..000000000 --- a/tools/cli/installers/lib/core/manifest.js +++ /dev/null @@ -1,1038 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const crypto = require('node:crypto'); -const { getProjectRoot } = require('../../../lib/project-root'); -const prompts = require('../../../lib/prompts'); - -class Manifest { - /** - * Create a new manifest - * @param {string} bmadDir - Path to bmad directory - * @param {Object} data - Manifest data - * @param {Array} installedFiles - List of installed files (no longer used, files tracked in files-manifest.csv) - */ - async create(bmadDir, data, installedFiles = []) { - const manifestPath = path.join(bmadDir, '_config', 'manifest.yaml'); - const yaml = require('yaml'); - - // Ensure _config directory exists - await fs.ensureDir(path.dirname(manifestPath)); - - // Get the BMad version from package.json - const bmadVersion = data.version || require(path.join(process.cwd(), 'package.json')).version; - - // Convert module list to new detailed format - const moduleDetails = []; - if (data.modules && Array.isArray(data.modules)) { - for (const moduleName of data.modules) { - // Core and BMM modules use the BMad version - const moduleVersion = moduleName === 'core' || moduleName === 'bmm' ? bmadVersion : null; - const now = data.installDate || new Date().toISOString(); - - moduleDetails.push({ - name: moduleName, - version: moduleVersion, - installDate: now, - lastUpdated: now, - source: moduleName === 'core' || moduleName === 'bmm' ? 'built-in' : 'unknown', - }); - } - } - - // Structure the manifest data - const manifestData = { - installation: { - version: bmadVersion, - installDate: data.installDate || new Date().toISOString(), - lastUpdated: data.lastUpdated || new Date().toISOString(), - }, - modules: moduleDetails, - ides: data.ides || [], - }; - - // Write YAML manifest - // Clean the manifest data to remove any non-serializable values - const cleanManifestData = structuredClone(manifestData); - - const yamlContent = yaml.stringify(cleanManifestData, { - indent: 2, - lineWidth: 0, - sortKeys: false, - }); - - // Ensure POSIX-compliant final newline - const content = yamlContent.endsWith('\n') ? yamlContent : yamlContent + '\n'; - await fs.writeFile(manifestPath, content, 'utf8'); - return { success: true, path: manifestPath, filesTracked: 0 }; - } - - /** - * Read existing manifest - * @param {string} bmadDir - Path to bmad directory - * @returns {Object|null} Manifest data or null if not found - */ - async read(bmadDir) { - const yamlPath = path.join(bmadDir, '_config', 'manifest.yaml'); - const yaml = require('yaml'); - - if (await fs.pathExists(yamlPath)) { - try { - const content = await fs.readFile(yamlPath, 'utf8'); - const manifestData = yaml.parse(content); - - // Handle new detailed module format - const modules = manifestData.modules || []; - - // For backward compatibility: if modules is an array of strings (old format), - // the calling code may need the array of names - const moduleNames = modules.map((m) => (typeof m === 'string' ? m : m.name)); - - // Check if we have the new detailed format - const hasDetailedModules = modules.length > 0 && typeof modules[0] === 'object'; - - // Flatten the structure for compatibility with existing code - return { - version: manifestData.installation?.version, - installDate: manifestData.installation?.installDate, - lastUpdated: manifestData.installation?.lastUpdated, - modules: moduleNames, // Simple array of module names for backward compatibility - modulesDetailed: hasDetailedModules ? modules : null, // New detailed format - customModules: manifestData.customModules || [], // Keep for backward compatibility - ides: manifestData.ides || [], - }; - } catch (error) { - await prompts.log.error(`Failed to read YAML manifest: ${error.message}`); - } - } - - return null; - } - - /** - * Update existing manifest - * @param {string} bmadDir - Path to bmad directory - * @param {Object} updates - Fields to update - * @param {Array} installedFiles - Updated list of installed files - */ - async update(bmadDir, updates, installedFiles = null) { - const yaml = require('yaml'); - const manifest = (await this._readRaw(bmadDir)) || { - installation: {}, - modules: [], - ides: [], - }; - - // Handle module updates - if (updates.modules) { - // If modules is being updated, we need to preserve detailed module info - const existingDetailed = manifest.modules || []; - const incomingNames = updates.modules; - - // Build updated modules array - const updatedModules = []; - for (const name of incomingNames) { - const existing = existingDetailed.find((m) => m.name === name); - if (existing) { - // Preserve existing details, update lastUpdated if this module is being updated - updatedModules.push({ - ...existing, - lastUpdated: new Date().toISOString(), - }); - } else { - // New module - add with minimal details - updatedModules.push({ - name, - version: null, - installDate: new Date().toISOString(), - lastUpdated: new Date().toISOString(), - source: 'unknown', - }); - } - } - - manifest.modules = updatedModules; - } - - // Merge other updates - if (updates.version) { - manifest.installation.version = updates.version; - } - if (updates.installDate) { - manifest.installation.installDate = updates.installDate; - } - manifest.installation.lastUpdated = new Date().toISOString(); - - if (updates.ides) { - manifest.ides = updates.ides; - } - - // Handle per-module version updates - if (updates.moduleVersions) { - for (const [moduleName, versionInfo] of Object.entries(updates.moduleVersions)) { - const moduleIndex = manifest.modules.findIndex((m) => m.name === moduleName); - if (moduleIndex !== -1) { - manifest.modules[moduleIndex] = { - ...manifest.modules[moduleIndex], - ...versionInfo, - lastUpdated: new Date().toISOString(), - }; - } - } - } - - // Handle adding a new module with version info - if (updates.addModule) { - const { name, version, source, npmPackage, repoUrl } = updates.addModule; - const existing = manifest.modules.find((m) => m.name === name); - if (!existing) { - manifest.modules.push({ - name, - version: version || null, - installDate: new Date().toISOString(), - lastUpdated: new Date().toISOString(), - source: source || 'external', - npmPackage: npmPackage || null, - repoUrl: repoUrl || null, - }); - } - } - - const manifestPath = path.join(bmadDir, '_config', 'manifest.yaml'); - await fs.ensureDir(path.dirname(manifestPath)); - - // Clean the manifest data to remove any non-serializable values - const cleanManifestData = structuredClone(manifest); - - const yamlContent = yaml.stringify(cleanManifestData, { - indent: 2, - lineWidth: 0, - sortKeys: false, - }); - - // Ensure POSIX-compliant final newline - const content = yamlContent.endsWith('\n') ? yamlContent : yamlContent + '\n'; - await fs.writeFile(manifestPath, content, 'utf8'); - - // Return the flattened format for compatibility - return this._flattenManifest(manifest); - } - - /** - * Read raw manifest data without flattening - * @param {string} bmadDir - Path to bmad directory - * @returns {Object|null} Raw manifest data or null if not found - */ - async _readRaw(bmadDir) { - const yamlPath = path.join(bmadDir, '_config', 'manifest.yaml'); - const yaml = require('yaml'); - - if (await fs.pathExists(yamlPath)) { - try { - const content = await fs.readFile(yamlPath, 'utf8'); - return yaml.parse(content); - } catch (error) { - await prompts.log.error(`Failed to read YAML manifest: ${error.message}`); - } - } - - return null; - } - - /** - * Flatten manifest for backward compatibility - * @param {Object} manifest - Raw manifest data - * @returns {Object} Flattened manifest - */ - _flattenManifest(manifest) { - const modules = manifest.modules || []; - const moduleNames = modules.map((m) => (typeof m === 'string' ? m : m.name)); - const hasDetailedModules = modules.length > 0 && typeof modules[0] === 'object'; - - return { - version: manifest.installation?.version, - installDate: manifest.installation?.installDate, - lastUpdated: manifest.installation?.lastUpdated, - modules: moduleNames, - modulesDetailed: hasDetailedModules ? modules : null, - customModules: manifest.customModules || [], - ides: manifest.ides || [], - }; - } - - /** - * Add a module to the manifest with optional version info - * If module already exists, update its version info - * @param {string} bmadDir - Path to bmad directory - * @param {string} moduleName - Module name to add - * @param {Object} options - Optional version info - */ - async addModule(bmadDir, moduleName, options = {}) { - const manifest = await this._readRaw(bmadDir); - if (!manifest) { - throw new Error('No manifest found'); - } - - if (!manifest.modules) { - manifest.modules = []; - } - - const existingIndex = manifest.modules.findIndex((m) => m.name === moduleName); - - if (existingIndex === -1) { - // Module doesn't exist, add it - manifest.modules.push({ - name: moduleName, - version: options.version || null, - installDate: new Date().toISOString(), - lastUpdated: new Date().toISOString(), - source: options.source || 'unknown', - npmPackage: options.npmPackage || null, - repoUrl: options.repoUrl || null, - }); - } else { - // Module exists, update its version info - const existing = manifest.modules[existingIndex]; - manifest.modules[existingIndex] = { - ...existing, - version: options.version === undefined ? existing.version : options.version, - source: options.source || existing.source, - npmPackage: options.npmPackage === undefined ? existing.npmPackage : options.npmPackage, - repoUrl: options.repoUrl === undefined ? existing.repoUrl : options.repoUrl, - lastUpdated: new Date().toISOString(), - }; - } - - await this._writeRaw(bmadDir, manifest); - } - - /** - * Remove a module from the manifest - * @param {string} bmadDir - Path to bmad directory - * @param {string} moduleName - Module name to remove - */ - async removeModule(bmadDir, moduleName) { - const manifest = await this._readRaw(bmadDir); - if (!manifest || !manifest.modules) { - return; - } - - const index = manifest.modules.findIndex((m) => m.name === moduleName); - if (index !== -1) { - manifest.modules.splice(index, 1); - await this._writeRaw(bmadDir, manifest); - } - } - - /** - * Update a single module's version info - * @param {string} bmadDir - Path to bmad directory - * @param {string} moduleName - Module name - * @param {Object} versionInfo - Version info to update - */ - async updateModuleVersion(bmadDir, moduleName, versionInfo) { - const manifest = await this._readRaw(bmadDir); - if (!manifest || !manifest.modules) { - return; - } - - const index = manifest.modules.findIndex((m) => m.name === moduleName); - if (index !== -1) { - manifest.modules[index] = { - ...manifest.modules[index], - ...versionInfo, - lastUpdated: new Date().toISOString(), - }; - await this._writeRaw(bmadDir, manifest); - } - } - - /** - * Get version info for a specific module - * @param {string} bmadDir - Path to bmad directory - * @param {string} moduleName - Module name - * @returns {Object|null} Module version info or null - */ - async getModuleVersion(bmadDir, moduleName) { - const manifest = await this._readRaw(bmadDir); - if (!manifest || !manifest.modules) { - return null; - } - - return manifest.modules.find((m) => m.name === moduleName) || null; - } - - /** - * Get all modules with their version info - * @param {string} bmadDir - Path to bmad directory - * @returns {Array} Array of module info objects - */ - async getAllModuleVersions(bmadDir) { - const manifest = await this._readRaw(bmadDir); - if (!manifest || !manifest.modules) { - return []; - } - - return manifest.modules; - } - - /** - * Write raw manifest data to file - * @param {string} bmadDir - Path to bmad directory - * @param {Object} manifestData - Raw manifest data to write - */ - async _writeRaw(bmadDir, manifestData) { - const yaml = require('yaml'); - const manifestPath = path.join(bmadDir, '_config', 'manifest.yaml'); - - await fs.ensureDir(path.dirname(manifestPath)); - - const cleanManifestData = structuredClone(manifestData); - - const yamlContent = yaml.stringify(cleanManifestData, { - indent: 2, - lineWidth: 0, - sortKeys: false, - }); - - const content = yamlContent.endsWith('\n') ? yamlContent : yamlContent + '\n'; - await fs.writeFile(manifestPath, content, 'utf8'); - } - - /** - * Add an IDE configuration to the manifest - * @param {string} bmadDir - Path to bmad directory - * @param {string} ideName - IDE name to add - */ - async addIde(bmadDir, ideName) { - const manifest = await this.read(bmadDir); - if (!manifest) { - throw new Error('No manifest found'); - } - - if (!manifest.ides) { - manifest.ides = []; - } - - if (!manifest.ides.includes(ideName)) { - manifest.ides.push(ideName); - await this.update(bmadDir, { ides: manifest.ides }); - } - } - - /** - * Calculate SHA256 hash of a file - * @param {string} filePath - Path to file - * @returns {string} SHA256 hash - */ - async calculateFileHash(filePath) { - try { - const content = await fs.readFile(filePath); - return crypto.createHash('sha256').update(content).digest('hex'); - } catch { - return null; - } - } - - /** - * Parse installed files to extract metadata - * @param {Array} installedFiles - List of installed file paths - * @param {string} bmadDir - Path to bmad directory for relative paths - * @returns {Array} Array of file metadata objects - */ - async parseInstalledFiles(installedFiles, bmadDir) { - const fileMetadata = []; - - for (const filePath of installedFiles) { - const fileExt = path.extname(filePath).toLowerCase(); - // Make path relative to parent of bmad directory, starting with 'bmad/' - const relativePath = 'bmad' + filePath.replace(bmadDir, '').replaceAll('\\', '/'); - - // Calculate file hash - const hash = await this.calculateFileHash(filePath); - - // Handle markdown files - extract XML metadata if present - if (fileExt === '.md') { - try { - if (await fs.pathExists(filePath)) { - const content = await fs.readFile(filePath, 'utf8'); - const metadata = this.extractXmlNodeAttributes(content, filePath, relativePath); - - if (metadata) { - // Has XML metadata - metadata.hash = hash; - fileMetadata.push(metadata); - } else { - // No XML metadata - still track the file - fileMetadata.push({ - file: relativePath, - type: 'md', - name: path.basename(filePath, fileExt), - title: null, - hash: hash, - }); - } - } - } catch (error) { - await prompts.log.warn(`Could not parse ${filePath}: ${error.message}`); - } - } - // Handle other file types (CSV, JSON, YAML, etc.) - else { - fileMetadata.push({ - file: relativePath, - type: fileExt.slice(1), // Remove the dot - name: path.basename(filePath, fileExt), - title: null, - hash: hash, - }); - } - } - - return fileMetadata; - } - - /** - * Extract XML node attributes from MD file content - * @param {string} content - File content - * @param {string} filePath - File path for context - * @param {string} relativePath - Relative path starting with 'bmad/' - * @returns {Object|null} Extracted metadata or null - */ - extractXmlNodeAttributes(content, filePath, relativePath) { - // Look for XML blocks in code fences - const xmlBlockMatch = content.match(/```xml\s*([\s\S]*?)```/); - if (!xmlBlockMatch) { - return null; - } - - const xmlContent = xmlBlockMatch[1]; - - // Extract root XML node (agent, task, template, etc.) - const rootNodeMatch = xmlContent.match(/<(\w+)([^>]*)>/); - if (!rootNodeMatch) { - return null; - } - - const nodeType = rootNodeMatch[1]; - const attributes = rootNodeMatch[2]; - - // Extract name and title attributes (id not needed since we have path) - const nameMatch = attributes.match(/name="([^"]*)"/); - const titleMatch = attributes.match(/title="([^"]*)"/); - - return { - file: relativePath, - type: nodeType, - name: nameMatch ? nameMatch[1] : null, - title: titleMatch ? titleMatch[1] : null, - }; - } - - /** - * Generate CSV manifest content - * @param {Object} data - Manifest data - * @param {Array} fileMetadata - File metadata array - * @param {Object} moduleConfigs - Module configuration data - * @returns {string} CSV content - */ - generateManifestCsv(data, fileMetadata, moduleConfigs = {}) { - const timestamp = new Date().toISOString(); - let csv = []; - - // Header section - csv.push( - '# BMAD Manifest', - `# Generated: ${timestamp}`, - '', - '## Installation Info', - 'Property,Value', - `Version,${data.version}`, - `InstallDate,${data.installDate || timestamp}`, - `LastUpdated,${data.lastUpdated || timestamp}`, - ); - if (data.language) { - csv.push(`Language,${data.language}`); - } - csv.push(''); - - // Modules section - if (data.modules && data.modules.length > 0) { - csv.push('## Modules', 'Name,Version,ShortTitle'); - for (const moduleName of data.modules) { - const config = moduleConfigs[moduleName] || {}; - csv.push([moduleName, config.version || '', config['short-title'] || ''].map((v) => this.escapeCsv(v)).join(',')); - } - csv.push(''); - } - - // IDEs section - if (data.ides && data.ides.length > 0) { - csv.push('## IDEs', 'IDE'); - for (const ide of data.ides) { - csv.push(this.escapeCsv(ide)); - } - csv.push(''); - } - - // Files section - NO LONGER USED - // Files are now tracked in files-manifest.csv by ManifestGenerator - - return csv.join('\n'); - } - - /** - * Parse CSV manifest content back to object - * @param {string} csvContent - CSV content to parse - * @returns {Object} Parsed manifest data - */ - parseManifestCsv(csvContent) { - const result = { - modules: [], - ides: [], - files: [], - }; - - const lines = csvContent.split('\n'); - let section = ''; - - for (const line_ of lines) { - const line = line_.trim(); - - // Skip empty lines and comments - if (!line || line.startsWith('#')) { - // Check for section headers - if (line.startsWith('## ')) { - section = line.slice(3).toLowerCase(); - } - continue; - } - - // Parse based on current section - switch (section) { - case 'installation info': { - // Skip header row - if (line === 'Property,Value') continue; - - const [property, ...valueParts] = line.split(','); - const value = this.unescapeCsv(valueParts.join(',')); - - switch (property) { - // Path no longer stored in manifest - case 'Version': { - result.version = value; - break; - } - case 'InstallDate': { - result.installDate = value; - break; - } - case 'LastUpdated': { - result.lastUpdated = value; - break; - } - case 'Language': { - result.language = value; - break; - } - } - - break; - } - case 'modules': { - // Skip header row - if (line === 'Name,Version,ShortTitle') continue; - - const parts = this.parseCsvLine(line); - if (parts[0]) { - result.modules.push(parts[0]); - } - - break; - } - case 'ides': { - // Skip header row - if (line === 'IDE') continue; - - result.ides.push(this.unescapeCsv(line)); - - break; - } - case 'files': { - // Skip header rows (support both old and new format) - if (line === 'Type,Path,Name,Title' || line === 'Type,Path,Name,Title,Hash') continue; - - const parts = this.parseCsvLine(line); - if (parts.length >= 2) { - result.files.push({ - type: parts[0] || '', - file: parts[1] || '', - name: parts[2] || null, - title: parts[3] || null, - hash: parts[4] || null, // Hash column (may not exist in old manifests) - }); - } - - break; - } - // No default - } - } - - return result; - } - - /** - * Parse a CSV line handling quotes and commas - * @param {string} line - CSV line to parse - * @returns {Array} Array of values - */ - parseCsvLine(line) { - const result = []; - let current = ''; - let inQuotes = false; - - for (let i = 0; i < line.length; i++) { - const char = line[i]; - - if (char === '"') { - if (inQuotes && line[i + 1] === '"') { - // Escaped quote - current += '"'; - i++; - } else { - // Toggle quote state - inQuotes = !inQuotes; - } - } else if (char === ',' && !inQuotes) { - // Field separator - result.push(this.unescapeCsv(current)); - current = ''; - } else { - current += char; - } - } - - // Add the last field - result.push(this.unescapeCsv(current)); - - return result; - } - - /** - * Escape CSV special characters - * @param {string} text - Text to escape - * @returns {string} Escaped text - */ - escapeCsv(text) { - if (!text) return ''; - const str = String(text); - - // If contains comma, newline, or quote, wrap in quotes and escape quotes - if (str.includes(',') || str.includes('\n') || str.includes('"')) { - return '"' + str.replaceAll('"', '""') + '"'; - } - - return str; - } - - /** - * Unescape CSV field - * @param {string} text - Text to unescape - * @returns {string} Unescaped text - */ - unescapeCsv(text) { - if (!text) return ''; - - // Remove surrounding quotes if present - if (text.startsWith('"') && text.endsWith('"')) { - text = text.slice(1, -1); - // Unescape doubled quotes - text = text.replaceAll('""', '"'); - } - - return text; - } - - /** - * Load module configuration files - * @param {Array} modules - List of module names - * @returns {Object} Module configurations indexed by name - */ - async loadModuleConfigs(modules) { - const configs = {}; - - for (const moduleName of modules) { - // Handle core module differently - it's in src/core not src/modules/core - const configPath = - moduleName === 'core' - ? path.join(process.cwd(), 'src', 'core', 'config.yaml') - : path.join(process.cwd(), 'src', 'modules', moduleName, 'config.yaml'); - - try { - if (await fs.pathExists(configPath)) { - const yaml = require('yaml'); - const content = await fs.readFile(configPath, 'utf8'); - configs[moduleName] = yaml.parse(content); - } - } catch (error) { - await prompts.log.warn(`Could not load config for module ${moduleName}: ${error.message}`); - } - } - - return configs; - } - /** - * Add a custom module to the manifest with its source path - * @param {string} bmadDir - Path to bmad directory - * @param {Object} customModule - Custom module info - */ - async addCustomModule(bmadDir, customModule) { - const manifest = await this.read(bmadDir); - if (!manifest) { - throw new Error('No manifest found'); - } - - if (!manifest.customModules) { - manifest.customModules = []; - } - - // Check if custom module already exists - const existingIndex = manifest.customModules.findIndex((m) => m.id === customModule.id); - if (existingIndex === -1) { - // Add new entry - manifest.customModules.push(customModule); - } else { - // Update existing entry - manifest.customModules[existingIndex] = customModule; - } - - await this.update(bmadDir, { customModules: manifest.customModules }); - } - - /** - * Remove a custom module from the manifest - * @param {string} bmadDir - Path to bmad directory - * @param {string} moduleId - Module ID to remove - */ - async removeCustomModule(bmadDir, moduleId) { - const manifest = await this.read(bmadDir); - if (!manifest || !manifest.customModules) { - return; - } - - const index = manifest.customModules.findIndex((m) => m.id === moduleId); - if (index !== -1) { - manifest.customModules.splice(index, 1); - await this.update(bmadDir, { customModules: manifest.customModules }); - } - } - - /** - * Get module version info from source - * @param {string} moduleName - Module name/code - * @param {string} bmadDir - Path to bmad directory - * @param {string} moduleSourcePath - Optional source path for custom modules - * @returns {Object} Version info object with version, source, npmPackage, repoUrl - */ - async getModuleVersionInfo(moduleName, bmadDir, moduleSourcePath = null) { - const os = require('node:os'); - const yaml = require('yaml'); - - // Built-in modules use BMad version (only core and bmm are in BMAD-METHOD repo) - if (['core', 'bmm'].includes(moduleName)) { - const bmadVersion = require(path.join(getProjectRoot(), 'package.json')).version; - return { - version: bmadVersion, - source: 'built-in', - npmPackage: null, - repoUrl: null, - }; - } - - // Check if this is an external official module - const { ExternalModuleManager } = require('../modules/external-manager'); - const extMgr = new ExternalModuleManager(); - const moduleInfo = await extMgr.getModuleByCode(moduleName); - - if (moduleInfo) { - // External module - try to get version from npm registry first, then fall back to cache - let version = null; - - if (moduleInfo.npmPackage) { - // Fetch version from npm registry - try { - version = await this.fetchNpmVersion(moduleInfo.npmPackage); - } catch { - // npm fetch failed, try cache as fallback - } - } - - // If npm didn't work, try reading from cached repo's package.json - if (!version) { - const cacheDir = path.join(os.homedir(), '.bmad', 'cache', 'external-modules', moduleName); - const packageJsonPath = path.join(cacheDir, 'package.json'); - - if (await fs.pathExists(packageJsonPath)) { - try { - const pkg = require(packageJsonPath); - version = pkg.version; - } catch (error) { - await prompts.log.warn(`Failed to read package.json for ${moduleName}: ${error.message}`); - } - } - } - - return { - version: version, - source: 'external', - npmPackage: moduleInfo.npmPackage || null, - repoUrl: moduleInfo.url || null, - }; - } - - // Custom module - check cache directory - const cacheDir = path.join(bmadDir, '_config', 'custom', moduleName); - const moduleYamlPath = path.join(cacheDir, 'module.yaml'); - - if (await fs.pathExists(moduleYamlPath)) { - try { - const yamlContent = await fs.readFile(moduleYamlPath, 'utf8'); - const moduleConfig = yaml.parse(yamlContent); - return { - version: moduleConfig.version || null, - source: 'custom', - npmPackage: moduleConfig.npmPackage || null, - repoUrl: moduleConfig.repoUrl || null, - }; - } catch (error) { - await prompts.log.warn(`Failed to read module.yaml for ${moduleName}: ${error.message}`); - } - } - - // Unknown module - return { - version: null, - source: 'unknown', - npmPackage: null, - repoUrl: null, - }; - } - - /** - * Fetch latest version from npm for a package - * @param {string} packageName - npm package name - * @returns {string|null} Latest version or null - */ - async fetchNpmVersion(packageName) { - try { - const https = require('node:https'); - const { execSync } = require('node:child_process'); - - // Try using npm view first (more reliable) - try { - const result = execSync(`npm view ${packageName} version`, { - encoding: 'utf8', - stdio: 'pipe', - timeout: 10_000, - }); - return result.trim(); - } catch { - // Fallback to npm registry API - return new Promise((resolve, reject) => { - https - .get(`https://registry.npmjs.org/${packageName}`, (res) => { - let data = ''; - res.on('data', (chunk) => (data += chunk)); - res.on('end', () => { - try { - const pkg = JSON.parse(data); - resolve(pkg['dist-tags']?.latest || pkg.version || null); - } catch { - resolve(null); - } - }); - }) - .on('error', () => resolve(null)); - }); - } - } catch { - return null; - } - } - - /** - * Check for available updates for installed modules - * @param {string} bmadDir - Path to bmad directory - * @returns {Array} Array of update info objects - */ - async checkForUpdates(bmadDir) { - const modules = await this.getAllModuleVersions(bmadDir); - const updates = []; - - for (const module of modules) { - if (!module.npmPackage) { - continue; // Skip modules without npm package (built-in) - } - - const latestVersion = await this.fetchNpmVersion(module.npmPackage); - if (!latestVersion) { - continue; - } - - if (module.version !== latestVersion) { - updates.push({ - name: module.name, - installedVersion: module.version, - latestVersion: latestVersion, - npmPackage: module.npmPackage, - updateAvailable: true, - }); - } - } - - return updates; - } - - /** - * Compare two semantic versions - * @param {string} v1 - First version - * @param {string} v2 - Second version - * @returns {number} -1 if v1 < v2, 0 if v1 == v2, 1 if v1 > v2 - */ - compareVersions(v1, v2) { - if (!v1 || !v2) return 0; - - const normalize = (v) => { - // Remove leading 'v' if present - v = v.replace(/^v/, ''); - // Handle prerelease tags - const parts = v.split('-'); - const main = parts[0].split('.'); - const prerelease = parts[1]; - return { main, prerelease }; - }; - - const n1 = normalize(v1); - const n2 = normalize(v2); - - // Compare main version parts - for (let i = 0; i < 3; i++) { - const num1 = parseInt(n1.main[i] || '0', 10); - const num2 = parseInt(n2.main[i] || '0', 10); - if (num1 !== num2) { - return num1 < num2 ? -1 : 1; - } - } - - // If main versions are equal, compare prerelease - if (n1.prerelease && n2.prerelease) { - return n1.prerelease < n2.prerelease ? -1 : n1.prerelease > n2.prerelease ? 1 : 0; - } - if (n1.prerelease) return -1; // Prerelease is older than stable - if (n2.prerelease) return 1; // Stable is newer than prerelease - - return 0; - } -} - -module.exports = { Manifest }; diff --git a/tools/cli/installers/lib/custom/handler.js b/tools/cli/installers/lib/custom/handler.js deleted file mode 100644 index 52595e4ff..000000000 --- a/tools/cli/installers/lib/custom/handler.js +++ /dev/null @@ -1,358 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const yaml = require('yaml'); -const prompts = require('../../../lib/prompts'); -const { FileOps } = require('../../../lib/file-ops'); -const { XmlHandler } = require('../../../lib/xml-handler'); - -/** - * Handler for custom content (custom.yaml) - * Installs custom agents and workflows without requiring a full module structure - */ -class CustomHandler { - constructor() { - this.fileOps = new FileOps(); - this.xmlHandler = new XmlHandler(); - } - - /** - * Find all custom.yaml files in the project - * @param {string} projectRoot - Project root directory - * @returns {Array} List of custom content paths - */ - async findCustomContent(projectRoot) { - const customPaths = []; - - // Helper function to recursively scan directories - async function scanDirectory(dir, excludePaths = []) { - try { - const entries = await fs.readdir(dir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(dir, entry.name); - - // Skip hidden directories and common exclusions - if ( - entry.name.startsWith('.') || - entry.name === 'node_modules' || - entry.name === 'dist' || - entry.name === 'build' || - entry.name === '.git' || - entry.name === 'bmad' - ) { - continue; - } - - // Skip excluded paths - if (excludePaths.some((exclude) => fullPath.startsWith(exclude))) { - continue; - } - - if (entry.isDirectory()) { - // Recursively scan subdirectories - await scanDirectory(fullPath, excludePaths); - } else if (entry.name === 'custom.yaml') { - // Found a custom.yaml file - customPaths.push(fullPath); - } else if ( - entry.name === 'module.yaml' && // Check if this is a custom module (in root directory) - // Skip if it's in src/modules (those are standard modules) - !fullPath.includes(path.join('src', 'modules')) - ) { - customPaths.push(fullPath); - } - } - } catch { - // Ignore errors (e.g., permission denied) - } - } - - // Scan the entire project, but exclude source directories - await scanDirectory(projectRoot, [path.join(projectRoot, 'src'), path.join(projectRoot, 'tools'), path.join(projectRoot, 'test')]); - - return customPaths; - } - - /** - * Get custom content info from a custom.yaml or module.yaml file - * @param {string} configPath - Path to config file - * @param {string} projectRoot - Project root directory for calculating relative paths - * @returns {Object|null} Custom content info - */ - async getCustomInfo(configPath, projectRoot = null) { - try { - const configContent = await fs.readFile(configPath, 'utf8'); - - // Try to parse YAML with error handling - let config; - try { - config = yaml.parse(configContent); - } catch (parseError) { - await prompts.log.warn('YAML parse error in ' + configPath + ': ' + parseError.message); - return null; - } - - // Check if this is an module.yaml (module) or custom.yaml (custom content) - const isInstallConfig = configPath.endsWith('module.yaml'); - const configDir = path.dirname(configPath); - - // Use provided projectRoot or fall back to process.cwd() - const basePath = projectRoot || process.cwd(); - const relativePath = path.relative(basePath, configDir); - - return { - id: config.code || 'unknown-code', - name: config.name, - description: config.description || '', - path: configDir, - relativePath: relativePath, - defaultSelected: config.default_selected === true, - config: config, - isInstallConfig: isInstallConfig, // Track which type this is - }; - } catch (error) { - await prompts.log.warn('Failed to read ' + configPath + ': ' + error.message); - return null; - } - } - - /** - * Install custom content - * @param {string} customPath - Path to custom content directory - * @param {string} bmadDir - Target bmad directory - * @param {Object} config - Configuration from custom.yaml - * @param {Function} fileTrackingCallback - Optional callback to track installed files - * @returns {Object} Installation result - */ - async install(customPath, bmadDir, config, fileTrackingCallback = null) { - const results = { - agentsInstalled: 0, - workflowsInstalled: 0, - filesCopied: 0, - preserved: 0, - errors: [], - }; - - try { - // Create custom directories in bmad - const bmadCustomDir = path.join(bmadDir, 'custom'); - const bmadAgentsDir = path.join(bmadCustomDir, 'agents'); - const bmadWorkflowsDir = path.join(bmadCustomDir, 'workflows'); - - await fs.ensureDir(bmadCustomDir); - await fs.ensureDir(bmadAgentsDir); - await fs.ensureDir(bmadWorkflowsDir); - - // Process agents - compile and copy agents - const agentsDir = path.join(customPath, 'agents'); - if (await fs.pathExists(agentsDir)) { - await this.compileAndCopyAgents(agentsDir, bmadAgentsDir, bmadDir, config, fileTrackingCallback, results); - - // Count agent files - const agentFiles = await this.findFilesRecursively(agentsDir, ['.agent.yaml', '.md']); - results.agentsInstalled = agentFiles.length; - } - - // Process workflows - copy entire workflows directory structure - const workflowsDir = path.join(customPath, 'workflows'); - if (await fs.pathExists(workflowsDir)) { - await this.copyDirectory(workflowsDir, bmadWorkflowsDir, results, fileTrackingCallback, config); - - // Count workflow files - const workflowFiles = await this.findFilesRecursively(workflowsDir, ['.md']); - results.workflowsInstalled = workflowFiles.length; - } - - // Process any additional files at root - const entries = await fs.readdir(customPath, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isFile() && entry.name !== 'custom.yaml' && !entry.name.startsWith('.') && !entry.name.endsWith('.md')) { - // Skip .md files at root as they're likely docs - const sourcePath = path.join(customPath, entry.name); - const targetPath = path.join(bmadCustomDir, entry.name); - - try { - // Check if file already exists - if (await fs.pathExists(targetPath)) { - // File already exists, preserve it - results.preserved = (results.preserved || 0) + 1; - } else { - await fs.copy(sourcePath, targetPath); - results.filesCopied++; - - if (fileTrackingCallback) { - fileTrackingCallback(targetPath); - } - } - } catch (error) { - results.errors.push(`Failed to copy file ${entry.name}: ${error.message}`); - } - } - } - } catch (error) { - results.errors.push(`Installation failed: ${error.message}`); - } - - return results; - } - - /** - * Find all files with specific extensions recursively - * @param {string} dir - Directory to search - * @param {Array} extensions - File extensions to match - * @returns {Array} List of matching files - */ - async findFilesRecursively(dir, extensions) { - const files = []; - - async function search(currentDir) { - const entries = await fs.readdir(currentDir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(currentDir, entry.name); - - if (entry.isDirectory()) { - await search(fullPath); - } else if (extensions.some((ext) => entry.name.endsWith(ext))) { - files.push(fullPath); - } - } - } - - await search(dir); - return files; - } - - /** - * Recursively copy a directory - * @param {string} sourceDir - Source directory - * @param {string} targetDir - Target directory - * @param {Object} results - Results object to update - * @param {Function} fileTrackingCallback - Optional callback - * @param {Object} config - Configuration for placeholder replacement - */ - async copyDirectory(sourceDir, targetDir, results, fileTrackingCallback, config) { - await fs.ensureDir(targetDir); - const entries = await fs.readdir(sourceDir, { withFileTypes: true }); - - for (const entry of entries) { - const sourcePath = path.join(sourceDir, entry.name); - const targetPath = path.join(targetDir, entry.name); - - if (entry.isDirectory()) { - await this.copyDirectory(sourcePath, targetPath, results, fileTrackingCallback, config); - } else { - try { - // Check if file already exists - if (await fs.pathExists(targetPath)) { - // File already exists, preserve it - results.preserved = (results.preserved || 0) + 1; - } else { - // Copy with placeholder replacement for text files - const textExtensions = ['.md', '.yaml', '.yml', '.txt', '.json']; - if (textExtensions.some((ext) => entry.name.endsWith(ext))) { - // Read source content - let content = await fs.readFile(sourcePath, 'utf8'); - - // Replace placeholders - content = content.replaceAll('{user_name}', config.user_name || 'User'); - content = content.replaceAll('{communication_language}', config.communication_language || 'English'); - content = content.replaceAll('{output_folder}', config.output_folder || 'docs'); - - // Write to target - await fs.ensureDir(path.dirname(targetPath)); - await fs.writeFile(targetPath, content, 'utf8'); - } else { - // Copy binary files as-is - await fs.copy(sourcePath, targetPath); - } - - results.filesCopied++; - if (entry.name.endsWith('.md')) { - results.workflowsInstalled++; - } - if (fileTrackingCallback) { - fileTrackingCallback(targetPath); - } - } - } catch (error) { - results.errors.push(`Failed to copy ${entry.name}: ${error.message}`); - } - } - } - } - - /** - * Compile .agent.yaml files to .md format and handle sidecars - * @param {string} sourceAgentsPath - Source agents directory - * @param {string} targetAgentsPath - Target agents directory - * @param {string} bmadDir - BMAD installation directory - * @param {Object} config - Configuration for placeholder replacement - * @param {Function} fileTrackingCallback - Optional callback to track installed files - * @param {Object} results - Results object to update - */ - async compileAndCopyAgents(sourceAgentsPath, targetAgentsPath, bmadDir, config, fileTrackingCallback, results) { - // Get all .agent.yaml files recursively - const agentFiles = await this.findFilesRecursively(sourceAgentsPath, ['.agent.yaml']); - - for (const agentFile of agentFiles) { - const relativePath = path.relative(sourceAgentsPath, agentFile).split(path.sep).join('/'); - const targetDir = path.join(targetAgentsPath, path.dirname(relativePath)); - - await fs.ensureDir(targetDir); - - const agentName = path.basename(agentFile, '.agent.yaml'); - const targetMdPath = path.join(targetDir, `${agentName}.md`); - // Use the actual bmadDir if available (for when installing to temp dir) - const actualBmadDir = config._bmadDir || bmadDir; - const customizePath = path.join(actualBmadDir, '_config', 'agents', `custom-${agentName}.customize.yaml`); - - // Read and compile the YAML - try { - const yamlContent = await fs.readFile(agentFile, 'utf8'); - const { compileAgent } = require('../../../lib/agent/compiler'); - - // Create customize template if it doesn't exist - if (!(await fs.pathExists(customizePath))) { - const { getSourcePath } = require('../../../lib/project-root'); - const genericTemplatePath = getSourcePath('utility', 'agent-components', 'agent.customize.template.yaml'); - if (await fs.pathExists(genericTemplatePath)) { - let templateContent = await fs.readFile(genericTemplatePath, 'utf8'); - await fs.writeFile(customizePath, templateContent, 'utf8'); - // Only show customize creation in verbose mode - if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.message(' Created customize: custom-' + agentName + '.customize.yaml'); - } - } - } - - // Compile the agent - const { xml } = compileAgent(yamlContent, {}, agentName, relativePath, { config }); - - // Replace placeholders in the compiled content - let processedXml = xml; - processedXml = processedXml.replaceAll('{user_name}', config.user_name || 'User'); - processedXml = processedXml.replaceAll('{communication_language}', config.communication_language || 'English'); - processedXml = processedXml.replaceAll('{output_folder}', config.output_folder || 'docs'); - - // Write the compiled MD file - await fs.writeFile(targetMdPath, processedXml, 'utf8'); - - // Track the file - if (fileTrackingCallback) { - fileTrackingCallback(targetMdPath); - } - - // Only show compilation details in verbose mode - if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.message(' Compiled agent: ' + agentName + ' -> ' + path.relative(targetAgentsPath, targetMdPath)); - } - } catch (error) { - await prompts.log.warn(' Failed to compile agent ' + agentName + ': ' + error.message); - results.errors.push(`Failed to compile agent ${agentName}: ${error.message}`); - } - } - } -} - -module.exports = { CustomHandler }; diff --git a/tools/cli/installers/lib/ide/_base-ide.js b/tools/cli/installers/lib/ide/_base-ide.js deleted file mode 100644 index 9bfbdcf30..000000000 --- a/tools/cli/installers/lib/ide/_base-ide.js +++ /dev/null @@ -1,665 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const { XmlHandler } = require('../../../lib/xml-handler'); -const prompts = require('../../../lib/prompts'); -const { getSourcePath } = require('../../../lib/project-root'); -const { BMAD_FOLDER_NAME } = require('./shared/path-utils'); - -/** - * Base class for IDE-specific setup - * All IDE handlers should extend this class - */ -class BaseIdeSetup { - constructor(name, displayName = null, preferred = false) { - this.name = name; - this.displayName = displayName || name; // Human-readable name for UI - this.preferred = preferred; // Whether this IDE should be shown in preferred list - this.configDir = null; // Override in subclasses - this.rulesDir = null; // Override in subclasses - this.configFile = null; // Override in subclasses when detection is file-based - this.detectionPaths = []; // Additional paths that indicate the IDE is configured - this.xmlHandler = new XmlHandler(); - this.bmadFolderName = BMAD_FOLDER_NAME; // Default, can be overridden - } - - /** - * Set the bmad folder name for placeholder replacement - * @param {string} bmadFolderName - The bmad folder name - */ - setBmadFolderName(bmadFolderName) { - this.bmadFolderName = bmadFolderName; - } - - /** - * Get the agent command activation header from the central template - * @returns {string} The activation header text - */ - async getAgentCommandHeader() { - const headerPath = getSourcePath('utility', 'agent-components', 'agent-command-header.md'); - return await fs.readFile(headerPath, 'utf8'); - } - - /** - * Main setup method - must be implemented by subclasses - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {Object} options - Setup options - */ - async setup(projectDir, bmadDir, options = {}) { - throw new Error(`setup() must be implemented by ${this.name} handler`); - } - - /** - * Cleanup IDE configuration - * @param {string} projectDir - Project directory - */ - async cleanup(projectDir, options = {}) { - // Default implementation - can be overridden - if (this.configDir) { - const configPath = path.join(projectDir, this.configDir); - if (await fs.pathExists(configPath)) { - const bmadRulesPath = path.join(configPath, BMAD_FOLDER_NAME); - if (await fs.pathExists(bmadRulesPath)) { - await fs.remove(bmadRulesPath); - if (!options.silent) await prompts.log.message(`Removed ${this.name} BMAD configuration`); - } - } - } - } - - /** - * Install a custom agent launcher - subclasses should override - * @param {string} projectDir - Project directory - * @param {string} agentName - Agent name (e.g., "fred-commit-poet") - * @param {string} agentPath - Path to compiled agent (relative to project root) - * @param {Object} metadata - Agent metadata - * @returns {Object|null} Info about created command, or null if not supported - */ - async installCustomAgentLauncher(projectDir, agentName, agentPath, metadata) { - // Default implementation - subclasses can override - return null; - } - - /** - * Detect whether this IDE already has configuration in the project - * Subclasses can override for custom logic - * @param {string} projectDir - Project directory - * @returns {boolean} - */ - async detect(projectDir) { - const pathsToCheck = []; - - if (this.configDir) { - pathsToCheck.push(path.join(projectDir, this.configDir)); - } - - if (this.configFile) { - pathsToCheck.push(path.join(projectDir, this.configFile)); - } - - if (Array.isArray(this.detectionPaths)) { - for (const candidate of this.detectionPaths) { - if (!candidate) continue; - const resolved = path.isAbsolute(candidate) ? candidate : path.join(projectDir, candidate); - pathsToCheck.push(resolved); - } - } - - for (const candidate of pathsToCheck) { - if (await fs.pathExists(candidate)) { - return true; - } - } - - return false; - } - - /** - * Get list of agents from BMAD installation - * @param {string} bmadDir - BMAD installation directory - * @returns {Array} List of agent files - */ - async getAgents(bmadDir) { - const agents = []; - - // Get core agents - const coreAgentsPath = path.join(bmadDir, 'core', 'agents'); - if (await fs.pathExists(coreAgentsPath)) { - const coreAgents = await this.scanDirectory(coreAgentsPath, '.md'); - agents.push( - ...coreAgents.map((a) => ({ - ...a, - module: 'core', - })), - ); - } - - // Get module agents - const entries = await fs.readdir(bmadDir, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isDirectory() && entry.name !== 'core' && entry.name !== '_config' && entry.name !== 'agents') { - const moduleAgentsPath = path.join(bmadDir, entry.name, 'agents'); - if (await fs.pathExists(moduleAgentsPath)) { - const moduleAgents = await this.scanDirectory(moduleAgentsPath, '.md'); - agents.push( - ...moduleAgents.map((a) => ({ - ...a, - module: entry.name, - })), - ); - } - } - } - - // Get standalone agents from bmad/agents/ directory - const standaloneAgentsDir = path.join(bmadDir, 'agents'); - if (await fs.pathExists(standaloneAgentsDir)) { - const agentDirs = await fs.readdir(standaloneAgentsDir, { withFileTypes: true }); - - for (const agentDir of agentDirs) { - if (!agentDir.isDirectory()) continue; - - const agentDirPath = path.join(standaloneAgentsDir, agentDir.name); - const agentFiles = await fs.readdir(agentDirPath); - - for (const file of agentFiles) { - if (!file.endsWith('.md')) continue; - if (file.includes('.customize.')) continue; - - const filePath = path.join(agentDirPath, file); - const content = await fs.readFile(filePath, 'utf8'); - - if (content.includes('localskip="true"')) continue; - - agents.push({ - name: file.replace('.md', ''), - path: filePath, - relativePath: path.relative(standaloneAgentsDir, filePath), - filename: file, - module: 'standalone', // Mark as standalone agent - }); - } - } - } - - return agents; - } - - /** - * Get list of tasks from BMAD installation - * @param {string} bmadDir - BMAD installation directory - * @param {boolean} standaloneOnly - If true, only return standalone tasks - * @returns {Array} List of task files - */ - async getTasks(bmadDir, standaloneOnly = false) { - const tasks = []; - - // Get core tasks (scan for both .md and .xml) - const coreTasksPath = path.join(bmadDir, 'core', 'tasks'); - if (await fs.pathExists(coreTasksPath)) { - const coreTasks = await this.scanDirectoryWithStandalone(coreTasksPath, ['.md', '.xml']); - tasks.push( - ...coreTasks.map((t) => ({ - ...t, - module: 'core', - })), - ); - } - - // Get module tasks - const entries = await fs.readdir(bmadDir, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isDirectory() && entry.name !== 'core' && entry.name !== '_config' && entry.name !== 'agents') { - const moduleTasksPath = path.join(bmadDir, entry.name, 'tasks'); - if (await fs.pathExists(moduleTasksPath)) { - const moduleTasks = await this.scanDirectoryWithStandalone(moduleTasksPath, ['.md', '.xml']); - tasks.push( - ...moduleTasks.map((t) => ({ - ...t, - module: entry.name, - })), - ); - } - } - } - - // Filter by standalone if requested - if (standaloneOnly) { - return tasks.filter((t) => t.standalone === true); - } - - return tasks; - } - - /** - * Get list of tools from BMAD installation - * @param {string} bmadDir - BMAD installation directory - * @param {boolean} standaloneOnly - If true, only return standalone tools - * @returns {Array} List of tool files - */ - async getTools(bmadDir, standaloneOnly = false) { - const tools = []; - - // Get core tools (scan for both .md and .xml) - const coreToolsPath = path.join(bmadDir, 'core', 'tools'); - if (await fs.pathExists(coreToolsPath)) { - const coreTools = await this.scanDirectoryWithStandalone(coreToolsPath, ['.md', '.xml']); - tools.push( - ...coreTools.map((t) => ({ - ...t, - module: 'core', - })), - ); - } - - // Get module tools - const entries = await fs.readdir(bmadDir, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isDirectory() && entry.name !== 'core' && entry.name !== '_config' && entry.name !== 'agents') { - const moduleToolsPath = path.join(bmadDir, entry.name, 'tools'); - if (await fs.pathExists(moduleToolsPath)) { - const moduleTools = await this.scanDirectoryWithStandalone(moduleToolsPath, ['.md', '.xml']); - tools.push( - ...moduleTools.map((t) => ({ - ...t, - module: entry.name, - })), - ); - } - } - } - - // Filter by standalone if requested - if (standaloneOnly) { - return tools.filter((t) => t.standalone === true); - } - - return tools; - } - - /** - * Get list of workflows from BMAD installation - * @param {string} bmadDir - BMAD installation directory - * @param {boolean} standaloneOnly - If true, only return standalone workflows - * @returns {Array} List of workflow files - */ - async getWorkflows(bmadDir, standaloneOnly = false) { - const workflows = []; - - // Get core workflows - const coreWorkflowsPath = path.join(bmadDir, 'core', 'workflows'); - if (await fs.pathExists(coreWorkflowsPath)) { - const coreWorkflows = await this.findWorkflowYamlFiles(coreWorkflowsPath); - workflows.push( - ...coreWorkflows.map((w) => ({ - ...w, - module: 'core', - })), - ); - } - - // Get module workflows - const entries = await fs.readdir(bmadDir, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isDirectory() && entry.name !== 'core' && entry.name !== '_config' && entry.name !== 'agents') { - const moduleWorkflowsPath = path.join(bmadDir, entry.name, 'workflows'); - if (await fs.pathExists(moduleWorkflowsPath)) { - const moduleWorkflows = await this.findWorkflowYamlFiles(moduleWorkflowsPath); - workflows.push( - ...moduleWorkflows.map((w) => ({ - ...w, - module: entry.name, - })), - ); - } - } - } - - // Filter by standalone if requested - if (standaloneOnly) { - return workflows.filter((w) => w.standalone === true); - } - - return workflows; - } - - /** - * Recursively find workflow.yaml files - * @param {string} dir - Directory to search - * @returns {Array} List of workflow file info objects - */ - async findWorkflowYamlFiles(dir) { - const workflows = []; - - if (!(await fs.pathExists(dir))) { - return workflows; - } - - const entries = await fs.readdir(dir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(dir, entry.name); - - if (entry.isDirectory()) { - // Recursively search subdirectories - const subWorkflows = await this.findWorkflowYamlFiles(fullPath); - workflows.push(...subWorkflows); - } else if (entry.isFile() && entry.name === 'workflow.yaml') { - // Read workflow.yaml to get name and standalone property - try { - const yaml = require('yaml'); - const content = await fs.readFile(fullPath, 'utf8'); - const workflowData = yaml.parse(content); - - if (workflowData && workflowData.name) { - // Workflows are standalone by default unless explicitly false - const standalone = workflowData.standalone !== false && workflowData.standalone !== 'false'; - workflows.push({ - name: workflowData.name, - path: fullPath, - relativePath: path.relative(dir, fullPath), - filename: entry.name, - description: workflowData.description || '', - standalone: standalone, - }); - } - } catch { - // Skip invalid workflow files - } - } - } - - return workflows; - } - - /** - * Scan a directory for files with specific extension(s) - * @param {string} dir - Directory to scan - * @param {string|Array} ext - File extension(s) to match (e.g., '.md' or ['.md', '.xml']) - * @returns {Array} List of file info objects - */ - async scanDirectory(dir, ext) { - const files = []; - - if (!(await fs.pathExists(dir))) { - return files; - } - - // Normalize ext to array - const extensions = Array.isArray(ext) ? ext : [ext]; - - const entries = await fs.readdir(dir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(dir, entry.name); - - if (entry.isDirectory()) { - // Recursively scan subdirectories - const subFiles = await this.scanDirectory(fullPath, ext); - files.push(...subFiles); - } else if (entry.isFile()) { - // Check if file matches any of the extensions - const matchedExt = extensions.find((e) => entry.name.endsWith(e)); - if (matchedExt) { - files.push({ - name: path.basename(entry.name, matchedExt), - path: fullPath, - relativePath: path.relative(dir, fullPath), - filename: entry.name, - }); - } - } - } - - return files; - } - - /** - * Scan a directory for files with specific extension(s) and check standalone attribute - * @param {string} dir - Directory to scan - * @param {string|Array} ext - File extension(s) to match (e.g., '.md' or ['.md', '.xml']) - * @returns {Array} List of file info objects with standalone property - */ - async scanDirectoryWithStandalone(dir, ext) { - const files = []; - - if (!(await fs.pathExists(dir))) { - return files; - } - - // Normalize ext to array - const extensions = Array.isArray(ext) ? ext : [ext]; - - const entries = await fs.readdir(dir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(dir, entry.name); - - if (entry.isDirectory()) { - // Recursively scan subdirectories - const subFiles = await this.scanDirectoryWithStandalone(fullPath, ext); - files.push(...subFiles); - } else if (entry.isFile()) { - // Check if file matches any of the extensions - const matchedExt = extensions.find((e) => entry.name.endsWith(e)); - if (matchedExt) { - // Read file content to check for standalone attribute - // All non-internal files are considered standalone by default - let standalone = true; - try { - const content = await fs.readFile(fullPath, 'utf8'); - - // Skip internal/engine files (not user-facing) - if (content.includes('internal="true"')) { - continue; - } - - // Check for explicit standalone: false - if (entry.name.endsWith('.xml')) { - // For XML files, check for standalone="false" attribute - const tagMatch = content.match(/<(task|tool)[^>]*standalone="false"/); - standalone = !tagMatch; - } else if (entry.name.endsWith('.md')) { - // For MD files, parse YAML frontmatter - const frontmatterMatch = content.match(/^---\r?\n([\s\S]*?)\r?\n---/); - if (frontmatterMatch) { - try { - const yaml = require('yaml'); - const frontmatter = yaml.parse(frontmatterMatch[1]); - standalone = frontmatter.standalone !== false && frontmatter.standalone !== 'false'; - } catch { - // If YAML parsing fails, default to standalone - } - } - // No frontmatter means standalone (default) - } - } catch { - // If we can't read the file, default to standalone - standalone = true; - } - - files.push({ - name: path.basename(entry.name, matchedExt), - path: fullPath, - relativePath: path.relative(dir, fullPath), - filename: entry.name, - standalone: standalone, - }); - } - } - } - - return files; - } - - /** - * Create IDE command/rule file from agent or task - * @param {string} content - File content - * @param {Object} metadata - File metadata - * @param {string} projectDir - The actual project directory path - * @returns {string} Processed content - */ - processContent(content, metadata = {}, projectDir = null) { - // Replace placeholders - let processed = content; - - // Inject activation block for agent files FIRST (before replacements) - if (metadata.name && content.includes(' word.charAt(0).toUpperCase() + word.slice(1)) - .join(' '); - } - - /** - * Flatten a relative path to a single filename for flat slash command naming - * @deprecated Use toColonPath() or toDashPath() from shared/path-utils.js instead - * Example: 'module/agents/name.md' -> 'bmad-module-agents-name.md' - * Used by IDEs that ignore directory structure for slash commands (e.g., Antigravity, Codex) - * @param {string} relativePath - Relative path to flatten - * @returns {string} Flattened filename with 'bmad-' prefix - */ - flattenFilename(relativePath) { - const sanitized = relativePath.replaceAll(/[/\\]/g, '-'); - return `bmad-${sanitized}`; - } - - /** - * Create agent configuration file - * @param {string} bmadDir - BMAD installation directory - * @param {Object} agent - Agent information - */ - async createAgentConfig(bmadDir, agent) { - const agentConfigDir = path.join(bmadDir, '_config', 'agents'); - await this.ensureDir(agentConfigDir); - - // Load agent config template - const templatePath = getSourcePath('utility', 'models', 'agent-config-template.md'); - const templateContent = await this.readFile(templatePath); - - const configContent = `# Agent Config: ${agent.name} - -${templateContent}`; - - const configPath = path.join(agentConfigDir, `${agent.module}-${agent.name}.md`); - await this.writeFile(configPath, configContent); - } -} - -module.exports = { BaseIdeSetup }; diff --git a/tools/cli/installers/lib/ide/_config-driven.js b/tools/cli/installers/lib/ide/_config-driven.js deleted file mode 100644 index 813a6e674..000000000 --- a/tools/cli/installers/lib/ide/_config-driven.js +++ /dev/null @@ -1,634 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const { BaseIdeSetup } = require('./_base-ide'); -const prompts = require('../../../lib/prompts'); -const { AgentCommandGenerator } = require('./shared/agent-command-generator'); -const { WorkflowCommandGenerator } = require('./shared/workflow-command-generator'); -const { TaskToolCommandGenerator } = require('./shared/task-tool-command-generator'); - -/** - * Config-driven IDE setup handler - * - * This class provides a standardized way to install BMAD artifacts to IDEs - * based on configuration in platform-codes.yaml. It eliminates the need for - * individual installer files for each IDE. - * - * Features: - * - Config-driven from platform-codes.yaml - * - Template-based content generation - * - Multi-target installation support (e.g., GitHub Copilot) - * - Artifact type filtering (agents, workflows, tasks, tools) - */ -class ConfigDrivenIdeSetup extends BaseIdeSetup { - constructor(platformCode, platformConfig) { - super(platformCode, platformConfig.name, platformConfig.preferred); - this.platformConfig = platformConfig; - this.installerConfig = platformConfig.installer || null; - } - - /** - * Main setup method - called by IdeManager - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {Object} options - Setup options - * @returns {Promise} Setup result - */ - async setup(projectDir, bmadDir, options = {}) { - // Check for BMAD files in ancestor directories that would cause duplicates - if (this.installerConfig?.ancestor_conflict_check) { - const conflict = await this.findAncestorConflict(projectDir); - if (conflict) { - await prompts.log.error( - `Found existing BMAD commands in ancestor installation: ${conflict}\n` + - ` ${this.name} inherits commands from parent directories, so this would cause duplicates.\n` + - ` Please remove the BMAD files from that directory first:\n` + - ` rm -rf "${conflict}"/bmad*`, - ); - return { - success: false, - reason: 'ancestor-conflict', - error: `Ancestor conflict: ${conflict}`, - conflictDir: conflict, - }; - } - } - - if (!options.silent) await prompts.log.info(`Setting up ${this.name}...`); - - // Clean up any old BMAD installation first - await this.cleanup(projectDir, options); - - if (!this.installerConfig) { - return { success: false, reason: 'no-config' }; - } - - // Handle multi-target installations (e.g., GitHub Copilot) - if (this.installerConfig.targets) { - return this.installToMultipleTargets(projectDir, bmadDir, this.installerConfig.targets, options); - } - - // Handle single-target installations - if (this.installerConfig.target_dir) { - return this.installToTarget(projectDir, bmadDir, this.installerConfig, options); - } - - return { success: false, reason: 'invalid-config' }; - } - - /** - * Install to a single target directory - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {Object} config - Installation configuration - * @param {Object} options - Setup options - * @returns {Promise} Installation result - */ - async installToTarget(projectDir, bmadDir, config, options) { - const { target_dir, template_type, artifact_types } = config; - - // Skip targets with explicitly empty artifact_types array - // This prevents creating empty directories when no artifacts will be written - if (Array.isArray(artifact_types) && artifact_types.length === 0) { - return { success: true, results: { agents: 0, workflows: 0, tasks: 0, tools: 0 } }; - } - - const targetPath = path.join(projectDir, target_dir); - await this.ensureDir(targetPath); - - const selectedModules = options.selectedModules || []; - const results = { agents: 0, workflows: 0, tasks: 0, tools: 0 }; - - // Install agents - if (!artifact_types || artifact_types.includes('agents')) { - const agentGen = new AgentCommandGenerator(this.bmadFolderName); - const { artifacts } = await agentGen.collectAgentArtifacts(bmadDir, selectedModules); - results.agents = await this.writeAgentArtifacts(targetPath, artifacts, template_type, config); - } - - // Install workflows - if (!artifact_types || artifact_types.includes('workflows')) { - const workflowGen = new WorkflowCommandGenerator(this.bmadFolderName); - const { artifacts } = await workflowGen.collectWorkflowArtifacts(bmadDir); - results.workflows = await this.writeWorkflowArtifacts(targetPath, artifacts, template_type, config); - } - - // Install tasks and tools using template system (supports TOML for Gemini, MD for others) - if (!artifact_types || artifact_types.includes('tasks') || artifact_types.includes('tools')) { - const taskToolGen = new TaskToolCommandGenerator(this.bmadFolderName); - const { artifacts } = await taskToolGen.collectTaskToolArtifacts(bmadDir); - const taskToolResult = await this.writeTaskToolArtifacts(targetPath, artifacts, template_type, config); - results.tasks = taskToolResult.tasks || 0; - results.tools = taskToolResult.tools || 0; - } - - await this.printSummary(results, target_dir, options); - return { success: true, results }; - } - - /** - * Install to multiple target directories - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {Array} targets - Array of target configurations - * @param {Object} options - Setup options - * @returns {Promise} Installation result - */ - async installToMultipleTargets(projectDir, bmadDir, targets, options) { - const allResults = { agents: 0, workflows: 0, tasks: 0, tools: 0 }; - - for (const target of targets) { - const result = await this.installToTarget(projectDir, bmadDir, target, options); - if (result.success) { - allResults.agents += result.results.agents || 0; - allResults.workflows += result.results.workflows || 0; - allResults.tasks += result.results.tasks || 0; - allResults.tools += result.results.tools || 0; - } - } - - return { success: true, results: allResults }; - } - - /** - * Write agent artifacts to target directory - * @param {string} targetPath - Target directory path - * @param {Array} artifacts - Agent artifacts - * @param {string} templateType - Template type to use - * @param {Object} config - Installation configuration - * @returns {Promise} Count of artifacts written - */ - async writeAgentArtifacts(targetPath, artifacts, templateType, config = {}) { - // Try to load platform-specific template, fall back to default-agent - const { content: template, extension } = await this.loadTemplate(templateType, 'agent', config, 'default-agent'); - let count = 0; - - for (const artifact of artifacts) { - const content = this.renderTemplate(template, artifact); - const filename = this.generateFilename(artifact, 'agent', extension); - const filePath = path.join(targetPath, filename); - await this.writeFile(filePath, content); - count++; - } - - return count; - } - - /** - * Write workflow artifacts to target directory - * @param {string} targetPath - Target directory path - * @param {Array} artifacts - Workflow artifacts - * @param {string} templateType - Template type to use - * @param {Object} config - Installation configuration - * @returns {Promise} Count of artifacts written - */ - async writeWorkflowArtifacts(targetPath, artifacts, templateType, config = {}) { - let count = 0; - - for (const artifact of artifacts) { - if (artifact.type === 'workflow-command') { - // Use different template based on workflow type (YAML vs MD) - // Default to 'default' template type, but allow override via config - const workflowTemplateType = artifact.isYamlWorkflow - ? config.yaml_workflow_template || `${templateType}-workflow-yaml` - : config.md_workflow_template || `${templateType}-workflow`; - - // Fall back to default templates if specific ones don't exist - const finalTemplateType = artifact.isYamlWorkflow ? 'default-workflow-yaml' : 'default-workflow'; - // workflowTemplateType already contains full name (e.g., 'gemini-workflow-yaml'), so pass empty artifactType - const { content: template, extension } = await this.loadTemplate(workflowTemplateType, '', config, finalTemplateType); - const content = this.renderTemplate(template, artifact); - const filename = this.generateFilename(artifact, 'workflow', extension); - const filePath = path.join(targetPath, filename); - await this.writeFile(filePath, content); - count++; - } - } - - return count; - } - - /** - * Write task/tool artifacts to target directory using templates - * @param {string} targetPath - Target directory path - * @param {Array} artifacts - Task/tool artifacts - * @param {string} templateType - Template type to use - * @param {Object} config - Installation configuration - * @returns {Promise} Counts of tasks and tools written - */ - async writeTaskToolArtifacts(targetPath, artifacts, templateType, config = {}) { - let taskCount = 0; - let toolCount = 0; - - // Pre-load templates to avoid repeated file I/O in the loop - const taskTemplate = await this.loadTemplate(templateType, 'task', config, 'default-task'); - const toolTemplate = await this.loadTemplate(templateType, 'tool', config, 'default-tool'); - - const { artifact_types } = config; - - for (const artifact of artifacts) { - if (artifact.type !== 'task' && artifact.type !== 'tool') { - continue; - } - - // Skip if the specific artifact type is not requested in config - if (artifact_types) { - if (artifact.type === 'task' && !artifact_types.includes('tasks')) continue; - if (artifact.type === 'tool' && !artifact_types.includes('tools')) continue; - } - - // Use pre-loaded template based on artifact type - const { content: template, extension } = artifact.type === 'task' ? taskTemplate : toolTemplate; - - const content = this.renderTemplate(template, artifact); - const filename = this.generateFilename(artifact, artifact.type, extension); - const filePath = path.join(targetPath, filename); - await this.writeFile(filePath, content); - - if (artifact.type === 'task') { - taskCount++; - } else { - toolCount++; - } - } - - return { tasks: taskCount, tools: toolCount }; - } - - /** - * Load template based on type and configuration - * @param {string} templateType - Template type (claude, windsurf, etc.) - * @param {string} artifactType - Artifact type (agent, workflow, task, tool) - * @param {Object} config - Installation configuration - * @param {string} fallbackTemplateType - Fallback template type if requested template not found - * @returns {Promise<{content: string, extension: string}>} Template content and extension - */ - async loadTemplate(templateType, artifactType, config = {}, fallbackTemplateType = null) { - const { header_template, body_template } = config; - - // Check for separate header/body templates - if (header_template || body_template) { - const content = await this.loadSplitTemplates(templateType, artifactType, header_template, body_template); - // Allow config to override extension, default to .md - const ext = config.extension || '.md'; - const normalizedExt = ext.startsWith('.') ? ext : `.${ext}`; - return { content, extension: normalizedExt }; - } - - // Load combined template - try multiple extensions - // If artifactType is empty, templateType already contains full name (e.g., 'gemini-workflow-yaml') - const templateBaseName = artifactType ? `${templateType}-${artifactType}` : templateType; - const templateDir = path.join(__dirname, 'templates', 'combined'); - const extensions = ['.md', '.toml', '.yaml', '.yml']; - - for (const ext of extensions) { - const templatePath = path.join(templateDir, templateBaseName + ext); - if (await fs.pathExists(templatePath)) { - const content = await fs.readFile(templatePath, 'utf8'); - return { content, extension: ext }; - } - } - - // Fall back to default template (if provided) - if (fallbackTemplateType) { - for (const ext of extensions) { - const fallbackPath = path.join(templateDir, `${fallbackTemplateType}${ext}`); - if (await fs.pathExists(fallbackPath)) { - const content = await fs.readFile(fallbackPath, 'utf8'); - return { content, extension: ext }; - } - } - } - - // Ultimate fallback - minimal template - return { content: this.getDefaultTemplate(artifactType), extension: '.md' }; - } - - /** - * Load split templates (header + body) - * @param {string} templateType - Template type - * @param {string} artifactType - Artifact type - * @param {string} headerTpl - Header template name - * @param {string} bodyTpl - Body template name - * @returns {Promise} Combined template content - */ - async loadSplitTemplates(templateType, artifactType, headerTpl, bodyTpl) { - let header = ''; - let body = ''; - - // Load header template - if (headerTpl) { - const headerPath = path.join(__dirname, 'templates', 'split', headerTpl); - if (await fs.pathExists(headerPath)) { - header = await fs.readFile(headerPath, 'utf8'); - } - } else { - // Use default header for template type - const defaultHeaderPath = path.join(__dirname, 'templates', 'split', templateType, 'header.md'); - if (await fs.pathExists(defaultHeaderPath)) { - header = await fs.readFile(defaultHeaderPath, 'utf8'); - } - } - - // Load body template - if (bodyTpl) { - const bodyPath = path.join(__dirname, 'templates', 'split', bodyTpl); - if (await fs.pathExists(bodyPath)) { - body = await fs.readFile(bodyPath, 'utf8'); - } - } else { - // Use default body for template type - const defaultBodyPath = path.join(__dirname, 'templates', 'split', templateType, 'body.md'); - if (await fs.pathExists(defaultBodyPath)) { - body = await fs.readFile(defaultBodyPath, 'utf8'); - } - } - - // Combine header and body - return `${header}\n${body}`; - } - - /** - * Get default minimal template - * @param {string} artifactType - Artifact type - * @returns {string} Default template - */ - getDefaultTemplate(artifactType) { - if (artifactType === 'agent') { - return `--- -name: '{{name}}' -description: '{{description}}' -disable-model-invocation: true ---- - -You must fully embody this agent's persona and follow all activation instructions exactly as specified. - - -1. LOAD the FULL agent file from {project-root}/{{bmadFolderName}}/{{path}} -2. READ its entire contents - this contains the complete agent persona, menu, and instructions -3. FOLLOW every step in the section precisely - -`; - } - return `--- -name: '{{name}}' -description: '{{description}}' ---- - -# {{name}} - -LOAD and execute from: {project-root}/{{bmadFolderName}}/{{path}} -`; - } - - /** - * Render template with artifact data - * @param {string} template - Template content - * @param {Object} artifact - Artifact data - * @returns {string} Rendered content - */ - renderTemplate(template, artifact) { - // Use the appropriate path property based on artifact type - let pathToUse = artifact.relativePath || ''; - switch (artifact.type) { - case 'agent-launcher': { - pathToUse = artifact.agentPath || artifact.relativePath || ''; - - break; - } - case 'workflow-command': { - pathToUse = artifact.workflowPath || artifact.relativePath || ''; - - break; - } - case 'task': - case 'tool': { - pathToUse = artifact.path || artifact.relativePath || ''; - - break; - } - // No default - } - - let rendered = template - .replaceAll('{{name}}', artifact.name || '') - .replaceAll('{{module}}', artifact.module || 'core') - .replaceAll('{{path}}', pathToUse) - .replaceAll('{{description}}', artifact.description || `${artifact.name} ${artifact.type || ''}`) - .replaceAll('{{workflow_path}}', pathToUse); - - // Replace _bmad placeholder with actual folder name - rendered = rendered.replaceAll('_bmad', this.bmadFolderName); - - // Replace {{bmadFolderName}} placeholder if present - rendered = rendered.replaceAll('{{bmadFolderName}}', this.bmadFolderName); - - return rendered; - } - - /** - * Generate filename for artifact - * @param {Object} artifact - Artifact data - * @param {string} artifactType - Artifact type (agent, workflow, task, tool) - * @param {string} extension - File extension to use (e.g., '.md', '.toml') - * @returns {string} Generated filename - */ - generateFilename(artifact, artifactType, extension = '.md') { - const { toDashPath } = require('./shared/path-utils'); - - // Reuse central logic to ensure consistent naming conventions - const standardName = toDashPath(artifact.relativePath); - - // Clean up potential double extensions from source files (e.g. .yaml.md, .xml.md -> .md) - // This handles any extensions that might slip through toDashPath() - const baseName = standardName.replace(/\.(md|yaml|yml|json|xml|toml)\.md$/i, '.md'); - - // If using default markdown, preserve the bmad-agent- prefix for agents - if (extension === '.md') { - return baseName; - } - - // For other extensions (e.g., .toml), replace .md extension - // Note: agent prefix is preserved even with non-markdown extensions - return baseName.replace(/\.md$/, extension); - } - - /** - * Print installation summary - * @param {Object} results - Installation results - * @param {string} targetDir - Target directory (relative) - */ - async printSummary(results, targetDir, options = {}) { - if (options.silent) return; - const parts = []; - if (results.agents > 0) parts.push(`${results.agents} agents`); - if (results.workflows > 0) parts.push(`${results.workflows} workflows`); - if (results.tasks > 0) parts.push(`${results.tasks} tasks`); - if (results.tools > 0) parts.push(`${results.tools} tools`); - await prompts.log.success(`${this.name} configured: ${parts.join(', ')} → ${targetDir}`); - } - - /** - * Cleanup IDE configuration - * @param {string} projectDir - Project directory - */ - async cleanup(projectDir, options = {}) { - // Migrate legacy target directories (e.g. .opencode/agent → .opencode/agents) - if (this.installerConfig?.legacy_targets) { - if (!options.silent) await prompts.log.message(' Migrating legacy directories...'); - for (const legacyDir of this.installerConfig.legacy_targets) { - await this.cleanupTarget(projectDir, legacyDir, options); - await this.removeEmptyParents(projectDir, legacyDir); - } - } - - // Clean all target directories - if (this.installerConfig?.targets) { - const parentDirs = new Set(); - for (const target of this.installerConfig.targets) { - await this.cleanupTarget(projectDir, target.target_dir, options); - // Track parent directories for empty-dir cleanup - const parentDir = path.dirname(target.target_dir); - if (parentDir && parentDir !== '.') { - parentDirs.add(parentDir); - } - } - // After all targets cleaned, remove empty parent directories (recursive up to projectDir) - for (const parentDir of parentDirs) { - await this.removeEmptyParents(projectDir, parentDir); - } - } else if (this.installerConfig?.target_dir) { - await this.cleanupTarget(projectDir, this.installerConfig.target_dir, options); - } - } - - /** - * Cleanup a specific target directory - * @param {string} projectDir - Project directory - * @param {string} targetDir - Target directory to clean - */ - async cleanupTarget(projectDir, targetDir, options = {}) { - const targetPath = path.join(projectDir, targetDir); - - if (!(await fs.pathExists(targetPath))) { - return; - } - - // Remove all bmad* files - let entries; - try { - entries = await fs.readdir(targetPath); - } catch { - // Directory exists but can't be read - skip cleanup - return; - } - - if (!entries || !Array.isArray(entries)) { - return; - } - - let removedCount = 0; - - for (const entry of entries) { - if (!entry || typeof entry !== 'string') { - continue; - } - if (entry.startsWith('bmad')) { - const entryPath = path.join(targetPath, entry); - try { - await fs.remove(entryPath); - removedCount++; - } catch { - // Skip entries that can't be removed (broken symlinks, permission errors) - } - } - } - - if (removedCount > 0 && !options.silent) { - await prompts.log.message(` Cleaned ${removedCount} BMAD files from ${targetDir}`); - } - - // Remove empty directory after cleanup - if (removedCount > 0) { - try { - const remaining = await fs.readdir(targetPath); - if (remaining.length === 0) { - await fs.remove(targetPath); - } - } catch { - // Directory may already be gone or in use — skip - } - } - } - /** - * Check ancestor directories for existing BMAD files in the same target_dir. - * IDEs like Claude Code inherit commands from parent directories, so an existing - * installation in an ancestor would cause duplicate commands. - * @param {string} projectDir - Project directory being installed to - * @returns {Promise} Path to conflicting directory, or null if clean - */ - async findAncestorConflict(projectDir) { - const targetDir = this.installerConfig?.target_dir; - if (!targetDir) return null; - - const resolvedProject = await fs.realpath(path.resolve(projectDir)); - let current = path.dirname(resolvedProject); - const root = path.parse(current).root; - - while (current !== root && current.length > root.length) { - const candidatePath = path.join(current, targetDir); - try { - if (await fs.pathExists(candidatePath)) { - const entries = await fs.readdir(candidatePath); - const hasBmad = entries.some((e) => typeof e === 'string' && e.toLowerCase().startsWith('bmad')); - if (hasBmad) { - return candidatePath; - } - } - } catch { - // Can't read directory — skip - } - current = path.dirname(current); - } - - return null; - } - - /** - * Walk up ancestor directories from relativeDir toward projectDir, removing each if empty - * Stops at projectDir boundary — never removes projectDir itself - * @param {string} projectDir - Project root (boundary) - * @param {string} relativeDir - Relative directory to start from - */ - async removeEmptyParents(projectDir, relativeDir) { - const resolvedProject = path.resolve(projectDir); - let current = relativeDir; - let last = null; - while (current && current !== '.' && current !== last) { - last = current; - const fullPath = path.resolve(projectDir, current); - // Boundary guard: never traverse outside projectDir - if (!fullPath.startsWith(resolvedProject + path.sep) && fullPath !== resolvedProject) break; - try { - if (!(await fs.pathExists(fullPath))) { - // Dir already gone — advance current; last is reset at top of next iteration - current = path.dirname(current); - continue; - } - const remaining = await fs.readdir(fullPath); - if (remaining.length > 0) break; - await fs.rmdir(fullPath); - } catch (error) { - // ENOTEMPTY: TOCTOU race (file added between readdir and rmdir) — skip level, continue upward - // ENOENT: dir removed by another process between pathExists and rmdir — skip level, continue upward - if (error.code === 'ENOTEMPTY' || error.code === 'ENOENT') { - current = path.dirname(current); - continue; - } - break; // fatal error (e.g. EACCES) — stop upward walk - } - current = path.dirname(current); - } - } -} - -module.exports = { ConfigDrivenIdeSetup }; diff --git a/tools/cli/installers/lib/ide/codex.js b/tools/cli/installers/lib/ide/codex.js deleted file mode 100644 index abee979fd..000000000 --- a/tools/cli/installers/lib/ide/codex.js +++ /dev/null @@ -1,440 +0,0 @@ -const path = require('node:path'); -const os = require('node:os'); -const fs = require('fs-extra'); -const yaml = require('yaml'); -const { BaseIdeSetup } = require('./_base-ide'); -const { WorkflowCommandGenerator } = require('./shared/workflow-command-generator'); -const { AgentCommandGenerator } = require('./shared/agent-command-generator'); -const { TaskToolCommandGenerator } = require('./shared/task-tool-command-generator'); -const { getTasksFromBmad } = require('./shared/bmad-artifacts'); -const { toDashPath, customAgentDashName } = require('./shared/path-utils'); -const prompts = require('../../../lib/prompts'); - -/** - * Codex setup handler (CLI mode) - */ -class CodexSetup extends BaseIdeSetup { - constructor() { - super('codex', 'Codex', false); - } - - /** - * Setup Codex configuration - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {Object} options - Setup options - */ - async setup(projectDir, bmadDir, options = {}) { - if (!options.silent) await prompts.log.info(`Setting up ${this.name}...`); - - // Always use CLI mode - const mode = 'cli'; - - const { artifacts, counts } = await this.collectClaudeArtifacts(projectDir, bmadDir, options); - - // Clean up old .codex/prompts locations (both global and project) - const oldGlobalDir = this.getOldCodexPromptDir(null, 'global'); - await this.clearOldBmadFiles(oldGlobalDir, options); - const oldProjectDir = this.getOldCodexPromptDir(projectDir, 'project'); - await this.clearOldBmadFiles(oldProjectDir, options); - - // Install to .agents/skills - const destDir = this.getCodexSkillsDir(projectDir); - await fs.ensureDir(destDir); - await this.clearOldBmadSkills(destDir, options); - - // Collect and write agent skills - const agentGen = new AgentCommandGenerator(this.bmadFolderName); - const { artifacts: agentArtifacts } = await agentGen.collectAgentArtifacts(bmadDir, options.selectedModules || []); - const agentCount = await this.writeSkillArtifacts(destDir, agentArtifacts, 'agent-launcher'); - - // Collect and write task skills - const tasks = await getTasksFromBmad(bmadDir, options.selectedModules || []); - const taskArtifacts = []; - for (const task of tasks) { - const content = await this.readAndProcessWithProject( - task.path, - { - module: task.module, - name: task.name, - }, - projectDir, - ); - taskArtifacts.push({ - type: 'task', - name: task.name, - displayName: task.name, - module: task.module, - path: task.path, - sourcePath: task.path, - relativePath: path.join(task.module, 'tasks', `${task.name}.md`), - content, - }); - } - - const ttGen = new TaskToolCommandGenerator(this.bmadFolderName); - const taskSkillArtifacts = taskArtifacts.map((artifact) => ({ - ...artifact, - content: ttGen.generateCommandContent(artifact, artifact.type), - })); - const tasksWritten = await this.writeSkillArtifacts(destDir, taskSkillArtifacts, 'task'); - - // Collect and write workflow skills - const workflowGenerator = new WorkflowCommandGenerator(this.bmadFolderName); - const { artifacts: workflowArtifacts } = await workflowGenerator.collectWorkflowArtifacts(bmadDir); - const workflowCount = await this.writeSkillArtifacts(destDir, workflowArtifacts, 'workflow-command'); - - const written = agentCount + workflowCount + tasksWritten; - - if (!options.silent) { - await prompts.log.success( - `${this.name} configured: ${counts.agents} agents, ${counts.workflows} workflows, ${counts.tasks} tasks, ${written} skills → ${destDir}`, - ); - } - - return { - success: true, - mode, - artifacts, - counts, - destination: destDir, - written, - }; - } - - /** - * Detect Codex installation by checking for BMAD skills - */ - async detect(projectDir) { - const dir = this.getCodexSkillsDir(projectDir || process.cwd()); - - if (await fs.pathExists(dir)) { - try { - const entries = await fs.readdir(dir); - if (entries && entries.some((entry) => entry && typeof entry === 'string' && entry.startsWith('bmad'))) { - return true; - } - } catch { - // Ignore errors - } - } - - return false; - } - - /** - * Collect Claude-style artifacts for Codex export. - * Returns the normalized artifact list for further processing. - */ - async collectClaudeArtifacts(projectDir, bmadDir, options = {}) { - const selectedModules = options.selectedModules || []; - const artifacts = []; - - // Generate agent launchers - const agentGen = new AgentCommandGenerator(this.bmadFolderName); - const { artifacts: agentArtifacts } = await agentGen.collectAgentArtifacts(bmadDir, selectedModules); - - for (const artifact of agentArtifacts) { - artifacts.push({ - type: 'agent', - module: artifact.module, - sourcePath: artifact.sourcePath, - relativePath: artifact.relativePath, - content: artifact.content, - }); - } - - const tasks = await getTasksFromBmad(bmadDir, selectedModules); - for (const task of tasks) { - const content = await this.readAndProcessWithProject( - task.path, - { - module: task.module, - name: task.name, - }, - projectDir, - ); - - artifacts.push({ - type: 'task', - name: task.name, - displayName: task.name, - module: task.module, - path: task.path, - sourcePath: task.path, - relativePath: path.join(task.module, 'tasks', `${task.name}.md`), - content, - }); - } - - const workflowGenerator = new WorkflowCommandGenerator(this.bmadFolderName); - const { artifacts: workflowArtifacts, counts: workflowCounts } = await workflowGenerator.collectWorkflowArtifacts(bmadDir); - artifacts.push(...workflowArtifacts); - - return { - artifacts, - counts: { - agents: agentArtifacts.length, - tasks: tasks.length, - workflows: workflowCounts.commands, - workflowLaunchers: workflowCounts.launchers, - }, - }; - } - - getCodexSkillsDir(projectDir) { - if (!projectDir) { - throw new Error('projectDir is required for project-scoped skill installation'); - } - return path.join(projectDir, '.agents', 'skills'); - } - - /** - * Get the old .codex/prompts directory for cleanup purposes - */ - getOldCodexPromptDir(projectDir = null, location = 'global') { - if (location === 'project' && projectDir) { - return path.join(projectDir, '.codex', 'prompts'); - } - return path.join(os.homedir(), '.codex', 'prompts'); - } - - /** - * Write artifacts as Agent Skills (agentskills.io format). - * Each artifact becomes a directory containing SKILL.md. - * @param {string} destDir - Base skills directory - * @param {Array} artifacts - Artifacts to write - * @param {string} artifactType - Type filter (e.g., 'agent-launcher', 'workflow-command', 'task') - * @returns {number} Number of skills written - */ - async writeSkillArtifacts(destDir, artifacts, artifactType) { - let writtenCount = 0; - - for (const artifact of artifacts) { - // Filter by type if the artifact has a type field - if (artifact.type && artifact.type !== artifactType) { - continue; - } - - // Get the dash-format name (e.g., bmad-bmm-create-prd.md) and remove .md - const flatName = toDashPath(artifact.relativePath); - const skillName = flatName.replace(/\.md$/, ''); - - // Create skill directory - const skillDir = path.join(destDir, skillName); - await fs.ensureDir(skillDir); - - // Transform content: rewrite frontmatter for skills format - const skillContent = this.transformToSkillFormat(artifact.content, skillName); - - // Write SKILL.md with platform-native line endings - const platformContent = skillContent.replaceAll('\n', os.EOL); - await fs.writeFile(path.join(skillDir, 'SKILL.md'), platformContent, 'utf8'); - writtenCount++; - } - - return writtenCount; - } - - /** - * Transform artifact content from Codex prompt format to Agent Skills format. - * Removes disable-model-invocation, ensures name matches directory. - * @param {string} content - Original content with YAML frontmatter - * @param {string} skillName - Skill name (must match directory name) - * @returns {string} Transformed content - */ - transformToSkillFormat(content, skillName) { - // Normalize line endings so body matches rebuilt frontmatter (both LF) - content = content.replaceAll('\r\n', '\n').replaceAll('\r', '\n'); - - // Parse frontmatter - const fmMatch = content.match(/^---\r?\n([\s\S]*?)\r?\n---\r?\n?([\s\S]*)$/); - if (!fmMatch) { - // No frontmatter -- wrap with minimal frontmatter - const fm = yaml.stringify({ name: skillName, description: skillName }).trimEnd(); - return `---\n${fm}\n---\n\n${content}`; - } - - const frontmatter = fmMatch[1]; - const body = fmMatch[2]; - - // Parse frontmatter with yaml library to handle all quoting variants - let description; - try { - const parsed = yaml.parse(frontmatter); - description = parsed?.description || `${skillName} skill`; - } catch { - description = `${skillName} skill`; - } - - // Build new frontmatter with only skills-spec fields, let yaml handle quoting - const newFrontmatter = yaml.stringify({ name: skillName, description }, { lineWidth: 0 }).trimEnd(); - return `---\n${newFrontmatter}\n---\n${body}`; - } - - /** - * Remove existing BMAD skill directories from the skills directory. - */ - async clearOldBmadSkills(destDir, options = {}) { - if (!(await fs.pathExists(destDir))) { - return; - } - - let entries; - try { - entries = await fs.readdir(destDir); - } catch (error) { - if (!options.silent) await prompts.log.warn(`Warning: Could not read directory ${destDir}: ${error.message}`); - return; - } - - if (!entries || !Array.isArray(entries)) { - return; - } - - for (const entry of entries) { - if (!entry || typeof entry !== 'string') { - continue; - } - if (!entry.startsWith('bmad')) { - continue; - } - - const entryPath = path.join(destDir, entry); - try { - await fs.remove(entryPath); - } catch (error) { - if (!options.silent) { - await prompts.log.message(` Skipping ${entry}: ${error.message}`); - } - } - } - } - - /** - * Clean old BMAD files from legacy .codex/prompts directories. - */ - async clearOldBmadFiles(destDir, options = {}) { - if (!(await fs.pathExists(destDir))) { - return; - } - - let entries; - try { - entries = await fs.readdir(destDir); - } catch (error) { - // Directory exists but can't be read - skip cleanup - if (!options.silent) await prompts.log.warn(`Warning: Could not read directory ${destDir}: ${error.message}`); - return; - } - - if (!entries || !Array.isArray(entries)) { - return; - } - - for (const entry of entries) { - // Skip non-strings or undefined entries - if (!entry || typeof entry !== 'string') { - continue; - } - if (!entry.startsWith('bmad')) { - continue; - } - - const entryPath = path.join(destDir, entry); - try { - await fs.remove(entryPath); - } catch (error) { - if (!options.silent) { - await prompts.log.message(` Skipping ${entry}: ${error.message}`); - } - } - } - } - - async readAndProcessWithProject(filePath, metadata, projectDir) { - const rawContent = await fs.readFile(filePath, 'utf8'); - const content = rawContent.replaceAll('\r\n', '\n').replaceAll('\r', '\n'); - return super.processContent(content, metadata, projectDir); - } - - /** - * Get instructions for project-specific installation - * @param {string} projectDir - Optional project directory - * @param {string} destDir - Optional destination directory - * @returns {string} Instructions text - */ - getProjectSpecificInstructions(projectDir = null, destDir = null) { - const lines = [ - 'Project-Specific Codex Configuration', - '', - `Skills installed to: ${destDir || '/.agents/skills'}`, - '', - 'Codex automatically discovers skills in .agents/skills/ at and above the current directory and in your home directory.', - 'No additional configuration is needed.', - ]; - - return lines.join('\n'); - } - - /** - * Cleanup Codex configuration - cleans both new .agents/skills and old .codex/prompts - */ - async cleanup(projectDir = null) { - // Clean old .codex/prompts locations - const oldGlobalDir = this.getOldCodexPromptDir(null, 'global'); - await this.clearOldBmadFiles(oldGlobalDir); - - if (projectDir) { - const oldProjectDir = this.getOldCodexPromptDir(projectDir, 'project'); - await this.clearOldBmadFiles(oldProjectDir); - - // Clean new .agents/skills location - const destDir = this.getCodexSkillsDir(projectDir); - await this.clearOldBmadSkills(destDir); - } - } - - /** - * Install a custom agent launcher for Codex as an Agent Skill - * @param {string} projectDir - Project directory - * @param {string} agentName - Agent name (e.g., "fred-commit-poet") - * @param {string} agentPath - Path to compiled agent (relative to project root) - * @param {Object} metadata - Agent metadata - * @returns {Object|null} Info about created skill - */ - async installCustomAgentLauncher(projectDir, agentName, agentPath, metadata) { - const destDir = this.getCodexSkillsDir(projectDir); - - // Skill name from the dash name (without .md) - const skillName = customAgentDashName(agentName).replace(/\.md$/, ''); - const skillDir = path.join(destDir, skillName); - await fs.ensureDir(skillDir); - - const description = metadata?.description || `${agentName} agent`; - const fm = yaml.stringify({ name: skillName, description }).trimEnd(); - const skillContent = - `---\n${fm}\n---\n` + - "\nYou must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.\n" + - '\n\n' + - `1. LOAD the FULL agent file from @${agentPath}\n` + - '2. READ its entire contents - this contains the complete agent persona, menu, and instructions\n' + - '3. FOLLOW every step in the section precisely\n' + - '4. DISPLAY the welcome/greeting as instructed\n' + - '5. PRESENT the numbered menu\n' + - '6. WAIT for user input before proceeding\n' + - '\n'; - - // Write with platform-native line endings - const platformContent = skillContent.replaceAll('\n', os.EOL); - const skillPath = path.join(skillDir, 'SKILL.md'); - await fs.writeFile(skillPath, platformContent, 'utf8'); - - return { - path: path.relative(projectDir, skillPath), - command: `$${skillName}`, - }; - } -} - -module.exports = { CodexSetup }; diff --git a/tools/cli/installers/lib/ide/github-copilot.js b/tools/cli/installers/lib/ide/github-copilot.js deleted file mode 100644 index 059127f81..000000000 --- a/tools/cli/installers/lib/ide/github-copilot.js +++ /dev/null @@ -1,699 +0,0 @@ -const path = require('node:path'); -const { BaseIdeSetup } = require('./_base-ide'); -const prompts = require('../../../lib/prompts'); -const { AgentCommandGenerator } = require('./shared/agent-command-generator'); -const { BMAD_FOLDER_NAME, toDashPath } = require('./shared/path-utils'); -const fs = require('fs-extra'); -const csv = require('csv-parse/sync'); -const yaml = require('yaml'); - -/** - * GitHub Copilot setup handler - * Creates agents in .github/agents/, prompts in .github/prompts/, - * copilot-instructions.md, and configures VS Code settings - */ -class GitHubCopilotSetup extends BaseIdeSetup { - constructor() { - super('github-copilot', 'GitHub Copilot', false); - // Don't set configDir to '.github' — nearly every GitHub repo has that directory, - // which would cause the base detect() to false-positive. Use detectionPaths instead. - this.configDir = null; - this.githubDir = '.github'; - this.agentsDir = 'agents'; - this.promptsDir = 'prompts'; - this.detectionPaths = ['.github/copilot-instructions.md', '.github/agents']; - } - - /** - * Setup GitHub Copilot configuration - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {Object} options - Setup options - */ - async setup(projectDir, bmadDir, options = {}) { - if (!options.silent) await prompts.log.info(`Setting up ${this.name}...`); - - // Create .github/agents and .github/prompts directories - const githubDir = path.join(projectDir, this.githubDir); - const agentsDir = path.join(githubDir, this.agentsDir); - const promptsDir = path.join(githubDir, this.promptsDir); - await this.ensureDir(agentsDir); - await this.ensureDir(promptsDir); - - // Preserve any customised tool permissions from existing files before cleanup - this.existingToolPermissions = await this.collectExistingToolPermissions(projectDir); - - // Clean up any existing BMAD files before reinstalling - await this.cleanup(projectDir); - - // Load agent manifest for enriched descriptions - const agentManifest = await this.loadAgentManifest(bmadDir); - - // Generate agent launchers - const agentGen = new AgentCommandGenerator(this.bmadFolderName); - const { artifacts: agentArtifacts } = await agentGen.collectAgentArtifacts(bmadDir, options.selectedModules || []); - - // Create agent .agent.md files - let agentCount = 0; - for (const artifact of agentArtifacts) { - const agentMeta = agentManifest.get(artifact.name); - - // Compute fileName first so we can look up any existing tool permissions - const dashName = toDashPath(artifact.relativePath); - const fileName = dashName.replace(/\.md$/, '.agent.md'); - const toolsStr = this.getToolsForFile(fileName); - const agentContent = this.createAgentContent(artifact, agentMeta, toolsStr); - const targetPath = path.join(agentsDir, fileName); - await this.writeFile(targetPath, agentContent); - agentCount++; - } - - // Generate prompt files from bmad-help.csv - const promptCount = await this.generatePromptFiles(projectDir, bmadDir, agentArtifacts, agentManifest); - - // Generate copilot-instructions.md - await this.generateCopilotInstructions(projectDir, bmadDir, agentManifest, options); - - if (!options.silent) await prompts.log.success(`${this.name} configured: ${agentCount} agents, ${promptCount} prompts → .github/`); - - return { - success: true, - results: { - agents: agentCount, - workflows: promptCount, - tasks: 0, - tools: 0, - }, - }; - } - - /** - * Load agent manifest CSV into a Map keyed by agent name - * @param {string} bmadDir - BMAD installation directory - * @returns {Map} Agent metadata keyed by name - */ - async loadAgentManifest(bmadDir) { - const manifestPath = path.join(bmadDir, '_config', 'agent-manifest.csv'); - const agents = new Map(); - - if (!(await fs.pathExists(manifestPath))) { - return agents; - } - - try { - const csvContent = await fs.readFile(manifestPath, 'utf8'); - const records = csv.parse(csvContent, { - columns: true, - skip_empty_lines: true, - }); - - for (const record of records) { - agents.set(record.name, record); - } - } catch { - // Gracefully degrade if manifest is unreadable/malformed - } - - return agents; - } - - /** - * Load bmad-help.csv to drive prompt generation - * @param {string} bmadDir - BMAD installation directory - * @returns {Array|null} Parsed CSV rows - */ - async loadBmadHelp(bmadDir) { - const helpPath = path.join(bmadDir, '_config', 'bmad-help.csv'); - - if (!(await fs.pathExists(helpPath))) { - return null; - } - - try { - const csvContent = await fs.readFile(helpPath, 'utf8'); - return csv.parse(csvContent, { - columns: true, - skip_empty_lines: true, - }); - } catch { - // Gracefully degrade if help CSV is unreadable/malformed - return null; - } - } - - /** - * Create agent .agent.md content with enriched description - * @param {Object} artifact - Agent artifact from AgentCommandGenerator - * @param {Object|undefined} manifestEntry - Agent manifest entry with metadata - * @returns {string} Agent file content - */ - createAgentContent(artifact, manifestEntry, toolsStr) { - // Build enriched description from manifest metadata - let description; - if (manifestEntry) { - const persona = manifestEntry.displayName || artifact.name; - const title = manifestEntry.title || this.formatTitle(artifact.name); - const capabilities = manifestEntry.capabilities || 'agent capabilities'; - description = `${persona} — ${title}: ${capabilities}`; - } else { - description = `Activates the ${this.formatTitle(artifact.name)} agent persona.`; - } - - // Build the agent file path for the activation block - const agentPath = artifact.agentPath || artifact.relativePath; - const agentFilePath = `{project-root}/${this.bmadFolderName}/${agentPath}`; - - return `--- -description: '${description.replaceAll("'", "''")}' -tools: ${toolsStr} ---- - -You must fully embody this agent's persona and follow all activation instructions exactly as specified. - - -1. LOAD the FULL agent file from ${agentFilePath} -2. READ its entire contents - this contains the complete agent persona, menu, and instructions -3. FOLLOW every step in the section precisely -4. DISPLAY the welcome/greeting as instructed -5. PRESENT the numbered menu -6. WAIT for user input before proceeding - -`; - } - - /** - * Generate .prompt.md files for workflows, tasks, tech-writer commands, and agent activators - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {Array} agentArtifacts - Agent artifacts for activator generation - * @param {Map} agentManifest - Agent manifest data - * @returns {number} Count of prompts generated - */ - async generatePromptFiles(projectDir, bmadDir, agentArtifacts, agentManifest) { - const promptsDir = path.join(projectDir, this.githubDir, this.promptsDir); - let promptCount = 0; - - // Load bmad-help.csv to drive workflow/task prompt generation - const helpEntries = await this.loadBmadHelp(bmadDir); - - if (helpEntries) { - for (const entry of helpEntries) { - const command = entry.command; - if (!command) continue; // Skip entries without a command (tech-writer commands have no command column) - - const workflowFile = entry['workflow-file']; - if (!workflowFile) continue; // Skip entries with no workflow file path - const promptFileName = `${command}.prompt.md`; - const toolsStr = this.getToolsForFile(promptFileName); - const promptContent = this.createWorkflowPromptContent(entry, workflowFile, toolsStr); - const promptPath = path.join(promptsDir, promptFileName); - await this.writeFile(promptPath, promptContent); - promptCount++; - } - - // Generate tech-writer command prompts (entries with no command column) - for (const entry of helpEntries) { - if (entry.command) continue; // Already handled above - const techWriterPrompt = this.createTechWriterPromptContent(entry); - if (techWriterPrompt) { - const promptFileName = `${techWriterPrompt.fileName}.prompt.md`; - const promptPath = path.join(promptsDir, promptFileName); - await this.writeFile(promptPath, techWriterPrompt.content); - promptCount++; - } - } - } - - // Generate agent activator prompts (Pattern D) - for (const artifact of agentArtifacts) { - const agentMeta = agentManifest.get(artifact.name); - const fileName = `bmad-${artifact.name}.prompt.md`; - const toolsStr = this.getToolsForFile(fileName); - const promptContent = this.createAgentActivatorPromptContent(artifact, agentMeta, toolsStr); - const promptPath = path.join(promptsDir, fileName); - await this.writeFile(promptPath, promptContent); - promptCount++; - } - - return promptCount; - } - - /** - * Create prompt content for a workflow/task entry from bmad-help.csv - * Determines the pattern (A, B, or A for .xml tasks) based on file extension - * @param {Object} entry - bmad-help.csv row - * @param {string} workflowFile - Workflow file path - * @returns {string} Prompt file content - */ - createWorkflowPromptContent(entry, workflowFile, toolsStr) { - const description = this.escapeYamlSingleQuote(this.createPromptDescription(entry.name)); - // bmm/config.yaml is safe to hardcode here: these prompts are only generated when - // bmad-help.csv exists (bmm module data), so bmm is guaranteed to be installed. - const configLine = `1. Load {project-root}/${this.bmadFolderName}/bmm/config.yaml and store ALL fields as session variables`; - - let body; - if (workflowFile.endsWith('.yaml')) { - // Pattern B: YAML-based workflows — use workflow engine - body = `${configLine} -2. Load the workflow engine at {project-root}/${this.bmadFolderName}/core/tasks/workflow.xml -3. Load and execute the workflow configuration at {project-root}/${workflowFile} using the engine from step 2`; - } else if (workflowFile.endsWith('.xml')) { - // Pattern A variant: XML tasks — load and execute directly - body = `${configLine} -2. Load and execute the task at {project-root}/${workflowFile}`; - } else { - // Pattern A: MD workflows — load and follow directly - body = `${configLine} -2. Load and follow the workflow at {project-root}/${workflowFile}`; - } - - return `--- -description: '${description}' -agent: 'agent' -tools: ${toolsStr} ---- - -${body} -`; - } - - /** - * Create a short 2-5 word description for a prompt from the entry name - * @param {string} name - Entry name from bmad-help.csv - * @returns {string} Short description - */ - createPromptDescription(name) { - const descriptionMap = { - 'Brainstorm Project': 'Brainstorm ideas', - 'Market Research': 'Market research', - 'Domain Research': 'Domain research', - 'Technical Research': 'Technical research', - 'Create Brief': 'Create product brief', - 'Create PRD': 'Create PRD', - 'Validate PRD': 'Validate PRD', - 'Edit PRD': 'Edit PRD', - 'Create UX': 'Create UX design', - 'Create Architecture': 'Create architecture', - 'Create Epics and Stories': 'Create epics and stories', - 'Check Implementation Readiness': 'Check implementation readiness', - 'Sprint Planning': 'Sprint planning', - 'Sprint Status': 'Sprint status', - 'Create Story': 'Create story', - 'Validate Story': 'Validate story', - 'Dev Story': 'Dev story', - 'QA Automation Test': 'QA automation', - 'Code Review': 'Code review', - Retrospective: 'Retrospective', - 'Document Project': 'Document project', - 'Generate Project Context': 'Generate project context', - 'Quick Spec': 'Quick spec', - 'Quick Dev': 'Quick dev', - 'Correct Course': 'Correct course', - Brainstorming: 'Brainstorm ideas', - 'Party Mode': 'Party mode', - 'bmad-help': 'BMAD help', - 'Index Docs': 'Index documents', - 'Shard Document': 'Shard document', - 'Editorial Review - Prose': 'Editorial review prose', - 'Editorial Review - Structure': 'Editorial review structure', - 'Adversarial Review (General)': 'Adversarial review', - }; - - return descriptionMap[name] || name; - } - - /** - * Create prompt content for tech-writer agent-only commands (Pattern C) - * @param {Object} entry - bmad-help.csv row - * @returns {Object|null} { fileName, content } or null if not a tech-writer command - */ - createTechWriterPromptContent(entry) { - if (entry['agent-name'] !== 'tech-writer') return null; - - const techWriterCommands = { - 'Write Document': { code: 'WD', file: 'bmad-bmm-write-document', description: 'Write document' }, - 'Update Standards': { code: 'US', file: 'bmad-bmm-update-standards', description: 'Update standards' }, - 'Mermaid Generate': { code: 'MG', file: 'bmad-bmm-mermaid-generate', description: 'Mermaid generate' }, - 'Validate Document': { code: 'VD', file: 'bmad-bmm-validate-document', description: 'Validate document' }, - 'Explain Concept': { code: 'EC', file: 'bmad-bmm-explain-concept', description: 'Explain concept' }, - }; - - const cmd = techWriterCommands[entry.name]; - if (!cmd) return null; - - const safeDescription = this.escapeYamlSingleQuote(cmd.description); - const toolsStr = this.getToolsForFile(`${cmd.file}.prompt.md`); - - const content = `--- -description: '${safeDescription}' -agent: 'agent' -tools: ${toolsStr} ---- - -1. Load {project-root}/${this.bmadFolderName}/bmm/config.yaml and store ALL fields as session variables -2. Load the full agent file from {project-root}/${this.bmadFolderName}/bmm/agents/tech-writer/tech-writer.md and activate the Paige (Technical Writer) persona -3. Execute the ${entry.name} menu command (${cmd.code}) -`; - - return { fileName: cmd.file, content }; - } - - /** - * Create agent activator prompt content (Pattern D) - * @param {Object} artifact - Agent artifact - * @param {Object|undefined} manifestEntry - Agent manifest entry - * @returns {string} Prompt file content - */ - createAgentActivatorPromptContent(artifact, manifestEntry, toolsStr) { - let description; - if (manifestEntry) { - description = manifestEntry.title || this.formatTitle(artifact.name); - } else { - description = this.formatTitle(artifact.name); - } - - const safeDescription = this.escapeYamlSingleQuote(description); - const agentPath = artifact.agentPath || artifact.relativePath; - const agentFilePath = `{project-root}/${this.bmadFolderName}/${agentPath}`; - - // bmm/config.yaml is safe to hardcode: agent activators are only generated from - // bmm agent artifacts, so bmm is guaranteed to be installed. - return `--- -description: '${safeDescription}' -agent: 'agent' -tools: ${toolsStr} ---- - -1. Load {project-root}/${this.bmadFolderName}/bmm/config.yaml and store ALL fields as session variables -2. Load the full agent file from ${agentFilePath} -3. Follow ALL activation instructions in the agent file -4. Display the welcome/greeting as instructed -5. Present the numbered menu -6. Wait for user input before proceeding -`; - } - - /** - * Generate copilot-instructions.md from module config - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {Map} agentManifest - Agent manifest data - */ - async generateCopilotInstructions(projectDir, bmadDir, agentManifest, options = {}) { - const configVars = await this.loadModuleConfig(bmadDir); - - // Build the agents table from the manifest - let agentsTable = '| Agent | Persona | Title | Capabilities |\n|---|---|---|---|\n'; - const agentOrder = [ - 'bmad-master', - 'analyst', - 'architect', - 'dev', - 'pm', - 'qa', - 'quick-flow-solo-dev', - 'sm', - 'tech-writer', - 'ux-designer', - ]; - - for (const agentName of agentOrder) { - const meta = agentManifest.get(agentName); - if (meta) { - const capabilities = meta.capabilities || 'agent capabilities'; - const cleanTitle = (meta.title || '').replaceAll('""', '"'); - agentsTable += `| ${agentName} | ${meta.displayName} | ${cleanTitle} | ${capabilities} |\n`; - } - } - - const bmad = this.bmadFolderName; - const bmadSection = `# BMAD Method — Project Instructions - -## Project Configuration - -- **Project**: ${configVars.project_name || '{{project_name}}'} -- **User**: ${configVars.user_name || '{{user_name}}'} -- **Communication Language**: ${configVars.communication_language || '{{communication_language}}'} -- **Document Output Language**: ${configVars.document_output_language || '{{document_output_language}}'} -- **User Skill Level**: ${configVars.user_skill_level || '{{user_skill_level}}'} -- **Output Folder**: ${configVars.output_folder || '{{output_folder}}'} -- **Planning Artifacts**: ${configVars.planning_artifacts || '{{planning_artifacts}}'} -- **Implementation Artifacts**: ${configVars.implementation_artifacts || '{{implementation_artifacts}}'} -- **Project Knowledge**: ${configVars.project_knowledge || '{{project_knowledge}}'} - -## BMAD Runtime Structure - -- **Agent definitions**: \`${bmad}/bmm/agents/\` (BMM module) and \`${bmad}/core/agents/\` (core) -- **Workflow definitions**: \`${bmad}/bmm/workflows/\` (organized by phase) -- **Core tasks**: \`${bmad}/core/tasks/\` (help, editorial review, indexing, sharding, adversarial review) -- **Core workflows**: \`${bmad}/core/workflows/\` (brainstorming, party-mode, advanced-elicitation) -- **Workflow engine**: \`${bmad}/core/tasks/workflow.xml\` (executes YAML-based workflows) -- **Module configuration**: \`${bmad}/bmm/config.yaml\` -- **Core configuration**: \`${bmad}/core/config.yaml\` -- **Agent manifest**: \`${bmad}/_config/agent-manifest.csv\` -- **Workflow manifest**: \`${bmad}/_config/workflow-manifest.csv\` -- **Help manifest**: \`${bmad}/_config/bmad-help.csv\` -- **Agent memory**: \`${bmad}/_memory/\` - -## Key Conventions - -- Always load \`${bmad}/bmm/config.yaml\` before any agent activation or workflow execution -- Store all config fields as session variables: \`{user_name}\`, \`{communication_language}\`, \`{output_folder}\`, \`{planning_artifacts}\`, \`{implementation_artifacts}\`, \`{project_knowledge}\` -- MD-based workflows execute directly — load and follow the \`.md\` file -- YAML-based workflows require the workflow engine — load \`workflow.xml\` first, then pass the \`.yaml\` config -- Follow step-based workflow execution: load steps JIT, never multiple at once -- Save outputs after EACH step when using the workflow engine -- The \`{project-root}\` variable resolves to the workspace root at runtime - -## Available Agents - -${agentsTable} -## Slash Commands - -Type \`/bmad-\` in Copilot Chat to see all available BMAD workflows and agent activators. Agents are also available in the agents dropdown.`; - - const instructionsPath = path.join(projectDir, this.githubDir, 'copilot-instructions.md'); - const markerStart = ''; - const markerEnd = ''; - const markedContent = `${markerStart}\n${bmadSection}\n${markerEnd}`; - - if (await fs.pathExists(instructionsPath)) { - const existing = await fs.readFile(instructionsPath, 'utf8'); - const startIdx = existing.indexOf(markerStart); - const endIdx = existing.indexOf(markerEnd); - - if (startIdx !== -1 && endIdx !== -1 && endIdx > startIdx) { - // Replace only the BMAD section between markers - const before = existing.slice(0, startIdx); - const after = existing.slice(endIdx + markerEnd.length); - const merged = `${before}${markedContent}${after}`; - await this.writeFile(instructionsPath, merged); - } else { - // Existing file without markers — back it up before overwriting - const backupPath = `${instructionsPath}.bak`; - await fs.copy(instructionsPath, backupPath); - if (!options.silent) await prompts.log.warn(` Backed up copilot-instructions.md → .bak`); - await this.writeFile(instructionsPath, `${markedContent}\n`); - } - } else { - // No existing file — create fresh with markers - await this.writeFile(instructionsPath, `${markedContent}\n`); - } - } - - /** - * Load module config.yaml for template variables - * @param {string} bmadDir - BMAD installation directory - * @returns {Object} Config variables - */ - async loadModuleConfig(bmadDir) { - const bmmConfigPath = path.join(bmadDir, 'bmm', 'config.yaml'); - const coreConfigPath = path.join(bmadDir, 'core', 'config.yaml'); - - for (const configPath of [bmmConfigPath, coreConfigPath]) { - if (await fs.pathExists(configPath)) { - try { - const content = await fs.readFile(configPath, 'utf8'); - return yaml.parse(content) || {}; - } catch { - // Fall through to next config - } - } - } - - return {}; - } - - /** - * Escape a string for use inside YAML single-quoted values. - * In YAML, the only escape inside single quotes is '' for a literal '. - * @param {string} value - Raw string - * @returns {string} Escaped string safe for YAML single-quoted context - */ - escapeYamlSingleQuote(value) { - return (value || '').replaceAll("'", "''"); - } - - /** - * Scan existing agent and prompt files for customised tool permissions before cleanup. - * Returns a Map so permissions can be preserved across reinstalls. - * @param {string} projectDir - Project directory - * @returns {Map} Existing tool permissions keyed by filename - */ - async collectExistingToolPermissions(projectDir) { - const permissions = new Map(); - const dirs = [ - [path.join(projectDir, this.githubDir, this.agentsDir), /^bmad.*\.agent\.md$/], - [path.join(projectDir, this.githubDir, this.promptsDir), /^bmad-.*\.prompt\.md$/], - ]; - - for (const [dir, pattern] of dirs) { - if (!(await fs.pathExists(dir))) continue; - const files = await fs.readdir(dir); - - for (const file of files) { - if (!pattern.test(file)) continue; - - try { - const content = await fs.readFile(path.join(dir, file), 'utf8'); - const fmMatch = content.match(/^---\n([\s\S]*?)\n---/); - if (!fmMatch) continue; - - const frontmatter = yaml.parse(fmMatch[1]); - if (frontmatter && Array.isArray(frontmatter.tools)) { - permissions.set(file, frontmatter.tools); - } - } catch { - // Skip unreadable files - } - } - } - - return permissions; - } - - /** - * Get the tools array string for a file, preserving any existing customisation. - * Falls back to the default tools if no prior customisation exists. - * @param {string} fileName - Target filename (e.g. 'bmad-agent-bmm-pm.agent.md') - * @returns {string} YAML inline array string - */ - getToolsForFile(fileName) { - const defaultTools = ['read', 'edit', 'search', 'execute']; - const tools = (this.existingToolPermissions && this.existingToolPermissions.get(fileName)) || defaultTools; - return '[' + tools.map((t) => `'${t}'`).join(', ') + ']'; - } - - /** - * Format name as title - */ - formatTitle(name) { - return name - .split('-') - .map((word) => word.charAt(0).toUpperCase() + word.slice(1)) - .join(' '); - } - - /** - * Cleanup GitHub Copilot configuration - surgically remove only BMAD files - */ - async cleanup(projectDir, options = {}) { - // Clean up agents directory - const agentsDir = path.join(projectDir, this.githubDir, this.agentsDir); - if (await fs.pathExists(agentsDir)) { - const files = await fs.readdir(agentsDir); - let removed = 0; - - for (const file of files) { - if (file.startsWith('bmad') && (file.endsWith('.agent.md') || file.endsWith('.md'))) { - await fs.remove(path.join(agentsDir, file)); - removed++; - } - } - - if (removed > 0 && !options.silent) { - await prompts.log.message(` Cleaned up ${removed} existing BMAD agents`); - } - } - - // Clean up prompts directory - const promptsDir = path.join(projectDir, this.githubDir, this.promptsDir); - if (await fs.pathExists(promptsDir)) { - const files = await fs.readdir(promptsDir); - let removed = 0; - - for (const file of files) { - if (file.startsWith('bmad-') && file.endsWith('.prompt.md')) { - await fs.remove(path.join(promptsDir, file)); - removed++; - } - } - - if (removed > 0 && !options.silent) { - await prompts.log.message(` Cleaned up ${removed} existing BMAD prompts`); - } - } - - // During uninstall, also strip BMAD markers from copilot-instructions.md. - // During reinstall (default), this is skipped because generateCopilotInstructions() - // handles marker-based replacement in a single read-modify-write pass, - // which correctly preserves user content outside the markers. - if (options.isUninstall) { - await this.cleanupCopilotInstructions(projectDir, options); - } - } - - /** - * Strip BMAD marker section from copilot-instructions.md - * If file becomes empty after stripping, delete it. - * If a .bak backup exists and the main file was deleted, restore the backup. - * @param {string} projectDir - Project directory - * @param {Object} [options] - Options (e.g. { silent: true }) - */ - async cleanupCopilotInstructions(projectDir, options = {}) { - const instructionsPath = path.join(projectDir, this.githubDir, 'copilot-instructions.md'); - const backupPath = `${instructionsPath}.bak`; - - if (!(await fs.pathExists(instructionsPath))) { - return; - } - - const content = await fs.readFile(instructionsPath, 'utf8'); - const markerStart = ''; - const markerEnd = ''; - const startIdx = content.indexOf(markerStart); - const endIdx = content.indexOf(markerEnd); - - if (startIdx === -1 || endIdx === -1 || endIdx <= startIdx) { - return; // No valid markers found - } - - // Strip the marker section (including markers) - const before = content.slice(0, startIdx); - const after = content.slice(endIdx + markerEnd.length); - const cleaned = before + after; - - if (cleaned.trim().length === 0) { - // File is empty after stripping — delete it - await fs.remove(instructionsPath); - - // If backup exists, restore it - if (await fs.pathExists(backupPath)) { - await fs.rename(backupPath, instructionsPath); - if (!options.silent) { - await prompts.log.message(' Restored copilot-instructions.md from backup'); - } - } - } else { - // Write cleaned content back (preserve original whitespace) - await fs.writeFile(instructionsPath, cleaned, 'utf8'); - - // If backup exists, it's stale now — remove it - if (await fs.pathExists(backupPath)) { - await fs.remove(backupPath); - } - } - } -} - -module.exports = { GitHubCopilotSetup }; diff --git a/tools/cli/installers/lib/ide/kilo.js b/tools/cli/installers/lib/ide/kilo.js deleted file mode 100644 index 2e5734391..000000000 --- a/tools/cli/installers/lib/ide/kilo.js +++ /dev/null @@ -1,269 +0,0 @@ -const path = require('node:path'); -const { BaseIdeSetup } = require('./_base-ide'); -const yaml = require('yaml'); -const prompts = require('../../../lib/prompts'); -const { AgentCommandGenerator } = require('./shared/agent-command-generator'); -const { WorkflowCommandGenerator } = require('./shared/workflow-command-generator'); -const { TaskToolCommandGenerator } = require('./shared/task-tool-command-generator'); - -/** - * KiloCode IDE setup handler - * Creates custom modes in .kilocodemodes file (similar to Roo) - */ -class KiloSetup extends BaseIdeSetup { - constructor() { - super('kilo', 'Kilo Code'); - this.configFile = '.kilocodemodes'; - } - - /** - * Setup KiloCode IDE configuration - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {Object} options - Setup options - */ - async setup(projectDir, bmadDir, options = {}) { - if (!options.silent) await prompts.log.info(`Setting up ${this.name}...`); - - // Clean up any old BMAD installation first - await this.cleanup(projectDir, options); - - // Load existing config (may contain non-BMAD modes and other settings) - const kiloModesPath = path.join(projectDir, this.configFile); - let config = {}; - - if (await this.pathExists(kiloModesPath)) { - const existingContent = await this.readFile(kiloModesPath); - try { - config = yaml.parse(existingContent) || {}; - } catch { - // If parsing fails, start fresh but warn user - await prompts.log.warn('Warning: Could not parse existing .kilocodemodes, starting fresh'); - config = {}; - } - } - - // Ensure customModes array exists - if (!Array.isArray(config.customModes)) { - config.customModes = []; - } - - // Generate agent launchers - const agentGen = new AgentCommandGenerator(this.bmadFolderName); - const { artifacts: agentArtifacts } = await agentGen.collectAgentArtifacts(bmadDir, options.selectedModules || []); - - // Create mode objects and add to config - let addedCount = 0; - - for (const artifact of agentArtifacts) { - const modeObject = await this.createModeObject(artifact, projectDir); - config.customModes.push(modeObject); - addedCount++; - } - - // Write .kilocodemodes file with proper YAML structure - const finalContent = yaml.stringify(config, { lineWidth: 0 }); - await this.writeFile(kiloModesPath, finalContent); - - // Generate workflow commands - const workflowGenerator = new WorkflowCommandGenerator(this.bmadFolderName); - const { artifacts: workflowArtifacts } = await workflowGenerator.collectWorkflowArtifacts(bmadDir); - - // Write to .kilocode/workflows/ directory - const workflowsDir = path.join(projectDir, '.kilocode', 'workflows'); - await this.ensureDir(workflowsDir); - - // Clear old BMAD workflows before writing new ones - await this.clearBmadWorkflows(workflowsDir); - - // Write workflow files - const workflowCount = await workflowGenerator.writeDashArtifacts(workflowsDir, workflowArtifacts); - - // Generate task and tool commands - const taskToolGen = new TaskToolCommandGenerator(this.bmadFolderName); - const { artifacts: taskToolArtifacts, counts: taskToolCounts } = await taskToolGen.collectTaskToolArtifacts(bmadDir); - - // Write task/tool files to workflows directory (same location as workflows) - await taskToolGen.writeDashArtifacts(workflowsDir, taskToolArtifacts); - const taskCount = taskToolCounts.tasks || 0; - const toolCount = taskToolCounts.tools || 0; - - if (!options.silent) { - await prompts.log.success( - `${this.name} configured: ${addedCount} modes, ${workflowCount} workflows, ${taskCount} tasks, ${toolCount} tools → ${this.configFile}`, - ); - } - - return { - success: true, - modes: addedCount, - workflows: workflowCount, - tasks: taskCount, - tools: toolCount, - }; - } - - /** - * Create a mode object for an agent - * @param {Object} artifact - Agent artifact - * @param {string} projectDir - Project directory - * @returns {Object} Mode object for YAML serialization - */ - async createModeObject(artifact, projectDir) { - // Extract metadata from launcher content - const titleMatch = artifact.content.match(/title="([^"]+)"/); - const title = titleMatch ? titleMatch[1] : this.formatTitle(artifact.name); - - const iconMatch = artifact.content.match(/icon="([^"]+)"/); - const icon = iconMatch ? iconMatch[1] : '🤖'; - - const whenToUseMatch = artifact.content.match(/whenToUse="([^"]+)"/); - const whenToUse = whenToUseMatch ? whenToUseMatch[1] : `Use for ${title} tasks`; - - // Get the activation header from central template (trim to avoid YAML formatting issues) - const activationHeader = (await this.getAgentCommandHeader()).trim(); - - const roleDefinitionMatch = artifact.content.match(/roleDefinition="([^"]+)"/); - const roleDefinition = roleDefinitionMatch - ? roleDefinitionMatch[1] - : `You are a ${title} specializing in ${title.toLowerCase()} tasks.`; - - // Get relative path - const relativePath = path.relative(projectDir, artifact.sourcePath).replaceAll('\\', '/'); - - // Build mode object (KiloCode uses same schema as Roo) - return { - slug: `bmad-${artifact.module}-${artifact.name}`, - name: `${icon} ${title}`, - roleDefinition: roleDefinition, - whenToUse: whenToUse, - customInstructions: `${activationHeader} Read the full YAML from ${relativePath} start activation to alter your state of being follow startup section instructions stay in this being until told to exit this mode\n`, - groups: ['read', 'edit', 'browser', 'command', 'mcp'], - }; - } - - /** - * Format name as title - */ - formatTitle(name) { - return name - .split('-') - .map((word) => word.charAt(0).toUpperCase() + word.slice(1)) - .join(' '); - } - - /** - * Clear old BMAD workflow files from workflows directory - * @param {string} workflowsDir - Workflows directory path - */ - async clearBmadWorkflows(workflowsDir) { - const fs = require('fs-extra'); - if (!(await fs.pathExists(workflowsDir))) return; - - const entries = await fs.readdir(workflowsDir); - for (const entry of entries) { - if (entry.startsWith('bmad-') && entry.endsWith('.md')) { - await fs.remove(path.join(workflowsDir, entry)); - } - } - } - - /** - * Cleanup KiloCode configuration - */ - async cleanup(projectDir, options = {}) { - const fs = require('fs-extra'); - const kiloModesPath = path.join(projectDir, this.configFile); - - if (await fs.pathExists(kiloModesPath)) { - const content = await fs.readFile(kiloModesPath, 'utf8'); - - try { - const config = yaml.parse(content) || {}; - - if (Array.isArray(config.customModes)) { - const originalCount = config.customModes.length; - // Remove BMAD modes only (keep non-BMAD modes) - config.customModes = config.customModes.filter((mode) => !mode.slug || !mode.slug.startsWith('bmad-')); - const removedCount = originalCount - config.customModes.length; - - if (removedCount > 0) { - await fs.writeFile(kiloModesPath, yaml.stringify(config, { lineWidth: 0 })); - if (!options.silent) await prompts.log.message(`Removed ${removedCount} BMAD modes from .kilocodemodes`); - } - } - } catch { - // If parsing fails, leave file as-is - if (!options.silent) await prompts.log.warn('Warning: Could not parse .kilocodemodes for cleanup'); - } - } - - // Clean up workflow files - const workflowsDir = path.join(projectDir, '.kilocode', 'workflows'); - await this.clearBmadWorkflows(workflowsDir); - } - - /** - * Install a custom agent launcher for Kilo - * @param {string} projectDir - Project directory - * @param {string} agentName - Agent name (e.g., "fred-commit-poet") - * @param {string} agentPath - Path to compiled agent (relative to project root) - * @param {Object} metadata - Agent metadata - * @returns {Object} Installation result - */ - async installCustomAgentLauncher(projectDir, agentName, agentPath, metadata) { - const kilocodemodesPath = path.join(projectDir, this.configFile); - let config = {}; - - // Read existing .kilocodemodes file - if (await this.pathExists(kilocodemodesPath)) { - const existingContent = await this.readFile(kilocodemodesPath); - try { - config = yaml.parse(existingContent) || {}; - } catch { - config = {}; - } - } - - // Ensure customModes array exists - if (!Array.isArray(config.customModes)) { - config.customModes = []; - } - - // Create custom agent mode object - const slug = `bmad-custom-${agentName.toLowerCase()}`; - - // Check if mode already exists - if (config.customModes.some((mode) => mode.slug === slug)) { - return { - ide: 'kilo', - path: this.configFile, - command: agentName, - type: 'custom-agent-launcher', - alreadyExists: true, - }; - } - - // Add custom mode object - config.customModes.push({ - slug: slug, - name: `BMAD Custom: ${agentName}`, - description: `Custom BMAD agent: ${agentName}\n\n**⚠️ IMPORTANT**: Run @${agentPath} first to load the complete agent!\n\nThis is a launcher for the custom BMAD agent "${agentName}". The agent will follow the persona and instructions from the main agent file.\n`, - prompt: `@${agentPath}\n`, - always: false, - permissions: 'all', - }); - - // Write .kilocodemodes file with proper YAML structure - await this.writeFile(kilocodemodesPath, yaml.stringify(config, { lineWidth: 0 })); - - return { - ide: 'kilo', - path: this.configFile, - command: slug, - type: 'custom-agent-launcher', - }; - } -} - -module.exports = { KiloSetup }; diff --git a/tools/cli/installers/lib/ide/manager.js b/tools/cli/installers/lib/ide/manager.js deleted file mode 100644 index 9e286fdd3..000000000 --- a/tools/cli/installers/lib/ide/manager.js +++ /dev/null @@ -1,342 +0,0 @@ -const fs = require('fs-extra'); -const path = require('node:path'); -const { BMAD_FOLDER_NAME } = require('./shared/path-utils'); -const prompts = require('../../../lib/prompts'); - -/** - * IDE Manager - handles IDE-specific setup - * Dynamically discovers and loads IDE handlers - * - * Loading strategy: - * 1. Custom installer files (codex.js, github-copilot.js, kilo.js, rovodev.js) - for platforms with unique installation logic - * 2. Config-driven handlers (from platform-codes.yaml) - for standard IDE installation patterns - */ -class IdeManager { - constructor() { - this.handlers = new Map(); - this._initialized = false; - this.bmadFolderName = BMAD_FOLDER_NAME; // Default, can be overridden - } - - /** - * Set the bmad folder name for all IDE handlers - * @param {string} bmadFolderName - The bmad folder name - */ - setBmadFolderName(bmadFolderName) { - this.bmadFolderName = bmadFolderName; - // Update all loaded handlers - for (const handler of this.handlers.values()) { - if (typeof handler.setBmadFolderName === 'function') { - handler.setBmadFolderName(bmadFolderName); - } - } - } - - /** - * Ensure handlers are loaded (lazy loading) - */ - async ensureInitialized() { - if (!this._initialized) { - await this.loadHandlers(); - this._initialized = true; - } - } - - /** - * Dynamically load all IDE handlers - * 1. Load custom installer files first (codex.js, github-copilot.js, kilo.js, rovodev.js) - * 2. Load config-driven handlers from platform-codes.yaml - */ - async loadHandlers() { - // Load custom installer files - await this.loadCustomInstallerFiles(); - - // Load config-driven handlers from platform-codes.yaml - await this.loadConfigDrivenHandlers(); - } - - /** - * Load custom installer files (unique installation logic) - * These files have special installation patterns that don't fit the config-driven model - */ - async loadCustomInstallerFiles() { - const ideDir = __dirname; - const customFiles = ['codex.js', 'github-copilot.js', 'kilo.js', 'rovodev.js']; - - for (const file of customFiles) { - const filePath = path.join(ideDir, file); - if (!fs.existsSync(filePath)) continue; - - try { - const HandlerModule = require(filePath); - const HandlerClass = HandlerModule.default || Object.values(HandlerModule)[0]; - - if (HandlerClass) { - const instance = new HandlerClass(); - if (instance.name && typeof instance.name === 'string') { - if (typeof instance.setBmadFolderName === 'function') { - instance.setBmadFolderName(this.bmadFolderName); - } - this.handlers.set(instance.name, instance); - } - } - } catch (error) { - await prompts.log.warn(`Warning: Could not load ${file}: ${error.message}`); - } - } - } - - /** - * Load config-driven handlers from platform-codes.yaml - * This creates ConfigDrivenIdeSetup instances for platforms with installer config - */ - async loadConfigDrivenHandlers() { - const { loadPlatformCodes } = require('./platform-codes'); - const platformConfig = await loadPlatformCodes(); - - const { ConfigDrivenIdeSetup } = require('./_config-driven'); - - for (const [platformCode, platformInfo] of Object.entries(platformConfig.platforms)) { - // Skip if already loaded by custom installer - if (this.handlers.has(platformCode)) continue; - - // Skip if no installer config (platform may not need installation) - if (!platformInfo.installer) continue; - - const handler = new ConfigDrivenIdeSetup(platformCode, platformInfo); - if (typeof handler.setBmadFolderName === 'function') { - handler.setBmadFolderName(this.bmadFolderName); - } - this.handlers.set(platformCode, handler); - } - } - - /** - * Get all available IDEs with their metadata - * @returns {Array} Array of IDE information objects - */ - getAvailableIdes() { - const ides = []; - - for (const [key, handler] of this.handlers) { - // Skip handlers without valid names - const name = handler.displayName || handler.name || key; - - // Filter out invalid entries (undefined name, empty key, etc.) - if (!key || !name || typeof key !== 'string' || typeof name !== 'string') { - continue; - } - - ides.push({ - value: key, - name: name, - preferred: handler.preferred || false, - }); - } - - // Sort: preferred first, then alphabetical - ides.sort((a, b) => { - if (a.preferred && !b.preferred) return -1; - if (!a.preferred && b.preferred) return 1; - return a.name.localeCompare(b.name); - }); - - return ides; - } - - /** - * Get preferred IDEs - * @returns {Array} Array of preferred IDE information - */ - getPreferredIdes() { - return this.getAvailableIdes().filter((ide) => ide.preferred); - } - - /** - * Get non-preferred IDEs - * @returns {Array} Array of non-preferred IDE information - */ - getOtherIdes() { - return this.getAvailableIdes().filter((ide) => !ide.preferred); - } - - /** - * Setup IDE configuration - * @param {string} ideName - Name of the IDE - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {Object} options - Setup options - */ - async setup(ideName, projectDir, bmadDir, options = {}) { - const handler = this.handlers.get(ideName.toLowerCase()); - - if (!handler) { - await prompts.log.warn(`IDE '${ideName}' is not yet supported`); - await prompts.log.message(`Supported IDEs: ${[...this.handlers.keys()].join(', ')}`); - return { success: false, ide: ideName, error: 'unsupported IDE' }; - } - - try { - const handlerResult = await handler.setup(projectDir, bmadDir, options); - // Build detail string from handler-returned data - let detail = ''; - if (handlerResult && handlerResult.results) { - // Config-driven handlers return { success, results: { agents, workflows, tasks, tools } } - const r = handlerResult.results; - const parts = []; - if (r.agents > 0) parts.push(`${r.agents} agents`); - if (r.workflows > 0) parts.push(`${r.workflows} workflows`); - if (r.tasks > 0) parts.push(`${r.tasks} tasks`); - if (r.tools > 0) parts.push(`${r.tools} tools`); - detail = parts.join(', '); - } else if (handlerResult && handlerResult.counts) { - // Codex handler returns { success, counts: { agents, workflows, tasks }, written } - const c = handlerResult.counts; - const parts = []; - if (c.agents > 0) parts.push(`${c.agents} agents`); - if (c.workflows > 0) parts.push(`${c.workflows} workflows`); - if (c.tasks > 0) parts.push(`${c.tasks} tasks`); - detail = parts.join(', '); - } else if (handlerResult && handlerResult.modes !== undefined) { - // Kilo handler returns { success, modes, workflows, tasks, tools } - const parts = []; - if (handlerResult.modes > 0) parts.push(`${handlerResult.modes} modes`); - if (handlerResult.workflows > 0) parts.push(`${handlerResult.workflows} workflows`); - if (handlerResult.tasks > 0) parts.push(`${handlerResult.tasks} tasks`); - if (handlerResult.tools > 0) parts.push(`${handlerResult.tools} tools`); - detail = parts.join(', '); - } - // Propagate handler's success status (default true for backward compat) - const success = handlerResult?.success !== false; - return { success, ide: ideName, detail, error: handlerResult?.error, handlerResult }; - } catch (error) { - await prompts.log.error(`Failed to setup ${ideName}: ${error.message}`); - return { success: false, ide: ideName, error: error.message }; - } - } - - /** - * Cleanup IDE configurations - * @param {string} projectDir - Project directory - * @param {Object} [options] - Cleanup options passed through to handlers - */ - async cleanup(projectDir, options = {}) { - const results = []; - - for (const [name, handler] of this.handlers) { - try { - await handler.cleanup(projectDir, options); - results.push({ ide: name, success: true }); - } catch (error) { - results.push({ ide: name, success: false, error: error.message }); - } - } - - return results; - } - - /** - * Cleanup only the IDEs in the provided list - * Falls back to cleanup() (all handlers) if ideList is empty or undefined - * @param {string} projectDir - Project directory - * @param {Array} ideList - List of IDE names to clean up - * @param {Object} [options] - Cleanup options passed through to handlers - * @returns {Array} Results array - */ - async cleanupByList(projectDir, ideList, options = {}) { - if (!ideList || ideList.length === 0) { - return this.cleanup(projectDir, options); - } - - await this.ensureInitialized(); - const results = []; - - // Build lowercase lookup for case-insensitive matching - const lowercaseHandlers = new Map([...this.handlers.entries()].map(([k, v]) => [k.toLowerCase(), v])); - - for (const ideName of ideList) { - const handler = lowercaseHandlers.get(ideName.toLowerCase()); - if (!handler) continue; - - try { - await handler.cleanup(projectDir, options); - results.push({ ide: ideName, success: true }); - } catch (error) { - results.push({ ide: ideName, success: false, error: error.message }); - } - } - - return results; - } - - /** - * Get list of supported IDEs - * @returns {Array} List of supported IDE names - */ - getSupportedIdes() { - return [...this.handlers.keys()]; - } - - /** - * Check if an IDE is supported - * @param {string} ideName - Name of the IDE - * @returns {boolean} True if IDE is supported - */ - isSupported(ideName) { - return this.handlers.has(ideName.toLowerCase()); - } - - /** - * Detect installed IDEs - * @param {string} projectDir - Project directory - * @returns {Array} List of detected IDEs - */ - async detectInstalledIdes(projectDir) { - const detected = []; - - for (const [name, handler] of this.handlers) { - if (typeof handler.detect === 'function' && (await handler.detect(projectDir))) { - detected.push(name); - } - } - - return detected; - } - - /** - * Install custom agent launchers for specified IDEs - * @param {Array} ides - List of IDE names to install for - * @param {string} projectDir - Project directory - * @param {string} agentName - Agent name (e.g., "fred-commit-poet") - * @param {string} agentPath - Path to compiled agent (relative to project root) - * @param {Object} metadata - Agent metadata - * @returns {Object} Results for each IDE - */ - async installCustomAgentLaunchers(ides, projectDir, agentName, agentPath, metadata) { - const results = {}; - - for (const ideName of ides) { - const handler = this.handlers.get(ideName.toLowerCase()); - - if (!handler) { - await prompts.log.warn(`IDE '${ideName}' is not yet supported for custom agent installation`); - continue; - } - - try { - if (typeof handler.installCustomAgentLauncher === 'function') { - const result = await handler.installCustomAgentLauncher(projectDir, agentName, agentPath, metadata); - if (result) { - results[ideName] = result; - } - } - } catch (error) { - await prompts.log.warn(`Failed to install ${ideName} launcher: ${error.message}`); - } - } - - return results; - } -} - -module.exports = { IdeManager }; diff --git a/tools/cli/installers/lib/ide/platform-codes.js b/tools/cli/installers/lib/ide/platform-codes.js deleted file mode 100644 index d5d8e0a47..000000000 --- a/tools/cli/installers/lib/ide/platform-codes.js +++ /dev/null @@ -1,100 +0,0 @@ -const fs = require('fs-extra'); -const path = require('node:path'); -const yaml = require('yaml'); - -const PLATFORM_CODES_PATH = path.join(__dirname, 'platform-codes.yaml'); - -let _cachedPlatformCodes = null; - -/** - * Load the platform codes configuration from YAML - * @returns {Object} Platform codes configuration - */ -async function loadPlatformCodes() { - if (_cachedPlatformCodes) { - return _cachedPlatformCodes; - } - - if (!(await fs.pathExists(PLATFORM_CODES_PATH))) { - throw new Error(`Platform codes configuration not found at: ${PLATFORM_CODES_PATH}`); - } - - const content = await fs.readFile(PLATFORM_CODES_PATH, 'utf8'); - _cachedPlatformCodes = yaml.parse(content); - return _cachedPlatformCodes; -} - -/** - * Get platform information by code - * @param {string} platformCode - Platform code (e.g., 'claude-code', 'cursor') - * @returns {Object|null} Platform info or null if not found - */ -function getPlatformInfo(platformCode) { - if (!_cachedPlatformCodes) { - throw new Error('Platform codes not loaded. Call loadPlatformCodes() first.'); - } - - return _cachedPlatformCodes.platforms[platformCode] || null; -} - -/** - * Get all preferred platforms - * @returns {Promise} Array of preferred platform codes - */ -async function getPreferredPlatforms() { - const config = await loadPlatformCodes(); - return Object.entries(config.platforms) - .filter(([_, info]) => info.preferred) - .map(([code, _]) => code); -} - -/** - * Get all platform codes by category - * @param {string} category - Category to filter by (ide, cli, tool, etc.) - * @returns {Promise} Array of platform codes in the category - */ -async function getPlatformsByCategory(category) { - const config = await loadPlatformCodes(); - return Object.entries(config.platforms) - .filter(([_, info]) => info.category === category) - .map(([code, _]) => code); -} - -/** - * Get all platforms with installer config - * @returns {Promise} Array of platform codes that have installer config - */ -async function getConfigDrivenPlatforms() { - const config = await loadPlatformCodes(); - return Object.entries(config.platforms) - .filter(([_, info]) => info.installer) - .map(([code, _]) => code); -} - -/** - * Get platforms that use custom installers (no installer config) - * @returns {Promise} Array of platform codes with custom installers - */ -async function getCustomInstallerPlatforms() { - const config = await loadPlatformCodes(); - return Object.entries(config.platforms) - .filter(([_, info]) => !info.installer) - .map(([code, _]) => code); -} - -/** - * Clear the cached platform codes (useful for testing) - */ -function clearCache() { - _cachedPlatformCodes = null; -} - -module.exports = { - loadPlatformCodes, - getPlatformInfo, - getPreferredPlatforms, - getPlatformsByCategory, - getConfigDrivenPlatforms, - getCustomInstallerPlatforms, - clearCache, -}; diff --git a/tools/cli/installers/lib/ide/platform-codes.yaml b/tools/cli/installers/lib/ide/platform-codes.yaml deleted file mode 100644 index 4e6ca8070..000000000 --- a/tools/cli/installers/lib/ide/platform-codes.yaml +++ /dev/null @@ -1,243 +0,0 @@ -# BMAD Platform Codes Configuration -# Central configuration for all platform/IDE codes used in the BMAD system -# -# This file defines: -# 1. Platform metadata (name, preferred status, category, description) -# 2. Installer configuration (target directories, templates, artifact types) -# -# Format: -# code: Platform identifier used internally -# name: Display name shown to users -# preferred: Whether this platform is shown as a recommended option on install -# category: Type of platform (ide, cli, tool, service) -# description: Brief description of the platform -# installer: Installation configuration (optional - omit for custom installers) - -platforms: - antigravity: - name: "Google Antigravity" - preferred: false - category: ide - description: "Google's AI development environment" - installer: - target_dir: .agent/workflows - template_type: antigravity - - auggie: - name: "Auggie" - preferred: false - category: cli - description: "AI development tool" - installer: - target_dir: .augment/commands - template_type: default - - claude-code: - name: "Claude Code" - preferred: true - category: cli - description: "Anthropic's official CLI for Claude" - installer: - target_dir: .claude/commands - template_type: default - ancestor_conflict_check: true - - cline: - name: "Cline" - preferred: false - category: ide - description: "AI coding assistant" - installer: - target_dir: .clinerules/workflows - template_type: windsurf - - codex: - name: "Codex" - preferred: false - category: cli - description: "OpenAI Codex integration" - # No installer config - uses custom codex.js - - codebuddy: - name: "CodeBuddy" - preferred: false - category: ide - description: "Tencent Cloud Code Assistant - AI-powered coding companion" - installer: - target_dir: .codebuddy/commands - template_type: default - - crush: - name: "Crush" - preferred: false - category: ide - description: "AI development assistant" - installer: - target_dir: .crush/commands - template_type: default - - cursor: - name: "Cursor" - preferred: true - category: ide - description: "AI-first code editor" - installer: - target_dir: .cursor/commands - template_type: default - - gemini: - name: "Gemini CLI" - preferred: false - category: cli - description: "Google's CLI for Gemini" - installer: - target_dir: .gemini/commands - template_type: gemini - - github-copilot: - name: "GitHub Copilot" - preferred: false - category: ide - description: "GitHub's AI pair programmer" - # No installer config - uses custom github-copilot.js - - iflow: - name: "iFlow" - preferred: false - category: ide - description: "AI workflow automation" - installer: - target_dir: .iflow/commands - template_type: default - - kilo: - name: "KiloCoder" - preferred: false - category: ide - description: "AI coding platform" - # No installer config - uses custom kilo.js (creates .kilocodemodes file) - - kiro: - name: "Kiro" - preferred: false - category: ide - description: "Amazon's AI-powered IDE" - installer: - target_dir: .kiro/steering - template_type: kiro - - opencode: - name: "OpenCode" - preferred: false - category: ide - description: "OpenCode terminal coding assistant" - installer: - legacy_targets: - - .opencode/agent - - .opencode/command - targets: - - target_dir: .opencode/agents - template_type: opencode - artifact_types: [agents] - - target_dir: .opencode/commands - template_type: opencode - artifact_types: [workflows, tasks, tools] - - qwen: - name: "QwenCoder" - preferred: false - category: ide - description: "Qwen AI coding assistant" - installer: - target_dir: .qwen/commands - template_type: default - - roo: - name: "Roo Cline" - preferred: false - category: ide - description: "Enhanced Cline fork" - installer: - target_dir: .roo/commands - template_type: default - - rovo-dev: - name: "Rovo Dev" - preferred: false - category: ide - description: "Atlassian's Rovo development environment" - # No installer config - uses custom rovodev.js (generates prompts.yml manifest) - - trae: - name: "Trae" - preferred: false - category: ide - description: "AI coding tool" - installer: - target_dir: .trae/rules - template_type: trae - - windsurf: - name: "Windsurf" - preferred: false - category: ide - description: "AI-powered IDE with cascade flows" - installer: - target_dir: .windsurf/workflows - template_type: windsurf - -# ============================================================================ -# Installer Config Schema -# ============================================================================ -# -# installer: -# target_dir: string # Directory where artifacts are installed -# template_type: string # Default template type to use -# header_template: string (optional) # Override for header/frontmatter template -# body_template: string (optional) # Override for body/content template -# legacy_targets: array (optional) # Old target dirs to clean up on reinstall (migration) -# - string # Relative path, e.g. .opencode/agent -# targets: array (optional) # For multi-target installations -# - target_dir: string -# template_type: string -# artifact_types: [agents, workflows, tasks, tools] -# artifact_types: array (optional) # Filter which artifacts to install (default: all) -# skip_existing: boolean (optional) # Skip files that already exist (default: false) -# ancestor_conflict_check: boolean (optional) # Refuse install when ancestor dir has BMAD files -# # in the same target_dir (for IDEs that inherit -# # commands from parent directories) - -# ============================================================================ -# Platform Categories -# ============================================================================ - -categories: - ide: - name: "Integrated Development Environment" - description: "Full-featured code editors with AI assistance" - - cli: - name: "Command Line Interface" - description: "Terminal-based tools" - - tool: - name: "Development Tool" - description: "Standalone development utilities" - - service: - name: "Cloud Service" - description: "Cloud-based development platforms" - - extension: - name: "Editor Extension" - description: "Plugins for existing editors" - -# ============================================================================ -# Naming Conventions and Rules -# ============================================================================ - -conventions: - code_format: "lowercase-kebab-case" - name_format: "Title Case" - max_code_length: 20 - allowed_characters: "a-z0-9-" diff --git a/tools/cli/installers/lib/ide/rovodev.js b/tools/cli/installers/lib/ide/rovodev.js deleted file mode 100644 index da3c4809d..000000000 --- a/tools/cli/installers/lib/ide/rovodev.js +++ /dev/null @@ -1,257 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const yaml = require('yaml'); -const { BaseIdeSetup } = require('./_base-ide'); -const prompts = require('../../../lib/prompts'); -const { AgentCommandGenerator } = require('./shared/agent-command-generator'); -const { WorkflowCommandGenerator } = require('./shared/workflow-command-generator'); -const { TaskToolCommandGenerator } = require('./shared/task-tool-command-generator'); -const { toDashPath } = require('./shared/path-utils'); - -/** - * Rovo Dev IDE setup handler - * - * Custom installer that writes .md workflow files to .rovodev/workflows/ - * and generates .rovodev/prompts.yml to register them with Rovo Dev's /prompts feature. - * - * prompts.yml format (per Rovo Dev docs): - * prompts: - * - name: bmad-bmm-create-prd - * description: "PRD workflow..." - * content_file: workflows/bmad-bmm-create-prd.md - */ -class RovoDevSetup extends BaseIdeSetup { - constructor() { - super('rovo-dev', 'Rovo Dev', false); - this.rovoDir = '.rovodev'; - this.workflowsDir = 'workflows'; - this.promptsFile = 'prompts.yml'; - } - - /** - * Setup Rovo Dev configuration - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {Object} options - Setup options - * @returns {Promise} Setup result with { success, results: { agents, workflows, tasks, tools } } - */ - async setup(projectDir, bmadDir, options = {}) { - if (!options.silent) await prompts.log.info(`Setting up ${this.name}...`); - - // Clean up any old BMAD installation first - await this.cleanup(projectDir, options); - - const workflowsPath = path.join(projectDir, this.rovoDir, this.workflowsDir); - await this.ensureDir(workflowsPath); - - const selectedModules = options.selectedModules || []; - const writtenFiles = []; - - // Generate and write agent launchers - const agentGen = new AgentCommandGenerator(this.bmadFolderName); - const { artifacts: agentArtifacts } = await agentGen.collectAgentArtifacts(bmadDir, selectedModules); - const agentCount = await agentGen.writeDashArtifacts(workflowsPath, agentArtifacts); - this._collectPromptEntries(writtenFiles, agentArtifacts, ['agent-launcher'], 'agent'); - - // Generate and write workflow commands - const workflowGen = new WorkflowCommandGenerator(this.bmadFolderName); - const { artifacts: workflowArtifacts } = await workflowGen.collectWorkflowArtifacts(bmadDir); - const workflowCount = await workflowGen.writeDashArtifacts(workflowsPath, workflowArtifacts); - this._collectPromptEntries(writtenFiles, workflowArtifacts, ['workflow-command'], 'workflow'); - - // Generate and write task/tool commands - const taskToolGen = new TaskToolCommandGenerator(this.bmadFolderName); - const { artifacts: taskToolArtifacts, counts: taskToolCounts } = await taskToolGen.collectTaskToolArtifacts(bmadDir); - await taskToolGen.writeDashArtifacts(workflowsPath, taskToolArtifacts); - const taskCount = taskToolCounts.tasks || 0; - const toolCount = taskToolCounts.tools || 0; - this._collectPromptEntries(writtenFiles, taskToolArtifacts, ['task', 'tool']); - - // Generate prompts.yml manifest (only if we have entries to write) - if (writtenFiles.length > 0) { - await this.generatePromptsYml(projectDir, writtenFiles); - } - - if (!options.silent) { - await prompts.log.success( - `${this.name} configured: ${agentCount} agents, ${workflowCount} workflows, ${taskCount} tasks, ${toolCount} tools`, - ); - } - - return { - success: true, - results: { - agents: agentCount, - workflows: workflowCount, - tasks: taskCount, - tools: toolCount, - }, - }; - } - - /** - * Collect prompt entries from artifacts into writtenFiles array - * @param {Array} writtenFiles - Target array to push entries into - * @param {Array} artifacts - Artifacts from a generator's collect method - * @param {string[]} acceptedTypes - Artifact types to include (e.g., ['agent-launcher']) - * @param {string} [fallbackSuffix] - Suffix for fallback description; defaults to artifact.type - */ - _collectPromptEntries(writtenFiles, artifacts, acceptedTypes, fallbackSuffix) { - for (const artifact of artifacts) { - if (!acceptedTypes.includes(artifact.type)) continue; - const flatName = toDashPath(artifact.relativePath); - writtenFiles.push({ - name: path.basename(flatName, '.md'), - description: artifact.description || `${artifact.name} ${fallbackSuffix || artifact.type}`, - contentFile: `${this.workflowsDir}/${flatName}`, - }); - } - } - - /** - * Generate .rovodev/prompts.yml manifest - * Merges with existing user entries -- strips entries with names starting 'bmad-', - * appends new BMAD entries, and writes back. - * - * @param {string} projectDir - Project directory - * @param {Array} writtenFiles - Array of { name, description, contentFile } - */ - async generatePromptsYml(projectDir, writtenFiles) { - const promptsPath = path.join(projectDir, this.rovoDir, this.promptsFile); - let existingPrompts = []; - - // Read existing prompts.yml and preserve non-BMAD entries - if (await this.pathExists(promptsPath)) { - try { - const content = await this.readFile(promptsPath); - const parsed = yaml.parse(content); - if (parsed && Array.isArray(parsed.prompts)) { - // Keep only non-BMAD entries (entries whose name does NOT start with bmad-) - existingPrompts = parsed.prompts.filter((entry) => !entry.name || !entry.name.startsWith('bmad-')); - } - } catch { - // If parsing fails, start fresh but preserve file safety - existingPrompts = []; - } - } - - // Build new BMAD entries (prefix description with name so /prompts list is scannable) - const bmadEntries = writtenFiles.map((file) => ({ - name: file.name, - description: `${file.name} - ${file.description}`, - content_file: file.contentFile, - })); - - // Merge: user entries first, then BMAD entries - const allPrompts = [...existingPrompts, ...bmadEntries]; - - const config = { prompts: allPrompts }; - const yamlContent = yaml.stringify(config, { lineWidth: 0 }); - await this.writeFile(promptsPath, yamlContent); - } - - /** - * Cleanup Rovo Dev configuration - * Removes bmad-* files from .rovodev/workflows/ and strips BMAD entries from prompts.yml - * @param {string} projectDir - Project directory - * @param {Object} options - Cleanup options - */ - async cleanup(projectDir, options = {}) { - const workflowsPath = path.join(projectDir, this.rovoDir, this.workflowsDir); - - // Remove all bmad-* entries from workflows dir (aligned with detect() predicate) - if (await this.pathExists(workflowsPath)) { - const entries = await fs.readdir(workflowsPath); - for (const entry of entries) { - if (entry.startsWith('bmad-')) { - await fs.remove(path.join(workflowsPath, entry)); - } - } - } - - // Clean BMAD entries from prompts.yml (preserve user entries) - const promptsPath = path.join(projectDir, this.rovoDir, this.promptsFile); - if (await this.pathExists(promptsPath)) { - try { - const content = await this.readFile(promptsPath); - const parsed = yaml.parse(content) || {}; - - if (Array.isArray(parsed.prompts)) { - const originalCount = parsed.prompts.length; - parsed.prompts = parsed.prompts.filter((entry) => !entry.name || !entry.name.startsWith('bmad-')); - const removedCount = originalCount - parsed.prompts.length; - - if (removedCount > 0) { - if (parsed.prompts.length === 0) { - // If no entries remain, remove the file entirely - await fs.remove(promptsPath); - } else { - await this.writeFile(promptsPath, yaml.stringify(parsed, { lineWidth: 0 })); - } - if (!options.silent) { - await prompts.log.message(`Removed ${removedCount} BMAD entries from ${this.promptsFile}`); - } - } - } - } catch { - // If parsing fails, leave file as-is - if (!options.silent) { - await prompts.log.warn(`Warning: Could not parse ${this.promptsFile} for cleanup`); - } - } - } - - // Remove empty .rovodev directories - if (await this.pathExists(workflowsPath)) { - const remaining = await fs.readdir(workflowsPath); - if (remaining.length === 0) { - await fs.remove(workflowsPath); - } - } - - const rovoDirPath = path.join(projectDir, this.rovoDir); - if (await this.pathExists(rovoDirPath)) { - const remaining = await fs.readdir(rovoDirPath); - if (remaining.length === 0) { - await fs.remove(rovoDirPath); - } - } - } - - /** - * Detect whether Rovo Dev configuration exists in the project - * Checks for .rovodev/ dir with bmad files or bmad entries in prompts.yml - * @param {string} projectDir - Project directory - * @returns {boolean} - */ - async detect(projectDir) { - const workflowsPath = path.join(projectDir, this.rovoDir, this.workflowsDir); - - // Check for bmad files in workflows dir - if (await fs.pathExists(workflowsPath)) { - const entries = await fs.readdir(workflowsPath); - if (entries.some((entry) => entry.startsWith('bmad-'))) { - return true; - } - } - - // Check for bmad entries in prompts.yml - const promptsPath = path.join(projectDir, this.rovoDir, this.promptsFile); - if (await fs.pathExists(promptsPath)) { - try { - const content = await fs.readFile(promptsPath, 'utf8'); - const parsed = yaml.parse(content); - if (parsed && Array.isArray(parsed.prompts)) { - return parsed.prompts.some((entry) => entry.name && entry.name.startsWith('bmad-')); - } - } catch { - // If parsing fails, check raw content - return false; - } - } - - return false; - } -} - -module.exports = { RovoDevSetup }; diff --git a/tools/cli/installers/lib/ide/shared/agent-command-generator.js b/tools/cli/installers/lib/ide/shared/agent-command-generator.js deleted file mode 100644 index 0915c306b..000000000 --- a/tools/cli/installers/lib/ide/shared/agent-command-generator.js +++ /dev/null @@ -1,180 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const { toColonPath, toDashPath, customAgentColonName, customAgentDashName, BMAD_FOLDER_NAME } = require('./path-utils'); - -/** - * Generates launcher command files for each agent - * Similar to WorkflowCommandGenerator but for agents - */ -class AgentCommandGenerator { - constructor(bmadFolderName = BMAD_FOLDER_NAME) { - this.templatePath = path.join(__dirname, '../templates/agent-command-template.md'); - this.bmadFolderName = bmadFolderName; - } - - /** - * Collect agent artifacts for IDE installation - * @param {string} bmadDir - BMAD installation directory - * @param {Array} selectedModules - Modules to include - * @returns {Object} Artifacts array with metadata - */ - async collectAgentArtifacts(bmadDir, selectedModules = []) { - const { getAgentsFromBmad } = require('./bmad-artifacts'); - - // Get agents from INSTALLED bmad/ directory - const agents = await getAgentsFromBmad(bmadDir, selectedModules); - - const artifacts = []; - - for (const agent of agents) { - const launcherContent = await this.generateLauncherContent(agent); - // Use relativePath if available (for nested agents), otherwise just name with .md - const agentPathInModule = agent.relativePath || `${agent.name}.md`; - // Calculate the relative agent path (e.g., bmm/agents/pm.md) - let agentRelPath = agent.path || ''; - // Normalize path separators for cross-platform compatibility - agentRelPath = agentRelPath.replaceAll('\\', '/'); - // Remove _bmad/ prefix if present to get relative path from project root - // Handle both absolute paths (/path/to/_bmad/...) and relative paths (_bmad/...) - if (agentRelPath.includes('_bmad/')) { - const parts = agentRelPath.split(/_bmad\//); - if (parts.length > 1) { - agentRelPath = parts.slice(1).join('/'); - } - } - artifacts.push({ - type: 'agent-launcher', - name: agent.name, - description: agent.description || `${agent.name} agent`, - module: agent.module, - relativePath: path.join(agent.module, 'agents', agentPathInModule), // For command filename - agentPath: agentRelPath, // Relative path to actual agent file - content: launcherContent, - sourcePath: agent.path, - }); - } - - return { - artifacts, - counts: { - agents: agents.length, - }, - }; - } - - /** - * Generate launcher content for an agent - * @param {Object} agent - Agent metadata - * @returns {string} Launcher file content - */ - async generateLauncherContent(agent) { - // Load the template - const template = await fs.readFile(this.templatePath, 'utf8'); - - // Replace template variables - // Use relativePath if available (for nested agents), otherwise just name with .md - const agentPathInModule = agent.relativePath || `${agent.name}.md`; - return template - .replaceAll('{{name}}', agent.name) - .replaceAll('{{module}}', agent.module) - .replaceAll('{{path}}', agentPathInModule) - .replaceAll('{{description}}', agent.description || `${agent.name} agent`) - .replaceAll('_bmad', this.bmadFolderName) - .replaceAll('_bmad', '_bmad'); - } - - /** - * Write agent launcher artifacts to IDE commands directory - * @param {string} baseCommandsDir - Base commands directory for the IDE - * @param {Array} artifacts - Agent launcher artifacts - * @returns {number} Count of launchers written - */ - async writeAgentLaunchers(baseCommandsDir, artifacts) { - let writtenCount = 0; - - for (const artifact of artifacts) { - if (artifact.type === 'agent-launcher') { - const moduleAgentsDir = path.join(baseCommandsDir, artifact.module, 'agents'); - await fs.ensureDir(moduleAgentsDir); - - const launcherPath = path.join(moduleAgentsDir, `${artifact.name}.md`); - await fs.writeFile(launcherPath, artifact.content); - writtenCount++; - } - } - - return writtenCount; - } - - /** - * Write agent launcher artifacts using underscore format (Windows-compatible) - * Creates flat files like: bmad_bmm_pm.md - * - * @param {string} baseCommandsDir - Base commands directory for the IDE - * @param {Array} artifacts - Agent launcher artifacts - * @returns {number} Count of launchers written - */ - async writeColonArtifacts(baseCommandsDir, artifacts) { - let writtenCount = 0; - - for (const artifact of artifacts) { - if (artifact.type === 'agent-launcher') { - // Convert relativePath to underscore format: bmm/agents/pm.md → bmad_bmm_pm.md - const flatName = toColonPath(artifact.relativePath); - const launcherPath = path.join(baseCommandsDir, flatName); - await fs.ensureDir(path.dirname(launcherPath)); - await fs.writeFile(launcherPath, artifact.content); - writtenCount++; - } - } - - return writtenCount; - } - - /** - * Write agent launcher artifacts using dash format (NEW STANDARD) - * Creates flat files like: bmad-agent-bmm-pm.md - * - * The bmad-agent- prefix distinguishes agents from workflows/tasks/tools. - * - * @param {string} baseCommandsDir - Base commands directory for the IDE - * @param {Array} artifacts - Agent launcher artifacts - * @returns {number} Count of launchers written - */ - async writeDashArtifacts(baseCommandsDir, artifacts) { - let writtenCount = 0; - - for (const artifact of artifacts) { - if (artifact.type === 'agent-launcher') { - // Convert relativePath to dash format: bmm/agents/pm.md → bmad-agent-bmm-pm.md - const flatName = toDashPath(artifact.relativePath); - const launcherPath = path.join(baseCommandsDir, flatName); - await fs.ensureDir(path.dirname(launcherPath)); - await fs.writeFile(launcherPath, artifact.content); - writtenCount++; - } - } - - return writtenCount; - } - - /** - * Get the custom agent name in underscore format (Windows-compatible) - * @param {string} agentName - Custom agent name - * @returns {string} Underscore-formatted filename - */ - getCustomAgentColonName(agentName) { - return customAgentColonName(agentName); - } - - /** - * Get the custom agent name in underscore format (Windows-compatible) - * @param {string} agentName - Custom agent name - * @returns {string} Underscore-formatted filename - */ - getCustomAgentDashName(agentName) { - return customAgentDashName(agentName); - } -} - -module.exports = { AgentCommandGenerator }; diff --git a/tools/cli/installers/lib/ide/shared/bmad-artifacts.js b/tools/cli/installers/lib/ide/shared/bmad-artifacts.js deleted file mode 100644 index 7bcfd6a79..000000000 --- a/tools/cli/installers/lib/ide/shared/bmad-artifacts.js +++ /dev/null @@ -1,174 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); - -/** - * Helpers for gathering BMAD agents/tasks from the installed tree. - * Shared by installers that need Claude-style exports. - */ -async function getAgentsFromBmad(bmadDir, selectedModules = []) { - const agents = []; - - // Get core agents - if (await fs.pathExists(path.join(bmadDir, 'core', 'agents'))) { - const coreAgents = await getAgentsFromDir(path.join(bmadDir, 'core', 'agents'), 'core'); - agents.push(...coreAgents); - } - - // Get module agents - for (const moduleName of selectedModules) { - const agentsPath = path.join(bmadDir, moduleName, 'agents'); - - if (await fs.pathExists(agentsPath)) { - const moduleAgents = await getAgentsFromDir(agentsPath, moduleName); - agents.push(...moduleAgents); - } - } - - // Get standalone agents from bmad/agents/ directory - const standaloneAgentsDir = path.join(bmadDir, 'agents'); - if (await fs.pathExists(standaloneAgentsDir)) { - const agentDirs = await fs.readdir(standaloneAgentsDir, { withFileTypes: true }); - - for (const agentDir of agentDirs) { - if (!agentDir.isDirectory()) continue; - - const agentDirPath = path.join(standaloneAgentsDir, agentDir.name); - const agentFiles = await fs.readdir(agentDirPath); - - for (const file of agentFiles) { - if (!file.endsWith('.md')) continue; - if (file.includes('.customize.')) continue; - - const filePath = path.join(agentDirPath, file); - const content = await fs.readFile(filePath, 'utf8'); - - if (content.includes('localskip="true"')) continue; - - agents.push({ - path: filePath, - name: file.replace('.md', ''), - module: 'standalone', // Mark as standalone agent - }); - } - } - } - - return agents; -} - -async function getTasksFromBmad(bmadDir, selectedModules = []) { - const tasks = []; - - if (await fs.pathExists(path.join(bmadDir, 'core', 'tasks'))) { - const coreTasks = await getTasksFromDir(path.join(bmadDir, 'core', 'tasks'), 'core'); - tasks.push(...coreTasks); - } - - for (const moduleName of selectedModules) { - const tasksPath = path.join(bmadDir, moduleName, 'tasks'); - - if (await fs.pathExists(tasksPath)) { - const moduleTasks = await getTasksFromDir(tasksPath, moduleName); - tasks.push(...moduleTasks); - } - } - - return tasks; -} - -async function getAgentsFromDir(dirPath, moduleName, relativePath = '') { - const agents = []; - - if (!(await fs.pathExists(dirPath))) { - return agents; - } - - const entries = await fs.readdir(dirPath, { withFileTypes: true }); - - for (const entry of entries) { - // Skip if entry.name is undefined or not a string - if (!entry.name || typeof entry.name !== 'string') { - continue; - } - - const fullPath = path.join(dirPath, entry.name); - const newRelativePath = relativePath ? `${relativePath}/${entry.name}` : entry.name; - - if (entry.isDirectory()) { - // Recurse into subdirectories - const subDirAgents = await getAgentsFromDir(fullPath, moduleName, newRelativePath); - agents.push(...subDirAgents); - } else if (entry.name.endsWith('.md')) { - // Skip README files and other non-agent files - if (entry.name.toLowerCase() === 'readme.md' || entry.name.toLowerCase().startsWith('readme-')) { - continue; - } - - if (entry.name.includes('.customize.')) { - continue; - } - - const content = await fs.readFile(fullPath, 'utf8'); - - if (content.includes('localskip="true"')) { - continue; - } - - // Only include files that have agent-specific content (compiled agents have tag) - if (!content.includes(' 0) { - return true; - } - - if (injection.requires) { - const required = `${injection.requires}.md`; - return selected.includes(required); - } - - if (injection.point) { - const selectedNames = selected.map((file) => file.replace('.md', '')); - return selectedNames.some((name) => injection.point.includes(name)); - } - } - - return false; -} - -function filterAgentInstructions(content, selectedFiles) { - if (!selectedFiles || selectedFiles.length === 0) { - return ''; - } - - const selectedAgents = selectedFiles.map((file) => file.replace('.md', '')); - const lines = content.split('\n'); - const filteredLines = []; - - for (const line of lines) { - if (line.includes('')) { - filteredLines.push(line); - } else if (line.includes('subagent')) { - let shouldInclude = false; - for (const agent of selectedAgents) { - if (line.includes(agent)) { - shouldInclude = true; - break; - } - } - - if (shouldInclude) { - filteredLines.push(line); - } - } else if (line.includes('When creating PRDs') || line.includes('ACTIVELY delegate')) { - filteredLines.push(line); - } - } - - if (filteredLines.length > 2) { - return filteredLines.join('\n'); - } - - return ''; -} - -async function resolveSubagentFiles(handlerBaseDir, subagentConfig, subagentChoices) { - if (!subagentConfig || !subagentConfig.files) { - return []; - } - - if (!subagentChoices || subagentChoices.install === 'none') { - return []; - } - - let filesToCopy = subagentConfig.files; - - if (subagentChoices.install === 'selective') { - filesToCopy = subagentChoices.selected || []; - } - - const sourceDir = path.join(handlerBaseDir, subagentConfig.source || ''); - const resolved = []; - - for (const file of filesToCopy) { - // Use forward slashes for glob pattern (works on both Windows and Unix) - // Convert backslashes to forward slashes for glob compatibility - const normalizedSourceDir = sourceDir.replaceAll('\\', '/'); - const pattern = `${normalizedSourceDir}/**/${file}`; - const matches = await glob(pattern); - - if (matches.length > 0) { - const absolutePath = matches[0]; - resolved.push({ - file, - absolutePath, - relativePath: path.relative(sourceDir, absolutePath), - sourceDir, - }); - } - } - - return resolved; -} - -module.exports = { - loadModuleInjectionConfig, - shouldApplyInjection, - filterAgentInstructions, - resolveSubagentFiles, -}; diff --git a/tools/cli/installers/lib/ide/shared/path-utils.js b/tools/cli/installers/lib/ide/shared/path-utils.js deleted file mode 100644 index 519669233..000000000 --- a/tools/cli/installers/lib/ide/shared/path-utils.js +++ /dev/null @@ -1,299 +0,0 @@ -/** - * Path transformation utilities for IDE installer standardization - * - * Provides utilities to convert hierarchical paths to flat naming conventions. - * - * DASH-BASED NAMING (new standard): - * - Agents: bmad-agent-module-name.md (with bmad-agent- prefix) - * - Workflows/Tasks/Tools: bmad-module-name.md - * - * Example outputs: - * - cis/agents/storymaster.md → bmad-agent-cis-storymaster.md - * - bmm/workflows/plan-project.md → bmad-bmm-plan-project.md - * - bmm/tasks/create-story.md → bmad-bmm-create-story.md - * - core/agents/brainstorming.md → bmad-agent-brainstorming.md (core agents skip module name) - */ - -// Type segments - agents are included in naming, others are filtered out -const TYPE_SEGMENTS = ['workflows', 'tasks', 'tools']; -const AGENT_SEGMENT = 'agents'; - -// BMAD installation folder name - centralized constant for all installers -const BMAD_FOLDER_NAME = '_bmad'; - -/** - * Convert hierarchical path to flat dash-separated name (NEW STANDARD) - * Converts: 'bmm', 'agents', 'pm' → 'bmad-agent-bmm-pm.md' - * Converts: 'bmm', 'workflows', 'correct-course' → 'bmad-bmm-correct-course.md' - * Converts: 'core', 'agents', 'brainstorming' → 'bmad-agent-brainstorming.md' (core agents skip module name) - * - * @param {string} module - Module name (e.g., 'bmm', 'core') - * @param {string} type - Artifact type ('agents', 'workflows', 'tasks', 'tools') - * @param {string} name - Artifact name (e.g., 'pm', 'brainstorming') - * @returns {string} Flat filename like 'bmad-agent-bmm-pm.md' or 'bmad-bmm-correct-course.md' - */ -function toDashName(module, type, name) { - const isAgent = type === AGENT_SEGMENT; - - // For core module, skip the module name: use 'bmad-agent-name.md' instead of 'bmad-agent-core-name.md' - if (module === 'core') { - return isAgent ? `bmad-agent-${name}.md` : `bmad-${name}.md`; - } - - // Module artifacts: bmad-module-name.md or bmad-agent-module-name.md - // eslint-disable-next-line unicorn/prefer-string-replace-all -- regex replace is intentional here - const dashName = name.replace(/\//g, '-'); // Flatten nested paths - return isAgent ? `bmad-agent-${module}-${dashName}.md` : `bmad-${module}-${dashName}.md`; -} - -/** - * Convert relative path to flat dash-separated name - * Converts: 'bmm/agents/pm.md' → 'bmad-agent-bmm-pm.md' - * Converts: 'bmm/agents/tech-writer/tech-writer.md' → 'bmad-agent-bmm-tech-writer.md' (uses folder name) - * Converts: 'bmm/workflows/correct-course.md' → 'bmad-bmm-correct-course.md' - * Converts: 'core/agents/brainstorming.md' → 'bmad-agent-brainstorming.md' (core agents skip module name) - * - * @param {string} relativePath - Path like 'bmm/agents/pm.md' - * @returns {string} Flat filename like 'bmad-agent-bmm-pm.md' or 'bmad-brainstorming.md' - */ -function toDashPath(relativePath) { - if (!relativePath || typeof relativePath !== 'string') { - // Return a safe default for invalid input - return 'bmad-unknown.md'; - } - - // Strip common file extensions to avoid double extensions in generated filenames - // e.g., 'create-story.xml' → 'create-story', 'workflow.yaml' → 'workflow' - const withoutExt = relativePath.replace(/\.(md|yaml|yml|json|xml|toml)$/i, ''); - const parts = withoutExt.split(/[/\\]/); - - const module = parts[0]; - const type = parts[1]; - let name; - - // For agents, if nested in a folder (more than 3 parts), use the folder name only - // e.g., 'bmm/agents/tech-writer/tech-writer' → 'tech-writer' (not 'tech-writer-tech-writer') - if (type === 'agents' && parts.length > 3) { - // Use the folder name (parts[2]) as the name, ignore the file name - name = parts[2]; - } else { - // For non-nested or non-agents, join all parts after type - name = parts.slice(2).join('-'); - } - - return toDashName(module, type, name); -} - -/** - * Create custom agent dash name - * Creates: 'bmad-custom-agent-fred-commit-poet.md' - * - * @param {string} agentName - Custom agent name - * @returns {string} Flat filename like 'bmad-custom-agent-fred-commit-poet.md' - */ -function customAgentDashName(agentName) { - return `bmad-custom-agent-${agentName}.md`; -} - -/** - * Check if a filename uses dash format - * @param {string} filename - Filename to check - * @returns {boolean} True if filename uses dash format - */ -function isDashFormat(filename) { - return filename.startsWith('bmad-') && filename.includes('-'); -} - -/** - * Extract parts from a dash-formatted filename - * Parses: 'bmad-agent-bmm-pm.md' → { prefix: 'bmad', module: 'bmm', type: 'agents', name: 'pm' } - * Parses: 'bmad-bmm-correct-course.md' → { prefix: 'bmad', module: 'bmm', type: 'workflows', name: 'correct-course' } - * Parses: 'bmad-agent-brainstorming.md' → { prefix: 'bmad', module: 'core', type: 'agents', name: 'brainstorming' } (core agents) - * Parses: 'bmad-brainstorming.md' → { prefix: 'bmad', module: 'core', type: 'workflows', name: 'brainstorming' } (core workflows) - * - * @param {string} filename - Dash-formatted filename - * @returns {Object|null} Parsed parts or null if invalid format - */ -function parseDashName(filename) { - const withoutExt = filename.replace('.md', ''); - const parts = withoutExt.split('-'); - - if (parts.length < 2 || parts[0] !== 'bmad') { - return null; - } - - // Check if this is an agent file (has 'agent' as second part) - const isAgent = parts[1] === 'agent'; - - if (isAgent) { - // This is an agent file - // Format: bmad-agent-name (core) or bmad-agent-module-name - if (parts.length === 3) { - // Core agent: bmad-agent-name - return { - prefix: parts[0], - module: 'core', - type: 'agents', - name: parts[2], - }; - } else { - // Module agent: bmad-agent-module-name - return { - prefix: parts[0], - module: parts[2], - type: 'agents', - name: parts.slice(3).join('-'), - }; - } - } - - // Not an agent file - must be a workflow/tool/task - // If only 2 parts (bmad-name), it's a core workflow/tool/task - if (parts.length === 2) { - return { - prefix: parts[0], - module: 'core', - type: 'workflows', // Default to workflows for non-agent core items - name: parts[1], - }; - } - - // Otherwise, it's a module workflow/tool/task (bmad-module-name) - return { - prefix: parts[0], - module: parts[1], - type: 'workflows', // Default to workflows for non-agent module items - name: parts.slice(2).join('-'), - }; -} - -// ============================================================================ -// LEGACY FUNCTIONS (underscore format) - kept for backward compatibility -// ============================================================================ - -/** - * Convert hierarchical path to flat underscore-separated name (LEGACY) - * @deprecated Use toDashName instead - */ -function toUnderscoreName(module, type, name) { - const isAgent = type === AGENT_SEGMENT; - if (module === 'core') { - return isAgent ? `bmad_agent_${name}.md` : `bmad_${name}.md`; - } - return isAgent ? `bmad_${module}_agent_${name}.md` : `bmad_${module}_${name}.md`; -} - -/** - * Convert relative path to flat underscore-separated name (LEGACY) - * @deprecated Use toDashPath instead - */ -function toUnderscorePath(relativePath) { - // Strip common file extensions (same as toDashPath for consistency) - const withoutExt = relativePath.replace(/\.(md|yaml|yml|json|xml|toml)$/i, ''); - const parts = withoutExt.split(/[/\\]/); - - const module = parts[0]; - const type = parts[1]; - const name = parts.slice(2).join('_'); - - return toUnderscoreName(module, type, name); -} - -/** - * Create custom agent underscore name (LEGACY) - * @deprecated Use customAgentDashName instead - */ -function customAgentUnderscoreName(agentName) { - return `bmad_custom_${agentName}.md`; -} - -/** - * Check if a filename uses underscore format (LEGACY) - * @deprecated Use isDashFormat instead - */ -function isUnderscoreFormat(filename) { - return filename.startsWith('bmad_') && filename.includes('_'); -} - -/** - * Extract parts from an underscore-formatted filename (LEGACY) - * @deprecated Use parseDashName instead - */ -function parseUnderscoreName(filename) { - const withoutExt = filename.replace('.md', ''); - const parts = withoutExt.split('_'); - - if (parts.length < 2 || parts[0] !== 'bmad') { - return null; - } - - const agentIndex = parts.indexOf('agent'); - - if (agentIndex !== -1) { - if (agentIndex === 1) { - return { - prefix: parts[0], - module: 'core', - type: 'agents', - name: parts.slice(agentIndex + 1).join('_'), - }; - } else { - return { - prefix: parts[0], - module: parts[1], - type: 'agents', - name: parts.slice(agentIndex + 1).join('_'), - }; - } - } - - if (parts.length === 2) { - return { - prefix: parts[0], - module: 'core', - type: 'workflows', - name: parts[1], - }; - } - - return { - prefix: parts[0], - module: parts[1], - type: 'workflows', - name: parts.slice(2).join('_'), - }; -} - -// Backward compatibility aliases (colon format was same as underscore) -const toColonName = toUnderscoreName; -const toColonPath = toUnderscorePath; -const customAgentColonName = customAgentUnderscoreName; -const isColonFormat = isUnderscoreFormat; -const parseColonName = parseUnderscoreName; - -module.exports = { - // New standard (dash-based) - toDashName, - toDashPath, - customAgentDashName, - isDashFormat, - parseDashName, - - // Legacy (underscore-based) - kept for backward compatibility - toUnderscoreName, - toUnderscorePath, - customAgentUnderscoreName, - isUnderscoreFormat, - parseUnderscoreName, - - // Backward compatibility aliases - toColonName, - toColonPath, - customAgentColonName, - isColonFormat, - parseColonName, - - TYPE_SEGMENTS, - AGENT_SEGMENT, - BMAD_FOLDER_NAME, -}; diff --git a/tools/cli/installers/lib/ide/shared/task-tool-command-generator.js b/tools/cli/installers/lib/ide/shared/task-tool-command-generator.js deleted file mode 100644 index 93e5b9a81..000000000 --- a/tools/cli/installers/lib/ide/shared/task-tool-command-generator.js +++ /dev/null @@ -1,366 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const csv = require('csv-parse/sync'); -const { toColonName, toColonPath, toDashPath, BMAD_FOLDER_NAME } = require('./path-utils'); - -/** - * Generates command files for standalone tasks and tools - */ -class TaskToolCommandGenerator { - /** - * @param {string} bmadFolderName - Name of the BMAD folder for template rendering (default: '_bmad') - * Note: This parameter is accepted for API consistency with AgentCommandGenerator and - * WorkflowCommandGenerator, but is not used for path stripping. The manifest always stores - * filesystem paths with '_bmad/' prefix (the actual folder name), while bmadFolderName is - * used for template placeholder rendering ({{bmadFolderName}}). - */ - constructor(bmadFolderName = BMAD_FOLDER_NAME) { - this.bmadFolderName = bmadFolderName; - } - - /** - * Collect task and tool artifacts for IDE installation - * @param {string} bmadDir - BMAD installation directory - * @returns {Promise} Artifacts array with metadata - */ - async collectTaskToolArtifacts(bmadDir) { - const tasks = await this.loadTaskManifest(bmadDir); - const tools = await this.loadToolManifest(bmadDir); - - // All tasks/tools in manifest are standalone (internal=true items are filtered during manifest generation) - const artifacts = []; - const bmadPrefix = `${BMAD_FOLDER_NAME}/`; - - // Collect task artifacts - for (const task of tasks || []) { - let taskPath = (task.path || '').replaceAll('\\', '/'); - // Convert absolute paths to relative paths - if (path.isAbsolute(taskPath)) { - taskPath = path.relative(bmadDir, taskPath).replaceAll('\\', '/'); - } - // Remove _bmad/ prefix if present to get relative path within bmad folder - if (taskPath.startsWith(bmadPrefix)) { - taskPath = taskPath.slice(bmadPrefix.length); - } - - const taskExt = path.extname(taskPath) || '.md'; - artifacts.push({ - type: 'task', - name: task.name, - displayName: task.displayName || task.name, - description: task.description || `Execute ${task.displayName || task.name}`, - module: task.module, - // Use forward slashes for cross-platform consistency (not path.join which uses backslashes on Windows) - relativePath: `${task.module}/tasks/${task.name}${taskExt}`, - path: taskPath, - }); - } - - // Collect tool artifacts - for (const tool of tools || []) { - let toolPath = (tool.path || '').replaceAll('\\', '/'); - // Convert absolute paths to relative paths - if (path.isAbsolute(toolPath)) { - toolPath = path.relative(bmadDir, toolPath).replaceAll('\\', '/'); - } - // Remove _bmad/ prefix if present to get relative path within bmad folder - if (toolPath.startsWith(bmadPrefix)) { - toolPath = toolPath.slice(bmadPrefix.length); - } - - const toolExt = path.extname(toolPath) || '.md'; - artifacts.push({ - type: 'tool', - name: tool.name, - displayName: tool.displayName || tool.name, - description: tool.description || `Execute ${tool.displayName || tool.name}`, - module: tool.module, - // Use forward slashes for cross-platform consistency (not path.join which uses backslashes on Windows) - relativePath: `${tool.module}/tools/${tool.name}${toolExt}`, - path: toolPath, - }); - } - - return { - artifacts, - counts: { - tasks: (tasks || []).length, - tools: (tools || []).length, - }, - }; - } - - /** - * Generate task and tool commands from manifest CSVs - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {string} baseCommandsDir - Optional base commands directory (defaults to .claude/commands/bmad) - */ - async generateTaskToolCommands(projectDir, bmadDir, baseCommandsDir = null) { - const tasks = await this.loadTaskManifest(bmadDir); - const tools = await this.loadToolManifest(bmadDir); - - // Base commands directory - use provided or default to Claude Code structure - const commandsDir = baseCommandsDir || path.join(projectDir, '.claude', 'commands', 'bmad'); - - let generatedCount = 0; - - // Generate command files for tasks - for (const task of tasks || []) { - const moduleTasksDir = path.join(commandsDir, task.module, 'tasks'); - await fs.ensureDir(moduleTasksDir); - - const commandContent = this.generateCommandContent(task, 'task'); - const commandPath = path.join(moduleTasksDir, `${task.name}.md`); - - await fs.writeFile(commandPath, commandContent); - generatedCount++; - } - - // Generate command files for tools - for (const tool of tools || []) { - const moduleToolsDir = path.join(commandsDir, tool.module, 'tools'); - await fs.ensureDir(moduleToolsDir); - - const commandContent = this.generateCommandContent(tool, 'tool'); - const commandPath = path.join(moduleToolsDir, `${tool.name}.md`); - - await fs.writeFile(commandPath, commandContent); - generatedCount++; - } - - return { - generated: generatedCount, - tasks: (tasks || []).length, - tools: (tools || []).length, - }; - } - - /** - * Generate command content for a task or tool - */ - generateCommandContent(item, type) { - const description = item.description || `Execute ${item.displayName || item.name}`; - - // Convert path to use {project-root} placeholder - // Handle undefined/missing path by constructing from module and name - let itemPath = item.path; - if (!itemPath || typeof itemPath !== 'string') { - // Fallback: construct path from module and name if path is missing - const typePlural = type === 'task' ? 'tasks' : 'tools'; - itemPath = `{project-root}/${this.bmadFolderName}/${item.module}/${typePlural}/${item.name}.md`; - } else { - // Normalize path separators to forward slashes - itemPath = itemPath.replaceAll('\\', '/'); - - // Extract relative path from absolute paths (Windows or Unix) - // Look for _bmad/ or bmad/ in the path and extract everything after it - // Match patterns like: /_bmad/core/tasks/... or /bmad/core/tasks/... - // Use [/\\] to handle both Unix forward slashes and Windows backslashes, - // and also paths without a leading separator (e.g., C:/_bmad/...) - const bmadMatch = itemPath.match(/[/\\]_bmad[/\\](.+)$/) || itemPath.match(/[/\\]bmad[/\\](.+)$/); - if (bmadMatch) { - // Found /_bmad/ or /bmad/ - use relative path after it - itemPath = `{project-root}/${this.bmadFolderName}/${bmadMatch[1]}`; - } else if (itemPath.startsWith(`${BMAD_FOLDER_NAME}/`)) { - // Relative path starting with _bmad/ - itemPath = `{project-root}/${this.bmadFolderName}/${itemPath.slice(BMAD_FOLDER_NAME.length + 1)}`; - } else if (itemPath.startsWith('bmad/')) { - // Relative path starting with bmad/ - itemPath = `{project-root}/${this.bmadFolderName}/${itemPath.slice(5)}`; - } else if (!itemPath.startsWith('{project-root}')) { - // For other relative paths, prefix with project root and bmad folder - itemPath = `{project-root}/${this.bmadFolderName}/${itemPath}`; - } - } - - return `--- -description: '${description.replaceAll("'", "''")}' ---- - -# ${item.displayName || item.name} - -Read the entire ${type} file at: ${itemPath} - -Follow all instructions in the ${type} file exactly as written. -`; - } - - /** - * Load task manifest CSV - */ - async loadTaskManifest(bmadDir) { - const manifestPath = path.join(bmadDir, '_config', 'task-manifest.csv'); - - if (!(await fs.pathExists(manifestPath))) { - return null; - } - - const csvContent = await fs.readFile(manifestPath, 'utf8'); - return csv.parse(csvContent, { - columns: true, - skip_empty_lines: true, - }); - } - - /** - * Load tool manifest CSV - */ - async loadToolManifest(bmadDir) { - const manifestPath = path.join(bmadDir, '_config', 'tool-manifest.csv'); - - if (!(await fs.pathExists(manifestPath))) { - return null; - } - - const csvContent = await fs.readFile(manifestPath, 'utf8'); - return csv.parse(csvContent, { - columns: true, - skip_empty_lines: true, - }); - } - - /** - * Generate task and tool commands using underscore format (Windows-compatible) - * Creates flat files like: bmad_bmm_help.md - * - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {string} baseCommandsDir - Base commands directory for the IDE - * @returns {Object} Generation results - */ - async generateColonTaskToolCommands(projectDir, bmadDir, baseCommandsDir) { - const tasks = await this.loadTaskManifest(bmadDir); - const tools = await this.loadToolManifest(bmadDir); - - let generatedCount = 0; - - // Generate command files for tasks - for (const task of tasks || []) { - const commandContent = this.generateCommandContent(task, 'task'); - // Use underscore format: bmad_bmm_name.md - const flatName = toColonName(task.module, 'tasks', task.name); - const commandPath = path.join(baseCommandsDir, flatName); - await fs.ensureDir(path.dirname(commandPath)); - await fs.writeFile(commandPath, commandContent); - generatedCount++; - } - - // Generate command files for tools - for (const tool of tools || []) { - const commandContent = this.generateCommandContent(tool, 'tool'); - // Use underscore format: bmad_bmm_name.md - const flatName = toColonName(tool.module, 'tools', tool.name); - const commandPath = path.join(baseCommandsDir, flatName); - await fs.ensureDir(path.dirname(commandPath)); - await fs.writeFile(commandPath, commandContent); - generatedCount++; - } - - return { - generated: generatedCount, - tasks: (tasks || []).length, - tools: (tools || []).length, - }; - } - - /** - * Generate task and tool commands using underscore format (Windows-compatible) - * Creates flat files like: bmad_bmm_help.md - * - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - * @param {string} baseCommandsDir - Base commands directory for the IDE - * @returns {Object} Generation results - */ - async generateDashTaskToolCommands(projectDir, bmadDir, baseCommandsDir) { - const tasks = await this.loadTaskManifest(bmadDir); - const tools = await this.loadToolManifest(bmadDir); - - let generatedCount = 0; - - // Generate command files for tasks - for (const task of tasks || []) { - const commandContent = this.generateCommandContent(task, 'task'); - // Use dash format: bmad-bmm-name.md - const flatName = toDashPath(`${task.module}/tasks/${task.name}.md`); - const commandPath = path.join(baseCommandsDir, flatName); - await fs.ensureDir(path.dirname(commandPath)); - await fs.writeFile(commandPath, commandContent); - generatedCount++; - } - - // Generate command files for tools - for (const tool of tools || []) { - const commandContent = this.generateCommandContent(tool, 'tool'); - // Use dash format: bmad-bmm-name.md - const flatName = toDashPath(`${tool.module}/tools/${tool.name}.md`); - const commandPath = path.join(baseCommandsDir, flatName); - await fs.ensureDir(path.dirname(commandPath)); - await fs.writeFile(commandPath, commandContent); - generatedCount++; - } - - return { - generated: generatedCount, - tasks: (tasks || []).length, - tools: (tools || []).length, - }; - } - - /** - * Write task/tool artifacts using underscore format (Windows-compatible) - * Creates flat files like: bmad_bmm_help.md - * - * @param {string} baseCommandsDir - Base commands directory for the IDE - * @param {Array} artifacts - Task/tool artifacts with relativePath - * @returns {number} Count of commands written - */ - async writeColonArtifacts(baseCommandsDir, artifacts) { - let writtenCount = 0; - - for (const artifact of artifacts) { - if (artifact.type === 'task' || artifact.type === 'tool') { - const commandContent = this.generateCommandContent(artifact, artifact.type); - // Use underscore format: bmad_module_name.md - const flatName = toColonPath(artifact.relativePath); - const commandPath = path.join(baseCommandsDir, flatName); - await fs.ensureDir(path.dirname(commandPath)); - await fs.writeFile(commandPath, commandContent); - writtenCount++; - } - } - - return writtenCount; - } - - /** - * Write task/tool artifacts using dash format (NEW STANDARD) - * Creates flat files like: bmad-bmm-help.md - * - * Note: Tasks/tools do NOT have bmad-agent- prefix - only agents do. - * - * @param {string} baseCommandsDir - Base commands directory for the IDE - * @param {Array} artifacts - Task/tool artifacts with relativePath - * @returns {number} Count of commands written - */ - async writeDashArtifacts(baseCommandsDir, artifacts) { - let writtenCount = 0; - - for (const artifact of artifacts) { - if (artifact.type === 'task' || artifact.type === 'tool') { - const commandContent = this.generateCommandContent(artifact, artifact.type); - // Use dash format: bmad-module-name.md - const flatName = toDashPath(artifact.relativePath); - const commandPath = path.join(baseCommandsDir, flatName); - await fs.ensureDir(path.dirname(commandPath)); - await fs.writeFile(commandPath, commandContent); - writtenCount++; - } - } - - return writtenCount; - } -} - -module.exports = { TaskToolCommandGenerator }; diff --git a/tools/cli/installers/lib/ide/shared/workflow-command-generator.js b/tools/cli/installers/lib/ide/shared/workflow-command-generator.js deleted file mode 100644 index d94e77db1..000000000 --- a/tools/cli/installers/lib/ide/shared/workflow-command-generator.js +++ /dev/null @@ -1,318 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const csv = require('csv-parse/sync'); -const prompts = require('../../../../lib/prompts'); -const { toColonPath, toDashPath, customAgentColonName, customAgentDashName, BMAD_FOLDER_NAME } = require('./path-utils'); - -/** - * Generates command files for each workflow in the manifest - */ -class WorkflowCommandGenerator { - constructor(bmadFolderName = BMAD_FOLDER_NAME) { - this.templatePath = path.join(__dirname, '../templates/workflow-command-template.md'); - this.bmadFolderName = bmadFolderName; - } - - /** - * Generate workflow commands from the manifest CSV - * @param {string} projectDir - Project directory - * @param {string} bmadDir - BMAD installation directory - */ - async generateWorkflowCommands(projectDir, bmadDir) { - const workflows = await this.loadWorkflowManifest(bmadDir); - - if (!workflows) { - await prompts.log.warn('Workflow manifest not found. Skipping command generation.'); - return { generated: 0 }; - } - - // ALL workflows now generate commands - no standalone filtering - const allWorkflows = workflows; - - // Base commands directory - const baseCommandsDir = path.join(projectDir, '.claude', 'commands', 'bmad'); - - let generatedCount = 0; - - // Generate a command file for each workflow, organized by module - for (const workflow of allWorkflows) { - const moduleWorkflowsDir = path.join(baseCommandsDir, workflow.module, 'workflows'); - await fs.ensureDir(moduleWorkflowsDir); - - const commandContent = await this.generateCommandContent(workflow, bmadDir); - const commandPath = path.join(moduleWorkflowsDir, `${workflow.name}.md`); - - await fs.writeFile(commandPath, commandContent); - generatedCount++; - } - - // Also create a workflow launcher README in each module - const groupedWorkflows = this.groupWorkflowsByModule(allWorkflows); - await this.createModuleWorkflowLaunchers(baseCommandsDir, groupedWorkflows); - - return { generated: generatedCount }; - } - - async collectWorkflowArtifacts(bmadDir) { - const workflows = await this.loadWorkflowManifest(bmadDir); - - if (!workflows) { - return { artifacts: [], counts: { commands: 0, launchers: 0 } }; - } - - // ALL workflows now generate commands - no standalone filtering - const allWorkflows = workflows; - - const artifacts = []; - - for (const workflow of allWorkflows) { - const commandContent = await this.generateCommandContent(workflow, bmadDir); - // Calculate the relative workflow path (e.g., bmm/workflows/4-implementation/sprint-planning/workflow.yaml) - let workflowRelPath = workflow.path || ''; - // Normalize path separators for cross-platform compatibility - workflowRelPath = workflowRelPath.replaceAll('\\', '/'); - // Remove _bmad/ prefix if present to get relative path from project root - // Handle both absolute paths (/path/to/_bmad/...) and relative paths (_bmad/...) - if (workflowRelPath.includes('_bmad/')) { - const parts = workflowRelPath.split(/_bmad\//); - if (parts.length > 1) { - workflowRelPath = parts.slice(1).join('/'); - } - } else if (workflowRelPath.includes('/src/')) { - // Normalize source paths (e.g. .../src/bmm/...) to relative module path (e.g. bmm/...) - const match = workflowRelPath.match(/\/src\/([^/]+)\/(.+)/); - if (match) { - workflowRelPath = `${match[1]}/${match[2]}`; - } - } - // Determine if this is a YAML workflow (use normalized path which is guaranteed to be a string) - const isYamlWorkflow = workflowRelPath.endsWith('.yaml') || workflowRelPath.endsWith('.yml'); - artifacts.push({ - type: 'workflow-command', - isYamlWorkflow: isYamlWorkflow, // For template selection - name: workflow.name, - description: workflow.description || `${workflow.name} workflow`, - module: workflow.module, - relativePath: path.join(workflow.module, 'workflows', `${workflow.name}.md`), - workflowPath: workflowRelPath, // Relative path to actual workflow file - content: commandContent, - sourcePath: workflow.path, - }); - } - - const groupedWorkflows = this.groupWorkflowsByModule(allWorkflows); - for (const [module, launcherContent] of Object.entries(this.buildModuleWorkflowLaunchers(groupedWorkflows))) { - artifacts.push({ - type: 'workflow-launcher', - module, - relativePath: path.join(module, 'workflows', 'README.md'), - content: launcherContent, - sourcePath: null, - }); - } - - return { - artifacts, - counts: { - commands: allWorkflows.length, - launchers: Object.keys(groupedWorkflows).length, - }, - }; - } - - /** - * Generate command content for a workflow - */ - async generateCommandContent(workflow, bmadDir) { - // Determine template based on workflow file type - const isMarkdownWorkflow = workflow.path.endsWith('workflow.md'); - const templateName = isMarkdownWorkflow ? 'workflow-commander.md' : 'workflow-command-template.md'; - const templatePath = path.join(path.dirname(this.templatePath), templateName); - - // Load the appropriate template - const template = await fs.readFile(templatePath, 'utf8'); - - // Convert source path to installed path - // From: /Users/.../src/bmm/workflows/.../workflow.yaml - // To: {project-root}/_bmad/bmm/workflows/.../workflow.yaml - let workflowPath = workflow.path; - - // Extract the relative path from source - if (workflowPath.includes('/src/bmm/')) { - // bmm is directly under src/ - const match = workflowPath.match(/\/src\/bmm\/(.+)/); - if (match) { - workflowPath = `${this.bmadFolderName}/bmm/${match[1]}`; - } - } else if (workflowPath.includes('/src/core/')) { - const match = workflowPath.match(/\/src\/core\/(.+)/); - if (match) { - workflowPath = `${this.bmadFolderName}/core/${match[1]}`; - } - } - - // Replace template variables - return template - .replaceAll('{{name}}', workflow.name) - .replaceAll('{{module}}', workflow.module) - .replaceAll('{{description}}', workflow.description) - .replaceAll('{{workflow_path}}', workflowPath) - .replaceAll('_bmad', this.bmadFolderName); - } - - /** - * Create workflow launcher files for each module - */ - async createModuleWorkflowLaunchers(baseCommandsDir, workflowsByModule) { - for (const [module, moduleWorkflows] of Object.entries(workflowsByModule)) { - const content = this.buildLauncherContent(module, moduleWorkflows); - const moduleWorkflowsDir = path.join(baseCommandsDir, module, 'workflows'); - await fs.ensureDir(moduleWorkflowsDir); - const launcherPath = path.join(moduleWorkflowsDir, 'README.md'); - await fs.writeFile(launcherPath, content); - } - } - - groupWorkflowsByModule(workflows) { - const workflowsByModule = {}; - - for (const workflow of workflows) { - if (!workflowsByModule[workflow.module]) { - workflowsByModule[workflow.module] = []; - } - - workflowsByModule[workflow.module].push({ - ...workflow, - displayPath: this.transformWorkflowPath(workflow.path), - }); - } - - return workflowsByModule; - } - - buildModuleWorkflowLaunchers(groupedWorkflows) { - const launchers = {}; - - for (const [module, moduleWorkflows] of Object.entries(groupedWorkflows)) { - launchers[module] = this.buildLauncherContent(module, moduleWorkflows); - } - - return launchers; - } - - buildLauncherContent(module, moduleWorkflows) { - let content = `# ${module.toUpperCase()} Workflows - -## Available Workflows in ${module} - -`; - - for (const workflow of moduleWorkflows) { - content += `**${workflow.name}**\n`; - content += `- Path: \`${workflow.displayPath}\`\n`; - content += `- ${workflow.description}\n\n`; - } - - content += ` -## Execution - -When running any workflow: -1. LOAD {project-root}/${this.bmadFolderName}/core/tasks/workflow.xml -2. Pass the workflow path as 'workflow-config' parameter -3. Follow workflow.xml instructions EXACTLY -4. Save outputs after EACH section - -## Modes -- Normal: Full interaction -- #yolo: Skip optional steps -`; - - return content; - } - - transformWorkflowPath(workflowPath) { - let transformed = workflowPath; - - if (workflowPath.includes('/src/bmm/')) { - const match = workflowPath.match(/\/src\/bmm\/(.+)/); - if (match) { - transformed = `{project-root}/${this.bmadFolderName}/bmm/${match[1]}`; - } - } else if (workflowPath.includes('/src/core/')) { - const match = workflowPath.match(/\/src\/core\/(.+)/); - if (match) { - transformed = `{project-root}/${this.bmadFolderName}/core/${match[1]}`; - } - } - - return transformed; - } - - async loadWorkflowManifest(bmadDir) { - const manifestPath = path.join(bmadDir, '_config', 'workflow-manifest.csv'); - - if (!(await fs.pathExists(manifestPath))) { - return null; - } - - const csvContent = await fs.readFile(manifestPath, 'utf8'); - return csv.parse(csvContent, { - columns: true, - skip_empty_lines: true, - }); - } - - /** - * Write workflow command artifacts using underscore format (Windows-compatible) - * Creates flat files like: bmad_bmm_correct-course.md - * - * @param {string} baseCommandsDir - Base commands directory for the IDE - * @param {Array} artifacts - Workflow artifacts - * @returns {number} Count of commands written - */ - async writeColonArtifacts(baseCommandsDir, artifacts) { - let writtenCount = 0; - - for (const artifact of artifacts) { - if (artifact.type === 'workflow-command') { - // Convert relativePath to underscore format: bmm/workflows/correct-course.md → bmad_bmm_correct-course.md - const flatName = toColonPath(artifact.relativePath); - const commandPath = path.join(baseCommandsDir, flatName); - await fs.ensureDir(path.dirname(commandPath)); - await fs.writeFile(commandPath, artifact.content); - writtenCount++; - } - } - - return writtenCount; - } - - /** - * Write workflow command artifacts using dash format (NEW STANDARD) - * Creates flat files like: bmad-bmm-correct-course.md - * - * Note: Workflows do NOT have bmad-agent- prefix - only agents do. - * - * @param {string} baseCommandsDir - Base commands directory for the IDE - * @param {Array} artifacts - Workflow artifacts - * @returns {number} Count of commands written - */ - async writeDashArtifacts(baseCommandsDir, artifacts) { - let writtenCount = 0; - - for (const artifact of artifacts) { - if (artifact.type === 'workflow-command') { - // Convert relativePath to dash format: bmm/workflows/correct-course.md → bmad-bmm-correct-course.md - const flatName = toDashPath(artifact.relativePath); - const commandPath = path.join(baseCommandsDir, flatName); - await fs.ensureDir(path.dirname(commandPath)); - await fs.writeFile(commandPath, artifact.content); - writtenCount++; - } - } - - return writtenCount; - } -} - -module.exports = { WorkflowCommandGenerator }; diff --git a/tools/cli/installers/lib/ide/templates/agent-command-template.md b/tools/cli/installers/lib/ide/templates/agent-command-template.md deleted file mode 100644 index 0f0c2e20d..000000000 --- a/tools/cli/installers/lib/ide/templates/agent-command-template.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -name: '{{name}}' -description: '{{description}}' ---- - -You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. - - -1. LOAD the FULL agent file from {project-root}/_bmad/{{module}}/agents/{{path}} -2. READ its entire contents - this contains the complete agent persona, menu, and instructions -3. Execute ALL activation steps exactly as written in the agent file -4. Follow the agent's persona and menu system precisely -5. Stay in character throughout the session - diff --git a/tools/cli/installers/lib/ide/templates/combined/antigravity.md b/tools/cli/installers/lib/ide/templates/combined/antigravity.md deleted file mode 100644 index 88e806e9d..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/antigravity.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -name: '{{name}}' -description: '{{description}}' ---- - -Read the entire workflow file at: {project-root}/_bmad/{{workflow_path}} - -Follow all instructions in the workflow file exactly as written. diff --git a/tools/cli/installers/lib/ide/templates/combined/claude-agent.md b/tools/cli/installers/lib/ide/templates/combined/claude-agent.md deleted file mode 120000 index 9f6c17b45..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/claude-agent.md +++ /dev/null @@ -1 +0,0 @@ -default-agent.md \ No newline at end of file diff --git a/tools/cli/installers/lib/ide/templates/combined/claude-workflow-yaml.md b/tools/cli/installers/lib/ide/templates/combined/claude-workflow-yaml.md deleted file mode 120000 index 11f78e1d4..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/claude-workflow-yaml.md +++ /dev/null @@ -1 +0,0 @@ -default-workflow-yaml.md \ No newline at end of file diff --git a/tools/cli/installers/lib/ide/templates/combined/claude-workflow.md b/tools/cli/installers/lib/ide/templates/combined/claude-workflow.md deleted file mode 120000 index 8d4ae5238..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/claude-workflow.md +++ /dev/null @@ -1 +0,0 @@ -default-workflow.md \ No newline at end of file diff --git a/tools/cli/installers/lib/ide/templates/combined/default-agent.md b/tools/cli/installers/lib/ide/templates/combined/default-agent.md deleted file mode 100644 index f8ad93801..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/default-agent.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -name: '{{name}}' -description: '{{description}}' ---- - -You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. - - -1. LOAD the FULL agent file from {project-root}/_bmad/{{path}} -2. READ its entire contents - this contains the complete agent persona, menu, and instructions -3. FOLLOW every step in the section precisely -4. DISPLAY the welcome/greeting as instructed -5. PRESENT the numbered menu -6. WAIT for user input before proceeding - diff --git a/tools/cli/installers/lib/ide/templates/combined/default-task.md b/tools/cli/installers/lib/ide/templates/combined/default-task.md deleted file mode 100644 index b865d6ffb..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/default-task.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -name: '{{name}}' -description: '{{description}}' ---- - -# {{name}} - -Read the entire task file at: {project-root}/{{bmadFolderName}}/{{path}} - -Follow all instructions in the task file exactly as written. diff --git a/tools/cli/installers/lib/ide/templates/combined/default-tool.md b/tools/cli/installers/lib/ide/templates/combined/default-tool.md deleted file mode 100644 index 11c6aac8d..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/default-tool.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -name: '{{name}}' -description: '{{description}}' ---- - -# {{name}} - -Read the entire tool file at: {project-root}/{{bmadFolderName}}/{{path}} - -Follow all instructions in the tool file exactly as written. diff --git a/tools/cli/installers/lib/ide/templates/combined/default-workflow-yaml.md b/tools/cli/installers/lib/ide/templates/combined/default-workflow-yaml.md deleted file mode 100644 index 4a8da26e7..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/default-workflow-yaml.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -name: '{{name}}' -description: '{{description}}' ---- - -IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded: - - -1. Always LOAD the FULL {project-root}/{{bmadFolderName}}/core/tasks/workflow.xml -2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/{{bmadFolderName}}/{{path}} -3. Pass the yaml path {project-root}/{{bmadFolderName}}/{{path}} as 'workflow-config' parameter to the workflow.xml instructions -4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions -5. Save outputs after EACH section when generating any documents from templates - diff --git a/tools/cli/installers/lib/ide/templates/combined/default-workflow.md b/tools/cli/installers/lib/ide/templates/combined/default-workflow.md deleted file mode 100644 index c8ad40459..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/default-workflow.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -name: '{{name}}' -description: '{{description}}' ---- - -IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/{{bmadFolderName}}/{{path}}, READ its entire contents and follow its directions exactly! diff --git a/tools/cli/installers/lib/ide/templates/combined/gemini-agent.toml b/tools/cli/installers/lib/ide/templates/combined/gemini-agent.toml deleted file mode 100644 index ae5f791cf..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/gemini-agent.toml +++ /dev/null @@ -1,14 +0,0 @@ -description = "Activates the {{name}} agent from the BMad Method." -prompt = """ -CRITICAL: You are now the BMad '{{name}}' agent. - -PRE-FLIGHT CHECKLIST: -1. [ ] IMMEDIATE ACTION: Load and parse {project-root}/{{bmadFolderName}}/{{module}}/config.yaml - store ALL config values in memory for use throughout the session. -2. [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/{{bmadFolderName}}/{{path}}. -3. [ ] CONFIRM: The user's name from config is {user_name}. - -Only after all checks are complete, greet the user by name and display the menu. -Acknowledge this checklist is complete in your first response. - -AGENT DEFINITION: {project-root}/{{bmadFolderName}}/{{path}} -""" diff --git a/tools/cli/installers/lib/ide/templates/combined/gemini-task.toml b/tools/cli/installers/lib/ide/templates/combined/gemini-task.toml deleted file mode 100644 index 7d15e2164..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/gemini-task.toml +++ /dev/null @@ -1,11 +0,0 @@ -description = "Executes the {{name}} task from the BMAD Method." -prompt = """ -Execute the BMAD '{{name}}' task. - -TASK INSTRUCTIONS: -1. LOAD the task file from {project-root}/{{bmadFolderName}}/{{path}} -2. READ its entire contents -3. FOLLOW every instruction precisely as specified - -TASK FILE: {project-root}/{{bmadFolderName}}/{{path}} -""" diff --git a/tools/cli/installers/lib/ide/templates/combined/gemini-tool.toml b/tools/cli/installers/lib/ide/templates/combined/gemini-tool.toml deleted file mode 100644 index fc78c6b72..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/gemini-tool.toml +++ /dev/null @@ -1,11 +0,0 @@ -description = "Executes the {{name}} tool from the BMAD Method." -prompt = """ -Execute the BMAD '{{name}}' tool. - -TOOL INSTRUCTIONS: -1. LOAD the tool file from {project-root}/{{bmadFolderName}}/{{path}} -2. READ its entire contents -3. FOLLOW every instruction precisely as specified - -TOOL FILE: {project-root}/{{bmadFolderName}}/{{path}} -""" diff --git a/tools/cli/installers/lib/ide/templates/combined/gemini-workflow-yaml.toml b/tools/cli/installers/lib/ide/templates/combined/gemini-workflow-yaml.toml deleted file mode 100644 index bc6c8da39..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/gemini-workflow-yaml.toml +++ /dev/null @@ -1,16 +0,0 @@ -description = '{{description}}' -prompt = """ -Execute the BMAD '{{name}}' workflow. - -CRITICAL: This is a structured YAML workflow. Follow these steps precisely: - -1. LOAD the workflow definition from {project-root}/{{bmadFolderName}}/{{workflow_path}} -2. PARSE the YAML structure to understand: - - Workflow phases and steps - - Required inputs and outputs - - Dependencies between steps -3. EXECUTE each step in order -4. VALIDATE outputs before proceeding to next step - -WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{workflow_path}} -""" diff --git a/tools/cli/installers/lib/ide/templates/combined/gemini-workflow.toml b/tools/cli/installers/lib/ide/templates/combined/gemini-workflow.toml deleted file mode 100644 index 3306cce04..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/gemini-workflow.toml +++ /dev/null @@ -1,14 +0,0 @@ -description = '{{description}}' -prompt = """ -Execute the BMAD '{{name}}' workflow. - -CRITICAL: You must load and follow the workflow definition exactly. - -WORKFLOW INSTRUCTIONS: -1. LOAD the workflow file from {project-root}/{{bmadFolderName}}/{{workflow_path}} -2. READ its entire contents -3. FOLLOW every step precisely as specified -4. DO NOT skip or modify any steps - -WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{workflow_path}} -""" diff --git a/tools/cli/installers/lib/ide/templates/combined/kiro-agent.md b/tools/cli/installers/lib/ide/templates/combined/kiro-agent.md deleted file mode 100644 index e2c2a83fa..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/kiro-agent.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -inclusion: manual ---- - -# {{name}} - -You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. - - -1. LOAD the FULL agent file from #[[file:{{bmadFolderName}}/{{path}}]] -2. READ its entire contents - this contains the complete agent persona, menu, and instructions -3. FOLLOW every step in the section precisely -4. DISPLAY the welcome/greeting as instructed -5. PRESENT the numbered menu -6. WAIT for user input before proceeding - diff --git a/tools/cli/installers/lib/ide/templates/combined/kiro-task.md b/tools/cli/installers/lib/ide/templates/combined/kiro-task.md deleted file mode 100644 index 8952e5ee2..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/kiro-task.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -inclusion: manual ---- - -# {{name}} - -Read the entire task file at: #[[file:{{bmadFolderName}}/{{path}}]] - -Follow all instructions in the task file exactly as written. diff --git a/tools/cli/installers/lib/ide/templates/combined/kiro-tool.md b/tools/cli/installers/lib/ide/templates/combined/kiro-tool.md deleted file mode 100644 index cd903217a..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/kiro-tool.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -inclusion: manual ---- - -# {{name}} - -Read the entire tool file at: #[[file:{{bmadFolderName}}/{{path}}]] - -Follow all instructions in the tool file exactly as written. diff --git a/tools/cli/installers/lib/ide/templates/combined/kiro-workflow-yaml.md b/tools/cli/installers/lib/ide/templates/combined/kiro-workflow-yaml.md deleted file mode 100644 index 4ee4e0824..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/kiro-workflow-yaml.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -inclusion: manual ---- - -# {{name}} - -IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded: - - -1. Always LOAD the FULL #[[file:{{bmadFolderName}}/core/tasks/workflow.xml]] -2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config #[[file:{{bmadFolderName}}/{{path}}]] -3. Pass the yaml path {{bmadFolderName}}/{{path}} as 'workflow-config' parameter to the workflow.xml instructions -4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions -5. Save outputs after EACH section when generating any documents from templates - diff --git a/tools/cli/installers/lib/ide/templates/combined/kiro-workflow.md b/tools/cli/installers/lib/ide/templates/combined/kiro-workflow.md deleted file mode 100644 index e1847f414..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/kiro-workflow.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -inclusion: manual ---- - -# {{name}} - -IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL #[[file:{{bmadFolderName}}/{{path}}]], READ its entire contents and follow its directions exactly! diff --git a/tools/cli/installers/lib/ide/templates/combined/opencode-agent.md b/tools/cli/installers/lib/ide/templates/combined/opencode-agent.md deleted file mode 100644 index 828d673ac..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/opencode-agent.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -mode: all -description: '{{description}}' ---- - -You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. - - -1. LOAD the FULL agent file from {project-root}/{{bmadFolderName}}/{{path}} -2. READ its entire contents - this contains the complete agent persona, menu, and instructions -3. FOLLOW every step in the section precisely -4. DISPLAY the welcome/greeting as instructed -5. PRESENT the numbered menu -6. WAIT for user input before proceeding - diff --git a/tools/cli/installers/lib/ide/templates/combined/opencode-task.md b/tools/cli/installers/lib/ide/templates/combined/opencode-task.md deleted file mode 100644 index 772f9c9eb..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/opencode-task.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -description: '{{description}}' ---- - -Execute the BMAD '{{name}}' task. - -TASK INSTRUCTIONS: - -1. LOAD the task file from {project-root}/{{bmadFolderName}}/{{path}} -2. READ its entire contents -3. FOLLOW every instruction precisely as specified - -TASK FILE: {project-root}/{{bmadFolderName}}/{{path}} diff --git a/tools/cli/installers/lib/ide/templates/combined/opencode-tool.md b/tools/cli/installers/lib/ide/templates/combined/opencode-tool.md deleted file mode 100644 index 88c317e63..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/opencode-tool.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -description: '{{description}}' ---- - -Execute the BMAD '{{name}}' tool. - -TOOL INSTRUCTIONS: - -1. LOAD the tool file from {project-root}/{{bmadFolderName}}/{{path}} -2. READ its entire contents -3. FOLLOW every instruction precisely as specified - -TOOL FILE: {project-root}/{{bmadFolderName}}/{{path}} diff --git a/tools/cli/installers/lib/ide/templates/combined/opencode-workflow-yaml.md b/tools/cli/installers/lib/ide/templates/combined/opencode-workflow-yaml.md deleted file mode 100644 index 88838cc1c..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/opencode-workflow-yaml.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -description: '{{description}}' ---- - -Execute the BMAD '{{name}}' workflow. - -CRITICAL: You must load and follow the workflow definition exactly. - -WORKFLOW INSTRUCTIONS: - -1. LOAD the workflow file from {project-root}/{{bmadFolderName}}/{{path}} -2. READ its entire contents -3. FOLLOW every step precisely as specified -4. DO NOT skip or modify any steps - -WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{path}} diff --git a/tools/cli/installers/lib/ide/templates/combined/opencode-workflow.md b/tools/cli/installers/lib/ide/templates/combined/opencode-workflow.md deleted file mode 100644 index 88838cc1c..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/opencode-workflow.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -description: '{{description}}' ---- - -Execute the BMAD '{{name}}' workflow. - -CRITICAL: You must load and follow the workflow definition exactly. - -WORKFLOW INSTRUCTIONS: - -1. LOAD the workflow file from {project-root}/{{bmadFolderName}}/{{path}} -2. READ its entire contents -3. FOLLOW every step precisely as specified -4. DO NOT skip or modify any steps - -WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{path}} diff --git a/tools/cli/installers/lib/ide/templates/combined/rovodev.md b/tools/cli/installers/lib/ide/templates/combined/rovodev.md deleted file mode 100644 index 066945ee5..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/rovodev.md +++ /dev/null @@ -1,9 +0,0 @@ -# {{name}} - -{{description}} - ---- - -Read the entire workflow file at: {project-root}/_bmad/{{workflow_path}} - -Follow all instructions in the workflow file exactly as written. diff --git a/tools/cli/installers/lib/ide/templates/combined/trae.md b/tools/cli/installers/lib/ide/templates/combined/trae.md deleted file mode 100644 index b4d43d7af..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/trae.md +++ /dev/null @@ -1,9 +0,0 @@ -# {{name}} - -{{description}} - -## Instructions - -Read the entire workflow file at: {project-root}/_bmad/{{workflow_path}} - -Follow all instructions in the workflow file exactly as written. diff --git a/tools/cli/installers/lib/ide/templates/combined/windsurf-workflow.md b/tools/cli/installers/lib/ide/templates/combined/windsurf-workflow.md deleted file mode 100644 index 6366425c7..000000000 --- a/tools/cli/installers/lib/ide/templates/combined/windsurf-workflow.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -description: '{{description}}' -auto_execution_mode: "iterate" ---- - -# {{name}} - -Read the entire workflow file at {project-root}/_bmad/{{workflow_path}} - -Follow all instructions in the workflow file exactly as written. diff --git a/tools/cli/installers/lib/ide/templates/split/.gitkeep b/tools/cli/installers/lib/ide/templates/split/.gitkeep deleted file mode 100644 index e69de29bb..000000000 diff --git a/tools/cli/installers/lib/ide/templates/workflow-command-template.md b/tools/cli/installers/lib/ide/templates/workflow-command-template.md deleted file mode 100644 index 328983c9e..000000000 --- a/tools/cli/installers/lib/ide/templates/workflow-command-template.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -description: '{{description}}' ---- - -IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded: - - -1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml -2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/{{workflow_path}} -3. Pass the yaml path {{workflow_path}} as 'workflow-config' parameter to the workflow.xml instructions -4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions -5. Save outputs after EACH section when generating any documents from templates - diff --git a/tools/cli/installers/lib/ide/templates/workflow-commander.md b/tools/cli/installers/lib/ide/templates/workflow-commander.md deleted file mode 100644 index 66eee15d1..000000000 --- a/tools/cli/installers/lib/ide/templates/workflow-commander.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -description: '{{description}}' ---- - -IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/{{workflow_path}}, READ its entire contents and follow its directions exactly! diff --git a/tools/cli/installers/lib/message-loader.js b/tools/cli/installers/lib/message-loader.js deleted file mode 100644 index 7198f0328..000000000 --- a/tools/cli/installers/lib/message-loader.js +++ /dev/null @@ -1,83 +0,0 @@ -const fs = require('fs-extra'); -const path = require('node:path'); -const yaml = require('yaml'); -const prompts = require('../../lib/prompts'); - -/** - * Load and display installer messages from messages.yaml - */ -class MessageLoader { - constructor() {} - - /** - * Load messages from the YAML file - * @returns {Object|null} Messages object or null if not found - */ - load() { - if (this.messages) { - return this.messages; - } - - const messagesPath = path.join(__dirname, '..', 'install-messages.yaml'); - - try { - const content = fs.readFileSync(messagesPath, 'utf8'); - this.messages = yaml.parse(content); - return this.messages; - } catch { - // File doesn't exist or is invalid - return null - return null; - } - } - - /** - * Get the start message for display - * @returns {string|null} Start message or null - */ - getStartMessage() { - const messages = this.load(); - return messages?.startMessage || null; - } - - /** - * Get the end message for display - * @returns {string|null} End message or null - */ - getEndMessage() { - const messages = this.load(); - return messages?.endMessage || null; - } - - /** - * Display the start message (after logo, before prompts) - */ - async displayStartMessage() { - const message = this.getStartMessage(); - if (message) { - await prompts.log.info(message); - } - } - - /** - * Display the end message (after installation completes) - */ - async displayEndMessage() { - const message = this.getEndMessage(); - if (message) { - await prompts.log.info(message); - } - } - - /** - * Check if messages exist for the current version - * @param {string} currentVersion - Current package version - * @returns {boolean} True if messages match current version - */ - isCurrent(currentVersion) { - const messages = this.load(); - return messages && messages.version === currentVersion; - } - messages = null; -} - -module.exports = { MessageLoader }; diff --git a/tools/cli/installers/lib/modules/external-manager.js b/tools/cli/installers/lib/modules/external-manager.js deleted file mode 100644 index f1ea2206e..000000000 --- a/tools/cli/installers/lib/modules/external-manager.js +++ /dev/null @@ -1,136 +0,0 @@ -const fs = require('fs-extra'); -const path = require('node:path'); -const yaml = require('yaml'); -const prompts = require('../../../lib/prompts'); - -/** - * Manages external official modules defined in external-official-modules.yaml - * These are modules hosted in external repositories that can be installed - * - * @class ExternalModuleManager - */ -class ExternalModuleManager { - constructor() { - this.externalModulesConfigPath = path.join(__dirname, '../../../external-official-modules.yaml'); - this.cachedModules = null; - } - - /** - * Load and parse the external-official-modules.yaml file - * @returns {Object} Parsed YAML content with modules object - */ - async loadExternalModulesConfig() { - if (this.cachedModules) { - return this.cachedModules; - } - - try { - const content = await fs.readFile(this.externalModulesConfigPath, 'utf8'); - const config = yaml.parse(content); - this.cachedModules = config; - return config; - } catch (error) { - await prompts.log.warn(`Failed to load external modules config: ${error.message}`); - return { modules: {} }; - } - } - - /** - * Get list of available external modules - * @returns {Array} Array of module info objects - */ - async listAvailable() { - const config = await this.loadExternalModulesConfig(); - const modules = []; - - for (const [key, moduleConfig] of Object.entries(config.modules || {})) { - modules.push({ - key, - url: moduleConfig.url, - moduleDefinition: moduleConfig['module-definition'], - code: moduleConfig.code, - name: moduleConfig.name, - header: moduleConfig.header, - subheader: moduleConfig.subheader, - description: moduleConfig.description || '', - defaultSelected: moduleConfig.defaultSelected === true, - type: moduleConfig.type || 'community', // bmad-org or community - npmPackage: moduleConfig.npmPackage || null, // Include npm package name - isExternal: true, - }); - } - - return modules; - } - - /** - * Get module info by code - * @param {string} code - The module code (e.g., 'cis') - * @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; - } - - /** - * Get module info by key - * @param {string} key - The module key (e.g., 'bmad-creative-intelligence-suite') - * @returns {Object|null} Module info or null if not found - */ - async getModuleByKey(key) { - const config = await this.loadExternalModulesConfig(); - const moduleConfig = config.modules?.[key]; - - if (!moduleConfig) { - return null; - } - - return { - key, - url: moduleConfig.url, - moduleDefinition: moduleConfig['module-definition'], - code: moduleConfig.code, - name: moduleConfig.name, - header: moduleConfig.header, - subheader: moduleConfig.subheader, - description: moduleConfig.description || '', - defaultSelected: moduleConfig.defaultSelected === true, - type: moduleConfig.type || 'community', // bmad-org or community - npmPackage: moduleConfig.npmPackage || null, // Include npm package name - isExternal: true, - }; - } - - /** - * Check if a module code exists in external modules - * @param {string} code - The module code to check - * @returns {boolean} True if the module exists - */ - async hasModule(code) { - const module = await this.getModuleByCode(code); - return module !== null; - } - - /** - * Get the URL for a module by code - * @param {string} code - The module code - * @returns {string|null} The URL or null if not found - */ - async getModuleUrl(code) { - const module = await this.getModuleByCode(code); - return module ? module.url : null; - } - - /** - * Get the module definition path for a module by code - * @param {string} code - The module code - * @returns {string|null} The module definition path or null if not found - */ - async getModuleDefinition(code) { - const module = await this.getModuleByCode(code); - return module ? module.moduleDefinition : null; - } -} - -module.exports = { ExternalModuleManager }; diff --git a/tools/cli/installers/lib/modules/manager.js b/tools/cli/installers/lib/modules/manager.js deleted file mode 100644 index f162593b7..000000000 --- a/tools/cli/installers/lib/modules/manager.js +++ /dev/null @@ -1,1498 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const yaml = require('yaml'); -const prompts = require('../../../lib/prompts'); -const { XmlHandler } = require('../../../lib/xml-handler'); -const { getProjectRoot, getSourcePath, getModulePath } = require('../../../lib/project-root'); -const { filterCustomizationData } = require('../../../lib/agent/compiler'); -const { ExternalModuleManager } = require('./external-manager'); -const { BMAD_FOLDER_NAME } = require('../ide/shared/path-utils'); - -/** - * Manages the installation, updating, and removal of BMAD modules. - * Handles module discovery, dependency resolution, configuration processing, - * and agent file management including XML activation block injection. - * - * @class ModuleManager - * @requires fs-extra - * @requires yaml - * @requires prompts - * @requires XmlHandler - * - * @example - * const manager = new ModuleManager(); - * const modules = await manager.listAvailable(); - * await manager.install('core-module', '/path/to/bmad'); - */ -class ModuleManager { - constructor(options = {}) { - this.xmlHandler = new XmlHandler(); - this.bmadFolderName = BMAD_FOLDER_NAME; // Default, can be overridden - this.customModulePaths = new Map(); // Initialize custom module paths - this.externalModuleManager = new ExternalModuleManager(); // For external official modules - } - - /** - * Set the bmad folder name for placeholder replacement - * @param {string} bmadFolderName - The bmad folder name - */ - setBmadFolderName(bmadFolderName) { - this.bmadFolderName = bmadFolderName; - } - - /** - * Set the core configuration for access during module installation - * @param {Object} coreConfig - Core configuration object - */ - setCoreConfig(coreConfig) { - this.coreConfig = coreConfig; - } - - /** - * Set custom module paths for priority lookup - * @param {Map} customModulePaths - Map of module ID to source path - */ - setCustomModulePaths(customModulePaths) { - this.customModulePaths = customModulePaths; - } - - /** - * Copy a file to the target location - * @param {string} sourcePath - Source file path - * @param {string} targetPath - Target file path - * @param {boolean} overwrite - Whether to overwrite existing files (default: true) - */ - async copyFileWithPlaceholderReplacement(sourcePath, targetPath, overwrite = true) { - await fs.copy(sourcePath, targetPath, { overwrite }); - } - - /** - * Copy a directory recursively - * @param {string} sourceDir - Source directory path - * @param {string} targetDir - Target directory path - * @param {boolean} overwrite - Whether to overwrite existing files (default: true) - */ - async copyDirectoryWithPlaceholderReplacement(sourceDir, targetDir, overwrite = true) { - await fs.ensureDir(targetDir); - const entries = await fs.readdir(sourceDir, { withFileTypes: true }); - - for (const entry of entries) { - const sourcePath = path.join(sourceDir, entry.name); - const targetPath = path.join(targetDir, entry.name); - - if (entry.isDirectory()) { - await this.copyDirectoryWithPlaceholderReplacement(sourcePath, targetPath, overwrite); - } else { - await this.copyFileWithPlaceholderReplacement(sourcePath, targetPath, overwrite); - } - } - } - - /** - * Copy sidecar directory to _bmad/_memory location with update-safe handling - * @param {string} sourceSidecarPath - Source sidecar directory path - * @param {string} agentName - Name of the agent (for naming) - * @param {string} bmadMemoryPath - This should ALWAYS be _bmad/_memory - * @param {boolean} isUpdate - Whether this is an update (default: false) - * @param {string} bmadDir - BMAD installation directory - * @param {Object} installer - Installer instance for file tracking - */ - async copySidecarToMemory(sourceSidecarPath, agentName, bmadMemoryPath, isUpdate = false, bmadDir = null, installer = null) { - const crypto = require('node:crypto'); - const sidecarTargetDir = path.join(bmadMemoryPath, `${agentName}-sidecar`); - - // Ensure target directory exists - await fs.ensureDir(bmadMemoryPath); - await fs.ensureDir(sidecarTargetDir); - - // Get existing files manifest for update checking - let existingFilesManifest = []; - if (isUpdate && installer) { - existingFilesManifest = await installer.readFilesManifest(bmadDir); - } - - // Build map of existing sidecar files with their hashes - const existingSidecarFiles = new Map(); - for (const fileEntry of existingFilesManifest) { - if (fileEntry.path && fileEntry.path.includes(`${agentName}-sidecar/`)) { - existingSidecarFiles.set(fileEntry.path, fileEntry.hash); - } - } - - // Get all files in source sidecar - const sourceFiles = await this.getFileList(sourceSidecarPath); - - for (const file of sourceFiles) { - const sourceFilePath = path.join(sourceSidecarPath, file); - const targetFilePath = path.join(sidecarTargetDir, file); - - // Calculate current source file hash - const sourceHash = crypto - .createHash('sha256') - .update(await fs.readFile(sourceFilePath)) - .digest('hex'); - - // Path relative to bmad directory - const relativeToBmad = path.join('_memory', `${agentName}-sidecar`, file); - - if (isUpdate && (await fs.pathExists(targetFilePath))) { - // Calculate current target file hash - const currentTargetHash = crypto - .createHash('sha256') - .update(await fs.readFile(targetFilePath)) - .digest('hex'); - - // Get the last known hash from files-manifest - const lastKnownHash = existingSidecarFiles.get(relativeToBmad); - - if (lastKnownHash) { - // We have a record of this file - if (currentTargetHash === lastKnownHash) { - // File hasn't been modified by user, safe to update - await this.copyFileWithPlaceholderReplacement(sourceFilePath, targetFilePath, true); - if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.message(` Updated sidecar file: ${relativeToBmad}`); - } - } else { - // User has modified the file, preserve it - if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.message(` Preserving user-modified file: ${relativeToBmad}`); - } - } - } else { - // First time seeing this file in manifest, copy it - await this.copyFileWithPlaceholderReplacement(sourceFilePath, targetFilePath, true); - if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.message(` Added new sidecar file: ${relativeToBmad}`); - } - } - } else { - // New installation - await this.copyFileWithPlaceholderReplacement(sourceFilePath, targetFilePath, true); - if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.message(` Copied sidecar file: ${relativeToBmad}`); - } - } - - // Track the file in the installer's file tracking system - if (installer && installer.installedFiles) { - installer.installedFiles.add(targetFilePath); - } - } - - // Return list of files that were processed - const processedFiles = sourceFiles.map((file) => path.join('_memory', `${agentName}-sidecar`, file)); - return processedFiles; - } - - /** - * List all available modules (excluding core which is always installed) - * bmm is the only built-in module, directly under src/bmm - * All other modules come from external-official-modules.yaml - * @returns {Object} Object with modules array and customModules array - */ - async listAvailable() { - const modules = []; - const customModules = []; - - // Add built-in bmm module (directly under src/bmm) - const bmmPath = getSourcePath('bmm'); - if (await fs.pathExists(bmmPath)) { - const bmmInfo = await this.getModuleInfo(bmmPath, 'bmm', 'src/bmm'); - if (bmmInfo) { - modules.push(bmmInfo); - } - } - - // Check for cached custom modules in _config/custom/ - if (this.bmadDir) { - const customCacheDir = path.join(this.bmadDir, '_config', 'custom'); - if (await fs.pathExists(customCacheDir)) { - const cacheEntries = await fs.readdir(customCacheDir, { withFileTypes: true }); - for (const entry of cacheEntries) { - if (entry.isDirectory()) { - const cachePath = path.join(customCacheDir, entry.name); - const moduleInfo = await this.getModuleInfo(cachePath, entry.name, '_config/custom'); - if (moduleInfo && !modules.some((m) => m.id === moduleInfo.id) && !customModules.some((m) => m.id === moduleInfo.id)) { - moduleInfo.isCustom = true; - moduleInfo.fromCache = true; - customModules.push(moduleInfo); - } - } - } - } - } - - return { modules, customModules }; - } - - /** - * Get module information from a module path - * @param {string} modulePath - Path to the module directory - * @param {string} defaultName - Default name for the module - * @param {string} sourceDescription - Description of where the module was found - * @returns {Object|null} Module info or null if not a valid module - */ - async getModuleInfo(modulePath, defaultName, sourceDescription) { - // Check for module structure (module.yaml OR custom.yaml) - const moduleConfigPath = path.join(modulePath, 'module.yaml'); - const rootCustomConfigPath = path.join(modulePath, 'custom.yaml'); - let configPath = null; - - if (await fs.pathExists(moduleConfigPath)) { - configPath = moduleConfigPath; - } else if (await fs.pathExists(rootCustomConfigPath)) { - configPath = rootCustomConfigPath; - } - - // Skip if this doesn't look like a module - if (!configPath) { - return null; - } - - // Mark as custom if it's using custom.yaml OR if it's outside src/bmm or src/core - const isCustomSource = sourceDescription !== 'src/bmm' && sourceDescription !== 'src/core' && sourceDescription !== 'src/modules'; - const moduleInfo = { - id: defaultName, - path: modulePath, - name: defaultName - .split('-') - .map((word) => word.charAt(0).toUpperCase() + word.slice(1)) - .join(' '), - description: 'BMAD Module', - version: '5.0.0', - source: sourceDescription, - isCustom: configPath === rootCustomConfigPath || isCustomSource, - }; - - // Read module config for metadata - try { - const configContent = await fs.readFile(configPath, 'utf8'); - const config = yaml.parse(configContent); - - // Use the code property as the id if available - if (config.code) { - moduleInfo.id = config.code; - } - - moduleInfo.name = config.name || moduleInfo.name; - moduleInfo.description = config.description || moduleInfo.description; - moduleInfo.version = config.version || moduleInfo.version; - moduleInfo.dependencies = config.dependencies || []; - moduleInfo.defaultSelected = config.default_selected === undefined ? false : config.default_selected; - } catch (error) { - await prompts.log.warn(`Failed to read config for ${defaultName}: ${error.message}`); - } - - return moduleInfo; - } - - /** - * Find the source path for a module by searching all possible locations - * @param {string} moduleCode - Code of the module to find (from module.yaml) - * @returns {string|null} Path to the module source or null if not found - */ - async findModuleSource(moduleCode, options = {}) { - const projectRoot = getProjectRoot(); - - // First check custom module paths if they exist - if (this.customModulePaths && this.customModulePaths.has(moduleCode)) { - return this.customModulePaths.get(moduleCode); - } - - // Check for built-in bmm module (directly under src/bmm) - if (moduleCode === 'bmm') { - const bmmPath = getSourcePath('bmm'); - if (await fs.pathExists(bmmPath)) { - return bmmPath; - } - } - - // Check external official modules - const externalSource = await this.findExternalModuleSource(moduleCode, options); - if (externalSource) { - return externalSource; - } - - return null; - } - - /** - * Check if a module is an external official module - * @param {string} moduleCode - Code of the module to check - * @returns {boolean} True if the module is external - */ - async isExternalModule(moduleCode) { - return await this.externalModuleManager.hasModule(moduleCode); - } - - /** - * Get the cache directory for external modules - * @returns {string} Path to the external modules cache directory - */ - getExternalCacheDir() { - const os = require('node:os'); - const cacheDir = path.join(os.homedir(), '.bmad', 'cache', 'external-modules'); - return cacheDir; - } - - /** - * Clone an external module repository to cache - * @param {string} moduleCode - Code of the external module - * @returns {string} Path to the cloned repository - */ - async cloneExternalModule(moduleCode, options = {}) { - const { execSync } = require('node:child_process'); - const moduleInfo = await this.externalModuleManager.getModuleByCode(moduleCode); - - if (!moduleInfo) { - throw new Error(`External module '${moduleCode}' not found in external-official-modules.yaml`); - } - - const cacheDir = this.getExternalCacheDir(); - const moduleCacheDir = path.join(cacheDir, moduleCode); - const silent = options.silent || false; - - // Create cache directory if it doesn't exist - await fs.ensureDir(cacheDir); - - // Helper to create a spinner or a no-op when silent - const createSpinner = async () => { - if (silent) { - return { - start() {}, - stop() {}, - error() {}, - message() {}, - cancel() {}, - clear() {}, - get isSpinning() { - return false; - }, - get isCancelled() { - return false; - }, - }; - } - return await prompts.spinner(); - }; - - // Track if we need to install dependencies - let needsDependencyInstall = false; - let wasNewClone = false; - - // Check if already cloned - if (await fs.pathExists(moduleCacheDir)) { - // Try to update if it's a git repo - const fetchSpinner = await createSpinner(); - fetchSpinner.start(`Fetching ${moduleInfo.name}...`); - try { - const currentRef = execSync('git rev-parse HEAD', { cwd: moduleCacheDir, stdio: 'pipe' }).toString().trim(); - // Fetch and reset to remote - works better with shallow clones than pull - execSync('git fetch origin --depth 1', { - cwd: moduleCacheDir, - stdio: ['ignore', 'pipe', 'pipe'], - env: { ...process.env, GIT_TERMINAL_PROMPT: '0' }, - }); - execSync('git reset --hard origin/HEAD', { - cwd: moduleCacheDir, - stdio: ['ignore', 'pipe', 'pipe'], - env: { ...process.env, GIT_TERMINAL_PROMPT: '0' }, - }); - const newRef = execSync('git rev-parse HEAD', { cwd: moduleCacheDir, stdio: 'pipe' }).toString().trim(); - - fetchSpinner.stop(`Fetched ${moduleInfo.name}`); - // Force dependency install if we got new code - if (currentRef !== newRef) { - needsDependencyInstall = true; - } - } catch { - fetchSpinner.error(`Fetch failed, re-downloading ${moduleInfo.name}`); - // If update fails, remove and re-clone - await fs.remove(moduleCacheDir); - wasNewClone = true; - } - } else { - wasNewClone = true; - } - - // Clone if not exists or was removed - if (wasNewClone) { - const fetchSpinner = await createSpinner(); - fetchSpinner.start(`Fetching ${moduleInfo.name}...`); - try { - execSync(`git clone --depth 1 "${moduleInfo.url}" "${moduleCacheDir}"`, { - stdio: ['ignore', 'pipe', 'pipe'], - env: { ...process.env, GIT_TERMINAL_PROMPT: '0' }, - }); - fetchSpinner.stop(`Fetched ${moduleInfo.name}`); - } catch (error) { - fetchSpinner.error(`Failed to fetch ${moduleInfo.name}`); - throw new Error(`Failed to clone external module '${moduleCode}': ${error.message}`); - } - } - - // Install dependencies if package.json exists - const packageJsonPath = path.join(moduleCacheDir, 'package.json'); - const nodeModulesPath = path.join(moduleCacheDir, 'node_modules'); - if (await fs.pathExists(packageJsonPath)) { - // Install if node_modules doesn't exist, or if package.json is newer (dependencies changed) - const nodeModulesMissing = !(await fs.pathExists(nodeModulesPath)); - - // Force install if we updated or cloned new - if (needsDependencyInstall || wasNewClone || nodeModulesMissing) { - const installSpinner = await createSpinner(); - installSpinner.start(`Installing dependencies for ${moduleInfo.name}...`); - try { - execSync('npm install --omit=dev --no-audit --no-fund --no-progress --legacy-peer-deps', { - cwd: moduleCacheDir, - stdio: ['ignore', 'pipe', 'pipe'], - timeout: 120_000, // 2 minute timeout - }); - installSpinner.stop(`Installed dependencies for ${moduleInfo.name}`); - } catch (error) { - installSpinner.error(`Failed to install dependencies for ${moduleInfo.name}`); - if (!silent) await prompts.log.warn(` ${error.message}`); - } - } else { - // Check if package.json is newer than node_modules - let packageJsonNewer = false; - try { - const packageStats = await fs.stat(packageJsonPath); - const nodeModulesStats = await fs.stat(nodeModulesPath); - packageJsonNewer = packageStats.mtime > nodeModulesStats.mtime; - } catch { - // If stat fails, assume we need to install - packageJsonNewer = true; - } - - if (packageJsonNewer) { - const installSpinner = await createSpinner(); - installSpinner.start(`Installing dependencies for ${moduleInfo.name}...`); - try { - execSync('npm install --omit=dev --no-audit --no-fund --no-progress --legacy-peer-deps', { - cwd: moduleCacheDir, - stdio: ['ignore', 'pipe', 'pipe'], - timeout: 120_000, // 2 minute timeout - }); - installSpinner.stop(`Installed dependencies for ${moduleInfo.name}`); - } catch (error) { - installSpinner.error(`Failed to install dependencies for ${moduleInfo.name}`); - if (!silent) await prompts.log.warn(` ${error.message}`); - } - } - } - } - - return moduleCacheDir; - } - - /** - * Find the source path for an external module - * @param {string} moduleCode - Code of the external module - * @returns {string|null} Path to the module source or null if not found - */ - async findExternalModuleSource(moduleCode, options = {}) { - const moduleInfo = await this.externalModuleManager.getModuleByCode(moduleCode); - - if (!moduleInfo) { - return null; - } - - // Clone the external module repo - const cloneDir = await this.cloneExternalModule(moduleCode, options); - - // The module-definition specifies the path to module.yaml relative to repo root - // We need to return the directory containing module.yaml - const moduleDefinitionPath = moduleInfo.moduleDefinition; // e.g., 'src/module.yaml' - const moduleDir = path.dirname(path.join(cloneDir, moduleDefinitionPath)); - - return moduleDir; - } - - /** - * Install a module - * @param {string} moduleName - Code of the module to install (from module.yaml) - * @param {string} bmadDir - Target bmad directory - * @param {Function} fileTrackingCallback - Optional callback to track installed files - * @param {Object} options - Additional installation options - * @param {Array} options.installedIDEs - Array of IDE codes that were installed - * @param {Object} options.moduleConfig - Module configuration from config collector - * @param {Object} options.logger - Logger instance for output - */ - async install(moduleName, bmadDir, fileTrackingCallback = null, options = {}) { - const sourcePath = await this.findModuleSource(moduleName, { silent: options.silent }); - const targetPath = path.join(bmadDir, moduleName); - - // Check if source module exists - if (!sourcePath) { - // Provide a more user-friendly error message - throw new Error( - `Source for module '${moduleName}' is not available. It will be retained but cannot be updated without its source files.`, - ); - } - - // Check if this is a custom module and read its custom.yaml values - let customConfig = null; - const rootCustomConfigPath = path.join(sourcePath, 'custom.yaml'); - - if (await fs.pathExists(rootCustomConfigPath)) { - try { - const customContent = await fs.readFile(rootCustomConfigPath, 'utf8'); - customConfig = yaml.parse(customContent); - } catch (error) { - await prompts.log.warn(`Failed to read custom.yaml for ${moduleName}: ${error.message}`); - } - } - - // If this is a custom module, merge its values into the module config - if (customConfig) { - options.moduleConfig = { ...options.moduleConfig, ...customConfig }; - if (options.logger) { - await options.logger.log(` Merged custom configuration for ${moduleName}`); - } - } - - // Check if already installed - if (await fs.pathExists(targetPath)) { - await fs.remove(targetPath); - } - - // Vendor cross-module workflows BEFORE copying - // This reads source agent.yaml files and copies referenced workflows - await this.vendorCrossModuleWorkflows(sourcePath, targetPath, moduleName); - - // Copy module files with filtering - await this.copyModuleWithFiltering(sourcePath, targetPath, fileTrackingCallback, options.moduleConfig); - - // Compile any .agent.yaml files to .md format - await this.compileModuleAgents(sourcePath, targetPath, moduleName, bmadDir, options.installer); - - // Process agent files to inject activation block - await this.processAgentFiles(targetPath, moduleName); - - // Create directories declared in module.yaml (unless explicitly skipped) - if (!options.skipModuleInstaller) { - await this.createModuleDirectories(moduleName, bmadDir, options); - } - - // Capture version info for manifest - const { Manifest } = require('../core/manifest'); - const manifestObj = new Manifest(); - const versionInfo = await manifestObj.getModuleVersionInfo(moduleName, bmadDir, sourcePath); - - await manifestObj.addModule(bmadDir, moduleName, { - version: versionInfo.version, - source: versionInfo.source, - npmPackage: versionInfo.npmPackage, - repoUrl: versionInfo.repoUrl, - }); - - return { - success: true, - module: moduleName, - path: targetPath, - versionInfo, - }; - } - - /** - * Update an existing module - * @param {string} moduleName - Name of the module to update - * @param {string} bmadDir - Target bmad directory - * @param {boolean} force - Force update (overwrite modifications) - */ - async update(moduleName, bmadDir, force = false, options = {}) { - const sourcePath = await this.findModuleSource(moduleName); - const targetPath = path.join(bmadDir, moduleName); - - // Check if source module exists - if (!sourcePath) { - throw new Error(`Module '${moduleName}' not found in any source location`); - } - - // Check if module is installed - if (!(await fs.pathExists(targetPath))) { - throw new Error(`Module '${moduleName}' is not installed`); - } - - if (force) { - // Force update - remove and reinstall - await fs.remove(targetPath); - return await this.install(moduleName, bmadDir, null, { installer: options.installer }); - } else { - // Selective update - preserve user modifications - await this.syncModule(sourcePath, targetPath); - - // Recompile agents (#1133) - await this.compileModuleAgents(sourcePath, targetPath, moduleName, bmadDir, options.installer); - await this.processAgentFiles(targetPath, moduleName); - } - - return { - success: true, - module: moduleName, - path: targetPath, - }; - } - - /** - * Remove a module - * @param {string} moduleName - Name of the module to remove - * @param {string} bmadDir - Target bmad directory - */ - async remove(moduleName, bmadDir) { - const targetPath = path.join(bmadDir, moduleName); - - if (!(await fs.pathExists(targetPath))) { - throw new Error(`Module '${moduleName}' is not installed`); - } - - await fs.remove(targetPath); - - return { - success: true, - module: moduleName, - }; - } - - /** - * Check if a module is installed - * @param {string} moduleName - Name of the module - * @param {string} bmadDir - Target bmad directory - * @returns {boolean} True if module is installed - */ - async isInstalled(moduleName, bmadDir) { - const targetPath = path.join(bmadDir, moduleName); - return await fs.pathExists(targetPath); - } - - /** - * Get installed module info - * @param {string} moduleName - Name of the module - * @param {string} bmadDir - Target bmad directory - * @returns {Object|null} Module info or null if not installed - */ - async getInstalledInfo(moduleName, bmadDir) { - const targetPath = path.join(bmadDir, moduleName); - - if (!(await fs.pathExists(targetPath))) { - return null; - } - - const configPath = path.join(targetPath, 'config.yaml'); - const moduleInfo = { - id: moduleName, - path: targetPath, - installed: true, - }; - - if (await fs.pathExists(configPath)) { - try { - const configContent = await fs.readFile(configPath, 'utf8'); - const config = yaml.parse(configContent); - Object.assign(moduleInfo, config); - } catch (error) { - await prompts.log.warn(`Failed to read installed module config: ${error.message}`); - } - } - - return moduleInfo; - } - - /** - * Copy module with filtering for localskip agents and conditional content - * @param {string} sourcePath - Source module path - * @param {string} targetPath - Target module path - * @param {Function} fileTrackingCallback - Optional callback to track installed files - * @param {Object} moduleConfig - Module configuration with conditional flags - */ - async copyModuleWithFiltering(sourcePath, targetPath, fileTrackingCallback = null, moduleConfig = {}) { - // Get all files in source - const sourceFiles = await this.getFileList(sourcePath); - - for (const file of sourceFiles) { - // Skip sub-modules directory - these are IDE-specific and handled separately - if (file.startsWith('sub-modules/')) { - continue; - } - - // Only skip sidecar directories - they are handled separately during agent compilation - // But still allow other files in agent directories - const isInAgentDirectory = file.startsWith('agents/'); - const isInSidecarDirectory = path - .dirname(file) - .split('/') - .some((dir) => dir.toLowerCase().endsWith('-sidecar')); - - if (isInSidecarDirectory) { - continue; - } - - // Skip module.yaml at root - it's only needed at install time - if (file === 'module.yaml') { - continue; - } - - // Skip module root config.yaml only - generated by config collector with actual values - // Workflow-level config.yaml (e.g. workflows/orchestrate-story/config.yaml) must be copied - // for custom modules that use workflow-specific configuration - if (file === 'config.yaml') { - continue; - } - - // Skip .agent.yaml files - they will be compiled separately - if (file.endsWith('.agent.yaml')) { - continue; - } - - const sourceFile = path.join(sourcePath, file); - const targetFile = path.join(targetPath, file); - - // Check if this is an agent file - if (file.startsWith('agents/') && file.endsWith('.md')) { - // Read the file to check for localskip - const content = await fs.readFile(sourceFile, 'utf8'); - - // Check for localskip="true" in the agent tag - const agentMatch = content.match(/]*\slocalskip="true"[^>]*>/); - if (agentMatch) { - await prompts.log.message(` Skipping web-only agent: ${path.basename(file)}`); - continue; // Skip this agent - } - } - - // Check if this is a workflow.yaml file - if (file.endsWith('workflow.yaml')) { - await fs.ensureDir(path.dirname(targetFile)); - await this.copyWorkflowYamlStripped(sourceFile, targetFile); - } else { - // Copy the file with placeholder replacement - await this.copyFileWithPlaceholderReplacement(sourceFile, targetFile); - } - - // Track the file if callback provided - if (fileTrackingCallback) { - fileTrackingCallback(targetFile); - } - } - } - - /** - * Copy workflow.yaml file with web_bundle section stripped - * Preserves comments, formatting, and line breaks - * @param {string} sourceFile - Source workflow.yaml file path - * @param {string} targetFile - Target workflow.yaml file path - */ - async copyWorkflowYamlStripped(sourceFile, targetFile) { - // Read the source YAML file - let yamlContent = await fs.readFile(sourceFile, 'utf8'); - - // IMPORTANT: Replace escape sequence and placeholder BEFORE parsing YAML - // Otherwise parsing will fail on the placeholder - yamlContent = yamlContent.replaceAll('_bmad', this.bmadFolderName); - - try { - // First check if web_bundle exists by parsing - const workflowConfig = yaml.parse(yamlContent); - - if (workflowConfig.web_bundle === undefined) { - // No web_bundle section, just write (placeholders already replaced above) - await fs.writeFile(targetFile, yamlContent, 'utf8'); - return; - } - - // Find the line that starts web_bundle - const lines = yamlContent.split('\n'); - let startIdx = -1; - let endIdx = -1; - let baseIndent = 0; - - // Find the start of web_bundle section - for (const [i, line] of lines.entries()) { - const match = line.match(/^(\s*)web_bundle:/); - if (match) { - startIdx = i; - baseIndent = match[1].length; - break; - } - } - - if (startIdx === -1) { - // web_bundle not found in text (shouldn't happen), copy as-is - await fs.writeFile(targetFile, yamlContent, 'utf8'); - return; - } - - // Find the end of web_bundle section - // It ends when we find a line with same or less indentation that's not empty/comment - endIdx = startIdx; - for (let i = startIdx + 1; i < lines.length; i++) { - const line = lines[i]; - - // Skip empty lines and comments - if (line.trim() === '' || line.trim().startsWith('#')) { - continue; - } - - // Check indentation - const indent = line.match(/^(\s*)/)[1].length; - if (indent <= baseIndent) { - // Found next section at same or lower indentation - endIdx = i - 1; - break; - } - } - - // If we didn't find an end, it goes to end of file - if (endIdx === startIdx) { - endIdx = lines.length - 1; - } - - // Remove the web_bundle section (including the line before if it's just a blank line) - const newLines = [...lines.slice(0, startIdx), ...lines.slice(endIdx + 1)]; - - // Clean up any double blank lines that might result - const strippedYaml = newLines.join('\n').replaceAll(/\n\n\n+/g, '\n\n'); - - // Placeholders already replaced at the beginning of this function - await fs.writeFile(targetFile, strippedYaml, 'utf8'); - } catch { - // If anything fails, just copy the file as-is - await prompts.log.warn(` Could not process ${path.basename(sourceFile)}, copying as-is`); - await fs.copy(sourceFile, targetFile, { overwrite: true }); - } - } - - /** - * Compile .agent.yaml files to .md format in modules - * @param {string} sourcePath - Source module path - * @param {string} targetPath - Target module path - * @param {string} moduleName - Module name - * @param {string} bmadDir - BMAD installation directory - * @param {Object} installer - Installer instance for file tracking - */ - async compileModuleAgents(sourcePath, targetPath, moduleName, bmadDir, installer = null) { - const sourceAgentsPath = path.join(sourcePath, 'agents'); - const targetAgentsPath = path.join(targetPath, 'agents'); - const cfgAgentsDir = path.join(bmadDir, '_config', 'agents'); - - // Check if agents directory exists in source - if (!(await fs.pathExists(sourceAgentsPath))) { - return; // No agents to compile - } - - // Get all agent YAML files recursively - const agentFiles = await this.findAgentFiles(sourceAgentsPath); - - for (const agentFile of agentFiles) { - if (!agentFile.endsWith('.agent.yaml')) continue; - - const relativePath = path.relative(sourceAgentsPath, agentFile).split(path.sep).join('/'); - const targetDir = path.join(targetAgentsPath, path.dirname(relativePath)); - - await fs.ensureDir(targetDir); - - const agentName = path.basename(agentFile, '.agent.yaml'); - const sourceYamlPath = agentFile; - const targetMdPath = path.join(targetDir, `${agentName}.md`); - const customizePath = path.join(cfgAgentsDir, `${moduleName}-${agentName}.customize.yaml`); - - // Read and compile the YAML - try { - const yamlContent = await fs.readFile(sourceYamlPath, 'utf8'); - const { compileAgent } = require('../../../lib/agent/compiler'); - - // Create customize template if it doesn't exist - if (!(await fs.pathExists(customizePath))) { - const { getSourcePath } = require('../../../lib/project-root'); - const genericTemplatePath = getSourcePath('utility', 'agent-components', 'agent.customize.template.yaml'); - if (await fs.pathExists(genericTemplatePath)) { - await this.copyFileWithPlaceholderReplacement(genericTemplatePath, customizePath); - // Only show customize creation in verbose mode - if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.message(` Created customize: ${moduleName}-${agentName}.customize.yaml`); - } - - // Store original hash for modification detection - const crypto = require('node:crypto'); - const customizeContent = await fs.readFile(customizePath, 'utf8'); - const originalHash = crypto.createHash('sha256').update(customizeContent).digest('hex'); - - // Store in main manifest - const manifestPath = path.join(bmadDir, '_config', 'manifest.yaml'); - let manifestData = {}; - if (await fs.pathExists(manifestPath)) { - const manifestContent = await fs.readFile(manifestPath, 'utf8'); - const yaml = require('yaml'); - manifestData = yaml.parse(manifestContent); - } - if (!manifestData.agentCustomizations) { - manifestData.agentCustomizations = {}; - } - manifestData.agentCustomizations[path.relative(bmadDir, customizePath)] = originalHash; - - // Write back to manifest - const yaml = require('yaml'); - // Clean the manifest data to remove any non-serializable values - const cleanManifestData = structuredClone(manifestData); - - const updatedContent = yaml.stringify(cleanManifestData, { - indent: 2, - lineWidth: 0, - }); - await fs.writeFile(manifestPath, updatedContent, 'utf8'); - } - } - - // Check for customizations and build answers object - let customizedFields = []; - let answers = {}; - if (await fs.pathExists(customizePath)) { - const customizeContent = await fs.readFile(customizePath, 'utf8'); - const customizeData = yaml.parse(customizeContent); - customizedFields = customizeData.customized_fields || []; - - // Build answers object from customizations - if (customizeData.persona) { - answers.persona = customizeData.persona; - } - if (customizeData.agent?.metadata) { - const filteredMetadata = filterCustomizationData(customizeData.agent.metadata); - if (Object.keys(filteredMetadata).length > 0) { - Object.assign(answers, { metadata: filteredMetadata }); - } - } - if (customizeData.critical_actions && customizeData.critical_actions.length > 0) { - answers.critical_actions = customizeData.critical_actions; - } - if (customizeData.memories && customizeData.memories.length > 0) { - answers.memories = customizeData.memories; - } - if (customizeData.menu && customizeData.menu.length > 0) { - answers.menu = customizeData.menu; - } - if (customizeData.prompts && customizeData.prompts.length > 0) { - answers.prompts = customizeData.prompts; - } - } - - // Check if agent has sidecar - let hasSidecar = false; - try { - const agentYaml = yaml.parse(yamlContent); - hasSidecar = agentYaml?.agent?.metadata?.hasSidecar === true; - } catch { - // Continue without sidecar processing - } - - // Compile with customizations if any - const { xml } = await compileAgent(yamlContent, answers, agentName, relativePath, { config: this.coreConfig || {} }); - - // Write the compiled agent - await fs.writeFile(targetMdPath, xml, 'utf8'); - - // Handle sidecar copying if present - if (hasSidecar) { - // Get the agent's directory to look for sidecar - const agentDir = path.dirname(agentFile); - const sidecarDirName = `${agentName}-sidecar`; - const sourceSidecarPath = path.join(agentDir, sidecarDirName); - - // Check if sidecar directory exists - if (await fs.pathExists(sourceSidecarPath)) { - // Memory is always in _bmad/_memory - const bmadMemoryPath = path.join(bmadDir, '_memory'); - - // Determine if this is an update (by checking if agent already exists) - const isUpdate = await fs.pathExists(targetMdPath); - - // Copy sidecar to memory location with update-safe handling - const copiedFiles = await this.copySidecarToMemory(sourceSidecarPath, agentName, bmadMemoryPath, isUpdate, bmadDir, installer); - - if (process.env.BMAD_VERBOSE_INSTALL === 'true' && copiedFiles.length > 0) { - await prompts.log.message(` Sidecar files processed: ${copiedFiles.length} files`); - } - } else if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.warn(` Agent marked as having sidecar but ${sidecarDirName} directory not found`); - } - } - - // Copy any non-sidecar files from agent directory (e.g., foo.md) - const agentDir = path.dirname(agentFile); - const agentEntries = await fs.readdir(agentDir, { withFileTypes: true }); - - for (const entry of agentEntries) { - if (entry.isFile() && !entry.name.endsWith('.agent.yaml') && !entry.name.endsWith('.md')) { - // Copy additional files (like foo.md) to the agent target directory - const sourceFile = path.join(agentDir, entry.name); - const targetFile = path.join(targetDir, entry.name); - await this.copyFileWithPlaceholderReplacement(sourceFile, targetFile); - } - } - - // Only show compilation details in verbose mode - if (process.env.BMAD_VERBOSE_INSTALL === 'true') { - await prompts.log.message( - ` Compiled agent: ${agentName} -> ${path.relative(targetPath, targetMdPath)}${hasSidecar ? ' (with sidecar)' : ''}`, - ); - } - } catch (error) { - await prompts.log.warn(` Failed to compile agent ${agentName}: ${error.message}`); - } - } - } - - /** - * Find all .agent.yaml files recursively in a directory - * @param {string} dir - Directory to search - * @returns {Array} List of .agent.yaml file paths - */ - async findAgentFiles(dir) { - const agentFiles = []; - - async function searchDirectory(searchDir) { - const entries = await fs.readdir(searchDir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(searchDir, entry.name); - - if (entry.isFile() && entry.name.endsWith('.agent.yaml')) { - agentFiles.push(fullPath); - } else if (entry.isDirectory()) { - await searchDirectory(fullPath); - } - } - } - - await searchDirectory(dir); - return agentFiles; - } - - /** - * Process agent files to inject activation block - * @param {string} modulePath - Path to installed module - * @param {string} moduleName - Module name - */ - async processAgentFiles(modulePath, moduleName) { - // const agentsPath = path.join(modulePath, 'agents'); - // // Check if agents directory exists - // if (!(await fs.pathExists(agentsPath))) { - // return; // No agents to process - // } - // // Get all agent MD files recursively - // const agentFiles = await this.findAgentMdFiles(agentsPath); - // for (const agentFile of agentFiles) { - // if (!agentFile.endsWith('.md')) continue; - // let content = await fs.readFile(agentFile, 'utf8'); - // // Check if content has agent XML and no activation block - // if (content.includes(' f.endsWith('.agent.yaml') || f.endsWith('.yaml')); - - if (yamlFiles.length === 0) { - return; // No YAML agent files - } - - let workflowsVendored = false; - - for (const agentFile of yamlFiles) { - const agentPath = path.join(sourceAgentsPath, agentFile); - const agentYaml = yaml.parse(await fs.readFile(agentPath, 'utf8')); - - // Check if agent has menu items with workflow-install - const menuItems = agentYaml?.agent?.menu || []; - const workflowInstallItems = menuItems.filter((item) => item['workflow-install']); - - if (workflowInstallItems.length === 0) { - continue; // No workflow-install in this agent - } - - if (!workflowsVendored) { - await prompts.log.info(`\n Vendoring cross-module workflows for ${moduleName}...`); - workflowsVendored = true; - } - - await prompts.log.message(` Processing: ${agentFile}`); - - for (const item of workflowInstallItems) { - const sourceWorkflowPath = item.workflow; // Where to copy FROM - const installWorkflowPath = item['workflow-install']; // Where to copy TO - - // Parse SOURCE workflow path - // Handle both _bmad placeholder and hardcoded 'bmad' - // Example: {project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml - // Or: {project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml - const sourceMatch = sourceWorkflowPath.match(/\{project-root\}\/(?:_bmad)\/([^/]+)\/workflows\/(.+)/); - if (!sourceMatch) { - await prompts.log.warn(` Could not parse workflow path: ${sourceWorkflowPath}`); - continue; - } - - const [, sourceModule, sourceWorkflowSubPath] = sourceMatch; - - // Parse INSTALL workflow path - // Handle_bmad - // Example: {project-root}/_bmad/bmgd/workflows/4-production/create-story/workflow.yaml - const installMatch = installWorkflowPath.match(/\{project-root\}\/(_bmad)\/([^/]+)\/workflows\/(.+)/); - if (!installMatch) { - await prompts.log.warn(` Could not parse workflow-install path: ${installWorkflowPath}`); - continue; - } - - const installWorkflowSubPath = installMatch[2]; - - const sourceModulePath = getModulePath(sourceModule); - const actualSourceWorkflowPath = path.join(sourceModulePath, 'workflows', sourceWorkflowSubPath.replace(/\/workflow\.yaml$/, '')); - - const actualDestWorkflowPath = path.join(targetPath, 'workflows', installWorkflowSubPath.replace(/\/workflow\.yaml$/, '')); - - // Check if source workflow exists - if (!(await fs.pathExists(actualSourceWorkflowPath))) { - await prompts.log.warn(` Source workflow not found: ${actualSourceWorkflowPath}`); - continue; - } - - // Copy the entire workflow folder - await prompts.log.message( - ` Vendoring: ${sourceModule}/workflows/${sourceWorkflowSubPath.replace(/\/workflow\.yaml$/, '')} → ${moduleName}/workflows/${installWorkflowSubPath.replace(/\/workflow\.yaml$/, '')}`, - ); - - await fs.ensureDir(path.dirname(actualDestWorkflowPath)); - // Copy the workflow directory recursively with placeholder replacement - await this.copyDirectoryWithPlaceholderReplacement(actualSourceWorkflowPath, actualDestWorkflowPath); - - // Update the workflow.yaml config_source reference - const workflowYamlPath = path.join(actualDestWorkflowPath, 'workflow.yaml'); - if (await fs.pathExists(workflowYamlPath)) { - await this.updateWorkflowConfigSource(workflowYamlPath, moduleName); - } - } - } - - if (workflowsVendored) { - await prompts.log.success(` Workflow vendoring complete\n`); - } - } - - /** - * Update workflow.yaml config_source to point to new module - * @param {string} workflowYamlPath - Path to workflow.yaml file - * @param {string} newModuleName - New module name to reference - */ - async updateWorkflowConfigSource(workflowYamlPath, newModuleName) { - let yamlContent = await fs.readFile(workflowYamlPath, 'utf8'); - - // Replace config_source: "{project-root}/_bmad/OLD_MODULE/config.yaml" - // with config_source: "{project-root}/_bmad/NEW_MODULE/config.yaml" - // Note: At this point _bmad has already been replaced with actual folder name - const configSourcePattern = /config_source:\s*["']?\{project-root\}\/[^/]+\/[^/]+\/config\.yaml["']?/g; - const newConfigSource = `config_source: "{project-root}/${this.bmadFolderName}/${newModuleName}/config.yaml"`; - - const updatedYaml = yamlContent.replaceAll(configSourcePattern, newConfigSource); - - if (updatedYaml !== yamlContent) { - await fs.writeFile(workflowYamlPath, updatedYaml, 'utf8'); - await prompts.log.message(` Updated config_source to: ${this.bmadFolderName}/${newModuleName}/config.yaml`); - } - } - - /** - * Create directories declared in module.yaml's `directories` key - * This replaces the security-risky module installer pattern with declarative config - * During updates, if a directory path changed, moves the old directory to the new path - * @param {string} moduleName - Name of the module - * @param {string} bmadDir - Target bmad directory - * @param {Object} options - Installation options - * @param {Object} options.moduleConfig - Module configuration from config collector - * @param {Object} options.existingModuleConfig - Previous module config (for detecting path changes during updates) - * @param {Object} options.coreConfig - Core configuration - * @returns {Promise<{createdDirs: string[], movedDirs: string[], createdWdsFolders: string[]}>} Created directories info - */ - async createModuleDirectories(moduleName, bmadDir, options = {}) { - const moduleConfig = options.moduleConfig || {}; - const existingModuleConfig = options.existingModuleConfig || {}; - const projectRoot = path.dirname(bmadDir); - const emptyResult = { createdDirs: [], movedDirs: [], createdWdsFolders: [] }; - - // Special handling for core module - it's in src/core not src/modules - let sourcePath; - if (moduleName === 'core') { - sourcePath = getSourcePath('core'); - } else { - sourcePath = await this.findModuleSource(moduleName, { silent: true }); - if (!sourcePath) { - return emptyResult; // No source found, skip - } - } - - // Read module.yaml to find the `directories` key - const moduleYamlPath = path.join(sourcePath, 'module.yaml'); - if (!(await fs.pathExists(moduleYamlPath))) { - return emptyResult; // No module.yaml, skip - } - - let moduleYaml; - try { - const yamlContent = await fs.readFile(moduleYamlPath, 'utf8'); - moduleYaml = yaml.parse(yamlContent); - } catch { - return emptyResult; // Invalid YAML, skip - } - - if (!moduleYaml || !moduleYaml.directories) { - return emptyResult; // No directories declared, skip - } - - const directories = moduleYaml.directories; - const wdsFolders = moduleYaml.wds_folders || []; - const createdDirs = []; - const movedDirs = []; - const createdWdsFolders = []; - - for (const dirRef of directories) { - // Parse variable reference like "{design_artifacts}" - const varMatch = dirRef.match(/^\{([^}]+)\}$/); - if (!varMatch) { - // Not a variable reference, skip - continue; - } - - const configKey = varMatch[1]; - const dirValue = moduleConfig[configKey]; - if (!dirValue || typeof dirValue !== 'string') { - continue; // No value or not a string, skip - } - - // Strip {project-root}/ prefix if present - let dirPath = dirValue.replace(/^\{project-root\}\/?/, ''); - - // Handle remaining {project-root} anywhere in the path - dirPath = dirPath.replaceAll('{project-root}', ''); - - // Resolve to absolute path - const fullPath = path.join(projectRoot, dirPath); - - // Validate path is within project root (prevent directory traversal) - const normalizedPath = path.normalize(fullPath); - const normalizedRoot = path.normalize(projectRoot); - if (!normalizedPath.startsWith(normalizedRoot + path.sep) && normalizedPath !== normalizedRoot) { - const color = await prompts.getColor(); - await prompts.log.warn(color.yellow(`${configKey} path escapes project root, skipping: ${dirPath}`)); - continue; - } - - // Check if directory path changed from previous config (update/modify scenario) - const oldDirValue = existingModuleConfig[configKey]; - let oldFullPath = null; - let oldDirPath = null; - if (oldDirValue && typeof oldDirValue === 'string') { - // F3: Normalize both values before comparing to avoid false negatives - // from trailing slashes, separator differences, or prefix format variations - let normalizedOld = oldDirValue.replace(/^\{project-root\}\/?/, ''); - normalizedOld = path.normalize(normalizedOld.replaceAll('{project-root}', '')); - const normalizedNew = path.normalize(dirPath); - - if (normalizedOld !== normalizedNew) { - oldDirPath = normalizedOld; - oldFullPath = path.join(projectRoot, oldDirPath); - const normalizedOldAbsolute = path.normalize(oldFullPath); - if (!normalizedOldAbsolute.startsWith(normalizedRoot + path.sep) && normalizedOldAbsolute !== normalizedRoot) { - oldFullPath = null; // Old path escapes project root, ignore it - } - - // F13: Prevent parent/child move (e.g. docs/planning → docs/planning/v2) - if (oldFullPath) { - const normalizedNewAbsolute = path.normalize(fullPath); - if ( - normalizedOldAbsolute.startsWith(normalizedNewAbsolute + path.sep) || - normalizedNewAbsolute.startsWith(normalizedOldAbsolute + path.sep) - ) { - const color = await prompts.getColor(); - await prompts.log.warn( - color.yellow( - `${configKey}: cannot move between parent/child paths (${oldDirPath} / ${dirPath}), creating new directory instead`, - ), - ); - oldFullPath = null; - } - } - } - } - - const dirName = configKey.replaceAll('_', ' '); - - if (oldFullPath && (await fs.pathExists(oldFullPath)) && !(await fs.pathExists(fullPath))) { - // Path changed and old dir exists → move old to new location - // F1: Use fs.move() instead of fs.rename() for cross-device/volume support - // F2: Wrap in try/catch — fallback to creating new dir on failure - try { - await fs.ensureDir(path.dirname(fullPath)); - await fs.move(oldFullPath, fullPath); - movedDirs.push(`${dirName}: ${oldDirPath} → ${dirPath}`); - } catch (moveError) { - const color = await prompts.getColor(); - await prompts.log.warn( - color.yellow( - `Failed to move ${oldDirPath} → ${dirPath}: ${moveError.message}\n Creating new directory instead. Please move contents from the old directory manually.`, - ), - ); - await fs.ensureDir(fullPath); - createdDirs.push(`${dirName}: ${dirPath}`); - } - } else if (oldFullPath && (await fs.pathExists(oldFullPath)) && (await fs.pathExists(fullPath))) { - // F5: Both old and new directories exist — warn user about potential orphaned documents - const color = await prompts.getColor(); - await prompts.log.warn( - color.yellow( - `${dirName}: path changed but both directories exist:\n Old: ${oldDirPath}\n New: ${dirPath}\n Old directory may contain orphaned documents — please review and merge manually.`, - ), - ); - } else if (!(await fs.pathExists(fullPath))) { - // New directory doesn't exist yet → create it - createdDirs.push(`${dirName}: ${dirPath}`); - await fs.ensureDir(fullPath); - } - - // Create WDS subfolders if this is the design_artifacts directory - if (configKey === 'design_artifacts' && wdsFolders.length > 0) { - for (const subfolder of wdsFolders) { - const subPath = path.join(fullPath, subfolder); - if (!(await fs.pathExists(subPath))) { - await fs.ensureDir(subPath); - createdWdsFolders.push(subfolder); - } - } - } - } - - return { createdDirs, movedDirs, createdWdsFolders }; - } - - /** - * Private: Process module configuration - * @param {string} modulePath - Path to installed module - * @param {string} moduleName - Module name - */ - async processModuleConfig(modulePath, moduleName) { - const configPath = path.join(modulePath, 'config.yaml'); - - if (await fs.pathExists(configPath)) { - try { - let configContent = await fs.readFile(configPath, 'utf8'); - - // Replace path placeholders - configContent = configContent.replaceAll('{project-root}', `bmad/${moduleName}`); - configContent = configContent.replaceAll('{module}', moduleName); - - await fs.writeFile(configPath, configContent, 'utf8'); - } catch (error) { - await prompts.log.warn(`Failed to process module config: ${error.message}`); - } - } - } - - /** - * Private: Sync module files (preserving user modifications) - * @param {string} sourcePath - Source module path - * @param {string} targetPath - Target module path - */ - async syncModule(sourcePath, targetPath) { - // Get list of all source files - const sourceFiles = await this.getFileList(sourcePath); - - for (const file of sourceFiles) { - const sourceFile = path.join(sourcePath, file); - const targetFile = path.join(targetPath, file); - - // Check if target file exists and has been modified - if (await fs.pathExists(targetFile)) { - const sourceStats = await fs.stat(sourceFile); - const targetStats = await fs.stat(targetFile); - - // Skip if target is newer (user modified) - if (targetStats.mtime > sourceStats.mtime) { - continue; - } - } - - // Copy file with placeholder replacement - await this.copyFileWithPlaceholderReplacement(sourceFile, targetFile); - } - } - - /** - * Private: Get list of all files in a directory - * @param {string} dir - Directory path - * @param {string} baseDir - Base directory for relative paths - * @returns {Array} List of relative file paths - */ - async getFileList(dir, baseDir = dir) { - const files = []; - const entries = await fs.readdir(dir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(dir, entry.name); - - if (entry.isDirectory()) { - const subFiles = await this.getFileList(fullPath, baseDir); - files.push(...subFiles); - } else { - files.push(path.relative(baseDir, fullPath)); - } - } - - return files; - } -} - -module.exports = { ModuleManager }; diff --git a/tools/cli/lib/activation-builder.js b/tools/cli/lib/activation-builder.js deleted file mode 100644 index 81e11158e..000000000 --- a/tools/cli/lib/activation-builder.js +++ /dev/null @@ -1,165 +0,0 @@ -const fs = require('fs-extra'); -const path = require('node:path'); -const { getSourcePath } = require('./project-root'); - -/** - * Builds activation blocks from fragments based on agent profile - */ -class ActivationBuilder { - constructor() { - this.agentComponents = getSourcePath('utility', 'agent-components'); - this.fragmentCache = new Map(); - } - - /** - * Load a fragment file - * @param {string} fragmentName - Name of fragment file (e.g., 'activation-init.txt') - * @returns {string} Fragment content - */ - async loadFragment(fragmentName) { - // Check cache first - if (this.fragmentCache.has(fragmentName)) { - return this.fragmentCache.get(fragmentName); - } - - const fragmentPath = path.join(this.agentComponents, fragmentName); - - if (!(await fs.pathExists(fragmentPath))) { - throw new Error(`Fragment not found: ${fragmentName}`); - } - - const content = await fs.readFile(fragmentPath, 'utf8'); - this.fragmentCache.set(fragmentName, content); - return content; - } - - /** - * Build complete activation block based on agent profile - * @param {Object} profile - Agent profile from AgentAnalyzer - * @param {Object} metadata - Agent metadata (module, name, etc.) - * @param {Array} agentSpecificActions - Optional agent-specific critical actions - * @param {boolean} forWebBundle - Whether this is for a web bundle - * @returns {string} Complete activation block XML - */ - async buildActivation(profile, metadata = {}, agentSpecificActions = [], forWebBundle = false) { - let activation = '\n'; - - // 1. Build sequential steps (use web-specific steps for web bundles) - const steps = await this.buildSteps(metadata, agentSpecificActions, forWebBundle); - activation += this.indent(steps, 2) + '\n'; - - // 2. Build menu handlers section with dynamic handlers - const menuHandlers = await this.loadFragment('menu-handlers.txt'); - - // Build handlers (load only needed handlers) - const handlers = await this.buildHandlers(profile); - - // Remove the extract line from the final output - it's just build metadata - // The extract list tells us which attributes to look for during processing - // but shouldn't appear in the final agent file - const processedHandlers = menuHandlers - .replace('{DYNAMIC_EXTRACT_LIST}\n', '') // Remove the entire extract line - .replace('{DYNAMIC_HANDLERS}', handlers); - - activation += '\n' + this.indent(processedHandlers, 2) + '\n'; - - const rules = await this.loadFragment('activation-rules.txt'); - activation += this.indent(rules, 2) + '\n'; - - activation += ''; - - return activation; - } - - /** - * Build handlers section based on profile - * @param {Object} profile - Agent profile - * @returns {string} Handlers XML - */ - async buildHandlers(profile) { - const handlerFragments = []; - - for (const attrType of profile.usedAttributes) { - const fragmentName = `handler-${attrType}.txt`; - try { - const handler = await this.loadFragment(fragmentName); - handlerFragments.push(handler); - } catch { - console.warn(`Warning: Handler fragment not found: ${fragmentName}`); - } - } - - return handlerFragments.join('\n'); - } - - /** - * Build sequential activation steps - * @param {Object} metadata - Agent metadata - * @param {Array} agentSpecificActions - Optional agent-specific actions - * @param {boolean} forWebBundle - Whether this is for a web bundle - * @returns {string} Steps XML - */ - async buildSteps(metadata = {}, agentSpecificActions = [], forWebBundle = false) { - const stepsTemplate = await this.loadFragment('activation-steps.txt'); - - // Extract basename from agent ID (e.g., "bmad/bmm/agents/pm.md" → "pm") - const agentBasename = metadata.id ? metadata.id.split('/').pop().replace('.md', '') : metadata.name || 'agent'; - - // Build agent-specific steps - let agentStepsXml = ''; - let currentStepNum = 4; // Steps 1-3 are standard - - if (agentSpecificActions && agentSpecificActions.length > 0) { - agentStepsXml = agentSpecificActions - .map((action) => { - const step = `${action}`; - currentStepNum++; - return step; - }) - .join('\n'); - } - - // Calculate final step numbers - const menuStep = currentStepNum; - const helpStep = currentStepNum + 1; - const haltStep = currentStepNum + 2; - const inputStep = currentStepNum + 3; - const executeStep = currentStepNum + 4; - - // Replace placeholders - const processed = stepsTemplate - .replace('{agent-file-basename}', agentBasename) - .replace('{{module}}', metadata.module || 'core') // Fixed to use {{module}} - .replace('{AGENT_SPECIFIC_STEPS}', agentStepsXml) - .replace('{MENU_STEP}', menuStep.toString()) - .replace('{HELP_STEP}', helpStep.toString()) - .replace('{HALT_STEP}', haltStep.toString()) - .replace('{INPUT_STEP}', inputStep.toString()) - .replace('{EXECUTE_STEP}', executeStep.toString()); - - return processed; - } - - /** - * Indent XML content - * @param {string} content - Content to indent - * @param {number} spaces - Number of spaces to indent - * @returns {string} Indented content - */ - indent(content, spaces) { - const indentation = ' '.repeat(spaces); - return content - .split('\n') - .map((line) => (line ? indentation + line : line)) - .join('\n'); - } - - /** - * Clear fragment cache (useful for testing or hot reload) - */ - clearCache() { - this.fragmentCache.clear(); - } -} - -module.exports = { ActivationBuilder }; diff --git a/tools/cli/lib/agent-analyzer.js b/tools/cli/lib/agent-analyzer.js deleted file mode 100644 index ae834a098..000000000 --- a/tools/cli/lib/agent-analyzer.js +++ /dev/null @@ -1,109 +0,0 @@ -const yaml = require('yaml'); -const fs = require('fs-extra'); - -/** - * Analyzes agent YAML files to detect which handlers are needed - */ -class AgentAnalyzer { - /** - * Analyze an agent YAML structure to determine which handlers it needs - * @param {Object} agentYaml - Parsed agent YAML object - * @returns {Object} Profile of needed handlers - */ - analyzeAgentObject(agentYaml) { - const profile = { - usedAttributes: new Set(), - hasPrompts: false, - menuItems: [], - }; - - // Check if agent has prompts section - if (agentYaml.agent && agentYaml.agent.prompts) { - profile.hasPrompts = true; - } - - // Analyze menu items (support both 'menu' and legacy 'commands') - const menuItems = agentYaml.agent?.menu || agentYaml.agent?.commands || []; - - for (const item of menuItems) { - // Track the menu item - profile.menuItems.push(item); - - // Check for multi format items - if (item.multi && item.triggers) { - profile.usedAttributes.add('multi'); - - // Also check attributes in nested handlers - for (const triggerGroup of item.triggers) { - for (const [triggerName, execArray] of Object.entries(triggerGroup)) { - if (Array.isArray(execArray)) { - for (const exec of execArray) { - if (exec.route) { - // Check if route is a workflow or exec - if (exec.route.endsWith('.yaml') || exec.route.endsWith('.yml')) { - profile.usedAttributes.add('workflow'); - } else { - profile.usedAttributes.add('exec'); - } - } - if (exec.workflow) profile.usedAttributes.add('workflow'); - if (exec.action) profile.usedAttributes.add('action'); - if (exec.type && ['exec', 'action', 'workflow'].includes(exec.type)) { - profile.usedAttributes.add(exec.type); - } - } - } - } - } - } else { - // Check for each possible attribute in legacy items - if (item.workflow) { - profile.usedAttributes.add('workflow'); - } - if (item['validate-workflow']) { - profile.usedAttributes.add('validate-workflow'); - } - if (item.exec) { - profile.usedAttributes.add('exec'); - } - if (item.tmpl) { - profile.usedAttributes.add('tmpl'); - } - if (item.data) { - profile.usedAttributes.add('data'); - } - if (item.action) { - profile.usedAttributes.add('action'); - } - } - } - - // Convert Set to Array for easier use - profile.usedAttributes = [...profile.usedAttributes]; - - return profile; - } - - /** - * Analyze an agent YAML file - * @param {string} filePath - Path to agent YAML file - * @returns {Object} Profile of needed handlers - */ - async analyzeAgentFile(filePath) { - const content = await fs.readFile(filePath, 'utf8'); - const agentYaml = yaml.parse(content); - return this.analyzeAgentObject(agentYaml); - } - - /** - * Check if an agent needs a specific handler - * @param {Object} profile - Agent profile from analyze - * @param {string} handlerType - Handler type to check - * @returns {boolean} True if handler is needed - */ - needsHandler(profile, handlerType) { - return profile.usedAttributes.includes(handlerType); - } -} - -module.exports = { AgentAnalyzer }; diff --git a/tools/cli/lib/agent-party-generator.js b/tools/cli/lib/agent-party-generator.js deleted file mode 100644 index efc783a87..000000000 --- a/tools/cli/lib/agent-party-generator.js +++ /dev/null @@ -1,194 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); -const { escapeXml } = require('../../lib/xml-utils'); - -const AgentPartyGenerator = { - /** - * Generate agent-manifest.csv content - * @param {Array} agentDetails - Array of agent details - * @param {Object} options - Generation options - * @returns {string} XML content - */ - generateAgentParty(agentDetails, options = {}) { - const { forWeb = false } = options; - - // Group agents by module - const agentsByModule = { - bmm: [], - cis: [], - core: [], - custom: [], - }; - - for (const agent of agentDetails) { - const moduleKey = agentsByModule[agent.module] ? agent.module : 'custom'; - agentsByModule[moduleKey].push(agent); - } - - // Build XML content - let xmlContent = ` - - - - - Complete roster of ${forWeb ? 'bundled' : 'installed'} BMAD agents with summarized personas for efficient multi-agent orchestration. - Used by party-mode and other multi-agent coordination features. - -`; - - // Add agents by module - for (const [module, agents] of Object.entries(agentsByModule)) { - if (agents.length === 0) continue; - - const moduleTitle = - module === 'bmm' ? 'BMM Module' : module === 'cis' ? 'CIS Module' : module === 'core' ? 'Core Module' : 'Custom Module'; - - xmlContent += `\n \n`; - - for (const agent of agents) { - xmlContent += ` - - ${escapeXml(agent.role || '')} - ${escapeXml(agent.identity || '')} - ${escapeXml(agent.communicationStyle || '')} - ${agent.principles || ''} - - \n`; - } - } - - // Add statistics - const totalAgents = agentDetails.length; - const moduleList = Object.keys(agentsByModule) - .filter((m) => agentsByModule[m].length > 0) - .join(', '); - - xmlContent += `\n - ${totalAgents} - ${moduleList} - ${new Date().toISOString()} - -`; - - return xmlContent; - }, - - /** - * Extract agent details from XML content - * @param {string} content - Full agent file content (markdown with XML) - * @param {string} moduleName - Module name - * @param {string} agentName - Agent name - * @returns {Object} Agent details - */ - extractAgentDetails(content, moduleName, agentName) { - try { - // Extract agent XML block - const agentMatch = content.match(/]*>([\s\S]*?)<\/agent>/); - if (!agentMatch) return null; - - const agentXml = agentMatch[0]; - - // Extract attributes from opening tag - const nameMatch = agentXml.match(/name="([^"]*)"/); - const titleMatch = agentXml.match(/title="([^"]*)"/); - const iconMatch = agentXml.match(/icon="([^"]*)"/); - - // Extract persona elements - now we just copy them as-is - const roleMatch = agentXml.match(/([\s\S]*?)<\/role>/); - const identityMatch = agentXml.match(/([\s\S]*?)<\/identity>/); - const styleMatch = agentXml.match(/([\s\S]*?)<\/communication_style>/); - const principlesMatch = agentXml.match(/([\s\S]*?)<\/principles>/); - - return { - id: `bmad/${moduleName}/agents/${agentName}.md`, - name: nameMatch ? nameMatch[1] : agentName, - title: titleMatch ? titleMatch[1] : 'Agent', - icon: iconMatch ? iconMatch[1] : '🤖', - module: moduleName, - role: roleMatch ? roleMatch[1].trim() : '', - identity: identityMatch ? identityMatch[1].trim() : '', - communicationStyle: styleMatch ? styleMatch[1].trim() : '', - principles: principlesMatch ? principlesMatch[1].trim() : '', - }; - } catch (error) { - console.error(`Error extracting details for agent ${agentName}:`, error); - return null; - } - }, - - /** - * Extract attribute from XML tag - */ - extractAttribute(xml, tagName, attrName) { - const regex = new RegExp(`<${tagName}[^>]*\\s${attrName}="([^"]*)"`, 'i'); - const match = xml.match(regex); - return match ? match[1] : ''; - }, - - /** - * Apply config overrides to agent details - * @param {Object} details - Original agent details - * @param {string} configContent - Config file content - * @returns {Object} Agent details with overrides applied - */ - applyConfigOverrides(details, configContent) { - try { - // Extract agent-config XML block - const configMatch = configContent.match(/([\s\S]*?)<\/agent-config>/); - if (!configMatch) return details; - - const configXml = configMatch[0]; - - // Extract override values - const nameMatch = configXml.match(/([\s\S]*?)<\/name>/); - const titleMatch = configXml.match(/([\s\S]*?)<\/title>/); - const roleMatch = configXml.match(/<role>([\s\S]*?)<\/role>/); - const identityMatch = configXml.match(/<identity>([\s\S]*?)<\/identity>/); - const styleMatch = configXml.match(/<communication_style>([\s\S]*?)<\/communication_style>/); - const principlesMatch = configXml.match(/<principles>([\s\S]*?)<\/principles>/); - - // Apply overrides only if values are non-empty - if (nameMatch && nameMatch[1].trim()) { - details.name = nameMatch[1].trim(); - } - - if (titleMatch && titleMatch[1].trim()) { - details.title = titleMatch[1].trim(); - } - - if (roleMatch && roleMatch[1].trim()) { - details.role = roleMatch[1].trim(); - } - - if (identityMatch && identityMatch[1].trim()) { - details.identity = identityMatch[1].trim(); - } - - if (styleMatch && styleMatch[1].trim()) { - details.communicationStyle = styleMatch[1].trim(); - } - - if (principlesMatch && principlesMatch[1].trim()) { - // Principles are now just copied as-is (narrative paragraph) - details.principles = principlesMatch[1].trim(); - } - - return details; - } catch (error) { - console.error(`Error applying config overrides:`, error); - return details; - } - }, - - /** - * Write agent-manifest.csv to file - */ - async writeAgentParty(filePath, agentDetails, options = {}) { - const content = this.generateAgentParty(agentDetails, options); - await fs.ensureDir(path.dirname(filePath)); - await fs.writeFile(filePath, content, 'utf8'); - return content; - }, -}; - -module.exports = { AgentPartyGenerator }; diff --git a/tools/cli/lib/agent/compiler.js b/tools/cli/lib/agent/compiler.js deleted file mode 100644 index f9f71baab..000000000 --- a/tools/cli/lib/agent/compiler.js +++ /dev/null @@ -1,525 +0,0 @@ -/** - * BMAD Agent Compiler - * Transforms agent YAML to compiled XML (.md) format - * Uses the existing BMAD builder infrastructure for proper formatting - */ - -const yaml = require('yaml'); -const fs = require('node:fs'); -const path = require('node:path'); -const { processAgentYaml, extractInstallConfig, stripInstallConfig, getDefaultValues } = require('./template-engine'); -const { escapeXml } = require('../../../lib/xml-utils'); -const { ActivationBuilder } = require('../activation-builder'); -const { AgentAnalyzer } = require('../agent-analyzer'); - -/** - * Build frontmatter for agent - * @param {Object} metadata - Agent metadata - * @param {string} agentName - Final agent name - * @returns {string} YAML frontmatter - */ -function buildFrontmatter(metadata, agentName) { - const nameFromFile = agentName.replaceAll('-', ' '); - const description = metadata.title || 'BMAD Agent'; - - return `--- -name: "${nameFromFile}" -description: "${description}" ---- - -You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command. - -`; -} - -// buildSimpleActivation function removed - replaced by ActivationBuilder for proper fragment loading from src/utility/agent-components/ - -/** - * Build persona XML section - * @param {Object} persona - Persona object - * @returns {string} Persona XML - */ -function buildPersonaXml(persona) { - if (!persona) return ''; - - let xml = ' <persona>\n'; - - if (persona.role) { - const roleText = persona.role.trim().replaceAll(/\n+/g, ' ').replaceAll(/\s+/g, ' '); - xml += ` <role>${escapeXml(roleText)}</role>\n`; - } - - if (persona.identity) { - const identityText = persona.identity.trim().replaceAll(/\n+/g, ' ').replaceAll(/\s+/g, ' '); - xml += ` <identity>${escapeXml(identityText)}</identity>\n`; - } - - if (persona.communication_style) { - const styleText = persona.communication_style.trim().replaceAll(/\n+/g, ' ').replaceAll(/\s+/g, ' '); - xml += ` <communication_style>${escapeXml(styleText)}</communication_style>\n`; - } - - if (persona.principles) { - let principlesText; - if (Array.isArray(persona.principles)) { - principlesText = persona.principles.join(' '); - } else { - principlesText = persona.principles.trim().replaceAll(/\n+/g, ' '); - } - xml += ` <principles>${escapeXml(principlesText)}</principles>\n`; - } - - xml += ' </persona>\n'; - - return xml; -} - -/** - * Build prompts XML section - * @param {Array} prompts - Prompts array - * @returns {string} Prompts XML - */ -function buildPromptsXml(prompts) { - if (!prompts || prompts.length === 0) return ''; - - let xml = ' <prompts>\n'; - - for (const prompt of prompts) { - xml += ` <prompt id="${prompt.id || ''}">\n`; - xml += ` <content>\n`; - // Don't escape prompt content - it's meant to be read as-is - xml += `${prompt.content || ''}\n`; - xml += ` </content>\n`; - xml += ` </prompt>\n`; - } - - xml += ' </prompts>\n'; - - return xml; -} - -/** - * Build memories XML section - * @param {Array} memories - Memories array - * @returns {string} Memories XML - */ -function buildMemoriesXml(memories) { - if (!memories || memories.length === 0) return ''; - - let xml = ' <memories>\n'; - - for (const memory of memories) { - xml += ` <memory>${escapeXml(String(memory))}</memory>\n`; - } - - xml += ' </memories>\n'; - - return xml; -} - -/** - * Build menu XML section - * Supports both legacy and multi format menu items - * Multi items display as a single menu item with nested handlers - * @param {Array} menuItems - Menu items - * @returns {string} Menu XML - */ -function buildMenuXml(menuItems) { - let xml = ' <menu>\n'; - - // Always inject menu display option first - xml += ` <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>\n`; - xml += ` <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>\n`; - - // Add user-defined menu items - if (menuItems && menuItems.length > 0) { - for (const item of menuItems) { - // Handle multi format menu items with nested handlers - if (item.multi && item.triggers && Array.isArray(item.triggers)) { - xml += ` <item type="multi">${escapeXml(item.multi)}\n`; - xml += buildNestedHandlers(item.triggers); - xml += ` </item>\n`; - } - // Handle legacy format menu items - else if (item.trigger) { - let trigger = item.trigger || ''; - - const attrs = [`cmd="${trigger}"`]; - - // Add handler attributes - if (item.workflow) attrs.push(`workflow="${item.workflow}"`); - if (item.exec) attrs.push(`exec="${item.exec}"`); - if (item.tmpl) attrs.push(`tmpl="${item.tmpl}"`); - if (item.data) attrs.push(`data="${item.data}"`); - if (item.action) attrs.push(`action="${item.action}"`); - - xml += ` <item ${attrs.join(' ')}>${escapeXml(item.description || '')}</item>\n`; - } - } - } - - xml += ` <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>\n`; - xml += ` <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>\n`; - - xml += ' </menu>\n'; - - return xml; -} - -/** - * Build nested handlers for multi format menu items - * @param {Array} triggers - Triggers array from multi format - * @returns {string} Handler XML - */ -function buildNestedHandlers(triggers) { - let xml = ''; - - for (const triggerGroup of triggers) { - for (const [triggerName, execArray] of Object.entries(triggerGroup)) { - // Build trigger with * prefix - let trigger = triggerName.startsWith('*') ? triggerName : '*' + triggerName; - - // Extract the relevant execution data - const execData = processExecArray(execArray); - - // For nested handlers in multi items, we use match attribute for fuzzy matching - const attrs = [`match="${escapeXml(execData.description || '')}"`]; - - // Add handler attributes based on exec data - if (execData.route) attrs.push(`exec="${execData.route}"`); - if (execData.workflow) attrs.push(`workflow="${execData.workflow}"`); - if (execData['validate-workflow']) attrs.push(`validate-workflow="${execData['validate-workflow']}"`); - if (execData.action) attrs.push(`action="${execData.action}"`); - if (execData.data) attrs.push(`data="${execData.data}"`); - if (execData.tmpl) attrs.push(`tmpl="${execData.tmpl}"`); - // Only add type if it's not 'exec' (exec is already implied by the exec attribute) - if (execData.type && execData.type !== 'exec') attrs.push(`type="${execData.type}"`); - - xml += ` <handler ${attrs.join(' ')}></handler>\n`; - } - } - - return xml; -} - -/** - * Process the execution array from multi format triggers - * Extracts relevant data for XML attributes - * @param {Array} execArray - Array of execution objects - * @returns {Object} Processed execution data - */ -function processExecArray(execArray) { - const result = { - description: '', - route: null, - workflow: null, - data: null, - action: null, - type: null, - }; - - if (!Array.isArray(execArray)) { - return result; - } - - for (const exec of execArray) { - if (exec.input) { - // Use input as description if no explicit description is provided - result.description = exec.input; - } - - if (exec.route) { - // Determine if it's a workflow or exec based on file extension or context - if (exec.route.endsWith('.yaml') || exec.route.endsWith('.yml')) { - result.workflow = exec.route; - } else { - result.route = exec.route; - } - } - - if (exec.data !== null && exec.data !== undefined) { - result.data = exec.data; - } - - if (exec.action) { - result.action = exec.action; - } - - if (exec.type) { - result.type = exec.type; - } - } - - return result; -} - -/** - * Compile agent YAML to proper XML format - * @param {Object} agentYaml - Parsed and processed agent YAML - * @param {string} agentName - Final agent name (for ID and frontmatter) - * @param {string} targetPath - Target path for agent ID - * @returns {Promise<string>} Compiled XML string with frontmatter - */ -async function compileToXml(agentYaml, agentName = '', targetPath = '') { - const agent = agentYaml.agent; - const meta = agent.metadata; - - let xml = ''; - - // Build frontmatter - xml += buildFrontmatter(meta, agentName || meta.name || 'agent'); - - // Start code fence - xml += '```xml\n'; - - // Agent opening tag - const agentAttrs = [ - `id="${targetPath || meta.id || ''}"`, - `name="${meta.name || ''}"`, - `title="${meta.title || ''}"`, - `icon="${meta.icon || '🤖'}"`, - ]; - if (meta.capabilities) { - agentAttrs.push(`capabilities="${escapeXml(meta.capabilities)}"`); - } - - xml += `<agent ${agentAttrs.join(' ')}>\n`; - - // Activation block - use ActivationBuilder for proper fragment loading - const activationBuilder = new ActivationBuilder(); - const analyzer = new AgentAnalyzer(); - const profile = analyzer.analyzeAgentObject(agentYaml); - xml += await activationBuilder.buildActivation( - profile, - meta, - agent.critical_actions || [], - false, // forWebBundle - set to false for IDE deployment - ); - - // Persona section - xml += buildPersonaXml(agent.persona); - - // Prompts section (if present) - if (agent.prompts && agent.prompts.length > 0) { - xml += buildPromptsXml(agent.prompts); - } - - // Memories section (if present) - if (agent.memories && agent.memories.length > 0) { - xml += buildMemoriesXml(agent.memories); - } - - // Menu section - xml += buildMenuXml(agent.menu || []); - - // Closing agent tag - xml += '</agent>\n'; - - // Close code fence - xml += '```\n'; - - return xml; -} - -/** - * Full compilation pipeline - * @param {string} yamlContent - Raw YAML string - * @param {Object} answers - Answers from install_config questions (or defaults) - * @param {string} agentName - Optional final agent name (user's custom persona name) - * @param {string} targetPath - Optional target path for agent ID - * @param {Object} options - Additional options including config - * @returns {Promise<Object>} { xml: string, metadata: Object } - */ -async function compileAgent(yamlContent, answers = {}, agentName = '', targetPath = '', options = {}) { - // Parse YAML - let agentYaml = yaml.parse(yamlContent); - - // Apply customization merges before template processing - // Handle metadata overrides (like name) - if (answers.metadata) { - // Filter out empty values from metadata - const filteredMetadata = filterCustomizationData(answers.metadata); - if (Object.keys(filteredMetadata).length > 0) { - agentYaml.agent.metadata = { ...agentYaml.agent.metadata, ...filteredMetadata }; - } - // Remove from answers so it doesn't get processed as template variables - const { metadata, ...templateAnswers } = answers; - answers = templateAnswers; - } - - // Handle other customization properties - // These should be merged into the agent structure, not processed as template variables - const customizationKeys = ['persona', 'critical_actions', 'memories', 'menu', 'prompts']; - const customizations = {}; - const remainingAnswers = { ...answers }; - - for (const key of customizationKeys) { - if (answers[key]) { - let filtered; - - // Handle different data types - if (Array.isArray(answers[key])) { - // For arrays, filter out empty/null/undefined values - filtered = answers[key].filter((item) => item !== null && item !== undefined && item !== ''); - } else { - // For objects, use filterCustomizationData - filtered = filterCustomizationData(answers[key]); - } - - // Check if we have valid content - const hasContent = Array.isArray(filtered) ? filtered.length > 0 : Object.keys(filtered).length > 0; - - if (hasContent) { - customizations[key] = filtered; - } - delete remainingAnswers[key]; - } - } - - // Merge customizations into agentYaml - if (Object.keys(customizations).length > 0) { - // For persona: replace entire section - if (customizations.persona) { - agentYaml.agent.persona = customizations.persona; - } - - // For critical_actions: append to existing or create new - if (customizations.critical_actions) { - const existing = agentYaml.agent.critical_actions || []; - agentYaml.agent.critical_actions = [...existing, ...customizations.critical_actions]; - } - - // For memories: append to existing or create new - if (customizations.memories) { - const existing = agentYaml.agent.memories || []; - agentYaml.agent.memories = [...existing, ...customizations.memories]; - } - - // For menu: append to existing or create new - if (customizations.menu) { - const existing = agentYaml.agent.menu || []; - agentYaml.agent.menu = [...existing, ...customizations.menu]; - } - - // For prompts: append to existing or create new (by id) - if (customizations.prompts) { - const existing = agentYaml.agent.prompts || []; - // Merge by id, with customizations taking precedence - const mergedPrompts = [...existing]; - for (const customPrompt of customizations.prompts) { - const existingIndex = mergedPrompts.findIndex((p) => p.id === customPrompt.id); - if (existingIndex === -1) { - mergedPrompts.push(customPrompt); - } else { - mergedPrompts[existingIndex] = customPrompt; - } - } - agentYaml.agent.prompts = mergedPrompts; - } - } - - // Use remaining answers for template processing - answers = remainingAnswers; - - // Extract install_config - const installConfig = extractInstallConfig(agentYaml); - - // Merge defaults with provided answers - let finalAnswers = answers; - if (installConfig) { - const defaults = getDefaultValues(installConfig); - finalAnswers = { ...defaults, ...answers }; - } - - // Process templates with answers - const processedYaml = processAgentYaml(agentYaml, finalAnswers); - - // Strip install_config from output - const cleanYaml = stripInstallConfig(processedYaml); - - let xml = await compileToXml(cleanYaml, agentName, targetPath); - - // Ensure xml is a string before attempting replaceAll - if (typeof xml !== 'string') { - throw new TypeError('compileToXml did not return a string'); - } - - return { - xml, - metadata: cleanYaml.agent.metadata, - processedYaml: cleanYaml, - }; -} - -/** - * Filter customization data to remove empty/null values - * @param {Object} data - Raw customization data - * @returns {Object} Filtered customization data - */ -function filterCustomizationData(data) { - const filtered = {}; - - for (const [key, value] of Object.entries(data)) { - if (value === null || value === undefined || value === '') { - continue; // Skip null/undefined/empty values - } - - if (Array.isArray(value)) { - if (value.length > 0) { - filtered[key] = value; - } - } else if (typeof value === 'object') { - const nested = filterCustomizationData(value); - if (Object.keys(nested).length > 0) { - filtered[key] = nested; - } - } else { - filtered[key] = value; - } - } - - return filtered; -} - -/** - * Compile agent file to .md - * @param {string} yamlPath - Path to agent YAML file - * @param {Object} options - { answers: {}, outputPath: string } - * @returns {Object} Compilation result - */ -function compileAgentFile(yamlPath, options = {}) { - const yamlContent = fs.readFileSync(yamlPath, 'utf8'); - const result = compileAgent(yamlContent, options.answers || {}); - - // Determine output path - let outputPath = options.outputPath; - if (!outputPath) { - // Default: same directory, same name, .md extension - const dir = path.dirname(yamlPath); - const basename = path.basename(yamlPath, '.agent.yaml'); - outputPath = path.join(dir, `${basename}.md`); - } - - // Write compiled XML - fs.writeFileSync(outputPath, xml, 'utf8'); - - return { - ...result, - xml, - outputPath, - sourcePath: yamlPath, - }; -} - -module.exports = { - compileToXml, - compileAgent, - compileAgentFile, - escapeXml, - buildFrontmatter, - buildPersonaXml, - buildPromptsXml, - buildMemoriesXml, - buildMenuXml, - filterCustomizationData, -}; diff --git a/tools/cli/lib/agent/installer.js b/tools/cli/lib/agent/installer.js deleted file mode 100644 index c9e0dd916..000000000 --- a/tools/cli/lib/agent/installer.js +++ /dev/null @@ -1,680 +0,0 @@ -/** - * BMAD Agent Installer - * Discovers, prompts, compiles, and installs agents - */ - -const fs = require('node:fs'); -const path = require('node:path'); -const yaml = require('yaml'); -const prompts = require('../prompts'); -const { compileAgent, compileAgentFile } = require('./compiler'); -const { extractInstallConfig, getDefaultValues } = require('./template-engine'); - -/** - * Find BMAD config file in project - * @param {string} startPath - Starting directory to search from - * @returns {Object|null} Config data or null - */ -function findBmadConfig(startPath = process.cwd()) { - // Look for common BMAD folder names - const possibleNames = ['_bmad']; - - for (const name of possibleNames) { - const configPath = path.join(startPath, name, 'bmb', 'config.yaml'); - if (fs.existsSync(configPath)) { - const content = fs.readFileSync(configPath, 'utf8'); - const config = yaml.parse(content); - return { - ...config, - bmadFolder: path.join(startPath, name), - projectRoot: startPath, - }; - } - } - - return null; -} - -/** - * Resolve path variables like {project-root} and {bmad-folder} - * @param {string} pathStr - Path with variables - * @param {Object} context - Contains projectRoot, bmadFolder - * @returns {string} Resolved path - */ -function resolvePath(pathStr, context) { - return pathStr.replaceAll('{project-root}', context.projectRoot).replaceAll('{bmad-folder}', context.bmadFolder); -} - -/** - * Discover available agents in the custom agent location recursively - * @param {string} searchPath - Path to search for agents - * @returns {Array} List of agent info objects - */ -function discoverAgents(searchPath) { - if (!fs.existsSync(searchPath)) { - return []; - } - - const agents = []; - - // Helper function to recursively search - function searchDirectory(dir, relativePath = '') { - const entries = fs.readdirSync(dir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(dir, entry.name); - const agentRelativePath = relativePath ? path.join(relativePath, entry.name) : entry.name; - - if (entry.isFile() && entry.name.endsWith('.agent.yaml')) { - // Simple agent (single file) - // The agent name is based on the filename - const agentName = entry.name.replace('.agent.yaml', ''); - agents.push({ - type: 'simple', - name: agentName, - path: fullPath, - yamlFile: fullPath, - relativePath: agentRelativePath.replace('.agent.yaml', ''), - }); - } else if (entry.isDirectory()) { - // Check if this directory contains an .agent.yaml file - try { - const dirContents = fs.readdirSync(fullPath); - const yamlFiles = dirContents.filter((f) => f.endsWith('.agent.yaml')); - - if (yamlFiles.length > 0) { - // Found .agent.yaml files in this directory - for (const yamlFile of yamlFiles) { - const agentYamlPath = path.join(fullPath, yamlFile); - const agentName = path.basename(yamlFile, '.agent.yaml'); - - agents.push({ - type: 'expert', - name: agentName, - path: fullPath, - yamlFile: agentYamlPath, - relativePath: agentRelativePath, - }); - } - } else { - // No .agent.yaml in this directory, recurse deeper - searchDirectory(fullPath, agentRelativePath); - } - } catch { - // Skip directories we can't read - } - } - } - } - - searchDirectory(searchPath); - return agents; -} - -/** - * Load agent YAML and extract install_config - * @param {string} yamlPath - Path to agent YAML file - * @returns {Object} Agent YAML and install config - */ -function loadAgentConfig(yamlPath) { - const content = fs.readFileSync(yamlPath, 'utf8'); - const agentYaml = yaml.parse(content); - const installConfig = extractInstallConfig(agentYaml); - const defaults = installConfig ? getDefaultValues(installConfig) : {}; - - // Check for saved_answers (from previously installed custom agents) - // These take precedence over defaults - const savedAnswers = agentYaml?.saved_answers || {}; - - const metadata = agentYaml?.agent?.metadata || {}; - - return { - yamlContent: content, - agentYaml, - installConfig, - defaults: { ...defaults, ...savedAnswers }, // saved_answers override defaults - metadata, - hasSidecar: metadata.hasSidecar === true, - }; -} - -/** - * Interactive prompt for install_config questions - * @param {Object} installConfig - Install configuration with questions - * @param {Object} defaults - Default values - * @returns {Promise<Object>} User answers - */ -async function promptInstallQuestions(installConfig, defaults, presetAnswers = {}) { - if (!installConfig || !installConfig.questions || installConfig.questions.length === 0) { - return { ...defaults, ...presetAnswers }; - } - - const answers = { ...defaults, ...presetAnswers }; - - await prompts.note(installConfig.description || '', 'Agent Configuration'); - - for (const q of installConfig.questions) { - // Skip questions for variables that are already set (e.g., custom_name set upfront) - if (answers[q.var] !== undefined && answers[q.var] !== defaults[q.var]) { - await prompts.log.message(` ${q.var}: ${answers[q.var]} (already set)`); - continue; - } - - switch (q.type) { - case 'text': { - const response = await prompts.text({ - message: q.prompt, - default: q.default ?? '', - }); - answers[q.var] = response ?? q.default ?? ''; - break; - } - case 'boolean': { - const response = await prompts.confirm({ - message: q.prompt, - default: q.default, - }); - answers[q.var] = response; - break; - } - case 'choice': { - const response = await prompts.select({ - message: q.prompt, - options: q.options.map((o) => ({ value: o.value, label: o.label })), - initialValue: q.default, - }); - answers[q.var] = response; - break; - } - // No default - } - } - - return answers; -} - -/** - * Install a compiled agent to target location - * @param {Object} agentInfo - Agent discovery info - * @param {Object} answers - User answers for install_config - * @param {string} targetPath - Target installation directory - * @param {Object} options - Additional options including config - * @returns {Object} Installation result - */ -function installAgent(agentInfo, answers, targetPath, options = {}) { - // Compile the agent - const { xml, metadata, processedYaml } = compileAgent(fs.readFileSync(agentInfo.yamlFile, 'utf8'), answers); - - // Determine target agent folder name - // Use the folder name from agentInfo, NOT the persona name from metadata - const agentFolderName = agentInfo.name; - - const agentTargetDir = path.join(targetPath, agentFolderName); - - // Create target directory - if (!fs.existsSync(agentTargetDir)) { - fs.mkdirSync(agentTargetDir, { recursive: true }); - } - - // Write compiled XML (.md) - const compiledFileName = `${agentFolderName}.md`; - const compiledPath = path.join(agentTargetDir, compiledFileName); - fs.writeFileSync(compiledPath, xml, 'utf8'); - - const result = { - success: true, - agentName: metadata.name || agentInfo.name, - targetDir: agentTargetDir, - compiledFile: compiledPath, - }; - - return result; -} - -/** - * Update agent metadata ID to reflect installed location - * @param {string} compiledContent - Compiled XML content - * @param {string} targetPath - Target installation path relative to project - * @returns {string} Updated content - */ -function updateAgentId(compiledContent, targetPath) { - // Update the id attribute in the opening agent tag - return compiledContent.replace(/(<agent\s+id=")[^"]*(")/, `$1${targetPath}$2`); -} - -/** - * Detect if a path is within a BMAD project - * @param {string} targetPath - Path to check - * @returns {Object|null} Project info with bmadFolder and cfgFolder - */ -function detectBmadProject(targetPath) { - let checkPath = path.resolve(targetPath); - const root = path.parse(checkPath).root; - - // Walk up directory tree looking for BMAD installation - while (checkPath !== root) { - const possibleNames = ['_bmad']; - for (const name of possibleNames) { - const bmadFolder = path.join(checkPath, name); - const cfgFolder = path.join(bmadFolder, '_config'); - const manifestFile = path.join(cfgFolder, 'agent-manifest.csv'); - - if (fs.existsSync(manifestFile)) { - return { - projectRoot: checkPath, - bmadFolder, - cfgFolder, - manifestFile, - }; - } - } - checkPath = path.dirname(checkPath); - } - - return null; -} - -/** - * Escape CSV field value - * @param {string} value - Value to escape - * @returns {string} Escaped value - */ -function escapeCsvField(value) { - if (typeof value !== 'string') value = String(value); - // If contains comma, quote, or newline, wrap in quotes and escape internal quotes - if (value.includes(',') || value.includes('"') || value.includes('\n')) { - return '"' + value.replaceAll('"', '""') + '"'; - } - return value; -} - -/** - * Parse CSV line respecting quoted fields - * @param {string} line - CSV line - * @returns {Array} Parsed fields - */ -function parseCsvLine(line) { - const fields = []; - let current = ''; - let inQuotes = false; - - for (let i = 0; i < line.length; i++) { - const char = line[i]; - const nextChar = line[i + 1]; - - if (char === '"' && !inQuotes) { - inQuotes = true; - } else if (char === '"' && inQuotes) { - if (nextChar === '"') { - current += '"'; - i++; // Skip escaped quote - } else { - inQuotes = false; - } - } else if (char === ',' && !inQuotes) { - fields.push(current); - current = ''; - } else { - current += char; - } - } - fields.push(current); - return fields; -} - -/** - * Check if agent name exists in manifest - * @param {string} manifestFile - Path to agent-manifest.csv - * @param {string} agentName - Agent name to check - * @returns {Object|null} Existing entry or null - */ -function checkManifestForAgent(manifestFile, agentName) { - const content = fs.readFileSync(manifestFile, 'utf8'); - const lines = content.trim().split('\n'); - - if (lines.length < 2) return null; - - const header = parseCsvLine(lines[0]); - const nameIndex = header.indexOf('name'); - - if (nameIndex === -1) return null; - - for (let i = 1; i < lines.length; i++) { - const fields = parseCsvLine(lines[i]); - if (fields[nameIndex] === agentName) { - const entry = {}; - for (const [idx, col] of header.entries()) { - entry[col] = fields[idx] || ''; - } - entry._lineNumber = i; - return entry; - } - } - - return null; -} - -/** - * Check if agent path exists in manifest - * @param {string} manifestFile - Path to agent-manifest.csv - * @param {string} agentPath - Agent path to check - * @returns {Object|null} Existing entry or null - */ -function checkManifestForPath(manifestFile, agentPath) { - const content = fs.readFileSync(manifestFile, 'utf8'); - const lines = content.trim().split('\n'); - - if (lines.length < 2) return null; - - const header = parseCsvLine(lines[0]); - const pathIndex = header.indexOf('path'); - - if (pathIndex === -1) return null; - - for (let i = 1; i < lines.length; i++) { - const fields = parseCsvLine(lines[i]); - if (fields[pathIndex] === agentPath) { - const entry = {}; - for (const [idx, col] of header.entries()) { - entry[col] = fields[idx] || ''; - } - entry._lineNumber = i; - return entry; - } - } - - return null; -} - -/** - * Update existing entry in manifest - * @param {string} manifestFile - Path to agent-manifest.csv - * @param {Object} agentData - New agent data - * @param {number} lineNumber - Line number to replace (1-indexed, excluding header) - * @returns {boolean} Success - */ -function updateManifestEntry(manifestFile, agentData, lineNumber) { - const content = fs.readFileSync(manifestFile, 'utf8'); - const lines = content.trim().split('\n'); - - const header = lines[0]; - const columns = header.split(','); - - // Build the new row - const row = columns.map((col) => { - const value = agentData[col] || ''; - return escapeCsvField(value); - }); - - // Replace the line - lines[lineNumber] = row.join(','); - - fs.writeFileSync(manifestFile, lines.join('\n') + '\n', 'utf8'); - return true; -} - -/** - * Add agent to manifest CSV - * @param {string} manifestFile - Path to agent-manifest.csv - * @param {Object} agentData - Agent metadata and path info - * @returns {boolean} Success - */ -function addToManifest(manifestFile, agentData) { - const content = fs.readFileSync(manifestFile, 'utf8'); - const lines = content.trim().split('\n'); - - // Parse header to understand column order - const header = lines[0]; - const columns = header.split(','); - - // Build the new row based on header columns - const row = columns.map((col) => { - const value = agentData[col] || ''; - return escapeCsvField(value); - }); - - // Append new row - const newLine = row.join(','); - const updatedContent = content.trim() + '\n' + newLine + '\n'; - - fs.writeFileSync(manifestFile, updatedContent, 'utf8'); - return true; -} - -/** - * Save agent source YAML to _config/custom/agents/ for reinstallation - * Stores user answers in a top-level saved_answers section (cleaner than overwriting defaults) - * @param {Object} agentInfo - Agent info (path, type, etc.) - * @param {string} cfgFolder - Path to _config folder - * @param {string} agentName - Final agent name (e.g., "fred-commit-poet") - * @param {Object} answers - User answers to save for reinstallation - * @returns {Object} Info about saved source - */ -function saveAgentSource(agentInfo, cfgFolder, agentName, answers = {}) { - // Save to _config/custom/agents/ instead of _config/agents/ - const customAgentsCfgDir = path.join(cfgFolder, 'custom', 'agents'); - - if (!fs.existsSync(customAgentsCfgDir)) { - fs.mkdirSync(customAgentsCfgDir, { recursive: true }); - } - - const yamlLib = require('yaml'); - - /** - * Add saved_answers section to store user's actual answers - */ - function addSavedAnswers(agentYaml, answers) { - // Store answers in a clear, separate section - agentYaml.saved_answers = answers; - return agentYaml; - } - - if (agentInfo.type === 'simple') { - // Simple agent: copy YAML with saved_answers section - const targetYaml = path.join(customAgentsCfgDir, `${agentName}.agent.yaml`); - const originalContent = fs.readFileSync(agentInfo.yamlFile, 'utf8'); - const agentYaml = yamlLib.parse(originalContent); - - // Add saved_answers section with user's choices - addSavedAnswers(agentYaml, answers); - - fs.writeFileSync(targetYaml, yamlLib.stringify(agentYaml), 'utf8'); - return { type: 'simple', path: targetYaml }; - } else { - // Expert agent with sidecar: copy entire folder with saved_answers - const targetFolder = path.join(customAgentsCfgDir, agentName); - if (!fs.existsSync(targetFolder)) { - fs.mkdirSync(targetFolder, { recursive: true }); - } - - // Copy YAML and entire sidecar structure - const sourceDir = agentInfo.path; - const copied = []; - - function copyDir(src, dest) { - if (!fs.existsSync(dest)) { - fs.mkdirSync(dest, { recursive: true }); - } - - const entries = fs.readdirSync(src, { withFileTypes: true }); - for (const entry of entries) { - const srcPath = path.join(src, entry.name); - const destPath = path.join(dest, entry.name); - - if (entry.isDirectory()) { - copyDir(srcPath, destPath); - } else if (entry.name.endsWith('.agent.yaml')) { - // For the agent YAML, add saved_answers section - const originalContent = fs.readFileSync(srcPath, 'utf8'); - const agentYaml = yamlLib.parse(originalContent); - addSavedAnswers(agentYaml, answers); - // Rename YAML to match final agent name - const newYamlPath = path.join(dest, `${agentName}.agent.yaml`); - fs.writeFileSync(newYamlPath, yamlLib.stringify(agentYaml), 'utf8'); - copied.push(newYamlPath); - } else { - fs.copyFileSync(srcPath, destPath); - copied.push(destPath); - } - } - } - - copyDir(sourceDir, targetFolder); - return { type: 'expert', path: targetFolder, files: copied }; - } -} - -/** - * Create IDE slash command wrapper for agent - * Leverages IdeManager to dispatch to IDE-specific handlers - * @param {string} projectRoot - Project root path - * @param {string} agentName - Agent name (e.g., "commit-poet") - * @param {string} agentPath - Path to compiled agent (relative to project root) - * @param {Object} metadata - Agent metadata - * @returns {Promise<Object>} Info about created slash commands - */ -async function createIdeSlashCommands(projectRoot, agentName, agentPath, metadata) { - // Read manifest.yaml to get installed IDEs - const manifestPath = path.join(projectRoot, '_bmad', '_config', 'manifest.yaml'); - let installedIdes = ['claude-code']; // Default to Claude Code if no manifest - - if (fs.existsSync(manifestPath)) { - const yamlLib = require('yaml'); - const manifestContent = fs.readFileSync(manifestPath, 'utf8'); - const manifest = yamlLib.parse(manifestContent); - if (manifest.ides && Array.isArray(manifest.ides)) { - installedIdes = manifest.ides; - } - } - - // Use IdeManager to install custom agent launchers for all configured IDEs - const { IdeManager } = require('../../installers/lib/ide/manager'); - const ideManager = new IdeManager(); - - const results = await ideManager.installCustomAgentLaunchers(installedIdes, projectRoot, agentName, agentPath, metadata); - - return results; -} - -/** - * Update manifest.yaml to track custom agent - * @param {string} manifestPath - Path to manifest.yaml - * @param {string} agentName - Agent name - * @param {string} agentType - Agent type (source name) - * @returns {boolean} Success - */ -function updateManifestYaml(manifestPath, agentName, agentType) { - if (!fs.existsSync(manifestPath)) { - return false; - } - - const yamlLib = require('yaml'); - const content = fs.readFileSync(manifestPath, 'utf8'); - const manifest = yamlLib.parse(content); - - // Initialize custom_agents array if not exists - if (!manifest.custom_agents) { - manifest.custom_agents = []; - } - - // Check if this agent is already registered - const existingIndex = manifest.custom_agents.findIndex((a) => a.name === agentName || (typeof a === 'string' && a === agentName)); - - const agentEntry = { - name: agentName, - type: agentType, - installed: new Date().toISOString(), - }; - - if (existingIndex === -1) { - // Add new entry - manifest.custom_agents.push(agentEntry); - } else { - // Update existing entry - manifest.custom_agents[existingIndex] = agentEntry; - } - - // Update lastUpdated timestamp - if (manifest.installation) { - manifest.installation.lastUpdated = new Date().toISOString(); - } - - // Write back - const newContent = yamlLib.stringify(manifest); - fs.writeFileSync(manifestPath, newContent, 'utf8'); - - return true; -} - -/** - * Extract manifest data from compiled agent XML - * @param {string} xmlContent - Compiled agent XML - * @param {Object} metadata - Agent metadata from YAML - * @param {string} agentPath - Relative path to agent file - * @param {string} moduleName - Module name (default: 'custom') - * @returns {Object} Manifest row data - */ -function extractManifestData(xmlContent, metadata, agentPath, moduleName = 'custom') { - // Extract data from XML using regex (simple parsing) - const extractTag = (tag) => { - const match = xmlContent.match(new RegExp(`<${tag}>([\\s\\S]*?)</${tag}>`)); - if (!match) return ''; - // Collapse multiple lines into single line, normalize whitespace - return match[1].trim().replaceAll(/\n+/g, ' ').replaceAll(/\s+/g, ' ').trim(); - }; - - // Extract attributes from agent tag - const extractAgentAttribute = (attr) => { - const match = xmlContent.match(new RegExp(`<agent[^>]*\\s${attr}=["']([^"']+)["']`)); - return match ? match[1] : ''; - }; - - const extractPrinciples = () => { - const match = xmlContent.match(/<principles>([\s\S]*?)<\/principles>/); - if (!match) return ''; - // Extract individual principle lines - const principles = match[1] - .split('\n') - .map((l) => l.trim()) - .filter((l) => l.length > 0) - .join(' '); - return principles; - }; - - // Prioritize XML extraction over metadata for agent persona info - const xmlTitle = extractAgentAttribute('title') || extractTag('name'); - const xmlIcon = extractAgentAttribute('icon'); - - return { - name: metadata.id ? path.basename(metadata.id, '.md') : metadata.name.toLowerCase().replaceAll(/\s+/g, '-'), - displayName: xmlTitle || metadata.name || '', - title: xmlTitle || metadata.title || '', - icon: xmlIcon || metadata.icon || '', - role: extractTag('role'), - identity: extractTag('identity'), - communicationStyle: extractTag('communication_style'), - principles: extractPrinciples(), - module: moduleName, - path: agentPath, - }; -} - -module.exports = { - findBmadConfig, - resolvePath, - discoverAgents, - loadAgentConfig, - promptInstallQuestions, - installAgent, - updateAgentId, - detectBmadProject, - addToManifest, - extractManifestData, - escapeCsvField, - checkManifestForAgent, - checkManifestForPath, - updateManifestEntry, - saveAgentSource, - createIdeSlashCommands, - updateManifestYaml, -}; diff --git a/tools/cli/lib/agent/template-engine.js b/tools/cli/lib/agent/template-engine.js deleted file mode 100644 index 01281fb17..000000000 --- a/tools/cli/lib/agent/template-engine.js +++ /dev/null @@ -1,152 +0,0 @@ -/** - * Template Engine for BMAD Agent Install Configuration - * Processes {{variable}}, {{#if}}, {{#unless}}, and {{/if}} blocks - */ - -/** - * Process all template syntax in a string - * @param {string} content - Content with template syntax - * @param {Object} variables - Key-value pairs from install_config answers - * @returns {string} Processed content - */ -function processTemplate(content, variables = {}) { - let result = content; - - // Process conditionals first (they may contain variables) - result = processConditionals(result, variables); - - // Then process simple variable replacements - result = processVariables(result, variables); - - // Clean up any empty lines left by removed conditionals - result = cleanupEmptyLines(result); - - return result; -} - -/** - * Process {{#if}}, {{#unless}}, {{/if}}, {{/unless}} blocks - */ -function processConditionals(content, variables) { - let result = content; - - // Process {{#if variable == "value"}} blocks - // Handle both regular quotes and JSON-escaped quotes (\") - const ifEqualsPattern = /\{\{#if\s+(\w+)\s*==\s*\\?"([^"\\]+)\\?"\s*\}\}([\s\S]*?)\{\{\/if\}\}/g; - result = result.replaceAll(ifEqualsPattern, (match, varName, value, block) => { - return variables[varName] === value ? block : ''; - }); - - // Process {{#if variable}} blocks (boolean or truthy check) - const ifBoolPattern = /\{\{#if\s+(\w+)\s*\}\}([\s\S]*?)\{\{\/if\}\}/g; - result = result.replaceAll(ifBoolPattern, (match, varName, block) => { - const val = variables[varName]; - // Treat as truthy: true, non-empty string, non-zero number - const isTruthy = val === true || (typeof val === 'string' && val.length > 0) || (typeof val === 'number' && val !== 0); - return isTruthy ? block : ''; - }); - - // Process {{#unless variable}} blocks (inverse of if) - const unlessPattern = /\{\{#unless\s+(\w+)\s*\}\}([\s\S]*?)\{\{\/unless\}\}/g; - result = result.replaceAll(unlessPattern, (match, varName, block) => { - const val = variables[varName]; - const isFalsy = val === false || val === '' || val === null || val === undefined || val === 0; - return isFalsy ? block : ''; - }); - - return result; -} - -/** - * Process {{variable}} replacements - */ -function processVariables(content, variables) { - let result = content; - - // Replace {{variable}} with value - const varPattern = /\{\{(\w+)\}\}/g; - result = result.replaceAll(varPattern, (match, varName) => { - if (Object.hasOwn(variables, varName)) { - return String(variables[varName]); - } - // If variable not found, leave as-is (might be runtime variable like {user_name}) - return match; - }); - - return result; -} - -/** - * Clean up excessive empty lines left after removing conditional blocks - */ -function cleanupEmptyLines(content) { - // Replace 3+ consecutive newlines with 2 - return content.replaceAll(/\n{3,}/g, '\n\n'); -} - -/** - * Extract install_config from agent YAML object - * @param {Object} agentYaml - Parsed agent YAML - * @returns {Object|null} install_config section or null - */ -function extractInstallConfig(agentYaml) { - return agentYaml?.agent?.install_config || null; -} - -/** - * Remove install_config from agent YAML (after processing) - * @param {Object} agentYaml - Parsed agent YAML - * @returns {Object} Agent YAML without install_config - */ -function stripInstallConfig(agentYaml) { - const result = structuredClone(agentYaml); - if (result.agent) { - delete result.agent.install_config; - } - return result; -} - -/** - * Process entire agent YAML object with template variables - * @param {Object} agentYaml - Parsed agent YAML - * @param {Object} variables - Answers from install_config questions - * @returns {Object} Processed agent YAML - */ -function processAgentYaml(agentYaml, variables) { - // Convert to JSON string, process templates, parse back - const jsonString = JSON.stringify(agentYaml, null, 2); - const processed = processTemplate(jsonString, variables); - return JSON.parse(processed); -} - -/** - * Get default values from install_config questions - * @param {Object} installConfig - install_config section - * @returns {Object} Default values keyed by variable name - */ -function getDefaultValues(installConfig) { - const defaults = {}; - - if (!installConfig?.questions) { - return defaults; - } - - for (const question of installConfig.questions) { - if (question.var && question.default !== undefined) { - defaults[question.var] = question.default; - } - } - - return defaults; -} - -module.exports = { - processTemplate, - processConditionals, - processVariables, - extractInstallConfig, - stripInstallConfig, - processAgentYaml, - getDefaultValues, - cleanupEmptyLines, -}; diff --git a/tools/cli/lib/cli-utils.js b/tools/cli/lib/cli-utils.js deleted file mode 100644 index 569f1c44c..000000000 --- a/tools/cli/lib/cli-utils.js +++ /dev/null @@ -1,182 +0,0 @@ -const path = require('node:path'); -const os = require('node:os'); -const prompts = require('./prompts'); - -const CLIUtils = { - /** - * Get version from package.json - */ - getVersion() { - try { - const packageJson = require(path.join(__dirname, '..', '..', '..', 'package.json')); - return packageJson.version || 'Unknown'; - } catch { - return 'Unknown'; - } - }, - - /** - * Display BMAD logo using @clack intro + box - * @param {boolean} _clearScreen - Deprecated, ignored (no longer clears screen) - */ - async displayLogo(_clearScreen = true) { - const version = this.getVersion(); - const color = await prompts.getColor(); - - // ASCII art logo - const logo = [ - ' ██████╗ ███╗ ███╗ █████╗ ██████╗ ™', - ' ██╔══██╗████╗ ████║██╔══██╗██╔══██╗', - ' ██████╔╝██╔████╔██║███████║██║ ██║', - ' ██╔══██╗██║╚██╔╝██║██╔══██║██║ ██║', - ' ██████╔╝██║ ╚═╝ ██║██║ ██║██████╔╝', - ' ╚═════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═════╝', - ] - .map((line) => color.yellow(line)) - .join('\n'); - - const tagline = ' Build More, Architect Dreams'; - - await prompts.box(`${logo}\n${tagline}`, `v${version}`, { - contentAlign: 'center', - rounded: true, - formatBorder: color.blue, - }); - }, - - /** - * Display section header - * @param {string} title - Section title - * @param {string} subtitle - Optional subtitle - */ - async displaySection(title, subtitle = null) { - await prompts.note(subtitle || '', title); - }, - - /** - * Display info box - * @param {string|Array} content - Content to display - * @param {Object} options - Box options - */ - async displayBox(content, options = {}) { - let text = content; - if (Array.isArray(content)) { - text = content.join('\n\n'); - } - - const color = await prompts.getColor(); - const borderColor = options.borderColor || 'cyan'; - const colorMap = { green: color.green, red: color.red, yellow: color.yellow, cyan: color.cyan, blue: color.blue }; - const formatBorder = colorMap[borderColor] || color.cyan; - - await prompts.box(text, options.title, { - rounded: options.borderStyle === 'round' || options.borderStyle === undefined, - formatBorder, - }); - }, - - /** - * Display module configuration header - * @param {string} moduleName - Module name (fallback if no custom header) - * @param {string} header - Custom header from module.yaml - * @param {string} subheader - Custom subheader from module.yaml - */ - async displayModuleConfigHeader(moduleName, header = null, subheader = null) { - const title = header || `Configuring ${moduleName.toUpperCase()} Module`; - await prompts.note(subheader || '', title); - }, - - /** - * Display module with no custom configuration - * @param {string} moduleName - Module name (fallback if no custom header) - * @param {string} header - Custom header from module.yaml - * @param {string} subheader - Custom subheader from module.yaml - */ - async displayModuleNoConfig(moduleName, header = null, subheader = null) { - const title = header || `${moduleName.toUpperCase()} Module - No Custom Configuration`; - await prompts.note(subheader || '', title); - }, - - /** - * Display step indicator - * @param {number} current - Current step - * @param {number} total - Total steps - * @param {string} description - Step description - */ - async displayStep(current, total, description) { - const progress = `[${current}/${total}]`; - await prompts.log.step(`${progress} ${description}`); - }, - - /** - * Display completion message - * @param {string} message - Completion message - */ - async displayComplete(message) { - const color = await prompts.getColor(); - await prompts.box(`\u2728 ${message}`, 'Complete', { - rounded: true, - formatBorder: color.green, - }); - }, - - /** - * Display error message - * @param {string} message - Error message - */ - async displayError(message) { - const color = await prompts.getColor(); - await prompts.box(`\u2717 ${message}`, 'Error', { - rounded: true, - formatBorder: color.red, - }); - }, - - /** - * Format list for display - * @param {Array} items - Items to display - * @param {string} prefix - Item prefix - */ - formatList(items, prefix = '\u2022') { - return items.map((item) => ` ${prefix} ${item}`).join('\n'); - }, - - /** - * Clear previous lines - * @param {number} lines - Number of lines to clear - */ - clearLines(lines) { - for (let i = 0; i < lines; i++) { - process.stdout.moveCursor(0, -1); - process.stdout.clearLine(1); - } - }, - - /** - * Display module completion message - * @param {string} moduleName - Name of the completed module - * @param {boolean} clearScreen - Whether to clear the screen first (deprecated, always false now) - */ - displayModuleComplete(moduleName, clearScreen = false) { - // No longer clear screen or show boxes - just a simple completion message - // This is deprecated but kept for backwards compatibility - }, - - /** - * Expand path with ~ expansion - * @param {string} inputPath - Path to expand - * @returns {string} Expanded path - */ - expandPath(inputPath) { - if (!inputPath) return inputPath; - - // Expand ~ to home directory - if (inputPath.startsWith('~')) { - return path.join(os.homedir(), inputPath.slice(1)); - } - - return inputPath; - }, -}; - -module.exports = { CLIUtils }; diff --git a/tools/cli/lib/config.js b/tools/cli/lib/config.js deleted file mode 100644 index a78250305..000000000 --- a/tools/cli/lib/config.js +++ /dev/null @@ -1,213 +0,0 @@ -const fs = require('fs-extra'); -const yaml = require('yaml'); -const path = require('node:path'); -const packageJson = require('../../../package.json'); - -/** - * Configuration utility class - */ -class Config { - /** - * Load a YAML configuration file - * @param {string} configPath - Path to config file - * @returns {Object} Parsed configuration - */ - async loadYaml(configPath) { - if (!(await fs.pathExists(configPath))) { - throw new Error(`Configuration file not found: ${configPath}`); - } - - const content = await fs.readFile(configPath, 'utf8'); - return yaml.parse(content); - } - - /** - * Save configuration to YAML file - * @param {string} configPath - Path to config file - * @param {Object} config - Configuration object - */ - async saveYaml(configPath, config) { - const yamlContent = yaml.dump(config, { - indent: 2, - lineWidth: 120, - noRefs: true, - }); - - await fs.ensureDir(path.dirname(configPath)); - // Ensure POSIX-compliant final newline - const content = yamlContent.endsWith('\n') ? yamlContent : yamlContent + '\n'; - await fs.writeFile(configPath, content, 'utf8'); - } - - /** - * Process configuration file (replace placeholders) - * @param {string} configPath - Path to config file - * @param {Object} replacements - Replacement values - */ - async processConfig(configPath, replacements = {}) { - let content = await fs.readFile(configPath, 'utf8'); - - // Standard replacements - const standardReplacements = { - '{project-root}': replacements.root || '', - '{module}': replacements.module || '', - '{version}': replacements.version || packageJson.version, - '{date}': new Date().toISOString().split('T')[0], - }; - - // Apply all replacements - const allReplacements = { ...standardReplacements, ...replacements }; - - for (const [placeholder, value] of Object.entries(allReplacements)) { - if (typeof placeholder === 'string' && typeof value === 'string') { - const regex = new RegExp(placeholder.replaceAll(/[.*+?^${}()|[\]\\]/g, String.raw`\$&`), 'g'); - content = content.replace(regex, value); - } - } - - await fs.writeFile(configPath, content, 'utf8'); - } - - /** - * Merge configurations - * @param {Object} base - Base configuration - * @param {Object} override - Override configuration - * @returns {Object} Merged configuration - */ - mergeConfigs(base, override) { - return this.deepMerge(base, override); - } - - /** - * Deep merge two objects - * @param {Object} target - Target object - * @param {Object} source - Source object - * @returns {Object} Merged object - */ - deepMerge(target, source) { - const output = { ...target }; - - if (this.isObject(target) && this.isObject(source)) { - for (const key of Object.keys(source)) { - if (this.isObject(source[key])) { - if (key in target) { - output[key] = this.deepMerge(target[key], source[key]); - } else { - output[key] = source[key]; - } - } else { - output[key] = source[key]; - } - } - } - - return output; - } - - /** - * Check if value is an object - * @param {*} item - Item to check - * @returns {boolean} True if object - */ - isObject(item) { - return item && typeof item === 'object' && !Array.isArray(item); - } - - /** - * Validate configuration against schema - * @param {Object} config - Configuration to validate - * @param {Object} schema - Validation schema - * @returns {Object} Validation result - */ - validateConfig(config, schema) { - const errors = []; - const warnings = []; - - // Check required fields - if (schema.required) { - for (const field of schema.required) { - if (!(field in config)) { - errors.push(`Missing required field: ${field}`); - } - } - } - - // Check field types - if (schema.properties) { - for (const [field, spec] of Object.entries(schema.properties)) { - if (field in config) { - const value = config[field]; - const expectedType = spec.type; - - if (expectedType === 'array' && !Array.isArray(value)) { - errors.push(`Field '${field}' should be an array`); - } else if (expectedType === 'object' && !this.isObject(value)) { - errors.push(`Field '${field}' should be an object`); - } else if (expectedType === 'string' && typeof value !== 'string') { - errors.push(`Field '${field}' should be a string`); - } else if (expectedType === 'number' && typeof value !== 'number') { - errors.push(`Field '${field}' should be a number`); - } else if (expectedType === 'boolean' && typeof value !== 'boolean') { - errors.push(`Field '${field}' should be a boolean`); - } - - // Check enum values - if (spec.enum && !spec.enum.includes(value)) { - errors.push(`Field '${field}' must be one of: ${spec.enum.join(', ')}`); - } - } - } - } - - return { - valid: errors.length === 0, - errors, - warnings, - }; - } - - /** - * Get configuration value with fallback - * @param {Object} config - Configuration object - * @param {string} path - Dot-notation path to value - * @param {*} defaultValue - Default value if not found - * @returns {*} Configuration value - */ - getValue(config, path, defaultValue = null) { - const keys = path.split('.'); - let current = config; - - for (const key of keys) { - if (current && typeof current === 'object' && key in current) { - current = current[key]; - } else { - return defaultValue; - } - } - - return current; - } - - /** - * Set configuration value - * @param {Object} config - Configuration object - * @param {string} path - Dot-notation path to value - * @param {*} value - Value to set - */ - setValue(config, path, value) { - const keys = path.split('.'); - const lastKey = keys.pop(); - let current = config; - - for (const key of keys) { - if (!(key in current) || typeof current[key] !== 'object') { - current[key] = {}; - } - current = current[key]; - } - - current[lastKey] = value; - } -} - -module.exports = { Config }; diff --git a/tools/cli/lib/file-ops.js b/tools/cli/lib/file-ops.js deleted file mode 100644 index 5cd7970d8..000000000 --- a/tools/cli/lib/file-ops.js +++ /dev/null @@ -1,204 +0,0 @@ -const fs = require('fs-extra'); -const path = require('node:path'); -const crypto = require('node:crypto'); - -/** - * File operations utility class - */ -class FileOps { - /** - * Copy a directory recursively - * @param {string} source - Source directory - * @param {string} dest - Destination directory - * @param {Object} options - Copy options - */ - async copyDirectory(source, dest, options = {}) { - const defaultOptions = { - overwrite: true, - errorOnExist: false, - filter: (src) => !this.shouldIgnore(src), - }; - - const copyOptions = { ...defaultOptions, ...options }; - await fs.copy(source, dest, copyOptions); - } - - /** - * Sync directory (selective copy preserving modifications) - * @param {string} source - Source directory - * @param {string} dest - Destination directory - */ - async syncDirectory(source, dest) { - const sourceFiles = await this.getFileList(source); - - for (const file of sourceFiles) { - const sourceFile = path.join(source, file); - const destFile = path.join(dest, file); - - // Check if destination file exists - if (await fs.pathExists(destFile)) { - // Compare checksums to see if file has been modified - const sourceHash = await this.getFileHash(sourceFile); - const destHash = await this.getFileHash(destFile); - - if (sourceHash === destHash) { - // Files are identical, safe to update - await fs.copy(sourceFile, destFile, { overwrite: true }); - } else { - // File has been modified, check timestamps - const sourceStats = await fs.stat(sourceFile); - const destStats = await fs.stat(destFile); - - if (sourceStats.mtime > destStats.mtime) { - // Source is newer, update - await fs.copy(sourceFile, destFile, { overwrite: true }); - } - // Otherwise, preserve user modifications - } - } else { - // New file, copy it - await fs.ensureDir(path.dirname(destFile)); - await fs.copy(sourceFile, destFile); - } - } - - // Remove files that no longer exist in source - const destFiles = await this.getFileList(dest); - for (const file of destFiles) { - const sourceFile = path.join(source, file); - const destFile = path.join(dest, file); - - if (!(await fs.pathExists(sourceFile))) { - await fs.remove(destFile); - } - } - } - - /** - * Get list of all files in a directory - * @param {string} dir - Directory path - * @returns {Array} List of relative file paths - */ - async getFileList(dir) { - const files = []; - - if (!(await fs.pathExists(dir))) { - return files; - } - - const walk = async (currentDir, baseDir) => { - const entries = await fs.readdir(currentDir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(currentDir, entry.name); - - if (entry.isDirectory() && !this.shouldIgnore(fullPath)) { - await walk(fullPath, baseDir); - } else if (entry.isFile() && !this.shouldIgnore(fullPath)) { - files.push(path.relative(baseDir, fullPath)); - } - } - }; - - await walk(dir, dir); - return files; - } - - /** - * Get file hash for comparison - * @param {string} filePath - File path - * @returns {string} File hash - */ - async getFileHash(filePath) { - const hash = crypto.createHash('sha256'); - const stream = fs.createReadStream(filePath); - - return new Promise((resolve, reject) => { - stream.on('data', (data) => hash.update(data)); - stream.on('end', () => resolve(hash.digest('hex'))); - stream.on('error', reject); - }); - } - - /** - * Check if a path should be ignored - * @param {string} filePath - Path to check - * @returns {boolean} True if should be ignored - */ - shouldIgnore(filePath) { - const ignoredPatterns = ['.git', '.DS_Store', 'node_modules', '*.swp', '*.tmp', '.idea', '.vscode', '__pycache__', '*.pyc']; - - const basename = path.basename(filePath); - - for (const pattern of ignoredPatterns) { - if (pattern.includes('*')) { - // Simple glob pattern matching - const regex = new RegExp(pattern.replace('*', '.*')); - if (regex.test(basename)) { - return true; - } - } else if (basename === pattern) { - return true; - } - } - - return false; - } - - /** - * Ensure directory exists - * @param {string} dir - Directory path - */ - async ensureDir(dir) { - await fs.ensureDir(dir); - } - - /** - * Remove directory or file - * @param {string} targetPath - Path to remove - */ - async remove(targetPath) { - if (await fs.pathExists(targetPath)) { - await fs.remove(targetPath); - } - } - - /** - * Read file content - * @param {string} filePath - File path - * @returns {string} File content - */ - async readFile(filePath) { - return await fs.readFile(filePath, 'utf8'); - } - - /** - * Write file content - * @param {string} filePath - File path - * @param {string} content - File content - */ - async writeFile(filePath, content) { - await fs.ensureDir(path.dirname(filePath)); - await fs.writeFile(filePath, content, 'utf8'); - } - - /** - * Check if path exists - * @param {string} targetPath - Path to check - * @returns {boolean} True if exists - */ - async exists(targetPath) { - return await fs.pathExists(targetPath); - } - - /** - * Get file or directory stats - * @param {string} targetPath - Path to check - * @returns {Object} File stats - */ - async stat(targetPath) { - return await fs.stat(targetPath); - } -} - -module.exports = { FileOps }; diff --git a/tools/cli/lib/platform-codes.js b/tools/cli/lib/platform-codes.js deleted file mode 100644 index bdf0e48c9..000000000 --- a/tools/cli/lib/platform-codes.js +++ /dev/null @@ -1,116 +0,0 @@ -const fs = require('fs-extra'); -const path = require('node:path'); -const yaml = require('yaml'); -const { getProjectRoot } = require('./project-root'); - -/** - * Platform Codes Manager - * Loads and provides access to the centralized platform codes configuration - */ -class PlatformCodes { - constructor() { - this.configPath = path.join(getProjectRoot(), 'tools', 'platform-codes.yaml'); - this.loadConfig(); - } - - /** - * Load the platform codes configuration - */ - loadConfig() { - try { - if (fs.existsSync(this.configPath)) { - const content = fs.readFileSync(this.configPath, 'utf8'); - this.config = yaml.parse(content); - } else { - console.warn(`Platform codes config not found at ${this.configPath}`); - this.config = { platforms: {} }; - } - } catch (error) { - console.error(`Error loading platform codes: ${error.message}`); - this.config = { platforms: {} }; - } - } - - /** - * Get all platform codes - * @returns {Object} All platform configurations - */ - getAllPlatforms() { - return this.config.platforms || {}; - } - - /** - * Get a specific platform configuration - * @param {string} code - Platform code - * @returns {Object|null} Platform configuration or null if not found - */ - getPlatform(code) { - return this.config.platforms[code] || null; - } - - /** - * Check if a platform code is valid - * @param {string} code - Platform code to validate - * @returns {boolean} True if valid - */ - isValidPlatform(code) { - return code in this.config.platforms; - } - - /** - * Get all preferred platforms - * @returns {Array} Array of preferred platform codes - */ - getPreferredPlatforms() { - return Object.entries(this.config.platforms) - .filter(([, config]) => config.preferred) - .map(([code]) => code); - } - - /** - * Get platforms by category - * @param {string} category - Category to filter by - * @returns {Array} Array of platform codes in the category - */ - getPlatformsByCategory(category) { - return Object.entries(this.config.platforms) - .filter(([, config]) => config.category === category) - .map(([code]) => code); - } - - /** - * Get platform display name - * @param {string} code - Platform code - * @returns {string} Display name or code if not found - */ - getDisplayName(code) { - const platform = this.getPlatform(code); - return platform ? platform.name : code; - } - - /** - * Validate platform code format - * @param {string} code - Platform code to validate - * @returns {boolean} True if format is valid - */ - isValidFormat(code) { - const conventions = this.config.conventions || {}; - const pattern = conventions.allowed_characters || 'a-z0-9-'; - const maxLength = conventions.max_code_length || 20; - - const regex = new RegExp(`^[${pattern}]+$`); - return regex.test(code) && code.length <= maxLength; - } - - /** - * Get all platform codes as array - * @returns {Array} Array of platform codes - */ - getCodes() { - return Object.keys(this.config.platforms); - } - config = null; -} - -// Export singleton instance -module.exports = new PlatformCodes(); diff --git a/tools/cli/lib/project-root.js b/tools/cli/lib/project-root.js deleted file mode 100644 index 4533c773c..000000000 --- a/tools/cli/lib/project-root.js +++ /dev/null @@ -1,77 +0,0 @@ -const path = require('node:path'); -const fs = require('fs-extra'); - -/** - * Find the BMAD project root directory by looking for package.json - * or specific BMAD markers - */ -function findProjectRoot(startPath = __dirname) { - let currentPath = path.resolve(startPath); - - // Keep going up until we find package.json with bmad-method - while (currentPath !== path.dirname(currentPath)) { - const packagePath = path.join(currentPath, 'package.json'); - - if (fs.existsSync(packagePath)) { - try { - const pkg = fs.readJsonSync(packagePath); - // Check if this is the BMAD project - if (pkg.name === 'bmad-method' || fs.existsSync(path.join(currentPath, 'src', 'core'))) { - return currentPath; - } - } catch { - // Continue searching - } - } - - // Also check for src/core as a marker - if (fs.existsSync(path.join(currentPath, 'src', 'core', 'agents'))) { - return currentPath; - } - - currentPath = path.dirname(currentPath); - } - - // If we can't find it, use process.cwd() as fallback - return process.cwd(); -} - -// Cache the project root after first calculation -let cachedRoot = null; - -function getProjectRoot() { - if (!cachedRoot) { - cachedRoot = findProjectRoot(); - } - return cachedRoot; -} - -/** - * Get path to source directory - */ -function getSourcePath(...segments) { - return path.join(getProjectRoot(), 'src', ...segments); -} - -/** - * Get path to a module's directory - * bmm is a built-in module directly under src/ - * core is also directly under src/ - * All other modules are stored remote - */ -function getModulePath(moduleName, ...segments) { - if (moduleName === 'core') { - return getSourcePath('core', ...segments); - } - if (moduleName === 'bmm') { - return getSourcePath('bmm', ...segments); - } - return getSourcePath('modules', moduleName, ...segments); -} - -module.exports = { - getProjectRoot, - getSourcePath, - getModulePath, - findProjectRoot, -}; diff --git a/tools/cli/lib/prompts.js b/tools/cli/lib/prompts.js deleted file mode 100644 index 24500700b..000000000 --- a/tools/cli/lib/prompts.js +++ /dev/null @@ -1,809 +0,0 @@ -/** - * @clack/prompts wrapper for BMAD CLI - * - * This module provides a unified interface for CLI prompts using @clack/prompts. - * It replaces Inquirer.js to fix Windows arrow key navigation issues (libuv #852). - * - * @module prompts - */ - -let _clack = null; -let _clackCore = null; -let _picocolors = null; - -/** - * Lazy-load @clack/prompts (ESM module) - * @returns {Promise<Object>} The clack prompts module - */ -async function getClack() { - if (!_clack) { - _clack = await import('@clack/prompts'); - } - return _clack; -} - -/** - * Lazy-load @clack/core (ESM module) - * @returns {Promise<Object>} The clack core module - */ -async function getClackCore() { - if (!_clackCore) { - _clackCore = await import('@clack/core'); - } - return _clackCore; -} - -/** - * Lazy-load picocolors - * @returns {Promise<Object>} The picocolors module - */ -async function getPicocolors() { - if (!_picocolors) { - _picocolors = (await import('picocolors')).default; - } - return _picocolors; -} - -/** - * Handle user cancellation gracefully - * @param {any} value - The value to check - * @param {string} [message='Operation cancelled'] - Message to display - * @returns {boolean} True if cancelled - */ -async function handleCancel(value, message = 'Operation cancelled') { - const clack = await getClack(); - if (clack.isCancel(value)) { - clack.cancel(message); - process.exit(0); - } - return false; -} - -/** - * Display intro message - * @param {string} message - The intro message - */ -async function intro(message) { - const clack = await getClack(); - clack.intro(message); -} - -/** - * Display outro message - * @param {string} message - The outro message - */ -async function outro(message) { - const clack = await getClack(); - clack.outro(message); -} - -/** - * Display a note/info box - * @param {string} message - The note content - * @param {string} [title] - Optional title - */ -async function note(message, title) { - const clack = await getClack(); - clack.note(message, title); -} - -/** - * Display a spinner for async operations - * Wraps @clack/prompts spinner with isSpinning state tracking - * @returns {Object} Spinner controller with start, stop, message, error, cancel, clear, isSpinning - */ -async function spinner() { - const clack = await getClack(); - const s = clack.spinner(); - let spinning = false; - - return { - start: (msg) => { - if (spinning) { - s.message(msg); - } else { - spinning = true; - s.start(msg); - } - }, - stop: (msg) => { - if (spinning) { - spinning = false; - s.stop(msg); - } - }, - message: (msg) => { - if (spinning) s.message(msg); - }, - error: (msg) => { - spinning = false; - s.error(msg); - }, - cancel: (msg) => { - spinning = false; - s.cancel(msg); - }, - clear: () => { - spinning = false; - s.clear(); - }, - get isSpinning() { - return spinning; - }, - get isCancelled() { - return s.isCancelled; - }, - }; -} - -/** - * Single-select prompt (replaces Inquirer 'list' type) - * @param {Object} options - Prompt options - * @param {string} options.message - The question to ask - * @param {Array} options.choices - Array of choices [{name, value, hint?}] - * @param {any} [options.default] - Default selected value - * @returns {Promise<any>} Selected value - */ -async function select(options) { - const clack = await getClack(); - - // Convert Inquirer-style choices to clack format - // Handle both object choices {name, value, hint} and primitive choices (string/number) - const clackOptions = options.choices - .filter((c) => c.type !== 'separator') // Skip separators for now - .map((choice) => { - if (typeof choice === 'string' || typeof choice === 'number') { - return { value: choice, label: String(choice) }; - } - return { - value: choice.value === undefined ? choice.name : choice.value, - label: choice.name || choice.label || String(choice.value), - hint: choice.hint || choice.description, - }; - }); - - // Find initial value - let initialValue; - if (options.default !== undefined) { - initialValue = options.default; - } - - const result = await clack.select({ - message: options.message, - options: clackOptions, - initialValue, - }); - - await handleCancel(result); - return result; -} - -/** - * Multi-select prompt (replaces Inquirer 'checkbox' type) - * @param {Object} options - Prompt options - * @param {string} options.message - The question to ask - * @param {Array} options.choices - Array of choices [{name, value, checked?, hint?}] - * @param {boolean} [options.required=false] - Whether at least one must be selected - * @returns {Promise<Array>} Array of selected values - */ -async function multiselect(options) { - const clack = await getClack(); - - // Support both clack-native (options) and Inquirer-style (choices) APIs - let clackOptions; - let initialValues; - - if (options.options) { - // Native clack format: options with label/value - clackOptions = options.options; - initialValues = options.initialValues || []; - } else { - // Convert Inquirer-style choices to clack format - // Handle both object choices {name, value, hint} and primitive choices (string/number) - clackOptions = options.choices - .filter((c) => c.type !== 'separator') // Skip separators - .map((choice) => { - if (typeof choice === 'string' || typeof choice === 'number') { - return { value: choice, label: String(choice) }; - } - return { - value: choice.value === undefined ? choice.name : choice.value, - label: choice.name || choice.label || String(choice.value), - hint: choice.hint || choice.description, - }; - }); - - // Find initial values (pre-checked items) - initialValues = options.choices - .filter((c) => c.checked && c.type !== 'separator') - .map((c) => (c.value === undefined ? c.name : c.value)); - } - - const result = await clack.multiselect({ - message: options.message, - options: clackOptions, - initialValues: initialValues.length > 0 ? initialValues : undefined, - required: options.required || false, - }); - - await handleCancel(result); - return result; -} - -/** - * Default filter function for autocomplete - case-insensitive label matching - * @param {string} search - Search string - * @param {Object} option - Option object with label - * @returns {boolean} Whether the option matches - */ -function defaultAutocompleteFilter(search, option) { - const label = option.label ?? String(option.value ?? ''); - return label.toLowerCase().includes(search.toLowerCase()); -} - -/** - * Autocomplete multi-select prompt with type-ahead filtering - * Custom implementation that always shows "Space/Tab:" in the hint - * @param {Object} options - Prompt options - * @param {string} options.message - The question to ask - * @param {Array} options.options - Array of choices [{label, value, hint?}] - * @param {string} [options.placeholder] - Placeholder text for search input - * @param {Array} [options.initialValues] - Array of initially selected values - * @param {boolean} [options.required=false] - Whether at least one must be selected - * @param {number} [options.maxItems=5] - Maximum visible items in scrollable list - * @param {Function} [options.filter] - Custom filter function (search, option) => boolean - * @param {Array} [options.lockedValues] - Values that are always selected and cannot be toggled off - * @returns {Promise<Array>} Array of selected values - */ -async function autocompleteMultiselect(options) { - const core = await getClackCore(); - const clack = await getClack(); - const color = await getPicocolors(); - - const filterFn = options.filter ?? defaultAutocompleteFilter; - const lockedSet = new Set(options.lockedValues || []); - - const prompt = new core.AutocompletePrompt({ - options: options.options, - multiple: true, - filter: filterFn, - validate: () => { - if (options.required && prompt.selectedValues.length === 0) { - return 'Please select at least one item'; - } - }, - initialValue: [...new Set([...(options.initialValues || []), ...(options.lockedValues || [])])], - render() { - const barColor = this.state === 'error' ? color.yellow : color.cyan; - const bar = barColor(clack.S_BAR); - const barEnd = barColor(clack.S_BAR_END); - - const title = `${color.gray(clack.S_BAR)}\n${clack.symbol(this.state)} ${options.message}\n`; - - const userInput = this.userInput; - const placeholder = options.placeholder || 'Type to search...'; - const hasPlaceholder = userInput === '' && placeholder !== undefined; - - // Show placeholder or user input with cursor - const searchDisplay = - this.isNavigating || hasPlaceholder ? color.dim(hasPlaceholder ? placeholder : userInput) : this.userInputWithCursor; - - const allOptions = this.options; - const matchCount = - this.filteredOptions.length === allOptions.length - ? '' - : color.dim(` (${this.filteredOptions.length} match${this.filteredOptions.length === 1 ? '' : 'es'})`); - - // Render option with checkbox - const renderOption = (opt, isHighlighted) => { - const isSelected = this.selectedValues.includes(opt.value); - const isLocked = lockedSet.has(opt.value); - const label = opt.label ?? String(opt.value ?? ''); - const hintText = opt.hint && isHighlighted ? color.dim(` (${opt.hint})`) : ''; - - let checkbox; - if (isLocked) { - checkbox = color.green(clack.S_CHECKBOX_SELECTED); - const lockHint = color.dim(' (always installed)'); - return isHighlighted ? `${checkbox} ${label}${lockHint}` : `${checkbox} ${color.dim(label)}${lockHint}`; - } - checkbox = isSelected ? color.green(clack.S_CHECKBOX_SELECTED) : color.dim(clack.S_CHECKBOX_INACTIVE); - return isHighlighted ? `${checkbox} ${label}${hintText}` : `${checkbox} ${color.dim(label)}`; - }; - - switch (this.state) { - case 'submit': { - return `${title}${color.gray(clack.S_BAR)} ${color.dim(`${this.selectedValues.length} items selected`)}`; - } - - case 'cancel': { - return `${title}${color.gray(clack.S_BAR)} ${color.strikethrough(color.dim(userInput))}`; - } - - default: { - // Always show "SPACE:" regardless of isNavigating state - const hints = [`${color.dim('↑/↓')} to navigate`, `${color.dim('TAB/SPACE:')} select`, `${color.dim('ENTER:')} confirm`]; - - const noMatchesLine = this.filteredOptions.length === 0 && userInput ? [`${bar} ${color.yellow('No matches found')}`] : []; - - const errorLine = this.state === 'error' ? [`${bar} ${color.yellow(this.error)}`] : []; - - const headerLines = [...`${title}${bar}`.split('\n'), `${bar} ${searchDisplay}${matchCount}`, ...noMatchesLine, ...errorLine]; - - const footerLines = [`${bar} ${color.dim(hints.join(' • '))}`, `${barEnd}`]; - - const optionLines = clack.limitOptions({ - cursor: this.cursor, - options: this.filteredOptions, - style: renderOption, - maxItems: options.maxItems || 5, - output: options.output, - rowPadding: headerLines.length + footerLines.length, - }); - - return [...headerLines, ...optionLines.map((line) => `${bar} ${line}`), ...footerLines].join('\n'); - } - } - }, - }); - - // Prevent locked values from being toggled off - if (lockedSet.size > 0) { - const originalToggle = prompt.toggleSelected.bind(prompt); - prompt.toggleSelected = function (value) { - // If locked and already selected, skip the toggle (would deselect) - if (lockedSet.has(value) && this.selectedValues.includes(value)) { - return; - } - originalToggle(value); - }; - } - - // === FIX: Make SPACE always act as selection key (not search input) === - // Override _isActionKey to treat SPACE like TAB - always an action key - // This prevents SPACE from being added to the search input - const originalIsActionKey = prompt._isActionKey.bind(prompt); - prompt._isActionKey = function (char, key) { - if (key && key.name === 'space') { - return true; - } - return originalIsActionKey(char, key); - }; - - // Handle SPACE toggle when NOT navigating (internal code only handles it when isNavigating=true) - prompt.on('key', (char, key) => { - if (key && key.name === 'space' && !prompt.isNavigating) { - const focused = prompt.filteredOptions[prompt.cursor]; - if (focused) prompt.toggleSelected(focused.value); - } - }); - // === END FIX === - - const result = await prompt.prompt(); - await handleCancel(result); - return result; -} - -/** - * Confirm prompt (replaces Inquirer 'confirm' type) - * @param {Object} options - Prompt options - * @param {string} options.message - The question to ask - * @param {boolean} [options.default=true] - Default value - * @returns {Promise<boolean>} User's answer - */ -async function confirm(options) { - const clack = await getClack(); - - const result = await clack.confirm({ - message: options.message, - initialValue: options.default === undefined ? true : options.default, - }); - - await handleCancel(result); - return result; -} - -/** - * Text input prompt with Tab-to-fill-placeholder support (replaces Inquirer 'input' type) - * - * This custom implementation restores the Tab-to-fill-placeholder behavior that was - * intentionally removed in @clack/prompts v1.0.0 (placeholder became purely visual). - * Uses @clack/core's TextPrompt primitive with custom key handling. - * - * @param {Object} options - Prompt options - * @param {string} options.message - The question to ask - * @param {string} [options.default] - Default value - * @param {string} [options.placeholder] - Placeholder text (defaults to options.default if not provided) - * @param {Function} [options.validate] - Validation function - * @returns {Promise<string>} User's input - */ -async function text(options) { - const core = await getClackCore(); - const color = await getPicocolors(); - - // Use default as placeholder if placeholder not explicitly provided - // This shows the default value as grayed-out hint text - const placeholder = options.placeholder === undefined ? options.default : options.placeholder; - const defaultValue = options.default; - - const prompt = new core.TextPrompt({ - defaultValue, - validate: options.validate, - render() { - const title = `${color.gray('◆')} ${options.message}`; - - // Show placeholder as dim text when input is empty - let valueDisplay; - if (this.state === 'error') { - valueDisplay = color.yellow(this.userInputWithCursor); - } else if (this.userInput) { - valueDisplay = this.userInputWithCursor; - } else if (placeholder) { - // Show placeholder with cursor indicator when empty - valueDisplay = `${color.inverse(color.hidden('_'))}${color.dim(placeholder)}`; - } else { - valueDisplay = color.inverse(color.hidden('_')); - } - - const bar = color.gray('│'); - - // Handle different states - if (this.state === 'submit') { - return `${color.gray('◇')} ${options.message}\n${bar} ${color.dim(this.value || defaultValue || '')}`; - } - - if (this.state === 'cancel') { - return `${color.gray('◇')} ${options.message}\n${bar} ${color.strikethrough(color.dim(this.userInput || ''))}`; - } - - if (this.state === 'error') { - return `${color.yellow('▲')} ${options.message}\n${bar} ${valueDisplay}\n${color.yellow('│')} ${color.yellow(this.error)}`; - } - - return `${title}\n${bar} ${valueDisplay}\n${bar}`; - }, - }); - - // Add Tab key handler to fill placeholder into input - prompt.on('key', (char) => { - if (char === '\t' && placeholder && !prompt.userInput) { - // Use _setUserInput with write=true to populate the readline and update internal state - prompt._setUserInput(placeholder, true); - } - }); - - const result = await prompt.prompt(); - await handleCancel(result); - - // TextPrompt's finalize handler already applies defaultValue for empty input - return result; -} - -/** - * Password input prompt (replaces Inquirer 'password' type) - * @param {Object} options - Prompt options - * @param {string} options.message - The question to ask - * @param {Function} [options.validate] - Validation function - * @returns {Promise<string>} User's input - */ -async function password(options) { - const clack = await getClack(); - - const result = await clack.password({ - message: options.message, - validate: options.validate, - }); - - await handleCancel(result); - return result; -} - -/** - * Group multiple prompts together - * @param {Object} prompts - Object of prompt functions - * @param {Object} [options] - Group options - * @returns {Promise<Object>} Object with all answers - */ -async function group(prompts, options = {}) { - const clack = await getClack(); - - const result = await clack.group(prompts, { - onCancel: () => { - clack.cancel('Operation cancelled'); - process.exit(0); - }, - ...options, - }); - - return result; -} - -/** - * Run tasks with spinner feedback - * @param {Array} tasks - Array of task objects [{title, task, enabled?}] - * @returns {Promise<void>} - */ -async function tasks(taskList) { - const clack = await getClack(); - await clack.tasks(taskList); -} - -/** - * Log messages with styling - */ -const log = { - async info(message) { - const clack = await getClack(); - clack.log.info(message); - }, - async success(message) { - const clack = await getClack(); - clack.log.success(message); - }, - async warn(message) { - const clack = await getClack(); - clack.log.warn(message); - }, - async error(message) { - const clack = await getClack(); - clack.log.error(message); - }, - async message(message) { - const clack = await getClack(); - clack.log.message(message); - }, - async step(message) { - const clack = await getClack(); - clack.log.step(message); - }, -}; - -/** - * Display cancellation message - * @param {string} [message='Operation cancelled'] - The cancellation message - */ -async function cancel(message = 'Operation cancelled') { - const clack = await getClack(); - clack.cancel(message); -} - -/** - * Display content in a styled box - * @param {string} content - The box content - * @param {string} [title] - Optional title - * @param {Object} [options] - Box options (contentAlign, titleAlign, width, rounded, formatBorder, etc.) - */ -async function box(content, title, options) { - const clack = await getClack(); - clack.box(content, title, options); -} - -/** - * Create a progress bar for visualizing task completion - * @param {Object} [options] - Progress options (max, style, etc.) - * @returns {Promise<Object>} Progress controller with start, advance, stop methods - */ -async function progress(options) { - const clack = await getClack(); - return clack.progress(options); -} - -/** - * Create a task log for displaying scrolling subprocess output - * @param {Object} options - TaskLog options (title, limit, retainLog) - * @returns {Promise<Object>} TaskLog controller with message, success, error methods - */ -async function taskLog(options) { - const clack = await getClack(); - return clack.taskLog(options); -} - -/** - * File system path prompt with autocomplete - * @param {Object} options - Path options - * @param {string} options.message - The prompt message - * @param {string} [options.initialValue] - Initial path value - * @param {boolean} [options.directory=false] - Only allow directories - * @param {Function} [options.validate] - Validation function - * @returns {Promise<string>} Selected path - */ -async function pathPrompt(options) { - const clack = await getClack(); - const result = await clack.path(options); - await handleCancel(result); - return result; -} - -/** - * Autocomplete single-select prompt with type-ahead filtering - * @param {Object} options - Autocomplete options - * @param {string} options.message - The prompt message - * @param {Array} options.options - Array of choices [{value, label, hint?}] - * @param {string} [options.placeholder] - Placeholder text - * @param {number} [options.maxItems] - Maximum visible items - * @param {Function} [options.filter] - Custom filter function - * @returns {Promise<any>} Selected value - */ -async function autocomplete(options) { - const clack = await getClack(); - const result = await clack.autocomplete(options); - await handleCancel(result); - return result; -} - -/** - * Key-based instant selection prompt - * @param {Object} options - SelectKey options - * @param {string} options.message - The prompt message - * @param {Array} options.options - Array of choices [{value, label, hint?}] - * @returns {Promise<any>} Selected value - */ -async function selectKey(options) { - const clack = await getClack(); - const result = await clack.selectKey(options); - await handleCancel(result); - return result; -} - -/** - * Stream messages with dynamic content (for LLMs, generators, etc.) - */ -const stream = { - async info(generator) { - const clack = await getClack(); - return clack.stream.info(generator); - }, - async success(generator) { - const clack = await getClack(); - return clack.stream.success(generator); - }, - async step(generator) { - const clack = await getClack(); - return clack.stream.step(generator); - }, - async warn(generator) { - const clack = await getClack(); - return clack.stream.warn(generator); - }, - async error(generator) { - const clack = await getClack(); - return clack.stream.error(generator); - }, - async message(generator, options) { - const clack = await getClack(); - return clack.stream.message(generator, options); - }, -}; - -/** - * Get the color utility (picocolors instance from @clack/prompts) - * @returns {Promise<Object>} The color utility (picocolors) - */ -async function getColor() { - return await getPicocolors(); -} - -/** - * Execute an array of Inquirer-style questions using @clack/prompts - * This provides compatibility with dynamic question arrays - * @param {Array} questions - Array of Inquirer-style question objects - * @returns {Promise<Object>} Object with answers keyed by question name - */ -async function prompt(questions) { - const answers = {}; - - for (const question of questions) { - const { type, name, message, choices, default: defaultValue, validate, when } = question; - - // Handle conditional questions via 'when' property - if (when !== undefined) { - const shouldAsk = typeof when === 'function' ? await when(answers) : when; - if (!shouldAsk) continue; - } - - let answer; - - switch (type) { - case 'input': { - // Note: @clack/prompts doesn't support async validation, so validate must be sync - answer = await text({ - message, - default: typeof defaultValue === 'function' ? defaultValue(answers) : defaultValue, - validate: validate - ? (val) => { - const result = validate(val, answers); - if (result instanceof Promise) { - throw new TypeError('Async validation is not supported by @clack/prompts. Please use synchronous validation.'); - } - return result === true ? undefined : result; - } - : undefined, - }); - break; - } - - case 'confirm': { - answer = await confirm({ - message, - default: typeof defaultValue === 'function' ? defaultValue(answers) : defaultValue, - }); - break; - } - - case 'list': { - answer = await select({ - message, - choices: choices || [], - default: typeof defaultValue === 'function' ? defaultValue(answers) : defaultValue, - }); - break; - } - - case 'checkbox': { - answer = await multiselect({ - message, - choices: choices || [], - required: false, - }); - break; - } - - case 'password': { - // Note: @clack/prompts doesn't support async validation, so validate must be sync - answer = await password({ - message, - validate: validate - ? (val) => { - const result = validate(val, answers); - if (result instanceof Promise) { - throw new TypeError('Async validation is not supported by @clack/prompts. Please use synchronous validation.'); - } - return result === true ? undefined : result; - } - : undefined, - }); - break; - } - - default: { - // Default to text input for unknown types - answer = await text({ - message, - default: typeof defaultValue === 'function' ? defaultValue(answers) : defaultValue, - }); - } - } - - answers[name] = answer; - } - - return answers; -} - -module.exports = { - getClack, - getColor, - handleCancel, - intro, - outro, - cancel, - note, - box, - spinner, - progress, - taskLog, - select, - multiselect, - autocompleteMultiselect, - autocomplete, - selectKey, - confirm, - text, - path: pathPrompt, - password, - group, - tasks, - log, - stream, - prompt, -}; diff --git a/tools/cli/lib/ui.js b/tools/cli/lib/ui.js deleted file mode 100644 index 1338c1f17..000000000 --- a/tools/cli/lib/ui.js +++ /dev/null @@ -1,1936 +0,0 @@ -const path = require('node:path'); -const os = require('node:os'); -const fs = require('fs-extra'); -const { CLIUtils } = require('./cli-utils'); -const { CustomHandler } = require('../installers/lib/custom/handler'); -const { ExternalModuleManager } = require('../installers/lib/modules/external-manager'); -const prompts = require('./prompts'); - -// Separator class for visual grouping in select/multiselect prompts -// Note: @clack/prompts doesn't support separators natively, they are filtered out -class Separator { - constructor(text = '────────') { - this.line = text; - this.name = text; - } - type = 'separator'; -} - -// Separator for choice lists (compatible interface) -const choiceUtils = { Separator }; - -/** - * UI utilities for the installer - */ -class UI { - /** - * Prompt for installation configuration - * @param {Object} options - Command-line options from install command - * @returns {Object} Installation configuration - */ - async promptInstall(options = {}) { - await CLIUtils.displayLogo(); - - // Display version-specific start message from install-messages.yaml - const { MessageLoader } = require('../installers/lib/message-loader'); - const messageLoader = new MessageLoader(); - await messageLoader.displayStartMessage(); - - // Get directory from options or prompt - let confirmedDirectory; - if (options.directory) { - // Use provided directory from command-line - const expandedDir = this.expandUserPath(options.directory); - const validation = this.validateDirectorySync(expandedDir); - if (validation) { - throw new Error(`Invalid directory: ${validation}`); - } - confirmedDirectory = expandedDir; - await prompts.log.info(`Using directory from command-line: ${confirmedDirectory}`); - } else { - confirmedDirectory = await this.getConfirmedDirectory(); - } - - // Preflight: Check for legacy BMAD v4 footprints immediately after getting directory - const { Detector } = require('../installers/lib/core/detector'); - const { Installer } = require('../installers/lib/core/installer'); - const detector = new Detector(); - const installer = new Installer(); - const legacyV4 = await detector.detectLegacyV4(confirmedDirectory); - if (legacyV4.hasLegacyV4) { - await installer.handleLegacyV4Migration(confirmedDirectory, legacyV4); - } - - // Check for legacy folders and prompt for rename before showing any menus - let hasLegacyCfg = false; - let hasLegacyBmadFolder = false; - let bmadDir = null; - let legacyBmadPath = null; - - // First check for legacy .bmad folder (instead of _bmad) - // Only check if directory exists - if (await fs.pathExists(confirmedDirectory)) { - const entries = await fs.readdir(confirmedDirectory, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isDirectory() && (entry.name === '.bmad' || entry.name === 'bmad')) { - hasLegacyBmadFolder = true; - legacyBmadPath = path.join(confirmedDirectory, entry.name); - bmadDir = legacyBmadPath; - - // Check if it has _cfg folder - const cfgPath = path.join(legacyBmadPath, '_cfg'); - if (await fs.pathExists(cfgPath)) { - hasLegacyCfg = true; - } - break; - } - } - } - - // If no .bmad or bmad found, check for current installations _bmad - if (!hasLegacyBmadFolder) { - const bmadResult = await installer.findBmadDir(confirmedDirectory); - bmadDir = bmadResult.bmadDir; - hasLegacyCfg = bmadResult.hasLegacyCfg; - } - - // Handle legacy .bmad or _cfg folder - these are very old (v4 or alpha) - // Show version warning instead of offering conversion - if (hasLegacyBmadFolder || hasLegacyCfg) { - await prompts.log.warn('LEGACY INSTALLATION DETECTED'); - await prompts.note( - 'Found a ".bmad"/"bmad" folder, or a legacy "_cfg" folder under the bmad folder -\n' + - 'this is from an old BMAD version that is out of date for automatic upgrade,\n' + - 'manual intervention required.\n\n' + - 'You have a legacy version installed (v4 or alpha).\n' + - 'Legacy installations may have compatibility issues.\n\n' + - 'For the best experience, we strongly recommend:\n' + - ' 1. Delete your current BMAD installation folder (.bmad or bmad)\n' + - ' 2. Run a fresh installation\n\n' + - 'If you do not want to start fresh, you can attempt to proceed beyond this\n' + - 'point IF you have ensured the bmad folder is named _bmad, and under it there\n' + - 'is a _config folder. If you have a folder under your bmad folder named _cfg,\n' + - 'you would need to rename it _config, and then restart the installer.\n\n' + - 'Benefits of a fresh install:\n' + - ' \u2022 Cleaner configuration without legacy artifacts\n' + - ' \u2022 All new features properly configured\n' + - ' \u2022 Fewer potential conflicts\n\n' + - 'If you have already produced output from an earlier alpha version, you can\n' + - 'still retain those artifacts. After installation, ensure you configured during\n' + - 'install the proper file locations for artifacts depending on the module you\n' + - 'are using, or move the files to the proper locations.', - 'Legacy Installation Detected', - ); - - const proceed = await prompts.select({ - message: 'How would you like to proceed?', - choices: [ - { - name: 'Cancel and do a fresh install (recommended)', - value: 'cancel', - }, - { - name: 'Proceed anyway (will attempt update, potentially may fail or have unstable behavior)', - value: 'proceed', - }, - ], - default: 'cancel', - }); - - if (proceed === 'cancel') { - await prompts.note('1. Delete the existing bmad folder in your project\n' + "2. Run 'bmad install' again", 'To do a fresh install'); - process.exit(0); - return; - } - - const s = await prompts.spinner(); - s.start('Updating folder structure...'); - try { - // Handle .bmad folder - if (hasLegacyBmadFolder) { - const newBmadPath = path.join(confirmedDirectory, '_bmad'); - await fs.move(legacyBmadPath, newBmadPath); - bmadDir = newBmadPath; - s.stop(`Renamed "${path.basename(legacyBmadPath)}" to "_bmad"`); - } - - // Handle _cfg folder (either from .bmad or standalone) - const cfgPath = path.join(bmadDir, '_cfg'); - if (await fs.pathExists(cfgPath)) { - s.start('Renaming configuration folder...'); - const newCfgPath = path.join(bmadDir, '_config'); - await fs.move(cfgPath, newCfgPath); - s.stop('Renamed "_cfg" to "_config"'); - } - } catch (error) { - s.stop('Failed to update folder structure'); - await prompts.log.error(`Error: ${error.message}`); - process.exit(1); - } - } - - // Check if there's an existing BMAD installation (after any folder renames) - const hasExistingInstall = await fs.pathExists(bmadDir); - - let customContentConfig = { hasCustomContent: false }; - if (!hasExistingInstall) { - customContentConfig._shouldAsk = true; - } - - // Track action type (only set if there's an existing installation) - let actionType; - - // Only show action menu if there's an existing installation - if (hasExistingInstall) { - // Get version information - const { existingInstall, bmadDir } = await this.getExistingInstallation(confirmedDirectory); - const packageJsonPath = path.join(__dirname, '../../../package.json'); - const currentVersion = require(packageJsonPath).version; - const installedVersion = existingInstall.version || 'unknown'; - - // Check if version is pre beta - const shouldProceed = await this.showLegacyVersionWarning(installedVersion, currentVersion, path.basename(bmadDir), options); - - // If user chose to cancel, exit the installer - if (!shouldProceed) { - process.exit(0); - return; - } - - // Build menu choices dynamically - const choices = []; - - // Always show Quick Update first (allows refreshing installation even on same version) - if (installedVersion !== 'unknown') { - choices.push({ - name: `Quick Update (v${installedVersion} → v${currentVersion})`, - value: 'quick-update', - }); - } - - // Add custom agent compilation option - if (installedVersion !== 'unknown') { - choices.push({ - name: 'Recompile Agents (apply customizations only)', - value: 'compile-agents', - }); - } - - // Common actions - choices.push({ name: 'Modify BMAD Installation', value: 'update' }); - - // Check if action is provided via command-line - if (options.action) { - const validActions = choices.map((c) => c.value); - if (!validActions.includes(options.action)) { - throw new Error(`Invalid action: ${options.action}. Valid actions: ${validActions.join(', ')}`); - } - actionType = options.action; - await prompts.log.info(`Using action from command-line: ${actionType}`); - } else if (options.yes) { - // Default to quick-update if available, otherwise first available choice - if (choices.length === 0) { - throw new Error('No valid actions available for this installation'); - } - const hasQuickUpdate = choices.some((c) => c.value === 'quick-update'); - actionType = hasQuickUpdate ? 'quick-update' : choices[0].value; - await prompts.log.info(`Non-interactive mode (--yes): defaulting to ${actionType}`); - } else { - actionType = await prompts.select({ - message: 'How would you like to proceed?', - choices: choices, - default: choices[0].value, - }); - } - - // Handle quick update separately - if (actionType === 'quick-update') { - // Pass --custom-content through so installer can re-cache if cache is missing - let customContentForQuickUpdate = { hasCustomContent: false }; - if (options.customContent) { - const paths = options.customContent - .split(',') - .map((p) => p.trim()) - .filter(Boolean); - if (paths.length > 0) { - const customPaths = []; - const selectedModuleIds = []; - const sources = []; - for (const customPath of paths) { - const expandedPath = this.expandUserPath(customPath); - const validation = this.validateCustomContentPathSync(expandedPath); - if (validation) continue; - let moduleMeta; - try { - const moduleYamlPath = path.join(expandedPath, 'module.yaml'); - moduleMeta = require('yaml').parse(await fs.readFile(moduleYamlPath, 'utf-8')); - } catch { - continue; - } - if (!moduleMeta?.code) continue; - customPaths.push(expandedPath); - selectedModuleIds.push(moduleMeta.code); - sources.push({ path: expandedPath, id: moduleMeta.code, name: moduleMeta.name || moduleMeta.code }); - } - if (customPaths.length > 0) { - customContentForQuickUpdate = { - hasCustomContent: true, - selected: true, - sources, - selectedFiles: customPaths.map((p) => path.join(p, 'module.yaml')), - selectedModuleIds, - }; - } - } - } - return { - actionType: 'quick-update', - directory: confirmedDirectory, - customContent: customContentForQuickUpdate, - skipPrompts: options.yes || false, - }; - } - - // Handle compile agents separately - if (actionType === 'compile-agents') { - // Only recompile agents with customizations, don't update any files - return { - actionType: 'compile-agents', - directory: confirmedDirectory, - customContent: { hasCustomContent: false }, - skipPrompts: options.yes || false, - }; - } - - // If actionType === 'update', handle it with the new flow - // Return early with modify configuration - if (actionType === 'update') { - // Get existing installation info - const { installedModuleIds } = await this.getExistingInstallation(confirmedDirectory); - - await prompts.log.message(`Found existing modules: ${[...installedModuleIds].join(', ')}`); - - // Unified module selection - all modules in one grouped multiselect - let selectedModules; - if (options.modules) { - // Use modules from command-line - selectedModules = options.modules - .split(',') - .map((m) => m.trim()) - .filter(Boolean); - await prompts.log.info(`Using modules from command-line: ${selectedModules.join(', ')}`); - } else if (options.yes) { - selectedModules = await this.getDefaultModules(installedModuleIds); - await prompts.log.info( - `Non-interactive mode (--yes): using default modules (installed + defaults): ${selectedModules.join(', ')}`, - ); - } else { - selectedModules = await this.selectAllModules(installedModuleIds); - } - - // After module selection, ask about custom modules - let customModuleResult = { selectedCustomModules: [], customContentConfig: { hasCustomContent: false } }; - - if (options.customContent) { - // Use custom content from command-line - const paths = options.customContent - .split(',') - .map((p) => p.trim()) - .filter(Boolean); - await prompts.log.info(`Using custom content from command-line: ${paths.join(', ')}`); - - // Build custom content config similar to promptCustomContentSource - const customPaths = []; - const selectedModuleIds = []; - const sources = []; - - for (const customPath of paths) { - const expandedPath = this.expandUserPath(customPath); - const validation = this.validateCustomContentPathSync(expandedPath); - if (validation) { - await prompts.log.warn(`Skipping invalid custom content path: ${customPath} - ${validation}`); - continue; - } - - // Read module metadata - let moduleMeta; - try { - const moduleYamlPath = path.join(expandedPath, 'module.yaml'); - const moduleYaml = await fs.readFile(moduleYamlPath, 'utf-8'); - const yaml = require('yaml'); - moduleMeta = yaml.parse(moduleYaml); - } catch (error) { - await prompts.log.warn(`Skipping custom content path: ${customPath} - failed to read module.yaml: ${error.message}`); - continue; - } - - if (!moduleMeta) { - await prompts.log.warn(`Skipping custom content path: ${customPath} - module.yaml is empty`); - continue; - } - - if (!moduleMeta.code) { - await prompts.log.warn(`Skipping custom content path: ${customPath} - module.yaml missing 'code' field`); - continue; - } - - customPaths.push(expandedPath); - selectedModuleIds.push(moduleMeta.code); - sources.push({ - path: expandedPath, - id: moduleMeta.code, - name: moduleMeta.name || moduleMeta.code, - }); - } - - if (customPaths.length > 0) { - customModuleResult = { - selectedCustomModules: selectedModuleIds, - customContentConfig: { - hasCustomContent: true, - selected: true, - sources, - selectedFiles: customPaths.map((p) => path.join(p, 'module.yaml')), - selectedModuleIds: selectedModuleIds, - }, - }; - } - } else if (options.yes) { - // Non-interactive mode: preserve existing custom modules (matches default: false) - const cacheDir = path.join(bmadDir, '_config', 'custom'); - if (await fs.pathExists(cacheDir)) { - const entries = await fs.readdir(cacheDir, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isDirectory()) { - customModuleResult.selectedCustomModules.push(entry.name); - } - } - await prompts.log.info( - `Non-interactive mode (--yes): preserving ${customModuleResult.selectedCustomModules.length} existing custom module(s)`, - ); - } else { - await prompts.log.info('Non-interactive mode (--yes): no existing custom modules found'); - } - } else { - const changeCustomModules = await prompts.confirm({ - message: 'Modify custom modules, agents, or workflows?', - default: false, - }); - - if (changeCustomModules) { - customModuleResult = await this.handleCustomModulesInModifyFlow(confirmedDirectory, selectedModules); - } else { - // Preserve existing custom modules if user doesn't want to modify them - const { Installer } = require('../installers/lib/core/installer'); - const installer = new Installer(); - const { bmadDir } = await installer.findBmadDir(confirmedDirectory); - - const cacheDir = path.join(bmadDir, '_config', 'custom'); - if (await fs.pathExists(cacheDir)) { - const entries = await fs.readdir(cacheDir, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isDirectory()) { - customModuleResult.selectedCustomModules.push(entry.name); - } - } - } - } - } - - // Merge any selected custom modules - if (customModuleResult.selectedCustomModules.length > 0) { - selectedModules.push(...customModuleResult.selectedCustomModules); - } - - // Filter out core - it's always installed via installCore flag - selectedModules = selectedModules.filter((m) => m !== 'core'); - - // Get tool selection - const toolSelection = await this.promptToolSelection(confirmedDirectory, options); - - const coreConfig = await this.collectCoreConfig(confirmedDirectory, options); - - return { - actionType: 'update', - directory: confirmedDirectory, - installCore: true, - modules: selectedModules, - ides: toolSelection.ides, - skipIde: toolSelection.skipIde, - coreConfig: coreConfig, - customContent: customModuleResult.customContentConfig, - skipPrompts: options.yes || false, - }; - } - } - - // This section is only for new installations (update returns early above) - const { installedModuleIds } = await this.getExistingInstallation(confirmedDirectory); - - // Unified module selection - all modules in one grouped multiselect - let selectedModules; - if (options.modules) { - // Use modules from command-line - selectedModules = options.modules - .split(',') - .map((m) => m.trim()) - .filter(Boolean); - await prompts.log.info(`Using modules from command-line: ${selectedModules.join(', ')}`); - } else if (options.yes) { - // Use default modules when --yes flag is set - selectedModules = await this.getDefaultModules(installedModuleIds); - await prompts.log.info(`Using default modules (--yes flag): ${selectedModules.join(', ')}`); - } else { - selectedModules = await this.selectAllModules(installedModuleIds); - } - - // Ask about custom content (local modules/agents/workflows) - if (options.customContent) { - // Use custom content from command-line - const paths = options.customContent - .split(',') - .map((p) => p.trim()) - .filter(Boolean); - await prompts.log.info(`Using custom content from command-line: ${paths.join(', ')}`); - - // Build custom content config similar to promptCustomContentSource - const customPaths = []; - const selectedModuleIds = []; - const sources = []; - - for (const customPath of paths) { - const expandedPath = this.expandUserPath(customPath); - const validation = this.validateCustomContentPathSync(expandedPath); - if (validation) { - await prompts.log.warn(`Skipping invalid custom content path: ${customPath} - ${validation}`); - continue; - } - - // Read module metadata - let moduleMeta; - try { - const moduleYamlPath = path.join(expandedPath, 'module.yaml'); - const moduleYaml = await fs.readFile(moduleYamlPath, 'utf-8'); - const yaml = require('yaml'); - moduleMeta = yaml.parse(moduleYaml); - } catch (error) { - await prompts.log.warn(`Skipping custom content path: ${customPath} - failed to read module.yaml: ${error.message}`); - continue; - } - - if (!moduleMeta) { - await prompts.log.warn(`Skipping custom content path: ${customPath} - module.yaml is empty`); - continue; - } - - if (!moduleMeta.code) { - await prompts.log.warn(`Skipping custom content path: ${customPath} - module.yaml missing 'code' field`); - continue; - } - - customPaths.push(expandedPath); - selectedModuleIds.push(moduleMeta.code); - sources.push({ - path: expandedPath, - id: moduleMeta.code, - name: moduleMeta.name || moduleMeta.code, - }); - } - - if (customPaths.length > 0) { - customContentConfig = { - hasCustomContent: true, - selected: true, - sources, - selectedFiles: customPaths.map((p) => path.join(p, 'module.yaml')), - selectedModuleIds: selectedModuleIds, - }; - } - } else if (!options.yes) { - const wantsCustomContent = await prompts.confirm({ - message: 'Add custom modules, agents, or workflows from your computer?', - default: false, - }); - - if (wantsCustomContent) { - customContentConfig = await this.promptCustomContentSource(); - } - } - - // Add custom content modules if any were selected - if (customContentConfig && customContentConfig.selectedModuleIds) { - selectedModules.push(...customContentConfig.selectedModuleIds); - } - - selectedModules = selectedModules.filter((m) => m !== 'core'); - let toolSelection = await this.promptToolSelection(confirmedDirectory, options); - const coreConfig = await this.collectCoreConfig(confirmedDirectory, options); - - return { - actionType: 'install', - directory: confirmedDirectory, - installCore: true, - modules: selectedModules, - ides: toolSelection.ides, - skipIde: toolSelection.skipIde, - coreConfig: coreConfig, - customContent: customContentConfig, - skipPrompts: options.yes || false, - }; - } - - /** - * Prompt for tool/IDE selection (called after module configuration) - * Uses a split prompt approach: - * 1. Recommended tools - standard multiselect for preferred tools - * 2. Additional tools - autocompleteMultiselect with search capability - * @param {string} projectDir - Project directory to check for existing IDEs - * @param {Object} options - Command-line options - * @returns {Object} Tool configuration - */ - async promptToolSelection(projectDir, options = {}) { - // Check for existing configured IDEs - use findBmadDir to detect custom folder names - const { Detector } = require('../installers/lib/core/detector'); - const { Installer } = require('../installers/lib/core/installer'); - const detector = new Detector(); - const installer = new Installer(); - const bmadResult = await installer.findBmadDir(projectDir || process.cwd()); - const bmadDir = bmadResult.bmadDir; - const existingInstall = await detector.detect(bmadDir); - const configuredIdes = existingInstall.ides || []; - - // Get IDE manager to fetch available IDEs dynamically - const { IdeManager } = require('../installers/lib/ide/manager'); - const ideManager = new IdeManager(); - await ideManager.ensureInitialized(); // IMPORTANT: Must initialize before getting IDEs - - const preferredIdes = ideManager.getPreferredIdes(); - const otherIdes = ideManager.getOtherIdes(); - - // Determine which configured IDEs are in "preferred" vs "other" categories - const configuredPreferred = configuredIdes.filter((id) => preferredIdes.some((ide) => ide.value === id)); - const configuredOther = configuredIdes.filter((id) => otherIdes.some((ide) => ide.value === id)); - - // Warn about previously configured tools that are no longer available - const allKnownValues = new Set([...preferredIdes, ...otherIdes].map((ide) => ide.value)); - const unknownTools = configuredIdes.filter((id) => id && typeof id === 'string' && !allKnownValues.has(id)); - if (unknownTools.length > 0) { - await prompts.log.warn(`Previously configured tools are no longer available: ${unknownTools.join(', ')}`); - } - - // ───────────────────────────────────────────────────────────────────────────── - // UPGRADE PATH: If tools already configured, show all tools with configured at top - // ───────────────────────────────────────────────────────────────────────────── - if (configuredIdes.length > 0) { - const allTools = [...preferredIdes, ...otherIdes]; - - // Non-interactive: handle --tools and --yes flags before interactive prompt - if (options.tools) { - if (options.tools.toLowerCase() === 'none') { - await prompts.log.info('Skipping tool configuration (--tools none)'); - return { ides: [], skipIde: true }; - } - const selectedIdes = options.tools - .split(',') - .map((t) => t.trim()) - .filter(Boolean); - await prompts.log.info(`Using tools from command-line: ${selectedIdes.join(', ')}`); - await this.displaySelectedTools(selectedIdes, preferredIdes, allTools); - return { ides: selectedIdes, skipIde: false }; - } - - if (options.yes) { - await prompts.log.info(`Non-interactive mode (--yes): keeping configured tools: ${configuredIdes.join(', ')}`); - await this.displaySelectedTools(configuredIdes, preferredIdes, allTools); - return { ides: configuredIdes, skipIde: false }; - } - - // Sort: configured tools first, then preferred, then others - const sortedTools = [ - ...allTools.filter((ide) => configuredIdes.includes(ide.value)), - ...allTools.filter((ide) => !configuredIdes.includes(ide.value)), - ]; - - const upgradeOptions = sortedTools.map((ide) => { - const isConfigured = configuredIdes.includes(ide.value); - const isPreferred = preferredIdes.some((p) => p.value === ide.value); - let label = ide.name; - if (isPreferred) label += ' ⭐'; - if (isConfigured) label += ' ✅'; - return { label, value: ide.value }; - }); - - // Sort initialValues to match display order - const sortedInitialValues = sortedTools.filter((ide) => configuredIdes.includes(ide.value)).map((ide) => ide.value); - - const upgradeSelected = await prompts.autocompleteMultiselect({ - message: 'Integrate with', - options: upgradeOptions, - initialValues: sortedInitialValues, - required: false, - maxItems: 8, - }); - - const selectedIdes = upgradeSelected || []; - - if (selectedIdes.length === 0) { - const confirmNoTools = await prompts.confirm({ - message: 'No tools selected. Continue without installing any tools?', - default: false, - }); - - if (!confirmNoTools) { - return this.promptToolSelection(projectDir, options); - } - - return { ides: [], skipIde: true }; - } - - // Display selected tools - await this.displaySelectedTools(selectedIdes, preferredIdes, allTools); - - return { ides: selectedIdes, skipIde: false }; - } - - // ───────────────────────────────────────────────────────────────────────────── - // NEW INSTALL: Show all tools with search - // ───────────────────────────────────────────────────────────────────────────── - const allTools = [...preferredIdes, ...otherIdes]; - - const allToolOptions = allTools.map((ide) => { - const isPreferred = preferredIdes.some((p) => p.value === ide.value); - let label = ide.name; - if (isPreferred) label += ' ⭐'; - return { - label, - value: ide.value, - }; - }); - - let selectedIdes = []; - - // Check if tools are provided via command-line - if (options.tools) { - // Check for explicit "none" value to skip tool installation - if (options.tools.toLowerCase() === 'none') { - await prompts.log.info('Skipping tool configuration (--tools none)'); - return { ides: [], skipIde: true }; - } else { - selectedIdes = options.tools - .split(',') - .map((t) => t.trim()) - .filter(Boolean); - await prompts.log.info(`Using tools from command-line: ${selectedIdes.join(', ')}`); - await this.displaySelectedTools(selectedIdes, preferredIdes, allTools); - return { ides: selectedIdes, skipIde: false }; - } - } else if (options.yes) { - // If --yes flag is set, skip tool prompt and use previously configured tools or empty - if (configuredIdes.length > 0) { - await prompts.log.info(`Using previously configured tools (--yes flag): ${configuredIdes.join(', ')}`); - await this.displaySelectedTools(configuredIdes, preferredIdes, allTools); - return { ides: configuredIdes, skipIde: false }; - } else { - await prompts.log.info('Skipping tool configuration (--yes flag, no previous tools)'); - return { ides: [], skipIde: true }; - } - } - - // Interactive mode - const interactiveSelectedIdes = await prompts.autocompleteMultiselect({ - message: 'Integrate with:', - options: allToolOptions, - initialValues: configuredIdes.length > 0 ? configuredIdes : undefined, - required: false, - maxItems: 8, - }); - - selectedIdes = interactiveSelectedIdes || []; - - // ───────────────────────────────────────────────────────────────────────────── - // STEP 3: Confirm if no tools selected - // ───────────────────────────────────────────────────────────────────────────── - if (selectedIdes.length === 0) { - const confirmNoTools = await prompts.confirm({ - message: 'No tools selected. Continue without installing any tools?', - default: false, - }); - - if (!confirmNoTools) { - // User wants to select tools - recurse - return this.promptToolSelection(projectDir, options); - } - - return { - ides: [], - skipIde: true, - }; - } - - // Display selected tools - await this.displaySelectedTools(selectedIdes, preferredIdes, allTools); - - return { - ides: selectedIdes, - skipIde: selectedIdes.length === 0, - }; - } - - /** - * Prompt for update configuration - * @returns {Object} Update configuration - */ - async promptUpdate() { - const backupFirst = await prompts.confirm({ - message: 'Create backup before updating?', - default: true, - }); - - const preserveCustomizations = await prompts.confirm({ - message: 'Preserve local customizations?', - default: true, - }); - - return { backupFirst, preserveCustomizations }; - } - - /** - * Confirm action - * @param {string} message - Confirmation message - * @param {boolean} defaultValue - Default value - * @returns {boolean} User confirmation - */ - async confirm(message, defaultValue = false) { - return await prompts.confirm({ - message, - default: defaultValue, - }); - } - - /** - * Get confirmed directory from user - * @returns {string} Confirmed directory path - */ - async getConfirmedDirectory() { - let confirmedDirectory = null; - while (!confirmedDirectory) { - const directoryAnswer = await this.promptForDirectory(); - await this.displayDirectoryInfo(directoryAnswer.directory); - - if (await this.confirmDirectory(directoryAnswer.directory)) { - confirmedDirectory = directoryAnswer.directory; - } - } - return confirmedDirectory; - } - - /** - * Get existing installation info and installed modules - * @param {string} directory - Installation directory - * @returns {Object} Object with existingInstall, installedModuleIds, and bmadDir - */ - async getExistingInstallation(directory) { - const { Detector } = require('../installers/lib/core/detector'); - const { Installer } = require('../installers/lib/core/installer'); - const detector = new Detector(); - const installer = new Installer(); - const bmadDirResult = await installer.findBmadDir(directory); - const bmadDir = bmadDirResult.bmadDir; - const existingInstall = await detector.detect(bmadDir); - const installedModuleIds = new Set(existingInstall.modules.map((mod) => mod.id)); - - return { existingInstall, installedModuleIds, bmadDir }; - } - - /** - * Collect core configuration - * @param {string} directory - Installation directory - * @param {Object} options - Command-line options - * @returns {Object} Core configuration - */ - async collectCoreConfig(directory, options = {}) { - const { ConfigCollector } = require('../installers/lib/core/config-collector'); - const configCollector = new ConfigCollector(); - - // If options are provided, set them directly - if (options.userName || options.communicationLanguage || options.documentOutputLanguage || options.outputFolder) { - const coreConfig = {}; - if (options.userName) { - coreConfig.user_name = options.userName; - await prompts.log.info(`Using user name from command-line: ${options.userName}`); - } - if (options.communicationLanguage) { - coreConfig.communication_language = options.communicationLanguage; - await prompts.log.info(`Using communication language from command-line: ${options.communicationLanguage}`); - } - if (options.documentOutputLanguage) { - coreConfig.document_output_language = options.documentOutputLanguage; - await prompts.log.info(`Using document output language from command-line: ${options.documentOutputLanguage}`); - } - if (options.outputFolder) { - coreConfig.output_folder = options.outputFolder; - await prompts.log.info(`Using output folder from command-line: ${options.outputFolder}`); - } - - // Load existing config to merge with provided options - await configCollector.loadExistingConfig(directory); - - // Merge provided options with existing config (or defaults) - const existingConfig = configCollector.collectedConfig.core || {}; - configCollector.collectedConfig.core = { ...existingConfig, ...coreConfig }; - - // If not all options are provided, collect the missing ones interactively (unless --yes flag) - if ( - !options.yes && - (!options.userName || !options.communicationLanguage || !options.documentOutputLanguage || !options.outputFolder) - ) { - await configCollector.collectModuleConfig('core', directory, false, true); - } - } else if (options.yes) { - // Use all defaults when --yes flag is set - await configCollector.loadExistingConfig(directory); - const existingConfig = configCollector.collectedConfig.core || {}; - - // If no existing config, use defaults - if (Object.keys(existingConfig).length === 0) { - let safeUsername; - try { - safeUsername = os.userInfo().username; - } catch { - safeUsername = process.env.USER || process.env.USERNAME || 'User'; - } - const defaultUsername = safeUsername.charAt(0).toUpperCase() + safeUsername.slice(1); - configCollector.collectedConfig.core = { - user_name: defaultUsername, - communication_language: 'English', - document_output_language: 'English', - output_folder: '_bmad-output', - }; - await prompts.log.info('Using default configuration (--yes flag)'); - } - } else { - // Load existing configs first if they exist - await configCollector.loadExistingConfig(directory); - // Now collect with existing values as defaults (false = don't skip loading, true = skip completion message) - await configCollector.collectModuleConfig('core', directory, false, true); - } - - const coreConfig = configCollector.collectedConfig.core; - // Ensure we always have a core config object, even if empty - return coreConfig || {}; - } - - /** - * Get module choices for selection - * @param {Set} installedModuleIds - Currently installed module IDs - * @param {Object} customContentConfig - Custom content configuration - * @returns {Array} Module choices for prompt - */ - async getModuleChoices(installedModuleIds, customContentConfig = null) { - const color = await prompts.getColor(); - const moduleChoices = []; - const isNewInstallation = installedModuleIds.size === 0; - - const customContentItems = []; - - // Add custom content items - if (customContentConfig && customContentConfig.hasCustomContent && customContentConfig.customPath) { - // Existing installation - show from directory - const customHandler = new CustomHandler(); - const customFiles = await customHandler.findCustomContent(customContentConfig.customPath); - - for (const customFile of customFiles) { - const customInfo = await customHandler.getCustomInfo(customFile); - if (customInfo) { - customContentItems.push({ - name: `${color.cyan('\u2713')} ${customInfo.name} ${color.dim(`(${customInfo.relativePath})`)}`, - value: `__CUSTOM_CONTENT__${customFile}`, // Unique value for each custom content - checked: true, // Default to selected since user chose to provide custom content - path: customInfo.path, // Track path to avoid duplicates - hint: customInfo.description || undefined, - }); - } - } - } - - // Add official modules - const { ModuleManager } = require('../installers/lib/modules/manager'); - const moduleManager = new ModuleManager(); - const { modules: availableModules, customModules: customModulesFromCache } = await moduleManager.listAvailable(); - - // First, add all items to appropriate sections - const allCustomModules = []; - - // Add custom content items from directory - allCustomModules.push(...customContentItems); - - // Add custom modules from cache - for (const mod of customModulesFromCache) { - // Skip if this module is already in customContentItems (by path) - const isDuplicate = allCustomModules.some((item) => item.path && mod.path && path.resolve(item.path) === path.resolve(mod.path)); - - if (!isDuplicate) { - allCustomModules.push({ - name: `${color.cyan('\u2713')} ${mod.name} ${color.dim('(cached)')}`, - value: mod.id, - checked: isNewInstallation ? mod.defaultSelected || false : installedModuleIds.has(mod.id), - hint: mod.description || undefined, - }); - } - } - - // Add separators and modules in correct order - if (allCustomModules.length > 0) { - // Add separator for custom content, all custom modules, and official content separator - moduleChoices.push( - new choiceUtils.Separator('── Custom Content ──'), - ...allCustomModules, - new choiceUtils.Separator('── Official Content ──'), - ); - } - - // Add official modules (only non-custom ones) - for (const mod of availableModules) { - if (!mod.isCustom) { - moduleChoices.push({ - name: mod.name, - value: mod.id, - checked: isNewInstallation ? mod.defaultSelected || false : installedModuleIds.has(mod.id), - hint: mod.description || undefined, - }); - } - } - - return moduleChoices; - } - - /** - * Select all modules (official + community) using grouped multiselect. - * Core is shown as locked but filtered from the result since it's always installed separately. - * @param {Set} installedModuleIds - Currently installed module IDs - * @returns {Array} Selected module codes (excluding core) - */ - async selectAllModules(installedModuleIds = new Set()) { - const { ModuleManager } = require('../installers/lib/modules/manager'); - const moduleManager = new ModuleManager(); - const { modules: localModules } = await moduleManager.listAvailable(); - - // Get external modules - const externalManager = new ExternalModuleManager(); - const externalModules = await externalManager.listAvailable(); - - // Build flat options list with group hints for autocompleteMultiselect - const allOptions = []; - const initialValues = []; - const lockedValues = ['core']; - - // Core module is always installed — show it locked at the top - allOptions.push({ label: 'BMad Core Module', value: 'core', hint: 'Core configuration and shared resources' }); - initialValues.push('core'); - - // Helper to build module entry with proper sorting and selection - const buildModuleEntry = (mod, value, group) => { - const isInstalled = installedModuleIds.has(value); - return { - label: mod.name, - value, - hint: mod.description || group, - // Pre-select only if already installed (not on fresh install) - selected: isInstalled, - }; - }; - - // Local modules (BMM, BMB, etc.) - const localEntries = []; - for (const mod of localModules) { - if (!mod.isCustom && mod.id !== 'core') { - const entry = buildModuleEntry(mod, mod.id, 'Local'); - localEntries.push(entry); - if (entry.selected) { - initialValues.push(mod.id); - } - } - } - allOptions.push(...localEntries.map(({ label, value, hint }) => ({ label, value, hint }))); - - // Group 2: BMad Official Modules (type: bmad-org) - const officialModules = []; - for (const mod of externalModules) { - if (mod.type === 'bmad-org') { - const entry = buildModuleEntry(mod, mod.code, 'Official'); - officialModules.push(entry); - if (entry.selected) { - initialValues.push(mod.code); - } - } - } - allOptions.push(...officialModules.map(({ label, value, hint }) => ({ label, value, hint }))); - - // Group 3: Community Modules (type: community) - const communityModules = []; - for (const mod of externalModules) { - if (mod.type === 'community') { - const entry = buildModuleEntry(mod, mod.code, 'Community'); - communityModules.push(entry); - if (entry.selected) { - initialValues.push(mod.code); - } - } - } - allOptions.push(...communityModules.map(({ label, value, hint }) => ({ label, value, hint }))); - - const selected = await prompts.autocompleteMultiselect({ - message: 'Select modules to install:', - options: allOptions, - initialValues: initialValues.length > 0 ? initialValues : undefined, - lockedValues, - required: true, - maxItems: allOptions.length, - }); - - const result = selected ? selected.filter((m) => m !== 'core') : []; - - // Display selected modules as bulleted list - if (result.length > 0) { - const moduleLines = result.map((moduleId) => { - const opt = allOptions.find((o) => o.value === moduleId); - return ` \u2022 ${opt?.label || moduleId}`; - }); - await prompts.log.message('Selected modules:\n' + moduleLines.join('\n')); - } - - return result; - } - - /** - * Get default modules for non-interactive mode - * @param {Set} installedModuleIds - Already installed module IDs - * @returns {Array} Default module codes - */ - async getDefaultModules(installedModuleIds = new Set()) { - const { ModuleManager } = require('../installers/lib/modules/manager'); - const moduleManager = new ModuleManager(); - const { modules: localModules } = await moduleManager.listAvailable(); - - const defaultModules = []; - - // Add default-selected local modules (typically BMM) - for (const mod of localModules) { - if (mod.defaultSelected === true || installedModuleIds.has(mod.id)) { - defaultModules.push(mod.id); - } - } - - // If no defaults found, use 'bmm' as the fallback default - if (defaultModules.length === 0) { - defaultModules.push('bmm'); - } - - return defaultModules; - } - - /** - * Prompt for directory selection - * @returns {Object} Directory answer from prompt - */ - async promptForDirectory() { - // Use sync validation because @clack/prompts doesn't support async validate - const directory = await prompts.text({ - message: 'Installation directory:', - default: process.cwd(), - placeholder: process.cwd(), - validate: (input) => this.validateDirectorySync(input), - }); - - // Apply filter logic - let filteredDir = directory; - if (!filteredDir || filteredDir.trim() === '') { - filteredDir = process.cwd(); - } else { - filteredDir = this.expandUserPath(filteredDir); - } - - return { directory: filteredDir }; - } - - /** - * Display directory information - * @param {string} directory - The directory path - */ - async displayDirectoryInfo(directory) { - await prompts.log.info(`Resolved installation path: ${directory}`); - - const dirExists = await fs.pathExists(directory); - if (dirExists) { - // Show helpful context about the existing path - const stats = await fs.stat(directory); - if (stats.isDirectory()) { - const files = await fs.readdir(directory); - if (files.length > 0) { - // Check for any bmad installation (any folder with _config/manifest.yaml) - const { Installer } = require('../installers/lib/core/installer'); - const installer = new Installer(); - const bmadResult = await installer.findBmadDir(directory); - const hasBmadInstall = - (await fs.pathExists(bmadResult.bmadDir)) && (await fs.pathExists(path.join(bmadResult.bmadDir, '_config', 'manifest.yaml'))); - - const bmadNote = hasBmadInstall ? ` including existing BMAD installation (${path.basename(bmadResult.bmadDir)})` : ''; - await prompts.log.message(`Directory exists and contains ${files.length} item(s)${bmadNote}`); - } else { - await prompts.log.message('Directory exists and is empty'); - } - } - } - } - - /** - * Confirm directory selection - * @param {string} directory - The directory path - * @returns {boolean} Whether user confirmed - */ - async confirmDirectory(directory) { - const dirExists = await fs.pathExists(directory); - - if (dirExists) { - const proceed = await prompts.confirm({ - message: 'Install to this directory?', - default: true, - }); - - if (!proceed) { - await prompts.log.warn("Let's try again with a different path."); - } - - return proceed; - } else { - // Ask for confirmation to create the directory - const create = await prompts.confirm({ - message: `Create directory: ${directory}?`, - default: false, - }); - - if (!create) { - await prompts.log.warn("Let's try again with a different path."); - } - - return create; - } - } - - /** - * Validate directory path for installation (sync version for clack prompts) - * @param {string} input - User input path - * @returns {string|undefined} Error message or undefined if valid - */ - validateDirectorySync(input) { - // Allow empty input to use the default - if (!input || input.trim() === '') { - return; // Empty means use default, undefined = valid for clack - } - - let expandedPath; - try { - expandedPath = this.expandUserPath(input.trim()); - } catch (error) { - return error.message; - } - - // Check if the path exists - const pathExists = fs.pathExistsSync(expandedPath); - - if (!pathExists) { - // Find the first existing parent directory - const existingParent = this.findExistingParentSync(expandedPath); - - if (!existingParent) { - return 'Cannot create directory: no existing parent directory found'; - } - - // Check if the existing parent is writable - try { - fs.accessSync(existingParent, fs.constants.W_OK); - // Path doesn't exist but can be created - will prompt for confirmation later - return; - } catch { - // Provide a detailed error message explaining both issues - return `Directory '${expandedPath}' does not exist and cannot be created: parent directory '${existingParent}' is not writable`; - } - } - - // If it exists, validate it's a directory and writable - const stat = fs.statSync(expandedPath); - if (!stat.isDirectory()) { - return `Path exists but is not a directory: ${expandedPath}`; - } - - // Check write permissions - try { - fs.accessSync(expandedPath, fs.constants.W_OK); - } catch { - return `Directory is not writable: ${expandedPath}`; - } - - return; - } - - /** - * Validate directory path for installation (async version) - * @param {string} input - User input path - * @returns {string|true} Error message or true if valid - */ - async validateDirectory(input) { - // Allow empty input to use the default - if (!input || input.trim() === '') { - return true; // Empty means use default - } - - let expandedPath; - try { - expandedPath = this.expandUserPath(input.trim()); - } catch (error) { - return error.message; - } - - // Check if the path exists - const pathExists = await fs.pathExists(expandedPath); - - if (!pathExists) { - // Find the first existing parent directory - const existingParent = await this.findExistingParent(expandedPath); - - if (!existingParent) { - return 'Cannot create directory: no existing parent directory found'; - } - - // Check if the existing parent is writable - try { - await fs.access(existingParent, fs.constants.W_OK); - // Path doesn't exist but can be created - will prompt for confirmation later - return true; - } catch { - // Provide a detailed error message explaining both issues - return `Directory '${expandedPath}' does not exist and cannot be created: parent directory '${existingParent}' is not writable`; - } - } - - // If it exists, validate it's a directory and writable - const stat = await fs.stat(expandedPath); - if (!stat.isDirectory()) { - return `Path exists but is not a directory: ${expandedPath}`; - } - - // Check write permissions - try { - await fs.access(expandedPath, fs.constants.W_OK); - } catch { - return `Directory is not writable: ${expandedPath}`; - } - - return true; - } - - /** - * Find the first existing parent directory (sync version) - * @param {string} targetPath - The path to check - * @returns {string|null} The first existing parent directory, or null if none found - */ - findExistingParentSync(targetPath) { - let currentPath = path.resolve(targetPath); - - // Walk up the directory tree until we find an existing directory - while (currentPath !== path.dirname(currentPath)) { - // Stop at root - const parent = path.dirname(currentPath); - if (fs.pathExistsSync(parent)) { - return parent; - } - currentPath = parent; - } - - return null; // No existing parent found (shouldn't happen in practice) - } - - /** - * Find the first existing parent directory (async version) - * @param {string} targetPath - The path to check - * @returns {string|null} The first existing parent directory, or null if none found - */ - async findExistingParent(targetPath) { - let currentPath = path.resolve(targetPath); - - // Walk up the directory tree until we find an existing directory - while (currentPath !== path.dirname(currentPath)) { - // Stop at root - const parent = path.dirname(currentPath); - if (await fs.pathExists(parent)) { - return parent; - } - currentPath = parent; - } - - return null; // No existing parent found (shouldn't happen in practice) - } - - /** - * Expands the user-provided path: handles ~ and resolves to absolute. - * @param {string} inputPath - User input path. - * @returns {string} Absolute expanded path. - */ - expandUserPath(inputPath) { - if (typeof inputPath !== 'string') { - throw new TypeError('Path must be a string.'); - } - - let expanded = inputPath.trim(); - - // Handle tilde expansion - if (expanded.startsWith('~')) { - if (expanded === '~') { - expanded = os.homedir(); - } else if (expanded.startsWith('~' + path.sep)) { - const pathAfterHome = expanded.slice(2); // Remove ~/ or ~\ - expanded = path.join(os.homedir(), pathAfterHome); - } else { - const restOfPath = expanded.slice(1); - const separatorIndex = restOfPath.indexOf(path.sep); - const username = separatorIndex === -1 ? restOfPath : restOfPath.slice(0, separatorIndex); - if (username) { - throw new Error(`Path expansion for ~${username} is not supported. Please use an absolute path or ~${path.sep}`); - } - } - } - - // Resolve to the absolute path relative to the current working directory - return path.resolve(expanded); - } - - /** - * Load existing configurations to use as defaults - * @param {string} directory - Installation directory - * @returns {Object} Existing configurations - */ - async loadExistingConfigurations(directory) { - const configs = { - hasCustomContent: false, - coreConfig: {}, - ideConfig: { ides: [], skipIde: false }, - }; - - try { - // Load core config - configs.coreConfig = await this.collectCoreConfig(directory); - - // Load IDE configuration - const configuredIdes = await this.getConfiguredIdes(directory); - if (configuredIdes.length > 0) { - configs.ideConfig.ides = configuredIdes; - configs.ideConfig.skipIde = false; - } - - return configs; - } catch { - // If loading fails, return empty configs - await prompts.log.warn('Could not load existing configurations'); - return configs; - } - } - - /** - * Get configured IDEs from existing installation - * @param {string} directory - Installation directory - * @returns {Array} List of configured IDEs - */ - async getConfiguredIdes(directory) { - const { Detector } = require('../installers/lib/core/detector'); - const { Installer } = require('../installers/lib/core/installer'); - const detector = new Detector(); - const installer = new Installer(); - const bmadResult = await installer.findBmadDir(directory); - const existingInstall = await detector.detect(bmadResult.bmadDir); - return existingInstall.ides || []; - } - - /** - * Validate custom content path synchronously - * @param {string} input - User input path - * @returns {string|undefined} Error message or undefined if valid - */ - validateCustomContentPathSync(input) { - // Allow empty input to cancel - if (!input || input.trim() === '') { - return; // Allow empty to exit - } - - try { - // Expand the path - const expandedPath = this.expandUserPath(input.trim()); - - // Check if path exists - if (!fs.pathExistsSync(expandedPath)) { - return 'Path does not exist'; - } - - // Check if it's a directory - const stat = fs.statSync(expandedPath); - if (!stat.isDirectory()) { - return 'Path must be a directory'; - } - - // Check for module.yaml in the root - const moduleYamlPath = path.join(expandedPath, 'module.yaml'); - if (!fs.pathExistsSync(moduleYamlPath)) { - return 'Directory must contain a module.yaml file in the root'; - } - - // Try to parse the module.yaml to get the module ID - try { - const yaml = require('yaml'); - const content = fs.readFileSync(moduleYamlPath, 'utf8'); - const moduleData = yaml.parse(content); - if (!moduleData.code) { - return 'module.yaml must contain a "code" field for the module ID'; - } - } catch (error) { - return 'Invalid module.yaml file: ' + error.message; - } - - return; // Valid - } catch (error) { - return 'Error validating path: ' + error.message; - } - } - - /** - * Prompt user for custom content source location - * @returns {Object} Custom content configuration - */ - async promptCustomContentSource() { - const customContentConfig = { hasCustomContent: true, sources: [] }; - - // Keep asking for more sources until user is done - while (true) { - // First ask if user wants to add another module or continue - if (customContentConfig.sources.length > 0) { - const action = await prompts.select({ - message: 'Would you like to:', - choices: [ - { name: 'Add another custom module', value: 'add' }, - { name: 'Continue with installation', value: 'continue' }, - ], - default: 'continue', - }); - - if (action === 'continue') { - break; - } - } - - let sourcePath; - let isValid = false; - - while (!isValid) { - // Use sync validation because @clack/prompts doesn't support async validate - const inputPath = await prompts.text({ - message: 'Path to custom module folder (press Enter to skip):', - validate: (input) => this.validateCustomContentPathSync(input), - }); - - // If user pressed Enter without typing anything, exit the loop - if (!inputPath || inputPath.trim() === '') { - // If we have no modules yet, return false for no custom content - if (customContentConfig.sources.length === 0) { - return { hasCustomContent: false }; - } - return customContentConfig; - } - - sourcePath = this.expandUserPath(inputPath); - isValid = true; - } - - // Read module.yaml to get module info - const yaml = require('yaml'); - const moduleYamlPath = path.join(sourcePath, 'module.yaml'); - const moduleContent = await fs.readFile(moduleYamlPath, 'utf8'); - const moduleData = yaml.parse(moduleContent); - - // Add to sources - customContentConfig.sources.push({ - path: sourcePath, - id: moduleData.code, - name: moduleData.name || moduleData.code, - }); - - await prompts.log.success(`Confirmed local custom module: ${moduleData.name || moduleData.code}`); - } - - // Ask if user wants to add these to the installation - const shouldInstall = await prompts.confirm({ - message: `Install these ${customContentConfig.sources.length} custom modules?`, - default: true, - }); - - if (shouldInstall) { - customContentConfig.selected = true; - // Store paths to module.yaml files, not directories - customContentConfig.selectedFiles = customContentConfig.sources.map((s) => path.join(s.path, 'module.yaml')); - // Also include module IDs for installation - customContentConfig.selectedModuleIds = customContentConfig.sources.map((s) => s.id); - } - - return customContentConfig; - } - - /** - * Handle custom modules in the modify flow - * @param {string} directory - Installation directory - * @param {Array} selectedModules - Currently selected modules - * @returns {Object} Result with selected custom modules and custom content config - */ - async handleCustomModulesInModifyFlow(directory, selectedModules) { - // Get existing installation to find custom modules - const { existingInstall } = await this.getExistingInstallation(directory); - - // Check if there are any custom modules in cache - const { Installer } = require('../installers/lib/core/installer'); - const installer = new Installer(); - const { bmadDir } = await installer.findBmadDir(directory); - - const cacheDir = path.join(bmadDir, '_config', 'custom'); - const cachedCustomModules = []; - - if (await fs.pathExists(cacheDir)) { - const entries = await fs.readdir(cacheDir, { withFileTypes: true }); - for (const entry of entries) { - if (entry.isDirectory()) { - const moduleYamlPath = path.join(cacheDir, entry.name, 'module.yaml'); - if (await fs.pathExists(moduleYamlPath)) { - const yaml = require('yaml'); - const content = await fs.readFile(moduleYamlPath, 'utf8'); - const moduleData = yaml.parse(content); - - cachedCustomModules.push({ - id: entry.name, - name: moduleData.name || entry.name, - description: moduleData.description || 'Custom module from cache', - checked: selectedModules.includes(entry.name), - fromCache: true, - }); - } - } - } - } - - const result = { - selectedCustomModules: [], - customContentConfig: { hasCustomContent: false }, - }; - - // Ask user about custom modules - await prompts.log.info('Custom Modules'); - if (cachedCustomModules.length > 0) { - await prompts.log.message('Found custom modules in your installation:'); - } else { - await prompts.log.message('No custom modules currently installed.'); - } - - // Build choices dynamically based on whether we have existing modules - const choices = []; - if (cachedCustomModules.length > 0) { - choices.push( - { name: 'Keep all existing custom modules', value: 'keep' }, - { name: 'Select which custom modules to keep', value: 'select' }, - { name: 'Add new custom modules', value: 'add' }, - { name: 'Remove all custom modules', value: 'remove' }, - ); - } else { - choices.push({ name: 'Add new custom modules', value: 'add' }, { name: 'Cancel (no custom modules)', value: 'cancel' }); - } - - const customAction = await prompts.select({ - message: cachedCustomModules.length > 0 ? 'Manage custom modules?' : 'Add custom modules?', - choices: choices, - default: cachedCustomModules.length > 0 ? 'keep' : 'add', - }); - - switch (customAction) { - case 'keep': { - // Keep all existing custom modules - result.selectedCustomModules = cachedCustomModules.map((m) => m.id); - await prompts.log.message(`Keeping ${result.selectedCustomModules.length} custom module(s)`); - break; - } - - case 'select': { - // Let user choose which to keep - const selectChoices = cachedCustomModules.map((m) => ({ - name: `${m.name} (${m.id})`, - value: m.id, - checked: m.checked, - })); - - // Add "None / I changed my mind" option at the end - const choicesWithSkip = [ - ...selectChoices, - { - name: '⚠ None / I changed my mind - keep no custom modules', - value: '__NONE__', - checked: false, - }, - ]; - - const keepModules = await prompts.multiselect({ - message: 'Select custom modules to keep (use arrow keys, space to toggle):', - choices: choicesWithSkip, - required: true, - }); - - // If user selected both "__NONE__" and other modules, honor the "None" choice - if (keepModules && keepModules.includes('__NONE__') && keepModules.length > 1) { - await prompts.log.warn('"None / I changed my mind" was selected, so no custom modules will be kept.'); - result.selectedCustomModules = []; - } else { - // Filter out the special '__NONE__' value - result.selectedCustomModules = keepModules ? keepModules.filter((m) => m !== '__NONE__') : []; - } - break; - } - - case 'add': { - // By default, keep existing modules when adding new ones - // User chose "Add new" not "Replace", so we assume they want to keep existing - result.selectedCustomModules = cachedCustomModules.map((m) => m.id); - - // Then prompt for new ones (reuse existing method) - const newCustomContent = await this.promptCustomContentSource(); - if (newCustomContent.hasCustomContent && newCustomContent.selected) { - result.selectedCustomModules.push(...newCustomContent.selectedModuleIds); - result.customContentConfig = newCustomContent; - } - break; - } - - case 'remove': { - // Remove all custom modules - await prompts.log.warn('All custom modules will be removed from the installation'); - break; - } - - case 'cancel': { - // User cancelled - no custom modules - await prompts.log.message('No custom modules will be added'); - break; - } - } - - return result; - } - - /** - * Check if installed version is a legacy version that needs fresh install - * @param {string} installedVersion - The installed version - * @returns {boolean} True if legacy (v4 or any alpha) - */ - isLegacyVersion(installedVersion) { - if (!installedVersion || installedVersion === 'unknown') { - return true; // Treat unknown as legacy for safety - } - // Check if version string contains -alpha or -Alpha (any v6 alpha) - return /-alpha\./i.test(installedVersion); - } - - /** - * Show warning for legacy version (v4 or alpha) and ask if user wants to proceed - * @param {string} installedVersion - The installed version - * @param {string} currentVersion - The current version - * @param {string} bmadFolderName - Name of the BMAD folder - * @returns {Promise<boolean>} True if user wants to proceed, false if they cancel - */ - async showLegacyVersionWarning(installedVersion, currentVersion, bmadFolderName, options = {}) { - if (!this.isLegacyVersion(installedVersion)) { - return true; // Not legacy, proceed - } - - let warningContent; - if (installedVersion === 'unknown') { - warningContent = 'Unable to detect your installed BMAD version.\n' + 'This appears to be a legacy or unsupported installation.'; - } else { - warningContent = - `You are updating from ${installedVersion} to ${currentVersion}.\n` + 'You have a legacy version installed (v4 or alpha).'; - } - - warningContent += - '\n\nFor the best experience, we recommend:\n' + - ' 1. Delete your current BMAD installation folder\n' + - ` (the "${bmadFolderName}/" folder in your project)\n` + - ' 2. Run a fresh installation\n\n' + - 'Benefits of a fresh install:\n' + - ' \u2022 Cleaner configuration without legacy artifacts\n' + - ' \u2022 All new features properly configured\n' + - ' \u2022 Fewer potential conflicts'; - - await prompts.log.warn('VERSION WARNING'); - await prompts.note(warningContent, 'Version Warning'); - - if (options.yes) { - await prompts.log.warn('Non-interactive mode (--yes): auto-proceeding with legacy update'); - return true; - } - - const proceed = await prompts.select({ - message: 'How would you like to proceed?', - choices: [ - { - name: 'Proceed with update anyway (may have issues)', - value: 'proceed', - }, - { - name: 'Cancel (recommended - do a fresh install instead)', - value: 'cancel', - }, - ], - default: 'cancel', - }); - - if (proceed === 'cancel') { - await prompts.note( - `1. Delete the "${bmadFolderName}/" folder in your project\n` + "2. Run 'bmad install' again", - 'To do a fresh install', - ); - } - - return proceed === 'proceed'; - } - - /** - * Display module versions with update availability - * @param {Array} modules - Array of module info objects with version info - * @param {Array} availableUpdates - Array of available updates - */ - async displayModuleVersions(modules, availableUpdates = []) { - // Group modules by source - const builtIn = modules.filter((m) => m.source === 'built-in'); - const external = modules.filter((m) => m.source === 'external'); - const custom = modules.filter((m) => m.source === 'custom'); - const unknown = modules.filter((m) => m.source === 'unknown'); - - const lines = []; - const formatGroup = (group, title) => { - if (group.length === 0) return; - lines.push(title); - for (const mod of group) { - const updateInfo = availableUpdates.find((u) => u.name === mod.name); - const versionDisplay = mod.version || 'unknown'; - if (updateInfo) { - lines.push(` ${mod.name.padEnd(20)} ${versionDisplay} \u2192 ${updateInfo.latestVersion} \u2191`); - } else { - lines.push(` ${mod.name.padEnd(20)} ${versionDisplay} \u2713`); - } - } - }; - - formatGroup(builtIn, 'Built-in Modules'); - formatGroup(external, 'External Modules (Official)'); - formatGroup(custom, 'Custom Modules'); - formatGroup(unknown, 'Other Modules'); - - await prompts.note(lines.join('\n'), 'Module Versions'); - } - - /** - * Prompt user to select which modules to update - * @param {Array} availableUpdates - Array of available updates - * @returns {Array} Selected module names to update - */ - async promptUpdateSelection(availableUpdates) { - if (availableUpdates.length === 0) { - return []; - } - - await prompts.log.info('Available Updates'); - - const choices = availableUpdates.map((update) => ({ - name: `${update.name} (v${update.installedVersion} \u2192 v${update.latestVersion})`, - value: update.name, - checked: true, // Default to selecting all updates - })); - - // Add "Update All" and "Cancel" options - const action = await prompts.select({ - message: 'How would you like to proceed?', - choices: [ - { name: 'Update all available modules', value: 'all' }, - { name: 'Select specific modules to update', value: 'select' }, - { name: 'Skip updates for now', value: 'skip' }, - ], - default: 'all', - }); - - if (action === 'all') { - return availableUpdates.map((u) => u.name); - } - - if (action === 'skip') { - return []; - } - - // Allow specific selection - const selected = await prompts.multiselect({ - message: 'Select modules to update (use arrow keys, space to toggle):', - choices: choices, - required: true, - }); - - return selected || []; - } - - /** - * Display status of all installed modules - * @param {Object} statusData - Status data with modules, installation info, and available updates - */ - async displayStatus(statusData) { - const { installation, modules, availableUpdates, bmadDir } = statusData; - - // Installation info - const infoLines = [ - `Version: ${installation.version || 'unknown'}`, - `Location: ${bmadDir}`, - `Installed: ${new Date(installation.installDate).toLocaleDateString()}`, - `Last Updated: ${installation.lastUpdated ? new Date(installation.lastUpdated).toLocaleDateString() : 'unknown'}`, - ]; - - await prompts.note(infoLines.join('\n'), 'BMAD Status'); - - // Module versions - await this.displayModuleVersions(modules, availableUpdates); - - // Update summary - if (availableUpdates.length > 0) { - await prompts.log.warn(`${availableUpdates.length} update(s) available`); - await prompts.log.message('Run \'bmad install\' and select "Quick Update" to update'); - } else { - await prompts.log.success('All modules are up to date'); - } - } - - /** - * Display list of selected tools after IDE selection - * @param {Array} selectedIdes - Array of selected IDE values - * @param {Array} preferredIdes - Array of preferred IDE objects - * @param {Array} allTools - Array of all tool objects - */ - async displaySelectedTools(selectedIdes, preferredIdes, allTools) { - if (selectedIdes.length === 0) return; - - const preferredValues = new Set(preferredIdes.map((ide) => ide.value)); - const toolLines = selectedIdes.map((ideValue) => { - const tool = allTools.find((t) => t.value === ideValue); - const name = tool?.name || ideValue; - const marker = preferredValues.has(ideValue) ? ' \u2B50' : ''; - return ` \u2022 ${name}${marker}`; - }); - await prompts.log.message('Selected tools:\n' + toolLines.join('\n')); - } -} - -module.exports = { UI }; diff --git a/tools/cli/lib/xml-handler.js b/tools/cli/lib/xml-handler.js deleted file mode 100644 index a6111b1a7..000000000 --- a/tools/cli/lib/xml-handler.js +++ /dev/null @@ -1,177 +0,0 @@ -const xml2js = require('xml2js'); -const fs = require('fs-extra'); -const path = require('node:path'); -const { getProjectRoot, getSourcePath } = require('./project-root'); -const { YamlXmlBuilder } = require('./yaml-xml-builder'); - -/** - * XML utility functions for BMAD installer - * Now supports both legacy XML agents and new YAML-based agents - */ -class XmlHandler { - constructor() { - this.parser = new xml2js.Parser({ - preserveChildrenOrder: true, - explicitChildren: true, - explicitArray: false, - trim: false, - normalizeTags: false, - attrkey: '$', - charkey: '_', - }); - - this.builder = new xml2js.Builder({ - renderOpts: { - pretty: true, - indent: ' ', - newline: '\n', - }, - xmldec: { - version: '1.0', - encoding: 'utf8', - standalone: false, - }, - headless: true, // Don't add XML declaration - attrkey: '$', - charkey: '_', - }); - - this.yamlBuilder = new YamlXmlBuilder(); - } - - /** - * Load and parse the activation template - * @returns {Object} Parsed activation block - */ - async loadActivationTemplate() { - console.error('Failed to load activation template:', error); - } - - /** - * Inject activation block into agent XML content - * @param {string} agentContent - The agent file content - * @param {Object} metadata - Metadata containing module and name - * @returns {string} Modified content with activation block - */ - async injectActivation(agentContent, metadata = {}) { - try { - // Check if already has activation - if (agentContent.includes('<activation')) { - return agentContent; - } - - // Extract the XML portion from markdown if needed - let xmlContent = agentContent; - let beforeXml = ''; - let afterXml = ''; - - const xmlBlockMatch = agentContent.match(/([\s\S]*?)```xml\n([\s\S]*?)\n```([\s\S]*)/); - if (xmlBlockMatch) { - beforeXml = xmlBlockMatch[1] + '```xml\n'; - xmlContent = xmlBlockMatch[2]; - afterXml = '\n```' + xmlBlockMatch[3]; - } - - // Parse the agent XML - const parsed = await this.parser.parseStringPromise(xmlContent); - - // Get the activation template - const activationBlock = await this.loadActivationTemplate(); - if (!activationBlock) { - console.warn('Could not load activation template'); - return agentContent; - } - - // Find the agent node - if ( - parsed.agent && // Insert activation as the first child - !parsed.agent.activation - ) { - // Ensure proper structure - if (!parsed.agent.$$) { - parsed.agent.$$ = []; - } - - // Create the activation node with proper structure - const activationNode = { - '#name': 'activation', - $: { critical: '1' }, - $$: activationBlock.$$, - }; - - // Insert at the beginning - parsed.agent.$$.unshift(activationNode); - } - - // Convert back to XML - let modifiedXml = this.builder.buildObject(parsed); - - // Fix indentation - xml2js doesn't maintain our exact formatting - // Add 2-space base indentation to match our style - const lines = modifiedXml.split('\n'); - const indentedLines = lines.map((line) => { - if (line.trim() === '') return line; - if (line.startsWith('<agent')) return line; // Keep agent at column 0 - return ' ' + line; // Indent everything else - }); - modifiedXml = indentedLines.join('\n'); - - // Reconstruct the full content - return beforeXml + modifiedXml + afterXml; - } catch (error) { - console.error('Error injecting activation:', error); - return agentContent; - } - } - - /** - * TODO: DELETE THIS METHOD - */ - injectActivationSimple(agentContent, metadata = {}) { - console.error('Error in simple injection:', error); - } - - /** - * Build agent from YAML source - * @param {string} yamlPath - Path to .agent.yaml file - * @param {string} customizePath - Path to .customize.yaml file (optional) - * @param {Object} metadata - Build metadata - * @returns {string} Generated XML content - */ - async buildFromYaml(yamlPath, customizePath = null, metadata = {}) { - try { - // Use YamlXmlBuilder to convert YAML to XML - const mergedAgent = await this.yamlBuilder.loadAndMergeAgent(yamlPath, customizePath); - - // Build metadata - const buildMetadata = { - sourceFile: path.basename(yamlPath), - sourceHash: await this.yamlBuilder.calculateFileHash(yamlPath), - customizeFile: customizePath ? path.basename(customizePath) : null, - customizeHash: customizePath ? await this.yamlBuilder.calculateFileHash(customizePath) : null, - builderVersion: '1.0.0', - includeMetadata: metadata.includeMetadata !== false, - forWebBundle: metadata.forWebBundle || false, // Pass through forWebBundle flag - }; - - // Convert to XML - const xml = await this.yamlBuilder.convertToXml(mergedAgent, buildMetadata); - - return xml; - } catch (error) { - console.error('Error building agent from YAML:', error); - throw error; - } - } - - /** - * Check if a path is a YAML agent file - * @param {string} filePath - Path to check - * @returns {boolean} True if it's a YAML agent file - */ - isYamlAgent(filePath) { - return filePath.endsWith('.agent.yaml'); - } -} - -module.exports = { XmlHandler }; diff --git a/tools/cli/lib/xml-to-markdown.js b/tools/cli/lib/xml-to-markdown.js deleted file mode 100644 index d5787b11f..000000000 --- a/tools/cli/lib/xml-to-markdown.js +++ /dev/null @@ -1,82 +0,0 @@ -const fs = require('node:fs'); -const path = require('node:path'); - -function convertXmlToMarkdown(xmlFilePath) { - if (!xmlFilePath.endsWith('.xml')) { - throw new Error('Input file must be an XML file'); - } - - const xmlContent = fs.readFileSync(xmlFilePath, 'utf8'); - - const basename = path.basename(xmlFilePath, '.xml'); - const dirname = path.dirname(xmlFilePath); - const mdFilePath = path.join(dirname, `${basename}.md`); - - // Extract version and name/title from root element attributes - let title = basename; - let version = ''; - - // Match the root element and its attributes - const rootMatch = xmlContent.match( - /<[^>\s]+[^>]*?\sv="([^"]+)"[^>]*?(?:\sname="([^"]+)")?|<[^>\s]+[^>]*?(?:\sname="([^"]+)")?[^>]*?\sv="([^"]+)"/, - ); - - if (rootMatch) { - // Handle both v="x" name="y" and name="y" v="x" orders - version = rootMatch[1] || rootMatch[4] || ''; - const nameAttr = rootMatch[2] || rootMatch[3] || ''; - - if (nameAttr) { - title = nameAttr; - } else { - // Try to find name in a <name> element if not in attributes - const nameElementMatch = xmlContent.match(/<name>([^<]+)<\/name>/); - if (nameElementMatch) { - title = nameElementMatch[1]; - } - } - } - - const heading = version ? `# ${title} v${version}` : `# ${title}`; - - const markdownContent = `${heading} - -\`\`\`xml -${xmlContent} -\`\`\` -`; - - fs.writeFileSync(mdFilePath, markdownContent, 'utf8'); - - return mdFilePath; -} - -function main() { - const args = process.argv.slice(2); - - if (args.length === 0) { - console.error('Usage: node xml-to-markdown.js <xml-file-path>'); - process.exit(1); - } - - const xmlFilePath = path.resolve(args[0]); - - if (!fs.existsSync(xmlFilePath)) { - console.error(`Error: File not found: ${xmlFilePath}`); - process.exit(1); - } - - try { - const mdFilePath = convertXmlToMarkdown(xmlFilePath); - console.log(`Successfully converted: ${xmlFilePath} -> ${mdFilePath}`); - } catch (error) { - console.error(`Error converting file: ${error.message}`); - process.exit(1); - } -} - -if (require.main === module) { - main(); -} - -module.exports = { convertXmlToMarkdown }; diff --git a/tools/cli/lib/yaml-format.js b/tools/cli/lib/yaml-format.js deleted file mode 100755 index 3c38b921e..000000000 --- a/tools/cli/lib/yaml-format.js +++ /dev/null @@ -1,245 +0,0 @@ -const fs = require('node:fs'); -const path = require('node:path'); -const yaml = require('yaml'); -const { execSync } = require('node:child_process'); - -// Dynamic import for ES module -let chalk; - -// Initialize ES modules -async function initializeModules() { - if (!chalk) { - chalk = (await import('chalk')).default; - } -} - -/** - * YAML Formatter and Linter for BMad-Method - * Formats and validates YAML files and YAML embedded in Markdown - */ - -async function formatYamlContent(content, filename) { - await initializeModules(); - try { - // First try to fix common YAML issues - let fixedContent = content - // Fix "commands :" -> "commands:" - .replaceAll(/^(\s*)(\w+)\s+:/gm, '$1$2:') - // Fix inconsistent list indentation - .replaceAll(/^(\s*)-\s{3,}/gm, '$1- '); - - // Skip auto-fixing for .roomodes files - they have special nested structure - if (!filename.includes('.roomodes')) { - fixedContent = fixedContent - // Fix unquoted list items that contain special characters or multiple parts - .replaceAll(/^(\s*)-\s+(.*)$/gm, (match, indent, content) => { - // Skip if already quoted - if (content.startsWith('"') && content.endsWith('"')) { - return match; - } - // If the content contains special YAML characters or looks complex, quote it - // BUT skip if it looks like a proper YAML key-value pair (like "key: value") - if ( - (content.includes(':') || content.includes('-') || content.includes('{') || content.includes('}')) && - !/^\w+:\s/.test(content) - ) { - // Remove any existing quotes first, escape internal quotes, then add proper quotes - const cleanContent = content.replaceAll(/^["']|["']$/g, '').replaceAll('"', String.raw`\"`); - return `${indent}- "${cleanContent}"`; - } - return match; - }); - } - - // Debug: show what we're trying to parse - if (fixedContent !== content) { - console.log(chalk.blue(`🔧 Applied YAML fixes to ${filename}`)); - } - - // Parse and re-dump YAML to format it - const parsed = yaml.parse(fixedContent); - const formatted = yaml.stringify(parsed, { - indent: 2, - lineWidth: 0, // Disable line wrapping - sortKeys: false, // Preserve key order - }); - // Ensure POSIX-compliant final newline - return formatted.endsWith('\n') ? formatted : formatted + '\n'; - } catch (error) { - console.error(chalk.red(`❌ YAML syntax error in ${filename}:`), error.message); - console.error(chalk.yellow(`💡 Try manually fixing the YAML structure first`)); - return null; - } -} - -async function processMarkdownFile(filePath) { - await initializeModules(); - const content = fs.readFileSync(filePath, 'utf8'); - let modified = false; - let newContent = content; - - // Fix untyped code blocks by adding 'text' type - // Match ``` at start of line followed by newline, but only if it's an opening fence - newContent = newContent.replaceAll(/^```\n([\s\S]*?)\n```$/gm, '```text\n$1\n```'); - if (newContent !== content) { - modified = true; - console.log(chalk.blue(`🔧 Added 'text' type to untyped code blocks in ${filePath}`)); - } - - // Find YAML code blocks - const yamlBlockRegex = /```ya?ml\n([\s\S]*?)\n```/g; - let match; - const replacements = []; - - while ((match = yamlBlockRegex.exec(newContent)) !== null) { - const [fullMatch, yamlContent] = match; - const formatted = await formatYamlContent(yamlContent, filePath); - if (formatted !== null) { - const trimmedFormatted = formatted.replace(/\n$/, ''); - - if (trimmedFormatted !== yamlContent) { - modified = true; - console.log(chalk.green(`✓ Formatted YAML in ${filePath}`)); - } - - replacements.push({ - start: match.index, - end: match.index + fullMatch.length, - replacement: `\`\`\`yaml\n${trimmedFormatted}\n\`\`\``, - }); - } - } - - // Apply replacements in reverse order to maintain indices - for (let index = replacements.length - 1; index >= 0; index--) { - const { start, end, replacement } = replacements[index]; - newContent = newContent.slice(0, start) + replacement + newContent.slice(end); - } - - if (modified) { - fs.writeFileSync(filePath, newContent); - return true; - } - return false; -} - -async function processYamlFile(filePath) { - await initializeModules(); - const content = fs.readFileSync(filePath, 'utf8'); - const formatted = await formatYamlContent(content, filePath); - - if (formatted === null) { - return false; // Syntax error - } - - if (formatted !== content) { - fs.writeFileSync(filePath, formatted); - return true; - } - return false; -} - -async function lintYamlFile(filePath) { - await initializeModules(); - try { - // Use yaml-lint for additional validation - execSync(`npx yaml-lint "${filePath}"`, { stdio: 'pipe' }); - return true; - } catch (error) { - console.error(chalk.red(`❌ YAML lint error in ${filePath}:`)); - console.error(error.stdout?.toString() || error.message); - return false; - } -} - -async function main() { - await initializeModules(); - const arguments_ = process.argv.slice(2); - const glob = require('glob'); - - if (arguments_.length === 0) { - console.error('Usage: node yaml-format.js <file1> [file2] ...'); - process.exit(1); - } - - let hasErrors = false; - let hasChanges = false; - let filesProcessed = []; - - // Expand glob patterns and collect all files - const allFiles = []; - for (const argument of arguments_) { - if (argument.includes('*')) { - // It's a glob pattern - const matches = glob.sync(argument); - allFiles.push(...matches); - } else { - // It's a direct file path - allFiles.push(argument); - } - } - - for (const filePath of allFiles) { - if (!fs.existsSync(filePath)) { - // Skip silently for glob patterns that don't match anything - if (!arguments_.some((argument) => argument.includes('*') && filePath === argument)) { - console.error(chalk.red(`❌ File not found: ${filePath}`)); - hasErrors = true; - } - continue; - } - - const extension = path.extname(filePath).toLowerCase(); - const basename = path.basename(filePath).toLowerCase(); - - try { - let changed = false; - if (extension === '.md') { - changed = await processMarkdownFile(filePath); - } else if ( - extension === '.yaml' || - extension === '.yml' || - basename.includes('roomodes') || - basename.includes('.yaml') || - basename.includes('.yml') - ) { - // Handle YAML files and special cases like .roomodes - changed = await processYamlFile(filePath); - - // Also run linting - const lintPassed = await lintYamlFile(filePath); - if (!lintPassed) hasErrors = true; - } else { - // Skip silently for unsupported files - continue; - } - - if (changed) { - hasChanges = true; - filesProcessed.push(filePath); - } - } catch (error) { - console.error(chalk.red(`❌ Error processing ${filePath}:`), error.message); - hasErrors = true; - } - } - - if (hasChanges) { - console.log(chalk.green(`\n✨ YAML formatting completed! Modified ${filesProcessed.length} files:`)); - for (const file of filesProcessed) console.log(chalk.blue(` 📝 ${file}`)); - } - - if (hasErrors) { - console.error(chalk.red('\n💥 Some files had errors. Please fix them before committing.')); - process.exit(1); - } -} - -if (require.main === module) { - main().catch((error) => { - console.error('Error:', error); - process.exit(1); - }); -} - -module.exports = { formatYamlContent, processMarkdownFile, processYamlFile }; diff --git a/tools/cli/lib/yaml-xml-builder.js b/tools/cli/lib/yaml-xml-builder.js deleted file mode 100644 index ac140814f..000000000 --- a/tools/cli/lib/yaml-xml-builder.js +++ /dev/null @@ -1,587 +0,0 @@ -const yaml = require('yaml'); -const fs = require('fs-extra'); -const path = require('node:path'); -const crypto = require('node:crypto'); -const { AgentAnalyzer } = require('./agent-analyzer'); -const { ActivationBuilder } = require('./activation-builder'); -const { escapeXml } = require('../../lib/xml-utils'); - -/** - * Converts agent YAML files to XML format with smart activation injection - */ -class YamlXmlBuilder { - constructor() { - this.analyzer = new AgentAnalyzer(); - this.activationBuilder = new ActivationBuilder(); - } - - /** - * Deep merge two objects (for customize.yaml + agent.yaml) - * @param {Object} target - Target object - * @param {Object} source - Source object to merge in - * @returns {Object} Merged object - */ - deepMerge(target, source) { - const output = { ...target }; - - if (this.isObject(target) && this.isObject(source)) { - for (const key of Object.keys(source)) { - if (this.isObject(source[key])) { - if (key in target) { - output[key] = this.deepMerge(target[key], source[key]); - } else { - output[key] = source[key]; - } - } else if (Array.isArray(source[key])) { - // For arrays, append rather than replace (for commands) - if (Array.isArray(target[key])) { - output[key] = [...target[key], ...source[key]]; - } else { - output[key] = source[key]; - } - } else { - output[key] = source[key]; - } - } - } - - return output; - } - - /** - * Check if value is an object - */ - isObject(item) { - return item && typeof item === 'object' && !Array.isArray(item); - } - - /** - * Load and merge agent YAML with customization - * @param {string} agentYamlPath - Path to base agent YAML - * @param {string} customizeYamlPath - Path to customize YAML (optional) - * @returns {Object} Merged agent configuration - */ - async loadAndMergeAgent(agentYamlPath, customizeYamlPath = null) { - // Load base agent - const agentContent = await fs.readFile(agentYamlPath, 'utf8'); - const agentYaml = yaml.parse(agentContent); - - // Load customization if exists - let merged = agentYaml; - if (customizeYamlPath && (await fs.pathExists(customizeYamlPath))) { - const customizeContent = await fs.readFile(customizeYamlPath, 'utf8'); - const customizeYaml = yaml.parse(customizeContent); - - if (customizeYaml) { - // Special handling: persona fields are merged, but only non-empty values override - if (customizeYaml.persona) { - const basePersona = merged.agent.persona || {}; - const customPersona = {}; - - // Only copy non-empty customize values - for (const [key, value] of Object.entries(customizeYaml.persona)) { - if (value !== '' && value !== null && !(Array.isArray(value) && value.length === 0)) { - customPersona[key] = value; - } - } - - // Merge non-empty customize values over base - if (Object.keys(customPersona).length > 0) { - merged.agent.persona = { ...basePersona, ...customPersona }; - } - } - - // Merge metadata (only non-empty values) - if (customizeYaml.agent && customizeYaml.agent.metadata) { - const nonEmptyMetadata = {}; - for (const [key, value] of Object.entries(customizeYaml.agent.metadata)) { - if (value !== '' && value !== null) { - nonEmptyMetadata[key] = value; - } - } - merged.agent.metadata = { ...merged.agent.metadata, ...nonEmptyMetadata }; - } - - // Append menu items (support both 'menu' and legacy 'commands') - const customMenuItems = customizeYaml.menu || customizeYaml.commands; - if (customMenuItems) { - // Determine if base uses 'menu' or 'commands' - if (merged.agent.menu) { - merged.agent.menu = [...merged.agent.menu, ...customMenuItems]; - } else if (merged.agent.commands) { - merged.agent.commands = [...merged.agent.commands, ...customMenuItems]; - } else { - // Default to 'menu' for new agents - merged.agent.menu = customMenuItems; - } - } - - // Append critical actions - if (customizeYaml.critical_actions) { - merged.agent.critical_actions = [...(merged.agent.critical_actions || []), ...customizeYaml.critical_actions]; - } - - // Append prompts - if (customizeYaml.prompts) { - merged.agent.prompts = [...(merged.agent.prompts || []), ...customizeYaml.prompts]; - } - - // Append memories - if (customizeYaml.memories) { - merged.agent.memories = [...(merged.agent.memories || []), ...customizeYaml.memories]; - } - } - } - - return merged; - } - - /** - * Convert agent YAML to XML - * @param {Object} agentYaml - Parsed agent YAML object - * @param {Object} buildMetadata - Metadata about the build (file paths, hashes, etc.) - * @returns {string} XML content - */ - async convertToXml(agentYaml, buildMetadata = {}) { - const agent = agentYaml.agent; - const metadata = agent.metadata || {}; - - // Add module from buildMetadata if available - if (buildMetadata.module) { - metadata.module = buildMetadata.module; - } - - // Analyze agent to determine needed handlers - const profile = this.analyzer.analyzeAgentObject(agentYaml); - - // Build activation block only if not skipped - let activationBlock = ''; - if (!buildMetadata.skipActivation) { - activationBlock = await this.activationBuilder.buildActivation( - profile, - metadata, - agent.critical_actions || [], - buildMetadata.forWebBundle || false, // Pass web bundle flag - ); - } - - // Start building XML - let xml = ''; - - if (buildMetadata.forWebBundle) { - // Web bundle: keep existing format - xml += '<!-- Powered by BMAD-CORE™ -->\n\n'; - xml += `# ${metadata.title || 'Agent'}\n\n`; - } else { - // Installation: use YAML frontmatter + instruction - // Extract name from filename: "cli-chief.yaml" or "pm.agent.yaml" -> "cli chief" or "pm" - const filename = buildMetadata.sourceFile || 'agent.yaml'; - let nameFromFile = path.basename(filename, path.extname(filename)); // Remove .yaml/.md extension - nameFromFile = nameFromFile.replace(/\.agent$/, ''); // Remove .agent suffix if present - nameFromFile = nameFromFile.replaceAll('-', ' '); // Replace dashes with spaces - - xml += '---\n'; - xml += `name: "${nameFromFile}"\n`; - xml += `description: "${metadata.title || 'BMAD Agent'}"\n`; - xml += '---\n\n'; - xml += - "You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.\n\n"; - } - - xml += '```xml\n'; - - // Agent opening tag - const agentAttrs = [ - `id="${metadata.id || ''}"`, - `name="${metadata.name || ''}"`, - `title="${metadata.title || ''}"`, - `icon="${metadata.icon || '🤖'}"`, - ]; - - // Add localskip attribute if present - if (metadata.localskip === true) { - agentAttrs.push('localskip="true"'); - } - - xml += `<agent ${agentAttrs.join(' ')}>\n`; - - // Activation block (only if not skipped) - if (activationBlock) { - xml += activationBlock + '\n'; - } - - // Persona section - xml += this.buildPersonaXml(agent.persona); - - // Memories section (if exists) - if (agent.memories) { - xml += this.buildMemoriesXml(agent.memories); - } - - // Prompts section (if exists) - if (agent.prompts) { - xml += this.buildPromptsXml(agent.prompts); - } - - // Menu section (support both 'menu' and legacy 'commands') - const menuItems = agent.menu || agent.commands || []; - xml += this.buildCommandsXml(menuItems, buildMetadata.forWebBundle); - - xml += '</agent>\n'; - xml += '```\n'; - - return xml; - } - - /** - * Build persona XML section - */ - buildPersonaXml(persona) { - if (!persona) return ''; - - let xml = ' <persona>\n'; - - if (persona.role) { - xml += ` <role>${escapeXml(persona.role)}</role>\n`; - } - - if (persona.identity) { - xml += ` <identity>${escapeXml(persona.identity)}</identity>\n`; - } - - if (persona.communication_style) { - xml += ` <communication_style>${escapeXml(persona.communication_style)}</communication_style>\n`; - } - - if (persona.principles) { - // Principles can be array or string - let principlesText; - if (Array.isArray(persona.principles)) { - principlesText = persona.principles.join(' '); - } else { - principlesText = persona.principles; - } - xml += ` <principles>${escapeXml(principlesText)}</principles>\n`; - } - - xml += ' </persona>\n'; - - return xml; - } - - /** - * Build memories XML section - */ - buildMemoriesXml(memories) { - if (!memories || memories.length === 0) return ''; - - let xml = ' <memories>\n'; - - for (const memory of memories) { - xml += ` <memory>${escapeXml(memory)}</memory>\n`; - } - - xml += ' </memories>\n'; - - return xml; - } - - /** - * Build prompts XML section - * Handles both array format and object/dictionary format - */ - buildPromptsXml(prompts) { - if (!prompts) return ''; - - // Handle object/dictionary format: { promptId: 'content', ... } - // Convert to array format for processing - let promptsArray = prompts; - if (!Array.isArray(prompts)) { - // Check if it's an object with no length property (dictionary format) - if (typeof prompts === 'object' && prompts.length === undefined) { - promptsArray = Object.entries(prompts).map(([id, content]) => ({ - id: id, - content: content, - })); - } else { - return ''; // Not a valid prompts format - } - } - - if (promptsArray.length === 0) return ''; - - let xml = ' <prompts>\n'; - - for (const prompt of promptsArray) { - xml += ` <prompt id="${prompt.id || ''}">\n`; - xml += ` <content>\n`; - xml += `${escapeXml(prompt.content || '')}\n`; - xml += ` </content>\n`; - xml += ` </prompt>\n`; - } - - xml += ' </prompts>\n'; - - return xml; - } - - /** - * Build menu XML section (renamed from commands for clarity) - * Auto-injects *help and *exit, adds * prefix to all triggers - * Supports both legacy format and new multi format with nested handlers - * @param {Array} menuItems - Menu items from YAML - * @param {boolean} forWebBundle - Whether building for web bundle - */ - buildCommandsXml(menuItems, forWebBundle = false) { - let xml = ' <menu>\n'; - - // Always inject menu display option first - xml += ` <item cmd="*menu">[M] Redisplay Menu Options</item>\n`; - - // Add user-defined menu items with * prefix - if (menuItems && menuItems.length > 0) { - for (const item of menuItems) { - // Skip ide-only items when building for web bundles - if (forWebBundle && item['ide-only'] === true) { - continue; - } - // Skip web-only items when NOT building for web bundles (i.e., IDE/local installation) - if (!forWebBundle && item['web-only'] === true) { - continue; - } - - // Handle multi format menu items with nested handlers - if (item.multi && item.triggers && Array.isArray(item.triggers)) { - xml += ` <item type="multi">${escapeXml(item.multi)}\n`; - xml += this.buildNestedHandlers(item.triggers); - xml += ` </item>\n`; - } - // Handle legacy format menu items - else if (item.trigger) { - // For legacy items, keep using cmd with *<trigger> format - let trigger = item.trigger || ''; - if (!trigger.startsWith('*')) { - trigger = '*' + trigger; - } - - const attrs = [`cmd="${trigger}"`]; - - // Add handler attributes - // If workflow-install exists, use its value for workflow attribute (vendoring) - // workflow-install is build-time metadata - tells installer where to copy workflows - // The final XML should only have workflow pointing to the install location - if (item['workflow-install']) { - attrs.push(`workflow="${item['workflow-install']}"`); - } else if (item.workflow) { - attrs.push(`workflow="${item.workflow}"`); - } - - if (item['validate-workflow']) attrs.push(`validate-workflow="${item['validate-workflow']}"`); - if (item.exec) attrs.push(`exec="${item.exec}"`); - if (item.tmpl) attrs.push(`tmpl="${item.tmpl}"`); - if (item.data) attrs.push(`data="${item.data}"`); - if (item.action) attrs.push(`action="${item.action}"`); - - xml += ` <item ${attrs.join(' ')}>${escapeXml(item.description || '')}</item>\n`; - } - } - } - - // Always inject dismiss last - xml += ` <item cmd="*dismiss">[D] Dismiss Agent</item>\n`; - - xml += ' </menu>\n'; - - return xml; - } - - /** - * Build nested handlers for multi format menu items - * @param {Array} triggers - Triggers array from multi format - * @returns {string} Handler XML - */ - buildNestedHandlers(triggers) { - let xml = ''; - - for (const triggerGroup of triggers) { - for (const [triggerName, execArray] of Object.entries(triggerGroup)) { - // Build trigger with * prefix - let trigger = triggerName.startsWith('*') ? triggerName : '*' + triggerName; - - // Extract the relevant execution data - const execData = this.processExecArray(execArray); - - // For nested handlers in multi items, we don't need cmd attribute - // The match attribute will handle fuzzy matching - const attrs = [`match="${escapeXml(execData.description || '')}"`]; - - // Add handler attributes based on exec data - if (execData.route) attrs.push(`exec="${execData.route}"`); - if (execData.workflow) attrs.push(`workflow="${execData.workflow}"`); - if (execData['validate-workflow']) attrs.push(`validate-workflow="${execData['validate-workflow']}"`); - if (execData.action) attrs.push(`action="${execData.action}"`); - if (execData.data) attrs.push(`data="${execData.data}"`); - if (execData.tmpl) attrs.push(`tmpl="${execData.tmpl}"`); - // Only add type if it's not 'exec' (exec is already implied by the exec attribute) - if (execData.type && execData.type !== 'exec') attrs.push(`type="${execData.type}"`); - - xml += ` <handler ${attrs.join(' ')}></handler>\n`; - } - } - - return xml; - } - - /** - * Process the execution array from multi format triggers - * Extracts relevant data for XML attributes - * @param {Array} execArray - Array of execution objects - * @returns {Object} Processed execution data - */ - processExecArray(execArray) { - const result = { - description: '', - route: null, - workflow: null, - data: null, - action: null, - type: null, - }; - - if (!Array.isArray(execArray)) { - return result; - } - - for (const exec of execArray) { - if (exec.input) { - // Use input as description if no explicit description is provided - result.description = exec.input; - } - - if (exec.route) { - // Determine if it's a workflow or exec based on file extension or context - if (exec.route.endsWith('.yaml') || exec.route.endsWith('.yml')) { - result.workflow = exec.route; - } else { - result.route = exec.route; - } - } - - if (exec.data !== null && exec.data !== undefined) { - result.data = exec.data; - } - - if (exec.action) { - result.action = exec.action; - } - - if (exec.type) { - result.type = exec.type; - } - } - - return result; - } - - /** - * Calculate file hash for build tracking - */ - async calculateFileHash(filePath) { - if (!(await fs.pathExists(filePath))) { - return null; - } - - const content = await fs.readFile(filePath, 'utf8'); - return crypto.createHash('md5').update(content).digest('hex').slice(0, 8); - } - - /** - * Build agent XML from YAML files and return as string (for in-memory use) - * @param {string} agentYamlPath - Path to agent YAML - * @param {string} customizeYamlPath - Path to customize YAML (optional) - * @param {Object} options - Build options - * @returns {Promise<string>} XML content as string - */ - async buildFromYaml(agentYamlPath, customizeYamlPath = null, options = {}) { - // Load and merge YAML files - const mergedAgent = await this.loadAndMergeAgent(agentYamlPath, customizeYamlPath); - - // Calculate hashes for build tracking - const sourceHash = await this.calculateFileHash(agentYamlPath); - const customizeHash = customizeYamlPath ? await this.calculateFileHash(customizeYamlPath) : null; - - // Extract module from path (e.g., /path/to/modules/bmm/agents/pm.yaml -> bmm) - // or /path/to/bmad/bmm/agents/pm.yaml -> bmm - // or /path/to/src/bmm/agents/pm.yaml -> bmm - let module = 'core'; // default to core - const pathParts = agentYamlPath.split(path.sep); - - // Look for module indicators in the path - const modulesIndex = pathParts.indexOf('modules'); - const bmadIndex = pathParts.indexOf('bmad'); - const srcIndex = pathParts.indexOf('src'); - - if (modulesIndex !== -1 && pathParts[modulesIndex + 1]) { - // Path contains /modules/{module}/ - module = pathParts[modulesIndex + 1]; - } else if (bmadIndex !== -1 && pathParts[bmadIndex + 1]) { - // Path contains /bmad/{module}/ - const potentialModule = pathParts[bmadIndex + 1]; - // Check if it's a known module, not 'agents' or '_config' - if (['bmm', 'bmb', 'cis', 'core'].includes(potentialModule)) { - module = potentialModule; - } - } else if (srcIndex !== -1 && pathParts[srcIndex + 1]) { - // Path contains /src/{module}/ (bmm and core are directly under src/) - const potentialModule = pathParts[srcIndex + 1]; - if (potentialModule === 'bmm' || potentialModule === 'core') { - module = potentialModule; - } - } - - // Build metadata - const buildMetadata = { - sourceFile: path.basename(agentYamlPath), - sourceHash, - customizeFile: customizeYamlPath ? path.basename(customizeYamlPath) : null, - customizeHash, - builderVersion: '1.0.0', - includeMetadata: options.includeMetadata !== false, - skipActivation: options.skipActivation === true, - forWebBundle: options.forWebBundle === true, - module: module, // Add module to buildMetadata - }; - - // Convert to XML and return - return await this.convertToXml(mergedAgent, buildMetadata); - } - - /** - * Build agent XML from YAML files - * @param {string} agentYamlPath - Path to agent YAML - * @param {string} customizeYamlPath - Path to customize YAML (optional) - * @param {string} outputPath - Path to write XML file - * @param {Object} options - Build options - */ - async buildAgent(agentYamlPath, customizeYamlPath, outputPath, options = {}) { - // Use buildFromYaml to get XML content - const xml = await this.buildFromYaml(agentYamlPath, customizeYamlPath, options); - - // Write output file - await fs.ensureDir(path.dirname(outputPath)); - await fs.writeFile(outputPath, xml, 'utf8'); - - // Calculate hashes for return value - const sourceHash = await this.calculateFileHash(agentYamlPath); - const customizeHash = customizeYamlPath ? await this.calculateFileHash(customizeYamlPath) : null; - - return { - success: true, - outputPath, - sourceHash, - customizeHash, - }; - } -} - -module.exports = { YamlXmlBuilder }; diff --git a/tools/docs/_prompt-external-modules-page.md b/tools/docs/_prompt-external-modules-page.md deleted file mode 100644 index f5e124373..000000000 --- a/tools/docs/_prompt-external-modules-page.md +++ /dev/null @@ -1,59 +0,0 @@ -# Prompt: Generate External Modules Reference Page - -## Goal - -Create a reference documentation page at `docs/reference/modules.md` that lists all official external BMad modules with descriptions and links. - -## Source of Truth - -Read `tools/cli/external-official-modules.yaml` — this is the authoritative registry of official external modules. Use the module names, codes, npm package names, and repository URLs from this file. - -## Research Step - -For each module in the registry, visit its GitHub repository (url in the YAML record) -and read its README to get: -- A 1-2 sentence description of what the module does -- The key agents and workflows it provides (if listed) -- Any notable features or use cases - -## Output Format - -Create `docs/reference/modules.md` following the project's Reference Catalog structure (see `docs/_STYLE_GUIDE.md`): - -``` -1. Title + Hook -2. Items (## for each module) - - Brief description (one sentence) - - **Key Info:** as flat list (code, npm package, GitHub link) -3. Installation note -``` - -## Style -use @docs/_STYLE_GUIDE.md - -## Frontmatter - -```yaml ---- -title: Official Modules ---- -``` - -## Content Requirements - -- Start with a brief intro explaining that BMad extends through official modules selected during installation -- For each module include: - - `##` header with module name - - 1-2 sentence description (sourced from GitHub README, not just the registry's short description) - - Key info list: module code, npm package (linked), GitHub repo (linked) - - Brief bullet list of what it provides (agents, workflows, key features) — keep to 3-5 bullets -- Include a `:::tip` admonition about how to install modules (via `npx bmad-method` installer) -- Mention that community modules and a marketplace are coming -- Do NOT include built-in modules (core, bmm) — this page is specifically for external/add-on modules - -## Existing Pages for Reference - -Look at these files to match the tone and style of existing reference docs: -- `docs/reference/agents.md` -- `docs/reference/commands.md` -- `docs/reference/testing.md` diff --git a/tools/docs/fix-refs.md b/tools/docs/fix-refs.md deleted file mode 100644 index df9835b43..000000000 --- a/tools/docs/fix-refs.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Fix Documentation References -description: Corrects workflow, agent, and command references in BMad documentation ---- - -# Fix Documentation References - -## Scope - -Fix reference patterns ONLY. Do not modify links, formatting, structure, or other content. - -## Purpose - -Fix incorrect references to workflows, agents, and commands in BMad documentation files. - -## Step 1: Establish Target Audience - -Before fixing references, determine who the document is for: - -| Audience | Indicators | Style | -|----------|------------|-------| -| **Newbies** | tutorials/, getting-started, installation/, "What You'll Learn" | Keep "workflow", include platform hints | -| **Experienced** | reference/, explanation/ | Drop "workflow", no platform hints | -| **How-To** | how-to/ | **Ask** — depends on the task | - -**How-To guides require judgment**: Don't assume experienced. Ask: "Does this task require prior BMad knowledge?" Early-journey tasks (first PRD, first sprint) are newbie docs. Customization and advanced features are experienced. - -**If unclear**: Ask the user "Who is the target audience for this document — new users learning BMad, or experienced users who know the system?" - -This determines whether helper words like "workflow" and platform hints are helpful context or just noise. - -## Reference Patterns to Fix - -### Always Wrong - -| Pattern | Example | Problem | -|---------|---------|---------| -| `*workflow` | `*prd` | Obsolete menu shortcut notation | -| `/workflow` | `/workflow-init` | Platform-specific slash command | -| `bmad_bmm_*` | `bmad_bmm_workflow-init` | Internal slash command name, platform-specific | - -### Correct Format - -Use backticks with plain workflow name: -- **Wrong**: Run `/workflow-init` -- **Wrong**: Run `*prd` - -**When to say "workflow"**: -- **Newbie docs** (getting-started): "Run the `prd` workflow" — helps them learn what it is -- **Other docs**: "Run `prd`" — they already know, so "workflow" is noise - -**Platform hint**: Only in newbie docs, and only on the **first** workflow mention: -- First mention: Run the `help` workflow (`/bmad-help` on most platforms) -- Subsequent mentions: Run `prd` — no hint, no "workflow" needed after they've seen the pattern - -In experienced docs, the hint is always noise — just use the workflow name. - -### Workflow Name Changes - -| Old Name | New Name | Notes | -|----------|----------|-------| -| `workflow-init` | `bmad-help` | DEPRECATED - help system replaces initialization | -| `workflow-status` | `bmad-help` | DEPRECATED - help system replaces status checking | - -### The Help System - -The `bmad-help` workflow is the modern replacement for both `workflow-init` and `workflow-status`: -- **Universal**: Works regardless of workflow state or module -- **Contextual**: Infers completion from artifacts and conversation -- **Adaptive**: Guides users through workflows based on phase ordering -- **Anytime**: Can be run at any point, no pre-initialization needed - -Users can run `bmad-help` to get guidance on what to do next. It detects: -- What workflows have been completed (by checking for output artifacts) -- What module is active -- What the next recommended/required step is - -## Lessons Learned - -1. **Platform-agnostic**: Docs should never include platform-specific invocation patterns (slashes, prefixes) -2. **Backtick the name**: Use backticks around workflow names: `workflow-name` -3. **Simple names**: Just the workflow name, no `bmad_bmm_` prefix, no `/` prefix - -## Self-Check - -Before finishing, verify you ONLY changed reference patterns: - -- [ ] Did I change any hyperlinks? **If yes, revert.** -- [ ] Did I change any formatting (horizontal rules, whitespace, structure)? **If yes, revert.** -- [ ] Did I remove or add any sections? **If yes, revert.** -- [ ] Did I modify anything not matching the patterns in "Reference Patterns to Fix"? **If yes, revert.** diff --git a/tools/fix-doc-links.js b/tools/fix-doc-links.js deleted file mode 100644 index e2ae6bdf7..000000000 --- a/tools/fix-doc-links.js +++ /dev/null @@ -1,285 +0,0 @@ -/** - * Fix Documentation Links - * - * Converts relative markdown links to repo-relative paths with .md extension. - * This ensures links work both in GitHub and on the Astro/Starlight site - * (the rehype plugin transforms /docs/path/file.md → /path/file/ at build time). - * - * - ./file.md → /docs/current/path/file.md - * - ../other/file.md → /docs/resolved/path/file.md - * - /path/file/ → /docs/path/file.md (or /docs/path/file/index.md if it's a directory) - * - * Usage: - * node tools/fix-doc-links.js # Dry run (shows what would change) - * node tools/fix-doc-links.js --write # Actually write changes - */ - -const fs = require('node:fs'); -const path = require('node:path'); - -const DOCS_ROOT = path.resolve(__dirname, '../docs'); -const DRY_RUN = !process.argv.includes('--write'); - -// Match all markdown links; filtering (external, anchors, assets) happens in convertToRepoRelative. -// This intentionally matches broadly so the handler can make context-aware decisions. -const ALL_MARKDOWN_LINKS_REGEX = /\[([^\]]*)\]\(([^)]+)\)/g; - -/** - * Get all markdown files in docs directory, excluding _* directories/files - */ -function getMarkdownFiles(dir) { - const files = []; - - function walk(currentDir) { - const entries = fs.readdirSync(currentDir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(currentDir, entry.name); - - // Skip underscore-prefixed entries - if (entry.name.startsWith('_')) { - continue; - } - - if (entry.isDirectory()) { - walk(fullPath); - } else if (entry.isFile() && entry.name.endsWith('.md')) { - files.push(fullPath); - } - } - } - - walk(dir); - return files; -} - -/** - * Convert a markdown link href to repo-relative path with .md extension - * - * @param {string} href - The original href (e.g., "./file.md", "/path/to/page/", "/path/to/page/#anchor") - * @param {string} currentFilePath - Absolute path to the file containing this link - * @returns {string|null} - Repo-relative path (e.g., "/docs/path/to/file.md"), or null if shouldn't be converted - */ -function convertToRepoRelative(href, currentFilePath) { - // Skip external links (including protocol-relative URLs like //cdn.example.com) - if (href.includes('://') || href.startsWith('//') || href.startsWith('mailto:') || href.startsWith('tel:')) { - return null; - } - - // Skip anchor-only links - if (href.startsWith('#')) { - return null; - } - - // Extract anchor and query string if present - let anchor = ''; - let query = ''; - let pathPortion = href; - - const hashIndex = href.indexOf('#'); - const queryIndex = href.indexOf('?'); - - if (hashIndex !== -1 || queryIndex !== -1) { - const firstDelimiter = Math.min(hashIndex === -1 ? Infinity : hashIndex, queryIndex === -1 ? Infinity : queryIndex); - pathPortion = href.slice(0, Math.max(0, firstDelimiter)); - - const suffix = href.slice(Math.max(0, firstDelimiter)); - const anchorInSuffix = suffix.indexOf('#'); - - if (suffix.startsWith('?')) { - if (anchorInSuffix === -1) { - query = suffix; - } else { - query = suffix.slice(0, Math.max(0, anchorInSuffix)); - anchor = suffix.slice(Math.max(0, anchorInSuffix)); - } - } else { - anchor = suffix; - } - } - - // Skip non-documentation links (images, external assets, etc.) - const ext = path.extname(pathPortion).toLowerCase(); - if ( - ext && - ext !== '.md' && - !['.md'].includes(ext) && // Has an extension that's not .md - skip unless it's a trailing slash path - !pathPortion.endsWith('/') - ) { - return null; - } - - // Check if original path ends with / (directory reference) BEFORE path.join normalizes it - const isDirectoryPath = pathPortion.endsWith('/'); - - let absolutePath; - - if (pathPortion.startsWith('/docs/')) { - // Already repo-relative with /docs/ prefix - absolutePath = path.join(path.dirname(DOCS_ROOT), pathPortion); - } else if (pathPortion.startsWith('/')) { - // Site-relative (e.g., /tutorials/getting-started/) - resolve from docs root - absolutePath = path.join(DOCS_ROOT, pathPortion); - } else { - // Relative path (./, ../, or bare filename) - resolve from current file's directory - const currentDir = path.dirname(currentFilePath); - absolutePath = path.resolve(currentDir, pathPortion); - } - - // Convert to repo-relative path (with /docs/ prefix) - let repoRelative = '/docs/' + path.relative(DOCS_ROOT, absolutePath); - - // Normalize path separators for Windows - repoRelative = repoRelative.split(path.sep).join('/'); - - // If original path was a directory reference (ended with /), check for index.md or file.md - if (isDirectoryPath) { - const relativeDir = repoRelative.slice(6); // Remove '/docs/' - - // Handle root path case (relativeDir is empty or just '.') - const normalizedDir = relativeDir === '' || relativeDir === '.' ? '' : relativeDir; - const indexPath = path.join(DOCS_ROOT, normalizedDir, 'index.md'); - const filePath = normalizedDir ? path.join(DOCS_ROOT, normalizedDir + '.md') : null; - - if (fs.existsSync(indexPath)) { - // Avoid double slash when repoRelative is '/docs/' (root case) - repoRelative = repoRelative.endsWith('/') ? repoRelative + 'index.md' : repoRelative + '/index.md'; - } else if (filePath && fs.existsSync(filePath)) { - repoRelative = repoRelative + '.md'; - } else { - // Neither exists - default to index.md and let validation catch it - repoRelative = repoRelative.endsWith('/') ? repoRelative + 'index.md' : repoRelative + '/index.md'; - } - } else if (!repoRelative.endsWith('.md')) { - // Path doesn't end with .md - add .md - repoRelative = repoRelative + '.md'; - } - - return repoRelative + query + anchor; -} - -/** - * Process a single markdown file, skipping links inside fenced code blocks - * - * @param {string} filePath - Absolute path to the file - * @returns {Object} - { changed: boolean, original: string, updated: string, changes: Array } - */ -function processFile(filePath) { - const original = fs.readFileSync(filePath, 'utf-8'); - const changes = []; - - // Extract fenced code blocks and replace with placeholders - const codeBlocks = []; - const CODE_PLACEHOLDER = '\u0000CODE_BLOCK_'; - - let contentWithPlaceholders = original.replaceAll(/```[\s\S]*?```/g, (match) => { - const index = codeBlocks.length; - codeBlocks.push(match); - return `${CODE_PLACEHOLDER}${index}\u0000`; - }); - - // Process links only in non-code-block content - contentWithPlaceholders = contentWithPlaceholders.replaceAll(ALL_MARKDOWN_LINKS_REGEX, (match, linkText, href) => { - const newHref = convertToRepoRelative(href, filePath); - - // Skip if conversion returned null (external link, anchor, etc.) - if (newHref === null) { - return match; - } - - // Only record as change if actually different - if (newHref !== href) { - changes.push({ from: href, to: newHref }); - return `[${linkText}](${newHref})`; - } - - return match; - }); - - // Restore code blocks - const updated = contentWithPlaceholders.replaceAll( - new RegExp(`${CODE_PLACEHOLDER}(\\d+)\u0000`, 'g'), - (match, index) => codeBlocks[parseInt(index, 10)], - ); - - return { - changed: changes.length > 0, - original, - updated, - changes, - }; -} - -/** - * Validate that a repo-relative link points to an existing file - */ -function validateLink(repoRelativePath) { - // Strip anchor/query - const checkPath = repoRelativePath.split('#')[0].split('?')[0]; - - // Remove /docs/ prefix to get path relative to DOCS_ROOT - const relativePath = checkPath.startsWith('/docs/') ? checkPath.slice(6) : checkPath.slice(1); - - return fs.existsSync(path.join(DOCS_ROOT, relativePath)); -} - -// Main execution -console.log(`\nScanning docs in: ${DOCS_ROOT}`); -console.log(`Mode: ${DRY_RUN ? 'DRY RUN (use --write to apply changes)' : 'WRITE MODE'}\n`); - -const files = getMarkdownFiles(DOCS_ROOT); -console.log(`Found ${files.length} markdown files (excluding _* paths)\n`); - -let totalChanges = 0; -let filesChanged = 0; -const brokenLinks = []; - -for (const filePath of files) { - const relativePath = path.relative(DOCS_ROOT, filePath); - const result = processFile(filePath); - - if (result.changed) { - filesChanged++; - totalChanges += result.changes.length; - - console.log(`\n${relativePath}`); - for (const change of result.changes) { - const isValid = validateLink(change.to); - const status = isValid ? ' ' : '! '; - - console.log(`${status} ${change.from}`); - console.log(` -> ${change.to}`); - - if (!isValid) { - brokenLinks.push({ - file: relativePath, - link: change.to, - original: change.from, - }); - } - } - - if (!DRY_RUN) { - fs.writeFileSync(filePath, result.updated, 'utf-8'); - } - } -} - -console.log(`\n${'─'.repeat(60)}`); -console.log(`\nSummary:`); -console.log(` Files scanned: ${files.length}`); -console.log(` Files with changes: ${filesChanged}`); -console.log(` Total link updates: ${totalChanges}`); - -if (brokenLinks.length > 0) { - console.log(`\n! Potential broken links (${brokenLinks.length}):`); - for (const bl of brokenLinks) { - console.log(` ${bl.file}: ${bl.link}`); - } -} - -if (DRY_RUN && totalChanges > 0) { - console.log(`\nRun with --write to apply these changes`); -} - -console.log(''); diff --git a/tools/format-workflow-md.js b/tools/format-workflow-md.js deleted file mode 100755 index 6079b620e..000000000 --- a/tools/format-workflow-md.js +++ /dev/null @@ -1,263 +0,0 @@ -/** - * BMAD Workflow Markdown Formatter - * - * Formats mixed markdown + XML workflow instruction files with: - * - 2-space XML indentation - * - Preserved markdown content - * - Proper tag nesting - * - Consistent formatting - */ - -const fs = require('node:fs'); -const path = require('node:path'); - -class WorkflowFormatter { - constructor(options = {}) { - this.indentSize = options.indentSize || 2; - this.preserveMarkdown = options.preserveMarkdown !== false; - this.verbose = options.verbose || false; - } - - /** - * Format a workflow markdown file - */ - format(filePath) { - if (this.verbose) { - console.log(`Formatting: ${filePath}`); - } - - const content = fs.readFileSync(filePath, 'utf8'); - const formatted = this.formatContent(content); - - // Only write if content changed - if (content === formatted) { - if (this.verbose) { - console.log(`- No changes: ${filePath}`); - } - return false; - } else { - fs.writeFileSync(filePath, formatted, 'utf8'); - if (this.verbose) { - console.log(`✓ Formatted: ${filePath}`); - } - return true; - } - } - - /** - * Format content string with stateful indentation tracking - */ - formatContent(content) { - const lines = content.split('\n'); - const formatted = []; - let indentLevel = 0; - let inCodeBlock = false; - let checkBlockDepth = 0; // Track nested check blocks - - for (let i = 0; i < lines.length; i++) { - const line = lines[i]; - const trimmed = line.trim(); - - // Track code blocks (don't format inside them) - if (trimmed.startsWith('```')) { - if (inCodeBlock) { - inCodeBlock = false; - } else { - inCodeBlock = true; - } - formatted.push(line); - continue; - } - - // Don't format inside code blocks - if (inCodeBlock) { - formatted.push(line); - continue; - } - - // Handle XML tags - if (this.isXMLLine(trimmed)) { - const result = this.formatXMLLine(trimmed, indentLevel, checkBlockDepth, i, lines); - formatted.push(result.line); - indentLevel = result.nextIndent; - checkBlockDepth = result.nextCheckDepth; - } else if (trimmed === '') { - // Preserve blank lines - formatted.push(''); - } else { - // Markdown content - preserve as-is but maintain current indent if inside XML - formatted.push(line); - } - } - - return formatted.join('\n'); - } - - /** - * Check if line contains XML tag - */ - isXMLLine(line) { - return /^<[a-zA-Z-]+(\s|>|\/)/.test(line) || /^<\/[a-zA-Z-]+>/.test(line); - } - - /** - * Format a single XML line with context awareness - */ - formatXMLLine(line, currentIndent, checkDepth, lineIndex, allLines) { - const trimmed = line.trim(); - let indent = currentIndent; - let nextIndent = currentIndent; - let nextCheckDepth = checkDepth; - - // Get the tag name - const tagMatch = trimmed.match(/^<\/?([a-zA-Z-]+)/); - const tagName = tagMatch ? tagMatch[1] : ''; - - // Closing tag - decrease indent before this line - if (trimmed.startsWith('</')) { - indent = Math.max(0, currentIndent - 1); - nextIndent = indent; - - // If closing a step, reset check depth - if (tagName === 'step' || tagName === 'workflow') { - nextCheckDepth = 0; - } - } - // Self-closing tags (opens and closes on same line) - // EXCEPT <check> tags which create logical blocks - else if (this.isSelfClosingTag(trimmed) && tagName !== 'check') { - // These don't change indent level - indent = currentIndent; - nextIndent = currentIndent; - } - // Opening tags - else if (trimmed.startsWith('<')) { - // Check if this is a <check> tag - these create logical blocks - if (tagName === 'check') { - indent = currentIndent; - // Check tags increase indent for following content - nextIndent = currentIndent + 1; - nextCheckDepth = checkDepth + 1; - } - // <action> tags inside check blocks stay at current indent - else if (tagName === 'action' && checkDepth > 0) { - indent = currentIndent; - nextIndent = currentIndent; // Don't increase further - } - // Other tags close check blocks and return to structural level - else if (checkDepth > 0) { - // Close all check blocks - return to base structural level - indent = Math.max(0, currentIndent - checkDepth); - nextIndent = indent + 1; - nextCheckDepth = 0; - } - // Regular opening tags (no check blocks active) - else { - indent = currentIndent; - nextIndent = currentIndent + 1; - } - } - - const indentStr = ' '.repeat(indent * this.indentSize); - return { - line: indentStr + trimmed, - nextIndent: nextIndent, - nextCheckDepth: nextCheckDepth, - }; - } - - /** - * Check if tag opens and closes on same line - */ - isSelfClosingTag(line) { - // Self-closing with /> - if (line.endsWith('/>')) { - return true; - } - // Opens and closes on same line: <tag>content</tag> - const match = line.match(/^<([a-zA-Z-]+)(\s[^>]*)?>.*<\/\1>$/); - return match !== null; - } - - /** - * Check if tag is a block-level structural tag - */ - isBlockLevelTag(tagName) { - return ['step', 'workflow', 'check'].includes(tagName); - } -} - -/** - * CLI Entry Point - */ -function main() { - const args = process.argv.slice(2); - - if (args.length === 0 || args.includes('--help') || args.includes('-h')) { - console.log(` -BMAD Workflow Markdown Formatter - -Usage: - node format-workflow-md.js <file-pattern> [options] - -Options: - --verbose, -v Verbose output - --check, -c Check formatting without writing (exit 1 if changes needed) - --help, -h Show this help - -Examples: - node format-workflow-md.js src/**/instructions.md - node format-workflow-md.js "src/modules/bmb/**/*.md" --verbose - node format-workflow-md.js file.md --check -`); - process.exit(0); - } - - const verbose = args.includes('--verbose') || args.includes('-v'); - const check = args.includes('--check') || args.includes('-c'); - - // Remove flags from args - const files = args.filter((arg) => !arg.startsWith('-')); - - const formatter = new WorkflowFormatter({ verbose }); - let hasChanges = false; - let formattedCount = 0; - - // Process files - for (const pattern of files) { - // For now, treat as direct file path - // TODO: Add glob support for patterns - if (fs.existsSync(pattern)) { - const stat = fs.statSync(pattern); - if (stat.isFile()) { - const changed = formatter.format(pattern); - if (changed) { - hasChanges = true; - formattedCount++; - } - } else if (stat.isDirectory()) { - console.error(`Error: ${pattern} is a directory. Please specify file paths.`); - } - } else { - console.error(`Error: File not found: ${pattern}`); - } - } - - if (verbose || formattedCount > 0) { - console.log(`\nFormatted ${formattedCount} file(s)`); - } - - if (check && hasChanges) { - console.error('\n❌ Some files need formatting. Run without --check to format.'); - process.exit(1); - } - - process.exit(0); -} - -// Run if called directly -if (require.main === module) { - main(); -} - -module.exports = { WorkflowFormatter }; diff --git a/tools/lib/xml-utils.js b/tools/lib/xml-utils.js deleted file mode 100644 index 482373151..000000000 --- a/tools/lib/xml-utils.js +++ /dev/null @@ -1,13 +0,0 @@ -/** - * Escape XML special characters in a string - * @param {string} text - The text to escape - * @returns {string} The escaped text - */ -function escapeXml(text) { - if (!text) return ''; - return text.replaceAll('&', '&').replaceAll('<', '<').replaceAll('>', '>').replaceAll('"', '"').replaceAll("'", '''); -} - -module.exports = { - escapeXml, -}; diff --git a/tools/migrate-custom-module-paths.js b/tools/migrate-custom-module-paths.js deleted file mode 100755 index 13aa3e710..000000000 --- a/tools/migrate-custom-module-paths.js +++ /dev/null @@ -1,124 +0,0 @@ -/** - * Migration script to convert relative paths to absolute paths in custom module manifests - * This should be run once to update existing installations - */ - -const fs = require('fs-extra'); -const path = require('node:path'); -const yaml = require('yaml'); -const chalk = require('chalk'); - -/** - * Find BMAD directory in project - */ -function findBmadDir(projectDir = process.cwd()) { - const possibleNames = ['_bmad']; - - for (const name of possibleNames) { - const bmadDir = path.join(projectDir, name); - if (fs.existsSync(bmadDir)) { - return bmadDir; - } - } - - return null; -} - -/** - * Update manifest to use absolute paths - */ -async function updateManifest(manifestPath, projectRoot) { - console.log(chalk.cyan(`\nUpdating manifest: ${manifestPath}`)); - - const content = await fs.readFile(manifestPath, 'utf8'); - const manifest = yaml.parse(content); - - if (!manifest.customModules || manifest.customModules.length === 0) { - console.log(chalk.dim(' No custom modules found')); - return false; - } - - let updated = false; - - for (const customModule of manifest.customModules) { - if (customModule.relativePath && !customModule.sourcePath) { - // Convert relative path to absolute - const absolutePath = path.resolve(projectRoot, customModule.relativePath); - customModule.sourcePath = absolutePath; - - // Remove the old relativePath - delete customModule.relativePath; - - console.log(chalk.green(` ✓ Updated ${customModule.id}: ${customModule.relativePath} → ${absolutePath}`)); - updated = true; - } else if (customModule.sourcePath && !path.isAbsolute(customModule.sourcePath)) { - // Source path exists but is not absolute - const absolutePath = path.resolve(customModule.sourcePath); - customModule.sourcePath = absolutePath; - - console.log(chalk.green(` ✓ Updated ${customModule.id}: ${customModule.sourcePath} → ${absolutePath}`)); - updated = true; - } - } - - if (updated) { - // Write back the updated manifest - const yamlStr = yaml.dump(manifest, { - indent: 2, - lineWidth: -1, - noRefs: true, - sortKeys: false, - }); - - await fs.writeFile(manifestPath, yamlStr); - console.log(chalk.green(' Manifest updated successfully')); - } else { - console.log(chalk.dim(' All paths already absolute')); - } - - return updated; -} - -/** - * Main migration function - */ -async function migrate(directory) { - const projectRoot = path.resolve(directory || process.cwd()); - const bmadDir = findBmadDir(projectRoot); - - if (!bmadDir) { - console.error(chalk.red('✗ No BMAD installation found in directory')); - process.exit(1); - } - - console.log(chalk.blue.bold('🔄 BMAD Custom Module Path Migration')); - console.log(chalk.dim(`Project: ${projectRoot}`)); - console.log(chalk.dim(`BMAD Directory: ${bmadDir}`)); - - const manifestPath = path.join(bmadDir, '_config', 'manifest.yaml'); - - if (!fs.existsSync(manifestPath)) { - console.error(chalk.red('✗ No manifest.yaml found')); - process.exit(1); - } - - const updated = await updateManifest(manifestPath, projectRoot); - - if (updated) { - console.log(chalk.green.bold('\n✨ Migration completed successfully!')); - console.log(chalk.dim('Custom modules now use absolute source paths.')); - } else { - console.log(chalk.yellow('\n⚠ No migration needed - paths already absolute')); - } -} - -// Run migration if called directly -if (require.main === module) { - const directory = process.argv[2]; - migrate(directory).catch((error) => { - console.error(chalk.red('\n✗ Migration failed:'), error.message); - process.exit(1); - }); -} - -module.exports = { migrate }; diff --git a/tools/platform-codes.yaml b/tools/platform-codes.yaml deleted file mode 100644 index 97846a9bd..000000000 --- a/tools/platform-codes.yaml +++ /dev/null @@ -1,157 +0,0 @@ -# BMAD Platform Codes Configuration -# Central configuration for all platform/IDE codes used in the BMAD system -# -# This file defines the standardized platform codes that are used throughout -# the installation system to identify different platforms (IDEs, tools, etc.) -# -# Format: -# code: Platform identifier used internally -# name: Display name shown to users -# preferred: Whether this platform is shown as a recommended option on install -# category: Type of platform (ide, tool, service, etc.) - -platforms: - # Recommended Platforms - claude-code: - name: "Claude Code" - preferred: true - category: cli - description: "Anthropic's official CLI for Claude" - - cursor: - name: "Cursor" - preferred: true - category: ide - description: "AI-first code editor" - - # Other IDEs and Tools - cline: - name: "Cline" - preferred: false - category: ide - description: "AI coding assistant" - - opencode: - name: "OpenCode" - preferred: false - category: ide - description: "OpenCode terminal coding assistant" - - codebuddy: - name: "CodeBuddy" - preferred: false - category: ide - description: "Tencent Cloud Code Assistant - AI-powered coding companion" - - auggie: - name: "Auggie" - preferred: false - category: cli - description: "AI development tool" - - roo: - name: "Roo Cline" - preferred: false - category: ide - description: "Enhanced Cline fork" - - rovo-dev: - name: "Rovo Dev" - preferred: false - category: ide - description: "Atlassian's Rovo development environment" - - kiro: - name: "Kiro" - preferred: false - category: ide - description: "Amazon's AI-powered IDE" - - github-copilot: - name: "GitHub Copilot" - preferred: false - category: ide - description: "GitHub's AI pair programmer" - - codex: - name: "Codex" - preferred: false - category: cli - description: "OpenAI Codex integration" - - qwen: - name: "QwenCoder" - preferred: false - category: ide - description: "Qwen AI coding assistant" - - gemini: - name: "Gemini CLI" - preferred: false - category: cli - description: "Google's CLI for Gemini" - - iflow: - name: "iFlow" - preferred: false - category: ide - description: "AI workflow automation" - - kilo: - name: "KiloCoder" - preferred: false - category: ide - description: "AI coding platform" - - crush: - name: "Crush" - preferred: false - category: ide - description: "AI development assistant" - - antigravity: - name: "Google Antigravity" - preferred: false - category: ide - description: "Google's AI development environment" - - trae: - name: "Trae" - preferred: false - category: ide - description: "AI coding tool" - - windsurf: - name: "Windsurf" - preferred: false - category: ide - description: "AI-powered IDE with cascade flows" - -# Platform categories -categories: - ide: - name: "Integrated Development Environment" - description: "Full-featured code editors with AI assistance" - - cli: - name: "Command Line Interface" - description: "Terminal-based tools" - - tool: - name: "Development Tool" - description: "Standalone development utilities" - - service: - name: "Cloud Service" - description: "Cloud-based development platforms" - - extension: - name: "Editor Extension" - description: "Plugins for existing editors" - -# Naming conventions and rules -conventions: - code_format: "lowercase-kebab-case" - name_format: "Title Case" - max_code_length: 20 - allowed_characters: "a-z0-9-" diff --git a/tools/schema/agent.js b/tools/schema/agent.js deleted file mode 100644 index 93ced7c6e..000000000 --- a/tools/schema/agent.js +++ /dev/null @@ -1,491 +0,0 @@ -// Zod schema definition for *.agent.yaml files -const assert = require('node:assert'); -const { z } = require('zod'); - -const COMMAND_TARGET_KEYS = ['workflow', 'validate-workflow', 'exec', 'action', 'tmpl', 'data']; -const TRIGGER_PATTERN = /^[a-z0-9]+(?:-[a-z0-9]+)*$/; -const COMPOUND_TRIGGER_PATTERN = /^([A-Z]{1,3}) or fuzzy match on ([a-z0-9]+(?:-[a-z0-9]+)*)$/; - -/** - * Derive the expected shortcut from a kebab-case trigger. - * - Single word: first letter (e.g., "help" → "H") - * - Multi-word: first letter of first two words (e.g., "tech-spec" → "TS") - * @param {string} kebabTrigger The kebab-case trigger name. - * @returns {string} The expected uppercase shortcut. - */ -function deriveShortcutFromKebab(kebabTrigger) { - const words = kebabTrigger.split('-'); - if (words.length === 1) { - return words[0][0].toUpperCase(); - } - return (words[0][0] + words[1][0]).toUpperCase(); -} - -/** - * Parse and validate a compound trigger string. - * Format: "<SHORTCUT> or fuzzy match on <kebab-case>" - * @param {string} triggerValue The trigger string to parse. - * @returns {{ valid: boolean, shortcut?: string, kebabTrigger?: string, error?: string }} - */ -function parseCompoundTrigger(triggerValue) { - const match = COMPOUND_TRIGGER_PATTERN.exec(triggerValue); - if (!match) { - return { valid: false, error: 'invalid compound trigger format' }; - } - - const [, shortcut, kebabTrigger] = match; - - return { valid: true, shortcut, kebabTrigger }; -} - -// Public API --------------------------------------------------------------- - -/** - * Validate an agent YAML payload against the schema derived from its file location. - * Exposed as the single public entry point, so callers do not reach into schema internals. - * - * @param {string} filePath Path to the agent file (used to infer module scope). - * @param {unknown} agentYaml Parsed YAML content. - * @returns {import('zod').SafeParseReturnType<unknown, unknown>} SafeParse result. - */ -function validateAgentFile(filePath, agentYaml) { - const expectedModule = deriveModuleFromPath(filePath); - const schema = agentSchema({ module: expectedModule }); - return schema.safeParse(agentYaml); -} - -module.exports = { validateAgentFile }; - -// Internal helpers --------------------------------------------------------- - -/** - * Build a Zod schema for validating a single agent definition. - * The schema is generated per call so module-scoped agents can pass their expected - * module slug while core agents leave it undefined. - * - * @param {Object} [options] - * @param {string|null|undefined} [options.module] Module slug for module agents; omit or null for core agents. - * @returns {import('zod').ZodSchema} Configured Zod schema instance. - */ -function agentSchema(options = {}) { - const expectedModule = normalizeModuleOption(options.module); - - return ( - z - .object({ - agent: buildAgentSchema(expectedModule), - }) - .strict() - // Refinement: enforce trigger format and uniqueness rules after structural checks. - .superRefine((value, ctx) => { - const seenTriggers = new Set(); - - let index = 0; - for (const item of value.agent.menu) { - // Handle legacy format with trigger field - if (item.trigger) { - const triggerValue = item.trigger; - let canonicalTrigger = triggerValue; - - // Check if it's a compound trigger (contains " or ") - if (triggerValue.includes(' or ')) { - const result = parseCompoundTrigger(triggerValue); - if (!result.valid) { - ctx.addIssue({ - code: 'custom', - path: ['agent', 'menu', index, 'trigger'], - message: `agent.menu[].trigger compound format error: ${result.error}`, - }); - return; - } - - // Validate that shortcut matches description brackets - const descriptionMatch = item.description?.match(/^\[([A-Z]{1,3})\]/); - if (!descriptionMatch) { - ctx.addIssue({ - code: 'custom', - path: ['agent', 'menu', index, 'description'], - message: `agent.menu[].description must start with [SHORTCUT] where SHORTCUT matches the trigger shortcut "${result.shortcut}"`, - }); - return; - } - - const descriptionShortcut = descriptionMatch[1]; - if (descriptionShortcut !== result.shortcut) { - ctx.addIssue({ - code: 'custom', - path: ['agent', 'menu', index, 'description'], - message: `agent.menu[].description shortcut "[${descriptionShortcut}]" must match trigger shortcut "${result.shortcut}"`, - }); - return; - } - - canonicalTrigger = result.kebabTrigger; - } else if (!TRIGGER_PATTERN.test(triggerValue)) { - ctx.addIssue({ - code: 'custom', - path: ['agent', 'menu', index, 'trigger'], - message: 'agent.menu[].trigger must be kebab-case (lowercase words separated by hyphen)', - }); - return; - } - - if (seenTriggers.has(canonicalTrigger)) { - ctx.addIssue({ - code: 'custom', - path: ['agent', 'menu', index, 'trigger'], - message: `agent.menu[].trigger duplicates "${canonicalTrigger}" within the same agent`, - }); - return; - } - - seenTriggers.add(canonicalTrigger); - } - // Handle multi format with triggers array (new format) - else if (item.triggers && Array.isArray(item.triggers)) { - for (const [triggerIndex, triggerItem] of item.triggers.entries()) { - let triggerName = null; - - // Extract trigger name from all three formats - if (triggerItem.trigger) { - // Format 1: Simple flat format with trigger field - triggerName = triggerItem.trigger; - } else { - // Format 2a or 2b: Object-key format - const keys = Object.keys(triggerItem); - if (keys.length === 1 && keys[0] !== 'trigger') { - triggerName = keys[0]; - } - } - - if (triggerName) { - if (!TRIGGER_PATTERN.test(triggerName)) { - ctx.addIssue({ - code: 'custom', - path: ['agent', 'menu', index, 'triggers', triggerIndex], - message: `agent.menu[].triggers[] must be kebab-case (lowercase words separated by hyphen) - got "${triggerName}"`, - }); - return; - } - - if (seenTriggers.has(triggerName)) { - ctx.addIssue({ - code: 'custom', - path: ['agent', 'menu', index, 'triggers', triggerIndex], - message: `agent.menu[].triggers[] duplicates "${triggerName}" within the same agent`, - }); - return; - } - - seenTriggers.add(triggerName); - } - } - } - - index += 1; - } - }) - // Refinement: suggest conversational_knowledge when discussion is true - .superRefine((value, ctx) => { - if (value.agent.discussion === true && !value.agent.conversational_knowledge) { - ctx.addIssue({ - code: 'custom', - path: ['agent', 'conversational_knowledge'], - message: 'It is recommended to include conversational_knowledge when discussion is true', - }); - } - }) - ); -} - -/** - * Assemble the full agent schema using the module expectation provided by the caller. - * @param {string|null} expectedModule Trimmed module slug or null for core agents. - */ -function buildAgentSchema(expectedModule) { - return z - .object({ - metadata: buildMetadataSchema(expectedModule), - persona: buildPersonaSchema(), - critical_actions: z.array(createNonEmptyString('agent.critical_actions[]')).optional(), - menu: z.array(buildMenuItemSchema()).min(1, { message: 'agent.menu must include at least one entry' }), - prompts: z.array(buildPromptSchema()).optional(), - discussion: z.boolean().optional(), - conversational_knowledge: z.array(z.object({}).passthrough()).min(1).optional(), - }) - .strict(); -} - -/** - * Validate metadata shape. - * @param {string|null} expectedModule Trimmed module slug or null when core agent metadata is expected. - * Note: Module field is optional and can be any value - no validation against path. - */ -function buildMetadataSchema(expectedModule) { - const schemaShape = { - id: createNonEmptyString('agent.metadata.id'), - name: createNonEmptyString('agent.metadata.name'), - title: createNonEmptyString('agent.metadata.title'), - icon: createNonEmptyString('agent.metadata.icon'), - module: createNonEmptyString('agent.metadata.module').optional(), - capabilities: createNonEmptyString('agent.metadata.capabilities').optional(), - hasSidecar: z.boolean(), - }; - - return z.object(schemaShape).strict(); -} - -function buildPersonaSchema() { - return z - .object({ - role: createNonEmptyString('agent.persona.role'), - identity: createNonEmptyString('agent.persona.identity'), - communication_style: createNonEmptyString('agent.persona.communication_style'), - principles: z.union([ - createNonEmptyString('agent.persona.principles'), - z - .array(createNonEmptyString('agent.persona.principles[]')) - .min(1, { message: 'agent.persona.principles must include at least one entry' }), - ]), - }) - .strict(); -} - -function buildPromptSchema() { - return z - .object({ - id: createNonEmptyString('agent.prompts[].id'), - content: z.string().refine((value) => value.trim().length > 0, { - message: 'agent.prompts[].content must be a non-empty string', - }), - description: createNonEmptyString('agent.prompts[].description').optional(), - }) - .strict(); -} - -/** - * Schema for individual menu entries ensuring they are actionable. - * Supports both legacy format and new multi format. - */ -function buildMenuItemSchema() { - // Legacy menu item format - const legacyMenuItemSchema = z - .object({ - trigger: createNonEmptyString('agent.menu[].trigger'), - description: createNonEmptyString('agent.menu[].description'), - workflow: createNonEmptyString('agent.menu[].workflow').optional(), - 'workflow-install': createNonEmptyString('agent.menu[].workflow-install').optional(), - 'validate-workflow': createNonEmptyString('agent.menu[].validate-workflow').optional(), - exec: createNonEmptyString('agent.menu[].exec').optional(), - action: createNonEmptyString('agent.menu[].action').optional(), - tmpl: createNonEmptyString('agent.menu[].tmpl').optional(), - data: z.string().optional(), - checklist: createNonEmptyString('agent.menu[].checklist').optional(), - document: createNonEmptyString('agent.menu[].document').optional(), - 'ide-only': z.boolean().optional(), - 'web-only': z.boolean().optional(), - discussion: z.boolean().optional(), - }) - .strict() - .superRefine((value, ctx) => { - const hasCommandTarget = COMMAND_TARGET_KEYS.some((key) => { - const commandValue = value[key]; - return typeof commandValue === 'string' && commandValue.trim().length > 0; - }); - - if (!hasCommandTarget) { - ctx.addIssue({ - code: 'custom', - message: 'agent.menu[] entries must include at least one command target field', - }); - } - }); - - // Multi menu item format - const multiMenuItemSchema = z - .object({ - multi: createNonEmptyString('agent.menu[].multi'), - triggers: z - .array( - z.union([ - // Format 1: Simple flat format (has trigger field) - z - .object({ - trigger: z.string(), - input: createNonEmptyString('agent.menu[].triggers[].input'), - route: createNonEmptyString('agent.menu[].triggers[].route').optional(), - action: createNonEmptyString('agent.menu[].triggers[].action').optional(), - data: z.string().optional(), - type: z.enum(['exec', 'action', 'workflow']).optional(), - }) - .strict() - .refine((data) => data.trigger, { message: 'Must have trigger field' }) - .superRefine((value, ctx) => { - // Must have either route or action (or both) - if (!value.route && !value.action) { - ctx.addIssue({ - code: 'custom', - message: 'agent.menu[].triggers[] must have either route or action (or both)', - }); - } - }), - // Format 2a: Object with array format (like bmad-builder.agent.yaml) - z - .object({}) - .passthrough() - .refine( - (value) => { - const keys = Object.keys(value); - if (keys.length !== 1) return false; - const triggerItems = value[keys[0]]; - return Array.isArray(triggerItems); - }, - { message: 'Must be object with single key pointing to array' }, - ) - .superRefine((value, ctx) => { - const triggerName = Object.keys(value)[0]; - const triggerItems = value[triggerName]; - - if (!Array.isArray(triggerItems)) { - ctx.addIssue({ - code: 'custom', - message: `Trigger "${triggerName}" must be an array of items`, - }); - return; - } - - // Check required fields in the array - const hasInput = triggerItems.some((item) => 'input' in item); - const hasRouteOrAction = triggerItems.some((item) => 'route' in item || 'action' in item); - - if (!hasInput) { - ctx.addIssue({ - code: 'custom', - message: `Trigger "${triggerName}" must have an input field`, - }); - } - - if (!hasRouteOrAction) { - ctx.addIssue({ - code: 'custom', - message: `Trigger "${triggerName}" must have a route or action field`, - }); - } - }), - // Format 2b: Object with direct fields (like analyst.agent.yaml) - z - .object({}) - .passthrough() - .refine( - (value) => { - const keys = Object.keys(value); - if (keys.length !== 1) return false; - const triggerFields = value[keys[0]]; - return !Array.isArray(triggerFields) && typeof triggerFields === 'object'; - }, - { message: 'Must be object with single key pointing to object' }, - ) - .superRefine((value, ctx) => { - const triggerName = Object.keys(value)[0]; - const triggerFields = value[triggerName]; - - // Check required fields - if (!triggerFields.input || typeof triggerFields.input !== 'string') { - ctx.addIssue({ - code: 'custom', - message: `Trigger "${triggerName}" must have an input field`, - }); - } - - if (!triggerFields.route && !triggerFields.action) { - ctx.addIssue({ - code: 'custom', - message: `Trigger "${triggerName}" must have a route or action field`, - }); - } - }), - ]), - ) - .min(1, { message: 'agent.menu[].triggers must have at least one trigger' }), - discussion: z.boolean().optional(), - }) - .strict() - .superRefine((value, ctx) => { - // Check for duplicate trigger names - const seenTriggers = new Set(); - for (const [index, triggerItem] of value.triggers.entries()) { - let triggerName = null; - - // Extract trigger name from either format - if (triggerItem.trigger) { - // Format 1 - triggerName = triggerItem.trigger; - } else { - // Format 2 - const keys = Object.keys(triggerItem); - if (keys.length === 1) { - triggerName = keys[0]; - } - } - - if (triggerName) { - if (seenTriggers.has(triggerName)) { - ctx.addIssue({ - code: 'custom', - path: ['agent', 'menu', 'triggers', index], - message: `Trigger name "${triggerName}" is duplicated`, - }); - } - seenTriggers.add(triggerName); - - // Validate trigger name format - if (!TRIGGER_PATTERN.test(triggerName)) { - ctx.addIssue({ - code: 'custom', - path: ['agent', 'menu', 'triggers', index], - message: `Trigger name "${triggerName}" must be kebab-case (lowercase words separated by hyphen)`, - }); - } - } - } - }); - - return z.union([legacyMenuItemSchema, multiMenuItemSchema]); -} - -/** - * Derive the expected module slug from a file path residing under src/<module>/agents/. - * @param {string} filePath Absolute or relative agent path. - * @returns {string|null} Module slug if identifiable, otherwise null. - */ -function deriveModuleFromPath(filePath) { - assert(filePath, 'validateAgentFile expects filePath to be provided'); - assert(typeof filePath === 'string', 'validateAgentFile expects filePath to be a string'); - assert(filePath.startsWith('src/'), 'validateAgentFile expects filePath to start with "src/"'); - - const marker = 'src/'; - if (!filePath.startsWith(marker)) { - return null; - } - - const remainder = filePath.slice(marker.length); - const slashIndex = remainder.indexOf('/'); - return slashIndex === -1 ? null : remainder.slice(0, slashIndex); -} - -function normalizeModuleOption(moduleOption) { - if (typeof moduleOption !== 'string') { - return null; - } - - const trimmed = moduleOption.trim(); - return trimmed.length > 0 ? trimmed : null; -} - -// Primitive validators ----------------------------------------------------- - -function createNonEmptyString(label) { - return z.string().refine((value) => value.trim().length > 0, { - message: `${label} must be a non-empty string`, - }); -} diff --git a/tools/validate-agent-schema.js b/tools/validate-agent-schema.js deleted file mode 100644 index 9c3595fef..000000000 --- a/tools/validate-agent-schema.js +++ /dev/null @@ -1,110 +0,0 @@ -/** - * Agent Schema Validator CLI - * - * Scans all *.agent.yaml files in src/{core,modules/*}/agents/ - * and validates them against the Zod schema. - * - * Usage: node tools/validate-agent-schema.js [project_root] - * Exit codes: 0 = success, 1 = validation failures - * - * Optional argument: - * project_root - Directory to scan (defaults to BMAD repo root) - */ - -const { glob } = require('glob'); -const yaml = require('yaml'); -const fs = require('node:fs'); -const path = require('node:path'); -const { validateAgentFile } = require('./schema/agent.js'); - -/** - * Main validation routine - * @param {string} [customProjectRoot] - Optional project root to scan (for testing) - */ -async function main(customProjectRoot) { - console.log('🔍 Scanning for agent files...\n'); - - // Determine project root: use custom path if provided, otherwise default to repo root - const project_root = customProjectRoot || path.join(__dirname, '..'); - - // Find all agent files - const agentFiles = await glob('src/{core,bmm}/agents/**/*.agent.yaml', { - cwd: project_root, - absolute: true, - }); - - if (agentFiles.length === 0) { - console.log('❌ No agent files found. This likely indicates a configuration error.'); - console.log(' Expected to find *.agent.yaml files in src/{core,modules/*}/agents/'); - process.exit(1); - } - - console.log(`Found ${agentFiles.length} agent file(s)\n`); - - const errors = []; - - // Validate each file - for (const filePath of agentFiles) { - const relativePath = path.relative(process.cwd(), filePath); - - try { - const fileContent = fs.readFileSync(filePath, 'utf8'); - const agentData = yaml.parse(fileContent); - - // Convert absolute path to relative src/ path for module detection - const srcRelativePath = relativePath.startsWith('src/') ? relativePath : path.relative(project_root, filePath).replaceAll('\\', '/'); - - const result = validateAgentFile(srcRelativePath, agentData); - - if (result.success) { - console.log(`✅ ${relativePath}`); - } else { - errors.push({ - file: relativePath, - issues: result.error.issues, - }); - } - } catch (error) { - errors.push({ - file: relativePath, - issues: [ - { - code: 'parse_error', - message: `Failed to parse YAML: ${error.message}`, - path: [], - }, - ], - }); - } - } - - // Report errors - if (errors.length > 0) { - console.log('\n❌ Validation failed for the following files:\n'); - - for (const { file, issues } of errors) { - console.log(`\n📄 ${file}`); - for (const issue of issues) { - const pathString = issue.path.length > 0 ? issue.path.join('.') : '(root)'; - console.log(` Path: ${pathString}`); - console.log(` Error: ${issue.message}`); - if (issue.code) { - console.log(` Code: ${issue.code}`); - } - } - } - - console.log(`\n\n💥 ${errors.length} file(s) failed validation`); - process.exit(1); - } - - console.log(`\n✨ All ${agentFiles.length} agent file(s) passed validation!\n`); - process.exit(0); -} - -// Run with optional command-line argument for project root -const customProjectRoot = process.argv[2]; -main(customProjectRoot).catch((error) => { - console.error('Fatal error:', error); - process.exit(1); -}); diff --git a/tools/validate-doc-links.js b/tools/validate-doc-links.js deleted file mode 100644 index 167268c90..000000000 --- a/tools/validate-doc-links.js +++ /dev/null @@ -1,407 +0,0 @@ -/** - * Documentation Link Validator - * - * Validates site-relative links in markdown files and attempts to fix broken ones. - * - * What it checks: - * - All site-relative links (starting with /) point to existing .md files - * - Anchor links (#section) point to valid headings - * - * What it fixes: - * - Broken links where the target file can be found elsewhere in /docs - * - * Usage: - * node tools/validate-doc-links.js # Dry run (validate and show issues) - * node tools/validate-doc-links.js --write # Fix auto-fixable issues - */ - -const fs = require('node:fs'); -const path = require('node:path'); - -const DOCS_ROOT = path.resolve(__dirname, '../docs'); -const DRY_RUN = !process.argv.includes('--write'); - -// Regex to match markdown links with site-relative paths or bare .md references -const LINK_REGEX = /\[([^\]]*)\]\(((?:\.{1,2}\/|\/)[^)]+|[\w][^)\s]*\.md(?:[?#][^)]*)?)\)/g; - -// File extensions that are static assets, not markdown docs -const STATIC_ASSET_EXTENSIONS = ['.zip', '.txt', '.pdf', '.png', '.jpg', '.jpeg', '.gif', '.svg', '.webp', '.ico']; - -// Custom Astro page routes (not part of the docs content collection) -const CUSTOM_PAGE_ROUTES = new Set([]); - -// Regex to extract headings for anchor validation -const HEADING_PATTERN = /^#{1,6}\s+(.+)$/gm; - -/** - * Get all markdown files in docs directory, excluding _* directories/files - */ -function getMarkdownFiles(dir) { - const files = []; - - function walk(currentDir) { - const entries = fs.readdirSync(currentDir, { withFileTypes: true }); - - for (const entry of entries) { - const fullPath = path.join(currentDir, entry.name); - - if (entry.name.startsWith('_')) { - continue; - } - - if (entry.isDirectory()) { - walk(fullPath); - } else if (entry.isFile() && (entry.name.endsWith('.md') || entry.name.endsWith('.mdx'))) { - files.push(fullPath); - } - } - } - - walk(dir); - return files; -} - -/** - * Strip fenced code blocks from content - */ -function stripCodeBlocks(content) { - return content.replaceAll(/```[\s\S]*?```/g, ''); -} - -/** - * Convert a heading to its anchor slug - */ -function headingToAnchor(heading) { - return heading - .toLowerCase() - .replaceAll(/[\u{1F300}-\u{1F9FF}]/gu, '') // Remove emojis - .replaceAll(/[^\w\s-]/g, '') // Remove special chars - .replaceAll(/\s+/g, '-') // Spaces to hyphens - .replaceAll(/-+/g, '-') // Collapse hyphens - .replaceAll(/^-+|-+$/g, ''); // Trim hyphens -} - -/** - * Extract anchor slugs from a markdown file - */ -function extractAnchors(content) { - const anchors = new Set(); - let match; - - HEADING_PATTERN.lastIndex = 0; - while ((match = HEADING_PATTERN.exec(content)) !== null) { - const headingText = match[1] - .trim() - .replaceAll(/`[^`]+`/g, '') - .replaceAll(/\*\*([^*]+)\*\*/g, '$1') - .replaceAll(/\*([^*]+)\*/g, '$1') - .replaceAll(/\[([^\]]+)\]\([^)]+\)/g, '$1') - .trim(); - anchors.add(headingToAnchor(headingText)); - } - - return anchors; -} - -/** - * Resolve a site-relative link to a file path - * /docs/how-to/installation/install-bmad.md -> docs/how-to/installation/install-bmad.md - * /how-to/installation/install-bmad/ -> docs/how-to/installation/install-bmad.md or .../index.md - */ -function resolveLink(siteRelativePath, sourceFile) { - // Strip anchor and query - let checkPath = siteRelativePath.split('#')[0].split('?')[0]; - - // Handle relative paths (including bare .md): resolve from source file's directory - if (checkPath.startsWith('./') || checkPath.startsWith('../') || (!checkPath.startsWith('/') && checkPath.endsWith('.md'))) { - const sourceDir = path.dirname(sourceFile); - const resolved = path.resolve(sourceDir, checkPath); - // Ensure the resolved path stays within DOCS_ROOT - if (!resolved.startsWith(DOCS_ROOT + path.sep) && resolved !== DOCS_ROOT) return null; - if (fs.existsSync(resolved) && fs.statSync(resolved).isFile()) return resolved; - if (fs.existsSync(resolved + '.md')) return resolved + '.md'; - if (fs.existsSync(resolved + '.mdx')) return resolved + '.mdx'; - // Directory: check for index.md or index.mdx - if (fs.existsSync(resolved) && fs.statSync(resolved).isDirectory()) { - const indexFile = path.join(resolved, 'index.md'); - const indexMdxFile = path.join(resolved, 'index.mdx'); - if (fs.existsSync(indexFile)) return indexFile; - if (fs.existsSync(indexMdxFile)) return indexMdxFile; - } - return null; - } - - // Strip /docs/ prefix if present (legacy absolute links) - if (checkPath.startsWith('/docs/')) { - checkPath = checkPath.slice(5); // Remove '/docs' but keep leading '/' - } - - if (checkPath.endsWith('/')) { - // Could be file.md, file.mdx, or directory/index.md/mdx - const baseName = checkPath.slice(0, -1); - const asMd = path.join(DOCS_ROOT, baseName + '.md'); - const asMdx = path.join(DOCS_ROOT, baseName + '.mdx'); - const asIndex = path.join(DOCS_ROOT, checkPath, 'index.md'); - const asIndexMdx = path.join(DOCS_ROOT, checkPath, 'index.mdx'); - - if (fs.existsSync(asMd)) return asMd; - if (fs.existsSync(asMdx)) return asMdx; - if (fs.existsSync(asIndex)) return asIndex; - if (fs.existsSync(asIndexMdx)) return asIndexMdx; - return null; - } - - // Direct path (e.g., /path/file.md) - const direct = path.join(DOCS_ROOT, checkPath); - if (fs.existsSync(direct) && fs.statSync(direct).isFile()) return direct; - - // Try with .md extension - const withMd = direct + '.md'; - if (fs.existsSync(withMd)) return withMd; - - // Try with .mdx extension - const withMdx = direct + '.mdx'; - if (fs.existsSync(withMdx)) return withMdx; - - // Directory without trailing slash: check for index.md or index.mdx - if (fs.existsSync(direct) && fs.statSync(direct).isDirectory()) { - const indexFile = path.join(direct, 'index.md'); - const indexMdxFile = path.join(direct, 'index.mdx'); - if (fs.existsSync(indexFile)) return indexFile; - if (fs.existsSync(indexMdxFile)) return indexMdxFile; - } - - return null; -} - -/** - * Search for a file with directory context - */ -function findFileWithContext(brokenPath) { - // Extract filename and parent directory from the broken path - // e.g., /tutorials/getting-started/foo/ -> parent: getting-started, file: foo.md - const cleanPath = brokenPath.replace(/\/$/, '').replace(/^(\.\.\/|\.\/|\/)+/, ''); - const parts = cleanPath.split('/'); - const fileName = parts.at(-1) + '.md'; - const parentDir = parts.length > 1 ? parts.at(-2) : null; - - const allFiles = getMarkdownFiles(DOCS_ROOT); - const matches = []; - - for (const file of allFiles) { - const fileBaseName = path.basename(file); - const fileParentDir = path.basename(path.dirname(file)); - - // Exact filename match with parent directory context - if (fileBaseName === fileName) { - if (parentDir && fileParentDir === parentDir) { - // Strong match: both filename and parent dir match - return [file]; - } - matches.push(file); - } - - // Also check for index.md in a matching directory - if (fileBaseName === 'index.md' && fileParentDir === fileName.replace('.md', '')) { - matches.push(file); - } - } - - return matches; -} - -/** - * Convert absolute file path to site-relative URL - */ -function fileToSiteRelative(filePath) { - let relative = '/' + path.relative(DOCS_ROOT, filePath); - relative = relative.split(path.sep).join('/'); - - if (relative.endsWith('/index.md')) { - return relative.replace(/\/index\.md$/, '/'); - } - return relative.replace(/\.md$/, '/'); -} - -/** - * Process a single file and find issues - */ -function processFile(filePath) { - const content = fs.readFileSync(filePath, 'utf-8'); - const strippedContent = stripCodeBlocks(content); - const issues = []; - - let match; - LINK_REGEX.lastIndex = 0; - - while ((match = LINK_REGEX.exec(strippedContent)) !== null) { - const linkText = match[1]; - const href = match[2]; - - // Extract path and anchor - const hashIndex = href.indexOf('#'); - const linkPath = hashIndex === -1 ? href : href.slice(0, hashIndex); - const anchor = hashIndex === -1 ? null : href.slice(hashIndex + 1); - - // Skip static asset links (zip, txt, images, etc.) - const linkLower = linkPath.toLowerCase(); - if (STATIC_ASSET_EXTENSIONS.some((ext) => linkLower.endsWith(ext))) { - continue; - } - - // Skip custom Astro page routes - if (CUSTOM_PAGE_ROUTES.has(linkPath)) { - continue; - } - - // Validate the link target exists - const targetFile = resolveLink(linkPath, filePath); - - if (!targetFile) { - // Link is broken - try to find the file - const candidates = findFileWithContext(linkPath); - - const issue = { - type: 'broken-link', - linkText, - href, - linkPath, - fullMatch: match[0], - }; - - if (candidates.length === 1) { - issue.status = 'auto-fixable'; - issue.suggestedFix = fileToSiteRelative(candidates[0]) + (anchor ? '#' + anchor : ''); - issue.foundAt = path.relative(DOCS_ROOT, candidates[0]); - } else if (candidates.length > 1) { - issue.status = 'needs-review'; - issue.candidates = candidates.map((c) => path.relative(DOCS_ROOT, c)); - } else { - issue.status = 'manual-check'; - } - - issues.push(issue); - continue; - } - - // Validate anchor if present - if (anchor) { - const targetContent = fs.readFileSync(targetFile, 'utf-8'); - const anchors = extractAnchors(targetContent); - - if (!anchors.has(anchor)) { - issues.push({ - type: 'broken-anchor', - linkText, - href, - anchor, - status: 'manual-check', - message: `Anchor "#${anchor}" not found`, - }); - } - } - } - - return { content, issues }; -} - -/** - * Apply fixes to file content - */ -function applyFixes(content, issues) { - let updated = content; - - for (const issue of issues) { - if (issue.status === 'auto-fixable' && issue.suggestedFix) { - const oldLink = `[${issue.linkText}](${issue.href})`; - const newLink = `[${issue.linkText}](${issue.suggestedFix})`; - updated = updated.replace(oldLink, newLink); - } - } - - return updated; -} - -// Main execution -console.log(`\nValidating docs in: ${DOCS_ROOT}`); -console.log(`Mode: ${DRY_RUN ? 'DRY RUN (use --write to fix)' : 'WRITE MODE'}\n`); - -const files = getMarkdownFiles(DOCS_ROOT); -console.log(`Found ${files.length} markdown files\n`); - -let totalIssues = 0; -let autoFixable = 0; -let needsReview = 0; -let manualCheck = 0; -let filesWithIssues = 0; - -const allIssues = []; - -for (const filePath of files) { - const relativePath = path.relative(DOCS_ROOT, filePath); - const { content, issues } = processFile(filePath); - - if (issues.length > 0) { - filesWithIssues++; - totalIssues += issues.length; - - console.log(`\n${relativePath}`); - - for (const issue of issues) { - if (issue.status === 'auto-fixable') { - autoFixable++; - console.log(` [FIX] ${issue.href}`); - console.log(` -> ${issue.suggestedFix}`); - } else if (issue.status === 'needs-review') { - needsReview++; - console.log(` [REVIEW] ${issue.href}`); - console.log(` Multiple matches found:`); - for (const candidate of issue.candidates) { - console.log(` - ${candidate}`); - } - } else if (issue.type === 'broken-anchor') { - manualCheck++; - console.log(` [MANUAL] ${issue.href}`); - console.log(` ${issue.message}`); - } else { - manualCheck++; - console.log(` [MANUAL] ${issue.href}`); - console.log(` File not found anywhere - may need to remove link`); - } - - allIssues.push({ file: relativePath, ...issue }); - } - - // Apply fixes if not dry run - if (!DRY_RUN) { - const fixableIssues = issues.filter((i) => i.status === 'auto-fixable'); - if (fixableIssues.length > 0) { - const updated = applyFixes(content, fixableIssues); - fs.writeFileSync(filePath, updated, 'utf-8'); - } - } - } -} - -console.log(`\n${'─'.repeat(60)}`); -console.log(`\nSummary:`); -console.log(` Files scanned: ${files.length}`); -console.log(` Files with issues: ${filesWithIssues}`); -console.log(` Total issues: ${totalIssues}`); - -if (totalIssues > 0) { - console.log(`\n Breakdown:`); - console.log(` Auto-fixable: ${autoFixable}`); - console.log(` Needs review: ${needsReview}`); - console.log(` Manual check: ${manualCheck}`); -} - -if (totalIssues === 0) { - console.log(`\n All links valid!`); -} else if (DRY_RUN && autoFixable > 0) { - console.log(`\nRun with --write to auto-fix ${autoFixable} issue(s)`); -} - -console.log(''); - -process.exit(totalIssues > 0 ? 1 : 0); diff --git a/tools/validate-file-refs.js b/tools/validate-file-refs.js deleted file mode 100644 index bf92f31f8..000000000 --- a/tools/validate-file-refs.js +++ /dev/null @@ -1,554 +0,0 @@ -/** - * File Reference Validator - * - * Validates cross-file references in BMAD source files (agents, workflows, tasks, steps). - * Catches broken file paths, missing referenced files, and absolute path leaks. - * - * What it checks: - * - {project-root}/_bmad/ references in YAML and markdown resolve to real src/ files - * - Relative path references (./file.md, ../data/file.csv) point to existing files - * - exec="..." and <invoke-task> targets exist - * - Step metadata (thisStepFile, nextStepFile) references are valid - * - Load directives (Load: `./file.md`) target existing files - * - No absolute paths (/Users/, /home/, C:\) leak into source files - * - * What it does NOT check (deferred): - * - {installed_path} variable interpolation (self-referential, low risk) - * - {{mustache}} template variables (runtime substitution) - * - {config_source}:key dynamic YAML dereferences - * - * Usage: - * node tools/validate-file-refs.js # Warn on broken references (exit 0) - * node tools/validate-file-refs.js --strict # Fail on broken references (exit 1) - * node tools/validate-file-refs.js --verbose # Show all checked references - * - * Default mode is warning-only (exit 0) so adoption is non-disruptive. - * Use --strict when you want CI or pre-commit to enforce valid references. - */ - -const fs = require('node:fs'); -const path = require('node:path'); -const yaml = require('yaml'); -const { parse: parseCsv } = require('csv-parse/sync'); - -const PROJECT_ROOT = path.resolve(__dirname, '..'); -const SRC_DIR = path.join(PROJECT_ROOT, 'src'); -const VERBOSE = process.argv.includes('--verbose'); -const STRICT = process.argv.includes('--strict'); - -// --- Constants --- - -// File extensions to scan -const SCAN_EXTENSIONS = new Set(['.yaml', '.yml', '.md', '.xml', '.csv']); - -// Skip directories -const SKIP_DIRS = new Set(['node_modules', '.git']); - -// Pattern: {project-root}/_bmad/ references -const PROJECT_ROOT_REF = /\{project-root\}\/_bmad\/([^\s'"<>})\]`]+)/g; - -// Pattern: {_bmad}/ shorthand references -const BMAD_SHORTHAND_REF = /\{_bmad\}\/([^\s'"<>})\]`]+)/g; - -// Pattern: exec="..." attributes -const EXEC_ATTR = /exec="([^"]+)"/g; - -// Pattern: <invoke-task> content -const INVOKE_TASK = /<invoke-task>([^<]+)<\/invoke-task>/g; - -// Pattern: relative paths in quotes -const RELATIVE_PATH_QUOTED = /['"](\.\.\/?[^'"]+\.(?:md|yaml|yml|xml|json|csv|txt))['"]/g; -const RELATIVE_PATH_DOT = /['"](\.\/[^'"]+\.(?:md|yaml|yml|xml|json|csv|txt))['"]/g; - -// Pattern: step metadata -const STEP_META = /(?:thisStepFile|nextStepFile|continueStepFile|skipToStepFile|altStepFile|workflowFile):\s*['"](\.[^'"]+)['"]/g; - -// Pattern: Load directives -const LOAD_DIRECTIVE = /Load[:\s]+`(\.[^`]+)`/g; - -// Pattern: absolute path leaks -const ABS_PATH_LEAK = /(?:\/Users\/|\/home\/|[A-Z]:\\\\)/; - -// --- Output Escaping --- - -function escapeAnnotation(str) { - return str.replaceAll('%', '%25').replaceAll('\r', '%0D').replaceAll('\n', '%0A'); -} - -function escapeTableCell(str) { - return String(str).replaceAll('|', String.raw`\|`); -} - -// Path prefixes/patterns that only exist in installed structure, not in source -const INSTALL_ONLY_PATHS = ['_config/']; - -// Files that are generated at install time and don't exist in the source tree -const INSTALL_GENERATED_FILES = ['config.yaml']; - -// Variables that indicate a path is not statically resolvable -const UNRESOLVABLE_VARS = [ - '{output_folder}', - '{value}', - '{timestamp}', - '{config_source}:', - '{installed_path}', - '{shared_path}', - '{planning_artifacts}', - '{research_topic}', - '{user_name}', - '{communication_language}', - '{epic_number}', - '{next_epic_num}', - '{epic_num}', - '{part_id}', - '{count}', - '{date}', - '{outputFile}', - '{nextStepFile}', -]; - -// --- File Discovery --- - -function getSourceFiles(dir) { - const files = []; - - function walk(currentDir) { - const entries = fs.readdirSync(currentDir, { withFileTypes: true }); - - for (const entry of entries) { - if (SKIP_DIRS.has(entry.name)) continue; - - const fullPath = path.join(currentDir, entry.name); - - if (entry.isDirectory()) { - walk(fullPath); - } else if (entry.isFile() && SCAN_EXTENSIONS.has(path.extname(entry.name))) { - files.push(fullPath); - } - } - } - - walk(dir); - return files; -} - -// --- Code Block Stripping --- - -function stripCodeBlocks(content) { - return content.replaceAll(/```[\s\S]*?```/g, (m) => m.replaceAll(/[^\n]/g, '')); -} - -function stripJsonExampleBlocks(content) { - // Strip bare JSON example blocks: { and } each on their own line. - // These are example/template data (not real file references). - return content.replaceAll(/^\{\s*\n(?:.*\n)*?^\}\s*$/gm, (m) => m.replaceAll(/[^\n]/g, '')); -} - -// --- Path Mapping --- - -function mapInstalledToSource(refPath) { - // Strip {project-root}/_bmad/ or {_bmad}/ prefix - let cleaned = refPath.replace(/^\{project-root\}\/_bmad\//, '').replace(/^\{_bmad\}\//, ''); - - // Also handle bare _bmad/ prefix (seen in some invoke-task) - cleaned = cleaned.replace(/^_bmad\//, ''); - - // Skip install-only paths (generated at install time, not in source) - if (isInstallOnly(cleaned)) return null; - - // core/, bmm/, and utility/ are directly under src/ - if (cleaned.startsWith('core/') || cleaned.startsWith('bmm/') || cleaned.startsWith('utility/')) { - return path.join(SRC_DIR, cleaned); - } - - // Fallback: map directly under src/ - return path.join(SRC_DIR, cleaned); -} - -// --- Reference Extraction --- - -function isResolvable(refStr) { - // Skip refs containing unresolvable runtime variables - if (refStr.includes('{{')) return false; - for (const v of UNRESOLVABLE_VARS) { - if (refStr.includes(v)) return false; - } - return true; -} - -function isInstallOnly(cleanedPath) { - // Skip paths that only exist in the installed _bmad/ structure, not in src/ - for (const prefix of INSTALL_ONLY_PATHS) { - if (cleanedPath.startsWith(prefix)) return true; - } - // Skip files that are generated during installation - const basename = path.basename(cleanedPath); - for (const generated of INSTALL_GENERATED_FILES) { - if (basename === generated) return true; - } - return false; -} - -function extractYamlRefs(filePath, content) { - const refs = []; - - let doc; - try { - doc = yaml.parseDocument(content); - } catch { - return refs; // Skip unparseable YAML (schema validator handles this) - } - - function checkValue(value, range, keyPath) { - if (typeof value !== 'string') return; - if (!isResolvable(value)) return; - - const line = range ? offsetToLine(content, range[0]) : undefined; - - // Check for {project-root}/_bmad/ refs - const prMatch = value.match(/\{project-root\}\/_bmad\/[^\s'"<>})\]`]+/); - if (prMatch) { - refs.push({ file: filePath, raw: prMatch[0], type: 'project-root', line, key: keyPath }); - } - - // Check for {_bmad}/ refs - const bmMatch = value.match(/\{_bmad\}\/[^\s'"<>})\]`]+/); - if (bmMatch) { - refs.push({ file: filePath, raw: bmMatch[0], type: 'project-root', line, key: keyPath }); - } - - // Check for relative paths - const relMatch = value.match(/^\.\.?\/[^\s'"<>})\]`]+\.(?:md|yaml|yml|xml|json|csv|txt)$/); - if (relMatch) { - refs.push({ file: filePath, raw: relMatch[0], type: 'relative', line, key: keyPath }); - } - } - - function walkNode(node, keyPath) { - if (!node) return; - - if (yaml.isMap(node)) { - for (const item of node.items) { - const key = item.key && item.key.value !== undefined ? item.key.value : '?'; - const childPath = keyPath ? `${keyPath}.${key}` : String(key); - walkNode(item.value, childPath); - } - } else if (yaml.isSeq(node)) { - for (const [i, item] of node.items.entries()) { - walkNode(item, `${keyPath}[${i}]`); - } - } else if (yaml.isScalar(node)) { - checkValue(node.value, node.range, keyPath); - } - } - - walkNode(doc.contents, ''); - return refs; -} - -function offsetToLine(content, offset) { - let line = 1; - for (let i = 0; i < offset && i < content.length; i++) { - if (content[i] === '\n') line++; - } - return line; -} - -function extractMarkdownRefs(filePath, content) { - const refs = []; - const stripped = stripJsonExampleBlocks(stripCodeBlocks(content)); - - function runPattern(regex, type) { - regex.lastIndex = 0; - let match; - while ((match = regex.exec(stripped)) !== null) { - const raw = match[1]; - if (!isResolvable(raw)) continue; - refs.push({ file: filePath, raw, type, line: offsetToLine(stripped, match.index) }); - } - } - - // {project-root}/_bmad/ refs - runPattern(PROJECT_ROOT_REF, 'project-root'); - - // {_bmad}/ shorthand - runPattern(BMAD_SHORTHAND_REF, 'project-root'); - - // exec="..." attributes - runPattern(EXEC_ATTR, 'exec-attr'); - - // <invoke-task> tags - runPattern(INVOKE_TASK, 'invoke-task'); - - // Step metadata - runPattern(STEP_META, 'relative'); - - // Load directives - runPattern(LOAD_DIRECTIVE, 'relative'); - - // Relative paths in quotes - runPattern(RELATIVE_PATH_QUOTED, 'relative'); - runPattern(RELATIVE_PATH_DOT, 'relative'); - - return refs; -} - -function extractCsvRefs(filePath, content) { - const refs = []; - - let records; - try { - records = parseCsv(content, { - columns: true, - skip_empty_lines: true, - relax_column_count: true, - }); - } catch (error) { - // No CSV schema validator exists yet (planned as Layer 2c) — surface parse errors visibly. - // YAML equivalent (line ~198) defers to validate-agent-schema.js; CSV has no such fallback. - const rel = path.relative(PROJECT_ROOT, filePath); - console.error(` [CSV-PARSE-ERROR] ${rel}: ${error.message}`); - if (process.env.GITHUB_ACTIONS) { - console.log(`::warning file=${rel},line=1::${escapeAnnotation(`CSV parse error: ${error.message}`)}`); - } - return refs; - } - - // Only process if workflow-file column exists - const firstRecord = records[0]; - if (!firstRecord || !('workflow-file' in firstRecord)) { - return refs; - } - - for (const [i, record] of records.entries()) { - const raw = record['workflow-file']; - if (!raw || raw.trim() === '') continue; - if (!isResolvable(raw)) continue; - - // Line = header (1) + data row index (0-based) + 1 - const line = i + 2; - refs.push({ file: filePath, raw, type: 'project-root', line }); - } - - return refs; -} - -// --- Reference Resolution --- - -function resolveRef(ref) { - if (ref.type === 'project-root') { - return mapInstalledToSource(ref.raw); - } - - if (ref.type === 'relative') { - return path.resolve(path.dirname(ref.file), ref.raw); - } - - if (ref.type === 'exec-attr') { - let execPath = ref.raw; - if (execPath.includes('{project-root}')) { - return mapInstalledToSource(execPath); - } - if (execPath.includes('{_bmad}')) { - return mapInstalledToSource(execPath); - } - if (execPath.startsWith('_bmad/')) { - return mapInstalledToSource(execPath); - } - // Relative exec path - return path.resolve(path.dirname(ref.file), execPath); - } - - if (ref.type === 'invoke-task') { - // Extract file path from invoke-task content - const prMatch = ref.raw.match(/\{project-root\}\/_bmad\/([^\s'"<>})\]`]+)/); - if (prMatch) return mapInstalledToSource(prMatch[0]); - - const bmMatch = ref.raw.match(/\{_bmad\}\/([^\s'"<>})\]`]+)/); - if (bmMatch) return mapInstalledToSource(bmMatch[0]); - - const bareMatch = ref.raw.match(/_bmad\/([^\s'"<>})\]`]+)/); - if (bareMatch) return mapInstalledToSource(bareMatch[0]); - - return null; // Can't resolve — skip - } - - return null; -} - -// --- Absolute Path Leak Detection --- - -function checkAbsolutePathLeaks(filePath, content) { - const leaks = []; - const stripped = stripCodeBlocks(content); - const lines = stripped.split('\n'); - - for (const [i, line] of lines.entries()) { - if (ABS_PATH_LEAK.test(line)) { - leaks.push({ file: filePath, line: i + 1, content: line.trim() }); - } - } - - return leaks; -} - -// --- Exports (for testing) --- -module.exports = { extractCsvRefs }; - -// --- Main --- - -if (require.main === module) { - console.log(`\nValidating file references in: ${SRC_DIR}`); - console.log(`Mode: ${STRICT ? 'STRICT (exit 1 on issues)' : 'WARNING (exit 0)'}${VERBOSE ? ' + VERBOSE' : ''}\n`); - - const files = getSourceFiles(SRC_DIR); - console.log(`Found ${files.length} source files\n`); - - let totalRefs = 0; - let brokenRefs = 0; - let totalLeaks = 0; - let filesWithIssues = 0; - const allIssues = []; // Collect for $GITHUB_STEP_SUMMARY - - for (const filePath of files) { - const relativePath = path.relative(PROJECT_ROOT, filePath); - const content = fs.readFileSync(filePath, 'utf-8'); - const ext = path.extname(filePath); - - // Extract references - let refs; - if (ext === '.yaml' || ext === '.yml') { - refs = extractYamlRefs(filePath, content); - } else if (ext === '.csv') { - refs = extractCsvRefs(filePath, content); - } else { - refs = extractMarkdownRefs(filePath, content); - } - - // Resolve and classify all refs before printing anything. - // This avoids the confusing pattern of printing headers at two different - // times depending on verbosity — collect first, then print once. - const broken = []; - const ok = []; - - for (const ref of refs) { - totalRefs++; - const resolved = resolveRef(ref); - - if (resolved && !fs.existsSync(resolved)) { - // Extensionless paths may be directory references or partial templates. - // If the path has no extension, check whether it exists as a directory. - // Flag it if nothing exists at all — likely a real broken reference. - const hasExt = path.extname(resolved) !== ''; - if (!hasExt) { - if (fs.existsSync(resolved)) { - ok.push({ ref, tag: 'OK-DIR' }); - } else { - // No extension and nothing exists — not a file, not a directory. - // Flag as UNRESOLVED (distinct from BROKEN which means "file with extension not found"). - broken.push({ ref, resolved: path.relative(PROJECT_ROOT, resolved), kind: 'unresolved' }); - brokenRefs++; - } - continue; - } - broken.push({ ref, resolved: path.relative(PROJECT_ROOT, resolved), kind: 'broken' }); - brokenRefs++; - continue; - } - - if (resolved) { - ok.push({ ref, tag: 'OK' }); - } - } - - // Check absolute path leaks - const leaks = checkAbsolutePathLeaks(filePath, content); - totalLeaks += leaks.length; - - // Print results — file header appears once, in one place - const hasFileIssues = broken.length > 0 || leaks.length > 0; - - if (hasFileIssues) { - filesWithIssues++; - console.log(`\n${relativePath}`); - - if (VERBOSE) { - for (const { ref, tag, note } of ok) { - const suffix = note ? ` (${note})` : ''; - console.log(` [${tag}] ${ref.raw}${suffix}`); - } - } - - for (const { ref, resolved, kind } of broken) { - const location = ref.line ? `line ${ref.line}` : ref.key ? `key: ${ref.key}` : ''; - const tag = kind === 'unresolved' ? 'UNRESOLVED' : 'BROKEN'; - const detail = kind === 'unresolved' ? 'Not found as file or directory' : 'Target not found'; - const issueType = kind === 'unresolved' ? 'unresolved path' : 'broken ref'; - console.log(` [${tag}] ${ref.raw}${location ? ` (${location})` : ''}`); - console.log(` ${detail}: ${resolved}`); - allIssues.push({ file: relativePath, line: ref.line || 1, ref: ref.raw, issue: issueType }); - if (process.env.GITHUB_ACTIONS) { - const line = ref.line || 1; - console.log( - `::warning file=${relativePath},line=${line}::${escapeAnnotation(`${tag === 'UNRESOLVED' ? 'Unresolved path' : 'Broken reference'}: ${ref.raw} → ${resolved}`)}`, - ); - } - } - - for (const leak of leaks) { - console.log(` [ABS-PATH] Line ${leak.line}: ${leak.content}`); - allIssues.push({ file: relativePath, line: leak.line, ref: leak.content, issue: 'abs-path' }); - if (process.env.GITHUB_ACTIONS) { - console.log(`::warning file=${relativePath},line=${leak.line}::${escapeAnnotation(`Absolute path leak: ${leak.content}`)}`); - } - } - } else if (VERBOSE && refs.length > 0) { - console.log(`\n${relativePath}`); - for (const { ref, tag, note } of ok) { - const suffix = note ? ` (${note})` : ''; - console.log(` [${tag}] ${ref.raw}${suffix}`); - } - } - } - - // Summary - console.log(`\n${'─'.repeat(60)}`); - console.log(`\nSummary:`); - console.log(` Files scanned: ${files.length}`); - console.log(` References checked: ${totalRefs}`); - console.log(` Broken references: ${brokenRefs}`); - console.log(` Absolute path leaks: ${totalLeaks}`); - - const hasIssues = brokenRefs > 0 || totalLeaks > 0; - - if (hasIssues) { - console.log(`\n ${filesWithIssues} file(s) with issues`); - - if (STRICT) { - console.log(`\n [STRICT MODE] Exiting with failure.`); - } else { - console.log(`\n Run with --strict to treat warnings as errors.`); - } - } else { - console.log(`\n All file references valid!`); - } - - console.log(''); - - // Write GitHub Actions step summary - if (process.env.GITHUB_STEP_SUMMARY) { - let summary = '## File Reference Validation\n\n'; - if (allIssues.length > 0) { - summary += '| File | Line | Reference | Issue |\n'; - summary += '|------|------|-----------|-------|\n'; - for (const issue of allIssues) { - summary += `| ${escapeTableCell(issue.file)} | ${issue.line} | ${escapeTableCell(issue.ref)} | ${issue.issue} |\n`; - } - summary += '\n'; - } - summary += `**${files.length} files scanned, ${totalRefs} references checked, ${brokenRefs + totalLeaks} issues found**\n`; - fs.appendFileSync(process.env.GITHUB_STEP_SUMMARY, summary); - } - - process.exit(hasIssues && STRICT ? 1 : 0); -} diff --git a/tools/validate-svg-changes.sh b/tools/validate-svg-changes.sh deleted file mode 100755 index 3138bfb27..000000000 --- a/tools/validate-svg-changes.sh +++ /dev/null @@ -1,356 +0,0 @@ -#!/bin/bash -# -# Visual SVG Validation Script -# -# Compares old vs new SVG files using browser-accurate rendering (Playwright) -# and pixel-level comparison (ImageMagick), then generates a prompt for AI analysis. -# -# Usage: ./tools/validate-svg-changes.sh <path-to-svg> -# - -set -e - -SVG_FILE="${1:-src/bmm/docs/images/workflow-method-greenfield.svg}" -TMP_DIR="/tmp/svg-validation-$$" - -echo "🎨 Visual SVG Validation" -echo "" - -# Check if file exists -if [ ! -f "$SVG_FILE" ]; then - echo "❌ Error: SVG file not found: $SVG_FILE" - exit 1 -fi - -# Check for ImageMagick -if ! command -v magick &> /dev/null; then - echo "❌ ImageMagick not found" - echo "" - echo "Install with:" - echo " brew install imagemagick" - echo "" - exit 1 -fi - -echo "✓ ImageMagick found" - -# Check for Node.js -if ! command -v node &> /dev/null; then - echo "❌ Node.js not found" - exit 1 -fi - -echo "✓ Node.js found ($(node -v))" - -# Check for Playwright (local install) -if [ ! -d "node_modules/playwright" ]; then - echo "" - echo "📦 Playwright not found locally" - echo "Installing Playwright (local to this project, no package.json changes)..." - echo "" - npm install --no-save playwright - echo "" - echo "✓ Playwright installed" -else - echo "✓ Playwright found" -fi - -echo "" -echo "🔄 Rendering SVGs to PNG..." -echo "" - -# Create temp directory -mkdir -p "$TMP_DIR" - -# Extract old SVG from git -git show HEAD:"$SVG_FILE" > "$TMP_DIR/old.svg" 2>/dev/null || { - echo "❌ Could not extract old SVG from git HEAD" - echo " Make sure you have uncommitted changes to compare" - exit 1 -} - -# Copy new SVG -cp "$SVG_FILE" "$TMP_DIR/new.svg" - -# Create Node.js renderer script in project directory (so it can find node_modules) -cat > "tools/render-svg-temp.js" << 'EOJS' -const { chromium } = require('playwright'); -const fs = require('fs'); - -async function renderSVG(svgPath, pngPath) { - const browser = await chromium.launch({ headless: true }); - const page = await browser.newPage(); - - const svgContent = fs.readFileSync(svgPath, 'utf8'); - const widthMatch = svgContent.match(/width="([^"]+)"/); - const heightMatch = svgContent.match(/height="([^"]+)"/); - const width = Math.ceil(parseFloat(widthMatch[1])); - const height = Math.ceil(parseFloat(heightMatch[1])); - - const html = ` - <!DOCTYPE html> - <html> - <head> - <style> - body { margin: 0; padding: 0; background: white; } - svg { display: block; } - </style> - </head> - <body>${svgContent}</body> - </html> - `; - - await page.setContent(html); - await page.setViewportSize({ width, height }); - await page.waitForTimeout(1000); - await page.screenshot({ path: pngPath, fullPage: true }); - await browser.close(); - - console.log(`✓ Rendered ${pngPath}`); -} - -(async () => { - await renderSVG(process.argv[2], process.argv[3]); - await renderSVG(process.argv[4], process.argv[5]); -})(); -EOJS - -# Render both SVGs (run from project dir so node_modules is accessible) -node tools/render-svg-temp.js \ - "$TMP_DIR/old.svg" "$TMP_DIR/old.png" \ - "$TMP_DIR/new.svg" "$TMP_DIR/new.png" - -# Clean up temp script -rm tools/render-svg-temp.js - -echo "" -echo "🔍 Comparing pixels..." -echo "" - -# Compare using ImageMagick -DIFF_OUTPUT=$(magick compare -metric AE "$TMP_DIR/old.png" "$TMP_DIR/new.png" "$TMP_DIR/diff.png" 2>&1 || true) -DIFF_PIXELS=$(echo "$DIFF_OUTPUT" | awk '{print $1}') - -# Get image dimensions -DIMENSIONS=$(magick identify -format "%wx%h" "$TMP_DIR/old.png") -WIDTH=$(echo "$DIMENSIONS" | cut -d'x' -f1) -HEIGHT=$(echo "$DIMENSIONS" | cut -d'x' -f2) -TOTAL_PIXELS=$((WIDTH * HEIGHT)) - -# Calculate percentage -DIFF_PERCENT=$(echo "scale=4; $DIFF_PIXELS / $TOTAL_PIXELS * 100" | bc) - -echo "📊 Results:" -echo " Dimensions: ${WIDTH} × ${HEIGHT}" -echo " Total pixels: $(printf "%'d" $TOTAL_PIXELS)" -echo " Different pixels: $(printf "%'d" $DIFF_PIXELS)" -echo " Difference: ${DIFF_PERCENT}%" -echo "" - -if (( $(echo "$DIFF_PERCENT < 0.01" | bc -l) )); then - echo "✅ ESSENTIALLY IDENTICAL (< 0.01% difference)" - VERDICT="essentially identical" -elif (( $(echo "$DIFF_PERCENT < 0.1" | bc -l) )); then - echo "⚠️ MINOR DIFFERENCES (< 0.1%)" - VERDICT="minor differences detected" -else - echo "❌ SIGNIFICANT DIFFERENCES (≥ 0.1%)" - VERDICT="significant differences detected" -fi - -echo "" -echo "📁 Output files:" -echo " Old render: $TMP_DIR/old.png" -echo " New render: $TMP_DIR/new.png" -echo " Diff image: $TMP_DIR/diff.png" -echo "" - -# Generate HTML comparison page -cat > "$TMP_DIR/comparison.html" << 'EOHTML' -<!DOCTYPE html> -<html> -<head> - <title>SVG Comparison - - - -
-

🎨 SVG Visual Comparison

-

File: FILENAME_PLACEHOLDER

-
-
-
Dimensions
-
DIMENSIONS_PLACEHOLDER
-
-
-
Different Pixels
-
DIFF_PIXELS_PLACEHOLDER
-
-
-
Difference
-
DIFF_PERCENT_PLACEHOLDER%
-
-
-
Verdict
-
VERDICT_PLACEHOLDER
-
-
-
- -
-
-

📄 Old (HEAD)

-
- Old SVG -
-
- -
-

📝 New (Working)

-
- New SVG -
-
- -
-

🔍 Diff (Red = Changes)

-
- Diff -
-
-
- - -EOHTML - -# Determine verdict class for styling -if (( $(echo "$DIFF_PERCENT < 0.01" | bc -l) )); then - VERDICT_CLASS="good" -elif (( $(echo "$DIFF_PERCENT < 0.1" | bc -l) )); then - VERDICT_CLASS="warning" -else - VERDICT_CLASS="bad" -fi - -# Replace placeholders in HTML -sed -i '' "s|FILENAME_PLACEHOLDER|$SVG_FILE|g" "$TMP_DIR/comparison.html" -sed -i '' "s|DIMENSIONS_PLACEHOLDER|${WIDTH} × ${HEIGHT}|g" "$TMP_DIR/comparison.html" -sed -i '' "s|DIFF_PIXELS_PLACEHOLDER|$(printf "%'d" $DIFF_PIXELS) / $(printf "%'d" $TOTAL_PIXELS)|g" "$TMP_DIR/comparison.html" -sed -i '' "s|DIFF_PERCENT_PLACEHOLDER|$DIFF_PERCENT|g" "$TMP_DIR/comparison.html" -sed -i '' "s|VERDICT_PLACEHOLDER|$VERDICT|g" "$TMP_DIR/comparison.html" -sed -i '' "s|VERDICT_CLASS_PLACEHOLDER|$VERDICT_CLASS|g" "$TMP_DIR/comparison.html" - -echo "✓ Generated comparison page: $TMP_DIR/comparison.html" -echo "" -echo "🌐 Opening comparison in browser..." -open "$TMP_DIR/comparison.html" -echo "" - -echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━" -echo "" -echo "🤖 AI VISUAL ANALYSIS PROMPT" -echo "" -echo "Copy and paste this into Gemini/Claude with the diff image attached:" -echo "" -echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━" -cat << PROMPT - -I've made changes to an Excalidraw diagram SVG file. Please analyze the visual differences between the old and new versions. - -**Automated Analysis:** -- Dimensions: ${WIDTH} × ${HEIGHT} pixels -- Different pixels: $(printf "%'d" $DIFF_PIXELS) out of $(printf "%'d" $TOTAL_PIXELS) -- Difference: ${DIFF_PERCENT}% -- Verdict: ${VERDICT} - -**Attached Image:** -The attached image shows the pixel-level diff (red = differences). - -**Questions:** -1. Are the differences purely anti-aliasing/rendering artifacts, or are there actual content changes? -2. If there are content changes, what specifically changed? -3. Do the changes align with the intent to remove zombie Excalidraw elements (elements marked as deleted but left in the JSON)? -4. Is this safe to commit? - -**Context:** -- File: $SVG_FILE -- Changes: Removed 191 lines of zombie JSON from Excalidraw source -- Expected: Visual output should be identical (zombie elements were already marked as deleted) - -PROMPT -echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━" -echo "" -echo "📎 Attach this file to your AI prompt:" -echo " $TMP_DIR/diff.png" -echo "" -echo "💡 To open the diff image:" -echo " open $TMP_DIR/diff.png" -echo "" diff --git a/website/README.md b/website/README.md deleted file mode 100644 index 911c0447f..000000000 --- a/website/README.md +++ /dev/null @@ -1,75 +0,0 @@ -# BMAD Method Documentation Site - -This directory contains the Astro + Starlight configuration for the BMAD Method documentation site. - -## Architecture - -The documentation uses a symlink architecture to keep content in `docs/` at the repo root while serving it through Astro: - -``` -bmad2/ -├── docs/ # Content lives here (repo root) -│ ├── index.md -│ ├── tutorials/ -│ ├── how-to/ -│ ├── explanation/ -│ └── reference/ -└── website/ - ├── astro.config.mjs # Astro + Starlight config - ├── src/ - │ ├── content/ - │ │ └── docs -> ../../docs # Symlink to content - │ └── styles/ - │ └── custom.css # Custom styling - └── public/ # Static assets -``` - -## Development - -```bash -# From repo root -npm run docs:dev # Start dev server -npm run docs:build # Build for production -npm run docs:preview # Preview production build -``` - -## Platform Notes - -### Windows Symlink Support - -The `website/src/content/docs` symlink may not work correctly on Windows without Developer Mode enabled or administrator privileges. - -**To enable symlinks on Windows:** - -1. **Enable Developer Mode** (recommended): - - Settings → Update & Security → For developers → Developer Mode: On - - This allows creating symlinks without admin rights - -2. **Or use Git's symlink support**: - ```bash - git config core.symlinks true - ``` - Then re-clone the repository. - -3. **Or create a junction** (alternative): - ```cmd - # Run as Administrator - mklink /J website\src\content\docs ..\..\docs - ``` - -**If symlinks don't work**, you can copy the docs folder instead: -```bash -# Remove the symlink -rm website/src/content/docs - -# Copy the docs folder -cp -r docs website/src/content/docs -``` - -Note: If copying, remember to keep the copy in sync with changes to `docs/`. - -## Build Output - -The build pipeline (`npm run docs:build`) produces: -- Static HTML site in `build/site/` -- LLM-friendly files: `llms.txt`, `llms-full.txt` diff --git a/website/astro.config.mjs b/website/astro.config.mjs deleted file mode 100644 index 565b81565..000000000 --- a/website/astro.config.mjs +++ /dev/null @@ -1,136 +0,0 @@ -// @ts-check -import { defineConfig } from 'astro/config'; -import starlight from '@astrojs/starlight'; -import sitemap from '@astrojs/sitemap'; -import rehypeMarkdownLinks from './src/rehype-markdown-links.js'; -import rehypeBasePaths from './src/rehype-base-paths.js'; -import { getSiteUrl } from './src/lib/site-url.mjs'; - -const siteUrl = getSiteUrl(); -const urlParts = new URL(siteUrl); -// Normalize basePath: ensure trailing slash so links can use `${BASE_URL}path` -const basePath = urlParts.pathname === '/' ? '/' : urlParts.pathname.endsWith('/') ? urlParts.pathname : urlParts.pathname + '/'; - -export default defineConfig({ - site: `${urlParts.origin}${basePath}`, - base: basePath, - outDir: '../build/site', - - // Disable aggressive caching in dev mode - vite: { - optimizeDeps: { - force: true, // Always re-bundle dependencies - }, - server: { - watch: { - usePolling: false, // Set to true if file changes aren't detected - }, - }, - }, - - markdown: { - rehypePlugins: [ - [rehypeMarkdownLinks, { base: basePath }], - [rehypeBasePaths, { base: basePath }], - ], - }, - - integrations: [ - sitemap(), - starlight({ - title: 'BMAD Method', - tagline: 'AI-driven agile development with specialized agents and workflows that scale from bug fixes to enterprise platforms.', - - logo: { - light: './public/img/bmad-light.png', - dark: './public/img/bmad-dark.png', - alt: 'BMAD Method', - replacesTitle: true, - }, - favicon: '/favicon.ico', - - // Social links - social: [ - { icon: 'discord', label: 'Discord', href: 'https://discord.gg/gk8jAdXWmj' }, - { icon: 'github', label: 'GitHub', href: 'https://github.com/bmad-code-org/BMAD-METHOD' }, - { icon: 'youtube', label: 'YouTube', href: 'https://www.youtube.com/@BMadCode' }, - ], - - // Show last updated timestamps - lastUpdated: true, - - // Custom head tags for LLM discovery - head: [ - { - tag: 'meta', - attrs: { - name: 'ai-terms', - content: `AI-optimized documentation: ${siteUrl}/llms-full.txt (plain text, ~100k tokens, complete BMAD reference). Index: ${siteUrl}/llms.txt`, - }, - }, - { - tag: 'meta', - attrs: { - name: 'llms-full', - content: `${siteUrl}/llms-full.txt`, - }, - }, - { - tag: 'meta', - attrs: { - name: 'llms', - content: `${siteUrl}/llms.txt`, - }, - }, - ], - - // Custom CSS - customCss: ['./src/styles/custom.css'], - - // Sidebar configuration (Diataxis structure) - sidebar: [ - { label: 'Welcome', slug: 'index' }, - { label: 'Roadmap', slug: 'roadmap' }, - { - label: 'Tutorials', - collapsed: false, - autogenerate: { directory: 'tutorials' }, - }, - { - label: 'How-To Guides', - collapsed: true, - autogenerate: { directory: 'how-to' }, - }, - { - label: 'Explanation', - collapsed: true, - autogenerate: { directory: 'explanation' }, - }, - { - label: 'Reference', - collapsed: true, - autogenerate: { directory: 'reference' }, - }, - // TEA docs moved to standalone module site; keep BMM sidebar focused. - ], - - // Credits in footer - credits: false, - - // Pagination - pagination: false, - - // Use our docs/404.md instead of Starlight's built-in 404 - disable404Route: true, - - // Custom components - components: { - Header: './src/components/Header.astro', - MobileMenuFooter: './src/components/MobileMenuFooter.astro', - }, - - // Table of contents - tableOfContents: { minHeadingLevel: 2, maxHeadingLevel: 3 }, - }), - ], -}); diff --git a/website/public/favicon.ico b/website/public/favicon.ico deleted file mode 100644 index c0e9719c559d72b71f42387b14d6fdd7cde798cd..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 4286 zcmeI0-%FEG7{^aU1y&>&vx_bUK?xDzP0?KtLC{S%T?ElhSM^6kL~0>psLA|MQaW3~ zY_J$f5DkKy#Dr9~l{&Qy6Pxo_siph&e9t_wi!MFyd*d0Oy)Wm5_jAtkoO9SSrFO{2 z>s9<#&&rkZD5a_d=~8C}_Uk6kt{p2<>`?07gZ&1N+}{zV1XyBD-rFV|6^xfxukcdX z5Nx?i-t4=YcBXXN9Ll>B{%(C4~s7PoyhaHW6Sr}K8a~5 z&h6d$Km~j)l_hvkA2_JTQ`fZDdamQ|Z((XWu}QzaPJE3ck@TbaaTRQjVK5y8+qdr@ zFp`a7bfOnO<}$i(I1}28g}r=yOm(7ASjY3|B^~qo%?HpHtVVue981g7Xz4s*H3r7t z6T1Rm>mm5t52O3V1uXxZ!E7##rj8@x=i0Or1NzzW3t7y}4vI5{Un@DxFHR!z>Z&!b znUC?0e|d|cbT?9;!^qEP_1qsmJ!Lia90UCulK)WTBJMWqLQTUSJ#WUOFX?l{Pgi2V zkLc^`h`qUi%xHvNc-LPe{xYjM7#M2DpY>I&{a*UV%4!~;#-a#3Ic|Oatz9P(>^YAv zL--sXg-+|eVEgQ0{^_V~EJLlt*-(tRy*+2v{`S?%nO1N)t~rs=Py_zlil zkM-tm!7o@nH~;f~)|;$(O%2E~I1vZddaO5D^U`f#9GDBP2d>Gj-WQx3YdzMRta-IJ RuGG%k{ENWhMrT~ye*q$z-4_4= diff --git a/website/public/img/bmad-dark.png b/website/public/img/bmad-dark.png deleted file mode 100644 index 7a12fe55c375c3c84a30cdc6c3d46cf2fddb79d7..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 65820 zcmc$F^-~-^5bqswxKrGr#ob+t6pFXFd!cx7cXueotvJQq4!7d&haS#R?C|$}Gf(FI z1@DJsc9PkAW|Qo!WD~8fs(^(~h7JG#u#^<#Gywnvod0N3RM3BY7D+M^0DvxHCo8M& zrl}x9qx4Z$fLmBVfSref8vsy@&eihN)$$~kxZgVK`xF%vSNGE)7(hpVMyr)kKFA@M9$cQFR9G54xDpka9>1%}2SKAr=k_|Dx&nHHnv=T9a+b3;+CU zQRvpT_qH3r7D!9yLR5*6#GIi-|I)qca)st#j#D57LRbO9;HxP!Oue>%ASn|LQPH_= z^4GARh(SzSIyDIWs}AtDg7KeO^t1;fN#TSLM%YO~u073+Sl|xB$jB%j;GJ@^KBfWJKxs)(k}w^yopy6`cX3iZFl4Hk0!hRH(Vlau%uay%Ltne6y)j0A61t0pk- zKfoZ3Ct&7vjr8xIXe-m3K^E#j<&EFYFP_^nqud26UAo<~({68Q`7ICAQnBw69W=(v zL>w*ovN?Yq`blV2zlQ`PjDwLr&mhZkA+pw?*f=Aq!NO@!Lv5oXy}^;%qe#sA{XDu@ z$m&ShW}@0s{0lOaeEnv&;TFzhQ+@B-FkhU>L1su)143P4N=VXCsFY?jSy5Exak_MO zs3^ap;dHc$4ETu*w9HW?$@CLR{EB#*A=)&)Nh13O`%JE6?LjxRg2}X&m=Eu~W6hbc ztcpa+(Y}Scs&n#@#LGjAn2%)K(XtX9WhQ3GZfMp*^5i)SUyf)VNpit}VskbX>c)N{ z5@L)2{5ngOm>Mv8y=FDYesHax?@Z)`D>!Fqm2~?uN)kV?@;iV12 zRa2yAd+)$-#=wWCiuZ^*5QavVT&~o_&_OT|B~}!tE5*i0#gNBfOq+mfl3LCno+3V$ zm?njv`cLt9iO(F`+`Bm@yOe4ffe)Q21EUE4%w4(LGd5H&-X|t8GFK96#fZMoN|D$5 z%v{W;Ii-1_o~KozjaZ4nAHq`frzk@MM`KzmvfRn`8y^PQ&kV)Xd4buxdDU6RxxD#f zcY+Q^@nDW(r=sQA>6yz}6ISlD>U4y3q))8rEb01bf0)F-d|)MK^<|#cGA=T#^pk7X zd5A{W8etdM)U0sTKIj+^W074{&3k ztP0;1rdKs9pH?rWR{X7S)OyguD5J{rQ6^t(nMqhMuI$$7H1L&C&>1mNDAM}lCJ&9~ zP+ry&{Op;1fwsvl9{- z$!5mVc{#~^lv_n$!+OO`$g#wR@LSX0^1h=C?$u0-oNrwNZ4>bH=nAFkF_F}-sgb2* zrNO1jDcnX{8(e~GddGmUr|Gu{5qPkLsVv`Dd2uxqlju=}uUC^IT2AE-|B*um{M z<_G7$l^V4c>3QoN=<@4g=`~i%R$o^e)a0*`tTL=P)E_rIn4a2Zn;F>quB%RRjB-r> z*}Ty4#qjO%|NX*`(h-_J@F`Lt(q^8$45REaD_|gbhvcMfs(#?AJGC)&p<>qV@9L=V zSo`>cNaPqA)L}ozv#-;uv)Wzw@Za#_*q1|}m0My#)>ijcpVmlT6&qBWg((sbL1$?D zr3-b=Sl%x_xBI`+IQ}?!3h^WUYO-p

E>`PPbaV+E8P)?(f~dw)|Z~F#-0+<7^0`^`LUX@?ekRga6h%HElI16a|C`-r*D8eZ0I478; z$O_0hNZUB|sL2sckwt~lg$A;he|hrW=PiAwYN`!7t`ULNfptv60uPuO@4GL0|{FAR0X+(xrUQ^qw$8&G*N8?zb{Zf8iT zL@BNO*qMi9x#oHMk%wl}Um(uFB6Bp(d80r3$%iOTB)6|HZ zfAP_Me7#8|ttb8btK@IV-(quqmyR}GWkGw5ula+Tnlz+_M;*>j{VsNO?j`~$;)0!@ zhtrfSH(hxj^dHox{^pG5EVpyFD-cz1;B%fBJJfp(?9RRqQ0_5~F&H;lt5*qJJ+YFV z=+3y*3$E6!E3){#Gya@TU-hg*sry+kx92fZY`rU`i`d?Lxe0o@Upr21eA?SmC{-b) z@9dwu-f?o&6)VR<^)E8YJrKBPL-DL^0) zD~RK8wc=VJ*KDaY23wk`VP9WaM{n(3kqCSWpF94&D9R+dFAAEF8DATZ9~b=DTcucY zRD1Ksp>poen)>axGE-=}QC=rm)sM>9%IyoH^Pc*VKsDufrO(I4{aZQRINvP3b@m+k z8MUg}o6PpyKMg&h;K)%ORlEJEs#^ZT=_p0Mk7a>EfMfhR49#wluNoHrTwPiu>#P`X zG~24QjZJ|qvEdTtR&ph}cUhT5IvLKcII){?wY0F**8*?pDVA0cUE5sC?rnVyc;kMt zNFP~DB+f6$8I`=c+D}O(C}Swg%TW~;-{9`uyZhC~yDUO4;yVS(7Z04e-1x;&`zIB; zIZfRO@!2{0I5o7Stol>GgR(O_(D}KreWar7_i}sddBeoPT@R^0;~y_WVgE(wNxOaU zGRN)o$t8KFxbvRR?rk4=2sw_E^@g7ZD|Bi9{EH{d6aBJsgT1@VzxGh!nmQYl3rfU! z!2GeD*b(TPDftX9JImjS-- z1>DC%IXCxQ_UNZerX^lGuG$Z;UpPy9k1|p7+wOU;5B972m$Pbdx^}vbeaN3Y+gzh$Y{ZO@mrwSIcAbp3MYuk#RRVW2h_$1uS5Hk@L;)#Z8FUUt@Sx2A#`{E^KZ zFIIPuj;KCLzt2A4;C~YTYpm$1?thbXszkBF1OI1Eh?$KH=YMg1WZNyNvlaWl%cS=I zKaA-AzZpk`KCTpV_KTT`2lWDy@*?le0c-$J5Ppy_fF6JiJVK#4+~LhYgad+hdAm#~ zz}c2>Q;=q{`Q~(>-x|5B*!iPveD*ZVH>MTknK7uxyDi}-(Cf;r z+H(!j699K&!^{F0VnM_Jn*b5O0wSu9g{kkgBR)8&^}#Gr0E+C$?(?uD{R^SvZ8Mpu#_wWXL}0agSit}U56}yMP0V}IECbuFg##RY zQlqJ!eI&k^%0guc31h9mG;LShd~XfY=T1012jM(wDvOz(xQ^-w4Djhuu&{ zu5lmny&UXZ-f$g2+pTbbD!D3o&@4gMG&Ld|ZwgxgxN`pDA1^pEozC>V%#(>~ga@Et z5AXho06!P=du;`Fog&q?Z?8KYVn{nlbRmO(Z%O+$lzZ93JGWjXO;*q$GHev1+$)Eq zlD)7Th+DsxkPgw{FR5&3?%P7+CrS61RG1u%^4q10wZ;VW7z5TGXjr`Cyde`P5z>|2 z3WQSw2mk@7ru2E#1)&E{Q!txX3#@E7ulFbv{cjnm!8^_rZw{~oRvA<-Igj^6qL~H& z$?tl3%m#3X#*42*Nn2XIW{(I+rJ(4V#!b*`N(lyXc8P3z z6%$WM62Obe7zx5TpyZbl(aSwlU=gw29Tb=~pcC-?$beba7~Lxxy7$@&5Xgb>kIdWt zr%!G>Kl18dT{!=7<=bA-F%f?0LY?L`Jo!z3yk_Dmz`2j(k5`LOH$Oo+E%>_Fm_v-; zRQ~#VczFtCd#}Rl_fOC2cW2&~=gT2Kz4HJr98*7x=b=+zXmvR^!UrN#4vyV>6qcZD z;Ku%y2a(T|#KlL!JSSZsL@aHUt!mp+=4NMjT~%IXH^(a@DB3>ws5Q+XadCx~m)O>~*NLYFjWeJ1 zDlhU5_CkM~j&)>1`kM2x_Fm>vN5>rLzYqPGGgMxUFn zoPi5Bsl7^+`DJx8flnH59%}ERU>JR&2DVK;@80V`9@HznBe?hQtZ$$&$1v!N22*d} z#C6`^zR&NS-VT%P4l(5B9;%6V^PQe!?_X^Y1AWMPmG_>hjVn$s38t=B&X#kc=PI?N zeiBo{N5y(M?={_R5Hoa^J{;Q3IzH8p4}+{-&f@hqP>fp1 z*tqq(dCcH>(A9^;I`>l8SI%as?D2V*XGo#QW0Ys$X;-^*gC)z{Dm=r6CN~ydr}JIz zz{)0tpH&fDYLYccPZ)nuNa&P@88P0ik z!=@T>zjM8GU+O)R3-9Kp^4r>dKk;N)w{1}}x9|6#qW78t<50Yqlm83LN8|Kmg*Rk& zbGH!u1t{(p;AoY6Qzch3r|hL?%p@Yz|KOC(U#q${*JpYX-3S#pXPPkK1&x_GB2S_ zJlT>=l)noTR8#wk%6%sMEgv=~(j3GB?%DbB%+3^Ga&4nFqF^s3L=@A!cJMjq0jwa_ zGqB3Dt7;jh;d4x_3d>^8TmDh%TxmHh;Z%Hb^RK=+WMy3=C%d3&Jpb>!um3Jv>C}`J z)FxR-pM00Go%6Md(Z{2~+)eVIdq8HZipRAw8N!}=WjF~|RTsIde;A1&}gIJk^J+9#Yi{15U^?~@TI`s;BpKyapco~ zNZ-E58yxxVLJ!U6@AHRjUV6yp5OI7o^48U0YsBnz)u%ELO8&!!9Xoxtrm2yNqCRDl z9F~&#Q8eXgE%_(9L*m&~++R;Q%h@&(unU4FVxgauIn=p>nMQ|rQpA{nOv8w^8k(8o z=S28A`Jh$U;@0vi`c=;w2B`#b-Y4{$A>}}vyg>Lo8LMlC7ig~CkGib#&%I8WbV?er z;<-ECG-p@ku-I#=@z|5!t~mc!Un4i7G4OQ6n+V!J@d|eil2`S(NF3knhv*_~oZMjh zhq#dwNxhsXg}ND`jRV434RTcr3M3y};ZN z11|xOR#<V)i+=r?Gs}>?@TI0D64x; zcaQI&@7Sj`Ke*{&6^S2#LNxw_WGDXG&ppjZpWf`Jh$#ml)103H)_A!=*MrNS^!e8& z`PTuEn({u*l9#O{TFOMljq+PDSGFK<8Bem<_Y+9H<(n1y&8KqO%O$;Tv^B%mh#fn&?c3(3u zgax&hV^3Z`1-t_$i{gS8k)<)b^~L6}5pEd`h!t|ZHWp^gl}ip>w2xv-Cfjz~3FYV8epu&Cdo)1JiA~wa~4V}Trghr%a0_Q#~o*~H$u<*Mno#=7u!uJh&@e}N6H(Ba{Z zMy6K(%FJqRXh6#Yu#sOt{b?D>ROnCj{@}ZWT7EvYTP5wfiv*RCW z>b-V40_eBTx6$eq$zmQY20sLS*4`M=FP-ixQ}WRA#e?zqo(X@Q4DtN^n1kBZ>Ev}GAo*n-|0DbW6An~vXSb}|(%1Y+wuu)VI*L|;m#e2l<*Or$+xpKf3tMt->q zy}=;ew=bl(`9Re?p9t13hvffOHv(U0{sU_RSNRppWjx5UBQUC|srj8C5%|I}o1{Oa z?EU-CPrM+D4sFbHxV=oZ)i#PpPr=yQykL-NVw|&yl9XMe5c9(p1d5Wf$*W9J zsHRPcOAuGMI?`&K1_b`8-qBJjV_RvKG^u1i?9!Afjwt2rCm2TcWm}!(cl?)Y%z6KC zBIHG}kb8d0h&o}i%ir}FqL3n%Ty|ftl}X4*-c$Mh#F;0h-sE1jPF-$?&dc6z(G1OBk&3;HG(t#?6x(4k%RN{rc?UXy&{?~Yo!YB?#3A({po4gQj5 zx2HR5E;Sy_lWVS2SSn)jElsYjm!?aH<{1nlUISI}Ol^jZsYS3HWoAx!?l}2%vzEO& z5U;m4*R$q3UO#$qyuTxGWQDat_spK zQwmLP(YWQT7Qs{da(*u8MK1PC6a$y%^$4vAGpqaai`+(RV!pZRg{6SPu2~K$_hk^8 zH~B;~cC2PRUV-G5CJ)AD$(g%Gti!o;{HHV5+jQ8znnk8(2Zh zTM+i!!wfRXU5_eC+0)Yq`O&+s?!9&xdSYq|E~+R4RAApc9w1z~KLfBX-KTUVG zh&$4ayXNLU)IH8 zCxkv7epd{SKL3UJ)1X~G|Jvc@05otF^w{m~j$y6{s^6O%t5&49Vw?zVH5FoC;w8mZ z78Sm`^nlsuxE>V;Eqs`=LNxyz|K0<`8|AkalM_8&UO4E0XFJ*r<)_!zyLQ0h`q8)V zzw_<{x(H+eIlPL@Kq|34d#ECo2)5eKeTh|%fBywYjXM~Oc%NT}#Lm?6@7qM0se0s^ zMuhiO#1F5Mze#@qxMUU`zx$bq>o}rR7fGp`N^V;aE7_{>Ns- z^xxah;TL{3zAfEQCc>`qm>MY7BpHEuX^l9Kf!@>O%CRZJt)7ti%9 zeqJ)7QtlzjDaQ_wfF+YPt@}c`PiPJc#jfqCel@HbfXn_Z?shA%hjo)5R{T5giY|X6 z?eW{n*QoW`H&;8|Lotp%Usi1pc*VYy3a~~6f@1haA#`J2( z6}z6T=C2Un@%-r)l<;o<2zO=UQ{i~=JX&WSq}QC~_xG!`NF@cB73^_^W3+y7g60KW zwt{|!c7SqU{Vf`)lW%P>wf~pkIfg!}R%mGFHsoM$f)PSbp_6s(y{kTHyd4#*y4#5D zFHN(@+a@eRqE;aC-$P2hA~RUS(B(cxa7Z{ zQTX}2HVu~3w$nXDuvW#hw)#C(*g@$=dF6=M7hjb)*$Zg~B?J^?qP+s(j>T31|Fd7$LOEO*z*ra$~Ckef@8 zrLGAhDhxOwp+jbYwmj1}hmGcW#tx~u{0mXozU^CP8=%VmNjNNHHi{9-&O}l}dKD-$ zyx?n5!MI9x`+;Yy=qoK!n@KR&chm_{t3#aWT{f$rT z_@i$5`L){)B^7Tr%a@RadE;Yd+R_@+fcTx!y;OK&E$9kX$j<~-=v&TA(r18w zddnVz8_nSIE5pzIN&R4%p_~D%sO{KwHqhk-$=A$00pi|^$-Xv5hIjXE*l+8|$=pDq znVmE~spsHhX*~qj?2u^LcTAOGmaLKD;?w`0GlCZIq%L2DyI}cLk%3%ch$i0@pcq1D zI}Zs`NjvHXy{{rqYAgE2p`K{e0+BtK*6hK~h;rAKP~o6`6qd^9-~sHf)f#=jkbT#9 z=_*^B2dbi;CY4+XRfz?C?J6sU6%E)Bz2p%4DVX%?Y-&#WCGJa~B`!CL#w%FZKzYvK zexf*Lw0l2+h}un0!4@mGD1BDv0F=l{l9=?j##c3Tj1-OE7)4V5*3O%pK6))L0w zZ%J8WArg$a2@2gU8v`7LpAkwj0A6yyYHu3%`J7_ct`f{Vb=sk4NUy#3_C8)@&zX0i z<9iT24nw8XH!QO*OQ~g~5*y>`GLdq2;!P8rrmdK^RtFt>N(C6(1PdP0zUSo# zp3j!HET2hF9fbHIcDNhgfAQj!ylDNG(yU(NBId~K*q;0~xG!z$Ib7UgcKDZ5Q^5#df_pYc#pj*cvkHYZ`6mzRAe z0iw}T%J_G-ctX718~Xninxq3xy}HHi3AsKKByRA9y*rh$H6*Rkf94Ur4KH@~+<6|k zS6*qXA*S}xLOA6-3u7RWE5(G`%_7O~lrkWONT-2f;Fpq;Q8<@J1HEtOAV1hGWzvTq zE4`h6?Cs)iRlIDl+S_*DA_kC9pdz|nfPqGP*z{gtOuGy@M-68Idw-opZ4BduB&yXL zQ`(FxLv4a|tRhJr((V$Ugv+X0UFjaKx+0h(9N$5QBK5!|SzS)2C8KNo4tc#6o7Z>Z7G;wZBD8X16Ob-g+p=4X5-9QsphOhFirGZ> z(jet6SJW1QP`9|9z5g=rfiL$AB_ddNY~N|hu1Ez!7ii5)p(Ou_iTa4O&VQc$kH=L3 z)6nC^*rEGl-(hU3G14xdL~LB36&WZMwijJn*y}}gvf;xpg5|LB<+1Mcta_mb+p)FJ zMcA**YfT65H{w8h8-T1C%ZOGeQ`JiAf3Gyh zsJ(oUn+1X^-w~R@)h>ArAFLl0myX=-ANqV_;Y;j^JB+ERB+uz_)b|MKAE+fArP`+~V^)O!-wBdGrt1>g0i=D(m@F^i<%)==* z+lfcP=?Cingge*SfZlHJLcKYZIquP|X`=#Vyh3;smQQZ>B-(~#`)+Tc1qi8Dw zZa-L3yw#uE!)H={!xx+gP-_te!-6cX^cmwt|NOOvaAV6^`rY=*UlsN)*3+dAO#L$B z%N2~9HtHfgZQ*OT;=R}{VLm5g#y+D5Cpt>TP5a$*4d02>2>{<Ki_$KA%hB#Ft);`R1x-183!$OG9kgQKl ze>U&g7nim(A-TPvWRUb*mLkgwN40bSg~HQ_e+gG{7~fJEW*Y~!3M=BIT_xOSa4#D4 zqchZrjb06gB5%Ozef;j-c<8==7$gamT_P4mbEQb1w4*48uCxk<5OsAN0Y@<2HAe8+C2zpc%w4w-e<=-zuWhHdD9P06Wp=H zj6!~2|H?_hIsOn;hU1Qd#HPAls)mejS#=7YB@Fm?9SK|KY~Gvt`+?2w`Q6vBpkt)- zZj8nZq75%0s^Fs&Z5P`zu)!Z+Ldl*NI(WvQv=TAn_c%24c%IhzHNT)drgqM)@{Xm| z65OLy29Hc7IY&2^Bug44J2XTlk<7>APtPvX-AC>0G5aknhLMDpqdX`x5$)<7vo?~S zK!Ysa^YN&%%XN!nBn#%~1Vs~(uqIy`gMTs2V0i09qcTDm)VO7m9V`M1w%_|EhEX0g(tbu$K?vrSH)* zegL{`@(AOQW)`h>^70vBOP(U|{W4zNo+X^IF(hjSn-7unwZn)sfgQJ62bo?i!eu`mSwWgiC?_lBp zZ4}?PTZrJ9LffLeIbCEQDYDbcUuD=AgFgGI)5rxeT zWh6~$YQY$Xb+>rUXUMP-8OIyyz}s_lc(Z}FA~sFwU?x3GS)?l8N@4<6<*;(JF7248 zVB5n4==9=FJZDF(Z`xTlbouv{D~S^jc$EQszE&V}>6_R~%0wf~38`r`Npc@;tOkBT z{h+LZ+2~9Lv5Hg8iEO2KU_Gl_-m4YC6g2wx7DyO6JRZe^EXmwOEP9RB#c?M-sHG6> zN}1#O?9w-gE;U2;(2HB0*XNxy!bZbDD<}{h_=LQR2UVU~O79=~OoX5h$f*j_5(z<83DBGb ze^(=P?qj3^=l51qI<0OXfA>D(78-w#iyV|4L<+=2tW%a+K}ibYs08LdN)Z+w|cFr-mHKAKw~*s~{Dh zK*XprAamH?f&_y{&%%4j;NttzKK&!Z-NhVUl;?QIN0Qzi8?xRmJ2E$3DIe0A8bk}C zI*$&Fb0dn>05Itv)sXUW+~EI=RHEMV(Fe-Ff8&l_C$gB|$lu;$ZgbM6mgxc=u<9(O z7J-K-Djie!F_9`8fg`9Hd7O18CkYCcA50Qrw0_gdA5+<$WL*rpanAWuA*-nVhNW+R zxRUH_F@-c7Txh1pBy<87UZ0PJNu+oppAu?D=BNWnYsV@3p|vkm8OAPNQUbZl;G(on z0L#coI<{T*#^E=Y{Jx#E^{dc49ccoQt(BG^hUf{sAVUya;3Dnpa$kZTL)laWLiaF}Fjlms9jqD+AC;hV+-a3-H@`fb4 z1Li9@n)xG8FY?tYSyZkiYx?&<(195#&bD9-J9YM;iO~&N*KG{N8t1leC&SQ*2&+(!MHSpzV2!1$gP_Sv7I7Ng}YBtayL?=N$`O32}%hTgIPp0zf z!7Eo6f>*Q?#)%w(jO#^MXk|xZ`d?z=IUX@u?2rM&>Gim3#)%CZddP(~s8wpmJ|DIWpsB>u25^vh4 zIdMT}!bi%kD*|5iJBr~l;}&cu!x~jZr3a9X8NUc z*NdM>6(vjht+bsni4t|M%%qpl1b*N_5#S)W1c^9l2zW%9y~Y53r{rNU+lgFnTxp+9 z6x{B_JKYW-g!UfcEK4;8hZBP!Ba6^D~6k(a=KIs$Xz;>=B?O78md#Mt}zx+~DB_XFE(F$1nH}#tjN$;Zvf;y6JxMrZXp@Yse*O!oU z6b5}|J_Ss3_4$C0k`stB!4NZ30hFVr2)2TPoiUV8Bzr{GPI|#_IdI_*9!6+H=U~yY z?`(Qb(t;$VXW!y%3tbN5P-=aK~l_%-3#F3e0 zD&Qa37DSx&BCPPjG_R)mYK^e8hA!uYh7jp$>dKi(I9NxZpd3I*E1Hn^o=7C(IkP!Z z{gC383->Q$(jV%9*LL)U&0CVqN*e0ifvHU`Ci<8jYkdT7I04Zh#anKgG801*69@)V z#mL|EB3W+Y9Ep4^g{Y)~$v-je^P6ghJFQX-J~F}S$&&(Zn0iE;-VH44d0ABe**{Yl zHoPsr`;DS}{V5|zo03K^C>?~ZQIIYa7^=~M+ckb*nl&3n(e+1 zY^0p{392^>Bpmmm^r#&#m^G32qKSwTiJHauw{o?DU!HF(o!^Z$f9eMZ|Ik1Zj58l( zEH2al2M$7g7KfH-&NNVz=EL3t=f|z!t%#g`JqjKLtme`QR%W@CoJWWAq)C~eXY7E7 z0b*0=_f2><&SqG`L1^aePibc~F}<+&+I0?2ATs~KabjW5 z{_Hn6&+@igNoN}8?+M=XUTR=mt@w?mpVv^$k*;Vs+j-r7C+p&iRv~vr)hi%A`n)Q| z<1Zk|lO)9o_&!B;32ne>)s{(37K)%si}~N#z$0kdq6fJkNE0jMuHYIWeH0S+Hwt3r2?KA3ZRt zCRk)uNA5EiHg8LVn=fUWi20cu9FMZAxa~vf5l2I_M7#qU|lgRnThIT*Ij0#C%KMIf zR<#kJn*pdnNU6R4Op#@>4iboI^vYow1@sQP9}UF<1f#~8F6gNxrbhFWb_a3&T&N$% zG~vu_VZ90p)cWxoR7~F&THMzc<-a~T_2V<#TXgJ13HfnGHSY7yi|qEGM3Hq1aQZ= zeOLT06fWhC^tz0DQnvU8S{YDx6qvzJPg-g>ps0`v zXRt(7l9KB zK*2&q{qsuABol#y6GDBV8!fl3`8v{}hn!eJ50#G@vRToN@hAI{s-k=My~>LR~_n(6Mn> zg%mcGfBS8}RYO>1UeuHSczp_^%9UY5N))@QanU!#cw|$3$WyCHh`(=bIPANtO^J6Q zVm7waC)?yh!(d=2LR*?N>m=>jW#rD07hfZA9mhCyfZy@4CxQmh&E*TrW3{a0}@Pz0@fL+a1ZKumL^55T7X_qHb2iyt8}c%VyTGNteFSfDjVB zG!?dzb&^nSz!t==pa1LT&;SE!c&8Zhqwr?}rCn#Hf9AqRN8{!zEW46{UT8g@w(rO^ z5?d5PSK1E%Jmj1RF|?-Zs)~C*!96F~)nAeN&q0Ty#f3)tOwLR%d+GD&V*pRyEuu{G zV2!R+ji%wMdz*J$F)(fd8R3h?8D64`>vTHr%vpSFOpl#Slkc*$YFArGa9_Zw1gTd8 z;Moc}u34%(RN84u2WLW_Q|NT7k@y2PfR}*#`TVm}6&X8F0o-%%(k-~Cr_F?vP!_jQr0U&I_suwNac4F;tM&oJ||2*(aQ zK&XDB8Zn&rpzwKNa9##AZIBM1{Wb|-v!r2KWl9nJG(Ayq;o&~k@I+xZ#jEZvzJ{rlLIw zJ321!9l&FmCKdywrDMm@~o)7Lk z!R0HqnaANSHbA@gkvfN=x&oFvk+l?&bGpL~20G?{@0s-VUF+K7b40D(O|W zyeVKrCk}KEvL_$e$z>vibEJ)-ev`77>2KRH-S6xc@+^Gy@30aJCXti2RkAO;1}C}cN_9BGqw;NoR}bo8l*aZI>@-aF(pr^2QyGO z6h!zFI%e0Csr*?JN`=tz3UmOoVd!64X1FZ-iHW#)H~0~bmBvk(IyF*HdMOKo&>sI_ zW?#sbKBe_-h>v>Qli$A{afzf3hcbk&yAvf*^r}UgN^|v@@}z1S!REIqJDjEX+sP-( z%A58_lSCXwBc$+o+~et+qr*mD%EMULnv{qqjigIsxXf>XQC3o2+~~YT{ra>svxkxA zjXQ}y4PRz;RZM?=E9xnt(@2^nYQ~F40?Y8|Bd~~Ipqo#)>TX#}V}*l7#`~#Zv=mXr z)ur4+EJ>Ja1(dqUV*PGtx=igT9lNOzF504qKKFn9Oe#<&+axQt)7_*_p+}F|28jAs z1P@BC5yCLM;7TB=q+GNfn=Vgblf9I2csim``sfplt8hfYpze?hjU`r=LqUo14Bt+I znG(P%=2<4fK@WAkMOkJpRigDo`tQCTA#Lz=y8-2LT6 z+8>b)+-GV#Cvax67=&C;M9GJi(-3BcGhx^`U?X>`;#dBy4naC{A1}wGr8V`TJxD>w z*Oaqg=bK>Uw`@nwSF;uqN(dnZ;(VbA56N^!C|5@9dm$Al{@tfy5atk^o?@4NIwS|a>5_z3PRkGX~I~-Y<<;bgz6xP-WXFT(#a2C zq0S7`c>nfRP}>)4s~S2wE1I6IuqKMA8{IgPlLILwDej=IzGtp*RZyaaoL&R289wIt zo%%bVSGul}>hHe)?wRtZmQ1eiW|OX^B6x5zQddF_Y72EMG@|y|Po!%(SmAR5J9I3i z$jmnMTZZx#AHgeS#bXPzt6$7{KO;BkQILzq{8#=4Q8dDSzsxle6_#NYUP9ZS^0%~_ z$FG5Hj>?$ofRRTNG2Cl^!Yt3+OFPR2~dAW2SVho zi(u;bN@?{`7EjM0g89p+Ena6e;9J>&*9Ep7Fr zzVqo7w$*~5nq=Bf0SwlBM4Jq;Qxj~1h{73lA*k=&DI8f4qT|#Tgo$i#=_4q#qooDd zt;+}PO*4jQo_4xa7j+vCMt~!7L)L7S%$ljgVL1f5b!_!D+C;ijKo5$p!ZFC#C7DPO z<_1b$)I-D~154d5_Q)kUs^g^?TjRnnU&3Xv=iQY@2921!qt#TLK?OT}qS z7=g)AS-`K=oUsL*NO^^JPW85$_}V`Xr{#2IS?ff`)lGItQc1Ebco1H3DU4)fT$17< zaW|9ju5!jpNJ;+(04YG$znhj%i3WWML|p)D!U2{;UQ9IBqj8)e=J~r8k|-A#6J`L8 zoPi#L2u=Bz$ruXUO>{Hab$$$}tONlQT(2Og`4CF@n93of#uyqp3aps2gf=2rW3a-u z#39y}Oa!>@(kq&xz;M(;BqgD#KFJyz@}eUh1X{{y4s)Dug%D}a!tWH&Y0GG7^+RgT z!(5_7WeafY?jAz61SMnXDlDL)jB>D2=nqWhi_{Mb8Tgm$L$o4!Q_+mWj>=;c-eNi zmNR&|RA7E(iqB;Vtmh7g@vO=tb2I$6ha|pxpqp3XBW$2U<=cPV$S3a&@YZ9OOZUZl z*b_%5dE*aWC*85+9_HJ=mYYY~_<^Rw+i7(TD;m(S<&~*sb$O#t@?~su zY}P6b1;8c}l075Ie5y;5Elm=RCdmg{d3(4d6*s4)W1&`_8C@*}z+|6d%Thp->j!Mb z$qK0?2W4ZjBKssmb|k-)&H1>Ji|}UEk<3Do7a~6HgoIqDr(`?Z&gUlEcz$@Jl-I_2 z`Sw+OZtw-tV;$2{Vdtx)9fcg<4uehge@xzyu4A*0CnYw$T-v^F7u%73yEL%Wou%u!Z*VPlCI@-M7~-MkDYo{=43CeN`QBI~A5@mJ zy$?hg;^Ryc+gLF*#Db}%JUw&?AJ=ABVyeP&wqRVIW4TopcjN}?;$Fd5^@aGhoI7(1}F50#ycf+6Nh%t(A$B81DYO!4bhB+)8Vl=lx|nh!{J z=&_7b$XLS68G;?nilTBTD|gIJEU$Jd>E@(V2s6?NFQ#U$vD5Lnf=A@<}_E&+)vJX4l-x zSs@@;e|LesaBGO&yz(xlHBRwRc_qIO`VMHLwt1+7Z<#G~ zv+YqnAPuqNbduG_8~I%KC{OKc=Jv9mGqb3&ygbFF@nOz)2Y6tW>7L6*Ul+H>Qrv>z zPV@r)?$^Keq>TqAPBBS)$psh6O>qtCC@>K#B9;gsI|s;S#SI4)LJWzlf=nWY0WFJ> z8IDLo;KFzx)LS>PBP}DM_tpE+a-)h%j+xjK73jHM!m54;El&#E14(Efkl6Y|60CbI zvF8entzN>=^4q8=mQB{Vl;O6vGL{}y(KywH+g1l~ZRLe%nB0Z_!Y{>(@>jD5H*=KP zF=$Ex4>cCy4E5rj2fA@SD~K;Honk$icB~q65ZB^(th0n02HuNZ>py`~sTsW3En1>G zS!!k(?tI@)$g^pzyj_8Oz%R1bV!%UX8BG^= zLoemAVdfBw@|)NXlT2jtH{tDjEJW>P_|^Gb^x4PQ<-6+9f~fe(pB`onA>dVCOJSIe%}B~o zq0a0pW{&mq>7#voHa#bq5>r&x3fYG_9WaOtP_>M8V7_rm0h>09DGdloN5Jb>A){n~C+DDTj)TqY1v|Dwp2XhbI{15R))*T?r5&P>RbU!n2vz`39))JNLHFq- zhcDFL2t?~N%hh*bZd!q_XTJz8?O?OM24Jj+WuXG{DTb*AjnxfAQAkx_u99H&SOPld z7@?dDgj%0xqNxOHG|Cj!2dCbKRi>OCpccVmWw2}=7;gs)>)`o3xK;fmLfUJ&n% z(tCM`5QnIg-~=o%1R?Z&u$(#wV=dqxa2zczL{^r>y1hb}D@yFp^pvwgE}~HH2u#Va z4#}8`GPGDxv0-#49zAal%B9Pg^mv=7kKG2XWeVkh!02RNh@m19%P(d1bEASCi@{!Y z5ZO{0Q+6xP8<~Z9(Gxh7G7)^}b!ZxoV&siKLcaNOw(WSr+50o%k(Zj{)x+=NyHbxJ9eYTu>sgM0)+J)7?lxSz>oPv+&xpBY2k}Suzn$$i z`o#W`i5$TL~mK%dAd; z2wr3|<5w!eg*4((hOHr8v}>!_+B<@{<^1hJj;zNucek*|?Ay`VyctuMTgZ*|Lp&5m zsbyR=IG5v6bsMwB>v8jvym%E?@yf#&vu|v^vJ3jce_wk)u{#(fL8S$E%Udta_ zez!nHVIwx1fViz9wuDRQUk!HP3ZU`Z4d|$(Fm?5? z$ZoDj{k|rwIJS#Tx8}hUU1;nPDDIqvmCB)YRRYD{4J^y{ik7wjirS?Z-ebav?ZvVB z2`tYjXg_!rX2N^L;|;w`8@m=SDkU)*zgaxq0a(*pm?CXP)pj4d<=QDR zeVz~48bb5>8JI>I)4EU8KeUedvsny9GeGAWpwKN4ng#R%m3<0d*FDUZWVG*k1)svj zSRKeQU(ZX#p;wLbm|SK|)S(cGBNN#KEx~y{0m%%2X)$o3Gsv@Wnk1;rF(i~IG@U^t z8B!B-C>)+Zk8Yx5^%L_5GL}PCrol~0&zZ1U*>XgM*(@eOia_-%h&ctYvL8jEqbLT1 zE;VGqd<{%0Cq7m&3Mp;s0#`n)LVZ7a1luSBVX91NVYW;{9@`-7Rm?Y@67~8pCJexAZGgWmfL08F6;+Yt^?Wjuca|vw zU@biu>&u~SpUsx8-Gk9pAz=iAh-GB#u@b0DJc>X^9h?VMh{!nP)eLf2LsS^T8C}VW zxh%_OA|lc_tiyB*-nZ}W@ipjxi&^5UR!QeR3jg4$fSqWuGXQK@Y^a}zE z0}_%)1XDI!n2K{aqY@~h%?*K!%;2jB3`?Lm$DmaJr^yg0N+-@LY^qL(L=nu609jdx z@EB*525=~JOZD%LU^$JW*kFr5*kR_N0z)!{Br6Oh20CDrI>D$i$1V%X=26W&W4S8H z95FB)^Jq|Xz)wIB(cI|-tgNft%|sHc9H?>`7|E=}!4U%IVX8YI2}H192r{K~4H=fi z!894n&eNlXqnTiK9VAL^$h|Pd3~W0EM=1%%h(RbaL#F{zEI?R~Lxh*w;9X@%15Atz z1w?r*gE9-zp6f%oC4-^42B?w`>!dP9>I_WvoACK{LHwIoWdg};E7Zw2`qVw5!kU>` zKLo!Ph2je#C-)<{H;heV_2^w)!9c`@_Lv1xEDQhUX~qL3bW;np%@yF!Qzl+nYE3gx0QT5=l^i%c=oF-2c}n5B!9nwb;%rGDtyHLUY?+ILoB z*Q+B8lTB#bzZ~HU9>!5shV$?WX6pi>F29JeA`0vX%S0$X-E1M*fmdGdd&S#Y^56XK zNZ<><{*Cl`Fk6+&lH&Bk;l;dgk^-U}qQZ0&DNfh}>Yy>hd2ZBrYM1ymTK0;*ni zWLBk4I3|QHVAwWfk#XX891@S+H6q;^*LN!&nV(Bmy-#G0J>p1}W60&}MdpEnSZZ}+ z@K#0ojV(<`$quy+}Z9qVvxWCs21-AHDAA`$ozrn+p* z-I)=A<|u1U{3#N}-ynZv8!pM8k8R73h~AJPR?Vuw(e3DeVG4Ep{k-$eABdSXJ*=)H zh{q3@;)?Y3jK6RX`g9wS11Utu_dvbK6q6}1-!D30H0B`QV2EjZ6FYKC0XLW&``@`8 z{lDr&Y_J>Ijypxi1|KW5`^E6%dAwqZW8e)s#vcyjUyrKnvBE6ArK}U{D)q=L+m8I^ zI;_7h!7OJ6*7VE8P{-q#Xxh#;{I(nNx)$tMRl&yW5}bc$6jR;51Zx<_rrmGH|HL21 zMBQOrVO)Y~F(&fK0rtiRKZqMIyBCqDj;kJ9kHhQlgJlQMp*KO+#*uF|U{2Z4^&)2K zFGZA@u*`8B_Gh5P!-&l^A`uV5-Zlq=G2FLj=b1AeuDf!h%qw}60|80{!cYR3v<-+x zKu<4$HeQC-F#;ZnKyC_RdioevWEr!H^_USsF&96ACHqG(a#0Fq&_v602yMTNVV^!M zhPPy}skDS0Jz$7|71J!<(1JJZH_@MN!RmoqY<^M#ph*B@;?%3~w7$Fx*ha zk;Xdo9rU5CK8t0N#HO7BbFk`!YzPcv&Bz*d|1}nd^+}v}u#6>7F2lad zdqw}1I#&N|DGQ<%JFnP^N?8&w7`~pZo=M{FD{qAQL=ufV>LInPM0!O%W_BJxVls`U zwKkquRY71nf(;`PSW8x5Of`i(y_@;0NjS~RpqD~uKk%f`CZp`=c?>%nb7EPdoCTf1_E?QN-d`ZJ9P zZ*67q*S$k(y`oE2_EZE{``D33@3trJ{Dy8HJ?y~pOA$CQlqB=X^+;4E?SZB55>CgT z0V^71G%;WbHr7BwnG(5BumUPFu#o}V=*NmnM-HJ}a;ABuZ6FF3-Z6?l_5nH99G-biDfF;Eo(nyKfBqytfEejsQOiG1uq=J^1 z4HaQb@(?OZ3uvAmhN`D9bN)C~izEI>9F@yWQB3$4KOA5@n?!zc=f65)5T2NgM_iI>wpm=NRsE$@Gkq8U)i%9l1 zxFv&WVMqu-t_V2Hf*uK@etkWzOme$T0;|kge7rA*k#Y&Mvxd9vR2&pppgAhY-q81!!BUm;Ip>2ae0HV+?!1goYECmF0mAM;&Dma{1SrEev+>{X8PZhpJ zG1ZlYe`^#D=cu$W(clPHKglp>DVS6l?3@E;$dE3}2pf4O-PZthx+E%F#v#N?#xf4H zNC}n6k`S#WwyY3ENgowsYi7WV^Vp_GbKn~ei|y?)FcQFKJImsoWwF)gXN~eK)WM*b zTi(bfH^qQQRJ3nXP`S#+^x-Ci4qME*1SoATi^wmDWUR1U<4z&QnF)1+K&lKRbg1z# z&P$2q7q5-H?&|jZyKfm+fAOQ=I3Km$jyXXe8)sFO@*}#CnjI*r0;3?ard1GgK{(|p z==BjtYh=7JO0?DpxWmAS`{pR%Iz4wAf~rI>USeN;asAwNzd8{4@$G}!|4jEhYWWNQ zsMPJ>CCpuO&V6QE*QY^=ZN;*= zPxFTTEo@(tj5aJmrSW_=v-t^e&AofUhjSQxQ;N;DFGKTJC!puEg1vnfiC`lWx7(PG z06Si@RQOxxu>Qw6wxx2RxNp-qv>t=4eoz+&FFDHW3zmrTw_0Gg%4qt#!+7NAC@#9A z2^|MsjN4=TF>^zjZMjXsn*Eb_sICKjm5NxAm}ci$%ds^%Amn0@t(d(8p+GMNwRPZa zIJ2CbrVvhK&{ya}r!ZIoLzt23h&2a+493D7 zVJnWDqGIKf4x8)J#AG;twdE2fBNfOUhcI#fby)Uf92*)3arp8caoFiZ=;!s!#LYsy zlEI8RSaoYVOUO&H>jg>p4i2K*FtMYf0$rSk_SrFnlmT>yCG08bP)n;2@z3Dyru}H! zu^dir0#nTq)Qzo1x&AjIJP=379|db0WX6n&u?dIH(xixAEGfVk z(QxHV1;-i-I1*^Zi|@3tsma7IRvt#6RK%+AMks{{MznDXlZq?yvuvhgJARs0&~PY( z%i?o5x*~*K+6HVIo@HUxCx%~`5#d6Gop+DIdfQTB|K^R%I^2yqYYxp9O`vx?j9K3b z)?rP{twz?hx0Di6%)*6G=QPnCS@NkV4iRaao0{ zBNgy7QPjZ90uZ7QFcD-)e!wD92L!1QSQc1>eii{TB*{P}`6N9NtkyTUnp71qxelyo z0l^}etO8{}VCTS88Qdp>%{I9$2w1oP=)NkET_(v324T?sP@#feZP7w(Yl;GtLlAUe z3l7Gpz{sphsgR_C>XhHUUkC5G0>LK^tPyOJE`ZCUSr;2#KzN zdbojFxRk&o9gL(nm=9c)z{@5qRA7>vhU@^E1jc<}#95{2qpG^xYelx;UlYKE*CmP{ zXmadz(`7zWu~AkeF8gH5Co>ceRJ2F#p4NUbIElSrsQ8kQX&fuITk~Tf4_nZ)C6-*8 zWV76I7(sRU(zN@1;m|!22{;DWjS!*&L1mNjBtU|QW<7*ThSFTMOq2?3Vg_l;GciRE zvj9d06py?2%%m9zYe)#z!Dw6%9&ig_1j$N}j1#rYq5IBK!&C`SCjfsvkV}Gzd{t&d zYjYqb7|L`)M_r>1W$OAc1{S9X(JHX=Bw&pKQZtz4hamR6B-_F+*~LUuiC?!0uWb(5 z%MBsx-7&Pc2JKY?GbR0JecFF-yG{LpHJEn%t5l!CgUli&^-(ZdFB+*5Myu z08=WMoO6k)260Qg=f$Rq%evwzW24E!m6y#} z*0o#EUdY*u-h%OmTM*i^M-*(%mdzO$+giq4VimGYV+d!K;>u1xD{Q)7?ELL=aeix= zg=0f_G<&5OiRW4U(g($>fA|u1mo8)6_po^B@O7+v^Q$q)Q^{#mTQ5X>q2~PKWprs60)Ac?wksrKY*o^5<+sxCEsV_ zDP(7|tlU~b$T}dXCf^?20A8L&M6IxpIV-fsnlKrdL~iX4_@*`?G24WprUY6_S*H6& zgzcL{z`qQm85J>>!%!uHy163IqGG5RM>INvJa^!j9IGnhh_vP~NWzMlC}s+sSU#P= z&`X0TMTXIEbP&$&ikMov8llxw%=h3*9DV-?MC*R6`G=K|(skI|2C*)*fpz)^uw%;| zqOvc7uKG^q+;Itv(00^q+=}4AEojblvSDWg{p>MucyA2NsY}3CClE$2+n62}1KD~v zRN6W%5L#kEUlxb9e+*Gsh&(GYBRGPISQ+)cRj5mc!6gf3%PjnZHcQ(rVtR8L)7A*q zPXjaY*F)c|u;OyTBGX9`H>R<#Z56A8Hn0o!^k6Cy7W+F^BD$-Kg&d1bZz{vCXmEPU zB0OG#f4G8Tx!*C04g9>ftWT^v-xsYE1)rLlDO;s!B*X3JuWJmwyrTojqoeko(JY(b zDpw)_q+$}9Qj*okDwbrFAZ&#>gE||%uOdIRyUZVlfeaK#2to@>h=odsGzL(AnP$JR zotZ1fOr_^YMe3V$FkNJrBFTc83MRo(u1a>hm5@F-@JCFkZndP%f^b;Ytu`YiWYP>0Br4|$IMFMpLDxBfh@pC|3RCo?z1K8 zj%k3Yvv6M zBuxf4WeA126~}JHCRJiN)wUXfu1llB1|Nh$N2pV^Cwx?0D}ky;=+G9NXiH=qc)Izn z$RDw*>HbOQh{jZd(8%EMw2xqe$rhN;sJ3Qdj_a9{J`VR+KuW+=NWe`SCXwqSL9|B# z2yzvs$xv}D7?K5B;!sDP2Co6$qa!;vvaevDRl_ zxFuq2lvR`-nf3qbuC(%-jD*8*P$*O8#fFXm99D+o=x_uT>eB&FMGY1NiJKw=!5j#e zT0ccI$JLw=Ze%A^oevHX?Wtg(;_@v>--)Vd-I`p|WOAtL7I z0Mg&9_dA39WOze6tX&4y;T%>yv=$85Uv;5UFY@sgorRRaLDyV7kQ#cDjsW zQ?j)B11pOkk0(O>i;wyLwuhk){bRt~04ZYvnGS@SH2(!JN_KDPmR5Dwqboaw?5;tK zv^9yuie?d>onu4gIhILJxbxB}7Ga>y)(f&znkvhBqdzBgh2e9OkKP-1Bcn?FW^dcnhmL42uTzCD4tjrft&!=Ojs-x&WZgSR)eb!l$&%|O#?{y znqZ79M-nj@$@`F*?n5rziP>DI7+!jeT|Rac%X=?E-?3vjxM3J+do|YWIuG@$CK0PY zh@rj~jHQOLc2=Jrg6yEiPf+FC zUoocbL02k*ax8+m!wkocM3GJ|LsMuR9lio|B>-(khd< zRf4XU5VVG%7LyQG7n77hVdUGP{XY&o4xveb@@5KR$`Hnu|vYphMqh;}i9zUe$V z${9q3hGQ+~p(2i;xlj^mbuG)QM-d8IaO@Rea}3U^9EwsGLp%m!qat$YZpe**FAdRi7)hrKbDs;CQHy92c}FRZz^R@x~1_{Rp%zsVM9=5 zq|mAdBZ&>tAIw*6xXa0lWDw*@k|Gx~UH&f<4uqw82Yvxi$YZ1fo+1~PCt=~L7FLBc z$-8ALm}P>|Axj2~EBqI6&e15jJ(BB3~G>7s`zAX<4h7-balHW0cJREIX9=Kp7i`pDzT(nq!E@N ztm^O3&)tL7)e0o33A%JqZ8t#`#WYqj9WDw4Dpe2E@qxJpjSkKvxNT6l1&PE#9mC~3 zxcZ)~3^k~T<=3nhFJJC6H<*ScgYyy?Od&W`jUm9Tpu(9_DZw1eiIJTJ-2vkNs$y!^1}VIsz>9<6)@WmK?glqM8}`4Lq-M7iL!gxgGIm;;(B;u zm{h`7R>3HXs~T_w@jqy5E&u@mVQFC04@N0KXtrC9Doh>Vlnx4jxvfPg8ba4e(}dCq z5ioJw;H9c~DiO87YB4#l&bo zGQAl#vpVw%j#{ZFl_L7kf)jd=Zh2b5eP%lbKP5WvK~K zc}bKRRvUtaB2eb&(#t~0bi%k&XU6aheESUOfxL&J^?T7z+nZmPo=n?k(_1P(FG zOx`a#T9&b5(*`y^@}THQ_@VbEFxIHRUr^xNbp&&5UGT>^mK+#_uX8=D^m-JhzJ*mx zV9K`{Ti0)4v-~$A+S@DYnwpt5l)|w<2S!(wv8MhY;=2TrVFk07^g`d!jR~KGlyXo^ zt4-)n&N0i;vBqkF^@_dI!QRhv7CLV)`*-rQzo)W-|@2WE-)%N!X(Sv`%S=B<3)8 zaSVYpXW9L#2$ie zpM+vMjlM~@R|}f905hF{)(S-Xfc))XeXjz#Gby&Z9Ao-5<4EncgeVvofb9geR;Xj| zhG9z>_g64%twd1W6493?8#^OLgJF%E`ySQznNRiehZ7!tu?ni*{t%)S*YEgGP; zfTh#b-7ON785@&fM8S#_=C;6W3MrQXB?#tEftP7B&jLIMZp)Bt+Bhlf*Z@YG5=EDV zaJbcLrvrwKKYEG!XQ_JL_1m4e>A*2;B_EkJBZ5ZAJ_VeUc$^8__3FrtrBJm2MKYn0 z*DG`g#a|`ARmu<&>FFqt$kVg9>vhtkl{kYUEO1c*qmV9@{*%HmdHtkoLL5Gd$P>qr zW^4d(3T5P)nRDR>Qkj35melmO)1eRPz_{>1R>??Va5T+L69|ho-s4KT5`^nflPWds zk;LGqFg{5R5V?<{4Ww-BR6p0@G$yWg6LaN!?W%&XLgJFtSxs?OjsKaMDinxrb1Ex8yoC!rc=+doEMbxaLosL4XFj&V2T4-a-irYVqu2n zgp5RxBNk&w##E%b;%0YD2=%cc>B&Ar^g85-`y5S?ppw{%?J#}3ERAM3?@OB))^!wO zGPD4PS|P)M#$ASDNNyxS2op|W4!%$UYhIQzU-8OzW6P5zY3Q3J->35$4roPiVZeX} zODe%}HFW6ktALm>HmO8Y4<^^sCUHhG-iQoM3xN(uH)U0Qrgl|^!8M*JLPR2{x(@<6 zgr7Wr4Z@*0WxMlBDD*QjSX~(mS4N}SMxy%cNrhkNG@ddTrJw|@5e8eP4(<%B$ib~5 z5R|}(A40lmq^cy`I{@Pxk|6n&A}ps2{N+x%pMg*SrU4CjEjr~CEwz9 zFDIT2*V`d7(@yzQxcLw7O7Pl zEK_Isi8y$w05e?>zGMT_{9*XyahT;ItSJpc{9+{f4q};@g3&=eI&3j>0O(%@%(Iy9)U%|cOzgG=XFrT6#iu2qh#^3%u-$4v^Ig_%!qN07pdWVOLM)L2((~VK!{0S8I^Ja+Wi4GDO<=jS+Iud z(3Pk|XCZ~H7nTs68f5i*mtf|?0%D;u<2~JMZli)a(`0&DgAq?c1OiO$AI0ocj;Wh0 zDDA*-qb(u_%VzUK1u^OPF)LDFu{QW;_Cry2fVHF$%3KE7_iAWYwg-}Gu+E;9qs2BP z)~&$m6%AObmtmD{%r*GYIBUVU<8l1Yfp6~I7w(!up%aoc(TBv8jp@Q>$gDw#^-S2Q zW=8Ii9I?42`(3Y=B^~H94&;K&q#_t^qnxnYu8!FjBcq_&l0|hz#OToDu0$N^R^_}! zO=>n(DPK+`Cs)$Vgv9)i6b9Lu^){t2I3opN`e_+u#X-vrYw^B93E8`Q@D1I>3>px1 zr7!9A!RjIFMhe{c0LhrS*Wr51v=OPY+hKtA-fB3Qyk9!eBuEq*wQX<`_S6`WAY6}& z(Sb|F$8?*tS-B@a9p2S$!EXBs&L9P3s1E7m*eC|`X#Q|4`|oKkkA5Q){E!tuNuyMH zwKawyA|4q6bYM$9*TZ)s5aj6#G7u;nOvXd?`rKxybjZ>MC~F;DE~lety~Pa3G(7((}oD3bo5I|kIlNs$HAzA0pH@59y!jvWXfYttbn!!cCoB?dz! z(wzl|y1z3CGCga0ew0z7x#PAVp=ac(Zo1FQ;VNuVhMgHjV1NTQ(=T!$??ux+*a4BZ*6Rrx`#;<^GssWXSn6iVCBf3(k#K0X=P=KszL+GjX) z*L0}LV^$kVxv4=nLPh3P78ze!#5|S^P@_0L}xhS(5vPf>sADr-*xc#`rlya6;Yu19ViY@LjBp#z>Yd-UKK*QsSXoIRj|=KmPNN?c-0uJZFOLs zYhfva;1lDJ>Hx!up}~r>y2(-2u_lZ|D^x`M6KFoDV|GMifr}mFoCFK|&V$lf0-qhh z%=l6aOVbDssi<#kLc@wQZvEW-XE1H?XP3K2gIoghOMa0xB!q_NP$y4dc1;-5dJ^@M z1&ljUY+Bt4F*c3;0|sItldTx0QD)5D70NM!Fe6HMxo`bo3oY- zAGlV8ko=G&VrEmwS#g~UuKFQa1|-XL4Q@G~fn3ahXEVaG(yTmJE)~npY=w4dMNLGS z;=cNZdc*=T#Oq_CK~)`TZjR5I1`0)k&5c?ZoHa14S@3PH!z((PvHEA*@bhi`;%?LL z7^!+G8i_)+N|2Za*)O{}VmjQ2=}rsR4bPLnoUFnovX&@OQGlB}ro6O7-mFipsv=i+ zXUG&nr`)RB3C`~wRt|WX7}1mycOWtH?_?;P`0nJnP+KPksYKp1r41|uqNdq-eKhmR zC{q&ODa5`^((IZFzb3ovcOg4q#L%bBSI}We2Phr9biBA*R`pLIz{ty`1JFHzT#aVe z)2<#!93F1e8scfV(hZeFH81(|S;8}V>c7v4GN9s+jtuyc(#x?VS> zA>hypXj~}g@A4oRxO=z@%7zGu8-lef0&QU#vo_3OLl|iiaWx!NN;WT+gsG@7d;ymm zA}J0NGKZkCFl^yabJ-%3i;{b^R<)94N;WvvL!HtN^fcUuLj(<)gWNsbsda@tmnQiL ztMzqFR^1UH&;B;gcNhlGhis-uj*x`owrpWg9PT)*s>Dr0PFxteS@#az=|%wrQi2yW zx7~J2G+XH7T^>r68Q>a=^ey^-b-ZXj2s#8^!_?I}7Bv3uw`jo$$2F*J&bciFEGl!H zwOJ_?fU+UzbV|gPC3Dqs1Wg+1BctN9UV5aU^^7Ga$pfB!3~}XSTfOk1#DNMnTGOsCq^>5tK&}w2VH}E zGj4x7GOoy|_Xf$SDj~Z+b0alme%Mv*7mN7D#AR_{I~K~ijY6^P@>_&Yg%nUAYxGlp8>#; zvL&}WfTP(kDV=Fs2t*_Vf()7_LDs0afu?pI%qo%0z7TV=V`a*+uFtW2Krv=zuw3t? zQr1<=@u#?A2bm(PcDQa#O0EvD#+C%?L<*{uLVkJ-$BrqbDV0@(b~L~Y=Ccb)6M~n7 zVk(YrCSX;XEL*iltS|BvBO6b`PQ%w_c zpicO6WjJwxqE*IYzkcw{84sJ*Z;LCP+Hu_{8 zsep_XrV3p)St2lr#B>Tt{d^p~^aXq<-o=Zd97~u*mh^?V8ZJvd-H>LC01s%26jo)~ zDMn>o4RH}Jab7Sui#d`%DoOsS3NKBooHsd4k*B#aZZk&@py)SX7dZ>kWFoWOQc(;D zXcY~1xy)?Ug2cnnD{)vf1Ea%&#o}Bo=uG%*Sw(Z0)g|Ncn9^Jy;Z2Mq5)LD#s!+HE zXRhpw9nMsGrssS!86PjPGRhi9xu~ItIv^QEpqPbRo<&8;qa0MR;+nO1QF|Emzuk{J zcMaiTza!*GBZ~$!_$VLERWOM{hB_RY___fjZ=jH^piC8n8iy*!5e@~Q(ZZt*hZYNk z$4TwkCEd9?`(A$xI>?ydev3Rw=9a)Y1|&fTlnj{;Rbto^2O(#p64anHN3iPhg#MPO zrq}hCt;2(Muy0n?av)JDSAhu*oq)7pRr++=m?)%PCDyrqhgLfu8#CF>%eyT?=-*XI0~EF4I#kw9k>5gO>)s>hXkmbd{D@_rq` zBq2CgC@LeEWHat?CYT`SlD^{xEWEp`hHfdjPW)U>t!muEg)zY$;eL`}ZY0JgSCqSl zj2qgf&mdci%os8pseJX?KyGayDal7P|16WZE;-E69d69gM^q{y#d0I)77e11xt(Ds zG7CIr+Yy!SlL<|eBw1D@x&ldJOqMxg3SBOxC&+bmLn75Ck6eP|avo>^ywE(|liR+A z4p({>M6M*Ghe!c}f)Lb@hZ6Z#Ro|8ZVh+l4j$F*y!Zd70Fk9G^7m>JdD@tUWNIKOf zI5gxmfR;%V5g|2jM2m)$A1q2E^k@}oI>YIpCna5S^xYt~;F3F~NXFll=%-ASdW;q#;d| zWi=ZnisW6Ch{fKgXQvMr33 z9ZMuaYN(+hm}qHasYDdP(K+OEB^VXc7RIzqz7r2AOydzr^{en{DuMwY0=|eFEn?h; zk>e=I7Nm%Spl(7_h^r*S7@ZVTdnZcMrJP=l%F)m=nmERK;Q9CPE%NJ@Q( z$9hn{fO-tXA;#JfGICIS1yt%~M5biOu^?tTgJ8X*5aUb1hps?iOE;YJLb8(=5p!yN zBwdI}X2Vng<+>TUK4xnTX;gm5pl?kB-8TdN0OV{7Ypy%SlnTd$kXg|d4nnpFt$VHS z@{QfExb8)G!T5wTdf$`c=ljyq0XJuAL#A>p+FG2VTka**2{f*+w=VG8)|!AUr~6I$ z-tDtEs07`9MXK2j&D7z5xiiHh!v8^mSJ0cS&BUiANTSh*={pbwfG)~@zYs}OWmxtqN|dssveo!?twNEH)l%e4vI(W?$0UZLa$}4R5d!hjikC)9REKV zNY%Kppu>&GfbREo=(Ym;jUAOQv~YXXmktNtW>RNq&8?3h7ovK#)%&3gyPG$5EiJkq zick>S-S!yoL2shFv3~FOj|XPm06w_8T~_;ERj5>-La^rI|+YmoWT^saXMT^IVqs;`g9w>(>DO(r`PzqhZA{9+K+}#wCu3DMmmbcP~ z(%+A-#p-)iOJB)cp`TF-mEN~nl3F#BlHM8`bqU07Paj6>y&6TTjx&9xPA#XYtjBm)1G0bfZV-4b%Uol2PyN*TXEY7(fZA~I2g6&(?JSCZNN z?MyaG4wB={qRn$ADKIx)83=7cjj zWmsCV%v&4mcvll|=?H}rt?ja+7hr6AGCei0=eC(6k8ev`Mcd-e185qd;k^=LmugU~ z07Cg7CJDlW*3 zg83sDURQxNH3qByr;sKF5X{>M&vqcz9K~E%!QRpYThcv&l~X__xfH8PJ~(sJYg>%Q4Fxm<!BUlh`im75qS#r!7&(i2!WskpCMsr+HjML4K36*hJz3HV%kuU3`mG5DVXUX zDq0z3X%c}MADTKcFpEjd8U={1f)K+&)McWW-B?1@ia>RWm!no$SMNjE9t*z!?y9$EqCK_9|P2OwB0Lg?n{#9>z2NexQ;LSFs@%p5gX;mF%X zFg1z>YnWMU{Ro5`+4{D6Yz@V&ZMR&B>#u2P-SWD`Yg^Z&>+n(Z9UQ_@;X_GMA*EDA zG$5G@isra#*9!|Fvt*mm2If!J$y(0{4i1m9dmq}#9z8Oiu~8@UfEtnmQ)7(v-2;Ex zaOBRHU@+5c`a8;qhlDojkf51qL&^h1f%X;2>Qvt+;!K9u+G5W+f z9@$;wj~WJyAVYvG`wA(?aWEgXC#TMtVXz`KS0rv^u*yNC=3UP5d@U1q@9NgSJ2#2B|JtX$6AFq-0tvJ19ro1gj4qy>Z^LbiE}Uw|S0b2F z*p|E%s#I`|C0TJjrfQicdE?c5E+sSEdmvs0In-2}Z&O6X0`u!|Nf#CJc62i8ASe$j zR5z98<{!wTs&ZE#OiBw>H{h~vp>S!t^ZwVybAR!hncx=>XOy1@H4C%qa+|8Up>fTC&1}~&AkUM`GV&O0oen#% zjiW)%c~yHtxGl}80)$Ba7Ai3r;Y%Y}U8f>3RK&=>5_)HWilRU!q9J*i6<3s>$Qq!F zU=_n{_$g_WmLpOwgJg5)1qZ3urtH6Xd6RMV9U0}}9}mi3w;c=+fzmw?i6D7AV?m*I zG9V34B~x(^Q7V8Wzpg0E z`Y9+PEVM~d=^bIyl?#C23>soXLXLn*117T5OGK(^0_kKClS7?YH{QS|BGY0->lF>{ zt9YzO!6b!UJ4Ued@Qm1R&Wd62T3ql)f8O?*m-w!1>4fjw_v4`*$I!oF1;WcCNOi=} z7;8W|HiS&$G&6ooBGF_Kpgz zG=fYxg1s{)1gYqU%jht|kjCQ}Ylvd?Y6ojFc|3O65){{gU9d08+LE)Zr_n+F$XYb6 z%z>x&V6cB2!R<-3^>?Dw4Ls@?$XNoZmQj`}$SCVA(26P=LuJhQ6|5@zFfrSU%%}o$ z{ZfoZZLHiq#Y%H=;kRV?V*(Xl4yG;e@O}54IpbmDrPs@fbrh4!6g1^7MtryjddR}0 z&j)Taf(J@yF>^2~)L%k{U!8(h_G8LyMzmc*;#dJgS^$0x2wNF27C|9kB9NXyWM(7E zi9E}vrbV$Oh`_N11mzLLd<@XaIFKjZ;z@)=05d#}kV@2E8*Uz^_RVqbojWra3=ueh2oNMq5&$DadQp~X$(CeN zlwet=Nt2c>Qxrv!1W5ow9;CtKxifQf?3_-Y(+}iLRrNmae)j%tcJU4e@#GPeRvGk$h8qtHY-ofeE-;K=8WDbf8QRezd-JJ%c9ww5 zldD**J)j@^p|{w6@RRJp+nZd?;4oS$L?1g%Z0Gc~=U;#AvlpJm@-Tvv?Q6*e7xIWL z2i}7rj%PDmyVu1*WI}6&xb%fBy!N@L@Z#-L?0@-J2fy~lFI{^tO}_z{-v%DO|5)o^ z`5ip-r@y%L`5(v6mMW-+W1Q_BdS{x1v}7nHeVyvDiZnTcXLZs0-aXv7<70QCp@R`p zErMYbA-Nfv`7vCHOR_hS%nVle{z=~hliHxnut*s=Cl7cTBqoyyj~-J9N$N+-M+yzcr_J-_$IoTTl19H}5e6phfiVw=-WZB1?;`|_- zzjQ5&m>zef`M#?7Uwr~FLVEA+==Y4NwQ%klXC?GoC5hrTk-$y#|qA0`K6KmcW;~t zzqG`lr6PneA$7Bl&w@3X9-Qssv;DFR-dDgf?@<=_%nppqtSJg}LnJrX=3Ic)r zY{1Cy12F_Y+Y>NQmW1`B`GJfq0g@T=^2r>-LX)iQGTS#NkJm}r&=X~s#$;{=%+82x z@1NN-5|<$nk~y(5bsl4cvS#tQd>v)$fy_jk`9#9G^#0gO@wkfnaZ`DwtxG@3%c>mb=6L-J zx#TbY{G$8w2Qkf#Q{lms69(_k`1f}PbS;|U7(RyCzmAY;Qkgk5Yc2mDrT$Eo&y>+Px^6cC)C0Aar z#IJv5IePIcUFpI9?VkLfg%WOZd2r+)O3#paqqE}2`Pbz`Bx3gUGn{uefb@}OO`~Z! zi_`!~|8asSOGj}2JfQ*42g@S8Fab6DHQUi=vC=7$$N~#xkfDN^88j_x8km8xVwRW# zvJzpd1vbc@ZpTQ4K@{i2F4e9;b;TTSL;`v~C9_j6X$?-&Fm5DJROI|aNIQJG+jbE> zr(xyv9K2(XaTmXiFcHzZzXg@;&_T^fwVTWMapx3gSKq|jSB~)7gNq1%y}}+Y?bGb3 z1je^ih=GU67cJ=A1D3m40GtNG%MWP4$ymPIWC{O1JIeJ)DCF?ceG@i%*mA!g8iF3wM z8i2_HVpWB=cXKfK`1bGj4(?gQ*t(VS$@_4=woB%UO>X@KTI-c)J$wuLX25QVPm{P` zfOyCwcR|GseS~^c#G-e`y6GK!ZDkQFTmvSCFnSlTRP#|-c!b3}8eOl5c+gUzM32aF z5*A+1p{hQKVtoKv-NkgoVc?snjb{kC7)KRuF8ai73z0_{DKj*)Fn*TaQhAiD0J6xS zb2)gth*Zu&c~qlNygyfZ)CCRhSb;(ozWK=yaCo@<{7(s38bZq@s7}goMk7oI5sohB z@J!D~P8Q(sA)@{grg0yQWQb5`A;=1*XCv6O0#4lpZ`bBTEWOgl@oo-cAYtiJorTkw ztcM4fJSi|^SRipLq5rwsHo^on7>}u4sG)P1 zN8jxre-2oXA`}KODv665bql)=p(ZXs7?}{g0pJ}o(X64pQpK1%!>wZuLVX2mON*4N zoKiJ9Ouqi!B;6JN7EI+ca(>Yh#dbUGE+Fbn5pmuCx-DX5Ljn4XcaFPhx3J4>uY{Uh zZvL@nmVV-gzlc|Ee)H_c+rRzB8~3`mc2dFRwl^fu3mk$`ON5E*gyX8_RhGx zATK{vT@-DmM=p8$cgG(;x^d_2fmyO*aUC|tAnFm-q(thRXnd4ivpqs25M!C-I0WOe zTzfO&*jZLyF;DpebpX@(!W+nEHfNwZ0CSBj&dwl~=3W6NavVjY4E^_5z7%DKEIE?( zBV_7Al6{_0Hb4SG23^VyT@ENbrXEr@#LVw}*&5+-N@9Lf6r;!RrfdkAI{^)lS_Ge) zf_Fts*4OduUs;^}3znwFZ#~lg@!gU5{w&0)Go24fR_0b$1So2rjDw;mhE%>vxdO8={5m0LgCHqKY7=VB>is`so!l zctTQ`$T%@{5^iMqbk?(}KMuK$op61|V=DX5UaDDt^-3dt?P5w8A-W;roaDJaLy9gR|c=aC3zv6Vx*f1AF{^ z^BLSJJ5(Mg7v@gS`GzY~da{H@2C+&X8z?h%C;Rj4mYsc#tdk_5S3 z?Q_2)3OF?cBrHK-_YlX~@Rgsd6j|CKWjVz2f%9ZObS8WeOq9X=5RkH%WM(29#*k(L zqQ#6*4){Eq*I=g>&t@5m!v@w0K(7ck&A1Yehxs{k#A`fO6EljYoKaGv?C%4DohHt3 z#$H&T6)v66<&(uiwEGsOAAjRU$f%Q0{X8T&VfpGKR{Us$TH|Z5h8G}qKF9itZ=t+! zhU9?9=rBa2oT5@v$f;~G>Eq*x;C6Kjr6j_#|C^YoFG2FJK=%5G zf)xIOg``!1Y0tpNHbUlrD_&z#Lqlih>CE7Wk`W=09oUmR0yC>y6`3%pkia<9#4%1w z5pH=3>Z5>dwK}x7+@caLv%*&eRFX%md+8g=oopjj`Cl7PUHWtF_~x})_xf-2;`kuB zG3jDm(eO$`;k|_#dDkoKqO(UNEaI1h29ESId`7XbAeSJpHp~K{Ev`S}|1L z!6WY?ro|n!4$kl!haddlhKDO({3$^fx@d$vMh|sNkAXtNhTB>|9Tr-%1k+T-KnoF# z4e(ljuDQu(3bT73UQ&hTS71p5ZoxyI6)>FTai6nbjCX*19mSFkN^T9 zy8y9ZgJ0FapG^_;81#;T$ntQu!BBMuwD3nU`?-QUd*Mp7h$Aq~&5_Bb8_nlE5q$Z1!;NLt_4|c7l~ZhpS(FV&n6#U;GoB zSEbENQWpuqD8_7fg0qj_$Gh)*?YG};T>CAYP#*rmCeZC5?w{m+M`2&0;`NX^%N#px1Nk?B zHAAG+r8?{C5n6)~B?{@Noxr|TV%k9i`sEq*8a=cJWr{rk9X^J*pc3{KL?cGH>_QPk zj_WHtl~gWi!75kS>W`M(fA7hS;D;qmQbyBcbTm$mu6O14Zl7pxjQh#WWE##g+!I$y zm24Fv`BFxBWs-_4?aG1_lyyMI=Ho`k?6J;ex%V+LrWWOmxs#jCc#xg#nl;1;hv@0$ z>@hn8)T0~cB5%Ub8Z6bsB@qu zGrsQ+@P&EIFoPn^U7Ws%#C;s;oJU(SRmovU<1ru=L1{*Q9L*i~86*iw<})Fr*>)|; zz;aa}$}#5m(-e2&aKUg&MlQ^mhQY>$oWu&!G!@b@(m2g?Nf=Qgx{rAV8C*7FnW!!B zf|B_&A!s~kY$HlMnVujh`o3S8Rly!(?>#yW7YJ46K_CS#YKh>eVu*LrLPc-bmR6w+8 z1>B(H$~O;Z;?0i-!be8|b|VixDaEihuiMn>e>`q9lX`9w2&GbR(h;`Hm^4=cOb(cvm zeIaEZFQ9Km92#5}5avkZ3HKt#jM?0W12^Co^+Q{Vw$@cdtde z!hZ>0ejZA*O#btIX!|aH;tw4CQO?a>y`z$!SIs3%9zw?#NELw_(vUo1h(_PhZ>-JU^or?A&d)Xvs1 zYwFDQZj*5o0lEe=jWLT4p>HoB&1)!hBpml|qIkK1hPcT--1#=#h{Iz33Wai*rA*<^ zIEYq?2Iru!8K{Li3uhg2SW3gR&IEUaO|AmHr{Yd!g1E%teDDy95n(5O6{p2rsy?W( zFAsj@2RA%C@l&q~8?J#^A{39@l}J7zbIB=Glm#M?2yR?mxI0 z-??>sUgS|MeM2x^Dx_QQP~mo6Zory%?H;1|X?nl`Cs`AlxVhp68`s+usyF~p-S2v6L_toRAi!yf^E zu7r?tA%4q6SXu*~Iz?sQrLfj#X=;Is4fq2NbZ`!nY97wo?Ri!B@?qAN)j{-pfXb6H z72XtCGAX0C{sQv4PioYmViYj0rqDfVVRRNCZ`E+uyQ_V7a6dWZV{lQ#b3zWB;eyk$ z0V2xaISB=91~1Q(l+mz;*@-L@vgSfYRHy-ylABsCdB#Q<0!W3A~3BygPmvKQfXNMbi`v59+CEM$8am zHkEw1a-Q+StXeW*YK18FIYbT+wB~VxIp``=W3mp1EY?N^aKZP@ZCT-!ltFX8f8)#q zoJ>j3vQMXjn+9{|Iung~UVgs2aUXLcnBdQ)?KuQ#mhloY1TleS%Ei1{Fsi0qbQY z8MX^r3^>*mV~l1oEm@hzo@b*1YbW zocTz=AS$Q|H_-J{YaGT%IOi#uZC*7-7c(d@cDMjQ12bXdh6H!Uq`*}C-&@< zkZY#z(6g_FbdoI4wUZo6ZV%a|PsLQjW%9ovGF9rp-F6VWn+TexC>klscSI;76G9-P zSAKxqX9<_iYIyRYj?+-bVOfSyd>8DYh@-TH@Y0ah#e@|O2w$(K7*8Dh&{2wUD1x=c zdG$a%u83dZkG5kxxb>Jsk7M{GLfsG8`=hWpI@9oGq|C80(o92qJW z`ZoA+54a#9?HX{!D!f7wt482Sn}WFO;F5#O@PxIBxX2_gpmDR^H)D|L|SeT-H$j5{j0d>*-^3Xv6& zDEC2&i^%U)k>0w-rms&)tEX6cpkYr{Aguyhp^d{nhkKlZ4U*aTW{%=Bj{Hjro1Ax$ zzng##Q>rdF@X8WPM=4!CERmTjCf~d$CCY=#n1md*j1!!&>wN4b+y-lq-|jF6`)qdO zJk%|h+~ol)-u+2%!3aI&CKZ%~t@%0z`#Bsvb4H11v!$ChKG!vHcdLXO+dhQTs;eF#REixjOfjQSbt_ZC*WMOf231}Gvt5zxLAK+9|JA0<%k zP9c|LOt*aS4;CS%CG?&+Mc=aFob!lU-om$e9^Fa#_>Vp{V*@A?3T2 z#jzG98_=SV4NHdMX&etlj$G-obVt1nNs)fe(9w4fBDz%iN9!O=;s)U>}3u% zj;yS6Ns#I%4LBx>Md|g<2fu%!0lx6c>!$22hoUOqBC}AL@3)}ixZyiL_+G& zkSPU^_yR%n4;f9GU^5N{?K(VThT%lT#YwhKAJVWnVGrvsAb)L!Lg5;`l{_jRzrd=( z3=dy_0G}7J@ufDpo=V=ukabl;keP*UEit&q49_rV5B8xSxfth5i0w^iC=sIf$Qv#* zp~Yc!JfrT#9L?NKrbdiUKBp`3VGwf;B}|aAW1CP*1lcA&%cEo}My$>6+A&;k%^a@$ zL_7SGWiDD}Vk)oJql-g|(qHYA|H+N1@Eyh@U|A|EVH_OF090{SNzcpRyaeotHhcch zH|&4E&Eo36ylec!u_V5`wTxVMgok^_Nk5x9MJrAxmKaC6l6w6l4IM5OWG)R|1e}gY zjSxE>2+BId)(i-4f_Z|+VlHI)k&T6GHhZe}`#Adf5Ao6TY4+&51R+qss}pDsXYd4` zg=ha&!eTG$PMI4|^tE&1AOG2ZzWnJw^FqBl3cbnwgP_%@OJ+Hz_Fb_3!_ZO-DbB4* z%4Ev1PCssc&K0XhHmP zlQ=7fOpSQYOxfn1ie+_%DQ}a;X9wB}JL(Fs&+X!Ak-@w50?-1E){iih`gq~(5Hlme zH@78R-4pO)FUD^??;mm& zz)Eh2)hU6A=a9%b1o8wwwH%jo1naW2Z!oK zaQ+yaRzZ27;v^L5x_-pY%PEzUJWEtUuVg}fWM_Rt6zL-B-iW1UhEF|(pJrs`6>9Mb z9A9AlIDqWQ(4-K&=99c5vYxp?4Z+8(<1uG-3}tH3y1UKN>N1;Eo?4(R^sxGS)3(C@}=S zg>&o-W2}HPGLCBiuRt(PLyUW6Bzyp4C1UkLg?w@_98X|G6ZnFP$yO72ehj%kgGeD7 z#R`UjhDkZg5!o1pF=?ed)5khy4tq!pK8htUykhEWLGzxL)J3eT2Mt%KC#g)Nuz3atG^!O&Tj@2BXW` z(_K8`II_YqQg;QSw!i}JF1f-vycb){Xxzq1SfSdW3GG~r{RbvmLmT`#5kXBr>I$$s z3REG0EEVTo5oN)~rmSHa-9q=^5W2pG!RqCCLr?LZ2PM{6A}e$->mzR+LtUyO+&F;N z%R#ma>7C2bNGV?J+u#OtY3;ihdhi~f-#l>v5bYa1L}5$%$VhX zEeD-4hwuXr+o_2+HXg8}?9lGHG{HTlE;Mj1Im32Grni?{a91a|`hK3i;Tp)757?!K zNO#UJV?22Z2o`9)yhQ0lX0~2TM%!1Cs;cvs+U)9j)BWLgeR|Po%5th0)5AVH**~U^ z{m7ZdVLIJ+D~E??IN&=SCmkO#N{*>8IOD~1%1=xlL0a@GpZ*E_=+9LC=I7LtU;Jku zw*HfEzn%O;^T9vo7s78!dst=$U#4awkAwa5%qnombNeJKDT_)iDA&$Xt?+HK9AGrc zv0U{O)sq8O$XUcTMroSx*jI{Rb^tB6&!oF;YI+yQJZH06`3%-qn+T*SYgc?6G858h zNJ{(yyseb69w9&Z7EMb_cq08g*lCab-eQN0@)9K{c^GG9wp7WJQMXXBEwuWK?k^Q_ zJC51%K!&I1aL7eyhsSuH-@zl7#{)w`%=cMyPe#O2+|m+u?&&Ty{2}(=H(?jI(W$4z z+=q;;4;jB9l6pB0na&_QS^_^_#3jwb_$ys}P;23jTNN;A%5GihkUJ2N-pw(8)5gU{)A)Lvme{w)8+6oFQ_aPnZVCbyV4%XOkQ75zikY(nV*t`TqX(2I8_?Ae4 zA%gzhpHtL8BKvE%f_$LUh0+mjZTg(Ga}GkbTX}NAv0w{=uQ8$7=Yo;$C$1EMlLWb0 z;GTFA7k_4R_V=1>^4U{C?Lo_Ve!xO0gM+b93L+#?ltdX^D6`HyQHj>76mfsl&3|KB zGJjc?*|?76s;LW<`q<6jNn+M6`k0fFr6#h31Z60ik(1Q`rN!|Kryt(ozIEEeu{)a^ zWu;9Ayq*y+^^;Wc@1*5-yOf!d-+5iaqcxRPuNM+E{)g%Cy$+1d-#~TwpGewk8|hbtvx#;>1^z3+_fS^eEN ztl76%+${7U6l)weDst@JM>yNeL%o#Z_>qN;doq;i6>zz`EKw&Ej2ui96>?mmVxbB* za#=d^z%N@ETbbCFpps8?bDn6f~* zxCn9Rv*DIPW640_Q36r*8CD49G=q-;{;mQ!iNS3#R8$_SK-8&m%-``S?T9QlEa z$cc+Ej&L-V=t)UrEt=xpp$R3D9wVv+8G||x!;&CK79_90VzB@pHi~ux-=EO5GJ z1#W973^Srs3YJ%4EoR9O4*h8YTC|Xl3J{<|tn{IpBUob@hOfXasMu9`)P*t1cO_W; zI@q&5!lHvx>QN~QS$76RI|T%iM8ppv-PBl6O+i}`(5sWE2TV^rl<%4djTEC+3BlnW zbc-P`ndq+YP{)i)g@^@X4)9Xp1hcR}>uF%fWC36h#+8I6+q@#X7@nBWO z^3uEPg}W;#U%N^>rLRF=k09*+Bs?R}K6Bv&!`&PBU0=X+0guYsDRq@a1ULCi>c-ve zZ=~g;r)hEaBKhi5iS$T=)oPF;MBE| z?_Yr)tMFI4pil>APazmGZVti3-fa|XpjLjBh52QKI|60L{?MBLV$C>ty3k;oD>bpnWM)bl<=mJ{x+CG}qkH-9 z+}fo#{n_Z~?7?WH8y(0bG5eVp#aCXH|HfY{9{%0m*lGUfzxLbWe~N2=9m<1$B-Q7n z&DTjd0*i)>*X6boSi{GZZ)^n&uA-gO*pj0d1{nTfUFu|v-6nav` zTVL43#;tp}*qh;9RmWlWx`;gFG@^(YdzkqjmQ51Rcns|cvvUTqNgMiS#_)1umcARa z;%Sl0W{9)A&E$J!DuKu{hs-tzNkT)|R|Gy! zYMN7df%S&bB-@yXDrl_GESm7+&QUrXru=N;2oJnT^6>2T`+d&M30iZzC>*_;c)ea) zul0li9n#1ZiS!qQ>dGZy@oG^oa7LxJ%`U8L(*-_7ymJrt2U+Us9&U{%m{JQcCV$8s z-anwd`!7?YXdroIDJ_tbK6RkW>rd}!cY;HuA-r6E;frQl)uEmo!G3UK+Ufk(KRes| z-QOGE^xsGpE)?js3!mls`TOi)XOhy`fg-o?`k{_~)WtM+O3BW%Tzq*8*oa^aZIa&& zVXmZJ;V6gVuM#B9RZ=mtd$C_zCBX;lqbUj-$i%>1ARF1`nYzejFRVyUxA6G4X4 zDzRqjLa{t(#|GRCp!5QR@?ii+1T@Vg>#oEy$cBDp4CPS;xqJ?(xr^aF8B(%ifPiIqAs#1icr=B(nXGqdIEfmF%pU-MTN8(9+6w|;L8cb z#6*}fs7|I)X>_ntLCG4jg=&a+C51easWK%dsKjDTq5T4*)j>biJ41AGDuvvO;G-`1 z?PG-6GHlmma{ri=QG~Qnh3#q>=VFNY0tydqp==ZWW%qkOxZ&aRKlBCR>{P_XKqS^T z=P)y+Rlt!k#nK^A7be)xtnbAby}LPZmm-KhLvSmFMtukyJjEz7?LiGz=>)^|5YpV$ z#DGB^QQbl*1DS_1?iF(=x9+pt*h`cbAr#b7tVhSVS}LA|B2# z+S^3ITY`IWAJWPg(#;q+Xd_&Z*m&`XvK&@?`wH68L(t{;2`(q!V0^ zBW(2ZXnF!>7gF%{1kqg+y^#*3xdYXlQF6bEyJ)aSn>X=O_5t#zFW}d59gNZrayHLa z(4>czF-(4h_L%`+siOCE$|h=_e(YKfp>&4cPme)+14#F)xKU`q3Q|_(e;Tp!@2BIU z$T;B+^r9@(tJQMI@+FDmt6S&X^XE6jXIn;{y zi0>9u2wNIHeYcsp=h;W)0Z#wMHB|p~X67ite!+usPs75#g1S9o@4jr4&Msm3-OsYw z+Lv&z+@Vj|SK+fIdepkZ8udFY_b&=KO6ySZEH2_6o!}mOUw9oHUm*(a;8oa|BI~d| zV=2yX9y(>2_4g35Ps5;X)5n*e2-z1tlIRJqj$cz>V>5c2Uefmvg_rQ5Ex}4YMh}nO z{fZ2BYHA1uM9(3_BT>R>^gLS>Wh_R2L~ol-Ca;@NA3mf7yM>}~%0AfQNRw5(-bnDR zuQE2)12nQIgUwNw7r~1GTl8g25MUyg2&D+Ej)IDw2aiKGa6XSMXmp4_U^~cB9!0ES zgnfPiPbN>`-10BuJ8>1pfATen&mGgfzx{bX9v8v3WE(?iB=#ke~A0Ci{$vz zz@<$JSpzLy;|muq@?C2w>B}>3c`i{hf_}`*Bbe`e6WZ(!iqR=p-avd|X}&kHj!Z0sgtLnau<1GJ z#ml89Ui>NL>h=~EtO?w`Q|#V5#I^q3(Q*3Gao~1}EWcQQcD`z?tavMpZKJ6*!Pf=E z{YL}uD_?WY?%(=$f2nsm+n;@d=^uR?q6Xa3KgY|PIjk>Can;l*gHQy+y>zOmG_ZAg z`YS00^%Asxtz$7RebtVsSn~i$8~>vm$kD4)w)=P1za9 zOeq!(mPMgT`7Xwu2`&o=k7G!p3R_gEnzOS~9Og``U~vLDxej`?h9r3&)INZ>WTVj2 zPz&lf891Qj2`W+%qr-$kua7OGo^})t5_5>gCKJs8rA)=*po;OvA?~^ggl?ZQcXX?0 zGI21&EQxTeE2L)c9~BEjho=!qXw*5TB@qp6o|#+*8nKa<37Ab06sn*To-)K*vcVu{NMRIf9Kz7c=#v3@LzMQU7q?G($yJa>IH~63+2H+296I_baBSbARcS;;Q3_K zrJy(jE@X`-C1eTJi9!eqM<|yg2vGx}IGwjC30ea50>pI@NhJq68KUA0X{l6zR@;Od z+E8$SL^g7ZGW&~^+&#|%4)he}z;f*(U74*9N$XL~U` zD&u~rlh28;as%}C#^{Y=@ZlM9Her~(AjaYR?}X(Pj_xBj0DO{=A4^C|0R%IEDa;^? z+2T5Dvx+1 zhDR)pUx8}+s6-z0`wEVyE!@^a6oYqBbH^C=N~n6D;9$B1KUk-w+&dUNs-SwbGIFd);m)6mCa_~|@j>-_vN=V`a?fVk6xPf6Yk0vLes7;8-0{@PVxRccgdypj& zcTcC-=`iS_h)Uw%ol+l><&%0}N1&+am>l8Gh$d$>7BdO?q(e%%%({+_*y8B|R>*$U z#~b<>EBjN3TOD+_6MQQAEVsaEIC=ISdgq_OOo4 zz&pGM+%B?(AG=0!IVAhh3I{0>aU76Eeu0W>J+h<;Ji$b5p^1@S!>)gxrin%J>iejt zF*)%VGxBMRy-I6bgWfS8VSy<)-_5fR9{$7R^7+5WU7kEii??ky-rR#!5vVpYSU$c> z2cPP(lC*(K{a2~6`W?#IUuNp$R#N)jjkuufL17Pty>Fh4rP^gyTtuF8Aw{w*6-Afi z{+`>tequZCIZW;D@M`rNydJ#CS9;$O%;^qk(J5P=ewPZuHU3I)pU;UW-1b7m>%}L9 zP+#KP)*sQO;2pl4SUm5WoPIcAryu=`WcR_%)31E<*FOH@>LFMckj9~x}XqtYq4{)~CM3XNu<`1xhpTHq1f9H6TTfYq3$vPSy;dIrcKRkv6;RG~{D z)kZ3vsxz8QZo@v|VFo;DDNkKpqpqSNs2;(H2bjhgIyGa&LtEwTcYV$YoCl2e$FL>*}~L2AxG_jEGuahT>D;tMCx2RWP`@d({6d4Y_$ zG()A&kvodf^@`LV7-)7aOc#CZQw(jGFpG~MxB)r7jhVH8NiL7VXbeA-|3@h;HZ&%d zIKaD@_Tc7#MS!IK7APY}ogS?MV}UI#yvVGk7w%Vor-1Cp`~cr7#Y z!U|p1?x$pG9ms5qu%OM`;vzAJvqXS**hg<)fY1|As7x_Au@Lt~YK9gC;R*Ka5WT=d zNt`0}IE-R~NmKA+32xs;#<$U%3>1a8rsuF@d zQZOnoNR&hUW)YkD2ttFv2ObNm7R6N)ZWb7?4PZX!<0+`9w(_vdglXCkEYvBkn8fKP zFzPb$wHPcczzv(aZi4v=?zLUqZs>FSbWu%^jD757m_9v5voFrO zkwvkGGG}HOLK@}_Y6%mpoH$4)5k{2|&ET=+-6#yO5;@4_8pua248}3IB?n8j7(qb> zt!Oau8XDC)Qt?9wg#=|S2R^ri-g1u=jYmC~f|@z7r4+VnP)?d6D0SgTEtJa=rE50q zM!H6NumB?#aVjyyg$U$jT_F~7a+a}Um_`z+ z`XVAxL1I@h&7@~(0x3=qHdP$61-M!h7uq38i>J8P4DjMZ4P`^YWHS$`E}}3x#O#QH zTQVtsF`?OFfZ)(1X(nTO@ge(oyNkvf=TTPM^r5a`<-UZ!EUbY&qu_ViXGq>l@Iq$; z3(xVm`HDoZ+`d5T?_I^O{`e8pgxK1D|6_EzF{2xw{eTHyEz$+Nz;*p=@Es}D3LBV? zkC7g}#l;VI#Nw7Gs#`^|Jg^0Q`UvC0LHFVHlbfG>W#_wZzd!uF;>OZ&<#K8LpWn{? z@4xz+qhHeYe+L`EAIc$rn#jX`dd?oOu%Z#REnEsW@$BRU809HGs86ub-@?VPjo_k% z{fj+3aqnd;IXpVgSqQcBSbdMj)`J4r1q}z~6LbzrSeq5W@-jPX*Qve};DRmT_>~#O zrz(u!ZD7=zGF?|m8hj3wx3`I!A=pdzA&zuZtt;4W_Mxf*ZaWK@LB(=fgc2X)1@xGO zpCiLiQBEJBk`9?zYM@)xk(>2cizyPVUjHDGPrmE&gWsHTx4#wgqXTYX>089; z*IDk-AL9Jr%a}|*VFSLOZcg9CqVqQM3a1DM4}c(MrQ#i|_d3w-*=%w!LlTOha}vCf zO*fB=*gSv4|M{)=xfeeF zO#+jPlyp<3s48+>14@iz5_&nj zxzZz5R2VOmv(_;ZtN}T;2ywqeKCh9bR9QBG0}rUaQ&P{_C!k&Xx^!nzI99ikYy zi1Qi(F@RD@F)b7!&vK9|8fvkMcp(Sf_b@h9v{ePGjt#pR;pC|)S_26wSEbl9z(g0U z#UrdJShfWuIR|1Zf-4H}%Od1B#;9W8j;_I$B2bWGH5#HLm{|h>(oBjH0=Qy^=~R%8 zb;`=O%wh&VfKwk>*mwx^){@{j( zuYc)Za#h8`ROirLl2J?|RI_e}(h_VwkAcP`%(%9cAU{ixWo!*cB5M|6CiNlM6X;d| zUvEQT4*c*fcmmLor{HG+1+heqP@q(np~ziI<0<*EMy;8HBa!fB&p_mdh$(?z^YC0K zK*>6Y#XiKi4@&D`Vb&>oO1>%}G&zKvkD4w*{+ZljAO4sRUNdzzQmSeM+rN@YR89frR{n8fs1olQ_KA)u8Y$ zjwKGci4DOqVVVi#iH=@x5tC4dEdydN2R8;Axu8lZhlRo-?tM~VAKYWqGiFGt22?k~ zY<&c$F@Zc5QJP+cEL9%fKU1Q4oh-p*wY zZE)HSgnK$Xv4FHOH391d`Gb%a~td3G<{ghwZkY9Gn*US4p`2s zqId8f^F=33D`}DwmRYIgCu8SMJbd>!PK+AF+A>$m@wjaC*i#qvg{MA$`A=Wp$2Y$A z-+cH7?cM(nuiXBgsN9~Ui^_GjY}JUj3bfn24OfaWX*M7V7Nmt9X0!;K+rlvYBWShz zSZ7zD8RuY+4lujchGtb5Efe)uCWy)t*qo2VEI`jqv66_?8W{+c4!mO4Ev-ZCF`ybl zXcG;SB~-KDAKyZqKLp)o2zvXhSX!WU!vLGUgL|RG+UXL>aUS1>#ohtKAwI(Mrce1; zWA~E;$7_e!aQ5+{CD2FW8ts=EQ@wr6!Ux#Ils*7q2+(tI$rAFoZk@8(=@{bDkUAHS zaCak*X`fj4Wruj_7-B{gyHmiPCt^WfqVicD+^z2+O(qzrz(RM*`n>~m;)|U4 zWAw)YmQOUuvl*^G*rGtXNZa*?$UW-gLD9#>4bYQr8RpqCW>1L7jcTZ9mk_KEh|hOW zxmifj;?wt?7i3sN(3_ z5c%E##3<{peuPT<4wResN!WWMtj7PX-wHm76#0PULx zkT*_PQ%oWID$3jtl@k-V-$wtqi8mH>c4zB^K0_QXRLj^^YY5d{tj%si|FcB=T7>#L zS2!t}@p|n$)Hc4u9^HA z>D3?lq1yV>KbCv%?V)?^#15}cX53$KQCX%jGnjZ5!YGU|>aH?ZFetYbP-c>cDj;xD zQkV?ICpc*y@hBnlG-dUAgnG_KbJj$cacH`yD2NWu3U!3Mgu=K7nYS=rUO`xjk&9J0 z-WrrB#j4@ME=NqY913;^z*dZwXo6`D!es}dk=1en)Qhpw4=~xPqsln&wgJA?L(S>I z4n^34iNb;jF32#YAx@A(FHX@g$1oBeXRZK4Q;>)`}BkWoi7E0ffw5Zwat zcQhuRMlgyRSdKxmQ*`}B1lc-M$)lJyVDm19RhecvlU#R#vPR&meTYT`G1>$!$&lg^ z4ofz}IgS$DLoH)&nvC@QC1`bG&VmAF`V`6;DUM(WA_CsV&;IORNq=CThiBKX2xX@P zl@#m^IB5D54Ov9OE3hpO#sZISnL$1ofs8zaVo34BEN`x%?@o~LCJLGcW32;A>w+6h zKx!RSTR@}BVTU|Q$Ha1p27i-5?{o9s=yUlP$FYc8V-Cic!@@~`lU9UTOTsaUsDGHJ z7b%BGA0hA#SudAIIds9?6n#;l<2c8r>I-;!_6co7M@-P`IE)JDt=u4v?y|;YJ2P(} zoX8kiH=$^YF!N8~hH!|Q@d)z4BFG%We>#t1po5)cPr503yoBzvS%fb|;VgTS0bQdG zAytvHCz#e}Fg*d}>9CY8`jinl&*M@zK{Y?YLqE&IO|TV*_}T&CBn|O&*2!8oARG|# z)iZLtJPUXiv#^ZiKtQb$Li74KaCzK|DmZ5lWZ#3Yi&#t&48_hIDw3%sy#|MR*#oC! z%wZLg+=V8ju+%p6_zYrP!|8%R?LcJmbWEp}7}8i`d_zMt%+u8N*<$?&sbxTmG$0@h zGq{54LwQ(00tLFO(U7|$zmkrJ}1<-s=Cmq@sfMS=aWQqsx4u8y=j<=DHT#dEiZ7@s7mYK z{ObPo@BID$@>|uxm#G+b#X|K08)*U-_Ijw4ZM?Oh(BQ14*j=B;^o#qiPsX5s|NyG4{-6@s{fypf_9JGgCSD+pv16kMC5GYd?E zh!mp?T}W;4S!)z~fE)~jq)I*lRYx#8hgaA!_Hj0cZJvN*7s2C2h;&Qf(2;DmDhhPB z6@v~$_FUVbo7@xwJH^^W!@6%`C&}R^w(-MA@f7y}-!nA4M?>WO6MQ<5@m;L}Cqpv2 zJ*H&$P}I<7ODN(zoLpw2{t9xZ0s7toPVs*C%lE=Vglj%1=OT2 z#NsX3;UX%hZM=&+NME1e)4it<+}^}nOYg#e)xu}qdj|C`!`DA`fZ?8wAHJ7||8#=y z{8R}1R|oh^m%wKS-U|bqkill(D&U2}0*!vYL+&+=iSOv3`V4~b0DNx=vb7C2$ITBC z-BPg1V%%Q^b_@wuZyH!BOz=s;hjj)7#Tb(n4Ygql=A*mVjwPgRg6A7|alh8Z(Sr?k-fuA#2P}B9N~=++WglW8|b<{JTW-IXD0!^wN)o~*u&+wmT>ch3WD4|dFr3bi8#W<$Ik-d+LEJ`p7#mW?T_pf9KyEPyKJLJp9vt z^($Pnk&>ZiqPdIM1TmIR%{Rz!yZM%O;p1BIGrwc@7S5J-&?z zEsUa7EV)b26d6Y>!)Nl41Q%&;h}*V_2cCga;A4EPi0Q0^X5E8EK8!ezQcZ+>HigeC zaO(T-gq2 zEjK~DwWP zA+N^)JiY~XS3oZoVJ**Cy&TcjFobZVV@KxjfVWX@2`C2%#zz_oRvAy}AzCXyd=jA@ zvWl`-fH9e%??kYt5u|1S!N?;$$~e3#!iCP9<|ZAL5Nqz^QiFa9 zKS`1EOGpzJZcRc_kRX~d#KcDsR-sBoY#JP9O$D5ipb=%tMg!5BhH8EUzM>-EkdZsh zx_^P_Nrv2d2zi)dY|T(B3NW6MGld5((~$IdXaf!DAi#JK!OERs`O-1ODX$SJ4wMU|$g_vkdu~gkfzT9^;wpZ4kT;MCk@#wZSi8!Tipu-AWrkIJe7X{2pr|_~?rmW=&G1efUfEmqj2s7G&QSC#q zXRH-E^empCC4phNd;&+mh5k@SUUCo#8L%gXvMM5|hA7-GBZwCu8xm-J3U2D6+*hFp zgd|y^N--u=9wPP>Y8XrdE=_Pey8uy) z;pryEEe^h;p=~UIZO;%bJ%p-dP%#^QSt*{^(f=DP3vPAV@mZe^=Ld+*OEf9*WB zgd>(dafj9d8Ga?kD6e72S5dS&Fph@s8*T90R@Uk)!piXwt6AX-Knsj?j!Aca6mw8aealnXTs)89Q{AdJKNuaO=5UYanHaSkrs%Ga-4!KHza*GGw3J{h=IC*K#kf^O!QJnQL zC=9@|w1!~8=M7R?O^`f6T#A{lVv$T}ih_Pi2c#J3guvx8Q%<%ga{zf> z#QMCJa?rC-=0(^{z@5m4n6sfu2_{sBnYofR0cjwC>nEt6Cg9{ea42J}xnQd|Q60;O zITfcB4rwUBlk@W?zRb=M$sT3{ma&Xk)J}-1A)Tff z2R8a<7gM!|jbk18-Z6H!Y@D<{56-F*3qD}-69HKQ!=e!6u2 z8-JMeKfL2Tob*2I|L%8>&))yuoz4euzuUe0Km7jj*_VH>b2$8iqn+RX)koq7zczf? z8*)NY7J3&JS$9oBb(hDvG{J0f5zF;8_+1YVk`K^&l0$yqNB4Jku-gw_K7{QY zfs!%8xQG4JpnjjRv%scZUq&SJxLU|q(OG%(2_UploNACyQaFnX7?ed)_yAHZMIm(I zq$xddDUTgV!1u0CS^n${=gN0!di5bH-7GaTVj1agAspZlMD)PHfR74HBFH3YHohRF z5Mze-=Y^UXg))a80hK60qX_gq3-TraIiRPA5$OpHorrO>2&oQoQeq1UQD#{RvdsJ; z!50a;9xwpVBOciTqg?bTE$8rX=wmHN5JYvFWfhl9o#PdsF&r$AIU-_7EjHu_f|7l{<3CS58dL@NW>FXpkl zucBKBaDG_=?Vf{LZd2OMAuop@D?pduf?iipW-f$4rz??)#T6Gg)<)6!4zVMv1_tx*k((q2q6qm8t z7+kK4N$w?*x2`br%%-)StT&~A<=l9_*4Ql=D2g1(s*3{oFb6#9od{gyfEqITEQde{ zAZkM(=gl$HXo} z6Rqj#yg|-h43N|+5CRdN5JO{47?zDv^#syl6{E2RpUp605z?p(PB+239ymXMo?RO1 z66BhN^nO-dnjmN#f!8wBb!Gk@nYFsbZXTyrmWG%>SREqF6+oT@ZYE{Lv5@Lx49Xe; zTR~SYp`7QjRZw6X5)%IeqbP+JmmsP<%ERn&0!|hfl#&R&9Kh3jP+%2s0A54)7N~ z^|yX-!^1!Nr@z6CBL+?<*qQ)Mn9VzT2T2BY^%0E%oIQUBB^ihYOBi=QMj*Q|mzS^r z2b26UX5tjNv`(SUp*S7Fu|}9~@G$B+oC6-ih(jR~a83vj^kf)268Oa!V!=gVxG*Oo zMQ(`XENcW}h>H^JfFUWLARe@^iixUafZG^=wI+}~9vfuP-J>m>Xdy0a^f6lu zAy$j1S&NW!9Q>e%z>lEiD=3>hxEu#rbYa^Gd@ZYA^w6Gi$SWSiR7J5ggG)*Ff?-Nt zMtaYs>wJVxfn#Lbv^N>ySO~DSJA-{AV&Op{tGB0uq@tjXFmQF;o(AaWrqJpGmYW&vYT$|{iRwLK<_xZv zrxS&!9_yfk3`1-Z74isG!omTEis)m=^Dw(SBFBR*_962{NSsY!#_RR#z@dQAI6-R1 z7|S9|!GnAnOj{g3`1r6+&>7m7{im4x2zr}{!CwN}*h^uEvRNJMFYv9+~0?Yy;&y#GmB@Q>Ih z*GB2?p_wk`e@6bf|Knf2SbI@u{-eM4{>?x7FaDdInER(*<=&g&z#vxPz@j5rHaVFzexi zTNdlaAw0*2H=7}hvv!GWZ4krD2+qC>k4<4?f;2dR;~dghU=Uh0R?9sibazlWiHJYciE0%`FwC7J{-a=|_s5%1Pe7ED^sAJQJzA}K6j z3#V8E;6g97~_-TBK_!bi{svSEBKA0e`H@=e?@-! zkNuyFtDpOG`lZTKf^1b%Z&PN8cPFLqfks}79CTpYJY?Ae6Dr7uWth1D8LY*f?G&BF|5u?8}IkBJj0` zC`BCjw2ja8soBrjTbPIQe#_?vklk;A9W{ z@dRAA1Erc#gL!DoN0d+D1vbnip07tJONQvqymT?$=P-@Bl+UVjQN^P)#OP!MRnH^J z3Z=#pq`(HhG{tOX2!E)<%DEJj0&s$iah->%@}zP(Ff!p}RMngeJ}$!CJVUj5h}k^} zQ)L-Ba|j{q!VQFZr7h3$;5`Kr)4&aR^eINTZ~}9DjOj<~kOL06s{`aIfn9JhRDyZG zyW={rtpv)!6cz)lgoETI6p96Og%QTK1s)cXSb!z~s{aw6gVV0ledkCTx6l@W4kiu$(Xb3#I$uX`g11!>2wDlT-T|r(+VNFAvQ2}zo5SfSa%LL9S zVl?AX(NFNc(nNM(7UK_KWD=vWhE$E9^%X=aN5hCQQ-!%@pf~n0?NzYM&oIay zSJMaYl%b{?X@0_({4pRJkh$|TbS+k5W$?WSzMj&s<*{HG!?+`(RpLo$%PjPL%n|}0 zF$60ioRN-4hgt87hDJUHKTPNDXjh#j{!|M9nK+z($`aQESIE*!6qgfr4~*6|bf=JojS zG)@v>%<8odaqmqIMRl9B)dn|HAw2oov&9RaGb*>f>UrP(2futby!-cp_0|#Rj+-1i zZDPA}3&G_nt{s%Ix^IE6Yj|(*Gg#Q4g74kO_byLSmzVIV4;L`J;$o*VL|r1};wGHv zCc3wV=(z^`c*5q*pZ{O4yYK(X{{Q~$fBItNBrINB!PcfqG~tLF6dB4MhN_D)88ACV zeCuWnWAhL~?IF9$mgsU`!eP`#42Fg4d+Z_dRDQXL5xSUt_%VCZ<4~v$h)Oy>w2F9l zb^U>J$Mu;eH>u_*XfBH|+Pjz>GCT^_P-`)yt!#H(qS~N~hLEz36C!Q8m>!%* zEi*R{ju8rdGMdXQIwJJW-=%4L8|K7j)jJ*Zie>Z*_Po!!nr|WMS;*aWV3%J)`K}6W z@dQW75Z$_qm0%I=BNa!585Po)F;|9vnZxxS!@?wn+AZOMH^xGvi1S(wedQQuiU>Xi z76TjZcmcLIBklYMCxXI?~gm&!V`m;wQ9mniv{=0J+TxinoJR@TDdn#LKJ%D#%%4YA>knZfU=|zbx z{Ope^?XADAH@P*byaH};tLvHXyc6B+PUFMp(Z9#NTt7|xJaocZ@h94O`@Q1pNW?Hq)t4E=!!wU$-d z=E#m@OjmNO#SKB%Wefu%z2zY`chMQCtX5hCKdnPP%jyaC;bz@YQX#Wrz?C>m6CcY? zfM_P5@F-%@`53*07O6Kp@LUK@N-!1mtPYoH8HO{r0Bd&!EfUB~8DoownAYnkTZOs0 z&@Z?!Gy%d$gYTWdYdYZ0mk{4g5DSEysAA#}k;zckQq25>xdOp<1Pmp@MLP!H;IXiG zf|Exnj%rIlF+pp@!M7cV^ESN#gd~EWkzK+(LU#x_eLB~YSl_Q8=}f3q^4KhC!e$aQ zJ%r^cNM=XyH3lK8on;~dm*x${a@L)`*~^YnL}39^BddLhP;gYR{0O$fV`dd$j{C5F z#DjONp>aEe)(S9btm3f4WBWLP%QL+Dm49=>p$Kj2~(%%|SyFoZJpL2(y% zk^q%ypWNAmgzgedX@a3J#4#&E_GM_dJ)HXcxK(yw#9I(!8w1NhEHmU~38Nto^DZEm zE>c~Cz%!hH>5cvT_FZexc$q=J$4>0uD~5YO4rTfsW|ev02AVd6b{?rJ zp|otFZYSu+buhDuygWn2?<3J3q8|oGdb|b0_e-2IPJLxmZM4XGq69MmcBBc4%2CE*KFc zL4e)OY7W!6zkp9AjI=5QuY!RWp;P5hsHJ%IeVgenQB&NUcL8@&5uX%&R@mlgyD&j- zGDF9bQ8@DuaXwPn#j=$muPUT*CPZ0-GV~BkvmWUf@mUOaR)-U3CN~wcdjkBaj7ibK zanXVs#gKSHck?bz2NUE*Pa)>EF>L~6e@Iy!bkNGC=!n!AsBV~;)LO6w2b#pe6htsZ zL7=J7wFpe-K?@Po{4o||6|I7afhofkW4Ig#sujU=9q_XdzGqO{>VfA@;LM)~4qTSN zdcH;IUxIPBLdN{zqTZs{{_o#w>aA__SN_v~dib?BfAuV#eGt0t-T3~{hA>UB z^qeNtKXXNDy?ox-T6*1l{>MJ8uf2LnE?-`d&Rtqp3vno4|5v|!`i;N;4|kil|1i1m z!bG@rv5I)*GC^b*mhsCi^nIiYUI3)bf{l^l_dL!_YE~?vCp_I1>xWqmLG>w4=K3Bqjj~0LLlMbT?^B@DGToQz*{2Q&|O-Ggh0w} zs2kMuh`l3qaGEzsLX+g8N$Wxd+u)gD%A2 zYX%kTDP`RRxRe$tcXmlvxy&C=Y>r>WL!dA7wo^2~J4E+Pxmk(-dD88IBh#P%8If9X>$s zbOyuB-mg5|BMt8-%jk-Q`Js760SZG816QU8#TwRLX>rR-KHuy9Zft+^*S-7qzU7J6 zZbjyyo7~rVTKvh2Lgi=w9btKS8{@b3lU^_c?*a~&V%#W@t{ar4v-t7^^?<=VjIDK9OtD*o(om73>*hztq9vbf&0)Uxf3&nNBD%xctJT7!w#MJ9r8wPxYsl|o`~6Mj2so94=NOf zMaUeXkgc6@9VI%;)^YHyEX~n?t*j!hpP*Uc;o$-XoPuBwV&jm|zcXK}5Q{0FH(j>Ey!Mu2cyb{Bn2*{N8r!Xh}VfN_hE3{05Q z>u|1yI1WO#wp%3eVwv16gPHg0nD&n;d|}FjWD4zVf@!p2ISm|cC0LcZPB}6O zTB&5e!5-Nu_LnUBoRU@BrZ`i0W~m9L_h-miCd`W*Y;y;`vjEJ_<8bu=_8D+Bm9Q`a zj#pf$`vL;_7{~qutNycdRcSCBL1iOEOH-)+3W6~YCVFIqDjTLnq%#|p@&GF3F}cGK zXFjGU2TX7^m|_d3F;M0M$ngYkn|YkJ0L5m=@iESOBJ$!GM;k)c{)0k)gx;(S%IC0b z&S1wOtb-CZpFY90|9&qi=6_Q7{2%;MZ8`)${%8MQ_g3;N;U_}GZ4b{eEqMgxR-aXe zYj7@Ya)*Jzi3bYDy=oHQd%#vd88EByWO`RmSk!wX{VY3zL=Eo9I8UADN+`bxQVkE2 z^8wVmc~&|R313X`2DgvgA2D2x^4Kl#xYU<0=<|5*#a$Rb#O&E%Z-9B*h_upWy zoAuuPe-wuQ#n<6{hw=ZbNc>O!u4Xjx(lalR&P`w)i>MqZ2)1(Ymqv)+9FyD*SQ0HD zq!got9>{M(=l7xD0i4}u5LS3-PreW7otTNkHimz>P5dVhaQSwRxt|Ad$2|5A72I|l z7M{%8sgLAA4smq?IzPkR@)Uo5w~p&~mhhG7IY`f^sGolq=KEj4xUdHC+%r($*+-Q# zAYPc_c2z<7qb^7}kHNwrcuT?BR~N7#b#b$qu*1)^NF4#Q?|9hy{51?S?~lERl{+eO zd#l(}6u7>FdYK_tJwvfXIKU7bYe6wROtcY_dpWeuOhg+!cx4eH<#1LwK-w44dRWB; zA*Ru1&RDOnAVlW%Nx<({kyh`+%S;aZ6XcZ`Qn8CfYcg%9AcG*)M#qe456I0e!n$+; zc148$|2)8=8)5I&5+?Z>o;faqk5ZhhM`-Se;N%kaFCOCjpn=vsLbsHIb#aVy!8^?Q zr5U^3H)*;sW2KWkTiE_lZtvg*hV46K{P7>>R@N?3@Z~hsv~NLrPeO8-XJ=OrKxv73 zg(>S+B`E$fuKM@Mo|>%LmvHtHA%1d*(whMW-Xi$zedOId#WR6L0>dB_V22u(#3`LN zBxp=!mHrgTzKP;WjG-EnI29T38ghaNp$Xi5cm!ioM0HaI8z0fwFEDMNfx-xQB8GTo zk+G+<>Cy%8x`i}4qNH1bnhP11WGM~-kBk#kcnM~>ideXhzB0mcrGnlK6O*Zgb1(HV zRb>ie28FxB#3)NGl@R9~M44*g9g`WZfH9R(F@YfOBDOW8{yCW5w-|4#G)z{YA&*=s z#4%(fcR^;uO4YtdF0atGUtknxE3pDbCn6gD1YILU(&LaC1ivjn76AR!1$7j#^D*|~ z5-c}?iYbbD1zYhUPQ?+Fa0LZ{fyE376~HS)%$h@RLWM>`ovFS9dDw%~N-(Zeu(6lN zkrBXTQQuBd>|1;hm@n~4FP?}GjMuf6+&Qy%{Ium27=(>NqoL+JM` zNI4A;7mL_P3h)ms9Fb3EA%)zLkj4>~rU~NkkOqrBMR^sQ4{B&0GV16O?X^Wx9;&1{ zOHf6P_C<-z%#;{Lh?9Jl^C7NwzX|1lN7C0wY^LaV3*f}8zIh4*IVdEO8p5zZd(G8M&`jnO(ijOi#DQ<7tf%mSh-j2#k#|#wVWy23r_|eACfq;fwLX zM}xr2#R6XjT@32dw3wMTJ=1$tb#-M`?vYDmMr7>E-$WUVF9z!(V_d&e9D_Lg#J0(4Pmz4LG+`G41{K<_E zx#^nc;`(oj@816&AI%JoORUW!mLhQ;L**Z4ZX`F3)bMbF&+0}nEWZK7XwJbj)eY> zO844uNzz>|+3!gnrb6!c#Tfd8(Dp#Q=1e-cMKtd=LJx0;ky z_GrOJP)q07Mj?e2l?g?T`286IX$coH^jvJ2Xh`aP$oEs|zK`s%0AVkr!AlNDMM5=(yphpcu>c7$XNHf3$dqTlHQ}_XYW8f0VM|>D!bFXg+2~32q;b(Hyklyfa7rt2_;YHU-Bew)sg7nOn@iAr|&qa4tHK zV;%@C%sT{gv&6vXFIDo|Z40VdBsR$?vNvd?HFz0E%bPAq2P#$GI5bmSI-Xat4C?4! zV>Ipzp&n}x0s#{>#xB;WLJ6JK651wRXlX=AWlnQ9*ZQawi7}NEhU8#HqXUuBN=Ey| z^W1lVOtnPiT^pMNfAk2LeFMpQ1wF;f*iCPLaAtRB^sh|c(Itum`nTQBtl?R3f3C@ND zetFr++@M0mvycY0m`=qe^^S_v;TB}NI@#+Uvd3#EazePtk?2mT?%J@$n@Ed9sW3n( z4T1duGC{*Q%|S`$aYUIO26DO^er>MpE?NOV4@T=ehMbV?yo!o9{Cd+2#C1)~PCx`s{1 zAvV2Kr`CokI<**`W>$D`+u#N`ybHY!Gl!qf0J*1^IQBEfB$E(clZyf z@ZledH@n{xrk{N`JX$}>wt>QV@@KI00PSglp-oWUuS0x&7vifGJjP-Dett0QP!3dhbD&rb z!FV2u%Ao6j=W>uv3eZ#owaE;;w!l`nj;&&`ursEvB|&r?jQ4poHwiQ|PZRP{SQ?0A z39g(#*oN47Jma+ljWytTXPBQDnB7(|8m*ar`VH=#AN)Xh`maxdSKt4xEeOx)Gi}4s zg5W;oQ9r$a+qLo2TPd~=_HoK07XHbA`rmfxH~#MT=-PCjUfunK%o{xStEUGPF^Nuu zHkeUB#LH+zDf}{rI7>+0F)R#=X_`gtX@v5&4yDwCzgNI6iXhq%qDn4hP%qWv-f~OF zKbo+>&4rLZSI6P!B8(VTyB(^0`Lf81OAJy$fLF*6jtR_EA*c)`(x8Y(IM)}L?;1#j z+$=1E_A4z|*-eB$^_gqC;GGr?iw&&4&{%Xrx<}4s#dhxW}#Ow$G@#CR#o5 zu~x?r%l9C*bK$Fv)GOlEv)jalYijy+ygm64#WbZUJICBxqb1*B${ zWXsXmxd~Y?SQ86OA_D>}1j!Vvmy&;QfX;XUc|X8|TO};K0g_iS8@^F-7He!-o1yl# z5gqVPv3q`u#U}+Elo&ahhzTt08D&V~3MbpgtmmAv`n@9AHyY&~b>g-hB*jAzsd!U9WS#b$>ZKZ#uS?MSG0eR(N^yqxgooY`plkpX zZbITyWR8z05+M3D+-^9au89s4u!w6oUI1Q$;3m%UQ=}AguPmLcy>0yEF4_s!sKgj)@3wBhrIC?gQGEf zI6uR5I>L73U^807o<-!&&e0JkkW)b2gjiS4VQrddof8E@%vNg~0t42O4rjhYYHyIb zWwdM!Cathri-?~)SW8dQ+!G->HL!d=SQ}$?gW+r!K;80CJMZU%Io60cD8)JWNuF}0 zg3ld-*)7cFD*Vz4YQ9MvDiiYU zvU!NiGf;>mWUn3AT8c%!wwg*%Azx+!6}|kd*TGnBglD2%GH}ci2$>5*tU)b==!XXC zR6;FT!`K+mRUfRx5ER=~sO^}=b_iV^s%WCZo0!e&*u0X_ER``!cbLZ`9C!xWXI+rJ zAS>9RWr6+iAN0eWS0w zu8C5VmqdWYg#`cr2+~qw$^ZZ;(!XazXvlx}EbJt3005TPN>o(QMOjjWSXx|^lZA(q zlYy0y1pttW%2n~uRPn$PeA&4g_!$`(Tc2(l1Ry25B2h^zA0`*ZCJ6`M0z<*5rlxH~ z7q0}xtWG0wBaIFTF5hb<78k1-p=HGPE1F&05d7?|GuRcn@ymbUJKfp!+I0a~f{>6p zVOD}B(xgd~efF$7-NV=#BNYfkg06ww0oRk~sQWAdfx-rie0&SLcweFEV1d*-8a1GU z>$bq}f{An~Gk_E~fEzk=-4{Sk1YmVGLlyVM2V}r4VBn9?w6ik`f&i8k?|#ktZj|NB zZmA4FWEz72D%+dH5@{6gej@@IUcjy$azwkIZg?K`AWHO9q7BZf`B%2p?q91i| z-(Q4_q+#PC6^c_>jV5A)x=Gw&)6=MMVysGO84Rf3RA}F3>jrmTwIG2??;sfuH9tzy zVb*5115Fe`WVT8iKRtFu{;(9Rb!+y_&$@iW`KH3^Q@Wof)8LhyQfMgERss9OCW{l?MM22~A)`oE1rE9IHwC3=NeT1tcYrB1cUi zC!vYNP9mF3{=7nz*HeI(up&XZs&{5&Im!_Mso6dTja5;YBSV`IS$q1KzqM%VPi zHYis^+6-?rFkaDeMhXn<>_Kxw#>X`ccI<;XHaYojiEP1cN$5h{0BRvtqq?H;2ICF| z_s%`-x+!)rh$0h)%Jy9DA%Mysg1&5D^u0tv!2#05$eQ3P!E7Xf$O=+q^c1$_SLEy{ z@+fc6L!mIFN#)YbC7O>SD_KHIj;5Ghc}Dq0F;AsJ z6|54DBbc_RwkS;rNoiIkqTIpKnjH=|JxwZQk#qieQGVWjA#d^A6|Iv>Ac(Qpp=fn} zcJ6lGfR5!?bt-5o_)of2+EnddwbTM?lyrD>J~Xo``bD~xzG593uTijCBVu7ygDP5u z$`#J4$DI?Qw4%%M9I_lLZpGF;7ZA%4)?yrJ90nXg+Pxe4Eo|09@UcdJ_E>?j9I@J? zTBFb@{p@Cttcw}qQw|vdQ%-IiPv;jb7con8%L!FTjm&8_D)%c$mZ+C37tU5atHxIzmt|MCiq(t6F3(t5;Gg zrYh`JURB`A2=lyU@RnQW;+OO*do;Rqd_*KQ#tbBjRBBx$PNNuQR#mvUb~t-dyc5GVBs9=1d(|6OI3{$Z~F( zuNiUM|F%H4Zk{S1I7?$$&oIfc?jCBN1g1t+NLP>Zrl_Yxl;V~KmCDHC$=+tnPxDV< zW-Vvvu~B8XOf61(WEr#yGvG5QGte@4GbqVW$s`@iPxe{?tr!=F7p+V6+KRNiw2n17 zG!e9#szs|GseH?Y^q*K8Zk8($4CEwhbuYIae^ zQl4bon4f~ELeQz;tP+z;9eZ7fzCw>(Psz^oPF;KL*725#U`9fpLZL!JUDmDbF6^$4 zKcqj6KZ5_^SNxaErvk(tSTI;CxGvHX%n{TIL_8D^6a&%)d?|z^ga-I7QUi2ScymNi z;g3Qc(c3B3Jc_(!Tu7rJBb}j}@a%9V_;0~rWE4UroO|L0MrSQk4RkVVe^tMwNz2=_ zgR{-1Y4b@7k74RD^3kP{?&zl|hA4vArYIdk4;p?eOs&_TuOcvnkk{kUcZMyBu_Nx7=I5U+q zk+a&t(jkdi!HCLqp>NyZIdm{j;V;vxAFVTCu+bnJuzq1CI@yzUs})qOSzlyQvOn>W zN>=ruL7*w8mD~Fk!N1v^+>K>pyxM$vc~mz+q<`7hS}0s0tnKKRyV-g1)c#cTB!Gv{ z`O5*QNKM_XX{w{D{b)}Xa5z$T)l2(+aaejJCom#E(#46!8N-ESd%xyfAl70kJ$|<` zSHrNmwh7zTvnCku9=32^vdl-#cfItJkJrV=&+Q@;>qog(OCJ zR_#(-Rkd2nWG{?&gkS=NhNS;BdYauTQ8g+cS6x~p>L}%ZHs2<_i-?aXxaAb;^823e z@U}7wXF7~QYVsiMer0K8pcUBKTl_rmmb1#k`RjsEkkKgj?MTbq$D&y1a#VuZjfa9U}!P5X< zFdmYF`IfIc-Ra8FwVKDB2kdR-7DG>&U)_o115q|)E@T4IE4?(gJ z?ntOWh?-y-ug1sn`)(~`ckNixg)ojkjX%#<`L5|=R!w0#&;KRnlxh3W>5y#p_pIPo z=Y7Y?!zWW|-&qE9e)|jS!|_qo;A&PKQuluMxi{XsyDRGp!M)zP&%?_#QLxa~YsTyS zp~Fk)!}~~il*qqg62?(V%LM>{L;KGK0?5k21_073rNw@zdgfgBK;@82x(R(<-;6i$ z>}>0=h@Z>z9)}_)CyK>WM%(tU1+rk{M0WT;%0#_w;OciC(>1x^=N_FE6Xr=_5j(AmJHdYv8TlTuZ3Ts*`80 z5~ta+O=Un}1GWyay>RHF`(<{+9g>i~{Z8Y@%?!XYic; zT#t51qF36$Sukp*@Vh&Am+g{U)>Ylc6-ylmvb10w20#nz9`D}>Mx91(`T^AcZ#mkA z(D4o#2UKaHD6{=7la6CZgFKF7{-;r!-$a1{`G=NGgAfw4Y2Wqo0W%%utCa2J^uNl& z>g&N}{%d_*!ogyVI1=#vsA4Qzpa2KmHm z6T+SN|2h#&!OaoG4@nv8iiZbzl`B-Sp5XUg0}$LiL#*1@41X&p)zR#B@uyzm1{e60uMGm3*R$VwQE?-cpuK$Zk8M-Pgvk#X_ z(Xh+*d=D3ZyRsJ+-Hdr-)mOm%&1D}`)$r(l67Vk#AO68Ze*xnV67N~x^L_JS5p7zV z2F+n`0!q9m$yLVxojrRm*zhDs*qGJVOdCI)MKnF7vZ`jj>(`qw?45jRxSjv|o*|6z zf4*iudrr*rLp|#`G-6fjlF1QkXpkR+|_gi&d{n zd_$b(7_URF{M10J;#BanWneq9bDuFbjrJgI^46WSpIJ|Jf|6M-Zu~4|E`$I~YF&z5 zV}Icm?p0SCN;@I5vwVRqyGrW!Ran56D?YUnTPuXNZ5S6z#62aU5XXBn_)I**9V4K2 zpxvQG)iCp51C5nw18pNgx0{90+**o#d2gY+cr@|5N_N7|WF1|@GhYHdp-L(fsN)Xkk z6$~221mtYQ;H+qr-`}p3ma}K{Wj2viTM%|#rpWfH^gq6f96#42(Oo!wd(9~EHOrD2 z75)aL26lW*HC-od<4JqAk6IegW$ES$JK7q(w41(jv(n(ngBi1G5c5}b^s6q1USpT5 zG91OQ;O9yeux6o#lH4$p#f-%hB;iXagXwU|lBAT*m`V_^@?gNd5ZDHTMSSbq7Jyy< zV$j5_HyO*Y?3#em=^Axr7EJ9QFuL&VbaZj9q$GQew?hj&UJ_Uh=#9yZXr#tqz>W$- zlh2KgdaC+s=}^;8A<_si+@y@gfa@@Z|1^P7l{988TnEXjgp&_Efr~fkXV%T>a09(> zSCRZ}H7oPVO~{iImQ=4G1&t;!#Hb}jL6Fnn^ea;;*OS17nLTZ|-!eMD!FA@$kCERG zl_3-N>hL$*7^wQx$oxGyA%WERgYCiNviPH0nqf+?3+h00*BO!ALBkh2eUVACIt84K zI{MtQzP%?TG!|?aw>wg)_;J5iFXa5G?cl&D8>Qil^Ue!WDGLvQL;KhmJ+msjVKlfI z+WibHr`?p1j{%5ITKe3&vIM6%yB>d)Hd_)MB{Og4@X#j>|3?16;U|tN)S>Ve=A)4R z$LU%{hUKh!!&h^Kly3f*&EF124F>cHOo=ko3_^v$3Rsdf@B+IM|rLeUNzXXm&cXfXIT&or0;q# z316;T5_J6pE@8=!Z3?#Fs5>|f#DcdpkPE&&OWq%xUPDPNz_FKyvF^(W#)Fx_T;WR{ zet|Kx`)R=WH`T!`7sEJ3>Qpk9JO{8AsIw%=t^;2U1Onric>#oTN1C<#fNP z5{wVEOhC&N&|TA<4*$8(9k2muT4g)!bBp(~pUPDHBAwgrB{owN`Te@P=(sJEGjbYP zz?m~>@VzhJ{ff~QlqCD;cTK_XdkSkCu**XnjGkWxFqqWR>?@4*5%Lt8(+2!hu16Hr zz+npb?f{M=sgp3C@-Y3|W#BNGlR}sEN7xt%23%%v22?l|j5jCn=X61&V8{!DBBL97 zlN8CEpw$|Gkvr`cQf@tK;`MqsVA=bZ%TYrR9Get|;Hz#miRj1vn{u!+S>j7f% z2dj>VhYia1rELxtSZ#4b8Jee|0i1nz7o0(dACCKtEo3ss@J6NWJ+GBW=-|-ZJC?Dq z21>s76Jd`0aHAzjo-1a;3N~X-Av+^)0K9|eJ{q6{AILA+^?U+KvG9l$%{YZ&4LNZI znH-Sv9!mea1&u#Jidk{~lrpG!8D}=o4m!*2BLT}h)1*IkkOzXJxKPblKB17K%#TQ} zxT83jtM?J0AD|}G>VSgqNTwyOy zlJ~A7|7riBjo!qp|B9BxeEJX`&o#mQE8ZtAjP8%D`g|5mv0Fz7f(4Ifn$2FW8JsAX z*2h&LqVGez{+6Q#R;39gTvrq@$|cFCHbxUt!sWIUTbY3_Ruj~oBOwLkNU}Jj!_oYQ zA3j{-4mR(b#MWpS7Si5e4CH;djrV=)tnH{kLUSXz0wu7+Hdtua+t@hv_gt43JkeXo zCvZ{0J}9@QA-oe?vG}P`?&ICf$IunakZ4?tld;K~l7|g*Wmhn1csU*3WK4_9QBq~$ zc&R^@CsWv54bh?77n$g5!MlB04SVc|?njUx1BW%!2@<6+WLEdwiPiU?5AT)CA@0j= zlJ55~sJjxK^h2~=tq_5(te|*Q)T2>t(`i9iTDH9+o?oMB4^a0vr-Y+py^VJHpAGhdZ zf0i3IYP13)hBA#2X9RAkXL<~g9lXrB1n-s+fICb+idMD6wFkQKAo#fXXLLOe!8rjO z;Sf@Kd8c-rXXn$0sbz9|sjGy8dPuJOXk66;T=v&LMjTNti6MaC`(>B?kt08xL#&1u zYnUsXR%rI7^u&lwa`jpakxKUCDIDiVK7mhEH^VVZc)|qI{!N2BaQ7Sm zL?8MN#{u6r7g?+uN7&g8U*y^DH|DLvB^a6H1~bWLp{`0IDUE&An#|Lm-*lP4L%O%5 zbDCm_0r@^rVenvjhG$LK8DZQCRR{;K5qo}MUEk=teiIV4vh4K1)x$jit*JWPf+ja_DpP^r7bn#n9CdKL*mdZeY!?5$r2bt>0`IzGr$bhoyaeP(5}W zs!)rv00kQU{GX&f&bZ$a?V8br>N@bgk;Q&yC`29hNQ&$Ue0N?j{@;NZz+xO*p_)Lx z@7-L_5x5u7L#MUkb3@V*kw90jwUA(x@A)eCgXe_pFtr{t)r3+7yA9LG0(&27u-LJ? zEgPhI)Q7)Sko)kZN)?L4PcT`LMk5M_q^lo+oEtxv4O`R=IcEPZs)nUj4E$VUwjety zh06{u$odJq&><4%zbueASv`bkgpK{}IB)jp`N{ScM%fw&J-#o0DBXPv5mEnKZN&YE zNCmx5Bb*`|=+Ng3IAiR$LTAS)f#_oVdaNW9PMHP?=vx$SXUh%T%pX{+;}6~an9N=4 zE{)uns}T3q%)pU85TE6ZEHmJoa)N>55rRz?V+=~@GbYkrRp>7yK0u@9o5N|F3VSbX z$xOAM0v-GNCS#n&Ez>f<&d6;7+xG^{U2Atkf8MWljG1y`^87YNq@P52=N>!VFoT;( zqMs3PNUWL5UcuCY;ZB`#B*(5rCXF{uvS&E3A?k&@^;-WCk5=fJghnRZezR5nEe-w? z4wrDoxDz`Yg~hT5l?6)foHk3llG$6Peu7f>r-#*1Nb!C6f@Yryc3qD(ApiZDHn6Ba zfh(@ee6SK5IPBJSAK>9`WKG-4Jdi@}6;D-f{=okAM)A(g95=?V#2BLsKe=*zUs;Ce z=>L$zVV6auMeiQFm*paPzi8n0@I~Lc_Vc`%1-9{me!5%ARN1f(Q`{yK-}3_1C<z*mLON#f5VahN9zF?S?K`AD zna0daw)&z1^ZufKqru6Jx5_xsv^F)dyOR_M>SAN+Fu6;Y_H&{e5g7->XJL2q6S@04 z)h{w}AA@5}JVbPjo5fIs7-d#7!xA}Ic`{s@AyR7n>f2_Rj}M}oL9N?vWU^xEVZO;R zzi_<`ooMMZnrK!KwjkKyvd@wi8m*===Oh4op7F?Qae$LhO1*-wAHvmfn0QRf;{Gp8 zLTbff%gX(be4T{ZuX3cQcxRK)B3I2Jao(G~*d5pzAv@T*t_$c^Tf8uiG_e|MXM11l zKl!EuBW_rT`z}J-<3W)Phcywxv1a^H&vA!9;N;8xbUrtjyUKO@<<#1dVXY?cMdM1; zS1X=k7L9_Usen1PpQz`ESh=cfFZr7R)H1HPsOFqlvx0TU?+NAO@tM#c%Owc`*<1zV z9kF>Yptm>3h67nJEC@U>_PB`b+EB{|!=@`{Z7n@wStn2&-<^NFffb>JnD^lm=dm`s zUqR>&;NJc2`>XV@2zjBRpnuLEzO4Q$hot*f9O`a=)-JGzGC;Ros%tWAoPKYyZXL{& z?h2AW2{${n=3rCEAS!=*GfGp%?#I!o?80aWRF~y-=Na2m|@7!BIR)B??>{ybu^Ih?a zKww($dFFZMM+UeND)u#*9B{g)r`^s04KbmFyC=y~!KE^sLrEMlM-65rvI23*c<_^WWm`Hb@hrQot{wo;rptOw`>1F~%D=eoCaaRT1uxERok-H@1 z$s0AIK4=WEfQEw5o&l(r-T)No|IpTb1BUEaY7eShPqTbL=~RIlrf zh(c-Kek*+AiYGo;-}J`wn@g zr#WC?o22RA+G&m>+FFfb@^uoJYZB(LhPG%@Bj2Diwrk|@J#Dr3J&o{-tAXZCT**){ zTx|5IHyf*$%8bhju)**Unh))J2XY2htGa+Ji0IHtxhnlAR{?K`Up?j^7z_9uA^W%4 zAJOf@;06?78UG~g=kqTS13x&Wj@&zaKb`spaK2omHpf;ZNtx#$S>yVp*6gS1fvfL)vk3C~R=z4z5kA~@6V`^v7TFR-h?9(eM z;Vwu$IHmc1Up{p?&UDS5X28;>3K*Q&aclyQs@zos(Q}*+hEZ&JZU3EgCt(rwwv!ou zZlFQ5P$J8Boo-okdi?RvL-o?NC6<||dqH>H)P(dsc5&*rCl1s zha%0D))PbXwxQV8KBedc-Ast`{Pv;0&fU74Ml;F!9Z}sGHed%LT*>1!`u1RSzq1Lq zTz#;NsS3CkbpzR1eP}^!%n9_m8#4@BA%b8IFYH^AU>x+xG5SH#o4sb%$-Y?;Mr3!J878~uHwz?6+j1q zaGvJbYkeo6^`C;NfLrXtgsAv`P?wa4R{LCVzdqpb<^za_g3-0QjTv%&X%Pi#aopYY z((gR&nSYEayxlQ5Y(!ZY_#m%n2J3kxS!6u>@ke>|*)sL|TX5ZYHAARdczwaIVX*1! zstoU4a39z$;~b82b560eOU!u$EXUn`bz=p52iV*PrC*Iz8MGrc{6fe+h%TC8s5!TU ztx!_|Ug5d#zY_7nadb@_pJT!KkCCn7f@RLEJE*bVjp(E|WuTk2ninK*PgM6LvL^;p zMJ#Z?FMxc^yU>(4`=h+NA}y-`Cr^n6!(GB(U(hPf)o2ijFZXgai1u5eC#*QLXwQgb z4qu5j<0X+eTt=lm8D8n-M(-yk-x>~@@vkayWTU8%En!*E=yerYO1PI#4731Qw7>x- zZ^s)x#=+IzF2b`)$C^Yb{G?3m$aUap`t_l8aha+ibj@Bqkm{ z`QwjFzVLfE45c}huA^q~uGJoV^RJiyzgK-?eY8``Xhg+&-%?0+9^j;c{TSVsJJj3Q zLB0BECd#6h9r8p!Mfu@1h9=#^+G75&%Z>-4;B#0F0K;8o$}zm6S4IbgsF>|4t7zvB z3?N23QIjz}n~H*GM<=+UyWb^Xde>oy?)!wl06#+9i4_4IwX}|mhX3}0%yS})%u(Xp zmT@OXf#jm~&Tx*j%m(}TgynwplTx-oHLB1V9;Md>0`Q@&r>i8TEA+Z^pe8!q+O~%-zrC^pRtiLcB&U%nt84-BE*&OU#e4Z(HLk zS5f_boS!thPWQx&0v_lyq|1_-7^d`MMa7`>OnWw5&-)uM`ADh@qbZj9Tu}kN_Cz*z zSGU<@OMg^UqW2998jzwec(}Jlt~I%9Wks{8nEz%%Lh+I+p_NpK_9uU6!hSzZnh9Hg z7psuS@I*6G*ZnbYF76vb-)Pz~TS8(>K+pnfT3)qj~SJKQl~3Xz^)L`eHZ z_8U#D`?x~#)%E@>msYrRI*ENHhbI=P8wgn4;!ZoTG=(iC9#_zBOOIk%W#^IDAF^Kh zbb|3`3Zy$64QxyLEByF72rs+~{t^8?CBJ$!qPHI8jDa}GdMnX}lDIR!fIcf8b?1#J z+iA8gedxDlibS|2YNO7C=j1V1QSi02nAR#pdI6`#>D{7E*Zqn@?f|1N+e%=4ePeq6 z@+qRpaXOP)9B@waO3^k;4zGj9__8LKSRD$rR7& zhv&nE7|A_HaVZb`VSnzpDn^3Qn0#@s?s2b?_UX;)sbB?Ai(H>KPV6dJ?(Qxau8-1mymql5zD(hlQm5|c#^R}d`Jnnhtth1TUb=o8p*EZhd1pg2 z^0_YA5vSu;mTJuu2W+Q+#z3>MDDZ#vyHCUYBh9{O?&RBKWoccHHy~Yi1<4~%jYEM# zW(qaOv*4lL+YeF0p2&pXHq^(wHTuF3)8T7D0+aP%EK`3fP3-4&4Zz`JPy*4mC3zk` z!|KWvepbK-onbPjUcp&SH@zBpxFQ|vj%ZgaZqt7rDrC_YPgmi*VjH6S>`Li|;pj^c z4oSB!*SdN3S%sqmM$wHvXk#DVnE8I)LooP(2|HA@q=+nV(V{d3xK&5ZIH;ckKzoi* z5xAoje8|$HpPS>iApLz+TTtt)1(p9BHmD(snNL!;O%ptm;wE|oBz`G3K^qVeRD&BI z_Wd!!T3{R*sJJ*#X0JzyXep+nk9lAV7V!M&j~J?bN1GF)rcuxp8gc6|_Pw(JnVbOrp?d~hf(!(eB&+2! zY6S5DqbVgPI&@JMm?3I}6r_Q`TNKZ%4qI|KvdoGho<4;F!@=K+E$-mrf&*i67#LjE zp+dQ&iR?v-tF@^)pcA?r8W__tRF3X#`d4F=#lGL(_P;pj4dim*iI9Y^9DC{hu<%5* z>Wo34|46Jq>=EJgvOSms=na6-LZA9Q4G}k7I2sIs zqU@YRzneHTSwW4C@jDu~uOm1p*A6)2(6tUa0M*X>+cr|=Pi}mS@)9bg$+D->cDp9UvHa`w7__#6FVEcewRsuOnw%d3- zSOA~RqfQ`T?-+PfirblcbW3S~iO_oN5UI^%QfsK+Qw)-1x&?VG zv#KoVhPqhlygF_RUqO98D6&2&X5T@-5z3+K84wFuVMhBYi03k&=QJmdY9^V~)!;M> z+e<8VC6%U`G*%1ceP23jf6_nU)ndNfUypwj?ZjSU8xQ6v#l{+ZYjSJ?e7}6&yX-q3 z*i*ze_h~_->9FYc#22{yyR{bSoT(MKFj}-)_`JgB;a?ZUyWFqTMv4u({5EB2>5!t6{oxgUO|lk(Rp(4B~#pNfO--HpYW) z=*Z;sc4!LEQVl%M<~0#H^u944jG-)|6?+nF4mJt460`|zfx5(7W%kkS$x_uj9kc&y zi+RK#ooxCgt+bo>XG%rt^FCmQLtMAg&ghG)N8sF%=?(4oTmzrbQc^Gv zRDF-Rb8pd!fp>=lYn!{Vm-_8^qnfPk4dm#ul!z~g6~&Pe|5_+eeO|b=0jGY zs}wTEE;cyRQG@qt3uK+fI#NlkKA=q*^4N)YlCs&q%EN+R89k{n#iv@ zeh1O#jFZoi`lv9G59`UwlGi^-p)qQ5AROW8YP33PE2KjFjL`KNPf^H`%@Ua!HId9( z%N4oCBjt-nC6e9L+|?V^LuzH5(RHi@!)PzWJua5Mxnw?^H5F-Q%q^TG&vs_mBg{8o{9VQ7w@wEVIJ|ks%qBecYjm5z&n7kkG)6>#p+ztO4oZF zTK{e9)Ap~2D1NG36$3~2Y4+v);aJwZ%uO)Fuua}yPt>}A3FJ=BgrVGMXxn7aL8P0T zfxPW$-D#zK5qcYw4@XFYJ`)@pBqe+0_;08CptYU8$dP#EiY##utkP~AYX7<@K|)`*alX*) zVph=YcxK(<3Vr5W9+|%b88|`g%4>K>^}Mn zQoX|u;qiBg8kYmjar`_wh~zKXjMy6YNabkQKLAZDNaz@ZagBk$z8UJ_XGXTV&pc$6 zjJ_)3_P_@RL~5jOPt#cY2_a3{Ne67xxP_F0gnjRX!Sa!5e@~}#yhM6$Pu@|k`$Lfd z^T#jUQq@w@`x0p!?G82VC#l2_pKM{?we;7c~pgZcs*6^ie<&>NDf9@ARUG&5MjSWQA~< zd=2rOeL!+rw~b(@xxq;s-OTrZE;DdtZ?p)M&Z@RKs9ALYFQs=i#U&c{3To!%Km9KKA9&6Zc4F0b-W+1uN{VZL>z03nK4;>08$5=wFg7>frZho%junb z=M(CkTZ&Z|=GRMkQ}C>>1;I^U+u@qyKeXZy1d2qL^NIE;(6wTWn5FUy$(DWxN51nc z_X%DltBUtOvjoDs;tYf1!RCmkqvr)I<~|} zAtlY!>7ry=51n9LB=Qdq0tedjJ|+DwceswAE7L}~=`HA^jv?r}(!h>n_Pvoc)V6j7 zUP``Ds#rHuL_nFZ&jiKH$o*{HR>b244L2G|oB^b?I%JdQyT+)p8xHy%OIts1StaKMspMZrBN82^vnA%}M_SZB+h@*VkN+ood!6w=A$U zMr3(Vm1N&zAQlvF?dK`oVUab{3QnyNLuySPjp(#9OKJj{LW5SBa47_ciRH*}rF~@< zf5>v?bJR-Kfj1`2;^nWI);-MGOkBZ_Wx4jRG>kvZ(_7x@(8*>X=j|aYt_YXjaGnG4 zEc~~PAc6pNS1l?=ln35q@!j(wU>n!fsLj_o{8A&_l6*%`Y~Onyhv$gyT!8m7ioLBF5sdf>-Jdn!>7~a0nE-(c=c^^Jj z%QcxU{;%A-=c>1R2ch%BBBc{j)i+(_a-2V{s`aVL?dIOMze7TbVN}bEx7e?KgYNsf zK->Z+y!pQmiY*QDLZwy(P z=m&HU#Ccjt*lCw!WkBS_yfOH}p66gs(- zz>7F|1PjN-S&f)Z<_FW@mddEse|Tk`CDb#RKKWse&xA4hl^b#_S+mC~{6R0)Xe^6= zYNb&MPVY>%q%x?r6_)em*jye*ZexuPJwmiWv*|7m4T64mh2FNLqs+#U64%rxsb8_V zJ^@q#tMhp9Hu$dJ5F~;UmD`sX;^m@|9%RSkz zZQnka^nyQ1!@v)l=u?S^aA!Fb`$3zOry7zh9@f8Aj;!5BC^ds11vvk0zbY zAl6R13OXH&Eq95cDjx>H1+DQnm>%#B!A6t1u@00} z>Vpbxt${H@q4(v-@Sj_O$v>()EltJrxZ+MXQeu!3rl2;n*dsAa_yb)2-SC<#?H?E8 zpqP852kpLN;GOC!(W~$nf9d!3gV+_BQEd3eK{Uu!+tgXys6&LlZ{>i4P&fM`!*8dvJ5AQoziqCFg$-C@~3CjYH2 zZ!|5{Di(g^s*8kt1kxBpKqxDpVGsg zZ`Ms)9>iOf%&4p;*dmu@^t5UJ*8!r0B&(+<^T;|*U;bbS96QP&*DCTXp$)fQ*y6YS zw;Wa8>wc5d?pQ#GYALOD|Ala96LQ45Mt>C};h=%Q9Aa6G_m(|lywVxtep%nu!1tFS z!q*Q{2zKY?2LSHAy@;&y!q?vsejH)fz45;d;$(ups zK7#^ZH1ID!zOk>89?Lm=Dn0*cBN^a&OgEC@eywO^`$rrkdxS9^HDz!$;Vw{|DP8s? zBT5B&E%YM8^HT*f$TgKgNa^37LV7IW@A;M(%HK41xMJ@)JEXn9Vhqni6)4B?MMRhJ zePIOjb&iKJ3;X*%{M_=isk4l1gznX%gImj=aYvfw!aB7@j$joxf5-XRpk^}as;SlZmh2L7ztl9wjr{NnRykP;_MKS$A5$G-Qb;-GN>hSBwT+i5IZhGMD%v$?-gZk2+u+4H7j86yF zcnyJ1Xmy87RKKVx2;L!4>8mxC@KfELS*rsC5|yDNVN9ViHrXGeR5tuGe1bXxoSJF)U$c_lX86iGM93U;4CVfP!4ot-2%5Nf8B&MwP zb%urpm;s+ccw)VNVgNXsNBiNPX^i$EobEVwfklZ}Qd=zCNIF@{yGj|T`4%HkM2xU3 z2wl4wm$%Fz_BF8`)d9Y8lysvhn*Ikd0E~bds{>^qQ=e0rrQ~*bLiyiO9Wda#i_kJX%M{pH{#isk-pV@q(z0LI*OJzfDQ-pD2CiUT@ZjiZ zfM)MiF8VlVQ~s`>sw94;x55mLFWlqX&s1w@0!K>mw8Oh zC4eOgwsnp1fMtzyKPiMVy(Pn|7c>h~yC-rsmx5Elf;7~kcvv-Y2YK(~jHJ`dNaL48 z$n_y(Q7X5f+(;8XZFGnV?Aphs`sjOK2O?O4tFy#{ZuB2T99>w@&#F4R{<}hUV}|9F z2r8L7KDcU#)j)+WUmiG!I9xZBpPm2Uq0jY??r#L2zyWw#3RL1PFPLwPXa!uEeU*Sl zv{QY40M%Bt0+=@ z!hq`3kf?v$5>qHt8s5JnrC_Q0x8CaSaj@kKqo4=lj@-(Lwr|kmO{#Xvk=WsM_MTc) zM4_cHBtIVnw2!dA?_o%o9dP=N1Js-jcwm%8i);$$iSMIVG<$X$@Qz!;-0e?dAU3pW zV9P@|dQLqYh3LuCVE?0FvIPaR^0E}*86V+Tez!AL83ossiJ0fM+Td)!cFgAOdFZ;n z0pK~qWFKQzAUNOmj8VxgV-rG5VS<#)iX^D-{fl-c)nF>zx6Hr)=pI0V zWJZBMQ()%?Qs=EL#4IP5hpX$*Nu7p9jkdtZzE~6s^Dk<4RK39M7SGQr_d$Mq8%wFZ z#uduD6($D}Gy3?oXkR^t;IKg49vgg5s??$rK+zkqFt6orB|OzaN0Ps}=X;2yuj~8V z(3qIcnEC;)071_o>sZA=Y78+gu>zbmbVT6?QV)zwwz9*ke81<#@H>UN%{aCh{QYL_ zbn-9iEn+ORR|y-;o!7W0QjxA@o*Q$U7*JHKKEFxUkH^2M?I)Q~0BcW z8bHIdO4-Uc>c5;${181 zC96W;_r<$|7^wM1dMLgkWHbw_M@**&q}2l-E+!MMv3pBzgv-b|);KE1{q@84tB=C) zAA#h5uuFr!-$t#td6SQ#^B*9(Y>S$TqlG#ype>RVSC=|pPf-8-t2XeMh=wJ1whc$mKv?sH=k(elBK!70jbLDa#6WUe$l+pi);T(H4OgIB|V zq1#{r`cJC>Ugv!QF!o#Qw?u7GhL<3d36?!&BCsCF9`DSpZkT+0(ed0OSn_I*7ULONYBTdwteDi~fC)1ivF|e*8}eKxp8SBH`iu4Z84)W+e!=@exYpW!M*9 zlfaDMSAl8gW4}p!)8WF1*`R>mY-pIrPh8j4O2|4SlUIlm3z;_4^HNRnE{f=}P`ep9 zUvi$>f;ax!hVuUbeL#Z0@u7D=z{DjgP?lU+8OudS+QG8cD%N%vv9T`?tG6IFV>}7F zD$RtA7LpEbUmiQ}>BXBqyP1QONKic0ToyWzU=!;oW8dS=_|P}j<8R;o5R800K)`wL z+snx9Z^b*mzJ5X8Ye7;f>G?$q&pvw;$=8c|DhtKtGf5jid9WQ1JduT&vQMdmpC=Qr zBGp{QoBnGPF5NnTb!QGYE=orN1Z5WVXVBi0$NS&@5dQi_P58~uHr%$i35Um0m@ZOf zU>D7)8rF0b@zf2|IDg9ouq@9tDry5nXBrFte1=!$@!MbZ;V-T~4QMaHGK}NGb%z4L zT^IlO@;x|mWs>o!?i#8GWB_dm7v0S^R&|!KZdnf9eFc$XIT=T-KO-6^Hn95gS*9R= z)5OdF-*yZh%pl&EUv%Z=lolSyjAP_t_?wsP!@HhyaMn~IGGN6_2g$gD=5!UQwyG$d zI~7B1Ff9l{)Ou1T5=F(2rSXN^dpR|SY#i>QnT(70(vMc+%}*V~#ZNmVOvduvIIf|! zf`9zfX6$>U1=gzk@pVOWASz6<`OQz#W~;+w9BVgC;U$+IJgs6e=3Ea_cx=e#tPdzp)RX!*q;?fznCWub#sD&K{bX zZLy_FYMo@|s#tJGlA^E2Oaw>1khP+K!6({q&EM@nDQ_a)T{@+$4gsq|dl?`8&Kl0N z*|43ep!yXhEz;&PHr{jnMob<|A-3u`H8Gc}ojQz*wC5z`&ljkj_KU7Kj2AuUz{0j1 zPL*JN;#}PKKs(G7bqQU9#f!bEqBNAkGe3M5e*4dNqNO(ndoWamSApDOdolrIn%oOz zTzc7ITzVA+22h7dX_cm$IOOsrB_$t&O$rgo{WGBmq2!7@`geBV+5dPZT-!xFV;}b! zcBK3J^)KExdzDA!G9{MwgG+luRd z-NQl+*+`COI{b*X3cmi^E_`ff8@ks_0+Y!|!O?<)cV2x2*WbLHTSXshzA~BkIHmGP z({W68CM%Z%qpyGik9XqQ_nwD?N79H#bgn#Qfe3iEhU!2DfBdCQxas3#+zSROf4sSb z`+l_=pZ@+zpt}T<>w_*lF3xWt7cRB3FD`I8ONWDL5+F~JUItHUa16wIO4zxt30MF1 z`S|HS-i1~woqlu%*RrICT6$d=Brwv#B_4ybXN-o$L zHl%RO0{LP9(a81^n=bz1qdV}4Z?54!E!GLLdYTS!ow6T?~Er?J>dDG?oG`@7( zG9cT)G)y0kCvo;UBe>$cQP~8M^pIpuaDn>ZqVNki|cI{&akp3MRSE?*`Fn0Mty*X({86u3wM$erFA5o=|)U)&H0*8*>(l zP8s2D34W)5&?dI5fQR;GaN)Zy#Haq`alGQ$2VmJ1(Tj)!l^5t?q%fK;OggW&h0lCt zGv4uEn@}#Ah%Yb$i;4i~ zJ(CKMkl7(B->JQfU*56`4?fZgqjlkG7I3b2YZZGQZ^4i5?7=giy&ve0)dy>`^&x?0 zTs(+vXH4MX$D0xBJh6G#WM(($z>;4v;i5E{#h1Re2A}xO8tmEC%}DV>UfgQ0rmkkUe3UyE_v zb=NX{;)XT&#;rZ#j4m(m`kiQt*+~~3;*@$q{pJ_6{&_nLyl0D37()-_drbVtFO~ykSs88tw}=EMnl6q1%xeyDiX@_l1JzYn zmdAUZaRje@a2sr=BK+o3_~Ht1QF}4(lS%=ils09H(?LN@(+NEAU^i~Oy9-~reHnJ{ zY!<0dD+(e8 z%TUc(T#$}6_IaFPlT9WLD;JUYeoP=2O{JYu9~z4DBO$(QVQ3(WpZ%-@-@Kz2H{8_) zn8&Te`+(d?Flk?b)$dAcUtGaPdUC zcwE(xM-jlNXNxrIxhz_WnAAekg}FeS*6lcgGw9Xn9c6}7BpC8cF2MGP^y3+xwNQAV z;=^X5e*{#t={SThPl#P!z;waFKYw!#{_Um}c*a@dc+NQ^c*^EUY+IRQYk@(}BK%+h z%GFxK(vQg&3wJ7s`*yeEw#VA=y?eWG^FwW%eMhGM__E6UV_aMr5UJMUxQRYhi8A1n zHX!4!7(H{qANoAKM-t>{0J77Nr`L429OpOYD%V_2K6p0>_>X_K29JfRPE zi6)r91*`MOq->EEcbs6zEQ0B(iK=68@t9&IhRIwEqoWBSwGyJGY{as)W6B&5n`B_) zvH~(>rjD2|H&CjW*nKpEs%^~NMREav1RhFD-L$;GhdN3ECBY(}k7EzVH3$T?k`B&U zl}Cm8SjcwDb@#<>43DO9a43Zs<-0G!tI%|7B?~LN%INJb!fntcj-H)N+1Njr!O&O& zM%;m0GqAd+g!a}-WTC0~0GUOL6$`my4E-c1P$L}z60Vx6h$l|6v><`@nF!a`6$Qj; zEg}S8!o6b2VqA2U7PgpkvJGTYHa3vo*l2)@F$a^A3GAo70u6+0(MZj}d8_ki$xy}9 z6RTB`rDJD*28YMu(jqr^U>e~XSleAfD>bxhU}ooan2uvVrH>zn;7jMFue*dUDudqO z4AA*66yn&;HE!mQ2ZUp(goBN}MecLbNZY0Nq4%QqW5#~GK<==L0Z>V1+eEyx!t`!? zUjbW|m(bZ#=6*zR`K)TqM6Q^?=wuQP_owh^e+G~DXW&l6MG9wg74i7-pJTUXpgCK^ zdKo9-E(Gs#43w)D3S=FhN?>|CE?hRmM@VVOoEmjUjHX`L4}LRu(u4;>VmfTq$%M#l zUC;~%DG73fo74iR&=eiidG4~R5mA|<4Q)`Rj1H9La*?MKkuJmi7i^NQArbPi1CH2VU8d&ryvB*PNO}fy{30)7M(K}9T#ao=v;UmSsUPDO5#)lg6o|#YKlhV zo#=cp;z3Q-dBw4axx1+3X2DBs9gfH4MU0xy0HrLFyDbVN9*{eL|8y6C)@b!&>VV#- zrHVvy5#oTjEw#x7!n{h7p2yXQp#8$FK#X^x1%HF^o$4{rdhnwcKz!grbkdR$cVH%* zMd@d>P{PAWb6Y4RrizOv?xDwdt1N6Xr|aDl6m&@hidx&wdaV&STXS9aS^a6QObsI3 zKSs62Rk_|2z)C-JxknNt_ZaVcGQqK)ofCqKv>!zD+RJmgw&8d3e{sp|P8Q6E@rk+5 z9WRfUxstUfPJwiDX!{<81CDLOu8CMMI=f_{@|ZE{K`{%aEX;8%v<8b62Sj*5u>kZl zk9!v!-(xcK;rA3ydd$OYpvjXFpZTHP-e&=!cq#OIvB5A+#4O6Oc2KR>*zavp?%zq9 zkjxYa|L%n()#F5?&!2oaB!Xb)MoFXI`_x~HxyI_vH>U4Yhq=5L$@nBR*fj^Otr%*0eP{`#`$(MMa%(%r3wZtojjtPw^ z_f&k$50|b34j}iek^&9Hp8BsZaYHT``wZoGj7zj8$`r^0(PuVHWiIFM6(ee#8Jz3(q3Vu~WOdXMwd&%E8)QwaXTs4Gs z+;F|W`3+_40A~)k1{|t}DUejoO|Fr5wiJGe7jx-a8MUsRcsXwmJG}Xef5dysW1``< zjHV;PF6QA}xlalUvYubnS zzecb4c)LtjxV$?P6JL2z@67vQiv2KXuhdI;^N{D#HT`oaAHe5Kv&1X9sNS2aeDYq4 zeOG5%t-Vh^C4zXdPy*YTs=5wrGma~sbs=_aT7zFdv=76BMSsgq3``OOE}`u8Ev7}8D}~o@h2b{$V1N8ag@3%XevER zkxq|l_%uY2S3!}Q@$@B8}Yk;oa9;u=%HFh@&011HRi#% z>Rlaz`MIT!%kton%31vT9#PZ8Esu7{kLXZ(d_@k%Tdy%vUNl9p}E;HbD7^c}jxg-K(#^VjO&%n5TL#`d5iAVe+f~uZV>| zoJ2tN42kDNq?tJSGm~rLBd9!&fxu&L1H1zj+CllcOatW!RIMJw;q)iM#E#9IYCnZw zF`X;2)gjxQMd$J!RLWIU@_7_f0KC~snXVF{k zyAr50X;uBM_KKIA+S%Kx(vBw-dQVhLBf#LLSSR<*XV8j(D*;b3QaZ=no!NwI$~|D} zYy<=ZB}@v&AQzMvwj}EOkvuOUUkjR|2|F zX!tBCp+=o=wO?xPEXay^_>@5{sqd@zWF;xQNY<+f$8s)wP8CYX-EmyFrojDbp^7b+ zoP!I_-ijMZmtK4pwr<^k{rmf|Z`T2or*jf< z6;V}{AZ1`5FRFz&DGpMA7wfOsnGjgTJmvQq#tZr_880zb?@Wo`14Ud7iWbZLbX`d+2p7qkBLzA!1_|qil&=KNaU(*J zSt|q--bZ?85r8W7I&aTwQV0kL4xUgY_!X_KPAdubIQ%6b0O>?u7bqIY5+_1<@b)mE zW)Or`W^INZgYpFlafvTcC?!Z2E<9rCJzHtWrj!)5Os1#<3^fa)TJCog#F zt&e!#SVXkUAQ$ok4Ud@!V#)`Rp2PpBlVwOm6>Cesm#S41hbNFurjTjPqN%$BW^)Etl+>~*3RLks zrNI)@XU$KIFWa376Bx4$eld^x2w_Mqn6H$JHPFRAGpyZ6ypXzm0R07OD*;&BZz;j5 ztQ^(2j2R=ppCY+(GZp^QYq07oM?h zgetYPVlpu?C<}8w&gf^tmt*vK2M+}kP0vgr&!}Qb%sj}tLIQ-iwPuTJY2EqJ>bwyi zQLz(ZeqI2bhOaaQ%6cGTEAiEnqS+cE)DR(@YeKC;0{IRC&jhXra;=?HwysI0#f(H+ z@|5M1-&K+$i6kua(^TX+3@bh!5~>oiN`sa3MQE{deF?|;S7Ji6Aj)2(_D8&HtyY6m ztYOWLEqLyg=iysFz6<;AybrMqWiZL|gtZza)tJ1AfS6~M=omq#T?_zjt3e)3c$)FP_tjR29s27yh7PiH)ChuDZb!M#& z6|cVBUS^u|KJ}evflxxDX2qdXN(zIr@OZ+Cw63c4^kg)h{K_~krL>2wQ?5o?J@O-Q zQ&@=PF(9Qy9#&!D^cfoAlClWeY+<0ek`OG!S+SQ&aFM@L%Cod42BjVCB|PdV*IcCr z>%5B*a3+hy35j`#5){IkkeabT3ZZd()YjLMbOlHoIglQ%){70n%G@N(NBXvUh4PeC z=H2UCL6kJF5K7QwB{2sD99^-}Wgh;+bH7OX<;_rkcTF$U1ujqcQER8PYNhoEf~c66 zE*oibh2)F!`{2vVLn{xmaeLZMvZ9=(HMWIkaZmNK(Tpra@87S0P4v3{=%wCNe5eN+(Jrj%A6jxtU&!nop z53Ri}5z9+_4Ne|kT0mw1ihHZwR)uSncHRX;TH0`8Msz3 zcY#|j3yCh{n;VP6?8qP3#4f2bp-P*FFt)0?_oP44ugU;DaJzW6I++1^eSk(-y~5fFGROksN=7wQ?ImW zk}HD(In;t`bkSExGeDW~C6Jgk9x|)ZF&cM556(ZL(?_zU&_Se({BefNbl{O7j#1H$d&1ey#jYnNG#W zJ|Pv0E;W@90~aPgP22SK1ONYe2?NIU;Ff!$4f`AfGZbb|b%^CPp5PH;!gU)U{f^9_ z<$JKC>HFs7%LV*(fz?z<;vt*%-t5CxE*_!%>qbAJV@nZ3#woByCAo}HBz>kzcUy_L zU~Ke(Nu{bC)QTn4sx@gE7K`iD$P5riqN4*XZOu$@D#Z$l=0%B8{cC90t@EM*VW{QbVP ztxKssrxcoTKnC`&;pLQCk@RPJ7|mvFxqljNFdoQQnecg0=36xlp*5>Bpmr+Ad<5|( z>yPe_^|c?d9#WH&{t};%`FQ1#LG8?XgjBhcq+8F&QTaS&y7sIPM5*;9RjwPK8S?7z zc~98a z2xv4mTO-(?Ndl>yIQ^~%8c8bv303?(|E|R*@T;m-Qy)q#-@8Qj*%O74&(U#Am&~Ma zsEEI=$Y=z|vwkR)Q}o3niPEa-?U|-!Rm)W>CV^ykCtLbR=-Rwy8P3?W8eQG(_~Gr3 z;f|Z{f@Rt;V{uK6)^M5>2x8(!5>AqYxC-_>zE28}N;>tQ?-4}9#MsvLxOm4#EbD5+ zFMfGHP|G2np);x-D374KY{8%aPBWE8*Rl>4M8?M^;griTNjXs(GPwejt5A!DAf?A9 zA(I+LC1Oa%Q%I+iu&g)=#WHfaNiO_l8sv5hP*u;RD{wdv1f#9DIL{*XOY#Q8w{its zd|uoV4XHW7G-j^w#tab&MK=_!SHhLBV)zkFo)9798+`t$J9?q?8V$6IkDEFq4om!?=L}N%biDMQM53$aNQalr-o9oid0KGE;@G`dRMfgSg}#8I&3+h0~wJ$ul^Rmn zG}>F5xJ~SyL&JD%_aRK=3dm%WSh1`P-7PIhSP8VXX3?2Ru_<+;Tw{M=rBcDg#hPvpj_ zxP~C@_KCiZyXqospLCw;eXV&Ubi&}#28kaEAAEsOBMM5$2%H=L@j^3`!NFQUo|uO; zdrRSl;vHB}RPiYqqxZ-3S-&568l0c6RR>W{qf1%{fcA$cHz>hb2}Eix(zMLZTLX60 z;U8FR)0PBW&Xz4t7ObW;+S{A4b^UT&e(q^Vm=+$~GmP=c0^-RyI@+^X)!mGhZAt7I z7{w2MwFi41IZUl$xi$yC3u)TQB|+n>I4X~($kp-8wtj4oC&lPgRXR!TvG)=I+Na zy7vH=mp0?1I~pOz8GJ4eufEq#jvs)hT~5jhDIWzJJ!_WZ>Zfc+E?>rvesK>fBg3$= zNtmAG<)TVTM~&(*q|mpb7h5*3MJk;{zEDAKDvu+F2QW1?4V&U@*eFV|M#2?A|1#E6 zwNA@IYilc3EbBrhl|;2FT#6Lj8IQ-Y@4#Uk?H@p#Q%Qn)fCswr8c;~}jn*%7z5Vb! za^6_JAm^PeNxSvmsNXO>_*BsKAQCD(@`=x})I~ndB2hB) z!CNS)iKvpD0mc|!b!`mq&;$v0BQZ!t=6V|%KF#Whnu4KbBS~kpNTIEp3fA-wk&j8N zJu(6Isje`K%4=EElNt|SDI(S#X%`kIrI0YA@1^Hc3u8xw;1hU%B@L+GC3=!JCT~%h z6TE(Ye4!wod^u@rVvdPS8p%u&m1+&PVdByYwqsRaAEt6s*tzow96mbEX2EneiRRW8 z^mesjc}Ei;f_$-pgTv$4eds7ElT%EXNPA#2A`^7MM6&HI*toinV;c?+jbWP7!YWiQ zmaehcbZr?Fz$*8heaOs#sQe|axMV9{aLIbyeBU8_@0N#vYLSV9Yg5>gWJn$=`2lO5 zhUSI|q~`hwog?1@Ag^}FRIZy8r6r0pfmD`su^7@V&Dg$vIj%UP4{Lif*gY_YAKiNhk3Dh#W-*5t#iS6viISC?nNVr| z>R|YP%VZm|R#6?H)euV7mQ`{CWJUg|+^G!8JEkX(Y2sU*%P6EP2@>ny#K(X<66A6r z_aB{;N{yNJ>ND2jrPrJXyJq0gUHzDtE?|5rk9`LRQ5&BC>*5WS{E?WhCoZO z2+*C-d-Ix*3llEN#R`yY!V9iG4=Z}x@RQpfz}{W^0dhOCrXNFdcL&ZoeJxsAT97N* z7#$kHp+o&_b?RHa9Lsw;IfIMNS3E`y03FXtQ7Th`EeDxo9F>aALUi1;Fg}&zcP^HS zd|g{}GuEzMj{S!QFiZjj$xG};^L=|>(6APd7PN$i1S?(dFcjYp_y{%WPUnP@HUxrj zmEnV&Ek;OkRO=fN2NxDrJ=(93Qr;X6D)q+H-{;t}Esjfg5c8zq7*9vj<}Vi}bn@zW zVPLiz#SZhyD1;8|rzVN{LTzxt^=E~7uD-!aAn>@3<^$DI%EWE@*hHutCV&j_m>{B+ zDoo2jJQ3Gqc1@=AOqfbH3}I(@@$>`kOE5CURST$7CTgh(s(16PA0pV%!!=DD=YObX zL!ro8;JHsbADh;%!u|K|!ebBbq2?IWct8t26VcU3CWJYYgV)F$N`i~YH6KK}rZm$M zqckZls|KekBO+rYC@2k81Vjo{l4fxJLuPtVuomU0S1oMXyaunkW*Z(oI*qUV@GhV@ zg*f?2Ifg=|_G;3ko>?Ma)-y*-?MekV>V9V>)_DXxEbHpZsEhpm{E zaD7RE$#WMd!9&+vWN@uI3o2Yd3Y#i}Lb)PXT&B1L0A& z*(S_nE4Hog!*efOi8I%=;3tnB#g~74AMCL)Bx(9pDy=R8`3%xpm4?THvWngh3GVt4 zjIum--fz?xE)wq%wtIRQP4Lz&5Z<*wiz-L0kN5!>RFgIaWN%%5w<<;lm z85eBCuOB#!@80wP+{tnBH`0OTBO2rQj)11*y;LC1Owk3O#02o(uL`H$O$!E-bcKGc zlIZ%b9cvu4$gQg=0rn18STB#$R+adJMV z@P*dkbQ?*I3obnPrzI?qsn0!uNd6)uw2(OeV2UTiQByC3d0;&Fk@at;+L$wVuNYfAYl$xsC zE`{)7Ou0R3?Z_y>x#r-=@pwl!-uSGuF(`(=(TpCGgbWu0wJHu3ayU3Ph}`rvOvgc73QNpzr6%G~5F*!2S9mSP z<@8lvGcAxyWq@deh<>FuA7r6Yfr%n*O_+&A7LbKZrU`5MIRiM)vhWnVJXiGbnhE=T8Cv2^cZ4MlySoKQEPN z&Mmm`tkrnq)7Ie8u>$_(`**_~97LS_!VYCo(PBtfmYlZ=zf&5x?k)A`8w(sH*oc%m z-D6I_3jQzB@(#v{%t-nxP0;kt5K0kxRxUcZ@g(ig{X`offi^ zhm>J2t4P;(Lh*k=p(C7)Q?KkVuJGVRlWS%G@8oIB)qk77ON%jlNtkhg4hIu9VeVI3 zAaF%3kRWnw!j)0fiqVUhA1V3Dd3a`E=|T{=t|*T%`7t5o;4?#55GpnHzn3dDj###B zTVx^_6nqp%Qznh(=4P~aG^4F4jgoD^Os3J6$)ZxNqJMaVQ=V4$Ek`z+z@7Izh{Jmi z0?8N>Y?bgZ$_r%k;wl(XG)61e)+1=TAKVD0O^Pcx=HDMnj>kot=o%(E!WtmH7gD}B zhYoUO7fq=QUUd0(94)x`>96jB;ZUvrgqIe{eoNjj8K9;PvkWHWu@xiMP}MiR%HL@& zGWbfBZ1RIjB@t3oND^E6%u-A@W}sNAp*`DD>we`g;{ejHf3RTS0~W=W{CEBL$m!sl?FL zl!O%%XV$SvQIQIZ9G+ZxoZUd@h5`T`7nf}9!!u4_i!c9jH*SAy51O-L-Avwem(wX( zfR+Lj$AGASQWn~@R6a@Ch2Sjf;e;}enE8b=a#YNV5J=Qvm5jA!qf)A%R*`|sBv9B@ zX|S~T{P-CyVqDdIRi$7H>y{<}N!q3-stLVGW%&5#pO&gd&vXr}U%LXmT`kzV_Xzrj z#$el3UaL4MGy&CDqsvNZ^-PQcUno6QB#04h6*NiFNTHaCRLq(T=wx@SGJo)*(7Hc{W<#Gu&S&t-bWYkd%!ISh!I99>&R9`|_M|?%w9}_ikKqy!)&V=9M#pG+qB*hY$Fm)2) zwq2B~ zLMx((+Ua~1!xMQ-6^kg_@P9mO&@jEcH zkkUFKo3frzSy(c;vDRdmh*4l7U(0nj8B_+G5P(8fG?s8#{FW8ah-rv-6l)@^5A@uM z?Vwn#qN%wR7i{RmX+24_#(^L0p2VR_2}xRCDpM=>kP{?Tfg4pZRB=Sz?Z6*NQAROo zx!%mYNa_zWb7iH{tuaz75(0;KFJ@MBXklQg;^4H-G|ufZar5Jo7|PkmCN0(m`GAvg zhy*6W87c5EE)gDa-2hPoKxs5|NQt2FpMuXyVaul`Dk5EEwi1(;0)%wWa4kGhIm`>h z<2VJmTAU}(j6}|b7y>U6?FTVB8{3y9k!?+&NN?$yybsjzVK7&g0O;rm}h3Y7P2v5UDm+vqXj%RRzNmu2@8|lD3?-LNoe9w zB3fv2`-%7_5+=MKMWf~Bd$CfqxwL;CZPz?tEZ2~br34WvlTaLqOr2!QjdUAvWlNd} zxr}72m9lt<7!fgVLEi)uR4mOS2WsCu2BTROiGIo>>M>alPhF0Ipm>Va-R)>^NuyY^ zF_kOgz>z`Zi)Cc9DW=CKZlK)(Rz@ z5q@xu4b=FIv2Z9PE+O30_cUicWwQaCV7G;DNbse0-`r9!$p-}tbzJqULM~-b0Pu?B zXs$oWvqWV$J&#(8a`vPtE!e~}N2ximIn;kBF&8VAKr)#`b5n++f3xW{Qpp5wNWM_U z(AXp22`!zSxa6GeXlZZ5L%R=P&(3|QRVql4 z8-S%5F<%Y_B7z~fGUD+hGv9J4&!#;p<`O5jfs(>K!l%EHQXo`7oOB;}Wl*yWjSr$YHikq}PS=+NMZ-s3Q1-By)`tir$6WXp3l_K?LkKh~2E`UWbJkETkxDk@ zSa`wNtFU=_3ODQ@MZvDXBB7*apdc9&MbQY8G6_EhDz3}gI|Yp;O_K>zGAVNS>4*M~ zB`n0^F(eWsoC{O0L0n&W-dG@`B3!K9N{NrPOtnzVW4KKaW5+`sQAT9P$Z0NDLN43U^JTNY)Z zDT!~a#j&K|Gd})KR*@BzBUNy$r~C!dyLnDhU{(r?S5!<|`zX<1a&1eSbOXq>RGPf6 z(fckbjf;DDCae)b>MwluT0pIr{-<25dPa+~h)Npb2~%>8%48Fu(ZM`IF`lnic$N>( zg(mI^nE5rjNX(Q{%M+G~)}{=W_jVzbPUFzgK@1L$@mwh$LJ3TB$H@q zZ9*)TWW}RcEFfPfh<#y3EtL{FU#7)rvWW!olLV3};w1@IOhu40U2C#?rcy0qWIT_d z(Fqg^1-6h0kxB-~cqO)_&_&;R%*=PW_!?wz8D|q8<|91Jzs`g5hsobXu$dOJ9*W%N z3F^$n`#`BQs${f8FfK2xRq^ujQ^mKzfJHg37bNG`kYMtpOgM6$Iud(UAo(%TylT0K z;*^W=VKunq9-^X=M|erYVvUFjCsjzwBMDOx5#g^UjcBU>0DgR=AFDQ=hV#xo9jm%p z@c6EMICNwXEy{sbP|y&tt)0Z0-fNC=a> z;KYKENzK1XLQREy#?r^FO7fAwK%ZsPXzgf6-?A>OSl*4!&UPeXaqNEL3H;`P-M~~% zs7!&qmJ7z!In^HdC6{$XRdm9OS5R3dUK*d=VVRdI{#07Owym0U;(HMFbO0%Q&>mE( zxOsROU2QEmZ&Me(|CRdzw+v)bTCkZG{OVDCjj}M|)Qaw?IVdLONv=u)(#G-*uNGv* z*CCvDVSBbWg8Y*8647{MQ|%K66w2E+r`3wD*hvvsNZpLs3n6n%RA8y6Nd&zF+4RT zG78k1hvF1;ft3X%dRN0>cga6JaTqUu=DB$3xm_p}$8pac`+(_bf8RKOP{l#W08o{E z@y}oTH846XjawR{ z7m|XOH6ov@Oh6KU3Oc7$(u(r==nPzq;k~O?cfr%@^)ywFLwjq(Dv7JkicjkUbXjwA zsrm?YhdXTM;y+c@Pi-Dr?FG${>??_yf+*_S@Im!WOmgj&Yo$O!=CFYU}$mMd3^ZwjbHBC>m4ZbG{ zl4MPfk=0qaYPg&UTY_jDHbZ*WQQf_+_Ds3#JTHTc$CD>OBV4*lBi2XXf`x#2r)t(G zcNjCvIof;F-6~c#>WjI9l4f=LhHlu<{|#5M(x$6V&;MPfbSVbt)nNA{@O4_|J%Y_w zVxx(;)=Fh0vd!4Ec?0_T`Z$=aTrIPPm7#cuL>!q^iiMr=$sC4`jV5Q>h>QO=syBEtYk}b{X>+9j!jE_&FSS+ywOu5i~Yx>aM-G+|l zCX@?hOiWDU$lwU}9z2TbXSK(7bZYazQl9sZT1@GRmf4!XN1)x=*wO0%&b1 z_7XhC3kxGCQRx|tWiusr0wshrP*>?y(d`I3MuAG*Xa{!DZE zaA#I4hTg7rv=NS0DjX$G#eOJ)o-FcQ;Z$m0TsuPYc;yD8wIVAESq5z@gQs1&1FySk z6K;F#D8Bovoub&-bP*VvVxg1F5afy=qODq}h|=Xs1Lw{3_DV%^YX%wtUWT304&_@) zhD8<*9w3$il36_E{B?NuOV7gn2lM#bFa8P`KZ-=k;tUZX==;Kp(*AwZqEv{K1yU>I zsTibB;$+aKYBWYx4TbNzDK==94Wx{U;8;SW2AejmMW!i( z!$(F?D_49Y(Of)#`cIG&tI@+PR?Lz{u7o@7iMsfIxvdo6< zm<{4J!+!?u3h+JgX^7+1!HLhdsH3R!1zp$(bNpE+qg^_S6c9p2zn1;%)AKF~%S0X` z`$f`KEQnCt1o2S;pOlJ5C3X|pR;*mL0_jW&6{@agPzp3vY%F1Vx`-knXu0fZ2SzrF z9b4CP%26zp!UOj|hTV@n4md>omka{dIFQaIANjBGXf}=h*p$IE2`yLAhaQM>w{mO+*jZ{ zONU~J+Sam5!Sjykj8rgX5{Oz?uf(5T_jC+T7Vy;{+=J=EN4@BMvUadplFiOqmBdhW zIG<5^PBXtOiE;t)yQfPV822?|DQD&tqhIKOz~4NRe+~f)?5lM zG$v&-5Zw|LmHn!$RCkm+`YFLgo_j@~Ig^6~R@FIBy2Hr5qAZ4NJl9h_R4$5$bapW)Dx{gy^~m#BjD65#;ix$YoVk4?UitJb z=;+FDn()D~0`7TY6npm#;pm}J6vn4%(>S#;P9{ZV$yC-)O%wNsxlXaY^n7XglmeDr zuEC|?hHMksR&-(8rXFls(~EV>+p%tWGk)^WAg;ghL11zS@dO1o)ikPB-P&C9nE zsI~(f4-%lkeukNJbVwShDh2zoCUvF-y~S>w0vc9SC9_n$i1;vSuEF8z z@KQgd-gM+4tCAm$+zSj+1ytH8o04VlsFYZ1wrFYtD}~M5x8STZ)}vM_;mE)+BX>5F zMY5#@&CMC?*>eyF_U&gPPDPxu*$kJPF648V7#SC}8YoyZ9+y=jW$LGzGe=k|Q%cZX z6uswqp(J5O^xCN_#Pocj{$hFUoYjF>hfSSBPrFd-rwfNhaDKd2A`*^@TeYp~!>gWk z9^?k>!J$bU9h|`7fl-vH;1ESw#|=^UKIC^%<$?ooMj8?H13TrKNsXP$6Wcb+ z1T7m@ZQy9^b7cgoOyrR%w!Q@03M_-B{8y$N{EwMyf74+S-tAPNP(*ph_`8Tq>PHDr_$x zPid~+V?@A#AoKuA1sB=w9-O&pIhr#utnSWY&8jXWGI36KEagi$I5v$R{&p`0AKnjC zN+KVhJbxSzB9Ty6sYCdxo=w7ovLso3%W%P2YjN)BE3mw?8BGZj!;?ikerO!Od3+Fu zA3ID{F_5Hp=l7u>HK?@k$QTcf*z|-7^^YbD$W+M?x@sbpWY+A(^p!P*O993wt2xq` z%}r@G-4`lVR0?I(D4R!GAw=ese6~`aRHF_x?>fdWaYkQ1Ne_HixUYHpIHSW1y0nm7 zeT7lS>o7C-By534RJ6`CV#0M-t9q6>Wwq3MQ5c$sOFMSne$)#O4dy!|C@C-WE_yIn z0CY`R3H`INt9ccP%9HRgWu5ub=J^CndN9+vM1H5+wL&lBN!4>%WOs&It`XPj8n6E{ z{v7MfZ5rbYBVi+J#Ei%uy3os1kq0L*C!JCHnhyt6R%*z!wqpI-HCVM~IkNFMCZ>yc z;>b}94N&u`an2H;z_%JlZc1b#e{ezw300@sgOwD65|AWUa!GWA_L+cC)uQ|0eJu-6BwG}1 zU~nXdoqPJRXYXM+lhk6^Mj|P!5&G8El>^a)9c7OYo(pA`qzoAYYtG+>*FN`bj11-R z<6rIMa@)jv(y0VG+gs4ml0i>Lh68dbwj^a47#q*w=3no^_}+s^q@*CCe5i6U#P4Fg zRS1A2V{(5~wNs;R>4e)N0x`wLOW{qciYm8``MG>PyX|G0WN!s@H$=z;?lUkoI|+W? zqsPqDJ;JB$A1)T0t2RfWQ?n$_5R!W#Tr?^LL=@f;fsFFK$tok$k{Kt+6;Pq)$AEYO z>1GO;YsK2-?bxuY4PBjCq?*&%bzl_tJbD;|BNG^-Ms8zypjP5yRw6l7WA2`!=vyl) zWh%McgbS`Z6VJbF6AKZK?-{~_dynG4p%F|Cj|0Ur2SjnnWWr^c->(%fR#KZhTUrXB z{LUv$BIU&|BIL_yzR^zzX+%FrIk8M~25G)PV^@=p?JP zty?@z+fet_$xpI{vHDp5MVUCY{Z;Wf|L zftzpNiyz(cAW$s`=H-<>mYkVlRj4Tu&)ML51h7j;kXh7{#k)Lyq%}%YxS`g7nXg|B zpI3$Bb5u)ixpsjT?EXe^Y=d?*RUZl^n314B>{`_`P;qxESkrSGC;`V)xs*@duZzHc zd$d5*bMVijrSEenpx-}7;6mOfbufvZ8PU^pc-c-JUbjVPR@A962l z$lGYqVN#@Ix=5!pY?`MG0FilRb3Ge!nbvAmq?2(Zk{KkZVl1ctR~h5ulU&e?ef)Yh zo2MA4^bb9lss6b8c%qXHt)r!OlTr&cbci0*JNO}XQAhWJ3ZsY(nL$a_B^SN%n>M%+ z@t#5XrJ*J{i^i?pt3Nk#jG4aETRr>EPW5cRjMTAO9=cGw?`uPbx$?Y+t@B=Y2Fg>a zUh3>OhXQNlOf+H_b<-TUF+tsiHd-KkFk_bMBF2l7lp8_>k_CjH*(@d6hBaEB@Yo(D zh#pM|U*xBwz&x@hFj4dljg;~w^B}?_I&G?t6mn_=nE&>D$j1f|0$-FYIM-qHHP=!) zlt|^5kCy&g%}?tOBwQyH7D8454)CHv31%Ek-JLk=^i|lpu^V4v*Ij!SZurG+{QBqj!Z1smEyKZV zqVj_**d-Xg$kZW?QT0qIrFxp5j;A`l%6aPrs6wtPMdrMyH)Z)!ZX+ce zh05V@t8I>)q>899(OAPfxa^{JXzIw~&fQ0G zcxW2M3N`quAwj9FFi^EciEV1g)ZUrFi!ND%wXGR^>c>yu-iP;L^O|P1Y8>2q6vaYG zR3YUQQJH>887ng2lp^n`(A*SRJZe==t>s!Mo|#(wn9?G_g|l?L;7t+jttlIZI?g6y zF)kBMRTf*CnlP0sa3xZ@mQvC)nJf#N^ju0mBnwTcQbw^@yLm1U`JEce4|nv_KHRVwJR5y6I=n% zj$_-?&cz#_eHOlS!vnbg7xy5Rsfu(gLFz?Fgx7#Z^Y?rDfUHv}nWG=Cpx#(%;?ixQ zm@#YR$}XU-vvvU03V8CHqVB5jRs`wL-9f$*<69NuV2Dsoka10I`VE*?FU!^3+Ake?Xh^2p12x`dXWD%+!96`BMVw@mBLR6d<1;WIOinh#L7l6_^ zsKJtJpgEI8XGaTCO&R_>pD)3+YsgaoU?DGy&k1~s#p2u(g)N%38e8lFm024x^BFfV zg5xS$6|tN8*g7uH&M>0pHXAMSg@-yk3@9HuT@6}zW|Up#yedKWz0N9JH=*vVpuPU_~lSN zNnaBV{Okc^?!m0HzEA@dV%7tz-K8DKAfc!q(VMg6db+IaGgdAA%4g4k?-Yyl?v)ea zioNUyk0X^$puMdL%e&jq-kd?EIgR#?CZwA(96z`J$T<7KN5`f(*SlP)!j7eI$@v@c zk}Edh8$Wp*x7~a?3B2`_ z;|X@|3ttFfR(J=3>(8Q(7m!R*|Kc7W2ZF>`kE)lW>3Oyxw%~nSH_*)B&pr4CepxwR zTyjlOjLor2av!L|Wk@7e)(=(QRP}#>iAt#qtE(3seSJul^T<&3Te37%Y~(2@GG?J_ zS5YmOQOH$T;DlWR%6X9urD{m9_D+^8W#$)WfXanaNpi||N+*-(>Tbu%z8*BUv@nw& z8X3bA2L>=XHO0>m^+Z)!ckw>W*$g)xGf6NpsB&R~pIOKkxW^8~EL1DhOGH#Y^m;9@ z7evKd_*p{@kRker>o}@&rvM`A?#j)MQSkka?(CB5t8mMVwW}t-!)I}9+NX#xWXRW;)(mmfK(DK9Zgub zq6?eWbt9QhB9Tm@<`^jCN?6&I#2M?l@xMRcg`a%?H;ARmY;hoex=KUS35H_iLh%=D zS_*APW=^|mBI2gnO{cSmeiHfR`DW6JT`%KQa@Dff*hAi<* z1mKFP&Op zE!iB2dO*0~w&PTP3H1N zwzv>Jk|4xcRa)KNI`HMKkf0kOOavep=i*)HA%oKNH72EM@~C((i3=KnMqpDEqm5Ex zbSZi!;u}GIbsPyKFFa?yFnf+|b+xn8|4$p2KWBXHGEln@5We>VYA1lQy5gVh3B6rT!xNPL2}If;)r29dSZ7xodb_%~As<_{DBgmyr{XcBGHLW5 z8ODJFhcPud$%2d-kF!NYJ>1Wb@@qK+8Dp6HL^0(MetC6XZBI6TE_UVr_lM-mK&?Fc05Y9Ue-D4s8uMy6q40OdC0W#=Se?MB zNyUxuLk;91_l)xm-amsVH9ye2B2oAoo`G-5j-KfZxHdN;G23M4aJ?d~;n{cuMgQ32 z_HtfsbYU+qLx6qQ@(I4AAns;!w5X`Z76{c$Non!gb3{D~DVWfp6tf`H>_vq@syk2v z@_8hCdvWZ&2?K5W*+{ z&Eu-RwkcSpE`0c6h0kVvDx^Dt8lGB_058|ne@732)%-o4LB4b~6ZH;iMRaq3jwt^7 z27eRHt9UFKxi1_#A)!qP(@H0hK{BFCrwSxi#fvmb9D1sdb;NUhZzm7(Ef`Qm$vHr?U7q~Lw?nsUu{5}vD z*N6hofij2WiiT{xQO%|Z(5cDs@U$Rk!k0Qns*X!2`Y3Gu_f~Tz1~FIRfnta3Dr&d< zAHW5)!qN;AUf|;a!u5TrU#hed!ZTHLGA% z2QikJWyQAO972H;viyXI@T) z|J=GNW3%srM=oYfck;*cBS-w_1Z`=4TtV<@x@;g%Xdru6R{vD%>uqV+(NHh83PvlK zxcb`{RQ$qNEFh@Zg*w8h&DXO4Xm6t9jd$jhHB0)GJuaw?AF&;Qm^M$N*QKWL%gLc6 zYU}mb7$;QLkh(~dGT602&6+q)L6sq==thg{h%{x>NTjmtG8q{iFgIew$Z&-P+2jOJx;#{pKarH0kdrNQiVBvBQ-8eHF)DQgwfWYC<)5`!2VAbQ?d z0TZTns^tYjE8zZ}(ZoZY@kkLh3UOxM$vPSsqWgYMegl-$4n^Q}hnR*DX}btrtH#nL znYlZZtK084jJ}5ap4d$h1@a!J0)w z)c_G6i);h04YVfYh}s#lPJ}nEWS;UF{uBa%6X8|xrw~BnAd3;-sSF#50Z$G%X; zhkTB>URmGN`wBdua^aLIM7Y}C)`CPLjnRool!^sUxK+3L%NAnTdQpWiA@Y=$5SQhz zb(#^v->CB&*t=Oc+YH}(`%{PS`h7F-o&aHun3i6tGW;40v&=n!t_^5x1n5P+{9yP7 z$3@8-QF?pS{so_;xH)DGlr(_aEg$)@n;&^*U}ylFtj*W%w9b5qus+NJ!FcPyJIo&< z1_lbK;@W?1jA zbR9LP*+kSv$X!pggZIt+Q6$t|7sW6`1lwbhzSgM6co+i z9~aD_U^8xaOgO^jkf}ptm2>C0{dKv_eHN(i1XVutN_(qm@dU!AAB|yn?;t-3Om>cI z7P*KaN}~(FKC5bYHbNr>*Ks~mYFwaoR^h~Gq#VezEB?^;UoB+BXyG6?Z*oyH@hvwb zK!^gYT1u_b^6Dqq;LSoSI9ryMcmHgS0<}F3$uk_MLnV@Sie_$K-6uG1k1Y5#E6ZKWiS+NW&}{0g2ycCBzw-$)*NdvzoH@60`Eo4p?ZMHbBk1oRKp{WPeL$wCawrsXD3uCa!IL8H z%jGf`=893{CAt4RI7=&V*<6a|zy|dWwh(Lcu}d@$`v$lhePipRE{Qi>=^4Rpx~X_MGYPM&p3U zE|_6ql$7W3;h>wLPAJp^u%$~v3B}}MquvbE(ZIzl z5}5z&lu#VHV6-_Si~Q5i2M+mE8)@noKbg_t0v96L0vRz-hNKG_JBF8Zv#t2#A6z74}Gel@x{wB&Evo{ zYLsas-O_@lmS&U-C6uYj6cxB}m0wuZz>t!?F8CM*SJ&(8=-?tb!$U)uo}NZ5PAP5N zuv(A;-I1>dB>(9LFY$+}EV8cUhtdC-L67NZpxJrHNX1Yz*c>&v20D-anf{#`!TU}R z;M7r4$H@kkhTu~8cv=6O|5qK#sMpqt{DkcAp(o1U>-NF_z!MNOCDRK@4SOkOBPD^g znMqp~j7IEO@O$r-w9QaKyZ$El@9hP6${TbvAwiesl1wBS&&gUwXQNuH!m;T`_HoeY z!rY+IyVbu-aLqzWU?8wwi-W1FG8l!|Ap!E31OYW>gTtxD^I{1?&v2t&JIdNP+k6^~ z7q~<#-5jVH6B?t@AUb~v)cuzD;$IYcuEW(NDc!er>&I?&rw5-_H*5&n%-*fPja~f5 z8!0au<>@*BLJ`)w341u8zhsc`MU`jv8Qu&F9r#)vx_}#0m+bWU)!iJ@X~O6evLH0V zQ6*(Ef74E@SL1!Y2qR_`FsaRiGy&;B-;0os(tFW{7#g14EbBM-LpuA_4Hiol?h$LQ z0^LMB3z=q{vQ5Zjn^3M)xJCnaq)>H}xT>_Mwnx?cNF!6EnjoDPX_xtY0iz?MsM%Go zCy4Lska7EA2Bi^luS=+^MImuVbb35~A(BVa@iDMwMv!5t|9KLv9=$Kj+2RuQenI*i zV9?>ZPWrzAoDWJ4;XpHgcvWO-hO7;pj%Wlkpt;HeD9o(>dPn1sj=y>VC|&Ri3PfJa zM4gK`xc^~+B|z#hSAipf4(UX#j)ZAUgcnoh7;(%4_4N?zqQYetMl4m-xS{9j$a2iWPu)v37$=kxAMx&W?i&^ynz<`&?brXg+ZlZ90ss?% zZ|G6TIUuAi z9Rz;$nU{Da$=-P>!cmNk=M_f7`g!@nkD#F{UJveK8&(W4GbU*+5l9h< zM%P!X6_iRv(YBeZ2{xKx=mi2yqF#VgjBTMoce{wK7QvOO)24r6_#HHy)B|dS4ZH3b z1W2Uzhc3f}+u+n=Mz|(Kh07uHWOQMG&ge=&=$SfC(CS14<{ow} zhx7XbbRr^KNRdC)_$d-4!VEe@6E!o2ny=oW)VJb_{f%5teNJ4PLj0=QOp7x@ja2}r zBF{%SfLt3$;Dk0;JrFnoJgO23a2UarPI==HJ>AejhIl~)BJnu>0G!jr2mbf zVYwy@&1k(j2HrI*%*4~8*1-s^z0a=#!UMfSx{d3F*mr&Lpfm8$6#({ypFYzYtTMVb z+z>nWHD^<>gqt4`O@dTOC@3^Qqy*nbfE29z=}+`7APi2w+@9| zWWh5V#<>O+CcQ-ry)gqq*^~?o%NE} z8!OL)LH^{@q-dw>Q4Bc+?S1@%(}=Tb2d&ODG^70LNrJ(}2p>-WJ3YTUY9j(?PCqaK zf*Q($*94`;(x3i!#Cta+C_drfe)6V>_~$OpY?C*+%&v+>AdQ&zCDz02x}p`t(Gr-X}wd20|}8KvPX#;GBZ zUsFWUulhF;SJlrV48Fy{r$vp9q0V4b`mg6s)0v0E*jme32SwOG!nR?=uJJHQTP*m0(G1U(!BcQ1#Ohj*$6OgSN!dZR-rlz0hf4~ z?}VAXK9>C4FZ!WfGXs5zUJ`vouV`02jVBsw!br8kHDhoO-wpeLZ++1%P5zPSK|k{& zXM>lUtIqqNwc)BwM#nnAxJp#toqHWOcr{s2MEkJOayEiS=A!ynh`vUxU89;+fsZx9 zsD7=hV-a!RT*-L&nT@^^T90UAL{b_-mz@clN*-SV+odE36@|U zz?N$Zh{a*VGa?42I01KJKb*t&KJFa4>yrRJ%_i!(3^$)S0C=8}>AcqH+W2&%b;WX{ zxfe#V6^JK=B(nrdumnr61WT|4IAwr51=TX#@+92pLAaCs1MbM~pSgw6p8)vYv5xou Y1FT6$XGH)x%>V!Z07*qoM6N<$f-fg&5C8xG diff --git a/website/public/workflow-map-diagram.html b/website/public/workflow-map-diagram.html deleted file mode 100644 index 2bcc4c441..000000000 --- a/website/public/workflow-map-diagram.html +++ /dev/null @@ -1,361 +0,0 @@ - - - - - - BMad Method Workflow Map - - - -

-
⚡ Workflow Map V6
-

BMad Method

-

Context engineering for AI-powered development

-
- -
→ arrows show artifact flow between workflows
- -
- -
-
-
1
-
Analysis
- Optional -
-
-
-
- brainstorm - opt -
-
-
M
Mary
- brainstorming-report.md -
-
-
-
- research - opt -
-
-
M
Mary
- findings -
-
-
-
- create-product-brief -
-
-
M
Mary
- product-brief.md → -
-
-
-
→
-
- - -
-
-
2
-
Planning
-
-
-
-
- create-prd -
-
-
J
John
- PRD.md → -
-
-
Has UI?
-
-
- create-ux-design - if yes -
-
-
S
Sally
- ux-spec.md → -
-
-
-
→
-
- - -
-
-
3
-
Solutioning
-
-
-
-
- create-architecture -
-
-
W
Winston
- architecture.md → -
-
-
-
- create-epics-and-stories -
-
-
J
John
- epics.md → -
-
-
-
- check-implementation-readiness -
-
-
J
John
- gate check -
-
-
-
→
-
- - -
-
-
4
-
Implementation
-
-
-
-
- sprint-planning -
-
-
B
Bob
- sprint-status.yaml → -
-
-
-
- create-story -
-
-
B
Bob
- story-[slug].md → -
-
-
-
- dev-story -
-
-
A
Amelia
- code → -
-
-
-
- code-review -
-
-
A
Amelia
- approve -
-
-
-
- correct-course - ad-hoc -
-
-
J
John
- updated plan -
-
-
-
- retrospective - per epic -
-
-
B
Bob
- lessons -
-
-
-
-
- -
-
- ⚡ -
-

Quick Flow (Parallel Track)

- For small, well-understood changes — skip phases 1-3 -
-
-
-
-
B
Barry
- quick-spec -
→ tech-spec.md
-
- → -
-
B
Barry
- quick-dev -
→ working code
-
-
-
- -
-
📚 Context Flow
-

Each document becomes context for the next phase.

-
- create-story loads epics, PRD, architecture, UX - dev-story loads story file - code-review loads architecture, story - quick-dev loads tech-spec -
-
- -
-
Analysis
-
Planning
-
Solutioning
-
Implementation
-
Quick Flow
-
- - diff --git a/website/src/components/Banner.astro b/website/src/components/Banner.astro deleted file mode 100644 index 00944d669..000000000 --- a/website/src/components/Banner.astro +++ /dev/null @@ -1,62 +0,0 @@ ---- -import { getSiteUrl } from '../lib/site-url.mjs'; - -const llmsFullUrl = `${getSiteUrl()}/llms-full.txt`; ---- - -
- 🤖 Consolidated, AI-optimized BMAD docs: llms-full.txt. Fetch this plain text file for complete context. -
- - diff --git a/website/src/components/Header.astro b/website/src/components/Header.astro deleted file mode 100644 index 94d056b49..000000000 --- a/website/src/components/Header.astro +++ /dev/null @@ -1,96 +0,0 @@ ---- -import config from 'virtual:starlight/user-config'; -import type { Props } from '@astrojs/starlight/props'; - -import LanguageSelect from 'virtual:starlight/components/LanguageSelect'; -import Search from 'virtual:starlight/components/Search'; -import SiteTitle from 'virtual:starlight/components/SiteTitle'; -import SocialIcons from 'virtual:starlight/components/SocialIcons'; -import ThemeSelect from 'virtual:starlight/components/ThemeSelect'; - -import Banner from './Banner.astro'; - -/** - * Render the `Search` component if Pagefind is enabled or the default search component has been overridden. - */ -const shouldRenderSearch = - config.pagefind || config.components.Search !== '@astrojs/starlight/components/Search.astro'; ---- - - -
-
- -
-
- {shouldRenderSearch && } -
-
- - - -
-
- - diff --git a/website/src/components/MobileMenuFooter.astro b/website/src/components/MobileMenuFooter.astro deleted file mode 100644 index c331d44d4..000000000 --- a/website/src/components/MobileMenuFooter.astro +++ /dev/null @@ -1,33 +0,0 @@ ---- -import LanguageSelect from 'virtual:starlight/components/LanguageSelect'; -import SocialIcons from 'virtual:starlight/components/SocialIcons'; -import ThemeSelect from 'virtual:starlight/components/ThemeSelect'; -import type { Props } from '@astrojs/starlight/props'; ---- - -
- - - -
- - diff --git a/website/src/content/config.ts b/website/src/content/config.ts deleted file mode 100644 index 31b747625..000000000 --- a/website/src/content/config.ts +++ /dev/null @@ -1,6 +0,0 @@ -import { defineCollection } from 'astro:content'; -import { docsSchema } from '@astrojs/starlight/schema'; - -export const collections = { - docs: defineCollection({ schema: docsSchema() }), -}; diff --git a/website/src/content/docs b/website/src/content/docs deleted file mode 120000 index 48c4a0c02..000000000 --- a/website/src/content/docs +++ /dev/null @@ -1 +0,0 @@ -../../../docs \ No newline at end of file diff --git a/website/src/lib/site-url.mjs b/website/src/lib/site-url.mjs deleted file mode 100644 index 62df2bf3e..000000000 --- a/website/src/lib/site-url.mjs +++ /dev/null @@ -1,25 +0,0 @@ -/** - * Resolve the site's base URL using cascading environment defaults. - * - * Preference order: use SITE_URL if set; otherwise derive a GitHub Pages URL from GITHUB_REPOSITORY; otherwise use the local development URL. - * @returns {string} The resolved site URL (SITE_URL override, or `https://{owner}.github.io/{repo}`, or `http://localhost:3000`). - */ -export function getSiteUrl() { - // Explicit override (works in both local and GitHub Actions) - if (process.env.SITE_URL) { - return process.env.SITE_URL; - } - - // GitHub Actions: compute from repository context - if (process.env.GITHUB_REPOSITORY) { - const parts = process.env.GITHUB_REPOSITORY.split('/'); - if (parts.length !== 2 || !parts[0] || !parts[1]) { - throw new Error(`Invalid GITHUB_REPOSITORY format: "${process.env.GITHUB_REPOSITORY}". Expected "owner/repo".`); - } - const [owner, repo] = parts; - return `https://${owner}.github.io/${repo}`; - } - - // Local development: use dev server - return 'http://localhost:3000'; -} diff --git a/website/src/pages/404.astro b/website/src/pages/404.astro deleted file mode 100644 index 46065d04c..000000000 --- a/website/src/pages/404.astro +++ /dev/null @@ -1,11 +0,0 @@ ---- -import StarlightPage from '@astrojs/starlight/components/StarlightPage.astro'; -import { getEntry } from 'astro:content'; - -const entry = await getEntry('docs', '404'); -const { Content } = await entry.render(); ---- - - - - diff --git a/website/src/pages/robots.txt.ts b/website/src/pages/robots.txt.ts deleted file mode 100644 index d4dec7971..000000000 --- a/website/src/pages/robots.txt.ts +++ /dev/null @@ -1,48 +0,0 @@ -import type { APIRoute } from 'astro'; - -export const GET: APIRoute = ({ site }) => { - const siteUrl = site?.href.replace(/\/$/, '') ?? ''; - - const body = `# BMAD Method Documentation -# ${siteUrl}/ -# -# This file controls web crawler access to the documentation site. - -User-agent: * -Allow: / - -# LLM-friendly documentation files -# These are specifically designed for AI consumption -# llms.txt - Concise overview with navigation -# llms-full.txt - Complete documentation in plain text - -# AI Crawlers - Welcome! -User-agent: GPTBot -Allow: / - -User-agent: ChatGPT-User -Allow: / - -User-agent: Google-Extended -Allow: / - -User-agent: CCBot -Allow: / - -User-agent: anthropic-ai -Allow: / - -User-agent: Claude-Web -Allow: / - -User-agent: cohere-ai -Allow: / - -# Sitemap -Sitemap: ${siteUrl}/sitemap-index.xml -`; - - return new Response(body, { - headers: { 'Content-Type': 'text/plain; charset=utf-8' }, - }); -}; diff --git a/website/src/rehype-base-paths.js b/website/src/rehype-base-paths.js deleted file mode 100644 index 5684d50fe..000000000 --- a/website/src/rehype-base-paths.js +++ /dev/null @@ -1,112 +0,0 @@ -/** - * Rehype plugin to prepend base path to absolute URLs - * - * Transforms: - * /img/foo.png → /BMAD-METHOD/img/foo.png (when base is /BMAD-METHOD/) - * /llms.txt → /BMAD-METHOD/llms.txt - * - * Supported elements: - * - img[src], iframe[src], video[src], source[src], audio[src] - * - a[href], link[href] - * - * Only affects absolute paths (/) - relative paths and external URLs are unchanged. - * Does NOT process .md links (those are handled by rehype-markdown-links). - */ - -import { visit } from 'unist-util-visit'; - -/** - * Create a rehype plugin that prepends the base path to absolute URLs. - * - * @param {Object} options - Plugin options - * @param {string} options.base - The base path to prepend (e.g., '/BMAD-METHOD/') - * @returns {function} A HAST tree transformer - */ -export default function rehypeBasePaths(options = {}) { - const base = options.base || '/'; - - // Normalize base: ensure trailing slash so concatenation with path.slice(1) (no leading /) - // produces correct paths like /BMAD-METHOD/img/foo.png. - // Note: rehype-markdown-links uses the opposite convention (strips trailing slash) because - // it concatenates with paths that start with /. - const normalizedBase = base === '/' ? '/' : base.endsWith('/') ? base : base + '/'; - - /** - * Prepend base path to an absolute URL attribute if needed. - * Skips protocol-relative URLs (//) and paths that already include the base. - * - * @param {object} node - HAST element node - * @param {string} attr - Attribute name ('src' or 'href') - */ - function prependBase(node, attr) { - const value = node.properties?.[attr]; - if (typeof value !== 'string' || !value.startsWith('/') || value.startsWith('//')) { - return; - } - if (normalizedBase !== '/' && !value.startsWith(normalizedBase)) { - node.properties[attr] = normalizedBase + value.slice(1); - } - } - - return (tree) => { - // Handle raw HTML blocks (inline HTML in markdown that isn't parsed into HAST elements) - if (normalizedBase !== '/') { - visit(tree, 'raw', (node) => { - // Replace absolute src="/..." and href="/..." attributes, skipping protocol-relative - // and paths that already have the base prefix - node.value = node.value.replace(/(?\b(?:src|href))="(?\/(?!\/)[^"]*)"/g, (match, attr, pathValue) => { - if (pathValue.startsWith(normalizedBase)) return match; - return `${attr}="${normalizedBase}${pathValue.slice(1)}"`; - }); - }); - } - - visit(tree, 'element', (node) => { - const tag = node.tagName; - - // Tags with src attribute - if (['img', 'iframe', 'video', 'source', 'audio'].includes(tag)) { - prependBase(node, 'src'); - } - - // Link tags with href attribute (stylesheets, preloads, etc.) - if (tag === 'link') { - prependBase(node, 'href'); - } - - // Anchor tags need special handling - skip .md links - if (tag === 'a' && node.properties?.href) { - const href = node.properties.href; - - if (typeof href !== 'string') { - return; - } - - // Only transform absolute paths starting with / (but not //) - if (!href.startsWith('/') || href.startsWith('//')) { - return; - } - - // Skip if already has the base path - if (normalizedBase !== '/' && href.startsWith(normalizedBase)) { - return; - } - - // Skip .md links - those are handled by rehype-markdown-links - // Extract path portion (before ? and #) - const firstDelimiter = Math.min( - href.indexOf('?') === -1 ? Infinity : href.indexOf('?'), - href.indexOf('#') === -1 ? Infinity : href.indexOf('#'), - ); - const pathPortion = firstDelimiter === Infinity ? href : href.substring(0, firstDelimiter); - - if (pathPortion.endsWith('.md')) { - return; // Let rehype-markdown-links handle this - } - - // Prepend base path - node.properties.href = normalizedBase + href.slice(1); - } - }); - }; -} diff --git a/website/src/rehype-markdown-links.js b/website/src/rehype-markdown-links.js deleted file mode 100644 index c0428f261..000000000 --- a/website/src/rehype-markdown-links.js +++ /dev/null @@ -1,119 +0,0 @@ -/** - * Rehype plugin to transform relative .md links into correct site URLs. - * - * Uses the source file's disk path (via vfile) to resolve the link target, - * then computes the output URL relative to the content root directory. - * This correctly handles Starlight's directory-per-page URL structure - * where ./sibling.md from reference/testing.md must become /reference/sibling/ - * (not ./sibling/ which would resolve to /reference/testing/sibling/). - * - * Supports: ./sibling.md, ../other/page.md, bare.md, /docs/absolute.md - * Preserves: query strings, hash anchors - * Skips: external URLs, non-.md links - */ - -import { visit } from 'unist-util-visit'; -import path from 'node:path'; - -/** - * @param {Object} options - * @param {string} options.base - Site base path (e.g., '/BMAD-METHOD/') - * @param {string} [options.contentDir] - Absolute path to content root; auto-detected if omitted - */ -export default function rehypeMarkdownLinks(options = {}) { - const base = options.base || '/'; - const normalizedBase = base === '/' ? '' : base.replace(/\/$/, ''); - - return (tree, file) => { - // The current file's absolute path on disk, set by Astro's markdown pipeline - const currentFilePath = file.path; - if (!currentFilePath) return; - - // Auto-detect content root: walk up from current file to find src/content/docs - const contentDir = options.contentDir || detectContentDir(currentFilePath); - if (!contentDir) { - throw new Error(`[rehype-markdown-links] Could not detect content directory for: ${currentFilePath}`); - } - - visit(tree, 'element', (node) => { - if (node.tagName !== 'a' || typeof node.properties?.href !== 'string') { - return; - } - - const href = node.properties.href; - - // Skip external links (including protocol-relative URLs like //cdn.example.com) - if (href.includes('://') || href.startsWith('//') || href.startsWith('mailto:') || href.startsWith('tel:')) { - return; - } - - // Split href into path vs query+fragment suffix - const delimIdx = findFirstDelimiter(href); - const linkPath = delimIdx === -1 ? href : href.substring(0, delimIdx); - const suffix = delimIdx === -1 ? '' : href.substring(delimIdx); - - // Only process .md links - if (!linkPath.endsWith('.md')) return; - - // Resolve the target file's absolute path on disk - let targetPath; - if (linkPath.startsWith('/docs/')) { - // Absolute /docs/ path — resolve from content root - targetPath = path.join(contentDir, linkPath.slice(5)); // strip '/docs' - } else if (linkPath.startsWith('/')) { - // Other absolute paths — resolve from content root - targetPath = path.join(contentDir, linkPath); - } else { - // Relative path (./sibling.md, ../other.md, bare.md) — resolve from current file - targetPath = path.resolve(path.dirname(currentFilePath), linkPath); - } - - // Compute the target's path relative to content root - const relativeToContent = path.relative(contentDir, targetPath); - - // Safety: skip if target resolves outside content root - if (relativeToContent.startsWith('..')) return; - - // Convert file path to URL: strip .md, handle index, ensure leading/trailing slashes - let urlPath = relativeToContent.replace(/\.md$/, ''); - - // index.md becomes the directory root - if (urlPath.endsWith('/index') || urlPath === 'index') { - urlPath = urlPath.slice(0, -'index'.length); - } - - // Build absolute URL with base path, normalizing any double slashes - const raw = normalizedBase + '/' + urlPath.replace(/\/?$/, '/') + suffix; - node.properties.href = raw.replace(/\/\/+/g, '/'); - }); - }; -} - -/** Find the index of the first ? or # in a string, or -1 if neither exists. */ -export function findFirstDelimiter(str) { - const q = str.indexOf('?'); - const h = str.indexOf('#'); - if (q === -1) return h; - if (h === -1) return q; - return Math.min(q, h); -} - -/** Walk up from a file path to find the content docs directory. */ -export function detectContentDir(filePath) { - const segments = filePath.split(path.sep); - // Look for src/content/docs in the path (standard Astro) - for (let i = segments.length - 1; i >= 2; i--) { - if (segments[i - 2] === 'src' && segments[i - 1] === 'content' && segments[i] === 'docs') { - return segments.slice(0, i + 1).join(path.sep); - } - } - // Also check for a standalone 'docs' directory (BMAD project structure) - // Path format: .../bmm/docs/file.mdx or .../bmm/website/... - for (let i = segments.length - 1; i >= 0; i--) { - if (segments[i] === 'docs') { - // Found docs directory - use its parent as the content root - return segments.slice(0, i + 1).join(path.sep); - } - } - return null; -} diff --git a/website/src/styles/custom.css b/website/src/styles/custom.css deleted file mode 100644 index 3c1c6d742..000000000 --- a/website/src/styles/custom.css +++ /dev/null @@ -1,805 +0,0 @@ -/** - * BMAD Method Documentation - Custom Styles for Starlight - * Electric Blue theme optimized for dark mode - * - * CSS Variable Mapping: - * Docusaurus → Starlight - * --ifm-color-primary → --sl-color-accent - * --ifm-background-color → --sl-color-bg - * --ifm-font-color-base → --sl-color-text - */ - -/* ============================================ - COLOR PALETTE - Light Mode - ============================================ */ -:root { - --ai-banner-height: 2.75rem; - --sl-nav-height: 6.25rem; /* Base nav height (~3.5rem) + banner height (2.75rem) */ - - /* Full-width content - override Starlight's default 45rem/67.5rem */ - --sl-content-width: 65rem; - - /* Primary accent colors - purple to match Docusaurus */ - --sl-color-accent-low: #e0e0ff; - --sl-color-accent: #5E5ED0; - --sl-color-accent-high: #3333CC; - - /* Text colors */ - --sl-color-white: #1e293b; - --sl-color-gray-1: #334155; - --sl-color-gray-2: #475569; - --sl-color-gray-3: #64748b; - --sl-color-gray-4: #94a3b8; - --sl-color-gray-5: #cbd5e1; - --sl-color-gray-6: #e2e8f0; - --sl-color-black: #f8fafc; - - /* Font settings */ - --sl-font: system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, 'Helvetica Neue', - Arial, sans-serif; - --sl-text-base: 1rem; - --sl-line-height: 1.7; - - /* Code highlighting */ - --sl-color-bg-inline-code: rgba(94, 94, 208, 0.1); -} - -/* ============================================ - COLOR PALETTE - Dark Mode (Primary Focus) - ============================================ */ -:root[data-theme='dark'] { - /* Full-width content - override Starlight's default */ - --sl-content-width: 65rem; - - /* Primary accent colors - purple to match Docusaurus */ - --sl-color-accent-low: #2a2a5a; - --sl-color-accent: #8C8CFF; - --sl-color-accent-high: #B9B9FF; - - /* Background colors */ - --sl-color-bg: #1b1b1d; - --sl-color-bg-nav: #1b1b1d; - --sl-color-bg-sidebar: #1b1b1d; - --sl-color-hairline-light: rgba(140, 140, 255, 0.1); - --sl-color-hairline: rgba(140, 140, 255, 0.15); - - /* Text colors */ - --sl-color-white: #f8fafc; - --sl-color-gray-1: #e2e8f0; - --sl-color-gray-2: #cbd5e1; - --sl-color-gray-3: #94a3b8; - --sl-color-gray-4: #64748b; - --sl-color-gray-5: #475569; - --sl-color-gray-6: #334155; - --sl-color-black: #1b1b1d; - - /* Code highlighting */ - --sl-color-bg-inline-code: rgba(140, 140, 255, 0.15); -} - -/* ============================================ - TYPOGRAPHY - ============================================ */ -.sl-markdown-content h1 { - margin-bottom: 1.5rem; -} - -.sl-markdown-content h2 { - margin-top: 2.5rem; - margin-bottom: 1rem; -} - -.sl-markdown-content h3 { - margin-top: 2rem; - margin-bottom: 0.75rem; -} - -.sl-markdown-content p { - margin-bottom: 1.25rem; -} - -/* ============================================ - SIDEBAR & NAVIGATION - Clean styling inspired by React Native docs - ============================================ */ - -/* Base transition for all sidebar links */ -.sidebar-content a { - transition: - background-color 0.15s ease, - color 0.15s ease, - border-color 0.15s ease; - border-radius: 4px; -} - -/* Top-level sidebar items (Diataxis categories) */ -.sidebar-content > ul > li > details > summary, -.sidebar-content > ul > li > a { - font-weight: 700; - font-size: 0.9375rem; - padding: 0.5rem 0.75rem; -} - -/* Nested sidebar items */ -.sidebar-content ul ul a { - font-weight: 500; - font-size: 0.875rem; - padding: 0.375rem 0.75rem; - padding-left: 1.5rem; - border-left: 3px solid transparent; -} - -/* Deep nested items */ -.sidebar-content ul ul ul a { - font-weight: 400; - font-size: 0.8125rem; - padding-left: 2.25rem; -} - -/* Active state - thin left accent bar */ -.sidebar-content a[aria-current='page'] { - background-color: rgba(94, 94, 208, 0.08); - color: var(--sl-color-accent); - border-left-color: var(--sl-color-accent); - font-weight: 600; -} - -:root[data-theme='dark'] .sidebar-content a[aria-current='page'] { - background-color: rgba(140, 140, 255, 0.1); - color: var(--sl-color-accent-high); - border-left-color: var(--sl-color-accent); -} - -/* Hover states */ -.sidebar-content a:hover { - background-color: rgba(0, 0, 0, 0.05); -} - -:root[data-theme='dark'] .sidebar-content a:hover { - background-color: rgba(255, 255, 255, 0.05); -} - -/* Section spacing */ -.sidebar-content > ul > li { - margin-top: 0.75rem; -} - -.sidebar-content > ul > li:first-child { - margin-top: 0; -} - -/* Lighter chevrons/carets */ -.sidebar-content summary::marker, -.sidebar-content details > summary::after { - opacity: 0.4; -} - -.sidebar-content summary:hover::marker, -.sidebar-content details > summary:hover::after { - opacity: 0.6; -} - -/* ============================================ - LAYOUT - Full width content - ============================================ */ -.content-panel { - width: 100%; - margin: 0 auto; -} - -/* Full-width workflow diagram iframe */ -.sl-markdown-content > iframe:first-child { - width: 100vw !important; - margin-left: calc(50% - 50vw); - border-radius: 0 !important; - border-left: none !important; - border-right: none !important; -} - -/* Main content area */ -main { - min-width: 0; -} - -.sl-markdown-content { - min-width: 0; - overflow-wrap: break-word; - word-wrap: break-word; -} - -/* Hide breadcrumbs if desired */ -/* Uncomment to hide: -nav[aria-label="Breadcrumb"] { - display: none; -} -*/ - -/* ============================================ - NAVBAR - ============================================ */ -header.header { - padding: 0 !important; /* Remove all padding for full-width banner */ - box-shadow: 0 1px 2px rgba(0, 0, 0, 0.1); - height: var(--sl-nav-height) !important; - display: flex; - flex-direction: column; -} - -header.header .header.sl-flex { - padding: 0 1.5rem; - height: calc(var(--sl-nav-height) - var(--ai-banner-height)); - width: 100%; -} - -:root[data-theme='dark'] header.header { - box-shadow: 0 1px 3px rgba(0, 0, 0, 0.3); -} - -.site-title { - font-weight: 700; - margin-left: 0; - padding-left: 0; -} - -/* Logo sizing - constrain to reasonable size */ -.site-title img { - height: 2.5rem; - width: auto; -} - -/* Social links styling */ -.social-icons a { - padding: 0.5rem; - transition: - background-color 0.15s ease, - color 0.15s ease; - border-radius: 6px; -} - -.social-icons a:hover { - background-color: rgba(0, 0, 0, 0.05); -} - -:root[data-theme='dark'] .social-icons a:hover { - background-color: rgba(255, 255, 255, 0.05); -} - -/* ============================================ - CARDS - ============================================ */ -.card { - border-radius: 12px; - border: 2px solid var(--sl-color-gray-5); - background-color: var(--sl-color-bg); - box-shadow: 0 2px 8px rgba(0, 0, 0, 0.08); - transition: - transform 0.2s ease, - box-shadow 0.2s ease, - border-color 0.2s ease; -} - -.card:hover { - transform: translateY(-3px); - border-color: var(--sl-color-accent); - box-shadow: 0 8px 24px rgba(94, 94, 208, 0.15); -} - -:root[data-theme='dark'] .card { - background: linear-gradient(145deg, rgba(30, 41, 59, 0.6), rgba(15, 23, 42, 0.8)); - border-color: rgba(140, 140, 255, 0.2); - box-shadow: 0 2px 8px rgba(0, 0, 0, 0.3); -} - -:root[data-theme='dark'] .card:hover { - border-color: rgba(140, 140, 255, 0.5); - box-shadow: - 0 8px 32px rgba(140, 140, 255, 0.2), - 0 0 0 1px rgba(140, 140, 255, 0.1); -} - -/* Starlight card grid */ -.sl-link-card { - border-radius: 12px; - border: 2px solid var(--sl-color-gray-5); - transition: - transform 0.2s ease, - box-shadow 0.2s ease, - border-color 0.2s ease; -} - -.sl-link-card:hover { - transform: translateY(-3px); - border-color: var(--sl-color-accent); -} - -:root[data-theme='dark'] .sl-link-card { - border-color: rgba(140, 140, 255, 0.2); -} - -:root[data-theme='dark'] .sl-link-card:hover { - border-color: rgba(140, 140, 255, 0.5); -} - -/* ============================================ - BUTTONS - ============================================ */ -.sl-flex a[href], -button { - transition: - background-color 0.2s ease, - transform 0.1s ease; -} - -.sl-flex a[href]:hover, -button:hover { - transform: translateY(-1px); -} - -/* ============================================ - MISC ENHANCEMENTS - ============================================ */ - -/* Prevent horizontal scrollbar from full-viewport-width breakout elements (e.g. iframe) */ -html { - overflow-x: clip; -} - -/* Smooth scrolling */ -@media (prefers-reduced-motion: no-preference) { - html { - scroll-behavior: smooth; - } -} - -/* Disable hover animations for users who prefer reduced motion */ -@media (prefers-reduced-motion: reduce) { - .card:hover, - .sl-link-card:hover { - transform: none; - } -} - -/* Better link underlines */ -.sl-markdown-content a:not(.sl-link-card) { - text-decoration-thickness: 1px; - text-underline-offset: 2px; -} - -/* Table styling */ -table { - display: table; - width: 100%; -} - -:root[data-theme='dark'] table { - border-color: rgba(140, 140, 255, 0.1); -} - -:root[data-theme='dark'] table th { - background-color: rgba(140, 140, 255, 0.05); -} - -:root[data-theme='dark'] table tr:nth-child(2n) { - background-color: rgba(140, 140, 255, 0.02); -} - -/* Blockquotes */ -blockquote { - border-left-color: var(--sl-color-accent); - background-color: rgba(94, 94, 208, 0.05); - border-radius: 0 8px 8px 0; - padding: 1rem 1.25rem; -} - -/* ============================================ - ADMONITIONS (Starlight Asides) - Rounded, no left border bar - ============================================ */ -.starlight-aside { - margin-bottom: 1.5rem; - padding: 1.25rem 1.5rem; - border-radius: 12px; - border: none; - border-left: 0; - box-shadow: 0 1px 4px rgba(0, 0, 0, 0.08); -} - -/* Tip aside */ -.starlight-aside--tip { - background-color: rgba(16, 185, 129, 0.08); -} - -.starlight-aside--tip .starlight-aside__title { - color: #047857; -} - -:root[data-theme='dark'] .starlight-aside--tip { - background-color: rgba(16, 185, 129, 0.12); -} - -:root[data-theme='dark'] .starlight-aside--tip .starlight-aside__title { - color: #34d399; -} - -/* Note aside */ -.starlight-aside--note { - background-color: rgba(94, 94, 208, 0.08); -} - -.starlight-aside--note .starlight-aside__title { - color: #5C5CCC; -} - -:root[data-theme='dark'] .starlight-aside--note { - background-color: rgba(140, 140, 255, 0.12); -} - -:root[data-theme='dark'] .starlight-aside--note .starlight-aside__title { - color: #8C8CFF; -} - -/* Caution aside */ -.starlight-aside--caution { - background-color: rgba(245, 158, 11, 0.1); -} - -.starlight-aside--caution .starlight-aside__title { - color: #a14908; -} - -:root[data-theme='dark'] .starlight-aside--caution { - background-color: rgba(245, 158, 11, 0.15); -} - -:root[data-theme='dark'] .starlight-aside--caution .starlight-aside__title { - color: #fbbf24; -} - -/* Danger aside */ -.starlight-aside--danger { - background-color: rgba(239, 68, 68, 0.1); -} - -.starlight-aside--danger .starlight-aside__title { - color: #be1c1c; -} - -:root[data-theme='dark'] .starlight-aside--danger { - background-color: rgba(239, 68, 68, 0.15); -} - -:root[data-theme='dark'] .starlight-aside--danger .starlight-aside__title { - color: #f87171; -} - -/* Aside icon styling */ -.starlight-aside__icon svg { - width: 1.25rem; - height: 1.25rem; -} - -/* ============================================ - FOOTER - No custom styling needed - The only