Stop the media seed from holding the onboard, and therefore the partnership, open for weeks

A first seed is ~28 TB behind a 12.5 MB/s bwlimit, and it ran inline as Step 9d, so the phase-2 flag every status reader depends on was written only after it finished.
2026-08-17 07:40:00 -04:00
parent 9d2610a911
commit ad623353bc
6 changed files with 466 additions and 61 deletions
@@ -104,6 +104,12 @@ For full profile definitions see `Manual-Rsync.md`.
 | Script | Role | When It Runs |
 |--------|------|-------------|
 | `rsync.sh` | Core transfer engine — profile resolution, pre-flights, container management, transfer, bandwidth logging | Called by orchestrators; directly for manual syncs |
+| `media_seed.sh` | First-fill of a new partner — loops every `DAILY_SYNC_SHARES` entry through `rsync.sh --seed` | Dispatched detached by partnership onboard Step 13; restartable from the Partnership tab |
+
+`media_seed.sh` is the one script here that is expected to run for weeks. A first seed of
+HOST1's library is ~28 TB against a 12.5 MB/s `--bwlimit`, which is why onboard dispatches it
+rather than waiting on it, and why the Partnership tab gives it a Stop button — `rsync.sh` runs
+`--inplace --partial`, so stopping costs the file in flight, not the share.

 ---