The spec defines cancellation semantics (notifications/cancelled) with clear MUST/SHOULD requirements, but no conformance scenario exists to validate server behavior.
Proposed checks:
- Server remains stable after receiving cancellation for an unknown request ID (MUST handle gracefully)
- Server handles cancellation of an in-progress request without degradation (SHOULD stop processing)
- Server remains stable under rapid cancellation notification bursts
The scenario requires test servers to expose a slow tool (5+ seconds) to allow cancellation to arrive during processing.
I'll submit a PR for this.
The spec defines cancellation semantics (notifications/cancelled) with clear MUST/SHOULD requirements, but no conformance scenario exists to validate server behavior.
Proposed checks:
The scenario requires test servers to expose a slow tool (5+ seconds) to allow cancellation to arrive during processing.
I'll submit a PR for this.