merge: main

Author: RomneyDa

.claude/lint-check.sh

@@ -0,0 +1,3 @@
+{
+  "install": "npm i"
+}

.claude/settings.json

@@ -0,0 +1,100 @@
+# Mintlify Documentation Formatting Rules
+
+## Component Formatting
+
+When working with Mintlify documentation components (Card, Info, Tip, Note, Warning, etc.), follow these formatting guidelines:
+
+### Bullet Points and Lists
+
+1. **Always add a blank line** after the opening component tag and before the closing tag
+2. **Indent content** by 2 spaces within components
+3. **Use proper list formatting** with each item on its own line:
+   - Start lists on a new line after introductory text
+   - Use `-` for unordered lists
+   - Maintain consistent indentation
+
+### Examples
+
+#### ✅ Correct Formatting:
+
+```mdx
+<Card title="Example" icon="icon-name">
+
+  This is the content with proper formatting:
+  - First bullet point
+  - Second bullet point
+  - Third bullet point
+
+</Card>
+```
+
+```mdx
+<Info>
+
+  Important information here:
+  - Point one
+  - Point two
+  - Point three
+
+</Info>
+```
+
+#### ❌ Incorrect Formatting:
+
+```mdx
+<Card title="Example" icon="icon-name">
+  This is wrong: - All bullets - On one line - Bad formatting
+</Card>
+```
+
+### Component-Specific Rules
+
+1. **Card Components**: Always include blank lines and proper indentation
+2. **Info/Tip/Note/Warning**: Format lists as bullet points, not inline
+3. **CardGroup**: Each Card within should follow the same formatting rules
+4. **Code Blocks**: Within components, maintain proper indentation
+
+### Links in Lists
+
+When including links in bullet points:
+```mdx
+- [Link Text](url): Description of the link
+```
+
+### Nested Components
+
+For nested components, maintain proper indentation levels:
+```mdx
+<CardGroup>
+  <Card title="First Card">
+
+    Content here:
+    - Bullet one
+    - Bullet two
+
+  </Card>
+
+  <Card title="Second Card">
+
+    More content:
+    - Another bullet
+    - Final bullet
+
+  </Card>
+</CardGroup>
+```
+
+## Application
+
+These rules apply to all `.mdx` files in the `docs/` directory, particularly:
+- Guide documents
+- Cookbook documents
+- Reference documentation
+- Any Mintlify-powered documentation
+
+## Automation Note
+
+When using Continue or other AI assistants to generate or modify documentation:
+- Always format Mintlify components according to these rules
+- Review generated content for proper formatting
+- Apply these rules consistently across all documentation

.continue/environment.json

@@ -0,0 +1,5 @@
+---
+globs: "**/*.{ts,tsx}"
+---
+
+Avoid using the `any` type wherever possible. Use unknown or find the correct type. The only acceptable place to use any is when typecasting for test mocks, and even then it's better to avoid and provide a proper mock.

.continue/rules/mintlify-formatting.md

@@ -0,0 +1,6 @@
+---
+name: Personality Rules
+description: Conversational and personality guidelines
+---
+
+When the user challenges your output or asks a question, don't be overly-amiable (e.g. responding "You're right" all the time). Focus on correctness and be willing to tell the user they are wrong.

.continue/rules/no-any-types.md

@@ -107,29 +107,15 @@ runs:
         cd binary
         npm run build
 
-    - name: Start test IDE
+    - name: Run tests
       shell: bash
       run: |
         cd extensions/intellij
         export DISPLAY=:99.0
         Xvfb -ac :99 -screen 0 1920x1080x24 &
         sleep 10
         mkdir -p build/reports
-        ./gradlew runIdeForUiTests &
-
-    - name: Wait for JB connection
-      uses: jtalk/url-health-check-action@v3
-      with:
-        url: http://127.0.0.1:8082
-        max-attempts: 15
-        retry-delay: 30s
-
-    - name: Run tests
-      shell: bash
-      run: |
-        cd extensions/intellij
-        export DISPLAY=:99.0
-        ./gradlew test
+        ./gradlew test testIntegration
 
     - name: Move video
       if: ${{ failure() }}

.continue/rules/personality.md

@@ -1,25 +1,25 @@
-name: 'Run VS Code E2E Test'
-description: 'Run a single VS Code E2E test with all required setup'
+name: "Run VS Code E2E Test"
+description: "Run a single VS Code E2E test with all required setup"
 inputs:
   test_file:
-    description: 'E2E test file to run'
+    description: "E2E test file to run"
     required: true
   command:
-    description: 'Command to run (e2e:ci:run or e2e:ci:run-yaml)'
+    description: "Command to run (e2e:ci:run or e2e:ci:run-yaml)"
     required: true
   ssh_key:
-    description: 'SSH private key for testing'
+    description: "SSH private key for testing"
     required: false
   ssh_host:
-    description: 'SSH host for testing' 
+    description: "SSH host for testing"
     required: false
   is_fork:
-    description: 'Whether this is a fork (affects SSH tests)'
+    description: "Whether this is a fork (affects SSH tests)"
     required: false
-    default: 'false'
+    default: "false"
 
 runs:
-  using: 'composite'
+  using: "composite"
   steps:
     - uses: actions/setup-node@v4
       with:
@@ -58,6 +58,7 @@ runs:
           cd core
           npm ci
           cd ../extensions/vscode
+          npm ci
           npm run e2e:ci:download
         else
           cd core
@@ -131,4 +132,4 @@ runs:
       uses: actions/upload-artifact@v4
       with:
         name: e2e-logs-${{ steps.sanitize_filename.outputs.sanitized_test_file || 'unknown' }}-${{ inputs.command == 'e2e:ci:run-yaml' && 'yaml' || 'json' }}
-        path: extensions/vscode/e2e.log
+        path: extensions/vscode/e2e.log

.github/actions/run-jetbrains-tests/action.yml

@@ -5,7 +5,7 @@
 ## AI Code Review
 
 - **Team members only**: AI review runs automatically when PR is opened or marked ready for review
-- Team members can also trigger a review by commenting `@continue-general-review` or `@continue-detailed-review`
+- Team members can also trigger a review by commenting `@continue-review`
 
 ## Checklist