export interface DatMigrationEntry {
    /** Human-readable area, e.g. "Camera — one-shot photo". */
    area: string;
    /** The raw DAT symbols the migrant has today, per platform. */
    datSymbols: {
        android: string[];
        ios: string[];
    };
    /** The Extentos call that replaces them (property path, e.g. glasses.camera.capturePhoto). */
    extentosCall: string;
    /**
     * Feature name from getPlatformInfo.features[] to drill into with
     * getCapabilityGuide(feature) for the full Kotlin/Swift idiom. null when
     * the replacement isn't a capability primitive (bootstrap, permissions).
     */
    extentosFeature: string | null;
    /** One-line semantic delta: what actually changes for the developer. */
    whatChanges: string;
    /** Optional deeper-dive pointers into the rest of the tool surface. */
    drill?: {
        codeExample?: string;
        searchDocs?: string;
        tool?: string;
    };
}
export declare const DAT_MIGRATION_ENTRIES: DatMigrationEntry[];
export declare const DAT_MIGRATION_PLAN: string[];
export declare const DAT_COEXISTENCE_NOTE = "This is a FULL-CUTOVER guide \u2014 replace your DAT calls with Extentos primitives. Running raw DAT and Extentos side-by-side in one process is NOT supported today: the Meta DeviceSession is a single-owner handle and there is no public accessor to the DAT session underneath Extentos yet. Incremental / side-by-side adoption is a roadmap item, not a current capability. Migrate an app fully, or keep it on raw DAT.";
export declare const MIGRATION_SOURCES: readonly ["meta_dat"];
export type MigrationSource = (typeof MIGRATION_SOURCES)[number];
//# sourceMappingURL=datMigrationMap.d.ts.map