/**
 * One-way identity migration: seed `~/.sapiom/analytics.json` from the
 * harness's legacy `~/.sapiom/harness/machine-id` when analytics.json does
 * not yet exist. Idempotent: a subsequent call after analytics.json exists is
 * always a no-op.
 *
 * Purpose: existing installs of harness 0.1.x had a stable anonymous id in
 * the harness-specific machine-id file. Seeding the canonical analytics.json
 * from that value preserves the longitudinal join key so prior sessions stay
 * attributable to the same install after the upgrade.
 *
 * Contract:
 * - Reads machine-id only if analytics.json is absent (avoids file-system
 *   I/O on the hot path for already-migrated installs).
 * - Never throws; degrades silently on any I/O failure (unwritable HOME, etc.)
 * - Call once at harness server boot, before the analytics emitter is created
 *   (so the emitter's IdentityStore finds the seeded file on first track()).
 */
/**
 * @param legacyMachineIdPath Absolute path to `~/.sapiom/harness/machine-id`.
 * @param analyticsJsonPath Absolute path to `~/.sapiom/analytics.json`.
 *   Defaults to the canonical location.
 */
export declare function migrateHarnessIdentity(legacyMachineIdPath: string, analyticsJsonPath?: string): Promise<void>;
//# sourceMappingURL=identity-migration.d.ts.map