feat: Add documentation guides, simplify folder structure, and major workflow refactoring

Created two comprehensive guides for v6 features:

**docs/agent-customization-guide.md**
- Complete guide for customizing agent names, personas, memories, and behaviors
- Update-safe customization via bmad/_cfg/agents/ configuration files
- Real-world examples (TDD setup, multilingual agents, custom workflows)
- Troubleshooting and best practices

**docs/web-bundles-gemini-gpt-guide.md**
- Comprehensive guide for using BMad agents in Gemini Gems and Custom GPTs
- Critical setup rules with exact configuration text required
- Cost-saving strategy: web planning → local implementation (60-80% savings)
- Platform comparison (Gemini Gems strongly recommended over Custom GPTs)
- Complete workflow examples showing full planning-to-implementation cycle
- Team bundle guidance (Gemini 2.5 Pro+ only)

**README.md updates**
- Added prominent links in v6 Core Enhancements section
- Created new "Customization & Sharing" documentation category
- Web Bundles feature highlighted with direct guide link

**Unified output folder structure across all modules:**

**Before (confusing):**
- output_folder: Main docs
- game_design_docs: Separate design folder
- tech_docs: Separate technical folder
- dev_ephemeral_location: Separate ephemeral folder outside docs

**After (simplified):**
- output_folder: Single location for ALL AI-generated artifacts (default: "docs")
  - Clearer prompt: "Where should AI Generated Artifacts be saved?"
- sprint_artifacts: Phase 4 ephemeral content now WITHIN output_folder
  - BMM: {output_folder}/stories (stories, context, reports)
  - BMGD: {output_folder}/sprint-artifacts
  - No longer in separate {bmad_folder}-ephemeral location

**Benefits:**
- One clear location for all planning artifacts (PRD, Architecture, UX, etc.)
- Phase 4 ephemeral items logically grouped within output folder
- Eliminated confusing separate folder proliferation
- sprint_artifacts now configurable per module

**Files changed:**
- src/core/_module-installer/install-config.yaml
- src/modules/bmm/_module-installer/install-config.yaml
- src/modules/bmgd/_module-installer/install-config.yaml

**Also cleaned up BMGD config:**
- Renamed: specified_framework → primary_platform (clearer naming)
- Removed: unused data_path variable

Replaced old "project_level" (0-4) system with new "selected_track" terminology:
- **quick-flow**: Bug fixes and small features (replaces Level 0-1)
- **bmad-method**: Full planning track (replaces Level 2-3)
- **enterprise-bmad-method**: Extended planning (replaces Level 4)

**Core workflow updates:**
- solutioning-gate-check: Complete rewrite of validation logic for track-based artifacts
- architecture: Updated context detection, error handling, and messaging for tracks
- workflow-init: Updated artifact detection patterns for track-based paths
- All workflow status paths updated (method-greenfield, method-brownfield, enterprise-*)

Unified variable naming conventions across all workflows:
- {output_folder} → {output-folder} (hyphenated format)
- {dev_ephemeral_location} → {sprint_artifacts} (clearer purpose)
- Hardcoded status file paths → {workflow_status_file} variable

Fixed corrupted variable patterns throughout workflow files:
- {output*folder} → {output-folder}
- {ephemeral*location} → {sprint_artifacts}
- \_prd* → *prd* (escaped underscore artifacts)
- **\*\***\_\_\_**\*\*** → proper field placeholders

Affected patterns included malformed glob patterns, template variables, and markdown formatting artifacts from previous edits.

**Architecture workflow (create-architecture):**
- Fixed: "Decision Architecture" → "Create Architecture" (consistent naming)
- Improved PRD not found handling with exit/continue options
- Better user guidance when running standalone vs. within workflow path
- Removed hardcoded Level checks, now track-aware
- Enhanced validation checklist formatting (□ → - [])
- Typo fixes: "mulitple" → "multiple"

**Solutioning gate check:**
- Complete validation logic rewrite for track-based system
- Removed Level-specific artifact expectations
- Simplified document discovery (track determines what exists)
- Better analysis prompts and user feedback

**Workflow-init:**
- Updated artifact detection patterns for new folder structure
- Fixed corrupt glob patterns throughout
- Better sprint_artifacts location detection
- Improved workflow path assignment logic

