/**
 * ImportScreen — import flow.
 *
 * Three phases:
 *   1. prompt — user types a file path (~/-relative ok)
 *   2. review — file parsed; known/unknown keys listed; user confirms to stage
 *   3. done   — known keys staged into the store as pending; user reviews
 *               them as the dirty marker on SettingsHome before committing.
 *
 * The store mutation is staged-only — we call store.set(settingsPath, value)
 * for each known key, leaving them in the pending bucket. The existing
 * propagation/save path on SettingsHome owns the actual config.json write.
 *
 * The import file format mirrors what DashboardExport writes: a JSON envelope
 * with a top-level `settings` map keyed by settingsPath. Unknown keys are
 * surfaced as warnings, not errors.
 */
import React from 'react';
import type { CategoryDef } from '../schema/types.js';
import type { SettingsStore } from '../state/settings-store.js';
import type { ActivityStore } from '../state/activity-store.js';
interface ImportScreenProps {
    store: SettingsStore;
    catalog: ReadonlyArray<CategoryDef>;
    onBack: () => void;
    activityStore?: ActivityStore;
}
export declare function ImportScreen({ store, catalog, onBack, activityStore, }: ImportScreenProps): React.ReactElement;
export {};
//# sourceMappingURL=ImportScreen.d.ts.map