@avocadostudio-ai/preview-adapter 0.8.0 → 0.10.0

package/dist/bridge-functions.d.ts

@@ -200,39 +200,26 @@ export declare function removeSkeletons(): void;
  */
 export declare function missingBlockWrapperWarning(blockCount: number, editableCount: number): string | null;
 /**
- * The other half of a half-finished integration — and the likelier half.
+ * Every integration problem the overlay can diagnose from the page alone.
  *
- * `missingBlockWrapperWarning` names the case where the fields are marked and
- * the blocks are not. This names its mirror, which is what following the
- * integration guide to its end and stopping one step early actually produces:
- * every block wrapped, no field marked. Wrapping blocks is a single call in the
- * preview route; marking fields means touching the site's own components, so it
- * is the step that gets deferred and then forgotten.
- *
- * What it costs is invisible rather than broken. Selection works. Highlighting,
- * scroll-to-block, the badges, the property panel and every edit made through
- * it all work, because the panel is built from the block manifest and never
- * looks at the page. What is silently off is everything the overlay finds by
- * walking the DOM: inline text editing, the field pills on hover, the image
- * Change/Remove buttons, and the live-draft path that streams a field into the
- * node that draws it. A reviewer sees a preview that responds to clicks and
- * concludes it is wired.
- *
- * Like its mirror this is an all-or-nothing test, not a coverage check: one
- * marked field means the integrator knows the attribute exists, and which of
- * their fields deserve it is their call, not ours.
+ * One, today. Its mirror — every block wrapped and not one field marked — used
+ * to be reported here too, and was withdrawn: that state is a preview whose
+ * selection, property panel, chat and publish all work, missing an opt-in step
+ * the integrator has not taken yet. Saying so on a dev overlay put a red
+ * Console Error on a working integration, which reads as a defect in the
+ * product rather than as an invitation. Marking fields is now its own named
+ * step in the docs, and whether a page has taken it is what
+ * `site-sdk/coverage` measures, on demand, for someone who asked.
  */
-export declare function missingEditableTargetsWarning(blockCount: number, editableCount: number): string | null;
-/** Every integration problem the overlay can diagnose from the page alone. */
 export declare function previewIntegrationWarnings(blockCount: number, editableCount: number): string[];
 /**
  * Put the diagnosis where the person is looking.
  *
- * Both warnings above describe a preview that looks like it works, so the
- * console they would print to is the one nobody opens — and in the editor it is
+ * The warning above describes a preview that looks like it works, so the
+ * console it would print to is the one nobody opens — and in the editor it is
  * the *iframe's* console, two context menus away from the window in front of
- * the user. The symptom is "the button is missing from the preview"; the
- * explanation has to be in the preview.
+ * the user. The symptom is "clicking a block does nothing"; the explanation
+ * has to be in the preview.
  *
  * Development only, and dismissible: it sits over the site's own design, and
  * once read it has done its work.

package/dist/bridge-functions.js

@@ -606,54 +606,28 @@ export function missingBlockWrapperWarning(blockCount, editableCount) {
         "editor-selectable class that the field pills are scoped to.");
 }
 /**
- * The other half of a half-finished integration — and the likelier half.
+ * Every integration problem the overlay can diagnose from the page alone.
  *
- * `missingBlockWrapperWarning` names the case where the fields are marked and
- * the blocks are not. This names its mirror, which is what following the
- * integration guide to its end and stopping one step early actually produces:
- * every block wrapped, no field marked. Wrapping blocks is a single call in the
- * preview route; marking fields means touching the site's own components, so it
- * is the step that gets deferred and then forgotten.
- *
- * What it costs is invisible rather than broken. Selection works. Highlighting,
- * scroll-to-block, the badges, the property panel and every edit made through
- * it all work, because the panel is built from the block manifest and never
- * looks at the page. What is silently off is everything the overlay finds by
- * walking the DOM: inline text editing, the field pills on hover, the image
- * Change/Remove buttons, and the live-draft path that streams a field into the
- * node that draws it. A reviewer sees a preview that responds to clicks and
- * concludes it is wired.
- *
- * Like its mirror this is an all-or-nothing test, not a coverage check: one
- * marked field means the integrator knows the attribute exists, and which of
- * their fields deserve it is their call, not ours.
+ * One, today. Its mirror — every block wrapped and not one field marked — used
+ * to be reported here too, and was withdrawn: that state is a preview whose
+ * selection, property panel, chat and publish all work, missing an opt-in step
+ * the integrator has not taken yet. Saying so on a dev overlay put a red
+ * Console Error on a working integration, which reads as a defect in the
+ * product rather than as an invitation. Marking fields is now its own named
+ * step in the docs, and whether a page has taken it is what
+ * `site-sdk/coverage` measures, on demand, for someone who asked.
  */
