Add abstract handling

Author: OEvgeny

__tests__/html2/part-grouping/status.copilot.dark.html.snap-12.png

@@ -146,7 +146,7 @@
         }
       };
 
-      const withModifiers = (activity, { position, status, abstract, howToStatus }) => ({
+      const withModifiers = (activity, { position, status, abstract, howToStatus, howToAbstract }) => ({
         ...activity,
         entities: activity.entities.map(entity => ({
           ...entity,
@@ -155,7 +155,8 @@
           creativeWorkStatus: status,
           isPartOf: {
             ...entity.isPartOf,
-            ...(typeof howToStatus !== 'undefined' ? { creativeWorkStatus: howToStatus } : {})
+            ...(typeof howToStatus !== 'undefined' ? { creativeWorkStatus: howToStatus } : {}),
+            ...(typeof howToAbstract !== 'undefined' ? { abstract: howToAbstract } : {})
           }
         }))
       });
@@ -260,15 +261,15 @@
 
       // Test Case 8: HowTo-level status takes precedence
       // When: setting the HowTo entity's creativeWorkStatus to 'Incomplete' while messages have 'Published'
-      directLine.emulateIncomingActivity(withModifiers(activities.at(0), { status: 'Published', abstract: 'one done', howToStatus: 'Incomplete' }));
+      directLine.emulateIncomingActivity(withModifiers(activities.at(0), { status: 'Published', abstract: 'one done', howToStatus: 'Incomplete', howToAbstract: 'HowTo in progress' }));
 
       // Then: the group header should show 'Incomplete' because the HowTo status takes precedence over derived message status
       await pageConditions.numActivitiesShown(6);
       await host.snapshot('local');
 
       // Test Case 9: HowTo-level status set to 'Published' overrides message-derived status
       // When: a message is 'Incomplete' but the HowTo entity is explicitly 'Published'
-      directLine.emulateIncomingActivity(withModifiers(activities.at(3), { status: 'Incomplete', abstract: 'four in progress again', howToStatus: 'Published' }));
+      directLine.emulateIncomingActivity(withModifiers(activities.at(3), { status: 'Incomplete', abstract: 'four in progress again', howToStatus: 'Published', howToAbstract: 'HowTo completed' }));
 
       // Then: the group header should show 'Published' from the HowTo, not 'Incomplete' from the message
       await pageConditions.numActivitiesShown(6);

__tests__/html2/part-grouping/status.copilot.dark.html.snap-13.png

@@ -181,10 +181,13 @@ function PartGroupingActivity(props: PartGroupingActivityProps) {
 
   const topAlignedCallout = isZeroOrPositive(bubbleNubOffset);
 
-  // The HowTo entity (the group root) may carry an explicit `creativeWorkStatus`.
+  // The HowTo entity (the group root) may carry an explicit `creativeWorkStatus` and `abstract`.
   // When present, it takes precedence over status derived from individual messages.
-  const howToStatus = useMemo(
-    () => messages.find(message => message.isPartOf?.creativeWorkStatus)?.isPartOf?.creativeWorkStatus,
+  const [howToStatus, howToAbstract] = useMemo(
+    () => [
+      messages.find(message => message.isPartOf?.creativeWorkStatus)?.isPartOf?.creativeWorkStatus,
+      messages.find(message => message.isPartOf?.creativeWorkStatus)?.isPartOf?.abstract
+    ],
     [messages]
   );
 
@@ -218,13 +221,13 @@ function PartGroupingActivity(props: PartGroupingActivityProps) {
           />
         )}
         <CollapsibleGroupingTitle>
-          {currentGroupStatus === 'Incomplete'
-            ? currentMessage?.abstract || localize('COLLAPSIBLE_GROUPING_TITLE')
+          {currentGroupStatus === 'Incomplete' || howToAbstract
+            ? howToAbstract || currentMessage?.abstract || localize('COLLAPSIBLE_GROUPING_TITLE')
             : localize('COLLAPSIBLE_GROUPING_TITLE')}
         </CollapsibleGroupingTitle>
       </Fragment>
     ),
-    [classNames, currentGroupStatus, currentMessage?.abstract, defaultWorkStatus, howToStatus, localize]
+    [classNames, currentGroupStatus, currentMessage?.abstract, defaultWorkStatus, howToAbstract, howToStatus, localize]
   );
 
   return (