efficient-easel 0.101.1 → 0.103.0

package/dist/screen/components/AddChildRow.d.ts

@@ -0,0 +1,39 @@
+import * as react from 'react';
+
+/**
+ * AddChildRow — the single-type "Add …" affordance, in ONE place (card 66210).
+ *
+ * ONE ROW, TWO SURFACES. A slot-backed section's children can be added from the
+ * Layers tree and from the section's own settings panel, and each surface had
+ * written the button out itself: the same `.sf-add-card`, the same registry
+ * label, the same insert. That is exactly the shape card 66200 removed for the
+ * HETEROGENEOUS add ("Add block", now {@link AddBlockRow}); this is its
+ * single-type twin, and it is here for a sharper reason than tidiness.
+ *
+ * ⚠️ THE SECOND COPY WAS A SHIPPED DEFECT. Card 66189 gave a Hero slide's groups
+ * a cap — four on one anchor, because a fifth is drawn on top of the fourth —
+ * and wired the refusal into the panel's copy of this button. The tree's copy
+ * knew nothing about it, so a merchant could make the fifth group from the row
+ * sitting directly beside the four. Two buttons doing one job is how one of them
+ * gets a rule and the other does not.
+ *
+ * So the REASON is never computed here. The caller asks the section's own spec
+ * (`SlotSectionSpec.addBlocked`) and hands the answer down; this component only
+ * draws it. A surface that forgets to ask is then visibly a surface that passes
+ * `blocked={null}`, rather than a surface with its own quietly missing check.
+ *
+ * `disabled` rather than hidden, for the same reason as the Placement grid's
+ * closed square: an affordance that vanishes reads as a broken editor, while one
+ * that dims and explains itself reads as an answer.
+ */
+declare function AddChildRow({ label, blocked, onAdd, small, }: {
+    /** The registry's own "Add …" words — never composed here. */
+    label: string;
+    /** Why the section cannot take another child, or null. From its spec. */
+    blocked: string | null;
+    onAdd: () => void;
+    /** The Layers tree's smaller plus. Panel rows use the full-size one. */
+    small?: boolean;
+}): react.JSX.Element;
+
+export { AddChildRow as default };

package/dist/screen/components/AddChildRow.js

@@ -0,0 +1 @@
+export{AddChildRow as default}from"../../chunk-3QVB4AG2.js";

package/dist/screen/components/AddSidePanel.d.ts

@@ -0,0 +1,54 @@
+import * as react from 'react';
+import { ReactNode } from 'react';
+import { D as DragSession } from '../../session-DSQFmIvx.js';
+import { SectionTemplate } from '../lib/section-template-types.js';
+import { BlockChoice } from '../lib/puck/block-choice.js';
+import '../../types-41704JE4.js';
+import '../lib/puck/content-tree.js';
+
+/** What a tile adds, parsed back out of its key. */
+type AddKey = {
+    kind: "section";
+    type: string;
+} | {
+    kind: "template";
+    template: SectionTemplate;
+} | {
+    kind: "block";
+    type: string;
+};
+declare const sectionKey: (type: string) => string;
+declare const blockKey: (type: string) => string;
+declare const templateKey: (id: string) => string;
+type AddSidePanelProps<I> = {
+    /** The blocks a target container takes — the slot the panel was opened at,
+     *  or the selected container — or null. */
+    blocks: {
+        parentName: string;
+        choices: BlockChoice[];
+    } | null;
+    /** Opened at a slot: only that slot's blocks are offered. */
+    blocksOnly: boolean;
+    /** Where the next thing goes, when the panel was opened at a place. */
+    at?: {
+        label: string;
+        onClear: () => void;
+    };
+    /** Add what a tile names. */
+    onAdd: (key: AddKey) => void;
+    /** The drag item for what a tile names — a drag in the editor's session. */
+    itemFor: (key: AddKey) => I;
+    session: DragSession<I>;
+    /** A row under the tiles for something that is not a block, drawn by the
+     *  layer that owns it (the website: the Live chat bubble). Not shown where
+     *  only a slot's blocks are offered. */
+    siteWide?: ReactNode;
+    /** Leave Add — back to the view underneath (the head's "Done"). */
+    onClose: () => void;
+    /** Hide the left panel (the head's last button, as on every panel). */
+    onHide?: () => void;
+    readOnly?: boolean;
+};
+declare function AddSidePanel<I>({ blocks, blocksOnly, at, onAdd, itemFor, session, siteWide, onClose, onHide, readOnly, }: AddSidePanelProps<I>): react.JSX.Element;
+
+export { type AddKey, type AddSidePanelProps, blockKey, AddSidePanel as default, sectionKey, templateKey };

package/dist/screen/components/AddSidePanel.js

@@ -0,0 +1 @@
+export{blockKey,AddSidePanel as default,sectionKey,templateKey}from"../../chunk-OORDMLL4.js";import"../../chunk-5ZBY24K7.js";import"../../chunk-GENAF3P6.js";import"../../chunk-4MXFKJUY.js";import"../../chunk-IWAPPEL4.js";import"../../chunk-KQMML6JM.js";import"../../chunk-KDYIMJTZ.js";import"../../chunk-6TZTKAB5.js";import"../../chunk-AJBJ74ME.js";import"../../chunk-HQ4VVRIC.js";import"../../chunk-NBJ2YY6Y.js";import"../../chunk-P67FP7PG.js";import"../../chunk-AELNNAFM.js";import"../../chunk-BXZ6WLHC.js";import"../../chunk-EOJNJCMJ.js";import"../../chunk-ZFDCDJNZ.js";import"../../chunk-ZNS7727Y.js";import"../../chunk-3EDSDPIP.js";import"../../chunk-QTLAVDJE.js";import"../../chunk-YRLPFZW3.js";import"../../chunk-KTVH2ZRL.js";import"../../chunk-D2BCHTQR.js";import"../../chunk-6DJHRLCU.js";import"../../chunk-ZJEBF4NB.js";import"../../chunk-JUQ6YJCG.js";import"../../chunk-RE4LP46F.js";import"../../chunk-WZ7TGAAT.js";import"../../chunk-2OAZYSWJ.js";import"../../chunk-EWVJSRRY.js";import"../../chunk-P6O363EE.js";import"../../chunk-FPOKPNO4.js";import"../../chunk-MFIRYGHW.js";import"../../chunk-BZ5ASXOL.js";import"../../chunk-TTJ54QGG.js";import"../../chunk-O2NLQBFX.js";import"../../chunk-67GNT6PF.js";import"../../chunk-PAELDYYS.js";import"../../chunk-ZNCEOSXO.js";import"../../chunk-L5KW4HG5.js";import"../../chunk-KRXQM65X.js";import"../../chunk-NKB3KVAB.js";

package/dist/screen/components/MediaSidePanel.d.ts

@@ -0,0 +1,47 @@
+import * as react from 'react';
+import { MediaPanelComponent, MediaPickRequest } from '../lib/media-panel.js';
+import '../../host-DJ8Gzsx7.js';
+import '../../blocks/index.js';
+import '../../types-E3HrTPg2.js';
+import '../../data/index.js';
+import '../../types-41704JE4.js';
+import '../../resolve-D68pb3Bx.js';
+import '../../plan-DChbUXdS.js';
+import '../lib/document-contract.js';
+import '../lib/session.js';
+import '../lib/host-chrome.js';
+import '../lib/links/link-filters.js';
+import '../../LinkPicker-W2Rtxetz.js';
+import '../lib/document-hooks.js';
+import '../lib/section-template-types.js';
+import '../lib/puck/content-tree.js';
+import '../lib/document-switch.js';
+import '../../engine-DBxp_v6B.js';
+import '../../edit-lock/index.js';
+import '../lib/admin-bridge.js';
+
+/**
+ * The left panel's MEDIA view: efficient-easel's `MediaPanelHead` over the
+ * HOST's media library (lib/media-panel), the host's one Media Library
+ * drawn narrow.
+ *
+ * The head is the engine's, the same one the campaign designer draws over the
+ * same library (card [MERGE] One Media Panel Head For Both Editors, owner
+ * ruling 2026-10-06: a part exists once, in efficient-easel). Its words, its
+ * two states and its Cancel are all there; this file only maps the request:
+ *
+ *   • Browsing (`pick` null): "Media library", the website under it, and the
+ *     hide button every panel ends with.
+ *   • Choosing for a field: "Choose image / For Background image", and
+ *     "Cancel" (the field gets nothing and the panel goes back to what it
+ *     showed before). Hiding the panel cancels too.
+ */
+declare function MediaSidePanel({ panel: Panel, pick, onHide, }: {
+    panel: MediaPanelComponent;
+    pick: MediaPickRequest | null;
+    /** Hide the panel. Omitted where it cannot be hidden (the standalone section
+     *  editor), and then the head draws no hide button. */
+    onHide?: () => void;
+}): react.JSX.Element;
+
+export { MediaSidePanel as default };

package/dist/screen/components/MediaSidePanel.js

@@ -0,0 +1 @@
+export{MediaSidePanel as default}from"../../chunk-3M3A3DN2.js";import"../../chunk-ZZ7VLIHQ.js";import"../../chunk-NBJ2YY6Y.js";import"../../chunk-P67FP7PG.js";import"../../chunk-AELNNAFM.js";import"../../chunk-BXZ6WLHC.js";import"../../chunk-EOJNJCMJ.js";import"../../chunk-ZFDCDJNZ.js";import"../../chunk-ZNS7727Y.js";import"../../chunk-3EDSDPIP.js";import"../../chunk-QTLAVDJE.js";import"../../chunk-YRLPFZW3.js";import"../../chunk-KTVH2ZRL.js";import"../../chunk-D2BCHTQR.js";import"../../chunk-6DJHRLCU.js";import"../../chunk-ZJEBF4NB.js";import"../../chunk-JUQ6YJCG.js";import"../../chunk-RE4LP46F.js";import"../../chunk-WZ7TGAAT.js";import"../../chunk-2OAZYSWJ.js";import"../../chunk-EWVJSRRY.js";import"../../chunk-P6O363EE.js";import"../../chunk-FPOKPNO4.js";import"../../chunk-MFIRYGHW.js";import"../../chunk-BZ5ASXOL.js";import"../../chunk-67GNT6PF.js";import"../../chunk-ZNCEOSXO.js";import"../../chunk-L5KW4HG5.js";import"../../chunk-KRXQM65X.js";import"../../chunk-NKB3KVAB.js";

