refactor: move RAG trace classes to argtrace package and update SQL schema

- Rename org.ruoyi.trace package to org.ruoyi.argtrace for RagTraceNodeTypes and RagTracePayloadBuilder; fix package declarations and update imports in ChatServiceFacade and KnowledgeRetrievalServiceImpl - Remove obsolete RagTracePayloadBuilderTest - Switch supervisor response strategy from SUMMARY to LAST in ChatServiceFacade - Refresh docs/script/sql/ruoyi-ai.sql with the latest full schema dump - Add live demo links (admin panel, user frontend, commercial edition) to README.md and README_ZH.md Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
docs: remove redundant registry commands
2026-09-13 00:14:59 +00:00 · 2026-08-04 17:44:39 +08:00 · 2026-08-04 15:57:32 +08:00 · 2026-08-04 15:55:17 +08:00 · 2026-08-04 15:50:51 +08:00 · 2026-08-04 15:50:36 +08:00
226 changed files with 10259 additions and 2112 deletions
--- a/.github/workflows/publish-images.yml
+++ b/.github/workflows/publish-images.yml
@@ -0,0 +1,133 @@
+name: Publish Docker Images
+
+on:
+  push:
+    tags:
+      - 'v*.*.*'
+  workflow_dispatch:
+    inputs:
+      release_tag:
+        description: Release tag to rebuild
+        required: true
+        type: string
+
+concurrency:
+  group: publish-images-${{ inputs.release_tag || github.ref_name }}
+  cancel-in-progress: false
+
+env:
+  REGISTRY: ghcr.io
+  IMAGE_OWNER: ${{ github.repository_owner }}
+  RELEASE_TAG: ${{ inputs.release_tag || github.ref_name }}
+
+jobs:
+  publish:
+    name: Publish ${{ matrix.image }}
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+      attestations: write
+      id-token: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - image: ruoyi-ai-backend
+            source: local
+            context: .
+            dockerfile: docs/docker/ruoyi-ai/Dockerfile.backend
+          - image: ruoyi-ai-mysql
+            source: local
+            context: .
+            dockerfile: docs/docker/ruoyi-ai/Dockerfile.mysql
+          - image: ruoyi-ai-admin
+            source: admin
+            context: build/ruoyi-admin
+            dockerfile: build/ruoyi-admin/apps/web-antd/Dockerfile
+          - image: ruoyi-ai-web
+            source: web
+            context: build/ruoyi-web
+            dockerfile: build/ruoyi-web/Dockerfile.frontend
+
+    steps:
+      - name: Checkout backend repository
+        uses: actions/checkout@v6
+        with:
+          ref: ${{ env.RELEASE_TAG }}
+          fetch-depth: 1
+
+      - name: Checkout admin repository
+        if: matrix.source == 'admin'
+        uses: actions/checkout@v6
+        with:
+          repository: ${{ github.repository_owner }}/ruoyi-admin
+          ref: ${{ env.RELEASE_TAG }}
+          path: build/ruoyi-admin
+          fetch-depth: 1
+
+      - name: Checkout web repository
+        if: matrix.source == 'web'
+        uses: actions/checkout@v6
+        with:
+          repository: ${{ github.repository_owner }}/ruoyi-web
+          ref: ${{ env.RELEASE_TAG }}
+          path: build/ruoyi-web
+          fetch-depth: 1
+
+      - name: Configure frontend dependency builds
+        if: matrix.source == 'admin' || matrix.source == 'web'
+        shell: bash
+        run: |
+          python3 - "${{ matrix.dockerfile }}" <<'PY'
+          from pathlib import Path
+          import sys
+
+          dockerfile = Path(sys.argv[1])
+          content = dockerfile.read_text()
+          marker = "pnpm install --frozen-lockfile"
+          replacement = (
+              "pnpm install --frozen-lockfile "
+              "--config.dangerously-allow-all-builds=true"
+          )
+          if marker not in content:
+              raise SystemExit(f"pnpm install command not found in {dockerfile}")
+          dockerfile.write_text(content.replace(marker, replacement, 1))
+          PY
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      - name: Log in to GHCR
+        uses: docker/login-action@v3
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Extract Docker metadata
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_OWNER }}/${{ matrix.image }}
+          tags: |
+            type=raw,value=${{ env.RELEASE_TAG }}
+            type=raw,value=latest
+          labels: |
+            org.opencontainers.image.source=https://github.com/${{ github.repository }}
+            org.opencontainers.image.version=${{ env.RELEASE_TAG }}
+
+      - name: Build and push image
+        uses: docker/build-push-action@v6
+        with:
+          context: ${{ matrix.context }}
+          file: ${{ matrix.dockerfile }}
+          platforms: linux/amd64
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          cache-from: type=gha,scope=${{ matrix.image }}
+          cache-to: type=gha,mode=max,scope=${{ matrix.image }}
+          provenance: true
+          sbom: true
--- a/.gitignore
+++ b/.gitignore
@@ -23,6 +23,9 @@ target/
 .idea
 .claude
 .github
+!.github/
+!.github/workflows/
+!.github/workflows/**
 *.iws
 *.iml
 *.ipr
@@ -45,6 +48,7 @@ nbdist/
 *.xml.versionsBackup
 *.swp
 data/
+logs/

 !*/build/*.java
 !*/build/*.html
@@ -52,3 +56,4 @@ data/

 .flattened-pom.xml
 /.claude/settings.local.json
+/docs/docker/milvus/volumes/
--- a/README.md
+++ b/README.md
@@ -2,11 +2,7 @@

 <div align="center">

-[![Contributors][contributors-shield]][contributors-url]
-[![Forks][forks-shield]][forks-url]
-[![Stargazers][stars-shield]][stars-url]
-[![Issues][issues-shield]][issues-url]
-[![MIT License][license-shield]][license-url]
+[![Contributors][contributors-shield]][contributors-url] [![Forks][forks-shield]][forks-url] [![Stargazers][stars-shield]][stars-url] [![Issues][issues-shield]][issues-url] [![MIT License][license-shield]][license-url]


 <p align="center">
@@ -17,234 +13,231 @@

 <img src="docs/image/logo.png" alt="RuoYi AI Logo" width="120" height="120">

-### 企业级AI助手平台
+### Enterprise-Grade AI Assistant Platform

-*开箱即用的全栈AI平台，支持多智能体协同、Supervisor模式编排、多种决策模式、RAG技术和流程编排能力*
+*An out-of-the-box full-stack AI platform supporting multi-agent collaboration, Supervisor mode orchestration, and multiple decision models, with advanced RAG technology and visual workflow orchestration capabilities*

-**[English](README_EN.md)** | **[📖 使用文档](https://doc.ruoyiai.chat/)** |
-**[🚀 在线体验](https://web.ruoyiai.chat/)** | **[🐛 问题反馈](https://github.com/ageerle/ruoyi-ai/issues)** | **[💡 功能建议](https://github.com/ageerle/ruoyi-ai/issues)**
+**[中文](README_ZH.md)** | **[📖 Documentation](https://doc.ruoyiai.chat/)** |
+**[🚀 Live Demo](https://web.ruoyiai.chat/)** | **[🐛 Report Issues](https://github.com/ageerle/ruoyi-ai/issues)** | **[💡 Feature Requests](https://github.com/ageerle/ruoyi-ai/issues)**

 </div>


-## ✨ 核心亮点
+## 🚀 Live Demo

-|    模块     | 现有能力 
-|:---------:|---
-| **模型管理**  | 多模型接入(DeepSeek/智谱/MIMO/百炼/OpenAI)、多模态理解、Coze/DIFY/FastGPT/RAGFlow平台集成
-| **知识管理**  | 本地RAG + 向量库(Milvus/Weaviate/Qdrant)  + 文档解析
-| **工具管理**  | Mcp协议集成、Skills能力 + 可扩展工具生态                             
-| **流程编排**  | 可视化工作流设计器、节点拖拽编排、SSE流式执行,目前已经支持模型调用,邮件发送,人工审核等节点  
-| **智能体管理** | 基于Langchain4j的Agent框架、Supervisor模式编排,支持多种决策模型,可以灵活搭配工具,skills          
+| Service | URL | Default Account |
+|---|---|---|
+| Admin Panel | http://129.226.199.247:25666 | admin / admin123 |
+| User Frontend | http://129.226.199.247:25137 | admin / admin123 |
+| Commercial Edition | https://web.ruoyiai.chat | WeChat QR code login |

+## ✨ Core Features

-### 项目源码
+| Module | Current Capabilities |
+|:---:|---|
+| **Model Management** | Multi-model integration (DeepSeek/Zhipu/MIMO/Bailian/OpenAI), multi-modal understanding, Coze/DIFY/FastGPT/RAGFlow platform integration |
+| **Knowledge Management** | Local RAG + Vector DB (Milvus/Weaviate/Qdrant) + Document parsing |
+| **Tool Management** | MCP protocol integration, Skills capability + Extensible tool ecosystem |
+| **Workflow Orchestration** | Visual workflow designer, drag-and-drop node orchestration, SSE streaming execution, currently supports model calls, email sending, manual review, and other nodes |
+| **Multi-Agent** | Agent framework based on Langchain4j, Supervisor mode orchestration, supports multiple decision models, can flexibly combine tools and skills |

-| 项目模块     | GitHub 仓库                                             | Gitee 仓库                                             | GitCode 仓库                                             |
+### Project Repositories
+
+| Module     | GitHub Repository                                             | Gitee Repository                                             | GitCode Repository                                             |
 |----------|-------------------------------------------------------|------------------------------------------------------|--------------------------------------------------------|
-| 🔧 后端服务  | [ruoyi-ai](https://github.com/ageerle/ruoyi-ai)       | [ruoyi-ai](https://gitee.com/ageerle/ruoyi-ai)       | [ruoyi-ai](https://gitcode.com/ageerle/ruoyi-ai)       |
-| 🎨 用户前端  | [ruoyi-web](https://github.com/ageerle/ruoyi-web)     | [ruoyi-web](https://gitee.com/ageerle/ruoyi-web)     | [ruoyi-web](https://gitcode.com/ageerle/ruoyi-web)     |
-| 🛠️ 管理后台 | [ruoyi-admin](https://github.com/ageerle/ruoyi-admin) | [ruoyi-admin](https://gitee.com/ageerle/ruoyi-admin) | [ruoyi-admin](https://gitcode.com/ageerle/ruoyi-admin) |
-| 🎬 短剧平台  | [ruoyi-drama](https://github.com/ageerle/ruoyi-drama) | [ruoyi-drama](https://gitee.com/ageerle/ruoyi-drama) | [ruoyi-drama](https://gitcode.com/ageerle/ruoyi-drama)   |
+| 🔧 Backend  | [ruoyi-ai](https://github.com/ageerle/ruoyi-ai)       | [ruoyi-ai](https://gitee.com/ageerle/ruoyi-ai)       | [ruoyi-ai](https://gitcode.com/ageerle/ruoyi-ai)       |
+| 🎨 User Frontend  | [ruoyi-web](https://github.com/ageerle/ruoyi-web)     | [ruoyi-web](https://gitee.com/ageerle/ruoyi-web)     | [ruoyi-web](https://gitcode.com/ageerle/ruoyi-web)     |
+| 🛠️ Admin Panel | [ruoyi-admin](https://github.com/ageerle/ruoyi-admin) | [ruoyi-admin](https://gitee.com/ageerle/ruoyi-admin) | [ruoyi-admin](https://gitcode.com/ageerle/ruoyi-admin) |
+| 🎬 Drama | [ruoyi-drama](https://github.com/ageerle/ruoyi-drama) | [ruoyi-drama](https://gitee.com/ageerle/ruoyi-drama) | [ruoyi-drama](https://gitcode.com/ageerle/ruoyi-drama) |
+| 🤖 Copilot | [ruoyi-copilot](https://github.com/ageerle/ruoyi-copilot) | [ruoyi-copilot](https://gitee.com/ageerle/ruoyi-copilot) | [ruoyi-copilot](https://gitcode.com/ageerle/ruoyi-copilot) |
+| 📱 Mini-App | [ruoyi-uniapp](https://github.com/ageerle/ruoyi-uniapp) | [ruoyi-uniapp](https://gitee.com/ageerle/ruoyi-uniapp) | [ruoyi-uniapp](https://gitcode.com/ageerle/ruoyi-uniapp) |

-### 合作项目
-| 项目名称           | GitHub 仓库                                             | Gitee 仓库                                             
+### Partner Projects
+| Project Name           | GitHub Repository                                             | Gitee Repository |
 |----------------|-------------------------------------------------------|------------------------------------------------------|
-| element-plus-x | [element-plus-x](https://github.com/element-plus-x/Element-Plus-X)       | [element-plus-x](https://gitee.com/he-jiayue/element-plus-x)       | 
+| element-plus-x | [element-plus-x](https://github.com/element-plus-x/Element-Plus-X)       | [element-plus-x](https://gitee.com/he-jiayue/element-plus-x)       |

-## 🛠️ 技术架构
+## 🛠️ Technical Architecture

-### 核心框架
- **后端架构**：Spring Boot 3.5.8 + Langchain4j
- **数据存储**：MySQL 8.0 + Redis + 向量数据库（Milvus/Weaviate/Qdrant）
- **前端技术**：Vue 3 + Vben Admin + element-plus-x
- **安全认证**：Sa-Token + JWT 双重保障
- **文档处理**：PDF、Word、Excel 解析，图像智能分析
- **实时通信**：WebSocket 实时通信，SSE 流式响应
- **系统监控**：完善的日志体系、性能监控、服务健康检查
+### Core Framework
+- **Backend**: Spring Boot 3.5.8 + Langchain4j
+- **Data Storage**: MySQL 8.0 + Redis + Vector Databases (Milvus/Weaviate/Qdrant)
+- **Frontend**: Vue 3 + Vben Admin + element-plus-x
+- **Security**: Sa-Token + JWT dual-layer security
+- **Document Processing**: PDF, Word, Excel parsing, intelligent image analysis
+- **Real-time Communication**: WebSocket real-time communication, SSE streaming response
+- **System Monitoring**: Comprehensive logging system, performance monitoring, service health checks

-## 🐳 Docker 部署
+## 🐳 Docker Deployment

-本项目提供两种 Docker 部署方式：
+This project provides two Docker deployment methods:

-### 方式一：一键启动所有服务（推荐）
+### Method 1: One-click Start All Services (Recommended)

-使用 `docker-compose-all.yaml` 可以一键启动所有服务（包括后端、管理端、用户端及依赖服务）：
+Use `docker-compose-all.yaml` to start all services at once (including backend, admin panel, user frontend, and dependencies):

 ```bash
-# 克隆仓库
-git clone https://github.com/ageerle/ruoyi-ai.git
+# Requirements: Docker Engine and Docker Compose V2
+
+# Clone the v3.1.0 release
+git clone --depth 1 --branch v3.1.0 https://github.com/ageerle/ruoyi-ai.git
 cd ruoyi-ai

-# 启动所有服务（从镜像仓库拉取预构建镜像）
-docker-compose -f docker-compose-all.yaml up -d
+# Pin the image version. Public GHCR images do not require docker login.
+cp docs/docker/ruoyi-ai/.env.example docs/docker/ruoyi-ai/.env
+sed -i 's/^RUIYI_VERSION=.*/RUIYI_VERSION=v3.1.0/' docs/docker/ruoyi-ai/.env

-# 查看服务状态
-docker-compose -f docker-compose-all.yaml ps
+# Pull pre-built images from GHCR and start all services
+docker compose --env-file docs/docker/ruoyi-ai/.env \
+  -f docs/docker/ruoyi-ai/docker-compose-all.yaml pull
+docker compose --env-file docs/docker/ruoyi-ai/.env \
+  -f docs/docker/ruoyi-ai/docker-compose-all.yaml up -d

-# 访问服务
-# 管理端: http://localhost:25666 (admin / admin123)
-# 用户端: http://localhost:25137
-# 后端API: http://localhost:26039
+# Check service status
+docker compose --env-file docs/docker/ruoyi-ai/.env \
+  -f docs/docker/ruoyi-ai/docker-compose-all.yaml ps
+
+# Access services (replace SERVER_IP with the server address)
+# Admin Panel: http://SERVER_IP:25666 (admin / admin123)
+# User Frontend: http://SERVER_IP:25137
+# Backend API: http://SERVER_IP:26039
 ```

-### 方式二：分步部署（源码编译）
+The default Compose file also publishes MySQL (`23306`), Redis (`26379`),
+Weaviate (`28080`), and MinIO (`29000`/`29090`). For production deployments,
+change the default MySQL and MinIO passwords and expose only the application
+ports through the firewall or a reverse proxy.

-如果您需要从源码构建后端服务，请按照以下步骤操作：
+To upgrade to another published release, update `RUIYI_VERSION` in
+`docs/docker/ruoyi-ai/.env`, then run `docker compose pull` and
+`docker compose up -d` with the same `--env-file` and `-f` options. Do not use
+`docker compose down -v` unless you intend to delete persistent data volumes.

-#### 第一步：部署后端服务
+### Method 2: Step-by-step Deployment (Source Build)
+
+If you need to build backend services from source, follow these steps:
+
+#### Step 1: Deploy Backend Service

 ```bash
-# 进入后端项目目录
+# Enter backend project directory
 cd ruoyi-ai

-# 启动后端服务（源码编译构建）
+# Start backend service (build from source)
 docker-compose up -d --build

-# 等待后端服务启动完成
+# Wait for backend service to start
 docker-compose logs -f backend
 ```

-#### 第二步：部署管理端
+#### Step 2: Deploy Admin Panel

 ```bash
-# 进入管理端项目目录
+# Enter admin panel project directory
 cd ruoyi-admin

-# 构建并启动管理端
+# Build and start admin panel
 docker-compose up -d --build

-# 访问管理端
-# 地址: http://localhost:5666
+# Access admin panel
+# URL: http://localhost:5666
 ```

-#### 第三步：部署用户端（可选）
+#### Step 3: Deploy User Frontend (Optional)

 ```bash
-# 进入用户端项目目录
+# Enter user frontend project directory
 cd ruoyi-web

-# 构建并启动用户端
+# Build and start user frontend
 docker-compose up -d --build

-# 访问用户端
-# 地址: http://localhost:5137
+# Access user frontend
+# URL: http://localhost:5137
 ```

-### 服务端口说明
+### Service Ports

-| 服务 | 一键启动端口 | 分步部署端口 | 说明 |
+| Service | One-click Port | Step-by-step Port | Description |
 |------|-------------|-------------|------|
-| 管理端 | 25666 | 5666 | 管理后台访问地址 |
-| 用户端 | 25137 | 5137 | 用户前端访问地址 |
-| 后端服务 | 26039 | 6039 | 后端 API 服务 |
-| MySQL | 23306 | 23306 | 数据库服务 |
-| Redis | 26379 | 6379 | 缓存服务 |
-| Weaviate | 28080 | 28080 | 向量数据库 |
-| MinIO API | 29000 | 9000 | 对象存储 API |
-| MinIO Console | 29090 | 9090 | 对象存储控制台 |
+| Admin Panel | 25666 | 5666 | Admin backend access |
+| User Frontend | 25137 | 5137 | User frontend access |
+| Backend Service | 26039 | 6039 | Backend API service |
+| MySQL | 23306 | 23306 | Database service |
+| Redis | 26379 | 6379 | Cache service |
+| Weaviate | 28080 | 28080 | Vector database |
+| MinIO API | 29000 | 9000 | Object storage API |
+| MinIO Console | 29090 | 9090 | Object storage console |

-### 镜像仓库
+## 📚 Documentation

-所有镜像托管在阿里云容器镜像服务：
+Want to learn more about installation, deployment, configuration, and secondary development?

-```
-crpi-31mraxd99y2gqdgr.cn-beijing.personal.cr.aliyuncs.com/ruoyi_ai
-```
+**👉 [Complete Documentation](https://doc.ruoyiai.chat/)**

-可用镜像：
- `mysql:v3` - MySQL 数据库（包含初始化 SQL）
- `redis:6.2` - Redis 缓存
- `weaviate:1.30.0` - 向量数据库
- `minio:latest` - 对象存储
- `ruoyi-ai-backend:latest` - 后端服务
- `ruoyi-ai-admin:latest` - 管理端前端
- `ruoyi-ai-web:latest` - 用户端前端
+## 🤝 Contributing

-### 常用命令
+We warmly welcome community contributions! Whether you are a seasoned developer or just getting started, you can contribute to the project 💪

-```bash
-# 停止所有服务
-docker-compose -f docker-compose-all.yaml down
+### How to Contribute

-# 查看服务日志
-docker-compose -f docker-compose-all.yaml logs -f [服务名]
+1. **Fork** the project to your account
+2. **Create a branch** (`git checkout -b feature/new-feature-name`)
+3. **Commit your changes** (`git commit -m 'Add new feature'`)
+4. **Push to the branch** (`git push origin feature/new-feature-name`)
+5. **Create a Pull Request**

