From 1d240617439536212bb43938c4cfcac2c7556c2f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E5=8F=AF=E4=B9=90?= <uni_kevin@outlook.com>
Date: Sat, 17 Oct 2026 06:00:49 +0800
Subject: [PATCH 01/18] i18n(zh): translate remaining Simplified Chinese
 messages and commonlib strings
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- Add the 18 catalogue entries added since the last zh update.
- Translate 68 zh entries that still held the English text
  (setup, doctor, tweak-mismatch, P2P and replicator dialogues).
- Translate 80 commonlib messages and setting labels which reach the
  LiveSync translator but were not in the catalogue, and add their
  canonical English to en.yaml so other languages keep the English
  fallback and the coverage report can see them.
- Add a space in the zh P2P sync title (Peer-to-Peer 同步).

Regenerated with npm run i18n:bake.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
 src/common/messages/combinedMessages.prod.ts |  505 +++++++--
 src/common/messagesJson/en.json              |   80 ++
 src/common/messagesJson/zh.json              | 1044 ++++++++++--------
 src/common/messagesYAML/en.yaml              |  153 +++
 src/common/messagesYAML/zh.yaml              |  499 +++++----
 5 files changed, 1499 insertions(+), 782 deletions(-)

diff --git a/src/common/messages/combinedMessages.prod.ts b/src/common/messages/combinedMessages.prod.ts
index 140a5af8..66cff47b 100644
--- a/src/common/messages/combinedMessages.prod.ts
+++ b/src/common/messages/combinedMessages.prod.ts
@@ -401,6 +401,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "生效中的远程配置",
         "zh-tw": "目前啟用的遠端設定",
     },
+    "Active Remote Type": {
+        def: "Active Remote Type",
+        zh: "当前使用的远程类型",
+    },
     "Add default patterns": {
         def: "Add default patterns",
         es: "Añadir patrones predeterminados",
@@ -521,6 +525,18 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "永久允许",
         "zh-tw": "永久允許",
     },
+    "Allow sleep during synchronisation": {
+        def: "Allow sleep during synchronisation",
+        zh: "同步期间允许睡眠",
+    },
+    "Allow sleep during synchronisation on the desktop": {
+        def: "Allow sleep during synchronisation on the desktop",
+        zh: "桌面端同步期间允许睡眠",
+    },
+    "Allow the operating system to sleep while finite synchronisation operations are in progress.": {
+        def: "Allow the operating system to sleep while finite synchronisation operations are in progress.",
+        zh: "在一次性同步操作进行期间，允许操作系统进入睡眠。",
+    },
     "Also, please note that if you are using Peer-to-Peer synchronization, this configuration will be used when you switch to other methods and connect to a remote server in the future.":
         {
             def: "Also, please note that if you are using Peer-to-Peer synchronization, this configuration will be used when you switch to other methods and connect to a remote server in the future.",
@@ -576,6 +592,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
             "zh-tw":
                 "分析資料庫使用情況並產生 TSV 報告，方便你自行診斷。你可以將產生的報告貼到任何慣用的試算表中查看。",
         },
+    "Application ID": {
+        def: "Application ID",
+        zh: "应用 ID",
+    },
     "Apply All Selected": {
         def: "Apply All Selected",
         es: "Aplicar todo lo seleccionado",
@@ -639,6 +659,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "自动启动 P2P 连接",
         "zh-tw": "自動啟動 P2P 連線",
     },
+    "Auto-accept compatible tweak mismatches": {
+        def: "Auto-accept compatible tweak mismatches",
+        zh: "自动接受兼容的调整值不一致",
+    },
     Automatic: {
         def: "Automatic",
         es: "Automático",
@@ -647,6 +671,19 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "自动",
         "zh-tw": "自動",
     },
+    "Automatically accepts mismatches that are compatible but potentially lossy by comparing tweak modification times.":
+        {
+            def: "Automatically accepts mismatches that are compatible but potentially lossy by comparing tweak modification times.",
+            zh: "通过比较调整值的修改时间，自动接受兼容但可能有损的配置不一致。",
+        },
+    "Automatically broadcast changes to connected peers": {
+        def: "Automatically broadcast changes to connected peers",
+        zh: "自动将更改广播给已连接的对等方",
+    },
+    "Automatically start P2P connection on launch": {
+        def: "Automatically start P2P connection on launch",
+        zh: "启动时自动启动 P2P 连接",
+    },
     "Automatically Sync all files when opening Obsidian.": {
         def: "Automatically Sync all files when opening Obsidian.",
         es: "Sincronizar automáticamente todos los archivos al abrir Obsidian",
@@ -780,6 +817,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Cancel all and reboot": {
         def: "Cancel all and reboot",
         es: "Cancelar todo y reiniciar",
+        zh: "全部取消并重启",
     },
     "Cancel Garbage Collection": {
         def: "Cancel Garbage Collection",
@@ -851,6 +889,14 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "正在检查连接…请稍候。",
         "zh-tw": "正在檢查連線⋯ 請稍候。",
     },
+    "Chunk revisions are always derived from their content. This stored key is retained only for compatibility.": {
+        def: "Chunk revisions are always derived from their content. This stored key is retained only for compatibility.",
+        zh: "数据块修订版本始终由其内容推导得出。此已存储的设置项仅为兼容而保留。",
+    },
+    "Chunk Splitter": {
+        def: "Chunk Splitter",
+        zh: "数据块分割器",
+    },
     Chunks: {
         def: "Chunks",
         es: "Fragmentos (chunks)",
@@ -986,6 +1032,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Compare time and take newer": {
         def: "Compare time and take newer",
         es: "Comparar fechas y usar la más reciente",
+        zh: "比较时间并采用较新版本",
     },
     "Compatibility (Conflict Behaviour)": {
         def: "Compatibility (Conflict Behaviour)",
@@ -1117,6 +1164,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Conflict & Deletion Options": {
         def: "Conflict & Deletion Options",
         es: "Opciones de conflictos y eliminación",
+        zh: "冲突与删除选项",
     },
     Connect: {
         def: "Connect",
@@ -1173,6 +1221,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "连接：",
         "zh-tw": "連線：",
     },
+    "Content-derived chunk revisions (obsolete setting)": {
+        def: "Content-derived chunk revisions (obsolete setting)",
+        zh: "基于内容的数据块修订（已过时的设置）",
+    },
     "Continue anyway": {
         def: "Continue anyway",
         es: "Continuar de todos modos",
@@ -1291,6 +1343,14 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "自定义请求头",
         "zh-tw": "自訂標頭",
     },
+    "Custom headers for requesting the bucket. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": {
+        def: "Custom headers for requesting the bucket. e.g. `x-custom-header1: value1\n x-custom-header2: value2`",
+        zh: "用于请求存储桶的自定义请求头。例如：`x-custom-header1: value1\n x-custom-header2: value2`",
+    },
+    "Custom headers for requesting the CouchDB. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": {
+        def: "Custom headers for requesting the CouchDB. e.g. `x-custom-header1: value1\n x-custom-header2: value2`",
+        zh: "用于请求 CouchDB 的自定义请求头。例如：`x-custom-header1: value1\n x-custom-header2: value2`",
+    },
     "Customization Sync": {
         def: "Customization Sync",
         es: "Sincronización de personalización",
@@ -1323,6 +1383,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Data retrieval scheduled": {
         def: "Data retrieval scheduled",
         es: "Obtención de datos programada",
+        zh: "已安排数据获取",
     },
     "Data to Copy": {
         def: "Data to Copy",
@@ -1457,10 +1518,12 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Delete local files if deleted on remote": {
         def: "Delete local files if deleted on remote",
         es: "Eliminar los archivos locales si se eliminaron en el remoto",
+        zh: "若远程已删除，则删除本地文件",
     },
     "Delete local files if not on remote": {
         def: "Delete local files if not on remote",
         es: "Eliminar los archivos locales que no estén en el remoto",
+        zh: "若远程不存在，则删除本地文件",
     },
     "Delete old metadata of deleted files on start-up": {
         def: "Delete old metadata of deleted files on start-up",
@@ -1556,6 +1619,14 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "桌面设备",
         "zh-tw": "桌面裝置",
     },
+    "Desktop only; uses more battery and network.": {
+        def: "Desktop only; uses more battery and network.",
+        zh: "仅限桌面端；会消耗更多电量和网络流量。",
+    },
+    "Desktop only. Allow sleep on this device even when the general option is disabled.": {
+        def: "Desktop only. Allow sleep on this device even when the general option is disabled.",
+        zh: "仅限桌面端。即使通用选项已禁用，也允许此设备进入睡眠。",
+    },
     "Detected Peers": {
         def: "Detected Peers",
         es: "Pares detectados",
@@ -1652,7 +1723,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "Self-hosted LiveSync に設定されている言語の翻訳がありましたので、インターフェースの表示言語が適用されました。\n\n注意： 全てのメッセージは翻訳されていません。あなたの貢献をお待ちしています！\nGithubにIssueを作成する際には、 インターフェースの表示言語 を一旦 Default に戻してから、スクショやメッセージ、ログを収集してください。これは設定から変更できます。\n\n便利に使用できれば幸いです。",
         ko: "Self-hosted LiveSync가 사용 중인 언어의 번역을 제공하므로 표시 언어 설정이 활성화되었습니다.\n\n참고: 모든 메시지가 번역되어 있지는 않습니다. 여러분의 기여를 기다리고 있습니다!\n참고 2: 이슈를 등록할 때는 **기본값 로 되돌린 뒤** 스크린샷과 메시지, 로그를 첨부해 주세요. 설정 대화 상자에서 되돌릴 수 있습니다.\n편하게 사용하실 수 있기를 바랍니다!",
         ru: "Self-hosted LiveSync имеет переводы для вашего языка, поэтому была включена настройка языка Display language.\n\nПримечание: Не все сообщения переведены. Мы ждём ваших предложений!\nПримечание 2: При создании Issue, пожалуйста, вернитесь к lang-def, затем сделайте скриншоты, сообщения и логи. Это можно сделать в настройках.\nНадеемся, вам будет удобно использовать!",
-        zh: "Self-hosted LiveSync已提供您语言的翻译,因此启用了%{Display language}\n\n注意：并非所有消息都已翻译。我们期待您的贡献！\n注意 2：若您创建问题报告， **请切换回Default** ，然后截取屏幕截图、消息和日志，此操作可在设置对话框中完成\n愿您使用顺心！",
+        zh: "Self-hosted LiveSync已提供您语言的翻译,因此启用了%{Display language}\n\n注意：并非所有消息都已翻译。我们期待您的贡献！\n注意 2：若您创建问题报告， **请切换回默认** ，然后截取屏幕截图、消息和日志，此操作可在设置对话框中完成\n愿您使用顺心！",
         "zh-tw":
             "Self-hosted LiveSync 已提供你目前語言的翻譯，因此已啟用顯示語言設定。\n\n注意：並非所有訊息都已完成翻譯，歡迎協助補充！\n注意 2：如果你要回報問題，請先切回預設語言，再附上截圖、訊息與日誌。\n\n希望你使用愉快！",
     },
@@ -1664,7 +1735,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "Keep Default",
         ko: "기본값 유지",
         ru: "Оставить lang-def",
-        zh: "保持Default",
+        zh: "保持默认",
         "zh-tw": "恢復為預設語言",
     },
     "dialog.yourLanguageAvailable.Title": {
@@ -1880,7 +1951,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "\n## ${name}\n\n| 現在の値 | 理想値 |\n|:---:|:---:|\n| ${current} | ${ideal} |\n\n**推奨レベル:** ${level}\n\n### 診断理由？\n\n${reason}\n\n${note}\n\nこれを理想値に修正しますか？",
         ko: "\n## ${name}\n\n| 현재 값 | 이상적인 값 |\n|:---:|:---:|\n| ${current} | ${ideal} |\n\n**권장 수준:** ${level}\n\n### 왜 이것이 감지되었나요?\n\n${reason}\n\n${note}\n\n이상적인 값으로 수정할까요?",
         ru: "\n## ${name}\n\n| Текущее | Идеальное |\n|:---:|:---:|\n| ${current} | ${ideal} |\n\n**Уровень рекомендации:** ${level}\n\n### Почему это было обнаружено?\n\n${reason}\n\n${note}\n\nИсправить на идеальное значение?",
-        zh: "\n## ${name}\n\n| Current | Ideal |\n|:---:|:---:|\n| ${current} | ${ideal} |\n\n**Recommendation Level:** ${level}\n\n### Why this has been detected?\n\n${reason}\n\n${note}\n\nFix this to the ideal value?",
+        zh: "\n## ${name}\n\n| 当前值 | 理想值 |\n|:---:|:---:|\n| ${current} | ${ideal} |\n\n**建议级别：** ${level}\n\n### 为何检测到此问题？\n\n${reason}\n\n${note}\n\n是否将其修正为理想值？",
         "zh-tw":
             "\n## ${name}\n\n| 目前值 | 建議值 |\n|:---:|:---:|\n| ${current} | ${ideal} |\n\n**建議等級：** ${level}\n\n### 為什麼會偵測到這個問題？\n\n${reason}\n\n${note}\n\n要將此項修正為建議值嗎？",
     },
@@ -2013,7 +2084,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "エンドツーエンド暗号化がより堅牢で高速になりました。また、以前のE2EEは再コードレビューにより脆弱性が発見されました。できるだけ早く適用することをお勧めします。ご不便をおかけして申し訳ありません。また、この設定は下位互換性がありません。すべての同期デバイスをv0.25.0以降にアップデートする必要があります。再構築は必須ではなく、新しい転送から新しいフォーマットに変換されますが、可能な限り再構築をお勧めします。",
         ko: "종단 간 암호화가 더 견고하고 빨라졌습니다. 또한 다시 진행한 코드 검토에서 이전 E2EE에 취약점이 있는 것으로 확인되었기 때문에, 가능한 한 빨리 적용해 주시기 바랍니다. 불편을 드려 대단히 죄송합니다. 그리고 이 설정은 이전 버전과 호환되지 않습니다. 동기화 중인 모든 기기를 v0.25.0 이상으로 업데이트해야 합니다. 재구축은 필요하지 않으며 새로 전송되는 항목부터 새 형식으로 변환됩니다. 다만 가능하다면 재구축하시기를 권장합니다.",
         ru: "Сквозное шифрование стало более надёжным и быстрым. Предыдущее E2EE было скомпрометировано. Следует применить как можно скорее.",
-        zh: "The End-to-End Encryption has got now more robust and faster. Also because, the previous E2EE was found to be compromised in a re-conducted code review. It should be applied as soon as possible. Really apologises for your inconvenience. And, this setting is not forward compatible. All synchronised devices must be updated to v0.25.0 or higher. Rebuilds are not required and will be converted from the new transfer to the new format, However, it is recommended to rebuild whenever possible.",
+        zh: "端到端加密现在变得更加稳健、更快。另外，之前的端到端加密在重新进行的代码审查中被发现存在安全漏洞，因此应尽快启用。对此给你带来的不便，我们深表歉意。此外，该设置不向前兼容，所有已同步的设备都必须更新到 v0.25.0 或更高版本。无需重建，数据会从新的传输方式转换为新格式，不过仍建议尽可能进行重建。",
         "zh-tw":
             "端對端加密現在變得更穩固也更快。此外，先前的 E2EE 在重新進行的程式碼審查中被發現有安全漏洞，應盡快套用此項修正。造成的不便由衷抱歉。另外，此設定不具向前相容性，所有同步的裝置都必須更新到 v0.25.0 或更新版本。不需要重建，資料會在下次傳輸時自動轉換為新格式；不過，若條件允許，仍建議進行重建。",
     },
@@ -2079,6 +2150,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "边缘情况处理（处理）",
         "zh-tw": "邊緣情況處理（處理）",
     },
+    "Effectively a directory. Should end with `/`. e.g., `vault-name/`.": {
+        def: "Effectively a directory. Should end with `/`. e.g., `vault-name/`.",
+        zh: "实际上是一个目录，应以 `/` 结尾，例如 `vault-name/`。",
+    },
     "Emergency restart": {
         def: "Emergency restart",
         es: "Reinicio de emergencia",
@@ -2099,6 +2174,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "启用高级功能",
         "zh-tw": "啟用進階功能",
     },
+    "Enable advanced mode": {
+        def: "Enable advanced mode",
+        zh: "启用高级模式",
+    },
     "Enable customization sync": {
         def: "Enable customization sync",
         es: "Habilitar sincronización de personalización",
@@ -2110,6 +2189,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "启用自定义同步",
         "zh-tw": "啟用自訂同步",
     },
+    "Enable Developers' Debug Tools (If available).": {
+        def: "Enable Developers' Debug Tools (If available).",
+        zh: "启用开发者调试工具（如可用）。",
+    },
     "Enable Developers' Debug Tools.": {
         def: "Enable Developers' Debug Tools.",
         es: "Habilitar herramientas de depuración",
@@ -2132,6 +2215,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "启用边缘情况处理功能",
         "zh-tw": "啟用邊緣情況處理功能",
     },
+    "Enable forcePathStyle": {
+        def: "Enable forcePathStyle",
+        zh: "启用 forcePathStyle",
+    },
     "Enable P2P Replicator": {
         def: "Enable P2P Replicator",
         es: "Habilitar el replicador P2P",
@@ -2140,6 +2227,18 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "启用 P2P 复制器",
         "zh-tw": "啟用 P2P 複寫器",
     },
+    "Enable P2P Synchronization": {
+        def: "Enable P2P Synchronization",
+        zh: "启用 P2P 同步",
+    },
+    "Enable per-file customization sync": {
+        def: "Enable per-file customization sync",
+        zh: "启用逐文件自定义同步",
+    },
+    "Enable power user mode": {
+        def: "Enable power user mode",
+        zh: "启用专家模式",
+    },
     "Enable poweruser features": {
         def: "Enable poweruser features",
         es: "Habilitar funciones para usuarios avanzados",
@@ -2203,6 +2302,15 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
             zh: "加密远程数据库中的内容。如果您使用插件的同步功能,则建议启用此功能 ",
             "zh-tw": "加密遠端資料庫中的內容。如果你使用外掛的同步功能，建議啟用此選項。",
         },
+    "Encrypt file properties (paths, times, sizes, and Chunk references) used by Hidden File Sync and Customisation Sync. This affects future writes; manually rebuild the remote database to protect existing properties. Requires E2EE V2, Property Encryption, and compatible clients on every device.":
+        {
+            def: "Encrypt file properties (paths, times, sizes, and Chunk references) used by Hidden File Sync and Customisation Sync. This affects future writes; manually rebuild the remote database to protect existing properties. Requires E2EE V2, Property Encryption, and compatible clients on every device.",
+            zh: "加密隐藏文件同步和自定义同步所使用的文件属性（路径、时间、大小以及数据块引用）。此设置影响之后的写入；如需保护已有属性，请手动重建远程数据库。需要 E2EE V2 和属性加密，并且每台设备上的客户端都需兼容。",
+        },
+    "Encrypt internal file Properties": {
+        def: "Encrypt internal file Properties",
+        zh: "加密内部文件属性",
+    },
     "Encrypting sensitive configuration items": {
         def: "Encrypting sensitive configuration items",
         es: "Cifrando elementos sensibles",
@@ -2222,6 +2330,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "加密算法",
         "zh-tw": "加密演算法",
     },
+    "Encryption passphrase. If changed, you should overwrite the server's database with the new (encrypted) files.": {
+        def: "Encryption passphrase. If changed, you should overwrite the server's database with the new (encrypted) files.",
+        zh: "加密密码短语。如果更改，你应当用新的（加密后的）文件覆盖服务器上的数据库。",
+    },
     "Encryption phassphrase. If changed, you should overwrite the server's database with the new (encrypted) files.": {
         def: "Encryption phassphrase. If changed, you should overwrite the server's database with the new (encrypted) files.",
         es: "Frase de cifrado. Si la cambia, sobrescriba la base del servidor con los nuevos archivos cifrados.",
@@ -2244,6 +2356,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "端到端加密",
         "zh-tw": "端對端加密",
     },
+    "End-to-End Encryption Algorithm": {
+        def: "End-to-End Encryption Algorithm",
+        zh: "端到端加密算法",
+    },
     "Endpoint URL": {
         def: "Endpoint URL",
         es: "URL del endpoint",
@@ -2591,6 +2707,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "文件完整性",
         "zh-tw": "檔案完整性",
     },
+    "File prefix on the bucket": {
+        def: "File prefix on the bucket",
+        zh: "存储桶中的文件前缀",
+    },
     "File to resolve conflict": {
         def: "File to resolve conflict",
         es: "Archivo para resolver el conflicto",
@@ -2619,6 +2739,11 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "文件名",
         "zh-tw": "檔名",
     },
+    "Files with modification times greater than this value (in seconds since the Unix epoch) will not have their events reflected. Set to 0 to disable this limit.":
+        {
+            def: "Files with modification times greater than this value (in seconds since the Unix epoch) will not have their events reflected. Set to 0 to disable this limit.",
+            zh: "修改时间大于此值（Unix 时间戳，单位为秒）的文件，其事件将不会被反映。设为 0 可禁用此限制。",
+        },
     "Final Confirmation: Overwrite Server Data with This Device's Files": {
         def: "Final Confirmation: Overwrite Server Data with This Device's Files",
         es: "Confirmación final: sobrescribir los datos del servidor con los archivos de este dispositivo",
@@ -2630,6 +2755,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Finalise the process and resume normal operation": {
         def: "Finalise the process and resume normal operation",
         es: "Finalizar el proceso y reanudar el funcionamiento normal",
+        zh: "完成流程并恢复正常运行",
     },
     "First, please select the option that best describes your current situation.": {
         def: "First, please select the option that best describes your current situation.",
@@ -2878,6 +3004,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         {
             def: "How should files that were deleted on other devices be handled?\n\n- **${NEWER_CLEANUP}**: Delete local files if they were deleted on remote.\n  This is useful if you want to keep your vault clean and consistent across devices, but please make sure you have a backup if there is already any important data in your vault.\n- **${NEWER_SYNC_ALL}**: Recreate remote files even if they were deleted on remote.\n  This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.",
             es: "¿Cómo se deben gestionar los archivos que se eliminaron en otros dispositivos?\n\n- **${NEWER_CLEANUP}**: elimina los archivos locales si se eliminaron en el remoto.\n  Es útil si quieres mantener tu vault limpio y coherente entre dispositivos; asegúrate de tener una copia de seguridad si ya tienes datos importantes en tu vault.\n- **${NEWER_SYNC_ALL}**: vuelve a crear los archivos remotos aunque se hayan eliminado en el remoto.\n  Esta opción mantiene todos tus archivos locales, pero puede causar duplicados si hay archivos que existen en local pero no en el remoto. Puedes limpiar esos duplicados manualmente después de sincronizar.",
+            zh: "其他设备上删除的文件应如何处理？\n\n- **${NEWER_CLEANUP}**：如果文件在远程被删除，则删除本地文件。\n  如果你希望让各设备上的库保持整洁一致，这会很有用。但如果库中已有重要数据，请务必先做好备份。\n- **${NEWER_SYNC_ALL}**：即使文件在远程已被删除，也重新创建远程文件。\n  此选项会保留你所有的本地文件，但如果有些文件只存在于本地而不存在于远程，可能会产生重复文件。同步完成后，你可以手动清理这些重复文件。",
         },
     "How to display network errors when the sync server is unreachable.": {
         def: "How to display network errors when the sync server is unreachable.",
@@ -2891,6 +3018,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "How to handle extra existing local files?": {
         def: "How to handle extra existing local files?",
         es: "¿Cómo gestionar los archivos locales adicionales?",
+        zh: "如何处理本地已有的多余文件？",
     },
     "How would you like to configure the connection to your server?": {
         def: "How would you like to configure the connection to your server?",
@@ -3058,6 +3186,11 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
             "zh-tw":
                 "啟用後會使用以每個檔案為單位的高效率自訂同步。啟用時需要進行一次小型遷移，且所有裝置都應升級到 v0.23.18。啟用後將不再相容舊版本。",
         },
+    "If enabled, changes will be automatically broadcasted to all connected peers. Notified peers will start fetching the changes.":
+        {
+            def: "If enabled, changes will be automatically broadcasted to all connected peers. Notified peers will start fetching the changes.",
+            zh: "启用后，更改将自动广播给所有已连接的对等方。收到通知的对等方将开始获取这些更改。",
+        },
     "If enabled, chunks will be split into no more than 100 items. However, dedupe is slightly weaker.": {
         def: "If enabled, chunks will be split into no more than 100 items. However, dedupe is slightly weaker.",
         es: "Divide chunks en máximo 100 ítems. Menos eficiente en deduplicación",
@@ -3069,6 +3202,11 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "如果启用,数据块将被分割成不超过 100 项。但是,去重效果会稍弱",
         "zh-tw": "啟用後，chunks 最多會分成 100 個項目，但去重效果會稍微變弱。",
     },
+    "If enabled, efficient per-file customization sync will be used. A minor migration is required when enabling this feature, and all devices must be updated to v0.23.18. Enabling this feature will result in losing compatibility with older versions.":
+        {
+            def: "If enabled, efficient per-file customization sync will be used. A minor migration is required when enabling this feature, and all devices must be updated to v0.23.18. Enabling this feature will result in losing compatibility with older versions.",
+            zh: "启用后，将使用更高效的逐文件自定义同步。启用此功能需要进行一次小规模迁移，并且所有设备都必须更新到 v0.23.18。启用此功能后，将失去与旧版本的兼容性。",
+        },
     "If enabled, newly created chunks are temporarily kept within the document, and graduated to become independent chunks once stabilised.":
         {
             def: "If enabled, newly created chunks are temporarily kept within the document, and graduated to become independent chunks once stabilised.",
@@ -3093,6 +3231,11 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
             zh: "如果启用，状态栏内将显示 ⛔ 图标，而非文件警告横幅，不会显示任何详细信息。",
             "zh-tw": "啟用後，將在狀態列中顯示 ⛔ 圖示，而不是檔案警告橫幅，且不會顯示詳細資訊。",
         },
+    "If enabled, the file properties will be encrypted in the remote database. This is useful for protecting sensitive information in file paths, sizes, and IDs of its chunks. If you are using V1 E2EE, this only obfuscates the file path.":
+        {
+            def: "If enabled, the file properties will be encrypted in the remote database. This is useful for protecting sensitive information in file paths, sizes, and IDs of its chunks. If you are using V1 E2EE, this only obfuscates the file path.",
+            zh: "启用后，文件属性将在远程数据库中加密。这有助于保护文件路径、大小以及其数据块 ID 等敏感信息。如果你使用的是 V1 E2EE，则只会混淆文件路径。",
+        },
     "If enabled, the file under 1kb will be processed in the UI thread.": {
         def: "If enabled, the file under 1kb will be processed in the UI thread.",
         es: "Archivos <1kb se procesan en el hilo de UI",
@@ -3104,6 +3247,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "如果启用,小于 1kb 的文件将在 UI 线程中处理",
         "zh-tw": "啟用後，小於 1KB 的檔案會在 UI 執行緒中處理。",
     },
+    "If enabled, the forcePathStyle option will be used for bucket operations.": {
+        def: "If enabled, the forcePathStyle option will be used for bucket operations.",
+        zh: "启用后，存储桶操作将使用 forcePathStyle 选项。",
+    },
     "If enabled, the notification of hidden files change will be suppressed.": {
         def: "If enabled, the notification of hidden files change will be suppressed.",
         es: "Si se habilita, se suprimirá la notificación de cambios en archivos ocultos.",
@@ -3115,6 +3262,20 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "如果启用,将不再通知隐藏文件被更改",
         "zh-tw": "啟用後，將不再通知隱藏檔案變更。",
     },
+    "If enabled, the P2P connection will be automatically started when the application launches.": {
+        def: "If enabled, the P2P connection will be automatically started when the application launches.",
+        zh: "启用后，应用启动时将自动开始 P2P 连接。",
+    },
+    "If enabled, the plugin will not attempt to connect to the remote database even if the chunk was not found locally.":
+        {
+            def: "If enabled, the plugin will not attempt to connect to the remote database even if the chunk was not found locally.",
+            zh: "启用后，即使本地未找到数据块，插件也不会尝试连接远程数据库。",
+        },
+    "If enabled, the request API will be used to avoid `inevitable` CORS problems. This is a workaround and may not work in all cases. PLEASE READ THE DOCUMENTATION BEFORE USING THIS OPTION. This is a less-secure option.":
+        {
+            def: "If enabled, the request API will be used to avoid `inevitable` CORS problems. This is a workaround and may not work in all cases. PLEASE READ THE DOCUMENTATION BEFORE USING THIS OPTION. This is a less-secure option.",
+            zh: "启用后，将使用 Request API 来避免 `inevitable` CORS 问题。这只是一种变通方法，并非在所有情况下都有效。请务必在使用此选项前阅读文档。这是一个安全性较低的选项。",
+        },
     "If this enabled, all chunks will be stored with the revision made from its content. (Previous behaviour)": {
         def: "If this enabled, all chunks will be stored with the revision made from its content. (Previous behaviour)",
         es: "Si se habilita, todos los chunks se almacenan con la revisión hecha desde su contenido. (comportamiento anterior)",
@@ -3149,6 +3310,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
             zh: "如果启用此功能,数据块将被分割成具有语义意义的段落。并非所有平台都支持此功能",
             "zh-tw": "啟用後，chunks 會依語意切分成有意義的區段，並非所有平台都支援此功能。",
         },
+    "If this enabled, JWT will be used for authentication.": {
+        def: "If this enabled, JWT will be used for authentication.",
+        zh: "启用后将使用 JWT 认证。",
+    },
     "If this is set, changes to local files which are matched by the ignore files will be skipped. Remote changes are determined using local ignore files.":
         {
             def: "If this is set, changes to local files which are matched by the ignore files will be skipped. Remote changes are determined using local ignore files.",
@@ -3367,6 +3532,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "初始化日志的已发送历史。下次同步时，除本设备已接收的项外，其余都会重新发送。",
         "zh-tw": "初始化傳送日誌歷程。下次同步時，除了此裝置已接收的項目外，其他項目都會再次傳送。",
     },
+    "Internal timestamp for resolving compatible tweak mismatches.": {
+        def: "Internal timestamp for resolving compatible tweak mismatches.",
+        zh: "用于解决兼容的调整值不一致问题的内部时间戳。",
+    },
     "Interval (sec)": {
         def: "Interval (sec)",
         es: "Intervalo (segundos)",
@@ -3479,7 +3648,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "Peer-to-Peer Sync (試験機能)",
         ko: "피어 투 피어(P2P) 동기화 (실험 기능)",
         ru: "title_p2p_sync",
-        zh: "Peer-to-Peer同步 (实验性)",
+        zh: "Peer-to-Peer 同步 (实验性)",
         "zh-tw": "Peer-to-Peer 同步",
     },
     "K.P2P": {
@@ -3534,7 +3703,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "Peer-to-Peer Sync",
         ko: "피어 투 피어(P2P) 동기화",
         ru: "Синхронизация между устройствами",
-        zh: "Peer-to-Peer同步",
+        zh: "Peer-to-Peer 同步",
         "zh-tw": "Peer-to-Peer 同步",
     },
     "Keep empty folder": {
@@ -3551,10 +3720,24 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Keep local files even if deleted on remote": {
         def: "Keep local files even if deleted on remote",
         es: "Mantener los archivos locales aunque se hayan eliminado en el remoto",
+        zh: "即使远程已删除，也保留本地文件",
     },
     "Keep local files even if not on remote": {
         def: "Keep local files even if not on remote",
         es: "Mantener los archivos locales aunque no estén en el remoto",
+        zh: "即使远程不存在，也保留本地文件",
+    },
+    "Keep replication active in the background": {
+        def: "Keep replication active in the background",
+        zh: "在后台保持复制运行",
+    },
+    "Key ID": {
+        def: "Key ID",
+        zh: "密钥 ID",
+    },
+    "Keypair or pre-shared key": {
+        def: "Keypair or pre-shared key",
+        zh: "密钥对或预共享密钥",
     },
     lang_def: {
         def: "Default",
@@ -3564,7 +3747,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "Default",
         ko: "기본값",
         ru: "По умолчанию",
-        zh: "Default",
+        zh: "默认",
         "zh-tw": "預設",
     },
     "lang-de": {
@@ -3586,7 +3769,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "Default",
         ko: "기본값",
         ru: "lang_def",
-        zh: "Default",
+        zh: "默认",
         "zh-tw": "預設",
     },
     "lang-es": {
@@ -3675,6 +3858,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "繁體中文",
         "zh-tw": "繁體中文",
     },
+    "Last tweak modified timestamp": {
+        def: "Last tweak modified timestamp",
+        zh: "调整值最后修改时间戳",
+    },
     Later: {
         def: "Later",
         es: "Más tarde",
@@ -4095,6 +4282,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "自动换行",
         "zh-tw": "自動換行",
     },
+    "Longest chunk line threshold value (Not Configurable from the UI Now).": {
+        def: "Longest chunk line threshold value (Not Configurable from the UI Now).",
+        zh: "最长数据块行的阈值（目前无法在界面中配置）。",
+    },
     "Lower (${local} < ${remote})": {
         def: "Lower (${local} < ${remote})",
         es: "Inferior (${local} < ${remote})",
@@ -4130,6 +4321,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "批量数据库更新的最大延迟",
         "zh-tw": "批次更新資料庫的最大延遲",
     },
+    "Maximum file modification time for reflected file events": {
+        def: "Maximum file modification time for reflected file events",
+        zh: "可反映文件事件的最大修改时间",
+    },
     "Maximum file size": {
         def: "Maximum file size",
         es: "Tamaño máximo de archivo",
@@ -4174,6 +4369,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "最大孵化期",
         "zh-tw": "最大暫存期間",
     },
+    "Maximum request size for manually resending chunks": {
+        def: "Maximum request size for manually resending chunks",
+        zh: "手动重新发送数据块时的最大请求大小",
+    },
     "MB (0 to disable).": {
         def: "MB (0 to disable).",
         es: "MB (0 para desactivar)",
@@ -4185,6 +4384,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "MB(0为禁用)",
         "zh-tw": "MB（0 表示停用）。",
     },
+    "MB per request": {
+        def: "MB per request",
+        zh: "每次请求的 MB 数",
+    },
     "Memory cache": {
         def: "Memory cache",
         es: "Caché en memoria",
@@ -4225,6 +4428,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "合并",
         "zh-tw": "合併",
     },
+    "Minimum Chunk Size (Not Configurable from the UI Now).": {
+        def: "Minimum Chunk Size (Not Configurable from the UI Now).",
+        zh: "最小数据块大小（目前无法在界面中配置）。",
+    },
     "Minimum delay for batch database updating": {
         def: "Minimum delay for batch database updating",
         es: "Retraso mínimo para actualización por lotes",
@@ -5057,6 +5264,11 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "将远程删除的文件移至回收站,而不是直接删除",
         "zh-tw": "將遠端刪除的檔案移至垃圾桶，而非直接刪除。",
     },
+    "Move remotely deleted files to the trash, instead of deleting. (This setting is ineffective from Obsidian v1.7.2 onwards, as deletion always respects your Obsidian preferences.)":
+        {
+            def: "Move remotely deleted files to the trash, instead of deleting. (This setting is ineffective from Obsidian v1.7.2 onwards, as deletion always respects your Obsidian preferences.)",
+            zh: "将远程删除的文件移至回收站，而不是直接删除。（此设置自 Obsidian v1.7.2 起不再生效，因为删除操作始终遵循你在 Obsidian 中的偏好设置。）",
+        },
     "My remote server is already set up. I want to join this device.": {
         def: "My remote server is already set up. I want to join this device.",
         es: "Mi servidor remoto ya está configurado. Quiero añadir este dispositivo.",
@@ -5298,6 +5510,11 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "启动时当估计的远程存储大小超出时通知",
         "zh-tw": "啟動時，若預估的遠端儲存空間大小超出限制則通知",
     },
+    "Now we can choose how to split the chunks; V3 is the most efficient. If you have troubled, please make this Default or Legacy.":
+        {
+            def: "Now we can choose how to split the chunks; V3 is the most efficient. If you have troubled, please make this Default or Legacy.",
+            zh: "现在可以选择数据块的分割方式；V3 效率最高。如果遇到问题，请将此项设为 Default 或 Legacy。",
+        },
     "Number of batches to process at a time. Defaults to 40. Minimum is 2. This along with batch size controls how many docs are kept in memory at a time.":
         {
             def: "Number of batches to process at a time. Defaults to 40. Minimum is 2. This along with batch size controls how many docs are kept in memory at a time.",
@@ -6575,7 +6792,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "✔ chttpd.enable_corsは正常です。",
         ko: "✔ chttpd.enable_cors가 정상입니다.",
         ru: "✔ chttpd.enable_cors в порядке.",
-        zh: "✔ chttpd.enable_cors is ok.",
+        zh: "✔ chttpd.enable_cors 设置正确",
         "zh-tw": "✔ chttpd.enable_cors 設定正確。",
     },
     "obsidianLiveSyncSettingTab.okMaxDocumentSize": {
@@ -7352,6 +7569,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Overwrite all with remote files": {
         def: "Overwrite all with remote files",
         es: "Sobrescribir todo con los archivos remotos",
+        zh: "全部用远程文件覆盖",
     },
     "Overwrite patterns": {
         def: "Overwrite patterns",
@@ -7435,7 +7653,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "Peer-to-Peer Syncは無効になっています。本当に有効にしますか？",
         ko: "피어 투 피어(P2P) 동기화가 비활성화되어 있습니다. 정말로 활성화하시겠습니까?",
         ru: "title_p2p_sync отключён. Вы действительно хотите включить?",
-        zh: "Peer-to-Peer同步 已禁用。你确定要启用它吗？",
+        zh: "Peer-to-Peer 同步 已禁用。你确定要启用它吗？",
         "zh-tw": "Peer-to-Peer 同步目前已停用。你確定要啟用它嗎？",
     },
     "P2P.FailedToOpen": {
@@ -7457,7 +7675,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "自動同期ピアが見つかりません。Peer-to-Peer Sync (試験機能)ペインでピアを設定してください。",
         ko: "자동 동기화 피어를 찾을 수 없습니다. 피어 투 피어(P2P) 동기화 (실험 기능) 창에서 피어를 설정해 주세요.",
         ru: "Автосинхронизируемые устройства не найдены.",
-        zh: "未找到自动同步的对等方，请在 Peer-to-Peer同步 (实验性) 面板中设置对等方",
+        zh: "未找到自动同步的对等方，请在 Peer-to-Peer 同步 (实验性) 面板中设置对等方",
         "zh-tw": "找不到自動同步的 Peer。請到「Peer-to-Peer 同步」面板設定 Peer。",
     },
     "P2P.NoKnownPeers": {
@@ -7525,7 +7743,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "Peer-to-Peer Syncが有効になっていません。新しい接続を開くことができません。",
         ko: "피어 투 피어(P2P) 동기화가 활성화되지 않았습니다. 새로운 연결을 열 수 없습니다.",
         ru: "title_p2p_sync не включён. Мы не можем открыть новое подключение.",
-        zh: "Peer-to-Peer同步 is not enabled. We cannot open a new connection.",
+        zh: "Peer-to-Peer 同步 未启用，无法建立新连接。",
         "zh-tw": "Peer-to-Peer 同步尚未啟用，無法開啟新連線。",
     },
     "P2P.P2PReplication": {
@@ -7536,7 +7754,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "Peer-to-Peerレプリケーション(複製)",
         ko: "피어-to-피어 복제",
         ru: "P2P Репликация",
-        zh: "Peer-to-Peer Replication",
+        zh: "Peer-to-Peer 复制",
         "zh-tw": "Peer-to-Peer 複寫",
     },
     "P2P.PaneTitle": {
@@ -7547,7 +7765,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "Peer-to-Peer Sync (試験機能)",
         ko: "피어 투 피어(P2P) 동기화 (실험 기능)",
         ru: "long_p2p_sync",
-        zh: "Peer-to-Peer同步 (实验性)",
+        zh: "Peer-to-Peer 同步 (实验性)",
         "zh-tw": "Peer-to-Peer 同步",
     },
     "P2P.ReplicatorInstanceMissing": {
@@ -7558,7 +7776,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "P2P同期レプリケーターが見つかりません。設定または有効化されていない可能性があります。",
         ko: "P2P 동기화 복제기를 찾을 수 없습니다. 구성되지 않았거나 활성화되지 않았을 수 있습니다.",
         ru: "P2P Sync репликатор не найден, возможно, не настроен.",
-        zh: "P2P Sync replicator is not found, possibly not have been configured or enabled.",
+        zh: "未找到 P2P 同步复制器，可能尚未配置或未启用。",
         "zh-tw": "找不到 P2P 同步複寫器，可能尚未設定或啟用。",
     },
     "P2P.SeemsOffline": {
@@ -7569,7 +7787,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "ピア${name}はオフラインのようです。スキップしました。",
         ko: "피어 ${name}이(가) 오프라인인 것 같습니다. 건너뜁니다.",
         ru: "Устройство ${name} офлайн, пропущено.",
-        zh: "Peer ${name} seems offline, skipped.",
+        zh: "对等方 ${name} 似乎处于离线状态，已跳过。",
         "zh-tw": "Peer ${name} 似乎已離線，已略過。",
     },
     "P2P.SyncAlreadyRunning": {
@@ -7580,7 +7798,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "P2P同期はすでに実行中です。",
         ko: "P2P 동기화가 이미 실행 중입니다.",
         ru: "P2P Sync уже запущен.",
-        zh: "P2P Sync is already running.",
+        zh: "P2P 同步已在运行。",
         "zh-tw": "P2P 同步已在執行中。",
     },
     "P2P.SyncCompleted": {
@@ -7591,7 +7809,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "P2P同期が完了しました。",
         ko: "P2P 동기화가 완료되었습니다.",
         ru: "P2P Sync завершён.",
-        zh: "P2P Sync completed.",
+        zh: "P2P 同步已完成。",
         "zh-tw": "P2P 同步已完成。",
     },
     "P2P.SyncStartedWith": {
@@ -7602,7 +7820,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "${name}とのP2P同期を開始しました。",
         ko: "${name}과의 P2P 동기화가 시작되었습니다.",
         ru: "P2P Sync с ${name} начат.",
-        zh: "P2P Sync with ${name} have been started.",
+        zh: "已开始与 ${name} 的 P2P 同步。",
         "zh-tw": "已開始與 ${name} 的 P2P 同步。",
     },
     "paneMaintenance.markDeviceResolvedAfterBackup": {
@@ -8052,6 +8270,11 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "请注意这是预期行为。",
         "zh-tw": "請理解這是預期中的行為。",
     },
+    "Please use V2, V1 is deprecated and will be removed in the future, It was not a very appropriate algorithm. Only for compatibility V1 is kept.":
+        {
+            def: "Please use V2, V1 is deprecated and will be removed in the future, It was not a very appropriate algorithm. Only for compatibility V1 is kept.",
+            zh: "请使用 V2。V1 已被弃用，将来会被移除，它并不是非常合适的算法。仅出于兼容性而保留 V1。",
+        },
     "Plug-in version": {
         def: "Plug-in version",
         es: "Versión del complemento",
@@ -8151,6 +8374,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "正在执行垃圾回收。",
         "zh-tw": "正在執行垃圾回收。",
     },
+    "Process files even if seems to be corrupted": {
+        def: "Process files even if seems to be corrupted",
+        zh: "即使文件疑似损坏也进行处理",
+    },
     "Process small files in the foreground": {
         def: "Process small files in the foreground",
         es: "Procesar archivos pequeños en primer plano",
@@ -8211,6 +8438,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Reboot to re-run the process": {
         def: "Reboot to re-run the process",
         es: "Reiniciar para volver a ejecutar el proceso",
+        zh: "重启以重新运行此流程",
     },
     "Rebuild local and remote database with local files.": {
         def: "Rebuild local and remote database with local files.",
@@ -8264,7 +8492,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "どのようにフェッチしますか？\n- フェッチ前にローカルデータベースを作成\n  **低トラフィック**, **高CPU負荷**, **低リスク**\n  推奨条件...\n  - ファイルの整合性に不安がある\n  - ファイル数がそれほど多くない\n- フェッチ前にローカルファイルチャンクを作成\n  **低トラフィック**, **中程CPU負荷**, **低～中リスク**\n  推奨条件...\n  - ファイルがおそらく整合している\n  - ファイル数が多い\n- リモートからすべてをフェッチ\n  **高トラフィック**, **低CPU負荷**, **低～中リスク**\n\n>[!INFO]- 詳細\n> ## フェッチ前にローカルデータベースを作成\n> **低トラフィック**, **高CPU負荷**, **低リスク**\n> このオプションは、リモートからデータをフェッチする前に、既存のローカルファイルを使用してローカルデータベースを作成します。\n> ローカルとリモートの両方に一致するファイルがある場合、差分のみが転送されます。\n> ただし、両方の場所に存在するファイルは最初は競合ファイルとして処理されます。実際に競合していなければ自動的に解決されますが、この処理には時間がかかる場合があります。\n> これは一般的に最も安全な方法で、データ損失のリスクを最小限に抑えます。\n> ## フェッチ前にローカルファイルチャンクを作成\n> **低トラフィック**, **中程CPU負荷**, **低～中リスク**（操作による）\n> このオプションは、最初にローカルファイルからデータベース用のチャンクを作成し、その後データをフェッチします。そのため、ローカルにないチャンクのみが転送されます。ただし、すべてのメタデータはリモートから取得されます。\n> ローカルファイルは起動時にこのメタデータと比較されます。新しいと判断されたコンテンツ（更新日時による）が古いものを上書きします。この結果はリモートデータベースに同期されます。\n> ローカルファイルが本当に最新のタイムスタンプであれば一般的に安全です。ただし、ファイルのタイムスタンプが新しくてもコンテンツが古い場合（初期の`welcome.md`など）は問題が発生する可能性があります。\n> これは\"フェッチ前にローカルデータベースを作成\"よりCPU使用量が少なく高速ですが、注意しないとデータ損失につながる可能性があります。\n> ## リモートからすべてをフェッチ\n> **高トラフィック**, **低CPU負荷**, **低～中リスク**（操作による）\n> すべてのデータがリモートからフェッチされます。\n> フェッチ前にローカルファイルチャンクを作成と似ていますが、すべてのチャンクがリモートからフェッチされます。\n> これは最も従来のフェッチ方法で、通常最もネットワークトラフィックと時間を消費します。'フェッチ前にローカルファイルチャンクを作成'オプションと同様のリモートファイル上書きのリスクがあります。\n> ただし、最も歴史があり簡単なアプローチであるため、最も安定した方法と見なされることが多いです。",
         ko: "어떻게 가져오시겠습니까?\n- 가져오기 전에 로컬 데이터베이스를 한 번 생성.\n  **낮은 트래픽**, **높은 CPU**, **낮은 위험**\n  다음의 경우에 권장합니다.\n  - 파일이 일관되지 않을 가능성이 있음\n  - 파일이 그리 많지 않음\n- 가져오기 전에 로컬 파일 청크 생성.\n  **낮은 트래픽**, **보통 CPU**, **낮음~보통 위험**\n  다음의 경우에 권장합니다.\n  - 파일이 대체로 일관됨\n  - 파일이 많음\n- 원격에서 모든 것 가져오기.\n  **높은 트래픽**, **낮은 CPU**, **낮음~보통 위험**\n\n>[!INFO]- 자세히\n> ## 가져오기 전에 로컬 데이터베이스를 한 번 생성.\n> **낮은 트래픽**, **높은 CPU**, **낮은 위험**\n> 원격에서 데이터를 가져오기 전에 기존 로컬 파일로 로컬 데이터베이스를 먼저 만듭니다.\n> 로컬과 원격 양쪽에 일치하는 파일이 있으면 둘 사이의 차이만 전송됩니다.\n> 다만 양쪽에 모두 있는 파일은 처음에 충돌 파일로 처리됩니다. 실제로 충돌하지 않는다면 자동으로 해결되지만, 이 과정에 시간이 걸릴 수 있습니다.\n> 일반적으로 가장 안전한 방법이며 데이터 손실 위험이 가장 낮습니다.\n> ## 가져오기 전에 로컬 파일 청크 생성.\n> **낮은 트래픽**, **보통 CPU**, **낮음~보통 위험** (작업에 따라 다름)\n> 먼저 로컬 파일로 데이터베이스용 청크를 만든 다음 데이터를 가져옵니다. 따라서 로컬에 없는 청크만 전송됩니다. 다만 메타데이터는 모두 원격에서 가져옵니다.\n> 그다음 시작 시점에 로컬 파일을 이 메타데이터와 비교합니다. 수정 시각을 기준으로 더 새롭다고 판단된 내용이 오래된 쪽을 덮어씁니다. 그 결과는 다시 원격 데이터베이스로 동기화됩니다.\n> 로컬 파일이 실제로 가장 최신 타임스탬프를 가지고 있다면 대체로 안전합니다. 하지만 타임스탬프는 더 새롭지만 내용은 더 오래된 파일(처음 만들어지는 `welcome.md` 같은)이 있으면 문제가 생길 수 있습니다.\n> \"가져오기 전에 로컬 데이터베이스를 한 번 생성\"보다 CPU를 적게 쓰고 더 빠르지만, 주의해서 사용하지 않으면 데이터가 손실될 수 있습니다.\n> ## 원격에서 모든 것 가져오기.\n> **높은 트래픽**, **낮은 CPU**, **낮음~보통 위험** (작업에 따라 다름)\n> 모든 것을 원격에서 가져옵니다.\n> 가져오기 전에 로컬 파일 청크 생성와 비슷하지만, 모든 청크를 원격에서 가져옵니다.\n> 가장 전통적인 가져오기 방식으로, 보통 네트워크 트래픽과 시간을 가장 많이 소모합니다. 또한 '가져오기 전에 로컬 파일 청크 생성' 옵션과 마찬가지로 원격 파일을 덮어쓸 위험이 있습니다.\n> 다만 가장 오래되고 단순한 방식이기 때문에 가장 안정적인 방법으로 여겨지는 경우가 많습니다.",
         ru: "Как вы хотите загрузить?",
-        zh: "How do you want to fetch?\n- Create a local database once before fetching.\n  **Low Traffic**, **High CPU**, **Low Risk**\n  Recommended if ...\n  - Files possibly inconsistent\n  - Files were not so much\n- Create local file chunks before fetching.\n  **Low Traffic**, **Moderate CPU**, **Low to Moderate Risk**\n  Recommended if ...\n  - Files probably consistent\n  - You have a lot of files.\n- Fetch everything from the remote.\n  **High Traffic**, **Low CPU**, **Low to Moderate Risk**\n\n>[!INFO]- Details\n> ## Create a local database once before fetching.\n> **Low Traffic**, **High CPU**, **Low Risk**\n> This option first creates a local database using existing local files before fetching data from the remote source.\n> If matching files exist both locally and remotely, only the differences between them will be transferred.\n> However, files present in both locations will initially be handled as conflicted files. They will be resolved automatically if they are not actually conflicted, but this process may take time.\n> This is generally the safest method, minimizing data loss risk.\n> ## Create local file chunks before fetching.\n> **Low Traffic**, **Moderate CPU**, **Low to Moderate Risk** (depending operation)\n> This option first creates chunks from local files for the database, then fetches data. Consequently, only chunks missing locally are transferred. However, all metadata is taken from the remote source.\n> Local files are then compared against this metadata at launch. The content considered newer will overwrite the older one (by modified time). This outcome is then synchronised back to the remote database.\n> This is generally safe if local files are genuinely the latest timestamp. However, it can cause problems if a file has a newer timestamp but older content (like the initial `welcome.md`).\n> This uses less CPU and faster than \"Create a local database once before fetching\", but it may lead to data loss if not used carefully.\n> ## Fetch everything from the remote.\n> **High Traffic**, **Low CPU**, **Low to Moderate Risk** (depending operation)\n> All things will be fetched from the remote.\n> Similar to the Create local file chunks before fetching, but all chunks are fetched from the remote source.\n> This is the most traditional way to fetch, typically consuming the most network traffic and time. It also carries a similar risk of overwriting remote files to the 'Create local file chunks before fetching' option.\n> However, it is often considered the most stable method because it is the longest-established and most straightforward approach.",
+        zh: "你希望如何获取？\n- 获取前先创建一次本地数据库。\n  **低流量**，**高 CPU**，**低风险**\n  在以下情况下推荐使用：\n  - 文件可能不一致\n  - 文件数量不多\n- 获取前先创建本地文件的数据块。\n  **低流量**，**中等 CPU**，**低到中等风险**\n  在以下情况下推荐使用：\n  - 文件基本一致\n  - 你有大量文件。\n- 从远程获取全部内容。\n  **高流量**，**低 CPU**，**低到中等风险**\n\n>[!INFO]- 详情\n> ## 获取前先创建一次本地数据库。\n> **低流量**，**高 CPU**，**低风险**\n> 此选项会先利用现有的本地文件创建本地数据库，然后再从远程源获取数据。\n> 如果本地和远程存在相同的文件，则只会传输两者之间的差异。\n> 但是，两边都存在的文件最初会被视为冲突文件。如果它们实际上并无冲突，将会被自动解决，不过这一过程可能需要一些时间。\n> 这通常是最安全的方法，能将数据丢失风险降到最低。\n> ## 获取前先创建本地文件的数据块。\n> **低流量**，**中等 CPU**，**低到中等风险**（视具体操作而定）\n> 此选项会先根据本地文件为数据库创建数据块，然后再获取数据。因此，只会传输本地缺少的数据块。但是，所有元数据都取自远程源。\n> 启动时，系统会将本地文件与这些元数据进行比较。被认为更新的内容（按修改时间判断）将覆盖较旧的版本。随后，这一结果会同步回远程数据库。\n> 如果本地文件的时间戳确实是最新的，这通常是安全的。但如果某个文件的时间戳较新、内容却较旧（例如最初的 `welcome.md`），就可能引发问题。\n> 这种方式比“获取前先创建一次本地数据库”占用更少的 CPU、速度更快，但如果使用不当，可能会导致数据丢失。\n> ## 从远程获取全部内容。\n> **高流量**，**低 CPU**，**低到中等风险**（视具体操作而定）\n> 所有内容都将从远程获取。\n> 与 获取前先创建本地文件的数据块 相似，但所有数据块都从远程源获取。\n> 这是最传统的获取方式，通常消耗最多的网络流量和时间。与“获取前先创建本地文件的数据块”选项类似，它同样存在覆盖远程文件的风险。\n> 不过，它通常被认为是最稳定的方法，因为它是历史最悠久、最直接的做法。",
         "zh-tw":
             "你想要如何抓取？\n- 先建立一次本機資料庫，再抓取。\n  **低流量**、**高 CPU 使用率**、**低風險**\n  建議情況：\n  - 檔案可能不一致\n  - 檔案數量不多\n- 先建立本機檔案的 chunks，再抓取。\n  **低流量**、**中等 CPU 使用率**、**低至中等風險**\n  建議情況：\n  - 檔案應該是一致的\n  - 你有大量檔案\n- 從遠端抓取所有內容。\n  **高流量**、**低 CPU 使用率**、**低至中等風險**\n\n>[!INFO]- 詳細說明\n> ## 先建立一次本機資料庫，再抓取。\n> **低流量**、**高 CPU 使用率**、**低風險**\n> 這個選項會先使用現有的本機檔案建立本機資料庫，再從遠端來源抓取資料。\n> 若本機與遠端都存在相符的檔案，只會傳輸兩者之間的差異部分。\n> 不過，兩邊都存在的檔案一開始會被當作衝突檔案處理。若實際上並無衝突，會自動解決，但這個過程可能需要一些時間。\n> 這通常是最安全的方式，能將資料遺失的風險降到最低。\n> ## 先建立本機檔案的 chunks，再抓取。\n> **低流量**、**中等 CPU 使用率**、**低至中等風險**（依操作而異）\n> 這個選項會先從本機檔案為資料庫建立 chunks，再抓取資料。因此只會傳輸本機缺少的 chunks，但所有中繼資料都會取自遠端來源。\n> 啟動時本機檔案會與這份中繼資料比對，內容較新的一方（依修改時間判斷）會覆寫較舊的一方，其結果會同步回遠端資料庫。\n> 如果本機檔案的時間戳記確實是最新的，這通常是安全的；但如果某個檔案時間戳記較新卻內容較舊（例如初始的 `welcome.md`），可能會出問題。\n> 這比「先建立一次本機資料庫，再抓取」耗用更少 CPU、速度也更快，但若不小心使用可能導致資料遺失。\n> ## 從遠端抓取所有內容。\n> **高流量**、**低 CPU 使用率**、**低至中等風險**（依操作而異）\n> 所有內容都會從遠端抓取。\n> 與「先建立本機檔案的 chunks，再抓取」類似，但所有 chunks 都是從遠端來源抓取。\n> 這是最傳統的抓取方式，通常會耗用最多的網路流量與時間，覆寫遠端檔案的風險也與「先建立本機檔案的 chunks，再抓取」選項相近。\n> 不過，由於這是歷史最久、最直接的做法，通常被認為是最穩定的方式。",
     },
@@ -8276,7 +8504,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "フェッチ前にローカルデータベースを作成",
         ko: "가져오기 전에 로컬 데이터베이스를 한 번 생성",
         ru: "Создать локальную базу данных перед загрузкой",
-        zh: "Create a local database once before fetching",
+        zh: "获取前先创建一次本地数据库",
         "zh-tw": "先建立一次本機資料庫，再抓取",
     },
     "RedFlag.Fetch.Method.FetchSmoother": {
@@ -8287,7 +8515,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "フェッチ前にローカルファイルチャンクを作成",
         ko: "가져오기 전에 로컬 파일 청크 생성",
         ru: "Создать локальные чанки перед загрузкой",
-        zh: "Create local file chunks before fetching",
+        zh: "获取前先创建本地文件的数据块",
         "zh-tw": "先建立本機檔案的 chunks，再抓取",
     },
     "RedFlag.Fetch.Method.FetchTraditional": {
@@ -8298,7 +8526,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "リモートからすべてをフェッチ",
         ko: "원격에서 모든 것 가져오기",
         ru: "Загрузить всё с удалённого",
-        zh: "Fetch everything from the remote",
+        zh: "从远程获取全部内容",
         "zh-tw": "從遠端抓取所有內容",
     },
     "RedFlag.Fetch.Method.Title": {
@@ -8309,7 +8537,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "どのようにフェッチしますか？",
         ko: "어떻게 가져오시겠습니까?",
         ru: "Как вы хотите загрузить?",
-        zh: "How do you want to fetch?",
+        zh: "你想如何获取？",
         "zh-tw": "你想要如何抓取？",
     },
     "RedFlag.FetchRemoteConfig.Buttons.Cancel": {
@@ -8320,7 +8548,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "いいえ、ローカル設定を使用",
         ko: "아니요, 로컬 설정을 사용합니다",
         ru: "Нет, использовать локальные настройки",
-        zh: "No, use local settings",
+        zh: "否，使用本地设置",
         "zh-tw": "不用，使用本機設定",
     },
     "RedFlag.FetchRemoteConfig.Buttons.Fetch": {
@@ -8331,7 +8559,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "はい、リモート設定を取得して適用",
         ko: "예, 원격 설정을 가져와 적용합니다",
         ru: "Да, загрузить и применить удалённые настройки",
-        zh: "Yes, fetch and apply remote settings",
+        zh: "是，获取并应用远程设置",
         "zh-tw": "要，抓取並套用遠端設定",
     },
     "RedFlag.FetchRemoteConfig.Message": {
@@ -8342,7 +8570,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "リモートに保存された設定を取得して、このデバイスに適用しますか？",
         ko: "원격에 저장된 환경 설정을 가져와 이 기기에 적용하시겠습니까?",
         ru: "Вы хотите загрузить и применить удалённые настройки?",
-        zh: "Do you want to fetch and apply remotely stored preference settings to the device?",
+        zh: "是否要获取远程保存的偏好设置，并将其应用到此设备？",
         "zh-tw": "要將遠端儲存的偏好設定抓取並套用到此裝置嗎？",
     },
     "RedFlag.FetchRemoteConfig.Title": {
@@ -8353,7 +8581,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "リモート設定の取得",
         ko: "원격 구성 가져오기",
         ru: "Загрузить удалённую конфигурацию",
-        zh: "Fetch Remote Configuration",
+        zh: "获取远程配置",
         "zh-tw": "抓取遠端設定",
     },
     "Reduces storage space by discarding all non-latest revisions. This requires the same amount of free space on the remote server and the local client.":
@@ -8529,7 +8757,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "再確認のためキャンセル",
         ko: "재확인을 위해 취소",
         ru: "Отмена для подтверждения",
-        zh: "Cancel for reconfirmation",
+        zh: "取消并重新确认",
         "zh-tw": "取消，稍後再確認",
     },
     "Replicator.Dialogue.Locked.Action.Fetch": {
@@ -8540,7 +8768,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "このデバイスの同期をリセット",
         ko: "이 기기의 동기화 재설정",
         ru: "Сбросить синхронизацию на этом устройстве",
-        zh: "Reset Synchronisation on This Device",
+        zh: "重置此设备上的同步",
         "zh-tw": "重設此裝置上的同步",
     },
     "Replicator.Dialogue.Locked.Action.Unlock": {
@@ -8551,7 +8779,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "リモートデータベースのロックを解除",
         ko: "원격 데이터베이스 잠금 해제",
         ru: "Разблокировать удалённую базу данных",
-        zh: "Unlock the remote database",
+        zh: "解锁远程数据库",
         "zh-tw": "解鎖遠端資料庫",
     },
     "Replicator.Dialogue.Locked.Message": {
@@ -8562,7 +8790,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "リモートデータベースがロックされています。これはいずれかの端末での再構築が原因です。\nデータベースの破損を避けるため、このデバイスは接続を保留するよう求められています。\n\n3つのオプションがあります：\n\n- このデバイスの同期をリセット\n  最も推奨される信頼性の高い方法です。ローカルデータベースを一度破棄し、リモートデータベースからすべての同期情報を再取得します。ほとんどの場合、これは安全に実行できます。ただし、時間がかかり、安定したネットワークで実行する必要があります。\n- リモートデータベースのロックを解除\n  この方法は、他のレプリケーション(複製)方法ですでに確実に同期されている場合のみ使用できます。単に同じファイルがあるという意味ではありません。確信がない場合は避けてください。\n- 再確認のためキャンセル\n  操作をキャンセルします。次回のリクエスト時に再度確認されます。\n",
         ko: "원격 데이터베이스가 잠겨 있습니다. 이는 일부 터미널에서 데이터베이스를 재구축했기 때문입니다.\n따라서 현재 기기는 데이터베이스 손상을 방지하기 위해 연결을 일시적으로 보류해야 합니다.\n\n선택할 수 있는 세 가지 방법이 있습니다:\n\n- 이 기기의 동기화 재설정\n  가장 권장되고 신뢰할 수 있는 방법입니다. 로컬 데이터베이스를 초기화한 뒤, 원격 데이터베이스의 전체 데이터를 다시 가져옵니다. 대부분의 경우 안전하게 수행할 수 있으나, 시간이 다소 걸리며 안정적인 네트워크 환경에서 진행해야 합니다.\n- 원격 데이터베이스 잠금 해제\n  이 방법은 다른 동기화 방식으로 이미 완전하고 안정적으로 동기화된 경우에만 사용할 수 있습니다. 단순히 파일이 같다는 의미가 아니므로, 확신이 없다면 사용을 피하는 것이 좋습니다.\n- 재확인을 위해 취소\n  이번 작업을 취소하고, 다음 요청 시 다시 안내받습니다.\n",
         ru: "Удалённая база данных заблокирована. Это связано с перестроением на одном из устройств.",
-        zh: "Remote database is locked. This is due to a rebuild on one of the terminals.\nThe device is therefore asked to withhold the connection to avoid database corruption.\n\nThere are three options that we can do:\n\n- Reset Synchronisation on This Device\n  The most preferred and reliable way. This will dispose the local database once, and fetch all from the remote database again, In most case, we can perform this safely. However, it takes some time and should be done in stable network.\n- Unlock the remote database\n  This method can only be used if we are already reliably synchronised by other replication methods. This does not simply mean that we have the same files. If you are not sure, you should avoid it.\n- Cancel for reconfirmation\n    This will cancel the operation. And we will asked again on next request.\n",
+        zh: "Remote database is locked. This is due to a rebuild on one of the terminals.\nThe device is therefore asked to withhold the connection to avoid database corruption.\n\nThere are three options that we can do:\n\n- 重置此设备上的同步\n  The most preferred and reliable way. This will dispose the local database once, and fetch all from the remote database again, In most case, we can perform this safely. However, it takes some time and should be done in stable network.\n- 解锁远程数据库\n  This method can only be used if we are already reliably synchronised by other replication methods. This does not simply mean that we have the same files. If you are not sure, you should avoid it.\n- 取消并重新确认\n    This will cancel the operation. And we will asked again on next request.\n",
         "zh-tw":
             "遠端資料庫已鎖定，這是因為其中一台裝置執行過重建。\n因此系統要求此裝置暫停連線，以避免資料庫損毀。\n\n我們有三種做法：\n\n- 重設此裝置上的同步\n  最建議且最可靠的方式。這會先捨棄本機資料庫，再從遠端資料庫重設所有同步資訊。多數情況下都能安全執行，但會花上一些時間，且應在網路穩定時進行。\n- 解鎖遠端資料庫\n  只有在已透過其他複寫方式可靠同步的情況下才能使用此方式。這不只是指雙方擁有相同的檔案。如果你不確定，請避免使用。\n- 取消，稍後再確認\n    這會取消此操作，下次請求時會再次詢問。\n",
     },
@@ -8574,7 +8802,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "全フェッチがスケジュールされました。プラグインは実行のために再起動されます。",
         ko: "모든 것 가져오기가 예약되었습니다. 이를 수행하기 위해 플러그인이 재시작됩니다.",
         ru: "Загрузка всего запланирована. Плагин будет перезапущен.",
-        zh: "Fetch all has been scheduled. Plug-in will be restarted to perform it.",
+        zh: "已安排获取全部内容。插件将重启以执行该操作。",
         "zh-tw": "已排定執行全部抓取。外掛將重新啟動以執行此作業。",
     },
     "Replicator.Dialogue.Locked.Message.Unlocked": {
@@ -8585,7 +8813,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "リモートデータベースのロックが解除されました。操作を再試行してください。",
         ko: "원격 데이터베이스 잠금이 해제되었습니다. 작업을 다시 시도해 주세요.",
         ru: "Удалённая база данных разблокирована. Повторите операцию.",
-        zh: "The remote database has been unlocked. Please retry the operation.",
+        zh: "远程数据库已解锁。请重试该操作。",
         "zh-tw": "遠端資料庫已解鎖，請重試該操作。",
     },
     "Replicator.Dialogue.Locked.Title": {
@@ -8596,7 +8824,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "ロック中",
         ko: "잠김",
         ru: "Заблокировано",
-        zh: "Locked",
+        zh: "已锁定",
         "zh-tw": "已鎖定",
     },
     "Replicator.Message.Cleaned": {
@@ -8607,7 +8835,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "データベースのクリーナップ中です。レプリケーション(複製)はキャンセルされました。",
         ko: "데이터베이스 정리가 진행 중입니다. 복제가 취소되었습니다",
         ru: "Очистка базы данных в процессе. Репликация отменена",
-        zh: "Database cleaning up is in process. replication has been cancelled",
+        zh: "数据库清理正在进行中，复制已取消。",
         "zh-tw": "資料庫正在清理中，複寫已取消",
     },
     "Replicator.Message.InitialiseFatalError": {
@@ -8618,7 +8846,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "レプリケーターが利用できません。これは致命的なエラーです。",
         ko: "사용 가능한 복제기가 없습니다. 치명적인 오류입니다.",
         ru: "Репликатор недоступен, это фатальная ошибка.",
-        zh: "No replicator is available, this is the fatal error.",
+        zh: "没有可用的复制器，这是一个致命错误。",
         "zh-tw": "沒有可用的複寫器，這是嚴重錯誤。",
     },
     "Replicator.Message.Pending": {
@@ -8629,7 +8857,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "ファイルイベントが保留中です。レプリケーション(複製)はキャンセルされました。",
         ko: "일부 파일 이벤트가 대기 중입니다. 복제가 취소되었습니다.",
         ru: "Некоторые события файлов ожидают. Репликация отменена.",
-        zh: "Some file events are pending. Replication has been cancelled.",
+        zh: "部分文件事件仍在等待处理。复制已取消。",
         "zh-tw": "有部分檔案事件尚待處理，複寫已取消。",
     },
     "Replicator.Message.SomeModuleFailed": {
@@ -8640,7 +8868,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "一部のモジュールの失敗によりレプリケーション(複製)がキャンセルされました。",
         ko: "일부 모듈 실패로 복제가 취소되었습니다",
         ru: "Репликация отменена из-за сбоя модуля",
-        zh: "Replication has been cancelled by some module failure",
+        zh: "由于某个模块出错，复制已取消。",
         "zh-tw": "複寫因某個模組失敗而取消",
     },
     "Replicator.Message.VersionUpFlash": {
@@ -8959,6 +9187,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "房间 ID 后缀：",
         "zh-tw": "房間 ID 後綴：",
     },
+    "Rotation Duration": {
+        def: "Rotation Duration",
+        zh: "令牌轮换时长",
+    },
     "Run Doctor": {
         def: "Run Doctor",
         es: "Ejecutar el Doctor",
@@ -9232,7 +9464,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "シークレットキー",
         ko: "시크릿 키",
         ru: "Секретный ключ",
-        zh: "Secret Key",
+        zh: "私有密钥",
         "zh-tw": "Secret Key",
     },
     "Select active P2P remote": {
@@ -9425,6 +9657,34 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "扫描数据库中未正确存储的文件。",
         "zh-tw": "掃描未正確儲存在資料庫中的檔案。",
     },
+    "SettingService.ConfigurationCouldNotBeDecrypted": {
+        def: "Existing configuration could not be decrypted. The configuration key was not changed.",
+        zh: "无法解密现有配置。配置密钥未更改。",
+    },
+    "SettingService.ConfigurationEncryptionSaveFailed": {
+        def: "Configuration encryption could not be saved. Verify the saved settings and device key before retrying.",
+        zh: "无法保存配置加密。请在重试前检查已保存的设置和设备密钥。",
+    },
+    "SettingService.ConfigurationPassphraseCancelled": {
+        def: "Configuration passphrase entry was cancelled or unavailable. Start-up was stopped; saved settings were retained.",
+        zh: "配置密码短语的输入已取消或不可用。启动已停止，已保存的设置已保留。",
+    },
+    "SettingService.ConfigurationPassphraseDeviceLocalDescription": {
+        def: "This passphrase stays on this device. When another device needs to decrypt protected settings without a saved key, enter the same passphrase at start-up.",
+        zh: "此密码短语只保留在此设备上。当其他设备需要在没有已保存密钥的情况下解密受保护的设置时，请在启动时输入相同的密码短语。",
+    },
+    "SettingService.ConfigurationPassphraseRetryTitle": {
+        def: "Configuration could not be decrypted. Enter the configuration passphrase again.",
+        zh: "无法解密配置。请重新输入配置密码短语。",
+    },
+    "SettingService.ConfigurationPassphraseRollbackFailed": {
+        def: "The configuration passphrase could not be restored after a write failure. Verify the saved settings and device key before retrying.",
+        zh: "写入失败后，无法恢复配置密码短语。请在重试前检查已保存的设置和设备密钥。",
+    },
+    "SettingService.ConfigurationPassphraseTitle": {
+        def: "Configuration passphrase",
+        zh: "配置密码短语",
+    },
     "SettingTab.Message.AskRebuild": {
         def: "Your changes require fetching from the remote database. Do you want to proceed?",
         es: "Tus cambios requieren obtener los datos de la base de datos remota. ¿Quieres continuar?",
@@ -9433,7 +9693,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "変更にはリモートデータベースからのフェッチが必要です。続行しますか？",
         ko: "변경 사항을 적용하려면 원격 데이터베이스에서 가져와야 합니다. 계속 진행하시겠습니까?",
         ru: "Ваши изменения требуют загрузки из удалённой базы данных. Хотите продолжить?",
-        zh: "Your changes require fetching from the remote database. Do you want to proceed?",
+        zh: "你的更改需要从远程数据库获取数据。是否继续？",
         "zh-tw": "你的變更需要從遠端資料庫抓取，要繼續嗎？",
     },
     "Setup Complete: Preparing to Fetch Synchronisation Data": {
@@ -9477,7 +9737,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "適用してフェッチ",
         ko: "적용 후 가져오기",
         ru: "Применить и загрузить",
-        zh: "Apply and Fetch",
+        zh: "应用并获取",
         "zh-tw": "套用並抓取",
     },
     "Setup.Apply.Buttons.ApplyAndMerge": {
@@ -9488,7 +9748,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "適用してマージ",
         ko: "적용 후 병합",
         ru: "Применить и объединить",
-        zh: "Apply and Merge",
+        zh: "应用并合并",
         "zh-tw": "套用並合併",
     },
     "Setup.Apply.Buttons.ApplyAndRebuild": {
@@ -9499,7 +9759,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "適用して再構築",
         ko: "적용 후 재구축",
         ru: "Применить и перестроить",
-        zh: "Apply and Rebuild",
+        zh: "应用并重建",
         "zh-tw": "套用並重建",
     },
     "Setup.Apply.Buttons.Cancel": {
@@ -9510,7 +9770,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "破棄してキャンセル",
         ko: "폐기하고 취소",
         ru: "Отменить и отменить",
-        zh: "Discard and Cancel",
+        zh: "丢弃并取消",
         "zh-tw": "捨棄並取消",
     },
     "Setup.Apply.Buttons.OnlyApply": {
@@ -9521,7 +9781,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "適用のみ",
         ko: "적용만 하기",
         ru: "Только применить",
-        zh: "Only Apply",
+        zh: "仅应用",
         "zh-tw": "僅套用",
     },
     "Setup.Apply.Message": {
@@ -9532,7 +9792,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "新しい設定の準備ができました。適用に進みましょう。\n適用方法はいくつかあります：\n\n- 適用してフェッチ\n  このデバイスを新しいクライアントとして設定します。適用後、リモートサーバーから同期します。\n- 適用してマージ\n  既にファイルがあるデバイスで設定します。ローカルファイルを処理し、差分を転送します。競合が発生する場合があります。\n- 適用して再構築\n  ローカルファイルを使用してリモートを再構築します。これは通常、サーバーが破損した場合や最初からやり直したい場合に行います。\n  他のデバイスはロックされ、再フェッチが必要になります。\n- 適用のみ\n  適用のみを行います。再構築が必要な場合、競合が発生する可能性があります。",
         ko: "새 구성이 준비되었습니다. 이제 적용해 보겠습니다.\n적용 방법은 여러 가지가 있습니다:\n\n- 적용 후 가져오기\n  이 기기를 새 클라이언트로 구성합니다. 적용한 뒤 원격 서버에서 동기화합니다.\n- 적용 후 병합\n  이미 파일이 있는 기기에서 구성합니다. 로컬 파일을 처리한 뒤 차이만 전송합니다. 충돌이 발생할 수 있습니다.\n- 적용 후 재구축\n  로컬 파일로 원격을 재구축합니다. 보통 서버가 손상되었거나 처음부터 다시 시작하려는 경우에 사용합니다.\n  다른 기기는 잠기며 다시 가져오기를 수행해야 합니다.\n- 적용만 하기\n  적용만 합니다. 재구축이 필요한 경우 충돌이 발생할 수 있습니다.",
         ru: "Новая конфигурация готова. Есть несколько способов применить её.",
-        zh: "The new configuration is ready. Let us proceed to apply it.\nThere are several ways to apply this:\n\n- Apply and Fetch\n  Configure this device as a new client. After applying, synchronise from the remote server.\n- Apply and Merge\n  Configure on a device that already has the file. It processes the local files and transfers the differences. Conflicts may arise.\n- Apply and Rebuild\n  Rebuild the remote using local files. This is typically done if the server becomes corrupted or we wish to start from scratch.\n  Other devices will be locked and required to re-fetch.\n- Only Apply\n  Apply only. Conflicts may arise if a rebuild is required.",
+        zh: "新配置已准备就绪，让我们继续应用它。\n应用此配置有以下几种方式：\n\n- 应用并获取\n  将此设备配置为新客户端。应用后，从远程服务器同步。\n- 应用并合并\n  在已有文件的设备上进行配置。它会处理本地文件并传输差异。可能会出现冲突。\n- 应用并重建\n  使用本地文件重建远程。通常在服务器损坏或希望从头开始时使用。\n  其他设备将被锁定，并需要重新获取。\n- 仅应用\n  仅应用配置。如果需要重建，可能会出现冲突。",
         "zh-tw":
             "新的設定已經就緒，接下來要套用它。\n有幾種套用方式：\n\n- 套用並抓取\n  將此裝置設定為新的用戶端。套用後會從遠端伺服器同步。\n- 套用並合併\n  在已經有檔案的裝置上設定。會處理本機檔案並傳輸差異部分，可能會產生衝突。\n- 套用並重建\n  使用本機檔案重建遠端。通常在伺服器損毀或想要從頭開始時執行。\n  其他裝置會被鎖定，需要重新抓取。\n- 僅套用\n  只套用設定。若需要重建，可能會產生衝突。",
     },
@@ -9544,7 +9804,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "${method}からの新しい設定を適用",
         ko: "${method}에서 가져온 새 구성 적용",
         ru: "Применить новую конфигурацию из ${method}",
-        zh: "Apply new configuration from the ${method}",
+        zh: "从 ${method} 应用新配置",
         "zh-tw": "從 ${method} 套用新設定",
     },
     "Setup.Apply.WarningRebuildRecommended": {
@@ -9555,7 +9815,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "注意: 設定の調整後、再構築が必要と判断されました。インポートのみは推奨されません。",
         ko: "참고: 설정을 조정한 결과 재구축이 필요한 것으로 판단되었습니다. 적용만 하는 것은 권장하지 않습니다.",
         ru: "ПРИМЕЧАНИЕ: после настройки изменений определено, что требуется перестроение.",
-        zh: "NOTE: after adjusting the settings, it has been determined that a rebuild is required; Just Import is not recommended.",
+        zh: "注意：调整设置后，已判定需要重建；不推荐仅导入。",
         "zh-tw": "注意：調整設定後判斷需要重建；不建議僅匯入設定。",
     },
     "Setup.Doctor.Buttons.No": {
@@ -9566,7 +9826,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "いいえ、URIの設定をそのまま使用",
         ko: "아니요, URI에 담긴 설정을 그대로 사용합니다",
         ru: "Нет, использовать настройки из URI как есть",
-        zh: "No, please use the settings in the URI as is",
+        zh: "否，请按原样使用 URI 中的设置",
         "zh-tw": "不用，請直接使用 URI 中的設定",
     },
     "Setup.Doctor.Buttons.Yes": {
@@ -9577,7 +9837,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "はい、診断ツールに相談する",
         ko: "예, 설정 진단 마법사를 실행합니다",
         ru: "Да, пожалуйста, запустить диагностику",
-        zh: "Yes, please consult the doctor",
+        zh: "是，请运行诊断",
         "zh-tw": "要，請諮詢診斷",
     },
     "Setup.Doctor.Message": {
@@ -9588,7 +9848,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "Self-hosted LiveSyncは徐々に歴史が長くなり、一部の推奨設定が変更されています。\n\nセットアップは、これを行う非常に良い機会です。\n\nインポートされた設定が最新の状態と比較して最適かどうかを確認するために、診断ツールを実行しますか？",
         ko: "Self-hosted LiveSync는 오랜 기간에 걸쳐 발전해 왔고, 그동안 권장 설정도 일부 바뀌었습니다.\n\n지금 설정 단계가 이를 점검하기에 아주 좋은 시점입니다.\n\n가져온 설정이 최신 기준에 비추어 최적인지 확인하도록 설정 진단 마법사를 실행하시겠습니까?",
         ru: "Self-hosted LiveSync постепенно набрал историю и некоторые рекомендуемые настройки изменились.",
-        zh: "Self-hosted LiveSync has gradually become longer in history and some recommended settings have changed.\n\nNow, setup is a very good time to do this.\n\nDo you want to run Doctor to check if the imported settings are optimal compared to the latest state?",
+        zh: "Self-hosted LiveSync 已经历经多次演进，一些推荐设置也随之发生了变化。\n\n现在正值设置阶段，是进行检查的好时机。\n\n你要运行诊断，检查导入的设置相对于最新状态是否最优吗？",
         "zh-tw":
             "Self-hosted LiveSync 的歷史逐漸變長，部分建議設定也隨之改變。\n\n現在正是進行這項檢查的好時機。\n\n要執行設定診斷，檢查匯入的設定是否符合最新建議嗎？",
     },
@@ -9600,7 +9860,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "診断ツールに相談しますか？",
         ko: "설정 진단 마법사를 실행할까요?",
         ru: "Хотите запустить диагностику?",
-        zh: "Do you want to consult the doctor?",
+        zh: "要运行诊断吗？",
         "zh-tw": "要諮詢設定診斷嗎？",
     },
     "Setup.FetchRemoteConf.Buttons.Fetch": {
@@ -9611,7 +9871,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "はい、設定を取得",
         ko: "예, 구성을 가져옵니다",
         ru: "Да, загрузить конфигурацию",
-        zh: "Yes, please fetch the configuration",
+        zh: "是，请获取配置",
         "zh-tw": "要，請抓取設定",
     },
     "Setup.FetchRemoteConf.Buttons.Skip": {
@@ -9622,7 +9882,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "いいえ、URIの設定を使用",
         ko: "아니요, URI에 담긴 설정을 사용합니다",
         ru: "Нет, использовать настройки из URI",
-        zh: "No, please use the settings in the URI",
+        zh: "否，请使用 URI 中的设置",
         "zh-tw": "不用，請使用 URI 中的設定",
     },
     "Setup.FetchRemoteConf.Message": {
@@ -9633,7 +9893,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "既に他のデバイスと同期したことがある場合、リモートデータベースには同期されたデバイス間の適切な設定値が保存されています。プラグインは堅牢な設定のためにそれらを取得したいと考えています。\n\nただし、1つ確認が必要です。現在、ネットワークに安全にアクセスして設定を取得できる状況ですか？\n\n注意: リモートデータベースがSSL証明書でホストされており、ネットワークが侵害されていなければ、ほとんどの場合安全に実行できます。",
         ko: "다른 기기와 이미 한 번이라도 동기화했다면, 원격 데이터베이스에 동기화된 기기 사이에 적합한 구성 값이 저장되어 있습니다. 플러그인은 더 견고한 구성을 위해 이 값을 가져오려고 합니다.\n\n다만 한 가지 확인이 필요합니다. 지금 네트워크에 안전하게 접근해 설정을 가져올 수 있는 상황인가요?\n\n참고: 원격 데이터베이스가 SSL 인증서로 보호되어 있고 네트워크가 안전하다면, 대부분의 경우 그대로 진행해도 괜찮습니다.",
         ru: "Если мы уже синхронизировались с другим устройством, удалённая база данных хранит подходящие значения конфигурации.",
-        zh: "If we have already synchronised once with another device, the remote database stores the suitable configuration values between the synchronised devices. The plug-in would like to retrieve them for robust configuration.\n\nHowever, we have to make sure the one thing. Are we currently in a situation where we can access the network safely and retrieve the settings?\n\nNote: Mostly, you are safe to do this, that your remote database is hosted with a SSL certificate, and your network is not compromised.",
+        zh: "如果我们之前已经与另一台设备同步过，远程数据库会保存已同步设备之间适用的配置值。插件希望获取这些值，以便进行更可靠的配置。\n\n但有一点必须确认：我们当前是否处于可以安全访问网络并获取这些设置的环境中？\n\n注意：通常情况下，只要你的远程数据库使用了 SSL 证书，且网络未被入侵，执行此操作就是安全的。",
         "zh-tw":
             "如果我們已經與其他裝置同步過一次，遠端資料庫會儲存這些已同步裝置之間適用的設定值。外掛想要取得這些值，以取得更穩健的設定。\n\n不過，我們需要先確認一件事：目前是否處於能安全存取網路並取得設定的情況？\n\n注意：多數情況下這樣做是安全的，只要你的遠端資料庫使用 SSL 憑證，且網路沒有遭到入侵。",
     },
@@ -9645,7 +9905,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "リモートデータベースから設定を取得しますか？",
         ko: "원격 데이터베이스에서 구성을 가져올까요?",
         ru: "Загрузить конфигурацию с удалённой базы данных?",
-        zh: "Fetch configuration from remote database?",
+        zh: "要从远程数据库获取配置吗？",
         "zh-tw": "要從遠端資料庫抓取設定嗎？",
     },
     "Setup.QRCode": {
@@ -9656,7 +9916,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: '設定を転送するためのQRコードを生成しました。スマートフォンや他のデバイスでQRコードをスキャンしてください。\n注意: QRコードは暗号化されていないため、開く際は注意してください。\n\n>[!FOR YOUR EYES ONLY]-\n> <div class="sls-qr">${qr_image}</div>',
         ko: '설정을 전송하기 위한 QR 코드를 생성했습니다. 휴대폰이나 다른 기기로 QR 코드를 스캔해 주세요.\n참고: QR 코드는 암호화되지 않았으므로 열 때 주의하세요.\n\n>[!FOR YOUR EYES ONLY]-\n> <div class="sls-qr">${qr_image}</div>',
         ru: 'Мы сгенерировали QR-код для передачи настроек. Отсканируйте QR-код телефоном или другим устройством.\nВнимание: QR-код не зашифрован, открывайте его осторожно.\n\n>[!FOR YOUR EYES ONLY]-\n> <div class="sls-qr">${qr_image}</div>',
-        zh: 'We have generated a QR code to transfer the settings. Please scan the QR code with your phone or other device.\nNote: The QR code is not encrypted, so be careful to open this.\n\n>[!FOR YOUR EYES ONLY]-\n> <div class="sls-qr">${qr_image}</div>',
+        zh: '我们已生成用于传输设置的二维码。请使用手机或其他设备扫描该二维码。\n注意：此二维码未加密，请谨慎打开。\n\n>[!FOR YOUR EYES ONLY]-\n> <div class="sls-qr">${qr_image}</div>',
         "zh-tw":
             '我們已產生用於傳遞設定的 QR 碼，請用你的手機或其他裝置掃描這個 QR 碼。\n注意：這個 QR 碼未經加密，開啟時請務必小心。\n\n>[!僅供本人查看]-\n> <div class="sls-qr">${qr_image}</div>',
     },
@@ -10170,6 +10430,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "信令服务器连接",
         "zh-tw": "訊號伺服器連線",
     },
+    "Signalling Relays": {
+        def: "Signalling Relays",
+        zh: "信令中继",
+    },
     "Signalling Status": {
         def: "Signalling Status",
         es: "Estado de la señalización",
@@ -10182,6 +10446,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         {
             def: "Since you have chosen to overwrite all local files with remote data, **how would you like to handle local files that are not present in the remote database?**\n\n- **${DELETE_ALL}**: Local-only files and remote-deleted files will be removed.\n  This option will make your local vault exactly the same as the remote database, but please make sure you have a backup if there is any important data in your vault.\n- **${DELETE_NONE}**: All existing local files will be preserved.\n  This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.",
             es: "Como has elegido sobrescribir todos los archivos locales con los datos remotos, **¿cómo quieres gestionar los archivos locales que no existen en la base de datos remota?**\n\n- **${DELETE_ALL}**: se eliminarán los archivos que solo existen en local y los que se han borrado en el remoto.\n  Esta opción hará que tu vault local sea exactamente igual que la base de datos remota; asegúrate de tener una copia de seguridad si tienes datos importantes en tu vault.\n- **${DELETE_NONE}**: se conservarán todos los archivos locales existentes.\n  Esta opción mantiene todos tus archivos locales, pero puede causar duplicados si hay archivos que existen en local pero no en el remoto. Puedes limpiar esos duplicados manualmente después de sincronizar.",
+            zh: "由于你选择了用远程数据覆盖所有本地文件，**对于远程数据库中不存在的本地文件，你希望如何处理？**\n\n- **${DELETE_ALL}**：仅存在于本地的文件和在远程已被删除的文件将被移除。\n  此选项会让你的本地库与远程数据库完全一致，但如果库中有重要数据，请务必先做好备份。\n- **${DELETE_NONE}**：保留所有现有的本地文件。\n  此选项会保留你所有的本地文件，但如果某些文件仅存在于本地而不在远程，可能会产生重复文件。同步完成后，你可以手动清理这些重复文件。",
         },
     "Skip and close": {
         def: "Skip and close",
@@ -10213,6 +10478,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Some files failed to synchronise. What would you like to do?": {
         def: "Some files failed to synchronise. What would you like to do?",
         es: "Algunos archivos no se pudieron sincronizar. ¿Qué quieres hacer?",
+        zh: "部分文件同步失败。你希望如何处理？",
     },
     "Start Broadcasting": {
         def: "Start Broadcasting",
@@ -10319,6 +10585,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "强烈推荐",
         "zh-tw": "強烈建議",
     },
+    "Subject (whoami)": {
+        def: "Subject (whoami)",
+        zh: "主体（whoami）",
+    },
     "Suppress notification of hidden files change": {
         def: "Suppress notification of hidden files change",
         es: "Suprimir notificaciones de cambios en archivos ocultos",
@@ -10466,6 +10736,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Synchronisation Issues Detected": {
         def: "Synchronisation Issues Detected",
         es: "Se han detectado problemas de sincronización",
+        zh: "检测到同步问题",
     },
     "Synchronisation utilising journal files. You must have set up an S3/MinIO/R2 compatible object storage.": {
         def: "Synchronisation utilising journal files. You must have set up an S3/MinIO/R2 compatible object storage.",
@@ -10537,6 +10808,15 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
             zh: "仅供测试 - 通过同步文件的较新副本来解决文件冲突,这可能会覆盖修改过的文件。请注意 ",
             "zh-tw": "僅供測試 —— 透過同步較新的檔案版本解決衝突，這可能會覆寫已修改的檔案，請注意。",
         },
+    "The algorithm used for JWT authentication.": {
+        def: "The algorithm used for JWT authentication.",
+        zh: "用于 JWT 认证的算法。",
+    },
+    "The Application ID for P2P connection. This should be same among your devices. Default is 'self-hosted-livesync' and could not be modified from the UI.":
+        {
+            def: "The Application ID for P2P connection. This should be same among your devices. Default is 'self-hosted-livesync' and could not be modified from the UI.",
+            zh: "用于 P2P 连接的应用 ID。所有设备应保持相同。默认值为 'self-hosted-livesync'，无法在界面中修改。",
+        },
     "The connection test cannot add a signalling relay while P2P is active. Use the active relay settings, or disconnect P2P before testing.":
         {
             def: "The connection test cannot add a signalling relay while P2P is active. Use the active relay settings, or disconnect P2P before testing.",
@@ -10551,6 +10831,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "与服务器的连接已配置成功。下一步，",
         "zh-tw": "與伺服器的連線已成功設定完成。接下來，",
     },
+    "The credential/password for the TURN servers.": {
+        def: "The credential/password for the TURN servers.",
+        zh: "TURN 服务器的凭据/密码。",
+    },
     "The delay for consecutive on-demand fetches": {
         def: "The delay for consecutive on-demand fetches",
         es: "Retraso entre obtenciones consecutivas",
@@ -10611,6 +10895,14 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
             "zh-tw":
                 "IndexedDB 轉接器在某些情況下通常能提供較佳效能，但在 LiveSync 模式下已發現可能導致記憶體洩漏。使用 LiveSync 模式時，請改用 IDB 轉接器。",
         },
+    "The key (PSK in HSxxx in base64, or private key in ESxxx in PEM) used for JWT authentication.": {
+        def: "The key (PSK in HSxxx in base64, or private key in ESxxx in PEM) used for JWT authentication.",
+        zh: "用于 JWT 认证的密钥（base64 格式的 PSK，形如 HSxxx；或 PEM 格式的私钥，形如 ESxxx）。",
+    },
+    "The key ID. this should be matched with CouchDB->jwt_keys->ALG:_`kid`.": {
+        def: "The key ID. this should be matched with CouchDB->jwt_keys->ALG:_`kid`.",
+        zh: "密钥 ID。它应与 CouchDB->jwt_keys->ALG:_`kid` 相匹配。",
+    },
     "the latest synchronisation data will be downloaded from the server to this device.": {
         def: "the latest synchronisation data will be downloaded from the server to this device.",
         es: "se descargarán a este dispositivo los datos de sincronización más recientes del servidor.",
@@ -10674,6 +10966,15 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "基于事件自动同步的最小间隔。",
         "zh-tw": "事件觸發自動同步的最小間隔。",
     },
+    "The Nostr relay servers to establish connections for P2P connections. Multiple servers can be separated by commas.":
+        {
+            def: "The Nostr relay servers to establish connections for P2P connections. Multiple servers can be separated by commas.",
+            zh: "用于建立 P2P 连接的 Nostr 中继服务器。多个服务器可以用逗号分隔。",
+        },
+    "The Passphrase for P2P connection. This should be same among your devices.": {
+        def: "The Passphrase for P2P connection. This should be same among your devices.",
+        zh: "用于 P2P 连接的密码短语。你的所有设备上都应使用相同的密码短语。",
+    },
     "The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.":
         {
             def: "The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.",
@@ -10692,6 +10993,14 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "远端已设置好，且配置兼容（或经此操作后已兼容）。",
         "zh-tw": "遠端已經設定完成，且設定相容（或透過此操作變得相容）。",
     },
+    "The Room ID for P2P connection. This should be same among your devices.": {
+        def: "The Room ID for P2P connection. This should be same among your devices.",
+        zh: "用于 P2P 连接的房间 ID。所有设备应使用相同的房间 ID。",
+    },
+    "The Rotation duration of token in minutes. Each generated tokens will be valid only within this duration.": {
+        def: "The Rotation duration of token in minutes. Each generated tokens will be valid only within this duration.",
+        zh: "令牌的轮换时长（单位：分钟）。每个生成的令牌仅在此时长内有效。",
+    },
     "The Setup-URI does not appear to be valid. Please check that you have copied it correctly.": {
         def: "The Setup-URI does not appear to be valid. Please check that you have copied it correctly.",
         es: "El Setup-URI no parece válido. Comprueba que lo hayas copiado correctamente.",
@@ -10716,6 +11025,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "唯一的权威主副本",
         "zh-tw": "唯一且具權威性的主要複本",
     },
+    "The subject for JWT authentication. Mostly username.": {
+        def: "The subject for JWT authentication. Mostly username.",
+        zh: "JWT 认证的主体，通常为用户名。",
+    },
     "the synchronisation data on the server will be built based on the current data on this device.": {
         def: "the synchronisation data on the server will be built based on the current data on this device.",
         es: "los datos de sincronización del servidor se construirán a partir de los datos actuales de este dispositivo.",
@@ -10724,6 +11037,14 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "服务器上的同步数据将基于本设备的当前数据构建。",
         "zh-tw": "伺服器上的同步資料將依此裝置目前的資料建立。",
     },
+    "The TURN servers to use for P2P connections. Multiple servers can be separated by commas.": {
+        def: "The TURN servers to use for P2P connections. Multiple servers can be separated by commas.",
+        zh: "用于 P2P 连接的 TURN 服务器。多个服务器可用逗号分隔。",
+    },
+    "The username for the TURN servers.": {
+        def: "The username for the TURN servers.",
+        zh: "TURN 服务器的用户名。",
+    },
     Themes: {
         def: "Themes",
         es: "Temas",
@@ -10951,6 +11272,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "TURN 服务器地址（逗号分隔）",
         "zh-tw": "TURN 伺服器網址（以逗號分隔）",
     },
+    "TURN Servers": {
+        def: "TURN Servers",
+        zh: "TURN 服务器",
+    },
     "TURN Username": {
         def: "TURN Username",
         es: "Usuario de TURN",
@@ -10975,7 +11300,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "無視",
         ko: "무시",
         ru: "Отмена",
-        zh: "Dismiss",
+        zh: "忽略",
         "zh-tw": "不處理",
     },
     "TweakMismatchResolve.Action.EnableAutoAcceptCompatible": {
@@ -10994,7 +11319,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "設定済みの設定を使用",
         ko: "구성된 설정 사용",
         ru: "Использовать настроенные параметры",
-        zh: "Use configured settings",
+        zh: "使用已配置的设置",
         "zh-tw": "採用已設定的值",
     },
     "TweakMismatchResolve.Action.UseMine": {
@@ -11005,7 +11330,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "リモートデータベースの設定を更新",
         ko: "원격 데이터베이스 설정 업데이트",
         ru: "Обновить настройки удалённой базы данных",
-        zh: "Update remote database settings",
+        zh: "更新远程数据库设置",
         "zh-tw": "更新遠端資料庫設定",
     },
     "TweakMismatchResolve.Action.UseMineAcceptIncompatible": {
@@ -11016,7 +11341,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "リモートデータベースの設定を更新するがそのまま維持",
         ko: "원격 데이터베이스 설정 업데이트하지만 그대로 유지",
         ru: "Обновить настройки, но оставить как есть",
-        zh: "Update remote database settings but keep as is",
+        zh: "更新远程数据库设置，但忽略不兼容问题",
         "zh-tw": "更新遠端資料庫設定，但保持現狀",
     },
     "TweakMismatchResolve.Action.UseMineWithRebuild": {
@@ -11027,7 +11352,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "リモートデータベースの設定を更新して再構築",
         ko: "원격 데이터베이스 설정 업데이트하고 다시 재구축",
         ru: "Обновить настройки и перестроить снова",
-        zh: "Update remote database settings and rebuild again",
+        zh: "更新远程数据库设置并再次重建",
         "zh-tw": "更新遠端資料庫設定並再次重建",
     },
     "TweakMismatchResolve.Action.UseRemote": {
@@ -11038,7 +11363,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "このデバイスに設定を適用",
         ko: "이 기기에 설정 적용",
         ru: "Применить настройки к этому устройству",
-        zh: "Apply settings to this device",
+        zh: "将设置应用到此设备",
         "zh-tw": "將設定套用到此裝置",
     },
     "TweakMismatchResolve.Action.UseRemoteAcceptIncompatible": {
@@ -11049,7 +11374,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "このデバイスに設定を適用し、非互換性を無視",
         ko: "이 기기에 설정 적용하지만 호환성 문제 무시",
         ru: "Применить настройки, но игнорировать несовместимость",
-        zh: "Apply settings to this device, but and ignore incompatibility",
+        zh: "将设置应用到此设备，但忽略不兼容问题",
         "zh-tw": "將設定套用到此裝置，並忽略不相容之處",
     },
     "TweakMismatchResolve.Action.UseRemoteWithRebuild": {
@@ -11060,7 +11385,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "このデバイスに設定を適用し、再フェッチ",
         ko: "이 기기에 설정 적용하고 다시 가져오기",
         ru: "Применить настройки и загрузить снова",
-        zh: "Apply settings to this device, and fetch again",
+        zh: "将设置应用到此设备，并重新获取",
         "zh-tw": "將設定套用到此裝置，並再次抓取",
     },
     "TweakMismatchResolve.Message.AutoAcceptCompatibleUndefined": {
@@ -11080,7 +11405,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "\nリモートデータベースの設定は以下の通りです。これらの値は、このデバイスと少なくとも1回同期された他のデバイスによって設定されています。\n\nこれらの設定を使用する場合は、設定済みの設定を使用を選択してください。\nこのデバイスの設定を維持する場合は、無視を選択してください。\n\n${table}\n\n>[!TIP]\n> すべての設定を同期したい場合は、この機能で最小限の設定を適用した後、`Sync settings via markdown`を使用してください。\n\n${additionalMessage}",
         ko: "\n원격 데이터베이스의 설정은 다음과 같습니다. 이 값들은 이 기기와 최소 한 번 동기화된 다른 기기에서 구성된 것입니다.\n\n이 설정을 사용하려면 구성된 설정 사용를 선택해 주세요.\n이 기기의 설정을 유지하려면 무시를 선택해 주세요.\n\n${table}\n\n>[!TIP]\n> 모든 설정을 동기화하려면 이 기능으로 최소 구성을 적용한 후 `마크다운을 통한 설정 동기화`를 사용해 주세요.\n\n${additionalMessage}",
         ru: "\nНастройки в удалённой базе данных следующие. Эти значения настроены другими устройствами, которые хотя бы раз синхронизировались с этим устройством.\n\nЕсли вы хотите использовать эти настройки, выберите Использовать настроенные параметры.\nЕсли вы хотите сохранить настройки этого устройства, выберите Отмена.\n\n${table}\n\n>[!TIP]\n> Если вы хотите синхронизировать все настройки, используйте «Синхронизация настроек через Markdown» после применения минимальной конфигурации этой функцией.\n\n${additionalMessage}",
-        zh: "\nThe settings in the remote database are as follows. These values are configured by other devices, which are synchronised with this device at least once.\n\nIf you want to use these settings, please select Use configured settings.\nIf you want to keep the settings of this device, please select Dismiss.\n\n${table}\n\n>[!TIP]\n> If you want to synchronise all settings, please use `Sync settings via markdown` after applying minimal configuration with this feature.\n\n${additionalMessage}",
+        zh: "\n远程数据库中的设置如下。这些值由与此设备至少同步过一次的其他设备配置。\n\n如果你想使用这些设置，请选择 使用已配置的设置。\n如果你想保留此设备的设置，请选择 忽略。\n\n${table}\n\n>[!TIP]\n> 如果你想同步全部设置，请先使用此功能应用最小配置，然后使用 `Sync settings via markdown`。\n\n${additionalMessage}",
         "zh-tw":
             "\n遠端資料庫中的設定如下。這些值由其他裝置所設定，而那些裝置至少與此裝置同步過一次。\n\n如果你想使用這些設定，請選擇「採用已設定的值」。\n如果你想保留此裝置的設定，請選擇「不處理」。\n\n${table}\n\n>[!TIP]\n> 如果你想同步所有設定，請先用此功能套用最小設定，再使用 `Sync settings via markdown`。\n\n${additionalMessage}",
     },
@@ -11092,7 +11417,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "設定がリモートサーバーの設定と一致しません。\n\n以下の設定が一致している必要があります：\n\n${table}\n\n判断をお知らせください。\n\n${additionalMessage}",
         ko: "구성이 원격 서버의 것과 일치하지 않습니다.\n\n다음 구성이 일치해야 합니다:\n\n${table}\n\n결정을 알려주세요.\n\n${additionalMessage}",
         ru: "Ваша конфигурация не совпадает с конфигурацией на удалённом сервере.\n\nСледующие параметры должны совпадать:\n\n${table}\n\nСообщите нам своё решение.\n\n${additionalMessage}",
-        zh: "Your configuration has not been matched with the one on the remote server.\n\nFollowing configuration should be matched:\n\n${table}\n\nLet us know your decision.\n\n${additionalMessage}",
+        zh: "你的配置与远程服务器上的配置不一致。\n\n以下配置应当保持一致：\n\n${table}\n\n请告知你的决定。\n\n${additionalMessage}",
         "zh-tw":
             "你的設定與遠端伺服器上的設定不一致。\n\n以下設定需要保持一致：\n\n${table}\n\n請告訴我們你的決定。\n\n${additionalMessage}",
     },
@@ -11120,7 +11445,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "\n>[!NOTICE]\n> 一部の変更は互換性がありますが、追加のストレージと転送量を消費する可能性があります。再構築をお勧めします。ただし、再構築は現時点では実行されない場合がありますが、将来のメンテナンスで実装される可能性があります。\n> ***適用には時間と安定したネットワーク接続が必要です！***",
         ko: "\n>[!NOTICE]\n> 일부 변경사항은 호환 가능하지만 추가 스토리지 및 전송량을 소모할 수 있습니다. 재구축을 권장합니다. 하지만 현재 재구축을 수행하지 않더라도 향후 유지보수에서 구현될 수 있습니다.\n> ***시간적 여유가 있고 안정적인 네트워크에 연결된 상태에서 적용해 주세요!***",
         ru: "Некоторые изменения совместимы, но могут потребовать дополнительного хранилища. Рекомендуется перестроение.",
-        zh: "\n>[!NOTICE]\n> Some changes are compatible but may consume extra storage and transfer volumes. A rebuild is recommended. However, a rebuild may not be performed at present, but may be implemented in future maintenance.\n> ***Please ensure that you have time and are connected to a stable network to apply!***",
+        zh: "\n>[!NOTICE]\n> 部分更改是兼容的，但可能会占用额外的存储空间和传输流量。建议进行重建。不过，也可以暂不重建，留待今后维护时再进行。\n> ***应用前请确保你有充足的时间，并已连接到稳定的网络！***",
         "zh-tw":
             "\n>[!NOTICE]\n> 部分變更雖然相容，但可能耗用額外的儲存空間與傳輸量，建議進行重建。不過目前可能不會執行重建，未來的維護作業可能會實作。\n> ***請確認你有足夠時間且網路連線穩定，再進行套用！***",
     },
@@ -11132,7 +11457,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "\n>[!WARNING]\n> 一部のリモート設定はこのデバイスのローカルデータベースと互換性がありません。ローカルデータベースの再構築が必要です。\n> ***適用には時間と安定したネットワーク接続が必要です！***",
         ko: "\n>[!WARNING]\n> 일부 원격 구성이 이 기기의 로컬 데이터베이스와 호환되지 않습니다. 로컬 데이터베이스 재구축이 필요합니다.\n> ***시간적 여유가 있고 안정적인 네트워크에 연결된 상태에서 적용해 주세요!***",
         ru: "Некоторые удалённые конфигурации несовместимы с локальной базой данных. Требуется перестроение.",
-        zh: "\n>[!WARNING]\n> Some remote configurations are not compatible with the local database of this device. Rebuilding the local database will be required.\n> ***Please ensure that you have time and are connected to a stable network to apply!***",
+        zh: "\n>[!WARNING]\n> 部分远程配置与本设备的本地数据库不兼容，将需要重建本地数据库。\n> ***应用前请确保你有充足的时间，并已连接到稳定的网络！***",
         "zh-tw":
             "\n>[!WARNING]\n> 部分遠端設定與此裝置的本機資料庫不相容，將需要重建本機資料庫。\n> ***請確認你有足夠時間且網路連線穩定，再進行套用！***",
     },
@@ -11144,7 +11469,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "\n>[!NOTICE]\n> ローカルデータベースとリモートデータベースの非互換性を引き起こす値の違いが検出されました。\n> 一部の変更は互換性がありますが、追加のストレージと転送量を消費する可能性があります。再構築をお勧めします。ただし、再構築は現時点では実行されない場合がありますが、将来のメンテナンスで実装される可能性があります。\n> 再構築を行う場合は数分以上かかります。**今実行しても安全か確認してください。**",
         ko: "\n>[!NOTICE]\n> 로컬 데이터베이스와 원격 데이터베이스가 호환되지 않도록 만드는 값들이 다른 것을 감지했습니다.\n> 일부 변경사항은 호환 가능하지만 추가 스토리지 및 전송량을 소모할 수 있습니다. 재구축을 권장합니다. 하지만 현재 재구축을 수행하지 않더라도 향후 유지보수에서 구현될 수 있습니다.\n> 재구축을 원한다면 몇 분 이상 소요됩니다. **지금 수행해도 안전한지 확인해 주세요.**",
         ru: "Обнаружены значения, несовместимые с удалённой базой данных. Рекомендуется перестроение.",
-        zh: "\n>[!NOTICE]\n> We have detected that some of the values are different to make incompatible the local database with the remote database.\n> Some changes are compatible but may consume extra storage and transfer volumes. A rebuild is recommended. However, a rebuild may not be performed at present, but may be implemented in future maintenance.\n> If you want to rebuild, it takes a few minutes or more. **Make sure it is safe to perform it now.**",
+        zh: "\n>[!NOTICE]\n> 我们检测到部分值存在差异，导致本地数据库与远程数据库不兼容。\n> 部分更改是兼容的，但可能会占用额外的存储空间和传输流量。建议进行重建。不过，也可以暂不重建，留待今后维护时再进行。\n> 如果你要重建，大约需要几分钟或更长时间。**请先确认现在执行是安全的。**",
         "zh-tw":
             "\n>[!NOTICE]\n> 我們偵測到部分值不同，會使本機資料庫與遠端資料庫不相容。\n> 部分變更雖然相容，但可能耗用額外的儲存空間與傳輸量，建議進行重建。不過目前可能不會執行重建，未來的維護作業可能會實作。\n> 如果你要重建，會花上數分鐘甚至更久。**請確認現在執行是安全的。**",
     },
@@ -11156,7 +11481,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "\n>[!WARNING]\n> ローカルデータベースとリモートデータベースの非互換性を引き起こす値の違いが検出されました。\n> ローカルまたはリモートの再構築が必要です。どちらも数分以上かかります。**今実行しても安全か確認してください。**",
         ko: "\n>[!WARNING]\n> 로컬 데이터베이스와 원격 데이터베이스가 호환되지 않도록 만드는 값들이 다른 것을 감지했습니다.\n> 로컬 또는 원격 재구축이 필요합니다. 둘 다 몇 분 이상 소요됩니다. **지금 수행해도 안전한지 확인해 주세요.**",
         ru: "Обнаружены значения, несовместимые с удалённой базой данных. Требуется перестроение.",
-        zh: "\n>[!WARNING]\n> We have detected that some of the values are different to make incompatible the local database with the remote database.\n> Either local or remote rebuilds are required. Both of them takes a few minutes or more. **Make sure it is safe to perform it now.**",
+        zh: "\n>[!WARNING]\n> 我们检测到某些值存在差异，导致本地数据库与远程数据库不兼容。\n> 需要重建本地或远程其中之一，两者都需要几分钟甚至更长时间。**请确保现在执行此操作是安全的。**",
         "zh-tw":
             "\n>[!WARNING]\n> 我們偵測到部分值不同，會使本機資料庫與遠端資料庫不相容。\n> 需要重建本機或遠端其中一方，兩者都會花上數分鐘甚至更久。**請確認現在執行是安全的。**",
     },
@@ -11168,7 +11493,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "| 値の名前 | このデバイス | リモート |\n|: --- |: ---- :|: ---- :|\n${rows}\n\n",
         ko: "| 값 이름 | 이 기기 | 원격 |\n|: --- |: ---- :|: ---- :|\n${rows}\n\n",
         ru: "| Имя значения | Это устройство | На удалённом |\n|: --- |: ---- :|: ---- :|\n${rows}\n\n",
-        zh: "| Value name | This device | On Remote |\n|: --- |: ---- :|: ---- :|\n${rows}\n\n",
+        zh: "| 值名称 | 此设备 | 远程 |\n|: --- |: ---- :|: ---- :|\n${rows}\n\n",
         "zh-tw": "| 設定項目 | 此裝置 | 遠端 |\n|: --- |: ---- :|: ---- :|\n${rows}\n\n",
     },
     "TweakMismatchResolve.Table.Row": {
@@ -11190,7 +11515,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "設定の不一致が検出されました",
         ko: "구성 불일치 감지",
         ru: "Обнаружено несоответствие конфигурации",
-        zh: "Configuration Mismatch Detected",
+        zh: "检测到配置不一致",
         "zh-tw": "偵測到設定不一致",
     },
     "TweakMismatchResolve.Title.AutoAcceptCompatible": {
@@ -11209,7 +11534,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "設定の不一致が検出されました",
         ko: "구성 불일치 감지",
         ru: "Обнаружено несоответствие конфигурации",
-        zh: "Configuration Mismatch Detected",
+        zh: "检测到配置不一致",
         "zh-tw": "偵測到設定不一致",
     },
     "TweakMismatchResolve.Title.UseRemoteConfig": {
@@ -11220,7 +11545,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         ja: "リモート設定を使用",
         ko: "원격 구성 사용",
         ru: "Использовать удалённую конфигурацию",
-        zh: "Use Remote Configuration",
+        zh: "使用远程配置",
         "zh-tw": "使用遠端設定",
     },
     "Ui.Common.LocalDatabaseInitialisationFailed": {
@@ -13558,6 +13883,14 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "使用 JWT 身份验证",
         "zh-tw": "使用 JWT 驗證",
     },
+    "Use JWT instead of Basic Authentication": {
+        def: "Use JWT instead of Basic Authentication",
+        zh: "使用 JWT 而非 Basic 认证",
+    },
+    "Use Only Local Chunks": {
+        def: "Use Only Local Chunks",
+        zh: "仅使用本地数据块",
+    },
     "Use Path-Style Access": {
         def: "Use Path-Style Access",
         es: "Usar acceso de tipo ruta (path-style)",
@@ -13574,6 +13907,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "使用随机数",
         "zh-tw": "使用隨機數字",
     },
+    "Use Request API to avoid `inevitable` CORS problem": {
+        def: "Use Request API to avoid `inevitable` CORS problem",
+        zh: "使用 Request API 以避免 `inevitable` CORS 问题",
+    },
     "Use Segmented-splitter": {
         def: "Use Segmented-splitter",
         es: "Usar divisor segmentado",
@@ -13599,6 +13936,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
     "Use the detailed flow": {
         def: "Use the detailed flow",
         es: "Usar el flujo detallado",
+        zh: "使用详细流程",
     },
     "Use the trash bin": {
         def: "Use the trash bin",
@@ -13706,6 +14044,7 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         {
             def: "We are about to retrieve the remote data.\n\nFirstly, how shall we handle the data retrieved from this remote source?\n\n- **${NEWER_WINS}**: Compares the modified time of files and takes the newer one.\n  If you have been using Self-hosted LiveSync and have made changes on multiple devices, this option may be suitable for you as it tries to merge changes based on modified time.\n- **${REMOTE_WINS}**: Remote data is the source of truth.\n  If you are new to using Self-hosted LiveSync. This option may be easiest to understand and get started with.\n  It will overwrite all your local files with the remote data, so please make sure you have a backup if there is any important data in your vault.\n- **${DETAILED}**: Opens the detailed setup wizard.\n  If you want to have more control over the synchronisation process, or want to review the changes before applying, you can choose this option to use the detailed flow.",
             es: "Vamos a obtener los datos remotos.\n\nEn primer lugar, ¿cómo quieres gestionar los datos obtenidos de este origen remoto?\n\n- **${NEWER_WINS}**: compara la fecha de modificación de los archivos y usa la más reciente.\n  Si has estado usando Self-hosted LiveSync y has hecho cambios en varios dispositivos, esta opción puede ser adecuada, ya que intenta combinar los cambios según la fecha de modificación.\n- **${REMOTE_WINS}**: los datos remotos son la fuente de la verdad.\n  Si eres nuevo en Self-hosted LiveSync, esta opción puede ser la más fácil de entender para empezar.\n  Sobrescribirá todos tus archivos locales con los datos remotos, así que asegúrate de tener una copia de seguridad si tienes datos importantes en tu vault.\n- **${DETAILED}**: abre el asistente de configuración detallado.\n  Si quieres tener más control sobre el proceso de sincronización, o revisar los cambios antes de aplicarlos, elige esta opción para usar el flujo detallado.",
+            zh: "即将获取远程数据。\n\n首先，应如何处理从此远程来源获取的数据？\n\n- **${NEWER_WINS}**：比较文件的修改时间，并采用较新的那一个。\n  如果你一直在使用 Self-hosted LiveSync，并且在多台设备上做过更改，此选项可能适合你，因为它会尝试根据修改时间合并更改。\n- **${REMOTE_WINS}**：以远程数据为准。\n  如果你是 Self-hosted LiveSync 的新用户，此选项可能最容易理解，也最容易上手。\n  它会用远程数据覆盖你所有的本地文件，因此如果库中有重要数据，请务必先备份。\n- **${DETAILED}**：打开详细设置向导。\n  如果你希望更好地控制同步过程，或希望在应用前检查更改，可以选择此选项使用详细流程。",
         },
     'We can not use "/" to the device name': {
         def: 'We can not use "/" to the device name',
@@ -13789,6 +14128,11 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "当您在编辑器中保存文件时,自动开始同步",
         "zh-tw": "在編輯器中儲存檔案時，自動開始同步",
     },
+    "While enabled, it causes very performance impact but debugging replication testing and other features will be enabled. Please disable this if you have not read the source code. Requires restart of Obsidian. Sometimes there is no implementation.":
+        {
+            def: "While enabled, it causes very performance impact but debugging replication testing and other features will be enabled. Please disable this if you have not read the source code. Requires restart of Obsidian. Sometimes there is no implementation.",
+            zh: "启用后会严重影响性能，但会开启复制调试测试等功能。如果你没有阅读过源代码，请关闭此项。需要重启 Obsidian。部分功能可能尚未实现。",
+        },
     "Write credentials in the file": {
         def: "Write credentials in the file",
         es: "Escribir credenciales en archivo",
@@ -13829,6 +14173,10 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "xxhash64（最快）",
         "zh-tw": "xxhash64（最快）",
     },
+    "xxhash64 is the current default.": {
+        def: "xxhash64 is the current default.",
+        zh: "xxhash64 是当前的默认值。",
+    },
     "Yes, I want to add this device to my existing synchronisation": {
         def: "Yes, I want to add this device to my existing synchronisation",
         es: "Sí, quiero añadir este dispositivo a mi sincronización existente",
@@ -13864,6 +14212,11 @@ export const allMessages: Readonly<Record<string, Readonly<Record<string, string
         zh: "你可以在 Obsidian 插件设置中配置。",
         "zh-tw": "你可以在 Obsidian 外掛設定中進行設定。",
     },
+    "You can enable this setting to process the files with size mismatches, these files can be created by some APIs or integrations.":
+        {
+            def: "You can enable this setting to process the files with size mismatches, these files can be created by some APIs or integrations.",
+            zh: "启用此设置后可以处理大小不匹配的文件，这些文件可能由某些 API 或集成创建。",
+        },
     "You should create a new synchronisation destination and rebuild your data there.": {
         def: "You should create a new synchronisation destination and rebuild your data there.",
         es: "Deberías crear un nuevo destino de sincronización y reconstruir allí tus datos.",
diff --git a/src/common/messagesJson/en.json b/src/common/messagesJson/en.json
index 58a944b0..c072bc3f 100644
--- a/src/common/messagesJson/en.json
+++ b/src/common/messagesJson/en.json
@@ -44,6 +44,7 @@
     "Action": "Action",
     "Activate": "Activate",
     "Active Remote Configuration": "Active Remote Configuration",
+    "Active Remote Type": "Active Remote Type",
     "Add default patterns": "Add default patterns",
     "Add new connection": "Add new connection",
     "AddOn Module (ConfigSync) has not been loaded. This is very unexpected situation. Please report this issue.": "AddOn Module (ConfigSync) has not been loaded. This is very unexpected situation. Please report this issue.",
@@ -58,11 +59,15 @@
     "All the same or non-existent": "All the same or non-existent",
     "Allow in session": "Allow in session",
     "Allow permanently": "Allow permanently",
+    "Allow sleep during synchronisation": "Allow sleep during synchronisation",
+    "Allow sleep during synchronisation on the desktop": "Allow sleep during synchronisation on the desktop",
+    "Allow the operating system to sleep while finite synchronisation operations are in progress.": "Allow the operating system to sleep while finite synchronisation operations are in progress.",
     "Also, please note that if you are using Peer-to-Peer synchronization, this configuration will be used when you switch to other methods and connect to a remote server in the future.": "Also, please note that if you are using Peer-to-Peer synchronization, this configuration will be used when you switch to other methods and connect to a remote server in the future.",
     "Always prompt merge conflicts": "Always prompt merge conflicts",
     "Analyse": "Analyse",
     "Analyse database usage": "Analyse database usage",
     "Analyse database usage and generate a TSV report for diagnosis yourself. You can paste the generated report with any spreadsheet you like.": "Analyse database usage and generate a TSV report for diagnosis yourself. You can paste the generated report with any spreadsheet you like.",
+    "Application ID": "Application ID",
     "Apply All Selected": "Apply All Selected",
     "Apply Latest Change if Conflicting": "Apply Latest Change if Conflicting",
     "Apply preset configuration": "Apply preset configuration",
@@ -70,7 +75,11 @@
     "Ask a passphrase at every launch": "Ask a passphrase at every launch",
     "Auto Connect": "Auto Connect",
     "Auto Start P2P Connection": "Auto Start P2P Connection",
+    "Auto-accept compatible tweak mismatches": "Auto-accept compatible tweak mismatches",
     "Automatic": "Automatic",
+    "Automatically accepts mismatches that are compatible but potentially lossy by comparing tweak modification times.": "Automatically accepts mismatches that are compatible but potentially lossy by comparing tweak modification times.",
+    "Automatically broadcast changes to connected peers": "Automatically broadcast changes to connected peers",
+    "Automatically start P2P connection on launch": "Automatically start P2P connection on launch",
     "Automatically Sync all files when opening Obsidian.": "Automatically Sync all files when opening Obsidian.",
     "Available Peers": "Available Peers",
     "Back": "Back",
@@ -93,6 +102,8 @@
     "Check for documents that have not been converted to path-obfuscated IDs and convert them if necessary.": "Check for documents that have not been converted to path-obfuscated IDs and convert them if necessary.",
     "Check server requirements": "Check server requirements",
     "Checking connection... Please wait.": "Checking connection... Please wait.",
+    "Chunk revisions are always derived from their content. This stored key is retained only for compatibility.": "Chunk revisions are always derived from their content. This stored key is retained only for compatibility.",
+    "Chunk Splitter": "Chunk Splitter",
     "Chunks": "Chunks",
     "Close": "Close",
     "Close & Disconnect": "Close & Disconnect",
@@ -131,6 +142,7 @@
     "Connection Method": "Connection Method",
     "Connection Settings": "Connection Settings",
     "Connection:": "Connection:",
+    "Content-derived chunk revisions (obsolete setting)": "Content-derived chunk revisions (obsolete setting)",
     "Continue anyway": "Continue anyway",
     "Continue to CouchDB setup": "Continue to CouchDB setup",
     "Continue to Peer-to-Peer only setup": "Continue to Peer-to-Peer only setup",
@@ -145,6 +157,8 @@
     "Cross-platform": "Cross-platform",
     "Current adapter: {adapter}": "Current adapter: {adapter}",
     "Custom Headers": "Custom Headers",
+    "Custom headers for requesting the bucket. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": "Custom headers for requesting the bucket. e.g. `x-custom-header1: value1\n x-custom-header2: value2`",
+    "Custom headers for requesting the CouchDB. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": "Custom headers for requesting the CouchDB. e.g. `x-custom-header1: value1\n x-custom-header2: value2`",
     "Customization Sync": "Customization Sync",
     "Customization Sync (Beta3)": "Customization Sync (Beta3)",
     "Data Compression": "Data Compression",
@@ -176,6 +190,8 @@
     "Deny permanently": "Deny permanently",
     "Deselect all": "Deselect all",
     "desktop": "desktop",
+    "Desktop only; uses more battery and network.": "Desktop only; uses more battery and network.",
+    "Desktop only. Allow sleep on this device even when the general option is disabled.": "Desktop only. Allow sleep on this device even when the general option is disabled.",
     "Detected Peers": "Detected Peers",
     "Developer": "Developer",
     "Device": "Device",
@@ -228,22 +244,33 @@
     "Edge case addressing (Behaviour)": "Edge case addressing (Behaviour)",
     "Edge case addressing (Database)": "Edge case addressing (Database)",
     "Edge case addressing (Processing)": "Edge case addressing (Processing)",
+    "Effectively a directory. Should end with `/`. e.g., `vault-name/`.": "Effectively a directory. Should end with `/`. e.g., `vault-name/`.",
     "Emergency restart": "Emergency restart",
     "Enable advanced features": "Enable advanced features",
+    "Enable advanced mode": "Enable advanced mode",
     "Enable customization sync": "Enable customization sync",
+    "Enable Developers' Debug Tools (If available).": "Enable Developers' Debug Tools (If available).",
     "Enable Developers' Debug Tools.": "Enable Developers' Debug Tools.",
     "Enable edge case treatment features": "Enable edge case treatment features",
+    "Enable forcePathStyle": "Enable forcePathStyle",
     "Enable P2P Replicator": "Enable P2P Replicator",
+    "Enable P2P Synchronization": "Enable P2P Synchronization",
+    "Enable per-file customization sync": "Enable per-file customization sync",
+    "Enable power user mode": "Enable power user mode",
     "Enable poweruser features": "Enable poweruser features",
     "Enable this if your Object Storage doesn't support CORS": "Enable this if your Object Storage doesn't support CORS",
     "Enable this option to automatically apply the most recent change to documents even when it conflicts": "Enable this option to automatically apply the most recent change to documents even when it conflicts",
     "Enabled": "Enabled",
     "Enabling end-to-end encryption ensures that your data is encrypted on your device before being sent to the remote server. This means that even if someone gains access to the server, they won't be able to read your data without the passphrase. Make sure to remember your passphrase, as it will be required to decrypt your data on other devices.": "Enabling end-to-end encryption ensures that your data is encrypted on your device before being sent to the remote server. This means that even if someone gains access to the server, they won't be able to read your data without the passphrase. Make sure to remember your passphrase, as it will be required to decrypt your data on other devices.",
     "Encrypt contents on the remote database. If you use the plugin's synchronization feature, enabling this is recommended.": "Encrypt contents on the remote database. If you use the plugin's synchronization feature, enabling this is recommended.",
+    "Encrypt file properties (paths, times, sizes, and Chunk references) used by Hidden File Sync and Customisation Sync. This affects future writes; manually rebuild the remote database to protect existing properties. Requires E2EE V2, Property Encryption, and compatible clients on every device.": "Encrypt file properties (paths, times, sizes, and Chunk references) used by Hidden File Sync and Customisation Sync. This affects future writes; manually rebuild the remote database to protect existing properties. Requires E2EE V2, Property Encryption, and compatible clients on every device.",
+    "Encrypt internal file Properties": "Encrypt internal file Properties",
     "Encrypting sensitive configuration items": "Encrypting sensitive configuration items",
     "Encryption Algorithm": "Encryption Algorithm",
+    "Encryption passphrase. If changed, you should overwrite the server's database with the new (encrypted) files.": "Encryption passphrase. If changed, you should overwrite the server's database with the new (encrypted) files.",
     "Encryption phassphrase. If changed, you should overwrite the server's database with the new (encrypted) files.": "Encryption phassphrase. If changed, you should overwrite the server's database with the new (encrypted) files.",
     "End-to-End Encryption": "End-to-End Encryption",
+    "End-to-End Encryption Algorithm": "End-to-End Encryption Algorithm",
     "Endpoint URL": "Endpoint URL",
     "Enhance chunk size": "Enhance chunk size",
     "Enter a complete HTTP or HTTPS URL.": "Enter a complete HTTP or HTTPS URL.",
@@ -285,9 +312,11 @@
     "FETCHING": "FETCHING",
     "Fetching status...": "Fetching status...",
     "File integrity": "File integrity",
+    "File prefix on the bucket": "File prefix on the bucket",
     "File to resolve conflict": "File to resolve conflict",
     "File to view History": "File to view History",
     "Filename": "Filename",
+    "Files with modification times greater than this value (in seconds since the Unix epoch) will not have their events reflected. Set to 0 to disable this limit.": "Files with modification times greater than this value (in seconds since the Unix epoch) will not have their events reflected. Set to 0 to disable this limit.",
     "Final Confirmation: Overwrite Server Data with This Device's Files": "Final Confirmation: Overwrite Server Data with This Device's Files",
     "Finalise the process and resume normal operation": "Finalise the process and resume normal operation",
     "First, please select the option that best describes your current situation.": "First, please select the option that best describes your current situation.",
@@ -340,14 +369,22 @@
     "If \"Auto Start P2P Connection\" is enabled, the P2P connection will be started automatically when the plug-in launches.": "If \"Auto Start P2P Connection\" is enabled, the P2P connection will be started automatically when the plug-in launches.",
     "If disabled(toggled), chunks will be split on the UI thread (Previous behaviour).": "If disabled(toggled), chunks will be split on the UI thread (Previous behaviour).",
     "If enabled per-filed efficient customization sync will be used. We need a small migration when enabling this. And all devices should be updated to v0.23.18. Once we enabled this, we lost a compatibility with old versions.": "If enabled per-filed efficient customization sync will be used. We need a small migration when enabling this. And all devices should be updated to v0.23.18. Once we enabled this, we lost a compatibility with old versions.",
+    "If enabled, changes will be automatically broadcasted to all connected peers. Notified peers will start fetching the changes.": "If enabled, changes will be automatically broadcasted to all connected peers. Notified peers will start fetching the changes.",
     "If enabled, chunks will be split into no more than 100 items. However, dedupe is slightly weaker.": "If enabled, chunks will be split into no more than 100 items. However, dedupe is slightly weaker.",
+    "If enabled, efficient per-file customization sync will be used. A minor migration is required when enabling this feature, and all devices must be updated to v0.23.18. Enabling this feature will result in losing compatibility with older versions.": "If enabled, efficient per-file customization sync will be used. A minor migration is required when enabling this feature, and all devices must be updated to v0.23.18. Enabling this feature will result in losing compatibility with older versions.",
     "If enabled, newly created chunks are temporarily kept within the document, and graduated to become independent chunks once stabilised.": "If enabled, newly created chunks are temporarily kept within the document, and graduated to become independent chunks once stabilised.",
     "If enabled, the ⛔ icon will be shown inside the status instead of the file warnings banner. No details will be shown.": "If enabled, the ⛔ icon will be shown inside the status instead of the file warnings banner. No details will be shown.",
+    "If enabled, the file properties will be encrypted in the remote database. This is useful for protecting sensitive information in file paths, sizes, and IDs of its chunks. If you are using V1 E2EE, this only obfuscates the file path.": "If enabled, the file properties will be encrypted in the remote database. This is useful for protecting sensitive information in file paths, sizes, and IDs of its chunks. If you are using V1 E2EE, this only obfuscates the file path.",
     "If enabled, the file under 1kb will be processed in the UI thread.": "If enabled, the file under 1kb will be processed in the UI thread.",
+    "If enabled, the forcePathStyle option will be used for bucket operations.": "If enabled, the forcePathStyle option will be used for bucket operations.",
     "If enabled, the notification of hidden files change will be suppressed.": "If enabled, the notification of hidden files change will be suppressed.",
+    "If enabled, the P2P connection will be automatically started when the application launches.": "If enabled, the P2P connection will be automatically started when the application launches.",
+    "If enabled, the plugin will not attempt to connect to the remote database even if the chunk was not found locally.": "If enabled, the plugin will not attempt to connect to the remote database even if the chunk was not found locally.",
+    "If enabled, the request API will be used to avoid `inevitable` CORS problems. This is a workaround and may not work in all cases. PLEASE READ THE DOCUMENTATION BEFORE USING THIS OPTION. This is a less-secure option.": "If enabled, the request API will be used to avoid `inevitable` CORS problems. This is a workaround and may not work in all cases. PLEASE READ THE DOCUMENTATION BEFORE USING THIS OPTION. This is a less-secure option.",
     "If this enabled, all chunks will be stored with the revision made from its content. (Previous behaviour)": "If this enabled, all chunks will be stored with the revision made from its content. (Previous behaviour)",
     "If this enabled, All files are handled as case-Sensitive (Previous behaviour).": "If this enabled, All files are handled as case-Sensitive (Previous behaviour).",
     "If this enabled, chunks will be split into semantically meaningful segments. Not all platforms support this feature.": "If this enabled, chunks will be split into semantically meaningful segments. Not all platforms support this feature.",
+    "If this enabled, JWT will be used for authentication.": "If this enabled, JWT will be used for authentication.",
     "If this is set, changes to local files which are matched by the ignore files will be skipped. Remote changes are determined using local ignore files.": "If this is set, changes to local files which are matched by the ignore files will be skipped. Remote changes are determined using local ignore files.",
     "If this option is enabled, PouchDB will hold the connection open for 60 seconds, and if no change arrives in that time, close and reopen the socket, instead of holding it open indefinitely. Useful when a proxy limits request duration but can increase resource usage.": "If this option is enabled, PouchDB will hold the connection open for 60 seconds, and if no change arrives in that time, close and reopen the socket, instead of holding it open indefinitely. Useful when a proxy limits request duration but can increase resource usage.",
     "If you cannot avoid CORS issues, you might want to try this option. It uses Obsidian's internal API to communicate with the CouchDB server. Not compliant with web standards, but works. Note that this might break in future Obsidian versions.": "If you cannot avoid CORS issues, you might want to try this option. It uses Obsidian's internal API to communicate with the CouchDB server. Not compliant with web standards, but works. Note that this might break in future Obsidian versions.",
@@ -371,6 +408,7 @@
     "Initialise all journal history, On the next sync, every item will be received and sent.": "Initialise all journal history, On the next sync, every item will be received and sent.",
     "Initialise journal received history. On the next sync, every item except this device sent will be downloaded again.": "Initialise journal received history. On the next sync, every item except this device sent will be downloaded again.",
     "Initialise journal sent history. On the next sync, every item except this device received will be sent again.": "Initialise journal sent history. On the next sync, every item except this device received will be sent again.",
+    "Internal timestamp for resolving compatible tweak mismatches.": "Internal timestamp for resolving compatible tweak mismatches.",
     "Interval (sec)": "Interval (sec)",
     "INVERTED": "INVERTED",
     "Issue detection log:": "Issue detection log:",
@@ -392,6 +430,9 @@
     "Keep empty folder": "Keep empty folder",
     "Keep local files even if deleted on remote": "Keep local files even if deleted on remote",
     "Keep local files even if not on remote": "Keep local files even if not on remote",
+    "Keep replication active in the background": "Keep replication active in the background",
+    "Key ID": "Key ID",
+    "Keypair or pre-shared key": "Keypair or pre-shared key",
     "lang_def": "Default",
     "lang-de": "Deutsche",
     "lang-def": "%{lang_def}",
@@ -403,6 +444,7 @@
     "lang-ru": "Русский",
     "lang-zh": "简体中文",
     "lang-zh-tw": "繁體中文",
+    "Last tweak modified timestamp": "Last tweak modified timestamp",
     "Later": "Later",
     "Limit: {datetime} ({timestamp})": "Limit: {datetime} ({timestamp})",
     "live": "live",
@@ -443,19 +485,24 @@
     "logPane.pause": "Pause",
     "logPane.title": "Self-hosted LiveSync Log",
     "logPane.wrap": "Wrap",
+    "Longest chunk line threshold value (Not Configurable from the UI Now).": "Longest chunk line threshold value (Not Configurable from the UI Now).",
     "Lower (${local} < ${remote})": "Lower (${local} < ${remote})",
     "Maintenance Commands": "Maintenance Commands",
     "Maintenance mode": "Maintenance mode",
     "Maximum delay for batch database updating": "Maximum delay for batch database updating",
+    "Maximum file modification time for reflected file events": "Maximum file modification time for reflected file events",
     "Maximum file size": "Maximum file size",
     "Maximum Incubating Chunk Size": "Maximum Incubating Chunk Size",
     "Maximum Incubating Chunks": "Maximum Incubating Chunks",
     "Maximum Incubation Period": "Maximum Incubation Period",
+    "Maximum request size for manually resending chunks": "Maximum request size for manually resending chunks",
     "MB (0 to disable).": "MB (0 to disable).",
+    "MB per request": "MB per request",
     "Memory cache": "Memory cache",
     "Memory cache size (by total characters)": "Memory cache size (by total characters)",
     "Memory cache size (by total items)": "Memory cache size (by total items)",
     "Merge": "Merge",
+    "Minimum Chunk Size (Not Configurable from the UI Now).": "Minimum Chunk Size (Not Configurable from the UI Now).",
     "Minimum delay for batch database updating": "Minimum delay for batch database updating",
     "Minimum interval for syncing": "Minimum interval for syncing",
     "Mixed": "Mixed",
@@ -533,6 +580,7 @@
     "More actions": "More actions",
     "Mostly Complete: Decision Required": "Mostly Complete: Decision Required",
     "Move remotely deleted files to the trash, instead of deleting.": "Move remotely deleted files to the trash, instead of deleting.",
+    "Move remotely deleted files to the trash, instead of deleting. (This setting is ineffective from Obsidian v1.7.2 onwards, as deletion always respects your Obsidian preferences.)": "Move remotely deleted files to the trash, instead of deleting. (This setting is ineffective from Obsidian v1.7.2 onwards, as deletion always respects your Obsidian preferences.)",
     "My remote server is already set up. I want to join this device.": "My remote server is already set up. I want to join this device.",
     "Name": "Name",
     "Network warning style": "Network warning style",
@@ -560,6 +608,7 @@
     "Notify customized": "Notify customized",
     "Notify when other device has newly customized.": "Notify when other device has newly customized.",
     "Notify when the estimated remote storage size exceeds on start up": "Notify when the estimated remote storage size exceeds on start up",
+    "Now we can choose how to split the chunks; V3 is the most efficient. If you have troubled, please make this Default or Legacy.": "Now we can choose how to split the chunks; V3 is the most efficient. If you have troubled, please make this Default or Legacy.",
     "Number of batches to process at a time. Defaults to 40. Minimum is 2. This along with batch size controls how many docs are kept in memory at a time.": "Number of batches to process at a time. Defaults to 40. Minimum is 2. This along with batch size controls how many docs are kept in memory at a time.",
     "Number of changes to sync at a time. Defaults to 50. Minimum is 2.": "Number of changes to sync at a time. Defaults to 50. Minimum is 2.",
     "Obfuscate Properties": "Obfuscate Properties",
@@ -830,6 +879,7 @@
     "Please set device name to identify this device. This name should be unique among your devices. While not configured, we cannot enable this feature.": "Please set device name to identify this device. This name should be unique among your devices. While not configured, we cannot enable this feature.",
     "Please set this device name": "Please set this device name",
     "Please understand that this is intended behaviour.": "Please understand that this is intended behaviour.",
+    "Please use V2, V1 is deprecated and will be removed in the future, It was not a very appropriate algorithm. Only for compatibility V1 is kept.": "Please use V2, V1 is deprecated and will be removed in the future, It was not a very appropriate algorithm. Only for compatibility V1 is kept.",
     "Plug-in version": "Plug-in version",
     "Plugins": "Plugins",
     "Prepare the 'report' to create an issue": "Prepare the 'report' to create an issue",
@@ -841,6 +891,7 @@
     "Proceed with Setup URI": "Proceed with Setup URI",
     "Proceeding with Garbage Collection, ignoring missing nodes.": "Proceeding with Garbage Collection, ignoring missing nodes.",
     "Proceeding with Garbage Collection.": "Proceeding with Garbage Collection.",
+    "Process files even if seems to be corrupted": "Process files even if seems to be corrupted",
     "Process small files in the foreground": "Process small files in the foreground",
     "Progress": "Progress",
     "Property Encryption": "Property Encryption",
@@ -925,6 +976,7 @@
     "Revoke": "Revoke",
     "Room ID": "Room ID",
     "Room ID suffix:": "Room ID suffix:",
+    "Rotation Duration": "Rotation Duration",
     "Run Doctor": "Run Doctor",
     "S3/MinIO/R2 Configuration": "S3/MinIO/R2 Configuration",
     "S3/MinIO/R2 Object Storage": "S3/MinIO/R2 Object Storage",
@@ -974,6 +1026,13 @@
     "Setting.TroubleShooting.Doctor.Desc": "Detects non optimal settings. (Same as during migration)",
     "Setting.TroubleShooting.ScanBrokenFiles": "Scan for broken files",
     "Setting.TroubleShooting.ScanBrokenFiles.Desc": "Scans for files that are not stored correctly in the database.",
+    "SettingService.ConfigurationCouldNotBeDecrypted": "Existing configuration could not be decrypted. The configuration key was not changed.",
+    "SettingService.ConfigurationEncryptionSaveFailed": "Configuration encryption could not be saved. Verify the saved settings and device key before retrying.",
+    "SettingService.ConfigurationPassphraseCancelled": "Configuration passphrase entry was cancelled or unavailable. Start-up was stopped; saved settings were retained.",
+    "SettingService.ConfigurationPassphraseDeviceLocalDescription": "This passphrase stays on this device. When another device needs to decrypt protected settings without a saved key, enter the same passphrase at start-up.",
+    "SettingService.ConfigurationPassphraseRetryTitle": "Configuration could not be decrypted. Enter the configuration passphrase again.",
+    "SettingService.ConfigurationPassphraseRollbackFailed": "The configuration passphrase could not be restored after a write failure. Verify the saved settings and device key before retrying.",
+    "SettingService.ConfigurationPassphraseTitle": "Configuration passphrase",
     "SettingTab.Message.AskRebuild": "Your changes require fetching from the remote database. Do you want to proceed?",
     "Setup Complete: Preparing to Fetch Synchronisation Data": "Setup Complete: Preparing to Fetch Synchronisation Data",
     "Setup Complete: Preparing to Initialise Server": "Setup Complete: Preparing to Initialise Server",
@@ -1050,6 +1109,7 @@
     "Show status on the status bar": "Show status on the status bar",
     "Show verbose log. Please enable if you report an issue.": "Show verbose log. Please enable if you report an issue.",
     "Signaling Server Connection": "Signaling Server Connection",
+    "Signalling Relays": "Signalling Relays",
     "Signalling Status": "Signalling Status",
     "Since you have chosen to overwrite all local files with remote data, **how would you like to handle local files that are not present in the remote database?**\n\n- **${DELETE_ALL}**: Local-only files and remote-deleted files will be removed.\n  This option will make your local vault exactly the same as the remote database, but please make sure you have a backup if there is any important data in your vault.\n- **${DELETE_NONE}**: All existing local files will be preserved.\n  This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.": "Since you have chosen to overwrite all local files with remote data, **how would you like to handle local files that are not present in the remote database?**\n\n- **${DELETE_ALL}**: Local-only files and remote-deleted files will be removed.\n  This option will make your local vault exactly the same as the remote database, but please make sure you have a backup if there is any important data in your vault.\n- **${DELETE_NONE}**: All existing local files will be preserved.\n  This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.",
     "Skip and close": "Skip and close",
@@ -1068,6 +1128,7 @@
     "Stop watching for file changes.": "Stop watching for file changes.",
     "Storage -> Database": "Storage -> Database",
     "Strongly Recommended": "Strongly Recommended",
+    "Subject (whoami)": "Subject (whoami)",
     "Suppress notification of hidden files change": "Suppress notification of hidden files change",
     "Suspend database reflecting": "Suspend database reflecting",
     "Suspend file watching": "Suspend file watching",
@@ -1091,26 +1152,38 @@
     "Test connection and save": "Test connection and save",
     "Test Settings and Continue": "Test Settings and Continue",
     "Testing only - Resolve file conflicts by syncing newer copies of the file, this can overwrite modified files. Be Warned.": "Testing only - Resolve file conflicts by syncing newer copies of the file, this can overwrite modified files. Be Warned.",
+    "The algorithm used for JWT authentication.": "The algorithm used for JWT authentication.",
+    "The Application ID for P2P connection. This should be same among your devices. Default is 'self-hosted-livesync' and could not be modified from the UI.": "The Application ID for P2P connection. This should be same among your devices. Default is 'self-hosted-livesync' and could not be modified from the UI.",
     "The connection test cannot add a signalling relay while P2P is active. Use the active relay settings, or disconnect P2P before testing.": "The connection test cannot add a signalling relay while P2P is active. Use the active relay settings, or disconnect P2P before testing.",
     "The connection to the server has been configured successfully. As the next step,": "The connection to the server has been configured successfully. As the next step,",
+    "The credential/password for the TURN servers.": "The credential/password for the TURN servers.",
     "The delay for consecutive on-demand fetches": "The delay for consecutive on-demand fetches",
     "The files in this Vault are almost identical to the server's.": "The files in this Vault are almost identical to the server's.",
     "The following accepted nodes are missing its node information:\n- ${missingNodes}\n\nThis indicates that they have not been connected for some time or have been left on an older version.\nIt is preferable to update all devices if possible. If you have any devices that are no longer in use, you can clear all accepted nodes by locking the remote once.": "The following accepted nodes are missing its node information:\n- ${missingNodes}\n\nThis indicates that they have not been connected for some time or have been left on an older version.\nIt is preferable to update all devices if possible. If you have any devices that are no longer in use, you can clear all accepted nodes by locking the remote once.",
     "The Group ID and passphrase are used to identify your group of devices. Make sure to use the same Group ID and passphrase on all devices you want to synchronise.": "The Group ID and passphrase are used to identify your group of devices. Make sure to use the same Group ID and passphrase on all devices you want to synchronise.",
     "The Hash algorithm for chunk IDs": "The Hash algorithm for chunk IDs",
     "The IndexedDB adapter often offers superior performance in certain scenarios, but it has been found to cause memory leaks when used with LiveSync mode. When using LiveSync mode, please use IDB adapter instead.": "The IndexedDB adapter often offers superior performance in certain scenarios, but it has been found to cause memory leaks when used with LiveSync mode. When using LiveSync mode, please use IDB adapter instead.",
+    "The key (PSK in HSxxx in base64, or private key in ESxxx in PEM) used for JWT authentication.": "The key (PSK in HSxxx in base64, or private key in ESxxx in PEM) used for JWT authentication.",
+    "The key ID. this should be matched with CouchDB->jwt_keys->ALG:_`kid`.": "The key ID. this should be matched with CouchDB->jwt_keys->ALG:_`kid`.",
     "the latest synchronisation data will be downloaded from the server to this device.": "the latest synchronisation data will be downloaded from the server to this device.",
     "the local database, that is to say the synchronisation information, must be reconstituted.": "the local database, that is to say the synchronisation information, must be reconstituted.",
     "The maximum duration for which chunks can be incubated within the document. Chunks exceeding this period will graduate to independent chunks.": "The maximum duration for which chunks can be incubated within the document. Chunks exceeding this period will graduate to independent chunks.",
     "The maximum number of chunks that can be incubated within the document. Chunks exceeding this number will immediately graduate to independent chunks.": "The maximum number of chunks that can be incubated within the document. Chunks exceeding this number will immediately graduate to independent chunks.",
     "The maximum total size of chunks that can be incubated within the document. Chunks exceeding this size will immediately graduate to independent chunks.": "The maximum total size of chunks that can be incubated within the document. Chunks exceeding this size will immediately graduate to independent chunks.",
     "The minimum interval for automatic synchronisation on event.": "The minimum interval for automatic synchronisation on event.",
+    "The Nostr relay servers to establish connections for P2P connections. Multiple servers can be separated by commas.": "The Nostr relay servers to establish connections for P2P connections. Multiple servers can be separated by commas.",
+    "The Passphrase for P2P connection. This should be same among your devices.": "The Passphrase for P2P connection. This should be same among your devices.",
     "The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.": "The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.",
     "The remote is already set up, and the configuration is compatible (or got compatible by this operation).": "The remote is already set up, and the configuration is compatible (or got compatible by this operation).",
+    "The Room ID for P2P connection. This should be same among your devices.": "The Room ID for P2P connection. This should be same among your devices.",
+    "The Rotation duration of token in minutes. Each generated tokens will be valid only within this duration.": "The Rotation duration of token in minutes. Each generated tokens will be valid only within this duration.",
     "The Setup-URI does not appear to be valid. Please check that you have copied it correctly.": "The Setup-URI does not appear to be valid. Please check that you have copied it correctly.",
     "The Setup-URI is valid and ready to use.": "The Setup-URI is valid and ready to use.",
     "the single, authoritative master copy": "the single, authoritative master copy",
+    "The subject for JWT authentication. Mostly username.": "The subject for JWT authentication. Mostly username.",
     "the synchronisation data on the server will be built based on the current data on this device.": "the synchronisation data on the server will be built based on the current data on this device.",
+    "The TURN servers to use for P2P connections. Multiple servers can be separated by commas.": "The TURN servers to use for P2P connections. Multiple servers can be separated by commas.",
+    "The username for the TURN servers.": "The username for the TURN servers.",
     "Themes": "Themes",
     "There is a way to resolve this on other devices.": "There is a way to resolve this on other devices.",
     "There may be differences between the files in this Vault and the server.": "There may be differences between the files in this Vault and the server.",
@@ -1137,6 +1210,7 @@
     "TURN Credential": "TURN Credential",
     "TURN server settings are only necessary if you are behind a strict NAT or firewall that prevents direct P2P connections. In most cases, you can leave these fields blank.": "TURN server settings are only necessary if you are behind a strict NAT or firewall that prevents direct P2P connections. In most cases, you can leave these fields blank.",
     "TURN Server URLs (comma-separated)": "TURN Server URLs (comma-separated)",
+    "TURN Servers": "TURN Servers",
     "TURN Username": "TURN Username",
     "TweakMismatchResolve.Action.DisableAutoAcceptCompatible": "Disable auto-accept",
     "TweakMismatchResolve.Action.Dismiss": "Dismiss",
@@ -1461,8 +1535,11 @@
     "Use internal API": "Use internal API",
     "Use Internal API": "Use Internal API",
     "Use JWT Authentication": "Use JWT Authentication",
+    "Use JWT instead of Basic Authentication": "Use JWT instead of Basic Authentication",
+    "Use Only Local Chunks": "Use Only Local Chunks",
     "Use Path-Style Access": "Use Path-Style Access",
     "Use Random Number": "Use Random Number",
+    "Use Request API to avoid `inevitable` CORS problem": "Use Request API to avoid `inevitable` CORS problem",
     "Use Segmented-splitter": "Use Segmented-splitter",
     "Use splitting-limit-capped chunk splitter": "Use splitting-limit-capped chunk splitter",
     "Use the detailed flow": "Use the detailed flow",
@@ -1486,14 +1563,17 @@
     "We will now proceed with the server configuration.": "We will now proceed with the server configuration.",
     "Welcome to Self-hosted LiveSync": "Welcome to Self-hosted LiveSync",
     "When you save a file in the editor, start a sync automatically": "When you save a file in the editor, start a sync automatically",
+    "While enabled, it causes very performance impact but debugging replication testing and other features will be enabled. Please disable this if you have not read the source code. Requires restart of Obsidian. Sometimes there is no implementation.": "While enabled, it causes very performance impact but debugging replication testing and other features will be enabled. Please disable this if you have not read the source code. Requires restart of Obsidian. Sometimes there is no implementation.",
     "Write credentials in the file": "Write credentials in the file",
     "Write logs into the file": "Write logs into the file",
     "xxhash32 (Fast but less collision resistance)": "xxhash32 (Fast but less collision resistance)",
     "xxhash64 (Fastest)": "xxhash64 (Fastest)",
+    "xxhash64 is the current default.": "xxhash64 is the current default.",
     "Yes, I want to add this device to my existing synchronisation": "Yes, I want to add this device to my existing synchronisation",
     "Yes, I want to set up a new synchronisation": "Yes, I want to set up a new synchronisation",
     "You are adding this device to an existing synchronisation setup.": "You are adding this device to an existing synchronisation setup.",
     "You can configure in the Obsidian Plugin Settings.": "You can configure in the Obsidian Plugin Settings.",
+    "You can enable this setting to process the files with size mismatches, these files can be created by some APIs or integrations.": "You can enable this setting to process the files with size mismatches, these files can be created by some APIs or integrations.",
     "You should create a new synchronisation destination and rebuild your data there.": "You should create a new synchronisation destination and rebuild your data there.",
     "You should perform this operation only in exceptional circumstances, such as when the server data is completely corrupted, when changes on all other devices are no longer needed, or when the database size has become unusually large in comparison to the Vault size.": "You should perform this operation only in exceptional circumstances, such as when the server data is completely corrupted, when changes on all other devices are no longer needed, or when the database size has become unusually large in comparison to the Vault size.",
     "you wanted(Thank you)!": "you wanted(Thank you)!"
diff --git a/src/common/messagesJson/zh.json b/src/common/messagesJson/zh.json
index 8f7ceb5c..eb5c5b05 100644
--- a/src/common/messagesJson/zh.json
+++ b/src/common/messagesJson/zh.json
@@ -1,33 +1,88 @@
 {
+    ", please select the option that best describes the current state of your Vault. The application will then check your files in the most appropriate way based on your selection.": "，请选择最符合你库当前状态的选项。程序会根据你的选择，用最合适的方式检查你的文件。",
     "(Active)": "（已启用）",
     "(BETA) Always overwrite with a newer file": "始终使用更新的文件覆盖(测试版)",
     "(Beta) Use ignore files": "(测试版)使用忽略文件",
     "(Days passed, 0 to disable automatic-deletion)": "(已过天数,0为禁用自动删除)",
+    "(e.g., after editing many files whilst offline)": "（例如：离线期间编辑了大量文件之后）",
+    "(e.g., immediately after restoring on another computer, or having recovered from a backup)": "（例如：在另一台电脑上还原之后，或从备份恢复之后）",
+    "(e.g., setting up for the first time on a new smartphone, starting from a clean slate)": "（例如：在新手机上首次设置，从零开始）",
     "(ex. Read chunks online) If this option is enabled, LiveSync reads chunks online directly instead of replicating them locally. Increasing Custom chunk size is recommended.": "(例如,在线读取块)如果启用此选项,LiveSync 将直接在线读取块,而不是在本地复制块。建议增加自定义块大小",
     "(MB) If this is set, changes to local and remote files that are larger than this will be skipped. If the file becomes smaller again, a newer one will be used.": "(MB)如果设置了此项,大于此大小的本地和远程文件的更改将被跳过。如果文件再次变小,将使用更新的文件",
     "(Mega chars)": "(百万字符)",
+    "(Missing)": "（缺失）",
     "(Not recommended) If set, credentials will be stored in the file.": "(不建议)如果设置,凭据将存储在文件中",
     "(Obsolete) Use an old adapter for compatibility": "(已弃用)为兼容性使用旧适配器",
     "(RegExp) Empty to sync all files. Set filter as a regular expression to limit synchronising files.": "（正则表达式）留空表示同步所有文件。可设置正则表达式来限制需要同步的文件。",
     "(RegExp) If this is set, any changes to local and remote files that match this will be skipped.": "（正则表达式）如果已设置，则所有匹配此模式的本地和远端文件变更都会被跳过。",
     "(Select this if another device is already using LiveSync.) This option adds this device to that existing synchronisation setup.": "（如果你已经在另一台电脑或手机上使用同步，请选择此项。）此选项适合将当前设备加入现有 LiveSync 配置的用户。",
+    "(Select this if you already have another synchronising device.) This option adds this device to the same synchronisation.": "（如果你已有另一台正在同步的设备，请选择此项。）此选项会把本设备加入同一个同步。",
     "(Select this if you are configuring this device as the first synchronisation device.) This option is suitable if you are new to LiveSync and want to set it up from scratch.": "（如果你正在将此设备配置为第一台同步设备，请选择此项。）此选项适合初次使用 LiveSync，并希望从头开始配置的用户。",
+    "↑: Overwrite Remote": "↑：覆盖远端",
+    "↓: Overwrite Local": "↓：覆盖本地",
+    "⇅: Use newer": "⇅：使用较新版本",
+    "+1 week": "+1 周",
     "> [!INFO]- The connected devices have been detected as follows:\n${devices}": "> [!INFO]- 已检测到以下已连接设备：\n${devices}",
+    "⚠️ Important Notice": "⚠️ 重要提示",
+    "⚠️ Please Confirm the Following": "⚠️ 请确认以下内容",
+    "✔ SELECT": "✔ 选择",
+    "✔ SYNC": "✔ 同步",
+    "✔ WATCH": "✔ 监视",
+    "📡 Off": "📡 关闭",
+    "📡 On": "📡 开启",
+    "🔴 Disconnected": "🔴 已断开",
+    "🕵️ Diag": "🕵️ 诊断",
+    "🗑 Delete": "🗑 删除",
+    "🟢 Connected": "🟢 已连接",
+    "${count} issue(s) detected!": "检测到 ${count} 个问题！",
     "A Setup URI is a single string of text containing your server address and authentication details. Using a URI, if one was generated by your server installation script, provides a simple and secure configuration.": "Setup URI 是一段包含服务器地址与认证信息的文本。如果服务器安装脚本已经生成了 URI，使用它可以更简单且更安全地完成配置。",
+    "Accept": "接受",
+    "Accept in session": "本次会话内接受",
+    "ACCEPTED": "已接受",
+    "ACCEPTED (in session)": "已接受（本次会话）",
     "Access Key": "访问密钥",
+    "Access Key ID": "访问密钥 ID",
+    "Action": "操作",
     "Activate": "启用",
     "Active Remote Configuration": "生效中的远程配置",
+    "Active Remote Type": "当前使用的远程类型",
     "Add default patterns": "添加默认模式",
     "Add new connection": "新增连接",
+    "AddOn Module (ConfigSync) has not been loaded. This is very unexpected situation. Please report this issue.": "附加模块（ConfigSync）未能加载。这是非常意外的情况。请报告此问题。",
+    "AddOn Module (HiddenFileSync) has not been loaded. This is very unexpected situation. Please report this issue.": "附加模块（HiddenFileSync）未能加载。这是非常意外的情况。请报告此问题。",
+    "Advanced": "高级",
+    "Advanced Settings": "高级设置",
+    "After restarting, the data on this device will be uploaded to the server as the 'master copy'. Please be aware that any unintended data currently on the server will be completely overwritten.": "重启后，本设备上的数据将作为「主副本」上传到服务器。请注意，服务器上现有的任何非预期数据都会被完全覆盖。",
+    "After restarting, the database on this device will be rebuilt using data from the server. If there are any unsynchronised files in this vault, conflicts may occur with the server data.": "重启后，将用服务器上的数据重建本设备的数据库。如果本库中有未同步的文件，可能会与服务器数据产生冲突。",
+    "After that, synchronise to a brand new vault on each other device with the new remote one by one.": "之后，在其他设备上逐个用新的远端同步到一个全新的库。",
+    "All checks passed successfully!": "所有检查均已通过！",
     "All devices have the same progress value (${progress}). Your devices seem to be synchronised. And be able to proceed with Garbage Collection.": "所有设备的进度值均相同（${progress}）。看起来你的设备已经同步，可以继续执行垃圾回收。",
+    "All the same or non-existent": "全部相同或不存在",
+    "Allow in session": "本次会话内允许",
+    "Allow permanently": "永久允许",
+    "Allow sleep during synchronisation": "同步期间允许睡眠",
+    "Allow sleep during synchronisation on the desktop": "桌面端同步期间允许睡眠",
+    "Allow the operating system to sleep while finite synchronisation operations are in progress.": "在一次性同步操作进行期间，允许操作系统进入睡眠。",
+    "Also, please note that if you are using Peer-to-Peer synchronization, this configuration will be used when you switch to other methods and connect to a remote server in the future.": "另外请注意，如果你正在使用点对点同步，当你日后切换到其他方式并连接远端服务器时，将使用此配置。",
     "Always prompt merge conflicts": "始终提示合并冲突",
     "Analyse": "立即分析",
     "Analyse database usage": "分析数据库使用情况",
     "Analyse database usage and generate a TSV report for diagnosis yourself. You can paste the generated report with any spreadsheet you like.": "分析数据库使用情况并生成 TSV 报告以供您自行诊断。您可以将生成的报告粘贴到您喜欢的任何电子表格中。",
+    "Application ID": "应用 ID",
+    "Apply All Selected": "应用所有已选项",
     "Apply Latest Change if Conflicting": "如果冲突则应用最新更改",
     "Apply preset configuration": "应用预设配置",
+    "Apply the settings": "应用设置",
     "Ask a passphrase at every launch": "每次启动时询问密码短语",
+    "Auto Connect": "自动连接",
+    "Auto Start P2P Connection": "自动启动 P2P 连接",
+    "Auto-accept compatible tweak mismatches": "自动接受兼容的调整值不一致",
+    "Automatic": "自动",
+    "Automatically accepts mismatches that are compatible but potentially lossy by comparing tweak modification times.": "通过比较调整值的修改时间，自动接受兼容但可能有损的配置不一致。",
+    "Automatically broadcast changes to connected peers": "自动将更改广播给已连接的对等方",
+    "Automatically start P2P connection on launch": "启动时自动启动 P2P 连接",
     "Automatically Sync all files when opening Obsidian.": "打开 Obsidian 时自动同步所有文件",
+    "Available Peers": "可用的对等方",
     "Back": "返回",
     "Back to non-configured": "恢复为未配置状态",
     "Batch database update": "批量数据库更新",
@@ -35,19 +90,37 @@
     "Batch size": "批量大小",
     "Batch size of on-demand fetching": "按需获取的批量大小",
     "Before v0.17.16, we used an old adapter for the local database. Now the new adapter is preferred. However, it needs local database rebuilding. Please disable this toggle when you have enough time. If leave it enabled, also while fetching from the remote database, you will be asked to disable this.": "在 v0.17.16 之前,我们使用旧适配器作为本地数据库。现在首选新适配器。但是,它需要重建本地数据库。请在有足够时间时禁用此开关。如果保持启用状态,并且在从远程数据库获取时,系统将要求您禁用此开关。",
+    "Broadcasting?": "正在广播？",
     "Bucket Name": "存储桶名称",
+    "by resetting the remote, you will be informed on other devices.": "重置远端后，其他设备会收到通知。",
     "Cancel": "取消",
+    "Cancel all and reboot": "全部取消并重启",
     "Cancel Garbage Collection": "取消垃圾回收",
+    "Changing the encryption algorithm will prevent access to any data previously encrypted with a different algorithm. Ensure that all your devices are configured to use the same algorithm to maintain access to your data.": "更改加密算法将导致无法访问此前用其他算法加密的数据。请确保所有设备都配置为使用相同算法，以保持对数据的访问。",
+    "Changing this setting requires migrating existing data (a bit time may be taken) and restarting Obsidian. Please make sure to back up your data before proceeding.": "更改此设置需要迁移现有数据（可能需要一些时间）并重启 Obsidian。请务必在继续之前备份数据。",
     "Check": "立即检查",
     "Check and convert non-path-obfuscated files": "检查并转换未进行路径混淆的文件",
     "Check for documents that have not been converted to path-obfuscated IDs and convert them if necessary.": "检查尚未转换为路径混淆 ID 的文档，并在需要时将其转换。",
+    "Check server requirements": "检查服务器要求",
+    "Checking connection... Please wait.": "正在检查连接…请稍候。",
+    "Chunk revisions are always derived from their content. This stored key is retained only for compatibility.": "数据块修订版本始终由其内容推导得出。此已存储的设置项仅为兼容而保留。",
+    "Chunk Splitter": "数据块分割器",
+    "Chunks": "块",
+    "Close": "关闭",
+    "Close & Disconnect": "关闭并断开连接",
+    "Close this dialog": "关闭此对话框",
+    "Closed:": "已关闭：",
     "cmdConfigSync.showCustomizationSync": "显示自定义同步",
     "Comma separated `.gitignore, .dockerignore`": "用逗号分隔,例如 `.gitignore, .dockerignore`",
+    "Command": "命令",
+    "Communicating": "通信中",
     "Compaction in progress on remote database...": "正在远程数据库上执行压缩...",
     "Compaction on remote database completed successfully.": "远程数据库压缩已成功完成。",
     "Compaction on remote database failed.": "远程数据库压缩失败。",
     "Compaction on remote database timed out.": "远程数据库压缩超时。",
+    "Compare file": "比较文件",
     "Compare the content of files between on local database and storage. If not matched, you will be asked which one you want to keep.": "比较本地数据库与存储中的文件内容；如果不一致，你将被询问要保留哪一份。",
+    "Compare time and take newer": "比较时间并采用较新版本",
     "Compatibility (Conflict Behaviour)": "兼容性（冲突行为）",
     "Compatibility (Database structure)": "兼容性（数据库结构）",
     "Compatibility (Internal API Usage)": "兼容性（内部 API 使用）",
@@ -55,47 +128,90 @@
     "Compatibility (Remote Database)": "兼容性（远端数据库）",
     "Compatibility (Trouble addressed)": "兼容性（问题修复）",
     "Compute revisions for chunks": "为 chunks 计算修订版本(以前的行为)",
+    "Configuration": "配置",
     "Configuration Encryption": "配置加密",
     "Configure": "配置",
     "Configure And Change Remote": "配置并切换远端",
     "Configure E2EE": "配置 E2EE",
     "Configure Remote": "配置远端",
     "Configure the same server information as your other devices again, manually, very advanced users only.": "手动重新输入与你其他设备相同的服务器信息。仅适合高级用户。",
+    "Conflict & Deletion Options": "冲突与删除选项",
+    "Connect": "连接",
+    "Connect to existing database and continue": "连接到现有数据库并继续",
+    "Connected to Signaling Server (as Peer ID: ${peerId})": "已连接到信令服务器（对等方 ID：${peerId}）",
+    "Connected:": "已连接：",
     "Connection Method": "连接方式",
+    "Connection Settings": "连接设置",
+    "Connection:": "连接：",
+    "Content-derived chunk revisions (obsolete setting)": "基于内容的数据块修订（已过时的设置）",
+    "Continue anyway": "仍然继续",
     "Continue to CouchDB setup": "继续进行 CouchDB 设置",
     "Continue to Peer-to-Peer only setup": "继续进行仅 Peer-to-Peer 设置",
     "Continue to S3/MinIO/R2 setup": "继续进行 S3/MinIO/R2 设置",
     "Copy": "复制",
     "Copy Report to clipboard": "将报告复制到剪贴板",
+    "CouchDB Configuration": "CouchDB 配置",
     "CouchDB Connection Tweak": "CouchDB 连接调优",
+    "CouchDB validates the database name when you connect. The name must not be empty.": "CouchDB 会在连接时校验数据库名称。名称不能为空。",
+    "Create or connect to database and continue": "创建或连接到数据库并继续",
+    "Create P2P remote": "创建 P2P 远端",
     "Cross-platform": "跨平台",
     "Current adapter: {adapter}": "当前适配器：{adapter}",
+    "Custom Headers": "自定义请求头",
+    "Custom headers for requesting the bucket. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": "用于请求存储桶的自定义请求头。例如：`x-custom-header1: value1\n x-custom-header2: value2`",
+    "Custom headers for requesting the CouchDB. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": "用于请求 CouchDB 的自定义请求头。例如：`x-custom-header1: value1\n x-custom-header2: value2`",
     "Customization Sync": "自定义同步",
     "Customization Sync (Beta3)": "自定义同步（Beta3）",
     "Data Compression": "数据压缩",
+    "Data retrieval scheduled": "已安排数据获取",
+    "Data to Copy": "要复制的数据",
+    "Database -> Storage": "数据库 → 存储",
     "Database Adapter": "数据库适配器",
     "Database Name": "数据库名称",
     "Database suffix": "数据库后缀",
+    "Date": "日期",
     "Default": "默认",
     "Delay conflict resolution of inactive files": "推迟解决不活动文件",
     "Delay merge conflict prompt for inactive files.": "推迟手动解决不活动文件",
     "Delete": "删除",
     "Delete all customization sync data": "删除所有自定义同步数据",
     "Delete all data on the remote server.": "删除远端服务器上的所有数据。",
+    "Delete All of": "全部删除",
     "Delete local database to reset or uninstall Self-hosted LiveSync": "删除本地数据库以重置或卸载 Self-hosted LiveSync",
+    "Delete local files if deleted on remote": "若远程已删除，则删除本地文件",
+    "Delete local files if not on remote": "若远程不存在，则删除本地文件",
     "Delete old metadata of deleted files on start-up": "启动时删除已删除文件的旧元数据",
     "Delete Remote Configuration": "删除远端配置",
     "Delete remote configuration '{name}'?": "要删除远端配置“{name}”吗？",
+    "Delete remote configuration '${name}'?": "删除远端配置「${name}」？",
+    "DENIED": "已拒绝",
+    "DENIED (in session)": "已拒绝（本次会话）",
+    "Deny": "拒绝",
+    "Deny in session": "本次会话内拒绝",
+    "Deny permanently": "永久拒绝",
+    "Deselect all": "取消全选",
     "desktop": "桌面设备",
+    "Desktop only; uses more battery and network.": "仅限桌面端；会消耗更多电量和网络流量。",
+    "Desktop only. Allow sleep on this device even when the general option is disabled.": "仅限桌面端。即使通用选项已禁用，也允许此设备进入睡眠。",
+    "Detected Peers": "检测到的对等方",
     "Developer": "开发者",
     "Device": "设备",
+    "device name": "设备名称",
     "Device name": "设备名称",
+    "Device name to identify the device. Please use shorter one for the stable peer detection, i.e., \"iphone-16\" or \"macbook-2021\".": "用于标识设备的名称。为了对等方检测更稳定，请使用较短的名字，例如「iphone-16」或「macbook-2021」。",
+    "Device Peer ID": "设备对等方 ID",
     "Device Setup Method": "设备设置方式",
+    "Devices:": "设备：",
+    "Diagnostic RTCPeerConnection is enabled": "已启用诊断用 RTCPeerConnection",
     "dialog.yourLanguageAvailable": "Self-hosted LiveSync已提供您语言的翻译,因此启用了%{Display language}\n\n注意：并非所有消息都已翻译。我们期待您的贡献！\n注意 2：若您创建问题报告， **请切换回%{lang-def}** ，然后截取屏幕截图、消息和日志，此操作可在设置对话框中完成\n愿您使用顺心！",
     "dialog.yourLanguageAvailable.btnRevertToDefault": "保持%{lang-def}",
     "dialog.yourLanguageAvailable.Title": " 翻译可用!",
+    "Diff": "差异",
+    "Different": "不同",
     "Disables all synchronization and restart.": "禁用所有同步并重新启动。",
     "Disables logging, only shows notifications. Please disable if you report an issue.": "禁用日志记录,仅显示通知。如果您报告问题,请禁用此选项",
+    "Disconnect": "断开连接",
+    "Dismiss": "忽略",
     "Display Language": "显示语言",
     "Display name": "显示名称",
     "Do not check configuration mismatch before replication": "在复制前不检查配置不匹配",
@@ -109,7 +225,7 @@
     "Doctor.Button.Skip": "保持不变",
     "Doctor.Button.Yes": "确定",
     "Doctor.Dialogue.Main": "您好！配置医生已根据您的要求启动(感谢您)！！遗憾的是,检测到部分配置存在潜在问题。请放心,我们将逐一解决这些问题。\n\n提前告知您,我们将就以下事项进行确认：\n\n为数据块计算修订版本(此前行为)\n增强块大小\n\n我们开始处理吗?",
-    "Doctor.Dialogue.MainFix": "\n## ${name}\n\n| Current | Ideal |\n|:---:|:---:|\n| ${current} | ${ideal} |\n\n**Recommendation Level:** ${level}\n\n### Why this has been detected?\n\n${reason}\n\n${note}\n\nFix this to the ideal value?",
+    "Doctor.Dialogue.MainFix": "\n## ${name}\n\n| 当前值 | 理想值 |\n|:---:|:---:|\n| ${current} | ${ideal} |\n\n**建议级别：** ${level}\n\n### 为何检测到此问题？\n\n${reason}\n\n${note}\n\n是否将其修正为理想值？",
     "Doctor.Dialogue.Title": "Self-hosted LiveSync 配置诊断",
     "Doctor.Dialogue.TitleAlmostDone": "全部完成!",
     "Doctor.Dialogue.TitleFix": "修复问题 ${current}/${total}",
@@ -121,44 +237,98 @@
     "Doctor.Message.RebuildLocalRequired": "注意！需要重建本地数据库以应用此项！",
     "Doctor.Message.RebuildRequired": "注意！需要重建才能应用此项！",
     "Doctor.Message.SomeSkipped": "我们将某些问题留给了以后处理。是否要在下次启动时再次询问您？",
-    "Doctor.RULES.E2EE_V02500.REASON": "The End-to-End Encryption has got now more robust and faster. Also because, the previous E2EE was found to be compromised in a re-conducted code review. It should be applied as soon as possible. Really apologises for your inconvenience. And, this setting is not forward compatible. All synchronised devices must be updated to v0.25.0 or higher. Rebuilds are not required and will be converted from the new transfer to the new format, However, it is recommended to rebuild whenever possible.",
+    "Doctor.RULES.E2EE_V02500.REASON": "端到端加密现在变得更加稳健、更快。另外，之前的端到端加密在重新进行的代码审查中被发现存在安全漏洞，因此应尽快启用。对此给你带来的不便，我们深表歉意。此外，该设置不向前兼容，所有已同步的设备都必须更新到 v0.25.0 或更高版本。无需重建，数据会从新的传输方式转换为新格式，不过仍建议尽可能进行重建。",
+    "Document History": "文档历史记录",
     "Duplicate": "复制",
     "Duplicate remote": "复制远端配置",
     "E2EE Configuration": "E2EE 配置",
     "Edge case addressing (Behaviour)": "边缘情况处理（行为）",
     "Edge case addressing (Database)": "边缘情况处理（数据库）",
     "Edge case addressing (Processing)": "边缘情况处理（处理）",
+    "Effectively a directory. Should end with `/`. e.g., `vault-name/`.": "实际上是一个目录，应以 `/` 结尾，例如 `vault-name/`。",
     "Emergency restart": "紧急重启",
     "Enable advanced features": "启用高级功能",
+    "Enable advanced mode": "启用高级模式",
     "Enable customization sync": "启用自定义同步",
+    "Enable Developers' Debug Tools (If available).": "启用开发者调试工具（如可用）。",
     "Enable Developers' Debug Tools.": "启用开发者调试工具 ",
     "Enable edge case treatment features": "启用边缘情况处理功能",
+    "Enable forcePathStyle": "启用 forcePathStyle",
+    "Enable P2P Replicator": "启用 P2P 复制器",
+    "Enable P2P Synchronization": "启用 P2P 同步",
+    "Enable per-file customization sync": "启用逐文件自定义同步",
+    "Enable power user mode": "启用专家模式",
     "Enable poweruser features": "启用高级用户功能",
     "Enable this if your Object Storage doesn't support CORS": "如果您的对象存储不支持 CORS,请启用此功能 ",
     "Enable this option to automatically apply the most recent change to documents even when it conflicts": "启用此选项可在文档冲突时自动应用最新的更改",
+    "Enabled": "已启用",
+    "Enabling end-to-end encryption ensures that your data is encrypted on your device before being sent to the remote server. This means that even if someone gains access to the server, they won't be able to read your data without the passphrase. Make sure to remember your passphrase, as it will be required to decrypt your data on other devices.": "启用端到端加密可确保数据在发送到远端服务器之前已在本设备上加密。这意味着即使有人获得了服务器的访问权限，没有密码短语也无法读取你的数据。请务必记住你的密码短语，因为在其他设备上解密数据时需要用到它。",
     "Encrypt contents on the remote database. If you use the plugin's synchronization feature, enabling this is recommended.": "加密远程数据库中的内容。如果您使用插件的同步功能,则建议启用此功能 ",
+    "Encrypt file properties (paths, times, sizes, and Chunk references) used by Hidden File Sync and Customisation Sync. This affects future writes; manually rebuild the remote database to protect existing properties. Requires E2EE V2, Property Encryption, and compatible clients on every device.": "加密隐藏文件同步和自定义同步所使用的文件属性（路径、时间、大小以及数据块引用）。此设置影响之后的写入；如需保护已有属性，请手动重建远程数据库。需要 E2EE V2 和属性加密，并且每台设备上的客户端都需兼容。",
+    "Encrypt internal file Properties": "加密内部文件属性",
     "Encrypting sensitive configuration items": "加密敏感配置项",
+    "Encryption Algorithm": "加密算法",
+    "Encryption passphrase. If changed, you should overwrite the server's database with the new (encrypted) files.": "加密密码短语。如果更改，你应当用新的（加密后的）文件覆盖服务器上的数据库。",
     "Encryption phassphrase. If changed, you should overwrite the server's database with the new (encrypted) files.": "加密密码。如果更改,您应该用新的(加密的)文件覆盖服务器的数据库 ",
     "End-to-End Encryption": "端到端加密",
+    "End-to-End Encryption Algorithm": "端到端加密算法",
     "Endpoint URL": "终端URL",
     "Enhance chunk size": "增大块大小",
+    "Enter a complete HTTP or HTTPS URL.": "输入完整的 HTTP 或 HTTPS 地址。",
+    "Enter a folder prefix (optional)": "输入文件夹前缀（可选）",
     "Enter Server Information": "输入服务器信息",
+    "Enter Setup URI": "输入设置 URI",
     "Enter the server information manually": "手动输入服务器信息",
+    "Enter TURN credential": "输入 TURN 凭据",
+    "Enter TURN username": "输入 TURN 用户名",
+    "Enter your Access Key ID": "输入你的访问密钥 ID",
+    "Enter your Bucket Name": "输入你的存储桶名称",
+    "Enter your database name": "输入你的数据库名称",
+    "Enter your JWT Key ID": "输入你的 JWT 密钥 ID",
+    "Enter your JWT secret or private key": "输入你的 JWT 密钥或私钥",
+    "Enter your JWT Subject (CouchDB Username)": "输入你的 JWT 主体（CouchDB 用户名）",
+    "Enter your passphrase": "输入你的密码短语",
+    "Enter your password": "输入你的密码",
+    "Enter your Region (e.g., us-east-1, auto for R2)": "输入你的区域（例如 us-east-1，R2 填 auto）",
+    "Enter your Secret Access Key": "输入你的私有访问密钥",
+    "Enter your username": "输入你的用户名",
+    "Error during connection test: ${reason}": "连接测试出错：${reason}",
+    "Error during testAndFixSettings: ${reason}": "testAndFixSettings 出错：${reason}",
+    "Experimental Settings": "实验性设置",
     "Export": "导出",
     "Failed to connect to remote for compaction.": "无法连接到远程数据库以执行压缩。",
     "Failed to connect to remote for compaction. ${reason}": "无法连接到远程数据库以执行压缩。${reason}",
+    "Failed to connect to the server: ${reason}": "无法连接到服务器：${reason}",
+    "Failed to connect to the server. Please check your settings.": "无法连接到服务器。请检查你的设置。",
+    "Failed to connect to the signalling relay: ${reason}": "无法连接到信令中继：${reason}",
+    "Failed to create replicator instance.": "创建复制器实例失败。",
+    "Failed to parse Setup-URI.": "无法解析设置 URI。",
     "Failed to start one-shot replication before Garbage Collection. Garbage Collection Cancelled.": "无法在垃圾回收前启动一次性复制。垃圾回收已取消。",
     "Failed to start replication after Garbage Collection.": "垃圾回收后无法启动复制。",
+    "Failed:": "失败：",
     "Fetch": "获取",
     "Fetch chunks on demand": "按需获取块",
     "Fetch database with previous behaviour": "使用以前的行为获取数据库",
     "Fetch remote settings": "获取远端设置",
+    "FETCHING": "获取中",
+    "Fetching status...": "正在获取状态…",
+    "File integrity": "文件完整性",
+    "File prefix on the bucket": "存储桶中的文件前缀",
     "File to resolve conflict": "选择要解决冲突的文件",
+    "File to view History": "要查看历史记录的文件",
     "Filename": "文件名",
+    "Files with modification times greater than this value (in seconds since the Unix epoch) will not have their events reflected. Set to 0 to disable this limit.": "修改时间大于此值（Unix 时间戳，单位为秒）的文件，其事件将不会被反映。设为 0 可禁用此限制。",
+    "Final Confirmation: Overwrite Server Data with This Device's Files": "最终确认：用本设备的文件覆盖服务器数据",
+    "Finalise the process and resume normal operation": "完成流程并恢复正常运行",
     "First, please select the option that best describes your current situation.": "首先，请选择最符合你当前情况的选项。",
+    "Fix": "修复",
     "Flag and restart": "标记后重启",
+    "Flagged Selective": "已标记为选择性",
+    "Folder Prefix": "文件夹前缀",
+    "For HS256/HS512 algorithms, provide the shared secret key. For ES256/ES512 algorithms, provide the pkcs8 PEM-formatted private key.": "对于 HS256/HS512 算法，请提供共享密钥。对于 ES256/ES512 算法，请提供 pkcs8 PEM 格式的私钥。",
     "Forces the file to be synced when opened.": "打开文件时强制同步该文件 ",
     "Fresh Start Wipe": "全新开始清除",
+    "Furthermore, if conflicts are already present in the server data, they will be synchronised to this device as they are, and you will need to resolve them locally.": "此外，如果服务器数据中已存在冲突，它们会原样同步到本设备，你需要在本设备上解决。",
     "Garbage Collection cancelled by user.": "用户已取消垃圾回收。",
     "Garbage Collection completed. Deleted chunks: ${deletedChunks} / ${totalChunks}. Time taken: ${seconds} seconds.": "垃圾回收完成。已删除 chunks：${deletedChunks} / ${totalChunks}。耗时：${seconds} 秒。",
     "Garbage Collection Confirmation": "垃圾回收确认",
@@ -166,55 +336,119 @@
     "Garbage Collection: Found ${unusedChunks} unused chunks to delete.": "垃圾回收：发现 ${unusedChunks} 个未使用的 chunks 待删除。",
     "Garbage Collection: Scanned ${scanned} / ~${docCount}": "垃圾回收：已扫描 ${scanned} / ~${docCount}",
     "Garbage Collection: Scanning completed. Total chunks: ${totalChunks}, Used chunks: ${usedChunks}": "垃圾回收：扫描完成。总 chunks：${totalChunks}，已使用 chunks：${usedChunks}",
+    "Gathering information...": "正在收集信息…",
+    "Generate Random ID": "生成随机 ID",
+    "Group ID": "组 ID",
     "Handle files as Case-Sensitive": "将文件视为区分大小写",
+    "Have you created a backup before proceeding?": "继续之前，你备份了吗？",
+    "Hidden file synchronization have been temporarily disabled. Please enable them after the fetching, if you need them.": "隐藏文件同步已被临时停用。获取完成后如需使用，请重新启用。",
     "Hidden Files": "隐藏文件",
     "Hide completely": "完全隐藏",
+    "Hide not applicable items": "隐藏不适用项",
+    "Hide password": "隐藏密码",
+    "Higher (${local} > ${remote})": "较高（${local} > ${remote}）",
+    "Highlight diff": "高亮差异",
+    "How should files that were deleted on other devices be handled?\n\n- **${NEWER_CLEANUP}**: Delete local files if they were deleted on remote.\n  This is useful if you want to keep your vault clean and consistent across devices, but please make sure you have a backup if there is already any important data in your vault.\n- **${NEWER_SYNC_ALL}**: Recreate remote files even if they were deleted on remote.\n  This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.": "其他设备上删除的文件应如何处理？\n\n- **${NEWER_CLEANUP}**：如果文件在远程被删除，则删除本地文件。\n  如果你希望让各设备上的库保持整洁一致，这会很有用。但如果库中已有重要数据，请务必先做好备份。\n- **${NEWER_SYNC_ALL}**：即使文件在远程已被删除，也重新创建远程文件。\n  此选项会保留你所有的本地文件，但如果有些文件只存在于本地而不存在于远程，可能会产生重复文件。同步完成后，你可以手动清理这些重复文件。",
     "How to display network errors when the sync server is unreachable.": "当同步服务器不可达时，如何显示网络错误。",
+    "How to handle extra existing local files?": "如何处理本地已有的多余文件？",
     "How would you like to configure the connection to your server?": "你希望如何配置与服务器的连接？",
+    "However, This should not be enabled if you want to increase your secrecy more.": "不过，如果你希望进一步提高保密性，则不应启用此项。",
     "I am adding a device to an existing synchronisation setup": "我要将设备加入现有同步配置",
     "I am ready, unlock the database": "我已准备好，立即解锁数据库",
     "I am setting this up for the first time": "我是第一次进行设置",
+    "I am setting up a new server for the first time / I want to reset my existing server.": "我是第一次设置新服务器／我想重置现有服务器。",
+    "I am unable to create a backup of my Vault.": "我无法备份我的库。",
+    "I am unable to create a backup of my Vaults.": "我无法备份我的库。",
+    "I have created a backup of my Vault.": "我已备份我的库。",
     "I have made a backup, mark this device as resolved": "我已完成备份，将此设备标记为“已确认”",
     "I know my server details, let me enter them": "我知道服务器详情，让我手动输入",
+    "I understand that all changes made on other smartphones or computers possibly could be lost.": "我明白在其他手机或电脑上所做的更改可能会丢失。",
+    "I understand that other devices will no longer be able to synchronise, and will need to be reset the synchronisation information.": "我明白其他设备将无法继续同步，需要重置同步信息。",
+    "I understand that this action is irreversible once performed.": "我明白此操作一旦执行便不可撤销。",
+    "I understand the risks and will proceed without a backup.": "我明白风险，将在没有备份的情况下继续。",
+    "I Understand, Overwrite Server": "我明白，覆盖服务器",
+    "If \"Auto Start P2P Connection\" is enabled, the P2P connection will be started automatically when the plug-in launches.": "如果启用了「自动启动 P2P 连接」，插件启动时会自动建立 P2P 连接。",
     "If disabled(toggled), chunks will be split on the UI thread (Previous behaviour).": "如果禁用(切换),chunks 将在 UI 线程上分割(以前的行为)",
     "If enabled per-filed efficient customization sync will be used. We need a small migration when enabling this. And all devices should be updated to v0.23.18. Once we enabled this, we lost a compatibility with old versions.": "如果启用,将使用基于文件的、高效的自定义同步。启用此功能需要进行一次小的迁移。所有设备都应更新到 v0.23.18。一旦启用此功能,我们将失去与旧版本的兼容性",
+    "If enabled, changes will be automatically broadcasted to all connected peers. Notified peers will start fetching the changes.": "启用后，更改将自动广播给所有已连接的对等方。收到通知的对等方将开始获取这些更改。",
     "If enabled, chunks will be split into no more than 100 items. However, dedupe is slightly weaker.": "如果启用,数据块将被分割成不超过 100 项。但是,去重效果会稍弱",
+    "If enabled, efficient per-file customization sync will be used. A minor migration is required when enabling this feature, and all devices must be updated to v0.23.18. Enabling this feature will result in losing compatibility with older versions.": "启用后，将使用更高效的逐文件自定义同步。启用此功能需要进行一次小规模迁移，并且所有设备都必须更新到 v0.23.18。启用此功能后，将失去与旧版本的兼容性。",
     "If enabled, newly created chunks are temporarily kept within the document, and graduated to become independent chunks once stabilised.": "如果启用,新创建的数据块将暂时保留在文档中,并在稳定后成为独立数据块",
     "If enabled, the ⛔ icon will be shown inside the status instead of the file warnings banner. No details will be shown.": "如果启用，状态栏内将显示 ⛔ 图标，而非文件警告横幅，不会显示任何详细信息。",
+    "If enabled, the file properties will be encrypted in the remote database. This is useful for protecting sensitive information in file paths, sizes, and IDs of its chunks. If you are using V1 E2EE, this only obfuscates the file path.": "启用后，文件属性将在远程数据库中加密。这有助于保护文件路径、大小以及其数据块 ID 等敏感信息。如果你使用的是 V1 E2EE，则只会混淆文件路径。",
     "If enabled, the file under 1kb will be processed in the UI thread.": "如果启用,小于 1kb 的文件将在 UI 线程中处理",
+    "If enabled, the forcePathStyle option will be used for bucket operations.": "启用后，存储桶操作将使用 forcePathStyle 选项。",
     "If enabled, the notification of hidden files change will be suppressed.": "如果启用,将不再通知隐藏文件被更改",
+    "If enabled, the P2P connection will be automatically started when the application launches.": "启用后，应用启动时将自动开始 P2P 连接。",
+    "If enabled, the plugin will not attempt to connect to the remote database even if the chunk was not found locally.": "启用后，即使本地未找到数据块，插件也不会尝试连接远程数据库。",
+    "If enabled, the request API will be used to avoid `inevitable` CORS problems. This is a workaround and may not work in all cases. PLEASE READ THE DOCUMENTATION BEFORE USING THIS OPTION. This is a less-secure option.": "启用后，将使用 Request API 来避免 `inevitable` CORS 问题。这只是一种变通方法，并非在所有情况下都有效。请务必在使用此选项前阅读文档。这是一个安全性较低的选项。",
     "If this enabled, all chunks will be stored with the revision made from its content. (Previous behaviour)": "如果启用,所有 chunks 将使用根据其内容生成的修订版本存储(以前的行为)",
     "If this enabled, All files are handled as case-Sensitive (Previous behaviour).": "如果启用,所有文件都将视为区分大小写(以前的行为)",
     "If this enabled, chunks will be split into semantically meaningful segments. Not all platforms support this feature.": "如果启用此功能,数据块将被分割成具有语义意义的段落。并非所有平台都支持此功能",
+    "If this enabled, JWT will be used for authentication.": "启用后将使用 JWT 认证。",
     "If this is set, changes to local files which are matched by the ignore files will be skipped. Remote changes are determined using local ignore files.": "如果设置了此项,与忽略文件匹配的本地文件的更改将被跳过。远程更改使用本地忽略文件确定",
     "If this option is enabled, PouchDB will hold the connection open for 60 seconds, and if no change arrives in that time, close and reopen the socket, instead of holding it open indefinitely. Useful when a proxy limits request duration but can increase resource usage.": "如果启用此选项,PouchDB 将保持连接打开 60 秒,如果在此时间内没有更改到达,则关闭并重新打开套接字,而不是无限期保持打开。当代理限制请求持续时间时有用,但可能会增加资源使用ß",
+    "If you cannot avoid CORS issues, you might want to try this option. It uses Obsidian's internal API to communicate with the CouchDB server. Not compliant with web standards, but works. Note that this might break in future Obsidian versions.": "如果无法避开 CORS 问题，可以试试此选项。它使用 Obsidian 的内部 API 与 CouchDB 服务器通信。不符合 Web 标准，但可用。请注意，未来的 Obsidian 版本可能会使其失效。",
+    "If you cannot avoid CORS issues, you might want to try this option. It uses Obsidian's internal API to communicate with the S3 server. Not compliant with web standards, but works. Note that this might break in future Obsidian versions.": "如果无法避开 CORS 问题，可以试试此选项。它使用 Obsidian 的内部 API 与 S3 服务器通信。不符合 Web 标准，但可用。请注意，未来的 Obsidian 版本可能会使其失效。",
+    "If you have unsynchronised changes in your Vault on this device, they will likely diverge from the server's versions after the reset. This may result in a large number of file conflicts.": "如果本设备的库中有未同步的更改，重置后它们很可能与服务器上的版本产生分歧。这可能导致大量文件冲突。",
+    "If you reached the payload size limit when using IBM Cloudant, please decrease batch size and batch limit to a lower value.": "如果在使用 IBM Cloudant 时达到载荷大小上限，请把批量大小和批量上限调低。",
+    "If you understand the risks and still wish to proceed, select so.": "如果你明白风险但仍希望继续，请选择此项。",
+    "If you want to store the data in a specific folder within the bucket, you can specify a folder prefix here. Otherwise, leave it blank to store data at the root of the bucket.": "如果想把数据存放在存储桶内的指定文件夹中，可以在此指定文件夹前缀。否则留空，数据将存放在存储桶根目录。",
+    "If you want to use `LiveSync`, you should broadcast changes. All `watching` peers which detects this will start the replication for fetching.": "如果要使用 `LiveSync`，你应当广播变更。所有检测到变更的 `watching` 对等方都会启动复制以获取数据。",
+    "Ignore": "忽略",
     "Ignore and Proceed": "忽略并继续",
     "Ignore files": "忽略文件",
     "Ignore patterns": "忽略模式",
     "Import connection": "导入连接",
+    "IMPORTANT": "重要",
+    "In most cases, you should stick with the default algorithm (${algorithm}), This setting is only required if you have an existing Vault encrypted in a different format.": "大多数情况下，你应当沿用默认算法（${algorithm}）。只有当你有以其他格式加密的现有库时，才需要此项设置。",
+    "In this scenario, Self-hosted LiveSync will recreate metadata for every file and deliberately generate conflicts. Where the file content is identical, these conflicts will be resolved automatically.": "在此情形下，Self-hosted LiveSync 会为每个文件重建元数据并有意制造冲突。若文件内容完全相同，这些冲突将被自动解决。",
+    "Incoming:": "接收：",
     "Incubate Chunks in Document": "在文档中孵化块",
+    "Initial Action": "初始操作",
     "Initialise all journal history, On the next sync, every item will be received and sent.": "初始化所有日志历史。下次同步时，所有项目都会重新接收并发送。",
+    "Initialise journal received history. On the next sync, every item except this device sent will be downloaded again.": "初始化日志的已接收历史。下次同步时，除本设备已发送的项外，其余都会重新下载。",
+    "Initialise journal sent history. On the next sync, every item except this device received will be sent again.": "初始化日志的已发送历史。下次同步时，除本设备已接收的项外，其余都会重新发送。",
+    "Internal timestamp for resolving compatible tweak mismatches.": "用于解决兼容的调整值不一致问题的内部时间戳。",
     "Interval (sec)": "间隔(秒)",
+    "INVERTED": "已反转",
+    "Issue detection log:": "问题检测日志：",
+    "It is strongly advised to create a backup before proceeding. Continuing without a backup may lead to data loss.": "强烈建议在继续之前先做备份。没有备份继续可能导致数据丢失。",
+    "Just for a minute, please!": "请稍等一分钟！",
+    "JWT (JSON Web Token) authentication allows you to securely authenticate with the CouchDB server using tokens. Ensure that your CouchDB server is configured to accept JWTs and that the provided key and settings match the server's configuration. Incidentally, I have not verified it very thoroughly.": "JWT（JSON Web Token）身份验证让你可以用令牌安全地通过 CouchDB 服务器验证身份。请确保你的 CouchDB 服务器已配置为接受 JWT，且所提供的密钥和设置与服务器配置相符。顺带一提，我并没有非常彻底地验证过它。",
+    "JWT Algorithm": "JWT 算法",
+    "JWT Expiration Duration (minutes)": "JWT 有效期（分钟）",
+    "JWT Key": "JWT 密钥",
+    "JWT Key ID (kid)": "JWT 密钥 ID（kid）",
+    "JWT Subject (sub)": "JWT 主体（sub）",
     "K.exp": "实验性",
     "K.long_p2p_sync": "%{title_p2p_sync} (%{exp})",
     "K.P2P": "%{Peer}-to-%{Peer}",
     "K.Peer": "Peer",
     "K.ScanCustomization": "扫描自定义",
     "K.short_p2p_sync": "P2P同步(%{exp})",
-    "K.title_p2p_sync": "Peer-to-Peer同步",
+    "K.title_p2p_sync": "Peer-to-Peer 同步",
     "Keep empty folder": "保留空文件夹",
-    "lang_def": "Default",
+    "Keep local files even if deleted on remote": "即使远程已删除，也保留本地文件",
+    "Keep local files even if not on remote": "即使远程不存在，也保留本地文件",
+    "Keep replication active in the background": "在后台保持复制运行",
+    "Key ID": "密钥 ID",
+    "Keypair or pre-shared key": "密钥对或预共享密钥",
+    "lang_def": "默认",
     "lang-de": "Deutsche",
     "lang-def": "%{lang_def}",
     "lang-es": "Español",
     "lang-fr": "Français",
+    "lang-he": "希伯来语",
     "lang-ja": "日本語",
     "lang-ko": "한국어",
     "lang-ru": "Русский",
     "lang-zh": "简体中文",
     "lang-zh-tw": "繁體中文",
+    "Last tweak modified timestamp": "调整值最后修改时间戳",
     "Later": "稍后",
     "Limit: {datetime} ({timestamp})": "限制：{datetime}（{timestamp}）",
+    "live": "实时",
     "LiveSync could not handle multiple vaults which have same name without different prefix, This should be automatically configured.": "LiveSync 无法处理具有相同名称但没有不同前缀的多个库。这应该自动配置",
     "liveSyncReplicator.beforeLiveSync": "在LiveSync前,先启动OneShot一次...",
     "liveSyncReplicator.cantReplicateLowerValue": "我们无法复制更小的值",
@@ -227,6 +461,7 @@
     "liveSyncReplicator.liveSyncBegin": "LiveSync 开始...",
     "liveSyncReplicator.lockRemoteDb": "锁定远程数据库以防止数据损坏",
     "liveSyncReplicator.markDeviceResolved": "将此设备标记为“已解决”",
+    "liveSyncReplicator.mismatchedTweakDetected": "检测到设备之间的配置存在不一致。执行一次手动复制将尝试解决此问题。",
     "liveSyncReplicator.oneShotSyncBegin": "OneShot同步开始...(${syncMode})",
     "liveSyncReplicator.remoteDbCorrupted": "远程数据库较新或已损坏,请确保已安装最新版本的self-hosted-livesync",
     "liveSyncReplicator.remoteDbCreatedOrConnected": "远程数据库已创建或连接",
@@ -241,6 +476,8 @@
     "liveSyncSetting.originalValue": "原始值：${value}",
     "liveSyncSetting.valueShouldBeInRange": "值应该在 ${min} < value < ${max} 之间",
     "liveSyncSettings.btnApply": "应用",
+    "Local Database Tweak": "本地数据库微调",
+    "Local only": "仅本地",
     "Lock": "锁定",
     "Lock Server": "锁定服务器",
     "Lock the remote server to prevent synchronization with other devices.": "锁定远端服务器，以阻止其他设备继续同步。",
@@ -249,17 +486,27 @@
     "logPane.pause": "暂停",
     "logPane.title": "Self-hosted LiveSync 日志",
     "logPane.wrap": "自动换行",
+    "Longest chunk line threshold value (Not Configurable from the UI Now).": "最长数据块行的阈值（目前无法在界面中配置）。",
+    "Lower (${local} < ${remote})": "较低（${local} < ${remote}）",
+    "Maintenance Commands": "维护命令",
+    "Maintenance mode": "维护模式",
     "Maximum delay for batch database updating": "批量数据库更新的最大延迟",
+    "Maximum file modification time for reflected file events": "可反映文件事件的最大修改时间",
     "Maximum file size": "最大文件大小",
     "Maximum Incubating Chunk Size": "最大孵化块大小",
     "Maximum Incubating Chunks": "最大孵化块数",
     "Maximum Incubation Period": "最大孵化期",
+    "Maximum request size for manually resending chunks": "手动重新发送数据块时的最大请求大小",
     "MB (0 to disable).": "MB(0为禁用)",
+    "MB per request": "每次请求的 MB 数",
+    "Memory cache": "内存缓存",
     "Memory cache size (by total characters)": "内存缓存大小(按总字符数)",
     "Memory cache size (by total items)": "内存缓存大小(按总项目数)",
     "Merge": "合并",
+    "Minimum Chunk Size (Not Configurable from the UI Now).": "最小数据块大小（目前无法在界面中配置）。",
     "Minimum delay for batch database updating": "批量数据库更新的最小延迟",
     "Minimum interval for syncing": "同步最小间隔",
+    "Mixed": "混合",
     "moduleCheckRemoteSize.logCheckingStorageSizes": "正在检查存储大小",
     "moduleCheckRemoteSize.logCurrentStorageSize": "远程存储大小：${measuredSize}",
     "moduleCheckRemoteSize.logExceededWarning": "远程存储大小：${measuredSize} 超过 ${notifySize}",
@@ -267,6 +514,8 @@
     "moduleCheckRemoteSize.msgConfirmRebuild": "这可能需要一些时间。您真的想现在重建所有内容吗？",
     "moduleCheckRemoteSize.msgDatabaseGrowing": "**您的数据库正在变大！** 但别担心,我们现在可以解决它。在远程存储空间用完之前还有时间。\n\n| 测量大小 | 配置大小 |\n| --- | --- |\n| ${estimatedSize} | ${maxSize} |\n\n> [!MORE]-\n> 如果您已经使用了很多年,数据库中可能会积累未引用的 chunks——也就是垃圾。因此,我们建议重建所有内容。它可能会变得小得多。\n>\n> 如果您的库容量只是在增加,最好在整理文件后重建所有内容。即使您为了加速过程删除了文件,Self-hosted LiveSync 也不会删除实际数据。这大致[有文档记录](https://github.com/vrtmrz/obsidian-livesync/blob/main/docs/tech_info.md)。\n>\n> 如果您不介意增加,可以将通知限制增加 100MB。如果您在自己的服务器上运行,就是这种情况。但是,最好还是不时地重建所有内容。\n>\n\n> [!WARNING]\n> 如果您执行重建所有内容,请确保所有设备都已同步。尽管如此,插件会尽可能地合并\n",
     "moduleCheckRemoteSize.msgSetDBCapacity": "我们可以设置一个最大数据库容量警告,**以便在远程存储空间耗尽前采取行动**。\n您想启用这个功能吗?\n\n> [!MORE]-\n> - 0: 不警告存储大小。\n>   如果您在远程存储(尤其是自托管)上有足够的空间,则推荐此选项。您可以手动检查存储大小并重建。\n> - 800: 如果远程存储大小超过 800MB 则发出警告。\n>   如果您使用的是 fly.io(1GB 限制) 或 IBM Cloudant,则推荐此选项。\n> - 2000: 如果远程存储大小超过 2GB 则发出警告。\n\n如果达到限制,系统会要求我们逐步增大限制\n",
+    "moduleCheckRemoteSize.noticeExceeded": "远端存储体积为 ${measuredSize}，已超过配置的提醒阈值 ${notifySize}。{HERE}",
+    "moduleCheckRemoteSize.noticeNotConfigured": "未配置远端存储体积提醒。{HERE}",
     "moduleCheckRemoteSize.option2GB": "2GB (标准)",
     "moduleCheckRemoteSize.option800MB": "800MB (Cloudant, fly.io)",
     "moduleCheckRemoteSize.optionAskMeLater": "稍后问我",
@@ -274,6 +523,7 @@
     "moduleCheckRemoteSize.optionIncreaseLimit": "增加到 ${newMax}MB",
     "moduleCheckRemoteSize.optionNoWarn": "不,请永远不要警告",
     "moduleCheckRemoteSize.optionRebuildAll": "立即重建所有内容",
+    "moduleCheckRemoteSize.optionReview": "查看选项",
     "moduleCheckRemoteSize.titleDatabaseSizeLimitExceeded": "远程存储大小超出限制",
     "moduleCheckRemoteSize.titleDatabaseSizeNotify": "设置数据库大小通知",
     "moduleInputUIObsidian.defaultTitleConfirmation": "确认",
@@ -294,6 +544,7 @@
     "moduleLiveSyncMain.optionResumeAndRestart": "恢复并重启 Obsidian",
     "moduleLiveSyncMain.titleScramEnabled": "紧急停止已启用",
     "moduleLocalDatabase.logWaitingForReady": "等待就绪...",
+    "moduleLog.pathComponentTooLong": "此路径中包含超过 ${maxBytes} 个 UTF-8 字节的文件或文件夹名。在某些 Android 和 Linux 文件系统上可能无法正常工作。",
     "moduleLog.showLog": "显示日志",
     "moduleMigration.fix0256.buttons.checkItLater": "稍后检查",
     "moduleMigration.fix0256.buttons.DismissForever": "我已经修复了，不再询问",
@@ -328,23 +579,41 @@
     "moduleMigration.titleCaseSensitivity": "大小写敏感性",
     "moduleObsidianMenu.replicate": "复制",
     "More actions": "更多操作",
+    "Mostly Complete: Decision Required": "基本完成：需要你决定",
     "Move remotely deleted files to the trash, instead of deleting.": "将远程删除的文件移至回收站,而不是直接删除",
+    "Move remotely deleted files to the trash, instead of deleting. (This setting is ineffective from Obsidian v1.7.2 onwards, as deletion always respects your Obsidian preferences.)": "将远程删除的文件移至回收站，而不是直接删除。（此设置自 Obsidian v1.7.2 起不再生效，因为删除操作始终遵循你在 Obsidian 中的偏好设置。）",
+    "My remote server is already set up. I want to join this device.": "我的远端服务器已设置好，我想让本设备加入。",
+    "Name": "名称",
     "Network warning style": "网络警告样式",
+    "NEW": "新增",
     "New Remote": "新建远端",
+    "Newer (${diff})": "较新（${diff}）",
+    "No checks have been performed yet.": "尚未执行任何检查。",
     "No connected device information found. Cancelling Garbage Collection.": "未找到已连接设备的信息。正在取消垃圾回收。",
+    "No Connection": "未连接",
+    "No devices available. Waiting for other devices to connect...": "没有可用的设备。正在等待其他设备连接…",
+    "No Items.": "无项目。",
     "No limit configured": "未配置限制",
+    "NO PREVIEW": "无预览",
     "No, please take me back": "不，返回上一步",
     "Node ID": "节点 ID",
     "Node Information Missing": "节点信息缺失",
     "Non-Synchronising files": "不同步的文件",
     "Normal Files": "普通文件",
     "Not all messages have been translated. And, please revert to \"Default\" when reporting errors.": "并非所有消息都已翻译。请在报告错误时恢复为\"默认\"",
+    "Not configured": "未配置",
+    "Not now": "暂不",
+    "Note that the Group ID is not limited to the generated format; you can use any string as the Group ID.": "请注意，组 ID 不限于生成的格式；你可以使用任意字符串作为组 ID。",
+    "Note that you can generate a new Setup URI by running the \"Copy settings as a new Setup URI\" command in the command palette.": "请注意，你可以在命令面板中运行「Copy settings as a new Setup URI」命令来生成新的设置 URI。",
     "Notify all setting files": "通知所有设置文件",
     "Notify customized": "通知自定义设置",
     "Notify when other device has newly customized.": "当其他设备有新的自定义设置时通知 ",
     "Notify when the estimated remote storage size exceeds on start up": "启动时当估计的远程存储大小超出时通知",
+    "Now we can choose how to split the chunks; V3 is the most efficient. If you have troubled, please make this Default or Legacy.": "现在可以选择数据块的分割方式；V3 效率最高。如果遇到问题，请将此项设为 Default 或 Legacy。",
     "Number of batches to process at a time. Defaults to 40. Minimum is 2. This along with batch size controls how many docs are kept in memory at a time.": "一次处理的批量数量。默认为 40。最小为 2。此设置与批量大小一起控制一次在内存中保留多少文档",
     "Number of changes to sync at a time. Defaults to 50. Minimum is 2.": "一次同步的更改数量。默认为 50。最小为 2。",
+    "Obfuscate Properties": "混淆属性",
+    "Obfuscating properties (e.g., path of file, size, creation and modification dates) adds an additional layer of security by making it harder to identify the structure and names of your files and folders on the remote server. This helps protect your privacy and makes it more difficult for unauthorized users to infer information about your data.": "混淆属性（例如文件路径、大小、创建和修改日期）通过让远端服务器上更难识别你文件和文件夹的结构与名称，增加了一层额外的安全保障。这有助于保护你的隐私，也让未授权用户更难推断出关于你数据的信息。",
     "Obsidian version": "Obsidian 版本",
     "obsidianLiveSyncSettingTab.btnApply": "应用",
     "obsidianLiveSyncSettingTab.btnCheck": "检查",
@@ -407,6 +676,7 @@
     "obsidianLiveSyncSettingTab.logPassphraseNotCompatible": "错误：密码与远程服务器不兼容！请再次检查！",
     "obsidianLiveSyncSettingTab.logRebuildNote": "同步已禁用,如果需要,请获取并重新启用",
     "obsidianLiveSyncSettingTab.logSelectAnyPreset": "请选择任一预设。",
+    "obsidianLiveSyncSettingTab.logServerConfigurationCheck": "服务器配置检查",
     "obsidianLiveSyncSettingTab.msgAreYouSureProceed": "您确定要继续吗？",
     "obsidianLiveSyncSettingTab.msgChangesNeedToBeApplied": "需要应用更改！",
     "obsidianLiveSyncSettingTab.msgConfigCheck": "--配置检查--",
@@ -456,7 +726,7 @@
     "obsidianLiveSyncSettingTab.okCorsOriginMatched": "✔ CORS 源正常",
     "obsidianLiveSyncSettingTab.okCorsOrigins": "✔ cors.origins 设置正确",
     "obsidianLiveSyncSettingTab.okEnableCors": "✔ httpd.enable_cors 设置正确",
-    "obsidianLiveSyncSettingTab.okEnableCorsChttpd": "✔ chttpd.enable_cors is ok.",
+    "obsidianLiveSyncSettingTab.okEnableCorsChttpd": "✔ chttpd.enable_cors 设置正确",
     "obsidianLiveSyncSettingTab.okMaxDocumentSize": "✔ couchdb.max_document_size 设置正确",
     "obsidianLiveSyncSettingTab.okMaxRequestSize": "✔ chttpd.max_http_request_size 设置正确",
     "obsidianLiveSyncSettingTab.okRequireValidUser": "✔ chttpd.require_valid_user 设置正确",
@@ -483,6 +753,7 @@
     "obsidianLiveSyncSettingTab.panelSetup": "设置",
     "obsidianLiveSyncSettingTab.serverVersion": "服务器信息: ${info}",
     "obsidianLiveSyncSettingTab.titleActiveRemoteServer": "活动远程服务器",
+    "obsidianLiveSyncSettingTab.titleAdvancedSettings": "高级设置",
     "obsidianLiveSyncSettingTab.titleAppearance": "外观",
     "obsidianLiveSyncSettingTab.titleConflictResolution": "冲突处理",
     "obsidianLiveSyncSettingTab.titleCouchDB": "CouchDB 服务器",
@@ -490,11 +761,16 @@
     "obsidianLiveSyncSettingTab.titleEncryptionNotEnabled": "尚未启用加密",
     "obsidianLiveSyncSettingTab.titleEncryptionPassphraseInvalid": "加密密码短语无效",
     "obsidianLiveSyncSettingTab.titleExtraFeatures": "启用额外和高级功能",
+    "obsidianLiveSyncSettingTab.titleExtraFeaturesGroup": "扩展功能",
+    "obsidianLiveSyncSettingTab.titleExtraMenus": "扩展菜单",
     "obsidianLiveSyncSettingTab.titleFetchConfig": "获取配置",
     "obsidianLiveSyncSettingTab.titleFetchConfigFromRemote": "从远程服务器获取配置",
     "obsidianLiveSyncSettingTab.titleFetchSettings": "获取设置",
+    "obsidianLiveSyncSettingTab.titleHelpAndInformation": "帮助与信息",
+    "obsidianLiveSyncSettingTab.titleHelpAndTroubleshooting": "帮助与疑难解答",
     "obsidianLiveSyncSettingTab.titleHiddenFiles": "隐藏文件",
     "obsidianLiveSyncSettingTab.titleLogging": "日志",
+    "obsidianLiveSyncSettingTab.titleMaintenanceAndRecovery": "维护与恢复",
     "obsidianLiveSyncSettingTab.titleMinioS3R2": "MinIO、S3、R2",
     "obsidianLiveSyncSettingTab.titleNotification": "通知",
     "obsidianLiveSyncSettingTab.titleOnlineTips": "在线提示",
@@ -504,6 +780,7 @@
     "obsidianLiveSyncSettingTab.titleRemoteServer": "远端服务器",
     "obsidianLiveSyncSettingTab.titleReset": "重置",
     "obsidianLiveSyncSettingTab.titleSetupOtherDevices": "设置其他设备",
+    "obsidianLiveSyncSettingTab.titleSynchronisation": "同步",
     "obsidianLiveSyncSettingTab.titleSynchronizationMethod": "同步方式",
     "obsidianLiveSyncSettingTab.titleSynchronizationPreset": "同步预设",
     "obsidianLiveSyncSettingTab.titleSyncSettings": "同步设置",
@@ -511,16 +788,30 @@
     "obsidianLiveSyncSettingTab.titleUpdateThinning": "更新精简",
     "obsidianLiveSyncSettingTab.warnCorsOriginUnmatched": "⚠ CORS 源不匹配 {from}->{to}",
     "obsidianLiveSyncSettingTab.warnNoAdmin": "⚠ 您没有管理员权限",
+    "Of course, we can back up the data before proceeding.": "当然，我们可以先备份数据再继续。",
+    "Off": "关闭",
     "Ok": "确定",
     "Old Algorithm": "旧算法",
+    "Older (${diff})": "较旧（${diff}）",
     "Older fallback (Slow, W/O WebAssembly)": "旧版回退（较慢，无 WebAssembly）",
+    "On": "开启",
+    "On the source device, from the command palette, run the 'Show settings as a QR code' command.": "在源设备上，从命令面板运行「Show settings as a QR code」命令。",
+    "On the source device, open Obsidian.": "在源设备上打开 Obsidian。",
+    "On this device, please keep this Vault open.": "请在本设备上保持此库处于打开状态。",
+    "On this device, switch to the camera app or use a QR code scanner to scan the displayed QR code.": "在本设备上切换到相机应用，或使用二维码扫描器扫描显示的二维码。",
     "Open": "打开",
+    "Open connection": "打开连接",
+    "Open P2P Setup...": "打开 P2P 设置…",
     "Open the dialog": "打开对话框",
+    "Other files": "其他文件",
     "Overwrite": "覆盖",
+    "Overwrite all with remote files": "全部用远程文件覆盖",
     "Overwrite patterns": "覆盖模式",
     "Overwrite remote": "覆盖远端",
     "Overwrite remote with local DB and passphrase.": "使用本地数据库和密码短语覆盖远端。",
     "Overwrite Server Data with This Device's Files": "用本设备文件覆盖服务器数据",
+    "P2P Configuration": "P2P 配置",
+    "P2P Status": "P2P 状态",
     "P2P.AskPassphraseForDecrypt": "远程对等方共享了配置，请输入密码短语以解密配置",
     "P2P.AskPassphraseForShare": "远程对等方请求此设备配置，请输入密码短语以共享配置。你可以通过取消此对话框来忽略此请求",
     "P2P.DisabledButNeed": "%{title_p2p_sync} 已禁用。你确定要启用它吗？",
@@ -531,92 +822,127 @@
     "P2P.Note.important_note": "The Experimental Implementation of the Peer-to-Peer Replicator.",
     "P2P.Note.important_note_sub": "This feature is still in the experimental stage. Please be aware that this feature may not work as expected. Furthermore, it may have some bugs, security issues, and other issues. Please use this feature at your own risk. Please contribute to the development of this feature.",
     "P2P.Note.Summary": "What is this  feature? (and some important notes, please read once)",
-    "P2P.NotEnabled": "%{title_p2p_sync} is not enabled. We cannot open a new connection.",
-    "P2P.P2PReplication": "%{P2P} Replication",
+    "P2P.NotEnabled": "%{title_p2p_sync} 未启用，无法建立新连接。",
+    "P2P.P2PReplication": "%{P2P} 复制",
     "P2P.PaneTitle": "%{long_p2p_sync}",
-    "P2P.ReplicatorInstanceMissing": "P2P Sync replicator is not found, possibly not have been configured or enabled.",
-    "P2P.SeemsOffline": "Peer ${name} seems offline, skipped.",
-    "P2P.SyncAlreadyRunning": "P2P Sync is already running.",
-    "P2P.SyncCompleted": "P2P Sync completed.",
-    "P2P.SyncStartedWith": "P2P Sync with ${name} have been started.",
+    "P2P.ReplicatorInstanceMissing": "未找到 P2P 同步复制器，可能尚未配置或未启用。",
+    "P2P.SeemsOffline": "对等方 ${name} 似乎处于离线状态，已跳过。",
+    "P2P.SyncAlreadyRunning": "P2P 同步已在运行。",
+    "P2P.SyncCompleted": "P2P 同步已完成。",
+    "P2P.SyncStartedWith": "已开始与 ${name} 的 P2P 同步。",
     "paneMaintenance.markDeviceResolvedAfterBackup": "请在完成备份后将此设备标记为已处理。",
     "paneMaintenance.remoteLockedAndDeviceNotAccepted": "远端数据库已锁定，且此设备尚未被接受。",
     "paneMaintenance.remoteLockedResolvedDevice": "远端数据库已锁定，但此设备已被接受。",
     "paneMaintenance.unlockDatabaseReady": "现在可以解锁数据库。",
     "Passphrase": "密码",
+    "Passphrase is required.": "密码短语是必填项。",
     "Passphrase of sensitive configuration items": "敏感配置项的密码",
     "password": "密码",
     "Password": "密码",
     "Paste a connection string": "粘贴连接字符串",
     "Paste the Setup URI generated from one of your active devices.": "粘贴从一台已在使用的设备上生成的 Setup URI。",
+    "Path": "路径",
     "Path Obfuscation": "路径混淆",
     "Patterns to match files for overwriting instead of merging": "用于匹配需覆盖而非合并文件的模式",
     "Patterns to match files for syncing": "用于匹配同步文件的模式",
+    "Peer ID:": "对等方 ID：",
+    "Peer to Peer Replicator": "点对点复制器",
     "Peer-to-Peer only": "仅 Peer-to-Peer",
     "Peer-to-Peer Synchronisation": "点对点同步",
+    "Peers": "对等方",
     "Per-file-saved customization sync": "按文件保存的自定义同步",
     "Perform": "执行",
     "Perform cleanup": "执行清理",
     "Perform Garbage Collection": "执行垃圾回收",
     "Perform Garbage Collection to remove unused chunks and reduce database size.": "执行垃圾回收以清理未使用的 chunks 并减小数据库体积。",
     "Periodic Sync interval": "定期同步间隔",
+    "PERMANENT": "永久",
     "Pick a file to resolve conflict": "选择要解决冲突的文件",
+    "Pick a file to show history": "选择一个文件以显示历史记录",
+    "Please be aware that the End-to-End Encryption passphrase is not validated until the synchronisation process actually commences. This is a security measure designed to protect your data.": "请注意，端到端加密密码短语要等到同步过程真正开始后才会被校验。这是为保护你的数据而设计的安全措施。",
+    "Please configure your end-to-end encryption settings.": "请配置你的端到端加密设置。",
     "Please disable 'Read chunks online' in settings to use Garbage Collection.": "要使用垃圾回收，请在设置中禁用“Read chunks online”。",
     "Please enable 'Compute revisions for chunks' in settings to use Garbage Collection.": "要使用垃圾回收，请在设置中启用“Compute revisions for chunks”。",
+    "Please enter the CouchDB server information below.": "请在下方填写 CouchDB 服务器信息。",
+    "Please enter the details required to connect to your S3/MinIO/R2 compatible object storage service.": "请填写连接到你的 S3/MinIO/R2 兼容对象存储服务所需的信息。",
+    "Please enter the Peer-to-Peer Synchronisation information below.": "请在下方填写点对点同步信息。",
+    "Please enter the Setup URI that was generated during server installation or on another device, along with the vault passphrase.": "请输入在服务器安装时或在其他设备上生成的设置 URI，以及库的密码短语。",
+    "Please follow the steps below to import settings from your existing device.": "请按以下步骤从你现有的设备导入设置。",
+    "PLEASE NOTE": "请注意",
     "Please select 'Cancel' explicitly to cancel this operation.": "如需取消此操作，请明确选择“取消”。",
     "Please select a method to import the settings from another device.": "请选择一种从其他设备导入设置的方法。",
+    "Please select an active P2P remote configuration to change P2P sync targets.": "请选择一个生效的 P2P 远端配置以更改 P2P 同步目标。",
     "Please select an option to proceed": "请选择一个选项以继续",
+    "Please select the button below to restart and proceed to the data fetching confirmation.": "请点击下方按钮重启，然后进入数据获取确认。",
+    "Please select the button below to restart and proceed to the final confirmation.": "请点击下方按钮重启，然后进入最终确认。",
     "Please select the type of server to which you are connecting.": "请选择你要连接的服务器类型。",
+    "Please select your situation.": "请选择你的情况。",
     "Please set device name to identify this device. This name should be unique among your devices. While not configured, we cannot enable this feature.": "请设置设备名称以标识此设备。该名称在你的所有设备之间应保持唯一；未配置前无法启用此功能。",
     "Please set this device name": "请设置此设备名称",
+    "Please understand that this is intended behaviour.": "请注意这是预期行为。",
+    "Please use V2, V1 is deprecated and will be removed in the future, It was not a very appropriate algorithm. Only for compatibility V1 is kept.": "请使用 V2。V1 已被弃用，将来会被移除，它并不是非常合适的算法。仅出于兼容性而保留 V1。",
     "Plug-in version": "插件版本",
+    "Plugins": "插件",
     "Prepare the 'report' to create an issue": "准备 '报告' 以创建问题单",
     "Presets": "预设",
+    "Prevent fetching configuration from server": "阻止从服务器获取配置",
+    "Proceed": "继续",
     "Proceed Garbage Collection": "继续执行垃圾回收",
+    "Proceed to the next step.": "继续下一步。",
     "Proceed with Setup URI": "继续使用 Setup URI",
     "Proceeding with Garbage Collection, ignoring missing nodes.": "正在继续执行垃圾回收，并忽略缺失节点。",
     "Proceeding with Garbage Collection.": "正在执行垃圾回收。",
+    "Process files even if seems to be corrupted": "即使文件疑似损坏也进行处理",
     "Process small files in the foreground": "在前台处理小文件",
     "Progress": "进度",
     "Property Encryption": "属性加密",
     "PureJS fallback  (Fast, W/O WebAssembly)": "PureJS 回退（快速，无 WebAssembly）",
     "Purge all download/upload cache.": "清除所有下载／上传缓存。",
     "Purge all journal counter": "清除所有日志计数器",
+    "Reboot to re-run the process": "重启以重新运行此流程",
     "Rebuild local and remote database with local files.": "使用本地文件重建本地和远端数据库。",
     "Rebuilding Operations (Remote Only)": "重建操作（仅远端）",
+    "Recovery and Repair": "恢复与修复",
     "Recreate all": "全部重建",
     "Recreate missing chunks for all files": "为所有文件重建缺失的 chunks",
-    "RedFlag.Fetch.Method.Desc": "How do you want to fetch?\n- %{RedFlag.Fetch.Method.FetchSafer}.\n  **Low Traffic**, **High CPU**, **Low Risk**\n  Recommended if ...\n  - Files possibly inconsistent\n  - Files were not so much\n- %{RedFlag.Fetch.Method.FetchSmoother}.\n  **Low Traffic**, **Moderate CPU**, **Low to Moderate Risk**\n  Recommended if ...\n  - Files probably consistent\n  - You have a lot of files.\n- %{RedFlag.Fetch.Method.FetchTraditional}.\n  **High Traffic**, **Low CPU**, **Low to Moderate Risk**\n\n>[!INFO]- Details\n> ## %{RedFlag.Fetch.Method.FetchSafer}.\n> **Low Traffic**, **High CPU**, **Low Risk**\n> This option first creates a local database using existing local files before fetching data from the remote source.\n> If matching files exist both locally and remotely, only the differences between them will be transferred.\n> However, files present in both locations will initially be handled as conflicted files. They will be resolved automatically if they are not actually conflicted, but this process may take time.\n> This is generally the safest method, minimizing data loss risk.\n> ## %{RedFlag.Fetch.Method.FetchSmoother}.\n> **Low Traffic**, **Moderate CPU**, **Low to Moderate Risk** (depending operation)\n> This option first creates chunks from local files for the database, then fetches data. Consequently, only chunks missing locally are transferred. However, all metadata is taken from the remote source.\n> Local files are then compared against this metadata at launch. The content considered newer will overwrite the older one (by modified time). This outcome is then synchronised back to the remote database.\n> This is generally safe if local files are genuinely the latest timestamp. However, it can cause problems if a file has a newer timestamp but older content (like the initial `welcome.md`).\n> This uses less CPU and faster than \"%{RedFlag.Fetch.Method.FetchSafer}\", but it may lead to data loss if not used carefully.\n> ## %{RedFlag.Fetch.Method.FetchTraditional}.\n> **High Traffic**, **Low CPU**, **Low to Moderate Risk** (depending operation)\n> All things will be fetched from the remote.\n> Similar to the %{RedFlag.Fetch.Method.FetchSmoother}, but all chunks are fetched from the remote source.\n> This is the most traditional way to fetch, typically consuming the most network traffic and time. It also carries a similar risk of overwriting remote files to the '%{RedFlag.Fetch.Method.FetchSmoother}' option.\n> However, it is often considered the most stable method because it is the longest-established and most straightforward approach.",
-    "RedFlag.Fetch.Method.FetchSafer": "Create a local database once before fetching",
-    "RedFlag.Fetch.Method.FetchSmoother": "Create local file chunks before fetching",
-    "RedFlag.Fetch.Method.FetchTraditional": "Fetch everything from the remote",
-    "RedFlag.Fetch.Method.Title": "How do you want to fetch?",
-    "RedFlag.FetchRemoteConfig.Buttons.Cancel": "No, use local settings",
-    "RedFlag.FetchRemoteConfig.Buttons.Fetch": "Yes, fetch and apply remote settings",
-    "RedFlag.FetchRemoteConfig.Message": "Do you want to fetch and apply remotely stored preference settings to the device?",
-    "RedFlag.FetchRemoteConfig.Title": "Fetch Remote Configuration",
+    "RedFlag.Fetch.Method.Desc": "你希望如何获取？\n- %{RedFlag.Fetch.Method.FetchSafer}。\n  **低流量**，**高 CPU**，**低风险**\n  在以下情况下推荐使用：\n  - 文件可能不一致\n  - 文件数量不多\n- %{RedFlag.Fetch.Method.FetchSmoother}。\n  **低流量**，**中等 CPU**，**低到中等风险**\n  在以下情况下推荐使用：\n  - 文件基本一致\n  - 你有大量文件。\n- %{RedFlag.Fetch.Method.FetchTraditional}。\n  **高流量**，**低 CPU**，**低到中等风险**\n\n>[!INFO]- 详情\n> ## %{RedFlag.Fetch.Method.FetchSafer}。\n> **低流量**，**高 CPU**，**低风险**\n> 此选项会先利用现有的本地文件创建本地数据库，然后再从远程源获取数据。\n> 如果本地和远程存在相同的文件，则只会传输两者之间的差异。\n> 但是，两边都存在的文件最初会被视为冲突文件。如果它们实际上并无冲突，将会被自动解决，不过这一过程可能需要一些时间。\n> 这通常是最安全的方法，能将数据丢失风险降到最低。\n> ## %{RedFlag.Fetch.Method.FetchSmoother}。\n> **低流量**，**中等 CPU**，**低到中等风险**（视具体操作而定）\n> 此选项会先根据本地文件为数据库创建数据块，然后再获取数据。因此，只会传输本地缺少的数据块。但是，所有元数据都取自远程源。\n> 启动时，系统会将本地文件与这些元数据进行比较。被认为更新的内容（按修改时间判断）将覆盖较旧的版本。随后，这一结果会同步回远程数据库。\n> 如果本地文件的时间戳确实是最新的，这通常是安全的。但如果某个文件的时间戳较新、内容却较旧（例如最初的 `welcome.md`），就可能引发问题。\n> 这种方式比“%{RedFlag.Fetch.Method.FetchSafer}”占用更少的 CPU、速度更快，但如果使用不当，可能会导致数据丢失。\n> ## %{RedFlag.Fetch.Method.FetchTraditional}。\n> **高流量**，**低 CPU**，**低到中等风险**（视具体操作而定）\n> 所有内容都将从远程获取。\n> 与 %{RedFlag.Fetch.Method.FetchSmoother} 相似，但所有数据块都从远程源获取。\n> 这是最传统的获取方式，通常消耗最多的网络流量和时间。与“%{RedFlag.Fetch.Method.FetchSmoother}”选项类似，它同样存在覆盖远程文件的风险。\n> 不过，它通常被认为是最稳定的方法，因为它是历史最悠久、最直接的做法。",
+    "RedFlag.Fetch.Method.FetchSafer": "获取前先创建一次本地数据库",
+    "RedFlag.Fetch.Method.FetchSmoother": "获取前先创建本地文件的数据块",
+    "RedFlag.Fetch.Method.FetchTraditional": "从远程获取全部内容",
+    "RedFlag.Fetch.Method.Title": "你想如何获取？",
+    "RedFlag.FetchRemoteConfig.Buttons.Cancel": "否，使用本地设置",
+    "RedFlag.FetchRemoteConfig.Buttons.Fetch": "是，获取并应用远程设置",
+    "RedFlag.FetchRemoteConfig.Message": "是否要获取远程保存的偏好设置，并将其应用到此设备？",
+    "RedFlag.FetchRemoteConfig.Title": "获取远程配置",
     "Reduces storage space by discarding all non-latest revisions. This requires the same amount of free space on the remote server and the local client.": "通过丢弃所有非最新版本来减少存储空间。这需要远程服务器和本地客户端具备相同数量的可用空间。",
     "Reducing the frequency with which on-disk changes are reflected into the DB": "降低将磁盘上的更改反映到数据库中的频率",
+    "Refresh": "刷新",
     "Region": "区域",
+    "Relay settings": "中继设置",
+    "Reload": "重新加载",
     "Remediation": "修复设置",
     "Remediation Setting Changed": "修复设置已更改",
     "Remote Database Tweak (In sunset)": "远端数据库调优（逐步淘汰）",
     "Remote Databases": "远端数据库",
     "Remote name": "远端名称",
+    "Remote only": "仅远端",
     "Remote server type": "远程服务器类型",
     "Remote Type": "远程类型",
     "Rename": "重命名",
-    "Replicator.Dialogue.Locked.Action.Dismiss": "Cancel for reconfirmation",
-    "Replicator.Dialogue.Locked.Action.Fetch": "Reset Synchronisation on This Device",
-    "Replicator.Dialogue.Locked.Action.Unlock": "Unlock the remote database",
+    "Replicate now": "立即复制",
+    "Replicating": "复制中",
+    "Replicating...": "复制中…",
+    "Replicator.Dialogue.Locked.Action.Dismiss": "取消并重新确认",
+    "Replicator.Dialogue.Locked.Action.Fetch": "重置此设备上的同步",
+    "Replicator.Dialogue.Locked.Action.Unlock": "解锁远程数据库",
     "Replicator.Dialogue.Locked.Message": "Remote database is locked. This is due to a rebuild on one of the terminals.\nThe device is therefore asked to withhold the connection to avoid database corruption.\n\nThere are three options that we can do:\n\n- %{Replicator.Dialogue.Locked.Action.Fetch}\n  The most preferred and reliable way. This will dispose the local database once, and fetch all from the remote database again, In most case, we can perform this safely. However, it takes some time and should be done in stable network.\n- %{Replicator.Dialogue.Locked.Action.Unlock}\n  This method can only be used if we are already reliably synchronised by other replication methods. This does not simply mean that we have the same files. If you are not sure, you should avoid it.\n- %{Replicator.Dialogue.Locked.Action.Dismiss}\n    This will cancel the operation. And we will asked again on next request.\n",
-    "Replicator.Dialogue.Locked.Message.Fetch": "Fetch all has been scheduled. Plug-in will be restarted to perform it.",
-    "Replicator.Dialogue.Locked.Message.Unlocked": "The remote database has been unlocked. Please retry the operation.",
-    "Replicator.Dialogue.Locked.Title": "Locked",
-    "Replicator.Message.Cleaned": "Database cleaning up is in process. replication has been cancelled",
-    "Replicator.Message.InitialiseFatalError": "No replicator is available, this is the fatal error.",
-    "Replicator.Message.Pending": "Some file events are pending. Replication has been cancelled.",
-    "Replicator.Message.SomeModuleFailed": "Replication has been cancelled by some module failure",
+    "Replicator.Dialogue.Locked.Message.Fetch": "已安排获取全部内容。插件将重启以执行该操作。",
+    "Replicator.Dialogue.Locked.Message.Unlocked": "远程数据库已解锁。请重试该操作。",
+    "Replicator.Dialogue.Locked.Title": "已锁定",
+    "Replicator.Message.Cleaned": "数据库清理正在进行中，复制已取消。",
+    "Replicator.Message.InitialiseFatalError": "没有可用的复制器，这是一个致命错误。",
+    "Replicator.Message.Pending": "部分文件事件仍在等待处理。复制已取消。",
+    "Replicator.Message.SomeModuleFailed": "由于某个模块出错，复制已取消。",
     "Replicator.Message.VersionUpFlash": "An update has been detected. Please open the Settings dialogue and check the Change Log. Replication has been cancelled.",
     "Requires restart of Obsidian": "需要重启 Obsidian",
     "Requires restart of Obsidian.": "需要重启 Obsidian ",
@@ -628,6 +954,7 @@
     "Reset": "重置",
     "Reset all": "全部重置",
     "Reset all journal counter": "重置所有日志计数器",
+    "Reset and Resume Synchronisation": "重置并恢复同步",
     "Reset journal received history": "重置日志接收历史",
     "Reset journal sent history": "重置日志发送历史",
     "Reset notification threshold and check the remote database usage": "重置通知阈值并检查远程数据库使用情况",
@@ -640,13 +967,29 @@
     "Resolve all conflicted files": "解决所有冲突文件",
     "Resolve All conflicted files by the newer one": "将所有冲突文件解析为较新的版本",
     "Resolve all conflicted files by the newer one. Caution: This will overwrite the older one, and cannot resurrect the overwritten one.": "将所有冲突文件统一保留较新的版本。注意：这会覆盖较旧的版本，且被覆盖的内容无法恢复。",
+    "Restart and Fetch Data": "重启并获取数据",
+    "Restart and Initialise Server": "重启并初始化服务器",
     "Restart Now": "立即重启",
+    "Restarting Obsidian is strongly recommended. Until restart, some changes may not take effect, and display may be inconsistent. Are you sure to restart now?": "强烈建议重启 Obsidian。在重启之前，部分更改可能不会生效，显示也可能不一致。确定现在重启吗？",
     "Restore or reconstruct local database from remote.": "从远端恢复或重建本地数据库。",
+    "Rev": "修订",
+    "Revert changes": "还原更改",
+    "Revoke": "撤销",
+    "Room ID": "房间 ID",
+    "Room ID suffix:": "房间 ID 后缀：",
+    "Rotation Duration": "令牌轮换时长",
     "Run Doctor": "立即诊断",
+    "S3/MinIO/R2 Configuration": "S3/MinIO/R2 配置",
     "S3/MinIO/R2 Object Storage": "S3/MinIO/R2 对象存储",
+    "Same": "相同",
+    "Same or local only": "相同或仅本地",
+    "Save and Apply": "保存并应用",
     "Save settings to a markdown file. You will be notified when new settings arrive. You can set different files by the platform.": "将设置保存到一个 Markdown 文件中。当新设置到达时,您将收到通知。您可以根据平台设置不同的文件 ",
+    "Save without connecting": "不连接直接保存",
     "Saving will be performed forcefully after this number of seconds.": "在此秒数后将强制执行保存 ",
+    "Saving without a successful connection test keeps this profile, but automatic synchronisation may fail until the connection is corrected.": "未通过连接测试就保存会保留此档案，但在连接修正之前，自动同步可能会失败。",
     "Scan a QR Code (Recommended for mobile)": "扫描二维码（移动端推荐）",
+    "Scan changes": "扫描变更",
     "Scan changes on customization sync": "在自定义同步时扫描更改",
     "Scan customization automatically": "自动扫描自定义设置",
     "Scan customization before replicating.": "在复制前扫描自定义设置 ",
@@ -655,17 +998,28 @@
     "Scan for Broken files": "扫描损坏文件",
     "Scan for hidden files before replication": "复制前扫描隐藏文件",
     "Scan hidden files periodically": "定期扫描隐藏文件",
+    "Scan QR Code": "扫描二维码",
     "Scan the QR code displayed on an active device using this device's camera.": "使用当前设备的摄像头扫描另一台已在使用设备上显示的二维码。",
     "Schedule and Restart": "安排并重启",
     "Scram Switches": "紧急开关",
     "Scram!": "紧急处置",
     "Seconds, 0 to disable": "秒,0为禁用",
     "Seconds. Saving to the local database will be delayed until this value after we stop typing or saving.": "秒。在我们停止输入或保存后,保存到本地数据库将延迟此值 ",
-    "Secret Key": "Secret Key",
+    "Secret Access Key": "私有访问密钥",
+    "Secret Key": "私有密钥",
+    "Select active P2P remote": "选择生效的 P2P 远端",
+    "Select All Shiny": "全选 Shiny",
+    "Select Flagged Shiny": "选择已标记的 Shiny",
+    "Select P2P remote...": "选择 P2P 远端…",
     "Select the database adapter to use.": "选择要使用的数据库适配器。",
+    "Selecting this option will result in the current data on this device being used to initialise the server. Any existing data on the server will be completely overwritten.": "选择此选项后，将用本设备的当前数据来初始化服务器。服务器上现有的数据将被完全覆盖。",
+    "Selecting this option will result in this device joining the existing server. You need to fetching the existing synchronisation data from the server to this device.": "选择此选项后，本设备将加入现有服务器。你需要把服务器上已有的同步数据获取到本设备。",
+    "Selective": "选择性",
     "Send": "发送",
     "Send chunks": "发送 chunks",
+    "SENDING": "发送中",
     "Server URI": "服务器 URI",
+    "SESSION": "会话",
     "Setting.GenerateKeyPair.Desc": "我们已经生成了一组密钥对！\n\n注意：这组密钥对之后将不会再次显示。请务必妥善保管；如果丢失，你需要重新生成新的密钥对。\n注意 2：公钥采用 spki 格式，私钥采用 pkcs8 格式。为方便复制，公钥中的换行会被转换为 `\\n`。\n注意 3：公钥应配置在远端数据库中，私钥应配置在本地设备上。\n\n>[!仅限本人查看]-\n> <div class=\"sls-keypair\">\n>\n> ### 公钥\n> ```\n${public_key}\n> ```\n>\n> ### 私钥\n> ```\n${private_key}\n> ```\n>\n> </div>\n\n>[!整段复制]-\n>\n> <div class=\"sls-keypair\">\n>\n> ```\n${public_key}\n${private_key}\n> ```\n>\n> </div>",
     "Setting.GenerateKeyPair.Title": "已生成新的密钥对！",
     "Setting.TroubleShooting": "故障排除",
@@ -673,25 +1027,35 @@
     "Setting.TroubleShooting.Doctor.Desc": "检测系统中不合理的设置。（与迁移期间逻辑相同）",
     "Setting.TroubleShooting.ScanBrokenFiles": "扫描损坏或异常的文件",
     "Setting.TroubleShooting.ScanBrokenFiles.Desc": "扫描数据库中未正确存储的文件。",
-    "SettingTab.Message.AskRebuild": "Your changes require fetching from the remote database. Do you want to proceed?",
+    "SettingService.ConfigurationCouldNotBeDecrypted": "无法解密现有配置。配置密钥未更改。",
+    "SettingService.ConfigurationEncryptionSaveFailed": "无法保存配置加密。请在重试前检查已保存的设置和设备密钥。",
+    "SettingService.ConfigurationPassphraseCancelled": "配置密码短语的输入已取消或不可用。启动已停止，已保存的设置已保留。",
+    "SettingService.ConfigurationPassphraseDeviceLocalDescription": "此密码短语只保留在此设备上。当其他设备需要在没有已保存密钥的情况下解密受保护的设置时，请在启动时输入相同的密码短语。",
+    "SettingService.ConfigurationPassphraseRetryTitle": "无法解密配置。请重新输入配置密码短语。",
+    "SettingService.ConfigurationPassphraseRollbackFailed": "写入失败后，无法恢复配置密码短语。请在重试前检查已保存的设置和设备密钥。",
+    "SettingService.ConfigurationPassphraseTitle": "配置密码短语",
+    "SettingTab.Message.AskRebuild": "你的更改需要从远程数据库获取数据。是否继续？",
+    "Setup Complete: Preparing to Fetch Synchronisation Data": "设置完成：正在准备获取同步数据",
+    "Setup Complete: Preparing to Initialise Server": "设置完成：正在准备初始化服务器",
     "Setup URI dialog cancelled.": "Setup URI 对话框已取消。",
-    "Setup.Apply.Buttons.ApplyAndFetch": "Apply and Fetch",
-    "Setup.Apply.Buttons.ApplyAndMerge": "Apply and Merge",
-    "Setup.Apply.Buttons.ApplyAndRebuild": "Apply and Rebuild",
-    "Setup.Apply.Buttons.Cancel": "Discard and Cancel",
-    "Setup.Apply.Buttons.OnlyApply": "Only Apply",
-    "Setup.Apply.Message": "The new configuration is ready. Let us proceed to apply it.\nThere are several ways to apply this:\n\n- Apply and Fetch\n  Configure this device as a new client. After applying, synchronise from the remote server.\n- Apply and Merge\n  Configure on a device that already has the file. It processes the local files and transfers the differences. Conflicts may arise.\n- Apply and Rebuild\n  Rebuild the remote using local files. This is typically done if the server becomes corrupted or we wish to start from scratch.\n  Other devices will be locked and required to re-fetch.\n- Only Apply\n  Apply only. Conflicts may arise if a rebuild is required.",
-    "Setup.Apply.Title": "Apply new configuration from the ${method}",
-    "Setup.Apply.WarningRebuildRecommended": "NOTE: after adjusting the settings, it has been determined that a rebuild is required; Just Import is not recommended.",
-    "Setup.Doctor.Buttons.No": "No, please use the settings in the URI as is",
-    "Setup.Doctor.Buttons.Yes": "Yes, please consult the doctor",
-    "Setup.Doctor.Message": "Self-hosted LiveSync has gradually become longer in history and some recommended settings have changed.\n\nNow, setup is a very good time to do this.\n\nDo you want to run Doctor to check if the imported settings are optimal compared to the latest state?",
-    "Setup.Doctor.Title": "Do you want to consult the doctor?",
-    "Setup.FetchRemoteConf.Buttons.Fetch": "Yes, please fetch the configuration",
-    "Setup.FetchRemoteConf.Buttons.Skip": "No, please use the settings in the URI",
-    "Setup.FetchRemoteConf.Message": "If we have already synchronised once with another device, the remote database stores the suitable configuration values between the synchronised devices. The plug-in would like to retrieve them for robust configuration.\n\nHowever, we have to make sure the one thing. Are we currently in a situation where we can access the network safely and retrieve the settings?\n\nNote: Mostly, you are safe to do this, that your remote database is hosted with a SSL certificate, and your network is not compromised.",
-    "Setup.FetchRemoteConf.Title": "Fetch configuration from remote database?",
-    "Setup.QRCode": "We have generated a QR code to transfer the settings. Please scan the QR code with your phone or other device.\nNote: The QR code is not encrypted, so be careful to open this.\n\n>[!FOR YOUR EYES ONLY]-\n> <div class=\"sls-qr\">${qr_image}</div>",
+    "Setup-URI": "设置 URI",
+    "Setup.Apply.Buttons.ApplyAndFetch": "应用并获取",
+    "Setup.Apply.Buttons.ApplyAndMerge": "应用并合并",
+    "Setup.Apply.Buttons.ApplyAndRebuild": "应用并重建",
+    "Setup.Apply.Buttons.Cancel": "丢弃并取消",
+    "Setup.Apply.Buttons.OnlyApply": "仅应用",
+    "Setup.Apply.Message": "新配置已准备就绪，让我们继续应用它。\n应用此配置有以下几种方式：\n\n- 应用并获取\n  将此设备配置为新客户端。应用后，从远程服务器同步。\n- 应用并合并\n  在已有文件的设备上进行配置。它会处理本地文件并传输差异。可能会出现冲突。\n- 应用并重建\n  使用本地文件重建远程。通常在服务器损坏或希望从头开始时使用。\n  其他设备将被锁定，并需要重新获取。\n- 仅应用\n  仅应用配置。如果需要重建，可能会出现冲突。",
+    "Setup.Apply.Title": "从 ${method} 应用新配置",
+    "Setup.Apply.WarningRebuildRecommended": "注意：调整设置后，已判定需要重建；不推荐仅导入。",
+    "Setup.Doctor.Buttons.No": "否，请按原样使用 URI 中的设置",
+    "Setup.Doctor.Buttons.Yes": "是，请运行诊断",
+    "Setup.Doctor.Message": "Self-hosted LiveSync 已经历经多次演进，一些推荐设置也随之发生了变化。\n\n现在正值设置阶段，是进行检查的好时机。\n\n你要运行诊断，检查导入的设置相对于最新状态是否最优吗？",
+    "Setup.Doctor.Title": "要运行诊断吗？",
+    "Setup.FetchRemoteConf.Buttons.Fetch": "是，请获取配置",
+    "Setup.FetchRemoteConf.Buttons.Skip": "否，请使用 URI 中的设置",
+    "Setup.FetchRemoteConf.Message": "如果我们之前已经与另一台设备同步过，远程数据库会保存已同步设备之间适用的配置值。插件希望获取这些值，以便进行更可靠的配置。\n\n但有一点必须确认：我们当前是否处于可以安全访问网络并获取这些设置的环境中？\n\n注意：通常情况下，只要你的远程数据库使用了 SSL 证书，且网络未被入侵，执行此操作就是安全的。",
+    "Setup.FetchRemoteConf.Title": "要从远程数据库获取配置吗？",
+    "Setup.QRCode": "我们已生成用于传输设置的二维码。请使用手机或其他设备扫描该二维码。\n注意：此二维码未加密，请谨慎打开。\n\n>[!FOR YOUR EYES ONLY]-\n> <div class=\"sls-qr\">${qr_image}</div>",
     "Setup.RemoteE2EE.AdvancedTitle": "高级",
     "Setup.RemoteE2EE.AlgorithmWarning": "更改加密算法会导致之前使用其他算法加密的数据无法访问。请确保所有设备都配置为使用同一算法，以保持对数据的访问能力。",
     "Setup.RemoteE2EE.ButtonCancel": "取消",
@@ -736,22 +1100,42 @@
     "Should we prompt you about conflicting files when a file is opened?": "当文件打开时,是否提示冲突文件？",
     "Should we prompt you for every single merge, even if we can safely merge automatcially?": "即使我们可以安全地自动合并,是否也应该为每一次合并提示您？",
     "Show full banner": "显示完整横幅",
+    "Show history": "显示历史记录",
     "Show icon only": "仅显示图标",
     "Show only notifications": "仅显示通知",
+    "Show password": "显示密码",
     "Show status as icons only": "仅以图标显示状态",
     "Show status icon instead of file warnings banner": "显示状态图标，而非文件警告横幅",
     "Show status inside the editor": "在编辑器内显示状态",
     "Show status on the status bar": "在状态栏上显示状态",
     "Show verbose log. Please enable if you report an issue.": "显示详细日志。如果您报告问题,请启用此选项 ",
+    "Signaling Server Connection": "信令服务器连接",
+    "Signalling Relays": "信令中继",
+    "Signalling Status": "信令状态",
+    "Since you have chosen to overwrite all local files with remote data, **how would you like to handle local files that are not present in the remote database?**\n\n- **${DELETE_ALL}**: Local-only files and remote-deleted files will be removed.\n  This option will make your local vault exactly the same as the remote database, but please make sure you have a backup if there is any important data in your vault.\n- **${DELETE_NONE}**: All existing local files will be preserved.\n  This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.": "由于你选择了用远程数据覆盖所有本地文件，**对于远程数据库中不存在的本地文件，你希望如何处理？**\n\n- **${DELETE_ALL}**：仅存在于本地的文件和在远程已被删除的文件将被移除。\n  此选项会让你的本地库与远程数据库完全一致，但如果库中有重要数据，请务必先做好备份。\n- **${DELETE_NONE}**：保留所有现有的本地文件。\n  此选项会保留你所有的本地文件，但如果某些文件仅存在于本地而不在远程，可能会产生重复文件。同步完成后，你可以手动清理这些重复文件。",
+    "Skip and close": "跳过并关闭",
+    "Snippets": "代码片段",
     "Some devices have differing progress values (max: ${maxProgress}, min: ${minProgress}).\nThis may indicate that some devices have not completed synchronisation, which could lead to conflicts. Strongly recommend confirming that all devices are synchronised before proceeding.": "某些设备的进度值不同（最大：${maxProgress}，最小：${minProgress}）。\n这可能表示某些设备尚未完成同步，从而可能引发冲突。强烈建议在继续之前先确认所有设备都已同步。",
+    "Some files failed to synchronise. What would you like to do?": "部分文件同步失败。你希望如何处理？",
+    "Start Broadcasting": "开始广播",
+    "Start change-broadcasting on Connect": "连接时开始广播变更",
+    "Start Sync & Close": "开始同步并关闭",
     "Starts synchronisation when a file is saved.": "当文件保存时启动同步 ",
+    "Stat": "统计",
+    "Stats": "统计",
+    "Stop ⚡": "停止 ⚡",
+    "Stop Broadcasting": "停止广播",
     "Stop reflecting database changes to storage files.": "停止将数据库更改反映到存储文件 ",
     "Stop watching for file changes.": "停止监视文件更改 ",
+    "Storage -> Database": "存储 → 数据库",
+    "Strongly Recommended": "强烈推荐",
+    "Subject (whoami)": "主体（whoami）",
     "Suppress notification of hidden files change": "暂停隐藏文件更改的通知",
     "Suspend database reflecting": "暂停数据库反映",
     "Suspend file watching": "暂停文件监视",
     "Switch to IDB": "切换到 IDB",
     "Switch to IndexedDB": "切换到 IndexedDB",
+    "Sync": "同步",
     "Sync after merging file": "合并文件后同步",
     "Sync automatically after merging files": "合并文件后自动同步",
     "Sync Mode": "同步模式",
@@ -759,48 +1143,107 @@
     "Sync on File Open": "打开文件时同步",
     "Sync on Save": "保存时同步",
     "Sync on Startup": "启动时同步",
+    "Sync once": "同步一次",
+    "Synchronisation Issues Detected": "检测到同步问题",
     "Synchronisation utilising journal files. You must have set up an S3/MinIO/R2 compatible object storage.": "通过日志文件进行同步。你需要事先部署好兼容 S3/MinIO/R2 的对象存储服务。",
     "Synchronising files": "同步文件",
     "Syncing": "同步中",
+    "Syncing...": "同步中…",
     "Target patterns": "目标模式",
+    "Test connection and save": "测试连接并保存",
+    "Test Settings and Continue": "测试设置并继续",
     "Testing only - Resolve file conflicts by syncing newer copies of the file, this can overwrite modified files. Be Warned.": "仅供测试 - 通过同步文件的较新副本来解决文件冲突,这可能会覆盖修改过的文件。请注意 ",
+    "The algorithm used for JWT authentication.": "用于 JWT 认证的算法。",
+    "The Application ID for P2P connection. This should be same among your devices. Default is 'self-hosted-livesync' and could not be modified from the UI.": "用于 P2P 连接的应用 ID。所有设备应保持相同。默认值为 'self-hosted-livesync'，无法在界面中修改。",
+    "The connection test cannot add a signalling relay while P2P is active. Use the active relay settings, or disconnect P2P before testing.": "P2P 处于活动状态时，连接测试无法添加信令中继。请使用当前生效的中继设置，或先断开 P2P 再测试。",
+    "The connection to the server has been configured successfully. As the next step,": "与服务器的连接已配置成功。下一步，",
+    "The credential/password for the TURN servers.": "TURN 服务器的凭据/密码。",
     "The delay for consecutive on-demand fetches": "连续按需获取的延迟",
+    "The files in this Vault are almost identical to the server's.": "本库中的文件与服务器上的几乎一致。",
     "The following accepted nodes are missing its node information:\n- ${missingNodes}\n\nThis indicates that they have not been connected for some time or have been left on an older version.\nIt is preferable to update all devices if possible. If you have any devices that are no longer in use, you can clear all accepted nodes by locking the remote once.": "以下已接受节点缺少节点信息：\n- ${missingNodes}\n\n这表示它们已有一段时间未连接，或仍停留在较旧版本。\n如有可能，建议先更新所有设备。如果有已不再使用的设备，可以先锁定一次远程端以清除全部已接受节点。",
+    "The Group ID and passphrase are used to identify your group of devices. Make sure to use the same Group ID and passphrase on all devices you want to synchronise.": "组 ID 和密码短语用于标识你的设备组。请确保所有要同步的设备都使用相同的组 ID 和密码短语。",
     "The Hash algorithm for chunk IDs": "块 ID 的哈希算法(实验性)",
+    "The IndexedDB adapter often offers superior performance in certain scenarios, but it has been found to cause memory leaks when used with LiveSync mode. When using LiveSync mode, please use IDB adapter instead.": "IndexedDB 适配器在某些场景下性能更好，但已发现与 LiveSync 模式同用时会造成内存泄漏。使用 LiveSync 模式时，请改用 IDB 适配器。",
+    "The key (PSK in HSxxx in base64, or private key in ESxxx in PEM) used for JWT authentication.": "用于 JWT 认证的密钥（base64 格式的 PSK，形如 HSxxx；或 PEM 格式的私钥，形如 ESxxx）。",
+    "The key ID. this should be matched with CouchDB->jwt_keys->ALG:_`kid`.": "密钥 ID。它应与 CouchDB->jwt_keys->ALG:_`kid` 相匹配。",
+    "the latest synchronisation data will be downloaded from the server to this device.": "最新的同步数据将从服务器下载到本设备。",
+    "the local database, that is to say the synchronisation information, must be reconstituted.": "本地数据库（即同步信息）必须重建。",
     "The maximum duration for which chunks can be incubated within the document. Chunks exceeding this period will graduate to independent chunks.": "文档中可以孵化的数据块的最大持续时间。超过此时间的数据块将成为独立数据块 ",
     "The maximum number of chunks that can be incubated within the document. Chunks exceeding this number will immediately graduate to independent chunks.": "文档中可以孵化的数据块的最大数量。超过此数量的数据块将立即成为独立数据块 ",
     "The maximum total size of chunks that can be incubated within the document. Chunks exceeding this size will immediately graduate to independent chunks.": "文档中可以孵化的数据块的最大总大小。超过此大小的数据块将立即成为独立数据块 ",
     "The minimum interval for automatic synchronisation on event.": "基于事件自动同步的最小间隔。",
+    "The Nostr relay servers to establish connections for P2P connections. Multiple servers can be separated by commas.": "用于建立 P2P 连接的 Nostr 中继服务器。多个服务器可以用逗号分隔。",
+    "The Passphrase for P2P connection. This should be same among your devices.": "用于 P2P 连接的密码短语。你的所有设备上都应使用相同的密码短语。",
     "The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.": "为防止数据仓库损坏，由于此设备尚未标记为“已确认”，远程数据库已被锁定，暂停同步。请先备份你的仓库、重置本地数据库，然后选择“将此设备标记为已确认”。在复制过程确认此设备已完成确认之前，此警告会持续显示。",
+    "The remote is already set up, and the configuration is compatible (or got compatible by this operation).": "远端已设置好，且配置兼容（或经此操作后已兼容）。",
+    "The Room ID for P2P connection. This should be same among your devices.": "用于 P2P 连接的房间 ID。所有设备应使用相同的房间 ID。",
+    "The Rotation duration of token in minutes. Each generated tokens will be valid only within this duration.": "令牌的轮换时长（单位：分钟）。每个生成的令牌仅在此时长内有效。",
+    "The Setup-URI does not appear to be valid. Please check that you have copied it correctly.": "设置 URI 似乎无效。请检查是否完整复制。",
+    "The Setup-URI is valid and ready to use.": "设置 URI 有效，可以使用。",
+    "the single, authoritative master copy": "唯一的权威主副本",
+    "The subject for JWT authentication. Mostly username.": "JWT 认证的主体，通常为用户名。",
+    "the synchronisation data on the server will be built based on the current data on this device.": "服务器上的同步数据将基于本设备的当前数据构建。",
+    "The TURN servers to use for P2P connections. Multiple servers can be separated by commas.": "用于 P2P 连接的 TURN 服务器。多个服务器可用逗号分隔。",
+    "The username for the TURN servers.": "TURN 服务器的用户名。",
+    "Themes": "主题",
+    "There is a way to resolve this on other devices.": "在其他设备上有办法解决这个问题。",
+    "There may be differences between the files in this Vault and the server.": "本库中的文件与服务器上可能存在差异。",
+    "Therefore, we ask that you exercise extreme caution when configuring server information manually. If an incorrect passphrase is entered, the data on the server will become corrupted.": "因此，我们要求你在手动配置服务器信息时格外小心。如果输入了错误的密码短语，服务器上的数据将会损坏。",
+    "This can isolate your connections between devices. Use the same Room ID for the same devices.": "这可以隔离设备之间的连接。同一组设备请使用相同的房间 ID。",
+    "This device": "本设备",
+    "This device name": "本设备名称",
     "This feature enables direct synchronisation between devices. No server is required, but both devices must be online at the same time for synchronisation to occur, and some features may be limited. Internet connection is only required to signalling (detecting peers) and not for data transfer.": "此功能可在设备之间直接同步，无需服务器；但同步时两台设备必须同时在线，且部分功能可能受限。互联网连接仅用于信令（发现对端），不用于数据传输。",
+    "This first setup has several short steps because it confirms encryption, the connection method, and which device provides the initial data. Once it is complete, additional devices can reuse a Setup URI.": "首次设置分为几个简短步骤，因为它要确认加密方式、连接方式，以及由哪台设备提供初始数据。完成后，其他设备可以复用设置 URI。",
     "This is an advanced option for users who do not have a URI or who wish to configure detailed settings.": "这是面向没有 URI 或希望手动配置详细参数的高级选项。",
+    "This is an extremely powerful operation. We strongly recommend that you copy your Vault folder to a safe location.": "这是一项影响极大的操作。我们强烈建议先把库文件夹复制到安全位置。",
     "This is the most suitable synchronisation method for the design. All functions are available. You must have set up a CouchDB instance.": "这是最符合当前设计的同步方式，所有功能均可用。你需要事先部署好 CouchDB 实例。",
+    "This optional check uses Obsidian's internal request API and sends the credentials above to the CouchDB server. Use it only with a server you trust; administrator access may be required.": "此可选检查使用 Obsidian 的内部请求 API，并把上面的凭据发送到 CouchDB 服务器。请仅对你信任的服务器使用；可能需要管理员权限。",
     "This passphrase will not be copied to another device. It will be set to `Default` until you configure it again.": "此密码不会复制到另一台设备。在您再次配置之前,它将设置为 `Default` ",
+    "This password is used to encrypt the connection. Use something long enough.": "此密码用于加密连接。请设置得足够长。",
+    "This procedure will first delete all existing synchronisation data from the server. Following this, the server data will be completely rebuilt, using the current state of your Vault on this device (including its local database) as": "此操作会先删除服务器上所有现有的同步数据。随后，服务器数据将被完全重建，以本设备上你库的当前状态（包括其本地数据库）作为",
+    "This setting must be the same even when connecting to multiple synchronisation destinations.": "即使连接到多个同步目标，此设置也必须保持一致。",
+    "This Vault is empty, or contains only new files that are not on the server.": "本库为空，或只包含服务器上没有的新文件。",
+    "This will rebuild the local database on this device using the most recent data from the server. This action is designed to resolve synchronisation inconsistencies and restore correct functionality.": "这将用服务器上的最新数据重建本设备的本地数据库。此操作旨在解决同步不一致并恢复正常功能。",
     "This will recreate chunks for all files. If there were missing chunks, this may fix the errors.": "这会为所有文件重新生成 chunks。如果之前存在缺失的 chunks，这可能修复相关错误。",
+    "To minimise the creation of new conflicts": "以减少新冲突的产生",
     "To prevent unwanted vault corruption, the remote database has been locked for synchronisation. (This device is marked as 'resolved'.) When all your devices are marked as 'resolved', unlock the database. This warning will continue to appear until replication confirms the device is resolved.": "为防止意外的数据仓库损坏，远程数据库已被锁定，暂停同步。（此设备已被标记为“已确认”）当你的所有设备都标记为“已确认”后，再解锁数据库。在复制过程确认此设备已完成确认之前，此警告会持续显示。",
-    "TweakMismatchResolve.Action.Dismiss": "Dismiss",
-    "TweakMismatchResolve.Action.UseConfigured": "Use configured settings",
-    "TweakMismatchResolve.Action.UseMine": "Update remote database settings",
-    "TweakMismatchResolve.Action.UseMineAcceptIncompatible": "Update remote database settings but keep as is",
-    "TweakMismatchResolve.Action.UseMineWithRebuild": "Update remote database settings and rebuild again",
-    "TweakMismatchResolve.Action.UseRemote": "Apply settings to this device",
-    "TweakMismatchResolve.Action.UseRemoteAcceptIncompatible": "Apply settings to this device, but and ignore incompatibility",
-    "TweakMismatchResolve.Action.UseRemoteWithRebuild": "Apply settings to this device, and fetch again",
-    "TweakMismatchResolve.Message.Main": "\nThe settings in the remote database are as follows. These values are configured by other devices, which are synchronised with this device at least once.\n\nIf you want to use these settings, please select %{TweakMismatchResolve.Action.UseConfigured}.\nIf you want to keep the settings of this device, please select %{TweakMismatchResolve.Action.Dismiss}.\n\n${table}\n\n>[!TIP]\n> If you want to synchronise all settings, please use `Sync settings via markdown` after applying minimal configuration with this feature.\n\n${additionalMessage}",
-    "TweakMismatchResolve.Message.MainTweakResolving": "Your configuration has not been matched with the one on the remote server.\n\nFollowing configuration should be matched:\n\n${table}\n\nLet us know your decision.\n\n${additionalMessage}",
-    "TweakMismatchResolve.Message.UseRemote.WarningRebuildRecommended": "\n>[!NOTICE]\n> Some changes are compatible but may consume extra storage and transfer volumes. A rebuild is recommended. However, a rebuild may not be performed at present, but may be implemented in future maintenance.\n> ***Please ensure that you have time and are connected to a stable network to apply!***",
-    "TweakMismatchResolve.Message.UseRemote.WarningRebuildRequired": "\n>[!WARNING]\n> Some remote configurations are not compatible with the local database of this device. Rebuilding the local database will be required.\n> ***Please ensure that you have time and are connected to a stable network to apply!***",
-    "TweakMismatchResolve.Message.WarningIncompatibleRebuildRecommended": "\n>[!NOTICE]\n> We have detected that some of the values are different to make incompatible the local database with the remote database.\n> Some changes are compatible but may consume extra storage and transfer volumes. A rebuild is recommended. However, a rebuild may not be performed at present, but may be implemented in future maintenance.\n> If you want to rebuild, it takes a few minutes or more. **Make sure it is safe to perform it now.**",
-    "TweakMismatchResolve.Message.WarningIncompatibleRebuildRequired": "\n>[!WARNING]\n> We have detected that some of the values are different to make incompatible the local database with the remote database.\n> Either local or remote rebuilds are required. Both of them takes a few minutes or more. **Make sure it is safe to perform it now.**",
-    "TweakMismatchResolve.Table": "| Value name | This device | On Remote |\n|: --- |: ---- :|: ---- :|\n${rows}\n\n",
+    "Transfer Tweak": "传输微调",
+    "TURN Credential": "TURN 凭据",
+    "TURN server settings are only necessary if you are behind a strict NAT or firewall that prevents direct P2P connections. In most cases, you can leave these fields blank.": "只有当处于阻止直接 P2P 连接的严格 NAT 或防火墙之后时，才需要 TURN 服务器设置。大多数情况下这些字段可以留空。",
+    "TURN Server URLs (comma-separated)": "TURN 服务器地址（逗号分隔）",
+    "TURN Servers": "TURN 服务器",
+    "TURN Username": "TURN 用户名",
+    "TweakMismatchResolve.Action.DisableAutoAcceptCompatible": "停用自动接受",
+    "TweakMismatchResolve.Action.Dismiss": "忽略",
+    "TweakMismatchResolve.Action.EnableAutoAcceptCompatible": "启用自动接受",
+    "TweakMismatchResolve.Action.UseConfigured": "使用已配置的设置",
+    "TweakMismatchResolve.Action.UseMine": "更新远程数据库设置",
+    "TweakMismatchResolve.Action.UseMineAcceptIncompatible": "更新远程数据库设置，但忽略不兼容问题",
+    "TweakMismatchResolve.Action.UseMineWithRebuild": "更新远程数据库设置并再次重建",
+    "TweakMismatchResolve.Action.UseRemote": "将设置应用到此设备",
+    "TweakMismatchResolve.Action.UseRemoteAcceptIncompatible": "将设置应用到此设备，但忽略不兼容问题",
+    "TweakMismatchResolve.Action.UseRemoteWithRebuild": "将设置应用到此设备，并重新获取",
+    "TweakMismatchResolve.Message.AutoAcceptCompatibleUndefined": "\n各设备的设置似乎存在差异。你现在可以自动应用兼容的更改到这些配置。\n是否要启用此「自动接受」设置？",
+    "TweakMismatchResolve.Message.Main": "\n远程数据库中的设置如下。这些值由与此设备至少同步过一次的其他设备配置。\n\n如果你想使用这些设置，请选择 %{TweakMismatchResolve.Action.UseConfigured}。\n如果你想保留此设备的设置，请选择 %{TweakMismatchResolve.Action.Dismiss}。\n\n${table}\n\n>[!TIP]\n> 如果你想同步全部设置，请先使用此功能应用最小配置，然后使用 `Sync settings via markdown`。\n\n${additionalMessage}",
+    "TweakMismatchResolve.Message.MainTweakResolving": "你的配置与远程服务器上的配置不一致。\n\n以下配置应当保持一致：\n\n${table}\n\n请告知你的决定。\n\n${additionalMessage}",
+    "TweakMismatchResolve.Message.mineUpdated": "本设备的配置已调整。",
+    "TweakMismatchResolve.Message.remoteUpdated": "远端存储的配置已更新。",
+    "TweakMismatchResolve.Message.UseRemote.WarningRebuildRecommended": "\n>[!NOTICE]\n> 部分更改是兼容的，但可能会占用额外的存储空间和传输流量。建议进行重建。不过，也可以暂不重建，留待今后维护时再进行。\n> ***应用前请确保你有充足的时间，并已连接到稳定的网络！***",
+    "TweakMismatchResolve.Message.UseRemote.WarningRebuildRequired": "\n>[!WARNING]\n> 部分远程配置与本设备的本地数据库不兼容，将需要重建本地数据库。\n> ***应用前请确保你有充足的时间，并已连接到稳定的网络！***",
+    "TweakMismatchResolve.Message.WarningIncompatibleRebuildRecommended": "\n>[!NOTICE]\n> 我们检测到部分值存在差异，导致本地数据库与远程数据库不兼容。\n> 部分更改是兼容的，但可能会占用额外的存储空间和传输流量。建议进行重建。不过，也可以暂不重建，留待今后维护时再进行。\n> 如果你要重建，大约需要几分钟或更长时间。**请先确认现在执行是安全的。**",
+    "TweakMismatchResolve.Message.WarningIncompatibleRebuildRequired": "\n>[!WARNING]\n> 我们检测到某些值存在差异，导致本地数据库与远程数据库不兼容。\n> 需要重建本地或远程其中之一，两者都需要几分钟甚至更长时间。**请确保现在执行此操作是安全的。**",
+    "TweakMismatchResolve.Table": "| 值名称 | 此设备 | 远程 |\n|: --- |: ---- :|: ---- :|\n${rows}\n\n",
     "TweakMismatchResolve.Table.Row": "| ${name} | ${self} | ${remote} |",
-    "TweakMismatchResolve.Title": "Configuration Mismatch Detected",
-    "TweakMismatchResolve.Title.TweakResolving": "Configuration Mismatch Detected",
-    "TweakMismatchResolve.Title.UseRemoteConfig": "Use Remote Configuration",
+    "TweakMismatchResolve.Title": "检测到配置不一致",
+    "TweakMismatchResolve.Title.AutoAcceptCompatible": "可自动接受",
+    "TweakMismatchResolve.Title.TweakResolving": "检测到配置不一致",
+    "TweakMismatchResolve.Title.UseRemoteConfig": "使用远程配置",
+    "Ui.Common.LocalDatabaseInitialisationFailed": "Self-hosted LiveSync 无法同步。请生成报告以查看详细日志。",
     "Ui.Common.Signal.Caution": "注意",
     "Ui.Common.Signal.Danger": "危险",
     "Ui.Common.Signal.Notice": "提示",
     "Ui.Common.Signal.Warning": "警告",
+    "Ui.Common.SomeFilesCouldNotBeSynchronised": "并非所有文件都能同步。请检查受影响的文件。生成报告以查看详细日志。",
     "Ui.Settings.Advanced.LocalDatabaseTweak": "本地数据库调整",
     "Ui.Settings.Advanced.MemoryCache": "内存缓存",
     "Ui.Settings.Advanced.TransferTweak": "传输调整",
@@ -985,6 +1428,28 @@
     "Ui.Settings.SyncSettings.Fetch": "获取",
     "Ui.Settings.SyncSettings.Merge": "合并",
     "Ui.Settings.SyncSettings.Overwrite": "覆盖",
+    "Ui.SetupWizard.ApplySettingsInitialisation.ApplyWithoutInitialisation": "不初始化直接应用",
+    "Ui.SetupWizard.ApplySettingsInitialisation.Back": "查看其他应用这些设置的方式",
+    "Ui.SetupWizard.ApplySettingsInitialisation.BypassGuidance": "仅应用这些设置可能使本设备与其现有同步数据不兼容。请仅在确认无需重建时使用。",
+    "Ui.SetupWizard.ApplySettingsInitialisation.BypassTitle": "不初始化直接应用设置？",
+    "Ui.SetupWizard.ApplySettingsInitialisation.ContinueFetch": "继续获取",
+    "Ui.SetupWizard.ApplySettingsInitialisation.FetchOption": "重置本设备的同步",
+    "Ui.SetupWizard.ApplySettingsInitialisation.FetchOptionDesc": "重启后，用当前的远端同步数据重建本设备的本地数据库。库中的文件随后会与该数据核对合并。",
+    "Ui.SetupWizard.ApplySettingsInitialisation.FetchOptionP2PDesc": "重启后选择一台在线的源设备。本设备的本地 LiveSync 数据库将从该源设备重建。",
+    "Ui.SetupWizard.ApplySettingsInitialisation.Guidance": "这些设置变更会改变同步数据的解释方式。请在重启后连同初始化操作一起应用。",
+    "Ui.SetupWizard.ApplySettingsInitialisation.KeepEditing": "继续编辑",
+    "Ui.SetupWizard.ApplySettingsInitialisation.ProceedFetch": "重启并获取同步数据",
+    "Ui.SetupWizard.ApplySettingsInitialisation.ProceedFetchP2P": "重启并选择源设备",
+    "Ui.SetupWizard.ApplySettingsInitialisation.ProceedRebuild": "重启并覆盖服务器数据",
+    "Ui.SetupWizard.ApplySettingsInitialisation.ProceedRebuildP2P": "重启并准备本设备",
+    "Ui.SetupWizard.ApplySettingsInitialisation.Question": "重启后应使用哪份现有数据？",
+    "Ui.SetupWizard.ApplySettingsInitialisation.RebuildOption": "用本设备的文件覆盖服务器数据",
+    "Ui.SetupWizard.ApplySettingsInitialisation.RebuildOptionDesc": "用本库中当前的文件重建本地和远端数据库。其他正在同步的设备之后必须重置其本地同步。",
+    "Ui.SetupWizard.ApplySettingsInitialisation.RebuildOptionP2P": "用本库的文件准备本设备",
+    "Ui.SetupWizard.ApplySettingsInitialisation.RebuildOptionP2PDesc": "用本库中当前的文件重建本设备的本地 LiveSync 数据库。这不会覆盖其他设备。",
+    "Ui.SetupWizard.ApplySettingsInitialisation.RemoteVerificationGuidance": "无法用当前的凭据和加密设置验证所配置的远端。继续可能导致重启后获取失败。",
+    "Ui.SetupWizard.ApplySettingsInitialisation.RemoteVerificationTitle": "无法验证远端同步数据",
+    "Ui.SetupWizard.ApplySettingsInitialisation.Title": "应用设置并重新初始化同步",
     "Ui.SetupWizard.Common.Back": "不，带我返回",
     "Ui.SetupWizard.Common.Cancel": "取消",
     "Ui.SetupWizard.Common.ProceedSelectOption": "请选择一个选项后继续",
@@ -997,6 +1462,7 @@
     "Ui.SetupWizard.Intro.ProceedNew": "是的，我要开始新的同步配置",
     "Ui.SetupWizard.Intro.Question": "首先，请选择最符合你当前情况的选项。",
     "Ui.SetupWizard.Intro.Title": "欢迎使用 Self-hosted LiveSync",
+    "Ui.SetupWizard.Invitation.Start": "开始设置",
     "Ui.SetupWizard.OutroAskUserMode.CompatibleOption": "远程端已配置完成，且当前配置兼容（或已通过本次操作变为兼容）。",
     "Ui.SetupWizard.OutroAskUserMode.CompatibleOptionDesc": "除非你非常确定，否则选择此项存在风险。它假定服务器配置与当前设备兼容。如果事实并非如此，可能会导致数据丢失。请确认你了解后果。",
     "Ui.SetupWizard.OutroAskUserMode.ExistingOption": "远程服务器已经配置完成，我想让此设备加入同步。",
@@ -1008,12 +1474,25 @@
     "Ui.SetupWizard.OutroAskUserMode.ProceedNext": "继续下一步",
     "Ui.SetupWizard.OutroAskUserMode.Question": "请选择你的当前情况。",
     "Ui.SetupWizard.OutroAskUserMode.Title": "即将完成：还需要做出选择",
+    "Ui.SetupWizard.OutroNewP2PUser.GuidanceNotice": "P2P 没有中心服务器副本可供覆盖。此步骤只准备本设备；当其他设备获取初始数据时，请保持本设备在线。",
+    "Ui.SetupWizard.OutroNewP2PUser.GuidancePrimary": "点对点连接已配置成功。接下来，将用本库中当前的文件构建本地 LiveSync 数据库。",
+    "Ui.SetupWizard.OutroNewP2PUser.Important": "请注意",
+    "Ui.SetupWizard.OutroNewP2PUser.Proceed": "重启并准备本设备",
+    "Ui.SetupWizard.OutroNewP2PUser.Question": "请点击下方按钮重启，然后进入本地初始化确认。",
+    "Ui.SetupWizard.OutroNewP2PUser.Title": "设置完成：正在准备本 P2P 设备",
     "Ui.SetupWizard.OutroNewUser.GuidancePrimary": "服务器连接已成功配置。下一步将根据当前设备上的数据，在服务器端建立同步数据。",
     "Ui.SetupWizard.OutroNewUser.GuidanceWarning": "重启后，当前设备上的数据会作为主副本上传到服务器。请注意，服务器上现有的非预期数据将被完全覆盖。",
     "Ui.SetupWizard.OutroNewUser.Important": "重要",
     "Ui.SetupWizard.OutroNewUser.Proceed": "重启并初始化服务器",
     "Ui.SetupWizard.OutroNewUser.Question": "请选择下方按钮，重启并进入最终确认步骤。",
     "Ui.SetupWizard.OutroNewUser.Title": "设置完成：准备初始化服务器",
+    "Ui.SetupWizard.RebuildEverythingP2P.ConfirmLocalReset": "我明白这只会重置本设备的本地同步数据库。",
+    "Ui.SetupWizard.RebuildEverythingP2P.ConfirmLocalResetNote": "将使用本库中当前的文件来重建它。",
+    "Ui.SetupWizard.RebuildEverythingP2P.ConfirmTitle": "⚠️ 请确认以下内容",
+    "Ui.SetupWizard.RebuildEverythingP2P.Guidance": "此操作会丢弃本设备的本地 LiveSync 数据库，并用本库中当前的文件重建。它不会删除或覆盖其他设备上的数据。",
+    "Ui.SetupWizard.RebuildEverythingP2P.Note": "初始化后请保持本设备在线，以便其他设备从它获取库。",
+    "Ui.SetupWizard.RebuildEverythingP2P.Proceed": "我明白，准备本设备",
+    "Ui.SetupWizard.RebuildEverythingP2P.Title": "最终确认：为本设备准备 P2P",
     "Ui.SetupWizard.SelectExisting.Guidance": "你正在将此设备加入已有同步配置。",
     "Ui.SetupWizard.SelectExisting.ManualOption": "手动输入服务器信息",
     "Ui.SetupWizard.SelectExisting.ManualOptionDesc": "手动重新配置与你其他设备相同的服务器信息。此方式仅适用于高级用户。",
@@ -1046,438 +1525,57 @@
     "Ui.SetupWizard.SetupRemote.ProceedP2P": "继续配置仅点对点模式",
     "Ui.SetupWizard.SetupRemote.Title": "输入服务器信息",
     "Unique name between all synchronized devices. To edit this setting, please disable customization sync once.": "所有同步设备之间的唯一名称。要编辑此设置,请首先禁用自定义同步",
+    "Unless you are certain, selecting this options is bit dangerous. It assumes that the server configuration is compatible with this device. If this is not the case, data loss may occur. Please ensure you know what you are doing.": "除非你非常确定，否则选择此选项有些危险。它假定服务器配置与本设备兼容。若不兼容，可能会发生数据丢失。请确保你清楚自己在做什么。",
+    "Updating list...": "正在更新列表…",
+    "URL": "URL",
     "Use a custom passphrase": "使用自定义密码短语",
     "Use a Setup URI (Recommended)": "使用 Setup URI（推荐）",
     "Use Custom HTTP Handler": "使用自定义 HTTP 处理程序",
+    "Use Diagnostic RTCPeerConnection for statistics": "使用诊断用 RTCPeerConnection 收集统计信息",
     "Use dynamic iteration count": "使用动态迭代次数",
+    "Use internal API": "使用内部 API",
+    "Use Internal API": "使用内部 API",
+    "Use JWT Authentication": "使用 JWT 身份验证",
+    "Use JWT instead of Basic Authentication": "使用 JWT 而非 Basic 认证",
+    "Use Only Local Chunks": "仅使用本地数据块",
+    "Use Path-Style Access": "使用路径风格访问",
+    "Use Random Number": "使用随机数",
+    "Use Request API to avoid `inevitable` CORS problem": "使用 Request API 以避免 `inevitable` CORS 问题",
     "Use Segmented-splitter": "使用分段分割器",
     "Use splitting-limit-capped chunk splitter": "使用分割限制上限的块分割器",
+    "Use the detailed flow": "使用详细流程",
     "Use the trash bin": "使用回收站",
     "Use timeouts instead of heartbeats": "使用超时而不是心跳",
+    "Use vrtmrz's relay": "使用 vrtmrz 的中继",
     "username": "用户名",
     "Username": "用户名",
     "Verbose Log": "详细日志",
     "Verify all": "全部校验",
     "Verify and repair all files": "校验并修复所有文件",
     "Warning! This will have a serious impact on performance. And the logs will not be synchronised under the default name. Please be careful with logs; they often contain your confidential information.": "警告！这将严重影响性能。并且日志不会以默认名称同步。请小心处理日志；它们通常包含您的敏感信息 ",
+    "WATCHING": "监视中",
+    "We are about to retrieve the remote data.\n\nFirstly, how shall we handle the data retrieved from this remote source?\n\n- **${NEWER_WINS}**: Compares the modified time of files and takes the newer one.\n  If you have been using Self-hosted LiveSync and have made changes on multiple devices, this option may be suitable for you as it tries to merge changes based on modified time.\n- **${REMOTE_WINS}**: Remote data is the source of truth.\n  If you are new to using Self-hosted LiveSync. This option may be easiest to understand and get started with.\n  It will overwrite all your local files with the remote data, so please make sure you have a backup if there is any important data in your vault.\n- **${DETAILED}**: Opens the detailed setup wizard.\n  If you want to have more control over the synchronisation process, or want to review the changes before applying, you can choose this option to use the detailed flow.": "即将获取远程数据。\n\n首先，应如何处理从此远程来源获取的数据？\n\n- **${NEWER_WINS}**：比较文件的修改时间，并采用较新的那一个。\n  如果你一直在使用 Self-hosted LiveSync，并且在多台设备上做过更改，此选项可能适合你，因为它会尝试根据修改时间合并更改。\n- **${REMOTE_WINS}**：以远程数据为准。\n  如果你是 Self-hosted LiveSync 的新用户，此选项可能最容易理解，也最容易上手。\n  它会用远程数据覆盖你所有的本地文件，因此如果库中有重要数据，请务必先备份。\n- **${DETAILED}**：打开详细设置向导。\n  如果你希望更好地控制同步过程，或希望在应用前检查更改，可以选择此选项使用详细流程。",
+    "We can not use \"/\" to the device name": "设备名称中不能使用「/」",
+    "We can use only Secure (HTTPS) connections on Obsidian Mobile.": "Obsidian 移动端只能使用安全（HTTPS）连接。",
     "We cannot change the device name while this feature is enabled. Please disable this feature to change the device name.": "启用此功能时无法更改设备名称。如需修改设备名称，请先禁用此功能。",
+    "We have to configure the device name": "需要先配置设备名称",
+    "We recommend that you copy your Vault folder to a safe location. This will provide a safeguard in case a large number of conflicts arise, or if you accidentally synchronise with an incorrect destination.": "我们建议你把库文件夹复制到安全位置。这样在出现大量冲突，或不小心同步到错误目标时，能多一层保障。",
     "We will now guide you through a few questions to simplify the synchronisation setup.": "接下来我们会通过几个问题，引导你更轻松地完成同步设置。",
     "We will now proceed with the server configuration.": "接下来将继续进行服务器配置。",
     "Welcome to Self-hosted LiveSync": "欢迎使用 Self-hosted LiveSync",
     "When you save a file in the editor, start a sync automatically": "当您在编辑器中保存文件时,自动开始同步",
+    "While enabled, it causes very performance impact but debugging replication testing and other features will be enabled. Please disable this if you have not read the source code. Requires restart of Obsidian. Sometimes there is no implementation.": "启用后会严重影响性能，但会开启复制调试测试等功能。如果你没有阅读过源代码，请关闭此项。需要重启 Obsidian。部分功能可能尚未实现。",
     "Write credentials in the file": "将凭据写入文件",
     "Write logs into the file": "将日志写入文件",
     "xxhash32 (Fast but less collision resistance)": "xxhash32（速度快，但抗碰撞能力较弱）",
     "xxhash64 (Fastest)": "xxhash64（最快）",
+    "xxhash64 is the current default.": "xxhash64 是当前的默认值。",
     "Yes, I want to add this device to my existing synchronisation": "是的，我要把这台设备加入现有同步",
     "Yes, I want to set up a new synchronisation": "是的，我要配置新的同步",
     "You are adding this device to an existing synchronisation setup.": "你正在将此设备加入到现有同步配置中。",
-    "On": "开启",
-    "Fix": "修复",
-    "NEW": "新增",
-    "Off": "关闭",
-    "Rev": "修订",
-    "URL": "URL",
-    "📡 On": "📡 开启",
-    "Date": "日期",
-    "Deny": "拒绝",
-    "Diff": "差异",
-    "live": "实时",
-    "Name": "名称",
-    "Path": "路径",
-    "Same": "相同",
-    "Stat": "统计",
-    "Sync": "同步",
-    "📡 Off": "📡 关闭",
-    "Close": "关闭",
-    "Mixed": "混合",
-    "Peers": "对等方",
-    "Stats": "统计",
-    "✔ SYNC": "✔ 同步",
-    "Accept": "接受",
-    "Action": "操作",
-    "Chunks": "块",
-    "DENIED": "已拒绝",
-    "Ignore": "忽略",
-    "lang-he": "希伯来语",
-    "Reload": "重新加载",
-    "Revoke": "撤销",
-    "Stop ⚡": "停止 ⚡",
-    "Themes": "主题",
-    "+1 week": "+1 周",
-    "✔ WATCH": "✔ 监视",
-    "🕵️ Diag": "🕵️ 诊断",
-    "Closed:": "已关闭：",
-    "Command": "命令",
-    "Connect": "连接",
-    "Dismiss": "忽略",
-    "Enabled": "已启用",
-    "Failed:": "失败：",
-    "JWT Key": "JWT 密钥",
-    "Not now": "暂不",
-    "Plugins": "插件",
-    "Proceed": "继续",
-    "Refresh": "刷新",
-    "Room ID": "房间 ID",
-    "SENDING": "发送中",
-    "SESSION": "会话",
-    "✔ SELECT": "✔ 选择",
-    "🗑 Delete": "🗑 删除",
-    "ACCEPTED": "已接受",
-    "Advanced": "高级",
-    "Devices:": "设备：",
-    "FETCHING": "获取中",
-    "Group ID": "组 ID",
-    "INVERTED": "已反转",
-    "Peer ID:": "对等方 ID：",
-    "Snippets": "代码片段",
-    "WATCHING": "监视中",
-    "(Missing)": "（缺失）",
-    "Automatic": "自动",
-    "Different": "不同",
-    "IMPORTANT": "重要",
-    "Incoming:": "接收：",
-    "No Items.": "无项目。",
-    "PERMANENT": "永久",
-    "Selective": "选择性",
-    "Setup-URI": "设置 URI",
-    "Sync once": "同步一次",
-    "Connected:": "已连接：",
-    "Disconnect": "断开连接",
-    "Local only": "仅本地",
-    "NO PREVIEW": "无预览",
-    "P2P Status": "P2P 状态",
-    "Syncing...": "同步中…",
-    "🟢 Connected": "🟢 已连接",
-    "Connection:": "连接：",
-    "device name": "设备名称",
-    "obsidianLiveSyncSettingTab.titleExtraMenus": "扩展菜单",
-    "Other files": "其他文件",
-    "PLEASE NOTE": "请注意",
-    "Remote only": "仅远端",
-    "Replicating": "复制中",
-    "This device": "本设备",
-    "Ui.SetupWizard.Invitation.Start": "开始设置",
-    "Ui.SetupWizard.OutroNewP2PUser.Important": "请注意",
-    "⇅: Use newer": "⇅：使用较新版本",
-    "Auto Connect": "自动连接",
-    "Compare file": "比较文件",
-    "Data to Copy": "要复制的数据",
-    "Deselect all": "取消全选",
-    "Memory cache": "内存缓存",
-    "Scan changes": "扫描变更",
-    "Scan QR Code": "扫描二维码",
-    "Show history": "显示历史记录",
-    "Ui.SetupWizard.ApplySettingsInitialisation.KeepEditing": "继续编辑",
-    "Access Key ID": "访问密钥 ID",
-    "Broadcasting?": "正在广播？",
-    "Communicating": "通信中",
-    "Configuration": "配置",
-    "Delete All of": "全部删除",
-    "Folder Prefix": "文件夹前缀",
-    "Hide password": "隐藏密码",
-    "JWT Algorithm": "JWT 算法",
-    "No Connection": "未连接",
-    "Replicate now": "立即复制",
-    "Show password": "显示密码",
-    "TURN Username": "TURN 用户名",
-    "🔴 Disconnected": "🔴 已断开",
-    "Custom Headers": "自定义请求头",
-    "Detected Peers": "检测到的对等方",
-    "Device Peer ID": "设备对等方 ID",
-    "File integrity": "文件完整性",
-    "Highlight diff": "高亮差异",
-    "Initial Action": "初始操作",
-    "moduleCheckRemoteSize.optionReview": "查看选项",
-    "Not configured": "未配置",
-    "obsidianLiveSyncSettingTab.titleExtraFeaturesGroup": "扩展功能",
-    "Relay settings": "中继设置",
-    "Replicating...": "复制中…",
-    "Revert changes": "还原更改",
-    "Save and Apply": "保存并应用",
-    "Skip and close": "跳过并关闭",
-    "Transfer Tweak": "传输微调",
-    "Available Peers": "可用的对等方",
-    "Continue anyway": "仍然继续",
-    "Deny in session": "本次会话内拒绝",
-    "Enter Setup URI": "输入设置 URI",
-    "Newer (${diff})": "较新（${diff}）",
-    "obsidianLiveSyncSettingTab.titleSynchronisation": "同步",
-    "Older (${diff})": "较旧（${diff}）",
-    "Open connection": "打开连接",
-    "Room ID suffix:": "房间 ID 后缀：",
-    "TURN Credential": "TURN 凭据",
-    "Allow in session": "本次会话内允许",
-    "Deny permanently": "永久拒绝",
-    "Document History": "文档历史记录",
-    "JWT Key ID (kid)": "JWT 密钥 ID（kid）",
-    "Maintenance mode": "维护模式",
-    "Select All Shiny": "全选 Shiny",
-    "This device name": "本设备名称",
-    "Updating list...": "正在更新列表…",
-    "Use internal API": "使用内部 API",
-    "Use Internal API": "使用内部 API",
-    "Accept in session": "本次会话内接受",
-    "Advanced Settings": "高级设置",
-    "Allow permanently": "永久允许",
-    "Close this dialog": "关闭此对话框",
-    "Create P2P remote": "创建 P2P 远端",
-    "Flagged Selective": "已标记为选择性",
-    "JWT Subject (sub)": "JWT 主体（sub）",
-    "obsidianLiveSyncSettingTab.titleAdvancedSettings": "高级设置",
-    "Open P2P Setup...": "打开 P2P 设置…",
-    "P2P Configuration": "P2P 配置",
-    "Secret Access Key": "私有访问密钥",
-    "Signalling Status": "信令状态",
-    "Stop Broadcasting": "停止广播",
-    "Use Random Number": "使用随机数",
-    "↓: Overwrite Local": "↓：覆盖本地",
-    "Apply All Selected": "应用所有已选项",
-    "Apply the settings": "应用设置",
-    "Close & Disconnect": "关闭并断开连接",
-    "Fetching status...": "正在获取状态…",
-    "Generate Random ID": "生成随机 ID",
-    "Same or local only": "相同或仅本地",
-    "Start Broadcasting": "开始广播",
-    "Start Sync & Close": "开始同步并关闭",
-    "TweakMismatchResolve.Action.EnableAutoAcceptCompatible": "启用自动接受",
-    "Use vrtmrz's relay": "使用 vrtmrz 的中继",
-    "↑: Overwrite Remote": "↑：覆盖远端",
-    "⚠️ Important Notice": "⚠️ 重要提示",
-    "Connection Settings": "连接设置",
-    "Database -> Storage": "数据库 → 存储",
-    "DENIED (in session)": "已拒绝（本次会话）",
-    "Enter TURN username": "输入 TURN 用户名",
-    "Enter your password": "输入你的密码",
-    "Enter your username": "输入你的用户名",
-    "Recovery and Repair": "恢复与修复",
-    "Storage -> Database": "存储 → 数据库",
-    "TweakMismatchResolve.Action.DisableAutoAcceptCompatible": "停用自动接受",
-    "Ui.SetupWizard.ApplySettingsInitialisation.ContinueFetch": "继续获取",
-    "Encryption Algorithm": "加密算法",
-    "File to view History": "要查看历史记录的文件",
-    "Issue detection log:": "问题检测日志：",
-    "Local Database Tweak": "本地数据库微调",
-    "Maintenance Commands": "维护命令",
-    "Obfuscate Properties": "混淆属性",
-    "obsidianLiveSyncSettingTab.titleHelpAndInformation": "帮助与信息",
-    "Select Flagged Shiny": "选择已标记的 Shiny",
-    "Select P2P remote...": "选择 P2P 远端…",
-    "Strongly Recommended": "强烈推荐",
-    "ACCEPTED (in session)": "已接受（本次会话）",
-    "CouchDB Configuration": "CouchDB 配置",
-    "Enable P2P Replicator": "启用 P2P 复制器",
-    "Enter TURN credential": "输入 TURN 凭据",
-    "Enter your JWT Key ID": "输入你的 JWT 密钥 ID",
-    "Enter your passphrase": "输入你的密码短语",
-    "Experimental Settings": "实验性设置",
-    "TweakMismatchResolve.Title.AutoAcceptCompatible": "可自动接受",
-    "Use Path-Style Access": "使用路径风格访问",
-    "Enter your Bucket Name": "输入你的存储桶名称",
-    "Restart and Fetch Data": "重启并获取数据",
-    "Use JWT Authentication": "使用 JWT 身份验证",
-    "you wanted(Thank you)!": "你要求的操作（谢谢）！",
-    "Passphrase is required.": "密码短语是必填项。",
-    "Peer to Peer Replicator": "点对点复制器",
-    "Save without connecting": "不连接直接保存",
-    "Enter your Access Key ID": "输入你的访问密钥 ID",
-    "Enter your database name": "输入你的数据库名称",
-    "Gathering information...": "正在收集信息…",
-    "obsidianLiveSyncSettingTab.titleHelpAndTroubleshooting": "帮助与疑难解答",
-    "obsidianLiveSyncSettingTab.titleMaintenanceAndRecovery": "维护与恢复",
-    "Select active P2P remote": "选择生效的 P2P 远端",
-    "Test connection and save": "测试连接并保存",
-    "Auto Start P2P Connection": "自动启动 P2P 连接",
-    "Check server requirements": "检查服务器要求",
-    "Hide not applicable items": "隐藏不适用项",
-    "Proceed to the next step.": "继续下一步。",
-    "S3/MinIO/R2 Configuration": "S3/MinIO/R2 配置",
-    "Failed to parse Setup-URI.": "无法解析设置 URI。",
-    "Just for a minute, please!": "请稍等一分钟！",
-    "Test Settings and Continue": "测试设置并继续",
-    "${count} issue(s) detected!": "检测到 ${count} 个问题！",
-    "Pick a file to show history": "选择一个文件以显示历史记录",
-    "Signaling Server Connection": "信令服务器连接",
-    "All the same or non-existent": "全部相同或不存在",
-    "Enter your Secret Access Key": "输入你的私有访问密钥",
-    "Lower (${local} < ${remote})": "较低（${local} < ${remote}）",
-    "Ui.SetupWizard.ApplySettingsInitialisation.ApplyWithoutInitialisation": "不初始化直接应用",
-    "Higher (${local} > ${remote})": "较高（${local} > ${remote}）",
-    "Please select your situation.": "请选择你的情况。",
-    "Restart and Initialise Server": "重启并初始化服务器",
-    "I Understand, Overwrite Server": "我明白，覆盖服务器",
-    "⚠️ Please Confirm the Following": "⚠️ 请确认以下内容",
-    "All checks passed successfully!": "所有检查均已通过！",
-    "Ui.SetupWizard.ApplySettingsInitialisation.ProceedRebuildP2P": "重启并准备本设备",
-    "Ui.SetupWizard.OutroNewP2PUser.Proceed": "重启并准备本设备",
-    "Ui.SetupWizard.RebuildEverythingP2P.ConfirmTitle": "⚠️ 请确认以下内容",
-    "Enter a folder prefix (optional)": "输入文件夹前缀（可选）",
-    "Reset and Resume Synchronisation": "重置并恢复同步",
-    "JWT Expiration Duration (minutes)": "JWT 有效期（分钟）",
-    "Ui.SetupWizard.ApplySettingsInitialisation.ProceedRebuild": "重启并覆盖服务器数据",
-    "Ui.SetupWizard.RebuildEverythingP2P.Proceed": "我明白，准备本设备",
-    "Mostly Complete: Decision Required": "基本完成：需要你决定",
-    "No checks have been performed yet.": "尚未执行任何检查。",
-    "TURN Server URLs (comma-separated)": "TURN 服务器地址（逗号分隔）",
-    "Ui.SetupWizard.ApplySettingsInitialisation.ProceedFetchP2P": "重启并选择源设备",
-    "Checking connection... Please wait.": "正在检查连接…请稍候。",
-    "Enter a complete HTTP or HTTPS URL.": "输入完整的 HTTP 或 HTTPS 地址。",
-    "Ui.SetupWizard.ApplySettingsInitialisation.RebuildOptionP2P": "用本库的文件准备本设备",
-    "Enter your JWT secret or private key": "输入你的 JWT 密钥或私钥",
-    "I have created a backup of my Vault.": "我已备份我的库。",
-    "On the source device, open Obsidian.": "在源设备上打开 Obsidian。",
-    "Start change-broadcasting on Connect": "连接时开始广播变更",
-    "Ui.SetupWizard.ApplySettingsInitialisation.FetchOption": "重置本设备的同步",
-    "We have to configure the device name": "需要先配置设备名称",
-    "Failed to create replicator instance.": "创建复制器实例失败。",
-    "the single, authoritative master copy": "唯一的权威主副本",
-    "We can not use \"/\" to the device name": "设备名称中不能使用「/」",
-    "Delete remote configuration '${name}'?": "删除远端配置「${name}」？",
-    "Ui.SetupWizard.ApplySettingsInitialisation.BypassTitle": "不初始化直接应用设置？",
-    "Ui.SetupWizard.ApplySettingsInitialisation.ProceedFetch": "重启并获取同步数据",
-    "Diagnostic RTCPeerConnection is enabled": "已启用诊断用 RTCPeerConnection",
-    "Error during connection test: ${reason}": "连接测试出错：${reason}",
-    "The Setup-URI is valid and ready to use.": "设置 URI 有效，可以使用。",
-    "Connect to existing database and continue": "连接到现有数据库并继续",
-    "Enter your JWT Subject (CouchDB Username)": "输入你的 JWT 主体（CouchDB 用户名）",
-    "To minimise the creation of new conflicts": "以减少新冲突的产生",
-    "Ui.SetupWizard.OutroNewP2PUser.Title": "设置完成：正在准备本 P2P 设备",
-    "Create or connect to database and continue": "创建或连接到数据库并继续",
-    "Error during testAndFixSettings: ${reason}": "testAndFixSettings 出错：${reason}",
-    "Failed to connect to the server: ${reason}": "无法连接到服务器：${reason}",
-    "Prevent fetching configuration from server": "阻止从服务器获取配置",
-    "Ui.SetupWizard.ApplySettingsInitialisation.Back": "查看其他应用这些设置的方式",
-    "I am unable to create a backup of my Vault.": "我无法备份我的库。",
-    "Have you created a backup before proceeding?": "继续之前，你备份了吗？",
-    "I am unable to create a backup of my Vaults.": "我无法备份我的库。",
-    "On this device, please keep this Vault open.": "请在本设备上保持此库处于打开状态。",
-    "TweakMismatchResolve.Message.mineUpdated": "本设备的配置已调整。",
-    "Setup Complete: Preparing to Initialise Server": "设置完成：正在准备初始化服务器",
-    "Ui.SetupWizard.ApplySettingsInitialisation.RebuildOption": "用本设备的文件覆盖服务器数据",
-    "(e.g., after editing many files whilst offline)": "（例如：离线期间编辑了大量文件之后）",
-    "Ui.SetupWizard.ApplySettingsInitialisation.Title": "应用设置并重新初始化同步",
-    "Ui.SetupWizard.RebuildEverythingP2P.Title": "最终确认：为本设备准备 P2P",
-    "Use Diagnostic RTCPeerConnection for statistics": "使用诊断用 RTCPeerConnection 收集统计信息",
-    "Enter your Region (e.g., us-east-1, auto for R2)": "输入你的区域（例如 us-east-1，R2 填 auto）",
-    "There is a way to resolve this on other devices.": "在其他设备上有办法解决这个问题。",
-    "Ui.SetupWizard.ApplySettingsInitialisation.Question": "重启后应使用哪份现有数据？",
-    "Ui.SetupWizard.ApplySettingsInitialisation.RemoteVerificationTitle": "无法验证远端同步数据",
-    "Please enter the CouchDB server information below.": "请在下方填写 CouchDB 服务器信息。",
-    "Please understand that this is intended behaviour.": "请注意这是预期行为。",
     "You can configure in the Obsidian Plugin Settings.": "你可以在 Obsidian 插件设置中配置。",
-    "TweakMismatchResolve.Message.remoteUpdated": "远端存储的配置已更新。",
-    "Failed to connect to the signalling relay: ${reason}": "无法连接到信令中继：${reason}",
-    "Connected to Signaling Server (as Peer ID: ${peerId})": "已连接到信令服务器（对等方 ID：${peerId}）",
-    "Of course, we can back up the data before proceeding.": "当然，我们可以先备份数据再继续。",
-    "Please configure your end-to-end encryption settings.": "请配置你的端到端加密设置。",
-    "obsidianLiveSyncSettingTab.logServerConfigurationCheck": "服务器配置检查",
-    "Setup Complete: Preparing to Fetch Synchronisation Data": "设置完成：正在准备获取同步数据",
-    "I understand the risks and will proceed without a backup.": "我明白风险，将在没有备份的情况下继续。",
-    "Ui.SetupWizard.RebuildEverythingP2P.ConfirmLocalResetNote": "将使用本库中当前的文件来重建它。",
-    "Failed to connect to the server. Please check your settings.": "无法连接到服务器。请检查你的设置。",
-    "moduleCheckRemoteSize.noticeNotConfigured": "未配置远端存储体积提醒。{HERE}",
-    "I understand that this action is irreversible once performed.": "我明白此操作一旦执行便不可撤销。",
-    "No devices available. Waiting for other devices to connect...": "没有可用的设备。正在等待其他设备连接…",
-    "The files in this Vault are almost identical to the server's.": "本库中的文件与服务器上的几乎一致。",
-    "We can use only Secure (HTTPS) connections on Obsidian Mobile.": "Obsidian 移动端只能使用安全（HTTPS）连接。",
-    "by resetting the remote, you will be informed on other devices.": "重置远端后，其他设备会收到通知。",
-    "My remote server is already set up. I want to join this device.": "我的远端服务器已设置好，我想让本设备加入。",
-    "Please enter the Peer-to-Peer Synchronisation information below.": "请在下方填写点对点同步信息。",
-    "If you understand the risks and still wish to proceed, select so.": "如果你明白风险但仍希望继续，请选择此项。",
-    "Final Confirmation: Overwrite Server Data with This Device's Files": "最终确认：用本设备的文件覆盖服务器数据",
-    "There may be differences between the files in this Vault and the server.": "本库中的文件与服务器上可能存在差异。",
-    "Please follow the steps below to import settings from your existing device.": "请按以下步骤从你现有的设备导入设置。",
-    "This password is used to encrypt the connection. Use something long enough.": "此密码用于加密连接。请设置得足够长。",
-    "This Vault is empty, or contains only new files that are not on the server.": "本库为空，或只包含服务器上没有的新文件。",
-    "Please select an active P2P remote configuration to change P2P sync targets.": "请选择一个生效的 P2P 远端配置以更改 P2P 同步目标。",
-    "However, This should not be enabled if you want to increase your secrecy more.": "不过，如果你希望进一步提高保密性，则不应启用此项。",
-    "Please select the button below to restart and proceed to the final confirmation.": "请点击下方按钮重启，然后进入最终确认。",
-    "The connection to the server has been configured successfully. As the next step,": "与服务器的连接已配置成功。下一步，",
-    "Ui.SetupWizard.RebuildEverythingP2P.ConfirmLocalReset": "我明白这只会重置本设备的本地同步数据库。",
+    "You can enable this setting to process the files with size mismatches, these files can be created by some APIs or integrations.": "启用此设置后可以处理大小不匹配的文件，这些文件可能由某些 API 或集成创建。",
     "You should create a new synchronisation destination and rebuild your data there.": "你应当创建一个新的同步目标，并在那里重建数据。",
-    "CouchDB validates the database name when you connect. The name must not be empty.": "CouchDB 会在连接时校验数据库名称。名称不能为空。",
-    "the latest synchronisation data will be downloaded from the server to this device.": "最新的同步数据将从服务器下载到本设备。",
-    "I am setting up a new server for the first time / I want to reset my existing server.": "我是第一次设置新服务器／我想重置现有服务器。",
-    "(e.g., setting up for the first time on a new smartphone, starting from a clean slate)": "（例如：在新手机上首次设置，从零开始）",
-    "Ui.Common.LocalDatabaseInitialisationFailed": "Self-hosted LiveSync 无法同步。请生成报告以查看详细日志。",
-    "Please select the button below to restart and proceed to the data fetching confirmation.": "请点击下方按钮重启，然后进入数据获取确认。",
-    "(e.g., immediately after restoring on another computer, or having recovered from a backup)": "（例如：在另一台电脑上还原之后，或从备份恢复之后）",
-    "the local database, that is to say the synchronisation information, must be reconstituted.": "本地数据库（即同步信息）必须重建。",
-    "The Setup-URI does not appear to be valid. Please check that you have copied it correctly.": "设置 URI 似乎无效。请检查是否完整复制。",
-    "I understand that all changes made on other smartphones or computers possibly could be lost.": "我明白在其他手机或电脑上所做的更改可能会丢失。",
-    "This setting must be the same even when connecting to multiple synchronisation destinations.": "即使连接到多个同步目标，此设置也必须保持一致。",
-    "On the source device, from the command palette, run the 'Show settings as a QR code' command.": "在源设备上，从命令面板运行「Show settings as a QR code」命令。",
-    "This can isolate your connections between devices. Use the same Room ID for the same devices.": "这可以隔离设备之间的连接。同一组设备请使用相同的房间 ID。",
-    "the synchronisation data on the server will be built based on the current data on this device.": "服务器上的同步数据将基于本设备的当前数据构建。",
-    "Ui.SetupWizard.OutroNewP2PUser.Question": "请点击下方按钮重启，然后进入本地初始化确认。",
-    "On this device, switch to the camera app or use a QR code scanner to scan the displayed QR code.": "在本设备上切换到相机应用，或使用二维码扫描器扫描显示的二维码。",
-    "Ui.SetupWizard.RebuildEverythingP2P.Note": "初始化后请保持本设备在线，以便其他设备从它获取库。",
-    "After that, synchronise to a brand new vault on each other device with the new remote one by one.": "之后，在其他设备上逐个用新的远端同步到一个全新的库。",
-    "Please enter the details required to connect to your S3/MinIO/R2 compatible object storage service.": "请填写连接到你的 S3/MinIO/R2 兼容对象存储服务所需的信息。",
-    "Note that the Group ID is not limited to the generated format; you can use any string as the Group ID.": "请注意，组 ID 不限于生成的格式；你可以使用任意字符串作为组 ID。",
-    "The remote is already set up, and the configuration is compatible (or got compatible by this operation).": "远端已设置好，且配置兼容（或经此操作后已兼容）。",
-    "moduleCheckRemoteSize.noticeExceeded": "远端存储体积为 ${measuredSize}，已超过配置的提醒阈值 ${notifySize}。{HERE}",
-    "AddOn Module (ConfigSync) has not been loaded. This is very unexpected situation. Please report this issue.": "附加模块（ConfigSync）未能加载。这是非常意外的情况。请报告此问题。",
-    "Ui.Common.SomeFilesCouldNotBeSynchronised": "并非所有文件都能同步。请检查受影响的文件。生成报告以查看详细日志。",
-    "Initialise journal sent history. On the next sync, every item except this device received will be sent again.": "初始化日志的已发送历史。下次同步时，除本设备已接收的项外，其余都会重新发送。",
-    "AddOn Module (HiddenFileSync) has not been loaded. This is very unexpected situation. Please report this issue.": "附加模块（HiddenFileSync）未能加载。这是非常意外的情况。请报告此问题。",
-    "It is strongly advised to create a backup before proceeding. Continuing without a backup may lead to data loss.": "强烈建议在继续之前先做备份。没有备份继续可能导致数据丢失。",
-    "This is an extremely powerful operation. We strongly recommend that you copy your Vault folder to a safe location.": "这是一项影响极大的操作。我们强烈建议先把库文件夹复制到安全位置。",
-    "Initialise journal received history. On the next sync, every item except this device sent will be downloaded again.": "初始化日志的已接收历史。下次同步时，除本设备已发送的项外，其余都会重新下载。",
-    "Hidden file synchronization have been temporarily disabled. Please enable them after the fetching, if you need them.": "隐藏文件同步已被临时停用。获取完成后如需使用，请重新启用。",
-    "If \"Auto Start P2P Connection\" is enabled, the P2P connection will be started automatically when the plug-in launches.": "如果启用了「自动启动 P2P 连接」，插件启动时会自动建立 P2P 连接。",
-    "(Select this if you already have another synchronising device.) This option adds this device to the same synchronisation.": "（如果你已有另一台正在同步的设备，请选择此项。）此选项会把本设备加入同一个同步。",
-    "Ui.SetupWizard.ApplySettingsInitialisation.FetchOptionP2PDesc": "重启后选择一台在线的源设备。本设备的本地 LiveSync 数据库将从该源设备重建。",
-    "If you reached the payload size limit when using IBM Cloudant, please decrease batch size and batch limit to a lower value.": "如果在使用 IBM Cloudant 时达到载荷大小上限，请把批量大小和批量上限调低。",
-    "Note that you can generate a new Setup URI by running the \"Copy settings as a new Setup URI\" command in the command palette.": "请注意，你可以在命令面板中运行「Copy settings as a new Setup URI」命令来生成新的设置 URI。",
-    "Ui.SetupWizard.ApplySettingsInitialisation.RebuildOptionP2PDesc": "用本库中当前的文件重建本设备的本地 LiveSync 数据库。这不会覆盖其他设备。",
-    "Device name to identify the device. Please use shorter one for the stable peer detection, i.e., \"iphone-16\" or \"macbook-2021\".": "用于标识设备的名称。为了对等方检测更稳定，请使用较短的名字，例如「iphone-16」或「macbook-2021」。",
-    "Please enter the Setup URI that was generated during server installation or on another device, along with the vault passphrase.": "请输入在服务器安装时或在其他设备上生成的设置 URI，以及库的密码短语。",
-    "I understand that other devices will no longer be able to synchronise, and will need to be reset the synchronisation information.": "我明白其他设备将无法继续同步，需要重置同步信息。",
-    "For HS256/HS512 algorithms, provide the shared secret key. For ES256/ES512 algorithms, provide the pkcs8 PEM-formatted private key.": "对于 HS256/HS512 算法，请提供共享密钥。对于 ES256/ES512 算法，请提供 pkcs8 PEM 格式的私钥。",
-    "moduleLog.pathComponentTooLong": "此路径中包含超过 ${maxBytes} 个 UTF-8 字节的文件或文件夹名。在某些 Android 和 Linux 文件系统上可能无法正常工作。",
-    "The connection test cannot add a signalling relay while P2P is active. Use the active relay settings, or disconnect P2P before testing.": "P2P 处于活动状态时，连接测试无法添加信令中继。请使用当前生效的中继设置，或先断开 P2P 再测试。",
-    "Ui.SetupWizard.ApplySettingsInitialisation.Guidance": "这些设置变更会改变同步数据的解释方式。请在重启后连同初始化操作一起应用。",
-    "liveSyncReplicator.mismatchedTweakDetected": "检测到设备之间的配置存在不一致。执行一次手动复制将尝试解决此问题。",
-    "Saving without a successful connection test keeps this profile, but automatic synchronisation may fail until the connection is corrected.": "未通过连接测试就保存会保留此档案，但在连接修正之前，自动同步可能会失败。",
-    "If you want to use `LiveSync`, you should broadcast changes. All `watching` peers which detects this will start the replication for fetching.": "如果要使用 `LiveSync`，你应当广播变更。所有检测到变更的 `watching` 对等方都会启动复制以获取数据。",
-    "Ui.SetupWizard.OutroNewP2PUser.GuidanceNotice": "P2P 没有中心服务器副本可供覆盖。此步骤只准备本设备；当其他设备获取初始数据时，请保持本设备在线。",
-    "Ui.SetupWizard.ApplySettingsInitialisation.RemoteVerificationGuidance": "无法用当前的凭据和加密设置验证所配置的远端。继续可能导致重启后获取失败。",
-    "Ui.SetupWizard.OutroNewP2PUser.GuidancePrimary": "点对点连接已配置成功。接下来，将用本库中当前的文件构建本地 LiveSync 数据库。",
-    "Restarting Obsidian is strongly recommended. Until restart, some changes may not take effect, and display may be inconsistent. Are you sure to restart now?": "强烈建议重启 Obsidian。在重启之前，部分更改可能不会生效，显示也可能不一致。确定现在重启吗？",
-    "Ui.SetupWizard.ApplySettingsInitialisation.RebuildOptionDesc": "用本库中当前的文件重建本地和远端数据库。其他正在同步的设备之后必须重置其本地同步。",
-    "Ui.SetupWizard.ApplySettingsInitialisation.FetchOptionDesc": "重启后，用当前的远端同步数据重建本设备的本地数据库。库中的文件随后会与该数据核对合并。",
-    "The Group ID and passphrase are used to identify your group of devices. Make sure to use the same Group ID and passphrase on all devices you want to synchronise.": "组 ID 和密码短语用于标识你的设备组。请确保所有要同步的设备都使用相同的组 ID 和密码短语。",
-    "Changing this setting requires migrating existing data (a bit time may be taken) and restarting Obsidian. Please make sure to back up your data before proceeding.": "更改此设置需要迁移现有数据（可能需要一些时间）并重启 Obsidian。请务必在继续之前备份数据。",
-    "Furthermore, if conflicts are already present in the server data, they will be synchronised to this device as they are, and you will need to resolve them locally.": "此外，如果服务器数据中已存在冲突，它们会原样同步到本设备，你需要在本设备上解决。",
-    "Selecting this option will result in this device joining the existing server. You need to fetching the existing synchronisation data from the server to this device.": "选择此选项后，本设备将加入现有服务器。你需要把服务器上已有的同步数据获取到本设备。",
-    "In most cases, you should stick with the default algorithm (${algorithm}), This setting is only required if you have an existing Vault encrypted in a different format.": "大多数情况下，你应当沿用默认算法（${algorithm}）。只有当你有以其他格式加密的现有库时，才需要此项设置。",
-    "Selecting this option will result in the current data on this device being used to initialise the server. Any existing data on the server will be completely overwritten.": "选择此选项后，将用本设备的当前数据来初始化服务器。服务器上现有的数据将被完全覆盖。",
-    "TURN server settings are only necessary if you are behind a strict NAT or firewall that prevents direct P2P connections. In most cases, you can leave these fields blank.": "只有当处于阻止直接 P2P 连接的严格 NAT 或防火墙之后时，才需要 TURN 服务器设置。大多数情况下这些字段可以留空。",
-    "If you want to store the data in a specific folder within the bucket, you can specify a folder prefix here. Otherwise, leave it blank to store data at the root of the bucket.": "如果想把数据存放在存储桶内的指定文件夹中，可以在此指定文件夹前缀。否则留空，数据将存放在存储桶根目录。",
-    ", please select the option that best describes the current state of your Vault. The application will then check your files in the most appropriate way based on your selection.": "，请选择最符合你库当前状态的选项。程序会根据你的选择，用最合适的方式检查你的文件。",
-    "Ui.SetupWizard.ApplySettingsInitialisation.BypassGuidance": "仅应用这些设置可能使本设备与其现有同步数据不兼容。请仅在确认无需重建时使用。",
-    "Ui.SetupWizard.RebuildEverythingP2P.Guidance": "此操作会丢弃本设备的本地 LiveSync 数据库，并用本库中当前的文件重建。它不会删除或覆盖其他设备上的数据。",
-    "Also, please note that if you are using Peer-to-Peer synchronization, this configuration will be used when you switch to other methods and connect to a remote server in the future.": "另外请注意，如果你正在使用点对点同步，当你日后切换到其他方式并连接远端服务器时，将使用此配置。",
-    "Therefore, we ask that you exercise extreme caution when configuring server information manually. If an incorrect passphrase is entered, the data on the server will become corrupted.": "因此，我们要求你在手动配置服务器信息时格外小心。如果输入了错误的密码短语，服务器上的数据将会损坏。",
-    "TweakMismatchResolve.Message.AutoAcceptCompatibleUndefined": "\n各设备的设置似乎存在差异。你现在可以自动应用兼容的更改到这些配置。\n是否要启用此「自动接受」设置？",
-    "After restarting, the database on this device will be rebuilt using data from the server. If there are any unsynchronised files in this vault, conflicts may occur with the server data.": "重启后，将用服务器上的数据重建本设备的数据库。如果本库中有未同步的文件，可能会与服务器数据产生冲突。",
-    "If you have unsynchronised changes in your Vault on this device, they will likely diverge from the server's versions after the reset. This may result in a large number of file conflicts.": "如果本设备的库中有未同步的更改，重置后它们很可能与服务器上的版本产生分歧。这可能导致大量文件冲突。",
-    "Please be aware that the End-to-End Encryption passphrase is not validated until the synchronisation process actually commences. This is a security measure designed to protect your data.": "请注意，端到端加密密码短语要等到同步过程真正开始后才会被校验。这是为保护你的数据而设计的安全措施。",
-    "This optional check uses Obsidian's internal request API and sends the credentials above to the CouchDB server. Use it only with a server you trust; administrator access may be required.": "此可选检查使用 Obsidian 的内部请求 API，并把上面的凭据发送到 CouchDB 服务器。请仅对你信任的服务器使用；可能需要管理员权限。",
-    "After restarting, the data on this device will be uploaded to the server as the 'master copy'. Please be aware that any unintended data currently on the server will be completely overwritten.": "重启后，本设备上的数据将作为「主副本」上传到服务器。请注意，服务器上现有的任何非预期数据都会被完全覆盖。",
-    "This will rebuild the local database on this device using the most recent data from the server. This action is designed to resolve synchronisation inconsistencies and restore correct functionality.": "这将用服务器上的最新数据重建本设备的本地数据库。此操作旨在解决同步不一致并恢复正常功能。",
-    "In this scenario, Self-hosted LiveSync will recreate metadata for every file and deliberately generate conflicts. Where the file content is identical, these conflicts will be resolved automatically.": "在此情形下，Self-hosted LiveSync 会为每个文件重建元数据并有意制造冲突。若文件内容完全相同，这些冲突将被自动解决。",
-    "This first setup has several short steps because it confirms encryption, the connection method, and which device provides the initial data. Once it is complete, additional devices can reuse a Setup URI.": "首次设置分为几个简短步骤，因为它要确认加密方式、连接方式，以及由哪台设备提供初始数据。完成后，其他设备可以复用设置 URI。",
-    "We recommend that you copy your Vault folder to a safe location. This will provide a safeguard in case a large number of conflicts arise, or if you accidentally synchronise with an incorrect destination.": "我们建议你把库文件夹复制到安全位置。这样在出现大量冲突，或不小心同步到错误目标时，能多一层保障。",
-    "The IndexedDB adapter often offers superior performance in certain scenarios, but it has been found to cause memory leaks when used with LiveSync mode. When using LiveSync mode, please use IDB adapter instead.": "IndexedDB 适配器在某些场景下性能更好，但已发现与 LiveSync 模式同用时会造成内存泄漏。使用 LiveSync 模式时，请改用 IDB 适配器。",
-    "Changing the encryption algorithm will prevent access to any data previously encrypted with a different algorithm. Ensure that all your devices are configured to use the same algorithm to maintain access to your data.": "更改加密算法将导致无法访问此前用其他算法加密的数据。请确保所有设备都配置为使用相同算法，以保持对数据的访问。",
-    "Unless you are certain, selecting this options is bit dangerous. It assumes that the server configuration is compatible with this device. If this is not the case, data loss may occur. Please ensure you know what you are doing.": "除非你非常确定，否则选择此选项有些危险。它假定服务器配置与本设备兼容。若不兼容，可能会发生数据丢失。请确保你清楚自己在做什么。",
-    "This procedure will first delete all existing synchronisation data from the server. Following this, the server data will be completely rebuilt, using the current state of your Vault on this device (including its local database) as": "此操作会先删除服务器上所有现有的同步数据。随后，服务器数据将被完全重建，以本设备上你库的当前状态（包括其本地数据库）作为",
-    "If you cannot avoid CORS issues, you might want to try this option. It uses Obsidian's internal API to communicate with the S3 server. Not compliant with web standards, but works. Note that this might break in future Obsidian versions.": "如果无法避开 CORS 问题，可以试试此选项。它使用 Obsidian 的内部 API 与 S3 服务器通信。不符合 Web 标准，但可用。请注意，未来的 Obsidian 版本可能会使其失效。",
-    "If you cannot avoid CORS issues, you might want to try this option. It uses Obsidian's internal API to communicate with the CouchDB server. Not compliant with web standards, but works. Note that this might break in future Obsidian versions.": "如果无法避开 CORS 问题，可以试试此选项。它使用 Obsidian 的内部 API 与 CouchDB 服务器通信。不符合 Web 标准，但可用。请注意，未来的 Obsidian 版本可能会使其失效。",
     "You should perform this operation only in exceptional circumstances, such as when the server data is completely corrupted, when changes on all other devices are no longer needed, or when the database size has become unusually large in comparison to the Vault size.": "你只应在特殊情况下执行此操作，例如服务器数据完全损坏、其他所有设备上的更改都不再需要，或数据库体积相对于库体积异常庞大时。",
-    "JWT (JSON Web Token) authentication allows you to securely authenticate with the CouchDB server using tokens. Ensure that your CouchDB server is configured to accept JWTs and that the provided key and settings match the server's configuration. Incidentally, I have not verified it very thoroughly.": "JWT（JSON Web Token）身份验证让你可以用令牌安全地通过 CouchDB 服务器验证身份。请确保你的 CouchDB 服务器已配置为接受 JWT，且所提供的密钥和设置与服务器配置相符。顺带一提，我并没有非常彻底地验证过它。",
-    "Enabling end-to-end encryption ensures that your data is encrypted on your device before being sent to the remote server. This means that even if someone gains access to the server, they won't be able to read your data without the passphrase. Make sure to remember your passphrase, as it will be required to decrypt your data on other devices.": "启用端到端加密可确保数据在发送到远端服务器之前已在本设备上加密。这意味着即使有人获得了服务器的访问权限，没有密码短语也无法读取你的数据。请务必记住你的密码短语，因为在其他设备上解密数据时需要用到它。",
-    "Obfuscating properties (e.g., path of file, size, creation and modification dates) adds an additional layer of security by making it harder to identify the structure and names of your files and folders on the remote server. This helps protect your privacy and makes it more difficult for unauthorized users to infer information about your data.": "混淆属性（例如文件路径、大小、创建和修改日期）通过让远端服务器上更难识别你文件和文件夹的结构与名称，增加了一层额外的安全保障。这有助于保护你的隐私，也让未授权用户更难推断出关于你数据的信息。"
+    "you wanted(Thank you)!": "你要求的操作（谢谢）！"
 }
diff --git a/src/common/messagesYAML/en.yaml b/src/common/messagesYAML/en.yaml
index 134517bb..25fc039b 100644
--- a/src/common/messagesYAML/en.yaml
+++ b/src/common/messagesYAML/en.yaml
@@ -2474,3 +2474,156 @@ You should perform this operation only in exceptional circumstances, such as whe
 "Synchronisation Issues Detected": "Synchronisation Issues Detected"
 "Use the detailed flow": "Use the detailed flow"
 "We are about to retrieve the remote data.\n\nFirstly, how shall we handle the data retrieved from this remote source?\n\n- **${NEWER_WINS}**: Compares the modified time of files and takes the newer one.\n  If you have been using Self-hosted LiveSync and have made changes on multiple devices, this option may be suitable for you as it tries to merge changes based on modified time.\n- **${REMOTE_WINS}**: Remote data is the source of truth.\n  If you are new to using Self-hosted LiveSync. This option may be easiest to understand and get started with.\n  It will overwrite all your local files with the remote data, so please make sure you have a backup if there is any important data in your vault.\n- **${DETAILED}**: Opens the detailed setup wizard.\n  If you want to have more control over the synchronisation process, or want to review the changes before applying, you can choose this option to use the detailed flow.": "We are about to retrieve the remote data.\n\nFirstly, how shall we handle the data retrieved from this remote source?\n\n- **${NEWER_WINS}**: Compares the modified time of files and takes the newer one.\n  If you have been using Self-hosted LiveSync and have made changes on multiple devices, this option may be suitable for you as it tries to merge changes based on modified time.\n- **${REMOTE_WINS}**: Remote data is the source of truth.\n  If you are new to using Self-hosted LiveSync. This option may be easiest to understand and get started with.\n  It will overwrite all your local files with the remote data, so please make sure you have a backup if there is any important data in your vault.\n- **${DETAILED}**: Opens the detailed setup wizard.\n  If you want to have more control over the synchronisation process, or want to review the changes before applying, you can choose this option to use the detailed flow."
+SettingService.ConfigurationPassphraseDeviceLocalDescription:
+    This passphrase stays on this device. When another device needs to decrypt
+    protected settings without a saved key, enter the same passphrase at
+    start-up.
+SettingService.ConfigurationPassphraseTitle: Configuration passphrase
+SettingService.ConfigurationPassphraseRetryTitle: Configuration could not be
+    decrypted. Enter the configuration passphrase again.
+SettingService.ConfigurationPassphraseCancelled: Configuration passphrase entry
+    was cancelled or unavailable. Start-up was stopped; saved settings were
+    retained.
+SettingService.ConfigurationEncryptionSaveFailed: Configuration encryption could
+    not be saved. Verify the saved settings and device key before retrying.
+SettingService.ConfigurationPassphraseRollbackFailed: The configuration
+    passphrase could not be restored after a write failure. Verify the saved
+    settings and device key before retrying.
+SettingService.ConfigurationCouldNotBeDecrypted: Existing configuration could
+    not be decrypted. The configuration key was not changed.
+Active Remote Type: Active Remote Type
+Application ID: Application ID
+Auto-accept compatible tweak mismatches: Auto-accept compatible tweak mismatches
+Automatically accepts mismatches that are compatible but potentially lossy by comparing tweak modification times.:
+    Automatically accepts mismatches that are compatible but potentially lossy
+    by comparing tweak modification times.
+Automatically broadcast changes to connected peers: Automatically broadcast changes to connected peers
+Automatically start P2P connection on launch: Automatically start P2P connection on launch
+Chunk Splitter: Chunk Splitter
+Chunk revisions are always derived from their content. This stored key is retained only for compatibility.:
+    Chunk revisions are always derived from their content. This stored key is
+    retained only for compatibility.
+Content-derived chunk revisions (obsolete setting): Content-derived chunk revisions (obsolete setting)
+"Custom headers for requesting the CouchDB. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": |-
+    Custom headers for requesting the CouchDB. e.g. `x-custom-header1: value1
+     x-custom-header2: value2`
+"Custom headers for requesting the bucket. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": |-
+    Custom headers for requesting the bucket. e.g. `x-custom-header1: value1
+     x-custom-header2: value2`
+Desktop only; uses more battery and network.: Desktop only; uses more battery and network.
+Effectively a directory. Should end with `/`. e.g., `vault-name/`.: Effectively a directory. Should end with `/`. e.g., `vault-name/`.
+Enable Developers' Debug Tools (If available).: Enable Developers' Debug Tools (If available).
+Enable P2P Synchronization: Enable P2P Synchronization
+Enable forcePathStyle: Enable forcePathStyle
+Enable per-file customization sync: Enable per-file customization sync
+Encrypt internal file Properties: Encrypt internal file Properties
+Encrypt file properties (paths, times, sizes, and Chunk references) used by Hidden File Sync and Customisation Sync. This affects future writes; manually rebuild the remote database to protect existing properties. Requires E2EE V2, Property Encryption, and compatible clients on every device.:
+    Encrypt file properties (paths, times, sizes, and Chunk references) used by
+    Hidden File Sync and Customisation Sync. This affects future writes;
+    manually rebuild the remote database to protect existing properties.
+    Requires E2EE V2, Property Encryption, and compatible clients on every
+    device.
+Encryption passphrase. If changed, you should overwrite the server's database with the new (encrypted) files.:
+    Encryption passphrase. If changed, you should overwrite the server's
+    database with the new (encrypted) files.
+End-to-End Encryption Algorithm: End-to-End Encryption Algorithm
+File prefix on the bucket: File prefix on the bucket
+Files with modification times greater than this value (in seconds since the Unix epoch) will not have their events reflected. Set to 0 to disable this limit.:
+    Files with modification times greater than this value (in seconds since the
+    Unix epoch) will not have their events reflected. Set to 0 to disable this
+    limit.
+If enabled, changes will be automatically broadcasted to all connected peers. Notified peers will start fetching the changes.:
+    If enabled, changes will be automatically broadcasted to all connected
+    peers. Notified peers will start fetching the changes.
+If enabled, efficient per-file customization sync will be used. A minor migration is required when enabling this feature, and all devices must be updated to v0.23.18. Enabling this feature will result in losing compatibility with older versions.:
+    If enabled, efficient per-file customization sync will be used. A minor
+    migration is required when enabling this feature, and all devices must be
+    updated to v0.23.18. Enabling this feature will result in losing
+    compatibility with older versions.
+If enabled, the P2P connection will be automatically started when the application launches.:
+    If enabled, the P2P connection will be automatically started when the
+    application launches.
+If enabled, the file properties will be encrypted in the remote database. This is useful for protecting sensitive information in file paths, sizes, and IDs of its chunks. If you are using V1 E2EE, this only obfuscates the file path.:
+    If enabled, the file properties will be encrypted in the remote database.
+    This is useful for protecting sensitive information in file paths, sizes,
+    and IDs of its chunks. If you are using V1 E2EE, this only obfuscates the
+    file path.
+If enabled, the forcePathStyle option will be used for bucket operations.: If enabled, the forcePathStyle option will be used for bucket operations.
+If enabled, the plugin will not attempt to connect to the remote database even if the chunk was not found locally.:
+    If enabled, the plugin will not attempt to connect to the remote database
+    even if the chunk was not found locally.
+If enabled, the request API will be used to avoid `inevitable` CORS problems. This is a workaround and may not work in all cases. PLEASE READ THE DOCUMENTATION BEFORE USING THIS OPTION. This is a less-secure option.:
+    If enabled, the request API will be used to avoid `inevitable` CORS
+    problems. This is a workaround and may not work in all cases. PLEASE READ
+    THE DOCUMENTATION BEFORE USING THIS OPTION. This is a less-secure option.
+If this enabled, JWT will be used for authentication.: If this enabled, JWT will be used for authentication.
+Internal timestamp for resolving compatible tweak mismatches.: Internal timestamp for resolving compatible tweak mismatches.
+Keep replication active in the background: Keep replication active in the background
+Key ID: Key ID
+Keypair or pre-shared key: Keypair or pre-shared key
+Last tweak modified timestamp: Last tweak modified timestamp
+Longest chunk line threshold value (Not Configurable from the UI Now).: Longest chunk line threshold value (Not Configurable from the UI Now).
+MB per request: MB per request
+Maximum file modification time for reflected file events: Maximum file modification time for reflected file events
+Maximum request size for manually resending chunks: Maximum request size for manually resending chunks
+Minimum Chunk Size (Not Configurable from the UI Now).: Minimum Chunk Size (Not Configurable from the UI Now).
+Move remotely deleted files to the trash, instead of deleting. (This setting is ineffective from Obsidian v1.7.2 onwards, as deletion always respects your Obsidian preferences.):
+    Move remotely deleted files to the trash, instead of deleting. (This setting
+    is ineffective from Obsidian v1.7.2 onwards, as deletion always respects
+    your Obsidian preferences.)
+Now we can choose how to split the chunks; V3 is the most efficient. If you have troubled, please make this Default or Legacy.:
+    Now we can choose how to split the chunks; V3 is the most efficient. If you
+    have troubled, please make this Default or Legacy.
+Please use V2, V1 is deprecated and will be removed in the future, It was not a very appropriate algorithm. Only for compatibility V1 is kept.:
+    Please use V2, V1 is deprecated and will be removed in the future, It was
+    not a very appropriate algorithm. Only for compatibility V1 is kept.
+Process files even if seems to be corrupted: Process files even if seems to be corrupted
+Rotation Duration: Rotation Duration
+Signalling Relays: Signalling Relays
+Subject (whoami): Subject (whoami)
+TURN Servers: TURN Servers
+The Application ID for P2P connection. This should be same among your devices. Default is 'self-hosted-livesync' and could not be modified from the UI.:
+    The Application ID for P2P connection. This should be same among your
+    devices. Default is 'self-hosted-livesync' and could not be modified from
+    the UI.
+The Nostr relay servers to establish connections for P2P connections. Multiple servers can be separated by commas.:
+    The Nostr relay servers to establish connections for P2P connections.
+    Multiple servers can be separated by commas.
+The Passphrase for P2P connection. This should be same among your devices.: The Passphrase for P2P connection. This should be same among your devices.
+The Room ID for P2P connection. This should be same among your devices.: The Room ID for P2P connection. This should be same among your devices.
+The Rotation duration of token in minutes. Each generated tokens will be valid only within this duration.:
+    The Rotation duration of token in minutes. Each generated tokens will be
+    valid only within this duration.
+The TURN servers to use for P2P connections. Multiple servers can be separated by commas.:
+    The TURN servers to use for P2P connections. Multiple servers can be
+    separated by commas.
+The algorithm used for JWT authentication.: The algorithm used for JWT authentication.
+The credential/password for the TURN servers.: The credential/password for the TURN servers.
+The key (PSK in HSxxx in base64, or private key in ESxxx in PEM) used for JWT authentication.:
+    The key (PSK in HSxxx in base64, or private key in ESxxx in PEM) used for
+    JWT authentication.
+The key ID. this should be matched with CouchDB->jwt_keys->ALG:_`kid`.: The key ID. this should be matched with CouchDB->jwt_keys->ALG:_`kid`.
+The subject for JWT authentication. Mostly username.: The subject for JWT authentication. Mostly username.
+The username for the TURN servers.: The username for the TURN servers.
+Use JWT instead of Basic Authentication: Use JWT instead of Basic Authentication
+Use Only Local Chunks: Use Only Local Chunks
+Use Request API to avoid `inevitable` CORS problem: Use Request API to avoid `inevitable` CORS problem
+While enabled, it causes very performance impact but debugging replication testing and other features will be enabled. Please disable this if you have not read the source code. Requires restart of Obsidian. Sometimes there is no implementation.:
+    While enabled, it causes very performance impact but debugging replication
+    testing and other features will be enabled. Please disable this if you have
+    not read the source code. Requires restart of Obsidian. Sometimes there is
+    no implementation.
+You can enable this setting to process the files with size mismatches, these files can be created by some APIs or integrations.:
+    You can enable this setting to process the files with size mismatches, these
+    files can be created by some APIs or integrations.
+xxhash64 is the current default.: xxhash64 is the current default.
+Allow sleep during synchronisation: Allow sleep during synchronisation
+Allow the operating system to sleep while finite synchronisation operations are in progress.:
+    Allow the operating system to sleep while finite synchronisation operations
+    are in progress.
+Allow sleep during synchronisation on the desktop: Allow sleep during synchronisation on the desktop
+Desktop only. Allow sleep on this device even when the general option is disabled.:
+    Desktop only. Allow sleep on this device even when the general option is
+    disabled.
+Enable advanced mode: Enable advanced mode
+Enable power user mode: Enable power user mode
diff --git a/src/common/messagesYAML/zh.yaml b/src/common/messagesYAML/zh.yaml
index ff2cfb05..3eee2c4a 100644
--- a/src/common/messagesYAML/zh.yaml
+++ b/src/common/messagesYAML/zh.yaml
@@ -229,19 +229,19 @@ Doctor:
 
       ## ${name}
 
-      | Current | Ideal |
+      | 当前值 | 理想值 |
       |:---:|:---:|
       | ${current} | ${ideal} |
 
-      **Recommendation Level:** ${level}
+      **建议级别：** ${level}
 
-      ### Why this has been detected?
+      ### 为何检测到此问题？
 
       ${reason}
 
       ${note}
 
-      Fix this to the ideal value?
+      是否将其修正为理想值？
     Title: Self-hosted LiveSync 配置诊断
     TitleAlmostDone: 全部完成!
     TitleFix: 修复问题 ${current}/${total}
@@ -257,13 +257,8 @@ Doctor:
     SomeSkipped: 我们将某些问题留给了以后处理。是否要在下次启动时再次询问您？
   RULES:
     E2EE_V02500:
-      REASON: The End-to-End Encryption has got now more robust and faster. Also
-        because, the previous E2EE was found to be compromised in a re-conducted
-        code review. It should be applied as soon as possible. Really apologises
-        for your inconvenience. And, this setting is not forward compatible. All
-        synchronised devices must be updated to v0.25.0 or higher. Rebuilds are
-        not required and will be converted from the new transfer to the new
-        format, However, it is recommended to rebuild whenever possible.
+      REASON: 端到端加密现在变得更加稳健、更快。另外，之前的端到端加密在重新进行的代码审查中被发现存在安全漏洞，因此应尽快启用。对此给你带来的不便，我们深表歉意。此外，该设置不向前兼容，所有已同步的设备都必须更新到
+        v0.25.0 或更高版本。无需重建，数据会从新的传输方式转换为新格式，不过仍建议尽可能进行重建。
 Document History: 文档历史记录
 Duplicate: 复制
 Duplicate remote: 复制远端配置
@@ -438,9 +433,9 @@ K:
   Peer: Peer
   ScanCustomization: 扫描自定义
   short_p2p_sync: P2P同步(%{exp})
-  title_p2p_sync: Peer-to-Peer同步
+  title_p2p_sync: Peer-to-Peer 同步
 Keep empty folder: 保留空文件夹
-lang_def: Default
+lang_def: 默认
 lang-de: Deutsche
 lang-def: "%{lang_def}"
 lang-es: Español
@@ -866,7 +861,7 @@ obsidianLiveSyncSettingTab:
   okCorsOriginMatched: ✔ CORS 源正常
   okCorsOrigins: ✔ cors.origins 设置正确
   okEnableCors: ✔ httpd.enable_cors 设置正确
-  okEnableCorsChttpd: ✔ chttpd.enable_cors is ok.
+  okEnableCorsChttpd: ✔ chttpd.enable_cors 设置正确
   okMaxDocumentSize: ✔ couchdb.max_document_size 设置正确
   okMaxRequestSize: ✔ chttpd.max_http_request_size 设置正确
   okRequireValidUser: ✔ chttpd.require_valid_user 设置正确
@@ -985,15 +980,14 @@ P2P:
       some bugs, security issues, and other issues. Please use this feature at
       your own risk. Please contribute to the development of this feature.
     Summary: What is this  feature? (and some important notes, please read once)
-  NotEnabled: "%{title_p2p_sync} is not enabled. We cannot open a new connection."
-  P2PReplication: "%{P2P} Replication"
+  NotEnabled: "%{title_p2p_sync} 未启用，无法建立新连接。"
+  P2PReplication: "%{P2P} 复制"
   PaneTitle: "%{long_p2p_sync}"
-  ReplicatorInstanceMissing: P2P Sync replicator is not found, possibly not have
-    been configured or enabled.
-  SeemsOffline: Peer ${name} seems offline, skipped.
-  SyncAlreadyRunning: P2P Sync is already running.
-  SyncCompleted: P2P Sync completed.
-  SyncStartedWith: P2P Sync with ${name} have been started.
+  ReplicatorInstanceMissing: 未找到 P2P 同步复制器，可能尚未配置或未启用。
+  SeemsOffline: 对等方 ${name} 似乎处于离线状态，已跳过。
+  SyncAlreadyRunning: P2P 同步已在运行。
+  SyncCompleted: P2P 同步已完成。
+  SyncStartedWith: 已开始与 ${name} 的 P2P 同步。
 paneMaintenance:
   markDeviceResolvedAfterBackup: 请在完成备份后将此设备标记为已处理。
   remoteLockedAndDeviceNotAccepted: 远端数据库已锁定，且此设备尚未被接受。
@@ -1070,89 +1064,50 @@ Recreate missing chunks for all files: 为所有文件重建缺失的 chunks
 RedFlag:
   Fetch:
     Method:
-      Desc: >-
-        How do you want to fetch?
+      Desc: |-
+        你希望如何获取？
+        - %{RedFlag.Fetch.Method.FetchSafer}。
+          **低流量**，**高 CPU**，**低风险**
+          在以下情况下推荐使用：
+          - 文件可能不一致
+          - 文件数量不多
+        - %{RedFlag.Fetch.Method.FetchSmoother}。
+          **低流量**，**中等 CPU**，**低到中等风险**
+          在以下情况下推荐使用：
+          - 文件基本一致
+          - 你有大量文件。
+        - %{RedFlag.Fetch.Method.FetchTraditional}。
+          **高流量**，**低 CPU**，**低到中等风险**
 
-        - %{RedFlag.Fetch.Method.FetchSafer}.
-          **Low Traffic**, **High CPU**, **Low Risk**
-          Recommended if ...
-          - Files possibly inconsistent
-          - Files were not so much
-        - %{RedFlag.Fetch.Method.FetchSmoother}.
-          **Low Traffic**, **Moderate CPU**, **Low to Moderate Risk**
-          Recommended if ...
-          - Files probably consistent
-          - You have a lot of files.
-        - %{RedFlag.Fetch.Method.FetchTraditional}.
-          **High Traffic**, **Low CPU**, **Low to Moderate Risk**
-
-        >[!INFO]- Details
-
-        > ## %{RedFlag.Fetch.Method.FetchSafer}.
-
-        > **Low Traffic**, **High CPU**, **Low Risk**
-
-        > This option first creates a local database using existing local files
-        before fetching data from the remote source.
-
-        > If matching files exist both locally and remotely, only the
-        differences between them will be transferred.
-
-        > However, files present in both locations will initially be handled as
-        conflicted files. They will be resolved automatically if they are not
-        actually conflicted, but this process may take time.
-
-        > This is generally the safest method, minimizing data loss risk.
-
-        > ## %{RedFlag.Fetch.Method.FetchSmoother}.
-
-        > **Low Traffic**, **Moderate CPU**, **Low to Moderate Risk** (depending
-        operation)
-
-        > This option first creates chunks from local files for the database,
-        then fetches data. Consequently, only chunks missing locally are
-        transferred. However, all metadata is taken from the remote source.
-
-        > Local files are then compared against this metadata at launch. The
-        content considered newer will overwrite the older one (by modified
-        time). This outcome is then synchronised back to the remote database.
-
-        > This is generally safe if local files are genuinely the latest
-        timestamp. However, it can cause problems if a file has a newer
-        timestamp but older content (like the initial `welcome.md`).
-
-        > This uses less CPU and faster than
-        "%{RedFlag.Fetch.Method.FetchSafer}", but it may lead to data loss if
-        not used carefully.
-
-        > ## %{RedFlag.Fetch.Method.FetchTraditional}.
-
-        > **High Traffic**, **Low CPU**, **Low to Moderate Risk** (depending
-        operation)
-
-        > All things will be fetched from the remote.
-
-        > Similar to the %{RedFlag.Fetch.Method.FetchSmoother}, but all chunks
-        are fetched from the remote source.
-
-        > This is the most traditional way to fetch, typically consuming the
-        most network traffic and time. It also carries a similar risk of
-        overwriting remote files to the '%{RedFlag.Fetch.Method.FetchSmoother}'
-        option.
-
-        > However, it is often considered the most stable method because it is
-        the longest-established and most straightforward approach.
-      FetchSafer: Create a local database once before fetching
-      FetchSmoother: Create local file chunks before fetching
-      FetchTraditional: Fetch everything from the remote
-      Title: How do you want to fetch?
+        >[!INFO]- 详情
+        > ## %{RedFlag.Fetch.Method.FetchSafer}。
+        > **低流量**，**高 CPU**，**低风险**
+        > 此选项会先利用现有的本地文件创建本地数据库，然后再从远程源获取数据。
+        > 如果本地和远程存在相同的文件，则只会传输两者之间的差异。
+        > 但是，两边都存在的文件最初会被视为冲突文件。如果它们实际上并无冲突，将会被自动解决，不过这一过程可能需要一些时间。
+        > 这通常是最安全的方法，能将数据丢失风险降到最低。
+        > ## %{RedFlag.Fetch.Method.FetchSmoother}。
+        > **低流量**，**中等 CPU**，**低到中等风险**（视具体操作而定）
+        > 此选项会先根据本地文件为数据库创建数据块，然后再获取数据。因此，只会传输本地缺少的数据块。但是，所有元数据都取自远程源。
+        > 启动时，系统会将本地文件与这些元数据进行比较。被认为更新的内容（按修改时间判断）将覆盖较旧的版本。随后，这一结果会同步回远程数据库。
+        > 如果本地文件的时间戳确实是最新的，这通常是安全的。但如果某个文件的时间戳较新、内容却较旧（例如最初的 `welcome.md`），就可能引发问题。
+        > 这种方式比“%{RedFlag.Fetch.Method.FetchSafer}”占用更少的 CPU、速度更快，但如果使用不当，可能会导致数据丢失。
+        > ## %{RedFlag.Fetch.Method.FetchTraditional}。
+        > **高流量**，**低 CPU**，**低到中等风险**（视具体操作而定）
+        > 所有内容都将从远程获取。
+        > 与 %{RedFlag.Fetch.Method.FetchSmoother} 相似，但所有数据块都从远程源获取。
+        > 这是最传统的获取方式，通常消耗最多的网络流量和时间。与“%{RedFlag.Fetch.Method.FetchSmoother}”选项类似，它同样存在覆盖远程文件的风险。
+        > 不过，它通常被认为是最稳定的方法，因为它是历史最悠久、最直接的做法。
+      FetchSafer: 获取前先创建一次本地数据库
+      FetchSmoother: 获取前先创建本地文件的数据块
+      FetchTraditional: 从远程获取全部内容
+      Title: 你想如何获取？
   FetchRemoteConfig:
     Buttons:
-      Cancel: No, use local settings
-      Fetch: Yes, fetch and apply remote settings
-    Message: Do you want to fetch and apply remotely stored preference settings to
-      the device?
-    Title: Fetch Remote Configuration
+      Cancel: 否，使用本地设置
+      Fetch: 是，获取并应用远程设置
+    Message: 是否要获取远程保存的偏好设置，并将其应用到此设备？
+    Title: 获取远程配置
 Reduces storage space by discarding all non-latest revisions. This requires the same amount of free space on the remote server and the local client.: 通过丢弃所有非最新版本来减少存储空间。这需要远程服务器和本地客户端具备相同数量的可用空间。
 Reducing the frequency with which on-disk changes are reflected into the DB: 降低将磁盘上的更改反映到数据库中的频率
 Refresh: 刷新
@@ -1178,9 +1133,9 @@ Replicator:
   Dialogue:
     Locked:
       Action:
-        Dismiss: Cancel for reconfirmation
-        Fetch: Reset Synchronisation on This Device
-        Unlock: Unlock the remote database
+        Dismiss: 取消并重新确认
+        Fetch: 重置此设备上的同步
+        Unlock: 解锁远程数据库
       Message:
         _value: >
           Remote database is locked. This is due to a rebuild on one of the
@@ -1199,14 +1154,14 @@ Replicator:
             This method can only be used if we are already reliably synchronised by other replication methods. This does not simply mean that we have the same files. If you are not sure, you should avoid it.
           - %{Replicator.Dialogue.Locked.Action.Dismiss}
               This will cancel the operation. And we will asked again on next request.
-        Fetch: Fetch all has been scheduled. Plug-in will be restarted to perform it.
-        Unlocked: The remote database has been unlocked. Please retry the operation.
-      Title: Locked
+        Fetch: 已安排获取全部内容。插件将重启以执行该操作。
+        Unlocked: 远程数据库已解锁。请重试该操作。
+      Title: 已锁定
   Message:
-    Cleaned: Database cleaning up is in process. replication has been cancelled
-    InitialiseFatalError: No replicator is available, this is the fatal error.
-    Pending: Some file events are pending. Replication has been cancelled.
-    SomeModuleFailed: Replication has been cancelled by some module failure
+    Cleaned: 数据库清理正在进行中，复制已取消。
+    InitialiseFatalError: 没有可用的复制器，这是一个致命错误。
+    Pending: 部分文件事件仍在等待处理。复制已取消。
+    SomeModuleFailed: 由于某个模块出错，复制已取消。
     VersionUpFlash: An update has been detected. Please open the Settings dialogue
       and check the Change Log. Replication has been cancelled.
 Requires restart of Obsidian: 需要重启 Obsidian
@@ -1270,7 +1225,7 @@ Scram!: 紧急处置
 Seconds, 0 to disable: 秒,0为禁用
 Seconds. Saving to the local database will be delayed until this value after we stop typing or saving.: "秒。在我们停止输入或保存后,保存到本地数据库将延迟此值 "
 Secret Access Key: 私有访问密钥
-Secret Key: Secret Key
+Secret Key: 私有密钥
 Select active P2P remote: 选择生效的 P2P 远端
 Select All Shiny: 全选 Shiny
 Select Flagged Shiny: 选择已标记的 Shiny
@@ -1329,8 +1284,7 @@ Setting:
       Desc: 扫描数据库中未正确存储的文件。
 SettingTab:
   Message:
-    AskRebuild: Your changes require fetching from the remote database. Do you want
-      to proceed?
+    AskRebuild: 你的更改需要从远程数据库获取数据。是否继续？
 "Setup Complete: Preparing to Fetch Synchronisation Data": 设置完成：正在准备获取同步数据
 "Setup Complete: Preparing to Initialise Server": 设置完成：正在准备初始化服务器
 Setup URI dialog cancelled.: Setup URI 对话框已取消。
@@ -1338,71 +1292,53 @@ Setup-URI: 设置 URI
 Setup:
   Apply:
     Buttons:
-      ApplyAndFetch: Apply and Fetch
-      ApplyAndMerge: Apply and Merge
-      ApplyAndRebuild: Apply and Rebuild
-      Cancel: Discard and Cancel
-      OnlyApply: Only Apply
-    Message: >-
-      The new configuration is ready. Let us proceed to apply it.
+      ApplyAndFetch: 应用并获取
+      ApplyAndMerge: 应用并合并
+      ApplyAndRebuild: 应用并重建
+      Cancel: 丢弃并取消
+      OnlyApply: 仅应用
+    Message: |-
+      新配置已准备就绪，让我们继续应用它。
+      应用此配置有以下几种方式：
 
-      There are several ways to apply this:
-
-
-      - Apply and Fetch
-        Configure this device as a new client. After applying, synchronise from the remote server.
-      - Apply and Merge
-        Configure on a device that already has the file. It processes the local files and transfers the differences. Conflicts may arise.
-      - Apply and Rebuild
-        Rebuild the remote using local files. This is typically done if the server becomes corrupted or we wish to start from scratch.
-        Other devices will be locked and required to re-fetch.
-      - Only Apply
-        Apply only. Conflicts may arise if a rebuild is required.
-    Title: Apply new configuration from the ${method}
-    WarningRebuildRecommended: "NOTE: after adjusting the settings, it has been
-      determined that a rebuild is required; Just Import is not recommended."
+      - 应用并获取
+        将此设备配置为新客户端。应用后，从远程服务器同步。
+      - 应用并合并
+        在已有文件的设备上进行配置。它会处理本地文件并传输差异。可能会出现冲突。
+      - 应用并重建
+        使用本地文件重建远程。通常在服务器损坏或希望从头开始时使用。
+        其他设备将被锁定，并需要重新获取。
+      - 仅应用
+        仅应用配置。如果需要重建，可能会出现冲突。
+    Title: 从 ${method} 应用新配置
+    WarningRebuildRecommended: 注意：调整设置后，已判定需要重建；不推荐仅导入。
   Doctor:
     Buttons:
-      No: No, please use the settings in the URI as is
-      Yes: Yes, please consult the doctor
-    Message: >-
-      Self-hosted LiveSync has gradually become longer in history and some
-      recommended settings have changed.
+      No: 否，请按原样使用 URI 中的设置
+      Yes: 是，请运行诊断
+    Message: |-
+      Self-hosted LiveSync 已经历经多次演进，一些推荐设置也随之发生了变化。
 
+      现在正值设置阶段，是进行检查的好时机。
 
-      Now, setup is a very good time to do this.
-
-
-      Do you want to run Doctor to check if the imported settings are optimal
-      compared to the latest state?
-    Title: Do you want to consult the doctor?
+      你要运行诊断，检查导入的设置相对于最新状态是否最优吗？
+    Title: 要运行诊断吗？
   FetchRemoteConf:
     Buttons:
-      Fetch: Yes, please fetch the configuration
-      Skip: No, please use the settings in the URI
-    Message: >-
-      If we have already synchronised once with another device, the remote
-      database stores the suitable configuration values between the synchronised
-      devices. The plug-in would like to retrieve them for robust configuration.
+      Fetch: 是，请获取配置
+      Skip: 否，请使用 URI 中的设置
+    Message: |-
+      如果我们之前已经与另一台设备同步过，远程数据库会保存已同步设备之间适用的配置值。插件希望获取这些值，以便进行更可靠的配置。
 
+      但有一点必须确认：我们当前是否处于可以安全访问网络并获取这些设置的环境中？
 
-      However, we have to make sure the one thing. Are we currently in a
-      situation where we can access the network safely and retrieve the
-      settings?
-
-
-      Note: Mostly, you are safe to do this, that your remote database is hosted
-      with a SSL certificate, and your network is not compromised.
-    Title: Fetch configuration from remote database?
-  QRCode: >-
-    We have generated a QR code to transfer the settings. Please scan the QR
-    code with your phone or other device.
-
-    Note: The QR code is not encrypted, so be careful to open this.
-
+      注意：通常情况下，只要你的远程数据库使用了 SSL 证书，且网络未被入侵，执行此操作就是安全的。
+    Title: 要从远程数据库获取配置吗？
+  QRCode: |-
+    我们已生成用于传输设置的二维码。请使用手机或其他设备扫描该二维码。
+    注意：此二维码未加密，请谨慎打开。
 
     >[!FOR YOUR EYES ONLY]-
-
     > <div class="sls-qr">${qr_image}</div>
   RemoteE2EE:
     AdvancedTitle: 高级
@@ -1564,110 +1500,79 @@ TURN Username: TURN 用户名
 TweakMismatchResolve:
   Action:
     DisableAutoAcceptCompatible: 停用自动接受
-    Dismiss: Dismiss
+    Dismiss: 忽略
     EnableAutoAcceptCompatible: 启用自动接受
-    UseConfigured: Use configured settings
-    UseMine: Update remote database settings
-    UseMineAcceptIncompatible: Update remote database settings but keep as is
-    UseMineWithRebuild: Update remote database settings and rebuild again
-    UseRemote: Apply settings to this device
-    UseRemoteAcceptIncompatible: Apply settings to this device, but and ignore incompatibility
-    UseRemoteWithRebuild: Apply settings to this device, and fetch again
+    UseConfigured: 使用已配置的设置
+    UseMine: 更新远程数据库设置
+    UseMineAcceptIncompatible: 更新远程数据库设置，但忽略不兼容问题
+    UseMineWithRebuild: 更新远程数据库设置并再次重建
+    UseRemote: 将设置应用到此设备
+    UseRemoteAcceptIncompatible: 将设置应用到此设备，但忽略不兼容问题
+    UseRemoteWithRebuild: 将设置应用到此设备，并重新获取
   Message:
     AutoAcceptCompatibleUndefined: |-
 
       各设备的设置似乎存在差异。你现在可以自动应用兼容的更改到这些配置。
       是否要启用此「自动接受」设置？
-    Main: >-
+    Main: |-
 
-      The settings in the remote database are as follows. These values are
-      configured by other devices, which are synchronised with this device at
-      least once.
-
-
-      If you want to use these settings, please select
-      %{TweakMismatchResolve.Action.UseConfigured}.
-
-      If you want to keep the settings of this device, please select
-      %{TweakMismatchResolve.Action.Dismiss}.
+      远程数据库中的设置如下。这些值由与此设备至少同步过一次的其他设备配置。
 
+      如果你想使用这些设置，请选择 %{TweakMismatchResolve.Action.UseConfigured}。
+      如果你想保留此设备的设置，请选择 %{TweakMismatchResolve.Action.Dismiss}。
 
       ${table}
 
-
       >[!TIP]
-
-      > If you want to synchronise all settings, please use `Sync settings via
-      markdown` after applying minimal configuration with this feature.
-
+      > 如果你想同步全部设置，请先使用此功能应用最小配置，然后使用 `Sync settings via markdown`。
 
       ${additionalMessage}
     MainTweakResolving: |-
-      Your configuration has not been matched with the one on the remote server.
+      你的配置与远程服务器上的配置不一致。
 
-      Following configuration should be matched:
+      以下配置应当保持一致：
 
       ${table}
 
-      Let us know your decision.
+      请告知你的决定。
 
       ${additionalMessage}
     mineUpdated: 本设备的配置已调整。
     remoteUpdated: 远端存储的配置已更新。
     UseRemote:
-      WarningRebuildRecommended: >-
+      WarningRebuildRecommended: |-
 
         >[!NOTICE]
-
-        > Some changes are compatible but may consume extra storage and transfer
-        volumes. A rebuild is recommended. However, a rebuild may not be
-        performed at present, but may be implemented in future maintenance.
-
-        > ***Please ensure that you have time and are connected to a stable
-        network to apply!***
-      WarningRebuildRequired: >-
+        > 部分更改是兼容的，但可能会占用额外的存储空间和传输流量。建议进行重建。不过，也可以暂不重建，留待今后维护时再进行。
+        > ***应用前请确保你有充足的时间，并已连接到稳定的网络！***
+      WarningRebuildRequired: |-
 
         >[!WARNING]
-
-        > Some remote configurations are not compatible with the local database
-        of this device. Rebuilding the local database will be required.
-
-        > ***Please ensure that you have time and are connected to a stable
-        network to apply!***
-    WarningIncompatibleRebuildRecommended: >-
+        > 部分远程配置与本设备的本地数据库不兼容，将需要重建本地数据库。
+        > ***应用前请确保你有充足的时间，并已连接到稳定的网络！***
+    WarningIncompatibleRebuildRecommended: |-
 
       >[!NOTICE]
-
-      > We have detected that some of the values are different to make
-      incompatible the local database with the remote database.
-
-      > Some changes are compatible but may consume extra storage and transfer
-      volumes. A rebuild is recommended. However, a rebuild may not be performed
-      at present, but may be implemented in future maintenance.
-
-      > If you want to rebuild, it takes a few minutes or more. **Make sure it
-      is safe to perform it now.**
-    WarningIncompatibleRebuildRequired: >-
+      > 我们检测到部分值存在差异，导致本地数据库与远程数据库不兼容。
+      > 部分更改是兼容的，但可能会占用额外的存储空间和传输流量。建议进行重建。不过，也可以暂不重建，留待今后维护时再进行。
+      > 如果你要重建，大约需要几分钟或更长时间。**请先确认现在执行是安全的。**
+    WarningIncompatibleRebuildRequired: |-
 
       >[!WARNING]
-
-      > We have detected that some of the values are different to make
-      incompatible the local database with the remote database.
-
-      > Either local or remote rebuilds are required. Both of them takes a few
-      minutes or more. **Make sure it is safe to perform it now.**
+      > 我们检测到某些值存在差异，导致本地数据库与远程数据库不兼容。
+      > 需要重建本地或远程其中之一，两者都需要几分钟甚至更长时间。**请确保现在执行此操作是安全的。**
   Table:
     _value: |+
-      | Value name | This device | On Remote |
+      | 值名称 | 此设备 | 远程 |
       |: --- |: ---- :|: ---- :|
       ${rows}
 
     Row: "| ${name} | ${self} | ${remote} |"
   Title:
-    _value: Configuration Mismatch Detected
+    _value: 检测到配置不一致
     AutoAcceptCompatible: 可自动接受
-    TweakResolving: Configuration Mismatch Detected
-    UseRemoteConfig: Use Remote Configuration
+    TweakResolving: 检测到配置不一致
+    UseRemoteConfig: 使用远程配置
 Ui:
   Common:
     LocalDatabaseInitialisationFailed: Self-hosted LiveSync 无法同步。请生成报告以查看详细日志。
@@ -2028,3 +1933,131 @@ You can configure in the Obsidian Plugin Settings.: 你可以在 Obsidian 插件
 You should create a new synchronisation destination and rebuild your data there.: 你应当创建一个新的同步目标，并在那里重建数据。
 You should perform this operation only in exceptional circumstances, such as when the server data is completely corrupted, when changes on all other devices are no longer needed, or when the database size has become unusually large in comparison to the Vault size.: 你只应在特殊情况下执行此操作，例如服务器数据完全损坏、其他所有设备上的更改都不再需要，或数据库体积相对于库体积异常庞大时。
 you wanted(Thank you)!: 你要求的操作（谢谢）！
+Cancel all and reboot: 全部取消并重启
+Compare time and take newer: 比较时间并采用较新版本
+Conflict & Deletion Options: 冲突与删除选项
+Data retrieval scheduled: 已安排数据获取
+Delete local files if deleted on remote: 若远程已删除，则删除本地文件
+Delete local files if not on remote: 若远程不存在，则删除本地文件
+Finalise the process and resume normal operation: 完成流程并恢复正常运行
+"How should files that were deleted on other devices be handled?\n\n- **${NEWER_CLEANUP}**: Delete local files if they were deleted on remote.\n  This is useful if you want to keep your vault clean and consistent across devices, but please make sure you have a backup if there is already any important data in your vault.\n- **${NEWER_SYNC_ALL}**: Recreate remote files even if they were deleted on remote.\n  This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.": |-
+  其他设备上删除的文件应如何处理？
+
+  - **${NEWER_CLEANUP}**：如果文件在远程被删除，则删除本地文件。
+    如果你希望让各设备上的库保持整洁一致，这会很有用。但如果库中已有重要数据，请务必先做好备份。
+  - **${NEWER_SYNC_ALL}**：即使文件在远程已被删除，也重新创建远程文件。
+    此选项会保留你所有的本地文件，但如果有些文件只存在于本地而不存在于远程，可能会产生重复文件。同步完成后，你可以手动清理这些重复文件。
+How to handle extra existing local files?: 如何处理本地已有的多余文件？
+Keep local files even if deleted on remote: 即使远程已删除，也保留本地文件
+Keep local files even if not on remote: 即使远程不存在，也保留本地文件
+Overwrite all with remote files: 全部用远程文件覆盖
+Reboot to re-run the process: 重启以重新运行此流程
+"Since you have chosen to overwrite all local files with remote data, **how would you like to handle local files that are not present in the remote database?**\n\n- **${DELETE_ALL}**: Local-only files and remote-deleted files will be removed.\n  This option will make your local vault exactly the same as the remote database, but please make sure you have a backup if there is any important data in your vault.\n- **${DELETE_NONE}**: All existing local files will be preserved.\n  This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.": |-
+  由于你选择了用远程数据覆盖所有本地文件，**对于远程数据库中不存在的本地文件，你希望如何处理？**
+
+  - **${DELETE_ALL}**：仅存在于本地的文件和在远程已被删除的文件将被移除。
+    此选项会让你的本地库与远程数据库完全一致，但如果库中有重要数据，请务必先做好备份。
+  - **${DELETE_NONE}**：保留所有现有的本地文件。
+    此选项会保留你所有的本地文件，但如果某些文件仅存在于本地而不在远程，可能会产生重复文件。同步完成后，你可以手动清理这些重复文件。
+Some files failed to synchronise. What would you like to do?: 部分文件同步失败。你希望如何处理？
+Synchronisation Issues Detected: 检测到同步问题
+Use the detailed flow: 使用详细流程
+"We are about to retrieve the remote data.\n\nFirstly, how shall we handle the data retrieved from this remote source?\n\n- **${NEWER_WINS}**: Compares the modified time of files and takes the newer one.\n  If you have been using Self-hosted LiveSync and have made changes on multiple devices, this option may be suitable for you as it tries to merge changes based on modified time.\n- **${REMOTE_WINS}**: Remote data is the source of truth.\n  If you are new to using Self-hosted LiveSync. This option may be easiest to understand and get started with.\n  It will overwrite all your local files with the remote data, so please make sure you have a backup if there is any important data in your vault.\n- **${DETAILED}**: Opens the detailed setup wizard.\n  If you want to have more control over the synchronisation process, or want to review the changes before applying, you can choose this option to use the detailed flow.": |-
+  即将获取远程数据。
+
+  首先，应如何处理从此远程来源获取的数据？
+
+  - **${NEWER_WINS}**：比较文件的修改时间，并采用较新的那一个。
+    如果你一直在使用 Self-hosted LiveSync，并且在多台设备上做过更改，此选项可能适合你，因为它会尝试根据修改时间合并更改。
+  - **${REMOTE_WINS}**：以远程数据为准。
+    如果你是 Self-hosted LiveSync 的新用户，此选项可能最容易理解，也最容易上手。
+    它会用远程数据覆盖你所有的本地文件，因此如果库中有重要数据，请务必先备份。
+  - **${DETAILED}**：打开详细设置向导。
+    如果你希望更好地控制同步过程，或希望在应用前检查更改，可以选择此选项使用详细流程。
+SettingService.ConfigurationPassphraseDeviceLocalDescription: 此密码短语只保留在此设备上。当其他设备需要在没有已保存密钥的情况下解密受保护的设置时，请在启动时输入相同的密码短语。
+SettingService.ConfigurationPassphraseTitle: 配置密码短语
+SettingService.ConfigurationPassphraseRetryTitle: 无法解密配置。请重新输入配置密码短语。
+SettingService.ConfigurationPassphraseCancelled: 配置密码短语的输入已取消或不可用。启动已停止，已保存的设置已保留。
+SettingService.ConfigurationEncryptionSaveFailed: 无法保存配置加密。请在重试前检查已保存的设置和设备密钥。
+SettingService.ConfigurationPassphraseRollbackFailed: 写入失败后，无法恢复配置密码短语。请在重试前检查已保存的设置和设备密钥。
+SettingService.ConfigurationCouldNotBeDecrypted: 无法解密现有配置。配置密钥未更改。
+Active Remote Type: 当前使用的远程类型
+Application ID: 应用 ID
+Auto-accept compatible tweak mismatches: 自动接受兼容的调整值不一致
+Automatically accepts mismatches that are compatible but potentially lossy by comparing tweak modification times.: 通过比较调整值的修改时间，自动接受兼容但可能有损的配置不一致。
+Automatically broadcast changes to connected peers: 自动将更改广播给已连接的对等方
+Automatically start P2P connection on launch: 启动时自动启动 P2P 连接
+Chunk Splitter: 数据块分割器
+Chunk revisions are always derived from their content. This stored key is retained only for compatibility.: 数据块修订版本始终由其内容推导得出。此已存储的设置项仅为兼容而保留。
+Content-derived chunk revisions (obsolete setting): 基于内容的数据块修订（已过时的设置）
+"Custom headers for requesting the CouchDB. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": |-
+  用于请求 CouchDB 的自定义请求头。例如：`x-custom-header1: value1
+   x-custom-header2: value2`
+"Custom headers for requesting the bucket. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": |-
+  用于请求存储桶的自定义请求头。例如：`x-custom-header1: value1
+   x-custom-header2: value2`
+Desktop only; uses more battery and network.: 仅限桌面端；会消耗更多电量和网络流量。
+Effectively a directory. Should end with `/`. e.g., `vault-name/`.: 实际上是一个目录，应以 `/` 结尾，例如 `vault-name/`。
+Enable Developers' Debug Tools (If available).: 启用开发者调试工具（如可用）。
+Enable P2P Synchronization: 启用 P2P 同步
+Enable forcePathStyle: 启用 forcePathStyle
+Enable per-file customization sync: 启用逐文件自定义同步
+Encrypt internal file Properties: 加密内部文件属性
+Encrypt file properties (paths, times, sizes, and Chunk references) used by Hidden File Sync and Customisation Sync. This affects future writes; manually rebuild the remote database to protect existing properties. Requires E2EE V2, Property Encryption, and compatible clients on every device.: 加密隐藏文件同步和自定义同步所使用的文件属性（路径、时间、大小以及数据块引用）。此设置影响之后的写入；如需保护已有属性，请手动重建远程数据库。需要 E2EE
+  V2 和属性加密，并且每台设备上的客户端都需兼容。
+Encryption passphrase. If changed, you should overwrite the server's database with the new (encrypted) files.: 加密密码短语。如果更改，你应当用新的（加密后的）文件覆盖服务器上的数据库。
+End-to-End Encryption Algorithm: 端到端加密算法
+File prefix on the bucket: 存储桶中的文件前缀
+Files with modification times greater than this value (in seconds since the Unix epoch) will not have their events reflected. Set to 0 to disable this limit.: 修改时间大于此值（Unix 时间戳，单位为秒）的文件，其事件将不会被反映。设为 0 可禁用此限制。
+If enabled, changes will be automatically broadcasted to all connected peers. Notified peers will start fetching the changes.: 启用后，更改将自动广播给所有已连接的对等方。收到通知的对等方将开始获取这些更改。
+If enabled, efficient per-file customization sync will be used. A minor migration is required when enabling this feature, and all devices must be updated to v0.23.18. Enabling this feature will result in losing compatibility with older versions.: 启用后，将使用更高效的逐文件自定义同步。启用此功能需要进行一次小规模迁移，并且所有设备都必须更新到 v0.23.18。启用此功能后，将失去与旧版本的兼容性。
+If enabled, the P2P connection will be automatically started when the application launches.: 启用后，应用启动时将自动开始 P2P 连接。
+If enabled, the file properties will be encrypted in the remote database. This is useful for protecting sensitive information in file paths, sizes, and IDs of its chunks. If you are using V1 E2EE, this only obfuscates the file path.: 启用后，文件属性将在远程数据库中加密。这有助于保护文件路径、大小以及其数据块 ID 等敏感信息。如果你使用的是 V1 E2EE，则只会混淆文件路径。
+If enabled, the forcePathStyle option will be used for bucket operations.: 启用后，存储桶操作将使用 forcePathStyle 选项。
+If enabled, the plugin will not attempt to connect to the remote database even if the chunk was not found locally.: 启用后，即使本地未找到数据块，插件也不会尝试连接远程数据库。
+If enabled, the request API will be used to avoid `inevitable` CORS problems. This is a workaround and may not work in all cases. PLEASE READ THE DOCUMENTATION BEFORE USING THIS OPTION. This is a less-secure option.: 启用后，将使用 Request API 来避免 `inevitable` CORS
+  问题。这只是一种变通方法，并非在所有情况下都有效。请务必在使用此选项前阅读文档。这是一个安全性较低的选项。
+If this enabled, JWT will be used for authentication.: 启用后将使用 JWT 认证。
+Internal timestamp for resolving compatible tweak mismatches.: 用于解决兼容的调整值不一致问题的内部时间戳。
+Keep replication active in the background: 在后台保持复制运行
+Key ID: 密钥 ID
+Keypair or pre-shared key: 密钥对或预共享密钥
+Last tweak modified timestamp: 调整值最后修改时间戳
+Longest chunk line threshold value (Not Configurable from the UI Now).: 最长数据块行的阈值（目前无法在界面中配置）。
+MB per request: 每次请求的 MB 数
+Maximum file modification time for reflected file events: 可反映文件事件的最大修改时间
+Maximum request size for manually resending chunks: 手动重新发送数据块时的最大请求大小
+Minimum Chunk Size (Not Configurable from the UI Now).: 最小数据块大小（目前无法在界面中配置）。
+Move remotely deleted files to the trash, instead of deleting. (This setting is ineffective from Obsidian v1.7.2 onwards, as deletion always respects your Obsidian preferences.): 将远程删除的文件移至回收站，而不是直接删除。（此设置自 Obsidian v1.7.2 起不再生效，因为删除操作始终遵循你在 Obsidian
+  中的偏好设置。）
+Now we can choose how to split the chunks; V3 is the most efficient. If you have troubled, please make this Default or Legacy.: 现在可以选择数据块的分割方式；V3 效率最高。如果遇到问题，请将此项设为 Default 或 Legacy。
+Please use V2, V1 is deprecated and will be removed in the future, It was not a very appropriate algorithm. Only for compatibility V1 is kept.: 请使用 V2。V1 已被弃用，将来会被移除，它并不是非常合适的算法。仅出于兼容性而保留 V1。
+Process files even if seems to be corrupted: 即使文件疑似损坏也进行处理
+Rotation Duration: 令牌轮换时长
+Signalling Relays: 信令中继
+Subject (whoami): 主体（whoami）
+TURN Servers: TURN 服务器
+The Application ID for P2P connection. This should be same among your devices. Default is 'self-hosted-livesync' and could not be modified from the UI.: 用于 P2P 连接的应用 ID。所有设备应保持相同。默认值为 'self-hosted-livesync'，无法在界面中修改。
+The Nostr relay servers to establish connections for P2P connections. Multiple servers can be separated by commas.: 用于建立 P2P 连接的 Nostr 中继服务器。多个服务器可以用逗号分隔。
+The Passphrase for P2P connection. This should be same among your devices.: 用于 P2P 连接的密码短语。你的所有设备上都应使用相同的密码短语。
+The Room ID for P2P connection. This should be same among your devices.: 用于 P2P 连接的房间 ID。所有设备应使用相同的房间 ID。
+The Rotation duration of token in minutes. Each generated tokens will be valid only within this duration.: 令牌的轮换时长（单位：分钟）。每个生成的令牌仅在此时长内有效。
+The TURN servers to use for P2P connections. Multiple servers can be separated by commas.: 用于 P2P 连接的 TURN 服务器。多个服务器可用逗号分隔。
+The algorithm used for JWT authentication.: 用于 JWT 认证的算法。
+The credential/password for the TURN servers.: TURN 服务器的凭据/密码。
+The key (PSK in HSxxx in base64, or private key in ESxxx in PEM) used for JWT authentication.: 用于 JWT 认证的密钥（base64 格式的 PSK，形如 HSxxx；或 PEM 格式的私钥，形如 ESxxx）。
+The key ID. this should be matched with CouchDB->jwt_keys->ALG:_`kid`.: 密钥 ID。它应与 CouchDB->jwt_keys->ALG:_`kid` 相匹配。
+The subject for JWT authentication. Mostly username.: JWT 认证的主体，通常为用户名。
+The username for the TURN servers.: TURN 服务器的用户名。
+Use JWT instead of Basic Authentication: 使用 JWT 而非 Basic 认证
+Use Only Local Chunks: 仅使用本地数据块
+Use Request API to avoid `inevitable` CORS problem: 使用 Request API 以避免 `inevitable` CORS 问题
+While enabled, it causes very performance impact but debugging replication testing and other features will be enabled. Please disable this if you have not read the source code. Requires restart of Obsidian. Sometimes there is no implementation.: 启用后会严重影响性能，但会开启复制调试测试等功能。如果你没有阅读过源代码，请关闭此项。需要重启 Obsidian。部分功能可能尚未实现。
+You can enable this setting to process the files with size mismatches, these files can be created by some APIs or integrations.: 启用此设置后可以处理大小不匹配的文件，这些文件可能由某些 API 或集成创建。
+xxhash64 is the current default.: xxhash64 是当前的默认值。
+Allow sleep during synchronisation: 同步期间允许睡眠
+Allow the operating system to sleep while finite synchronisation operations are in progress.: 在一次性同步操作进行期间，允许操作系统进入睡眠。
+Allow sleep during synchronisation on the desktop: 桌面端同步期间允许睡眠
+Desktop only. Allow sleep on this device even when the general option is disabled.: 仅限桌面端。即使通用选项已禁用，也允许此设备进入睡眠。
+Enable advanced mode: 启用高级模式
+Enable power user mode: 启用专家模式

From 7d98f0c084239f909774524c9b9fe6d8ac2e9d90 Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Tue, 27 Oct 2026 11:11:15 +0000
Subject: [PATCH 02/18] Document release notes and recovery assessment

---
 AGENTS.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index 6b93bc33..9e9529ec 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -39,6 +39,13 @@ Always adhere to the following stylistic and spelling rules:
 
 ---
 
+## Release Notes
+
+- Follow the release-note scope and history rules in [devs.md](devs.md#release-notes). Structure substantive entries as the user-visible outcome, the method that produces it, and supporting conditions, defaults, limitations, or required actions. Put the outcome first and use subordinate items when the explanation needs them.
+- When a pull request explains only its implementation, consult the relevant issue or design decision to establish the problem it resolves. Verify the claimed outcome against the change and its evidence. Distinguish removing a cause from reducing occurrence, detecting a problem, or improving recovery.
+
+---
+
 ## Technical & Architecture Rules
 
 1. **Database Structure**:
@@ -56,6 +63,15 @@ Always adhere to the following stylistic and spelling rules:
 
 ---
 
+## Failure Assessment and Recovery
+
+- Establish the intended behaviour from [the conflict policy](devs.md#conflict-merge-policy) and [the revision-provenance contract](docs/specs_conflict_resolution.md) before classifying a failure. A visible conflict which preserves both versions can be the correct outcome; manual selection alone does not establish a serious defect.
+- Assess preservation of user edits and required revision ancestry separately from extra work, temporary synchronisation delays, or duplicate internal records. A successful automatic merge or an empty queue is not proof of correct recovery. Check the resulting contents and history, safe convergence, and behaviour after restart where applicable.
+- Distinguish data still present on a device or in readable history from irretrievable loss. Verify that a recovery source contains the affected edits before treating the failure as fully recoverable. Follow [the recovery guidance](docs/recovery.md) before recommending a rebuild or reset which could discard unique work.
+- Give demonstrated irreversible information loss particular weight. Describe the actual burden of safe manual conflict resolution without treating automation as a correctness requirement. If preservation, recovery, impact, or the appropriate response remains unclear, review the evidence and alternatives with the collaborating user before changing the design or accepting the risk; continue independent investigation.
+
+---
+
 ## Development & Verification Commands
 
 Before submitting code, you should run verification scripts locally to ensure correct syntax and function.

From 2cfa4268cce1af9c3f2aaf51654ffe496fc80d73 Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Tue, 27 Oct 2026 13:14:38 +0000
Subject: [PATCH 03/18] Document published features and current technical
 behaviour

---
 docker/coturn/README.md                       |   2 +-
 .../2026_08_p2p_transport_compatibility.md    |  32 ++-
 ...local_file_save_completion_and_batching.md |  30 ++-
 docs/adr/2026_10_unicode_path_identity.md     |   7 +-
 .../design_docs/configurable_id_derivation.md |  10 +-
 .../document_history_revision_restoration.md  |  45 ++--
 .../internal_metadata_encryption.md           |  15 +-
 .../path_component_length_compatibility.md    |   8 +-
 .../design_docs/renewable_turn_credentials.md |   5 +-
 docs/design_docs/time_bound_setup_uri.md      | 200 +++++++++---------
 docs/design_docs/tweak_compatibility.md       |  11 +-
 docs/design_docs/unicode_path_identity.md     |   8 +-
 docs/design_docs_of_journalsync.md            |   4 +-
 docs/design_docs_of_remote_configurations.md  |  21 +-
 docs/design_docs_of_sharing_tweak_value.md    |   4 +-
 docs/review_harness.md                        |   5 +-
 docs/specs_data_compression.md                |   6 +-
 src/apps/cli/testdeno/test_dev_deno.md        |   6 +-
 src/apps/webpeer/README.md                    |   2 +
 19 files changed, 241 insertions(+), 180 deletions(-)

diff --git a/docker/coturn/README.md b/docker/coturn/README.md
index f62bb088..33642f03 100644
--- a/docker/coturn/README.md
+++ b/docker/coturn/README.md
@@ -51,7 +51,7 @@ Enter both client paths in the P2P profile's TURN server list:
 turn:turn.example.com:3478?transport=udp,turn:turn.example.com:3478?transport=tcp
 ```
 
-Use `TURN_USERNAME` and `TURN_PASSWORD` as the TURN username and credential. Keep the normal `Automatic` ICE policy unless a future LiveSync release offers `TURN relay only` and the direct path needs to be excluded deliberately.
+Use `TURN_USERNAME` and `TURN_PASSWORD` as the TURN username and credential. Keep the normal `Automatic` connection path unless the direct path needs to be excluded deliberately. Select `TURN relay only` under `Connection compatibility` to require the configured TURN route.
 
 Both synchronising devices must be able to reach the server. Prove an explicit two-way `Replicate now` round trip on the intended networks before relying on the configuration.
 
diff --git a/docs/adr/2026_08_p2p_transport_compatibility.md b/docs/adr/2026_08_p2p_transport_compatibility.md
index 48ef540b..1045e6f4 100644
--- a/docs/adr/2026_08_p2p_transport_compatibility.md
+++ b/docs/adr/2026_08_p2p_transport_compatibility.md
@@ -2,7 +2,10 @@
 
 ## Status
 
-Accepted — the user-facing controls will be introduced in stages. This record defines their boundaries before Commonlib settings and LiveSync interfaces are changed.
+Accepted. The P2P message-size presets and connection-path choice are present
+in current Self-hosted LiveSync 1.0.42 with Commonlib 0.2.2. The proposed
+`Test TURN server` action and concise route diagnostics in the Obsidian
+interface remain future work.
 
 ## Context
 
@@ -11,10 +14,12 @@ WebRTC connectivity depends on both devices, their browsers or embedded WebViews
 The current P2P transport has several relevant properties:
 
 - Trystero supplies the Nostr signalling strategy and the browser-owned WebRTC connection.
-- Commonlib limits one RPC wire payload to 15,360 bytes so it remains below Trystero's own action-chunk boundary.
-- Trystero supplies ordinary STUN servers and accepts an optional TURN server list with one username and credential.
-- ICE chooses a direct, server-reflexive, or TURN-relayed path automatically.
-- Commonlib can collect raw WebRTC statistics, but LiveSync does not yet present the selected candidate route in a concise diagnostic result.
+- Commonlib defaults to a 15,360-byte RPC wire payload limit, below Trystero's own action-chunk boundary; the presets below can lower it.
+- Manual TURN settings use one URL list, username, and credential. Managed preparation can supply multiple ICE server entries with their own credentials.
+- ICE chooses a direct, server-reflexive, or TURN-relayed path automatically unless the profile selects `TURN relay only`.
+- Commonlib can collect raw WebRTC statistics. The CLI reports the selected
+  candidate route, but the Obsidian interface does not yet present it in a
+  concise diagnostic result.
 
 Issue reports suggest that reducing the application payload may improve some mobile and constrained-network paths. A VPN such as Tailscale may also turn an unreliable route into a reliable one. These observations are consistent with NAT, path-MTU, fragmentation, or intermediary behaviour, but they do not prove one universal cause. Browser WebRTC implementations retain responsibility for SCTP, DTLS, ICE, packetisation, congestion control, and retransmission.
 
@@ -24,7 +29,7 @@ One low-level number cannot represent all of these concerns. Users need a small
 
 ### Message-size presets
 
-LiveSync will expose a `P2P message size` choice with four presets:
+LiveSync exposes a `P2P message size` choice with four presets:
 
 | Label                   | Maximum RPC wire payload | Intended use                                                                    |
 | ----------------------- | -----------------------: | ------------------------------------------------------------------------------- |
@@ -37,11 +42,11 @@ This value limits Commonlib RPC wire payloads before Trystero applies its own fr
 
 The bound applies to outgoing messages. A device which only lowers its own value still receives messages produced under the sender's value. The selected preset therefore belongs to the P2P profile and is included in an encrypted Setup URI for additional devices. A device which was configured earlier must be changed separately; the interface and troubleshooting guidance must state that the same conservative preset should be selected on every participating device. An absent key preserves the current 15,360-byte default.
 
-Automatic negotiation or fallback between presets is deferred. A failed ordered data channel may require connection replacement before a smaller retry can prove anything, and changing transport parameters during a replication session would broaden the lifecycle contract considerably. The first implementation remains explicit, stable for one room lifetime, and inspectable.
+Automatic negotiation or fallback between presets is deferred. A failed ordered data channel may require connection replacement before a smaller retry can prove anything, and changing transport parameters during a replication session would broaden the lifecycle contract considerably. The implementation remains explicit, stable for one room lifetime, and inspectable.
 
 ### Connection path
 
-LiveSync will expose a separate `Connection path` choice:
+LiveSync exposes a separate `Connection path` choice:
 
 - `Automatic` retains normal ICE selection and is the default.
 - `TURN relay only` supplies `iceTransportPolicy: 'relay'` and prevents direct or server-reflexive candidates from being selected.
@@ -81,11 +86,15 @@ Where the browser exposes the evidence, the result should report:
 - UDP, TCP, or TLS transport; and
 - a bounded failure or inconclusive result.
 
-Ordinary P2P diagnostics should later summarise the selected candidate pair as direct, server-reflexive, or relayed, with its transport. Raw `getStats()` output remains supporting evidence rather than the primary interface.
+The proposed Obsidian P2P diagnostics should summarise the selected candidate
+pair as direct, server-reflexive, or relayed, with its transport. The CLI's
+candidate-route output does not provide this user-facing summary. Raw
+`getStats()` output remains supporting evidence rather than the primary
+interface.
 
 ### Placement and defaults
 
-These controls belong inside `P2P Configuration` under a `Connection compatibility` section. They do not require the repository-wide Advanced, Power User, or Edge Case modes. P2P itself remains a supported opt-in feature.
+These controls appear inside `P2P Configuration` under a `Connection compatibility` section. They do not require the repository-wide Advanced, Power User, or Edge Case modes. P2P itself remains a supported opt-in feature.
 
 Existing profiles retain the following defaults:
 
@@ -161,7 +170,8 @@ A layer-4 TLS router could share one public address between distinct CouchDB and
 
 ## Verification
 
-The first implementation stage must add focused tests before production changes:
+The following list records the original focused-test plan for the message-size
+and connection-path controls. It remains useful as regression coverage:
 
 - settings-schema defaults for absent keys;
 - P2P connection-string and Setup URI round trips which retain both transport compatibility settings;
diff --git a/docs/adr/2026_10_local_file_save_completion_and_batching.md b/docs/adr/2026_10_local_file_save_completion_and_batching.md
index bbf67b13..f100d2a6 100644
--- a/docs/adr/2026_10_local_file_save_completion_and_batching.md
+++ b/docs/adr/2026_10_local_file_save_completion_and_batching.md
@@ -2,15 +2,17 @@
 date: 2026-10-24
 commonlib-version: "0.2.0"
 self-hosted-livesync-version: "1.0.40"
-status: accepted-unreleased
+status: accepted
 ---
 
 # Architectural Decision Record: Local File Save Completion and Batching
 
 ## Status
 
-Accepted on 2026-10-25. The package versions above identify the investigated
-baseline, rather than a released implementation of this decision.
+Accepted on 2026-10-25. The recovery contracts and LiveSync mode batching in
+implementation-order steps 1–3 are present in current Self-hosted LiveSync
+1.0.42 with Commonlib 0.2.2. The version fields above retain the investigated
+baseline. Further same-path coalescing in step 4 remains a follow-up.
 
 ## Context
 
@@ -349,6 +351,9 @@ eliminating genuine concurrent-edit conflicts or as a confirmed fix for #1207.
 
 ## Ownership and implementation order
 
+The list below records the implementation sequence. Steps 1–3 are published
+in the current version line; the further coalescing in step 4 remains planned.
+
 1. **Commonlib recovery:** event ownership, ordered snapshot persistence,
    successful completion and failure propagation, finite flush boundaries, and
    same-time content reconciliation. Add focused failing regressions before
@@ -373,6 +378,11 @@ automation transaction API require a further design decision.
 
 ## Verification required
 
+The matrix below records the acceptance criteria for implementation steps 1–3
+and remains useful for regression work. Publication in the current version line
+does not extend the historical test results above to untested platforms or
+automation workflows.
+
 Use controlled promises at the manager and persistence boundaries for focused
 regressions, and real PouchDB tests for content and ancestry. The acceptance
 matrix is:
@@ -395,13 +405,13 @@ matrix is:
 | Old settings, mode changes, explicit opt-in, and settings import                                                     | Existing LiveSync mode users retain immediate saving until they choose batching.                                                       |
 | Incoming identical content, an edit, a deletion, or delete/recreate while waiting                                    | Preserve genuine branches without extra conflicts or loss of local work.                                                               |
 
-Keep the existing E2E comparison between batching disabled, an ignored legacy
-setting, and explicitly enabled batching. Repeat both directions, manual
-synchronisation, saved-snapshot restart, and controlled in-progress restart with
-the fix. Record the original failure separately from repaired results; a pass
-with a different timestamp bucket or a test-only bundle is not verification of
-the production fix. Run platform-specific lifecycle checks before extending the
-evidence to Windows or mobile.
+The original E2E plan compared batching disabled, an ignored legacy setting, and
+explicitly enabled batching in both directions, with manual synchronisation,
+saved-snapshot restart, and controlled in-progress restart. Record the original
+failure separately from repaired results; a pass with a different timestamp
+bucket or a test-only bundle is not verification of the production fix. Keep
+platform-specific lifecycle evidence bounded to the tested environments before
+extending conclusions to Windows or mobile.
 
 ## Alternatives and consequences
 
diff --git a/docs/adr/2026_10_unicode_path_identity.md b/docs/adr/2026_10_unicode_path_identity.md
index 839ea986..2bc5a036 100644
--- a/docs/adr/2026_10_unicode_path_identity.md
+++ b/docs/adr/2026_10_unicode_path_identity.md
@@ -2,15 +2,16 @@
 date: 2026-10-17
 commonlib-version: "0.1.42"
 self-hosted-livesync-version: "1.0.37"
-status: unreleased
+status: released
 ---
 
 # Architectural Decision Record: Unicode Path Identity for CouchDB
 
 ## Status
 
-Accepted on 2026-10-17. The feature remains unreleased. Local validation
-evidence and platform limits are recorded in the design document.
+Accepted on 2026-10-17. Unicode NFC path identity was released in Self-hosted
+LiveSync 1.0.38 with Commonlib 0.1.42. Local validation evidence and platform
+limits are recorded in the design document.
 
 ## Context
 
diff --git a/docs/design_docs/configurable_id_derivation.md b/docs/design_docs/configurable_id_derivation.md
index 8a88ce5f..00bc1d80 100644
--- a/docs/design_docs/configurable_id_derivation.md
+++ b/docs/design_docs/configurable_id_derivation.md
@@ -2,7 +2,7 @@
 date: 2026-09-29
 commonlib-version: "0.1.33"
 self-hosted-livesync-version: "1.0.32"
-status: unreleased
+status: released
 ---
 
 # Configurable ID derivation
@@ -21,12 +21,12 @@ including its passphrase-persistence correction at commit
 the `next` tag, provides the construction described here. It replaces the
 independent Chunk algorithm from the `0.1.32` prerelease without a
 compatibility branch or a new settings version. Legacy ID generation remains
-unchanged. LiveSync pins the published `0.1.33` package and its registry
-integrity in the lockfile.
+unchanged. At that implementation baseline, LiveSync pinned the published
+`0.1.33` package and its registry integrity in the lockfile.
 Its [Internal Metadata encryption design](https://github.com/vrtmrz/obsidian-livesync/blob/126d6eadb858a79a08ad7f600061e54fc8d31196/docs/design_docs/internal_metadata_encryption.md)
 remains the basis for Properties encryption and CouchDB feature admission.
-This document records an unreleased LiveSync feature. It does not select a
-plug-in release version.
+Independent ID derivation shipped in Self-hosted LiveSync 1.0.33. This document
+retains the design and package baseline recorded above.
 
 ## Feasibility
 
diff --git a/docs/design_docs/document_history_revision_restoration.md b/docs/design_docs/document_history_revision_restoration.md
index c064daf6..714c4944 100644
--- a/docs/design_docs/document_history_revision_restoration.md
+++ b/docs/design_docs/document_history_revision_restoration.md
@@ -10,40 +10,45 @@ This document uses the independent revision properties defined under
 [Revision](../glossary.md#revision) and the general state model in
 [Conflict resolution and revision provenance](../specs_conflict_resolution.md).
 
-Document History can reconstruct an available historical revision from its
-Chunks and write that content to the Vault through **Back to this revision**.
-The current action writes directly through the storage adapter. It does not
-create a new Metadata revision, clear a logical deletion through a successor,
-or record which database revision produced the restored Vault file.
+Before the current restoration implementation, Document History could
+reconstruct an available historical revision from its Chunks and write that
+content to the Vault through **Back to this revision**. That action wrote
+directly through the storage adapter. It did not create a new Metadata revision,
+clear a logical deletion through a successor, or record which database revision
+produced the restored Vault file.
 
-This leaves a logically deleted Metadata document at `deleted: true` after the
-file has returned to the Vault. A later ordinary Vault save may create a
-non-deleted successor, but restoration must not depend on an unrelated later
-file event.
+That left a logically deleted Metadata document at `deleted: true` after the
+file had returned to the Vault. A later ordinary Vault save could create a
+non-deleted successor, but restoration needed to succeed without depending on
+an unrelated later file event.
 
-The same action does not inspect or preserve revision-tree intent explicitly
-when conflicts exist. Document History currently displays the ancestry of the
-PouchDB winner. It does not display the complete revision tree or the ancestry
-of every conflict leaf.
+Restoration does not resolve conflicts or provide a branch-aware history view.
+Document History displays the ancestry of the PouchDB winner; it does not
+display the complete revision tree or the ancestry of every conflict leaf.
 
 This design covers restoration of one readable historical revision of a normal
 Vault file. It creates a new non-deleted successor revision, reflects that exact
 revision to the Vault, and leaves every other conflict branch available for the
 existing conflict workflow.
 
+The current **Back to this revision** implementation writes that successor
+revision, reflects the exact created revision to the Vault, and records it as
+device-local provenance. The storage-only behaviour described above is the
+pre-fix history.
+
 ## Evidence
 
-A real-Obsidian exercise created a Markdown document, removed it through the
-Vault API, and waited for LiveSync to store a logical-deletion successor. The
-Metadata retained all referenced Chunks, and Document History could reconstruct
-the deleted content.
+A real-Obsidian exercise before the current restoration implementation created
+a Markdown document, removed it through the Vault API, and waited for LiveSync
+to store a logical-deletion successor. The Metadata retained all referenced
+Chunks, and Document History could reconstruct the deleted content.
 
 Selecting **Back to this revision** restored the file and its exact bytes to the
 Vault. The local database nevertheless retained the same deleted current
 revision after file processing had settled. An additional ordinary Vault save
-then created a new non-deleted successor. This demonstrates that content
-reconstruction works and that the missing operation is the database-aware
-restoration step.
+then created a new non-deleted successor. This historical reproduction showed
+that content reconstruction worked while the database-aware restoration step
+was missing.
 
 ## Revision-tree decision
 
diff --git a/docs/design_docs/internal_metadata_encryption.md b/docs/design_docs/internal_metadata_encryption.md
index e7d16ec6..0392dbdf 100644
--- a/docs/design_docs/internal_metadata_encryption.md
+++ b/docs/design_docs/internal_metadata_encryption.md
@@ -2,14 +2,15 @@
 date: 2026-09-27
 commonlib-version: "0.1.30"
 self-hosted-livesync-version: "1.0.32"
-status: unreleased
+status: released
 ---
 
 # Internal Metadata encryption and remote feature changes
 
 This document defines the LiveSync integration of Commonlib's remote feature
 contract and encrypted Metadata for Hidden File Sync and Customisation Sync.
-It describes unreleased behaviour being implemented in this branch.
+The implementation shipped in Self-hosted LiveSync 1.0.33; this document
+retains its original design and implementation context.
 
 Commonlib's companion `docs/remote-feature-compatibility.md` is the
 source of truth for the wire document, identifiers, validation, and shared
@@ -159,11 +160,11 @@ after alignment. With the preference subsequently OFF, verify that Fast Fetch
 still decodes encrypted Metadata and preserves the remote feature declaration.
 
 Keep the primary-language settings and troubleshooting guides, the
-database-compatibility ADR, and Unreleased notes aligned with this behaviour.
-Keep the detailed shared protocol in Commonlib and link to it after publication;
-do not maintain another copy of its wire schema here. Translations are a separate
-change. Update tested-version evidence when the implementation and its
-validation have been accepted.
+database-compatibility ADR, and release notes consistent with this behaviour.
+Commonlib's companion document remains the source of truth for the shared
+protocol; this document does not repeat its wire schema. Translations remain a
+separate change. The version fields above retain the original design baseline;
+add later tested-version evidence only when validation is recorded.
 
 Related application contracts: [Replicator architecture](replicator_architecture.md),
 [Tweak compatibility](tweak_compatibility.md), and
diff --git a/docs/design_docs/path_component_length_compatibility.md b/docs/design_docs/path_component_length_compatibility.md
index 367d7d42..ed97a9c5 100644
--- a/docs/design_docs/path_component_length_compatibility.md
+++ b/docs/design_docs/path_component_length_compatibility.md
@@ -2,7 +2,7 @@
 date: 2026-09-04
 commonlib-version: "0.1.21"
 self-hosted-livesync-version: "1.0.24"
-status: unreleased
+status: released
 ---
 
 # Path component length compatibility
@@ -11,9 +11,9 @@ status: unreleased
 
 File systems place limits on each file or folder name, rather than applying one
 common limit to an entire Vault-relative path. Those limits are also expressed
-in different units. Self-hosted LiveSync therefore treats 255 UTF-8 bytes as a
-focused Android and Linux compatibility warning, not as a universal definition
-of a valid path.
+in different units. The warning shipped in Self-hosted LiveSync 1.0.26. It
+treats 255 UTF-8 bytes as a focused Android and Linux compatibility warning,
+not as a universal definition of a valid path.
 
 ## Basis for the 255-byte warning
 
diff --git a/docs/design_docs/renewable_turn_credentials.md b/docs/design_docs/renewable_turn_credentials.md
index 0f903ba6..b5ae5788 100644
--- a/docs/design_docs/renewable_turn_credentials.md
+++ b/docs/design_docs/renewable_turn_credentials.md
@@ -2,7 +2,7 @@
 date: 2026-09-16
 commonlib-version: "0.1.25"
 self-hosted-livesync-version: "1.0.28"
-status: unreleased
+status: released
 ---
 
 # TURN credentials in P2P connection settings
@@ -14,6 +14,9 @@ by acquiring temporary TURN credentials on the device before opening a P2P room.
 The [P2P transport compatibility ADR](../adr/2026_08_p2p_transport_compatibility.md)
 records the connection and persistence policy.
 
+Managed Cloudflare TURN credentials shipped in Self-hosted LiveSync 1.0.29.
+This document records the design and its remaining runtime verification limits.
+
 LiveSync prepares a connection copy of `P2PSyncSetting`. Commonlib owns the room
 lifecycle and consumes the resulting ICE settings. Service-specific HTTP and
 validation remain under `src/integrations/`; Commonlib has no provider catalogue
diff --git a/docs/design_docs/time_bound_setup_uri.md b/docs/design_docs/time_bound_setup_uri.md
index bf5ceef6..2c2d3231 100644
--- a/docs/design_docs/time_bound_setup_uri.md
+++ b/docs/design_docs/time_bound_setup_uri.md
@@ -3,40 +3,42 @@ date: 2026-09-28
 commonlib-version: "0.1.33"
 feasibility-probe-version: "0.1.27"
 self-hosted-livesync-version: "1.0.32"
-status: implementing
+status: released
 ---
 
 # Time-bound Setup URIs
 
 ## Purpose and status
 
-Offer two modes when generating a [Setup URI](../glossary.md):
+The published Obsidian generator offers two choices when creating a [Setup URI](../glossary.md):
 
-- **Ephemeral**, selected by default, derives an effective passphrase from the
-  entered passphrase and the current fixed time window.
-- **Persistent** uses the entered passphrase and the existing URI format
-  unchanged. It also serves as the compatibility mode for older readers.
+- **Time-bound** (the `ephemeral` derivation mode), selected by default,
+  derives an effective passphrase from the entered passphrase and the current
+  fixed time window.
+- **Compatible (no time limit)** (the `persistent` derivation mode) uses the
+  entered passphrase and the existing URI format unchanged. It also serves as
+  the compatibility mode for older readers.
 
-The generation mode choice shows the exact time until which an Ephemeral URI
-can be opened through the ordinary reader. Import still requires only the URI and
-the entered passphrase. Neither the mode nor a timestamp is stored in the URI.
+The Time-bound choice shows the exact time until which the URI can be opened
+through the ordinary reader. Import still requires only the URI and the entered
+passphrase. Neither the mode nor a timestamp is stored in the URI.
 
-The design is technically feasible with the existing encryption primitives.
-An executable protocol probe passes 22 cases against Commonlib 0.1.27 and
-octagonal-wheels 0.1.54. The implementation was first published as Commonlib 0.1.32
-on the npm `next` tag. LiveSync now pins Commonlib 0.1.33 from that tag in its npm
-dependency and independent Deno tool imports. A mobile performance bound remains
-outstanding.
+Both URI availability choices shipped in Self-hosted LiveSync 1.0.33. The
+initial executable protocol probe passed 22 cases against Commonlib 0.1.27 and
+octagonal-wheels 0.1.54. The implementation was first published as Commonlib
+0.1.32 on the npm `next` tag. Current Self-hosted LiveSync 1.0.42 uses Commonlib
+0.2.2. A mobile performance bound remains outstanding.
 
-This document records the proposed key derivation and integration contract. The
-companion probe demonstrates them without changing an application entry point.
+This document records the protocol and the integration plan used for the
+published feature. The companion probe remains a standalone design check; it
+does not exercise an application entry point.
 
 ## Scope
 
-The first version offers Ephemeral and Persistent only. Ephemeral uses one
-fixed seven-day window shared by every implementation. Arbitrary start dates,
-custom end dates, selectable window lengths, and rolling seven-day lifetimes
-are outside this version.
+The published protocol offers the Ephemeral and Persistent modes only.
+Ephemeral uses one fixed seven-day window shared by every implementation.
+Arbitrary start dates, custom end dates, selectable window lengths, and rolling
+seven-day lifetimes are outside this version.
 
 Keep the current settings filtering, remote profiles, main and P2P selections,
 and short/full export variants. Time binding affects opening the exported
@@ -255,15 +257,16 @@ separately shared message.
 ## Ownership and compatibility
 
 Commonlib owns preparation of exported settings, the time-window calculation,
-passphrase derivation, format parsing, and dual-candidate decoding. Make these
-changes in the Commonlib repository. LiveSync must consume a validated packed
-artefact and then an exact reviewed package version, following
+passphrase derivation, format parsing, and dual-candidate decoding. These
+changes were made in the Commonlib repository. LiveSync consumes the reviewed
+Commonlib package, following
 [the Commonlib dependency workflow](../../devs.md#commonlib-dependency).
 
-Preserve the existing positional encoder API. Its third and fourth arguments
-already mean properties to remove and whether to omit default values. Add a
-separate encoder, provisionally `encodeTimeBoundSetupURI`, with an options
-object containing the mode and the existing export options. Its result is:
+The implementation preserves the existing positional encoder API. Its third
+and fourth arguments retain their meanings: properties to remove and whether
+to omit default values. It adds a separate `encodeTimeBoundSetupURI` encoder
+with an options object containing the mode and the existing export options.
+Its result is:
 
 ```typescript
 type TimeBoundSetupURIResult = {
@@ -272,27 +275,27 @@ type TimeBoundSetupURIResult = {
 };
 ```
 
-The new encoder defaults to Ephemeral. Preserve the old encoder's legacy
-behaviour for callers which have not migrated. Extend
-`decodeSettingsFromSetupURI` to try both candidates for `%$` while retaining its
+The new encoder defaults to Ephemeral. The old encoder retains its legacy
+behaviour for callers which have not migrated. The updated
+`decodeSettingsFromSetupURI` tries both candidates for `%$` while retaining its
 settings return contract and historical format handling. Persistent generation
-through the new API delegates to the old encoder. Time injection belongs in
+through the new API delegates to the old encoder. Time injection remains in
 internal test seams, not an import option exposed to users.
 
-| Surface                                                                              | Required work                                                                                                                                            |
+| Surface                                                                              | Published integration                                                                                                                                   |
 | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Obsidian generation](../../src/serviceFeatures/setupObsidian/setupUri.ts)           | Reuse the passphrase and copy dialogues, add a mode choice with the exact current window end, and use the new encoder for all three copy variants and the copy event. Preserve each variant's export filters.                 |
-| [Obsidian import](../../src/modules/features/SetupWizard/dialogs/UseSetupURI.svelte) | Consume the updated decoder and retain one authentication failure message. The existing prefix check indicates URI shape, not successful authentication. |
-| [Protocol handler](../../src/serviceFeatures/setupObsidian/setupProtocol.ts)         | Keep the existing `settings` reconstruction; test encoded delimiters for both modes.                                                                     |
-| [CLI setup](../../src/apps/cli/commands/runCommand.ts)                               | Consume the updated decoder and leave settings unchanged after any rejection.                                                                            |
-| [WebPeer generator](../../src/apps/webpeer/src/P2PCheckSetup.ts)                     | Choose a mode explicitly and return availability to its result UI; keep Ephemeral as the default.                                                        |
-| [Setup utility](../../utils/setup/generate_setup_uri.ts)                             | Add an explicit mode input, default to Ephemeral, and return/print the end time. Persistent is an explicit choice for durable provisioning output.       |
-| [Setup utility package facade](../../utils/setup/livesync-commonlib.ts)              | Update its independent Commonlib pin and associated lockfiles; updating the root npm dependency alone is insufficient.                                   |
+| [Obsidian generation](../../src/serviceFeatures/setupObsidian/setupUri.ts)           | Reuses the passphrase and copy dialogues, presents the mode choice and exact current window end, and uses the encoder for all copy variants and the copy event while preserving each variant's export filters. |
+| [Obsidian import](../../src/modules/features/SetupWizard/dialogs/UseSetupURI.svelte) | Consumes the updated decoder and retains one authentication failure message. The existing prefix check indicates URI shape, not successful authentication. |
+| [Protocol handler](../../src/serviceFeatures/setupObsidian/setupProtocol.ts)         | Retains the existing `settings` reconstruction; encoded delimiters remain part of protocol validation for both modes.                                 |
+| [CLI setup](../../src/apps/cli/commands/runCommand.ts)                               | Uses the updated decoder and leaves settings unchanged after a rejection.                                                                               |
+| [WebPeer generator](../../src/apps/webpeer/src/P2PCheckSetup.ts)                     | Explicitly selects Time-bound mode and returns availability to its result UI; this generator does not offer a Persistent choice.                                                    |
+| [Setup utility](../../utils/setup/generate_setup_uri.ts)                             | Accepts an explicit mode, defaults to Time-bound, and returns or prints the end time. Persistent is selected for durable provisioning output.          |
+| [Setup utility package facade](../../utils/setup/livesync-commonlib.ts)              | Retains its independent Commonlib pin and associated lockfiles, separate from the root npm dependency.                                                 |
 
-The Fly.io wrapper delegates to the setup utility and should inherit the same
-contract. All maintained generators must migrate explicitly before this
-feature is described as the default across applications. Non-interactive
-automation which needs a durable URI must select Persistent.
+The Fly.io wrapper delegates to the setup utility and inherits the same
+contract. The initial plan required each maintained generator to select a mode
+explicitly. Non-interactive automation which needs a durable URI selects
+Persistent.
 
 WebPeer hides an Ephemeral URI and disables its copy and additional-device
 actions after the window ends. Its connection monitor remains available for a
@@ -309,8 +312,9 @@ The assessed, unchanged Commonlib 0.1.27 decoder opens Persistent with the
 entered passphrase and rejects Ephemeral with that same passphrase. Persistent
 compatibility means compatibility with readers which already support the
 ordinary generated `%$` representation; it does not add that representation
-to still older readers. Historical supported versions and their settings
-schemas still need compatibility fixtures before rollout.
+to still older readers. This design does not establish compatibility with every
+historical reader or settings schema; compatibility fixtures are needed before
+making broader claims about them.
 
 Keep the original raw-passphrase behaviour of existing URIs. They are
 indistinguishable from newly generated Persistent URIs to the updated reader.
@@ -358,68 +362,72 @@ All 22 cases passed:
   and raw-passphrase candidates;
 - the deliberate limitation that clock rollback reproduces an old key.
 
-This demonstrates the proposed mechanism and baseline interoperability, not
-completed application support, formal mode indistinguishability, or a mobile
-latency bound. The present encryption API may perform two PBKDF2 derivations
-on a cold import. Do not infer production performance from this small probe,
-whose operations can reuse the dependency's in-memory key cache.
+The probe demonstrates feasibility and baseline interoperability. Application
+integration is recorded above; the probe does not establish formal mode
+indistinguishability or a mobile latency bound. The encryption API may perform
+two PBKDF2 derivations on a cold import. Do not infer production performance
+from this small probe, whose operations can reuse the dependency's in-memory
+key cache.
 
-Implementation validation must cover Commonlib unit and packed-package tests,
-plus shared fixed-input protocol vectors across consumers. Add targeted LiveSync
-tests for the generation metadata, cancellation, a window change during mode
-selection, encoded deep links, and rejected imports without settings writes. Extend CLI, WebPeer,
-and Deno setup-tool round trips, including their Persistent selection.
+The original implementation validation plan covered Commonlib unit and
+packed-package tests, plus shared fixed-input protocol vectors across consumers.
+It called for targeted LiveSync tests of generation metadata, cancellation, a
+window change during mode selection, encoded deep links, and rejected imports
+without settings writes, alongside CLI, WebPeer, and Deno setup-tool round trips
+for both modes.
 
-Then run the required LiveSync checks, unit suite, and production build, one
-broad process at a time with `NODE_OPTIONS=--max-old-space-size=3072` and bounded
-test workers. Use the existing focused real-Obsidian Setup URI workflow for
-copy/paste, deep-link import, cancellation, and successful setup. Verify
-selection-boundary handling with an injected test clock and mobile behaviour on a
-supported runtime; do not change the host's system clock. No remote database
-service is needed for the protocol tests themselves.
+The plan also called for the LiveSync checks, unit suite, and production build,
+one broad process at a time with `NODE_OPTIONS=--max-old-space-size=3072` and
+bounded test workers. It used the focused real-Obsidian Setup URI workflow for
+copy/paste, deep-link import, cancellation, and successful setup. Selection-
+boundary handling was to use an injected test clock; mobile behaviour requires
+a supported runtime and must not change the host's system clock. Protocol tests
+do not require a remote database service.
 
-There is no identified blocker in the Time-bound URI protocol. The Commonlib
-candidate based on 0.1.31 passed its type, unit, boundary, release-process,
-and packed-package gates before the 0.1.32 release. A clean `npm ci` against
-the published 0.1.32 artefact and the frozen Deno tool lock resolve the same
-registry integrity. LiveSync passes its source checks, production build, and
-1,034 unit tests on a local stack with [PR #1222](https://github.com/vrtmrz/obsidian-livesync/pull/1222).
-The two CLI installer tests need a runner which permits child processes; both
-pass under normal process permissions. The Deno setup-tool suite, CLI setup
+The original protocol assessment found no blocker in the Time-bound URI
+protocol. The Commonlib candidate based on 0.1.31 passed its type, unit,
+boundary, release-process, and packed-package gates before the 0.1.32 release. A
+clean `npm ci` against the published 0.1.32 artefact and the frozen Deno tool
+lock resolved the same registry integrity. In the original implementation
+baseline, LiveSync passed its source checks, production build, and 1,034 unit
+tests on a local stack with [PR #1222](https://github.com/vrtmrz/obsidian-livesync/pull/1222).
+The two CLI installer tests needed a runner which permits child processes; both
+passed under normal process permissions. The Deno setup-tool suite, CLI setup
 and file-operation contract, and WebPeer browser tests passed before stacking.
 
-Focused real-Obsidian generation checks pass on desktop and emulated mobile,
+The recorded real-Obsidian generation checks passed on desktop and emulated mobile,
 including the displayed Time-bound end, Compatible output, and mobile touch
-targets. A two-device CouchDB workflow now passes on the local stack: the
-provisioning tool creates a generation 12 database, the first device generates
+targets. A two-device CouchDB workflow passed on the local stack: the
+provisioning tool created a generation 12 database, the first device generated
 a Time-bound Setup URI after declaring its required generation 13 feature, and
-the second device imports it. An ordinary note completes a round trip, and a
-hidden snippet synchronises. The separate real-Obsidian tests for live remote
+the second device imported it. An ordinary note completed a round trip, and a
+hidden snippet synchronised. The separate real-Obsidian tests for live remote
 feature changes, internal Metadata migration, and a percent-prefixed E2EE
-passphrase also pass with published Commonlib 0.1.32. Unit and protocol tests
-cover window boundaries and preserve the existing distinction between an empty
-passphrase and cancellation. The WebPeer browser test confirms that its monitor
-remains available after the URI window ends for a device which has already
-imported the URI.
+passphrase also passed with published Commonlib 0.1.32. Unit and protocol tests
+covered window boundaries and preserved the existing distinction between an
+empty passphrase and cancellation. The WebPeer browser test confirmed that its
+monitor remained available after the URI window ended for a device which had
+already imported the URI.
 
-The current Commonlib 0.1.33 integration includes the merged host changes from
-PR #1222 and PR #1225. npm 10 and normal clean installations preserve the lockfile;
-source checks, the production build, 1,064 unit tests, and ten Deno setup-tool
-tests pass. Both URI modes preserve ID recovery and explicit legacy ID selection.
+The Commonlib 0.1.33 integration included the merged host changes from
+PR #1222 and PR #1225. At that baseline, npm 10 and normal clean installations
+preserved the lockfile; source checks, the production build, 1,064 unit tests,
+and ten Deno setup-tool tests passed. Both URI modes preserved ID recovery and
+explicit legacy ID selection.
 
-Real Obsidian tests cover independent ID keys through Time-bound, Compatible,
-and QR setup, encrypted local persistence, natural restarts of both devices,
-and bidirectional note transfers with stable document and Chunk IDs. Incorrect
-passphrases and past-window URIs leave runtime and persisted settings unchanged.
-The past clock belongs to an isolated fixture worker, not Obsidian or the host.
-CouchDB tests also cover a custom ID source and recovery code, rejection of
-incompatible document keys before remote writes, and the Doctor's decline,
-reminder, dismissal, and later acceptance paths. The detailed commands and the
-remaining published-artefact and physical-device checks are recorded in the
+Recorded real-Obsidian tests covered independent ID keys through Time-bound,
+Compatible, and QR setup, encrypted local persistence, natural restarts of both
+devices, and bidirectional note transfers with stable document and Chunk IDs.
+Incorrect passphrases and past-window URIs left runtime and persisted settings
+unchanged. The past clock belonged to an isolated fixture worker, not Obsidian
+or the host. CouchDB tests also covered a custom ID source and recovery code,
+rejection of incompatible document keys before remote writes, and the Doctor's
+decline, reminder, dismissal, and later acceptance paths. The detailed commands,
+remaining published-artefact checks, and physical-device checks are recorded in the
 [real Obsidian test guide](../../test/e2e-obsidian/README.md#combined-setup-and-security-regression-checks).
 
 Compatible preserves the URI encryption format; each receiving client must
 still support the shared settings and the remote's declared features. The host
 compatibility checks from PR #1222 remain necessary. These results do not
-establish a mobile performance bound. The first implementation changes only
-primary-language resources; translation changes require separate scope.
+establish a mobile performance bound. The initial implementation changed only
+primary-language resources; translation changes remain a separate scope.
diff --git a/docs/design_docs/tweak_compatibility.md b/docs/design_docs/tweak_compatibility.md
index be7dda44..d9b0e971 100644
--- a/docs/design_docs/tweak_compatibility.md
+++ b/docs/design_docs/tweak_compatibility.md
@@ -2,15 +2,16 @@
 date: 2026-10-17
 commonlib-version: "0.1.42"
 self-hosted-livesync-version: "1.0.37"
-status: unreleased
+status: released
 ---
 
 # Tweak compatibility and recovery
 
-This document describes the compatibility and recovery contract, including
-unreleased changes after Self-hosted LiveSync 1.0.37 using Commonlib 0.1.42.
-Commonlib owns the interpretation of synchronisation settings; LiveSync owns
-the dialogues and operations which consume that result.
+This document describes the compatibility and recovery contract introduced
+after the Self-hosted LiveSync 1.0.37 and Commonlib 0.1.42 baseline recorded
+above. The current assessment is included in Self-hosted LiveSync 1.0.42 with
+Commonlib 0.2.2. Commonlib owns the interpretation of synchronisation settings;
+LiveSync owns the dialogues and operations which consume that result.
 
 ## Shared assessment
 
diff --git a/docs/design_docs/unicode_path_identity.md b/docs/design_docs/unicode_path_identity.md
index 6827d9b0..c5808f92 100644
--- a/docs/design_docs/unicode_path_identity.md
+++ b/docs/design_docs/unicode_path_identity.md
@@ -2,7 +2,7 @@
 date: 2026-10-19
 commonlib-version: "0.1.43"
 self-hosted-livesync-version: "1.0.38"
-status: unreleased
+status: released
 ---
 
 # Unicode path identity
@@ -17,8 +17,10 @@ Commonlib's [consumer contract](https://github.com/vrtmrz/livesync-commonlib/blo
 defines the shared package boundary.
 
 NFC identity shipped in Self-hosted LiveSync `1.0.38` with Commonlib `0.1.42`.
-The deletion handling in reconstruction below uses Commonlib `0.1.43` and
-remains unreleased in Self-hosted LiveSync.
+Conflict-aware deletion handling during reconstruction was added separately
+and is included in current Commonlib `0.2.2`, used by Self-hosted LiveSync
+`1.0.42`. This later handling is distinct from the initial NFC identity
+release.
 
 ## Scope
 
diff --git a/docs/design_docs_of_journalsync.md b/docs/design_docs_of_journalsync.md
index e2f18b0c..398c3844 100644
--- a/docs/design_docs_of_journalsync.md
+++ b/docs/design_docs_of_journalsync.md
@@ -1,5 +1,7 @@
 ## The design document of the journal sync
 
+Historical design: this is the first Journal Sync design. Its original transfer sequence and discussion of possible storage backends are retained as history. For the maintained pipeline and storage-adapter design, read [Journal Replicator 2nd Edition](design_docs_of_journalsync_2nd.md) and the [Replicator architecture](design_docs/replicator_architecture.md). Use [Object Storage Setup](setup_object_storage.md) for supported client setup. A possible backend discussed here is not evidence that an adapter is available in the current release.
+
 Original title: Synchronise without CouchDB 
 
 ### Goal
@@ -47,4 +49,4 @@ This implementation replaces the synchronisation performed by CouchDB. Therefore
 
 ### Consideration and Conclusion
 
-This design offers a novel approach to journal synchronisation without relying on CouchDB. It leverages PouchDB's journaling capabilities and leverages simple server-side storage for efficient data exchange. Hence, the new design could be said to have gotten a broader outlook.
\ No newline at end of file
+This design offers a novel approach to journal synchronisation without relying on CouchDB. It leverages PouchDB's journaling capabilities and leverages simple server-side storage for efficient data exchange. Hence, the new design could be said to have gotten a broader outlook.
diff --git a/docs/design_docs_of_remote_configurations.md b/docs/design_docs_of_remote_configurations.md
index 1fdd2fb8..9ea42634 100644
--- a/docs/design_docs_of_remote_configurations.md
+++ b/docs/design_docs_of_remote_configurations.md
@@ -1,5 +1,9 @@
 # The design document of remote configuration management
 
+## Implementation status
+
+This document describes the profile catalogue and its runtime projections as used by Self-hosted LiveSync 1.0.42 with Commonlib 0.2.2. Commonlib owns profile migration, activation, and protected settings persistence. The [Replicator architecture](design_docs/replicator_architecture.md) and [P2P service lifecycle decision](adr/2026_08_replicator_capabilities_02_p2p_service_lifecycle.md) describe the separate P2P service boundary.
+
 ## Goal
 
 - Allow us to manage multiple remote connections in a single vault.
@@ -33,7 +37,9 @@ Once multiple remotes of the same type became desirable, the previous model no l
 The current settings now have two layers for remote configuration.
 
 1. A stored collection of named remotes.
-2. One active remote projected into the legacy flat settings fields.
+2. One active main remote projected into the legacy flat settings fields.
+
+The P2P service also has its own selected profile, recorded by `P2P_ActiveRemoteConfigurationId`. This permits the P2P service to use a selected P2P profile alongside a CouchDB or Object Storage main remote; it does not introduce a second main remote.
 
 This means the replication and database layers can continue to read the effective remote from the existing settings fields, while the settings dialogue and migration logic can manage many stored remotes.
 
@@ -54,6 +60,7 @@ type RemoteConfiguration = {
 type RemoteConfigurations = {
     remoteConfigurations: Record<string, RemoteConfiguration>;
     activeConfigurationId: string;
+    P2P_ActiveRemoteConfigurationId: string;
 };
 ```
 
@@ -116,7 +123,11 @@ Therefore:
 - Import trusts the supplied connection string as-is after parsing.
 - We should regard exported connection strings as sensitive information, much like Setup URI or a credentials-bearing configuration file.
 
-The `isEncrypted` field is currently reserved for future expansion. At present, the connection string itself is stored plainly inside the settings data, in the same sense that the effective runtime configuration can contain usable remote credentials.
+The `isEncrypted` field identifies an encrypted profile URI in persisted settings. When settings are saved with configuration encryption enabled, Commonlib encrypts the profile URIs and records `isEncrypted: true`. Loading protected settings decrypts the URIs into the runtime settings and clears that runtime flag before profile activation. The runtime settings and the persisted representation therefore have different purposes.
+
+Protection depends on the configured settings-passphrase policy and a usable key. A plaintext configuration is not made confidential by the presence of the field alone. Consult [Encrypting sensitive configuration items](settings.md#encrypting-sensitive-configuration-items) for that policy.
+
+Clipboard export serialises the usable connection string. Treat that exported value as sensitive even when its saved profile URI is encrypted at rest; storage protection does not encrypt the clipboard representation.
 
 ### Migration strategy
 
@@ -129,7 +140,7 @@ Rules:
 - If no remote list exists and the legacy fields contain a Peer-to-Peer configuration, create `legacy-p2p`.
 - If more than one legacy remote is populated, create all possible entries and select the active one according to `remoteType`.
 
-This migration is intentionally additive. It does not remove the flat fields because they remain necessary as the active runtime projection.
+This migration is intentionally additive. It does not remove the flat fields because they remain necessary as the active runtime projection. A migrated legacy P2P profile also initialises the separate P2P selection. Loading an existing profile catalogue does not unconditionally replace an intentionally empty P2P selection.
 
 ### Normalisation and application paths
 
@@ -190,7 +201,7 @@ The feature should be tested from four viewpoints.
 
 ## Outlook
 
-Import/export configuration strings should also be encrypted in the future, but this is a separate feature that can be added on top of the current design.
+A separately encrypted representation for clipboard import and export remains a possible extension. Encryption of profile URIs in persisted settings is already implemented as described above.
 
 ## Consideration and conclusion
 
@@ -203,4 +214,4 @@ Its core idea is modest but effective.
 - Project it into the legacy settings for runtime use.
 - Normalise every imported settings object through the same path.
 
-This keeps the implementation understandable and migration-friendly. It also opens the door for future work, such as encrypted per-remote storage, richer remote metadata, or remote-scoped options, without forcing another large redesign of how remotes are represented.
\ No newline at end of file
+This keeps the implementation understandable and migration-friendly. It also opens the door for future work, such as richer remote metadata or remote-scoped options, without forcing another large redesign of how remotes are represented.
diff --git a/docs/design_docs_of_sharing_tweak_value.md b/docs/design_docs_of_sharing_tweak_value.md
index 4016b7fb..3ab02008 100644
--- a/docs/design_docs_of_sharing_tweak_value.md
+++ b/docs/design_docs_of_sharing_tweak_value.md
@@ -1,6 +1,6 @@
 # Sharing `Tweak values`
 
-NOTE: This is the planned feature design document. This is planned, but not be implemented now (v0.23.3). This has not reached the design freeze and will be added to from time to time.
+Historical design: this document records the original proposal written for v0.23.3. Tweak sharing and compatibility assessment are implemented in published releases. Use [Tweak compatibility and recovery](design_docs/tweak_compatibility.md) for the maintained contract, and [Settings](settings.md) for the available controls. The proposal and test plan below are retained as design history; they do not define the current behaviour.
 
 ## Goal
 
@@ -52,4 +52,4 @@ B: On the setting dialogue.
     - However, this might be an essential feature. Further efforts are desired.
 
 ### Consideration and Conclusion
-To be described after implemented, tested, and, released.
\ No newline at end of file
+The published implementation has evolved beyond this proposal, including classification of compatible differences and automatic alignment where configured. Its current decisions, recovery requirements, and remaining limitations are recorded in [Tweak compatibility and recovery](design_docs/tweak_compatibility.md). The original proposal does not establish that every item in its test plan was implemented unchanged.
diff --git a/docs/review_harness.md b/docs/review_harness.md
index f94c670f..92738b57 100644
--- a/docs/review_harness.md
+++ b/docs/review_harness.md
@@ -19,10 +19,11 @@ The command and view are registered only when developer tools are enabled. Disab
 | --- | --- | --- | --- |
 | Settings lifecycle | Automatic | Read-only | Exposes the seven synchronisation choices as typed observations and, for a genuinely new Vault, compares the selected recommendations with Commonlib's new-Vault contract. Existing-Vault setting preservation remains an automated migration and `settings-ui` E2E responsibility. |
 | Compatibility review boundary | Guided | Device-local state | Observes the current dedicated compatibility controller and opens its actual review action. The Harness does not restore Change Log acknowledgement, `lastReadUpdates`, or a separate manual Pass or Fail result. |
-| P2P composition | Automatic | Read-only | Confirms that the live P2P result resolves one replicator bound to the active Obsidian services. Peer discovery, replacement, reconnection, and transfer remain unit, CLI, and Compose E2E responsibilities. |
+| ID generation performance | Automatic, individual | Read-only | Measures legacy and independent IDs using fixed in-memory inputs, including key derivation and heap samples where available. Keep Obsidian in the foreground. |
+| File content hash performance | Manual | Read-only | Compares SHA-256 and xxHash64 on fixed in-memory Blob inputs. Input creation is excluded from hash timings; engine initialisation and warm-up are reported separately. |
 | Vault fixture round trip | Automatic, explicit | Dedicated Vault fixtures | After explicit confirmation, creates, reads, modifies, renames, and removes one owned fixture tree. General Vault reflection remains covered by its separate real-Obsidian E2E workflow. |
 
-**Automatic** runs only the two read-only local observations. **Full review** also starts the guided compatibility observation and asks before the Vault fixture scenario writes anything. A scenario can also be run individually.
+**Automatic** runs only Settings lifecycle. **Full review** visits all listed scenarios, including the guided compatibility review and the two performance measurements, and asks before the Vault fixture scenario writes anything. Each scenario can also be run individually; a scenario's mode label does not by itself include it in the Automatic action.
 
 These observations deliberately do not repeat stronger automated workflows. They exist to record which contracts the current real-device composition exposes while a maintainer reviews an immutable artefact.
 
diff --git a/docs/specs_data_compression.md b/docs/specs_data_compression.md
index ac6e2845..119bc879 100644
--- a/docs/specs_data_compression.md
+++ b/docs/specs_data_compression.md
@@ -33,7 +33,11 @@ The current benchmark measures the Node CLI process. It does not establish Obsid
 
 ## Reproducible benchmark
 
-The benchmark is implemented under `src/apps/cli/testdeno` and packaged by `test/bench-network`. It uses the real CLI mirror and synchronisation path, Commonlib 0.1.0-rc.4, CouchDB 3.5.0, the V3 Rabin–Karp splitter, optional Data Compression, and E2EE V2. It runs each of these conditions three times in rotating order:
+The benchmark is implemented under `src/apps/cli/testdeno` and packaged by `test/bench-network`. It exercises the real CLI mirror and synchronisation path. The recorded three-repeat result below used Commonlib 0.1.0-rc.4, CouchDB 3.5.0, the V3 Rabin–Karp splitter, optional Data Compression, and E2EE V2.
+
+The current Compose runner installs the checked-out repository's package and lockfile with `npm ci`; Self-hosted LiveSync 1.0.42 selects Commonlib 0.2.2. Running the command below measures that checkout, rather than recreating the older package environment automatically. Keep the recorded results associated with their original measurement date and dependency version.
+
+With the repeat count shown below, it runs each of these conditions three times in rotating order:
 
 - E2EE off, compression off;
 - E2EE off, compression on;
diff --git a/src/apps/cli/testdeno/test_dev_deno.md b/src/apps/cli/testdeno/test_dev_deno.md
index 110f2e94..bdd67142 100644
--- a/src/apps/cli/testdeno/test_dev_deno.md
+++ b/src/apps/cli/testdeno/test_dev_deno.md
@@ -146,7 +146,7 @@ These flows do not require Bash on the host. The S3 matrix tasks, environment va
 
 ### `test-mirror.ts`
 
-- Verifies six core mirror scenarios.
+- Verifies seven core mirror scenarios, including an unrecognised revision origin.
 - Does not require an external remote.
 
 ### `test-sync-two-local-databases.ts`
@@ -247,11 +247,12 @@ deno task test:daemon
 deno task test:push-pull
 deno task test:sync-locked-remote
 
-# CouchDB-based tests
+# CouchDB and Object Storage tests
 deno task test:sync-two-local
 deno task test:decoupled-vault
 deno task test:remote-commands
 deno task test:e2e-couchdb
+deno task test:e2e-matrix
 
 # Explicit host-direct P2P diagnostics for cross-platform investigations.
 # These are not part of the default suite or release evidence.
@@ -260,7 +261,6 @@ deno task test:p2p-peers
 deno task test:p2p-sync
 deno task test:p2p-three-nodes
 deno task test:p2p-upload-download
-deno task test:e2e-matrix
 ```
 
 ---
diff --git a/src/apps/webpeer/README.md b/src/apps/webpeer/README.md
index 8441896a..08122557 100644
--- a/src/apps/webpeer/README.md
+++ b/src/apps/webpeer/README.md
@@ -49,6 +49,8 @@ After the first device connects, **Try another device without resetting** keeps
 
 Serve the production build over HTTPS or from `localhost`. Downloading `check.html` alone is not supported because the page uses built module assets and origin-scoped browser storage. The generated credentials are temporary and must not replace the settings of a production Vault.
 
+The generated Setup URI is Time-bound, and the page shows when its current fixed UTC window ends. After that time, the page hides the URI and QR code and disables the additional-device action. Start a fresh check to configure another device. A monitor for a device which already imported the settings remains available.
+
 The detailed scope and result semantics are recorded in the [browser-assisted P2P connection-check ADR](../../../docs/adr/2026_07_p2p_connection_check.md).
 
 ## Storage and lifecycle

From e17979e45700e1087ddc43aca4f4cbcc42c71a85 Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Tue, 27 Oct 2026 13:14:38 +0000
Subject: [PATCH 04/18] Correct setup and server operation guidance

---
 docker/.env.example           |   8 +-
 docker/README.md              | 141 +++++++++++++---------------------
 docker/config/cloudflared.yml |  15 ++--
 docker/config/livesync.ini    |   9 +--
 docker/docker-compose.yml     |   8 +-
 docs/setup_flyio.md           |  36 +++++----
 docs/setup_object_storage.md  |  10 +--
 docs/setup_own_server.md      |  28 +++----
 docs/setup_p2p.md             |  10 +--
 docs/tips/fast-setup.md       |  22 +++---
 utils/readme.md               |  10 +--
 11 files changed, 133 insertions(+), 164 deletions(-)

diff --git a/docker/.env.example b/docker/.env.example
index 816b1460..fd1fdc45 100644
--- a/docker/.env.example
+++ b/docker/.env.example
@@ -34,9 +34,9 @@ ACME_EMAIL=you@yourdomain.com
 # PROFILE: tailscale  (--profile tailscale)
 # =============================================================================
 
-# Tailscale OAuth key (not a regular auth key — must be OAuth for persistent use)
-# Generate at: https://login.tailscale.com/admin/settings/oauth
-# Scopes needed: devices:write
+# Tailscale authentication key for this container.
+# OAuth clients require their own scopes and tag configuration; see:
+# https://tailscale.com/docs/features/containers/docker/docker-params#ts_authkey
 TS_AUTHKEY=tskey-auth-xxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
 # Hostname this node will have on your tailnet (becomes <hostname>.<tailnet>.ts.net)
@@ -47,6 +47,6 @@ TS_HOSTNAME=livesync
 # =============================================================================
 
 # Tunnel token from Cloudflare Zero Trust dashboard
-# Create at: https://one.dash.cloudflare.com/ → Networks → Tunnels → Create tunnel
+# Current setup guide: https://developers.cloudflare.com/tunnel/get-started/
 # Copy the token from the "Install connector" step
 CF_TUNNEL_TOKEN=eyJhIjoixxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
diff --git a/docker/README.md b/docker/README.md
index eaa1bcdd..0eb33e55 100644
--- a/docker/README.md
+++ b/docker/README.md
@@ -61,11 +61,11 @@ docker compose --profile cloudflare up -d
 
 ```bash
 # Should return {"status":"ok"}
-curl -u admin:yourpassword http://localhost:5984/_up
+curl -u '<COUCHDB_USER>:<COUCHDB_PASSWORD>' http://localhost:5984/_up
 
 # Check CORS headers
 curl -v -H "Origin: app://obsidian.md" \
-     -u admin:yourpassword \
+     -u '<COUCHDB_USER>:<COUCHDB_PASSWORD>' \
      http://localhost:5984/
 ```
 
@@ -75,7 +75,7 @@ In the Obsidian plugin settings (**Self-hosted LiveSync**):
 
 | Field | Value |
 |---|---|
-| URI | `https://your-domain-or-ts-hostname:5984` (or `http://localhost:5984` for LAN-only) |
+| URI | `https://your-domain-or-ts-hostname` for an HTTPS profile, or `http://localhost:5984` for local HTTP |
 | Username | value of `COUCHDB_USER` |
 | Password | value of `COUCHDB_PASSWORD` |
 | Database name | value of `COUCHDB_DATABASE` (default: `obsidiannotes`) |
@@ -85,10 +85,13 @@ In the Obsidian plugin settings (**Self-hosted LiveSync**):
 
 ## Profile Details
 
-### Default (no profile) — LAN / Localhost only
+<a id="default-no-profile--lan--localhost-only"></a>
 
-CouchDB is exposed on `http://localhost:5984` (or LAN IP).  
-**Desktop Obsidian works over HTTP.** Mobile Obsidian requires HTTPS — use a tunnel profile.
+### Default (no profile) — Host HTTP access
+
+The Compose file publishes CouchDB on host port 5984 by default, on all host interfaces. Its reachability depends on the host firewall and network; selecting an HTTPS profile does not close that direct HTTP port. Restrict the host port to the intended network, bind it to loopback, or remove the mapping when all access uses the proxy.
+
+Desktop Obsidian can use HTTP. Use HTTPS for mobile clients and connections outside a trusted local network. The supplied HTTPS profiles use port 443, so their client URL normally has no `:5984` suffix.
 
 ### `--profile caddy` — Public Domain + Auto TLS
 
@@ -104,13 +107,14 @@ ACME_EMAIL=you@example.com
 
 Caddy automatically issues a Let's Encrypt certificate. No manual cert management.
 
-### `--profile tailscale` — No Domain Required ✅ Recommended for privacy
+<a id="--profile-tailscale--no-domain-required--recommended-for-privacy"></a>
+
+### `--profile tailscale` — Tailnet or public HTTPS
 
 **Requires**:
-- Free [Tailscale account](https://login.tailscale.com/)
-- Install the Tailscale app on all your Obsidian devices
-- Generate an **OAuth key** at: https://login.tailscale.com/admin/settings/oauth  
-  (Scopes: `devices:write`)
+- A [Tailscale account](https://login.tailscale.com/).
+- The Tailscale app on devices using private tailnet access.
+- An authentication key for `TS_AUTHKEY`. Follow the [Docker authentication parameters](https://tailscale.com/docs/features/containers/docker/docker-params#ts_authkey) if using an OAuth client instead.
 
 **Set in `.env`**:
 ```
@@ -118,34 +122,22 @@ TS_AUTHKEY=tskey-auth-...
 TS_HOSTNAME=livesync
 ```
 
-**Two sub-modes**:
-- **VPN mode** (default): CouchDB accessible only to devices on your Tailnet at  
-  `https://livesync.<tailnet>.ts.net` — completely private
-- **Funnel mode**: public HTTPS at `https://livesync.<tailnet>.ts.net` — no domain purchase  
-  Enable in your [Tailscale ACL](https://login.tailscale.com/admin/acls):
-  ```json
-  "nodeAttrs": [{"target": ["tag:container"], "attr": ["funnel"]}]
-  ```
+Choose the exposure before starting the profile. The bundled `config/ts-serve.json` sets `AllowFunnel` to `true`, requesting public HTTPS when the tailnet permits Funnel. It is not a private-only default.
 
-> **Note on Windows Docker Desktop**: If `/dev/net/tun` is unavailable, add `TS_USERSPACE=true`  
-> to the tailscale service environment in `docker-compose.yml`.
+- For private tailnet access, set that entry to `false` and verify the effective Serve configuration.
+- For public Funnel access, retain `true` and configure the required tailnet permissions. See the [Tailscale Docker guide](https://tailscale.com/blog/docker-tailscale-guide) for the distinction between Serve and Funnel.
+
+The bundled service expects `/dev/net/tun`. On hosts without that device, follow Tailscale's userspace-networking instructions and adjust the device mount as well as `TS_USERSPACE`; changing the environment variable alone leaves the required bind mount in place.
 
 ### `--profile cloudflare` — Cloudflare Tunnel
 
 **Requires**:
-- Free [Cloudflare account](https://www.cloudflare.com/)
-- A domain managed by Cloudflare DNS (can transfer existing domain for free)
-- Cloudflare Zero Trust account (free)
+- A [Cloudflare account](https://www.cloudflare.com/).
+- A domain whose DNS is managed by Cloudflare.
 
 #### Step 1: Create a Cloudflare Tunnel
 
-1. Log in to [Cloudflare Zero Trust](https://one.dash.cloudflare.com/)
-2. Navigate to **Networks → Tunnels**
-3. Click **Create a tunnel**
-4. Choose **Cloudflared** as tunnel type
-5. Name your tunnel (e.g., `obsidian-livesync`)
-6. Click **Save tunnel**
-7. **Copy the tunnel token** — it looks like `eyJhIjoiZX...` (very long, ~400 characters)
+Create a remotely managed tunnel using the current [Cloudflare Tunnel setup instructions](https://developers.cloudflare.com/tunnel/get-started/). Copy its connector token into `CF_TUNNEL_TOKEN` below. This Compose profile runs the connector; a separate host installation of `cloudflared` is unnecessary for this profile.
 
 #### Step 2: Configure Environment
 
@@ -157,27 +149,14 @@ COUCHDB_DOMAIN=sync.yourdomain.com   # Must be a domain managed by Cloudflare
 
 #### Step 3: Add Public Hostname Route
 
-🚨 **CRITICAL**: Token-based tunnels ignore the local `cloudflared.yml` config file. All routing is controlled from the dashboard.
+Configure the route in the Cloudflare dashboard for this remotely managed tunnel. The local `config/cloudflared.yml` is not the routing source for the token-managed profile.
 
-Back in the Zero Trust dashboard, **in the same tunnel creation flow** (or edit your tunnel later):
+1. Open the tunnel under **Networking → Tunnels**.
+2. Under **Routes**, add a **Published application**.
+3. Choose the public hostname, for example `sync.yourdomain.com`.
+4. Set the service URL to `http://couchdb:5984` and save the route.
 
-1. Go to the **Public Hostname** tab
-2. Click **Add a public hostname**
-3. Configure:
-   - **Subdomain**: `sync` (or your preferred subdomain)
-   - **Domain**: Select your Cloudflare domain from dropdown
-   - **Type**: `HTTP`
-   - **URL**: `couchdb:5984` ← **Do NOT use `localhost`!**
-
-**Why `couchdb:5984` not `localhost:5984`?**
-- The `cloudflared` container runs inside Docker on the same network as `couchdb`
-- Docker's internal DNS resolves `couchdb` to the correct container
-- Using `localhost` would look inside the `cloudflared` container (nothing there)
-
-4. Under **Additional application settings** (expand):
-   - **No TLS Verify**: Leave **OFF** (CouchDB uses plain HTTP internally, that's fine)
-   - Leave other settings at defaults
-5. Click **Save hostname**
+The `cloudflared` and `couchdb` services share a Docker network. The service name reaches CouchDB; `localhost` would address the `cloudflared` container itself. The local connection is HTTP, while the public client URL is HTTPS. Keep TLS certificate verification enabled for any HTTPS origin you configure later. The [current setup guide](https://developers.cloudflare.com/tunnel/get-started/) describes the dashboard flow.
 
 #### Step 4: Start the Stack
 
@@ -203,7 +182,7 @@ You should see:
 curl -I https://sync.yourdomain.com
 
 # Should return {"couchdb":"Welcome",...}
-curl -u admin:yourpassword https://sync.yourdomain.com
+curl -u '<COUCHDB_USER>:<COUCHDB_PASSWORD>' https://sync.yourdomain.com
 ```
 
 If you get **404**, see Troubleshooting below.
@@ -220,9 +199,7 @@ In Obsidian → Settings → **Self-hosted LiveSync**:
 | Database name | value of `COUCHDB_DATABASE` from `.env` (default: `obsidiannotes`) |
 | End-to-end passphrase | *Choose your own* — never stored server-side |
 
-Under **Remote Database Configuration → Advanced**:
-- Enable: ✅ **Use Request API to avoid inevitable CORS problem**
-  (See "Known Issue" below for why this is critical)
+If browser requests encounter a CORS failure, consult [Use Request API](../docs/settings.md#use-request-api-to-avoid-inevitable-cors-problem). That setting selects Obsidian's HTTP request adapter. It does not select the synchronisation mode or remove Cloudflare's proxy limits.
 
 ---
 
@@ -241,13 +218,11 @@ docker logs livesync-cloudflared --tail 20
 
 **Fix**: The public hostname rule is missing or incorrect.
 
-1. Go to Zero Trust → Networks → Tunnels → your tunnel → **Edit**
-2. Click **Public Hostname** tab
-3. Verify a hostname exists with:
-   - Service Type: `HTTP`
-   - URL: `couchdb:5984` (NOT `localhost:5984`)
-4. If no hostname exists, add it (see Step 3 above)
-5. Wait 30 seconds for changes to propagate, then test again
+1. Open the tunnel's published application routes in the Cloudflare dashboard.
+2. Verify that the requested hostname maps to `http://couchdb:5984`.
+3. Add or correct the route if required, then retry after the configuration has propagated.
+
+A connected tunnel alone does not establish that the hostname route or origin is correct.
 
 **Problem: Connection immediately closes / 502 Bad Gateway**
 
@@ -258,10 +233,10 @@ docker ps --filter "name=livesync-couchdb"
 # Status should be: Up (healthy)
 
 docker inspect livesync-couchdb -f '{{.NetworkSettings.Networks}}'
-# Should show: livesync-net
+# Both services should list the same Compose network.
 
 docker inspect livesync-cloudflared -f '{{.NetworkSettings.Networks}}'
-# Should also show: livesync-net
+# Compare with the CouchDB network above.
 ```
 
 **Fix**: If CouchDB is unhealthy, check logs:
@@ -271,41 +246,35 @@ docker logs livesync-couchdb --tail 50
 
 **Problem: 524 Timeout Errors During Sync**
 
-**Root cause**: Cloudflare's proxy has a **100-second idle timeout**. CouchDB's replication protocol uses long-polling on the `_changes` feed, which can idle for longer during quiet periods.
+A `524` can indicate that the origin did not respond or accept request data within Cloudflare's proxy timeout. Inspect the failing request, CouchDB response times, and connector logs before selecting a remedy. See [Cloudflare's current 524 guidance](https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/) for the applicable limits and diagnostic steps.
 
-**Fix**: Switch to short-polling mode in the Obsidian plugin:
-1. Obsidian → Settings → Self-hosted LiveSync
-2. **Remote Database Configuration → Advanced**
-3. Enable: ✅ **Use Request API to avoid inevitable CORS problem**
-4. Save and restart sync
-
-This keeps all requests under 100 seconds.
-
-**Alternative**: Use Tailscale or Caddy profiles instead — neither has aggressive timeouts.
+**Use Request API** changes the HTTP adapter; it does not turn LiveSync mode into short polling or guarantee that a request completes within a proxy timeout. Review the actual synchronisation mode and [heartbeat/timeout setting](../docs/settings.md#use-timeouts-instead-of-heartbeats), then verify transfers on the intended devices. If the required traffic does not fit the proxy limits, consider an appropriately secured direct HTTPS route through Caddy or private Tailscale access.
 
 ---
 
 ## Data & Backup
 
-All vault data lives in the `couchdb-data` Docker named volume.
+The server database files live in the `couchdb-data` Docker named volume. Keep Vault backups, encryption passphrases, and ID recovery information separately. Back up the Compose configuration and CouchDB configuration as well; the database volume alone does not contain all of them.
+
+The following example creates an archive while CouchDB is stopped. Verify the volume name before running it, especially if you have overridden the Compose project name:
 
 ```bash
-# Backup
-docker run --rm -v obsidian-livesync_couchdb-data:/data \
-  -v $(pwd)/backup:/backup alpine \
-  tar czf /backup/couchdb-backup-$(date +%Y%m%d).tar.gz -C /data .
-
-# Restore
-docker run --rm -v obsidian-livesync_couchdb-data:/data \
-  -v $(pwd)/backup:/backup alpine \
-  tar xzf /backup/couchdb-backup-20260218.tar.gz -C /data
+docker volume inspect obsidian-livesync_couchdb-data
+mkdir -p backup
+docker compose stop couchdb
+docker run --rm --network none -v obsidian-livesync_couchdb-data:/data:ro \
+  -v "$(pwd)/backup:/backup" alpine \
+  tar czf "/backup/couchdb-backup-$(date +%Y%m%d-%H%M%S).tar.gz" -C /data .
+docker compose start couchdb
 ```
 
+Before restoration, preserve the existing database volume. Restore and verify the archive in a separate recovery volume with a compatible CouchDB installation before replacing the active data. Do not extract an archive over a running database. See [Backing up CouchDB](https://docs.couchdb.org/en/stable/maintenance/backups.html) for database, configuration, and replication-based backup options.
+
 ---
 
 ## Security Notes
 
-- CouchDB requires authentication for **all** requests (configured by `livesync.ini`)
+- The init service enables authenticated CouchDB access through the REST API. Verify that protected database endpoints reject unauthenticated requests before exposing the service.
 - Enable **End-to-End Encryption** passphrase in the Obsidian plugin — vault data is  
   encrypted before it ever leaves your device
 - The init container runs once and exits — it has no persistent access
@@ -344,8 +313,8 @@ open http://localhost:5984/_utils
 | Init container keeps restarting | CouchDB not healthy yet — wait 30s, check `docker compose logs couchdb` |
 | `curl: (52) Empty reply` | CouchDB not fully started — the healthcheck should gate this |
 | Mobile can't connect | Needs HTTPS — use tailscale or caddy profile |
-| 524 errors with Cloudflare | Enable "Use Request API" toggle in Obsidian plugin |
-| `Permission denied` on volumes | Run `docker compose down -v` and retry — first-run volume ownership issue |
+| 524 errors with Cloudflare | Inspect the failing request and origin response time; follow the timeout guidance above. |
+| `Permission denied` on volumes | Preserve the volume, inspect the CouchDB logs and mount ownership, and correct the specific permission problem. `docker compose down -v` deletes the database volume and is not a repair step. |
 | CORS errors in browser | Confirm CouchDB headers: `curl -v -H "Origin: app://obsidian.md" http://localhost:5984/` |
 | CouchDB exits immediately, zero logs (Windows) | **Do not add `:ro`** to the `livesync.ini` volume mount. CouchDB's entrypoint runs `chmod 0644` on all files in `/opt/couchdb/etc` — read-only bind mounts cause a silent EPERM crash on Docker Desktop for Windows (WSL2). The compose file is already correct; do not modify it. |
 | Settings in `livesync.ini` seem ignored | Settings requiring restart (e.g. bind_address) load at start. Runtime-only settings (require_valid_user, enable_cors) are set by the init container via REST API and take effect immediately without restart. |
diff --git a/docker/config/cloudflared.yml b/docker/config/cloudflared.yml
index 3e18bcfb..0ea3a205 100644
--- a/docker/config/cloudflared.yml
+++ b/docker/config/cloudflared.yml
@@ -2,17 +2,16 @@
 # =============================================================================
 #
 # Prerequisites:
-#   1. Create a tunnel in Cloudflare Zero Trust → Networks → Tunnels
+#   1. Create a remotely managed tunnel using the current Cloudflare dashboard guide.
 #   2. Copy the tunnel token to CF_TUNNEL_TOKEN in your .env
-#   3. Add a public hostname in the tunnel config:
+#   3. Add a published application route in the dashboard:
 #       Hostname : couchdb.yourdomain.com   (or whatever you set COUCHDB_DOMAIN to)
 #       Service  : http://couchdb:5984
 #
-# Known issue: Cloudflare's 100-second proxy timeout can interrupt CouchDB's
-# long-polling replication change feed, causing 524 errors.
-# MITIGATION: In the Obsidian plugin settings, enable:
-#   "Use Request API to avoid inevitable CORS problem"
-# This switches from long-poll to short-poll mode.
+# The token-managed Compose profile uses dashboard routing. The local ingress
+# example below describes locally managed routing and is not that profile's
+# source of routes. Diagnose 524 errors using current Cloudflare guidance.
+# The Obsidian Request API setting changes the HTTP adapter, not the sync mode.
 #
 # =============================================================================
 
@@ -23,7 +22,7 @@ ingress:
   - hostname: ${COUCHDB_DOMAIN}
     service: http://couchdb:5984
     originRequest:
-      # Increase timeouts for CouchDB replication streams
+      # Origin connection settings for this locally managed example
       connectTimeout: 30s
       keepAliveTimeout: 90s
       keepAliveConnections: 100
diff --git a/docker/config/livesync.ini b/docker/config/livesync.ini
index fd1ffb00..062d8e98 100644
--- a/docker/config/livesync.ini
+++ b/docker/config/livesync.ini
@@ -1,10 +1,9 @@
 ; CouchDB local configuration for Self-hosted LiveSync
-; This file is volume-mounted into /opt/couchdb/etc/local.d/livesync.ini
+; This file is volume-mounted into /opt/couchdb/etc/local.ini
 ;
-; IMPORTANT: Do NOT set require_valid_user here.
-; CouchDB needs to start without auth to complete its first-run cluster setup
-; (_users, _replicator databases must be created first).
-; The couchdb-init service applies auth lockdown via REST API after first-run.
+; The couchdb-init service configures require_valid_user and CORS through the
+; REST API during provisioning. Verify that the init service completes before
+; exposing the database to clients.
 
 [couchdb]
 ; Max size per document (50MB). Large enough for binary attachments.
diff --git a/docker/docker-compose.yml b/docker/docker-compose.yml
index 5f7350b0..b074af09 100644
--- a/docker/docker-compose.yml
+++ b/docker/docker-compose.yml
@@ -2,7 +2,7 @@
 # =============================================================================
 #  PROFILES
 #  --------
-#  (default)              CouchDB only — LAN/localhost access, no TLS
+#  (default)              CouchDB only — host HTTP port, no TLS
 #                         Suitable for desktop-only use or testing.
 #
 #  --profile caddy        CouchDB + Caddy reverse proxy
@@ -14,7 +14,7 @@
 #
 #  --profile cloudflare   CouchDB + cloudflared tunnel daemon
 #                         Free public HTTPS via Cloudflare. Needs a CF account + tunnel token.
-#                         NOTE: Enable "Use Request API" in the Obsidian plugin to avoid 524 timeouts.
+#                         Review proxy timeouts separately from the Obsidian HTTP adapter setting.
 #
 #  QUICK START (local test):
 #    cp .env.example .env && edit .env
@@ -147,8 +147,8 @@ services:
   # PROFILE: cloudflare — cloudflared tunnel daemon
   # Requirements: Cloudflare account, tunnel token from CF Zero Trust dashboard
   # Usage: docker compose --profile cloudflare up -d
-  # NOTE: Enable "Use Request API" toggle in the Obsidian LiveSync plugin settings
-  #       to avoid Cloudflare's 100-second proxy timeout (524 errors).
+  # NOTE: The Request API setting changes the HTTP adapter, not the sync mode.
+  #       Diagnose proxy timeouts using the Docker README and current provider limits.
   # ---------------------------------------------------------------------------
   cloudflared:
     image: cloudflare/cloudflared:latest
diff --git a/docs/setup_flyio.md b/docs/setup_flyio.md
index 56f38caa..0b926b3f 100644
--- a/docs/setup_flyio.md
+++ b/docs/setup_flyio.md
@@ -12,7 +12,7 @@ This is how to configure fly.io and CouchDB on it for Self-hosted LiveSync.
 > **What and why is the Fly.io?**  
 > At some point, we started to experience problems related to our IBM Cloudant account. At the same time, Self-hosted LiveSync started to improve its functionality, requiring CouchDB in a more natural state to use all its features.
 >
-> Then we found Fly.io. Fly.io is the PaaS Platform, which can be useable for a very reasonable price. It generally falls within the `Free Allowances` range in most cases.
+> Fly.io charges according to current account and resource usage, including Machines, persistent volumes, and network usage. Check [Fly.io pricing](https://fly.io/pricing/) and the [pricing documentation](https://fly.io/docs/about/pricing/) before deploying. A time-limited trial does not provide ongoing free hosting.
 
 ## Required materials
 
@@ -31,10 +31,10 @@ This is how to configure fly.io and CouchDB on it for Self-hosted LiveSync.
 4. Copy the Setup-URI and Use it in the Obsidian.
 5. You have been synchronised. Use the Setup-URI in subsequent devices.
 
-Steps 4 and 5 are detailed in the [Quick Setup](./quick_setup.md#1-using-setup-uris).
+For steps 4 and 5, see [Set up the first device](./quick_setup.md#set-up-the-first-device), then [Add another device](./quick_setup.md#add-another-device) for subsequent devices.
 
 > [!NOTE]
-> Your automatically configured configurations will be shown on the result in the Colab note like below, and **it will not be saved**. Please make a note of it somewhere.
+> Save your own generated connection details and Setup URI securely. This is a historical Colab output example from 2024; its values are illustrative and will differ for each deployment. Replace all example credentials before deployment.
 > ```
 > -- YOUR CONFIGURATION --
 > URL     : https://billowing-dawn-6619.fly.dev
@@ -45,16 +45,18 @@ Steps 4 and 5 are detailed in the [Quick Setup](./quick_setup.md#1-using-setup-u
 
 ### B. Scripted Setup
 
-Please refer to the document of [deploy-server.sh](../utils/readme.md#deploy-serversh).
+Please refer to the document of [deploy-server.sh](../utils/readme.md#flyio-deployment).
 
 ### C. Manual Setup
 
 | Used in the text | Meaning and where to use    | Memo                                                                     |
 | ---------------- | --------------------------- | ------------------------------------------------------------------------ |
-| campanella       | Username                    | It is less likely to fail if it consists only of letters and numbers.    |
-| dfusiuada9suy    | Password                    |                                                                          |
+| `<YOUR UNIQUE COUCHDB USERNAME>` | Username                    | Choose a unique value using only letters and numbers.                     |
+| `<YOUR UNIQUE COUCHDB PASSWORD>` | Password                    | Generate a strong, unique password for this instance.                     |
 | nrt              | Region to make the instance | We can use any [region](https://fly.io/docs/reference/regions/) near us. |
 
+Choose an available, unique Fly.io application name and replace both credential placeholders before deployment. Historical output below illustrates the command responses; use your own application name, hostname, and credentials.
+
 #### 1. Install flyctl
 
 - Mac or Linux
@@ -97,8 +99,8 @@ For more information, please refer to [Sign up](https://fly.io/docs/hands-on/sig
 
 
 ```bash
-$ fly launch --name=billowing-dawn-6619 --env="COUCHDB_USER=campanella" --copy-config=true --detach --no-deploy --region nrt --yes
-$ fly secrets set COUCHDB_PASSWORD=dfusiuada9suy
+$ fly launch --name='<YOUR UNIQUE APP NAME>' --env="COUCHDB_USER=<YOUR UNIQUE COUCHDB USERNAME>" --copy-config=true --detach --no-deploy --region nrt --yes
+$ fly secrets set COUCHDB_PASSWORD='<YOUR UNIQUE COUCHDB PASSWORD>'
 ```
 
 #### 4. Deploy
@@ -177,17 +179,17 @@ This section is set up using the REST API.
 - Mac or Linux:
 
 ```bash
-export couchHost=https://billowing-dawn-6619.fly.dev
-export couchUser=campanella
-export couchPwd=dfusiuada9suy
+export couchHost='https://<YOUR APP HOSTNAME>'
+export couchUser='<YOUR UNIQUE COUCHDB USERNAME>'
+export couchPwd='<YOUR UNIQUE COUCHDB PASSWORD>'
 ```
 
 - Windows
 
 ```powershell
-set couchHost https://billowing-dawn-6619.fly.dev
-set couchUser campanella
-set couchPwd dfusiuada9suy
+set couchHost 'https://<YOUR APP HOSTNAME>'
+set couchUser '<YOUR UNIQUE COUCHDB USERNAME>'
+set couchPwd '<YOUR UNIQUE COUCHDB PASSWORD>'
 $creds = [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("${couchUser}:${couchPwd}"))
 ```
 
@@ -242,11 +244,11 @@ Note: Each of these should also be repeated until finished in 200.
 
 #### 6. Use it from Self-hosted LiveSync
 
-Now the CouchDB is ready to use from Self-hosted LiveSync. We can use `https://billowing-dawn-6619.fly.dev` in URI, `campanella` in `Username` and `dfusiuada9suy` in `Password` on Self-hosted LiveSync. The `Database name` could be anything you want.
-Please refer to the [Minimal Setup of the Quick Setup](./quick_setup.md#2-minimal-setup).
+Now the CouchDB is ready to use from Self-hosted LiveSync. Use your Fly.io app's hostname in `URI`, and the unique credentials configured above in `Username` and `Password`. The `Database name` could be anything you want.
+Please refer to [Configure CouchDB manually on the first device](./quick_setup.md#configure-couchdb-manually-on-the-first-device).
 
 ## Delete the Instance
 
 If you want to delete the CouchDB instance, you can do that in [fly.io Dashboard](https://fly.io/dashboard/personal)
 
-If you have done with [B. Scripted Setup](#b-scripted-setup), we can use [delete-server.sh](../utils/readme.md#delete-serversh).
\ No newline at end of file
+If you have done with [B. Scripted Setup](#b-scripted-setup), we can use [delete-server.sh](../utils/readme.md#flyio-deployment).
diff --git a/docs/setup_object_storage.md b/docs/setup_object_storage.md
index c2a5237b..37b93075 100644
--- a/docs/setup_object_storage.md
+++ b/docs/setup_object_storage.md
@@ -18,14 +18,14 @@ The public generator applies the Object Storage preset and records the connectio
 
 ```sh
 export remote_type=s3
-export endpoint=https://objects.example.com
-export access_key=<ACCESS KEY>
-export secret_key=<SECRET KEY>
+export endpoint='https://objects.example.com'
+export access_key='<ACCESS KEY>'
+export secret_key='<SECRET KEY>'
 export bucket=vault-data
 export region=auto
 export bucket_prefix=my-vault
-export LIVESYNC_PASSPHRASE=<A STRONG VAULT ENCRYPTION PASSPHRASE>
-export uri_passphrase=<A SEPARATE SETUP URI PASSPHRASE>
+export LIVESYNC_PASSPHRASE='<A STRONG VAULT ENCRYPTION PASSPHRASE>'
+export uri_passphrase='<A SEPARATE SETUP URI PASSPHRASE>'
 deno run --minimum-dependency-age=0 --allow-env https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/setup/generate_setup_uri.ts
 ```
 
diff --git a/docs/setup_own_server.md b/docs/setup_own_server.md
index 6924ec55..cc1994e1 100644
--- a/docs/setup_own_server.md
+++ b/docs/setup_own_server.md
@@ -122,14 +122,14 @@ The `username` and `password` in this step are CouchDB administrator credentials
 
 ```
 export hostname=http://localhost:5984
-export username=<INSERT COUCHDB ADMINISTRATOR USERNAME HERE>
-export password=<INSERT COUCHDB ADMINISTRATOR PASSWORD HERE>
+export username='<INSERT COUCHDB ADMINISTRATOR USERNAME HERE>'
+export password='<INSERT COUCHDB ADMINISTRATOR PASSWORD HERE>'
 export database=obsidiannotes
 curl -s https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/couchdb/couchdb-init.sh | bash
 ```
 
 > [!TIP]
-> In fish, `hostname` is read-only and cannot be exported. Pass the values through `env` instead: `curl -s https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/couchdb/couchdb-init.sh | env hostname=http://localhost:5984 username=<...> password=<...> database=obsidiannotes bash`.
+> In fish, `hostname` is read-only and cannot be exported. Pass the values through `env` instead: `curl -s https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/couchdb/couchdb-init.sh | env hostname='http://localhost:5984' username='<INSERT COUCHDB ADMINISTRATOR USERNAME HERE>' password='<INSERT COUCHDB ADMINISTRATOR PASSWORD HERE>' database=obsidiannotes bash`.
 
 If it results like the following:
 ```
@@ -140,7 +140,7 @@ The wrapper runs the exact registry-pinned Commonlib consumer. When `database` i
 
 If you are using Docker Compose and the above command does not work or displays `ERROR: Hostname missing`, you can try running the following command, replacing the placeholders with your own values:
 ```
-curl -s https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/couchdb/couchdb-init.sh | hostname=http://<YOUR SERVER IP>:5984 username=<INSERT COUCHDB ADMINISTRATOR USERNAME HERE> password=<INSERT COUCHDB ADMINISTRATOR PASSWORD HERE> database=obsidiannotes bash
+curl -s https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/couchdb/couchdb-init.sh | hostname='http://<YOUR SERVER IP>:5984' username='<INSERT COUCHDB ADMINISTRATOR USERNAME HERE>' password='<INSERT COUCHDB ADMINISTRATOR PASSWORD HERE>' database=obsidiannotes bash
 ```
 
 ## 3. Expose CouchDB to the Internet
@@ -148,13 +148,13 @@ curl -s https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/co
 - You can skip this instruction if you using only in intranet and only with desktop devices.
   - For mobile devices, Obsidian requires a valid SSL certificate. Usually, it needs exposing the internet.
 
-Whatever solutions we can use. For simplicity, the following sample uses Cloudflare Zero Trust for testing.
+For temporary testing, create a Cloudflare Quick Tunnel by following the [Quick Tunnels instructions](https://developers.cloudflare.com/tunnel/get-started/quick-tunnels/). It prints a random hostname which changes each time you create a tunnel, and the URL stops working when the `cloudflared` process stops. Quick Tunnels are intended for testing and development, not production. See the [Cloudflare Tunnel guide](https://developers.cloudflare.com/tunnel/get-started/) for durable use.
 
 ```
 cloudflared tunnel --url http://localhost:5984
 ```
 
-You will then get the following output:
+The following 2024 output is an example of the format. Its hostname is illustrative only; use the URL printed by your own tunnel instead.
 
 ```
 2024-02-14T10:35:25Z INF Thank you for trying Cloudflare Tunnel. Doing so, without a Cloudflare account, is a quick way to experiment and try it out. However, be aware that these account-less Tunnels have no uptime guarantee. If you intend to use Tunnels in production you should use a pre-created named tunnel by following: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
@@ -167,7 +167,7 @@ You will then get the following output:
   :
   :
 ```
-Now `https://tiles-photograph-routine-groundwater.trycloudflare.com` is our server. Make it into the background once, please.
+Use the URL printed by your tunnel as the server address. Keep the tunnel process running while you configure and test the client.
 
 
 ## 4. Client Setup
@@ -179,12 +179,12 @@ Now `https://tiles-photograph-routine-groundwater.trycloudflare.com` is our serv
 The `LIVESYNC_USER` and `LIVESYNC_PASS` here are the credentials which Self-hosted LiveSync will store for routine access to this database. They may be the administrator credentials from step 2. If you have separately configured a CouchDB account with the required access to this database, use that account instead. Neither the provisioning wrapper nor the Setup URI generator creates that separate account.
 
 ```bash
-export LIVESYNC_HOST=https://tiles-photograph-routine-groundwater.trycloudflare.com
+export LIVESYNC_HOST='<YOUR QUICK-TUNNEL URL>'
 export LIVESYNC_DB=obsidiannotes
-export LIVESYNC_USER=<INSERT COUCHDB USERNAME FOR LIVESYNC>
-export LIVESYNC_PASS=<INSERT THE COUCHDB PASSWORD>
-export LIVESYNC_PASSPHRASE=<INSERT A STRONG VAULT ENCRYPTION PASSPHRASE>
-export uri_passphrase=<INSERT A SEPARATE SETUP URI PASSPHRASE> # Optional
+export LIVESYNC_USER='<INSERT COUCHDB USERNAME FOR LIVESYNC>'
+export LIVESYNC_PASS='<INSERT THE COUCHDB PASSWORD>'
+export LIVESYNC_PASSPHRASE='<INSERT A STRONG VAULT ENCRYPTION PASSPHRASE>'
+export uri_passphrase='<INSERT A SEPARATE SETUP URI PASSPHRASE>' # Optional
 deno run --minimum-dependency-age=0 --allow-env https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/setup/generate_setup_uri.ts
 ```
 
@@ -199,9 +199,9 @@ The generator consumes the exact registry-pinned Commonlib release used by the p
 
 By default, the URI is Ephemeral and can be opened only until the exact UTC time printed by the generator. This is the end of a fixed seven-day window, not seven days after creation. Set `uri_mode=persistent` before running the command if the URI needs no time condition or must be readable by an older client that supports the existing encrypted format.
 
-You will then get the following output:
+The output has the following form. The timestamp and values below are illustrative:
 
-```bash
+```text
 Generated couchdb Setup URI.
 Ephemeral: usable until 2026-10-01T00:00:00.000Z (UTC).
 Your passphrase for the Setup URI is: H7vX...a-random-32-character-value
diff --git a/docs/setup_p2p.md b/docs/setup_p2p.md
index c755ce0a..ea334e19 100644
--- a/docs/setup_p2p.md
+++ b/docs/setup_p2p.md
@@ -127,11 +127,11 @@ The public Setup URI generator is also available when configuration must be crea
 
 ```sh
 export remote_type=p2p
-export p2p_relays=wss://relay.example.com
-export p2p_room_id=<A PRIVATE ROOM ID> # Optional; generated when omitted
-export p2p_passphrase=<A PRIVATE P2P PASSPHRASE> # Optional; generated when omitted
-export LIVESYNC_PASSPHRASE=<A STRONG VAULT ENCRYPTION PASSPHRASE>
-export uri_passphrase=<A SEPARATE SETUP URI PASSPHRASE>
+export p2p_relays='wss://relay.example.com'
+export p2p_room_id='<A PRIVATE ROOM ID>' # Optional; generated when omitted
+export p2p_passphrase='<A PRIVATE P2P PASSPHRASE>' # Optional; generated when omitted
+export LIVESYNC_PASSPHRASE='<A STRONG VAULT ENCRYPTION PASSPHRASE>'
+export uri_passphrase='<A SEPARATE SETUP URI PASSPHRASE>'
 deno run --minimum-dependency-age=0 --allow-env https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/setup/generate_setup_uri.ts
 ```
 
diff --git a/docs/tips/fast-setup.md b/docs/tips/fast-setup.md
index d67c743d..e570ed5e 100644
--- a/docs/tips/fast-setup.md
+++ b/docs/tips/fast-setup.md
@@ -1,8 +1,8 @@
 # Fast Setup (Simple Fetch)
 
-Fast Setup is a streamlined, user-friendly data retrieval and initialisation flow designed to simplify setting up secondary devices or recovering databases. 
+Fast Setup (Simple Fetch) is the preferred flow for initial replication to a new or empty secondary device. It can also be used for recovery, but a retrieval choice may replace local files. Preserve valuable local and remote copies before choosing how to handle a Vault that already contains work. See [Recovery and flag files](../recovery.md#first-choose-the-authoritative-copy) for guidance on identifying the authoritative copy.
 
-Instead of guiding the user through the detailed multi-step setup wizard dialogues, Fast Setup prompts the user with high-level sync decisions and automates database download and local storage scanning in one continuous process.
+Instead of guiding the user through the detailed multi-step setup wizard dialogues, Fast Setup prompts the user with high-level synchronisation decisions and automates data retrieval and local storage scanning in one process. The retrieval path depends on the selected remote.
 
 ---
 
@@ -16,14 +16,14 @@ On the next startup, the plug-in boots in scheduled fetch mode and opens a simpl
 
 ## Technical Characteristics
 
-Fast Setup leverages several backend optimisations to make the retrieval fast, safe, and clean:
+Fast Setup uses several retrieval and reflection behaviours:
 
-1. **Stream-based Replication for Speed**
-   - It fetches all remote metadata via stream reception, which is significantly faster than traditional chunk-by-chunk retrieval.
+1. **Stream-based Fast Fetch for CouchDB**
+   - The stream-based Fast Fetch path is CouchDB-specific. It retrieves remote Metadata incrementally; Object Storage and P2P use their own retrieval paths.
 2. **Delayed File Reflection to Prevent Corrupted Warnings**
-   - By suspending file reflection during the download phase, it prevents the plug-in from raising temporary or false "corrupted data synchronisation" or "size mismatch" warnings that can occur during the chunk download process.
-3. **Time-Based Comparison is Generally Sufficient**
-   - Since the vault is entering a fresh synchronisation or recovery state, comparing files based on their modification timestamps (newer-wins) is highly reliable and sufficient to reconcile files without needing complex manual conflict resolution.
+   - Delaying local file reflection during retrieval suppresses temporary synchronisation warnings while remote data is being fetched.
+3. **Timestamp Comparison Selects a Whole File**
+   - **Compare time and take newer** compares modification timestamps and selects one whole-file version. It does not merge file contents. Before choosing this policy for a Vault with existing work, preserve valuable local and remote edits and review [Recovery and flag files](../recovery.md#first-choose-the-authoritative-copy).
 
 ---
 
@@ -33,11 +33,11 @@ Fast Setup leverages several backend optimisations to make the retrieval fast, s
 You will be prompted to choose how the retrieved remote data will interact with your existing local files:
 
 1. **Compare time and take newer (newer-wins)**
-   - Compares the modified time of files and accepts the newer version.
-   - **Recommended if:** You have been using Self-hosted LiveSync and have made changes on multiple devices that you want to merge.
+   - Compares the modified time of files and selects the newer whole-file version; it does not combine edits from both versions.
+   - **Recommended if:** You have preserved both versions and deliberately want to select one according to its modification time.
 2. **Overwrite all with remote files (remote-wins)**
    - Remote data is treated as the source of truth.
-   - **Recommended if:** You are setting up a brand new device with an empty or clean vault.
+   - **Recommended if:** You are setting up a new secondary device with an empty Vault.
    - *Warning: This will overwrite local files with remote files. Please ensure you have a backup of your local vault before proceeding.*
 3. **Use the detailed flow (legacy)**
    - Switches back to the detailed, traditional setup wizard dialogues.
diff --git a/utils/readme.md b/utils/readme.md
index 8f0dca6f..7ef8e321 100644
--- a/utils/readme.md
+++ b/utils/readme.md
@@ -55,13 +55,13 @@ The generator defaults to `uri_mode=ephemeral`. The URI opens only during the cu
 
 ```sh
 export remote_type=s3
-export endpoint=https://objects.example.com
-export access_key=<ACCESS KEY>
-export secret_key=<SECRET KEY>
+export endpoint='https://objects.example.com'
+export access_key='<ACCESS KEY>'
+export secret_key='<SECRET KEY>'
 export bucket=vault-data
 export region=auto
 export bucket_prefix=team-a # Optional
-export LIVESYNC_PASSPHRASE=<A STRONG VAULT ENCRYPTION PASSPHRASE>
+export LIVESYNC_PASSPHRASE='<A STRONG VAULT ENCRYPTION PASSPHRASE>'
 deno run --minimum-dependency-age=0 --config=./flyio/deno.jsonc --frozen --lock=./flyio/deno.lock --allow-env ./setup/generate_setup_uri.ts
 ```
 
@@ -71,7 +71,7 @@ Optional Object Storage variables are `use_custom_request_handler`, `force_path_
 
 ```sh
 export remote_type=p2p
-export LIVESYNC_PASSPHRASE=<A STRONG VAULT ENCRYPTION PASSPHRASE>
+export LIVESYNC_PASSPHRASE='<A STRONG VAULT ENCRYPTION PASSPHRASE>'
 deno run --minimum-dependency-age=0 --config=./flyio/deno.jsonc --frozen --lock=./flyio/deno.lock --allow-env ./setup/generate_setup_uri.ts
 ```
 

From 2befb2afdb186f7be6054720e36f11c84d8f3c7a Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Tue, 27 Oct 2026 13:14:38 +0000
Subject: [PATCH 05/18] Index documentation and clarify verification entry
 points

---
 AGENTS.md      |  6 ++++
 README.md      |  2 ++
 devs.md        |  4 ++-
 docs/README.md | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 103 insertions(+), 1 deletion(-)
 create mode 100644 docs/README.md

diff --git a/AGENTS.md b/AGENTS.md
index 9e9529ec..93172ba0 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -2,6 +2,12 @@
 
 When working on this repository (writing code, comments, documentation, or commits), you MUST follow these guidelines to maintain consistency.
 
+## Documentation Navigation and Maintenance
+
+- Use the [documentation index](docs/README.md) to select the relevant implementation reference, ADR, proposal, or historical record. The required references below still apply.
+- When implementation or publication changes a recorded status, update its publication note and supporting references in the same change. Preserve the original decision date, reviewed-version baseline, and remaining follow-ups.
+- Mark superseded or frozen documents at their entry point and link to the maintained reference. Keep historical evidence distinguishable from current operating instructions, and preserve existing links when reorganising documentation.
+
 ## Required Reference Files
 
 Before making changes to documentation, user-facing text, or settings:
diff --git a/README.md b/README.md
index 8bdbacef..3503eb81 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,8 @@
 # Self-hosted LiveSync
 [Japanese docs](./README_ja.md) - [Chinese docs](./README_cn.md).
 
+Find setup guides, troubleshooting, technical references, design decisions, and historical material in the [documentation index](docs/README.md).
+
 
 Self-hosted LiveSync is a community-developed synchronisation plug-in available on all Obsidian-compatible platforms. It leverages robust server solutions such as CouchDB or object storage systems (e.g., MinIO, S3, R2, etc.) to ensure reliable data synchronisation.
 
diff --git a/devs.md b/devs.md
index a9279f14..5fdbbb2b 100644
--- a/devs.md
+++ b/devs.md
@@ -1,5 +1,7 @@
 # Self-hosted LiveSync Development Guide
 
+Use the [documentation index](docs/README.md) to find implementation references, architectural decisions, proposals, and historical material for the area being changed.
+
 ## Project Overview
 
 Self-hosted LiveSync is an Obsidian plugin for synchronising vaults across devices using CouchDB, MinIO/S3, or peer-to-peer WebRTC. The codebase uses a modular architecture with TypeScript, Svelte, and PouchDB.
@@ -78,7 +80,7 @@ Regression tests remain in the suite owned by the implementation under test. Plu
 
 - **CLI E2E** (`src/apps/cli/testdeno/`): Host-independent consumer workflows. The canonical Compose P2P suite covers ordinary two-peer synchronisation, replacement of the current Replicator followed by transfer with the same peer, and explicit relay disconnection followed by paused and resumed reconnection. Its lifecycle entry point is included only in the Docker test build and does not add a public CLI command. Run `npm run test:e2e:cli` for the ordinary suite or `npm run test:e2e:cli:p2p` for P2P validation.
 - **Self-hosted setup tools** (`utils/couchdb/`, `utils/setup/`, and `utils/flyio/`): Deno contract tests consume the exact locked Commonlib registry package, verify current CouchDB, Object Storage, and random-room P2P Setup URI defaults and remote profiles, and keep CouchDB administration separate from package-owned LiveSync database-version negotiation. `unit-ci` also provisions a real temporary CouchDB database and verifies its version document against the installed Commonlib package. Run `npm run test:setup-tools` for the local contract gate.
-- **Real Obsidian E2E** (`test/e2e-obsidian/`): Local-first scripts that launch real Obsidian with temporary vaults and the built Self-hosted LiveSync plug-in. Use these for boot-up sequence, vault reflection, RedFlag flows, Fast Setup (Simple Fetch), settings dialogues, restart-sensitive workflows, Object Storage regressions, and other behaviour that depends on Obsidian itself. Run focused scripts such as `npm run test:e2e:obsidian:two-vault-sync`, or use `npm run test:e2e:obsidian:local-suite:services` to run the broader local suite with CouchDB and RustFS fixtures managed by the wrapper.
+- **Real Obsidian E2E** (`test/e2e-obsidian/`): Local-first scripts that launch real Obsidian with temporary vaults and the built Self-hosted LiveSync plug-in. Use these for boot-up sequence, vault reflection, RedFlag flows, Fast Setup (Simple Fetch), settings dialogues, restart-sensitive workflows, Object Storage regressions, and other behaviour that depends on Obsidian itself. After source changes, run the build-owning wrapper, for example `npm run test:e2e:obsidian:focused -- two-vault-sync`, with the required fixture already running. Direct scenario scripts reuse the existing bundle and are suitable for reruns only while that build remains unchanged. Use `npm run test:e2e:obsidian:local-suite:services` to run the broader local suite with CouchDB and RustFS fixtures managed by the wrapper.
 
 - **Docker Services**: Service-backed tests use CouchDB and RustFS (S3). Canonical P2P validation owns its relay through the CLI Compose runner:
 
diff --git a/docs/README.md b/docs/README.md
new file mode 100644
index 00000000..86d2afd0
--- /dev/null
+++ b/docs/README.md
@@ -0,0 +1,92 @@
+# Documentation index
+
+Choose a document by the task and its status. User guides describe supported operations; implementation references describe contracts and their limits; ADRs record why a decision was made. Proposals and historical designs are grouped separately below.
+
+A document's original date and reviewed-version fields describe its baseline. Read its implementation or publication note before treating that baseline as the current release. A published feature does not by itself establish that every proposal or validation step in its design is complete.
+
+## Setup and everyday use
+
+| Task | Start here |
+|---|---|
+| Choose a synchronisation method | [Project overview and setup workflows](../README.md#setup-workflows) |
+| Set up CouchDB clients | [CouchDB server setup](setup_own_server.md), then [Quick setup](quick_setup.md) |
+| Choose a packaged CouchDB deployment | [Docker stack](../docker/README.md), [Fly.io](setup_flyio.md), or [IBM Cloudant](setup_cloudant.md) |
+| Set up S3-compatible storage | [Object Storage Setup](setup_object_storage.md) |
+| Set up peer-to-peer synchronisation | [P2P communication model](p2p.md), then [Peer-to-Peer Setup](setup_p2p.md) |
+| Diagnose P2P connectivity | [Browser-assisted check](../src/apps/webpeer/README.md#p2p-connection-check), [network tips](tips/p2p-sync-tips.md), and [self-hosted TURN](../docker/coturn/README.md) |
+| Understand a setting or command | [Settings reference](settings.md) |
+| Investigate or recover from a problem | [Troubleshooting](troubleshooting.md), then the relevant [recovery procedure](recovery.md) |
+| Prepare an issue report | [Issue reporting](to_issue_reporting.md) |
+
+The project overview links to Japanese and Chinese documentation.
+
+## Implementation and technical references
+
+Use these references for the area being changed, together with its relevant ADR. Check the document's stated scope and validation limits before relying on a guarantee.
+
+| Area | References |
+|---|---|
+| Overall synchronisation and terminology | [Technical overview](tech_info.md), [glossary](glossary.md), and [terminology conventions](terms.md) |
+| Metadata, Chunks, and database representations | [Data structures](datastructure.md) |
+| Conflict resolution, provenance, and history restoration | [Conflict and provenance contract](specs_conflict_resolution.md), [Document History restoration](design_docs/document_history_revision_restoration.md), and [local save completion](adr/2026_10_local_file_save_completion_and_batching.md) |
+| Replicator and host boundaries | [Replicator architecture snapshot](design_docs/replicator_architecture.md) and [service feature and legacy Module boundaries](design_docs/service_feature_and_legacy_module_boundaries.md) |
+| Chunk retrieval and maintenance | [Chunk retrieval and waiting](design_docs/chunk_retrieval_and_waiting.md), [Garbage Collection V3](specs_garbage_collection.md), and [Data Compression](specs_data_compression.md) |
+| Document identity and validation | [Unicode path identity](design_docs/unicode_path_identity.md), [configurable ID derivation](design_docs/configurable_id_derivation.md), [Metadata ID validation and repair](design_docs/metadata_document_id_validation_and_repair.md), and [path component compatibility](design_docs/path_component_length_compatibility.md) |
+| Settings compatibility and profiles | [Tweak compatibility and recovery](design_docs/tweak_compatibility.md) and [remote configuration management](design_docs_of_remote_configurations.md) |
+| Encryption and sharing | [Metadata encryption](design_docs/internal_metadata_encryption.md) and [time-bound Setup URIs](design_docs/time_bound_setup_uri.md) |
+| P2P connection preparation | [TURN connection settings](design_docs/renewable_turn_credentials.md) |
+| Journal storage internals | [Journal Replicator 2nd Edition](design_docs_of_journalsync_2nd.md) |
+
+The installed `@vrtmrz/livesync-commonlib` package is authoritative for shared runtime contracts. Use the exact dependency selected by [package.json](../package.json) and its lockfile when checking behaviour. The [Commonlib documentation](https://github.com/vrtmrz/livesync-commonlib/tree/main/docs) is maintained in that repository; this index does not replace its package contracts.
+
+## Architectural decisions
+
+Read the decisions relevant to the change, rather than treating the whole ADR directory as a prerequisite. A decision's acceptance, its implementation, its release, and its remaining verification work are separate facts.
+
+| Decision area | Records |
+|---|---|
+| Shared package boundary | [Common library package boundary](adr/2026_07_common_library_package_boundary.md) |
+| Replicator capabilities and migration | [Core contract](adr/2026_08_replicator_capabilities_01_core_contract.md), [P2P service lifecycle](adr/2026_08_replicator_capabilities_02_p2p_service_lifecycle.md), and [migration plan](adr/2026_08_replicator_capabilities_03_migration_plan.md) |
+| Remote resources and Fast Setup | [CouchDB connection ownership](adr/2026_08_couchdb_remote_connection_ownership.md), [Fast Fetch eligibility](adr/2026_08_fast_fetch_transport_eligibility.md), and [persistence and completion](adr/2026_08_fast_fetch_persistence_and_completion.md) |
+| P2P lifecycle and setup | [Transport lifecycle](adr/2026_07_p2p_transport_lifecycle.md), [connection check](adr/2026_07_p2p_connection_check.md), [profile-aware onboarding](adr/2026_07_multiple_remote_onboarding.md), and [compatibility controls](adr/2026_08_p2p_transport_compatibility.md) |
+| Settings interface integration | [Declarative settings adapter](adr/2026_08_declarative_settings_adapter.md) |
+| Saving and path identity | [Local file save completion and batching](adr/2026_10_local_file_save_completion_and_batching.md) and [Unicode path identity](adr/2026_10_unicode_path_identity.md) |
+| Activity and Chunk arrival | [Bounded remote activity](adr/2026_07_bounded_remote_activity.md) and [Chunk arrival quiescence](adr/2026_07_chunk_arrival_quiescence.md) |
+| Compatibility and validation | [Release notes and database compatibility gates](adr/2026_07_release_notes_and_database_compatibility.md) and [real Obsidian E2E](adr/2026_06_real_obsidian_e2e.md) |
+
+## Proposals and incomplete explanations
+
+These records are useful for design work. Their proposed representation or behaviour is not a current runtime contract.
+
+| Document | Recorded state |
+|---|---|
+| [Tiered Chunk Storage with Live Compaction](design_docs/tired_chunk_pack.md) | In design |
+| [Tiered Chunk Storage for Bucket Sync](design_docs/tired_chunk_pack_bucket.md) | In design |
+| [Design intent for Metadata and Chunks](design_docs/intention_of_chunks.md) | Incomplete explanation; use the data-structure reference for current representations |
+| [Feature maturity for 1.0](adr/2026_07_feature_maturity_for_1_0.md) | Proposed; publication of 1.0 alone does not establish formal acceptance of this record |
+
+## Historical and retired designs
+
+These documents preserve earlier motivations, approaches, or results. Follow their maintained replacement for current operations.
+
+| Historical material | Current starting point |
+|---|---|
+| [Original Tweak-sharing proposal](design_docs_of_sharing_tweak_value.md) | [Tweak compatibility and recovery](design_docs/tweak_compatibility.md) |
+| [First Journal Sync design](design_docs_of_journalsync.md) | [Journal Replicator 2nd Edition](design_docs_of_journalsync_2nd.md) |
+| [Eden design and operational results](design_docs_of_keep_newborn_chunks.md#results-from-actual-operation) | The document records its deprecated, frozen status; use [Data structures](datastructure.md) for representations still accepted by current code |
+| [Withdrawn Chunk Aggregation by Prefix](design_docs/chunk_aggregation_by_prefix.md) | Retained as a withdrawn proposal, not an implemented storage layout |
+
+Dated measurements, including the [Data Compression benchmark](specs_data_compression.md#reproducible-benchmark), remain evidence for their recorded revision and environment. A current rerun is a separate measurement.
+
+## Development, validation, and release history
+
+- [Development guide](../devs.md): build, module ownership, and release workflow.
+- [Contributing](../CONTRIBUTING.md): contribution and documentation checks.
+- Independent applications: [CLI](../src/apps/cli/README.md), [WebApp](../src/apps/webapp/README.md), and [WebPeer](../src/apps/webpeer/README.md).
+- [Setup utilities](../utils/readme.md): provisioning and Setup URI generation.
+- [Review Harness](review_harness.md): bounded real-device observations and performance measurements.
+- [Test procedures](../test/README.md): choose the suite which owns the boundary being changed.
+- [Change notes](../updates.md): current release and unreleased changes.
+- Published release archives: [1.0](releases/1.0.md), [1.0 previews](releases/1.0-previews.md), [0.25](releases/0.25.md), and [earlier releases](releases/legacy.md).
+
+When a feature ships or a design is replaced, update its implementation note and this index if its role changes. Preserve the original decision and measurement history, state the maintained replacement, and keep existing links working.

From 68a232c6dfd8456706ba26615f523def10fd753c Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Tue, 27 Oct 2026 17:21:44 +0000
Subject: [PATCH 06/18] Move status customisation details out of the project
 overview

---
 README.md                   | 88 +++++++------------------------------
 docs/README.md              |  1 +
 docs/settings.md            |  2 +
 docs/tips/status-display.md | 54 +++++++++++++++++++++++
 4 files changed, 72 insertions(+), 73 deletions(-)
 create mode 100644 docs/tips/status-display.md

diff --git a/README.md b/README.md
index 3503eb81..279558b8 100644
--- a/README.md
+++ b/README.md
@@ -1,13 +1,12 @@
 # Self-hosted LiveSync
 [Japanese docs](./README_ja.md) - [Chinese docs](./README_cn.md).
 
-Find setup guides, troubleshooting, technical references, design decisions, and historical material in the [documentation index](docs/README.md).
-
-
 Self-hosted LiveSync is a community-developed synchronisation plug-in available on all Obsidian-compatible platforms. It leverages robust server solutions such as CouchDB or object storage systems (e.g., MinIO, S3, R2, etc.) to ensure reliable data synchronisation.
 
 Additionally, it supports peer-to-peer synchronisation using WebRTC, enabling devices to exchange notes without a central data-storage server. A signalling relay is still required for peer discovery. See [How peer-to-peer synchronisation works](./docs/p2p.md).
 
+Find setup guides, troubleshooting, technical references, design decisions, and historical material in the [documentation index](docs/README.md).
+
 ![obsidian_live_sync_demo](https://user-images.githubusercontent.com/45774780/137355323-f57a8b09-abf2-4501-836c-8cb7d2ff24a3.gif)
 
 >[!IMPORTANT]
@@ -36,39 +35,23 @@ This plug-in may be particularly useful for researchers, engineers, and develope
 
 ## How to Use
 
-### 3-minute setup - CouchDB on fly.io
-
-**Recommended for beginners**
-
-[![LiveSync Setup onto Fly.io SpeedRun 2024 using Google Colab](https://img.youtube.com/vi/7sa_I1832Xc/0.jpg)](https://www.youtube.com/watch?v=7sa_I1832Xc)
-
-1. [Set up CouchDB on fly.io](docs/setup_flyio.md)
-2. Configure plug-in in [Quick Setup](docs/quick_setup.md)
-
 ### Setup workflows
 
 Choose a synchronisation method, prepare its server where required, then follow the corresponding client setup:
 
-1. CouchDB
-   1. Prepare the server:
-      - [Set up your own CouchDB server](docs/setup_own_server.md).
-      - [Set up CouchDB on fly.io](docs/setup_flyio.md).
-   2. Configure the clients by following [CouchDB Quick Setup](docs/quick_setup.md).
-2. Object Storage
-   1. Prepare the server. A maintained MinIO server installation guide is not currently available here, so set up an S3-compatible service or server of your choice.
-   2. Configure the clients by following [Object Storage Setup](docs/setup_object_storage.md).
-3. Peer-to-Peer
-   1. No central data-storage server is required. The project's public signalling relay requires no server provisioning; controlled deployments can provide another compatible relay.
-   2. Configure the clients by following [Peer-to-Peer Setup](docs/setup_p2p.md).
+| Method | What you need | Setup guides |
+| --- | --- | --- |
+| CouchDB | A CouchDB server you operate or trust. | [Own server](docs/setup_own_server.md), [Docker stack](docker/README.md), [Fly.io](docs/setup_flyio.md), or [IBM Cloudant](docs/setup_cloudant.md); then [Quick Setup](docs/quick_setup.md). |
+| Object Storage | An S3-compatible service or server. | [Object Storage Setup](docs/setup_object_storage.md). |
+| Peer-to-Peer | A signalling relay and an online device containing the data you need. | [P2P communication model](docs/p2p.md), then [Peer-to-Peer Setup](docs/setup_p2p.md). |
 
-Each workflow establishes ordinary note synchronisation on the first device, generates a Setup URI for each additional device from that working device, and verifies synchronisation in both directions.
+The project's public P2P signalling relay requires no server provisioning; controlled deployments can provide another compatible relay. A maintained MinIO server installation guide is not currently available here, so Object Storage users need to prepare their chosen S3-compatible service or server separately.
 
-> [!TIP]
-> Fly.io is no longer free. Fortunately, we can still use IBM Cloudant despite some limitations. Refer to [Set up IBM Cloudant](docs/setup_cloudant.md).
-> We can also use peer-to-peer synchronisation without a central data-storage server; a signalling relay is still used for peer discovery. Alternatively, cheap object storage like Cloudflare R2 can be used for free.
-> However, most importantly, we can use a server that we trust. Therefore, please set up your own server.
-> CouchDB can also be run on a Raspberry Pi (please be mindful of your server's security).
+Each workflow establishes ordinary note synchronisation on the first device, generates a Setup URI for each additional device from that working device, and verifies synchronisation in both directions. The linked hosting guides explain provider-specific setup and costs.
 
+<a id="3-minute-setup---couchdb-on-flyio"></a>
+
+For the Fly.io video walkthrough, see [automated setup](docs/setup_flyio.md#a-very-automated-setup).
 
 ### Third-party managed CouchDB hosting
 
@@ -79,52 +62,11 @@ If you would rather not set up and maintain a server yourself, Zenith Hosting of
 
 ## Information in the Status Bar
 
-Synchronisation status is shown in the status bar with the following icons.
+<a id="customising-status-items-with-css-snippets"></a>
 
--   Activity Indicator
-    -   📲 A finite remote operation is in progress
-    -   🌐N Approximate remote requests currently in progress
--   Status
-    -   ⏹️ Stopped
-    -   ⏩ Comparing CouchDB change history, including entries already held locally
-    -   💤 LiveSync enabled. Waiting for changes
-    -   ⚡️ Synchronisation in progress
-    -   ⚠ An error occurred
--   Statistical Indicators
-     -   ↑ Uploaded chunks and metadata
-     -   ↓ Downloaded chunks and metadata
--   Progress Indicators
-     -   📥 Unprocessed transferred items
-     -   📄 Working database operation
-     -   💾 Working write storage processes
-     -   ⏳ Working read storage processes
-     -   🛫 Pending read storage processes
-     -   📬 Batched read storage processes
-     -   ⚙️ Working or pending storage processes for hidden files
-     -   🛄 Pending initial on-demand chunk requests
-     -   🔁 Pending chunk retries, including retry delays
-     -   🔌 Working customisation items (configuration, snippets, and plug-ins)
+See the [status display guide](docs/tips/status-display.md) for icon meanings, progress counters, and [CSS customisation](docs/tips/status-display.md#customising-status-items-with-css-snippets).
 
-To prevent file and database corruption, please avoid closing Obsidian until all progress indicators have disappeared as much as possible (although the plug-in will attempt to resume if interrupted). This is especially important if you have deleted or renamed files.
-
-When CouchDB change history is being compared, `(⏩ 1200) ↑ 0 ↓ 0` can appear before any new documents arrive. The count is the number of candidate changes-feed entries compared during the current replication attempt, including repeated entries on retries. It is separate from downloaded Chunks and Metadata, and is neither a Vault file count nor a count of entries already present locally. It appears before the upload count, disappears after three seconds without a change, and reappears when the count changes. The ⏩ status icon follows comparison activity independently of that timer.
-
-### Customising status items with CSS snippets
-
-The status bar and editor overlay use individual spans with the common `livesync-stat-` class prefix. CSS snippets can hide or style the items we need. For example, this hides the comparison count and P2P summary:
-
-```css
-.livesync-stat-ff,
-.livesync-stat-p2p {
-    display: none;
-}
-```
-
-The item classes include `livesync-stat-network`, `livesync-stat-sync`, `livesync-stat-sent`, `livesync-stat-push-remaining`, `livesync-stat-arrived`, `livesync-stat-pull-remaining`, `livesync-stat-ff`, and `livesync-stat-p2p`. File-processing items use `livesync-stat-file-processing`, `livesync-stat-file-pending`, and `livesync-stat-file-batched`; queue items use `livesync-stat-queue-` followed by `replication`, `database`, `storage`, `chunk-initial`, `chunk-retrying`, `plugin-scan`, `hidden-files`, or `conflicts`. The skipped-file indicator uses `livesync-stat-file-skip`.
-
-All items also have `livesync-stat-item`. Numeric children use `livesync-stat-value`, tabular digits, and right alignment. Each numeric item retains its widest displayed digit count during an active period, reducing movement as counts decrease. The editor overlay uses wider gaps between items, while remaining counts stay beside their transfer totals.
-
-Inactive items receive `livesync-stat-inactive` instead of the HTML `hidden` attribute. The default CSS hides them immediately. They retain their last text, numeric width, and position amongst the other items so that CSS snippets can customise how they disappear. The numeric width starts afresh when an item becomes active again.
+Allow pending file operations to finish before closing Obsidian, especially after deleting or renaming files.
 
 ## Tips and Troubleshooting
 - If you want a faster and simpler initial replication when setting up subsequent devices, see the [Fast Setup Guide](docs/tips/fast-setup.md).
diff --git a/docs/README.md b/docs/README.md
index 86d2afd0..79d97e6d 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -15,6 +15,7 @@ A document's original date and reviewed-version fields describe its baseline. Re
 | Set up peer-to-peer synchronisation | [P2P communication model](p2p.md), then [Peer-to-Peer Setup](setup_p2p.md) |
 | Diagnose P2P connectivity | [Browser-assisted check](../src/apps/webpeer/README.md#p2p-connection-check), [network tips](tips/p2p-sync-tips.md), and [self-hosted TURN](../docker/coturn/README.md) |
 | Understand a setting or command | [Settings reference](settings.md) |
+| Read or customise synchronisation status | [Status indicators and CSS snippets](tips/status-display.md) |
 | Investigate or recover from a problem | [Troubleshooting](troubleshooting.md), then the relevant [recovery procedure](recovery.md) |
 | Prepare an issue report | [Issue reporting](to_issue_reporting.md) |
 
diff --git a/docs/settings.md b/docs/settings.md
index 135351aa..359b109c 100644
--- a/docs/settings.md
+++ b/docs/settings.md
@@ -161,6 +161,8 @@ Following panes will be shown when you enable this setting.
 
 ### 1. Appearance
 
+For icon meanings, progress counters, and CSS snippets, see the [status display guide](tips/status-display.md).
+
 #### Display Language
 
 Setting key: displayLanguage
diff --git a/docs/tips/status-display.md b/docs/tips/status-display.md
new file mode 100644
index 00000000..751d143e
--- /dev/null
+++ b/docs/tips/status-display.md
@@ -0,0 +1,54 @@
+# Synchronisation status and CSS customisation
+
+Use [General Settings](../settings.md#2-general-settings) to choose whether synchronisation status appears in the status bar, inside the editor, or both. The following sections explain the indicators and how to customise their appearance.
+
+## Status indicators
+
+-   Activity Indicator
+    -   📲 A finite remote operation is in progress
+    -   🌐N Approximate remote requests currently in progress
+-   Status
+    -   ⏹️ Stopped
+    -   ⏩ Comparing CouchDB change history, including entries already held locally
+    -   💤 LiveSync enabled. Waiting for changes
+    -   ⚡️ Synchronisation in progress
+    -   ⚠ An error occurred
+-   Statistical Indicators
+     -   ↑ Uploaded chunks and metadata
+     -   ↓ Downloaded chunks and metadata
+-   Progress Indicators
+     -   📥 Unprocessed transferred items
+     -   📄 Working database operation
+     -   💾 Working write storage processes
+     -   ⏳ Working read storage processes
+     -   🛫 Pending read storage processes
+     -   📬 Batched read storage processes
+     -   ⚙️ Working or pending storage processes for hidden files
+     -   🛄 Pending initial on-demand chunk requests
+     -   🔁 Pending chunk retries, including retry delays
+     -   🔌 Working customisation items (configuration, snippets, and plug-ins)
+
+To prevent file and database corruption, please avoid closing Obsidian until all progress indicators have disappeared as much as possible (although the plug-in will attempt to resume if interrupted). This is especially important if you have deleted or renamed files.
+
+## CouchDB comparison count
+
+When CouchDB change history is being compared, `(⏩ 1200) ↑ 0 ↓ 0` can appear before any new documents arrive. The count is the number of candidate changes-feed entries compared during the current replication attempt, including repeated entries on retries. It is separate from downloaded Chunks and Metadata, and is neither a Vault file count nor a count of entries already present locally. It appears before the upload count, disappears after three seconds without a change, and reappears when the count changes. The ⏩ status icon follows comparison activity independently of that timer.
+
+## Customising status items with CSS snippets
+
+The status bar and editor overlay use individual spans with the common `livesync-stat-` class prefix. CSS snippets can hide or style individual items. For example, this hides the comparison count and P2P summary:
+
+```css
+.livesync-stat-ff,
+.livesync-stat-p2p {
+    display: none;
+}
+```
+
+The item classes include `livesync-stat-network`, `livesync-stat-sync`, `livesync-stat-sent`, `livesync-stat-push-remaining`, `livesync-stat-arrived`, `livesync-stat-pull-remaining`, `livesync-stat-ff`, and `livesync-stat-p2p`. File-processing items use `livesync-stat-file-processing`, `livesync-stat-file-pending`, and `livesync-stat-file-batched`; queue items use `livesync-stat-queue-` followed by `replication`, `database`, `storage`, `chunk-initial`, `chunk-retrying`, `plugin-scan`, `hidden-files`, or `conflicts`. The skipped-file indicator uses `livesync-stat-file-skip`.
+
+All items also have `livesync-stat-item`. Numeric children use `livesync-stat-value`, tabular digits, and right alignment. Each numeric item retains its widest displayed digit count during an active period, reducing movement as counts decrease. The editor overlay uses wider gaps between items, while remaining counts stay beside their transfer totals.
+
+Inactive items receive `livesync-stat-inactive` instead of the HTML `hidden` attribute. The default CSS hides them immediately. They retain their last text, numeric width, and position amongst the other items so that CSS snippets can customise how they disappear. The numeric width starts afresh when an item becomes active again.
+
+See the [documentation index](../README.md) for setup and troubleshooting guides.

From bd0d81d7a7111170fa099b100cb3c7adc76bbf50 Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Wed, 28 Oct 2026 04:25:05 +0000
Subject: [PATCH 07/18] Restore basic status icons and clarify P2P setup
 requirements

---
 README.md | 27 ++++++++++++++++++++-------
 1 file changed, 20 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index 279558b8..f49adbe5 100644
--- a/README.md
+++ b/README.md
@@ -39,13 +39,13 @@ This plug-in may be particularly useful for researchers, engineers, and develope
 
 Choose a synchronisation method, prepare its server where required, then follow the corresponding client setup:
 
-| Method | What you need | Setup guides |
-| --- | --- | --- |
-| CouchDB | A CouchDB server you operate or trust. | [Own server](docs/setup_own_server.md), [Docker stack](docker/README.md), [Fly.io](docs/setup_flyio.md), or [IBM Cloudant](docs/setup_cloudant.md); then [Quick Setup](docs/quick_setup.md). |
-| Object Storage | An S3-compatible service or server. | [Object Storage Setup](docs/setup_object_storage.md). |
-| Peer-to-Peer | A signalling relay and an online device containing the data you need. | [P2P communication model](docs/p2p.md), then [Peer-to-Peer Setup](docs/setup_p2p.md). |
+| Method | What you need | Nice to have | Setup guides |
+| --- | --- | --- | --- |
+| CouchDB | A CouchDB server you operate or trust. | — | [Own server](docs/setup_own_server.md), [Docker stack](docker/README.md), [Fly.io](docs/setup_flyio.md), or [IBM Cloudant](docs/setup_cloudant.md); then [Quick Setup](docs/quick_setup.md). |
+| Object Storage | An S3-compatible service or server. | — | [Object Storage Setup](docs/setup_object_storage.md). |
+| Peer-to-Peer | Nothing. | Your own signalling server. | [P2P communication model](docs/p2p.md), then [Peer-to-Peer Setup](docs/setup_p2p.md). |
 
-The project's public P2P signalling relay requires no server provisioning; controlled deployments can provide another compatible relay. A maintained MinIO server installation guide is not currently available here, so Object Storage users need to prepare their chosen S3-compatible service or server separately.
+P2P can use the project's public signalling relay, so there is no server to provision. An optional self-hosted signalling server must be Nostr-compatible. A maintained MinIO server installation guide is not currently available here, so Object Storage users need to prepare their chosen S3-compatible service or server separately.
 
 Each workflow establishes ordinary note synchronisation on the first device, generates a Setup URI for each additional device from that working device, and verifies synchronisation in both directions. The linked hosting guides explain provider-specific setup and costs.
 
@@ -62,9 +62,22 @@ If you would rather not set up and maintain a server yourself, Zenith Hosting of
 
 ## Information in the Status Bar
 
+Synchronisation status is shown in the status bar and inside the editor by default. The main indicators are:
+
+| Indicator | Meaning |
+| --- | --- |
+| ⏹️ | Stopped. |
+| 🌀 | Starting synchronisation. |
+| 💤 | LiveSync mode is waiting for changes. |
+| ⚡️ | Synchronisation is in progress. |
+| ⏩ | Comparing CouchDB change history, including entries already held locally. |
+| ⚠ | An error occurred. |
+| ↑ / ↓ | Uploaded / downloaded Chunks and Metadata. |
+| 📲 / 🌐N | A finite remote operation is in progress / approximate remote requests in progress. |
+
 <a id="customising-status-items-with-css-snippets"></a>
 
-See the [status display guide](docs/tips/status-display.md) for icon meanings, progress counters, and [CSS customisation](docs/tips/status-display.md#customising-status-items-with-css-snippets).
+See the [status display guide](docs/tips/status-display.md) for detailed progress counters and [CSS customisation](docs/tips/status-display.md#customising-status-items-with-css-snippets).
 
 Allow pending file operations to finish before closing Obsidian, especially after deleting or renaming files.
 

From b8dc4d0c0ba51569ece786ae6f0a00f606324ff6 Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Wed, 28 Oct 2026 04:31:03 +0000
Subject: [PATCH 08/18] List third-party hosting providers under a shared
 notice

---
 README.md | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index f49adbe5..55146577 100644
--- a/README.md
+++ b/README.md
@@ -56,9 +56,15 @@ For the Fly.io video walkthrough, see [automated setup](docs/setup_flyio.md#a-ve
 ### Third-party managed CouchDB hosting
 
 > [!NOTE]
-> The following is a third-party hosting option proposed by Zenith Hosting. It is not an official Self-hosted LiveSync service, and it is neither endorsed nor recommended by this project.
+> The services below are operated by third parties. They are not official Self-hosted LiveSync services, and this project neither endorses nor recommends them.
 
-If you would rather not set up and maintain a server yourself, Zenith Hosting offers a managed CouchDB server which this plug-in can be configured to connect to: [Zenith Hosting](https://zenith.hosting/host/obsidian-livesync). As with any hosted service, your data will reside on a server operated by a third party, so please consider whether that is acceptable for your vault before using it.
+If you prefer a hosted CouchDB server, the following providers offer options for this plug-in:
+
+| Provider | Offering |
+| --- | --- |
+| [Zenith Hosting](https://zenith.hosting/host/obsidian-livesync) | Managed CouchDB hosting. |
+
+Your synchronisation data will reside on a server operated by the provider. Consider whether that is acceptable for your Vault, and review the provider's current terms, pricing, and data-handling policies before using the service.
 
 ## Information in the Status Bar
 

From ec12e132827c2676542b9a57727fa3bcdec26f5f Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Wed, 28 Oct 2026 05:01:42 +0000
Subject: [PATCH 09/18] Correct recovery guidance and setup credential encoding

Preserve Vault and remote data before deleting a Fly.io instance. Build cluster setup JSON with jq and ConvertTo-Json so credential characters remain intact.

Also include the starting status icon and clarify the CouchDB hosting category.
---
 docs/README.md              |  2 +-
 docs/setup_flyio.md         | 35 +++++++++++++++++++++++++++++------
 docs/tips/status-display.md |  1 +
 3 files changed, 31 insertions(+), 7 deletions(-)

diff --git a/docs/README.md b/docs/README.md
index 79d97e6d..9c5499f9 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -10,7 +10,7 @@ A document's original date and reviewed-version fields describe its baseline. Re
 |---|---|
 | Choose a synchronisation method | [Project overview and setup workflows](../README.md#setup-workflows) |
 | Set up CouchDB clients | [CouchDB server setup](setup_own_server.md), then [Quick setup](quick_setup.md) |
-| Choose a packaged CouchDB deployment | [Docker stack](../docker/README.md), [Fly.io](setup_flyio.md), or [IBM Cloudant](setup_cloudant.md) |
+| Choose a CouchDB hosting option | [Docker stack](../docker/README.md), [Fly.io](setup_flyio.md), or [IBM Cloudant](setup_cloudant.md) |
 | Set up S3-compatible storage | [Object Storage Setup](setup_object_storage.md) |
 | Set up peer-to-peer synchronisation | [P2P communication model](p2p.md), then [Peer-to-Peer Setup](setup_p2p.md) |
 | Diagnose P2P connectivity | [Browser-assisted check](../src/apps/webpeer/README.md#p2p-connection-check), [network tips](tips/p2p-sync-tips.md), and [self-hosted TURN](../docker/coturn/README.md) |
diff --git a/docs/setup_flyio.md b/docs/setup_flyio.md
index 0b926b3f..fcc3c1ee 100644
--- a/docs/setup_flyio.md
+++ b/docs/setup_flyio.md
@@ -4,9 +4,7 @@
 This is how to configure fly.io and CouchDB on it for Self-hosted LiveSync.
 
 > [!WARNING]
-> It is **your** instance. In Obsidian, we have files locally. Hence, do not hesitate to destroy the remote database if you feel something have got weird. We can launch and switch to the new CouchDB instance anytime[^1].
-> 
-[^1]: Actually, I am always building the database for reproduction of the issue like so.
+> Before replacing or deleting an existing CouchDB instance, back up every available Vault and the remote database, then [choose the authoritative copy](recovery.md#first-choose-the-authoritative-copy). Stop or suspend synchronisation on other devices while reviewing recovery options. Local files alone do not establish that every needed edit or revision has been preserved.
 
 > [!NOTE] 
 > **What and why is the Fly.io?**  
@@ -172,7 +170,7 @@ Visit your newly deployed app at https://billowing-dawn-6619.fly.dev/
 
 After the initial setup, CouchDB needs some more customisations to be used from Self-hosted LiveSync. It can be configured in browsers or by HTTP-REST APIs.
 
-This section is set up using the REST API.
+This section uses the REST API. The macOS and Linux commands require [jq](https://jqlang.org/download/) to encode credentials as JSON. Windows uses PowerShell's built-in `ConvertTo-Json`.
 
 1. Prepare environment variables.
 
@@ -198,13 +196,36 @@ $creds = [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes(
 - Mac or Linux
 
 ```bash
-curl -X POST "${couchHost}/_cluster_setup" -H "Content-Type: application/json" -d "{\"action\":\"enable_single_node\",\"username\":\"${couchUser}\",\"password\":\"${couchPwd}\",\"bind_address\":\"0.0.0.0\",\"port\":5984,\"singlenode\":true}"  --user "${couchUser}:${couchPwd}"
+clusterSetupJSON=$(jq -n \
+  --arg username "$couchUser" \
+  --arg password "$couchPwd" \
+  '{
+    action: "enable_single_node",
+    username: $username,
+    password: $password,
+    bind_address: "0.0.0.0",
+    port: 5984,
+    singlenode: true
+  }') &&
+curl -X POST "${couchHost}/_cluster_setup" \
+  -H "Content-Type: application/json" \
+  --data-binary "$clusterSetupJSON" \
+  --user "${couchUser}:${couchPwd}"
 ```
 
 - Windows
 
 ```powershell
-iwr -UseBasicParsing -Method 'POST' -ContentType 'application/json; charset=utf-8' -Headers @{ 'Authorization' = 'Basic ' + $creds } "${couchHost}/_cluster_setup" -Body "{""action"":""enable_single_node"",""username"":""${couchUser}"",""password"":""${couchPwd}"",""bind_address"":""0.0.0.0"",""port"":5984,""singlenode"":true}"
+$clusterSetupJSON = @{
+    action = 'enable_single_node'
+    username = $couchUser
+    password = $couchPwd
+    bind_address = '0.0.0.0'
+    port = 5984
+    singlenode = $true
+} | ConvertTo-Json -Compress
+
+iwr -UseBasicParsing -Method 'POST' -ContentType 'application/json; charset=utf-8' -Headers @{ 'Authorization' = 'Basic ' + $creds } "${couchHost}/_cluster_setup" -Body $clusterSetupJSON
 ```
 
 Note: if the response code is not 200. We have to retry the request once again.
@@ -249,6 +270,8 @@ Please refer to [Configure CouchDB manually on the first device](./quick_setup.m
 
 ## Delete the Instance
 
+Before deleting the instance, preserve the data you still need and follow [Recovery and flag files](recovery.md#first-choose-the-authoritative-copy).
+
 If you want to delete the CouchDB instance, you can do that in [fly.io Dashboard](https://fly.io/dashboard/personal)
 
 If you have done with [B. Scripted Setup](#b-scripted-setup), we can use [delete-server.sh](../utils/readme.md#flyio-deployment).
diff --git a/docs/tips/status-display.md b/docs/tips/status-display.md
index 751d143e..d2cdf824 100644
--- a/docs/tips/status-display.md
+++ b/docs/tips/status-display.md
@@ -9,6 +9,7 @@ Use [General Settings](../settings.md#2-general-settings) to choose whether sync
     -   🌐N Approximate remote requests currently in progress
 -   Status
     -   ⏹️ Stopped
+    -   🌀 Starting synchronisation
     -   ⏩ Comparing CouchDB change history, including entries already held locally
     -   💤 LiveSync enabled. Waiting for changes
     -   ⚡️ Synchronisation in progress

From 22d10777fc71a94ade221a4aa061594a521ac745 Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Wed, 28 Oct 2026 05:57:40 +0000
Subject: [PATCH 10/18] Align Customisation Sync maturity with the supported
 feature policy

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 55146577..c75dd253 100644
--- a/README.md
+++ b/README.md
@@ -19,7 +19,7 @@ Find setup guides, troubleshooting, technical references, design decisions, and
 - Use open-source solutions for the server.
   - Compatible solutions are supported.
 - Support end-to-end encryption.
-- Synchronise settings, snippets, themes, and plug-ins via [Customisation Sync (Beta)](docs/settings.md#6-customisation-sync-advanced) or [Hidden File Sync](docs/tips/hidden-file-sync.md).
+- Synchronise settings, snippets, themes, and plug-ins via [Customisation Sync (Advanced)](docs/settings.md#6-customisation-sync-advanced) or [Hidden File Sync](docs/tips/hidden-file-sync.md).
 - Enable supported, opt-in WebRTC peer-to-peer synchronisation.
   - No central data-storage server is required, but a signalling relay is still required for peer discovery.
   - At least one device containing the required data must be online while another device synchronises.

From fac53afe84153a0dc12cc0e9073620fc52543ffe Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Wed, 28 Oct 2026 07:41:49 +0000
Subject: [PATCH 11/18] Restore self-hosting as the primary setup path

---
 README.md                | 10 +++++++---
 docs/README.md           |  5 +++--
 docs/setup_flyio.md      |  2 ++
 docs/setup_own_server.md | 18 ++++++++++++------
 4 files changed, 24 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md
index c75dd253..1fd6eef7 100644
--- a/README.md
+++ b/README.md
@@ -37,11 +37,13 @@ This plug-in may be particularly useful for researchers, engineers, and develope
 
 ### Setup workflows
 
+Self-hosting lets us choose a server we trust and manage it ourselves. For CouchDB, please set up and maintain your own instance. CouchDB can run on a Raspberry Pi, another server you operate, or infrastructure such as Fly.io. Please keep your server secure.
+
 Choose a synchronisation method, prepare its server where required, then follow the corresponding client setup:
 
 | Method | What you need | Nice to have | Setup guides |
 | --- | --- | --- | --- |
-| CouchDB | A CouchDB server you operate or trust. | — | [Own server](docs/setup_own_server.md), [Docker stack](docker/README.md), [Fly.io](docs/setup_flyio.md), or [IBM Cloudant](docs/setup_cloudant.md); then [Quick Setup](docs/quick_setup.md). |
+| CouchDB | A CouchDB server. | — | [Set up your own server](docs/setup_own_server.md), [Docker stack](docker/README.md), or [Fly.io](docs/setup_flyio.md); then [Quick Setup](docs/quick_setup.md). |
 | Object Storage | An S3-compatible service or server. | — | [Object Storage Setup](docs/setup_object_storage.md). |
 | Peer-to-Peer | Nothing. | Your own signalling server. | [P2P communication model](docs/p2p.md), then [Peer-to-Peer Setup](docs/setup_p2p.md). |
 
@@ -56,14 +58,16 @@ For the Fly.io video walkthrough, see [automated setup](docs/setup_flyio.md#a-ve
 ### Third-party managed CouchDB hosting
 
 > [!NOTE]
-> The services below are operated by third parties. They are not official Self-hosted LiveSync services, and this project neither endorses nor recommends them.
+> The services below are operated by third parties. They are not official Self-hosted LiveSync services, and this project neither endorses nor recommends them. The providers proposed the listings in the table.
 
-If you prefer a hosted CouchDB server, the following providers offer options for this plug-in:
+If you would rather not set up and maintain a server yourself, the following providers offer managed CouchDB servers which this plug-in can be configured to connect to:
 
 | Provider | Offering |
 | --- | --- |
 | [Zenith Hosting](https://zenith.hosting/host/obsidian-livesync) | Managed CouchDB hosting. |
 
+[IBM Cloudant](docs/setup_cloudant.md) is another managed alternative, with some limitations.
+
 Your synchronisation data will reside on a server operated by the provider. Consider whether that is acceptable for your Vault, and review the provider's current terms, pricing, and data-handling policies before using the service.
 
 ## Information in the Status Bar
diff --git a/docs/README.md b/docs/README.md
index 9c5499f9..a43a43ea 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -9,8 +9,9 @@ A document's original date and reviewed-version fields describe its baseline. Re
 | Task | Start here |
 |---|---|
 | Choose a synchronisation method | [Project overview and setup workflows](../README.md#setup-workflows) |
-| Set up CouchDB clients | [CouchDB server setup](setup_own_server.md), then [Quick setup](quick_setup.md) |
-| Choose a CouchDB hosting option | [Docker stack](../docker/README.md), [Fly.io](setup_flyio.md), or [IBM Cloudant](setup_cloudant.md) |
+| Run your own CouchDB server | [Own server](setup_own_server.md), [Docker stack](../docker/README.md), or [Fly.io](setup_flyio.md) |
+| Configure CouchDB clients | [Quick setup](quick_setup.md) |
+| Consider third-party managed services | [Alternatives to maintaining your own server](../README.md#third-party-managed-couchdb-hosting) |
 | Set up S3-compatible storage | [Object Storage Setup](setup_object_storage.md) |
 | Set up peer-to-peer synchronisation | [P2P communication model](p2p.md), then [Peer-to-Peer Setup](setup_p2p.md) |
 | Diagnose P2P connectivity | [Browser-assisted check](../src/apps/webpeer/README.md#p2p-connection-check), [network tips](tips/p2p-sync-tips.md), and [self-hosted TURN](../docker/coturn/README.md) |
diff --git a/docs/setup_flyio.md b/docs/setup_flyio.md
index fcc3c1ee..475e7e54 100644
--- a/docs/setup_flyio.md
+++ b/docs/setup_flyio.md
@@ -3,6 +3,8 @@
 
 This is how to configure fly.io and CouchDB on it for Self-hosted LiveSync.
 
+The CouchDB instance is yours to manage. You can configure it yourself or set up another instance and switch to it, following the preservation and recovery guidance below.
+
 > [!WARNING]
 > Before replacing or deleting an existing CouchDB instance, back up every available Vault and the remote database, then [choose the authoritative copy](recovery.md#first-choose-the-authoritative-copy). Stop or suspend synchronisation on other devices while reviewing recovery options. Local files alone do not establish that every needed edit or revision has been preserved.
 
diff --git a/docs/setup_own_server.md b/docs/setup_own_server.md
index cc1994e1..4f59c95b 100644
--- a/docs/setup_own_server.md
+++ b/docs/setup_own_server.md
@@ -15,7 +15,7 @@
       - [4. Starting Docker Compose in background](#4-run-the-docker-compose-file-in-the-background)
     - [C. Install CouchDB directly](#c-install-couchdb-directly)
   - [2. Run couchdb-init.sh for initialise](#2-run-couchdb-initsh-for-initialise)
-  - [3. Expose CouchDB to the Internet](#3-expose-couchdb-to-the-internet)
+  - [3. Make CouchDB reachable from your devices](#3-make-couchdb-reachable-from-your-devices)
   - [4. Client Setup](#4-client-setup)
     - [1. Generate the setup URI on a desktop device or server](#1-generate-the-setup-uri-on-a-desktop-device-or-server)
     - [2. Setup Self-hosted LiveSync to Obsidian](#2-setup-self-hosted-livesync-to-obsidian)
@@ -143,12 +143,16 @@ If you are using Docker Compose and the above command does not work or displays
 curl -s https://raw.githubusercontent.com/vrtmrz/obsidian-livesync/main/utils/couchdb/couchdb-init.sh | hostname='http://<YOUR SERVER IP>:5984' username='<INSERT COUCHDB ADMINISTRATOR USERNAME HERE>' password='<INSERT COUCHDB ADMINISTRATOR PASSWORD HERE>' database=obsidiannotes bash
 ```
 
-## 3. Expose CouchDB to the Internet
+<a id="3-expose-couchdb-to-the-internet"></a>
 
-- You can skip this instruction if you using only in intranet and only with desktop devices.
-  - For mobile devices, Obsidian requires a valid SSL certificate. Usually, it needs exposing the internet.
+## 3. Make CouchDB reachable from your devices
 
-For temporary testing, create a Cloudflare Quick Tunnel by following the [Quick Tunnels instructions](https://developers.cloudflare.com/tunnel/get-started/quick-tunnels/). It prints a random hostname which changes each time you create a tunnel, and the URL stops working when the `cloudflared` process stops. Quick Tunnels are intended for testing and development, not production. See the [Cloudflare Tunnel guide](https://developers.cloudflare.com/tunnel/get-started/) for durable use.
+- You can skip this step if you use CouchDB only on a trusted local network with desktop devices.
+  - For mobile devices, Obsidian requires HTTPS with a valid certificate. HTTPS does not require making CouchDB publicly accessible.
+
+Choose how your devices reach your CouchDB server. You can use a [reverse proxy you operate](#reverse-proxies), private-network access, or a tunnel service of your choice. The [Docker profiles](../docker/README.md#profile-details) provide examples.
+
+Cloudflare is one optional choice. The following example uses a [Quick Tunnel](https://developers.cloudflare.com/tunnel/get-started/quick-tunnels/) for temporary testing. It prints a random hostname which changes each time you create a tunnel, and the URL stops working when the `cloudflared` process stops. Quick Tunnels are intended for testing and development, not production. For ongoing use, configure your chosen connection method; the [Cloudflare Tunnel guide](https://developers.cloudflare.com/tunnel/get-started/) applies if you choose that provider.
 
 ```
 cloudflared tunnel --url http://localhost:5984
@@ -178,8 +182,10 @@ Use the URL printed by your tunnel as the server address. Keep the tunnel proces
 
 The `LIVESYNC_USER` and `LIVESYNC_PASS` here are the credentials which Self-hosted LiveSync will store for routine access to this database. They may be the administrator credentials from step 2. If you have separately configured a CouchDB account with the required access to this database, use that account instead. Neither the provisioning wrapper nor the Setup URI generator creates that separate account.
 
+Use the server URL through which your devices reach CouchDB. For the temporary Quick Tunnel example above, use the URL printed by your own running tunnel.
+
 ```bash
-export LIVESYNC_HOST='<YOUR QUICK-TUNNEL URL>'
+export LIVESYNC_HOST='<YOUR COUCHDB SERVER URL>'
 export LIVESYNC_DB=obsidiannotes
 export LIVESYNC_USER='<INSERT COUCHDB USERNAME FOR LIVESYNC>'
 export LIVESYNC_PASS='<INSERT THE COUCHDB PASSWORD>'

From d15ad5c28705614407fb8ad802aa6fa7e194130e Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Wed, 28 Oct 2026 08:23:10 +0000
Subject: [PATCH 12/18] Clarify CouchDB setup options and community hosting
 listings

---
 README.md      | 10 ++++++----
 docs/README.md |  4 ++--
 2 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index 1fd6eef7..36f53ee3 100644
--- a/README.md
+++ b/README.md
@@ -43,10 +43,12 @@ Choose a synchronisation method, prepare its server where required, then follow
 
 | Method | What you need | Nice to have | Setup guides |
 | --- | --- | --- | --- |
-| CouchDB | A CouchDB server. | — | [Set up your own server](docs/setup_own_server.md), [Docker stack](docker/README.md), or [Fly.io](docs/setup_flyio.md); then [Quick Setup](docs/quick_setup.md). |
+| CouchDB | A CouchDB server. | — | [Set up your own server](docs/setup_own_server.md), [Docker stack](docker/README.md), [Fly.io](docs/setup_flyio.md), or [IBM Cloudant (managed)](docs/setup_cloudant.md); then [Quick Setup](docs/quick_setup.md). |
 | Object Storage | An S3-compatible service or server. | — | [Object Storage Setup](docs/setup_object_storage.md). |
 | Peer-to-Peer | Nothing. | Your own signalling server. | [P2P communication model](docs/p2p.md), then [Peer-to-Peer Setup](docs/setup_p2p.md). |
 
+With your own server, you manage both the host and CouchDB; Docker is one way to deploy it. On Fly.io, you manage your CouchDB instance on hosted infrastructure. IBM Cloudant manages the database service.
+
 P2P can use the project's public signalling relay, so there is no server to provision. An optional self-hosted signalling server must be Nostr-compatible. A maintained MinIO server installation guide is not currently available here, so Object Storage users need to prepare their chosen S3-compatible service or server separately.
 
 Each workflow establishes ordinary note synchronisation on the first device, generates a Setup URI for each additional device from that working device, and verifies synchronisation in both directions. The linked hosting guides explain provider-specific setup and costs.
@@ -55,7 +57,9 @@ Each workflow establishes ordinary note synchronisation on the first device, gen
 
 For the Fly.io video walkthrough, see [automated setup](docs/setup_flyio.md#a-very-automated-setup).
 
-### Third-party managed CouchDB hosting
+<a id="third-party-managed-couchdb-hosting"></a>
+
+### Hosting services proposed by the community
 
 > [!NOTE]
 > The services below are operated by third parties. They are not official Self-hosted LiveSync services, and this project neither endorses nor recommends them. The providers proposed the listings in the table.
@@ -66,8 +70,6 @@ If you would rather not set up and maintain a server yourself, the following pro
 | --- | --- |
 | [Zenith Hosting](https://zenith.hosting/host/obsidian-livesync) | Managed CouchDB hosting. |
 
-[IBM Cloudant](docs/setup_cloudant.md) is another managed alternative, with some limitations.
-
 Your synchronisation data will reside on a server operated by the provider. Consider whether that is acceptable for your Vault, and review the provider's current terms, pricing, and data-handling policies before using the service.
 
 ## Information in the Status Bar
diff --git a/docs/README.md b/docs/README.md
index a43a43ea..95ad98d4 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -9,9 +9,9 @@ A document's original date and reviewed-version fields describe its baseline. Re
 | Task | Start here |
 |---|---|
 | Choose a synchronisation method | [Project overview and setup workflows](../README.md#setup-workflows) |
-| Run your own CouchDB server | [Own server](setup_own_server.md), [Docker stack](../docker/README.md), or [Fly.io](setup_flyio.md) |
+| Choose a CouchDB setup | [Own server](setup_own_server.md), [Docker stack](../docker/README.md), [Fly.io](setup_flyio.md), or [IBM Cloudant (managed)](setup_cloudant.md) |
 | Configure CouchDB clients | [Quick setup](quick_setup.md) |
-| Consider third-party managed services | [Alternatives to maintaining your own server](../README.md#third-party-managed-couchdb-hosting) |
+| Find hosting services proposed by the community | [Third-party hosting listings](../README.md#hosting-services-proposed-by-the-community) |
 | Set up S3-compatible storage | [Object Storage Setup](setup_object_storage.md) |
 | Set up peer-to-peer synchronisation | [P2P communication model](p2p.md), then [Peer-to-Peer Setup](setup_p2p.md) |
 | Diagnose P2P connectivity | [Browser-assisted check](../src/apps/webpeer/README.md#p2p-connection-check), [network tips](tips/p2p-sync-tips.md), and [self-hosted TURN](../docker/coturn/README.md) |

From f72f1011f2c321978a7af8f56f4264e5bbf9f3b4 Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Wed, 28 Oct 2026 08:50:29 +0000
Subject: [PATCH 13/18] Clarify requirements and first steps in the README

---
 README.md      | 33 ++++++++++++++++++++++-----------
 docs/README.md |  2 +-
 2 files changed, 23 insertions(+), 12 deletions(-)

diff --git a/README.md b/README.md
index 36f53ee3..2ed9b552 100644
--- a/README.md
+++ b/README.md
@@ -35,28 +35,39 @@ This plug-in may be particularly useful for researchers, engineers, and develope
 
 ## How to Use
 
-### Setup workflows
+Self-hosting lets us choose a server we trust and manage it ourselves. Please set up and maintain your own server, and keep it secure.
 
-Self-hosting lets us choose a server we trust and manage it ourselves. For CouchDB, please set up and maintain your own instance. CouchDB can run on a Raspberry Pi, another server you operate, or infrastructure such as Fly.io. Please keep your server secure.
+<a id="setup-workflows"></a>
 
-Choose a synchronisation method, prepare its server where required, then follow the corresponding client setup:
+### What you need
 
-| Method | What you need | Nice to have | Setup guides |
-| --- | --- | --- | --- |
-| CouchDB | A CouchDB server. | — | [Set up your own server](docs/setup_own_server.md), [Docker stack](docker/README.md), [Fly.io](docs/setup_flyio.md), or [IBM Cloudant (managed)](docs/setup_cloudant.md); then [Quick Setup](docs/quick_setup.md). |
-| Object Storage | An S3-compatible service or server. | — | [Object Storage Setup](docs/setup_object_storage.md). |
-| Peer-to-Peer | Nothing. | Your own signalling server. | [P2P communication model](docs/p2p.md), then [Peer-to-Peer Setup](docs/setup_p2p.md). |
+| Method | What you need | Nice to have |
+| --- | --- | --- |
+| CouchDB | A CouchDB-compatible server. | — |
+| Object Storage | An S3-compatible service or server. | — |
+| Peer-to-Peer | Nothing. | Your own signalling server. |
 
-With your own server, you manage both the host and CouchDB; Docker is one way to deploy it. On Fly.io, you manage your CouchDB instance on hosted infrastructure. IBM Cloudant manages the database service.
+For a CouchDB-compatible server, choose a setup guide for your environment:
 
-P2P can use the project's public signalling relay, so there is no server to provision. An optional self-hosted signalling server must be Nostr-compatible. A maintained MinIO server installation guide is not currently available here, so Object Storage users need to prepare their chosen S3-compatible service or server separately.
+- [Your own server](docs/setup_own_server.md): run CouchDB on a Raspberry Pi or another server you manage.
+- [Docker](docker/README.md): deploy CouchDB with the supplied Docker stack.
+- [Fly.io](docs/setup_flyio.md): manage your own CouchDB instance on hosted infrastructure.
+- [IBM Cloudant (managed)](docs/setup_cloudant.md): use a database service managed by IBM.
 
-Each workflow establishes ordinary note synchronisation on the first device, generates a Setup URI for each additional device from that working device, and verifies synchronisation in both directions. The linked hosting guides explain provider-specific setup and costs.
+The linked guides explain the setup and any provider-specific costs.
 
 <a id="3-minute-setup---couchdb-on-flyio"></a>
 
 For the Fly.io video walkthrough, see [automated setup](docs/setup_flyio.md#a-very-automated-setup).
 
+P2P can use the project's public signalling relay, so there is no server to provision. See [How peer-to-peer synchronisation works](docs/p2p.md) for more about the connection.
+
+### Start synchronising
+
+1. Install and configure Self-hosted LiveSync on your first device using [Quick Setup](docs/quick_setup.md) for CouchDB, [Object Storage Setup](docs/setup_object_storage.md), or [Peer-to-Peer Setup](docs/setup_p2p.md).
+2. Generate a Setup URI from that working device and follow the same guide to add your other devices.
+3. Create test notes and confirm that they synchronise in both directions.
+
 <a id="third-party-managed-couchdb-hosting"></a>
 
 ### Hosting services proposed by the community
diff --git a/docs/README.md b/docs/README.md
index 95ad98d4..2938d7c1 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -8,7 +8,7 @@ A document's original date and reviewed-version fields describe its baseline. Re
 
 | Task | Start here |
 |---|---|
-| Choose a synchronisation method | [Project overview and setup workflows](../README.md#setup-workflows) |
+| Get started | [What you need](../README.md#what-you-need), then [Start synchronising](../README.md#start-synchronising) |
 | Choose a CouchDB setup | [Own server](setup_own_server.md), [Docker stack](../docker/README.md), [Fly.io](setup_flyio.md), or [IBM Cloudant (managed)](setup_cloudant.md) |
 | Configure CouchDB clients | [Quick setup](quick_setup.md) |
 | Find hosting services proposed by the community | [Third-party hosting listings](../README.md#hosting-services-proposed-by-the-community) |

From 6a97ba689170749f4a3819a27ae8d3e87ad4934f Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Wed, 28 Oct 2026 09:27:45 +0000
Subject: [PATCH 14/18] Restore practical Docker setup and recovery guidance

---
 docker/README.md | 83 +++++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 78 insertions(+), 5 deletions(-)

diff --git a/docker/README.md b/docker/README.md
index 0eb33e55..50e4b4c6 100644
--- a/docker/README.md
+++ b/docker/README.md
@@ -122,10 +122,14 @@ TS_AUTHKEY=tskey-auth-...
 TS_HOSTNAME=livesync
 ```
 
-Choose the exposure before starting the profile. The bundled `config/ts-serve.json` sets `AllowFunnel` to `true`, requesting public HTTPS when the tailnet permits Funnel. It is not a private-only default.
+**Two sub-modes**:
 
-- For private tailnet access, set that entry to `false` and verify the effective Serve configuration.
-- For public Funnel access, retain `true` and configure the required tailnet permissions. See the [Tailscale Docker guide](https://tailscale.com/blog/docker-tailscale-guide) for the distinction between Serve and Funnel.
+- **Private tailnet access (VPN / Serve)**: choose this for access from your own devices on your tailnet, subject to its access rules. Set `AllowFunnel` to `false` in `config/ts-serve.json`, and use the Tailscale app on those devices.
+- **Public HTTPS (Funnel)**: choose this when devices need to connect over the Internet without joining your tailnet. Keep `AllowFunnel` set to `true`, and allow Funnel for this server in your tailnet's access controls.
+
+Both modes use a Tailscale HTTPS name, such as `https://livesync.<tailnet>.ts.net`, so you do not need to buy a domain. Use the actual DNS name assigned to your server in Tailscale. See the [Tailscale Docker guide](https://tailscale.com/blog/docker-tailscale-guide) for HTTPS and Funnel prerequisites.
+
+Choose the mode before starting the profile. The bundled `config/ts-serve.json` sets `AllowFunnel` to `true`, requesting public HTTPS when the tailnet permits Funnel; change that entry to `false` to keep the Tailscale endpoint private. After starting or restarting the Tailscale service, check the effective configuration with `docker exec livesync-tailscale tailscale serve status`. The separate host HTTP port described above is unaffected by this choice.
 
 The bundled service expects `/dev/net/tun`. On hosts without that device, follow Tailscale's userspace-networking instructions and adjust the device mount as well as `TS_USERSPACE`; changing the environment variable alone leaves the required bind mount in place.
 
@@ -137,7 +141,11 @@ The bundled service expects `/dev/net/tun`. On hosts without that device, follow
 
 #### Step 1: Create a Cloudflare Tunnel
 
-Create a remotely managed tunnel using the current [Cloudflare Tunnel setup instructions](https://developers.cloudflare.com/tunnel/get-started/). Copy its connector token into `CF_TUNNEL_TOKEN` below. This Compose profile runs the connector; a separate host installation of `cloudflared` is unnecessary for this profile.
+1. Open the [Cloudflare dashboard](https://dash.cloudflare.com/) and go to **Networking → Tunnels**.
+2. Select **Create Tunnel**, give it a name such as `obsidian-livesync`, and create it.
+3. On the connector setup screen, copy the installation command into a text editor without running it. Extract only the tunnel token, the string beginning with `eyJ`, and put it in `CF_TUNNEL_TOKEN` in the next step. Keep the token private.
+
+For an existing tunnel, select it and use **Add a replica** to display the installation command again. This Compose profile starts the connector in step 4. Until then, the dashboard can show the tunnel as disconnected. See the official [tunnel setup](https://developers.cloudflare.com/tunnel/get-started/) and [token instructions](https://developers.cloudflare.com/tunnel/reference/tunnel-tokens/) for the current screens.
 
 #### Step 2: Configure Environment
 
@@ -268,7 +276,72 @@ docker run --rm --network none -v obsidian-livesync_couchdb-data:/data:ro \
 docker compose start couchdb
 ```
 
-Before restoration, preserve the existing database volume. Restore and verify the archive in a separate recovery volume with a compatible CouchDB installation before replacing the active data. Do not extract an archive over a running database. See [Backing up CouchDB](https://docs.couchdb.org/en/stable/maintenance/backups.html) for database, configuration, and replication-based backup options.
+### Restore a backup
+
+Restore into a new volume so that the current database remains available. The following Bash commands run from the `docker/` directory. Use a trusted archive from the backup above, and the same CouchDB image version used to create it. Keep the saved CouchDB configuration available too. Run each block only after the previous step succeeds.
+
+First, choose the archive and create a new recovery volume. Docker generates an unused volume name:
+
+```bash
+backupArchive='<BACKUP ARCHIVE FILENAME>'
+recoveryImage='<COUCHDB IMAGE TAG OR DIGEST FROM THE BACKUP>'
+recoveryVolume=$(docker volume create) &&
+docker run --rm --network none \
+  --mount "type=volume,src=$recoveryVolume,dst=/data" \
+  --mount "type=bind,src=$(pwd)/backup,dst=/backup,readonly" \
+  alpine:3.22 tar xzf "/backup/$backupArchive" -C /data
+```
+
+If extraction fails, stop here. The new recovery volume may be empty or incomplete; remove it with `docker volume rm "$recoveryVolume"` before retrying. The original database volume is unaffected.
+
+Start a temporary CouchDB with the restored data. It has no external network connection or published ports, so synchronising clients cannot reach it:
+
+```bash
+recoveryUser='<COUCHDB USERNAME>'
+recoveryPassword='<COUCHDB PASSWORD>'
+recoveryContainer=$(docker run -d --network none \
+  -e COUCHDB_USER="$recoveryUser" \
+  -e COUCHDB_PASSWORD="$recoveryPassword" \
+  --mount "type=volume,src=$recoveryVolume,dst=/opt/couchdb/data" \
+  "$recoveryImage")
+```
+
+Wait for CouchDB to start, then inspect its health, database list, and your restored database. Replace the database name with the one you backed up:
+
+```bash
+recoveryDatabase='<DATABASE NAME>'
+docker exec "$recoveryContainer" curl -fsS \
+  -u "$recoveryUser:$recoveryPassword" http://127.0.0.1:5984/_up
+docker exec "$recoveryContainer" curl -fsS \
+  -u "$recoveryUser:$recoveryPassword" http://127.0.0.1:5984/_all_dbs
+docker exec "$recoveryContainer" curl -fsS \
+  -u "$recoveryUser:$recoveryPassword" "http://127.0.0.1:5984/$recoveryDatabase"
+docker exec "$recoveryContainer" curl -fsS \
+  -u "$recoveryUser:$recoveryPassword" \
+  "http://127.0.0.1:5984/$recoveryDatabase/_all_docs?limit=5"
+```
+
+Compare the database names, document counts, and expected document IDs with your backup. These checks establish that CouchDB can read the restored files; they do not establish that every required note is present. If a check fails, inspect `docker logs "$recoveryContainer"` and keep the original volume in place.
+
+Once you have verified the restored database, stop and remove only the temporary container, and note the recovery volume name:
+
+```bash
+docker stop "$recoveryContainer" && docker rm "$recoveryContainer"
+docker volume inspect "$recoveryVolume" --format '{{.Name}}'
+```
+
+To use the restored copy, first [choose the authoritative copy](../docs/recovery.md#first-choose-the-authoritative-copy) and suspend synchronisation on your devices. Stop the stack with `docker compose down`, using the same profile options as usual and without `-v`. Save a copy of `docker-compose.yml`, then replace only its `couchdb-data` volume declaration with the following, using the printed recovery volume name. Keep the other volume declarations:
+
+```yaml
+volumes:
+  couchdb-data:
+    external: true
+    name: <RECOVERY VOLUME NAME>
+```
+
+Use the same CouchDB image version in the `couchdb` service, restore any saved configuration changes, and start the stack with your usual `docker compose up -d` profile command. The original volume and archive remain available. Verify the required notes from a separate test Vault. When the restored remote is your chosen source of truth, follow [Reset Synchronisation on This Device](../docs/recovery.md#reset-synchronisation-on-this-device) on your existing devices before resuming them, preserving any newer local work first.
+
+See [Backing up CouchDB](https://docs.couchdb.org/en/stable/maintenance/backups.html) for database, configuration, and replication-based backup options.
 
 ---
 

From d550e7a200100b24e22d0eb79d8e43ba2686bacd Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Wed, 28 Oct 2026 14:26:34 +0000
Subject: [PATCH 15/18] Move P2P setup details below the requirements table

---
 README.md | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index 2ed9b552..1b720a2c 100644
--- a/README.md
+++ b/README.md
@@ -20,11 +20,7 @@ Find setup guides, troubleshooting, technical references, design decisions, and
   - Compatible solutions are supported.
 - Support end-to-end encryption.
 - Synchronise settings, snippets, themes, and plug-ins via [Customisation Sync (Advanced)](docs/settings.md#6-customisation-sync-advanced) or [Hidden File Sync](docs/tips/hidden-file-sync.md).
-- Enable supported, opt-in WebRTC peer-to-peer synchronisation.
-  - No central data-storage server is required, but a signalling relay is still required for peer discovery.
-  - At least one device containing the required data must be online while another device synchronises.
-  - Follow the [Peer-to-Peer Setup](docs/setup_p2p.md) after reviewing the [P2P communication model](docs/p2p.md).
-  - If you would like to see how P2P setup and connectivity behave on your devices, try the guided connection check in the experimental [WebPeer browser utility](https://vrtmrz.github.io/obsidian-livesync/webpeer/). It uses an empty Vault and does not test note synchronisation. See the [WebPeer documentation](src/apps/webpeer/README.md) for its scope and limitations.
+- Synchronise peer-to-peer using WebRTC.
 
 This plug-in may be particularly useful for researchers, engineers, and developers who need to keep their notes fully self-hosted for security reasons. It is also suitable for anyone seeking the peace of mind that comes with knowing their notes remain entirely private.
 
@@ -60,7 +56,9 @@ The linked guides explain the setup and any provider-specific costs.
 
 For the Fly.io video walkthrough, see [automated setup](docs/setup_flyio.md#a-very-automated-setup).
 
-P2P can use the project's public signalling relay, so there is no server to provision. See [How peer-to-peer synchronisation works](docs/p2p.md) for more about the connection.
+P2P does not require a central data-storage server, but a signalling relay is still required for peer discovery. You can use the project's public signalling relay, so there is no server to provision. At least one device containing the required data must be online while another device synchronises. Follow the [Peer-to-Peer Setup](docs/setup_p2p.md) after reviewing the [P2P communication model](docs/p2p.md).
+
+If you would like to see how P2P setup and connectivity behave on your devices, try the guided connection check in the experimental [WebPeer browser utility](https://vrtmrz.github.io/obsidian-livesync/webpeer/). It uses an empty Vault and does not test note synchronisation. See the [WebPeer documentation](src/apps/webpeer/README.md) for its scope and limitations.
 
 ### Start synchronising
 

From b3d74aa06db1bfc2dbbeb37c1b9abc83187a6bdf Mon Sep 17 00:00:00 2001
From: ARCJ137442 <61109168+ARCJ137442@users.noreply.github.com>
Date: Thu, 29 Oct 2026 14:42:46 +0800
Subject: [PATCH 16/18] feat: show directional CouchDB comparison progress

---
 .../features/ReplicationStatusLabel.ts        | 120 +++++++++++-------
 .../ReplicationStatusLabel.unit.spec.ts       | 104 +++++++++++----
 2 files changed, 157 insertions(+), 67 deletions(-)

diff --git a/src/modules/features/ReplicationStatusLabel.ts b/src/modules/features/ReplicationStatusLabel.ts
index 8358127c..ef596b56 100644
--- a/src/modules/features/ReplicationStatusLabel.ts
+++ b/src/modules/features/ReplicationStatusLabel.ts
@@ -13,13 +13,25 @@ import {
 
 export const FAST_FORWARD_COUNT_LINGER_MS = 3_000;
 
-function readPositiveCheckedChanges(source: ReactiveValue<ReplicationStatics>): number | undefined {
-    const count = source.value.couchDB?.pull?.checkedChanges;
+export type FastForwardCheckedChanges = {
+    push?: number;
+    pull?: number;
+};
+
+function readPositiveCheckedChanges(
+    source: ReactiveValue<ReplicationStatics>,
+    direction: keyof FastForwardCheckedChanges
+): number | undefined {
+    const count = source.value.couchDB?.[direction]?.checkedChanges;
     return typeof count === "number" && Number.isFinite(count) && count > 0 ? count : undefined;
 }
 
+function copyCheckedChanges(counts: FastForwardCheckedChanges): FastForwardCheckedChanges {
+    return { ...counts };
+}
+
 /**
- * Briefly displays changing CouchDB pull-feed comparison counts.
+ * Briefly displays changing CouchDB push- and pull-feed comparison counts.
  *
  * Unrelated replication-stat changes do not extend the linger or redisplay an
  * expired count. A positive initial snapshot is displayed to late subscribers.
@@ -27,46 +39,61 @@ function readPositiveCheckedChanges(source: ReactiveValue<ReplicationStatics>):
 export function createFastForwardCheckedChangesDisplay(
     source: ReactiveValue<ReplicationStatics>,
     lingerMs = FAST_FORWARD_COUNT_LINGER_MS
-): DisposableReactiveValue<number | undefined> {
-    const displayed = reactiveSource<number | undefined>(undefined);
+): DisposableReactiveValue<FastForwardCheckedChanges> {
+    const displayed = reactiveSource<FastForwardCheckedChanges>({});
     const linger = Math.max(0, lingerMs);
-    let lastObserved = readPositiveCheckedChanges(source);
-    let clearTimer: number | undefined;
+    const directions: (keyof FastForwardCheckedChanges)[] = ["push", "pull"];
+    const lastObserved: FastForwardCheckedChanges = {};
+    const clearTimers = new Map<keyof FastForwardCheckedChanges, number>();
     let disposed = false;
 
-    const cancelClear = () => {
-        if (clearTimer === undefined) return;
-        compatGlobal.clearTimeout(clearTimer);
-        clearTimer = undefined;
+    const cancelClear = (direction: keyof FastForwardCheckedChanges) => {
+        const timer = clearTimers.get(direction);
+        if (timer === undefined) return;
+        compatGlobal.clearTimeout(timer);
+        clearTimers.delete(direction);
     };
-    const scheduleClear = () => {
-        clearTimer = compatGlobal.setTimeout(() => {
-            clearTimer = undefined;
+    const scheduleClear = (direction: keyof FastForwardCheckedChanges) => {
+        const timer = compatGlobal.setTimeout(() => {
+            clearTimers.delete(direction);
             if (disposed) return;
-            if (readPositiveCheckedChanges(source) !== lastObserved) {
+            if (readPositiveCheckedChanges(source, direction) !== lastObserved[direction]) {
                 update();
                 return;
             }
-            displayed.value = undefined;
+            const nextDisplayed = copyCheckedChanges(displayed.value);
+            delete nextDisplayed[direction];
+            displayed.value = nextDisplayed;
         }, linger);
+        clearTimers.set(direction, timer);
     };
     const update = () => {
         if (disposed) return;
-        const nextCount = readPositiveCheckedChanges(source);
-        if (nextCount === lastObserved) return;
-        lastObserved = nextCount;
-        cancelClear();
-        if (nextCount === undefined) {
-            displayed.value = undefined;
-            return;
+        const nextDisplayed = copyCheckedChanges(displayed.value);
+        let changed = false;
+        for (const direction of directions) {
+            const nextCount = readPositiveCheckedChanges(source, direction);
+            if (nextCount === lastObserved[direction]) continue;
+            lastObserved[direction] = nextCount;
+            cancelClear(direction);
+            if (nextCount === undefined) {
+                delete nextDisplayed[direction];
+                changed = true;
+                continue;
+            }
+            nextDisplayed[direction] = nextCount;
+            scheduleClear(direction);
+            changed = true;
         }
-        displayed.value = nextCount;
-        scheduleClear();
+        if (changed) displayed.value = nextDisplayed;
     };
 
-    if (lastObserved !== undefined) {
-        displayed.value = lastObserved;
-        scheduleClear();
+    for (const direction of directions) {
+        const count = readPositiveCheckedChanges(source, direction);
+        if (count === undefined) continue;
+        lastObserved[direction] = count;
+        displayed.value = { ...displayed.value, [direction]: count };
+        scheduleClear(direction);
     }
     source.onChanged(update);
 
@@ -83,7 +110,7 @@ export function createFastForwardCheckedChangesDisplay(
         dispose() {
             if (disposed) return;
             disposed = true;
-            cancelClear();
+            for (const direction of directions) cancelClear(direction);
             source.offChanged(update);
         },
     };
@@ -113,7 +140,7 @@ function remainingSequenceLabel(
 export function projectReplicationStatusLabel(
     stats: ReplicationStatics,
     networkStatus: RemoteActivityStatus,
-    fastForwardCount?: number
+    fastForwardCounts?: FastForwardCheckedChanges
 ): ReplicationStatusProjection {
     const { sent, arrived, maxPullSeq, maxPushSeq, lastSyncPullSeq, lastSyncPushSeq } = stats;
     const networkActivity = formatRemoteActivityStatusLabel(networkStatus);
@@ -154,14 +181,19 @@ export function projectReplicationStatusLabel(
         (couchDB.pull?.checking === true || couchDB.push?.checking === true);
     if (isFastForwardChecking) icon = "⏩";
 
-    const visibleFastForwardCount =
-        couchDB !== undefined &&
-        typeof fastForwardCount === "number" &&
-        Number.isFinite(fastForwardCount) &&
-        fastForwardCount > 0
-            ? fastForwardCount
-            : undefined;
-    const fastForwardLabel = visibleFastForwardCount === undefined ? "" : " (⏩ " + visibleFastForwardCount + ")";
+    const visibleFastForwardCounts: FastForwardCheckedChanges = {};
+    if (couchDB !== undefined) {
+        for (const direction of ["push", "pull"] as const) {
+            const count = fastForwardCounts?.[direction];
+            if (typeof count === "number" && Number.isFinite(count) && count > 0) {
+                visibleFastForwardCounts[direction] = count;
+            }
+        }
+    }
+    const fastForwardLabels = (["push", "pull"] as const)
+        .filter((direction) => visibleFastForwardCounts[direction] !== undefined)
+        .map((direction) => ` (⏩${direction === "push" ? "↑" : "↓"} ${visibleFastForwardCounts[direction]})`);
+    const fastForwardLabel = fastForwardLabels.join("");
 
     const parts: StatusBarPart[] = [];
     if (networkStatus.trackedRequestCount > 0) {
@@ -177,13 +209,15 @@ export function projectReplicationStatusLabel(
         parts.push({ key: "network", text: networkActivity });
     }
     parts.push({ key: "sync", text: "Sync: " + icon });
-    if (visibleFastForwardCount !== undefined) {
+    for (const direction of ["push", "pull"] as const) {
+        const count = visibleFastForwardCounts[direction];
+        if (count === undefined) continue;
         parts.push({
-            key: "ff",
-            text: " (⏩ ",
-            value: visibleFastForwardCount,
+            key: `ff-${direction}`,
+            text: ` (⏩${direction === "push" ? "↑" : "↓"} `,
+            value: count,
             suffix: ")",
-            title: "Compared CouchDB feed entries",
+            title: `Compared CouchDB ${direction} feed entries`,
         });
     }
     parts.push({ key: "sent", text: " ↑ ", value: sent });
diff --git a/src/modules/features/ReplicationStatusLabel.unit.spec.ts b/src/modules/features/ReplicationStatusLabel.unit.spec.ts
index 054d597e..74b63196 100644
--- a/src/modules/features/ReplicationStatusLabel.unit.spec.ts
+++ b/src/modules/features/ReplicationStatusLabel.unit.spec.ts
@@ -90,18 +90,22 @@ describe("projectReplicationStatusLabel", () => {
             const idleWithCount = projectReplicationStatusLabel(
                 stats({ syncStatus, couchDB: couchDBProgress("idle", 19, true) }),
                 noNetworkActivity,
-                19
+                { push: 19, pull: 19 }
             );
             expect(idleWithCount.icon).toBe(icon);
-            expect(idleWithCount.parts.some((part) => part.key === "ff")).toBe(true);
+            expect(idleWithCount.parts.some((part) => part.key === "ff-push")).toBe(true);
+            expect(idleWithCount.parts.some((part) => part.key === "ff-pull")).toBe(true);
 
-            const withoutCouchDB = projectReplicationStatusLabel(stats({ syncStatus }), noNetworkActivity, 19);
+            const withoutCouchDB = projectReplicationStatusLabel(stats({ syncStatus }), noNetworkActivity, {
+                push: 19,
+                pull: 19,
+            });
             expect(withoutCouchDB.icon).toBe(icon);
-            expect(withoutCouchDB.parts.some((part) => part.key === "ff")).toBe(false);
+            expect(withoutCouchDB.parts.some((part) => part.key.startsWith("ff-"))).toBe(false);
         }
 
         const noFastForward = projectReplicationStatusLabel(stats(), noNetworkActivity);
-        expect(noFastForward.parts.some((part) => part.key === "ff")).toBe(false);
+        expect(noFastForward.parts.some((part) => part.key.startsWith("ff-"))).toBe(false);
         expect(noFastForward.message).toBe("Sync: ⚡ ↑ 0 ↓ 0");
     });
 
@@ -123,18 +127,40 @@ describe("projectReplicationStatusLabel", () => {
                 couchDB: couchDBProgress("continuous", 1200, false),
             }),
             noNetworkActivity,
-            1200
+            { pull: 1200 }
         );
         expect(transferred.icon).toBe("⚡");
-        expect(transferred.message).toBe("Sync: ⚡ (⏩ 1200) ↑ 0 ↓ 7");
-        expect(transferred.parts.map((part) => part.key)).toEqual(["sync", "ff", "sent", "arrived"]);
+        expect(transferred.message).toBe("Sync: ⚡ (⏩↓ 1200) ↑ 0 ↓ 7");
+        expect(transferred.parts.map((part) => part.key)).toEqual(["sync", "ff-pull", "sent", "arrived"]);
         expect(transferred.parts[1]).toMatchObject({
-            key: "ff",
-            text: " (⏩ ",
+            key: "ff-pull",
+            text: " (⏩↓ ",
             value: 1200,
             suffix: ")",
+            title: "Compared CouchDB pull feed entries",
         });
 
+        const pushChecking = projectReplicationStatusLabel(
+            stats({
+                couchDB: {
+                    phase: "continuous",
+                    push: { checkedChanges: 71975, completedBatches: 2878, checking: true },
+                },
+            }),
+            noNetworkActivity,
+            { push: 71975 }
+        );
+        expect(pushChecking.icon).toBe("⏩");
+        expect(pushChecking.message).toBe("Sync: ⏩ (⏩↑ 71975) ↑ 0 ↓ 0");
+        expect(pushChecking.parts[1]).toMatchObject({ key: "ff-push", value: 71975 });
+
+        const bothChecking = projectReplicationStatusLabel(
+            stats({ couchDB: couchDBProgress("continuous", 10, true) }),
+            noNetworkActivity,
+            { push: 71975, pull: 10 }
+        );
+        expect(bothChecking.message).toBe("Sync: ⏩ (⏩↑ 71975) (⏩↓ 10) ↑ 0 ↓ 0");
+
         const idle = projectReplicationStatusLabel(
             stats({
                 syncStatus: "CONNECTED",
@@ -142,10 +168,10 @@ describe("projectReplicationStatusLabel", () => {
                 couchDB: couchDBProgress("idle", 1200, false),
             }),
             noNetworkActivity,
-            1200
+            { pull: 1200 }
         );
         expect(idle.icon).toBe("⚡");
-        expect(idle.message).toBe("Sync: ⚡ (⏩ 1200) ↑ 0 ↓ 7");
+        expect(idle.message).toBe("Sync: ⚡ (⏩↓ 1200) ↑ 0 ↓ 7");
     });
 
     it("keeps the error icon ahead of an active CouchDB checking indicator", () => {
@@ -154,7 +180,7 @@ describe("projectReplicationStatusLabel", () => {
                 syncStatus: "ERRORED",
                 couchDB: {
                     ...couchDBProgress("one-shot", 2, true),
-                    push: { checkedChanges: 0, completedBatches: 0, checking: true },
+                    push: { checkedChanges: 2, completedBatches: 1, checking: true },
                 },
             }),
             noNetworkActivity
@@ -181,41 +207,41 @@ describe("createFastForwardCheckedChangesDisplay", () => {
         );
         const display = createFastForwardCheckedChangesDisplay(source);
 
-        expect(display.value).toBe(1200);
+        expect(display.value).toEqual({ pull: 1200 });
         vi.advanceTimersByTime(1000);
         source.value = stats({
             sent: 3,
             couchDB: couchDBProgress("idle", 1200, false),
         });
-        expect(display.value).toBe(1200);
+        expect(display.value).toEqual({ pull: 1200 });
         vi.advanceTimersByTime(FAST_FORWARD_COUNT_LINGER_MS - 1001);
-        expect(display.value).toBe(1200);
+        expect(display.value).toEqual({ pull: 1200 });
 
         source.value = stats({
             sent: 4,
             couchDB: couchDBProgress("idle", 1200, false),
         });
         vi.advanceTimersByTime(1);
-        expect(display.value).toBeUndefined();
+        expect(display.value).toEqual({});
 
         source.value = stats({
             syncStatus: "PAUSED",
             couchDB: couchDBProgress("continuous", 1200, true),
         });
-        expect(display.value).toBeUndefined();
+        expect(display.value).toEqual({});
 
         source.value = stats({
             couchDB: couchDBProgress("continuous", 1201, true),
         });
-        expect(display.value).toBe(1201);
+        expect(display.value).toEqual({ pull: 1201 });
 
         source.value = stats({
             couchDB: couchDBProgress("one-shot", 0, true),
         });
-        expect(display.value).toBeUndefined();
+        expect(display.value).toEqual({});
 
         source.value = stats();
-        expect(display.value).toBeUndefined();
+        expect(display.value).toEqual({});
         display.dispose();
     });
 
@@ -227,16 +253,46 @@ describe("createFastForwardCheckedChangesDisplay", () => {
         vi.advanceTimersByTime(FAST_FORWARD_COUNT_LINGER_MS);
         source.value = stats({ couchDB: couchDBProgress("continuous", 6, true) });
 
-        expect(display.value).toBe(5);
+        expect(display.value).toEqual({ pull: 5 });
     });
 
     it("does not display progress for providers without CouchDB replication state", () => {
         const source = reactiveSource(stats());
         const display = createFastForwardCheckedChangesDisplay(source);
 
-        expect(display.value).toBeUndefined();
+        expect(display.value).toEqual({});
         source.value = stats({ couchDB: { phase: "continuous" } });
-        expect(display.value).toBeUndefined();
+        expect(display.value).toEqual({});
+        display.dispose();
+    });
+
+    it("tracks push and pull independently and expires only the direction that stopped changing", () => {
+        const source = reactiveSource(
+            stats({
+                couchDB: {
+                    phase: "catch-up",
+                    pull: { checkedChanges: 4, completedBatches: 1, checking: true },
+                    push: { checkedChanges: 40, completedBatches: 2, checking: true },
+                },
+            })
+        );
+        const display = createFastForwardCheckedChangesDisplay(source, 100);
+
+        expect(display.value).toEqual({ push: 40, pull: 4 });
+        vi.advanceTimersByTime(50);
+        source.value = stats({
+            couchDB: {
+                phase: "catch-up",
+                pull: { checkedChanges: 4, completedBatches: 1, checking: true },
+                push: { checkedChanges: 41, completedBatches: 2, checking: true },
+            },
+        });
+        expect(display.value).toEqual({ push: 41, pull: 4 });
+
+        vi.advanceTimersByTime(50);
+        expect(display.value).toEqual({ push: 41 });
+        vi.advanceTimersByTime(50);
+        expect(display.value).toEqual({});
         display.dispose();
     });
 });

From a9434895fb535783f968309c855bf0516843e1cf Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Thu, 29 Oct 2026 11:18:21 +0000
Subject: [PATCH 17/18] docs: note expanded Simplified Chinese translations

---
 updates.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/updates.md b/updates.md
index 31d529ec..4fb738b6 100644
--- a/updates.md
+++ b/updates.md
@@ -12,6 +12,10 @@ Earlier releases remain available in the 1.0 release history, the 1.0 preview hi
 
 ## Unreleased
 
+### Translations
+
+- Simplified Chinese translations have been expanded across settings, setup, recovery, and configuration messages. (#1258) Thank you to @kannazuki-c for the contribution!
+
 ## 1.0.37
 
 16th October, 2026

From 2fb1c0352d2bf547ab6e337290ce80a07129efb4 Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Thu, 29 Oct 2026 12:22:44 +0000
Subject: [PATCH 18/18] fix: complete directional CouchDB status integration

Keep editor comparison counters compact with their directional CSS classes,
and document selector migration plus an optional CSS animation snippet.

Extend real Obsidian coverage for push comparison with zero transfers,
independent expiry, idle and error states, and the documented snippet.
Prepare the fixture editor before loading the plug-in so the UI scenario
owns its setup order.
---
 docs/tips/status-display.md                   |  51 +++-
 styles.css                                    |   3 +-
 test/e2e-obsidian/README.md                   |   6 +-
 .../scripts/replication-status.ts             | 271 ++++++++++++++++--
 updates.md                                    |   6 +
 5 files changed, 309 insertions(+), 28 deletions(-)

diff --git a/docs/tips/status-display.md b/docs/tips/status-display.md
index d2cdf824..cb6bc336 100644
--- a/docs/tips/status-display.md
+++ b/docs/tips/status-display.md
@@ -33,23 +33,66 @@ To prevent file and database corruption, please avoid closing Obsidian until all
 
 ## CouchDB comparison count
 
-When CouchDB change history is being compared, `(⏩ 1200) ↑ 0 ↓ 0` can appear before any new documents arrive. The count is the number of candidate changes-feed entries compared during the current replication attempt, including repeated entries on retries. It is separate from downloaded Chunks and Metadata, and is neither a Vault file count nor a count of entries already present locally. It appears before the upload count, disappears after three seconds without a change, and reappears when the count changes. The ⏩ status icon follows comparison activity independently of that timer.
+When CouchDB change history is being compared, directional counts can appear before any new documents arrive, for example `Sync: ⏩ (⏩↑ 1200) (⏩↓ 84) ↑ 0 ↓ 0`. The `⏩↑` count is for the push direction, and `⏩↓` is for the pull direction. Each counts candidate changes-feed entries compared during the current replication attempt, including entries which do not need to be transferred and repeated entries on retries. They are feed-entry counts, not counts of Vault files which need to be transferred. The final `↑` and `↓` counts continue to show uploaded and downloaded Chunks and Metadata.
+
+Each directional count has its own display timer. A positive count remains visible for three seconds after its last change, then clears; a count which reaches zero clears immediately. A change in one direction does not extend the other direction's timer. The ⏩ status icon follows comparison activity independently of these timers.
 
 ## Customising status items with CSS snippets
 
-The status bar and editor overlay use individual spans with the common `livesync-stat-` class prefix. CSS snippets can hide or style individual items. For example, this hides the comparison count and P2P summary:
+The status bar and editor overlay use individual spans with the common `livesync-stat-` class prefix. CSS snippets can hide or style individual items. For example, this hides both directional comparison counts and the P2P summary:
 
 ```css
-.livesync-stat-ff,
+.livesync-stat-ff-push,
+.livesync-stat-ff-pull,
 .livesync-stat-p2p {
     display: none;
 }
 ```
 
-The item classes include `livesync-stat-network`, `livesync-stat-sync`, `livesync-stat-sent`, `livesync-stat-push-remaining`, `livesync-stat-arrived`, `livesync-stat-pull-remaining`, `livesync-stat-ff`, and `livesync-stat-p2p`. File-processing items use `livesync-stat-file-processing`, `livesync-stat-file-pending`, and `livesync-stat-file-batched`; queue items use `livesync-stat-queue-` followed by `replication`, `database`, `storage`, `chunk-initial`, `chunk-retrying`, `plugin-scan`, `hidden-files`, or `conflicts`. The skipped-file indicator uses `livesync-stat-file-skip`.
+The item classes include `livesync-stat-network`, `livesync-stat-sync`, `livesync-stat-sent`, `livesync-stat-push-remaining`, `livesync-stat-arrived`, `livesync-stat-pull-remaining`, `livesync-stat-ff-push`, `livesync-stat-ff-pull`, and `livesync-stat-p2p`. File-processing items use `livesync-stat-file-processing`, `livesync-stat-file-pending`, and `livesync-stat-file-batched`; queue items use `livesync-stat-queue-` followed by `replication`, `database`, `storage`, `chunk-initial`, `chunk-retrying`, `plugin-scan`, `hidden-files`, or `conflicts`. The skipped-file indicator uses `livesync-stat-file-skip`.
+
+The former `livesync-stat-ff` class has been replaced by `livesync-stat-ff-push` and `livesync-stat-ff-pull`. Update existing CSS snippets to target one or both of the directional classes.
 
 All items also have `livesync-stat-item`. Numeric children use `livesync-stat-value`, tabular digits, and right alignment. Each numeric item retains its widest displayed digit count during an active period, reducing movement as counts decrease. The editor overlay uses wider gaps between items, while remaining counts stay beside their transfer totals.
 
 Inactive items receive `livesync-stat-inactive` instead of the HTML `hidden` attribute. The default CSS hides them immediately. They retain their last text, numeric width, and position amongst the other items so that CSS snippets can customise how they disappear. The numeric width starts afresh when an item becomes active again.
 
+### Animate editor status items
+
+This optional CSS snippet shrinks inactive items in the editor status line and expands them when they reappear. It applies to all status items in that line. Because inactive items remain in the DOM, their width can transition as their state changes; the initial creation of an item is not guaranteed to animate. Text changes, including on first appearance, do not necessarily animate an item's width. The `@supports` guard leaves the default, immediate hiding behaviour in place in CSS engines which do not support `calc-size()`.
+
+```css
+@supports (width: calc-size(auto, size)) {
+    .livesync-status-statusline > .livesync-stat-item {
+        font-variant-numeric: tabular-nums;
+        transition: width 0.125s;
+        display: inline-block;
+        width: calc-size(auto, size);
+        overflow: hidden;
+        white-space: nowrap;
+    }
+
+    .livesync-status-statusline > .livesync-stat-item.livesync-stat-inactive {
+        transition: width 0.46s;
+        display: inline-block;
+        width: calc-size(auto, size * 0);
+        overflow: hidden;
+        white-space: nowrap;
+        margin-inline-start: 0 !important;
+    }
+
+    @media (prefers-reduced-motion: reduce) {
+        .livesync-status-statusline > .livesync-stat-item {
+            transition: none;
+        }
+
+        .livesync-status-statusline > .livesync-stat-item.livesync-stat-inactive {
+            transition: none;
+        }
+    }
+}
+```
+
+The snippet affects the editor overlay only; the status bar keeps its default appearance. See the [`calc-size()` reference](https://developer.chrome.com/docs/css-ui/animate-to-height-auto/) for the CSS feature used to calculate an item's intrinsic width.
+
 See the [documentation index](../README.md) for setup and troubleshooting guides.
diff --git a/styles.css b/styles.css
index e957358b..73427f02 100644
--- a/styles.css
+++ b/styles.css
@@ -857,7 +857,8 @@ body.is-mobile .livesync-compatibility-review-notice {
     ~ .livesync-stat-item:not(
         .livesync-stat-push-remaining,
         .livesync-stat-pull-remaining,
-        .livesync-stat-ff,
+        .livesync-stat-ff-push,
+        .livesync-stat-ff-pull,
         .livesync-stat-p2p
     ) {
     margin-inline-start: 1em;
diff --git a/test/e2e-obsidian/README.md b/test/e2e-obsidian/README.md
index a8355261..386e5167 100644
--- a/test/e2e-obsidian/README.md
+++ b/test/e2e-obsidian/README.md
@@ -88,7 +88,11 @@ npm run test:e2e:obsidian:focused -- replication-status
 
 The wrapper accepts only maintained real-Obsidian scenario names; run it with `--help` for the current list. It deliberately does not manage CouchDB, Object Storage, or the P2P signalling relay. Start the required fixture first, or use the complete service-managed suite.
 
-`replication-status` uses an isolated Vault without a remote service. It injects synthetic replication statistics into the real plug-in to check the ⏩ icon, the comparison count and its three-second expiry, independently styled numeric items, stable rendered digit widths, computed right alignment, and unchanged DOM nodes for repeated values. It also feeds the existing queue sources and checks their values in both displays, the separate P2P line, file warnings and their compact icon, and the corresponding plain-text status. It verifies the inactive class, retained inactive content and width, and the ability to override the default hiding behaviour through CSS. A separate session enters mobile emulation before loading the plug-in and measures the editor item gaps at a 390px viewport width. The desktop checks also ensure that the status bar keeps its compact spacing. The mobile spacing fixture uses the existing overlay placement method before measurement; it does not verify Android window events. It switches between split panes, opens a popout editor, checks log updates there, and returns to the main window. Where Electron exposes native window control, it also hides the main window and verifies that popout logs still update before restoring it. This checks display behaviour; Commonlib owns the tests which establish that PouchDB produces the underlying statistics.
+`replication-status` uses isolated Vaults without a remote service. It opens the fixture editor before loading the plug-in, then checks the resulting overlay and subsequent leaf transitions. It injects synthetic replication statistics into real Obsidian to check the ⏩ icon and the push and pull comparison counts. The comparison cases cover a push-only count while the `sent` total is zero, independent three-second expiry when both directions are active, a zeroed state before a fresh 0-to-1 count, restoration of the ordinary Sync icon when CouchDB is idle, and error-icon priority. The plain-text status is checked for separate comparison and transfer counts, including its `(LIVE)` labels.
+
+The scenario also checks independently styled numeric items, stable rendered digit widths, computed right alignment, and unchanged DOM nodes for repeated values. It feeds the existing queue sources and checks their values in both displays, the separate P2P line, file warnings and their compact icon, and the corresponding plain-text status. It verifies the inactive class, retained inactive content and width, and the ability to override the default hiding behaviour through CSS. The desktop checks ensure that the status bar keeps its compact spacing.
+
+The scenario reads the animation CSS fence from [the status display guide](../../docs/tips/status-display.md) and checks it in desktop and mobile emulation: an inactive item collapses through an interpolated width, the same DOM node expands when reactivated, and reduced motion disables the transition. The fallback check substitutes a false `@supports` condition and confirms default hiding; this simulates feature unavailability and does not verify a browser which lacks `calc-size()` or Safari. A separate session enters mobile emulation before loading the plug-in and measures editor item gaps at a 390px viewport width. The mobile spacing fixture uses the existing overlay placement method before measurement; it does not verify Android window events. The scenario switches between split panes, opens a popout editor, checks log updates there, and returns to the main window. Where Electron exposes native window control, it also hides the main window and verifies that popout logs still update before restoring it. This checks display behaviour; Commonlib owns the tests which establish that PouchDB produces the underlying statistics.
 
 `database-diagnostics` needs no remote service. It checks the Usage command and Hatch integrity action with an isolated Vault, including visible radio choices for original names and pseudonyms, their default and keyboard navigation, the default-on integrity-only remote option, retained local findings when the remote is unavailable, cancellation during inspection with earlier rows retained, and unchanged settings, local revisions, and Vault files. It captures desktop results and the choice and result dialogues in mobile emulation, checking layout at 800×600 and 375×667, radio choices for available formats, their touch targets, and export controls. Copy and download payloads are captured inside the isolated renderer, so the scenario leaves the host clipboard and download directory unchanged.
 
diff --git a/test/e2e-obsidian/scripts/replication-status.ts b/test/e2e-obsidian/scripts/replication-status.ts
index 155bbf61..ee63e9f3 100644
--- a/test/e2e-obsidian/scripts/replication-status.ts
+++ b/test/e2e-obsidian/scripts/replication-status.ts
@@ -1,3 +1,4 @@
+import { readFileSync } from "node:fs";
 import { discoverObsidianCli, requireObsidianBinary } from "../runner/environment.ts";
 import { startObsidianLiveSyncSession, type ObsidianLiveSyncSession } from "../runner/session.ts";
 import { withObsidianPage } from "../runner/ui.ts";
@@ -8,7 +9,7 @@ import { setObsidianMobileTestModeBeforePluginStart } from "../runner/mobileUi.t
 const fixturePath = "replication-status-e2e.md";
 const uiTimeoutMs = Number(process.env.E2E_OBSIDIAN_UI_TIMEOUT_MS ?? 10000);
 const fastForwardLingerMs = 3000;
-const numericKeys = ["network", "sent", "push-remaining", "arrived", "pull-remaining", "ff"] as const;
+const numericKeys = ["network", "sent", "push-remaining", "arrived", "pull-remaining", "ff-push", "ff-pull"] as const;
 
 type TestReplicationStatics = {
     sent: number;
@@ -17,9 +18,9 @@ type TestReplicationStatics = {
     maxPushSeq: number;
     lastSyncPullSeq: number;
     lastSyncPushSeq: number;
-    syncStatus: "CONNECTED";
+    syncStatus: "CONNECTED" | "PAUSED" | "ERRORED";
     couchDB: {
-        phase: "continuous";
+        phase: "continuous" | "idle";
         pull: { checkedChanges: number; completedBatches: number; checking: boolean };
         push: { checkedChanges: number; completedBatches: number; checking: boolean };
     };
@@ -33,6 +34,8 @@ type TestLeaf = {
     detach?: () => void;
 };
 type TestWorkspace = {
+    layoutReady?: boolean;
+    getMostRecentLeaf?: () => TestLeaf | null;
     activeLeaf?: TestLeaf | null;
     getLeaf?: (newLeaf?: boolean | "split" | "tab" | "window", direction?: "horizontal" | "vertical") => TestLeaf;
     openPopoutLeaf?: () => TestLeaf;
@@ -106,7 +109,12 @@ function failUnless(condition: unknown, message: string): asserts condition {
     if (!condition) throw new Error(message);
 }
 
-function replicationStats(checkedChanges: number, sent: number, arrived: number): TestReplicationStatics {
+function replicationStats(
+    checkedChanges: number,
+    sent: number,
+    arrived: number,
+    pushCheckedChanges = 0
+): TestReplicationStatics {
     return {
         sent,
         arrived,
@@ -118,7 +126,7 @@ function replicationStats(checkedChanges: number, sent: number, arrived: number)
         couchDB: {
             phase: "continuous",
             pull: { checkedChanges, completedBatches: 0, checking: true },
-            push: { checkedChanges: 0, completedBatches: 0, checking: false },
+            push: { checkedChanges: pushCheckedChanges, completedBatches: 0, checking: pushCheckedChanges > 0 },
         },
     };
 }
@@ -252,7 +260,7 @@ async function getStatusDiagnostics(page: Page): Promise<Record<string, unknown>
         const status = document.querySelector<HTMLElement>(".livesync-status");
         const statusParent = status?.parentElement;
         const activeLeaf = app?.workspace?.activeLeaf;
-        const recentLeaf = app?.workspace?.getLeaf?.(false);
+        const recentLeaf = app?.workspace?.getMostRecentLeaf?.();
         const statusStyle = status ? getComputedStyle(status) : undefined;
         const statusParentStyle = statusParent ? getComputedStyle(statusParent) : undefined;
         const activeLeafContainer = activeLeaf?.view?.containerEl;
@@ -284,7 +292,11 @@ async function getStatusDiagnostics(page: Page): Promise<Record<string, unknown>
                       visibility: statusParentStyle?.visibility,
                   }
                 : undefined,
+            workspaceLayoutReady: app?.workspace?.layoutReady,
             moduleHasStatusDiv: moduleLog?.statusDiv !== undefined,
+            moduleStatusDivConnected: moduleLog?.statusDiv?.isConnected,
+            moduleStatusDivParent: moduleLog?.statusDiv?.parentElement?.className,
+            recentLeafIsActive: recentLeaf === activeLeaf,
             moduleStatusLine: moduleLog?.statusLine
                 ? {
                       tag: moduleLog.statusLine.tagName,
@@ -557,7 +569,7 @@ async function assertStatusBarItemSpacing(page: Page): Promise<void> {
 async function assertInactiveItemStyling(page: Page): Promise<void> {
     const roots = [".livesync-status-statusline", ".syncstatusbar"];
     for (const root of roots) {
-        const state = await page.locator(`${root} .livesync-stat-ff`).evaluate((element) => {
+        const state = await page.locator(`${root} .livesync-stat-ff-pull`).evaluate((element) => {
             const item = element as HTMLElement;
             return {
                 inactive: item.classList.contains("livesync-stat-inactive"),
@@ -588,7 +600,7 @@ async function assertInactiveItemStyling(page: Page): Promise<void> {
     try {
         for (const root of roots) {
             failUnless(
-                await page.locator(`${root} .livesync-stat-ff`).isVisible(),
+                await page.locator(`${root} .livesync-stat-ff-pull`).isVisible(),
                 `A CSS override could not reveal the inactive item in ${root}.`
             );
         }
@@ -597,12 +609,221 @@ async function assertInactiveItemStyling(page: Page): Promise<void> {
     }
     for (const root of roots) {
         failUnless(
-            await page.locator(`${root} .livesync-stat-ff`).isHidden(),
+            await page.locator(`${root} .livesync-stat-ff-pull`).isHidden(),
             `The default inactive style was not restored in ${root}.`
         );
     }
 }
 
+async function waitForComparisonCounts(page: Page, push?: number, pull?: number): Promise<void> {
+    await page.waitForFunction(
+        ({ push, pull }) =>
+            [".livesync-status-statusline", ".syncstatusbar"].every((root) =>
+                (["push", "pull"] as const).every((direction) => {
+                    const value = document.querySelector(
+                        `${root} .livesync-stat-ff-${direction}:not(.livesync-stat-inactive) .livesync-stat-value`
+                    );
+                    const expected = direction === "push" ? push : pull;
+                    return expected === undefined ? value === null : value?.textContent?.trim() === String(expected);
+                })
+            ),
+        { push, pull },
+        { timeout: uiTimeoutMs }
+    );
+}
+
+async function waitForSyncIcon(page: Page, icon: string): Promise<void> {
+    await page.waitForFunction(
+        (expected) =>
+            [".livesync-status-statusline", ".syncstatusbar"].every(
+                (root) => document.querySelector(`${root} .livesync-stat-sync`)?.textContent === `Sync: ${expected}`
+            ),
+        icon,
+        { timeout: uiTimeoutMs }
+    );
+}
+
+async function assertDirectionalComparison(page: Page): Promise<void> {
+    const pushOnly = replicationStats(0, 0, 0, 71975);
+    pushOnly.couchDB.pull.checking = false;
+    await injectReplicationStats(page, pushOnly, 0, 0);
+    await waitForComparisonCounts(page, 71975);
+    await waitForSyncIcon(page, "⏩");
+    for (const root of [".livesync-status-statusline", ".syncstatusbar"]) {
+        failUnless(
+            (await page.locator(`${root} .livesync-stat-sent .livesync-stat-value`).textContent())?.trim() === "0",
+            `Push comparison changed the transfer count in ${root}.`
+        );
+    }
+
+    await injectReplicationStats(page, replicationStats(4, 0, 0, 40), 0, 0);
+    await waitForComparisonCounts(page, 40, 4);
+    for (const direction of ["push", "pull"]) {
+        const margin = await page
+            .locator(`.livesync-status-statusline .livesync-stat-ff-${direction}`)
+            .evaluate((element) => Number.parseFloat(getComputedStyle(element).marginInlineStart));
+        failUnless(margin === 0, `The ${direction} comparison item acquired an extra ${margin}px editor gap.`);
+    }
+    for (let update = 1; update <= 3; update++) {
+        await page.waitForTimeout(700);
+        await injectReplicationStats(page, replicationStats(4, 0, 0, 40 + update), 0, 0);
+    }
+    await waitForComparisonCounts(page, 43);
+    await waitForComparisonCounts(page);
+    await injectReplicationStats(page, replicationStats(4, 7, 11, 43), 0, 0);
+    await waitForPartText(page, "arrived", "11");
+    await waitForComparisonCounts(page);
+
+    const idle = replicationStats(4, 7, 11, 43);
+    idle.syncStatus = "PAUSED";
+    idle.couchDB.phase = "idle";
+    idle.couchDB.push.checking = false;
+    idle.couchDB.pull.checking = false;
+    await injectReplicationStats(page, idle, 0, 0);
+    await waitForSyncIcon(page, "💤");
+    await waitForComparisonCounts(page);
+
+    const failed = replicationStats(5, 7, 11, 44);
+    failed.syncStatus = "ERRORED";
+    await injectReplicationStats(page, failed, 0, 0);
+    await waitForComparisonCounts(page, 44, 5);
+    await waitForSyncIcon(page, "⚠");
+
+    await injectReplicationStats(page, replicationStats(0, 0, 0), 0, 0);
+    await waitForComparisonCounts(page);
+    await injectReplicationStats(page, replicationStats(1, 0, 0, 1), 0, 0);
+    await waitForComparisonCounts(page, 1, 1);
+    await waitForSyncIcon(page, "⏩");
+    const labels = await page.evaluate(() => {
+        const modules = (globalThis as TestWindow).app?.plugins?.plugins?.["obsidian-livesync"]?.core?.modules ?? [];
+        const moduleLog = modules.find(
+            (entry): entry is TestLogModule =>
+                typeof entry === "object" && entry !== null && (entry as TestLogModule).statusBarLabels !== undefined
+        );
+        return moduleLog?.statusBarLabels?.value.message;
+    });
+    failUnless(
+        labels?.includes("(⏩↑ 1) (⏩↓ 1) ↑ 0 (LIVE) ↓ 0 (LIVE)"),
+        `The plain-text status did not distinguish comparison directions from transfers: ${labels}`
+    );
+    console.log(
+        "Directional comparison passed: push-only, independent expiry, idle/error icons, and fresh-run counts."
+    );
+}
+
+function documentedAnimationSnippet(): string {
+    const guide = readFileSync(new URL("../../../docs/tips/status-display.md", import.meta.url), "utf8");
+    const section = guide.split("### Animate editor status items")[1];
+    const snippet = section?.match(/```css\r?\n([\s\S]*?)\r?\n```/u)?.[1];
+    failUnless(snippet, "The documented editor animation snippet could not be found.");
+    return snippet;
+}
+
+async function assertDocumentedAnimation(page: Page): Promise<void> {
+    const css = documentedAnimationSnippet();
+    const fallbackCss = css.replace("@supports (width: calc-size(auto, size))", "@supports (width: e2e-unsupported)");
+    failUnless(fallbackCss !== css, "The animation example is missing its calc-size feature guard.");
+    const selector = ".livesync-status-statusline .livesync-stat-ff-push";
+    await injectReplicationStats(page, replicationStats(0, 0, 0, 200), 0, 0);
+    await waitForComparisonCounts(page, 200);
+    const fallback = await page.addStyleTag({ content: fallbackCss });
+    try {
+        await injectReplicationStats(page, replicationStats(0, 0, 0), 0, 0);
+        await waitForComparisonCounts(page);
+        failUnless(
+            (await page.locator(selector).evaluate((element) => getComputedStyle(element).display)) === "none",
+            "An unsupported animation guard overrode the default inactive-item hiding."
+        );
+    } finally {
+        await fallback.evaluate((element) => element.parentNode?.removeChild(element));
+    }
+
+    const supported = await page.evaluate(() => CSS.supports("width", "calc-size(auto, size)"));
+    if (!supported) {
+        console.log("Documented snippet: default hiding passed; this runtime does not support calc-size animations.");
+        return;
+    }
+    await page.emulateMedia({ reducedMotion: "no-preference" });
+    const style = await page.addStyleTag({ content: css });
+    try {
+        const item = page.locator(selector);
+        await injectReplicationStats(page, replicationStats(0, 0, 0, 201), 0, 0);
+        await waitForComparisonCounts(page, 201);
+        await page.waitForFunction(
+            (selector) => {
+                const item = document.querySelector<HTMLElement>(selector);
+                return item !== null && item.getBoundingClientRect().width > 1 && item.getAnimations().length === 0;
+            },
+            selector,
+            { timeout: uiTimeoutMs }
+        );
+        const openWidth = await item.evaluate((element) => element.getBoundingClientRect().width);
+        const original = await item.elementHandle();
+        failUnless(original, "The animated comparison item is missing.");
+        await injectReplicationStats(page, replicationStats(0, 0, 0), 0, 0);
+        await page.waitForFunction(
+            ({ selector, openWidth }) => {
+                const item = document.querySelector<HTMLElement>(selector);
+                const width = item?.getBoundingClientRect().width ?? 0;
+                return item?.classList.contains("livesync-stat-inactive") && width > 0.5 && width < openWidth - 0.5;
+            },
+            { selector, openWidth },
+            { timeout: uiTimeoutMs }
+        );
+        await page.waitForFunction(
+            (selector) => {
+                const item = document.querySelector<HTMLElement>(selector);
+                return item !== null && item.getBoundingClientRect().width < 0.5 && item.getAnimations().length === 0;
+            },
+            selector,
+            { timeout: uiTimeoutMs }
+        );
+        const collapsed = await item.evaluate((element) => ({
+            display: getComputedStyle(element).display,
+            margin: getComputedStyle(element).marginInlineStart,
+            ariaHidden: element.getAttribute("aria-hidden"),
+        }));
+        failUnless(
+            collapsed.display === "inline-block" && collapsed.margin === "0px" && collapsed.ariaHidden === "true",
+            "The animated inactive item lost its collapsed layout or accessibility state."
+        );
+        await injectReplicationStats(page, replicationStats(0, 0, 0, 202), 0, 0);
+        await waitForComparisonCounts(page, 202);
+        await page.waitForFunction(
+            ({ selector, openWidth }) => {
+                const item = document.querySelector<HTMLElement>(selector);
+                return item !== null && Math.abs(item.getBoundingClientRect().width - openWidth) < 0.5;
+            },
+            { selector, openWidth },
+            { timeout: uiTimeoutMs }
+        );
+        failUnless(
+            await original.evaluate((element, selector) => element === document.querySelector(selector), selector),
+            "Reopening an animated item replaced its retained DOM node."
+        );
+        await original.dispose();
+
+        await page.emulateMedia({ reducedMotion: "reduce" });
+        await injectReplicationStats(page, replicationStats(0, 0, 0), 0, 0);
+        await waitForComparisonCounts(page);
+        const reduced = await item.evaluate((element) => ({
+            width: element.getBoundingClientRect().width,
+            transition: getComputedStyle(element).transitionProperty,
+            animations: element.getAnimations().length,
+        }));
+        failUnless(
+            reduced.width < 0.5 && reduced.transition === "none" && reduced.animations === 0,
+            "The documented snippet did not honour reduced motion."
+        );
+        console.log(
+            "Documented snippet passed: interpolated collapse, retained-node reopening, reduced motion, and disabled-guard fallback."
+        );
+    } finally {
+        await style.evaluate((element) => element.parentNode?.removeChild(element));
+        await page.emulateMedia({ reducedMotion: null });
+    }
+}
+
 async function measureStatusBarNetworkWidth(
     page: Page,
     expectedValue: string
@@ -846,7 +1067,7 @@ async function runStatusScenario(session: ObsidianLiveSyncSession): Promise<void
         let popoutPage: Page | undefined;
         let mainWindow: MainWindowControl | undefined;
         try {
-            await installFixtureFile(page);
+            console.log(`Replication status runtime: ${await page.evaluate(() => navigator.userAgent)}`);
             try {
                 await page.locator(".livesync-status").waitFor({ state: "attached", timeout: uiTimeoutMs });
             } catch (error) {
@@ -882,11 +1103,11 @@ async function runStatusScenario(session: ObsidianLiveSyncSession): Promise<void
             const startedAt = Date.now();
             await injectReplicationStats(page, initialStats, 0, 0);
             await waitForPartText(page, "arrived", "0");
-            await waitForPartText(page, "ff", "1000");
+            await waitForPartText(page, "ff-pull", "1000");
             await assertStatusBarItemSpacing(page);
             for (const root of [".livesync-status-statusline", ".syncstatusbar"]) {
                 failUnless(
-                    (await page.locator(`${root} .livesync-stat-ff + .livesync-stat-sent`).count()) === 1,
+                    (await page.locator(`${root} .livesync-stat-ff-pull + .livesync-stat-sent`).count()) === 1,
                     `The comparison count did not appear immediately before uploads in ${root}.`
                 );
             }
@@ -902,7 +1123,7 @@ async function runStatusScenario(session: ObsidianLiveSyncSession): Promise<void
             await page.waitForFunction(
                 () =>
                     document
-                        .querySelector(".livesync-status-statusline .livesync-stat-ff")
+                        .querySelector(".livesync-status-statusline .livesync-stat-ff-pull")
                         ?.classList.contains("livesync-stat-inactive") === true,
                 undefined,
                 { timeout: uiTimeoutMs }
@@ -914,11 +1135,11 @@ async function runStatusScenario(session: ObsidianLiveSyncSession): Promise<void
                 "The fast-forward checking icon disappeared when its count expired."
             );
 
-            await injectReplicationStats(page, replicationStats(1001, 1001, 1001), 1001, 0);
+            await injectReplicationStats(page, replicationStats(1001, 1001, 1001, 1001), 1001, 0);
             const wideWidths = await assertNumericWidths(page, "1001");
             const wideStatusBarWidth = await measureStatusBarNetworkWidth(page, "1001");
             failUnless(wideStatusBarWidth.cssWidth === "4ch", "The status-bar network count did not reserve 4ch.");
-            await injectReplicationStats(page, replicationStats(7, 7, 7), 7, 0);
+            await injectReplicationStats(page, replicationStats(7, 7, 7, 7), 7, 0);
             const narrowWidths = await assertNumericWidths(page, "7");
             const narrowStatusBarWidth = await measureStatusBarNetworkWidth(page, "7");
             for (const key of numericKeys) {
@@ -942,6 +1163,8 @@ async function runStatusScenario(session: ObsidianLiveSyncSession): Promise<void
                 `Identical status render: 1000 iterations, 0 DOM mutations, ${repeatedRender.elapsedMs.toFixed(2)} ms.`
             );
 
+            await assertDirectionalComparison(page);
+
             await createSplitLeaf(page);
             await assertSingleOverlay(page.context().pages());
             await waitForOverlayOnActiveLeaf(page);
@@ -1030,13 +1253,15 @@ async function main(): Promise<void> {
                 binary,
                 cliBinary: cli.binary,
                 vault,
-                lifecycle: mobile
-                    ? {
-                          beforePluginStart: async ({ remoteDebuggingPort }) => {
-                              await setObsidianMobileTestModeBeforePluginStart(remoteDebuggingPort, true, uiTimeoutMs);
-                          },
-                      }
-                    : undefined,
+                lifecycle: {
+                    beforePluginStart: async ({ remoteDebuggingPort }) => {
+                        if (mobile) {
+                            await setObsidianMobileTestModeBeforePluginStart(remoteDebuggingPort, true, uiTimeoutMs);
+                        }
+                        // Prepare the editor before asynchronous plug-in loading can place the overlay in it.
+                        await withObsidianPage(remoteDebuggingPort, installFixtureFile);
+                    },
+                },
                 startupGraceMs: Number(process.env.E2E_OBSIDIAN_STARTUP_GRACE_MS ?? 1000),
                 pluginData: {
                     liveSync: false,
@@ -1080,6 +1305,8 @@ async function main(): Promise<void> {
                     );
                 }
                 await assertEditorItemSpacing(page, mobile);
+                if (mobile) await assertDirectionalComparison(page);
+                await assertDocumentedAnimation(page);
             });
         } finally {
             if (session) await session.app.stop();
diff --git a/updates.md b/updates.md
index f5551d3b..00254d01 100644
--- a/updates.md
+++ b/updates.md
@@ -12,6 +12,12 @@ Earlier releases remain available in the 1.0 release history, the 1.0 preview hi
 
 ## Unreleased
 
+### Synchronisation
+
+- We can see CouchDB change-feed comparison progress separately for push and pull.
+    - The `⏩↑` and `⏩↓` counts show entries compared in each direction; the upload and download totals remain separate.
+    - Existing CSS snippets which target `livesync-stat-ff` to hide comparison progress need to target both `livesync-stat-ff-push` and `livesync-stat-ff-pull`. See the [status display guide](docs/tips/status-display.md).
+
 ## 1.0.42
 
 27th October, 2026