@fusebase/fusebase-gate-sdk 2.11.3 → 2.11.6-sdk.0

package/dist/apis/AppApisApi.d.ts

@@ -11,7 +11,7 @@ export declare class AppApisApi {
     constructor(client: Client);
     /**
      * Call app API operation
-     * Invokes a published app API operation through the owner app runtime using a runtime app token minted for the current authenticated caller context. Pass `onBehalfOfUserToken` (a platform app token, i.e. the user's `fbsfeaturetoken`) to run the call on behalf of an end user: Gate verifies it fail-closed and forwards the resolved user to the runtime as `X-Fusebase-Verified-User-Id` / `X-Fusebase-Verified-User-Source: obo`, so apps no longer need to hand-roll dual-token forwarding. The operation's `allowedCallers` / `requiredPermissions` are still evaluated against the calling identity, not the on-behalf-of user.
+     * Invokes a published app API operation through the owner app runtime using a runtime app token minted for the current authenticated caller context. Pass `onBehalfOfUserToken` (a platform app token, i.e. the user's `fbsfeaturetoken`) to run the call on behalf of an end user: Gate verifies it fail-closed and forwards the resolved user to the runtime as `X-Fusebase-Verified-User-Id` / `X-Fusebase-Verified-User-Source: obo`, so apps no longer need to hand-roll dual-token forwarding. The operation's `allowedCallers` / `requiredPermissions` are still evaluated against the calling identity, not the on-behalf-of user. Pass `headers` to forward extra request headers to the runtime, for operations that require one such as `Idempotency-Key`; headers Gate sets itself (auth and `X-Fusebase-*` identity headers) are reserved and rejected with 400.
      */
     callAppApi(params: {
         path: {

package/dist/apis/AppApisApi.js

@@ -13,7 +13,7 @@ class AppApisApi {
     }
     /**
      * Call app API operation
-     * Invokes a published app API operation through the owner app runtime using a runtime app token minted for the current authenticated caller context. Pass `onBehalfOfUserToken` (a platform app token, i.e. the user's `fbsfeaturetoken`) to run the call on behalf of an end user: Gate verifies it fail-closed and forwards the resolved user to the runtime as `X-Fusebase-Verified-User-Id` / `X-Fusebase-Verified-User-Source: obo`, so apps no longer need to hand-roll dual-token forwarding. The operation's `allowedCallers` / `requiredPermissions` are still evaluated against the calling identity, not the on-behalf-of user.
+     * Invokes a published app API operation through the owner app runtime using a runtime app token minted for the current authenticated caller context. Pass `onBehalfOfUserToken` (a platform app token, i.e. the user's `fbsfeaturetoken`) to run the call on behalf of an end user: Gate verifies it fail-closed and forwards the resolved user to the runtime as `X-Fusebase-Verified-User-Id` / `X-Fusebase-Verified-User-Source: obo`, so apps no longer need to hand-roll dual-token forwarding. The operation's `allowedCallers` / `requiredPermissions` are still evaluated against the calling identity, not the on-behalf-of user. Pass `headers` to forward extra request headers to the runtime, for operations that require one such as `Idempotency-Key`; headers Gate sets itself (auth and `X-Fusebase-*` identity headers) are reserved and rejected with 400.
      */
     async callAppApi(params) {
         return this.client.request({

package/dist/types/app-api/app-api.d.ts

@@ -76,6 +76,12 @@ export interface CallAppApiRequestContract {
     path?: Record<string, string>;
     query?: Record<string, string | number | boolean>;
     body?: unknown;
+    /**
+     * Extra request headers forwarded verbatim to the app runtime, for operations
+     * that require one (e.g. `Idempotency-Key`). Headers Gate sets itself to prove
+     * the caller's identity to the runtime are reserved and rejected with 400.
+     */
+    headers?: Record<string, string>;
     /**
      * On-behalf-of: a platform app token (`fbsfeaturetoken` / `x-app-feature-token`)
      * identifying the end user this call runs for. Gate verifies it fail-closed and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusebase/fusebase-gate-sdk",
-  "version": "2.11.3",
+  "version": "2.11.6-sdk.0",
   "description": "TypeScript SDK for Fusebase Gate APIs - Generated from contract introspection",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",

package/release-notes/2.11.6-sdk.0.md

@@ -0,0 +1,9 @@
+# Release Notes 2.11.6-sdk.0
+
+- Current ref: `HEAD`
+- Previous tag: `v2.11.6-sdk.0`
+- Generated at: 2026-09-07T15:25:08.819Z
+
+## Included Drafts
+
+- None

package/release-notes/latest.md

@@ -1,77 +1,9 @@
-# Release Notes 2.11.3
+# Release Notes 2.11.6-sdk.0
 
 - Current ref: `HEAD`
-- Previous tag: `v2.11.3`
-- Generated at: 2026-09-03T04:13:04.983Z
+- Previous tag: `v2.11.6-sdk.0`
+- Generated at: 2026-09-07T15:25:08.819Z
 
 ## Included Drafts
 
-- `docs/release-notes/2026-09-02-portal-style-colors-font.md` - Portal branding: color roles and web font (NIM-42204)
-
-## Summary
-
-### Portal branding: color roles and web font (NIM-42204)
-
-`updatePortalStyle` now also takes `colors` and `font`, the two field groups the
-first round left out. Colors are expressed the way the portal actually renders
-them — as **Tailwind palette tokens** written into the theme's own color slots,
-not as hex. The font is delivered through the portal's custom code, since the
-theme model has no font field.
-
-
-## API / SDK Changes
-
-### Portal branding: color roles and web font (NIM-42204)
-
-- `updatePortalStyle` body gained:
-  - `colors` — five semantic roles, each one palette token (`transparent`,
-    `white`, `black` or `<hue>-<shade>`, e.g. `indigo-600`):
-
-    | Role | Theme slots written |
-    | --- | --- |
-    | `primary` | `bg_primary`, `bg_primary_hover`, `primary` |
-    | `background` | `bg_body` |
-    | `surface` | `bg_surface` |
-    | `text` | `text_surface` |
-    | `accent` | `bg_secondary`, `bg_secondary_hover` |
-
-  - `font` — `{ family, source: "google" }`. The family is spelled as Google
-    Fonts spells it; letters, digits and spaces only.
-- `getPortal` → `style` gained `colors` (the roles the portal overrides) and
-  `fontFamily`.
-- A body touching both the theme fields and `font` stages **two** events (one
-  `updateThemeSettings`, one `updateCustomCodeSettings`); `seq` is the first.
-- The error for an empty body is now
-  `At least one of theme, colors, font, logo, or favicon is required`.
-
-
-## Consumer Impact
-
-### Portal branding: color roles and web font (NIM-42204)
-
-An agent can now recolor a portal past the 13 named themes without writing
-custom CSS, and the recolor works on any domain.
-
-**Hex is still rejected, on purpose.** The renderer interpolates the stored
-token straight into a class name (`bg-neutral-900`), and
-`apps/portals/tailwind.config.js` safelists palette names only, so `#2563eb`
-would be stored, published, and style nothing. `stone` and `violet` are rejected
-for the same reason: they are missing from that safelist. Convert a hex to the
-nearest token before calling.
-
-**Where the font lives.** The theme DTO has no font field, so `font` stages one
-marked `<style>` block inside the portal's `customStyle`:
-
-```html
-<!--fusebase-font--><style>@import url("https://fonts.googleapis.com/css2?family=Fraunces&display=swap");#main-scrolling-container{font-family:'Fraunces',sans-serif}</style><!--/fusebase-font-->
-```
-
-The markers make it replaceable: a second `font` call swaps the block rather
-than appending one, and `updatePortalCustomCode` carries it through when the
-agent rewrites the surrounding CSS. Because it is custom code, it renders
-wherever custom code renders — the customizer only offers the custom-code editor
-on portals served from a custom CNAME domain.
-
-**Hover slots take the same token as their base.** No shade is derived, so a
-recolored hover never lands on an unrelated preset color. An agent that wants a
-distinct hover uses `updatePortalCustomCode`.
+- None

package/release-notes/2.11.3.md

@@ -1,77 +0,0 @@
-# Release Notes 2.11.3
-
-- Current ref: `HEAD`
-- Previous tag: `v2.11.3`
-- Generated at: 2026-09-03T04:13:04.983Z
-
-## Included Drafts
-
-- `docs/release-notes/2026-09-02-portal-style-colors-font.md` - Portal branding: color roles and web font (NIM-42204)
-
-## Summary
-
-### Portal branding: color roles and web font (NIM-42204)
-
-`updatePortalStyle` now also takes `colors` and `font`, the two field groups the
-first round left out. Colors are expressed the way the portal actually renders
-them — as **Tailwind palette tokens** written into the theme's own color slots,
-not as hex. The font is delivered through the portal's custom code, since the
-theme model has no font field.
-
-
-## API / SDK Changes
-
-### Portal branding: color roles and web font (NIM-42204)
-
-- `updatePortalStyle` body gained:
-  - `colors` — five semantic roles, each one palette token (`transparent`,
-    `white`, `black` or `<hue>-<shade>`, e.g. `indigo-600`):
-
-    | Role | Theme slots written |
-    | --- | --- |
-    | `primary` | `bg_primary`, `bg_primary_hover`, `primary` |
-    | `background` | `bg_body` |
-    | `surface` | `bg_surface` |
-    | `text` | `text_surface` |
-    | `accent` | `bg_secondary`, `bg_secondary_hover` |
-
-  - `font` — `{ family, source: "google" }`. The family is spelled as Google
-    Fonts spells it; letters, digits and spaces only.
-- `getPortal` → `style` gained `colors` (the roles the portal overrides) and
-  `fontFamily`.
-- A body touching both the theme fields and `font` stages **two** events (one
-  `updateThemeSettings`, one `updateCustomCodeSettings`); `seq` is the first.
-- The error for an empty body is now
-  `At least one of theme, colors, font, logo, or favicon is required`.
-
-
-## Consumer Impact
-
-### Portal branding: color roles and web font (NIM-42204)
-
-An agent can now recolor a portal past the 13 named themes without writing
-custom CSS, and the recolor works on any domain.
-
-**Hex is still rejected, on purpose.** The renderer interpolates the stored
-token straight into a class name (`bg-neutral-900`), and
-`apps/portals/tailwind.config.js` safelists palette names only, so `#2563eb`
-would be stored, published, and style nothing. `stone` and `violet` are rejected
-for the same reason: they are missing from that safelist. Convert a hex to the
-nearest token before calling.
-
-**Where the font lives.** The theme DTO has no font field, so `font` stages one
-marked `<style>` block inside the portal's `customStyle`:
-
-```html
-<!--fusebase-font--><style>@import url("https://fonts.googleapis.com/css2?family=Fraunces&display=swap");#main-scrolling-container{font-family:'Fraunces',sans-serif}</style><!--/fusebase-font-->
-```
-
-The markers make it replaceable: a second `font` call swaps the block rather
-than appending one, and `updatePortalCustomCode` carries it through when the
-agent rewrites the surrounding CSS. Because it is custom code, it renders
-wherever custom code renders — the customizer only offers the custom-code editor
-on portals served from a custom CNAME domain.
-
-**Hover slots take the same token as their base.** No shade is derived, so a
-recolored hover never lands on an unrelated preset color. An agent that wants a
-distinct hover uses `updatePortalCustomCode`.