Merge remote-tracking branch 'origin/main' into v2

[zbeyens]

Description
A clear and concise description of what this pull request solves. (Please do not just link to a long issue thread. Instead include a clear description here or your pull request will likely not be reviewed as quickly.)

Issue
Fixes: (link to issue)

Example
A GIF or video showing the old and new behaviors after this pull request is merged. Or a code sample showing the usage of a new API. (If you don't include this, your pull request will not be reviewed as quickly, because it's much too hard to figure out exactly what is going wrong, and it makes maintenance much harder.)

Context
If your change is non-trivial, please include a description of how the new logic works, and why you decided to solve it the way you did. (This is incredibly helpful so that reviewers don't have to guess your intentions based on the code, and without it your pull request will likely not be reviewed as quickly.)

Checks

• The new code matches the existing patterns and styles.
• The tests pass with yarn test.
• The linter passes with yarn lint. (Fix errors with yarn fix.)
• The relevant examples still work. (Run examples with yarn start.)
• You've added a changeset if changing functionality. (Add one with yarn changeset add.)

[changeset-bot]

🦋 Changeset detected

Latest commit: 4764d33

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
slate-dom	Major
slate-react	Major
slate	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ce2bd6c68c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Clear cursor marks when applying set_selection

The set_selection mark reset is now guarded by !isInTransaction(editor), but this code path executes only after apply has entered a transaction (either directly or via the runEditorTransaction wrapper), so the condition is never true. In editors with listeners (the common slate-react path), selection changes no longer clear pending marks, so subsequent typing can incorrectly inherit stale formatting after cursor moves. This regresses the prior behavior noted by the inline comment and can surface as unexpected bold/italic carryover.

Useful? React with 👍 / 👎.