fix: standardize on file extension .yaml instead of a mix of yml and yaml

dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt

@@ -117,7 +117,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
 
 ### 0. Check Workflow Plan (if configured)
 
-[[LLM: Check if plan tracking is enabled in core-config.yml]]
+[[LLM: Check if plan tracking is enabled in core-config.yaml]]
 
 - If `workflow.trackProgress: true`, check for active plan using utils#plan-management
 - If plan exists and this document creation is part of the plan:

dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt

@@ -1004,7 +1004,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
 
 ### 0. Check Workflow Plan (if configured)
 
-[[LLM: Check if plan tracking is enabled in core-config.yml]]
+[[LLM: Check if plan tracking is enabled in core-config.yaml]]
 
 - If `workflow.trackProgress: true`, check for active plan using utils#plan-management
 - If plan exists and this document creation is part of the plan:
@@ -2969,7 +2969,7 @@ Update the status of steps in an active workflow plan, mark completions, add not
 
 ### 0. Load Plan Configuration
 
-[[LLM: First load core-config.yml to get plan settings]]
+[[LLM: First load core-config.yaml to get plan settings]]
 
 Check workflow configuration:
 
@@ -3225,7 +3225,7 @@ Provides utilities for agents and tasks to interact with workflow plans, check p
 ```
 Check for workflow plan:
 1. Look for docs/workflow-plan.md (default location)
-2. Check core-config.yml for custom plan location
+2. Check core-config.yaml for custom plan location
 3. Return plan status (exists/not exists)
 ```
 
@@ -7110,7 +7110,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 - {{future_optimization_1}}
 ==================== END: templates#game-story-tmpl ====================
 
-==================== START: workflows#game-dev-greenfield ====================
+==================== START: workflows#game-dev-greenfield.yaml ====================
 workflow:
   id: game-dev-greenfield
   name: Game Development - Greenfield Project
@@ -7294,9 +7294,9 @@ workflow:
       - Testing framework in place
       - Team roles and responsibilities defined
       - First implementation stories created and ready
-==================== END: workflows#game-dev-greenfield ====================
+==================== END: workflows#game-dev-greenfield.yaml ====================
 
-==================== START: workflows#game-prototype ====================
+==================== START: workflows#game-prototype.yaml ====================
 workflow:
   id: game-prototype
   name: Game Prototype Development
@@ -7472,4 +7472,4 @@ workflow:
     technical_to_stories: Technical plan complete. Create focused implementation stories for prototype development.
     stories_to_implementation: Stories ready. Begin iterative implementation with frequent playtesting and design validation.
     prototype_to_evaluation: Prototype playable. Evaluate core mechanics, gather feedback, and determine next development steps.
-==================== END: workflows#game-prototype ====================
+==================== END: workflows#game-prototype.yaml ====================

dist/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.txt

@@ -586,7 +586,7 @@ IMPORTANT: Only proceed after plan.md is approved
 expansion-packs/
 └── {pack-name}/
 ├── plan.md (ALREADY CREATED)
-├── manifest.yml
+├── manifest.yaml
 ├── README.md
 ├── agents/
 │ ├── {pack-name}-orchestrator.md (REQUIRED - Custom themed orchestrator)
@@ -609,13 +609,13 @@ expansion-packs/
 ├── workflows/
 │ └── {domain}-workflow.md (REQUIRED if multiple agents)
 └── agent-teams/
-└── {domain}-team.yml (REQUIRED if multiple agents)
+└── {domain}-team.yaml (REQUIRED if multiple agents)
 
 ```
 
 #### 3.2 Create Manifest
 
-Create `manifest.yml`:
+Create `manifest.yaml`:
 
 ```yaml
 name: {pack-name}
@@ -658,7 +658,7 @@ files:
     - {domain}-workflow.md        # REQUIRED if multiple agents - decision trees
 
   agent-teams:
-    - {domain}-team.yml           # REQUIRED if multiple agents - team config
+    - {domain}-team.yaml          # REQUIRED if multiple agents - team config
 
 # Data files users must provide (in their bmad-core/data/ directory)
 required_user_data:
@@ -794,7 +794,7 @@ cp common/utils/workflow-management.md expansion-packs/{pack-name}/utils/
 1. Design decision trees for workflow branching
 2. Create handoff protocols to specialist agents
 3. Implement validation loops and quality checkpoints
-4. **If multiple agents**: Create team configuration in `agent-teams/{domain}-team.yml`
+4. **If multiple agents**: Create team configuration in `agent-teams/{domain}-team.yaml`
 5. **If multiple agents**: Create workflow in `workflows/{domain}-workflow.md`
 6. Ensure orchestrator references workflow-management utility
 7. Verify ALL referenced tasks exist (including core utilities)
@@ -965,7 +965,7 @@ Before declaring complete:
 
 1. [ ] Decision trees and workflow orchestration complete
 2. [ ] Knowledge base files embedded (best practices, terminology, standards)
-3. [ ] Manifest.yml reflects all components and dependencies
+3. [ ] Manifest.yaml reflects all components and dependencies
 4. [ ] All items in plan.md marked complete
 5. [ ] No orphaned tasks or templates
 
@@ -1072,7 +1072,7 @@ These files are automatically available to all agents and don't require user set
 ```text
 healthcare/
 ├── plan.md (Created first for approval)
-├── manifest.yml (with dependency mapping and character descriptions)
+├── manifest.yaml (with dependency mapping and character descriptions)
 ├── README.md (featuring character introductions and numbered options)
 ├── agents/
 │   ├── healthcare-orchestrator.md (Dr. Sarah Chen - YAML-in-Markdown)
@@ -1098,7 +1098,7 @@ healthcare/
 │   ├── clinical-trial-workflow.md (decision trees with Mermaid diagrams)
 │   └── compliance-audit-workflow.md (handoff protocols and quality gates)
 └── agent-teams/
-    └── healthcare-team.yml (coordinated team configurations)
+    └── healthcare-team.yaml (coordinated team configurations)
 
 Required user data files (bmad-core/data/):
 - medical-terminology.md (institution-specific terms and abbreviations)
@@ -1309,7 +1309,7 @@ Embedded knowledge (automatic):
 - [ ] All agent references verified (tasks, templates, data, checklists)
 - [ ] Data requirements documented with validation criteria and examples
 - [ ] README includes character introductions and numbered options explanation
-- [ ] manifest.yml reflects actual files with dependency mapping and character descriptions
+- [ ] manifest.yaml reflects actual files with dependency mapping and character descriptions
 
 **Advanced Quality Gates:**
 
@@ -1732,7 +1732,7 @@ Present these numbered options to the user:
 
 CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
-```yml
+```yaml
 activation-instructions:
     - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
     - Only read the files/tasks listed here when user selects them for execution to minimize context usage

dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt

@@ -118,7 +118,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
 
 ### 0. Check Workflow Plan (if configured)
 
-[[LLM: Check if plan tracking is enabled in core-config.yml]]
+[[LLM: Check if plan tracking is enabled in core-config.yaml]]
 
 - If `workflow.trackProgress: true`, check for active plan using utils#plan-management
 - If plan exists and this document creation is part of the plan:
@@ -1300,7 +1300,7 @@ kind: ConfigMap
 metadata:
   name: prometheus-config
 data:
-  prometheus.yml: |
+  prometheus.yaml: |
     global:
       scrape_interval: {{scrape_interval}}
     scrape_configs: