@syncular/tauri 0.59.0 → 0.60.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -73,13 +73,13 @@ The bridge also exposes `purgeLocalData({ purgeId, targets })` with the same
73
73
  idempotent transaction as the browser worker: exact synced-row and generated
74
74
  FTS deletion, whole-commit outbox rejection, optimistic replay, blob-reference
75
75
  reconciliation, and counts-only acknowledgement. The app remains responsible
76
- for validating the server-authoritative directive, gating subscriptions before
76
+ for validating the server-authoritative directive, gating units before
77
77
  the purge, deleting app-owned drafts/files, and removing the corresponding key
78
78
  from the OS secure store after SQLite cleanup succeeds.
79
79
 
80
80
  For support-directed projection recovery, the bridge also exposes
81
81
  `rebootstrapLocalData({ rebootstrapId })`. It atomically recreates only synced
82
- projection tables, rewinds retained subscriptions, replays the complete
82
+ projection tables, rewinds every registered unit, replays the complete
83
83
  outbox, and requests a fresh bootstrap while preserving device identity,
84
84
  lease state, outcomes, and protected bookkeeping. The result contains only
85
85
  `alreadyApplied`, `retainedCommits`, and `resetSubscriptions`. It is blocked
@@ -157,7 +157,7 @@ opening a socket.
157
157
  Create with `securityPreflight: true` when authentication, signed device
158
158
  quarantine, or crash-resumed cleanup must finish before clinical data is
159
159
  available. The native database opens and migrates, but query/snapshot, mutation,
160
- subscription, sync, realtime, presence, blob, and automatic retry work fails
160
+ unit registration, sync, realtime, presence, blob, and automatic retry work fails
161
161
  with `client.security_preflight_required`. Status, local revision, lifecycle,
162
162
  and `purgeLocalData` remain available. A creation-time `defineAuthorityReads`
163
163
  policy on `createTauriAuthoritySyncClient` enables the read-only
@@ -240,15 +240,15 @@ still fail with `client.security_preflight_required`.
240
240
  The result contains `revision: bigint`, `complete`, and `tables`. Every table
241
241
  contains accepted `rows` (`values`, server `version`, `hasLocalIntent`), scoped
242
242
  `localIntentRowIds`, the declared `scopes`, `coverage`, and sanitized
243
- `persisted` subscription evidence (`requestedScopes`, `effectiveScopes`,
244
- `cursor`, `status`, `complete`). It exposes no intended values, bootstrap
245
- tokens, subscription parameters or keys. Both cores read rows, revision and
243
+ `persisted` unit evidence (`requestedScopes`, `effectiveScopes`, `cursor`,
244
+ `status`, `complete`). It exposes no intended values, bootstrap tokens or
245
+ keys. Both cores read rows, revision and
246
246
  coverage in one SQLite snapshot. The native authority read runs on the mutable
247
247
  owner; it does not use the ordinary query sidecar or its latency contract.
248
248
 
249
249
  `coverage` is `complete`, `pending` or `missing`. Complete coverage requires
250
- completed unfiltered subscriptions for every requested scope tuple. Several
251
- subscriptions can cover the selection together. Scope loss and an unfinished
250
+ a completed unit for every requested scope tuple. Several units can cover the
251
+ selection together. Scope loss and an unfinished
252
252
  bootstrap invalidate completeness. Completed empty coverage has an empty row
253
253
  set. The application must reject admission when an expected authority row is
254
254
  absent, even when the set is complete.
@@ -258,7 +258,7 @@ A local-only creation appears only in `localIntentRowIds`. The application
258
258
  validates the complete chain against independently accepted authority evidence,
259
259
  actor/device identity, signed lease and trusted time before installing keys.
260
260
  The SDK does not authorize the application. The read changes no lifecycle,
261
- transport, keyring, subscriptions or rows.
261
+ transport, keyring, units or rows.
262
262
 
263
263
  The direct Bun/SQLite client and worker handle expose the same policy and
264
264
  snapshot shape. Importing the policy is opt-in; ordinary clients do not ship
@@ -266,17 +266,17 @@ its reader. Update npm packages and native crates together and rebuild the app.
266
266
 
