Move the site meta filters behind @require-wp-5.1

Multisite gained the site meta table in WordPress 5.1, and WP_Site_Query
gained the meta_* parameters that read it in the same release, so
`wp site meta add` fails on 4.9 with "The table is not installed" and the
filters have nothing to match against. They get a scenario of their own,
tagged for the version that has them, and the docblock says so.

The rest stays where it is: 'lang_id', 'lang__in' and 'lang__not_in' date
from 4.8 and everything else here from 4.6, so only the meta arguments
needed separating.

Also covers '--last_updated' against an OR date query, not just
'--registered', so both filters are pinned against the relation leaking.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014SSZzqMJRDTiLiDxQEPYcL

Author: claude

README.md

@@ -5538,7 +5538,8 @@ wp site list [--network=<id>|site_id|network_id] [--<field>=<value>] [--site__in
 		and 'path'.
 
 	[--meta_key=<meta_key>]
-		Filter by this site meta key.
+		Filter by this site meta key. The site meta arguments need WordPress 5.1
+		or later, which is where multisite gained the table they read.
 
 	[--meta_value=<meta_value>]
 		Filter by this site meta value. Used together with `--meta_key`.

features/site.feature

@@ -1169,35 +1169,7 @@ Feature: Manage sites in a multisite installation
       3
       """
 
-    When I run `wp site meta add {ALPHA_ID} colour blue`
-    Then STDOUT should not be empty
-
-    When I run `wp site list --meta_key=colour --meta_value=blue --field=blog_id`
-    Then STDOUT should be:
-      """
-      {ALPHA_ID}
-      """
-
-    When I run `wp site list --meta_key=colour --meta_value=red --format=count`
-    Then STDOUT should be:
-      """
-      0
-      """
-
-    # --meta_query and --date_query are nested arrays, so they are given as JSON.
-    When I run `wp site list --meta_query='[{"key":"colour","value":"blue"}]' --field=blog_id`
-    Then STDOUT should be:
-      """
-      {ALPHA_ID}
-      """
-
-    When I run `wp site list --meta_query='[{"key":"colour","compare":"NOT EXISTS"}]' --field=blog_id`
-    Then STDOUT should be:
-      """
-      1
-      {BETA_ID}
-      """
-
+    # --date_query is a nested array, so it is given as JSON.
     When I run `wp site list --date_query='[{"column":"registered","after":"1999-01-01"}]' --format=count`
     Then STDOUT should be:
       """
@@ -1236,6 +1208,21 @@ Feature: Manage sites in a multisite installation
       0
       """
 
+    When I run `wp site list --blog_id={ALPHA_ID} --field=last_updated`
+    Then save STDOUT as {ALPHA_UPDATED}
+
+    When I run `wp site list --blog_id={ALPHA_ID} --last_updated='{ALPHA_UPDATED}' --format=count`
+    Then STDOUT should be:
+      """
+      1
+      """
+
+    When I run `wp site list --blog_id={ALPHA_ID} --date_query='{"relation":"OR","0":{"column":"last_updated","before":"1999-01-01"},"1":{"column":"last_updated","before":"1998-01-01"}}' --last_updated='{ALPHA_UPDATED}' --format=count`
+    Then STDOUT should be:
+      """
+      0
+      """
+
     When I try `wp site list --meta_query=notjson`
     Then STDERR should contain:
       """
@@ -1250,6 +1237,49 @@ Feature: Manage sites in a multisite installation
       """
     And the return code should be 1
 
+  # WP_Site_Query gained the meta_* parameters, and multisite gained the site meta
+  # table they read, in WordPress 5.1.
+  @require-wp-5.1
+  Scenario: Filter the site list by site meta
+    Given a WP multisite install
+
+    When I run `wp site create --slug=alpha --porcelain`
+    Then STDOUT should be a number
+    And save STDOUT as {ALPHA_ID}
+
+    When I run `wp site create --slug=beta --porcelain`
+    Then STDOUT should be a number
+    And save STDOUT as {BETA_ID}
+
+    When I run `wp site meta add {ALPHA_ID} colour blue`
+    Then STDOUT should not be empty
+
+    When I run `wp site list --meta_key=colour --meta_value=blue --field=blog_id`
+    Then STDOUT should be:
+      """
+      {ALPHA_ID}
+      """
+
+    When I run `wp site list --meta_key=colour --meta_value=red --format=count`
+    Then STDOUT should be:
+      """
+      0
+      """
+
+    # --meta_query is a nested array, so it is given as JSON.
+    When I run `wp site list --meta_query='[{"key":"colour","value":"blue"}]' --field=blog_id`
+    Then STDOUT should be:
+      """
+      {ALPHA_ID}
+      """
+
+    When I run `wp site list --meta_query='[{"key":"colour","compare":"NOT EXISTS"}]' --field=blog_id`
+    Then STDOUT should be:
+      """
+      1
+      {BETA_ID}
+      """
+
   Scenario: Existing site list filters keep working against WP_Site_Query
     Given a WP multisite install
 

src/Site_Command.php

@@ -1072,7 +1072,8 @@ private function get_network( $network_id ) {
 	 * and 'path'.
 	 *
 	 * [--meta_key=<meta_key>]
-	 * : Filter by this site meta key.
+	 * : Filter by this site meta key. The site meta arguments need WordPress 5.1
+	 * or later, which is where multisite gained the table they read.
 	 *
 	 * [--meta_value=<meta_value>]
 	 * : Filter by this site meta value. Used together with `--meta_key`.
@@ -1290,7 +1291,13 @@ public function list_( $args, $assoc_args ) {
 
 			$query_args['date_query'] = empty( $given )
 				? $date_query
-				: array_merge( [ 'relation' => 'AND', $given ], $date_query );
+				: array_merge(
+					[
+						'relation' => 'AND',
+						$given,
+					],
+					$date_query
+				);
 		}
 
 		if ( isset( $assoc_args['site_user'] ) ) {