Two small questions about the subscriptions/listen response shape added in #2953 (and the related _meta type from #2889). Both may be intentional, so this is a request to confirm rather than a bug report.

1. subscriptions/listen has no dedicated *ResultResponse envelope

The draft defines a per-method JSON-RPC response envelope for every request method:

CallToolResultResponse, CompleteResultResponse, DiscoverResultResponse, GetPromptResultResponse, ListPromptsResultResponse, ListResourcesResultResponse, ListResourceTemplatesResultResponse, ListToolsResultResponse, ReadResourceResultResponse

subscriptions/listen is the one request method without a matching SubscriptionsListenResultResponse. #2953 added SubscriptionsListenResult (now a member of the ServerResult union) but no envelope def.

Is the omission intentional? A few things suggest it might be:

• SubscriptionsListenResult.resultType is "complete"-only, so there's no XResult | InputRequiredResult union for a dedicated envelope to express (unlike tools/call / prompts/get / resources/read).
• The response is a terminal teardown message sent only on graceful close, not a synchronous request reply.

If the intent is that subscriptions/listen falls back to the generic JSONRPCResultResponse (result: Result) rather than getting its own typed envelope, that's easy to honor. The asymmetry with the other nine methods is conspicuous enough to be worth confirming as deliberate. If instead a SubscriptionsListenResultResponse was meant to land alongside the result, this is a heads-up that it's missing.

2. SubscriptionsListenResultMeta vs the ...MetaObject naming convention

The _meta-contents defs are named with a MetaObject suffix:

• MetaObject
• RequestMetaObject
• NotificationMetaObject (added in Align draft schema with spec docs (subscriptionId, HeaderMismatch, notification directions) #2889)

but SubscriptionsListenResultMeta (added in #2953) ends in Meta. Since NotificationMetaObject and SubscriptionsListenResultMeta landed within a week of each other with different suffixes, the shorter one looks like it may be an unintentional divergence. Would a rename to SubscriptionsListenResultMetaObject be welcome for consistency, or is the shorter suffix deliberate?