docs(data): explain skipped-file cleanup policy

Clarify that skipped files can leave unique data on either side, so cleanup records intentionally remain unchanged and deletion performs the final active-path safety check.
This commit is contained in:
digua committed 2026-07-18 16:15:19 +08:00
1 parent d4c837b367
commit 4518a3aaa9
1 file changed
+1
@@ -261,6 +261,7 @@ export function runPendingDataDirMigration(
deps.writeUserDataDir(pending.to)
// Skipped files may leave unique data in either directory, so cleanup records stay unchanged; deletion revalidates active paths.
if (pending.migrate && path.resolve(pending.from) !== path.resolve(pending.to) && stats.skipped === 0) {
deps.recordPendingCleanup?.(pending.from, pending.to)
} else if (stats.skipped > 0) {