Site Health: Remove COMPRESS_SCRIPTS and COMPRESS_CSS from WordPress …

[haritpanchal]

The Site Health "Info" tab currently shows COMPRESS_SCRIPTS and COMPRESS_CSS under WordPress Constants. Per westonruter's comment on the ticket, these constants no longer have any practical effect on most hosts and will be removed as part of the ongoing work in #57548 to retire wp-admin script/style concatenation (load-scripts.php/load-styles.php). This removes their now-misleading display from Site Health ahead of that — the constants themselves and their functional use in script_concat_settings() are untouched; this is a Site Health display change only.

ENFORCE_GZIP was also mentioned in the ticket description but is not currently shown in Site Health, so no change was needed for it.

Testing instructions

1. Go to Tools → Site Health → Info → WordPress Constants.
2. Confirm COMPRESS_SCRIPTS and COMPRESS_CSS no longer appear in the list.
3. Confirm all other constants (CONCATENATE_SCRIPTS, WP_ENVIRONMENT_TYPE, etc.) are still listed correctly.
4. npm run test:php -- --group site-health passes (44 tests).
5. vendor/bin/phpcs --standard=phpcs.xml.dist src/wp-admin/includes/class-wp-debug-data.php is clean.

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

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Sonnet 5
Used for: Identifying the exact code to remove, drafting the diff and changelog note, and running the coding-standards/PHPUnit/manual smoke checks. I reviewed the diff and test output before opening this PR.

[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 haritpanchal.

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.