Why must the final Kaspa node sync be coordinated with the source node operator?

The very last rsync run must happen only after the source node has been deliberately stopped. A running node continuously writes new data to disk, so any copy taken while it is live may capture files mid-write and produce an inconsistent database. By stopping the source node first, all pending data is flushed to disk in a clean state, and the final rsync copies a snapshot that is guaranteed to be consistent. For someone setting up a Kaspa node by copying an existing one, skipping this coordination step risks starting with a corrupted database that causes sync or validation errors.