@crownpeak/dqm-react-component-dev-mcp 1.2.0

package/data/probe/build-windows.bat

@@ -0,0 +1,229 @@
+@echo off
+setlocal enabledelayedexpansion
+
+echo.
+echo =======================================
+echo Probe Windows Build Script
+echo =======================================
+echo.
+
+set "BUILD_LOG=%TEMP%\probe-build-windows.log"
+echo Probe Windows Build Started at %date% %time% > "%BUILD_LOG%"
+
+:: Set script directory and repo root
+set "SCRIPT_DIR=%~dp0"
+set "REPO_ROOT=%SCRIPT_DIR%"
+cd /d "%REPO_ROOT%"
+
+echo [1/5] Checking prerequisites...
+echo [1/5] Checking prerequisites... >> "%BUILD_LOG%"
+
+:: Check for Rust installation
+echo   - Checking for Rust installation...
+where /q rustc
+if %ERRORLEVEL% neq 0 (
+    echo [ERROR] Rust is not installed or not in PATH >> "%BUILD_LOG%"
+    echo [ERROR] Rust is not installed or not in PATH.
+    echo         Please install Rust from https://www.rust-lang.org/tools/install
+    echo         Run the following command in your browser:
+    echo         https://static.rust-lang.org/rustup/rustup-init.exe
+    exit /b 1
+) else (
+    rustc --version >> "%BUILD_LOG%" 2>&1
+    echo   - Rust is installed: !ERRORLEVEL!
+)
+
+:: Check for MSYS2 installation
+echo   - Checking for MSYS2 installation...
+if exist "C:\msys64\usr\bin\bash.exe" (
+    echo   - MSYS2 is installed.
+    echo MSYS2 is installed >> "%BUILD_LOG%"
+) else (
+    echo   - [WARNING] MSYS2 does not appear to be installed at the default location.
+    echo   - This is required for GCC compiler toolchain.
+    echo   - Install MSYS2 using Windows Package Manager:
+    echo   - winget install MSYS2.MSYS2
+    echo   - Then install MinGW toolchain by running:
+    echo   - pacman -S --needed base-devel mingw-w64-ucrt-x86_64-toolchain
+    echo   - And add C:\msys64\ucrt64\bin to your PATH
+    echo MSYS2 might not be installed >> "%BUILD_LOG%"
+)
+
+:: Check if GCC is available
+echo   - Checking for GCC compiler...
+where /q gcc
+if %ERRORLEVEL% neq 0 (
+    echo   - [WARNING] GCC compiler not found in PATH.
+    echo   - If you encounter build errors related to 'gcc.exe', you will need to:
+    echo   - 1. Ensure MSYS2 is installed: winget install MSYS2.MSYS2
+    echo   - 2. Open MSYS2 MSYS shell from Start Menu
+    echo   - 3. Run: pacman -S --needed base-devel mingw-w64-ucrt-x86_64-toolchain
+    echo   - 4. Add C:\msys64\ucrt64\bin to your system PATH
+    echo GCC not found in PATH >> "%BUILD_LOG%"
+) else (
+    gcc --version >> "%BUILD_LOG%" 2>&1
+    echo   - GCC compiler found: !ERRORLEVEL!
+)
+
+:: Check for Visual Studio Build Tools
+echo   - Checking for Visual Studio 2022 C++ Build Tools...
+reg query "HKLM\SOFTWARE\Microsoft\VisualStudio\SxS\VS7" /v "17.0" >nul 2>&1
+set VS2022_INSTALLED=%ERRORLEVEL%
+
+reg query "HKLM\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\SxS\VS7" /v "17.0" >nul 2>&1
+set VS2022_INSTALLED_WOW=%ERRORLEVEL%
+
+reg query "HKLM\SOFTWARE\Microsoft\VisualStudio\SxS\VC7" /v "17.0" >nul 2>&1
+set VS2022_VC_INSTALLED=%ERRORLEVEL%
+
+if %VS2022_INSTALLED% equ 0 (
+    echo   - Visual Studio 2022 is installed.
+    echo VS2022 is installed >> "%BUILD_LOG%"
+) else if %VS2022_INSTALLED_WOW% equ 0 (
+    echo   - Visual Studio 2022 is installed (WOW64).
+    echo VS2022 is installed (WOW64) >> "%BUILD_LOG%"
+) else if %VS2022_VC_INSTALLED% equ 0 (
+    echo   - Visual Studio 2022 C++ components are installed.
+    echo VS2022 C++ components are installed >> "%BUILD_LOG%"
+) else (
+    echo   - [WARNING] Visual Studio 2022 Build Tools might not be installed.
+    echo   - This could cause compilation issues with some dependencies.
+    echo   - Download and install Build Tools from:
+    echo   - https://visualstudio.microsoft.com/visual-cpp-build-tools/
+    echo   - Be sure to select "Desktop development with C++" workload.
+    echo VS2022 Build Tools might not be installed >> "%BUILD_LOG%"
+)
+
+:: Check for MSVC installation
+echo   - Checking for Microsoft Visual C++ Redistributable...
+reg query "HKLM\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\x64" /v Version >nul 2>&1
+if %ERRORLEVEL% equ 0 (
+    echo   - Microsoft Visual C++ Redistributable is installed.
+    echo MSVC is installed >> "%BUILD_LOG%"
+) else (
+    reg query "HKLM\SOFTWARE\Classes\Installer\Dependencies\VC,redist.x64,amd64,14.29,bundle" /v Version >nul 2>&1
+    if %ERRORLEVEL% equ 0 (
+        echo   - Microsoft Visual C++ Redistributable is installed.
+        echo MSVC is installed (alternate registry key) >> "%BUILD_LOG%"
+    ) else (
+        echo   - [WARNING] Microsoft Visual C++ Redistributable might not be installed.
+        echo   - The build can proceed, but the binary may not run without installing:
+        echo   - https://aka.ms/vs/17/release/vc_redist.x64.exe
+        echo MSVC might not be installed, but continuing build >> "%BUILD_LOG%"
+    )
+)
+
+echo.
+echo [2/5] Cleaning previous build...
+echo [2/5] Cleaning previous build... >> "%BUILD_LOG%"
+cargo clean
+if %ERRORLEVEL% neq 0 (
+    echo [ERROR] Failed to clean project >> "%BUILD_LOG%"
+    echo [ERROR] Failed to clean project. See build log for details: "%BUILD_LOG%"
+    exit /b 1
+)
+
+echo.
+echo [3/5] Building Probe with Windows-optimized settings...
+echo [3/5] Building Probe with Windows-optimized settings... >> "%BUILD_LOG%"
+echo   - This may take a few minutes...
+echo.
+
+:: Build with release settings
+cargo build --release >> "%BUILD_LOG%" 2>&1
+set BUILD_ERROR=%ERRORLEVEL%
+
+if %BUILD_ERROR% neq 0 (
+    echo [ERROR] Build failed with code %BUILD_ERROR%. >> "%BUILD_LOG%"
+    echo [ERROR] Build failed with code %BUILD_ERROR%.
+    
+    :: Check for specific error patterns in the log
+    findstr /C:"failed to find tool \"gcc.exe\"" "%BUILD_LOG%" >nul 2>&1
+    if %ERRORLEVEL% equ 0 (
+        echo.
+        echo [ERROR DETAILS] Missing GCC compiler.
+        echo.
+        echo This error occurs because the C/C++ compiler toolchain is missing.
+        echo To fix this:
+        echo.
+        echo 1. Install MSYS2 using Windows Package Manager:
+        echo    winget install MSYS2.MSYS2
+        echo.
+        echo 2. Open the "MSYS2 MSYS2" shortcut from the Start Menu
+        echo.
+        echo 3. Install the MinGW-w64 toolchain by running:
+        echo    pacman -S --needed base-devel mingw-w64-ucrt-x86_64-toolchain
+        echo.
+        echo 4. Add the compiler to your PATH:
+        echo    - Open Windows Settings ^> System ^> About ^> Advanced system settings
+        echo    - Click on "Environment Variables"
+        echo    - Edit the "Path" variable under either User or System variables
+        echo    - Add C:\msys64\ucrt64\bin to the list
+        echo    - Click OK and close all dialogs
+        echo.
+        echo 5. Restart your terminal/PowerShell and run this script again
+        echo.
+    ) else (
+        findstr /C:"requires nightly" "%BUILD_LOG%" >nul 2>&1
+        if %ERRORLEVEL% equ 0 (
+            echo [ERROR DETAILS] This project requires the nightly Rust toolchain.
+            echo To fix this, run:
+            echo.
+            echo rustup install nightly
+            echo rustup default nightly
+            echo.
+            echo Then run this script again.
+        ) else (
+            echo See build log for details: "%BUILD_LOG%"
+        )
+    )
+    
+    exit /b 1
+)
+
+echo.
+echo [4/5] Verifying build...
+echo [4/5] Verifying build... >> "%BUILD_LOG%"
+
+:: Check if executable exists
+if not exist "target\release\probe.exe" (
+    echo [ERROR] Build completed but executable not found >> "%BUILD_LOG%"
+    echo [ERROR] Build completed but executable not found at target\release\probe.exe
+    exit /b 1
+)
+
+echo   - Executable created successfully at target\release\probe.exe
+echo   - Executable created successfully >> "%BUILD_LOG%"
+
+echo.
+echo [5/5] Testing executable...
+echo [5/5] Testing executable... >> "%BUILD_LOG%"
+
+:: Test if executable runs
+target\release\probe.exe --help > nul 2>&1
+if %ERRORLEVEL% neq 0 (
+    echo [WARNING] Executable built but test run failed. You may need to install: >> "%BUILD_LOG%"
+    echo [WARNING] Executable built but test run failed.
+    echo           This may be due to missing Microsoft Visual C++ Redistributable.
+    echo           Please install it from: https://aka.ms/vs/17/release/vc_redist.x64.exe
+) else (
+    echo   - Executable test successful
+    echo   - Executable test successful >> "%BUILD_LOG%"
+)
+
+echo.
+echo =======================================
+echo Build completed successfully!
+echo =======================================
+echo.
+echo The probe executable is available at:
+echo   %REPO_ROOT%target\release\probe.exe
+echo.
+echo Build log saved to: "%BUILD_LOG%"
+echo.
+echo Next steps:
+echo   - Run: .\target\release\probe.exe search "query" path\to\search
+echo   - Start MCP server: cd mcp ^&^& npm run build ^&^& node build\index.js
+echo.
+
+endlocal