-# 重启某个服务
-docker-compose -f docker-compose-all.yaml restart [服务名]
-```
+> 💡 **Tip**: We recommend submitting PRs to GitHub, we will automatically sync to other code hosting platforms

-## 📚 使用文档
+## 📄 License

-想要深入了解安装部署、功能配置和二次开发？
+This project is licensed under the **MIT License**. See the [LICENSE](LICENSE) file for details.

-**👉 [完整使用文档](https://doc.ruoyiai.chat/)**
+## 🙏 Acknowledgments

-## 🤝 参与贡献
+Thanks to the following excellent open-source projects for their support:
+- [Langchain4j](https://github.com/langchain4j/langchain4j) - Powerful Java LLM development framework
+- [RuoYi-Vue-Plus](https://gitee.com/dromara/RuoYi-Vue-Plus) - Mature enterprise-level rapid development framework
+- [Vben Admin](https://github.com/vbenjs/vue-vben-admin) - Modern Vue admin template

-我们热烈欢迎社区贡献！无论您是资深开发者还是初学者，都可以为项目贡献力量 💪
+## 💎 Sponsors

-### 贡献方式
-
-1. **Fork** 项目到您的账户
-2. **创建分支** (`git checkout -b feature/新功能名称`)
-3. **提交代码** (`git commit -m '添加某某功能'`)
-4. **推送分支** (`git push origin feature/新功能名称`)
-5. **发起 Pull Request**
-
-> 💡 **小贴士**：建议将 PR 提交到 GitHub，我们会自动同步到其他代码托管平台
-
-## 📄 开源协议
-
-本项目采用 **MIT 开源协议**，详情请查看 [LICENSE](LICENSE) 文件。
-
-## 🙏 特别鸣谢
-
-感谢以下优秀的开源项目为本项目提供支持：
- [Langchain4j](https://github.com/langchain4j/langchain4j) - 强大的 Java LLM 开发框架
- [RuoYi-Vue-Plus](https://gitee.com/dromara/RuoYi-Vue-Plus) - 成熟的企业级快速开发框架
- [Vben Admin](https://github.com/vbenjs/vue-vben-admin) - 现代化的 Vue 后台管理模板
-
-
-## 💎 赞助商
-
-**感谢以下赞助商对本项目的支持：**
+**Thanks to the following sponsors for supporting this project:**

 <a href="https://www.atlascloud.ai?ref=89F97E">
  <img src="docs/image/sponsor/atlascloud_banner.png" alt="Atlas Cloud" width="160" height="80">
 </a>

-[访问Atlas Cloud官网](https://www.atlascloud.ai?ref=89F97E&utm_source=github&utm_campaign=ruoyi-drama) · [编程计划优惠](https://www.atlascloud.ai/console/coding-plan)
-全模态 AI 推理平台，为开发者提供统一的 AI API，支持视频生成、图像生成和大语言模型。一次接入，即可访问 **300+ 精选模型**。
+[Visit Atlas Cloud](https://www.atlascloud.ai?ref=89F97E&utm_source=github&utm_campaign=ruoyi-drama) · [Coding Plan Promotion](https://www.atlascloud.ai/console/coding-plan)
+A full-modal AI inference platform that gives developers a unified AI API, supporting video generation, image generation, and LLMs. Connect once to access **300+ curated models**.

 <a href="https://www.volcengine.com/activity/codingplan?utm_campaign=hw&utm_content=hw&utm_medium=devrel_tool_web&utm_source=OWO&utm_term=ageerle-ruoyi-ai">
-  <img src="docs/image/sponsor/huoshan.png" alt="火山引擎 CodingPlan" width="160" height="80">
+  <img src="docs/image/sponsor/huoshan.png" alt="Volcengine CodingPlan" width="160" height="80">
 </a>

-[注册即领2500万Tokens，立即前往](https://www.volcengine.com/activity/ai618?utm_campaign=hw&utm_content=hw&utm_medium=devrel_tool_web&utm_source=OWO&utm_term=ageerle-ruoyi-ai)
-享字节自研豆包模型+满血版开源 SOTA模型，覆盖文本、VLM、图像生成，全模态一站配齐：Seed-2.1、Seedream-5.0、GLM-5.2、DeepSeek等。不止编程、更能解决 Agent 复杂长程任务！
+[Sign up to claim 25 million tokens — go now](https://www.volcengine.com/activity/ai618?utm_campaign=hw&utm_content=hw&utm_medium=devrel_tool_web&utm_source=OWO&utm_term=ageerle-ruoyi-ai)
+Enjoy ByteDance's in-house Doubao models plus full-power open-source SOTA models, covering text, VLM, and image generation — all modalities in one stop: Seed-2.1, Seedream-5.0, GLM-5.2, DeepSeek, and more. Not just for coding — it can also tackle complex long-horizon Agent tasks!

-
-## 💬 社区交流
+## 💬 Community Chat

 <div align="center">

 <table>
 <tr>
 <td align="center">
-<img src="docs/image/wx.png" alt="微信二维码" width="200" height="200"><br>
-<strong>扫码添加作者微信</strong><br>
-<em>邀请进群学习</em>
+<img src="docs/image/wx.png" alt="WeChat QR Code" width="200" height="200"><br>
+<strong>Scan to add author on WeChat</strong><br>
+<em>Join group for learning</em>
 </td>
 <td align="center">
-<img src="docs/image/wx06.png" alt="微信二维码" width="200" height="200"><br>
-<strong>微信技术交流群</strong><br>
-<em>技术讨论</em>
+<img src="docs/image/douyin.png" alt="Douyin QR Code" width="200" height="200"><br>
+<strong>Douyin Video Tutorials</strong><br>
+<em>Open Douyin, scan & follow to watch video tutorials</em>
 </td>
 <td align="center">
-<img src="docs/image/qq.png" alt="QQ群二维码" width="200" height="200"><br>
-<strong>QQ技术交流群</strong><br>
-<em>技术讨论</em>
+<img src="docs/image/qq.png" alt="QQ Group QR Code" width="200" height="200"><br>
+<strong>QQ Tech Exchange Group</strong><br>
+<em>Technical discussion</em>
 </td>

 </tr>
@@ -253,11 +246,12 @@ docker-compose -f docker-compose-all.yaml restart [服务名]
 </div>

 ---
+
 <div align="center">

-**[⭐ 点个Star支持一下](https://github.com/ageerle/ruoyi-ai)** • **[ Fork 开始贡献](https://github.com/ageerle/ruoyi-ai/fork)** • **[📚 English](README_EN.md)** • **[📖 查看完整文档](https://doc.ruoyiai.chat/)**
+**[⭐ Star to Support](https://github.com/ageerle/ruoyi-ai)** • **[Fork to Contribute](https://github.com/ageerle/ruoyi-ai/fork)** • **[📚 中文](README_ZH.md)** • **[📖 Complete Documentation](https://doc.ruoyiai.chat/)**

-*用 ❤️ 打造，由 RuoYi AI 开源社区维护*
+*Built with ❤️, maintained by the RuoYi AI open-source community*

 </div>

--- a/README_EN.md
+++ b/README_EN.md
@@ -1,280 +0,0 @@
-
-# RuoYi AI
-
-<div align="center">
-
-[![Contributors][contributors-shield]][contributors-url]
-[![Forks][forks-shield]][forks-url]
-[![Stargazers][stars-shield]][stars-url]
-[![Issues][issues-shield]][issues-url]
-[![MIT License][license-shield]][license-url]
-
-
-<p align="center">
-  <a href="https://trendshift.io/repositories/13209">
-    <img src="https://trendshift.io/api/badge/repositories/13209" alt="GitHub Trending">
-  </a>
-</p>
-
-<img src="docs/image/logo.png" alt="RuoYi AI Logo" width="120" height="120">
-
-### Enterprise-Grade AI Assistant Platform
-
-*An out-of-the-box full-stack AI platform supporting multi-agent collaboration, Supervisor mode orchestration, and multiple decision models, with advanced RAG technology and visual workflow orchestration capabilities*
-
-**[中文](README.md)** | **[📖 Documentation](https://doc.ruoyiai.chat/)** |
-**[🚀 Live Demo](https://web.ruoyiai.chat/)** | **[🐛 Report Issues](https://github.com/ageerle/ruoyi-ai/issues)** | **[💡 Feature Requests](https://github.com/ageerle/ruoyi-ai/issues)**
-
-</div>
-
-
-
-
-## ✨ Core Features
-
-| Module | Current Capabilities |
-|:---:|---|
-| **Model Management** | Multi-model integration (OpenAI/DeepSeek/Tongyi/Zhipu/MiniMax), multi-modal understanding, Coze/DIFY/FastGPT platform integration |
-| **Knowledge Base** | Local RAG + Vector DB (Milvus/Weaviate/Qdrant) + Document parsing |
-| **Tool Management** | MCP protocol integration, Skills capability + Extensible tool ecosystem |
-| **Workflow Orchestration** | Visual workflow designer, drag-and-drop node orchestration, SSE streaming execution, currently supports model calls, email sending, manual review nodes |
-| **Multi-Agent** | Agent framework based on Langchain4j, Supervisor mode orchestration, supports multiple decision models |
-
-### Project Repositories
-
-| Module     | GitHub Repository                                             | Gitee Repository                                             | GitCode Repository                                             |
-|----------|-------------------------------------------------------|------------------------------------------------------|--------------------------------------------------------|
-| 🔧 Backend  | [ruoyi-ai](https://github.com/ageerle/ruoyi-ai)       | [ruoyi-ai](https://gitee.com/ageerle/ruoyi-ai)       | [ruoyi-ai](https://gitcode.com/ageerle/ruoyi-ai)       |
-| 🎨 User Frontend  | [ruoyi-web](https://github.com/ageerle/ruoyi-web)     | [ruoyi-web](https://gitee.com/ageerle/ruoyi-web)     | [ruoyi-web](https://gitcode.com/ageerle/ruoyi-web)     |
-| 🛠️ Admin Panel | [ruoyi-admin](https://github.com/ageerle/ruoyi-admin) | [ruoyi-admin](https://gitee.com/ageerle/ruoyi-admin) | [ruoyi-admin](https://gitcode.com/ageerle/ruoyi-admin) |
-| 🎬 Drama | [ruoyi-drama](https://github.com/ageerle/ruoyi-drama) | [ruoyi-drama](https://gitee.com/ageerle/ruoyi-drama) | |
-
-### Partner Projects
-| Project Name           | GitHub Repository                                             | Gitee Repository |
-|----------------|-------------------------------------------------------|------------------------------------------------------|
-| element-plus-x | [element-plus-x](https://github.com/element-plus-x/Element-Plus-X)       | [element-plus-x](https://gitee.com/he-jiayue/element-plus-x)       |
-
-## 🛠️ Technical Architecture
-
-### Core Framework
- **Backend**: Spring Boot 3.5.8 + Langchain4j
- **Data Storage**: MySQL 8.0 + Redis + Vector Databases (Milvus/Weaviate/Qdrant)
- **Frontend**: Vue 3 + Vben Admin + element-plus-x
- **Security**: Sa-Token + JWT dual-layer security
- **Document Processing**: PDF, Word, Excel parsing, intelligent image analysis
- **Real-time Communication**: WebSocket real-time communication, SSE streaming response
- **System Monitoring**: Comprehensive logging system, performance monitoring, service health checks
-
-## 🐳 Docker Deployment
-
-This project provides two Docker deployment methods:
-
-### Method 1: One-click Start All Services (Recommended)
-
-Use `docker-compose-all.yaml` to start all services at once (including backend, admin panel, user frontend, and dependencies):
-
-```bash
-# Clone the repository
-git clone https://github.com/ageerle/ruoyi-ai.git
-cd ruoyi-ai
-
-# Start all services (pull pre-built images from registry)
-docker-compose -f docker-compose-all.yaml up -d
-
-# Check service status
-docker-compose -f docker-compose-all.yaml ps
-
-# Access services
-# Admin Panel: http://localhost:25666 (admin / admin123)
-# User Frontend: http://localhost:25137
-# Backend API: http://localhost:26039
-```
-
-### Method 2: Step-by-step Deployment (Source Build)
-
-If you need to build backend services from source, follow these steps:
-
-#### Step 1: Deploy Backend Service
-
-```bash
-# Enter backend project directory
-cd ruoyi-ai
-
-# Start backend service (build from source)
-docker-compose up -d --build
-
-# Wait for backend service to start
-docker-compose logs -f backend
-```
-
-#### Step 2: Deploy Admin Panel
-
-```bash
-# Enter admin panel project directory
-cd ruoyi-admin
-
-# Build and start admin panel
-docker-compose up -d --build
-
-# Access admin panel
-# URL: http://localhost:5666
-```
-
-#### Step 3: Deploy User Frontend (Optional)
-
-```bash
-# Enter user frontend project directory
-cd ruoyi-web
-
-# Build and start user frontend
-docker-compose up -d --build
-
-# Access user frontend
-# URL: http://localhost:5137
-```
-
-### Service Ports
-
-| Service | One-click Port | Step-by-step Port | Description |
-|------|-------------|-------------|------|
-| Admin Panel | 25666 | 5666 | Admin backend access |
-| User Frontend | 25137 | 5137 | User frontend access |
-| Backend Service | 26039 | 6039 | Backend API service |
-| MySQL | 23306 | 23306 | Database service |
-| Redis | 26379 | 6379 | Cache service |
-| Weaviate | 28080 | 28080 | Vector database |
-| MinIO API | 29000 | 9000 | Object storage API |
-| MinIO Console | 29090 | 9090 | Object storage console |
-
-### Image Registry
-
-All images are hosted on Alibaba Cloud Container Registry:
-
-```
-crpi-31mraxd99y2gqdgr.cn-beijing.personal.cr.aliyuncs.com/ruoyi_ai
-```
-
-Available images:
- `mysql:v3` - MySQL database (includes initialization SQL)
- `redis:6.2` - Redis cache
- `weaviate:1.30.0` - Vector database
- `minio:latest` - Object storage
- `ruoyi-ai-backend:latest` - Backend service
- `ruoyi-ai-admin:latest` - Admin frontend
- `ruoyi-ai-web:latest` - User frontend
-
-### Common Commands
-
-```bash
-# Stop all services
-docker-compose -f docker-compose-all.yaml down
-
-# View service logs
-docker-compose -f docker-compose-all.yaml logs -f [service-name]
-
-# Restart a service
-docker-compose -f docker-compose-all.yaml restart [service-name]
-```
-
-## 📚 Documentation
-
-Want to learn more about installation, deployment, configuration, and secondary development?
-
-**👉 [Complete Documentation](https://doc.ruoyiai.chat/)**
-
-## 🤝 Contributing
-
-We warmly welcome community contributions! Whether you are a seasoned developer or just getting started, you can contribute to the project 💪
-
-### How to Contribute
-
-1. **Fork** the project to your account
-2. **Create a branch** (`git checkout -b feature/new-feature-name`)
-3. **Commit your changes** (`git commit -m 'Add new feature'`)
-4. **Push to the branch** (`git push origin feature/new-feature-name`)
-5. **Create a Pull Request**
-
-> 💡 **Tip**: We recommend submitting PRs to GitHub, we will automatically sync to other code hosting platforms
-
-## 📄 License
-
-This project is licensed under the **MIT License**. See the [LICENSE](LICENSE) file for details.
-
-## 🙏 Acknowledgments
-
-Thanks to the following excellent open-source projects for their support:
- [Langchain4j](https://github.com/langchain4j/langchain4j) - Powerful Java LLM development framework
- [RuoYi-Vue-Plus](https://gitee.com/dromara/RuoYi-Vue-Plus) - Mature enterprise-level rapid development framework
- [Vben Admin](https://github.com/vbenjs/vue-vben-admin) - Modern Vue admin template
-
-## 💎 Sponsors
-
-**Thanks to the following sponsors for supporting this project:**
-
-<a href="https://www.atlascloud.ai?ref=89F97E">
-  <img src="docs/image/sponsor/atlascloud_banner.png" alt="Atlas Cloud" width="160" height="80">
-</a>
-
-[Visit Atlas Cloud](https://www.atlascloud.ai?ref=89F97E) · [Coding Plan Promotion](https://www.atlascloud.ai/console/coding-plan)
-A full-modal AI inference platform that gives developers a unified AI API, supporting video generation, image generation, and LLMs. Connect once to access **300+ curated models**.
-
-<a href="https://www.volcengine.com/activity/codingplan?utm_campaign=hw&utm_content=hw&utm_medium=devrel_tool_web&utm_source=OWO&utm_term=ageerle-ruoyi-ai">
-  <img src="docs/image/sponsor/huoshan.png" alt="Volcengine CodingPlan" width="160" height="80">
-</a>
-
-[Volcengine CodingPlan Developer Program](https://www.volcengine.com/activity/codingplan?utm_campaign=hw&utm_content=hw&utm_medium=devrel_tool_web&utm_source=OWO&utm_term=ageerle-ruoyi-ai)
-Volcengine is ByteDance's cloud and AI service platform. Volcengine Ark provides API access to Doubao LLM, DeepSeek, and more — a one-stop AI development and inference platform for developers.
-
-## 💬 Community Chat
-
-<div align="center">
-
-<table>
-<tr>
-<td align="center">
-<img src="docs/image/wx.png" alt="WeChat QR Code" width="200" height="200"><br>
-<strong>Scan to add author on WeChat</strong><br>
-<em>Join group for learning</em>
-</td>
-<td align="center">
-<img src="docs/image/qq.png" alt="QQ Group QR Code" width="200" height="200"><br>
-<strong>QQ Tech Exchange Group</strong><br>
-<em>Technical discussion</em>
-</td>
-
-</tr>
-</table>
-
-</div>
-
---
-
-<div align="center">
-
-**[⭐ Star to Support](https://github.com/ageerle/ruoyi-ai)** • **[Fork to Contribute](https://github.com/ageerle/ruoyi-ai/fork)** • **[📚 中文](README.md)** • **[📖 Complete Documentation](https://doc.ruoyiai.chat/)**
-
-*Built with ❤️, maintained by the RuoYi AI open-source community*
-
-</div>
-
-<!-- Badge Links -->
-
-[contributors-shield]: https://img.shields.io/github/contributors/ageerle/ruoyi-ai.svg?style=flat-square
-
-[contributors-url]: https://github.com/ageerle/ruoyi-ai/graphs/contributors
-
-[forks-shield]: https://img.shields.io/github/forks/ageerle/ruoyi-ai.svg?style=flat-square
-
-[forks-url]: https://github.com/ageerle/ruoyi-ai/network/members
-
-[stars-shield]: https://img.shields.io/github/stars/ageerle/ruoyi-ai.svg?style=flat-square
-
-[stars-url]: https://github.com/ageerle/ruoyi-ai/stargazers
-
-[issues-shield]: https://img.shields.io/github/issues/ageerle/ruoyi-ai.svg?style=flat-square
-
-[issues-url]: https://github.com/ageerle/ruoyi-ai/issues
-
-[license-shield]: https://img.shields.io/github/license/ageerle/ruoyi-ai.svg?style=flat-square
-
-[license-url]: https://github.com/ageerle/ruoyi-ai/blob/main/LICENSE
--- a/README_ZH.md
+++ b/README_ZH.md
@@ -0,0 +1,277 @@
+# RuoYi AI
+
+<div align="center">
+
+[![Contributors][contributors-shield]][contributors-url] [![Forks][forks-shield]][forks-url] [![Stargazers][stars-shield]][stars-url] [![Issues][issues-shield]][issues-url] [![MIT License][license-shield]][license-url]
+
+
+<p align="center">
+  <a href="https://trendshift.io/repositories/13209">
+    <img src="https://trendshift.io/api/badge/repositories/13209" alt="GitHub Trending">
+  </a>
+</p>
+
+<img src="docs/image/logo.png" alt="RuoYi AI Logo" width="120" height="120">
+
+### 企业级AI助手平台
+
+*开箱即用的全栈AI平台，支持多智能体协同、Supervisor模式编排、多种决策模式、RAG技术和流程编排能力*
+
+**[English](README.md)** | **[📖 使用文档](https://doc.ruoyiai.chat/)** |
+**[🚀 在线体验](https://web.ruoyiai.chat/)** | **[🐛 问题反馈](https://github.com/ageerle/ruoyi-ai/issues)** | **[💡 功能建议](https://github.com/ageerle/ruoyi-ai/issues)**
+
+</div>
+
+
+## 🚀 演示地址
+
+| 服务 | 访问地址 | 默认账号 |
+|---|---|---|
+| 管理端 | http://129.226.199.247:25666 | admin / admin123 |
+| 用户端 | http://129.226.199.247:25137 | admin / admin123 |
+| 商业版 | https://web.ruoyiai.chat | 微信扫码登录 |
+
+## ✨ 核心亮点
+
+|    模块     | 现有能力
+|:---------:|---
+| **模型管理**  | 多模型接入(DeepSeek/智谱/MIMO/百炼/OpenAI)、多模态理解、Coze/DIFY/FastGPT/RAGFlow平台集成
+| **知识管理**  | 本地RAG + 向量库(Milvus/Weaviate/Qdrant)  + 文档解析
+| **工具管理**  | Mcp协议集成、Skills能力 + 可扩展工具生态
+| **流程编排**  | 可视化工作流设计器、节点拖拽编排、SSE流式执行,目前已经支持模型调用,邮件发送,人工审核等节点
+| **智能体管理** | 基于Langchain4j的Agent框架、Supervisor模式编排,支持多种决策模型,可以灵活搭配工具,skills
+
+
+### 项目源码
+
+| 项目模块     | GitHub 仓库                                             | Gitee 仓库                                             | GitCode 仓库                                             |
+|----------|-------------------------------------------------------|------------------------------------------------------|--------------------------------------------------------|
+| 🔧 后端服务  | [ruoyi-ai](https://github.com/ageerle/ruoyi-ai)       | [ruoyi-ai](https://gitee.com/ageerle/ruoyi-ai)       | [ruoyi-ai](https://gitcode.com/ageerle/ruoyi-ai)       |
+| 🎨 用户前端  | [ruoyi-web](https://github.com/ageerle/ruoyi-web)     | [ruoyi-web](https://gitee.com/ageerle/ruoyi-web)     | [ruoyi-web](https://gitcode.com/ageerle/ruoyi-web)     |
+| 🛠️ 管理后台 | [ruoyi-admin](https://github.com/ageerle/ruoyi-admin) | [ruoyi-admin](https://gitee.com/ageerle/ruoyi-admin) | [ruoyi-admin](https://gitcode.com/ageerle/ruoyi-admin) |
+| 🎬 短剧平台  | [ruoyi-drama](https://github.com/ageerle/ruoyi-drama) | [ruoyi-drama](https://gitee.com/ageerle/ruoyi-drama) | [ruoyi-drama](https://gitcode.com/ageerle/ruoyi-drama)   |
+| 🤖 编程助手  | [ruoyi-copilot](https://github.com/ageerle/ruoyi-copilot) | [ruoyi-copilot](https://gitee.com/ageerle/ruoyi-copilot) | [ruoyi-copilot](https://gitcode.com/ageerle/ruoyi-copilot) |
+| 📱 小程序端  | [ruoyi-uniapp](https://github.com/ageerle/ruoyi-uniapp) | [ruoyi-uniapp](https://gitee.com/ageerle/ruoyi-uniapp) | [ruoyi-uniapp](https://gitcode.com/ageerle/ruoyi-uniapp) |
+
+### 合作项目
+| 项目名称           | GitHub 仓库                                             | Gitee 仓库
+|----------------|-------------------------------------------------------|------------------------------------------------------|
+| element-plus-x | [element-plus-x](https://github.com/element-plus-x/Element-Plus-X)       | [element-plus-x](https://gitee.com/he-jiayue/element-plus-x)       |
+
+## 🛠️ 技术架构
+
+### 核心框架
+- **后端架构**：Spring Boot 3.5.8 + Langchain4j
+- **数据存储**：MySQL 8.0 + Redis + 向量数据库（Milvus/Weaviate/Qdrant）
+- **前端技术**：Vue 3 + Vben Admin + element-plus-x
+- **安全认证**：Sa-Token + JWT 双重保障
+- **文档处理**：PDF、Word、Excel 解析，图像智能分析
+- **实时通信**：WebSocket 实时通信，SSE 流式响应
+- **系统监控**：完善的日志体系、性能监控、服务健康检查
+
+## 🐳 Docker 部署
+
+本项目提供两种 Docker 部署方式：
+
+### 方式一：一键启动所有服务（推荐）
+
+使用 `docker-compose-all.yaml` 可以一键启动所有服务（包括后端、管理端、用户端及依赖服务）：
+
+```bash
+# 环境要求：Docker Engine 和 Docker Compose V2
+
+# 克隆 v3.1.0 版本
+git clone --depth 1 --branch v3.1.0 https://github.com/ageerle/ruoyi-ai.git
+cd ruoyi-ai
+
+# 固定镜像版本。GHCR 镜像已公开，无需 docker login
+cp docs/docker/ruoyi-ai/.env.example docs/docker/ruoyi-ai/.env
+sed -i 's/^RUIYI_VERSION=.*/RUIYI_VERSION=v3.1.0/' docs/docker/ruoyi-ai/.env
+
+# 从 GHCR 拉取预构建镜像并启动全部服务
+docker compose --env-file docs/docker/ruoyi-ai/.env \
+  -f docs/docker/ruoyi-ai/docker-compose-all.yaml pull
+docker compose --env-file docs/docker/ruoyi-ai/.env \
+  -f docs/docker/ruoyi-ai/docker-compose-all.yaml up -d
+
+# 查看服务状态
+docker compose --env-file docs/docker/ruoyi-ai/.env \
+  -f docs/docker/ruoyi-ai/docker-compose-all.yaml ps
+
+# 访问服务（将 SERVER_IP 替换为服务器地址）
+# 管理端: http://SERVER_IP:25666 (admin / admin123)
+# 用户端: http://SERVER_IP:25137
+# 后端API: http://SERVER_IP:26039
+```
+
+默认 Compose 还会发布 MySQL（`23306`）、Redis（`26379`）、Weaviate（`28080`）和
+MinIO（`29000`/`29090`）端口。生产环境请修改 MySQL 和 MinIO 默认密码，并通过防火墙或反向代理只开放应用端口。
+
+升级到其他已发布版本时，修改 `docs/docker/ruoyi-ai/.env` 中的 `RUIYI_VERSION`，然后使用相同的
+`--env-file` 和 `-f` 参数执行 `docker compose pull`、`docker compose up -d`。除非确定要删除持久化数据卷，
+不要执行 `docker compose down -v`。
+
+### 方式二：分步部署（源码编译）
+
+如果您需要从源码构建后端服务，请按照以下步骤操作：
+
+#### 第一步：部署后端服务
+
+```bash
+# 进入后端项目目录
+cd ruoyi-ai
+
+# 启动后端服务（源码编译构建）
+docker-compose up -d --build
+
+# 等待后端服务启动完成
+docker-compose logs -f backend
+```
+
+#### 第二步：部署管理端
+
+```bash
+# 进入管理端项目目录
+cd ruoyi-admin
+
+# 构建并启动管理端
+docker-compose up -d --build
+
+# 访问管理端
+# 地址: http://localhost:5666
+```
+
+#### 第三步：部署用户端（可选）
+
+```bash
+# 进入用户端项目目录
+cd ruoyi-web
+
+# 构建并启动用户端
+docker-compose up -d --build
+
+# 访问用户端
+# 地址: http://localhost:5137
+```
+
+### 服务端口说明
+
+| 服务 | 一键启动端口 | 分步部署端口 | 说明 |
+|------|-------------|-------------|------|
+| 管理端 | 25666 | 5666 | 管理后台访问地址 |
+| 用户端 | 25137 | 5137 | 用户前端访问地址 |
+| 后端服务 | 26039 | 6039 | 后端 API 服务 |
+| MySQL | 23306 | 23306 | 数据库服务 |
+| Redis | 26379 | 6379 | 缓存服务 |
+| Weaviate | 28080 | 28080 | 向量数据库 |
+| MinIO API | 29000 | 9000 | 对象存储 API |
+| MinIO Console | 29090 | 9090 | 对象存储控制台 |
+
+## 📚 使用文档
+
+想要深入了解安装部署、功能配置和二次开发？
+
+**👉 [完整使用文档](https://doc.ruoyiai.chat/)**
+
+## 🤝 参与贡献
+
+我们热烈欢迎社区贡献！无论您是资深开发者还是初学者，都可以为项目贡献力量 💪
+
+### 贡献方式
+
+1. **Fork** 项目到您的账户
+2. **创建分支** (`git checkout -b feature/新功能名称`)
+3. **提交代码** (`git commit -m '添加某某功能'`)
+4. **推送分支** (`git push origin feature/新功能名称`)
+5. **发起 Pull Request**
+
+> 💡 **小贴士**：建议将 PR 提交到 GitHub，我们会自动同步到其他代码托管平台
+
+## 📄 开源协议
+
+本项目采用 **MIT 开源协议**，详情请查看 [LICENSE](LICENSE) 文件。
+
+## 🙏 特别鸣谢
+
+感谢以下优秀的开源项目为本项目提供支持：
+- [Langchain4j](https://github.com/langchain4j/langchain4j) - 强大的 Java LLM 开发框架
+- [RuoYi-Vue-Plus](https://gitee.com/dromara/RuoYi-Vue-Plus) - 成熟的企业级快速开发框架
+- [Vben Admin](https://github.com/vbenjs/vue-vben-admin) - 现代化的 Vue 后台管理模板
+
+
+## 💎 赞助商
+
+**感谢以下赞助商对本项目的支持：**
+
+<a href="https://www.atlascloud.ai?ref=89F97E">
+  <img src="docs/image/sponsor/atlascloud_banner.png" alt="Atlas Cloud" width="160" height="80">
+</a>
+
+[访问Atlas Cloud官网](https://www.atlascloud.ai?ref=89F97E&utm_source=github&utm_campaign=ruoyi-drama) · [编程计划优惠](https://www.atlascloud.ai/console/coding-plan)
+全模态 AI 推理平台，为开发者提供统一的 AI API，支持视频生成、图像生成和大语言模型。一次接入，即可访问 **300+ 精选模型**。
+
+<a href="https://www.volcengine.com/activity/codingplan?utm_campaign=hw&utm_content=hw&utm_medium=devrel_tool_web&utm_source=OWO&utm_term=ageerle-ruoyi-ai">
+  <img src="docs/image/sponsor/huoshan.png" alt="火山引擎 CodingPlan" width="160" height="80">
+</a>
+
+[注册即领2500万Tokens，立即前往](https://www.volcengine.com/activity/ai618?utm_campaign=hw&utm_content=hw&utm_medium=devrel_tool_web&utm_source=OWO&utm_term=ageerle-ruoyi-ai)
+享字节自研豆包模型+满血版开源 SOTA模型，覆盖文本、VLM、图像生成，全模态一站配齐：Seed-2.1、Seedream-5.0、GLM-5.2、DeepSeek等。不止编程、更能解决 Agent 复杂长程任务！
+
+
+## 💬 社区交流
+
+<div align="center">
+
+<table>
+<tr>
+<td align="center">
+<img src="docs/image/wx.png" alt="微信二维码" width="200" height="200"><br>
+<strong>扫码添加作者微信</strong><br>
+<em>邀请进群学习</em>
+</td>
+<td align="center">
+<img src="docs/image/douyin.png" alt="抖音二维码" width="200" height="200"><br>
+<strong>抖音视频教程</strong><br>
+<em>打开抖音扫一扫，关注查看视频教程</em>
+</td>
+<td align="center">
+<img src="docs/image/qq.png" alt="QQ群二维码" width="200" height="200"><br>
+<strong>QQ技术交流群</strong><br>
+<em>技术讨论</em>
+</td>
+
+</tr>
+</table>
+
+</div>
+
+---
+<div align="center">
+
+**[⭐ 点个Star支持一下](https://github.com/ageerle/ruoyi-ai)** • **[ Fork 开始贡献](https://github.com/ageerle/ruoyi-ai/fork)** • **[📚 English](README.md)** • **[📖 查看完整文档](https://doc.ruoyiai.chat/)**
+
+*用 ❤️ 打造，由 RuoYi AI 开源社区维护*
+
+</div>
+
+<!-- Badge Links -->
+
+[contributors-shield]: https://img.shields.io/github/contributors/ageerle/ruoyi-ai.svg?style=flat-square
+
+[contributors-url]: https://github.com/ageerle/ruoyi-ai/graphs/contributors
+
+[forks-shield]: https://img.shields.io/github/forks/ageerle/ruoyi-ai.svg?style=flat-square
+
+[forks-url]: https://github.com/ageerle/ruoyi-ai/network/members
+
+[stars-shield]: https://img.shields.io/github/stars/ageerle/ruoyi-ai.svg?style=flat-square
+
+[stars-url]: https://github.com/ageerle/ruoyi-ai/stargazers
+
+[issues-shield]: https://img.shields.io/github/issues/ageerle/ruoyi-ai.svg?style=flat-square
+
+[issues-url]: https://github.com/ageerle/ruoyi-ai/issues
+
+[license-shield]: https://img.shields.io/github/license/ageerle/ruoyi-ai.svg?style=flat-square
+
+[license-url]: https://github.com/ageerle/ruoyi-ai/blob/main/LICENSE
--- a/docs/docker/milvus/docker-compose.yml
+++ b/docs/docker/milvus/docker-compose.yml
@@ -1,8 +1,6 @@
-version: '3.5'
- 
 services:
  etcd:
-    container_name: milvus-etcd
+    container_name: ruoyi-rag-milvus-etcd
    image: quay.io/coreos/etcd:v3.5.18
    environment:
      - ETCD_AUTO_COMPACTION_MODE=revision
@@ -19,14 +17,11 @@ services:
      retries: 3
 
  minio:
-    container_name: milvus-minio
+    container_name: ruoyi-rag-milvus-minio
    image: minio/minio:RELEASE.2023-03-20T20-16-18Z
    environment:
      MINIO_ACCESS_KEY: minioadmin
      MINIO_SECRET_KEY: minioadmin
-    ports:
-      - "9001:9001"
-      - "9000:9000"
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/minio:/minio_data
    command: minio server /minio_data --console-address ":9001"
@@ -37,7 +32,7 @@ services:
      retries: 3
 
  standalone:
-    container_name: milvus-standalone
+    container_name: ruoyi-rag-milvus
    image: milvusdb/milvus:v2.5.7
    command: ["milvus", "run", "standalone"]
    security_opt:
@@ -61,7 +56,7 @@ services:
      - "minio"
 
  attu:
-    container_name: attu
+    container_name: ruoyi-rag-attu
    image: zilliz/attu:v2.5.7
    environment:
      MILVUS_URL: milvus-standalone:19530
@@ -72,4 +67,4 @@ services:
 
 networks:
  default:
-    name: milvus
+    name: ruoyi-rag-milvus
--- a/docs/docker/qdrant/docker-compose.yml
+++ b/docs/docker/qdrant/docker-compose.yml
@@ -1,12 +1,20 @@
 ---
 services:
  qdrant:
-    image: qdrant/qdrant:latest
+    container_name: ruoyi-rag-qdrant
+    image: qdrant/qdrant:v1.17.0
    ports:
      - 6333:6333
      - 6334:6334
    volumes:
      - qdrant_data:/qdrant/storage
+    healthcheck:
+      test: ["CMD-SHELL", "bash -c 'exec 3<>/dev/tcp/127.0.0.1/6333 && printf \"GET /healthz HTTP/1.1\\r\\nHost: localhost\\r\\nConnection: close\\r\\n\\r\\n\" >&3 && grep -q \"200 OK\" <&3'"]
+      interval: 10s
+      timeout: 5s
+      retries: 12
+      start_period: 10s
+    restart: unless-stopped
 volumes:
  qdrant_data:
 ...
--- a/docs/docker/ruoyi-ai/.env.example
+++ b/docs/docker/ruoyi-ai/.env.example
@@ -0,0 +1,6 @@
+# GitHub Container Registry namespace owner.
+# For the upstream project this is ageerle; change it when using a fork.
+IMAGE_OWNER=ageerle
+
+# Use latest for convenience, or pin a release such as v3.1.0.
+RUIYI_VERSION=latest
--- a/docs/docker/ruoyi-ai/Dockerfile.mysql
+++ b/docs/docker/ruoyi-ai/Dockerfile.mysql
@@ -1,16 +1,14 @@
 # 基于官方MySQL 8.0镜像构建自定义镜像
 # 构建命令: docker build -t registry.cn-hangzhou.aliyuncs.com/ruoyi-ai/mysql:v3 -f Dockerfile.mysql .
-FROM mysql:8.0.33
+FROM mysql:8.0

 # 设置时区
 ENV TZ=Asia/Shanghai

-# 复制初始化脚本和SQL文件到镜像中
-COPY docs/script/docker/mysql/init/init-db.sh /docker-entrypoint-initdb.d/init-db.sh
-COPY docs/script/sql/ruoyi-ai-v3_mysql8.sql /docker-entrypoint-initdb.d/ruoyi-ai-v3_mysql8.sql
-
-# 设置脚本可执行权限
-RUN chmod +x /docker-entrypoint-initdb.d/init-db.sh
+# MySQL 官方入口会按文件名顺序执行初始化目录中的 SQL。
+# ruoyi-ai.sql 会导入 MYSQL_DATABASE，snail_job_mysql.sql 会自行创建并切换数据库。
+COPY docs/script/sql/ruoyi-ai.sql /docker-entrypoint-initdb.d/01-ruoyi-ai.sql
+COPY docs/script/sql/snail_job_mysql.sql /docker-entrypoint-initdb.d/02-snail-job.sql

 # MySQL启动参数
 CMD ["--default-authentication-plugin=mysql_native_password", \
@@ -18,4 +16,4 @@ CMD ["--default-authentication-plugin=mysql_native_password", \
     "--collation-server=utf8mb4_general_ci", \
     "--explicit_defaults_for_timestamp=true", \
     "--lower_case_table_names=1", \
-     "--skip-ssl"]
+     "--skip-ssl"]
--- a/docs/docker/ruoyi-ai/docker-compose-all.yaml
+++ b/docs/docker/ruoyi-ai/docker-compose-all.yaml
@@ -10,15 +10,13 @@
 #   - RuoYi-Admin (管理端前端)
 #   - RuoYi-Web (用户端前端)
 #
-# 镜像仓库地址: crpi-31mraxd99y2gqdgr.cn-beijing.personal.cr.aliyuncs.com/ruoyi_ai
-
-version: '3.8'
+# 镜像仓库地址: ghcr.io/ageerle

 services:
  # ==================== MySQL 数据库 ====================
  mysql:
-    # 阿里云镜像地址（包含初始化SQL）
-    image: crpi-31mraxd99y2gqdgr.cn-beijing.personal.cr.aliyuncs.com/ruoyi_ai/mysql:v3
+    # GHCR 镜像（包含初始化SQL）
+    image: ghcr.io/${IMAGE_OWNER:-ageerle}/ruoyi-ai-mysql:${RUIYI_VERSION:-latest}
    container_name: ruoyi-ai-mysql
    restart: always
    ports:
@@ -30,7 +28,10 @@ services:
    volumes:
      - mysql-data:/var/lib/mysql
    healthcheck:
-      test: ["CMD", "mysqladmin", "ping", "-h", "localhost", "-u", "root", "-proot"]
+      # Force TCP: during first-time initialization MySQL exposes a temporary
+      # socket-only server. A socket ping would mark the service healthy before
+      # the real network listener (used by the backend) is ready.
+      test: ["CMD", "mysqladmin", "ping", "--protocol=tcp", "-h", "127.0.0.1", "-u", "root", "-proot"]
      interval: 15s
      timeout: 10s
      retries: 10
@@ -40,7 +41,7 @@ services:

  # ==================== Redis 缓存 ====================
  redis:
-    image: crpi-31mraxd99y2gqdgr.cn-beijing.personal.cr.aliyuncs.com/ruoyi_ai/redis:6.2
+    image: redis:6.2
    container_name: ruoyi-ai-redis
    restart: always
    ports:
@@ -58,7 +59,7 @@ services:

  # ==================== Weaviate 向量数据库 ====================
  weaviate:
-    image: crpi-31mraxd99y2gqdgr.cn-beijing.personal.cr.aliyuncs.com/ruoyi_ai/weaviate:1.30.0
+    image: semitechnologies/weaviate:1.30.0
    container_name: ruoyi-ai-weaviate
    restart: always
    ports:
@@ -77,7 +78,7 @@ services:

  # ==================== MinIO 对象存储 ====================
  minio:
-    image: crpi-31mraxd99y2gqdgr.cn-beijing.personal.cr.aliyuncs.com/ruoyi_ai/minio:latest
+    image: minio/minio:latest
    container_name: ruoyi-ai-minio
    restart: always
    ports:
@@ -94,7 +95,7 @@ services:

  # ==================== RuoYi-AI 后端服务 ====================
  backend:
-    image: crpi-31mraxd99y2gqdgr.cn-beijing.personal.cr.aliyuncs.com/ruoyi_ai/ruoyi-ai-backend:latest
+    image: ghcr.io/${IMAGE_OWNER:-ageerle}/ruoyi-ai-backend:${RUIYI_VERSION:-latest}
    container_name: ruoyi-ai-backend
    restart: always
    ports:
@@ -128,7 +129,7 @@ services:

  # ==================== RuoYi-AI 管理端前端 ====================
  admin-frontend:
-    image: crpi-31mraxd99y2gqdgr.cn-beijing.personal.cr.aliyuncs.com/ruoyi_ai/ruoyi-ai-admin:latest
+    image: ghcr.io/${IMAGE_OWNER:-ageerle}/ruoyi-ai-admin:${RUIYI_VERSION:-latest}
    container_name: ruoyi-ai-admin
    restart: always
    ports:
@@ -153,7 +154,7 @@ services:

  # ==================== RuoYi-AI 用户端前端 ====================
  web-frontend:
-    image: crpi-31mraxd99y2gqdgr.cn-beijing.personal.cr.aliyuncs.com/ruoyi_ai/ruoyi-ai-web:latest
+    image: ghcr.io/${IMAGE_OWNER:-ageerle}/ruoyi-ai-web:${RUIYI_VERSION:-latest}
    container_name: ruoyi-ai-web
    restart: always
    ports:
@@ -177,4 +178,4 @@ volumes:
  weaviate-data:
  minio-data:
  logs-data:
-  upload-data:
+  upload-data:
--- a/docs/docker/ruoyi-ai/docker-compose.yaml
+++ b/docs/docker/ruoyi-ai/docker-compose.yaml
@@ -21,8 +21,8 @@ services:
      MYSQL_DATABASE: ruoyi-ai-agent
      TZ: Asia/Shanghai
    volumes:
-      - ./docs/script/docker/mysql/init/init-db.sh:/docker-entrypoint-initdb.d/init-db.sh:ro
-      - ./docs/script/sql/ruoyi-ai-v3_mysql8.sql:/docker-entrypoint-initdb.d/ruoyi-ai-v3_mysql8.sql:ro
+      - ../../script/sql/ruoyi-ai.sql:/docker-entrypoint-initdb.d/01-ruoyi-ai.sql:ro
+      - ../../script/sql/snail_job_mysql.sql:/docker-entrypoint-initdb.d/02-snail-job.sql:ro
      - mysql-data:/var/lib/mysql
    command:
      --default-authentication-plugin=mysql_native_password
@@ -32,7 +32,9 @@ services:
      --lower_case_table_names=1
      --skip-ssl
    healthcheck:
-      test: ["CMD", "mysqladmin", "ping", "-h", "localhost", "-u", "root", "-proot"]
+      # Do not let the socket-only initialization server satisfy the check.
+      # The backend connects over TCP and must wait for that listener.
+      test: ["CMD", "mysqladmin", "ping", "--protocol=tcp", "-h", "127.0.0.1", "-u", "root", "-proot"]
      interval: 15s
      timeout: 10s
      retries: 10
--- a/docs/docker/weaviate/docker-compose.yml
+++ b/docs/docker/weaviate/docker-compose.yml
@@ -5,12 +5,12 @@ services:
      - --host
      - 0.0.0.0
      - --port
-      - '6038'
+      - '8080'
      - --scheme
      - http
-    image: semitechnologies/weaviate:1.19.7
+    image: semitechnologies/weaviate:1.30.0
    ports:
-      - 6038:6038
+      - 28080:8080
      - 50051:50051
    volumes:
      - weaviate_data:/var/lib/weaviate
--- a/docs/image/douyin.png
+++ b/docs/image/douyin.png
--- a/docs/image/dy.png
+++ b/docs/image/dy.png
--- a/docs/image/wx06.png
+++ b/docs/image/wx06.png
--- a/docs/script/sql/ruoyi-ai-v3_mysql8.sql
+++ b/docs/script/sql/ruoyi-ai-v3_mysql8.sql
--- a/docs/script/sql/snail_job_mysql.sql
+++ b/docs/script/sql/snail_job_mysql.sql
--- a/docs/script/sql/update/2026-07-20-knowledge-fragment-fid.sql
+++ b/docs/script/sql/update/2026-07-20-knowledge-fragment-fid.sql
@@ -0,0 +1,58 @@
+-- RAG metadata migration (MySQL 8). Safe to execute repeatedly.
+-- 注意：MySQL 8 不支持 ALTER TABLE ... ADD COLUMN IF NOT EXISTS（仅 MariaDB 支持），
+-- 因此列的增量添加统一用 information_schema 守卫 + PREPARE 实现幂等。
+SET @add_file_hash_col = IF(EXISTS(
+    SELECT 1 FROM information_schema.columns WHERE table_schema = DATABASE()
+    AND table_name = 'knowledge_attach' AND column_name = 'file_hash'),
+    'SELECT 1',
+    'ALTER TABLE `knowledge_attach` ADD COLUMN `file_hash` varchar(64) NULL DEFAULT NULL COMMENT ''文件SHA-256摘要'' AFTER `doc_id`');
+PREPARE stmt FROM @add_file_hash_col; EXECUTE stmt; DEALLOCATE PREPARE stmt;
+
+ALTER TABLE `knowledge_attach`
+    MODIFY COLUMN `doc_id` varchar(32) NULL DEFAULT NULL COMMENT '文档ID';
+
+SET @add_file_hash = IF(EXISTS(
+    SELECT 1 FROM information_schema.statistics WHERE table_schema = DATABASE()
+    AND table_name = 'knowledge_attach' AND index_name = 'uk_knowledge_file_hash'),
+    'SELECT 1', 'ALTER TABLE `knowledge_attach` ADD UNIQUE INDEX `uk_knowledge_file_hash` (`knowledge_id`, `file_hash`)');
+PREPARE stmt FROM @add_file_hash; EXECUTE stmt; DEALLOCATE PREPARE stmt;
+
+SET @add_fid_col = IF(EXISTS(
+    SELECT 1 FROM information_schema.columns WHERE table_schema = DATABASE()
+    AND table_name = 'knowledge_fragment' AND column_name = 'fid'),
+    'SELECT 1',
+    'ALTER TABLE `knowledge_fragment` ADD COLUMN `fid` varchar(32) NULL DEFAULT NULL COMMENT ''向量库片段ID'' AFTER `id`');
+PREPARE stmt FROM @add_fid_col; EXECUTE stmt; DEALLOCATE PREPARE stmt;
+
+ALTER TABLE `knowledge_fragment`
+    MODIFY COLUMN `doc_id` varchar(32) NULL DEFAULT NULL COMMENT '文档ID';
+
+UPDATE `knowledge_fragment`
+SET `fid` = LOWER(MD5(CONCAT('knowledge_fragment:', `id`)))
+WHERE `fid` IS NULL OR `fid` = '';
+
+SET @drop_idx_fid = IF(EXISTS(
+    SELECT 1 FROM information_schema.statistics WHERE table_schema = DATABASE()
+    AND table_name = 'knowledge_fragment' AND index_name = 'idx_fid'),
+    'ALTER TABLE `knowledge_fragment` DROP INDEX `idx_fid`', 'SELECT 1');
+PREPARE stmt FROM @drop_idx_fid; EXECUTE stmt; DEALLOCATE PREPARE stmt;
+
+SET @add_uk_fid = IF(EXISTS(
+    SELECT 1 FROM information_schema.statistics WHERE table_schema = DATABASE()
+    AND table_name = 'knowledge_fragment' AND index_name = 'uk_fid'),
+    'SELECT 1', 'ALTER TABLE `knowledge_fragment` ADD UNIQUE INDEX `uk_fid` (`fid`)');
+PREPARE stmt FROM @add_uk_fid; EXECUTE stmt; DEALLOCATE PREPARE stmt;
+
+ALTER TABLE `knowledge_fragment` MODIFY COLUMN `fid` varchar(32) NOT NULL COMMENT '向量库片段ID';
+
+SET @add_tenant_user = IF(EXISTS(
+    SELECT 1 FROM information_schema.statistics WHERE table_schema = DATABASE()
+    AND table_name = 'knowledge_info' AND index_name = 'idx_tenant_user'),
+    'SELECT 1', 'ALTER TABLE `knowledge_info` ADD INDEX `idx_tenant_user` (`tenant_id`, `user_id`)');
+PREPARE stmt FROM @add_tenant_user; EXECUTE stmt; DEALLOCATE PREPARE stmt;
+
+SET @add_tenant_share = IF(EXISTS(
+    SELECT 1 FROM information_schema.statistics WHERE table_schema = DATABASE()
+    AND table_name = 'knowledge_info' AND index_name = 'idx_tenant_share'),
+    'SELECT 1', 'ALTER TABLE `knowledge_info` ADD INDEX `idx_tenant_share` (`tenant_id`, `share`)');
+PREPARE stmt FROM @add_tenant_share; EXECUTE stmt; DEALLOCATE PREPARE stmt;
--- a/docs/script/sql/update/2026-07-21-chat-provider-icon-length.sql
+++ b/docs/script/sql/update/2026-07-21-chat-provider-icon-length.sql
@@ -0,0 +1,7 @@
+-- 加宽 chat_provider.provider_icon 字段 (对应 issue IHPUDA)
+-- 背景：文件系统使用 minio 私有桶时，厂商图标存的是带签名的临时访问 URL，
+--       长度常超过 255，导致「Data too long for column 'provider_icon'」。
+-- MODIFY COLUMN 可重复执行。
+
+ALTER TABLE `chat_provider`
+    MODIFY COLUMN `provider_icon` varchar(1000) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NULL DEFAULT NULL COMMENT '厂商图标';
--- a/docs/script/sql/update/2026-07-21-sys-config-node-template.sql
+++ b/docs/script/sql/update/2026-07-21-sys-config-node-template.sql
@@ -0,0 +1,33 @@
+-- 补充工作流节点消息模板配置 (对应 issue IJX5VV)
+-- 背景：NodeMessageTemplateEnum 依赖以下 7 个 sys_config 键，缺失时
+--       WorkflowMessageUtil.getNodeMessageTemplate 会抛出「请先配置该节点的响应模板」。
+-- 这批配置在历史提交 20d531c0 中存在，SQL 脚本合并重命名时遗失，此处恢复。
+-- 幂等：按 config_key + tenant_id 判重，可重复执行。
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027192921483309058, '000000', 'HTTP请求节点响应模板', 'node.httpRequest.template', '✅ HTTP请求节点：结束响应 - ', 'Y', 103, 1, '2026-02-27 09:23:51', 1, '2026-02-27 09:31:41', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.httpRequest.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027193296990957569, '000000', '文生图节点响应模板', 'node.image.template', '🎨 文生图节点：结束响应 - 图片URL: ', 'Y', 103, 1, '2026-02-27 09:25:20', 1, '2026-02-27 09:31:52', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.image.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027193820393959425, '000000', '发送邮箱节点响应模板', 'node.mailsend.template', '📧 发送邮箱节点：结束响应 - ', 'Y', 103, 1, '2026-02-27 09:27:25', 1, '2026-02-27 09:32:05', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.mailsend.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027194134438277122, '000000', '结束节点响应模板', 'node.end.template', '🔚 流程已执行完毕，如果您有其他需求，请随时重新发起请求。', 'Y', 103, 1, '2026-02-27 09:28:40', 1, '2026-02-27 09:32:53', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.end.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027208880369647617, '000000', '条件分支节点响应模板', 'node.switch.template', '🔀 条件分支节点：触发 -> 跳转到节点 ', 'Y', 103, 1, '2026-02-27 10:27:15', 1, '2026-02-27 10:35:54', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.switch.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027213914603995137, '000000', '大模型回答节点响应模板', 'node.llmAnswer.template', '🤖 LLM 节点 生成回答：', 'Y', 103, 1, '2026-02-27 10:47:16', 1, '2026-02-27 10:52:40', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.llmAnswer.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027217577397391361, '000000', '工作流异常响应模板', 'node.exception.template', '🛑 工作流发生异常：', 'N', 103, 1, '2026-02-27 11:01:49', 1, '2026-02-27 11:02:01', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.exception.template' AND `tenant_id` = '000000');
--- a/docs/script/sql/update/2026-07-24-register-default-role-and-missing-menus.sql
+++ b/docs/script/sql/update/2026-07-24-register-default-role-and-missing-menus.sql
@@ -0,0 +1,119 @@
+-- 注册链路修复：补齐缺失的菜单权限标识 + 新建注册默认角色
+-- 关联问题：
+--   #3 注册用户无默认角色 -> 无权限访问 AI 对话界面
+--   #4 sys_menu 缺 system:session:* / system:attach:* / system:fragment:*，
+--      且 知识管理 父菜单 perms 为 knowledge:info:list，与控制器
+--      KnowledgeInfoController 用的 system:info:list 对不上，:list 无法授权。
+-- 本脚本幂等，可重复执行（INSERT IGNORE + UPDATE 天然幂等）。
+-- 新增 menu_id / role_id / config_id 统一使用 2099010100000000xxx 段，
+-- 与现有 snowflake id（2xxxxxxxxxxxxxxxxx）不冲突。
+
+-- ============================================================
+-- 1. 修正 知识管理 父菜单权限标识：knowledge:info:list -> system:info:list
+-- ============================================================
+UPDATE `sys_menu`
+SET `perms` = 'system:info:list'
+WHERE `menu_id` = 2006681261898813441 AND `perms` = 'knowledge:info:list';
+
+-- ============================================================
+-- 2. 新增 会话管理 菜单组（system:session:*）
+--    父菜单=对话管理(2000209300188356609)。
+--    管理端暂无 chat/session 页面，故 C 菜单设为隐藏(visible=1)，
+--    权限标识仍可在角色管理中授权给用户端使用。
+-- ============================================================
+INSERT IGNORE INTO `sys_menu` VALUES
+(2099010100000000001, '会话管理', 2000209300188356609, 6, 'session', NULL, NULL, 1, 0, 'C', '1', '0', 'system:session:list', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, '会话管理菜单'),
+(2099010100000000002, '会话管理查询', 2099010100000000001, 1, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:session:query', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000003, '会话管理新增', 2099010100000000001, 2, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:session:add', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000004, '会话管理修改', 2099010100000000001, 3, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:session:edit', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000005, '会话管理删除', 2099010100000000001, 4, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:session:remove', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000006, '会话管理导出', 2099010100000000001, 5, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:session:export', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, '');
+
+-- ============================================================
+-- 3. 新增 知识附件 菜单组（system:attach:*）
+--    父菜单=对话管理(2000209300188356609)，组件对应管理端 knowledge/attach/index。
+-- ============================================================
+INSERT IGNORE INTO `sys_menu` VALUES
+(2099010100000000010, '知识附件', 2000209300188356609, 7, 'attach', 'knowledge/attach/index', NULL, 1, 0, 'C', '0', '0', 'system:attach:list', 'ant-design:paper-clip-outlined', 103, 1, '2026-07-24 00:00:00', NULL, NULL, '知识附件菜单'),
+(2099010100000000011, '知识附件查询', 2099010100000000010, 1, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:attach:query', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000012, '知识附件新增', 2099010100000000010, 2, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:attach:add', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000013, '知识附件修改', 2099010100000000010, 3, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:attach:edit', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000014, '知识附件删除', 2099010100000000010, 4, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:attach:remove', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000015, '知识附件导出', 2099010100000000010, 5, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:attach:export', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, '');
+
+-- ============================================================
+-- 4. 新增 知识片段 菜单组（system:fragment:*）
+--    父菜单=对话管理(2000209300188356609)，组件对应管理端 knowledge/fragment/index。
+-- ============================================================
+INSERT IGNORE INTO `sys_menu` VALUES
+(2099010100000000020, '知识片段', 2000209300188356609, 8, 'fragment', 'knowledge/fragment/index', NULL, 1, 0, 'C', '0', '0', 'system:fragment:list', 'ant-design:file-text-outlined', 103, 1, '2026-07-24 00:00:00', NULL, NULL, '知识片段菜单'),
+(2099010100000000021, '知识片段查询', 2099010100000000020, 1, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:fragment:query', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000022, '知识片段新增', 2099010100000000020, 2, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:fragment:add', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000023, '知识片段修改', 2099010100000000020, 3, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:fragment:edit', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000024, '知识片段删除', 2099010100000000020, 4, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:fragment:remove', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, ''),
+(2099010100000000025, '知识片段导出', 2099010100000000020, 5, '#', '', NULL, 1, 0, 'F', '0', '0', 'system:fragment:export', '#', 103, 1, '2026-07-24 00:00:00', NULL, NULL, '');
+
+-- ============================================================
+-- 5. 新建 普通用户 角色（租户 000000，data_scope=5 仅本人）
+-- ============================================================
+INSERT IGNORE INTO `sys_role` VALUES
+(2099010100000000030, '000000', '普通用户', 'user', 2, '5', 1, 1, '0', '0', 103, 1, '2026-07-24 00:00:00', NULL, NULL, '注册用户默认角色');
+
+-- ============================================================
+-- 6. 角色-菜单关联：普通用户 拥有用户端 AI 对话所需权限
+--    会话管理(001-006) + 聊天消息(2000210914680823809 及 810-814)
+--    + 知识管理(2006681261898813441 及 442-446)
+--    + 知识附件(010-015) + 知识片段(020-025)
+-- ============================================================
+INSERT IGNORE INTO `sys_role_menu` (`role_id`, `menu_id`) VALUES
+-- 会话管理
+(2099010100000000030, 2099010100000000001),
+(2099010100000000030, 2099010100000000002),
+(2099010100000000030, 2099010100000000003),
+(2099010100000000030, 2099010100000000004),
+(2099010100000000030, 2099010100000000005),
+(2099010100000000030, 2099010100000000006),
+-- 聊天消息
+(2099010100000000030, 2000210914680823809),
+(2099010100000000030, 2000210914680823810),
+(2099010100000000030, 2000210914680823811),
+(2099010100000000030, 2000210914680823812),
+(2099010100000000030, 2000210914680823813),
+(2099010100000000030, 2000210914680823814),
+-- 知识管理
+(2099010100000000030, 2006681261898813441),
+(2099010100000000030, 2006681261898813442),
+(2099010100000000030, 2006681261898813443),
+(2099010100000000030, 2006681261898813444),
+(2099010100000000030, 2006681261898813445),
+(2099010100000000030, 2006681261898813446),
+-- 知识附件
+(2099010100000000030, 2099010100000000010),
+(2099010100000000030, 2099010100000000011),
+(2099010100000000030, 2099010100000000012),
+(2099010100000000030, 2099010100000000013),
+(2099010100000000030, 2099010100000000014),
+(2099010100000000030, 2099010100000000015),
+-- 知识片段
+(2099010100000000030, 2099010100000000020),
+(2099010100000000030, 2099010100000000021),
+(2099010100000000030, 2099010100000000022),
+(2099010100000000030, 2099010100000000023),
+(2099010100000000030, 2099010100000000024),
+(2099010100000000030, 2099010100000000025);
+
+-- ============================================================
+-- 7. 注册默认角色配置项 sys.register.defaultRoleId
+--    后端 SysRegisterService 注册成功后读取此配置为新用户绑定角色；
+--    值为空字符串时不绑定（保留旧行为）。
+-- ============================================================
+INSERT IGNORE INTO `sys_config` VALUES
+(2099010100000000031, '000000', '注册-默认角色ID', 'sys.register.defaultRoleId', '2099010100000000030', 'Y', 103, 1, '2026-07-24 00:00:00', NULL, NULL, '新注册用户绑定的默认角色ID，留空则不绑定');
+
+-- ============================================================
+-- 8. 前置条件（运营项，默认不执行）：开启用户注册
+--    sys.account.registerUser 默认 false，后端 AuthController.register
+--    会据此返回「当前系统没有开启注册功能」。若要开放注册，取消注释执行。
+-- ============================================================
+-- UPDATE `sys_config` SET `config_value` = 'true'
+-- WHERE `config_key` = 'sys.account.registerUser' AND `tenant_id` = '000000';
--- a/docs/script/sql/update/2026-07-29-sys-config-node-template-all.sql
+++ b/docs/script/sql/update/2026-07-29-sys-config-node-template-all.sql
@@ -0,0 +1,39 @@
+-- 一次性补全工作流节点消息模板配置 (NodeMessageTemplateEnum 全部 8 个键)
+-- 背景：节点执行时 WorkflowMessageUtil.getNodeMessageTemplate 从 sys_config 读取展示模板,
+--       历史库中这批配置缺失, 导致运行工作流抛「请先配置该节点的响应模板」。
+--       其中前 7 个见 2026-07-21-sys-config-node-template.sql,
+--       Google Search 为此前从未入库的节点模板。
+-- 说明：代码已增加内置默认模板兜底, 本脚本为可选, 执行后模板可在 系统管理-配置管理 中自定义。
+-- 幂等：按 config_key + tenant_id 判重, 可重复执行。
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027192921483309058, '000000', 'HTTP请求节点响应模板', 'node.httpRequest.template', '✅ HTTP请求节点：结束响应 - ', 'Y', 103, 1, '2026-02-27 09:23:51', 1, '2026-02-27 09:31:41', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.httpRequest.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027193296990957569, '000000', '文生图节点响应模板', 'node.image.template', '🎨 文生图节点：结束响应 - 图片URL: ', 'Y', 103, 1, '2026-02-27 09:25:20', 1, '2026-02-27 09:31:52', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.image.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027193820393959425, '000000', '发送邮箱节点响应模板', 'node.mailsend.template', '📧 发送邮箱节点：结束响应 - ', 'Y', 103, 1, '2026-02-27 09:27:25', 1, '2026-02-27 09:32:05', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.mailsend.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027194134438277122, '000000', '结束节点响应模板', 'node.end.template', '🔚 流程已执行完毕，如果您有其他需求，请随时重新发起请求。', 'Y', 103, 1, '2026-02-27 09:28:40', 1, '2026-02-27 09:32:53', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.end.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027208880369647617, '000000', '条件分支节点响应模板', 'node.switch.template', '🔀 条件分支节点：触发 -> 跳转到节点 ', 'Y', 103, 1, '2026-02-27 10:27:15', 1, '2026-02-27 10:35:54', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.switch.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027213914603995137, '000000', '大模型回答节点响应模板', 'node.llmAnswer.template', '🤖 LLM 节点 生成回答：', 'Y', 103, 1, '2026-02-27 10:47:16', 1, '2026-02-27 10:52:40', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.llmAnswer.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2027217577397391361, '000000', '工作流异常响应模板', 'node.exception.template', '🛑 工作流发生异常：', 'N', 103, 1, '2026-02-27 11:01:49', 1, '2026-02-27 11:02:01', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.exception.template' AND `tenant_id` = '000000');
+
+INSERT INTO `sys_config` (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`, `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`, `update_time`, `remark`)
+SELECT 2084157200000000003, '000000', '网络搜索节点响应模板', 'node.googleSearch.template', '🔍 网络搜索节点处理完成：', 'Y', 103, 1, '2026-07-29 19:40:00', 1, '2026-07-29 19:40:00', NULL
+FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM `sys_config` WHERE `config_key` = 'node.googleSearch.template' AND `tenant_id` = '000000');
--- a/docs/script/sql/update/2026-07-29-zhipu-web-search-node.sql
+++ b/docs/script/sql/update/2026-07-29-zhipu-web-search-node.sql
@@ -0,0 +1,66 @@
+-- 智谱 Web Search 工作流扩展节点
+-- 内部组件名继续使用 Google，以兼容现有前端组件和已保存流程。
+
+UPDATE `t_workflow_component`
+SET `title` = '网络搜索',
+    `remark` = '调用智谱 Web Search 检索互联网信息',
+    `display_order` = 40,
+    `is_enable` = 1,
+    `is_deleted` = 0,
+    `update_time` = NOW()
+WHERE `name` = 'Google'
+  AND `tenant_id` = '000000';
+
+INSERT INTO `t_workflow_component`
+    (`uuid`, `name`, `title`, `remark`, `display_order`, `is_enable`,
+     `create_time`, `update_time`, `is_deleted`, `tenant_id`)
+SELECT
+    'a7f8c2d44e5b4c83a9d6f103c2b47e18',
+    'Google',
+    '网络搜索',
+    '调用智谱 Web Search 检索互联网信息',
+    40,
+    1,
+    NOW(),
+    NOW(),
+    0,
+    '000000'
+FROM DUAL
+WHERE NOT EXISTS (
+    SELECT 1
+    FROM `t_workflow_component`
+    WHERE `name` = 'Google'
+      AND `tenant_id` = '000000'
+);
+
+UPDATE `sys_config`
+SET `config_name` = '网络搜索节点响应模板',
+    `config_value` = '🔍 网络搜索节点处理完成：',
+    `update_time` = NOW()
+WHERE `config_key` = 'node.googleSearch.template'
+  AND `tenant_id` = '000000';
+
+INSERT INTO `sys_config`
+    (`config_id`, `tenant_id`, `config_name`, `config_key`, `config_value`,
+     `config_type`, `create_dept`, `create_by`, `create_time`, `update_by`,
+     `update_time`, `remark`)
+SELECT
+    2084157200000000003,
+    '000000',
+    '网络搜索节点响应模板',
+    'node.googleSearch.template',
+    '🔍 网络搜索节点处理完成：',
+    'Y',
+    103,
+    1,
+    NOW(),
+    1,
+    NOW(),
+    '智谱 Web Search 工作流扩展节点'
+FROM DUAL
+WHERE NOT EXISTS (
+    SELECT 1
+    FROM `sys_config`
+    WHERE `config_key` = 'node.googleSearch.template'
+      AND `tenant_id` = '000000'
+);
--- a/docs/script/sql/update/update-0615-trace.sql
+++ b/docs/script/sql/update/update-0615-trace.sql
@@ -0,0 +1,128 @@
+-- 链路追踪运行记录表
+CREATE TABLE IF NOT EXISTS `trace_run` (
+  `id` bigint NOT NULL COMMENT '主键',
+  `trace_id` varchar(64) NOT NULL COMMENT '链路ID',
+  `trace_name` varchar(128) NOT NULL COMMENT '链路名称',
+  `business_type` varchar(64) NOT NULL COMMENT '业务类型',
+  `business_id` varchar(128) DEFAULT NULL COMMENT '业务ID',
+  `user_id` bigint DEFAULT NULL COMMENT '用户ID',
+  `tenant_id` varchar(20) DEFAULT '000000' COMMENT '租户编号',
+  `status` varchar(32) NOT NULL COMMENT '状态',
+  `start_time` datetime NOT NULL COMMENT '开始时间',
+  `end_time` datetime DEFAULT NULL COMMENT '结束时间',
+  `duration_ms` bigint DEFAULT NULL COMMENT '耗时毫秒',
+  `error_message` varchar(1000) DEFAULT NULL COMMENT '错误摘要',
+  `metadata` text DEFAULT NULL COMMENT '元数据JSON',
+  `create_dept` bigint DEFAULT NULL COMMENT '创建部门',
+  `create_by` bigint DEFAULT NULL COMMENT '创建者',
+  `create_time` datetime DEFAULT NULL COMMENT '创建时间',
+  `update_by` bigint DEFAULT NULL COMMENT '更新者',
+  `update_time` datetime DEFAULT NULL COMMENT '更新时间',
+  `del_flag` char(1) DEFAULT '0' COMMENT '删除标志（0代表存在 2代表删除）',
+  PRIMARY KEY (`id`) USING BTREE,
+  UNIQUE KEY `uk_trace_run_trace_id` (`trace_id`) USING BTREE,
+  KEY `idx_trace_run_business` (`business_type`, `business_id`) USING BTREE,
+  KEY `idx_trace_run_status_time` (`status`, `start_time`) USING BTREE,
+  KEY `idx_trace_run_tenant_time` (`tenant_id`, `start_time`) USING BTREE
+) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci COMMENT='链路追踪运行记录表' ROW_FORMAT=DYNAMIC;
+
+-- 链路追踪节点记录表
+CREATE TABLE IF NOT EXISTS `trace_node` (
+  `id` bigint NOT NULL COMMENT '主键',
+  `trace_id` varchar(64) NOT NULL COMMENT '链路ID',
+  `node_id` varchar(64) NOT NULL COMMENT '节点ID',
+  `tenant_id` varchar(20) DEFAULT '000000' COMMENT '租户编号',
+  `parent_node_id` varchar(64) DEFAULT NULL COMMENT '父节点ID',
+  `node_name` varchar(128) NOT NULL COMMENT '节点名称',
+  `node_type` varchar(64) NOT NULL COMMENT '节点类型',
+  `depth` int DEFAULT 0 COMMENT '节点深度',
+  `sort_order` int DEFAULT 0 COMMENT '排序',
+  `class_name` varchar(255) DEFAULT NULL COMMENT '类名',
+  `method_name` varchar(128) DEFAULT NULL COMMENT '方法名',
+  `status` varchar(32) NOT NULL COMMENT '状态',
+  `start_time` datetime NOT NULL COMMENT '开始时间',
+  `end_time` datetime DEFAULT NULL COMMENT '结束时间',
+  `duration_ms` bigint DEFAULT NULL COMMENT '耗时毫秒',
+  `error_message` varchar(1000) DEFAULT NULL COMMENT '错误摘要',
+  `input_payload` text DEFAULT NULL COMMENT '输入JSON',
+  `output_payload` text DEFAULT NULL COMMENT '输出JSON',
+  `metadata` text DEFAULT NULL COMMENT '元数据JSON',
+  `create_dept` bigint DEFAULT NULL COMMENT '创建部门',
+  `create_by` bigint DEFAULT NULL COMMENT '创建者',
+  `create_time` datetime DEFAULT NULL COMMENT '创建时间',
+  `update_by` bigint DEFAULT NULL COMMENT '更新者',
+  `update_time` datetime DEFAULT NULL COMMENT '更新时间',
+  `del_flag` char(1) DEFAULT '0' COMMENT '删除标志（0代表存在 2代表删除）',
+  PRIMARY KEY (`id`) USING BTREE,
+  KEY `idx_trace_node_trace_id` (`trace_id`) USING BTREE,
+  KEY `idx_trace_node_parent` (`trace_id`, `parent_node_id`) USING BTREE,
+  KEY `idx_trace_node_time` (`trace_id`, `start_time`) USING BTREE,
+  KEY `idx_trace_node_tenant_time` (`tenant_id`, `start_time`) USING BTREE,
+  KEY `idx_trace_node_type_status` (`node_type`, `status`) USING BTREE
+) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci COMMENT='链路追踪节点记录表' ROW_FORMAT=DYNAMIC;
+
+-- 兼容已存在的旧 trace 表：CREATE TABLE IF NOT EXISTS 不会给旧表补新字段
+SET @trace_run_add_tenant_sql = (
+  SELECT IF(COUNT(*) = 0,
+    'ALTER TABLE `trace_run` ADD COLUMN `tenant_id` varchar(20) DEFAULT ''000000'' COMMENT ''租户编号'' AFTER `user_id`',
+    'SELECT 1'
+  )
+  FROM information_schema.COLUMNS
+  WHERE TABLE_SCHEMA = DATABASE()
+    AND TABLE_NAME = 'trace_run'
+    AND COLUMN_NAME = 'tenant_id'
+);
+PREPARE trace_run_add_tenant_stmt FROM @trace_run_add_tenant_sql;
+EXECUTE trace_run_add_tenant_stmt;
+DEALLOCATE PREPARE trace_run_add_tenant_stmt;
+
+SET @trace_run_add_tenant_idx_sql = (
+  SELECT IF(COUNT(*) = 0,
+    'ALTER TABLE `trace_run` ADD INDEX `idx_trace_run_tenant_time` (`tenant_id`, `start_time`) USING BTREE',
+    'SELECT 1'
+  )
+  FROM information_schema.STATISTICS
+  WHERE TABLE_SCHEMA = DATABASE()
+    AND TABLE_NAME = 'trace_run'
+    AND INDEX_NAME = 'idx_trace_run_tenant_time'
+);
+PREPARE trace_run_add_tenant_idx_stmt FROM @trace_run_add_tenant_idx_sql;
+EXECUTE trace_run_add_tenant_idx_stmt;
+DEALLOCATE PREPARE trace_run_add_tenant_idx_stmt;
+
+SET @trace_node_add_tenant_sql = (
+  SELECT IF(COUNT(*) = 0,
+    'ALTER TABLE `trace_node` ADD COLUMN `tenant_id` varchar(20) DEFAULT ''000000'' COMMENT ''租户编号'' AFTER `node_id`',
+    'SELECT 1'
+  )
+  FROM information_schema.COLUMNS
+  WHERE TABLE_SCHEMA = DATABASE()
+    AND TABLE_NAME = 'trace_node'
+    AND COLUMN_NAME = 'tenant_id'
+);
+PREPARE trace_node_add_tenant_stmt FROM @trace_node_add_tenant_sql;
+EXECUTE trace_node_add_tenant_stmt;
+DEALLOCATE PREPARE trace_node_add_tenant_stmt;
+
+SET @trace_node_add_tenant_idx_sql = (
+  SELECT IF(COUNT(*) = 0,
+    'ALTER TABLE `trace_node` ADD INDEX `idx_trace_node_tenant_time` (`tenant_id`, `start_time`) USING BTREE',
+    'SELECT 1'
+  )
+  FROM information_schema.STATISTICS
+  WHERE TABLE_SCHEMA = DATABASE()
+    AND TABLE_NAME = 'trace_node'
+    AND INDEX_NAME = 'idx_trace_node_tenant_time'
+);
+PREPARE trace_node_add_tenant_idx_stmt FROM @trace_node_add_tenant_idx_sql;
+EXECUTE trace_node_add_tenant_idx_stmt;
+DEALLOCATE PREPARE trace_node_add_tenant_idx_stmt;
+
+-- 链路追踪监控菜单 & 按钮权限
+INSERT INTO `sys_menu`
+(`menu_id`, `menu_name`, `parent_id`, `order_num`, `path`, `component`, `query_param`, `is_frame`, `is_cache`, `menu_type`, `visible`, `status`, `perms`, `icon`, `create_dept`, `create_by`, `create_time`, `remark`)
+SELECT (SELECT COALESCE(MAX(`menu_id`), 0) + 1 FROM (SELECT `menu_id` FROM `sys_menu`) t), '链路追踪', 2, 7, 'trace', 'monitor/trace/index', '', 1, 0, 'C', '0', '0', 'monitor:trace:list', 'tabler:route', 103, 1, NOW(), '链路追踪监控菜单';
+
+INSERT INTO `sys_menu`
+(`menu_id`, `menu_name`, `parent_id`, `order_num`, `path`, `component`, `query_param`, `is_frame`, `is_cache`, `menu_type`, `visible`, `status`, `perms`, `icon`, `create_dept`, `create_by`, `create_time`, `remark`)
+SELECT (SELECT COALESCE(MAX(`menu_id`), 0) + 1 FROM (SELECT `menu_id` FROM `sys_menu`) t), '链路追踪查询', (SELECT `menu_id` FROM `sys_menu` WHERE `perms` = 'monitor:trace:list' AND `menu_type` = 'C' LIMIT 1), 1, '#', '', '', 1, 0, 'F', '0', '0', 'monitor:trace:query', '#', 103, 1, NOW(), '';
--- a/pom.xml
+++ b/pom.xml
@@ -43,8 +43,6 @@
        <aws.sdk.version>2.28.22</aws.sdk.version>
        <!-- SMS 配置 -->
        <sms4j.version>3.3.5</sms4j.version>
-        <!-- 限制框架中的fastjson版本 -->
-        <fastjson.version>1.2.83</fastjson.version>
        <!-- 面向运行时的D-ORM依赖 -->
        <anyline.version>8.7.2-20250603</anyline.version>
        <!-- 工作流配置 -->
@@ -63,6 +61,8 @@
        <weaviate.version>1.19.6</weaviate.version>
        <dify.version>1.2.7</dify.version>
        <coze.version>0.4.2</coze.version>
+        <!-- 智谱官方 Java SDK -->
+        <zai-sdk.version>0.3.5</zai-sdk.version>

        <!-- gRPC 版本 - 解决 Milvus SDK 依赖冲突 -->
        <grpc.version>1.62.2</grpc.version>
@@ -70,6 +70,7 @@
        <commons-compress.version>1.27.1</commons-compress.version>

        <avatar-generator.version>1.1.0</avatar-generator.version>
+        <javassist.version>3.30.2-GA</javassist.version>
        <jsoup.version>1.21.2</jsoup.version>
        <knife4j.version>4.4.0</knife4j.version>
        <swagger-annotations.version>2.2.8</swagger-annotations.version>
@@ -83,7 +84,7 @@
        <maven-surefire-plugin.version>3.5.3</maven-surefire-plugin.version>
        <flatten-maven-plugin.version>1.3.0</flatten-maven-plugin.version>
        <!-- 打包默认跳过测试 -->
