Add some basic dashboard widgets

[dkotter]

What?

Adds the framework for registering new dashboard widgets and adds two to start: AI Status and AI Capabilities

Why?

The admin dashboard in WordPress provides a quick, at-a-glance place to get an overview of your site. Adding in some AI dashboard widgets can provide more value there.

How?

• Adds the framework to easily register dashboard widgets
• Adds an AI Status dashboard widget that will render a simple getting started guide if things aren't set up yet. If things are setup, will show which Providers are connected and which Experiments are turned on
• Adds an AI Capabilities widget that will render how many Abilities we have (same output that's on the Abilities Explorer page) as well as what AI capabilities each registered Provider has

Use of AI Tools

Planned approach and executed that plan using Claude Code running Opus 4.6. Tested and cleaned things up manually.

Testing Instructions

1. Pull this PR down and run npm i && npm run build
2. Add an AI Provider plugin and set that up
3. Go to the Dashboard page and ensure you see an AI Status and AI Capabilities widget
4. Turn Experiments on/off and ensure they are reflected there
5. Do the same for individual Providers

Screenshots

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

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>

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

[codecov]

Codecov Report

❌ Patch coverage is 44.74708% with 142 lines in your changes missing coverage. Please review.
✅ Project coverage is 67.30%. Comparing base (4f5732e) to head (21e8e48).
⚠️ Report is 101 commits behind head on develop.

Files with missing lines	Patch %	Lines
includes/Admin/Dashboard/AI_Status_Widget.php	33.57%	93 Missing ⚠️
...ncludes/Admin/Dashboard/AI_Capabilities_Widget.php	47.19%	47 Missing ⚠️
includes/Admin/Dashboard/Dashboard_Widgets.php	95.00%	1 Missing ⚠️
includes/Main.php	0.00%	1 Missing ⚠️

Additional details and impacted files

@@              Coverage Diff              @@
##             develop     #311      +/-   ##
=============================================
- Coverage      68.36%   67.30%   -1.07%     
- Complexity       813      874      +61     
=============================================
  Files             53       56       +3     
  Lines           3945     4202     +257     
=============================================
+ Hits            2697     2828     +131     
- Misses          1248     1374     +126     

Flag	Coverage Δ
unit	67.30% <44.74%> (-1.07%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jeffpaul]

Only adjustment here is to "Enable a feature or experiment" and a column between Connectors and Experiments for Features that will include the Image Generation and Editing one underway.

[dkotter]

Only adjustment here is to "Enable a feature or experiment" and a column between Connectors and Experiments for Features that will include the Image Generation and Editing one underway.

I think it's likely that migrating Image Gen to be a Feature will happen in the next release so going to punt this to that release as well. I can come back and make this change once that has happened

[jeffpaul]

I think it's likely that migrating Image Gen to be a Feature will happen in the next release so going to punt this to that release as well. I can come back and make this change once that has happened

That works for me, I'll add a reference from this PR to the Experiments > Features open issue.

[dkotter]

I think it's likely that migrating Image Gen to be a Feature will happen in the next release so going to punt this to that release as well. I can come back and make this change once that has happened

That works for me, I'll add a reference from this PR to the Experiments > Features open issue.

Sorry, to be more specific, was going to punt this entire PR until the next release, though happy to merge this as-is if we want it in 0.6.0 (noting this is just a minor PR so no real issue holding this for a bit)

[jeffpaul]

Sorry, to be more specific, was going to punt this entire PR until the next release, though happy to merge this as-is if we want it in 0.6.0 (noting this is just a minor PR so no real issue holding this for a bit)

No strong opinion either way, plenty other things to try and wrap for 0.6.0 so will leave this here and we can YOLO into it if we want or punt and worry more in 0.7.0.

[dkotter]

Only adjustment here is to "Enable a feature or experiment" and a column between Connectors and Experiments for Features that will include the Image Generation and Editing one underway.

Now that we have a "stable" Feature in place, I've made these changes. New screenshots in the PR description

[jeffpaul]

Tests well, thanks!