efficient-easel 20.2.1 → 21.1.0

package/dist/screen/lib/document/text-control-kinds.d.ts

@@ -0,0 +1,71 @@
+/**
+ * text-control-kinds — the authored-text control kinds, and the ONE fact about
+ * each that three separate lists used to hold by hand (card 66286).
+ *
+ * A LEAF ON PURPOSE: it imports nothing. `lib/document/controls` is nine hops deep in
+ * a require cycle back to `lib/document/part-text`
+ * (controls → MediaUploadField → ScreenDocumentContext →
+ * catalog-default-layout → ProductGridSection → goldPhrases → PartStyledText →
+ * part-styles → part-rows → part-text), so a list defined in `controls` and read
+ * at another module's INIT time throws "Cannot access before initialization".
+ * The cycle never bit before because the values `part-text` takes from `controls`
+ * — `TEXT_FIELD_MARKER`, `readHidable` — are only read inside functions. A
+ * single source has to be readable at init, so it lives here, on its own, where
+ * nothing can be in flight ahead of it.
+ *
+ * `lib/document/controls` re-exports every name below, because that is where the rest
+ * of the text-field vocabulary lives (`TEXT_FIELD_MARKER`, `TextFieldMeta`, the
+ * builders) and every existing caller already reads it from there. The
+ * definitions are here and only here.
+ */
+/**
+ * Every authored-text control kind, as recorded on `TEXT_FIELD_MARKER`
+ * (`lib/document/controls`),
+ * and the one fact three separate lists used to hold by hand (card 66286):
+ * whether the kind's value is ONE string a merchant edits as a single box
+ * (`"scalar"`), or N of them a control adds, removes and reorders (`"list"`).
+ *
+ * ⚠️ THIS IS THE SOURCE. {@link TextControlKind} and {@link SCALAR_TEXT_CONTROLS}
+ * are both read off it, so a sixth kind cannot be added without answering the
+ * scalar/list question once, here, where the answer is. Until this card it was
+ * answered THREE times in three files, kept in step by a comment asking the next
+ * reader to remember: which parts get an entry row on the section screen
+ * (`ENTRY_CONTROLS`), which copy boxes move to the drill (`DRILL_TEXT_CONTROLS`),
+ * and which parts a caret may be opened in (`TYPE_IN_PLACE_KINDS`). All three
+ * were the same question and nothing went red when they disagreed — card 66282
+ * added `copyText` to one of them first and the drift surfaced afterwards as
+ * `1 unreachable: altName`.
+ *
+ * `control` also fixes the STORED VALUE SHAPE the neutralizer must preserve, so
+ * each kind names its own shape beside it.
+ */
+declare const TEXT_CONTROL_KINDS: {
+    readonly text: "scalar";
+    readonly textarea: "scalar";
+    readonly plainText: "scalar";
+    readonly copyText: "scalar";
+    readonly plainTextarea: "scalar";
+    readonly textList: "list";
+};
+/** The authored-text control kinds — the keys of {@link TEXT_CONTROL_KINDS}. */
+type TextControlKind = keyof typeof TEXT_CONTROL_KINDS;
+/** The kinds whose value is ONE string, as a type — so a caller may hold one of
+ *  those and not the list kind, which the compiler then keeps it to. */
+type ScalarTextControlKind = {
+    [K in TextControlKind]: (typeof TEXT_CONTROL_KINDS)[K] extends "scalar" ? K : never;
+}[TextControlKind];
+/**
+ * THE SCALAR CONTROLS, derived — one string each, so one box, so one row.
+ *
+ * The three lists this replaces all named exactly these and each stated the same
+ * reason for leaving `textList` out: its control manages ROW STRUCTURE (add,
+ * remove, reorder), which a per-row box cannot, so it keeps its place on the
+ * section screen. That reason is now the `"list"` beside it above, stated once.
+ *
+ * Order is declaration order, and the section screen's rows are built by walking
+ * a section's FIELDS rather than this list, so nothing merchant-facing reads it
+ * as an ordering.
+ */
+declare const SCALAR_TEXT_CONTROLS: readonly ScalarTextControlKind[];
+
+export { SCALAR_TEXT_CONTROLS, type ScalarTextControlKind, TEXT_CONTROL_KINDS, type TextControlKind };

