3070 bulk editor during ai generation user can edit manually

[pls78]

Context

Note: to be tested together with https://github.com/Yoast/wordpress-seo-premium/pull/5021

Summary

This PR can be summarized in the following changelog entry:

• Disables the "Edit" button for posts that have a pending AI Generate call.

Relevant technical choices:

• N/A

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

Prerequisites

• Have Premium installed and active with a valid subscription
  • Make sure your site either has a public URL or you're using OAuth as your authentication mechanism
• Have some posts with a focus keyphrase set

Test the fix

• Go to Yoast -> Tools -> Bulk editor
• Select some posts that have a focus keyphrase and bulk-generate e.g. their SEO titles
  • Verify the Edit button stays deactivated while the AI generation is running

Relevant test scenarios

• Changes should be tested with the browser console open
• Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
• Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
• Changes should be tested on different browsers
• Changes should be tested on multisite

Test instructions for QA when the code is in the RC

• QA should use the same steps as above.

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

• N/A

Other environments

• This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.
• This PR also affects Yoast SEO for Google Docs. I have added a changelog entry starting with [yoast-doc-extension], added test instructions for Yoast SEO for Google Docs and attached the Google Docs Add-on label to this PR.

Documentation

• I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

• I have tested this code to the best of my abilities.
• During testing, I had activated all plugins that Yoast SEO provides integrations for.
• [] I have added unit tests to verify the code works as intended.
• If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
• I have written this PR in accordance with my team's definition of done.
• I have checked that the base branch is correctly set.
• I have run grunt build:images and committed the results, if my PR introduces or edits images or SVGs.

Innovation

• No innovation project is applicable for this PR.
• This PR falls under an innovation project. I have attached the innovation label.
• I have added my hours to the WBSO document.

Fixes https://github.com/Yoast/plugins-automated-testing/issues/3070

[github-actions]

A merge conflict has been detected for the proposed code changes in this PR. Please resolve the conflict by either rebasing the PR or merging in changes from the base branch.

[coveralls]

Coverage Report for CI Build 15

Coverage increased (+0.006%) to 55.185%

Details

• Coverage increased (+0.006%) from the base build.
• Patch coverage: 11 of 11 lines across 5 files are fully covered (100%).
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	72125
Covered Lines:	39682
Line Coverage:	55.02%
Relevant Branches:	18766
Covered Branches:	10476
Branch Coverage:	55.82%
Branches in Coverage %:	Yes
Coverage Strength:	41727.04 hits per line

---

💛 - Coveralls

[FAMarfuaty]

The new hasExternalGeneration path isn't covered by a test. registerStore() in beforeAll keeps the existing tests green now that the row reads the store, but nothing asserts the actual new behaviour — that Edit disables table-wide when the flag is set. There's a dedicated test for the sibling flag (disables every row's Edit button while Premium AI suggestions are pending review), and this deserves the mirror:

it( "disables every row's Edit button while an external AI generation is in flight", () => {
    dispatch( STORE_NAME ).setHasExternalGeneration( true );
    render( <BulkEditorTable items={ items } fieldSet={ searchFieldSet } /> );
    expect( screen.getByRole( "button", { name: "Edit What Is SEO" } ) ).toBeDisabled();
    expect( screen.getByRole( "button", { name: "Edit On-Page SEO Checklist" } ) ).toBeDisabled();
    dispatch( STORE_NAME ).setHasExternalGeneration( false ); // reset — the store is a shared singleton across this file
} );

Note the reset: because the store is registered once in beforeAll, a true left set here leaks into every later test in the file. Worth also adding a small reducer test under store/external-generation.test.js to match external-pending-changes.test.js.

[FAMarfuaty]

Consistency nit (non-blocking): the sibling flag hasExternalPendingChanges is selected once in bulk-editor-content.js and drilled down as a prop (bulk-editor-table → table-body → table-row), whereas hasExternalGeneration is read here with useSelect inside every row. Two conceptually identical global flags now follow two different patterns, and this variant adds a per-row store subscription (N per page) instead of one at the top. Unless there's a reason to diverge, I'd source it the same way as hasExternalPendingChanges and pass it through as a prop — it keeps the row presentational and the two flags symmetrical.

[pls78]

Damn, I thought about avoiding prop drilling and didn't think about the multiplication of the store subscription...

[FAMarfuaty]

CR & Acceptance: ✅