**Various workflows:**
- Consistent variable naming across 40+ workflow files
- Improved error messages and user guidance
- Better markdown formatting (checkboxes, lists)
- Removed redundant validation criteria files (now inline)

Removed duplicate BMGD 4-production workflows (12 workflows):
- code-review, correct-course, create-story, dev-story
- epic-tech-context, retrospective, sprint-planning
- story-context, story-done, story-ready

**Why:** BMGD now uses shared BMM Phase 4 implementation workflows
**Benefit:** Single source of truth, no duplication to maintain

Also removed:
- validation-criteria.yaml (validation now inline in instructions)
- architecture-patterns.yaml references (patterns now managed differently)
- AUDIT-REPORT.md files (stale audit artifacts)

**BMB workflows:**
- Updated checklists for workflow and module creation
- Improved agent architecture documentation
- Minor instruction clarifications

**Core brainstorming workflow:**
- Updated README with usage examples
- Enhanced instructions and template clarity
- Better integration with other modules

**BMM installer:**
- Updated for track-based system
- sprint_artifacts configuration

**Tech Writer agent:**
- Minor configuration update for documentation workflows

Removed 200+ files that should not be in repository:
- Installed agent markdown files (analyst, architect, dev, pm, sm, tea, etc.)
- Complete workflow instruction copies
- Documentation duplicates (quick-start, agents-guide, workflows-*)
- Test architecture knowledge base (22 files, 14,000+ lines)
- Configuration files (config.yaml, team definitions)

These are generated during installation and should not be version controlled.

Removed 21 pre-generated XML bundles:
- BMM agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer)
- BMGD agents (game-architect, game-designer, game-dev, game-scrum-master)
- CIS agents (brainstorming-coach, creative-problem-solver, etc.)
- Team bundles (team-fullstack, team-gamedev, creative-squad)

**Why:** Users should generate fresh bundles via `npm run bundle` to get latest changes and customizations.

- **2 new documentation files** (comprehensive guides)
- **98 source files modified** (299 insertions, 6,567 deletions)
- **3 installer config files simplified** (major folder structure improvement)
- **200+ .bmad/ artifacts removed** (should not be in repo)
- **21 web-bundle files removed** (users regenerate as needed)
- **12 duplicate workflows removed** (BMGD consolidation)
- **40+ workflows updated** (track system, variable standardization, corruption fixes)

src/modules/bmm/workflows/2-plan-workflows/prd/checklist.md

@@ -296,14 +296,10 @@ If ANY of these are true, validation FAILS:
 
 ## Validation Summary
 
-**Total Validation Points:** ~85
-
-### Scoring Guide
-
-- **Pass Rate ≥ 95% (81+/85):** ✅ EXCELLENT - Ready for architecture phase
-- **Pass Rate 85-94% (72-80/85):** ⚠️ GOOD - Minor fixes needed
-- **Pass Rate 70-84% (60-71/85):** ⚠️ FAIR - Important issues to address
-- **Pass Rate < 70% (<60/85):** ❌ POOR - Significant rework required
+- **Pass Rate ≥ 95%:** ✅ EXCELLENT - Ready for architecture phase
+- **Pass Rate 85-94%:** ⚠️ GOOD - Minor fixes needed
+- **Pass Rate 70-84%:** ⚠️ FAIR - Important issues to address
+- **Pass Rate < 70%:** ❌ POOR - Significant rework required
 
 ### Critical Issue Threshold
 
@@ -316,7 +312,7 @@ If ANY of these are true, validation FAILS:
 
 **When validating:**
 
-1. **Load ALL documents:**
+1. **Load ALL documents - whole or sharded (but not both of each) for example epics.md vs epics/\*.md:**
    - PRD.md (required)
    - epics.md (required)
    - product-brief.md (if exists)

src/modules/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md

@@ -129,14 +129,14 @@ Ensure stories are:
 
 For each story in epic {{N}}, output variables following this pattern:
 
-- story*title*{{N}}_1, story_title_{{N}}\_2, etc.
+- story*title*{{N}}_1, story_title_{{N}}\*2, etc.
 - Each containing: user story, BDD acceptance criteria, prerequisites, technical notes</action>
 
 <template-output>epic*title*{{N}}</template-output>
 <template-output>epic*goal*{{N}}</template-output>
 
 <action>For each story M in epic {{N}}, generate story content</action>
