@quecue/dev-notify 0.1.2 → 0.1.4

package/dist/i18n.js

@@ -0,0 +1,960 @@
+// 中文是默认语言；英文键必须与中文键完全一致，缺少翻译会在编译期报错。
+const zh = {
+    'common.cancelled': '已取消。',
+    'common.failure': '操作失败。请检查文件、权限或输入；为避免泄露密钥，这里不显示底层异常。',
+    'config.homeAbsolute': 'DEV_NOTIFY_HOME 需要是绝对路径。',
+    'config.rootName': '配置',
+    'config.objectRequired': '{name} 需要是 JSON 对象。',
+    'config.objectUnknown': '{name} 包含不支持的字段；不能直接保存明文密钥。',
+    'config.enabledBoolean': 'enabled 需要是布尔值。',
+    'config.credentialEnvName': '凭据引用需要是合法的环境变量名称。',
+    'config.unsupportedVersion': '不支持这个配置版本。',
+    'config.invalidLanguage': 'language 需要是 zh 或 en。',
+    'config.invalidReference': '系统凭据引用无效。',
+    'config.chatIdsArray': 'telegram.chat_ids 需要是数组。',
+    'config.chatIdNumeric': '接收人需要使用数字 chat_id；大整数请写成字符串。',
+    'config.chatIdNonZero': '接收人需要是非零的数字 chat_id。',
+    'config.telegramToken': 'Telegram Token 格式不正确。',
+    'config.feishuWebhook': '飞书 webhook 需要是 open.feishu.cn 的 HTTPS 自定义机器人地址。',
+    'config.utf8': '输入需要是有效的 UTF-8 文本。',
+    'config.unreadable': '配置文件缺失、无法读取，或不是合法的 UTF-8 JSON。',
+    'config.exists': '配置已经存在，没有覆盖。Node 版不会修改旧版原型的配置。',
+    'config.createFailed': '无法创建配置，请检查路径和权限。',
+    'config.languageNoConfig': '配置文件不存在，无法保存语言设置：{file}。请先运行 setup --lang {language} 创建配置。',
+    'credentials.invalidReference': '系统凭据引用无效。',
+    'credentials.invalidBundle': '系统凭据数据无效，请重新运行 setup。',
+    'credentials.tooLong': '凭据总长度超过 2400 字节，请检查输入；没有保存。',
+    'credentials.readFailed': '无法读取系统凭据，或内容无效。请解锁系统凭据存储并允许访问，或重新运行 setup 配置。',
+    'credentials.exists': '这个随机凭据引用已经存在，没有覆盖，请重试。',
+    'credentials.accessFailed': '无法访问系统凭据存储，请检查系统权限。',
+    'credentials.writeUnknown': '凭据写入状态未知，清理也失败了。请检查引用 ID：{id}',
+    'credentials.writeFailed': '系统凭据写入失败，配置没有切换。',
+    'credentials.deleteFailed': '系统凭据删除失败，请检查存储权限。',
+    'credentials.platform': '系统凭据仅支持 Windows 和 macOS；其他平台请使用环境变量。',
+    'credentials.nativeLoad': '原生凭据组件无法加载。请确认 npm 安装保留了 optional 依赖，并且架构匹配；不会降级为明文存储。',
+    'credentials.oldReference': '这是旧版原型保存的凭据引用。请用 setup 重新输入并保存为 Node 凭据，或显式提供环境变量；不会自动读取或删除旧凭据。',
+    'credentials.missingEntry': '系统凭据条目缺失，请运行 setup 重新配置。',
+    'prompts.terminalRequired': '配置向导需要在交互终端中运行。自动化场景可以改用 setup --template --yes 搭配环境变量。',
+    'prompts.hiddenUnsupported': '当前终端不支持隐藏输入。为了不暴露密钥，这里不会改用明文输入；请在支持的终端中运行，或用环境变量配置。',
+    'prompts.hiddenIncomplete': '隐藏输入没有完成，凭据没有保存。',
+    'prompts.cancelled': '已取消。',
+    'prompts.inputTooLong': '凭据输入过长，没有保存。',
+    'channels.emptyTitle': '通知标题不能为空。',
+    'channels.telegramTooLong': 'Telegram 分段后仍然超过消息长度限制。',
+    'channels.feishuTooLong': '飞书分段后仍然超过请求大小限制。',
+    'channels.noResponse': '服务端没有返回内容。',
+    'channels.responseTooLarge': '服务端响应过大，已停止读取。',
+    'channels.notJsonObject': '服务端返回的不是 JSON 对象。',
+    'channels.network': '网络请求失败或响应无效。为避免重复通知，不会自动重发；这条消息可能没有送达。',
+    'channels.rejected': '渠道拒绝了这次发送。请检查凭据、接收人授权、签名和频率限制。',
+    'channels.sendFailed': '发送失败，这条消息可能没有送达。',
+    'channels.feishuReplyButton': '💬 在 Telegram 回复 Claude',
+    'format.noSpace': '可用空间不足，无法分段。',
+    'format.oneChar': '可用空间连一个字符都放不下。',
+    'format.telegramHeader': 'Telegram 标题或底部信息太长，没有剩余空间放正文。',
+    'format.feishuHeader': '飞书标题或底部信息太长，没有剩余空间放正文。',
+    'setup.readFailed': '无法读取现有配置，这次没有做任何修改。',
+    'setup.parseFailed': '现有配置无法解析，这次没有覆盖它。请先修复 JSON。',
+    'setup.lockUnavailable': '配置写入锁不可用。请检查权限；如果确认没有向导在运行，可以删除残留的 .setup.lock。',
+    'setup.changedDuringWizard': '配置在向导期间发生了变化，这次没有覆盖它。请重试。',
+    'setup.credentialVerifyFailed': '凭据写入后校验失败，配置没有切换。',
+    'setup.changedDuringSave': '配置在保存期间发生了变化，这次没有覆盖它。请重试。',
+    'setup.tempCleanupFailed': '临时配置没有清理掉：{name}',
+    'setup.credentialCleanupFailed': '配置没有切换，新凭据也未能清理。引用 ID：{id}',
+    'setup.lockCleanupFailed': '配置写入锁没有清理掉。请确认没有向导在运行，再删除 .setup.lock。',
+    'setup.oldCredentialCleanupFailed': '配置已保存，但旧凭据没有清理掉。引用 ID：{id}',
+    'setup.oldSystemRetained': '旧版原型的旧凭据仍然保留，由旧版工具继续管理，避免两个实现互相误删。',
+    'setup.path': '配置路径：{file}',
+    'setup.secretsNote': 'Token、webhook 和签名密钥都不会回显，将保存到 Windows Credential Manager / macOS Keychain；配置文件只保留引用。',
+    'setup.channelPrompt': '选择通知渠道：1 Telegram，2 飞书，3 两者{current}（输入其他内容取消）：',
+    'setup.credentialUnreadable': '当前凭据暂时读不到，可能是条目缺失、凭据库锁定或权限不足。',
+    'setup.reenterPrompt': '要重新输入所选渠道的凭据吗？[y/N] ',
+    'setup.oldSystemDetected': '检测到旧版原型保存的凭据。本次会重新输入并保存为 Node 版凭据，旧凭据保持不变。',
+    'setup.secretRequiredKeep': '{label}（隐藏输入，不回显；留空保留当前值）：',
+    'setup.secretRequiredNew': '{label}（隐藏输入，不回显；不会从环境变量自动填充）：',
+    'setup.secretOptionalKeep': '{label}（隐藏输入，不回显；可选；留空保留当前值；输入 - 清除）：',
+    'setup.secretOptionalNew': '{label}（隐藏输入，不回显；可选；不会从环境变量自动填充；输入 - 清除）：',
+    'setup.requiredBlank': '这一项不能为空，请重新输入；按 Ctrl+C 可退出。',
+    'setup.invalidFormat': '格式不正确，请重新输入（输入内容不会显示）。',
+    'setup.telegramChatInstruction': '请先让接收人给 Bot 发一条消息，然后填写数字 chat_id；这里不会自动获取或配对接收人。',
+    'setup.telegramChatPrompt': '接收人 chat_id，多个用逗号分隔（留空保留现有名单）：',
+    'setup.telegramChatInvalid': '请填写至少一个有效的数字 chat_id；按 Ctrl+C 可退出。',
+    'setup.channelsEnabled': '将启用：{channels}',
+    'setup.envPriority': '环境变量的优先级更高，空值也会覆盖这里的设置；测试通知使用最终生效的配置。',
+    'setup.envOverrides': '以下环境变量正在覆盖配置：{names}',
+    'setup.oldDeleteWarning': '保存成功后会删除旧凭据；如果其他配置也引用了同一个凭据，需要一并更新。',
+    'setup.disabledChannels': '没有选中的渠道会被停用；新凭据只用于本次选中的渠道。',
+    'setup.actionSave': '保存配置和系统凭据',
+    'setup.actionTest': '发送固定内容的测试通知',
+    'setup.actionHooks': '安装 Claude Code 通知 hooks',
+    'setup.continue': '将{actions}。继续？[Y/n] ',
+    'setup.saved': '配置和系统凭据已保存。',
+    'setup.testSuccess': '测试通知发送成功。',
+    'setup.testFailed': '配置已保存。测试通知没有发送成功，请运行 dev-notify doctor 检查。',
+    'setup.testFailedEnv': '配置已保存。测试通知没有发送成功，可能是环境变量覆盖或网络问题；请运行 dev-notify doctor 检查。',
+    'setup.testSkipped': '已跳过测试通知。',
+    'setup.hooksFailed': '配置已保存。Claude Code hooks 没有安装完成：{reason}',
+    'setup.hooksCheckHint': '请运行 integration claude-code status 检查',
+    'setup.replyHint': '如需在 Telegram 中回复 Claude，请运行：dev-notify reply setup',
+    'setup.clearNoReference': '当前配置没有系统凭据引用，无需清理。',
+    'setup.clearOldBackend': '这是旧版原型保存的凭据；Node 版不会跨实现删除，请用原工具处理。',
+    'setup.clearWarning': '将删除当前配置引用的系统凭据，并从配置中移除引用。环境变量不受影响；如果其他配置共享同一个凭据，它们也会失效。',
+    'setup.clearConfirm': '确认清除吗？[y/N] ',
+    'setup.cleared': '凭据引用已移除。如果系统条目删除失败，上方会显示提示。',
+    'setup.channelTelegram': 'Telegram（{count} 个接收人）',
+    'setup.channelFeishu': '飞书',
+    'setup.labelFeishuWebhook': '飞书 webhook',
+    'setup.labelFeishuSecret': '飞书签名密钥',
+    'cli.help': `dev-notify {version} — 跨平台开发任务通知
+
+命令：
+  send --title 标题 [--content 正文 | --content-file 文件 | --stdin]
+       [--channel all|telegram|feishu] [--level info|success|warn|error]
+       [--footer 辅助信息] [--dry-run]
+  setup [--no-test] [--no-hooks]
+                            配置渠道及系统凭据；默认同时发送测试并安装
+                            Claude Code 通知 hooks，一次确认完成
+  setup --template [--yes]   只创建无密钥模板；不会覆盖已有配置，也不会安装 hooks
+  credentials clear         移除当前 Node 凭据引用和条目（需要确认）
+  paths                     显示配置路径（不会写入文件）
+  doctor / status           离线检查（不会发送消息）
+  update [--check] [--yes] [--no-post]
+                            检查并更新到 npm 最新版本，并维护 hooks 和桥接
+  integration list          列出可用集成
+  integration claude-code install / status / remove
+                            单独安装、查询或移除用户级 hooks（install/remove 可用 --yes）
+  reply setup               授权可信的 Telegram 私聊用户
+  reply start / status / stop
+                            启动、查询或停止回复桥接
+  reply disable             撤销远程回复授权并停止桥接（需要确认）
+  reply run                 前台运行桥接（排错用，不启用系统自启动）
+  language [zh|en]          查看或切换已保存的界面语言
+
+全局选项：--config 路径、--lang zh|en、--help、--version
+环境变量：TELEGRAM_BOT_TOKEN、TELEGRAM_CHAT_ID / TELEGRAM_CHAT_IDS、
+          FEISHU_WEBHOOK、FEISHU_SECRET；显式存在时优先。
+          DEV_NOTIFY_LANG=zh|en 切换界面语言。详见 README。
+系统凭据保存在 Windows Credential Manager / macOS Keychain；不会写入明文密钥。`,
+    'cli.invalidArgs': '参数无效，请运行 --help 查看用法。',
+    'cli.invalidCommand': '命令或选项组合不正确，请运行 --help 查看用法。',
+    'cli.invalidLanguage': '语言必须是 zh 或 en：{value}',
+    'cli.integrationList': 'claude-code：支持通知、Telegram 回复和结构化问题交互。通知 hooks 与回复权限分开，默认只发送通知，不接收远程输入。',
+    'cli.integrationUsage': '请使用 integration list，或 integration claude-code install / status / remove。',
+    'cli.integrationStatusFile': 'Claude Code 用户级设置：{file}',
+    'cli.integrationStatusCounts': '本工具 hooks：Stop {stop} 个，Notification {notification} 个，会话生命周期 {lifecycle}/3 个，交互及结果确认 {interaction}/5 个；其他处理器 {others} 个。',
+    'cli.integrationDisabled': '当前文件启用了 disableAllHooks，安装后 hooks 不会生效；请自行解除禁用。',
+    'cli.integrationStatusNote': '这里只检查用户级文件。是否实际加载还受项目和托管策略影响，请在 Claude Code 的 /hooks 中确认。',
+    'cli.setupChannelFirst': '请先运行 setup 配置至少一个通知渠道，再安装 Claude Code hooks。',
+    'cli.replyUsage': '请使用 reply setup / start / status / stop / disable / run。',
+    'cli.credentialsUsage': 'credentials 目前只支持 clear，并且需要在交互终端中确认。',
+    'cli.yesTemplateOnly': '--yes 只能和 --template 一起使用；保存密钥前仍然需要确认。',
+    'cli.sendTitle': 'send 需要提供非空的 --title。',
+    'cli.sendSources': '--content、--content-file 和 --stdin 只能选择一个。',
+    'cli.channelLevel': '渠道或通知级别不正确。',
+    'cli.segmentationFailed': '{channel}：无法安全分段。请缩短标题或底部信息，或检查正文格式。',
+    'cli.dryRun': '{channel}：接收目标 {recipients}，预计请求 {items} 条（dry-run，没有实际发送）',
+    'cli.sent': '{channel}：已发送 {sent}/{planned} 条',
+    'cli.testSent': '{channel}：测试已发送 {sent}/{planned} 条',
+    'cli.noChannels': '没有可用渠道，请先配置环境凭据和接收人。',
+    'cli.channelNotReady': '这个渠道未启用，或配置不完整。',
+    'cli.testTitle': 'dev-notify 配置测试',
+    'cli.testContent': '这是一条由你确认发送的测试通知。',
+    'cli.setupNoteTest': '保存后会向最终生效的接收目标发送一条固定内容的测试通知。',
+    'cli.setupNoteHooksPath': 'Claude Code 用户级设置：{path}',
+    'cli.setupNoteHooksScope': '会为该设置文件对应的所有项目安装通知 hooks。最终回复正文可能包含敏感内容，将发送到配置实际生效的渠道。',
+    'cli.setupNoteHooksLifecycle': '同时安装会话生命周期和结构化问题 hooks。远程输入只有在运行 reply setup 授权后才会开启。',
+    'cli.skipHooks': '跳过 Claude Code hooks：{reason}',
+    'cli.skipHooksNoPath': '跳过 Claude Code hooks：没有找到用户级设置路径。',
+    'cli.templateWillCreate': '将创建无密钥模板：{file}。不会联网，也不会修改 hooks。',
+    'cli.templateCancelled': '已取消，没有写入。',
+    'cli.templateCreated': '模板已创建。请配置环境凭据和接收人。',
+    'cli.configPath': '配置路径: {file}',
+    'cli.channelReady': '配置完整（尚未验证网络）',
+    'cli.channelNotReadyStatus': '未启用或配置不完整',
+    'cli.channelStatus': '{channel}：{status}',
+    'cli.credentialsNote': '凭据：优先使用环境变量，其次系统凭据；本检查不联网，系统可能弹出授权提示。',
+    'cli.confirmTemplate': '确认创建模板？[y/N] ',
+    'cli.nonInteractive': '当前不是交互终端。自动化场景请使用 setup --template --yes。',
+    'cli.replySaved': '授权已保存。请确认 hooks 已安装，然后运行 reply start。旧消息的回复映射不会保留。',
+    'cli.bridgeStopped': '桥接已停止或未运行。',
+    'cli.replyDisabled': '已撤销授权并请求停止。正在进行中的调用无法撤回。',
+    'cli.stopStopped': '桥接已停止或未运行。授权仍然保留，下次事件可以再次启动；如需彻底关闭，请运行 reply disable。',
+    'cli.stopRequested': '已发出停止请求，桥接正在退出。可运行 reply status 查看状态。',
+    'cli.replyStatusAccess': '远程回复：已授权 {users} 个私聊用户；工具权限逐次确认{state}。',
+    'cli.replyPermissionOn': '已开启',
+    'cli.replyPermissionOff': '未开启',
+    'cli.replyStatusNoAccess': '远程回复：尚未启用。',
+    'cli.bridgeReady': '桥接：已就绪。',
+    'cli.bridgeStarting': '桥接：进程存在，但还没有就绪。',
+    'cli.bridgeNotRunning': '桥接：未运行。',
+    'cli.replyStartReady': '回复桥接已就绪。请从新的任务通知进入。',
+    'cli.replyStartNotReady': '桥接还没有就绪。请运行 reply status 或 reply run 查看原因；如果旧版桥接在运行，请先停用它。',
+    'cli.languageCurrent': '当前语言：{language}（{code}）。',
+    'cli.languageChanged': '语言已切换为{language}（{code}）。',
+    'cli.languageAlready': '当前已经是{language}（{code}）。',
+    'cli.languageHint': '使用 language zh 或 language en 切换并保存。',
+    'update.npmUnavailable': '无法运行 npm。请确认已安装 npm，并且它在 PATH 中。',
+    'update.checkNetwork': '无法检查最新版本。请检查网络后重试。',
+    'update.checkHttp': '无法检查最新版本（HTTP {status}）。请检查网络后重试。',
+    'update.parseRegistry': 'npm registry 返回的版本信息无法解析。',
+    'update.registryVersion': 'npm registry 返回的版本号格式不受支持。',
+    'update.versionFormat': '版本号格式不受支持。',
+    'update.terminalRequired': '更新需要在交互终端中确认；非交互场景请使用 dev-notify update --yes。',
+    'update.confirm': '更新到 {latest}？[y/N] ',
+    'update.manualPost': '如有 Claude Code hooks，请运行 dev-notify integration claude-code install；如使用远程回复，请重启桥接。',
+    'update.partialUpdated': '更新已完成，但后续维护步骤没有全部成功；请按上面的提示检查。',
+    'update.partial': '维护步骤没有全部成功；请按上面的提示检查。',
+    'update.postDoneUpdated': '更新后的维护步骤已完成。',
+    'update.postDone': '维护步骤已完成。',
+    'update.currentFormat': '当前版本号格式不受支持，无法检查更新。',
+    'update.upToDate': '已是最新版本 {version}。',
+    'update.maintenanceNote': '将执行 Claude Code hooks 和回复桥接维护。',
+    'update.versions': '当前版本 {current}，npm 最新版本 {latest}。',
+    'update.checkHint': '运行 dev-notify update 更新。',
+    'update.postNote': '更新完成后会自动重新安装绑定当前配置的 Claude Code hooks，并重启正在运行的回复桥接；可用 --no-post 跳过。',
+    'update.cancelled': '已取消，没有更新。',
+    'update.running': '运行 npm install -g {name}@{latest} ...',
+    'update.failed': '更新没有完成。请检查 npm 权限，或手动运行 npm install -g {name}@latest。',
+    'update.updated': '已更新到 {latest}。请重新打开终端后运行 dev-notify --version 确认。',
+    'maintenance.runFailed': '无法运行更新后的 dev-notify。请重新打开终端后运行 dev-notify --version 检查。',
+    'maintenance.reasonHint': '请运行 dev-notify integration claude-code status 或 dev-notify reply status 检查。',
+    'maintenance.hooksCheckFailed': '无法检查 Claude Code hooks：{reason}',
+    'maintenance.noHooks': '未检测到本工具的 Claude Code hooks，跳过。',
+    'maintenance.otherConfig': 'Claude Code hooks 绑定的是其他通知配置，跳过自动更新；如需更新，请用原来的 --config 运行 integration claude-code install。',
+    'maintenance.updatingHooks': '更新 Claude Code hooks ...',
+    'maintenance.hooksUpdated': 'Claude Code hooks 已更新。',
+    'maintenance.hooksFailed': 'Claude Code hooks 更新失败。',
+    'maintenance.hooksFailedReason': 'Claude Code hooks 更新失败：{reason}',
+    'maintenance.bridgeCheckFailed': '无法检查回复桥接：{reason}',
+    'maintenance.restartingBridge': '重启回复桥接 ...',
+    'maintenance.bridgeStillRunning': '回复桥接仍在退出，请稍后运行 dev-notify reply start。',
+    'maintenance.bridgeRestarted': '回复桥接已重启。',
+    'maintenance.bridgeStartFailed': '回复桥接启动失败。',
+    'maintenance.bridgeRestartFailed': '回复桥接重启失败：{reason}',
+    'maintenance.noBridge': '未检测到运行中的回复桥接，跳过。',
+    'claude.settingsAbsolute': 'CLAUDE_CONFIG_DIR 需要是绝对路径，Claude Code 设置没有改动',
+    'claude.settingsTooLarge': 'Claude Code 设置超过 1 MiB，操作已停止，文件没有改动。',
+    'claude.settingsReadFailed': '无法读取 Claude Code 设置，操作已停止。',
+    'claude.settingsInvalidJson': 'Claude Code 设置不是合法的 UTF-8 JSON，没有覆盖。',
+    'claude.settingsInvalidShape': 'Claude Code 设置或 hooks 结构无效，没有覆盖。',
+    'claude.hooksInvalidShape': 'Claude Code hook 数组结构无效，没有覆盖。',
+    'claude.lockUnavailable': '暂时无法获取 Claude Code 设置写入锁。请确认没有安装进程在运行，再处理残留的 .dev-notify.lock。',
+    'claude.changedDuringConfirm': 'Claude Code 设置在确认期间发生了变化，没有覆盖，请重试。',
+    'claude.changedDuringSave': 'Claude Code 设置在保存期间发生了变化，没有覆盖，请重试。',
+    'claude.tempCleanupFailed': '临时文件清理失败。安装结束后请删除 .dev-notify-*.tmp。',
+    'claude.lockCleanupFailed': '锁文件清理失败。安装结束后请删除 .dev-notify.lock。',
+    'claude.settingsPath': 'Claude Code 用户级设置：{file}',
+    'claude.noHooks': '没有找到本工具添加的 hooks，设置没有改动。',
+    'claude.alreadyInstalled': '本工具 hooks 已经安装，配置一致，无需重复添加。',
+    'claude.configPath': '通知配置：{config}',
+    'claude.installScope': '会为这个 Claude Code 配置目录下的所有项目启用通知：任务结束时发送最终回复，需要你确认或输入时也会提醒。',
+    'claude.installSensitive': '最终回复和提醒正文可能包含敏感内容，会发送到配置实际生效的 Telegram / 飞书。环境变量仍然优先。',
+    'claude.installLifecycle': '同时安装会话生命周期和结构化问题 hooks。远程输入需要另行运行 reply setup 授权。',
+    'claude.installReads': '不会读取整份会话记录。启用回复后，会读取会话的进程元数据；结构化问题或权限请求会发送对应的问题和工具信息。',
+    'claude.installTiming': 'PreToolUse 只登记调用身份；PermissionRequest 会和本机终端窗口同时等待，远程回答的有效期是 10 分钟。安装完成事件只用于反馈结果，不会代替你作答。已核对 Claude Code 2.1.316；其他版本或宿主环境需要另行验证。',
+    'claude.otherHandlers': '当前文件里还有 {count} 个其他相关处理器，可能会重复通知。',
+    'claude.projectHooks': '项目级或插件的 hooks 也可能同时生效；本工具不会自动迁移或删除旧版 hooks。',
+    'claude.disabledWarning': '注意：该文件启用了 disableAllHooks，安装后 hooks 也不会生效；请自行解除禁用。',
+    'claude.removeScope': '只会移除本工具添加的通知、生命周期和交互处理器；其他设置、hooks、通知配置和系统凭据都会保留。如需停止回复桥接，请运行 reply disable 或 reply stop。',
+    'claude.confirmInstall': '安装这些 Claude Code hooks？[y/N] ',
+    'claude.confirmRemove': '移除本工具的 Claude Code hooks？[y/N] ',
+    'claude.cancelled': '已取消，Claude Code 设置没有改动。',
+    'claude.installed': 'Claude Code hooks 已安装。请在 /hooks 中检查并按界面确认；如果没有生效，请重启会话。',
+    'claude.removed': '本工具的 Claude Code hooks 已移除。请在 /hooks 中检查，必要时重启会话。',
+    'hook.timeout': 'Claude Code hook 输入超时，通知没有发送。',
+    'hook.tooLarge': 'Claude Code hook 输入超过大小限制，通知没有发送；内容不会被截断。',
+    'hook.footerProject': '项目：{value}',
+    'hook.footerTopic': '主题：{value}',
+    'hook.footerSession': '会话：{value}',
+    'hook.invalidJson': 'Claude Code hook 输入不是合法的 UTF-8 JSON，通知没有发送。',
+    'hook.notObject': 'Claude Code hook 输入需要是 JSON 对象。',
+    'hook.invalidStopState': 'Claude Code Stop 状态字段无效。',
+    'hook.invalidReply': 'Claude Code 最终回复字段无效。',
+    'hook.replyTitle': 'Claude Code 回复完成',
+    'hook.replyFallback': '本轮回复已结束，Claude Code 没有提供最终正文。请回到终端查看；这里不会读取会话文件来补正文，以免显示过期内容。',
+    'hook.invalidNotification': 'Claude Code 通知正文字段无效。',
+    'hook.notificationTitle': 'Claude Code 需要你处理',
+    'hook.notificationFallback': 'Claude Code 正在等待你的确认或输入，请回到终端处理。',
+    'hook.interactionFailed': 'Claude Code 的回复状态或交互处理失败。没有自动选择答案或批准权限，请在本机处理。',
+    'hook.sessionNameFailed': '读取不到 Claude Code 会话名称，通知底部将省略主题。',
+    'hook.replyNotReady': '远程回复还没有就绪，仍会尝试发送普通通知。',
+    'hook.coverageFailed': '没有核验到选择题通知的覆盖情况，将保留普通权限提醒。',
+    'hook.sendIncomplete': '{channel}：Claude Code 通知没有完整发送。整条消息不会自动重发。',
+    'hook.sendFailed': '{channel}：Claude Code 通知发送失败。请检查配置、系统凭据和网络；整条消息不会自动重发。',
+    'hook.noChannels': 'Claude Code 通知没有可用渠道，请运行 dev-notify doctor 检查。',
+    'reply.readFailed': '无法读取回复配置或状态。为了不覆盖现有数据，远程输入没有启用。',
+    'reply.lockUnavailable': '无法获取回复状态写入锁。',
+    'reply.lockBusy': '回复状态锁正忙。请确认相关进程已经退出，再处理残留锁。',
+    'reply.invalidPolicy': '回复授权配置无效，远程输入已停用。',
+    'reply.hooksMissing': '回复所需的 hooks 缺失、时序不安全或已禁用。请重新运行 integration claude-code install，并在 /hooks 中确认加载。',
+    'reply.botChanged': 'Telegram Bot 已变更或不可用，请重新运行 reply setup 授权。',
+    'reply.usersRevoked': '授权用户不在当前 Telegram 接收名单中，远程输入已停用。',
+    'reply.authorizationChanged': '回复授权已撤销或发生变化，没有写入旧状态。',
+    'reply.invalidState': '回复状态结构无效，远程输入已停用。',
+    'reply.setupHooksFirst': '请先运行 integration claude-code install，安装绑定此通知配置的完整 hooks，再配置回复。',
+    'reply.setupTelegramFirst': '回复 Claude 需要先配置 Telegram Bot 和私聊接收人。',
+    'reply.setupPrivateOnly': '远程回复仅支持 Telegram 私聊用户，不支持群聊。',
+    'reply.setupNoticeInput': '远程回复等同于在本机 Claude Code 终端输入并提交内容。它可以提交 Claude 命令，但不会自动批准工具权限。请只授权给可信用户。',
+    'reply.setupNoticeBridge': '飞书按钮会跳转到 Telegram，不直接接收飞书消息。这个功能需要独占 Bot 的 getUpdates，请不要与旧版桥接或其他机器共用同一个 Bot。',
+    'reply.setupNoticePlatform': 'Windows 使用系统 PowerShell / 控制台 API；macOS 使用 Ghostty 或 tmux，需要相应的系统权限。',
+    'reply.setupNoticeUnsupported': '目前不支持 VS Code 集成终端、WSL 和 SSH。目标不确定或会话已经切换时，会拒绝输入。',
+    'reply.setupAvailable': '通知接收人不会自动获得输入权限。可选择的私聊 chat_id：{users}',
+    'reply.setupPrompt': '请输入要授权的私聊 chat_id（逗号分隔；留空取消）：',
+    'reply.setupInvalidUser': '只能授权当前通知名单中的私聊用户。',
+    'reply.setupAuthorizing': '将授权以下用户远程输入：{users}',
+    'reply.setupSensitive': '结构化问题会展示真实选项，也支持自定义回答；普通回复会在本轮结束后输入。问题、选项和工具请求参数可能包含敏感信息，会发送到授权私聊和已配置的飞书。',
+    'reply.setupPermissionsPrompt': '是否允许这些用户逐次批准或拒绝工具权限？这不会修改永久规则。[y/N] ',
+    'reply.setupConfirm': '确认启用远程回复并接受上述权限范围？[y/N] ',
+    'reply.setupChanged': '回复授权已被其他进程修改，请重试。',
+    'reply.setupConfigChanged': '通知配置在授权期间发生了变化，请重试。',
+    'reply.setupSaved': '授权已保存。旧消息的回复映射不会保留；请从启用后的任务完成通知进入。',
+    'reply.disableNotEnabled': '远程回复尚未启用。',
+    'reply.disableConfirm': '确认禁用远程回复？通知和凭据都会保留。[y/N] ',
+    'reply.disableChanged': '回复授权发生了变化，请重试。',
+    'reply.disabled': '远程回复已禁用。正在进行的操作无法撤回，桥接会在下次检查时退出。',
+    'reply.endSessionReason': '会话已经结束，或无法核验身份',
+    'reply.endSwitchedReason': '会话已经切换',
+    'reply.endTurnReason': '本轮已结束',
+    'reply.endLocalReason': '本机已开始新任务或新会话',
+    'reply.receivedTitle': '✅ Claude 已收到回复',
+    'reply.receivedBody': 'Claude 已收到你提交的回复，任务完成后会再发通知。',
+    'reply.receivedTelegramFailed': 'Telegram：收到确认没有发送成功；已提交的输入不会重放。',
+    'reply.receivedFeishuBody': 'Claude 已收到你提交的回复，任务完成后会再发通知。为减少扩散，这里不转发回复原文。',
+    'reply.receivedFeishuFooter': '会话：{session}',
+    'reply.receivedFeishuIncomplete': '飞书：收到确认没有完整发送；已提交的输入不会重放。',
+    'reply.receivedFeishuFailed': '飞书：收到确认发送失败；已提交的输入不会重放。',
+    'reply.bridgeNotReadyButton': '回复桥接还没有就绪，这条通知不会显示回复按钮。可运行 reply status 查看原因。',
+    'reply.botUsernameInvalid': 'Telegram Bot 用户名无效，回复按钮没有启用。',
+    'reply.noMessageId': '通知没有返回可关联的 Telegram 消息 ID。',
+    'reply.noSession': '没有核验到会话，结构化交互将在本机处理。',
+    'reply.noMatchingCall': '没有唯一匹配到这次工具调用，远程交互没有启用；本机窗口不受影响。',
+    'reply.bridgeNotReadyQuestion': '回复桥接还没有就绪，问题将在本机处理。',
+    'reply.permissionRequest': '工具权限请求：{tool}',
+    'reply.interactionEnded': '远程交互已经结束，或答案没有提交。不会自动作答，本机操作不受影响。',
+    'reply.interactionFailed': '远程交互处理失败，请在本机检查。',
+    'reply.interactionCancelled': '交互等待已取消，远程答案是否生效还没有确认。',
+    'reply.sessionGoneTitle': '⚠️ 无法回复',
+    'reply.sessionGoneBody': '这个会话已经关闭、切换，或这条通知已过期。请从最新通知进入。',
+    'reply.replyPromptTitle': '💬 回复 Claude',
+    'reply.replyPromptBody': '请回复此消息输入内容。该输入将提交到对应本机会话。\n会话：{session}',
+    'reply.replyPromptLongPress': '请长按这条消息并选择「回复」，然后输入内容。该输入将提交到对应本机会话。\n会话：{session}',
+    'reply.processingFailedCallback': '处理没有完成，请检查终端；不会自动重复提交。',
+    'reply.processingFailedTitle': '⚠️ 本次提交没有完成',
+    'reply.processingFailedBody': '处理时出现了异常，这次提交可能已经登记，也可能没有生效。请检查终端和后续结果；不会自动重复提交。',
+    'reply.interactionExpiredCallback': '会话已关闭，或这次交互已经失效。',
+    'reply.interactionExpiredTitle': '⚠️ 这次提交没有生效',
+    'reply.interactionExpiredBody': '会话已经关闭、切换，或交互已经失效，答案没有回传。',
+    'reply.replyBoxHint': '请在回复框输入内容',
+    'reply.staleTitle': '⚠️ 本次提交没有生效',
+    'reply.staleBody': '这条消息已经超过有效时间，答案没有回传。请查看最新问题或终端状态。',
+    'reply.howToTitle': '💬 回复方式',
+    'reply.howToBody': '请直接回复任务完成通知，或点击通知里的「回复 Claude」按钮。',
+    'reply.expiredReplyBody': '通知已过期，或对应会话已经关闭、切换。请从最新通知回复。',
+    'reply.replyFailedTitle': '❌ 回复没有提交',
+    'reply.invalidInput': '输入无效。',
+    'reply.sessionChanged': '会话已经变化，这次回复没有提交。',
+    'reply.pendingTitle': '⏳ 新回复没有提交',
+    'reply.pendingBody': '这个会话已有一条待确认的回复。请先等待确认，或检查本机终端后再试。',
+    'reply.queuedTitle': '⏳ 回复已排队',
+    'reply.queuedBody': 'Claude 正在处理当前任务；本地队列将在本轮结束后尝试提交，不会把文本输入到正在等待权限的弹窗。',
+    'reply.queueExpired': '排队的回复已超过 5 分钟，没有提交。请检查本机后重新回复。',
+    'reply.sessionClosed': '会话已经关闭或切换，这次回复没有提交。',
+    'reply.forwardedTitle': '✅ 已转发给 Claude',
+    'reply.forwardedBody': '终端输入已提交，正在等待 UserPromptSubmit 确认。',
+    'reply.forwardUnknownTitle': '⚠️ 转发状态待确认',
+    'reply.forwardFailed': '提交没有完成，请检查本机终端；不会自动重复提交。',
+    'reply.invalidQuestions': '问题结构无效，请在本机回答。',
+    'reply.permissionsNotAuthorized': '未授权远程处理工具权限。',
+    'reply.targetChanged': '会话目标发生了变化。',
+    'reply.callUnavailable': '调用已经结束或已绑定，没有创建远程问题。',
+    'reply.questionSwitched': '问题已切换，旧请求不再接受答案。',
+    'reply.allowButton': '✅ 本次允许',
+    'reply.denyButton': '⛔ 拒绝',
+    'reply.customDenyButton': '✍️ 自定义拒绝说明',
+    'reply.submitSelected': '提交所选项',
+    'reply.customInput': '✍️ 自定义输入',
+    'reply.closeRemote': '关闭远程答题（本机仍可操作）',
+    'reply.toolLabel': '工具：{tool}',
+    'reply.unknownTool': '未知',
+    'reply.permissionNote': '这里处理本次的允许、拒绝或自定义拒绝说明。Claude 没有提供完整的本地按钮列表，因此这里也不会创建永久权限规则。',
+    'reply.questionHeading': '问题 {index}/{total}：{question}',
+    'reply.multiSelectHint': '\n\n可多选，选好后点击「提交所选项」；也可自定义输入。',
+    'reply.singleSelectHint': '\n\n点击选项直接回答，或选择自定义输入。',
+    'reply.localWindowNote': '\n本机原生窗口也可以同时作答；Claude 先收到的完整答案生效。远程窗口有效期为 10 分钟，不会自动选择。',
+    'reply.feishuMultiSelectHint': '\n\n可多选：进入 Telegram 后逐项选择，再点击「提交所选项」；也可自定义输入。',
+    'reply.feishuSingleSelectHint': '\n\n进入 Telegram 后点击选项直接回答，或选择自定义输入。',
+    'reply.inactiveTitle': '⚠️ 交互已失效',
+    'reply.inactiveBody': '请从最新通知进入，或回到本机处理。',
+    'reply.noInteractionMessageId': '交互通知没有返回消息 ID。',
+    'reply.interactionNotSent': '交互通知没有完整发送，请回到本机处理。',
+    'reply.closedLocal': '已关闭远程答题，本机仍可正常处理。',
+    'reply.callbackExpired': '没有提交：按钮已失效，或已有答案等待确认。',
+    'reply.callbackClosed': '已关闭远程答题，本机不受影响。',
+    'reply.callbackRegistered': '答案已登记，尚未确认生效。',
+    'reply.callbackUpdated': '已更新。',
+    'reply.pendingConfirmationTitle': '⏳ 答案已登记，等待确认',
+    'reply.pendingRemaining': '仍需完成其余问题，之后才回传整份答案。',
+    'reply.pendingSubmitted': '已进入回传流程，Claude 是否采用会在稍后反馈。',
+    'reply.pendingFooter': '\n稍后会反馈结果；如果一直没有收到，请检查终端。\n请求：{id}',
+    'reply.notAppliedTitle': '⚠️ 本次提交未生效',
+    'reply.notAppliedBody': '这次操作没有提交：问题已处理、过期、题目已切换，或已有答案等待确认。\n请求：{id}',
+    'reply.denyInstruction': '请回复这条消息，填写拒绝说明。这段说明不会批准权限。',
+    'reply.answerInstruction': '请回复这条消息，输入这个问题的完整答案。',
+    'reply.answerInvalidTitle': '❌ 答案没有提交',
+    'reply.answerInvalidBody': '请输入不超过 4000 字符的答案；内容不会被截断。',
+    'reply.finalWaiting': '等待 Claude 确认，稍后会反馈最终结果；如果一直没有收到，请检查终端。',
+    'reply.nextWaiting': '仍需完成其余问题，之后才会回传整份答案；目前还没有生效。',
+    'reply.notSubmitted': '这次操作没有提交：对应问题已经结束、过期、切换，或已有答案等待确认。',
+    'reply.requestLine': '\n请求：{id}',
+    'reply.expiredUnsentAnswer': '远程答题已超时，没有提交任何答案；你仍可在本机继续处理。',
+    'reply.buttonUnknown': '已关闭 · 结果待核实',
+    'reply.buttonApplied': '已处理 · 不再接受答案',
+    'reply.buttonExpired': '已超时 · 未作答',
+    'reply.buttonInvalid': '已失效 · 未作答',
+    'reply.buttonClosed': '已关闭 · 不再接受答案',
+    'reply.buttonProcessed': '已处理 · 不再接受答案',
+    'reply.buttonEnded': '已结束 · 不再接受答案',
+    'reply.sessionUnknownSuffix': '；还没有收到本次答案的生效确认，请检查终端。',
+    'reply.sessionUnsentSuffix': '；这次远程答案没有回传。',
+    'reply.earlierHandled': '本机或其他端已经先处理了，这次 Telegram 答案没有提交。',
+    'reply.noVerifiableResult': 'Claude 已经结束了这个问题，但没有返回可核实的结果。请检查终端。',
+    'reply.answerApplied': 'Claude 已确认采用了与你提交内容一致的答案。如果本机也提交了相同内容，这次结果无法说明是哪一方生效。',
+    'reply.answerNotApplied': 'Claude 已经结束问题，但没有采用你提交的答案；本机或其他端可能已经先处理。',
+    'reply.questionProcessed': '问题已处理，旧按钮已失效。',
+    'reply.permissionApplied': '工具已获准并执行完成。如果本机同时也批准了，完成事件本身无法说明是哪一方放行。',
+    'reply.permissionNotApplied': '工具已经获准执行，这次远程决定没有阻止执行。',
+    'reply.toolFailedUnknown': '工具执行失败、被拒绝或取消。这个事件无法说明远程决定是否生效，请检查终端。',
+    'reply.toolFailed': '请求失败、被拒绝或取消，这次远程决定没有回传。',
+    'reply.waitTimeoutUnknown': '等待生效确认超时，或会话已经切换。结果暂时未知，请检查终端。',
+    'reply.sessionEndedUnsent': '会话已结束或已经切换；远程答案没有回传，你仍可在本机界面继续处理。',
+    'reply.expiredUnanswered': '远程答题已超时；没有提交任何答案，你仍可在本机界面继续处理。',
+    'reply.appliedTitle': '✅ 答案内容已生效',
+    'reply.resultUnknownTitle': '⚠️ 提交结果暂时无法确认',
+    'reply.requestLabel': '请求：{id}',
+    'reply.feedbackFailedLog': 'Telegram 结果反馈没有发送成功。不会自动重发，已经采用的答案不受影响。',
+    'reply.clearButtonsFailedLog': 'Telegram 旧按钮没有移除成功。服务端仍会拒绝这个请求。',
+    'reply.platformTimeout': '系统会话操作超时。输入可能已经部分送达，为避免重复提交，不会自动重试。',
+    'reply.platformFailed': '系统会话操作失败。为了避免泄露命令或输入，这里不显示底层信息。',
+    'reply.emptyReply': '回复内容不能为空。',
+    'reply.replyTooLong': '回复超过 4000 字符，没有提交。内容不会被截断，也不会拆成多次发送。',
+    'reply.emptyAfterCleanup': '回复清理后没有可提交的内容。',
+    'reply.targetInvalid': '会话已经关闭、切换，或无法核验身份。请从最新通知回复。',
+    'reply.windowsPartial': 'Windows 控制台注入失败，可能只写入了一部分。不会自动重试，请检查终端。',
+    'reply.unsupportedPlatform': '远程回复仅支持 Windows 和 macOS。',
+    'reply.tmuxBufferFailed': 'tmux 输入缓冲区创建失败，这次回复没有提交。',
+    'reply.tmuxChanged': '会话已经变化，这次回复没有提交。',
+    'reply.tmuxPasteFailed': 'tmux 粘贴失败，可能只送达了一部分。不会自动重试。',
+    'reply.tmuxSubmitFailed': 'tmux 提交失败，文本可能已经输入。不会自动重试。',
+    'reply.ghosttyFailed': 'Ghostty 没有找到目标窗口，或注入失败。不会改投其他窗口，也不会重复输入。',
+    'reply.telegramMethod': '不支持的 Telegram 桥接方法',
+    'reply.telegramConflict': 'Telegram 轮询冲突；检查旧版桥接、其他机器或 webhook，桥接不会抢占或删除 webhook',
+    'reply.telegramRequestFailed': 'Telegram 桥接请求失败；不输出服务端正文或秘密',
+    'reply.bridgeAuthFirst': '远程回复尚未授权，请先运行 reply setup。',
+    'reply.bridgeNotAuthorized': '远程回复尚未授权。',
+    'reply.bridgeLocked': '当前用户已经有同一个 Bot 的桥接在运行，或残留了锁文件。请确认进程退出后，再处理 reply-bots 中对应的锁。',
+    'reply.webhookConflict': '这个 Bot 已经设置了 webhook，不能同时使用 getUpdates。请先移除 webhook；本工具不会自动删除。',
+    'reply.pollFailedLog': 'Telegram 轮询失败；日志中没有记录密钥或服务端正文。',
+    'reply.pollFailedFatal': 'Telegram 连续轮询失败 5 次，桥接已经退出。请检查网络、Token 或 API 冲突后重新启动。',
+    'reply.updatesInvalid': 'Telegram 更新格式无效。',
+    'reply.handleFailedLog': '回复处理失败。这条更新不会重放；请检查终端，或从最新通知重试。',
+    'reply.bridgeFailed': '桥接启动或运行失败；为避免泄露密钥，没有显示底层错误。',
+    'channels.telegramReplyButton': '💬 回复 Claude',
+};
+const en = {
+    'common.cancelled': 'Cancelled.',
+    'common.failure': 'The operation failed. Check files, permissions, or input; to avoid leaking secrets, the underlying exception is not shown.',
+    'config.homeAbsolute': 'DEV_NOTIFY_HOME must be an absolute path.',
+    'config.rootName': 'configuration',
+    'config.objectRequired': '{name} must be a JSON object.',
+    'config.objectUnknown': '{name} contains unsupported fields; plaintext secrets cannot be stored directly.',
+    'config.enabledBoolean': 'enabled must be a boolean.',
+    'config.credentialEnvName': 'The credential reference must be a valid environment variable name.',
+    'config.unsupportedVersion': 'This configuration version is not supported.',
+    'config.invalidLanguage': 'language must be zh or en.',
+    'config.invalidReference': 'The system credential reference is invalid.',
+    'config.chatIdsArray': 'telegram.chat_ids must be an array.',
+    'config.chatIdNumeric': 'Recipients must use numeric chat_id values; write large integers as strings.',
+    'config.chatIdNonZero': 'Recipients must use non-zero numeric chat_id values.',
+    'config.telegramToken': 'The Telegram token format is invalid.',
+    'config.feishuWebhook': 'The Feishu webhook must be an HTTPS custom bot URL on open.feishu.cn.',
+    'config.utf8': 'Input must be valid UTF-8 text.',
+    'config.unreadable': 'The configuration file is missing, unreadable, or not valid UTF-8 JSON.',
+    'config.exists': 'Configuration already exists and was not overwritten. The Node version will not modify old-prototype configuration.',
+    'config.createFailed': 'Could not create the configuration. Check the path and permissions.',
+    'config.languageNoConfig': 'The configuration file does not exist, so the language setting cannot be saved: {file}. Run setup --lang {language} first to create a configuration.',
+    'credentials.invalidReference': 'The system credential reference is invalid.',
+    'credentials.invalidBundle': 'The system credential data is invalid. Re-run setup.',
+    'credentials.tooLong': 'The credential bundle exceeds 2400 bytes. Check the input; nothing was saved.',
+    'credentials.readFailed': 'Could not read the system credential, or its contents are invalid. Unlock the system credential store and allow access, or re-run setup.',
+    'credentials.exists': 'This random credential reference already exists and was not overwritten. Try again.',
+    'credentials.accessFailed': 'Could not access the system credential store. Check system permissions.',
+    'credentials.writeUnknown': 'The credential write state is unknown, and cleanup also failed. Check reference ID: {id}',
+    'credentials.writeFailed': 'Writing the system credential failed; the configuration was not switched.',
+    'credentials.deleteFailed': 'Deleting the system credential failed. Check storage permissions.',
+    'credentials.platform': 'System credentials are supported only on Windows and macOS; use environment variables on other platforms.',
+    'credentials.nativeLoad': 'The native credential component could not be loaded. Confirm that the npm install kept optional dependencies and that the architecture matches; it will not fall back to plaintext storage.',
+    'credentials.oldReference': 'This credential reference was saved by the old prototype. Re-enter it with setup and save it as a Node credential, or provide environment variables explicitly; old credentials are never read or deleted automatically.',
+    'credentials.missingEntry': 'The system credential entry is missing. Run setup to configure it again.',
+    'prompts.terminalRequired': 'The configuration wizard must run in an interactive terminal. For automation, use setup --template --yes with environment variables.',
+    'prompts.hiddenUnsupported': 'This terminal does not support hidden input. To avoid exposing secrets, it will not fall back to plaintext input; run in a supported terminal or configure with environment variables.',
+    'prompts.hiddenIncomplete': 'Hidden input did not complete; credentials were not saved.',
+    'prompts.cancelled': 'Cancelled.',
+    'prompts.inputTooLong': 'The credential input is too long; nothing was saved.',
+    'channels.emptyTitle': 'The notification title cannot be empty.',
+    'channels.telegramTooLong': 'A Telegram segment still exceeds the message length limit.',
+    'channels.feishuTooLong': 'A Feishu segment still exceeds the request size limit.',
+    'channels.noResponse': 'The server returned no content.',
+    'channels.responseTooLarge': 'The server response is too large; reading stopped.',
+    'channels.notJsonObject': 'The server did not return a JSON object.',
+    'channels.network': 'The network request failed or the response was invalid. To avoid duplicate notifications, it will not resend automatically; this message may not have been delivered.',
+    'channels.rejected': 'The channel rejected this send. Check credentials, recipient authorization, signing, and rate limits.',
+    'channels.sendFailed': 'Sending failed; this message may not have been delivered.',
+    'channels.feishuReplyButton': '💬 Reply to Claude on Telegram',
+    'format.noSpace': 'There is not enough space to split the content.',
+    'format.oneChar': 'There is not enough space for even one character.',
+    'format.telegramHeader': 'The Telegram title or footer is too long, leaving no room for the body.',
+    'format.feishuHeader': 'The Feishu title or footer is too long, leaving no room for the body.',
+    'setup.readFailed': 'Could not read the existing configuration; nothing was changed this time.',
+    'setup.parseFailed': 'The existing configuration could not be parsed and was not overwritten. Fix the JSON first.',
+    'setup.lockUnavailable': 'The configuration write lock is unavailable. Check permissions; if you confirm no wizard is running, you may delete a leftover .setup.lock.',
+    'setup.changedDuringWizard': 'The configuration changed during the wizard and was not overwritten. Try again.',
+    'setup.credentialVerifyFailed': 'Credential verification failed after writing; the configuration was not switched.',
+    'setup.changedDuringSave': 'The configuration changed while saving and was not overwritten. Try again.',
+    'setup.tempCleanupFailed': 'Temporary configuration was not cleaned up: {name}',
+    'setup.credentialCleanupFailed': 'The configuration was not switched, and the new credential could not be cleaned up. Reference ID: {id}',
+    'setup.lockCleanupFailed': 'The configuration write lock was not cleaned up. Confirm no wizard is running, then delete .setup.lock.',
+    'setup.oldCredentialCleanupFailed': 'The configuration was saved, but the old credential was not cleaned up. Reference ID: {id}',
+    'setup.oldSystemRetained': 'The old prototype credential is retained and continues to be managed by the old tool, so the two implementations do not delete each other\'s data.',
+    'setup.path': 'Config path: {file}',
+    'setup.secretsNote': 'Token, webhook, and signing secret are never echoed. They are stored in Windows Credential Manager / macOS Keychain; the configuration file keeps only references.',
+    'setup.channelPrompt': 'Choose notification channels: 1 Telegram, 2 Feishu, 3 both{current} (enter anything else to cancel): ',
+    'setup.credentialUnreadable': 'The current credential cannot be read right now. The entry may be missing, the credential store may be locked, or permissions may be insufficient.',
+    'setup.reenterPrompt': 'Re-enter credentials for the selected channels? [y/N] ',
+    'setup.oldSystemDetected': 'Credentials saved by the old prototype were detected. This run re-enters and saves them as Node credentials; the old credentials remain unchanged.',
+    'setup.secretRequiredKeep': '{label} (hidden input, not echoed; leave blank to keep the current value): ',
+    'setup.secretRequiredNew': '{label} (hidden input, not echoed; not filled from environment variables): ',
+    'setup.secretOptionalKeep': '{label} (hidden input, not echoed; optional; leave blank to keep the current value; enter - to clear): ',
+    'setup.secretOptionalNew': '{label} (hidden input, not echoed; optional; not filled from environment variables; enter - to clear): ',
+    'setup.requiredBlank': 'This field cannot be empty. Enter it again; press Ctrl+C to exit.',
+    'setup.invalidFormat': 'The format is invalid. Enter it again (input is not displayed).',
+    'setup.telegramChatInstruction': 'Have the recipient send the bot a message first, then enter the numeric chat_id; recipients are not fetched or paired automatically here.',
+    'setup.telegramChatPrompt': 'Recipient chat_id, separated by commas (leave blank to keep the current list): ',
+    'setup.telegramChatInvalid': 'Enter at least one valid numeric chat_id; press Ctrl+C to exit.',
+    'setup.channelsEnabled': 'Will enable: {channels}',
+    'setup.envPriority': 'Environment variables take precedence, and empty values also override these settings; the test notification uses the effective configuration.',
+    'setup.envOverrides': 'These environment variables are overriding configuration: {names}',
+    'setup.oldDeleteWarning': 'After a successful save, the old credential will be deleted; if other configurations reference the same credential, update them too.',
+    'setup.disabledChannels': 'Channels that are not selected will be disabled; new credentials are used only for the channels selected this time.',
+    'setup.actionSave': 'save configuration and system credentials',
+    'setup.actionTest': 'send a fixed-content test notification',
+    'setup.actionHooks': 'install Claude Code notification hooks',
+    'setup.continue': 'This will {actions}. Continue? [Y/n] ',
+    'setup.saved': 'Configuration and system credentials saved.',
+    'setup.testSuccess': 'Test notification sent successfully.',
+    'setup.testFailed': 'Configuration saved. The test notification was not sent successfully; run dev-notify doctor to check.',
+    'setup.testFailedEnv': 'Configuration saved. The test notification was not sent successfully, possibly due to environment overrides or a network problem; run dev-notify doctor to check.',
+    'setup.testSkipped': 'Test notification skipped.',
+    'setup.hooksFailed': 'Configuration saved. Claude Code hooks were not fully installed: {reason}',
+    'setup.hooksCheckHint': 'run integration claude-code status to check',
+    'setup.replyHint': 'To reply to Claude in Telegram, run: dev-notify reply setup',
+    'setup.clearNoReference': 'The current configuration has no system credential reference; nothing to clear.',
+    'setup.clearOldBackend': 'This credential was saved by the old prototype; the Node version will not delete across implementations. Use the old tool to handle it.',
+    'setup.clearWarning': 'This will delete the system credential referenced by the current configuration and remove the reference. Environment variables are unaffected; other configurations sharing the same credential will also stop working.',
+    'setup.clearConfirm': 'Clear it? [y/N] ',
+    'setup.cleared': 'Credential reference removed. If deleting the system entry failed, a notice is shown above.',
+    'setup.channelTelegram': 'Telegram ({count} recipients)',
+    'setup.channelFeishu': 'Feishu',
+    'setup.labelFeishuWebhook': 'Feishu webhook',
+    'setup.labelFeishuSecret': 'Feishu signing secret',
+    'cli.help': `dev-notify {version} — cross-platform developer task notifications
+
+Commands:
+  send --title TITLE [--content TEXT | --content-file FILE | --stdin]
+       [--channel all|telegram|feishu] [--level info|success|warn|error]
+       [--footer NOTE] [--dry-run]
+  setup [--no-test] [--no-hooks]
+                            Configure channels and system credentials; by default
+                            also sends a test and installs Claude Code notification
+                            hooks after one confirmation
+  setup --template [--yes]  Create a secret-free template only; does not overwrite
+                            existing configuration or install hooks
+  credentials clear         Remove the current Node credential reference and entry
+                            (requires confirmation)
+  paths                     Show configuration paths (does not write files)
+  doctor / status           Offline check (does not send messages)
+  update [--check] [--yes] [--no-post]
+                            Check for and install the latest npm version, then
+                            maintain hooks and the bridge
+  integration list          List available integrations
+  integration claude-code install / status / remove
+                            Install, query, or remove user-level hooks separately
+                            (install/remove accept --yes)
+  reply setup               Authorize trusted Telegram private-chat users
+  reply start / status / stop
+                            Start, query, or stop the reply bridge
+  reply disable             Revoke remote reply authorization and stop the bridge
+                            (requires confirmation)
+  reply run                 Run the bridge in the foreground (for diagnostics,
+                            no system auto-start)
+  language [zh|en]          Show or change the saved interface language
+
+Global options: --config PATH, --lang zh|en, --help, --version
+Environment: TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID / TELEGRAM_CHAT_IDS,
+             FEISHU_WEBHOOK, FEISHU_SECRET; explicitly present values take
+             precedence. DEV_NOTIFY_LANG=zh|en switches the interface language.
+             See README for details.
+System credentials are stored in Windows Credential Manager / macOS Keychain;
+secrets are never written in plaintext.`,
+    'cli.invalidArgs': 'Invalid arguments. Run --help for usage.',
+    'cli.invalidCommand': 'The command or option combination is invalid. Run --help for usage.',
+    'cli.invalidLanguage': 'The language must be zh or en: {value}',
+    'cli.integrationList': 'claude-code: supports notifications, Telegram replies, and structured question interaction. Notification hooks and reply permission are separate; by default only notifications are sent and no remote input is accepted.',
+    'cli.integrationUsage': 'Use integration list, or integration claude-code install / status / remove.',
+    'cli.integrationStatusFile': 'Claude Code user-level settings: {file}',
+    'cli.integrationStatusCounts': 'dev-notify hooks: Stop {stop}, Notification {notification}, session lifecycle {lifecycle}/3, interaction and result confirmation {interaction}/5; other handlers {others}.',
+    'cli.integrationDisabled': 'This file enables disableAllHooks, so hooks will not take effect after installation; lift the disablement yourself.',
+    'cli.integrationStatusNote': 'Only the user-level file is checked here. Actual loading also depends on project and managed policy; confirm in Claude Code /hooks.',
+    'cli.setupChannelFirst': 'Run setup to configure at least one notification channel before installing Claude Code hooks.',
+    'cli.replyUsage': 'Use reply setup / start / status / stop / disable / run.',
+    'cli.credentialsUsage': 'credentials currently supports only clear, and requires confirmation in an interactive terminal.',
+    'cli.yesTemplateOnly': '--yes can only be used with --template; confirmation is still required before saving secrets.',
+    'cli.sendTitle': 'send requires a non-empty --title.',
+    'cli.sendSources': 'Choose only one of --content, --content-file, and --stdin.',
+    'cli.channelLevel': 'The channel or notification level is invalid.',
+    'cli.segmentationFailed': '{channel}: could not split safely. Shorten the title or footer, or check the body format.',
+    'cli.dryRun': '{channel}: recipients {recipients}, planned requests {items} (dry-run, nothing sent)',
+    'cli.sent': '{channel}: sent {sent}/{planned} messages',
+    'cli.testSent': '{channel}: test sent {sent}/{planned} messages',
+    'cli.noChannels': 'No usable channel. Configure environment credentials and recipients first.',
+    'cli.channelNotReady': 'This channel is not enabled or its configuration is incomplete.',
+    'cli.testTitle': 'dev-notify configuration test',
+    'cli.testContent': 'This is a test notification you confirmed sending.',
+    'cli.setupNoteTest': 'After saving, a fixed-content test notification will be sent to the effective recipients.',
+    'cli.setupNoteHooksPath': 'Claude Code user-level settings: {path}',
+    'cli.setupNoteHooksScope': 'Notification hooks will be installed for all projects using this settings file. Final reply text may contain sensitive content and will be sent to the channels in effect.',
+    'cli.setupNoteHooksLifecycle': 'Session lifecycle and structured question hooks are installed at the same time. Remote input is enabled only after running reply setup to authorize it.',
+    'cli.skipHooks': 'Skipping Claude Code hooks: {reason}',
+    'cli.skipHooksNoPath': 'Skipping Claude Code hooks: no user-level settings path was found.',
+    'cli.templateWillCreate': 'Will create a secret-free template: {file}. It will not use the network or modify hooks.',
+    'cli.templateCancelled': 'Cancelled; nothing was written.',
+    'cli.templateCreated': 'Template created. Configure environment credentials and recipients.',
+    'cli.configPath': 'Config path: {file}',
+    'cli.channelReady': 'configuration complete (network not verified)',
+    'cli.channelNotReadyStatus': 'not enabled or configuration incomplete',
+    'cli.channelStatus': '{channel}: {status}',
+    'cli.credentialsNote': 'Credentials: environment variables take precedence, then system credentials; this check does not use the network, and the system may prompt for authorization.',
+    'cli.confirmTemplate': 'Create the template? [y/N] ',
+    'cli.nonInteractive': 'This is not an interactive terminal. For automation, use setup --template --yes.',
+    'cli.replySaved': 'Authorization saved. Confirm hooks are installed, then run reply start. Reply mappings for old messages are not retained.',
+    'cli.bridgeStopped': 'The bridge is stopped or was not running.',
+    'cli.replyDisabled': 'Authorization revoked and stop requested. Calls already in progress cannot be withdrawn.',
+    'cli.stopStopped': 'The bridge is stopped or was not running. Authorization remains, and a later event may start it again; to shut it down completely, run reply disable.',
+    'cli.stopRequested': 'Stop requested; the bridge is exiting. Run reply status to check.',
+    'cli.replyStatusAccess': 'Remote replies: {users} authorized private-chat users; per-request tool permission {state}.',
+    'cli.replyPermissionOn': 'enabled',
+    'cli.replyPermissionOff': 'not enabled',
+    'cli.replyStatusNoAccess': 'Remote replies: not enabled.',
+    'cli.bridgeReady': 'Bridge: ready.',
+    'cli.bridgeStarting': 'Bridge: process exists but is not ready yet.',
+    'cli.bridgeNotRunning': 'Bridge: not running.',
+    'cli.replyStartReady': 'Reply bridge ready. Enter from a new task notification.',
+    'cli.replyStartNotReady': 'The bridge is not ready yet. Run reply status or reply run to see why; if an old bridge is running, stop it first.',
+    'cli.languageCurrent': 'Current language: {language} ({code}).',
+    'cli.languageChanged': 'Language changed to {language} ({code}).',
+    'cli.languageAlready': 'Already using {language} ({code}).',
+    'cli.languageHint': 'Use language zh or language en to switch and save.',
+    'update.npmUnavailable': 'Could not run npm. Confirm npm is installed and on PATH.',
+    'update.checkNetwork': 'Could not check the latest version. Check the network and try again.',
+    'update.checkHttp': 'Could not check the latest version (HTTP {status}). Check the network and try again.',
+    'update.parseRegistry': 'The version information returned by the npm registry could not be parsed.',
+    'update.registryVersion': 'The npm registry returned an unsupported version format.',
+    'update.versionFormat': 'The version format is not supported.',
+    'update.terminalRequired': 'Updates must be confirmed in an interactive terminal; for non-interactive use, run dev-notify update --yes.',
+    'update.confirm': 'Update to {latest}? [y/N] ',
+    'update.manualPost': 'If Claude Code hooks are installed, run dev-notify integration claude-code install; if remote replies are in use, restart the bridge.',
+    'update.partialUpdated': 'The update completed, but not all post-update maintenance steps succeeded; check the notices above.',
+    'update.partial': 'Not all maintenance steps succeeded; check the notices above.',
+    'update.postDoneUpdated': 'Post-update maintenance completed.',
+    'update.postDone': 'Maintenance completed.',
+    'update.currentFormat': 'The current version format is not supported, so updates cannot be checked.',
+    'update.upToDate': 'Already up to date: {version}.',
+    'update.maintenanceNote': 'Claude Code hooks and reply bridge maintenance will run.',
+    'update.versions': 'Current version {current}; latest npm version {latest}.',
+    'update.checkHint': 'Run dev-notify update to update.',
+    'update.postNote': 'After updating, Claude Code hooks bound to the current configuration will be reinstalled and a running reply bridge restarted; use --no-post to skip.',
+    'update.cancelled': 'Cancelled; no update was performed.',
+    'update.running': 'Running npm install -g {name}@{latest} ...',
+    'update.failed': 'The update did not complete. Check npm permissions, or run npm install -g {name}@latest manually.',
+    'update.updated': 'Updated to {latest}. Reopen the terminal and run dev-notify --version to confirm.',
+    'maintenance.runFailed': 'Could not run the updated dev-notify. Reopen the terminal and run dev-notify --version to check.',
+    'maintenance.reasonHint': 'Run dev-notify integration claude-code status or dev-notify reply status to check.',
+    'maintenance.hooksCheckFailed': 'Could not check Claude Code hooks: {reason}',
+    'maintenance.noHooks': 'No dev-notify Claude Code hooks detected; skipping.',
+    'maintenance.otherConfig': 'Claude Code hooks are bound to another notification configuration; skipping automatic update. To update them, run integration claude-code install with the original --config.',
+    'maintenance.updatingHooks': 'Updating Claude Code hooks ...',
+    'maintenance.hooksUpdated': 'Claude Code hooks updated.',
+    'maintenance.hooksFailed': 'Claude Code hooks update failed.',
+    'maintenance.hooksFailedReason': 'Claude Code hooks update failed: {reason}',
+    'maintenance.bridgeCheckFailed': 'Could not check the reply bridge: {reason}',
+    'maintenance.restartingBridge': 'Restarting the reply bridge ...',
+    'maintenance.bridgeStillRunning': 'The reply bridge is still exiting; run dev-notify reply start later.',
+    'maintenance.bridgeRestarted': 'Reply bridge restarted.',
+    'maintenance.bridgeStartFailed': 'The reply bridge failed to start.',
+    'maintenance.bridgeRestartFailed': 'The reply bridge failed to restart: {reason}',
+    'maintenance.noBridge': 'No running reply bridge detected; skipping.',
+    'claude.settingsAbsolute': 'CLAUDE_CONFIG_DIR must be an absolute path; Claude Code settings were not changed',
+    'claude.settingsTooLarge': 'Claude Code settings exceed 1 MiB; the operation stopped and the file was not changed.',
+    'claude.settingsReadFailed': 'Could not read Claude Code settings; the operation stopped.',
+    'claude.settingsInvalidJson': 'Claude Code settings are not valid UTF-8 JSON and were not overwritten.',
+    'claude.settingsInvalidShape': 'Claude Code settings or hooks structure is invalid and was not overwritten.',
+    'claude.hooksInvalidShape': 'The Claude Code hook array structure is invalid and was not overwritten.',
+    'claude.lockUnavailable': 'Could not acquire the Claude Code settings write lock. Confirm no installation process is running, then handle a leftover .dev-notify.lock.',
+    'claude.changedDuringConfirm': 'Claude Code settings changed during confirmation and were not overwritten. Try again.',
+    'claude.changedDuringSave': 'Claude Code settings changed while saving and were not overwritten. Try again.',
+    'claude.tempCleanupFailed': 'Temporary file cleanup failed. Delete .dev-notify-*.tmp after installation.',
+    'claude.lockCleanupFailed': 'Lock file cleanup failed. Delete .dev-notify.lock after installation.',
+    'claude.settingsPath': 'Claude Code user-level settings: {file}',
+    'claude.noHooks': 'No hooks added by this tool were found; settings were not changed.',
+    'claude.alreadyInstalled': 'This tool\'s hooks are already installed and match the configuration; nothing was added.',
+    'claude.configPath': 'Notification configuration: {config}',
+    'claude.installScope': 'Notifications will be enabled for all projects under this Claude Code configuration directory: the final reply is sent when a task ends, and reminders appear when your confirmation or input is needed.',
+    'claude.installSensitive': 'Final replies and reminder text may contain sensitive content and will be sent to the effective Telegram / Feishu channels. Environment variables still take precedence.',
+    'claude.installLifecycle': 'Session lifecycle and structured question hooks are installed at the same time. Remote input requires separate authorization with reply setup.',
+    'claude.installReads': 'The full transcript is not read. After replies are enabled, session process metadata is read; structured questions or permission requests send the corresponding question and tool information.',
+    'claude.installTiming': 'PreToolUse only registers call identity; PermissionRequest waits in parallel with the local terminal window, and remote answers are valid for 10 minutes. Completion events are used only for result feedback and never answer on your behalf. Checked against Claude Code 2.1.316; other versions or host environments require separate verification.',
+    'claude.otherHandlers': 'This file contains {count} other related handlers, which may cause duplicate notifications.',
+    'claude.projectHooks': 'Project-level or plugin hooks may also be active; this tool will not automatically migrate or delete old hooks.',
+    'claude.disabledWarning': 'Note: this file enables disableAllHooks, so hooks will not take effect after installation; lift the disablement yourself.',
+    'claude.removeScope': 'Only notification, lifecycle, and interaction handlers added by this tool are removed; other settings, hooks, notification configuration, and system credentials are preserved. To stop the reply bridge, run reply disable or reply stop.',
+    'claude.confirmInstall': 'Install these Claude Code hooks? [y/N] ',
+    'claude.confirmRemove': 'Remove this tool\'s Claude Code hooks? [y/N] ',
+    'claude.cancelled': 'Cancelled; Claude Code settings were not changed.',
+    'claude.installed': 'Claude Code hooks installed. Check and confirm them in /hooks; if they do not take effect, restart the session.',
+    'claude.removed': 'This tool\'s Claude Code hooks were removed. Check /hooks and restart the session if necessary.',
+    'hook.timeout': 'Claude Code hook input timed out; the notification was not sent.',
+    'hook.tooLarge': 'Claude Code hook input exceeds the size limit; the notification was not sent and the content was not truncated.',
+    'hook.footerProject': 'Project: {value}',
+    'hook.footerTopic': 'Topic: {value}',
+    'hook.footerSession': 'Session: {value}',
+    'hook.invalidJson': 'Claude Code hook input is not valid UTF-8 JSON; the notification was not sent.',
+    'hook.notObject': 'Claude Code hook input must be a JSON object.',
+    'hook.invalidStopState': 'The Claude Code Stop state field is invalid.',
+    'hook.invalidReply': 'The Claude Code final reply field is invalid.',
+    'hook.replyTitle': 'Claude Code reply complete',
+    'hook.replyFallback': 'This turn has ended, but Claude Code did not provide final text. Return to the terminal; the session file is not read to fill in the body, to avoid showing stale content.',
+    'hook.invalidNotification': 'The Claude Code notification body field is invalid.',
+    'hook.notificationTitle': 'Claude Code needs your input',
+    'hook.notificationFallback': 'Claude Code is waiting for your confirmation or input. Return to the terminal to handle it.',
+    'hook.interactionFailed': 'Claude Code reply state or interaction handling failed. No answer or permission was selected automatically; handle it locally.',
+    'hook.sessionNameFailed': 'Could not read the Claude Code session name; the topic will be omitted from the notification footer.',
+    'hook.replyNotReady': 'Remote replies are not ready yet; a normal notification will still be attempted.',
+    'hook.coverageFailed': 'Could not verify question-notification coverage; the general permission reminder will be kept.',
+    'hook.sendIncomplete': '{channel}: the Claude Code notification was not fully sent. The message will not be resent automatically.',
+    'hook.sendFailed': '{channel}: the Claude Code notification failed to send. Check configuration, system credentials, and network; the message will not be resent automatically.',
+    'hook.noChannels': 'No usable channel for Claude Code notifications. Run dev-notify doctor to check.',
+    'reply.readFailed': 'Could not read reply configuration or state. To avoid overwriting existing data, remote input was not enabled.',
+    'reply.lockUnavailable': 'Could not acquire the reply state write lock.',
+    'reply.lockBusy': 'The reply state lock is busy. Confirm the relevant processes have exited, then handle the leftover lock.',
+    'reply.invalidPolicy': 'The reply authorization configuration is invalid; remote input is disabled.',
+    'reply.hooksMissing': 'Required reply hooks are missing, timed unsafely, or disabled. Re-run integration claude-code install and confirm loading in /hooks.',
+    'reply.botChanged': 'The Telegram bot changed or is unavailable. Re-run reply setup to authorize again.',
+    'reply.usersRevoked': 'Authorized users are no longer in the current Telegram recipient list; remote input is disabled.',
+    'reply.authorizationChanged': 'Reply authorization was revoked or changed; old state was not written.',
+    'reply.invalidState': 'The reply state structure is invalid; remote input is disabled.',
+    'reply.setupHooksFirst': 'Run integration claude-code install first to install the complete hooks bound to this notification configuration, then configure replies.',
+    'reply.setupTelegramFirst': 'Replying to Claude requires a configured Telegram bot and private-chat recipients.',
+    'reply.setupPrivateOnly': 'Remote replies support only Telegram private-chat users, not group chats.',
+    'reply.setupNoticeInput': 'Remote replies are equivalent to typing and submitting content in the local Claude Code terminal. They can submit Claude commands but never approve tool permissions automatically. Authorize only trusted users.',
+    'reply.setupNoticeBridge': 'Feishu buttons jump to Telegram and do not receive Feishu messages directly. This feature needs exclusive getUpdates access to the bot; do not share the same bot with an old bridge or other machines.',
+    'reply.setupNoticePlatform': 'Windows uses the system PowerShell / console API; macOS uses Ghostty or tmux and requires the corresponding system permissions.',
+    'reply.setupNoticeUnsupported': 'VS Code integrated terminal, WSL, and SSH are not supported. Input is refused when the target is uncertain or the session has switched.',
+    'reply.setupAvailable': 'Notification recipients do not automatically gain input rights. Available private-chat chat_id values: {users}',
+    'reply.setupPrompt': 'Enter the private-chat chat_id to authorize (comma-separated; leave blank to cancel): ',
+    'reply.setupInvalidUser': 'You can authorize only private-chat users in the current notification list.',
+    'reply.setupAuthorizing': 'Remote input will be authorized for: {users}',
+    'reply.setupSensitive': 'Structured questions show the real options and support custom answers; normal replies are entered after the current turn ends. Questions, options, and tool request parameters may contain sensitive information and will be sent to authorized private chats and configured Feishu.',
+    'reply.setupPermissionsPrompt': 'Allow these users to approve or deny tool permissions one request at a time? This does not modify permanent rules. [y/N] ',
+    'reply.setupConfirm': 'Enable remote replies and accept the permission scope above? [y/N] ',
+    'reply.setupChanged': 'Reply authorization was modified by another process. Try again.',
+    'reply.setupConfigChanged': 'The notification configuration changed during authorization. Try again.',
+    'reply.setupSaved': 'Authorization saved. Reply mappings for old messages are not retained; enter from task-completion notifications created after enabling.',
+    'reply.disableNotEnabled': 'Remote replies are not enabled.',
+    'reply.disableConfirm': 'Disable remote replies? Notifications and credentials will be preserved. [y/N] ',
+    'reply.disableChanged': 'Reply authorization changed. Try again.',
+    'reply.disabled': 'Remote replies disabled. Operations already in progress cannot be withdrawn; the bridge will exit on its next check.',
+    'reply.endSessionReason': 'The session ended, or its identity could not be verified',
+    'reply.endSwitchedReason': 'The session switched',
+    'reply.endTurnReason': 'This turn ended',
+    'reply.endLocalReason': 'A new task or session started locally',
+    'reply.receivedTitle': '✅ Claude received your reply',
+    'reply.receivedBody': 'Claude received your reply and will send another notification when the task completes.',
+    'reply.receivedTelegramFailed': 'Telegram: the receipt confirmation was not sent; the submitted input will not be replayed.',
+    'reply.receivedFeishuBody': 'Claude received your reply and will send another notification when the task completes. The reply text is not forwarded here to reduce exposure.',
+    'reply.receivedFeishuFooter': 'Session: {session}',
+    'reply.receivedFeishuIncomplete': 'Feishu: the receipt confirmation was not fully sent; the submitted input will not be replayed.',
+    'reply.receivedFeishuFailed': 'Feishu: the receipt confirmation failed to send; the submitted input will not be replayed.',
+    'reply.bridgeNotReadyButton': 'The reply bridge is not ready yet, so this notification will not show a reply button. Run reply status to see why.',
+    'reply.botUsernameInvalid': 'The Telegram bot username is invalid; the reply button was not enabled.',
+    'reply.noMessageId': 'The notification did not return a Telegram message ID to associate with.',
+    'reply.noSession': 'Could not verify the session; the structured interaction will be handled locally.',
+    'reply.noMatchingCall': 'Could not uniquely match this tool call; remote interaction was not enabled and the local window is unaffected.',
+    'reply.bridgeNotReadyQuestion': 'The reply bridge is not ready yet; the question will be handled locally.',
+    'reply.permissionRequest': 'Tool permission request: {tool}',
+    'reply.interactionEnded': 'The remote interaction ended, or no answer was submitted. Nothing is answered automatically; local operation is unaffected.',
+    'reply.interactionFailed': 'Remote interaction handling failed. Check locally.',
+    'reply.interactionCancelled': 'The interaction wait was cancelled; whether the remote answer took effect is not yet confirmed.',
+    'reply.sessionGoneTitle': '⚠️ Cannot reply',
+    'reply.sessionGoneBody': 'This session has closed or switched, or this notification has expired. Enter from the latest notification.',
+    'reply.replyPromptTitle': '💬 Reply to Claude',
+    'reply.replyPromptBody': 'Reply to this message with your input. It will be submitted to the corresponding local session.\nSession: {session}',
+    'reply.replyPromptLongPress': 'Long-press this message and choose "Reply", then enter your input. It will be submitted to the corresponding local session.\nSession: {session}',
+    'reply.processingFailedCallback': 'Processing did not complete. Check the terminal; nothing will be resubmitted automatically.',
+    'reply.processingFailedTitle': '⚠️ This submission did not complete',
+    'reply.processingFailedBody': 'An error occurred while processing. This submission may or may not have been registered or applied. Check the terminal and later results; nothing will be resubmitted automatically.',
+    'reply.interactionExpiredCallback': 'The session is closed, or this interaction has expired.',
+    'reply.interactionExpiredTitle': '⚠️ This submission did not take effect',
+    'reply.interactionExpiredBody': 'The session closed or switched, or the interaction expired; the answer was not returned.',
+    'reply.replyBoxHint': 'Please type in the reply box',
+    'reply.staleTitle': '⚠️ This submission did not take effect',
+    'reply.staleBody': 'This message is past its validity window; the answer was not returned. Check the latest question or the terminal state.',
+    'reply.howToTitle': '💬 How to reply',
+    'reply.howToBody': 'Reply directly to the task-completion notification, or tap the "Reply to Claude" button in the notification.',
+    'reply.expiredReplyBody': 'The notification expired, or the corresponding session closed or switched. Reply from the latest notification.',
+    'reply.replyFailedTitle': '❌ Reply not submitted',
+    'reply.invalidInput': 'Invalid input.',
+    'reply.sessionChanged': 'The session changed; this reply was not submitted.',
+    'reply.pendingTitle': '⏳ New reply not submitted',
+    'reply.pendingBody': 'This session already has a reply awaiting confirmation. Wait for confirmation, or check the local terminal and try again.',
+    'reply.queuedTitle': '⏳ Reply queued',
+    'reply.queuedBody': 'Claude is working on the current task; the local queue will try to submit after this turn ends and will not type text into a permission prompt that is waiting.',
+    'reply.queueExpired': 'The queued reply is more than 5 minutes old and was not submitted. Check the local machine and reply again.',
+    'reply.sessionClosed': 'The session is closed or switched; this reply was not submitted.',
+    'reply.forwardedTitle': '✅ Forwarded to Claude',
+    'reply.forwardedBody': 'Terminal input was submitted; waiting for UserPromptSubmit confirmation.',
+    'reply.forwardUnknownTitle': '⚠️ Forward status unconfirmed',
+    'reply.forwardFailed': 'The submission did not complete. Check the local terminal; nothing will be resubmitted automatically.',
+    'reply.invalidQuestions': 'The question structure is invalid; answer locally.',
+    'reply.permissionsNotAuthorized': 'Remote handling of tool permissions is not authorized.',
+    'reply.targetChanged': 'The session target changed.',
+    'reply.callUnavailable': 'The call has ended or is already bound; no remote question was created.',
+    'reply.questionSwitched': 'The question switched; the old request no longer accepts answers.',
+    'reply.allowButton': '✅ Allow this time',
+    'reply.denyButton': '⛔ Deny',
+    'reply.customDenyButton': '✍️ Custom deny reason',
+    'reply.submitSelected': 'Submit selected',
+    'reply.customInput': '✍️ Custom input',
+    'reply.closeRemote': 'Close remote answering (local still works)',
+    'reply.toolLabel': 'Tool: {tool}',
+    'reply.unknownTool': 'unknown',
+    'reply.permissionNote': 'This handles allow, deny, or a custom deny reason for this request. Claude did not provide the complete local button list, so no permanent permission rule is created here.',
+    'reply.questionHeading': 'Question {index}/{total}: {question}',
+    'reply.multiSelectHint': '\n\nYou can select multiple options, then tap "Submit selected"; custom input is also available.',
+    'reply.singleSelectHint': '\n\nTap an option to answer directly, or choose custom input.',
+    'reply.localWindowNote': '\nThe local native window can also answer at the same time; the first complete answer Claude receives takes effect. Remote windows are valid for 10 minutes and never auto-select.',
+    'reply.feishuMultiSelectHint': '\n\nMulti-select: open Telegram, select options one by one, then tap "Submit selected"; custom input is also available.',
+    'reply.feishuSingleSelectHint': '\n\nOpen Telegram, then tap an option to answer directly, or choose custom input.',
+    'reply.inactiveTitle': '⚠️ Interaction expired',
+    'reply.inactiveBody': 'Enter from the latest notification, or handle it locally.',
+    'reply.noInteractionMessageId': 'The interaction notification did not return a message ID.',
+    'reply.interactionNotSent': 'The interaction notification was not fully sent; handle it locally.',
+    'reply.closedLocal': 'Remote answering was closed; local handling is unaffected.',
+    'reply.callbackExpired': 'Not submitted: the button expired, or an answer is already awaiting confirmation.',
+    'reply.callbackClosed': 'Remote answering was closed; local handling is unaffected.',
+    'reply.callbackRegistered': 'Answer registered; effectiveness not yet confirmed.',
+    'reply.callbackUpdated': 'Updated.',
+    'reply.pendingConfirmationTitle': '⏳ Answer registered, awaiting confirmation',
+    'reply.pendingRemaining': 'The remaining questions still need answers before the full answer is returned.',
+    'reply.pendingSubmitted': 'The answer is being returned; whether Claude uses it will be reported later.',
+    'reply.pendingFooter': '\nThe result will be reported later; if you never receive it, check the terminal.\nRequest: {id}',
+    'reply.notAppliedTitle': '⚠️ This submission did not take effect',
+    'reply.notAppliedBody': 'This operation was not submitted: the question was already handled, expired, switched, or an answer is already awaiting confirmation.\nRequest: {id}',
+    'reply.denyInstruction': 'Reply to this message with the deny reason. This reason does not approve the permission.',
+    'reply.answerInstruction': 'Reply to this message with the complete answer to this question.',
+    'reply.answerInvalidTitle': '❌ Answer not submitted',
+    'reply.answerInvalidBody': 'Enter an answer of at most 4000 characters; the content will not be truncated.',
+    'reply.finalWaiting': 'Waiting for Claude to confirm; the final result will be reported later. If you never receive it, check the terminal.',
+    'reply.nextWaiting': 'The remaining questions still need answers before the full answer is returned; it has not taken effect yet.',
+    'reply.notSubmitted': 'This operation was not submitted: the question has ended, expired, switched, or an answer is already awaiting confirmation.',
+    'reply.requestLine': '\nRequest: {id}',
+    'reply.expiredUnsentAnswer': 'Remote answering timed out; no answer was submitted. You can still continue locally.',
+    'reply.buttonUnknown': 'Closed · result pending verification',
+    'reply.buttonApplied': 'Handled · no more answers',
+    'reply.buttonExpired': 'Expired · unanswered',
+    'reply.buttonInvalid': 'Invalid · unanswered',
+    'reply.buttonClosed': 'Closed · no more answers',
+    'reply.buttonProcessed': 'Handled · no more answers',
+    'reply.buttonEnded': 'Ended · no more answers',
+    'reply.sessionUnknownSuffix': '; no effectiveness confirmation was received for this answer. Check the terminal.',
+    'reply.sessionUnsentSuffix': '; this remote answer was not returned.',
+    'reply.earlierHandled': 'The local machine or another client handled it first; this Telegram answer was not submitted.',
+    'reply.noVerifiableResult': 'Claude ended this question but did not return a verifiable result. Check the terminal.',
+    'reply.answerApplied': 'Claude confirmed an answer matching what you submitted was used. If the local machine submitted identical content, this result cannot show which side took effect.',
+    'reply.answerNotApplied': 'Claude ended the question without using the answer you submitted; the local machine or another client may have handled it first.',
+    'reply.questionProcessed': 'The question was handled; old buttons have expired.',
+    'reply.permissionApplied': 'The tool was allowed and completed. If the local machine also approved it, this completion event cannot show which side allowed it.',
+    'reply.permissionNotApplied': 'The tool was allowed and executed; this remote decision did not prevent it.',
+    'reply.toolFailedUnknown': 'Tool execution failed, was denied, or was cancelled. This event cannot show whether the remote decision took effect. Check the terminal.',
+    'reply.toolFailed': 'The request failed, was denied, or was cancelled; this remote decision was not returned.',
+    'reply.waitTimeoutUnknown': 'Timed out waiting for effectiveness confirmation, or the session switched. The result is currently unknown. Check the terminal.',
+    'reply.sessionEndedUnsent': 'The session ended or switched; the remote answer was not returned. You can still continue in the local interface.',
+    'reply.expiredUnanswered': 'Remote answering timed out; no answer was submitted. You can still continue in the local interface.',
+    'reply.appliedTitle': '✅ Answer content took effect',
+    'reply.resultUnknownTitle': '⚠️ Submission result cannot be confirmed yet',
+    'reply.requestLabel': 'Request: {id}',
+    'reply.feedbackFailedLog': 'The Telegram result feedback was not sent. It will not be resent automatically; answers already used are unaffected.',
+    'reply.clearButtonsFailedLog': 'Telegram old buttons were not removed. The server will still reject this request.',
+    'reply.platformTimeout': 'The system session operation timed out. Input may have been partially delivered; to avoid duplicate submission, it will not be retried automatically.',
+    'reply.platformFailed': 'The system session operation failed. To avoid leaking commands or input, underlying details are not shown.',
+    'reply.emptyReply': 'Reply content cannot be empty.',
+    'reply.replyTooLong': 'The reply exceeds 4000 characters and was not submitted. The content will not be truncated or split into multiple messages.',
+    'reply.emptyAfterCleanup': 'The reply has no content left to submit after cleanup.',
+    'reply.targetInvalid': 'The session is closed or switched, or its identity cannot be verified. Reply from the latest notification.',
+    'reply.windowsPartial': 'Windows console injection failed and may have written only part of the text. It will not retry automatically; check the terminal.',
+    'reply.unsupportedPlatform': 'Remote replies support only Windows and macOS.',
+    'reply.tmuxBufferFailed': 'Failed to create the tmux input buffer; this reply was not submitted.',
+    'reply.tmuxChanged': 'The session changed; this reply was not submitted.',
+    'reply.tmuxPasteFailed': 'tmux paste failed and may have delivered only part of the text. It will not retry automatically.',
+    'reply.tmuxSubmitFailed': 'tmux submission failed; the text may already be entered. It will not retry automatically.',
+    'reply.ghosttyFailed': 'Ghostty did not find the target window, or injection failed. It will not fall back to another window or retype the input.',
+    'reply.telegramMethod': 'Unsupported Telegram bridge method',
+    'reply.telegramConflict': 'Telegram polling conflict; check for an old bridge, another machine, or a webhook. The bridge will not take over or delete a webhook',
+    'reply.telegramRequestFailed': 'The Telegram bridge request failed; the server body and secrets are not printed',
+    'reply.bridgeAuthFirst': 'Remote replies are not authorized yet. Run reply setup first.',
+    'reply.bridgeNotAuthorized': 'Remote replies are not authorized yet.',
+    'reply.bridgeLocked': 'A bridge for the same bot is already running for this user, or a lock file was left behind. Confirm the process has exited, then handle the corresponding lock in reply-bots.',
+    'reply.webhookConflict': 'This bot already has a webhook and cannot use getUpdates at the same time. Remove the webhook first; this tool will not delete it automatically.',
+    'reply.pollFailedLog': 'Telegram polling failed; no secrets or server body are written to the log.',
+    'reply.pollFailedFatal': 'Telegram polling failed 5 times in a row; the bridge has exited. Check the network, token, or API conflicts, then start it again.',
+    'reply.updatesInvalid': 'The Telegram update format is invalid.',
+    'reply.handleFailedLog': 'Reply handling failed. This update will not be replayed; check the terminal, or retry from the latest notification.',
+    'reply.bridgeFailed': 'The bridge failed to start or run; to avoid leaking secrets, the underlying error is not shown.',
+    'channels.telegramReplyButton': '💬 Reply to Claude',
+};
+let current = 'zh';
+export function setLocale(locale) { current = locale; }
+export function getLocale() { return current; }
+export function parseLocale(value) {
+    if (typeof value !== 'string')
+        return undefined;
+    const normalized = value.trim().toLowerCase();
+    if (['zh', 'zh-cn', 'zh_cn'].includes(normalized))
+        return 'zh';
+    if (['en', 'en-us', 'en_us'].includes(normalized))
+        return 'en';
+    return undefined;
+}
+export function resolveLocale(explicit, env, configured) {
+    return parseLocale(explicit) ?? parseLocale(env.DEV_NOTIFY_LANG) ?? parseLocale(configured) ?? 'zh';
+}
+export function localeName(locale = current) {
+    return locale === 'zh' ? '简体中文' : 'English';
+}
+export function joinList(items) {
+    return items.join(current === 'zh' ? '、' : ', ');
+}
+export function t(key, params = {}) {
+    const message = current === 'en' ? en[key] : zh[key];
+    if (typeof message === 'function')
+        return message(params);
+    return message.replace(/\{(\w+)\}/g, (match, name) => Object.hasOwn(params, name) ? String(params[name]) : match);
+}