@rebasepro/cli 0.25.0 → 0.26.0

package/dist/{prepare-DdnU70z8.js.map → prepare-CTw9NEkh.js.map}

@@ -1 +1 @@
-{"version":3,"file":"prepare-DdnU70z8.js","names":[],"sources":["../src/dev-db/branch-pointer.ts","../src/dev-db/last-dev-database.ts","../src/dev-db/resolve.ts","../src/dev-db/prepare.ts"],"sourcesContent":["/**\n * Which database branch this checkout is working on.\n *\n * `rebase db branch create` made a full copy of the database in about a second\n * and then stopped one step short of being a feature: there was no `switch`, no\n * `--branch` on `rebase dev`, and nothing wrote the branch anywhere a command\n * would read it. The only way to *use* a branch was to hand-edit\n * `DATABASE_URL`, and the documentation claimed otherwise — \"the CLI updates\n * your local development configuration\" — which it did not; the `.env` was\n * byte-identical afterwards.\n *\n * This is that missing step, and the shape of it is chosen to avoid three\n * things:\n *\n * 1. **It does not touch `.env`.** That file holds secrets, comments and the\n *    developer's own ordering, and a command that rewrites it in place will\n *    eventually lose something that was not its business. The branch is\n *    recorded beside the other per-checkout state in `.rebase/`, which is\n *    already gitignored — a branch is a fact about one machine, never about\n *    the project.\n *\n * 2. **It stores a name, not a connection string.** The credentials stay in\n *    exactly one place; the URL is derived by swapping the database name on\n *    the base one at resolution time. A stored URL would be a second copy of\n *    the password, and would go stale the moment `.env` changed.\n *\n * 3. **It does not outrank an explicit instruction.** `--database-url` and a\n *    `DATABASE_URL` in the shell are more immediate and more specific than a\n *    switch made yesterday, so they still win. The pointer sits directly above\n *    the project's `.env`: it is a deliberate, persistent choice, and `.env` is\n *    the project default it is meant to override. Anything less and `switch`\n *    would silently do nothing on every project that sets `DATABASE_URL` —\n *    which is every project not using the managed database.\n */\n\nimport fs from \"fs\";\nimport path from \"path\";\n\n/** Where the pointer lives, next to the rest of the per-checkout state. */\nexport function branchPointerPath(projectRoot: string): string {\n    return path.join(projectRoot, \".rebase\", \"branch.json\");\n}\n\nexport interface ActiveBranch {\n    /** The name the developer typed. */\n    name: string;\n    /** The PostgreSQL database that name refers to. */\n    database: string;\n}\n\n/**\n * The prefix `BranchService` puts on every branch database.\n *\n * Duplicated from the driver rather than imported because the CLI must answer\n * \"which database\" without loading a database driver — `rebase dev` reads this\n * before it knows which plugin the project uses. It is covered by a test that\n * fails if the driver's prefix moves.\n */\nexport const BRANCH_DB_PREFIX = \"rb_\";\n\nexport function branchDatabaseName(name: string): string {\n    return `${BRANCH_DB_PREFIX}${name}`;\n}\n\n/** Read the active branch, or null when the checkout is on the main database. */\nexport function readActiveBranch(projectRoot: string): ActiveBranch | null {\n    try {\n        const raw = fs.readFileSync(branchPointerPath(projectRoot), \"utf-8\");\n        const parsed = JSON.parse(raw) as Partial<ActiveBranch>;\n        if (typeof parsed.name !== \"string\" || typeof parsed.database !== \"string\") return null;\n        if (!parsed.name || !parsed.database) return null;\n\n        return { name: parsed.name, database: parsed.database };\n    } catch {\n        // Absent is the common case and is not an error. A corrupt file is\n        // treated the same way: the answer is \"no branch\", which is the state\n        // the developer can always get back to with `branch switch --off`.\n        return null;\n    }\n}\n\nexport function writeActiveBranch(projectRoot: string, branch: ActiveBranch): void {\n    const file = branchPointerPath(projectRoot);\n    fs.mkdirSync(path.dirname(file), { recursive: true });\n    fs.writeFileSync(file, `${JSON.stringify(branch, null, 2)}\\n`, \"utf-8\");\n}\n\n/** Return to the main database. Absent is success — this is idempotent. */\nexport function clearActiveBranch(projectRoot: string): void {\n    fs.rmSync(branchPointerPath(projectRoot), { force: true });\n}\n\n/**\n * The base connection string with its database swapped for the branch's.\n *\n * Everything else is carried across untouched — credentials, host, port, and\n * the query string, which is load-bearing here: `?sslmode=disable` is what a\n * local Docker Postgres needs, and dropping it turns a switch into a TLS error\n * that says nothing about branches.\n *\n * Returns null for a connection string that cannot be parsed, so the caller can\n * say so plainly rather than emitting a mangled URL that fails later.\n */\nexport function branchUrl(baseUrl: string, database: string): string | null {\n    try {\n        const url = new URL(baseUrl);\n        // `pathname` keeps its leading slash; a URL with no database at all\n        // still gets one, which is what connecting to a named branch means.\n        url.pathname = `/${database}`;\n\n        return url.toString();\n    } catch {\n        return null;\n    }\n}\n\n/** The database name in a connection string, for reporting what you are on. */\nexport function databaseNameOf(connectionString: string): string | null {\n    try {\n        const name = new URL(connectionString).pathname.replace(/^\\//, \"\");\n\n        return name || null;\n    } catch {\n        return null;\n    }\n}\n","/**\n * Which database the last `rebase dev` ran on, when nothing else records it.\n *\n * `rebase dev --docker` is a choice made on one command line, and every other\n * command resolved without it: while dev served the project from its compose\n * database, `rebase db url` printed a managed PGlite URL — and started that\n * daemon to print it — and `db push`, `console` and the rest would have used\n * the same empty database. Nothing said the two disagreed.\n *\n * So `rebase dev` records its choice here, and the other commands follow it\n * (`resolve.ts`, rule 5). Only Docker is recorded. Every other database is\n * already somewhere each command reads — `--database-url` aside, which is a\n * choice for one command line — or is the default, so the record holds\n * `docker` exactly when the last `rebase dev` ran on it, and any other start\n * of `rebase dev` removes it. That is also the way back: `rebase dev` without\n * `--docker`.\n *\n * Beside the branch pointer in `.rebase/`, which is gitignored: which database\n * this checkout last ran on is a fact about one machine, never the project.\n */\n\nimport fs from \"fs\";\nimport path from \"path\";\n\nimport type { DevDatabase } from \"./resolve\";\n\nexport function lastDevDatabasePath(projectRoot: string): string {\n    return path.join(projectRoot, \".rebase\", \"dev-database.json\");\n}\n\n/** Whether the last `rebase dev` ran on the compose database. */\nexport function readLastDevDocker(projectRoot: string): boolean {\n    try {\n        const parsed: unknown = JSON.parse(fs.readFileSync(lastDevDatabasePath(projectRoot), \"utf8\"));\n        return typeof parsed === \"object\" && parsed !== null && \"kind\" in parsed && parsed.kind === \"docker\";\n    } catch {\n        // Absent is the common case; unreadable has the same answer.\n        return false;\n    }\n}\n\n/** What this `rebase dev` was asked for, beside what it runs on. */\nexport interface LastDevRun {\n    /** `--docker` was on this command line. */\n    dockerFlag?: boolean;\n}\n\n/**\n * Record what this `rebase dev` runs on, and say what the last one ran on.\n *\n * A run that asked for Docker and was outranked by a connection string leaves\n * the record as it was. It is not on Docker, so it records nothing; but it is\n * not a run without `--docker` either, which is what forgets the record. The\n * reader was told to comment the `.env` line out to reach Docker, and once\n * they have, the other commands follow Docker as they did before.\n *\n * Best effort: a checkout whose `.rebase/` cannot be written still runs, and\n * the other commands then resolve as they did before this existed.\n */\nexport function recordLastDevDatabase(\n    projectRoot: string,\n    kind: DevDatabase[\"kind\"],\n    run: LastDevRun = {}\n): { previous: \"docker\" | null } {\n    const previous = readLastDevDocker(projectRoot) ? \"docker\" : null;\n    if (run.dockerFlag && kind !== \"docker\") return { previous };\n    const file = lastDevDatabasePath(projectRoot);\n    try {\n        if (kind === \"docker\") {\n            fs.mkdirSync(path.dirname(file), { recursive: true });\n            fs.writeFileSync(file, `${JSON.stringify({ kind: \"docker\", recordedAt: new Date().toISOString() }, null, 2)}\\n`);\n        } else {\n            fs.rmSync(file, { force: true });\n        }\n    } catch {\n        // See above: not worth failing a dev start over.\n    }\n\n    return { previous };\n}\n\n/**\n * What `rebase dev` says when it leaves the Docker database the last run used.\n *\n * Said rather than left to be noticed: the data a developer was working with\n * is in the container, and the managed database this run is on is a different,\n * possibly empty, one. Not said to a run that asked for Docker: the line that\n * says `--docker` was ignored, and what outranked it, is the one that applies.\n */\nexport function lastDevDatabaseNotice(previous: \"docker\" | null, kind: DevDatabase[\"kind\"], run: LastDevRun = {}): string | null {\n    if (previous !== \"docker\" || kind === \"docker\" || run.dockerFlag) return null;\n\n    return \"The last `rebase dev` ran on Postgres in Docker; this one does not. \"\n        + \"Pass --docker to stay on it — the other commands now follow this run.\";\n}\n","/**\n * Which database a command should talk to, decided in one place.\n *\n * Before this existed every command that needed Postgres read `DATABASE_URL`\n * for itself, which was fine while there was exactly one answer. Introducing a\n * managed database makes the question real: a project may have no\n * `DATABASE_URL` at all and still expect `rebase db push` to work, and a\n * project that *does* set one must never be quietly redirected somewhere else.\n *\n * So the rule is ordered and boring, and the order is the promise:\n *\n *   1. `--database-url <url>`   — said on this command line, wins over everything\n *   2. `DATABASE_URL` in the shell environment\n *   3. the database branch this checkout is switched to\n *   4. `DATABASE_URL` in the project's `.env`\n *   5. `--docker`, or the last `rebase dev` having run with it\n *   6. the managed PGlite database\n *\n * An explicit connection string always wins. That is the whole point of the\n * override: someone pointing Rebase at their own Postgres — a colleague's\n * staging box, a Neon branch, a container they manage — must get exactly that,\n * with no cleverness in between. The managed database is what fills the vacuum\n * when nobody has said anything, and it is the only case where the CLI picks.\n *\n * The second half of (5) is `rebase dev --docker` remembered, so that `rebase\n * db url`, `db push` and the rest reach the database a dev server is on rather\n * than start an empty PGlite beside it (`last-dev-database.ts`). It is exactly\n * as strong as the flag it stands in for, and no stronger.\n *\n * The branch at (3) is the one addition that is not an explicit connection\n * string, and it sits where it does deliberately. It has to outrank `.env` or\n * `rebase db branch switch` would silently do nothing on every project that\n * sets `DATABASE_URL` — which is every project not on the managed database.\n * It must not outrank (1) or (2), because a flag on this command line and a\n * variable in this shell are more immediate than a switch made yesterday.\n *\n * {@link resolveDevDatabase} is pure: inputs in, decision out, no filesystem\n * and no process. Reading `.env`, reading the branch pointer and starting a\n * daemon happen elsewhere, so the ordering above can be tested without any of\n * them.\n */\n\n/** Where the answer came from. Carried so diagnostics can name it. */\nexport type DevDatabaseSource =\n    /** `--database-url` on the command line. */\n    | \"flag\"\n    /** `DATABASE_URL` in the shell environment. */\n    | \"environment\"\n    /** `DATABASE_URL` in the project's `.env`. */\n    | \"env-file\"\n    /** The branch this checkout is switched to, over the base connection. */\n    | \"branch\"\n    /** `--docker`. */\n    | \"docker\"\n    /** `--docker`, on the last `rebase dev` rather than this command line. */\n    | \"last-dev\"\n    /** Nobody said anything, so the managed database fills in. */\n    | \"managed\";\n\nexport type DevDatabase =\n    | {\n        kind: \"external\";\n        /** The connection string, exactly as given. Never rewritten. */\n        url: string;\n        source: Extract<DevDatabaseSource, \"flag\" | \"environment\" | \"env-file\" | \"branch\">;\n        /** The branch name, when this checkout is switched to one. */\n        branch?: string;\n    }\n    | {\n        kind: \"docker\";\n        source: Extract<DevDatabaseSource, \"docker\" | \"last-dev\">;\n        /**\n         * The compose `db` service's connection string, derived by the caller.\n         *\n         * Null when the project has no compose file to derive one from, which\n         * is a `--docker` that cannot be honoured rather than a fallback: the\n         * caller says so instead of guessing at `localhost:5432`.\n         */\n        url: string | null;\n    }\n    | {\n        kind: \"managed\";\n        source: \"managed\";\n    };\n\nexport interface ResolveDevDatabaseInput {\n    /** `--database-url <url>`, if given. */\n    flagUrl?: string | null;\n    /** `--docker`, if given. */\n    flagDocker?: boolean;\n    /**\n     * Whether the last `rebase dev` ran with `--docker`. Followed only while\n     * the compose file still names a database, since there is none to go back\n     * to otherwise.\n     */\n    lastDevDocker?: boolean;\n    /** The shell environment. Only `DATABASE_URL` is read. */\n    env?: Record<string, string | undefined>;\n    /** Parsed `.env` from the project root. Only `DATABASE_URL` is read. */\n    envFile?: Record<string, string> | null;\n    /**\n     * The compose `db` service's connection string, when the project has one.\n     *\n     * Passed in rather than read here so this function stays pure. Only\n     * consulted for the Docker case; an explicit `DATABASE_URL` still wins.\n     */\n    composeUrl?: string | null;\n    /**\n     * The branch this checkout is switched to, already resolved to a URL.\n     *\n     * Resolved by the caller rather than here so this stays pure: deriving it\n     * needs the base connection string, which needs the `.env` this function is\n     * handed rather than reads.\n     */\n    branch?: { name: string; url: string } | null;\n}\n\n/**\n * A value that is present but empty is treated as absent.\n *\n * `DATABASE_URL=` in a `.env` is what a developer writes when they mean \"not\n * this one\" — honouring it literally would hand an empty connection string to\n * libpq and produce an error about a missing host, which explains nothing.\n */\nfunction present(value: string | undefined | null): string | null {\n    if (typeof value !== \"string\") return null;\n    const trimmed = value.trim();\n\n    return trimmed.length > 0 ? trimmed : null;\n}\n\nexport function resolveDevDatabase(input: ResolveDevDatabaseInput = {}): DevDatabase {\n    const flagUrl = present(input.flagUrl);\n    if (flagUrl) return { kind: \"external\", url: flagUrl, source: \"flag\" };\n\n    const fromEnvironment = present(input.env?.DATABASE_URL);\n    if (fromEnvironment) return { kind: \"external\", url: fromEnvironment, source: \"environment\" };\n\n    // Above `.env`, below anything said explicitly — see the ordering note at\n    // the top of this file.\n    const fromBranch = present(input.branch?.url);\n    if (fromBranch && input.branch) {\n        return { kind: \"external\", url: fromBranch, source: \"branch\", branch: input.branch.name };\n    }\n\n    const fromEnvFile = present(input.envFile?.DATABASE_URL);\n    if (fromEnvFile) return { kind: \"external\", url: fromEnvFile, source: \"env-file\" };\n\n    // Only consulted once every explicit connection string is exhausted: asking\n    // for Docker is a choice about *how to get* a database, not which one, so a\n    // DATABASE_URL that already names one outranks it.\n    if (input.flagDocker) {\n        return { kind: \"docker\", source: \"docker\", url: present(input.composeUrl) };\n    }\n    const composeUrl = present(input.composeUrl);\n    if (input.lastDevDocker && composeUrl) {\n        return { kind: \"docker\", source: \"last-dev\", url: composeUrl };\n    }\n\n    return { kind: \"managed\", source: \"managed\" };\n}\n\n/**\n * The line to print when `--docker` was typed and a connection string outranked\n * it, or null when it was not typed or was what this command used.\n *\n * The order stays as documented: asking for Docker says how to get a database,\n * and a `DATABASE_URL` that already names one wins. But a flag on this command\n * line that changes nothing without a word reads as a flag that worked. Only the\n * typed flag is reported — the last `rebase dev --docker` standing in for it is\n * a default, and losing to `.env` is what a default does.\n */\nexport function outrankedDockerFlagNotice(database: DevDatabase, flagDocker: boolean | undefined): string | null {\n    if (!flagDocker || database.kind !== \"external\") return null;\n    const ignored = \"--docker is ignored:\";\n    switch (database.source) {\n        case \"flag\":\n            return `${ignored} --database-url outranks it.`;\n        case \"environment\":\n            return `${ignored} DATABASE_URL in the environment outranks it. Unset it to use Postgres in Docker.`;\n        case \"branch\":\n            return `${ignored} branch \"${database.branch}\" (rebase db branch switch) outranks it. ` +\n                \"`rebase db branch switch --off` returns to the database in .env.\";\n        case \"env-file\":\n            return `${ignored} DATABASE_URL in .env outranks it. Comment that line out to use Postgres in Docker.`;\n    }\n}\n\n/** One line for the startup banner, naming both the database and why. */\nexport function describeDevDatabase(database: DevDatabase): string {\n    switch (database.kind) {\n        case \"external\":\n            switch (database.source) {\n                case \"flag\":\n                    return \"your database (--database-url)\";\n                case \"environment\":\n                    return \"your database (DATABASE_URL in the environment)\";\n                case \"env-file\":\n                    return \"your database (DATABASE_URL in .env)\";\n                case \"branch\":\n                    return `branch \"${database.branch}\" (rebase db branch switch)`;\n            }\n            break;\n        case \"docker\":\n            return database.source === \"last-dev\"\n                ? \"Postgres in Docker, as the last `rebase dev --docker` did\"\n                : \"Postgres in Docker\";\n        case \"managed\":\n            return \"the managed development database (PGlite)\";\n    }\n\n    // Unreachable while the union is exhaustive; kept so a future variant fails\n    // loudly in review rather than printing \"undefined\" to a user.\n    throw new Error(`Unhandled dev database: ${JSON.stringify(database)}`);\n}\n","/**\n * The one place a command asks \"which database, and how do I reach it?\".\n *\n * Every command that touches Postgres — `dev`, and the whole `db` namespace\n * through the driver plugin — goes through {@link prepareDatabaseEnv}. It\n * resolves the ordering in `resolve.ts`, starts the managed database if that is\n * what the ordering chose, and hands back the environment additions the child\n * process needs.\n *\n * Two things it deliberately does *not* do:\n *\n * - **It never overwrites an existing `DATABASE_URL`.** When the developer has\n *   named a database, the returned environment is empty and the child inherits\n *   exactly what it would have inherited before this feature existed. A\n *   migration must never be redirected away from the database its author meant.\n *\n * - **It never starts anything for a command that is not going to connect.**\n *   `--help` and argument errors are handled by the caller before this is\n *   reached, because booting a Postgres to print usage would be absurd.\n */\n\nimport fs from \"fs\";\nimport path from \"path\";\n\nimport { composeDatabaseUrl } from \"../utils/dev-preflight\";\nimport { findProjectRoot, readEnvFile } from \"../utils/project\";\nimport { Refusal } from \"../utils/refusal\";\nimport { resourceEnvSuffix } from \"@rebasepro/types\";\nimport { branchUrl, databaseNameOf, readActiveBranch } from \"./branch-pointer\";\nimport { readLastDevDocker } from \"./last-dev-database\";\nimport { MANAGED_LIMITATIONS, MANAGED_POOL_MAX } from \"./constraints\";\nimport { ensureManagedDatabase } from \"./daemon\";\nimport { type DevDatabase, describeDevDatabase, outrankedDockerFlagNotice, resolveDevDatabase } from \"./resolve\";\n\nexport interface PrepareOptions {\n    /** `--database-url <url>`. */\n    flagUrl?: string | null;\n    /** `--docker`. */\n    flagDocker?: boolean;\n    /**\n     * Follow the database the last `rebase dev` ran on (`last-dev-database.ts`).\n     * On by default; `rebase dev` itself turns it off, because its own flags are\n     * the choice being recorded.\n     */\n    followLastDev?: boolean;\n    /** Suppress the \"starting…\" progress line. */\n    quiet?: boolean;\n    /** Where human-facing lines go. Defaults to stdout via the caller. */\n    onProgress?: (message: string) => void;\n    /**\n     * Keys of the additional databases the project declares —\n     * `database(\"analytics\")` → `analytics`. On the managed path each gets\n     * its own PGlite instance and a `DATABASE_URL__<KEY>` in the child's\n     * environment, unless the developer set that variable themselves. On an\n     * external database nothing is added: whoever chose the database binds\n     * the rest of them.\n     */\n    additionalKeys?: readonly string[];\n}\n\nexport interface PreparedDatabase {\n    /** What the resolver chose, for the banner and for tests. */\n    database: DevDatabase;\n    /**\n     * Variables to add to a child process's environment.\n     *\n     * Empty for an external database: the child already has what it needs, and\n     * adding to it could only do harm.\n     */\n    env: Record<string, string>;\n    /** One line naming the database, suitable for a startup banner. */\n    description: string;\n    /** Absolute path of the managed data directory, when there is one. */\n    dataDir?: string;\n    /** True when this call started the managed database rather than finding it. */\n    startedDaemon?: boolean;\n    /** The additional managed databases, by declared key, when any were asked for. */\n    additional?: Record<string, string>;\n}\n\n/**\n * The branch this checkout is switched to, over the `DATABASE_URL` in `.env`.\n *\n * Derived rather than stored: the pointer holds a name, and the credentials\n * stay in the one place the developer wrote them. The base here is the\n * project's `.env` — a switch is a statement about *this project's* database,\n * so a `DATABASE_URL` that happens to be in the shell is not the thing being\n * branched, and it outranks the branch anyway.\n *\n * Returns null when there is no branch, and also when `.env` names no base to\n * swap the database name on. That is not the end of it: a project on Postgres\n * in Docker has no `DATABASE_URL` either, and its branch is applied over the\n * compose URL once the order has picked Docker — see\n * {@link resolveProjectDatabaseAndBranch}.\n *\n * Exported for its tests. Asserting this through {@link prepareDatabaseEnv}\n * would start a real PGlite daemon to check a decision made before any daemon\n * is involved.\n */\nexport function resolveActiveBranch(\n    projectRoot: string,\n    envFile: Record<string, string>\n): { name: string; url: string } | null {\n    const active = readActiveBranch(projectRoot);\n    if (!active) return null;\n\n    const base = envFile.DATABASE_URL?.trim();\n    if (!base) return null;\n\n    const url = branchUrl(base, active.database);\n\n    return url ? { name: active.name, url } : null;\n}\n\n/**\n * The compose `db` service's connection string for this project, or null.\n *\n * Read here rather than in `resolve.ts` so the ordering there stays pure, and\n * exported for the commands that feed the resolver themselves (`rebase status`,\n * `db branch switch`). The preflight that starts the container takes the URL\n * from {@link resolveProjectDatabase}, so it starts one only when the order\n * picks Docker.\n */\nexport function resolveComposeUrl(projectRoot: string, envFile: Record<string, string>): string | null {\n    const composePath = path.join(projectRoot, \"docker-compose.yml\");\n    if (!fs.existsSync(composePath)) return null;\n    try {\n        return composeDatabaseUrl(fs.readFileSync(composePath, \"utf8\"), envFile);\n    } catch {\n        return null;\n    }\n}\n\n/**\n * Which database a project is on, decided without starting anything.\n *\n * `resolveDevDatabase` is pure, so the answer is available to help text and to\n * a driver child alike — and neither should pay for a daemon to learn it. The\n * driver cannot work it out for itself: on the managed path `DATABASE_URL` is a\n * perfectly ordinary connection string to a Postgres on loopback, so a child\n * handed only that has no way to know that `rebase db generate` will be refused.\n *\n * Null when there is no project here, which is legal — `rebase db --help` is\n * answered outside one — and when anything at all goes wrong reading the\n * project, because help text must not fail to print over an unreadable `.env`.\n */\nexport function devDatabaseKind(projectRoot?: string | null): DevDatabase[\"kind\"] | null {\n    try {\n        const root = projectRoot ?? findProjectRoot();\n        if (!root) return null;\n\n        return resolveProjectDatabase(root).kind;\n    } catch {\n        return null;\n    }\n}\n\n/**\n * The database this command resolves to in this project, decided without\n * starting anything: the ordering in `resolve.ts`, fed from the project's\n * `.env`, its branch pointer, its compose file and the last `rebase dev`.\n *\n * The one place those four are read for a resolution, so a command that asks\n * \"which database\" and a command that then connects to it cannot disagree.\n */\nexport function resolveProjectDatabase(\n    projectRoot: string,\n    options: Pick<PrepareOptions, \"flagUrl\" | \"flagDocker\" | \"followLastDev\"> = {}\n): DevDatabase {\n    return resolveProjectDatabaseAndBranch(projectRoot, options).database;\n}\n\n/** The branch a resolution landed on. */\nexport interface ResolvedBranch {\n    /** The name the developer switched to. */\n    name: string;\n    /** The PostgreSQL database that name refers to. */\n    database: string;\n    /**\n     * The database the branch was taken from, where the branch registry lives:\n     * the one the switch swapped the name on.\n     */\n    parent: string | null;\n}\n\nexport interface ProjectDatabase {\n    database: DevDatabase;\n    /** Set when the resolved database is this checkout's branch rather than the main one. */\n    branch: ResolvedBranch | null;\n    /**\n     * The branch this checkout is switched to, when the database resolved to\n     * is the managed one — which serves exactly one database, so the switch\n     * cannot be honoured and the main database is used instead. Null otherwise.\n     */\n    ignoredBranch: string | null;\n}\n\n/**\n * {@link resolveProjectDatabase}, and which branch the answer is.\n *\n * The switch applies to whichever base the order picks, not to `.env` alone. A\n * project on Postgres in Docker — `rebase dev --docker`, remembered, with the\n * scaffold's `DATABASE_URL` left commented out, which is the setup the docs\n * point to for branching — resolved its branch to nothing, and every command\n * went on using the main database while `switch` said they had moved. So the\n * branch is applied over the compose URL whenever the order picks Docker, by a\n * typed `--docker` or the remembered one, and the answer stays Docker: that is\n * what has the container started and what `rebase dev` records.\n *\n * What outranks a switch still does. `--database-url` and a `DATABASE_URL` in\n * the shell name a database outright, and the managed database cannot hold a\n * branch at all — that last one is reported as `ignoredBranch`, so the caller\n * can say so instead of quietly using main.\n *\n * `env` is the shell environment to judge against, `process.env` by default;\n * `rebase status` passes `{}`, because it asks what *this project* is on.\n */\nexport function resolveProjectDatabaseAndBranch(\n    projectRoot: string,\n    options: Pick<PrepareOptions, \"flagUrl\" | \"flagDocker\" | \"followLastDev\"> & {\n        env?: Record<string, string | undefined>;\n    } = {}\n): ProjectDatabase {\n    const envFile = readEnvFile(projectRoot);\n    const active = readActiveBranch(projectRoot);\n\n    const database = resolveDevDatabase({\n        flagUrl: options.flagUrl,\n        flagDocker: options.flagDocker,\n        lastDevDocker: options.followLastDev !== false && readLastDevDocker(projectRoot),\n        env: options.env ?? process.env,\n        envFile,\n        branch: resolveActiveBranch(projectRoot, envFile),\n        composeUrl: resolveComposeUrl(projectRoot, envFile)\n    });\n\n    if (!active) return { database, branch: null, ignoredBranch: null };\n\n    if (database.kind === \"external\" && database.source === \"branch\") {\n        const parent = databaseNameOf(envFile.DATABASE_URL?.trim() ?? \"\");\n        return { database, branch: { ...active, parent }, ignoredBranch: null };\n    }\n\n    if (database.kind === \"docker\" && database.url) {\n        const url = branchUrl(database.url, active.database);\n        if (url) {\n            return {\n                database: { ...database, url },\n                branch: { ...active, parent: databaseNameOf(database.url) },\n                ignoredBranch: null\n            };\n        }\n    }\n\n    return { database, branch: null, ignoredBranch: database.kind === \"managed\" ? active.name : null };\n}\n\n/**\n * The variable a driver child reads {@link devDatabaseKind} from.\n *\n * One name, exported, because three commands build that child's environment and\n * a fourth reads it in another package.\n */\nexport const DEV_DATABASE_KIND_ENV = \"REBASE_DEV_DATABASE_KIND\";\n\n/**\n * The variable that tells a server started on a branch which database it was\n * branched from.\n *\n * The branch registry lives in that database, and a branch database holds\n * only a snapshot of it taken when it was copied — so a server on a branch\n * keeps its branches, and copies new ones from, the database named here. A\n * branch URL does not say which that is; only this checkout's `.env` does.\n */\nexport const BRANCH_PARENT_DATABASE_ENV = \"REBASE_BRANCH_PARENT_DATABASE\";\n\n/**\n * Resolve, start if needed, and describe the database for this command.\n *\n * `projectRoot` is where the managed database's data lives, so two projects on\n * one machine get two databases without either being told about the other.\n */\nexport async function prepareDatabaseEnv(\n    projectRoot: string,\n    options: PrepareOptions = {}\n): Promise<PreparedDatabase> {\n    const envFile = readEnvFile(projectRoot);\n    const { database, branch, ignoredBranch } = resolveProjectDatabaseAndBranch(projectRoot, options);\n\n    // A branch on Docker is still Docker to the resolver, so its own line does\n    // not name the branch; this does, because that is the database in use.\n    const description = database.kind === \"docker\" && branch\n        ? `branch \"${branch.name}\" (rebase db branch switch) on ${describeDevDatabase(database)}`\n        : describeDevDatabase(database);\n    // Where a branch lives, for the server: the registry is kept in the\n    // database the branch was taken from, and a branch URL does not say which.\n    const parentEnv: Record<string, string> = branch?.parent ? { [BRANCH_PARENT_DATABASE_ENV]: branch.parent } : {};\n\n    // Said even on a quiet command: `rebase db url --docker` is quiet, and its\n    // progress goes to stderr, which is where a flag it did not follow belongs.\n    const outranked = outrankedDockerFlagNotice(database, options.flagDocker);\n    if (outranked) options.onProgress?.(outranked);\n\n    if (ignoredBranch) {\n        options.onProgress?.(\n            `Branch \"${ignoredBranch}\" is switched to, but this uses the managed database, which has no branches, `\n            + \"so the main database is used. `--docker` (or DATABASE_URL in .env) reaches the branch; \"\n            + \"`rebase db branch switch --off` clears the switch.\"\n        );\n    }\n\n    if (database.kind === \"external\" && (database.source === \"branch\" || database.source === \"flag\")) {\n        // The two external cases that MUST be exported. `environment` and\n        // `env-file` are already somewhere the child will look — the shell it\n        // inherits, or `.env` via DOTENV_CONFIG_PATH — but a branch URL is\n        // derived here and exists nowhere else, and `--database-url` lives only\n        // in this process's argv. Without this the pointer resolves correctly\n        // and then changes nothing: `rebase db backup` on a switched checkout\n        // still reported `Database: leadgen`, and `rebase dev --database-url …`\n        // announced the database and then died on `DATABASE_URL: is required`.\n        //\n        // Safe to set: `dotenv` does not overwrite a variable that is already\n        // in the environment, so the child's own `.env` load cannot undo it.\n        // On a branch, the database it was branched from too.\n        return { database, env: { DATABASE_URL: database.url, ...parentEnv }, description };\n    }\n\n    if (database.kind === \"docker\") {\n        // Docker is the one case where nothing has named a connection string:\n        // `.env` leaves DATABASE_URL commented out, so without this the child\n        // booted with no database at all and failed on the message a project\n        // that configured nothing gets — while the container it had just been\n        // asked for was never started either.\n        if (!database.url) {\n            throw new Refusal(\n                \"--docker needs a docker-compose.yml with a db service in this project, \" +\n                \"and this one has none that names POSTGRES_USER, POSTGRES_DB and a published port. \" +\n                \"Set DATABASE_URL in .env to point at the database you mean instead.\"\n            );\n        }\n        // Said every time it decides, because nothing on this command line\n        // asked for Docker: the reader should not have to remember that an\n        // earlier `rebase dev` did.\n        if (database.source === \"last-dev\") {\n            options.onProgress?.(\n                `Using ${branch ? `branch \"${branch.name}\" (${branch.database}) of ` : \"\"}Postgres in Docker, `\n                + \"as the last `rebase dev --docker` did. `rebase dev` without --docker goes back to the managed database.\"\n            );\n        }\n        return { database, env: { DATABASE_URL: database.url, ...parentEnv }, description };\n    }\n\n    if (database.kind !== \"managed\") {\n        // `environment` or `env-file`: the connection string is already in a\n        // place the child reads for itself, so this adds nothing to it.\n        return { database, env: {}, description };\n    }\n\n    // Only the keys nobody bound by hand. A developer who set\n    // DATABASE_URL__ANALYTICS to a warehouse of their own has said which\n    // database that is, and the managed one fills a vacuum, never a choice.\n    const unbound = (options.additionalKeys ?? []).filter((key) => {\n        const name = `DATABASE_URL${resourceEnvSuffix(key)}`;\n        return !process.env[name] && !envFile[name];\n    });\n\n    const managed = await ensureManagedDatabase(projectRoot, {\n        quiet: options.quiet,\n        onProgress: options.onProgress,\n        additionalKeys: unbound\n    });\n\n    const additionalEnv: Record<string, string> = {};\n    for (const [key, url] of Object.entries(managed.additional)) {\n        additionalEnv[`DATABASE_URL${resourceEnvSuffix(key)}`] = url;\n    }\n\n    return {\n        database,\n        description,\n        dataDir: managed.dataDir,\n        startedDaemon: managed.started,\n        additional: managed.additional,\n        env: {\n            DATABASE_URL: managed.url,\n            // PGlite is one session behind a multiplexer: two pooled clients in\n            // overlapping transactions deadlock there. This is the ceiling that\n            // turns that into ordinary queueing — see `constraints.ts`.\n            REBASE_DB_POOL_MAX: String(MANAGED_POOL_MAX),\n            ...additionalEnv\n        }\n    };\n}\n\n/**\n * The lines to print about a managed database, in the order to print them.\n *\n * Returned rather than printed so the caller decides where they go — `dev` has\n * a banner, `db push` has a single line above its own output — and so a test can\n * assert on them without capturing a stream.\n */\nexport function managedNotices(prepared: PreparedDatabase): string[] {\n    if (prepared.database.kind !== \"managed\") return [];\n\n    const lines = [`Using ${prepared.description}.`];\n    if (prepared.dataDir) lines.push(`Data: ${prepared.dataDir}`);\n    for (const key of Object.keys(prepared.additional ?? {})) {\n        lines.push(`Also serving database \"${key}\" as DATABASE_URL${resourceEnvSuffix(key)}`);\n    }\n\n    // Stated every time rather than discovered. A developer who does not know\n    // requests are serialized here will read a concurrency difference as a bug\n    // in their own code.\n    for (const limitation of MANAGED_LIMITATIONS) {\n        lines.push(`${limitation.summary} ${limitation.remedy}`);\n    }\n    lines.push(\"To use your own Postgres instead, set DATABASE_URL in .env.\");\n\n    return lines;\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAuCA,SAAgB,kBAAkB,aAA6B;CAC3D,OAAO,KAAK,KAAK,aAAa,WAAW,aAAa;AAC1D;AAmBA,SAAgB,mBAAmB,MAAsB;CACrD,OAAO,MAAsB;AACjC;;AAGA,SAAgB,iBAAiB,aAA0C;CACvE,IAAI;EACA,MAAM,MAAM,GAAG,aAAa,kBAAkB,WAAW,GAAG,OAAO;EACnE,MAAM,SAAS,KAAK,MAAM,GAAG;EAC7B,IAAI,OAAO,OAAO,SAAS,YAAY,OAAO,OAAO,aAAa,UAAU,OAAO;EACnF,IAAI,CAAC,OAAO,QAAQ,CAAC,OAAO,UAAU,OAAO;EAE7C,OAAO;GAAE,MAAM,OAAO;GAAM,UAAU,OAAO;EAAS;CAC1D,QAAQ;EAIJ,OAAO;CACX;AACJ;AAEA,SAAgB,kBAAkB,aAAqB,QAA4B;CAC/E,MAAM,OAAO,kBAAkB,WAAW;CAC1C,GAAG,UAAU,KAAK,QAAQ,IAAI,GAAG,EAAE,WAAW,KAAK,CAAC;CACpD,GAAG,cAAc,MAAM,GAAG,KAAK,UAAU,QAAQ,MAAM,CAAC,EAAE,KAAK,OAAO;AAC1E;;AAGA,SAAgB,kBAAkB,aAA2B;CACzD,GAAG,OAAO,kBAAkB,WAAW,GAAG,EAAE,OAAO,KAAK,CAAC;AAC7D;;;;;;;;;;;;AAaA,SAAgB,UAAU,SAAiB,UAAiC;CACxE,IAAI;EACA,MAAM,MAAM,IAAI,IAAI,OAAO;EAG3B,IAAI,WAAW,IAAI;EAEnB,OAAO,IAAI,SAAS;CACxB,QAAQ;EACJ,OAAO;CACX;AACJ;;AAGA,SAAgB,eAAe,kBAAyC;CACpE,IAAI;EAGA,OAFa,IAAI,IAAI,gBAAgB,CAAC,CAAC,SAAS,QAAQ,OAAO,EAExD,KAAQ;CACnB,QAAQ;EACJ,OAAO;CACX;AACJ;;;;;;;;;;;;;;;;;;;;;;;ACnGA,SAAgB,oBAAoB,aAA6B;CAC7D,OAAO,KAAK,KAAK,aAAa,WAAW,mBAAmB;AAChE;;AAGA,SAAgB,kBAAkB,aAA8B;CAC5D,IAAI;EACA,MAAM,SAAkB,KAAK,MAAM,GAAG,aAAa,oBAAoB,WAAW,GAAG,MAAM,CAAC;EAC5F,OAAO,OAAO,WAAW,YAAY,WAAW,QAAQ,UAAU,UAAU,OAAO,SAAS;CAChG,QAAQ;EAEJ,OAAO;CACX;AACJ;;;;;;;;;;;;;AAoBA,SAAgB,sBACZ,aACA,MACA,MAAkB,CAAC,GACU;CAC7B,MAAM,WAAW,kBAAkB,WAAW,IAAI,WAAW;CAC7D,IAAI,IAAI,cAAc,SAAS,UAAU,OAAO,EAAE,SAAS;CAC3D,MAAM,OAAO,oBAAoB,WAAW;CAC5C,IAAI;EACA,IAAI,SAAS,UAAU;GACnB,GAAG,UAAU,KAAK,QAAQ,IAAI,GAAG,EAAE,WAAW,KAAK,CAAC;GACpD,GAAG,cAAc,MAAM,GAAG,KAAK,UAAU;IAAE,MAAM;IAAU,6BAAY,IAAI,KAAK,EAAA,CAAE,YAAY;GAAE,GAAG,MAAM,CAAC,EAAE,GAAG;EACnH,OACI,GAAG,OAAO,MAAM,EAAE,OAAO,KAAK,CAAC;CAEvC,QAAQ,CAER;CAEA,OAAO,EAAE,SAAS;AACtB;;;;;;;;;AAUA,SAAgB,sBAAsB,UAA2B,MAA2B,MAAkB,CAAC,GAAkB;CAC7H,IAAI,aAAa,YAAY,SAAS,YAAY,IAAI,YAAY,OAAO;CAEzE,OAAO;AAEX;;;;;;;;;;AC8BA,SAAS,QAAQ,OAAiD;CAC9D,IAAI,OAAO,UAAU,UAAU,OAAO;CACtC,MAAM,UAAU,MAAM,KAAK;CAE3B,OAAO,QAAQ,SAAS,IAAI,UAAU;AAC1C;AAEA,SAAgB,mBAAmB,QAAiC,CAAC,GAAgB;CACjF,MAAM,UAAU,QAAQ,MAAM,OAAO;CACrC,IAAI,SAAS,OAAO;EAAE,MAAM;EAAY,KAAK;EAAS,QAAQ;CAAO;CAErE,MAAM,kBAAkB,QAAQ,MAAM,KAAK,YAAY;CACvD,IAAI,iBAAiB,OAAO;EAAE,MAAM;EAAY,KAAK;EAAiB,QAAQ;CAAc;CAI5F,MAAM,aAAa,QAAQ,MAAM,QAAQ,GAAG;CAC5C,IAAI,cAAc,MAAM,QACpB,OAAO;EAAE,MAAM;EAAY,KAAK;EAAY,QAAQ;EAAU,QAAQ,MAAM,OAAO;CAAK;CAG5F,MAAM,cAAc,QAAQ,MAAM,SAAS,YAAY;CACvD,IAAI,aAAa,OAAO;EAAE,MAAM;EAAY,KAAK;EAAa,QAAQ;CAAW;CAKjF,IAAI,MAAM,YACN,OAAO;EAAE,MAAM;EAAU,QAAQ;EAAU,KAAK,QAAQ,MAAM,UAAU;CAAE;CAE9E,MAAM,aAAa,QAAQ,MAAM,UAAU;CAC3C,IAAI,MAAM,iBAAiB,YACvB,OAAO;EAAE,MAAM;EAAU,QAAQ;EAAY,KAAK;CAAW;CAGjE,OAAO;EAAE,MAAM;EAAW,QAAQ;CAAU;AAChD;;;;;;;;;;;AAYA,SAAgB,0BAA0B,UAAuB,YAAgD;CAC7G,IAAI,CAAC,cAAc,SAAS,SAAS,YAAY,OAAO;CACxD,MAAM,UAAU;CAChB,QAAQ,SAAS,QAAjB;EACI,KAAK,QACD,OAAO,GAAG,QAAQ;EACtB,KAAK,eACD,OAAO,GAAG,QAAQ;EACtB,KAAK,UACD,OAAO,GAAG,QAAQ,WAAW,SAAS,OAAO;EAEjD,KAAK,YACD,OAAO,GAAG,QAAQ;CAC1B;AACJ;;AAGA,SAAgB,oBAAoB,UAA+B;CAC/D,QAAQ,SAAS,MAAjB;EACI,KAAK;GACD,QAAQ,SAAS,QAAjB;IACI,KAAK,QACD,OAAO;IACX,KAAK,eACD,OAAO;IACX,KAAK,YACD,OAAO;IACX,KAAK,UACD,OAAO,WAAW,SAAS,OAAO;GAC1C;GACA;EACJ,KAAK,UACD,OAAO,SAAS,WAAW,aACrB,8DACA;EACV,KAAK,WACD,OAAO;CACf;CAIA,MAAM,IAAI,MAAM,2BAA2B,KAAK,UAAU,QAAQ,GAAG;AACzE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;ACnHA,SAAgB,oBACZ,aACA,SACoC;CACpC,MAAM,SAAS,iBAAiB,WAAW;CAC3C,IAAI,CAAC,QAAQ,OAAO;CAEpB,MAAM,OAAO,QAAQ,cAAc,KAAK;CACxC,IAAI,CAAC,MAAM,OAAO;CAElB,MAAM,MAAM,UAAU,MAAM,OAAO,QAAQ;CAE3C,OAAO,MAAM;EAAE,MAAM,OAAO;EAAM;CAAI,IAAI;AAC9C;;;;;;;;;;AAWA,SAAgB,kBAAkB,aAAqB,SAAgD;CACnG,MAAM,cAAc,KAAK,KAAK,aAAa,oBAAoB;CAC/D,IAAI,CAAC,GAAG,WAAW,WAAW,GAAG,OAAO;CACxC,IAAI;EACA,OAAO,mBAAmB,GAAG,aAAa,aAAa,MAAM,GAAG,OAAO;CAC3E,QAAQ;EACJ,OAAO;CACX;AACJ;;;;;;;;;;;;;;AAeA,SAAgB,gBAAgB,aAAyD;CACrF,IAAI;EACA,MAAM,OAAO,eAAe,gBAAgB;EAC5C,IAAI,CAAC,MAAM,OAAO;EAElB,OAAO,uBAAuB,IAAI,CAAC,CAAC;CACxC,QAAQ;EACJ,OAAO;CACX;AACJ;;;;;;;;;AAUA,SAAgB,uBACZ,aACA,UAA4E,CAAC,GAClE;CACX,OAAO,gCAAgC,aAAa,OAAO,CAAC,CAAC;AACjE;;;;;;;;;;;;;;;;;;;;;AA+CA,SAAgB,gCACZ,aACA,UAEI,CAAC,GACU;CACf,MAAM,UAAU,YAAY,WAAW;CACvC,MAAM,SAAS,iBAAiB,WAAW;CAE3C,MAAM,WAAW,mBAAmB;EAChC,SAAS,QAAQ;EACjB,YAAY,QAAQ;EACpB,eAAe,QAAQ,kBAAkB,SAAS,kBAAkB,WAAW;EAC/E,KAAK,QAAQ,OAAO,QAAQ;EAC5B;EACA,QAAQ,oBAAoB,aAAa,OAAO;EAChD,YAAY,kBAAkB,aAAa,OAAO;CACtD,CAAC;CAED,IAAI,CAAC,QAAQ,OAAO;EAAE;EAAU,QAAQ;EAAM,eAAe;CAAK;CAElE,IAAI,SAAS,SAAS,cAAc,SAAS,WAAW,UAAU;EAC9D,MAAM,SAAS,eAAe,QAAQ,cAAc,KAAK,KAAK,EAAE;EAChE,OAAO;GAAE;GAAU,QAAQ;IAAE,GAAG;IAAQ;GAAO;GAAG,eAAe;EAAK;CAC1E;CAEA,IAAI,SAAS,SAAS,YAAY,SAAS,KAAK;EAC5C,MAAM,MAAM,UAAU,SAAS,KAAK,OAAO,QAAQ;EACnD,IAAI,KACA,OAAO;GACH,UAAU;IAAE,GAAG;IAAU;GAAI;GAC7B,QAAQ;IAAE,GAAG;IAAQ,QAAQ,eAAe,SAAS,GAAG;GAAE;GAC1D,eAAe;EACnB;CAER;CAEA,OAAO;EAAE;EAAU,QAAQ;EAAM,eAAe,SAAS,SAAS,YAAY,OAAO,OAAO;CAAK;AACrG;;;;;;;AAQA,IAAa,wBAAwB;;;;;;;;;;AAWrC,IAAa,6BAA6B;;;;;;;AAQ1C,eAAsB,mBAClB,aACA,UAA0B,CAAC,GACF;CACzB,MAAM,UAAU,YAAY,WAAW;CACvC,MAAM,EAAE,UAAU,QAAQ,kBAAkB,gCAAgC,aAAa,OAAO;CAIhG,MAAM,cAAc,SAAS,SAAS,YAAY,SAC5C,WAAW,OAAO,KAAK,iCAAiC,oBAAoB,QAAQ,MACpF,oBAAoB,QAAQ;CAGlC,MAAM,YAAoC,QAAQ,SAAS,GAAG,6BAA6B,OAAO,OAAO,IAAI,CAAC;CAI9G,MAAM,YAAY,0BAA0B,UAAU,QAAQ,UAAU;CACxE,IAAI,WAAW,QAAQ,aAAa,SAAS;CAE7C,IAAI,eACA,QAAQ,aACJ,WAAW,cAAc,2NAG7B;CAGJ,IAAI,SAAS,SAAS,eAAe,SAAS,WAAW,YAAY,SAAS,WAAW,SAarF,OAAO;EAAE;EAAU,KAAK;GAAE,cAAc,SAAS;GAAK,GAAG;EAAU;EAAG;CAAY;CAGtF,IAAI,SAAS,SAAS,UAAU;EAM5B,IAAI,CAAC,SAAS,KACV,MAAM,IAAI,QACN,8NAGJ;EAKJ,IAAI,SAAS,WAAW,YACpB,QAAQ,aACJ,SAAS,SAAS,WAAW,OAAO,KAAK,KAAK,OAAO,SAAS,SAAS,GAAG,gIAE9E;EAEJ,OAAO;GAAE;GAAU,KAAK;IAAE,cAAc,SAAS;IAAK,GAAG;GAAU;GAAG;EAAY;CACtF;CAEA,IAAI,SAAS,SAAS,WAGlB,OAAO;EAAE;EAAU,KAAK,CAAC;EAAG;CAAY;CAM5C,MAAM,WAAW,QAAQ,kBAAkB,CAAC,EAAA,CAAG,QAAQ,QAAQ;EAC3D,MAAM,OAAO,eAAe,kBAAkB,GAAG;EACjD,OAAO,CAAC,QAAQ,IAAI,SAAS,CAAC,QAAQ;CAC1C,CAAC;CAED,MAAM,UAAU,MAAM,sBAAsB,aAAa;EACrD,OAAO,QAAQ;EACf,YAAY,QAAQ;EACpB,gBAAgB;CACpB,CAAC;CAED,MAAM,gBAAwC,CAAC;CAC/C,KAAK,MAAM,CAAC,KAAK,QAAQ,OAAO,QAAQ,QAAQ,UAAU,GACtD,cAAc,eAAe,kBAAkB,GAAG,OAAO;CAG7D,OAAO;EACH;EACA;EACA,SAAS,QAAQ;EACjB,eAAe,QAAQ;EACvB,YAAY,QAAQ;EACpB,KAAK;GACD,cAAc,QAAQ;GAItB,oBAAoB,OAAA,CAAuB;GAC3C,GAAG;EACP;CACJ;AACJ;;;;;;;;AASA,SAAgB,eAAe,UAAsC;CACjE,IAAI,SAAS,SAAS,SAAS,WAAW,OAAO,CAAC;CAElD,MAAM,QAAQ,CAAC,SAAS,SAAS,YAAY,EAAE;CAC/C,IAAI,SAAS,SAAS,MAAM,KAAK,SAAS,SAAS,SAAS;CAC5D,KAAK,MAAM,OAAO,OAAO,KAAK,SAAS,cAAc,CAAC,CAAC,GACnD,MAAM,KAAK,0BAA0B,IAAI,mBAAmB,kBAAkB,GAAG,GAAG;CAMxF,KAAK,MAAM,cAAc,qBACrB,MAAM,KAAK,GAAG,WAAW,QAAQ,GAAG,WAAW,QAAQ;CAE3D,MAAM,KAAK,6DAA6D;CAExE,OAAO;AACX"}
+{"version":3,"file":"prepare-CTw9NEkh.js","names":[],"sources":["../src/dev-db/branch-pointer.ts","../src/dev-db/last-dev-database.ts","../src/dev-db/resolve.ts","../src/dev-db/prepare.ts"],"sourcesContent":["/**\n * Which database branch this checkout is working on.\n *\n * `rebase db branch create` made a full copy of the database in about a second\n * and then stopped one step short of being a feature: there was no `switch`, no\n * `--branch` on `rebase dev`, and nothing wrote the branch anywhere a command\n * would read it. The only way to *use* a branch was to hand-edit\n * `DATABASE_URL`, and the documentation claimed otherwise — \"the CLI updates\n * your local development configuration\" — which it did not; the `.env` was\n * byte-identical afterwards.\n *\n * This is that missing step, and the shape of it is chosen to avoid three\n * things:\n *\n * 1. **It does not touch `.env`.** That file holds secrets, comments and the\n *    developer's own ordering, and a command that rewrites it in place will\n *    eventually lose something that was not its business. The branch is\n *    recorded beside the other per-checkout state in `.rebase/`, which is\n *    already gitignored — a branch is a fact about one machine, never about\n *    the project.\n *\n * 2. **It stores a name, not a connection string.** The credentials stay in\n *    exactly one place; the URL is derived by swapping the database name on\n *    the base one at resolution time. A stored URL would be a second copy of\n *    the password, and would go stale the moment `.env` changed.\n *\n * 3. **It does not outrank an explicit instruction.** `--database-url` and a\n *    `DATABASE_URL` in the shell are more immediate and more specific than a\n *    switch made yesterday, so they still win. The pointer sits directly above\n *    the project's `.env`: it is a deliberate, persistent choice, and `.env` is\n *    the project default it is meant to override. Anything less and `switch`\n *    would silently do nothing on every project that sets `DATABASE_URL` —\n *    which is every project not using the managed database.\n */\n\nimport fs from \"fs\";\nimport path from \"path\";\n\n/** Where the pointer lives, next to the rest of the per-checkout state. */\nexport function branchPointerPath(projectRoot: string): string {\n    return path.join(projectRoot, \".rebase\", \"branch.json\");\n}\n\nexport interface ActiveBranch {\n    /** The name the developer typed. */\n    name: string;\n    /** The PostgreSQL database that name refers to. */\n    database: string;\n}\n\n/**\n * The prefix `BranchService` puts on every branch database.\n *\n * Duplicated from the driver rather than imported because the CLI must answer\n * \"which database\" without loading a database driver — `rebase dev` reads this\n * before it knows which plugin the project uses. It is covered by a test that\n * fails if the driver's prefix moves.\n */\nexport const BRANCH_DB_PREFIX = \"rb_\";\n\nexport function branchDatabaseName(name: string): string {\n    return `${BRANCH_DB_PREFIX}${name}`;\n}\n\n/** Read the active branch, or null when the checkout is on the main database. */\nexport function readActiveBranch(projectRoot: string): ActiveBranch | null {\n    try {\n        const raw = fs.readFileSync(branchPointerPath(projectRoot), \"utf-8\");\n        const parsed = JSON.parse(raw) as Partial<ActiveBranch>;\n        if (typeof parsed.name !== \"string\" || typeof parsed.database !== \"string\") return null;\n        if (!parsed.name || !parsed.database) return null;\n\n        return { name: parsed.name, database: parsed.database };\n    } catch {\n        // Absent is the common case and is not an error. A corrupt file is\n        // treated the same way: the answer is \"no branch\", which is the state\n        // the developer can always get back to with `branch switch --off`.\n        return null;\n    }\n}\n\nexport function writeActiveBranch(projectRoot: string, branch: ActiveBranch): void {\n    const file = branchPointerPath(projectRoot);\n    fs.mkdirSync(path.dirname(file), { recursive: true });\n    fs.writeFileSync(file, `${JSON.stringify(branch, null, 2)}\\n`, \"utf-8\");\n}\n\n/** Return to the main database. Absent is success — this is idempotent. */\nexport function clearActiveBranch(projectRoot: string): void {\n    fs.rmSync(branchPointerPath(projectRoot), { force: true });\n}\n\n/**\n * The base connection string with its database swapped for the branch's.\n *\n * Everything else is carried across untouched — credentials, host, port, and\n * the query string, which is load-bearing here: `?sslmode=disable` is what a\n * local Docker Postgres needs, and dropping it turns a switch into a TLS error\n * that says nothing about branches.\n *\n * Returns null for a connection string that cannot be parsed, so the caller can\n * say so plainly rather than emitting a mangled URL that fails later.\n */\nexport function branchUrl(baseUrl: string, database: string): string | null {\n    try {\n        const url = new URL(baseUrl);\n        // `pathname` keeps its leading slash; a URL with no database at all\n        // still gets one, which is what connecting to a named branch means.\n        url.pathname = `/${database}`;\n\n        return url.toString();\n    } catch {\n        return null;\n    }\n}\n\n/** The database name in a connection string, for reporting what you are on. */\nexport function databaseNameOf(connectionString: string): string | null {\n    try {\n        const name = new URL(connectionString).pathname.replace(/^\\//, \"\");\n\n        return name || null;\n    } catch {\n        return null;\n    }\n}\n","/**\n * Which database the last `rebase dev` ran on, when nothing else records it.\n *\n * `rebase dev --docker` is a choice made on one command line, and every other\n * command resolved without it: while dev served the project from its compose\n * database, `rebase db url` printed a managed PGlite URL — and started that\n * daemon to print it — and `db push`, `console` and the rest would have used\n * the same empty database. Nothing said the two disagreed.\n *\n * So `rebase dev` records its choice here, and the other commands follow it\n * (`resolve.ts`, rule 5). Only Docker is recorded. Every other database is\n * already somewhere each command reads — `--database-url` aside, which is a\n * choice for one command line — or is the default, so the record holds\n * `docker` exactly when the last `rebase dev` ran on it, and any other start\n * of `rebase dev` removes it. That is also the way back: `rebase dev` without\n * `--docker`.\n *\n * Beside the branch pointer in `.rebase/`, which is gitignored: which database\n * this checkout last ran on is a fact about one machine, never the project.\n */\n\nimport fs from \"fs\";\nimport path from \"path\";\n\nimport type { DevDatabase } from \"./resolve\";\n\nexport function lastDevDatabasePath(projectRoot: string): string {\n    return path.join(projectRoot, \".rebase\", \"dev-database.json\");\n}\n\n/** Whether the last `rebase dev` ran on the compose database. */\nexport function readLastDevDocker(projectRoot: string): boolean {\n    try {\n        const parsed: unknown = JSON.parse(fs.readFileSync(lastDevDatabasePath(projectRoot), \"utf8\"));\n        return typeof parsed === \"object\" && parsed !== null && \"kind\" in parsed && parsed.kind === \"docker\";\n    } catch {\n        // Absent is the common case; unreadable has the same answer.\n        return false;\n    }\n}\n\n/** What this `rebase dev` was asked for, beside what it runs on. */\nexport interface LastDevRun {\n    /** `--docker` was on this command line. */\n    dockerFlag?: boolean;\n}\n\n/**\n * Record what this `rebase dev` runs on, and say what the last one ran on.\n *\n * A run that asked for Docker and was outranked by a connection string leaves\n * the record as it was. It is not on Docker, so it records nothing; but it is\n * not a run without `--docker` either, which is what forgets the record. The\n * reader was told to comment the `.env` line out to reach Docker, and once\n * they have, the other commands follow Docker as they did before.\n *\n * Best effort: a checkout whose `.rebase/` cannot be written still runs, and\n * the other commands then resolve as they did before this existed.\n */\nexport function recordLastDevDatabase(\n    projectRoot: string,\n    kind: DevDatabase[\"kind\"],\n    run: LastDevRun = {}\n): { previous: \"docker\" | null } {\n    const previous = readLastDevDocker(projectRoot) ? \"docker\" : null;\n    if (run.dockerFlag && kind !== \"docker\") return { previous };\n    const file = lastDevDatabasePath(projectRoot);\n    try {\n        if (kind === \"docker\") {\n            fs.mkdirSync(path.dirname(file), { recursive: true });\n            fs.writeFileSync(file, `${JSON.stringify({ kind: \"docker\", recordedAt: new Date().toISOString() }, null, 2)}\\n`);\n        } else {\n            fs.rmSync(file, { force: true });\n        }\n    } catch {\n        // See above: not worth failing a dev start over.\n    }\n\n    return { previous };\n}\n\n/**\n * What `rebase dev` says when it leaves the Docker database the last run used.\n *\n * Said rather than left to be noticed: the data a developer was working with\n * is in the container, and the managed database this run is on is a different,\n * possibly empty, one. Not said to a run that asked for Docker: the line that\n * says `--docker` was ignored, and what outranked it, is the one that applies.\n */\nexport function lastDevDatabaseNotice(previous: \"docker\" | null, kind: DevDatabase[\"kind\"], run: LastDevRun = {}): string | null {\n    if (previous !== \"docker\" || kind === \"docker\" || run.dockerFlag) return null;\n\n    return \"The last `rebase dev` ran on Postgres in Docker; this one does not. \"\n        + \"Pass --docker to stay on it — the other commands now follow this run.\";\n}\n","/**\n * Which database a command should talk to, decided in one place.\n *\n * Before this existed every command that needed Postgres read `DATABASE_URL`\n * for itself, which was fine while there was exactly one answer. Introducing a\n * managed database makes the question real: a project may have no\n * `DATABASE_URL` at all and still expect `rebase db push` to work, and a\n * project that *does* set one must never be quietly redirected somewhere else.\n *\n * So the rule is ordered and boring, and the order is the promise:\n *\n *   1. `--database-url <url>`   — said on this command line, wins over everything\n *   2. `DATABASE_URL` in the shell environment\n *   3. the database branch this checkout is switched to\n *   4. `DATABASE_URL` in the project's `.env`\n *   5. `--docker`, or the last `rebase dev` having run with it\n *   6. the managed PGlite database\n *\n * An explicit connection string always wins. That is the whole point of the\n * override: someone pointing Rebase at their own Postgres — a colleague's\n * staging box, a Neon branch, a container they manage — must get exactly that,\n * with no cleverness in between. The managed database is what fills the vacuum\n * when nobody has said anything, and it is the only case where the CLI picks.\n *\n * The second half of (5) is `rebase dev --docker` remembered, so that `rebase\n * db url`, `db push` and the rest reach the database a dev server is on rather\n * than start an empty PGlite beside it (`last-dev-database.ts`). It is exactly\n * as strong as the flag it stands in for, and no stronger.\n *\n * The branch at (3) is the one addition that is not an explicit connection\n * string, and it sits where it does deliberately. It has to outrank `.env` or\n * `rebase db branch switch` would silently do nothing on every project that\n * sets `DATABASE_URL` — which is every project not on the managed database.\n * It must not outrank (1) or (2), because a flag on this command line and a\n * variable in this shell are more immediate than a switch made yesterday.\n *\n * {@link resolveDevDatabase} is pure: inputs in, decision out, no filesystem\n * and no process. Reading `.env`, reading the branch pointer and starting a\n * daemon happen elsewhere, so the ordering above can be tested without any of\n * them.\n */\n\n/** Where the answer came from. Carried so diagnostics can name it. */\nexport type DevDatabaseSource =\n    /** `--database-url` on the command line. */\n    | \"flag\"\n    /** `DATABASE_URL` in the shell environment. */\n    | \"environment\"\n    /** `DATABASE_URL` in the project's `.env`. */\n    | \"env-file\"\n    /** The branch this checkout is switched to, over the base connection. */\n    | \"branch\"\n    /** `--docker`. */\n    | \"docker\"\n    /** `--docker`, on the last `rebase dev` rather than this command line. */\n    | \"last-dev\"\n    /** Nobody said anything, so the managed database fills in. */\n    | \"managed\";\n\nexport type DevDatabase =\n    | {\n        kind: \"external\";\n        /** The connection string, exactly as given. Never rewritten. */\n        url: string;\n        source: Extract<DevDatabaseSource, \"flag\" | \"environment\" | \"env-file\" | \"branch\">;\n        /** The branch name, when this checkout is switched to one. */\n        branch?: string;\n    }\n    | {\n        kind: \"docker\";\n        source: Extract<DevDatabaseSource, \"docker\" | \"last-dev\">;\n        /**\n         * The compose `db` service's connection string, derived by the caller.\n         *\n         * Null when the project has no compose file to derive one from, which\n         * is a `--docker` that cannot be honoured rather than a fallback: the\n         * caller says so instead of guessing at `localhost:5432`.\n         */\n        url: string | null;\n    }\n    | {\n        kind: \"managed\";\n        source: \"managed\";\n    };\n\nexport interface ResolveDevDatabaseInput {\n    /** `--database-url <url>`, if given. */\n    flagUrl?: string | null;\n    /** `--docker`, if given. */\n    flagDocker?: boolean;\n    /**\n     * Whether the last `rebase dev` ran with `--docker`. Followed only while\n     * the compose file still names a database, since there is none to go back\n     * to otherwise.\n     */\n    lastDevDocker?: boolean;\n    /** The shell environment. Only `DATABASE_URL` is read. */\n    env?: Record<string, string | undefined>;\n    /** Parsed `.env` from the project root. Only `DATABASE_URL` is read. */\n    envFile?: Record<string, string> | null;\n    /**\n     * The compose `db` service's connection string, when the project has one.\n     *\n     * Passed in rather than read here so this function stays pure. Only\n     * consulted for the Docker case; an explicit `DATABASE_URL` still wins.\n     */\n    composeUrl?: string | null;\n    /**\n     * The branch this checkout is switched to, already resolved to a URL.\n     *\n     * Resolved by the caller rather than here so this stays pure: deriving it\n     * needs the base connection string, which needs the `.env` this function is\n     * handed rather than reads.\n     */\n    branch?: { name: string; url: string } | null;\n}\n\n/**\n * A value that is present but empty is treated as absent.\n *\n * `DATABASE_URL=` in a `.env` is what a developer writes when they mean \"not\n * this one\" — honouring it literally would hand an empty connection string to\n * libpq and produce an error about a missing host, which explains nothing.\n */\nfunction present(value: string | undefined | null): string | null {\n    if (typeof value !== \"string\") return null;\n    const trimmed = value.trim();\n\n    return trimmed.length > 0 ? trimmed : null;\n}\n\nexport function resolveDevDatabase(input: ResolveDevDatabaseInput = {}): DevDatabase {\n    const flagUrl = present(input.flagUrl);\n    if (flagUrl) return { kind: \"external\", url: flagUrl, source: \"flag\" };\n\n    const fromEnvironment = present(input.env?.DATABASE_URL);\n    if (fromEnvironment) return { kind: \"external\", url: fromEnvironment, source: \"environment\" };\n\n    // Above `.env`, below anything said explicitly — see the ordering note at\n    // the top of this file.\n    const fromBranch = present(input.branch?.url);\n    if (fromBranch && input.branch) {\n        return { kind: \"external\", url: fromBranch, source: \"branch\", branch: input.branch.name };\n    }\n\n    const fromEnvFile = present(input.envFile?.DATABASE_URL);\n    if (fromEnvFile) return { kind: \"external\", url: fromEnvFile, source: \"env-file\" };\n\n    // Only consulted once every explicit connection string is exhausted: asking\n    // for Docker is a choice about *how to get* a database, not which one, so a\n    // DATABASE_URL that already names one outranks it.\n    if (input.flagDocker) {\n        return { kind: \"docker\", source: \"docker\", url: present(input.composeUrl) };\n    }\n    const composeUrl = present(input.composeUrl);\n    if (input.lastDevDocker && composeUrl) {\n        return { kind: \"docker\", source: \"last-dev\", url: composeUrl };\n    }\n\n    return { kind: \"managed\", source: \"managed\" };\n}\n\n/**\n * The line to print when `--docker` was typed and a connection string outranked\n * it, or null when it was not typed or was what this command used.\n *\n * The order stays as documented: asking for Docker says how to get a database,\n * and a `DATABASE_URL` that already names one wins. But a flag on this command\n * line that changes nothing without a word reads as a flag that worked. Only the\n * typed flag is reported — the last `rebase dev --docker` standing in for it is\n * a default, and losing to `.env` is what a default does.\n */\nexport function outrankedDockerFlagNotice(database: DevDatabase, flagDocker: boolean | undefined): string | null {\n    if (!flagDocker || database.kind !== \"external\") return null;\n    const ignored = \"--docker is ignored:\";\n    switch (database.source) {\n        case \"flag\":\n            return `${ignored} --database-url outranks it.`;\n        case \"environment\":\n            return `${ignored} DATABASE_URL in the environment outranks it. Unset it to use Postgres in Docker.`;\n        case \"branch\":\n            return `${ignored} branch \"${database.branch}\" (rebase db branch switch) outranks it. ` +\n                \"`rebase db branch switch --off` returns to the database in .env.\";\n        case \"env-file\":\n            return `${ignored} DATABASE_URL in .env outranks it. Comment that line out to use Postgres in Docker.`;\n    }\n}\n\n/** One line for the startup banner, naming both the database and why. */\nexport function describeDevDatabase(database: DevDatabase): string {\n    switch (database.kind) {\n        case \"external\":\n            switch (database.source) {\n                case \"flag\":\n                    return \"your database (--database-url)\";\n                case \"environment\":\n                    return \"your database (DATABASE_URL in the environment)\";\n                case \"env-file\":\n                    return \"your database (DATABASE_URL in .env)\";\n                case \"branch\":\n                    return `branch \"${database.branch}\" (rebase db branch switch)`;\n            }\n            break;\n        case \"docker\":\n            return database.source === \"last-dev\"\n                ? \"Postgres in Docker, as the last `rebase dev --docker` did\"\n                : \"Postgres in Docker\";\n        case \"managed\":\n            return \"the managed development database (PGlite)\";\n    }\n\n    // Unreachable while the union is exhaustive; kept so a future variant fails\n    // loudly in review rather than printing \"undefined\" to a user.\n    throw new Error(`Unhandled dev database: ${JSON.stringify(database)}`);\n}\n","/**\n * The one place a command asks \"which database, and how do I reach it?\".\n *\n * Every command that touches Postgres — `dev`, and the whole `db` namespace\n * through the driver plugin — goes through {@link prepareDatabaseEnv}. It\n * resolves the ordering in `resolve.ts`, starts the managed database if that is\n * what the ordering chose, and hands back the environment additions the child\n * process needs.\n *\n * Two things it deliberately does *not* do:\n *\n * - **It never overwrites an existing `DATABASE_URL`.** When the developer has\n *   named a database, the returned environment is empty and the child inherits\n *   exactly what it would have inherited before this feature existed. A\n *   migration must never be redirected away from the database its author meant.\n *\n * - **It never starts anything for a command that is not going to connect.**\n *   `--help` and argument errors are handled by the caller before this is\n *   reached, because booting a Postgres to print usage would be absurd.\n */\n\nimport fs from \"fs\";\nimport path from \"path\";\n\nimport { composeDatabaseUrl } from \"../utils/dev-preflight\";\nimport { findProjectRoot, readEnvFile } from \"../utils/project\";\nimport { Refusal } from \"../utils/refusal\";\nimport { resourceEnvSuffix } from \"@rebasepro/types\";\nimport { branchUrl, databaseNameOf, readActiveBranch } from \"./branch-pointer\";\nimport { readLastDevDocker } from \"./last-dev-database\";\nimport { MANAGED_LIMITATIONS, MANAGED_POOL_MAX } from \"./constraints\";\nimport { ensureManagedDatabase } from \"./daemon\";\nimport { type DevDatabase, describeDevDatabase, outrankedDockerFlagNotice, resolveDevDatabase } from \"./resolve\";\n\nexport interface PrepareOptions {\n    /** `--database-url <url>`. */\n    flagUrl?: string | null;\n    /** `--docker`. */\n    flagDocker?: boolean;\n    /**\n     * Follow the database the last `rebase dev` ran on (`last-dev-database.ts`).\n     * On by default; `rebase dev` itself turns it off, because its own flags are\n     * the choice being recorded.\n     */\n    followLastDev?: boolean;\n    /** Suppress the \"starting…\" progress line. */\n    quiet?: boolean;\n    /** Where human-facing lines go. Defaults to stdout via the caller. */\n    onProgress?: (message: string) => void;\n    /**\n     * Keys of the additional databases the project declares —\n     * `database(\"analytics\")` → `analytics`. On the managed path each gets\n     * its own PGlite instance and a `DATABASE_URL__<KEY>` in the child's\n     * environment, unless the developer set that variable themselves. On an\n     * external database nothing is added: whoever chose the database binds\n     * the rest of them.\n     */\n    additionalKeys?: readonly string[];\n}\n\nexport interface PreparedDatabase {\n    /** What the resolver chose, for the banner and for tests. */\n    database: DevDatabase;\n    /**\n     * Variables to add to a child process's environment.\n     *\n     * Empty for an external database: the child already has what it needs, and\n     * adding to it could only do harm.\n     */\n    env: Record<string, string>;\n    /** One line naming the database, suitable for a startup banner. */\n    description: string;\n    /** Absolute path of the managed data directory, when there is one. */\n    dataDir?: string;\n    /** True when this call started the managed database rather than finding it. */\n    startedDaemon?: boolean;\n    /** The additional managed databases, by declared key, when any were asked for. */\n    additional?: Record<string, string>;\n}\n\n/**\n * The branch this checkout is switched to, over the `DATABASE_URL` in `.env`.\n *\n * Derived rather than stored: the pointer holds a name, and the credentials\n * stay in the one place the developer wrote them. The base here is the\n * project's `.env` — a switch is a statement about *this project's* database,\n * so a `DATABASE_URL` that happens to be in the shell is not the thing being\n * branched, and it outranks the branch anyway.\n *\n * Returns null when there is no branch, and also when `.env` names no base to\n * swap the database name on. That is not the end of it: a project on Postgres\n * in Docker has no `DATABASE_URL` either, and its branch is applied over the\n * compose URL once the order has picked Docker — see\n * {@link resolveProjectDatabaseAndBranch}.\n *\n * Exported for its tests. Asserting this through {@link prepareDatabaseEnv}\n * would start a real PGlite daemon to check a decision made before any daemon\n * is involved.\n */\nexport function resolveActiveBranch(\n    projectRoot: string,\n    envFile: Record<string, string>\n): { name: string; url: string } | null {\n    const active = readActiveBranch(projectRoot);\n    if (!active) return null;\n\n    const base = envFile.DATABASE_URL?.trim();\n    if (!base) return null;\n\n    const url = branchUrl(base, active.database);\n\n    return url ? { name: active.name, url } : null;\n}\n\n/**\n * The compose `db` service's connection string for this project, or null.\n *\n * Read here rather than in `resolve.ts` so the ordering there stays pure, and\n * exported for the commands that feed the resolver themselves (`rebase status`,\n * `db branch switch`). The preflight that starts the container takes the URL\n * from {@link resolveProjectDatabase}, so it starts one only when the order\n * picks Docker.\n */\nexport function resolveComposeUrl(projectRoot: string, envFile: Record<string, string>): string | null {\n    const composePath = path.join(projectRoot, \"docker-compose.yml\");\n    if (!fs.existsSync(composePath)) return null;\n    try {\n        return composeDatabaseUrl(fs.readFileSync(composePath, \"utf8\"), envFile);\n    } catch {\n        return null;\n    }\n}\n\n/**\n * Which database a project is on, decided without starting anything.\n *\n * `resolveDevDatabase` is pure, so the answer is available to help text and to\n * a driver child alike — and neither should pay for a daemon to learn it. The\n * driver cannot work it out for itself: on the managed path `DATABASE_URL` is a\n * perfectly ordinary connection string to a Postgres on loopback, so a child\n * handed only that has no way to know that `rebase db generate` will be refused.\n *\n * Null when there is no project here, which is legal — `rebase db --help` is\n * answered outside one — and when anything at all goes wrong reading the\n * project, because help text must not fail to print over an unreadable `.env`.\n */\nexport function devDatabaseKind(projectRoot?: string | null): DevDatabase[\"kind\"] | null {\n    try {\n        const root = projectRoot ?? findProjectRoot();\n        if (!root) return null;\n\n        return resolveProjectDatabase(root).kind;\n    } catch {\n        return null;\n    }\n}\n\n/**\n * The database this command resolves to in this project, decided without\n * starting anything: the ordering in `resolve.ts`, fed from the project's\n * `.env`, its branch pointer, its compose file and the last `rebase dev`.\n *\n * The one place those four are read for a resolution, so a command that asks\n * \"which database\" and a command that then connects to it cannot disagree.\n */\nexport function resolveProjectDatabase(\n    projectRoot: string,\n    options: Pick<PrepareOptions, \"flagUrl\" | \"flagDocker\" | \"followLastDev\"> = {}\n): DevDatabase {\n    return resolveProjectDatabaseAndBranch(projectRoot, options).database;\n}\n\n/** The branch a resolution landed on. */\nexport interface ResolvedBranch {\n    /** The name the developer switched to. */\n    name: string;\n    /** The PostgreSQL database that name refers to. */\n    database: string;\n    /**\n     * The database the branch was taken from, where the branch registry lives:\n     * the one the switch swapped the name on.\n     */\n    parent: string | null;\n}\n\nexport interface ProjectDatabase {\n    database: DevDatabase;\n    /** Set when the resolved database is this checkout's branch rather than the main one. */\n    branch: ResolvedBranch | null;\n    /**\n     * The branch this checkout is switched to, when the database resolved to\n     * is the managed one — which serves exactly one database, so the switch\n     * cannot be honoured and the main database is used instead. Null otherwise.\n     */\n    ignoredBranch: string | null;\n}\n\n/**\n * {@link resolveProjectDatabase}, and which branch the answer is.\n *\n * The switch applies to whichever base the order picks, not to `.env` alone. A\n * project on Postgres in Docker — `rebase dev --docker`, remembered, with the\n * scaffold's `DATABASE_URL` left commented out, which is the setup the docs\n * point to for branching — resolved its branch to nothing, and every command\n * went on using the main database while `switch` said they had moved. So the\n * branch is applied over the compose URL whenever the order picks Docker, by a\n * typed `--docker` or the remembered one, and the answer stays Docker: that is\n * what has the container started and what `rebase dev` records.\n *\n * What outranks a switch still does. `--database-url` and a `DATABASE_URL` in\n * the shell name a database outright, and the managed database cannot hold a\n * branch at all — that last one is reported as `ignoredBranch`, so the caller\n * can say so instead of quietly using main.\n *\n * `env` is the shell environment to judge against, `process.env` by default;\n * `rebase status` passes `{}`, because it asks what *this project* is on.\n */\nexport function resolveProjectDatabaseAndBranch(\n    projectRoot: string,\n    options: Pick<PrepareOptions, \"flagUrl\" | \"flagDocker\" | \"followLastDev\"> & {\n        env?: Record<string, string | undefined>;\n    } = {}\n): ProjectDatabase {\n    const envFile = readEnvFile(projectRoot);\n    const active = readActiveBranch(projectRoot);\n\n    const database = resolveDevDatabase({\n        flagUrl: options.flagUrl,\n        flagDocker: options.flagDocker,\n        lastDevDocker: options.followLastDev !== false && readLastDevDocker(projectRoot),\n        env: options.env ?? process.env,\n        envFile,\n        branch: resolveActiveBranch(projectRoot, envFile),\n        composeUrl: resolveComposeUrl(projectRoot, envFile)\n    });\n\n    if (!active) return { database, branch: null, ignoredBranch: null };\n\n    if (database.kind === \"external\" && database.source === \"branch\") {\n        const parent = databaseNameOf(envFile.DATABASE_URL?.trim() ?? \"\");\n        return { database, branch: { ...active, parent }, ignoredBranch: null };\n    }\n\n    if (database.kind === \"docker\" && database.url) {\n        const url = branchUrl(database.url, active.database);\n        if (url) {\n            return {\n                database: { ...database, url },\n                branch: { ...active, parent: databaseNameOf(database.url) },\n                ignoredBranch: null\n            };\n        }\n    }\n\n    return { database, branch: null, ignoredBranch: database.kind === \"managed\" ? active.name : null };\n}\n\n/**\n * The variable a driver child reads {@link devDatabaseKind} from.\n *\n * One name, exported, because three commands build that child's environment and\n * a fourth reads it in another package.\n */\nexport const DEV_DATABASE_KIND_ENV = \"REBASE_DEV_DATABASE_KIND\";\n\n/**\n * The variable that tells a server started on a branch which database it was\n * branched from.\n *\n * The branch registry lives in that database, and a branch database holds\n * only a snapshot of it taken when it was copied — so a server on a branch\n * keeps its branches, and copies new ones from, the database named here. A\n * branch URL does not say which that is; only this checkout's `.env` does.\n */\nexport const BRANCH_PARENT_DATABASE_ENV = \"REBASE_BRANCH_PARENT_DATABASE\";\n\n/**\n * Resolve, start if needed, and describe the database for this command.\n *\n * `projectRoot` is where the managed database's data lives, so two projects on\n * one machine get two databases without either being told about the other.\n */\nexport async function prepareDatabaseEnv(\n    projectRoot: string,\n    options: PrepareOptions = {}\n): Promise<PreparedDatabase> {\n    const envFile = readEnvFile(projectRoot);\n    const { database, branch, ignoredBranch } = resolveProjectDatabaseAndBranch(projectRoot, options);\n\n    // A branch on Docker is still Docker to the resolver, so its own line does\n    // not name the branch; this does, because that is the database in use.\n    const description = database.kind === \"docker\" && branch\n        ? `branch \"${branch.name}\" (rebase db branch switch) on ${describeDevDatabase(database)}`\n        : describeDevDatabase(database);\n    // Where a branch lives, for the server: the registry is kept in the\n    // database the branch was taken from, and a branch URL does not say which.\n    const parentEnv: Record<string, string> = branch?.parent ? { [BRANCH_PARENT_DATABASE_ENV]: branch.parent } : {};\n\n    // Said even on a quiet command: `rebase db url --docker` is quiet, and its\n    // progress goes to stderr, which is where a flag it did not follow belongs.\n    const outranked = outrankedDockerFlagNotice(database, options.flagDocker);\n    if (outranked) options.onProgress?.(outranked);\n\n    if (ignoredBranch) {\n        options.onProgress?.(\n            `Branch \"${ignoredBranch}\" is switched to, but this uses the managed database, which has no branches, `\n            + \"so the main database is used. `--docker` (or DATABASE_URL in .env) reaches the branch; \"\n            + \"`rebase db branch switch --off` clears the switch.\"\n        );\n    }\n\n    if (database.kind === \"external\" && (database.source === \"branch\" || database.source === \"flag\")) {\n        // The two external cases that MUST be exported. `environment` and\n        // `env-file` are already somewhere the child will look — the shell it\n        // inherits, or `.env` via DOTENV_CONFIG_PATH — but a branch URL is\n        // derived here and exists nowhere else, and `--database-url` lives only\n        // in this process's argv. Without this the pointer resolves correctly\n        // and then changes nothing: `rebase db backup` on a switched checkout\n        // still reported `Database: leadgen`, and `rebase dev --database-url …`\n        // announced the database and then died on `DATABASE_URL: is required`.\n        //\n        // Safe to set: `dotenv` does not overwrite a variable that is already\n        // in the environment, so the child's own `.env` load cannot undo it.\n        // On a branch, the database it was branched from too.\n        return { database, env: { DATABASE_URL: database.url, ...parentEnv }, description };\n    }\n\n    if (database.kind === \"docker\") {\n        // Docker is the one case where nothing has named a connection string:\n        // `.env` leaves DATABASE_URL commented out, so without this the child\n        // booted with no database at all and failed on the message a project\n        // that configured nothing gets — while the container it had just been\n        // asked for was never started either.\n        if (!database.url) {\n            throw new Refusal(\n                \"--docker needs a docker-compose.yml with a db service in this project, \" +\n                \"and this one has none that names POSTGRES_USER, POSTGRES_DB and a published port. \" +\n                \"Set DATABASE_URL in .env to point at the database you mean instead.\"\n            );\n        }\n        // Said every time it decides, because nothing on this command line\n        // asked for Docker: the reader should not have to remember that an\n        // earlier `rebase dev` did.\n        if (database.source === \"last-dev\") {\n            options.onProgress?.(\n                `Using ${branch ? `branch \"${branch.name}\" (${branch.database}) of ` : \"\"}Postgres in Docker, `\n                + \"as the last `rebase dev --docker` did. `rebase dev` without --docker goes back to the managed database.\"\n            );\n        }\n        return { database, env: { DATABASE_URL: database.url, ...parentEnv }, description };\n    }\n\n    if (database.kind !== \"managed\") {\n        // `environment` or `env-file`: the connection string is already in a\n        // place the child reads for itself, so this adds nothing to it.\n        return { database, env: {}, description };\n    }\n\n    // Only the keys nobody bound by hand. A developer who set\n    // DATABASE_URL__ANALYTICS to a warehouse of their own has said which\n    // database that is, and the managed one fills a vacuum, never a choice.\n    const unbound = (options.additionalKeys ?? []).filter((key) => {\n        const name = `DATABASE_URL${resourceEnvSuffix(key)}`;\n        return !process.env[name] && !envFile[name];\n    });\n\n    const managed = await ensureManagedDatabase(projectRoot, {\n        quiet: options.quiet,\n        onProgress: options.onProgress,\n        additionalKeys: unbound\n    });\n\n    const additionalEnv: Record<string, string> = {};\n    for (const [key, url] of Object.entries(managed.additional)) {\n        additionalEnv[`DATABASE_URL${resourceEnvSuffix(key)}`] = url;\n    }\n\n    return {\n        database,\n        description,\n        dataDir: managed.dataDir,\n        startedDaemon: managed.started,\n        additional: managed.additional,\n        env: {\n            DATABASE_URL: managed.url,\n            // PGlite is one session behind a multiplexer: two pooled clients in\n            // overlapping transactions deadlock there. This is the ceiling that\n            // turns that into ordinary queueing — see `constraints.ts`.\n            REBASE_DB_POOL_MAX: String(MANAGED_POOL_MAX),\n            ...additionalEnv\n        }\n    };\n}\n\n/**\n * The lines to print about a managed database, in the order to print them.\n *\n * Returned rather than printed so the caller decides where they go — `dev` has\n * a banner, `db push` has a single line above its own output — and so a test can\n * assert on them without capturing a stream.\n */\nexport function managedNotices(prepared: PreparedDatabase): string[] {\n    if (prepared.database.kind !== \"managed\") return [];\n\n    const lines = [`Using ${prepared.description}.`];\n    if (prepared.dataDir) lines.push(`Data: ${prepared.dataDir}`);\n    for (const key of Object.keys(prepared.additional ?? {})) {\n        lines.push(`Also serving database \"${key}\" as DATABASE_URL${resourceEnvSuffix(key)}`);\n    }\n\n    // Stated every time rather than discovered. A developer who does not know\n    // requests are serialized here will read a concurrency difference as a bug\n    // in their own code.\n    for (const limitation of MANAGED_LIMITATIONS) {\n        lines.push(`${limitation.summary} ${limitation.remedy}`);\n    }\n    lines.push(\"To use your own Postgres instead, set DATABASE_URL in .env.\");\n\n    return lines;\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAuCA,SAAgB,kBAAkB,aAA6B;CAC3D,OAAO,KAAK,KAAK,aAAa,WAAW,aAAa;AAC1D;AAmBA,SAAgB,mBAAmB,MAAsB;CACrD,OAAO,MAAsB;AACjC;;AAGA,SAAgB,iBAAiB,aAA0C;CACvE,IAAI;EACA,MAAM,MAAM,GAAG,aAAa,kBAAkB,WAAW,GAAG,OAAO;EACnE,MAAM,SAAS,KAAK,MAAM,GAAG;EAC7B,IAAI,OAAO,OAAO,SAAS,YAAY,OAAO,OAAO,aAAa,UAAU,OAAO;EACnF,IAAI,CAAC,OAAO,QAAQ,CAAC,OAAO,UAAU,OAAO;EAE7C,OAAO;GAAE,MAAM,OAAO;GAAM,UAAU,OAAO;EAAS;CAC1D,QAAQ;EAIJ,OAAO;CACX;AACJ;AAEA,SAAgB,kBAAkB,aAAqB,QAA4B;CAC/E,MAAM,OAAO,kBAAkB,WAAW;CAC1C,GAAG,UAAU,KAAK,QAAQ,IAAI,GAAG,EAAE,WAAW,KAAK,CAAC;CACpD,GAAG,cAAc,MAAM,GAAG,KAAK,UAAU,QAAQ,MAAM,CAAC,EAAE,KAAK,OAAO;AAC1E;;AAGA,SAAgB,kBAAkB,aAA2B;CACzD,GAAG,OAAO,kBAAkB,WAAW,GAAG,EAAE,OAAO,KAAK,CAAC;AAC7D;;;;;;;;;;;;AAaA,SAAgB,UAAU,SAAiB,UAAiC;CACxE,IAAI;EACA,MAAM,MAAM,IAAI,IAAI,OAAO;EAG3B,IAAI,WAAW,IAAI;EAEnB,OAAO,IAAI,SAAS;CACxB,QAAQ;EACJ,OAAO;CACX;AACJ;;AAGA,SAAgB,eAAe,kBAAyC;CACpE,IAAI;EAGA,OAFa,IAAI,IAAI,gBAAgB,CAAC,CAAC,SAAS,QAAQ,OAAO,EAExD,KAAQ;CACnB,QAAQ;EACJ,OAAO;CACX;AACJ;;;;;;;;;;;;;;;;;;;;;;;ACnGA,SAAgB,oBAAoB,aAA6B;CAC7D,OAAO,KAAK,KAAK,aAAa,WAAW,mBAAmB;AAChE;;AAGA,SAAgB,kBAAkB,aAA8B;CAC5D,IAAI;EACA,MAAM,SAAkB,KAAK,MAAM,GAAG,aAAa,oBAAoB,WAAW,GAAG,MAAM,CAAC;EAC5F,OAAO,OAAO,WAAW,YAAY,WAAW,QAAQ,UAAU,UAAU,OAAO,SAAS;CAChG,QAAQ;EAEJ,OAAO;CACX;AACJ;;;;;;;;;;;;;AAoBA,SAAgB,sBACZ,aACA,MACA,MAAkB,CAAC,GACU;CAC7B,MAAM,WAAW,kBAAkB,WAAW,IAAI,WAAW;CAC7D,IAAI,IAAI,cAAc,SAAS,UAAU,OAAO,EAAE,SAAS;CAC3D,MAAM,OAAO,oBAAoB,WAAW;CAC5C,IAAI;EACA,IAAI,SAAS,UAAU;GACnB,GAAG,UAAU,KAAK,QAAQ,IAAI,GAAG,EAAE,WAAW,KAAK,CAAC;GACpD,GAAG,cAAc,MAAM,GAAG,KAAK,UAAU;IAAE,MAAM;IAAU,6BAAY,IAAI,KAAK,EAAA,CAAE,YAAY;GAAE,GAAG,MAAM,CAAC,EAAE,GAAG;EACnH,OACI,GAAG,OAAO,MAAM,EAAE,OAAO,KAAK,CAAC;CAEvC,QAAQ,CAER;CAEA,OAAO,EAAE,SAAS;AACtB;;;;;;;;;AAUA,SAAgB,sBAAsB,UAA2B,MAA2B,MAAkB,CAAC,GAAkB;CAC7H,IAAI,aAAa,YAAY,SAAS,YAAY,IAAI,YAAY,OAAO;CAEzE,OAAO;AAEX;;;;;;;;;;AC8BA,SAAS,QAAQ,OAAiD;CAC9D,IAAI,OAAO,UAAU,UAAU,OAAO;CACtC,MAAM,UAAU,MAAM,KAAK;CAE3B,OAAO,QAAQ,SAAS,IAAI,UAAU;AAC1C;AAEA,SAAgB,mBAAmB,QAAiC,CAAC,GAAgB;CACjF,MAAM,UAAU,QAAQ,MAAM,OAAO;CACrC,IAAI,SAAS,OAAO;EAAE,MAAM;EAAY,KAAK;EAAS,QAAQ;CAAO;CAErE,MAAM,kBAAkB,QAAQ,MAAM,KAAK,YAAY;CACvD,IAAI,iBAAiB,OAAO;EAAE,MAAM;EAAY,KAAK;EAAiB,QAAQ;CAAc;CAI5F,MAAM,aAAa,QAAQ,MAAM,QAAQ,GAAG;CAC5C,IAAI,cAAc,MAAM,QACpB,OAAO;EAAE,MAAM;EAAY,KAAK;EAAY,QAAQ;EAAU,QAAQ,MAAM,OAAO;CAAK;CAG5F,MAAM,cAAc,QAAQ,MAAM,SAAS,YAAY;CACvD,IAAI,aAAa,OAAO;EAAE,MAAM;EAAY,KAAK;EAAa,QAAQ;CAAW;CAKjF,IAAI,MAAM,YACN,OAAO;EAAE,MAAM;EAAU,QAAQ;EAAU,KAAK,QAAQ,MAAM,UAAU;CAAE;CAE9E,MAAM,aAAa,QAAQ,MAAM,UAAU;CAC3C,IAAI,MAAM,iBAAiB,YACvB,OAAO;EAAE,MAAM;EAAU,QAAQ;EAAY,KAAK;CAAW;CAGjE,OAAO;EAAE,MAAM;EAAW,QAAQ;CAAU;AAChD;;;;;;;;;;;AAYA,SAAgB,0BAA0B,UAAuB,YAAgD;CAC7G,IAAI,CAAC,cAAc,SAAS,SAAS,YAAY,OAAO;CACxD,MAAM,UAAU;CAChB,QAAQ,SAAS,QAAjB;EACI,KAAK,QACD,OAAO,GAAG,QAAQ;EACtB,KAAK,eACD,OAAO,GAAG,QAAQ;EACtB,KAAK,UACD,OAAO,GAAG,QAAQ,WAAW,SAAS,OAAO;EAEjD,KAAK,YACD,OAAO,GAAG,QAAQ;CAC1B;AACJ;;AAGA,SAAgB,oBAAoB,UAA+B;CAC/D,QAAQ,SAAS,MAAjB;EACI,KAAK;GACD,QAAQ,SAAS,QAAjB;IACI,KAAK,QACD,OAAO;IACX,KAAK,eACD,OAAO;IACX,KAAK,YACD,OAAO;IACX,KAAK,UACD,OAAO,WAAW,SAAS,OAAO;GAC1C;GACA;EACJ,KAAK,UACD,OAAO,SAAS,WAAW,aACrB,8DACA;EACV,KAAK,WACD,OAAO;CACf;CAIA,MAAM,IAAI,MAAM,2BAA2B,KAAK,UAAU,QAAQ,GAAG;AACzE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;ACnHA,SAAgB,oBACZ,aACA,SACoC;CACpC,MAAM,SAAS,iBAAiB,WAAW;CAC3C,IAAI,CAAC,QAAQ,OAAO;CAEpB,MAAM,OAAO,QAAQ,cAAc,KAAK;CACxC,IAAI,CAAC,MAAM,OAAO;CAElB,MAAM,MAAM,UAAU,MAAM,OAAO,QAAQ;CAE3C,OAAO,MAAM;EAAE,MAAM,OAAO;EAAM;CAAI,IAAI;AAC9C;;;;;;;;;;AAWA,SAAgB,kBAAkB,aAAqB,SAAgD;CACnG,MAAM,cAAc,KAAK,KAAK,aAAa,oBAAoB;CAC/D,IAAI,CAAC,GAAG,WAAW,WAAW,GAAG,OAAO;CACxC,IAAI;EACA,OAAO,mBAAmB,GAAG,aAAa,aAAa,MAAM,GAAG,OAAO;CAC3E,QAAQ;EACJ,OAAO;CACX;AACJ;;;;;;;;;;;;;;AAeA,SAAgB,gBAAgB,aAAyD;CACrF,IAAI;EACA,MAAM,OAAO,eAAe,gBAAgB;EAC5C,IAAI,CAAC,MAAM,OAAO;EAElB,OAAO,uBAAuB,IAAI,CAAC,CAAC;CACxC,QAAQ;EACJ,OAAO;CACX;AACJ;;;;;;;;;AAUA,SAAgB,uBACZ,aACA,UAA4E,CAAC,GAClE;CACX,OAAO,gCAAgC,aAAa,OAAO,CAAC,CAAC;AACjE;;;;;;;;;;;;;;;;;;;;;AA+CA,SAAgB,gCACZ,aACA,UAEI,CAAC,GACU;CACf,MAAM,UAAU,YAAY,WAAW;CACvC,MAAM,SAAS,iBAAiB,WAAW;CAE3C,MAAM,WAAW,mBAAmB;EAChC,SAAS,QAAQ;EACjB,YAAY,QAAQ;EACpB,eAAe,QAAQ,kBAAkB,SAAS,kBAAkB,WAAW;EAC/E,KAAK,QAAQ,OAAO,QAAQ;EAC5B;EACA,QAAQ,oBAAoB,aAAa,OAAO;EAChD,YAAY,kBAAkB,aAAa,OAAO;CACtD,CAAC;CAED,IAAI,CAAC,QAAQ,OAAO;EAAE;EAAU,QAAQ;EAAM,eAAe;CAAK;CAElE,IAAI,SAAS,SAAS,cAAc,SAAS,WAAW,UAAU;EAC9D,MAAM,SAAS,eAAe,QAAQ,cAAc,KAAK,KAAK,EAAE;EAChE,OAAO;GAAE;GAAU,QAAQ;IAAE,GAAG;IAAQ;GAAO;GAAG,eAAe;EAAK;CAC1E;CAEA,IAAI,SAAS,SAAS,YAAY,SAAS,KAAK;EAC5C,MAAM,MAAM,UAAU,SAAS,KAAK,OAAO,QAAQ;EACnD,IAAI,KACA,OAAO;GACH,UAAU;IAAE,GAAG;IAAU;GAAI;GAC7B,QAAQ;IAAE,GAAG;IAAQ,QAAQ,eAAe,SAAS,GAAG;GAAE;GAC1D,eAAe;EACnB;CAER;CAEA,OAAO;EAAE;EAAU,QAAQ;EAAM,eAAe,SAAS,SAAS,YAAY,OAAO,OAAO;CAAK;AACrG;;;;;;;AAQA,IAAa,wBAAwB;;;;;;;;;;AAWrC,IAAa,6BAA6B;;;;;;;AAQ1C,eAAsB,mBAClB,aACA,UAA0B,CAAC,GACF;CACzB,MAAM,UAAU,YAAY,WAAW;CACvC,MAAM,EAAE,UAAU,QAAQ,kBAAkB,gCAAgC,aAAa,OAAO;CAIhG,MAAM,cAAc,SAAS,SAAS,YAAY,SAC5C,WAAW,OAAO,KAAK,iCAAiC,oBAAoB,QAAQ,MACpF,oBAAoB,QAAQ;CAGlC,MAAM,YAAoC,QAAQ,SAAS,GAAG,6BAA6B,OAAO,OAAO,IAAI,CAAC;CAI9G,MAAM,YAAY,0BAA0B,UAAU,QAAQ,UAAU;CACxE,IAAI,WAAW,QAAQ,aAAa,SAAS;CAE7C,IAAI,eACA,QAAQ,aACJ,WAAW,cAAc,2NAG7B;CAGJ,IAAI,SAAS,SAAS,eAAe,SAAS,WAAW,YAAY,SAAS,WAAW,SAarF,OAAO;EAAE;EAAU,KAAK;GAAE,cAAc,SAAS;GAAK,GAAG;EAAU;EAAG;CAAY;CAGtF,IAAI,SAAS,SAAS,UAAU;EAM5B,IAAI,CAAC,SAAS,KACV,MAAM,IAAI,QACN,8NAGJ;EAKJ,IAAI,SAAS,WAAW,YACpB,QAAQ,aACJ,SAAS,SAAS,WAAW,OAAO,KAAK,KAAK,OAAO,SAAS,SAAS,GAAG,gIAE9E;EAEJ,OAAO;GAAE;GAAU,KAAK;IAAE,cAAc,SAAS;IAAK,GAAG;GAAU;GAAG;EAAY;CACtF;CAEA,IAAI,SAAS,SAAS,WAGlB,OAAO;EAAE;EAAU,KAAK,CAAC;EAAG;CAAY;CAM5C,MAAM,WAAW,QAAQ,kBAAkB,CAAC,EAAA,CAAG,QAAQ,QAAQ;EAC3D,MAAM,OAAO,eAAe,kBAAkB,GAAG;EACjD,OAAO,CAAC,QAAQ,IAAI,SAAS,CAAC,QAAQ;CAC1C,CAAC;CAED,MAAM,UAAU,MAAM,sBAAsB,aAAa;EACrD,OAAO,QAAQ;EACf,YAAY,QAAQ;EACpB,gBAAgB;CACpB,CAAC;CAED,MAAM,gBAAwC,CAAC;CAC/C,KAAK,MAAM,CAAC,KAAK,QAAQ,OAAO,QAAQ,QAAQ,UAAU,GACtD,cAAc,eAAe,kBAAkB,GAAG,OAAO;CAG7D,OAAO;EACH;EACA;EACA,SAAS,QAAQ;EACjB,eAAe,QAAQ;EACvB,YAAY,QAAQ;EACpB,KAAK;GACD,cAAc,QAAQ;GAItB,oBAAoB,OAAA,CAAuB;GAC3C,GAAG;EACP;CACJ;AACJ;;;;;;;;AASA,SAAgB,eAAe,UAAsC;CACjE,IAAI,SAAS,SAAS,SAAS,WAAW,OAAO,CAAC;CAElD,MAAM,QAAQ,CAAC,SAAS,SAAS,YAAY,EAAE;CAC/C,IAAI,SAAS,SAAS,MAAM,KAAK,SAAS,SAAS,SAAS;CAC5D,KAAK,MAAM,OAAO,OAAO,KAAK,SAAS,cAAc,CAAC,CAAC,GACnD,MAAM,KAAK,0BAA0B,IAAI,mBAAmB,kBAAkB,GAAG,GAAG;CAMxF,KAAK,MAAM,cAAc,qBACrB,MAAM,KAAK,GAAG,WAAW,QAAQ,GAAG,WAAW,QAAQ;CAE3D,MAAM,KAAK,6DAA6D;CAExE,OAAO;AACX"}