refactoring of system messages

tests/Feature/DashboardTest.php

@@ -104,9 +104,9 @@ test('dashboard groups and filters unread entities correctly based on cursor', f
         ->where('unreadEntities.0.name', 'Testing Dynamic')
         ->where('unreadEntities.0.unread_count', 1)
         ->has('unreadEntities.0.context_activities', 1) // Should have old message as context
-        ->where('unreadEntities.0.context_activities.0.description', 'Old message context')
+        ->where('unreadEntities.0.context_activities.0.content', 'Old message context')
         ->has('unreadEntities.0.new_activities', 1) // Should have unread message
-        ->where('unreadEntities.0.new_activities.0.description', 'New unread message alert')
+        ->where('unreadEntities.0.new_activities.0.content', 'New unread message alert')
     );
 
     // Now visit the Dynamic, which clears the unread count

tests/Feature/InvitationTest.php

@@ -99,5 +99,5 @@ test('only the user with the specified email address can accept the link', funct
     // Verify system notification is added to Dynamic activity chat
     $chatMessages = $dynamic->chat->messages;
     expect($chatMessages)->not->toBeEmpty();
-    expect($chatMessages->last()->content)->toBe("System: {$invitee->name} joined the Dynamic as a EDITOR after accepting an invitation.");
+    expect($chatMessages->last()->content)->toBe("{$invitee->name} joined the Dynamic as a EDITOR");
 });