feat: Overhaul bmad-wechat-mini-game-dev expansion pack

This commit represents a complete overhaul of the WeChat Mini-Game development expansion pack. It makes the pack fully self-contained and aligns it with a professional, platform-specific game development workflow.

Key changes include:

1.  **New Agent Roles**: Introduced `game-analyst`, `game-pm`, `game-po`, `game-orchestrator`, and `game-qa` to create a specialized game development team.

2.  **Self-Contained Pack**: Removed all dependencies on `bmad-core`. All necessary tasks, templates, and checklists have been copied into the expansion pack directory and all references have been updated to be local.

3.  **Refined Workflows**: Updated `game-dev-greenfield.yaml` and `game-prototype.yaml` to orchestrate the new agent team through a structured process, from concept to sharded stories.

4.  **Enriched Content**: Enhanced all documentation, templates, and checklists with best practices and specific considerations for WeChat Mini-Game development, including performance, API usage, subpackages, and monetization.

5.  **Simplified Outputs**: Updated templates to produce cleaner, more direct output paths for generated documents (e.g., `docs/brief.md`).

expansion-packs/bmad-wechat-mini-game-dev/tasks/nfr-assess.md

@@ -9,11 +9,11 @@ Quick NFR validation focused on the core four: security, performance, reliabilit
 ```yaml
 required:
   - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: `bmad-core/core-config.yaml` for the `devStoryLocation`
+  - story_path: 'Path to the development story file.'
 
 optional:
-  - architecture_refs: `bmad-core/core-config.yaml` for the `architecture.architectureFile`
-  - technical_preferences: `bmad-core/core-config.yaml` for the `technicalPreferences`
+  - architecture_refs: 'Path to the architecture document.'
+  - technical_preferences: 'Path to the technical preferences document.'
   - acceptance_criteria: From story file
 ```
 

expansion-packs/bmad-wechat-mini-game-dev/tasks/qa-gate.md

@@ -16,7 +16,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision
 
 ## Gate File Location
 
-**ALWAYS** check the `bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
+**ALWAYS** check the project's configuration for the QA gates location (e.g., `docs/qa/gates`).
 
 Slug rules:
 
@@ -126,7 +126,7 @@ waiver:
 
 ## Output Requirements
 
-1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `bmad-core/core-config.yaml`
+1. **ALWAYS** create gate file at the configured QA gates location (e.g., `docs/qa/gates`).
 2. **ALWAYS** append this exact format to story's QA Results section:
 
    ```text

expansion-packs/bmad-wechat-mini-game-dev/tasks/review-story.md

@@ -9,7 +9,7 @@ Perform a comprehensive test architecture review with quality gate decision. Thi
 ```yaml
 required:
   - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: '{devStoryLocation}/{epic}.{story}.*.md' # Path from core-config.yaml
+  - story_path: '{devStoryLocation}/{epic}.{story}.*.md' # Path provided by the project setup.
   - story_title: '{title}' # If missing, derive from story file H1
   - story_slug: '{slug}' # If missing, derive from title (lowercase, hyphenated)
 ```
@@ -173,7 +173,7 @@ Gate: {STATUS} → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
 Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
 NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
 
-# Note: Paths should reference core-config.yaml for custom configurations
+# Note: Paths should be based on the project's defined structure.
 
 ### Recommended Status
 
@@ -186,7 +186,7 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
 **Template and Directory:**
 
 - Render from `../templates/qa-gate-tmpl.yaml`
-- Create directory defined in `qa.qaLocation/gates` (see `bmad-core/core-config.yaml`) if missing
+- Create the QA gates directory (e.g., `docs/qa/gates`) if it is missing.
 - Save to: `qa.qaLocation/gates/{epic}.{story}-{slug}.yml`
 
 Gate file structure:

expansion-packs/bmad-wechat-mini-game-dev/tasks/test-design.md

@@ -9,7 +9,7 @@ Create comprehensive test scenarios with appropriate test level recommendations
 ```yaml
 required:
   - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: '{devStoryLocation}/{epic}.{story}.*.md' # Path from core-config.yaml
+  - story_path: '{devStoryLocation}/{epic}.{story}.*.md' # Path provided by the project setup.
   - story_title: '{title}' # If missing, derive from story file H1
   - story_slug: '{slug}' # If missing, derive from title (lowercase, hyphenated)
 ```