@riverbankcms/sdk 0.128.0 → 0.129.1

package/README.md

@@ -24,6 +24,20 @@ npm install @riverbankcms/sdk
 pnpm add @riverbankcms/sdk
 ```
 
+The SDK is the data-plane runtime only. It does not install or expose the
+`riverbankcms` command. SDK sites that use content/config management should
+declare the standalone CLI explicitly:
+
+```bash
+pnpm add @riverbankcms/sdk
+pnpm add -D riverbankcms
+pnpm exec riverbankcms --help
+```
+
+The CLI and SDK are versioned independently. Keep the CLI invocation project
+local (`pnpm exec`) so a site never depends on a transitive or globally
+installed binary.
+
 ## Quick Start
 
 > **Important:** The `baseUrl` parameter must be the complete API URL including the `/api` path. For example: `https://dashboard.example.com/api`
@@ -2627,6 +2641,38 @@ export default Page;
 export { generateMetadata };
 ```
 
+### Fully custom, override-only rendering
+
+Hosts that own all visual rendering can opt out of CMS theme admission and built-in block fallbacks explicitly. The registry only needs to cover block kinds the host's content actually uses; `satisfies BlockOverrideRegistrations` checks each registration without pretending custom block kinds form a closed exhaustive set.
+
+```tsx
+import { createCatchAllPage } from '@riverbankcms/sdk/next';
+import type {
+  BlockOverrideProps,
+  BlockOverrideRegistrations,
+} from '@riverbankcms/sdk/rendering';
+
+const blockOverrides = {
+  hero: ({ content }: BlockOverrideProps) => (
+    <Hero heading={String(content.heading ?? '')} />
+  ),
+  'custom.product-grid': ProductGrid,
+} satisfies BlockOverrideRegistrations;
+
+const { Page, generateMetadata } = createCatchAllPage({
+  getClient: getRiverbankClient,
+  config,
+  rendering: { kind: 'overrides-only' },
+  blockOverrides,
+});
+```
+
+In this mode the SDK does not resolve, parse, normalize, or build tokens from the response theme. Overrides receive the usual content, resolved data, routing, media, API/auth, IDs, and preview context, but no `theme` or `themeConfig`. A page fails with `MissingBlockOverrideError` when its content contains an unregistered kind; it never falls through to the known built-in renderer.
+
+The optional theme-independent wrapper belongs inside `rendering`: use `runtime: { kind: 'responsive-only' }` (the default) for Riverbank's generated responsive utility scope, or `runtime: { kind: 'none' }` when the host owns that too. Do not combine override-only rendering with top-level `themeRuntime`, `theme`, `themes`, or `getTheme`. If you use SDK `Layout` directly, its header and footer must both be custom or disabled. Preview receives the same rendering selection and registry.
+
+The content response still carries a compatibility theme field for now; override-only rendering deliberately ignores it. Wire-level theme nullability is tracked separately in #1290.
+
 Keep the `server-only` marker at the top of the registry so Next.js turns an accidental Client Component import into a build error. `generateMetadata()` never receives or runs host loaders—even with `customMetadata`—so a normal request does not repeat host queries for metadata and rendering.
 
 ```tsx
