feat: add devcontainer profiles for MCP development

- Split devcontainer config into base + profile structure
  - default: Standard Superset development (port 9001)
  - with-mcp: Superset + MCP service (ports 9001, 5008)
- Add MCP service to docker-compose-light.yml as optional profile
- Update start-superset.sh to conditionally start MCP when ENABLE_MCP=true
- Add MCP case to docker-bootstrap.sh for starting MCP service
- Preserve original devcontainer.json as .old for migration reference

This allows developers to choose their development environment:
- Use default profile for standard Superset development
- Use with-mcp profile for MCP/LLM agent development
- MCP service runs on port 5008 when enabled via profile

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

.devcontainer/Dockerfile

@@ -1,20 +0,0 @@
-# Keep this in sync with the base image in the main Dockerfile (ARG PY_VER)
-FROM python:3.11.13-trixie AS base
-
-# Install system dependencies that Superset needs
-# This layer will be cached across Codespace sessions
-RUN apt-get update && apt-get install -y \
-    libsasl2-dev \
-    libldap2-dev \
-    libpq-dev \
-    tmux \
-    gh \
-    && rm -rf /var/lib/apt/lists/*
-
-# Install uv for fast Python package management
-# This will also be cached in the image
-RUN curl -LsSf https://astral.sh/uv/install.sh | sh && \
-    echo 'export PATH="/root/.cargo/bin:$PATH"' >> /etc/bash.bashrc
-
-# Set the cargo/bin directory in PATH for all users
-ENV PATH="/root/.cargo/bin:${PATH}"

.devcontainer/README.md

@@ -3,14 +3,3 @@
 For complete documentation on using GitHub Codespaces with Apache Superset, please see:
 
 **[Setting up a Development Environment - GitHub Codespaces](https://superset.apache.org/docs/contributing/development#github-codespaces-cloud-development)**
-
-## Pre-installed Development Environment
-
-When you create a new Codespace from this repository, it automatically:
-
-1. **Creates a Python virtual environment** using `uv venv`
-2. **Installs all development dependencies** via `uv pip install -r requirements/development.txt`
-3. **Sets up pre-commit hooks** with `pre-commit install`
-4. **Activates the virtual environment** automatically in all terminals
-
-The virtual environment is located at `/workspaces/{repository-name}/.venv` and is automatically activated through environment variables set in the devcontainer configuration.

.devcontainer/bashrc-additions

@@ -1,62 +0,0 @@
-# Superset Codespaces environment setup
-# This file is appended to ~/.bashrc during Codespace setup
-
-# Find the workspace directory (handles both 'superset' and 'superset-2' names)
-WORKSPACE_DIR=$(find /workspaces -maxdepth 1 -name "superset*" -type d | head -1)
-
-if [ -n "$WORKSPACE_DIR" ]; then
-    # Check if virtual environment exists
-    if [ -d "$WORKSPACE_DIR/.venv" ]; then
-        # Activate the virtual environment
-        source "$WORKSPACE_DIR/.venv/bin/activate"
-        echo "✅ Python virtual environment activated"
-
-        # Verify pre-commit is installed and set up
-        if command -v pre-commit &> /dev/null; then
-            echo "✅ pre-commit is available ($(pre-commit --version))"
-            # Install git hooks if not already installed
-            if [ -d "$WORKSPACE_DIR/.git" ] && [ ! -f "$WORKSPACE_DIR/.git/hooks/pre-commit" ]; then
-                echo "🪝 Installing pre-commit hooks..."
-                cd "$WORKSPACE_DIR" && pre-commit install
-            fi
-        else
-            echo "⚠️  pre-commit not found. Run: pip install pre-commit"
-        fi
-    else
-        echo "⚠️  Python virtual environment not found at $WORKSPACE_DIR/.venv"
-        echo "   Run: cd $WORKSPACE_DIR && .devcontainer/setup-dev.sh"
-    fi
-
-    # Always cd to the workspace directory for convenience
-    cd "$WORKSPACE_DIR"
-fi
-
-# Add helpful aliases for Superset development
-alias start-superset="$WORKSPACE_DIR/.devcontainer/start-superset.sh"
-alias setup-dev="$WORKSPACE_DIR/.devcontainer/setup-dev.sh"
-
-# Show helpful message on login
-echo ""
-echo "🚀 Superset Codespaces Environment"
-echo "=================================="
-
-# Check if Superset is running
-if docker ps 2>/dev/null | grep -q "superset"; then
-    echo "✅ Superset is running!"
-    echo "   - Check the 'Ports' tab for your live Superset URL"
-    echo "   - Initial startup takes 10-20 minutes"
-    echo "   - Login: admin/admin"
-else
-    echo "⚠️  Superset is not running. Use: start-superset"
-    # Check if there's a startup log
-    if [ -f "/tmp/superset-startup.log" ]; then
-        echo "   📋 Startup log found: cat /tmp/superset-startup.log"
-    fi
-fi
-
-echo ""
-echo "Quick commands:"
-echo "  start-superset - Start Superset with Docker Compose"
-echo "  setup-dev      - Set up Python environment (if not already done)"
-echo "  pre-commit run - Run pre-commit checks on staged files"
-echo ""

.devcontainer/build-and-push-image.sh

@@ -1,20 +0,0 @@
-#!/bin/bash
-# Script to build and push the devcontainer image to GitHub Container Registry
-# This allows caching the image between Codespace sessions
-
-# You'll need to run this with appropriate GitHub permissions
-# gh auth login --scopes write:packages
-
-REGISTRY="ghcr.io"
-OWNER="apache"
-REPO="superset"
-TAG="devcontainer-base"
-
-echo "Building devcontainer image..."
-docker build -t $REGISTRY/$OWNER/$REPO:$TAG .devcontainer/
-
-echo "Pushing to GitHub Container Registry..."
-docker push $REGISTRY/$OWNER/$REPO:$TAG
-
-echo "Done! Update .devcontainer/devcontainer.json to use:"
-echo "  \"image\": \"$REGISTRY/$OWNER/$REPO:$TAG\""

.devcontainer/default/devcontainer.json

@@ -0,0 +1,19 @@
+{
+  // Extend the base configuration
+  "extends": "../devcontainer-base.json",
+
+  "name": "Apache Superset Development (Default)",
+
+  // Forward ports for development
+  "forwardPorts": [9001],
+  "portsAttributes": {
+    "9001": {
+      "label": "Superset (via Webpack Dev Server)",
+      "onAutoForward": "notify",
+      "visibility": "public"
+    }
+  },
+
+  // Auto-start Superset on Codespace resume
+  "postStartCommand": ".devcontainer/start-superset.sh"
+}

.devcontainer/devcontainer-base.json

@@ -0,0 +1,39 @@
+{
+  "name": "Apache Superset Development",
+  // Keep this in sync with the base image in Dockerfile (ARG PY_VER)
+  // Using the same base as Dockerfile, but non-slim for dev tools
+  "image": "python:3.11.13-bookworm",
+
+  "features": {
+    "ghcr.io/devcontainers/features/docker-in-docker:2": {
+      "moby": true,
+      "dockerDashComposeVersion": "v2"
+    },
+    "ghcr.io/devcontainers/features/node:1": {
+      "version": "20"
+    },
+    "ghcr.io/devcontainers/features/git:1": {},
+    "ghcr.io/devcontainers/features/common-utils:2": {
+      "configureZshAsDefaultShell": true
+    },
+    "ghcr.io/devcontainers/features/sshd:1": {
+      "version": "latest"
+    }
+  },
+
+  // Run commands after container is created
+  "postCreateCommand": "chmod +x .devcontainer/setup-dev.sh && .devcontainer/setup-dev.sh",
+
+  // VS Code customizations
+  "customizations": {
+    "vscode": {
+      "extensions": [
+        "ms-python.python",
+        "ms-python.vscode-pylance",
+        "charliermarsh.ruff",
+        "dbaeumer.vscode-eslint",
+        "esbenp.prettier-vscode"
+      ]
+    }
+  }
+}

.devcontainer/devcontainer.json.old

@@ -1,15 +1,8 @@
 {
   "name": "Apache Superset Development",
-  // Option 1: Use pre-built image directly
-  // "image": "ghcr.io/apache/superset:devcontainer-base",
-
-  // Option 2: Build from Dockerfile with cache (current approach)
-  "build": {
-    "dockerfile": "Dockerfile",
-    "context": ".",
-    // Cache from the Apache registry image
-    "cacheFrom": ["ghcr.io/apache/superset:devcontainer-base"]
-  },
+  // Keep this in sync with the base image in Dockerfile (ARG PY_VER)
+  // Using the same base as Dockerfile, but non-slim for dev tools
+  "image": "python:3.11.13-bookworm",
 
   "features": {
     "ghcr.io/devcontainers/features/docker-in-docker:2": {
@@ -39,17 +32,10 @@
   },
 
   // Run commands after container is created
-  "postCreateCommand": "bash .devcontainer/setup-dev.sh || echo '⚠️ Setup had issues - run .devcontainer/setup-dev.sh manually'",
+  "postCreateCommand": "chmod +x .devcontainer/setup-dev.sh && .devcontainer/setup-dev.sh",
 
-  // Auto-start Superset after ensuring Docker is ready
-  // Run in foreground to see any errors, but don't block on failures
-  "postStartCommand": "bash -c 'echo \"Waiting 30s for services to initialize...\"; sleep 30; .devcontainer/start-superset.sh || echo \"⚠️ Auto-start failed - run start-superset manually\"'",
-
-  // Set environment variables
-  "remoteEnv": {
-    // Removed automatic venv activation to prevent startup issues
-    // The setup script will handle this
-  },
+  // Auto-start Superset on Codespace resume
+  "postStartCommand": ".devcontainer/start-superset.sh",
 
   // VS Code customizations
   "customizations": {

.devcontainer/setup-dev.sh

@@ -3,76 +3,30 @@
 
 echo "🔧 Setting up Superset development environment..."
 
-# System dependencies and uv are now pre-installed in the Docker image
-# This speeds up Codespace creation significantly!
+# The universal image has most tools, just need Superset-specific libs
+echo "📦 Installing Superset-specific dependencies..."
+sudo apt-get update
+sudo apt-get install -y \
+    libsasl2-dev \
+    libldap2-dev \
+    libpq-dev \
+    tmux \
+    gh
 
-# Create virtual environment using uv
-echo "🐍 Creating Python virtual environment..."
-if ! uv venv; then
-    echo "❌ Failed to create virtual environment"
-    exit 1
-fi
+# Install uv for fast Python package management
+echo "📦 Installing uv..."
+curl -LsSf https://astral.sh/uv/install.sh | sh
 
-# Install Python dependencies
-echo "📦 Installing Python dependencies..."
-if ! uv pip install -r requirements/development.txt; then
-    echo "❌ Failed to install Python dependencies"
-    echo "💡 You may need to run this manually after the Codespace starts"
-    exit 1
-fi
-
-# Install pre-commit hooks
-echo "🪝 Installing pre-commit hooks..."
-if source .venv/bin/activate && pre-commit install; then
-    echo "✅ Pre-commit hooks installed"
-else
-    echo "⚠️  Pre-commit hooks installation failed (non-critical)"
-fi
+# Add cargo/bin to PATH for uv
+echo 'export PATH="$HOME/.cargo/bin:$PATH"' >> ~/.bashrc
+echo 'export PATH="$HOME/.cargo/bin:$PATH"' >> ~/.zshrc
 
 # Install Claude Code CLI via npm
 echo "🤖 Installing Claude Code..."
-if npm install -g @anthropic-ai/claude-code; then
-    echo "✅ Claude Code installed"
-else
-    echo "⚠️  Claude Code installation failed (non-critical)"
-fi
+npm install -g @anthropic-ai/claude-code
 
 # Make the start script executable
 chmod +x .devcontainer/start-superset.sh
 
-# Add bashrc additions for automatic venv activation
-echo "🔧 Setting up automatic environment activation..."
-if [ -f ~/.bashrc ]; then
-    # Check if we've already added our additions
-    if ! grep -q "Superset Codespaces environment setup" ~/.bashrc; then
-        echo "" >> ~/.bashrc
-        cat .devcontainer/bashrc-additions >> ~/.bashrc
-        echo "✅ Added automatic venv activation to ~/.bashrc"
-    else
-        echo "✅ Bashrc additions already present"
-    fi
-else
-    # Create bashrc if it doesn't exist
-    cat .devcontainer/bashrc-additions > ~/.bashrc
-    echo "✅ Created ~/.bashrc with automatic venv activation"
-fi
-
-# Also add to zshrc since that's the default shell
-if [ -f ~/.zshrc ] || [ -n "$ZSH_VERSION" ]; then
-    if ! grep -q "Superset Codespaces environment setup" ~/.zshrc; then
-        echo "" >> ~/.zshrc
-        cat .devcontainer/bashrc-additions >> ~/.zshrc
-        echo "✅ Added automatic venv activation to ~/.zshrc"
-    fi
-fi
-
 echo "✅ Development environment setup complete!"
-echo ""
-echo "📝 The virtual environment will be automatically activated in new terminals"
-echo ""
-echo "🔄 To activate in this terminal, run:"
-echo "   source ~/.bashrc"
-echo ""
-echo "🚀 To start Superset:"
-echo "   start-superset"
-echo ""
+echo "🚀 Run '.devcontainer/start-superset.sh' to start Superset"

.devcontainer/start-superset.sh

@@ -1,14 +1,14 @@
 #!/bin/bash
 # Startup script for Superset in Codespaces
 
-# Log to a file for debugging
-LOG_FILE="/tmp/superset-startup.log"
-echo "[$(date)] Starting Superset startup script" >> "$LOG_FILE"
-echo "[$(date)] User: $(whoami), PWD: $(pwd)" >> "$LOG_FILE"
-
 echo "🚀 Starting Superset in Codespaces..."
 echo "🌐 Frontend will be available at port 9001"
 
+# Check if MCP is enabled
+if [ "$ENABLE_MCP" = "true" ]; then
+    echo "🤖 MCP Service will be available at port 5008"
+fi
+
 # Find the workspace directory (Codespaces clones as 'superset', not 'superset-2')
 WORKSPACE_DIR=$(find /workspaces -maxdepth 1 -name "superset*" -type d | head -1)
 if [ -n "$WORKSPACE_DIR" ]; then
@@ -18,71 +18,32 @@ else
     echo "📁 Using current directory: $(pwd)"
 fi
 
-# Wait for Docker to be available
-echo "⏳ Waiting for Docker to start..."
-echo "[$(date)] Waiting for Docker..." >> "$LOG_FILE"
-max_attempts=30
-attempt=0
-while ! docker info > /dev/null 2>&1; do
-    if [ $attempt -eq $max_attempts ]; then
-        echo "❌ Docker failed to start after $max_attempts attempts"
-        echo "[$(date)] Docker failed to start after $max_attempts attempts" >> "$LOG_FILE"
-        echo "🔄 Please restart the Codespace or run this script manually later"
-        exit 1
-    fi
-    echo "   Attempt $((attempt + 1))/$max_attempts..."
-    echo "[$(date)] Docker check attempt $((attempt + 1))/$max_attempts" >> "$LOG_FILE"
-    sleep 2
-    attempt=$((attempt + 1))
-done
-echo "✅ Docker is ready!"
-echo "[$(date)] Docker is ready" >> "$LOG_FILE"
-
-# Check if Superset containers are already running
-if docker ps | grep -q "superset"; then
-    echo "✅ Superset containers are already running!"
-    echo ""
-    echo "🌐 To access Superset:"
-    echo "   1. Click the 'Ports' tab at the bottom of VS Code"
-    echo "   2. Find port 9001 and click the globe icon to open"
-    echo "   3. Wait 10-20 minutes for initial startup"
-    echo ""
-    echo "📝 Login credentials: admin/admin"
-    exit 0
+# Check if docker is running
+if ! docker info > /dev/null 2>&1; then
+    echo "⏳ Waiting for Docker to start..."
+    sleep 5
 fi
 
 # Clean up any existing containers
 echo "🧹 Cleaning up existing containers..."
-docker-compose -f docker-compose-light.yml down
+docker-compose -f docker-compose-light.yml --profile mcp down
 
 # Start services
-echo "🏗️  Starting Superset in background (daemon mode)..."
+echo "🏗️  Building and starting services..."
 echo ""
+echo "📝 Once started, login with:"
+echo "   Username: admin"
+echo "   Password: admin"
+echo ""
+echo "📋 Running in foreground with live logs (Ctrl+C to stop)..."
 
-# Start in detached mode
-docker-compose -f docker-compose-light.yml up -d
-
-echo ""
-echo "✅ Docker Compose started successfully!"
-echo ""
-echo "📋 Important information:"
-echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo "⏱️  Initial startup takes 10-20 minutes"
-echo "🌐 Check the 'Ports' tab for your Superset URL (port 9001)"
-echo "👤 Login: admin / admin"
-echo ""
-echo "📊 Useful commands:"
-echo "   docker-compose -f docker-compose-light.yml logs -f    # Follow logs"
-echo "   docker-compose -f docker-compose-light.yml ps         # Check status"
-echo "   docker-compose -f docker-compose-light.yml down       # Stop services"
-echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo ""
-echo "💤 Keeping terminal open for 60 seconds to test persistence..."
-sleep 60
-echo "✅ Test complete - check if this terminal is still visible!"
-
-# Show final status
-docker-compose -f docker-compose-light.yml ps
+# Run docker-compose and capture exit code
+if [ "$ENABLE_MCP" = "true" ]; then
+    echo "🤖 Starting with MCP Service enabled..."
+    docker-compose -f docker-compose-light.yml --profile mcp up
+else
+    docker-compose -f docker-compose-light.yml up
+fi
 EXIT_CODE=$?
 
 # If it failed, provide helpful instructions

.devcontainer/with-mcp/devcontainer.json

@@ -0,0 +1,29 @@
+{
+  // Extend the base configuration
+  "extends": "../devcontainer-base.json",
+
+  "name": "Apache Superset Development with MCP",
+
+  // Forward ports for development
+  "forwardPorts": [9001, 5008],
+  "portsAttributes": {
+    "9001": {
+      "label": "Superset (via Webpack Dev Server)",
+      "onAutoForward": "notify",
+      "visibility": "public"
+    },
+    "5008": {
+      "label": "MCP Service (Model Context Protocol)",
+      "onAutoForward": "notify",
+      "visibility": "private"
+    }
+  },
+
+  // Auto-start Superset with MCP on Codespace resume
+  "postStartCommand": "ENABLE_MCP=true .devcontainer/start-superset.sh",
+
+  // Environment variables
+  "containerEnv": {
+    "ENABLE_MCP": "true"
+  }
+}

.github/CODEOWNERS

@@ -2,7 +2,7 @@
 
 # https://github.com/apache/superset/issues/13351
 
-/superset/migrations/ @mistercrunch @michael-s-molina @betodealmeida @eschutho @sadpandajoe
+/superset/migrations/ @mistercrunch @michael-s-molina @betodealmeida @eschutho
 
 # Notify some committers of changes in the components
 
@@ -30,13 +30,3 @@
 
 **/*.geojson @villebro @rusackas
 /superset-frontend/plugins/legacy-plugin-chart-country-map/ @villebro @rusackas
-
-# Notify PMC members of changes to extension-related files
-
-/superset-core/ @michael-s-molina @villebro
-/superset-extensions-cli/ @michael-s-molina @villebro
-/superset/core/ @michael-s-molina @villebro
-/superset/extensions/ @michael-s-molina @villebro
-/superset-frontend/src/packages/superset-core/ @michael-s-molina @villebro
-/superset-frontend/src/core/ @michael-s-molina @villebro
-/superset-frontend/src/extensions/ @michael-s-molina @villebro

.github/actions/change-detector/action.yml

@@ -1,27 +1,24 @@
-name: Change Detector
-description: Detects file changes for pull request and push events
+name: 'Change Detector'
+description: 'Detects file changes for pull request and push events'
 inputs:
   token:
-    description: GitHub token for authentication
+    description: 'GitHub token for authentication'
     required: true
 outputs:
   python:
-    description: Whether Python-related files were changed
+    description: 'Whether Python-related files were changed'
     value: ${{ steps.change-detector.outputs.python }}
   frontend:
-    description: Whether frontend-related files were changed
+    description: 'Whether frontend-related files were changed'
     value: ${{ steps.change-detector.outputs.frontend }}
   docker:
-    description: Whether docker-related files were changed
+    description: 'Whether docker-related files were changed'
     value: ${{ steps.change-detector.outputs.docker }}
   docs:
-    description: Whether docs-related files were changed
+    description: 'Whether docs-related files were changed'
     value: ${{ steps.change-detector.outputs.docs }}
-  superset-extensions-cli:
-    description: Whether superset-extensions-cli package-related files were changed
-    value: ${{ steps.change-detector.outputs.superset-extensions-cli }}
 runs:
-  using: composite
+  using: 'composite'
   steps:
     - name: Detect file changes
       id: change-detector

.github/workflows/docker.yml

@@ -22,7 +22,7 @@ jobs:
     steps:
       - id: set_matrix
         run: |
-          MATRIX_CONFIG=$(if [ "${{ github.event_name }}" == "pull_request" ]; then echo '["dev", "lean"]'; else echo '["dev", "lean", "py310", "websocket", "dockerize", "py311", "py312"]'; fi)
+          MATRIX_CONFIG=$(if [ "${{ github.event_name }}" == "pull_request" ]; then echo '["dev", "lean"]'; else echo '["dev", "lean", "py310", "websocket", "dockerize", "py311"]'; fi)
           echo "matrix_config=${MATRIX_CONFIG}" >> $GITHUB_OUTPUT
           echo $GITHUB_OUTPUT
 
@@ -102,7 +102,7 @@ jobs:
           docker history $IMAGE_TAG
 
       - name: docker-compose sanity check
-        if: (steps.check.outputs.python || steps.check.outputs.frontend || steps.check.outputs.docker) && matrix.build_preset == 'dev'
+        if: (steps.check.outputs.python || steps.check.outputs.frontend || steps.check.outputs.docker) && (matrix.build_preset == 'dev' || matrix.build_preset == 'lean')
         shell: bash
         run: |
           export SUPERSET_BUILD_TARGET=${{ matrix.build_preset }}

.github/workflows/ephemeral-env-pr-close.yml

@@ -1,10 +1,4 @@
-name: Cleanup ephemeral envs (PR close) [DEPRECATED]
-
-# ⚠️  DEPRECATION NOTICE ⚠️
-# This workflow is deprecated and will be removed in a future version.
-# The new Superset Showtime workflow handles cleanup automatically.
-# See .github/workflows/showtime.yml and showtime-cleanup.yml for replacements.
-# Migration guide: https://github.com/mistercrunch/superset-showtime
+name: Cleanup ephemeral envs (PR close)
 
 on:
   pull_request_target:
@@ -77,5 +71,5 @@ jobs:
               issue_number: ${{ github.event.number }},
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: '⚠️ **DEPRECATED WORKFLOW** - Ephemeral environment shutdown and build artifacts deleted. Please migrate to the new Superset Showtime system for future PRs.'
+              body: 'Ephemeral environment shutdown and build artifacts deleted.'
             })

.github/workflows/ephemeral-env.yml

@@ -1,12 +1,4 @@
-name: Ephemeral env workflow [DEPRECATED]
-
-# ⚠️  DEPRECATION NOTICE ⚠️
-# This workflow is deprecated and will be removed in a future version.
-# Please use the new Superset Showtime workflow instead:
-# - Use label "🎪 trigger-start" instead of "testenv-up"
-# - Showtime provides better reliability and easier management
-# - See .github/workflows/showtime.yml for the replacement
-# - Migration guide: https://github.com/mistercrunch/superset-showtime
+name: Ephemeral env workflow
 
 # Example manual trigger:
 # gh workflow run ephemeral-env.yml --ref fix_ephemerals --field label_name="testenv-up" --field issue_number=666
@@ -134,11 +126,8 @@ jobs:
               throw new Error("Issue number is not available.");
             }
 
-            const body = `⚠️ **DEPRECATED WORKFLOW** ⚠️\n\n@${user} This workflow is deprecated! Please use the new **Superset Showtime** system instead:\n\n` +
-              `- Replace "testenv-up" label with "🎪 trigger-start"\n` +
-              `- Better reliability and easier management\n` +
-              `- See https://github.com/mistercrunch/superset-showtime for details\n\n` +
-              `Processing your ephemeral environment request [here](${workflowUrl}). Action: **${action}**.` +
+            const body = `@${user} Processing your ephemeral environment request [here](${workflowUrl}).` +
+              ` Action: **${action}**.` +
               ` More information on [how to use or configure ephemeral environments]` +
               `(https://superset.apache.org/docs/contributing/howtos/#github-ephemeral-environments)`;
 

.github/workflows/showtime-cleanup.yml

@@ -1,50 +0,0 @@
-name: 🎪 Showtime Cleanup
-
-# Scheduled cleanup of expired environments
-on:
-  schedule:
-    - cron: '0 */6 * * *'  # Every 6 hours
-
-  # Manual trigger for testing
-  workflow_dispatch:
-    inputs:
-      max_age_hours:
-        description: 'Maximum age in hours before cleanup'
-        required: false
-        default: '48'
-        type: string
-
-# Common environment variables
-env:
-  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-  AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
-  AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-  AWS_REGION: ${{ vars.AWS_REGION || 'us-west-2' }}
-  GITHUB_ORG: ${{ github.repository_owner }}
-  GITHUB_REPO: ${{ github.event.repository.name }}
-
-jobs:
-  cleanup-expired:
-    name: Clean up expired showtime environments
-    runs-on: ubuntu-latest
-
-    permissions:
-      contents: read
-      pull-requests: write
-
-    steps:
-      - name: Install Superset Showtime
-        run: pip install superset-showtime
-
-      - name: Cleanup expired environments
-        run: |
-          MAX_AGE="${{ github.event.inputs.max_age_hours || '48' }}"
-
-          # Validate max_age is numeric
-          if [[ ! "$MAX_AGE" =~ ^[0-9]+$ ]]; then
-            echo "❌ Invalid max_age_hours format: $MAX_AGE (must be numeric)"
-            exit 1
-          fi
-
-          echo "Cleaning up environments older than ${MAX_AGE}h"
-          python -m showtime cleanup --older-than "${MAX_AGE}h"

.github/workflows/showtime-trigger.yml

@@ -1,179 +0,0 @@
-name: 🎪 Superset Showtime
-
-# Ultra-simple: just sync on any PR state change
-on:
-  pull_request_target:
-    types: [labeled, unlabeled, synchronize, closed]
-
-  # Manual testing
-  workflow_dispatch:
-    inputs:
-      pr_number:
-        description: 'PR number to sync'
-        required: true
-        type: number
-      sha:
-        description: 'Specific SHA to deploy (optional, defaults to latest)'
-        required: false
-        type: string
-
-# Common environment variables for all jobs (non-sensitive only)
-env:
-  AWS_REGION: us-west-2
-  GITHUB_ORG: ${{ github.repository_owner }}
-  GITHUB_REPO: ${{ github.event.repository.name }}
-  GITHUB_ACTOR: ${{ github.actor }}
-
-jobs:
-  sync:
-    name: 🎪 Sync PR to desired state
-    runs-on: ubuntu-latest
-    timeout-minutes: 90
-
-    permissions:
-      contents: read
-      pull-requests: write
-
-    steps:
-      - name: Security Check - Authorize Maintainers Only
-        id: auth
-        uses: actions/github-script@v7
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          script: |
-            const actor = context.actor;
-            console.log(`🔍 Checking authorization for ${actor}`);
-
-            // Early exit for workflow_dispatch - assume authorized since it's manually triggered
-            if (context.eventName === 'workflow_dispatch') {
-              console.log(`✅ Workflow dispatch event - assuming authorized for ${actor}`);
-              core.setOutput('authorized', 'true');
-              return;
-            }
-
-            const { data: permission } = await github.rest.repos.getCollaboratorPermissionLevel({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              username: actor
-            });
-
-            console.log(`📊 Permission level for ${actor}: ${permission.permission}`);
-            const authorized = ['write', 'admin'].includes(permission.permission);
-
-            if (!authorized) {
-              console.log(`🚨 Unauthorized user ${actor} - skipping all operations`);
-              core.setOutput('authorized', 'false');
-              return;
-            }
-
-            console.log(`✅ Authorized maintainer: ${actor}`);
-            core.setOutput('authorized', 'true');
-
-            // If this is a synchronize event, check if Showtime is active and set blocked label
-            if (context.eventName === 'pull_request_target' && context.payload.action === 'synchronize') {
-              console.log(`🔒 Synchronize event detected - checking if Showtime is active`);
-
-              // Check if PR has any circus tent labels (Showtime is in use)
-              const { data: issue } = await github.rest.issues.get({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: context.payload.pull_request.number
-              });
-
-              const hasCircusLabels = issue.labels.some(label => label.name.startsWith('🎪 '));
-
-              if (hasCircusLabels) {
-                console.log(`🎪 Circus labels found - setting blocked label to prevent auto-deployment`);
-
-                await github.rest.issues.addLabels({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  issue_number: context.payload.pull_request.number,
-                  labels: ['🎪 🔒 showtime-blocked']
-                });
-
-                console.log(`✅ Blocked label set - Showtime will detect and skip operations`);
-              } else {
-                console.log(`ℹ️ No circus labels found - Showtime not in use, skipping block`);
-              }
-            }
-
-      - name: Install Superset Showtime
-        if: steps.auth.outputs.authorized == 'true'
-        run: |
-          echo "::notice::Maintainer ${{ github.actor }} triggered deploy for PR ${{ github.event.pull_request.number || github.event.inputs.pr_number }}"
-          pip install --upgrade superset-showtime
-          showtime version
-
-      - name: Check what actions are needed
-        if: steps.auth.outputs.authorized == 'true'
-        id: check
-        env:
-          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
-          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          # Bulletproof PR number extraction
-          if [[ -n "${{ github.event.pull_request.number }}" ]]; then
-            PR_NUM="${{ github.event.pull_request.number }}"
-          elif [[ -n "${{ github.event.inputs.pr_number }}" ]]; then
-            PR_NUM="${{ github.event.inputs.pr_number }}"
-          else
-            echo "❌ No PR number found in event or inputs"
-            exit 1
-          fi
-
-          echo "Using PR number: $PR_NUM"
-
-          # Run sync check-only with optional SHA override
-          if [[ -n "${{ github.event.inputs.sha }}" ]]; then
-            OUTPUT=$(python -m showtime sync $PR_NUM --check-only --sha "${{ github.event.inputs.sha }}")
-          else
-            OUTPUT=$(python -m showtime sync $PR_NUM --check-only)
-          fi
-          echo "$OUTPUT"
-
-          # Extract the outputs we need for conditional steps
-          BUILD=$(echo "$OUTPUT" | grep "build_needed=" | cut -d'=' -f2)
-          SYNC=$(echo "$OUTPUT" | grep "sync_needed=" | cut -d'=' -f2)
-          PR_NUM_OUT=$(echo "$OUTPUT" | grep "pr_number=" | cut -d'=' -f2)
-          TARGET_SHA=$(echo "$OUTPUT" | grep "target_sha=" | cut -d'=' -f2)
-
-          echo "build_needed=$BUILD" >> $GITHUB_OUTPUT
-          echo "sync_needed=$SYNC" >> $GITHUB_OUTPUT
-          echo "pr_number=$PR_NUM_OUT" >> $GITHUB_OUTPUT
-          echo "target_sha=$TARGET_SHA" >> $GITHUB_OUTPUT
-
-      - name: Checkout PR code (only if build needed)
-        if: steps.auth.outputs.authorized == 'true' && steps.check.outputs.build_needed == 'true'
-        uses: actions/checkout@v4
-        with:
-          ref: ${{ steps.check.outputs.target_sha }}
-          persist-credentials: false
-
-      - name: Setup Docker Environment (only if build needed)
-        if: steps.auth.outputs.authorized == 'true' && steps.check.outputs.build_needed == 'true'
-        uses: ./.github/actions/setup-docker
-        with:
-          dockerhub-user: ${{ secrets.DOCKERHUB_USER }}
-          dockerhub-token: ${{ secrets.DOCKERHUB_TOKEN }}
-          build: "true"
-          install-docker-compose: "false"
-
-      - name: Execute sync (handles everything)
-        if: steps.auth.outputs.authorized == 'true' && steps.check.outputs.sync_needed == 'true'
-        env:
-          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
-          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          DOCKERHUB_USER: ${{ secrets.DOCKERHUB_USER }}
-          DOCKERHUB_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}
-        run: |
-          PR_NUM="${{ steps.check.outputs.pr_number }}"
-          TARGET_SHA="${{ steps.check.outputs.target_sha }}"
-          if [[ -n "$TARGET_SHA" ]]; then
-            python -m showtime sync $PR_NUM --sha "$TARGET_SHA"
-          else
-            python -m showtime sync $PR_NUM
-          fi

.github/workflows/superset-cli.yml

@@ -1,4 +1,4 @@
-name: Superset App CLI tests
+name: Superset CLI tests
 
 on:
   push:

.github/workflows/superset-extensions-cli.yml

@@ -1,64 +0,0 @@
-name: Superset Extensions CLI Package Tests
-
-on:
-  push:
-    branches:
-      - "master"
-      - "[0-9].[0-9]*"
-  pull_request:
-    types: [synchronize, opened, reopened, ready_for_review]
-
-# cancel previous workflow jobs for PRs
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
-  cancel-in-progress: true
-
-jobs:
-  test-superset-extensions-cli-package:
-    runs-on: ubuntu-24.04
-    strategy:
-      matrix:
-        python-version: ["previous", "current", "next"]
-    defaults:
-      run:
-        working-directory: superset-extensions-cli
-    steps:
-      - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
-        uses: actions/checkout@v4
-        with:
-          persist-credentials: false
-          submodules: recursive
-
-      - name: Check for file changes
-        id: check
-        uses: ./.github/actions/change-detector/
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Setup Python
-        if: steps.check.outputs.superset-extensions-cli
-        uses: ./.github/actions/setup-backend/
-        with:
-          python-version: ${{ matrix.python-version }}
-          requirements-type: dev
-
-      - name: Run pytest with coverage
-        if: steps.check.outputs.superset-extensions-cli
-        run: |
-          pytest --cov=superset_extensions_cli --cov-report=xml --cov-report=term-missing --cov-report=html -v --tb=short
-
-      - name: Upload coverage reports to Codecov
-        if: steps.check.outputs.superset-extensions-cli
-        uses: codecov/codecov-action@v3
-        with:
-          file: ./coverage.xml
-          flags: superset-extensions-cli
-          name: superset-extensions-cli-coverage
-          fail_ci_if_error: false
-
-      - name: Upload HTML coverage report
-        if: steps.check.outputs.superset-extensions-cli
-        uses: actions/upload-artifact@v4
-        with:
-          name: superset-extensions-cli-coverage-html
-          path: htmlcov/

.github/workflows/superset-frontend.yml

@@ -47,7 +47,7 @@ jobs:
           git show -s --format=raw HEAD
           docker buildx build \
             -t $TAG \
-            --cache-from=type=registry,ref=apache/superset-cache:3.10-slim-trixie \
+            --cache-from=type=registry,ref=apache/superset-cache:3.10-slim-bookworm \
             --target superset-node-ci \
             .
 

.github/workflows/tag-release.yml

@@ -42,7 +42,7 @@ jobs:
     runs-on: ubuntu-24.04
     strategy:
       matrix:
-        build_preset: ["dev", "lean", "py310", "websocket", "dockerize", "py311", "py312"]
+        build_preset: ["dev", "lean", "py310", "websocket", "dockerize", "py311"]
       fail-fast: false
     steps:
 

.github/workflows/welcome-new-users.yml

@@ -12,7 +12,7 @@ jobs:
 
     steps:
       - name: Welcome Message
-        uses: actions/first-interaction@v2
+        uses: actions/first-interaction@v1
         continue-on-error: true
         with:
           repo-token: ${{ github.token }}

.gitignore

@@ -43,7 +43,7 @@ _modules
 _static
 build
 app.db
-*.egg-info/
+apache_superset.egg-info/
 changelog.sh
 dist
 dump.rdb
@@ -130,7 +130,4 @@ superset/static/stats/statistics.html
 
 # LLM-related
 CLAUDE.local.md
-PROJECT.md
 .aider*
-.claude_rc*
-.env.local

.pre-commit-config.yaml

@@ -23,9 +23,7 @@ repos:
     rev: v1.15.0
     hooks:
       - id: mypy
-        name: mypy (main)
         args: [--check-untyped-defs]
-        exclude: ^superset-extensions-cli/
         additional_dependencies: [
             types-simplejson,
             types-python-dateutil,
@@ -40,10 +38,6 @@ repos:
             types-paramiko,
             types-Markdown,
           ]
-      - id: mypy
-        name: mypy (superset-extensions-cli)
-        args: [--check-untyped-defs]
-        files: ^superset-extensions-cli/
   - repo: https://github.com/pre-commit/pre-commit-hooks
     rev: v5.0.0
     hooks:
@@ -60,25 +54,25 @@ repos:
         args: ["--markdown-linebreak-ext=md"]
   - repo: local
     hooks:
-      - id: eslint-frontend
-        name: eslint (frontend)
-        entry: ./scripts/eslint.sh
-        language: system
-        pass_filenames: true
-        files: ^superset-frontend/.*\.(js|jsx|ts|tsx)$
-      - id: eslint-docs
-        name: eslint (docs)
-        entry: bash -c 'cd docs && FILES=$(echo "$@" | sed "s|docs/||g") && yarn eslint --fix --ext .js,.jsx,.ts,.tsx --quiet $FILES'
-        language: system
-        pass_filenames: true
-        files: ^docs/.*\.(js|jsx|ts|tsx)$
-      - id: type-checking-frontend
-        name: Type-Checking (Frontend)
-        entry: ./scripts/check-type.js package=superset-frontend excludeDeclarationDir=cypress-base
-        language: system
-        files: ^superset-frontend\/.*\.(js|jsx|ts|tsx)$
-        exclude: ^superset-frontend/cypress-base\/
-        require_serial: true
+    - id: eslint-frontend
+      name: eslint (frontend)
+      entry: ./scripts/eslint.sh
+      language: system
+      pass_filenames: true
+      files: ^superset-frontend/.*\.(js|jsx|ts|tsx)$
+    - id: eslint-docs
+      name: eslint (docs)
+      entry: bash -c 'cd docs && FILES=$(echo "$@" | sed "s|docs/||g") && yarn eslint --fix --ext .js,.jsx,.ts,.tsx --quiet $FILES'
+      language: system
+      pass_filenames: true
+      files: ^docs/.*\.(js|jsx|ts|tsx)$
+    - id: type-checking-frontend
+      name: Type-Checking (Frontend)
+      entry: ./scripts/check-type.js package=superset-frontend excludeDeclarationDir=cypress-base
+      language: system
+      files: ^superset-frontend\/.*\.(js|jsx|ts|tsx)$
+      exclude: ^superset-frontend/cypress-base\/
+      require_serial: true
   # blacklist unsafe functions like make_url (see #19526)
   - repo: https://github.com/skorokithakis/blacklist-pre-commit-hook
     rev: e2f070289d8eddcaec0b580d3bde29437e7c8221
