Merge branch 'main' into feat/2.5.0

# Conflicts:
#	src/frontend/platform/public/locales/en-US/bs.json
#	src/frontend/platform/public/locales/en-US/dashboard.json
#	src/frontend/platform/public/locales/en-US/knowledge.json
#	src/frontend/platform/public/locales/en-US/model.json

src/frontend/platform/public/locales/en-US/bs.json

@@ -110,7 +110,8 @@
     "registrationSuccess": "Registration successful. Please enter your password to log in",
     "pleaseEnterCaptcha": "Please enter captcha",
     "passwordExpired": "Your password has expired, please change it promptly",
-    "otherMethods": "Other login methods"
+    "otherMethods": "Other login methods",
+    "bottomText": "Bisheng"
   },
   "menu": {
     "user": "User",
@@ -708,7 +709,8 @@
       "modelRequired": "Model cannot be empty",
       "modelDuplicate": "Model cannot be duplicated",
       "modelNameDuplicate": "Display name cannot be duplicated",
-      "required": "Cannot be empty"
+      "required": "Cannot be empty",
+      "voiceTypeRequired": "Voice type is required"
     },
     "systemPrompt2": "# Role\nYou are the $t(bisheng) Intelligent Q&A Assistant. Your task is to answer user questions by combining the query with available tools (such as knowledge base retrieval and web search) when necessary to obtain supporting evidence.\n\n# General Requirements\n1. Always respond in the language currently used by the user.\n2. Maintain a rigorous, professional, and clear style.\n3. Prefer answers based on known information or tool results; if tools are needed, search first, then answer.\n4. Do not present unverified guesses or assumptions as facts.\n\n# Tool Usage Rules\n## 1. Knowledge Base / Web Search\nWhen a question depends on knowledge base or web search results, only answer if the retrieved information is clearly relevant and sufficient to support the response.\n\nDo NOT answer based on results if:\n- Results are empty\n- Results are irrelevant\n- Relevance is weak and cannot support a clear conclusion\n- Information is insufficient\n\n## 2. No Fabrication\n- Do NOT fabricate any knowledge base results, search results, images, document snippets, or reference IDs\n- Do NOT claim \"according to search results\" without actual evidence\n- Do NOT invent or complete nonexistent reference IDs\n\n# Rendering Rules\n## 1. Image Rendering\nIf results include image references like: `![image](path/IMAGE_1.png)`\n\nYou must:\n- Preserve original Markdown format\n- Not modify, delete, or transform it\n\n## 2. Chart Rendering\nIf charts are needed, use ```echarts code blocks:\n\n```echarts\n{\n  \\\"title\\\": {\n    \\\"text\\\": \\\"ECharts Example\\\"\n  },\n  \\\"tooltip\\\": {},\n  \\\"legend\\\": {\n    \\\"data\\\": [\\\"Sales\\\"]\n  },\n  \\\"xAxis\\\": {\n    \\\"data\\\": [\\\"Shirts\\\", \\\"Sweaters\\\", \\\"Chiffon\\\", \\\"Pants\\\", \\\"Heels\\\", \\\"Socks\\\"]\n  },\n  \\\"yAxis\\\": {},\n  \\\"series\\\": [{\n    \\\"name\\\": \\\"Sales\\\",\n    \\\"type\\\": \\\"bar\\\",\n    \\\"data\\\": [5, 20, 36, 10, 10, 20]\n  }]\n}\n```\n\n# Citation Rules\nWhen using knowledge base or web search results, append references at the end of the paragraph.\n\n## Format\n- `\\ue200`: start\n- `\\ue201`: separator\n- `\\ue202`: end\n\n## Requirements\n1. Place at end of paragraph\n2. Single: `text.\\ue200id\\ue202`\n3. Multiple: `text.\\ue200id1\\ue201id2\\ue202`\n4. IDs must come from tools\n5. No fabrication\n6. Do not add if unused\n\n## Other\nCurrent time: {cur_date}。",
     "webSearchPrompt": "# The following content is based on the search results of the message sent by the user:\n{search_results}\nIn the search results I provide you, each result is in the format [webpage X begin]...[webpage X end], where X represents the numerical index of each article. Please cite the context at the end of sentences when appropriate. Use the citation number [citation:X] format in the corresponding part of the answer. If a sentence comes from multiple contexts, list all relevant citation numbers, for example: cite[3]:cite[5]. Remember not to concentrate citations at the end but list them in the corresponding parts of the answer.\nWhen answering, please note the following points:\n- Today is {cur_date}.\n- Not all content in the search results is closely related to the user's question. You need to combine the question and filter the search results.\n- For enumeration questions (such as listing all flight information), try to keep the answer within 10 key points and inform the user that they can check the source for complete information. Prioritize providing complete and most relevant items; do not proactively inform the user of content not provided in the search results unless necessary.\n- For creative questions (such as writing an essay), ensure that you cite the corresponding reference numbers in the body paragraphs, for example: cite[3]:cite[5]. Do not only cite at the end of the article. Interpret and summarize the user's requirements, choose an appropriate format, fully utilize the search results, and extract important information to generate answers that meet the user's requirements, are highly insightful, creative, and professional. Extend the length of your creation as much as possible, infer the user's intent for each key point, and provide multi-angle answers with substantial information and detailed explanations.\n- If the answer is long, try to structure it and summarize in paragraphs. If you need to answer in points, try to limit it to 5 points and merge related content.\n- For objective questions, if the answer is very short, you can add one or two additional pieces of relevant information to enrich the content.\n- Choose an appropriate and aesthetically pleasing answer format based on the user's requirements and content to ensure readability.\n- Your answer should be based on multiple relevant web pages and should not repeatedly cite the same page.\n- Unless the user requests otherwise, the language of your answer should match the language of the user's question.\n\n# User message is:\n{question}",
