NeoGDSync

Fixes a bug where two devices syncing the same vault could end up with two Drive files sharing the exact same name and path — silently, with zero conflict ever reported.

What happened

handlePush() decides how to push a pending create/modify op. When the local path index has no entry for that path, it's supposed to first check whether Drive already has a file with that name in the target folder (findOnDrive()) before deciding whether to update the existing file or upload a new one. That safety net was added in 1.0.9 for modify ops (an index-loss recovery case) — but create ops never got it, and just uploaded unconditionally.

A create op fires whenever a device's local index has no record of a path yet — which includes the case where another device already pushed that exact file to Drive, and this device simply hasn't learned about it. Since conflict detection only compares Drive changes against paths already present in the local index, a path with no index entry never enters that check either. Two devices could therefore push the same filename through two completely different, conflict-free code paths and end up with two Drive objects.

Reproduced 2026-08-06/07: a note was edited on a Mac (auto-pushed via a scheduled Smart Sync) and independently re-created on an iPad before the iPad's index had ever seen that path. Both devices' Smart Sync runs reported zero conflicts. Drive ended up holding two files at the same path: 2026/2026.08.06 Communication with Leo on ETHSystem.md (10Cm8T3BLFyyjIZ1F9jC7v_dXGtfeIUR0 and 1uOmTJX4ZmyBAZbdbSnQLlOvr4mst0OvQ), confirmed via a direct Drive API files.list query scoped to the vault's 2026 folder.

Fix

• syncer.ts: handlePush() now runs findOnDrive() for both create and modify ops before deciding to upload vs. update. findOnDrive() already resolves duplicates deterministically (prefers the index-cached id, else the most recently modified same-name file) — no new duplicate-resolution logic was needed, just closing the gap in which op types used it.
• tests/syncer.test.ts (new — syncer.ts had no test coverage before this): asserts a create op with no index entry updates an existing same-name Drive file instead of uploading a duplicate, and that a genuinely new filename still uploads normally.

Upgrade notes

This prevents new duplicates from forming; it does not scan for or merge duplicates that already exist in a vault from before this version. If a device's index goes stale for long enough that it stops recognizing paths another device owns, re-running "Rebuild Drive Index" keeps both devices' views of Drive in sync and avoids relying on findOnDrive()'s per-path fallback lookup.