snapback4-expo 0.2.0 → 0.2.1

package/README.md

@@ -11,8 +11,6 @@ import { createLocalClient } from "snapback4/local";
 import { createClient } from "snapback4/client";
 import { nativeAvailable, nativeDevice } from "snapback4-expo";
 
-const safe = (name: string) => name.replace(/[^A-Za-z0-9._-]/g, "_");   // store and session names carry the URL and the viewer
-const sqliteStore = { open: async (name: string, schema: unknown) => openSqlite(expoSqliteDriver(await SQLite.openDatabaseAsync(`${safe(name)}.db`)), schema) };
 const client = nativeAvailable()
   ? await createLocalClient({ url, guest: true, sessionStore, device: nativeDevice })
   : createClient({ url, session });   // Expo Go: the online tier, with a session the app keeps
@@ -27,11 +25,13 @@ Expo Go loads no custom native code, so the module is present only in a
 development or production build: add `expo-dev-client`, then
 `npx expo run:ios` (the module autolinks; nothing to configure). The
 Rust library ships in the package as `ios/Snapback4Device.xcframework`
-(9.1 MB, a 4.8 MB archive a slice, built by `scripts/build-xcframework.sh`
-from `crates/snapback4-device`); it costs an app 1.7 MB linked, SQLite
-included, and a module call takes about a millisecond.
+(about 13.2 MB in 0.2.1, a 6.6 MB archive per slice, built by
+`scripts/build-xcframework.sh` from `crates/snapback4-device`). It includes
+SQLite and the native-query Wasm host. The earlier module measured 1.7 MB
+linked and about a millisecond per call; those measurements predate the
+native-query host.
 
-Proved on the iOS simulator by the repository's witness in a development
+Earlier iOS simulator evidence from the repository's witness in a development
 build (`WITNESS_DEV_CLIENT=1 node witness/expo.mjs`, recorded in
 `metrics/witness.jsonl` as `dev-client-native`): a cold sync of 303 rows
 in 31 ms, a reopen in 6 ms, a cold start with no network answering the

package/ios/Snapback4Device.xcframework/ios-arm64/Headers/snapback4.h

@@ -9,9 +9,13 @@
  * Ops: state, adopt {backend}, apply {page, first}, query {name, viewer, args, now},
  * predict {name, viewer, args, now, newIds, entropy}, withdraw {predicted},
  * enqueue {entry}, queued, next_submission, dequeue {id}, meta {key},
- * set_meta {key, value}, clear_rows. Nothing panics across this boundary;
- * every answer is JSON the caller frees. A device is not thread-safe: one
- * caller at a time, as the store is one transaction at a time.
+ * set_meta {key, value}, clear_rows. Nothing unwinds across this boundary:
+ * unwind builds translate an internal panic to E_STORE; production uses
+ * panic=abort and terminates before unwinding. Every answer is JSON the
+ * caller frees. A device is not thread-safe: one caller at a time, as the
+ * store is one transaction at a time.
+ * `apply.first` must be true on the first page of a snapshot. It defaults
+ * to false so an omitted marker cannot discard a snapshot already staged.
  */
 #ifndef SNAPBACK4_H
 #define SNAPBACK4_H
@@ -26,7 +30,10 @@ typedef struct sb4_device sb4_device;
  * (ask `sb4_open_reason` why). */
 sb4_device *sb4_open(const char *path, const char *backend_json);
 
-/* Why `sb4_open` would refuse, as JSON to free: {"ok":true} when it would open. */
+/* Take the refusal recorded by the most recent failed `sb4_open` on this
+ * thread, as JSON to free. This diagnoses that attempt without opening or
+ * mutating the store a second time. The arguments are retained for ABI
+ * compatibility. */
 char *sb4_open_reason(const char *path, const char *backend_json);
 
 /* One call; the answer is JSON to free with `sb4_free`. */

package/ios/Snapback4Device.xcframework/ios-arm64-simulator/Headers/snapback4.h

@@ -9,9 +9,13 @@
  * Ops: state, adopt {backend}, apply {page, first}, query {name, viewer, args, now},
  * predict {name, viewer, args, now, newIds, entropy}, withdraw {predicted},
  * enqueue {entry}, queued, next_submission, dequeue {id}, meta {key},
- * set_meta {key, value}, clear_rows. Nothing panics across this boundary;
- * every answer is JSON the caller frees. A device is not thread-safe: one
- * caller at a time, as the store is one transaction at a time.
+ * set_meta {key, value}, clear_rows. Nothing unwinds across this boundary:
+ * unwind builds translate an internal panic to E_STORE; production uses
+ * panic=abort and terminates before unwinding. Every answer is JSON the
+ * caller frees. A device is not thread-safe: one caller at a time, as the
+ * store is one transaction at a time.
+ * `apply.first` must be true on the first page of a snapshot. It defaults
+ * to false so an omitted marker cannot discard a snapshot already staged.
  */
 #ifndef SNAPBACK4_H
 #define SNAPBACK4_H
@@ -26,7 +30,10 @@ typedef struct sb4_device sb4_device;
  * (ask `sb4_open_reason` why). */
 sb4_device *sb4_open(const char *path, const char *backend_json);
 
-/* Why `sb4_open` would refuse, as JSON to free: {"ok":true} when it would open. */
+/* Take the refusal recorded by the most recent failed `sb4_open` on this
+ * thread, as JSON to free. This diagnoses that attempt without opening or
+ * mutating the store a second time. The arguments are retained for ABI
+ * compatibility. */
 char *sb4_open_reason(const char *path, const char *backend_json);
 
 /* One call; the answer is JSON to free with `sb4_free`. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "snapback4-expo",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "type": "module",
   "description": "Snapback 4's native module for Expo: the device in Rust (the partition in its own SQLite, the stream applied, the outbox kept, queries and predictions answered) behind one JSON call, and the opener `snapback4/native` takes.",
   "main": "src/index.ts",