docs(protocol): fix deprecation prose contradictions (codex review)

- sampling.rs module docs claimed ModelPreferences/ToolChoice/ToolChoiceMode/
  ModelHint were "Types NOT deprecated" — contradicting the markers the
  fidelity sweep added (and the schema's own @deprecated on all three named
  interfaces). The prose now matches: those three are deprecated; the
  unmarked leftovers are ToolChoiceMode (no schema symbol of its own — it
  binds the inline mode union of the deprecated ToolChoice) and Role (used
  outside sampling).
- roots.rs claimed notifications/roots/list_changed "was REMOVED entirely in
  DRAFT-2026-v1" — true of this crate's pinned schema.ts (zero bindings) but
  ambiguous as a live-spec claim, since the upstream lifecycle registry has
  removed nothing yet. Reworded to the pinned-schema-scoped form per the
  review doc's Authority note.
- logging.rs had the same "REMOVED entirely" phrasing for logging/setLevel
  (caught by the slice-completion grep) — same pinned-schema-scoped rewording,
  plus the per-request opt-in is correctly described as itself deprecated.

Author: hortovanyi

crates/turul-mcp-protocol-2026-07-28/src/logging.rs

@@ -12,8 +12,10 @@
 //!   `META_KEY_TRACEPARENT` etc. in [`crate::meta`]).
 //!
 //! The per-request log level mechanism ([`crate::meta::RequestMetaObject::log_level`])
-//! is the replacement opt-in. `logging/setLevel` was REMOVED entirely in
-//! DRAFT-2026-v1 — clients now declare desired level per-request.
+//! is the replacement opt-in (itself SEP-2577-deprecated — see above). The
+//! `logging/setLevel` RPC has no binding in this crate's pinned `schema.ts`
+//! (the stateless redesign replaced it with the per-request opt-in); clients
+//! declare the desired level per request.
 //!
 //! The wire-payload types ([`crate::notifications::LoggingMessageNotification`]
 //! and [`crate::notifications::LoggingMessageNotificationParams`]) live in

crates/turul-mcp-protocol-2026-07-28/src/roots.rs

@@ -10,9 +10,12 @@
 //! Replacement: pass directories or files via tool parameters, resource URIs,
 //! or server configuration.
 //!
-//! Note: the `notifications/roots/list_changed` notification was REMOVED
-//! entirely in DRAFT-2026-v1 (not just deprecated). Only the request/response
-//! surface remains during the 12-month migration window.
+//! Note: `notifications/roots/list_changed` is **absent from this crate's
+//! pinned `schema.ts`** (no `RootsListChangedNotification` binding exists),
+//! unlike the request/response surface above, which is deprecated-but-present
+//! through the 12-month migration window. The upstream lifecycle registry has
+//! not removed any deprecated feature yet — this describes the pinned schema,
+//! not a lifecycle-policy removal.
 
 use serde::{Deserialize, Serialize};
 use serde_json::Value;

crates/turul-mcp-protocol-2026-07-28/src/sampling.rs

@@ -13,11 +13,14 @@
 //! `CreateMessageRequestParams.include_context` values `"thisServer"` and
 //! `"allServers"`. Omit the field or use `"none"`.
 //!
-//! Types NOT deprecated:
-//! - [`Role`] — used outside sampling (e.g. by `Annotations.audience` in `meta`).
-//! - [`ModelPreferences`], [`ToolChoice`], [`ToolChoiceMode`], [`ModelHint`] —
-//!   referenced by the in-spec `sampling/createMessage` shape and the SEP-2322
-//!   MRTR `InputRequest::CreateMessage` variant during the migration window.
+//! [`ModelPreferences`], [`ToolChoice`], and [`ModelHint`] carry their own
+//! schema `@deprecated` markers and are `#[deprecated]` here accordingly;
+//! they remain referenced by the `sampling/createMessage` shape and the
+//! SEP-2322 MRTR `InputRequest::CreateMessage` variant through the migration
+//! window. [`ToolChoiceMode`] has no schema symbol of its own (it binds the
+//! inline `mode` union of the deprecated [`ToolChoice`]) and is left
+//! unmarked. The only genuinely non-deprecated export is [`Role`], which is
+//! used outside sampling (e.g. by `Annotations.audience` in `meta`).
 
 use crate::content::ContentBlock;
 use serde::{Deserialize, Serialize};