@gemmein/sdk 0.8.0 → 0.10.0

package/migrations/README.md

@@ -33,3 +33,5 @@ the same surface gets its own file.
 | File | Since | Action required by |
 |------|-------|--------------------|
 | [`list-limit-refusal.md`](./list-limit-refusal.md) | 0.6.0 | 0.6.0 |
+| [`raw-calls-off.md`](./raw-calls-off.md) | 0.9.0 | 0.9.0 |
+| [`secure-store-set-throws.md`](./secure-store-set-throws.md) | 0.10.0 | 0.10.0 |

package/migrations/raw-calls-off.md

@@ -0,0 +1,51 @@
+# Raw AI calls are off until the owner switches them on
+
+```
+Since: 0.9.0
+Action required by: 0.9.0
+```
+
+## What changed
+
+Before 0.9.0 `g.ai.chat(body)` and `g.ai.text(body)` forwarded the
+provider request the browser composed to any provider the owner had a key
+for. From 0.9.0 that raw call is refused with `403 raw_calls_off` unless the
+owner has switched raw calls on for that provider's key on the AI tools
+page. The cloud applies this to every key, new and existing, from 7 Sep
+2026; the local engine (`gemmein dev`) keeps its keyless fake provider open
+and applies the same rule to a configured key.
+
+The normal path is a named tool: the owner defines it on the AI tools page
+or your AI writes `gemmein/ai/tools/<name>.json` (instructions, prompt
+template, typed inputs, model, caps) and the app calls it with inputs only.
+
+## Who is affected
+
+Apps that call `g.ai.chat` or `g.ai.text` without `tool`, or with a `tool`
+that only prices and gates a browser-composed body. An app that already
+calls `g.ai.run` / `g.ai.runText`, or makes no AI calls, sees no
+difference.
+
+## What to do
+
+Move each call to a named tool. The prompt leaves the browser and lives on
+the tool:
+
+```ts
+// before
+const res = await g.ai.chat({ model: "gpt-4o-mini", messages: [{ role: "user", content: `Summarise: ${text}` }] });
+
+// after — gemmein/ai/tools/summarise.json carries the instructions and
+// "promptTemplate": "Summarise: {{text}}", "inputs": [{ "name": "text", "type": "text", "required": true }]
+const res = await g.ai.run("summarise", { text });
+const answer = await g.ai.runText("summarise", { text });
+```
+
+An owner who wants the raw path back switches raw calls on for that
+provider's key on the AI tools page; the switch is per key and audited.
+
+## How to tell
+
+A 403 with `code: "raw_calls_off"` in the response, `err.code ===
+"raw_calls_off"` in the SDK, and the message naming the provider and the
+switch. On the AI calls record the outcome is `refused` with that reason.

package/migrations/secure-store-set-throws.md

