2.3.2

Fix: deploys failing against older rsync on the server

Since 2.3.1, deploys could abort when the remote server runs an older rsync (e.g. 3.1.3):

ERROR: rejecting excluded file-list name: public/core
rsync error: protocol incompatibility (code 2) at flist.c(912) [receiver=3.1.3]

The new protect rules (P /public/*) also matched the deployed paths themselves, which older receivers treat as excluded. Deployed paths and their parents are now explicitly exempted, while undeployed files like wp-config.php, index.php and uploads stay protected.

Also fixed for nested deploy paths (e.g. core at public with content at public/content): stale files in the outer directory are deleted again, and those setups no longer hit the same error.