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

_bmad/bmb/workflows/agent/steps-c/step-06-activation.md

@@ -6,13 +6,12 @@ description: 'Plan activation behavior and route to build'
 agentPlan: '{bmb_creations_output_folder}/agent-plan-{agent_name}.md'
 criticalActions: ../data/critical-actions.md
 
-# Build Step Routes (determined by agent type)
-simpleBuild: './step-07a-build-simple.md'
-expertBuild: './step-07b-build-expert.md'
-moduleBuild: './step-07c-build-module.md'
+# Build Step Route (determined by hasSidecar)
+agentBuild: './step-07-build-agent.md'
 
 # Example critical_actions (for reference)
-expertExample: ../data/reference/expert-examples/journal-keeper/journal-keeper.agent.yaml
+withSidecarExample: ../data/reference/with-sidecar/journal-keeper/journal-keeper.agent.yaml
+withoutSidecarExample: ../data/reference/without-sidecar/commit-poet.agent.yaml
 
 # Task References
 advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
@@ -20,7 +19,8 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
 # STEP GOAL
-Define activation behavior through critical_actions and route to the appropriate build step based on agent complexity.
+
+Define activation behavior through critical_actions and confirm routing to the build step based on hasSidecar decision.
 
 # MANDATORY EXECUTION RULES
 
@@ -29,9 +29,9 @@ Define activation behavior through critical_actions and route to the appropriate
    - Read agentPlan to access all accumulated metadata
    - These are non-negotiable prerequisites
 
-2. **MUST Determine Route Before Activation Discussion**
-   - Check `module` and `hasSidecar` from plan metadata
-   - Determine destination build step FIRST
+2. **MUST Confirm hasSidecar Decision**
+   - Check `hasSidecar` from plan metadata (decided in Step 3)
+   - This determines the build approach
    - Inform user of routing decision
 
 3. **MUST Document Activation Decision**
@@ -39,14 +39,11 @@ Define activation behavior through critical_actions and route to the appropriate
    - OR document deliberate omission with rationale
    - No middle ground - commit to one path
 
-4. **MUST Follow Routing Logic Exactly**
+4. **MUST Follow Simple Routing Logic**
    ```yaml
-   # Route determination based on module and hasSidecar
-   # Module agents: any module value other than "stand-alone"
-   module ≠ "stand-alone" → step-07c-build-module.md
-   # Stand-alone agents: determined by hasSidecar
-   module = "stand-alone" + hasSidecar: true → step-07b-build-expert.md
-   module = "stand-alone" + hasSidecar: false → step-07a-build-simple.md
+   # Route determination based on hasSidecar only
+   hasSidecar: false → Agent without sidecar (single YAML file)
+   hasSidecar: true → Agent with sidecar (YAML + sidecar folder)
    ```
 
 5. **NEVER Skip Documentation**
@@ -62,10 +59,9 @@ Execute BEFORE engaging user:
 1. Load criticalActions.md
 2. Load agentPlan-{agent_name}.md
 3. Extract routing metadata:
-   - hasSidecar (boolean)
-   - module (string)
-   - agentType (if defined)
-4. Determine destination build step
+   - hasSidecar (boolean) - decided in Step 3
+   - All other metadata from prior steps
+4. Confirm build approach
 
 ## Protocol 2: Routing Disclosure
 Inform user immediately of determined route:
@@ -73,9 +69,8 @@ Inform user immediately of determined route:
 ```
 "Based on your agent configuration:
 - hasSidecar: {hasSidecar}
-- module: {module}
 
-→ Routing to: {destinationStep}
+→ Building: Agent {WITH|WITHOUT} sidecar
 
 Now let's plan your activation behavior..."
 ```
@@ -106,10 +101,10 @@ activation:
   hasCriticalActions: true/false
   rationale: "Explanation of why or why not"
   criticalActions: []  # Only if hasCriticalActions: true
+
 routing:
-  destinationBuild: "step-06-{X}.md"
+  buildApproach: "Agent {with|without} sidecar"
   hasSidecar: {boolean}
