docs(cloud): recommend exported repair command

Author: Alan-TheGentleman

README.md

@@ -127,7 +127,14 @@ engram sync --cloud --project smoke-project
 Cloud mode is always project-scoped (`--project` is required; `engram sync --cloud --all` is intentionally blocked).
 Known repairable cloud sync/upsert/canonicalization failures keep the original error visible and recommend the explicit `doctor`/`repair` flow below; Engram never auto-applies repair from sync or autosync.
 For blocked cloud sync, `transport_failed`, or legacy session directory repair, see [Engram Cloud Troubleshooting](docs/engram-cloud/troubleshooting.md).
-If `doctor` reports a legacy mutation missing `directory` or observation fields such as `title`, use the dry-run helper first: `tools/repair-missing-session-directory.sh <project>`. Add `--interactive` when the helper needs a human-provided title/content from the shown excerpt; after previewing, use `--apply --interactive --all <project>` to clear sequential supported blockers. If `doctor` is ready but `sync --cloud` fails with `sessions[N].directory is required`, rerun the helper with `--fix-empty-sessions` or `--all` so it repairs local empty `sessions.directory` rows for that project without touching `sync_mutations`.
+If cloud sync stays blocked after `doctor`/`repair`, download the rescue helper and run the recommended exported-row repair:
+
+```bash
+tools/repair-missing-session-directory.sh --apply --interactive --fix-exported <project>
+engram sync --cloud --project <project>
+```
+
+`--fix-exported` repairs local exported `sessions[].directory` and `observations[]` required fields that can still break the final push after `doctor` reports ready. For sequential legacy `sync_mutations` blockers, use `tools/repair-missing-session-directory.sh --apply --interactive --all <project>`.
 
 **After upgrading `engram` while an MCP client is already running:**