chore(sync): mirror docs from openclaw/openclaw@bdd68a75ea

.openclaw-sync/source.json

@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "3e80805d11de4eec7f015edf5c87d02a55003c5a",
-  "syncedAt": "2026-05-03T21:38:53.753Z"
+  "sha": "bdd68a75eadcbaf5513fda5b876046302f7e6d87",
+  "syncedAt": "2026-05-03T21:45:40.633Z"
 }

docs/cli/doctor.md

@@ -45,7 +45,7 @@ Notes:
 - State integrity checks now detect orphan transcript files in the sessions directory. Archiving them as `.deleted.<timestamp>` requires an interactive confirmation; `--fix`, `--yes`, and headless runs leave them in place.
 - Doctor also scans `~/.openclaw/cron/jobs.json` (or `cron.store`) for legacy cron job shapes and can rewrite them in place before the scheduler has to auto-normalize them at runtime.
 - On Linux, doctor warns when the user's crontab still runs legacy `~/.openclaw/bin/ensure-whatsapp.sh`; that script is no longer maintained and can log false WhatsApp gateway outages when cron lacks the systemd user-bus environment.
-- Doctor cleans legacy plugin dependency staging state created by older OpenClaw versions. It also repairs missing configured downloadable plugins when the registry can resolve them, and the 2026.5.2 doctor pass automatically installs downloadable plugins that an older config already uses before marking the config touched for that release.
+- Doctor cleans legacy plugin dependency staging state created by older OpenClaw versions. It also repairs missing configured downloadable plugins when the registry can resolve them, and the 2026.5.2 doctor pass automatically installs downloadable plugins that an older config already uses before marking the config touched for that release. If the download fails, doctor reports the install error and preserves the configured plugin entry for the next repair attempt.
 - Doctor repairs stale plugin config by removing missing plugin ids from `plugins.allow`/`plugins.entries`, plus matching dangling channel config, heartbeat targets, and channel model overrides when plugin discovery is healthy.
 - Doctor quarantines invalid plugin config by disabling the affected `plugins.entries.<id>` entry and removing its invalid `config` payload. Gateway startup already skips only that bad plugin so other plugins and channels can keep running.
 - Set `OPENCLAW_SERVICE_REPAIR_POLICY=external` when another supervisor owns the gateway lifecycle. Doctor still reports gateway/service health and applies non-service repairs, but skips service install/start/restart/bootstrap and legacy service cleanup.

docs/fr/concepts/active-memory.md

@@ -695,6 +695,7 @@ Active Memory s’appuie sur le pipeline de rappel du Plugin mémoire configuré
     - Surveillez les journaux de la Gateway pour `active-memory: ... start|done`, `memory sync failed (search-bootstrap)` ou les erreurs d’embedding du fournisseur.
     - Exécutez `openclaw memory status --deep` pour inspecter le backend memory-search et l’état de l’index.
     - Si vous utilisez `ollama`, vérifiez que le modèle d’embedding est installé (`ollama list`).
+
   </Accordion>
 
   <Accordion title="Le premier rappel après un redémarrage de Gateway renvoie `status=timeout`">

docs/id/concepts/active-memory.md

@@ -694,6 +694,7 @@ Active Memory berjalan di atas pipeline recall plugin memori yang dikonfigurasi,
     - Pantau log Gateway untuk `active-memory: ... start|done`, `memory sync failed (search-bootstrap)`, atau error embedding provider.
     - Jalankan `openclaw memory status --deep` untuk memeriksa backend memory-search dan kesehatan indeks.
     - Jika Anda menggunakan `ollama`, pastikan model embedding terinstal (`ollama list`).
+
   </Accordion>
 
   <Accordion title="Recall pertama setelah restart Gateway mengembalikan `status=timeout`">

docs/ja-JP/concepts/active-memory.md

@@ -636,6 +636,7 @@ Active Memory は設定済みメモリー Plugin の recall パイプライン
     - Gateway ログで `active-memory: ... start|done`、`memory sync failed (search-bootstrap)`、またはプロバイダーの埋め込みエラーを確認します。
     - メモリー検索バックエンドとインデックスの健全性を調べるには、`openclaw memory status --deep` を実行します。
     - `ollama` を使用している場合は、埋め込みモデルがインストールされていることを確認します（`ollama list`）。
+
   </Accordion>
 
   <Accordion title="Gateway 再起動後の最初の recall が `status=timeout` を返す">

docs/tr/concepts/active-memory.md

@@ -646,6 +646,7 @@ Active Memory, yapılandırılmış bellek Plugin'inin geri çağırma işlem ha
     - Gateway günlüklerinde `active-memory: ... start|done`, `memory sync failed (search-bootstrap)` veya sağlayıcı embedding hatalarını izleyin.
     - Bellek arama arka ucunu ve dizin sağlığını incelemek için `openclaw memory status --deep` çalıştırın.
     - `ollama` kullanıyorsanız embedding modelinin yüklü olduğunu doğrulayın (`ollama list`).
+
   </Accordion>
 
   <Accordion title="Gateway yeniden başlatıldıktan sonraki ilk geri çağırma `status=timeout` döndürüyor">

docs/vi/concepts/active-memory.md

@@ -694,6 +694,7 @@ Active Memory chạy trên pipeline recall của Plugin bộ nhớ đã cấu h
     - Theo dõi nhật ký Gateway để tìm `active-memory: ... start|done`, `memory sync failed (search-bootstrap)`, hoặc lỗi embedding của provider.
     - Chạy `openclaw memory status --deep` để kiểm tra backend memory-search và tình trạng chỉ mục.
     - Nếu bạn dùng `ollama`, hãy xác nhận model embedding đã được cài đặt (`ollama list`).
+
   </Accordion>
 
   <Accordion title="Recall đầu tiên sau khi Gateway khởi động lại trả về `status=timeout`">