cli-wechat-bridge 1.1.0 → 1.1.2

package/dist/bridge/claude-hooks.js

@@ -1,4 +1,4 @@
-import { WECHAT_OUTBOUND_ATTACHMENT_DENY_MESSAGE, containsWechatOutboundAttachmentPath, isHighRiskShellCommand, isWechatOutboundAttachmentWriteCommand, normalizeOutput, truncatePreview, } from "./bridge-utils.js";
+import { WECHAT_OUTBOUND_ATTACHMENT_DENY_MESSAGE, containsWechatOutboundAttachmentPath, isHighRiskShellCommand, isStrictApprovalModeEnabled, isWechatOutboundAttachmentWriteCommand, normalizeOutput, truncatePreview, } from "./bridge-utils.js";
 export const CLAUDE_WECHAT_OUTBOUND_ATTACHMENT_DENY_MESSAGE = WECHAT_OUTBOUND_ATTACHMENT_DENY_MESSAGE;
 const FILE_MUTATION_TOOL_NAMES = new Set([
     "Write",
@@ -88,6 +88,11 @@ export function buildClaudeHookScript(params) {
         return [
             "@echo off",
             "setlocal",
+            // The script is written as UTF-8, but cmd.exe decodes batch lines with
+            // the active OEM code page (GBK on zh-CN systems). Paths below may
+            // contain non-ASCII characters (e.g. a Chinese Windows user name), so
+            // switch to UTF-8 before any line that embeds a path.
+            "chcp 65001>nul",
             `set "CLAUDE_WECHAT_HOOK_PORT=${params.hookPort}"`,
             `set "CLAUDE_WECHAT_HOOK_TOKEN=${params.hookToken}"`,
             `${command} ${stderrRedirect}`,
@@ -205,7 +210,10 @@ export function getClaudeWechatOutboundAttachmentDenyMessage(payload) {
     }
     return null;
 }
-export function getClaudePermissionAutoResponse(payload) {
+export function getClaudePermissionAutoResponse(payload, env = process.env) {
+    if (isStrictApprovalModeEnabled(env)) {
+        return null;
+    }
     const toolName = typeof payload.tool_name === "string" ? payload.tool_name.trim() : "";
     if (!toolName) {
         return null;

package/dist/bridge/wechat-bridge.js

@@ -242,6 +242,11 @@ function printUsageAndExit() {
     process.exit(0);
 }
 async function main() {
+    if (process.argv.includes("--doctor")) {
+        const { runDoctorCheck } = await import("../utils/doctor.js");
+        await runDoctorCheck(process.argv.slice(2), { mode: "bridge" });
+        process.exit(0);
+    }
     const options = parseCliArgs(process.argv.slice(2));
     const daemonEndpoint = readDaemonEndpoint();
     if (daemonEndpoint && await isDaemonEndpointAlive(daemonEndpoint, { timeoutMs: 500 })) {
@@ -261,7 +266,9 @@ async function main() {
     }
     const transport = new WeChatTransport({ log, logError });
     // 非阻塞地检查更新（不影响启动速度，也避免首次登录时打断二维码输出）
-    setTimeout(async () => {
+    // unref：不能让这个延迟检查把 event loop 挂活（如 --doctor 或快速退出场景），
+    // 否则会与强制退出 teardown 竞态。
+    const updateCheckTimer = setTimeout(async () => {
         try {
             const versionInfo = await checkForUpdate();
             if (versionInfo?.hasUpdate) {
@@ -272,6 +279,7 @@ async function main() {
             // 静默失败，不影响正常使用
         }
     }, 3000); // 延迟3秒，确保不影响启动
+    updateCheckTimer.unref?.();
     const stateStore = new BridgeStateStore({
         ...options,
         authorizedUserId: credentials.userId,
@@ -333,6 +341,7 @@ async function main() {
     let lastOutputAt = 0;
     let lastHeartbeatAt = 0;
     let consecutivePollFailures = 0;
+    let backlogNoticeSent = false;
     const queueWechatTextAction = (action) => {
         const run = textSendChain.then(action);
         textSendChain = run.then(() => undefined, () => undefined);
@@ -656,6 +665,13 @@ async function main() {
             if (pollResult.ignoredBacklogCount > 0) {
                 stateStore.incrementIgnoredBacklog(pollResult.ignoredBacklogCount);
                 stateStore.appendLog(`ignored_startup_backlog: count=${pollResult.ignoredBacklogCount}`);
+                if (!backlogNoticeSent) {
+                    backlogNoticeSent = true;
+                    await queueWechatMessage(stateStore.getState().authorizedUserId, t("bridge.backlogIgnored", {
+                        count: pollResult.ignoredBacklogCount,
+                        graceSeconds: Math.round(MESSAGE_START_GRACE_MS / 1000),
+                    }), "notice");
+                }
             }
             for (const message of pollResult.messages) {
                 if (!ensureRuntimeOwnership()) {

package/dist/commands/check-update.js

@@ -7,12 +7,23 @@ async function main() {
     console.log(`Checking for updates...`);
     const versionInfo = await checkForUpdate(true); // 强制检查
     if (!versionInfo) {
-        console.log(`ERROR: Unable to check for updates, please check your network connection`);
-        process.exit(1);
+        console.error(`ERROR: Unable to check for updates.`);
+        console.error(`Could not read the latest version from the npm registry or GitHub.`);
+        console.error(`Possible causes:`);
+        console.error(`  - No network connection`);
+        console.error(`  - A proxy is required but not configured (set HTTP_PROXY/HTTPS_PROXY and NODE_USE_ENV_PROXY=1)`);
+        console.error(`  - The npm registry or GitHub API are temporarily unavailable`);
+        console.error(`\nCheck the latest release manually:`);
+        console.error(`  https://github.com/UNLINEARITY/CLI-WeChat-Bridge/releases`);
+        // 不使用 process.exit():强制退出会打断 fetch 底层 handle 的关闭流程,
+        // 在 Windows + Node 24 上触发 libuv 的 UV_HANDLE_CLOSING 断言崩溃。
+        // 设置 exitCode 后让事件循环自然退出。
+        process.exitCode = 1;
+        return;
     }
     if (!versionInfo.hasUpdate) {
         console.log(`OK: Already up to date (v${versionInfo.latest})`);
-        process.exit(0);
+        return;
     }
     console.log(`[New Version Available] v${versionInfo.latest}`);
     console.log(`Current version: v${versionInfo.current}\n`);
@@ -26,5 +37,5 @@ async function main() {
 }
 main().catch((error) => {
     console.error(`Error checking for updates: ${error.message}`);
-    process.exit(1);
+    process.exitCode = 1;
 });

package/dist/companion/local-companion-start.js

@@ -283,6 +283,11 @@ function startBridgeInBackground(options) {
         stdio: "ignore",
         windowsHide: true,
     });
+    // A detached background spawn must still handle its own 'error' event
+    // (e.g. ENOENT), otherwise it surfaces as an unhandled exception.
+    child.on("error", () => {
+        /* best effort: background bridge failed to detach */
+    });
     child.unref();
 }
 async function waitForEndpoint(cwd, adapter, timeoutMs) {

package/dist/daemon/wechat-daemon.js

@@ -13,7 +13,7 @@ import { readBridgeLockFile, } from "../bridge/bridge-state.js";
 import { getProcessRecordByPid, isWechatDaemonCommandLine, killProcessTreeSync, listWechatDaemonProcesses, reapOrphanedOpencodeProcesses, reapPeerBridgeProcesses, } from "../bridge/bridge-process-reaper.js";
 import { buildOneTimeCode, buildWechatInboundPrompt, formatApprovalMessage, formatDuration, formatMirroredUserInputMessage, formatPendingApprovalReminder, formatPendingUserInputReminder, formatSessionSwitchMessage, formatTaskFailedMessage, formatUserInputRequestMessage, MESSAGE_START_GRACE_MS, nowIso, OutputBatcher, parsePendingUserInputAnswerCommand, parseWechatControlCommand, truncatePreview, } from "../bridge/bridge-utils.js";
 import { formatUserFacingBridgeFatalError, formatUserFacingInboundError, formatWechatContextTokenStaleLogEntry, formatWechatSendFailureLogEntry, isRetryableWechatSendError, shouldForwardBridgeEventToWechat, } from "../bridge/wechat-bridge.js";
-import { BRIDGE_LOCK_FILE, BRIDGE_LOG_FILE, ensureChannelDataDir, migrateLegacyChannelFiles, } from "../wechat/channel-config.js";
+import { BRIDGE_LOCK_FILE, BRIDGE_LOG_FILE, appendBoundedLog, ensureChannelDataDir, migrateLegacyChannelFiles, } from "../wechat/channel-config.js";
 import { ensureWechatCredentials } from "../wechat/setup.js";
 import { formatBindCommandUsage, formatBindingsListMessage, isBindCommandPrefix, listBindings, loadEmojiBindings, parseEmojiBindingsCommand, removeBinding, resolveEmojiCommand, setBinding, } from "./emoji-bindings.js";
 import { classifyWechatTransportError, DEFAULT_LONG_POLL_TIMEOUT_MS, describeWechatTransportError, isWechatContextTokenStaleError, WeChatTransport, } from "../wechat/wechat-transport.js";
@@ -45,7 +45,7 @@ function logError(message) {
 }
 function appendDaemonLog(message) {
     ensureChannelDataDir();
-    fs.appendFileSync(BRIDGE_LOG_FILE, `[${new Date().toISOString()}] daemon: ${message}\n`, "utf8");
+    appendBoundedLog(BRIDGE_LOG_FILE, `[${new Date().toISOString()}] daemon: ${message}\n`);
 }
 function computePollRetryDelayMs(consecutiveFailures) {
     const normalizedFailures = Math.max(1, consecutiveFailures);
@@ -444,6 +444,7 @@ class WechatDaemon {
     slots = new Map();
     startedAt = new Date().toISOString();
     bridgeStartedAtMs = Date.now();
+    backlogNoticeSent = false;
     activeAdapter = null;
     takenOverAdapter;
     textSendChain = Promise.resolve();
@@ -582,6 +583,13 @@ class WechatDaemon {
             }
             if (pollResult.ignoredBacklogCount > 0) {
                 appendDaemonLog(`ignored_startup_backlog: count=${pollResult.ignoredBacklogCount}`);
+                if (!this.backlogNoticeSent) {
+                    this.backlogNoticeSent = true;
+                    await this.queueWechatMessage(this.authorizedUserId, t("bridge.backlogIgnored", {
+                        count: pollResult.ignoredBacklogCount,
+                        graceSeconds: Math.round(MESSAGE_START_GRACE_MS / 1000),
+                    }), "notice");
+                }
             }
             for (const message of pollResult.messages) {
                 try {
@@ -1580,6 +1588,11 @@ export async function runDaemon(options) {
     await daemon.runPollLoop();
 }
 export async function main(argv = process.argv.slice(2)) {
+    if (argv.includes("--doctor")) {
+        const { runDoctorCheck } = await import("../utils/doctor.js");
+        await runDoctorCheck(argv, { mode: "daemon" });
+        process.exit(0);
+    }
     try {
         await runDaemon(parseDaemonCliArgs(argv));
     }

package/dist/i18n/messages-en.js

@@ -9,6 +9,7 @@ export const messages = {
     "bridge.status.busy": "{adapter} is still working on the previous request. Wait for it to finish or send /interrupt.",
     "bridge.newSession.done": "New session started.",
     "bridge.fatalError": "Bridge error: {message}",
+    "bridge.backlogIgnored": "Ignored {count} backlog message(s) sent before the bridge started (they will not be processed).\nIf you actually sent them after the bridge started, your system clock is likely skewed by more than {graceSeconds}s — sync the clock and restart the bridge.",
     // === Daemon welcome & control ===
     "daemon.welcome": "WeChat Daemon ready.\nCWD: {cwd}\nActive: {adapter}\n\nCommands: /claude, /codex, /opencode, /stop, /confirm, /deny, /status\n{bindings}\n\nManage: /bind [emoji] cmd, /unbind [emoji], /bindings",
     "daemon.noActiveAdapter": "No active terminal is selected. Send /codex, /claude, or /opencode to start one.",
@@ -26,16 +27,17 @@ export const messages = {
     "hook.healthCheck.logHint": "\nCheck: {logPath}",
     "hook.healthCheck.fixes": "\nCommon fixes:\n- Ensure Node.js >= 22.6.0: node --version\n- Reinstall: npm install -g cli-wechat-bridge@latest\n- Check firewall: allow localhost TCP connections",
     // === PTY fallback ===
-    "pty.fallback.warning": "[Warning] PTY unavailable, using fallback mode. Terminal rendering may be degraded.\n",
+    "pty.fallback.warning": "[Warning] PTY unavailable — using fallback mode (TERM=dumb).\nCore features (messaging, approvals, session management) work normally; terminal rendering (colors, progress bars) may be degraded.\nFix: Linux install build-essential python3 | Windows run npm rebuild node-pty | macOS run xcode-select --install\nRun --doctor for detailed environment info.\n",
     // === Spawn diagnostic ===
     "spawn.diagnostic.title": "Failed to start CLI process: {target}\nError: {error}",
     "spawn.diagnostic.fixesHeader": "\nPossible fixes:",
     "spawn.diagnostic.nodePty": "- The node-pty native module is incompatible with your Node.js version.\n- Run: npm rebuild node-pty\n- Or reinstall: npm install -g cli-wechat-bridge@latest",
     "spawn.diagnostic.xcode": "- Ensure Xcode CLI tools are installed: xcode-select --install",
+    "spawn.diagnostic.linuxBuildTools": "- Linux requires build tools for node-pty: sudo apt install build-essential python3\n- Then reinstall: npm install -g cli-wechat-bridge@latest",
     "spawn.diagnostic.notFound": "- The command \"{target}\" was not found on PATH.\n- Verify it is installed and accessible from your terminal.",
     "spawn.diagnostic.generic": "- Reinstall: npm install -g cli-wechat-bridge@latest",
     "spawn.diagnostic.nodeVersion": "- Ensure Node.js >= 22.6.0: node --version",
-    "spawn.diagnostic.winAdmin": "- If using ConPTY, try running as Administrator.",
+    "spawn.diagnostic.winFull": "- Ensure Windows 10 build 18309+ (run 'winver' to check)\n- Install Visual C++ Redistributable: https://aka.ms/vs/17/release/vc_redist.x64.exe\n- Run: npm rebuild node-pty\n- Try running as Administrator",
     // === Emoji bindings ===
     "binding.usage": "Invalid format.\nUsage: /bind [emoji] command\nExample: /bind 🚀 deploy --prod",
     "binding.bound": "Bound {emoji} → {command}",
@@ -45,4 +47,89 @@ export const messages = {
     "binding.listHeader": "Emoji bindings:",
     // === Version checker ===
     "update.available": "[Update Available] Version {latest} is available (current: {current}).\nRun: npm install -g cli-wechat-bridge@latest",
+    // === Doctor ===
+    "doctor.title": "CLI WeChat Bridge Doctor",
+    "doctor.section.environment": "Environment",
+    "doctor.section.adapterCli": "Adapter commands",
+    "doctor.section.data": "Data",
+    "doctor.section.runtime": "Runtime",
+    "doctor.label.node": "Node.js",
+    "doctor.label.platform": "Platform",
+    "doctor.label.winBuild": "Windows build",
+    "doctor.label.codePage": "Console code page",
+    "doctor.codePage.nonAsciiWarning": "{codePage} (not UTF-8 and the data directory path contains non-ASCII characters; hook scripts from older versions break in this environment — upgrade to the latest release)",
+    "doctor.label.connectivity": "WeChat connectivity",
+    "doctor.connectivity.ok": "reachable ({baseUrl})",
+    "doctor.connectivity.unreachable": "cannot reach {baseUrl} (check network and firewall)",
+    "doctor.connectivity.proxyHint": "cannot reach {baseUrl}. Proxy {proxy} detected, but Node fetch ignores proxy environment variables by default; if your network requires the proxy, set NODE_USE_ENV_PROXY=1 and retry.",
+    "doctor.label.clock": "System clock",
+    "doctor.clock.ok": "~{skewSeconds}s skew vs server time",
+    "doctor.clock.skewWarning": "~{skewSeconds}s skew vs server time (large skew makes the bridge treat fresh messages as pre-start backlog — sync the system clock)",
+    "doctor.label.nodePty": "node-pty",
+    "doctor.label.shell": "shell",
+    "doctor.label.dataDir": "Data dir",
+    "doctor.label.credentials": "Credentials",
+    "doctor.label.mode": "Mode",
+    "doctor.label.cwd": "Cwd",
+    "doctor.label.adapter": "Adapter",
+    "doctor.label.daemon": "Daemon",
+    "doctor.label.bridgeLock": "Bridge lock",
+    "doctor.label.workspaceEndpoint": "Workspace endpoint ({adapter})",
+    "doctor.label.legacyEndpoint": "Legacy endpoint",
+    "doctor.winBuildConpty": "(ConPTY requires build 18309+)",
+    "doctor.nodePty.loaded": "loaded",
+    "doctor.nodePty.fix": "Fix: {fix}",
+    "doctor.adapterCli.shellNative": "uses the local shell; no other adapter CLI is checked.",
+    "doctor.adapterCli.notFound": "not found{optional}",
+    "doctor.dataDirMissing": "(will be created on first run)",
+    "doctor.credentialsFound": "found",
+    "doctor.credentialsMissing": "not found (run wechat-setup first)",
+    "doctor.mode.bridge": "standalone bridge",
+    "doctor.mode.generic": "generic",
+    "doctor.notSpecified": "(not specified)",
+    "doctor.none": "none",
+    "doctor.unknown": "unknown",
+    "doctor.yes": "yes",
+    "doctor.no": "no",
+    "doctor.optional": "(optional)",
+    "doctor.invalidShape": "unexpected file shape",
+    "doctor.file": "File: {file}",
+    "doctor.issue": "Issue: {issue}.",
+    "doctor.daemon.invalid": "invalid endpoint file ({error})",
+    "doctor.daemon.stale": "stale endpoint pid={pid} cwd={cwd} port={port}",
+    "doctor.daemon.staleStartup": "Startup: bridge and daemon startup paths will clear stale daemon endpoint state before continuing.",
+    "doctor.daemon.live": "live pid={pid} cwd={cwd} port={port}",
+    "doctor.daemon.liveBridgeStartup": "Startup: standalone bridge will refuse to start while this daemon is live.",
+    "doctor.daemon.liveDaemonStartup": "Startup: daemon startup will request shutdown of this daemon before binding.",
+    "doctor.lock.invalid": "invalid lock file ({error})",
+    "doctor.lock.stale": "stale",
+    "doctor.lock.staleDaemonStartup": "daemon startup will clear this stale single-bridge lock.",
+    "doctor.lock.staleBridgeStartup": "the next standalone bridge start will replace this stale lock.",
+    "doctor.lock.reclaimable": "reclaimable",
+    "doctor.lock.parent": "pid={pid} alive={alive}",
+    "doctor.lock.detail.pid": "pid",
+    "doctor.lock.detail.adapter": "adapter",
+    "doctor.lock.detail.cwd": "cwd",
+    "doctor.lock.detail.lifecycle": "lifecycle",
+    "doctor.lock.detail.startedAt": "started at",
+    "doctor.lock.detail.parent": "parent",
+    "doctor.lock.detail.startup": "startup",
+    "doctor.lock.detail.note": "note",
+    "doctor.lock.reclaimableDaemonStartup": "daemon startup will stop or clear this orphaned single bridge before continuing.",
+    "doctor.lock.reclaimableBridgeStartup": "standalone bridge startup can reclaim this companion-bound or legacy lock because its parent is gone.",
+    "doctor.lock.live": "live",
+    "doctor.lock.liveDaemonStartup": "daemon startup will stop this single bridge before continuing.",
+    "doctor.lock.liveBridgeStartup": "standalone bridge will fail with a lock conflict until this process exits.",
+    "doctor.lock.cwdDifferent": "lock cwd differs from requested cwd ({cwd}); single-bridge lock is global.",
+    "doctor.lock.adapterDifferent": "lock adapter={lockAdapter} differs from requested adapter={requestedAdapter}.",
+    "doctor.endpoint.legacySame": "same as adapter endpoint",
+    "doctor.endpoint.summary": "instance={instanceId} kind={kind} port={port} reachable={reachable}",
+    "doctor.endpoint.owner": "ownerPid={ownerPid} ownerAlive={ownerAlive} companionPid={companionPid} companionAlive={companionAlive} status={status}",
+    "doctor.endpoint.issue.kind": "endpoint kind={kind} differs from requested adapter={adapter}",
+    "doctor.endpoint.issue.cwd": "endpoint cwd differs from requested cwd ({cwd})",
+    "doctor.endpoint.issue.port": "endpoint port {port} is not reachable",
+    "doctor.endpoint.issue.ownerDead": "bridge owner pid={pid} is dead",
+    "doctor.endpoint.issue.companionDead": "companion pid={pid} is dead",
+    "doctor.endpoint.issue.workerStatus": "visible worker status={status}",
+    "doctor.endpoint.issue.instanceMismatch": "endpoint instanceId does not match bridge lock instanceId",
 };

package/dist/i18n/messages-zh.js

@@ -9,6 +9,7 @@ export const messages = {
     "bridge.status.busy": "{adapter} 仍在处理上一个请求。请等待完成或发送 /interrupt。",
     "bridge.newSession.done": "已开始新会话。",
     "bridge.fatalError": "桥接错误: {message}",
+    "bridge.backlogIgnored": "已忽略 {count} 条桥接启动前的积压消息（不会自动处理）。\n如果你是在桥接启动后才发送的消息却看到此提示，说明本机系统时钟可能不准（偏差超过 {graceSeconds} 秒），请校准时间后重启桥接。",
     // === Daemon 欢迎 & 控制 ===
     "daemon.welcome": "微信 Daemon 就绪。\n工作目录: {cwd}\n当前: {adapter}\n\n命令: /claude, /codex, /opencode, /stop, /confirm, /deny, /status\n{bindings}\n\n管理: /bind [表情] 命令, /unbind [表情], /bindings",
     "daemon.noActiveAdapter": "未选择活跃终端。发送 /codex、/claude 或 /opencode 启动一个。",
@@ -26,16 +27,17 @@ export const messages = {
     "hook.healthCheck.logHint": "\n查看日志: {logPath}",
     "hook.healthCheck.fixes": "\n常见修复方法:\n- 确保 Node.js >= 22.6.0: node --version\n- 重新安装: npm install -g cli-wechat-bridge@latest\n- 检查防火墙: 允许 localhost TCP 连接",
     // === PTY 回退 ===
-    "pty.fallback.warning": "[警告] PTY 不可用，已切换到回退模式。终端渲染可能受限。\n",
+    "pty.fallback.warning": "[警告] PTY 不可用 — 已切换到回退模式（TERM=dumb）。\n核心功能（消息收发、审批、会话管理）正常工作；终端渲染（颜色、进度条）可能受限。\n修复方法: Linux 安装 build-essential python3 | Windows 运行 npm rebuild node-pty | macOS 运行 xcode-select --install\n运行 --doctor 查看详细环境信息。\n",
     // === 启动诊断 ===
     "spawn.diagnostic.title": "无法启动 CLI 进程: {target}\n错误: {error}",
     "spawn.diagnostic.fixesHeader": "\n可能的修复方法:",
     "spawn.diagnostic.nodePty": "- node-pty 原生模块与当前 Node.js 版本不兼容。\n- 运行: npm rebuild node-pty\n- 或重新安装: npm install -g cli-wechat-bridge@latest",
     "spawn.diagnostic.xcode": "- 确保已安装 Xcode 命令行工具: xcode-select --install",
+    "spawn.diagnostic.linuxBuildTools": "- Linux 需要编译工具来构建 node-pty: sudo apt install build-essential python3\n- 然后重新安装: npm install -g cli-wechat-bridge@latest",
     "spawn.diagnostic.notFound": "- 命令 \"{target}\" 未在 PATH 中找到。\n- 请确认已安装并可从终端访问。",
     "spawn.diagnostic.generic": "- 重新安装: npm install -g cli-wechat-bridge@latest",
     "spawn.diagnostic.nodeVersion": "- 确保 Node.js >= 22.6.0: node --version",
-    "spawn.diagnostic.winAdmin": "- 如使用 ConPTY，请尝试以管理员身份运行。",
+    "spawn.diagnostic.winFull": "- 确保 Windows 10 build 18309+（运行 winver 查看）\n- 安装 Visual C++ Redistributable: https://aka.ms/vs/17/release/vc_redist.x64.exe\n- 运行: npm rebuild node-pty\n- 尝试以管理员身份运行",
     // === Emoji 绑定 ===
     "binding.usage": "格式错误。\n用法: /bind [表情] 命令\n示例: /bind 🚀 deploy --prod",
     "binding.bound": "已绑定 {emoji} → {command}",
@@ -45,4 +47,89 @@ export const messages = {
     "binding.listHeader": "Emoji 绑定列表:",
     // === 版本检查 ===
     "update.available": "[有新版本] 版本 {latest} 可用（当前: {current}）。\n运行: npm install -g cli-wechat-bridge@latest",
+    // === Doctor ===
+    "doctor.title": "CLI WeChat Bridge 诊断",
+    "doctor.section.environment": "环境",
+    "doctor.section.adapterCli": "适配器命令",
+    "doctor.section.data": "数据",
+    "doctor.section.runtime": "运行时",
+    "doctor.label.node": "Node.js",
+    "doctor.label.platform": "平台",
+    "doctor.label.winBuild": "Windows build",
+    "doctor.label.codePage": "控制台代码页",
+    "doctor.codePage.nonAsciiWarning": "{codePage}（非 UTF-8，且数据目录路径含非 ASCII 字符；旧版本的 hook 脚本在此环境下会乱码失效，请升级到最新版本）",
+    "doctor.label.connectivity": "微信服务可达性",
+    "doctor.connectivity.ok": "可达 ({baseUrl})",
+    "doctor.connectivity.unreachable": "无法访问 {baseUrl}（检查网络与防火墙）",
+    "doctor.connectivity.proxyHint": "无法访问 {baseUrl}。检测到代理 {proxy}，但 Node fetch 默认不使用代理环境变量；若必须经代理出网，请设置 NODE_USE_ENV_PROXY=1 后重试。",
+    "doctor.label.clock": "系统时钟",
+    "doctor.clock.ok": "与服务器时间偏差约 {skewSeconds}s",
+    "doctor.clock.skewWarning": "与服务器时间偏差约 {skewSeconds}s（偏差过大会导致桥接启动后的消息被当作积压忽略，请校准系统时间）",
+    "doctor.label.nodePty": "node-pty",
+    "doctor.label.shell": "shell",
+    "doctor.label.dataDir": "数据目录",
+    "doctor.label.credentials": "凭据",
+    "doctor.label.mode": "模式",
+    "doctor.label.cwd": "目录",
+    "doctor.label.adapter": "适配器",
+    "doctor.label.daemon": "守护进程",
+    "doctor.label.bridgeLock": "桥接锁",
+    "doctor.label.workspaceEndpoint": "工作区端点 ({adapter})",
+    "doctor.label.legacyEndpoint": "旧端点",
+    "doctor.winBuildConpty": "(ConPTY 需要 build 18309+)",
+    "doctor.nodePty.loaded": "已加载",
+    "doctor.nodePty.fix": "修复: {fix}",
+    "doctor.adapterCli.shellNative": "使用本机 shell，无需检查其它适配器 CLI。",
+    "doctor.adapterCli.notFound": "未找到{optional}",
+    "doctor.dataDirMissing": "(首次运行会创建)",
+    "doctor.credentialsFound": "已找到",
+    "doctor.credentialsMissing": "未找到 (先运行 wechat-setup)",
+    "doctor.mode.bridge": "独立桥接",
+    "doctor.mode.generic": "通用",
+    "doctor.notSpecified": "(未指定)",
+    "doctor.none": "无",
+    "doctor.unknown": "未知",
+    "doctor.yes": "是",
+    "doctor.no": "否",
+    "doctor.optional": "（可选）",
+    "doctor.invalidShape": "文件结构不符合预期",
+    "doctor.file": "文件: {file}",
+    "doctor.issue": "问题: {issue}。",
+    "doctor.daemon.invalid": "端点文件无效 ({error})",
+    "doctor.daemon.stale": "过期端点 pid={pid} cwd={cwd} port={port}",
+    "doctor.daemon.staleStartup": "启动行为: 桥接和守护进程启动路径会先清理过期守护进程端点。",
+    "doctor.daemon.live": "运行中 pid={pid} cwd={cwd} port={port}",
+    "doctor.daemon.liveBridgeStartup": "启动行为: 守护进程运行中时，独立桥接会拒绝启动。",
+    "doctor.daemon.liveDaemonStartup": "启动行为: 守护进程启动会先请求关闭这个旧守护进程再绑定。",
+    "doctor.lock.invalid": "锁文件无效 ({error})",
+    "doctor.lock.stale": "过期",
+    "doctor.lock.staleDaemonStartup": "守护进程启动会清理这个过期的单桥接锁。",
+    "doctor.lock.staleBridgeStartup": "下次独立桥接启动会替换这个过期锁。",
+    "doctor.lock.reclaimable": "可回收",
+    "doctor.lock.parent": "pid={pid} alive={alive}",
+    "doctor.lock.detail.pid": "pid",
+    "doctor.lock.detail.adapter": "适配器",
+    "doctor.lock.detail.cwd": "目录",
+    "doctor.lock.detail.lifecycle": "生命周期",
+    "doctor.lock.detail.startedAt": "启动时间",
+    "doctor.lock.detail.parent": "父进程",
+    "doctor.lock.detail.startup": "启动行为",
+    "doctor.lock.detail.note": "注意",
+    "doctor.lock.reclaimableDaemonStartup": "守护进程启动会先停止或清理这个孤儿单桥接。",
+    "doctor.lock.reclaimableBridgeStartup": "独立桥接可回收这个父进程已退出的锁。",
+    "doctor.lock.live": "运行中",
+    "doctor.lock.liveDaemonStartup": "守护进程启动会先停止这个单桥接。",
+    "doctor.lock.liveBridgeStartup": "该进程退出前，独立桥接会因锁冲突启动失败。",
+    "doctor.lock.cwdDifferent": "锁 cwd 与请求 cwd 不同 ({cwd})；单桥接锁是全局的。",
+    "doctor.lock.adapterDifferent": "锁 adapter={lockAdapter} 与请求 adapter={requestedAdapter} 不同。",
+    "doctor.endpoint.legacySame": "与适配器端点相同",
+    "doctor.endpoint.summary": "实例={instanceId} 类型={kind} 端口={port} 可达={reachable}",
+    "doctor.endpoint.owner": "ownerPid={ownerPid} ownerAlive={ownerAlive} companionPid={companionPid} companionAlive={companionAlive} 状态={status}",
+    "doctor.endpoint.issue.kind": "端点类型 {kind} 与请求适配器 {adapter} 不同",
+    "doctor.endpoint.issue.cwd": "端点 cwd 与请求 cwd 不同 ({cwd})",
+    "doctor.endpoint.issue.port": "端点端口 {port} 不可达",
+    "doctor.endpoint.issue.ownerDead": "桥接 owner pid={pid} 已退出",
+    "doctor.endpoint.issue.companionDead": "companion pid={pid} 已退出",
+    "doctor.endpoint.issue.workerStatus": "可见端 worker 状态={status}",
+    "doctor.endpoint.issue.instanceMismatch": "端点 instanceId 与桥接锁 instanceId 不一致",
 };