Feat roo import

.github/ISSUE_TEMPLATE/add-provider-model.md

@@ -0,0 +1,13 @@
+---
+name: Add provider model
+about: Add a provider model that isn't htere
+title: ''
+labels: model
+assignees: ''
+type: Task
+
+---
+
+Name of model: (GPT 5.4)
+Model creator: (i.e. Open AI)
+Link to model:

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[BUG] "
+labels: bug
+assignees: ''
+type: Bug
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Video**
+Add a video of the incident happening, it will help us debug
+
+**What version of zoo are you running**
+i.e. 3.55
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,21 @@
+---
+name: Feature request
+about: What do you want to add to zoo?
+title: ''
+labels: enhancement
+assignees: ''
+type: Feature
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/workflows/code-qa.yml

@@ -49,12 +49,34 @@ jobs:
                 include:
                     - os: ubuntu-latest
                       name: ubuntu-latest
+                      codecov-flag: ubuntu
                     - os: windows-latest
                       name: windows-latest
+                      codecov-flag: windows
         steps:
             - name: Checkout code
               uses: actions/checkout@v4
             - name: Setup Node.js and pnpm
               uses: ./.github/actions/setup-node-pnpm
-            - name: Run unit tests
-              run: pnpm test
+            - name: Cache Turbo
+              uses: actions/cache@v4
+              with:
+                  path: .turbo/cache
+                  key: ${{ runner.os }}-turbo-${{ hashFiles('**/pnpm-lock.yaml') }}
+                  restore-keys: |
+                      ${{ runner.os }}-turbo-${{ hashFiles('**/pnpm-lock.yaml') }}-
+                      ${{ runner.os }}-turbo-
+            - name: Run unit tests with coverage
+              run: pnpm test:coverage
+            - name: Upload coverage to Codecov
+              uses: codecov/codecov-action@v4
+              with:
+                  files: >-
+                      src/coverage/lcov.info,
+                      webview-ui/coverage/lcov.info,
+                      packages/core/coverage/lcov.info,
+                      packages/cloud/coverage/lcov.info,
+                      packages/telemetry/coverage/lcov.info,
+                      apps/cli/coverage/lcov.info
+                  flags: ${{ matrix.codecov-flag }}
+                  token: ${{ secrets.CODECOV_TOKEN }}

.github/workflows/e2e.yml

@@ -0,0 +1,30 @@
+name: E2E Tests (Mocked)
+
+on:
+    workflow_dispatch:
+    pull_request:
+        types: [opened, reopened, ready_for_review, synchronize]
+        branches: [main]
+        paths:
+            - "src/**"
+            - "webview-ui/**"
+            - "apps/vscode-e2e/**"
+            - "packages/core/**"
+            - "package.json"
+            - "pnpm-lock.yaml"
+            - "turbo.json"
+            - ".github/actions/setup-node-pnpm/**"
+
+jobs:
+    e2e-mock:
+        runs-on: ubuntu-latest
+        timeout-minutes: 30
+        steps:
+            - name: Checkout code
+              uses: actions/checkout@v4
+            - name: Setup Node.js and pnpm
+              uses: ./.github/actions/setup-node-pnpm
+            - name: Install xvfb
+              run: sudo apt-get install -y xvfb
+            - name: Run mocked E2E tests
+              run: xvfb-run -a pnpm --filter @roo-code/vscode-e2e test:ci:mock

.roomodes

@@ -1,7 +1,7 @@
 customModes:
   - slug: 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.
+    roleDefinition: You are Zoo, 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.
     whenToUse: Translate and manage localization files.
     description: Translate and manage localization files.
     groups:
@@ -33,7 +33,7 @@ customModes:
     source: project
   - slug: pr-fixer
     name: 🛠️ PR Fixer
-    roleDefinition: "You are Roo, a pull request resolution specialist. Your focus is on addressing feedback and resolving issues within existing pull requests. Your expertise includes: - Analyzing PR review comments to understand required changes. - Checking CI/CD workflow statuses to identify failing tests. - Fetching and analyzing test logs to diagnose failures. - Identifying and resolving merge conflicts. - Guiding the user through the resolution process."
+    roleDefinition: "You are Zoo, a pull request resolution specialist. Your focus is on addressing feedback and resolving issues within existing pull requests. Your expertise includes: - Analyzing PR review comments to understand required changes. - Checking CI/CD workflow statuses to identify failing tests. - Fetching and analyzing test logs to diagnose failures. - Identifying and resolving merge conflicts. - Guiding the user through the resolution process."
     whenToUse: Use this mode to fix pull requests. It can analyze PR feedback from GitHub, check for failing tests, and help resolve merge conflicts before applying the necessary code changes.
     description: Fix pull requests.
     groups:
@@ -44,7 +44,7 @@ customModes:
   - slug: merge-resolver
     name: 🔀 Merge Resolver
     roleDefinition: |-
-      You are Roo, a merge conflict resolution specialist with expertise in:
+      You are Zoo, a merge conflict resolution specialist with expertise in:
       - Analyzing pull request merge conflicts using git blame and commit history
       - Understanding code intent through commit messages and diffs
       - Making intelligent decisions about which changes to keep, merge, or discard
@@ -76,7 +76,7 @@ customModes:
   - slug: docs-extractor
     name: 📚 Docs Extractor
     roleDefinition: |-
-      You are Roo Code, a codebase analyst who extracts raw facts for documentation teams.
+      You are Zoo Code, a codebase analyst who extracts raw facts for documentation teams.
       You do NOT write documentation. You extract and organize information.
 
       Two functions:
@@ -98,7 +98,7 @@ customModes:
     source: project
   - slug: issue-investigator
     name: 🕵️ Issue Investigator
-    roleDefinition: You are Roo, a GitHub issue investigator. Your purpose is to analyze GitHub issues, investigate the probable causes using extensive codebase searches, and propose well-reasoned, theoretical solutions. You methodically track your investigation using a todo list, attempting to disprove initial theories to ensure a thorough analysis. Your final output is a human-like, conversational comment for the GitHub issue.
+    roleDefinition: You are Zoo, a GitHub issue investigator. Your purpose is to analyze GitHub issues, investigate the probable causes using extensive codebase searches, and propose well-reasoned, theoretical solutions. You methodically track your investigation using a todo list, attempting to disprove initial theories to ensure a thorough analysis. Your final output is a human-like, conversational comment for the GitHub issue.
     whenToUse: Use this mode when you need to investigate a GitHub issue to understand its root cause and propose a solution. This mode is ideal for triaging issues, providing initial analysis, and suggesting fixes before implementation begins. It uses the `gh` CLI for issue interaction.
     description: Investigates GitHub issues
     groups:

.vscode/settings.json

@@ -10,5 +10,7 @@
 	},
 	// Turn off tsc task auto detection since we have the necessary tasks as npm scripts
 	"typescript.tsc.autoDetect": "off",
+	// Use the workspace TypeScript version so editor diagnostics match `pnpm check-types`
+	"typescript.tsdk": "node_modules/typescript/lib",
 	"vitest.disableWorkspaceWarning": true
 }