deploy: excluded must mean GONE from the droplet, not merely unsent

I claimed the last commit took 28 MB off the deploy. It took 28 MB off the TRANSFER and left every byte of it live on stellate.app, which I should have checked before saying so.

• rsync's plain --delete only removes receiver files that are absent from the SOURCE. It deliberately PROTECTS anything matching an --exclude, on the theory that you may be excluding files you want left alone on…

• 154 engine/faust/node_modules the @grame cut that did not take 134 found/samples/*/zones.json extractor output nothing fetches ~600 tools/node_modules better-sqlite3, semver, tar-fs and friends -- build-time…

• Nothing outside those buckets is touched. MEDIA_MANIFEST appears in the deletion list and is irrelevant: it is not in the source tree, so plain --delete already removed it on every deploy, and the very next…

• This is the same failure shape as the found/midi leak that had to be scrubbed from the droplet by hand: an exclusion that everyone believed was removing something when it was only declining to send it.

▶ Play it: Rail Replacement Rapture — a bed-heavy genre where the found-sound layer carries the room https://stellate.app/?genre=transitwave&seed=7731&path=749.12536,768.12569,730.12569&xdur=13.122

76c905e https://github.com/aboard-io/stellate/commit/76c905e3c8436b10a215b8224545d3be7116d923