Document DB sync prototype scope

This commit is contained in:
Eric Wendland 2026-05-22 14:55:31 +02:00
commit 59c86aba6a
4 changed files with 40 additions and 14 deletions

View file

@ -292,7 +292,11 @@ background live-sync require `db.sync` on `resource:db:<name>`, exchange typed
schema metadata against the local DB before applying and advancing the per-peer
cursor. Compatible batches are inserted into the local `crsql_changes` table or
view; for real cr-sqlite databases, loading/configuring cr-sqlite remains the
database owner's responsibility.
database owner's responsibility. The prototype does not use CAS-backed DB
snapshots or change-batch blobs; that is deferred until large initial catch-up
needs it. The automated tests use deterministic `crsql_changes` fixtures because
this dev environment does not provide a `sqlite3` CLI or cr-sqlite extension
artifact for a real extension-backed integration test.
Importing or pinging a peer card never grants capabilities by itself.
When `[iroh].local_discovery = true`, the daemon also advertises and discovers
signed peer cards on LAN using a geth-specific mDNS TXT payload. That payload is