feat(jsonrpc): add tracked response receipts

[danielkov]

Summary

Adds optional responder APIs that return a receipt for the outgoing JSON-RPC response:

• Responder::respond_tracked
• Responder::respond_with_result_tracked
• ResponseReceipt

Awaiting the receipt confirms that the response frame has been queued for transport. For a batched request, the receipt waits until the complete batch response is assembled and queued, not merely until one response entry is ready.

The existing responder APIs keep their current behavior. Callers only pay for tracking when they use the new methods.

This gives handlers an ordering point for follow-up work that must happen after the response, such as emitting a notification that refers to a newly accepted resource.

Related

• Session injection RFD: docs(rfd): mid-turn input via session/inject (queue and steer) agent-client-protocol#1261
• First consumer: feat(unstable-v2): add session injection support #339

[danielkov]

Summary

Adds optional responder APIs that return a receipt for the outgoing JSON-RPC response:

• Responder::respond_tracked
• Responder::respond_with_result_tracked
• ResponseReceipt

Awaiting the receipt confirms that the response frame has been queued for transport. For a batched request, the receipt waits until the complete batch response is assembled and queued, not merely until one response entry is ready.

The existing responder APIs keep their current behavior. Callers only pay for tracking when they use the new methods.

This gives handlers an ordering point for follow-up work that must happen after the response, such as emitting a notification that refers to a newly accepted resource.

Related

• Session injection RFD: docs(rfd): mid-turn input via session/inject (queue and steer) agent-client-protocol#1261
• First consumer: feat(unstable-v2): add session injection support #339

[danielkov]

Summary

Adds optional responder APIs that return a receipt for the outgoing JSON-RPC response:

• Responder::respond_tracked
• Responder::respond_with_result_tracked
• ResponseReceipt

Awaiting the receipt confirms that the response frame has been queued for transport. For a batched request, the receipt waits until the complete batch response is assembled and queued, not merely until one response entry is ready.

The existing responder APIs keep their current behavior. Callers only pay for tracking when they use the new methods.

This gives handlers an ordering point for follow-up work that must happen after the response, such as emitting a notification that refers to a newly accepted resource.

Related

• Session injection RFD: docs(rfd): mid-turn input via session/inject (queue and steer) agent-client-protocol#1261
• First consumer: feat(unstable-v2): add session injection support #339

[danielkov]

Summary

Adds optional responder APIs that return a receipt for the outgoing JSON-RPC response:

• Responder::respond_tracked
• Responder::respond_with_result_tracked
• ResponseReceipt

Awaiting the receipt confirms that the response frame has been queued for transport. For a batched request, the receipt waits until the complete batch response is assembled and queued, not merely until one response entry is ready.

The existing responder APIs keep their current behavior. Callers only pay for tracking when they use the new methods.

This gives handlers an ordering point for follow-up work that must happen after the response, such as emitting a notification that refers to a newly accepted resource.

Related

• Session injection RFD: docs(rfd): mid-turn input via session/inject (queue and steer) agent-client-protocol#1261
• First consumer: feat(unstable-v2): add session injection support #339

[danielkov]

Summary

Adds optional responder APIs that return a receipt for the outgoing JSON-RPC response:

• Responder::respond_tracked
• Responder::respond_with_result_tracked
• ResponseReceipt

Awaiting the receipt confirms that the response frame has been queued for transport. For a batched request, the receipt waits until the complete batch response is assembled and queued, not merely until one response entry is ready.

The existing responder APIs keep their current behavior. Callers only pay for tracking when they use the new methods.

This gives handlers an ordering point for follow-up work that must happen after the response, such as emitting a notification that refers to a newly accepted resource.

Related

• Session injection RFD: docs(rfd): mid-turn input via session/inject (queue and steer) agent-client-protocol#1261
• First consumer: feat(unstable-v2): add session injection support #339

[danielkov]

Summary

Adds optional responder APIs that return a receipt for the outgoing JSON-RPC response:

• Responder::respond_tracked
• Responder::respond_with_result_tracked
• ResponseReceipt

Awaiting the receipt confirms that the response frame has been queued for transport. For a batched request, the receipt waits until the complete batch response is assembled and queued, not merely until one response entry is ready.

The existing responder APIs keep their current behavior. Callers only pay for tracking when they use the new methods.

This gives handlers an ordering point for follow-up work that must happen after the response, such as emitting a notification that refers to a newly accepted resource.

Related

• Session injection RFD: docs(rfd): mid-turn input via session/inject (queue and steer) agent-client-protocol#1261
• First consumer: feat(unstable-v2): add session injection support #339

[danielkov]

Summary

Adds optional responder APIs that return a receipt for the outgoing JSON-RPC response:

• Responder::respond_tracked
• Responder::respond_with_result_tracked
• ResponseReceipt

Awaiting the receipt confirms that the response frame has been queued for transport. For a batched request, the receipt waits until the complete batch response is assembled and queued, not merely until one response entry is ready.

The existing responder APIs keep their current behavior. Callers only pay for tracking when they use the new methods.

This gives handlers an ordering point for follow-up work that must happen after the response, such as emitting a notification that refers to a newly accepted resource.

Related

• Session injection RFD: docs(rfd): mid-turn input via session/inject (queue and steer) agent-client-protocol#1261
• First consumer: feat(unstable-v2): add session injection support #339

[danielkov]

Summary

Adds optional responder APIs that return a receipt for the outgoing JSON-RPC response:

• Responder::respond_tracked
• Responder::respond_with_result_tracked
• ResponseReceipt

Awaiting the receipt confirms that the response frame has been queued for transport. For a batched request, the receipt waits until the complete batch response is assembled and queued, not merely until one response entry is ready.

The existing responder APIs keep their current behavior. Callers only pay for tracking when they use the new methods.

This gives handlers an ordering point for follow-up work that must happen after the response, such as emitting a notification that refers to a newly accepted resource.

Related

• Session injection RFD: docs(rfd): mid-turn input via session/inject (queue and steer) agent-client-protocol#1261
• First consumer: feat(unstable-v2): add session injection support #339