beagle-turso 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f17107643c1060a1ed9f07307e780363f00197430168196cd0df08bf21ad494e
-  data.tar.gz: edc64897b8050f9bd2af1427cec29f8aed148461e4309180ac4647f2ac6ed35e
+  metadata.gz: f35de8fc3b33e04d7d170ee1032ee2d57af85642fcec1b120d591700baa9532c
+  data.tar.gz: 67bbe8aaa50468fb2cf0ef2c44e208fd414c4dff3694e9ae2a8dc8394ae671b7
 SHA512:
-  metadata.gz: df0e9d7fa56baa131741c48a6e2e035ba6c5d34b97f4902efb1c5e9dda028f724ca26506889cec6e991bd2ae19e0924a1501718f753b15f4c53b4cda6f57c5ab
-  data.tar.gz: f8509436bbc8df56a34fab0cbaad3bf18e0be2e772ed99dcc728b8d8f62c2e0dc5fd80a15479c3ba42a0e108a9b78278b2fa9837d75459ceee72f79dd34e679d
+  metadata.gz: ce2cef361285eed71718e587fbbe3a1a3d321e2e45ba269b1274edbbc622d073a0b55274ea2950e89e67eafeaceb70a0f3e469e0bd0bf29b59ac2ffedc205095
+  data.tar.gz: edd3d0df3ce5ba628e4ca6923c9df228c9f480d9a05ba4bf879f95a599adeed5d362f38f10b8621ee1d0fa01a0ca07ae1a69e9b85065c0fd089b59e3510706be

data/README.md

@@ -79,6 +79,30 @@ called; `push` is not called automatically after every write. Until a
 `push` succeeds, a write that's durable locally is not yet visible to other
 replicas of the same remote database.
 
+## Which Turso database?
+
+Point a synced database at a Turso database **dedicated to this engine** —
+ideally a fresh, empty one. On first open of an empty local replica,
+`bootstrap_if_empty` pulls the remote down; against a fresh remote that's a
+clean start, and the engine then manages its own state in that database (it
+creates `turso_cdc`, `__turso_internal_*`, and `turso_sync_last_change_id`
+tables and takes an **exclusive lock** on the local replica file — only one
+OS process may hold a given replica open at a time).
+
+Two things to avoid:
+
+- **Don't co-host a synced database with the legacy libSQL/Hrana driver.**
+  This engine (Turso's newer Rust core) and the classic libSQL client have
+  different write/sync models; running both against the same remote database
+  at once risks corrupting its sync state. Give this engine its own database.
+- **Migrating an existing, populated libSQL database into the synced engine
+  is not validated.** A fresh database is the supported, tested path. If you
+  must adopt existing data, treat it as unproven — test push/pull round-trips
+  before relying on it.
+
+A single remote database, dedicated to this engine and written by one process
+at a time, is the model it's built for.
+
 ## Credential safety
 
 `auth_token` is never included in `inspect` output or in error messages —

data/ext/beagle_turso/Cargo.toml

@@ -9,4 +9,4 @@ crate-type = ["cdylib"]
 
 [dependencies]
 magnus = "0.8"
-beagle_turso_core = "0.1.0"
+beagle_turso_core = "0.1.3"

data/lib/beagle/turso/version.rb

@@ -1,5 +1,5 @@
 module Beagle
   module Turso
-    VERSION = "0.1.2"
+    VERSION = "0.1.3"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: beagle-turso
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - BeagleSoftwareUK
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-08-08 00:00:00.000000000 Z
+date: 2026-08-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rb_sys