export type CapabilityKindName = "Camera" | "Microphone" | "Speaker" | "Display" | "Location" | "Notifications";
/**
 * Map declared SDK feature names → the deduped, canonically-ordered
 * CapabilityKind tiles. Unknown / cross-cutting features contribute nothing,
 * which is safe: an empty result means no tiles — the connection page hides the
 * capabilities section ("declare nothing, show nothing").
 */
export declare function capabilityKindsForFeatures(features: string[]): CapabilityKindName[];
/**
 * Does this capability footprint need a VENDOR transport, or is it a voice-only
 * app that runs on the vendorless Bluetooth-audio baseline?
 *
 * The two integration paths, derived rather than asked: microphone + speaker
 * reach the glasses through the phone's own Bluetooth routing with no vendor
 * SDK, so a voice app needs no vendor credentials, no connection page and no
 * pairing flow. Camera and display are what a vendor transport adds on top —
 * only those pull in `com.extentos:glasses-meta` and the credentialed DAT repo.
 *
 * An EMPTY footprint resolves to voice on purpose. The vendorless path is the
 * cheap one to be wrong about: a voice scaffold that later needs a camera is one
 * additive step, whereas sending someone through Meta account setup they never
 * needed is a dead-end afternoon.
 */
export declare function requiresVendorTransport(features: string[]): boolean;
//# sourceMappingURL=capabilityKinds.d.ts.map