iCloud Drive sync

○ planned

When you opt in, let iCloud carry your SQLly setup between Macs without routing it through us.

Turn it on and your SQLly setup can follow you to each Mac you use: configuration, customization, and your connection list travel through Apple's sync, not ours. Sit down at another Mac and your workspace is ready the way you left it; we never see the data.

// Preferences › iCloud
Sync via iCloud Drive   [ off ]
↳ stores everything locally only

What travels, and what does not

	Item
Travels	Connections and their clients, projects, and environments; colors and cues; safety policy; keybindings; snippets; formatting and IntelliSense rules.
Stays put	Passwords and tokens - they live in each Mac's own Keychain, and the synced files only reference them. Also machine-local things with no meaning elsewhere: temporary result spill files, caches, and window state.

So a synced connection arrives complete except for its secret, which that Mac's Keychain supplies (or asks you for once). This is the point rather than a limitation: your connection list is not a credential file, so syncing it is not syncing your credentials.

Off means off. Flip it off and the files never leave the machine - there is no half-on state and no background upload waiting for you to change your mind.

Two Macs, one folder

iCloud Drive resolves conflicts at the file level, which suits SQLly's one-file-per-concern layout: editing keybindings on one Mac and a connection on another touches different files and merges cleanly. Editing the same file on two Macs at once is the case where iCloud keeps both versions - the same thing it does for any document, and the reason the settings are small separate files rather than one large one.

Planned. Everything it depends on already ships - see Everything is a file - and in the meantime any file-sync tool pointed at the SQLLY folder does the same job today.