package/data/probe/codex-config/config.toml

@@ -0,0 +1,6 @@
+# IMPORTANT: the top-level key is `mcp_servers` rather than `mcpServers`.
+[mcp_servers.code-search]
+command = "npx"
+args = ["-y", "@probelabs/probe", "mcp", "server"]
+# env = { "API_KEY" = "value" }
+

package/data/probe/docs/PERFORMANCE_OPTIMIZATION.md

@@ -0,0 +1,161 @@
+# Performance Optimization Methodology
+
+This document describes the systematic approach for identifying and fixing performance bottlenecks in the probe codebase.
+
+## Phase 1: Performance Profiling and Analysis
+
+### Step 1: Establish Baseline Performance
+```bash
+# Build release binary first
+cargo build --release
+
+# Run performance profiling with debug timing
+DEBUG=1 ./target/release/probe search "workflow" ~/go/src/semantic-kernel/ --max-results 10 --timeout 300 2>/dev/null | sed -n '/=== SEARCH TIMING INFORMATION ===/,/====================================/p'
+```
+
+### Step 2: Identify Performance Bottlenecks
+- Parse timing output to identify components taking >1 second
+- Focus on operations consuming >5% of total execution time
+- Look for patterns: repeated operations, inefficient algorithms, unnecessary work
+
+**Example Analysis:**
+```
+=== SEARCH TIMING INFORMATION ===
+Total search time:     53.38s
+Result processing:     39.95s (75% of total - PRIMARY TARGET)
+  - Uncovered lines:   22.73s (43% of total - HIGHEST PRIORITY)  
+  - AST parsing:       11.74s (22% of total - HIGH PRIORITY)
+    - Line map building: 8.90s (biggest AST component)
+  - Term matching:     7.74s (15% of total - HIGH PRIORITY)
+Limit application:     11.72s (22% of total - HIGH PRIORITY)
+===================================
+```
+
+### Step 3: Architecture Research
+For each bottleneck >1s, spawn separate research agents to analyze:
+- Current implementation approach and complexity
+- Root cause analysis of performance issues  
+- Potential optimization strategies with confidence levels
+- Expected performance savings for each strategy
+
+## Phase 2: Implementation Strategy
+
+### Priority Classification:
+- **High Priority**: >8s potential savings or >15% of total time
+- **Medium Priority**: 2-8s potential savings or 5-15% of total time  
+- **Low Priority**: <2s potential savings or <5% of total time
+
+### Implementation Order:
+1. **Quick wins first**: High confidence (8-10/10), low complexity optimizations
+2. **High impact second**: Medium confidence, high potential savings
+3. **Polish last**: Lower impact optimizations for final performance tuning
+
+## Phase 3: Individual Optimization Implementation
+
+For each optimization, follow this exact process:
+
+### Step 1: Pre-Implementation Baseline
+```bash
+# Performance test
+DEBUG=1 ./target/release/probe search "workflow" ~/go/src/semantic-kernel/ --max-results 10 --timeout 300 2>/dev/null | sed -n '/=== SEARCH TIMING INFORMATION ===/,/====================================/p'
+
+# Correctness test  
+./target/release/probe search "stemming" ~/go/src/semantic-kernel/ --max-results 5
+```
+
+### Step 2: Implementation
+- Use architecture agents for complex optimizations
+- Maintain full backward compatibility
+- Add comprehensive comments explaining the optimization
+- Focus on correctness first, performance second
+
+### Step 3: Post-Implementation Verification
+```bash
+# Performance verification (same commands as Step 1)
+DEBUG=1 ./target/release/probe search "workflow" ~/go/src/semantic-kernel/ --max-results 10 --timeout 300 2>/dev/null | sed -n '/=== SEARCH TIMING INFORMATION ===/,/====================================/p'
+
+# Correctness verification - output should be identical
+./target/release/probe search "stemming" ~/go/src/semantic-kernel/ --max-results 5
+
+# Comprehensive testing
+make test
+```
+
+### Step 4: Quality Assurance
+- All tests must pass (unit, integration, CLI tests)
+- Output correctness: same number of results, same content (slight ranking differences OK)
+- Performance improvement: measurable reduction in target timing component
+- Code quality: passes `make lint` and `make format`
+
+### Step 5: Documentation and Commit
+```bash
+# Create separate git commit for each optimization
+git add .
+git commit -m "Optimize [component]: [brief description]
+
+- [Technical details of what was optimized]
+- Performance improvement: [measurement]
+- [Any important implementation notes]
+
+🤖 Generated with [Claude Code](https://claude.ai/code)
+
+Co-Authored-By: Claude <noreply@anthropic.com>"
+```
+
+## Phase 4: Verification Commands
+
+### Standard Performance Test:
+```bash
+DEBUG=1 ./target/release/probe search "workflow" ~/go/src/semantic-kernel/ --max-results 10 --timeout 300 2>/dev/null | sed -n '/=== SEARCH TIMING INFORMATION ===/,/====================================/p'
+```
+
+### Standard Correctness Test:
+```bash
+./target/release/probe search "stemming" ~/go/src/semantic-kernel/ --max-results 5
+```
+
+### Comprehensive Test Suite:
+```bash
+make test
+```
+
+### Output Validation Checklist:
+- ✅ Same number of search results before/after
+- ✅ Same total bytes and tokens returned  
+- ✅ All tests pass without regressions
+- ✅ Performance improvement in target component
+- ✅ No new compilation warnings or errors
+
+## Phase 5: Success Metrics
+
+### Optimization Success Criteria:
+1. **Performance**: Measurable improvement in target timing component
+2. **Correctness**: Identical functional output (same results, bytes, tokens)
+3. **Quality**: All tests pass, no regressions introduced
+4. **Maintainability**: Clean code with comprehensive comments
+5. **Reliability**: Backward compatibility preserved
+
+### Performance Tracking:
+Track cumulative improvements across optimization phases:
+- **Baseline**: 53.38s total search time
+- **After Phase 1**: [timing] ([improvement]% faster)
+- **After Phase 2**: [timing] ([improvement]% faster)  
+- **Final**: [timing] ([improvement]% faster overall)
+
+## Optimization Examples Applied
+
+### High-Impact Optimizations Completed:
+1. **Lazy line map construction**: 980ms improvement (26% faster overall)
+2. **AST node filtering**: 700ms improvement (39% faster line map building)
+3. **Simplified query evaluation**: 45% improvement in filtering time
+4. **Token count caching**: 300ms improvement for repeated tokenization
+5. **Uncovered lines batch processing**: 57ms improvement (26% faster uncovered lines)
+
+### Key Lessons Learned:
+- **Algorithm complexity** often matters more than micro-optimizations
+- **Lazy evaluation** provides significant gains when work can be avoided
+- **Caching strategies** effective for repeated operations on similar data
+- **Early termination** powerful for processing large datasets
+- **Backward compatibility** essential - never sacrifice correctness for performance
+
+This methodology successfully achieved **~95% performance improvement** (53.38s → 2.86s) while maintaining full correctness and backward compatibility.

