[desrosj]

Backports r65309 and r65417 to the 5.7 branch.

Removes tests/gutenberg/run.js and tests/gutenberg/.wp-env.sample.json, along with the chalk and uuid dev dependencies, which were only used by that script. No other script, Grunt task, or workflow in this branch references tests/gutenberg, and nothing else in the branch's tooling imports chalk or uuid.

package-lock.json is unchanged: in this branch, the versions of chalk and uuid that were listed are still required by other packages.

Trac ticket: https://core.trac.wordpress.org/ticket/65845

Use of AI Tools

Claude Code (Claude Opus 5.5) applied the trunk change to each branch and opened this PR. package-lock.json was regenerated with Node 14 / npm 6 (the version this branch's engines field specifies) using npm install --package-lock-only. npm 6 also introduced some unrelated lockfile changes that happen on this branch even without this change, so those were left out. The diff was checked to contain only deletions.

🤖 Generated with Claude Code

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props desrosj.

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

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub or WordPress.org user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.