fix: alphabetize agent commands and dependencies for improved organization

- Alphabetized all commands in agent files while maintaining help first and exit last
- Alphabetized all dependency categories (checklists, data, tasks, templates, utils, workflows)
- Alphabetized items within each dependency category across all 10 core agents:
  - analyst.md: commands and dependencies reorganized
  - architect.md: commands and dependencies reorganized
  - bmad-master.md: commands and dependencies reorganized, fixed YAML parsing issue
  - bmad-orchestrator.md: commands and dependencies reorganized
  - dev.md: commands and dependencies reorganized
  - pm.md: commands and dependencies reorganized
  - po.md: commands and dependencies reorganized
  - qa.md: commands and dependencies reorganized
  - sm.md: commands and dependencies reorganized
  - ux-expert.md: commands and dependencies reorganized
- Fixed YAML parsing error in bmad-master.md by properly quoting activation instructions
- Rebuilt all agent bundles and team bundles successfully
- Updated expansion pack bundles including new creative writing agents

This improves consistency and makes it easier to locate specific commands and dependencies
across all agent configurations.

dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-sm.txt

@@ -514,8 +514,8 @@ template:
   version: 3.0
   output:
     format: markdown
-    filename: 'stories/{{epic_name}}/{{story_id}}-{{story_name}}.md'
-    title: 'Story: {{story_title}}'
+    filename: "stories/{{epic_name}}/{{story_id}}-{{story_name}}.md"
+    title: "Story: {{story_title}}"
 
 workflow:
   mode: interactive
@@ -544,7 +544,7 @@ sections:
   - id: description
     title: Description
     instruction: Provide a clear, concise description of what this story implements. Focus on the specific game feature or system being built. Reference the GDD section that defines this feature.
-    template: '{{clear_description_of_what_needs_to_be_implemented}}'
+    template: "{{clear_description_of_what_needs_to_be_implemented}}"
 
   - id: acceptance-criteria
     title: Acceptance Criteria
@@ -554,7 +554,7 @@ sections:
         title: Functional Requirements
         type: checklist
         items:
-          - '{{specific_functional_requirement}}'
+          - "{{specific_functional_requirement}}"
       - id: technical-requirements
         title: Technical Requirements
         type: checklist
@@ -562,14 +562,14 @@ sections:
           - Code follows C# best practices
           - Maintains stable frame rate on target devices
           - No memory leaks or performance degradation
-          - '{{specific_technical_requirement}}'
+          - "{{specific_technical_requirement}}"
       - id: game-design-requirements
         title: Game Design Requirements
         type: checklist
         items:
-          - '{{gameplay_requirement_from_gdd}}'
-          - '{{balance_requirement_if_applicable}}'
-          - '{{player_experience_requirement}}'
+          - "{{gameplay_requirement_from_gdd}}"
+          - "{{balance_requirement_if_applicable}}"
+          - "{{player_experience_requirement}}"
 
   - id: technical-specifications
     title: Technical Specifications
@@ -744,7 +744,7 @@ sections:
       - Performance targets met
       - No C# compiler errors or warnings
       - Documentation updated
-      - '{{game_specific_dod_item}}'
+      - "{{game_specific_dod_item}}"
 
   - id: notes
     title: Notes