package/dist/screen/components/NodeContextMenu.d.ts

@@ -0,0 +1,364 @@
+import * as react from 'react';
+import { N as NodeClipboard, a as NodeOps } from '../../useNodeOps-BF0fQsif.js';
+import { E as EaselContextMenuItem } from '../../types-Djdq6Xkd.js';
+import { StyleSnapshot } from '../../style-clipboard/index.js';
+import { C as CanvasTarget } from '../../watch-BTYOJpQU.js';
+import { AddTarget } from '../lib/puck/add-target-types.js';
+import '../../types-41704JE4.js';
+import '../../plan-DChbUXdS.js';
+import '../../words-CnnHb9jo.js';
+import '../lib/puck/block-choice.js';
+import '../lib/puck/slot-section-spec.js';
+
+/**
+ * Where the menu is open, and WHAT it was opened on.
+ *
+ * Three kinds, because a right-click means three different things in an editor
+ * and one menu for all of them would be mostly greyed rows. The kind is decided
+ * once, at the event, by what is under the pointer — never guessed later.
+ */
+type NodeMenuTarget = 
+/** On a node: a Layers row, or its box on the canvas. */
+{
+    kind: "node";
+    x: number;
+    y: number;
+    zone: string;
+    index: number;
+}
+/** On editor chrome that is not a node — the tree's ground, the panel, the
+ *  canvas between sections. The menu is about the PAGE, not a block. */
+ | {
+    kind: "empty";
+    x: number;
+    y: number;
+}
+/** Inside something you type in. Text actions, not document ones. */
+ | {
+    kind: "input";
+    x: number;
+    y: number;
+    el: TextEl;
+};
+/** As much of an input as the text actions use. */
+type TextEl = {
+    value: string;
+    selectionStart: number | null;
+    selectionEnd: number | null;
+    setRangeText: (t: string, s: number, e: number, m?: string) => void;
+    select: () => void;
+    focus: () => void;
+    dispatchEvent: (e: Event) => boolean;
+};
+/**
+ * A node as the tree already models it — kept structural so this module does not
+ * import the chrome's own types and become a cycle.
+ *
+ * ⚠️ `id` IS REQUIRED, and that is the type checker's correction rather than my
+ * choice. The first cut wrote `props: Record<string, unknown>` and `tsc` refused
+ * it against `ops.replaceComponent`, whose `TreeItem` requires one. It is right:
+ * every node in the open document carries an id — it is what
+ * `data-puck-component` publishes and what `locate` reads back — so a node
+ * without one is a node the tree cannot address, and passing it to
+ * `replaceComponent` would write something unreachable.
+ */
+type NodeLike = {
+    type: string;
+    props: {
+        [key: string]: unknown;
+        id: string;
+    };
+};
+type NodeMenuHost = {
+    /** The nodes of `zone`, in order — for "is there anything above me". */
+    nodesIn: (zone: string) => NodeLike[];
+    /** The node at an address, or null if the address has gone stale. */
+    nodeAt: (zone: string, index: number) => NodeLike | null;
+    /** The merchant-facing name of a node type, in the ZONE it was found in — a
+     *  node in the ROOT zone is a section, a node in a slot is a block, and one
+     *  node is named differently at each (lib/puck/section-catalog labelAtLevel).
+     *  A host that does not care may still pass a one-argument function. */
+    labelOf: (type: string, zone: string) => string;
+    /**
+     * What the LAYERS TREE calls this node — its row's own words, not its type's.
+     *
+     * ⚠️ NOT `labelOf`, and the difference is the whole reason this exists. A Hero
+     * slide's tree row reads "Winter" because the merchant typed a slide name;
+     * `labelOf` would call it "Slide". The Select layer flyout lists the same
+     * nodes the tree lists, so it must say the same words — a menu that called
+     * something "Slide" while the tree three inches away called it "Winter" would
+     * be two vocabularies for one node, which is the thing card 66194 spent a
+     * whole card removing. The chrome already owns this rule
+     * (`lib/puck/slot-child-name.ts`, the ONE home) and hands it in.
+     */
+    rowNameOf: (node: NodeLike, zone: string) => string;
+    /**
+     * Can this node be renamed, and under which prop? `null` takes `Rename` out of
+     * the menu entirely — an item that opens a box writing nowhere is worse than
+     * no item.
+     *
+     * The chrome answers it through `slotChildRenameProp` (lib/puck/slot-child-name),
+     * the ONE home for what a child is called — the same module `rowNameOf` above
+     * already reads. It is handed in rather than looked up here for the reason
+     * everything else on this type is: this module is given nodes, never the config.
+     */
+    renamePropOf: (node: NodeLike, zone: string) => string | null;
+    /**
+     * Put the node's LAYERS ROW into its rename state — the tree owns the input,
+     * not the menu.
+     *
+     * ⚠️ THE MENU DOES NOT COLLECT THE NAME. A box drawn by the menu would be a
+     * second place to type a name, three inches from the row that shows it, and
+     * the owner deleted type-in-place on 2026-08-26 precisely to stop one string
+     * having two editors. The row a merchant is looking at is the row they type
+     * in, and this only asks for it.
+     */
+    beginRename: (zone: string, index: number) => void;
+    /** Undo / redo, as the toolbar already drives it. The menu is a SECOND door to
+     *  what a button and a key already do, never the only one. */
+    history: {
+        hasPast: boolean;
+        hasFuture: boolean;
+        back: () => void;
+        forward: () => void;
+    };
+    /** Open the Add door with nothing preselected — a new top-level section. */
+    openAddSection: () => void;
+    /** Put the panel on the page's own settings. */
+    openPageSettings: () => void;
+    /** Fold every section in the Layers tree. */
+    collapseAll: () => void;
+    /** Say, in the editor's own voice, that the browser refused clipboard reading
+     *  and ⌘V is the way. NOT a console warning: the merchant pressed a row and
+     *  something has to answer them. */
+    onPasteRefused: () => void;
+    /**
+     * A block that is what its section IS: it may be selected and edited, and
+     * never taken away or hidden (the Booking Form's three boxes). The host's
+     * answer, for the reason everything else on this type is handed in: this
+     * module is given nodes and is never told which blocks exist.
+     */
+    isLocked: (node: NodeLike) => boolean;
+    /**
+     * Why a second one of this node cannot be made, or null — a rule of the
+     * block's own (the hero's arithmetic: an anchor holds four groups). What
+     * cannot be made twice cannot be cut either.
+     */
+    duplicateBlocked: (node: NodeLike) => string | null;
+    /**
+     * What may be added inside a node of this type, or null for one that takes
+     * no children — the ONE add lookup, the host's (its block rules), for the
+     * reason the two above are handed in. Only whether there is an answer is
+     * read: a node with none has no "Add block inside" row.
+     */
+    canAddTo: (nodeType: string) => AddTarget | null;
+    /**
+     * The BLOCK OPERATIONS — `efficient-easel/node-ops`' `useNodeOps`, hosted by
+     * the chrome (blueprint step 2.4b). Every row that changes the document
+     * presses one of these, and nothing in this module mutates any other way.
+     *
+     * Each is ONE commit: planned whole on the document, written once through
+     * `use-section-ops`' `commitDocument` — behind the same read-only gate as
+     * every other mutation ("somebody else holds the open document") — with its
+     * selection by id, never by position. Before 2.4b two of them were several
+     * dispatches, and that is where both of this menu's worst bugs lived:
+     *
+     *   - DELETE was three (drop the node, reset the inspector mode, clear the
+     *     selection). This module once owned a copy with the middle one missing,
+     *     and deleting a section while one of its PARTS was engaged unmounted the
+     *     editor into "This page didn't load" (Lewis, 2026-09-07). The mode reset
+     *     now lives in the chrome's ONE commit: any operation that changes the
+     *     selection resets it, so no caller can leave it out.
+     *   - PASTE was two (insert, then fill), so two undo steps.
+     *
+     * Paste still clones with fresh ids — every address in the editor is an id,
+     * and a paste that kept the original's would put two nodes with one id in
+     * the document. `node-ops`' paste does that at every depth.
+     */
+    nodeOps: Pick<NodeOps, "held" | "remove" | "duplicate" | "step" | "canStep" | "setProps" | "copy" | "cut" | "paste">;
+    /**
+     * Is this node PINNED CHROME — the Header or the Footer section at the page's
+     * root? The Layers tree draws those two in groups of their own, with no
+     * delete, no eye and no grip; the canvas menu used to offer them Duplicate,
+     * Move, Cut, Hide and Delete anyway (blueprint step 2.4b). It now withholds
+     * exactly what the tree withholds, and says why.
+     */
+    isPinned: (node: NodeLike, zone: string) => boolean;
+    /**
+     * Where a SECTION may sit at the page root: after the pinned Header
+     * (`floor`) and before the pinned Footer (`cap`) — the chrome's `sectionBand`,
+     * the one home the add and drag clamps already read. A section pasted at the
+     * root lands inside it; Move up / Move down never leave it.
+     */
+    sectionBand: () => {
+        floor: number;
+        cap: number;
+    };
+    /**
+     * Select a node the way the LAYERS TREE selects it — the tree's own two
+     * handlers, not a third one.
+     *
+     * ⚠️ Selecting is not one action, it is two, and the difference is visible.
+     * A top-level node goes through `selectIndex` (inspector mode, the Locations
+     * focus reset, scroll the preview to it); a slot child goes through
+     * `selectChild`, which for a SLIDER parent must move the carousel to that
+     * slide BEFORE selecting, or Puck measures its overlay on an off-screen slide
+     * and the canvas grows a horizontal scrollbar. Neither is restated here. The
+     * `parentType` is what the slider question is asked of, so the chain hands it
+     * down rather than the chrome looking it up a second time.
+     */
+    selectAt: (zone: string, index: number, id: string, parentType: string | null) => void;
+    /** Open the Add door for a parent that can take children. The chrome owns
+     *  WHERE a new node lands (`placementIndex`); this only asks it to open. */
+    openAddInside: (zone: string, index: number) => void;
+    /**
+     * Turn a `data-puck-component` id into an address.
+     *
+     * The chrome owns this because the address is a fact about the OPEN DOCUMENT
+     * (which zone, which index) and this module is handed nodes, not the tree. The
+     * canvas hands us the id the browser says was clicked, so the node the menu
+     * ACTS on is the node the browser says was hit — with no second hit-test that
+     * could disagree.
+     */
+    locate: (id: string) => {
+        zone: string;
+        index: number;
+    } | null;
+    /**
+     * COPY STYLE / PASTE STYLE (card [ADD] Copy Style And Paste Style). The rows,
+     * their words and glyphs are editor-shell's; the chrome answers the rest —
+     * which rows are a look (lib/puck/style-clipboard), the site's scope, and the
+     * toast. Optional: a host without it offers neither row.
+     *
+     * ⚠️ `paste` writes through the chrome's `ops.replaceComponent`, the one op
+     * behind the READ-ONLY gate — this module still dispatches nothing itself.
+     */
+    style?: {
+        held: () => StyleSnapshot | null;
+        canCopy: (node: NodeLike, zone: string) => boolean;
+        copy: (node: NodeLike, zone: string) => void;
+        paste: (zone: string, index: number, node: NodeLike) => void;
+    };
+};
+/** One rung of the stack under the pointer: a node, and where it lives. */
+type ChainRung = {
+    zone: string;
+    index: number;
+    node: NodeLike;
+    parentType: string | null;
+};
+/**
+ * The stack of nodes under the pointer, INNERMOST FIRST.
+ *
+ * ── WHY THIS EXISTS ─────────────────────────────────────────────────────────
+ * A canvas click selects the innermost thing under the pointer, because that is
+ * the element the browser says was hit. Once nesting is a few deep — Text inside
+ * a Box inside a Slide inside a Hero Slideshow — the outer three have no free
+ * pixels left to click, so they are not merely hard to select but UNREACHABLE
+ * from the canvas. Lewis asked for the fix on 2026-09-03 and chose this reading
+ * of it — the stack under the cursor, not a jump to the Layers tree.
+ *
+ * ── HOW A PARENT IS FOUND, AND WHY NOTHING NEW IS INTRODUCED ────────────────
+ * A zone is `<parentId>:<slot>` (the chrome's own words, and `ROOT_ZONE` is the
+ * literal `root:default-zone`). So the parent's ID is already written on the
+ * child's address, and walking up is `locate` on that id — the SAME lookup the
+ * canvas uses to turn a right-clicked element into an address. No second tree
+ * walk, no second idea of what contains what, and therefore no way for the two
+ * to disagree.
+ *
+ * ⚠️ THE ID IS TAKEN FROM THE LAST COLON, not the first. A node id is
+ * `${type}-${uuid}` (`newNodeId`) and carries no colon of its own today — but a
+ * slot NAME is a plain identifier and never will, while a type is somebody
+ * else's string. Splitting on the first colon is right only by luck; splitting
+ * on the last is right by construction.
+ *
+ * Ends at the root zone. `seen` is not defensive tidiness about cycles — a tree
+ * has none — it stops a STALE address (a node deleted between the right-click
+ * and the render) from resolving back onto something already in the chain and
+ * spinning the loop forever, which would hang the editor rather than draw a
+ * short menu.
+ */
+declare function ancestorChain(host: NodeMenuHost, target: {
+    zone: string;
+    index: number;
+}): ChainRung[];
+/**
+ * THE BLOCK CLIPBOARD — one node, held by us, for the whole tab.
+ *
+ * Owner 2026-09-04, asked whether we could do copy and paste ourselves: for a
+ * BLOCK we can, completely, and with no browser permission at all — the thing
+ * being copied is our own document node, not the operating system's clipboard.
+ * (Text paste is the one that is not free; see {@link textMenuItems}.)
+ *
+ * Module-level, and deliberately not React state: the clipboard outlives every
+ * menu that reads it, and putting it in the hook would give each mounted editor
+ * its own — copy in one and paste in another would silently do nothing. Since
+ * blueprint step 2.4b it is `efficient-easel/node-ops`' clipboard, which the
+ * chrome hands its `useNodeOps`; an entry remembers the zone it came from
+ * (`from`), because "may this paste here" is a question about the type and its
+ * destination.
+ */
+declare const EASEL_NODE_CLIPBOARD: NodeClipboard;
+/**
+ * Build the rows for one node.
+ *
+ * Pure, and handed everything it needs — so a test can pass spies and assert,
+ * row by row, which operation each row presses.
+ *
+ * Since blueprint step 2.4b the ROWS THEMSELVES — their order, their groups,
+ * their words, glyphs and shortcuts — are `efficient-easel/node-ops`'
+ * `nodeMenuItems`, the one menu both editors draw (the campaign designer moved
+ * onto it in 2.3b). They were drawn from this module's own list, which is where
+ * that shared one was copied from, so nothing moves. What stays HERE is which
+ * rows this node gets: a row is offered by passing its action, and every rule
+ * below is the storefront's.
+ */
+declare function nodeMenuItems(host: NodeMenuHost, target: {
+    zone: string;
+    index: number;
+}): EaselContextMenuItem[];
+/**
+ * What a right-click on the PAGE offers — the tree's ground, the panel, the
+ * canvas between two sections.
+ *
+ * This ground used to fall through to Chrome, which is half of what the owner
+ * was pointing at: a right-click that sometimes gives you the editor and
+ * sometimes gives you Reload teaches you not to right-click at all.
+ *
+ * Everything here already exists on a button or a key. That is on purpose — a
+ * context menu is a second door to actions a merchant can already reach, never
+ * the only door to one, or the feature is hidden inside a gesture.
+ */
+declare function pageMenuItems(host: NodeMenuHost): EaselContextMenuItem[];
+/**
+ * What a right-click INSIDE A TEXT BOX offers.
+ *
+ * ── THE ONE ROW THAT IS NOT FREE ─────────────────────────────────────────────
+ * Copy, Cut and Select all are ours outright. PASTE is not: reading the system
+ * clipboard needs the browser's `clipboard-read` permission, Chrome asks once,
+ * and a merchant who says no would have a Paste row that is dead for ever while
+ * ⌘V keeps working perfectly.
+ *
+ * So Paste TRIES, and on refusal turns into the shortcut instead — the row is
+ * never a button that does nothing. That is the whole reason `onPasteRefused`
+ * is a host callback rather than a `console.warn`: the merchant has to be told
+ * something, and this module does not own the editor's way of saying it.
+ */
+declare function textMenuItems(host: NodeMenuHost, el: TextEl): EaselContextMenuItem[];
+/**
+ * Wire the menu to both surfaces and render it.
+ *
+ * Returns ONE `onContextMenu` for the whole Layers tree, and the element to
+ * render. Per-row handlers are deliberately gone — see {@link onTreeContextMenu}.
+ *
+ * `canvas` is the editor's canvas frame (`efficient-easel/canvas`
+ * `useCanvasFrame`, found once by the chrome) — null until Puck has drawn into
+ * it. The canvas half below listens on it.
+ */
+declare function useNodeContextMenu(host: NodeMenuHost, canvas: CanvasTarget | null): {
+    onEditorContextMenu: (e: React.MouseEvent) => void;
+    menu: react.JSX.Element | null;
+    closeMenu: () => void;
+};
+
+export { type ChainRung, EASEL_NODE_CLIPBOARD, type NodeMenuHost, type NodeMenuTarget, ancestorChain, nodeMenuItems, pageMenuItems, textMenuItems, useNodeContextMenu };

