- ServerEntrySchema mirrors the client's startupTimeoutMs/healthCheckIntervalMs
bounds and validateServers re-judges the reconnect policy via the client's
own resolveReconnectPolicy, so a bad entry is refused where it is written
- assertTemplateSyntax anchors each ${...} occurrence to a whole token; a
nested prefix the resolver would leave behind is refused at the write
- probeServer answers a pre-aborted signal immediately and breaks a hung
connect by closing the client on abort; the option's JSDoc says exactly that
- mcp-manager/status emission and async status observers are contained per
docs/defensive-patterns.md; onChange admits void | Promise<void>
- toClientConfig resolves through the client schema (no type assertions),
the gave-up disposal loop contains a disposer throw, and the mount re-check
comment states the serialized-tail truth