Group Editorial Notes and Updates controls in editor sidebar

[macayu17]

What?

Closes #601

Moves the Content Summarization sidebar control so the Editorial Notes and Editorial Updates controls stay
grouped together in the post editor sidebar.

Why?

The summary action currently appears between Generate Editorial Notes and Apply Editorial Updates. That splits
two related editorial actions and makes the notes/updates flow feel disconnected.

How?

• Registers the Summarization editor assets on enqueue_block_editor_assets with priority 5 so the Summary control loads before the Editorial Notes and Editorial Updates controls.
• Keeps the post-editor screen guard so the summary control does not load in unrelated block editor contexts.
• Adds regression coverage for the Summarization asset hook registration.

Use of AI Tools

AI assistance: Yes
Tool(s): OpenAI Codex
Model(s): GPT-5.5
Used for: Test updates, and local verification. I reviewed the changes and take responsibility for the final submission.

Testing Instructions

Automated checks run locally:

git diff --check
php -l includes/Experiments/Summarization/Summarization.php
php -l tests/Integration/Includes/Experiments/Summarization/SummarizationTest.php
php vendor/bin/phpcs --standard=phpcs.xml.dist includes/Experiments/Summarization/Summarization.php tests/
Integration/Includes/Experiments/Summarization/SummarizationTest.php
php vendor/bin/phpstan analyse includes/Experiments/Summarization/Summarization.php tests/Integration/Includes/
Experiments/Summarization/SummarizationTest.php --memory-limit=1G --no-progress
php vendor/bin/phpcs --standard=phpcs.xml.dist

Manual verification:

1. Enable Content Summarization, Editorial Notes, and Editorial Updates.
2. Open a post in the editor with enough content for summarization.
3. Generate Editorial Notes so pending notes exist and Apply Editorial Updates is visible.
4. Confirm Generate Editorial Notes and Apply Editorial Updates are adjacent in the sidebar.
5. Confirm Generate/Regenerate Summary appears before those controls and still generates or regenerates the summary block.

[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: macayu17 <ayushhoff@git.wordpress.org>
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.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR updates the Summarization experiment to enqueue its editor assets via the block editor-specific hook instead of the general admin hook, and adds an integration test to prevent regressions.

Changes:

• Switch asset enqueuing from admin_enqueue_scripts to enqueue_block_editor_assets.
• Update enqueue_assets() to no longer accept $hook_suffix and to use get_current_screen() for gating.
• Add an integration test asserting the correct hook usage and ensuring cleanup of registered actions.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
includes/Experiments/Summarization/Summarization.php	Moves editor asset loading to the block editor hook and updates the enqueue gate accordingly.
tests/Integration/Includes/Experiments/Summarization/SummarizationTest.php	Adds coverage to ensure editor assets are registered on the correct hook (and not on the generic admin hook).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.50%. Comparing base (0a84f42) to head (b13b7fe).

Additional details and impacted files

@@              Coverage Diff              @@
##             develop     #605      +/-   ##
=============================================
+ Coverage      74.45%   74.50%   +0.04%     
  Complexity      1740     1740              
=============================================
  Files             85       85              
  Lines           7521     7522       +1     
=============================================
+ Hits            5600     5604       +4     
+ Misses          1921     1918       -3     

Flag	Coverage Δ
unit	74.50% <100.00%> (+0.04%)	⬆️

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]

Testing on Playground and seems the buttons are still separated with the content summarization in between them:

[macayu17]

@jeffpaul I have made the changes. Please review them

[jeffpaul]

Tested well on Playground, thanks!

[dkotter]

Left a few minor comments.

But I'm wondering if this is overcomplicating things? Can we not just change the priority order of the enqueue hooks to ensure the Summarization script is always loaded either first or last? In doing a quick test, seems if I set the priority to 5 on the enqueue_assets hook for Summarization, it always loads before Editorial Notes