vhaudiquet
29099add9d
A client tool is three moves: read the connection from the environment, make one HTTP call carrying the bearer and the contract header, and print either the answer as one JSON line or the one error shape — then exit with the code that says which happened. Common is those three moves, so no client reimplements them and all clients fail identically: `Config::from_env` (`RHEMA_URL`, `RHEMA_TOKEN`), the `Client` call with the contract envelope, `print`/`fail` and the `ToolError` exit codes. The HTTP client is `ureq`, blocking, no TLS: the contract speaks to a loopback or otherwise trusted daemon, and a remote TLS endpoint is a stated non-goal in v1 — a thin client stays thin.