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

package/data/probe/scripts/claude-hook-wrapper.sh

@@ -0,0 +1,56 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+#––– Claude Hook Wrapper –––––––––––––––––––––––––––––––––––––––––––––––––
+# Generic wrapper that runs any command and formats output for Claude Code
+# Usage: ./scripts/claude-hook-wrapper.sh <command> [args...]
+#
+# Returns JSON with:
+#   - decision: "approve" if command exits with 0, "block" otherwise
+#   - reason: Success message or command output on failure
+
+#––– CONSTANTS ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
+readonly PASS='approve'
+readonly FAIL='block'
+
+#––– SHORT-CIRCUIT WHEN NESTED ––––––––––––––––––––––––––––––––––––––––––
+if [[ ${CLAUDE_STOP_HOOK_ACTIVE:-false} == "true" ]]; then
+  printf '{"decision":"%s"}\n' "$PASS"
+  exit 0
+fi
+
+#––– CHANGE TO REPOSITORY ROOT –––––––––––––––––––––––––––––––––––––––––
+# This ensures relative paths work correctly regardless of where Claude runs the hook
+cd "$(dirname "$0")/.."
+
+#––– VALIDATE ARGUMENTS –––––––––––––––––––––––––––––––––––––––––––––––––
+if [[ $# -eq 0 ]]; then
+  printf '{"decision":"%s","reason":"Error: No command provided to claude-hook-wrapper.sh"}\n' "$FAIL"
+  exit 1
+fi
+
+#––– JSON ESCAPE FUNCTION ––––––––––––––––––––––––––––––––––––––––––––––
+json_escape() { 
+  if command -v jq >/dev/null 2>&1; then
+    jq -Rs '.' <<<"$1"
+  else
+    # Fallback if jq is not available
+    printf '%s' "$1" | sed 's/\\/\\\\/g; s/"/\\"/g; s/	/\\t/g' | awk '{gsub(/\r/,"\\r"); gsub(/\n/,"\\n"); printf "%s\\n", $0}' | sed '$ s/\\n$//'
+  fi
+}
+
+#––– RUN COMMAND ––––––––––––––––––––––––––––––––––––––––––––––––––––––––
+# Capture both stdout and stderr
+output=$(mktemp)
+trap 'rm -f "$output"' EXIT
+
+# Run the command, capturing all output
+if "$@" >"$output" 2>&1; then
+  # Command succeeded
+  printf '{"decision":"%s","reason":"✅ %s completed successfully!"}\n' "$PASS" "$1"
+else
+  # Command failed - include the output in the reason
+  exit_code=$?
+  reason=$(printf "❌ %s failed with exit code %d!\n\nOutput:\n%s\n\n💡 Please fix the issues above and try again." "$1" "$exit_code" "$(<"$output")")
+  printf '{"decision":"%s","reason":%s}\n' "$FAIL" "$(json_escape "$reason")"
+fi

package/data/probe/site/.env.example

@@ -0,0 +1,10 @@
+# Environment variables for Cloudflare Pages deployment
+# Copy this to .env and configure as needed
+
+# Cloudflare configuration (optional)
+# CLOUDFLARE_ACCOUNT_ID=your-account-id
+# CLOUDFLARE_API_TOKEN=your-api-token
+
+# Build configuration
+NODE_VERSION=20
+NPM_VERSION=latest

package/data/probe/site/DEPLOYMENT.md

@@ -0,0 +1,86 @@
+# Cloudflare Pages Deployment
+
+This documentation site is deployed using Cloudflare Pages with automatic deployments from the main branch to **probelabs.com**.
+
+## Deployment Configuration
+
+### Files
+- `wrangler.toml` - Cloudflare Pages configuration
+- `public/_headers` - HTTP headers for security and caching
+- `public/_redirects` - URL redirect rules
+- `.env.example` - Environment variable template
+
+### Build Settings
+- **Build command**: `npm run build`
+- **Build output directory**: `.vitepress/dist`
+- **Root directory**: `site`
+- **Node.js version**: 20
+
+## Setup Instructions
+
+### 1. Cloudflare Pages Setup
+1. Go to [Cloudflare Pages](https://pages.cloudflare.com/)
+2. Connect your GitHub repository
+3. Configure the build settings:
+   - **Project name**: `probe-docs`
+   - **Production branch**: `main`
+   - **Build command**: `npm run build`
+   - **Build output directory**: `.vitepress/dist`
+   - **Root directory**: `site`
+
+### 2. Environment Variables
+Set these in Cloudflare Pages dashboard if needed:
+- `NODE_VERSION`: `20`
+- `NPM_VERSION`: `latest`
+
+### 3. Custom Domain Setup
+The site is configured to deploy to **probelabs.com**. To set this up:
+
+1. In Cloudflare Pages dashboard, go to Custom domains
+2. Add the domain `probelabs.com`
+3. Add a redirect from `www.probelabs.com` to `probelabs.com` (already configured in `_redirects`)
+4. Update your DNS records:
+   - **A Record**: `probelabs.com` → Your Cloudflare Pages IP
+   - **CNAME**: `www.probelabs.com` → `probelabs.com`
+5. The domain configuration is already set in `wrangler.toml`
+
+## Build Process
+
+The site builds automatically when:
+- Code is pushed to the `main` branch
+- Pull requests are created (preview deployments)
+
+### Local Development
+```bash
+cd site
+npm install
+npm run dev
+```
+
+### Local Build Test
+```bash
+cd site
+npm run build
+npm run preview
+```
+
+## Troubleshooting
+
+### Common Issues
+1. **Build fails**: Check Node.js version is 20
+2. **Assets not loading**: Verify `public/` directory structure
+3. **404 errors**: Check `_redirects` file configuration
+
+### Logs
+Build logs are available in the Cloudflare Pages dashboard under the deployment details.
+
+## Migration Notes
+
+This site was migrated from GitHub Pages. The old workflow file has been disabled and renamed to `vitepress-gh-pages.yml.disabled`.
+
+## Performance Features
+
+- **Edge deployment**: Served from Cloudflare's global edge network
+- **Automatic HTTPS**: SSL certificates managed automatically
+- **Caching**: Optimized caching headers for static assets
+- **Security headers**: CSP and security headers configured

package/data/probe/site/README.md

@@ -0,0 +1,183 @@
+# Probe Documentation Site
+
+This directory contains the VitePress-powered documentation site for the Probe project. This README provides information about the documentation structure, how to contribute, and how to maintain the documentation.
+
+## Documentation Structure
+
+The documentation is organized into several main sections:
+
+- **Getting Started**: Quick Start, Installation, Core Features
+- **Core Functionality**: How It Works, Search Functionality, Code Extraction, CLI Mode
+- **AI Integration**: AI Integration Overview, AI Chat Mode, MCP Server, MCP Integration, Node.js SDK, Web Interface
+- **Language Support**: Language Support Overview, Supported Languages, Adding Languages
+
+For a complete overview of the documentation structure, see [documentation-maintenance.md](./documentation-maintenance.md).
+
+## Key Documentation Files
+
+- **index.md**: Main landing page with feature highlights
+- **quick-start.md**: Getting started guide
+- **installation.md**: Detailed installation instructions
+- **features.md**: Overview of core features
+- **how-it-works.md**: Technical explanation of Probe's architecture
+- **ai-integration.md**: Overview of AI integration capabilities
+- **language-support-overview.md**: Overview of language support features
+- **documentation-guide.md**: Guide for users on how to use the documentation
+- **documentation-maintenance.md**: Technical guide for documentation maintainers
+
+## Cross-References
+
+The documentation uses cross-references to help users navigate between related topics. For a complete guide on cross-references and documentation maintenance, see [documentation-maintenance.md](./documentation-maintenance.md).
+
+When adding new documentation or updating existing documentation, please ensure that cross-references are maintained and updated as needed.
+
+## Defining Features in index.md
+
+The `index.md` file supports a custom features section that can be defined in the frontmatter. Each feature can have the following properties:
+
+```yaml
+features:
+  - icon: 🔎                      # Emoji icon (optional if image is provided)
+    title: Feature Title          # Required
+    details: Feature description  # Required
+    link: /page-link              # Optional link to another page
+    linkText: Learn more          # Optional custom text for the link (defaults to "Learn more")
+    theme: alt                    # Optional theme (alt, brand, or default)
+    image: /icons/my-icon.svg     # Optional image path (replaces the emoji icon)
+    highlight: true               # Optional boolean to highlight the feature
+```
+
+### Example Feature Definition
+
+Here's an example of how to define features in the index.md frontmatter:
+
+```yaml
+---
+layout: home
+
+hero:
+  name: "Probe"
+  text: "Local, AI-ready\nCode Exploration"
+  tagline: "Open-source tooling that truly understands your codebase."
+  
+features:
+  - icon: 🔎
+    title: AST-Aware Code Search
+    details: Search your code with semantic understanding. Find functions, classes, and patterns across your entire codebase.
+    link: /how-it-works
+    linkText: Learn how it works
+    highlight: true
+    
+  - icon: ⚡
+    title: Lightning Fast
+    details: Built on ripgrep and tree-sitter for blazing fast performance. No indexing needed.
+    theme: alt
+    
+  - icon: 🔒
+    title: 100% Local & Private
+    details: Your code stays on your machine. Perfect for sensitive projects.
+    image: /icons/privacy-icon.svg
+---
+```
+
+## Custom Components
+
+The documentation uses several custom components:
+
+### CodeEditor
+
+The `CodeEditor` component displays code snippets with syntax highlighting:
+
+```markdown
+<CodeEditor filePath="example.js">
+function handleError(error) {
+  console.error(`Error: ${error.message}`);
+  return { success: false, error: error.message };
+}
+</CodeEditor>
+```
+
+### CommandExample
+
+The `CommandExample` component displays command-line examples:
+
+```markdown
+<CommandExample>probe search "error handling" ./src</CommandExample>
+```
+
+With output:
+
+```markdown
+<CommandExample output="Found 3 matches in 2 files">probe search "user authentication" ./src</CommandExample>
+```
+
+## Documentation Conventions
+
+Please follow these conventions when contributing to the documentation:
+
+1. **File Names**: Use kebab-case for file names (e.g., `quick-start.md`, `how-it-works.md`)
+2. **Headings**: Use Title Case for headings (e.g., "Getting Started", "Core Functionality")
+3. **Code Examples**: Use appropriate syntax highlighting for code examples
+4. **Cross-References**: Use relative links for cross-references (e.g., `[Quick Start](./quick-start.md)`)
+5. **Images**: Store images in the `public` directory and reference them with absolute paths (e.g., `/images/example.png`)
+
+## Running the Site Locally
+
+To run the site locally:
+
+1. Navigate to the site directory
+2. Install dependencies: `npm install`
+3. Start the development server: `npm run dev`
+
+## Deployment
+
+The site is deployed using **Cloudflare Pages** with automatic deployments from the main branch to **probelabs.com**.
+
+### Deployment Configuration
+- Platform: Cloudflare Pages
+- Domain: probelabs.com
+- Build command: `npm run build`
+- Output directory: `.vitepress/dist`
+- Node.js version: 20
+
+For detailed deployment instructions, see [DEPLOYMENT.md](./DEPLOYMENT.md).
+
+### Previous Deployment
+The site was previously deployed via GitHub Pages. The old workflow has been disabled and renamed to `vitepress-gh-pages.yml.disabled`.
+
+## Building for Production
+
+To build the site for production:
+
+```bash
+npm run build
+```
+
+The built site will be in the `.vitepress/dist` directory.
+
+## Contributing to the Documentation
+
+We welcome contributions to the Probe documentation. If you find errors, omissions, or have suggestions for improvements, please consider contributing:
+
+1. Fork the [Probe repository](https://github.com/probelabs/probe) on GitHub
+2. Make your changes to the documentation files in the `site` directory
+3. Ensure that cross-references are maintained and updated as needed
+4. Run the site locally to verify your changes
+5. Submit a pull request with your changes
+
+## Maintenance Guidelines
+
+When maintaining the documentation:
+
+1. **Keep Cross-References Updated**: When adding or removing documentation, update cross-references in related files
+2. **Maintain Consistent Style**: Follow the established style and formatting conventions
+3. **Update Navigation**: When adding new documentation, update the navigation structure as described in [documentation-maintenance.md](./documentation-maintenance.md)
+4. **Check for Broken Links**: Regularly check for broken links and fix them
+5. **Update Examples**: Keep code examples and command examples up to date with the latest version of Probe
+6. **Review Regularly**: Regularly review the documentation for accuracy and completeness
+
+## VitePress Configuration
+
+The VitePress configuration is located in the `.vitepress/config.js` file. When updating the documentation structure, be sure to update the sidebar and navigation configuration in this file.
+
+For more information on VitePress configuration, see the [VitePress documentation](https://vitepress.dev/reference/site-config).# Temporary test change

package/data/probe/site/adding-languages.md

@@ -0,0 +1,135 @@
+# Adding Support for New Languages
+
+This guide lists the exact files you must modify to add a new language to Probe.
+
+## Required File Modifications
+
+Adding a new language requires modifying exactly **11 files**. Missing any of these will result in incomplete language support.
+
+### Step 1: Core Language Implementation (4 files)
+### Step 2: Search & Extract Integration (4 files)
+### Step 3: CLI & User Interface (2 files)
+### Step 4: Documentation (1 file)
+
+## Step 1: Core Language Implementation
+
+### File 1: `Cargo.toml`
+Add tree-sitter dependency:
+```toml
+tree-sitter-yourlang = "X.Y.Z"
+```
+
+### File 2: `src/language/yourlang.rs`
+Create language implementation (copy from existing language like `rust.rs`):
+```rust
+use super::language_trait::LanguageImpl;
+use tree_sitter::{Language as TSLanguage, Node};
+
+pub struct YourLangLanguage;
+
+impl LanguageImpl for YourLangLanguage {
+    fn get_tree_sitter_language(&self) -> TSLanguage {
+        tree_sitter_yourlang::language().into()
+    }
+    // ... implement other required methods
+}
+```
+
+### File 3: `src/language/mod.rs`
+Add module export:
+```rust
+pub mod yourlang;
+```
+
+### File 4: `src/language/factory.rs`
+Add import:
+```rust
+use probe_code::language::yourlang::YourLangLanguage;
+```
+Add registration:
+```rust
+"yourext" => Some(Box::new(YourLangLanguage::new())),
+```
+
+## Step 2: Search & Extract Integration
+
+### File 5: `src/search/file_list_cache.rs`
+Add to `get_language_extensions()` function:
+```rust
+"yourlang" => vec![".yourext".to_string()],
+```
+
+### File 6: `src/extract/formatter.rs`
+Add to syntax highlighting mapping:
+```rust
+"yourext" => "yourlang",
+```
+
+### File 7: `src/search/results_formatter.rs`
+Add to language mapping:
+```rust
+"yourext" => "yourlang",
+```
+
+### File 8: `src/search/search_output.rs`
+Add to language mapping and comment prefix:
+```rust
+// In syntax highlighting mapping:
+"yourext" => "yourlang",
+
+// In comment prefix mapping (choose appropriate section):
+// For # comments:
+"py" | "rb" | "sh" | "bash" | "pl" | "r" | "yourext" => "#",
+// For // comments:
+"rs" | "c" | "h" | "cpp" | "yourext" => "//",
+```
+
+## Step 3: CLI & User Interface
+
+### File 9: `src/cli.rs`
+Add to language completion lists (2 locations):
+```rust
+"yourlang", "yourext",
+```
+
+### File 10: `npm/src/mcp/index.ts`
+Add to supported languages description:
+```rust
+'Supported languages: rust, javascript, typescript, python, go, c, cpp, java, ruby, php, swift, csharp, yourlang.',
+```
+
+## Step 4: Documentation
+
+### File 11: `site/supported-languages.md`
+Add table entry and language-specific features section.
+
+## Testing
+
+Create comprehensive tests in your language file:
+```rust
+#[cfg(test)]
+mod tests {
+    use super::*;
+    // Add tests for all LanguageImpl methods
+}
+```
+
+## LanguageImpl Methods to Implement
+
+Copy implementation patterns from similar languages:
+
+- `get_tree_sitter_language()` - Return tree-sitter language
+- `is_acceptable_parent()` - Define extractable code blocks
+- `is_test_node()` - Detect test code
+- `get_symbol_signature()` - Extract clean signatures
+- `find_parent_function()` - Optional method
+
+Use tree-sitter playground to understand AST structure: https://tree-sitter.github.io/tree-sitter/playground
+
+## Verification
+
+After modifying all 11 files:
+1. `cargo test` - All tests pass
+2. `cargo run -- search "term" file.yourext` - Search works
+3. `cargo run -- extract file.yourext:N` - Extract works
+4. `cargo run -- search "test" --allow-tests` - Test detection works