Fix AI Status feature checklist state

[ekamran]

What?

Fixes the AI Status dashboard checklist so the "Enable a feature or experiment" step reflects whether an individual feature setting is enabled.

Why?

The checklist currently uses the feature runtime enabled state for this step. That state also depends on the global Enable AI toggle, so when global AI is off the dashboard can show the feature step as incomplete even if a feature or experiment is already enabled in Settings > AI.

This makes the setup checklist confusing because the global AI step and the individual feature step are separate checklist items.

How?

The dashboard widget now checks the saved individual feature options for the checklist step. The full status view still requires credentials, the global AI toggle, and at least one enabled feature setting.

Testing Instructions

Manual testing:

1. Go to Settings > AI.
2. Enable at least one feature or experiment.
3. Turn the global Enable AI toggle off.
4. Go to Dashboard.
5. Confirm the AI Status checklist shows:
   • Configure an AI provider: complete, if a connector is configured.
   • Globally enable AI Features: incomplete.
   • Enable a feature or experiment: complete.

Automated checks run locally:

npm run test:php -- --filter AI_Status_WidgetTest
npm run lint:php -- includes/Admin/Dashboard/AI_Status_Widget.php tests/Integration/Includes/Dashboard/AI_Status_WidgetTest.php
npm run lint:php:stan -- includes/Admin/Dashboard/AI_Status_Widget.php tests/Integration/Includes/Dashboard/AI_Status_WidgetTest.php
npm run test:e2e -- tests/e2e/specs/admin/dashboard.spec.js

Screenshots/Screencast

Before:

The Dashboard AI Status checklist showed "Enable a feature or experiment" as incomplete when global AI was off, even though an individual feature was enabled.

After:

The same checklist now shows "Enable a feature or experiment" as complete when an individual feature setting is enabled, while "Globally enable AI Features" remains incomplete.

Use of AI Tools

AI assistance: Yes
Tool(s): ChatGPT / Codex
Used for: Repository review, reproduction planning, implementation guidance, test updates, and local verification. I reviewed the changes, tested the behavior locally, and take responsibility for the final submission.

[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: ekamran <ekamran@git.wordpress.org>
Co-authored-by: dkotter <dkotter@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

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.00%. Comparing base (1446a16) to head (f7a0d60).

Additional details and impacted files

@@              Coverage Diff              @@
##             develop     #604      +/-   ##
=============================================
- Coverage      74.00%   74.00%   -0.01%     
- Complexity      1736     1738       +2     
=============================================
  Files             85       85              
  Lines           7491     7490       -1     
=============================================
- Hits            5544     5543       -1     
  Misses          1947     1947              

Flag	Coverage Δ
unit	74.00% <100.00%> (-0.01%)	⬇️

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.