/**
 * Single source of truth for Sensorium's data directory.
 *
 * Everything the server owns on disk lives under this one dir: memory.db,
 * settings.json, schedules/, heartbeats, server-heartbeat.json, pids/,
 * active-sessions.json, files/, templates/, the maintenance flag, dispatcher
 * queues and locks.
 *
 * `SENSORIUM_BASE_DIR` overrides the default `~/.remote-copilot-mcp`. This is
 * the durable follow-up to the 2026-07-28 live-host incident. That day a fix
 * redirected only the LOG dir (`SENSORIUM_LOG_DIR`, see logger.ts), but a test
 * run on the live host still shared memory.db / pids / heartbeats / schedules
 * with the LIVE server through `os.homedir()` and froze it. Routing every
 * base-dir consumer through here lets the test bootstrap relocate the ENTIRE
 * data dir to a throwaway per-run temp dir — exactly as `SENSORIUM_LOG_DIR`
 * already does for logs — so the suite is structurally incapable of touching
 * production state. Side-by-side production instances become possible for free.
 *
 * Production leaves `SENSORIUM_BASE_DIR` unset, so behaviour is byte-for-byte
 * identical to the previous `join(homedir(), ".remote-copilot-mcp")`.
 *
 * Read lazily (a function, not a module const) so an override applied after this
 * module is first imported still takes effect.
 */
/** Absolute path to the Sensorium data dir (honours SENSORIUM_BASE_DIR). */
export declare function dataDir(): string;
/** `join(dataDir(), ...segments)` — the ergonomic form for the common case. */
export declare function dataPath(...segments: string[]): string;
//# sourceMappingURL=paths.d.ts.map