package/dist/screen/lib/document/text-control-kinds.js

@@ -0,0 +1 @@
+export{SCALAR_TEXT_CONTROLS,TEXT_CONTROL_KINDS}from"../../../chunk-I6SK6ZDT.js";

package/dist/screen/lib/document/tree-reveal.d.ts

@@ -0,0 +1,62 @@
+/** Puck's index-based address, as `use-section-ops` spells it (zone omitted at root). */
+type Selector = {
+    index: number;
+    zone?: string;
+} | null;
+/**
+ * Do these two addresses name the same node?
+ *
+ * `ops.select` omits the zone for a top-level node (Puck's reducer falls back to
+ * the root zone), while `getSelectorForId` always fills it in — so the two
+ * spellings of one top-level node differ, and the comparison has to normalise
+ * before it can answer. Exported for `scripts/test-tree-reveal.ts`.
+ */
+declare function sameSelector(a: Selector, b: Selector, rootZone: string): boolean;
+/**
+ * Bring the selected Layers row into view. Returns whether a row was found —
+ * false whenever the panel is collapsed or on another view, which is a no-op and
+ * not a failure. A row that is already fully visible is found and left alone:
+ * the return says "there is a row", not "the panel moved".
+ */
+declare function revealSelectedTreeRow(doc?: Document | undefined): boolean;
+/**
+ * Which node's Layers row is the MARKED one — the row that draws `is-selected`,
+ * and so the row {@link revealSelectedTreeRow} scrolls to.
+ *
+ * TWO SOURCES, ONE ANSWER. Normally it is the Puck selection. While a PART
+ * panel is open it is that part's OWNER, because `usePartBridge` deliberately
+ * leaves the Puck selection where it was — "the Layers tree, undo, redo and
+ * autosave therefore see nothing at all", which is that bridge's own cheapest
+ * proof that they still behave. The chrome asked `isPuckMode && selectedItem`
+ * instead, and `isPuckMode` is false in part mode, so opening a part put the
+ * mark out on EVERY row at once: a merchant who clicked a run of text in the
+ * canvas was left looking at a Layers list with nothing lit, which had also not
+ * moved (owner, 2026-09-09 — the "SHOP" tag on a Collections card). The bridge
+ * has returned `openPartId` for exactly this since card 66268 and no shell ever
+ * read it.
+ *
+ * EVERY OTHER OVERRIDE STILL ANSWERS `null` — Header, Website, Live chat and the
+ * ticker. Those panels are not about a node in this tree at all, and the rows
+ * that DO mark them (`inspectorMode.kind === "header"`, `tickerHeroId === secId`,
+ * …) read their own state, which is why widening this to them would light two
+ * rows for one panel.
+ *
+ * ⚠️ THE HERO'S `Text` / `Background` WERE ON THIS LIST AND ARE GONE
+ * ([ADD] The Hero Takes Boxes). They were two SYNTHETIC rows standing for the
+ * section's own copy and media; the owner put the background back in the hero's
+ * settings on 2026-09-09 and deleted the built-in copy, so both panels and both
+ * `…SectionId` derivations went with them. The example above named
+ * `heroTextSectionId`, a variable that no longer exists — corrected to the ticker
+ * rather than dropped, because the RULE it illustrates is unchanged and this is
+ * the only place that states it.
+ *
+ * The mode is taken structurally rather than as `InspectorMode`: that union
+ * lives in a component (SectionEditor) and this is `lib`, so a named import
+ * here would point the dependency the wrong way for one field.
+ */
+declare function markedTreeNodeId(mode: {
+    kind: string;
+    nodeId?: string;
+}, selectedId: string | null | undefined): string | null;
+
+export { markedTreeNodeId, revealSelectedTreeRow, sameSelector };

package/dist/screen/lib/document/tree-reveal.js

