Expand description
The forge reads and writes of the release engine, through gh and
glab, the clients rk release status reads through.
rk keeps no HTTP client and holds no token: each client reads its own
credential from the environment the CI job sets, GH_TOKEN on GitHub
and GITLAB_TOKEN on GitLab. A JSON body travels on the client’s
standard input, so no body is written to disk. A read that fails is
never read as an absence: only a definite not-found answers None. A
list is read whole: an exact filter where the forge offers one, and
every page through the client’s --paginate, because a first page
proves no absence.