@@ -154,11 +154,11 @@ array(
 Two properties are worth stating plainly:
 
 - **No body content is ever returned.** Rows carry a title and a plain-text excerpt, generated from the content when the post has none. Reading a body is `ai/read-content-bodies`'s job, and is capped at five posts a call.
-- **Every row is filtered at execute time** by the current user's read permission, using the same inherited-parent walk `core/read-content` performs. `total` comes from the underlying query and may therefore exceed the number of rows returned. The 20-item page cap is a context limit for the model, not an access control. `edit_link` is present only when the user can edit that post.
+- **Every row is filtered at execute time** by the current user's read permission, using the same inherited-parent walk `core/content-query` performs. `total` comes from the underlying query and may therefore exceed the number of rows returned. The 20-item page cap is a context limit for the model, not an access control. `edit_link` is present only when the user can edit that post.
 
 ### `ai/read-content-bodies`
 
-The reading half of retrieval, and the largest increase in reachable content on this surface. Registered by this experiment for the same reason the search ability is: `core/read-content` belongs to the Custom Abilities experiment, and the workspace's reach must not change when a different experiment is switched off.
+The reading half of retrieval, and the largest increase in reachable content on this surface. Registered by this experiment for the same reason the search ability is: `core/content-query` belongs to the Custom Abilities experiment, and the workspace's reach must not change when a different experiment is switched off.
 
 **Input schema** (`additionalProperties` is false):
 
@@ -372,8 +372,14 @@ The filter does not have the last word on removals: the site owner's own removal
 ### `wpai_workspace_withheld_abilities`
 
 The abilities the workspace never admits, whatever their exposure and
-annotations say. Ships holding `core/get-user-info`, `core/read-users`,
-`core/read-settings` and `core/get-environment-info`.
+annotations say. Ships holding `core/get-user-info`, `core/users-query`,
+`core/read-users`, `core/read-settings` and `core/get-environment-info`.
+
+`core/users-query` and `core/read-users` are the same ability under two names:
+[#1002](https://github.com/WordPress/ai/pull/1002) renamed it and kept the old
+name as a deprecated alias. The alias is a real registration that copies the
+replacement's meta, so a change in exposure reaches both at once and both have
+to be listed. A rename upstream is a hole here until the new name is added.
 
 The effect class asks whether an ability writes or reaches outside the site. It
 cannot ask whether handing it to a model is a bad idea, and for these the answer
 
@@ -24,7 +24,7 @@
  * of a small number of posts named by ID.
  *
  * This is a sibling of {@see Search_Content}, and exists for the same reason: a
- * conversational surface needs to read the posts it finds, and `core/read-content` is
+ * conversational surface needs to read the posts it finds, and `core/content-query` is
  * registered behind the Custom Abilities experiment. Depending on that ability would
  * make this tool appear and disappear with a switch that has nothing to do with it, so
  * the reading path is registered here instead and every ability consumer — the AI
 
@@ -25,7 +25,7 @@
  * across the post types exposed to abilities via `show_in_abilities` and returns a
  * bounded list of matching posts as titles and excerpts.
  *
- * This is a sibling of {@see Content}, not a change to it: `core/read-content` is kept
+ * This is a sibling of {@see Content}, not a change to it: `core/content-query` is kept
  * byte-similar to WordPress core's copy, and its registered description states that its
  * lookups and filters are exact-match only. Rather than widen that ability, this class
  * adds search as its own ability so every ability consumer — the AI Workspace, the MCP
@@ -36,7 +36,7 @@
  *  - The result set is capped at {@see self::MAX_PER_PAGE} items. That is a context
  *    limit for the model, not an access control.
  *  - Every returned row is filtered at execute time by the requesting user's own
- *    capabilities, using the same read permission walk `core/read-content` performs,
+ *    capabilities, using the same read permission walk `core/content-query` performs,
  *    so a result set never contains an item the user could not otherwise read. The
  *    permission callback can only gate the request coarsely, because the matching
  *    rows are unknown until the query runs.
@@ -139,7 +139,7 @@ public function register(): void {
 		}
 
 		/*
-		 * Internal statuses (e.g. `inherit`) are excluded, matching `core/read-content`.
+		 * Internal statuses (e.g. `inherit`) are excluded, matching `core/content-query`.
 		 */
 		$statuses = array_values( get_post_stati( array( 'internal' => false ) ) );
 
@@ -200,10 +200,10 @@ public function check_permission( $input = array() ): bool {
 	 * {@see \WP_Ability::execute()} always runs {@see self::check_permission()} first, so
 	 * this only needs to enforce what the gate could not: every matched row is checked
 	 * against the current user's read permission before it is included, mirroring the
-	 * row filtering `core/read-content` performs in query mode.
+	 * row filtering `core/content-query` performs in query mode.
 	 *
 	 * Totals come from the underlying query and may therefore exceed the number of
-	 * returned rows, matching `core/read-content` and the REST posts controller.
+	 * returned rows, matching `core/content-query` and the REST posts controller.
 	 *
 	 * `total` exceeds the returned rows for two unrelated reasons — the rest of the
 	 * matches are on later pages, and the permission walk dropped some of this page —
 
@@ -104,7 +104,7 @@ public function register(): void {
 		/*
 		 * The reading half of retrieval. Search finds posts; this returns the bodies
 		 * of a handful of them, filtered row by row at execute time. It is registered
-		 * here rather than leaning on `core/read-content`, which belongs to the Custom
+		 * here rather than leaning on `core/content-query`, which belongs to the Custom
 		 * Abilities experiment: the workspace's reach must not change when a different
 		 * experiment is switched off.
 		 */
Original file line number	Diff line number	Diff line change
`@@ -24,7 +24,7 @@`
`24`	`24`	`* of a small number of posts named by ID.`
`25`	`25`	`*`
`26`	`26`	`* This is a sibling of {@see Search_Content}, and exists for the same reason: a`
`27`		- * conversational surface needs to read the posts it finds, and `core/read-content` is
	`27`	+ * conversational surface needs to read the posts it finds, and `core/content-query` is
`28`	`28`	`* registered behind the Custom Abilities experiment. Depending on that ability would`
`29`	`29`	`* make this tool appear and disappear with a switch that has nothing to do with it, so`
`30`	`30`	`* the reading path is registered here instead and every ability consumer — the AI`