package/dist/screen/components/NodeContextMenu.js

@@ -0,0 +1 @@
+export{EASEL_NODE_CLIPBOARD,ancestorChain,nodeMenuItems,pageMenuItems,textMenuItems,useNodeContextMenu}from"../../chunk-F6CCTEIX.js";import"../../chunk-FUDHI5I4.js";import"../../chunk-57DJOKXT.js";import"../../chunk-6WY6ZXJG.js";import"../../chunk-RW4XBUUW.js";import"../../chunk-KTVH2ZRL.js";import"../../chunk-2LK54I4E.js";import"../../chunk-WK3AFPXY.js";import"../../chunk-D2BCHTQR.js";import"../../chunk-PAELDYYS.js";import"../../chunk-ZNCEOSXO.js";import"../../chunk-L5KW4HG5.js";import"../../chunk-KRXQM65X.js";import"../../chunk-NKB3KVAB.js";

package/dist/screen/components/PageEditGuardNotices.d.ts

@@ -0,0 +1,5 @@
+import * as react from 'react';
+
+declare function PageEditGuardNotices(): react.JSX.Element | null;
+
+export { PageEditGuardNotices as default };

package/dist/screen/components/PageEditGuardNotices.js

@@ -0,0 +1 @@
+export{PageEditGuardNotices as default}from"../../chunk-LG436UTD.js";import"../../chunk-YJXEHK6I.js";import"../../chunk-7MU3RJ6S.js";import"../../chunk-A7ZJII7O.js";import"../../chunk-6FY3PZS3.js";import"../../chunk-AKZWUV5Z.js";import"../../chunk-RLBXE4EU.js";import"../../chunk-OYX47SL7.js";import"../../chunk-HMX55DYT.js";import"../../chunk-Q3SQBNJB.js";import"../../chunk-3WSPDAK2.js";import"../../chunk-R5ZVNJLJ.js";import"../../chunk-KDYIMJTZ.js";import"../../chunk-6TZTKAB5.js";import"../../chunk-AJBJ74ME.js";import"../../chunk-ZZ7VLIHQ.js";import"../../chunk-ZWK3CBRU.js";import"../../chunk-BDTITTMW.js";import"../../chunk-H6DDIBQ4.js";import"../../chunk-6DJHRLCU.js";import"../../chunk-ZJEBF4NB.js";import"../../chunk-JUQ6YJCG.js";import"../../chunk-RE4LP46F.js";import"../../chunk-WZ7TGAAT.js";import"../../chunk-2OAZYSWJ.js";import"../../chunk-MFIRYGHW.js";import"../../chunk-BZ5ASXOL.js";import"../../chunk-L5KW4HG5.js";

