In schema/draft/schema.ts, every notification except ElicitationCompleteNotification incorporates NotificationParams in its params type, in one of three forms:

ElicitationCompleteNotification is the only outlier:

export interface ElicitationCompleteNotification extends JSONRPCNotification {
  method: "notifications/elicitation/complete";
  params: {
    elicitationId: string;
  };
}

This shape:

• Drops _meta support, which NotificationParams makes universally available (per General fields: _meta).
• Has no named ElicitationCompleteNotificationParams def in schema.json, so SDKs that map spec defs 1:1 to types need a special case for this one notification. No other notification with params lacks a named params type.

Question: is the inline shape intentional (e.g., the SEP-1036 author wanted to forbid _meta here), or an oversight? If unintentional, the fix would be to extract a named ElicitationCompleteNotificationParams extends NotificationParams interface carrying the elicitationId field, matching the pattern used everywhere else.

Origin: PR #887 (SEP-1036).