/**
 * Cross-service HTTP capability surface (change: add-cross-service-api-topology).
 *
 * The authoritative declaration of which languages participate in cross-service API
 * topology. Kept in a dependency-free LEAF module so the language-support registry
 * can derive its `crossServiceHttp` column from it WITHOUT importing the full
 * `http-route-parser` (which several tests `vi.mock`, and which sits in the
 * call-graph's import cycle). `http-route-parser` re-exports these for the public
 * extraction API; a behavioral test (language-support.test.ts) proves each member
 * actually extracts a client call or a route, so the registry cannot over-claim.
 */
/** Languages OpenLore extracts outbound HTTP CLIENT call sites from (fetch/axios/ky/got). */
export declare const HTTP_CLIENT_LANGUAGES: ReadonlySet<string>;
/** Languages OpenLore extracts server ROUTE registrations from (the handler half of an edge). */
export declare const HTTP_ROUTE_LANGUAGES: ReadonlySet<string>;
/**
 * Languages that contribute to a cross-service edge — as a client call site, a
 * server route handler, or both. The union of the two halves above; the registry's
 * `crossServiceHttp` capability is exactly membership in this set.
 */
export declare const CROSS_SERVICE_HTTP_LANGUAGES: ReadonlySet<string>;
//# sourceMappingURL=http-capability.d.ts.map