Content Summarization: Synchronize loading state between sidebar and toolbar regenerate buttons

[Infinite-Null]

What?

Synchronizes the loading state between the right sidebar Regenerate Summary button and the block toolbar Regenerate Summary button.

Why?

Previously, when a Content Summary block was present, both the sidebar and block toolbar displayed "Regenerate Summary" buttons. However, their loading states were isolated to individual component instances. If a user clicked "Regenerate Summary" on the block toolbar, the sidebar button remained enabled and idle, allowing duplicate parallel generation requests. Now, both regenerate buttons enter the loading state simultaneously.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Sonnet 4.6
Used for: Validating bug, suggesting a fix.

Testing Instructions

1. Enable the Content Summarization experiment in plugin settings.
2. Create or edit a post with content longer than 250 characters.
3. Open the Document Settings sidebar and click Generate Summary.
4. Verify that the Content Summary block is created at the top of the post editor.
5. Select the Content Summary block so the Block Toolbar appears above it. Both the Block Toolbar and the Document Settings sidebar will now show Regenerate Summary.
6. Click Regenerate Summary on either the Block Toolbar or the Document Settings sidebar.
7. Verify that both buttons display "Generating…", show busy spinners, and become disabled simultaneously.
8. Confirm that once regeneration completes, both buttons return to normal state.

Screenshots or screencast

Before

Screen.Recording.2026-07-31.at.6.08.33.PM.mov

After

Screen.Recording.2026-07-31.at.6.06.42.PM.mov

Changelog Entry

Fixed - Synchronized loading state between sidebar and block toolbar regenerate summary buttons.

[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: Infinite-Null <ankitkumarshah@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 80.43%. Comparing base (a1ba294) to head (133bc3b).
⚠️ Report is 3 commits behind head on develop.

Additional details and impacted files

@@            Coverage Diff             @@
##             develop     #912   +/-   ##
==========================================
  Coverage      80.43%   80.43%           
  Complexity      2565     2565           
==========================================
  Files            110      110           
  Lines          10448    10448           
==========================================
  Hits            8404     8404           
  Misses          2044     2044           

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

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.