@sevenfold/setto-client 0.14.0 → 0.15.0

package/dist/chrome.d.ts

@@ -71,6 +71,8 @@ export interface SettoChromeHandshake {
         } | null;
         sitesLoaded: boolean;
         editMode: boolean;
+        /** A signed-out visitor trying the editor on setto.no. */
+        guestEdit: boolean;
         authLoading: boolean;
     };
     /** Told whenever that state changes. Returns an unsubscribe. */

package/dist/guest-edit.d.ts

@@ -1,16 +1,22 @@
-import { type ReactNode } from 'react';
-interface GuestEditContextValue {
-    active: boolean;
-    start: () => void;
-    stop: () => void;
-}
+import type { ReactNode } from 'react';
 /**
  * Lets visitors inline-edit a marketing site (e.g. setto.no) without auth —
  * text, section/block colours, icons and list items. Changes are session-only
  * and never published. Real Setto edit mode always takes precedence.
+ *
+ * A provider in name only since 2026-09-09: the state moved into the main
+ * context so the chrome could see it, and what is left here is the one thing
+ * guest mode adds — the section toolbar, over a page nobody is signed in to.
+ * The component comes from Setto like the rest of the editing chrome, so there
+ * is nothing to draw until it arrives, and nothing to draw at all if it does
+ * not. That is the right failure for a demo.
  */
 export declare function GuestEditProvider({ children }: {
     children: ReactNode;
 }): import("react/jsx-runtime").JSX.Element;
+export interface GuestEditContextValue {
+    active: boolean;
+    start: () => void;
+    stop: () => void;
+}
 export declare function useGuestEdit(): GuestEditContextValue;
-export {};

package/dist/index.d.ts

@@ -36,6 +36,8 @@ export { BLOCK_REGISTRY, BLOCK_TYPES, nodeChildren } from './block-tree/registry
 export type { BlockTypeMeta } from './block-tree/registry';
 export { SETTO_BASE, siteHomeUrl, isAdminRoute, isAdminDeploymentView, adminViewUrl, currentAdminView, isAdminPanelView, adminRedirectUrl, CHECKOUT_INTENT, checkoutIntentUrl, wantsCheckout, withoutCheckoutIntent, } from './lib/urls';
 export { SettoMark } from './edit-mode/setto-mark';
+export { isLinkContext } from './lib/link-context';
+export { useCoarsePointer } from './lib/use-coarse-pointer';
 export { FAB_SIZE, FAB_INSET } from './edit-mode/constants';
 export { EMPTY_I18N_STORE_SNAPSHOT } from './lib/i18n-store';
 export type { I18nStoreSnapshot } from './lib/i18n-store';

package/dist/provider.d.ts

@@ -25,6 +25,18 @@ export interface SettoContextValue {
     store: I18nStore | null;
     themeStore: ThemeStore | null;
     assetStore: AssetStore | null;
+    /** The section the editor has selected, or null. */
+    selectedSectionId: string | null;
+    selectSection: (id: string | null) => void;
+    /**
+     * True while a signed-out visitor is trying the editor (setto.no).
+     *
+     * Here beside `editMode` rather than in `GuestEditProvider`'s own context
+     * for the same reason the selected section is: the chrome that draws the
+     * section toolbar sits above that provider and can call only `useSetto`.
+     */
+    guestEdit: boolean;
+    setGuestEdit: (on: boolean) => void;
 }
 /**
  * Exported for one caller: the chrome bundle.

package/dist/section-context.d.ts

@@ -1,10 +1,15 @@
-import { type ReactNode } from 'react';
-interface SectionEditContextValue {
+/**
+ * Which section the editor has selected.
+ *
+ * A context of its own until 2026-09-09, when the section toolbar moved out to
+ * the chrome served by setto-server. That bundle can call exactly one hook of
+ * the host's — `useSetto` — so the state moved into the main context and this
+ * became an adapter. Kept because `SettoSection` and `SettoBlock` read it on
+ * every render of every page, and renaming that in thirteen pinned sites buys
+ * nothing.
+ */
+export interface SectionEditContextValue {
     selectedId: string | null;
     selectSection: (id: string | null) => void;
 }
-export declare function SectionEditProvider({ children }: {
-    children: ReactNode;
-}): import("react/jsx-runtime").JSX.Element;
 export declare function useSectionEdit(): SectionEditContextValue;
-export {};