/**
 * method-catalog-devices.ts, paired-device verbs.
 *
 * The operator-contract surface for the paired-phone capability feature: which
 * device nodes are paired and what each can serve, ASKING one of them for a
 * capability and reading back what it returned, the durable "always allow"
 * grants with the ledger behind them, revoking a grant, and running the
 * housekeeping sweep on demand with its disclosure.
 *
 * The grants surface in any client renders from these verbs, so "visible and
 * revocable in the grants surface" (owner ruling 2026-07-25) is one contract
 * every surface shares rather than a per-surface reimplementation.
 *
 * `devices.capability.request` is what makes the feature reachable from a
 * surface that does not host the device posture runtime itself. In-process, the
 * `phone` tool calls `DeviceCapabilityService.request` directly; a client with
 * no runtime of its own had a grants surface it could read and revoke from, and
 * no way to actually ask a phone for anything. These three verbs are that path,
 * and they are deliberately the SAME path: the confirmation prompt, the durable
 * grant lookup, the capture retention and the disclosure all stay inside the
 * runtime. Nothing here re-decides any of it.
 */
import type { GatewayMethodDescriptor } from './method-catalog-shared.js';
export declare const builtinGatewayDeviceMethodDescriptors: readonly GatewayMethodDescriptor[];
//# sourceMappingURL=method-catalog-devices.d.ts.map