From 4023ab62eb4fcb881e65cc21a3c221b9612f3c38 Mon Sep 17 00:00:00 2001
From: lyzno1 <yuanyouhuilyz@gmail.com>
Date: Thu, 14 Aug 2025 19:25:23 +0800
Subject: [PATCH] fix: align Authorization and error response descriptions
 across all languages
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- Update Authorization description to match other API files
- Add bearerFormat field for consistency
- Ensure FileError, FileTooLarge, UnsupportedFileType descriptions are aligned
- Maintain semantic consistency across English, Chinese, and Japanese versions

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
---
 en/openapi_knowledge.json      | 3 ++-
 ja-jp/openapi_knowledge.json   | 3 ++-
 zh-hans/openapi_knowledge.json | 3 ++-
 3 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/en/openapi_knowledge.json b/en/openapi_knowledge.json
index 6773045b..7b8a799a 100644
--- a/en/openapi_knowledge.json
+++ b/en/openapi_knowledge.json
@@ -1711,7 +1711,8 @@
       "ApiKeyAuth": {
         "type": "http",
         "scheme": "bearer",
-        "description": "API Key authentication. Provide the key in the 'Authorization' header as 'Bearer {API_KEY}'."
+        "bearerFormat": "API_KEY",
+        "description": "API Key authentication. For all API requests, include your API Key in the `Authorization` HTTP Header, prefixed with 'Bearer '. Example: `Authorization: Bearer {API_KEY}`. **Strongly recommend storing your API Key on the server-side, not shared or stored on the client-side, to avoid possible API-Key leakage that can lead to serious consequences.**"
       }
     },
     "responses": {
diff --git a/ja-jp/openapi_knowledge.json b/ja-jp/openapi_knowledge.json
index 10b84d7f..3428d6db 100644
--- a/ja-jp/openapi_knowledge.json
+++ b/ja-jp/openapi_knowledge.json
@@ -1711,7 +1711,8 @@
       "ApiKeyAuth": {
         "type": "http",
         "scheme": "bearer",
-        "description": "APIキー認証。'Authorization'ヘッダーに'Bearer {API_KEY}'形式でキーを提供してください。"
+        "bearerFormat": "API_KEY",
+        "description": "APIキー認証。すべてのAPIリクエストにおいて、Authorization HTTPヘッダーにAPIキーを含めてください。形式：Bearer {API_KEY}。**APIキーの漏洩を防ぐため、APIキーはクライアント側で共有または保存せず、サーバー側で保存することを強くお勧めします。**"
       }
     },
     "responses": {
diff --git a/zh-hans/openapi_knowledge.json b/zh-hans/openapi_knowledge.json
index 8fd80233..114d3cac 100644
--- a/zh-hans/openapi_knowledge.json
+++ b/zh-hans/openapi_knowledge.json
@@ -1711,7 +1711,8 @@
       "ApiKeyAuth": {
         "type": "http",
         "scheme": "bearer",
-        "description": "API 密钥身份验证。在 'Authorization' 标头中以 'Bearer {API_KEY}' 格式提供密钥。"
+        "bearerFormat": "API_KEY",
+        "description": "API-Key 鉴权。所有 API 请求都应在 `Authorization` HTTP Header 中包含您的 API-Key，格式为 `Bearer {API_KEY}`。**强烈建议开发者把 API-Key 放在后端存储，而非分享或者放在客户端存储，以免 API-Key 泄露，导致财产损失。**"
       }
     },
     "responses": {