@@ -3173,263 +3219,12 @@ export default defineConfig({
 
 ## CLI
 
-The SDK includes a CLI for syncing configuration and content between your local environment and the CMS.
-
-### setup plan
-
-Show the read-only lifecycle for site creation, management-key setup, dashboard user access, and SDK env variables:
-
-```bash
-npx riverbankcms setup plan --env=remote
-```
-
-The SDK CLI cannot create remote sites, issue keys, or grant user access from a site-scoped management key. Do those privileged operations through the dashboard/admin surface or approved CMS repo tooling, then use the setup planner and `env status` to verify the SDK repo has the right `RIVERBANK_*` variables.
-
-### push-config
-
-Push schema/config surfaces to your CMS dashboard, including custom blocks, block field options/extensions, content type definitions/templates, SDK-managed site settings, and footer blocks:
-
-```bash
-npx riverbankcms push-config --dashboard <url>
-```
-
-Pages, content entries, navigation menus, and canonical events are content documents. Sync them with `riverbankcms push pages`, `riverbankcms push entries`, `riverbankcms push navigation`, or `riverbankcms push events`.
-
-Canonical event files in `content/events/*.json` include `preset`, `bookingScope`, and an explicit `occurrences` list. Each occurrence carries UTC `startsAt`/`endsAt` instants and its IANA `timeZone`; this supports one-off events and whole-series schedules without reconstructing dates from a recurrence summary. Files may also include `path` and `blocks`. `path` updates the linked event content entry route. `blocks` writes per-event entry-slot content, such as `blocks.main` for the built-in event template. Use stable block identifiers so repeat pushes update existing slot blocks; `push events` rejects duplicate event identifiers before writing. Default entry slots accept enabled SDK `custom.*` blocks, while explicit template `allowedBlocks` lists remain authoritative.
-
-The retired `schedule` object is not accepted. When upgrading a site with local event edits: preserve those edits, deploy the matching CMS API first, upgrade the SDK, run `riverbankcms pull events`, then reapply the edits to the canonical files. Existing occurrence schedules may be replayed exactly; changing an already-created schedule remains an explicit CMS capability gap.
-
-**Options:**
-
-| Option | Description |
-|--------|-------------|
-| `--api-key <key>` | Management API key (or set `RIVERBANK_*_MGMT_API_KEY`) |
-| `--dashboard <url>` | Dashboard URL (or set `RIVERBANK_*_DASHBOARD_URL`) |
-| `--config <path>` | Path to config file (default: `./riverbank.config.ts`) |
-| `--dry-run` | Validate config and preview schema/config surfaces without mutating the dashboard |
-
-**Example:**
-
-```bash
-# Using environment variables (local)
-export RIVERBANK_LOCAL_DASHBOARD_URL=https://www.riverbankcms.com
-export RIVERBANK_LOCAL_MGMT_API_KEY=bld_mgmt_sk_...
-npx riverbankcms push-config
-
-# Preview without applying
-npx riverbankcms push-config --dry-run
-
-# Or inline (remote)
-npx riverbankcms push-config \
-  --api-key bld_mgmt_sk_... \
-  --dashboard https://www.riverbankcms.com
-```
-
-### pull
-
-Download content from the CMS to local JSON files:
-
-```bash
-npx riverbankcms pull [scope] [type] [identifier]
-```
-
-**Scopes:**
-
-| Scope | Description |
-|-------|-------------|
-| (none) / `all` | Pull all content types |
-| `entries` | Pull all entries, a content type, or a single entry |
-| `pages` | Pull all pages or a single page |
-| `navigation` | Pull navigation menus |
-| `settings` | Pull site settings |
-| `forms` | Pull form definitions |
-| `venues` | Pull all event venues or one venue by slug |
-| `event-categories` | Pull all event categories or one category by identifier |
-| `events` | Pull all event series or one event by identifier |
-
-**Examples:**
-
-```bash
-# Pull all content
-npx riverbankcms pull
-
-# Pull only forms
-npx riverbankcms pull forms
-
-# Pull entries for a specific content type
-npx riverbankcms pull entries blog-post
-
-# Pull one entry
-npx riverbankcms pull entries blog-post welcome
-
-# Pull one page
-npx riverbankcms pull pages home
-
-# Pull one canonical event
-npx riverbankcms pull events the-whole-in-your-heart
-
-# Pull from remote environment
-npx riverbankcms pull --env=remote
-
-# Sync media files between environments
-npx riverbankcms pull --env=remote --sync-media --yes
-
-# Overwrite target media on checksum mismatch (explicit / unsafe)
-npx riverbankcms pull --env=remote --sync-media --overwrite-media --yes
-
-# Download media referenced by identifiers
-npx riverbankcms pull --local-media
-```
-
-**Output Structure:**
-
-```
-content/
-├── entries/
-│   └── {content-type}/
-│       └── {identifier}.json
-├── pages/
-│   └── {identifier}.json
-├── forms/
-│   └── {slug}.json
-├── navigation.json
-├── settings.json
-├── media/
-│   ├── <identifier>.<ext>
-│   └── .manifest.json
-└── .meta/
-    ├── local/
-    │   └── {entity}.json  # Local CMS sync timestamps
-    └── remote/
-        └── {entity}.json  # Remote CMS sync timestamps
-```
-
-Older projects with flat `content/.meta/{entity}.json` files are read as a compatibility fallback. The CLI writes new metadata into the target-specific `local/` or `remote/` directory the next time you pull or update metadata.
-
-Note: `content/media/` is local cache and migration working data by default. Generated SDK sites gitignore `content/media/*` so large downloaded files are not staged accidentally, while allowing intentional small fixtures under `content/media/fixtures/`. `content/media/.manifest.json` is also cache data (identifier -> checksum/filename) and intentionally does not store env-specific `assetId`s.
-
-### push
-
-Push local content to the CMS with diff-based sync:
-
-```bash
-npx riverbankcms push [scope] [type] [identifier]
-```
-
-**Scopes:**
-
-| Scope | Description |
-|-------|-------------|
-| (none) / `all` | Push all content types |
-| `entries` | Push all entries, a content type, or a single entry |
-| `pages` | Push all pages or a single page with blocks |
-| `navigation` | Push navigation menus |
-| `settings` | Push `content/settings.json` only |
-| `forms` | Push form definitions |
-
-**Options:**
-
-| Option | Description |
-|--------|-------------|
-| `--dry-run` | Show what would be pushed without making changes |
-| `--yes` | Skip confirmation (required for `--env=remote`) |
-| `--force` | Push even if remote is newer |
-| `--force-update-asset` | Replace CMS media when identifiers conflict (local media sync only) |
-| `--sync-media` | Sync media files from local to remote environment |
-| `--overwrite-media` | When using `--sync-media`, overwrite target media on checksum mismatch |
-| `--json-diff` | Output JSON diff (`summary` or `full`) |
-| `--merge-remote` | Plan an entries/pages three-way merge for `--env=remote` that preserves remote edits |
-| `--verify-noop` | Re-fetch after an applied push and fail if changes remain |
-
-**Examples:**
-
-```bash
-# Preview changes (dry run)
-npx riverbankcms push --dry-run
-
-# Push all content
-npx riverbankcms push
-
-# Push only forms
-npx riverbankcms push forms
-
-# Push only site settings / branding
-npx riverbankcms push settings
-
-# Push to production with confirmation bypass
-npx riverbankcms push --env=remote --yes
-
-# Preview a production-safe merge for entries
-npx riverbankcms push entries blog-post --env=remote --merge-remote
-
-# Preview a production-safe merge for a page
-npx riverbankcms push pages home --env=remote --merge-remote
-
-# Apply that merge after reviewing the plan
-npx riverbankcms push entries blog-post --env=remote --merge-remote --yes
-
-# Get JSON diff for automation
-npx riverbankcms push --dry-run --json-diff=summary
-
-# Push to both environments and verify both are clean afterwards
-npx riverbankcms push --env=both --yes --verify-noop
-```
-
-**Remote-aware content merge:**
-
-`--merge-remote` is a safer production entries/pages workflow. It compares the last pulled base snapshot, your local files, and the current remote CMS, then reports a merge plan. Remote runs still default to dry-run; add `--yes` only after reviewing the plan. In v1 this supports entries and pages, is `--env=remote` only, and cannot be combined with `--force`, `--delete-orphaned`, or `--auto-pull-stale`. Page block changes are treated conservatively as conflicts unless remote blocks are unchanged.
-
-**Local content edit helpers:**
-
-`riverbankcms content edit ...` changes local `content/**` JSON files only. It previews by default and writes only with `--write`.
-
-```bash
-npx riverbankcms content edit remove-page-block home old-hero
-npx riverbankcms content edit move-page-block home intro --after hero --write
-npx riverbankcms content edit set-page-field home title --value "New title" --write
-npx riverbankcms content edit set-page-field home blocks[0].data.count --json-value 3
-```
-
-After editing, run `riverbankcms push --dry-run --diff`, then push with `--verify-noop` when ready.
-
-**Post-push verification:** `--verify-noop` re-reads local files after an applied push, fetches the target CMS, and fails if changes remain. It cannot be combined with `--dry-run`; remote targets need `--yes` so there is an applied push to verify. In JSON mode the CLI emits a `verification` object with `clean`, `dirty`, `fetch_failed`, or `unsupported_scope` status. A dirty result can also mean another actor changed remote content between push and verification.
-
-**Local Media (Identifiers):**
-
-- Add `identifier` to media fields (slug only, no extension)
-- Place files at `content/media/<identifier>.<ext>`
-- Use `npx riverbankcms push` to upload referenced files (default-on)
-- Use `--force-update-asset` to replace a CMS asset when checksums differ
-- Treat `content/media/*` as local cache/migration working data by default. For existing repos that already committed media, opt in with `git rm --cached -r content/media` after adding the generated ignore rule. Keep intentional small fixtures under `content/media/fixtures/`.
-
-**Site branding via `content/settings.json`:**
-
-```json
-{
-  "homepageId": null,
-  "seoDefaults": null,
-  "logoIdentifier": "positive-play-primary-logo",
-  "faviconIdentifier": "positive-play-primary-logo"
-}
-```
-
-- Keep branding files in `content/media/<identifier>.<ext>`
-- Run `npx riverbankcms push settings` to upload missing branding files and assign the site logo/favicon without pushing unrelated content
-- Run `npx riverbankcms pull settings` to round-trip the current identifier-based branding state
-- If the current CMS logo/favicon asset has no media identifier yet, pull warns and omits that field instead of writing a destructive clear
-- Dashboard branding edits and CLI pushes both write the same site settings columns, so pull before pushing if someone may have changed branding in the dashboard
-
-**Media portability (important):**
-
-- Content JSON is portable across environments; media references must be **identifier-only**.
-- Do not commit or hand-write `assetId`, `storagePath`, `storageBucket`, or `src` into content JSON.
-
-**Sync Behavior:**
+The standalone `riverbankcms` package provides the CLI for syncing configuration
+and content between your SDK site and the CMS. Install it alongside
+`@riverbankcms/sdk`, then use the standalone package's
+[CLI reference](../cli/README.md) for setup, commands, environment behavior,
+and operational guidance.
 
-- **Creates** new content if identifier/slug doesn't exist
-- **Updates** existing content based on diff
-- **Never deletes** - removing from local doesn't delete from CMS
-- **Stale detection** - warns if remote changed since last pull (use `--force` to override)
 
 ## Next.js Catch-All Page Factory
 
@@ -3772,6 +3567,7 @@ createCatchAllPage({
 | `getClient` | `() => RiverbankClient` | Yes | Factory function returning a configured client |
 | `config` | `RiverbankSiteConfig` | Yes | Site config from `defineConfig()` |
 | `blockOverrides` | `BlockOverrides` | No | Custom block component overrides |
+| `rendering` | `{ kind: 'overrides-only', runtime?: { kind: 'responsive-only' \| 'none' } }` | No | Opt into host-only rendering; requires `blockOverrides` and forbids theme options |
 | `siteUrl` | `string` | No | Override site URL for metadata (uses `config.liveUrl`/`previewUrl` as fallback) |
 | `beforeRender` | `function` | No | Intercept before rendering |
 | `customMetadata` | `function` | No | Custom metadata generation |

package/dist/{PreviewEditorSidebar-Dbvb7GIr.mjs → PreviewEditorSidebar-DceRseRV.mjs}

@@ -1,8 +1,8 @@
 "use client";
-import { $ as createOptimisticActionRunner, $i as Callout, A as isPreviewingChange, B as previewHeaderStyle, Br as getHeaderStyle, Ca as DropdownMenuLabel, Ci as updateButtonStyleSelectionChoice, D as createStyleConfiguratorState, Da as Button, Dr as getCuratedSiteStyle, E as cancelPreview, F as palettePreviewProjection, Ft as BlockEditor, G as syncStyleConfiguratorState, H as resetTypographyToSaved, Ht as useEditorUiStoreInstance, I as previewButtonStyle, Ji as Select, K as toggleRow, L as previewCuratedPalette, La as X$1, M as markApplySaved, Mi as paletteColorsSchema, N as markApplySaving, Na as assertNever$1, O as deriveStyleConfiguratorCapabilities, On as ThemeScope, P as openRow, Qa as LoaderCircle, Qi as SelectValue, R as previewFooterLook, Sa as DropdownMenuItem, Si as resolveButtonStyleSelection, T as applyTypographyDraftPatch, Ta as DropdownMenuTrigger, Ti as themeButtonClassName, Tr as curatedSiteStyles, U as setPaletteColors, Ua as Smartphone, V as previewSiteStyle, Va as Tablet, Vt as useEditorUiStore, W as styleConfiguratorHistoryEntryForPersistedSelection, Wa as SlidersHorizontal, Xa as Monitor, Xi as SelectItem, Yi as SelectContent, Za as Maximize2, Zi as SelectTrigger, _ as cycleableSiteChromeOptions, _a as CollapsibleContent, aa as Input, an as deriveRouteMetadataPresentation, ba as DropdownMenu, bi as buttonStyleSelectionParameterValue, c as selectionSnapshotFromApplySiteStyleSelectionResponse, ca as TabsList, d as resolveStyleConfiguratorInitialSnapshot, ea as CalloutDescription, et as resolvePreviewSidebarTab, fn as createManifestValidation, g as cycleSiteChromeLookId, ga as Collapsible, h as buildSiteChromeLookModels, hn as createStoreBackend, ia as PopoverTrigger, io as ChevronLeft, j as markApplyFailed, ja as unsafeAsEditorBlockId, ji as paletteColorEntries, k as dismissWarnings, ka as cn, kr as findFooterLook, l as deriveSiteStylePreviewUpdate, la as TabsTrigger, m as reportPreviewDesignError, n as useSiteChromeCustomizeOptional, na as Popover, oa as Tabs, on as resolvePageRouteSlug, oo as Check, ot as ContentFieldsForm, p as PREVIEW_DESIGN_SAVE_ERROR_MESSAGE, pn as FormRenderer, qr as curatedPalettes, ra as PopoverContent, rn as isAdapterReferenceKind, ro as ChevronRight, s as buildApplySiteStyleSelectionBody, sa as TabsContent, sn as resolveContentTitle, st as useUISelector, ta as SearchInput, tt as FooterComposerPanel, u as planSiteStylePreviewChange, un as ManifestForm, ut as useEntryController, v as planSiteChromeLookSelection, va as CollapsibleTrigger, w as applyResolvedSelections, wa as DropdownMenuSeparator, wi as buttonStyleSelectionKey, x as usePreviewDesignCoordinator, xa as DropdownMenuContent, xi as findButtonStyleRecipe, y as siteChromeLookUnavailableReasonLabel, ya as Surface, yn as listEntryPageContentSlots, z as previewHeaderLayout, zr as getHeaderLayout } from "./SiteChromeCustomizeContext-CvuGbHJX.mjs";
+import { $ as createOptimisticActionRunner, $i as Callout, A as isPreviewingChange, B as previewHeaderStyle, Br as getHeaderStyle, Ca as DropdownMenuLabel, Ci as updateButtonStyleSelectionChoice, D as createStyleConfiguratorState, Da as Button, Dr as getCuratedSiteStyle, E as cancelPreview, F as palettePreviewProjection, Ft as BlockEditor, G as syncStyleConfiguratorState, H as resetTypographyToSaved, Ht as useEditorUiStoreInstance, I as previewButtonStyle, Ji as Select, K as toggleRow, L as previewCuratedPalette, La as X$1, M as markApplySaved, Mi as paletteColorsSchema, N as markApplySaving, Na as assertNever$1, O as deriveStyleConfiguratorCapabilities, On as ThemeScope, P as openRow, Qa as LoaderCircle, Qi as SelectValue, R as previewFooterLook, Sa as DropdownMenuItem, Si as resolveButtonStyleSelection, T as applyTypographyDraftPatch, Ta as DropdownMenuTrigger, Ti as themeButtonClassName, Tr as curatedSiteStyles, U as setPaletteColors, Ua as Smartphone, V as previewSiteStyle, Va as Tablet, Vt as useEditorUiStore, W as styleConfiguratorHistoryEntryForPersistedSelection, Wa as SlidersHorizontal, Xa as Monitor, Xi as SelectItem, Yi as SelectContent, Za as Maximize2, Zi as SelectTrigger, _ as cycleableSiteChromeOptions, _a as CollapsibleContent, aa as Input, an as deriveRouteMetadataPresentation, ba as DropdownMenu, bi as buttonStyleSelectionParameterValue, c as selectionSnapshotFromApplySiteStyleSelectionResponse, ca as TabsList, d as resolveStyleConfiguratorInitialSnapshot, ea as CalloutDescription, et as resolvePreviewSidebarTab, fn as createManifestValidation, g as cycleSiteChromeLookId, ga as Collapsible, h as buildSiteChromeLookModels, hn as createStoreBackend, ia as PopoverTrigger, io as ChevronLeft, j as markApplyFailed, ja as unsafeAsEditorBlockId, ji as paletteColorEntries, k as dismissWarnings, ka as cn, kr as findFooterLook, l as deriveSiteStylePreviewUpdate, la as TabsTrigger, m as reportPreviewDesignError, n as useSiteChromeCustomizeOptional, na as Popover, oa as Tabs, on as resolvePageRouteSlug, oo as Check, ot as ContentFieldsForm, p as PREVIEW_DESIGN_SAVE_ERROR_MESSAGE, pn as FormRenderer, qr as curatedPalettes, ra as PopoverContent, rn as isAdapterReferenceKind, ro as ChevronRight, s as buildApplySiteStyleSelectionBody, sa as TabsContent, sn as resolveContentTitle, st as useUISelector, ta as SearchInput, tt as FooterComposerPanel, u as planSiteStylePreviewChange, un as ManifestForm, ut as useEntryController, v as planSiteChromeLookSelection, va as CollapsibleTrigger, w as applyResolvedSelections, wa as DropdownMenuSeparator, wi as buttonStyleSelectionKey, x as usePreviewDesignCoordinator, xa as DropdownMenuContent, xi as findButtonStyleRecipe, y as siteChromeLookUnavailableReasonLabel, ya as Surface, yn as listEntryPageContentSlots, z as previewHeaderLayout, zr as getHeaderLayout } from "./SiteChromeCustomizeContext-BLl-OlL4.mjs";
 import { d as unwrapResponse, f as getDashboardUrl, r as usePreviewAuth } from "./previewAuthStore-BesgU5Xu.mjs";
-import { t as Separator } from "./separator-CEoGABRc.mjs";
-import { S as getSiteFontsStorageUrl, _ as useBlockCustomizeControls, b as buildFontPreviewUrl, d as resolvePreviewDashboardSetupHandoff, f as resolvePreviewEditorGuidanceModel, g as usePreviewBlockCustomizeSelectionOptional, h as canInspectSiteStyle, m as canApplySiteStyle, p as resolvePreviewSidebarChromeModel, u as buildPreviewDashboardSetupUrl, v as PreviewFormProvider, x as generateFontFaceCss, y as previewWidgetOverrides } from "./SdkPreviewModeRuntime-BZHt6e9w.mjs";
+import { t as Separator } from "./separator-BE3NCquy.mjs";
+import { S as getSiteFontsStorageUrl, _ as useBlockCustomizeControls, b as buildFontPreviewUrl, d as resolvePreviewDashboardSetupHandoff, f as resolvePreviewEditorGuidanceModel, g as usePreviewBlockCustomizeSelectionOptional, h as canInspectSiteStyle, m as canApplySiteStyle, p as resolvePreviewSidebarChromeModel, u as buildPreviewDashboardSetupUrl, v as PreviewFormProvider, x as generateFontFaceCss, y as previewWidgetOverrides } from "./SdkPreviewModeRuntime-Bt87-62u.mjs";
 import React, { createContext, forwardRef, useCallback, useContext, useEffect, useId, useLayoutEffect, useMemo, useRef, useState, useSyncExternalStore, useTransition } from "react";
 import { Fragment as Fragment$1, jsx, jsxs } from "react/jsx-runtime";
 import { useQuery, useQueryClient } from "@tanstack/react-query";

package/dist/{PreviewEditorUI-e9O9l20X.mjs → PreviewEditorUI-BNunq3kk.mjs}

@@ -1,7 +1,7 @@
 "use client";
-import { Ba as TriangleAlert, Bt as classifyHistoryShortcut, Da as Button, Gi as Tooltip, Ha as Sparkles, Ht as useEditorUiStoreInstance, Ja as PenLine, Ka as Redo2, Ki as TooltipContent, Mt as useEditor, Oa as cva, Qa as LoaderCircle, Qt as useMultiAutosave, Sa as DropdownMenuItem, Ta as DropdownMenuTrigger, Vt as useEditorUiStore, Ya as Palette, a as previewDesignHistoryDomainForCommand, ao as ChevronDown, ba as DropdownMenu, da as DialogContent, dt as useEntryEditorController, fa as DialogDescription, ha as DialogTitle, i as usePreviewDesignHistoryOrder, ka as cn, ma as DialogHeader, n as useSiteChromeCustomizeOptional, no as EllipsisVertical, o as selectPreviewDesignHistoryDomain, qa as Pencil, qi as TooltipTrigger, to as Eye, ua as Dialog, xa as DropdownMenuContent, za as Undo2 } from "./SiteChromeCustomizeContext-CvuGbHJX.mjs";
+import { Ba as TriangleAlert, Bt as classifyHistoryShortcut, Da as Button, Gi as Tooltip, Ha as Sparkles, Ht as useEditorUiStoreInstance, Ja as PenLine, Ka as Redo2, Ki as TooltipContent, Mt as useEditor, Oa as cva, Qa as LoaderCircle, Qt as useMultiAutosave, Sa as DropdownMenuItem, Ta as DropdownMenuTrigger, Vt as useEditorUiStore, Ya as Palette, a as previewDesignHistoryDomainForCommand, ao as ChevronDown, ba as DropdownMenu, da as DialogContent, dt as useEntryEditorController, fa as DialogDescription, ha as DialogTitle, i as usePreviewDesignHistoryOrder, ka as cn, ma as DialogHeader, n as useSiteChromeCustomizeOptional, no as EllipsisVertical, o as selectPreviewDesignHistoryDomain, qa as Pencil, qi as TooltipTrigger, to as Eye, ua as Dialog, xa as DropdownMenuContent, za as Undo2 } from "./SiteChromeCustomizeContext-BLl-OlL4.mjs";
 import { d as unwrapResponse, r as usePreviewAuth } from "./previewAuthStore-BesgU5Xu.mjs";
-import { C as FixedBottomSurface, a as usePreviewPageDesignEditorState, c as applyPreviewChromeSurfaceToElement, l as resolvePreviewChromeSurface, o as PREVIEW_CHROME_PORTAL_CLASS_NAME, s as PREVIEW_CHROME_THEME_CLASS_NAME } from "./SdkPreviewModeRuntime-BZHt6e9w.mjs";
+import { C as FixedBottomSurface, a as usePreviewPageDesignEditorState, c as applyPreviewChromeSurfaceToElement, l as resolvePreviewChromeSurface, o as PREVIEW_CHROME_PORTAL_CLASS_NAME, s as PREVIEW_CHROME_THEME_CLASS_NAME } from "./SdkPreviewModeRuntime-Bt87-62u.mjs";
 import * as React$1 from "react";
 import { useCallback, useEffect, useMemo, useState, useTransition } from "react";
 import { Fragment as Fragment$1, jsx, jsxs } from "react/jsx-runtime";