feat: 支持 OpenRouter/Qwen 多模型推理与完整用法说明

Author: StellarLume-ops

.DS_Store

@@ -0,0 +1,8 @@
+package-lock.json
+node_modules/
+dist/
+.git/
+*.log
+.env.*
+!.env.example
+!.github/

.clineignore

@@ -0,0 +1,29 @@
+# Cline Custom Instructions
+
+- ALWAYS refer to the `README.md` for the latest information on the project.
+- ALWAYS refer to `ARCHITECTURE.md` for the latest information on the architecture of the project.
+- ALWAYS Follow programming principles such as DRY, KISS, YAGNI, and SOLID
+- ALWAYS use the latest version of the programming language and libraries.
+- ALWAYS prefer the simplest solution.
+- When importing a relative path, avoid using file extensions like ".js" and ".ts".
+- ALWAYS add and update TSDoc for all classes, methods and functions. Focus on functionality and reasoning.
+- NEVER document individual parameters or return values if their use can easily be derived from their name.
+
+## Architecture Documentation Guidelines
+
+Keep `ARCHITECTURE.md` high-level:
+
+- Focus on system concepts and component relationships
+- Include design principles and code conventions
+- Use simple MermaidJS diagrams for visualization
+- Put implementation details in source code
+- Update when architecture changes
+
+## Git
+
+- The repository owner and name is `arabold/docs-mcp-server` on GitHub.
+- AWLAYS create new branches locally first before pushing them to the GitHub repository.
+- ALWAYS format Git commit messages as markdown.
+- ALWAYS adhere to the Conventional Commits specification for all Git commit messages
+- ALWAYS prefix branch names with the type of work being done, such as `feature/`, `bugfix/`, `chore/`, etc.
+- ALWAYS include the issue number in the branch name, such as `feature/1234-issue-name`.

.clinerules

@@ -0,0 +1,20 @@
+# Docker specific
+Dockerfile
+.dockerignore
+
+# Version control
+.git
+.github
+.husky
+
+# Already in gitignore but explicitly listed for Docker context
+node_modules
+dist
+*.log
+.env*
+
+# Other
+.store
+README.md
+ARCHITECTURE.md
+CHANGELOG.md

.dockerignore

@@ -0,0 +1,47 @@
+# Embedding Model Configuration
+# Optional: Format is "provider:model_name" or just "model_name" for OpenAI (default)
+# Examples:
+#   - openai:text-embedding-3-small (default if no provider specified)
+#   - vertex:text-embedding-004 (Google Cloud Vertex AI)
+#   - gemini:gemini-embedding-exp-03-07 (Google Generative AI)
+#   - aws:amazon.titan-embed-text-v1
+#   - microsoft:text-embedding-ada-002
+DOCS_MCP_EMBEDDING_MODEL=
+
+# OpenAI Provider Configuration (Default)
+# Required for OpenAI provider or as fallback
+OPENAI_API_KEY=your-key-here
+# Optional: Your OpenAI Organization ID
+OPENAI_ORG_ID=
+# Optional: Custom base URL for OpenAI-compatible APIs (e.g., Ollama, Azure OpenAI)
+OPENAI_API_BASE=
+
+# Google Cloud Vertex AI Configuration
+# Required for vertex provider: Path to service account JSON key file
+GOOGLE_APPLICATION_CREDENTIALS=/path/to/gcp-key.json
+
+# Google Generative AI (Gemini) Configuration
+# Required for gemini provider: Google API key
+GOOGLE_API_KEY=your-google-api-key
+
+# AWS Bedrock Configuration
+# Required for aws provider
+AWS_ACCESS_KEY_ID=your-aws-key
+AWS_SECRET_ACCESS_KEY=your-aws-secret
+AWS_REGION=us-east-1
+# Optional: Use BEDROCK_AWS_REGION instead of AWS_REGION if needed
+# BEDROCK_AWS_REGION=us-east-1
+
+# Azure OpenAI Configuration
+# Required for microsoft provider
+AZURE_OPENAI_API_KEY=your-azure-key
+AZURE_OPENAI_API_INSTANCE_NAME=your-instance
+AZURE_OPENAI_API_DEPLOYMENT_NAME=your-deployment
+AZURE_OPENAI_API_VERSION=2024-02-01
+
+# Optional: Specify a custom directory to store the SQLite database file (documents.db).
+# If set, this path takes precedence over the default locations.
+# Default behavior (if unset):
+# 1. Uses './.store/' in the project root if it exists (legacy).
+# 2. Falls back to OS-specific data directory (e.g., ~/Library/Application Support/docs-mcp-server on macOS).
+# DOCS_MCP_STORE_PATH=/path/to/your/desired/storage/directory

