# UnifiedFiler v1.9.7-fix1 Notes

## Purpose

This fix addresses Google Drive 403 errors that can occur when renaming files from the Drive UI.

## Changes

- Command state now merges adapter capabilities with per-entry capabilities from Google Drive file metadata.
- Rename/Delete UI actions are disabled when the selected Drive file reports insufficient per-file permission, such as `capabilities.canRename === false`.
- Inline rename performs a preflight permission check before calling Drive API.
- `GoogleDriveAdapter.rename()` rejects early when Drive file capabilities indicate rename is not allowed.
- `GoogleDriveApiService` now preserves HTTP status, reason and request context in error messages.
- Google Drive demo default OAuth scope was changed to `https://www.googleapis.com/auth/drive` because full file-manager operations over arbitrary listed Drive files require broader Drive access. Hosts may still use `drive.file` when files are selected through Google Picker or created by the app.

## Notes

When using `https://www.googleapis.com/auth/drive.file`, Google Drive may deny PATCH/rename for files that were merely listed by the app. The UI now respects Google Drive per-file capabilities to avoid sending unsupported operations where possible.