@nivaro/react 0.1.244 → 0.1.246

package/dist/index.d.ts

@@ -2283,6 +2283,8 @@ declare interface LayoutGroup {
     container_id?: number | null;
     is_collapsed?: boolean | number | null;
     visibility_mode?: string | null;
+    /** Migration 311 — read-board width: full | half | third | null (auto). */
+    read_width?: string | null;
 }
 
 export declare type LayoutItem = FormGroupDescriptor | '__ungrouped__';
@@ -3827,12 +3829,26 @@ export declare function RecordGridWidgetBody({ widget }: {
     widget: PageRendererWidget;
 }): JSX.Element;
 
-export declare function RecordReadView({ collection, itemId, layoutData, flush }: {
+export declare function RecordReadView({ collection, itemId, layoutData, flush, renderSlot, integrityMarks }: {
     collection: string;
     itemId: string;
     layoutData: ReadViewLayout;
-    /** Host already pads and scrolls the body (the record form's read mode). */
+    /** Host already pads and scrolls the body (the record form's Summary mode). */
     flush?: boolean;
+    /**
+     * Page-slot sentinels (`__comments__`, `__tasks__`, …) the host wants to
+     * keep LIVE inside the read view — Summary mode is read-only for the
+     * record's fields, but notes and tasks stay editable (Rob). Return null to
+     * skip a slot. A slot placed in a section renders inside that card; the
+     * rest render full-width under the cards, in layout order.
+     */
+    renderSlot?: (key: string, assignment: LayoutAssignment) => ReactNode;
+    /**
+     * Summary mode hides the data-integrity banner but must not hide the
+     * problem: with this on, every field (or child grid) that carries a
+     * finding gets an amber mark whose tip lists the messages.
+     */
+    integrityMarks?: boolean;
 }): JSX.Element;
 
 /**
@@ -3840,8 +3856,9 @@ export declare function RecordReadView({ collection, itemId, layoutData, flush }
  * watermark and, when other people changed the record in between, renders a
  * one-line recap above the form. The server owns the session semantics (a
  * refresh within 30 minutes keeps the same baseline), the strip just shows
- * whatever the touch returned. Dismiss is per-mount — the next genuine visit
- * recomputes against the new baseline anyway.
+ * whatever the touch returned. Dismiss POSTs /dismiss, which collapses the
+ * server baseline to now — a reload inside the session grace stays quiet, and
+ * only changes made after the dismissal come back as news.
  */
 export declare function RecordRecapStrip({ collection, itemId }: {
     collection: string;