@@ -100,21 +94,21 @@ repos:
         args: [--fix]
   - repo: local
     hooks:
-      - id: pylint
-        name: pylint with custom Superset plugins
-        entry: bash
-        language: system
-        types: [python]
-        exclude: ^(tests/|superset/migrations/|scripts/|RELEASING/|docker/)
-        args:
-          - -c
-          - |
-            TARGET_BRANCH=${GITHUB_BASE_REF:-master}
-            git fetch origin "$TARGET_BRANCH"
-            BASE=$(git merge-base origin/"$TARGET_BRANCH" HEAD)
-            files=$(git diff --name-only --diff-filter=ACM "$BASE"..HEAD | grep '^superset/.*\.py$' || true)
-            if [ -n "$files" ]; then
-              pylint --rcfile=.pylintrc --load-plugins=superset.extensions.pylint --reports=no $files
-            else
-              echo "No Python files to lint."
-            fi
+    - id: pylint
+      name: pylint with custom Superset plugins
+      entry: bash
+      language: system
+      types: [python]
+      exclude: ^(tests/|superset/migrations/|scripts/|RELEASING/|docker/)
+      args:
+        - -c
+        - |
+          TARGET_BRANCH=${GITHUB_BASE_REF:-master}
+          git fetch origin "$TARGET_BRANCH"
+          BASE=$(git merge-base origin/"$TARGET_BRANCH" HEAD)
+          files=$(git diff --name-only --diff-filter=ACM "$BASE"..HEAD | grep '^superset/.*\.py$' || true)
+          if [ -n "$files" ]; then
+            pylint --rcfile=.pylintrc --load-plugins=superset.extensions.pylint --reports=no $files
+          else
+            echo "No Python files to lint."
+          fi

.rat-excludes

@@ -32,8 +32,6 @@ apache_superset.egg-info
 # json and csv in general cannot have comments
 .*json
 .*csv
-# jinja templates often need to be as-is
-.*j2
 # Generated doc files
 env/*
 docs/.htaccess*
@@ -73,7 +71,6 @@ ibm-db2.svg
 postgresql.svg
 snowflake.svg
 ydb.svg
-loading.svg
 
 # docs-related
 erd.puml

CHANGELOG.md

@@ -44,8 +44,4 @@ under the License.
 - [4.0.1](./CHANGELOG/4.0.1.md)
 - [4.0.2](./CHANGELOG/4.0.2.md)
 - [4.1.0](./CHANGELOG/4.1.0.md)
-- [4.1.1](./CHANGELOG/4.1.1.md)
-- [4.1.2](./CHANGELOG/4.1.2.md)
-- [4.1.3](./CHANGELOG/4.1.3.md)
-- [4.1.4](./CHANGELOG/4.1.4.md)
 - [5.0.0](./CHANGELOG/5.0.0.md)

CHANGELOG/4.1.4.md

@@ -1,33 +0,0 @@
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
-
-  http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-## Change Log
-
-### 4.1.4 (Thu Jul 24 08:30:04 2025 -0300)
-
-**Database Migrations**
-
-**Features**
-
-**Fixes**
-- [#34289](https://github.com/apache/superset/pull/34289) fix: Saved queries list break if one query can't be parsed (@michael-s-molina)
-- [#33059](https://github.com/apache/superset/pull/33059) fix: Adds missing __init__ file to commands/logs (@michael-s-molina)
-
-**Others**
-- [#32236](https://github.com/apache/superset/pull/32236) chore(deps): bump cryptography from 43.0.3 to 44.0.1 (@dependabot[bot])

CHART_METADATA_API.md

@@ -0,0 +1,215 @@
+# Chart Metadata API Reference
+
+The Superset MCP service provides rich metadata alongside chart generation to enable better UI integration and user experiences.
+
+## Background & Design Philosophy
+
+Modern chart systems need to provide more than just visual output. Inspired by contemporary web standards and LLM integration patterns, this metadata system addresses several key needs:
+
+**Accessibility-First Design**: Following WCAG guidelines and `aria-*` attribute patterns, charts include semantic descriptions and accessibility metadata to ensure inclusive experiences.
+
+**Rich Context for AI Systems**: Similar to how platforms like social media generate rich previews (OpenGraph, Twitter Cards), charts provide semantic understanding beyond just visual representation - enabling AI agents to reason about and describe visualizations meaningfully.
+
+**Performance-Aware Integration**: Modern web APIs emphasize performance transparency (Core Web Vitals, etc.). Charts include execution metrics and optimization suggestions to help UIs make informed decisions about rendering and user feedback.
+
+**Capability-Driven UX**: Rather than requiring UIs to hardcode chart type behaviors, the system exposes what each chart can actually do - enabling dynamic, contextual interfaces that adapt to chart capabilities.
+
+## Overview
+
+When generating charts via `generate_chart`, the response includes structured metadata that helps UIs:
+- Present appropriate controls and interactions
+- Generate accessible descriptions
+- Optimize rendering performance
+- Guide user workflows
+
+## Metadata Types
+
+### ChartCapabilities
+
+Describes what interactions and features the chart supports.
+
+```python
+{
+  "supports_interaction": bool,      # User can interact (zoom, pan, hover)
+  "supports_real_time": bool,        # Chart can update with live data
+  "supports_drill_down": bool,       # Can navigate to more detailed views
+  "supports_export": bool,           # Can be exported to other formats
+  "optimal_formats": [               # Recommended preview formats
+    "url",           # Static image URL
+    "interactive",   # HTML with JavaScript controls
+    "ascii",         # Text-based representation
+    "vega_lite"      # Vega-Lite specification
+  ],
+  "data_types": [                    # Types of data visualized
+    "time_series",   # Time-based data
+    "categorical",   # Discrete categories
+    "metric"         # Numeric measurements
+  ]
+}
+```
+
+**UI Integration:**
+- Show/hide interaction controls based on `supports_interaction`
+- Enable real-time updates if `supports_real_time`
+- Display drill-down options for `supports_drill_down`
+- Choose optimal preview format from `optimal_formats`
+
+### ChartSemantics
+
+Provides semantic understanding of what the chart represents and reveals.
+
+```python
+{
+  "primary_insight": "Shows trends and changes over time",
+  "data_story": "This line chart analyzes sales, revenue over Q1-Q4",
+  "recommended_actions": [
+    "Review data patterns and trends",
+    "Consider filtering for more detail",
+    "Export chart for reporting"
+  ],
+  "anomalies": [],                   # Notable outliers (future enhancement)
+  "statistical_summary": {}         # Key statistics (future enhancement)
+}
+```
+
+**UI Integration:**
+- Display `primary_insight` as chart description
+- Use `data_story` for accessibility and tooltips
+- Show `recommended_actions` as suggested next steps
+- Highlight `anomalies` in the visualization
+
+### AccessibilityMetadata
+
+Information for creating inclusive, accessible chart experiences.
+
+```python
+{
+  "color_blind_safe": bool,          # Uses colorblind-friendly palette
+  "alt_text": "Chart showing Sales Data over time",
+  "high_contrast_available": bool    # High contrast version available
+}
+```
+
+**UI Integration:**
+- Use `alt_text` for screen readers
+- Show accessibility indicators if `color_blind_safe`
+- Offer high contrast mode if available
+
+### PerformanceMetadata
+
+Performance information for optimization and user feedback.
+
+```python
+{
+  "query_duration_ms": 1250,        # Time to generate chart data
+  "cache_status": "hit|miss|error", # Whether data came from cache
+  "optimization_suggestions": [      # Performance improvement tips
+    "Consider adding date filters to reduce data volume",
+    "Chart complexity may impact load time"
+  ]
+}
+```
+
+**UI Integration:**
+- Show loading indicators based on `query_duration_ms`
+- Display cache status for debugging
+- Present `optimization_suggestions` to users
+- Warn about slow queries
+
+## Example Response
+
+```json
+{
+  "chart": {
+    "id": 123,
+    "slice_name": "Sales Trends Q1-Q4",
+    "viz_type": "echarts_timeseries_line",
+    "url": "/explore/?slice_id=123"
+  },
+  "capabilities": {
+    "supports_interaction": true,
+    "supports_real_time": false,
+    "supports_drill_down": false,
+    "supports_export": true,
+    "optimal_formats": ["url", "interactive", "ascii"],
+    "data_types": ["time_series", "metric"]
+  },
+  "semantics": {
+    "primary_insight": "Shows trends and changes over time",
+    "data_story": "This line chart analyzes sales over Q1-Q4",
+    "recommended_actions": [
+      "Review seasonal patterns",
+      "Export for quarterly report"
+    ]
+  },
+  "accessibility": {
+    "color_blind_safe": true,
+    "alt_text": "Line chart showing sales trends from Q1 to Q4",
+    "high_contrast_available": false
+  },
+  "performance": {
+    "query_duration_ms": 450,
+    "cache_status": "miss",
+    "optimization_suggestions": []
+  }
+}
+```
+
+## Usage Examples
+
+### React Component Integration
+
+```jsx
+function ChartComponent({ chartData }) {
+  const { capabilities, semantics, accessibility, performance } = chartData;
+
+  return (
+    <div>
+      {/* Accessibility */}
+      <img
+        src={chartData.chart.url}
+        alt={accessibility.alt_text}
+        aria-describedby="chart-description"
+      />
+
+      {/* Semantic description */}
+      <p id="chart-description">{semantics.primary_insight}</p>
+
+      {/* Conditional controls based on capabilities */}
+      {capabilities.supports_interaction && (
+        <InteractiveControls />
+      )}
+
+      {capabilities.supports_export && (
+        <ExportButton />
+      )}
+
+      {/* Performance feedback */}
+      {performance.query_duration_ms > 2000 && (
+        <SlowQueryWarning suggestions={performance.optimization_suggestions} />
+      )}
+
+      {/* Recommended actions */}
+      <ActionSuggestions actions={semantics.recommended_actions} />
+    </div>
+  );
+}
+```
+
+## Chart Type Mapping
+
+Different chart types provide different capabilities:
+
+| Chart Type | Interaction | Real-time | Drill-down | Optimal Formats |
+|------------|------------|-----------|------------|-----------------|
+| `echarts_timeseries_line` | ✅ | ✅ | ❌ | url, interactive, ascii |
+| `echarts_timeseries_bar` | ✅ | ✅ | ❌ | url, interactive, ascii |
+| `table` | ❌ | ❌ | ✅ | url, table, ascii |
+| `pie` | ✅ | ❌ | ❌ | url, interactive |
+
+## Future Enhancements
+
+- **Statistical Summary**: Automatic calculation of mean, median, trends
+- **Anomaly Detection**: Identification of outliers and unusual patterns
+- **Smart Recommendations**: ML-powered suggestions for chart improvements
+- **Accessibility Scoring**: Automated accessibility compliance checking

Dockerfile

@@ -18,7 +18,7 @@
 ######################################################################
 # Node stage to deal with static asset construction
 ######################################################################
-ARG PY_VER=3.11.13-slim-trixie
+ARG PY_VER=3.11.13-slim-bookworm
 
 # If BUILDPLATFORM is null, set it to 'amd64' (or leave as is otherwise).
 ARG BUILDPLATFORM=${BUILDPLATFORM:-amd64}
@@ -29,7 +29,7 @@ ARG BUILD_TRANSLATIONS="false"
 ######################################################################
 # superset-node-ci used as a base for building frontend assets and CI
 ######################################################################
-FROM --platform=${BUILDPLATFORM} node:20-trixie-slim AS superset-node-ci
+FROM --platform=${BUILDPLATFORM} node:20-bookworm-slim AS superset-node-ci
 ARG BUILD_TRANSLATIONS
 ENV BUILD_TRANSLATIONS=${BUILD_TRANSLATIONS}
 ARG DEV_MODE="false"           # Skip frontend build in dev mode
@@ -64,7 +64,7 @@ RUN --mount=type=bind,source=./superset-frontend/package.json,target=./package.j
     --mount=type=bind,source=./superset-frontend/package-lock.json,target=./package-lock.json \
     --mount=type=cache,target=/root/.cache \
     --mount=type=cache,target=/root/.npm \
-    if [ "${DEV_MODE}" = "false" ]; then \
+    if [ "$DEV_MODE" = "false" ]; then \
         npm ci; \
     else \
         echo "Skipping 'npm ci' in dev mode"; \
@@ -80,7 +80,7 @@ FROM superset-node-ci AS superset-node
 
 # Build the frontend if not in dev mode
 RUN --mount=type=cache,target=/root/.npm \
-    if [ "${DEV_MODE}" = "false" ]; then \
+    if [ "$DEV_MODE" = "false" ]; then \
         echo "Running 'npm run ${BUILD_CMD}'"; \
         npm run ${BUILD_CMD}; \
     else \
@@ -91,10 +91,11 @@ RUN --mount=type=cache,target=/root/.npm \
 COPY superset/translations /app/superset/translations
 
 # Build translations if enabled, then cleanup localization files
-RUN if [ "${BUILD_TRANSLATIONS}" = "true" ]; then \
+RUN if [ "$BUILD_TRANSLATIONS" = "true" ]; then \
         npm run build-translation; \
     fi; \
-    rm -rf /app/superset/translations/*/*/*.[po,mo];
+    rm -rf /app/superset/translations/*/*/*.po; \
+    rm -rf /app/superset/translations/*/*/*.mo;
 
 
 ######################################################################
@@ -105,10 +106,10 @@ FROM python:${PY_VER} AS python-base
 ARG SUPERSET_HOME="/app/superset_home"
 ENV SUPERSET_HOME=${SUPERSET_HOME}
 
-RUN mkdir -p ${SUPERSET_HOME}
+RUN mkdir -p $SUPERSET_HOME
 RUN useradd --user-group -d ${SUPERSET_HOME} -m --no-log-init --shell /bin/bash superset \
-    && chmod -R 1777 ${SUPERSET_HOME} \
-    && chown -R superset:superset ${SUPERSET_HOME}
+    && chmod -R 1777 $SUPERSET_HOME \
+    && chown -R superset:superset $SUPERSET_HOME
 
 # Some bash scripts needed throughout the layers
 COPY --chmod=755 docker/*.sh /app/docker/
@@ -133,19 +134,17 @@ RUN --mount=type=cache,target=/root/.cache/uv \
     . /app/.venv/bin/activate && /app/docker/pip-install.sh --requires-build-essential -r requirements/translations.txt
 
 COPY superset/translations/ /app/translations_mo/
-RUN if [ "${BUILD_TRANSLATIONS}" = "true" ]; then \
+RUN if [ "$BUILD_TRANSLATIONS" = "true" ]; then \
         pybabel compile -d /app/translations_mo | true; \
     fi; \
-    rm -f /app/translations_mo/*/*/*.[po,json]
+    rm -f /app/translations_mo/*/*/*.po; \
+    rm -f /app/translations_mo/*/*/*.json;
 
 ######################################################################
 # Python APP common layer
 ######################################################################
 FROM python-base AS python-common
 
-# Build arg to pre-populate examples DuckDB file
-ARG LOAD_EXAMPLES_DUCKDB="false"
-
 ENV SUPERSET_HOME="/app/superset_home" \
     HOME="/app/superset_home" \
     SUPERSET_ENV="production" \
@@ -171,11 +170,11 @@ RUN mkdir -p \
 ARG INCLUDE_CHROMIUM="false"
 ARG INCLUDE_FIREFOX="false"
 RUN --mount=type=cache,target=${SUPERSET_HOME}/.cache/uv \
-    if [ "${INCLUDE_CHROMIUM}" = "true" ] || [ "${INCLUDE_FIREFOX}" = "true" ]; then \
+    if [ "$INCLUDE_CHROMIUM" = "true" ] || [ "$INCLUDE_FIREFOX" = "true" ]; then \
         uv pip install playwright && \
         playwright install-deps && \
-        if [ "${INCLUDE_CHROMIUM}" = "true" ]; then playwright install chromium; fi && \
-        if [ "${INCLUDE_FIREFOX}" = "true" ]; then playwright install firefox; fi; \
+        if [ "$INCLUDE_CHROMIUM" = "true" ]; then playwright install chromium; fi && \
+        if [ "$INCLUDE_FIREFOX" = "true" ]; then playwright install firefox; fi; \
     else \
         echo "Skipping browser installation"; \
     fi
@@ -197,18 +196,6 @@ RUN /app/docker/apt-install.sh \
       libecpg-dev \
       libldap2-dev
 
-# Pre-load examples DuckDB file if requested
-RUN if [ "$LOAD_EXAMPLES_DUCKDB" = "true" ]; then \
-        mkdir -p /app/data && \
-        echo "Downloading pre-built examples.duckdb..." && \
-        curl -L -o /app/data/examples.duckdb \
-            "https://raw.githubusercontent.com/apache-superset/examples-data/master/examples.duckdb" && \
-        chown -R superset:superset /app/data; \
-    else \
-        mkdir -p /app/data && \
-        chown -R superset:superset /app/data; \
-    fi
-
 # Copy compiled things from previous stages
 COPY --from=superset-node /app/superset/static/assets superset/static/assets
 
@@ -232,10 +219,6 @@ FROM python-common AS lean
 
 # Install Python dependencies using docker/pip-install.sh
 COPY requirements/base.txt requirements/
-
-# Copy superset-core package needed for editable install in base.txt
-COPY superset-core superset-core
-
 RUN --mount=type=cache,target=${SUPERSET_HOME}/.cache/uv \
     /app/docker/pip-install.sh --requires-build-essential -r requirements/base.txt
 # Install the superset package
@@ -258,11 +241,6 @@ RUN /app/docker/apt-install.sh \
 
 # Copy development requirements and install them
 COPY requirements/*.txt requirements/
-
-# Copy local packages needed for editable installs in development.txt
-COPY superset-core superset-core
-COPY superset-extensions-cli superset-extensions-cli
-
 # Install Python dependencies using docker/pip-install.sh
 RUN --mount=type=cache,target=${SUPERSET_HOME}/.cache/uv \
     /app/docker/pip-install.sh --requires-build-essential -r requirements/development.txt
@@ -280,15 +258,6 @@ USER superset
 ######################################################################
 FROM lean AS ci
 USER root
-RUN uv pip install .[postgres,duckdb]
-USER superset
-CMD ["/app/docker/entrypoints/docker-ci.sh"]
-
-######################################################################
-# Showtime image - lean + DuckDB for examples database
-######################################################################
-FROM lean AS showtime
-USER root
-RUN uv pip install .[duckdb]
+RUN uv pip install .[postgres]
 USER superset
 CMD ["/app/docker/entrypoints/docker-ci.sh"]

LLMS.md

@@ -9,16 +9,13 @@ Apache Superset is a data visualization platform with Flask/Python backend and R
 ### Frontend Modernization
 - **NO `any` types** - Use proper TypeScript types
 - **NO JavaScript files** - Convert to TypeScript (.ts/.tsx)
-- **Use @superset-ui/core** - Don't import Ant Design directly, prefer Ant Design component wrappers from @superset-ui/core/components
-- **Use antd theming tokens** - Prefer antd tokens over legacy theming tokens
-- **Avoid custom css and styles** - Follow antd best practices and avoid styling and custom CSS whenever possible
+- **Use @superset-ui/core** - Don't import Ant Design directly
 
 ### Testing Strategy Migration
 - **Prefer unit tests** over integration tests
 - **Prefer integration tests** over Cypress end-to-end tests
 - **Cypress is last resort** - Actively moving away from Cypress
 - **Use Jest + React Testing Library** for component testing
-- **Use `test()` instead of `describe()`** - Follow [avoid nesting when testing](https://kentcdodds.com/blog/avoid-nesting-when-youre-testing) principles
 
 ### Backend Type Safety
 - **Add type hints** - All new Python code needs proper typing
@@ -183,6 +180,7 @@ pre-commit run eslint            # Frontend linting
 
 ## Platform-Specific Instructions
 
+- **[LLMS.md](LLMS.md)** - General LLM development guide (READ THIS FIRST)
 - **[CLAUDE.md](CLAUDE.md)** - For Claude/Anthropic tools
 - **[.github/copilot-instructions.md](.github/copilot-instructions.md)** - For GitHub Copilot  
 - **[GEMINI.md](GEMINI.md)** - For Google Gemini tools

Makefile

@@ -91,7 +91,7 @@ js-format:
 	cd superset-frontend; npm run prettier
 
 flask-app:
-	flask run -p 8088 --reload --debugger
+	flask run -p 8088 --with-threads --reload --debugger
 
 node-app:
 	cd superset-frontend; npm run dev-server

RELEASING/Dockerfile.from_local_tarball

@@ -14,7 +14,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 #
-FROM python:3.10-slim-trixie
+FROM python:3.10-slim-bookworm
 
 RUN useradd --user-group --create-home --no-log-init --shell /bin/bash superset
 

RELEASING/Dockerfile.from_svn_tarball

@@ -14,7 +14,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 #
-FROM python:3.10-slim-trixie
+FROM python:3.10-slim-bookworm
 
 RUN useradd --user-group --create-home --no-log-init --shell /bin/bash superset
 

RELEASING/Dockerfile.make_docs

@@ -14,7 +14,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 #
-FROM python:3.10-slim-trixie
+FROM python:3.10-slim-bookworm
 ARG VERSION
 
 RUN git clone --depth 1 --branch ${VERSION} https://github.com/apache/superset.git /superset

RELEASING/Dockerfile.make_tarball

@@ -14,7 +14,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 #
-FROM python:3.10-slim-trixie
+FROM python:3.10-slim-bookworm
 
 RUN apt-get update -y
 RUN apt-get install -y \

RELEASING/README.md

@@ -469,10 +469,6 @@ an account first if you don't have one, and reference your username
 while requesting access to push packages.
 
 ```bash
