efficient-easel 21.0.0 → 22.0.0

package/dist/screen/lib/{puck → document}/add-target-types.d.ts

@@ -15,7 +15,7 @@ type AddTargetSource = "section" | "footer" | "container";
  *      `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
+ *      lib/document/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.

package/dist/screen/lib/{puck → document}/block-choice.d.ts

@@ -9,7 +9,7 @@
  *
  * 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.
+ * `lib/document/container-blocks.ts`, which is the only assembler that sets one.
  */
 type BlockChoice = {
     type: string;
@@ -38,7 +38,7 @@ declare function offeredChoices<C extends BlockChoice>(choices: readonly C[]): C
  * 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
+ * same list differently. That is the exact defect `lib/document/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.
@@ -48,7 +48,7 @@ declare function offeredChoices<C extends BlockChoice>(choices: readonly C[]): C
  * 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
+ * chose (`lib/document/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

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

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

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

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

package/dist/screen/lib/{puck → document}/content-tree.d.ts

@@ -31,7 +31,7 @@ declare function slotFieldsOf(config: SlotConfigView, type: string): string[];
  * What a component type's config ALLOWS of the two actions that make another
  * node or take one away (0.103.0): its `permissions.duplicate` and
  * `permissions.delete`, each true unless the config says false — the reading
- * Puck gave a config that carried none. The campaign designer's Product keeps
+ * The old editor gave a config that carried none. The campaign designer's Product keeps
  * its Price line this way (`{ delete: false, duplicate: false }`).
  *
  * The screen's tree rows, its menu and the inspector head it hands this to
@@ -48,7 +48,7 @@ declare function blockNodeActions(config: SlotConfigView, type: string): {
 };
 /**
  * A slot child, addressed the way the Layers tree selects it: the node, the
- * compound zone key "<parentId>:<slotName>" Puck's ops take, and its index in
+ * compound zone key "<parentId>:<slotName>" the old editor's ops take, and its index in
  * that slot.
  */
 type SlotChild = {
@@ -75,7 +75,7 @@ declare function slotChildrenIn(item: TreeItem, slot: string): SlotChild[];
 /**
  * WHERE a node sits in the document — the node itself, the zone key its own
  * array is addressed by, and its index in that array. Exactly the three
- * arguments a Puck `replace` / `remove` / `reorder` op takes.
+ * arguments an old-editor `replace` / `remove` / `reorder` op takes.
  */
 type NodeLocation = {
     item: TreeItem;
@@ -112,16 +112,16 @@ type NodeLocation = {
  * `ScreenChrome` memoises a Map of EVERY node's address (plus each
  * zone's whole sibling list) and hands the lookup to the context menu as
  * `locate`. That map is built once per document for a surface that needs all of
- * it; this finds ONE node and is reachable from a Puck field, which the map is
+ * it; this finds ONE node and is reachable from an old-editor field, which the map is
  * not — it lives in a component's closure and rides no context. What must not
  * be two things is the set of SLOT PROP NAMES, and it is not: both walk through
  * `childSlotsOf`, so an address here and an address there cannot disagree.
- * Puck's own `getSelectorForId` is a third reader of the same fact, and the one
+ * The old editor's own `getSelectorForId` is a third reader of the same fact, and the one
  * a live store already offers — it is a hook-bound function, so a guard cannot
  * call it, which is the whole reason this one is written pure.
  *
  * PURE, and takes the config as an argument, so a guard can assert against it
- * without a Puck store, a React tree or a hook.
+ * without an old-editor store, a React tree or a hook.
  *
  * `null` when no node carries the id — the honest answer for a stale selection,
  * and every caller treats it as "there is nothing to write".
@@ -201,7 +201,7 @@ declare function pinnedDuplicateIds(content: ReadonlyArray<{
  * Which pinned chrome types a document is MISSING, and a load-time seed must
  * therefore create. A type counts as missing only when it is absent from BOTH:
  *
- *   - `live` — the editor's Puck store, read at the moment of the write; and
+ *   - `live` — the editor's the old editor store, read at the moment of the write; and
  *   - `persisted` — the document exactly as it was LOADED from the backend.
  *
  * Requiring both is what makes seeding idempotent, and neither check can be

package/dist/screen/lib/{puck → document}/content-tree.js

@@ -1 +1 @@
-export{FOOTER_TYPE,HEADER_TYPE,ROOT_ZONE,TREE_MAX_DEPTH,blockNodeActions,childSlotsOf,locateNode,missingPinnedTypes,nestsInTree,newNodeId,pinnedDuplicateIds,pinnedDuplicateIndices,slotChildrenIn,slotFieldsOf}from"../../../chunk-PLVEGYK6.js";
+export{FOOTER_TYPE,HEADER_TYPE,ROOT_ZONE,TREE_MAX_DEPTH,blockNodeActions,childSlotsOf,locateNode,missingPinnedTypes,nestsInTree,newNodeId,pinnedDuplicateIds,pinnedDuplicateIndices,slotChildrenIn,slotFieldsOf}from"../../../chunk-TCAAOYQY.js";

package/dist/screen/lib/{puck → document}/device-fields.d.ts

@@ -3,7 +3,7 @@ import { PreviewDevice } from '../../components/PreviewDeviceContext.js';
 import '../content/view-tiers.js';
 
 /**
- * lib/puck/device-fields.tsx — show the setting for the device the merchant is
+ * lib/document/device-fields.tsx — show the setting for the device the merchant is
  * currently looking at, and only that one.
  *
  * THE PROBLEM. A section that can be sized differently on a phone stores TWO
@@ -12,8 +12,8 @@ import '../content/view-tiers.js';
  * screen; the panel ignored it, so the merchant read labels to find the control
  * that matched what they were looking at.
  *
- * THE MECHANISM, and why this one. A Puck `resolveFields` cannot do it: in this
- * Puck version the fields slice re-resolves only when the selected node's DATA
+ * THE MECHANISM, and why this one. A the old editor `resolveFields` cannot do it: in this
+ * The old editor version the fields slice re-resolves only when the selected node's DATA
  * changes (`useRegisterFieldsSlice` subscribes to `state.indexes.nodes[id]`), and
  * switching device changes no data — the panel would keep whatever field set the
  * last edit produced. So the decision is made where it can re-render freely: in
@@ -35,11 +35,11 @@ import '../content/view-tiers.js';
  * ({@link DEVICE_NOTE}); it never presents desktop values as if they were
  * tablet's. {@link shownTier} is the single place that ruling is written down.
  *
- * WHY THE HIDDEN FIELD LEAVES NO GAP. Puck wraps every top-level field in its
- * own padded `_PuckFields-field_` box before it calls `render`, so a field that
+ * WHY THE HIDDEN FIELD LEAVES NO GAP. The old editor wraps every top-level field in its
+ * own padded old editor's padded field box before it calls `render`, so a field that
  * renders nothing would still cost ~37px of empty panel. The gate instead paints
  * a zero-size marker and this package's `screen.css` collapses the
- * wrapper that contains one — the same "reach the wrapper Puck owns" trick the
+ * wrapper that contains one — the same "reach the wrapper the old editor owns" trick the
  * fold reflow in `controls.tsx` already relies on, expressed as one CSS rule
  * instead of a second DOM pass (so it cannot race the fold's).
  */
@@ -63,7 +63,7 @@ declare function shownTier(device: PreviewDevice): DeviceTier;
  * letting the desktop values pass for tablet's own.
  */
 declare const DEVICE_NOTE: Readonly<Record<PreviewDevice, string | null>>;
-/** The attribute the stylesheet looks for to collapse a gated-off field's Puck
+/** The attribute the stylesheet looks for to collapse a gated-off field's the old editor
  *  wrapper. Declared here, matched once in this package's `screen.css`, which
  *  every host that mounts the screen loads (it sat in the website's sheet until
  *  0.103.0, so a second host's hidden rows kept their space). */
@@ -83,7 +83,7 @@ type AnyCustomField = {
  *  wraps live ON the field object, never only inside the render closure. Without
  *  it a gated control is opaque to every static walk — and the fold guard in
  *  `scripts/test-section-groups.ts` genuinely needs to see the header underneath
- *  to check its label against what it draws. Puck ignores extra keys. */
+ *  to check its label against what it draws. The old editor ignores extra keys. */
 declare const DEVICE_FIELD_MARKER: "__device";
 /** The payload on {@link DEVICE_FIELD_MARKER}. */
 type DeviceFieldMeta = {

package/dist/screen/lib/{puck → document}/device-fields.js

@@ -1 +1 @@
-export{DEVICE_FIELD_MARKER,DEVICE_HIDDEN_ATTR,DEVICE_NOTE,deviceField,deviceMetaOf,deviceNote,shownTier,withoutDeviceGate}from"../../../chunk-MSGZ56QL.js";import"../../../chunk-7F52SZOI.js";import"../../../chunk-EB6NI2VK.js";import"../../../chunk-MFIRYGHW.js";import"../../../chunk-BSPCSC45.js";
+export{DEVICE_FIELD_MARKER,DEVICE_HIDDEN_ATTR,DEVICE_NOTE,deviceField,deviceMetaOf,deviceNote,shownTier,withoutDeviceGate}from"../../../chunk-KWLHKKZO.js";import"../../../chunk-INRERJU4.js";import"../../../chunk-EB6NI2VK.js";import"../../../chunk-MFIRYGHW.js";import"../../../chunk-BSPCSC45.js";

package/dist/screen/lib/{puck → document}/field-buckets.d.ts

@@ -1,12 +1,12 @@
-import { S as SettingsBucket, D as DesignGroup } from '../../../buckets-Tj-nkBpg.js';
+import { S as SettingsBucket, D as DesignGroup } from '../../../buckets-_MGDYJlb.js';
 
 /**
- * lib/puck/field-buckets.ts — the two settings buckets a section's fields are
+ * lib/document/field-buckets.ts — the two settings buckets a section's fields are
  * sorted into (Design, Animation: owner 2026-10-08, final 2026-10-10), the
  * field key each bucket's header is emitted under, and the field key of each
  * Design group's heading.
  *
- * Moved out of lib/puck/field-groups (which re-exports both) so the editor's
+ * Moved out of lib/document/field-groups (which re-exports both) so the editor's
  * screen can read a header's key — the style clipboard copies a look by the
  * groups it sits in — without importing the field builders that sort a
  * section's fields (doc/adr/0004). The reasoning behind the buckets themselves

package/dist/screen/lib/document/field-buckets.js

@@ -0,0 +1 @@
+export{BUCKET_KEY,DESIGN_GROUP_KEY}from"../../../chunk-3QB2ZQXK.js";

package/dist/screen/lib/{puck → document}/field-markers.d.ts

@@ -4,12 +4,12 @@ import { TextControlKind } from './text-control-kinds.js';
  * field-markers — what a field DECLARES about itself, readable without the
  * inspector.
  *
- * A control factory in `lib/puck/controls` stamps a marker on the field object
+ * A control factory in `lib/document/controls` stamps a marker on the field object
  * it returns: this prop holds authored copy, this one a link, this row array
  * draws these scaffold rows while it is empty. Two kinds of code read those
  * stamps. The inspector does, and so does the RENDER side — the part walk that
- * makes a headline clickable (`lib/puck/text-parts`), the typing bridge
- * (`lib/puck/part-text`, `lib/puck/part-rows`) — and a section's own option
+ * makes a headline clickable (`lib/document/text-parts`), the typing bridge
+ * (`lib/document/part-text`, `lib/document/part-rows`) — and a section's own option
  * module may be typed by a control's vocabulary (`lib/sections/ticker-scroll`
  * names the pad cell each direction sits in).
  *
@@ -19,7 +19,7 @@ import { TextControlKind } from './text-control-kinds.js';
  * client and the cart. A render-side module that only wanted the string
  * `"__text"` imported all of it, which is what kept a general section from being
  * drawn anywhere the inspector cannot go (doc/adr/0002). The same split, for the
- * same reason, that `lib/puck/hidable` and `lib/puck/text-control-kinds` already
+ * same reason, that `lib/document/hidable` and `lib/document/text-control-kinds` already
  * made.
  *
  * This file imports nothing but that kinds leaf. `controls.tsx` re-exports
@@ -33,7 +33,7 @@ import { TextControlKind } from './text-control-kinds.js';
  *  GENERATOR (`scripts/gen-neutralization-manifest.ts`) walks the built config
  *  looking for it, so the text factories are the single source of truth for
  *  "this prop holds customer-authored copy" — a new text field is covered the
- *  moment it is declared, with no list to maintain anywhere (Puck ignores extra
+ *  moment it is declared, with no list to maintain anywhere (the old editor ignores extra
  *  keys).
  *
  *  Unlike the media marker this carries a PAYLOAD, because the neutralizer needs
@@ -59,14 +59,14 @@ declare const LINK_FIELD_MARKER: "__link";
  * greyed hint (`placeholder` above), and everything that asks "what does this
  * prop put on screen?" — the neutralizer, the part walk — reads it there. A row
  * array had no equivalent: `config.tsx` passes the scaffold constant straight
- * into `phRows(value, SCAFFOLD, puck)` inside the render, where nothing outside
+ * into `phRows(value, SCAFFOLD, editor)` inside the render, where nothing outside
  * the component can see it. So a freshly-dropped section drew three grey rows of
- * scaffold copy that `lib/puck/text-parts` could not name, and clicking that copy
+ * scaffold copy that `lib/document/text-parts` could not name, and clicking that copy
  * opened the whole section instead of the one control behind it (card 66072).
  *
  * It is the SAME constant the render passes — `withScaffold` (in
- * `lib/puck/controls`) takes it as an argument rather than copying it — so the
- * preview and the walk cannot drift. Puck ignores extra keys on a field, exactly
+ * `lib/document/controls`) takes it as an argument rather than copying it — so the
+ * preview and the walk cannot drift. The old editor ignores extra keys on a field, exactly
  * as it does for the two markers above.
  */
 declare const SCAFFOLD_FIELD_MARKER: "__scaffold";
@@ -96,7 +96,7 @@ type TextListRendering =
  | "verbatim";
 /** The payload on {@link TEXT_FIELD_MARKER}: what a text field says about the
  *  copy it holds. The `with…` wrappers that set its optional facts, and the
- *  readers that pair with them, are in `lib/puck/controls`. */
+ *  readers that pair with them, are in `lib/document/controls`. */
 type TextFieldMeta = {
     control: TextControlKind;
     /** The control's inspector label — a classification signal when a field
@@ -160,21 +160,21 @@ type TextFieldMeta = {
 };
 /** Which of an edge pad's four live squares an answer sits in — the cell a
  *  direction option names beside its value (`lib/sections/ticker-scroll`), and
- *  the one the pad in `lib/puck/controls` lights. */
+ *  the one the pad in `lib/document/controls` lights. */
 type EdgeCell = "top" | "right" | "bottom" | "left";
 /** Marker carried by every media field object. The manifest GENERATOR walks the
  *  built config looking for it, so the factory below is the single source of
  *  truth for "this prop holds media" — a new media field is covered the moment
- *  it is declared, with no list to maintain anywhere (Puck ignores extra keys). */
+ *  it is declared, with no list to maintain anywhere (the old editor ignores extra keys). */
 declare const MEDIA_FIELD_MARKER: "__media";
 /** Marker carried by every heading {@link group} / {@link section} builds — and
  *  by every bucket header {@link bucketHeader} builds, whose "heading" a
  *  merchant reads as a TAB. Same style as {@link TEXT_FIELD_MARKER} / {@link LINK_FIELD_MARKER}:
  *  the label and the level ON the field object, not only inside the render
  *  closure. Without it a header's label is unreadable at runtime — the closure
- *  is all there is — and the four-bucket pass (`lib/puck/field-groups.ts`) would
+ *  is all there is — and the four-bucket pass (`lib/document/field-groups.ts`) would
  *  have to re-derive it by parsing `config.tsx`, i.e. a second source of truth
- *  for something the field already knows. Puck ignores extra keys, and the
+ *  for something the field already knows. The old editor ignores extra keys, and the
  *  neutralization walk classifies by its own markers / `type` / prop name, so a
  *  header stays exactly as invisible to it as it was (see
  *  `scripts/gen-neutralization-manifest.ts`). */
@@ -194,7 +194,7 @@ declare function foldMetaOf(field: unknown): FoldFieldMeta | null;
  */
 declare function textFieldIdentifier(field: unknown): boolean;
 /**
- * The keys `anchorFields()` (lib/puck/controls) declares: the anchor's group
+ * The keys `anchorFields()` (lib/document/controls) declares: the anchor's group
  * header and its name row. The style clipboard leaves them out of a copied
  * look — an anchor is the section's address, not its style — and reads them
  * here rather than calling the builder, so it needs nothing of the inspector's

package/dist/screen/lib/{puck → document}/field-markers.js

@@ -1 +1 @@
-export{ANCHOR_FIELD_KEYS,FOLD_FIELD_MARKER,LINK_FIELD_MARKER,MEDIA_FIELD_MARKER,SCAFFOLD_FIELD_MARKER,TEXT_FIELD_MARKER,foldMetaOf,textFieldIdentifier}from"../../../chunk-DUVRZ456.js";
+export{ANCHOR_FIELD_KEYS,FOLD_FIELD_MARKER,LINK_FIELD_MARKER,MEDIA_FIELD_MARKER,SCAFFOLD_FIELD_MARKER,TEXT_FIELD_MARKER,foldMetaOf,textFieldIdentifier}from"../../../chunk-ANPOR6EY.js";

package/dist/screen/lib/{puck → document}/hidable.d.ts

@@ -2,18 +2,18 @@
  * hidable — the ONE reader for the shape a hideable copy row stores.
  *
  * Every authored-text row in the editor is one of five controls
- * (`lib/puck/text-control-kinds`), and two of them — `text()` and `textarea()` —
+ * (`lib/document/text-control-kinds`), and two of them — `text()` and `textarea()` —
  * carry the eye that takes an element off the page while keeping the words. Those
  * two persist `{ text, hidden }`; the other three persist a bare string, and so
  * does every page published before the eye existed. A prop's stored value is
  * therefore an OBJECT OR A STRING, and which one it is depends on whether a
  * merchant has touched that row — not on anything a reader can see in the code.
  *
- * ⚠️ WHY THIS IS ITS OWN FILE. `readHidable` was born in `lib/puck/controls.tsx`
+ * ⚠️ WHY THIS IS ITS OWN FILE. `readHidable` was born in `lib/document/controls.tsx`
  * beside the field that writes the shape, and `controls.tsx` is React: it imports
  * the editor shell, the markup toolbar and 30 components. So a PURE module that
  * needs to read a stored heading could not use the one reader without dragging
- * the whole editor in — and `lib/puck/heading-outline.ts` is exactly that module
+ * the whole editor in — and `lib/document/heading-outline.ts` is exactly that module
  * (its own header promises no React and no config import, so the audit can be
  * walked in a test without mounting the editor). It called `String(...)` on the
  * prop instead, and printed the literal words `[object Object]` into the outline

package/dist/screen/lib/document/hidable.js

@@ -0,0 +1 @@
+export{hidableText,readHidable}from"../../../chunk-6UAEFOJ4.js";

package/dist/screen/lib/{puck → document}/palette-sections.d.ts

@@ -1,10 +1,10 @@
 import { Config } from '../../../blocks/index.js';
 import 'react';
-import '../../../types-Cq53lL8d.js';
+import '../../../types-DFxBChE3.js';
 import '../../../data/index.js';
-import '../../../types-41704JE4.js';
-import '../../../resolve-D68pb3Bx.js';
-import '../../../plan-CZS902DV.js';
+import '../../../types-DlQIM1YO.js';
+import '../../../resolve-AJ6WF4EL.js';
+import '../../../plan-CRUh2kVK.js';
 
 /** One offerable section, with the category it is grouped under. */
 type PaletteSection = {
@@ -43,7 +43,7 @@ type PaletteSection = {
  * What the layer says of its sections for the palette: the word for a type at
  * a level, a group's short heading where it has one, and the blurbs. The
  * screen's `blockLook` is one (lib/screen-parts); so is the website's own
- * (lib/puck/add-palette).
+ * (lib/document/add-palette).
  */
 interface PaletteLook {
     /** What a node of `type` is called at a level, given the label the config
@@ -67,13 +67,13 @@ interface PaletteLook {
  * Child-only blocks (HeroSlide / CollectionCard / ProductRef) and the four
  * generic primitives (Heading / Text / ImageBlock / ButtonBlock) sit in NO
  * category on purpose, so they never appear here — they are added from their
- * parent's slot instead. See the note above `categories:` in lib/puck/config.tsx.
+ * parent's slot instead. See the note above `categories:` in lib/document/config.tsx.
  *
  * A category the config marks `visible: false` is NOT offered (0.105.0, seam
  * E9): it is a registry's way of keeping blocks it has out of the picker — the
  * campaign designer's Product parts, its retired blocks, its Sections — and a
  * palette that listed them would offer things that may not be put on a page.
- * Puck's own palette read the flag the same way. No website category carries
+ * The old editor's own palette read the flag the same way. No website category carries
  * it, so the website's palette is the list it was.
  */
 declare function buildPaletteSections(config: Config, look: PaletteLook): PaletteSection[];

package/dist/screen/lib/{puck → document}/palette-sections.js

@@ -1 +1 @@
-export{buildPaletteSections,categoryLabel,matchesQuery,paletteWithoutPinned,pinnedSection}from"../../../chunk-PA3PNTVV.js";
+export{buildPaletteSections,categoryLabel,matchesQuery,paletteWithoutPinned,pinnedSection}from"../../../chunk-VKPOH6MK.js";

package/dist/screen/lib/{puck → document}/panel-fields.d.ts

@@ -7,16 +7,16 @@
  * array on a linked product, Image & Text Columns takes its text-position row
  * away once it has Boxes.
  *
- * `Puck.Fields` honours all of that. Every list built beside it from the raw
+ * `the old editor's fields panel` honours all of that. Every list built beside it from the raw
  * declaration does not — and one of them is the copy list in
  * `components/SectionEditor`. So a merchant met the SAME heading twice: once in
- * the panel Puck drew, and once in a list drawn from rows the resolver had
+ * the panel the old editor drew, and once in a list drawn from rows the resolver had
  * already dropped (owner, 2026-09-10, on a Booking Form's Head box).
  *
- * ⚠️ PUCK DOES NOT EXPOSE ITS RESOLVED SET. The store slice that holds it is
- * internal — `useEasel((s) => s)` and `createUsePuck()` both hand back `PuckApi`, which
+ * ⚠️ THE OLD EDITOR DOES NOT EXPOSE ITS RESOLVED SET. The store slice that holds it is
+ * internal — `useEasel((s) => s)` and `the old selector hook` both hand back `the old store API`, which
  * has no `fields` on it (checked against 0.20.2's own types, not remembered). So
- * the resolver is asked here, the same way Puck asks it.
+ * the resolver is asked here, the same way the old editor asks it.
  *
  * ⚠️ AND AN ASYNC RESOLVER IS ANSWERED WITH THE DECLARATION. A promise cannot be
  * read during a render, and a list that waited would flicker rows in and out.
@@ -35,7 +35,7 @@ interface PanelComponent {
  * `parent` is passed as null and `appState` as an empty object because the ONE
  * caller uses the result for authored-copy rows, which no resolver decides from
  * either. A caller that needs the width rows — which DO read `parent` — must ask
- * Puck rather than this.
+ * The old editor rather than this.
  */
 declare function panelFieldsOf(config: {
     components?: Record<string, PanelComponent>;

package/dist/screen/lib/document/panel-fields.js

@@ -0,0 +1 @@
+export{panelFieldsOf}from"../../../chunk-5XL2RXFU.js";import"../../../chunk-BPXEFVSQ.js";

package/dist/screen/lib/{puck → document}/panel-no-control-mark.d.ts

@@ -4,12 +4,11 @@ import { ReactElement } from 'react';
  * panel-no-control-mark — what a settings field draws when it draws NO CONTROL
  * on the screen it is on (card 66178).
  *
- * WHY A FIELD HAS TO SAY THIS OUT LOUD. Puck lays the inspector out as a FLAT
+ * WHY A FIELD HAS TO SAY THIS OUT LOUD. The old editor lays the inspector out as a FLAT
  * list and owns the wrapper around every top-level field, and its own stylesheet
  * rules the gap between two of them:
  *
- *   ._PuckFields--wrapFields_ ._PuckFields-field_ + ._PuckFields-field_ {
- *     border-top: 1px solid var(--puck-color-grey-09); margin-top: 8px; }
+ *   (wrapper) field + field { border-top: 1px solid <grey>; margin-top: 8px; }
  *
  * That rule is right — a line between two adjacent rows. But a field whose
  * `render` returns `null` still gets the wrapper, still takes its `16px 16px
@@ -19,7 +18,7 @@ import { ReactElement } from 'react';
  * `<div class="_InputWrapper_"></div>`, and three rules stacked with only blank
  * space between them. Across the catalogue it was 338 such rows in 74 panels.
  *
- * We cannot stop Puck emitting the wrapper, so the wrapper is collapsed from the
+ * We cannot stop the old editor emitting the wrapper, so the wrapper is collapsed from the
  * outside: the field renders this zero-size marker and ONE declarative rule in
  * `components/storefront-editor.css` takes the wrapper out of the layout
  * entirely — `display: none`, so the row leaves the accessibility tree with it
@@ -50,7 +49,7 @@ declare function NoControlMark(): ReactElement;
  * and no React — it has a field list and nothing else. So a field that draws no
  * control has to say so twice, in the two places the answer is asked, and both
  * are stamped by the ONE `if` that decides it: see `textField` in
- * `lib/puck/controls`, which wraps the render and stamps the marker together.
+ * `lib/document/controls`, which wraps the render and stamps the marker together.
  *
  * The two reasons are not the same shape, hence a word rather than a boolean:
  *   • `"always"` — it draws nothing wherever it appears. A device scope note, a
@@ -66,7 +65,7 @@ type NoControlFieldMeta = "always" | "authored-copy";
  *  own. The ONE place that knows the marker's shape. */
 declare function noControlMetaOf(field: unknown): NoControlFieldMeta | null;
 /** Stamp {@link NO_CONTROL_FIELD} on a field. The cast is here and nowhere else:
- *  Puck's field types have no slot for a marker, so an object literal carrying
+ *  The old editor's field types have no slot for a marker, so an object literal carrying
  *  one trips the excess-property check at every call site otherwise — the same
  *  reason `group()` and the text/link markers have their own builders. */
 declare function noControlField<F>(field: F, reason: NoControlFieldMeta): F;

package/dist/screen/lib/{puck → document}/panel-no-control-mark.js

@@ -1 +1 @@
-export{NO_CONTROL_ATTR,NO_CONTROL_FIELD,NoControlMark,noControlField,noControlMetaOf}from"../../../chunk-7F52SZOI.js";
+export{NO_CONTROL_ATTR,NO_CONTROL_FIELD,NoControlMark,noControlField,noControlMetaOf}from"../../../chunk-INRERJU4.js";

package/dist/screen/lib/{puck → document}/part-id.d.ts

@@ -1,15 +1,15 @@
 /**
- * lib/puck/part-id.ts — how one PART of a section is named: `"<nodeId>::<propKey>"`.
+ * lib/document/part-id.ts — how one PART of a section is named: `"<nodeId>::<propKey>"`.
  *
  * A part is one authored text of a node (a heading, a button label) that the
  * editor's inspector can drill into. Its id is read on both sides of the
  * preview: the section's render marks each part with it, and the screen's part
  * bridge (components/usePartBridge) opens the part it names. The codec moved
- * here from lib/puck/text-parts (which re-exports it) so the screen reads it
+ * here from lib/document/text-parts (which re-exports it) so the screen reads it
  * without the text walk, and moves into efficient-easel with it (doc/adr/0004).
  */
 /** Separates the node id from the prop key inside a part id. A doubled colon:
- *  a Puck node id is `<Type>-<uuid>` and a compound zone is `<parentId>:<slot>`,
+ *  an old-editor node id is `<Type>-<uuid>` and a compound zone is `<parentId>:<slot>`,
  *  so a single colon is already taken. */
 declare const PART_SEP = "::";
 /** `"<nodeId>::<propKey>"`, or `"<nodeId>::"` for "the whole section". */

package/dist/screen/lib/document/part-id.js

@@ -0,0 +1 @@
+export{PART_SEP,decodePartId,encodePartId}from"../../../chunk-R4AUZVA3.js";

package/dist/screen/lib/{puck → document}/preview-click.d.ts

@@ -16,7 +16,7 @@
  *
  * The two callers are told apart HERE rather than at each of the eight call
  * sites, because the difference is one rule and a rule spelled eight times is a
- * rule that drifts. `useSelectHandler` (lib/puck/preview-selection-context) is
+ * rule that drifts. `useSelectHandler` (lib/document/preview-selection-context) is
  * the single entry point every in-preview click already goes through — it is
  * invoked from inside the portaled preview iframe — so wrapping it once covers
  * both editor shells and all four bridges, and the tree keeps calling the same

package/dist/screen/lib/document/preview-click.js

@@ -0,0 +1 @@
+export{isPreviewClick,runAsPreviewClick}from"../../../chunk-MGVI67QV.js";

package/dist/screen/lib/{puck → document}/preview-dom.js

@@ -1 +1 @@
-export{gotoPreviewSlide,pinPreviewToBottom,pinPreviewToSection,previewFrame,scrollPreviewToSection,scrollPreviewToTop}from"../../../chunk-2E2SXDYQ.js";import"../../../chunk-IQ5TA7AM.js";import"../../../chunk-LF3FUSCQ.js";import"../../../chunk-R5L2E7JX.js";
+export{gotoPreviewSlide,pinPreviewToBottom,pinPreviewToSection,previewFrame,scrollPreviewToSection,scrollPreviewToTop}from"../../../chunk-DDH2DYQP.js";import"../../../chunk-AJ2SUSET.js";import"../../../chunk-LF3FUSCQ.js";import"../../../chunk-MGVI67QV.js";

package/dist/screen/lib/{puck → document}/preview-events.d.ts

@@ -1,22 +1,22 @@
 /**
- * lib/puck/preview-events.ts — events the editor's screen sends INTO the preview.
+ * lib/document/preview-events.ts — events the editor's screen sends INTO the preview.
  *
  * Moved from components/HeroSection (which re-exports them) so the screen's
- * preview bridge (lib/puck/preview-dom) can send them without importing a
+ * preview bridge (lib/document/preview-dom) can send them without importing a
  * section, and moves into efficient-easel with the screen (doc/adr/0004). A
  * section listens for its own; the name is the contract between the two.
  */
 /**
  * Event the editor chrome dispatches INTO the preview iframe to jump a Hero's
  * slider to a slide by index. The chrome (section tree + "Add slide") lives
- * outside this iframe and can't reach the slider's React state, and Puck's
+ * outside this iframe and can't reach the slider's React state, and the old editor's
  * selection overlay is portaled to the iframe `<body>` (not inside `.hero-track`),
  * so selection alone can't be observed from here — this is the explicit bridge.
  * See {@link ScreenChrome} `selectChild` / `addChild`.
  */
 declare const HERO_SLIDER_GOTO_EVENT = "hero-slider:goto";
 interface HeroSliderGotoDetail {
-    /** Target Hero's stable Puck id (`data-puck-component`); omit to hit all Heroes. */
+    /** Target Hero's stable the old editor id (`data-easel-block`); omit to hit all Heroes. */
     id?: string;
     /** Zero-based slide index to show. */
     index: number;

package/dist/screen/lib/document/preview-events.js

@@ -0,0 +1 @@
+export{HERO_SLIDER_GOTO_EVENT}from"../../../chunk-AJ2SUSET.js";

package/dist/screen/lib/{puck → document}/preview-selection-context.d.ts

@@ -3,8 +3,8 @@ import { ReactNode } from 'react';
 
 /**
  * Shared machinery for the editor preview's "selection bridges" — the click-to-
- * select plumbing every piece of site CHROME needs because it is NOT a Puck node
- * and so can't route through Puck's own selection. The header, the chat bubble,
+ * select plumbing every piece of site CHROME needs because it is NOT an old-editor node
+ * and so can't route through the old editor's own selection. The header, the chat bubble,
  * and a Hero's ticker / background / text overlay each expose the SAME two-way
  * bridge, and all built it by hand until this file:
  *

package/dist/screen/lib/{puck → document}/preview-selection-context.js

@@ -1 +1 @@
-export{createPreviewSelectionContext,useSelectHandler}from"../../../chunk-GOTN2KY4.js";import"../../../chunk-R5L2E7JX.js";
+export{createPreviewSelectionContext,useSelectHandler}from"../../../chunk-TIAWIOGD.js";import"../../../chunk-MGVI67QV.js";

package/dist/screen/lib/{puck → document}/section-doc.d.ts

@@ -1,18 +1,18 @@
 import { Data } from '../../../blocks/index.js';
 import { TreeItem } from './content-tree.js';
 import 'react';
-import '../../../types-Cq53lL8d.js';
+import '../../../types-DFxBChE3.js';
 import '../../../data/index.js';
-import '../../../types-41704JE4.js';
-import '../../../resolve-D68pb3Bx.js';
-import '../../../plan-CZS902DV.js';
+import '../../../types-DlQIM1YO.js';
+import '../../../resolve-AJ6WF4EL.js';
+import '../../../plan-CRUh2kVK.js';
 
 declare function nodeToDoc(node: TreeItem): Data;
 declare function docToNode(data: Data): TreeItem | null;
 /**
  * Deep-copy a stored section node with FRESH ids — the node's own and every
  * inline slot child's, recursively — so inserting the same template twice never
- * lands two nodes with colliding ids (Puck keys selection/replace on id, and
+ * lands two nodes with colliding ids (the old editor keys selection/replace on id, and
  * React keys render on it).
  *
  * `strip` (0.106.0) sees each copied node once its children are copied, and

package/dist/screen/lib/{puck → document}/section-doc.js

@@ -1 +1 @@
-export{cloneNodeWithFreshIds,docToNode,nodeToDoc}from"../../../chunk-2GVCAIPX.js";import"../../../chunk-PLVEGYK6.js";
+export{cloneNodeWithFreshIds,docToNode,nodeToDoc}from"../../../chunk-BDSLF5BR.js";import"../../../chunk-TCAAOYQY.js";

package/dist/screen/lib/{puck → document}/slot-child-name.d.ts

@@ -64,7 +64,7 @@
  * `scripts/test-slot-child-lists.tsx` §5 pins that this stays the ONE home.
  */
 /**
- * A Puck content node as this rule reads it. Deliberately looser than
+ * A the old editor content node as this rule reads it. Deliberately looser than
  * `TreeItem` (no required `id`): `CollectionCard.render` names itself from the
  * props it was handed, and never has a node in hand.
  */
@@ -155,7 +155,7 @@ type RowNameRule<N extends SlotChild = SlotChild> = (node: N, level: "section" |
  * an ordinary `Heading` a merchant writes — copy, printed on the page. A rename
  * keyed on the prop NAME would quietly rewrite that heading from a menu item
  * called "Rename". So the field must DECLARE itself an identifier
- * (`withIdentifier`, see `lib/puck/controls`), which is the same declaration the
+ * (`withIdentifier`, see `lib/document/controls`), which is the same declaration the
  * settings panel reads to keep these rows out of the copy list.
  *
  * `fields` is taken as an argument rather than imported, exactly like the

package/dist/screen/lib/document/slot-child-name.js

@@ -0,0 +1 @@
+export{rootRowName,sectionRenameProp,slotChildName,slotChildRenameProp,slotChildRowName}from"../../../chunk-SSRYU3YG.js";import"../../../chunk-ANPOR6EY.js";import"../../../chunk-6UAEFOJ4.js";

package/dist/screen/lib/document/slot-heal.js

@@ -0,0 +1 @@
+export{dedupeSlotChildren}from"../../../chunk-7OCEPOEJ.js";

package/dist/screen/lib/{puck → document}/slot-section-spec.d.ts

@@ -1,7 +1,7 @@
 /**
- * A component type's own `defaultProps`, looked up in the Puck config.
+ * A component type's own `defaultProps`, looked up in the old editor config.
  *
- * Handed IN rather than imported: `lib/puck/config` imports the seed
+ * Handed IN rather than imported: `lib/document/config` imports the seed
  * registry's neighbours, and a seed registry that reached back into the config
  * would close the loop. Both callers of `seeds()` already hold the config
  * (`components/ScreenChrome`, `components/StandaloneSectionEditor`),
@@ -11,7 +11,7 @@
  * seed ONE flat child whose every field is content, so a missing default changes
  * nothing they draw. Image & Text Columns seeds a Box holding blocks, and a Box
  * without its `direction` / `justify` / `align` / `wrap` is a different shape on
- * the page — see `boxColumnSeed` in lib/puck/slot-specs.
+ * the page — see `boxColumnSeed` in lib/document/slot-specs.
  */
 type NodeDefaults = (type: string) => Record<string, unknown>;
 interface SlotSectionSpec {