@lobehub/lobehub 2.0.0-next.9 → 2.0.0-next.91

package/Dockerfile.lite

@@ -1,272 +0,0 @@
-## Set global build ENV
-ARG NODEJS_VERSION="24"
-
-## Base image for all building stages
-FROM node:${NODEJS_VERSION}-slim AS base
-
-ARG USE_CN_MIRROR
-
-ENV DEBIAN_FRONTEND="noninteractive"
-
-RUN \
-    # If you want to build docker in China, build with --build-arg USE_CN_MIRROR=true
-    if [ "${USE_CN_MIRROR:-false}" = "true" ]; then \
-        sed -i "s/deb.debian.org/mirrors.ustc.edu.cn/g" "/etc/apt/sources.list.d/debian.sources"; \
-    fi \
-    # Add required package
-    && apt update \
-    && apt install ca-certificates proxychains-ng -qy \
-    # Prepare required package to distroless
-    && mkdir -p /distroless/bin /distroless/etc /distroless/etc/ssl/certs /distroless/lib \
-    # Copy proxychains to distroless
-    && cp /usr/lib/$(arch)-linux-gnu/libproxychains.so.4 /distroless/lib/libproxychains.so.4 \
-    && cp /usr/lib/$(arch)-linux-gnu/libdl.so.2 /distroless/lib/libdl.so.2 \
-    && cp /usr/bin/proxychains4 /distroless/bin/proxychains \
-    && cp /etc/proxychains4.conf /distroless/etc/proxychains4.conf \
-    # Copy node to distroless
-    && cp /usr/lib/$(arch)-linux-gnu/libstdc++.so.6 /distroless/lib/libstdc++.so.6 \
-    && cp /usr/lib/$(arch)-linux-gnu/libgcc_s.so.1 /distroless/lib/libgcc_s.so.1 \
-    && cp /usr/local/bin/node /distroless/bin/node \
-    # Copy CA certificates to distroless
-    && cp /etc/ssl/certs/ca-certificates.crt /distroless/etc/ssl/certs/ca-certificates.crt \
-    # Cleanup temp files
-    && rm -rf /tmp/* /var/lib/apt/lists/* /var/tmp/*
-
-## Builder image, install all the dependencies and build the app
-FROM base AS builder
-
-ARG USE_CN_MIRROR
-ARG NEXT_PUBLIC_BASE_PATH
-ARG NEXT_PUBLIC_SENTRY_DSN
-ARG NEXT_PUBLIC_ANALYTICS_POSTHOG
-ARG NEXT_PUBLIC_POSTHOG_HOST
-ARG NEXT_PUBLIC_POSTHOG_KEY
-ARG NEXT_PUBLIC_ANALYTICS_UMAMI
-ARG NEXT_PUBLIC_UMAMI_SCRIPT_URL
-ARG NEXT_PUBLIC_UMAMI_WEBSITE_ID
-ARG FEATURE_FLAGS
-
-ENV NEXT_PUBLIC_CLIENT_DB="pglite"
-ENV NEXT_PUBLIC_BASE_PATH="${NEXT_PUBLIC_BASE_PATH}" \
-    FEATURE_FLAGS="${FEATURE_FLAGS}"
-
-# Sentry
-ENV NEXT_PUBLIC_SENTRY_DSN="${NEXT_PUBLIC_SENTRY_DSN}" \
-    SENTRY_ORG="" \
-    SENTRY_PROJECT=""
-
-ENV APP_URL="http://app.com"
-
-# Posthog
-ENV NEXT_PUBLIC_ANALYTICS_POSTHOG="${NEXT_PUBLIC_ANALYTICS_POSTHOG}" \
-    NEXT_PUBLIC_POSTHOG_HOST="${NEXT_PUBLIC_POSTHOG_HOST}" \
-    NEXT_PUBLIC_POSTHOG_KEY="${NEXT_PUBLIC_POSTHOG_KEY}"
-
-# Umami
-ENV NEXT_PUBLIC_ANALYTICS_UMAMI="${NEXT_PUBLIC_ANALYTICS_UMAMI}" \
-    NEXT_PUBLIC_UMAMI_SCRIPT_URL="${NEXT_PUBLIC_UMAMI_SCRIPT_URL}" \
-    NEXT_PUBLIC_UMAMI_WEBSITE_ID="${NEXT_PUBLIC_UMAMI_WEBSITE_ID}"
-
-# Node
-ENV NODE_OPTIONS="--max-old-space-size=6144"
-
-WORKDIR /app
-
-COPY package.json pnpm-workspace.yaml ./
-COPY .npmrc ./
-COPY packages ./packages
-
-RUN \
-    # If you want to build docker in China, build with --build-arg USE_CN_MIRROR=true
-    if [ "${USE_CN_MIRROR:-false}" = "true" ]; then \
-        export SENTRYCLI_CDNURL="https://npmmirror.com/mirrors/sentry-cli"; \
-        npm config set registry "https://registry.npmmirror.com/"; \
-        echo 'canvas_binary_host_mirror=https://npmmirror.com/mirrors/canvas' >> .npmrc; \
-    fi \
-    # Set the registry for corepack
-    && export COREPACK_NPM_REGISTRY=$(npm config get registry | sed 's/\/$//') \
-    # Update corepack to latest (nodejs/corepack#612)
-    && npm i -g corepack@latest \
-    # Enable corepack
-    && corepack enable \
-    # Use pnpm for corepack
-    && corepack use $(sed -n 's/.*"packageManager": "\(.*\)".*/\1/p' package.json) \
-    # Install the dependencies
-    && pnpm i
-
-COPY . .
-
-# run build standalone for docker version
-RUN npm run build:docker
-
-## Application image, copy all the files for production
-FROM busybox:latest AS app
-
-COPY --from=base /distroless/ /
-
-# Automatically leverage output traces to reduce image size
-# https://nextjs.org/docs/advanced-features/output-file-tracing
-COPY --from=builder /app/.next/standalone /app/
-
-# Copy server launcher
-COPY --from=builder /app/scripts/serverLauncher/startServer.js /app/startServer.js
-
-RUN \
-    # Add nextjs:nodejs to run the app
-    addgroup -S -g 1001 nodejs \
-    && adduser -D -G nodejs -H -S -h /app -u 1001 nextjs \
-    # Set permission for nextjs:nodejs
-    && chown -R nextjs:nodejs /app /etc/proxychains4.conf
-
-## Production image, copy all the files and run next
-FROM scratch
-
-# Copy all the files from app, set the correct permission for prerender cache
-COPY --from=app / /
-
-ENV NODE_ENV="production" \
-    NODE_OPTIONS="--dns-result-order=ipv4first --use-openssl-ca" \
-    NODE_EXTRA_CA_CERTS="" \
-    NODE_TLS_REJECT_UNAUTHORIZED="" \
-    SSL_CERT_FILE="/etc/ssl/certs/ca-certificates.crt"
-
-# Make the middleware rewrite through local as default
-# refs: https://github.com/lobehub/lobe-chat/issues/5876
-ENV MIDDLEWARE_REWRITE_THROUGH_LOCAL="1"
-
-# set hostname to localhost
-ENV HOSTNAME="0.0.0.0" \
-    PORT="3210"
-
-# General Variables
-ENV ACCESS_CODE="" \
-    API_KEY_SELECT_MODE="" \
-    DEFAULT_AGENT_CONFIG="" \
-    SYSTEM_AGENT="" \
-    FEATURE_FLAGS="" \
-    PROXY_URL="" \
-    ENABLE_AUTH_PROTECTION=""
-
-# Model Variables
-ENV \
-    # AI21
-    AI21_API_KEY="" AI21_MODEL_LIST="" \
-    # Ai360
-    AI360_API_KEY="" AI360_MODEL_LIST="" \
-    # AiHubMix
-    AIHUBMIX_API_KEY="" AIHUBMIX_MODEL_LIST="" \
-    # Anthropic
-    ANTHROPIC_API_KEY="" ANTHROPIC_MODEL_LIST="" ANTHROPIC_PROXY_URL="" \
-    # Amazon Bedrock
-    ENABLED_AWS_BEDROCK="" AWS_ACCESS_KEY_ID="" AWS_SECRET_ACCESS_KEY="" AWS_REGION="" AWS_BEDROCK_MODEL_LIST="" \
-    # Azure OpenAI
-    AZURE_API_KEY="" AZURE_API_VERSION="" AZURE_ENDPOINT="" AZURE_MODEL_LIST="" \
-    # Baichuan
-    BAICHUAN_API_KEY="" BAICHUAN_MODEL_LIST="" \
-    # Cloudflare
-    CLOUDFLARE_API_KEY="" CLOUDFLARE_BASE_URL_OR_ACCOUNT_ID="" CLOUDFLARE_MODEL_LIST="" \
-    # Cohere
-    COHERE_API_KEY="" COHERE_MODEL_LIST="" COHERE_PROXY_URL="" \
-    # ComfyUI
-    ENABLED_COMFYUI="" COMFYUI_BASE_URL="" COMFYUI_AUTH_TYPE="" \
-    COMFYUI_API_KEY="" COMFYUI_USERNAME="" COMFYUI_PASSWORD="" COMFYUI_CUSTOM_HEADERS="" \
-    # DeepSeek
-    DEEPSEEK_API_KEY="" DEEPSEEK_MODEL_LIST="" \
-    # Fireworks AI
-    FIREWORKSAI_API_KEY="" FIREWORKSAI_MODEL_LIST="" \
-    # Gitee AI
-    GITEE_AI_API_KEY="" GITEE_AI_MODEL_LIST="" \
-    # GitHub
-    GITHUB_TOKEN="" GITHUB_MODEL_LIST="" \
-    # Google
-    GOOGLE_API_KEY="" GOOGLE_MODEL_LIST="" GOOGLE_PROXY_URL="" \
-    # Groq
-    GROQ_API_KEY="" GROQ_MODEL_LIST="" GROQ_PROXY_URL="" \
-    # Higress
-    HIGRESS_API_KEY="" HIGRESS_MODEL_LIST="" HIGRESS_PROXY_URL="" \
-    # HuggingFace
-    HUGGINGFACE_API_KEY="" HUGGINGFACE_MODEL_LIST="" HUGGINGFACE_PROXY_URL="" \
-    # Hunyuan
-    HUNYUAN_API_KEY="" HUNYUAN_MODEL_LIST="" \
-    # InternLM
-    INTERNLM_API_KEY="" INTERNLM_MODEL_LIST="" \
-    # Jina
-    JINA_API_KEY="" JINA_MODEL_LIST="" JINA_PROXY_URL="" \
-    # Minimax
-    MINIMAX_API_KEY="" MINIMAX_MODEL_LIST="" \
-    # Mistral
-    MISTRAL_API_KEY="" MISTRAL_MODEL_LIST="" \
-    # ModelScope
-    MODELSCOPE_API_KEY="" MODELSCOPE_MODEL_LIST="" MODELSCOPE_PROXY_URL="" \
-    # Moonshot
-    MOONSHOT_API_KEY="" MOONSHOT_MODEL_LIST="" MOONSHOT_PROXY_URL="" \
-    # Nebius
-    NEBIUS_API_KEY="" NEBIUS_MODEL_LIST="" NEBIUS_PROXY_URL="" \
-    # NewAPI
-    NEWAPI_API_KEY="" NEWAPI_PROXY_URL="" \
-    # Novita
-    NOVITA_API_KEY="" NOVITA_MODEL_LIST="" \
-    # Nvidia NIM
-    NVIDIA_API_KEY="" NVIDIA_MODEL_LIST="" NVIDIA_PROXY_URL="" \
-    # Ollama
-    ENABLED_OLLAMA="" OLLAMA_MODEL_LIST="" OLLAMA_PROXY_URL="" \
-    # OpenAI
-    ENABLED_OPENAI="" OPENAI_API_KEY="" OPENAI_MODEL_LIST="" OPENAI_PROXY_URL="" \
-    # OpenRouter
-    OPENROUTER_API_KEY="" OPENROUTER_MODEL_LIST="" \
-    # Perplexity
-    PERPLEXITY_API_KEY="" PERPLEXITY_MODEL_LIST="" PERPLEXITY_PROXY_URL="" \
-    # Qiniu
-    QINIU_API_KEY="" QINIU_MODEL_LIST="" QINIU_PROXY_URL="" \
-    # Qwen
-    QWEN_API_KEY="" QWEN_MODEL_LIST="" QWEN_PROXY_URL="" \
-    # SambaNova
-    SAMBANOVA_API_KEY="" SAMBANOVA_MODEL_LIST="" \
-    # SenseNova
-    SENSENOVA_API_KEY="" SENSENOVA_MODEL_LIST="" \
-    # SiliconCloud
-    SILICONCLOUD_API_KEY="" SILICONCLOUD_MODEL_LIST="" SILICONCLOUD_PROXY_URL="" \
-    # Spark
-    SPARK_API_KEY="" SPARK_MODEL_LIST="" SPARK_PROXY_URL="" SPARK_SEARCH_MODE="" \
-    # Stepfun
-    STEPFUN_API_KEY="" STEPFUN_MODEL_LIST="" \
-    # Taichu
-    TAICHU_API_KEY="" TAICHU_MODEL_LIST="" \
-    # TogetherAI
-    TOGETHERAI_API_KEY="" TOGETHERAI_MODEL_LIST="" \
-    # Upstage
-    UPSTAGE_API_KEY="" UPSTAGE_MODEL_LIST="" \
-    # v0 (Vercel)
-    V0_API_KEY="" V0_MODEL_LIST="" \
-    # vLLM
-    VLLM_API_KEY="" VLLM_MODEL_LIST="" VLLM_PROXY_URL="" \
-    # Wenxin
-    WENXIN_API_KEY="" WENXIN_MODEL_LIST="" \
-    # xAI
-    XAI_API_KEY="" XAI_MODEL_LIST="" XAI_PROXY_URL="" \
-    # Xinference
-    XINFERENCE_API_KEY="" XINFERENCE_MODEL_LIST="" XINFERENCE_PROXY_URL="" \
-    # 01.AI
-    ZEROONE_API_KEY="" ZEROONE_MODEL_LIST="" \
-    # Zhipu
-    ZHIPU_API_KEY="" ZHIPU_MODEL_LIST="" \
-    # Tencent Cloud
-    TENCENT_CLOUD_API_KEY="" TENCENT_CLOUD_MODEL_LIST="" \
-    # Infini-AI
-    INFINIAI_API_KEY="" INFINIAI_MODEL_LIST="" \
-    # 302.AI
-    AI302_API_KEY="" AI302_MODEL_LIST="" \
-    # FAL
-    ENABLED_FAL="" FAL_API_KEY="" FAL_MODEL_LIST="" \
-    # BFL
-    BFL_API_KEY="" BFL_MODEL_LIST="" \
-    # Vercel AI Gateway
-    VERCELAIGATEWAY_API_KEY="" VERCELAIGATEWAY_MODEL_LIST=""
-
-USER nextjs
-
-EXPOSE 3210/tcp
-
-ENTRYPOINT ["/bin/node"]
-
-CMD ["/app/startServer.js"]

