Summary
Rename the internal Experimentals constants associated with MCPEXP002 so their names and documentation reflect the diagnostic's actual scope: experimental extensibility points in the C# SDK implementation, not only subclassing.
Background
MCPEXP002 currently covers SDK-specific extensibility APIs including subclassing, custom request handlers, alternate handlers and filters, outgoing request interception, and routing metadata. Its shared constants remain named Subclassing_DiagnosticId, Subclassing_Message, and Subclassing_Url, which is misleading for APIs unrelated to subclassing.
Proposed change
- Rename the shared constants to names such as
Extensibility_DiagnosticId, Extensibility_Message, and Extensibility_Url.
- Update XML documentation to describe
MCPEXP002 consistently as experimental extensibility points in the C# implementation.
- Update references without changing the diagnostic ID or suppression behavior.
- Revise diagnostic documentation if it overemphasizes subclassing.
This is an internal naming and documentation cleanup. Consumers will continue suppressing MCPEXP002 as before.
Summary
Rename the internal
Experimentalsconstants associated withMCPEXP002so their names and documentation reflect the diagnostic's actual scope: experimental extensibility points in the C# SDK implementation, not only subclassing.Background
MCPEXP002currently covers SDK-specific extensibility APIs including subclassing, custom request handlers, alternate handlers and filters, outgoing request interception, and routing metadata. Its shared constants remain namedSubclassing_DiagnosticId,Subclassing_Message, andSubclassing_Url, which is misleading for APIs unrelated to subclassing.Proposed change
Extensibility_DiagnosticId,Extensibility_Message, andExtensibility_Url.MCPEXP002consistently as experimental extensibility points in the C# implementation.This is an internal naming and documentation cleanup. Consumers will continue suppressing
MCPEXP002as before.