fix: update remaining src files and remove duplicate RULE lines from merge

- Apply explicit {interaction_style} variable reference to handler-action,
  handler-exec, handler-workflow, agent-command-header, and workflow.xml
- Remove old duplicate RULE lines left over from merge conflict resolution
  in 10 template files (default-task/tool, rovodev, opencode-workflow*,
  gemini-agent/task/tool/workflow/workflow-yaml)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

src/core/tasks/workflow.xml

@@ -2,7 +2,7 @@
   <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
 
   <llm critical="true">
-    <mandate>RULE: When interaction_style is "structured", EVERY question to the user MUST use the native question tool. No exceptions. No inline prompts. When interaction_style is "open", ask questions naturally in conversation.</mandate>
+    <mandate>RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use the native question tool. No exceptions. No inline prompts. When {interaction_style} is "open", ask questions naturally in conversation. If you cannot determine {interaction_style}, default to structured mode.</mandate>
     <mandate>Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files</mandate>
     <mandate>Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown</mandate>
     <mandate>Execute ALL steps in instructions IN EXACT ORDER</mandate>

src/utility/agent-components/agent-command-header.md

@@ -1,3 +1,3 @@
 You must fully embody this agent's persona and follow all activation instructions, steps and rules exactly as specified. NEVER break character until given an exit command.
 
-RULE: When interaction_style is "structured", EVERY question to the user MUST call the AskUserQuestion tool. Do NOT write questions as plain text. No exceptions.
+RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the AskUserQuestion tool. Do NOT write questions as plain text. No exceptions. If you cannot determine {interaction_style}, default to structured mode.

src/utility/agent-components/handler-action.txt

@@ -1,5 +1,5 @@
   <handler type="action">
     When menu item has: action="#id" → Find prompt with id="id" in current agent XML, follow its content
     When menu item has: action="text" → Follow the text directly as an inline instruction
-    RULE: When interaction_style is "structured", ALL questions to the user MUST use the AskUserQuestion tool. No plain text prompts.
+    RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", ALL questions to the user MUST use the AskUserQuestion tool. No plain text prompts. If you cannot determine {interaction_style}, default to structured mode.
   </handler>

src/utility/agent-components/handler-exec.txt

@@ -3,5 +3,5 @@
       1. Read fully and follow the file at that path
       2. Process the complete file and follow all instructions within it
       3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
-      4. RULE: When interaction_style is "structured", ALL questions to the user MUST use the AskUserQuestion tool. No plain text prompts.
+      4. RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", ALL questions to the user MUST use the AskUserQuestion tool. No plain text prompts. If you cannot determine {interaction_style}, default to structured mode.
     </handler>

src/utility/agent-components/handler-workflow.txt

@@ -7,5 +7,5 @@
       4. Follow workflow.xml instructions precisely following all steps
       5. Save outputs after completing EACH workflow step (never batch multiple steps together)
       6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
-      7. RULE: When interaction_style is "structured", ALL questions to the user MUST use the AskUserQuestion tool. No plain text prompts.
+      7. RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", ALL questions to the user MUST use the AskUserQuestion tool. No plain text prompts. If you cannot determine {interaction_style}, default to structured mode.
     </handler>

tools/cli/installers/lib/ide/templates/combined/default-task.md

@@ -10,5 +10,3 @@ RULE: Check your stored {interaction_style} session variable from activation ste
 Read the entire task file at: {project-root}/{{bmadFolderName}}/{{path}}
 
 Follow all instructions in the task file exactly as written.
-
-RULE: When interaction_style is "structured", EVERY question to the user MUST call the AskUserQuestion tool. Do NOT write questions as plain text. No exceptions.

tools/cli/installers/lib/ide/templates/combined/default-tool.md

@@ -10,5 +10,3 @@ RULE: Check your stored {interaction_style} session variable from activation ste
 Read the entire tool file at: {project-root}/{{bmadFolderName}}/{{path}}
 
 Follow all instructions in the tool file exactly as written.
-
-RULE: When interaction_style is "structured", EVERY question to the user MUST call the AskUserQuestion tool. Do NOT write questions as plain text. No exceptions.

tools/cli/installers/lib/ide/templates/combined/gemini-agent.toml

@@ -10,8 +10,6 @@ PRE-FLIGHT CHECKLIST:
 
 RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the ask_user tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to structured mode.
 
-RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
-
 Only after all checks are complete, greet the user by name and display the menu.
 Acknowledge this checklist is complete in your first response.
 

tools/cli/installers/lib/ide/templates/combined/gemini-task.toml

@@ -6,7 +6,6 @@ TASK INSTRUCTIONS:
 1. LOAD the task file from {project-root}/{{bmadFolderName}}/{{path}}
 2. READ its entire contents
 3. FOLLOW every instruction precisely as specified
-4. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
 
 RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the ask_user tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to structured mode.
 

tools/cli/installers/lib/ide/templates/combined/gemini-tool.toml

@@ -6,7 +6,6 @@ TOOL INSTRUCTIONS:
 1. LOAD the tool file from {project-root}/{{bmadFolderName}}/{{path}}
 2. READ its entire contents
 3. FOLLOW every instruction precisely as specified
-4. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
 
 RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the ask_user tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to structured mode.
 

tools/cli/installers/lib/ide/templates/combined/gemini-workflow-yaml.toml

@@ -11,7 +11,6 @@ CRITICAL: This is a structured YAML workflow. Follow these steps precisely:
    - Dependencies between steps
 3. EXECUTE each step in order
 4. VALIDATE outputs before proceeding to next step
-5. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
 
 RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the ask_user tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to structured mode.
 

tools/cli/installers/lib/ide/templates/combined/gemini-workflow.toml

@@ -9,7 +9,6 @@ WORKFLOW INSTRUCTIONS:
 2. READ its entire contents
 3. FOLLOW every step precisely as specified
 4. DO NOT skip or modify any steps
-5. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
 
 RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the ask_user tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to structured mode.
 

tools/cli/installers/lib/ide/templates/combined/opencode-workflow-yaml.md

@@ -12,7 +12,6 @@ WORKFLOW INSTRUCTIONS:
 2. READ its entire contents
 3. FOLLOW every step precisely as specified
 4. DO NOT skip or modify any steps
-5. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
 
 RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `question` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to structured mode.
 

tools/cli/installers/lib/ide/templates/combined/opencode-workflow.md

@@ -12,7 +12,6 @@ WORKFLOW INSTRUCTIONS:
 2. READ its entire contents
 3. FOLLOW every step precisely as specified
 4. DO NOT skip or modify any steps
-5. RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.
 
 RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `question` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to structured mode.
 

tools/cli/installers/lib/ide/templates/combined/rovodev.md

@@ -9,5 +9,3 @@ RULE: Check your stored {interaction_style} session variable from activation ste
 Read the entire workflow file at: {project-root}/{{bmadFolderName}}/{{workflow_path}}
 
 Follow all instructions in the workflow file exactly as written.
-
-RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.