muster release v5.27.9

muster agent --mcp-server and the REPL wait for a slow tool. The CLI’s MCP client bounded every request at 30 s, tool calls included, while a tool behind the aggregator may legitimately take longer – an MCPServer’s spec.timeout allows up to 300 s – so a tool that answered after a minute succeeded through the aggregator and failed through the bridge with transport error: ... context deadline exceeded after exactly 30 s; muster agent --timeout was bound to nothing. A tool call now runs under a timeout of its own, five minutes by default (the aggregator’s largest tool timeout), for the bridge, the REPL’s call and every CLI command that calls a tool (muster call among them); the handshake, listings, resources and prompts keep their 30 s. muster agent --timeout sets the call timeout for the REPL and the bridge, and the bridge’s call_tool takes an optional timeout argument (seconds) that bounds one call in its place – for a client that knows a read takes longer; the argument is the bridge’s own and never reaches the aggregator. (#1293)