A hung MCP server listed in an agent's frontmatter can no longer stall subagent startup.
What's wrong with this entry?
MCP servers declared in an agent's frontmatter are connected through the shared dial helper with a timeout and abort signal, so a hung server can no longer stall subagent startup indefinitely.
- previously the code awaited
connectToServerdirectly with no bound - on timeout it logs a warning and returns no client
- if the server entry was newly created, the connection is still cleaned up should it land after the timeout
subagent MCP server connect
Strings lifted out of the shipped bundle, so the claim above can be checked against them.