chore(release): Prepare release v7.1.1

Refs: General

Author: jezweb

.builds/README.md

@@ -10,4 +10,5 @@ This file tracks the distributable builds created for Roo Commander.
 - **v7.0.4 (Wallaby)** - 2025-04-21 - File: `roo-commander-v7.0.4-Wallaby.zip`
 - **v7.0.5 (Wallaby)** - 2025-04-21 - File: `roo-commander-v7.0.5-Wallaby.zip`
 - **v7.0.6 (Wallaby)** - 2025-04-23 - File: `roo-commander-v7.0.6-Wallaby.zip`
-- **v7.1.0 (Wallaby)** - 2025-04-23 - File: \`roo-commander-v7.1.0-Wallaby.zip\`
+- **v7.1.0 (Wallaby)** - 2025-04-23 - File: \`roo-commander-v7.1.0-Wallaby.zip\`
+- **v7.1.1 (Wallaby)** - 2025-04-24 - File: \`roo-commander-v7.1.1-Wallaby.zip\`

.roo/mcp.json

@@ -0,0 +1,53 @@
+{
+  "mcpServers": {
+    "vertex-ai-mcp-server": {
+      "command": "node",
+      "args": [
+        "/home/jez/vscode/roo-commander/mcp-servers/vertex-ai/build/index.js"
+      ],
+      "env": {
+        "GOOGLE_CLOUD_PROJECT": "jeremy-roocode-04",
+        "GOOGLE_CLOUD_LOCATION": "us-central1",
+        "GOOGLE_APPLICATION_CREDENTIALS": "/home/jez/vscode/vertexai-keys/jeremy-roocode-04-vertexai.json"
+      },
+      "disabled": false,
+      "alwaysAllow": [
+        "answer_query_websearch",
+        "answer_query_direct",
+        "explain_topic_with_docs",
+        "get_doc_snippets",
+        "generate_project_guidelines",
+        "read_file_content",
+        "read_multiple_files_content",
+        "write_file_content",
+        "edit_file_content",
+        "create_directory",
+        "list_directory_contents",
+        "get_directory_tree",
+        "move_file_or_directory",
+        "search_filesystem",
+        "get_filesystem_info",
+        "save_generate_project_guidelines",
+        "save_doc_snippet",
+        "save_topic_explanation",
+        "save_answer_query_direct",
+        "save_answer_query_websearch"
+      ],
+      "timeout": 3600
+    },
+    "upsplash-mcp-server": {
+      "description": "Provides access to Unsplash images.",
+      "command": "bun",
+      "args": [
+        ".ruru/mcp-servers/upsplash-mcp-server/build/index.js"
+      ],
+      "env": {"UNSPLASH_ACCESS_KEY": "XPFQELdkM0AlaXLKUtXfV53264qJzFBptdDy7b4t-KY" },
+      "alwaysAllow": [
+        "search_photos",
+        "download_photo"
+      ],
+      "disabled": false,
+      "timeout": 3600
+    }
+  }
+}

.roo/rules-agent-mcp-manager/01-initialization-rule.md

@@ -0,0 +1,60 @@
++++
+id = "AGENT-MCP-MANAGER-RULE-INIT-V1"
+title = "MCP Manager Agent: Rule - Initial Request Processing"
+context_type = "rules"
+scope = "Initial user interaction handling for MCP installation and management and management"
+target_audience = ["agent-mcp-manager"]
+granularity = "procedure"
+status = "active"
+last_updated = "2025-04-24" # Use current date
+tags = ["rules", "workflow", "initialization", "mcp", "install", "manage", "update", "agent-mcp-manager"]
+related_context = [
+    ".ruru/modes/agent-mcp-manager/agent-mcp-manager.mode.md",
+    # Specific KB Action files
+    ".ruru/modes/agent-mcp-manager/kb/install-vertex-ai.md",
+    ".ruru/modes/agent-mcp-manager/kb/install-unsplash.md",
+    ".ruru/modes/agent-mcp-manager/kb/install-custom-url.md",
+    ".ruru/modes/agent-mcp-manager/kb/remove-mcp-server.md" # Added remove KB
+    ]
+template_schema_doc = ".ruru/templates/toml-md/16_ai_rule.README.md"
+relevance = "Critical: Defines the entry point for the MCP installer mode"
++++
+
+# Rule: Initial Request Processing (MCP Manager Agent)
+
+This rule governs how you handle the initial interaction when activated, presenting MCP server installation and management options and routing to specific KB procedures.
+
+**Standard Initial Prompt:**
+
+```xml
+ <ask_followup_question>
+  <question>Welcome to the MCP Manager Agent! What would you like to do?</question>
+  <follow_up>
+    <suggest>🔌 Install Vertex AI Server</suggest> <!-- Option 1 -->
+    <suggest>🖼️ Install Unsplash Image Server (Placeholder)</suggest> <!-- Option 2 -->
+    <suggest>🌐 Install Custom Server from Git URL (Placeholder)</suggest> <!-- Option 3 -->
+    <suggest>🗑️ Remove an existing MCP Server</suggest> <!-- Option 4 -->
+    <suggest>🔄 Check for MCP Server Updates (Placeholder)</suggest> <!-- Option 5 -->
+    <suggest>❌ Cancel</suggest> <!-- Option 6 -->
+  </follow_up>
+ </ask_followup_question>
+```
+
+**Procedure:**
+
+1.  **Present Options:** Present the **Standard Initial Prompt** (defined above) using `<ask_followup_question>`.
+2.  **Await User Selection:** Wait for the user's choice.
+3.  **Handle User Selection:**
+    *   Once the user selects an option:
+        1.  Identify the selected option.
+        2.  Log the chosen installation path.
+        3.  **Execute the detailed procedure defined in the corresponding KB file (adding placeholders for new options) (adding placeholders for new options)**:
+            *   Option 1 (Vertex AI): Execute KB `.ruru/modes/agent-mcp-manager/kb/install-vertex-ai.md`.
+            *   Option 2 (Unsplash): Execute KB `.ruru/modes/agent-mcp-manager/kb/install-unsplash.md`. (Currently a placeholder).
+            *   Option 3 (Custom URL): Execute KB `.ruru/modes/agent-mcp-manager/kb/install-custom-url.md`. (Currently a placeholder).
+            *   Option 4 (Remove): Execute KB `.ruru/modes/agent-mcp-manager/kb/remove-mcp-server.md`.
+            *   Option 5 (Update): Execute KB `.ruru/modes/agent-mcp-manager/kb/check-updates.md`. (Placeholder).
+            *   Option 6 (Cancel): Report cancellation to the coordinator (`roo-commander`) using `<attempt_completion>`. **Stop.**
+        4.  Follow the steps within that specific KB procedure. **End this initialization workflow** upon completion or cancellation of the KB procedure.
+
+**Key Objective:** To provide clear installation and management options and route the user interaction to the precise, detailed procedure stored in the relevant Knowledge Base file for the selected MCP server or management task.

.roo/rules-agent-mcp-manager/99-kb-lookup-rule.md

@@ -0,0 +1,37 @@
++++
+id = "AGENT-MCP-MANAGER-RULE-KB-LOOKUP-V1"
+title = "MCP Manager Agent: Rule - KB Lookup Trigger"
+context_type = "rules"
+scope = "Mode-specific knowledge base access conditions"
+target_audience = ["agent-mcp-manager"]
+granularity = "procedure"
+status = "active"
+last_updated = "2025-04-24" # Use current date
+tags = ["rules", "kb-lookup", "knowledge-base", "context", "reference", "agent-mcp-manager"]
+related_context = [
+    ".ruru/modes/agent-mcp-manager/kb/",
+    ".ruru/modes/agent-mcp-manager/kb/README.md",
+    ".roo/rules-agent-mcp-manager/01-initialization-rule.md"
+    ]
+template_schema_doc = ".ruru/templates/toml-md/16_ai_rule.README.md"
+relevance = "Critical: Defines how the mode accesses its specific procedures"
++++
+
+# Rule: KB Lookup Trigger (MCP Manager Agent)
+
+This rule defines when you **MUST** consult the detailed Knowledge Base (KB) located in `.ruru/modes/agent-mcp-manager/kb/`.
+
+**Consult the KB When:**
+
+1.  **Executing Installation:** After the user selects an installation or management option (Vertex AI, Unsplash, Custom URL) via the `01-initialization-rule.md`, you **MUST** read and follow the procedure defined in the corresponding KB file (e.g., `kb/install-vertex-ai.md`, `kb/install-custom-url.md`, `kb/check-updates.md`, `kb/check-updates.md`).
+2.  **Checking Prerequisites:** Before starting any installation or update process or update process, consult the relevant KB file to identify the specific prerequisites (tools, authentication methods) required for that server/task.
+3.  **Handling Configuration:** Refer to the KB file for guidance on what configuration details to prompt the user for and how to structure the `.env` file or update `.roo/mcp.json`.
+4.  **Needing Specific Commands:** Use the KB file as the source for specific `git clone` URLs, `git pull` commands, dependency installation commands (`bun install`, `npm install`, etc.), or other necessary commands for a particular server type.
+
+**Procedure for KB Lookup:**
+
+1.  **Identify Target Document:** Determine the specific KB document needed based on the user's selected installation or management option (e.g., `install-vertex-ai.md`). Use the KB README (`.ruru/modes/agent-mcp-manager/kb/README.md`) for an overview if needed.
+2.  **Use `read_file`:** Access the content of the target KB document.
+3.  **Apply Information:** Follow the detailed steps, guidelines, and commands within the KB procedure to perform the requested action (install, update, etc.). Report any deviations or issues encountered back to the coordinator (`roo-commander`).
+
+**Key Objective:** To ensure that specific, potentially complex installation and management procedures for different MCP servers are reliably executed by following the detailed instructions stored in the mode's Knowledge Base.

.roo/rules-prime-coordinator/03-meta-dev-workflow-simplified.md

@@ -1,36 +1,44 @@
 +++
-id = "PRIME-RULE-METADEV-SIMPLE-V1"
-title = "Prime Coordinator: Rule - Meta-Development Workflow Trigger"
+id = "PRIME-RULE-METADEV-SIMPLE-V3" # Incremented version
+title = "Prime Coordinator: Rule - Meta-Development Workflow Trigger (Simplified)"
 context_type = "rules"
 scope = "Routing requests to modify Roo Commander configuration files"
 target_audience = ["prime"]
 granularity = "procedure"
 status = "active"
-last_updated = "2025-04-22"
-tags = ["rules", "workflow", "meta-development", "configuration", "staging", "safety", "prime"]
+last_updated = "2025-04-24" # Updated date
+tags = ["rules", "workflow", "meta-development", "configuration", "staging", "safety", "prime", "confirmation", "auto-apply", "generated-files"] # Added tags
 related_context = [
     "01-operational-principles.md",
     "02-request-analysis-dispatch.md",
     "07-logging-confirmation-simplified.md",
-    ".ruru/modes/prime-coordinator/kb/03-meta-dev-staging-workflow.md", # Points to KB
-    ".ruru/modes/prime-coordinator/kb/04-meta-dev-direct-workflow.md", # Points to KB
-    "prime-txt", "prime-dev"
+    ".ruru/modes/prime-coordinator/kb/05-meta-dev-staging-confirm-auto-apply.md", # Staging KB ref
+    ".ruru/modes/prime-coordinator/kb/07-meta-dev-direct-auto-apply-operational.md", # Operational KB ref
+    "prime-txt", "prime-dev",
+    "build_roomodes.js" # Related build script
     ]
 template_schema_doc = ".ruru/templates/toml-md/16_ai_rule.README.md"
 relevance = "High: Core workflow for configuration changes"
 +++
 
-# Rule: Meta-Development Workflow Trigger
+# Rule: Meta-Development Workflow Trigger (Simplified)
 
-This rule defines how to handle requests (Type A from Rule `02`) to modify Roo Commander configuration files.
+This rule defines how to handle requests (Type A from Rule `02`) to modify Roo Commander configuration files, implementing a simplified workflow based on path sensitivity.
 
 **Procedure:**
 
 1.  **Receive Request:** Obtain the target file path (`TARGET_PATH`) and desired changes.
-2.  **Define Protected Paths:** `PROTECTED_PATHS` = patterns matching: `.roo/rules/**`, `.ruru/modes/roo-commander/**`, `.roo/rules-roo-commander/**`, `.ruru/modes/prime*/**`, `.roo/rules-prime*/**`, `.roomodes*`, `build_*.js`, `create_build.js`.
-3.  **Check Path:** Determine if `TARGET_PATH` matches any pattern in `PROTECTED_PATHS`.
-4.  **Execute Appropriate Workflow:**
-    *   **IF Protected:** Initiate the **Staging Workflow**. Consult **KB `.ruru/modes/prime-coordinator/kb/03-meta-dev-staging-workflow.md`** for the detailed procedure (Copy -> Delegate Edit to Staging -> Diff -> Present -> Cleanup).
-    *   **ELSE (Operational Config):** Initiate the **Direct Edit Workflow**. Consult **KB `.ruru/modes/prime-coordinator/kb/04-meta-dev-direct-workflow.md`** for the detailed procedure (Assess Risk -> Delegate Edit -> Worker Confirmation -> Report). Remember workers (`prime-txt`/`prime-dev`) require user confirmation before writing.
+2.  **Define Path Patterns:**
+    *   `PROTECTED_CORE_PATHS` = patterns matching: `.roo/rules/**`, `.ruru/modes/roo-commander/**`, `.roo/rules-roo-commander/**`, `.ruru/modes/prime*/**`, `.roo/rules-prime*/**`, `build_*.js`, `create_build.js`. (These require staging and confirmation).
+    *   `GENERATED_CONFIG_PATHS` = patterns matching: `.roomodes*`. (These are generated files, editing directly is discouraged).
+3.  **Check Path & Execute Appropriate Workflow:**
+    *   **IF `TARGET_PATH` matches `GENERATED_CONFIG_PATHS`:** Initiate **Generated File Handling**.
+        *   *Brief:* **Do not proceed with direct edit.** Ask the user for confirmation, explaining that this file is auto-generated. Strongly suggest running the appropriate build script (e.g., `node build_roomodes.js`) instead of manual editing. If the user insists on manual editing *after* the warning, proceed with the "Staging + Confirmation + Auto-Apply Workflow" below as if it were a `PROTECTED_CORE_PATHS` file.
+    *   **ELSE IF `TARGET_PATH` matches `PROTECTED_CORE_PATHS`:** Initiate the **Staging + Confirmation + Auto-Apply Workflow**.
+        *   *Brief:* Copy to staging -> Delegate edit to worker -> Generate diff -> Present diff to user & ask for confirmation -> If confirmed, Coordinator applies change to original -> Cleanup staging.
+        *   Consult **KB `.ruru/modes/prime-coordinator/kb/05-meta-dev-staging-confirm-auto-apply.md`** for the detailed procedure.
+    *   **ELSE (Operational Config - not protected):** Initiate the **Direct Auto-Apply Workflow (Operational)**.
+        *   *Brief:* Delegate edit directly to the appropriate worker (`prime-txt`/`prime-dev`) -> Worker applies change directly (worker's internal confirmation rule still applies) -> Worker reports completion/failure.
+        *   Consult **KB `.ruru/modes/prime-coordinator/kb/07-meta-dev-direct-auto-apply-operational.md`** for the detailed procedure.
 
-**Key Objective:** Ensure protected core files are modified via the safer Staging Workflow, while allowing direct (but confirmed) edits for operational configuration files via Prime workers.
+**Key Objective:** Ensure maximum safety (staging + user confirmation) for all core configuration, rules, modes, and build scripts (`PROTECTED_CORE_PATHS`). Discourage direct editing of generated files (`GENERATED_CONFIG_PATHS`) by suggesting build scripts first. Allow direct application by workers for general operational configuration, while consistently respecting the worker's own confirmation rules before any write action.

.roo/rules-prime-dev/02-format-adherence-rule.md

@@ -23,6 +23,4 @@ related_context = [".roo/rules/01-standard-toml-md-format.md"]
     *   Consult the workspace standard `.roo/rules/01-standard-toml-md-format.md` for detailed TOML+MD specifications if necessary.
 *   **`.js` / `.ts` Files:** Maintain valid JavaScript/TypeScript syntax.
 *   **`.json` Files:** Maintain valid JSON syntax.
-*   **`.toml` Files:** Maintain valid TOML syntax.
-
-**Action:** Before generating the confirmation prompt (Rule `01`), perform a mental check or use internal validation logic to confirm the syntax correctness of the proposed change relative to the file type. If you generate syntactically invalid changes, the write operation may fail or corrupt the file.
+*   **`.toml` Files:** Maintain valid TOML syntax.

.roo/rules-roo-commander/02-initialization-workflow-rule.md

@@ -1,16 +1,17 @@
 +++
-id = "ROO-CMD-RULE-INIT-V3" # Incremented version
+id = "ROO-CMD-RULE-INIT-V4" # Incremented version
 title = "Roo Commander: Rule - Initial Request Processing (Explicit KB Routing)"
 context_type = "rules"
 scope = "Initial user interaction handling, presenting comprehensive starting options and routing to specific KB procedures"
 target_audience = ["roo-commander"]
 granularity = "procedure"
 status = "active"
-last_updated = "2025-04-22" # Use current date
+last_updated = "2025-04-24" # Use current date
 tags = ["rules", "workflow", "initialization", "onboarding", "intent", "options", "kb-routing", "roo-commander"]
 related_context = [
     "01-operational-principles.md",
     # Specific KB Action files
+    ".ruru/modes/roo-commander/kb/initial-actions/00-install-mcp.md", # Added MCP Install option
     ".ruru/modes/roo-commander/kb/initial-actions/01-start-new-project.md",
     ".ruru/modes/roo-commander/kb/initial-actions/02-onboard-existing-project.md",
     ".ruru/modes/roo-commander/kb/initial-actions/03-clone-onboard.md",
@@ -52,20 +53,21 @@ This rule governs how you handle the **first user message** in a session, presen
  <ask_followup_question>
   <question>Welcome to Roo Commander v7 (Wallaby)! How can I assist you today?</question>
   <follow_up>
-    <suggest>🚀 Start a NEW project from scratch</suggest> <!-- Option 1 -->
+    <suggest>🔌 Install/Manage MCP Servers</suggest> <!-- Option 0 -->
+    <suggest>🎩 Start a NEW project from scratch</suggest> <!-- Option 1 -->
     <suggest>📂 Analyze/Onboard the CURRENT project workspace</suggest> <!-- Option 2 -->
     <suggest>🌐 Clone a Git repository & onboard</suggest> <!-- Option 3 -->
-    <suggest>📄 Use existing project files/plans to define the work</suggest> <!-- Option 4 -->
-    <suggest>💡 Plan/Design a new feature or project</suggest> <!-- Option 5 -->
+    <suggest>🗃️ Use existing project files/plans to define the work</suggest> <!-- Option 4 -->
+    <suggest>📑 Plan/Design a new feature or project</suggest> <!-- Option 5 -->
     <suggest>🐞 Fix a specific bug</suggest> <!-- Option 6 -->
     <suggest>♻️ Refactor or improve existing code</suggest> <!-- Option 7 -->
     <suggest>✍️ Write or update documentation</suggest> <!-- Option 8 -->
-    <suggest>📊 Review project status / Manage tasks (MDTM)</suggest> <!-- Option 9 -->
+    <suggest>📟 Review project status / Manage tasks (MDTM)</suggest> <!-- Option 9 -->
     <suggest>❓ Research a topic / Ask a technical question</suggest> <!-- Option 10 -->
-    <suggest>🛠️ Execute a command / Delegate a specific known task</suggest> <!-- Option 11 -->
-    <suggest>⚙️ Manage Roo Configuration (Advanced)</suggest> <!-- Option 12 -->
-    <suggest>⚙️ Update my preferences / profile</suggest> <!-- Option 13 -->
-    <suggest>📖 Learn about Roo Commander capabilities</suggest> <!-- Option 14 -->
+    <suggest>🎺 Execute a command / Delegate a specific known task</suggest> <!-- Option 11 -->
+    <suggest>🪃 Manage Roo Configuration (Advanced)</suggest> <!-- Option 12 -->
+    <suggest>🖲️ Update my preferences / profile</suggest> <!-- Option 13 -->
+    <suggest>🦘 Learn about Roo Commander capabilities</suggest> <!-- Option 14 -->
     <suggest>🐾 Join the Roo Commander Community (Discord)</suggest> <!-- Option 15 -->
     <suggest>🤔 Something else... (Describe your goal)</suggest> <!-- Option 16 -->
   </follow_up>
@@ -96,10 +98,11 @@ This rule governs how you handle the **first user message** in a session, presen
         *   Await user's selection. Proceed to Step 3.
 
 3.  **Handle User Selection (from Standard Initial Prompt):**
-    *   Once the user selects an option (identified 1-16) from the standard prompt:
+    *   Once the user selects an option (identified 0-16) from the standard prompt:
         1.  Identify the selected option number.
         2.  Log the chosen starting path (Rule `08`).
         3.  **Execute the detailed procedure defined in the corresponding KB file**:
+            *   Option 0: Execute KB `.ruru/modes/roo-commander/kb/initial-actions/00-install-mcp.md`.
             *   Option 1: Execute KB `.ruru/modes/roo-commander/kb/initial-actions/01-start-new-project.md`.
             *   Option 2: Execute KB `.ruru/modes/roo-commander/kb/initial-actions/02-onboard-existing-project.md`.
             *   Option 3: Execute KB `.ruru/modes/roo-commander/kb/initial-actions/03-clone-onboard.md`.

.roo/rules/00-user-preferences.md

@@ -26,7 +26,9 @@ preferred_modes = [
 ]
 verbosity_level = "normal" # << OPTIONAL. Options: "concise", "normal", "verbose" >>
 auto_execute_commands = false # << OPTIONAL >>
-preferred_language = "en" # << OPTIONAL >>
++preferred_language = "en" # << OPTIONAL. Fallback if specific input/output prefs not set. Default 'en' >>
++preferred_input_language = "en" # << OPTIONAL. Language user primarily uses for prompts >>
++preferred_output_language = "en" # << OPTIONAL. Preferred language for conversational output, comments, etc. >>
 +++
 
 # User Preferences Data (Defined in TOML)