import { DoomHarnessContext, HarnessState, HarnessState as HarnessState$1 } from "@agimon-ai/doompi-config/types";
import { HarnessFailureReporter } from "@agimon-ai/doompi-core/runtime-log-sink-telemetry";
import { HARNESS_STATE_KEYS, projectHarnessEnvironment } from "@agimon-ai/doompi-config/harnessState";
import { HARNESS_STATE_POINTER, HarnessStateTransactionSnapshot, createHarnessSession, harnessRoot, loadHarnessState, requireHarnessPaths, requireHarnessRoot, resetHarnessStore, restoreHarnessStateSnapshot, snapshotHarnessState } from "@agimon-ai/doompi-config/harnessStore";
//#region src/composition/harnessState/index.d.ts
export declare function readHarnessState(environment?: NodeJS.ProcessEnv, report?: HarnessFailureReporter): HarnessState;
export declare function getHarnessState(report?: HarnessFailureReporter): HarnessState;
/**
 * Re-reads the state, dropping what this process had cached.
 *
 * The store caches for the life of a process because nothing else writes the
 * file it owns. A test suite and a Pi reload are the two places that outlive
 * that assumption, so both come through here.
 */
export declare function refreshHarnessState(report?: HarnessFailureReporter): HarnessState;
export declare function updateHarnessState(patch: Partial<HarnessState>, environment?: NodeJS.ProcessEnv): HarnessState;
//#endregion
export { type DoomHarnessContext, HARNESS_STATE_KEYS, HARNESS_STATE_POINTER, type HarnessState$1 as HarnessState, type HarnessStateTransactionSnapshot, createHarnessSession, harnessRoot, loadHarnessState, projectHarnessEnvironment, requireHarnessPaths, requireHarnessRoot, resetHarnessStore, restoreHarnessStateSnapshot, snapshotHarnessState };
//# sourceMappingURL=index.d.cts.map