docs(changeset): scope the sandbox limit the same way as the docs

The entry lands verbatim in the emdash CHANGELOG and carried the absolute
that 003597d narrowed everywhere else.

Author: danielmlr

.changeset/before-save-rejection.md

@@ -2,4 +2,4 @@
 "emdash": minor
 ---
 
-Adds `ContentSaveRejectedError` so a `content:beforeSave` hook can reject a save with a message for the editor. Throwing it from a trusted plugin makes the content API respond with a structured `SAVE_REJECTED` error (HTTP 422) that carries the message, and the admin shows it in the save and autosave toasts. Any other exception thrown by the hook still cancels the save, but now returns a generic `CONTENT_HOOK_ERROR` response instead of escaping as an unstructured 500 that could leak exception details. Sandboxed plugins cannot reject saves yet; their hook errors are logged and the save proceeds, as before.
+Adds `ContentSaveRejectedError` so a `content:beforeSave` hook can reject a save with a message for the editor. Throwing it from a trusted plugin makes the content API respond with a structured `SAVE_REJECTED` error (HTTP 422) that carries the message, and the admin shows it in the save and autosave toasts. Any other exception thrown by the hook still cancels the save, but now returns a generic `CONTENT_HOOK_ERROR` response instead of escaping as an unstructured 500 that could leak exception details. A plugin running in the sandbox cannot reject a save yet; the sandbox logs its hook errors and the save proceeds, as before. Moving the plugin into `plugins: []` runs it in the host process, where rejection works.