claude
1b5d093148
A Hexis 401 was spoken as an outage, which sent the owner to inspect a service running fine when the fix is a token in config. errors.As could never match: the vendored client is a separate implementation and wraps nothing in *ecosystemError. hexisError re-wraps at Maven's boundary, mapping the http.StatusText spelling back to a code, with anything unrecognised staying at status 0, which is Unreachable. The execute hop did not call ecosystemGap at all and named neither the service nor the cause. It does now, but only for an ecosystem error: an execution Hexis accepted and then failed keeps ActFailEntity, because calling a failed restart an outage is the same defect pointed the other way. A Praxis failure named no service. The classifiers already worked and handle() threw the answer away. Authorization is untouched. A 401 is still terminal. Only the sentence changed. No new Russian was written; both halves are shipped lines. The boundary adapter is the wrong layer and says so in a comment. Parsing http.StatusText output is a string contract with another repo, and a typed Hexis-side error carrying the code is the real fix. (V-587) (V-588)