Expose db change batches over control

docs/architecture.md

@@ -96,10 +96,10 @@ and file sync trees are future work.
 `geth-db` currently registers local SQLite paths as DB resources and reports
 local-only sync status plus a read-only SQLite schema summary/hash. It also
 inspects `crsql_changes` metadata when that table or view exists, reporting
-change count, columns, and max `db_version`. The crate can extract read-only
-typed change batches from `crsql_changes` with schema metadata for future sync
-messages. Loading cr-sqlite, applying remote changes, and DB sync are future
-work.
+change count, columns, and max `db_version`. The crate and local daemon can
+extract read-only typed change batches from `crsql_changes` with schema metadata
+through `db changes`. Loading cr-sqlite, applying remote changes, and DB sync
+are future work.
 
 `geth-kv` currently provides a SQLite-backed local fallback for named KV stores
 through `kv create/set/get`. Iroh Documents namespaces, prefix authorization

docs/roadmap.md

@@ -306,7 +306,7 @@ Automerge documents.
   - `geth db status <name>` reports local path, schema metadata, and sync state.
   - Nonexistent paths and invalid names produce clear errors.
 
-- `[ ]` cr-sqlite change extraction.
+- `[x]` cr-sqlite change extraction.
   Acceptance criteria:
   - `[x]` DB status detects whether `crsql_changes` exists.
   - `[x]` DB status reports `crsql_changes` row count, columns, and max
@@ -314,8 +314,7 @@ Automerge documents.
   - `[x]` Tests use a temp SQLite DB and deterministic fixture changes.
   - `[x]` The module can extract typed change batches from `crsql_changes`.
   - `[x]` Schema hash/version metadata is included in extracted change batches.
-  - `[ ]` Extracted batches are exposed through a daemon control command or sync
-    protocol.
+  - `[x]` Extracted batches are exposed through `geth db changes`.
 
 - `[ ]` DB sync over Iroh.
   Acceptance criteria: