Merge branch 'feat/selection-assistant-mac-version' into feat/1.5.0-rc.2

feat(SelectionToolbar): enhance styling and layout of selection toolbar

.editorconfig

@@ -1,9 +1,9 @@
-root = true
-
-[*]
-charset = utf-8
-indent_style = space
-indent_size = 2
-end_of_line = lf
-insert_final_newline = true
-trim_trailing_whitespace = true
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 2
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true

.env.example

@@ -1,8 +0,0 @@
-NODE_OPTIONS=--max-old-space-size=8000
-API_KEY="sk-xxx"
-BASE_URL="https://api.siliconflow.cn/v1/"
-MODEL="Qwen/Qwen3-235B-A22B-Instruct-2507"
-CSLOGGER_MAIN_LEVEL=info
-CSLOGGER_RENDERER_LEVEL=info
-#CSLOGGER_MAIN_SHOW_MODULES=
-#CSLOGGER_RENDERER_SHOW_MODULES=

.git-blame-ignore-revs

@@ -1,2 +0,0 @@
-# ignore #7923 eol change and code formatting
-4ac8a388347ff35f34de42c3ef4a2f81f03fb3b1

.gitattributes

@@ -1,3 +1,2 @@
-* text=auto eol=lf
 /.yarn/**            linguist-vendored
 /.yarn/releases/*    binary

.github/CODEOWNERS

@@ -1,6 +0,0 @@
-/src/renderer/src/store/ @0xfullex
-/src/renderer/src/databases/ @0xfullex
-/src/main/services/ConfigManager.ts @0xfullex
-/packages/shared/IpcChannel.ts @0xfullex
-/src/main/ipc.ts @0xfullex
-/app-upgrade-config.json @kangfenmao

.github/ISSUE_TEMPLATE/#0_bug_report.yml

@@ -0,0 +1,92 @@
+name: 🐛 错误报告 (中文)
+description: 创建一个报告以帮助我们改进
+title: '[错误]: '
+labels: ['kind/bug']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        感谢您花时间填写此错误报告！
+        在提交此问题之前，请确保您已经了解了[常见问题](https://docs.cherry-ai.com/question-contact/questions)和[知识科普](https://docs.cherry-ai.com/question-contact/knowledge)
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: 提交前检查
+      description: |
+        在提交 Issue 前请确保您已经完成了以下所有步骤
+      options:
+        - label: 我理解 Issue 是用于反馈和解决问题的，而非吐槽评论区，将尽可能提供更多信息帮助问题解决。
+          required: true
+        - label: 我的问题不是 [常见问题](https://github.com/CherryHQ/cherry-studio/issues/3881) 中的内容。
+          required: true
+        - label: 我已经查看了 **置顶 Issue** 并搜索了现有的 [开放Issue](https://github.com/CherryHQ/cherry-studio/issues)和[已关闭Issue](https://github.com/CherryHQ/cherry-studio/issues?q=is%3Aissue%20state%3Aclosed%20)，没有找到类似的问题。
+          required: true
+        - label: 我填写了简短且清晰明确的标题，以便开发者在翻阅 Issue 列表时能快速确定大致问题。而不是“一个建议”、“卡住了”等。
+          required: true
+
+  - type: dropdown
+    id: platform
+    attributes:
+      label: 平台
+      description: 您正在使用哪个平台？
+      options:
+        - Windows
+        - macOS
+        - Linux
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: 版本
+      description: 您正在运行的 Cherry Studio 版本是什么？
+      placeholder: 例如 v1.0.0
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: 错误描述
+      description: 描述问题时请尽可能详细。请尽可能提供截图或屏幕录制，以帮助我们更好地理解问题。
+      placeholder: 告诉我们发生了什么...(记得附上截图/录屏，如果适用)
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: 重现步骤
+      description: 提供详细的重现步骤，以便于我们的开发人员可以准确地重现问题。请尽可能为每个步骤提供截图或屏幕录制。
+      placeholder: |
+        1. 转到 '...'
+        2. 点击 '....'
+        3. 向下滚动到 '....'
+        4. 看到错误
+
+        记得尽可能为每个步骤附上截图/录屏！
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: 预期行为
+      description: 清晰简洁地描述您期望发生的事情
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: 相关日志输出
+      description: 请复制并粘贴任何相关的日志输出
+      render: shell
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: 附加信息
+      description: 任何能让我们对你所遇到的问题有更多了解的东西

.github/ISSUE_TEMPLATE/#1_feature_request.yml

@@ -0,0 +1,76 @@
+name: 💡 功能建议 (中文)
+description: 为项目提出新的想法
+title: '[功能]: '
+labels: ['kind/enhancement']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        感谢您花时间提出新的功能建议!
+        在提交此问题之前，请确保您已经了解了[项目规划](https://docs.cherry-ai.com/cherrystudio/planning)和[功能介绍](https://docs.cherry-ai.com/cherrystudio/preview)
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: 提交前检查
+      description: |
+        在提交 Issue 前请确保您已经完成了以下所有步骤
+      options:
+        - label: 我理解 Issue 是用于反馈和解决问题的，而非吐槽评论区，将尽可能提供更多信息帮助问题解决。
+          required: true
+        - label: 我已经查看了置顶 Issue 并搜索了现有的 [开放Issue](https://github.com/CherryHQ/cherry-studio/issues)和[已关闭Issue](https://github.com/CherryHQ/cherry-studio/issues?q=is%3Aissue%20state%3Aclosed%20)，没有找到类似的建议。
+          required: true
+        - label: 我填写了简短且清晰明确的标题，以便开发者在翻阅 Issue 列表时能快速确定大致问题。而不是“一个建议”、“卡住了”等。
+          required: true
+        - label: 最新的 Cherry Studio 版本没有实现我所提出的功能。
+          required: true
+
+  - type: dropdown
+    id: platform
+    attributes:
+      label: 平台
+      description: 您正在使用哪个平台？
+      options:
+        - Windows
+        - macOS
+        - Linux
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: 版本
+      description: 您正在运行的 Cherry Studio 版本是什么？
+      placeholder: 例如 v1.0.0
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: 您的功能建议是否与某个问题/issue相关?
+      description: 请简明扼要地描述您遇到的问题
+      placeholder: 我总是感到沮丧,因为...
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: 请描述您希望实现的解决方案
+      description: 请简明扼要地描述您希望发生的情况
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: 请描述您考虑过的其他方案
+      description: 请简明扼要地描述您考虑过的任何其他解决方案或功能
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: 其他补充信息
+      description: 在此添加任何其他与功能建议相关的上下文或截图

.github/ISSUE_TEMPLATE/#2_question.yml

@@ -0,0 +1,77 @@
+name: ❓ 提问 & 讨论 (中文)
+description: 寻求帮助、讨论问题、提出疑问等...
+title: '[讨论]: '
+labels: ['kind/question']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        感谢您的提问！请尽可能详细地描述您的问题，这样我们才能更好地帮助您。
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Issue 检查清单
+      description: |
+        在提交 Issue 前请确保您已经完成了以下所有步骤
+      options:
+        - label: 我理解 Issue 是用于反馈和解决问题的，而非吐槽评论区，将尽可能提供更多信息帮助问题解决。
+          required: true
+        - label: 我确认自己需要的是提出问题并且讨论问题，而不是 Bug 反馈或需求建议。
+          required: true
+
+  - type: dropdown
+    id: platform
+    attributes:
+      label: 平台
+      description: 您正在使用哪个平台？
+      options:
+        - Windows
+        - macOS
+        - Linux
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: 版本
+      description: 您正在运行的 Cherry Studio 版本是什么？
+      placeholder: 例如 v1.0.0
+    validations:
+      required: true
+
+  - type: textarea
+    id: question
+    attributes:
+      label: 您的问题
+      description: 请详细描述您的问题
+      placeholder: 请尽可能清楚地说明您的问题...
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: 相关背景
+      description: 请提供一些背景信息，帮助我们更好地理解您的问题
+      placeholder: 例如：使用场景、已尝试的解决方案等
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: 补充信息
+      description: 任何其他相关的信息、截图或代码示例
+      render: shell
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: 优先级
+      description: 这个问题对您来说有多紧急？
+      options:
+        - 低 (有空再看)
+        - 中 (希望尽快得到答复)
+        - 高 (阻碍工作进行)
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/#3_others.yml

@@ -0,0 +1,76 @@
+name: 🤔 其他问题 (中文)
+description: 提交不属于错误报告或功能需求的问题
+title: '[其他]: '
+body:
+  - type: markdown
+    attributes:
+      value: |
+        感谢您花时间提出问题！
+        在提交此问题之前，请确保您已经了解了[常见问题](https://docs.cherry-ai.com/question-contact/questions)和[知识科普](https://docs.cherry-ai.com/question-contact/knowledge)
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: 提交前检查
+      description: |
+        在提交 Issue 前请确保您已经完成了以下所有步骤
+      options:
+        - label: 我理解 Issue 是用于反馈和解决问题的，而非吐槽评论区，将尽可能提供更多信息帮助问题解决。
+          required: true
+        - label: 我已经查看了置顶 Issue 并搜索了现有的 [开放Issue](https://github.com/CherryHQ/cherry-studio/issues)和[已关闭Issue](https://github.com/CherryHQ/cherry-studio/issues?q=is%3Aissue%20state%3Aclosed%20)，没有找到类似的问题。
+          required: true
+        - label: 我填写了简短且清晰明确的标题，以便开发者在翻阅 Issue 列表时能快速确定大致问题。而不是"一个问题"、"求助"等。
+          required: true
+        - label: 我的问题不属于错误报告或功能需求类别。
+          required: true
+
+  - type: dropdown
+    id: platform
+    attributes:
+      label: 平台
+      description: 您正在使用哪个平台？
+      options:
+        - Windows
+        - macOS
+        - Linux
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: 版本
+      description: 您正在运行的 Cherry Studio 版本是什么？
+      placeholder: 例如 v1.0.0
+    validations:
+      required: true
+
+  - type: textarea
+    id: question
+    attributes:
+      label: 问题描述
+      description: 请详细描述您的问题或疑问
+      placeholder: 我想了解有关...的更多信息
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: 相关背景
+      description: 请提供与您的问题相关的任何背景信息或上下文
+      placeholder: 我尝试实现...时遇到了疑问
+    validations:
+      required: true
+
+  - type: textarea
+    id: attempts
+    attributes:
+      label: 您已尝试的方法
+      description: 请描述您为解决问题已经尝试过的方法（如果有）
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: 附加信息
+      description: 任何能让我们对您的问题有更多了解的信息，包括截图或相关链接

.github/ISSUE_TEMPLATE/0_bug_report.yml

@@ -1,7 +1,7 @@
-name: 🐛 Bug Report
+name: 🐛 Bug Report (English)
 description: Create a report to help us improve
 title: '[Bug]: '
-labels: ['BUG']
+labels: ['kind/bug']
 body:
   - type: markdown
     attributes:
@@ -24,8 +24,6 @@ body:
           required: true
         - label: I've filled in short, clear headings so that developers can quickly identify a rough idea of what to expect when flipping through the list of issues. And not "a suggestion", "stuck", etc.
           required: true
-        - label: I've confirmed that I am using the latest version of Cherry Studio.
-          required: true
 
   - type: dropdown
     id: platform

.github/ISSUE_TEMPLATE/1_feature_request.yml

@@ -1,7 +1,7 @@
-name: 💡 Feature Request
+name: 💡 Feature Request (English)
 description: Suggest an idea for this project
 title: '[Feature]: '
-labels: ['feature']
+labels: ['kind/enhancement']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/2_question.yml

@@ -1,7 +1,7 @@
 name: ❓ Questions & Discussion
 description: Seeking help, discussing issues, asking questions, etc...
 title: '[Discussion]: '
-labels: ['discussion', 'help wanted']
+labels: ['kind/question']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/3_others.yml

@@ -1,4 +1,4 @@
-name: 🤔 Other Questions
+name: 🤔 Other Questions (English)
 description: Submit questions that don't fit into bug reports or feature requests
 title: '[Other]: '
 body:
@@ -73,4 +73,4 @@ body:
     id: additional
     attributes:
       label: Additional Information
-      description: Any other information that could help us better understand your question, including screenshots or relevant links
+      description: Any other information that could help us better understand your question, including screenshots or relevant links

.github/dependabot.yml

@@ -1,17 +1,86 @@
 version: 2
 updates:
-  - package-ecosystem: 'github-actions'
-    directory: '/'
+  - package-ecosystem: "npm"
+    directory: "/"
     schedule:
-      interval: 'monthly'
+      interval: "monthly"
+    open-pull-requests-limit: 7
+    target-branch: "main"
+    commit-message:
+      prefix: "chore"
+      include: "scope"
+    groups:
+      # 核心框架
+      core-framework:
+        patterns:
+          - "react"
+          - "react-dom"
+          - "electron"
+          - "typescript"
+          - "@types/react*"
+          - "@types/node"
+        update-types:
+          - "minor"
+          - "patch"
+
+      # Electron 生态和构建工具
+      electron-build:
+        patterns:
+          - "electron-*"
+          - "@electron*"
+          - "vite"
+          - "@vitejs/*"
+          - "dotenv-cli"
+          - "rollup-plugin-*"
+          - "@swc/*"
+        update-types:
+          - "minor"
+          - "patch"
+
+      # 测试工具
+      testing-tools:
+        patterns:
+          - "vitest"
+          - "@vitest/*"
+          - "playwright"
+          - "@playwright/*"
+          - "eslint*"
+          - "@eslint*"
+          - "prettier"
+          - "husky"
+          - "lint-staged"
+        update-types:
+          - "minor"
+          - "patch"
+
+      # CherryStudio 自定义包
+      cherrystudio-packages:
+        patterns:
+          - "@cherrystudio/*"
+        update-types:
+          - "minor"
+          - "patch"
+
+      # 兜底其他 dependencies
+      other-dependencies:
+        dependency-type: "production"
+
+      # 兜底其他 devDependencies
+      other-dev-dependencies:
+        dependency-type: "development"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
     open-pull-requests-limit: 3
     commit-message:
-      prefix: 'ci'
-      include: 'scope'
+      prefix: "ci"
+      include: "scope"
     groups:
       github-actions:
         patterns:
-          - '*'
+          - "*"
         update-types:
-          - 'minor'
-          - 'patch'
+          - "minor"
+          - "patch"

.github/issue-checker.yml

@@ -0,0 +1,252 @@
+default-mode:
+  add:
+  remove: [pull_request_target, issues]
+
+labels:
+  # <!-- [Ss]kip `LABEL` --> 跳过一个 label
+  # <!-- [Rr]emove `LABEL` --> 去掉一个 label
+
+  # skips and removes
+  - name: skip all
+    content:
+    regexes: "[Ss]kip (?:[Aa]ll |)[Ll]abels?"
+  - name: remove all
+    content:
+    regexes: "[Rr]emove (?:[Aa]ll |)[Ll]abels?"
+
+  - name: skip kind/bug
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)kind/bug(?:`|)"
+  - name: remove kind/bug
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)kind/bug(?:`|)"
+
+  - name: skip kind/enhancement
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)kind/enhancement(?:`|)"
+  - name: remove kind/enhancement
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)kind/enhancement(?:`|)"
+
+  - name: skip kind/question
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)kind/question(?:`|)"
+  - name: remove kind/question
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)kind/question(?:`|)"
+
+  - name: skip area/Connectivity
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)area/Connectivity(?:`|)"
+  - name: remove area/Connectivity
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)area/Connectivity(?:`|)"
+
+  - name: skip area/UI/UX
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)area/UI/UX(?:`|)"
+  - name: remove area/UI/UX
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)area/UI/UX(?:`|)"
+
+  - name: skip kind/documentation
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)kind/documentation(?:`|)"
+  - name: remove kind/documentation
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)kind/documentation(?:`|)"
+
+  - name: skip client:linux
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)client:linux(?:`|)"
+  - name: remove client:linux
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)client:linux(?:`|)"
+
+  - name: skip client:mac
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)client:mac(?:`|)"
+  - name: remove client:mac
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)client:mac(?:`|)"
+
+  - name: skip client:win
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)client:win(?:`|)"
+  - name: remove client:win
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)client:win(?:`|)"
+  
+  - name: skip sig/Assistant
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)sig/Assistant(?:`|)"
+  - name: remove sig/Assistant
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)sig/Assistant(?:`|)"
+
+  - name: skip sig/Data
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)sig/Data(?:`|)"
+  - name: remove sig/Data
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)sig/Data(?:`|)"
+
+  - name: skip sig/MCP
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)sig/MCP(?:`|)"
+  - name: remove sig/MCP
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)sig/MCP(?:`|)"
+
+  - name: skip sig/RAG
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)sig/RAG(?:`|)"
+  - name: remove sig/RAG
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)sig/RAG(?:`|)"
+
+  - name: skip lgtm
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)lgtm(?:`|)"
+  - name: remove lgtm
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)lgtm(?:`|)"
+
+  - name: skip License
+    content:
+    regexes: "[Ss]kip (?:[Ll]abels? |)(?:`|)License(?:`|)"
+  - name: remove License
+    content:
+    regexes: "[Rr]emove (?:[Ll]abels? |)(?:`|)License(?:`|)"
+
+  # `Dev Team`
+  - name: Dev Team
+    mode:
+      add: [pull_request_target, issues]
+    author_association:
+      - COLLABORATOR
+
+  # Area labels
+  - name: area/Connectivity
+    content: area/Connectivity
+    regexes: "代理|[Pp]roxy"
+    skip-if:
+      - skip all
+      - skip area/Connectivity
+    remove-if:
+      - remove all
+      - remove area/Connectivity
+
+  - name: area/UI/UX
+    content: area/UI/UX
+    regexes: "界面|[Uu][Ii]|重叠|按钮|图标|组件|渲染|菜单|栏目|头像|主题|样式|[Cc][Ss][Ss]"
+    skip-if:
+      - skip all
+      - skip area/UI/UX
+    remove-if:
+      - remove all
+      - remove area/UI/UX
+
+  # Kind labels
+  - name: kind/documentation
+    content: kind/documentation
+    regexes: "文档|教程|[Dd]oc(s|umentation)|[Rr]eadme"
+    skip-if:
+      - skip all
+      - skip kind/documentation
+    remove-if:
+      - remove all
+      - remove kind/documentation
+
+  # Client labels
+  - name: client:linux
+    content: client:linux
+    regexes: "(?:[Ll]inux|[Uu]buntu|[Dd]ebian)"
+    skip-if:
+      - skip all
+      - skip client:linux
+    remove-if:
+      - remove all
+      - remove client:linux
+
+  - name: client:mac
+    content: client:mac
+    regexes: "(?:[Mm]ac|[Mm]acOS|[Oo]SX)"
+    skip-if:
+      - skip all
+      - skip client:mac
+    remove-if:
+      - remove all
+      - remove client:mac
+
+  - name: client:win
+    content: client:win
+    regexes: "(?:[Ww]in|[Ww]indows)"
+    skip-if:
+      - skip all
+      - skip client:win
+    remove-if:
+      - remove all
+      - remove client:win
+
+  # SIG labels
+  - name: sig/Assistant
+    content: sig/Assistant
+    regexes: "快捷助手|[Aa]ssistant"
+    skip-if:
+      - skip all
+      - skip sig/Assistant
+    remove-if:
+      - remove all
+      - remove sig/Assistant
+
+  - name: sig/Data
+    content: sig/Data
+    regexes: "[Ww]ebdav|坚果云|备份|同步|数据|Obsidian|Notion|Joplin|思源"
+    skip-if:
+      - skip all
+      - skip sig/Data
+    remove-if:
+      - remove all
+      - remove sig/Data
+
+  - name: sig/MCP
+    content: sig/MCP
+    regexes: "[Mm][Cc][Pp]"
+    skip-if:
+      - skip all
+      - skip sig/MCP
+    remove-if:
+      - remove all
+      - remove sig/MCP
+
+  - name: sig/RAG
+    content: sig/RAG
+    regexes: "知识库|[Rr][Aa][Gg]"
+    skip-if:
+      - skip all
+      - skip sig/RAG
+    remove-if:
+      - remove all
+      - remove sig/RAG
+
+  # Other labels
+  - name: lgtm
+    content: lgtm
+    regexes: "(?:[Ll][Gg][Tt][Mm]|[Ll]ooks [Gg]ood [Tt]o [Mm]e)"
+    skip-if:
+      - skip all
+      - skip lgtm
+    remove-if:
+      - remove all
+      - remove lgtm
+
+  - name: License
+    content: License
+    regexes: "(?:[Ll]icense|[Cc]opyright|[Mm][Ii][Tt]|[Aa]pache)"
+    skip-if:
+      - skip all
+      - skip License
+    remove-if:
+      - remove all
+      - remove License

.github/pull_request_template.md

@@ -3,18 +3,6 @@
 1. Consider creating this PR as draft: https://github.com/CherryHQ/cherry-studio/blob/main/CONTRIBUTING.md
 -->
 
-<!--
-
-⚠️ Important: Redux/IndexedDB Data-Changing Feature PRs Temporarily On Hold ⚠️
-
-Please note: For our current development cycle, we are not accepting feature Pull Requests that introduce changes to Redux data models or IndexedDB schemas.
-
-While we value your contributions, PRs of this nature will be blocked without merge. We welcome all other contributions (bug fixes, perf enhancements, docs, etc.). Thank you!
-
-Once version 2.0.0 is released, we will resume reviewing feature PRs.
-
--->
-
 ### What this PR does
 
 Before this PR:

.github/workflows/auto-i18n.yml

@@ -1,93 +0,0 @@
-name: Auto I18N Weekly
-
-env:
-  TRANSLATION_API_KEY: ${{ secrets.TRANSLATE_API_KEY }}
-  TRANSLATION_MODEL: ${{ vars.AUTO_I18N_MODEL || 'deepseek/deepseek-v3.1'}}
-  TRANSLATION_BASE_URL: ${{ vars.AUTO_I18N_BASE_URL || 'https://api.ppinfra.com/openai'}}
-  TRANSLATION_BASE_LOCALE: ${{ vars.AUTO_I18N_BASE_LOCALE || 'en-us'}}
-
-on:
-  schedule:
-    # Runs at 00:00 UTC every Sunday.
-    # This corresponds to 08:00 AM UTC+8 (Beijing time) every Sunday.
-    - cron: "0 0 * * 0"
-  workflow_dispatch:
-
-jobs:
-  auto-i18n:
-    runs-on: ubuntu-latest
-    name: Auto I18N
-    permissions:
-      contents: write
-      pull-requests: write
-
-    steps:
-      - name: 🐈‍⬛ Checkout
-        uses: actions/checkout@v5
-        with:
-          fetch-depth: 0
-
-      - name: 📦 Setting Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version: 22
-
-      - name: 📦 Install corepack
-        run: corepack enable && corepack prepare yarn@4.9.1 --activate
-
-      - name: 📂 Get yarn cache directory path
-        id: yarn-cache-dir-path
-        run: echo "dir=$(yarn config get cacheFolder)" >> $GITHUB_OUTPUT
-
-      - name: 💾 Cache yarn dependencies
-        uses: actions/cache@v4
-        with:
-          path: |
-            ${{ steps.yarn-cache-dir-path.outputs.dir }}
-            node_modules
-          key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-yarn-
-
-      - name: 📦 Install dependencies
-        run: |
-          yarn install
-
-      - name: 🏃‍♀️ Translate
-        run: yarn sync:i18n && yarn auto:i18n
-
-      - name: 🔍 Format
-        run: yarn format
-
-      - name: 🔍 Check for changes
-        id: git_status
-        run: |
-          # Check if there are any uncommitted changes
-          git reset -- package.json yarn.lock  # 不提交 package.json 和 yarn.lock 的更改
-          git diff --exit-code --quiet || echo "::set-output name=has_changes::true"
-          git status --porcelain
-
-      - name: 📅 Set current date for PR title
-        id: set_date
-        run: echo "CURRENT_DATE=$(date +'%b %d, %Y')" >> $GITHUB_ENV # e.g., "Jun 06, 2024"
-
-      - name: 🚀 Create Pull Request if changes exist
-        if: steps.git_status.outputs.has_changes == 'true'
-        uses: peter-evans/create-pull-request@v6
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }} # Use the built-in GITHUB_TOKEN for bot actions
-          commit-message: "feat(bot): Weekly automated script run"
-          title: "🤖 Weekly Auto I18N Sync: ${{ env.CURRENT_DATE }}"
-          body: |
-            This PR includes changes generated by the weekly auto i18n.
-            Review the changes before merging.
-
-            ---
-            _Generated by the automated weekly workflow_
-          branch: "auto-i18n-weekly-${{ github.run_id }}" # Unique branch name
-          base: "main" # Or 'develop', set your base branch
-          delete-branch: true # Delete the branch after merging or closing the PR
-
-      - name: 📢 Notify if no changes
-        if: steps.git_status.outputs.has_changes != 'true'
-        run: echo "Bot script ran, but no changes were detected. No PR created."

.github/workflows/claude-code-review.yml

@@ -1,56 +0,0 @@
-name: Claude Code Review
-
-on:
-  pull_request:
-    types: [opened]
-    # Optional: Only run on specific file changes
-    # paths:
-    #   - "src/**/*.ts"
-    #   - "src/**/*.tsx"
-    #   - "src/**/*.js"
-    #   - "src/**/*.jsx"
-
-jobs:
-  claude-review:
-    # Only trigger code review for PRs from the main repository due to upstream OIDC issues
-    # https://github.com/anthropics/claude-code-action/issues/542
-    if: |
-      (github.event.pull_request.head.repo.full_name == github.repository) &&
-      (github.event.pull_request.draft == false)
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      pull-requests: write
-      issues: read
-      id-token: write
-      actions: read
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v5
-        with:
-          fetch-depth: 1
-
-      - name: Run Claude Code Review
-        id: claude-review
-        uses: anthropics/claude-code-action@v1
-        with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-          prompt: |
-            Please review this pull request and provide feedback on:
-            - Code quality and best practices
-            - Potential bugs or issues
-            - Performance considerations
-            - Security concerns
-            - Test coverage
-
-            PR number: ${{ github.event.number }}
-            Repo: ${{ github.repository }}
-
-            Use the repository's CLAUDE.md for guidance on style and conventions. Be constructive and helpful in your feedback.
-
-            Use `gh pr comment` with your Bash tool to leave your review as a comment on the PR.
-
-          # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
-          # or https://docs.anthropic.com/en/docs/claude-code/sdk#command-line for available options
-          claude_args: '--allowed-tools "Bash(gh issue view:*),Bash(gh search:*),Bash(gh issue list:*),Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*),Bash(gh pr list:*)"'

.github/workflows/claude-translator.yml

@@ -1,112 +0,0 @@
-name: Claude Translator
-concurrency:
-  group: translator-${{ github.event.comment.id || github.event.issue.number || github.event.review.id }}
-  cancel-in-progress: false
-
-on:
-  issues:
-    types: [opened]
-  issue_comment:
-    types: [created, edited]
-  pull_request_review:
-    types: [submitted, edited]
-  pull_request_review_comment:
-    types: [created, edited]
-
-jobs:
-  translate:
-    if: |
-      (github.event_name == 'issues')
-      || (github.event_name == 'issue_comment' && github.event.sender.type != 'Bot')
-      || (
-        (github.event_name == 'pull_request_review' || github.event_name == 'pull_request_review_comment')
-        && github.event.sender.type != 'Bot'
-        && github.event.pull_request.head.repo.fork == false
-      )
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      issues: write # 编辑issues/comments
-      pull-requests: write
-      id-token: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v5
-        with:
-          fetch-depth: 1
-
-      - name: Run Claude for translation
-        uses: anthropics/claude-code-action@main
-        id: claude
-        with:
-          # Warning: Permissions should have been controlled by workflow permission.
-          # Now `contents: read` is safe for files, but we could make a fine-grained token to control it.
-          # See: https://github.com/anthropics/claude-code-action/blob/main/docs/security.md
-          github_token: ${{ secrets.TOKEN_GITHUB_WRITE }}
-          allowed_non_write_users: "*"
-          anthropic_api_key: ${{ secrets.CLAUDE_TRANSLATOR_APIKEY }}
-          claude_args: "--allowed-tools Bash(gh issue:*),Bash(gh api:repos/*/issues:*),Bash(gh api:repos/*/pulls/*/reviews/*),Bash(gh api:repos/*/pulls/comments/*)"
-          prompt: |
-            你是一个多语言翻译助手。你需要响应 GitHub Webhooks 中的以下四种事件：
-
-            - issues
-            - issue_comment
-            - pull_request_review
-            - pull_request_review_comment
-
-            请完成以下任务：
-
-            1. 获取当前事件的完整信息。
-
-               - 如果当前事件是 issues，就获取该 issues 的信息。
-               - 如果当前事件是 issue_comment，就获取该 comment 的信息。
-               - 如果当前事件是 pull_request_review，就获取该 review 的信息。
-               - 如果当前事件是 pull_request_review_comment，就获取该 comment 的信息。
-
-            2. 智能检测内容。
-
-                - 如果获取到的信息是已经遵循格式要求翻译过的内容，则检查翻译内容和原始内容是否匹配。若不匹配，则重新翻译一次令其匹配，并遵循格式要求；
-                - 如果获取到的信息是未翻译过的内容，检查其内容语言。若不是英文，则翻译成英文；
-                - 如果获取到的信息是部分翻译为英文的内容，则将其翻译为英文；
-                - 如果获取到的信息包含了对已翻译内容的引用，则将引用内容清理为仅含英文的内容。引用的内容不能够包含"This xxx was translated by Claude"和"Original Content`等内容。
-                - 如果获取到的信息包含了其他类型的引用，即对非 Claude 翻译的内容的引用，则直接照原样引用，不进行翻译。
-                - 如果获取到的信息是通过邮件回复的内容，则在翻译时应当将邮件内容的引用放到最后。在原始内容和翻译内容中只需要回复的内容本身，不要包含对邮件内容的引用。
-                - 如果获取到的信息本身不需要任何处理，则跳过任务。
-
-            3. 格式要求：
-
-               - 标题：英文翻译（如果非英文）
-               - 内容格式：
-                 > [!NOTE]
-                 > This issue/comment/review was translated by Claude.
-
-                 [翻译内容]
-
-                 ---
-                 <details>
-                 <summary>Original Content</summary>
-                 [原始内容]
-                 </details>
-
-            4. 使用gh工具更新：
-
-               - 根据环境信息中的Event类型选择正确的命令：
-                 - 如果 Event 是 'issues': gh issue edit [ISSUE_NUMBER] --title "[英文标题]" --body "[翻译内容 + 原始内容]"
-                 - 如果 Event 是 'issue_comment': gh api -X PATCH /repos/${{ github.repository }}/issues/comments/${{ github.event.comment.id }} -f body="[翻译内容 + 原始内容]"
-                 - 如果 Event 是 'pull_request_review': gh api -X PUT /repos/${{ github.repository }}/pulls/${{ github.event.pull_request.number }}/reviews/${{ github.event.review.id }} -f body="[翻译内容]"
-                 - 如果 Event 是 'pull_request_review_comment': gh api -X PATCH /repos/${{ github.repository }}/pulls/comments/${{ github.event.comment.id }} -f body="[翻译内容 + 原始内容]"
-
-            环境信息：
-            - Event: ${{ github.event_name }}
-            - Issue Number: ${{ github.event.issue.number }}
-            - Repository: ${{ github.repository }}
-            - (Review) Comment ID: ${{ github.event.comment.id || 'N/A' }}
-            - Pull Request Number: ${{ github.event.pull_request.number || 'N/A' }}
-            - Review ID: ${{ github.event.review.id || 'N/A' }}
-
-
-            使用以下命令获取完整信息：
-            gh issue view ${{ github.event.issue.number }} --json title,body,comments
-        env:
-          ANTHROPIC_BASE_URL: ${{ secrets.CLAUDE_TRANSLATOR_BASEURL }}

.github/workflows/claude.yml

@@ -1,60 +0,0 @@
-name: Claude Code
-
-on:
-  issue_comment:
-    types: [created]
-  pull_request_review_comment:
-    types: [created]
-  issues:
-    types: [opened]
-  pull_request_review:
-    types: [submitted]
-
-jobs:
-  claude:
-    if: |
-      (github.event_name == 'issue_comment'
-        && contains(github.event.comment.body, '@claude')
-        && contains(fromJSON('["COLLABORATOR","MEMBER","OWNER"]'), github.event.comment.author_association))
-      ||
-      (github.event_name == 'pull_request_review_comment'
-        && contains(github.event.comment.body, '@claude')
-        && contains(fromJSON('["COLLABORATOR","MEMBER","OWNER"]'), github.event.comment.author_association))
-      ||
-      (github.event_name == 'pull_request_review'
-        && contains(github.event.review.body, '@claude')
-        && contains(fromJSON('["COLLABORATOR","MEMBER","OWNER"]'), github.event.review.author_association))
-      ||
-      (github.event_name == 'issues'
-        && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude'))
-        && contains(fromJSON('["COLLABORATOR","MEMBER","OWNER"]'), github.event.issue.author_association))
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      pull-requests: read
-      issues: read
-      id-token: write
-      actions: read # Required for Claude to read CI results on PRs
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v5
-        with:
-          fetch-depth: 1
-
-      - name: Run Claude Code
-        id: claude
-        uses: anthropics/claude-code-action@v1
-        with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-
-          # This is an optional setting that allows Claude to read CI results on PRs
-          additional_permissions: |
-            actions: read
-
-          # Optional: Give a custom prompt to Claude. If this is not specified, Claude will perform the instructions specified in the comment that tagged it.
-          # prompt: 'Update the pull request description to include a summary of changes.'
-
-          # Optional: Add claude_args to customize behavior and configuration
-          # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
-          # or https://docs.anthropic.com/en/docs/claude-code/sdk#command-line for available options
-          # claude_args: '--model claude-opus-4-1-20250805 --allowed-tools Bash(gh pr:*)'

.github/workflows/delete-branch.yml

@@ -1,23 +0,0 @@
-name: Delete merged branch
-on:
-  pull_request:
-    types:
-      - closed
-
-jobs:
-  delete-branch:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-    if: github.event.pull_request.merged == true && github.event.pull_request.head.repo.full_name == github.repository
-    steps:
-      - name: Delete merged branch
-        uses: actions/github-script@v8
-        continue-on-error: true
-        with:
-          script: |
-            github.rest.git.deleteRef({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              ref: `heads/${context.payload.pull_request.head.ref}`,
-            })

.github/workflows/dispatch-docs-update.yml

@@ -1,27 +0,0 @@
-name: Dispatch Docs Update on Release
-
-on:
-  release:
-    types: [released]
-
-permissions:
-  contents: write
-
-jobs:
-  dispatch-docs-update:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Get Release Tag from Event
-        id: get-event-tag
-        shell: bash
-        run: |
-          # 从当前 Release 事件中获取 tag_name
-          echo "tag=${{ github.event.release.tag_name }}" >> $GITHUB_OUTPUT
-
-      - name: Dispatch update-download-version workflow to cherry-studio-docs
-        uses: peter-evans/repository-dispatch@v3
-        with:
-          token: ${{ secrets.REPO_DISPATCH_TOKEN }}
-          repository: CherryHQ/cherry-studio-docs
-          event-type: update-download-version
-          client-payload: '{"version": "${{ steps.get-event-tag.outputs.tag }}"}'

.github/workflows/github-issue-tracker.yml

@@ -1,187 +0,0 @@
-name: GitHub Issue Tracker with Feishu Notification
-
-on:
-  issues:
-    types: [opened]
-  schedule:
-    # Run every day at 8:30 Beijing Time (00:30 UTC)
-    - cron: "30 0 * * *"
-  workflow_dispatch:
-
-jobs:
-  process-new-issue:
-    if: github.event_name == 'issues'
-    runs-on: ubuntu-latest
-    permissions:
-      issues: write
-      contents: read
-      id-token: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Check Beijing Time
-        id: check_time
-        run: |
-          # Get current time in Beijing timezone (UTC+8)
-          BEIJING_HOUR=$(TZ='Asia/Shanghai' date +%H)
-          BEIJING_MINUTE=$(TZ='Asia/Shanghai' date +%M)
-
-          echo "Beijing Time: ${BEIJING_HOUR}:${BEIJING_MINUTE}"
-
-          # Check if time is between 00:00 and 08:30
-          if [ $BEIJING_HOUR -lt 8 ] || ([ $BEIJING_HOUR -eq 8 ] && [ $BEIJING_MINUTE -le 30 ]); then
-            echo "should_delay=true" >> $GITHUB_OUTPUT
-            echo "⏰ Issue created during quiet hours (00:00-08:30 Beijing Time)"
-            echo "Will schedule notification for 08:30"
-          else
-            echo "should_delay=false" >> $GITHUB_OUTPUT
-            echo "✅ Issue created during active hours, will notify immediately"
-          fi
-
-      - name: Add pending label if in quiet hours
-        if: steps.check_time.outputs.should_delay == 'true'
-        uses: actions/github-script@v7
-        with:
-          script: |
-            github.rest.issues.addLabels({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              issue_number: context.issue.number,
-              labels: ['pending-feishu-notification']
-            });
-
-      - name: Setup Node.js
-        if: steps.check_time.outputs.should_delay == 'false'
-        uses: actions/setup-node@v6
-        with:
-          node-version: 22
-
-      - name: Process issue with Claude
-        if: steps.check_time.outputs.should_delay == 'false'
-        uses: anthropics/claude-code-action@main
-        with:
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          allowed_non_write_users: "*"
-          anthropic_api_key: ${{ secrets.CLAUDE_TRANSLATOR_APIKEY }}
-          claude_args: "--allowed-tools Bash(gh issue:*),Bash(node scripts/feishu-notify.js)"
-          prompt: |
-            你是一个GitHub Issue自动化处理助手。请完成以下任务：
-
-            ## 当前Issue信息
-            - Issue编号：#${{ github.event.issue.number }}
-            - 标题：${{ github.event.issue.title }}
-            - 作者：${{ github.event.issue.user.login }}
-            - URL：${{ github.event.issue.html_url }}
-            - 内容：${{ github.event.issue.body }}
-            - 标签：${{ join(github.event.issue.labels.*.name, ', ') }}
-
-            ## 任务步骤
-
-            1. **分析并总结issue**
-               用中文（简体）提供简洁的总结（2-3句话），包括：
-               - 问题的主要内容
-               - 核心诉求
-               - 重要的技术细节
-
-            2. **发送飞书通知**
-               使用以下命令发送飞书通知（注意：ISSUE_SUMMARY需要用引号包裹）：
-               ```bash
-               ISSUE_URL="${{ github.event.issue.html_url }}" \
-               ISSUE_NUMBER="${{ github.event.issue.number }}" \
-               ISSUE_TITLE="${{ github.event.issue.title }}" \
-               ISSUE_AUTHOR="${{ github.event.issue.user.login }}" \
-               ISSUE_LABELS="${{ join(github.event.issue.labels.*.name, ',') }}" \
-               ISSUE_SUMMARY="<你生成的中文总结>" \
-               node scripts/feishu-notify.js
-               ```
-
-            ## 注意事项
-            - 总结必须使用简体中文
-            - ISSUE_SUMMARY 在传递给 node 命令时需要正确转义特殊字符
-            - 如果issue内容为空，也要提供一个简短的说明
-
-            请开始执行任务！
-        env:
-          ANTHROPIC_BASE_URL: ${{ secrets.CLAUDE_TRANSLATOR_BASEURL }}
-          FEISHU_WEBHOOK_URL: ${{ secrets.FEISHU_WEBHOOK_URL }}
-          FEISHU_WEBHOOK_SECRET: ${{ secrets.FEISHU_WEBHOOK_SECRET }}
-
-  process-pending-issues:
-    if: github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'
-    runs-on: ubuntu-latest
-    permissions:
-      issues: write
-      contents: read
-      id-token: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version: 22
-
-      - name: Process pending issues with Claude
-        uses: anthropics/claude-code-action@main
-        with:
-          anthropic_api_key: ${{ secrets.CLAUDE_TRANSLATOR_APIKEY }}
-          allowed_non_write_users: "*"
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          claude_args: "--allowed-tools Bash(gh issue:*),Bash(gh api:*),Bash(node scripts/feishu-notify.js)"
-          prompt: |
-            你是一个GitHub Issue自动化处理助手。请完成以下任务：
-
-            ## 任务说明
-            处理所有待发送飞书通知的GitHub Issues（标记为 `pending-feishu-notification` 的issues）
-
-            ## 步骤
-
-            1. **获取待处理的issues**
-               使用以下命令获取所有带 `pending-feishu-notification` 标签的issues：
-               ```bash
-               gh api repos/${{ github.repository }}/issues?labels=pending-feishu-notification&state=open
-               ```
-
-            2. **总结每个issue**
-               对于每个找到的issue，用中文提供简洁的总结（2-3句话），包括：
-               - 问题的主要内容
-               - 核心诉求
-               - 重要的技术细节
-
-            3. **发送飞书通知**
-               对于每个issue，使用以下命令发送飞书通知：
-               ```bash
-               ISSUE_URL="<issue的html_url>" \
-               ISSUE_NUMBER="<issue编号>" \
-               ISSUE_TITLE="<issue标题>" \
-               ISSUE_AUTHOR="<issue作者>" \
-               ISSUE_LABELS="<逗号分隔的标签列表，排除pending-feishu-notification>" \
-               ISSUE_SUMMARY="<你生成的中文总结>" \
-               node scripts/feishu-notify.js
-               ```
-
-            4. **移除标签**
-               成功发送后，使用以下命令移除 `pending-feishu-notification` 标签：
-               ```bash
-               gh api -X DELETE repos/${{ github.repository }}/issues/<issue编号>/labels/pending-feishu-notification
-               ```
-
-            ## 环境变量
-            - Repository: ${{ github.repository }}
-            - Feishu webhook URL和密钥已在环境变量中配置好
-
-            ## 注意事项
-            - 如果没有待处理的issues，输出提示信息后直接结束
-            - 处理多个issues时，每个issue之间等待2-3秒，避免API限流
-            - 如果某个issue处理失败，继续处理下一个，不要中断整个流程
-            - 所有总结必须使用中文（简体中文）
-
-            请开始执行任务！
-        env:
-          ANTHROPIC_BASE_URL: ${{ secrets.CLAUDE_TRANSLATOR_BASEURL }}
-          FEISHU_WEBHOOK_URL: ${{ secrets.FEISHU_WEBHOOK_URL }}
-          FEISHU_WEBHOOK_SECRET: ${{ secrets.FEISHU_WEBHOOK_SECRET }}

.github/workflows/issue-checker.yml

@@ -0,0 +1,25 @@
+name: "Issue Checker"
+
+on:
+  issues:
+    types: [opened, edited]
+  pull_request_target:
+    types: [opened, edited]
+  issue_comment:
+    types: [created, edited]
+
+permissions:
+  contents: read
+  issues: write
+  pull-requests: write
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: MaaAssistantArknights/issue-checker@v1.14
+        with:
+          repo-token: "${{ secrets.GITHUB_TOKEN }}"
+          configuration-path: .github/issue-checker.yml
+          not-before: 2022-08-05T00:00:00Z
+          include-title: 1

.github/workflows/issue-management.yml

@@ -1,8 +1,8 @@
-name: 'Stale Issue Management'
+name: "Stale Issue Management"
 
 on:
   schedule:
-    - cron: '0 0 * * *'
+    - cron: "0 0 * * *"
   workflow_dispatch:
 
 env:
@@ -21,39 +21,35 @@ jobs:
       contents: none
     steps:
       - name: Close needs-more-info issues
-        uses: actions/stale@v10
+        uses: actions/stale@v9
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
-          only-labels: 'needs-more-info'
+          only-labels: "needs-more-info"
           days-before-stale: ${{ env.daysBeforeStale }}
-          days-before-close: 0 # Close immediately after stale
-          stale-issue-label: 'inactive'
-          close-issue-label: 'closed:no-response'
-          exempt-all-milestones: true
-          exempt-all-assignees: true
+          days-before-close: 0  # Close immediately after stale
+          stale-issue-label: "inactive"
+          close-issue-label: "closed:no-response"
           stale-issue-message: |
-            This issue has been labeled as needing more information and has been inactive for ${{ env.daysBeforeStale }} days.
+            This issue has been labeled as needing more information and has been inactive for ${{ env.daysBeforeStale }} days. 
             It will be closed now due to lack of additional information.
-
+            
             该问题被标记为"需要更多信息"且已经 ${{ env.daysBeforeStale }} 天没有任何活动，将立即关闭。
           operations-per-run: 50
-          exempt-issue-labels: 'pending, Dev Team'
+          exempt-issue-labels: "pending, Dev Team"
           days-before-pr-stale: -1
           days-before-pr-close: -1
 
       - name: Close inactive issues
-        uses: actions/stale@v10
+        uses: actions/stale@v9
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           days-before-stale: ${{ env.daysBeforeStale }}
           days-before-close: ${{ env.daysBeforeClose }}
-          stale-issue-label: 'inactive'
-          exempt-all-milestones: true
-          exempt-all-assignees: true
+          stale-issue-label: "inactive"
           stale-issue-message: |
             This issue has been inactive for a prolonged period and will be closed automatically in ${{ env.daysBeforeClose }} days.
             该问题已长时间处于闲置状态，${{ env.daysBeforeClose }} 天后将自动关闭。
-          exempt-issue-labels: 'pending, Dev Team, kind/enhancement'
+          exempt-issue-labels: "pending, Dev Team, kind/enhancement"
           days-before-pr-stale: -1 # Completely disable stalling for PRs
           days-before-pr-close: -1 # Completely disable closing for PRs
 

.github/workflows/nightly-build.yml

@@ -3,7 +3,7 @@ name: Nightly Build
 on:
   workflow_dispatch:
   schedule:
-    - cron: "0 17 * * *" # 1:00 BJ Time
+    - cron: '0 17 * * *' # 1:00 BJ Time
 
 permissions:
   contents: write
@@ -51,14 +51,14 @@ jobs:
 
     steps:
       - name: Check out Git repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v4
         with:
           ref: main
 
       - name: Install Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v4
         with:
-          node-version: 22
+          node-version: 20
 
       - name: macos-latest dependencies fix
         if: matrix.os == 'macos-latest'
@@ -66,7 +66,7 @@ jobs:
           brew install python-setuptools
 
       - name: Install corepack
-        run: corepack enable && corepack prepare yarn@4.9.1 --activate
+        run: corepack enable && corepack prepare yarn@4.6.0 --activate
 
       - name: Get yarn cache directory path
         id: yarn-cache-dir-path
@@ -93,44 +93,37 @@ jobs:
       - name: Build Linux
         if: matrix.os == 'ubuntu-latest'
         run: |
-          sudo apt-get install -y rpm
+          yarn build:npm linux
           yarn build:linux
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          RENDERER_VITE_AIHUBMIX_SECRET: ${{ vars.RENDERER_VITE_AIHUBMIX_SECRET }}
           NODE_OPTIONS: --max-old-space-size=8192
-          MAIN_VITE_CHERRYAI_CLIENT_SECRET: ${{ secrets.MAIN_VITE_CHERRYAI_CLIENT_SECRET }}
-          MAIN_VITE_MINERU_API_KEY: ${{ secrets.MAIN_VITE_MINERU_API_KEY }}
-          RENDERER_VITE_AIHUBMIX_SECRET: ${{ secrets.RENDERER_VITE_AIHUBMIX_SECRET }}
-          RENDERER_VITE_PPIO_APP_SECRET: ${{ secrets.RENDERER_VITE_PPIO_APP_SECRET }}
 
       - name: Build Mac
         if: matrix.os == 'macos-latest'
         run: |
+          yarn build:npm mac
           yarn build:mac
         env:
           CSC_LINK: ${{ secrets.CSC_LINK }}
           CSC_KEY_PASSWORD: ${{ secrets.CSC_KEY_PASSWORD }}
-          APPLE_ID: ${{ secrets.APPLE_ID }}
-          APPLE_APP_SPECIFIC_PASSWORD: ${{ secrets.APPLE_APP_SPECIFIC_PASSWORD }}
-          APPLE_TEAM_ID: ${{ secrets.APPLE_TEAM_ID }}
+          APPLE_ID: ${{ vars.APPLE_ID }}
+          APPLE_APP_SPECIFIC_PASSWORD: ${{ vars.APPLE_APP_SPECIFIC_PASSWORD }}
+          APPLE_TEAM_ID: ${{ vars.APPLE_TEAM_ID }}
+          RENDERER_VITE_AIHUBMIX_SECRET: ${{ vars.RENDERER_VITE_AIHUBMIX_SECRET }}
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NODE_OPTIONS: --max-old-space-size=8192
-          MAIN_VITE_CHERRYAI_CLIENT_SECRET: ${{ secrets.MAIN_VITE_CHERRYAI_CLIENT_SECRET }}
-          MAIN_VITE_MINERU_API_KEY: ${{ secrets.MAIN_VITE_MINERU_API_KEY }}
-          RENDERER_VITE_AIHUBMIX_SECRET: ${{ secrets.RENDERER_VITE_AIHUBMIX_SECRET }}
-          RENDERER_VITE_PPIO_APP_SECRET: ${{ secrets.RENDERER_VITE_PPIO_APP_SECRET }}
 
       - name: Build Windows
         if: matrix.os == 'windows-latest'
         run: |
+          yarn build:npm windows
           yarn build:win
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          RENDERER_VITE_AIHUBMIX_SECRET: ${{ vars.RENDERER_VITE_AIHUBMIX_SECRET }}
           NODE_OPTIONS: --max-old-space-size=8192
-          MAIN_VITE_CHERRYAI_CLIENT_SECRET: ${{ secrets.MAIN_VITE_CHERRYAI_CLIENT_SECRET }}
-          MAIN_VITE_MINERU_API_KEY: ${{ secrets.MAIN_VITE_MINERU_API_KEY }}
-          RENDERER_VITE_AIHUBMIX_SECRET: ${{ secrets.RENDERER_VITE_AIHUBMIX_SECRET }}
-          RENDERER_VITE_PPIO_APP_SECRET: ${{ secrets.RENDERER_VITE_PPIO_APP_SECRET }}
 
       - name: Rename artifacts with nightly format
         shell: bash
@@ -208,7 +201,7 @@ jobs:
           echo "总计: $(find renamed-artifacts -type f | wc -l) 个文件"
 
       - name: Upload artifacts
-        uses: actions/upload-artifact@v5
+        uses: actions/upload-artifact@v4
         with:
           name: cherry-studio-nightly-${{ steps.date.outputs.date }}-${{ matrix.os }}
           path: renamed-artifacts/*
@@ -226,7 +219,7 @@ jobs:
         shell: bash
 
       - name: Download all artifacts
-        uses: actions/download-artifact@v5
+        uses: actions/download-artifact@v4
         with:
           path: all-artifacts
           merge-multiple: false

.github/workflows/pr-ci.yml

@@ -1,35 +1,27 @@
 name: Pull Request CI
 
-permissions:
-  contents: read
-
 on:
   workflow_dispatch:
   pull_request:
     branches:
       - main
       - develop
-      - v2
-    types: [ready_for_review, synchronize, opened]
 
 jobs:
   build:
     runs-on: ubuntu-latest
-    env:
-      PRCI: true
-    if: github.event.pull_request.draft == false
 
     steps:
       - name: Check out Git repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v4
 
       - name: Install Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v4
         with:
-          node-version: 22
+          node-version: 20
 
       - name: Install corepack
-        run: corepack enable && corepack prepare yarn@4.9.1 --activate
+        run: corepack enable && corepack prepare yarn@4.6.0 --activate
 
       - name: Get yarn cache directory path
         id: yarn-cache-dir-path
@@ -48,17 +40,8 @@ jobs:
       - name: Install Dependencies
         run: yarn install
 
+      - name: Build Check
+        run: yarn build:check
+
       - name: Lint Check
         run: yarn test:lint
-
-      - name: Format Check
-        run: yarn format:check
-
-      - name: Type Check
-        run: yarn typecheck
-
-      - name: i18n Check
-        run: yarn check:i18n
-
-      - name: Test
-        run: yarn test

.github/workflows/release.yml

@@ -4,9 +4,9 @@ on:
   workflow_dispatch:
     inputs:
       tag:
-        description: "Release tag (e.g. v1.0.0)"
+        description: 'Release tag (e.g. v1.0.0)'
         required: true
-        default: "v1.0.0"
+        default: 'v1.0.0'
   push:
     tags:
       - v*.*.*
@@ -25,7 +25,7 @@ jobs:
 
     steps:
       - name: Check out Git repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v4
         with:
           fetch-depth: 0
 
@@ -39,25 +39,13 @@ jobs:
             echo "tag=${GITHUB_REF#refs/tags/}" >> $GITHUB_OUTPUT
           fi
 
-      - name: Set package.json version
-        shell: bash
-        run: |
-          TAG="${{ steps.get-tag.outputs.tag }}"
-          VERSION="${TAG#v}"
-          npm version "$VERSION" --no-git-tag-version --allow-same-version
-
       - name: Install Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v4
         with:
-          node-version: 22
-
-      - name: macos-latest dependencies fix
-        if: matrix.os == 'macos-latest'
-        run: |
-          brew install python-setuptools
+          node-version: 20
 
       - name: Install corepack
-        run: corepack enable && corepack prepare yarn@4.9.1 --activate
+        run: corepack enable && corepack prepare yarn@4.6.0 --activate
 
       - name: Get yarn cache directory path
         id: yarn-cache-dir-path
@@ -79,46 +67,42 @@ jobs:
       - name: Build Linux
         if: matrix.os == 'ubuntu-latest'
         run: |
-          sudo apt-get install -y rpm
+          yarn build:npm linux
           yarn build:linux
 
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          RENDERER_VITE_AIHUBMIX_SECRET: ${{ vars.RENDERER_VITE_AIHUBMIX_SECRET }}
           NODE_OPTIONS: --max-old-space-size=8192
-          MAIN_VITE_CHERRYAI_CLIENT_SECRET: ${{ secrets.MAIN_VITE_CHERRYAI_CLIENT_SECRET }}
-          MAIN_VITE_MINERU_API_KEY: ${{ secrets.MAIN_VITE_MINERU_API_KEY }}
-          RENDERER_VITE_AIHUBMIX_SECRET: ${{ secrets.RENDERER_VITE_AIHUBMIX_SECRET }}
-          RENDERER_VITE_PPIO_APP_SECRET: ${{ secrets.RENDERER_VITE_PPIO_APP_SECRET }}
+          MAIN_VITE_MINERU_API_KEY: ${{ vars.MAIN_VITE_MINERU_API_KEY }}
 
       - name: Build Mac
         if: matrix.os == 'macos-latest'
         run: |
           sudo -H pip install setuptools
+          yarn build:npm mac
           yarn build:mac
         env:
           CSC_LINK: ${{ secrets.CSC_LINK }}
           CSC_KEY_PASSWORD: ${{ secrets.CSC_KEY_PASSWORD }}
-          APPLE_ID: ${{ secrets.APPLE_ID }}
-          APPLE_APP_SPECIFIC_PASSWORD: ${{ secrets.APPLE_APP_SPECIFIC_PASSWORD }}
-          APPLE_TEAM_ID: ${{ secrets.APPLE_TEAM_ID }}
+          APPLE_ID: ${{ vars.APPLE_ID }}
+          APPLE_APP_SPECIFIC_PASSWORD: ${{ vars.APPLE_APP_SPECIFIC_PASSWORD }}
+          APPLE_TEAM_ID: ${{ vars.APPLE_TEAM_ID }}
+          RENDERER_VITE_AIHUBMIX_SECRET: ${{ vars.RENDERER_VITE_AIHUBMIX_SECRET }}
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NODE_OPTIONS: --max-old-space-size=8192
-          MAIN_VITE_CHERRYAI_CLIENT_SECRET: ${{ secrets.MAIN_VITE_CHERRYAI_CLIENT_SECRET }}
-          MAIN_VITE_MINERU_API_KEY: ${{ secrets.MAIN_VITE_MINERU_API_KEY }}
-          RENDERER_VITE_AIHUBMIX_SECRET: ${{ secrets.RENDERER_VITE_AIHUBMIX_SECRET }}
-          RENDERER_VITE_PPIO_APP_SECRET: ${{ secrets.RENDERER_VITE_PPIO_APP_SECRET }}
+          MAIN_VITE_MINERU_API_KEY: ${{ vars.MAIN_VITE_MINERU_API_KEY }}
 
       - name: Build Windows
         if: matrix.os == 'windows-latest'
         run: |
+          yarn build:npm windows
           yarn build:win
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          RENDERER_VITE_AIHUBMIX_SECRET: ${{ vars.RENDERER_VITE_AIHUBMIX_SECRET }}
           NODE_OPTIONS: --max-old-space-size=8192
-          MAIN_VITE_CHERRYAI_CLIENT_SECRET: ${{ secrets.MAIN_VITE_CHERRYAI_CLIENT_SECRET }}
-          MAIN_VITE_MINERU_API_KEY: ${{ secrets.MAIN_VITE_MINERU_API_KEY }}
-          RENDERER_VITE_AIHUBMIX_SECRET: ${{ secrets.RENDERER_VITE_AIHUBMIX_SECRET }}
-          RENDERER_VITE_PPIO_APP_SECRET: ${{ secrets.RENDERER_VITE_PPIO_APP_SECRET }}
+          MAIN_VITE_MINERU_API_KEY: ${{ vars.MAIN_VITE_MINERU_API_KEY }}
 
       - name: Release
         uses: ncipollo/release-action@v1
@@ -127,5 +111,40 @@ jobs:
           allowUpdates: true
           makeLatest: false
           tag: ${{ steps.get-tag.outputs.tag }}
-          artifacts: "dist/*.exe,dist/*.zip,dist/*.dmg,dist/*.AppImage,dist/*.snap,dist/*.deb,dist/*.rpm,dist/*.tar.gz,dist/latest*.yml,dist/rc*.yml,dist/beta*.yml,dist/*.blockmap"
+          artifacts: 'dist/*.exe,dist/*.zip,dist/*.dmg,dist/*.AppImage,dist/*.snap,dist/*.deb,dist/*.rpm,dist/*.tar.gz,dist/latest*.yml,dist/rc*.yml,dist/*.blockmap'
           token: ${{ secrets.GITHUB_TOKEN }}
+
+  dispatch-docs-update:
+    needs: release
+    if: success() && github.repository == 'CherryHQ/cherry-studio' # 确保所有构建成功且在主仓库中运行
+    runs-on: ubuntu-latest
+    steps:
+      - name: Get release tag
+        id: get-tag
+        shell: bash
+        run: |
+          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
+            echo "tag=${{ github.event.inputs.tag }}" >> $GITHUB_OUTPUT
+          else
+            echo "tag=${GITHUB_REF#refs/tags/}" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Check if tag is pre-release
+        id: check-tag
+        shell: bash
+        run: |
+          TAG="${{ steps.get-tag.outputs.tag }}"
+          if [[ "$TAG" == *"rc"* || "$TAG" == *"pre-release"* ]]; then
+            echo "is_pre_release=true" >> $GITHUB_OUTPUT
+          else
+            echo "is_pre_release=false" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Dispatch update-download-version workflow to cherry-studio-docs
+        if: steps.check-tag.outputs.is_pre_release == 'false'
+        uses: peter-evans/repository-dispatch@v3
+        with:
+          token: ${{ secrets.REPO_DISPATCH_TOKEN }}
+          repository: CherryHQ/cherry-studio-docs
+          event-type: update-download-version
+          client-payload: '{"version": "${{ steps.get-tag.outputs.tag }}"}'

.github/workflows/update-app-upgrade-config.yml

@@ -1,212 +0,0 @@
-name: Update App Upgrade Config
-
-on:
-  release:
-    types:
-      - released
-      - prereleased
-  workflow_dispatch:
-    inputs:
-      tag:
-        description: "Release tag (e.g., v1.2.3)"
-        required: true
-        type: string
-      is_prerelease:
-        description: "Mark the tag as a prerelease when running manually"
-        required: false
-        default: false
-        type: boolean
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  propose-update:
-    runs-on: ubuntu-latest
-    if: github.event_name == 'workflow_dispatch' || (github.event_name == 'release' && github.event.release.draft == false)
-
-    steps:
-      - name: Check if should proceed
-        id: check
-        run: |
-          EVENT="${{ github.event_name }}"
-
-          if [ "$EVENT" = "workflow_dispatch" ]; then
-            TAG="${{ github.event.inputs.tag }}"
-          else
-            TAG="${{ github.event.release.tag_name }}"
-          fi
-
-          latest_tag=$(
-            curl -L \
-              -H "Accept: application/vnd.github+json" \
-              -H "Authorization: Bearer ${{ github.token }}" \
-              -H "X-GitHub-Api-Version: 2022-11-28" \
-              https://api.github.com/repos/${{ github.repository }}/releases/latest \
-              | jq -r '.tag_name'
-          )
-
-          if [ "$EVENT" = "workflow_dispatch" ]; then
-            MANUAL_IS_PRERELEASE="${{ github.event.inputs.is_prerelease }}"
-            if [ -z "$MANUAL_IS_PRERELEASE" ]; then
-              MANUAL_IS_PRERELEASE="false"
-            fi
-            if [ "$MANUAL_IS_PRERELEASE" = "true" ]; then
-              if ! echo "$TAG" | grep -E '(-beta([.-][0-9]+)?|-rc([.-][0-9]+)?)' >/dev/null; then
-                echo "Manual prerelease flag set but tag $TAG lacks beta/rc suffix. Skipping." >&2
-                echo "should_run=false" >> "$GITHUB_OUTPUT"
-                echo "is_prerelease=false" >> "$GITHUB_OUTPUT"
-                echo "latest_tag=$latest_tag" >> "$GITHUB_OUTPUT"
-                exit 0
-              fi
-            fi
-            echo "should_run=true" >> "$GITHUB_OUTPUT"
-            echo "is_prerelease=$MANUAL_IS_PRERELEASE" >> "$GITHUB_OUTPUT"
-            echo "latest_tag=$latest_tag" >> "$GITHUB_OUTPUT"
-            exit 0
-          fi
-
-          IS_PRERELEASE="${{ github.event.release.prerelease }}"
-
-          if [ "$IS_PRERELEASE" = "true" ]; then
-            if ! echo "$TAG" | grep -E '(-beta([.-][0-9]+)?|-rc([.-][0-9]+)?)' >/dev/null; then
-              echo "Release marked as prerelease but tag $TAG lacks beta/rc suffix. Skipping." >&2
-              echo "should_run=false" >> "$GITHUB_OUTPUT"
-              echo "is_prerelease=false" >> "$GITHUB_OUTPUT"
-              echo "latest_tag=$latest_tag" >> "$GITHUB_OUTPUT"
-              exit 0
-            fi
-            echo "should_run=true" >> "$GITHUB_OUTPUT"
-            echo "is_prerelease=true" >> "$GITHUB_OUTPUT"
-            echo "latest_tag=$latest_tag" >> "$GITHUB_OUTPUT"
-            echo "Release is prerelease, proceeding"
-            exit 0
-          fi
-
-          if [[ "${latest_tag}" == "$TAG" ]]; then
-            echo "should_run=true" >> "$GITHUB_OUTPUT"
-            echo "is_prerelease=false" >> "$GITHUB_OUTPUT"
-            echo "latest_tag=$latest_tag" >> "$GITHUB_OUTPUT"
-            echo "Release is latest, proceeding"
-          else
-            echo "should_run=false" >> "$GITHUB_OUTPUT"
-            echo "is_prerelease=false" >> "$GITHUB_OUTPUT"
-            echo "latest_tag=$latest_tag" >> "$GITHUB_OUTPUT"
-            echo "Release is neither prerelease nor latest, skipping"
-          fi
-
-      - name: Prepare metadata
-        id: meta
-        if: steps.check.outputs.should_run == 'true'
-        run: |
-          EVENT="${{ github.event_name }}"
-          LATEST_TAG="${{ steps.check.outputs.latest_tag }}"
-          if [ "$EVENT" = "release" ]; then
-            TAG="${{ github.event.release.tag_name }}"
-            PRE="${{ github.event.release.prerelease }}"
-
-            if [ -n "$LATEST_TAG" ] && [ "$LATEST_TAG" = "$TAG" ]; then
-              LATEST="true"
-            else
-              LATEST="false"
-            fi
-            TRIGGER="release"
-          else
-            TAG="${{ github.event.inputs.tag }}"
-            PRE="${{ github.event.inputs.is_prerelease }}"
-            if [ -z "$PRE" ]; then
-              PRE="false"
-            fi
-            if [ -n "$LATEST_TAG" ] && [ "$LATEST_TAG" = "$TAG" ] && [ "$PRE" != "true" ]; then
-              LATEST="true"
-            else
-              LATEST="false"
-            fi
-            TRIGGER="manual"
-          fi
-
-          SAFE_TAG=$(echo "$TAG" | sed 's/[^A-Za-z0-9._-]/-/g')
-          echo "tag=$TAG" >> "$GITHUB_OUTPUT"
-          echo "safe_tag=$SAFE_TAG" >> "$GITHUB_OUTPUT"
-          echo "prerelease=$PRE" >> "$GITHUB_OUTPUT"
-          echo "latest=$LATEST" >> "$GITHUB_OUTPUT"
-          echo "trigger=$TRIGGER" >> "$GITHUB_OUTPUT"
-
-      - name: Checkout default branch
-        if: steps.check.outputs.should_run == 'true'
-        uses: actions/checkout@v5
-        with:
-          ref: ${{ github.event.repository.default_branch }}
-          path: main
-          fetch-depth: 0
-
-      - name: Checkout x-files/app-upgrade-config branch
-        if: steps.check.outputs.should_run == 'true'
-        uses: actions/checkout@v5
-        with:
-          ref: x-files/app-upgrade-config
-          path: cs
-          fetch-depth: 0
-
-      - name: Setup Node.js
-        if: steps.check.outputs.should_run == 'true'
-        uses: actions/setup-node@v4
-        with:
-          node-version: 22
-
-      - name: Enable Corepack
-        if: steps.check.outputs.should_run == 'true'
-        run: corepack enable && corepack prepare yarn@4.9.1 --activate
-
-      - name: Install dependencies
-        if: steps.check.outputs.should_run == 'true'
-        working-directory: main
-        run: yarn install --immutable
-
-      - name: Update upgrade config
-        if: steps.check.outputs.should_run == 'true'
-        working-directory: main
-        env:
-          RELEASE_TAG: ${{ steps.meta.outputs.tag }}
-          IS_PRERELEASE: ${{ steps.check.outputs.is_prerelease }}
-        run: |
-          yarn tsx scripts/update-app-upgrade-config.ts \
-            --tag "$RELEASE_TAG" \
-            --config ../cs/app-upgrade-config.json \
-            --is-prerelease "$IS_PRERELEASE"
-
-      - name: Detect changes
-        if: steps.check.outputs.should_run == 'true'
-        id: diff
-        working-directory: cs
-        run: |
-          if git diff --quiet -- app-upgrade-config.json; then
-            echo "changed=false" >> "$GITHUB_OUTPUT"
-          else
-            echo "changed=true" >> "$GITHUB_OUTPUT"
-          fi
-
-      - name: Create pull request
-        if: steps.check.outputs.should_run == 'true' && steps.diff.outputs.changed == 'true'
-        uses: peter-evans/create-pull-request@v7
-        with:
-          path: cs
-          base: x-files/app-upgrade-config
-          branch: chore/update-app-upgrade-config/${{ steps.meta.outputs.safe_tag }}
-          commit-message: "🤖 chore: sync app-upgrade-config for ${{ steps.meta.outputs.tag }}"
-          title: "chore: update app-upgrade-config for ${{ steps.meta.outputs.tag }}"
-          body: |
-            Automated update triggered by `${{ steps.meta.outputs.trigger }}`.
-
-            - Source tag: `${{ steps.meta.outputs.tag }}`
-            - Pre-release: `${{ steps.meta.outputs.prerelease }}`
-            - Latest: `${{ steps.meta.outputs.latest }}`
-            - Workflow run: https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}
-          labels: |
-            automation
-            app-upgrade
-
-      - name: No changes detected
-        if: steps.check.outputs.should_run == 'true' && steps.diff.outputs.changed != 'true'
-        run: echo "No updates required for x-files/app-upgrade-config/app-upgrade-config.json"

.gitignore

@@ -35,41 +35,25 @@ Thumbs.db
 node_modules
 dist
 out
-mcp_server
 stats.html
-.eslintcache
 
 # ENV
 .env
 .env.*
-!.env.example
 
 # Local
 local
 .aider*
 .cursorrules
 .cursor/*
-.claude/*
-.gemini/*
-.qwen/*
-.trae/*
-.claude-code-router/*
-.codebuddy/*
-.zed/*
-CLAUDE.local.md
 
 # vitest
 coverage
 .vitest-cache
 vitest.config.*.timestamp-*
 
-# TypeScript incremental build
-.tsbuildinfo
-
 # playwright
 playwright-report
 test-results
 
 YOUR_MEMORY_FILE_PATH
-
-.sessions/

.oxlintrc.json

@@ -1,158 +0,0 @@
-{
-  "$schema": "./node_modules/oxlint/configuration_schema.json",
-  "categories": {},
-  "env": {
-    "es2022": true
-  },
-  "globals": {},
-  "ignorePatterns": [
-    "node_modules/**",
-    "build/**",
-    "dist/**",
-    "out/**",
-    "local/**",
-    "tests/**",
-    ".yarn/**",
-    ".gitignore",
-    "scripts/cloudflare-worker.js",
-    "src/main/integration/nutstore/sso/lib/**",
-    "src/main/integration/cherryai/index.js",
-    "src/main/integration/nutstore/sso/lib/**",
-    "src/renderer/src/ui/**",
-    "packages/**/dist",
-    "eslint.config.mjs"
-  ],
-  "overrides": [
-    {
-      "env": {
-        "node": true
-      },
-      "files": ["src/main/**", "resources/scripts/**", "scripts/**", "playwright.config.ts", "electron.vite.config.ts"]
-    },
-    {
-      "env": {
-        "browser": true
-      },
-      "files": [
-        "src/renderer/**/*.{ts,tsx}",
-        "packages/aiCore/**",
-        "packages/extension-table-plus/**"
-      ]
-    },
-    {
-      "env": {
-        "node": true,
-        "vitest": true
-      },
-      "files": ["**/__tests__/*.test.{ts,tsx}", "tests/**"]
-    },
-    {
-      "env": {
-        "browser": true,
-        "node": true
-      },
-      "files": ["src/preload/**"]
-    },
-    {
-      "files": ["packages/ai-sdk-provider/**"],
-      "globals": {
-        "fetch": "readonly"
-      }
-    }
-  ],
-  "plugins": ["unicorn", "typescript", "oxc", "import"],
-  "rules": {
-    "no-array-constructor": "off",
-    "no-caller": "warn",
-    "no-eval": "warn",
-    "no-fallthrough": "warn",
-    "no-unassigned-vars": "warn",
-    "no-unused-expressions": "off",
-    "no-unused-vars": ["warn", { "caughtErrors": "none" }],
-    "no-useless-rename": "warn",
-    "oxc/bad-array-method-on-arguments": "warn",
-    "oxc/bad-char-at-comparison": "warn",
-    "oxc/bad-comparison-sequence": "warn",
-    "oxc/bad-min-max-func": "warn",
-    "oxc/bad-object-literal-comparison": "warn",
-    "oxc/bad-replace-all-arg": "warn",
-    "oxc/const-comparisons": "warn",
-    "oxc/double-comparisons": "warn",
-    "oxc/erasing-op": "warn",
-    "oxc/missing-throw": "warn",
-    "oxc/number-arg-out-of-range": "warn",
-    "oxc/only-used-in-recursion": "off",
-    "oxc/uninvoked-array-callback": "warn",
-    "typescript/await-thenable": "warn",
-    "typescript/consistent-type-imports": "error",
-    "typescript/no-array-constructor": "error",
-    "typescript/no-array-delete": "warn",
-    "typescript/no-base-to-string": "warn",
-    "typescript/no-duplicate-enum-values": "error",
-    "typescript/no-duplicate-type-constituents": "warn",
-    "typescript/no-empty-object-type": "off",
-    "typescript/no-explicit-any": "off",
-    "typescript/no-extra-non-null-assertion": "error",
-    "typescript/no-floating-promises": "warn",
-    "typescript/no-for-in-array": "warn",
-    "typescript/no-implied-eval": "warn",
-    "typescript/no-meaningless-void-operator": "warn",
-    "typescript/no-misused-new": "error",
-    "typescript/no-misused-spread": "warn",
-    "typescript/no-namespace": "error",
-    "typescript/no-non-null-asserted-optional-chain": "off",
-    "typescript/no-redundant-type-constituents": "warn",
-    "typescript/no-require-imports": "off",
-    "typescript/no-this-alias": "error",
-    "typescript/no-unnecessary-parameter-property-assignment": "warn",
-    "typescript/no-unnecessary-type-constraint": "error",
-    "typescript/no-unsafe-declaration-merging": "error",
-    "typescript/no-unsafe-function-type": "error",
-    "typescript/no-unsafe-unary-minus": "warn",
-    "typescript/no-useless-empty-export": "warn",
-    "typescript/no-wrapper-object-types": "error",
-    "typescript/prefer-as-const": "error",
-    "typescript/prefer-namespace-keyword": "error",
-    "typescript/require-array-sort-compare": "warn",
-    "typescript/restrict-template-expressions": "warn",
-    "typescript/triple-slash-reference": "error",
-    "typescript/unbound-method": "warn",
-    "unicorn/no-await-in-promise-methods": "warn",
-    "unicorn/no-empty-file": "off",
-    "unicorn/no-invalid-fetch-options": "warn",
-    "unicorn/no-invalid-remove-event-listener": "warn",
-    "unicorn/no-new-array": "off",
-    "unicorn/no-single-promise-in-promise-methods": "warn",
-    "unicorn/no-thenable": "off",
-    "unicorn/no-unnecessary-await": "warn",
-    "unicorn/no-useless-fallback-in-spread": "warn",
-    "unicorn/no-useless-length-check": "warn",
-    "unicorn/no-useless-spread": "off",
-    "unicorn/prefer-set-size": "warn",
-    "unicorn/prefer-string-starts-ends-with": "warn"
-  },
-  "settings": {
-    "jsdoc": {
-      "augmentsExtendsReplacesDocs": false,
-      "exemptDestructuredRootsFromChecks": false,
-      "ignoreInternal": false,
-      "ignorePrivate": false,
-      "ignoreReplacesDocs": true,
-      "implementsReplacesDocs": false,
-      "overrideReplacesDocs": true,
-      "tagNamePreference": {}
-    },
-    "jsx-a11y": {
-      "attributes": {},
-      "components": {},
-      "polymorphicPropName": null
-    },
-    "next": {
-      "rootDir": []
-    },
-    "react": {
-      "formComponents": [],
-      "linkComponents": []
-    }
-  }
-}

.prettierignore

@@ -0,0 +1,9 @@
+out
+dist
+pnpm-lock.yaml
+LICENSE.md
+tsconfig.json
+tsconfig.*.json
+CHANGELOG*.md
+agents.json
+src/renderer/src/integration/nutstore/sso/lib

.prettierrc

@@ -0,0 +1,8 @@
+{
+  "singleQuote": true,
+  "semi": false,
+  "printWidth": 120,
+  "trailingComma": "none",
+  "endOfLine": "lf",
+  "bracketSameLine": true
+}

.vscode/extensions.json

@@ -1,11 +1,3 @@
 {
-  "recommendations": [
-    "dbaeumer.vscode-eslint",
-    "editorconfig.editorconfig",
-    "lokalise.i18n-ally",
-    "bradlc.vscode-tailwindcss",
-    "vitest.explorer",
-    "oxc.oxc-vscode",
-    "biomejs.biome"
-  ]
+  "recommendations": ["dbaeumer.vscode-eslint"]
 }

.vscode/launch.json

@@ -1,40 +1,39 @@
 {
-  "compounds": [
-    {
-      "configurations": ["Debug Main Process", "Debug Renderer Process"],
-      "name": "Debug All",
-      "presentation": {
-        "order": 1
-      }
-    }
-  ],
+  "version": "0.2.0",
   "configurations": [
     {
-      "cwd": "${workspaceRoot}",
-      "env": {
-        "REMOTE_DEBUGGING_PORT": "9222"
-      },
-      "envFile": "${workspaceFolder}/.env",
       "name": "Debug Main Process",
-      "request": "launch",
-      "runtimeArgs": ["--inspect", "--sourcemap"],
-      "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron-vite",
       "type": "node",
+      "request": "launch",
+      "cwd": "${workspaceRoot}",
+      "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron-vite",
       "windows": {
         "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron-vite.cmd"
+      },
+      "runtimeArgs": ["--sourcemap"],
+      "env": {
+        "REMOTE_DEBUGGING_PORT": "9222"
       }
     },
     {
       "name": "Debug Renderer Process",
       "port": 9222,
+      "request": "attach",
+      "type": "chrome",
+      "webRoot": "${workspaceFolder}/src/renderer",
+      "timeout": 60000,
       "presentation": {
         "hidden": true
-      },
-      "request": "attach",
-      "timeout": 3000000,
-      "type": "chrome",
-      "webRoot": "${workspaceFolder}/src/renderer"
+      }
     }
   ],
-  "version": "0.2.0"
+  "compounds": [
+    {
+      "name": "Debug All",
+      "configurations": ["Debug Main Process", "Debug Renderer Process"],
+      "presentation": {
+        "order": 1
+      }
+    }
+  ]
 }

.vscode/settings.json

@@ -1,55 +1,43 @@
 {
-  "[css]": {
-    "editor.defaultFormatter": "biomejs.biome"
-  },
-  "[javascript]": {
-    "editor.defaultFormatter": "biomejs.biome"
-  },
-  "[json]": {
-    "editor.defaultFormatter": "biomejs.biome"
-  },
-  "[jsonc]": {
-    "editor.defaultFormatter": "biomejs.biome"
-  },
-  "[markdown]": {
-    "files.trimTrailingWhitespace": false
-  },
-  "[scss]": {
-    "editor.defaultFormatter": "biomejs.biome"
-  },
-  "[typescript]": {
-    "editor.defaultFormatter": "biomejs.biome"
-  },
-  "[typescriptreact]": {
-    "editor.defaultFormatter": "biomejs.biome"
-  },
-  "editor.codeActionsOnSave": {
-    "source.fixAll.biome": "explicit",
-    "source.fixAll.eslint": "explicit",
-    "source.fixAll.oxc": "explicit",
-    "source.organizeImports": "never"
-  },
   "editor.formatOnSave": true,
-  "files.associations": {
-    "*.css": "tailwindcss"
+  "editor.codeActionsOnSave": {
+    "source.fixAll.eslint": "explicit"
   },
-  "files.eol": "\n",
-  // "i18n-ally.displayLanguage": "zh-cn", // 界面显示语言
-  "i18n-ally.enabledFrameworks": ["react-i18next", "i18next"],
-  "i18n-ally.enabledParsers": ["ts", "js", "json"], // 解析语言
-  "i18n-ally.fullReloadOnChanged": true,
-  "i18n-ally.keystyle": "nested", // 翻译路径格式
-  "i18n-ally.localesPaths": ["src/renderer/src/i18n/locales"],
-  // "i18n-ally.namespace": true, // 开启命名空间
-  "i18n-ally.sortKeys": true, // 排序
-  "i18n-ally.sourceLanguage": "zh-cn", // 翻译源语言
-  "i18n-ally.usage.derivedKeyRules": ["{key}_one", "{key}_other"], // 标记单复数形式的键为已翻译
   "search.exclude": {
     "**/dist/**": true,
     ".yarn/releases/**": true
   },
-  "tailwindCSS.classAttributes": [
-    "className",
-    "classNames",
-  ]
+  "[javascript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[typescript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[typescriptreact]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[json]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[jsonc]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[css]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[scss]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[markdown]": {
+    "files.trimTrailingWhitespace": false
+  },
+  "i18n-ally.localesPaths": ["src/renderer/src/i18n/locales"],
+  "i18n-ally.enabledFrameworks": ["react-i18next", "i18next"],
+  "i18n-ally.keystyle": "nested", // 翻译路径格式
+  "i18n-ally.sortKeys": true, // 排序
+  "i18n-ally.namespace": true, // 开启命名空间
+  "i18n-ally.enabledParsers": ["ts", "js", "json"], // 解析语言
+  "i18n-ally.sourceLanguage": "en-us", // 翻译源语言
+  "i18n-ally.displayLanguage": "zh-cn",
+  "i18n-ally.fullReloadOnChanged": true // 界面显示语言
 }

.yarn/patches/@ai-sdk-google-npm-2.0.43-689ed559b3.patch

@@ -1,26 +0,0 @@
-diff --git a/dist/index.js b/dist/index.js
-index 51ce7e423934fb717cb90245cdfcdb3dae6780e6..0f7f7009e2f41a79a8669d38c8a44867bbff5e1f 100644
---- a/dist/index.js
-+++ b/dist/index.js
-@@ -474,7 +474,7 @@ function convertToGoogleGenerativeAIMessages(prompt, options) {
- 
- // src/get-model-path.ts
- function getModelPath(modelId) {
--  return modelId.includes("/") ? modelId : `models/${modelId}`;
-+  return modelId.includes("models/") ? modelId : `models/${modelId}`;
- }
- 
- // src/google-generative-ai-options.ts
-diff --git a/dist/index.mjs b/dist/index.mjs
-index f4b77e35c0cbfece85a3ef0d4f4e67aa6dde6271..8d2fecf8155a226006a0bde72b00b6036d4014b6 100644
---- a/dist/index.mjs
-+++ b/dist/index.mjs
-@@ -480,7 +480,7 @@ function convertToGoogleGenerativeAIMessages(prompt, options) {
- 
- // src/get-model-path.ts
- function getModelPath(modelId) {
--  return modelId.includes("/") ? modelId : `models/${modelId}`;
-+  return modelId.includes("models/") ? modelId : `models/${modelId}`;
- }
- 
- // src/google-generative-ai-options.ts

.yarn/patches/@ai-sdk-openai-compatible-npm-1.0.27-06f74278cf.patch

@@ -1,140 +0,0 @@
-diff --git a/dist/index.js b/dist/index.js
-index 73045a7d38faafdc7f7d2cd79d7ff0e2b031056b..8d948c9ac4ea4b474db9ef3c5491961e7fcf9a07 100644
---- a/dist/index.js
-+++ b/dist/index.js
-@@ -421,6 +421,17 @@ var OpenAICompatibleChatLanguageModel = class {
-         text: reasoning
-       });
-     }
-+    if (choice.message.images) {
-+      for (const image of choice.message.images) {
-+        const match1 = image.image_url.url.match(/^data:([^;]+)/)
-+        const match2 = image.image_url.url.match(/^data:[^;]*;base64,(.+)$/);
-+        content.push({
-+          type: 'file',
-+          mediaType: match1 ? (match1[1] ?? 'image/jpeg') : 'image/jpeg',
-+          data: match2 ? match2[1] : image.image_url.url,
-+        });
-+      }
-+    }
-     if (choice.message.tool_calls != null) {
-       for (const toolCall of choice.message.tool_calls) {
-         content.push({
-@@ -598,6 +609,17 @@ var OpenAICompatibleChatLanguageModel = class {
-                 delta: delta.content
-               });
-             }
-+            if (delta.images) {
-+              for (const image of delta.images) {
-+                const match1 = image.image_url.url.match(/^data:([^;]+)/)
-+                const match2 = image.image_url.url.match(/^data:[^;]*;base64,(.+)$/);
-+                controller.enqueue({
-+                  type: 'file',
-+                  mediaType: match1 ? (match1[1] ?? 'image/jpeg') : 'image/jpeg',
-+                  data: match2 ? match2[1] : image.image_url.url,
-+                });
-+              }
-+            }
-             if (delta.tool_calls != null) {
-               for (const toolCallDelta of delta.tool_calls) {
-                 const index = toolCallDelta.index;
-@@ -765,6 +787,14 @@ var OpenAICompatibleChatResponseSchema = import_v43.z.object({
-               arguments: import_v43.z.string()
-             })
-           })
-+        ).nullish(),
-+        images: import_v43.z.array(
-+          import_v43.z.object({
-+            type: import_v43.z.literal('image_url'),
-+            image_url: import_v43.z.object({
-+              url: import_v43.z.string(),
-+            })
-+          })
-         ).nullish()
-       }),
-       finish_reason: import_v43.z.string().nullish()
-@@ -795,6 +825,14 @@ var createOpenAICompatibleChatChunkSchema = (errorSchema) => import_v43.z.union(
-                 arguments: import_v43.z.string().nullish()
-               })
-             })
-+          ).nullish(),
-+          images: import_v43.z.array(
-+            import_v43.z.object({
-+              type: import_v43.z.literal('image_url'),
-+              image_url: import_v43.z.object({
-+                url: import_v43.z.string(),
-+              })
-+            })
-           ).nullish()
-         }).nullish(),
-         finish_reason: import_v43.z.string().nullish()
-diff --git a/dist/index.mjs b/dist/index.mjs
-index 1c2b9560bbfbfe10cb01af080aeeed4ff59db29c..2c8ddc4fc9bfc5e7e06cfca105d197a08864c427 100644
---- a/dist/index.mjs
-+++ b/dist/index.mjs
-@@ -405,6 +405,17 @@ var OpenAICompatibleChatLanguageModel = class {
-         text: reasoning
-       });
-     }
-+    if (choice.message.images) {
-+      for (const image of choice.message.images) {
-+        const match1 = image.image_url.url.match(/^data:([^;]+)/)
-+        const match2 = image.image_url.url.match(/^data:[^;]*;base64,(.+)$/);
-+        content.push({
-+          type: 'file',
-+          mediaType: match1 ? (match1[1] ?? 'image/jpeg') : 'image/jpeg',
-+          data: match2 ? match2[1] : image.image_url.url,
-+        });
-+      }
-+    }
-     if (choice.message.tool_calls != null) {
-       for (const toolCall of choice.message.tool_calls) {
-         content.push({
-@@ -582,6 +593,17 @@ var OpenAICompatibleChatLanguageModel = class {
-                 delta: delta.content
-               });
-             }
-+            if (delta.images) {
-+              for (const image of delta.images) {
-+                const match1 = image.image_url.url.match(/^data:([^;]+)/)
-+                const match2 = image.image_url.url.match(/^data:[^;]*;base64,(.+)$/);
-+                controller.enqueue({
-+                  type: 'file',
-+                  mediaType: match1 ? (match1[1] ?? 'image/jpeg') : 'image/jpeg',
-+                  data: match2 ? match2[1] : image.image_url.url,
-+                });
-+              }
-+            }
-             if (delta.tool_calls != null) {
-               for (const toolCallDelta of delta.tool_calls) {
-                 const index = toolCallDelta.index;
-@@ -749,6 +771,14 @@ var OpenAICompatibleChatResponseSchema = z3.object({
-               arguments: z3.string()
-             })
-           })
-+        ).nullish(),
-+        images: z3.array(
-+          z3.object({
-+            type: z3.literal('image_url'),
-+            image_url: z3.object({
-+              url: z3.string(),
-+            })
-+          })
-         ).nullish()
-       }),
-       finish_reason: z3.string().nullish()
-@@ -779,6 +809,14 @@ var createOpenAICompatibleChatChunkSchema = (errorSchema) => z3.union([
-                 arguments: z3.string().nullish()
-               })
-             })
-+          ).nullish(),
-+          images: z3.array(
-+            z3.object({
-+              type: z3.literal('image_url'),
-+              image_url: z3.object({
-+                url: z3.string(),
-+              })
-+            })
-           ).nullish()
-         }).nullish(),
-         finish_reason: z3.string().nullish()

.yarn/patches/@ai-sdk-openai-npm-2.0.72-234e68da87.patch

@@ -1,74 +0,0 @@
-diff --git a/dist/index.js b/dist/index.js
-index bf900591bf2847a3253fe441aad24c06da19c6c1..c1d9bb6fefa2df1383339324073db0a70ea2b5a2 100644
---- a/dist/index.js
-+++ b/dist/index.js
-@@ -274,6 +274,7 @@ var openaiChatResponseSchema = (0, import_provider_utils3.lazyValidator)(
-           message: import_v42.z.object({
-             role: import_v42.z.literal("assistant").nullish(),
-             content: import_v42.z.string().nullish(),
-+            reasoning_content: import_v42.z.string().nullish(),
-             tool_calls: import_v42.z.array(
-               import_v42.z.object({
-                 id: import_v42.z.string().nullish(),
-@@ -340,6 +341,7 @@ var openaiChatChunkSchema = (0, import_provider_utils3.lazyValidator)(
-             delta: import_v42.z.object({
-               role: import_v42.z.enum(["assistant"]).nullish(),
-               content: import_v42.z.string().nullish(),
-+              reasoning_content: import_v42.z.string().nullish(),
-               tool_calls: import_v42.z.array(
-                 import_v42.z.object({
-                   index: import_v42.z.number(),
-@@ -795,6 +797,13 @@ var OpenAIChatLanguageModel = class {
-     if (text != null && text.length > 0) {
-       content.push({ type: "text", text });
-     }
-+    const reasoning = choice.message.reasoning_content;
-+    if (reasoning != null && reasoning.length > 0) {
-+      content.push({
-+        type: 'reasoning',
-+        text: reasoning
-+      });
-+    }
-     for (const toolCall of (_a = choice.message.tool_calls) != null ? _a : []) {
-       content.push({
-         type: "tool-call",
-@@ -876,6 +885,7 @@ var OpenAIChatLanguageModel = class {
-     };
-     let metadataExtracted = false;
-     let isActiveText = false;
-+    let isActiveReasoning = false;
-     const providerMetadata = { openai: {} };
-     return {
-       stream: response.pipeThrough(
-@@ -933,6 +943,21 @@ var OpenAIChatLanguageModel = class {
-               return;
-             }
-             const delta = choice.delta;
-+            const reasoningContent = delta.reasoning_content;
-+            if (reasoningContent) {
-+              if (!isActiveReasoning) {
-+                controller.enqueue({
-+                  type: 'reasoning-start',
-+                  id: 'reasoning-0',
-+                });
-+                isActiveReasoning = true;
-+              }
-+              controller.enqueue({
-+                type: 'reasoning-delta',
-+                id: 'reasoning-0',
-+                delta: reasoningContent,
-+              });
-+            }
-             if (delta.content != null) {
-               if (!isActiveText) {
-                 controller.enqueue({ type: "text-start", id: "0" });
-@@ -1045,6 +1070,9 @@ var OpenAIChatLanguageModel = class {
-             }
-           },
-           flush(controller) {
-+            if (isActiveReasoning) {
-+              controller.enqueue({ type: 'reasoning-end', id: 'reasoning-0' });
-+            }
-             if (isActiveText) {
-               controller.enqueue({ type: "text-end", id: "0" });
-             }

.yarn/patches/@anthropic-ai-claude-agent-sdk-npm-0.1.53-4b77f4cf29.patch

@@ -1,35 +0,0 @@
-diff --git a/sdk.mjs b/sdk.mjs
-index bf429a344b7d59f70aead16b639f949b07688a81..f77d50cc5d3fb04292cb3ac7fa7085d02dcc628f 100755
---- a/sdk.mjs
-+++ b/sdk.mjs
-@@ -6250,7 +6250,7 @@ function createAbortController(maxListeners = DEFAULT_MAX_LISTENERS) {
- }
- 
- // ../src/transport/ProcessTransport.ts
--import { spawn } from "child_process";
-+import { fork } from "child_process";
- import { createInterface } from "readline";
- 
- // ../src/utils/fsOperations.ts
-@@ -6619,18 +6619,11 @@ class ProcessTransport {
-         const errorMessage = isNativeBinary(pathToClaudeCodeExecutable) ? `Claude Code native binary not found at ${pathToClaudeCodeExecutable}. Please ensure Claude Code is installed via native installer or specify a valid path with options.pathToClaudeCodeExecutable.` : `Claude Code executable not found at ${pathToClaudeCodeExecutable}. Is options.pathToClaudeCodeExecutable set?`;
-         throw new ReferenceError(errorMessage);
-       }
--      const isNative = isNativeBinary(pathToClaudeCodeExecutable);
--      const spawnCommand = isNative ? pathToClaudeCodeExecutable : executable;
--      const spawnArgs = isNative ? [...executableArgs, ...args] : [...executableArgs, pathToClaudeCodeExecutable, ...args];
--      const spawnMessage = isNative ? `Spawning Claude Code native binary: ${spawnCommand} ${spawnArgs.join(" ")}` : `Spawning Claude Code process: ${spawnCommand} ${spawnArgs.join(" ")}`;
--      logForSdkDebugging(spawnMessage);
--      if (stderr) {
--        stderr(spawnMessage);
--      }
-+      logForSdkDebugging(`Forking Claude Code Node.js process: ${pathToClaudeCodeExecutable} ${args.join(" ")}`);
-       const stderrMode = env.DEBUG_CLAUDE_AGENT_SDK || stderr ? "pipe" : "ignore";
--      this.child = spawn(spawnCommand, spawnArgs, {
-+      this.child = fork(pathToClaudeCodeExecutable, args, {
-         cwd,
--        stdio: ["pipe", "pipe", stderrMode],
-+        stdio: stderrMode === "pipe" ? ["pipe", "pipe", "pipe", "ipc"] : ["pipe", "pipe", "ignore", "ipc"],
-         signal: this.abortController.signal,
-         env
-       });

.yarn/patches/@anthropic-ai-vertex-sdk-npm-0.11.4-c19cb41edb.patch

@@ -1,196 +0,0 @@
-diff --git a/client.js b/client.js
-index c2b9cd6e46f9f66f901af259661bc2d2f8b38936..9b6b3af1a6573e1ccaf3a1c5f41b48df198cbbe0 100644
---- a/client.js
-+++ b/client.js
-@@ -26,7 +26,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
- exports.AnthropicVertex = exports.BaseAnthropic = void 0;
- const client_1 = require("@anthropic-ai/sdk/client");
- const Resources = __importStar(require("@anthropic-ai/sdk/resources/index"));
--const google_auth_library_1 = require("google-auth-library");
-+// const google_auth_library_1 = require("google-auth-library");
- const env_1 = require("./internal/utils/env.js");
- const values_1 = require("./internal/utils/values.js");
- const headers_1 = require("./internal/headers.js");
-@@ -56,7 +56,7 @@ class AnthropicVertex extends client_1.BaseAnthropic {
-             throw new Error('No region was given. The client should be instantiated with the `region` option or the `CLOUD_ML_REGION` environment variable should be set.');
-         }
-         super({
--            baseURL: baseURL || `https://${region}-aiplatform.googleapis.com/v1`,
-+            baseURL: baseURL || (region === 'global' ? 'https://aiplatform.googleapis.com/v1' : `https://${region}-aiplatform.googleapis.com/v1`),
-             ...opts,
-         });
-         this.messages = makeMessagesResource(this);
-@@ -64,22 +64,22 @@ class AnthropicVertex extends client_1.BaseAnthropic {
-         this.region = region;
-         this.projectId = projectId;
-         this.accessToken = opts.accessToken ?? null;
--        this._auth =
--            opts.googleAuth ?? new google_auth_library_1.GoogleAuth({ scopes: 'https://www.googleapis.com/auth/cloud-platform' });
--        this._authClientPromise = this._auth.getClient();
-+        // this._auth =
-+        //    opts.googleAuth ?? new google_auth_library_1.GoogleAuth({ scopes: 'https://www.googleapis.com/auth/cloud-platform' });
-+        // this._authClientPromise = this._auth.getClient();
-     }
-     validateHeaders() {
-         // auth validation is handled in prepareOptions since it needs to be async
-     }
--    async prepareOptions(options) {
--        const authClient = await this._authClientPromise;
--        const authHeaders = await authClient.getRequestHeaders();
--        const projectId = authClient.projectId ?? authHeaders['x-goog-user-project'];
--        if (!this.projectId && projectId) {
--            this.projectId = projectId;
--        }
--        options.headers = (0, headers_1.buildHeaders)([authHeaders, options.headers]);
--    }
-+        // async prepareOptions(options) {
-+        //     const authClient = await this._authClientPromise;
-+        //     const authHeaders = await authClient.getRequestHeaders();
-+        //     const projectId = authClient.projectId ?? authHeaders['x-goog-user-project'];
-+        //     if (!this.projectId && projectId) {
-+        //         this.projectId = projectId;
-+        //     }
-+        //     options.headers = (0, headers_1.buildHeaders)([authHeaders, options.headers]);
-+        // }
-     buildRequest(options) {
-         if ((0, values_1.isObj)(options.body)) {
-             // create a shallow copy of the request body so that code that mutates it later
-diff --git a/client.mjs b/client.mjs
-index 70274cbf38f69f87cbcca9567e77e4a7b938cf90..4dea954b6f4afad565663426b7adfad5de973a7d 100644
---- a/client.mjs
-+++ b/client.mjs
-@@ -1,6 +1,6 @@
- import { BaseAnthropic } from '@anthropic-ai/sdk/client';
- import * as Resources from '@anthropic-ai/sdk/resources/index';
--import { GoogleAuth } from 'google-auth-library';
-+// import { GoogleAuth } from 'google-auth-library';
- import { readEnv } from "./internal/utils/env.mjs";
- import { isObj } from "./internal/utils/values.mjs";
- import { buildHeaders } from "./internal/headers.mjs";
-@@ -29,7 +29,7 @@ export class AnthropicVertex extends BaseAnthropic {
-             throw new Error('No region was given. The client should be instantiated with the `region` option or the `CLOUD_ML_REGION` environment variable should be set.');
-         }
-         super({
--            baseURL: baseURL || `https://${region}-aiplatform.googleapis.com/v1`,
-+            baseURL: baseURL || (region === 'global' ? 'https://aiplatform.googleapis.com/v1' : `https://${region}-aiplatform.googleapis.com/v1`),
-             ...opts,
-         });
-         this.messages = makeMessagesResource(this);
-@@ -37,22 +37,22 @@ export class AnthropicVertex extends BaseAnthropic {
-         this.region = region;
-         this.projectId = projectId;
-         this.accessToken = opts.accessToken ?? null;
--        this._auth =
--            opts.googleAuth ?? new GoogleAuth({ scopes: 'https://www.googleapis.com/auth/cloud-platform' });
--        this._authClientPromise = this._auth.getClient();
-+        // this._auth =
-+        //    opts.googleAuth ?? new GoogleAuth({ scopes: 'https://www.googleapis.com/auth/cloud-platform' });
-+        //this._authClientPromise = this._auth.getClient();
-     }
-     validateHeaders() {
-         // auth validation is handled in prepareOptions since it needs to be async
-     }
--    async prepareOptions(options) {
--        const authClient = await this._authClientPromise;
--        const authHeaders = await authClient.getRequestHeaders();
--        const projectId = authClient.projectId ?? authHeaders['x-goog-user-project'];
--        if (!this.projectId && projectId) {
--            this.projectId = projectId;
--        }
--        options.headers = buildHeaders([authHeaders, options.headers]);
--    }
-+    // async prepareOptions(options) {
-+    //     const authClient = await this._authClientPromise;
-+    //     const authHeaders = await authClient.getRequestHeaders();
-+    //     const projectId = authClient.projectId ?? authHeaders['x-goog-user-project'];
-+    //     if (!this.projectId && projectId) {
-+    //         this.projectId = projectId;
-+    //     }
-+    //     options.headers = buildHeaders([authHeaders, options.headers]);
-+    // }
-     buildRequest(options) {
-         if (isObj(options.body)) {
-             // create a shallow copy of the request body so that code that mutates it later
-diff --git a/src/client.ts b/src/client.ts
-index a6f9c6be65e4189f4f9601fb560df3f68e7563eb..37b1ad2802e3ca0dae4ca35f9dcb5b22dcf09796 100644
---- a/src/client.ts
-+++ b/src/client.ts
-@@ -12,22 +12,22 @@ export { BaseAnthropic } from '@anthropic-ai/sdk/client';
- const DEFAULT_VERSION = 'vertex-2023-10-16';
- const MODEL_ENDPOINTS = new Set<string>(['/v1/messages', '/v1/messages?beta=true']);
- 
--export type ClientOptions = Omit<CoreClientOptions, 'apiKey' | 'authToken'> & {
--  region?: string | null | undefined;
--  projectId?: string | null | undefined;
--  accessToken?: string | null | undefined;
--
--  /**
--   * Override the default google auth config using the
--   * [google-auth-library](https://www.npmjs.com/package/google-auth-library) package.
--   *
--   * Note that you'll likely have to set `scopes`, e.g.
--   * ```ts
--   * new GoogleAuth({ scopes: 'https://www.googleapis.com/auth/cloud-platform' })
--   * ```
--   */
--  googleAuth?: GoogleAuth | null | undefined;
--};
-+// export type ClientOptions = Omit<CoreClientOptions, 'apiKey' | 'authToken'> & {
-+//   region?: string | null | undefined;
-+//   projectId?: string | null | undefined;
-+//   accessToken?: string | null | undefined;
-+
-+//   /**
-+//    * Override the default google auth config using the
-+//    * [google-auth-library](https://www.npmjs.com/package/google-auth-library) package.
-+//    *
-+//    * Note that you'll likely have to set `scopes`, e.g.
-+//    * ```ts
-+//    * new GoogleAuth({ scopes: 'https://www.googleapis.com/auth/cloud-platform' })
-+//    * ```
-+//    */
-+//   googleAuth?: GoogleAuth | null | undefined;
-+// };
- 
- export class AnthropicVertex extends BaseAnthropic {
-   region: string;
-@@ -74,9 +74,9 @@ export class AnthropicVertex extends BaseAnthropic {
-     this.projectId = projectId;
-     this.accessToken = opts.accessToken ?? null;
- 
--    this._auth =
--      opts.googleAuth ?? new GoogleAuth({ scopes: 'https://www.googleapis.com/auth/cloud-platform' });
--    this._authClientPromise = this._auth.getClient();
-+    // this._auth =
-+    //   opts.googleAuth ?? new GoogleAuth({ scopes: 'https://www.googleapis.com/auth/cloud-platform' });
-+    // this._authClientPromise = this._auth.getClient();
-   }
- 
-   messages: MessagesResource = makeMessagesResource(this);
-@@ -86,17 +86,17 @@ export class AnthropicVertex extends BaseAnthropic {
-     // auth validation is handled in prepareOptions since it needs to be async
-   }
- 
--  protected override async prepareOptions(options: FinalRequestOptions): Promise<void> {
--    const authClient = await this._authClientPromise;
-+  // protected override async prepareOptions(options: FinalRequestOptions): Promise<void> {
-+  //   const authClient = await this._authClientPromise;
- 
--    const authHeaders = await authClient.getRequestHeaders();
--    const projectId = authClient.projectId ?? authHeaders['x-goog-user-project'];
--    if (!this.projectId && projectId) {
--      this.projectId = projectId;
--    }
-+  //   const authHeaders = await authClient.getRequestHeaders();
-+  //   const projectId = authClient.projectId ?? authHeaders['x-goog-user-project'];
-+  //   if (!this.projectId && projectId) {
-+  //     this.projectId = projectId;
-+  //   }
- 
--    options.headers = buildHeaders([authHeaders, options.headers]);
--  }
-+  //   options.headers = buildHeaders([authHeaders, options.headers]);
-+  // }
- 
-   override buildRequest(options: FinalRequestOptions): {
-     req: FinalizedRequestInit;

.yarn/patches/@langchain-core-npm-0.3.44-41d5c3cb0a.patch

@@ -0,0 +1,71 @@
+diff --git a/dist/utils/tiktoken.cjs b/dist/utils/tiktoken.cjs
+index 973b0d0e75aeaf8de579419af31b879b32975413..f23c7caa8b9dc8bd404132725346a4786f6b278b 100644
+--- a/dist/utils/tiktoken.cjs
++++ b/dist/utils/tiktoken.cjs
+@@ -1,25 +1,14 @@
+ "use strict";
+ Object.defineProperty(exports, "__esModule", { value: true });
+ exports.encodingForModel = exports.getEncoding = void 0;
+-const lite_1 = require("js-tiktoken/lite");
+ const async_caller_js_1 = require("./async_caller.cjs");
+ const cache = {};
+ const caller = /* #__PURE__ */ new async_caller_js_1.AsyncCaller({});
+ async function getEncoding(encoding) {
+-    if (!(encoding in cache)) {
+-        cache[encoding] = caller
+-            .fetch(`https://tiktoken.pages.dev/js/${encoding}.json`)
+-            .then((res) => res.json())
+-            .then((data) => new lite_1.Tiktoken(data))
+-            .catch((e) => {
+-            delete cache[encoding];
+-            throw e;
+-        });
+-    }
+-    return await cache[encoding];
++    throw new Error("TikToken Not implemented");
+ }
+ exports.getEncoding = getEncoding;
+ async function encodingForModel(model) {
+-    return getEncoding((0, lite_1.getEncodingNameForModel)(model));
++    throw new Error("TikToken Not implemented");
+ }
+ exports.encodingForModel = encodingForModel;
+diff --git a/dist/utils/tiktoken.js b/dist/utils/tiktoken.js
+index 8e41ee6f00f2f9c7fa2c59fa2b2f4297634b97aa..aa5f314a6349ad0d1c5aea8631a56aad099176e0 100644
+--- a/dist/utils/tiktoken.js
++++ b/dist/utils/tiktoken.js
+@@ -1,20 +1,9 @@
+-import { Tiktoken, getEncodingNameForModel, } from "js-tiktoken/lite";
+ import { AsyncCaller } from "./async_caller.js";
+ const cache = {};
+ const caller = /* #__PURE__ */ new AsyncCaller({});
+ export async function getEncoding(encoding) {
+-    if (!(encoding in cache)) {
+-        cache[encoding] = caller
+-            .fetch(`https://tiktoken.pages.dev/js/${encoding}.json`)
+-            .then((res) => res.json())
+-            .then((data) => new Tiktoken(data))
+-            .catch((e) => {
+-            delete cache[encoding];
+-            throw e;
+-        });
+-    }
+-    return await cache[encoding];
++    throw new Error("TikToken Not implemented");
+ }
+ export async function encodingForModel(model) {
+-    return getEncoding(getEncodingNameForModel(model));
++    throw new Error("TikToken Not implemented");
+ }
+diff --git a/package.json b/package.json
+index 36072aecf700fca1bc49832a19be832eca726103..90b8922fba1c3d1b26f78477c891b07816d6238a 100644
+--- a/package.json
++++ b/package.json
+@@ -37,7 +37,6 @@
+     "ansi-styles": "^5.0.0",
+     "camelcase": "6",
+     "decamelize": "1.2.0",
+-    "js-tiktoken": "^1.0.12",
+     "langsmith": ">=0.2.8 <0.4.0",
+     "mustache": "^4.2.0",
+     "p-queue": "^6.6.2",

.yarn/patches/@langchain-core-npm-1.0.2-183ef83fe4.patch

@@ -1,68 +0,0 @@
-diff --git a/dist/utils/tiktoken.cjs b/dist/utils/tiktoken.cjs
-index c5b41f121d2e3d24c3a4969e31fa1acffdcad3b9..ec724489dcae79ee6c61acf2d4d84bd19daef036 100644
---- a/dist/utils/tiktoken.cjs
-+++ b/dist/utils/tiktoken.cjs
-@@ -1,6 +1,5 @@
- const require_rolldown_runtime = require('../_virtual/rolldown_runtime.cjs');
- const require_utils_async_caller = require('./async_caller.cjs');
--const js_tiktoken_lite = require_rolldown_runtime.__toESM(require("js-tiktoken/lite"));
- 
- //#region src/utils/tiktoken.ts
- var tiktoken_exports = {};
-@@ -11,14 +10,10 @@ require_rolldown_runtime.__export(tiktoken_exports, {
- const cache = {};
- const caller = /* @__PURE__ */ new require_utils_async_caller.AsyncCaller({});
- async function getEncoding(encoding) {
--	if (!(encoding in cache)) cache[encoding] = caller.fetch(`https://tiktoken.pages.dev/js/${encoding}.json`).then((res) => res.json()).then((data) => new js_tiktoken_lite.Tiktoken(data)).catch((e) => {
--		delete cache[encoding];
--		throw e;
--	});
--	return await cache[encoding];
-+	throw new Error("TikToken Not implemented");
- }
- async function encodingForModel(model) {
--	return getEncoding((0, js_tiktoken_lite.getEncodingNameForModel)(model));
-+	throw new Error("TikToken Not implemented");
- }
- 
- //#endregion
-diff --git a/dist/utils/tiktoken.js b/dist/utils/tiktoken.js
-index 641acca03cb92f04a6fa5c9c31f1880ce635572e..707389970ad957aa0ff20ef37fa8dd2875be737c 100644
---- a/dist/utils/tiktoken.js
-+++ b/dist/utils/tiktoken.js
-@@ -1,6 +1,5 @@
- import { __export } from "../_virtual/rolldown_runtime.js";
- import { AsyncCaller } from "./async_caller.js";
--import { Tiktoken, getEncodingNameForModel } from "js-tiktoken/lite";
- 
- //#region src/utils/tiktoken.ts
- var tiktoken_exports = {};
-@@ -11,14 +10,10 @@ __export(tiktoken_exports, {
- const cache = {};
- const caller = /* @__PURE__ */ new AsyncCaller({});
- async function getEncoding(encoding) {
--	if (!(encoding in cache)) cache[encoding] = caller.fetch(`https://tiktoken.pages.dev/js/${encoding}.json`).then((res) => res.json()).then((data) => new Tiktoken(data)).catch((e) => {
--		delete cache[encoding];
--		throw e;
--	});
--	return await cache[encoding];
-+	throw new Error("TikToken Not implemented");
- }
- async function encodingForModel(model) {
--	return getEncoding(getEncodingNameForModel(model));
-+	throw new Error("TikToken Not implemented");
- }
- 
- //#endregion
-diff --git a/package.json b/package.json
-index a24f8fc61de58526051999260f2ebee5f136354b..e885359e8966e7730c51772533ce37e01edb3046 100644
---- a/package.json
-+++ b/package.json
-@@ -20,7 +20,6 @@
-     "ansi-styles": "^5.0.0",
-     "camelcase": "6",
-     "decamelize": "1.2.0",
--    "js-tiktoken": "^1.0.12",
-     "langsmith": "^0.3.64",
-     "mustache": "^4.2.0",
-     "p-queue": "^6.6.2",

.yarn/patches/@langchain-openai-npm-0.3.16-e525b59526.patch

@@ -0,0 +1,19 @@
+diff --git a/dist/embeddings.js b/dist/embeddings.js
+index 1f8154be3e9c22442a915eb4b85fa6d2a21b0d0c..dc13ef4a30e6c282824a5357bcee9bd0ae222aab 100644
+--- a/dist/embeddings.js
++++ b/dist/embeddings.js
+@@ -214,10 +214,12 @@ export class OpenAIEmbeddings extends Embeddings {
+      * @returns Promise that resolves to an embedding for the document.
+      */
+     async embedQuery(text) {
++        const isBaiduCloud = this.clientConfig.baseURL.includes('baidubce.com')
++        const input = this.stripNewLines ? text.replace(/\n/g, ' ') : text
+         const params = {
+             model: this.model,
+-            input: this.stripNewLines ? text.replace(/\n/g, " ") : text,
+-        };
++            input: isBaiduCloud ? [input] : input
++        }
+         if (this.dimensions) {
+             params.dimensions = this.dimensions;
+         }

.yarn/patches/@langchain-openai-npm-1.0.0-474d0ad9d4.patch

@@ -1,17 +0,0 @@
-diff --git a/dist/embeddings.js b/dist/embeddings.js
-index 6f4b928d3e4717309382e1b5c2e31ab5bc6c5af0..bc79429c88a6d27d4997a2740c4d8ae0707f5991 100644
---- a/dist/embeddings.js
-+++ b/dist/embeddings.js
-@@ -94,9 +94,11 @@ var OpenAIEmbeddings = class extends Embeddings {
- 	* @returns Promise that resolves to an embedding for the document.
- 	*/
- 	async embedQuery(text) {
-+		const isBaiduCloud = this.clientConfig.baseURL.includes('baidubce.com');
-+		const input = this.stripNewLines ? text.replace(/\n/g, " ") : text
- 		const params = {
- 			model: this.model,
--			input: this.stripNewLines ? text.replace(/\n/g, " ") : text
-+			input: isBaiduCloud ? [input] : input
- 		};
- 		if (this.dimensions) params.dimensions = this.dimensions;
- 		if (this.encodingFormat) params.encoding_format = this.encodingFormat;

.yarn/patches/@napi-rs-system-ocr-npm-1.0.2-59e7a78e8b.patch

@@ -1,30 +0,0 @@
-diff --git a/index.js b/index.js
-index dc071739e79876dff88e1be06a9168e294222d13..b9df7525c62bdf777e89e732e1b0c81f84d872f2 100644
---- a/index.js
-+++ b/index.js
-@@ -380,7 +380,7 @@ if (!nativeBinding || process.env.NAPI_RS_FORCE_WASI) {
-   }
- }
- 
--if (!nativeBinding) {
-+if (!nativeBinding && process.platform !== 'linux') {
-   if (loadErrors.length > 0) {
-     throw new Error(
-       `Cannot find native binding. ` +
-@@ -392,6 +392,13 @@ if (!nativeBinding) {
-   throw new Error(`Failed to load native binding`)
- }
- 
--module.exports = nativeBinding
--module.exports.OcrAccuracy = nativeBinding.OcrAccuracy
--module.exports.recognize = nativeBinding.recognize
-+if (process.platform === 'linux') {
-+  module.exports = {OcrAccuracy: {
-+    Fast: 0,
-+    Accurate: 1
-+  }, recognize: () => Promise.resolve({text: '', confidence: 1.0})}
-+}else{
-+  module.exports = nativeBinding
-+  module.exports.OcrAccuracy = nativeBinding.OcrAccuracy
-+  module.exports.recognize = nativeBinding.recognize
-+}

.yarn/patches/@tiptap-extension-drag-handle-npm-3.2.0-5a9ebff7c9.patch

@@ -1,48 +0,0 @@
-diff --git a/dist/index.cjs b/dist/index.cjs
-index 8e560a4406c5cc616c11bb9fd5455ac0dcf47fa3..c7cd0d65ddc971bff71e89f610de82cfdaa5a8c7 100644
---- a/dist/index.cjs
-+++ b/dist/index.cjs
-@@ -413,6 +413,19 @@ var DragHandlePlugin = ({
-             }
-             return false;
-           },
-+          scroll(view) {
-+            if (!element || locked) {
-+              return false;
-+            }
-+            if (view.hasFocus()) {
-+              hideHandle();
-+              currentNode = null;
-+              currentNodePos = -1;
-+              onNodeChange == null ? void 0 : onNodeChange({ editor, node: null, pos: -1 });
-+              return false;
-+            }
-+            return false;
-+          },
-           mouseleave(_view, e) {
-             if (locked) {
-               return false;
-diff --git a/dist/index.js b/dist/index.js
-index 39e4c3ef9986cd25544d9d3994cf6a9ada74b145..378d9130abbfdd0e1e4f743b5b537743c9ab07d0 100644
---- a/dist/index.js
-+++ b/dist/index.js
-@@ -387,6 +387,19 @@ var DragHandlePlugin = ({
-             }
-             return false;
-           },
-+          scroll(view) {
-+            if (!element || locked) {
-+              return false;
-+            }
-+            if (view.hasFocus()) {
-+              hideHandle();
-+              currentNode = null;
-+              currentNodePos = -1;
-+              onNodeChange == null ? void 0 : onNodeChange({ editor, node: null, pos: -1 });
-+              return false;
-+            }
-+            return false;
-+          },
-           mouseleave(_view, e) {
-             if (locked) {
-               return false;

.yarn/patches/antd-npm-5.27.0-aa91c36546.patch

@@ -1,55 +0,0 @@
-diff --git a/es/dropdown/dropdown.js b/es/dropdown/dropdown.js
-index 2e45574398ff68450022a0078e213cc81fe7454e..58ba7789939b7805a89f92b93d222f8fb1168bdf 100644
---- a/es/dropdown/dropdown.js
-+++ b/es/dropdown/dropdown.js
-@@ -2,7 +2,7 @@
- 
- import * as React from 'react';
- import LeftOutlined from "@ant-design/icons/es/icons/LeftOutlined";
--import RightOutlined from "@ant-design/icons/es/icons/RightOutlined";
-+import { ChevronRight } from 'lucide-react';
- import classNames from 'classnames';
- import RcDropdown from 'rc-dropdown';
- import useEvent from "rc-util/es/hooks/useEvent";
-@@ -160,8 +160,10 @@ const Dropdown = props => {
-         className: `${prefixCls}-menu-submenu-arrow`
-       }, direction === 'rtl' ? (/*#__PURE__*/React.createElement(LeftOutlined, {
-         className: `${prefixCls}-menu-submenu-arrow-icon`
--      })) : (/*#__PURE__*/React.createElement(RightOutlined, {
--        className: `${prefixCls}-menu-submenu-arrow-icon`
-+      })) : (/*#__PURE__*/React.createElement(ChevronRight, {
-+        size: 16,
-+        strokeWidth: 1.8,
-+        className: `${prefixCls}-menu-submenu-arrow-icon lucide-custom`
-       }))),
-       mode: "vertical",
-       selectable: false,
-diff --git a/es/select/useIcons.js b/es/select/useIcons.js
-index 572aaaa0899f429cbf8a7181f2eeada545f76dcb..4e175c8d7713dd6422f8bcdc74ee671a835de6ce 100644
---- a/es/select/useIcons.js
-+++ b/es/select/useIcons.js
-@@ -4,10 +4,10 @@ import * as React from 'react';
- import CheckOutlined from "@ant-design/icons/es/icons/CheckOutlined";
- import CloseCircleFilled from "@ant-design/icons/es/icons/CloseCircleFilled";
- import CloseOutlined from "@ant-design/icons/es/icons/CloseOutlined";
--import DownOutlined from "@ant-design/icons/es/icons/DownOutlined";
- import LoadingOutlined from "@ant-design/icons/es/icons/LoadingOutlined";
- import SearchOutlined from "@ant-design/icons/es/icons/SearchOutlined";
- import { devUseWarning } from '../_util/warning';
-+import { ChevronDown } from 'lucide-react';
- export default function useIcons({
-   suffixIcon,
-   clearIcon,
-@@ -54,8 +54,10 @@ export default function useIcons({
-           className: iconCls
-         }));
-       }
--      return getSuffixIconNode(/*#__PURE__*/React.createElement(DownOutlined, {
--        className: iconCls
-+      return getSuffixIconNode(/*#__PURE__*/React.createElement(ChevronDown, {
-+        size: 16,
-+        strokeWidth: 1.8,
-+        className: `${iconCls} lucide-custom`
-       }));
-     };
-   }

.yarn/patches/app-builder-lib-npm-26.0.15-360e5b0476.patch

@@ -0,0 +1,324 @@
+diff --git a/out/macPackager.js b/out/macPackager.js
+index 852f6c4d16f86a7bb8a78bf1ed5a14647a279aa1..60e7f5f16a844541eb1909b215fcda1811e924b8 100644
+--- a/out/macPackager.js
++++ b/out/macPackager.js
+@@ -423,7 +423,7 @@ class MacPackager extends platformPackager_1.PlatformPackager {
+         }
+         appPlist.CFBundleName = appInfo.productName;
+         appPlist.CFBundleDisplayName = appInfo.productName;
+-        const minimumSystemVersion = this.platformSpecificBuildOptions.minimumSystemVersion;
++        const minimumSystemVersion = this.platformSpecificBuildOptions.LSMinimumSystemVersion;
+         if (minimumSystemVersion != null) {
+             appPlist.LSMinimumSystemVersion = minimumSystemVersion;
+         }
+diff --git a/out/packager.js b/out/packager.js
+index 579f7f4b62f61037234098ba378ab30efb64c7a9..02df1dd38f83a57a60258a51b2ee9f0b4020dab4 100644
+--- a/out/packager.js
++++ b/out/packager.js
+@@ -426,12 +426,12 @@ class Packager {
+                 throw new Error(`Unknown platform: ${platform}`);
+         }
+     }
+-    async installAppDependencies(platform, arch) {
++    async installAppDependencies(platform, arch, excludeReBuildModules) {
+         if (this.options.prepackaged != null || !this.framework.isNpmRebuildRequired) {
+             return;
+         }
+         const frameworkInfo = { version: this.framework.version, useCustomDist: true };
+-        const config = this.config;
++        const config= this.config;
+         if (config.nodeGypRebuild === true) {
+             await (0, yarn_1.nodeGypRebuild)(platform.nodeName, builder_util_1.Arch[arch], frameworkInfo);
+         }
+@@ -462,6 +462,7 @@ class Packager {
+                 platform: platform.nodeName,
+                 arch: builder_util_1.Arch[arch],
+                 productionDeps: this.getNodeDependencyInfo(null, false),
++                excludeReBuildModules,
+             });
+         }
+     }
+diff --git a/out/platformPackager.js b/out/platformPackager.js
+index 05c740ead5e1e16dd77d5e523309c8b2c3bd581e..38f730d148ddda2e1bae64371658d7917e8ff05a 100644
+--- a/out/platformPackager.js
++++ b/out/platformPackager.js
+@@ -148,6 +148,7 @@ class PlatformPackager {
+         // Due to node-gyp rewriting GYP_MSVS_VERSION when reused across the same session, we must reset the env var: https://github.com/electron-userland/electron-builder/issues/7256
+         delete process.env.GYP_MSVS_VERSION;
+         const { outDir, appOutDir, platformName, arch, platformSpecificBuildOptions, targets, options } = packOptions;
++        builder_util_1.log.info(platformSpecificBuildOptions,"platformSpecificBuildOptions");
+         await this.info.emitBeforePack({
+             appOutDir,
+             outDir,
+@@ -156,7 +157,7 @@ class PlatformPackager {
+             packager: this,
+             electronPlatformName: platformName,
+         });
+-        await this.info.installAppDependencies(this.platform, arch);
++        await this.info.installAppDependencies(this.platform, arch, platformSpecificBuildOptions.excludeReBuildModules);
+         if (this.info.cancellationToken.cancelled) {
+             return;
+         }
+diff --git a/out/publish/updateInfoBuilder.js b/out/publish/updateInfoBuilder.js
+index 7924c5b47d01f8dfccccb8f46658015fa66da1f7..1a1588923c3939ae1297b87931ba83f0ebc052d8 100644
+--- a/out/publish/updateInfoBuilder.js
++++ b/out/publish/updateInfoBuilder.js
+@@ -133,6 +133,7 @@ async function createUpdateInfo(version, event, releaseInfo) {
+     const customUpdateInfo = event.updateInfo;
+     const url = path.basename(event.file);
+     const sha512 = (customUpdateInfo == null ? null : customUpdateInfo.sha512) || (await (0, hash_1.hashFile)(event.file));
++    const minimumSystemVersion = customUpdateInfo == null ? null : customUpdateInfo.minimumSystemVersion;
+     const files = [{ url, sha512 }];
+     const result = {
+         // @ts-ignore
+@@ -143,9 +144,13 @@ async function createUpdateInfo(version, event, releaseInfo) {
+         path: url /* backward compatibility, electron-updater 1.x - electron-updater 2.15.0 */,
+         // @ts-ignore
+         sha512 /* backward compatibility, electron-updater 1.x - electron-updater 2.15.0 */,
++        minimumSystemVersion,
+         ...releaseInfo,
+     };
+     if (customUpdateInfo != null) {
++        if (customUpdateInfo.minimumSystemVersion) {
++            delete customUpdateInfo.minimumSystemVersion;
++        }
+         // file info or nsis web installer packages info
+         Object.assign("sha512" in customUpdateInfo ? files[0] : result, customUpdateInfo);
+     }
+diff --git a/out/targets/ArchiveTarget.js b/out/targets/ArchiveTarget.js
+index e1f52a5fa86fff6643b2e57eaf2af318d541f865..47cc347f154a24b365e70ae5e1f6d309f3582ed0 100644
+--- a/out/targets/ArchiveTarget.js
++++ b/out/targets/ArchiveTarget.js
+@@ -69,6 +69,9 @@ class ArchiveTarget extends core_1.Target {
+                     }
+                 }
+             }
++            if (updateInfo != null && this.packager.platformSpecificBuildOptions.minimumSystemVersion) {
++                updateInfo.minimumSystemVersion = this.packager.platformSpecificBuildOptions.minimumSystemVersion;
++            }
+             await packager.info.emitArtifactBuildCompleted({
+                 updateInfo,
+                 file: artifactPath,
+diff --git a/out/targets/nsis/NsisTarget.js b/out/targets/nsis/NsisTarget.js
+index e8bd7bb46c8a54b3f55cf3a853ef924195271e01..f956e9f3fe9eb903c78aef3502553b01de4b89b1 100644
+--- a/out/targets/nsis/NsisTarget.js
++++ b/out/targets/nsis/NsisTarget.js
+@@ -305,6 +305,9 @@ class NsisTarget extends core_1.Target {
+             if (updateInfo != null && isPerMachine && (oneClick || options.packElevateHelper)) {
+                 updateInfo.isAdminRightsRequired = true;
+             }
++            if (updateInfo != null && this.packager.platformSpecificBuildOptions.minimumSystemVersion) {
++                updateInfo.minimumSystemVersion = this.packager.platformSpecificBuildOptions.minimumSystemVersion;
++            }
+             await packager.info.emitArtifactBuildCompleted({
+                 file: installerPath,
+                 updateInfo,
+diff --git a/out/util/yarn.js b/out/util/yarn.js
+index 1ee20f8b252a8f28d0c7b103789cf0a9a427aec1..74177e6f230d9b7176bdaddd3007922cc99ccdb9 100644
+--- a/out/util/yarn.js
++++ b/out/util/yarn.js
+@@ -140,6 +140,7 @@ async function rebuild(config, { appDir, projectDir }, options) {
+         arch,
+         platform,
+         buildFromSource,
++        ignoreModules: options.excludeReBuildModules || undefined,
+         projectRootPath: projectDir,
+         mode: config.nativeRebuilder || "sequential",
+         disablePreGypCopy: true,
+diff --git a/scheme.json b/scheme.json
+index 433e2efc9cef156ff5444f0c4520362ed2ef9ea7..0167441bf928a92f59b5dbe70b2317a74dda74c9 100644
+--- a/scheme.json
++++ b/scheme.json
+@@ -1825,6 +1825,20 @@
+             "string"
+           ]
+         },
++        "excludeReBuildModules": {
++          "anyOf": [
++            {
++              "items": {
++                "type": "string"
++              },
++              "type": "array"
++            },
++            {
++              "type": "null"
++            }
++          ],
++          "description": "The modules to exclude from the rebuild."
++        },
+         "executableArgs": {
+           "anyOf": [
+             {
+@@ -1975,6 +1989,13 @@
+           ],
+           "description": "The mime types in addition to specified in the file associations. Use it if you don't want to register a new mime type, but reuse existing."
+         },
++        "minimumSystemVersion": {
++          "description": "The minimum os kernel version required to install the application.",
++          "type": [
++            "null",
++            "string"
++          ]
++        },
+         "packageCategory": {
+           "description": "backward compatibility + to allow specify fpm-only category for all possible fpm targets in one place",
+           "type": [
+@@ -2327,6 +2348,13 @@
+     "MacConfiguration": {
+       "additionalProperties": false,
+       "properties": {
++        "LSMinimumSystemVersion": {
++          "description": "The minimum version of macOS required for the app to run. Corresponds to `LSMinimumSystemVersion`.",
++          "type": [
++            "null",
++            "string"
++          ]
++        },
+         "additionalArguments": {
+           "anyOf": [
+             {
+@@ -2527,6 +2555,20 @@
+             "string"
+           ]
+         },
++        "excludeReBuildModules": {
++          "anyOf": [
++            {
++              "items": {
++                "type": "string"
++              },
++              "type": "array"
++            },
++            {
++              "type": "null"
++            }
++          ],
++          "description": "The modules to exclude from the rebuild."
++        },
+         "executableName": {
+           "description": "The executable name. Defaults to `productName`.",
+           "type": [
+@@ -2737,7 +2779,7 @@
+           "type": "boolean"
+         },
+         "minimumSystemVersion": {
+-          "description": "The minimum version of macOS required for the app to run. Corresponds to `LSMinimumSystemVersion`.",
++          "description": "The minimum os kernel version required to install the application.",
+           "type": [
+             "null",
+             "string"
+@@ -2959,6 +3001,13 @@
+     "MasConfiguration": {
+       "additionalProperties": false,
+       "properties": {
++        "LSMinimumSystemVersion": {
++          "description": "The minimum version of macOS required for the app to run. Corresponds to `LSMinimumSystemVersion`.",
++          "type": [
++            "null",
++            "string"
++          ]
++        },
+         "additionalArguments": {
+           "anyOf": [
+             {
+@@ -3159,6 +3208,20 @@
+             "string"
+           ]
+         },
++        "excludeReBuildModules": {
++          "anyOf": [
++            {
++              "items": {
++                "type": "string"
++              },
++              "type": "array"
++            },
++            {
++              "type": "null"
++            }
++          ],
++          "description": "The modules to exclude from the rebuild."
++        },
+         "executableName": {
+           "description": "The executable name. Defaults to `productName`.",
+           "type": [
+@@ -3369,7 +3432,7 @@
+           "type": "boolean"
+         },
+         "minimumSystemVersion": {
+-          "description": "The minimum version of macOS required for the app to run. Corresponds to `LSMinimumSystemVersion`.",
++          "description": "The minimum os kernel version required to install the application.",
+           "type": [
+             "null",
+             "string"
+@@ -6381,6 +6444,20 @@
+             "string"
+           ]
+         },
++        "excludeReBuildModules": {
++          "anyOf": [
++            {
++              "items": {
++                "type": "string"
++              },
++              "type": "array"
++            },
++            {
++              "type": "null"
++            }
++          ],
++          "description": "The modules to exclude from the rebuild."
++        },
+         "executableName": {
+           "description": "The executable name. Defaults to `productName`.",
+           "type": [
+@@ -6507,6 +6584,13 @@
+             "string"
+           ]
+         },
++        "minimumSystemVersion": {
++          "description": "The minimum os kernel version required to install the application.",
++          "type": [
++            "null",
++            "string"
++          ]
++        },
+         "protocols": {
+           "anyOf": [
+             {
+@@ -7153,6 +7237,20 @@
+         "string"
+       ]
+     },
++    "excludeReBuildModules": {
++      "anyOf": [
++        {
++          "items": {
++            "type": "string"
++          },
++          "type": "array"
++        },
++        {
++          "type": "null"
++        }
++      ],
++      "description": "The modules to exclude from the rebuild."
++    },
+     "executableName": {
+       "description": "The executable name. Defaults to `productName`.",
+       "type": [
+@@ -7376,6 +7474,13 @@
+       ],
+       "description": "MAS (Mac Application Store) development options (`mas-dev` target)."
+     },
++    "minimumSystemVersion": {
++      "description": "The minimum os kernel version required to install the application.",
++      "type": [
++        "null",
++        "string"
++      ]
++    },
+     "msi": {
+       "anyOf": [
+         {

.yarn/patches/atomically-npm-1.7.0-e742e5293b.patch

@@ -1,12 +0,0 @@
-diff --git a/dist/utils/temp.js b/dist/utils/temp.js
-index c0844f640f7927ff87edda13f7c853d10ebb8dd0..3ca3d29e0f4ee700c43ebde47002883955b664b3 100644
---- a/dist/utils/temp.js
-+++ b/dist/utils/temp.js
-@@ -2,6 +2,7 @@
- /* IMPORT */
- Object.defineProperty(exports, "__esModule", { value: true });
- const path = require("path");
-+const process = require("process");
- const consts_1 = require("../consts");
- const fs_1 = require("./fs");
- /* TEMP */

.yarn/patches/electron-updater-npm-6.7.0-47b11bb0d4.patch

@@ -1,14 +0,0 @@
-diff --git a/out/util.js b/out/util.js
-index 9294ffd6ca8f02c2e0f90c663e7e9cdc02c1ac37..f52107493e2995320ee4efd0eb2a8c9bf03291a2 100644
---- a/out/util.js
-+++ b/out/util.js
-@@ -23,7 +23,8 @@ function newUrlFromBase(pathname, baseUrl, addRandomQueryToAvoidCaching = false)
-         result.search = search;
-     }
-     else if (addRandomQueryToAvoidCaching) {
--        result.search = `noCache=${Date.now().toString(32)}`;
-+        // use no cache header instead
-+        // result.search = `noCache=${Date.now().toString(32)}`;
-     }
-     return result;
- }

.yarn/patches/file-stream-rotator-npm-0.6.1-eab45fb13d.patch

@@ -1,13 +0,0 @@
-diff --git a/FileStreamRotator.js b/FileStreamRotator.js
-index 639bb9c8f972ba672bd27d9f8b1739d1030cb44b..a12a6d93b61fe782e981027248fa10876151f65f 100644
---- a/FileStreamRotator.js
-+++ b/FileStreamRotator.js
-@@ -12,7 +12,7 @@
-  */
- var fs = require('fs');
- var path = require('path');
--var moment = require('moment');
-+var moment = require('moment').default || require('moment');
- var crypto = require('crypto');
- 
- var EventEmitter = require('events');

.yarn/patches/openai-npm-5.1.0-0e7b3ccb07.patch

@@ -0,0 +1,279 @@
+diff --git a/client.js b/client.js
+index 33b4ff6309d5f29187dab4e285d07dac20340bab..8f568637ee9e4677585931fb0284c8165a933f69 100644
+--- a/client.js
++++ b/client.js
+@@ -433,7 +433,7 @@ class OpenAI {
+                 'User-Agent': this.getUserAgent(),
+                 'X-Stainless-Retry-Count': String(retryCount),
+                 ...(options.timeout ? { 'X-Stainless-Timeout': String(Math.trunc(options.timeout / 1000)) } : {}),
+-                ...(0, detect_platform_1.getPlatformHeaders)(),
++                // ...(0, detect_platform_1.getPlatformHeaders)(),
+                 'OpenAI-Organization': this.organization,
+                 'OpenAI-Project': this.project,
+             },
+diff --git a/client.mjs b/client.mjs
+index c34c18213073540ebb296ea540b1d1ad39527906..1ce1a98256d7e90e26ca963582f235b23e996e73 100644
+--- a/client.mjs
++++ b/client.mjs
+@@ -430,7 +430,7 @@ export class OpenAI {
+                 'User-Agent': this.getUserAgent(),
+                 'X-Stainless-Retry-Count': String(retryCount),
+                 ...(options.timeout ? { 'X-Stainless-Timeout': String(Math.trunc(options.timeout / 1000)) } : {}),
+-                ...getPlatformHeaders(),
++                // ...getPlatformHeaders(),
+                 'OpenAI-Organization': this.organization,
+                 'OpenAI-Project': this.project,
+             },
+diff --git a/core/error.js b/core/error.js
+index a12d9d9ccd242050161adeb0f82e1b98d9e78e20..fe3a5462480558bc426deea147f864f12b36f9bd 100644
+--- a/core/error.js
++++ b/core/error.js
+@@ -40,7 +40,7 @@ class APIError extends OpenAIError {
+         if (!status || !headers) {
+             return new APIConnectionError({ message, cause: (0, errors_1.castToError)(errorResponse) });
+         }
+-        const error = errorResponse?.['error'];
++        const error = errorResponse?.['error'] || errorResponse;
+         if (status === 400) {
+             return new BadRequestError(status, error, message, headers);
+         }
+diff --git a/core/error.mjs b/core/error.mjs
+index 83cefbaffeb8c657536347322d8de9516af479a2..63334b7972ec04882aa4a0800c1ead5982345045 100644
+--- a/core/error.mjs
++++ b/core/error.mjs
+@@ -36,7 +36,7 @@ export class APIError extends OpenAIError {
+         if (!status || !headers) {
+             return new APIConnectionError({ message, cause: castToError(errorResponse) });
+         }
+-        const error = errorResponse?.['error'];
++        const error = errorResponse?.['error'] || errorResponse;
+         if (status === 400) {
+             return new BadRequestError(status, error, message, headers);
+         }
+diff --git a/resources/embeddings.js b/resources/embeddings.js
+index 2404264d4ba0204322548945ebb7eab3bea82173..8f1bc45cc45e0797d50989d96b51147b90ae6790 100644
+--- a/resources/embeddings.js
++++ b/resources/embeddings.js
+@@ -5,52 +5,64 @@ exports.Embeddings = void 0;
+ const resource_1 = require("../core/resource.js");
+ const utils_1 = require("../internal/utils.js");
+ class Embeddings extends resource_1.APIResource {
+-    /**
+-     * Creates an embedding vector representing the input text.
+-     *
+-     * @example
+-     * ```ts
+-     * const createEmbeddingResponse =
+-     *   await client.embeddings.create({
+-     *     input: 'The quick brown fox jumped over the lazy dog',
+-     *     model: 'text-embedding-3-small',
+-     *   });
+-     * ```
+-     */
+-    create(body, options) {
+-        const hasUserProvidedEncodingFormat = !!body.encoding_format;
+-        // No encoding_format specified, defaulting to base64 for performance reasons
+-        // See https://github.com/openai/openai-node/pull/1312
+-        let encoding_format = hasUserProvidedEncodingFormat ? body.encoding_format : 'base64';
+-        if (hasUserProvidedEncodingFormat) {
+-            (0, utils_1.loggerFor)(this._client).debug('embeddings/user defined encoding_format:', body.encoding_format);
+-        }
+-        const response = this._client.post('/embeddings', {
+-            body: {
+-                ...body,
+-                encoding_format: encoding_format,
+-            },
+-            ...options,
+-        });
+-        // if the user specified an encoding_format, return the response as-is
+-        if (hasUserProvidedEncodingFormat) {
+-            return response;
+-        }
+-        // in this stage, we are sure the user did not specify an encoding_format
+-        // and we defaulted to base64 for performance reasons
+-        // we are sure then that the response is base64 encoded, let's decode it
+-        // the returned result will be a float32 array since this is OpenAI API's default encoding
+-        (0, utils_1.loggerFor)(this._client).debug('embeddings/decoding base64 embeddings from base64');
+-        return response._thenUnwrap((response) => {
+-            if (response && response.data) {
+-                response.data.forEach((embeddingBase64Obj) => {
+-                    const embeddingBase64Str = embeddingBase64Obj.embedding;
+-                    embeddingBase64Obj.embedding = (0, utils_1.toFloat32Array)(embeddingBase64Str);
+-                });
+-            }
+-            return response;
+-        });
+-    }
++	/**
++	 * Creates an embedding vector representing the input text.
++	 *
++	 * @example
++	 * ```ts
++	 * const createEmbeddingResponse =
++	 *   await client.embeddings.create({
++	 *     input: 'The quick brown fox jumped over the lazy dog',
++	 *     model: 'text-embedding-3-small',
++	 *   });
++	 * ```
++	 */
++	create(body, options) {
++		const hasUserProvidedEncodingFormat = !!body.encoding_format;
++		// No encoding_format specified, defaulting to base64 for performance reasons
++		// See https://github.com/openai/openai-node/pull/1312
++		let encoding_format = hasUserProvidedEncodingFormat
++			? body.encoding_format
++			: "base64";
++		if (body.model.includes("jina")) {
++			encoding_format = undefined;
++		}
++		if (hasUserProvidedEncodingFormat) {
++			(0, utils_1.loggerFor)(this._client).debug(
++				"embeddings/user defined encoding_format:",
++				body.encoding_format
++			);
++		}
++		const response = this._client.post("/embeddings", {
++			body: {
++				...body,
++				encoding_format: encoding_format,
++			},
++			...options,
++		});
++		// if the user specified an encoding_format, return the response as-is
++		if (hasUserProvidedEncodingFormat || body.model.includes("jina")) {
++			return response;
++		}
++		// in this stage, we are sure the user did not specify an encoding_format
++		// and we defaulted to base64 for performance reasons
++		// we are sure then that the response is base64 encoded, let's decode it
++		// the returned result will be a float32 array since this is OpenAI API's default encoding
++		(0, utils_1.loggerFor)(this._client).debug(
++			"embeddings/decoding base64 embeddings from base64"
++		);
++		return response._thenUnwrap((response) => {
++			if (response && response.data && typeof response.data[0]?.embedding === 'string') {
++				response.data.forEach((embeddingBase64Obj) => {
++					const embeddingBase64Str = embeddingBase64Obj.embedding;
++					embeddingBase64Obj.embedding = (0, utils_1.toFloat32Array)(
++						embeddingBase64Str
++					);
++				});
++			}
++			return response;
++		});
++	}
+ }
+ exports.Embeddings = Embeddings;
+ //# sourceMappingURL=embeddings.js.map
+diff --git a/resources/embeddings.mjs b/resources/embeddings.mjs
+index 19dcaef578c194a89759c4360073cfd4f7dd2cbf..0284e9cc615c900eff508eb595f7360a74bd9200 100644
+--- a/resources/embeddings.mjs
++++ b/resources/embeddings.mjs
+@@ -2,51 +2,61 @@
+ import { APIResource } from "../core/resource.mjs";
+ import { loggerFor, toFloat32Array } from "../internal/utils.mjs";
+ export class Embeddings extends APIResource {
+-    /**
+-     * Creates an embedding vector representing the input text.
+-     *
+-     * @example
+-     * ```ts
+-     * const createEmbeddingResponse =
+-     *   await client.embeddings.create({
+-     *     input: 'The quick brown fox jumped over the lazy dog',
+-     *     model: 'text-embedding-3-small',
+-     *   });
+-     * ```
+-     */
+-    create(body, options) {
+-        const hasUserProvidedEncodingFormat = !!body.encoding_format;
+-        // No encoding_format specified, defaulting to base64 for performance reasons
+-        // See https://github.com/openai/openai-node/pull/1312
+-        let encoding_format = hasUserProvidedEncodingFormat ? body.encoding_format : 'base64';
+-        if (hasUserProvidedEncodingFormat) {
+-            loggerFor(this._client).debug('embeddings/user defined encoding_format:', body.encoding_format);
+-        }
+-        const response = this._client.post('/embeddings', {
+-            body: {
+-                ...body,
+-                encoding_format: encoding_format,
+-            },
+-            ...options,
+-        });
+-        // if the user specified an encoding_format, return the response as-is
+-        if (hasUserProvidedEncodingFormat) {
+-            return response;
+-        }
+-        // in this stage, we are sure the user did not specify an encoding_format
+-        // and we defaulted to base64 for performance reasons
+-        // we are sure then that the response is base64 encoded, let's decode it
+-        // the returned result will be a float32 array since this is OpenAI API's default encoding
+-        loggerFor(this._client).debug('embeddings/decoding base64 embeddings from base64');
+-        return response._thenUnwrap((response) => {
+-            if (response && response.data) {
+-                response.data.forEach((embeddingBase64Obj) => {
+-                    const embeddingBase64Str = embeddingBase64Obj.embedding;
+-                    embeddingBase64Obj.embedding = toFloat32Array(embeddingBase64Str);
+-                });
+-            }
+-            return response;
+-        });
+-    }
++	/**
++	 * Creates an embedding vector representing the input text.
++	 *
++	 * @example
++	 * ```ts
++	 * const createEmbeddingResponse =
++	 *   await client.embeddings.create({
++	 *     input: 'The quick brown fox jumped over the lazy dog',
++	 *     model: 'text-embedding-3-small',
++	 *   });
++	 * ```
++	 */
++	create(body, options) {
++		const hasUserProvidedEncodingFormat = !!body.encoding_format;
++		// No encoding_format specified, defaulting to base64 for performance reasons
++		// See https://github.com/openai/openai-node/pull/1312
++		let encoding_format = hasUserProvidedEncodingFormat
++			? body.encoding_format
++			: "base64";
++		if (body.model.includes("jina")) {
++			encoding_format = undefined;
++		}
++		if (hasUserProvidedEncodingFormat) {
++			loggerFor(this._client).debug(
++				"embeddings/user defined encoding_format:",
++				body.encoding_format
++			);
++		}
++		const response = this._client.post("/embeddings", {
++			body: {
++				...body,
++				encoding_format: encoding_format,
++			},
++			...options,
++		});
++		// if the user specified an encoding_format, return the response as-is
++		if (hasUserProvidedEncodingFormat || body.model.includes("jina")) {
++			return response;
++		}
++		// in this stage, we are sure the user did not specify an encoding_format
++		// and we defaulted to base64 for performance reasons
++		// we are sure then that the response is base64 encoded, let's decode it
++		// the returned result will be a float32 array since this is OpenAI API's default encoding
++		loggerFor(this._client).debug(
++			"embeddings/decoding base64 embeddings from base64"
++		);
++		return response._thenUnwrap((response) => {
++			if (response && response.data && typeof response.data[0]?.embedding === 'string') {
++				response.data.forEach((embeddingBase64Obj) => {
++					const embeddingBase64Str = embeddingBase64Obj.embedding;
++					embeddingBase64Obj.embedding = toFloat32Array(embeddingBase64Str);
++				});
++			}
++			return response;
++		});
++	}
+ }
+ //# sourceMappingURL=embeddings.mjs.map

.yarn/patches/tesseract.js-npm-6.0.1-2562a7e46d.patch

@@ -1,348 +0,0 @@
-diff --git a/src/constants/languages.d.ts b/src/constants/languages.d.ts
-new file mode 100644
-index 0000000000000000000000000000000000000000..6a2ba5086187622b8ca8887bcc7406018fba8a89
---- /dev/null
-+++ b/src/constants/languages.d.ts
-@@ -0,0 +1,43 @@
-+/**
-+ * Languages with existing tesseract traineddata
-+ * https://tesseract-ocr.github.io/tessdoc/Data-Files#data-files-for-version-400-november-29-2016
-+ */
-+
-+// Define the language codes as string literals
-+type LanguageCode =
-+  | 'afr' | 'amh' | 'ara' | 'asm' | 'aze' | 'aze_cyrl' | 'bel' | 'ben' | 'bod' | 'bos'
-+  | 'bul' | 'cat' | 'ceb' | 'ces' | 'chi_sim' | 'chi_tra' | 'chr' | 'cym' | 'dan' | 'deu'
-+  | 'dzo' | 'ell' | 'eng' | 'enm' | 'epo' | 'est' | 'eus' | 'fas' | 'fin' | 'fra'
-+  | 'frk' | 'frm' | 'gle' | 'glg' | 'grc' | 'guj' | 'hat' | 'heb' | 'hin' | 'hrv'
-+  | 'hun' | 'iku' | 'ind' | 'isl' | 'ita' | 'ita_old' | 'jav' | 'jpn' | 'kan' | 'kat'
-+  | 'kat_old' | 'kaz' | 'khm' | 'kir' | 'kor' | 'kur' | 'lao' | 'lat' | 'lav' | 'lit'
-+  | 'mal' | 'mar' | 'mkd' | 'mlt' | 'msa' | 'mya' | 'nep' | 'nld' | 'nor' | 'ori'
-+  | 'pan' | 'pol' | 'por' | 'pus' | 'ron' | 'rus' | 'san' | 'sin' | 'slk' | 'slv'
-+  | 'spa' | 'spa_old' | 'sqi' | 'srp' | 'srp_latn' | 'swa' | 'swe' | 'syr' | 'tam' | 'tel'
-+  | 'tgk' | 'tgl' | 'tha' | 'tir' | 'tur' | 'uig' | 'ukr' | 'urd' | 'uzb' | 'uzb_cyrl'
-+  | 'vie' | 'yid';
-+
-+// Define the language keys as string literals
-+type LanguageKey =
-+  | 'AFR' | 'AMH' | 'ARA' | 'ASM' | 'AZE' | 'AZE_CYRL' | 'BEL' | 'BEN' | 'BOD' | 'BOS'
-+  | 'BUL' | 'CAT' | 'CEB' | 'CES' | 'CHI_SIM' | 'CHI_TRA' | 'CHR' | 'CYM' | 'DAN' | 'DEU'
-+  | 'DZO' | 'ELL' | 'ENG' | 'ENM' | 'EPO' | 'EST' | 'EUS' | 'FAS' | 'FIN' | 'FRA'
-+  | 'FRK' | 'FRM' | 'GLE' | 'GLG' | 'GRC' | 'GUJ' | 'HAT' | 'HEB' | 'HIN' | 'HRV'
-+  | 'HUN' | 'IKU' | 'IND' | 'ISL' | 'ITA' | 'ITA_OLD' | 'JAV' | 'JPN' | 'KAN' | 'KAT'
-+  | 'KAT_OLD' | 'KAZ' | 'KHM' | 'KIR' | 'KOR' | 'KUR' | 'LAO' | 'LAT' | 'LAV' | 'LIT'
-+  | 'MAL' | 'MAR' | 'MKD' | 'MLT' | 'MSA' | 'MYA' | 'NEP' | 'NLD' | 'NOR' | 'ORI'
-+  | 'PAN' | 'POL' | 'POR' | 'PUS' | 'RON' | 'RUS' | 'SAN' | 'SIN' | 'SLK' | 'SLV'
-+  | 'SPA' | 'SPA_OLD' | 'SQI' | 'SRP' | 'SRP_LATN' | 'SWA' | 'SWE' | 'SYR' | 'TAM' | 'TEL'
-+  | 'TGK' | 'TGL' | 'THA' | 'TIR' | 'TUR' | 'UIG' | 'UKR' | 'URD' | 'UZB' | 'UZB_CYRL'
-+  | 'VIE' | 'YID';
-+
-+// Create a mapped type to ensure each key maps to its specific value
-+type LanguagesMap = {
-+  [K in LanguageKey]: LanguageCode;
-+};
-+
-+// Declare the exported constant with the specific type
-+export const LANGUAGES: LanguagesMap;
-+
-+// Export the individual types for use in other modules
-+export type { LanguageCode, LanguageKey, LanguagesMap };
-\ No newline at end of file
-diff --git a/src/index.d.ts b/src/index.d.ts
-index 1f5a9c8094fe4de7983467f9efb43bdb4de535f2..16dc95cf68663673e37e189b719cb74897b7735f 100644
---- a/src/index.d.ts
-+++ b/src/index.d.ts
-@@ -1,31 +1,74 @@
-+// Import the languages types
-+import { LanguagesMap } from "./constants/languages";
-+
-+/// <reference types="node" />
-+
- declare namespace Tesseract {
--  function createScheduler(): Scheduler
--  function createWorker(langs?: string | string[] | Lang[], oem?: OEM, options?: Partial<WorkerOptions>, config?: string | Partial<InitOptions>): Promise<Worker>
--  function setLogging(logging: boolean): void
--  function recognize(image: ImageLike, langs?: string, options?: Partial<WorkerOptions>): Promise<RecognizeResult>
--  function detect(image: ImageLike, options?: Partial<WorkerOptions>): any
-+  function createScheduler(): Scheduler;
-+  function createWorker(
-+    langs?: LanguageCode | LanguageCode[] | Lang[],
-+    oem?: OEM,
-+    options?: Partial<WorkerOptions>,
-+    config?: string | Partial<InitOptions>
-+  ): Promise<Worker>;
-+  function setLogging(logging: boolean): void;
-+  function recognize(
-+    image: ImageLike,
-+    langs?: LanguageCode,
-+    options?: Partial<WorkerOptions>
-+  ): Promise<RecognizeResult>;
-+  function detect(image: ImageLike, options?: Partial<WorkerOptions>): any;
-+
-+  // Export languages constant
-+  const languages: LanguagesMap;
-+
-+  type LanguageCode = import("./constants/languages").LanguageCode;
-+  type LanguageKey = import("./constants/languages").LanguageKey;
- 
-   interface Scheduler {
--    addWorker(worker: Worker): string
--    addJob(action: 'recognize', ...args: Parameters<Worker['recognize']>): Promise<RecognizeResult>
--    addJob(action: 'detect', ...args: Parameters<Worker['detect']>): Promise<DetectResult>
--    terminate(): Promise<any>
--    getQueueLen(): number
--    getNumWorkers(): number
-+    addWorker(worker: Worker): string;
-+    addJob(
-+      action: "recognize",
-+      ...args: Parameters<Worker["recognize"]>
-+    ): Promise<RecognizeResult>;
-+    addJob(
-+      action: "detect",
-+      ...args: Parameters<Worker["detect"]>
-+    ): Promise<DetectResult>;
-+    terminate(): Promise<any>;
-+    getQueueLen(): number;
-+    getNumWorkers(): number;
-   }
- 
-   interface Worker {
--    load(jobId?: string): Promise<ConfigResult>
--    writeText(path: string, text: string, jobId?: string): Promise<ConfigResult>
--    readText(path: string, jobId?: string): Promise<ConfigResult>
--    removeText(path: string, jobId?: string): Promise<ConfigResult>
--    FS(method: string, args: any[], jobId?: string): Promise<ConfigResult>
--    reinitialize(langs?: string | Lang[], oem?: OEM, config?: string | Partial<InitOptions>, jobId?: string): Promise<ConfigResult>
--    setParameters(params: Partial<WorkerParams>, jobId?: string): Promise<ConfigResult>
--    getImage(type: imageType): string
--    recognize(image: ImageLike, options?: Partial<RecognizeOptions>, output?: Partial<OutputFormats>, jobId?: string): Promise<RecognizeResult>
--    detect(image: ImageLike, jobId?: string): Promise<DetectResult>
--    terminate(jobId?: string): Promise<ConfigResult>
-+    load(jobId?: string): Promise<ConfigResult>;
-+    writeText(
-+      path: string,
-+      text: string,
-+      jobId?: string
-+    ): Promise<ConfigResult>;
-+    readText(path: string, jobId?: string): Promise<ConfigResult>;
-+    removeText(path: string, jobId?: string): Promise<ConfigResult>;
-+    FS(method: string, args: any[], jobId?: string): Promise<ConfigResult>;
-+    reinitialize(
-+      langs?: string | Lang[],
-+      oem?: OEM,
-+      config?: string | Partial<InitOptions>,
-+      jobId?: string
-+    ): Promise<ConfigResult>;
-+    setParameters(
-+      params: Partial<WorkerParams>,
-+      jobId?: string
-+    ): Promise<ConfigResult>;
-+    getImage(type: imageType): string;
-+    recognize(
-+      image: ImageLike,
-+      options?: Partial<RecognizeOptions>,
-+      output?: Partial<OutputFormats>,
-+      jobId?: string
-+    ): Promise<RecognizeResult>;
-+    detect(image: ImageLike, jobId?: string): Promise<DetectResult>;
-+    terminate(jobId?: string): Promise<ConfigResult>;
-   }
- 
-   interface Lang {
-@@ -34,43 +77,43 @@ declare namespace Tesseract {
-   }
- 
-   interface InitOptions {
--    load_system_dawg: string
--    load_freq_dawg: string
--    load_unambig_dawg: string
--    load_punc_dawg: string
--    load_number_dawg: string
--    load_bigram_dawg: string
--  }
--  
--  type LoggerMessage = {
--    jobId: string
--    progress: number
--    status: string
--    userJobId: string
--    workerId: string
-+    load_system_dawg: string;
-+    load_freq_dawg: string;
-+    load_unambig_dawg: string;
-+    load_punc_dawg: string;
-+    load_number_dawg: string;
-+    load_bigram_dawg: string;
-   }
--  
-+
-+  type LoggerMessage = {
-+    jobId: string;
-+    progress: number;
-+    status: string;
-+    userJobId: string;
-+    workerId: string;
-+  };
-+
-   interface WorkerOptions {
--    corePath: string
--    langPath: string
--    cachePath: string
--    dataPath: string
--    workerPath: string
--    cacheMethod: string
--    workerBlobURL: boolean
--    gzip: boolean
--    legacyLang: boolean
--    legacyCore: boolean
--    logger: (arg: LoggerMessage) => void,
--    errorHandler: (arg: any) => void
-+    corePath: string;
-+    langPath: string;
-+    cachePath: string;
-+    dataPath: string;
-+    workerPath: string;
-+    cacheMethod: string;
-+    workerBlobURL: boolean;
-+    gzip: boolean;
-+    legacyLang: boolean;
-+    legacyCore: boolean;
-+    logger: (arg: LoggerMessage) => void;
-+    errorHandler: (arg: any) => void;
-   }
-   interface WorkerParams {
--    tessedit_pageseg_mode: PSM
--    tessedit_char_whitelist: string
--    tessedit_char_blacklist: string
--    preserve_interword_spaces: string
--    user_defined_dpi: string
--    [propName: string]: any
-+    tessedit_pageseg_mode: PSM;
-+    tessedit_char_whitelist: string;
-+    tessedit_char_blacklist: string;
-+    preserve_interword_spaces: string;
-+    user_defined_dpi: string;
-+    [propName: string]: any;
-   }
-   interface OutputFormats {
-     text: boolean;
-@@ -88,36 +131,36 @@ declare namespace Tesseract {
-     debug: boolean;
-   }
-   interface RecognizeOptions {
--    rectangle: Rectangle
--    pdfTitle: string
--    pdfTextOnly: boolean
--    rotateAuto: boolean
--    rotateRadians: number
-+    rectangle: Rectangle;
-+    pdfTitle: string;
-+    pdfTextOnly: boolean;
-+    rotateAuto: boolean;
-+    rotateRadians: number;
-   }
-   interface ConfigResult {
--    jobId: string
--    data: any
-+    jobId: string;
-+    data: any;
-   }
-   interface RecognizeResult {
--    jobId: string
--    data: Page
-+    jobId: string;
-+    data: Page;
-   }
-   interface DetectResult {
--    jobId: string
--    data: DetectData
-+    jobId: string;
-+    data: DetectData;
-   }
-   interface DetectData {
--    tesseract_script_id: number | null
--    script: string | null
--    script_confidence: number | null
--    orientation_degrees: number | null
--    orientation_confidence: number | null
-+    tesseract_script_id: number | null;
-+    script: string | null;
-+    script_confidence: number | null;
-+    orientation_degrees: number | null;
-+    orientation_confidence: number | null;
-   }
-   interface Rectangle {
--    left: number
--    top: number
--    width: number
--    height: number
-+    left: number;
-+    top: number;
-+    width: number;
-+    height: number;
-   }
-   enum OEM {
-     TESSERACT_ONLY,
-@@ -126,28 +169,36 @@ declare namespace Tesseract {
-     DEFAULT,
-   }
-   enum PSM {
--    OSD_ONLY = '0',
--    AUTO_OSD = '1',
--    AUTO_ONLY = '2',
--    AUTO = '3',
--    SINGLE_COLUMN = '4',
--    SINGLE_BLOCK_VERT_TEXT = '5',
--    SINGLE_BLOCK = '6',
--    SINGLE_LINE = '7',
--    SINGLE_WORD = '8',
--    CIRCLE_WORD = '9',
--    SINGLE_CHAR = '10',
--    SPARSE_TEXT = '11',
--    SPARSE_TEXT_OSD = '12',
--    RAW_LINE = '13'
-+    OSD_ONLY = "0",
-+    AUTO_OSD = "1",
-+    AUTO_ONLY = "2",
-+    AUTO = "3",
-+    SINGLE_COLUMN = "4",
-+    SINGLE_BLOCK_VERT_TEXT = "5",
-+    SINGLE_BLOCK = "6",
-+    SINGLE_LINE = "7",
-+    SINGLE_WORD = "8",
-+    CIRCLE_WORD = "9",
-+    SINGLE_CHAR = "10",
-+    SPARSE_TEXT = "11",
-+    SPARSE_TEXT_OSD = "12",
-+    RAW_LINE = "13",
-   }
-   const enum imageType {
-     COLOR = 0,
-     GREY = 1,
--    BINARY = 2
-+    BINARY = 2,
-   }
--  type ImageLike = string | HTMLImageElement | HTMLCanvasElement | HTMLVideoElement
--    | CanvasRenderingContext2D | File | Blob | Buffer | OffscreenCanvas;
-+  type ImageLike =
-+    | string
-+    | HTMLImageElement
-+    | HTMLCanvasElement
-+    | HTMLVideoElement
-+    | CanvasRenderingContext2D
-+    | File
-+    | Blob
-+    | (typeof Buffer extends undefined ? never : Buffer)
-+    | OffscreenCanvas;
-   interface Block {
-     paragraphs: Paragraph[];
-     text: string;
-@@ -179,7 +230,7 @@ declare namespace Tesseract {
-     text: string;
-     confidence: number;
-     baseline: Baseline;
--    rowAttributes: RowAttributes
-+    rowAttributes: RowAttributes;
-     bbox: Bbox;
-   }
-   interface Paragraph {

.yarnrc.yml

@@ -5,5 +5,3 @@ httpTimeout: 300000
 nodeLinker: node-modules
 
 yarnPath: .yarn/releases/yarn-4.9.1.cjs
-npmRegistryServer: https://registry.npmjs.org
-npmPublishRegistry: https://registry.npmjs.org

AGENTS.md

@@ -1 +0,0 @@
-CLAUDE.md

CLAUDE.md

@@ -1,59 +0,0 @@
-# AI Assistant Guide
-
-This file provides guidance to AI coding assistants when working with code in this repository. Adherence to these guidelines is crucial for maintaining code quality and consistency.
-
-## Guiding Principles (MUST FOLLOW)
-
-- **Keep it clear**: Write code that is easy to read, maintain, and explain.
-- **Match the house style**: Reuse existing patterns, naming, and conventions.
-- **Search smart**: Prefer `ast-grep` for semantic queries; fall back to `rg`/`grep` when needed.
-- **Log centrally**: Route all logging through `loggerService` with the right context—no `console.log`.
-- **Research via subagent**: Lean on `subagent` for external docs, APIs, news, and references.
-- **Always propose before executing**: Before making any changes, clearly explain your planned approach and wait for explicit user approval to ensure alignment and prevent unwanted modifications.
-- **Lint, test, and format before completion**: Coding tasks are only complete after running `yarn lint`, `yarn test`, and `yarn format` successfully.
-- **Write conventional commits**: Commit small, focused changes using Conventional Commit messages (e.g., `feat:`, `fix:`, `refactor:`, `docs:`).
-
-## Pull Request Workflow (CRITICAL)
-
-When creating a Pull Request, you MUST:
-
-1. **Read the PR template first**: Always read `.github/pull_request_template.md` before creating the PR
-2. **Follow ALL template sections**: Structure the `--body` parameter to include every section from the template
-3. **Never skip sections**: Include all sections even if marking them as N/A or "None"
-4. **Use proper formatting**: Match the template's markdown structure exactly (headings, checkboxes, code blocks)
-
-## Development Commands
-
-- **Install**: `yarn install` - Install all project dependencies
-- **Development**: `yarn dev` - Runs Electron app in development mode with hot reload
-- **Debug**: `yarn debug` - Starts with debugging enabled, use `chrome://inspect` to attach debugger
-- **Build Check**: `yarn build:check` - **REQUIRED** before commits (lint + test + typecheck)
-  - If having i18n sort issues, run `yarn sync:i18n` first to sync template
-  - If having formatting issues, run `yarn format` first
-- **Test**: `yarn test` - Run all tests (Vitest) across main and renderer processes
-- **Single Test**:
-  - `yarn test:main` - Run tests for main process only
-  - `yarn test:renderer` - Run tests for renderer process only
-- **Lint**: `yarn lint` - Fix linting issues and run TypeScript type checking
-- **Format**: `yarn format` - Auto-format code using Biome
-
-## Project Architecture
-
-### Electron Structure
-- **Main Process** (`src/main/`): Node.js backend with services (MCP, Knowledge, Storage, etc.)
-- **Renderer Process** (`src/renderer/`): React UI with Redux state management
-- **Preload Scripts** (`src/preload/`): Secure IPC bridge
-
-### Key Components
-- **AI Core** (`src/renderer/src/aiCore/`): Middleware pipeline for multiple AI providers.
-- **Services** (`src/main/services/`): MCPService, KnowledgeService, WindowService, etc.
-- **Build System**: Electron-Vite with experimental rolldown-vite, yarn workspaces.
-- **State Management**: Redux Toolkit (`src/renderer/src/store/`) for predictable state.
-
-### Logging
-```typescript
-import { loggerService } from '@logger'
-const logger = loggerService.withContext('moduleName')
-// Renderer: loggerService.initWindowSource('windowName') first
-logger.info('message', CONTEXT)
-```

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-[中文](docs/zh/guides/contributing.md) | [English](CONTRIBUTING.md)
+[中文](./docs/CONTRIBUTING.zh.md) | [English](./CONTRIBUTING.md)
 
 # Cherry Studio Contributor Guide
 
@@ -32,7 +32,7 @@ To help you get familiar with the codebase, we recommend tackling issues tagged
 
 ### Testing
 
-Features without tests are considered non-existent. To ensure code is truly effective, relevant processes should be covered by unit tests and functional tests. Therefore, when considering contributions, please also consider testability. All tests can be run locally without dependency on CI. Please refer to the "Testing" section in the [Developer Guide](docs/zh/guides/development.md).
+Features without tests are considered non-existent. To ensure code is truly effective, relevant processes should be covered by unit tests and functional tests. Therefore, when considering contributions, please also consider testability. All tests can be run locally without dependency on CI. Please refer to the "Testing" section in the [Developer Guide](docs/dev.md).
 
 ### Automated Testing for Pull Requests
 
@@ -58,35 +58,10 @@ git commit --signoff -m "Your commit message"
 
 Maintainers are here to help you implement your use case within a reasonable timeframe. They will do their best to review your code and provide constructive feedback promptly. However, if you get stuck during the review process or feel your Pull Request is not receiving the attention it deserves, please contact us via comments in the Issue or through the [Community](README.md#-community).
 
-### Participating in the Test Plan
-
-The Test Plan aims to provide users with a more stable application experience and faster iteration speed. For details, please refer to the [Test Plan](docs/en/guides/test-plan.md).
-
 ### Other Suggestions
 
 - **Contact Developers**: Before submitting a PR, you can contact the developers first to discuss or get help.
-
-## Important Contribution Guidelines & Focus Areas
-
-Please review the following critical information before submitting your Pull Request:
-
-### Temporary Restriction on Data-Changing Feature PRs 🚫
-
-**Currently, we are NOT accepting feature Pull Requests that introduce changes to our Redux data models or IndexedDB schemas.**
-
-Our core team is currently focused on significant architectural updates that involve these data structures. To ensure stability and focus during this period, contributions of this nature will be temporarily managed internally.
-
-*   **PRs that require changes to Redux state shape or IndexedDB schemas will be closed.**
-*   **This restriction is temporary and will be lifted with the release of `v2.0.0`.** You can track the progress of `v2.0.0` and its related discussions on issue [#10162](https://github.com/CherryHQ/cherry-studio/pull/10162).
-
-We highly encourage contributions for:
-*   Bug fixes 🐞
-*   Performance improvements 🚀
-*   Documentation updates 📚
-*   Features that **do not** alter Redux data models or IndexedDB schemas (e.g., UI enhancements, new components, minor refactors). ✨
-
-We appreciate your understanding and continued support during this important development phase. Thank you!
-
+- **Become a Core Developer**: If you contribute to the project consistently, congratulations, you can become a core developer and gain project membership status. Please check our [Membership Guide](https://github.com/CherryHQ/community/blob/main/docs/membership.en.md).
 
 ## Contact Us
 

LICENSE

@@ -1,661 +1,87 @@
-                    GNU AFFERO GENERAL PUBLIC LICENSE
-                       Version 3, 19 November 2007
+**许可协议 (Licensing)**
 
- Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
+本项目采用**区分用户的双重许可 (User-Segmented Dual Licensing)** 模式。
 
-                            Preamble
+**核心原则：**
 
-  The GNU Affero General Public License is a free, copyleft license for
-software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
+* **个人用户 和 10人及以下企业/组织:** 默认适用 **GNU Affero 通用公共许可证 v3.0 (AGPLv3)**。  
+* **超过10人的企业/组织:** **必须** 获取 **商业许可证 (Commercial License)**。
 
-  The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works.  By contrast,
-our General Public Licenses are intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.
+定义：“10人及以下”  
+指在您的组织（包括公司、非营利组织、政府机构、教育机构等任何实体）中，能够访问、使用或以任何方式直接或间接受益于本软件（Cherry Studio）功能的个人总数不超过10人。这包括但不限于开发者、测试人员、运营人员、最终用户、通过集成系统间接使用者等。
 
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
+---
 
-  Developers that use our General Public Licenses protect your rights
-with two steps: (1) assert copyright on the software, and (2) offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
+**1. 开源许可证 (Open Source License): AGPLv3 - 适用于个人及10人及以下组织**
 
-  A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate.  Many developers of free software are heartened and
-encouraged by the resulting cooperation.  However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
+* 如果您是个人用户，或者您的组织满足上述“10人及以下”的定义，您可以在 **AGPLv3** 的条款下自由使用、修改和分发 Cherry Studio。AGPLv3 的完整文本可以访问 [https://www.gnu.org/licenses/agpl-3.0.html](https://www.gnu.org/licenses/agpl-3.0.html) 获取。  
+* **核心义务：** AGPLv3 的一个关键要求是，如果您修改了 Cherry Studio 并通过网络提供服务，或者分发了修改后的版本，您必须以 AGPLv3 许可证向接收者提供相应的**完整源代码**。即使您符合“10人及以下”的标准，如果您希望避免此源代码公开义务，您也需要考虑获取商业许可证（见下文）。  
+* 使用前请务必仔细阅读并理解 AGPLv3 的所有条款。
 
-  The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community.  It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server.  Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
+**2. 商业许可证 (Commercial License) - 适用于超过10人的组织，或希望规避 AGPLv3 义务的用户**
 
-  An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals.  This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
+* **强制要求：** 如果您的组织**不**满足上述“10人及以下”的定义（即有11人或更多人可以访问、使用或受益于本软件），您**必须**联系我们获取并签署一份商业许可证才能使用 Cherry Studio。  
+* **自愿选择：** 即使您的组织满足“10人及以下”的条件，但如果您的使用场景**无法满足 AGPLv3 的条款要求**（特别是关于**源代码公开**的义务），或者您需要 AGPLv3 **未提供**的特定商业条款（如保证、赔偿、无 Copyleft 限制等），您也**必须**联系我们获取并签署一份商业许可证。  
+* **需要商业许可证的常见情况包括（但不限于）：**  
+  * 您的组织规模超过10人。  
+  * （无论组织规模）您希望分发修改过的 Cherry Studio 版本，但**不希望**根据 AGPLv3 公开您修改部分的源代码。  
+  * （无论组织规模）您希望基于修改过的 Cherry Studio 提供网络服务（SaaS），但**不希望**根据 AGPLv3 向服务使用者提供修改后的源代码。  
+  * （无论组织规模）您的公司政策、客户合同或项目要求不允许使用 AGPLv3 许可的软件，或要求闭源分发及保密。  
+* 商业许可证将为您提供豁免 AGPLv3 义务（如源代码公开）的权利，并可能包含额外的商业保障条款。  
+* **获取商业许可：** 请通过邮箱 **bd@cherry-ai.com** 联系 Cherry Studio 开发团队洽谈商业授权事宜。
 
-  The precise terms and conditions for copying, distribution and
-modification follow.
+**3. 贡献 (Contributions)**
 
-                       TERMS AND CONDITIONS
+* 我们欢迎社区对 Cherry Studio 的贡献。所有向本项目提交的贡献都将被视为在 **AGPLv3** 许可证下提供。  
+* 通过向本项目提交贡献（例如通过 Pull Request），即表示您同意您的代码以 AGPLv3 许可证授权给本项目及所有后续使用者（无论这些使用者最终遵循 AGPLv3 还是商业许可）。  
+* 您也理解并同意，您的贡献可能会被包含在根据商业许可证分发的 Cherry Studio 版本中。
 
-  0. Definitions.
+**4. 其他条款 (Other Terms)**
 
-  "This License" refers to version 3 of the GNU Affero General Public License.
+* 关于商业许可证的具体条款和条件，以双方签署的正式商业许可协议为准。  
+* 项目维护者保留根据需要更新本许可政策（包括用户规模定义和阈值）的权利。相关更新将通过项目官方渠道（如代码仓库、官方网站）进行通知。
 
-  "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
+---
 
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
+**Licensing**
 
-  To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
+This project employs a **User-Segmented Dual Licensing** model.
 
-  A "covered work" means either the unmodified Program or a work based
-on the Program.
+**Core Principle:**
 
-  To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy.  Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
+* **Individual Users and Organizations with 10 or Fewer Individuals:** Governed by default under the **GNU Affero General Public License v3.0 (AGPLv3)**.  
+* **Organizations with More Than 10 Individuals:** **Must** obtain a **Commercial License**.
 
-  To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies.  Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
+Definition: "10 or Fewer Individuals"  
+Refers to any organization (including companies, non-profits, government agencies, educational institutions, etc.) where the total number of individuals who can access, use, or in any way directly or indirectly benefit from the functionality of this software (Cherry Studio) does not exceed 10. This includes, but is not limited to, developers, testers, operations staff, end-users, and indirect users via integrated systems.
 
-  An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License.  If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
+---
 
-  1. Source Code.
+**1. Open Source License: AGPLv3 - For Individuals and Organizations of 10 or Fewer**
 
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
-form of a work.
+* If you are an individual user, or if your organization meets the "10 or Fewer Individuals" definition above, you are free to use, modify, and distribute Cherry Studio under the terms of the **AGPLv3**. The full text of the AGPLv3 can be found in the LICENSE file at [https://www.gnu.org/licenses/agpl-3.0.html](https://www.gnu.org/licenses/agpl-3.0.html).  
+* **Core Obligation:** A key requirement of the AGPLv3 is that if you modify Cherry Studio and make it available over a network, or distribute the modified version, you must provide the **complete corresponding source code** under the AGPLv3 license to the recipients. Even if you qualify under the "10 or Fewer Individuals" rule, if you wish to avoid this source code disclosure obligation, you will need to obtain a Commercial License (see below).  
+* Please read and understand the full terms of the AGPLv3 carefully before use.
 
-  A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
+**2. Commercial License - For Organizations with More Than 10 Individuals, or Users Needing to Avoid AGPLv3 Obligations**
 
-  The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form.  A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
+* **Mandatory Requirement:** If your organization does **not** meet the "10 or Fewer Individuals" definition above (i.e., 11 or more individuals can access, use, or benefit from the software), you **must** contact us to obtain and execute a Commercial License to use Cherry Studio.  
+* **Voluntary Option:** Even if your organization meets the "10 or Fewer Individuals" condition, if your intended use case **cannot comply with the terms of the AGPLv3** (particularly the obligations regarding **source code disclosure**), or if you require specific commercial terms **not offered** by the AGPLv3 (such as warranties, indemnities, or freedom from copyleft restrictions), you also **must** contact us to obtain and execute a Commercial License.  
+* **Common scenarios requiring a Commercial License include (but are not limited to):**  
+  * Your organization has more than 10 individuals who can access, use, or benefit from the software.  
+  * (Regardless of organization size) You wish to distribute a modified version of Cherry Studio but **do not want** to disclose the source code of your modifications under AGPLv3.  
+  * (Regardless of organization size) You wish to provide a network service (SaaS) based on a modified version of Cherry Studio but **do not want** to provide the modified source code to users of the service under AGPLv3.  
+  * (Regardless of organization size) Your corporate policies, client contracts, or project requirements prohibit the use of AGPLv3-licensed software or mandate closed-source distribution and confidentiality.  
+* The Commercial License grants you rights exempting you from AGPLv3 obligations (like source code disclosure) and may include additional commercial assurances.  
+* **Obtaining a Commercial License:** Please contact the Cherry Studio development team via email at **bd@cherry-ai.com** to discuss commercial licensing options.
 
-  The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities.  However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work.  For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
+**3. Contributions**
 
-  The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
+* We welcome community contributions to Cherry Studio. All contributions submitted to this project are considered to be offered under the **AGPLv3** license.  
+* By submitting a contribution to this project (e.g., via a Pull Request), you agree to license your code under the AGPLv3 to the project and all its downstream users (regardless of whether those users ultimately operate under AGPLv3 or a Commercial License).  
+* You also understand and agree that your contribution may be included in distributions of Cherry Studio offered under our commercial license.
 
-  The Corresponding Source for a work in source code form is that
-same work.
+**4. Other Terms**
 
-  2. Basic Permissions.
-
-  All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met.  This License explicitly affirms your unlimited
-permission to run the unmodified Program.  The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work.  This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-  You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force.  You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright.  Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-  Conveying under any other circumstances is permitted solely under
-the conditions stated below.  Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-  No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-  When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-  4. Conveying Verbatim Copies.
-
-  You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-  You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-  5. Conveying Modified Source Versions.
-
-  You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-  A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit.  Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-  6. Conveying Non-Source Forms.
-
-  You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-
-  A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source.  The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-  If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information.  But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-  Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-  7. Additional Terms.
-
-  "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law.  If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-  When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it.  (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.)  You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-  Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-
-  All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10.  If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term.  If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-  If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-  Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-  8. Termination.
-
-  You may not propagate or modify a covered work except as expressly
-provided under this License.  Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-  However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-  Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-  Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License.  If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-  9. Acceptance Not Required for Having Copies.
-
-  You are not required to accept this License in order to receive or
-run a copy of the Program.  Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance.  However,
-nothing other than this License grants you permission to propagate or
-modify any covered work.  These actions infringe copyright if you do
-not accept this License.  Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-  10. Automatic Licensing of Downstream Recipients.
-
-  Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License.  You are not responsible
-for enforcing compliance by third parties with this License.
-
-  An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations.  If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-  You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License.  For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-  11. Patents.
-
-  A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based.  The
-work thus licensed is called the contributor's "contributor version".
-
-  A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version.  For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-  Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-  In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement).  To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-  If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients.  "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-  If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-  A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License.  You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-  Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-  12. No Surrender of Others' Freedom.
-
-  If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all.  For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-  13. Remote Network Interaction; Use with the GNU General Public License.
-
-  Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users
-interacting with it remotely through a computer network (if your version
-supports such interaction) an opportunity to receive the Corresponding
-Source of your version by providing access to the Corresponding Source
-from a network server at no charge, through some standard or customary
-means of facilitating copying of software.  This Corresponding Source
-shall include the Corresponding Source for any work covered by version 3
-of the GNU General Public License that is incorporated pursuant to the
-following paragraph.
-
-  Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU General Public License into a single
-combined work, and to convey the resulting work.  The terms of this
-License will continue to apply to the part which is the covered work,
-but the work with which it is combined will remain governed by version
-3 of the GNU General Public License.
-
-  14. Revised Versions of this License.
-
-  The Free Software Foundation may publish revised and/or new versions of
-the GNU Affero General Public License from time to time.  Such new versions
-will be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-  Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU Affero General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation.  If the Program does not specify a version number of the
-GNU Affero General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
-  If the Program specifies that a proxy can decide which future
-versions of the GNU Affero General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
-  Later license versions may give you additional or different
-permissions.  However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-  15. Disclaimer of Warranty.
-
-  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-  16. Limitation of Liability.
-
-  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
-  17. Interpretation of Sections 15 and 16.
-
-  If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-                     END OF TERMS AND CONDITIONS
-
-            How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU Affero General Public License as published by
-    the Free Software Foundation, either version 3 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU Affero General Public License for more details.
-
-    You should have received a copy of the GNU Affero General Public License
-    along with this program.  If not, see <https://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-  If your software can interact with users remotely through a computer
-network, you should also make sure that it provides a way for users to
-get its source.  For example, if your program is a web application, its
-interface could display a "Source" link that leads users to an archive
-of the code.  There are many ways you could offer source, and different
-solutions will be better for different programs; see section 13 for the
-specific requirements.
-
-  You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU AGPL, see
-<https://www.gnu.org/licenses/>.
+* The specific terms and conditions of the Commercial License are governed by the formal commercial license agreement signed by both parties.  
+* The project maintainers reserve the right to update this licensing policy (including the definition and threshold for user count) as needed. Updates will be communicated through official project channels (e.g., code repository, official website).

README.md

@@ -13,7 +13,7 @@
         <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=fr">Français</a></p>
         <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=de">Deutsch</a></p>
         <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=es">Español</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=it">Italiano</a></p>
+        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=it">Itapano</a></p>
         <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=ru">Русский</a></p>
         <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=pt">Português</a></p>
         <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=nl">Nederlands</a></p>
@@ -33,8 +33,9 @@
     <img src="https://github.com/CherryHQ/cherry-studio/blob/main/build/icon.png?raw=true" width="150" height="150" alt="banner" /><br>
   </a>
 </h1>
+  <p align="center">English | <a href="./docs/README.zh.md">中文</a> | <a href="./docs/README.ja.md">日本語</a> | <a href="https://cherry-ai.com">Official Site</a> | <a href="https://docs.cherry-ai.com/cherry-studio-wen-dang/en-us">Documents</a> | <a href="./docs/dev.md">Development</a> | <a href="https://github.com/CherryHQ/cherry-studio/issues">Feedback</a><br></p>
 
-<p align="center">English | <a href="./docs/zh/README.md">中文</a> | <a href="https://cherry-ai.com">Official Site</a> | <a href="https://docs.cherry-ai.com/cherry-studio-wen-dang/en-us">Documents</a> | <a href="./docs/en/guides/development.md">Development</a> | <a href="https://github.com/CherryHQ/cherry-studio/issues">Feedback</a><br></p>
+<!-- 题头徽章组合 -->
 
 <div align="center">
 
@@ -44,11 +45,20 @@
 [![][telegram-shield]][telegram-link]
 
 </div>
+
+<!-- 项目统计徽章 -->
+
 <div align="center">
 
+[![][github-stars-shield]][github-stars-link]
+[![][github-forks-shield]][github-forks-link]
 [![][github-release-shield]][github-release-link]
-[![][github-nightly-shield]][github-nightly-link]
 [![][github-contributors-shield]][github-contributors-link]
+
+</div>
+
+<div align="center">
+
 [![][license-shield]][license-link]
 [![][commercial-shield]][commercial-link]
 [![][sponsor-shield]][sponsor-link]
@@ -56,18 +66,18 @@
 </div>
 
 <div align="center">
- <a href="https://hellogithub.com/repository/1605492e1e2a4df3be07abfa4578dd37" target="_blank" style="text-decoration: none"><img src="https://api.hellogithub.com/v1/widgets/recommend.svg?rid=1605492e1e2a4df3be07abfa4578dd37" alt="Featured｜HelloGitHub"  width="220" height="55" /></a>
- <a href="https://trendshift.io/repositories/14318" target="_blank" style="text-decoration: none"><img src="https://trendshift.io/api/badge/repositories/14318" alt="CherryHQ%2Fcherry-studio | Trendshift" width="220" height="55" /></a>
- <a href="https://www.producthunt.com/posts/cherry-studio?embed=true&utm_source=badge-featured&utm_medium=badge&utm_souce=badge-cherry&#0045;studio" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=496640&theme=light" alt="Cherry&#0032;Studio - AI&#0032;Chatbots&#0044;&#0032;AI&#0032;Desktop&#0032;Client | Product Hunt" width="220" height="55" /></a>
+ <a href="https://hellogithub.com/repository/1605492e1e2a4df3be07abfa4578dd37" target="_blank"><img src="https://api.hellogithub.com/v1/widgets/recommend.svg?rid=1605492e1e2a4df3be07abfa4578dd37" alt="Featured｜HelloGitHub" style="width: 200px; height: 43px;" width="200" height="43" /></a>
+ <a href="https://trendshift.io/repositories/11772" target="_blank"><img src="https://trendshift.io/api/badge/repositories/11772" alt="kangfenmao%2Fcherry-studio | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
+ <a href="https://www.producthunt.com/posts/cherry-studio?embed=true&utm_source=badge-featured&utm_medium=badge&utm_souce=badge-cherry&#0045;studio" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=496640&theme=light" alt="Cherry&#0032;Studio - AI&#0032;Chatbots&#0044;&#0032;AI&#0032;Desktop&#0032;Client | Product Hunt" style="width: 200px; height: 43px;" width="200" height="43" /></a>
 </div>
 
 # 🍒 Cherry Studio
 
-Cherry Studio is a desktop client that supports multiple LLM providers, available on Windows, Mac and Linux.
+Cherry Studio is a desktop client that supports for multiple LLM providers, available on Windows, Mac and Linux.
 
 👏 Join [Telegram Group](https://t.me/CherryStudioAI)｜[Discord](https://discord.gg/wez8HtpxqQ) | [QQ Group(575014769)](https://qm.qq.com/q/lo0D4qVZKi)
 
-❤️ Like Cherry Studio? Give it a star 🌟 or [Sponsor](docs/zh/guides/sponsor.md) to support the development!
+❤️ Like Cherry Studio? Give it a star 🌟 or [Sponsor](docs/sponsor.md) to support the development!
 
 # 🌠 Screenshot
 
@@ -82,7 +92,7 @@ Cherry Studio is a desktop client that supports multiple LLM providers, availabl
 1. **Diverse LLM Provider Support**:
 
 - ☁️ Major LLM Cloud Services: OpenAI, Gemini, Anthropic, and more
-- 🔗 AI Web Service Integration: Claude, Perplexity, [Poe](https://poe.com/), and others
+- 🔗 AI Web Service Integration: Claude, Peplexity, Poe, and others
 - 💻 Local Model Support with Ollama, LM Studio
 
 2. **AI Assistants & Conversations**:
@@ -93,7 +103,7 @@ Cherry Studio is a desktop client that supports multiple LLM providers, availabl
 
 3. **Document & Data Processing**:
 
-- 📄 Supports Text, Images, Office, PDF, and more
+- 📄 Support for Text, Images, Office, PDF, and more
 - ☁️ WebDAV File Management and Backup
 - 📊 Mermaid Chart Visualization
 - 💻 Code Syntax Highlighting
@@ -110,7 +120,7 @@ Cherry Studio is a desktop client that supports multiple LLM providers, availabl
 5. **Enhanced User Experience**:
 
 - 🖥️ Cross-platform Support for Windows, Mac, and Linux
-- 📦 Ready to Use - No Environment Setup Required
+- 📦 Ready to Use, No Environment Setup Required
 - 🎨 Light/Dark Themes and Transparent Window
 - 📝 Complete Markdown Rendering
 - 🤲 Easy Content Sharing
@@ -121,11 +131,11 @@ We're actively working on the following features and improvements:
 
 1. 🎯 **Core Features**
 
-- Selection Assistant with smart content selection enhancement
-- Deep Research with advanced research capabilities
-- Memory System with global context awareness
-- Document Preprocessing with improved document handling
-- MCP Marketplace for Model Context Protocol ecosystem
+- Selection Assistant - Smart content selection enhancement
+- Deep Research - Advanced research capabilities
+- Memory System - Global context awareness
+- Document Preprocessing - Improved document handling
+- MCP Marketplace - Model Context Protocol ecosystem
 
 2. 🗂 **Knowledge Management**
 
@@ -141,7 +151,6 @@ We're actively working on the following features and improvements:
 - iOS App (Phase 1)
 - Multi-Window support
 - Window Pinning functionality
-- Intel AI PC (Core Ultra) Support
 
 4. 🔌 **Advanced Features**
 
@@ -175,7 +184,7 @@ We welcome contributions to Cherry Studio! Here are some ways you can contribute
 6. **Community Engagement**: Join discussions and help users.
 7. **Promote Usage**: Spread the word about Cherry Studio.
 
-Refer to the [Branching Strategy](docs/en/guides/branching-strategy.md) for contribution guidelines
+Refer to the [Branching Strategy](docs/branching-strategy-en.md) for contribution guidelines
 
 ## Getting Started
 
@@ -184,87 +193,15 @@ Refer to the [Branching Strategy](docs/en/guides/branching-strategy.md) for cont
 3. **Submit Changes**: Commit and push your changes.
 4. **Open a Pull Request**: Describe your changes and reasons.
 
-For more detailed guidelines, please refer to our [Contributing Guide](CONTRIBUTING.md).
+For more detailed guidelines, please refer to our [Contributing Guide](./CONTRIBUTING.md).
 
 Thank you for your support and contributions!
 
-# 🔧 Developer Co-creation Program
-
-We are launching the Cherry Studio Developer Co-creation Program to foster a healthy and positive-feedback loop within the open-source ecosystem. We believe that great software is built collaboratively, and every merged pull request breathes new life into the project.
-
-We sincerely invite you to join our ranks of contributors and shape the future of Cherry Studio with us.
-
-## Contributor Rewards Program
-
-To give back to our core contributors and create a virtuous cycle, we have established the following long-term incentive plan.
-
-**The inaugural tracking period for this program will be Q3 2025 (July, August, September). Rewards for this cycle will be distributed on October 1st.**
-
-Within any tracking period (e.g., July 1st to September 30th for the first cycle), any developer who contributes more than **30 meaningful commits** to any of Cherry Studio's open-source projects on GitHub will be eligible for the following benefits:
-
-- **Cursor Subscription Sponsorship**: Receive a **$70 USD** credit or reimbursement for your [Cursor](https://cursor.sh/) subscription, making AI your most efficient coding partner.
-- **Unlimited Model Access**: Get **unlimited** API calls for the **DeepSeek** and **Qwen** models.
-- **Cutting-Edge Tech Access**: Enjoy occasional perks, including API access to models like **Claude**, **Gemini**, and **OpenAI**, keeping you at the forefront of technology.
-
-## Growing Together & Future Plans
-
-A vibrant community is the driving force behind any sustainable open-source project. As Cherry Studio grows, so will our rewards program. We are committed to continuously aligning our benefits with the best-in-class tools and resources in the industry. This ensures our core contributors receive meaningful support, creating a positive cycle where developers, the community, and the project grow together.
-
-**Moving forward, the project will also embrace an increasingly open stance to give back to the entire open-source community.**
-
-## How to Get Started?
-
-We look forward to your first Pull Request!
-
-You can start by exploring our repositories, picking up a `good first issue`, or proposing your own enhancements. Every commit is a testament to the spirit of open source.
-
-Thank you for your interest and contributions.
-
-Let's build together.
-
-# 🏢 Enterprise Edition
-
-Building on the Community Edition, we are proud to introduce **Cherry Studio Enterprise Edition**—a privately-deployable AI productivity and management platform designed for modern teams and enterprises.
-
-The Enterprise Edition addresses core challenges in team collaboration by centralizing the management of AI resources, knowledge, and data. It empowers organizations to enhance efficiency, foster innovation, and ensure compliance, all while maintaining 100% control over their data in a secure environment.
-
-## Core Advantages
-
-- **Unified Model Management**: Centrally integrate and manage various cloud-based LLMs (e.g., OpenAI, Anthropic, Google Gemini) and locally deployed private models. Employees can use them out-of-the-box without individual configuration.
-- **Enterprise-Grade Knowledge Base**: Build, manage, and share team-wide knowledge bases. Ensures knowledge retention and consistency, enabling team members to interact with AI based on unified and accurate information.
-- **Fine-Grained Access Control**: Easily manage employee accounts and assign role-based permissions for different models, knowledge bases, and features through a unified admin backend.
-- **Fully Private Deployment**: Deploy the entire backend service on your on-premises servers or private cloud, ensuring your data remains 100% private and under your control to meet the strictest security and compliance standards.
-- **Reliable Backend Services**: Provides stable API services and enterprise-grade data backup and recovery mechanisms to ensure business continuity.
-
-## ✨ Online Demo
-
-**🔗 [Cherry Studio Enterprise](https://www.cherry-ai.com/enterprise)**
-
-## Version Comparison
-
-| Feature           | Community Edition                          | Enterprise Edition                                                                                                                      |
-| :---------------- | :----------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------- |
-| **Open Source**   | ✅ Yes                                      | ⭕️ Partially released to customers                                                                                                       |
-| **Cost**          | [AGPL-3.0 License](https://github.com/CherryHQ/cherry-studio?tab=AGPL-3.0-1-ov-file) | Buyout / Subscription Fee                                                                                                               |
-| **Admin Backend** | —                                          | ● Centralized **Model** Access<br>● **Employee** Management<br>● Shared **Knowledge Base**<br>● **Access** Control<br>● **Data** Backup |
-| **Server**        | —                                          | ✅ Dedicated Private Deployment                                                                                                          |
-
-## Get the Enterprise Edition
-
-We believe the Enterprise Edition will become your team's AI productivity engine. If you are interested in Cherry Studio Enterprise Edition and would like to learn more, request a quote, or schedule a demo, please feel free to contact us.
-
-- **For Business Inquiries & Purchasing**:
-  **📧 [bd@cherry-ai.com](mailto:bd@cherry-ai.com)**
-
 # 🔗 Related Projects
 
-- [new-api](https://github.com/QuantumNous/new-api): The next-generation LLM gateway and AI asset management system supports multiple languages.
+- [one-api](https://github.com/songquanpeng/one-api):LLM API management and distribution system, supporting mainstream models like OpenAI, Azure, and Anthropic. Features unified API interface, suitable for key management and secondary distribution.
 
-- [one-api](https://github.com/songquanpeng/one-api): LLM API management and distribution system supporting mainstream models like OpenAI, Azure, and Anthropic. Features a unified API interface, suitable for key management and secondary distribution.
-
-- [Poe](https://poe.com/): Poe gives you access to the best AI, all in one place. Explore GPT-5, Claude Opus 4.1, DeepSeek-R1, Veo 3, ElevenLabs, and millions of others.
-
-- [ublacklist](https://github.com/iorate/ublacklist): Blocks specific sites from appearing in Google search results
+- [ublacklist](https://github.com/iorate/ublacklist):Blocks specific sites from appearing in Google search results
 
 # 🚀 Contributors
 
@@ -273,53 +210,34 @@ We believe the Enterprise Edition will become your team's AI productivity engine
 </a>
 <br /><br />
 
-# 📊 GitHub Stats
-
-![Stats](https://repobeats.axiom.co/api/embed/a693f2e5f773eed620f70031e974552156c7f397.svg 'Repobeats analytics image')
-
 # ⭐️ Star History
 
-<a href="https://www.star-history.com/#CherryHQ/cherry-studio&Date">
- <picture>
-   <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=CherryHQ/cherry-studio&type=Date&theme=dark" />
-   <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=CherryHQ/cherry-studio&type=Date" />
-   <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=CherryHQ/cherry-studio&type=Date" />
- </picture>
-</a>
-
-# 📜 License
-
-The Cherry Studio Community Edition is governed by the standard GNU Affero General Public License v3.0 (AGPL-3.0), available at https://www.gnu.org/licenses/agpl-3.0.html.
-
-Use of the Cherry Studio Community Edition for commercial purposes is permitted, subject to full compliance with the terms and conditions of the AGPL-3.0 license.
-
-Should you require a commercial license that provides an exemption from the AGPL-3.0 requirements, please contact us at bd@cherry-ai.com.
+[![Star History Chart](https://api.star-history.com/svg?repos=CherryHQ/cherry-studio&type=Timeline)](https://star-history.com/#CherryHQ/cherry-studio&Timeline)
 
 <!-- Links & Images -->
-
-[deepwiki-shield]: https://img.shields.io/badge/Deepwiki-CherryHQ-0088CC?logo=data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNy45MyAzMiI+PHBhdGggZD0iTTE5LjMzIDE0LjEyYy42Ny0uMzkgMS41LS4zOSAyLjE4IDBsMS43NCAxYy4wNi4wMy4xMS4wNi4xOC4wN2guMDRjLjA2LjAzLjEyLjAzLjE4LjAzaC4wMmMuMDYgMCAuMTEgMCAuMTctLjAyaC4wM2MuMDYtLjAyLjEyLS4wNS4xNy0uMDhoLjAybDMuNDgtMi4wMWMuMjUtLjE0LjQtLjQxLjQtLjdWOC40YS44MS44MSAwIDAgMC0uNC0uN2wtMy40OC0yLjAxYS44My44MyAwIDAgMC0uODEgMEwxOS43NyA3LjdoLS4wMWwtLjE1LjEyLS4wMi4wMnMtLjA3LjA5LS4xLjE0VjhhLjQuNCAwIDAgMC0uMDguMTd2LjA0Yy0uMDMuMDYtLjAzLjEyLS4wMy4xOXYyLjAxYzAgLjc4LS40MSAxLjQ5LTEuMDkgMS44OC0uNjcuMzktMS41LjM5LTIuMTggMGwtMS43NC0xYS42LjYgMCAwIDAtLjIxLS4wOGMtLjA2LS4wMS0uMTItLjAyLS4xOC0uMDJoLS4wM2MtLjA2IDAtLjExLjAxLS4xNy4wMmgtLjAzYy0uMDYuMDItLjEyLjA0LS4xNy4wN2gtLjAybC0zLjQ3IDIuMDFjLS4yNS4xNC0uNC40MS0uNC43VjE4YzAgLjI5LjE1LjU1LjQuN2wzLjQ4IDIuMDFoLjAyYy4wNi4wNC4xMS4wNi4xNy4wOGguMDNjLjA1LjAyLjExLjAzLjE3LjAzaC4wMmMuMDYgMCAuMTIgMCAuMTgtLjAyaC4wNGMuMDYtLjAzLjEyLS4wNS4xOC0uMDhsMS43NC0xYy42Ny0uMzkgMS41LS4zOSAyLjE3IDBzMS4wOSAxLjExIDEuMDkgMS44OHYyLjAxYzAgLjA3IDAgLjEzLjAyLjE5di4wNGMuMDMuMDYuMDUuMTIuMDguMTd2LjAycy4wOC4wOS4xMi4xM2wuMDIuMDJzLjA5LjA4LjE1LjExYzAgMCAuMDEgMCAuMDEuMDFsMy40OCAyLjAxYy4yNS4xNC41Ni4xNC44MSAwbDMuNDgtMi4wMWMuMjUtLjE0LjQtLjQxLjQtLjd2LTQuMDFhLjgxLjgxIDAgMCAwLS40LS43bC0zLjQ4LTIuMDFoLS4wMmMtLjA1LS4wNC0uMTEtLjA2LS4xNy0uMDhoLS4wM2EuNS41IDAgMCAwLS4xNy0uMDNoLS4wM2MtLjA2IDAtLjEyIDAtLjE4LjAyLS4wNy4wMi0uMTUuMDUtLjIxLjA4bC0xLjc0IDFjLS42Ny4zOS0xLjUuMzktMi4xNyAwYTIuMTkgMi4xOSAwIDAgMS0xLjA5LTEuODhjMC0uNzguNDItMS40OSAxLjA5LTEuODhaIiBzdHlsZT0iZmlsbDojNWRiZjlkIi8+PHBhdGggZD0ibS40IDEzLjExIDMuNDcgMi4wMWMuMjUuMTQuNTYuMTQuOCAwbDMuNDctMi4wMWguMDFsLjE1LS4xMi4wMi0uMDJzLjA3LS4wOS4xLS4xNGwuMDItLjAyYy4wMy0uMDUuMDUtLjExLjA3LS4xN3YtLjA0Yy4wMy0uMDYuMDMtLjEyLjAzLS4xOVYxMC40YzAtLjc4LjQyLTEuNDkgMS4wOS0xLjg4czEuNS0uMzkgMi4xOCAwbDEuNzQgMWMuMDcuMDQuMTQuMDcuMjEuMDguMDYuMDEuMTIuMDIuMTguMDJoLjAzYy4wNiAwIC4xMS0uMDEuMTctLjAyaC4wM2MuMDYtLjAyLjEyLS4wNC4xNy0uMDdoLjAybDMuNDctMi4wMmMuMjUtLjE0LjQtLjQxLjQtLjd2LTRhLjgxLjgxIDAgMCAwLS40LS43bC0zLjQ2LTJhLjgzLjgzIDAgMCAwLS44MSAwbC0zLjQ4IDIuMDFoLS4wMWwtLjE1LjEyLS4wMi4wMi0uMS4xMy0uMDIuMDJjLS4wMy4wNS0uMDUuMTEtLjA3LjE3di4wNGMtLjAzLjA2LS4wMy4xMi0uMDMuMTl2Mi4wMWMwIC43OC0uNDIgMS40OS0xLjA5IDEuODhzLTEuNS4zOS0yLjE4IDBsLTEuNzQtMWEuNi42IDAgMCAwLS4yMS0uMDhjLS4wNi0uMDEtLjEyLS4wMi0uMTgtLjAyaC0uMDNjLS4wNiAwLS4xMS4wMS0uMTcuMDJoLS4wM2MtLjA2LjAyLS4xMi4wNS0uMTcuMDhoLS4wMkwuNCA3LjcxYy0uMjUuMTQtLjQuNDEtLjQuNjl2NC4wMWMwIC4yOS4xNS41Ni40LjciIHN0eWxlPSJmaWxsOiM0NDY4YzQiLz48cGF0aCBkPSJtMTcuODQgMjQuNDgtMy40OC0yLjAxaC0uMDJjLS4wNS0uMDQtLjExLS4wNi0uMTctLjA4aC0uMDNhLjUuNSAwIDAgMC0uMTctLjAzaC0uMDNjLS4wNiAwLS4xMiAwLS4xOC4wMmgtLjA0Yy0uMDYuMDMtLjEyLjA1LS4xOC4wOGwtMS43NCAxYy0uNjcuMzktMS41LjM5LTIuMTggMGEyLjE5IDIuMTkgMCAwIDEtMS4wOS0xLjg4di0yLjAxYzAtLjA2IDAtLjEzLS4wMi0uMTl2LS4wNGMtLjAzLS4wNi0uMDUtLjExLS4wOC0uMTdsLS4wMi0uMDJzLS4wNi0uMDktLjEtLjEzTDguMjkgMTlzLS4wOS0uMDgtLjE1LS4xMWgtLjAxbC0zLjQ3LTIuMDJhLjgzLjgzIDAgMCAwLS44MSAwTC4zNyAxOC44OGEuODcuODcgMCAwIDAtLjM3LjcxdjQuMDFjMCAuMjkuMTUuNTUuNC43bDMuNDcgMi4wMWguMDJjLjA1LjA0LjExLjA2LjE3LjA4aC4wM2MuMDUuMDIuMTEuMDMuMTYuMDNoLjAzYy4wNiAwIC4xMiAwIC4xOC0uMDJoLjA0Yy4wNi0uMDMuMTItLjA1LjE4LS4wOGwxLjc0LTFjLjY3LS4zOSAxLjUtLjM5IDIuMTcgMHMxLjA5IDEuMTEgMS4wOSAxLjg4djIuMDFjMCAuMDcgMCAuMTMuMDIuMTl2LjA0Yy4wMy4wNi4wNS4xMS4wOC4xN2wuMDIuMDJzLjA2LjA5LjEuMTRsLjAyLjAycy4wOS4wOC4xNS4xMWguMDFsMy40OCAyLjAyYy4yNS4xNC41Ni4xNC44MSAwbDMuNDgtMi4wMWMuMjUtLjE0LjQtLjQxLjQtLjdWMjUuMmEuODEuODEgMCAwIDAtLjQtLjdaIiBzdHlsZT0iZmlsbDojNDI5M2Q5Ii8+PC9zdmc+
+[deepwiki-shield]: https://img.shields.io/badge/Deepwiki-CherryHQ-0088CC?style=plastic
 [deepwiki-link]: https://deepwiki.com/CherryHQ/cherry-studio
-[twitter-shield]: https://img.shields.io/badge/Twitter-CherryStudioApp-0088CC?logo=x
+[twitter-shield]: https://img.shields.io/badge/Twitter-CherryStudioApp-0088CC?style=plastic&logo=x
 [twitter-link]: https://twitter.com/CherryStudioHQ
-[discord-shield]: https://img.shields.io/badge/Discord-@CherryStudio-0088CC?logo=discord
+[discord-shield]: https://img.shields.io/badge/Discord-@CherryStudio-0088CC?style=plastic&logo=discord
 [discord-link]: https://discord.gg/wez8HtpxqQ
-[telegram-shield]: https://img.shields.io/badge/Telegram-@CherryStudioAI-0088CC?logo=telegram
+[telegram-shield]: https://img.shields.io/badge/Telegram-@CherryStudioAI-0088CC?style=plastic&logo=telegram
 [telegram-link]: https://t.me/CherryStudioAI
 
 <!-- Links & Images -->
-
-[github-release-shield]: https://img.shields.io/github/v/release/CherryHQ/cherry-studio?logo=github
+[github-stars-shield]: https://img.shields.io/github/stars/CherryHQ/cherry-studio?style=social
+[github-stars-link]: https://github.com/CherryHQ/cherry-studio/stargazers
+[github-forks-shield]: https://img.shields.io/github/forks/CherryHQ/cherry-studio?style=social
+[github-forks-link]: https://github.com/CherryHQ/cherry-studio/network
+[github-release-shield]: https://img.shields.io/github/v/release/CherryHQ/cherry-studio
 [github-release-link]: https://github.com/CherryHQ/cherry-studio/releases
-[github-nightly-shield]: https://img.shields.io/github/actions/workflow/status/CherryHQ/cherry-studio/nightly-build.yml?label=nightly%20build&logo=github
-[github-nightly-link]: https://github.com/CherryHQ/cherry-studio/actions/workflows/nightly-build.yml
-[github-contributors-shield]: https://img.shields.io/github/contributors/CherryHQ/cherry-studio?logo=github
+[github-contributors-shield]: https://img.shields.io/github/contributors/CherryHQ/cherry-studio
 [github-contributors-link]: https://github.com/CherryHQ/cherry-studio/graphs/contributors
 
 <!-- Links & Images -->
-
-[license-shield]: https://img.shields.io/badge/License-AGPLv3-important.svg?logo=gnu
+[license-shield]: https://img.shields.io/badge/License-AGPLv3-important.svg?style=plastic&logo=gnu
 [license-link]: https://www.gnu.org/licenses/agpl-3.0
-[commercial-shield]: https://img.shields.io/badge/License-Contact-white.svg?logoColor=white&logo=telegram&color=blue
+[commercial-shield]: https://img.shields.io/badge/License-Contact-white.svg?style=plastic&logoColor=white&logo=telegram&color=blue
 [commercial-link]: mailto:license@cherry-ai.com?subject=Commercial%20License%20Inquiry
-[sponsor-shield]: https://img.shields.io/badge/Sponsor-FF6699.svg?logo=githubsponsors&logoColor=white
+[sponsor-shield]: https://img.shields.io/badge/Sponsor-FF6699.svg?style=plastic&logo=githubsponsors&logoColor=white
 [sponsor-link]: https://github.com/CherryHQ/cherry-studio/blob/main/docs/sponsor.md

SECURITY.md

@@ -1,64 +0,0 @@
-# Security Policy
-
-## 📢 Reporting a Vulnerability
-
-At Cherry Studio, we take security seriously and appreciate your efforts to responsibly disclose vulnerabilities. If you discover a security issue, please report it as soon as possible.
-
-**Please do not create public issues for security-related reports.**
-
-- To report a security issue, please use the GitHub Security Advisories tab to "[Open a draft security advisory](https://github.com/CherryHQ/cherry-studio/security/advisories/new)".
-- Include a detailed description of the issue, steps to reproduce, potential impact, and any possible mitigations.
-- If applicable, please also attach proof-of-concept code or screenshots.
-
-We will acknowledge your report within **72 hours** and provide a status update as we investigate.
-
----
-
-## 🔒 Supported Versions
-
-We aim to support the latest released version and one previous minor release.
-
-| Version         | Supported        |
-| --------------- | ---------------- |
-| Latest (`main`) | ✅ Supported     |
-| Previous minor  | ✅ Supported     |
-| Older versions  | ❌ Not supported |
-
-If you are using an unsupported version, we strongly recommend updating to the latest release to receive security fixes.
-
----
-
-## 💡 Security Measures
-
-Cherry Studio integrates several security best practices, including:
-
-- Strict dependency updates and regular vulnerability scanning.
-- TypeScript strict mode and linting to reduce potential injection or runtime issues.
-- Enforced code formatting and pre-commit hooks.
-- Internal security reviews before releases.
-- Dedicated MCP (Model Context Protocol) safeguards for model interactions and data privacy.
-
----
-
-## 🛡️ Disclosure Policy
-
-- We follow a **coordinated disclosure** approach.
-- We will not publicly disclose vulnerabilities until a fix has been developed and released.
-- Credit will be given to researchers who responsibly disclose vulnerabilities, if requested.
-
----
-
-## 🤝 Acknowledgements
-
-We greatly appreciate contributions from the security community and strive to recognize all researchers who help keep Cherry Studio safe.
-
----
-
-## 🌟 Questions?
-
-For any security-related questions not involving vulnerabilities, please reach out to:  
-**security@cherry-ai.com**
-
----
-
-Thank you for helping keep Cherry Studio and its users secure!

app-upgrade-config.json

@@ -1,49 +0,0 @@
-{
-  "lastUpdated": "2025-11-10T08:14:28Z",
-  "versions": {
-    "1.6.7": {
-      "metadata": {
-        "segmentId": "legacy-v1",
-        "segmentType": "legacy"
-      },
-      "minCompatibleVersion": "1.0.0",
-      "description": "Last stable v1.7.x release - required intermediate version for users below v1.7",
-      "channels": {
-        "latest": {
-          "version": "1.6.7",
-          "feedUrls": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.6.7",
-            "gitcode": "https://releases.cherry-ai.com"
-          }
-        },
-        "rc": {
-          "version": "1.6.0-rc.5",
-          "feedUrls": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.6.0-rc.5",
-            "gitcode": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.6.0-rc.5"
-          }
-        },
-        "beta": {
-          "version": "1.7.0-beta.3",
-          "feedUrls": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.7.0-beta.3",
-            "gitcode": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.7.0-beta.3"
-          }
-        }
-      }
-    },
-    "2.0.0": {
-      "metadata": {
-        "segmentId": "gateway-v2",
-        "segmentType": "breaking"
-      },
-      "minCompatibleVersion": "1.7.0",
-      "description": "Major release v2.0 - required intermediate version for v2.x upgrades",
-      "channels": {
-        "latest": null,
-        "rc": null,
-        "beta": null
-      }
-    }
-  }
-}

biome.jsonc

@@ -1,101 +0,0 @@
-{
-  "$schema": "https://biomejs.dev/schemas/2.2.4/schema.json",
-  "assist": {
-    // to sort json
-    "actions": {
-      "source": {
-        "organizeImports": "on",
-        "useSortedKeys": {
-          "level": "on",
-          "options": {
-            "sortOrder": "lexicographic"
-          }
-        }
-      }
-    },
-    "enabled": true,
-    "includes": ["**/*.json", "!*.json", "!**/package.json", "!coverage/**"]
-  },
-  "css": {
-    "formatter": {
-      "quoteStyle": "single"
-    }
-  },
-  "files": {
-    "ignoreUnknown": false,
-    "includes": ["**", "!**/.claude/**", "!**/.vscode/**"],
-    "maxSize": 2097152
-  },
-  "formatter": {
-    "attributePosition": "auto",
-    "bracketSameLine": false,
-    "bracketSpacing": true,
-    "enabled": true,
-    "expand": "auto",
-    "formatWithErrors": true,
-    "includes": [
-      "**",
-      "!out/**",
-      "!**/dist/**",
-      "!build/**",
-      "!.yarn/**",
-      "!.github/**",
-      "!.husky/**",
-      "!.vscode/**",
-      "!*.yaml",
-      "!*.yml",
-      "!*.mjs",
-      "!*.cjs",
-      "!*.md",
-      "!*.json",
-      "!src/main/integration/**",
-      "!**/tailwind.css",
-      "!**/package.json"
-    ],
-    "indentStyle": "space",
-    "indentWidth": 2,
-    "lineEnding": "lf",
-    "lineWidth": 120,
-    "useEditorconfig": true
-  },
-  "html": { "formatter": { "selfCloseVoidElements": "always" } },
-  "javascript": {
-    "formatter": {
-      "arrowParentheses": "always",
-      "attributePosition": "auto",
-      // To minimize changes in this PR as much as possible, it's set to true. However, setting it to false would make it more convenient to add attributes at the end.
-      "bracketSameLine": true,
-      "bracketSpacing": true,
-      "jsxQuoteStyle": "double",
-      "quoteProperties": "asNeeded",
-      "quoteStyle": "single",
-      "semicolons": "asNeeded",
-      "trailingCommas": "none"
-    }
-  },
-  "json": {
-    "parser": {
-      "allowComments": true
-    }
-  },
-  "linter": {
-    "enabled": true,
-    "includes": ["!**/tailwind.css", "src/renderer/**/*.{tsx,ts}"],
-    // only enable sorted tailwind css rule. used as formatter instead of linter
-    "rules": {
-      "nursery": {
-        // to sort tailwind css classes
-        "useSortedClasses": {
-          "fix": "safe",
-          "level": "warn",
-          "options": {
-            "functions": ["cn"]
-          }
-        }
-      },
-      "recommended": false,
-      "suspicious": "off"
-    }
-  },
-  "vcs": { "clientKind": "git", "enabled": false, "useIgnoreFile": false }
-}

build/entitlements.mac.plist

@@ -8,7 +8,5 @@
     <true/>
     <key>com.apple.security.cs.allow-dyld-environment-variables</key>
     <true/>
-    <key>com.apple.security.cs.disable-library-validation</key>
-    <true/>
   </dict>
 </plist>

build/nsis-installer.nsh

@@ -8,93 +8,16 @@
 ; https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist
 
 !include LogicLib.nsh
-!include x64.nsh
 
 ; https://github.com/electron-userland/electron-builder/issues/1122
 !ifndef BUILD_UNINSTALLER
   Function checkVCRedist
     ReadRegDWORD $0 HKLM "SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\x64" "Installed"
   FunctionEnd
-
-  Function checkArchitectureCompatibility
-    ; Initialize variables
-    StrCpy $0 "0"  ; Default to incompatible
-    StrCpy $1 ""   ; System architecture
-    StrCpy $3 ""   ; App architecture
-
-    ; Check system architecture using built-in NSIS functions
-    ${If} ${RunningX64}
-      ; Check if it's ARM64 by looking at processor architecture
-      ReadEnvStr $2 "PROCESSOR_ARCHITECTURE"
-      ReadEnvStr $4 "PROCESSOR_ARCHITEW6432"
-
-      ${If} $2 == "ARM64"
-      ${OrIf} $4 == "ARM64"
-        StrCpy $1 "arm64"
-      ${Else}
-        StrCpy $1 "x64"
-      ${EndIf}
-    ${Else}
-      StrCpy $1 "x86"
-    ${EndIf}
-
-    ; Determine app architecture based on build variables
-    !ifdef APP_ARM64_NAME
-      !ifndef APP_64_NAME
-        StrCpy $3 "arm64"  ; App is ARM64 only
-      !endif
-    !endif
-    !ifdef APP_64_NAME
-      !ifndef APP_ARM64_NAME
-        StrCpy $3 "x64"    ; App is x64 only
-      !endif
-    !endif
-    !ifdef APP_64_NAME
-      !ifdef APP_ARM64_NAME
-        StrCpy $3 "universal"  ; Both architectures available
-      !endif
-    !endif
-
-    ; If no architecture variables are defined, assume x64
-    ${If} $3 == ""
-      StrCpy $3 "x64"
-    ${EndIf}
-
-    ; Compare system and app architectures
-    ${If} $3 == "universal"
-      ; Universal build, compatible with all architectures
-      StrCpy $0 "1"
-    ${ElseIf} $1 == $3
-      ; Architectures match
-      StrCpy $0 "1"
-    ${Else}
-      ; Architectures don't match
-      StrCpy $0 "0"
-    ${EndIf}
-  FunctionEnd
 !endif
 
 !macro customInit
   Push $0
-  Push $1
-  Push $2
-  Push $3
-  Push $4
-
-  ; Check architecture compatibility first
-  Call checkArchitectureCompatibility
-  ${If} $0 != "1"
-    MessageBox MB_ICONEXCLAMATION "\
-      Architecture Mismatch$\r$\n$\r$\n\
-      This installer is not compatible with your system architecture.$\r$\n\
-      Your system: $1$\r$\n\
-      App architecture: $3$\r$\n$\r$\n\
-      Please download the correct version from:$\r$\n\
-      https://www.cherry-ai.com/"
-    ExecShell "open" "https://www.cherry-ai.com/"
-    Abort
-  ${EndIf}
-
   Call checkVCRedist
   ${If} $0 != "1"
     MessageBox MB_YESNO "\
@@ -120,9 +43,5 @@
       Abort
   ${EndIf}
   ContinueInstall:
-    Pop $4
-    Pop $3
-    Pop $2
-    Pop $1
     Pop $0
-!macroend
+!macroend

config/app-upgrade-segments.json

@@ -1,81 +0,0 @@
-{
-  "segments": [
-    {
-      "id": "legacy-v1",
-      "type": "legacy",
-      "match": {
-        "range": ">=1.0.0 <2.0.0"
-      },
-      "minCompatibleVersion": "1.0.0",
-      "description": "Last stable v1.7.x release - required intermediate version for users below v1.7",
-      "channelTemplates": {
-        "latest": {
-          "feedTemplates": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/{{tag}}",
-            "gitcode": "https://releases.cherry-ai.com"
-          }
-        },
-        "rc": {
-          "feedTemplates": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/{{tag}}",
-            "gitcode": "https://github.com/CherryHQ/cherry-studio/releases/download/{{tag}}"
-          }
-        },
-        "beta": {
-          "feedTemplates": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/{{tag}}",
-            "gitcode": "https://github.com/CherryHQ/cherry-studio/releases/download/{{tag}}"
-          }
-        }
-      }
-    },
-    {
-      "id": "gateway-v2",
-      "type": "breaking",
-      "match": {
-        "exact": ["2.0.0"]
-      },
-      "lockedVersion": "2.0.0",
-      "minCompatibleVersion": "1.7.0",
-      "description": "Major release v2.0 - required intermediate version for v2.x upgrades",
-      "channelTemplates": {
-        "latest": {
-          "feedTemplates": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/{{tag}}",
-            "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/download/{{tag}}"
-          }
-        }
-      }
-    },
-    {
-      "id": "current-v2",
-      "type": "latest",
-      "match": {
-        "range": ">=2.0.0 <3.0.0",
-        "excludeExact": ["2.0.0"]
-      },
-      "minCompatibleVersion": "2.0.0",
-      "description": "Current latest v2.x release",
-      "channelTemplates": {
-        "latest": {
-          "feedTemplates": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/{{tag}}",
-            "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/download/{{tag}}"
-          }
-        },
-        "rc": {
-          "feedTemplates": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/{{tag}}",
-            "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/download/{{tag}}"
-          }
-        },
-        "beta": {
-          "feedTemplates": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/{{tag}}",
-            "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/download/{{tag}}"
-          }
-        }
-      }
-    }
-  ]
-}

docs/CONTRIBUTING.zh.md

@@ -1,6 +1,6 @@
 # Cherry Studio 贡献者指南
 
-[**English**](../../../CONTRIBUTING.md) | **中文**
+[**English**](../CONTRIBUTING.md) | [**中文**](./CONTRIBUTING.zh.md)
 
 欢迎来到 Cherry Studio 的贡献者社区！我们致力于将 Cherry Studio 打造成一个长期提供价值的项目，并希望邀请更多的开发者加入我们的行列。无论您是经验丰富的开发者还是刚刚起步的初学者，您的贡献都将帮助我们更好地服务用户，提升软件质量。
 
@@ -24,7 +24,7 @@
 
 ## 开始之前
 
-请确保阅读了[行为准则](../../../CODE_OF_CONDUCT.md)和[LICENSE](../../../LICENSE)。
+请确保阅读了[行为准则](CODE_OF_CONDUCT.md)和[LICENSE](LICENSE)。
 
 ## 开始贡献
 
@@ -32,7 +32,7 @@
 
 ### 测试
 
-未经测试的功能等同于不存在。为确保代码真正有效，应通过单元测试和功能测试覆盖相关流程。因此，在考虑贡献时，也请考虑可测试性。所有测试均可本地运行，无需依赖 CI。请参阅[开发者指南](./development.md#test)中的"Test"部分。
+未经测试的功能等同于不存在。为确保代码真正有效，应通过单元测试和功能测试覆盖相关流程。因此，在考虑贡献时，也请考虑可测试性。所有测试均可本地运行，无需依赖 CI。请参阅[开发者指南](docs/dev.md#test)中的“Test”部分。
 
 ### 拉取请求的自动化测试
 
@@ -60,37 +60,12 @@ git commit --signoff -m "Your commit message"
 
 ### 获取代码审查/合并
 
-维护者在此帮助您在合理时间内实现您的用例。他们会尽力在合理时间内审查您的代码并提供建设性反馈。但如果您在审查过程中受阻，或认为您的 Pull Request 未得到应有的关注，请通过 Issue 中的评论或者[社群](../README.md#-community)联系我们
-
-### 参与测试计划
-
-测试计划旨在为用户提供更稳定的应用体验和更快的迭代速度，详细情况请参阅[测试计划](./test-plan.md)。
+维护者在此帮助您在合理时间内实现您的用例。他们会尽力在合理时间内审查您的代码并提供建设性反馈。但如果您在审查过程中受阻，或认为您的 Pull Request 未得到应有的关注，请通过 Issue 中的评论或者[社群](README.md#-community)联系我们
 
 ### 其他建议
 
 - **联系开发者**：在提交 PR 之前，您可以先和开发者进行联系，共同探讨或者获取帮助。
-
-## 重要贡献指南与关注点
-
-在提交 Pull Request 之前，请务必阅读以下关键信息：
-
-### 🚫 暂时限制涉及数据更改的功能性 PR
-
-**目前，我们不接受涉及 Redux 数据模型或 IndexedDB schema 变更的功能性 Pull Request。**
-
-我们的核心团队目前正专注于涉及这些数据结构的关键架构更新和基础工作。为确保在此期间的稳定性与专注，此类贡献将暂时由内部进行管理。
-
-*   **需要更改 Redux 状态结构或 IndexedDB schema 的 PR 将会被关闭。**
-*   **此限制是临时性的，并将在 `v2.0.0` 版本发布后解除。** 您可以通过 Issue [#10162](https://github.com/CherryHQ/cherry-studio/pull/10162) 跟踪 `v2.0.0` 的进展及相关讨论。
-
-我们非常鼓励以下类型的贡献：
-*   错误修复 🐞
-*   性能改进 🚀
-*   文档更新 📚
-*   不改变 Redux 数据模型或 IndexedDB schema 的功能（例如，UI 增强、新组件、小型重构）。✨
-
-感谢您在此重要开发阶段的理解与持续支持。谢谢！
-
+- **成为核心开发者**：如果您能够稳定为项目贡献，恭喜您可以成为项目核心开发者，获取到项目成员身份。请查看我们的[成员指南](https://github.com/CherryHQ/community/blob/main/membership.md)
 
 ## 联系我们
 

docs/README.ja.md

@@ -0,0 +1,215 @@
+<h1 align="center">
+  <a href="https://github.com/CherryHQ/cherry-studio/releases">
+    <img src="https://github.com/CherryHQ/cherry-studio/blob/main/build/icon.png?raw=true" width="150" height="150" alt="banner" /><br>
+  </a>
+</h1>
+<p align="center">
+  <a href="https://github.com/CherryHQ/cherry-studio">English</a> | <a href="./README.zh.md">中文</a> | 日本語 | <a href="https://cherry-ai.com">公式サイト</a> | <a href="https://docs.cherry-ai.com/cherry-studio-wen-dang/ja">ドキュメント</a> | <a href="./dev.md">開発</a> | <a href="https://github.com/CherryHQ/cherry-studio/issues">フィードバック</a><br>
+</p>
+
+<!-- バッジコレクション -->
+
+<div align="center">
+
+[![][deepwiki-shield]][deepwiki-link]
+[![][twitter-shield]][twitter-link]
+[![][discord-shield]][discord-link]
+[![][telegram-shield]][telegram-link]
+
+</div>
+
+<!-- プロジェクト統計 -->
+
+<div align="center">
+
+[![][github-stars-shield]][github-stars-link]
+[![][github-forks-shield]][github-forks-link]
+[![][github-release-shield]][github-release-link]
+[![][github-contributors-shield]][github-contributors-link]
+
+</div>
+
+<div align="center">
+
+[![][license-shield]][license-link]
+[![][commercial-shield]][commercial-link]
+[![][sponsor-shield]][sponsor-link]
+
+</div>
+
+<div align="center">
+ <a href="https://hellogithub.com/repository/1605492e1e2a4df3be07abfa4578dd37" target="_blank"><img src="https://api.hellogithub.com/v1/widgets/recommend.svg?rid=1605492e1e2a4df3be07abfa4578dd37" alt="Featured｜HelloGitHub" style="width: 200px; height: 43px;" width="200" height="43" /></a>
+ <a href="https://trendshift.io/repositories/11772" target="_blank"><img src="https://trendshift.io/api/badge/repositories/11772" alt="kangfenmao%2Fcherry-studio | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
+ <a href="https://www.producthunt.com/posts/cherry-studio?embed=true&utm_source=badge-featured&utm_medium=badge&utm_souce=badge-cherry&#0045;studio" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=496640&theme=light" alt="Cherry&#0032;Studio - AI&#0032;Chatbots&#0044;&#0032;AI&#0032;Desktop&#0032;Client | Product Hunt" style="width: 200px; height: 43px;" width="200" height="43" /></a>
+</div>
+
+# 🍒 Cherry Studio
+
+Cherry Studio は、複数の LLM プロバイダーをサポートするデスクトップクライアントで、Windows、Mac、Linux で利用可能です。
+
+👏 [Telegram](https://t.me/CherryStudioAI)｜[Discord](https://discord.gg/wez8HtpxqQ) | [QQグループ(575014769)](https://qm.qq.com/q/lo0D4qVZKi)
+
+❤️ Cherry Studio をお気に入りにしましたか？小さな星をつけてください 🌟 または [スポンサー](sponsor.md) をして開発をサポートしてください！
+
+# 🌠 スクリーンショット
+
+![](https://github.com/user-attachments/assets/36dddb2c-e0fb-4a5f-9411-91447bab6e18)
+
+![](https://github.com/user-attachments/assets/f549e8a0-2385-40b4-b52b-2039e39f2930)
+
+![](https://github.com/user-attachments/assets/58e0237c-4d36-40de-b428-53051d982026)
+
+# 🌟 主な機能
+
+1. **多様な LLM サービス対応**：
+
+- ☁️ 主要な LLM クラウドサービス対応：OpenAI、Gemini、Anthropic など
+- 🔗 AI Web サービス統合：Claude、Peplexity、Poe など
+- 💻 Ollama、LM Studio によるローカルモデル実行対応
+
+2. **AI アシスタントと対話**：
+
+- 📚 300+ の事前設定済み AI アシスタント
+- 🤖 カスタム AI アシスタントの作成
+- 💬 複数モデルでの同時対話機能
+
+3. **文書とデータ処理**：
+
+- 📄 テキスト、画像、Office、PDF など多様な形式対応
+- ☁️ WebDAV によるファイル管理とバックアップ
+- 📊 Mermaid による図表作成
+- 💻 コードハイライト機能
+
+4. **実用的なツール統合**：
+
+- 🔍 グローバル検索機能
+- 📝 トピック管理システム
+- 🔤 AI による翻訳機能
+- 🎯 ドラッグ＆ドロップによる整理
+- 🔌 ミニプログラム対応
+- ⚙️ MCP（モデルコンテキストプロトコル）サービス
+
+5. **優れたユーザー体験**：
+
+- 🖥️ Windows、Mac、Linux のクロスプラットフォーム対応
+- 📦 環境構築不要ですぐに使用可能
+- 🎨 ライト/ダークテーマと透明ウィンドウ対応
+- 📝 完全な Markdown レンダリング
+- 🤲 簡単な共有機能
+
+# 📝 開発計画
+
+以下の機能と改善に積極的に取り組んでいます：
+
+1. 🎯 **コア機能**
+
+- 選択アシスタント - スマートな内容選択の強化
+- ディープリサーチ - 高度な研究能力
+- メモリーシステム - グローバルコンテキスト認識
+- ドキュメント前処理 - 文書処理の改善
+- MCP マーケットプレイス - モデルコンテキストプロトコルエコシステム
+
+2. 🗂 **ナレッジ管理**
+
+- ノートとコレクション
+- ダイナミックキャンバス可視化
+- OCR 機能
+- TTS（テキスト読み上げ）サポート
+
+3. 📱 **プラットフォーム対応**
+
+- HarmonyOS エディション
+- Android アプリ（フェーズ1）
+- iOS アプリ（フェーズ1）
+- マルチウィンドウ対応
+- ウィンドウピン留め機能
+
+4. 🔌 **高度な機能**
+
+- プラグインシステム
+- ASR（音声認識）
+- アシスタントとトピックの対話機能リファクタリング
+
+[プロジェクトボード](https://github.com/orgs/CherryHQ/projects/7)で進捗を確認し、貢献することができます。
+
+開発計画に影響を与えたいですか？[GitHub ディスカッション](https://github.com/CherryHQ/cherry-studio/discussions)に参加して、アイデアやフィードバックを共有してください！
+
+# 🌈 テーマ
+
+- テーマギャラリー：https://cherrycss.com
+- Aero テーマ：https://github.com/hakadao/CherryStudio-Aero
+- PaperMaterial テーマ：https://github.com/rainoffallingstar/CherryStudio-PaperMaterial
+- Claude テーマ：https://github.com/bjl101501/CherryStudio-Claudestyle-dynamic
+- メープルネオンテーマ：https://github.com/BoningtonChen/CherryStudio_themes
+
+より多くのテーマの PR を歓迎します
+
+# 🤝 貢献
+
+Cherry Studio への貢献を歓迎します！以下の方法で貢献できます：
+
+1. **コードの貢献**：新機能を開発するか、既存のコードを最適化します
+2. **バグの修正**：見つけたバグを修正します
+3. **問題の管理**：GitHub の問題を管理するのを手伝います
+4. **製品デザイン**：デザインの議論に参加します
+5. **ドキュメントの作成**：ユーザーマニュアルやガイドを改善します
+6. **コミュニティの参加**：ディスカッションに参加し、ユーザーを支援します
+7. **使用の促進**：Cherry Studio を広めます
+
+[ブランチ戦略](branching-strategy-en.md)を参照して貢献ガイドラインを確認してください
+
+## 始め方
+
+1. **リポジトリをフォーク**：フォークしてローカルマシンにクローンします
+2. **ブランチを作成**：変更のためのブランチを作成します
+3. **変更を提出**：変更をコミットしてプッシュします
+4. **プルリクエストを開く**：変更内容と理由を説明します
+
+詳細なガイドラインについては、[貢献ガイド](../CONTRIBUTING.md)をご覧ください。
+
+ご支援と貢献に感謝します！
+
+# 🔗 関連プロジェクト
+
+- [one-api](https://github.com/songquanpeng/one-api)：LLM API の管理・配信システム。OpenAI、Azure、Anthropic などの主要モデルに対応し、統一 API インターフェースを提供。API キー管理と再配布に利用可能。
+
+- [ublacklist](https://github.com/iorate/ublacklist)：Google 検索結果から特定のサイトを非表示にします
+
+# 🚀 コントリビューター
+
+<a href="https://github.com/CherryHQ/cherry-studio/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=CherryHQ/cherry-studio" />
+</a>
+<br /><br />
+
+# ⭐️ スター履歴
+
+[![Star History Chart](https://api.star-history.com/svg?repos=CherryHQ/cherry-studio&type=Timeline)](https://star-history.com/#CherryHQ/cherry-studio&Timeline)
+
+<!-- リンクと画像 -->
+[deepwiki-shield]: https://img.shields.io/badge/Deepwiki-CherryHQ-0088CC?style=plastic
+[deepwiki-link]: https://deepwiki.com/CherryHQ/cherry-studio
+[twitter-shield]: https://img.shields.io/badge/Twitter-CherryStudioApp-0088CC?style=plastic&logo=x
+[twitter-link]: https://twitter.com/CherryStudioHQ
+[discord-shield]: https://img.shields.io/badge/Discord-@CherryStudio-0088CC?style=plastic&logo=discord
+[discord-link]: https://discord.gg/wez8HtpxqQ
+[telegram-shield]: https://img.shields.io/badge/Telegram-@CherryStudioAI-0088CC?style=plastic&logo=telegram
+[telegram-link]: https://t.me/CherryStudioAI
+
+<!-- プロジェクト統計 -->
+[github-stars-shield]: https://img.shields.io/github/stars/CherryHQ/cherry-studio?style=social
+[github-stars-link]: https://github.com/CherryHQ/cherry-studio/stargazers
+[github-forks-shield]: https://img.shields.io/github/forks/CherryHQ/cherry-studio?style=social
+[github-forks-link]: https://github.com/CherryHQ/cherry-studio/network
+[github-release-shield]: https://img.shields.io/github/v/release/CherryHQ/cherry-studio
+[github-release-link]: https://github.com/CherryHQ/cherry-studio/releases
+[github-contributors-shield]: https://img.shields.io/github/contributors/CherryHQ/cherry-studio
+[github-contributors-link]: https://github.com/CherryHQ/cherry-studio/graphs/contributors
+
+<!-- ライセンスとスポンサー -->
+[license-shield]: https://img.shields.io/badge/License-AGPLv3-important.svg?style=plastic&logo=gnu
+[license-link]: https://www.gnu.org/licenses/agpl-3.0
+[commercial-shield]: https://img.shields.io/badge/商用ライセンス-お問い合わせ-white.svg?style=plastic&logoColor=white&logo=telegram&color=blue
+[commercial-link]: mailto:license@cherry-ai.com?subject=商業ライセンスについて
+[sponsor-shield]: https://img.shields.io/badge/スポンサー-FF6699.svg?style=plastic&logo=githubsponsors&logoColor=white
+[sponsor-link]: https://github.com/CherryHQ/cherry-studio/blob/main/docs/sponsor.md

docs/README.md

@@ -1,81 +0,0 @@
-# Cherry Studio Documentation / 文档
-
-This directory contains the project documentation in multiple languages.
-
-本目录包含多语言项目文档。
-
----
-
-## Languages / 语言
-
-- **[中文文档](./zh/README.md)** - Chinese Documentation
-- **English Documentation** - See sections below
-
----
-
-## English Documentation
-
-### Guides
-
-| Document | Description |
-|----------|-------------|
-| [Development Setup](./en/guides/development.md) | Development environment setup |
-| [Branching Strategy](./en/guides/branching-strategy.md) | Git branching workflow |
-| [i18n Guide](./en/guides/i18n.md) | Internationalization guide |
-| [Logging Guide](./en/guides/logging.md) | How to use the logger service |
-| [Test Plan](./en/guides/test-plan.md) | Test plan and release channels |
-
-### References
-
-| Document | Description |
-|----------|-------------|
-| [App Upgrade Config](./en/references/app-upgrade.md) | Application upgrade configuration |
-| [CodeBlockView Component](./en/references/components/code-block-view.md) | Code block view component |
-| [Image Preview Components](./en/references/components/image-preview.md) | Image preview components |
-
----
-
-## 中文文档
-
-### 指南 (Guides)
-
-| 文档 | 说明 |
-|------|------|
-| [开发环境设置](./zh/guides/development.md) | 开发环境配置 |
-| [贡献指南](./zh/guides/contributing.md) | 如何贡献代码 |
-| [分支策略](./zh/guides/branching-strategy.md) | Git 分支工作流 |
-| [测试计划](./zh/guides/test-plan.md) | 测试计划和发布通道 |
-| [国际化指南](./zh/guides/i18n.md) | 国际化开发指南 |
-| [日志使用指南](./zh/guides/logging.md) | 如何使用日志服务 |
-| [中间件开发](./zh/guides/middleware.md) | 如何编写中间件 |
-| [记忆功能](./zh/guides/memory.md) | 记忆功能使用指南 |
-| [赞助信息](./zh/guides/sponsor.md) | 赞助相关信息 |
-
-### 参考 (References)
-
-| 文档 | 说明 |
-|------|------|
-| [消息系统](./zh/references/message-system.md) | 消息系统架构和 API |
-| [数据库结构](./zh/references/database.md) | 数据库表结构 |
-| [服务](./zh/references/services.md) | 服务层文档 (KnowledgeService) |
-| [代码执行](./zh/references/code-execution.md) | 代码执行功能 |
-| [应用升级配置](./zh/references/app-upgrade.md) | 应用升级配置 |
-| [CodeBlockView 组件](./zh/references/components/code-block-view.md) | 代码块视图组件 |
-| [图像预览组件](./zh/references/components/image-preview.md) | 图像预览组件 |
-
----
-
-## Missing Translations / 缺少翻译
-
-The following documents are only available in Chinese and need English translations:
-
-以下文档仅有中文版本，需要英文翻译：
-
-- `guides/contributing.md`
-- `guides/memory.md`
-- `guides/middleware.md`
-- `guides/sponsor.md`
-- `references/message-system.md`
-- `references/database.md`
-- `references/services.md`
-- `references/code-execution.md`

docs/README.zh.md

@@ -0,0 +1,227 @@
+<h1 align="center">
+  <a href="https://github.com/CherryHQ/cherry-studio/releases">
+    <img src="https://github.com/CherryHQ/cherry-studio/blob/main/build/icon.png?raw=true" width="150" height="150" alt="banner" /><br>
+  </a>
+</h1>
+<p align="center">
+  <a href="https://github.com/CherryHQ/cherry-studio">English</a> | 中文 | <a href="./README.ja.md">日本語</a> | <a href="https://cherry-ai.com">官方网站</a> | <a href="https://docs.cherry-ai.com/cherry-studio-wen-dang/zh-cn">文档</a> | <a href="./dev.md">开发</a> | <a href="https://github.com/CherryHQ/cherry-studio/issues">反馈</a><br>
+</p>
+
+<!-- 题头徽章组合 -->
+
+<div align="center">
+
+[![][deepwiki-shield]][deepwiki-link]
+[![][twitter-shield]][twitter-link]
+[![][discord-shield]][discord-link]
+[![][telegram-shield]][telegram-link]
+
+</div>
+
+<!-- 项目统计徽章 -->
+
+<div align="center">
+
+[![][github-stars-shield]][github-stars-link]
+[![][github-forks-shield]][github-forks-link]
+[![][github-release-shield]][github-release-link]
+[![][github-contributors-shield]][github-contributors-link]
+
+</div>
+
+<div align="center">
+
+[![][license-shield]][license-link]
+[![][commercial-shield]][commercial-link]
+[![][sponsor-shield]][sponsor-link]
+
+</div>
+
+<div align="center">
+ <a href="https://hellogithub.com/repository/1605492e1e2a4df3be07abfa4578dd37" target="_blank"><img src="https://api.hellogithub.com/v1/widgets/recommend.svg?rid=1605492e1e2a4df3be07abfa4578dd37" alt="Featured｜HelloGitHub" style="width: 200px; height: 43px;" width="200" height="43" /></a>
+ <a href="https://trendshift.io/repositories/11772" target="_blank"><img src="https://trendshift.io/api/badge/repositories/11772" alt="kangfenmao%2Fcherry-studio | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
+ <a href="https://www.producthunt.com/posts/cherry-studio?embed=true&utm_source=badge-featured&utm_medium=badge&utm_souce=badge-cherry&#0045;studio" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=496640&theme=light" alt="Cherry&#0032;Studio - AI&#0032;Chatbots&#0044;&#0032;AI&#0032;Desktop&#0032;Client | Product Hunt" style="width: 200px; height: 43px;" width="200" height="43" /></a>
+</div>
+
+# 🍒 Cherry Studio
+
+Cherry Studio 是一款支持多个大语言模型（LLM）服务商的桌面客户端，兼容 Windows、Mac 和 Linux 系统。
+
+👏 欢迎加入 [Telegram 群组](https://t.me/CherryStudioAI)｜[Discord](https://discord.gg/wez8HtpxqQ) | [QQ群(575014769)](https://qm.qq.com/q/lo0D4qVZKi)
+
+❤️ 喜欢 Cherry Studio? 点亮小星星 🌟 或 [赞助开发者](sponsor.md)! ❤️
+
+# GitCode✖️Cherry Studio【新源力】贡献挑战赛
+
+<p align="center">
+  <a href="https://gitcode.com/CherryHQ/cherry-studio/discussion/2">
+    <img src="https://raw.gitcode.com/user-images/assets/5007375/8d8d7559-1141-4691-b90f-d154558c6896/cherry-studio-gitcode.jpg" width="100%" alt="banner" />
+  </a>
+</p>
+
+# 📖 使用教程
+
+https://docs.cherry-ai.com
+
+# 🌠 界面
+
+![](https://github.com/user-attachments/assets/36dddb2c-e0fb-4a5f-9411-91447bab6e18)
+
+![](https://github.com/user-attachments/assets/f549e8a0-2385-40b4-b52b-2039e39f2930)
+
+![](https://github.com/user-attachments/assets/58e0237c-4d36-40de-b428-53051d982026)
+
+# 🌟 主要特性
+
+1. **多样化 LLM 服务支持**：
+
+- ☁️ 支持主流 LLM 云服务：OpenAI、Gemini、Anthropic、硅基流动等
+- 🔗 集成流行 AI Web 服务：Claude、Peplexity、Poe、腾讯元宝、知乎直答等
+- 💻 支持 Ollama、LM Studio 本地模型部署
+
+2. **智能助手与对话**：
+
+- 📚 内置 300+ 预配置 AI 助手
+- 🤖 支持自定义创建专属助手
+- 💬 多模型同时对话，获得多样化观点
+
+3. **文档与数据处理**：
+
+- 📄 支持文本、图片、Office、PDF 等多种格式
+- ☁️ WebDAV 文件管理与数据备份
+- 📊 Mermaid 图表可视化
+- 💻 代码高亮显示
+
+4. **实用工具集成**：
+
+- 🔍 全局搜索功能
+- 📝 话题管理系统
+- 🔤 AI 驱动的翻译功能
+- 🎯 拖拽排序
+- 🔌 小程序支持
+- ⚙️ MCP(模型上下文协议) 服务
+
+5. **优质使用体验**：
+
+- 🖥️ Windows、Mac、Linux 跨平台支持
+- 📦 开箱即用，无需配置环境
+- 🎨 支持明暗主题与透明窗口
+- 📝 完整的 Markdown 渲染
+- 🤲 便捷的内容分享功能
+
+# 📝 开发计划
+
+我们正在积极开发以下功能和改进：
+
+1. 🎯 **核心功能**
+
+- 选择助手 - 智能内容选择增强
+- 深度研究 - 高级研究能力
+- 全局记忆 - 全局上下文感知
+- 文档预处理 - 改进文档处理能力
+- MCP 市场 - 模型上下文协议生态系统
+
+2. 🗂 **知识管理**
+
+- 笔记与收藏功能
+- 动态画布可视化
+- OCR 光学字符识别
+- TTS 文本转语音支持
+
+3. 📱 **平台支持**
+
+- 鸿蒙版本 (PC)
+- Android 应用（第一期）
+- iOS 应用（第一期）
+- 多窗口支持
+- 窗口置顶功能
+
+4. 🔌 **高级特性**
+
+- 插件系统
+- ASR 语音识别
+- 助手与话题交互重构
+
+在我们的[项目面板](https://github.com/orgs/CherryHQ/projects/7)上跟踪进展并参与贡献。
+
+想要影响开发计划？欢迎加入我们的 [GitHub 讨论区](https://github.com/CherryHQ/cherry-studio/discussions) 分享您的想法和反馈！
+
+# 🌈 主题
+
+- 主题库：https://cherrycss.com
+- Aero 主题：https://github.com/hakadao/CherryStudio-Aero
+- PaperMaterial 主题：https://github.com/rainoffallingstar/CherryStudio-PaperMaterial
+- 仿 Claude 主题：https://github.com/bjl101501/CherryStudio-Claudestyle-dynamic
+- 霓虹枫叶主题：https://github.com/BoningtonChen/CherryStudio_themes
+
+欢迎 PR 更多主题
+
+# 🤝 贡献
+
+我们欢迎对 Cherry Studio 的贡献！您可以通过以下方式贡献：
+
+1. **贡献代码**：开发新功能或优化现有代码
+2. **修复错误**：提交您发现的错误修复
+3. **维护问题**：帮助管理 GitHub 问题
+4. **产品设计**：参与设计讨论
+5. **撰写文档**：改进用户手册和指南
+6. **社区参与**：加入讨论并帮助用户
+7. **推广使用**：宣传 Cherry Studio
+
+参考[分支策略](branching-strategy-zh.md)了解贡献指南
+
+## 入门
+
+1. **Fork 仓库**：Fork 并克隆到您的本地机器
+2. **创建分支**：为您的更改创建分支
+3. **提交更改**：提交并推送您的更改
+4. **打开 Pull Request**：描述您的更改和原因
+
+有关更详细的指南，请参阅我们的 [贡献指南](./CONTRIBUTING.zh.md)
+
+感谢您的支持和贡献！
+
+# 🔗 相关项目
+
+- [one-api](https://github.com/songquanpeng/one-api)：LLM API 管理及分发系统，支持 OpenAI、Azure、Anthropic 等主流模型，统一 API 接口，可用于密钥管理与二次分发。
+
+- [ublacklist](https://github.com/iorate/ublacklist)：屏蔽特定网站在 Google 搜索结果中显示
+
+# 🚀 贡献者
+
+<a href="https://github.com/CherryHQ/cherry-studio/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=CherryHQ/cherry-studio" />
+</a>
+<br /><br />
+
+# ⭐️ Star 记录
+
+[![Star History Chart](https://api.star-history.com/svg?repos=CherryHQ/cherry-studio&type=Timeline)](https://star-history.com/#CherryHQ/cherry-studio&Timeline)
+
+<!-- Links & Images -->
+[deepwiki-shield]: https://img.shields.io/badge/Deepwiki-CherryHQ-0088CC?style=plastic
+[deepwiki-link]: https://deepwiki.com/CherryHQ/cherry-studio
+[twitter-shield]: https://img.shields.io/badge/Twitter-CherryStudioApp-0088CC?style=plastic&logo=x
+[twitter-link]: https://twitter.com/CherryStudioHQ
+[discord-shield]: https://img.shields.io/badge/Discord-@CherryStudio-0088CC?style=plastic&logo=discord
+[discord-link]: https://discord.gg/wez8HtpxqQ
+[telegram-shield]: https://img.shields.io/badge/Telegram-@CherryStudioAI-0088CC?style=plastic&logo=telegram
+[telegram-link]: https://t.me/CherryStudioAI
+
+<!-- 项目统计徽章 -->
+[github-stars-shield]: https://img.shields.io/github/stars/CherryHQ/cherry-studio?style=social
+[github-stars-link]: https://github.com/CherryHQ/cherry-studio/stargazers
+[github-forks-shield]: https://img.shields.io/github/forks/CherryHQ/cherry-studio?style=social
+[github-forks-link]: https://github.com/CherryHQ/cherry-studio/network
+[github-release-shield]: https://img.shields.io/github/v/release/CherryHQ/cherry-studio
+[github-release-link]: https://github.com/CherryHQ/cherry-studio/releases
+[github-contributors-shield]: https://img.shields.io/github/contributors/CherryHQ/cherry-studio
+[github-contributors-link]: https://github.com/CherryHQ/cherry-studio/graphs/contributors
+
+<!-- 许可和赞助徽章 -->
+[license-shield]: https://img.shields.io/badge/License-AGPLv3-important.svg?style=plastic&logo=gnu
+[license-link]: https://www.gnu.org/licenses/agpl-3.0
+[commercial-shield]: https://img.shields.io/badge/商用授权-联系-white.svg?style=plastic&logoColor=white&logo=telegram&color=blue
+[commercial-link]: mailto:license@cherry-ai.com?subject=商业授权咨询
+[sponsor-shield]: https://img.shields.io/badge/赞助支持-FF6699.svg?style=plastic&logo=githubsponsors&logoColor=white
+[sponsor-link]: https://github.com/CherryHQ/cherry-studio/blob/main/docs/sponsor.md

docs/branching-strategy-en.md

@@ -16,8 +16,6 @@ Cherry Studio implements a structured branching strategy to maintain code qualit
   - Only accepts documentation updates and bug fixes
   - Thoroughly tested before production deployment
 
-For details about the `testplan` branch used in the Test Plan, please refer to the [Test Plan](./test-plan.md).
-
 ## Contributing Branches
 
 When contributing to Cherry Studio, please follow these guidelines:

docs/branching-strategy-zh.md

@@ -16,8 +16,6 @@ Cherry Studio 采用结构化的分支策略来维护代码质量并简化开发
   - 只接受文档更新和 bug 修复
   - 经过完整测试后可以发布到生产环境
 
-关于测试计划所使用的`testplan`分支，请查阅[测试计划](./test-plan.md)。
-
 ## 贡献分支
 
 在为 Cherry Studio 贡献代码时，请遵循以下准则：

docs/dev.md

@@ -2,9 +2,7 @@
 
 ## IDE Setup
 
-- Editor: [Cursor](https://www.cursor.com/), etc. Any VS Code compatible editor.
-- Linter: [ESLint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint)
-- Formatter: [Biome](https://marketplace.visualstudio.com/items?itemName=biomejs.biome)
+[Cursor](https://www.cursor.com/) + [ESLint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) + [Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode)
 
 ## Project Setup
 
@@ -18,13 +16,13 @@ yarn
 
 ### Setup Node.js
 
-Download and install [Node.js v22.x.x](https://nodejs.org/en/download)
+Download and install [Node.js v20.x.x](https://nodejs.org/en/download)
 
 ### Setup Yarn
 
 ```bash
 corepack enable
-corepack prepare yarn@4.9.1 --activate
+corepack prepare yarn@4.6.0 --activate
 ```
 
 ### Install Dependencies
@@ -33,12 +31,6 @@ corepack prepare yarn@4.9.1 --activate
 yarn install
 ```
 
-### ENV
-
-```bash
-copy .env.example .env
-```
-
 ### Start
 
 ```bash

docs/en/guides/development.md

@@ -1,73 +0,0 @@
-# 🖥️ Develop
-
-## IDE Setup
-
-- Editor: [Cursor](https://www.cursor.com/), etc. Any VS Code compatible editor.
-- Linter: [ESLint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint)
-- Formatter: [Biome](https://marketplace.visualstudio.com/items?itemName=biomejs.biome)
-
-## Project Setup
-
-### Install
-
-```bash
-yarn
-```
-
-### Development
-
-### Setup Node.js
-
-Download and install [Node.js v22.x.x](https://nodejs.org/en/download)
-
-### Setup Yarn
-
-```bash
-corepack enable
-corepack prepare yarn@4.9.1 --activate
-```
-
-### Install Dependencies
-
-```bash
-yarn install
-```
-
-### ENV
-
-```bash
-copy .env.example .env
-```
-
-### Start
-
-```bash
-yarn dev
-```
-
-### Debug
-
-```bash
-yarn debug
-```
-
-Then input chrome://inspect in browser
-
-### Test
-
-```bash
-yarn test
-```
-
-### Build
-
-```bash
-# For windows
-$ yarn build:win
-
-# For macOS
-$ yarn build:mac
-
-# For Linux
-$ yarn build:linux
-```

docs/en/guides/i18n.md

@@ -1,177 +0,0 @@
-# How to Do i18n Gracefully
-
-> [!WARNING]
-> This document is machine translated from Chinese. While we strive for accuracy, there may be some imperfections in the translation.
-
-## Enhance Development Experience with the i18n Ally Plugin
-
-i18n Ally is a powerful VSCode extension that provides real-time feedback during development, helping developers detect missing or incorrect translations earlier.
-
-The plugin has already been configured in the project — simply install it to get started.
-
-### Advantages During Development
-
-- **Real-time Preview**: Translated texts are displayed directly in the editor.
-- **Error Detection**: Automatically tracks and highlights missing translations or unused keys.
-- **Quick Navigation**: Jump to key definitions with Ctrl/Cmd + click.
-- **Auto-completion**: Provides suggestions when typing i18n keys.
-
-### Demo
-
-![demo-1](../../assets/images/i18n/demo-1.png)
-
-![demo-2](../../assets/images/i18n/demo-2.png)
-
-![demo-3](../../assets/images/i18n/demo-3.png)
-
-## i18n Conventions
-
-### **Avoid Flat Structure at All Costs**
-
-Never use flat structures like `"add.button.tip": "Add"`. Instead, adopt a clear nested structure:
-
-```json
-// Wrong - Flat structure
-{
-  "add.button.tip": "Add",
-  "delete.button.tip": "Delete"
-}
-
-// Correct - Nested structure
-{
-  "add": {
-    "button": {
-      "tip": "Add"
-    }
-  },
-  "delete": {
-    "button": {
-      "tip": "Delete"
-    }
-  }
-}
-```
-
-#### Why Use Nested Structure?
-
-1. **Natural Grouping**: Related texts are logically grouped by their context through object nesting.
-2. **Plugin Requirement**: Tools like i18n Ally require either flat or nested format to properly analyze translation files.
-
-### **Avoid Template Strings in `t()`**
-
-**We strongly advise against using template strings for dynamic interpolation.** While convenient in general JavaScript development, they cause several issues in i18n scenarios.
-
-#### 1. **Plugin Cannot Track Dynamic Keys**
-
-Tools like i18n Ally cannot parse dynamic content within template strings, resulting in:
-
-- No real-time preview
-- No detection of missing translations
-- No navigation to key definitions
-
-```javascript
-// Not recommended - Plugin cannot resolve
-const message = t(`fruits.${fruit}`)
-```
-
-#### 2. **No Real-time Rendering in Editor**
-
-Template strings appear as raw code instead of the final translated text in IDEs, degrading the development experience.
-
-#### 3. **Harder to Maintain**
-
-Since the plugin cannot track such usages, developers must manually verify the existence of corresponding keys in language files.
-
-### Recommended Approach
-
-To avoid missing keys, all dynamically translated texts should first maintain a `FooKeyMap`, then retrieve the translation text through a function.
-
-For example:
-
-```ts
-// src/renderer/src/i18n/label.ts
-const themeModeKeyMap = {
-  dark: 'settings.theme.dark',
-  light: 'settings.theme.light',
-  system: 'settings.theme.system'
-} as const
-
-export const getThemeModeLabel = (key: string): string => {
-  return themeModeKeyMap[key] ? t(themeModeKeyMap[key]) : key
-}
-```
-
-By avoiding template strings, you gain better developer experience, more reliable translation checks, and a more maintainable codebase.
-
-## Automation Scripts
-
-The project includes several scripts to automate i18n-related tasks:
-
-### `check:i18n` - Validate i18n Structure
-
-This script checks:
-
-- Whether all language files use nested structure
-- For missing or unused keys
-- Whether keys are properly sorted
-
-```bash
-yarn check:i18n
-```
-
-### `sync:i18n` - Synchronize JSON Structure and Sort Order
-
-This script uses `zh-cn.json` as the source of truth to sync structure across all language files, including:
-
-1. Adding missing keys, with placeholder `[to be translated]`
-2. Removing obsolete keys
-3. Sorting keys automatically
-
-```bash
-yarn sync:i18n
-```
-
-### `auto:i18n` - Automatically Translate Pending Texts
-
-This script fills in texts marked as `[to be translated]` using machine translation.
-
-Typically, after adding new texts in `zh-cn.json`, run `sync:i18n`, then `auto:i18n` to complete translations.
-
-Before using this script, set the required environment variables:
-
-```bash
-API_KEY="sk-xxx"
-BASE_URL="https://dashscope.aliyuncs.com/compatible-mode/v1/"
-MODEL="qwen-plus-latest"
-```
-
-Alternatively, add these variables directly to your `.env` file.
-
-```bash
-yarn auto:i18n
-```
-
-### `update:i18n` - Object-level Translation Update
-
-Updates translations in language files under `src/renderer/src/i18n/translate` at the object level, preserving existing translations and only updating new content.
-
-**Not recommended** — prefer `auto:i18n` for translation tasks.
-
-```bash
-yarn update:i18n
-```
-
-### Workflow
-
-1. During development, first add the required text in `zh-cn.json`
-2. Confirm it displays correctly in the Chinese environment
-3. Run `yarn sync:i18n` to propagate the keys to other language files
-4. Run `yarn auto:i18n` to perform machine translation
-5. Grab a coffee and let the magic happen!
-
-## Best Practices
-
-1. **Use Chinese as Source Language**: All development starts in Chinese, then translates to other languages.
-2. **Run Check Script Before Commit**: Use `yarn check:i18n` to catch i18n issues early.
-3. **Translate in Small Increments**: Avoid accumulating a large backlog of untranslated content.
-4. **Keep Keys Semantically Clear**: Keys should clearly express their purpose, e.g., `user.profile.avatar.upload.error`

docs/en/guides/logging.md

@@ -1,191 +0,0 @@
-# How to use the LoggerService
-
-This is a developer document on how to use the logger.
-
-CherryStudio uses a unified logging service to print and record logs. **Unless there is a special reason, do not use `console.xxx` to print logs**.
-
-The following are detailed instructions.
-
-## Usage in the `main` process
-
-### Importing
-
-```typescript
-import { loggerService } from '@logger'
-```
-
-### Setting module information (Required by convention)
-
-After the import statements, set it up as follows:
-
-```typescript
-const logger = loggerService.withContext('moduleName')
-```
-
-- `moduleName` is the name of the current file's module. It can be named after the filename, main class name, main function name, etc. The principle is to be clear and understandable.
-- `moduleName` will be printed in the terminal and will also be present in the file log, making it easier to filter.
-
-### Setting `CONTEXT` information (Optional)
-
-In `withContext`, you can also set other `CONTEXT` information:
-
-```typescript
-const logger = loggerService.withContext('moduleName', CONTEXT)
-```
-
-- `CONTEXT` is an object of the form `{ key: value, ... }`.
-- `CONTEXT` information will not be printed in the terminal, but it will be recorded in the file log, making it easier to filter.
-
-### Logging
-
-In your code, you can call `logger` at any time to record logs. The supported levels are: `error`, `warn`, `info`, `verbose`, `debug`, and `silly`.
-For the meaning of each level, please refer to the subsequent sections.
-
-The following are the supported parameters for logging (using `logger.LEVEL` as an example, where `LEVEL` represents one of the levels mentioned above):
-
-```typescript
-logger.LEVEL(message)
-logger.LEVEL(message, CONTEXT)
-logger.LEVEL(message, error)
-logger.LEVEL(message, error, CONTEXT)
-```
-
-**Only the four calling methods above are supported**.
-
-| Parameter | Type     | Description                                                                                                                                                                                                                                                                                                                   |
-| --------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `message` | `string` | Required. This is the core field of the log, containing the main content to be recorded.                                                                                                                                                                                                                                      |
-| `CONTEXT` | `object` | Optional. Additional information to be recorded in the log file. It is recommended to use the `{ key: value, ...}` format.                                                                                                                                                                                                    |
-| `error`   | `Error`  | Optional. The error stack trace will also be printed.<br />Note that the `error` caught by `catch(error)` is of the `unknown` type. According to TypeScript best practices, you should first use `instanceof` for type checking. If you are certain it is an `Error` type, you can also use a type assertion like `as Error`. |
-
-#### Recording non-`object` type context information
-
-```typescript
-const foo = getFoo()
-logger.debug(`foo ${foo}`)
-```
-
-### Log Levels
-
-- In the development environment, all log levels are printed to the terminal and recorded in the file log.
-- In the production environment, the default log level is `info`. Logs are only recorded to the file and are not printed to the terminal.
-
-Changing the log level:
-
-- You can change the log level with `logger.setLevel('newLevel')`.
-- `logger.resetLevel()` resets it to the default level.
-- `logger.getLevel()` gets the current log level.
-
-**Note:** Changing the log level has a global effect. Please do not change it arbitrarily in your code unless you are very clear about what you are doing.
-
-## Usage in the `renderer` process
-
-Usage in the `renderer` process for _importing_, _setting module information_, and _setting context information_ is **exactly the same** as in the `main` process.
-The following section focuses on the differences.
-
-### `initWindowSource`
-
-In the `renderer` process, there are different `window`s. Before starting to use the `logger`, we must set the `window` information:
-
-```typescript
-loggerService.initWindowSource('windowName')
-```
-
-As a rule, we will set this in the `window`'s `entryPoint.tsx`. This ensures that `windowName` is set before it's used.
-
-- An error will be thrown if `windowName` is not set, and the `logger` will not work.
-- `windowName` can only be set once; subsequent attempts to set it will have no effect.
-- `windowName` will not be printed in the `devTool`'s `console`, but it will be recorded in the `main` process terminal and the file log.
-- `initWindowSource` returns the LoggerService instance, allowing for method chaining.
-
-### Log Levels
-
-- In the development environment, all log levels are printed to the `devTool`'s `console` by default.
-- In the production environment, the default log level is `info`, and logs are printed to the `devTool`'s `console`.
-- In both development and production environments, `warn` and `error` level logs are, by default, transmitted to the `main` process and recorded in the file log.
-  - In the development environment, the `main` process terminal will also print the logs transmitted from the renderer.
-
-#### Changing the Log Level
-
-Same as in the `main` process, you can manage the log level using `setLevel('level')`, `resetLevel()`, and `getLevel()`.
-Similarly, changing the log level is a global adjustment.
-
-#### Changing the Level Transmitted to `main`
-
-Logs from the `renderer` are sent to `main` to be managed and recorded to a file centrally (according to `main`'s file logging level). By default, only `warn` and `error` level logs are transmitted to `main`.
-
-There are two ways to change the log level for transmission to `main`:
-
-##### Global Change
-
-The following methods can be used to set, reset, and get the log level for transmission to `main`, respectively.
-
-```typescript
-logger.setLogToMainLevel('newLevel')
-logger.resetLogToMainLevel()
-logger.getLogToMainLevel()
-```
-
-**Note:** This method has a global effect. Please do not change it arbitrarily in your code unless you are very clear about what you are doing.
-
-##### Per-log Change
-
-By adding `{ logToMain: true }` at the end of the log call, you can force a single log entry to be transmitted to `main` (bypassing the global log level restriction), for example:
-
-```typescript
-logger.info('message', { logToMain: true })
-```
-
-## About `worker` Threads
-
-- Currently, logging is not supported for workers in the `main` process.
-- Logging is supported for workers started in the `renderer` process, but currently these logs are not sent to `main` for recording.
-
-### How to Use Logging in `renderer` Workers
-
-Since worker threads are independent, using LoggerService in them is equivalent to using it in a new `renderer` window. Therefore, you must first call `initWindowSource`.
-
-If the worker is relatively simple (just one file), you can also use method chaining directly:
-
-```typescript
-const logger = loggerService.initWindowSource('Worker').withContext('LetsWork')
-```
-
-## Filtering Logs with Environment Variables
-
-In a development environment, you can define environment variables to filter displayed logs by level and module. This helps developers focus on their specific logs and improves development efficiency.
-
-Environment variables can be set in the terminal or defined in the `.env` file in the project's root directory. The available variables are as follows:
-
-| Variable Name                    | Description                                                                                                                                                                 |
-| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `CSLOGGER_MAIN_LEVEL`            | Log level for the `main` process. Logs below this level will not be displayed.                                                                                              |
-| `CSLOGGER_MAIN_SHOW_MODULES`     | Filters log modules for the `main` process. Use a comma (`,`) to separate modules. The filter is case-sensitive. Only logs from modules in this list will be displayed.     |
-| `CSLOGGER_RENDERER_LEVEL`        | Log level for the `renderer` process. Logs below this level will not be displayed.                                                                                          |
-| `CSLOGGER_RENDERER_SHOW_MODULES` | Filters log modules for the `renderer` process. Use a comma (`,`) to separate modules. The filter is case-sensitive. Only logs from modules in this list will be displayed. |
-
-Example:
-
-```bash
-CSLOGGER_MAIN_LEVEL=verbose
-CSLOGGER_MAIN_SHOW_MODULES=MCPService,SelectionService
-```
-
-Note:
-
-- Environment variables are only effective in the development environment.
-- These variables only affect the logs displayed in the terminal or DevTools. They do not affect file logging or the `logToMain` recording logic.
-
-## Log Level Usage Guidelines
-
-There are many log levels. The following are the guidelines that should be followed in CherryStudio for when to use each level:
-(Arranged from highest to lowest log level)
-
-| Log Level     | Core Definition & Use case                                                                                                                                                                          | Example                                                                                                                                                                                                            |
-| :------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`error`**   | **Critical error causing the program to crash or core functionality to become unusable.** <br> This is the highest-priority log, usually requiring immediate reporting or user notification.        | - Main or renderer process crash. <br> - Failure to read/write critical user data files (e.g., database, configuration files), preventing the application from running. <br> - All unhandled exceptions.           |
-| **`warn`**    | **Potential issue or unexpected situation that does not affect the program's core functionality.** <br> The program can recover or use a fallback.                                                  | - Configuration file `settings.json` is missing; started with default settings. <br> - Auto-update check failed, but does not affect the use of the current version. <br> - A non-essential plugin failed to load. |
-| **`info`**    | **Records application lifecycle events and key user actions.** <br> This is the default level that should be recorded in a production release to trace the user's main operational path.            | - Application start, exit. <br> - User successfully opens/saves a file. <br> - Main window created/closed. <br> - Starting an important task (e.g., "Start video export").                                         |
-| **`verbose`** | **More detailed flow information than `info`, used for tracing specific features.** <br> Enabled when diagnosing issues with a specific feature to help understand the internal execution flow.     | - Loading `Toolbar` module. <br> - IPC message `open-file-dialog` sent from the renderer process. <br> - Applying filter 'Sepia' to the image.                                                                     |
-| **`debug`**   | **Detailed diagnostic information used during development and debugging.** <br> **Must not be enabled by default in production releases**, as it may contain sensitive data and impact performance. | - Parameters for function `renderImage`: `{ width: 800, ... }`. <br> - Specific data content received by IPC message `save-file`. <br> - Details of Redux/Vuex state changes in the renderer process.              |
-| **`silly`**   | **The most detailed, low-level information, used only for extreme debugging.** <br> Rarely used in regular development; only for solving very difficult problems.                                   | - Real-time mouse coordinates `(x: 150, y: 320)`. <br> - Size of each data chunk when reading a file. <br> - Time taken for each rendered frame.                                                                   |

docs/en/guides/test-plan.md

@@ -1,101 +0,0 @@
-# Test Plan
-
-To provide users with a more stable application experience and faster iteration speed, Cherry Studio has launched the "Test Plan".
-
-## User Guide
-
-The Test Plan is divided into the RC channel and the Beta channel, with the following differences:
-
-- **RC (Release Candidate)**: The features are stable, with fewer bugs, and it is close to the official release.
-- **Beta**: Features may change at any time, and there may be more bugs, but users can experience future features earlier.
-
-Users can enable the "Test Plan" and select the version channel in the software's `Settings` > `About`. Please note that the versions in the "Test Plan" cannot guarantee data consistency, so be sure to back up your data before using them.
-
-After enabling the RC channel or Beta channel, if a stable version is released, users will still be upgraded to the stable version.
-
-Users are welcome to submit issues or provide feedback through other channels for any bugs encountered during testing. Your feedback is very important to us.
-
-## Developer Guide
-
-### Participating in the Test Plan
-
-Developers should submit `PRs` according to the [Contributor Guide](../../CONTRIBUTING.md) (and ensure the target branch is `main`). The repository maintainers will evaluate whether the `PR` should be included in the Test Plan based on factors such as the impact of the feature on the application, its importance, and whether broader testing is needed.
-
-If the `PR` is added to the Test Plan, the repository maintainers will:
-
-- Notify the `PR` submitter.
-- Set the PR to `draft` status (to avoid accidental merging into `main` before testing is complete).
-- Set the `milestone` to the specific Test Plan version.
-- Modify the `PR` title.
-
-During participation in the Test Plan, `PR` submitters should:
-
-- Keep the `PR` branch synchronized with the latest `main` (i.e., the `PR` branch should always be based on the latest `main` code).
-- Ensure the `PR` branch is conflict-free.
-- Actively respond to comments & reviews and fix bugs.
-- Enable maintainers to modify the `PR` branch to allow for bug fixes at any time.
-
-Inclusion in the Test Plan does not guarantee the final merging of the `PR`. It may be shelved due to immature features or poor testing feedback.
-
-### Test Plan Lead
-
-A maintainer will be assigned as the lead for a specific version (e.g., `1.5.0-rc`). The responsibilities of the Test Plan lead include:
-
-- Determining whether a `PR` meets the Test Plan requirements and deciding whether it should be included in the current Test Plan.
-- Modifying the status of `PRs` added to the Test Plan and communicating relevant matters with the `PR` submitter.
-- Before the Test Plan release, merging the branches of `PRs` added to the Test Plan (using squash merge) into the corresponding version branch of `testplan` and resolving conflicts.
-- Ensuring the `testplan` branch is synchronized with the latest `main`.
-- Overseeing the Test Plan release.
-
-## In-Depth Understanding
-
-### About `PRs`
-
-A `PR` is a collection of a specific branch (and commits), comments, reviews, and other information, and it is the **smallest management unit** of the Test Plan.
-
-Compared to submitting all features to a single branch, the Test Plan manages features through `PRs`, which offers greater flexibility and efficiency:
-
-- Features can be added or removed between different versions of the Test Plan without cumbersome `revert` operations.
-- Clear feature boundaries and responsibilities are established. Bug fixes are completed within their respective `PRs`, isolating cross-impact and better tracking progress.
-- The `PR` submitter is responsible for resolving conflicts with the latest `main`. The Test Plan lead is responsible for resolving conflicts between `PR` branches. However, since features added to the Test Plan are relatively independent (in other words, if a feature has broad implications, it should be independently included in the Test Plan), conflicts are generally few or simple.
-
-### The `testplan` Branch
-
-The `testplan` branch is a **temporary** branch used for Test Plan releases.
-
-Note:
-
-- **Do not develop based on this branch**. It may change or even be deleted at any time, and there is no guarantee of commit completeness or order.
-- **Do not submit `commits` or `PRs` to this branch**, as they will not be retained.
-- The `testplan` branch is always based on the latest `main` branch (not on a released version), with features added on top.
-
-#### RC Branch
-
-Branch name: `testplan/rc/x.y.z`
-
-Used for RC releases, where `x.y.z` is the target version number. Note that whether it is rc.1 or rc.5, as long as the major version number is `x.y.z`, it is completed in this branch.
-
-Generally, the version number for releases from this branch is named `x.y.z-rc.n`.
-
-#### Beta Branch
-
-Branch name: `testplan/beta/x.y.z`
-
-Used for Beta releases, where `x.y.z` is the target version number. Note that whether it is beta.1 or beta.5, as long as the major version number is `x.y.z`, it is completed in this branch.
-
-Generally, the version number for releases from this branch is named `x.y.z-beta.n`.
-
-### Version Rules
-
-The application version number for the Test Plan is: `x.y.z-CHA.n`, where:
-
-- `x.y.z` is the conventional version number, referred to here as the **target version number**.
-- `CHA` is the channel code (Channel), currently divided into `rc` and `beta`.
-- `n` is the release number, starting from `1`.
-
-Examples of complete version numbers: `1.5.0-rc.3`, `1.5.1-beta.1`, `1.6.0-beta.6`.
-
-The **target version number** of the Test Plan points to the official version number where these features are expected to be added. For example:
-
-- `1.5.0-rc.3` means this is a preview of the `1.5.0` official release (the current latest official release is `1.4.9`, and `1.5.0` has not yet been officially released).
-- `1.5.1-beta.1` means this is a beta version of the `1.5.1` official release (the current latest official release is `1.5.0`, and `1.5.1` has not yet been officially released).

docs/en/references/app-upgrade.md

@@ -1,430 +0,0 @@
-# Update Configuration System Design Document
-
-## Background
-
-Currently, AppUpdater directly queries the GitHub API to retrieve beta and rc update information. To support users in China, we need to fetch a static JSON configuration file from GitHub/GitCode based on IP geolocation, which contains update URLs for all channels.
-
-## Design Goals
-
-1. Support different configuration sources based on IP geolocation (GitHub/GitCode)
-2. Support version compatibility control (e.g., users below v1.x must upgrade to v1.7.0 before upgrading to v2.0)
-3. Easy to extend, supporting future multi-major-version upgrade paths (v1.6 → v1.7 → v2.0 → v2.8 → v3.0)
-4. Maintain compatibility with existing electron-updater mechanism
-
-## Current Version Strategy
-
-- **v1.7.x** is the last version of the 1.x series
-- Users **below v1.7.0** must first upgrade to v1.7.0 (or higher 1.7.x version)
-- Users **v1.7.0 and above** can directly upgrade to v2.x.x
-
-## Automation Workflow
-
-The `x-files/app-upgrade-config/app-upgrade-config.json` file is synchronized by the [`Update App Upgrade Config`](../../.github/workflows/update-app-upgrade-config.yml) workflow. The workflow runs the [`scripts/update-app-upgrade-config.ts`](../../scripts/update-app-upgrade-config.ts) helper so that every release tag automatically updates the JSON in `x-files/app-upgrade-config`.
-
-### Trigger Conditions
-
-- **Release events (`release: released/prereleased`)**  
-  - Draft releases are ignored.  
-  - When GitHub marks the release as _prerelease_, the tag must include `-beta`/`-rc` (with optional numeric suffix). Otherwise the workflow exits early.  
-  - When GitHub marks the release as stable, the tag must match the latest release returned by the GitHub API. This prevents out-of-order updates when publishing historical tags.  
-  - If the guard clauses pass, the version is tagged as `latest` or `beta/rc` based on its semantic suffix and propagated to the script through the `IS_PRERELEASE` flag.
-- **Manual dispatch (`workflow_dispatch`)**  
-  - Required input: `tag` (e.g., `v2.0.1`). Optional input: `is_prerelease` (defaults to `false`).  
-  - When `is_prerelease=true`, the tag must carry a beta/rc suffix, mirroring the automatic validation.  
-  - Manual runs still download the latest release metadata so that the workflow knows whether the tag represents the newest stable version (for documentation inside the PR body).
-
-### Workflow Steps
-
-1. **Guard + metadata preparation** – the `Check if should proceed` and `Prepare metadata` steps compute the target tag, prerelease flag, whether the tag is the newest release, and a `safe_tag` slug used for branch names. When any rule fails, the workflow stops without touching the config.
-2. **Checkout source branches** – the default branch is checked out into `main/`, while the long-lived `x-files/app-upgrade-config` branch lives in `cs/`. All modifications happen in the latter directory.
-3. **Install toolchain** – Node.js 22, Corepack, and frozen Yarn dependencies are installed inside `main/`.
-4. **Run the update script** – `yarn tsx scripts/update-app-upgrade-config.ts --tag <tag> --config ../cs/app-upgrade-config.json --is-prerelease <flag>` updates the JSON in-place.  
-   - The script normalizes the tag (e.g., strips `v` prefix), detects the release channel (`latest`, `rc`, `beta`), and loads segment rules from `config/app-upgrade-segments.json`.  
-   - It validates that prerelease flags and semantic suffixes agree, enforces locked segments, builds mirror feed URLs, and performs release-availability checks (GitHub HEAD request for every channel; GitCode GET for latest channels, falling back to `https://releases.cherry-ai.com` when gitcode is delayed).  
-   - After updating the relevant channel entry, the script rewrites the config with semver-sort order and a new `lastUpdated` timestamp.
-5. **Detect changes + create PR** – if `cs/app-upgrade-config.json` changed, the workflow opens a PR `chore/update-app-upgrade-config/<safe_tag>` against `x-files/app-upgrade-config` with a commit message `🤖 chore: sync app-upgrade-config for <tag>`. Otherwise it logs that no update is required.
-
-### Manual Trigger Guide
-
-1. Open the Cherry Studio repository on GitHub → **Actions** tab → select **Update App Upgrade Config**.
-2. Click **Run workflow**, choose the default branch (usually `main`), and fill in the `tag` input (e.g., `v2.1.0`).  
-3. Toggle `is_prerelease` only when the tag carries a prerelease suffix (`-beta`, `-rc`). Leave it unchecked for stable releases.  
-4. Start the run and wait for it to finish. Check the generated PR in the `x-files/app-upgrade-config` branch, verify the diff in `app-upgrade-config.json`, and merge once validated.
-
-## JSON Configuration File Format
-
-### File Location
-
-- **GitHub**: `https://raw.githubusercontent.com/CherryHQ/cherry-studio/refs/heads/x-files/app-upgrade-config/app-upgrade-config.json`
-- **GitCode**: `https://gitcode.com/CherryHQ/cherry-studio/raw/x-files/app-upgrade-config/app-upgrade-config.json`
-
-**Note**: Both mirrors provide the same configuration file hosted on the `x-files/app-upgrade-config` branch. The client automatically selects the optimal mirror based on IP geolocation.
-
-### Configuration Structure (Current Implementation)
-
-```json
-{
-  "lastUpdated": "2025-01-05T00:00:00Z",
-  "versions": {
-    "1.6.7": {
-      "minCompatibleVersion": "1.0.0",
-      "description": "Last stable v1.7.x release - required intermediate version for users below v1.7",
-      "channels": {
-        "latest": {
-          "version": "1.6.7",
-          "feedUrls": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.6.7",
-            "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/download/v1.6.7"
-          }
-        },
-        "rc": {
-          "version": "1.6.0-rc.5",
-          "feedUrls": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.6.0-rc.5",
-            "gitcode": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.6.0-rc.5"
-          }
-        },
-        "beta": {
-          "version": "1.6.7-beta.3",
-          "feedUrls": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.7.0-beta.3",
-            "gitcode": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.7.0-beta.3"
-          }
-        }
-      }
-    },
-    "2.0.0": {
-      "minCompatibleVersion": "1.7.0",
-      "description": "Major release v2.0 - required intermediate version for v2.x upgrades",
-      "channels": {
-        "latest": null,
-        "rc": null,
-        "beta": null
-      }
-    }
-  }
-}
-```
-
-### Future Extension Example
-
-When releasing v3.0, if users need to first upgrade to v2.8, you can add:
-
-```json
-{
-  "2.8.0": {
-    "minCompatibleVersion": "2.0.0",
-    "description": "Stable v2.8 - required for v3 upgrade",
-    "channels": {
-      "latest": {
-        "version": "2.8.0",
-        "feedUrls": {
-          "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v2.8.0",
-          "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/download/v2.8.0"
-        }
-      },
-      "rc": null,
-      "beta": null
-    }
-  },
-  "3.0.0": {
-    "minCompatibleVersion": "2.8.0",
-    "description": "Major release v3.0",
-    "channels": {
-      "latest": {
-        "version": "3.0.0",
-        "feedUrls": {
-          "github": "https://github.com/CherryHQ/cherry-studio/releases/latest",
-          "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/latest"
-        }
-      },
-      "rc": {
-        "version": "3.0.0-rc.1",
-        "feedUrls": {
-          "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v3.0.0-rc.1",
-          "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/download/v3.0.0-rc.1"
-        }
-      },
-      "beta": null
-    }
-  }
-}
-```
-
-### Field Descriptions
-
-- `lastUpdated`: Last update time of the configuration file (ISO 8601 format)
-- `versions`: Version configuration object, key is the version number, sorted by semantic versioning
-  - `minCompatibleVersion`: Minimum compatible version that can upgrade to this version
-  - `description`: Version description
-  - `channels`: Update channel configuration
-    - `latest`: Stable release channel
-    - `rc`: Release Candidate channel
-    - `beta`: Beta testing channel
-    - Each channel contains:
-      - `version`: Version number for this channel
-      - `feedUrls`: Multi-mirror URL configuration
-        - `github`: electron-updater feed URL for GitHub mirror
-        - `gitcode`: electron-updater feed URL for GitCode mirror
-  - `metadata`: Stable mapping info for automation
-    - `segmentId`: ID from `config/app-upgrade-segments.json`
-    - `segmentType`: Optional flag (`legacy` | `breaking` | `latest`) for documentation/debugging
-
-## TypeScript Type Definitions
-
-```typescript
-// Mirror enum
-enum UpdateMirror {
-  GITHUB = 'github',
-  GITCODE = 'gitcode'
-}
-
-interface UpdateConfig {
-  lastUpdated: string
-  versions: {
-    [versionKey: string]: VersionConfig
-  }
-}
-
-interface VersionConfig {
-  minCompatibleVersion: string
-  description: string
-  channels: {
-    latest: ChannelConfig | null
-    rc: ChannelConfig | null
-    beta: ChannelConfig | null
-  }
-  metadata?: {
-    segmentId: string
-    segmentType?: 'legacy' | 'breaking' | 'latest'
-  }
-}
-
-interface ChannelConfig {
-  version: string
-  feedUrls: Record<UpdateMirror, string>
-  // Equivalent to:
-  // feedUrls: {
-  //   github: string
-  //   gitcode: string
-  // }
-}
-```
-
-## Segment Metadata & Breaking Markers
-
-- **Segment definitions** now live in `config/app-upgrade-segments.json`. Each segment describes a semantic-version range (or exact matches) plus metadata such as `segmentId`, `segmentType`, `minCompatibleVersion`, and per-channel feed URL templates.
-- Each entry under `versions` carries a `metadata.segmentId`. This acts as the stable key that scripts use to decide which slot to update, even if the actual semantic version string changes.
-- Mark major upgrade gateways (e.g., `2.0.0`) by giving the related segment a `segmentType: "breaking"` and (optionally) `lockedVersion`. This prevents automation from accidentally moving that entry when other 2.x builds ship.
-- Adding another breaking hop (e.g., `3.0.0`) only requires defining a new segment in the JSON file; the automation will pick it up on the next run.
-
-## Automation Workflow
-
-Starting from this change, `.github/workflows/update-app-upgrade-config.yml` listens to GitHub release events (published + prerelease). The workflow:
-
-1. Checks out the default branch (for scripts) and the `x-files/app-upgrade-config` branch (where the config is hosted).
-2. Runs `yarn tsx scripts/update-app-upgrade-config.ts --tag <tag> --config ../cs/app-upgrade-config.json` to regenerate the config directly inside the `x-files/app-upgrade-config` working tree.
-3. If the file changed, it opens a PR against `x-files/app-upgrade-config` via `peter-evans/create-pull-request`, with the generated diff limited to `app-upgrade-config.json`.
-
-You can run the same script locally via `yarn update:upgrade-config --tag v2.1.6 --config ../cs/app-upgrade-config.json` (add `--dry-run` to preview) to reproduce or debug whatever the workflow does. Passing `--skip-release-checks` along with `--dry-run` lets you bypass the release-page existence check (useful when the GitHub/GitCode pages aren’t published yet). Running without `--config` continues to update the copy in your current working directory (main branch) for documentation purposes.
-
-## Version Matching Logic
-
-### Algorithm Flow
-
-1. Get user's current version (`currentVersion`) and requested channel (`requestedChannel`)
-2. Get all version numbers from configuration file, sort in descending order by semantic versioning
-3. Iterate through the sorted version list:
-   - Check if `currentVersion >= minCompatibleVersion`
-   - Check if the requested `channel` exists and is not `null`
-   - If conditions are met, return the channel configuration
-4. If no matching version is found, return `null`
-
-### Pseudocode Implementation
-
-```typescript
-function findCompatibleVersion(
-  currentVersion: string,
-  requestedChannel: UpgradeChannel,
-  config: UpdateConfig
-): ChannelConfig | null {
-  // Get all version numbers and sort in descending order
-  const versions = Object.keys(config.versions).sort(semver.rcompare)
-
-  for (const versionKey of versions) {
-    const versionConfig = config.versions[versionKey]
-    const channelConfig = versionConfig.channels[requestedChannel]
-
-    // Check version compatibility and channel availability
-    if (
-      semver.gte(currentVersion, versionConfig.minCompatibleVersion) &&
-      channelConfig !== null
-    ) {
-      return channelConfig
-    }
-  }
-
-  return null // No compatible version found
-}
-```
-
-## Upgrade Path Examples
-
-### Scenario 1: v1.6.5 User Upgrade (Below 1.7)
-
-- **Current Version**: 1.6.5
-- **Requested Channel**: latest
-- **Match Result**: 1.7.0
-- **Reason**: 1.6.5 >= 0.0.0 (satisfies 1.7.0's minCompatibleVersion), but doesn't satisfy 2.0.0's minCompatibleVersion (1.7.0)
-- **Action**: Prompt user to upgrade to 1.7.0, which is the required intermediate version for v2.x upgrade
-
-### Scenario 2: v1.6.5 User Requests rc/beta
-
-- **Current Version**: 1.6.5
-- **Requested Channel**: rc or beta
-- **Match Result**: 1.7.0 (latest)
-- **Reason**: 1.7.0 version doesn't provide rc/beta channels (values are null)
-- **Action**: Upgrade to 1.7.0 stable version
-
-### Scenario 3: v1.7.0 User Upgrades to Latest
-
-- **Current Version**: 1.7.0
-- **Requested Channel**: latest
-- **Match Result**: 2.0.0
-- **Reason**: 1.7.0 >= 1.7.0 (satisfies 2.0.0's minCompatibleVersion)
-- **Action**: Directly upgrade to 2.0.0 (current latest stable version)
-
-### Scenario 4: v1.7.2 User Upgrades to RC Version
-
-- **Current Version**: 1.7.2
-- **Requested Channel**: rc
-- **Match Result**: 2.0.0-rc.1
-- **Reason**: 1.7.2 >= 1.7.0 (satisfies 2.0.0's minCompatibleVersion), and rc channel exists
-- **Action**: Upgrade to 2.0.0-rc.1
-
-### Scenario 5: v1.7.0 User Upgrades to Beta Version
-
-- **Current Version**: 1.7.0
-- **Requested Channel**: beta
-- **Match Result**: 2.0.0-beta.1
-- **Reason**: 1.7.0 >= 1.7.0, and beta channel exists
-- **Action**: Upgrade to 2.0.0-beta.1
-
-### Scenario 6: v2.5.0 User Upgrade (Future)
-
-Assuming v2.8.0 and v3.0.0 configurations have been added:
-- **Current Version**: 2.5.0
-- **Requested Channel**: latest
-- **Match Result**: 2.8.0
-- **Reason**: 2.5.0 >= 2.0.0 (satisfies 2.8.0's minCompatibleVersion), but doesn't satisfy 3.0.0's requirement
-- **Action**: Prompt user to upgrade to 2.8.0, which is the required intermediate version for v3.x upgrade
-
-## Code Changes
-
-### Main Modifications
-
-1. **New Methods**
-   - `_fetchUpdateConfig(ipCountry: string): Promise<UpdateConfig | null>` - Fetch configuration file based on IP
-   - `_findCompatibleChannel(currentVersion: string, channel: UpgradeChannel, config: UpdateConfig): ChannelConfig | null` - Find compatible channel configuration
-
-2. **Modified Methods**
-   - `_getReleaseVersionFromGithub()` → Remove or refactor to `_getChannelFeedUrl()`
-   - `_setFeedUrl()` - Use new configuration system to replace existing logic
-
-3. **New Type Definitions**
-   - `UpdateConfig`
-   - `VersionConfig`
-   - `ChannelConfig`
-
-### Mirror Selection Logic
-
-The client automatically selects the optimal mirror based on IP geolocation:
-
-```typescript
-private async _setFeedUrl() {
-  const currentVersion = app.getVersion()
-  const testPlan = configManager.getTestPlan()
-  const requestedChannel = testPlan ? this._getTestChannel() : UpgradeChannel.LATEST
-
-  // Determine mirror based on IP country
-  const ipCountry = await getIpCountry()
-  const mirror = ipCountry.toLowerCase() === 'cn' ? 'gitcode' : 'github'
-
-  // Fetch update config
-  const config = await this._fetchUpdateConfig(mirror)
-
-  if (config) {
-    const channelConfig = this._findCompatibleChannel(currentVersion, requestedChannel, config)
-    if (channelConfig) {
-      // Select feed URL from the corresponding mirror
-      const feedUrl = channelConfig.feedUrls[mirror]
-      this._setChannel(requestedChannel, feedUrl)
-      return
-    }
-  }
-
-  // Fallback logic
-  const defaultFeedUrl = mirror === 'gitcode'
-    ? FeedUrl.PRODUCTION
-    : FeedUrl.GITHUB_LATEST
-  this._setChannel(UpgradeChannel.LATEST, defaultFeedUrl)
-}
-
-private async _fetchUpdateConfig(mirror: 'github' | 'gitcode'): Promise<UpdateConfig | null> {
-  const configUrl = mirror === 'gitcode'
-    ? UpdateConfigUrl.GITCODE
-    : UpdateConfigUrl.GITHUB
-
-  try {
-    const response = await net.fetch(configUrl, {
-      headers: {
-        'User-Agent': generateUserAgent(),
-        'Accept': 'application/json',
-        'X-Client-Id': configManager.getClientId()
-      }
-    })
-    return await response.json() as UpdateConfig
-  } catch (error) {
-    logger.error('Failed to fetch update config:', error)
-    return null
-  }
-}
-```
-
-## Fallback and Error Handling Strategy
-
-1. **Configuration file fetch failure**: Log error, return current version, don't offer updates
-2. **No matching version**: Notify user that current version doesn't support automatic upgrade
-3. **Network exception**: Cache last successfully fetched configuration (optional)
-
-## GitHub Release Requirements
-
-To support intermediate version upgrades, the following files need to be retained:
-
-- **v1.7.0 release** and its latest*.yml files (as upgrade target for users below v1.7)
-- Future intermediate versions (e.g., v2.8.0) need to retain corresponding release and latest*.yml files
-- Complete installation packages for each version
-
-### Currently Required Releases
-
-| Version | Purpose | Must Retain |
-|---------|---------|-------------|
-| v1.7.0 | Upgrade target for users below 1.7 | ✅ Yes |
-| v2.0.0-rc.1 | RC testing channel | ❌ Optional |
-| v2.0.0-beta.1 | Beta testing channel | ❌ Optional |
-| latest | Latest stable version (automatic) | ✅ Yes |
-
-## Advantages
-
-1. **Flexibility**: Supports arbitrarily complex upgrade paths
-2. **Extensibility**: Adding new versions only requires adding new entries to the configuration file
-3. **Maintainability**: Configuration is separated from code, allowing upgrade strategy adjustments without releasing new versions
-4. **Multi-source support**: Automatically selects optimal configuration source based on geolocation
-5. **Version control**: Enforces intermediate version upgrades, ensuring data migration and compatibility
-
-## Future Extensions
-
-- Support more granular version range control (e.g., `>=1.5.0 <1.8.0`)
-- Support multi-step upgrade path hints (e.g., notify user needs 1.5 → 1.8 → 2.0)
-- Support A/B testing and gradual rollout
-- Support local caching and expiration strategy for configuration files

docs/en/references/components/code-block-view.md

@@ -1,180 +0,0 @@
-# CodeBlockView Component Structure
-
-## Overview
-
-CodeBlockView is the core component in Cherry Studio for displaying and manipulating code blocks. It supports multiple view modes and visual previews for special languages, providing rich interactive tools.
-
-## Component Structure
-
-```mermaid
-graph TD
-    A[CodeBlockView] --> B[CodeToolbar]
-    A --> C[SourceView]
-    A --> D[SpecialView]
-    A --> E[StatusBar]
-
-    B --> F[CodeToolButton]
-
-    C --> G[CodeEditor / CodeViewer]
-
-    D --> H[MermaidPreview]
-    D --> I[PlantUmlPreview]
-    D --> J[SvgPreview]
-    D --> K[GraphvizPreview]
-
-    F --> L[useCopyTool]
-    F --> M[useDownloadTool]
-    F --> N[useViewSourceTool]
-    F --> O[useSplitViewTool]
-    F --> P[useRunTool]
-    F --> Q[useExpandTool]
-    F --> R[useWrapTool]
-    F --> S[useSaveTool]
-```
-
-## Core Concepts
-
-### View Types
-
-- **preview**: Preview view, where non-source code is displayed as special views
-- **edit**: Edit view
-
-### View Modes
-
-- **source**: Source code view mode
-- **special**: Special view mode (Mermaid, PlantUML, SVG)
-- **split**: Split view mode (source code and special view displayed side by side)
-
-### Special View Languages
-
-- mermaid
-- plantuml
-- svg
-- dot
-- graphviz
-
-## Component Details
-
-### CodeBlockView Main Component
-
-Main responsibilities:
-
-1. Managing view mode state
-2. Coordinating the display of source code view and special view
-3. Managing toolbar tools
-4. Handling code execution state
-
-### Subcomponents
-
-#### CodeToolbar
-
-- Toolbar displayed at the top-right corner of the code block
-- Contains core and quick tools
-- Dynamically displays relevant tools based on context
-
-#### CodeEditor/CodeViewer Source View
-
-- Editable code editor or read-only code viewer
-- Uses either component based on settings
-- Supports syntax highlighting for multiple programming languages
-
-#### Special View Components
-
-- **MermaidPreview**: Mermaid diagram preview
-- **PlantUmlPreview**: PlantUML diagram preview
-- **SvgPreview**: SVG image preview
-- **GraphvizPreview**: Graphviz diagram preview
-
-All special view components share a common architecture for consistent user experience and functionality. For detailed information about these components and their implementation, see [Image Preview Components Documentation](./image-preview.md).
-
-#### StatusBar
-
-- Displays Python code execution results
-- Can show both text and image results
-
-## Tool System
-
-CodeBlockView uses a hook-based tool system:
-
-```mermaid
-graph TD
-    A[CodeBlockView] --> B[useCopyTool]
-    A --> C[useDownloadTool]
-    A --> D[useViewSourceTool]
-    A --> E[useSplitViewTool]
-    A --> F[useRunTool]
-    A --> G[useExpandTool]
-    A --> H[useWrapTool]
-    A --> I[useSaveTool]
-
-    B --> J[ToolManager]
-    C --> J
-    D --> J
-    E --> J
-    F --> J
-    G --> J
-    H --> J
-    I --> J
-
-    J --> K[CodeToolbar]
-```
-
-Each tool hook is responsible for registering specific function tool buttons to the tool manager, which then passes these tools to the CodeToolbar component for rendering.
-
-### Tool Types
-
-- **core**: Core tools, always displayed in the toolbar
-- **quick**: Quick tools, displayed in a dropdown menu when there are more than one
-
-### Tool List
-
-1. **Copy**: Copy code or image
-2. **Download**: Download code or image
-3. **View Source**: Switch between special view and source code view
-4. **Split View**: Toggle split view mode
-5. **Run**: Run Python code
-6. **Expand/Collapse**: Control code block expansion/collapse
-7. **Wrap**: Control automatic line wrapping
-8. **Save**: Save edited code
-
-## State Management
-
-CodeBlockView manages the following states through React hooks:
-
-1. **viewMode**: Current view mode ('source' | 'special' | 'split')
-2. **isRunning**: Python code execution status
-3. **executionResult**: Python code execution result
-4. **tools**: Toolbar tool list
-5. **expandOverride/unwrapOverride**: User override settings for expand/wrap
-6. **sourceScrollHeight**: Source code view scroll height
-
-## Interaction Flow
-
-```mermaid
-sequenceDiagram
-    participant U as User
-    participant CB as CodeBlockView
-    participant CT as CodeToolbar
-    participant SV as SpecialView
-    participant SE as SourceEditor
-
-    U->>CB: View code block
-    CB->>CB: Initialize state
-    CB->>CT: Register tools
-    CB->>SV: Render special view (if applicable)
-    CB->>SE: Render source view
-    U->>CT: Click tool button
-    CT->>CB: Trigger tool callback
-    CB->>CB: Update state
-    CB->>CT: Re-register tools (if needed)
-```
-
-## Special Handling
-
-### HTML Code Blocks
-
-HTML code blocks are specially handled using the HtmlArtifactsCard component.
-
-### Python Code Execution
-
-Supports executing Python code and displaying results using Pyodide to run Python code in the browser.

docs/en/references/components/image-preview.md

@@ -1,195 +0,0 @@
-# Image Preview Components
-
-## Overview
-
-Image Preview Components are a set of specialized components in Cherry Studio for rendering and displaying various diagram and image formats. They provide a consistent user experience across different preview types with shared functionality for loading states, error handling, and interactive controls.
-
-## Supported Formats
-
-- **Mermaid**: Interactive diagrams and flowcharts
-- **PlantUML**: UML diagrams and system architecture
-- **SVG**: Scalable vector graphics
-- **Graphviz/DOT**: Graph visualization and network diagrams
-
-## Architecture
-
-```mermaid
-graph TD
-    A[MermaidPreview] --> D[ImagePreviewLayout]
-    B[PlantUmlPreview] --> D
-    C[SvgPreview] --> D
-    E[GraphvizPreview] --> D
-
-    D --> F[ImageToolbar]
-    D --> G[useDebouncedRender]
-
-    F --> H[Pan Controls]
-    F --> I[Zoom Controls]
-    F --> J[Reset Function]
-    F --> K[Dialog Control]
-
-    G --> L[Debounced Rendering]
-    G --> M[Error Handling]
-    G --> N[Loading State]
-    G --> O[Dependency Management]
-```
-
-## Core Components
-
-### ImagePreviewLayout
-
-A common layout wrapper that provides the foundation for all image preview components.
-
-**Features:**
-
-- **Loading State Management**: Shows loading spinner during rendering
-- **Error Display**: Displays error messages when rendering fails
-- **Toolbar Integration**: Conditionally renders ImageToolbar when enabled
-- **Container Management**: Wraps preview content with consistent styling
-- **Responsive Design**: Adapts to different container sizes
-
-**Props:**
-
-- `children`: The preview content to be displayed
-- `loading`: Boolean indicating if content is being rendered
-- `error`: Error message to display if rendering fails
-- `enableToolbar`: Whether to show the interactive toolbar
-- `imageRef`: Reference to the container element for image manipulation
-
-### ImageToolbar
-
-Interactive toolbar component providing image manipulation controls.
-
-**Features:**
-
-- **Pan Controls**: 4-directional pan buttons (up, down, left, right)
-- **Zoom Controls**: Zoom in/out functionality with configurable increments
-- **Reset Function**: Restore original pan and zoom state
-- **Dialog Control**: Open preview in expanded dialog view
-- **Accessible Design**: Full keyboard navigation and screen reader support
-
-**Layout:**
-
-- 3x3 grid layout positioned at bottom-right of preview
-- Responsive button sizing
-- Tooltip support for all controls
-
-### useDebouncedRender Hook
-
-A specialized React hook for managing preview rendering with performance optimizations.
-
-**Features:**
-
-- **Debounced Rendering**: Prevents excessive re-renders during rapid content changes (default 300ms delay)
-- **Automatic Dependency Management**: Handles dependencies for render and condition functions
-- **Error Handling**: Catches and manages rendering errors with detailed error messages
-- **Loading State**: Tracks rendering progress with automatic state updates
-- **Conditional Rendering**: Supports pre-render condition checks
-- **Manual Controls**: Provides trigger, cancel, and state management functions
-
-**API:**
-
-```typescript
-const { containerRef, error, isLoading, triggerRender, cancelRender, clearError, setLoading } = useDebouncedRender(
-  value,
-  renderFunction,
-  options
-)
-```
-
-**Options:**
-
-- `debounceDelay`: Customize debounce timing
-- `shouldRender`: Function for conditional rendering logic
-
-## Component Implementations
-
-### MermaidPreview
-
-Renders Mermaid diagrams with special handling for visibility detection.
-
-**Special Features:**
-
-- Syntax validation before rendering
-- Visibility detection to handle collapsed containers
-- SVG coordinate fixing for edge cases
-- Integration with mermaid.js library
-
-### PlantUmlPreview
-
-Renders PlantUML diagrams using the online PlantUML server.
-
-**Special Features:**
-
-- Network error handling and retry logic
-- Diagram encoding using deflate compression
-- Support for light/dark themes
-- Server status monitoring
-
-### SvgPreview
-
-Renders SVG content using Shadow DOM for isolation.
-
-**Special Features:**
-
-- Shadow DOM rendering for style isolation
-- Direct SVG content injection
-- Minimal processing overhead
-- Cross-browser compatibility
-
-### GraphvizPreview
-
-Renders Graphviz/DOT diagrams using the viz.js library.
-
-**Special Features:**
-
-- Client-side rendering with viz.js
-- Lazy loading of viz.js library
-- SVG element generation
-- Memory-efficient processing
-
-## Shared Functionality
-
-### Error Handling
-
-All preview components provide consistent error handling:
-
-- Network errors (connection failures)
-- Syntax errors (invalid diagram code)
-- Server errors (external service failures)
-- Rendering errors (library failures)
-
-### Loading States
-
-Standardized loading indicators across all components:
-
-- Spinner animation during processing
-- Progress feedback for long operations
-- Smooth transitions between states
-
-### Interactive Controls
-
-Common interaction patterns:
-
-- Pan and zoom functionality
-- Reset to original view
-- Full-screen dialog mode
-- Keyboard accessibility
-
-### Performance Optimizations
-
-- Debounced rendering to prevent excessive updates
-- Lazy loading of heavy libraries
-- Memory management for large diagrams
-- Efficient re-rendering strategies
-
-## Integration with CodeBlockView
-
-Image Preview Components integrate seamlessly with CodeBlockView:
-
-- Automatic format detection based on language tags
-- Consistent toolbar integration
-- Shared state management
-- Responsive layout adaptation
-
-For more information about the overall CodeBlockView architecture, see [CodeBlockView Documentation](./code-block-view.md).

docs/technical/Message.md

@@ -0,0 +1,3 @@
+# 消息的生命周期
+
+![image](./message-lifecycle.png)

docs/technical/how-to-use-messageBlock.md

@@ -0,0 +1,127 @@
+# messageBlock.ts 使用指南
+
+该文件定义了用于管理应用程序中所有 `MessageBlock` 实体的 Redux Slice。它使用 Redux Toolkit 的 `createSlice` 和 `createEntityAdapter` 来高效地处理规范化的状态，并提供了一系列 actions 和 selectors 用于与消息块数据交互。
+
+## 核心目标
+
+- **状态管理**: 集中管理所有 `MessageBlock` 的状态。`MessageBlock` 代表消息中的不同内容单元（如文本、代码、图片、引用等）。
+- **规范化**: 使用 `createEntityAdapter` 将 `MessageBlock` 数据存储在规范化的结构中（`{ ids: [], entities: {} }`），这有助于提高性能和简化更新逻辑。
+- **可预测性**: 提供明确的 actions 来修改状态，并通过 selectors 安全地访问状态。
+
+## 关键概念
+
+- **Slice (`createSlice`)**: Redux Toolkit 的核心 API，用于创建包含 reducer 逻辑、action creators 和初始状态的 Redux 模块。
+- **Entity Adapter (`createEntityAdapter`)**: Redux Toolkit 提供的工具，用于简化对规范化数据的 CRUD（创建、读取、更新、删除）操作。它会自动生成 reducer 函数和 selectors。
+- **Selectors**: 用于从 Redux store 中派生和计算数据的函数。Selectors 可以被记忆化（memoized），以提高性能。
+
+## State 结构
+
+`messageBlocks` slice 的状态结构由 `createEntityAdapter` 定义，大致如下：
+
+```typescript
+{
+  ids: string[]; // 存储所有 MessageBlock ID 的有序列表
+  entities: { [id: string]: MessageBlock }; // 按 ID 存储 MessageBlock 对象的字典
+  loadingState: 'idle' | 'loading' | 'succeeded' | 'failed'; // (可选) 其他状态，如加载状态
+  error: string | null; // (可选) 错误信息
+}
+```
+
+## Actions
+
+该 slice 导出以下 actions (由 `createSlice` 和 `createEntityAdapter` 自动生成或自定义)：
+
+- **`upsertOneBlock(payload: MessageBlock)`**:
+
+  - 添加一个新的 `MessageBlock` 或更新一个已存在的 `MessageBlock`。如果 payload 中的 `id` 已存在，则执行更新；否则执行插入。
+
+- **`upsertManyBlocks(payload: MessageBlock[])`**:
+
+  - 添加或更新多个 `MessageBlock`。常用于批量加载数据（例如，加载一个 Topic 的所有消息块）。
+
+- **`removeOneBlock(payload: string)`**:
+
+  - 根据提供的 `id` (payload) 移除单个 `MessageBlock`。
+
+- **`removeManyBlocks(payload: string[])`**:
+
+  - 根据提供的 `id` 数组 (payload) 移除多个 `MessageBlock`。常用于删除消息或清空 Topic 时清理相关的块。
+
+- **`removeAllBlocks()`**:
+
+  - 移除 state 中的所有 `MessageBlock` 实体。
+
+- **`updateOneBlock(payload: { id: string; changes: Partial<MessageBlock> })`**:
+
+  - 更新一个已存在的 `MessageBlock`。`payload` 需要包含块的 `id` 和一个包含要更改的字段的 `changes` 对象。
+
+- **`setMessageBlocksLoading(payload: 'idle' | 'loading')`**:
+
+  - (自定义) 设置 `loadingState` 属性。
+
+- **`setMessageBlocksError(payload: string)`**:
+  - (自定义) 设置 `loadingState` 为 `'failed'` 并记录错误信息。
+
+**使用示例 (在 Thunk 或其他 Dispatch 的地方):**
+
+```typescript
+import { upsertOneBlock, removeManyBlocks, updateOneBlock } from './messageBlock'
+import store from './store' // 假设这是你的 Redux store 实例
+
+// 添加或更新一个块
+const newBlock: MessageBlock = {
+  /* ... block data ... */
+}
+store.dispatch(upsertOneBlock(newBlock))
+
+// 更新一个块的内容
+store.dispatch(updateOneBlock({ id: blockId, changes: { content: 'New content' } }))
+
+// 删除多个块
+const blockIdsToRemove = ['id1', 'id2']
+store.dispatch(removeManyBlocks(blockIdsToRemove))
+```
+
+## Selectors
+
+该 slice 导出由 `createEntityAdapter` 生成的基础 selectors，并通过 `messageBlocksSelectors` 对象访问：
+
+- **`messageBlocksSelectors.selectIds(state: RootState): string[]`**: 返回包含所有块 ID 的数组。
+- **`messageBlocksSelectors.selectEntities(state: RootState): { [id: string]: MessageBlock }`**: 返回块 ID 到块对象的映射字典。
+- **`messageBlocksSelectors.selectAll(state: RootState): MessageBlock[]`**: 返回包含所有块对象的数组。
+- **`messageBlocksSelectors.selectTotal(state: RootState): number`**: 返回块的总数。
+- **`messageBlocksSelectors.selectById(state: RootState, id: string): MessageBlock | undefined`**: 根据 ID 返回单个块对象，如果找不到则返回 `undefined`。
+
+**此外，还提供了一个自定义的、记忆化的 selector：**
+
+- **`selectFormattedCitationsByBlockId(state: RootState, blockId: string | undefined): Citation[]`**:
+  - 接收一个 `blockId`。
+  - 如果该 ID 对应的块是 `CITATION` 类型，则提取并格式化其包含的引用信息（来自网页搜索、知识库等），进行去重和重新编号，最后返回一个 `Citation[]` 数组，用于在 UI 中显示。
+  - 如果块不存在或类型不匹配，返回空数组 `[]`。
+  - 这个 selector 封装了处理不同引用来源（Gemini, OpenAI, OpenRouter, Zhipu 等）的复杂逻辑。
+
+**使用示例 (在 React 组件或 `useSelector` 中):**
+
+```typescript
+import { useSelector } from 'react-redux'
+import { messageBlocksSelectors, selectFormattedCitationsByBlockId } from './messageBlock'
+import type { RootState } from './store'
+
+// 获取所有块
+const allBlocks = useSelector(messageBlocksSelectors.selectAll)
+
+// 获取特定 ID 的块
+const specificBlock = useSelector((state: RootState) => messageBlocksSelectors.selectById(state, someBlockId))
+
+// 获取特定引用块格式化后的引用列表
+const formattedCitations = useSelector((state: RootState) => selectFormattedCitationsByBlockId(state, citationBlockId))
+
+// 在组件中使用引用数据
+// {formattedCitations.map(citation => ...)}
+```
+
+## 集成
+
+`messageBlock.ts` slice 通常与 `messageThunk.ts` 中的 Thunks 紧密协作。Thunks 负责处理异步逻辑（如 API 调用、数据库操作），并在需要时 dispatch `messageBlock` slice 的 actions 来更新状态。例如，当 `messageThunk` 接收到流式响应时，它会 dispatch `upsertOneBlock` 或 `updateOneBlock` 来实时更新对应的 `MessageBlock`。同样，删除消息的 Thunk 会 dispatch `removeManyBlocks`。
+
+理解 `messageBlock.ts` 的职责是管理**状态本身**，而 `messageThunk.ts` 负责**触发状态变更**的异步流程，这对于维护清晰的应用架构至关重要。

docs/technical/how-to-use-messageThunk.md

@@ -0,0 +1,105 @@
+# messageThunk.ts 使用指南
+
+该文件包含用于管理应用程序中消息流、处理助手交互以及同步 Redux 状态与 IndexedDB 数据库的核心 Thunk Action Creators。主要围绕 `Message` 和 `MessageBlock` 对象进行操作。
+
+## 核心功能
+
+1.  **发送/接收消息**: 处理用户消息的发送，触发助手响应，并流式处理返回的数据，将其解析为不同的 `MessageBlock`。
+2.  **状态管理**: 确保 Redux store 中的消息和消息块状态与 IndexedDB 中的持久化数据保持一致。
+3.  **消息操作**: 提供删除、重发、重新生成、编辑后重发、追加响应、克隆等消息生命周期管理功能。
+4.  **Block 处理**: 动态创建、更新和保存各种类型的 `MessageBlock`（文本、思考过程、工具调用、引用、图片、错误、翻译等）。
+
+## 主要 Thunks
+
+以下是一些关键的 Thunk 函数及其用途：
+
+1.  **`sendMessage(userMessage, userMessageBlocks, assistant, topicId)`**
+
+    - **用途**: 发送一条新的用户消息。
+    - **流程**:
+      - 保存用户消息 (`userMessage`) 及其块 (`userMessageBlocks`) 到 Redux 和 DB。
+      - 检查 `@mentions` 以确定是单模型响应还是多模型响应。
+      - 创建助手消息(们)的存根 (Stub)。
+      - 将存根添加到 Redux 和 DB。
+      - 将核心处理逻辑 `fetchAndProcessAssistantResponseImpl` 添加到该 `topicId` 的队列中以获取实际响应。
+    - **Block 相关**: 主要处理用户消息的初始 `MessageBlock` 保存。
+
+2.  **`fetchAndProcessAssistantResponseImpl(dispatch, getState, topicId, assistant, assistantMessage)`**
+
+    - **用途**: (内部函数) 获取并处理单个助手响应的核心逻辑，被 `sendMessage`, `resend...`, `regenerate...`, `append...` 等调用。
+    - **流程**:
+      - 设置 Topic 加载状态。
+      - 准备上下文消息。
+      - 调用 `fetchChatCompletion` API 服务。
+      - 使用 `createStreamProcessor` 处理流式响应。
+      - 通过各种回调 (`onTextChunk`, `onThinkingChunk`, `onToolCallComplete`, `onImageGenerated`, `onError`, `onComplete` 等) 处理不同类型的事件。
+    - **Block 相关**:
+      - 根据流事件创建初始 `UNKNOWN` 块。
+      - 实时创建和更新 `MAIN_TEXT` 和 `THINKING` 块，使用 `throttledBlockUpdate` 和 `throttledBlockDbUpdate` 进行节流更新。
+      - 创建 `TOOL`, `CITATION`, `IMAGE`, `ERROR` 等类型的块。
+      - 在事件完成时（如 `onTextComplete`, `onToolCallComplete`）将块状态标记为 `SUCCESS` 或 `ERROR`，并使用 `saveUpdatedBlockToDB` 保存最终状态。
+      - 使用 `handleBlockTransition` 管理非流式块（如 `TOOL`, `CITATION`）的添加和状态更新。
+
+3.  **`loadTopicMessagesThunk(topicId, forceReload)`**
+
+    - **用途**: 从数据库加载指定主题的所有消息及其关联的 `MessageBlock`。
+    - **流程**:
+      - 从 DB 获取 `Topic` 及其 `messages` 列表。
+      - 根据消息 ID 列表从 DB 获取所有相关的 `MessageBlock`。
+      - 使用 `upsertManyBlocks` 将块更新到 Redux。
+      - 将消息更新到 Redux。
+    - **Block 相关**: 负责将持久化的 `MessageBlock` 加载到 Redux 状态。
+
+4.  **删除 Thunks**
+
+    - `deleteSingleMessageThunk(topicId, messageId)`: 删除单个消息及其所有 `MessageBlock`。
+    - `deleteMessageGroupThunk(topicId, askId)`: 删除一个用户消息及其所有相关的助手响应消息和它们的所有 `MessageBlock`。
+    - `clearTopicMessagesThunk(topicId)`: 清空主题下的所有消息及其所有 `MessageBlock`。
+    - **Block 相关**: 从 Redux 和 DB 中移除指定的 `MessageBlock`。
+
+5.  **重发/重新生成 Thunks**
+
+    - `resendMessageThunk(topicId, userMessageToResend, assistant)`: 重发用户消息。会重置（清空 Block 并标记为 PENDING）所有与该用户消息关联的助手响应，然后重新请求生成。
+    - `resendUserMessageWithEditThunk(topicId, originalMessage, mainTextBlockId, editedContent, assistant)`: 用户编辑消息内容后重发。先更新用户消息的 `MAIN_TEXT` 块内容，然后调用 `resendMessageThunk`。
+    - `regenerateAssistantResponseThunk(topicId, assistantMessageToRegenerate, assistant)`: 重新生成单个助手响应。重置该助手消息（清空 Block 并标记为 PENDING），然后重新请求生成。
+    - **Block 相关**: 删除旧的 `MessageBlock`，并在重新生成过程中创建新的 `MessageBlock`。
+
+6.  **`appendAssistantResponseThunk(topicId, existingAssistantMessageId, newModel, assistant)`**
+
+    - **用途**: 在已有的对话上下文中，针对同一个用户问题，使用新选择的模型追加一个新的助手响应。
+    - **流程**:
+      - 找到现有助手消息以获取原始 `askId`。
+      - 创建使用 `newModel` 的新助手消息存根（使用相同的 `askId`）。
+      - 添加新存根到 Redux 和 DB。
+      - 将 `fetchAndProcessAssistantResponseImpl` 添加到队列以生成新响应。
+    - **Block 相关**: 为新的助手响应创建全新的 `MessageBlock`。
+
+7.  **`cloneMessagesToNewTopicThunk(sourceTopicId, branchPointIndex, newTopic)`**
+
+    - **用途**: 将源主题的部分消息（及其 Block）克隆到一个**已存在**的新主题中。
+    - **流程**:
+      - 复制指定索引前的消息。
+      - 为所有克隆的消息和 Block 生成新的 UUID。
+      - 正确映射克隆消息之间的 `askId` 关系。
+      - 复制 `MessageBlock` 内容，更新其 `messageId` 指向新的消息 ID。
+      - 更新文件引用计数（如果 Block 是文件或图片）。
+      - 将克隆的消息和 Block 保存到新主题的 Redux 状态和 DB 中。
+    - **Block 相关**: 创建 `MessageBlock` 的副本，并更新其 ID 和 `messageId`。
+
+8.  **`initiateTranslationThunk(messageId, topicId, targetLanguage, sourceBlockId?, sourceLanguage?)`**
+    - **用途**: 为指定消息启动翻译流程，创建一个初始的 `TRANSLATION` 类型的 `MessageBlock`。
+    - **流程**:
+      - 创建一个状态为 `STREAMING` 的 `TranslationMessageBlock`。
+      - 将其添加到 Redux 和 DB。
+      - 更新原消息的 `blocks` 列表以包含新的翻译块 ID。
+    - **Block 相关**: 创建并保存一个占位的 `TranslationMessageBlock`。实际翻译内容的获取和填充需要后续步骤。
+
+## 内部机制和注意事项
+
+- **数据库交互**: 通过 `saveMessageAndBlocksToDB`, `updateExistingMessageAndBlocksInDB`, `saveUpdatesToDB`, `saveUpdatedBlockToDB`, `throttledBlockDbUpdate` 等辅助函数与 IndexedDB (`db`) 交互，确保数据持久化。
+- **状态同步**: Thunks 负责协调 Redux Store 和 IndexedDB 之间的数据一致性。
+- **队列 (`getTopicQueue`)**: 使用 `AsyncQueue` 确保对同一主题的操作（尤其是 API 请求）按顺序执行，避免竞态条件。
+- **节流 (`throttle`)**: 对流式响应中频繁的 Block 更新（文本、思考）使用 `lodash.throttle` 优化性能，减少 Redux dispatch 和 DB 写入次数。
+- **错误处理**: `fetchAndProcessAssistantResponseImpl` 内的回调函数（特别是 `onError`）处理流处理和 API 调用中可能出现的错误，并创建 `ERROR` 类型的 `MessageBlock`。
+
+开发者在使用这些 Thunks 时，通常需要提供 `dispatch`, `getState` (由 Redux Thunk 中间件注入)，以及如 `topicId`, `assistant` 配置对象, 相关的 `Message` 或 `MessageBlock` 对象/ID 等参数。理解每个 Thunk 的职责和它如何影响消息及块的状态至关重要。

docs/technical/how-to-use-useMessageOperations.md

@@ -0,0 +1,156 @@
+# useMessageOperations.ts 使用指南
+
+该文件定义了一个名为 `useMessageOperations` 的自定义 React Hook。这个 Hook 的主要目的是为 React 组件提供一个便捷的接口，用于执行与特定主题（Topic）相关的各种消息操作。它封装了调用 Redux Thunks (`messageThunk.ts`) 和 Actions (`newMessage.ts`, `messageBlock.ts`) 的逻辑，简化了组件与消息数据交互的代码。
+
+## 核心目标
+
+- **封装**: 将复杂的消息操作逻辑（如删除、重发、重新生成、编辑、翻译等）封装在易于使用的函数中。
+- **简化**: 让组件可以直接调用这些操作函数，而无需直接与 Redux `dispatch` 或 Thunks 交互。
+- **上下文关联**: 所有操作都与传入的 `topic` 对象相关联，确保操作作用于正确的主题。
+
+## 如何使用
+
+在你的 React 函数组件中，导入并调用 `useMessageOperations` Hook，并传入当前活动的 `Topic` 对象。
+
+```typescript
+import React from 'react';
+import { useMessageOperations } from '@renderer/hooks/useMessageOperations';
+import type { Topic, Message, Assistant, Model } from '@renderer/types';
+
+interface MyComponentProps {
+  currentTopic: Topic;
+  currentAssistant: Assistant;
+}
+
+function MyComponent({ currentTopic, currentAssistant }: MyComponentProps) {
+  const {
+    deleteMessage,
+    resendMessage,
+    regenerateAssistantMessage,
+    appendAssistantResponse,
+    getTranslationUpdater,
+    createTopicBranch,
+    // ... 其他操作函数
+  } = useMessageOperations(currentTopic);
+
+  const handleDelete = (messageId: string) => {
+    deleteMessage(messageId);
+  };
+
+  const handleResend = (message: Message) => {
+    resendMessage(message, currentAssistant);
+  };
+
+  const handleAppend = (existingMsg: Message, newModel: Model) => {
+    appendAssistantResponse(existingMsg, newModel, currentAssistant);
+  }
+
+  // ... 在组件中使用其他操作函数
+
+  return (
+    <div>
+      {/* Component UI */}
+      <button onClick={() => handleDelete('some-message-id')}>Delete Message</button>
+      {/* ... */}
+    </div>
+  );
+}
+```
+
+## 返回值
+
+`useMessageOperations(topic)` Hook 返回一个包含以下函数和值的对象：
+
+- **`deleteMessage(id: string)`**:
+
+  - 删除指定 `id` 的单个消息。
+  - 内部调用 `deleteSingleMessageThunk`。
+
+- **`deleteGroupMessages(askId: string)`**:
+
+  - 删除与指定 `askId` 相关联的一组消息（通常是用户提问及其所有助手回答）。
+  - 内部调用 `deleteMessageGroupThunk`。
+
+- **`editMessage(messageId: string, updates: Partial<Message>)`**:
+
+  - 更新指定 `messageId` 的消息的部分属性。
+  - **注意**: 目前主要用于更新 Redux 状态
+  - 内部调用 `newMessagesActions.updateMessage`。
+
+- **`resendMessage(message: Message, assistant: Assistant)`**:
+
+  - 重新发送指定的用户消息 (`message`)，这将触发其所有关联助手响应的重新生成。
+  - 内部调用 `resendMessageThunk`。
+
+- **`resendUserMessageWithEdit(message: Message, editedContent: string, assistant: Assistant)`**:
+
+  - 在用户消息的主要文本块被编辑后，重新发送该消息。
+  - 会先查找消息的 `MAIN_TEXT` 块 ID，然后调用 `resendUserMessageWithEditThunk`。
+
+- **`clearTopicMessages(_topicId?: string)`**:
+
+  - 清除当前主题（或可选的指定 `_topicId`）下的所有消息。
+  - 内部调用 `clearTopicMessagesThunk`。
+
+- **`createNewContext()`**:
+
+  - 发出一个全局事件 (`EVENT_NAMES.NEW_CONTEXT`)，通常用于通知 UI 清空显示，准备新的上下文。不直接修改 Redux 状态。
+
+- **`displayCount`**:
+
+  - (非操作函数) 从 Redux store 中获取当前的 `displayCount` 值。
+
+- **`pauseMessages()`**:
+
+  - 尝试中止当前主题中正在进行的消息生成（状态为 `processing` 或 `pending`）。
+  - 通过查找相关的 `askId` 并调用 `abortCompletion` 来实现。
+  - 同时会 dispatch `setTopicLoading` action 将加载状态设为 `false`。
+
+- **`resumeMessage(message: Message, assistant: Assistant)`**:
+
+  - 恢复/重新发送一个用户消息。目前实现为直接调用 `resendMessage`。
+
+- **`regenerateAssistantMessage(message: Message, assistant: Assistant)`**:
+
+  - 重新生成指定的**助手**消息 (`message`) 的响应。
+  - 内部调用 `regenerateAssistantResponseThunk`。
+
+- **`appendAssistantResponse(existingAssistantMessage: Message, newModel: Model, assistant: Assistant)`**:
+
+  - 针对 `existingAssistantMessage` 所回复的**同一用户提问**，使用 `newModel` 追加一个新的助手响应。
+  - 内部调用 `appendAssistantResponseThunk`。
+
+- **`getTranslationUpdater(messageId: string, targetLanguage: string, sourceBlockId?: string, sourceLanguage?: string)`**:
+
+  - **用途**: 获取一个用于逐步更新翻译块内容的函数。
+  - **流程**:
+    1.  内部调用 `initiateTranslationThunk` 来创建或获取一个 `TRANSLATION` 类型的 `MessageBlock`，并获取其 `blockId`。
+    2.  返回一个**异步更新函数**。
+  - **返回的更新函数 `(accumulatedText: string, isComplete?: boolean) => void`**:
+    - 接收累积的翻译文本和完成状态。
+    - 调用 `updateOneBlock` 更新 Redux 中的翻译块内容和状态 (`STREAMING` 或 `SUCCESS`)。
+    - 调用 `throttledBlockDbUpdate` 将更新（节流地）保存到数据库。
+  - 如果初始化失败（Thunk 返回 `undefined`），则此函数返回 `null`。
+
+- **`createTopicBranch(sourceTopicId: string, branchPointIndex: number, newTopic: Topic)`**:
+  - 创建一个主题分支，将 `sourceTopicId` 主题中 `branchPointIndex` 索引之前的消息克隆到 `newTopic` 中。
+  - **注意**: `newTopic` 对象必须是调用此函数**之前**已经创建并添加到 Redux 和数据库中的。
+  - 内部调用 `cloneMessagesToNewTopicThunk`。
+
+## 依赖
+
+- **`topic: Topic`**: 必须传入当前操作上下文的主题对象。Hook 返回的操作函数将始终作用于这个主题的 `topic.id`。
+- **Redux `dispatch`**: Hook 内部使用 `useAppDispatch` 获取 `dispatch` 函数来调用 actions 和 thunks。
+
+## 相关 Hooks
+
+在同一文件中还定义了两个辅助 Hook：
+
+- **`useTopicMessages(topic: Topic)`**:
+
+  - 使用 `selectMessagesForTopic` selector 来获取并返回指定主题的消息列表。
+
+- **`useTopicLoading(topic: Topic)`**:
+  - 使用 `selectNewTopicLoading` selector 来获取并返回指定主题的加载状态。
+
+这些 Hook 可以与 `useMessageOperations` 结合使用，方便地在组件中获取消息数据、加载状态，并执行相关操作。

docs/technical/how-to-write-middlewares.md

@@ -80,13 +80,15 @@ import { ChunkType } from '@renderer/types' // 调整路径
 
 export const createSimpleLoggingMiddleware = (): CompletionsMiddleware => {
   return (api: MiddlewareAPI<AiProviderMiddlewareCompletionsContext, [CompletionsParams]>) => {
+    // console.log(`[LoggingMiddleware] Initialized for provider: ${api.getProviderId()}`);
+
     return (next: (context: AiProviderMiddlewareCompletionsContext, params: CompletionsParams) => Promise<any>) => {
       return async (context: AiProviderMiddlewareCompletionsContext, params: CompletionsParams): Promise<void> => {
         const startTime = Date.now()
         // 从 context 中获取 onChunk (它最初来自 params.onChunk)
         const onChunk = context.onChunk
 
-        logger.debug(
+        console.log(
           `[LoggingMiddleware] Request for ${context.methodName} with params:`,
           params.messages?.[params.messages.length - 1]?.content
         )
@@ -102,14 +104,14 @@ export const createSimpleLoggingMiddleware = (): CompletionsMiddleware => {
           // 如果在之前，那么它需要自己处理 rawSdkResponse 或确保下游会处理。
 
           const duration = Date.now() - startTime
-          logger.debug(`[LoggingMiddleware] Request for ${context.methodName} completed in ${duration}ms.`)
+          console.log(`[LoggingMiddleware] Request for ${context.methodName} completed in ${duration}ms.`)
 
           // 假设下游已经通过 onChunk 发送了所有数据。
           // 如果这个中间件是链的末端，并且需要确保 BLOCK_COMPLETE 被发送，
           // 它可能需要更复杂的逻辑来跟踪何时所有数据都已发送。
         } catch (error) {
           const duration = Date.now() - startTime
-          logger.error(`[LoggingMiddleware] Request for ${context.methodName} failed after ${duration}ms:`, error)
+          console.error(`[LoggingMiddleware] Request for ${context.methodName} failed after ${duration}ms:`, error)
 
           // 如果 onChunk 可用，可以尝试发送一个错误块
           if (onChunk) {
@@ -205,7 +207,7 @@ export default middlewareConfig
 
 ### 调试技巧
 
-- 在中间件的关键点使用 `logger.debug` 或调试器来检查 `params`、`context` 的状态以及 `next` 的返回值。
+- 在中间件的关键点使用 `console.log` 或调试器来检查 `params`、`context` 的状态以及 `next` 的返回值。
 - 暂时简化中间件链，只保留你正在调试的中间件和最简单的核心逻辑，以隔离问题。
 - 编写单元测试来独立验证每个中间件的行为。
 

docs/zh/README.md

@@ -1,321 +0,0 @@
-<div align="right" >
-  <details>
-    <summary >🌐 Language</summary>
-    <div>
-      <div align="right">
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=en">English</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=zh-CN">简体中文</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=zh-TW">繁體中文</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=ja">日本語</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=ko">한국어</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=hi">हिन्दी</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=th">ไทย</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=fr">Français</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=de">Deutsch</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=es">Español</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=it">Italiano</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=ru">Русский</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=pt">Português</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=nl">Nederlands</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=pl">Polski</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=ar">العربية</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=fa">فارسی</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=tr">Türkçe</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=vi">Tiếng Việt</a></p>
-        <p><a href="https://openaitx.github.io/view.html?user=CherryHQ&project=cherry-studio&lang=id">Bahasa Indonesia</a></p>
-      </div>
-    </div>
-  </details>
-</div>
-
-<h1 align="center">
-  <a href="https://github.com/CherryHQ/cherry-studio/releases">
-    <img src="https://github.com/CherryHQ/cherry-studio/blob/main/build/icon.png?raw=true" width="150" height="150" alt="banner" /><br>
-  </a>
-</h1>
-<p align="center">
-  <a href="https://github.com/CherryHQ/cherry-studio">English</a> | 中文 | <a href="https://cherry-ai.com">官方网站</a> | <a href="https://docs.cherry-ai.com/cherry-studio-wen-dang/zh-cn">文档</a> | <a href="./guides/development.md">开发</a> | <a href="https://github.com/CherryHQ/cherry-studio/issues">反馈</a><br>
-</p>
-
-<!-- 题头徽章组合 -->
-
-<div align="center">
-
-[![][deepwiki-shield]][deepwiki-link]
-[![][twitter-shield]][twitter-link]
-[![][discord-shield]][discord-link]
-[![][telegram-shield]][telegram-link]
-
-</div>
-
-<div align="center">
-
-[![][github-release-shield]][github-release-link]
-[![][github-contributors-shield]][github-contributors-link]
-[![][license-shield]][license-link]
-[![][commercial-shield]][commercial-link]
-[![][sponsor-shield]][sponsor-link]
-
-</div>
-
-<div align="center">
- <a href="https://hellogithub.com/repository/1605492e1e2a4df3be07abfa4578dd37" target="_blank" style="text-decoration: none"><img src="https://api.hellogithub.com/v1/widgets/recommend.svg?rid=1605492e1e2a4df3be07abfa4578dd37" alt="Featured｜HelloGitHub"  width="220" height="55" /></a>
- <a href="https://trendshift.io/repositories/11772" target="_blank" style="text-decoration: none"><img src="https://trendshift.io/api/badge/repositories/11772" alt="kangfenmao%2Fcherry-studio | Trendshift" width="220" height="55" /></a>
- <a href="https://www.producthunt.com/posts/cherry-studio?embed=true&utm_source=badge-featured&utm_medium=badge&utm_souce=badge-cherry&#0045;studio" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=496640&theme=light" alt="Cherry&#0032;Studio - AI&#0032;Chatbots&#0044;&#0032;AI&#0032;Desktop&#0032;Client | Product Hunt" width="220" height="55" /></a>
-</div>
-
-# 🍒 Cherry Studio
-
-Cherry Studio 是一款支持多个大语言模型（LLM）服务商的桌面客户端，兼容 Windows、Mac 和 Linux 系统。
-
-👏 欢迎加入 [Telegram 群组](https://t.me/CherryStudioAI)｜[Discord](https://discord.gg/wez8HtpxqQ) | [QQ群(575014769)](https://qm.qq.com/q/lo0D4qVZKi)
-
-❤️ 喜欢 Cherry Studio? 点亮小星星 🌟 或 [赞助开发者](./guides/sponsor.md)! ❤️
-
-# 📖 使用教程
-
-https://docs.cherry-ai.com
-
-# 🌠 界面
-
-![](https://github.com/user-attachments/assets/36dddb2c-e0fb-4a5f-9411-91447bab6e18)
-
-![](https://github.com/user-attachments/assets/f549e8a0-2385-40b4-b52b-2039e39f2930)
-
-![](https://github.com/user-attachments/assets/58e0237c-4d36-40de-b428-53051d982026)
-
-# 🌟 主要特性
-
-1. **多样化 LLM 服务支持**：
-
-- ☁️ 支持主流 LLM 云服务：OpenAI、Gemini、Anthropic、硅基流动等
-- 🔗 集成流行 AI Web 服务：Claude、Perplexity、Poe、腾讯元宝、知乎直答等
-- 💻 支持 Ollama、LM Studio 本地模型部署
-
-2. **智能助手与对话**：
-
-- 📚 内置 300+ 预配置 AI 助手
-- 🤖 支持自定义创建专属助手
-- 💬 多模型同时对话，获得多样化观点
-
-3. **文档与数据处理**：
-
-- 📄 支持文本、图片、Office、PDF 等多种格式
-- ☁️ WebDAV 文件管理与数据备份
-- 📊 Mermaid 图表可视化
-- 💻 代码高亮显示
-
-4. **实用工具集成**：
-
-- 🔍 全局搜索功能
-- 📝 话题管理系统
-- 🔤 AI 驱动的翻译功能
-- 🎯 拖拽排序
-- 🔌 小程序支持
-- ⚙️ MCP(模型上下文协议) 服务
-
-5. **优质使用体验**：
-
-- 🖥️ Windows、Mac、Linux 跨平台支持
-- 📦 开箱即用，无需配置环境
-- 🎨 支持明暗主题与透明窗口
-- 📝 完整的 Markdown 渲染
-- 🤲 便捷的内容分享功能
-
-# 📝 开发计划
-
-我们正在积极开发以下功能和改进：
-
-1. 🎯 **核心功能**
-
-- 选择助手 - 智能内容选择增强
-- 深度研究 - 高级研究能力
-- 全局记忆 - 全局上下文感知
-- 文档预处理 - 改进文档处理能力
-- MCP 市场 - 模型上下文协议生态系统
-
-2. 🗂 **知识管理**
-
-- 笔记与收藏功能
-- 动态画布可视化
-- OCR 光学字符识别
-- TTS 文本转语音支持
-
-3. 📱 **平台支持**
-
-- 鸿蒙版本 (PC)
-- Android 应用（第一期）
-- iOS 应用（第一期）
-- 多窗口支持
-- 窗口置顶功能
-
-4. 🔌 **高级特性**
-
-- 插件系统
-- ASR 语音识别
-- 助手与话题交互重构
-
-在我们的[项目面板](https://github.com/orgs/CherryHQ/projects/7)上跟踪进展并参与贡献。
-
-想要影响开发计划？欢迎加入我们的 [GitHub 讨论区](https://github.com/CherryHQ/cherry-studio/discussions) 分享您的想法和反馈！
-
-# 🌈 主题
-
-- 主题库：https://cherrycss.com
-- Aero 主题：https://github.com/hakadao/CherryStudio-Aero
-- PaperMaterial 主题：https://github.com/rainoffallingstar/CherryStudio-PaperMaterial
-- 仿 Claude 主题：https://github.com/bjl101501/CherryStudio-Claudestyle-dynamic
-- 霓虹枫叶主题：https://github.com/BoningtonChen/CherryStudio_themes
-
-欢迎 PR 更多主题
-
-# 🤝 贡献
-
-我们欢迎对 Cherry Studio 的贡献！您可以通过以下方式贡献：
-
-1. **贡献代码**：开发新功能或优化现有代码
-2. **修复错误**：提交您发现的错误修复
-3. **维护问题**：帮助管理 GitHub 问题
-4. **产品设计**：参与设计讨论
-5. **撰写文档**：改进用户手册和指南
-6. **社区参与**：加入讨论并帮助用户
-7. **推广使用**：宣传 Cherry Studio
-
-参考[分支策略](./guides/branching-strategy.md)了解贡献指南
-
-## 入门
-
-1. **Fork 仓库**：Fork 并克隆到您的本地机器
-2. **创建分支**：为您的更改创建分支
-3. **提交更改**：提交并推送您的更改
-4. **打开 Pull Request**：描述您的更改和原因
-
-有关更详细的指南，请参阅我们的 [贡献指南](./guides/contributing.md)
-
-感谢您的支持和贡献！
-
-# 🔧 开发者共创计划
-
-我们正在启动 Cherry Studio 开发者共创计划，旨在为开源生态系统构建一个健康、正向反馈的循环。我们相信，优秀的软件是通过协作构建的，每一个合并的拉取请求都为项目注入新的生命力。
-
-我们诚挚地邀请您加入我们的贡献者队伍，与我们一起塑造 Cherry Studio 的未来。
-
-## 贡献者奖励计划
-
-为了回馈我们的核心贡献者并创造良性循环，我们建立了以下长期激励计划。
-
-**该计划的首个跟踪周期将是 2025 年第三季度（7月、8月、9月）。此周期的奖励将在 10月1日 发放。**
-
-在任何跟踪周期内（例如，首个周期的 7月1日 至 9月30日），任何为 Cherry Studio 在 GitHub 上的开源项目贡献超过 **30 个有意义提交** 的开发者都有资格获得以下福利：
-
-- **Cursor 订阅赞助**：获得 **70 美元** 的 [Cursor](https://cursor.sh/) 订阅积分或报销，让 AI 成为您最高效的编码伙伴。
-- **无限模型访问**：获得 **DeepSeek** 和 **Qwen** 模型的 **无限次** API 调用。
-- **前沿技术访问**：享受偶尔的特殊福利，包括 **Claude**、**Gemini** 和 **OpenAI** 等模型的 API 访问权限，让您始终站在技术前沿。
-
-## 共同成长与未来规划
-
-活跃的社区是任何可持续开源项目背后的推动力。随着 Cherry Studio 的发展，我们的奖励计划也将随之发展。我们致力于持续将我们的福利与行业内最优秀的工具和资源保持一致。这确保我们的核心贡献者获得有意义的支持，创造一个开发者、社区和项目共同成长的正向循环。
-
-**展望未来，该项目还将采取越来越开放的态度来回馈整个开源社区。**
-
-## 如何开始？
-
-我们期待您的第一个拉取请求！
-
-您可以从探索我们的仓库开始，选择一个 `good first issue`，或者提出您自己的改进建议。每一个提交都是开源精神的体现。
-
-感谢您的关注和贡献。
-
-让我们一起建设。
-
-# 🏢 企业版
-
-在社区版的基础上，我们自豪地推出 **Cherry Studio 企业版**——一个为现代团队和企业设计的私有部署 AI 生产力与管理平台。
-
-企业版通过集中管理 AI 资源、知识和数据，解决了团队协作中的核心挑战。它赋能组织提升效率、促进创新并确保合规，同时在安全环境中保持对数据的 100% 控制。
-
-## 核心优势
-
-- **统一模型管理**：集中整合和管理各种基于云的大语言模型（如 OpenAI、Anthropic、Google Gemini）和本地部署的私有模型。员工可以开箱即用，无需单独配置。
-- **企业级知识库**：构建、管理和分享全团队的知识库。确保知识得到保留且一致，使团队成员能够基于统一准确的信息与 AI 交互。
-- **细粒度访问控制**：通过统一的管理后台轻松管理员工账户，并为不同模型、知识库和功能分配基于角色的权限。
-- **完全私有部署**：在您的本地服务器或私有云上部署整个后端服务，确保您的数据 100% 私有且在您的控制之下，满足最严格的安全和合规标准。
-- **可靠的后端服务**：提供稳定的 API 服务、企业级数据备份和恢复机制，确保业务连续性。
-
-## ✨ 在线演示
-
-> 🚧 **公开测试版通知**
->
-> 企业版目前处于早期公开测试阶段，我们正在积极迭代和优化其功能。我们知道它可能还不够完全稳定。如果您在试用过程中遇到任何问题或有宝贵建议，我们非常感谢您能通过邮件联系我们提供反馈。
-
-**🔗 [Cherry Studio 企业版](https://www.cherry-ai.com/enterprise)**
-
-## 版本对比
-
-| 功能         | 社区版                  | 企业版                                                                                         |
-| :----------- | :---------------------- | :--------------------------------------------------------------------------------------------- |
-| **开源**     | ✅ 是                   | ⭕️ 部分开源，对客户开放                                                                        |
-| **成本**     | 个人使用免费 / 商业授权 | 买断 / 订阅费用                                                                                |
-| **管理后台** | —                       | ● 集中化**模型**访问<br>● **员工**管理<br>● 共享**知识库**<br>● **访问**控制<br>● **数据**备份 |
-| **服务器**   | —                       | ✅ 专用私有部署                                                                                |
-
-## 获取企业版
-
-我们相信企业版将成为您团队的 AI 生产力引擎。如果您对 Cherry Studio 企业版感兴趣，希望了解更多信息、请求报价或安排演示，请联系我们。
-
-- **商业咨询与购买**：
-  **📧 [bd@cherry-ai.com](mailto:bd@cherry-ai.com)**
-
-# 🔗 相关项目
-
-- [one-api](https://github.com/songquanpeng/one-api)：LLM API 管理及分发系统，支持 OpenAI、Azure、Anthropic 等主流模型，统一 API 接口，可用于密钥管理与二次分发。
-
-- [ublacklist](https://github.com/iorate/ublacklist)：屏蔽特定网站在 Google 搜索结果中显示
-
-# 🚀 贡献者
-
-<a href="https://github.com/CherryHQ/cherry-studio/graphs/contributors">
-  <img src="https://contrib.rocks/image?repo=CherryHQ/cherry-studio" />
-</a>
-<br /><br />
-
-# 📊 GitHub 统计
-
-![Stats](https://repobeats.axiom.co/api/embed/a693f2e5f773eed620f70031e974552156c7f397.svg 'Repobeats analytics image')
-
-# ⭐️ Star 记录
-
-<a href="https://www.star-history.com/#CherryHQ/cherry-studio&Date">
- <picture>
-   <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=CherryHQ/cherry-studio&type=Date&theme=dark" />
-   <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=CherryHQ/cherry-studio&type=Date" />
-   <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=CherryHQ/cherry-studio&type=Date" />
- </picture>
-</a>
-
-<!-- Links & Images -->
-
-[deepwiki-shield]: https://img.shields.io/badge/Deepwiki-CherryHQ-0088CC
-[deepwiki-link]: https://deepwiki.com/CherryHQ/cherry-studio
-[twitter-shield]: https://img.shields.io/badge/Twitter-CherryStudioApp-0088CC?logo=x
-[twitter-link]: https://twitter.com/CherryStudioHQ
-[discord-shield]: https://img.shields.io/badge/Discord-@CherryStudio-0088CC?logo=discord
-[discord-link]: https://discord.gg/wez8HtpxqQ
-[telegram-shield]: https://img.shields.io/badge/Telegram-@CherryStudioAI-0088CC?logo=telegram
-[telegram-link]: https://t.me/CherryStudioAI
-
-<!-- 项目统计徽章 -->
-
-[github-release-shield]: https://img.shields.io/github/v/release/CherryHQ/cherry-studio
-[github-release-link]: https://github.com/CherryHQ/cherry-studio/releases
-[github-contributors-shield]: https://img.shields.io/github/contributors/CherryHQ/cherry-studio
-[github-contributors-link]: https://github.com/CherryHQ/cherry-studio/graphs/contributors
-
-<!-- 许可和赞助徽章 -->
-
-[license-shield]: https://img.shields.io/badge/License-AGPLv3-important.svg?logo=gnu
-[license-link]: https://www.gnu.org/licenses/agpl-3.0
-[commercial-shield]: https://img.shields.io/badge/商用授权-联系-white.svg?logoColor=white&logo=telegram&color=blue
-[commercial-link]: mailto:license@cherry-ai.com?subject=商业授权咨询
-[sponsor-shield]: https://img.shields.io/badge/赞助支持-FF6699.svg?logo=githubsponsors&logoColor=white
-[sponsor-link]: https://github.com/CherryHQ/cherry-studio/blob/main/docs/sponsor.md

docs/zh/guides/i18n.md

@@ -1,171 +0,0 @@
-# 如何优雅地做好 i18n
-
-## 使用i18n ally插件提升开发体验
-
-i18n ally是一个强大的VSCode插件，它能在开发阶段提供实时反馈，帮助开发者更早发现文案缺失和错译问题。
-
-项目中已经配置好了插件设置，直接安装即可。
-
-### 开发时优势
-
-- **实时预览**：翻译文案会直接显示在编辑器中
-- **错误检测**：自动追踪标记出缺失的翻译或未使用的key
-- **快速跳转**：可通过key直接跳转到定义处（Ctrl/Cmd + click)
-- **自动补全**：输入i18n key时提供自动补全建议
-
-### 效果展示
-
-![demo-1](../../assets/images/i18n/demo-1.png)
-
-![demo-2](../../assets/images/i18n/demo-2.png)
-
-![demo-3](../../assets/images/i18n/demo-3.png)
-
-## i18n 约定
-
-### **绝对避免使用flat格式**
-
-绝对避免使用flat格式，如`"add.button.tip": "添加"`。应采用清晰的嵌套结构：
-
-```json
-// 错误示例 - flat结构
-{
-  "add.button.tip": "添加",
-  "delete.button.tip": "删除"
-}
-
-// 正确示例 - 嵌套结构
-{
-  "add": {
-    "button": {
-      "tip": "添加"
-    }
-  },
-  "delete": {
-    "button": {
-      "tip": "删除"
-    }
-  }
-}
-```
-
-#### 为什么要使用嵌套结构
-
-1. **自然分组**：通过对象结构天然能将相关上下文的文案分到一个组别中
-2. **插件要求**：i18n ally 插件需要嵌套或flat格式其一的文件才能正常分析
-
-### **避免在`t()`中使用模板字符串**
-
-**强烈建议避免使用模板字符串**进行动态插值。虽然模板字符串在JavaScript开发中非常方便，但在国际化场景下会带来一系列问题。
-
-1. **插件无法跟踪**
-   i18n ally等工具无法解析模板字符串中的动态内容，导致：
-
-   - 无法正确显示实时预览
-   - 无法检测翻译缺失
-   - 无法提供跳转到定义的功能
-
-   ```javascript
-   // 不推荐 - 插件无法解析
-   const message = t(`fruits.${fruit}`)
-   ```
-
-2. **编辑器无法实时渲染**
-   在IDE中，模板字符串会显示为原始代码而非最终翻译结果，降低了开发体验。
-
-3. **更难以维护**
-   由于插件无法跟踪这样的文案，编辑器中也无法渲染，开发者必须人工确认语言文件中是否存在相应的文案。
-
-### 推荐做法
-
-为了避免键的缺失，所有需要动态翻译的文本都应当先维护一个`FooKeyMap`，再通过函数获取翻译文本。
-
-例如：
-
-```ts
-// src/renderer/src/i18n/label.ts
-const themeModeKeyMap = {
-  dark: 'settings.theme.dark',
-  light: 'settings.theme.light',
-  system: 'settings.theme.system'
-} as const
-
-export const getThemeModeLabel = (key: string): string => {
-  return themeModeKeyMap[key] ? t(themeModeKeyMap[key]) : key
-}
-```
-
-通过避免模板字符串，可以获得更好的开发体验、更可靠的翻译检查以及更易维护的代码库。
-
-## 自动化脚本
-
-项目中有一系列脚本来自动化i18n相关任务：
-
-### `check:i18n` - 检查i18n结构
-
-此脚本会检查：
-
-- 所有语言文件是否为嵌套结构
-- 是否存在缺失的key
-- 是否存在多余的key
-- 是否已经有序
-
-```bash
-yarn check:i18n
-```
-
-### `sync:i18n` - 同步json结构与排序
-
-此脚本以`zh-cn.json`文件为基准，将结构同步到其他语言文件，包括：
-
-1. 添加缺失的键。缺少的翻译内容会以`[to be translated]`标记
-2. 删除多余的键
-3. 自动排序
-
-```bash
-yarn sync:i18n
-```
-
-### `auto:i18n` - 自动翻译待翻译文本
-
-次脚本自动将标记为待翻译的文本通过机器翻译填充。
-
-通常，在`zh-cn.json`中添加所需文案后，执行`sync:i18n`即可自动完成翻译。
-
-使用该脚本前，需要配置环境变量，例如：
-
-```bash
-API_KEY="sk-xxx"
-BASE_URL="https://dashscope.aliyuncs.com/compatible-mode/v1/"
-MODEL="qwen-plus-latest"
-```
-
-你也可以通过直接编辑`.env`文件来添加环境变量。
-
-```bash
-yarn auto:i18n
-```
-
-### `update:i18n` - 对象级别翻译更新
-
-对`src/renderer/src/i18n/translate`中的语言文件进行对象级别的翻译更新，保留已有翻译，只更新新增内容。
-
-**不建议**使用该脚本，更推荐使用`auto:i18n`进行翻译。
-
-```bash
-yarn update:i18n
-```
-
-### 工作流
-
-1. 开发阶段，先在`zh-cn.json`中添加所需文案
-2. 确认在中文环境下显示无误后，使用`yarn sync:i18n`将文案同步到其他语言文件
-3. 使用`yarn auto:i18n`进行自动翻译
-4. 喝杯咖啡，等翻译完成吧！
-
-## 最佳实践
-
-1. **以中文为源语言**：所有开发首先使用中文，再翻译为其他语言
-2. **提交前运行检查脚本**：使用`yarn check:i18n`检查i18n是否有问题
-3. **小步提交翻译**：避免积累大量未翻译文本
-4. **保持key语义明确**：key应能清晰表达其用途，如`user.profile.avatar.upload.error`

docs/zh/guides/logging.md

@@ -1,194 +0,0 @@
-# 如何使用日志 LoggerService
-
-这是关于如何使用日志的开发者文档。
-
-CherryStudio使用统一的日志服务来打印和记录日志，**若无特殊原因，请勿使用`console.xxx`来打印日志**。
-
-以下是详细说明。
-
-## 在`main`进程中使用
-
-### 引入
-
-```typescript
-import { loggerService } from '@logger'
-```
-
-### 设置module信息（规范要求）
-
-在import头之后，设置：
-
-```typescript
-const logger = loggerService.withContext('moduleName')
-```
-
-- `moduleName`是当前文件模块的名称，命名可以以文件名、主类名、主函数名等，原则是清晰明了
-- `moduleName`会在终端中打印出来，也会在文件日志中体现，方便筛选
-
-### 设置`CONTEXT`信息（可选）
-
-在`withContext`中，也可以设置其他`CONTEXT`信息：
-
-```typescript
-const logger = loggerService.withContext('moduleName', CONTEXT)
-```
-
-- `CONTEXT`为`{ key: value, ... }`
-- `CONTEXT`信息不会在终端中打印出来，但是会在文件日志中记录，方便筛选
-
-### 记录日志
-
-在代码中，可以随时调用 `logger` 来记录日志，支持的级别有：`error`, `warn`, `info`, `verbose`, `debug`, `silly`。
-
-各级别的含义，请参考后面的章节。
-
-以下支持的记录日志的参数（以 `logger.LEVEL` 举例如何使用，`LEVEL`指代为上述级别）：
-
-```typescript
-logger.LEVEL(message)
-logger.LEVEL(message, CONTEXT)
-logger.LEVEL(message, error)
-logger.LEVEL(message, error, CONTEXT)
-```
-
-**只支持上述四种调用方式**。
-
-| 参数      | 类型     | 说明                                                                                                                                                                                              |
-| --------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `message` | `string` | 必填项。这是日志的核心字段，记录的重点内容                                                                                                                                                        |
-| `CONTEXT` | `object` | 可选。其他需要再日志文件中记录的信息，建议为`{ key: value, ...}`格式                                                                                                                              |
-| `error`   | `Error`  | 可选。同时会打印错误堆栈信息。<br />注意`catch(error)`所捕获的`error`是`unknown`类型，按照`Typescript`最佳实践，请先用`instanceof`进行类型判断，如果确信一定是`Error`类型，也可用断言`as Error`。 |
-
-#### 记录非`object`类型的上下文信息
-
-```typescript
-const foo = getFoo()
-logger.debug(`foo ${foo}`)
-```
-
-### 记录级别
-
-- 开发环境下，所有级别的日志都会打印到终端，并且记录到文件日志中
-- 生产环境下，默认记录级别为`info`，日志只会记录到文件，不会打印到终端
-
-更改日志记录级别：
-
-- 可以通过 `logger.setLevel('newLevel')` 来更改日志记录级别
-- `logger.resetLevel()` 可以重置为默认级别
-- `logger.getLevel()` 可以获取当前记录记录级别
-
-**注意** 更改日志记录级别是全局生效的，请不要在代码中随意更改，除非你非常清楚自己在做什么
-
-## 在`renderer`进程中使用
-
-在`renderer`进程中使用，_引入方法_、_设置`module`信息_、*设置`context`信息的方法*和`main`进程中是**完全一样**的。
-
-下面着重讲一下不同之处。
-
-### `initWindowSource`
-
-`renderer`进程中，有不同的`window`，在开始使用`logger`之前，我们必须设置`window`信息：
-
-```typescript
-loggerService.initWindowSource('windowName')
-```
-
-原则上，我们将在`window`的`entryPoint.tsx`中进行设置，这可以保证`windowName`在开始使用前已经设置好了。
-
-- 未设置`windowName`会报错，`logger`将不起作用
-- `windowName`只能设置一次，重复设置将不生效
-- `windowName`不会在`devTool`的`console`中打印出来，但是会在`main`进程的终端和文件日志中记录
-- `initWindowSource`返回的是LoggerService的实例，因此可以做链式调用
-
-### 记录级别
-
-- 开发环境下，默认所有级别的日志都会打印到`devTool`的`console`
-- 生产环境下，默认记录级别为`info`，日志会打印到`devTool`的`console`
-- 在开发和生产环境下，默认`warn`和`error`级别的日志，会传输给`main`进程，并记录到文件日志
-  - 开发环境下，`main`进程终端中也会打印传输过来的日志
-
-#### 更改日志记录级别
-
-和`main`进程中一样，你可以通过`setLevel('level')`、`resetLevel()`和`getLevel()`来管理日志记录级别。
-
-同样，该日志记录级别也是全局调整的。
-
-#### 更改传输到`main`的级别
-
-将`renderer`的日志发送到`main`，并由`main`统一管理和记录到文件（根据`main`的记录到文件的级别），默认只有`warn`和`error`级别的日志会传输到`main`
-
-有以下两种方式，可以更改传输到`main`的日志级别：
-
-##### 全局更改
-
-以下方法可以分别设置、重置和获取传输到`main`的日志级别
-
-```typescript
-logger.setLogToMainLevel('newLevel')
-logger.resetLogToMainLevel()
-logger.getLogToMainLevel()
-```
-
-**注意** 该方法是全局生效的，请不要在代码中随意更改，除非你非常清楚自己在做什么
-
-##### 单条更改
-
-在日志记录的最末尾，加上`{ logToMain: true }`，即可将本条日志传输到`main`（不受全局日志级别限制），例如：
-
-```typescript
-logger.info('message', { logToMain: true })
-```
-
-## 关于`worker`线程
-
-- 现在不支持`main`进程中的`worker`的日志。
-- 支持`renderer`中起的`worker`的日志，但是现在该日志不会发送给`main`进行记录。
-
-### 如何在`renderer`的`worker`中使用日志
-
-由于`worker`线程是独立的，在其中使用LoggerService，等同于在一个新`renderer`窗口中使用。因此也必须先`initWindowSource`。
-
-如果`worker`比较简单，只有一个文件，也可以使用链式语法直接使用：
-
-```typescript
-const logger = loggerService.initWindowSource('Worker').withContext('LetsWork')
-```
-
-## 使用环境变量来筛选要显示的日志
-
-在开发环境中，可以通过环境变量的定义，来筛选要显示的日志的级别和module。开发者可以专注于自己的日志，提高开发效率。
-
-环境变量可以在终端中自行设置，或者在开发根目录的`.env`文件中进行定义，可以定义的变量如下：
-
-| 变量名                           | 含义                                                                                            |
-| -------------------------------- | ----------------------------------------------------------------------------------------------- |
-| `CSLOGGER_MAIN_LEVEL`            | 用于`main`进程的日志级别，低于该级别的日志将不显示                                              |
-| `CSLOGGER_MAIN_SHOW_MODULES`     | 用于`main`进程的日志module筛选，用`,`分隔，区分大小写。只有在该列表中的module的日志才会显示     |
-| `CSLOGGER_RENDERER_LEVEL`        | 用于`renderer`进程的日志级别，低于该级别的日志将不显示                                          |
-| `CSLOGGER_RENDERER_SHOW_MODULES` | 用于`renderer`进程的日志module筛选，用`,`分隔，区分大小写。只有在该列表中的module的日志才会显示 |
-
-示例：
-
-```bash
-CSLOGGER_MAIN_LEVEL=verbose
-CSLOGGER_MAIN_SHOW_MODULES=MCPService,SelectionService
-```
-
-注意：
-
-- 环境变量仅在开发环境中生效
-- 该变量仅会改变在终端或在devTools中显示的日志，不会影响文件日志和`logToMain`的记录逻辑
-
-## 日志级别的使用规范
-
-日志有很多级别，什么时候应该用哪个级别，下面是在CherryStudio中应该遵循的规范：
-(按日志级别从高到低排列)
-
-| 日志级别      | 核心定义与使用场景                                                                                       | 示例                                                                                                                                                 |
-| :------------ | :------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`error`**   | **严重错误，导致程序崩溃或核心功能无法使用。** <br> 这是最高优的日志，通常需要立即上报或提示用户。       | - 主进程或渲染进程崩溃。 <br> - 无法读写用户关键数据文件（如数据库、配置文件），导致应用无法运行。<br> - 所有未捕获的异常。                          |
-| **`warn`**    | **潜在问题或非预期情况，但不影响程序核心功能。** <br> 程序可以从中恢复或使用备用方案。                   | - 配置文件 `settings.json` 缺失，已使用默认配置启动。 <br> - 自动更新检查失败，但不影响当前版本使用。<br> - 某个非核心插件加载失败。                 |
-| **`info`**    | **记录应用生命周期和关键用户行为。** <br> 这是发布版中默认应记录的级别，用于追踪用户的主要操作路径。     | - 应用启动、退出。<br> - 用户成功打开/保存文件。 <br> - 主窗口创建/关闭。<br> - 开始执行一项重要任务（如“开始导出视频”）。                           |
-| **`verbose`** | **比 `info` 更详细的流程信息，用于追踪特定功能。** <br> 在诊断特定功能问题时开启，帮助理解内部执行流程。 | - 正在加载 `Toolbar` 模块。 <br> - IPC 消息 `open-file-dialog` 已从渲染进程发送。<br> - 正在应用滤镜 'Sepia' 到图像。                                |
-| **`debug`**   | **开发和调试时使用的详细诊断信息。** <br> **严禁在发布版中默认开启**，因为它可能包含敏感数据并影响性能。 | - 函数 `renderImage` 的入参: `{ width: 800, ... }`。<br> - IPC 消息 `save-file` 收到的具体数据内容。<br> - 渲染进程中 Redux/Vuex 的 state 变更详情。 |
-| **`silly`**   | **最详尽的底层信息，仅用于极限调试。** <br> 几乎不在常规开发中使用，仅为解决棘手问题。                   | - 鼠标移动的实时坐标 `(x: 150, y: 320)`。<br> - 读取文件时每个数据块（chunk）的大小。<br> - 每一次渲染帧的耗时。                                     |

docs/zh/guides/test-plan.md

@@ -1,101 +0,0 @@
-# 测试计划
-
-为了给用户提供更稳定的应用体验，并提供更快的迭代速度，Cherry Studio推出“测试计划”。
-
-## 用户指南
-
-测试计划分为RC版通道和Beta版通道吗，区别在于：
-
-- **RC版（预览版）**：RC即Release Candidate，功能已经稳定，BUG较少，接近正式版
-- **Beta版（测试版）**：功能可能随时变化，BUG较多，可以较早体验未来功能
-
-用户可以在软件的`设置`-`关于`中，开启“测试计划”并选择版本通道。请注意“测试计划”的版本无法保证数据的一致性，请使用前一定要备份数据。
-
-用户选择RC版通道或Beta版通道后，若发布了正式版，仍旧会升级到正式版。
-
-用户在测试过程中发现的BUG，欢迎提交issue或通过其他渠道反馈。用户的反馈对我们非常重要。
-
-## 开发者指南
-
-### 参与测试计划
-
-开发者按照[贡献者指南](./contributing.md)要求正常提交`PR`（并注意提交target为`main`）。仓库维护者会综合考虑（例如该功能对应用的影响程度，功能的重要性，是否需要更广泛的测试等），决定该`PR`是否应加入测试计划。
-
-若该`PR`加入测试计划，仓库维护者会做如下操作：
-
-- 通知`PR`提交人
-- 设置PR为`draft`状态（避免在测试完成前意外并入`main`）
-- `milestone`设置为具体测试计划版本
-- 修改`PR`标题
-
-`PR`提交人在参与测试计划过程中，应做到：
-
-- 保持`PR`分支与最新`main`同步（即`PR`分支总是应基于最新`main`代码）
-- 保持`PR`分支为无冲突状态
-- 积极响应 comments & reviews，修复bug
-- 开启维护者可以修改`PR`分支的权限，以便维护者能随时修改BUG
-
-加入测试计划并不保证`PR`的最终合并，也有可能由于功能不成熟或测试反馈不佳而搁置
-
-### 测试计划负责人
-
-某个维护者会被指定为某个版本期间（例如`1.5.0-rc`）的测试计划负责人。测试计划负责人的工作为：
-
-- 判断某个`PR`是否符合测试计划要求，并决定是否应合入当期测试计划
-- 修改加入测试计划的`PR`状态，并与`PR`提交人沟通相关事宜
-- 在测试计划发版前，将加入测试计划的`PR`分支逐一合并（采用squash merge）至`testplan`对应版本分支，并解决冲突
-- 保证`testplan`分支与最新`main`同步
-- 负责测试计划发版
-
-## 深入理解
-
-### 关于`PR`
-
-`PR`是特定分支（及commits）、comments、reviews等各种信息的集合，也是测试计划的**最小管理单元**。
-
-相比将所有功能都提交到某个分支，测试计划通过`PR`来管理功能，这可以带来极大的灵活度和效率：
-
-- 测试计划的各个版本间，可以随意增减功能，而无需繁琐的`revert`操作
-- 明确了功能边界和负责人，bug修复在各自`PR`中完成，隔离了交叉影响，也能更好观察进度
-- `PR`提交人负责与最新`main`之间的冲突；测试计划负责人负责各`PR`分支之间的冲突，但因加入测试计划的各功能相对比较独立（话句话说，如果功能牵涉较广，则应独立上测试计划），冲突一般比较少或简单。
-
-### `testplan`分支
-
-`testplan`分支是用于测试计划发版所用的**临时**分支。
-
-注意：
-
-- **请勿基于该分支开发**。该分支随时会变化甚至删除，且并不保证commit的完整和顺序。
-- **请勿向该分支提交`commit`及`PR`**，将不会得到保留
-- `testplan`分支总是基于最新`main`分支（而不是基于已发布版本），在其之上添加功能
-
-#### RC版分支
-
-分支名称：`testplan/rc/x.y.z`
-
-用于RC版的发版，x.y.z为目标版本号，注意无论是rc.1还是rc.5，只要主版本号为x.y.z，都在该分支完成。
-
-一般而言，该分支发版的版本号命名为`x.y.z-rc.n`
-
-#### Beta版分支
-
-分支名称：`testplan/beta/x.y.z`
-
-用于Beta版的发版，x.y.z为目标版本号，注意无论是beta.1还是beta.5，只要主版本号为x.y.z，都在该分支完成。
-
-一般而言，该分支发版的版本号命名为`x.y.z-beta.n`
-
-### 版本规则
-
-测试计划的应用版本号为：`x.y.z-CHA.n`，其中：
-
-- `x.y.z`为一般意义上的版本号，在这里称为**目标版本号**
-- `CHA`为通道号（Channel），现在分为`rc`和`beta`
-- `n`为发版编号，从`1`计数
-
-完整的版本号举例：`1.5.0-rc.3`、`1.5.1-beta.1`、`1.6.0-beta.6`
-
-测试计划的**目标版本号**指向希望添加这些功能的正式版版本号。例如：
-
-- `1.5.0-rc.3`是指，这是`1.5.0`正式版的预览版（当前最新正式版是`1.4.9`，而`1.5.0`正式版还未发布）
-- `1.5.1-beta.1`是指，这是`1.5.1`正式版的测试版（当前最新正式版是`1.5.0`，而`1.5.1`正式版还未发布）

docs/zh/references/app-upgrade.md

@@ -1,430 +0,0 @@
-# 更新配置系统设计文档
-
-## 背景
-
-当前 AppUpdater 直接请求 GitHub API 获取 beta 和 rc 的更新信息。为了支持国内用户，需要根据 IP 地理位置，分别从 GitHub/GitCode 获取一个固定的 JSON 配置文件，该文件包含所有渠道的更新地址。
-
-## 设计目标
-
-1. 支持根据 IP 地理位置选择不同的配置源（GitHub/GitCode）
-2. 支持版本兼容性控制（如 v1.x 以下必须先升级到 v1.7.0 才能升级到 v2.0）
-3. 易于扩展，支持未来多个主版本的升级路径（v1.6 → v1.7 → v2.0 → v2.8 → v3.0）
-4. 保持与现有 electron-updater 机制的兼容性
-
-## 当前版本策略
-
-- **v1.7.x** 是 1.x 系列的最后版本
-- **v1.7.0 以下**的用户必须先升级到 v1.7.0（或更高的 1.7.x 版本）
-- **v1.7.0 及以上**的用户可以直接升级到 v2.x.x
-
-## 自动化工作流
-
-`x-files/app-upgrade-config/app-upgrade-config.json` 由 [`Update App Upgrade Config`](../../.github/workflows/update-app-upgrade-config.yml) workflow 自动同步。工作流会调用 [`scripts/update-app-upgrade-config.ts`](../../scripts/update-app-upgrade-config.ts) 脚本，根据指定 tag 更新 `x-files/app-upgrade-config` 分支上的配置文件。
-
-### 触发条件
-
-- **Release 事件（`release: released/prereleased`）**  
-  - Draft release 会被忽略。  
-  - 当 GitHub 将 release 标记为 *prerelease* 时，tag 必须包含 `-beta`/`-rc`（可带序号），否则直接跳过。  
-  - 当 release 标记为稳定版时，tag 必须与 GitHub API 返回的最新稳定版本一致，防止发布历史 tag 时意外挂起工作流。  
-  - 满足上述条件后，工作流会根据语义化版本判断渠道（`latest`/`beta`/`rc`），并通过 `IS_PRERELEASE` 传递给脚本。
-- **手动触发（`workflow_dispatch`）**  
-  - 必填：`tag`（例：`v2.0.1`）；选填：`is_prerelease`（默认 `false`）。  
-  - 当 `is_prerelease=true` 时，同样要求 tag 带有 beta/rc 后缀。  
-  - 手动运行仍会请求 GitHub 最新 release 信息，用于在 PR 说明中标注该 tag 是否是最新稳定版。
-
-### 工作流步骤
-
-1. **检查与元数据准备**：`Check if should proceed` 和 `Prepare metadata` 步骤会计算 tag、prerelease 标志、是否最新版本以及用于分支名的 `safe_tag`。若任意校验失败，工作流立即退出。
-2. **检出分支**：默认分支被检出到 `main/`，长期维护的 `x-files/app-upgrade-config` 分支则在 `cs/` 中，所有改动都发生在 `cs/`。
-3. **安装工具链**：安装 Node.js 22、启用 Corepack，并在 `main/` 目录执行 `yarn install --immutable`。
-4. **运行更新脚本**：执行 `yarn tsx scripts/update-app-upgrade-config.ts --tag <tag> --config ../cs/app-upgrade-config.json --is-prerelease <flag>`。  
-   - 脚本会标准化 tag（去掉 `v` 前缀等）、识别渠道、加载 `config/app-upgrade-segments.json` 中的分段规则。  
-   - 校验 prerelease 标志与语义后缀是否匹配、强制锁定的 segment 是否满足、生成镜像的下载地址，并检查 release 是否已经在 GitHub/GitCode 可用（latest 渠道在 GitCode 不可用时会回退到 `https://releases.cherry-ai.com`）。  
-   - 更新对应的渠道配置后，脚本会按 semver 排序写回 JSON，并刷新 `lastUpdated`。
-5. **检测变更并创建 PR**：若 `cs/app-upgrade-config.json` 有变更，则创建 `chore/update-app-upgrade-config/<safe_tag>` 分支，提交信息为 `🤖 chore: sync app-upgrade-config for <tag>`，并向 `x-files/app-upgrade-config` 提 PR；无变更则输出提示。
-
-### 手动触发指南
-
-1. 进入 Cherry Studio 仓库的 GitHub **Actions** 页面，选择 **Update App Upgrade Config** 工作流。
-2. 点击 **Run workflow**，保持默认分支（通常为 `main`），填写 `tag`（如 `v2.1.0`）。  
-3. 只有在 tag 带 `-beta`/`-rc` 后缀时才勾选 `is_prerelease`，稳定版保持默认。  
-4. 启动运行并等待完成，随后到 `x-files/app-upgrade-config` 分支的 PR 查看 `app-upgrade-config.json` 的变更并在验证后合并。
-
-## JSON 配置文件格式
-
-### 文件位置
-
-- **GitHub**: `https://raw.githubusercontent.com/CherryHQ/cherry-studio/refs/heads/x-files/app-upgrade-config/app-upgrade-config.json`
-- **GitCode**: `https://gitcode.com/CherryHQ/cherry-studio/raw/x-files/app-upgrade-config/app-upgrade-config.json`
-
-**说明**：两个镜像源提供相同的配置文件，统一托管在 `x-files/app-upgrade-config` 分支上。客户端根据 IP 地理位置自动选择最优镜像源。
-
-### 配置结构（当前实际配置）
-
-```json
-{
-  "lastUpdated": "2025-01-05T00:00:00Z",
-  "versions": {
-    "1.6.7": {
-      "minCompatibleVersion": "1.0.0",
-      "description": "Last stable v1.7.x release - required intermediate version for users below v1.7",
-      "channels": {
-        "latest": {
-          "version": "1.6.7",
-          "feedUrls": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.6.7",
-            "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/download/v1.6.7"
-          }
-        },
-        "rc": {
-          "version": "1.6.0-rc.5",
-          "feedUrls": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.6.0-rc.5",
-            "gitcode": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.6.0-rc.5"
-          }
-        },
-        "beta": {
-          "version": "1.6.7-beta.3",
-          "feedUrls": {
-            "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.7.0-beta.3",
-            "gitcode": "https://github.com/CherryHQ/cherry-studio/releases/download/v1.7.0-beta.3"
-          }
-        }
-      }
-    },
-    "2.0.0": {
-      "minCompatibleVersion": "1.7.0",
-      "description": "Major release v2.0 - required intermediate version for v2.x upgrades",
-      "channels": {
-        "latest": null,
-        "rc": null,
-        "beta": null
-      }
-    }
-  }
-}
-```
-
-### 未来扩展示例
-
-当需要发布 v3.0 时，如果需要强制用户先升级到 v2.8，可以添加：
-
-```json
-{
-  "2.8.0": {
-    "minCompatibleVersion": "2.0.0",
-    "description": "Stable v2.8 - required for v3 upgrade",
-    "channels": {
-      "latest": {
-        "version": "2.8.0",
-        "feedUrls": {
-          "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v2.8.0",
-          "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/download/v2.8.0"
-        }
-      },
-      "rc": null,
-      "beta": null
-    }
-  },
-  "3.0.0": {
-    "minCompatibleVersion": "2.8.0",
-    "description": "Major release v3.0",
-    "channels": {
-      "latest": {
-        "version": "3.0.0",
-        "feedUrls": {
-          "github": "https://github.com/CherryHQ/cherry-studio/releases/latest",
-          "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/latest"
-        }
-      },
-      "rc": {
-        "version": "3.0.0-rc.1",
-        "feedUrls": {
-          "github": "https://github.com/CherryHQ/cherry-studio/releases/download/v3.0.0-rc.1",
-          "gitcode": "https://gitcode.com/CherryHQ/cherry-studio/releases/download/v3.0.0-rc.1"
-        }
-      },
-      "beta": null
-    }
-  }
-}
-```
-
-### 字段说明
-
-- `lastUpdated`: 配置文件最后更新时间（ISO 8601 格式）
-- `versions`: 版本配置对象，key 为版本号，按语义化版本排序
-  - `minCompatibleVersion`: 可以升级到此版本的最低兼容版本
-  - `description`: 版本描述
-  - `channels`: 更新渠道配置
-    - `latest`: 稳定版渠道
-    - `rc`: Release Candidate 渠道
-    - `beta`: Beta 测试渠道
-    - 每个渠道包含：
-      - `version`: 该渠道的版本号
-      - `feedUrls`: 多镜像源 URL 配置
-        - `github`: GitHub 镜像源的 electron-updater feed URL
-        - `gitcode`: GitCode 镜像源的 electron-updater feed URL
-  - `metadata`: 自动化匹配所需的稳定标识
-    - `segmentId`: 来自 `config/app-upgrade-segments.json` 的段位 ID
-    - `segmentType`: 可选字段（`legacy` | `breaking` | `latest`），便于文档/调试
-
-## TypeScript 类型定义
-
-```typescript
-// 镜像源枚举
-enum UpdateMirror {
-  GITHUB = 'github',
-  GITCODE = 'gitcode'
-}
-
-interface UpdateConfig {
-  lastUpdated: string
-  versions: {
-    [versionKey: string]: VersionConfig
-  }
-}
-
-interface VersionConfig {
-  minCompatibleVersion: string
-  description: string
-  channels: {
-    latest: ChannelConfig | null
-    rc: ChannelConfig | null
-    beta: ChannelConfig | null
-  }
-  metadata?: {
-    segmentId: string
-    segmentType?: 'legacy' | 'breaking' | 'latest'
-  }
-}
-
-interface ChannelConfig {
-  version: string
-  feedUrls: Record<UpdateMirror, string>
-  // 等同于:
-  // feedUrls: {
-  //   github: string
-  //   gitcode: string
-  // }
-}
-```
-
-## 段位元数据（Break Change 标记）
-
-- 所有段位定义（如 `legacy-v1`、`gateway-v2` 等）集中在 `config/app-upgrade-segments.json`，用于描述匹配范围、`segmentId`、`segmentType`、默认 `minCompatibleVersion/description` 以及各渠道的 URL 模板。
-- `versions` 下的每个节点都会带上 `metadata.segmentId`。自动脚本始终依据该 ID 来定位并更新条目，即便 key 从 `2.1.5` 切换到 `2.1.6` 也不会错位。
-- 如果某段需要锁死在特定版本（例如 `2.0.0` 的 break change），可在段定义中设置 `segmentType: "breaking"` 并提供 `lockedVersion`，脚本在遇到不匹配的 tag 时会短路报错，保证升级路径安全。
-- 面对未来新的断层（例如 `3.0.0`），只需要在段定义里新增一段，自动化即可识别并更新。
-
-## 自动化工作流
-
-`.github/workflows/update-app-upgrade-config.yml` 会在 GitHub Release（包含正常发布与 Pre Release）触发：
-
-1. 同时 Checkout 仓库默认分支（用于脚本）和 `x-files/app-upgrade-config` 分支（真实托管配置的分支）。
-2. 在默认分支目录执行 `yarn tsx scripts/update-app-upgrade-config.ts --tag <tag> --config ../cs/app-upgrade-config.json`，直接重写 `x-files/app-upgrade-config` 分支里的配置文件。
-3. 如果 `app-upgrade-config.json` 有变化，则通过 `peter-evans/create-pull-request` 自动创建一个指向 `x-files/app-upgrade-config` 的 PR，Diff 仅包含该文件。
-
-如需本地调试，可执行 `yarn update:upgrade-config --tag v2.1.6 --config ../cs/app-upgrade-config.json`（加 `--dry-run` 仅打印结果）来复现 CI 行为。若需要暂时跳过 GitHub/GitCode Release 页面是否就绪的校验，可在 `--dry-run` 的同时附加 `--skip-release-checks`。不加 `--config` 时默认更新当前工作目录（通常是 main 分支）下的副本，方便文档/审查。
-
-## 版本匹配逻辑
-
-### 算法流程
-
-1. 获取用户当前版本（`currentVersion`）和请求的渠道（`requestedChannel`）
-2. 获取配置文件中所有版本号，按语义化版本从大到小排序
-3. 遍历排序后的版本列表：
-   - 检查 `currentVersion >= minCompatibleVersion`
-   - 检查请求的 `channel` 是否存在且不为 `null`
-   - 如果满足条件，返回该渠道配置
-4. 如果没有找到匹配版本，返回 `null`
-
-### 伪代码实现
-
-```typescript
-function findCompatibleVersion(
-  currentVersion: string,
-  requestedChannel: UpgradeChannel,
-  config: UpdateConfig
-): ChannelConfig | null {
-  // 获取所有版本号并从大到小排序
-  const versions = Object.keys(config.versions).sort(semver.rcompare)
-
-  for (const versionKey of versions) {
-    const versionConfig = config.versions[versionKey]
-    const channelConfig = versionConfig.channels[requestedChannel]
-
-    // 检查版本兼容性和渠道可用性
-    if (
-      semver.gte(currentVersion, versionConfig.minCompatibleVersion) &&
-      channelConfig !== null
-    ) {
-      return channelConfig
-    }
-  }
-
-  return null // 没有找到兼容版本
-}
-```
-
-## 升级路径示例
-
-### 场景 1: v1.6.5 用户升级（低于 1.7）
-
-- **当前版本**: 1.6.5
-- **请求渠道**: latest
-- **匹配结果**: 1.7.0
-- **原因**: 1.6.5 >= 0.0.0（满足 1.7.0 的 minCompatibleVersion），但不满足 2.0.0 的 minCompatibleVersion (1.7.0)
-- **操作**: 提示用户升级到 1.7.0，这是升级到 v2.x 的必要中间版本
-
-### 场景 2: v1.6.5 用户请求 rc/beta
-
-- **当前版本**: 1.6.5
-- **请求渠道**: rc 或 beta
-- **匹配结果**: 1.7.0 (latest)
-- **原因**: 1.7.0 版本不提供 rc/beta 渠道（值为 null）
-- **操作**: 升级到 1.7.0 稳定版
-
-### 场景 3: v1.7.0 用户升级到最新版
-
-- **当前版本**: 1.7.0
-- **请求渠道**: latest
-- **匹配结果**: 2.0.0
-- **原因**: 1.7.0 >= 1.7.0（满足 2.0.0 的 minCompatibleVersion）
-- **操作**: 直接升级到 2.0.0（当前最新稳定版）
-
-### 场景 4: v1.7.2 用户升级到 RC 版本
-
-- **当前版本**: 1.7.2
-- **请求渠道**: rc
-- **匹配结果**: 2.0.0-rc.1
-- **原因**: 1.7.2 >= 1.7.0（满足 2.0.0 的 minCompatibleVersion），且 rc 渠道存在
-- **操作**: 升级到 2.0.0-rc.1
-
-### 场景 5: v1.7.0 用户升级到 Beta 版本
-
-- **当前版本**: 1.7.0
-- **请求渠道**: beta
-- **匹配结果**: 2.0.0-beta.1
-- **原因**: 1.7.0 >= 1.7.0，且 beta 渠道存在
-- **操作**: 升级到 2.0.0-beta.1
-
-### 场景 6: v2.5.0 用户升级（未来）
-
-假设已添加 v2.8.0 和 v3.0.0 配置：
-- **当前版本**: 2.5.0
-- **请求渠道**: latest
-- **匹配结果**: 2.8.0
-- **原因**: 2.5.0 >= 2.0.0（满足 2.8.0 的 minCompatibleVersion），但不满足 3.0.0 的要求
-- **操作**: 提示用户升级到 2.8.0，这是升级到 v3.x 的必要中间版本
-
-## 代码改动计划
-
-### 主要修改
-
-1. **新增方法**
-   - `_fetchUpdateConfig(ipCountry: string): Promise<UpdateConfig | null>` - 根据 IP 获取配置文件
-   - `_findCompatibleChannel(currentVersion: string, channel: UpgradeChannel, config: UpdateConfig): ChannelConfig | null` - 查找兼容的渠道配置
-
-2. **修改方法**
-   - `_getReleaseVersionFromGithub()` → 移除或重构为 `_getChannelFeedUrl()`
-   - `_setFeedUrl()` - 使用新的配置系统替代现有逻辑
-
-3. **新增类型定义**
-   - `UpdateConfig`
-   - `VersionConfig`
-   - `ChannelConfig`
-
-### 镜像源选择逻辑
-
-客户端根据 IP 地理位置自动选择最优镜像源：
-
-```typescript
-private async _setFeedUrl() {
-  const currentVersion = app.getVersion()
-  const testPlan = configManager.getTestPlan()
-  const requestedChannel = testPlan ? this._getTestChannel() : UpgradeChannel.LATEST
-
-  // 根据 IP 国家确定镜像源
-  const ipCountry = await getIpCountry()
-  const mirror = ipCountry.toLowerCase() === 'cn' ? 'gitcode' : 'github'
-
-  // 获取更新配置
-  const config = await this._fetchUpdateConfig(mirror)
-
-  if (config) {
-    const channelConfig = this._findCompatibleChannel(currentVersion, requestedChannel, config)
-    if (channelConfig) {
-      // 从配置中选择对应镜像源的 URL
-      const feedUrl = channelConfig.feedUrls[mirror]
-      this._setChannel(requestedChannel, feedUrl)
-      return
-    }
-  }
-
-  // Fallback 逻辑
-  const defaultFeedUrl = mirror === 'gitcode'
-    ? FeedUrl.PRODUCTION
-    : FeedUrl.GITHUB_LATEST
-  this._setChannel(UpgradeChannel.LATEST, defaultFeedUrl)
-}
-
-private async _fetchUpdateConfig(mirror: 'github' | 'gitcode'): Promise<UpdateConfig | null> {
-  const configUrl = mirror === 'gitcode'
-    ? UpdateConfigUrl.GITCODE
-    : UpdateConfigUrl.GITHUB
-
-  try {
-    const response = await net.fetch(configUrl, {
-      headers: {
-        'User-Agent': generateUserAgent(),
-        'Accept': 'application/json',
-        'X-Client-Id': configManager.getClientId()
-      }
-    })
-    return await response.json() as UpdateConfig
-  } catch (error) {
-    logger.error('Failed to fetch update config:', error)
-    return null
-  }
-}
-```
-
-## 降级和容错策略
-
-1. **配置文件获取失败**: 记录错误日志，返回当前版本，不提供更新
-2. **没有匹配的版本**: 提示用户当前版本不支持自动升级
-3. **网络异常**: 缓存上次成功获取的配置（可选）
-
-## GitHub Release 要求
-
-为支持中间版本升级，需要保留以下文件：
-
-- **v1.7.0 release** 及其 latest*.yml 文件（作为 v1.7 以下用户的升级目标）
-- 未来如需强制中间版本（如 v2.8.0），需要保留对应的 release 和 latest*.yml 文件
-- 各版本的完整安装包
-
-### 当前需要的 Release
-
-| 版本 | 用途 | 必须保留 |
-|------|------|---------|
-| v1.7.0 | 1.7 以下用户的升级目标 | ✅ 是 |
-| v2.0.0-rc.1 | RC 测试渠道 | ❌ 可选 |
-| v2.0.0-beta.1 | Beta 测试渠道 | ❌ 可选 |
-| latest | 最新稳定版（自动） | ✅ 是 |
-
-## 优势
-
-1. **灵活性**: 支持任意复杂的升级路径
-2. **可扩展性**: 新增版本只需在配置文件中添加新条目
-3. **可维护性**: 配置与代码分离，无需发版即可调整升级策略
-4. **多源支持**: 自动根据地理位置选择最优配置源
-5. **版本控制**: 强制中间版本升级，确保数据迁移和兼容性
-
-## 未来扩展
-
-- 支持更细粒度的版本范围控制（如 `>=1.5.0 <1.8.0`）
-- 支持多步升级路径提示（如提示用户需要 1.5 → 1.8 → 2.0）
-- 支持 A/B 测试和灰度发布
-- 支持配置文件的本地缓存和过期策略

docs/zh/references/code-execution.md

@@ -1,127 +0,0 @@
-# 代码执行功能
-
-本文档说明了代码块的 Python 代码执行功能。该实现利用 [Pyodide][pyodide-link] 在浏览器环境中直接运行 Python 代码，并将其置于 Web Worker 中，以避免阻塞主 UI 线程。
-
-整个实现分为三个主要部分：UI 层、服务层和 Worker 层。
-
-## 执行流程图
-
-```mermaid
-sequenceDiagram
-    participant 用户
-    participant CodeBlockView (UI)
-    participant PyodideService (服务)
-    participant PyodideWorker (Worker)
-
-    用户->>CodeBlockView (UI): 点击“运行”按钮
-    CodeBlockView (UI)->>PyodideService (服务): 调用 runScript(code)
-    PyodideService (服务)->>PyodideWorker (Worker): 发送 postMessage({ id, python: code })
-    PyodideWorker (Worker)->>PyodideWorker (Worker): 加载 Pyodide 和相关包
-    PyodideWorker (Worker)->>PyodideWorker (Worker): (按需)注入垫片并合并代码
-    PyodideWorker (Worker)->>PyodideWorker (Worker): 执行合并后的 Python 代码
-    PyodideWorker (Worker)-->>PyodideService (服务): 返回 postMessage({ id, output })
-    PyodideService (服务)-->>CodeBlockView (UI): 返回 { text, image } 对象
-    CodeBlockView (UI)->>用户: 在状态栏中显示文本和/或图像输出
-```
-
-## 1. UI 层
-
-面向用户的代码执行组件是 [CodeBlockView][codeblock-view-link]。
-
-### 关键机制：
-
-- **运行按钮**：当代码块语言为 `python` 且 `codeExecution.enabled` 设置为 true 时，`CodeToolbar` 中会条件性地渲染一个“运行”按钮。
-- **事件处理**：运行按钮的 `onClick` 事件会触发 `handleRunScript` 函数。
-- **服务调用**：`handleRunScript` 调用 `pyodideService.runScript(code)`，将代码块中的 Python 代码传递给服务。
-- **状态管理与输出显示**：使用 `executionResult` 来管理所有执行输出，只要有任何结果（文本或图像），[StatusBar][statusbar-link] 组件就会被渲染以统一显示。
-
-```typescript
-// src/renderer/src/components/CodeBlockView/view.tsx
-const [executionResult, setExecutionResult] = useState<{ text: string; image?: string } | null>(null)
-
-const handleRunScript = useCallback(() => {
-  setIsRunning(true)
-  setExecutionResult(null)
-
-  pyodideService
-    .runScript(children, {}, codeExecution.timeoutMinutes * 60000)
-    .then((result) => {
-      setExecutionResult(result)
-    })
-    .catch((error) => {
-      console.error('Unexpected error:', error)
-      setExecutionResult({
-        text: `Unexpected error: ${error.message || 'Unknown error'}`
-      })
-    })
-    .finally(() => {
-      setIsRunning(false)
-    })
-}, [children, codeExecution.timeoutMinutes]);
-
-// ... 在 JSX 中
-{isExecutable && executionResult && (
-  <StatusBar>
-    {executionResult.text}
-    {executionResult.image && (
-      <ImageOutput>
-        <img src={executionResult.image} alt="Matplotlib plot" />
-      </ImageOutput>
-    )}
-  </StatusBar>
-)}
-```
-
-## 2. 服务层
-
-服务层充当 UI 组件和运行 Pyodide 的 Web Worker 之间的桥梁。其逻辑封装在位于单例类 [PyodideService][pyodide-service-link]。
-
-### 主要职责：
-
-- **Worker 管理**：初始化、管理并与 Pyodide Web Worker 通信。
-- **请求处理**：使用 `resolvers` Map 管理并发请求，通过唯一 ID 匹配请求和响应。
-- **为 UI 提供 API**：向 UI 提供 `runScript(script, context, timeout)` 方法。此方法的返回值已修改为 `Promise<{ text: string; image?: string }>`，以支持包括图像在内的多种输出类型。
-- **输出处理**：从 Worker 接收包含文本、错误和可选图像数据的 `output` 对象。它将文本和错误格式化为对用户友好的单个字符串，然后连同图像数据一起包装成对象返回给 UI 层。
-- **IPC 端点**：该服务还提供了一个 `python-execution-request` IPC 端点，允许主进程请求执行 Python 代码，展示了其灵活的架构。
-
-## 3. Worker 层
-
-核心的 Python 执行发生在 [pyodide.worker.ts][pyodide-worker-link] 中定义的 Web Worker 内部。这确保了计算密集的 Python 代码不会冻结用户界面。
-
-### Worker 逻辑：
-
-- **Pyodide 加载**：Worker 从 CDN 加载 Pyodide 引擎，并设置处理器以捕获 Python 的 `stdout` 和 `stderr`。
-- **动态包安装**：使用 `pyodide.loadPackagesFromImports()` 自动分析并安装代码中导入的依赖包。
-- **按需执行垫片代码**：Worker 会检查传入的代码中是否包含 "matplotlib" 字符串。如果是，它会先执行一段 Python“垫片”代码确保图像输出到全局命名空间。
-- **结果序列化**：执行结果通过 `.toJs()` 等方法被递归转换为可序列化的标准 JavaScript 对象。
-- **返回结构化输出**：执行后，Worker 将一个包含 `id` 和 `output` 对象的-消息发回服务层。`output` 对象是一个结构化对象，包含 `result`、`text`、`error` 以及一个可选的 `image` 字段（用于 Base64 图像数据）。
-
-### 数据流
-
-最终的数据流如下：
-
-1.  **UI 层 ([CodeBlockView][codeblock-view-link])**: 用户点击“运行”按钮。
-2.  **服务层 ([PyodideService][pyodide-service-link])**:
-    - 接收到代码执行请求。
-    - 调用 Web Worker ([pyodide.worker.ts][pyodide-worker-link])，传递用户代码。
-3.  **Worker 层 ([pyodide.worker.ts][pyodide-worker-link])**:
-    - 加载 Pyodide 运行时。
-    - 动态安装代码中 `import` 语句声明的依赖包。
-    - **注入 Matplotlib 垫片**: 如果代码中包含 `matplotlib`，则在用户代码前拼接垫片代码，强制使用 `AGG` 后端。
-    - **执行代码并捕获输出**: 在代码执行后，检查 `matplotlib.pyplot` 的所有 figure，如果存在图像，则将其保存到内存中的 `BytesIO` 对象，并编码为 Base64 字符串。
-    - **结构化返回**: 将捕获的文本输出和 Base64 图像数据封装在一个 JSON 对象中 (`{ "text": "...", "image": "data:image/png;base64,..." }`) 返回给主线程。
-4.  **服务层 ([PyodideService][pyodide-service-link])**:
-    - 接收来自 Worker 的结构化数据。
-    - 将数据原样传递给 UI 层。
-5.  **UI 层 ([CodeBlockView][codeblock-view-link])**:
-    - 接收包含文本和图像数据的对象。
-    - 使用一个 `useState` 来管理执行结果 (`executionResult`)。
-    - 在界面上分别渲染文本输出和图像（如果存在）。
-
-<!-- Link Definitions -->
-
-[pyodide-link]: https://pyodide.org/
-[codeblock-view-link]: /src/renderer/src/components/CodeBlockView/view.tsx
-[pyodide-service-link]: /src/renderer/src/services/PyodideService.ts
-[pyodide-worker-link]: /src/renderer/src/workers/pyodide.worker.ts
-[statusbar-link]: /src/renderer/src/components/CodeBlockView/StatusBar.tsx

docs/zh/references/components/code-block-view.md

@@ -1,180 +0,0 @@
-# CodeBlockView 组件结构说明
-
-## 概述
-
-CodeBlockView 是 Cherry Studio 中用于显示和操作代码块的核心组件。它支持多种视图模式和特殊语言的可视化预览，提供丰富的交互工具。
-
-## 组件结构
-
-```mermaid
-graph TD
-    A[CodeBlockView] --> B[CodeToolbar]
-    A --> C[SourceView]
-    A --> D[SpecialView]
-    A --> E[StatusBar]
-
-    B --> F[CodeToolButton]
-
-    C --> G[CodeEditor / CodeViewer]
-
-    D --> H[MermaidPreview]
-    D --> I[PlantUmlPreview]
-    D --> J[SvgPreview]
-    D --> K[GraphvizPreview]
-
-    F --> L[useCopyTool]
-    F --> M[useDownloadTool]
-    F --> N[useViewSourceTool]
-    F --> O[useSplitViewTool]
-    F --> P[useRunTool]
-    F --> Q[useExpandTool]
-    F --> R[useWrapTool]
-    F --> S[useSaveTool]
-```
-
-## 核心概念
-
-### 视图类型
-
-- **preview**: 预览视图，非源代码的是特殊视图
-- **edit**: 编辑视图
-
-### 视图模式
-
-- **source**: 源代码视图模式
-- **special**: 特殊视图模式（Mermaid、PlantUML、SVG）
-- **split**: 分屏模式（源代码和特殊视图并排显示）
-
-### 特殊视图语言
-
-- mermaid
-- plantuml
-- svg
-- dot
-- graphviz
-
-## 组件详细说明
-
-### CodeBlockView 主组件
-
-主要负责：
-
-1. 管理视图模式状态
-2. 协调源代码视图和特殊视图的显示
-3. 管理工具栏工具
-4. 处理代码执行状态
-
-### 子组件
-
-#### CodeToolbar 工具栏
-
-- 显示在代码块右上角的工具栏
-- 包含核心(core)和快捷(quick)两类工具
-- 根据上下文动态显示相关工具
-
-#### CodeEditor/CodeViewer 源代码视图
-
-- 可编辑的代码编辑器或只读的代码查看器
-- 根据设置决定使用哪个组件
-- 支持多种编程语言高亮
-
-#### 特殊视图组件
-
-- **MermaidPreview**: Mermaid 图表预览
-- **PlantUmlPreview**: PlantUML 图表预览
-- **SvgPreview**: SVG 图像预览
-- **GraphvizPreview**: Graphviz 图表预览
-
-所有特殊视图组件共享通用架构，以确保一致的用户体验和功能。有关这些组件及其实现的详细信息，请参阅[图像预览组件文档](./image-preview.md)。
-
-#### StatusBar 状态栏
-
-- 显示 Python 代码执行结果
-- 可显示文本和图像结果
-
-## 工具系统
-
-CodeBlockView 使用基于 hooks 的工具系统：
-
-```mermaid
-graph TD
-    A[CodeBlockView] --> B[useCopyTool]
-    A --> C[useDownloadTool]
-    A --> D[useViewSourceTool]
-    A --> E[useSplitViewTool]
-    A --> F[useRunTool]
-    A --> G[useExpandTool]
-    A --> H[useWrapTool]
-    A --> I[useSaveTool]
-
-    B --> J[ToolManager]
-    C --> J
-    D --> J
-    E --> J
-    F --> J
-    G --> J
-    H --> J
-    I --> J
-
-    J --> K[CodeToolbar]
-```
-
-每个工具 hook 负责注册特定功能的工具按钮到工具管理器，工具管理器再将这些工具传递给 CodeToolbar 组件进行渲染。
-
-### 工具类型
-
-- **core**: 核心工具，始终显示在工具栏
-- **quick**: 快捷工具，当数量大于1时通过下拉菜单显示
-
-### 工具列表
-
-1. **复制(copy)**: 复制代码或图像
-2. **下载(download)**: 下载代码或图像
-3. **查看源码(view-source)**: 在特殊视图和源码视图间切换
-4. **分屏(split-view)**: 切换分屏模式
-5. **运行(run)**: 运行 Python 代码
-6. **展开/折叠(expand)**: 控制代码块的展开/折叠
-7. **换行(wrap)**: 控制代码的自动换行
-8. **保存(save)**: 保存编辑的代码
-
-## 状态管理
-
-CodeBlockView 通过 React hooks 管理以下状态：
-
-1. **viewMode**: 当前视图模式 ('source' | 'special' | 'split')
-2. **isRunning**: Python 代码执行状态
-3. **executionResult**: Python 代码执行结果
-4. **tools**: 工具栏工具列表
-5. **expandOverride/unwrapOverride**: 用户展开/换行的覆盖设置
-6. **sourceScrollHeight**: 源代码视图滚动高度
-
-## 交互流程
-
-```mermaid
-sequenceDiagram
-    participant U as User
-    participant CB as CodeBlockView
-    participant CT as CodeToolbar
-    participant SV as SpecialView
-    participant SE as SourceEditor
-
-    U->>CB: 查看代码块
-    CB->>CB: 初始化状态
-    CB->>CT: 注册工具
-    CB->>SV: 渲染特殊视图(如果适用)
-    CB->>SE: 渲染源码视图
-    U->>CT: 点击工具按钮
-    CT->>CB: 触发工具回调
-    CB->>CB: 更新状态
-    CB->>CT: 重新注册工具(如果需要)
-```
-
-## 特殊处理
-
-### HTML 代码块
-
-HTML 代码块会被特殊处理，使用 HtmlArtifactsCard 组件显示。
-
-### Python 代码执行
-
-支持执行 Python 代码并显示结果，使用 Pyodide 在浏览器中运行 Python 代码。