/**
 * WHERE THE CROSS-PRODUCT BUS LIVES (acceptance finding F-043) — one pure resolution the CLI, the
 * bridge spawn and the tests share.
 *
 * The interactive seams, the project bus and the /ws relay read one wicked-bus db, and the
 * wicked-interactive bridge crew spawns must emit onto THE SAME one. Before this, all of them
 * fell through to wicked-bus's own default — `~/.something-wicked/wicked-bus/bus.db`, keyed by
 * HOME — so two daemons on one host (an isolated `--db` daemon beside the operator's) shared one
 * bus, armed the same durable cursor names, and raced for each other's `doc.created`.
 *
 * Resolution, in order:
 *  1. an explicit `--bus-db` / `WICKED_BUS_DB` file — the operator's own choice for the seams; the
 *     bridge can only be pointed at it when the file is named `bus.db` (wicked-bus reaches a bus
 *     through a data DIRECTORY, `WICKED_BUS_DATA_DIR`, whose file is always `bus.db`);
 *  2. an explicit `WICKED_BUS_DATA_DIR` — wicked-bus's own env, honoured as-is: `<dir>/bus.db`;
 *  3. `<core db>.bus/` — the daemon's OWN bus, a SIDECAR of its core db (`core.db.bus/` beside
 *     `core.db`, `core.db-wal`, `core.db.events/`). Why a sidecar and not `<state home>/bus/`:
 *     wicked-core embeds crew's state-home registry (`tests/fixtures/state-home-subtrees.json`,
 *     core `src/state_home.rs`) as the worker Read fence and REFUSES every launch that meets a
 *     top-level entry the registry does not classify; the registry's `core.db` entry is a PREFIX
 *     claim (`file-with-sidecars` — "the name and every sidecar sharing its prefix") that already
 *     covers a `core.db.*` directory, exactly as it covers core's own `core.db.events/`. A new
 *     top-level `bus/` would need a byte-identical registry change in BOTH repos and a core
 *     release before a single governed run could start beside it; the sidecar spelling needs
 *     neither, and `GET /diagnostics.stores` lists it for free (it lists the db's sidecars).
 *     wicked-bus keeps `config.json`, `cas/`, `archive/`, `bus.sock`, `daemon.lock` beside its
 *     `bus.db`, so the bus MUST have a directory of its own — this one.
 */
/** What decided the location — logged at boot so an operator can see which rule won. */
export type CrewBusSource = 'flag-or-env-db' | 'env-data-dir' | 'core-db-sidecar';
export interface CrewBusLocation {
    /** The bus db every cross-product seam opens — always `<dataDir>/bus.db`. */
    dbPath: string;
    /** The directory handed to the spawned bridge as `WICKED_BUS_DATA_DIR` — the SAME database the
     *  seams open, by construction (an explicit db not named `bus.db` is refused, see {@link CrewBusError}). */
    dataDir: string;
    source: CrewBusSource;
}
/** An explicit bus db wicked-bus cannot share with the bridge (its file is not `bus.db`) — a boot
 *  error, not a warning: the alternative is a daemon and a bridge on two different buses (codex on
 *  crew#506). */
export declare class CrewBusError extends Error {
    constructor(message: string);
}
export interface CrewBusInput {
    /** `--bus-db` (flag) or `WICKED_BUS_DB` (env) — an explicit db FILE, or undefined. */
    explicitDb?: string | undefined;
    /** `WICKED_BUS_DATA_DIR` — wicked-bus's own env, or undefined/empty. */
    envDataDir?: string | undefined;
    /** The daemon's core db path (`--db`, or the default under the state home). */
    coreDbPath: string;
}
/** The sidecar directory the daemon's own bus lives in: `<core db>.bus`. */
export declare function busSidecarDir(coreDbPath: string): string;
/**
 * The `WICKED_BUS_DATA_DIR` a bus db path implies: its parent when the file is `bus.db`, else
 * `null` — wicked-bus resolves ONLY a data directory (the file under it is always `bus.db`), so a
 * differently named db cannot be handed to the bridge, and the CLI says so instead of pointing the
 * bridge at a directory whose `bus.db` is a different database.
 */
export declare function busDataDirOf(busDbPath: string): string | null;
/** Resolve the cross-product bus for one daemon — pure, so two `--db` inputs can be compared.
 *  Throws {@link CrewBusError} for an explicit db whose file is not `bus.db`. */
export declare function resolveCrewBus(input: CrewBusInput): CrewBusLocation;
//# sourceMappingURL=bus-location.d.ts.map