@civitai/sdk 0.10.0 → 0.10.2

package/README.md

@@ -71,7 +71,11 @@ observed two ways is two values that can disagree.
 A block opts in by declaring `auth: "oauth"` in its `block.manifest.json`. The
 host then hands it a real OAuth access token that `/api/v1`, the orchestrator
 and the MCP accept, and consent — including `requestGrants` — goes through the
-host's consent dialog.
+host's consent dialog. The manifest must also declare `user:read:self`, which
+every OAuth token carries: on civitai.com the host never mints one without it
+and hands back the block token. The dev tunnel mints one regardless, so a
+missing `user:read:self` only shows up after approval. And `auth: "oauth"` cannot be declared alongside any
+`apps:storage:*` scope: such a manifest is refused at submit.
 
 ### When the token is the block-scoped one
 
@@ -357,7 +361,10 @@ wider scope — and refuses without one.
 | `publishGenerationOutputs({ workflowId, imageIndexes })` | Publishes your own workflow's outputs, behind the host's confirmation; resolves the new image ids |
 
 Host failures reject with a `BridgeError` carrying a `code` (`forbidden`,
-`unauthenticated`, `rate-limited`, …). Timeouts are the host's to set; pass a
+`unauthenticated`, `rate-limited`, …). `unauthenticated` includes a viewer whose
+session ended (signed out in another tab) — offer `requestSignIn()`. A session
+that now belongs to a different account is `forbidden`; its `message` asks the
+viewer to reload the page. Timeouts are the host's to set; pass a
 `signal` to cancel. `ApiError` and `BridgeError` both extend `CivitaiError`, so
 one `catch` can tell a refusal from a bug.
 

package/dist/core/errors.js

@@ -20,11 +20,18 @@ export class BridgeError extends CivitaiError {
  * The messages this bridge already had report failure as the server's own
  * sentence — the host holds the tRPC code and drops it. Unmatched text is
  * `unavailable`; `message` still carries what the host said.
+ *
+ * Procedures that need the viewer's signed-in session can refuse with a bare
+ * `UNAUTHORIZED` (the session ended, e.g. signed out in another tab), which is
+ * `unauthenticated`, or with "…belongs to a different account; reload the page
+ * to continue" (the page's session changed account), which is `forbidden`:
+ * signing in again does not help, reloading the page does.
  */
 const HOST_FAILURES = [
     [/authenticated viewer|no block token/i, 'unauthenticated'],
+    [/^UNAUTHORIZED$/, 'unauthenticated'],
     [
-        /(requires|lacks) .+ scope|not approved|revoked|invalid block token|not enabled|review preview|^banned$/i,
+        /(requires|lacks) .+ scope|not approved|revoked|invalid block token|not enabled|review preview|belongs to a different account|^banned$/i,
         'forbidden',
     ],
     [/rate limit|^busy$/i, 'rate-limited'],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@civitai/sdk",
-  "version": "0.10.0",
+  "version": "0.10.2",
   "description": "The Civitai SDK: an app holds a token and calls the Civitai API and the orchestrator; a block asks its host only to show host UI.",
   "license": "MIT",
   "type": "module",