package/data/probe/examples/cache_demo.rs

@@ -0,0 +1,46 @@
+use probe_code::language::parser::parse_file_for_code_blocks;
+use std::collections::HashSet;
+
+fn main() {
+    // Set up test content
+    let content = r#"
+fn test_function() {
+    // This is a comment
+    let x = 42;
+    println!("Hello, world!");
+}
+
+struct TestStruct {
+    field1: i32,
+    field2: String,
+}
+"#;
+
+    // Create a set of line numbers to extract
+    let mut line_numbers = HashSet::new();
+    line_numbers.insert(3); // Comment line
+    line_numbers.insert(4); // Code line
+    line_numbers.insert(8); // Struct field line
+
+    println!("First call (should be a cache miss):");
+    let result1 = parse_file_for_code_blocks(content, "rs", &line_numbers, true, None).unwrap();
+    println!("Found {} code blocks", result1.len());
+
+    println!("\nSecond call (should be a cache hit):");
+    let result2 = parse_file_for_code_blocks(content, "rs", &line_numbers, true, None).unwrap();
+    println!("Found {} code blocks", result2.len());
+
+    println!("\nThird call with different allow_tests flag (should be a cache miss):");
+    let result3 = parse_file_for_code_blocks(content, "rs", &line_numbers, false, None).unwrap();
+    println!("Found {} code blocks", result3.len());
+
+    println!("\nFourth call with different content (should be a cache miss):");
+    let content2 = r#"
+fn different_function() {
+    // This is a different comment
+    let y = 100;
+}
+"#;
+    let result4 = parse_file_for_code_blocks(content2, "rs", &line_numbers, true, None).unwrap();
+    println!("Found {} code blocks", result4.len());
+}

package/data/probe/examples/chat/.dockerignore

@@ -0,0 +1,37 @@
+# Node.js
+node_modules/
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+.npm
+.yarn
+
+# Logs
+*.log
+logs/
+*.tmp
+
+# Test files (we'll copy them explicitly if needed)
+test/
+*.test.js
+test-*.js
+
+# Development files
+.gitignore
+.git/
+.github/
+.vscode/
+.idea/
+
+# Temporary files
+probe-debug.txt
+simple-traces.jsonl
+*.cache
+
+# Documentation (keep only essential ones)
+TRACING.md
+README.md
+
+# OS generated files
+.DS_Store
+Thumbs.db