/**
 * These tools all accept a `connectionReason` in their schema. That parameter
 * is only honest if the work actually happens on the resolved connection - a
 * handler that resolves the connection and then quietly operates on the
 * default/active managers is the same "accepted but ignored parameter" bug as
 * a param nothing reads at all.
 *
 * Each test below routes to a *non-default* connection and asserts the effect
 * landed there, not on the default managers.
 */
export {};
//# sourceMappingURL=connection-routing.test.d.ts.map