the periodicScan code is still in main branch and reachable via WorkLauncher.kt - see the Readme for activity to trigger. Imo FileObserver is an alternative method that doesn’t rely on a interval schedule? but looking at logcat as you trigger either the FORCE_SCAN or Observer intents and see the log messages things will be clear.
I do look at handleFileDelete in FileEventHandler.kt and I think it will not go into a remote delete, but DISABLE_SYNCING - as it’d do in the periodicScan methods. To me it reads like “do not engage” in the sqlite db that holds state. You’ll see the removal of “REMOTE_DELETE” sync type in that observer file too before refactor. It survived the refactor.
I appreciate you look into the code, but nothing beats debugging probably. I’d still say from what I saw that there’s no remote removal, but I haven’t run eDrive for long now to know intuitively from usage