package/dist/screen/components/PanelToggleIcon.d.ts

@@ -0,0 +1,14 @@
+import * as react from 'react';
+
+/**
+ * The picture of ONE side panel: a window with its left or right column ruled
+ * off. It is the Hide panel button at the end of that panel's head and the
+ * Show panel button in the strip a hidden panel leaves (components/
+ * SidePanelHead) — one control, so one drawing. It was the top bar's two
+ * panel toggles until those went (2026-10-04).
+ */
+declare function PanelToggleIcon({ side }: {
+    side: "left" | "right";
+}): react.JSX.Element;
+
+export { PanelToggleIcon as default };

package/dist/screen/components/PanelToggleIcon.js

@@ -0,0 +1 @@
+export{PanelToggleIcon as default}from"../../chunk-KQMML6JM.js";

package/dist/screen/components/PreviewDeviceContext.d.ts

@@ -0,0 +1,28 @@
+import * as react from 'react';
+import { ViewTier } from '../lib/content/view-tiers.js';
+
+/**
+ * PreviewDeviceContext — the editor's current preview device.
+ *
+ * The storefront editor chrome (ScreenChrome) owns a Desktop / Tablet
+ * / Mobile switcher in its top bar (local `device` state, rendered at logical
+ * widths 2000 / 800 / 390). That switcher — NOT Puck's built-in viewports — is
+ * what resizes the preview iframe, so viewport-aware inspector fields must read
+ * IT to know which view the merchant is editing. The chrome lends its live
+ * `device` to the website layer, which provides it here
+ * (components/WebsiteScreenParts); fields (e.g. the Footer's "Logo fills its
+ * column" toggle) read it via usePreviewDevice().
+ *
+ * Defaults to "desktop" outside the chrome (e.g. a bare field harness), matching
+ * the chrome's own initial device.
+ *
+ * The device IS a `ViewTier` — the switcher, the per-view fields and the runtime
+ * grids have to name the same three views or a control sets a tier nothing
+ * renders, so the union has one home (lib/content/view-tiers) and this is an
+ * alias for the editor's word for it.
+ */
+type PreviewDevice = ViewTier;
+declare const PreviewDeviceContext: react.Context<ViewTier>;
+declare const usePreviewDevice: () => PreviewDevice;
+
+export { type PreviewDevice, PreviewDeviceContext, usePreviewDevice };