.env.example

@@ -0,0 +1,72 @@
+name: CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  lint:
+    name: Lint
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '>=20.0.0' # Match engines requirement in package.json
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run linter
+        run: npm run lint
+
+  test:
+    name: Test
+    runs-on: ubuntu-latest
+    needs: lint # Run after linting passes
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '>=20.0.0'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Install Playwright browsers
+        # FIXME: Why is this needed? Where does the version conflict come from?
+        run: ln -s /home/runner/.cache/ms-playwright/chromium-1161 /home/runner/.cache/ms-playwright/chromium-1169
+
+      - name: Run tests
+        # run: npm run test
+        run: npx vitest run
+
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+    needs: test # Run after tests pass
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '>=20.0.0'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run build
+        run: npm run build

.github/workflows/ci.yml

@@ -0,0 +1,108 @@
+name: Release
+
+on:
+  workflow_dispatch: # Allows manual triggering
+
+jobs:
+  release:
+    name: Release to npm and GitHub
+    runs-on: ubuntu-latest
+    # Permissions needed for semantic-release to commit/tag/release
+    permissions:
+      contents: write
+      issues: write
+      pull-requests: write
+      # id-token: write # Needed for OIDC trusted publishing (if not using NPM_TOKEN)
+    outputs:
+      # Output whether a new release was published
+      new_release_published: ${{ steps.semantic.outputs.new_release_published }}
+      new_release_version: ${{ steps.semantic.outputs.new_release_version }}
+    steps:
+      - name: Checkout code
+        # Need fetch-depth: 0 for semantic-release to analyze all relevant commits
+        # and commit package.json/CHANGELOG.md changes
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '>=20.0.0' # Match engines requirement in package.json
+          registry-url: 'https://registry.npmjs.org' # Specify npm registry
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run build
+        run: npm run build
+
+      - name: Run semantic-release
+        id: semantic # Give step an ID to reference its outputs
+        uses: cycjimmy/semantic-release-action@v4
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+  docker_publish:
+    name: Build and Push Docker Image to GHCR
+    # Run only after the release job completes successfully
+    needs: release
+    # Run only if semantic-release actually published a new version
+    if: needs.release.outputs.new_release_published == 'true'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read      # Needed to check out the code
+      packages: write     # Needed to push Docker image to GHCR
+      attestations: write # Needed for build attestations
+      id-token: write     # Needed for OIDC (good practice)
+
+    steps:
+      - name: Checkout code
+        # Checkout the specific commit tagged by semantic-release
+        uses: actions/checkout@v4
+        with:
+          # Use the tag name determined by the release job
+          ref: v${{ needs.release.outputs.new_release_version }}
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      - name: Log in to GitHub Container Registry
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Extract Docker metadata
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: ghcr.io/${{ github.repository }}
+          # Use the version from the semantic-release output
+          tags: |
+            type=raw,value=${{ needs.release.outputs.new_release_version }} # e.g., v1.4.1
+            type=semver,pattern={{version}},value=${{ needs.release.outputs.new_release_version }} # e.g., 1.4.1
+            type=semver,pattern=v{{major}}.{{minor}},value=${{ needs.release.outputs.new_release_version }} # e.g., v1.4
+            type=semver,pattern=v{{major}},value=${{ needs.release.outputs.new_release_version }} # e.g., v1
+            type=raw,value=latest,enable=true # Always tag latest on main branch release
+
+      - name: Build and push Docker image
+        id: push
+        uses: docker/build-push-action@v6
+        with:
+          context: .
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          cache-from: type=gha
+          cache-to: type=gha,mode=max
+
+      - name: Generate artifact attestation
+        uses: actions/attest-build-provenance@v1
+        with:
+          subject-name: ghcr.io/${{ github.repository }}
+          subject-digest: ${{ steps.push.outputs.digest }}
+          push-to-registry: true

.github/workflows/release.yml

@@ -0,0 +1,7 @@
+node_modules/
+dist/
+.store/
+*.log
+.env*
+!*.env.example
+*.code-workspace

.gitignore

@@ -0,0 +1 @@
+npx commitlint --edit $1

.husky/commit-msg

@@ -0,0 +1 @@
+npx lint-staged