@@ -2202,5 +2204,10 @@
   "dailyFullName": "{{dailyFullName}}",
   "failed": "Failed",
   "inProgress": "In Progress",
-  "success": "Success"
+  "success": "Success",
+  "com_preview_type_unsupported": "This file type is not supported for preview",
+  "success": "Success",
+  "failed": "Failed",
+  "inProgress": "In Progress",
+  "createImport": "Create and Import"
 }

src/frontend/platform/public/locales/en-US/flow.json

@@ -141,6 +141,7 @@
   "inputInteractionTooltip": "Provide the ability for users to edit text, suitable for multi-step task processing scenarios, such as allowing users to directly modify model-generated content or input suggestions for optimization. Submitted content will be stored in the output_result variable.",
   "dbAddress": "Database Address",
   "dbName": "Database Name",
+  "dbType": "Database Type",
   "dbUsername": "Database Username",
   "dbPassword": "Database Password",
   "dbAddressRequired": "Database address cannot be empty",

src/frontend/platform/public/locales/en-US/model.json

@@ -56,6 +56,8 @@
     "modelName": "Model Name",
     "modelNameTooltip": "Name for local deployment or API request",
     "modelType": "Type",
+        "voiceType": "Voice Type",
+        "voiceTypeRequired": "Voice type is required",
     "webSearch": "Online Search",
     "systemModelSettings": "System Settings",
     "knowledgeBaseModel": "Knowledge",
@@ -67,6 +69,9 @@
     "defaultEmbeddingModel": "Default Embedding for Knowledge Base",
     "sourceTracingModel": "Source Tracing for Knowledge Base",
     "sourceTracingModelTooltip": "Used for knowledge base (including workstation knowledge space) Q&A traceability. LLM automatically extracts keywords from answers to help users quickly locate possible source paragraphs. If not configured here, jieba word segmentation will be used to output keywords from the answers.",
+        "sourceTracingModelTooltip": "Auto-extract keywords for source tracing. Uses jieba if not configured.",
+        "workInformationModel": "Workbench Information Summary Model",
+        "workInformationModelTooltip": "Used for workbench sidebar dialog title generation and SOP name/description generation. Recommend a model with fewer parameters and faster response.",
     "documentSummaryModel": "Doc Summary for Knowledge Base",
     "documentSummaryModelTooltip": "Summarizes content into title for vector DB. Not summarized if not configured.",
     "qaSimilarModel": "QA Similar Model",