-        <skipTests>true</skipTests>
+        <skipTests>false</skipTests>
    </properties>

    <profiles>
@@ -346,6 +347,12 @@
                <groupId>me.zhyd.oauth</groupId>
                <artifactId>JustAuth</artifactId>
                <version>${justauth.version}</version>
+                <exclusions>
+                    <exclusion>
+                        <groupId>com.alibaba</groupId>
+                        <artifactId>fastjson</artifactId>
+                    </exclusion>
+                </exclusions>
            </dependency>

            <!-- 离线IP地址定位库 ip2region -->
@@ -355,12 +362,6 @@
                <version>${ip2region.version}</version>
            </dependency>

-            <dependency>
-                <groupId>com.alibaba</groupId>
-                <artifactId>fastjson</artifactId>
-                <version>${fastjson.version}</version>
-            </dependency>
-
            <dependency>
                <groupId>org.ruoyi</groupId>
                <artifactId>ruoyi-system</artifactId>
@@ -503,20 +504,8 @@
        <resources>
            <resource>
                <directory>src/main/resources</directory>
-                <!-- 关闭过滤 -->
                <filtering>false</filtering>
            </resource>
-            <resource>
-                <directory>src/main/resources</directory>
-                <!-- 引入所有 匹配文件进行过滤 -->
-                <includes>
-                    <include>application*</include>
-                    <include>bootstrap*</include>
-                    <include>banner*</include>
-                </includes>
-                <!-- 启用过滤 即该资源中的变量将会被过滤器中的值替换 -->
-                <filtering>true</filtering>
-            </resource>
        </resources>
    </build>