@@ -0,0 +1 @@
+export{markedTreeNodeId,revealSelectedTreeRow,sameSelector}from"../../../chunk-U5DNBT63.js";

package/dist/screen/lib/document/use-section-ops.d.ts

@@ -0,0 +1,110 @@
+import { N as NodeSelection } from '../../../plan-CZS902DV.js';
+import { Data } from '../../../blocks/index.js';
+import { TreeItem } from './content-tree.js';
+import '../../../types-41704JE4.js';
+import 'react';
+import '../../../types-Cq53lL8d.js';
+import '../../../data/index.js';
+import '../../../resolve-D68pb3Bx.js';
+
+type NodeSelector = {
+    index: number;
+    zone?: string;
+} | null;
+type ComponentData = TreeItem;
+type SectionOps = {
+    /** Insert a component into a zone at an index; returns the generated id. */
+    insertComponent: (zone: string, type: string, index: number) => string;
+    /** Insert into ROOT_ZONE (top-level section); returns the generated id. */
+    insertSection: (type: string, index: number) => string;
+    /** Atomically replace the node at (zone, index) — heal, reseed, hide toggle. */
+    replaceComponent: (zone: string, index: number, data: ComponentData) => void;
+    /** Seed a freshly-inserted slot child's props (insert THEN replace at a stable id). */
+    seedChild: (zone: string, index: number, childType: string, props: Record<string, unknown>) => void;
+    /**
+     * Insert a FULL node — type + props, including inline slot children — at
+     * (zone, index); returns its id. The same insert-then-replace pattern as
+     * seedChild, one level up: how a saved section template lands in a page.
+     * Callers pass a node whose ids are already fresh (cloneNodeWithFreshIds).
+     */
+    insertNode: (zone: string, index: number, node: TreeItem) => string;
+    /** Remove the node at (zone, index). A normal dispatch, so Undo restores it. */
+    removeComponent: (zone: string, index: number) => void;
+    /**
+     * Move the node at (zone, sourceIndex) to destinationIndex WITHIN THE SAME
+     * zone. `destinationIndex` is the node's final resting index in the array
+     * (Puck's `reorder` reducer splices it out then back in), so a caller moving a
+     * node DOWN must account for the one-slot shift itself.
+     */
+    reorderComponent: (zone: string, sourceIndex: number, destinationIndex: number) => void;
+    /** Duplicate the node at (zone, index). */
+    duplicateComponent: (zone: string, index: number) => void;
+    /** Set (or clear) the Puck selection by index-based address. */
+    select: (selector: NodeSelector) => void;
+    /** Replace the whole working document (used by Reset). */
+    setDocument: (data: Data) => void;
+    /**
+     * Write the next document, and what to select in it, as ONE undo step — the
+     * commit behind the block operations (`efficient-easel/node-ops`, blueprint
+     * step 2.4b: the menu's Delete, Duplicate, Move, Copy / Cut / Paste and Hide,
+     * and the rows' hover-delete). Each of those is planned whole and lands here
+     * once, instead of the two or three dispatches it used to be.
+     *
+     * `select` is BY ID, in `data` (`undefined` leaves the selection as it is),
+     * and goes in with the document through the store's `run` (0.105.1). Until
+     * then the chrome selected first, by position (`setUi { itemSelector }`),
+     * which the store reads in the document it still holds: a paste or a
+     * Duplicate selected the node after its copy, and a Move the node it passed.
+     * Behind the read-only gate like every other mutation here.
+     */
+    commitDocument: (data: Data, select?: NodeSelection) => void;
+};
+type SectionOpsOptions = {
+    /**
+     * SOMEBODY ELSE holds the open document: every MUTATION below becomes a no-op.
+     *
+     * This is the one place the editor's read-only state is enforced on the
+     * document, and it is here rather than on each button because this hook is
+     * already the single source of truth for every mutation — the tree rows, the
+     * canvas "+" seams, the inspector head buttons and the lifecycle effects all
+     * come through it. A gate on the buttons would be a gate on the ones somebody
+     * remembered.
+     *
+     * `select` and `setUi` are NOT mutations and stay live: a read-only viewer must
+     * still be able to click a section and read its settings.
+     *
+     * Deliberately keyed on "somebody else has it" and NOT on the wider save gate.
+     * The save gate is also false while the lock claim is still `checking`, and the
+     * pinned Header/Footer seed runs in the chrome's mount commit, inside that
+     * window, through these very ops. Its WRITE is what is held there — by
+     * `onChange`, released by the claim if it is granted — so the seed must be
+     * allowed to lay the node down (card 1096). Blocking it here would silently
+     * un-fix that card.
+     */
+    readOnly?: boolean;
+    /**
+     * Resolve each node an op puts in (`easel.resolveNode`, trigger `"insert"`).
+     * Default: the layer's rule (`ScreenBlockRules.resolveOnInsert`), else
+     * false — no op resolves anything, as before 0.103.0.
+     */
+    resolveOnInsert?: boolean;
+    /**
+     * NOT AN UNDO STEP: every write is folded into the history entry it happens
+     * in (the store's `recordHistory: false`), as the store folds a resolver's
+     * write (`resolveAll`), instead of being recorded as a step of its own.
+     *
+     * For the passes the screen runs over a document AS IT OPENS — the slot
+     * seeding, the duplicate-id heal, and the layer's own pass (the website's
+     * pinned Header and Footer). Recorded, each was the first entry of the
+     * history: Undo was offered the moment the page opened, and ONE press took
+     * the seeded slides and cards (or the Header) back out of the page, which
+     * autosave then wrote (1.0.1). Folded, the document opens as the history's
+     * first entry; a pass that runs after an edit (a section just inserted,
+     * seeded) lands in that edit's step, so one Undo takes both out together.
+     * Autosave still hears every write (the store's `onChange` fires on a fold).
+     */
+    foldIntoHistory?: boolean;
+};
+declare function useSectionOps(options?: SectionOpsOptions): SectionOps;
+
+export { type NodeSelector, type SectionOps, type SectionOpsOptions, useSectionOps };

