muster release v5.27.2

A remote server’s spec.timeout governs each tool call. The value bounded the first connect, the health probe and the session-recovery handshake, while the requests themselves – a tool call above all – ran under the caller’s context alone: a tool that legitimately blocks for two minutes behind a server declaring timeout: 180 was cut whenever the caller’s connection gave up first, and muster reported the cut as a transport failure of the POST (transport error: failed to send request: Post "http://..."). Now every operation on a remote client – each request, and a recovery handshake on the way – runs under the server’s spec.timeout, the CRD’s default of 30 s when unset, so the documented range (1-300) holds end to end; a call that outlasts the budget fails with no answer within the server's timeout of 60s: context deadline exceeded rather than a transport error. The session-scoped clients of servers that need a sign-in get the same budget through their registration. (#1281)