Where
packages/extension-chrome/src/lib/apply-remote.ts (early-return when existingNode != null).
What
When applying a remote BookmarksFile state into chrome.bookmarks, the function early-returns on bookmarks already in the local id map ("Already in the local tree — assume in sync; next reconcile fixes drift"). But reconciliation only fires on cold start + 1h-stale-or-older, so a title edit made on Device B is invisible on Device A for up to an hour.
Cheap fix
Call chrome.bookmarks.update(existingNode, { title, url }) on the existing node when the remote entry differs from local. Costs one extra Chrome API call per changed bookmark per poll but eliminates the 1h lag.
Tracked from
PR review of feat/chrome-native-tree-integration.
Where
packages/extension-chrome/src/lib/apply-remote.ts(early-return whenexistingNode != null).What
When applying a remote
BookmarksFilestate intochrome.bookmarks, the function early-returns on bookmarks already in the local id map ("Already in the local tree — assume in sync; next reconcile fixes drift"). But reconciliation only fires on cold start + 1h-stale-or-older, so a title edit made on Device B is invisible on Device A for up to an hour.Cheap fix
Call
chrome.bookmarks.update(existingNode, { title, url })on the existing node when the remote entry differs from local. Costs one extra Chrome API call per changed bookmark per poll but eliminates the 1h lag.Tracked from
PR review of
feat/chrome-native-tree-integration.