-# Run this first to make sure you are uploading the right version.
-# Pypi does not allow you to delete or retract once uplaoded.
-twine check dist/*
-
 twine upload dist/*
 ```
 
@@ -522,8 +518,6 @@ takes the version (ie `3.1.1`), the git reference (any SHA, tag or branch
 reference), and whether to force the `latest` Docker tag on the
 generated images.
 
-**NOTE:** If the docker image isn't built, you'll need to run this [GH action](https://github.com/apache/superset/actions/workflows/tag-release.yml) where you provide it the tag sha.
-
 ### Npm Release
 
 You might want to publish the latest @superset-ui release to npm

RELEASING/make_tarball.sh

@@ -32,10 +32,11 @@ else
   SUPERSET_VERSION="${1}"
   SUPERSET_RC="${2}"
   SUPERSET_PGP_FULLNAME="${3}"
-  SUPERSET_VERSION_RC="${SUPERSET_VERSION}rc${SUPERSET_RC}"
   SUPERSET_RELEASE_RC_TARBALL="apache_superset-${SUPERSET_VERSION_RC}-source.tar.gz"
 fi
 
+SUPERSET_VERSION_RC="${SUPERSET_VERSION}rc${SUPERSET_RC}"
+
 if [ -z "${SUPERSET_SVN_DEV_PATH}" ]; then
   SUPERSET_SVN_DEV_PATH="$HOME/svn/superset_dev"
 fi

RESOURCES/FEATURE_FLAGS.md

@@ -28,7 +28,6 @@ These features are considered **unfinished** and should only be used on developm
 [//]: # "PLEASE KEEP THE LIST SORTED ALPHABETICALLY"
 
 - ALERT_REPORT_TABS
-- DATE_RANGE_TIMESHIFTS_ENABLED
 - ENABLE_ADVANCED_DATA_TYPES
 - PRESTO_EXPAND_DATA
 - SHARE_QUERIES_VIA_KV_STORE

RESOURCES/STANDARD_ROLES.md

@@ -94,9 +94,9 @@ under the License.
 | can available domains on Superset                |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|O|
 | can request access on Superset                   |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|O|
 | can dashboard on Superset                        |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|O|
-| can post on TableSchemaView                      |:heavy_check_mark:|O|O|:heavy_check_mark:|
-| can expanded on TableSchemaView                  |:heavy_check_mark:|O|O|:heavy_check_mark:|
-| can delete on TableSchemaView                    |:heavy_check_mark:|O|O|:heavy_check_mark:|
+| can post on TableSchemaView                      |:heavy_check_mark:|:heavy_check_mark:|O|O|
+| can expanded on TableSchemaView                  |:heavy_check_mark:|:heavy_check_mark:|O|O|
+| can delete on TableSchemaView                    |:heavy_check_mark:|:heavy_check_mark:|O|O|
 | can get on TabStateView                          |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|
 | can post on TabStateView                         |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|
 | can delete query on TabStateView                 |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|

UPDATING.md

@@ -23,15 +23,6 @@ This file documents any backwards-incompatible changes in Superset and
 assists people when migrating to a new version.
 
 ## Next
-- [34871](https://github.com/apache/superset/pull/34871): Fixed Jest test hanging issue from Ant Design v5 upgrade. MessageChannel is now mocked in test environment to prevent rc-overflow from causing Jest to hang. Test environment only - no production impact.
-- [34782](https://github.com/apache/superset/pull/34782): Dataset exports now include the dataset ID in their file name (similar to charts and dashboards). If managing assets as code, make sure to rename existing dataset YAMLs to include the ID (and avoid duplicated files).
-- [34536](https://github.com/apache/superset/pull/34536): The `ENVIRONMENT_TAG_CONFIG` color values have changed to support only Ant Design semantic colors. Update your `superset_config.py`:
-  - Change `"error.base"` to just `"error"` after this PR
-  - Change any hex color values to one of: `"success"`, `"processing"`, `"error"`, `"warning"`, `"default"`
-  - Custom colors are no longer supported to maintain consistency with Ant Design components
-- [34561](https://github.com/apache/superset/pull/34561) Added tiled screenshot functionality for Playwright-based reports to handle large dashboards more efficiently. When enabled (default: `SCREENSHOT_TILED_ENABLED = True`), dashboards with 20+ charts or height exceeding 5000px will be captured using multiple viewport-sized tiles and combined into a single image. This improves report generation performance and reliability for large dashboards.
-Note: Pillow is now a required dependency (previously optional) to support image processing for tiled screenshots.
-`thumbnails` optional dependency is now deprecated and will be removed in the next major release (7.0).
 - [33084](https://github.com/apache/superset/pull/33084) The DISALLOWED_SQL_FUNCTIONS configuration now includes additional potentially sensitive database functions across PostgreSQL, MySQL, SQLite, MS SQL Server, and ClickHouse. Existing queries using these functions may now be blocked. Review your SQL Lab queries and dashboards if you encounter "disallowed function" errors after upgrading
 - [34235](https://github.com/apache/superset/pull/34235) CSV exports now use `utf-8-sig` encoding by default to include a UTF-8 BOM, improving compatibility with Excel.
 - [34258](https://github.com/apache/superset/pull/34258) changing the default in Dockerfile to INCLUDE_CHROMIUM="false" (from "true") in the past. This ensures the `lean` layer is lean by default, and people can opt-in to the `chromium` layer by setting the build arg `INCLUDE_CHROMIUM=true`. This is a breaking change for anyone using the `lean` layer, as it will no longer include Chromium by default.
@@ -41,7 +32,6 @@ Note: Pillow is now a required dependency (previously optional) to support image
 - [32317](https://github.com/apache/superset/pull/32317) The horizontal filter bar feature is now out of testing/beta development and its feature flag `HORIZONTAL_FILTER_BAR` has been removed.
 - [31590](https://github.com/apache/superset/pull/31590) Marks the begining of intricate work around supporting dynamic Theming, and breaks support for [THEME_OVERRIDES](https://github.com/apache/superset/blob/732de4ac7fae88e29b7f123b6cbb2d7cd411b0e4/superset/config.py#L671) in favor of a new theming system based on AntD V5. Likely this will be in disrepair until settling over the 5.x lifecycle.
 - [32432](https://github.com/apache/superset/pull/31260) Moves the List Roles FAB view to the frontend and requires `FAB_ADD_SECURITY_API` to be enabled in the configuration and `superset init` to be executed.
-- [34319](https://github.com/apache/superset/pull/34319) Drill to Detail and Drill By is now supported in Embedded mode, and also with the `DASHBOARD_RBAC` FF. If you don't want to expose these features in Embedded / `DASHBOARD_RBAC`, make sure the roles used for Embedded / `DASHBOARD_RBAC`don't have the required permissions to perform D2D actions.
 
 ## 5.0.0
 

docker-compose-light.yml

@@ -17,47 +17,22 @@
 
 # -----------------------------------------------------------------------
 # Lightweight docker-compose for running multiple Superset instances
-# This includes only essential services: database and Superset app (no Redis)
+# This includes only essential services: database, Redis, and Superset app
 #
-# RUNNING SUPERSET:
-# 1. Start services: docker-compose -f docker-compose-light.yml up
-# 2. Access at: http://localhost:9001 (or NODE_PORT if specified)
-#
-# RUNNING MULTIPLE INSTANCES:
+# IMPORTANT: To run multiple instances in parallel:
 # - Use different project names: docker-compose -p project1 -f docker-compose-light.yml up
 # - Use different NODE_PORT values: NODE_PORT=9002 docker-compose -p project2 -f docker-compose-light.yml up
 # - Volumes are isolated by project name (e.g., project1_db_home_light, project2_db_home_light)
 # - Database name is intentionally different (superset_light) to prevent accidental cross-connections
 #
-# RUNNING TESTS WITH PYTEST:
-# Tests run in an isolated environment with a separate test database.
-# The pytest-runner service automatically creates and initializes the test database on first use.
+# MCP Service (Model Context Protocol):
+# - Optional service for LLM agent integration, available under 'mcp' profile
+# - To include MCP: docker-compose -f docker-compose-light.yml --profile mcp up
+# - MCP runs on port 5008 by default (customize with MCP_PORT=5009)
+# - Enable SQL debugging with MCP_SQL_DEBUG=true
 #
-# Basic usage:
-#   docker-compose -f docker-compose-light.yml run --rm pytest-runner pytest tests/unit_tests/
-#
-# Run specific test file:
-#   docker-compose -f docker-compose-light.yml run --rm pytest-runner pytest tests/unit_tests/test_foo.py
-#
-# Run with pytest options:
-#   docker-compose -f docker-compose-light.yml run --rm pytest-runner pytest -v -s -x tests/
-#
-# Force reload test database and run tests (when tests are failing due to bad state):
-#   docker-compose -f docker-compose-light.yml run --rm -e FORCE_RELOAD=true pytest-runner pytest tests/
-#
-# Run any command in test environment:
-#   docker-compose -f docker-compose-light.yml run --rm pytest-runner bash
-#   docker-compose -f docker-compose-light.yml run --rm pytest-runner pytest --collect-only
-#
-# For parallel test execution with different projects:
-#   docker-compose -p project1 -f docker-compose-light.yml run --rm pytest-runner pytest tests/
-#
-# DEVELOPMENT TIPS:
-# - First test run takes ~20-30 seconds (database creation + initialization)
-# - Subsequent runs are fast (~2-3 seconds startup)
-# - Use FORCE_RELOAD=true when you need a clean test database
-# - Tests use SimpleCache instead of Redis (no Redis required)
-# - Set SUPERSET_LOG_LEVEL=debug in docker/.env-local for detailed logs
+# For verbose logging during development:
+# - Set SUPERSET_LOG_LEVEL=debug in docker/.env-local for detailed Superset logs
 # -----------------------------------------------------------------------
 x-superset-user: &superset-user root
 x-superset-volumes: &superset-volumes
@@ -71,13 +46,12 @@ x-common-build: &common-build
   context: .
   target: ${SUPERSET_BUILD_TARGET:-dev} # can use `dev` (default) or `lean`
   cache_from:
-    - apache/superset-cache:3.10-slim-trixie
+    - apache/superset-cache:3.10-slim-bookworm
   args:
     DEV_MODE: "true"
     INCLUDE_CHROMIUM: ${INCLUDE_CHROMIUM:-false}
     INCLUDE_FIREFOX: ${INCLUDE_FIREFOX:-false}
     BUILD_TRANSLATIONS: ${BUILD_TRANSLATIONS:-false}
-    LOAD_EXAMPLES_DUCKDB: ${LOAD_EXAMPLES_DUCKDB:-true}
 
 services:
   db-light:
@@ -88,12 +62,13 @@ services:
         required: false
     image: postgres:16
     restart: unless-stopped
+    # No host port mapping - only accessible within Docker network
     volumes:
       - db_home_light:/var/lib/postgresql/data
       - ./docker/docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d
     environment:
+      # Override database name to avoid conflicts
       POSTGRES_DB: superset_light
-    command: postgres -c max_connections=200
 
   superset-light:
     env_file:
@@ -105,6 +80,7 @@ services:
       <<: *common-build
     command: ["/app/docker/docker-bootstrap.sh", "app"]
     restart: unless-stopped
+    # No host port mapping - accessed via webpack dev server proxy
     extra_hosts:
       - "host.docker.internal:host-gateway"
     user: *superset-user
@@ -113,13 +89,16 @@ services:
         condition: service_completed_successfully
     volumes: *superset-volumes
     environment:
+      # Override DB connection for light service
       DATABASE_HOST: db-light
       DATABASE_DB: superset_light
       POSTGRES_DB: superset_light
-      SUPERSET__SQLALCHEMY_EXAMPLES_URI: "duckdb:////app/data/examples.duckdb"
+      EXAMPLES_HOST: db-light
+      EXAMPLES_DB: superset_light
+      EXAMPLES_USER: superset
+      EXAMPLES_PASSWORD: superset
+      # Use light-specific config that disables Redis
       SUPERSET_CONFIG_PATH: /app/docker/pythonpath_dev/superset_config_docker_light.py
-      GITHUB_HEAD_REF: ${GITHUB_HEAD_REF:-}
-      GITHUB_SHA: ${GITHUB_SHA:-}
 
   superset-init-light:
     build:
@@ -130,16 +109,21 @@ services:
         required: true
       - path: docker/.env-local # optional override
         required: false
-    user: *superset-user
     depends_on:
       db-light:
         condition: service_started
+    user: *superset-user
     volumes: *superset-volumes
     environment:
+      # Override DB connection for light service
       DATABASE_HOST: db-light
       DATABASE_DB: superset_light
       POSTGRES_DB: superset_light
-      SUPERSET__SQLALCHEMY_EXAMPLES_URI: "duckdb:////app/data/examples.duckdb"
+      EXAMPLES_HOST: db-light
+      EXAMPLES_DB: superset_light
+      EXAMPLES_USER: superset
+      EXAMPLES_PASSWORD: superset
+      # Use light-specific config that disables Redis
       SUPERSET_CONFIG_PATH: /app/docker/pythonpath_dev/superset_config_docker_light.py
     healthcheck:
       disable: true
@@ -172,30 +156,36 @@ services:
         required: false
     volumes: *superset-volumes
 
-  pytest-runner:
+  superset-mcp-light:
+    profiles:
+      - mcp
     build:
       <<: *common-build
-    entrypoint: ["/app/docker/docker-pytest-entrypoint.sh"]
+    command: ["/app/docker/docker-bootstrap.sh", "mcp"]
+    restart: unless-stopped
+    ports:
+      - "127.0.0.1:${MCP_PORT:-5008}:5008"  # Parameterized port
+    extra_hosts:
+      - "host.docker.internal:host-gateway"
+    user: *superset-user
+    depends_on:
+      superset-init-light:
+        condition: service_completed_successfully
+    volumes: *superset-volumes
     env_file:
       - path: docker/.env # default
         required: true
       - path: docker/.env-local # optional override
         required: false
-    profiles:
-      - test  # Only starts when --profile test is used
-    depends_on:
-      db-light:
-        condition: service_started
-    user: *superset-user
-    volumes: *superset-volumes
     environment:
+      # Override DB connection for light service
       DATABASE_HOST: db-light
-      DATABASE_DB: test
-      POSTGRES_DB: test
-      SUPERSET__SQLALCHEMY_DATABASE_URI: postgresql+psycopg2://superset:superset@db-light:5432/test
-      SUPERSET__SQLALCHEMY_EXAMPLES_URI: "duckdb:////app/data/examples.duckdb"
-      SUPERSET_CONFIG: superset_test_config_light
-      PYTHONPATH: /app/pythonpath:/app/docker/pythonpath_dev:/app
+      DATABASE_DB: superset_light
+      POSTGRES_DB: superset_light
+      # Use light-specific config that disables Redis
+      SUPERSET_CONFIG_PATH: /app/docker/pythonpath_dev/superset_config_docker_light.py
+      # Enable SQL debugging for MCP if needed
+      SQLALCHEMY_DEBUG: ${MCP_SQL_DEBUG:-false}
 
 volumes:
   superset_home_light:

docker-compose-non-dev.yml

@@ -33,7 +33,7 @@ x-common-build: &common-build
   context: .
   target: dev
   cache_from:
-    - apache/superset-cache:3.10-slim-trixie
+    - apache/superset-cache:3.10-slim-bookworm
 
 services:
   redis:

docker-compose.yml

@@ -36,13 +36,12 @@ x-common-build: &common-build
   context: .
   target: ${SUPERSET_BUILD_TARGET:-dev} # can use `dev` (default) or `lean`
   cache_from:
-    - apache/superset-cache:3.10-slim-trixie
+    - apache/superset-cache:3.10-slim-bookworm
   args:
     DEV_MODE: "true"
     INCLUDE_CHROMIUM: ${INCLUDE_CHROMIUM:-false}
     INCLUDE_FIREFOX: ${INCLUDE_FIREFOX:-false}
     BUILD_TRANSLATIONS: ${BUILD_TRANSLATIONS:-false}
-    LOAD_EXAMPLES_DUCKDB: ${LOAD_EXAMPLES_DUCKDB:-true}
 
 services:
   nginx:
@@ -108,8 +107,6 @@ services:
       superset-init:
         condition: service_completed_successfully
     volumes: *superset-volumes
-    environment:
-      SUPERSET__SQLALCHEMY_EXAMPLES_URI: "duckdb:////app/data/examples.duckdb"
 
   superset-websocket:
     container_name: superset_websocket
@@ -161,8 +158,6 @@ services:
         condition: service_started
     user: *superset-user
     volumes: *superset-volumes
-    environment:
-      SUPERSET__SQLALCHEMY_EXAMPLES_URI: "duckdb:////app/data/examples.duckdb"
     healthcheck:
       disable: true
 

docker/apt-install.sh

@@ -18,7 +18,7 @@
 set -euo pipefail
 
 # Ensure this script is run as root
-if [[ ${EUID} -ne 0 ]]; then
+if [[ $EUID -ne 0 ]]; then
   echo "This script must be run as root" >&2
   exit 1
 fi
@@ -42,7 +42,7 @@ echo -e "${GREEN}Installing packages: $@${RESET}"
 apt-get install -yqq --no-install-recommends "$@"
 
 echo -e "${GREEN}Autoremoving unnecessary packages...${RESET}"
-apt-get autoremove -yqq --purge
+apt-get autoremove -y
 
 echo -e "${GREEN}Cleaning up package cache and metadata...${RESET}"
 apt-get clean

docker/docker-bootstrap.sh

@@ -72,12 +72,16 @@ case "${1}" in
     ;;
   app)
     echo "Starting web app (using development server)..."
-    flask run -p $PORT --reload --debugger --without-threads --host=0.0.0.0
+    flask run -p $PORT --with-threads --reload --debugger --host=0.0.0.0
     ;;
   app-gunicorn)
     echo "Starting web app..."
     /usr/bin/run-server.sh
     ;;
+  mcp)
+    echo "Starting MCP service..."
+    superset mcp run --host 0.0.0.0 --port ${MCP_PORT:-5008} --debug
+    ;;
   *)
     echo "Unknown Operation!!!"
     ;;

docker/docker-init.sh

@@ -69,8 +69,6 @@ echo_step "3" "Complete" "Setting up roles and perms"
 if [ "$SUPERSET_LOAD_EXAMPLES" = "yes" ]; then
     # Load some data to play with
     echo_step "4" "Starting" "Loading examples"
-
-
     # If Cypress run which consumes superset_test_config – load required data for tests
     if [ "$CYPRESS_CONFIG" == "true" ]; then
         superset load_examples --load-test-data

docker/docker-pytest-entrypoint.sh

@@ -1,152 +0,0 @@
-#!/bin/bash
-#
-# Licensed to the Apache Software Foundation (ASF) under one or more
-# contributor license agreements.  See the NOTICE file distributed with
-# this work for additional information regarding copyright ownership.
-# The ASF licenses this file to You under the Apache License, Version 2.0
-# (the "License"); you may not use this file except in compliance with
-# the License.  You may obtain a copy of the License at
-#
-#    http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-
-set -e
-
-# Wait for PostgreSQL to be ready
-echo "Waiting for database to be ready..."
-for i in {1..30}; do
-  if python3 -c "
-import psycopg2
-try:
-    conn = psycopg2.connect(host='db-light', user='superset', password='superset', database='superset_light')
-    conn.close()
-    print('Database is ready!')
-except:
-    exit(1)
-" 2>/dev/null; then
-    echo "Database connection established!"
-    break
-  fi
-  echo "Waiting for database... ($i/30)"
-  if [ $i -eq 30 ]; then
-    echo "Database connection timeout after 30 seconds"
-    exit 1
-  fi
-  sleep 1
-done
-
-# Handle database setup based on FORCE_RELOAD
-if [ "${FORCE_RELOAD}" = "true" ]; then
-  echo "Force reload requested - resetting test database"
-  # Drop and recreate the test database using Python
-  python3 -c "
-import psycopg2
-from psycopg2.extensions import ISOLATION_LEVEL_AUTOCOMMIT
-
-# Connect to default database
-conn = psycopg2.connect(host='db-light', user='superset', password='superset', database='superset_light')
-conn.set_isolation_level(ISOLATION_LEVEL_AUTOCOMMIT)
-cur = conn.cursor()
-
-# Drop and recreate test database
-try:
-    cur.execute('DROP DATABASE IF EXISTS test')
-except:
-    pass
-
-cur.execute('CREATE DATABASE test')
-conn.close()
-
-# Connect to test database to create schemas
-conn = psycopg2.connect(host='db-light', user='superset', password='superset', database='test')
-conn.set_isolation_level(ISOLATION_LEVEL_AUTOCOMMIT)
-cur = conn.cursor()
-
-cur.execute('CREATE SCHEMA sqllab_test_db')
-cur.execute('CREATE SCHEMA admin_database')
-
-cur.close()
-conn.close()
-print('Test database reset successfully')
-"
-  # Use --no-reset-db since we already reset it
-  FLAGS="--no-reset-db"
-else
-  echo "Using existing test database (set FORCE_RELOAD=true to reset)"
-  FLAGS="--no-reset-db"
-
-  # Ensure test database exists using Python
-  python3 -c "
-import psycopg2
-from psycopg2.extensions import ISOLATION_LEVEL_AUTOCOMMIT
-
-# Check if test database exists
-try:
-    conn = psycopg2.connect(host='db-light', user='superset', password='superset', database='test')
-    conn.close()
-    print('Test database already exists')
-except:
-    print('Creating test database...')
-    # Connect to default database to create test database
-    conn = psycopg2.connect(host='db-light', user='superset', password='superset', database='superset_light')
-    conn.set_isolation_level(ISOLATION_LEVEL_AUTOCOMMIT)
-    cur = conn.cursor()
-
-    # Create test database
-    cur.execute('CREATE DATABASE test')
-    conn.close()
-
-    # Connect to test database to create schemas
-    conn = psycopg2.connect(host='db-light', user='superset', password='superset', database='test')
-    conn.set_isolation_level(ISOLATION_LEVEL_AUTOCOMMIT)
-    cur = conn.cursor()
-
-    cur.execute('CREATE SCHEMA IF NOT EXISTS sqllab_test_db')
-    cur.execute('CREATE SCHEMA IF NOT EXISTS admin_database')
-
-    cur.close()
-    conn.close()
-    print('Test database created successfully')
-"
-fi
-
-# Always run database migrations to ensure schema is up to date
-echo "Running database migrations..."
-cd /app
-superset db upgrade
-
-# Initialize test environment if needed
-if [ "${FORCE_RELOAD}" = "true" ] || [ ! -f "/app/superset_home/.test_initialized" ]; then
-  echo "Initializing test environment..."
-  # Run initialization commands
-  superset init
-  echo "Loading test users..."
-  superset load-test-users
-
-  # Mark as initialized
-  touch /app/superset_home/.test_initialized
-else
-  echo "Test environment already initialized (skipping init and load-test-users)"
-  echo "Tip: Use FORCE_RELOAD=true to reinitialize the test database"
-fi
-
-# Create missing scripts needed for tests
-if [ ! -f "/app/scripts/tag_latest_release.sh" ]; then
-  echo "Creating missing tag_latest_release.sh script for tests..."
-  cp /app/docker/tag_latest_release.sh /app/scripts/tag_latest_release.sh 2>/dev/null || true
-fi
-
-# Install pip module for Shillelagh compatibility (aligns with CI environment)
-echo "Installing pip module for Shillelagh compatibility..."
-uv pip install pip
-
-# If arguments provided, execute them
-if [ $# -gt 0 ]; then
-  exec "$@"
-fi

docker/entrypoints/run-server.sh

@@ -26,7 +26,7 @@ gunicorn \
     --workers ${SERVER_WORKER_AMOUNT:-1} \
     --worker-class ${SERVER_WORKER_CLASS:-gthread} \
     --threads ${SERVER_THREADS_AMOUNT:-20} \
-    --log-level "${GUNICORN_LOGLEVEL:-info}" \
+    --log-level "${GUNICORN_LOGLEVEL:info}" \
     --timeout ${GUNICORN_TIMEOUT:-60} \
     --keep-alive ${GUNICORN_KEEPALIVE:-2} \
     --max-requests ${WORKER_MAX_REQUESTS:-0} \

docker/frontend-mem-nag.sh

@@ -23,57 +23,25 @@ MIN_MEM_FREE_GB=3
 MIN_MEM_FREE_KB=$(($MIN_MEM_FREE_GB*1000000))
 
 echo_mem_warn() {
-  # Check if running in Codespaces first
-  if [[ -n "${CODESPACES}" ]]; then
-    echo "Memory available: Codespaces managed"
-    return
-  fi
+  MEM_FREE_KB=$(awk '/MemFree/ { printf "%s \n", $2 }' /proc/meminfo)
+  MEM_FREE_GB=$(awk '/MemFree/ { printf "%s \n", $2/1024/1024 }' /proc/meminfo)
 
-  # Check platform and get memory accordingly
-  if [[ -f /proc/meminfo ]]; then
-    # Linux
-    if grep -q MemAvailable /proc/meminfo; then
-      MEM_AVAIL_KB=$(awk '/MemAvailable/ { printf "%s \n", $2 }' /proc/meminfo)
-      MEM_AVAIL_GB=$(awk '/MemAvailable/ { printf "%s \n", $2/1024/1024 }' /proc/meminfo)
-    else
-      MEM_AVAIL_KB=$(awk '/MemFree/ { printf "%s \n", $2 }' /proc/meminfo)
-      MEM_AVAIL_GB=$(awk '/MemFree/ { printf "%s \n", $2/1024/1024 }' /proc/meminfo)
-    fi
-  elif [[ "$(uname)" == "Darwin" ]]; then
-    # macOS - use vm_stat to get free memory
-    # vm_stat reports in pages, typically 4096 bytes per page
-    PAGE_SIZE=$(pagesize)
-    FREE_PAGES=$(vm_stat | awk '/Pages free:/ {print $3}' | tr -d '.')
-    INACTIVE_PAGES=$(vm_stat | awk '/Pages inactive:/ {print $3}' | tr -d '.')
-    # Free + inactive pages give us available memory (similar to MemAvailable on Linux)
-    AVAIL_PAGES=$((FREE_PAGES + INACTIVE_PAGES))
-    MEM_AVAIL_KB=$((AVAIL_PAGES * PAGE_SIZE / 1024))
-    MEM_AVAIL_GB=$(echo "scale=2; $MEM_AVAIL_KB / 1024 / 1024" | bc)
-  else
-    # Other platforms
-    echo "Memory available: Unable to determine"
-    return
-  fi
-
-  if [[ "${MEM_AVAIL_KB}" -lt "${MIN_MEM_FREE_KB}" ]]; then
+  if [[ "${MEM_FREE_KB}" -lt "${MIN_MEM_FREE_KB}" ]]; then
     cat <<EOF
     ===============================================
     ========  Memory Insufficient Warning =========
     ===============================================
 
-    It looks like you only have ${MEM_AVAIL_GB}GB of
-    memory ${MEM_TYPE}. Please increase your Docker
+    It looks like you only have ${MEM_FREE_GB}GB of
+    memory free. Please increase your Docker
     resources to at least ${MIN_MEM_FREE_GB}GB
 
-    Note: During builds, available memory may be
-    temporarily low due to caching and compilation.
-
     ===============================================
     ========  Memory Insufficient Warning =========
     ===============================================
 EOF
   else
-    echo "Memory available: ${MEM_AVAIL_GB} GB"
+    echo "Memory check Ok [${MEM_FREE_GB}GB free]"
   fi
 }
 

docker/pip-install.sh

@@ -38,14 +38,14 @@ for arg in "$@"; do
 done
 
 # Install build-essential if required
-if ${REQUIRES_BUILD_ESSENTIAL}; then
+if $REQUIRES_BUILD_ESSENTIAL; then
   echo "Installing build-essential for package builds..."
   apt-get update -qq \
     && apt-get install -yqq --no-install-recommends build-essential
 fi
 
 # Choose whether to use pip cache
-if ${USE_CACHE}; then
+if $USE_CACHE; then
   echo "Using pip cache..."
   uv pip install "${ARGS[@]}"
 else
@@ -54,7 +54,7 @@ else
 fi
 
 # Remove build-essential if it was installed
-if ${REQUIRES_BUILD_ESSENTIAL}; then
+if $REQUIRES_BUILD_ESSENTIAL; then
   echo "Removing build-essential to keep the image lean..."
   apt-get autoremove -yqq --purge build-essential \
     && apt-get clean \

docker/pythonpath_dev/superset_config.py

@@ -49,18 +49,12 @@ SQLALCHEMY_DATABASE_URI = (
     f"{DATABASE_HOST}:{DATABASE_PORT}/{DATABASE_DB}"
 )
 
-# Use environment variable if set, otherwise construct from components
-# This MUST take precedence over any other configuration
-SQLALCHEMY_EXAMPLES_URI = os.getenv(
-    "SUPERSET__SQLALCHEMY_EXAMPLES_URI",
-    (
-        f"{DATABASE_DIALECT}://"
-        f"{EXAMPLES_USER}:{EXAMPLES_PASSWORD}@"
-        f"{EXAMPLES_HOST}:{EXAMPLES_PORT}/{EXAMPLES_DB}"
-    ),
+SQLALCHEMY_EXAMPLES_URI = (
+    f"{DATABASE_DIALECT}://"
+    f"{EXAMPLES_USER}:{EXAMPLES_PASSWORD}@"
+    f"{EXAMPLES_HOST}:{EXAMPLES_PORT}/{EXAMPLES_DB}"
 )
 
-
 REDIS_HOST = os.getenv("REDIS_HOST", "redis")
 REDIS_PORT = os.getenv("REDIS_PORT", "6379")
 REDIS_CELERY_DB = os.getenv("REDIS_CELERY_DB", "0")

docker/pythonpath_dev/superset_test_config_light.py

@@ -1,55 +0,0 @@
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements.  See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership.  The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License.  You may obtain a copy of the License at
-#
-#   http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-# KIND, either express or implied.  See the License for the
-# specific language governing permissions and limitations
-# under the License.
-#
-# Test configuration for docker-compose-light.yml - uses SimpleCache instead of Redis
-
-# Import all settings from the main test config first
-import os
-import sys
-
-# Add the tests directory to the path to import the test config
-sys.path.insert(0, os.path.join(os.path.dirname(__file__), "..", ".."))
-from tests.integration_tests.superset_test_config import *  # noqa: F403
-
-# Override Redis-based caching to use simple in-memory cache
-CACHE_CONFIG = {
-    "CACHE_TYPE": "SimpleCache",
-    "CACHE_DEFAULT_TIMEOUT": 300,
-    "CACHE_KEY_PREFIX": "superset_test_",
-}
-
-DATA_CACHE_CONFIG = {
-    **CACHE_CONFIG,
-    "CACHE_DEFAULT_TIMEOUT": 30,
-    "CACHE_KEY_PREFIX": "superset_test_data_",
-}
-
-# Keep SimpleCache for these as they're already using it
-# FILTER_STATE_CACHE_CONFIG - already SimpleCache in parent
-# EXPLORE_FORM_DATA_CACHE_CONFIG - already SimpleCache in parent
-
-# Disable Celery for lightweight testing
-CELERY_CONFIG = None
-
-# Use FileSystemCache for SQL Lab results instead of Redis
-from flask_caching.backends.filesystemcache import FileSystemCache  # noqa: E402
-
-RESULTS_BACKEND = FileSystemCache("/app/superset_home/sqllab_test")
-
-# Override WEBDRIVER_BASEURL for tests to match expected values
-WEBDRIVER_BASEURL = "http://0.0.0.0:8080/"
-WEBDRIVER_BASEURL_USER_FRIENDLY = WEBDRIVER_BASEURL

docker/tag_latest_release.sh

@@ -1,190 +0,0 @@
-#! /bin/bash
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements.  See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership.  The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License.  You may obtain a copy of the License at
-#
-#   http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-# KIND, either express or implied.  See the License for the
-# specific language governing permissions and limitations
-# under the License.
-
-run_git_tag () {
-  if [[ "$DRY_RUN" == "false" ]] && [[ "$SKIP_TAG" == "false" ]]
-  then
-    git tag -a -f latest "${GITHUB_TAG_NAME}" -m "latest tag"
-    echo "${GITHUB_TAG_NAME} has been tagged 'latest'"
-  fi
-  exit 0
-}
-
-###
-# separating out git commands into functions so they can be mocked in unit tests
-###
-git_show_ref () {
-  if [[ "$TEST_ENV" == "true" ]]
-  then
-    if [[ "$GITHUB_TAG_NAME" == "does_not_exist" ]]
-        # mock return for testing only
-    then
-      echo ""
-    else
-      echo "2817aebd69dc7d199ec45d973a2079f35e5658b6 refs/tags/${GITHUB_TAG_NAME}"
-    fi
-  fi
-  result=$(git show-ref "${GITHUB_TAG_NAME}")
-  echo "${result}"
-}
-
-get_latest_tag_list () {
-  if [[ "$TEST_ENV" == "true" ]]
-  then
-    echo "(tag: 2.1.0, apache/2.1test)"
-  else
-    result=$(git show-ref --tags --dereference latest | awk '{print $2}' | xargs git show --pretty=tformat:%d -s | grep tag:)
-    echo "${result}"
-  fi
-}
-###
-
-split_string () {
-  local version="$1"
-  local delimiter="$2"
-  local components=()
-  local tmp=""
-  for (( i=0; i<${#version}; i++ )); do
-    local char="${version:$i:1}"
-    if [[ "$char" != "$delimiter" ]]; then
-      tmp="$tmp$char"
-    elif [[ -n "$tmp" ]]; then
-      components+=("$tmp")
-      tmp=""
-    fi
-  done
-  if [[ -n "$tmp" ]]; then
-    components+=("$tmp")
-  fi
-  echo "${components[@]}"
-}
-
-DRY_RUN=false
-
-# get params passed in with script when it was run
-# --dry-run is optional and returns the value of SKIP_TAG, but does not run the git tag statement
-# A tag name is required as a param. A SHA won't work. You must first tag a sha with a release number
-# and then run this script
-while [[ $# -gt 0 ]]
-do
-key="$1"
-
-case $key in
-    --dry-run)
-    DRY_RUN=true
-    shift # past value
-    ;;
-    *)    # this should be the tag name
-    GITHUB_TAG_NAME=$key
-    shift # past value
-    ;;
-esac
-done
-
-if [ -z "${GITHUB_TAG_NAME}" ]; then
-    echo "Missing tag parameter, usage: ./scripts/tag_latest_release.sh <GITHUB_TAG_NAME>"
-    echo "SKIP_TAG=true" >> $GITHUB_OUTPUT
-    exit 1
-fi
-
-if [ -z "$(git_show_ref)" ]; then
-    echo "The tag ${GITHUB_TAG_NAME} does not exist. Please use a different tag."
-    echo "SKIP_TAG=true" >> $GITHUB_OUTPUT
-    exit 0
-fi
-
-# check that this tag only contains a proper semantic version
-if ! [[ ${GITHUB_TAG_NAME} =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]
-then
-  echo "This tag ${GITHUB_TAG_NAME} is not a valid release version. Not tagging."
-  echo "SKIP_TAG=true" >> $GITHUB_OUTPUT
-  exit 1
-fi
-
-## split the current GITHUB_TAG_NAME into an array at the dot
-THIS_TAG_NAME=$(split_string "${GITHUB_TAG_NAME}" ".")
-
-# look up the 'latest' tag on git
-LATEST_TAG_LIST=$(get_latest_tag_list) || echo 'not found'
-
-# if 'latest' tag doesn't exist, then set this commit to latest
-if [[ -z "$LATEST_TAG_LIST" ]]
-then
-  echo "there are no latest tags yet, so I'm going to start by tagging this sha as the latest"
-  run_git_tag
-  exit 0
-fi
-
-# remove parenthesis and tag: from the list of tags
-LATEST_TAGS_STRINGS=$(echo "$LATEST_TAG_LIST" | sed 's/tag: \([^,]*\)/\1/g' | tr -d '()')
-
-LATEST_TAGS=$(split_string "$LATEST_TAGS_STRINGS" ",")
-TAGS=($(split_string "$LATEST_TAGS" " "))
-
-# Initialize a flag for comparison result
-compare_result=""
-
-# Iterate through the tags of the latest release
-for tag in $TAGS
-do
-  if [[ $tag == "latest" ]]; then
-    continue
-  else
-    ## extract just the version from this tag
-    LATEST_RELEASE_TAG="$tag"
-    echo "LATEST_RELEASE_TAG: ${LATEST_RELEASE_TAG}"
-
-    # check that this only contains a proper semantic version
-    if ! [[ ${LATEST_RELEASE_TAG} =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]
-    then
-      echo "'Latest' has been associated with tag ${LATEST_RELEASE_TAG} which is not a valid release version. Looking for another."
-      continue
-    fi
-    echo "The current release with the latest tag is version ${LATEST_RELEASE_TAG}"
-    # Split the version strings into arrays
-    THIS_TAG_NAME_ARRAY=($(split_string "$THIS_TAG_NAME" "."))
-    LATEST_RELEASE_TAG_ARRAY=($(split_string "$LATEST_RELEASE_TAG" "."))
-
-    # Iterate through the components of the version strings
-    for (( j=0; j<${#THIS_TAG_NAME_ARRAY[@]}; j++ )); do
-        echo "Comparing ${THIS_TAG_NAME_ARRAY[$j]} to ${LATEST_RELEASE_TAG_ARRAY[$j]}"
-        if [[ $((THIS_TAG_NAME_ARRAY[$j])) > $((LATEST_RELEASE_TAG_ARRAY[$j])) ]]; then
-            compare_result="greater"
-            break
-        elif [[ $((THIS_TAG_NAME_ARRAY[$j])) < $((LATEST_RELEASE_TAG_ARRAY[$j])) ]]; then
-            compare_result="lesser"
-            break
-        fi
-    done
-  fi
-done
-
-# Determine the result based on the comparison
-if [[ -z "$compare_result" ]]; then
-    echo "Versions are equal"
-    echo "SKIP_TAG=true" >> $GITHUB_OUTPUT
-elif [[ "$compare_result" == "greater" ]]; then
-    echo "This release tag ${GITHUB_TAG_NAME} is newer than the latest."
-    echo "SKIP_TAG=false" >> $GITHUB_OUTPUT
-    # Add other actions you want to perform for a newer version
-elif [[ "$compare_result" == "lesser" ]]; then
-    echo "This release tag ${GITHUB_TAG_NAME} is older than the latest."
-    echo "This release tag ${GITHUB_TAG_NAME} is not the latest. Not tagging."
-    # if you've gotten this far, then we don't want to run any tags in the next step
-    echo "SKIP_TAG=true" >> $GITHUB_OUTPUT
-fi

docs/README.md

@@ -21,183 +21,3 @@ This is the public documentation site for Superset, built using
 [Docusaurus 3](https://docusaurus.io/). See
 [CONTRIBUTING.md](../CONTRIBUTING.md#documentation) for documentation on
 contributing to documentation.
-
-## Version Management
-
-The Superset documentation site uses Docusaurus versioning with three independent versioned sections:
-
-- **Main Documentation** (`/docs/`) - Core Superset documentation
-- **Developer Portal** (`/developer_portal/`) - Developer guides and tutorials  
-- **Component Playground** (`/components/`) - Interactive component examples (currently disabled)
-
-Each section maintains its own version history and can be versioned independently.
-
-### Creating a New Version
-
-To create a new version for any section, use the Docusaurus version command with the appropriate plugin ID or use our automated scripts:
-
-#### Using Automated Scripts (Required)
-
-**⚠️ Important:** Always use these custom commands instead of the native Docusaurus commands. These scripts ensure that both the Docusaurus versioning system AND the `versions-config.json` file are updated correctly.
-
-```bash
-# Main Documentation
-yarn version:add:docs 1.2.0
-
-# Developer Portal
-yarn version:add:developer_portal 1.2.0
-
-# Component Playground (when enabled)
-yarn version:add:components 1.2.0
-```
-
-**Do NOT use** the native Docusaurus commands directly (`yarn docusaurus docs:version`), as they will:
-- ❌ Create version files but NOT update `versions-config.json`
-- ❌ Cause versions to not appear in dropdown menus
-- ❌ Require manual fixes to synchronize the configuration
-
-### Managing Versions
-
-#### With Automated Scripts
-The automated scripts handle all configuration updates automatically. No manual editing required!
-
-#### Manual Configuration
-If creating versions manually, you'll need to:
-
-1. **Update `versions-config.json`** (or `docusaurus.config.ts` if not using dynamic config):
-   - Add version to `onlyIncludeVersions` array
-   - Add version metadata to `versions` object
-   - Update `lastVersion` if needed
-
-2. **Files Created by Versioning**:
-   When a new version is created, Docusaurus generates:
-   - **Versioned docs folder**: `[section]_versioned_docs/version-X.X.X/`
-   - **Versioned sidebars**: `[section]_versioned_sidebars/version-X.X.X-sidebars.json`
-   - **Versions list**: `[section]_versions.json`
-
-   Note: For main docs, the prefix is omitted (e.g., `versioned_docs/` instead of `docs_versioned_docs/`)
-
-3. **Important**: After adding a version, restart the development server to see changes:
-   ```bash
-   yarn stop
-   yarn start
-   ```
-
-### Removing a Version
-
-#### Using Automated Scripts (Recommended)
-```bash
-# Main Documentation
-yarn version:remove:docs 1.0.0
-
-# Developer Portal
-yarn version:remove:developer_portal 1.0.0
-
-# Component Playground
-yarn version:remove:components 1.0.0
-```
-
-#### Manual Removal
-To manually remove a version:
-
-1. **Delete the version folder** from the appropriate location:
-   - Main docs: `versioned_docs/version-X.X.X/` (no prefix for main)
-   - Developer Portal: `developer_portal_versioned_docs/version-X.X.X/`
-   - Components: `components_versioned_docs/version-X.X.X/`
-
-2. **Delete the version metadata file**:
-   - Main docs: `versioned_sidebars/version-X.X.X-sidebars.json` (no prefix)
-   - Developer Portal: `developer_portal_versioned_sidebars/version-X.X.X-sidebars.json`
-   - Components: `components_versioned_sidebars/version-X.X.X-sidebars.json`
-
-3. **Update the versions list file**:
-   - Main docs: `versions.json`
-   - Developer Portal: `developer_portal_versions.json`
-   - Components: `components_versions.json`
-
-4. **Update configuration**:
-   - If using dynamic config: Update `versions-config.json`
-   - If using static config: Update `docusaurus.config.ts`
-
-5. **Restart the server** to see changes
-
-### Version Configuration Examples
-
-#### Main Documentation (default plugin)
-```typescript
-docs: {
-  includeCurrentVersion: true,
-  lastVersion: 'current',  // Makes /docs/ show Next version
-  onlyIncludeVersions: ['current', '1.1.0', '1.0.0'],
-  versions: {
-    current: {
-      label: 'Next',
-      path: '',  // Empty path for default routing
-      banner: 'unreleased',
-    },
-    '1.1.0': {
-      label: '1.1.0',
-      path: '1.1.0',
-      banner: 'none',
-    },
-  },
-}
-```
-
-#### Developer Portal & Components (custom plugins)
-```typescript
-{
-  id: 'developer_portal',
-  path: 'developer_portal',
-  routeBasePath: 'developer_portal',
-  includeCurrentVersion: true,
-  lastVersion: '1.1.0',  // Default version
-  onlyIncludeVersions: ['current', '1.1.0', '1.0.0'],
-  versions: {
-    current: {
-      label: 'Next',
-      path: 'next',
-      banner: 'unreleased',
-    },
-    '1.1.0': {
-      label: '1.1.0',
-      path: '1.1.0',
-      banner: 'none',
-    },
-  },
-}
-```
-
-### Best Practices
-
-1. **Version naming**: Use semantic versioning (e.g., 1.0.0, 1.1.0, 2.0.0)
-2. **Version banners**: Use `'unreleased'` for development versions, `'none'` for stable releases
-3. **Limit displayed versions**: Use `onlyIncludeVersions` to show only relevant versions
-4. **Test locally**: Always test version changes locally before deploying
-5. **Independent versioning**: Each section can have different version numbers and release cycles
-
-### Troubleshooting
-
-#### Version Not Showing After Creation
-
-If you accidentally used `yarn docusaurus docs:version` instead of `yarn version:add`:
-1. **Problem**: The version files were created but `versions-config.json` wasn't updated
-2. **Solution**: Either:
-   - Revert the changes: `git restore versions.json && rm -rf versioned_docs/ versioned_sidebars/`
-   - Then use the correct command: `yarn version:add:docs <version>`
-
-For other issues:
-- **Restart the server**: Changes to version configuration require a server restart
-- **Check config file**: Ensure `versions-config.json` includes the new version
-- **Verify files exist**: Check that versioned docs folder was created
-
-#### Broken Links in Versioned Documentation
-When creating a new version, links in the documentation are preserved as-is. Common issues:
-- **Cross-section links**: Links between sections (e.g., from developer_portal to docs) need to be version-aware
-- **Absolute vs relative paths**: Use relative paths within the same section
-- **Version-specific URLs**: Update hardcoded URLs to use version variables
-
-To fix broken links:
-1. Use `type: 'doc'` with `docId` for version-aware navigation in navbar
-2. Use relative paths within the same documentation section
-3. Test all versions after creation to identify broken links

docs/components/chart-components/bar-chart.md

@@ -1,105 +0,0 @@
-<!--
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
--->
----
-title: Bar Chart
-sidebar_position: 1
----
-
-# Bar Chart Component
-
-The Bar Chart component is used to visualize categorical data with rectangular bars.
-
-## Props
-
-| Prop | Type | Default | Description |
-|------|------|---------|-------------|
-| `data` | `array` | `[]` | Array of data objects to visualize |
-| `width` | `number` | `800` | Width of the chart in pixels |
-| `height` | `number` | `600` | Height of the chart in pixels |
-| `xField` | `string` | - | Field name for x-axis values |
-| `yField` | `string` | - | Field name for y-axis values |
-| `colorField` | `string` | - | Field name for color encoding |
-| `colorScheme` | `string` | `'supersetColors'` | Color scheme to use |
-| `showLegend` | `boolean` | `true` | Whether to show the legend |
-| `showGrid` | `boolean` | `true` | Whether to show grid lines |
-| `labelPosition` | `string` | `'top'` | Position of bar labels: 'top', 'middle', 'bottom' |
-
-## Examples
-
-### Basic Bar Chart
-
-```jsx
-import { BarChart } from '@superset-ui/chart-components';
-
-const data = [
-  { category: 'A', value: 10 },
-  { category: 'B', value: 20 },
-  { category: 'C', value: 15 },
-  { category: 'D', value: 25 },
-];
-
-function Example() {
-  return (
-    <BarChart
-      data={data}
-      width={800}
-      height={400}
-      xField="category"
-      yField="value"
-      colorScheme="supersetColors"
-    />
-  );
-}
-```
-
-### Grouped Bar Chart
-
-```jsx
-import { BarChart } from '@superset-ui/chart-components';
-
-const data = [
-  { category: 'A', group: 'Group 1', value: 10 },
-  { category: 'A', group: 'Group 2', value: 15 },
-  { category: 'B', group: 'Group 1', value: 20 },
-  { category: 'B', group: 'Group 2', value: 25 },
-  { category: 'C', group: 'Group 1', value: 15 },
-  { category: 'C', group: 'Group 2', value: 10 },
-];
-
-function Example() {
-  return (
-    <BarChart
-      data={data}
-      width={800}
-      height={400}
-      xField="category"
-      yField="value"
-      colorField="group"
-      colorScheme="supersetColors"
-    />
-  );
-}
-```
-
-## Best Practices
-
-- Use bar charts when comparing quantities across categories
-- Sort bars by value for better readability, unless there's a natural order to the categories
-- Use consistent colors for the same categories across different charts
-- Consider using horizontal bar charts when category labels are long

docs/components/index.md

@@ -1,59 +0,0 @@
-<!--
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
--->
----
-title: Component Library
-sidebar_position: 1
----
-
-# Superset Component Library
-
-Welcome to the Apache Superset Component Library documentation. This section provides comprehensive documentation for all the UI components, chart components, and layout components used in Superset.
-
-## What is the Component Library?
-
-The Component Library is a collection of reusable UI components that are used to build the Superset user interface. These components are designed to be consistent, accessible, and easy to use.
-
-## Component Categories
-
-The Component Library is organized into the following categories:
-
-### UI Components
-
-Basic UI components like buttons, inputs, dropdowns, and other form elements.
-
-### Chart Components
-
-Visualization components used to render different types of charts and graphs.
-
-### Layout Components
-
-Components used for page layout, such as containers, grids, and navigation elements.
-
-## Versioning
-
-The Component Library documentation follows its own versioning scheme, independent from the main Superset documentation. This allows us to update the component documentation as the components evolve, without affecting the main documentation.
-
-## Getting Started
-
-Browse the sidebar to explore the different components available in the library. Each component documentation includes:
-
-- Component description and purpose
-- Props and configuration options
-- Usage examples
-- Best practices

docs/components/layout-components/grid.md

@@ -1,113 +0,0 @@
-<!--
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
--->
----
-title: Grid
-sidebar_position: 1
----
-
-# Grid Component
-
-The Grid component provides a flexible layout system for arranging content in rows and columns.
-
-## Props
-
-| Prop | Type | Default | Description |
-|------|------|---------|-------------|
-| `gutter` | `number` or `[number, number]` | `0` | Grid spacing between items, can be a single number or [horizontal, vertical] |
-| `columns` | `number` | `12` | Number of columns in the grid |
-| `justify` | `string` | `'start'` | Horizontal alignment: 'start', 'center', 'end', 'space-between', 'space-around' |
-| `align` | `string` | `'top'` | Vertical alignment: 'top', 'middle', 'bottom' |
-| `wrap` | `boolean` | `true` | Whether to wrap items when they overflow |
-
-### Row Props
-
-| Prop | Type | Default | Description |
-|------|------|---------|-------------|
-| `gutter` | `number` or `[number, number]` | `0` | Spacing between items in the row |
-| `justify` | `string` | `'start'` | Horizontal alignment for this row |
-| `align` | `string` | `'top'` | Vertical alignment for this row |
-
-### Col Props
-
-| Prop | Type | Default | Description |
-|------|------|---------|-------------|
-| `span` | `number` | - | Number of columns the grid item spans |
-| `offset` | `number` | `0` | Number of columns the grid item is offset |
-| `xs`, `sm`, `md`, `lg`, `xl` | `number` or `object` | - | Responsive props for different screen sizes |
-
-## Examples
-
-### Basic Grid
-
-```jsx
-import { Grid, Row, Col } from '@superset-ui/core';
-
-function Example() {
-  return (
-    <Grid>
-      <Row gutter={16}>
-        <Col span={8}>
-          <div>Column 1</div>
-        </Col>
-        <Col span={8}>
-          <div>Column 2</div>
-        </Col>
-        <Col span={8}>
-          <div>Column 3</div>
-        </Col>
-      </Row>
-    </Grid>
-  );
-}
-```
-
-### Responsive Grid
-
-```jsx
-import { Grid, Row, Col } from '@superset-ui/core';
-
-function Example() {
-  return (
-    <Grid>
-      <Row gutter={[16, 24]}>
-        <Col xs={24} sm={12} md={8} lg={6}>
-          <div>Responsive Column 1</div>
-        </Col>
-        <Col xs={24} sm={12} md={8} lg={6}>
-          <div>Responsive Column 2</div>
-        </Col>
-        <Col xs={24} sm={12} md={8} lg={6}>
-          <div>Responsive Column 3</div>
-        </Col>
-        <Col xs={24} sm={12} md={8} lg={6}>
-          <div>Responsive Column 4</div>
-        </Col>
-      </Row>
-    </Grid>
-  );
-}
-```
-
-## Best Practices
-
-- Use the Grid system for complex layouts that need to be responsive
-- Specify column widths for different screen sizes to ensure proper responsive behavior
-- Use gutters to create appropriate spacing between grid items
-- Keep the grid structure consistent throughout your application
-- Consider using the grid system for dashboard layouts to ensure consistent spacing and alignment

docs/components/test.mdx

@@ -1,35 +0,0 @@
-<!--
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
--->
----
-title: Test
----
-
-import { StoryExample } from '../src/components/StorybookWrapper';
-
-# Test
-
-This is a test using our custom StorybookWrapper component.
-
-<StoryExample
-  component={() => (
-    <div style={{ padding: '10px', background: '#f0f0f0', borderRadius: '4px' }}>
-      This is a simple example component
-    </div>
-  )}
-/>

docs/components/ui-components/button.mdx

@@ -1,146 +0,0 @@
-<!--
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
--->
----
-title: Button Component
-sidebar_position: 1
----
-
-import { StoryExample, StoryWithControls } from '../../src/components/StorybookWrapper';
-import { Button } from '../../../superset-frontend/packages/superset-ui-core/src/components/Button';
-
-# Button Component
-
-The Button component is a fundamental UI element used throughout Superset for user interactions.
-
-## Basic Usage
-
-The default button with primary styling:
-<StoryExample
-  component={() => (
-    <Button buttonStyle="primary" onClick={() => console.log('Clicked!')}>
-      Click Me
-    </Button>
-  )}
-/>
-
-## Interactive Example
-
-<StoryWithControls
-  component={({ buttonStyle, buttonSize, label, disabled }) => (
-    <Button
-      buttonStyle={buttonStyle}
-      buttonSize={buttonSize}
-      disabled={disabled}
-      onClick={() => console.log('Clicked!')}
-    >
-      {label}
-    </Button>
-  )}
-  props={{
-    buttonStyle: 'primary',
-    buttonSize: 'default',
-    label: 'Click Me',
-    disabled: false
-  }}
-  controls={[
-    {
-      name: 'buttonStyle',
-      label: 'Button Style',
-      type: 'select',
-      options: ['primary', 'secondary', 'tertiary', 'success', 'warning', 'danger', 'default', 'link', 'dashed']
-    },
-    {
-      name: 'buttonSize',
-      label: 'Button Size',
-      type: 'select',
-      options: ['default', 'small', 'xsmall']
-    },
-    {
-      name: 'label',
-      label: 'Button Text',
-      type: 'text'
-    },
-    {
-      name: 'disabled',
-      label: 'Disabled',
-      type: 'boolean'
-    }
-  ]}
-/>
-
-## Props
-
-| Prop | Type | Default | Description |
-|------|------|---------|-------------|
-| `buttonStyle` | `'primary' \| 'secondary' \| 'tertiary' \| 'success' \| 'warning' \| 'danger' \| 'default' \| 'link' \| 'dashed'` | `'default'` | Button style |
-| `buttonSize` | `'default' \| 'small' \| 'xsmall'` | `'default'` | Button size |
-| `disabled` | `boolean` | `false` | Whether the button is disabled |
-| `cta` | `boolean` | `false` | Whether the button is a call-to-action button |
-| `tooltip` | `ReactNode` | - | Tooltip content |
-| `placement` | `TooltipProps['placement']` | - | Tooltip placement |
-| `onClick` | `function` | - | Callback when button is clicked |
-| `href` | `string` | - | Turns button into an anchor link |
-| `target` | `string` | - | Target attribute for anchor links |
-
-## Usage
-
-```jsx
-import Button from 'src/components/Button';
-
-function MyComponent() {
-  return (
-    <Button
-      buttonStyle="primary"
-      onClick={() => console.log('Button clicked')}
-    >
-      Click Me
-    </Button>
-  );
-}
-```
-
-## Button Styles
-
-Superset provides a variety of button styles for different purposes:
-
-- **Primary**: Used for primary actions
-- **Secondary**: Used for secondary actions
-- **Tertiary**: Used for less important actions
-- **Success**: Used for successful or confirming actions
-- **Warning**: Used for actions that require caution
-- **Danger**: Used for destructive actions
-- **Link**: Used for navigation
-- **Dashed**: Used for adding new items or features
-
-## Button Sizes
-
-Buttons come in three sizes:
-
-- **Default**: Standard size for most use cases
-- **Small**: Compact size for tight spaces
-- **XSmall**: Extra small size for very limited spaces
-
-## Best Practices
-
-- Use primary buttons for the main action in a form or page
-- Use secondary buttons for alternative actions
-- Use danger buttons for destructive actions
-- Limit the number of primary buttons on a page to avoid confusion
-- Use consistent button styles throughout your application
-- Add tooltips to buttons when their purpose might not be immediately clear

docs/components/versions.json

@@ -1 +0,0 @@
-[]

docs/components_versions.json

@@ -1 +0,0 @@
-[]

docs/developer_portal/api/frontend.md

@@ -1,477 +0,0 @@
----
-title: Frontend API Reference
-sidebar_position: 1
-hide_title: true
----
-
-<!--
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
--->
-
-# Frontend API Reference
-
-The `@apache-superset/core` package provides comprehensive APIs for frontend extension development. All APIs are organized into logical namespaces for easy discovery and use.
-
-## Core API
-
-The core namespace provides fundamental extension functionality.
-
-### registerView
-
-Registers a new view or panel in the specified contribution point.
-
-```typescript
-core.registerView(
-  id: string,
-  component: React.ComponentType
-): Disposable
-```
-
-**Example:**
-```typescript
-const panel = context.core.registerView('my-extension.panel', () => (
-  <MyPanelComponent />
-));
-```
-
-### getActiveView
-
-Gets the currently active view in a contribution area.
-
-```typescript
-core.getActiveView(area: string): View | undefined
-```
-
-## Commands API
-
-Manages command registration and execution.
-
-### registerCommand
-
-Registers a new command that can be triggered by menus, shortcuts, or programmatically.
-
-```typescript
-commands.registerCommand(
-  id: string,
-  handler: CommandHandler
-): Disposable
-
-interface CommandHandler {
-  title: string;
-  icon?: string;
-  execute: (...args: any[]) => any;
-  isEnabled?: (...args: any[]) => boolean;
-}
-```
-
-**Example:**
-```typescript
-const cmd = context.commands.registerCommand('my-extension.analyze', {
-  title: 'Analyze Query',
-  icon: 'BarChartOutlined',
-  execute: () => {
-    const query = context.sqlLab.getCurrentQuery();
-    // Perform analysis
-  },
-  isEnabled: () => {
-    return context.sqlLab.hasActiveEditor();
-  }
-});
-```
-
-### executeCommand
-
-Executes a registered command by ID.
-
-```typescript
-commands.executeCommand(id: string, ...args: any[]): Promise<any>
-```
-
-## SQL Lab API
-
-Provides access to SQL Lab functionality and events.
-
-### Query Access
-
-```typescript
-// Get current tab
-sqlLab.getCurrentTab(): Tab | undefined
-
-// Get all tabs
-sqlLab.getTabs(): Tab[]
-
-// Get current query
-sqlLab.getCurrentQuery(): string
-
-// Get selected text
-sqlLab.getSelectedText(): string | undefined
-```
-
-### Database Access
-
-```typescript
-// Get available databases
-sqlLab.getDatabases(): Database[]
-
-// Get database by ID
-sqlLab.getDatabase(id: number): Database | undefined
-
-// Get schemas for database
-sqlLab.getSchemas(databaseId: number): Promise<string[]>
-
-// Get tables for schema
-sqlLab.getTables(
-  databaseId: number,
-  schema: string
-): Promise<Table[]>
-```
-
-### Events
-
-```typescript
-// Query execution events
-sqlLab.onDidQueryRun: Event<QueryResult>
-sqlLab.onDidQueryStop: Event<QueryResult>
-sqlLab.onDidQueryFail: Event<QueryError>
-
-// Editor events
-sqlLab.onDidChangeEditorContent: Event<string>
-sqlLab.onDidChangeSelection: Event<Selection>
-
-// Tab events
-sqlLab.onDidChangeActiveTab: Event<Tab>
-sqlLab.onDidCloseTab: Event<Tab>
-sqlLab.onDidChangeTabTitle: Event<{tab: Tab, title: string}>
-
-// Panel events
-sqlLab.onDidOpenPanel: Event<Panel>
-sqlLab.onDidClosePanel: Event<Panel>
-sqlLab.onDidChangeActivePanel: Event<Panel>
-```
-
-**Event Usage Example:**
-```typescript
-const disposable = context.sqlLab.onDidQueryRun((result) => {
-  console.log('Query executed:', result.query);
-  console.log('Rows returned:', result.rowCount);
-  console.log('Execution time:', result.executionTime);
-});
-
-// Remember to dispose when done
-context.subscriptions.push(disposable);
-```
-
-## Authentication API
-
-Handles authentication and security tokens.
-
-### getCSRFToken
-
-Gets the current CSRF token for API requests.
-
-```typescript
-authentication.getCSRFToken(): Promise<string>
-```
-
-### getCurrentUser
-
-Gets information about the current user.
-
-```typescript
-authentication.getCurrentUser(): User
-
-interface User {
-  id: number;
-  username: string;
-  email: string;
-  roles: Role[];
-  permissions: Permission[];
-}
-```
-
-### hasPermission
-
-Checks if the current user has a specific permission.
-
-```typescript
-authentication.hasPermission(permission: string): boolean
-```
-
-## Extensions API
-
-Manages extension lifecycle and inter-extension communication.
-
-### getExtension
-
-Gets information about an installed extension.
-
-```typescript
-extensions.getExtension(id: string): Extension | undefined
-
-interface Extension {
-  id: string;
-  name: string;
-  version: string;
-  isActive: boolean;
-  metadata: ExtensionMetadata;
-}
-```
-
-### getActiveExtensions
-
-Gets all currently active extensions.
-
-```typescript
-extensions.getActiveExtensions(): Extension[]
-```
-
-### Events
-
-```typescript
-// Extension lifecycle events
-extensions.onDidActivateExtension: Event<Extension>
-extensions.onDidDeactivateExtension: Event<Extension>
-```
-
-## UI Components
-
-Import pre-built UI components from `@apache-superset/core`:
-
-```typescript
-import {
-  Button,
-  Select,
-  Input,
-  Table,
-  Modal,
-  Alert,
-  Tabs,
-  Card,
-  Dropdown,
-  Menu,
-  Tooltip,
-  Icon,
-  // ... many more
-} from '@apache-superset/core';
-```
-
-### Example Component Usage
-
-```typescript
-import { Button, Alert } from '@apache-superset/core';
-
-function MyExtensionPanel() {
-  return (
-    <div>
-      <Alert
-        message="Extension Loaded"
-        description="Your extension is ready to use"
-        type="success"
-      />
-      <Button
-        type="primary"
-        onClick={() => console.log('Clicked!')}
-      >
-        Execute Action
-      </Button>
-    </div>
-  );
-}
-```
-
-## Storage API
-
-Provides persistent storage for extension data.
-
-### Local Storage
-
-```typescript
-// Store data
-storage.local.set(key: string, value: any): Promise<void>
-
-// Retrieve data
-storage.local.get(key: string): Promise<any>
-
-// Remove data
-storage.local.remove(key: string): Promise<void>
-
-// Clear all extension data
-storage.local.clear(): Promise<void>
-```
-
-### Workspace Storage
-
-Workspace storage is shared across all users for collaborative features.
-
-```typescript
-storage.workspace.set(key: string, value: any): Promise<void>
-storage.workspace.get(key: string): Promise<any>
-storage.workspace.remove(key: string): Promise<void>
-```
-
-## Network API
-
-Utilities for making API calls to Superset.
-
-### fetch
-
-Enhanced fetch with CSRF token handling.
-
-```typescript
-network.fetch(url: string, options?: RequestInit): Promise<Response>
-```
-
-### API Client
-
-Type-safe API client for Superset endpoints.
-
-```typescript
-// Get chart data
-network.api.charts.get(id: number): Promise<Chart>
-
-// Query database
-network.api.sqlLab.execute(
-  databaseId: number,
-  query: string
-): Promise<QueryResult>
-
-// Get datasets
-network.api.datasets.list(): Promise<Dataset[]>
-```
-
-## Utility Functions
-
-### Formatting
-
-```typescript
-// Format numbers
-utils.formatNumber(value: number, format?: string): string
-
-// Format dates
-utils.formatDate(date: Date, format?: string): string
-
-// Format SQL
-utils.formatSQL(sql: string): string
-```
-
-### Validation
-
-```typescript
-// Validate SQL syntax
-utils.validateSQL(sql: string): ValidationResult
-
-// Check if valid database ID
-utils.isValidDatabaseId(id: any): boolean
-```
-
-## TypeScript Types
-
-Import common types for type safety:
-
-```typescript
-import type {
-  Database,
-  Dataset,
-  Chart,
-  Dashboard,
-  Query,
-  QueryResult,
-  Tab,
-  Panel,
-  User,
-  Role,
-  Permission,
-  ExtensionContext,
-  Disposable,
-  Event,
-  // ... more types
-} from '@apache-superset/core';
-```
-
-## Extension Context
-
-The context object passed to your extension's `activate` function:
-
-```typescript
-interface ExtensionContext {
-  // Subscription management
-  subscriptions: Disposable[];
-
-  // Extension metadata
-  extensionId: string;
-  extensionPath: string;
-
-  // API namespaces
-  core: CoreAPI;
-  commands: CommandsAPI;
-  sqlLab: SqlLabAPI;
-  authentication: AuthenticationAPI;
-  extensions: ExtensionsAPI;
-  storage: StorageAPI;
-  network: NetworkAPI;
-  utils: UtilsAPI;
-
-  // Logging
-  logger: Logger;
-}
-```
-
-## Event Handling
-
-Events follow the VS Code pattern with subscribe/dispose:
-
-```typescript
-// Subscribe to event
-const disposable = sqlLab.onDidQueryRun((result) => {
-  // Handle event
-});
-
-// Dispose when done
-disposable.dispose();
-
-// Or add to context for automatic cleanup
-context.subscriptions.push(disposable);
-```
-
-## Best Practices
-
-1. **Always dispose subscriptions** to prevent memory leaks
-2. **Use TypeScript** for better IDE support and type safety
-3. **Handle errors gracefully** with try-catch blocks
-4. **Check permissions** before sensitive operations
-5. **Use provided UI components** for consistency
-6. **Cache API responses** when appropriate
-7. **Validate user input** before processing
-
-## Version Compatibility
-
-The frontend API follows semantic versioning:
-
-- **Major version**: Breaking changes
-- **Minor version**: New features, backward compatible
-- **Patch version**: Bug fixes
-
-Check compatibility in your `extension.json`:
-
-```json
-{
-  "engines": {
-    "@apache-superset/core": "^1.0.0"
-  }
-}
-```

docs/developer_portal/architecture/overview.md

@@ -1,348 +0,0 @@
----
-title: Architecture Overview
-sidebar_position: 1
-hide_title: true
----
-
-<!--
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
--->
-
-# Extension Architecture Overview
-
-The Superset extension architecture is designed to be modular, secure, and performant. This document provides a comprehensive overview of how extensions work and interact with the Superset host application.
-
-## Core Principles
-
-### 1. Lean Core
-Superset's core remains minimal, with features delegated to extensions wherever possible. Built-in features use the same APIs as external extensions, ensuring API quality through dogfooding.
-
-### 2. Explicit Contribution Points
-All extension points are clearly defined and documented. Extensions declare their capabilities in metadata files, enabling predictable lifecycle management.
-
-### 3. Versioned APIs
-Public interfaces follow semantic versioning, ensuring backward compatibility and safe evolution of the platform.
-
-### 4. Lazy Loading
-Extensions load only when needed, minimizing performance impact and resource consumption.
-
-### 5. Composability
-Architecture patterns and APIs are reusable across different Superset modules, promoting consistency.
-
-### 6. Community-Driven
-The system evolves based on real-world feedback, with new extension points added as needs emerge.
-
-## System Architecture
-
-```mermaid
-graph TB
-    subgraph "Superset Host Application"
-        Core[Core Application]
-        API[Extension APIs]
-        Loader[Extension Loader]
-        Manager[Extension Manager]
-    end
-
-    subgraph "Core Packages"
-        FrontendCore["@apache-superset/core<br/>(Frontend)"]
-        BackendCore["apache-superset-core<br/>(Backend)"]
-        CLI["apache-superset-extensions-cli"]
-    end
-
-    subgraph "Extension"
-        Metadata[extension.json]
-        Frontend[Frontend Code]
-        Backend[Backend Code]
-        Bundle[.supx Bundle]
-    end
-
-    Core --> API
-    API --> FrontendCore
-    API --> BackendCore
-    Loader --> Manager
-    Manager --> Bundle
-    Frontend --> FrontendCore
-    Backend --> BackendCore
-    CLI --> Bundle
-```
-
-## Key Components
-
-### Host Application
-
-The Superset host application provides:
-
-- **Extension APIs**: Well-defined interfaces for extensions to interact with Superset
-- **Extension Manager**: Handles lifecycle, activation, and deactivation
-- **Module Loader**: Dynamically loads extension code using Webpack Module Federation
-- **Security Context**: Manages permissions and sandboxing for extensions
-
-### Core Packages
-
-#### @apache-superset/core (Frontend)
-- Shared UI components and utilities
-- TypeScript type definitions
-- Frontend API implementations
-- Event system and command registry
-
-#### apache-superset-core (Backend)
-- Python base classes and utilities
-- Database access APIs
-- Security and permission helpers
-- REST API registration
-
-#### apache-superset-extensions-cli
-- Project scaffolding
-- Build and bundling tools
-- Development server
-- Package management
-
-### Extension Structure
-
-Each extension consists of:
-
-- **Metadata** (`extension.json`): Declares capabilities and requirements
-- **Frontend**: React components and TypeScript code
-- **Backend**: Python modules and API endpoints
-- **Assets**: Styles, images, and other resources
-- **Bundle** (`.supx`): Packaged distribution format
-
-## Module Federation
-
-Extensions use Webpack Module Federation for dynamic loading:
-
-```javascript
-// Extension webpack.config.js
-new ModuleFederationPlugin({
-  name: 'my_extension',
-  filename: 'remoteEntry.[contenthash].js',
-  exposes: {
-    './index': './src/index.tsx',
-  },
-  externals: {
-    '@apache-superset/core': 'superset',
-  },
-  shared: {
-    react: { singleton: true },
-    'react-dom': { singleton: true },
-  }
-})
-```
-
-This allows:
-- **Independent builds**: Extensions compile separately from Superset
-- **Shared dependencies**: Common libraries like React aren't duplicated
-- **Dynamic loading**: Extensions load at runtime without rebuilding Superset
-- **Version compatibility**: Extensions declare compatible core versions
-
-## Extension Lifecycle
-
-### 1. Registration
-```typescript
-// Extension registered with host
-extensionManager.register({
-  name: 'my-extension',
-  version: '1.0.0',
-  manifest: manifestData
-});
-```
-
-### 2. Activation
-```typescript
-// activate() called when extension loads
-export function activate(context: ExtensionContext) {
-  // Register contributions
-  const disposables = [];
-
-  // Add panel
-  disposables.push(
-    context.core.registerView('my-panel', MyPanel)
-  );
-
-  // Register command
-  disposables.push(
-    context.commands.registerCommand('my-command', {
-      execute: () => { /* ... */ }
-    })
-  );
-
-  // Store for cleanup
-  context.subscriptions.push(...disposables);
-}
-```
-
-### 3. Runtime
-- Extension responds to events
-- Provides UI components when requested
-- Executes commands when triggered
-- Accesses APIs as needed
-
-### 4. Deactivation
-```typescript
-// Automatic cleanup of registered items
-export function deactivate() {
-  // context.subscriptions automatically disposed
-  // Additional cleanup if needed
-}
-```
-
-## Contribution Types
-
-### Views
-Extensions can add panels and UI components:
-
-```json
-{
-  "views": {
-    "sqllab.panels": [{
-      "id": "my-panel",
-      "name": "My Panel",
-      "icon": "ToolOutlined"
-    }]
-  }
-}
-```
-
-### Commands
-Define executable actions:
-
-```json
-{
-  "commands": [{
-    "command": "my-extension.run",
-    "title": "Run Analysis",
-    "icon": "PlayCircleOutlined"
-  }]
-}
-```
-
-### Menus
-Add items to existing menus:
-
-```json
-{
-  "menus": {
-    "sqllab.editor": {
-      "primary": [{
-        "command": "my-extension.run",
-        "when": "editorHasSelection"
-      }]
-    }
-  }
-}
-```
-
-### API Endpoints
-Register backend REST endpoints:
-
-```python
-from superset_core.api import rest_api
-
-@rest_api.route('/my-endpoint')
-def my_endpoint():
-    return {'data': 'value'}
-```
-
-## Security Model
-
-### Permissions
-- Extensions run with user's permissions
-- No elevation of privileges
-- Access controlled by Superset's RBAC
-
-### Sandboxing
-- Frontend code runs in browser context
-- Backend code runs in Python process
-- Future: Optional sandboxed execution
-
-### Validation
-- Manifest validation on upload
-- Signature verification (future)
-- Dependency scanning
-
-## Performance Considerations
-
-### Lazy Loading
-- Extensions load only when features are accessed
-- Code splitting for large extensions
-- Cached after first load
-
-### Bundle Optimization
-- Tree shaking removes unused code
-- Minification reduces size
-- Compression for network transfer
-
-### Resource Management
-- Automatic cleanup on deactivation
-- Memory leak prevention
-- Event listener management
-
-## Development vs Production
-
-### Development Mode
-```python
-# superset_config.py
-ENABLE_EXTENSIONS = True
-LOCAL_EXTENSIONS = ['/path/to/extension']
-```
-- Hot reloading
-- Source maps
-- Debug logging
-
-### Production Mode
-- Optimized bundles
-- Cached assets
-- Performance monitoring
-
-## Future Enhancements
-
-### Planned Features
-- Enhanced sandboxing
-- Extension marketplace
-- Inter-extension communication
-- Theme contributions
-- Chart type extensions
-
-### API Expansion
-- Dashboard extensions
-- Database connector API
-- Security provider interface
-- Workflow automation
-
-## Best Practices
-
-### Do's
-- ✅ Use TypeScript for type safety
-- ✅ Follow semantic versioning
-- ✅ Handle errors gracefully
-- ✅ Clean up resources properly
-- ✅ Document your extension
-
-### Don'ts
-- ❌ Access private APIs
-- ❌ Modify global state directly
-- ❌ Block the main thread
-- ❌ Store sensitive data insecurely
-- ❌ Assume API stability in 0.x versions
-
-## Learn More
-
-- [API Reference](../api/frontend)
-- [Development Guide](../getting-started)
-- [Security Guidelines](./security)
-- [Performance Optimization](./performance)

docs/developer_portal/cli/overview.md

@@ -1,466 +0,0 @@
-<!--
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
--->
----
-title: CLI Documentation
-sidebar_position: 1
-hide_title: true
----
-
-# Superset Extensions CLI
-
-The `apache-superset-extensions-cli` provides command-line tools for creating, developing, and packaging Superset extensions.
-
-## Installation
-
-```bash
-pip install apache-superset-extensions-cli
-```
-
-## Commands
-
-### init
-
-Creates a new extension project with the standard folder structure.
-
-```bash
-superset-extensions init <extension-name> [options]
-```
-
-**Options:**
-- `--template <template>`: Use a specific template (default: basic)
-- `--author <name>`: Set the author name
-- `--description <text>`: Set the extension description
-- `--with-backend`: Include backend code structure
-
-**Example:**
-```bash
-superset-extensions init my-extension \
-  --author "John Doe" \
-  --description "Adds custom analytics to SQL Lab" \
-  --with-backend
-```
-
-**Generated Structure:**
-```
-my-extension/
-├── extension.json
-├── frontend/
-│   ├── src/
-│   │   └── index.tsx
-│   ├── package.json
-│   ├── tsconfig.json
-│   └── webpack.config.js
-├── backend/
-│   ├── src/
-│   │   └── my_extension/
-│   │       ├── __init__.py
-│   │       └── entrypoint.py
-│   ├── tests/
-│   ├── pyproject.toml
-│   └── requirements.txt
-└── README.md
-```
-
-### dev
-
-Starts the development server with hot reloading.
-
-```bash
-superset-extensions dev [options]
-```
-
-**Options:**
-- `--port <port>`: Development server port (default: 9001)
-- `--host <host>`: Development server host (default: localhost)
-- `--no-watch`: Disable file watching
-- `--verbose`: Show detailed output
-
-**Example:**
-```bash
-# Start development server
-superset-extensions dev
-
-# Output:
-⚙️  Building frontend assets...
-✅ Frontend rebuilt
-✅ Backend files synced
-✅ Manifest updated
-👀 Watching for changes...
-```
-
-### build
-
-Builds the extension for production.
-
-```bash
-superset-extensions build [options]
-```
-
-**Options:**
-- `--mode <mode>`: Build mode (development | production)
-- `--analyze`: Generate bundle analysis
-- `--source-maps`: Include source maps
-
-**Example:**
-```bash
-# Production build
-superset-extensions build --mode production
-
-# With analysis
-superset-extensions build --analyze
-```
-
-### bundle
-
-Creates a `.supx` package for distribution.
-
-```bash
-superset-extensions bundle [options]
-```
-
-**Options:**
-- `--output <path>`: Output directory (default: current)
-- `--sign`: Sign the package (requires certificate)
-- `--compress`: Compression level (0-9, default: 6)
-
-**Example:**
-```bash
-# Create bundle
-superset-extensions bundle
-
-# Creates: my-extension-1.0.0.supx
-```
-
-### validate
-
-Validates extension configuration and structure.
-
-```bash
-superset-extensions validate [options]
-```
-
-**Options:**
-- `--fix`: Auto-fix common issues
-- `--strict`: Enable strict validation
-
-**Checks:**
-- Valid extension.json syntax
-- Required files present
-- Dependency versions
-- Module exports
-- TypeScript configuration
-
-**Example:**
-```bash
-superset-extensions validate --strict
-
-# Output:
-✅ extension.json valid
-✅ Frontend structure valid
-✅ Backend structure valid
-⚠️  Warning: Missing LICENSE file
-✅ Validation passed with warnings
-```
-
-### test
-
-Runs extension tests.
-
-```bash
-superset-extensions test [options]
-```
-
-**Options:**
-- `--coverage`: Generate coverage report
-- `--watch`: Run in watch mode
-- `--frontend-only`: Run only frontend tests
-- `--backend-only`: Run only backend tests
-
-**Example:**
-```bash
-# Run all tests
-superset-extensions test --coverage
-
-# Watch mode for frontend
-superset-extensions test --frontend-only --watch
-```
-
-### publish
-
-Publishes extension to a registry (future feature).
-
-```bash
-superset-extensions publish [options]
-```
-
-**Options:**
-- `--registry <url>`: Registry URL
-- `--token <token>`: Authentication token
-- `--dry-run`: Simulate publish
-
-## Configuration
-
-### Project Configuration
-
-The CLI reads configuration from multiple sources:
-
-1. **extension.json** - Extension metadata
-2. **package.json** - Frontend dependencies
-3. **pyproject.toml** - Backend configuration
-4. **.extensionrc** - CLI-specific settings
-
-### .extensionrc Example
-
-```json
-{
-  "dev": {
-    "port": 9001,
-    "host": "localhost",
-    "autoReload": true
-  },
-  "build": {
-    "mode": "production",
-    "sourceMaps": false,
-    "optimization": true
-  },
-  "test": {
-    "coverage": true,
-    "threshold": {
-      "statements": 80,
-      "branches": 70,
-      "functions": 80,
-      "lines": 80
-    }
-  }
-}
-```
-
-## Templates
-
-### Available Templates
-
-- **basic**: Simple extension with frontend only
-- **full-stack**: Frontend and backend components
-- **sql-panel**: SQL Lab panel extension
-- **api-only**: Backend API extension
-- **chart-plugin**: Custom chart visualization
-
-### Using Templates
-
-```bash
-# Use specific template
-superset-extensions init my-chart --template chart-plugin
-
-# List available templates
-superset-extensions init --list-templates
-```
-
-### Custom Templates
-
-Create custom templates in `~/.superset-extensions/templates/`:
-
-```
-~/.superset-extensions/templates/
-└── my-template/
-    ├── template.json
-    └── files/
-        └── ... template files ...
-```
-
-## Development Workflow
-
-### 1. Create Extension
-
-```bash
-superset-extensions init awesome-feature
-cd awesome-feature
-```
-
-### 2. Install Dependencies
-
-```bash
-# Frontend
-cd frontend && npm install
-
-# Backend (if applicable)
-cd ../backend && pip install -r requirements.txt
-```
-
-### 3. Configure Superset
-
-```python
-# superset_config.py
-ENABLE_EXTENSIONS = True
-LOCAL_EXTENSIONS = [
-    "/path/to/awesome-feature"
-]
-```
-
-### 4. Start Development
-
-```bash
-# Terminal 1: Extension dev server
-superset-extensions dev
-
-# Terminal 2: Superset
-superset run -p 8088 --reload
-```
-
-### 5. Test Changes
-
-Make changes to your code and see them reflected immediately in Superset.
-
-### 6. Build and Package
-
-```bash
-# Validate
-superset-extensions validate
-
-# Test
-superset-extensions test
-
-# Build
-superset-extensions build --mode production
-
-# Bundle
-superset-extensions bundle
-```
-
-### 7. Deploy
-
-Upload the `.supx` file to your Superset instance.
-
-## Environment Variables
-
-The CLI respects these environment variables:
-
-- `SUPERSET_EXTENSIONS_DEV_PORT`: Development server port
-- `SUPERSET_EXTENSIONS_DEV_HOST`: Development server host
-- `SUPERSET_BASE_URL`: Superset instance URL
-- `NODE_ENV`: Node environment (development/production)
-- `PYTHONPATH`: Python module search path
-
-## Troubleshooting
-
-### Common Issues
-
-#### Port Already in Use
-
-```bash
-# Use different port
-superset-extensions dev --port 9002
-```
-
-#### Module Federation Errors
-
-```bash
-# Rebuild with clean cache
-rm -rf dist/ node_modules/.cache
-superset-extensions build
-```
-
-#### Python Import Errors
-
-```bash
-# Ensure virtual environment is activated
-source venv/bin/activate
-superset-extensions dev
-```
-
-### Debug Mode
-
-Enable verbose output for troubleshooting:
-
-```bash
-# Verbose output
-superset-extensions dev --verbose
-
-# Debug webpack
-DEBUG=webpack:* superset-extensions build
-```
-
-## Best Practices
-
-1. **Version Control**: Commit `extension.json` but not `dist/`
-2. **Dependencies**: Pin versions in package.json
-3. **Testing**: Write tests for critical functionality
-4. **Documentation**: Keep README.md updated
-5. **Validation**: Run validate before bundling
-6. **Semantic Versioning**: Follow semver for releases
-
-## Advanced Usage
-
-### Custom Webpack Configuration
-
-Extend the default webpack config:
-
-```javascript
-// webpack.config.js
-const baseConfig = require('./webpack.base.config');
-
-module.exports = {
-  ...baseConfig,
-  // Custom modifications
-  resolve: {
-    ...baseConfig.resolve,
-    alias: {
-      '@': path.resolve(__dirname, 'src'),
-    },
-  },
-};
-```
-
-### CI/CD Integration
-
-```yaml
-# .github/workflows/extension.yml
-name: Extension CI
-
-on: [push, pull_request]
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-node@v2
-      - uses: actions/setup-python@v2
-
-      - name: Install CLI
-        run: pip install apache-superset-extensions-cli
-
-      - name: Validate
-        run: superset-extensions validate --strict
-
-      - name: Test
-        run: superset-extensions test --coverage
-
-      - name: Build
-        run: superset-extensions build --mode production
-
-      - name: Bundle
-        run: superset-extensions bundle
-```
-
-## Getting Help
-
-- **Documentation**: [Developer Portal](../)
-- **Examples**: [GitHub Repository](https://github.com/apache/superset/tree/master/extensions)
-- **Issues**: [GitHub Issues](https://github.com/apache/superset/issues)
-- **Community**: [Slack Channel](https://apache-superset.slack.com)

docs/developer_portal/examples/index.md

@@ -1,464 +0,0 @@
----
-title: Extension Examples
-sidebar_position: 1
-hide_title: true
----
-
-<!--
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
--->
-
-# Extension Examples
-
-Learn from real-world extension implementations that showcase different capabilities of the Superset extension system.
-
-## Dataset References Panel
-
-A SQL Lab panel that analyzes queries and displays information about referenced tables.
-
-### Features
-- Parses SQL to extract table references
-- Shows table owners and permissions
-- Displays last partition information
-- Provides row count estimates
-
-### Key Implementation
-
-```typescript
-// Parse SQL and extract tables
-function extractTables(sql: string): TableReference[] {
-  const tables = [];
-  const tableRegex = /FROM\s+(\w+\.?\w+)/gi;
-  let match;
-
-  while ((match = tableRegex.exec(sql)) !== null) {
-    tables.push({
-      schema: match[1].split('.')[0],
-      table: match[1].split('.')[1] || match[1],
-    });
-  }
-
-  return tables;
-}
-
-// Register panel
-export function activate(context: ExtensionContext) {
-  const panel = context.core.registerView('dataset-references.panel', () => (
-    <DatasetReferencesPanel />
-  ));
-
-  // Listen for query changes
-  const listener = context.sqlLab.onDidChangeEditorContent((content) => {
-    const tables = extractTables(content);
-    updatePanelWithTables(tables);
-  });
-
-  context.subscriptions.push(panel, listener);
-}
-```
-
-### Manifest
-
-```json
-{
-  "name": "dataset-references",
-  "contributions": {
-    "views": {
-      "sqllab.panels": [{
-        "id": "dataset-references.panel",
-        "name": "Dataset References",
-        "icon": "DatabaseOutlined",
-        "location": "right"
-      }]
-    }
-  }
-}
-```
-
-## Query Optimizer
-
-Analyzes SQL queries and suggests optimizations.
-
-### Features
-- Detects missing indexes
-- Suggests query rewrites
-- Identifies expensive operations
-- Provides execution plan analysis
-
-### Implementation Highlights
-
-```typescript
-// Register optimization command
-const optimizeCommand = context.commands.registerCommand('query-optimizer.analyze', {
-  title: 'Analyze Query Performance',
-  icon: 'ThunderboltOutlined',
-  execute: async () => {
-    const query = context.sqlLab.getCurrentQuery();
-    const database = context.sqlLab.getCurrentDatabase();
-
-    // Get execution plan
-    const plan = await getExecutionPlan(database.id, query);
-
-    // Analyze and suggest improvements
-    const suggestions = analyzeExecutionPlan(plan);
-
-    // Show results in panel
-    showOptimizationResults(suggestions);
-  }
-});
-
-// Add to editor menu
-"menus": {
-  "sqllab.editor": {
-    "primary": [{
-      "command": "query-optimizer.analyze",
-      "when": "editorHasContent"
-    }]
-  }
-}
-```
-
-## Natural Language to SQL
-
-Converts natural language questions to SQL queries using LLM integration.
-
-### Features
-- Natural language input
-- Context-aware SQL generation
-- Query validation
-- History tracking
-
-### Key Components
-
-```typescript
-// Backend API endpoint
-@rest_api.route('/nl2sql/generate')
-def generate_sql(prompt: str, context: dict):
-    # Use LLM to generate SQL
-    sql = llm_client.generate(
-        prompt=prompt,
-        schema=context['schema'],
-        examples=context['examples']
-    )
-
-    # Validate generated SQL
-    validation = validate_sql(sql)
-
-    return {
-        'sql': sql,
-        'valid': validation.is_valid,
-        'errors': validation.errors
-    }
-```
-
-```typescript
-// Frontend integration
-function NL2SQLPanel() {
-  const [prompt, setPrompt] = useState('');
-  const [loading, setLoading] = useState(false);
-
-  const generateSQL = async () => {
-    setLoading(true);
-
-    const response = await context.network.api.post('/extensions/nl2sql/generate', {
-      prompt,
-      context: {
-        database: context.sqlLab.getCurrentDatabase(),
-        schema: await context.sqlLab.getCurrentSchema(),
-      }
-    });
-
-    if (response.valid) {
-      // Insert SQL into editor
-      context.sqlLab.insertText(response.sql);
-    }
-
-    setLoading(false);
-  };
-
-  return (
-    <div>
-      <Input.TextArea
-        value={prompt}
-        onChange={(e) => setPrompt(e.target.value)}
-        placeholder="Describe what data you want..."
-      />
-      <Button onClick={generateSQL} loading={loading}>
-        Generate SQL
-      </Button>
-    </div>
-  );
-}
-```
-
-## Schema Visualizer
-
-Interactive database schema visualization.
-
-### Features
-- Visual ERD diagram
-- Table relationships
-- Column details on hover
-- Export to image
-
-### Implementation
-
-```typescript
-import { Graph } from '@antv/g6';
-
-function SchemaVisualizer() {
-  const containerRef = useRef<HTMLDivElement>(null);
-  const [graph, setGraph] = useState<Graph>();
-
-  useEffect(() => {
-    if (!containerRef.current) return;
-
-    const g = new Graph({
-      container: containerRef.current,
-      layout: {
-        type: 'dagre',
-        rankdir: 'LR',
-      },
-      defaultNode: {
-        type: 'sql-table-node',
-      },
-      defaultEdge: {
-        type: 'sql-relation-edge',
-      },
-    });
-
-    setGraph(g);
-    loadSchemaData(g);
-
-    return () => g.destroy();
-  }, []);
-
-  const loadSchemaData = async (g: Graph) => {
-    const tables = await context.sqlLab.getTables();
-    const nodes = tables.map(table => ({
-      id: table.name,
-      label: table.name,
-      columns: table.columns,
-    }));
-
-    const edges = extractRelationships(tables);
-
-    g.data({ nodes, edges });
-    g.render();
-  };
-
-  return <div ref={containerRef} style={{ height: '100%' }} />;
-}
-```
-
-## SQL Formatter
-
-Formats and beautifies SQL code with customizable rules.
-
-### Features
-- Multiple formatting styles
-- Custom rule configuration
-- Batch formatting
-- Format on save
-
-### Simple Implementation
-
-```typescript
-import { format } from 'sql-formatter';
-
-const formatCommand = context.commands.registerCommand('sql-formatter.format', {
-  title: 'Format SQL',
-  execute: () => {
-    const sql = context.sqlLab.getCurrentQuery();
-
-    const formatted = format(sql, {
-      language: 'sql',
-      indent: '  ',
-      uppercase: true,
-      linesBetweenQueries: 2,
-    });
-
-    context.sqlLab.replaceQuery(formatted);
-  }
-});
-
-// Auto-format on save
-context.sqlLab.onWillSaveQuery((event) => {
-  if (context.storage.local.get('autoFormat')) {
-    const formatted = format(event.query);
-    event.waitUntil(Promise.resolve(formatted));
-  }
-});
-```
-
-## Query History Search
-
-Enhanced query history with advanced search and filtering.
-
-### Features
-- Full-text search
-- Filter by date, user, database
-- Query statistics
-- Export capabilities
-
-### UI Component
-
-```typescript
-function QueryHistoryPanel() {
-  const [queries, setQueries] = useState<Query[]>([]);
-  const [filters, setFilters] = useState<Filters>({});
-
-  useEffect(() => {
-    loadQueries();
-  }, [filters]);
-
-  const loadQueries = async () => {
-    const history = await context.network.api.get('/api/v1/query', {
-      params: {
-        ...filters,
-        page_size: 100,
-      }
-    });
-
-    setQueries(history.result);
-  };
-
-  return (
-    <div>
-      <SearchFilters onChange={setFilters} />
-      <Table
-        dataSource={queries}
-        columns={[
-          { title: 'Query', dataIndex: 'sql', ellipsis: true },
-          { title: 'Database', dataIndex: 'database' },
-          { title: 'Status', dataIndex: 'status' },
-          { title: 'Duration', dataIndex: 'duration' },
-          { title: 'User', dataIndex: 'user' },
-          {
-            title: 'Actions',
-            render: (query) => (
-              <Button
-                icon={<CopyOutlined />}
-                onClick={() => context.sqlLab.insertText(query.sql)}
-              />
-            ),
-          },
-        ]}
-      />
-    </div>
-  );
-}
-```
-
-## Git Integration
-
-Version control for SQL queries and dashboards.
-
-### Features
-- Save queries to Git
-- Track changes
-- Collaborative editing
-- Branch management
-
-### Backend Integration
-
-```python
-from git import Repo
-
-class GitExtension:
-    def __init__(self, repo_path):
-        self.repo = Repo(repo_path)
-
-    def save_query(self, query, message):
-        # Save query to file
-        path = f"queries/{query.name}.sql"
-        with open(path, 'w') as f:
-            f.write(query.sql)
-
-        # Commit to Git
-        self.repo.index.add([path])
-        self.repo.index.commit(message)
-
-        return {
-            'status': 'success',
-            'commit': self.repo.head.commit.hexsha
-        }
-```
-
-## Best Practices from Examples
-
-### 1. User Experience
-- Provide clear feedback for async operations
-- Handle errors gracefully
-- Include loading states
-- Add keyboard shortcuts
-
-### 2. Performance
-- Debounce expensive operations
-- Cache API responses
-- Use virtual scrolling for large lists
-- Lazy load heavy components
-
-### 3. Integration
-- Respect Superset's theme
-- Use provided UI components
-- Follow existing UX patterns
-- Integrate with existing menus
-
-### 4. Code Organization
-```
-extension/
-├── frontend/
-│   ├── src/
-│   │   ├── components/     # UI components
-│   │   ├── hooks/          # Custom hooks
-│   │   ├── services/       # API services
-│   │   ├── utils/          # Utilities
-│   │   └── index.tsx       # Entry point
-│   └── tests/
-├── backend/
-│   ├── src/
-│   │   ├── api/           # REST endpoints
-│   │   ├── models/        # Data models
-│   │   ├── services/      # Business logic
-│   │   └── entrypoint.py
-│   └── tests/
-```
-
-### 5. Testing
-```typescript
-// Test example
-describe('DatasetReferences', () => {
-  it('should extract tables from SQL', () => {
-    const sql = 'SELECT * FROM users JOIN orders ON users.id = orders.user_id';
-    const tables = extractTables(sql);
-
-    expect(tables).toEqual([
-      { schema: 'public', table: 'users' },
-      { schema: 'public', table: 'orders' },
-    ]);
-  });
-});
-```
-
-## Learn More
-
-- [API Reference](../api/frontend)
-- [Architecture Overview](../architecture/overview)
-- [Getting Started Guide](../getting-started)
-- [CLI Documentation](../cli/overview)

docs/developer_portal/getting-started/index.md

@@ -1,248 +0,0 @@
----
-title: Getting Started
-sidebar_position: 2
-hide_title: true
----
-
-<!--
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
--->
-
-# Getting Started with Extensions
-
-This guide will walk you through creating, developing, and deploying your first Superset extension.
-
-## Prerequisites
-
-Before you begin, make sure you have:
-
-- **Node.js 16+** and npm/yarn installed
-- **Python 3.9+** and pip installed  
-- **Superset** running locally or access to a Superset instance
-- **Git** for version control
-- Basic knowledge of React and TypeScript
-
-## Quick Start
-
-### 1. Install the CLI
-
-First, install the Superset Extensions CLI globally:
-
-```bash
-pip install apache-superset-extensions-cli
-```
-
-### 2. Create Your First Extension
-
-Use the CLI to scaffold a new extension project:
-
-```bash
-superset-extensions init my-first-extension
-cd my-first-extension
-```
-
-This creates the following structure:
-
-```
-my-first-extension/
-├── extension.json          # Extension metadata
-├── frontend/              # Frontend code
-│   ├── src/
-│   │   └── index.tsx     # Main entry point
-│   ├── package.json
-│   └── webpack.config.js
-├── backend/              # Backend code (optional)
-│   ├── src/
-│   └── requirements.txt
-└── README.md
-```
-
-### 3. Configure Your Extension
-
-Edit `extension.json` to define your extension's capabilities:
-
-```json
-{
-  "name": "my-first-extension",
-  "version": "1.0.0",
-  "description": "My first Superset extension",
-  "author": "Your Name",
-  "frontend": {
-    "contributions": {
-      "views": {
-        "sqllab.panels": [
-          {
-            "id": "my-extension.main",
-            "name": "My Panel",
-            "icon": "ToolOutlined"
-          }
-        ]
-      }
-    }
-  }
-}
-```
-
-### 4. Develop Your Extension
-
-Edit `frontend/src/index.tsx` to implement your extension:
-
-```typescript
-import React from 'react';
-import { ExtensionContext } from '@apache-superset/core';
-
-export function activate(context: ExtensionContext) {
-  // Register your panel component
-  const panel = context.core.registerView('my-extension.main', () => (
-    <div style={{ padding: 20 }}>
-      <h2>Hello from My Extension!</h2>
-      <p>This is my first Superset extension.</p>
-    </div>
-  ));
-
-  // Clean up on deactivation
-  context.subscriptions.push(panel);
-}
-
-export function deactivate() {
-  // Cleanup code if needed
-}
-```
-
-### 5. Test Locally
-
-Enable development mode in your Superset configuration:
-
-```python
-# superset_config.py
-ENABLE_EXTENSIONS = True
-LOCAL_EXTENSIONS = [
-    "/path/to/my-first-extension"
-]
-```
-
-Run the development server:
-
-```bash
-# In your extension directory
-superset-extensions dev
-
-# In a separate terminal, start Superset
-superset run -p 8088 --with-threads --reload
-```
-
-Your extension will now appear in SQL Lab!
-
-### 6. Build and Package
-
-When ready to distribute your extension:
-
-```bash
-superset-extensions build
-superset-extensions bundle
-```
-
-This creates a `my-first-extension-1.0.0.supx` file that can be uploaded to any Superset instance.
-
-### 7. Deploy
-
-Upload your extension via the Superset UI or API:
-
-```bash
-curl -X POST http://localhost:8088/api/v1/extensions/import/ \
-  -H "Authorization: Bearer YOUR_TOKEN" \
-  -F "file=@my-first-extension-1.0.0.supx"
-```
-
-## What's Next?
-
-Now that you have a basic extension working, explore:
-
-- [Extension Architecture](../architecture/overview) - Understand how extensions work
-- [API Reference](../api/frontend) - Learn about available APIs
-- [Examples](../examples) - See more complex extension examples
-- [Best Practices](./best-practices) - Learn extension development best practices
-
-## Common Patterns
-
-### Adding a SQL Lab Panel
-
-```typescript
-const panel = context.core.registerView('my-extension.panel', () => (
-  <MyPanelComponent />
-));
-```
-
-### Registering Commands
-
-```typescript
-const command = context.commands.registerCommand('my-extension.run', {
-  title: 'Run My Command',
-  execute: () => {
-    // Command logic
-  }
-});
-```
-
-### Listening to Events
-
-```typescript
-const listener = context.sqlLab.onDidQueryRun((query) => {
-  console.log('Query executed:', query);
-});
-```
-
-### Adding Menu Items
-
-```json
-{
-  "menus": {
-    "sqllab.editor": {
-      "primary": [{
-        "command": "my-extension.run",
-        "when": "editorHasSelection"
-      }]
-    }
-  }
-}
-```
-
-## Troubleshooting
-
-### Extension Not Loading
-
-- Ensure `ENABLE_EXTENSIONS = True` in your config
-- Check the browser console for errors
-- Verify the extension path in `LOCAL_EXTENSIONS`
-
-### Module Not Found Errors
-
-- Run `npm install` in the frontend directory
-- Check that `@apache-superset/core` is properly externalized
-
-### Build Failures
-
-- Ensure all dependencies are installed
-- Check webpack.config.js for proper Module Federation setup
-- Verify extension.json is valid JSON
-
-## Get Help
-
-- Join the [Superset Slack](https://join.slack.com/t/apache-superset/shared_invite/zt-16jvzmoi8-sI1TY1Pm~y_RnSiUAN0jqQ)
-- Ask questions on [GitHub Discussions](https://github.com/apache/superset/discussions)
-- Report issues on [GitHub Issues](https://github.com/apache/superset/issues)

docs/developer_portal/index.md

@@ -1,126 +0,0 @@
----
-title: Developer Portal
-sidebar_position: 1
-hide_title: true
----
-
-<!--
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
--->
-
-# Superset Developer Portal
-
-Welcome to the Apache Superset Developer Portal! This is your comprehensive guide to extending and customizing Superset through our new extension architecture.
-
-## What are Superset Extensions?
-
-Superset Extensions provide a powerful way to enhance and customize Apache Superset without modifying the core codebase. Following the successful model pioneered by VS Code, our extension architecture enables developers to:
-
-- **Add custom features** to SQL Lab and other Superset modules
-- **Create reusable components** that can be shared across organizations
-- **Integrate external tools** and services seamlessly
-- **Customize workflows** to match your team's specific needs
-
-## Why Extensions?
-
-As Superset has grown, we've recognized the need for a more modular architecture that allows:
-
-- **Innovation without fragmentation** - Build features without forking the codebase
-- **Community-driven development** - Share and reuse extensions across organizations
-- **Stable APIs** - Develop against versioned, well-documented interfaces
-- **Rapid iteration** - Deploy custom features without waiting for core releases
-
-## Key Features
-
-### 🎯 Well-Defined Extension Points
-
-Extensions can contribute to specific areas of Superset:
-- SQL Lab panels (left, right, bottom, editor)
-- Custom commands and menu items
-- Status bar components
-- API endpoints and backend functionality
-
-### 🔧 Modern Development Experience
-
-- **CLI tools** for scaffolding, building, and packaging
-- **Hot reloading** during development
-- **TypeScript support** with full type safety
-- **Module Federation** for dynamic loading
-
-### 📦 Simple Distribution
-
-- Package extensions as `.supx` files
-- Upload via REST API or UI
-- Automatic activation and lifecycle management
-- Version compatibility checking
-
-## Getting Started
-
-Ready to build your first extension? Check out our [Getting Started Guide](./getting-started) to:
-
-1. Set up your development environment
-2. Create your first extension
-3. Test it locally
-4. Package and deploy it
-
-## Architecture Overview
-
-Our extension architecture is built on several key principles:
-
-- **Lean Core**: Keep Superset's core minimal and delegate features to extensions
-- **Explicit APIs**: Clear, versioned interfaces for extension interactions
-- **Lazy Loading**: Extensions load only when needed for optimal performance
-- **Security First**: Extensions run with appropriate permissions and sandboxing
-
-Learn more in our [Architecture Documentation](./architecture/overview).
-
-## Current Status
-
-The extension architecture is currently in active development. The initial focus is on SQL Lab extensions, with plans to expand to:
-
-- Dashboard extensions
-- Chart plugins (enhanced from current system)
-- Database connectors
-- Security providers
-
-## Example: Dataset References Extension
-
-See the extension system in action with our Dataset References example, which adds a SQL Lab panel showing:
-
-- Tables referenced in queries
-- Table owners for permission requests  
-- Last available partitions
-- Estimated row counts
-
-## Join the Community
-
-- **Contribute**: Help shape the future of Superset extensions
-- **Share**: Publish your extensions for others to use
-- **Learn**: Explore extensions built by the community
-
-## Quick Links
-
-- [Getting Started Guide](./getting-started)
-- [Extension Architecture](./architecture/overview)
-- [API Reference](./api/frontend)
-- [CLI Documentation](./cli/overview)
-- [Examples](./examples)
-
----
-
-*The Superset extension architecture is inspired by the successful model of VS Code Extensions, bringing similar flexibility and power to the data exploration domain.*

docs/developer_portal/sidebars.js

@@ -1,59 +0,0 @@
-/**
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-module.exports = {
-  developerPortalSidebar: [
-    'index',
-    {
-      type: 'category',
-      label: 'Getting Started',
-      items: [
-        'getting-started/index',
-      ],
-    },
-    {
-      type: 'category',
-      label: 'Architecture',
-      items: [
-        'architecture/overview',
-      ],
-    },
-    {
-      type: 'category',
-      label: 'API Reference',
-      items: [
-        'api/frontend',
-      ],
-    },
-    {
-      type: 'category',
-      label: 'CLI',
-      items: [
-        'cli/overview',
-      ],
-    },
-    {
-      type: 'category',
-      label: 'Examples',
-      items: [
-        'examples/index',
-      ],
-    },
-  ],
-};

docs/developer_portal/versions.json

@@ -1 +0,0 @@
-[]

docs/developer_portal_versions.json

@@ -1 +0,0 @@
-[]

docs/docs/configuration/alerts-reports.mdx

@@ -12,7 +12,7 @@ Users can configure automated alerts and reports to send dashboards or charts to
 - *Alerts* are sent when a SQL condition is reached
 - *Reports* are sent on a schedule
 
-Alerts and reports are disabled by default. To turn them on, you'll need to change configuration settings and install a suitable headless browser in your environment.
+Alerts and reports are disabled by default. To turn them on, you need to do some setup, described here.
 
 ## Requirements
 
@@ -35,14 +35,16 @@ Screenshots will be taken but no messages actually sent as long as `ALERT_REPORT
 
 #### In your `Dockerfile`
 
