Collaboration: Rename remove_updates_up_to_cursor to remove_updates_through_cursor

The previous name was ambiguous — it suggested exclusive semantics,
but the query uses inclusive deletion (id <= %d). "through" clearly
communicates the inclusive behavior without needing to read the docblock.

Author: josephfusco

src/wp-includes/collaboration/class-wp-collaboration-table-storage.php

@@ -251,7 +251,7 @@ public function get_updates_after_cursor( string $room, int $cursor ): array {
 	 * @param int    $cursor Remove updates up to and including this cursor.
 	 * @return bool True on success, false on failure.
 	 */
-	public function remove_updates_up_to_cursor( string $room, int $cursor ): bool {
+	public function remove_updates_through_cursor( string $room, int $cursor ): bool {
 		global $wpdb;
 
 		// Uses a single atomic DELETE query, avoiding the race-prone

src/wp-includes/collaboration/class-wp-http-polling-collaboration-server.php

@@ -507,7 +507,7 @@ private function process_collaboration_update( string $room, string $client_id,
 						return $insert_result;
 					}
 
-					if ( ! $this->storage->remove_updates_up_to_cursor( $room, $cursor ) ) {
+					if ( ! $this->storage->remove_updates_through_cursor( $room, $cursor ) ) {
 						global $wpdb;
 						$error_data = array( 'status' => 500 );
 						if ( defined( 'WP_DEBUG' ) && WP_DEBUG ) {

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

@@ -1838,7 +1838,7 @@ public function test_collaboration_awareness_rows_do_not_affect_cursor(): void {
 	}
 
 	/**
-	 * Compaction (remove_updates_up_to_cursor) should not delete awareness rows.
+	 * Compaction (remove_updates_through_cursor) should not delete awareness rows.
 	 *
 	 * @ticket 64696
 	 */