@webority-technologies/mobile-core 0.0.6 → 0.0.8

package/lib/module/specs/NativeSmsRetriever.js

@@ -0,0 +1,13 @@
+"use strict";
+
+import { TurboModuleRegistry } from 'react-native';
+
+/**
+ * Android-only — the Play Services SMS Retriever API has no iOS equivalent.
+ * The JS wrapper in `smsRetriever/index.ts` never touches this module on
+ * iOS, so `getEnforcing` only ever runs on Android, where autolinking has
+ * registered `SmsRetrieverPackage`.
+ */
+
+export default TurboModuleRegistry.getEnforcing('WeborityMobileCoreSmsRetriever');
+//# sourceMappingURL=NativeSmsRetriever.js.map

package/lib/module/sqlite/index.js

@@ -5,40 +5,25 @@ import { Logger } from "../logger/index.js";
 import { adaptExpoSqlite } from "./adapters/expo.js";
 
 /**
- * This module names NO native package. Metro resolves requires statically, so a
- * driver named here would be bundled by every consumer and would have to be
- * installed by every app, whichever driver it actually chose. Each driver lives
- * behind its own import path, and the app wires one at startup:
- *
- *   import { setSqliteImplementation } from '@webority-technologies/mobile-core/sqlite';
- *   import { opSqliteDriver } from '@webority-technologies/mobile-core/sqlite/op';
- *   setSqliteImplementation(opSqliteDriver());
- *
- * Supported entry points: /sqlite/op, /sqlite/nitro, /sqlite/quick,
- * /sqlite/storage. Any object matching SqliteDriver also works.
+ * expo-sqlite is the fleet's only sanctioned SQLite driver (react-native.md:
+ * "we will always use expo-sqlite, what Expo gives, we don't look elsewhere
+ * ever") — this module resolves it automatically, with no app-side wiring.
+ * `setSqliteImplementation` still exists, narrowed to tests and the showcase:
+ * it injects a denying/failing backend to reach error paths a healthy device
+ * never takes, the same pattern every other injectable surface in this
+ * library follows. It is not a way to pick an alternate real driver.
  */
 
 /** Only what a test or an app injected; null means use expo-sqlite. */
 let backend = null;
 
