/**
 * @fileoverview Opt-in forced-GC pressure loop. Mitigates the per-request
 * heap retention scenario tracked in issue #50: per-request `McpServer` /
 * `McpSessionTransport` pairs reach `close()` cleanly, but the V8/JSC cycle
 * between `server.onmessage` and `transport` is only broken by a major GC.
 * Under sustained moderate HTTP load on a constrained host (~10 RPS for
 * hours), major GC fires too rarely to drain the backlog and old-gen
 * accumulates. A periodic `Bun.gc(true)` (synchronous, force-major) reclaims
 * the backlog cheaply — ~50 ms per call to clear dozens of pairs.
 *
 * Guards: only active on Bun with a callable `Bun.gc` and an interval > 0.
 * Returns a no-op disposer on Node, Workers, or when disabled, so callers
 * always have something safe to invoke in their shutdown path.
 * @module src/core/gcPressure
 */
/** @internal — indirection so tests can stub the gc lookup. */
export declare const _gcPressureInternals: {
    resolveBunGc(): ((sync?: boolean) => void) | undefined;
};
/**
 * Starts an interval that calls `Bun.gc(true)` every `intervalMs`.
 *
 * @param intervalMs - Interval in milliseconds. `0` (or negative) disables.
 * @returns Disposer that clears the interval. Safe to call when disabled —
 * the no-op disposer is returned in that case.
 */
export declare function startGcPressureLoop(intervalMs: number): () => void;
//# sourceMappingURL=gcPressure.d.ts.map