Command Palette: Fix duplicate enqueue breaking the palette in the Site Editor

[t-hamano]

Fixes #79390

What?

Follow up to #79196.

Fixes the Command Palette not opening on the Site Editor (admin.php?page=site-editor-v2) and other boot-based admin pages.

Why?

#79196 dropped the lib/compat/wordpress-6.9/ directory. One of the removed files used to swap core's wp_enqueue_command_palette_assets out of the admin_enqueue_scripts hook, and the /wp-block-editor/v1/assets REST endpoint relied on that.

Without it, core's wp_enqueue_command_palette_assets stays hooked, and the editor then loads wp-core-commands a second time, splitting the core/commands store into two instances. initializeCommandPalette() runs, but the palette never opens.

How?

Removes the action before the asset capture in get_assets(), so the Command Palette is enqueued only once — on the page itself.

Testing Instructions

1. Enable the Extensible Site Editor experiment.
2. Open the site editor.
3. Press Cmd/Ctrl+K.
4. The Command Palette opens.

Use of AI Tools

Root cause analysis and the fix were assisted by Claude Code. All changes were reviewed by the author.

[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: t-hamano <[email protected]>
Co-authored-by: youknowriad <[email protected]>
Co-authored-by: fushar <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Flaky tests detected in fb01cb6.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/27947496018
📝 Reported issues:

• [Flaky Test] does not dirty related template parts or navigation menus when rendered in the post editor #79294 in /test/e2e/specs/editor/blocks/navigation-passive-rendering.spec.js
• [Flaky Test] three users concurrently edit a large post with diverse blocks #78754 in /test/e2e/specs/editor/collaboration/collaboration-stress.spec.ts

[youknowriad]

AFAIK, that endpoint tries to find the scripts/styles that are not loaded yet. I wonder why the command palette assets were not detected as loaded.

[youknowriad]

I noticed the command palette button (and focus styles) is cut a bit on the extensible site editor but that's probably a separate regression.

[t-hamano]

AFAIK, that endpoint tries to find the scripts/styles that are not loaded yet. I wonder why the command palette assets were not detected as loaded.

I'm not sure of the cause, but there might be room for improvement in the auto-load logic itself. Perhaps we can eventually remove some of these remove_actions. Let's consider essential improvements in a follow-up.