package/dist/screen/lib/document/use-section-ops.js

@@ -0,0 +1 @@
+export{useSectionOps}from"../../../chunk-MLQKNED6.js";import"../../../chunk-OHZHYROJ.js";import"../../../chunk-PRHBWA5V.js";import"../../../chunk-FHCKFOCD.js";import"../../../chunk-MQA7OFRA.js";import"../../../chunk-TCAAOYQY.js";import"../../../chunk-TUXLORVR.js";import"../../../chunk-TBY3DFKS.js";import"../../../chunk-PFFH7ASD.js";import"../../../chunk-BPXEFVSQ.js";import"../../../chunk-ZEH6QLBH.js";import"../../../chunk-FM6JO4WF.js";import"../../../chunk-KFV7N2DJ.js";import"../../../chunk-WHS6Y55E.js";import"../../../chunk-K56YDHYQ.js";import"../../../chunk-IWCKVZHS.js";import"../../../chunk-FIVU2COQ.js";import"../../../chunk-BSHIQIZC.js";import"../../../chunk-MZ5GSSZ3.js";import"../../../chunk-KRL3IUV3.js";import"../../../chunk-Y2T3JX7K.js";import"../../../chunk-KFWNGPW3.js";import"../../../chunk-S3DUFDQ6.js";import"../../../chunk-JACEEVVF.js";import"../../../chunk-MFIRYGHW.js";import"../../../chunk-3S5N4HLJ.js";import"../../../chunk-P2VEMZH5.js";import"../../../chunk-4FD7TAOE.js";import"../../../chunk-LF3FUSCQ.js";import"../../../chunk-K7BTCBWD.js";import"../../../chunk-L55YIXDC.js";

package/dist/screen/lib/document-addressing.d.ts

