/**
 * method-catalog-push.ts
 *
 * Browser-push (Web Push) verb descriptors: the VAPID public-key read, and the
 * subscription lifecycle (register / list / delete / verify) a PWA uses to
 * receive approvals and completions as notifications.
 *
 * These are pure descriptors so `buildOperatorContract` / the generated catalog
 * / api docs see them; the handlers are attached at RuntimeServices construction
 * time in routes/push.ts (the same `catalog.register(descriptor, handler)`
 * pattern fleet.* uses), reached over HTTP through the generic
 * `/api/control-plane/methods/{id}/invoke` endpoint.
 *
 * Verb tails follow docs/decisions/2026-07-06-core-verb-spec.md: register is
 * `create`, unregister is `delete`, the collection read is `list`, the public
 * key read is `get`. `verify` (send a live test push to prove the round trip)
 * is not a generic CRUD word, it is documented in the `push-delivery` exempt
 * category in packages/contracts/src/core-verbs.ts.
 *
 * Like the other handler-registered verb groups (fleet.*, checkpoints.*,
 * sessions.search) these declare `transport: ['ws']` and carry NO dedicated
 * REST `http` binding: they are served by the registered in-process handler
 * through the generic `/api/control-plane/methods/{id}/invoke` endpoint, not by
 * a path route in the external daemon-sdk package. Advertising an `http` path
 * that no route serves would trip the capability-advertisement honesty gate
 * (method-catalog-route-reconcile.ts), so it is deliberately omitted.
 */
import type { GatewayMethodDescriptor } from './method-catalog-shared.js';
export declare const builtinGatewayPushMethodDescriptors: readonly GatewayMethodDescriptor[];
//# sourceMappingURL=method-catalog-push.d.ts.map