@@ -0,0 +1,75 @@
+# A token store that cannot keep the session says so
+
+```
+Since: 0.10.0
+Action required by: 0.10.0
+```
+
+## What changed
+
+Before 0.10.0 a token store that could not write swallowed the failure.
+`auth.verifyEmailCode()` resolved, the app believed it was signed in, and the
+session was gone on the next read — the app reported itself signed out with
+nothing anywhere saying why.
+
+From 0.10.0 `tokenStore.set()` THROWS a `GemmeinError` with code
+`secure_store_unavailable` (status 0) when the store refuses the write, and
+`auth.verifyEmailCode()` carries it to the caller. The law is all three
+stores:
+
+- `SecureStoreTokenStore` (`@gemmein/sdk/expo`) — `expo-secure-store` missing
+  or refusing (an unsigned simulator build has no keychain access group).
+- `BrowserTokenStore` — a refused `localStorage` write: Safari private mode
+  past its quota, a browser set to block site data, a sandboxed iframe whose
+  access throws.
+- `KeychainTokenStore` (`GemmeinSwift`) — the same, with the OSStatus and
+  `SecCopyErrorMessageString`'s words for it in the sentence.
+
+The device's or browser's own error is on `err.cause`. `get()` and `clear()`
+are unchanged and stay lenient: an unreadable store means signed out, which
+every app already handles, and a crash at launch is worse than a sign-in
+screen. `MemoryTokenStore.set()` never throws. The existing `token_too_large`
+refusal is unchanged.
+
+## Who is affected
+
+Apps that call `auth.verifyEmailCode()` (or any call that stores a session)
+in a place where the store may refuse the write, and that RELIED on the old
+silence to keep running: a kiosk browser, an embedded or sandboxed iframe, a
+private-mode visitor, an unsigned simulator or ad-hoc mobile build. An app in
+an ordinary browser tab or a signed app sees no difference — nothing that
+stored the token before throws now.
+
+## What to do
+
+Catch the one code and rebuild the client with a `MemoryTokenStore`. The
+session is real either way — the server minted it — so an app that would
+rather run than stop can carry it in memory: sign-in works, and ends with the
+process.
+
+```ts
+import { gemmein, MemoryTokenStore, GemmeinError } from "@gemmein/sdk";
+
+let g = gemmein({ appKey });
+try {
+  await g.auth.verifyEmailCode(email, code);
+} catch (err) {
+  if (err instanceof GemmeinError && err.code === "secure_store_unavailable") {
+    // This session will not survive a reload. Say so, or carry on knowingly.
+    g = gemmein({ appKey, tokenStore: new MemoryTokenStore() });
+    await g.auth.verifyEmailCode(email, code);
+  } else {
+    throw err;
+  }
+}
+```
+
+An app that knows it runs where nothing can be stored passes
+`tokenStore: new MemoryTokenStore()` from the start and never sees the code.
+
+## How to tell
+
+`err.code === "secure_store_unavailable"` on the SDK (status 0, no HTTP
+response — the request succeeded; the STORE refused), with the store's own
+throw on `err.cause` and the fix in the message. In `GemmeinSwift` the same
+case is a thrown `GemmeinError` whose message carries the keychain's OSStatus.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gemmein/sdk",
-  "version": "0.8.0",
+  "version": "0.10.0",
   "description": "Gemmein SDK \u2014 passwordless auth, safe storage, and Stripe-driven record flips for AI-built apps. Small enough that one prompt teaches the whole API.",
   "license": "MIT",
   "type": "module",
@@ -13,6 +13,11 @@
       "import": "./dist/index.js",
       "require": "./dist/index.cjs"
     },
+    "./expo": {
+      "types": "./dist/expo.d.ts",
+      "import": "./dist/expo.js",
+      "require": "./dist/expo.cjs"
+    },
     "./llms.txt": "./llms.txt",
     "./REFERENCE.md": "./REFERENCE.md",
     "./reaffirm.mjs": "./reaffirm.mjs",
@@ -27,6 +32,22 @@
     "reaffirm.mjs"
   ],
   "sideEffects": false,
+  "peerDependencies": {
+    "expo": "*",
+    "expo-secure-store": "*",
+    "react-native": "*"
+  },
+  "peerDependenciesMeta": {
+    "expo": {
+      "optional": true
+    },
+    "expo-secure-store": {
+      "optional": true
+    },
+    "react-native": {
+      "optional": true
+    }
+  },
   "engines": {
     "node": ">=20"
   },
@@ -49,7 +70,7 @@
   "scripts": {
     "version:sync": "node scripts/sync-version.mjs",
     "prebuild": "node scripts/sync-version.mjs",
-    "build": "rm -rf dist && tsc -p tsconfig.build.json && tsc -p tsconfig.cjs.json && mv dist/cjs/index.js dist/index.cjs && rm -rf dist/cjs && cp dist/index.d.ts dist/index.d.cts",
+    "build": "rm -rf dist && tsc -p tsconfig.build.json && tsc -p tsconfig.cjs.json && mv dist/cjs/index.js dist/index.cjs && mv dist/cjs/expo.js dist/expo.cjs && rm -rf dist/cjs && sed -i.bak 's#\"./index.js\"#\"./index.cjs\"#g' dist/expo.cjs && rm -f dist/expo.cjs.bak && cp dist/index.d.ts dist/index.d.cts && cp dist/expo.d.ts dist/expo.d.cts",
     "prepack": "npm run build",
     "prepublishOnly": "npm run build"
   },