package/packages/context-engine/ARCHITECTURE.md

@@ -1,425 +0,0 @@
-# Context Engine 架构设计
-
-## 概述
-
-Context Engine 是一个灵活的消息处理管道系统，用于在 AI 对话中动态管理和处理上下文信息。它提供了一种可扩展的方式来注入、转换和验证消息流。
-
-## 核心概念
-
-### 1. 处理器（Processor）
-
-处理器是 Context Engine 的基本单元，负责对消息进行特定的处理操作。
-
-#### 处理器分类
-
-根据功能职责，处理器分为以下几类：
-
-1. **注入器（Injector）**
-   - 职责：向消息流中添加新的上下文信息
-   - 示例：SystemRoleInjector、HistoryInjector、RAGContextInjector
-
-2. **转换器（Transformer）**
-   - 职责：修改现有消息的内容或结构
-   - 示例：MessageRoleTransformer、ImageContentProcessor
-
-3. **截断器（Truncator）**
-   - 职责：根据特定规则裁剪消息内容
-   - 示例：HistoryTruncator、TokenBasedTruncator
-
-4. **验证器（Validator）**
-   - 职责：验证消息是否符合特定要求
-   - 示例：ModelCapabilityValidator
-
-5. **重排器（Reorderer）**
-   - 职责：调整消息的顺序
-   - 示例：ToolMessageReorder
-
-### 2. 管道（Pipeline）
-
-管道是一系列处理器的有序组合，消息流经管道时会被逐个处理器处理。
-
-```typescript
-interface Pipeline {
-  // 添加处理器到管道
-  add(processor: BaseProcessor): Pipeline;
-  
-  // 执行管道处理
-  execute(context: ProcessorContext): Promise<ProcessorContext>;
-  
-  // 获取管道中的所有处理器
-  getProcessors(): BaseProcessor[];
-}
-```
-
-### 3. 上下文（Context）
-
-上下文包含了处理器需要的所有信息：
-
-```typescript
-interface ProcessorContext {
-  messages: Message[];           // 消息列表
-  metadata?: ProcessorMetadata;  // 元数据
-  variables?: Record<string, any>; // 变量
-  abortSignal?: AbortSignal;    // 中止信号
-}
-```
-
-## 架构设计
-
-### 类层次结构
-
-```
-BaseProcessor (抽象基类)
-├── BaseInjector (注入器基类)
-│   ├── SystemRoleInjector
-│   ├── HistoryInjector
-│   ├── RAGContextInjector
-│   └── ...
-├── BaseTransformer (转换器基类)
-│   ├── MessageRoleTransformer
-│   └── ImageContentProcessor
-├── BaseTruncator (截断器基类)
-│   ├── HistoryTruncator
-│   └── TokenBasedTruncator
-├── BaseValidator (验证器基类)
-│   └── ModelCapabilityValidator
-└── BaseReorderer (重排器基类)
-    └── ToolMessageReorder
-```
-
-### 核心接口设计
-
-#### BaseProcessor
-
-```typescript
-abstract class BaseProcessor {
-  // 处理器类型
-  abstract readonly type: ProcessorType;
-  
-  // 处理器名称
-  abstract readonly name: string;
-  
-  // 主处理方法
-  async process(context: ProcessorContext): Promise<ProcessorContext> {
-    // 1. 前置验证
-    this.validateInput(context);
-    
-    // 2. 执行处理
-    const result = await this.doProcess(context);
-    
-    // 3. 后置验证
-    this.validateOutput(result);
-    
-    return result;
-  }
-  
-  // 子类实现的核心处理逻辑
-  protected abstract doProcess(context: ProcessorContext): Promise<ProcessorContext>;
-  
-  // 输入验证（可选覆盖）
-  protected validateInput(context: ProcessorContext): void {}
-  
-  // 输出验证（可选覆盖）
-  protected validateOutput(context: ProcessorContext): void {}
-}
-```
-
-#### BaseInjector
-
-```typescript
-abstract class BaseInjector extends BaseProcessor {
-  readonly type = ProcessorType.Injector;
-  
-  protected async doProcess(context: ProcessorContext): Promise<ProcessorContext> {
-    // 1. 判断是否需要注入
-    if (!this.shouldInject(context)) {
-      return context;
-    }
-    
-    // 2. 构建注入内容
-    const content = await this.buildContent(context);
-    
-    // 3. 创建消息
-    const message = this.createMessage(content, context);
-    
-    // 4. 确定注入位置
-    const position = this.getInjectionPosition(context);
-    
-    // 5. 执行注入
-    return this.inject(context, message, position);
-  }
-  
-  // 子类需要实现的方法
-  protected abstract shouldInject(context: ProcessorContext): boolean;
-  protected abstract buildContent(context: ProcessorContext): Promise<string>;
-  
-  // 可选覆盖的方法
-  protected getInjectionPosition(context: ProcessorContext): number {
-    return 0; // 默认注入到开头
-  }
-  
-  protected createMessage(content: string, context: ProcessorContext): Message {
-    return {
-      role: 'system',
-      content,
-      metadata: { injectedBy: this.name }
-    };
-  }
-}
-```
-
-## 使用方式
-
-### 1. 创建自定义处理器
-
-```typescript
-// 创建一个自定义注入器
-class CustomContextInjector extends BaseInjector {
-  readonly name = 'custom-context-injector';
-  
-  protected shouldInject(context: ProcessorContext): boolean {
-    // 判断逻辑
-    return !context.messages.some(msg => 
-      msg.metadata?.injectedBy === this.name
-    );
-  }
-  
-  protected async buildContent(context: ProcessorContext): Promise<string> {
-    // 构建内容逻辑
-    return `Custom context: ${context.variables?.customValue}`;
-  }
-}
-```
-
-### 2. 构建处理管道
-
-```typescript
-// 使用工厂模式创建管道
-const pipeline = createPipeline()
-  .add(new SystemRoleInjector())
-  .add(new HistoryInjector({ maxMessages: 10 }))
-  .add(new CustomContextInjector())
-  .add(new MessageRoleTransformer())
-  .add(new TokenBasedTruncator({ maxTokens: 4000 }))
-  .add(new ModelCapabilityValidator());
-
-// 执行管道
-const result = await pipeline.execute({
-  messages: initialMessages,
-  variables: { customValue: 'test' },
-  metadata: { model: 'gpt-4' }
-});
-```
-
-### 3. 条件处理
-
-```typescript
-// 基于条件的管道构建
-const pipeline = createPipeline();
-
-if (config.enableRAG) {
-  pipeline.add(new RAGContextInjector());
-}
-
-if (config.enableSearch) {
-  pipeline.add(new SearchContextInjector());
-}
-
-// 始终添加的处理器
-pipeline
-  .add(new HistoryTruncator())
-  .add(new ModelCapabilityValidator());
-```
-
-### 4. 错误处理
-
-```typescript
-try {
-  const result = await pipeline.execute(context);
-} catch (error) {
-  if (error instanceof ProcessorError) {
-    console.error(`Processor ${error.processorName} failed:`, error.message);
-  } else if (error instanceof PipelineError) {
-    console.error('Pipeline execution failed:', error.message);
-  }
-}
-```
-
-## 配置管理
-
-### 处理器配置
-
-每个处理器可以接受特定的配置选项：
-
-```typescript
-interface ProcessorConfig {
-  // 通用配置
-  enabled?: boolean;
-  priority?: number;
-  
-  // 处理器特定配置
-  [key: string]: any;
-}
-
-// 示例：历史注入器配置
-interface HistoryInjectorConfig extends ProcessorConfig {
-  maxMessages?: number;
-  includeSystemMessages?: boolean;
-  preserveTools?: boolean;
-}
-```
-
-### 管道配置
-
-```typescript
-interface PipelineConfig {
-  processors: Array<{
-    type: string;
-    config?: ProcessorConfig;
-  }>;
-  
-  // 全局配置
-  abortOnError?: boolean;
-  timeout?: number;
-}
-
-// 从配置创建管道
-const pipeline = createPipelineFromConfig({
-  processors: [
-    { type: 'system-role', config: { enabled: true } },
-    { type: 'history', config: { maxMessages: 20 } },
-    { type: 'rag', config: { threshold: 0.7 } }
-  ],
-  abortOnError: false,
-  timeout: 30000
-});
-```
-
-## 最佳实践
-
-### 1. 单一职责原则
-每个处理器应该只负责一种特定的处理任务。
-
-### 2. 可配置性
-处理器应该通过配置参数来控制行为，而不是硬编码。
-
-### 3. 错误处理
-- 使用具体的错误类型
-- 提供有意义的错误信息
-- 考虑错误恢复策略
-
-### 4. 性能优化
-- 避免不必要的消息复制
-- 使用流式处理处理大量数据
-- 实现适当的缓存机制
-
-### 5. 测试
-- 为每个处理器编写单元测试
-- 测试处理器组合的集成测试
-- 边界条件和错误场景测试
-
-## 扩展机制
-
-### 1. 自定义处理器类型
-
-```typescript
-// 定义新的处理器类型
-enum CustomProcessorType {
-  Analyzer = 'analyzer',
-  Enhancer = 'enhancer'
-}
-
-// 创建对应的基类
-abstract class BaseAnalyzer extends BaseProcessor {
-  readonly type = CustomProcessorType.Analyzer;
-  
-  // 分析器特定的方法
-  protected abstract analyze(messages: Message[]): AnalysisResult;
-}
-```
-
-### 2. 处理器组合
-
-```typescript
-// 创建复合处理器
-class CompositeProcessor extends BaseProcessor {
-  constructor(private processors: BaseProcessor[]) {
-    super();
-  }
-  
-  protected async doProcess(context: ProcessorContext): Promise<ProcessorContext> {
-    let result = context;
-    for (const processor of this.processors) {
-      result = await processor.process(result);
-    }
-    return result;
-  }
-}
-```
-
-### 3. 插件系统
-
-```typescript
-interface ProcessorPlugin {
-  name: string;
-  version: string;
-  processors: ProcessorDefinition[];
-}
-
-// 注册插件
-registry.registerPlugin({
-  name: 'custom-processors',
-  version: '1.0.0',
-  processors: [
-    { type: 'custom-injector', factory: () => new CustomInjector() },
-    { type: 'custom-validator', factory: () => new CustomValidator() }
-  ]
-});
-```
-
-## 迁移指南
-
-### 从当前架构迁移
-
-1. **BaseProvider 迁移到 BaseInjector**
-   ```typescript
-   // 旧代码
-   class MyProvider extends BaseProvider {
-     doProcess(context) {
-       // 实现
-     }
-   }
-   
-   // 新代码
-   class MyInjector extends BaseInjector {
-     shouldInject(context) {
-       // 判断逻辑
-     }
-     
-     buildContent(context) {
-       // 构建内容
-     }
-   }
-   ```
-
-2. **处理器分类**
-   - 将现有处理器按功能分类
-   - 继承对应的基类
-   - 实现必要的抽象方法
-
-3. **配置迁移**
-   - 统一配置格式
-   - 支持向后兼容
-   - 提供迁移工具
-
-## 总结
-
-新的 Context Engine 架构提供了：
-
-1. **清晰的分层结构**：基于功能的处理器分类
-2. **灵活的扩展机制**：易于添加新的处理器类型
-3. **强大的组合能力**：通过管道组合实现复杂功能
-4. **完善的错误处理**：细粒度的错误类型和恢复策略
-5. **优秀的可测试性**：模块化设计便于单元测试
-
-这种设计使得 Context Engine 更加模块化、可维护和可扩展，能够更好地满足不同场景下的上下文处理需求。