@techysy/10router 1.3.3 → 1.3.5

package/app/public/i18n/literals/zh-CN.json

@@ -1272,6 +1272,7 @@
   "Under": "在",
   "Unified Endpoint": "统一端点",
   "Unknown": "未知",
+  "Partial": "部分受限",
   "Unauthorized": "会话已过期或无访问权限，请重新登录后重试",
   "Unselect all": "取消选择全部",
   "Update": "更新",
@@ -1760,6 +1761,7 @@
   "Last 7 days": "最近 7 天",
   "Last 7 days (≥50 real requests)": "最近 7 天（≥50 次真实有效请求）",
   "Individual quota reached. Resets at {time} (in {duration}).": "该账号额度已用完，将于 {time} 重置（约 {duration} 后）；可升级订阅提升限额。",
+  "Individual quota reached for model {model}. Resets at {time} (in {duration}).": "模型 {model} 的额度已用完，将于 {time} 重置（约 {duration} 后）；该账号的其它模型仍可正常使用。",
   "Subscription quota used up. Please wait for the quota reset.": "该账号额度已用完，请等待重置。",
   "Retry on empty": "空回复时切换",
   "When the model returns an empty answer (content filter or zero output), fall through to the next model. The abandoned attempt still consumes its input tokens.": "当模型返回空回复（内容审查或零输出）时，自动改用下一个模型。被放弃的调用仍会消耗其输入 token。",
@@ -2001,5 +2003,9 @@
   "Local: enable the gateway switch under \"MiniMax → Interface settings\" in CreditDaddy desktop and add a MiniMax account (default 127.0.0.1:47860).": "本机：在 CreditDaddy 桌面版「MiniMax → 接口设置」里开启网关开关并添加 MiniMax 账号（默认 127.0.0.1:47860）。",
   "Local: enable the gateway switch under \"ZCode → Interface settings\" in CreditDaddy desktop (default 127.0.0.1:47860).": "本机：在 CreditDaddy 桌面版「ZCode → 接口设置」里开启网关开关（默认 127.0.0.1:47860）。",
   "LAN (NAS, etc.): put the CreditDaddy machine IP above, then in the same CreditDaddy panel turn on \"Allow LAN access\" and add this 10Router machine's IP to the allowlist, then restart CreditDaddy.": "局域网（NAS 等）：在上方填 CreditDaddy 所在机器的 IP，再在同一面板里打开「允许局域网访问」并把本 10Router 机器的 IP 加入白名单，然后重启 CreditDaddy。",
-  "The gateway is protected by an IP allowlist and checks no key, so there is nothing to enter here.": "网关由 IP 白名单保护、不校验任何 key，所以这里无需填凭据。"
+  "The gateway is protected by an IP allowlist and checks no key, so there is nothing to enter here.": "网关由 IP 白名单保护、不校验任何 key，所以这里无需填凭据。",
+  "Getting a 404? The path must keep its brand segment (e.g. /gateway/zcode/v1/messages) — CreditDaddy serves only the branded endpoints, and a build older than the rename still serves the old /gateway/v1/messages, so upgrade CreditDaddy rather than editing this field.": "遇到 404？路径必须保留品牌段（如 /gateway/zcode/v1/messages）——CreditDaddy 只提供带品牌名的端点；重命名之前的旧版本仍只提供 /gateway/v1/messages，所以请升级 CreditDaddy，而不是改这个输入框。",
+  "Synced CreditDaddy web session expired — plan credits may read low or missing. Re-export the account from CreditDaddy after logging in to Qoder web again.": "已同步的 CreditDaddy 网页会话已失效——套餐积分可能显示偏低或缺失。请在 CreditDaddy 重新登录 Qoder 网页后再次导出导入。",
+  "Web session check failed for": "以下账号的网页会话校验失败：",
+  "Web sessions verified": "网页会话校验通过"
 }

package/app/public/i18n/literals/zh-TW.json

@@ -585,6 +585,7 @@
   "Last 7 days": "最近 7 天",
   "Last 7 days (≥50 real requests)": "最近 7 天（≥50 次真實有效請求）",
   "Individual quota reached. Resets at {time} (in {duration}).": "該帳號額度已用完，將於 {time} 重置（約 {duration} 後）；可升級訂閱提升限額。",
+  "Individual quota reached for model {model}. Resets at {time} (in {duration}).": "模型 {model} 的額度已用完，將於 {time} 重置（約 {duration} 後）；該帳號的其它模型仍可正常使用。",
   "Subscription quota used up. Please wait for the quota reset.": "該帳號額度已用完，請等待重置。",
   "Retry on empty": "空回覆時切換",
   "When the model returns an empty answer (content filter or zero output), fall through to the next model. The abandoned attempt still consumes its input tokens.": "當模型返回空回覆（內容審查或零輸出）時，自動改用下一個模型。被放棄的呼叫仍會消耗其輸入 token。",
