#1002 renamed core/read-users to core/users-query and kept the old name as a
deprecated alias. Both are registered, and the withheld list named only the
old one -- so the ability it exists to hold back was reachable under the name
core now prefers.

Not reachable in practice yet: core/users-query is not public and does not
assert an admissible effect class. But the point of the list is to hold when
those change, and it was not holding.

Both names are listed, because the alias is a real registration rather than a
redirect. A rename upstream is a hole here until someone adds the new name,
which the docblock now says.

PHPStan goes with it. The composer script pinned 1G, and this branch pushed
analysis past it once develop merged in, so the documented command crashed.
2G clears it. CI never used that script -- it runs phpstan with no limit at
all -- so this is the local command catching up to what CI already did.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

#1002 renamed core/read-content to core/content-query. Nine docblock and doc
references here still pointed at the old name, which now resolves to a
deprecated alias -- accurate enough to pass review and wrong enough to send
the next reader somewhere that will be removed.

The withheld list keeps naming both sides of the users rename, and the docs
now say why: the alias is a real registration that copies the replacement's
meta, so exposure changes reach both names at once and holding back only one
holds back nothing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

#1002 renamed core/read-users to core/users-query and kept the old name as a
deprecated alias. Both are registered, and the withheld list named only the
old one -- so the ability it exists to hold back was reachable under the name
core now prefers.

Not reachable in practice yet: core/users-query is not public and does not
assert an admissible effect class. But the point of the list is to hold when
those change, and it was not holding.

Both names are listed, because the alias is a real registration rather than a
redirect. A rename upstream is a hole here until someone adds the new name,
which the docblock now says.

PHPStan goes with it. The composer script pinned 1G, and this branch pushed
analysis past it once develop merged in, so the documented command crashed.
2G clears it. CI never used that script -- it runs phpstan with no limit at
all -- so this is the local command catching up to what CI already did.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

#1002 renamed core/read-content to core/content-query. Nine docblock and doc
references here still pointed at the old name, which now resolves to a
deprecated alias -- accurate enough to pass review and wrong enough to send
the next reader somewhere that will be removed.

The withheld list keeps naming both sides of the users rename, and the docs
now say why: the alias is a real registration that copies the replacement's
meta, so exposure changes reach both names at once and holding back only one
holds back nothing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Renames the ability from `core/read-content` to `core/content-query` to
match the AI plugin (WordPress/ai#1002), and ports the plugin's lean
projection test, which checks the query arguments the ability builds
instead of counting post meta queries.

Also drops the trailing period from the hook documentation references,
which the PHPStan hook docblock rule reads as part of the file path.

…ery`.

This matches the name and label that the AI plugin uses since
WordPress/ai#1002.

Renames the ability from `core/read-content` to `core/content-query` to
match the AI plugin (WordPress/ai#1002), and ports the plugin's lean
projection test, which checks the query arguments the ability builds
instead of counting post meta queries.

Also drops the trailing period from the hook documentation references,
which the PHPStan hook docblock rule reads as part of the file path.

…ery`.

This matches the name and label that the AI plugin uses since
WordPress/ai#1002.

Renames the ability from `core/read-content` to `core/content-query` to
match the AI plugin (WordPress/ai#1002), and ports the plugin's lean
projection test, which checks the query arguments the ability builds
instead of counting post meta queries.

Also drops the trailing period from the hook documentation references,
which the PHPStan hook docblock rule reads as part of the file path.

…ery`.

This matches the name and label that the AI plugin uses since
WordPress/ai#1002.