Collaboration: Replace leftover sync terminology in comments

Replaces "sync update" and "sync data" with "collaboration" or
"update" in comments and test assertion messages across source,
tests, and benchmark scripts. Code and method names are unchanged.

Author: josephfusco

src/wp-includes/collaboration.php

@@ -41,7 +41,7 @@ function wp_collaboration_inject_setting() {
 /**
  * Deletes stale collaboration data from the collaboration table.
  *
- * Removes sync-update rows older than 7 days and awareness rows older than
+ * Removes collaboration rows older than 7 days and awareness rows older than
  * 60 seconds. Rows left behind by abandoned collaborative editing sessions
  * are cleaned up to prevent unbounded table growth.
  *
@@ -54,7 +54,7 @@ function wp_delete_old_collaboration_data() {
 
 	global $wpdb;
 
-	// Clean up sync update rows older than 7 days.
+	// Clean up collaboration rows older than 7 days.
 	$wpdb->query(
 		$wpdb->prepare(
 			"DELETE FROM {$wpdb->collaboration} WHERE created_at < %s",

tests/phpunit/tests/rest-api/rest-collaboration-server.php

@@ -1345,13 +1345,13 @@ public function test_collaboration_awareness_rows_do_not_affect_cursor(): void {
 			)
 		);
 
-		// With no sync updates, cursor should be 0.
+		// With no updates, cursor should be 0.
 		$data1 = $response1->get_data();
 		$this->assertSame( 0, $data1['rooms'][0]['end_cursor'], 'Awareness rows should not affect the cursor.' );
 		$this->assertSame( 0, $data1['rooms'][0]['total_updates'], 'Awareness rows should not count as updates.' );
 		$this->assertEmpty( $data1['rooms'][0]['updates'], 'Awareness rows should not appear as updates.' );
 
-		// Now add a sync update.
+		// Now add an update.
 		$update    = array(
 			'type' => 'update',
 			'data' => 'dGVzdA==',
@@ -1363,7 +1363,7 @@ public function test_collaboration_awareness_rows_do_not_affect_cursor(): void {
 		);
 
 		$data2 = $response2->get_data();
-		$this->assertSame( 1, $data2['rooms'][0]['total_updates'], 'Only sync updates should count toward total.' );
+		$this->assertSame( 1, $data2['rooms'][0]['total_updates'], 'Only updates should count toward total.' );
 	}
 
 	/**
@@ -1502,15 +1502,15 @@ public function test_cron_cleanup_deletes_expired_awareness_rows(): void {
 			array( '%s', '%d', '%d', '%s', '%s' )
 		);
 
-		// Insert a recent sync update row (should survive).
+		// Insert a recent collaboration row (should survive).
 		$this->insert_collaboration_row( HOUR_IN_SECONDS );
 
-		$this->assertSame( 1, $this->get_collaboration_row_count(), 'Collaboration table should have 1 sync update row.' );
+		$this->assertSame( 1, $this->get_collaboration_row_count(), 'Collaboration table should have 1 row.' );
 		$this->assertSame( 1, $this->get_awareness_row_count(), 'Awareness table should have 1 awareness row.' );
 
 		wp_delete_old_collaboration_data();
 
-		$this->assertSame( 1, $this->get_collaboration_row_count(), 'Only the recent sync update row should survive cron cleanup.' );
+		$this->assertSame( 1, $this->get_collaboration_row_count(), 'Only the recent collaboration row should survive cron cleanup.' );
 		$this->assertSame( 0, $this->get_awareness_row_count(), 'Expired awareness row should be deleted after cron cleanup.' );
 	}
 

tools/local-env/scripts/collaboration-perf/DO_NOT_RELEASE_prove-beta3-post_meta_data_loss.php

@@ -1,6 +1,6 @@
 <?php
 /**
- * Proves that post meta compaction loses sync data.
+ * Proves that post meta compaction loses collaboration data.
  *
  * Compaction triggers at 50 updates, keeping the newest 20% (10) and
  * discarding the oldest 80% (40).
@@ -32,7 +32,7 @@
 $keep    = $total - $discard;       // 20% — the newest updates that should remain.
 
 // =====================================================================
-// Setup: 50 sync updates exist in both backends.
+// Setup: 50 updates exist in both backends.
 // =====================================================================
 
 // Table backend.
@@ -99,7 +99,7 @@
 //       }
 //   }
 //
-// Between the delete and the first re-insert, the sync history is empty.
+// Between the delete and the first re-insert, the update history is empty.
 // =====================================================================
 
 // Step 1 of 2: delete ALL updates (this is the production code path).