Exit codes

read and write keep going after a problem so one bad entry doesn't hide the rest, then report it in the exit status. CI can rely on $?: a green step means every configured file is in sync.

Exit	Meaning
0	Everything configured was synced.
1	The run finished but something is out of sync, or it couldn't start (missing tooling, no session, bad config, unknown vault argument).

Failing the run: a document that can't be fetched, uploaded, resolved (duplicate items), or listed; a configured file with no document in the vault; a vault you can't access; a stored path rejected by the safety gate; an upload whose path field couldn't be stamped.

Not failing the run: a pattern that matches nothing (on either side — patterns describe "whatever is there"), and a configured file that doesn't exist locally when you write.