Discoverability of supported update methods on resources without read permission

This is not necessarily an issue, but more of a request for clarification inspired by an actual use case - whether misuse or valid, I do not know, hence why I am asking. If this is not the correct place to ask, I would appreciate any pointers to the appropriate location.

Are there any guidelines in the specification for how a client can discover supported update methods (or, in general, any write/delete/append support) on resources on a Solid server, when the client has write or append permissions but no read permission?

An example use case could maybe be an inbox, to which everyone has append permission but only the owner has read permission. So whenever a client wants to write to that inbox, the client would either know that the server supports specific types or updates (or updates in general) or just blindly send some form of update and hope it works.

Is there an existing way for a client to determine whether they can do updates on a resource without read permissions? Or if there is no way for a client to do that (without trying an update first), could something be done with response headers to indicate support for updates without read permission?

I tried to look through the open issues, but did not find anything addressing that.

Thank you in advance for your time, and apologies if this has been answered before.