-/**
- * expo-sqlite, adapted once and memoised.
- *
- * Unlike the other surfaces this one keeps a real reason to inject: an app with
- * an existing database on another driver (op-sqlite, nitro, quick,
- * sqlite-storage) can hand it over, and those entry points stay published for
- * exactly that. expo-sqlite is simply what happens when nobody does.
- */
+/** expo-sqlite, adapted once and memoised. The only driver this module resolves. */
 let expoDriver;
 
 /**
- * Inject the SQLite driver. Pass `null` to clear it.
- *
- * `@webority-technologies/mobile-core` ships no database: it is pure JavaScript
- * and defines only this interface. Wire a driver once at startup:
- *
- *   import { opSqliteDriver } from '@webority-technologies/mobile-core/sqlite/op';
- *   setSqliteImplementation(opSqliteDriver());
+ * Test/showcase-only injection point — see the module header. Not a way to
+ * pick an alternate real driver; `@webority-technologies/mobile-core` always
+ * resolves expo-sqlite when nothing is injected. Pass `null` to clear it.
  */
 export const setSqliteImplementation = impl => {
   backend = impl;
@@ -56,10 +41,7 @@ export const isSqliteAvailable = () => resolveDriver() !== null;
 const requireBackend = op => {
   const b = resolveDriver();
   if (!b) {
-    // Naming the SETTER and an import path, not just packages to install:
-    // installing a driver alone does nothing here, and the previous wording
-    // ("Install one of ...") sent people to fix a thing that was not broken.
-    const err = new Error(`[@webority-technologies/mobile-core] No SQLite driver injected; cannot ${op}. ` + 'Install a driver and wire it once at startup, e.g. ' + "`import { opSqliteDriver } from '@webority-technologies/mobile-core/sqlite/op'` " + 'then `setSqliteImplementation(opSqliteDriver())`. Drivers: @op-engineering/op-sqlite ' + '(recommended), expo-sqlite, react-native-nitro-sqlite, react-native-quick-sqlite, ' + 'react-native-sqlite-storage.');
+    const err = new Error(`[@webority-technologies/mobile-core] No SQLite driver available; cannot ${op}. ` + 'Install expo-sqlite (the only sanctioned driver) in the consuming app.');
     Logger.error(err.message);
     throw err;
   }

package/lib/typescript/commonjs/formatters/windowsToIanaTable.d.ts

@@ -0,0 +1,18 @@
+/**
+ * .NET-style Windows time zone ID → IANA time zone name, one entry per
+ * Windows zone, generated from CLDR's `windowsZones.xml` (the same
+ * upstream source the retired `windows-iana` npm package derived its own
+ * table from). Only the `territory="001"` (world-default) row is kept per
+ * Windows zone — `formatTimeInWindowsZone` only ever reads the first IANA
+ * candidate, and CLDR's `001` row is exactly that default candidate, so
+ * per-country territory variants (`US`, `CA`, `ZZ`, …) carry no information
+ * this table's one caller uses.
+ *
+ * Regenerate with `node packages/core/scripts/generate-windows-to-iana-table.mjs
+ * <path-to-windowsZones.xml>` (CLDR: `common/supplemental/windowsZones.xml` in
+ * https://github.com/unicode-org/cldr) whenever CLDR adds/renames a zone —
+ * this is a committed, static table; nothing fetches CLDR at build or test
+ * time.
+ */
+export declare const WINDOWS_TO_IANA: Readonly<Record<string, string>>;
+//# sourceMappingURL=windowsToIanaTable.d.ts.map

package/lib/typescript/commonjs/geolocation/index.d.ts

@@ -1,3 +1,4 @@
+import '../permissions/location';
 export interface GeoCoordinates {
     latitude: number;
     longitude: number;

package/lib/typescript/commonjs/index.d.ts

@@ -5,11 +5,12 @@
  * for anyone importing anything at all. Those live behind their own import
  * paths instead:
  *
- *   @webority-technologies/mobile-core/permissions  react-native-permissions
+ *   @webority-technologies/mobile-core/permissions  per kind, its own Expo module
  *   @webority-technologies/mobile-core/compressor   react-native-compressor
  *   @webority-technologies/mobile-core/geolocation  a geolocation provider
- *   @webority-technologies/mobile-core/sqlite       a SQLite driver
+ *   @webority-technologies/mobile-core/sqlite       expo-sqlite
  *   @webority-technologies/mobile-core/download     a filesystem module
+ *   @webority-technologies/mobile-core/smsRetriever Android only, own TurboModule
  *
  * react-native-keychain is the exception and is a REQUIRED peer: the HTTP client
  * reads the bearer token, so it is reachable from the main barrel by design.

package/lib/typescript/commonjs/permissions/calendar.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=calendar.d.ts.map

package/lib/typescript/commonjs/permissions/camera.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=camera.d.ts.map

package/lib/typescript/commonjs/permissions/contacts.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=contacts.d.ts.map

package/lib/typescript/commonjs/permissions/index.d.ts

@@ -1,46 +1,39 @@
 export type PermissionKind = 'camera' | 'microphone' | 'photos' | 'photosAdd' | 'mediaLibrary' | 'location' | 'locationAlways' | 'contacts' | 'calendar' | 'reminders' | 'notifications' | 'bluetooth' | 'storage';
 export type PermissionStatus = 'unavailable' | 'denied' | 'limited' | 'granted' | 'blocked';
-export interface RNPermissionsModule {
-    PERMISSIONS: {
-        IOS: Record<string, string>;
-        ANDROID: Record<string, string>;
-    };
-    RESULTS: {
-        UNAVAILABLE: string;
-        DENIED: string;
-        LIMITED: string;
-        GRANTED: string;
-        BLOCKED: string;
-    };
-    check: (permission: string) => Promise<string>;
-    request: (permission: string) => Promise<string>;
-    openSettings: () => Promise<void>;
+/** The shared response shape every Expo permission function returns. */
+interface ExpoPermissionResponse {
+    status: 'granted' | 'denied' | 'undetermined';
+    granted: boolean;
+    canAskAgain: boolean;
+    /** iOS partial photo access, from expo-image-picker's MediaLibraryPermissionResponse. */
+    accessPrivileges?: 'all' | 'limited' | 'none';
+}
+interface ExpoPermissionFns {
+    check: () => Promise<ExpoPermissionResponse>;
+    request: () => Promise<ExpoPermissionResponse>;
+}
+export interface PermissionsBackend {
+    check: (kind: PermissionKind) => Promise<PermissionStatus>;
+    request: (kind: PermissionKind) => Promise<PermissionStatus>;
 }
 /**
- * Inject a custom permissions implementation at runtime.
- * Pass `null` to reset to the default lazily-resolved native module.
- *
- * `resolved` goes FALSE on null, never true. Marking it resolved with a null
- * backend would permanently disable permissions: the resolver short-circuits and the
- * real module is never loaded again, which contradicts this function's own
- * documented contract. That exact bug shipped once, in the storage seam.
+ * Inject a custom permissions backend at runtime. Pass `null` to reset to the
+ * default per-kind Expo resolution.
  *
- * THIS MODULE IS THE EXPO-FIRST EXCEPTION, and deliberately keeps the old
- * shape. Expo ships no permissions package: each module carries its own
- * (expo-location's requestForegroundPermissionsAsync, expo-image-picker's, and
- * so on), so there is no single object to adapt and the library must not guess
- * which Expo modules an app installed. react-native-permissions stays, behind
- * this module's own import path so an app that never asks for permissions
- * never names the package to Metro.
+ * Two legitimate reasons to call this: tests/the showcase reaching a denied,
+ * blocked or unavailable path a healthy device never takes; and an app that
+ * genuinely needs `bluetooth` or `storage`, which no Expo module covers.
  */
-export declare const setPermissionsImplementation: (impl: RNPermissionsModule | null) => void;
+export declare const setPermissionsImplementation: (impl: PermissionsBackend | null) => void;
+/** Called by the per-package entry points to register their kind(s). Not for app code. */
+export declare const registerPermissionAdapter: (kind: PermissionKind, fns: ExpoPermissionFns) => void;
 /**
  * Cross-platform permissions wrapper. Maps an abstract `PermissionKind`
- * (camera, photos, location, notifications, …) to the right
- * iOS / Android permission string under the hood.
- *
- * Requires `react-native-permissions` as an optional peer dependency;
- * when missing, every check/request resolves to `'unavailable'`.
+ * (camera, photos, location, notifications, …) to whichever Expo adapter an
+ * app has registered by importing that kind's entry point — expo-camera,
+ * expo-image-picker, expo-location, expo-contacts, expo-calendar,
+ * expo-notifications, expo-media-library. An app imports only the entry
+ * points for the kinds it actually asks for.
  */
 export declare const Permissions: {
     check: (kind: PermissionKind) => Promise<PermissionStatus>;
@@ -51,5 +44,5 @@ export declare const Permissions: {
     ensure: (kind: PermissionKind) => Promise<PermissionStatus>;
     openSettings: () => Promise<boolean>;
 };
-export type { RNPermissionsModule as PermissionsLike };
+export {};
 //# sourceMappingURL=index.d.ts.map

package/lib/typescript/commonjs/permissions/location.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=location.d.ts.map

package/lib/typescript/commonjs/permissions/mediaLibrary.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=mediaLibrary.d.ts.map

package/lib/typescript/commonjs/permissions/notifications.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=notifications.d.ts.map

package/lib/typescript/commonjs/permissions/photos.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=photos.d.ts.map

package/lib/typescript/commonjs/smsRetriever/index.d.ts

@@ -0,0 +1,30 @@
+export interface SmsRetrieverError {
+    type: 'TIMEOUT' | 'SERVICE_UNAVAILABLE' | 'UNKNOWN_ERROR';
+    message: string;
+}
+export interface SmsListenerSubscription {
+    remove: () => void;
+}
+export interface SmsRetrieverBackend {
+    getAppHash: () => Promise<string>;
+    startListening: (onMessage: (message: string) => void, onError?: (error: SmsRetrieverError) => void) => SmsListenerSubscription;
+}
+/** Test-only injection point. Pass `null` to reset to the native module. */
+export declare const setSmsRetrieverImplementation: (impl: SmsRetrieverBackend | null) => void;
+/**
+ * The Play Services SMS Retriever API — auto-reads an incoming OTP SMS with
+ * no SMS permission, matched by an 11-character app-signature hash
+ * (`getAppHash`) the backend appends to the message. Android only; every
+ * method is safe to call on iOS and resolves/reports unavailable rather than
+ * throwing, so a caller doesn't need a platform check at every call site.
+ *
+ * OTP extraction is left to the caller — `onMessage` receives the raw SMS
+ * text, since the expected OTP format (digit count, prefix) is a backend
+ * concern, not this module's.
+ */
+export declare const SmsRetriever: {
+    isAvailable: () => boolean;
+    getAppHash: () => Promise<string>;
+    startListening: (onMessage: (message: string) => void, onError?: (error: SmsRetrieverError) => void) => SmsListenerSubscription;
+};
+//# sourceMappingURL=index.d.ts.map

package/lib/typescript/commonjs/specs/NativeSmsRetriever.d.ts

@@ -0,0 +1,15 @@
+import type { TurboModule } from 'react-native';
+/**
+ * Android-only — the Play Services SMS Retriever API has no iOS equivalent.
+ * The JS wrapper in `smsRetriever/index.ts` never touches this module on
+ * iOS, so `getEnforcing` only ever runs on Android, where autolinking has
+ * registered `SmsRetrieverPackage`.
+ */
+export interface Spec extends TurboModule {
+    startSMSListener(): void;
+    stopSMSListener(): void;
+    getAppHash(): Promise<string>;
+}
+declare const _default: Spec;
+export default _default;
+//# sourceMappingURL=NativeSmsRetriever.d.ts.map

package/lib/typescript/commonjs/sqlite/index.d.ts

@@ -1,15 +1,11 @@
 /**
- * This module names NO native package. Metro resolves requires statically, so a
- * driver named here would be bundled by every consumer and would have to be
- * installed by every app, whichever driver it actually chose. Each driver lives
- * behind its own import path, and the app wires one at startup:
- *
- *   import { setSqliteImplementation } from '@webority-technologies/mobile-core/sqlite';
- *   import { opSqliteDriver } from '@webority-technologies/mobile-core/sqlite/op';
- *   setSqliteImplementation(opSqliteDriver());
- *
- * Supported entry points: /sqlite/op, /sqlite/nitro, /sqlite/quick,
- * /sqlite/storage. Any object matching SqliteDriver also works.
+ * expo-sqlite is the fleet's only sanctioned SQLite driver (react-native.md:
+ * "we will always use expo-sqlite, what Expo gives, we don't look elsewhere
+ * ever") — this module resolves it automatically, with no app-side wiring.
+ * `setSqliteImplementation` still exists, narrowed to tests and the showcase:
+ * it injects a denying/failing backend to reach error paths a healthy device
+ * never takes, the same pattern every other injectable surface in this
+ * library follows. It is not a way to pick an alternate real driver.
  */
 export interface SqliteResultSet {
     rows: Record<string, unknown>[];
@@ -26,13 +22,9 @@ export interface SqliteDriver {
     }) => Promise<SqliteDatabase>;
 }
 /**
- * Inject the SQLite driver. Pass `null` to clear it.
- *
- * `@webority-technologies/mobile-core` ships no database: it is pure JavaScript
- * and defines only this interface. Wire a driver once at startup:
- *
- *   import { opSqliteDriver } from '@webority-technologies/mobile-core/sqlite/op';
- *   setSqliteImplementation(opSqliteDriver());
+ * Test/showcase-only injection point — see the module header. Not a way to
+ * pick an alternate real driver; `@webority-technologies/mobile-core` always
+ * resolves expo-sqlite when nothing is injected. Pass `null` to clear it.
  */
 export declare const setSqliteImplementation: (impl: SqliteDriver | null) => void;
 export declare const isSqliteAvailable: () => boolean;

package/lib/typescript/module/formatters/windowsToIanaTable.d.ts

@@ -0,0 +1,18 @@
+/**
+ * .NET-style Windows time zone ID → IANA time zone name, one entry per
+ * Windows zone, generated from CLDR's `windowsZones.xml` (the same
+ * upstream source the retired `windows-iana` npm package derived its own
+ * table from). Only the `territory="001"` (world-default) row is kept per
+ * Windows zone — `formatTimeInWindowsZone` only ever reads the first IANA
+ * candidate, and CLDR's `001` row is exactly that default candidate, so
+ * per-country territory variants (`US`, `CA`, `ZZ`, …) carry no information
+ * this table's one caller uses.
+ *
+ * Regenerate with `node packages/core/scripts/generate-windows-to-iana-table.mjs
+ * <path-to-windowsZones.xml>` (CLDR: `common/supplemental/windowsZones.xml` in
+ * https://github.com/unicode-org/cldr) whenever CLDR adds/renames a zone —
+ * this is a committed, static table; nothing fetches CLDR at build or test
+ * time.
+ */
+export declare const WINDOWS_TO_IANA: Readonly<Record<string, string>>;
+//# sourceMappingURL=windowsToIanaTable.d.ts.map

package/lib/typescript/module/geolocation/index.d.ts

@@ -1,3 +1,4 @@
+import '../permissions/location.js';
 export interface GeoCoordinates {
     latitude: number;
     longitude: number;

package/lib/typescript/module/index.d.ts

@@ -5,11 +5,12 @@
  * for anyone importing anything at all. Those live behind their own import
  * paths instead:
  *
- *   @webority-technologies/mobile-core/permissions  react-native-permissions
+ *   @webority-technologies/mobile-core/permissions  per kind, its own Expo module
  *   @webority-technologies/mobile-core/compressor   react-native-compressor
  *   @webority-technologies/mobile-core/geolocation  a geolocation provider
- *   @webority-technologies/mobile-core/sqlite       a SQLite driver
+ *   @webority-technologies/mobile-core/sqlite       expo-sqlite
  *   @webority-technologies/mobile-core/download     a filesystem module
+ *   @webority-technologies/mobile-core/smsRetriever Android only, own TurboModule
  *
  * react-native-keychain is the exception and is a REQUIRED peer: the HTTP client
  * reads the bearer token, so it is reachable from the main barrel by design.

package/lib/typescript/module/permissions/calendar.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=calendar.d.ts.map

package/lib/typescript/module/permissions/camera.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=camera.d.ts.map

package/lib/typescript/module/permissions/contacts.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=contacts.d.ts.map

package/lib/typescript/module/permissions/index.d.ts

@@ -1,46 +1,39 @@
 export type PermissionKind = 'camera' | 'microphone' | 'photos' | 'photosAdd' | 'mediaLibrary' | 'location' | 'locationAlways' | 'contacts' | 'calendar' | 'reminders' | 'notifications' | 'bluetooth' | 'storage';
 export type PermissionStatus = 'unavailable' | 'denied' | 'limited' | 'granted' | 'blocked';
-export interface RNPermissionsModule {
-    PERMISSIONS: {
-        IOS: Record<string, string>;
-        ANDROID: Record<string, string>;
-    };
-    RESULTS: {
-        UNAVAILABLE: string;
-        DENIED: string;
-        LIMITED: string;
-        GRANTED: string;
-        BLOCKED: string;
-    };
-    check: (permission: string) => Promise<string>;
-    request: (permission: string) => Promise<string>;
-    openSettings: () => Promise<void>;
+/** The shared response shape every Expo permission function returns. */
+interface ExpoPermissionResponse {
+    status: 'granted' | 'denied' | 'undetermined';
+    granted: boolean;
+    canAskAgain: boolean;
+    /** iOS partial photo access, from expo-image-picker's MediaLibraryPermissionResponse. */
+    accessPrivileges?: 'all' | 'limited' | 'none';
+}
+interface ExpoPermissionFns {
+    check: () => Promise<ExpoPermissionResponse>;
+    request: () => Promise<ExpoPermissionResponse>;
+}
+export interface PermissionsBackend {
+    check: (kind: PermissionKind) => Promise<PermissionStatus>;
+    request: (kind: PermissionKind) => Promise<PermissionStatus>;
 }
 /**
- * Inject a custom permissions implementation at runtime.
- * Pass `null` to reset to the default lazily-resolved native module.
- *
- * `resolved` goes FALSE on null, never true. Marking it resolved with a null
- * backend would permanently disable permissions: the resolver short-circuits and the
- * real module is never loaded again, which contradicts this function's own
- * documented contract. That exact bug shipped once, in the storage seam.
+ * Inject a custom permissions backend at runtime. Pass `null` to reset to the
+ * default per-kind Expo resolution.
  *
- * THIS MODULE IS THE EXPO-FIRST EXCEPTION, and deliberately keeps the old
- * shape. Expo ships no permissions package: each module carries its own
- * (expo-location's requestForegroundPermissionsAsync, expo-image-picker's, and
- * so on), so there is no single object to adapt and the library must not guess
- * which Expo modules an app installed. react-native-permissions stays, behind
- * this module's own import path so an app that never asks for permissions
- * never names the package to Metro.
+ * Two legitimate reasons to call this: tests/the showcase reaching a denied,
+ * blocked or unavailable path a healthy device never takes; and an app that
+ * genuinely needs `bluetooth` or `storage`, which no Expo module covers.
  */
-export declare const setPermissionsImplementation: (impl: RNPermissionsModule | null) => void;
+export declare const setPermissionsImplementation: (impl: PermissionsBackend | null) => void;
+/** Called by the per-package entry points to register their kind(s). Not for app code. */
+export declare const registerPermissionAdapter: (kind: PermissionKind, fns: ExpoPermissionFns) => void;
 /**
  * Cross-platform permissions wrapper. Maps an abstract `PermissionKind`
- * (camera, photos, location, notifications, …) to the right
- * iOS / Android permission string under the hood.
- *
- * Requires `react-native-permissions` as an optional peer dependency;
- * when missing, every check/request resolves to `'unavailable'`.
+ * (camera, photos, location, notifications, …) to whichever Expo adapter an
+ * app has registered by importing that kind's entry point — expo-camera,
+ * expo-image-picker, expo-location, expo-contacts, expo-calendar,
+ * expo-notifications, expo-media-library. An app imports only the entry
+ * points for the kinds it actually asks for.
  */
 export declare const Permissions: {
     check: (kind: PermissionKind) => Promise<PermissionStatus>;
@@ -51,5 +44,5 @@ export declare const Permissions: {
     ensure: (kind: PermissionKind) => Promise<PermissionStatus>;
     openSettings: () => Promise<boolean>;
 };
-export type { RNPermissionsModule as PermissionsLike };
+export {};
 //# sourceMappingURL=index.d.ts.map

package/lib/typescript/module/permissions/location.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=location.d.ts.map

package/lib/typescript/module/permissions/mediaLibrary.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=mediaLibrary.d.ts.map

package/lib/typescript/module/permissions/notifications.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=notifications.d.ts.map

package/lib/typescript/module/permissions/photos.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=photos.d.ts.map

package/lib/typescript/module/smsRetriever/index.d.ts

@@ -0,0 +1,30 @@
+export interface SmsRetrieverError {
+    type: 'TIMEOUT' | 'SERVICE_UNAVAILABLE' | 'UNKNOWN_ERROR';
+    message: string;
+}
+export interface SmsListenerSubscription {
+    remove: () => void;
+}
+export interface SmsRetrieverBackend {
+    getAppHash: () => Promise<string>;
+    startListening: (onMessage: (message: string) => void, onError?: (error: SmsRetrieverError) => void) => SmsListenerSubscription;
+}
+/** Test-only injection point. Pass `null` to reset to the native module. */
+export declare const setSmsRetrieverImplementation: (impl: SmsRetrieverBackend | null) => void;
+/**
+ * The Play Services SMS Retriever API — auto-reads an incoming OTP SMS with
+ * no SMS permission, matched by an 11-character app-signature hash
+ * (`getAppHash`) the backend appends to the message. Android only; every
+ * method is safe to call on iOS and resolves/reports unavailable rather than
+ * throwing, so a caller doesn't need a platform check at every call site.
+ *
+ * OTP extraction is left to the caller — `onMessage` receives the raw SMS
+ * text, since the expected OTP format (digit count, prefix) is a backend
+ * concern, not this module's.
+ */
+export declare const SmsRetriever: {
+    isAvailable: () => boolean;
+    getAppHash: () => Promise<string>;
+    startListening: (onMessage: (message: string) => void, onError?: (error: SmsRetrieverError) => void) => SmsListenerSubscription;
+};
+//# sourceMappingURL=index.d.ts.map

package/lib/typescript/module/specs/NativeSmsRetriever.d.ts

@@ -0,0 +1,15 @@
+import type { TurboModule } from 'react-native';
+/**
+ * Android-only — the Play Services SMS Retriever API has no iOS equivalent.
+ * The JS wrapper in `smsRetriever/index.ts` never touches this module on
+ * iOS, so `getEnforcing` only ever runs on Android, where autolinking has
+ * registered `SmsRetrieverPackage`.
+ */
+export interface Spec extends TurboModule {
+    startSMSListener(): void;
+    stopSMSListener(): void;
+    getAppHash(): Promise<string>;
+}
+declare const _default: Spec;
+export default _default;
+//# sourceMappingURL=NativeSmsRetriever.d.ts.map

package/lib/typescript/module/sqlite/index.d.ts

@@ -1,15 +1,11 @@
 /**
- * This module names NO native package. Metro resolves requires statically, so a
- * driver named here would be bundled by every consumer and would have to be
- * installed by every app, whichever driver it actually chose. Each driver lives
- * behind its own import path, and the app wires one at startup:
- *
- *   import { setSqliteImplementation } from '@webority-technologies/mobile-core/sqlite';
- *   import { opSqliteDriver } from '@webority-technologies/mobile-core/sqlite/op';
- *   setSqliteImplementation(opSqliteDriver());
- *
- * Supported entry points: /sqlite/op, /sqlite/nitro, /sqlite/quick,
- * /sqlite/storage. Any object matching SqliteDriver also works.
+ * expo-sqlite is the fleet's only sanctioned SQLite driver (react-native.md:
+ * "we will always use expo-sqlite, what Expo gives, we don't look elsewhere
+ * ever") — this module resolves it automatically, with no app-side wiring.
+ * `setSqliteImplementation` still exists, narrowed to tests and the showcase:
+ * it injects a denying/failing backend to reach error paths a healthy device
+ * never takes, the same pattern every other injectable surface in this
+ * library follows. It is not a way to pick an alternate real driver.
  */
 export interface SqliteResultSet {
     rows: Record<string, unknown>[];
@@ -26,13 +22,9 @@ export interface SqliteDriver {
     }) => Promise<SqliteDatabase>;
 }
 /**
- * Inject the SQLite driver. Pass `null` to clear it.
- *
- * `@webority-technologies/mobile-core` ships no database: it is pure JavaScript
- * and defines only this interface. Wire a driver once at startup:
- *
- *   import { opSqliteDriver } from '@webority-technologies/mobile-core/sqlite/op';
- *   setSqliteImplementation(opSqliteDriver());
+ * Test/showcase-only injection point — see the module header. Not a way to
+ * pick an alternate real driver; `@webority-technologies/mobile-core` always
+ * resolves expo-sqlite when nothing is injected. Pass `null` to clear it.
  */
 export declare const setSqliteImplementation: (impl: SqliteDriver | null) => void;
 export declare const isSqliteAvailable: () => boolean;