Exchange DB changes over Iroh

docs/roadmap.md

@@ -376,11 +376,25 @@ Automerge documents.
   - `[x]` Schema hash/version metadata is included in extracted change batches.
   - `[x]` Extracted batches are exposed through `geth db changes`.
 
-- `[ ]` DB sync over Iroh.
+- `[~]` DB sync over Iroh.
   Acceptance criteria:
-  - Two local test nodes can exchange and apply DB changes.
-  - Schema mismatch is detected before applying changes.
-  - Optional CAS-backed snapshots or batches are documented if used.
+  - `[x]` `geth db sync <node-id> <name>` exists and talks to the daemon.
+  - `[x]` Remote DB sync uses the protected Iroh control ALPN.
+  - `[x]` The serving peer validates the caller's signed peer card against the
+    observed Iroh EndpointID before considering authorization.
+  - `[x]` Remote DB sync requires `db.sync` on the remote
+    `resource:db:<name>`.
+  - `[x]` The response carries typed `crsql_changes` batches plus schema
+    metadata.
+  - `[x]` The requester detects schema mismatch before advancing the sync
+    cursor.
+  - `[x]` Background live-sync runs DB sync for local DB resources and known
+    peers.
+  - `[x]` Per-peer/per-DB high-water cursors are stored in `module_state`.
+  - `[ ]` Apply compatible remote changes through cr-sqlite.
+  - `[ ]` Add an integration test with a real cr-sqlite-enabled SQLite DB that
+    proves two local test nodes exchange and apply changes.
+  - `[ ]` Optional CAS-backed snapshots or batches are documented if used.
 
 - `[~]` Automerge document resource.
   Acceptance criteria: