Plugin Directory: Add wp-env local development environment

[dd32]

Summary

Local development environment for the Plugin Directory using wp-env (Docker, PHP 8.4).

Environment setup:

cd environments && npm install
npm run plugins:env start

On first start, ~30 plugins are auto-imported from wordpress.org (featured, popular, beta sections).

What works

• Plugin browsing, single plugin pages, and search
• Plugin submissions and the review/approval process
• Readme validator, block plugin checker, release management pages
• Dev login button on wp-login for quick admin access
• npm run plugins:import <slug> to import individual plugins from SVN
• npm run plugins:refresh to re-import all plugin metadata from the API
• Admin notice reminding to import approved plugins via CLI

What does not work

• Trigger SVN Sync button
• Custom crons tightly coupled to Cavalcade
• Commits metabox (no trac_plugins table)
• HelpScout metabox (no HelpScout access)
• Reviews (could be mocked in future)

Changes

Environment (environments/)

• plugin-directory/.wp-env.json — wp-env config with PHP 8.4, mu-plugin mocks, theme mappings, lifecycle scripts
• plugin-directory/bin/after-start.sh — Installs CLI tools (svn, unzip, zip), sets up permalinks, creates pages, imports stub DB tables, creates browse terms, imports plugins
• plugin-directory/bin/import-plugins.php — Bulk imports plugin data from the wordpress.org REST API (metadata, users, icons, banners, screenshots, tags, contributors, committer access)
• plugin-directory/bin/database-tables.sql — Stub wp_svn_access and wp_update_source tables
• mocks/mu-plugins-loader.php — Loads mu-plugins from pub/ and wporg-mu-plugins/
• mocks/wporg-query-filter.php — Intercepts queries to production-only tables
• mocks/wporg-dev-login.php — One-click admin login on wp-login screen
• mocks/wporg-plugins-local-reminders.php — Admin notice for approved plugins needing import
• .nvmrc — Node 20 requirement

Plugin Directory code fixes

• Gate SVN credential usage on defined() checks, bail on writes without credentials
• Fix SVN::ls() fatal when XML parsing fails (no SVN server)
• Fix undefined $plugins_prefix variable in custom_redirect()
• Fix /readme.txt redirect path for non-/plugins/ environments
• Gate HelpScout stats on HELPSCOUT_PLUGINS_MAILBOXID constant
• Gate Two_Factor and is_email_address_unsafe() on existence checks

CI / Testing

• Flatten test directory structure (tests/phpunit/tests/ to tests/)
• Update bootstrap for wp-env test framework compatibility
• Add Plugin Directory to GitHub Actions using environments wp-env with cli container
• Remote API tests excluded from CI suite

Test plan

• cd environments && npm install && npm run plugins:env start
• Verify plugins are imported with icons, banners, and contributors
• Browse featured/popular/beta sections
• View a single plugin page without errors
• Submit a new plugin via /developers/add/
• Approve a plugin and verify the import notice appears
• Run npm run plugins:import <slug> for an approved plugin
• Run npm run plugins:refresh to re-import metadata
• Verify CI passes

🤖 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 dd32, obenland.

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

[dd32]

@obenland I suggest... running a destroy, I've also updated the packages just incase that was related..

For some reason, even when using --config the mapping paths are relative to where you're running the command from, not relative to the wp-env config, which I think could be part of the problem, along with a invalid docker mount config from a previous iteration of the environment..

Claude was incorrect in the assumption behind 39d164b...

[dd32]

At this point, I think it's as about complete as it's going to be for now.

Plugin submissions work, as does the review process.
In c87b0b2 I've added a reminder that once the plugin is approved, it needs to be imported (I'm assuming that people submit real plugins to test it...)

Some things don't work

• Trigger SVN Sync button
• Custom Crons that are tightly coupled to Cavalcade
• Commits metabox (no trac_plugins table)
• Helpscout metabox (no helpscout access)
• No reviews (Could mock it)

It would be "helpful" if the Global WordPress Header/Footer detected running locally and semi-disabled itself, but that's outside of this issues scope.

It would also be helpful if we had an API on w.org that dumps out get_post() + array_intersect( $public_safe_fields, get_metadata() ), which would allow a faster provisioning for plugins... It would avoid the current Metadata -> API output -> API Parsing -> Local metadata