Updated source paths in docs_mapping.yaml to use ./influxdb3_plugins/ instead of ../influxdb3_plugins/ to match what the

  GitHub Actions workflow expects when it clones the
  repository:

  1. GitHub Actions workflow clones to ./influxdb3_plugins/
  2. docs_mapping.yaml references
  ./influxdb3_plugins/influxdata/[plugin]/README.md
  3. Local development can manually clone the repo to the same
   location for testing

  Tupdated all the source paths in
  docs_mapping.yaml to use ./influxdb3_plugins/ instead of
  ../influxdb3_plugins/. This now matches exactly what the
  GitHub Actions workflow expects when it clones the
  repository.

  The paths are now consistent:

  1. GitHub Actions workflow clones to ./influxdb3_plugins/
  2. docs_mapping.yaml references
  ./influxdb3_plugins/influxdata/[plugin]/README.md
  3. Local development can manually clone the repo to the same
   location for testing

  This resolves the inconsistency and makes the automation
  more reliable. For local development, developers would
  just need to run:

  git clone
  https://github.com/influxdata/influxdb3_plugins.git

  From the docs-v2 root directory, and then they can use the
  same paths that the automation uses.

Author: jstirnaman

.github/workflows/sync-plugins.yml

@@ -83,7 +83,7 @@ jobs:
         run: |
           git clone --filter=blob:none --sparse https://github.com/influxdata/influxdb3_plugins.git influxdb3_plugins
           cd influxdb3_plugins
-          git sparse-checkout set influxdata/ validate_readme.py
+          git sparse-checkout set influxdata/ scripts/
           git checkout ${{ steps.inputs.outputs.source_commit }}
 
       - name: Setup Node.js
@@ -118,10 +118,10 @@ jobs:
           # Run validation
           if [[ -n "$PLUGINS" ]]; then
             echo "Validating specific plugins: $PLUGINS"
-            python validate_readme.py --plugins "$PLUGINS" 2>&1 | tee validation.log
+            python scripts/validate_readme.py --plugins "$PLUGINS" 2>&1 | tee validation.log
           else
             echo "Validating all plugins"
-            python validate_readme.py 2>&1 | tee validation.log
+            python scripts/validate_readme.py 2>&1 | tee validation.log
           fi
           
           # Check if validation passed

helper-scripts/influxdb3-plugins/README.md

@@ -33,7 +33,7 @@ For local testing and development:
 1. **Validate source content** (run from influxdb3_plugins directory):
    ```bash
    cd /path/to/influxdb3_plugins
-   python validate_readme.py
+   python scripts/validate_readme.py
    ```
 
 2. **Transform content** (run from docs-v2 root directory):
@@ -323,7 +323,7 @@ Plugin documentation location:
 
 ## Phase 3: Automation Implementation
 
-### 3.1 Validation Script (validate_readme.py)
+### 3.1 Validation Script (scripts/validate_readme.py)
 
 ```python
 #!/usr/bin/env python3
@@ -577,7 +577,7 @@ Plugin README change → Commit → Automatic comment with sync link
 
 **Process**:
 1. **Parse request** - Extract plugin names and source commit from issue
-2. **Validate source** - Run `validate_readme.py` on specified plugins
+2. **Validate source** - Run `scripts/validate_readme.py` on specified plugins
 3. **Transform content** - Apply docs-v2 formatting and enhancements
 4. **Generate screenshots** - Capture Hugo-rendered plugin pages
 5. **Create PR** - Submit changes with comprehensive summary
@@ -595,7 +595,7 @@ Plugin README change → Commit → Automatic comment with sync link
 
 ### Step 1: Update Source README
 1. Edit README in `influxdb3_plugins/influxdata/[plugin]/`
-2. Run validation: `python validate_readme.py`
+2. Run validation: `python scripts/validate_readme.py`
 3. Fix any validation errors
 
 ### Step 2: Transform Content
@@ -635,7 +635,7 @@ Plugin README change → Commit → Automatic comment with sync link
 
 Before merging any plugin documentation:
 
-- [ ] Source README passes validation (`validate_readme.py`)
+- [ ] Source README passes validation (`scripts/validate_readme.py`)
 - [ ] All required sections present and properly formatted
 - [ ] At least 2 complete usage examples with expected output
 - [ ] All configuration parameters documented