# File Operations

These references cover the canonical file browsing and transfer behaviors.

## Primary References

- [File Management](../FILE_MANAGEMENT.md).
- [Rclone Usage](../RCLONE_USAGE.md).
- [Path Resolution](../PATH_RESOLUTION.md).
- [System Logs](../SYSTEM_LOGS.md).

## What This Covers

- File and folder browsing.
- Copy and move behavior across providers.
- Path normalization and provider-specific ID resolution.
- Transfer observability and failure diagnosis.

## Delete Results

Delete progress reports what each connected provider actually completed. A
successful item is shown under either `Permanently deleted` or `Moved to Trash`.
If permanent deletion is unavailable but the provider successfully falls back
to its trash or recycle bin, Stratofusion identifies that recoverable result
instead of claiming the item was permanently deleted.

## Resolving Google to OneDrive Name Conflicts

When you copy a folder from Google Drive to OneDrive, Stratofusion now checks for sibling items that Google permits but OneDrive cannot store. The common case is a folder and a file that would land in OneDrive with the same name.

### What Happens

1. Before the folder copy starts, Stratofusion runs a compatibility check.
2. If conflicts are found, the copy pauses and opens a resolution dialog.
3. You choose how to handle each conflict before any copy starts.
4. The folder copy proceeds only after the conflict set is valid for OneDrive.

### Resolution Options

- Rename the conflicting Google Drive item before the copy starts.
- Skip one or more conflicting items from the copy.
- Cancel the entire operation.

The dialog also includes bulk actions so you can:

- Rename all conflicting folders using the suggested ` - Folder` suffix.
- Rename all conflicting files using the suggested safe filename.
- Skip every conflicting item in the current folder copy.

### Safety Rules

- Stratofusion never auto-renames without an explicit user confirmation.
- If a Google Drive rename batch fails, already-applied renames are rolled back.
- If post-rename validation still finds an incompatible collision, the rename batch is rolled back.
- If you choose to skip a conflicting folder, its descendants are excluded from the copy as well.

### Completion Summary

Successful folder copies now include a short compatibility summary in progress and completion messaging, for example:

- `1 source rename applied`.
- `2 conflicting items skipped`.
- `1 source rename applied, 1 conflicting item skipped`.

### Recommended Manual Verification

1. Create a Google Drive test folder with a folder/file sibling collision.
2. Start a Google Drive to OneDrive folder copy in Stratofusion.
3. Confirm the compatibility dialog appears before the copy starts.
4. Test rename and skip paths separately.
5. Verify the OneDrive destination reflects the chosen resolution with no silent overwrites.

## Related Guides

- [Search Features](./SEARCH_FEATURES.md).
- [Backup and Sync](./BACKUP_SYNC.md).
- [Troubleshooting](./TROUBLESHOOTING.md).