Merge branch 'main' into refactor-mcp

# Conflicts:
#	src/core/webview/webviewMessageHandler.ts
#	src/services/mcp/McpHub.ts

Author: aheizi

.changeset/brave-pigs-judge.md

@@ -0,0 +1,5 @@
+---
+"roo-cline": patch
+---
+
+Add editor name to telemetry

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -2,6 +2,12 @@ name: Bug Report
 description: Clearly report a bug with detailed repro steps
 labels: ["bug"]
 body:
+  - type: markdown
+    attributes:
+      value: |
+        **Thank you for taking the time to fill out this bug report!**
+
+        Please ensure this bug hasn't been reported already by searching existing [GitHub Issues](https://github.com/RooVetGit/Roo-Code/issues).
   - type: input
     id: version
     attributes:
@@ -17,27 +23,33 @@ body:
       description: Choose the API provider involved
       multiple: false
       options:
-        - OpenRouter
         - Anthropic
-        - Google Gemini
+        - AWS Bedrock
+        - Chutes AI
         - DeepSeek
-        - OpenAI
-        - OpenAI Compatible
-        - GCP Vertex AI
-        - Amazon Bedrock
-        - Requesty
         - Glama
-        - VS Code LM API
+        - Google Gemini
+        - Groq
+        - Human Relay Provider
         - LM Studio
+        - Mistral AI
         - Ollama
+        - OpenAI
+        - OpenAI Compatible
+        - OpenRouter
+        - Requesty
+        - Unbound
+        - VS Code Language Model API
+        - xAI (Grok)
+        - Not Applicable / Other
     validations:
       required: true
 
   - type: input
     id: model
     attributes:
       label: Model Used
-      description: Clearly specify the exact model (e.g., Claude 3.7 Sonnet)
+      description: Clearly specify the exact model (e.g., Claude 3.7 Sonnet). If not applicable, enter N/A.
     validations:
       required: true
 
@@ -69,8 +81,8 @@ body:
   - type: textarea
     id: logs
     attributes:
