@veltdev/types 6.0.11 → 6.0.13

package/app/models/data/config.data.model.d.ts

@@ -175,6 +175,24 @@ export interface SelfHostedConfig {
      * unchanged — no behavior change when the backend does not send it.
      */
     enablePortableBackend?: boolean;
+    /**
+     * Tier B (portable backend) identify bootstrap: the base URL of the customer's OWN
+     * self-hosted gateway (e.g. `https://velt.customer.internal`). Identify is what
+     * RETURNS `wsEndpoint`/`apiEndpoint`, so the gateway's address cannot come from
+     * identify itself — this option tells the SDK where to send it.
+     *
+     * - Unset (default): identify goes to the Velt-hosted `validateClient` URL — behavior
+     *   byte-identical to today, including when `enablePortableBackend` is true.
+     * - Set (requires `enablePortableBackend: true`): identify is a plain-JSON
+     *   `POST {portableBackendUrl}/identify` on the customer's gateway (NOT a
+     *   Firebase-callable envelope) and the SDK never contacts Velt infrastructure for
+     *   identify. Set without the flag is a reported misconfiguration and is ignored.
+     *
+     * `https://` is required; plain `http://` is tolerated for loopback hosts only (local
+     * self-host development gateways) — an insecure URL fails closed with zero egress
+     * (never a silent fallback to Velt). See specs/self-hosting-tier2 iteration-8.
+     */
+    portableBackendUrl?: string;
     /**
      * The RESOLVED module closure of the deployment profile (backend plan §8.3) — the
      * enabled-module-id list the backend deploy tooling emits in

package/app/models/data/user.data.model.d.ts

@@ -220,4 +220,17 @@ export interface PermissionResult {
     accessRole?: UserPermissionAccessRole;
     expiresAt?: number;
     hasAccess: boolean;
+    /**
+     * ADDITIVE-OPTIONAL third state on Tier B gateway answers (backend Part 28
+     * iteration-1, `BACKEND-REPLY-THREE-ITEMS-2026-08-20.md` §2): on a
+     * folder-unprovisioned portable deployment, FOLDER-type entries answer
+     * `hasAccess: false` PLUS `errorCode: 'not_provided'` — "this deployment cannot
+     * answer the folder question", not "denied". Consumption contract (binding ack,
+     * `SDK-ACK-GETACCESS-ERRORCODE-2026-08-20.md`): the SDK skips the gate for the
+     * EXACT literal on FOLDER entries only; every other value — including unknown
+     * future codes — is inert and `hasAccess` is consumed verbatim. Entries for
+     * document/organization/context types never carry it; a provisioned build never
+     * emits `not_provided`. Hosted/resolver answers never carry this field.
+     */
+    errorCode?: string;
 }

package/app/utils/constants.d.ts

@@ -640,6 +640,7 @@ export declare class Constants {
         VELT_ADVANCED_QUERIES: string;
         VELT_COMMENT_VIEWS_MIGRATED: string;
         VELT_AUTH_PROXY_HOST: string;
+        VELT_PORTABLE_SESSION: string;
     };
     static NON_NESTABLE_ELEMENTS: {
         [tag: string]: boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@veltdev/types",
-    "version": "6.0.11",
+    "version": "6.0.13",
     "description": "Velt is an SDK to add collaborative features to your product within minutes. Example: Comments like Figma, Frame.io, Google docs or sheets, Recording like Loom, Huddles like Slack and much more.",
     "homepage": "https://velt.dev",
     "keywords": [