# synckit

End-to-end-encrypted sync: the client SDK and the local config store.

Extracted from the MNW monorepo (2026-07-24) so synckit can version and deploy
independently. Two standalone crates, no root workspace (each builds on its own,
matching the ecosystem convention):

- **`synckit-client`** — the sync SDK: transport, crypto, the declarative
  `SyncStore` engine over SQLite. Internal; consumed by path or git dependency,
  never published to crates.io.
- **`synckit-config`** — a local key/value settings store with per-key sync
  postures. The store half of portable config; usable with no network, so a
  no-sync consumer (a TUI remembering a theme) links it without the SDK. The
  sync adapter that turns a `ConfigSpec` into a `SyncTable` lives in
  `synckit-client` behind its `store` feature.

The synckit **server** still lives in the MNW server. Splitting it into a
standalone service on its own VPS is a separate, later effort — see the wiki
note `mnw-strategy-synckit-vps-separation`, triggered by the first external
developer.