#!/usr/bin/env node
/**
 * `tagada-init [email]`
 *
 * Reachable as:
 *   - `npx -p @tagadapay/node-sdk tagada-init` (one-shot, no install)
 *   - `npx tagada-init` (after `npm i -D @tagadapay/node-sdk`)
 *   - `tagada-init`     (after a global install)
 *
 * Interactive CLI that walks a developer through provisioning a fresh
 * sandbox Tagada account in ~30 seconds:
 *
 *  1. Asks for an email (or accepts it as the first positional arg).
 *  2. POSTs `/api/public/onboarding/start` to mail a 6-digit code.
 *  3. Prompts the user to paste the code from their inbox.
 *  4. POSTs `/api/public/onboarding/verify` to provision the account.
 *  5. Writes the returned `apiKey` / `storeId` / `accountId` to a `.env`
 *     file in the current working directory (creating it if missing,
 *     appending non-conflicting keys if it exists).
 *  6. Prints next steps.
 *
 * Flags:
 *   --base-url=<url>       Override the API host (default https://api.tagada.io)
 *   --no-env               Print the values instead of writing `.env`
 *   --env-file=<path>      Custom path for the env file (default ./.env)
 *   --source=<tag>         Acquisition source override (default 'cli')
 *
 * UTM forwarding: any `--utm-foo=bar` flag, plus matching `UTM_FOO` env
 * vars, are bundled into the `utm` payload so attribution survives the
 * jump from a docs link → terminal command.
 *
 * Naming note: the package is `@tagadapay/node-sdk` (the SDK to talk to
 * the TagadaPay payment processor), but the *account* this command
 * creates is a **Tagada** account (the CRM / control plane). Hence
 * `tagada-init`, not `tagadapay-init`.
 */
export {};
//# sourceMappingURL=init.d.ts.map