/**
 * Compat layer — translate a v1.6.0 (legacy) config into synthetic
 * global SensorMapOverride entries, deterministically and one-shot.
 *
 * See docs/future/sensor-map.md §6. The layer's contract:
 *   - Reads a LegacyConfig (whatever fields the user has set)
 *   - Emits a SensorMapOverride[] with `stationMac` absent (all global)
 *   - buildEffectiveSensorMap consumes them like any other override
 *   - Nothing written back to config.json; the projection is
 *     recomputed every boot
 *
 * The layer runs ONLY when configMode === 'legacy' (Stage 5). If the
 * user has a `sensorMap` field defined, v2 mode wins and this layer
 * is skipped entirely.
 *
 * Behavioral invariant: for any 1.6.0 config, the effective map
 * produced by (defaults + compatOverrides) MUST produce the same
 * HAP service graph as v1.6.0's determineSensorType-based pipeline.
 * Tested by the migration-equivalence property tests (§12.7),
 * scheduled for Stage 9.
 */
import type { SensorMapOverride, SensorUnit, StationInventory, StationRecord } from './types.js';
/**
 * v1.6.0 config shape — union of every field the compat layer inspects.
 * Fields the compat layer doesn't consume (stationFilter, dataSource,
 * apiKey/applicationKey, embedNameUpdateMinIntervalMinutes) are
 * intentionally omitted; they either flow through unchanged or are
 * consumed elsewhere.
 */
export interface LegacyConfig {
    temperatureSensors?: boolean;
    humiditySensors?: boolean;
    solarRadiationSensors?: boolean;
    co2Sensors?: boolean;
    airQualitySensors?: boolean;
    extendedSensors?: boolean;
    windSensors?: boolean;
    rainSensors?: boolean;
    pressureSensors?: boolean;
    uvSensors?: boolean;
    lightningSensors?: boolean;
    extendedDisplayMode?: 'static' | 'embed';
    thresholds?: {
        windSpeedEnabled?: boolean;
        windSpeedMph?: number;
        windGustEnabled?: boolean;
        windGustMph?: number;
        rainRateEnabled?: boolean;
        rainRateInHr?: number;
        uvEnabled?: boolean;
        uv?: number;
        lightningDistanceEnabled?: boolean;
        lightningDistanceMi?: number;
        pressureEnabled?: boolean;
        pressureInHg?: number;
    };
    units?: {
        windSpeed?: SensorUnit;
        rain?: SensorUnit;
        pressure?: SensorUnit;
        distance?: SensorUnit;
    };
    excludeSensors?: string[];
    includeOnly?: string[];
}
/**
 * Public entry point. Emits synthetic sensor-map overrides from a
 * v1.6.0 legacy config. Result is stable across calls with equal
 * input; safe to cache but cheap enough to recompute each boot.
 *
 * `stations` is the current station inventory (from AWN device list
 * or the accessory cache). If empty, the layer falls back to
 * global-only match forms (`dataPoint`, `friendlyName`) — good enough
 * for boot-before-fetch scenarios but does NOT preserve full v1
 * semantics.
 *
 * Full v1 semantics require the inventory: v1's include/exclude
 * matchers compare against SEVEN candidate forms per accessory —
 * `uniqueId` (`MAC-sensorKey`), current displayName, prefixed form
 * (`hapClean(stationName + friendlyName)`), sensorKey, friendly
 * name, station MAC, station name — and the last five are
 * station-specific. Without stations, entries like
 * `excludeSensors: ["AA:BB:CC:DD:EE:01-tempf"]` or `"Backyard"`
 * would be silently ignored (review finding #2 pre-fix).
 *
 * With inventory, the layer emits station-scoped overrides
 * (`stationMac` set) for every (station, row) pair the include/
 * exclude machinery would have disabled in v1; row-level knobs that
 * don't depend on station (threshold, displayUnit, category
 * toggles, embed mode) still flow through as global overrides.
 */
/**
 * The discovery-observed data points that resolve only via the dynamic
 * legacy-matcher fallback — the fields the compat projection must gate
 * beyond the static table (GA review P1-1). Lives here, in a module
 * with a LEAF import graph: the UI bridge imports it, and its previous
 * home (platformEffectiveMap) transitively reaches the accessory
 * classes, which the Angular app's typecheck must never include.
 */
export declare function dynamicDataPointsFrom(discovery: {
    entries: ReadonlyArray<{
        dataPoint: string;
    }>;
}, cachedPairs?: ReadonlyArray<{
    dataPoint: string;
}>): string[];
export declare function compatToOverrides(legacy: LegacyConfig, stations?: StationInventory, 
/**
 * Data points OUTSIDE the static default table that resolve via the
 * dynamic legacy-matcher fallback (GA review P1-1) — in practice the
 * discovery-observed fields the static table lacks. The compat
 * projection must gate them exactly like static rows (category
 * toggles, include/exclude, battery suppression), or a legacy
 * config with a category off would register accessories v1.7 never
 * created.
 */
dynamicDataPoints?: Iterable<string>): SensorMapOverride[];
/**
 * Legacy selectors match both stable field identities and station-derived
 * names. Missing station metadata cannot make the latter a definite non-match.
 * This is an exposure decision only; it does not synthesize row identity or
 * infer a station name from a cached HomeKit label.
 */
export declare function legacyRowFilterState(legacy: LegacyConfig, dataPoint: string, station: StationRecord, isMultiStation: boolean): 'enabled' | 'disabled' | 'unknown' | undefined;
//# sourceMappingURL=compat.d.ts.map