@@ -1,4 +1,4 @@
-export { A as AnyDocumentAddressing, a as DocumentAddressing, N as NO_DOCUMENT_ADDRESSING } from '../../ScreenDocumentContext-CFJeqqKk.js';
+export { A as AnyDocumentAddressing, a as DocumentAddressing, N as NO_DOCUMENT_ADDRESSING } from '../../ScreenDocumentContext-1RgtGKWR.js';
 import './document-contract.js';
 import './session.js';
 import 'react';
@@ -18,5 +18,5 @@ import './links/link-filters.js';
 import 'efficient-shell/ui';
 import './document-hooks.js';
 import './section-template-types.js';
-import './puck/content-tree.js';
+import './document/content-tree.js';
 import './shared-section-types.js';

package/dist/screen/lib/document-switch.d.ts

@@ -9,7 +9,7 @@ import { EditAccess } from '../../edit-lock/index.js';
  * read off the autosave's state, and a set of per-document facts (the pending
  * edit, the version token, a refused save, the lock) that are true of the
  * document being left and of no other. They were written beside the website's
- * pinned-chrome seed, which defers on that status (lib/puck/pinned-seed-gate —
+ * pinned-chrome seed, which defers on that status (lib/document/pinned-seed-gate —
  * the account of why the two must not drift is there, and that module still
  * hands these on), and are here because the document provider reads them and
  * holds no website.

package/dist/screen/lib/host.d.ts

@@ -1,5 +1,5 @@
 import 'react';
-export { D as DETACHED_EASEL_HOST, E as EaselBlockType, b as EaselFieldDescription, c as EaselHost, d as EaselHostAddress, e as EaselHostContext, f as EaselHostPanels, g as EaselHostProvider, h as EaselMessageType, i as EaselSelection, j as EaselToHostMessage, H as HostPickedMedia, k as HostToEaselMessage, I as InboundHostMessage, P as PageEditOp, l as PickedMediaSource, S as SectionScreenTarget, m as SendToHost, n as createEaselHost, u as useEaselHost, o as useHostEscape } from '../../ScreenDocumentContext-CFJeqqKk.js';
+export { D as DETACHED_EASEL_HOST, E as EaselBlockType, b as EaselFieldDescription, c as EaselHost, d as EaselHostAddress, e as EaselHostContext, f as EaselHostPanels, g as EaselHostProvider, h as EaselMessageType, i as EaselSelection, j as EaselToHostMessage, H as HostPickedMedia, k as HostToEaselMessage, I as InboundHostMessage, P as PageEditOp, l as PickedMediaSource, S as SectionScreenTarget, m as SendToHost, n as createEaselHost, u as useEaselHost, o as useHostEscape } from '../../ScreenDocumentContext-1RgtGKWR.js';
 import '../../blocks/index.js';
 import '../../types-Cq53lL8d.js';
 import '../../data/index.js';
@@ -18,5 +18,5 @@ import './links/link-filters.js';
 import 'efficient-shell/ui';
 import './document-hooks.js';
 import './section-template-types.js';
-import './puck/content-tree.js';
+import './document/content-tree.js';
 import './shared-section-types.js';

package/dist/screen/lib/key-scope.d.ts

@@ -1,5 +1,5 @@
 import { RefObject } from 'react';
-import { C as CanvasTarget } from '../../watch-BTYOJpQU.js';
+import { C as CanvasTarget } from '../../watch-D8xZow3y.js';
 
 /**
  * Where the editor listens for its page-wide shortcuts — undo / redo, copy and

package/dist/screen/lib/key-scope.js

@@ -1 +1 @@
-export{editorRootFocus,isSaveShortcut,useEaselKeyTarget,useEaselSaveKey,useEaselUndoKeys}from"../../chunk-I7BROL77.js";import"../../chunk-MQA7OFRA.js";import"../../chunk-EFHV56BO.js";import"../../chunk-TBY3DFKS.js";import"../../chunk-IWCKVZHS.js";import"../../chunk-BSHIQIZC.js";import"../../chunk-23VM4PMV.js";import"../../chunk-KRL3IUV3.js";import"../../chunk-MFIRYGHW.js";import"../../chunk-K7BTCBWD.js";import"../../chunk-L55YIXDC.js";import"../../chunk-QIDRJH3S.js";import"../../chunk-LF3FUSCQ.js";
+export{editorRootFocus,isSaveShortcut,useEaselKeyTarget,useEaselSaveKey,useEaselUndoKeys}from"../../chunk-DNQ7AF6K.js";import"../../chunk-MQA7OFRA.js";import"../../chunk-TUXLORVR.js";import"../../chunk-TBY3DFKS.js";import"../../chunk-IWCKVZHS.js";import"../../chunk-BSHIQIZC.js";import"../../chunk-MZ5GSSZ3.js";import"../../chunk-KRL3IUV3.js";import"../../chunk-MFIRYGHW.js";import"../../chunk-4FD7TAOE.js";import"../../chunk-LF3FUSCQ.js";import"../../chunk-K7BTCBWD.js";import"../../chunk-L55YIXDC.js";

package/dist/screen/lib/media-panel.d.ts

@@ -1,6 +1,6 @@
 import * as react from 'react';
 import { ComponentType, ReactNode } from 'react';
-import { H as HostPickedMedia, c as EaselHost } from '../../ScreenDocumentContext-CFJeqqKk.js';
+import { H as HostPickedMedia, c as EaselHost } from '../../ScreenDocumentContext-1RgtGKWR.js';
 import '../../blocks/index.js';
 import '../../types-Cq53lL8d.js';
 import '../../data/index.js';
@@ -19,7 +19,7 @@ import './links/link-filters.js';
 import 'efficient-shell/ui';
 import './document-hooks.js';
 import './section-template-types.js';
-import './puck/content-tree.js';
+import './document/content-tree.js';
 import './shared-section-types.js';
 
 /**

package/dist/screen/lib/media-picker.d.ts

@@ -1,4 +1,4 @@
-import { H as HostPickedMedia, c as EaselHost } from '../../ScreenDocumentContext-CFJeqqKk.js';
+import { H as HostPickedMedia, c as EaselHost } from '../../ScreenDocumentContext-1RgtGKWR.js';
 import 'react';
 import '../../blocks/index.js';
 import '../../types-Cq53lL8d.js';
@@ -18,7 +18,7 @@ import './links/link-filters.js';
 import 'efficient-shell/ui';
 import './document-hooks.js';
 import './section-template-types.js';
-import './puck/content-tree.js';
+import './document/content-tree.js';
 import './shared-section-types.js';
 
 /**

package/dist/screen/lib/page-lock.d.ts

@@ -14,7 +14,7 @@ import 'efficient-shell/ui';
 import './document-contract.js';
 import './document-hooks.js';
 import './section-template-types.js';
-import './puck/content-tree.js';
+import './document/content-tree.js';
 import './shared-section-types.js';
 
 /**

package/dist/screen/lib/puck/add-target-types.d.ts

@@ -1,55 +1,3 @@
-import { BlockChoice } from './block-choice.js';
-import { SlotSectionSpec } from './slot-section-spec.js';
-
-/** Which registry answered — the discriminator three of the four decisions read. */
-type AddTargetSource = "section" | "footer" | "container";
-/**
- * What a parent can take, and everything the four decisions below need to act on
- * it.
- *
- * ⚠️ THE LOOKUP DECIDES FOUR THINGS, NOT ONE. Wiring only the choice list ships
- * a menu with wrong row names, wrong handlers, and unreachable on an empty
- * container — which is why this returns a record rather than a list:
- *
- *   1  the CHOICE LIST — {@link AddTarget.choices}, what the Add menu offers, or
- *      `null` where the parent adds ONE child type from a button instead.
- *   2  the ROW NAME    — `rowNamerFor` (components/SlotChildRows) reads
- *      {@link AddTarget.source} to pick the FOOTER's block-label rule over
- *      lib/puck/slot-child-name.ts. It must ask "is this a FOOTER block", NOT
- *      "does this parent use a menu": a Box adds from a menu too and
- *      keeps the slot-child rule, or its Headings, Texts and Buttons all fall
- *      through to a rule that reads a heading, a bound menu and first-words.
- *   3  WHICH HANDLERS  — SectionScreenShell's adapter reads `source` to choose
- *      which pair of host handlers a row presses. Keyed the other way round it
- *      answered null for a Box, whose rows then pressed and did nothing.
- *   4  REACHABILITY    — `Boolean(canAddTo(type))` feeds `nestState`, and a row
- *      folds open only if it has children OR an add affordance. An EMPTY
- *      container with no caret cannot be opened to reach its own menu — and
- *      empty is exactly the state a merchant is in when adding the first block.
- */
-interface AddTarget {
-    /** Which of the three registries answered. */
-    source: AddTargetSource;
-    /**
-     * The slot this parent keeps its children on.
-     *
-     * RETURNED rather than defaulted, so a caller can never reach it by falling
-     * through another mechanism's constant — the rule container-blocks states for
-     * its own lookup, kept here because this is now the one that is asked. A Flex
-     * listed on the Footer's `blocks` would draw its rows off `undefined`.
-     */
-    slot: string;
-    /** The registry's own choice list, or `null` for a single-type "Add …" button. */
-    choices: BlockChoice[] | null;
-    /**
-     * The section's own spec — its `addLabel`, `childType`, `seeds`, `addBlocked`,
-     * `notice` and `slider`. Non-null exactly when `source === "section"`.
-     *
-     * Carried so a caller that needs a section's own arithmetic (the Hero slide's
-     * anchor cap, the seed-on-load effect) reaches it through this one seam rather
-     * than importing the registry beside it and gaining a second opinion.
-     */
-    spec: SlotSectionSpec | null;
-}
-
-export type { AddTarget, AddTargetSource };
+export { AddTarget, AddTargetSource } from '../document/add-target-types.js';
+import '../document/block-choice.js';
+import '../document/slot-section-spec.js';

package/dist/screen/lib/puck/add-target-types.js

@@ -0,0 +1 @@
+import"../../../chunk-YIUE4US7.js";

package/dist/screen/lib/puck/block-choice.d.ts

@@ -1,64 +1 @@
-/**
- * One row of an "Add block" menu.
- *
- * `group` is OPTIONAL and is the menu's own heading, not a property of the
- * block: the same `ImageBlock` is grouped in a Box's menu and ungrouped in a
- * Slide box's, because grouping is a fact about the LIST a merchant is reading,
- * not about the component. A list whose choices carry no group renders flat, so
- * every menu that shipped before this stays exactly as it was.
- *
- * It is set at BUILD time by whichever module assembles the list, from the
- * source each choice came from — never hand-written per row. See
- * `lib/puck/container-blocks.ts`, which is the only assembler that sets one.
- */
-type BlockChoice = {
-    type: string;
-    label: string;
-    group?: string;
-    /**
-     * RETIRED: Add does not offer it, and a node of it already in a slot still
-     * belongs there (card [MERGE] One Text Block And Click Through Parts). The
-     * website's Heading and Eyebrow blocks: the Text block took their job, so
-     * nobody starts a new one, and every stored one still draws, edits, moves
-     * and pastes. Read through {@link offeredChoices} wherever a list is shown
-     * to ADD from; the whole list is still the slot's answer to "does this slot
-     * take it?", so a move or a paste reads it unfiltered.
-     */
-    retired?: boolean;
-};
-/** The choices Add offers: every one that is not {@link BlockChoice.retired}, in order. */
-declare function offeredChoices<C extends BlockChoice>(choices: readonly C[]): C[];
-/**
- * One run of consecutive choices sharing a `group` — what a menu draws under one
- * heading.
- *
- * ⚠️ ONE FUNCTION, BOTH SURFACES, and that is the whole reason it is a function.
- * A Box's menu is drawn twice — the dropdown in `components/AddBlockRow`
- * (reached from the Layers tree and from the box's own settings panel) and the
- * chip row at the top of the Add panel (`components/AddSectionPanel`). They draw
- * ONE list, so "where does a heading start" must be ONE answer; two `map`s each
- * comparing with the previous item is how the two surfaces begin dividing the
- * same list differently. That is the exact defect `lib/puck/add-target.ts`'s
- * docblock is an essay about, one tier down.
- *
- * ⚠️ AND THE MENU'S CLASS NAME IS DELIBERATELY NOT WRITTEN IN THIS FILE.
- * `test-footer-block-lists` §8 counts the files mentioning it to prove the menu
- * has exactly ONE home, and it reads prose the same way it reads code — naming
- * the class in a comment here makes this module look like a second menu. The
- * markup lives in `components/AddBlockRow`; this is only the arithmetic.
- *
- * It preserves ORDER and never sorts: the list arrives in the order its assembler
- * chose (`lib/puck/container-blocks.ts` says why that order is what it is), and a
- * renderer is not the place to have a second opinion about it.
- *
- * A list whose choices carry NO group comes back as a single run with
- * `group: undefined` — so a caller written for runs draws an ungrouped list
- * exactly the way it drew it before groups existed, with no branch of its own.
- */
-type BlockChoiceRun = {
-    group?: string;
-    items: BlockChoice[];
-};
-declare function blockRuns(choices: BlockChoice[]): BlockChoiceRun[];
-
-export { type BlockChoice, type BlockChoiceRun, blockRuns, offeredChoices };
+export { BlockChoice, BlockChoiceRun, blockRuns, offeredChoices } from '../document/block-choice.js';

package/dist/screen/lib/puck/block-choice.js

@@ -1 +1 @@
-export{blockRuns,offeredChoices}from"../../../chunk-M2Z775ZC.js";
+export{blockRuns,offeredChoices}from"../../../chunk-RUQOIQWI.js";

package/dist/screen/lib/puck/block-types-in.d.ts

@@ -1,39 +1 @@
-/**
- * Every block type a saved layout uses — the top-level sections and whatever
- * sits in their slots, to any depth.
- *
- * WHAT IT IS FOR. A host chooses which blocks its editor offers
- * (`WebsiteEditor`'s `blocks`), and that choice hides them in the palette, the
- * slot menus and the drop targets. It is not a boundary: a saved page is a JSON
- * document, and whoever can call the host's save endpoint can send one holding
- * any type. So the host's SERVER reads the layout it was handed with this, and
- * refuses a type it does not allow.
- *
- * READ BY SHAPE, WITH NO REGISTRY. A node is `{ type: string, props: {…} }`,
- * and a slot is an array of nodes kept on a prop of its parent — directly, or
- * inside an object or a list item. This walks every value under `props` and
- * takes each array item of that shape as a node. It asks no block registry which
- * props are slots, because the caller is a server that must not have to load
- * one: this module imports nothing.
- *
- * That makes it wider than the editor's own walk in one direction only: a prop
- * that merely LOOKS like a node (an object with a string `type` and an object
- * `props`, inside an array) is counted. It does not ask for the `id` the engine
- * gives every node, because the renderer draws a node without one and a request
- * written by hand can leave it out. Wider is the safe side for an allow-list —
- * it can refuse a page it might have accepted, never accept one it should have
- * refused.
- *
- * `zones` — the engine's older place for slot children, which this editor has
- * never written — is walked too, so a document from elsewhere hides nothing
- * there.
- */
-/**
- * The block types in `layout`, each once, sorted. `layout` is the page document
- * a `WebsiteBackend` stores (`PageLayout`: `content`, `root`, `zones`); a single
- * node — a section template's — is read the same way. Anything else answers
- * an empty list: it holds no block.
- */
-declare function blockTypesIn(layout: unknown): string[];
-
-export { blockTypesIn };
+export { blockTypesIn } from '../document/block-types-in.js';

package/dist/screen/lib/puck/block-types-in.js

@@ -1 +1 @@
-export{blockTypesIn}from"../../../chunk-5ZBY24K7.js";
+export{blockTypesIn}from"../../../chunk-CPL43ZLJ.js";