-<template-output>story*title*{{N}}\_{{M}}</template-output>
+<template-output>story-title-{{N}}\_{{M}}</template-output>
 
 <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 </step>

src/modules/bmm/workflows/2-plan-workflows/tech-spec/checklist.md

@@ -13,7 +13,7 @@
 ## 1. Output Files Exist
 
 - [ ] tech-spec.md created in output folder
-- [ ] Story file(s) created in dev_ephemeral_location
+- [ ] Story file(s) created in sprint_artifacts
   - Level 0: 1 story file (story-{slug}.md)
   - Level 1: epics.md + 2-3 story files (story-{epic-slug}-N.md)
 - [ ] bmm-workflow-status.yaml updated (if not standalone mode)

src/modules/bmm/workflows/2-plan-workflows/tech-spec/epics-template.md

@@ -72,9 +72,3 @@ So that {{value_benefit}}.
 ---
 
 <!-- End epic repeat -->
-
----
-
-## Tech-Spec Reference
-
-See [tech-spec.md](../tech-spec.md) for complete technical implementation details.

src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions-level0-story.md

@@ -11,7 +11,7 @@
 
 <action>Read the completed tech-spec.md file from {output_folder}/tech-spec.md</action>
 <action>Load bmm-workflow-status.yaml from {output_folder}/bmm-workflow-status.yaml (if exists)</action>
-<action>Extract dev_ephemeral_location from config (where stories are stored)</action>
+<action>Extract sprint_artifacts from config (where stories are stored)</action>
 
 <action>Extract from the ENHANCED tech-spec structure:
 
@@ -42,7 +42,7 @@
 </example>
 
 <action>Set story_filename = "story-{slug}.md"</action>
-<action>Set story_path = "{dev_ephemeral_location}/story-{slug}.md"</action>
+<action>Set story_path = "{sprint_artifacts}/story-{slug}.md"</action>
 
 </step>
 
@@ -193,7 +193,7 @@ Only needed for extremely complex scenarios:
 2. Generate additional story context (for complex edge cases)
 3. Exit for now
 
-Select option (1-3):</ask>
+Select option (1-3)</ask>
 
 </step>
 

src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions-level1-stories.md

@@ -12,7 +12,7 @@
 
 <action>Read the completed tech-spec.md file from {output_folder}/tech-spec.md</action>
 <action>Load bmm-workflow-status.yaml from {output_folder}/bmm-workflow-status.yaml (if exists)</action>
-<action>Extract dev_ephemeral_location from config (where stories are stored)</action>
+<action>Extract sprint_artifacts from config (where stories are stored)</action>
 
 <action>Extract from the ENHANCED tech-spec structure:
 
@@ -178,7 +178,7 @@ Since tech-spec is context-rich, populate ALL template fields:
   </guidelines>
 
 <for-each story="1 to story_count">
-  <action>Set story_path_{n} = "{dev_ephemeral_location}/story-{epic_slug}-{n}.md"</action>
+  <action>Set story_path_{n} = "{sprint_artifacts}/story-{epic_slug}-{n}.md"</action>
   <action>Create story file from user_story_template with the following content:</action>
 
   <template-output file="{story_path_{n}}">
@@ -391,7 +391,7 @@ Stories are implementation-ready!</output>
 - `story-{epic_slug}-3.md` → Third story
   {{/if}}
 
-**Story Location:** `{dev_ephemeral_location}/`
+**Story Location:** `{sprint_artifacts}/`
 
 **Next Steps - Iterative Implementation:**
 

src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md

@@ -123,13 +123,13 @@ This ensures the tech-spec is grounded in reality and gives developers everythin
 Search for and load (using dual-strategy: whole first, then sharded):
 
 1. **Product Brief:**
-   - Search pattern: {output*folder}/\_brief*.md
-   - Sharded: {output*folder}/\_brief*/index.md
+   - Search pattern: {output-folder}/_brief_.md
+   - Sharded: {output-folder}/_brief_/index.md
    - If found: Load completely and extract key context
 
 2. **Research Documents:**
-   - Search pattern: {output*folder}/\_research*.md
-   - Sharded: {output*folder}/\_research*/index.md
+   - Search pattern: {output-folder}/\_research\*.md
+   - Sharded: {output-folder}/\_research\*/index.md
    - If found: Load completely and extract insights
 
 3. **Document-Project Output (CRITICAL for brownfield):**