@gengage/assistant-fe 0.6.49 → 0.6.50

package/dist/chat/runtime.d.ts

@@ -86,6 +86,22 @@ export declare class GengageChat extends BaseWidget<ChatWidgetConfig> {
     private _pdpLaunched;
     private _plpLaunched;
     private _homepageLaunched;
+    /**
+     * True ONLY when this widget actually restored a non-empty thread that now owns the
+     * surface. When set, the generic page-context auto-launch (homepage/PLP greeting) is
+     * suppressed so the restored thread — and its in-flight continuation — are not
+     * clobbered by a "Merhaba!" welcome. See R1 (yataş store-finder nav clobber).
+     *
+     * INVARIANT (regression #1 fix): this flag is tied to ACTUAL restored on-screen
+     * content, never to mere restore-KEY presence. If a restore no-ops (stale/missing
+     * session, cross-SKU guard, IDB absent, empty thread, rejected freshness token) the
+     * flag stays/returns false so the NORMAL greeting/auto-launch fires — the surface is
+     * never left blank.
+     */
+    private _restorePending;
+    /** One-shot gate for an assistant-driven soft navigation update in the same document. */
+    private _assistantSoftNavigationPending;
+    private _assistantSoftNavigationTimer;
     private _entryContextPrimed;
     /** True while a silent context-prime launch (PDP/PLP/homepage) is in flight. */
     private _contextPrimingInFlight;
@@ -177,6 +193,42 @@ export declare class GengageChat extends BaseWidget<ChatWidgetConfig> {
     }): void;
     close(): void;
     saveSession(sessionId: string, sku: string): void;
+    /**
+     * Set the restore handoff marker for an assistant-driven PAGE navigation that has
+     * no associated product (R1, e.g. the store-finder redirect). Mirrors saveSession()
+     * but without a SKU — the destination is not a PDP, so there is nothing to gate the
+     * restore on. The restore session id alone tells the re-mounted widget "the chat
+     * navigated you here; restore the thread and continue, do not auto-launch a greeting".
+     *
+     * Only stamps the marker when there is a real session id to restore; otherwise it is
+     * a no-op (a user/site navigation should stay a fresh session).
+     */
+    saveSessionForNavigation(): void;
+    /** Read the persisted same-document nav sequence (0 when absent/corrupt). */
+    private _readNavSeq;
+    /**
+     * Stamp the freshness token onto the current restore marker: bump the nav seq and
+     * record it (with a timestamp) so the immediately-following mount can recognize this
+     * marker as fresh. Best-effort — non-fatal if sessionStorage is unavailable.
+     */
+    private _stampRestoreFreshnessToken;
+    /**
+     * True when the current restore marker was produced by the immediately-preceding
+     * navigation (its token's seq matches the current nav seq). A stale/stranded marker
+     * — or one with no/corrupt token (e.g. an empty-SKU saveSession) — is NOT fresh.
+     */
+    private _isRestoreMarkerFresh;
+    /**
+     * Clear the restore marker and its freshness token in one place — the single
+     * guaranteed-consume point so a marker never strands. Called on mount (onInit, after
+     * the freshness decision) and on any state reset (_resetForNewPage / soft-nav).
+     * Leaves gengage_nav_seq intact: it is the monotonic clock, not part of the marker.
+     */
+    private _clearRestoreMarker;
+    private _markAssistantSoftNavigationPending;
+    private _clearAssistantSoftNavigationPending;
+    private _expireAssistantSoftNavigationIfUnclaimed;
+    private _scheduleAssistantSoftNavigationExpiry;
     get isOpen(): boolean;
     /**
      * Register a callback for integration events (e.g. 'gengage-cart-add', 'gengage-product-favorite').
@@ -339,11 +391,29 @@ export declare class GengageChat extends BaseWidget<ChatWidgetConfig> {
     private _hasUnavailableProductContext;
     private _ensureAssistantMessageRendered;
     private _saveSessionAndOpenURL;
+    /**
+     * Assistant-driven page navigation (R1): persist the thread, stamp the restore
+     * handoff marker, then navigate. On the SPA re-mount the widget restores the thread
+     * and continues its flow — the homepage/PLP auto-launch greeting is suppressed
+     * (see _restorePending / _primeOpenPageContext) so the assistant's answer is not
+     * clobbered by a generic welcome. Same-origin only; cross-origin/new-tab callers
+     * keep the raw navigation since the current page (and its thread) is not replaced.
+     *
+     * The restore-key stamp is the durable "the chat initiated this navigation" marker
+     * across the navigation boundary — we distinguish assistant-vs-user navigation by
+     * WHO called this (an assistant action handler), never by inspecting the URL.
+     */
+    private _navigateAssistantDriven;
     private _loadPayload;
     /**
      * Attempt to restore chat session from IndexedDB.
-     * Always restores when IDB has session data for the current sessionId.
+     * Restores when IDB has non-empty session data for the current sessionId AND an
+     * explicit handoff is pending.
      * Best-effort — failures are silently ignored.
+     *
+     * @returns true ONLY when a non-empty thread was actually replayed onto the surface.
+     * Every no-op/early-return path returns false so the caller leaves the normal
+     * greeting/auto-launch enabled (regression #1: never suppress launch over nothing).
      */
     private _restoreFromIndexedDB;
     /**

package/dist/chat-runtime.js

@@ -1,4 +1,4 @@
-import { c as e, d as t, f as r, i as s, l as n, n as i, r as l, s as C, t as c, u as d } from "./runtime-COLQGOkl.js";
+import { c as e, d as t, f as r, i as s, l as n, n as i, r as l, s as C, t as c, u as d } from "./runtime-9f9SB4WE.js";
 export {
   d as CHAT_SCROLL_ELEMENT_ID,
   s as ChatPresentationState,