@atlaskit/rovo-triggers 10.30.0 → 10.33.0

package/CHANGELOG.md

@@ -1,5 +1,51 @@
 # @atlaskit/rovo-triggers
 
+## 10.33.0
+
+### Minor Changes
+
+- [`692f360535ec2`](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/commits/692f360535ec2) -
+  Under sprt_hix_9681_workflow_agent_edit_status, group workflow actions under numbered headings in
+  a fixed order, show a consistent previous/updated status diff, fold the shared-workflow warning
+  into the update-status card, show a trash can icon on delete cards, and show the transition name
+  with inline crossed-out previous name and statuses on update-transition cards.
+
+  Adds optional previous-state fields on UpdateTransitionRovoPayload (existingName,
+  existingToStatusId, existingToStatusName, existingToStatusCategory, existingLinks) and exports
+  DeleteTransitionRovoPayloadOld.
+
+## 10.32.0
+
+### Minor Changes
+
+- [`2aa696d5503d0`](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/commits/2aa696d5503d0) -
+  Add a control-message channel to the extension context bridge.
+
+  `request-context` is a message the extension chat may send a product, asking it to re-send the
+  context it has already published. It carries no data: it is a request, not content, and is
+  mutually exclusive with payload messages by construction, so it cannot be used to move content in
+  either direction or to bypass the relay allowlists.
+
+  This exists because the bridge is otherwise fire-and-forget, relaying only what it observes while
+  a chat is listening. That suits a product whose publisher runs continuously, such as the
+  Confluence editor, but not one that publishes once per navigation, such as a Jira view: a chat
+  opened after the page settled would observe nothing at all.
+
+  Additive. `Transport.subscribe` now also carries control messages, so consumers that assume every
+  message has a payload should narrow with the exported `isBridgeControlMessage` guard. Nothing
+  sends or answers requests yet.
+
+## 10.31.0
+
+### Minor Changes
+
+- [`4d3888ae4550d`](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/commits/4d3888ae4550d) -
+  Allow shared Rovo URL parameters to carry a search query using the `rovoChatSearchQuery` key.
+
+### Patch Changes
+
+- Updated dependencies
+
 ## 10.30.0
 
 ### Minor Changes

package/dist/cjs/common/utils/extension-context-bridge/ExtensionContextBridgeClient.js