package/dist/screen/components/PreviewDeviceContext.js

@@ -0,0 +1 @@
+export{PreviewDeviceContext,usePreviewDevice}from"../../chunk-BSPCSC45.js";

package/dist/screen/components/PreviewPartsContext.d.ts

@@ -0,0 +1,33 @@
+import { PreviewIdSelection } from '../lib/puck/preview-selection-context.js';
+import * as react from 'react';
+
+/**
+ * Editor-preview SELECTION bridge for a section's PARTS — the headline, the
+ * body, the eyebrow a merchant clicks in the canvas to edit that one thing.
+ *
+ * The GENERAL member of a family the editor already had three hand-wired
+ * instances of (a Hero's ticker, a HeroSingle's Background and its Text). Those
+ * three each bridge ONE region of ONE section and name it in code; this one
+ * bridges any authored-text prop of any section, because what is clickable is
+ * derived from the config's own text fields (`lib/puck/text-parts.ts`) rather
+ * than listed.
+ *
+ * That is also why it is a fourth context and not a rewrite of the three: their
+ * regions carry NO Puck fields at all (a HeroSingle's copy and a Hero's ticker
+ * items are props with bespoke panels and no field declarations), so a
+ * field-derived bridge cannot see them and the two mechanisms provably never
+ * claim the same element. See the card report for why retiring them is its own
+ * piece of work.
+ *
+ * The payload is ONE string — `"<nodeId>::<propKey>"`, or `"<nodeId>::"` for the
+ * whole section — so the shared {@link createPreviewSelectionContext} factory
+ * fits unchanged; `encodePartId`/`decodePartId` own that spelling. Provider sits
+ * ABOVE <Puck> so its value reaches BOTH the chrome (which registers the select
+ * handler and mirrors the open panel back) AND the portaled preview iframe.
+ */
+declare const PreviewPartsProvider: ({ children }: {
+    children: react.ReactNode;
+}) => react.JSX.Element;
+declare const usePreviewParts: () => PreviewIdSelection<"selectedPartId">;
+
+export { PreviewPartsProvider, usePreviewParts };

