/**
 * method-catalog-relay.ts, asking a daemon whether it is reachable through
 * the relay, and getting the pairing payload that makes a surface able to.
 *
 * The controller has been composed on every daemon that turns the relay on
 * (platform/relay/reachability.ts), and its state was reachable through
 * exactly one door: `DaemonServer.getRelayReachability()`, an in-process method
 * on the facade. A surface running in the same process could read it; every
 * pure client, the terminal, the web surface, the agent, anything over the
 * wire, had no verb to ask and could only report the relay as unavailable,
 * which it did, honestly and uselessly.
 *
 * These two verbs expose what already exists and nothing more. `status` is the
 * controller's own value, including the `disabled` it reports when any of the
 * three gates (relay.enabled, the relay-connect capability, a configured
 * relay.url) is off, so "not reachable" and "not turned on" stay different
 * answers. `mint` is the same call the facade's capability exposes, and returns
 * null the same way when there is no live registration to mint against.
 */
import type { GatewayMethodDescriptor } from './method-catalog-shared.js';
export declare const builtinGatewayRelayMethodDescriptors: readonly GatewayMethodDescriptor[];
//# sourceMappingURL=method-catalog-relay.d.ts.map