@@ -93,6 +93,10 @@ var ExtensionContextBridgeClient = exports.ExtensionContextBridgeClient = functi
       return;
     }
     return activeTransport.subscribe(function (message) {
+      // Control messages are requests to the product, never context for the chat.
+      if ((0, _transport.isBridgeControlMessage)(message)) {
+        return;
+      }
       if (message.direction !== _constants.BRIDGE_TO_EXTENSION) {
         return;
       }

package/dist/cjs/common/utils/extension-context-bridge/ExtensionContextBridgeHost.js

@@ -6,6 +6,7 @@ Object.defineProperty(exports, "__esModule", {
 });
 exports.ExtensionContextBridgeHost = void 0;
 var _defineProperty2 = _interopRequireDefault(require("@babel/runtime/helpers/defineProperty"));
+var _typeof2 = _interopRequireDefault(require("@babel/runtime/helpers/typeof"));
 var _react = require("react");
 var _fg = require("@atlaskit/platform-feature-flags/fg");
 var _main = require("../../../main");
@@ -32,6 +33,22 @@ var stampProductContentId = function stampProductContentId(serialized, targetCon
     data.contentMauiId = targetContentId;
   }
 };
+
+/**
+ * Identity of a context *slot*. `set-message-context` is keyed by `contextKey` because a product
+ * publishes several independent contexts, each superseding only its own previous value; everything
+ * else is keyed by payload type, of which there is one live instance at a time.
+ */
+var getContextSlotKey = function getContextSlotKey(payload) {
+  if (payload.type === 'set-message-context') {
+    var data = payload.data;
+    var contextKey = (0, _typeof2.default)(data) === 'object' && data !== null && 'contextKey' in data ? data.contextKey : undefined;
+    if (typeof contextKey === 'string') {
+      return "".concat(payload.type, ":").concat(contextKey);
+    }
+  }
+  return payload.type;
+};
 /**
  * Product-window half of the bridge. Observes the `ai-mate` bus and mirrors allowlisted context out
  * to the extension via same-window `postMessage` (see `./policy` for the allow/deny rules).
@@ -60,6 +77,43 @@ var ExtensionContextBridgeHost = exports.ExtensionContextBridgeHost = function E
       targetWindow: window
     });
   }, [active, transport]);
+
+  /**
+   * The last message relayed for each context slot, kept so a chat opened later can be caught up.
+   *
+   * Deliberately held here rather than in the extension. This is the page's own context, already in
+   * this page's memory, scoped to this document and gone when it unloads — so answering a request
+   * creates no copy that outlives the page, and a chat that is never opened is never sent anything.
+   */
+  var lastRelayedRef = (0, _react.useRef)(new Map());
+
+  // Answers `request-context` from the chat, which cannot observe context published before it
+  // mounted. Products such as Jira publish once per navigation, so without this a chat opened after
+  // the page settled would describe the wrong view — or none at all.
+  (0, _react.useEffect)(function () {
+    if (!activeTransport) {
+      return;
+    }
+    return activeTransport.subscribe(function (message) {
+      if (!(0, _transport.isBridgeControlMessage)(message) || message.direction !== _constants.BRIDGE_TO_PRODUCT) {
+        return;
+      }
+      if (message.control !== _constants.BRIDGE_CONTROL_REQUEST_CONTEXT) {
+        return;
+      }
+      // Re-checked here, not just at relay time: entitlement can change while the page is open.
+      if (isAiEnabled === false) {
+        return;
+      }
+      lastRelayedRef.current.forEach(function (relayed) {
+        try {
+          activeTransport.send(relayed);
+        } catch (_unused) {
+          // Never let bridging break the host page.
+        }
+      });
+    });
+  }, [activeTransport, isAiEnabled]);
   (0, _main.useSubscribeAll)(function (payload) {
     if (!activeTransport) {
       return;
@@ -82,9 +136,19 @@ var ExtensionContextBridgeHost = exports.ExtensionContextBridgeHost = function E
       return;
     }
     stampProductContentId(serialized, getContentId === null || getContentId === void 0 ? void 0 : getContentId());
+    var message = (0, _defineProperty2.default)((0, _defineProperty2.default)((0, _defineProperty2.default)({}, _constants.BRIDGE_MESSAGE_MARKER, true), "direction", _constants.BRIDGE_TO_EXTENSION), "payload", serialized);
+    // Keyed by context slot, not by message, so a re-publish replaces rather than accumulates.
+    // A cleared context is recorded too: replaying it clears the chat rather than resurrecting
+    // context the page no longer shows.
+    //
+    // Publisher contract: in an SPA this component outlives any single route, so a slot stays
+    // filled until its publisher says otherwise. Publishers must clear on unmount (publish with
+    // `setContext` returning undefined) or a later route could be answered with a previous
+    // view's context. Every Jira view-context publisher does this today.
+    lastRelayedRef.current.set(getContextSlotKey(serialized), message);
     try {
-      activeTransport.send((0, _defineProperty2.default)((0, _defineProperty2.default)((0, _defineProperty2.default)({}, _constants.BRIDGE_MESSAGE_MARKER, true), "direction", _constants.BRIDGE_TO_EXTENSION), "payload", serialized));
-    } catch (_unused) {
+      activeTransport.send(message);
+    } catch (_unused2) {
       // Never let bridging break the host page.
     }
   });

package/dist/cjs/common/utils/extension-context-bridge/constants.js

@@ -3,7 +3,7 @@
 Object.defineProperty(exports, "__esModule", {
   value: true
 });
-exports.BRIDGE_TO_PRODUCT = exports.BRIDGE_TO_EXTENSION = exports.BRIDGE_SOURCE = exports.BRIDGE_MESSAGE_MARKER = exports.BRIDGE_FEATURE_GATE = void 0;
+exports.BRIDGE_TO_PRODUCT = exports.BRIDGE_TO_EXTENSION = exports.BRIDGE_SOURCE = exports.BRIDGE_MESSAGE_MARKER = exports.BRIDGE_FEATURE_GATE = exports.BRIDGE_CONTROL_REQUEST_CONTEXT = void 0;
 /**
  * Feature gate for the extension context bridge; both Host and Client self-gate on it.
  * `fg()` requires a static literal, so call sites inline this value rather than importing it;
@@ -19,4 +19,13 @@ var BRIDGE_TO_EXTENSION = exports.BRIDGE_TO_EXTENSION = 'to-extension';
 var BRIDGE_TO_PRODUCT = exports.BRIDGE_TO_PRODUCT = 'to-product';
 
 /** Loop-guard sentinel stamped on re-published payloads so they never ping-pong. */
-var BRIDGE_SOURCE = exports.BRIDGE_SOURCE = 'rovo-extension-bridge';
+var BRIDGE_SOURCE = exports.BRIDGE_SOURCE = 'rovo-extension-bridge';
+
+/**
+ * Control-plane message asking the product to re-send the context it last relayed.
+ *
+ * Carries no data and is not a bus payload, so it deliberately bypasses the relay allow/deny lists
+ * in `./policy` — there is nothing in it to inject. The Host answers by re-sending what it already
+ * sent once; a request can never make it relay something the policy would have dropped.
+ */
+var BRIDGE_CONTROL_REQUEST_CONTEXT = exports.BRIDGE_CONTROL_REQUEST_CONTEXT = 'request-context';

package/dist/cjs/common/utils/extension-context-bridge/transport.js

@@ -4,7 +4,7 @@ var _interopRequireDefault = require("@babel/runtime/helpers/interopRequireDefau
 Object.defineProperty(exports, "__esModule", {
   value: true
 });
-exports.isBridgeMessage = exports.createWindowTransport = void 0;
+exports.isBridgeMessage = exports.isBridgeControlMessage = exports.createWindowTransport = void 0;
 var _typeof2 = _interopRequireDefault(require("@babel/runtime/helpers/typeof"));
 var _bindEventListener = require("bind-event-listener");
 var _constants = require("./constants");
@@ -13,6 +13,12 @@ var _constants = require("./constants");
  * `set-message-context`'s `setContext`) are resolved to values by `./registry` first.
  */
 
+/**
+ * Control-plane message. Distinguished from `BridgeMessage` by carrying `control` instead of
+ * `payload`, so a control message can never be mistaken for relayed context: the guards are
+ * mutually exclusive on the presence of those fields.
+ */
+
 /**
  * Transport abstraction so Host/Client work over any carrier: same-window `postMessage` on the
  * product side, iframe/side-panel `postMessage` in the chat iframe. Carries `BridgeMessage` only;
@@ -22,6 +28,12 @@ var _constants = require("./constants");
 var isBridgeMessage = exports.isBridgeMessage = function isBridgeMessage(value) {
   return (0, _typeof2.default)(value) === 'object' && value !== null && value[_constants.BRIDGE_MESSAGE_MARKER] === true && typeof value.direction === 'string' && (0, _typeof2.default)(value.payload) === 'object' && value.payload !== null;
 };
+var isBridgeControlMessage = exports.isBridgeControlMessage = function isBridgeControlMessage(value) {
+  return (0, _typeof2.default)(value) === 'object' && value !== null && value[_constants.BRIDGE_MESSAGE_MARKER] === true && typeof value.direction === 'string' && value.control === _constants.BRIDGE_CONTROL_REQUEST_CONTEXT &&
+  // Mutually exclusive with `isBridgeMessage`: a control message carries no payload to relay, so a
+  // message bearing both is treated as a payload and held to the relay policy.
+  value.payload === undefined;
+};
 
 /** `postMessage`-based transport. Callers override `targetWindow`/`self` for the iframe side. */
 var createWindowTransport = exports.createWindowTransport = function createWindowTransport(_ref) {
@@ -47,7 +59,7 @@ var createWindowTransport = exports.createWindowTransport = function createWindo
           if (event.origin !== acceptOrigin) {
             return;
           }
-          if (isBridgeMessage(event.data)) {
+          if (isBridgeMessage(event.data) || isBridgeControlMessage(event.data)) {
             handler(event.data);
           }
         }

package/dist/cjs/common/utils/params/constants.js

@@ -5,4 +5,4 @@ Object.defineProperty(exports, "__esModule", {
 });
 exports.ROVO_VALID_PARAMS = exports.ROVO_PARAM_PREFIX = void 0;
 var ROVO_PARAM_PREFIX = exports.ROVO_PARAM_PREFIX = 'rovoChat';
-var ROVO_VALID_PARAMS = exports.ROVO_VALID_PARAMS = ['pathway', 'agentId', 'conversationId', 'prompt', 'cloudId', 'triggerOpen', 'insertPrompt', 'stagingAreaOpen', 'messageIdSelectedForPreview', 'invocationIdSelectedForPreview', 'promptLibraryOpen', 'openChatMode', 'rovoJourneyId'];
+var ROVO_VALID_PARAMS = exports.ROVO_VALID_PARAMS = ['pathway', 'agentId', 'conversationId', 'prompt', 'cloudId', 'triggerOpen', 'insertPrompt', 'stagingAreaOpen', 'messageIdSelectedForPreview', 'invocationIdSelectedForPreview', 'promptLibraryOpen', 'openChatMode', 'rovoJourneyId', 'searchQuery'];

package/dist/es2019/common/utils/extension-context-bridge/ExtensionContextBridgeClient.js

@@ -4,7 +4,7 @@ import { usePublish, useSubscribeAll } from '../../../main';
 import { BRIDGE_MESSAGE_MARKER, BRIDGE_SOURCE, BRIDGE_TO_EXTENSION, BRIDGE_TO_PRODUCT } from './constants';
 import { shouldRelayToProduct } from './policy';
 import { deserializePayload, serializePayload } from './registry';
-import { createWindowTransport } from './transport';
+import { createWindowTransport, isBridgeControlMessage } from './transport';
 
 /** Selection shape preserved across editor focus loss. */
 
@@ -85,6 +85,10 @@ export const ExtensionContextBridgeClient = ({
       return;
     }
     return activeTransport.subscribe(message => {
+      // Control messages are requests to the product, never context for the chat.
+      if (isBridgeControlMessage(message)) {
+        return;
+      }
       if (message.direction !== BRIDGE_TO_EXTENSION) {
         return;
       }

package/dist/es2019/common/utils/extension-context-bridge/ExtensionContextBridgeHost.js

@@ -1,10 +1,10 @@
-import { useMemo } from 'react';
+import { useEffect, useMemo, useRef } from 'react';
 import { fg } from '@atlaskit/platform-feature-flags/fg';
 import { useSubscribeAll } from '../../../main';
-import { BRIDGE_MESSAGE_MARKER, BRIDGE_SOURCE, BRIDGE_TO_EXTENSION } from './constants';
+import { BRIDGE_CONTROL_REQUEST_CONTEXT, BRIDGE_MESSAGE_MARKER, BRIDGE_SOURCE, BRIDGE_TO_EXTENSION, BRIDGE_TO_PRODUCT } from './constants';
 import { getInboundDecision } from './policy';
 import { serializePayload } from './registry';
-import { createWindowTransport } from './transport';
+import { createWindowTransport, isBridgeControlMessage } from './transport';
 /**
  * Stamps the page id onto `editor-context-payload` when the product left it unpopulated, since the
  * extension chat cannot derive its own `contentId` from `window.location` (that's the side panel, not
@@ -24,6 +24,22 @@ const stampProductContentId = (serialized, targetContentId) => {
     data.contentMauiId = targetContentId;
   }
 };
+
+/**
+ * Identity of a context *slot*. `set-message-context` is keyed by `contextKey` because a product
+ * publishes several independent contexts, each superseding only its own previous value; everything
+ * else is keyed by payload type, of which there is one live instance at a time.
+ */
+const getContextSlotKey = payload => {
+  if (payload.type === 'set-message-context') {
+    const data = payload.data;
+    const contextKey = typeof data === 'object' && data !== null && 'contextKey' in data ? data.contextKey : undefined;
+    if (typeof contextKey === 'string') {
+      return `${payload.type}:${contextKey}`;
+    }
+  }
+  return payload.type;
+};
 /**
  * Product-window half of the bridge. Observes the `ai-mate` bus and mirrors allowlisted context out
  * to the extension via same-window `postMessage` (see `./policy` for the allow/deny rules).
@@ -53,6 +69,43 @@ export const ExtensionContextBridgeHost = ({
       targetWindow: window
     });
   }, [active, transport]);
+
+  /**
+   * The last message relayed for each context slot, kept so a chat opened later can be caught up.
+   *
+   * Deliberately held here rather than in the extension. This is the page's own context, already in
+   * this page's memory, scoped to this document and gone when it unloads — so answering a request
+   * creates no copy that outlives the page, and a chat that is never opened is never sent anything.
+   */
+  const lastRelayedRef = useRef(new Map());
+
+  // Answers `request-context` from the chat, which cannot observe context published before it
+  // mounted. Products such as Jira publish once per navigation, so without this a chat opened after
+  // the page settled would describe the wrong view — or none at all.
+  useEffect(() => {
+    if (!activeTransport) {
+      return;
+    }
+    return activeTransport.subscribe(message => {
+      if (!isBridgeControlMessage(message) || message.direction !== BRIDGE_TO_PRODUCT) {
+        return;
+      }
+      if (message.control !== BRIDGE_CONTROL_REQUEST_CONTEXT) {
+        return;
+      }
+      // Re-checked here, not just at relay time: entitlement can change while the page is open.
+      if (isAiEnabled === false) {
+        return;
+      }
+      lastRelayedRef.current.forEach(relayed => {
+        try {
+          activeTransport.send(relayed);
+        } catch {
+          // Never let bridging break the host page.
+        }
+      });
+    });
+  }, [activeTransport, isAiEnabled]);
   useSubscribeAll(payload => {
     if (!activeTransport) {
       return;
@@ -75,12 +128,22 @@ export const ExtensionContextBridgeHost = ({
       return;
     }
     stampProductContentId(serialized, getContentId === null || getContentId === void 0 ? void 0 : getContentId());
+    const message = {
+      [BRIDGE_MESSAGE_MARKER]: true,
+      direction: BRIDGE_TO_EXTENSION,
+      payload: serialized
+    };
+    // Keyed by context slot, not by message, so a re-publish replaces rather than accumulates.
+    // A cleared context is recorded too: replaying it clears the chat rather than resurrecting
+    // context the page no longer shows.
+    //
+    // Publisher contract: in an SPA this component outlives any single route, so a slot stays
+    // filled until its publisher says otherwise. Publishers must clear on unmount (publish with
+    // `setContext` returning undefined) or a later route could be answered with a previous
+    // view's context. Every Jira view-context publisher does this today.
+    lastRelayedRef.current.set(getContextSlotKey(serialized), message);
     try {
-      activeTransport.send({
-        [BRIDGE_MESSAGE_MARKER]: true,
-        direction: BRIDGE_TO_EXTENSION,
-        payload: serialized
-      });
+      activeTransport.send(message);
     } catch {
       // Never let bridging break the host page.
     }

package/dist/es2019/common/utils/extension-context-bridge/constants.js

@@ -13,4 +13,13 @@ export const BRIDGE_TO_EXTENSION = 'to-extension';
 export const BRIDGE_TO_PRODUCT = 'to-product';
 
 /** Loop-guard sentinel stamped on re-published payloads so they never ping-pong. */
-export const BRIDGE_SOURCE = 'rovo-extension-bridge';
+export const BRIDGE_SOURCE = 'rovo-extension-bridge';
+
+/**
+ * Control-plane message asking the product to re-send the context it last relayed.
+ *
+ * Carries no data and is not a bus payload, so it deliberately bypasses the relay allow/deny lists
+ * in `./policy` — there is nothing in it to inject. The Host answers by re-sending what it already
+ * sent once; a request can never make it relay something the policy would have dropped.
+ */
+export const BRIDGE_CONTROL_REQUEST_CONTEXT = 'request-context';

package/dist/es2019/common/utils/extension-context-bridge/transport.js

@@ -1,11 +1,17 @@
 import { bind } from 'bind-event-listener';
-import { BRIDGE_MESSAGE_MARKER } from './constants';
+import { BRIDGE_CONTROL_REQUEST_CONTEXT, BRIDGE_MESSAGE_MARKER } from './constants';
 
 /**
  * A `rovo-triggers` payload reduced to a structured-clone-safe shape. Functions (e.g.
  * `set-message-context`'s `setContext`) are resolved to values by `./registry` first.
  */
 
+/**
+ * Control-plane message. Distinguished from `BridgeMessage` by carrying `control` instead of
+ * `payload`, so a control message can never be mistaken for relayed context: the guards are
+ * mutually exclusive on the presence of those fields.
+ */
+
 /**
  * Transport abstraction so Host/Client work over any carrier: same-window `postMessage` on the
  * product side, iframe/side-panel `postMessage` in the chat iframe. Carries `BridgeMessage` only;
@@ -13,6 +19,10 @@ import { BRIDGE_MESSAGE_MARKER } from './constants';
  */
 
 export const isBridgeMessage = value => typeof value === 'object' && value !== null && value[BRIDGE_MESSAGE_MARKER] === true && typeof value.direction === 'string' && typeof value.payload === 'object' && value.payload !== null;
+export const isBridgeControlMessage = value => typeof value === 'object' && value !== null && value[BRIDGE_MESSAGE_MARKER] === true && typeof value.direction === 'string' && value.control === BRIDGE_CONTROL_REQUEST_CONTEXT &&
+// Mutually exclusive with `isBridgeMessage`: a control message carries no payload to relay, so a
+// message bearing both is treated as a payload and held to the relay policy.
+value.payload === undefined;
 
 /** `postMessage`-based transport. Callers override `targetWindow`/`self` for the iframe side. */
 export const createWindowTransport = ({
@@ -35,7 +45,7 @@ export const createWindowTransport = ({
         if (event.origin !== acceptOrigin) {
           return;
         }
-        if (isBridgeMessage(event.data)) {
+        if (isBridgeMessage(event.data) || isBridgeControlMessage(event.data)) {
           handler(event.data);
         }
       }

package/dist/es2019/common/utils/params/constants.js

@@ -1,2 +1,2 @@
 export const ROVO_PARAM_PREFIX = 'rovoChat';
-export const ROVO_VALID_PARAMS = ['pathway', 'agentId', 'conversationId', 'prompt', 'cloudId', 'triggerOpen', 'insertPrompt', 'stagingAreaOpen', 'messageIdSelectedForPreview', 'invocationIdSelectedForPreview', 'promptLibraryOpen', 'openChatMode', 'rovoJourneyId'];
+export const ROVO_VALID_PARAMS = ['pathway', 'agentId', 'conversationId', 'prompt', 'cloudId', 'triggerOpen', 'insertPrompt', 'stagingAreaOpen', 'messageIdSelectedForPreview', 'invocationIdSelectedForPreview', 'promptLibraryOpen', 'openChatMode', 'rovoJourneyId', 'searchQuery'];

package/dist/esm/common/utils/extension-context-bridge/ExtensionContextBridgeClient.js

@@ -7,7 +7,7 @@ import { usePublish, useSubscribeAll } from '../../../main';
 import { BRIDGE_MESSAGE_MARKER, BRIDGE_SOURCE, BRIDGE_TO_EXTENSION, BRIDGE_TO_PRODUCT } from './constants';
 import { shouldRelayToProduct } from './policy';
 import { deserializePayload, serializePayload } from './registry';
-import { createWindowTransport } from './transport';
+import { createWindowTransport, isBridgeControlMessage } from './transport';
 
 /** Selection shape preserved across editor focus loss. */
 
@@ -87,6 +87,10 @@ export var ExtensionContextBridgeClient = function ExtensionContextBridgeClient(
       return;
     }
     return activeTransport.subscribe(function (message) {
+      // Control messages are requests to the product, never context for the chat.
+      if (isBridgeControlMessage(message)) {
+        return;
+      }
       if (message.direction !== BRIDGE_TO_EXTENSION) {
         return;
       }

package/dist/esm/common/utils/extension-context-bridge/ExtensionContextBridgeHost.js

@@ -1,11 +1,12 @@
 import _defineProperty from "@babel/runtime/helpers/defineProperty";
-import { useMemo } from 'react';
+import _typeof from "@babel/runtime/helpers/typeof";
+import { useEffect, useMemo, useRef } from 'react';
 import { fg } from '@atlaskit/platform-feature-flags/fg';
 import { useSubscribeAll } from '../../../main';
-import { BRIDGE_MESSAGE_MARKER, BRIDGE_SOURCE, BRIDGE_TO_EXTENSION } from './constants';
+import { BRIDGE_CONTROL_REQUEST_CONTEXT, BRIDGE_MESSAGE_MARKER, BRIDGE_SOURCE, BRIDGE_TO_EXTENSION, BRIDGE_TO_PRODUCT } from './constants';
 import { getInboundDecision } from './policy';
 import { serializePayload } from './registry';
-import { createWindowTransport } from './transport';
+import { createWindowTransport, isBridgeControlMessage } from './transport';
 /**
  * Stamps the page id onto `editor-context-payload` when the product left it unpopulated, since the
  * extension chat cannot derive its own `contentId` from `window.location` (that's the side panel, not
@@ -25,6 +26,22 @@ var stampProductContentId = function stampProductContentId(serialized, targetCon
     data.contentMauiId = targetContentId;
   }
 };
+
+/**
+ * Identity of a context *slot*. `set-message-context` is keyed by `contextKey` because a product
+ * publishes several independent contexts, each superseding only its own previous value; everything
+ * else is keyed by payload type, of which there is one live instance at a time.
+ */
+var getContextSlotKey = function getContextSlotKey(payload) {
+  if (payload.type === 'set-message-context') {
+    var data = payload.data;
+    var contextKey = _typeof(data) === 'object' && data !== null && 'contextKey' in data ? data.contextKey : undefined;
+    if (typeof contextKey === 'string') {
+      return "".concat(payload.type, ":").concat(contextKey);
+    }
+  }
+  return payload.type;
+};
 /**
  * Product-window half of the bridge. Observes the `ai-mate` bus and mirrors allowlisted context out
  * to the extension via same-window `postMessage` (see `./policy` for the allow/deny rules).
@@ -53,6 +70,43 @@ export var ExtensionContextBridgeHost = function ExtensionContextBridgeHost(_ref
       targetWindow: window
     });
   }, [active, transport]);
+
+  /**
+   * The last message relayed for each context slot, kept so a chat opened later can be caught up.
+   *
+   * Deliberately held here rather than in the extension. This is the page's own context, already in
+   * this page's memory, scoped to this document and gone when it unloads — so answering a request
+   * creates no copy that outlives the page, and a chat that is never opened is never sent anything.
+   */
+  var lastRelayedRef = useRef(new Map());
+
+  // Answers `request-context` from the chat, which cannot observe context published before it
+  // mounted. Products such as Jira publish once per navigation, so without this a chat opened after
+  // the page settled would describe the wrong view — or none at all.
+  useEffect(function () {
+    if (!activeTransport) {
+      return;
+    }
+    return activeTransport.subscribe(function (message) {
+      if (!isBridgeControlMessage(message) || message.direction !== BRIDGE_TO_PRODUCT) {
+        return;
+      }
+      if (message.control !== BRIDGE_CONTROL_REQUEST_CONTEXT) {
+        return;
+      }
+      // Re-checked here, not just at relay time: entitlement can change while the page is open.
+      if (isAiEnabled === false) {
+        return;
+      }
+      lastRelayedRef.current.forEach(function (relayed) {
+        try {
+          activeTransport.send(relayed);
+        } catch (_unused) {
+          // Never let bridging break the host page.
+        }
+      });
+    });
+  }, [activeTransport, isAiEnabled]);
   useSubscribeAll(function (payload) {
     if (!activeTransport) {
       return;
@@ -75,9 +129,19 @@ export var ExtensionContextBridgeHost = function ExtensionContextBridgeHost(_ref
       return;
     }
     stampProductContentId(serialized, getContentId === null || getContentId === void 0 ? void 0 : getContentId());
+    var message = _defineProperty(_defineProperty(_defineProperty({}, BRIDGE_MESSAGE_MARKER, true), "direction", BRIDGE_TO_EXTENSION), "payload", serialized);
+    // Keyed by context slot, not by message, so a re-publish replaces rather than accumulates.
+    // A cleared context is recorded too: replaying it clears the chat rather than resurrecting
+    // context the page no longer shows.
+    //
+    // Publisher contract: in an SPA this component outlives any single route, so a slot stays
+    // filled until its publisher says otherwise. Publishers must clear on unmount (publish with
+    // `setContext` returning undefined) or a later route could be answered with a previous
+    // view's context. Every Jira view-context publisher does this today.
+    lastRelayedRef.current.set(getContextSlotKey(serialized), message);
     try {
-      activeTransport.send(_defineProperty(_defineProperty(_defineProperty({}, BRIDGE_MESSAGE_MARKER, true), "direction", BRIDGE_TO_EXTENSION), "payload", serialized));
-    } catch (_unused) {
+      activeTransport.send(message);
+    } catch (_unused2) {
       // Never let bridging break the host page.
     }
   });

package/dist/esm/common/utils/extension-context-bridge/constants.js

@@ -13,4 +13,13 @@ export var BRIDGE_TO_EXTENSION = 'to-extension';
 export var BRIDGE_TO_PRODUCT = 'to-product';
 
 /** Loop-guard sentinel stamped on re-published payloads so they never ping-pong. */
-export var BRIDGE_SOURCE = 'rovo-extension-bridge';
+export var BRIDGE_SOURCE = 'rovo-extension-bridge';
+
+/**
+ * Control-plane message asking the product to re-send the context it last relayed.
+ *
+ * Carries no data and is not a bus payload, so it deliberately bypasses the relay allow/deny lists
+ * in `./policy` — there is nothing in it to inject. The Host answers by re-sending what it already
+ * sent once; a request can never make it relay something the policy would have dropped.
+ */
+export var BRIDGE_CONTROL_REQUEST_CONTEXT = 'request-context';

package/dist/esm/common/utils/extension-context-bridge/transport.js

@@ -1,12 +1,18 @@
 import _typeof from "@babel/runtime/helpers/typeof";
 import { bind } from 'bind-event-listener';
-import { BRIDGE_MESSAGE_MARKER } from './constants';
+import { BRIDGE_CONTROL_REQUEST_CONTEXT, BRIDGE_MESSAGE_MARKER } from './constants';
 
 /**
  * A `rovo-triggers` payload reduced to a structured-clone-safe shape. Functions (e.g.
  * `set-message-context`'s `setContext`) are resolved to values by `./registry` first.
  */
 
+/**
+ * Control-plane message. Distinguished from `BridgeMessage` by carrying `control` instead of
+ * `payload`, so a control message can never be mistaken for relayed context: the guards are
+ * mutually exclusive on the presence of those fields.
+ */
+
 /**
  * Transport abstraction so Host/Client work over any carrier: same-window `postMessage` on the
  * product side, iframe/side-panel `postMessage` in the chat iframe. Carries `BridgeMessage` only;
@@ -16,6 +22,12 @@ import { BRIDGE_MESSAGE_MARKER } from './constants';
 export var isBridgeMessage = function isBridgeMessage(value) {
   return _typeof(value) === 'object' && value !== null && value[BRIDGE_MESSAGE_MARKER] === true && typeof value.direction === 'string' && _typeof(value.payload) === 'object' && value.payload !== null;
 };
+export var isBridgeControlMessage = function isBridgeControlMessage(value) {
+  return _typeof(value) === 'object' && value !== null && value[BRIDGE_MESSAGE_MARKER] === true && typeof value.direction === 'string' && value.control === BRIDGE_CONTROL_REQUEST_CONTEXT &&
+  // Mutually exclusive with `isBridgeMessage`: a control message carries no payload to relay, so a
+  // message bearing both is treated as a payload and held to the relay policy.
+  value.payload === undefined;
+};
 
 /** `postMessage`-based transport. Callers override `targetWindow`/`self` for the iframe side. */
 export var createWindowTransport = function createWindowTransport(_ref) {
@@ -41,7 +53,7 @@ export var createWindowTransport = function createWindowTransport(_ref) {
           if (event.origin !== acceptOrigin) {
             return;
           }
-          if (isBridgeMessage(event.data)) {
+          if (isBridgeMessage(event.data) || isBridgeControlMessage(event.data)) {
             handler(event.data);
           }
         }

package/dist/esm/common/utils/params/constants.js

@@ -1,2 +1,2 @@
 export var ROVO_PARAM_PREFIX = 'rovoChat';
-export var ROVO_VALID_PARAMS = ['pathway', 'agentId', 'conversationId', 'prompt', 'cloudId', 'triggerOpen', 'insertPrompt', 'stagingAreaOpen', 'messageIdSelectedForPreview', 'invocationIdSelectedForPreview', 'promptLibraryOpen', 'openChatMode', 'rovoJourneyId'];
+export var ROVO_VALID_PARAMS = ['pathway', 'agentId', 'conversationId', 'prompt', 'cloudId', 'triggerOpen', 'insertPrompt', 'stagingAreaOpen', 'messageIdSelectedForPreview', 'invocationIdSelectedForPreview', 'promptLibraryOpen', 'openChatMode', 'rovoJourneyId', 'searchQuery'];

package/dist/types/common/utils/extension-context-bridge/constants.d.ts

@@ -11,3 +11,11 @@ export declare const BRIDGE_TO_EXTENSION: 'to-extension';
 export declare const BRIDGE_TO_PRODUCT: 'to-product';
 /** Loop-guard sentinel stamped on re-published payloads so they never ping-pong. */
 export declare const BRIDGE_SOURCE: 'rovo-extension-bridge';
+/**
+ * Control-plane message asking the product to re-send the context it last relayed.
+ *
+ * Carries no data and is not a bus payload, so it deliberately bypasses the relay allow/deny lists
+ * in `./policy` — there is nothing in it to inject. The Host answers by re-sending what it already
+ * sent once; a request can never make it relay something the policy would have dropped.
+ */
+export declare const BRIDGE_CONTROL_REQUEST_CONTEXT: 'request-context';

package/dist/types/common/utils/extension-context-bridge/transport.d.ts

@@ -1,5 +1,5 @@
 import { type Payload } from '../../../types';
-import { BRIDGE_MESSAGE_MARKER } from './constants';
+import { BRIDGE_CONTROL_REQUEST_CONTEXT, BRIDGE_MESSAGE_MARKER } from './constants';
 import type { BRIDGE_TO_EXTENSION, BRIDGE_TO_PRODUCT } from './constants';
 type BridgeDirection = typeof BRIDGE_TO_EXTENSION | typeof BRIDGE_TO_PRODUCT;
 /**
@@ -18,17 +18,28 @@ export type BridgeMessage = {
     direction: BridgeDirection;
     payload: SerializedPayload;
 };
+/**
+ * Control-plane message. Distinguished from `BridgeMessage` by carrying `control` instead of
+ * `payload`, so a control message can never be mistaken for relayed context: the guards are
+ * mutually exclusive on the presence of those fields.
+ */
+export type BridgeControlMessage = {
+    [BRIDGE_MESSAGE_MARKER]: true;
+    direction: BridgeDirection;
+    control: typeof BRIDGE_CONTROL_REQUEST_CONTEXT;
+};
 /**
  * Transport abstraction so Host/Client work over any carrier: same-window `postMessage` on the
  * product side, iframe/side-panel `postMessage` in the chat iframe. Carries `BridgeMessage` only;
  * `rovo-content-bridge-api` commands travel separately, relayed verbatim by the extension.
  */
 export type Transport = {
-    send: (message: BridgeMessage) => void;
+    send: (message: BridgeMessage | BridgeControlMessage) => void;
     /** Returns an unsubscribe function. */
-    subscribe: (handler: (message: BridgeMessage) => void) => () => void;
+    subscribe: (handler: (message: BridgeMessage | BridgeControlMessage) => void) => () => void;
 };
 export declare const isBridgeMessage: (value: unknown) => value is BridgeMessage;
+export declare const isBridgeControlMessage: (value: unknown) => value is BridgeControlMessage;
 /** `postMessage`-based transport. Callers override `targetWindow`/`self` for the iframe side. */
 export declare const createWindowTransport: ({ targetWindow, self: selfWindow, targetOrigin, acceptOrigin, }: {
     targetWindow: Window;

package/dist/types/common/utils/params/types.d.ts

@@ -15,6 +15,7 @@ export interface BaseRovoChatParams {
     promptLibraryOpen: boolean;
     openChatMode: RovoChatOpenMode;
     rovoJourneyId: string;
+    searchQuery: string;
 }
 export type ValidPrefix = 'rovoChat';
 export type ValidParam = keyof BaseRovoChatParams;

package/dist/types/types.d.ts

@@ -513,6 +513,15 @@ export type UpdateTransitionRovoPayload = {
         fromStatusName: string;
         fromStatusCategory: StatusCategory;
     }[];
+    existingName?: string;
+    existingToStatusId?: StatusId;
+    existingToStatusName?: string;
+    existingToStatusCategory?: StatusCategory;
+    existingLinks?: {
+        fromStatusId: StatusId;
+        fromStatusName: string;
+        fromStatusCategory: StatusCategory;
+    }[];
 };
 export type DeleteTransitionRovoPayloadOld = {
     transitionId: TransitionId;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@atlaskit/rovo-triggers",
-	"version": "10.30.0",
+	"version": "10.33.0",
 	"description": "Provides various trigger events to drive Rovo Chat functionality, such as a publish-subscribe and URL parameter hooks",
 	"author": "Atlassian Pty Ltd",
 	"publishConfig": {
@@ -44,7 +44,7 @@
 		"@atlaskit/primitives": "^22.5.0",
 		"@atlaskit/ssr": "workspace:^",
 		"@atlassian/a11y-jest-testing": "^0.17.0",
-		"@atlassian/conversation-assistant-service-api": "^17.7.0",
+		"@atlassian/conversation-assistant-service-api": "^17.10.0",
 		"@atlassian/feature-flags-test-utils": "^1.3.0",
 		"@atlassian/testing-library": "^0.11.0",
 		"@atlassian/workbench": "workspace:*",