Trickle 0.1.15

Trickle 0.1.15 makes the successful transfer methods the defaults: continuous resumable downloads for pulls and signed upload windows of at most 16 MiB for pushes. The dashboard labels this Automatic (recommended); CLI commands use it unless another transport is explicitly selected.

• Keep large pushes below common request-body limits and declare Content-Length for each upload window.
• Resume from acknowledged byte offsets after interruption. Complete snapshot and per-file checksums still gate staging and replacement.
• Preserve the explicit 512 KB chunk option, checksum skips, saved transfer choices and destination backups.
• Keep plugin-originated traffic on the normal Trickle transfer/health user agents, including when an AI operator starts the migration. Remove test overrides and add actual-header regression checks.

Validation: 12 upload-window checks, 20 streaming regressions, actual API/health header capture, JavaScript regressions and PHP/Python syntax checks. A normal-identity ~949 MB SiteDistrict push completed with 131 API requests and no request errors. All 9,878 source media files and 15,325 code files matched destination hashes. Forty-three checked database tables matched the pinned snapshot; differences in two scheduler tables were tied to logged background execution and cleanup. Frontend health passed, three destination backups were retained, and recovery was idle.

Install the same version on both sites. Source snapshot preparation and final staging remain foreground PHP operations; host time/storage limits still apply. Very restrictive hosts can use the 512 KB option.