A client that only ever meets the hub it was written with is not
tested against the hubs operators run. The skew job downloads a
released binary and runs the same suite against it.
It needs CHAIN_RELEASE_READ_TOKEN, because a Forgejo job token cannot
read release assets, and says so and fails instead of passing quietly
when the secret is absent.
Signed-off-by: flemming-it <sf@flemming.it>
A service in front of a hub needs four things: start a flow, follow
it, read what a detached run produced, and decide approvals. This is
that surface, plus the part a gateway cannot test without: a fake hub
that speaks the same service from the same .proto files and can be
scripted into every failure a real hub produces.
Errors carry the hub's own class (chain-error-kind), a coarse family,
and reachedHub, which separates a refused connection from a hub that
reports a dependency as down. Both arrive as gRPC UNAVAILABLE, and a
gateway that shows 'service not reachable' for the second one lies to
its users.
The .proto files are carried verbatim and loaded at runtime, so no
generated code can drift from the contract; two guards hold the
copies in place, and a skew suite runs the same client against a real
hub binary.
32 hermetic tests plus 4 against a real hub.
Signed-off-by: Dr. Stefan Flemming <sf@flemming.it>