/**
 * Resolve the effective cortex.yaml path for read-mode commands.
 *
 * Order (first hit wins):
 *   1. $PRZM_CORTEX_CONFIG_PATH — explicit override
 *   2. Active workspace from `~/.cortex/state.json` — the workspace
 *      user picked via `cortex workspace switch`. Read synchronously
 *      here so every command that touches config doesn't have to be
 *      async-aware.
 *   3. Walk up from cwd looking for `config/cortex.yaml` — handles
 *      `cortex <cmd>` run from any subdirectory of the repo (or from
 *      the repo root itself).
 *   4. `~/.cortex/config/cortex.yaml` — legacy global-install location,
 *      kept as a fallback for setups that predate workspaces.
 *   5. Fallback: cwd-relative `./config/cortex.yaml`, whether or not it
 *      exists. Commands that expect a real file surface a readable
 *      "not found" error; commands that bootstrap a new config (like
 *      `cortex init`) treat this as their write target.
 *
 * The returned path may not exist on disk — it's the *intended*
 * location. Callers read/write it and handle ENOENT themselves.
 */
export declare function resolveConfigPath(): string;
//# sourceMappingURL=config-path.d.ts.map