/**
 * buildEffectiveSensorMap — pure merge of built-in defaults, user
 * overrides, and observational data into per-(station, dataPoint)
 * effective rows.
 *
 * See docs/future/sensor-map.md §7 for the design contract and §3.4
 * for the discriminated-union output shape.
 *
 * Precedence (later wins):
 *   1. Built-in defaults (global template, keyed by dataPoint)
 *   2. Global user overrides (stationMac absent)
 *   3. Station-specific user overrides (stationMac matches)
 *   4. Observational metadata (firstSeen, lastSeen from discovery)
 *
 * The compat-layer transformation (legacy config → synthetic overrides)
 * belongs to Stage 3; this function takes already-normalized overrides.
 *
 * Safe mode: returns { rows: [], errors: [] }. Existing cached
 * accessories continue via configureAccessory() restore; no new
 * add/remove decisions happen.
 */
import type { DiscoveryStore, EffectiveSensorMap, SensorMapOverride, StationInventory, UiStateStore, WrapperDescriptor } from './types.js';
export interface BuildInput {
    /**
     * Raw override entries. Accepted as `unknown[]` because in v2 mode
     * the values come from user-authored `config.json`; the boundary
     * runtime-typechecks them before promoting to `SensorMapOverride`
     * (fix for review finding #10). Callers on the compat path may
     * pass already-typed overrides — they'll pass validation trivially.
     */
    userOverrides: ReadonlyArray<unknown>;
    discovery: DiscoveryStore;
    uiState: UiStateStore;
    stations: StationInventory;
    /** Existing HomeKit pairs are inventory, not fresh telemetry observations. */
    cachedPairs?: ReadonlyArray<{
        stationMac: string;
        dataPoint: string;
    }>;
    configMode: 'legacy' | 'v2' | 'safe-mode';
    /**
     * The config's adoption stamps (§18.3). Absent means the v1
     * baseline (1, 1) — every unstamped config in the field. Callers
     * with an INVALID stamp pair never reach this builder: config-mode
     * detection routes them to the safe-mode protective posture.
     */
    catalogBaseline?: number;
    catalogAdopted?: number;
}
export declare function buildEffectiveSensorMap(input: BuildInput): EffectiveSensorMap;
/**
 * Later-wins field merge for duplicate override entries with the same
 * (dataPoint, stationMac?) key. §3.3.2.
 */
/**
 * Partition ALREADY-VALID overrides into the global/station layers with
 * the SAME §3.3.2 duplicate-merge semantics the resolver applies
 * (later-field-wins per (dataPoint, stationMac?) key). Exposed for the
 * canonical serializer (review #67 round 2): canonical output must
 * mirror the proposal's own layering — a global template stays global
 * so it keeps applying to future stations — and the layering must be
 * read through this machinery, never re-derived.
 */
export declare function partitionOverrideLayers(overrides: ReadonlyArray<SensorMapOverride>): {
    global: Map<string, SensorMapOverride>;
    station: Map<string, Map<string, SensorMapOverride>>;
};
export type { WrapperDescriptor };
//# sourceMappingURL=buildEffectiveMap.d.ts.map