/**
 * Mapping of harness identifiers to their native session environment variables.
 * These are used after the PID-scoped marker for harnesses that inject their
 * own per-session env vars. AGENT_SESSION_ID remains the lowest-priority
 * inheritable fallback unless trust-env is explicitly enabled.
 *
 * Note: inlined here to avoid circular dependencies with the harness registry
 * (registry -> adapters -> hooks -> storage -> session -> registry).
 */
export declare const HARNESS_ENV_VARS: Record<string, string[]>;
/**
 * Resolve the current session ID from the ambient environment (markers + env vars).
 *
 * This is used for "autodiscovery" in contexts where no explicit session ID
 * was provided (e.g. journaling low-level events).
 *
 * Precedence matches the standard adapter resolution:
 *   1. PID-scoped marker for the given harness
 *   2. Harness-native env vars (e.g. GEMINI_SESSION_ID)
 *   3. AGENT_SESSION_ID
 *
 * If AGENT_TRUST_ENV_SESSION=1 (or BABYSITTER_TRUST_ENV_SESSION=1) is set, env vars are preferred over markers.
 */
export declare function resolveAmbientSessionId(harness?: string): string | undefined;
//# sourceMappingURL=discovery.d.ts.map