@@ -657,6 +658,7 @@
   "This machine only": "僅本機",
   "Anyone who can reach the port": "任何能存取該連接埠的人",
   "Unknown": "未知",
+  "Partial": "部分受限",
   "Anyone who can reach the port and knows the password": "任何能存取該連接埠且知道密碼的人",
   "Remote access to the dashboard stays disabled until a password is set. Set the first password on the machine running 10Router (open http://127.0.0.1:20128 there), or start it with the INITIAL_PASSWORD environment variable.": "在設定密碼之前，儀表板的遠端存取維持關閉。請在執行 10Router 的機器上設定第一個密碼（在該機開啟 http://127.0.0.1:20128），或以 INITIAL_PASSWORD 環境變數啟動。",
   "No password is set yet, so the dashboard opens on this machine only. Set a password on the Settings page to reach it from other devices. The gateway API (/v1) is unaffected.": "尚未設定密碼：儀表板目前只能在本機開啟。請在「設定」頁設定一組密碼，即可從其它裝置存取；閘道介面（/v1）不受影響。",
@@ -844,5 +846,9 @@
   "Local: enable the gateway switch under \"MiniMax → Interface settings\" in CreditDaddy desktop and add a MiniMax account (default 127.0.0.1:47860).": "本機：在 CreditDaddy 桌面版「MiniMax → 介面設定」裡開啟閘道開關並新增 MiniMax 帳號（預設 127.0.0.1:47860）。",
   "Local: enable the gateway switch under \"ZCode → Interface settings\" in CreditDaddy desktop (default 127.0.0.1:47860).": "本機：在 CreditDaddy 桌面版「ZCode → 介面設定」裡開啟閘道開關（預設 127.0.0.1:47860）。",
   "LAN (NAS, etc.): put the CreditDaddy machine IP above, then in the same CreditDaddy panel turn on \"Allow LAN access\" and add this 10Router machine's IP to the allowlist, then restart CreditDaddy.": "區網（NAS 等）：在上方填 CreditDaddy 所在機器的 IP，再在同一面板裡開啟「允許區網存取」並把本 10Router 機器的 IP 加入白名單，然後重新啟動 CreditDaddy。",
-  "The gateway is protected by an IP allowlist and checks no key, so there is nothing to enter here.": "閘道由 IP 白名單保護、不驗證任何 key，所以這裡無需填憑證。"
+  "The gateway is protected by an IP allowlist and checks no key, so there is nothing to enter here.": "閘道由 IP 白名單保護、不驗證任何 key，所以這裡無需填憑證。",
+  "Getting a 404? The path must keep its brand segment (e.g. /gateway/zcode/v1/messages) — CreditDaddy serves only the branded endpoints, and a build older than the rename still serves the old /gateway/v1/messages, so upgrade CreditDaddy rather than editing this field.": "遇到 404？路徑必須保留品牌段（如 /gateway/zcode/v1/messages）——CreditDaddy 只提供帶品牌名的端點；重新命名之前的舊版本仍只提供 /gateway/v1/messages，所以請升級 CreditDaddy，而不是改這個輸入框。",
+  "Synced CreditDaddy web session expired — plan credits may read low or missing. Re-export the account from CreditDaddy after logging in to Qoder web again.": "已同步的 CreditDaddy 網頁工作階段已失效——套餐積分可能顯示偏低或缺失。請在 CreditDaddy 重新登入 Qoder 網頁後再次匯出匯入。",
+  "Web session check failed for": "以下帳號的網頁工作階段校驗失敗：",
+  "Web sessions verified": "網頁工作階段校驗通過"
 }

package/package.json

