@fusebase/fusebase-gate-sdk 2.11.3 → 2.11.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusebase/fusebase-gate-sdk",
-  "version": "2.11.3",
+  "version": "2.11.5",
   "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.3.md

@@ -2,11 +2,12 @@
 
 - Current ref: `HEAD`
 - Previous tag: `v2.11.3`
-- Generated at: 2026-09-03T04:13:04.983Z
+- Generated at: 2026-09-03T11:31:56.879Z
 
 ## Included Drafts
 
 - `docs/release-notes/2026-09-02-portal-style-colors-font.md` - Portal branding: color roles and web font (NIM-42204)
+- `docs/release-notes/2026-09-03-firecrawl-proxy-forwarding.md` - Firecrawl proxy settings forwarding
 
 ## Summary
 
@@ -18,6 +19,11 @@ 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.
 
+### Firecrawl proxy settings forwarding
+
+Fusebase Gate now exposes the organization-scoped Paperclip Services routes
+needed to read and update Firecrawl proxy settings.
+
 
 ## API / SDK Changes
 
@@ -44,6 +50,16 @@ theme model has no font field.
 - The error for an empty body is now
   `At least one of theme, colors, font, logo, or favicon is required`.
 
+### Firecrawl proxy settings forwarding
+
+- Added `GET /:orgId/paperclip-services/installations/:appKey/proxy`.
+- Added `PUT /:orgId/paperclip-services/installations/:appKey/proxy`.
+- Added typed redacted settings and write-only configuration contracts for
+  direct, custom gateway, uploaded list, and HTTPS list/API modes.
+- Added `firecrawlProxyManagement` to the Paperclip Services capabilities
+  contract.
+- The `paperclip-services` tag remains excluded from the public SDK surface.
+
 
 ## Consumer Impact
 
@@ -75,3 +91,26 @@ 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`.
+
+### Firecrawl proxy settings forwarding
+
+Deployed Paperclip instances can open and save Firecrawl proxy settings through
+Fusebase Gate. Reads require `paperclip_services.read`; updates require
+`paperclip_services.write`. Credentials and proxy-list contents are forwarded
+only in the request body and are not included in responses.
+
+
+## Verification
+
+### Firecrawl proxy settings forwarding
+
+- Paperclip Services route authorization tests.
+- Nimbus AI client forwarding tests for GET and PUT.
+- Generated contract/OpenAPI validation and service build.
+
+
+## Follow-ups
+
+### Firecrawl proxy settings forwarding
+
+- Verify the dev Gate rollout before running Firecrawl proxy acceptance tests.

package/release-notes/2.11.5.md

@@ -0,0 +1,9 @@
+# Release Notes 2.11.5
+
+- Current ref: `HEAD`
+- Previous tag: `v2.11.5`
+- Generated at: 2026-09-04T07:08:20.261Z
+
+## Included Drafts
+
+- None

package/release-notes/latest.md

@@ -1,77 +1,9 @@
-# Release Notes 2.11.3
+# Release Notes 2.11.5
 
 - Current ref: `HEAD`
-- Previous tag: `v2.11.3`
-- Generated at: 2026-09-03T04:13:04.983Z
+- Previous tag: `v2.11.5`
+- Generated at: 2026-09-04T07:08:20.261Z
 
 ## 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