--- a/ruoyi-admin/src/main/resources/application-dev.yml
+++ b/ruoyi-admin/src/main/resources/application-dev.yml
@@ -8,8 +8,8 @@ spring.boot.admin.client:
    metadata:
      username: ${spring.boot.admin.client.username}
      userpassword: ${spring.boot.admin.client.password}
-  username: @monitor.username@
-  password: @monitor.password@
+  username: ${MONITOR_USERNAME:ruoyi}
+  password: ${MONITOR_PASSWORD:123456}

 --- # mcp配置信息
 mcp:
@@ -27,12 +27,12 @@ snail-job:
  enabled: false
  # 需要在 SnailJob 后台组管理创建对应名称的组,然后创建任务的时候选择对应的组,才能正确分派任务
  group: "ruoyi_group"
-  # SnailJob 接入验证令牌 详见 script/sql/ry_job.sql `sj_group_config` 表
+  # SnailJob 接入验证令牌 详见 docs/script/sql/ruoyi-ai-v3_mysql8.sql `sj_group_config` 表
  token: "SJ_cKqBTPzCsWA3VyuCfFoccmuIEGXjr5KT"
  server:
    host: 127.0.0.1
    port: 17888
-  # 命名空间UUID 详见 script/sql/ry_job.sql `sj_namespace`表`unique_id`字段
+  # 命名空间UUID 详见 docs/script/sql/ruoyi-ai-v3_mysql8.sql `sj_namespace`表`unique_id`字段
  namespace: ${spring.profiles.active}
  # 随主应用端口漂移
  port: 2${server.port}
--- a/ruoyi-admin/src/main/resources/application-prod.yml
+++ b/ruoyi-admin/src/main/resources/application-prod.yml
@@ -9,8 +9,8 @@ spring.boot.admin.client:
    metadata:
      username: ${spring.boot.admin.client.username}
      userpassword: ${spring.boot.admin.client.password}
-  username: @monitor.username@
-  password: @monitor.password@
+  username: ${MONITOR_USERNAME:ruoyi}
+  password: ${MONITOR_PASSWORD:123456}

 --- # mcp配置信息
 mcp:
@@ -28,12 +28,12 @@ snail-job:
  enabled: false
  # 需要在 SnailJob 后台组管理创建对应名称的组,然后创建任务的时候选择对应的组,才能正确分派任务
  group: "ruoyi_group"
-  # SnailJob 接入验证令牌 详见 script/sql/ry_job.sql `sj_group_config` 表
+  # SnailJob 接入验证令牌 详见 docs/script/sql/ruoyi-ai-v3_mysql8.sql `sj_group_config` 表
  token: "SJ_cKqBTPzCsWA3VyuCfFoccmuIEGXjr5KT"
  server:
    host: 127.0.0.1
    port: 17888
-  # 命名空间UUID 详见 script/sql/ry_job.sql `sj_namespace`表`unique_id`字段
+  # 命名空间UUID 详见 docs/script/sql/ruoyi-ai-v3_mysql8.sql `sj_namespace`表`unique_id`字段
  namespace: ${spring.profiles.active}
  # 随主应用端口漂移
  port: 2${server.port}
--- a/ruoyi-admin/src/main/resources/application.yml
+++ b/ruoyi-admin/src/main/resources/application.yml
@@ -20,6 +20,10 @@ server:
      # 阻塞任务线程池, 当执行类似servlet请求阻塞操作, undertow会从这个线程池中取得线程,它的值设置取决于系统的负载
      worker: 256

+--- # 小程序对话 WebSocket 兜底默认模型（前端未传 model 且无智能体绑定时使用）
+chat:
+  default-model: deepseek-v4-flash
+
 captcha:
  # 是否启用验证码校验
  enable: false
@@ -35,7 +39,7 @@ captcha:
 # 日志配置
 logging:
  level:
-    org.ruoyi: @logging.level@
+    org.ruoyi: ${LOGGING_LEVEL_ORG_RUOYI:info}
    org.springframework: warn
    org.mybatis.spring.mapper: error
    org.apache.fury: warn
@@ -75,7 +79,7 @@ spring:
    # 国际化资源文件路径
    basename: i18n/messages
  profiles:
-    active: @profiles.active@
+    active: ${SPRING_PROFILES_ACTIVE:dev}
  # 文件上传
  servlet:
    multipart:
