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

_bmad/bmb/workflows/workflow/data/architecture.md

@@ -21,39 +21,39 @@ workflow-folder/
 
 ---
 
-## workflow.md File Standards
+## workflow.md Standards
 
-**CRITICAL:** The workflow.md file MUST be lean. It is the entry point and should NOT contain:
+**CRITICAL:** workflow.md MUST be lean — entry point only.
 
-- ❌ **Listing of all steps** - This defeats progressive disclosure
-- ❌ **Detailed descriptions of what each step does** - Steps are self-documenting
-- ❌ **Validation checklists** - These belong in steps-v/, not workflow.md
-- ❌ **Implementation details** - These belong in step files
+**❌ PROHIBITED:**
+- Listing all steps (defeats progressive disclosure)
+- Detailed step descriptions (steps are self-documenting)
+- Validation checklists (belong in steps-v/)
+- Implementation details (belong in step files)
 
-**The workflow.md SHOULD contain:**
-- ✅ Frontmatter: name, description, web_bundle
-- ✅ Goal: What the workflow accomplishes
-- ✅ Role: Who the AI embodies when running this workflow
-- ✅ Meta-context: Background about the architecture (if demonstrating a pattern)
-- ✅ Core architecture principles (step-file design, JIT loading, etc.)
-- ✅ Initialization/routing: How to start and which step to load first
+**✅ REQUIRED:**
+- Frontmatter: name, description, web_bundle
+- Goal: What the workflow accomplishes
+- Role: Who the AI embodies
+- Meta-context: Architecture background (if pattern demo)
+- Core principles (step-file design, JIT loading, etc.)
+- Initialization/routing: How to start, which step first
 
-**Progressive Disclosure Rule:**
-Users should ONLY know about the current step they're executing. The workflow.md routes to the first step, and each step routes to the next. No step lists in workflow.md!
+**Progressive Disclosure:** Users ONLY know about current step. workflow.md routes to first step, each step routes to next. No step lists in workflow.md!
 
 ---
 
 ## Core Principles
 
 ### 1. Micro-File Design
-- Each step is a focused file (~80-200 lines)
+- Each step: ~80-200 lines, focused
 - One concept per step
 - Self-contained instructions
 
 ### 2. Just-In-Time Loading
-- Only current step file is in memory
-- Never load future steps until user selects 'C'
-- Progressive disclosure - LLM stays focused
+- Only current step in memory
+- Never load future steps until 'C' selected
+- Progressive disclosure = LLM focus
 
 ### 3. Sequential Enforcement
 - Steps execute in order
@@ -67,28 +67,27 @@ stepsCompleted: ['step-01-init', 'step-02-gather', 'step-03-design']
 lastStep: 'step-03-design'
 lastContinued: '2025-01-02'
 ```
-
 Each step appends its name to `stepsCompleted` before loading next.
 
 ---
 
 ## Execution Flow
 
-### Fresh Start
+**Fresh Start:**
 ```
 workflow.md → step-01-init.md → step-02-[name].md → ... → step-N-final.md
 ```
 
-### Continuation (Resumed)
+**Continuation:**
 ```
-workflow.md → step-01-init.md (detects existing) → step-01b-continue.md → [appropriate next step]
+workflow.md → step-01-init.md (detects existing) → step-01b-continue.md → [next step]
 ```
 
 ---
 
 ## Frontmatter Variables
 
-### Standard (All Workflows)
+### Standard
 ```yaml
 workflow_path: '{project-root}/_bmad/[module]/workflows/[name]'
 thisStepFile: './step-[N]-[name].md'
@@ -98,11 +97,10 @@ outputFile: '{output_folder}/[output].md'
 
 ### Module-Specific
 ```yaml
-# BMB example:
 bmb_creations_output_folder: '{project-root}/_bmad/bmb-creations'
 ```
 
-### Critical Rules
+### Rules
 - ONLY variables used in step body go in frontmatter
 - All file references use `{variable}` format
 - Paths within workflow folder are relative
@@ -133,7 +131,7 @@ Display: "**Select:** [A] [action] [P] [action] [C] Continue"
 
 ## Output Pattern
 
-Every step writes to a document BEFORE loading next step:
+Every step writes BEFORE loading next:
 
 1. **Plan-then-build:** Steps append to plan.md → build step consumes plan
 2. **Direct-to-final:** Steps append directly to final document