-      label: Relevant API Request Output
-      description: Paste relevant API logs or outputs here (formatted automatically as code)
+      label: Relevant API Request Output or Error Logs
+      description: Paste relevant API logs, console outputs, or error messages here (formatted automatically as code).
       render: shell
 
   - type: textarea

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,76 @@
+name: Detailed Feature Proposal
+description: Propose a specific, actionable feature or enhancement for implementation
+labels: ["proposal", "enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **Thank you for proposing a detailed feature for Roo Code!**
+
+        This template is for submitting specific, actionable proposals that you or others intend to implement after discussion and approval. It's a key part of our [Issue-First Approach](../../CONTRIBUTING.md).
+
+        - **For general ideas or less defined suggestions**, please use [GitHub Discussions](https://github.com/RooVetGit/Roo-Code/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop) first.
+        - **Before submitting**, please search existing [GitHub Issues](https://github.com/RooVetGit/Roo-Code/issues) and [Discussions](https://github.com/RooVetGit/Roo-Code/discussions) to avoid duplicates.
+
+        For guidance or to discuss your idea, join the [Roo Code Discord](https://discord.gg/roocode) and DM **Hannes Rudolph** (`hrudolph`).
+
+        A maintainer (especially @hannesrudolph) will review this proposal. **Do not start implementation until this proposal is approved and assigned.**
+  - type: textarea
+    id: problem-description
+    attributes:
+      label: What problem does this proposed feature solve?
+      description: Clearly describe the problem, use case, or opportunity this feature addresses. Why is this change needed?
+      placeholder: e.g., "Users currently cannot..." or "It would be beneficial if..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposed-solution
+    attributes:
+      label: Describe the proposed solution in detail
+      description: Provide a clear and comprehensive description of the feature or enhancement. How should it work? What are the key functionalities?
+      placeholder: Include details on user interaction, expected behavior, and potential impact.
+    validations:
+      required: true
+
+  - type: textarea
+    id: technical-details
+    attributes:
+      label: Technical considerations or implementation details (optional)
+      description: If you have thoughts on how this could be implemented, or specific technical aspects to consider, please share them.
+      placeholder: e.g., "This might involve changes to X component..." or "We should consider Y library..."
+
+  - type: textarea
+    id: alternatives-considered
+    attributes:
+      label: Describe alternatives considered (if any)
+      description: What other ways could this problem be solved or this functionality be achieved? Why is your proposed solution preferred?
+      placeholder: Briefly outline any alternative approaches and why they were not chosen.
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context & Mockups
+      description: Add any other context, mockups, screenshots, or links that help illustrate the proposal.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Proposal Checklist
+      description: Please confirm the following before submitting.
+      options:
+        - label: I have searched existing Issues and Discussions to ensure this proposal is not a duplicate.
+          required: true
+        - label: This proposal is for a specific, actionable change intended for implementation (not a general idea).
+          required: true
+        - label: I understand that this proposal requires review and approval before any development work begins.
+          required: true
+
+  - type: checkboxes
+    id: willingness-to-contribute
+    attributes:
+      label: Are you interested in implementing this feature if approved?
+      description: (This is optional and does not affect the proposal's consideration)
+      options:
+        - label: Yes, I would like to contribute to implementing this feature.
+          required: false

.github/pull_request_template.md

@@ -1,35 +1,83 @@
-## Context
+<!--
+Thank you for contributing to Roo Code!
+
+Before submitting your PR, please ensure:
+- It's linked to an approved GitHub Issue.
+- You've reviewed our [Contributing Guidelines](../../CONTRIBUTING.md).
+-->
+
+### Related GitHub Issue
 
-<!-- Brief description of WHAT you’re doing and WHY. -->
+<!-- Every PR MUST be linked to an approved issue. -->
 
-## Implementation
+Closes: # <!-- Replace with the issue number, e.g., Closes: #123 -->
+
+### Description
 
 <!--
+Briefly summarize the changes in this PR and how they address the linked issue.
+The issue should cover the "what" and "why"; this section should focus on:
+- The "how": key implementation details, design choices, or trade-offs made.
+- Anything specific reviewers should pay attention to in this PR.
+-->
 
-Some description of HOW you achieved it. Perhaps give a high level description of the program flow. Did you need to refactor something? What tradeoffs did you take? Are there things in here which you’d particularly like people to pay close attention to?
+### Test Procedure
 
+<!--
+Detail the steps to test your changes. This helps reviewers verify your work.
+- How did you test this specific implementation? (e.g., unit tests, manual testing steps)
+- How can reviewers reproduce your tests or verify the fix/feature?
+- Include relevant testing environment details if applicable.
 -->
 
-## Screenshots
+### Type of Change
 
-| before | after |
-| ------ | ----- |
-|        |       |
+<!-- Mark all applicable boxes with an 'x'. -->
 
-## How to Test
+- [ ] 🐛 **Bug Fix**: Non-breaking change that fixes an issue.
+- [ ] ✨ **New Feature**: Non-breaking change that adds functionality.
+- [ ] 💥 **Breaking Change**: Fix or feature that would cause existing functionality to not work as expected.
+- [ ] ♻️ **Refactor**: Code change that neither fixes a bug nor adds a feature.
+- [ ] 💅 **Style**: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
+- [ ] 📚 **Documentation**: Updates to documentation files.
+- [ ] ⚙️ **Build/CI**: Changes to the build process or CI configuration.
+- [ ] 🧹 **Chore**: Other changes that don't modify `src` or test files.
 
-<!--
+### Pre-Submission Checklist
+
+<!-- Go through this checklist before marking your PR as ready for review. -->
+
+- [ ] **Issue Linked**: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
+- [ ] **Scope**: My changes are focused on the linked issue (one major feature/fix per PR).
+- [ ] **Self-Review**: I have performed a thorough self-review of my code.
+- [ ] **Code Quality**:
+    - [ ] My code adheres to the project's style guidelines.
+    - [ ] There are no new linting errors or warnings (`npm run lint`).
+    - [ ] All debug code (e.g., `console.log`) has been removed.
+- [ ] **Testing**:
+    - [ ] New and/or updated tests have been added to cover my changes.
+    - [ ] All tests pass locally (`npm test`).
+    - [ ] The application builds successfully with my changes.
+- [ ] **Branch Hygiene**: My branch is up-to-date (rebased) with the `main` branch.
+- [ ] **Documentation Impact**: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
+- [ ] **Changeset**: A changeset has been created using `npm run changeset` if this PR includes user-facing changes or dependency updates.
+- [ ] **Contribution Guidelines**: I have read and agree to the [Contributor Guidelines](../../CONTRIBUTING.md).
 
-A straightforward scenario of how to test your changes will help reviewers that are not familiar with the part of the code that you are changing but want to see it in action. This section can include a description or step-by-step instructions of how to get to the state of v2 that your change affects.
+### Screenshots / Videos
 
-A "How To Test" section can look something like this:
+<!--
+For UI changes, please provide before-and-after screenshots or a short video of the *actual results*.
+This greatly helps in understanding the visual impact of your changes.
+-->
 
-- Sign in with a user with tracks
-- Activate `show_awesome_cat_gifs` feature (add `?feature.show_awesome_cat_gifs=1` to your URL)
-- You should see a GIF with cats dancing
+### Documentation Updates
 
+<!--
+Does this PR necessitate updates to user-facing documentation?
+- [ ] No documentation updates are required.
+- [ ] Yes, documentation updates are required. (Please describe what needs to be updated or link to a PR in the docs repository).
 -->
 
-## Get in Touch
+### Additional Notes
 
-<!-- We'd love to have a way to chat with you about your changes if necessary. If you're in the [Roo Code Discord](https://discord.gg/roocode), please share your handle here. -->
+<!-- Add any other context, questions, or information for reviewers here. -->

.github/workflows/code-qa.yml

@@ -78,8 +78,10 @@ jobs:
         run: npm run install:all
       - name: Compile (to build and copy WASM files)
         run: npm run compile
-      - name: Run unit tests
+      - name: Run jest unit tests
         run: npx jest --silent
+      - name: Run vitest unit tests
+        run: npx vitest run --silent
 
   test-webview:
     runs-on: ${{ matrix.os }}

.roo/rules-translate/001-general-rules.md

@@ -1,6 +1,6 @@
 # 1. SUPPORTED LANGUAGES AND LOCATION
 
-- Localize all strings into the following locale files: ca, de, en, es, fr, hi, it, ja, ko, pl, pt-BR, ru, tr, vi, zh-CN, zh-TW
+- Localize all strings into the following locale files: ca, de, en, es, fr, hi, it, ja, ko, nl, pl, pt-BR, ru, tr, vi, zh-CN, zh-TW
 - The VSCode extension has two main areas that require localization:
     - Core Extension: src/i18n/locales/ (extension backend)
     - WebView UI: webview-ui/src/i18n/locales/ (user interface)

.roomodes

@@ -2,7 +2,7 @@
   "customModes": [
     {
       "slug": "test",
-      "name": "Test",
+      "name": "🧪 Test",
       "roleDefinition": "You are Roo, a Jest testing specialist with deep expertise in:\n- Writing and maintaining Jest test suites\n- Test-driven development (TDD) practices\n- Mocking and stubbing with Jest\n- Integration testing strategies\n- TypeScript testing patterns\n- Code coverage analysis\n- Test performance optimization\n\nYour focus is on maintaining high test quality and coverage across the codebase, working primarily with:\n- Test files in __tests__ directories\n- Mock implementations in __mocks__\n- Test utilities and helpers\n- Jest configuration and setup\n\nYou ensure tests are:\n- Well-structured and maintainable\n- Following Jest best practices\n- Properly typed with TypeScript\n- Providing meaningful coverage\n- Using appropriate mocking strategies",
       "groups": [
         "read",
@@ -20,7 +20,7 @@
     },
     {
       "slug": "translate",
-      "name": "Translate",
+      "name": "🌐 Translate",
       "roleDefinition": "You are Roo, a linguistic specialist focused on translating and managing localization files. Your responsibility is to help maintain and update translation files for the application, ensuring consistency and accuracy across all language resources.",
       "groups": [
         "read",
@@ -34,6 +34,39 @@
         ]
       ],
       "source": "project"
+    },
+    {
+      "slug": "design-engineer",
+      "name": "🎨 Design Engineer",
+      "roleDefinition": "You are Roo, an expert Design Engineer focused on VSCode Extension development. Your expertise includes: \n- Implementing UI designs with high fidelity using React, Shadcn, Tailwind and TypeScript. \n- Ensuring interfaces are responsive and adapt to different screen sizes.  \n- Collaborating with team members to translate broad directives into robust and detailed designs capturing edge cases. \n- Maintaining uniformity and consistency across the user interface.",
+      "groups": [
+        "read",
+        [
+          "edit",
+          {
+            "fileRegex": "\\.(css|html|json|mdx?|jsx?|tsx?|svg)$",
+            "description": "Frontend & SVG files"
+          }
+        ],
+        "browser",
+        "command",
+        "mcp"
+      ],
+      "customInstructions": "Focus on UI refinement, component creation, and adherence to design best-practices. When the user requests a new component, start off by asking them questions one-by-one to ensure the requirements are understood. Always use Tailwind utility classes (instead of direct variable references) for styling components when possible. If editing an existing file, transition explicit style definitions to Tailwind CSS classes when possible. Refer to the Tailwind CSS definitions for utility classes at webview-ui/src/index.css. Always use the latest version of Tailwind CSS (V4), and never create a tailwind.config.js file. Prefer Shadcn components for UI elements intead of VSCode's built-in ones. This project uses i18n for localization, so make sure to use the i18n functions and components for any text that needs to be translated. Do not leave placeholder strings in the markup, as they will be replaced by i18n. Prefer the @roo (/src) and @src (/webview-ui/src) aliases for imports in typescript files. Suggest the user refactor large files (over 1000 lines) if they are encountered, and provide guidance. Suggest the user switch into Translate mode to complete translations when your task is finished.",
+      "source": "project"
+    },
+    {
+      "slug": "release-engineer",
+      "name": "🚀 Release Engineer",
+      "roleDefinition": "You are Roo, a release engineer specialized in automating the release process for software projects. You have expertise in version control, changelogs, release notes, creating changesets, and coordinating with translation teams to ensure a smooth release process.",
+      "customInstructions": "When preparing a release:\n1. Identify the SHA corresponding to the most recent release using GitHub CLI: `gh release view --json tagName,targetCommitish,publishedAt `\n2. Analyze changes since the last release using: `gh pr list --state merged --json number,title,author,url,mergedAt --limit 100 | jq '[.[] | select(.mergedAt > \"TIMESTAMP\") | {number, title, author: .author.login, url, mergedAt}]'`\n3. Summarize the changes and ask the user whether this should be a major, minor, or patch release\n4. Create a changeset in .changeset/v[version].md instead of directly modifying package.json. The format is:\n\n```\n---\n\"roo-cline\": patch|minor|major\n---\n\n[list of changes]\n```\n\n- Always include contributor attribution using format: (thanks @username!)\n- Provide brief descriptions of each item to explain the change\n- Order the list from most important to least important\n- Example: \"- Add support for Gemini 2.5 Pro caching (thanks @contributor!)\"\n\n5. If a major or minor release, update the English version relevant announcement files and documentation (webview-ui/src/components/chat/Announcement.tsx, README.md, and the `latestAnnouncementId` in src/core/webview/ClineProvider.ts)\n6. Ask the user to confirm the English version\n7. Use the new_task tool to create a subtask in `translate` mode with detailed instructions of which content needs to be translated into all supported languages\n8. Commit and push the changeset file to the repository\n9. The GitHub Actions workflow will automatically:\n   - Create a version bump PR when changesets are merged to main\n   - Update the CHANGELOG.md with proper formatting\n   - Publish the release when the version bump PR is merged",
+      "groups": [
+        "read",
+        "edit",
+        "command",
+        "browser"
+      ],
+      "source": "project"
     }
   ]
 }