-  module: "{module}"
 ```
 
 # CONTEXT BOUNDARIES
@@ -117,21 +112,22 @@ routing:
 ## In Scope
 - Planning activation behavior for the agent
 - Defining critical_actions array
-- Routing to appropriate build step
+- Confirming routing to build step
 - Documenting activation decisions
 
 ## Out of Scope
 - Writing actual activation code (build step)
 - Designing sidecar workflows (build step)
-- Changing core agent metadata (locked after step 04)
+- Changing core agent metadata (locked after Step 4)
 - Implementing commands (build step)
 
 ## Routing Boundaries
-- Simple agents: No sidecar, straightforward activation
-- Expert agents: Sidecar + stand-alone module
-- Module agents: Sidecar + parent module integration
+- **Agent WITHOUT sidecar**: Single YAML file, no persistent memory
+- **Agent WITH sidecar**: YAML file + sidecar folder with persistent memory
 
-## MANDATORY SEQUENCE
+---
+
+# MANDATORY SEQUENCE
 
 **CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
 
@@ -142,14 +138,26 @@ cat {criticalActions}
 cat {agentPlan}
 ```
 
-## 2. Discuss Activation Needs
+## 2. Confirm Routing Decision
+Verify hasSidecar decision from Step 3:
+
+```
+"Confirming your agent configuration from Step 3:
+- hasSidecar: {value from plan}
+- This means: {Agent will|will not} remember things between sessions
+- Build approach: {Single YAML file|YAML + sidecar folder}
+
+Is this still correct?"
+```
+
+## 3. Discuss Activation Needs
 Ask user:
 - "Should your agent be able to take autonomous actions?"
 - "Are there specific workflows it should trigger?"
 - "Should it run as a background process or scheduled task?"
 - "Or will it primarily respond to direct prompts?"
 
-## 3. Define critical_actions OR Explicitly Omit
+## 4. Define critical_actions OR Explicitly Omit
 
 **If defining:**
 - Reference criticalActions.md patterns
@@ -157,29 +165,27 @@ Ask user:
 - Each action should be clear and scoped
 - Document rationale for each
 
+**For agents WITH sidecar, critical_actions MUST include:**
+```
+- "Load COMPLETE file {project-root}/_bmad/_memory/{sidecar-folder}/memories.md"
+- "Load COMPLETE file {project-root}/_bmad/_memory/{sidecar-folder}/instructions.md"
+- "ONLY read/write files in {project-root}/_bmad/_memory/{sidecar-folder}/ - private space"
+```
+Plus any additional activation behaviors the agent needs.
+
+**For agents WITHOUT sidecar, critical_actions are OPTIONAL and can include:**
+```
+- "Give user an inspirational quote before showing menu"
+- "Fetch latest data from {project-root}/finances/ before displaying menu"
+- "Display a quick status summary on activation"
+```
+Agents without sidecar omit critical_actions entirely if no activation behavior is needed.
+
 **If omitting:**
 - State clearly: "This agent will not have critical_actions"
 - Explain why: "This agent is a responsive assistant that operates under direct user guidance"
 - Document the rationale
 
-## 4. Route to Build Step
-
-Determine destination:
-
-```yaml
-# Check plan metadata
-hasSidecar: {value from step 04}
-module: "{value from step 04}"
-
-# Route logic
-if hasSidecar == false:
-  destination = simpleBuild
-elif hasSidecar == true and module == "stand-alone":
-  destination = expertBuild
-else:  # hasSidecar == true and module != "stand-alone"
-  destination = moduleBuild
-```
-
 ## 5. Document to Plan
 
 Update agentPlan with:
@@ -187,21 +193,17 @@ Update agentPlan with:
 ```yaml
 ---
 activation:
-  hasCriticalActions: true
-  rationale: "Agent needs to autonomously trigger workflows for task automation"
+  hasCriticalActions: {true/false}
+  rationale: "Agent needs to autonomously trigger workflows for task automation" OR "Agent operates under direct user guidance"
   criticalActions:
     - name: "start-workflow"
       description: "Initiate a predefined workflow for task execution"
-    - name: "schedule-task"
-      description: "Schedule tasks for future execution"
-    - name: "sync-data"
-      description: "Synchronize data with external systems"
+    # ... additional actions if needed
 
 routing:
-  destinationBuild: "step-06-build-expert.md"
-  hasSidecar: true
-  module: "stand-alone"
-  rationale: "Agent requires sidecar workflows for autonomous operation"
+  buildApproach: "Agent {with|without} sidecar"
+  hasSidecar: {true/false}
+  rationale: "Agent {needs|does not need} persistent memory across sessions"
 ---
 ```
 
@@ -213,7 +215,7 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
 
 - IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
 - IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
-- IF C: Save content to {agentPlan}, update frontmatter, determine appropriate build step based on hasSidecar and module values, then only then load, read entire file, then execute {simpleBuild} or {expertBuild} or {moduleBuild} as determined
+- IF C: Save content to {agentPlan}, update frontmatter, then only then load, read entire file, then execute {agentBuild}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
 
 #### EXECUTION RULES:
@@ -225,14 +227,13 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
 
 ## CRITICAL STEP COMPLETION NOTE
 
-This is the **ROUTING HUB** of agent creation. ONLY WHEN [C continue option] is selected and [routing decision determined with activation needs documented], will you then determine the appropriate build step based on hasSidecar/module values and load and read fully that build step file to execute.
+This is the **final planning step** before building. ONLY WHEN [C continue option] is selected and [activation needs documented], will you then load and read fully `{agentBuild}` to execute and build the agent.
 
 Routing logic:
-- hasSidecar: false → step-06-build-simple.md
-- hasSidecar: true + module: "stand-alone" → step-06-build-expert.md
-- hasSidecar: true + module: ≠ "stand-alone" → step-06-build-module.md
+- hasSidecar: false → Agent WITHOUT sidecar (single YAML)
+- hasSidecar: true → Agent WITH sidecar (YAML + sidecar folder)
 
-You cannot proceed to build without completing routing.
+You cannot proceed to build without completing activation planning.
 
 ---
 
@@ -241,39 +242,36 @@ You cannot proceed to build without completing routing.
 ✅ **COMPLETION CRITERIA:**
 - [ ] criticalActions.md loaded and understood
 - [ ] agentPlan loaded with all prior metadata
-- [ ] Routing decision determined and communicated
+- [ ] Routing decision confirmed (hasSidecar from Step 3)
 - [ ] Activation needs discussed with user
 - [ ] critical_actions defined OR explicitly omitted with rationale
 - [ ] Plan updated with activation and routing metadata
-- [ ] User confirms routing to appropriate build step
+- [ ] User confirms ready to build
 
 ✅ **SUCCESS INDICATORS:**
 - Clear activation decision documented
-- Route to build step is unambiguous
-- User understands why they're going to {simple|expert|module} build
+- Route to build is unambiguous
+- User understands the build approach
 - Plan file reflects complete activation configuration
 
 ❌ **FAILURE MODES:**
 - Attempting to define critical_actions without reading reference
 - Routing decision not documented in plan
-- User doesn't understand which build step comes next
+- User doesn't understand the build approach
 - Ambiguous activation configuration (neither defined nor omitted)
-- Skipping routing discussion entirely
+- Skipping activation discussion entirely
 
-⚠️ **RECOVERY PATHS:**
+⚠️ **RECOVERY PATHS**
 If activation planning goes wrong:
 
 1. **Can't decide on activation?**
    - Default: Omit critical_actions
-   - Route to simpleBuild
    - Can add later via edit-agent workflow
 
-2. **Uncertain about routing?**
-   - Check hasSidecar value
-   - Check module value
-   - Apply routing logic strictly
-
-3. **User wants to change route?**
-   - Adjust hasSidecar or module values
-   - Re-run routing logic
+2. **User wants to change hasSidecar?**
+   - Return to Step 3 to revise decision
    - Update plan accordingly
+
+3. **Uncertain about routing?**
+   - Check hasSidecar value
+   - Apply simple routing logic