/**
 * Implicit `.env` bootstrap, shared by the SDK entry point and the CLI.
 *
 * Both sites used to call dotenv's `config()` with no options beyond
 * `quiet`, and a direct `config()` call does NOT read `DOTENV_CONFIG_PATH`
 * — only dotenv's own `dotenv/config` preload entry does. So the strip this
 * repo documents and uses to vet suites,
 *
 *     env -i HOME=… PATH=… CI=true DOTENV_CONFIG_PATH=/dev/null …
 *
 * stripped nothing the moment a suite imported the built SDK: importing
 * `dist/index.js` loads `src/lib/neurolink.ts`, which loaded `.env` from the
 * working directory regardless. A credential the strip was supposed to
 * remove was present at every read site, and a suite that only passes
 * because of it looks identical to one that does not need it. See #1744;
 * the CI-only failure in #1735 is what surfaced it.
 *
 * Honouring the variable here makes that strip real. It is additive: with
 * `DOTENV_CONFIG_PATH` unset — which is every existing caller, SDK consumers
 * included — this does exactly what it did before, loading `.env` from the
 * current working directory. Only a caller that explicitly sets the variable
 * sees a difference, and what it then sees is dotenv's own documented
 * meaning for it.
 */
export declare function loadProcessDotenv(): Promise<void>;