I18N: Fix PHPStan errors for literal strings in nooped plurals

[westonruter]

✅ Committed in r64234 (80c6c39).

---

Follow-up to r64232 (#14079), which made the localization API require literal strings. That left five PHPStan errors on trunk, reported as warnings on PRs that touch the affected files:

src/wp-includes/post.php:1506              _n_noop() $singular and $plural expect literal-string, mixed given
src/wp-includes/category-template.php:899  _n_noop() $singular and $plural expect literal-string, mixed given
src/wp-admin/includes/media.php:2898       translate_nooped_plural() expects the literal-string nooped plural shape, array given

Post mime types. get_post_mime_types() documented the third element of each mime type as a bare array, so the literal types returned by _n_noop() were lost before media.php passed them to translate_nooped_plural(). The nooped plural shape is now declared in a @phpstan-return for get_post_mime_types(), a @phpstan-param for the post_mime_types filter (whose documented type is what PHPStan uses for the filtered return value), and a @phpstan-return for wp_edit_attachments_query(), which passes the mime types through.

Runtime strings passed to _n_noop(). register_post_status() builds its default label_count from the status label, and wp_generate_tag_cloud() supports the old-style single_text and multiple_text arguments. Both pass runtime values to _n_noop() only to build the nooped plural structure, so there is nothing to extract for translation. These are intentional for back-compat, so the errors are ignored inline with the reason, next to the existing phpcs:ignore for the corresponding I18n sniffs. Each line lists argument.type twice, since one ignore covers one error and there is one each for $singular and $plural.

Building the nooped plural arrays by hand instead was tried in one commit and reverted in the next: it duplicated the structure returned by _n_noop() and only hid the runtime strings from static analysis, without making them literal.

The nested nooped plural shape is repeated in three places. A shared type alias is being discussed in #13890 (comment) and is left for later.

PHPStan with phpstan.neon.dist now reports no errors, and the inline ignores also match at level 10, so reportUnmatchedIgnoredErrors reports nothing.

Trac ticket: https://core.trac.wordpress.org/ticket/65817

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Reproducing the CI warnings, writing the type and code changes, and verifying them with PHPStan, PHPCS, and WP-CLI; the approach was directed and reviewed by me.

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

🤖 Generated with Claude Code

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props westonruter.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.