@@ -125,6 +129,7 @@ security:
    - /*/api-docs/**
    - /warm-flow-ui/config
    - /workflow/run
+    - /coding/**
 # 多租户配置
 tenant:
  # 是否开启
@@ -141,6 +146,9 @@ tenant:
    - sys_client
    - sys_oss_config
    - flow_spel
+    # 链路追踪监控表：运维需跨租户全局查看，且 trace_node 在异步线程写入、租户上下文不传播，故排除租户过滤
+    - trace_run
+    - trace_node

 # MyBatisPlus配置
 # https://baomidou.com/config/
@@ -227,6 +235,15 @@ xss:
  excludeUrls:
    - /system/notice

+--- # 链路追踪配置
+trace:
+  # 是否启用链路追踪，默认 true
+  # 关闭后所有埋点代码会直接透传业务逻辑，不写库、不创建上下文，零性能开销
+  enabled: true
+  payload:
+    # 错误信息最大字符长度（格式: "异常类名: 异常消息"），超过部分会被截断丢弃
+    max-error-length: 1000
+
 --- # 分布式锁 lock4j 全局配置
 lock4j:
  # 获取分布式锁超时时间，默认为 3000 毫秒
@@ -296,11 +313,12 @@ warm-flow:
 vector-store:
  # 向量存储类型 可选(weaviate/milvus/qdrant)
  # 如需修改向量库类型，请修改此配置值!
-  type: milvus
+  # 注意：需与 docker-compose 实际部署的向量库保持一致（当前 compose 内置 weaviate，映射端口 28080）
+  type: weaviate
  # Weaviate配置
  weaviate:
    protocol: http
-    host: 127.0.0.1:6038
+    host: 127.0.0.1:28080
    classname: LocalKnowledge
  # Milvus配置
  milvus:
@@ -314,6 +332,16 @@ vector-store:
    api-key:
    use-tls: false

+# 流程编排扩展节点
+workflow:
+  web-search:
+    zhipu:
+      # 推荐通过环境变量注入；为空时回退到模型管理中的 zhipu 厂商密钥
+      api-key: ${ZAI_API_KEY:}
+      base-url: ${ZHIPU_WEB_SEARCH_BASE_URL:https://open.bigmodel.cn/api/paas/v4/}
+      connect-timeout: ${ZHIPU_WEB_SEARCH_CONNECT_TIMEOUT:10}
+      read-timeout: ${ZHIPU_WEB_SEARCH_READ_TIMEOUT:30}
+
 # 短剧成片合成
 short-drama:
  composition:
@@ -335,6 +363,7 @@ short-drama:
    probe-timeout: ${SHORT_DRAMA_COMPOSITION_PROBE_TIMEOUT:30s}
    process-timeout: ${SHORT_DRAMA_COMPOSITION_PROCESS_TIMEOUT:30m}
    job-stale-after: ${SHORT_DRAMA_COMPOSITION_JOB_STALE_AFTER:45m}
+    watermark-font-file: ${SHORT_DRAMA_COMPOSITION_WATERMARK_FONT_FILE:}
    worker-core-size: ${SHORT_DRAMA_COMPOSITION_WORKER_CORE_SIZE:1}
    worker-max-size: ${SHORT_DRAMA_COMPOSITION_WORKER_MAX_SIZE:2}
    worker-queue-capacity: ${SHORT_DRAMA_COMPOSITION_WORKER_QUEUE_CAPACITY:8}
--- a/ruoyi-common/pom.xml
+++ b/ruoyi-common/pom.xml
@@ -35,6 +35,7 @@
        <module>ruoyi-common-tenant</module>
        <module>ruoyi-common-websocket</module>
        <module>ruoyi-common-sse</module>
+        <module>ruoyi-common-trace</module>
    </modules>

    <artifactId>ruoyi-common</artifactId>
--- a/ruoyi-common/ruoyi-common-bom/pom.xml
+++ b/ruoyi-common/ruoyi-common-bom/pom.xml
@@ -186,6 +186,13 @@
                <version>${revision}</version>
            </dependency>

+            <!-- 链路追踪模块 -->
+            <dependency>
+                <groupId>org.ruoyi</groupId>
+                <artifactId>ruoyi-common-trace</artifactId>
+                <version>${revision}</version>
+            </dependency>
+
        </dependencies>
    </dependencyManagement>

--- a/ruoyi-common/ruoyi-common-chat/pom.xml
+++ b/ruoyi-common/ruoyi-common-chat/pom.xml
@@ -38,8 +38,8 @@
        </dependency>

        <dependency>
-            <groupId>com.alibaba</groupId>
-            <artifactId>fastjson</artifactId>
+            <groupId>com.fasterxml.jackson.core</groupId>
+            <artifactId>jackson-databind</artifactId>
        </dependency>

        <dependency>
--- a/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/domain/bo/chat/ChatModelBo.java
+++ b/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/domain/bo/chat/ChatModelBo.java
@@ -1,10 +1,12 @@
 package org.ruoyi.common.chat.domain.bo.chat;

 import io.github.linpeilie.annotations.AutoMapper;
+import jakarta.validation.constraints.NotBlank;
 import jakarta.validation.constraints.NotNull;
 import lombok.Data;
 import lombok.EqualsAndHashCode;
 import org.ruoyi.common.chat.entity.chat.ChatModel;
+import org.ruoyi.common.core.validate.AddGroup;
 import org.ruoyi.common.core.validate.EditGroup;
 import org.ruoyi.common.mybatis.core.domain.BaseEntity;

@@ -28,16 +30,19 @@ public class ChatModelBo extends BaseEntity {
    /**
     * 模型分类
     */
+    @NotBlank(message = "模型分类不能为空", groups = { AddGroup.class, EditGroup.class })
    private String category;

    /**
     * 模型名称
     */
+    @NotBlank(message = "模型名称不能为空", groups = { AddGroup.class, EditGroup.class })
    private String modelName;

    /**
     * 模型供应商
     */
+    @NotBlank(message = "模型供应商不能为空", groups = { AddGroup.class, EditGroup.class })
    private String providerCode;

    /**
--- a/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/domain/dto/request/ChatRequest.java
+++ b/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/domain/dto/request/ChatRequest.java
@@ -1,6 +1,5 @@
 package org.ruoyi.common.chat.domain.dto.request;

-import com.alibaba.fastjson.annotation.JSONField;
 import com.fasterxml.jackson.databind.annotation.JsonSerialize;
 import com.fasterxml.jackson.databind.ser.std.ToStringSerializer;
 import dev.langchain4j.data.message.ChatMessage;
@@ -31,7 +30,6 @@ public class ChatRequest {
     * 智能体ID。传入时后端按智能体配置解析模型/工具/技能/知识库/提示词/是否深度思考。
     */
    @JsonSerialize(using = ToStringSerializer.class)
-    @JSONField(serializeUsing = String.class)
    private Long agentId;

    /**
@@ -54,7 +52,6 @@ public class ChatRequest {
     * 会话id
     */
    @JsonSerialize(using = ToStringSerializer.class)
-    @JSONField(serializeUsing = String.class)
    private Long sessionId;

    /**
@@ -71,7 +68,6 @@ public class ChatRequest {
     * 对话id(每个聊天窗口都不一样)
     */
    @JsonSerialize(using = ToStringSerializer.class)
-    @JSONField(serializeUsing = String.class)
    private Long uuid;

    /**
--- a/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/entity/audio/AudioContext.java
+++ b/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/entity/audio/AudioContext.java
@@ -26,4 +26,19 @@ public class AudioContext {
    private Double speed;

    private String instructions;
+
+    /** Atlas seed-audio 参考资源：[{speaker, audioUrl, audioData, imageData}]，speaker 为音色名 */
+    private java.util.List<java.util.Map<String, String>> references;
+
+    /** Atlas seed-audio 采样率 */
+    private Integer sampleRate;
+
+    /** Atlas seed-audio 音调调整 (-12~12) */
+    private Integer pitchRate;
+
+    /** Atlas seed-audio 语速调整 (-50~100) */
+    private Integer speechRate;
+
+    /** Atlas seed-audio 响度调整 (-50~100) */
+    private Integer loudnessRate;
 }
--- a/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/entity/media/MediaGenerationResponse.java
+++ b/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/entity/media/MediaGenerationResponse.java
@@ -25,4 +25,7 @@ public class MediaGenerationResponse {
    private String status;

    private String rawResponse;
+
+    /** 末帧图片 URL（Atlas return_last_frame=true 时返回，用于下一镜首帧承接） */
+    private String lastFrameUrl;
 }
--- a/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/entity/video/VideoContext.java
+++ b/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/entity/video/VideoContext.java
@@ -31,5 +31,17 @@ public class VideoContext {
    /** 多参考图 URL（多参考图生视频模式，配合 @imageN prompt 使用） */
    private java.util.List<String> referenceImages;

+    /** 参考音频 URL 列表（对白口型对齐模式） */
+    private java.util.List<String> referenceAudios;
+
+    /** 是否让模型生成同步音频（环境音/动效） */
+    private Boolean generateAudio;
+
+    /** 是否要求返回末帧，用于下一镜首帧承接 */
+    private Boolean returnLastFrame;
+
+    /** 上一镜末帧 URL（同场景连续镜头首帧承接用，作为额外参考图传入） */
+    private String lastFrameUrl;
+
    private String videoId;
 }
