Add editor support to readmes

[jeffpaul]

What?

This PR adds sections to the README.md and readme.txt files to call out the plugins intentional focus on the Block Editor only and specifically that we do not target the Classic Editor. This is in part due to recent support requests and reviews that describe expectations for Classic Editor support, which has been purposely avoided in order to focus on the current and future-leaning integration with the modern WordPress editing experience within Gutenberg. Thus this PR attempts to make it explicitly clear that expectations for AI integrations within an editor will ONLY exist with the Block Editor.

Copilot support

This pull request updates the plugin documentation to clarify editor support and emphasize the experimental nature of the plugin. The most important changes are:

Editor Support Clarification:

• Added explicit statements in both README.md and readme.txt that the AI plugin requires the Block Editor (Gutenberg) and does not support the Classic Editor or other non-Block Editor experiences. [1] [2]
• Provided a detailed explanation in README.md and a new FAQ entry in readme.txt outlining the rationale for focusing exclusively on the Block Editor and the lack of plans for Classic Editor support. [1] [2]

Experimental Status Notice:

• Improved the experimental status notice in README.md by converting it to a prominent callout, warning users about potential instability and recommending use in non-production environments.

Why?

How?

Use of AI Tools

AI assistance: None, besides the Copilot summary from this PR description.

Testing Instructions

Screenshots or screencast

Before	After

Changelog Entry

Added - Documentation callouts that the plugin has targeted support for the Block Editor only.

[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: jeffpaul <jeffpaul@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.

[github-actions]

✅ WordPress Plugin Check Report

✅ Status: Passed

📊 Report

All checks passed! No errors or warnings found.

---

🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.41%. Comparing base (ba6d4b8) to head (99fbd85).

Additional details and impacted files

@@            Coverage Diff             @@
##             develop     #766   +/-   ##
==========================================
  Coverage      76.41%   76.41%           
  Complexity      1828     1828           
==========================================
  Files             87       87           
  Lines           7764     7764           
==========================================
  Hits            5933     5933           
  Misses          1831     1831           

Flag	Coverage Δ
unit	76.41% <ø> (ø)

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

☔ View full report in Codecov by Harness.
📢 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.