package/dist/screen/components/PreviewPartsContext.js

@@ -0,0 +1 @@
+export{PreviewPartsProvider,usePreviewParts}from"../../chunk-I54UCYOU.js";import"../../chunk-GOTN2KY4.js";import"../../chunk-R5L2E7JX.js";

package/dist/screen/components/ScreenChrome.d.ts

@@ -0,0 +1,5 @@
+import { ReactNode } from 'react';
+
+declare function ScreenChrome(): ReactNode;
+
+export { ScreenChrome as default };

package/dist/screen/components/ScreenChrome.js

@@ -0,0 +1 @@
+export{ScreenChrome as default}from"../../chunk-HDKTR5TZ.js";import"../../chunk-26OOWIJJ.js";import"../../chunk-Q2HPBMG5.js";import"../../chunk-FGNR22NY.js";import"../../chunk-ZE7I3PLX.js";import"../../chunk-AKFJK65Z.js";import"../../chunk-PWZOS45R.js";import"../../chunk-7F52SZOI.js";import"../../chunk-R2HLPNQF.js";import"../../chunk-HWW4XJOH.js";import"../../chunk-4ES5JGGX.js";import"../../chunk-IQ5TA7AM.js";import"../../chunk-DUVRZ456.js";import"../../chunk-6W7WLPZH.js";import"../../chunk-OM67AJQC.js";import"../../chunk-KCBEE2MC.js";import"../../chunk-5MZ3RNQQ.js";import"../../chunk-SERF2FAU.js";import"../../chunk-GXN65JMA.js";import"../../chunk-VV5ADNBR.js";import"../../chunk-IYT6NN2J.js";import"../../chunk-F6CCTEIX.js";import"../../chunk-FUDHI5I4.js";import"../../chunk-LG436UTD.js";import"../../chunk-BSPCSC45.js";import"../../chunk-I54UCYOU.js";import"../../chunk-GOTN2KY4.js";import"../../chunk-R5L2E7JX.js";import"../../chunk-YJXEHK6I.js";import"../../chunk-7MU3RJ6S.js";import"../../chunk-A7ZJII7O.js";import"../../chunk-6FY3PZS3.js";import"../../chunk-AKZWUV5Z.js";import"../../chunk-RLBXE4EU.js";import"../../chunk-OYX47SL7.js";import"../../chunk-HMX55DYT.js";import"../../chunk-Q3SQBNJB.js";import"../../chunk-3WSPDAK2.js";import"../../chunk-R5ZVNJLJ.js";import"../../chunk-57DJOKXT.js";import"../../chunk-3QVB4AG2.js";import"../../chunk-OORDMLL4.js";import"../../chunk-5ZBY24K7.js";import"../../chunk-GENAF3P6.js";import"../../chunk-4MXFKJUY.js";import"../../chunk-IWAPPEL4.js";import"../../chunk-KQMML6JM.js";import"../../chunk-KDYIMJTZ.js";import"../../chunk-6TZTKAB5.js";import"../../chunk-AJBJ74ME.js";import"../../chunk-HQ4VVRIC.js";import"../../chunk-3M3A3DN2.js";import"../../chunk-ZZ7VLIHQ.js";import"../../chunk-NBJ2YY6Y.js";import"../../chunk-6WY6ZXJG.js";import"../../chunk-ZWK3CBRU.js";import"../../chunk-P67FP7PG.js";import"../../chunk-AELNNAFM.js";import"../../chunk-BXZ6WLHC.js";import"../../chunk-EOJNJCMJ.js";import"../../chunk-ZFDCDJNZ.js";import"../../chunk-ZNS7727Y.js";import"../../chunk-3EDSDPIP.js";import"../../chunk-QTLAVDJE.js";import"../../chunk-YRLPFZW3.js";import"../../chunk-RW4XBUUW.js";import"../../chunk-KTVH2ZRL.js";import"../../chunk-2LK54I4E.js";import"../../chunk-WK3AFPXY.js";import"../../chunk-D2BCHTQR.js";import"../../chunk-OWBO4WKA.js";import"../../chunk-BDTITTMW.js";import"../../chunk-H6DDIBQ4.js";import"../../chunk-6DJHRLCU.js";import"../../chunk-ZJEBF4NB.js";import"../../chunk-JUQ6YJCG.js";import"../../chunk-RE4LP46F.js";import"../../chunk-WZ7TGAAT.js";import"../../chunk-2OAZYSWJ.js";import"../../chunk-EWVJSRRY.js";import"../../chunk-P6O363EE.js";import"../../chunk-FPOKPNO4.js";import"../../chunk-MFIRYGHW.js";import"../../chunk-BZ5ASXOL.js";import"../../chunk-TTJ54QGG.js";import"../../chunk-O2NLQBFX.js";import"../../chunk-67GNT6PF.js";import"../../chunk-PAELDYYS.js";import"../../chunk-ZNCEOSXO.js";import"../../chunk-L5KW4HG5.js";import"../../chunk-KRXQM65X.js";import"../../chunk-NKB3KVAB.js";