@jxsuite/studio 5.2.0 → 5.4.0

package/src/workspace/workspace.ts

@@ -1,5 +1,6 @@
 import { computed, reactive, toRaw } from "../reactivity";
 import { commitTabBuffers } from "../services/monaco-buffer";
+import { resetAiWrites } from "../services/ai-writes";
 import { ensureCollab, rekeyCollab } from "../collab/collab-session";
 import { createTab, disposeTab } from "../tabs/tab";
 import { projectState } from "../state";
@@ -12,7 +13,7 @@ import {
 } from "../commands/command-args";
 import { EDITOR_KIND_LABELS } from "../commands/context";
 import type { Tab, TabOrigin } from "../tabs/tab";
-import type { JsonLayout } from "../files/json-layout";
+import type { JsonLayout } from "@jxsuite/schema/json-layout";
 
 import type { ComponentEntry } from "../files/components";
 import type { AnyCommand, CommandRegistry } from "../commands/registry";
@@ -35,11 +36,11 @@ export interface ClosedTabRecord {
 const CLOSED_TAB_LIMIT = 20;
 
 /**
- * One editor pane — the unit of split, focus and zoom (§4.1).
+ * One editor pane — the unit of split, focus and zoom (§18.1).
  *
  * A tab BELONGS to a pane, and the pane is what splits; the tab strip is per-pane for the same
- * reason. This is the minimal model P3 asks for: an ordered list and an active id, with no rules
- * for derived panes and no follow behaviour (those are P8).
+ * reason. The model is deliberately minimal, an ordered list and an active id; derived panes and
+ * their follow behaviour (§18.4) sit beside it in `derived` rather than in either.
  */
 export interface Pane {
   id: string;
@@ -357,10 +358,10 @@ export function focusOtherPane() {
  * `session.ui.canvasMode`), one picked the replacement kind, and two narrowed what the controls
  * offered so no dropdown could contain an entry the app would refuse.
  *
- * The cap existed because a second LIVE canvas host was unaffordable, and it is gone because
- * workstream 1 made it affordable — see {@link MAX_PANES}. Its LAST act was a bug: `capToPaneKind`
- * flipped a splitting Design tab to `source` before focus moved, so `⌘\` on a page you were
- * designing silently became "open this as Code somewhere else".
+ * The cap existed because a second LIVE canvas host was unaffordable, and it is gone because render
+ * fan-out (§18.2) made it affordable — see {@link MAX_PANES}. Its LAST act was a bug:
+ * `capToPaneKind` flipped a splitting Design tab to `source` before focus moved, so `⌘\` on a page
+ * you were designing silently became "open this as Code somewhere else".
  *
  * What replaces them is `tabs/tab.ts`'s `editorKindsOf` — the kinds a DOCUMENT declares — which is
  * the only narrowing left and the only one that was ever about the document rather than about what
@@ -371,7 +372,7 @@ export function focusOtherPane() {
  * Split the grid and move a tab into the new pane, which becomes focused.
  *
  * Moves rather than duplicates: one tab is one document with one undo history and one collab
- * session, and two strips claiming the same id is the duplicate-`repeat`-key bug §4.3 describes.
+ * session, and two strips claiming the same id is the duplicate-`repeat`-key bug §14.1 describes.
  *
  * The subject is `tabId` when given, else the focused pane's active tab. The drag resolver names
  * the tab it is carrying — the gesture points at a chip, not at whatever the keyboard is in — and
@@ -607,11 +608,11 @@ export function paneIsEmpty(pane: Pane): boolean {
   return pane.tabOrder.length === 0 && pane.derived === null;
 }
 
-/* No `togglePaneZoom`. Zoom is a view of a GRID, and there is no grid: §18.3 hands the one stage
-   between panes, so the focused pane already fills the shell and the other one is not on screen to
-   be zoomed away from. The state existed, both commands wrote it, and nothing that draws ever read
-   it — a control whose only observable effect is on itself. It comes back with the second live
-   host, and not one release earlier. */
+/* No `togglePaneZoom`. It was removed when the shell still handed one stage between panes: the
+   focused pane already filled the shell, so the state existed, both commands wrote it, and nothing
+   that draws ever read it — a control whose only observable effect is on itself. There is a grid of
+   live panes now (§18.3), so a zoom is buildable, but no section of studio.md asks for one; it
+   comes back with the section that does, and not one release earlier. */
 
 /**
  * Remove a tab id from whichever pane holds it, without touching the tab itself.
@@ -696,6 +697,13 @@ function defaultSlot(pane: Pane, tabId: string): number {
  * @param {object | null} [config]
  */
 export function setWorkspaceProject(root: string | null, config: object | null = null) {
+  /* Leaving a project drops the assistant's record of what each turn changed (ai.md §3.2). It
+     names project-relative paths, and its Restore undoes the active tab, so carried into another
+     project it would list files that are not there and undo a document the turn never touched.
+     Adopting a project from none keeps it: a bootstrap conversation follows the project it made. */
+  if (workspace.projectRoot && root !== workspace.projectRoot) {
+    resetAiWrites();
+  }
   workspace.projectRoot = root;
   workspace.projectConfig = config;
 }
@@ -820,12 +828,12 @@ function setActiveTab(tabId: string, opts: { cycling?: boolean; focus?: boolean
  * keys. Callers that mean "show me this file" should use `files/files.ts`'s `openFileInTab`, which
  * activates the existing tab instead.
  *
- * `preview: true` opens a DISPOSABLE tab (§4.3): single-clicking through the tree or the palette is
- * browsing, and browsing must not litter, so the next preview open in the same pane takes its slot.
- * It is opt-in rather than the default because only the CALLER knows whether the author was
- * browsing or committing — an author who typed a new file name has committed, and silently
- * discarding that tab on their next click is the one failure a preview tab must never have.
- * {@link promoteTab} records a commitment made after the fact.
+ * `preview: true` opens a DISPOSABLE tab (docs/studio/interface/tabs.md): single-clicking through
+ * the tree or the palette is browsing, and browsing must not litter, so the next preview open in
+ * the same pane takes its slot. It is opt-in rather than the default because only the CALLER knows
+ * whether the author was browsing or committing — an author who typed a new file name has
+ * committed, and silently discarding that tab on their next click is the one failure a preview tab
+ * must never have. {@link promoteTab} records a commitment made after the fact.
  *
  * `paneId` says WHERE, and `focus` says whether the keyboard goes with it. Both default to today's
  * answer — the focused pane, and yes — because "open this document" has always meant "in front of
@@ -1383,12 +1391,12 @@ export function tabCommands(deps: TabCommandDeps): AnyCommand[] {
           "Use it when the user should SEE the page, or for iterative visual refinement after " +
           "creating a page or component.",
         name: "open_document",
-        /* The person's own read: `activeTab` is what the tab strip highlights, and `editor.kind`
-           is the fact the document-tree tier is gated on. Both are named so the model learns in one
+        /* The person's own read: `activeTab` is what the tab strip highlights, and `editor.kind` is
+           the fact the document-tree tier is gated on. Both are named so the model learns in one
            round whether the tree tools reach the file it opened — a `.csv` lands in the Grid, a
            `.png` in the Media viewer, and neither is an element tree. The `.value` read is module
-           state, which a projected `report` may close over (§12.4); `after` alone cannot say WHICH
-           document is active. */
+           state, which a projected `report` may close over (studio-ui-guidelines.md §12.4); `after`
+           alone cannot say WHICH document is active. */
         report: ({ after, args }) => {
           const path = stringArg("document.open", args, "path");
           const active = activeTab.value?.documentPath ?? null;
@@ -1402,11 +1410,12 @@ export function tabCommands(deps: TabCommandDeps): AnyCommand[] {
           return `"${path}" is the active document, ${where}.`;
         },
       },
-      /* Refuses by THROWING (§12.4's first review rule). `openFileInTab` reports a file it cannot
-         open as a Problem and returns normally — the right answer for a click in the Files tree,
-         where the toast is in front of the person — so the record has to look for the tab itself.
-         The hand tool this replaced read `getTab()` after the open and called whatever it found a
-         success, so a missing file left the PREVIOUS document active and reported "Switched to". */
+      /* Refuses by THROWING (studio-ui-guidelines.md §12.4's first review rule). `openFileInTab`
+         reports a file it cannot open as a Problem and returns normally — the right answer for a
+         click in the Files tree, where the toast is in front of the person — so the record has to
+         look for the tab itself. The hand tool this replaced read `getTab()` after the open and
+         called whatever it found a success, so a missing file left the PREVIOUS document active and
+         reported "Switched to". */
       run: async (_ctx, args) => {
         const path = stringArg("document.open", args, "path");
         await deps.openFile(path);
@@ -1435,8 +1444,9 @@ export function tabCommands(deps: TabCommandDeps): AnyCommand[] {
       group: "1_file",
       when: (ctx) => ctx.project.open,
       requires: "an open project",
-      /* No `aiTool`, by §12.4's first deletion rule: chrome — it arranges what the person is
-         looking at. No `undo`: opening a tab is not a state the undo stack owns. */
+      /* No `aiTool`, by studio-ui-guidelines.md §12.4's first deletion rule: chrome — it arranges
+         what the person is looking at. No `undo`: opening a tab is not a state the undo stack
+         owns. */
       undo: "none",
       /* The non-drag equivalent of dragging a file row onto the other pane's strip (SC 2.5.7): the
          same `receivingPane` the drag resolver uses, so a file tree row and this command can never
@@ -1550,12 +1560,12 @@ export function tabCommands(deps: TabCommandDeps): AnyCommand[] {
  * The pane commands.
  *
  * They live beside the pane model for the same reason the tab commands do, and they are the whole
- * user-facing surface of §4.1's Pane transport: split, focus, unsplit, zoom.
+ * user-facing surface of the pane transport (§18.1): split, focus, unsplit, zoom.
  *
  * `⌘0` and `⌘⌥0` are a PAIR, and they are both bound. `⌘0` was `canvas.zoomReset`, which held it
- * for the one verb of the zoom cluster that also has a button in the floating zoom pod (§3.2 ⑩) —
- * so the chord was the second way to reach a control that is already on screen, while focusing a
- * pane had no way at all. The zoom keeps its pod button and gives up the key.
+ * for the one verb of the zoom cluster that also has a button in the floating zoom pod — so the
+ * chord was the second way to reach a control that is already on screen, while focusing a pane had
+ * no way at all. The zoom keeps its pod button and gives up the key.
  *
  * @param {TabCommandDeps} deps
  * @returns {AnyCommand[]}
@@ -1604,13 +1614,13 @@ export function paneCommands(deps: TabCommandDeps): AnyCommand[] {
       /* This is NOT `pane.derive`, and the distinction is the whole reason both exist. `derive`
          shows a projection OF THIS PANE — its Code, its diff, the same page at another breakpoint —
          and follows it. `compareWith` puts THAT DOCUMENT beside this one and then leaves it alone.
-         Collapsing them would give "open a second document in the other pane" two definition
-         sites, which is how the two names in §4.1 came to disagree in the first place. */
+         Collapsing them would give "open a second document in the other pane" two definition sites,
+         which is how the shell redesign's two names for it came to disagree in the first place. */
       enablement: () => workspace.activeTabId !== null,
       requires: "an open document",
       undo: "none",
-      /* No `aiTool`, by §12.4's first deletion rule: chrome — it arranges what the person is
-         looking at. */
+      /* No `aiTool`, by studio-ui-guidelines.md §12.4's first deletion rule: chrome — it arranges
+         what the person is looking at. */
       run: async (_ctx, args) => {
         const path = stringArg("pane.compareWith", args, "path");
         const here = activePane();

package/styles/canvas.css

@@ -18,32 +18,6 @@
   min-height: 0;
 }
 
-/* ─── Document Header card ─────────────────────
-   Region ⑧: the artefact's own header, drawn IN the stage. `#frontmatter-panel` — a fourth
-   full-width band up to 40vh that appeared and vanished as a side effect of the canvas mode — is
-   gone, grid row and all.
-
-   Two placements, because the stage draws a page two ways. In Edit the card is `in-column`: a block
-   of the document's own centered column that scrolls with it, so it is part of the artefact rather
-   than a strip above it. In Design the artboards are under a pan/zoom transform, and a form drawn
-   at 40% is a picture of a form — so the card is `pinned` above the surface at 1:1, and that is the
-   one placement that still needs a cap. */
-.doc-header-host[hidden] {
-  display: none;
-}
-.doc-header-host.in-column {
-  display: block;
-  padding-bottom: 16px;
-}
-.doc-header-host.pinned {
-  flex-shrink: 0;
-  max-height: 40vh;
-  overflow-y: auto;
-}
-.doc-header-host.pinned .doc-header {
-  border-width: 0 0 1px;
-  border-radius: 0;
-}
 /* ─── Content edit mode canvas ─────────────── */
 .content-edit-canvas {
   width: 100%;
@@ -201,7 +175,7 @@
 .overlay-coselection-group {
   display: contents;
 }
-/* The other members of a multi-selection (§6.5). Same accent, thinner: one box is the primary —
+/* The other members of a multi-selection (§6.7). Same accent, thinner: one box is the primary —
    what the Inspector, the block action bar and the status bar address — and the rest are along for
    the batch. A selection of one draws no co-selection boxes at all. */
 .overlay-coselection {

package/styles/inspector.css

@@ -76,7 +76,7 @@
   text-decoration: underline;
 }
 
-/* ─── Provenance dots on a section heading (plan §6.2) ────────────────────────
+/* ─── Provenance dots on a section heading (§6.7) ─────────────────────────────
    The chip itself is styled with the rest of the row vocabulary further down —
    one block, because Style and Component Props are the same chip in two
    cascades. What is only needed here is the DOT form: a collapsed accordion
@@ -93,7 +93,7 @@
   border: none;
   cursor: default;
 }
-/* `mixed` (§6.5) — the multi-selection's own state. Neutral on purpose: unlike the other three it
+/* `mixed` (§6.7) — the multi-selection's own state. Neutral on purpose: unlike the other three it
    says nothing about WHERE the value came from, only that the selected elements disagree, so it
    must not borrow the accent that means "set here" or the amber that means "inherited". */
 .set-dot.provenance-chip--mixed {
@@ -146,7 +146,8 @@
 }
 
 /* ─── The Layout-element card ───────────────────────────────────────────────
-   What the inspector says when you click page chrome — §8.2's first click. */
+   What the inspector says when you click page chrome — the first click a new author makes
+   (docs/studio/design/properties.md, "Layout elements"). */
 .layout-origin {
   display: flex;
   align-items: center;

package/styles/overlays.css

@@ -232,7 +232,7 @@
   color: var(--danger);
 }
 
-/* ─── ④ The toast host — the fourth overlay layer ─────────────────────────── */
+/* ─── The toast host — the fourth overlay layer ───────────────────────────── */
 /* The consequence line inside a destructive confirmation — what this delete or rename breaks, and
    what survives it. Set apart from the question above it, because the question is a sentence the
    user already wrote in their head and this is the part they have not thought about. */

package/styles/tokens.css

@@ -12,7 +12,11 @@
 
    The four --canvas-* steps are the exception and are meant to be: they colour surfaces that
    render as a light DOCUMENT in both chromes, so they are mixed from the black and white keywords
-   and do not follow the theme. See tokens.json for what else moved here out of styles/spectrum.css. */
+   and do not follow the theme. See tokens.json for what else moved here out of styles/spectrum.css.
+
+   user-select: none on :root is Studio's selection policy: the chrome is not text. Every surface
+   inherits it, a modal dialog restates it below, and a part whose text the reader must copy opts
+   back in from its own surface document, against the list tests/selection-policy.test.ts holds. */
 
 :root {
   box-sizing: border-box;
@@ -24,6 +28,7 @@
   font-family: var(--jx-font-sans, -apple-system, BlinkMacSystemFont, "Segoe UI", system-ui, sans-serif);
   font-size: var(--jx-text-md, 12px);
   line-height: 1.5;
+  user-select: none;
   --panel-w-left: 240px;
   --panel-w-right: 280px;
   --bg: var(--jx-bg, #111114);
@@ -89,6 +94,17 @@
   overflow: hidden;
   background: var(--jx-bg, #111114);
 }
+/* The root's `user-select: none` restated, because a modal dialog would otherwise take it back:
+   Chromium's UA sheet gives a MODAL dialog `user-select: text` (measured: `auto` while closed or
+   after show(), `text` after showModal()), and Blink inherits that into every node inside. Every
+   Studio modal is a jx-dialog opened with showModal(), so without this rule the headline, labels
+   and buttons of every dialog would be selectable whatever the root says. An author rule beats the
+   UA one at any specificity, since it is not `!important`. A dialog's MESSAGE opts back in from
+   its own surface document (`surfaces/dialog.json`), and an input inside one stays selectable
+   without help. */
+:root dialog {
+  user-select: none;
+}
 :root[data-theme="light"],
 :root[data-theme="light"] body {
   background: var(--jx-bg, #f7f7f9);

package/styles/tokens.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://jxsuite.com/schema/v1",
   "$id": "StudioTokens",
-  "$description": "Studio's global base and its semantic token layer, as a Jx style block. `styles/tokens.css` is GENERATED from this by `scripts/build-styles.ts`; edit this file and run `bun run styles:sync`. It stays a linked stylesheet because every declaration in it is pre-paint: the kit's own theme is adopted from JavaScript, so these hex fallbacks are what paints the shell before that lands. THE LAST OF `styles/spectrum.css` IS HERE. That file was the whole of what was declared ON the `sp-theme` element, where Spectrum's own ramp was in scope and `:root` was not, and its header said it would be deleted whole when that element went. It has: the box is `#shell-root` in `shell-frame.json`, the typography is the four declarations above (the sans stack is the kit's and 12px is `--jx-text-md`, which is what `--spectrum-font-size-75` resolved to), and `--case-c`/`--slot-c` are aliases in the same idiom as `--switch-c`, at the values `panel-outline.json` had already written down as their fallbacks. THE FOUR `--canvas-*` STEPS DO NOT FOLLOW THE THEME, and that is the point of them rather than an oversight: they colour surfaces that render as a light DOCUMENT in both chromes — the stylebook, the element-card previews, the empty-slot placeholder on the canvas — so they are mixed from the `black` and `white` KEYWORDS, which is what `var(--spectrum-black)`/`var(--spectrum-white)` were. Seven more steps were declared beside them and no rule in the package ever read one, so those are not here. The four `--data-*` syntax colours are not here either, for a reason `panel-data.json` states outright: nothing read them, they were declared for a palette nobody wrote, and `data-tone` still carries the type on every value for the day somebody does.",
+  "$description": "Studio's global base and its semantic token layer, as a Jx style block. `styles/tokens.css` is GENERATED from this by `scripts/build-styles.ts`; edit this file and run `bun run styles:sync`. It stays a linked stylesheet because every declaration in it is pre-paint: the kit's own theme is adopted from JavaScript, so these hex fallbacks are what paints the shell before that lands. THE LAST OF `styles/spectrum.css` IS HERE. That file was the whole of what was declared ON the `sp-theme` element, where Spectrum's own ramp was in scope and `:root` was not, and its header said it would be deleted whole when that element went. It has: the box is `#shell-root` in `shell-frame.json`, the typography is the four declarations above (the sans stack is the kit's and 12px is `--jx-text-md`, which is what `--spectrum-font-size-75` resolved to), and `--case-c`/`--slot-c` are aliases in the same idiom as `--switch-c`, at the values `panel-outline.json` had already written down as their fallbacks. THE FOUR `--canvas-*` STEPS DO NOT FOLLOW THE THEME, and that is the point of them rather than an oversight: they colour surfaces that render as a light DOCUMENT in both chromes — the stylebook, the element-card previews, the empty-slot placeholder on the canvas — so they are mixed from the `black` and `white` KEYWORDS, which is what `var(--spectrum-black)`/`var(--spectrum-white)` were. Seven more steps were declared beside them and no rule in the package ever read one, so those are not here. The four `--data-*` syntax colours are not here either, for a reason `panel-data.json` states outright: nothing read them, they were declared for a palette nobody wrote, and `data-tone` still carries the type on every value for the day somebody does. THE CHROME IS NOT TEXT: `user-select: none` on the root is Studio's selection policy, stated once so a drag across the window highlights no label, button or heading; every surface inherits it, `& dialog` restates it where the UA sheet would reopen it, and a part whose text the reader must copy opts back in on that part alone, from its own surface document, against the list `tests/selection-policy.test.ts` holds. Editable controls, Monaco and the canvas iframe keep their own selection and need nothing.",
   "tagName": "html",
   "style": {
     "box-sizing": "border-box",
@@ -13,6 +13,7 @@
     "font-family": "var(--jx-font-sans, -apple-system, BlinkMacSystemFont, \"Segoe UI\", system-ui, sans-serif)",
     "font-size": "var(--jx-text-md, 12px)",
     "line-height": "1.5",
+    "user-select": "none",
     "--panel-w-left": "240px",
     "--panel-w-right": "280px",
     "--bg": "var(--jx-bg, #111114)",
@@ -77,6 +78,10 @@
       "overflow": "hidden",
       "background": "var(--jx-bg, #111114)"
     },
+    "& dialog": {
+      "$description": "The root's `user-select: none` restated, because a modal dialog would otherwise take it back: Chromium's UA sheet gives a MODAL dialog `user-select: text` (measured: `auto` while closed or after show(), `text` after showModal()), and Blink inherits that into every node inside. Every Studio modal is a jx-dialog opened with showModal(), so without this rule the headline, labels and buttons of every dialog would be selectable whatever the root says. An author rule beats the UA one at any specificity, since it is not `!important`. A dialog's MESSAGE opts back in from its own surface document (`surfaces/dialog.json`), and an input inside one stays selectable without help.",
+      "user-select": "none"
+    },
     "&[data-theme=\"light\"], &[data-theme=\"light\"] body": {
       "background": "var(--jx-bg, #f7f7f9)"
     }

package/dist/chunks/entry-commands-w9qsxa6q.js

@@ -1,42 +0,0 @@
-import {
-  createEntry2,
-  registerContentCommands2
-} from "./studio-68fydsrj.js";
-import"./studio-hdc2jt3z.js";
-import"./studio-ctm7bhx5.js";
-import"./studio-5t7ena5z.js";
-import"./studio-x10fp4tp.js";
-import"./studio-4c041r8y.js";
-import"./studio-q0a3yk4n.js";
-import"./studio-4r14yzyy.js";
-import"./studio-y4f9fdge.js";
-import"./studio-9j6sfeba.js";
-import"./studio-x72j58vw.js";
-import"./studio-nq5yf5mp.js";
-import"./studio-etvx9s2g.js";
-import"./studio-mpzwze9x.js";
-import"./studio-zjjde71a.js";
-import"./studio-z2smx5ce.js";
-import"./studio-en82c639.js";
-import"./studio-c07s5ckd.js";
-import"./studio-ez11dmdh.js";
-import"./studio-wnsyffg1.js";
-import"./studio-m1p9b6c3.js";
-import"./studio-esrxgwh6.js";
-import"./studio-28vs5k2y.js";
-import"./studio-6nzaktvy.js";
-import"./studio-qa7fzxan.js";
-import"./studio-ympe0n7a.js";
-import"./studio-1k325pwf.js";
-import"./studio-p6pmwkvh.js";
-import"./studio-yxa81f45.js";
-import"./studio-3ntvq6cg.js";
-import"./studio-d8z5bajd.js";
-import"./studio-tjjk7jvk.js";
-export {
-  createEntry2 as createEntry,
-  registerContentCommands2 as registerContentCommands
-};
-
-//# debugId=474288D19E3E71A764756E2164756E21
-//# sourceMappingURL=entry-commands-w9qsxa6q.js.map

package/dist/chunks/layers-panel-fksbdg4q.js

@@ -1,40 +0,0 @@
-import {
-  startLayerTitleEdit2,
-  registerLayersPanel2
-} from "./studio-hhskq2mr.js";
-import"./studio-2mdbbc76.js";
-import"./studio-a1pswps3.js";
-import"./studio-ncn9e189.js";
-import"./studio-5nz00bhh.js";
-import"./studio-ctm7bhx5.js";
-import"./studio-q0a3yk4n.js";
-import"./studio-4r14yzyy.js";
-import"./studio-x72j58vw.js";
-import"./studio-nq5yf5mp.js";
-import"./studio-etvx9s2g.js";
-import"./studio-mpzwze9x.js";
-import"./studio-zjjde71a.js";
-import"./studio-z2smx5ce.js";
-import"./studio-en82c639.js";
-import"./studio-c07s5ckd.js";
-import"./studio-ez11dmdh.js";
-import"./studio-wnsyffg1.js";
-import"./studio-m1p9b6c3.js";
-import"./studio-esrxgwh6.js";
-import"./studio-28vs5k2y.js";
-import"./studio-6nzaktvy.js";
-import"./studio-qa7fzxan.js";
-import"./studio-ympe0n7a.js";
-import"./studio-1k325pwf.js";
-import"./studio-p6pmwkvh.js";
-import"./studio-yxa81f45.js";
-import"./studio-3ntvq6cg.js";
-import"./studio-d8z5bajd.js";
-import"./studio-tjjk7jvk.js";
-export {
-  registerLayersPanel2 as registerLayersPanel,
-  startLayerTitleEdit2 as startLayerTitleEdit
-};
-
-//# debugId=0A17594D4CFC8C3764756E2164756E21
-//# sourceMappingURL=layers-panel-fksbdg4q.js.map

package/dist/chunks/publish-panel-vz23wwmg.js

@@ -1,27 +0,0 @@
-import {
-  seedPublishConnected2,
-  openPublishPanel2
-} from "./studio-14d9tq4d.js";
-import"./studio-vn5hske5.js";
-import"./studio-c04nzbby.js";
-import"./studio-9j6sfeba.js";
-import"./studio-mpzwze9x.js";
-import"./studio-z2smx5ce.js";
-import"./studio-ez11dmdh.js";
-import"./studio-wnsyffg1.js";
-import"./studio-m1p9b6c3.js";
-import"./studio-28vs5k2y.js";
-import"./studio-6nzaktvy.js";
-import"./studio-ympe0n7a.js";
-import"./studio-1k325pwf.js";
-import"./studio-p6pmwkvh.js";
-import"./studio-yxa81f45.js";
-import"./studio-3ntvq6cg.js";
-import"./studio-d8z5bajd.js";
-export {
-  openPublishPanel2 as openPublishPanel,
-  seedPublishConnected2 as seedPublishConnected
-};
-
-//# debugId=6014AB98C3074CCB64756E2164756E21
-//# sourceMappingURL=publish-panel-vz23wwmg.js.map

package/dist/chunks/quick-search-e9rp74m8.js

@@ -1,46 +0,0 @@
-import {
-  initQuickSearch2,
-  openQuickSearch2
-} from "./studio-66arbpc2.js";
-import"./studio-01jeck2y.js";
-import"./studio-vt0tj32j.js";
-import"./studio-wjpgxywa.js";
-import"./studio-t171hxhe.js";
-import"./studio-5nz00bhh.js";
-import"./studio-hdc2jt3z.js";
-import"./studio-t3adrr56.js";
-import"./studio-5t7ena5z.js";
-import"./studio-x10fp4tp.js";
-import"./studio-4c041r8y.js";
-import"./studio-q0a3yk4n.js";
-import"./studio-4r14yzyy.js";
-import"./studio-y4f9fdge.js";
-import"./studio-9j6sfeba.js";
-import"./studio-x72j58vw.js";
-import"./studio-nq5yf5mp.js";
-import"./studio-etvx9s2g.js";
-import"./studio-mpzwze9x.js";
-import"./studio-zjjde71a.js";
-import"./studio-z2smx5ce.js";
-import"./studio-en82c639.js";
-import"./studio-c07s5ckd.js";
-import"./studio-ez11dmdh.js";
-import"./studio-wnsyffg1.js";
-import"./studio-m1p9b6c3.js";
-import"./studio-esrxgwh6.js";
-import"./studio-28vs5k2y.js";
-import"./studio-6nzaktvy.js";
-import"./studio-qa7fzxan.js";
-import"./studio-ympe0n7a.js";
-import"./studio-1k325pwf.js";
-import"./studio-p6pmwkvh.js";
-import"./studio-yxa81f45.js";
-import"./studio-3ntvq6cg.js";
-import"./studio-d8z5bajd.js";
-export {
-  initQuickSearch2 as initQuickSearch,
-  openQuickSearch2 as openQuickSearch
-};
-
-//# debugId=1B07B932BE385C7264756E2164756E21
-//# sourceMappingURL=quick-search-e9rp74m8.js.map

package/dist/chunks/right-panel-j97t2yvy.js

@@ -1,45 +0,0 @@
-import {
-  mount2,
-  unmount2,
-  render2,
-  inspectorTab2,
-  setInspectorTab2
-} from "./studio-15f3kxqe.js";
-import"./studio-2mdbbc76.js";
-import"./studio-a1pswps3.js";
-import"./studio-ncn9e189.js";
-import"./studio-5nz00bhh.js";
-import"./studio-ctm7bhx5.js";
-import"./studio-4r14yzyy.js";
-import"./studio-x72j58vw.js";
-import"./studio-nq5yf5mp.js";
-import"./studio-etvx9s2g.js";
-import"./studio-mpzwze9x.js";
-import"./studio-zjjde71a.js";
-import"./studio-z2smx5ce.js";
-import"./studio-en82c639.js";
-import"./studio-c07s5ckd.js";
-import"./studio-ez11dmdh.js";
-import"./studio-wnsyffg1.js";
-import"./studio-m1p9b6c3.js";
-import"./studio-esrxgwh6.js";
-import"./studio-28vs5k2y.js";
-import"./studio-6nzaktvy.js";
-import"./studio-qa7fzxan.js";
-import"./studio-ympe0n7a.js";
-import"./studio-1k325pwf.js";
-import"./studio-p6pmwkvh.js";
-import"./studio-yxa81f45.js";
-import"./studio-3ntvq6cg.js";
-import"./studio-d8z5bajd.js";
-import"./studio-tjjk7jvk.js";
-export {
-  inspectorTab2 as inspectorTab,
-  mount2 as mount,
-  render2 as render,
-  setInspectorTab2 as setInspectorTab,
-  unmount2 as unmount
-};
-
-//# debugId=ACC2FC3785A3466764756E2164756E21
-//# sourceMappingURL=right-panel-j97t2yvy.js.map

package/dist/chunks/studio-727xh0e3.js

@@ -1,76 +0,0 @@
-// ../collab/src/ops.ts
-function jsonClone(value) {
-  return JSON.parse(JSON.stringify(value));
-}
-function cloneValue2(v) {
-  return v === undefined || v === null ? v : jsonClone(v);
-}
-function getNodeAtPath3(doc, path) {
-  let node = doc;
-  for (const key of path) {
-    if (node == null) {
-      return;
-    }
-    node = node[key];
-  }
-  return node;
-}
-function childArray2(node) {
-  if (Array.isArray(node)) {
-    throw new TypeError("Cannot insert into a children array; parentPath must point at a node");
-  }
-  if (!node.children) {
-    node.children = [];
-  }
-  if (!Array.isArray(node.children)) {
-    throw new TypeError("Cannot insert into mapped-array children; edit the map template instead");
-  }
-  return node.children;
-}
-function applyDocOpToDoc2(doc, op) {
-  switch (op.op) {
-    case "set-key": {
-      const node = getNodeAtPath3(doc, op.path);
-      if (!node) {
-        throw new Error(`doc-op-node-not-found:${op.path.join("/")}`);
-      }
-      const target = node;
-      if (op.value === undefined) {
-        delete target[op.key];
-      } else {
-        target[op.key] = cloneValue2(op.value);
-      }
-      return;
-    }
-    case "insert-child": {
-      const parent = getNodeAtPath3(doc, op.parentPath);
-      childArray2(parent).splice(op.index, 0, cloneValue2(op.node));
-      return;
-    }
-    case "remove-child": {
-      const parent = getNodeAtPath3(doc, op.parentPath);
-      childArray2(parent).splice(op.index, 1);
-      return;
-    }
-    case "set-child": {
-      const parent = getNodeAtPath3(doc, op.parentPath);
-      childArray2(parent).splice(op.index, 1, cloneValue2(op.node));
-      return;
-    }
-    case "move-child": {
-      const fromParent = getNodeAtPath3(doc, op.fromParentPath);
-      const toParent = getNodeAtPath3(doc, op.toParentPath);
-      const [node] = childArray2(fromParent).splice(op.fromIndex, 1);
-      childArray2(toParent).splice(op.toIndex, 0, node);
-      return;
-    }
-    default: {
-      throw new Error(`unknown-doc-op:${op.op}`);
-    }
-  }
-}
-
-export { cloneValue2, getNodeAtPath3, childArray2, applyDocOpToDoc2 };
-
-//# debugId=32556033BC6FC83D64756E2164756E21
-//# sourceMappingURL=studio-727xh0e3.js.map