Improve control on close reason

What's the intended usage pattern of the Reader and Writer context w.r.t. closing the connection from the server side?

It seems like the connection is closed automatically by the reader / writer when the context is cancelled. However, I don't have any way of impacting the status and reason for that close within the reader / writer.

Is the intention that the user of the reader / writer closes the connection with the status and reason they want and let the writer / reader return?

Another option could be that this package would support influencing the close status and reason via an error provided as context cancellation cause.

WDYT?

まず、Reader と Writer がコンテキストのキャンセルをどのように処理しているか、また呼び出し元が現在サーバー側の接続をどのように閉じているかを追跡します。提案されている cancellation cause アプローチと接続を明示的に閉じる方法を比較し、その後、両方の経路のテストを特定する前に、close status と reason の意図された動作を定義します。

索引モデルが issue の本文から書いたものです。