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.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: dkotter <dkotter@git.wordpress.org>
Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>
Co-authored-by: gziolo <gziolo@git.wordpress.org>
Co-authored-by: justlevine <justlevine@git.wordpress.org>

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

Codecov Report

❌ Patch coverage is 0% with 19 lines in your changes missing coverage. Please review.
✅ Project coverage is 58.72%. Comparing base (df06cb5) to head (b2e8274).
⚠️ Report is 15 commits behind head on develop.

@@              Coverage Diff              @@
##             develop     #287      +/-   ##
=============================================
- Coverage      58.74%   58.72%   -0.02%     
  Complexity       573      573              
=============================================
  Files             37       37              
  Lines           2950     2951       +1     
=============================================
  Hits            1733     1733              
- Misses          1217     1218       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Noting that I've confirmed with James, Felix, and Pascal on renaming the plugin to AI; see https://wordpress.slack.com/archives/C09ASH3E87R/p1773241702237249.

Noting that I've confirmed with James, Felix, and Pascal on renaming the plugin to AI; see https://wordpress.slack.com/archives/C09ASH3E87R/p1773241702237249.

@jeffpaul I believe all of this should be done so this is ready for review

I reviewed the PR and the branding rename from "AI Experiments" to "AI" looks complete — all user-facing plugin name references have been updated.

Regarding @jeffpaul's suggestion about renaming the remaining experiment-named items: I'd suggest tracking that as a separate issue. The scope is significant — it touches the public API surface and would benefit from a deprecation strategy before 1.0:

Public API (requires deprecation):

• 9 hooks (ai_experiments_register_experiments, ai_experiments_enabled, ai_experiments_initialized, etc.)
• 9 constants (AI_EXPERIMENTS_DIR, AI_EXPERIMENTS_VERSION, AI_EXPERIMENTS_PLUGIN_FILE, etc.)
• 3 option name patterns (ai_experiments_enabled, ai_experiment_{id}_enabled, ai_experiment_{id}_field_{name})
• Public classes/interfaces (Experiment, Abstract_Experiment, Experiment_Registry, Experiment_Loader, Experiment_Category)
• Namespace WordPress\AI\Experiments\

This could also be an opportunity to rethink the architecture — rather than a separate "experiment" concept, these could become "features" with a maturity stage (experimental, stable, etc.). That would make the naming more future-proof and align with the plugin rebrand.

Doing it before 1.0 makes sense since breaking changes are easier early, but it shouldn't block this PR.

What is the preferred workflow for merging PRs? @dkotter, do you plan to handle it? There is no blocking feedback, assuming we follow up with additional refactorings. If I understand correctly, @justlevine is already working on related enhancements in #309.

If I understand correctly, @justlevine is already working on related enhancements in #309.

Yup, specifically the public API stuff you noted. Getting this in sooner than later would let me work faster and chunk things into parallel work for better collab.

What is the preferred workflow for merging PRs? @dkotter, do you plan to handle it? There is no blocking feedback, assuming we follow up with additional refactorings.

Generally either Jeff or I will merge, once something has been approved and we've discussed wanting it in the next release (which generally is anything that has been approved though sometimes we hold something). But I agree, getting this in now will help unblock future work. Will merge this once tests are finished running