When using the Proton Drive CLI to sync a local folder to Drive, the --conflict-strategy skip flag appears to skip entire directories that already exist on the remote side, without inspecting their contents for new or modified files.

This makes incremental syncing impractical. In a typical workflow — for example, backing up a Documents folder after a day of work — new files are often created in various subdirectories. With the current behavior, the user would need to manually identify every subdirectory that already exists on Drive and target those individually, which defeats the purpose of a CLI backup command.

Expected behavior: when --conflict-strategy skip encounters an existing directory, it should recurse into it and skip only the individual files that already exist, while still uploading new or modified files within that directory.

This would make the CLI suitable for recurring backup scenarios, which is one of the primary use cases highlighted in the documentation.