Clarify changelog scope: kernel-specific, not XEUS-wide

XEUS's create_error_reply / create_successful_reply helpers in
xhelper.cpp always set status, and the mainstream XEUS-based kernels
(xeus-python, xeus-r) go through those helpers — their execute_reply
messages are conforming. The omission is specific to kernel authors
who bypass the helpers or use an older XEUS. Maple 2025 is the only
one currently known to do that.

The previous wording implied every XEUS-based kernel was at risk,
which would misdirect users of conforming kernels.

Author: cderv

news/changelog-1.10.md

@@ -52,7 +52,7 @@ All changes included in 1.10:
 
 ### Jupyter
 
-- ([#14374](https://github.com/quarto-dev/quarto-cli/pull/14374)): Avoid a crash when a XEUS-based kernel (e.g. Maple 2025) returns `execute_reply` without the required `status` field. The failing cell is recorded as an error instead of aborting the render. (author: @ChrisJefferson)
+- ([#14374](https://github.com/quarto-dev/quarto-cli/pull/14374)): Avoid a crash when a third-party Jupyter kernel (observed with Maple 2025, built on XEUS) returns `execute_reply` without the required `status` field. The failing cell is recorded as an error instead of aborting the render. (author: @ChrisJefferson)
 
 ## Other fixes and improvements