High-level HTTP provider contract for host.http API 1.
Import service for setup before requiring nupp.io.http. Provider functions have no implicit receiver; Client and Response methods do. Request, Options, Version, and Capabilities come from nupp.io.http.messages, URI from nupp.io.uri, and Body is the canonical nupp.io Reader interface.
A Client owns its transport and outstanding work. A successful send returns an affine Response owning the response resources and body reader. Preserve borrowing of the Request during send and exclusive access during flush. Closing clients and responses must release resources on success, error, and cancellation paths. Implementers must not replace these affine contracts with unowned table aliases.
Capabilities describe actual behavior, including streaming, policy control, and protocol observability. Unsupported options must follow the public HTTP API's error behavior. The facade selects the implementation at require-time; clients and resource methods retain direct provider operations.