-export function missingEditableTargetsWarning(blockCount, editableCount) {
-    if (editableCount > 0 || blockCount === 0)
-        return null;
-    return (`[avocado] The overlay found ${blockCount} [data-block-id] wrapper(s) and no ` +
-        "data-editable-target attribute. Selection and the property panel work; inline text " +
-        "editing, the field pills and the image Change/Remove buttons are all off, because every " +
-        "one of them is found by walking the marked fields in the page.\n" +
-        "Mark the element that draws each editable prop with editableProps(path, { kind }) from " +
-        "@avocadostudio-ai/site-sdk/editor — e.g. editableProps(\"imageUrl\", { kind: \"image\" }) " +
-        "on the wrapper around an image, editableProps(\"heading\") on the element holding it.");
-}
-/** Every integration problem the overlay can diagnose from the page alone. */
 export function previewIntegrationWarnings(blockCount, editableCount) {
-    return [
-        missingBlockWrapperWarning(blockCount, editableCount),
-        missingEditableTargetsWarning(blockCount, editableCount),
-    ].filter((w) => w !== null);
+    return [missingBlockWrapperWarning(blockCount, editableCount)].filter((w) => w !== null);
 }
 /**
  * Put the diagnosis where the person is looking.
  *
- * Both warnings above describe a preview that looks like it works, so the
- * console they would print to is the one nobody opens — and in the editor it is
+ * The warning above describes a preview that looks like it works, so the
+ * console it would print to is the one nobody opens — and in the editor it is
  * the *iframe's* console, two context menus away from the window in front of
- * the user. The symptom is "the button is missing from the preview"; the
- * explanation has to be in the preview.
+ * the user. The symptom is "clicking a block does nothing"; the explanation
+ * has to be in the preview.
  *
  * Development only, and dismissible: it sits over the site's own design, and
  * once read it has done its work.

package/dist/index.d.ts

@@ -2,7 +2,7 @@ export { PreviewBridge } from "./preview-bridge.tsx";
 export { PreviewBridgeCore } from "./preview-bridge-core.tsx";
 export type { PreviewBridgeConfig, PreviewBridgeCoreProps } from "./preview-bridge-core.tsx";
 export { getPreviewWrapperProps } from "./selectable.ts";
-export { createBridgeFunctions, createBridgeState, findBlockNode, findEditableNode, scrollBlockIntoView, parseListItemPath, supportsInlineEditablePath, readNodeText, placeCaretAtEnd, orderedBlockNodes, blockOrderIndex, computeMoveAfter, computeInsertBefore, groupListItemNodes, commonItemRoot, markdownToHtml, withPreviewParams, setNestedLabelsVisibility, clearChildFocus, clearListItemSelection, removeOverlayControls, clearAllHighlights, showSkeleton, removeSkeletons, ensureBlockBadges, applyAiFieldLoading, cleanupOverlayElements, isImageEditable, isInlineEditable, isMultilineEditable, missingBlockWrapperWarning, missingEditableTargetsWarning, previewIntegrationWarnings, } from "./bridge-functions.ts";
+export { createBridgeFunctions, createBridgeState, findBlockNode, findEditableNode, scrollBlockIntoView, parseListItemPath, supportsInlineEditablePath, readNodeText, placeCaretAtEnd, orderedBlockNodes, blockOrderIndex, computeMoveAfter, computeInsertBefore, groupListItemNodes, commonItemRoot, markdownToHtml, withPreviewParams, setNestedLabelsVisibility, clearChildFocus, clearListItemSelection, removeOverlayControls, clearAllHighlights, showSkeleton, removeSkeletons, ensureBlockBadges, applyAiFieldLoading, cleanupOverlayElements, isImageEditable, isInlineEditable, isMultilineEditable, missingBlockWrapperWarning, previewIntegrationWarnings, } from "./bridge-functions.ts";
 export type { BridgeCallbacks, BridgeState, BridgeFunctions } from "./bridge-functions.ts";
 export { LivePreviewProvider, useLivePreviewBlocks, useLivePreviewBridgeApi, } from "./live-preview-store.tsx";
 export type { LivePreviewPage, LivePreviewBridgeApi } from "./live-preview-store.tsx";

package/dist/index.js

@@ -1,5 +1,5 @@
 export { PreviewBridge } from "./preview-bridge.js";
 export { PreviewBridgeCore } from "./preview-bridge-core.js";
 export { getPreviewWrapperProps } from "./selectable.js";
-export { createBridgeFunctions, createBridgeState, findBlockNode, findEditableNode, scrollBlockIntoView, parseListItemPath, supportsInlineEditablePath, readNodeText, placeCaretAtEnd, orderedBlockNodes, blockOrderIndex, computeMoveAfter, computeInsertBefore, groupListItemNodes, commonItemRoot, markdownToHtml, withPreviewParams, setNestedLabelsVisibility, clearChildFocus, clearListItemSelection, removeOverlayControls, clearAllHighlights, showSkeleton, removeSkeletons, ensureBlockBadges, applyAiFieldLoading, cleanupOverlayElements, isImageEditable, isInlineEditable, isMultilineEditable, missingBlockWrapperWarning, missingEditableTargetsWarning, previewIntegrationWarnings, } from "./bridge-functions.js";
+export { createBridgeFunctions, createBridgeState, findBlockNode, findEditableNode, scrollBlockIntoView, parseListItemPath, supportsInlineEditablePath, readNodeText, placeCaretAtEnd, orderedBlockNodes, blockOrderIndex, computeMoveAfter, computeInsertBefore, groupListItemNodes, commonItemRoot, markdownToHtml, withPreviewParams, setNestedLabelsVisibility, clearChildFocus, clearListItemSelection, removeOverlayControls, clearAllHighlights, showSkeleton, removeSkeletons, ensureBlockBadges, applyAiFieldLoading, cleanupOverlayElements, isImageEditable, isInlineEditable, isMultilineEditable, missingBlockWrapperWarning, previewIntegrationWarnings, } from "./bridge-functions.js";
 export { LivePreviewProvider, useLivePreviewBlocks, useLivePreviewBridgeApi, } from "./live-preview-store.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@avocadostudio-ai/preview-adapter",
-  "version": "0.8.0",
+  "version": "0.10.0",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -37,7 +37,7 @@
     "src/styles.css"
   ],
   "dependencies": {
-    "@avocadostudio-ai/shared": "^0.8.0"
+    "@avocadostudio-ai/shared": "^0.10.0"
   },
   "peerDependencies": {
     "next": ">=15.0.0",