Vite asset hashing in a multi-server deployment without sticky sessions

During rolling deploys across two VPS instances, users occasionally hit 404 errors for JavaScript chunks. A browser would load HTML from Server A, but fetch chunk app-8a1f.js from Server B which was still on the prior release.

# In the deployment script: retain previous build artifacts for 24 hours
rsync -av --keep-dirlinks ./build/ /var/www/shared/assets/

# Do not run `rm -rf dist` on deploy; prune old hashes via find:
find /var/www/shared/assets -type f -mtime +2 -delete

Retaining previous hashed assets on disk across rolling deploys ensures that users on mid-session page loads never suffer asset 404s while nodes finish updating.