You'll notice
File sync now refuses to push files into its own reserved .ccr-seed directory
What
A new guard rejects any file-sync push whose path is, or is inside, the .ccr-seed directory, which is reserved for sync's own internal use. This is checked when pushing a synced file, when re-fetching a seed, and when scanning for changed files, and a rejection is logged with the reason lane_path_reserved.
Why
This prevents file sync from accidentally overwriting or interfering with its own internal state, which could otherwise corrupt the sync mechanism itself.