Does Dreamweaver's cloaking feature delete remote files during synchronization when they are locally cloaked?

Cloaking and Remote File Deletion in Dreamweaver Synchronization

Dreamweaver's cloaking feature is designed to prevent accidental public exposure of local files during remote publishing. When configured in Site Setup > Advanced Settings > Cloaking, developers can mark specific files or folders as cloaked using patterns like *.psd or /config/. These cloaked items are excluded from Put, Get, Synchronize, and Check In/Check Out operations with the remote server.

The Files panel displays a diagonal line icon over cloaked items, clearly indicating their protected status. Cloaked files remain fully accessible for local editing, Find/Replace, and site-wide reports, but they are never transferred to the remote server unless cloaking is temporarily disabled.

An unresolved behavior involves the interaction between cloaking and the 'Synchronize' command when 'Delete remote files not on local' is selected. The question is whether cloaked remote files that exist on the server but are marked as cloaked locally will be deleted during synchronization, or if Dreamweaver's logic preserves them to avoid unintended data loss.

This behavior is not well-documented across versions, and the outcome may depend on specific implementation details in the synchronization logic. Testing across different Dreamweaver versions would be required to determine the consistent behavior.

What is the expected behavior when synchronizing a site with cloaked files and the 'Delete remote files not on local' option enabled? Does the presence of cloaking override the deletion logic for remote files that match cloaked patterns?