--- a/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/enums/ErrorEnum.java
+++ b/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/enums/ErrorEnum.java
@@ -54,7 +54,6 @@ public enum ErrorEnum {
    A_WF_RUNTIME_NOT_FOUND("A00045", "工作流运行时数据找不到"),
    A_SEARCH_QUERY_IS_EMPTY("A00046", "搜索内容不能为空"),
    A_WF_COMPONENT_NOT_FOUND("A00047", "工作流基础组件找不到"),
-    A_WF_RESUME_FAIL("A00048", "工作流恢复执行时失败"),
    A_MAIL_SENDER_EMPTY("A00049", "邮件发送人不能为空"),
    A_MAIL_SENDER_CONFIG_ERROR("A00050", "邮件发送人配置错误"),
    A_MAIL_RECEIVER_EMPTY("A00051", "邮件接收人不能为空"),
--- a/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/service/workFlow/IWorkFlowStarterService.java
+++ b/ruoyi-common/ruoyi-common-chat/src/main/java/org/ruoyi/common/chat/service/workFlow/IWorkFlowStarterService.java
@@ -22,12 +22,4 @@ public interface IWorkFlowStarterService {
     * @return 流式输出结果
     */
    SseEmitter streaming(User user, String workflowUuid, List<ObjectNode> userInputs, Long sessionId);
-
-    /**
-     * 恢复工作流
-      * @param runtimeUuid 运行时UUID
-     * @param userInput 用户输入
-     * @param sseEmitter SSE连接对象
-     */
-    void resumeFlow(String runtimeUuid, String userInput, SseEmitter sseEmitter);
 }
--- a/ruoyi-common/ruoyi-common-social/src/main/java/me/zhyd/oauth/request/AbstractAuthWeChatEnterpriseRequest.java
+++ b/ruoyi-common/ruoyi-common-social/src/main/java/me/zhyd/oauth/request/AbstractAuthWeChatEnterpriseRequest.java
@@ -1,6 +1,7 @@
 package me.zhyd.oauth.request;

-import com.alibaba.fastjson.JSONObject;
+import com.fasterxml.jackson.databind.JsonNode;
+import com.fasterxml.jackson.databind.ObjectMapper;
 import me.zhyd.oauth.cache.AuthStateCache;
 import me.zhyd.oauth.config.AuthConfig;
 import me.zhyd.oauth.config.AuthSource;
@@ -37,11 +38,11 @@ public abstract class AbstractAuthWeChatEnterpriseRequest extends AuthDefaultReq
    public AuthToken getAccessToken(AuthCallback authCallback) {
        String response = doGetAuthorizationCode(accessTokenUrl(null));

-        JSONObject object = this.checkResponse(response);
+        JsonNode object = this.checkResponse(response);

        return AuthToken.builder()
-            .accessToken(object.getString("access_token"))
-            .expireIn(object.getIntValue("expires_in"))
+            .accessToken(object.get("access_token").asText())
+            .expireIn(object.get("expires_in").asInt())
            .code(authCallback.getCode())
            .build();
    }
@@ -49,26 +50,25 @@ public abstract class AbstractAuthWeChatEnterpriseRequest extends AuthDefaultReq
    @Override
    public AuthUser getUserInfo(AuthToken authToken) {
        String response = doGetUserInfo(authToken);
-        JSONObject object = this.checkResponse(response);
+        JsonNode object = this.checkResponse(response);

        // 返回 OpenId 或其他，均代表非当前企业用户，不支持
        // https://github.com/justauth/JustAuth/issues/227 修复bug
-        if (!object.containsKey("userid")) {
+        if (!object.has("userid")) {
            throw new AuthException(AuthResponseStatus.UNIDENTIFIED_PLATFORM, source);
        }
-        String userId = object.getString("userid");
-        String userTicket = object.getString("user_ticket");
-        JSONObject userDetail = getUserDetail(authToken.getAccessToken(), userId, userTicket);
+        String userId = object.get("userid").asText();
+        String userTicket = object.has("user_ticket") ? object.get("user_ticket").asText() : null;
+        JsonNode userDetail = getUserDetail(authToken.getAccessToken(), userId, userTicket);

        return AuthUser.builder()
-            .rawUserInfo(userDetail)
-            .username(userDetail.getString("name"))
-            .nickname(userDetail.getString("alias"))
-            .avatar(userDetail.getString("avatar"))
-            .location(userDetail.getString("address"))
-            .email(userDetail.getString("email"))
+            .username(userDetail.has("name") ? userDetail.get("name").asText() : null)
+            .nickname(userDetail.has("alias") ? userDetail.get("alias").asText() : null)
+            .avatar(userDetail.has("avatar") ? userDetail.get("avatar").asText() : null)
+            .location(userDetail.has("address") ? userDetail.get("address").asText() : null)
+            .email(userDetail.has("email") ? userDetail.get("email").asText() : null)
            .uuid(userId)
-            .gender(AuthUserGender.getWechatRealGender(userDetail.getString("gender")))
+            .gender(AuthUserGender.getWechatRealGender(userDetail.has("gender") ? userDetail.get("gender").asText() : null))
            .token(authToken)
            .source(source.toString())
            .build();
@@ -78,16 +78,21 @@ public abstract class AbstractAuthWeChatEnterpriseRequest extends AuthDefaultReq
     * 校验请求结果
     *
     * @param response 请求结果
-     * @return 如果请求结果正常，则返回JSONObject
+     * @return 如果请求结果正常，则返回JsonNode
     */
-    private JSONObject checkResponse(String response) {
-        JSONObject object = JSONObject.parseObject(response);
+    private JsonNode checkResponse(String response) {
+        try {
+            ObjectMapper objectMapper = new ObjectMapper();
+            JsonNode object = objectMapper.readTree(response);

-        if (object.containsKey("errcode") && object.getIntValue("errcode") != 0) {
-            throw new AuthException(object.getString("errmsg"), source);
+            if (object.has("errcode") && object.get("errcode").asInt() != 0) {
+                throw new AuthException(object.get("errmsg").asText(), source);
+            }
+
+            return object;
+        } catch (Exception e) {
+            throw new AuthException("解析响应失败: " + e.getMessage(), source);
        }
-
-        return object;
    }


@@ -127,28 +132,39 @@ public abstract class AbstractAuthWeChatEnterpriseRequest extends AuthDefaultReq
     * @param userTicket  成员票据，用于获取用户信息或敏感信息
     * @return 用户详情
     */
-    private JSONObject getUserDetail(String accessToken, String userId, String userTicket) {
-        // 用户基础信息
-        String userInfoUrl = UrlBuilder.fromBaseUrl("https://qyapi.weixin.qq.com/cgi-bin/user/get")
-            .queryParam("access_token", accessToken)
-            .queryParam("userid", userId)
-            .build();
-        String userInfoResponse = new HttpUtils(config.getHttpConfig()).get(userInfoUrl).getBody();
-        JSONObject userInfo = checkResponse(userInfoResponse);
+    private JsonNode getUserDetail(String accessToken, String userId, String userTicket) {
+        try {
+            ObjectMapper objectMapper = new ObjectMapper();

-        // 用户敏感信息
-        if (StringUtils.isNotEmpty(userTicket)) {
-            String userDetailUrl = UrlBuilder.fromBaseUrl("https://qyapi.weixin.qq.com/cgi-bin/auth/getuserdetail")
+            // 用户基础信息
+            String userInfoUrl = UrlBuilder.fromBaseUrl("https://qyapi.weixin.qq.com/cgi-bin/user/get")
                .queryParam("access_token", accessToken)
+                .queryParam("userid", userId)
                .build();
-            JSONObject param = new JSONObject();
-            param.put("user_ticket", userTicket);
-            String userDetailResponse = new HttpUtils(config.getHttpConfig()).post(userDetailUrl, param.toJSONString()).getBody();
-            JSONObject userDetail = checkResponse(userDetailResponse);
+            String userInfoResponse = new HttpUtils(config.getHttpConfig()).get(userInfoUrl).getBody();
+            JsonNode userInfo = checkResponse(userInfoResponse);

-            userInfo.putAll(userDetail);
+            // 用户敏感信息
+            if (StringUtils.isNotEmpty(userTicket)) {
+                String userDetailUrl = UrlBuilder.fromBaseUrl("https://qyapi.weixin.qq.com/cgi-bin/auth/getuserdetail")
+                    .queryParam("access_token", accessToken)
+                    .build();
+
+                // 构建请求参数
+                String paramJson = objectMapper.createObjectNode()
+                    .put("user_ticket", userTicket)
+                    .toString();
+
+                String userDetailResponse = new HttpUtils(config.getHttpConfig()).post(userDetailUrl, paramJson).getBody();
+                JsonNode userDetail = checkResponse(userDetailResponse);
+
+                // 合并两个JsonNode
+                ((com.fasterxml.jackson.databind.node.ObjectNode) userInfo).setAll((com.fasterxml.jackson.databind.node.ObjectNode) userDetail);
+            }
+            return userInfo;
+        } catch (Exception e) {
+            throw new AuthException("获取用户详情失败: " + e.getMessage(), source);
        }
-        return userInfo;
    }

 }
--- a/ruoyi-common/ruoyi-common-social/src/main/java/me/zhyd/oauth/request/AuthDingTalkV2Request.java
+++ b/ruoyi-common/ruoyi-common-social/src/main/java/me/zhyd/oauth/request/AuthDingTalkV2Request.java
@@ -1,6 +1,7 @@
 package me.zhyd.oauth.request;

-import com.alibaba.fastjson.JSONObject;
+import com.fasterxml.jackson.databind.JsonNode;
+import com.fasterxml.jackson.databind.ObjectMapper;
 import com.xkcoding.http.support.HttpHeader;
 import me.zhyd.oauth.cache.AuthStateCache;
 import me.zhyd.oauth.config.AuthConfig;
@@ -52,44 +53,56 @@ public class AuthDingTalkV2Request extends AuthDefaultRequest {

    @Override
    public AuthToken getAccessToken(AuthCallback authCallback) {
-        Map<String, String> params = new HashMap<>();
-        params.put("grantType", "authorization_code");
-        params.put("clientId", config.getClientId());
-        params.put("clientSecret", config.getClientSecret());
-        params.put("code", authCallback.getCode());
-        String response = new HttpUtils(config.getHttpConfig()).post(this.source.accessToken(), JSONObject.toJSONString(params)).getBody();
-        JSONObject accessTokenObject = JSONObject.parseObject(response);
-        if (!accessTokenObject.containsKey("accessToken")) {
-            throw new AuthException(JSONObject.toJSONString(response), source);
+        try {
+            ObjectMapper objectMapper = new ObjectMapper();
+            Map<String, String> params = new HashMap<>();
+            params.put("grantType", "authorization_code");
+            params.put("clientId", config.getClientId());
+            params.put("clientSecret", config.getClientSecret());
+            params.put("code", authCallback.getCode());
+
+            String paramsJson = objectMapper.writeValueAsString(params);
+            String response = new HttpUtils(config.getHttpConfig()).post(this.source.accessToken(), paramsJson).getBody();
+            JsonNode accessTokenObject = objectMapper.readTree(response);
+
+            if (!accessTokenObject.has("accessToken")) {
+                throw new AuthException(response, source);
+            }
+            return AuthToken.builder()
+                .accessToken(accessTokenObject.get("accessToken").asText())
+                .refreshToken(accessTokenObject.has("refreshToken") ? accessTokenObject.get("refreshToken").asText() : null)
+                .expireIn(accessTokenObject.has("expireIn") ? accessTokenObject.get("expireIn").asInt() : 0)
+                .corpId(accessTokenObject.has("corpId") ? accessTokenObject.get("corpId").asText() : null)
+                .build();
+        } catch (Exception e) {
+            throw new AuthException("获取AccessToken失败: " + e.getMessage(), source);
        }
-        return AuthToken.builder()
-            .accessToken(accessTokenObject.getString("accessToken"))
-            .refreshToken(accessTokenObject.getString("refreshToken"))
-            .expireIn(accessTokenObject.getIntValue("expireIn"))
-            .corpId(accessTokenObject.getString("corpId"))
-            .build();
    }

    @Override
    public AuthUser getUserInfo(AuthToken authToken) {
-        HttpHeader header = new HttpHeader();
-        header.add("x-acs-dingtalk-access-token", authToken.getAccessToken());
+        try {
+            ObjectMapper objectMapper = new ObjectMapper();
+            HttpHeader header = new HttpHeader();
+            header.add("x-acs-dingtalk-access-token", authToken.getAccessToken());

-        String response = new HttpUtils(config.getHttpConfig()).get(this.source.userInfo(), null, header, false).getBody();
-        JSONObject object = JSONObject.parseObject(response);
+            String response = new HttpUtils(config.getHttpConfig()).get(this.source.userInfo(), null, header, false).getBody();
+            JsonNode object = objectMapper.readTree(response);

-        authToken.setOpenId(object.getString("openId"));
-        authToken.setUnionId(object.getString("unionId"));
-        return AuthUser.builder()
-            .rawUserInfo(object)
-            .uuid(object.getString("unionId"))
-            .username(object.getString("nick"))
-            .nickname(object.getString("nick"))
-            .avatar(object.getString("avatarUrl"))
-            .snapshotUser(object.getBooleanValue("visitor"))
-            .token(authToken)
-            .source(source.toString())
-            .build();
+            authToken.setOpenId(object.has("openId") ? object.get("openId").asText() : null);
+            authToken.setUnionId(object.has("unionId") ? object.get("unionId").asText() : null);
+            return AuthUser.builder()
+                .uuid(object.has("unionId") ? object.get("unionId").asText() : null)
+                .username(object.has("nick") ? object.get("nick").asText() : null)
+                .nickname(object.has("nick") ? object.get("nick").asText() : null)
+                .avatar(object.has("avatarUrl") ? object.get("avatarUrl").asText() : null)
+                .snapshotUser(object.has("visitor") && object.get("visitor").asBoolean())
+                .token(authToken)
+                .source(source.toString())
+                .build();
+        } catch (Exception e) {
+            throw new AuthException("获取用户信息失败: " + e.getMessage(), source);
+        }
    }

    /**
--- a/ruoyi-common/ruoyi-common-sse/src/main/java/org/ruoyi/common/sse/core/SseEmitterManager.java
+++ b/ruoyi-common/ruoyi-common-sse/src/main/java/org/ruoyi/common/sse/core/SseEmitterManager.java
@@ -32,6 +32,16 @@ public class SseEmitterManager {
     */
    private final static String SSE_TOPIC = "global:sse";

+    /**
+     * 按会话维度管理：每个会话一个 SSE 连接，用于对话流式响应
+     * Key: sessionId
+     */
+    private final static Map<String, SseEmitter> SESSION_EMITTERS = new ConcurrentHashMap<>();
+
+    /**
+     * 按用户维度管理：全局通知、站内信等场景，一个用户可有多个连接（按 token 区分）
+     * Key: userId, Value: token -> SseEmitter
+     */
    private final static Map<Long, Map<String, SseEmitter>> USER_TOKEN_EMITTERS = new ConcurrentHashMap<>();

    public SseEmitterManager() {
@@ -40,6 +50,98 @@ public class SseEmitterManager {
            .scheduleWithFixedDelay(this::sseMonitor, 60L, 60L, TimeUnit.SECONDS);
    }

+    // ======================== 会话维度（对话流式响应） ========================
+
+    /**
+     * 建立与指定会话的 SSE 连接，每个会话仅保留一个连接，重复建连会替换旧连接。
+     *
+     * @param sessionId 会话ID
+     * @return SseEmitter 实例
+     */
+    public SseEmitter connect(String sessionId) {
+        if (sessionId == null) {
+            throw new IllegalArgumentException("sessionId 不能为空");
+        }
+        // 关闭已存在的 SseEmitter，保证每个会话只有一个活跃连接
+        SseEmitter oldEmitter = SESSION_EMITTERS.remove(sessionId);
+        if (oldEmitter != null) {
+            oldEmitter.complete();
+        }
+
+        SseEmitter emitter = new SseEmitter(86400000L);
+        SESSION_EMITTERS.put(sessionId, emitter);
+
+        emitter.onCompletion(() -> removeSessionEmitter(sessionId, emitter));
+        emitter.onTimeout(() -> removeSessionEmitter(sessionId, emitter));
+        emitter.onError(e -> removeSessionEmitter(sessionId, emitter));
+
+        try {
+            emitter.send(SseEmitter.event().comment("connected"));
+        } catch (IOException e) {
+            SESSION_EMITTERS.remove(sessionId);
+        }
+        return emitter;
+    }
+
+    /**
+     * 断开指定会话的 SSE 连接
+     *
+     * @param sessionId 会话ID
+     */
+    public void disconnect(String sessionId) {
+        if (sessionId == null) {
+            return;
+        }
+        SseEmitter emitter = SESSION_EMITTERS.remove(sessionId);
+        if (emitter != null) {
+            try {
+                emitter.send(SseEmitter.event().comment("disconnected"));
+            } catch (Exception exception) {
+                log.error(exception.getMessage());
+            }
+            emitter.complete();
+        }
+    }
+
+    /**
+     * 向指定会话发送结构化事件
+     *
+     * @param sessionId 会话ID
+     * @param eventDto  SSE事件对象
+     */
+    public void sendEvent(String sessionId, SseEventDto eventDto) {
+        if (sessionId == null || eventDto == null) {
+            return;
+        }
+        SseEmitter emitter = SESSION_EMITTERS.get(sessionId);
+        if (emitter == null) {
+            log.warn("【SSE发送失败】sessionId: {} 没有活跃的SSE连接", sessionId);
+            return;
+        }
+        try {
+            log.debug("【SSE发送】sessionId: {}, event: {}", sessionId, eventDto.getEvent());
+            emitter.send(SseEmitter.event()
+                .name(eventDto.getEvent())
+                .data(JSONUtil.toJsonStr(eventDto)));
+        } catch (Exception e) {
+            log.error("【SSE发送失败】sessionId: {}, error: {}", sessionId, e.getMessage());
+            removeSessionEmitter(sessionId, emitter);
+        }
+    }
+
+    private void removeSessionEmitter(String sessionId, SseEmitter emitter) {
+        boolean removed = SESSION_EMITTERS.remove(sessionId, emitter);
+        if (removed) {
+            try {
+                emitter.complete();
+            } catch (Exception ignore) {
+                // 忽略重复关闭异常
+            }
+        }
+    }
+
+    // ======================== 用户维度（全局通知） ========================
+
    /**
     * 建立与指定用户的 SSE 连接
     *
@@ -154,6 +256,23 @@ public class SseEmitterManager {

        // 循环结束后统一清理空用户，避免并发修改异常
        toRemoveUsers.forEach(USER_TOKEN_EMITTERS::remove);
+
+        // 会话维度心跳：发送失败的连接移除
+        if (!SESSION_EMITTERS.isEmpty()) {
+            SESSION_EMITTERS.entrySet().removeIf(entry -> {
+                try {
+                    entry.getValue().send(heartbeat);
+                    return false;
+                } catch (Exception ex) {
+                    try {
+                        entry.getValue().complete();
+                    } catch (Exception ignore) {
+                        // 忽略重复关闭异常
+                    }
+                    return true;
+                }
+            });
+        }
    }

    /**
@@ -243,9 +362,11 @@ public class SseEmitterManager {
        SseMessageDto broadcastMessage = new SseMessageDto();
        broadcastMessage.setMessage(sseMessageDto.getMessage());
        broadcastMessage.setUserIds(sseMessageDto.getUserIds());
+        broadcastMessage.setSessionId(sseMessageDto.getSessionId());
+        broadcastMessage.setEventDto(sseMessageDto.getEventDto());
        RedisUtils.publish(SSE_TOPIC, broadcastMessage, consumer -> {
-            log.info("SSE发送主题订阅消息topic:{} session keys:{} message:{}",
-                SSE_TOPIC, sseMessageDto.getUserIds(), sseMessageDto.getMessage());
+            log.info("SSE发送主题订阅消息topic:{} session:{} session keys:{} message:{}",
+                SSE_TOPIC, sseMessageDto.getSessionId(), sseMessageDto.getUserIds(), sseMessageDto.getMessage());
        });
    }

--- a/ruoyi-common/ruoyi-common-sse/src/main/java/org/ruoyi/common/sse/dto/SseMessageDto.java
+++ b/ruoyi-common/ruoyi-common-sse/src/main/java/org/ruoyi/common/sse/dto/SseMessageDto.java
@@ -26,4 +26,14 @@ public class SseMessageDto implements Serializable {
     * 需要发送的消息
     */
    private String message;
+
+    /**
+     * 按会话定向推送的会话ID（非空时优先按会话路由，忽略 userIds）
+     */
+    private String sessionId;
+
+    /**
+     * 结构化事件（按会话定向推送时使用，message 为兼容旧逻辑保留）
+     */
+    private SseEventDto eventDto;
 }
--- a/ruoyi-common/ruoyi-common-sse/src/main/java/org/ruoyi/common/sse/listener/SseTopicListener.java
+++ b/ruoyi-common/ruoyi-common-sse/src/main/java/org/ruoyi/common/sse/listener/SseTopicListener.java
@@ -1,8 +1,10 @@
 package org.ruoyi.common.sse.listener;

 import cn.hutool.core.collection.CollUtil;
+import cn.hutool.core.util.StrUtil;
 import lombok.extern.slf4j.Slf4j;
 import org.ruoyi.common.sse.core.SseEmitterManager;
+import org.ruoyi.common.sse.dto.SseMessageDto;
 import org.springframework.beans.factory.annotation.Autowired;
 import org.springframework.boot.ApplicationArguments;
 import org.springframework.boot.ApplicationRunner;
@@ -28,8 +30,20 @@ public class SseTopicListener implements ApplicationRunner, Ordered {
    @Override
    public void run(ApplicationArguments args) throws Exception {
        sseEmitterManager.subscribeMessage((message) -> {
-            log.info("SSE主题订阅收到消息session keys={} message={}", message.getUserIds(), message.getMessage());
-            // 如果key不为空就按照key发消息 如果为空就群发
+            log.info("SSE主题订阅收到消息session:{} session keys={} message={}",
+                message.getSessionId(), message.getUserIds(), message.getMessage());
+            // 优先按会话路由（对话流式响应）
+            if (StrUtil.isNotBlank(message.getSessionId())) {
+                if (message.getEventDto() != null) {
+                    sseEmitterManager.sendEvent(message.getSessionId(), message.getEventDto());
+                } else if (message.getMessage() != null) {
+                    // 兼容按会话发纯文本的场景
+                    sseEmitterManager.sendEvent(message.getSessionId(),
+                        org.ruoyi.common.sse.dto.SseEventDto.content(message.getMessage()));
+                }
+                return;
+            }
+            // 否则按用户/群发路由（全局通知）
            if (CollUtil.isNotEmpty(message.getUserIds())) {
                message.getUserIds().forEach(key -> {
                    sseEmitterManager.sendMessage(key, message.getMessage());
--- a/ruoyi-common/ruoyi-common-sse/src/main/java/org/ruoyi/common/sse/utils/SseMessageUtils.java
+++ b/ruoyi-common/ruoyi-common-sse/src/main/java/org/ruoyi/common/sse/utils/SseMessageUtils.java
@@ -93,6 +93,15 @@ public class SseMessageUtils {
        MANAGER.disconnect(userId, tokenValue);
    }

+    /**
+     * 完成指定会话的SSE连接
+     *
+     * @param sessionId 会话ID
+     */
+    public static void completeConnection(String sessionId) {
+        MANAGER.disconnect(sessionId);
+    }
+
    /**
     * 向指定的SSE会话发送结构化事件
     *
@@ -106,6 +115,22 @@ public class SseMessageUtils {
        MANAGER.sendEvent(userId, eventDto);
    }

+    /**
+     * 向指定会话发送结构化事件（通过 Redis 广播，跨实例可达）
+     *
+     * @param sessionId 会话ID
+     * @param eventDto  SSE事件对象
+     */
+    public static void sendEvent(String sessionId, SseEventDto eventDto) {
+        if (!isEnable() || sessionId == null) {
+            return;
+        }
+        SseMessageDto dto = new SseMessageDto();
+        dto.setSessionId(sessionId);
+        dto.setEventDto(eventDto);
+        MANAGER.publishMessage(dto);
+    }
+
    /**
     * 发送内容事件
     *
@@ -116,6 +141,16 @@ public class SseMessageUtils {
        sendEvent(userId, SseEventDto.content(content));
    }

+    /**
+     * 向指定会话发送内容事件
+     *
+     * @param sessionId 会话ID
+     * @param content   内容
+     */
+    public static void sendContent(String sessionId, String content) {
+        sendEvent(sessionId, SseEventDto.content(content));
+    }
+
    /**
     * 发送推理内容事件
     *
@@ -126,6 +161,16 @@ public class SseMessageUtils {
        sendEvent(userId, SseEventDto.reasoning(reasoningContent));
    }

+    /**
+     * 向指定会话发送推理内容事件
+     *
+     * @param sessionId        会话ID
+     * @param reasoningContent 推理内容
+     */
+    public static void sendReasoning(String sessionId, String reasoningContent) {
+        sendEvent(sessionId, SseEventDto.reasoning(reasoningContent));
+    }
+
    /**
     * 发送完成事件
     *
@@ -135,6 +180,15 @@ public class SseMessageUtils {
        sendEvent(userId, SseEventDto.done());
    }

+    /**
+     * 向指定会话发送完成事件
+     *
+     * @param sessionId 会话ID
+     */
+    public static void sendDone(String sessionId) {
+        sendEvent(sessionId, SseEventDto.done());
+    }
+
    /**
     * 发送错误事件
     *
@@ -145,6 +199,16 @@ public class SseMessageUtils {
        sendEvent(userId, SseEventDto.error(error));
    }

+    /**
+     * 向指定会话发送错误事件
+     *
+     * @param sessionId 会话ID
+     * @param error     错误信息
+     */
+    public static void sendError(String sessionId, String error) {
+        sendEvent(sessionId, SseEventDto.error(error));
+    }
+
    /**
     * 是否开启
     */
--- a/ruoyi-common/ruoyi-common-trace/pom.xml
+++ b/ruoyi-common/ruoyi-common-trace/pom.xml
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project xmlns="http://maven.apache.org/POM/4.0.0"
+         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+    <parent>
+        <groupId>org.ruoyi</groupId>
+        <artifactId>ruoyi-common</artifactId>
+        <version>${revision}</version>
+    </parent>
+    <modelVersion>4.0.0</modelVersion>
+
+    <artifactId>ruoyi-common-trace</artifactId>
+
+    <description>
+        ruoyi-common-trace 通用链路追踪
+    </description>
+
+    <dependencies>
+        <dependency>
+            <groupId>org.ruoyi</groupId>
+            <artifactId>ruoyi-common-core</artifactId>
+        </dependency>
+        <dependency>
+            <groupId>org.ruoyi</groupId>
+            <artifactId>ruoyi-common-mybatis</artifactId>
+        </dependency>
+        <dependency>
+            <groupId>org.ruoyi</groupId>
+            <artifactId>ruoyi-common-json</artifactId>
+        </dependency>
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-test</artifactId>
+            <scope>test</scope>
+        </dependency>
+        <dependency>
+            <groupId>org.mockito</groupId>
+            <artifactId>mockito-junit-jupiter</artifactId>
+            <scope>test</scope>
+        </dependency>
+    </dependencies>
+</project>
--- a/ruoyi-common/ruoyi-common-trace/src/main/java/org/ruoyi/common/trace/config/TraceAutoConfiguration.java
+++ b/ruoyi-common/ruoyi-common-trace/src/main/java/org/ruoyi/common/trace/config/TraceAutoConfiguration.java
@@ -0,0 +1,14 @@
+package org.ruoyi.common.trace.config;
+
+import org.springframework.boot.autoconfigure.AutoConfiguration;
+import org.springframework.boot.context.properties.EnableConfigurationProperties;
+
+/**
+ * 通用链路追踪自动配置。
+ * <p>
+ * 仅注册配置属性；节点采集通过 {@code TraceNodeTemplate} / {@code DefaultTraceStreamSpan} 编程式埋点完成。
+ */
+@AutoConfiguration
+@EnableConfigurationProperties(TraceProperties.class)
+public class TraceAutoConfiguration {
+}
--- a/ruoyi-common/ruoyi-common-trace/src/main/java/org/ruoyi/common/trace/config/TraceProperties.java
+++ b/ruoyi-common/ruoyi-common-trace/src/main/java/org/ruoyi/common/trace/config/TraceProperties.java
@@ -0,0 +1,31 @@
+package org.ruoyi.common.trace.config;
+
+import lombok.Data;
+import org.springframework.boot.context.properties.ConfigurationProperties;
+
+/**
+ * 通用链路追踪配置。
+ */
+@Data
+@ConfigurationProperties(prefix = "trace")
+public class TraceProperties {
+
+    /**
+     * 是否启用链路追踪。
+     */
+    private boolean enabled = true;
+
+    /**
+     * payload 记录策略。
+     */
+    private Payload payload = new Payload();
+
+    @Data
+    public static class Payload {
+
+        /**
+         * 错误信息最大长度。
+         */
+        private int maxErrorLength = 1000;
+    }
+}
--- a/ruoyi-common/ruoyi-common-trace/src/main/java/org/ruoyi/common/trace/constant/TraceConstants.java
+++ b/ruoyi-common/ruoyi-common-trace/src/main/java/org/ruoyi/common/trace/constant/TraceConstants.java
@@ -0,0 +1,15 @@
+package org.ruoyi.common.trace.constant;
+
+/**
+ * 通用链路追踪常量。
+ */
+public final class TraceConstants {
+
+    private TraceConstants() {
+    }
+
+    public static final String STATUS_RUNNING = "RUNNING";
+    public static final String STATUS_SUCCESS = "SUCCESS";
+    public static final String STATUS_ERROR = "ERROR";
+    public static final String STATUS_CANCELLED = "CANCELLED";
+}
--- a/ruoyi-common/ruoyi-common-trace/src/main/java/org/ruoyi/common/trace/constant/TraceDisplayConstants.java
+++ b/ruoyi-common/ruoyi-common-trace/src/main/java/org/ruoyi/common/trace/constant/TraceDisplayConstants.java
@@ -0,0 +1,163 @@
+package org.ruoyi.common.trace.constant;
+
+import java.util.Map;
+
+/**
+ * 链路追踪中文展示常量。
+ * <p>
+ * 将技术标识映射为用户可读的中文标签，供前端直接展示。
+ */
+public final class TraceDisplayConstants {
+
+    private TraceDisplayConstants() {
+    }
+
+    // ======================== 节点类型中文映射 ========================
+
+    /**
+     * 通用节点类型中文标签。
+     */
+    public static final Map<String, String> NODE_TYPE_LABELS = Map.ofEntries(
+        Map.entry("RETRIEVAL", "知识检索"),
+        Map.entry("RERANK", "重排序"),
+        Map.entry("LLM_CALL", "LLM 调用"),
+        Map.entry("STREAM", "流式输出"),
+        Map.entry("METHOD", "方法调用"),
+        Map.entry("HTTP", "HTTP 请求"),
+        Map.entry("DB", "数据库"),
+        Map.entry("CACHE", "缓存操作"),
+        Map.entry("TASK", "异步任务"),
+        Map.entry("ROOT", "根节点")
+    );
+
+    /**
+     * 业务类型中文标签。
+     */
+    public static final Map<String, String> BUSINESS_TYPE_LABELS = Map.ofEntries(
+        Map.entry("RAG_CHAT", "RAG 对话"),
+        Map.entry("API", "API 调用"),
+        Map.entry("SCHEDULED", "定时任务")
+    );
+
+    /**
+     * 状态中文标签。
+     */
+    public static final Map<String, String> STATUS_LABELS = Map.ofEntries(
+        Map.entry("RUNNING", "运行中"),
+        Map.entry("SUCCESS", "成功"),
+        Map.entry("ERROR", "失败"),
+        Map.entry("CANCELLED", "已取消"),
+        Map.entry("TIMEOUT", "超时")
+    );
+
+    // ======================== 工具方法 ========================
+
+    /**
+     * 获取节点类型中文标签，未匹配时返回原始值。
+     */
+    public static String nodeTypeLabel(String nodeType) {
+        if (nodeType == null) {
+            return "-";
+        }
+        return NODE_TYPE_LABELS.getOrDefault(nodeType.toUpperCase(), nodeType);
+    }
+
+    /**
+     * 获取业务类型中文标签，未匹配时返回原始值。
+     */
+    public static String businessTypeLabel(String businessType) {
+        if (businessType == null) {
+            return "-";
+        }
+        return BUSINESS_TYPE_LABELS.getOrDefault(businessType.toUpperCase(), businessType);
+    }
+
+    /**
+     * 获取状态中文标签，未匹配时返回原始值。
+     */
+    public static String statusLabel(String status) {
+        if (status == null) {
+            return "未知";
+        }
+        return STATUS_LABELS.getOrDefault(status.toUpperCase(), status);
+    }
+
+    /**
+     * 将技术节点名称转为可读展示名。
+     * <p>
+     * 支持 kebab-case / snake_case / camelCase → 首字母大写空格分隔。
+     */
+    public static String prettifyNodeName(String raw) {
+        if (raw == null || raw.isBlank()) {
+            return "-";
+        }
+        String trimmed = raw.trim();
+        // 已知映射优先
+        Map<String, String> known = Map.ofEntries(
+            Map.entry("rag-chat", "RAG 流式对话"),
+            Map.entry("rag-stream-chat", "RAG 流式对话"),
+            Map.entry("retrieval-engine", "知识库检索"),
+            Map.entry("multi-channel-retrieval", "多路召回"),
+            Map.entry("context-build", "上下文组装"),
+            Map.entry("prompt-render", "Prompt 渲染"),
+            Map.entry("query-rewrite-and-split", "问题改写与拆分"),
+            Map.entry("intent-resolve", "意图识别"),
+            Map.entry("guidance-detect", "歧义引导"),
+            Map.entry("conversation-title-gen", "会话标题生成"),
+            Map.entry("user-first-packet", "用户感知首包"),
+            Map.entry("llm-first-packet", "LLM 首包"),
+            Map.entry("llm-chat-routing", "LLM 路由调度"),
+            Map.entry("llm-stream-routing", "LLM 流式路由")
+        );
+        if (known.containsKey(trimmed)) {
+            return known.get(trimmed);
+        }
+        // 通用格式化: 按 [-_] 分割，每段首字母大写
+        String[] parts = trimmed.split("[-_\\s]+");
+        StringBuilder sb = new StringBuilder();
+        for (String part : parts) {
+            if (part.isEmpty()) {
+                continue;
+            }
+            if (sb.length() > 0) {
+                sb.append(' ');
+            }
+            sb.append(Character.toUpperCase(part.charAt(0)));
+            if (part.length() > 1) {
+                sb.append(part.substring(1));
+            }
+        }
+        return sb.length() > 0 ? sb.toString() : trimmed;
+    }
+
+    /**
+     * 判断状态是否为失败。
+     */
+    public static boolean isFailed(String status) {
+        if (status == null) {
+            return false;
+        }
+        String upper = status.toUpperCase();
+        return "ERROR".equals(upper) || "FAILED".equals(upper) || "TIMEOUT".equals(upper);
+    }
+
+    /**
+     * 判断状态是否为成功。
+     */
+    public static boolean isSuccess(String status) {
+        if (status == null) {
+            return false;
+        }
+        return "SUCCESS".equalsIgnoreCase(status);
+    }
+
+    /**
+     * 判断状态是否为运行中。
+     */
+    public static boolean isRunning(String status) {
+        if (status == null) {
+            return false;
+        }
+        return "RUNNING".equalsIgnoreCase(status);
+    }
+}
--- a/ruoyi-common/ruoyi-common-trace/src/main/java/org/ruoyi/common/trace/core/DefaultTraceStreamSpan.java
+++ b/ruoyi-common/ruoyi-common-trace/src/main/java/org/ruoyi/common/trace/core/DefaultTraceStreamSpan.java
@@ -0,0 +1,71 @@
+package org.ruoyi.common.trace.core;
+
+import lombok.extern.slf4j.Slf4j;
+import org.ruoyi.common.trace.config.TraceProperties;
+import org.ruoyi.common.trace.constant.TraceConstants;
+import org.ruoyi.common.trace.service.TraceRecordService;
+import org.ruoyi.common.trace.util.TracePayloadUtils;
+
+import java.util.Date;
+import java.util.concurrent.atomic.AtomicBoolean;
+
+/**
+ * 默认流式 trace 节点实现。
+ */
+@Slf4j
+public class DefaultTraceStreamSpan implements TraceStreamSpan {
+
+    private final TraceRecordService traceRecordService;
+    private final TraceProperties traceProperties;
+    private final String traceId;
+    private final String nodeId;
+    private final long startMillis;
+    private final AtomicBoolean finished = new AtomicBoolean(false);
+    private final AtomicBoolean detached = new AtomicBoolean(false);
+
+    public DefaultTraceStreamSpan(TraceRecordService traceRecordService,
+                                  TraceProperties traceProperties,
+                                  String traceId,
+                                  String nodeId,
+                                  long startMillis) {
+        this.traceRecordService = traceRecordService;
+        this.traceProperties = traceProperties;
+        this.traceId = traceId;
+        this.nodeId = nodeId;
+        this.startMillis = startMillis;
+    }
+
+    @Override
+    public void detach() {
+        if (detached.compareAndSet(false, true)) {
+            TraceContext.popNode();
+        }
+    }
+
+    @Override
+    public void finishSuccess(String outputPayload) {
+        finish(TraceConstants.STATUS_SUCCESS, null, outputPayload);
+    }
+
+    @Override
+    public void finishError(Throwable throwable) {
+        finish(TraceConstants.STATUS_ERROR, TracePayloadUtils.error(throwable, traceProperties), null);
+    }
+
+    @Override
+    public void finishCancelledIfRunning() {
+        finish(TraceConstants.STATUS_CANCELLED, null, null);
+    }
+
+    private void finish(String status, String errorMessage, String outputPayload) {
+        if (!finished.compareAndSet(false, true)) {
+            return;
+        }
+        try {
+            traceRecordService.finishNode(traceId, nodeId, status, errorMessage, outputPayload,
+                new Date(), System.currentTimeMillis() - startMillis);
+        } catch (Exception e) {
+            log.warn("结束 trace stream span 失败，traceId={}, nodeId={}", traceId, nodeId, e);
+        }
+    }
+}
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
ageerle	9d439d1dcf	refactor: move RAG trace classes to argtrace package and update SQL schema - Rename org.ruoyi.trace package to org.ruoyi.argtrace for RagTraceNodeTypes and RagTracePayloadBuilder; fix package declarations and update imports in ChatServiceFacade and KnowledgeRetrievalServiceImpl - Remove obsolete RagTracePayloadBuilderTest - Switch supervisor response strategy from SUMMARY to LAST in ChatServiceFacade - Refresh docs/script/sql/ruoyi-ai.sql with the latest full schema dump - Add live demo links (admin panel, user frontend, commercial edition) to README.md and README_ZH.md Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-04 17:44:39 +08:00
ageerle	0a08c489be	docs: remove redundant registry commands	2026-08-04 15:57:32 +08:00
ageerle	038e7725f9	docs: add prebuilt image deployment guide	2026-08-04 15:55:17 +08:00
ageerle	4ccf249663	docs: remove obsolete WeChat image	2026-08-04 15:50:51 +08:00
ageerle	1d5b01f77f	docs: remove obsolete Douyin image	2026-08-04 15:50:36 +08:00
ageerle	538dac3a46	docs: add Douyin tutorial QR code	2026-08-04 15:49:40 +08:00
ageerle	6c383dd9f5	fix: 修复智能体编辑时关联工具加载失败 (#320 )	2026-08-04 15:38:25 +08:00
ageerle	9ae49f8797	fix: allow frontend dependency builds in image workflow	2026-08-04 15:30:34 +08:00
ageerle	3c175ba28d	chore: sync pending project changes	2026-08-04 15:23:19 +08:00
ageerle	e34592c3d4	release: prepare v3.1.0	2026-08-04 15:18:57 +08:00
ageerle	fd044a4752	docs: align README badges in one row	2026-07-30 00:22:22 +08:00
ageerle	6e264ad500	feat: streamline workflow orchestration and chat routing Add Zhipu web search integration, remove obsolete workflow nodes and resume handling, and separate model, agent, and workflow chat execution.	2026-07-30 00:15:44 +08:00
ageerle	83fd1ee983	fix: 移除FastJson 1.2.83严重安全漏洞，替换为Jackson - 移除FastJson 1.2.83依赖（存在严重RCE漏洞CVE-2022-25845等） - 替换为Spring Boot内置的Jackson 2.18.2 - 修改6个Java文件的JSON处理逻辑 - 所有模块编译验证通过修改文件： 1. pom.xml - 移除fastjson依赖定义 2. ruoyi-common-chat/pom.xml - 替换为jackson-databind 3. QwenFileUploadUtils.java - 千问文件上传JSON解析 4. ChatRequest.java - 移除FastJson注解 5. MailSendNode.java - 邮件节点JSON处理 6. SwitcherNode.java - 条件分支JSON处理 7. AbstractAuthWeChatEnterpriseRequest.java - 企业微信登录 8. AuthDingTalkV2Request.java - 钉钉登录安全提升：消除FastJson反序列化RCE漏洞攻击面 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-29 14:59:20 +08:00
ageerle	7640de34e5	Merge pull request #318 from ageerle/feat/register-default-role-and-misc feat: 注册默认角色绑定 + 短剧流式超时兜底 + trace 测试适配	2026-07-28 11:25:37 +08:00
ageerle	77846601ee	test(retrieval): 适配 KnowledgeRetrievalServiceImpl 新增 trace 依赖构造测试实例时补上 TraceRecordService 与 TraceProperties 两个新参数, 修复编译/构造失败。 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-28 11:22:26 +08:00
ageerle	b80dc6e23f	fix(shortdrama): 流式生成增加首 token 90 秒超时兜底部分聚合站对 stream=true 既不返回内容也不报错,外层 30 分钟总超时才会失败,前端会长时间卡死。90 秒内未收到任何 token 时快速失败, 提示更换模型或使用同步生成。收到首 token 后取消兜底计时。 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-28 11:22:19 +08:00
ageerle	176cc67a5c	feat(register): 新用户注册成功后绑定默认角色并补齐缺失菜单权限 - SysRegisterService: 注册成功后读取 sys.register.defaultRoleId 配置, 为新用户绑定默认角色;未配置则静默跳过,不影响注册流程 - SysUserServiceImpl.registerUser: insert 后回写 userId 主键, 供调用方绑定默认角色或登录使用 - SQL: 修正知识管理父菜单 perms(knowledge:info:list -> system:info:list), 新增 system:session:* / system:attach:* / system:fragment:* 菜单, 新建普通用户角色(租户 000000,data_scope=5 仅本人)及角色-菜单关联, 写入 sys.register.defaultRoleId 配置项解决注册用户无默认角色导致无权限访问 AI 对话界面、以及菜单权限标识与控制器不一致无法授权的问题。 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-28 11:22:12 +08:00
ageerle	afaa86ef6e	Merge branch 'fix/sse-session-trace-cleanup'	2026-07-23 15:38:50 +08:00
ageerle	d1a820728f	fix(sse): SSE 改为按会话隔离 + 修 trace 租户 bug + 清理冗余 SSE 串台修复： - SseEmitterManager 新增按 sessionId 维度的 connect/sendEvent/disconnect，每个会话一个 SSE 连接，替代原 userId+token 维度（同用户多会话串台） - SseMessageDto 增加 sessionId + eventDto 字段，跨实例按会话路由 - SseTopicListener 优先按 sessionId 路由，回退原 userId/群发逻辑 - SseMessageUtils 增加 sessionId 重载，对话链路全部切换 - ChatServiceFacade / MyMcpClientListener / WorkflowStarter 切到 sessionId - 通知/全局 /sse 端点保留 userId 模式（通知按用户） trace 租户 bug 修复： - trace_run / trace_node 加入 tenant.excludes，监控表跨租户全局可见，绕过异步线程租户上下文不传播导致 node 查不到的问题冗余清理： - 删除零使用的 @TraceNode 注解 + TraceNodeAspect 切面 + 对应单测 - TraceProperties 删除 recordDetail/maxInputLength/maxOutputLength （仅对已删切面生效，编程式埋点用 RagTracePayloadBuilder 不受影响） - TracePayloadUtils 删除 input/output/asString 方法 - TraceConstants 删除无引用的 NODE_METHOD/HTTP/DB/CACHE/TASK/STREAM - TraceContext 删除预留的 copyNodeStack - TraceNodeVo 删除未用的 children 字段 - TraceRecordServiceImpl.getDetail 删除重复 enrich - application.yml 删除 trace.payload 无效配置项 - RagTraceNodeTypes 删除无引用的 NODE_STREAM Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-23 15:35:10 +08:00
ageerle	11bb1dba0f	Merge PR #308 : 通用链路追踪模块与 RAG 对话全链路埋点	2026-07-23 15:10:40 +08:00
Obltv	345d2819d8	fix: 修复链路追踪输出记录及关闭追踪时的额外开销	2026-07-23 14:52:19 +08:00
Obltv	36e3cf8c52	fix: 修复链路追踪输出记录及关闭追踪时的额外开销	2026-07-23 14:45:43 +08:00
Obltv	06ff95cdc3	Merge upstream/main into feature/common-trace-rag-chat	2026-07-23 14:30:38 +08:00
ageerle	9adeee6c83	fix(short-drama): 修复角色形象跨分镜不一致 1. findRefImageIndex 补上 appearance 参数，与 findStoryboardReferenceImages 的调用对齐。之前多形象角色（换装/青年老年）的 @imageN 绑定查的是默认形象 URL，和实际参考图列表对不上，导致 prompt 里没有 @imageN 标记 2. buildEnrichedVideoPrompt 角色段追加 visualDescription，文字 prompt 也承载外貌信息（发型/服装/体态），不能全靠参考图 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-21 16:06:06 +08:00
ageerle	e42d35f3bf	fix: 工作流实体保留字转义 + 千问向量模型厂商映射 1. WorkflowRuntimeNode/WorkflowRuntime: input/output/status 字段加反引号，修复 MySQL 8.0 保留字导致 MyBatis-Plus SQL 解析异常 (#307) 2. EmbeddingModelFactory: 新增 providerCode→BeanName 映射， qianwen→alibailian，修复千问向量模型找不到 Bean 的问题 (#301) Closes #307 #301 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-21 15:43:36 +08:00
ageerle	a69d1f51b9	feat: 打通 thinking 流式链路 + SqlAgent 表白名单校验 1. OllamaServiceImpl 补 .think() + .returnThinking()，对齐其他 provider (#306) 2. ChatServiceFacade.createCombinedHandler 新增 onPartialThinking， reasoning 内容经 SseMessageUtils.sendReasoning 流式推到前端 (#303) 3. SqlAgent 系统提示词追加无表时禁止执行 SQL 的规则 (#279) 4. ExecuteSqlQueryTool 代码层硬拦截：空白名单直接拒绝，有白名单则校验 SQL 中 FROM/JOIN 引用的表名 (#279) Closes #303 #306 #279 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-21 15:31:32 +08:00
ageerle	911ae6cb1f	fix: 修复 issue IJX5VV/IJPYWL/IHPUDA - IJX5VV: 补全工作流 9 个节点消息模板 sys_config 配置（SQL 脚本合并重命名时遗失），附幂等增量脚本；此前节点执行会抛「请先配置该节点的响应模板」 - IJPYWL: 向量模型未配置维度时，Milvus/Qdrant 回退默认 1024，避免 Integer 拆箱 NPE - IHPUDA: chat_provider.provider_icon 由 varchar(255) 加宽至 varchar(1000)，容纳 minio 私有桶签名 URL，附增量脚本 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-21 15:28:28 +08:00
ageerle	9a2f326e42	fix(rag): 合并后修正-升级脚本兼容 MySQL 8、重解析按 docId 清理旧向量 1. 升级脚本 2026-07-20-knowledge-fragment-fid.sql 使用了 MySQL 8 不支持的 ADD COLUMN IF NOT EXISTS（MariaDB 语法），在存量库执行会直接语法报错。改为与脚本内索引守卫一致的 information_schema 判断 + PREPARE 方式，保持幂等。 2. parse() 重新解析时按 fragment.fid 删除旧向量：存量数据的 fid 为迁移脚本回填的 MD5 值，与向量库中实际存储的随机 fid 不一致，首次重解析无法命中旧向量，导致新旧向量重复累积。改为写入新向量前先按 docId 清理（三种向量库策略均支持），写入失败时仍补偿删除新 fid。 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-21 14:33:28 +08:00
ageerle@163.com	46a8d6b552	Merge pull request #315 from MuSan-Li/update/2026-07-19-fixes 修复RAG相关逻辑优化:统一文档切割配置、向量数据生命周期、统一检索服务(阈值/重排/缓存)、按知识库路由向量库、重新解析支持	2026-07-21 14:33:11 +08:00
evo	cf5423f69f	fix(rag): 统一文档切割配置并支持重新解析	2026-07-21 12:18:19 +08:00
evo	177375a7b7	docs(rag): 更新完整修复与验收报告	2026-07-21 09:35:56 +08:00
evo	016bdbdd94	test(rag): 增加三向量库 Docker 生命周期测试	2026-07-21 09:35:56 +08:00
evo	41e0dcb528	chore(rag): 对齐默认向量配置并启用测试	2026-07-21 09:35:56 +08:00
evo	787e447d09	fix(aiflow): 接入统一知识库检索服务	2026-07-21 09:35:33 +08:00
evo	9c092ae3bb	fix(chat): 统一单轮检索并完善多库上下文	2026-07-21 09:35:26 +08:00
evo	42bc8fea95	fix(rag): 完善向量路由批量写入与数据生命周期	2026-07-21 09:35:18 +08:00
evo	c4fc1e6fcf	fix(rag): 隔离模型实例并修正缓存刷新	2026-07-21 09:35:07 +08:00
evo	6f6d0893ec	fix(rag): 统一检索阈值重排降级与缓存语义	2026-07-21 09:34:56 +08:00
evo	a6a55202a3	fix(rag): 修复文本分片边界与字面量分隔符	2026-07-21 09:34:47 +08:00
ageerle@163.com	24bee53f9e	feat: 新增 ChitChatAgent 闲聊兜底子 Agent 并接入 supervisor 简单任务无专业子 Agent 可用时由闲聊 Agent 兜底，避免 supervisor 空转返回空内容；通过 supervisorContext 约束仅在问候/闲聊场景路由到该 Agent。 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-20 16:08:48 +08:00
evo	afc9d3d17d	fix: 修复本地启动、数据库初始化与构建问题 (#314 ) * fix: 修复本地启动、数据库初始化与构建问题 * fix: 修复pr的一些问题提交	2026-07-19 13:42:43 +08:00
evo	97ce15d116	fix: 修复pr的一些问题提交	2026-07-19 13:30:09 +08:00
evo	879fe48945	fix: 修复本地启动、数据库初始化与构建问题	2026-07-19 12:20:22 +08:00
ageerle@163.com	5d834d924a	feat: 编程助手按聊天模型过滤并补充 MCP 工具 thinking 事件，README 补充 copilot/uniapp 仓库 - CodingController.models 按 category=chat 过滤，编程对话只展示聊天模型 - 各 MCP 文件/命令工具在执行前推送 thinking 提示事件 - README/README_EN 项目源码表新增 ruoyi-copilot、ruoyi-uniapp 三端链接 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-17 14:47:18 +08:00
ageerle@163.com	fece90b307	feat: 新增短剧音频/编码模块、MCP 文件工具与 WebSocket 支持 - 短剧: 新增 ShortDramaAudio 实体/Mapper/BO/VO，扩展 ShortDramaServiceImpl 合成逻辑与 FfmpegFilterGraphBuilder 滤镜图 - MCP: 新增 WriteFileTool/DeleteFileTool/ExecuteCommandTool，重构 EditFileTool/ReadFileTool/ListDirectoryTool - 编码: 新增 coding 模块（CodingAgent/WorkspaceService/SSE 事件通道） - Atlas: 新增音频生成实现，扩展音视频/媒体实体与预测服务 - WebSocket: 新增公众号聊天 WebSocket 处理器与握手拦截 - 忽略 logs/ 目录，避免合成产物入库 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-17 11:52:53 +08:00
ageerle@163.com	06d110ed16	@docs: 修正 snailjob 注释里失效的 ry_job.sql 引用实际建表脚本在 docs/script/sql/ruoyi-ai-v3_mysql8.sql（sj_ 前缀表），仓库中并无 ry_job.sql。关联 issue #311。 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-15 18:25:55 +08:00
ageerle@163.com	dfcadda2bb	@style: 修正 QdrantVectorStoreStrategy 缩进为空格 createSchema 调用与文件其余代码保持 4 空格缩进统一，避免 checkstyle/spotless 报错。 Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-15 18:00:07 +08:00
Jack Jiang	3c9546ded9	fix: 修复 Qdrant 初始化创建集合问题 (#298 )	2026-07-15 17:58:12 +08:00
Octopus	a3d82e092e	Refresh MiniMax models and protocol support (#313 ) Co-authored-by: octo-patch <266937838+octo-patch@users.noreply.github.com>	2026-07-15 17:43:51 +08:00
Obltv	e925050207	feat: 新增通用链路追踪模块与 RAG 对话全链路埋点 - 新增 ruoyi-common-trace 模块：TraceContext 上下文、TraceNodeAspect 注解切面、数据库双表持久化 - ChatServiceFacade / KnowledgeRetrievalServiceImpl 完成 RAG 对话 retrieval → rerank → llm-call 全链路采集 - 新增 TraceController 提供列表/详情/节点查询 API 及数据统计 - 支持 trace.enabled 开关、payload 长度截断、错误安全降级 - TraceNodeTemplate 模板封装标准节点生命周期，减少重复样板代码	2026-06-16 10:14:35 +08:00