/**
 * DataIngestionCheckScreen — "Start your app and trigger some actions" polling screen.
 *
 * Shown after MCP setup. Polls for events every 30 seconds:
 *   1. MCP query_dataset (Bearer auth, works for all users, detects any track() call)
 *   2. App API activation endpoint (autocapture events only, session-cookie auth)
 *   3. Data-API event catalog (taxonomy events as a proxy)
 *
 * Active guidance as prominent instruction with framework-aware hint.
 *
 * Surfaces the agent's tracking plan inline (read from
 * `<installDir>/.amplitude/events.json` via `readLocalEventPlan`) so users
 * remember what they need to trigger. Each planned event is rendered with a
 * status marker that flips from spinner → ✓ as the polling loop accumulates
 * `activeEventNames` from the MCP `get_events` response — same "live arrival"
 * feedback the data-setup phase showed during instrumentation.
 *
 * Skip guard: when zero events have been observed (whether the activation
 * API is healthy or unavailable), pressing Enter or q surfaces a two-step
 * "Continue without verifying? [y] / [Esc] keep waiting" prompt so the user
 * cannot accidentally bypass verification. With partial evidence (MCP
 * observed names or catalog fallback), Enter or q confirms immediately.
 * x exits the wizard to resume later (cancel outro).
 */
import type { WizardStore } from '../store.js';
import { Integration } from '../../../lib/constants.js';
/**
 * Backend / server-side SDKs. For these integrations the App API
 * activation endpoint is unreliable as a success signal — autocapture is
 * irrelevant and the user has no browser tab to "click around" in. We
 * fall back to the data-API event catalog (taxonomy entries), which is
 * a strong proxy for "ingestion is working" in a backend context where
 * events are typically registered as the SDK initializes.
 *
 * Browser SDKs (nextjs/vue/react-router/javascript_web) intentionally
 * do NOT get this fallback — schema registrations there can predate
 * real ingestion and would falsely celebrate. Mobile / native / game
 * engine integrations are excluded too: the PR's coaching tips are the
 * primary unblock path for them and we don't want to over-trigger.
 */
export declare const BACKEND_SDK_INTEGRATIONS: ReadonlySet<Integration>;
interface DataIngestionCheckScreenProps {
    store: WizardStore;
}
export declare const DataIngestionCheckScreen: ({ store, }: DataIngestionCheckScreenProps) => import("react/jsx-runtime").JSX.Element;
export {};