-You'll need to extend the Superset image to include a headless browser. Your options include:
-- Use Playwright with Chrome: this is the recommended approach as of version >=4.1.x. A working example of a Dockerfile that installs these tools is provided under “Building your own production Docker image” on the [Docker Builds](/docs/installation/docker-builds#building-your-own-production-docker-image) page. Read the code comments there as you'll also need to change a feature flag in your config.
-- Use Firefox: you'll need to install geckodriver and Firefox.
-- Use Chrome without Playwright: you'll need to install Chrome and set the value of `WEBDRIVER_TYPE` to `"chrome"` in your `superset_config.py`.
+- You must install a headless browser, for taking screenshots of the charts and dashboards. Only Firefox and Chrome are currently supported.
+  > If you choose Chrome, you must also change the value of `WEBDRIVER_TYPE` to `"chrome"` in your `superset_config.py`.
 
-In Superset versions <=4.0x, users installed Firefox or Chrome and that was documented here.
+Note: All the components required (Firefox headless browser, Redis, Postgres db, celery worker and celery beat) are present in the *dev* docker image if you are following [Installing Superset Locally](/docs/installation/docker-compose/).
+All you need to do is add the required config variables described in this guide (See `Detailed Config`).
 
-Only the worker container needs the browser.
+If you are running a non-dev docker image, e.g., a stable release like `apache/superset:3.1.0`, that image does not include a headless browser.  Only the `superset_worker` container needs this headless browser to browse to the target chart or dashboard.
+You can either install and configure the headless browser - see "Custom Dockerfile" section below - or when deploying via `docker compose`, modify your `docker-compose.yml` file to use a dev image for the worker container and a stable release image for the `superset_app` container.
+
+*Note*: In this context, a "dev image" is the same application software as its corresponding non-dev image, just bundled with additional tools.  So an image like `3.1.0-dev` is identical to `3.1.0` when it comes to stability, functionality, and running in production.  The actual "in-development" versions of Superset - cutting-edge and unstable - are not tagged with version numbers on Docker Hub and will display version `0.0.0-dev` within the Superset UI.
 
 ### Slack integration
 
@@ -150,8 +152,8 @@ SMTP_MAIL_FROM = "noreply@youremail.com"
 EMAIL_REPORTS_SUBJECT_PREFIX = "[Superset] " # optional - overwrites default value in config.py of "[Report] "
 
 # WebDriver configuration
-# If you use Firefox or Playwright with Chrome, you can stick with default values
-# If you use Chrome and are *not* using Playwright, then add the following WEBDRIVER_TYPE and WEBDRIVER_OPTION_ARGS
+# If you use Firefox, you can stick with default values
+# If you use Chrome, then add the following WEBDRIVER_TYPE and WEBDRIVER_OPTION_ARGS
 WEBDRIVER_TYPE = "chrome"
 WEBDRIVER_OPTION_ARGS = [
     "--force-device-scale-factor=2.0",
@@ -217,6 +219,62 @@ def alert_dynamic_minimal_interval(**kwargs) -> int:
 ALERT_MINIMUM_INTERVAL = alert_dynamic_minimal_interval
 ```
 
+## Custom Dockerfile
+
+If you're running the dev version of a released Superset image, like `apache/superset:3.1.0-dev`, you should be set with the above.
+
+But if you're building your own image, or starting with a non-dev version, a webdriver (and headless browser) is needed to capture screenshots of the charts and dashboards which are then sent to the recipient.
+Here's how you can modify your Dockerfile to take the screenshots either with Firefox or Chrome.
+
+### Using Firefox
+
+```docker
+FROM apache/superset:3.1.0
+
+USER root
+
+RUN apt-get update && \
+    apt-get install --no-install-recommends -y firefox-esr
+
+ENV GECKODRIVER_VERSION=0.29.0
+RUN wget -q https://github.com/mozilla/geckodriver/releases/download/v${GECKODRIVER_VERSION}/geckodriver-v${GECKODRIVER_VERSION}-linux64.tar.gz && \
+    tar -x geckodriver -zf geckodriver-v${GECKODRIVER_VERSION}-linux64.tar.gz -O > /usr/bin/geckodriver && \
+    chmod 755 /usr/bin/geckodriver && \
+    rm geckodriver-v${GECKODRIVER_VERSION}-linux64.tar.gz
+
+RUN pip install --no-cache gevent psycopg2 redis
+
+USER superset
+```
+
+### Using Chrome
+
+```docker
+FROM apache/superset:3.1.0
+
+USER root
+
+RUN apt-get update && \
+    apt-get install -y wget zip libaio1
+
+RUN export CHROMEDRIVER_VERSION=$(curl --silent https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_116) && \
+    wget -O google-chrome-stable_current_amd64.deb -q http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_${CHROMEDRIVER_VERSION}-1_amd64.deb && \
+    apt-get install -y --no-install-recommends ./google-chrome-stable_current_amd64.deb && \
+    rm -f google-chrome-stable_current_amd64.deb
+
+RUN export CHROMEDRIVER_VERSION=$(curl --silent https://googlechromelabs.github.io/chrome-for-testing/LATEST_RELEASE_116) && \
+    wget -q https://storage.googleapis.com/chrome-for-testing-public/${CHROMEDRIVER_VERSION}/linux64/chromedriver-linux64.zip && \
+    unzip -j chromedriver-linux64.zip -d /usr/bin && \
+    chmod 755 /usr/bin/chromedriver && \
+    rm -f chromedriver-linux64.zip
+
+RUN pip install --no-cache gevent psycopg2 redis
+
+USER superset
+```
+
+Don't forget to set `WEBDRIVER_TYPE` and `WEBDRIVER_OPTION_ARGS` in your config if you use Chrome.
+
 ## Troubleshooting
 
 There are many reasons that reports might not be working.  Try these steps to check for specific issues.
@@ -235,7 +293,9 @@ This is the best source of information about the problem.  In a docker compose d
 
 To take a screenshot, the worker visits the dashboard or chart using a headless browser, then takes a screenshot. If you are able to send a chart as CSV or text but can't send as PNG, your problem may lie with the browser.
 
-If you are handling the installation of the headless browser on your own, do your own verification to ensure that the headless browser opens successfully in the worker environment.
+Superset docker images that have a tag ending with `-dev` have the Firefox headless browser and geckodriver already installed. You can test that these are installed and in the proper path by entering your Superset worker and running `firefox --headless` and then `geckodriver`. Both commands should start those applications.
+
+If you are handling the installation of that software on your own, or wish to use Chromium instead, do your own verification to ensure that the headless browser opens successfully in the worker environment.
 
 ### Send a test email
 

docs/docs/configuration/theming.mdx

@@ -13,9 +13,9 @@ apache-superset>=6.0
 Superset now rides on **Ant Design v5's token-based theming**.
 Every Antd token works, plus a handful of Superset-specific ones for charts and dashboard chrome.
 
-## Managing Themes via UI
+## Managing Themes via CRUD Interface
 
-Superset includes a built-in **Theme Management** interface accessible from the admin menu under **Settings > Themes**.
+Superset now includes a built-in **Theme Management** interface accessible from the admin menu under **Settings > Themes**.
 
 ### Creating a New Theme
 
@@ -29,38 +29,22 @@ Superset includes a built-in **Theme Management** interface accessible from the
 
 You can also extend with Superset-specific tokens (documented in the default theme object) before you import.
 
-### System Theme Administration
-
-When `ENABLE_UI_THEME_ADMINISTRATION = True` is configured, administrators can manage system-wide themes directly from the UI:
-
-#### Setting System Themes
-- **System Default Theme**: Click the sun icon on any theme to set it as the system-wide default
-- **System Dark Theme**: Click the moon icon on any theme to set it as the system dark mode theme
-- **Automatic OS Detection**: When both default and dark themes are set, Superset automatically detects and applies the appropriate theme based on OS preferences
-
-#### Managing System Themes
-- System themes are indicated with special badges in the theme list
-- Only administrators with write permissions can modify system theme settings
-- Removing a system theme designation reverts to configuration file defaults
-
 ### Applying Themes to Dashboards
 
 Once created, themes can be applied to individual dashboards:
 - Edit any dashboard and select your custom theme from the theme dropdown
 - Each dashboard can have its own theme, allowing for branded or context-specific styling
 
-## Configuration Options
+## Alternative: Instance-wide Configuration
 
-### Python Configuration
+For system-wide theming, you can configure default themes via Python configuration:
 
-Configure theme behavior via `superset_config.py`:
+### Setting Default Themes
 
 ```python
-# Enable UI-based theme administration for admins
-ENABLE_UI_THEME_ADMINISTRATION = True
+# superset_config.py
 
-# Optional: Set initial default themes via configuration
-# These can be overridden via the UI when ENABLE_UI_THEME_ADMINISTRATION = True
+# Default theme (light mode)
 THEME_DEFAULT = {
     "token": {
         "colorPrimary": "#2893B3",
@@ -69,7 +53,7 @@ THEME_DEFAULT = {
     }
 }
 
-# Optional: Dark theme configuration
+# Dark theme configuration
 THEME_DARK = {
     "algorithm": "dark",
     "token": {
@@ -78,28 +62,23 @@ THEME_DARK = {
     }
 }
 
-# To force a single theme on all users, set THEME_DARK = None
-# When both themes are defined (via UI or config):
-# - Users can manually switch between themes
-# - OS preference detection is automatically enabled
+# Theme behavior settings
+THEME_SETTINGS = {
+    "enforced": False,          # If True, forces default theme always
+    "allowSwitching": True,     # Allow users to switch between themes
+    "allowOSPreference": True,  # Auto-detect system theme preference
+}
 ```
 
-### Migration from Configuration to UI
+### Copying Themes from CRUD Interface
 
-When `ENABLE_UI_THEME_ADMINISTRATION = True`:
+To use a theme created via the CRUD interface as your system default:
 
-1. System themes set via the UI take precedence over configuration file settings
-2. The UI shows which themes are currently set as system defaults
-3. Administrators can change system themes without restarting Superset
-4. Configuration file themes serve as fallbacks when no UI themes are set
+1. Navigate to **Settings > Themes** and edit your desired theme
+2. Copy the complete JSON configuration from the theme definition field
+3. Paste it directly into your `superset_config.py` as shown above
 
-### Copying Themes Between Systems
-
-To export a theme for use in configuration files or another instance:
-
-1. Navigate to **Settings > Themes** and click the export icon on your desired theme
-2. Extract the JSON configuration from the exported YAML file
-3. Use this JSON in your `superset_config.py` or import it into another Superset instance
+Restart Superset to apply changes.
 
 ## Theme Development Workflow
 
@@ -108,85 +87,8 @@ To export a theme for use in configuration files or another instance:
 3. **Apply**: Assign themes to specific dashboards or configure instance-wide
 4. **Iterate**: Modify theme JSON directly in the CRUD interface or re-import from the theme editor
 
-## Custom Fonts
-
-Superset supports custom fonts through runtime configuration, allowing you to use branded or custom typefaces without rebuilding the application.
-
-### Configuring Custom Fonts
-
-Add font URLs to your `superset_config.py`:
-
-```python
-# Load fonts from Google Fonts, Adobe Fonts, or self-hosted sources
-CUSTOM_FONT_URLS = [
-    "https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap",
-    "https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@400;500&display=swap",
-]
-
-# Update CSP to allow font sources
-TALISMAN_CONFIG = {
-    "content_security_policy": {
-        "font-src": ["'self'", "https://fonts.googleapis.com", "https://fonts.gstatic.com"],
-        "style-src": ["'self'", "'unsafe-inline'", "https://fonts.googleapis.com"],
-    }
-}
-```
-
-### Using Custom Fonts in Themes
-
-Once configured, reference the fonts in your theme configuration:
-
-```python
-THEME_DEFAULT = {
-    "token": {
-        "fontFamily": "Inter, -apple-system, BlinkMacSystemFont, sans-serif",
-        "fontFamilyCode": "JetBrains Mono, Monaco, monospace",
-        # ... other theme tokens
-    }
-}
-```
-
-Or in the CRUD interface theme JSON:
-
-```json
-{
-  "token": {
-    "fontFamily": "Inter, -apple-system, BlinkMacSystemFont, sans-serif",
-    "fontFamilyCode": "JetBrains Mono, Monaco, monospace"
-  }
-}
-```
-
-### Font Sources
-
-- **Google Fonts**: Free, CDN-hosted fonts with wide variety
-- **Adobe Fonts**: Premium fonts (requires subscription and kit ID)
-- **Self-hosted**: Place font files in `/static/assets/fonts/` and reference via CSS
-
-This feature works with the stock Docker image - no custom build required!
-
 ## Advanced Features
 
-- **System Themes**: Manage system-wide default and dark themes via UI or configuration
+- **System Themes**: Superset includes built-in light and dark themes
 - **Per-Dashboard Theming**: Each dashboard can have its own visual identity
 - **JSON Editor**: Edit theme configurations directly within Superset's interface
-- **Custom Fonts**: Load external fonts via configuration without rebuilding
-- **OS Dark Mode Detection**: Automatically switches themes based on system preferences
-- **Theme Import/Export**: Share themes between instances via YAML files
-
-## API Access
-
-For programmatic theme management, Superset provides REST endpoints:
-
-- `GET /api/v1/theme/` - List all themes
-- `POST /api/v1/theme/` - Create a new theme
-- `PUT /api/v1/theme/{id}` - Update a theme
-- `DELETE /api/v1/theme/{id}` - Delete a theme
-- `PUT /api/v1/theme/{id}/set_system_default` - Set as system default theme (admin only)
-- `PUT /api/v1/theme/{id}/set_system_dark` - Set as system dark theme (admin only)
-- `DELETE /api/v1/theme/unset_system_default` - Remove system default designation
-- `DELETE /api/v1/theme/unset_system_dark` - Remove system dark designation
-- `GET /api/v1/theme/export/` - Export themes as YAML
-- `POST /api/v1/theme/import/` - Import themes from YAML
-
-These endpoints require appropriate permissions and are subject to RBAC controls.

docs/docs/contributing/development.mdx

@@ -137,7 +137,7 @@ contributing to Apache Superset more accessible to developers worldwide.
 
 1. **Create a Codespace**: Use this pre-configured link that sets up everything you need:
 
-   [**Launch Superset Codespace →**](https://github.com/codespaces/new?skip_quickstart=true&machine=standardLinux32gb&repo=39464018&ref=master&devcontainer_path=.devcontainer%2Fdevcontainer.json&geo=UsWest)
+   [**Launch Superset Codespace →**](https://github.com/codespaces/new?skip_quickstart=true&machine=standardLinux32gb&repo=39464018&ref=codespaces&geo=UsWest&devcontainer_path=.devcontainer%2Fdevcontainer.json)
 
    :::caution
    **Important**: You must select at least the **4 CPU / 16GB RAM** machine type (pre-selected in the link above).
@@ -421,6 +421,14 @@ Then make sure you run your WSGI server using the right worker type:
 gunicorn "superset.app:create_app()" -k "geventwebsocket.gunicorn.workers.GeventWebSocketWorker" -b 127.0.0.1:8088 --reload
 ```
 
+You can log anything to the browser console, including objects:
+
+```python
+from superset import app
+app.logger.error('An exception occurred!')
+app.logger.info(form_data)
+```
+
 ### Frontend
 
 Frontend assets (TypeScript, JavaScript, CSS, and images) must be compiled in order to properly display the web UI. The `superset-frontend` directory contains all NPM-managed frontend assets. Note that for some legacy pages there are additional frontend assets bundled with Flask-Appbuilder (e.g. jQuery and bootstrap). These are not managed by NPM and may be phased out in the future.
@@ -747,26 +755,6 @@ To run a single test file:
 npm run test -- path/to/file.js
 ```
 
-#### Known Issues and Workarounds
-
-**Jest Test Hanging (MessageChannel Issue)**
-
-If Jest tests hang with "Jest did not exit one second after the test run has completed", this is likely due to the MessageChannel issue from rc-overflow (Ant Design v5 components).
-
-**Root Cause**: `rc-overflow@1.4.1` creates MessageChannel handles for responsive overflow detection that remain open after test completion.
-
-**Current Workaround**: MessageChannel is mocked as undefined in `spec/helpers/jsDomWithFetchAPI.ts`, forcing rc-overflow to use requestAnimationFrame fallback.
-
-**To verify if still needed**: Remove the MessageChannel mocking lines and run `npm test -- --shard=4/8`. If tests hang, the workaround is still required.
-
-**Future removal conditions**: This workaround can be removed when:
-- rc-overflow updates to properly clean up MessagePorts in test environments
-- Jest updates to handle MessageChannel/MessagePort cleanup better
-- Ant Design switches away from rc-overflow
-- We switch away from Ant Design v5
-
-**See**: [PR #34871](https://github.com/apache/superset/pull/34871) for full technical details.
-
 ### Debugging Server App
 
 #### Local

docs/docs/installation/docker-builds.mdx

@@ -86,6 +86,8 @@ USER root
 ENV PLAYWRIGHT_BROWSERS_PATH=/usr/local/share/playwright-browsers
 
 # Install packages using uv into the virtual environment
+# Superset started using uv after the 4.1 branch; if you are building from apache/superset:4.1.x or an older version,
+# replace the first two lines with RUN pip install \
 RUN . /app/.venv/bin/activate && \
     uv pip install \
     # install psycopg2 for using PostgreSQL metadata store - could be a MySQL package if using that backend:

docs/docs/mcp-service/api-reference.mdx

@@ -0,0 +1,741 @@
+---
+title: API Reference
+sidebar_position: 3
+version: 1
+---
+
+# MCP Tools API Reference
+
+Complete reference for all 16 MCP tools with request/response examples.
+
+> 🚀 **First time here?** Start with [Dashboard Tools](#dashboard-tools) or [Chart Tools](#chart-tools) to see the most commonly used features.
+>
+> 🔐 **Need authentication?** See the [Authentication Guide](./authentication) for JWT setup.
+>
+> 🔧 **Want to add tools?** Check the [Development Guide](./development#adding-new-tools) for step-by-step instructions.
+
+## Dashboard Tools
+
+### list_dashboards
+
+List dashboards with search, filtering, and pagination support.
+
+**Request Schema:**
+```json
+{
+  "search": "sales",              // Optional: Search term
+  "filters": [                    // Optional: Advanced filters
+    {
+      "col": "published",
+      "opr": "eq",
+      "value": true
+    }
+  ],
+  "page": 1,                      // Optional: Page number (default: 1)
+  "page_size": 20,                // Optional: Items per page (default: 20)
+  "select_columns": [             // Optional: Specific columns
+    "id", "dashboard_title", "uuid"
+  ],
+  "use_cache": true               // Optional: Use cached data (default: true)
+}
+```
+
+**Response Example:**
+```json
+{
+  "dashboards": [
+    {
+      "id": 1,
+      "uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+      "dashboard_title": "Sales Performance",
+      "url": "/superset/dashboard/1/",
+      "published": true,
+      "owners": ["admin"],
+      "created_on": "2024-01-15T10:30:00Z",
+      "changed_on": "2024-01-20T14:15:00Z"
+    }
+  ],
+  "total_count": 45,
+  "page": 1,
+  "page_size": 20,
+  "cache_status": {
+    "cache_hit": true,
+    "cache_age_seconds": 300
+  }
+}
+```
+
+### get_dashboard_info
+
+Get detailed information about a specific dashboard.
+
+**Request Schema:**
+```json
+{
+  "identifier": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",  // ID, UUID, or slug
+  "use_cache": true
+}
+```
+
+**Response Example:**
+```json
+{
+  "dashboard_id": 1,
+  "uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+  "dashboard_title": "Sales Performance Dashboard",
+  "slug": "sales-performance",
+  "url": "/superset/dashboard/1/",
+  "published": true,
+  "owners": ["admin", "analyst"],
+  "roles": ["Sales Team"],
+  "charts": [
+    {
+      "id": 10,
+      "slice_name": "Monthly Revenue",
+      "viz_type": "line"
+    },
+    {
+      "id": 11,
+      "slice_name": "Regional Sales",
+      "viz_type": "bar"
+    }
+  ],
+  "filters": [
+    {
+      "column": "region",
+      "type": "select"
+    }
+  ],
+  "created_on": "2024-01-15T10:30:00Z",
+  "changed_on": "2024-01-20T14:15:00Z"
+}
+```
+
+### generate_dashboard
+
+Create a new dashboard with multiple charts.
+
+**Request Schema:**
+```json
+{
+  "chart_ids": [10, 11, 12, 13],
+  "dashboard_title": "Q4 Performance Dashboard",
+  "description": "Quarterly performance metrics and KPIs",
+  "published": true,
+  "layout_type": "grid"          // Optional: "grid" or "tabs"
+}
+```
+
+**Response Example:**
+```json
+{
+  "dashboard_id": 25,
+  "uuid": "new-dash-uuid-here",
+  "dashboard_title": "Q4 Performance Dashboard",
+  "url": "/superset/dashboard/25/",
+  "charts_added": 4,
+  "layout": {
+    "type": "grid",
+    "columns": 2,
+    "rows": 2
+  },
+  "created_on": "2024-01-25T16:45:00Z"
+}
+```
+
+## Chart Tools
+
+### list_charts
+
+List charts with advanced filtering and search capabilities.
+
+**Request Schema:**
+```json
+{
+  "search": "revenue",
+  "filters": [
+    {
+      "col": "viz_type",
+      "opr": "in",
+      "value": ["line", "bar", "area"]
+    }
+  ],
+  "page": 1,
+  "page_size": 25,
+  "select_columns": ["id", "slice_name", "viz_type", "uuid"],
+  "use_cache": true
+}
+```
+
+**Response Example:**
+```json
+{
+  "charts": [
+    {
+      "id": 10,
+      "uuid": "chart-uuid-1",
+      "slice_name": "Monthly Revenue Trend",
+      "viz_type": "line",
+      "datasource_name": "sales_data",
+      "owners": ["admin"],
+      "created_on": "2024-01-10T09:15:00Z"
+    }
+  ],
+  "total_count": 125,
+  "page": 1,
+  "page_size": 25
+}
+```
+
+### get_chart_info
+
+Get comprehensive chart information including configuration.
+
+**Request Schema:**
+```json
+{
+  "identifier": 10,                // ID or UUID
+  "include_form_data": true,       // Include chart configuration
+  "use_cache": true
+}
+```
+
+**Response Example:**
+```json
+{
+  "chart_id": 10,
+  "uuid": "chart-uuid-1",
+  "slice_name": "Monthly Revenue Trend",
+  "viz_type": "line",
+  "datasource_id": 5,
+  "datasource_name": "sales_data",
+  "datasource_type": "table",
+  "form_data": {
+    "viz_type": "line",
+    "x_axis": "month",
+    "metrics": ["sum__revenue"],
+    "time_range": "Last 12 months"
+  },
+  "query_context": {
+    "datasource": {"id": 5, "type": "table"},
+    "queries": [{"columns": [], "metrics": ["sum__revenue"]}]
+  },
+  "explore_url": "/superset/explore/?form_data=%7B%22slice_id%22%3A10%7D",
+  "owners": ["admin"],
+  "created_on": "2024-01-10T09:15:00Z",
+  "changed_on": "2024-01-15T11:30:00Z"
+}
+```
+
+### generate_chart
+
+Create a new chart with specified configuration.
+
+**Request Schema:**
+```json
+{
+  "dataset_id": "5",
+  "config": {
+    "chart_type": "xy",
+    "x": {"name": "month", "label": "Month"},
+    "y": [
+      {
+        "name": "revenue",
+        "aggregate": "SUM",
+        "label": "Total Revenue"
+      },
+      {
+        "name": "orders",
+        "aggregate": "COUNT",
+        "label": "Order Count"
+      }
+    ],
+    "kind": "line",
+    "x_axis": {
+      "title": "Month",
+      "format": "smart_date"
+    },
+    "y_axis": {
+      "title": "Revenue ($)",
+      "format": "$,.0f"
+    },
+    "legend": {
+      "show": true,
+      "position": "top"
+    }
+  },
+  "slice_name": "Revenue and Orders Trend",
+  "description": "Monthly revenue and order count comparison",
+  "save_chart": true,
+  "generate_preview": true,
+  "preview_formats": ["url", "ascii"]
+}
+```
+
+**Response Example:**
+```json
+{
+  "chart_id": 45,
+  "uuid": "new-chart-uuid",
+  "slice_name": "Revenue and Orders Trend",
+  "viz_type": "echarts_timeseries_line",
+  "datasource_id": 5,
+  "explore_url": "/superset/explore/?form_data=%7B%22slice_id%22%3A45%7D",
+  "query_executed": true,
+  "query_result": {
+    "status": "success",
+    "row_count": 12,
+    "execution_time": 0.145
+  },
+  "preview": {
+    "url": {
+      "preview_url": "http://localhost:5008/screenshot/chart/45.png",
+      "width": 800,
+      "height": 600
+    },
+    "ascii": {
+      "ascii_content": "Revenue Trend\n==============\nJan |████████████████ $125K\nFeb |██████████████████ $140K\n...",
+      "width": 80,
+      "height": 20
+    }
+  },
+  "created_on": "2024-01-25T14:20:00Z"
+}
+```
+
+### get_chart_data
+
+Export chart data in multiple formats.
+
+**Request Schema:**
+```json
+{
+  "identifier": 10,
+  "format": "json",               // "json", "csv", "excel"
+  "limit": 1000,                  // Optional: Row limit
+  "offset": 0,                    // Optional: Row offset
+  "filters": [                    // Optional: Additional filters
+    {
+      "column": "region",
+      "op": "=",
+      "value": "US"
+    }
+  ],
+  "use_cache": true,
+  "force_refresh": false
+}
+```
+
+**Response Example:**
+```json
+{
+  "data": [
+    {
+      "month": "2024-01",
+      "revenue": 125000,
+      "orders": 450
+    },
+    {
+      "month": "2024-02",
+      "revenue": 140000,
+      "orders": 520
+    }
+  ],
+  "total_rows": 12,
+  "columns": [
+    {"name": "month", "type": "DATE"},
+    {"name": "revenue", "type": "BIGINT"},
+    {"name": "orders", "type": "BIGINT"}
+  ],
+  "query": {
+    "sql": "SELECT month, SUM(revenue) as revenue, COUNT(*) as orders FROM sales_data GROUP BY month ORDER BY month",
+    "execution_time": 0.089
+  },
+  "cache_status": {
+    "cache_hit": false,
+    "cache_type": "query",
+    "refreshed": true
+  }
+}
+```
+
+### get_chart_preview
+
+Generate chart previews in multiple formats.
+
+**Request Schema:**
+```json
+{
+  "identifier": 10,
+  "format": "url",                // "url", "base64", "ascii", "table"
+  "width": 800,                   // For image formats
+  "height": 600,                  // For image formats
+  "ascii_width": 80,              // For ASCII format
+  "ascii_height": 20,             // For ASCII format
+  "use_cache": true
+}
+```
+
+**Response Examples:**
+
+**URL Format:**
+```json
+{
+  "format": "url",
+  "preview_url": "http://localhost:5008/screenshot/chart/10.png",
+  "width": 800,
+  "height": 600,
+  "supports_interaction": false,
+  "expires_at": "2024-01-26T14:20:00Z"
+}
+```
+
+**ASCII Format:**
+```json
+{
+  "format": "ascii",
+  "ascii_content": "Monthly Revenue Trend\n=====================\n\nJan |████████████████████ $125K\nFeb |██████████████████████ $140K\nMar |███████████████████ $135K\nApr |█████████████████████████ $155K\n\nRange: $125K to $155K\n▁▃▂▅▇▆▄▃▂▄▅▆▇▅▃▂",
+  "width": 80,
+  "height": 20,
+  "supports_color": false
+}
+```
+
+**Table Format:**
+```json
+{
+  "format": "table",
+  "table_data": "Monthly Revenue Data\n====================\n\nMonth    | Revenue  | Orders\n---------|----------|--------\nJan 2024 | $125,000 |    450\nFeb 2024 | $140,000 |    520\nMar 2024 | $135,000 |    495\n\nTotal: 12 rows × 3 columns",
+  "row_count": 12,
+  "supports_sorting": true
+}
+```
+
+## Dataset Tools
+
+### list_datasets
+
+List available datasets with columns and metrics.
+
+**Request Schema:**
+```json
+{
+  "search": "sales",
+  "filters": [
+    {
+      "col": "is_active",
+      "opr": "eq",
+      "value": true
+    }
+  ],
+  "include_columns": true,        // Include column metadata
+  "include_metrics": true,        // Include metric metadata
+  "page": 1,
+  "page_size": 15
+}
+```
+
+**Response Example:**
+```json
+{
+  "datasets": [
+    {
+      "id": 1,
+      "uuid": "dataset-uuid-1",
+      "table_name": "sales_data",
+      "database_name": "main_warehouse",
+      "schema": "public",
+      "owners": ["admin"],
+      "columns": [
+        {
+          "column_name": "region",
+          "type": "VARCHAR",
+          "is_active": true,
+          "is_dttm": false
+        },
+        {
+          "column_name": "revenue",
+          "type": "DECIMAL",
+          "is_active": true,
+          "is_dttm": false
+        }
+      ],
+      "metrics": [
+        {
+          "metric_name": "sum__revenue",
+          "expression": "SUM(revenue)",
+          "metric_type": "sum"
+        }
+      ],
+      "created_on": "2024-01-05T08:00:00Z"
+    }
+  ],
+  "total_count": 23,
+  "page": 1,
+  "page_size": 15
+}
+```
+
+### get_dataset_info
+
+Get detailed dataset information with full column/metric metadata.
+
+**Request Schema:**
+```json
+{
+  "identifier": "dataset-uuid-1",  // ID or UUID
+  "include_columns": true,
+  "include_metrics": true,
+  "use_cache": true
+}
+```
+
+**Response Example:**
+```json
+{
+  "dataset_id": 1,
+  "uuid": "dataset-uuid-1",
+  "table_name": "sales_data",
+  "database_name": "main_warehouse",
+  "database_id": 1,
+  "schema": "public",
+  "sql": null,
+  "is_active": true,
+  "owners": ["admin", "data_team"],
+  "columns": [
+    {
+      "id": 101,
+      "column_name": "region",
+      "type": "VARCHAR",
+      "is_active": true,
+      "is_dttm": false,
+      "groupby": true,
+      "filterable": true,
+      "description": "Geographic region"
+    },
+    {
+      "id": 102,
+      "column_name": "order_date",
+      "type": "DATE",
+      "is_active": true,
+      "is_dttm": true,
+      "groupby": true,
+      "filterable": true
+    }
+  ],
+  "metrics": [
+    {
+      "id": 201,
+      "metric_name": "sum__revenue",
+      "expression": "SUM(revenue)",
+      "metric_type": "sum",
+      "is_active": true,
+      "description": "Total revenue"
+    }
+  ],
+  "created_on": "2024-01-05T08:00:00Z",
+  "changed_on": "2024-01-18T12:30:00Z"
+}
+```
+
+## System Tools
+
+### get_superset_instance_info
+
+Get Superset instance information and statistics.
+
+**Request Schema:**
+```json
+{
+  "include_statistics": true,     // Include usage statistics
+  "include_tools": true,          // Include available MCP tools
+  "use_cache": true
+}
+```
+
+**Response Example:**
+```json
+{
+  "version": "4.1.0",
+  "build": "apache-superset-4.1.0",
+  "mcp_service_version": "1.0.0",
+  "authentication": {
+    "enabled": true,
+    "type": "jwt_bearer",
+    "required_scopes": ["dashboard:read", "chart:read"]
+  },
+  "statistics": {
+    "dashboards": {
+      "total": 45,
+      "published": 32
+    },
+    "charts": {
+      "total": 125,
+      "by_viz_type": {
+        "line": 35,
+        "bar": 28,
+        "table": 42,
+        "pie": 20
+      }
+    },
+    "datasets": {
+      "total": 23,
+      "active": 18
+    },
+    "users": {
+      "total": 15,
+      "active": 12
+    }
+  },
+  "mcp_tools": [
+    {
+      "name": "list_dashboards",
+      "description": "List dashboards with search and filtering",
+      "category": "dashboard"
+    },
+    {
+      "name": "generate_chart",
+      "description": "Create new charts programmatically",
+      "category": "chart"
+    }
+  ],
+  "database_connections": [
+    {
+      "id": 1,
+      "database_name": "main_warehouse",
+      "backend": "postgresql",
+      "status": "healthy"
+    }
+  ],
+  "cache_status": {
+    "enabled": true,
+    "backend": "redis",
+    "hit_rate": 0.85
+  }
+}
+```
+
+### generate_explore_link
+
+Generate Superset explore URLs with pre-configured chart settings.
+
+**Request Schema:**
+```json
+{
+  "dataset_id": "1",
+  "chart_config": {
+    "viz_type": "line",
+    "x_axis": "month",
+    "metrics": ["sum__revenue"],
+    "time_range": "Last 6 months"
+  },
+  "title": "Revenue Analysis",
+  "cache_form_data": true
+}
+```
+
+**Response Example:**
+```json
+{
+  "explore_url": "/superset/explore/?form_data_key=abc123def456",
+  "full_url": "http://localhost:8088/superset/explore/?form_data_key=abc123def456",
+  "form_data_key": "abc123def456",
+  "expires_at": "2024-01-26T16:45:00Z",
+  "chart_config": {
+    "viz_type": "line",
+    "datasource": "1__table",
+    "x_axis": "month",
+    "metrics": ["sum__revenue"],
+    "time_range": "Last 6 months"
+  }
+}
+```
+
+## SQL Lab Tools
+
+### open_sql_lab_with_context
+
+Open SQL Lab with pre-configured database, schema, and SQL.
+
+**Request Schema:**
+```json
+{
+  "database_connection_id": 1,
+  "schema": "public",
+  "dataset_in_context": "sales_data",
+  "sql": "SELECT region, SUM(revenue) as total_revenue\nFROM sales_data \nWHERE order_date >= '2024-01-01'\nGROUP BY region\nORDER BY total_revenue DESC",
+  "title": "Regional Sales Analysis"
+}
+```
+
+**Response Example:**
+```json
+{
+  "sql_lab_url": "/superset/sqllab/?dbid=1&schema=public&sql_template=encoded_sql_here",
+  "full_url": "http://localhost:8088/superset/sqllab/?dbid=1&schema=public&sql_template=encoded_sql_here",
+  "database_connection": {
+    "id": 1,
+    "database_name": "main_warehouse",
+    "backend": "postgresql"
+  },
+  "schema": "public",
+  "sql_template": "SELECT region, SUM(revenue) as total_revenue...",
+  "context": {
+    "dataset": "sales_data",
+    "title": "Regional Sales Analysis"
+  }
+}
+```
+
+## Error Responses
+
+All tools can return error responses with this structure:
+
+```json
+{
+  "error": "Chart not found with identifier: 999",
+  "error_type": "NotFound",
+  "suggestions": [
+    "Verify the chart ID exists",
+    "Check if you have permission to access this chart",
+    "Try using the chart UUID instead of ID"
+  ],
+  "details": {
+    "identifier": 999,
+    "identifier_type": "id"
+  }
+}
+```
+
+## Cache Status
+
+Many responses include cache status information:
+
+```json
+{
+  "cache_status": {
+    "cache_hit": true,           // Data served from cache
+    "cache_type": "query",       // Type: query, metadata, form_data
+    "cache_age_seconds": 300,    // Age of cached data
+    "refreshed": false           // Whether cache was refreshed
+  }
+}
+```
+
+This API reference provides complete documentation for integrating with the Superset MCP service, including all request schemas, response formats, and error handling patterns.
+
+## What's Next?
+
+### 🔐 **Ready for Production?**
+Set up authentication and security with the [Authentication Guide](./authentication).
+
+### 🔧 **Want to Add More Tools?**
+Learn how to extend the MCP service in the [Development Guide](./development).
+
+### 🏗️ **Need Architecture Details?**
+Understand the system design in the [Architecture Overview](./architecture).
+
+### 🏢 **Enterprise Features?**
+Explore advanced capabilities in the [Preset Integration Guide](./preset-integration).
+
+> 📖 **Back to Documentation Index**: [MCP Service](./intro)

docs/docs/mcp-service/architecture.mdx

@@ -0,0 +1,191 @@
+---
+title: Architecture Overview
+sidebar_position: 5
+version: 1
+---
+
+# Architecture Overview
+
+The Superset Model Context Protocol (MCP) service provides a modular, schema-driven interface for programmatic access to Superset dashboards, charts, datasets, and instance metadata. Built on FastMCP for LLM agents and automation tools.
+
+**Status:** Phase 1 Complete. Core functionality stable, authentication production-ready. See [SIP-171](https://github.com/apache/superset/issues/33870) for roadmap.
+
+## Core Architecture
+
+### Tool Structure
+- **16 MCP tools** organized by domain: `dashboard/`, `chart/`, `dataset/`, `system/`
+- All tools decorated with `@mcp.tool` and `@mcp_auth_hook`
+- **Import inside functions**: All Superset DAOs/commands imported in function body to ensure proper app context
+- Pydantic v2 schemas with LLM/OpenAPI-compatible field descriptions
+
+### Request Schema Pattern
+Eliminates LLM parameter validation issues using structured request objects:
+```python
+# New approach - single request object
+get_dataset_info(request={"identifier": 123})  # ID
+get_dataset_info(request={"identifier": "uuid-string"})  # UUID
+
+# Old approach - replaced
+get_dataset_info(dataset_id=123)
+```
+
+### Multi-Identifier Support
+- **Charts/Datasets**: ID (numeric) or UUID (string)
+- **Dashboards**: ID (numeric), UUID (string), or slug (string)
+- Validation prevents conflicting parameters (search + filters)
+
+## Available Tools
+
+### Dashboard Tools (5)
+- `list_dashboards` - List with search/filters/pagination
+- `get_dashboard_info` - Get by ID/UUID/slug
+- `get_dashboard_available_filters` - Discover filterable columns
+- `generate_dashboard` - Create dashboards with multiple charts
+- `add_chart_to_existing_dashboard` - Add charts to existing dashboards
+
+### Chart Tools (8)
+- `list_charts` - List with search/filters/pagination
+- `get_chart_info` - Get by ID/UUID
+- `get_chart_available_filters` - Discover filterable columns
+- `generate_chart` - Create charts (table, line, bar, area, scatter)
+- `update_chart` - Update saved charts
+- `update_chart_preview` - Update cached previews
+- `get_chart_data` - Export data (JSON/CSV/Excel)
+- `get_chart_preview` - Screenshots, ASCII art, table previews
+
+### Dataset Tools (3)
+- `list_datasets` - List with columns/metrics
+- `get_dataset_info` - Get by ID/UUID with metadata
+- `get_dataset_available_filters` - Discover filterable columns
+
+### System Tools (2)
+- `get_superset_instance_info` - Instance statistics and version
+- `generate_explore_link` - Generate chart exploration URLs
+
+### SQL Lab Tools (1)
+- `open_sql_lab_with_context` - Pre-configured SQL Lab sessions
+
+## Authentication & Security
+
+### JWT Bearer Authentication
+Production-ready authentication with configurable factory pattern:
+```python
+# In superset_config.py
+MCP_AUTH_ENABLED = True
+MCP_JWKS_URI = "https://auth.company.com/.well-known/jwks.json"
+MCP_JWT_ISSUER = "https://auth.company.com/"
+MCP_JWT_AUDIENCE = "superset-mcp-api"
+```
+
+### Scope-Based Authorization
+| Tool Category | Required Scope |
+|---------------|----------------|
+| Dashboard ops | `dashboard:read` |
+| Chart ops | `chart:read` / `chart:write` |
+| Dataset ops | `dataset:read` |
+| System ops | `instance:read` |
+
+### Audit Logging
+All operations logged with MCP context:
+- User impersonation tracking
+- Tool execution details
+- Sanitized payloads (sensitive data redacted)
+
+## Cache Control
+
+Leverages Superset's existing cache layers with comprehensive control:
+
+### Cache Types
+1. **Query Result Cache** - Database query results
+2. **Metadata Cache** - Table schemas, columns, metrics
+3. **Form Data Cache** - Chart configurations
+4. **Dashboard Cache** - Rendered components
+
+### Cache Parameters
+Tools support cache control through request schemas:
+- `use_cache`: Enable/disable caching (default: true)
+- `force_refresh`: Force cache refresh (default: false)
+- `cache_timeout`: Override timeout in seconds
+- `refresh_metadata`: Force metadata refresh
+
+### Cache Status Reporting
+```json
+{
+  "cache_status": {
+    "cache_hit": true,
+    "cache_type": "query",
+    "cache_age_seconds": 300,
+    "refreshed": false
+  }
+}
+```
+
+## Tool Abstractions
+
+### Generic Base Classes
+- **ModelListTool**: Handles list/search/filter operations with pagination
+- **ModelGetInfoTool**: Single object retrieval by multiple identifier types
+- **ModelGetAvailableFiltersTool**: Returns filterable columns/operators
+
+### Implementation Pattern
+```python
+@mcp.tool
+@mcp_auth_hook
+def my_tool(request: MyRequest) -> MyResponse:
+    # Import Superset modules inside function
+    from superset.daos.dashboard import DashboardDAO
+    from superset.commands.chart.create import CreateChartCommand
+
+    # Tool implementation
+    return response
+```
+
+## Configuration
+
+### URL Configuration
+Centralized URL management for consistent link generation:
+```python
+# In superset_config.py
+SUPERSET_WEBSERVER_ADDRESS = "http://localhost:8088"  # Development
+SUPERSET_WEBSERVER_ADDRESS = "https://superset.company.com"  # Production
+```
+
+### Schema Design Principles
+- **Minimal columns** in list responses
+- **Optional fields** in info schemas for missing data handling
+- **Null exclusion** for cleaner JSON responses
+- **Type safety** with clear Pydantic validation
+
+## Adding New Tools
+
+1. **Choose domain folder**: `dashboard/`, `chart/`, `dataset/`, or `system/`
+2. **Define schemas**: Use Pydantic with field descriptions
+3. **Implement tool**:
+   - Decorate with `@mcp.tool` and `@mcp_auth_hook`
+   - Import Superset modules inside function body
+   - Use generic abstractions where applicable
+4. **Register**: Add to appropriate `__init__.py`
+5. **Test**: Add unit tests in `tests/unit_tests/mcp_service/`
+
+## Current Status
+
+### ✅ Phase 1 Complete
+- FastMCP server with CLI
+- JWT authentication with RBAC
+- All 16 core tools implemented
+- Request schema pattern
+- Cache control system
+- Audit logging
+- 194+ unit tests
+
+### 🎯 Future Enhancements
+- Demo notebooks and video examples
+- OAuth integration for user impersonation
+- Enhanced chart rendering formats
+- Advanced security features
+
+**Production Ready**: Core functionality stable with comprehensive testing and authentication.
+
+---
+
+For setup and usage, see the [MCP Service overview](./intro).

docs/docs/mcp-service/authentication.mdx

@@ -0,0 +1,434 @@
+---
+title: Authentication & Security
+sidebar_position: 4
+version: 1
+---
+
+# Authentication & Security
+
+The MCP service provides enterprise-grade JWT Bearer authentication with flexible configuration options and comprehensive security controls.
+
+## Quick Start
+
+### Development Mode (Default)
+
+:::tip
+Authentication is **disabled by default** for local development - no configuration needed.
+:::
+
+```bash
+# No configuration needed - service runs without authentication
+superset mcp run --port 5008 --debug
+```
+
+### Production Mode
+
+:::warning
+Always enable authentication for production deployments to secure your Superset instance.
+:::
+
+Enable JWT authentication in your Superset configuration:
+
+```python
+# In superset_config.py
+MCP_AUTH_ENABLED = True
+MCP_JWKS_URI = "https://auth.company.com/.well-known/jwks.json"
+MCP_JWT_ISSUER = "https://auth.company.com/"
+MCP_JWT_AUDIENCE = "superset-mcp-api"
+MCP_REQUIRED_SCOPES = ["dashboard:read", "chart:read", "dataset:read"]
+```
+
+## Configuration Options
+
+### Option 1: Simple Configuration
+
+Add to your `superset_config.py`:
+
+```python
+# Enable authentication
+MCP_AUTH_ENABLED = True
+
+# JWT settings
+MCP_JWKS_URI = "https://auth.company.com/.well-known/jwks.json"
+MCP_JWT_ISSUER = "https://auth.company.com/"
+MCP_JWT_AUDIENCE = "superset-mcp-api"
+MCP_REQUIRED_SCOPES = ["dashboard:read", "chart:read"]
+
+# Optional: User resolution
+MCP_JWT_USER_CLAIM = "sub"              # JWT claim for username (default: "sub")
+MCP_JWT_EMAIL_CLAIM = "email"           # JWT claim for email (default: "email")
+MCP_FALLBACK_USER = "admin"             # Fallback user if JWT user not found
+```
+
+### Option 2: Custom Factory
+
+For advanced authentication requirements:
+
+```python
+def create_custom_mcp_auth(app):
+    """Custom auth factory for enterprise environments."""
+    from fastmcp.server.auth.providers.bearer import BearerAuthProvider
+
+    return BearerAuthProvider(
+        jwks_uri=app.config["MCP_JWKS_URI"],
+        issuer=app.config["MCP_JWT_ISSUER"],
+        audience=app.config["MCP_JWT_AUDIENCE"],
+        required_scopes=app.config.get("MCP_REQUIRED_SCOPES", []),
+        user_resolver=custom_user_resolver,
+        cache_ttl=300  # Cache JWKS for 5 minutes
+    )
+
+MCP_AUTH_FACTORY = create_custom_mcp_auth
+```
+
+### Option 3: Environment Variables
+
+For containerized deployments:
+
+```bash
+# Environment variables
+export MCP_AUTH_ENABLED=true
+export MCP_JWKS_URI=https://auth.company.com/.well-known/jwks.json
+export MCP_JWT_ISSUER=https://auth.company.com/
+export MCP_JWT_AUDIENCE=superset-mcp-api
+export MCP_REQUIRED_SCOPES=dashboard:read,chart:read,dataset:read
+```
+
+## Identity Provider Integration
+
+### Auth0
+
+```python
+# Auth0 configuration
+MCP_JWKS_URI = "https://your-tenant.auth0.com/.well-known/jwks.json"
+MCP_JWT_ISSUER = "https://your-tenant.auth0.com/"
+MCP_JWT_AUDIENCE = "superset-mcp-api"
+```
+
+### Okta
+
+```python
+# Okta configuration
+MCP_JWKS_URI = "https://your-org.okta.com/oauth2/default/v1/keys"
+MCP_JWT_ISSUER = "https://your-org.okta.com/oauth2/default"
+MCP_JWT_AUDIENCE = "api://superset-mcp"
+```
+
+### AWS Cognito
+
+```python
+# Cognito configuration
+MCP_JWKS_URI = "https://cognito-idp.{region}.amazonaws.com/{userPoolId}/.well-known/jwks.json"
+MCP_JWT_ISSUER = "https://cognito-idp.{region}.amazonaws.com/{userPoolId}"
+MCP_JWT_AUDIENCE = "your-app-client-id"
+```
+
+### Azure AD
+
+```python
+# Azure AD configuration
+MCP_JWKS_URI = "https://login.microsoftonline.com/{tenant}/discovery/v2.0/keys"
+MCP_JWT_ISSUER = "https://login.microsoftonline.com/{tenant}/v2.0"
+MCP_JWT_AUDIENCE = "api://superset-mcp"
+```
+
+## Scope-Based Authorization
+
+### Standard Scopes
+
+The MCP service defines these standard scopes:
+
+| Scope | Description | Required For |
+|-------|-------------|--------------|
+| `dashboard:read` | Read dashboard information | `list_dashboards`, `get_dashboard_info` |
+| `dashboard:write` | Create/modify dashboards | `generate_dashboard`, `add_chart_to_existing_dashboard` |
+| `chart:read` | Read chart information | `list_charts`, `get_chart_info`, `get_chart_data` |
+| `chart:write` | Create/modify charts | `generate_chart`, `update_chart` |
+| `dataset:read` | Read dataset information | `list_datasets`, `get_dataset_info` |
+| `instance:read` | Read instance information | `get_superset_instance_info` |
+
+### Custom Scopes
+
+Define custom scopes for specific use cases:
+
+```python
+# Custom scope definitions
+CUSTOM_MCP_SCOPES = {
+    "analytics:export": "Export analytical data",
+    "reports:generate": "Generate automated reports",
+    "admin:config": "Access administrative configuration"
+}
+
+# Map tools to custom scopes
+def get_custom_required_scopes(tool_name: str) -> List[str]:
+    scope_map = {
+        "get_chart_data": ["chart:read", "analytics:export"],
+        "generate_dashboard": ["dashboard:write", "reports:generate"],
+        "get_superset_instance_info": ["instance:read", "admin:config"]
+    }
+    return scope_map.get(tool_name, [])
+
+MCP_SCOPE_RESOLVER = get_custom_required_scopes
+```
+
+## JWT Token Format
+
+### Required Claims
+
+Your JWT tokens must include these standard claims:
+
+```json
+{
+  "iss": "https://auth.company.com/",      // Issuer
+  "aud": "superset-mcp-api",               // Audience
+  "sub": "user@company.com",               // Subject (username)
+  "exp": 1704118800,                       // Expiration timestamp
+  "iat": 1704115200,                       // Issued at timestamp
+  "scope": "dashboard:read chart:read"     // Space-separated scopes
+}
+```
+
+### Optional Claims
+
+Additional claims for enhanced functionality:
+
+```json
+{
+  "email": "user@company.com",             // User email
+  "name": "John Doe",                      // Full name
+  "groups": ["analysts", "sales_team"],    // User groups
+  "tenant_id": "company_123",              // Multi-tenant ID
+  "role": "analyst"                        // User role
+}
+```
+
+## Client Integration
+
+### API Client Usage
+
+```python
+import requests
+
+# Get JWT token from your identity provider
+token = get_jwt_token()
+
+# Call MCP service with Bearer authentication
+headers = {
+    "Authorization": f"Bearer {token}",
+    "Content-Type": "application/json"
+}
+
+response = requests.post(
+    "http://localhost:5008/call_tool",
+    headers=headers,
+    json={
+        "tool": "list_dashboards",
+        "arguments": {"search": "sales"}
+    }
+)
+
+data = response.json()
+```
+
+### Claude Desktop with Authentication
+
+For Claude Desktop, the proxy script handles authentication:
+
+```bash
+#!/bin/bash
+# run_proxy_with_auth.sh
+
+# Get token from environment or file
+if [ -f ~/.superset_mcp_token ]; then
+    TOKEN=$(cat ~/.superset_mcp_token)
+else
+    TOKEN=${SUPERSET_MCP_TOKEN}
+fi
+
+# Export token for proxy
+export MCP_AUTH_TOKEN="$TOKEN"
+
+cd /path/to/superset
+source venv/bin/activate
+exec fastmcp proxy http://localhost:5008 --auth-header "Authorization: Bearer $TOKEN"
+```
+
+## User Resolution
+
+### Default User Resolution
+
+The service maps JWT claims to Superset users:
+
+```python
+def default_user_resolver(claims: Dict[str, Any]) -> User:
+    """Default user resolution from JWT claims."""
+
+    # Extract username from configurable claim
+    username = claims.get(app.config.get("MCP_JWT_USER_CLAIM", "sub"))
+
+    # Find Superset user
+    user = security_manager.find_user(username=username)
+
+    if not user:
+        # Try email lookup
+        email = claims.get(app.config.get("MCP_JWT_EMAIL_CLAIM", "email"))
+        if email:
+            user = security_manager.find_user(email=email)
+
+    if not user and app.config.get("MCP_FALLBACK_USER"):
+        # Use fallback user for development
+        user = security_manager.find_user(username=app.config["MCP_FALLBACK_USER"])
+
+    return user
+```
+
+### Custom User Resolution
+
+Implement custom user resolution logic:
+
+```python
+def custom_user_resolver(claims: Dict[str, Any]) -> User:
+    """Custom user resolution for enterprise environments."""
+
+    # Extract custom claims
+    employee_id = claims.get("employee_id")
+    tenant_id = claims.get("tenant_id")
+
+    # Multi-tenant user lookup
+    user = find_user_by_employee_id(employee_id, tenant_id)
+
+    if user:
+        # Set additional context
+        user.mcp_tenant_id = tenant_id
+        user.mcp_groups = claims.get("groups", [])
+
+    return user
+
+# Use custom resolver
+MCP_USER_RESOLVER = custom_user_resolver
+```
+
+## Security Features
+
+### Token Validation
+
+Comprehensive JWT validation:
+
+- **Signature verification**: RS256 with JWKS key rotation support
+- **Expiration checking**: Automatic token expiry validation
+- **Audience validation**: Prevents token reuse across services
+- **Issuer validation**: Ensures tokens from trusted sources only
+- **Scope validation**: Enforces tool-level permissions
+
+### Request Security
+
+- **HTTPS enforcement**: Production deployments should use HTTPS
+- **Rate limiting**: Configurable per-user rate limits
+- **Request logging**: All authenticated requests logged with user context
+- **Input validation**: Comprehensive request schema validation
+
+### Audit Logging
+
+Every tool call is logged with security context:
+
+```json
+{
+  "timestamp": "2024-01-25T14:30:00Z",
+  "user_id": "user@company.com",
+  "tool_name": "get_chart_data",
+  "source": "mcp",
+  "jwt_subject": "user@company.com",
+  "jwt_scopes": ["chart:read", "analytics:export"],
+  "tenant_id": "company_123",
+  "request_id": "req_12345",
+  "execution_time": 0.145,
+  "status": "success"
+}
+```
+
+## Testing Authentication
+
+### Generate Test Tokens
+
+For development and testing:
+
+```python
+from fastmcp.server.auth.providers.bearer import RSAKeyPair
+
+# Generate test keypair
+keypair = RSAKeyPair.generate()
+print("Public key:", keypair.public_key)
+
+# Create test token
+token = keypair.create_token(
+    subject="test@example.com",
+    issuer="https://test.example.com",
+    audience="superset-mcp-api",
+    scopes=["dashboard:read", "chart:read", "dataset:read"],
+    expires_in=3600  # 1 hour
+)
+print("Test token:", token)
+```
+
+### Test Configuration
+
+```python
+# Test configuration with generated keypair
+MCP_AUTH_ENABLED = True
+MCP_JWT_PUBLIC_KEY = """-----BEGIN PUBLIC KEY-----
+MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA...
+-----END PUBLIC KEY-----"""
+MCP_JWT_ISSUER = "https://test.example.com"
+MCP_JWT_AUDIENCE = "superset-mcp-api"
+MCP_FALLBACK_USER = "admin"
+```
+
+### Manual Testing
+
+```bash
+# Test with curl
+curl -X POST http://localhost:5008/call_tool \
+  -H "Authorization: Bearer $TEST_TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "tool": "get_superset_instance_info",
+    "arguments": {"include_statistics": true}
+  }'
+```
+
+## Troubleshooting
+
+### Common Issues
+
+**Token Validation Errors:**
+```
+Error: Invalid JWT signature
+Solution: Verify JWKS_URI is accessible and contains correct keys
+```
+
+**User Not Found:**
+```
+Error: User not found for JWT subject
+Solution: Check MCP_JWT_USER_CLAIM configuration and user exists in Superset
+```
+
+**Insufficient Scopes:**
+```
+Error: Missing required scope 'chart:read'
+Solution: Update JWT token to include required scopes
+```
+
+### Debug Configuration
+
+Enable debug logging for authentication issues:
+
+```python
+# Enhanced logging for auth debugging
+import logging
+logging.getLogger('superset.mcp_service.auth').setLevel(logging.DEBUG)
+
+# Log all JWT validation steps
+MCP_AUTH_DEBUG = True
+```
+
+This authentication guide provides comprehensive coverage for securing the MCP service in production environments while maintaining development flexibility.

docs/docs/mcp-service/development.mdx

@@ -0,0 +1,705 @@
+---
+title: Development Guide
+sidebar_position: 2
+version: 1
+---
+
+# MCP Service Development Guide
+
+This guide covers the internal architecture, development workflows, and patterns for extending the Superset MCP service.
+
+> 🚀 **New to MCP?** Start with the [Overview](./overview) to understand what the service does before diving into development.
+>
+> 📚 **Need API examples?** Check the [API Reference](./api-reference) to see how existing tools work.
+>
+> 🔐 **Planning production use?** Review [Authentication](./authentication) for security considerations.
+
+## Internal Architecture
+
+### Component Overview
+
+The MCP service follows a layered architecture with clear separation of concerns:
+
+```mermaid
+graph TB
+    subgraph "Transport Layer"
+        HTTP[HTTP Server :5008]
+        FastMCP[FastMCP Protocol Handler]
+    end
+
+    subgraph "Auth & Middleware Layer"
+        AuthHook[Auth Hook Decorator]
+        JWT[JWT Validator]
+        RBAC[RBAC Engine]
+        Audit[Audit Logger]
+    end
+
+    subgraph "Tool Layer"
+        Tools[16 MCP Tools<br/>Tool Decorated]
+        Schemas[Pydantic Schemas]
+        Validation[Request Validation]
+    end
+
+    subgraph "Business Logic Layer"
+        Generic[Generic Tool Abstractions]
+        ModelList[ModelListTool]
+        ModelGet[ModelGetInfoTool]
+        ModelFilter[ModelGetAvailableFiltersTool]
+    end
+
+    subgraph "Data Access Layer"
+        DAOs[Superset DAOs]
+        Commands[Superset Commands]
+        Cache[Cache Manager]
+    end
+
+    subgraph "Storage Layer"
+        MetaDB[(Metadata DB)]
+        DataWH[(Data Warehouse)]
+        Redis[(Redis Cache)]
+    end
+
+    HTTP --> FastMCP
+    FastMCP --> AuthHook
+    AuthHook --> JWT
+    JWT --> RBAC
+    RBAC --> Audit
+    Audit --> Tools
+
+    Tools --> Schemas
+    Schemas --> Validation
+    Validation --> Generic
+
+    Generic --> ModelList
+    Generic --> ModelGet
+    Generic --> ModelFilter
+
+    ModelList --> DAOs
+    ModelGet --> DAOs
+    ModelFilter --> DAOs
+
+    Tools --> Commands
+    Commands --> Cache
+
+    DAOs --> MetaDB
+    Commands --> MetaDB
+    Commands --> DataWH
+    Cache --> Redis
+```
+
+### Request Flow
+
+Every MCP tool call follows this execution pattern:
+
+```mermaid
+sequenceDiagram
+    participant Client as LLM Client
+    participant MCP as FastMCP Server
+    participant Auth as Auth Hook
+    participant Tool as MCP Tool
+    participant Generic as Generic Abstraction
+    participant DAO as Superset DAO
+    participant DB as Database
+
+    Client->>+MCP: tool_call(request)
+    MCP->>+Auth: validate_and_authorize()
+    Auth->>Auth: Validate JWT token
+    Auth->>Auth: Check required scopes
+    Auth->>Auth: Set Flask g.user context
+    Auth->>Auth: Log audit event
+    Auth->>+Tool: execute_tool(validated_request)
+
+    Tool->>Tool: Parse Pydantic request schema
+    Tool->>+Generic: Use generic abstraction
+    Generic->>+DAO: Query Superset data
+    DAO->>+DB: Execute SQL
+    DB-->>-DAO: Return results
+    DAO-->>-Generic: Return objects
+    Generic->>Generic: Apply pagination/filtering
+    Generic-->>-Tool: Return formatted data
+
+    Tool->>Tool: Build Pydantic response schema
+    Tool-->>-Auth: Return response
+    Auth->>Auth: Log success audit event
+    Auth-->>-MCP: Return validated response
+    MCP-->>-Client: JSON response
+```
+
+### Tool Registration System
+
+Tools are automatically discovered and registered through the decorator pattern:
+
+```python
+# superset/mcp_service/mcp_app.py
+from fastmcp import FastMCP
+
+# Global MCP instance
+mcp = FastMCP("Superset MCP Service")
+
+# Tools register themselves via decorators
+@mcp.tool
+@mcp_auth_hook(['chart:read'])
+def get_chart_info(request: GetChartInfoRequest) -> GetChartInfoResponse:
+    # Tool implementation
+    pass
+
+# All tool modules imported to trigger registration
+from superset.mcp_service.chart.tool import *
+from superset.mcp_service.dashboard.tool import *
+from superset.mcp_service.dataset.tool import *
+from superset.mcp_service.system.tool import *
+```
+
+## Development Patterns
+
+### Tool Implementation Pattern
+
+All tools follow this standardized pattern:
+
+```python
+# Example: superset/mcp_service/chart/tool/get_chart_info.py
+from superset.mcp_service.auth import mcp_auth_hook
+from superset.mcp_service.mcp_app import mcp
+from superset.mcp_service.schemas.chart_schemas import (
+    GetChartInfoRequest,
+    GetChartInfoResponse,
+    ChartError
+)
+
+@mcp.tool
+@mcp_auth_hook(['chart:read'])
+def get_chart_info(request: GetChartInfoRequest) -> GetChartInfoResponse:
+    """
+    Get detailed information about a specific chart.
+
+    Supports lookup by ID or UUID with comprehensive metadata.
+    """
+    try:
+        # CRITICAL: Import Superset modules inside function
+        from superset.daos.chart import ChartDAO
+        from superset.models.slice import Slice
+
+        # Use generic abstraction for common operations
+        from superset.mcp_service.generic_tools import ModelGetInfoTool
+
+        tool = ModelGetInfoTool(
+            dao=ChartDAO,
+            model=Slice,
+            response_schema=GetChartInfoResponse,
+            identifier_field_map={
+                'id': 'id',
+                'uuid': 'uuid'
+            }
+        )
+
+        return tool.execute(request)
+
+    except Exception as e:
+        return ChartError(
+            error=f"Failed to get chart info: {str(e)}",
+            error_type="ChartInfoError"
+        )
+```
+
+### Schema Design Patterns
+
+Pydantic schemas follow these conventions:
+
+```python
+# Request Schema Pattern
+class GetChartInfoRequest(BaseModel):
+    """Request to get detailed chart information."""
+
+    identifier: Union[int, str] = Field(
+        ...,
+        description="Chart ID (numeric) or UUID (string)"
+    )
+
+    include_form_data: bool = Field(
+        default=True,
+        description="Whether to include chart configuration"
+    )
+
+    use_cache: bool = Field(
+        default=True,
+        description="Whether to use cached data"
+    )
+
+# Response Schema Pattern
+class GetChartInfoResponse(BaseModel):
+    """Detailed chart information response."""
+
+    chart_id: int = Field(description="Chart numeric ID")
+    uuid: Optional[str] = Field(description="Chart UUID")
+    slice_name: str = Field(description="Chart display name")
+    viz_type: str = Field(description="Visualization type")
+    datasource_id: Optional[int] = Field(description="Dataset ID")
+    form_data: Optional[Dict[str, Any]] = Field(description="Chart configuration")
+    explore_url: Optional[str] = Field(description="Explore URL for editing")
+
+    # Cache status for transparency
+    cache_status: Optional[CacheStatus] = Field(description="Cache hit information")
+
+# Error Schema Pattern
+class ChartError(BaseModel):
+    """Chart operation error response."""
+
+    error: str = Field(description="Error message")
+    error_type: str = Field(description="Error type identifier")
+    suggestions: Optional[List[str]] = Field(description="Suggested fixes")
+```
+
+### Generic Tool Abstractions
+
+Common operations are abstracted into reusable classes:
+
+```python
+# superset/mcp_service/generic_tools.py
+from typing import Type, Dict, Any, List, Optional
+from pydantic import BaseModel
+
+class ModelListTool:
+    """Generic tool for list operations with pagination and filtering."""
+
+    def __init__(self,
+                 dao: Type,
+                 model: Type,
+                 response_schema: Type[BaseModel],
+                 default_columns: List[str] = None,
+                 searchable_columns: List[str] = None):
+        self.dao = dao
+        self.model = model
+        self.response_schema = response_schema
+        self.default_columns = default_columns or []
+        self.searchable_columns = searchable_columns or []
+
+    def execute(self, request: BaseModel) -> BaseModel:
+        """Execute list operation with pagination and filtering."""
+
+        # Build query with filters
+        query = self.dao.find_all()
+
+        # Apply search if provided
+        if hasattr(request, 'search') and request.search:
+            query = self._apply_search(query, request.search)
+
+        # Apply filters if provided
+        if hasattr(request, 'filters') and request.filters:
+            query = self._apply_filters(query, request.filters)
+
+        # Apply pagination
+        total = query.count()
+
+        if hasattr(request, 'page') and hasattr(request, 'page_size'):
+            offset = (request.page - 1) * request.page_size
+            query = query.offset(offset).limit(request.page_size)
+
+        # Execute query and serialize
+        results = query.all()
+        serialized = [self._serialize_model(obj) for obj in results]
+
+        return self.response_schema(
+            results=serialized,
+            total_count=total,
+            page=getattr(request, 'page', 1),
+            page_size=getattr(request, 'page_size', len(serialized))
+        )
+
+class ModelGetInfoTool:
+    """Generic tool for getting single object by multiple identifier types."""
+
+    def __init__(self,
+                 dao: Type,
+                 model: Type,
+                 response_schema: Type[BaseModel],
+                 identifier_field_map: Dict[str, str]):
+        self.dao = dao
+        self.model = model
+        self.response_schema = response_schema
+        self.identifier_field_map = identifier_field_map
+
+    def execute(self, request: BaseModel) -> BaseModel:
+        """Execute get operation with multi-identifier support."""
+
+        identifier = request.identifier
+
+        # Determine identifier type and field
+        if isinstance(identifier, int):
+            field = self.identifier_field_map.get('id', 'id')
+            obj = self.dao.find_by_id(identifier)
+        elif isinstance(identifier, str):
+            if len(identifier) == 36 and '-' in identifier:  # UUID format
+                field = self.identifier_field_map.get('uuid', 'uuid')
+                obj = self.dao.find_by_uuid(identifier)
+            else:  # Assume slug
+                field = self.identifier_field_map.get('slug', 'slug')
+                obj = getattr(self.dao, 'find_by_slug', lambda x: None)(identifier)
+
+        if not obj:
+            raise ValueError(f"Object not found with identifier: {identifier}")
+
+        # Serialize and return
+        serialized = self._serialize_model(obj)
+        return self.response_schema(**serialized)
+```
+
+## Adding New Tools
+
+### Step-by-Step Process
+
+1. **Define the Domain**
+
+   Choose the appropriate domain folder:
+   - `dashboard/` - Dashboard operations
+   - `chart/` - Chart operations
+   - `dataset/` - Dataset operations
+   - `system/` - System-level operations
+
+2. **Create Schemas**
+
+   ```bash
+   # Create schema file
+   touch superset/mcp_service/schemas/my_domain_schemas.py
+   ```
+
+   ```python
+   # Define request/response schemas
+   class MyToolRequest(BaseModel):
+       param1: str = Field(description="Parameter description")
+       param2: Optional[int] = Field(default=None, description="Optional parameter")
+
+   class MyToolResponse(BaseModel):
+       result: str = Field(description="Result description")
+       metadata: Dict[str, Any] = Field(description="Additional metadata")
+   ```
+
+3. **Implement the Tool**
+
+   ```bash
+   # Create tool file
+   touch superset/mcp_service/my_domain/tool/my_tool.py
+   ```
+
+   ```python
+   @mcp.tool
+   @mcp_auth_hook(['required:scope'])
+   def my_tool(request: MyToolRequest) -> MyToolResponse:
+       """Tool description for LLM."""
+
+       # Import Superset modules inside function
+       from superset.daos.my_dao import MyDAO
+
+       # Implement business logic
+       result = MyDAO.do_something(request.param1)
+
+       return MyToolResponse(
+           result=result,
+           metadata={"processed_at": datetime.utcnow()}
+       )
+   ```
+
+4. **Register the Tool**
+
+   ```python
+   # Add to superset/mcp_service/my_domain/tool/__init__.py
+   from .my_tool import my_tool
+
+   __all__ = ['my_tool']
+   ```
+
+   ```python
+   # Import in superset/mcp_service/mcp_app.py
+   from superset.mcp_service.my_domain.tool import *
+   ```
+
+5. **Add Tests**
+
+   ```bash
+   # Create test file
+   touch tests/unit_tests/mcp_service/test_my_tool.py
+   ```
+
+   ```python
+   import pytest
+   from superset.mcp_service.my_domain.tool.my_tool import my_tool
+   from superset.mcp_service.schemas.my_domain_schemas import MyToolRequest
+
+   class TestMyTool:
+       def test_my_tool_success(self):
+           request = MyToolRequest(param1="test")
+           response = my_tool(request)
+           assert response.result == "expected_result"
+   ```
+
+### Tool Best Practices
+
+1. **Import Inside Functions**
+   ```python
+   # ❌ DON'T: Import at module level
+   from superset.daos.chart import ChartDAO
+
+   @mcp.tool
+   def my_tool():
+       # Tool implementation
+       pass
+
+   # ✅ DO: Import inside function
+   @mcp.tool
+   def my_tool():
+       from superset.daos.chart import ChartDAO
+       # Tool implementation
+       pass
+   ```
+
+2. **Use Generic Abstractions**
+   ```python
+   # ✅ Leverage existing patterns
+   @mcp.tool
+   def list_my_objects(request):
+       from superset.mcp_service.generic_tools import ModelListTool
+
+       tool = ModelListTool(
+           dao=MyDAO,
+           model=MyModel,
+           response_schema=ListMyObjectsResponse
+       )
+       return tool.execute(request)
+   ```
+
+3. **Comprehensive Error Handling**
+   ```python
+   @mcp.tool
+   def my_tool(request):
+       try:
+           # Tool implementation
+           return success_response
+       except PermissionError as e:
+           return MyToolError(
+               error="Permission denied",
+               error_type="PermissionError",
+               suggestions=["Check user permissions"]
+           )
+       except Exception as e:
+           return MyToolError(
+               error=f"Unexpected error: {str(e)}",
+               error_type="InternalError"
+           )
+   ```
+
+## Testing Patterns
+
+### Unit Test Structure
+
+```python
+# tests/unit_tests/mcp_service/test_chart_tools.py
+import pytest
+from unittest.mock import Mock, patch
+from superset.mcp_service.chart.tool.get_chart_info import get_chart_info
+from superset.mcp_service.schemas.chart_schemas import GetChartInfoRequest
+
+class TestGetChartInfo:
+    """Test suite for get_chart_info tool."""
+
+    @patch('superset.mcp_service.chart.tool.get_chart_info.ChartDAO')
+    def test_get_chart_info_by_id_success(self, mock_dao):
+        """Test successful chart lookup by ID."""
+
+        # Setup mock
+        mock_chart = Mock()
+        mock_chart.id = 1
+        mock_chart.slice_name = "Test Chart"
+        mock_chart.viz_type = "line"
+        mock_dao.find_by_id.return_value = mock_chart
+
+        # Execute
+        request = GetChartInfoRequest(identifier=1)
+        response = get_chart_info(request)
+
+        # Verify
+        assert response.chart_id == 1
+        assert response.slice_name == "Test Chart"
+        mock_dao.find_by_id.assert_called_once_with(1)
+
+    @patch('superset.mcp_service.chart.tool.get_chart_info.ChartDAO')
+    def test_get_chart_info_not_found(self, mock_dao):
+        """Test chart not found scenario."""
+
+        # Setup mock
+        mock_dao.find_by_id.return_value = None
+
+        # Execute
+        request = GetChartInfoRequest(identifier=999)
+        response = get_chart_info(request)
+
+        # Verify error response
+        assert hasattr(response, 'error')
+        assert "not found" in response.error.lower()
+```
+
+### Integration Test Patterns
+
+```python
+# tests/integration_tests/mcp_service/test_chart_integration.py
+import pytest
+from superset.app import create_app
+from superset.mcp_service.mcp_app import mcp
+from tests.integration_tests.base_tests import SupersetTestCase
+
+class TestChartIntegration(SupersetTestCase):
+    """Integration tests for chart tools."""
+
+    def setUp(self):
+        super().setUp()
+        self.app = create_app()
+        self.app_context = self.app.app_context()
+        self.app_context.push()
+
+    def tearDown(self):
+        self.app_context.pop()
+        super().tearDown()
+
+    def test_chart_workflow_integration(self):
+        """Test complete chart workflow."""
+
+        # Create chart
+        create_request = {
+            "dataset_id": "1",
+            "config": {
+                "chart_type": "table",
+                "columns": [{"name": "region"}]
+            }
+        }
+
+        create_response = mcp.call_tool("generate_chart", create_request)
+        chart_id = create_response["chart_id"]
+
+        # Get chart info
+        info_request = {"identifier": chart_id}
+        info_response = mcp.call_tool("get_chart_info", info_request)
+
+        assert info_response["chart_id"] == chart_id
+        assert info_response["viz_type"] == "table"
+
+        # Get chart data
+        data_request = {"identifier": chart_id, "limit": 10}
+        data_response = mcp.call_tool("get_chart_data", data_request)
+
+        assert "data" in data_response
+        assert len(data_response["data"]) <= 10
+```
+
+## Performance Considerations
+
+### Caching Strategy
+
+The MCP service leverages Superset's existing cache layers:
+
+```python
+# Cache control in tools
+@mcp.tool
+def get_chart_data(request: GetChartDataRequest):
+    """Tool with cache control."""
+
+    cache_config = {
+        'use_cache': request.use_cache,
+        'force_refresh': request.force_refresh,
+        'cache_timeout': request.cache_timeout
+    }
+
+    # Use Superset's cache infrastructure
+    result = execute_with_cache(query, cache_config)
+
+    return ChartDataResponse(
+        data=result.data,
+        cache_status=result.cache_status
+    )
+```
+
+### Query Optimization
+
+```python
+# Efficient pagination
+def list_objects(query, page, page_size):
+    """Optimized pagination pattern."""
+
+    # Count query optimization
+    total = query.count()
+
+    # Limit columns for list operations
+    query = query.options(load_only('id', 'name', 'created_on'))
+
+    # Apply pagination
+    offset = (page - 1) * page_size
+    results = query.offset(offset).limit(page_size).all()
+
+    return results, total
+```
+
+## Security Considerations
+
+### Authentication Flow
+
+```python
+# JWT validation and user context
+@mcp_auth_hook(['chart:read'])
+def secure_tool(request):
+    """Tool with proper security context."""
+
+    # g.user is set by auth hook
+    user_id = g.user.id
+
+    # Apply user-specific filtering
+    query = ChartDAO.find_all().filter(
+        Chart.owners.contains(g.user)
+    )
+
+    return execute_query(query)
+```
+
+### Input Validation
+
+```python
+# Comprehensive request validation
+class CreateChartRequest(BaseModel):
+    """Validated chart creation request."""
+
+    dataset_id: Union[int, str] = Field(
+        ...,
+        description="Dataset ID or UUID"
+    )
+
+    config: ChartConfig = Field(
+        ...,
+        description="Chart configuration"
+    )
+
+    @validator('dataset_id')
+    def validate_dataset_id(cls, v):
+        """Validate dataset exists and user has access."""
+        # Validation logic
+        return v
+
+    @validator('config')
+    def validate_chart_config(cls, v):
+        """Validate chart configuration."""
+        # Configuration validation
+        return v
+```
+
+This development guide provides comprehensive coverage of the MCP service's internal architecture and development patterns, enabling team members to effectively extend and maintain the system.
+
+## Related Documentation
+
+### 📚 **Ready to Use Your New Tools?**
+Test your implementations with examples from the [API Reference](./api-reference).
+
+### 🔐 **Securing Your Extensions?**
+Add authentication to your tools using the [Authentication Guide](./authentication).
+
+### 🏗️ **Understanding the Big Picture?**
+See the complete system design in the [Architecture Overview](./architecture).
+
+### 🏢 **Building Enterprise Features?**
+Explore advanced patterns in the [Preset Integration Guide](./preset-integration).
+
+> 📖 **Back to Documentation Index**: [MCP Service](./intro)

docs/docs/mcp-service/intro.mdx

@@ -0,0 +1,124 @@
+---
+title: MCP Service
+sidebar_position: 1
+version: 1
+---
+
+# Superset MCP Service
+
+The Superset Model Context Protocol (MCP) service provides programmatic access to Superset dashboards, charts, datasets, and instance metadata. Built for LLM agents and automation tools.
+
+## What is MCP?
+
+The Model Context Protocol (MCP) is an open standard that allows AI assistants to securely connect to data sources and tools. Superset's MCP service exposes **16 production-ready tools** that enable:
+
+- 📊 **Data Exploration**: List and query dashboards, charts, and datasets
+- 🔧 **Chart Creation**: Generate visualizations programmatically
+- 📈 **Data Export**: Extract data in multiple formats (JSON, CSV, Excel)
+- 🔗 **Navigation**: Generate explore links and SQL Lab sessions
+
+## Quick Start
+
+### Installation
+
+:::note
+The MCP service is included with Superset development setup. FastMCP dependencies are installed automatically with `make install`.
+:::
+
+```bash
+# MCP service is included with Superset development setup
+git clone https://github.com/apache/superset.git
+cd superset
+make venv && source venv/bin/activate
+make install
+
+# Start Superset
+superset run -p 8088 --with-threads --reload --debugger
+
+# Start MCP service (separate terminal)
+source venv/bin/activate
+superset mcp run --port 5008 --debug
+```
+
+### Claude Desktop Integration
+
+```json
+{
+  "mcpServers": {
+    "Superset MCP": {
+      "command": "/path/to/superset/superset/mcp_service/run_proxy.sh",
+      "args": [],
+      "env": {}
+    }
+  }
+}
+```
+
+## Key Features
+
+### 🔧 **16 Production Tools**
+| Category | Tools | Purpose |
+|----------|-------|---------|
+| **Dashboard** (5) | List, get info, create, add charts | Dashboard management |
+| **Chart** (8) | Full CRUD, data export, previews | Chart operations |
+| **Dataset** (3) | List, get info, discover filters | Dataset exploration |
+| **System** (2) | Instance info, explore links | System integration |
+| **SQL Lab** (1) | Pre-configured sessions | SQL development |
+
+### 🔐 **Enterprise Security**
+- **JWT Bearer Authentication**: Production-ready with configurable factory pattern
+- **RBAC Integration**: Scope-based permissions with Superset's security model
+- **Audit Logging**: Comprehensive MCP context tracking
+
+### 📊 **Advanced Capabilities**
+- **Multi-format Export**: JSON, CSV, Excel data export
+- **Chart Previews**: Screenshots, ASCII art, table representations
+- **Cache Control**: Leverage Superset's existing cache infrastructure
+- **Request Schemas**: Eliminates LLM parameter validation issues
+
+## Example Usage
+
+```python
+# List dashboards
+dashboards = client.call_tool("list_dashboards", {
+    "search": "sales",
+    "page_size": 10
+})
+
+# Create a chart
+chart = client.call_tool("generate_chart", {
+    "dataset_id": "1",
+    "config": {
+        "chart_type": "line",
+        "x": {"name": "date"},
+        "y": [{"name": "revenue", "aggregate": "SUM"}]
+    }
+})
+
+# Export chart data
+data = client.call_tool("get_chart_data", {
+    "identifier": chart["chart_id"],
+    "format": "json",
+    "limit": 1000
+})
+```
+
+## Status
+
+✅ **Phase 1 Complete** - Core functionality stable, authentication production-ready, comprehensive testing coverage.
+
+## Documentation Structure
+
+### Getting Started
+- **[Overview](./overview)** - Features, use cases, and examples
+- **[API Reference](./api-reference)** - Complete tool documentation
+
+### Development
+- **[Development Guide](./development)** - Internal architecture and adding tools
+- **[Architecture](./architecture)** - System design and patterns
+
+### Production
+- **[Authentication](./authentication)** - JWT setup and security
+- **[Preset Integration](./preset-integration)** - Enterprise features
+
+> 🚀 **Ready to start?** Continue with the [Overview](./overview) for detailed examples and use cases.

docs/docs/mcp-service/overview.mdx

@@ -0,0 +1,196 @@
+---
+title: MCP Service Overview
+sidebar_position: 1
+version: 1
+---
+
+# Superset MCP Service
+
+The Superset Model Context Protocol (MCP) service provides a modular, schema-driven interface for programmatic access to Superset dashboards, charts, datasets, and instance metadata. Built on FastMCP, it's designed for LLM agents and automation tools.
+
+**Status:** ✅ Phase 1 Complete. Core functionality stable, authentication production-ready, comprehensive testing coverage.
+
+## What is MCP?
+
+The Model Context Protocol (MCP) is an open standard for connecting AI assistants to data sources and tools. Superset's MCP service exposes 16 tools that allow LLM agents to:
+
+- **Explore data**: List and query dashboards, charts, and datasets
+- **Create visualizations**: Generate charts and dashboards programmatically
+- **Export data**: Extract chart data in multiple formats
+- **Navigate interfaces**: Generate explore links and SQL Lab sessions
+
+## Key Features
+
+### 🔧 **16 Production-Ready Tools**
+- **Dashboard Tools (5)**: List, get info, create dashboards, add charts
+- **Chart Tools (8)**: Full CRUD operations, data export, screenshot previews
+- **Dataset Tools (3)**: List, get info, discover filterable columns
+- **System Tools (2)**: Instance info, explore link generation
+- **SQL Lab Tools (1)**: Pre-configured SQL sessions
+
+### 🔐 **Enterprise Authentication**
+- **JWT Bearer Authentication**: Production-ready with configurable factory pattern
+- **RBAC Integration**: Scope-based permissions with Superset's security model
+- **Audit Logging**: Comprehensive MCP context tracking with impersonation support
+
+### 📊 **Advanced Capabilities**
+- **Multi-format Export**: JSON, CSV, Excel data export
+- **Chart Previews**: Screenshots, ASCII art, and table representations
+- **Cache Control**: Comprehensive control over Superset's cache layers
+- **Request Schema Pattern**: Eliminates LLM parameter validation issues
+
+## Architecture Overview
+
+```mermaid
+graph TB
+    subgraph "Client Layer"
+        LLM[LLM/Agent Client]
+        Claude[Claude Desktop]
+        SDK[Custom SDK]
+    end
+
+    subgraph "MCP Service Layer"
+        FastMCP[FastMCP Server<br/>Port 5008]
+        Auth[JWT Auth Hook]
+        Tools[16 MCP Tools]
+    end
+
+    subgraph "Superset Integration"
+        DAOs[Superset DAOs]
+        Commands[Superset Commands]
+        Cache[Cache Layer]
+    end
+
+    subgraph "Data Layer"
+        DB[(Superset Database)]
+        DataWarehouse[(Data Warehouse)]
+    end
+
+    LLM --> FastMCP
+    Claude --> FastMCP
+    SDK --> FastMCP
+
+    FastMCP --> Auth
+    Auth --> Tools
+
+    Tools --> DAOs
+    Tools --> Commands
+    Tools --> Cache
+
+    DAOs --> DB
+    Commands --> DB
+    Commands --> DataWarehouse
+```
+
+## Getting Started
+
+### Quick Setup
+
+```bash
+# Clone and install Superset
+git clone https://github.com/apache/superset.git
+cd superset
+make venv && source venv/bin/activate
+make install
+
+# Start Superset
+superset run -p 8088 --with-threads --reload --debugger
+
+# Start MCP service (in separate terminal)
+source venv/bin/activate
+superset mcp run --port 5008 --debug
+```
+
+### Connect to Claude Desktop
+
+:::note
+The MCP service runs on HTTP and requires a proxy for Claude Desktop integration.
+:::
+
+```bash
+# Install FastMCP proxy
+pip install fastmcp
+```
+
+Configure Claude Desktop (`~/.config/Claude/claude_desktop_config.json`):
+
+```json
+{
+  "mcpServers": {
+    "Superset MCP": {
+      "command": "/path/to/superset/superset/mcp_service/run_proxy.sh",
+      "args": [],
+      "env": {}
+    }
+  }
+}
+```
+
+## Use Cases
+
+### Data Exploration
+- "List all dashboards related to sales"
+- "Show me the charts in the Q4 Performance dashboard"
+- "What datasets are available for customer analysis?"
+
+### Chart Creation
+- "Create a line chart showing revenue trends by month"
+- "Generate a table showing top 10 products by sales"
+- "Build a bar chart comparing regional performance"
+
+### Data Export
+- "Export the sales data from this chart as CSV"
+- "Get the underlying data for this dashboard as JSON"
+- "Show me a preview of this chart as ASCII art"
+
+### Dashboard Management
+- "Create a new dashboard with these 4 charts"
+- "Add this revenue chart to the executive dashboard"
+- "Generate an explore link for this chart configuration"
+
+## Example Workflow
+
+```python
+# List available dashboards
+dashboards = client.call_tool("list_dashboards", {
+    "search": "sales",
+    "page_size": 10
+})
+
+# Get detailed dashboard info
+dashboard = client.call_tool("get_dashboard_info", {
+    "identifier": dashboards["dashboards"][0]["id"]
+})
+
+# Create a new chart
+chart = client.call_tool("generate_chart", {
+    "dataset_id": "1",
+    "config": {
+        "chart_type": "line",
+        "x": {"name": "date"},
+        "y": [{"name": "revenue", "aggregate": "SUM"}]
+    }
+})
+
+# Export chart data
+data = client.call_tool("get_chart_data", {
+    "identifier": chart["chart_id"],
+    "format": "json",
+    "limit": 1000
+})
+```
+
+## Next Steps
+
+### Ready to Use MCP?
+- **[📚 API Reference](./api-reference)** - Try all 16 tools with request/response examples
+- **[🔐 Authentication](./authentication)** - Set up JWT security for production use
+
+### Want to Extend MCP?
+- **[🔧 Development Guide](./development)** - Learn internal architecture and add new tools
+- **[🏗️ Architecture](./architecture)** - Understand system design and deployment patterns
+
+### Enterprise Deployment?
+- **[🏢 Preset Integration](./preset-integration)** - RBAC extensions and OIDC integration for enterprise
+
+> 💡 **Getting started?** Return to the [MCP Service intro](./intro) for a complete overview.

docs/docs/mcp-service/preset-integration.mdx

@@ -0,0 +1,483 @@
+---
+title: Preset.io Integration
+sidebar_position: 6
+version: 1
+---
+
+# Preset.io Integration Guide
+
+This document outlines integration points for the Preset.io team to extend the Superset MCP service with enterprise features, RBAC customizations, and OIDC integration.
+
+## RBAC Extension Points
+
+### Custom Authorization Factory
+
+The MCP service supports custom authorization logic through the factory pattern:
+
+```python
+# In preset_config.py or superset_config.py
+def create_preset_mcp_auth(app):
+    """Custom auth factory for Preset.io environments."""
+    from superset.mcp_service.auth import create_auth_provider
+    from preset.auth.mcp import PresetMCPAuthProvider
+
+    return PresetMCPAuthProvider(
+        jwks_uri=app.config["PRESET_JWKS_URI"],
+        issuer=app.config["PRESET_JWT_ISSUER"],
+        audience=app.config["PRESET_JWT_AUDIENCE"],
+        tenant_resolver=preset_tenant_resolver,
+        rbac_manager=app.security_manager,
+    )
+
+MCP_AUTH_FACTORY = create_preset_mcp_auth
+```
+
+### Multi-Tenant RBAC
+
+Extend the base auth hook for tenant-aware permissions:
+
+```python
+# preset/mcp/auth.py
+from superset.mcp_service.auth import mcp_auth_hook
+from functools import wraps
+
+def preset_tenant_auth_hook(required_permissions=None):
+    """Preset-specific auth hook with tenant isolation."""
+    def decorator(func):
+        @wraps(func)
+        @mcp_auth_hook(required_permissions)
+        def wrapper(*args, **kwargs):
+            # Extract tenant from JWT claims
+            tenant_id = g.user.tenant_id if hasattr(g.user, 'tenant_id') else None
+
+            # Inject tenant context
+            g.mcp_tenant_id = tenant_id
+            g.mcp_tenant_context = get_tenant_context(tenant_id)
+
+            return func(*args, **kwargs)
+        return wrapper
+    return decorator
+```
+
+### Custom Permission Scopes
+
+Define Preset-specific permission scopes:
+
+```python
+# preset/mcp/permissions.py
+PRESET_MCP_SCOPES = {
+    # Tenant-level permissions
+    "tenant:admin": "Full tenant administration",
+    "tenant:read": "Read tenant resources",
+
+    # Workspace-level permissions
+    "workspace:admin": "Full workspace administration",
+    "workspace:read": "Read workspace resources",
+
+    # Enhanced dashboard permissions
+    "dashboard:publish": "Publish dashboards to marketplace",
+    "dashboard:embed": "Generate embed tokens",
+
+    # Enhanced chart permissions
+    "chart:export": "Export chart data and configs",
+    "chart:alerts": "Manage chart alerts and notifications",
+
+    # Dataset permissions with row-level security
+    "dataset:rls": "Apply row-level security filters",
+    "dataset:pii": "Access PII-flagged columns",
+}
+
+def get_preset_required_scopes(tool_name: str, context: dict = None) -> List[str]:
+    """Map tool calls to Preset-specific permission requirements."""
+    base_scopes = get_base_required_scopes(tool_name)
+
+    # Add tenant-aware scopes
+    if context and context.get('tenant_id'):
+        base_scopes.append(f"tenant:{context['tenant_id']}")
+
+    # Add workspace-aware scopes
+    if context and context.get('workspace_id'):
+        base_scopes.append(f"workspace:{context['workspace_id']}")
+
+    return base_scopes
+```
+
+### Row-Level Security Integration
+
+Extend data access tools with RLS:
+
+```python
+# preset/mcp/rls.py
+def apply_preset_rls_filters(query_context: dict, user_context: dict) -> dict:
+    """Apply Preset row-level security filters to query context."""
+
+    # Get user's RLS rules from Preset metadata
+    rls_rules = get_user_rls_rules(
+        user_id=user_context['user_id'],
+        tenant_id=user_context['tenant_id'],
+        workspace_id=user_context.get('workspace_id')
+    )
+
+    # Apply RLS filters to query
+    for rule in rls_rules:
+        if rule.applies_to_dataset(query_context['datasource']['id']):
+            query_context = rule.apply_filter(query_context)
+
+    return query_context
+
+# Usage in custom tools
+@mcp.tool
+@preset_tenant_auth_hook(['dataset:read', 'dataset:rls'])
+def preset_get_chart_data(request: GetChartDataRequest) -> ChartDataResponse:
+    """Get chart data with Preset RLS applied."""
+
+    # Apply RLS before executing query
+    query_context = build_query_context(request)
+    query_context = apply_preset_rls_filters(
+        query_context,
+        {'user_id': g.user.id, 'tenant_id': g.mcp_tenant_id}
+    )
+
+    return execute_chart_data_query(query_context)
+```
+
+## OIDC Integration Points
+
+### Preset OIDC Provider
+
+Custom OIDC integration for Preset environments:
+
+```python
+# preset/mcp/oidc.py
+from superset.mcp_service.auth.providers.bearer import BearerAuthProvider
+import requests
+from typing import Dict, Any
+
+class PresetOIDCAuthProvider(BearerAuthProvider):
+    """OIDC-specific auth provider for Preset.io."""
+
+    def __init__(self,
+                 oidc_discovery_url: str,
+                 client_id: str,
+                 client_secret: str = None,
+                 **kwargs):
+
+        # Discover OIDC endpoints
+        self.discovery_doc = self._fetch_discovery_document(oidc_discovery_url)
+
+        super().__init__(
+            jwks_uri=self.discovery_doc['jwks_uri'],
+            issuer=self.discovery_doc['issuer'],
+            **kwargs
+        )
+
+        self.client_id = client_id
+        self.client_secret = client_secret
+
+    def _fetch_discovery_document(self, discovery_url: str) -> Dict[str, Any]:
+        """Fetch OIDC discovery document."""
+        response = requests.get(discovery_url)
+        response.raise_for_status()
+        return response.json()
+
+    def validate_token(self, token: str) -> Dict[str, Any]:
+        """Validate JWT token with OIDC-specific claims."""
+        claims = super().validate_token(token)
+
+        # Validate OIDC-specific claims
+        if claims.get('aud') != self.client_id:
+            raise ValueError("Invalid audience claim")
+
+        # Extract Preset-specific claims
+        claims['preset_tenant_id'] = claims.get('tenant_id')
+        claims['preset_workspace_id'] = claims.get('workspace_id')
+        claims['preset_roles'] = claims.get('roles', [])
+
+        return claims
+
+    def resolve_user(self, claims: Dict[str, Any]) -> Any:
+        """Resolve Superset user from OIDC claims."""
+        from preset.auth.user_resolver import resolve_preset_user
+
+        return resolve_preset_user(
+            subject=claims['sub'],
+            email=claims.get('email'),
+            tenant_id=claims.get('preset_tenant_id'),
+            roles=claims.get('preset_roles', [])
+        )
+```
+
+### Configuration for OIDC
+
+```python
+# In preset_config.py
+def create_preset_oidc_auth(app):
+    """Factory for Preset OIDC authentication."""
+    from preset.mcp.oidc import PresetOIDCAuthProvider
+
+    return PresetOIDCAuthProvider(
+        oidc_discovery_url=app.config["PRESET_OIDC_DISCOVERY_URL"],
+        client_id=app.config["PRESET_OIDC_CLIENT_ID"],
+        client_secret=app.config["PRESET_OIDC_CLIENT_SECRET"],
+        audience=app.config["PRESET_MCP_AUDIENCE"],
+        required_scopes=app.config.get("PRESET_MCP_REQUIRED_SCOPES", [])
+    )
+
+# MCP Configuration
+MCP_AUTH_ENABLED = True
+MCP_AUTH_FACTORY = create_preset_oidc_auth
+
+# OIDC Configuration
+PRESET_OIDC_DISCOVERY_URL = "https://auth.preset.io/.well-known/openid_configuration"
+PRESET_OIDC_CLIENT_ID = "preset-mcp-service"
+PRESET_OIDC_CLIENT_SECRET = os.environ.get("PRESET_OIDC_CLIENT_SECRET")
+PRESET_MCP_AUDIENCE = "preset-superset-mcp"
+PRESET_MCP_REQUIRED_SCOPES = [
+    "openid", "profile", "email",
+    "superset:read", "superset:write"
+]
+```
+
+## Preset-Specific Tools
+
+### Tenant Management Tools
+
+```python
+# preset/mcp/tools/tenant.py
+@mcp.tool
+@preset_tenant_auth_hook(['tenant:read'])
+def get_tenant_info(request: GetTenantInfoRequest) -> TenantInfoResponse:
+    """Get Preset tenant information and quotas."""
+
+    tenant_id = g.mcp_tenant_id
+    tenant = get_tenant_by_id(tenant_id)
+
+    return TenantInfoResponse(
+        tenant_id=tenant.id,
+        name=tenant.name,
+        plan=tenant.plan,
+        quotas=tenant.quotas,
+        usage=get_tenant_usage(tenant_id),
+        workspaces=list_tenant_workspaces(tenant_id)
+    )
+
+@mcp.tool
+@preset_tenant_auth_hook(['workspace:read'])
+def list_workspace_assets(request: ListWorkspaceAssetsRequest) -> ListWorkspaceAssetsResponse:
+    """List all assets in a Preset workspace."""
+
+    workspace_id = request.workspace_id
+    tenant_id = g.mcp_tenant_id
+
+    # Validate workspace belongs to tenant
+    validate_workspace_access(workspace_id, tenant_id)
+
+    assets = {
+        'dashboards': list_workspace_dashboards(workspace_id),
+        'charts': list_workspace_charts(workspace_id),
+        'datasets': list_workspace_datasets(workspace_id)
+    }
+
+    return ListWorkspaceAssetsResponse(
+        workspace_id=workspace_id,
+        assets=assets,
+        total_count=sum(len(v) for v in assets.values())
+    )
+```
+
+### Embed Token Generation
+
+```python
+# preset/mcp/tools/embed.py
+@mcp.tool
+@preset_tenant_auth_hook(['dashboard:embed'])
+def generate_embed_token(request: GenerateEmbedTokenRequest) -> EmbedTokenResponse:
+    """Generate secure embed token for dashboard/chart."""
+
+    # Validate resource access
+    resource = validate_embed_resource_access(
+        resource_type=request.resource_type,
+        resource_id=request.resource_id,
+        tenant_id=g.mcp_tenant_id
+    )
+
+    # Generate signed embed token
+    embed_token = create_embed_token(
+        resource=resource,
+        user_id=g.user.id,
+        tenant_id=g.mcp_tenant_id,
+        permissions=request.permissions,
+        expiry=request.expiry_hours
+    )
+
+    return EmbedTokenResponse(
+        embed_token=embed_token,
+        embed_url=f"{get_preset_base_url()}/embed/{embed_token}",
+        expires_at=embed_token.expires_at
+    )
+```
+
+## Audit and Compliance Extensions
+
+### Enhanced Audit Logging
+
+```python
+# preset/mcp/audit.py
+from superset.mcp_service.auth import get_audit_context
+
+def create_preset_audit_context(user_context: dict, tool_name: str,
+                               request_data: dict) -> dict:
+    """Create Preset-specific audit context."""
+
+    base_context = get_audit_context(user_context, tool_name, request_data)
+
+    # Add Preset-specific fields
+    preset_context = {
+        **base_context,
+        'tenant_id': user_context.get('tenant_id'),
+        'workspace_id': user_context.get('workspace_id'),
+        'preset_user_role': user_context.get('preset_role'),
+        'data_classification': classify_request_data(request_data),
+        'compliance_flags': get_compliance_flags(tool_name, request_data)
+    }
+
+    return preset_context
+
+def log_preset_mcp_access(audit_context: dict):
+    """Log MCP access to Preset audit systems."""
+
+    # Log to Superset's audit system
+    log_superset_audit_event(audit_context)
+
+    # Log to Preset's compliance system
+    log_preset_compliance_event(audit_context)
+
+    # Log to external SIEM if configured
+    if app.config.get('PRESET_SIEM_ENABLED'):
+        log_to_siem(audit_context)
+```
+
+### Data Classification
+
+```python
+# preset/mcp/classification.py
+def classify_request_data(request_data: dict) -> dict:
+    """Classify data sensitivity in MCP requests."""
+
+    classification = {
+        'contains_pii': False,
+        'data_level': 'public',
+        'retention_policy': 'standard'
+    }
+
+    # Check for PII in request
+    if contains_pii_fields(request_data):
+        classification['contains_pii'] = True
+        classification['data_level'] = 'restricted'
+        classification['retention_policy'] = 'pii_compliant'
+
+    # Check for sensitive datasets
+    if references_sensitive_datasets(request_data):
+        classification['data_level'] = 'confidential'
+
+    return classification
+```
+
+## Deployment Considerations
+
+### Multi-Region Deployment
+
+```python
+# preset/mcp/deployment.py
+def get_region_specific_config():
+    """Get region-specific MCP configuration."""
+
+    region = os.environ.get('PRESET_REGION', 'us-east-1')
+
+    config_map = {
+        'us-east-1': {
+            'jwks_uri': 'https://auth-us.preset.io/.well-known/jwks.json',
+            'base_url': 'https://app.preset.io',
+            'data_residency': 'US'
+        },
+        'eu-west-1': {
+            'jwks_uri': 'https://auth-eu.preset.io/.well-known/jwks.json',
+            'base_url': 'https://eu.preset.io',
+            'data_residency': 'EU'
+        }
+    }
+
+    return config_map.get(region, config_map['us-east-1'])
+
+# Usage in config
+region_config = get_region_specific_config()
+PRESET_JWKS_URI = region_config['jwks_uri']
+SUPERSET_WEBSERVER_ADDRESS = region_config['base_url']
+```
+
+### Health Check Extensions
+
+```python
+# preset/mcp/health.py
+@mcp.tool
+def preset_health_check() -> HealthCheckResponse:
+    """Preset-specific health check for MCP service."""
+
+    checks = {
+        'mcp_service': check_mcp_service_health(),
+        'database': check_database_health(),
+        'auth_provider': check_auth_provider_health(),
+        'tenant_isolation': check_tenant_isolation(),
+        'rls_engine': check_rls_engine_health()
+    }
+
+    overall_status = 'healthy' if all(
+        check['status'] == 'healthy' for check in checks.values()
+    ) else 'degraded'
+
+    return HealthCheckResponse(
+        status=overall_status,
+        checks=checks,
+        region=os.environ.get('PRESET_REGION'),
+        version=get_preset_mcp_version()
+    )
+```
+
+## Configuration Templates
+
+### Production Configuration
+
+```python
+# preset_production_config.py
+from preset.mcp.auth import create_preset_oidc_auth
+from preset.mcp.audit import create_preset_audit_context
+
+# MCP Service Configuration
+MCP_AUTH_ENABLED = True
+MCP_AUTH_FACTORY = create_preset_oidc_auth
+MCP_AUDIT_CONTEXT_FACTORY = create_preset_audit_context
+
+# Preset OIDC Configuration
+PRESET_OIDC_DISCOVERY_URL = "https://auth.preset.io/.well-known/openid_configuration"
+PRESET_OIDC_CLIENT_ID = "preset-mcp-production"
+PRESET_MCP_AUDIENCE = "preset-superset-mcp"
+
+# Security Configuration
+PRESET_MCP_REQUIRED_SCOPES = [
+    "openid", "profile", "email",
+    "tenant:read", "workspace:read",
+    "dashboard:read", "chart:read", "dataset:read"
+]
+
+# Audit Configuration
+PRESET_AUDIT_ENABLED = True
+PRESET_SIEM_ENABLED = True
+PRESET_COMPLIANCE_MODE = "SOC2"
+
+# Performance Configuration
+PRESET_MCP_CACHE_ENABLED = True
+PRESET_MCP_RATE_LIMIT = "1000/hour"
+PRESET_MCP_TIMEOUT = 30
+```
+
+This integration guide provides the Preset.io team with concrete extension points for implementing enterprise features while maintaining compatibility with the base MCP service architecture.

docs/docs/security/cves.mdx

@@ -2,20 +2,6 @@
 title: CVEs fixed by release
 sidebar_position: 2
 ---
-#### Version 5.0.0
-
-| CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
-| CVE-2025-55673 | Exposure of Sensitive Information to an Unauthorized Actor                         |  < 5.0.0 |
-| CVE-2025-55674 | Improper Neutralization of Special Elements used in an SQL Command                 |  < 5.0.0 |
-| CVE-2025-55675 | Improper Access Control leading to Information Disclosure                          |  < 5.0.0 |
-
-#### Version 4.1.3
-
-| CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
-| CVE-2025-55672 | Improper Neutralization of Input During Web Page Generation                        |  < 4.1.3 |
-
 #### Version 4.1.2
 
 | CVE            | Title                                                                              | Affected |

docs/docusaurus.config.ts

@@ -20,125 +20,16 @@
 import type { Config } from '@docusaurus/types';
 import type { Options, ThemeConfig } from '@docusaurus/preset-classic';
 import { themes } from 'prism-react-renderer';
-import remarkImportPartial from 'remark-import-partial';
-import * as fs from 'fs';
-import * as path from 'path';
 
 const { github: lightCodeTheme, vsDark: darkCodeTheme } = themes;
 
-// Load version configuration from external file
-const versionsConfigPath = path.join(__dirname, 'versions-config.json');
-const versionsConfig = JSON.parse(fs.readFileSync(versionsConfigPath, 'utf8'));
-
-// Build plugins array dynamically based on disabled flags
-const dynamicPlugins = [];
-
-// Add components plugin if not disabled
-if (!versionsConfig.components.disabled) {
-  dynamicPlugins.push([
-    '@docusaurus/plugin-content-docs',
-    {
-      id: 'components',
-      path: 'components',
-      routeBasePath: 'components',
-      sidebarPath: require.resolve('./sidebarComponents.js'),
-      editUrl:
-        'https://github.com/apache/superset/edit/master/docs/components',
-      remarkPlugins: [remarkImportPartial],
-      docItemComponent: '@theme/DocItem',
-      includeCurrentVersion: versionsConfig.components.includeCurrentVersion,
-      lastVersion: versionsConfig.components.lastVersion,
-      onlyIncludeVersions: versionsConfig.components.onlyIncludeVersions,
-      versions: versionsConfig.components.versions,
-      disableVersioning: false,
-      showLastUpdateAuthor: true,
-      showLastUpdateTime: true,
-    },
-  ]);
-}
-
-// Add developer_portal plugin if not disabled
-if (!versionsConfig.developer_portal.disabled) {
-  dynamicPlugins.push([
-    '@docusaurus/plugin-content-docs',
-    {
-      id: 'developer_portal',
-      path: 'developer_portal',
-      routeBasePath: 'developer_portal',
-      sidebarPath: require.resolve('./sidebarTutorials.js'),
-      editUrl:
-        'https://github.com/apache/superset/edit/master/docs/developer_portal',
-      remarkPlugins: [remarkImportPartial],
-      docItemComponent: '@theme/DocItem',
-      includeCurrentVersion: versionsConfig.developer_portal.includeCurrentVersion,
-      lastVersion: versionsConfig.developer_portal.lastVersion,
-      onlyIncludeVersions: versionsConfig.developer_portal.onlyIncludeVersions,
-      versions: versionsConfig.developer_portal.versions,
-      disableVersioning: false,
-      showLastUpdateAuthor: true,
-      showLastUpdateTime: true,
-    },
-  ]);
-}
-
-// Build navbar items dynamically based on disabled flags
-const dynamicNavbarItems = [];
-
-// Add Component Playground navbar item if not disabled
-if (!versionsConfig.components.disabled) {
-  dynamicNavbarItems.push({
-    label: 'Component Playground',
-    to: '/components',
-    items: [
-      {
-        label: 'Introduction',
-        to: '/components',
-      },
-      {
-        label: 'UI Components',
-        to: '/components/ui-components/button',
-      },
-      {
-        label: 'Chart Components',
-        to: '/components/chart-components/bar-chart',
-      },
-      {
-        label: 'Layout Components',
-        to: '/components/layout-components/grid',
-      },
-    ],
-  });
-}
-
-// Add Developer Portal navbar item if not disabled
-if (!versionsConfig.developer_portal.disabled) {
-  dynamicNavbarItems.push({
-    label: 'Developer Portal',
-    position: 'left',
-    items: [
-      {
-        type: 'doc',
-        docsPluginId: 'developer_portal',
-        docId: 'index',
-        label: 'Introduction',
-      },
-      {
-        type: 'doc',
-        docsPluginId: 'developer_portal',
-        docId: 'getting-started/index',
-        label: 'Getting Started',
-      },
-    ],
-  });
-}
-
 const config: Config = {
   title: 'Superset',
   tagline:
     'Apache Superset is a modern data exploration and visualization platform',
   url: 'https://superset.apache.org',
   baseUrl: '/',
-  onBrokenLinks: 'warn',
+  onBrokenLinks: 'throw',
   onBrokenMarkdownLinks: 'throw',
   markdown: {
     mermaid: true,
@@ -148,7 +39,6 @@ const config: Config = {
   projectName: 'superset',
   themes: ['@saucelabs/theme-github-codeblock', '@docusaurus/theme-mermaid'],
   plugins: [
-    require.resolve('./src/webpack.extend.ts'),
     [
       'docusaurus-plugin-less',
       {
@@ -157,10 +47,11 @@ const config: Config = {
         },
       },
     ],
-    ...dynamicPlugins,
     [
       '@docusaurus/plugin-client-redirects',
       {
+        fromExtensions: ['html', 'htm'],
+        toExtensions: ['exe', 'zip'],
         redirects: [
           {
             to: '/docs/installation/docker-compose',
@@ -319,13 +210,6 @@ const config: Config = {
             }
             return `https://github.com/apache/superset/edit/master/docs/${versionDocsDirPath}/${docPath}`;
           },
-          includeCurrentVersion: versionsConfig.docs.includeCurrentVersion,
-          lastVersion: versionsConfig.docs.lastVersion,  // Make 'next' the default
-          onlyIncludeVersions: versionsConfig.docs.onlyIncludeVersions,
-          versions: versionsConfig.docs.versions,
-          disableVersioning: false,
-          showLastUpdateAuthor: true,
-          showLastUpdateTime: true,
         },
         blog: {
           showReadingTime: true,
@@ -351,13 +235,6 @@ const config: Config = {
       apiKey: 'd0d22810f2e9b614ffac3a73b26891fe',
       indexName: 'superset-apache',
     },
-    mermaid: {
-      theme: { light: 'neutral', dark: 'dark' },
-      options: {
-        // Any Mermaid config options go here...
-        maxTextSize: 100000,
-      },
-    },
     navbar: {
       logo: {
         alt: 'Superset Logo',
@@ -367,22 +244,20 @@ const config: Config = {
       items: [
         {
           label: 'Documentation',
-          position: 'left',
+          to: '/docs/intro',
           items: [
             {
-              type: 'doc',
-              docId: 'intro',
               label: 'Getting Started',
+              to: '/docs/intro',
             },
             {
-              type: 'doc',
-              docId: 'faq',
               label: 'FAQ',
+              to: '/docs/faq',
             },
           ],
         },
         {
-          label: 'Community Resources',
+          label: 'Community',
           to: '/community',
           items: [
             {
@@ -407,7 +282,6 @@ const config: Config = {
             },
           ],
         },
-        ...dynamicNavbarItems,
         {
           href: '/docs/intro',
           position: 'right',
@@ -462,6 +336,7 @@ const config: Config = {
     //   src: 'https://www.bugherd.com/sidebarv2.js?apikey=enilpiu7bgexxsnoqfjtxa',
     //   async: true,
     // },
+    '/script/matomo.js',
     {
       src: 'https://widget.kapa.ai/kapa-widget.bundle.js',
       async: true,

docs/eslint.config.js

@@ -28,9 +28,6 @@ const globals = require('globals');
 const { defineConfig, globalIgnores } = require('eslint/config');
 
 module.exports = defineConfig([
-  {
-    files: ['**/*.{js,jsx,ts,tsx}'],
-  },
   globalIgnores(['build/**/*', '.docusaurus/**/*', 'node_modules/**/*']),
   js.configs.recommended,
   ...ts.configs.recommended,
@@ -39,7 +36,7 @@ module.exports = defineConfig([
     files: ['eslint.config.js'],
     rules: {
       '@typescript-eslint/no-require-imports': 'off',
-    },
+    }
   },
   {
     languageOptions: {
@@ -71,5 +68,5 @@ module.exports = defineConfig([
         version: 'detect',
       },
     },
-  },
-]);
+  }
+])

docs/package.json

@@ -6,8 +6,7 @@
   "scripts": {
     "docusaurus": "docusaurus",
     "_init": "cat src/intro_header.txt ../README.md > docs/intro.md",
-    "start": "yarn run _init && NODE_ENV=development docusaurus start",
-    "stop": "pkill -f 'docusaurus start' || echo 'No docusaurus server running'",
+    "start": "yarn run _init && docusaurus start",
     "build": "yarn run _init && DEBUG=docusaurus:* docusaurus build",
     "swizzle": "docusaurus swizzle",
     "deploy": "docusaurus deploy",
@@ -16,73 +15,44 @@
     "write-translations": "docusaurus write-translations",
     "write-heading-ids": "docusaurus write-heading-ids",
     "typecheck": "tsc",
-    "eslint": "eslint .",
-    "version:add": "node scripts/manage-versions.mjs add",
-    "version:remove": "node scripts/manage-versions.mjs remove",
-    "version:add:docs": "node scripts/manage-versions.mjs add docs",
-    "version:add:developer_portal": "node scripts/manage-versions.mjs add developer_portal",
-    "version:add:components": "node scripts/manage-versions.mjs add components",
-    "version:remove:docs": "node scripts/manage-versions.mjs remove docs",
-    "version:remove:developer_portal": "node scripts/manage-versions.mjs remove developer_portal",
-    "version:remove:components": "node scripts/manage-versions.mjs remove components"
+    "eslint": "eslint . --ext .js,.jsx,.ts,.tsx"
   },
   "dependencies": {
     "@ant-design/icons": "^6.0.0",
     "@docusaurus/core": "3.8.1",
     "@docusaurus/plugin-client-redirects": "3.8.1",
     "@docusaurus/preset-classic": "3.8.1",
-    "@docusaurus/theme-mermaid": "^3.8.1",
-    "@emotion/core": "^10.0.27",
-    "@emotion/react": "^11.13.3",
+    "@docusaurus/theme-mermaid": "3.8.1",
     "@emotion/styled": "^10.0.27",
-    "@mdx-js/react": "^3.1.1",
     "@saucelabs/theme-github-codeblock": "^0.3.0",
-    "@storybook/addon-docs": "^8.6.11",
-    "@storybook/blocks": "^8.6.11",
-    "@storybook/channels": "^8.6.11",
-    "@storybook/client-logger": "^8.6.11",
-    "@storybook/components": "^8.6.11",
-    "@storybook/core": "^8.6.11",
-    "@storybook/core-events": "^8.6.11",
-    "@storybook/csf": "^0.1.13",
-    "@storybook/docs-tools": "^8.6.11",
-    "@storybook/preview-api": "^8.6.11",
-    "@storybook/theming": "^8.6.11",
-    "@superset-ui/core": "^0.20.4",
-    "antd": "^5.26.7",
-    "caniuse-lite": "^1.0.30001739",
+    "@superset-ui/style": "^0.14.23",
+    "antd": "^5.26.3",
     "docusaurus-plugin-less": "^2.0.2",
-    "json-bigint": "^1.0.0",
-    "less": "^4.4.0",
+    "less": "^4.3.0",
     "less-loader": "^12.3.0",
     "prism-react-renderer": "^2.4.1",
     "react": "^18.3.1",
     "react-dom": "^18.3.1",
     "react-github-btn": "^1.4.0",
     "react-svg-pan-zoom": "^3.13.1",
-    "remark-import-partial": "^0.0.2",
-    "reselect": "^5.1.1",
-    "storybook": "^8.6.11",
-    "swagger-ui-react": "^5.27.1",
-    "tinycolor2": "^1.4.2",
-    "ts-loader": "^9.5.2"
+    "swagger-ui-react": "^5.26.0"
   },
   "devDependencies": {
     "@docusaurus/module-type-aliases": "^3.8.1",
     "@docusaurus/tsconfig": "^3.8.1",
-    "@eslint/js": "^9.32.0",
+    "@eslint/js": "^9.31.0",
     "@types/react": "^19.1.8",
     "@typescript-eslint/eslint-plugin": "^8.37.0",
     "@typescript-eslint/parser": "^8.37.0",
-    "eslint": "^9.34.0",
-    "eslint-config-prettier": "^10.1.8",
-    "eslint-plugin-prettier": "^5.5.3",
+    "eslint": "^9.31.0",
+    "eslint-config-prettier": "^10.1.5",
+    "eslint-plugin-prettier": "^5.5.1",
     "eslint-plugin-react": "^7.37.5",
     "globals": "^16.3.0",
     "prettier": "^3.6.2",
-    "typescript": "~5.9.2",
-    "typescript-eslint": "^8.39.0",
-    "webpack": "^5.101.0"
+    "typescript": "~5.8.3",
+    "typescript-eslint": "^8.37.0",
+    "webpack": "^5.99.9"
   },
   "browserslist": {
     "production": [

docs/scripts/manage-versions.mjs

@@ -1,242 +0,0 @@
-#!/usr/bin/env node
-
-/**
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-import fs from 'fs';
-import path from 'path';
-import { execSync } from 'child_process';
-import { fileURLToPath } from 'url';
-
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = path.dirname(__filename);
-
-const CONFIG_FILE = path.join(__dirname, '..', 'versions-config.json');
-
-// Parse command line arguments
-const args = process.argv.slice(2);
-const command = args[0]; // 'add' or 'remove'
-const section = args[1]; // 'docs', 'developer_portal', or 'components'
-const version = args[2]; // version string like '1.2.0'
-
-function loadConfig() {
-  return JSON.parse(fs.readFileSync(CONFIG_FILE, 'utf8'));
-}
-
-function saveConfig(config) {
-  fs.writeFileSync(CONFIG_FILE, JSON.stringify(config, null, 2) + '\n');
-}
-
-function fixVersionedImports(version) {
-  const versionedDocsPath = path.join(__dirname, '..', 'versioned_docs', `version-${version}`);
-
-  // Files that need import path fixes
-  const filesToFix = [
-    'contributing/resources.mdx',
-    'configuration/country-map-tools.mdx'
-  ];
-
-  console.log(`  Fixing relative imports in versioned docs...`);
-
-  filesToFix.forEach(filePath => {
-    const fullPath = path.join(versionedDocsPath, filePath);
-    if (fs.existsSync(fullPath)) {
-      let content = fs.readFileSync(fullPath, 'utf8');
-
-      // Fix imports that go up two directories to go up three instead
-      content = content.replace(
-        /from ['"]\.\.\/\.\.\/src\//g,
-        "from '../../../src/"
-      );
-      content = content.replace(
-        /from ['"]\.\.\/\.\.\/data\//g,
-        "from '../../../data/"
-      );
-
-      fs.writeFileSync(fullPath, content);
-      console.log(`    Fixed imports in ${filePath}`);
-    }
-  });
-}
-
-function addVersion(section, version) {
-  const config = loadConfig();
-
-  if (!config[section]) {
-    console.error(`Section '${section}' not found in config`);
-    process.exit(1);
-  }
-
-  // Check if version already exists
-  if (config[section].onlyIncludeVersions.includes(version)) {
-    console.error(`Version ${version} already exists in ${section}`);
-    process.exit(1);
-  }
-
-  console.log(`Creating version ${version} for ${section}...`);
-
-  // Run Docusaurus version command
-  const docusaurusCommand = section === 'docs'
-    ? `yarn docusaurus docs:version ${version}`
-    : `yarn docusaurus docs:version:${section} ${version}`;
-
-  try {
-    execSync(docusaurusCommand, { stdio: 'inherit' });
-  } catch (error) {
-    console.error(`Failed to create version: ${error.message}`);
-    process.exit(1);
-  }
-
-  // Fix relative imports in versioned docs (for main docs section only)
-  if (section === 'docs') {
-    fixVersionedImports(version);
-  }
-
-  // Update config
-  // Add to onlyIncludeVersions array (after 'current')
-  const versionIndex = config[section].onlyIncludeVersions.indexOf('current') + 1;
-  config[section].onlyIncludeVersions.splice(versionIndex, 0, version);
-
-  // Add version metadata
-  const versionPath = section === 'docs' ? version : version;
-  config[section].versions[version] = {
-    label: version,
-    path: versionPath,
-    banner: 'none'
-  };
-
-  // Optionally update lastVersion if this is the first non-current version
-  if (config[section].onlyIncludeVersions.length === 2) {
-    config[section].lastVersion = version;
-  }
-
-  saveConfig(config);
-  console.log(`✅ Version ${version} added successfully to ${section}`);
-  console.log(`📝 Updated versions-config.json`);
-}
-
-function removeVersion(section, version) {
-  const config = loadConfig();
-
-  if (!config[section]) {
-    console.error(`Section '${section}' not found in config`);
-    process.exit(1);
-  }
-
-  if (version === 'current') {
-    console.error(`Cannot remove 'current' version`);
-    process.exit(1);
-  }
-
-  if (!config[section].onlyIncludeVersions.includes(version)) {
-    console.error(`Version ${version} not found in ${section}`);
-    process.exit(1);
-  }
-
-  console.log(`Removing version ${version} from ${section}...`);
-
-  // Determine file paths based on section
-  const versionedDocsDir = section === 'docs'
-    ? `versioned_docs/version-${version}`
-    : `${section}_versioned_docs/version-${version}`;
-
-  const versionedSidebarsFile = section === 'docs'
-    ? `versioned_sidebars/version-${version}-sidebars.json`
-    : `${section}_versioned_sidebars/version-${version}-sidebars.json`;
-
-  // Remove versioned files
-  const docsPath = path.join(__dirname, '..', versionedDocsDir);
-  const sidebarsPath = path.join(__dirname, '..', versionedSidebarsFile);
-
-  if (fs.existsSync(docsPath)) {
-    fs.rmSync(docsPath, { recursive: true });
-    console.log(`  Removed ${versionedDocsDir}`);
-  }
-
-  if (fs.existsSync(sidebarsPath)) {
-    fs.unlinkSync(sidebarsPath);
-    console.log(`  Removed ${versionedSidebarsFile}`);
-  }
-
-  // Update versions.json file
-  const versionsJsonFile = section === 'docs'
-    ? 'versions.json'
-    : `${section}_versions.json`;
-  const versionsJsonPath = path.join(__dirname, '..', versionsJsonFile);
-
-  if (fs.existsSync(versionsJsonPath)) {
-    const versions = JSON.parse(fs.readFileSync(versionsJsonPath, 'utf8'));
-    const versionIndex = versions.indexOf(version);
-    if (versionIndex > -1) {
-      versions.splice(versionIndex, 1);
-      fs.writeFileSync(versionsJsonPath, JSON.stringify(versions, null, 2) + '\n');
-      console.log(`  Updated ${versionsJsonFile}`);
-    }
-  }
-
-  // Update config
-  const versionIndex = config[section].onlyIncludeVersions.indexOf(version);
-  config[section].onlyIncludeVersions.splice(versionIndex, 1);
-  delete config[section].versions[version];
-
-  // Update lastVersion if needed
-  if (config[section].lastVersion === version) {
-    // Set to the next available version or 'current'
-    const remainingVersions = config[section].onlyIncludeVersions.filter(v => v !== 'current');
-    config[section].lastVersion = remainingVersions.length > 0 ? remainingVersions[0] : 'current';
-    console.log(`  Updated lastVersion to ${config[section].lastVersion}`);
-  }
-
-  saveConfig(config);
-  console.log(`✅ Version ${version} removed successfully from ${section}`);
-  console.log(`📝 Updated versions-config.json`);
-}
-
-function printUsage() {
-  console.log(`
-Usage:
-  node scripts/manage-versions.js add <section> <version>
-  node scripts/manage-versions.js remove <section> <version>
-
-Where:
-  - section: 'docs', 'developer_portal', or 'components'
-  - version: version string (e.g., '1.2.0', '2.0.0')
-
-Examples:
-  node scripts/manage-versions.js add docs 2.0.0
-  node scripts/manage-versions.js add developer_portal 1.3.0
-  node scripts/manage-versions.js remove components 1.0.0
-`);
-}
-
-// Main execution
-if (!command || !section || !version) {
-  printUsage();
-  process.exit(1);
-}
-
-if (command === 'add') {
-  addVersion(section, version);
-} else if (command === 'remove') {
-  removeVersion(section, version);
-} else {
-  console.error(`Unknown command: ${command}`);
-  printUsage();
-  process.exit(1);
-}

docs/sidebarComponents.js

@@ -1,68 +0,0 @@
-/* eslint-env node */
-/**
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-// @ts-check
-
-/** @type {import('@docusaurus/plugin-content-docs').SidebarsConfig} */
-const sidebars = {
-  // By default, Docusaurus generates a sidebar from the docs folder structure
-  //tutorialSidebar: [{type: 'autogenerated', dirName: '.'}],
-
-  // But we're not doing that.
-  ComponentSidebar: [
-    {
-      type: 'doc',
-      label: 'Introduction',
-      id: 'index',
-    },
-    {
-      type: 'category',
-      label: 'UI Components',
-      items: [
-        {
-          type: 'autogenerated',
-          dirName: 'ui-components',
-        },
-      ],
-    },
-    {
-      type: 'category',
-      label: 'Chart Components',
-      items: [
-        {
-          type: 'autogenerated',
-          dirName: 'chart-components',
-        },
-      ],
-    },
-    {
-      type: 'category',
-      label: 'Layout Components',
-      items: [
-        {
-          type: 'autogenerated',
-          dirName: 'layout-components',
-        },
-      ],
-    },
-  ],
-};
-
-module.exports = sidebars;

docs/sidebarTutorials.js

@@ -1,48 +0,0 @@
-/* eslint-env node */
-/**
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-// @ts-check
-
-/** @type {import('@docusaurus/plugin-content-docs').SidebarsConfig} */
-const sidebars = {
-  // By default, Docusaurus generates a sidebar from the docs folder structure
-  //tutorialSidebar: [{type: 'autogenerated', dirName: '.'}],
-
-  // But we're not doing that.
-  TutorialsSidebar: [
-    {
-      type: 'doc',
-      label: 'Introduction',
-      id: 'index',
-    },
-    {
-      type: 'category',
-      label: 'Getting Started',
-      items: [
-        {
-          type: 'autogenerated',
-          dirName: 'getting-started',
-        },
-      ],
-    },
-  ],
-};
-
-module.exports = sidebars;

docs/sidebars.js

@@ -87,6 +87,16 @@ const sidebars = {
         },
       ],
     },
+    {
+      type: 'category',
+      label: 'MCP Service',
+      items: [
+        {
+          type: 'autogenerated',
+          dirName: 'mcp-service',
+        },
+      ],
+    },
     {
       type: 'doc',
       label: 'FAQ',

docs/src/components/Button.jsx

@@ -1,23 +0,0 @@
-/**
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-// Re-export the Button component as a default export
-import { Button } from '../../../superset-frontend/packages/superset-ui-core/src/components/Button';
-
-export default Button;

docs/src/components/StorybookWrapper.jsx

@@ -1,121 +0,0 @@
-/**
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-import React from 'react';
-import { supersetTheme, ThemeProvider } from '@superset-ui/core';
-
-// A simple component to display a story example
-export function StoryExample({ component: Component, props = {} }) {
-  return (
-    <ThemeProvider theme={supersetTheme}>
-      <div
-        className="storybook-example"
-        style={{
-          border: '1px solid #e8e8e8',
-          borderRadius: '4px',
-          padding: '20px',
-          marginBottom: '20px',
-        }}
-      >
-        {Component && <Component {...props} />}
-      </div>
-    </ThemeProvider>
-  );
-}
-
-// A simple component to display a story with controls
-export function StoryWithControls({
-  component: Component,
-  props = {},
-  controls = [],
-}) {
-  const [stateProps, setStateProps] = React.useState(props);
-
-  const updateProp = (key, value) => {
-    setStateProps(prev => ({
-      ...prev,
-      [key]: value,
-    }));
-  };
-
-  return (
-    <ThemeProvider theme={supersetTheme}>
-      <div className="storybook-with-controls">
-        <div
-          className="storybook-example"
-          style={{
-            border: '1px solid #e8e8e8',
-            borderRadius: '4px',
-            padding: '20px',
-            marginBottom: '20px',
-          }}
-        >
-          {Component && <Component {...stateProps} />}
-        </div>
-
-        {controls.length > 0 && (
-          <div
-            className="storybook-controls"
-            style={{
-              border: '1px solid #e8e8e8',
-              borderRadius: '4px',
-              padding: '20px',
-              marginBottom: '20px',
-            }}
-          >
-            <h4>Controls</h4>
-            {controls.map(control => (
-              <div key={control.name} style={{ marginBottom: '10px' }}>
-                <label style={{ display: 'block', marginBottom: '5px' }}>
-                  {control.label || control.name}:
-                </label>
-                {control.type === 'select' ? (
-                  <select
-                    value={stateProps[control.name]}
-                    onChange={e => updateProp(control.name, e.target.value)}
-                    style={{ width: '100%', padding: '5px' }}
-                  >
-                    {control.options.map(option => (
-                      <option key={option} value={option}>
-                        {option}
-                      </option>
-                    ))}
-                  </select>
-                ) : control.type === 'boolean' ? (
-                  <input
-                    type="checkbox"
-                    checked={stateProps[control.name]}
-                    onChange={e => updateProp(control.name, e.target.checked)}
-                  />
-                ) : (
-                  <input
-                    type="text"
-                    value={stateProps[control.name]}
-                    onChange={e => updateProp(control.name, e.target.value)}
-                    style={{ width: '100%', padding: '5px' }}
-                  />
-                )}
-              </div>
-            ))}
-          </div>
-        )}
-      </div>
-    </ThemeProvider>
-  );
-}

docs/src/pages/index.tsx

@@ -460,23 +460,15 @@ export default function Home(): JSX.Element {
   const changeToDark = () => {
     const navbar = document.body.querySelector('.navbar');
     const logo = document.body.querySelector('.navbar__logo img');
-    if (navbar) {
-      navbar.classList.add('navbar--dark');
-    }
-    if (logo) {
-      logo.setAttribute('src', '/img/superset-logo-horiz-dark.svg');
-    }
+    navbar.classList.add('navbar--dark');
+    logo.setAttribute('src', '/img/superset-logo-horiz-dark.svg');
   };
 
   const changeToLight = () => {
     const navbar = document.body.querySelector('.navbar');
     const logo = document.body.querySelector('.navbar__logo img');
-    if (navbar) {
-      navbar.classList.remove('navbar--dark');
-    }
-    if (logo) {
-      logo.setAttribute('src', '/img/superset-logo-horiz.svg');
-    }
+    navbar.classList.remove('navbar--dark');
+    logo.setAttribute('src', '/img/superset-logo-horiz.svg');
   };
 
   // Set up dark <-> light navbar change
@@ -484,9 +476,7 @@ export default function Home(): JSX.Element {
     changeToDark();
 
     const navbarToggle = document.body.querySelector('.navbar__toggle');
-    if (navbarToggle) {
-      navbarToggle.addEventListener('click', () => changeToLight());
-    }
+    navbarToggle.addEventListener('click', () => changeToLight());
 
     const scrollListener = () => {
       if (window.scrollY > 0) {

docs/src/styles/custom.css

@@ -45,60 +45,6 @@ ul.dropdown__menu svg {
   display: none;
 }
 
-/* Consistent dropdown styling for navbar */
-.navbar__item.dropdown .dropdown__menu {
-  background-color: white;
-  border: 1px solid rgba(0, 0, 0, 0.1);
-  box-shadow: 0 2px 8px rgba(0, 0, 0, 0.1);
-}
-
-.navbar__item.dropdown .dropdown__link {
-  color: #1c1e21 !important;
-  background-color: transparent !important;
-  border-radius: 0 !important;
-  padding: 0.5rem 1rem !important;
-  display: block !important;
-}
-
-.navbar__item.dropdown .dropdown__link:hover {
-  background-color: #f5f5f5 !important;
-  color: #1c1e21 !important;
-  text-decoration: none !important;
-}
-
-/* Remove the blue box styling for doc links in dropdowns */
-.navbar__item.dropdown .dropdown__link--active {
-  background-color: transparent !important;
-  color: #1c1e21 !important;
-}
-
-.navbar__item.dropdown .dropdown__link--active:hover {
-  background-color: #f5f5f5 !important;
-}
-
-/* Dark mode support */
-[data-theme='dark'] .navbar__item.dropdown .dropdown__menu {
-  background-color: #242526;
-  border: 1px solid rgba(255, 255, 255, 0.1);
-}
-
-[data-theme='dark'] .navbar__item.dropdown .dropdown__link {
-  color: #f5f6f7 !important;
-}
-
-[data-theme='dark'] .navbar__item.dropdown .dropdown__link:hover {
-  background-color: #3a3b3c !important;
-  color: #f5f6f7 !important;
-}
-
-[data-theme='dark'] .navbar__item.dropdown .dropdown__link--active {
-  color: #f5f6f7 !important;
-}
-
-[data-theme='dark'] .navbar__item.dropdown .dropdown__link--active:hover {
-  background-color: #3a3b3c !important;
-}
-
 :root {
   --ifm-color-primary: #20a7c9;
   --ifm-color-primary-dark: #1985a0;

docs/src/theme/DocVersionBadge/index.js

@@ -1,119 +0,0 @@
-/**
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-import React from 'react';
-import {
-  useActivePlugin,
-  useDocsVersion,
-  useVersions,
-} from '@docusaurus/plugin-content-docs/client';
-import { useLocation } from '@docusaurus/router';
-import { useDocsPreferredVersion } from '@docusaurus/theme-common';
-import { Dropdown } from 'antd';
-import { DownOutlined } from '@ant-design/icons';
-
-import styles from './styles.module.css';
-
-export default function DocVersionBadge() {
-  const activePlugin = useActivePlugin();
-  const { pathname } = useLocation();
-  const pluginId = activePlugin?.pluginId;
-  const [versionedPath, setVersionedPath] = React.useState('');
-
-  // Show version selector for all versioned sections
-  const isVersioned = [
-    'default',  // main docs
-    'components',
-    'tutorials',
-    'developer_portal',
-  ].includes(pluginId);
-
-  const { preferredVersion } = useDocsPreferredVersion(pluginId);
-  const versions = useVersions(pluginId);
-  const version = useDocsVersion();
-
-  // Extract the current page path relative to the version
-  React.useEffect(() => {
-    if (!pathname || !version || !pluginId) return;
-
-    let relativePath = '';
-    const basePath = pluginId === 'default' ? '/docs' : `/${pluginId}`;
-
-    // Handle different version path patterns
-    if (pathname.includes(basePath)) {
-      // Extract the part after the base path
-      const parts = pathname.split(basePath);
-      if (parts.length > 1) {
-        const afterBase = parts[1];
-        // For versioned paths, remove the version segment
-        if (afterBase.startsWith('/')) {
-          const segments = afterBase.substring(1).split('/');
-          // Check if first segment is a version (e.g., "1.1.0", "next")
-          if (segments[0] && (segments[0].match(/^\d+\.\d+\.\d+$/) || segments[0] === 'next')) {
-            // Skip the version segment
-            relativePath = segments.length > 1 ? '/' + segments.slice(1).join('/') : '';
-          } else {
-            // No version in path (e.g., /docs/intro for current version with empty path)
-            relativePath = afterBase;
-          }
-        }
-      }
-    }
-
-    setVersionedPath(relativePath);
-  }, [pathname, version, pluginId]);
-
-  // Create dropdown items for version selection
-  const items = versions.map(v => {
-    // Construct the URL for this version, preserving the current page
-    // v.path contains the full path including base, e.g., "/docs/1.1.0" or "/docs"
-    let versionUrl = v.path;
-
-    if (versionedPath) {
-      // Append the current page path to the version base
-      versionUrl = v.path + versionedPath;
-    }
-
-    return {
-      key: v.name,
-      label: (
-        <a href={versionUrl}>
-          {v.label}
-          {v.name === version.name && ' (current)'}
-          {v.name === preferredVersion?.name && ' (preferred)'}
-        </a>
-      ),
-    };
-  });
-
-  if (!isVersioned) {
-    return null;
-  }
-
-  return (
-    <span className={styles.versionBadge}>
-      Version:{' '}
-      <Dropdown menu={{ items }} trigger={['click']}>
-        <a onClick={e => e.preventDefault()} className={styles.versionSelector}>
-          {version.label} <DownOutlined />
-        </a>
-      </Dropdown>
-    </span>
-  );
-}

docs/src/theme/DocVersionBadge/styles.module.css

@@ -1,42 +0,0 @@
-/**
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-.versionBadge {
-  display: inline-flex;
-  align-items: center;
-  font-size: 0.8rem;
-  font-weight: 500;
-  color: var(--ifm-color-emphasis-700);
-  background-color: var(--ifm-color-emphasis-200);
-  border-radius: 0.5rem;
-  padding: 0.2rem 0.5rem;
-  margin-right: 0.5rem;
-}
-
-.versionSelector {
-  cursor: pointer;
-  color: var(--ifm-color-primary);
-  font-weight: 500;
-  margin-left: 0.25rem;
-}
-
-.versionSelector:hover {
-  text-decoration: none;
-  color: var(--ifm-color-primary-darker);
-}

docs/src/theme/DocVersionBanner/index.js

@@ -1,121 +0,0 @@
-/**
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-import React, { useState, useEffect } from 'react';
-import DocVersionBanner from '@theme-original/DocVersionBanner';
-import {
-  useActivePlugin,
-  useDocsVersion,
-  useVersions,
-} from '@docusaurus/plugin-content-docs/client';
-import { useLocation } from '@docusaurus/router';
-import { useDocsPreferredVersion } from '@docusaurus/theme-common';
-import { Dropdown } from 'antd';
-import { DownOutlined } from '@ant-design/icons';
-
-import styles from './styles.module.css';
-
-export default function DocVersionBannerWrapper(props) {
-  const activePlugin = useActivePlugin();
-  const { pathname } = useLocation();
-  const pluginId = activePlugin?.pluginId;
-  const [versionedPath, setVersionedPath] = useState('');
-
-  // Only show version selector for tutorials
-  // Main docs, components, and developer_portal use the DocVersionBadge component instead
-  const isVersioned = pluginId && ['tutorials'].includes(pluginId);
-
-  const { preferredVersion } = useDocsPreferredVersion(pluginId);
-  const versions = useVersions(pluginId);
-  const version = useDocsVersion();
-
-  // Early return if required data is not available
-  if (!isVersioned || !versions || !version) {
-    return <DocVersionBanner {...props} />;
-  }
-
-  // Extract the current page path relative to the version
-  useEffect(() => {
-    if (!pathname || !version || !pluginId) return;
-
-    let relativePath = '';
-
-    // Handle different version path patterns
-    if (pathname.includes(`/${pluginId}/`)) {
-      // Extract the part after the version
-      // Example: /components/1.1.0/ui-components/button -> /ui-components/button
-      const parts = pathname.split(`/${pluginId}/`);
-      if (parts.length > 1) {
-        const afterPluginId = parts[1];
-        // Find where the version part ends
-        const versionParts = afterPluginId.split('/');
-        if (versionParts.length > 1) {
-          // Remove the version part and join the rest
-          relativePath = '/' + versionParts.slice(1).join('/');
-        }
-      }
-    }
-
-    setVersionedPath(relativePath);
-  }, [pathname, version, pluginId]);
-
-  // Create dropdown items for version selection
-  const items = versions.map(v => {
-    // Construct the URL for this version, preserving the current page
-    // v.path is the version-specific path like "1.0.0" or "next"
-    let versionUrl = v.path;
-
-    if (versionedPath) {
-      // Construct the full URL with the version and the current page path
-      versionUrl = v.path + versionedPath;
-    }
-
-    return {
-      key: v.name,
-      label: (
-        <a href={versionUrl}>
-          {v.label}
-          {v.name === version.name && ' (current)'}
-          {v.name === preferredVersion?.name && ' (preferred)'}
-        </a>
-      ),
-    };
-  });
-
-  return (
-    <>
-      <DocVersionBanner {...props} />
-      {isVersioned && (
-        <div className={styles.versionBanner}>
-          <div className={styles.versionContainer}>
-            <span className={styles.versionLabel}>Version:</span>
-            <Dropdown menu={{ items }} trigger={['click']}>
-              <a
-                onClick={e => e.preventDefault()}
-                className={styles.versionSelector}
-              >
-                {version.label} <DownOutlined />
-              </a>
-            </Dropdown>
-          </div>
-        </div>
-      )}
-    </>
-  );
-}

docs/src/theme/DocVersionBanner/styles.module.css

@@ -1,49 +0,0 @@
-/**
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-.versionBanner {
-  background-color: var(--ifm-color-emphasis-100);
-  padding: 0.5rem 1rem;
-  margin-bottom: 1rem;
-  border-bottom: 1px solid var(--ifm-color-emphasis-200);
-}
-
-.versionContainer {
-  display: flex;
-  align-items: center;
-  max-width: var(--ifm-container-width);
-  margin: 0 auto;
-  padding: 0 var(--ifm-spacing-horizontal);
-}
-
-.versionLabel {
-  font-weight: bold;
-  margin-right: 0.5rem;
-}
-
-.versionSelector {
-  cursor: pointer;
-  color: var(--ifm-color-primary);
-  font-weight: 500;
-}
-
-.versionSelector:hover {
-  text-decoration: none;
-  color: var(--ifm-color-primary-darker);
-}

docs/src/webpack.extend.ts

@@ -1,115 +0,0 @@
-/**
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-import path from 'path';
-import type { Plugin } from '@docusaurus/types';
-
-export default function webpackExtendPlugin(): Plugin<void> {
-  return {
-    name: 'custom-webpack-plugin',
-    configureWebpack(config, isServer, utils) {
-      const { isDev } = utils;
-      return {
-        devtool: isDev ? 'eval-source-map' : config.devtool,
-        ...(isDev && {
-          optimization: {
-            ...config.optimization,
-            minimize: false,
-            removeAvailableModules: false,
-            removeEmptyChunks: false,
-            splitChunks: false,
-          },
-        }),
-        resolve: {
-          alias: {
-            ...config.resolve.alias,
-            // Allow importing from superset-frontend
-            src: path.resolve(__dirname, '../../superset-frontend/src'),
-            // '@superset-ui/core': path.resolve(
-            //   __dirname,
-            //   '../../superset-frontend/packages/superset-ui-core',
-            // ),
-            // Add aliases for our components to make imports easier
-            '@docs/components': path.resolve(__dirname, '../src/components'),
-            '@superset/components': path.resolve(
-              __dirname,
-              '../../superset-frontend/packages/superset-ui-core/src/components',
-            ),
-            // Add proper Storybook aliases
-            '@storybook/blocks': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/blocks',
-            ),
-            '@storybook/components': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/components',
-            ),
-            '@storybook/theming': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/theming',
-            ),
-            '@storybook/client-logger': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/client-logger',
-            ),
-            '@storybook/core-events': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/core-events',
-            ),
-            // Add internal Storybook aliases
-            'storybook/internal/components': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/components',
-            ),
-            'storybook/internal/theming': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/theming',
-            ),
-            'storybook/internal/client-logger': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/client-logger',
-            ),
-            'storybook/internal/csf': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/csf',
-            ),
-            'storybook/internal/preview-api': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/preview-api',
-            ),
-            'storybook/internal/docs-tools': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/docs-tools',
-            ),
-            'storybook/internal/core-events': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/core-events',
-            ),
-            'storybook/internal/channels': path.resolve(
-              __dirname,
-              '../node_modules/@storybook/channels',
-            ),
-          },
-        },
-        // We're removing the ts-loader rule that was processing superset-frontend files
-        // This will prevent TypeScript errors from files outside the docs directory
-      };
-    },
-  };
-}

docs/static/resources/openapi.json

@@ -962,11 +962,8 @@
       "ChartDataDatasource": {
         "properties": {
           "id": {
-            "description": "Datasource id/uuid",
-            "oneOf": [
-              { "type": "integer" },
-              { "type": "string" }
-            ]
+            "description": "Datasource id",
+            "type": "integer"
           },
           "type": {
             "description": "Datasource type",

docs/tutorials_versions.json

@@ -1,3 +0,0 @@
-[
-  "1.0.0"
-]