@weasel-js/labkit 1.0.3 → 1.0.4

package/dist/_dts/{DrawCommand-uKHt4Vul.d.ts → DrawCommand-BkZztJsW.d.ts}

@@ -185,7 +185,9 @@ interface History {
      *  2026-05-24-modality-design.md for the full lifecycle. */
     beginJournal(opts: BeginJournalOptions): Journal;
     /** Re-activate a suspended journal. Throws if the journal was committed or
-     *  cancelled (those are terminal). Staleness checking is the caller's
+     *  cancelled (those are terminal), or if a different journal is currently
+     *  active — at most one journal writes to the adapter at a time, on resume
+     *  as well as on open. Staleness checking is the caller's
      *  responsibility — consult `journal.forkedAtEntryId` against
      *  `currentEntryId()` and your own op-semantic rules to decide whether
      *  to resume or discard before calling this. */

package/dist/_dts/{useExperimentState-vrttakTt.d.ts → useExperimentState-D7EQnnwJ.d.ts}

@@ -43,6 +43,9 @@ interface LabStoreState {
     workspaces: WorkspaceRecord[];
     savedSnapshots: SavedSnapshot[];
     mode: LabMode;
+    /** Per-workspace tile extents, keyed by workspace id. Opaque here — the
+     *  shape belongs to whatever lays the workspaces out. */
+    layout: Record<string, unknown>;
 }
 /** Where a lab persists itself. Implementations are keyed string storage and
  *  nothing more, so the same store works against localStorage, the URL hash,
@@ -103,6 +106,7 @@ interface LabStoreActions {
     deleteSnapshot: (snapshotId: string) => void;
     listSnapshots: (workspaceId?: string) => SavedSnapshot[];
     setMode: (mode: LabMode) => void;
+    setLayout: (layout: Record<string, unknown>) => void;
 }
 /** A lab's store: its state and actions, plus the hook instruments use to
  *  register how their state is serialized. */