267
267
  ## Privacy-safe diagnostics
268
268
 
269
- `diagnosticsSnapshot({ expectedSubscriptions })` and `onDiagnostics(listener)`
270
- carry the native Rust core's versioned support evidence through the Tauri event
271
- channel. The bridge marks the host as `{ kind: 'tauri', role: 'single' }`; it
272
- does not infer state from IPC commands. Expected subscriptions accept only
273
- stable PHI-free ids and generated table names, never scope values.
269
+ `diagnosticsSnapshot()` and `onDiagnostics(listener)` carry the native Rust
270
+ core's version 2 support evidence through the Tauri event channel: registered
271
+ units counted per state (`units`), `activeUnits` and the `replicaCursor`. A unit
272
+ id never enters the snapshot. The bridge marks the host as
273
+ `{ kind: 'tauri', role: 'single' }`; it does not infer state from IPC commands.
274
274
 
275
275
  The snapshot is suitable for a redacted “copy diagnostics” workflow: it omits
276
276
  rows, clinical row counts, scopes, SQL, paths, client/actor/lease ids, auth,
277
277
  keys, mutations, stack traces, and arbitrary prose. Do not supplement it with
278
278
  the SQLite file, WebView console dump, or application state. Diagnostics stays
279
- blocked during security preflight because subscription/table evidence is
279
+ blocked during security preflight because unit and table evidence is
280
280
  protected. See SPEC §7.6 and `@syncular/react`'s `useDiagnostics`.
281
281
 
282
282
  ## React availability guard
package/dist/remote.d.ts CHANGED
@@ -25,8 +25,8 @@ import { NativeBridgeClient, type NativeCreateConfig, type NativeReply, NativeSy
25
25
  export type { BytesEnvelope } from '@syncular/client/native-bridge';
26
26
  /** §7.5: one read-only statement in an atomic sidecar snapshot read. */
27
27
  export type { SnapshotStatement } from '@syncular/client';
28
- /** §7.5: the catch-up state of one subscription from the sidecar. */
29
- export type { SubscriptionCatchup } from '@syncular/client';
28
+ /** §7.5: the catch-up state of one unit from the sidecar. */
29
+ export type { UnitCatchup } from '@syncular/client';
30
30
  /** §7.5: delivery status for one client commit id. */
31
31
  export type { CommitDelivery } from '@syncular/client';
32
32
  /** §7.5: one atomic sidecar snapshot read result with decoded rows. */
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@syncular/tauri",
3
- "version": "0.59.0",
3
+ "version": "0.60.0",
4
4
  "description": "Tauri integration for the Syncular client",
5
5
  "license": "Apache-2.0",
6
6
  "author": "Benjamin Kniffler",
@@ -64,13 +64,13 @@
64
64
  "test": "bun test"
65
65
  },
66
66
  "dependencies": {
67
- "@syncular/client": "0.59.0"
67
+ "@syncular/client": "0.60.0"
68
68
  },
69
69
  "peerDependencies": {
70
70
  "@tauri-apps/api": ">=2.0.0"
71
71
  },
72
72
  "devDependencies": {
73
- "@syncular/react": "0.59.0",
74
- "@syncular/server": "0.59.0"
73
+ "@syncular/react": "0.60.0",
74
+ "@syncular/server": "0.60.0"
75
75
  }
76
76
  }
package/src/remote.ts CHANGED
@@ -40,8 +40,8 @@ export type { BytesEnvelope } from '@syncular/client/native-bridge';
40
40
  /** §7.5: one read-only statement in an atomic sidecar snapshot read. */
41
41
  export type { SnapshotStatement } from '@syncular/client';
42
42
 
43
- /** §7.5: the catch-up state of one subscription from the sidecar. */
44
- export type { SubscriptionCatchup } from '@syncular/client';
43
+ /** §7.5: the catch-up state of one unit from the sidecar. */
44
+ export type { UnitCatchup } from '@syncular/client';
45
45
 
46
46
  /** §7.5: delivery status for one client commit id. */
47
47
  export type { CommitDelivery } from '@syncular/client';