@@ -1,61 +1,61 @@
-{
-  "name": "@techysy/10router",
-  "version": "1.3.3",
-  "description": "10Router CLI - Start and manage 10Router server",
-  "publishConfig": {
-    "access": "public"
-  },
-  "bin": {
-    "10router": "./cli.js"
-  },
-  "files": [
-    "cli.js",
-    "src",
-    "hooks",
-    "app",
-    "README.md",
-    "LICENSE"
-  ],
-  "scripts": {
-    "dev": "nodemon -I --watch cli.js --watch src --watch hooks --ext js,json cli.js",
-    "build": "node scripts/build-cli.js",
-    "pack:cli": "npm run build && npm pack --pack-destination ..",
-    "publish:cli": "npm run build && npm publish --registry https://registry.npmjs.org",
-    "postinstall": "node hooks/postinstall.js || exit 0",
-    "prepublishOnly": "npm run build"
-  },
-  "dependencies": {
-    "enquirer": "^2.4.1",
-    "node-forge": "^1.3.3",
-    "node-machine-id": "^1.1.12",
-    "react": "19.2.1",
-    "react-dom": "19.2.1"
-  },
-  "comment_postinstall": "`|| exit 0` is deliberate: this hook only warms ~/.10router/runtime, and cli.js re-runs the same ensureSqliteRuntime/ensureTrayRuntime on every start, so a failure here costs nothing. Without it npm aborts the whole install — e.g. running Windows npm against a WSL path, where cmd.exe cannot cd to a UNC directory, falls back to C:\\Windows and node then cannot find hooks/postinstall.js at all, so the script's own try/catch never gets to run.",
-  "comment_sqlite": "sql.js + better-sqlite3 are NOT bundled here. They are installed into ~/.10router/runtime/node_modules by hooks/postinstall.js (and re-checked at runtime by cli.js). This avoids Windows EBUSY errors when updating the global CLI, since native .node files no longer live under the locked install dir. Both runtime deps are installed WITH save (never --no-save): the runtime dir is a single shared npm project, so a package found in node_modules but missing from runtime/package.json is pruned as extraneous by the other hook's next install, and the two hooks would otherwise uninstall each other in a ping-pong.",
-  "comment_systray": "systray2 is NOT bundled here. It is lazy-installed into ~/.10router/runtime/node_modules by hooks/postinstall.js on macOS/Linux only. Windows uses PowerShell NotifyIcon (zero binary). This avoids shipping unsigned Go binaries that trigger antivirus false positives (Kaspersky). We use the systray2 fork because the legacy systray@1.0.5 ships a 2017 x86_64 binary that fails on modern macOS dyld.",
-  "engines": {
-    "node": ">=18.0.0"
-  },
-  "keywords": [
-    "10router",
-    "cli",
-    "proxy",
-    "ai",
-    "api"
-  ],
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/techysy/10router.git",
-    "directory": "cli"
-  },
-  "homepage": "https://github.com/techysy/10router#readme",
-  "bugs": {
-    "url": "https://github.com/techysy/10router/issues"
-  },
-  "devDependencies": {
-    "esbuild": "^0.25.12",
-    "nodemon": "^3.1.14"
-  }
-}
+{
+  "name": "@techysy/10router",
+  "version": "1.3.5",
+  "description": "10Router CLI - Start and manage 10Router server",
+  "publishConfig": {
+    "access": "public"
+  },
+  "bin": {
+    "10router": "./cli.js"
+  },
+  "files": [
+    "cli.js",
+    "src",
+    "hooks",
+    "app",
+    "README.md",
+    "LICENSE"
+  ],
+  "scripts": {
+    "dev": "nodemon -I --watch cli.js --watch src --watch hooks --ext js,json cli.js",
+    "build": "node scripts/build-cli.js",
+    "pack:cli": "npm run build && npm pack --pack-destination ..",
+    "publish:cli": "npm run build && npm publish --registry https://registry.npmjs.org",
+    "postinstall": "node hooks/postinstall.js || exit 0",
+    "prepublishOnly": "npm run build"
+  },
+  "dependencies": {
+    "enquirer": "^2.4.1",
+    "node-forge": "^1.3.3",
+    "node-machine-id": "^1.1.12",
+    "react": "19.2.1",
+    "react-dom": "19.2.1"
+  },
+  "comment_postinstall": "`|| exit 0` is deliberate: this hook only warms ~/.10router/runtime, and cli.js re-runs the same ensureSqliteRuntime/ensureTrayRuntime on every start, so a failure here costs nothing. Without it npm aborts the whole install — e.g. running Windows npm against a WSL path, where cmd.exe cannot cd to a UNC directory, falls back to C:\\Windows and node then cannot find hooks/postinstall.js at all, so the script's own try/catch never gets to run.",
+  "comment_sqlite": "sql.js + better-sqlite3 are NOT bundled here. They are installed into ~/.10router/runtime/node_modules by hooks/postinstall.js (and re-checked at runtime by cli.js). This avoids Windows EBUSY errors when updating the global CLI, since native .node files no longer live under the locked install dir. Both runtime deps are installed WITH save (never --no-save): the runtime dir is a single shared npm project, so a package found in node_modules but missing from runtime/package.json is pruned as extraneous by the other hook's next install, and the two hooks would otherwise uninstall each other in a ping-pong.",
+  "comment_systray": "systray2 is NOT bundled here. It is lazy-installed into ~/.10router/runtime/node_modules by hooks/postinstall.js on macOS/Linux only. Windows uses PowerShell NotifyIcon (zero binary). This avoids shipping unsigned Go binaries that trigger antivirus false positives (Kaspersky). We use the systray2 fork because the legacy systray@1.0.5 ships a 2017 x86_64 binary that fails on modern macOS dyld.",
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "keywords": [
+    "10router",
+    "cli",
+    "proxy",
+    "ai",
+    "api"
+  ],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/techysy/10router.git",
+    "directory": "cli"
+  },
+  "homepage": "https://github.com/techysy/10router#readme",
+  "bugs": {
+    "url": "https://github.com/techysy/10router/issues"
+  },
+  "devDependencies": {
+    "esbuild": "^0.25.12",
+    "nodemon": "^3.1.14"
+  }
+}