feat(ux): fix focus swipe animation, button visibility and mobile scroll

_bmad/bmb/workflows/module/steps-v/step-02-file-structure.md

@@ -3,7 +3,7 @@ name: 'step-02-file-structure'
 description: 'Validate file structure compliance'
 
 nextStepFile: './step-03-module-yaml.md'
-moduleStandardsFile: '../../data/module-standards.md'
+moduleStandardsFile: '../data/module-standards.md'
 validationReportOutput: '{validation_report_output}'
 ---
 
@@ -40,7 +40,6 @@ Check based on target type:
 - [ ] README.md exists
 - [ ] agents/ folder exists (if agents specified)
 - [ ] workflows/ folder exists (if workflows specified)
-- [ ] _module-installer/ folder (if installer specified)
 
 **For Briefs:**
 - [ ] Brief file exists

_bmad/bmb/workflows/module/steps-v/step-03-module-yaml.md

@@ -3,7 +3,7 @@ name: 'step-03-module-yaml'
 description: 'Validate module.yaml against conventions'
 
 nextStepFile: './step-04-agent-specs.md'
-moduleYamlConventionsFile: '../../data/module-yaml-conventions.md'
+moduleYamlConventionsFile: '../data/module-yaml-conventions.md'
 validationReportOutput: '{validation_report_output}'
 targetPath: '{validation_target_path}'
 ---

_bmad/bmb/workflows/module/steps-v/step-04-agent-specs.md

@@ -3,8 +3,8 @@ name: 'step-04-agent-specs'
 description: 'Validate agent specifications and built agents'
 
 nextStepFile: './step-05-workflow-specs.md'
-agentSpecTemplate: '../../templates/agent-spec-template.md'
-agentArchitectureFile: '../../data/agent-architecture.md'
+agentSpecTemplate: '../data/agent-spec-template.md'
+agentArchitectureFile: '../data/agent-architecture.md'
 agentValidationWorkflow: '{project-root}/_bmad/bmb/workflows/agent/steps-v/step-01-validate.md'
 validationReportOutput: '{validation_report_output}'
 targetPath: '{validation_target_path}'

_bmad/bmb/workflows/module/steps-v/step-05-workflow-specs.md

@@ -3,7 +3,7 @@ name: 'step-05-workflow-specs'
 description: 'Validate workflow specifications and built workflows'
 
 nextStepFile: './step-06-documentation.md'
-workflowSpecTemplate: '../../templates/workflow-spec-template.md'
+workflowSpecTemplate: '../templates/workflow-spec-template.md'
 workflowValidationWorkflow: '{project-root}/_bmad/bmb/workflows/workflow/steps-v/step-01-validate.md'
 validationReportOutput: '{validation_report_output}'
 targetPath: '{validation_target_path}'

_bmad/bmb/workflows/module/steps-v/step-07-installation.md

@@ -3,9 +3,10 @@ name: 'step-07-installation'
 description: 'Installation readiness check'
 
 nextStepFile: './step-08-report.md'
-moduleInstallerStandardsFile: '../../data/module-installer-standards.md'
+moduleHelpGenerateWorkflow: '../module-help-generate.md'
 validationReportOutput: '{validation_report_output}'
 targetPath: '{validation_target_path}'
+moduleHelpCsvFile: '{validation_target_path}/module-help.csv'
 ---
 
 # Step 7: Installation Readiness
@@ -29,35 +30,7 @@ Check if the module is ready for installation.
 
 ## MANDATORY SEQUENCE
 
-### 1. Check Installer
-
-**IF `_module-installer/` exists:**
-- [ ] `installer.js` present
-- [ ] Has valid `install()` function
-- [ ] Platform-specific handlers (if any IDEs supported)
-
-**IF `_module-installer/` doesn't exist:**
-- Note: Module may not need installer
-- Check if this is intentional
-
-### 2. Validate installer.js (if present)
-
-Load `{moduleInstallerStandardsFile}` and check:
-
-**Function Signature:**
-- [ ] `async function install(options)`
-- [ ] Accepts: projectRoot, config, installedIDEs, logger
-- [ ] Returns: Promise<boolean>
-
-**Error Handling:**
-- [ ] Try/catch block present
-- [ ] Error logging present
-
-**Platform Validation:**
-- [ ] Uses platformCodes for IDE validation
-- [ ] Graceful handling of unknown platforms
-
-### 3. Check module.yaml Install Variables
+### 1. Check module.yaml Install Variables
 
 **IF custom variables exist:**
 - [ ] All variables have prompts
@@ -68,7 +41,22 @@ Load `{moduleInstallerStandardsFile}` and check:
 - [ ] Paths use `{project-root}/` prefix
 - [ ] Output paths are user-configurable
 
-### 4. Module Type Installation
+### 2. Check module-help.csv
+
+**CRITICAL:** Every module must have `module-help.csv` at its root.
+
+**Check:**
+- [ ] `module-help.csv` exists at `{moduleHelpCsvFile}`
+- [ ] Has valid header: `module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,`
+- [ ] `anytime` entries at TOP with EMPTY sequence
+- [ ] Phased entries BELOW anytime (phase-1, phase-2, etc.)
+- [ ] Agent-only entries have EMPTY `workflow-file`
+
+**If missing:**
+- FAIL - Module is not ready for installation without help registry
+- Suggest running `{moduleHelpGenerateWorkflow}`
+
+### 3. Module Type Installation
 
 **IF Extension:**
 - [ ] `code:` matches base (for proper merge)
@@ -78,7 +66,7 @@ Load `{moduleInstallerStandardsFile}` and check:
 - [ ] `global: true` or documented
 - [ ] Global impact is minimal/intentional
 
-### 5. Record Results
+### 4. Record Results
 
 Append to `{validationReportOutput}`:
 
@@ -87,15 +75,16 @@ Append to `{validationReportOutput}`:
 
 **Status:** {PASS/FAIL/WARNINGS}
 
-**Installer:** {present/missing} - {status}
 **Install Variables:** {count} variables
+**Install Variables:** {count} variables
+**Help Registry:** {present/missing} - {status}
 **Ready to Install:** {yes/no}
 
 **Issues Found:**
 {list any issues}
 ```
 
-### 6. Auto-Proceed
+### 5. Auto-Proceed
 
 "**✓ Installation readiness check complete.**"
 
@@ -108,6 +97,6 @@ Load `{nextStepFile}`
 ## Success Metrics
 
 ✅ Installation readiness assessed
-✅ Installer validated (if present)
+✅ module-help.csv presence and structure validated
 ✅ Module type compatibility checked
 ✅ Results recorded