@useinsider/guido 3.18.3-beta.ec88281 → 3.19.0-beta.f02eaa1

package/dist/src/stores/guido-email-editor.d.ts

@@ -1,41 +1,41 @@
-/**
- * Outbound contract Guido publishes to the host's shared Pinia singleton so
- * cortex-fe can pick up the current editor state and forward it as
- * `clientState.editor` on the next chat-stream POST.
- *
- * State + getters only — `useGuidoStateBridge` writes via `$patch`, no actions
- * live here (architecture invariant).
- *
- * Store id `guidoEmailEditor` is cross-MFE: cortex-fe reads it via
- * `pinia._s.get('guidoEmailEditor')` at runtime. The internal Guido editor
- * store keeps id `guidoEditor` — these are intentionally separate. The
- * internal store carries UI state that cortex-fe should not see; this public
- * store carries the contract Guido is willing to share.
- */
-export declare const useGuidoEmailEditorStore: import("pinia").StoreDefinition<"guidoEmailEditor", {
+/** The published editor snapshot — the shape a consumer reads off the shared store. */
+export interface GuidoEmailEditorState {
     /** Current Stripo HTML — stripe tables only, no DOCTYPE/wrapper. */
     html: string;
     /** Current Stripo CSS — es-p* utility classes used by the html. */
     css: string;
     /** Wall-clock ms when html/css were last written by the bridge. */
     lastUpdatedAt: number;
-    /** Template id from the editor config, for cortex-fe to scope per-template. */
+    /** Template id from the editor config, so a consumer can scope per-template. */
     templateId: string;
-}, {
+}
+/**
+ * Outbound contract Guido publishes to the host's shared Pinia singleton so a
+ * consumer can read the current editor state: cortex-fe forwards it as
+ * `clientState.editor` on the next chat-stream POST, email-fe scans it for the
+ * Array of Objects lock.
+ *
+ * Published as `@useinsider/guido/editor-state` and from the root barrel, so a
+ * consumer imports this store instead of re-declaring one under the same id.
+ *
+ * State + getters only, no actions. `useGuidoStateBridge` is the only intended
+ * writer, but that is Guido's own convention rather than something the store
+ * enforces: publishing the definition hands a consumer `$patch` as well, exactly
+ * as the runtime `pinia._s` probe always did.
+ *
+ * Store id `guidoEmailEditor` is cross-MFE: cortex-fe reads it via
+ * `pinia._s.get('guidoEmailEditor')` at runtime rather than importing it, so the
+ * id stays part of the contract. The internal Guido editor store keeps id
+ * `guidoEditor` — these are intentionally separate. The internal store carries
+ * UI state a consumer should not see; this public store carries the contract
+ * Guido is willing to share.
+ */
+export declare const useGuidoEmailEditorStore: import("pinia").StoreDefinition<"guidoEmailEditor", GuidoEmailEditorState, {
     /** True once the bridge has published at least one snapshot. */
     hasSnapshot: (state: {
         html: string;
         css: string;
         lastUpdatedAt: number;
         templateId: string;
-    } & import("pinia").PiniaCustomStateProperties<{
-        /** Current Stripo HTML — stripe tables only, no DOCTYPE/wrapper. */
-        html: string;
-        /** Current Stripo CSS — es-p* utility classes used by the html. */
-        css: string;
-        /** Wall-clock ms when html/css were last written by the bridge. */
-        lastUpdatedAt: number;
-        /** Template id from the editor config, for cortex-fe to scope per-template. */
-        templateId: string;
-    }>) => boolean;
+    } & import("pinia").PiniaCustomStateProperties<GuidoEmailEditorState>) => boolean;
 }, {}>;