@lunora/cli 1.0.0-alpha.7 → 1.0.0-alpha.71

package/dist/bin.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { runCli } from './packem_shared/COMMANDS-Bn8luojF.mjs';
+import { runCli } from './packem_shared/COMMANDS-0BD3K1pb.mjs';
 
 try {
   const code = await runCli();

package/dist/index.d.mts

@@ -1,6 +1,6 @@
 import { CodegenOptions, SchemaIR } from '@lunora/codegen';
 import '@visulima/cerebro';
-import { ensureDevVariables, ensureDevVarsExample, materializeRemoteWranglerConfig } from '@lunora/config';
+import { ensureDevVariables, ensureDevVarsExample, fillDevSecrets, materializeRemoteWranglerConfig } from '@lunora/config';
 export { REQUIRED_COMPATIBILITY_DATE, REQUIRED_FLAG, type WranglerProjectValidationOptions as WranglerValidationOptions, type WranglerValidationReport, type WranglerProjectValidationResult as WranglerValidationResult, validateWranglerProject as validateWrangler, validateWranglerConfig } from '@lunora/config';
 /** Every command name the CLI registers (drives the `CommandName` type + tests). */
 declare const COMMANDS: readonly ["init", "add", "dev", "codegen", "build", "deploy", "containers", "prepare", "link", "deployments", "logs", "run", "insights", "reset", "migrate", "export", "import", "seed", "backup", "verify", "info", "doctor", "env", "analyze", "view", "docs", "registry", "rules"];
@@ -49,6 +49,15 @@ interface PailLogger {
   success: (message: string) => void;
   warn: (message: string) => void;
 }
+/**
+* Minimal reporter shape consumed by `createPail`. We re-declare it locally
+* because `@visulima/pail`'s `reporter/*` entrypoints ship a packaging bug:
+* their `index.d.ts` re-exports `./json-reporter.d.ts` / `./pretty-reporter.d.ts`,
+* but the real declaration files are suffixed (`*.server.d.ts`). `tsc` tolerates
+* the dangling re-export, but the type-aware linter resolves `JsonReporter` /
+* `PrettyReporter` to an unresolved type. Constructing them through this typed
+* factory keeps every call site safe.
+*/
 declare const createLogger: () => Logger;
 /**
 * Logger whose every channel writes to `process.stderr`. Used by commands in
@@ -64,6 +73,12 @@ declare const createLogger: () => Logger;
 * the package barrel) stays side-effect-free.
 */
 declare const pail: PailLogger;
+/**
+* Emit a badged step line through the shared pail (the `init` flow's off-TTY
+* fallback for the create-astro-style transcript). The `message` may contain
+* newlines — `LunoraReporter` indents continuation lines under the badge so a
+* dimmed answer sits below its question.
+*/
 interface CodegenCommandOptions {
   /** Which API spec(s) to emit. Defaults to codegen's `"openapi"` when omitted. */
   apiSpec?: ApiSpec;
@@ -220,6 +235,35 @@ declare const createRecordingSpawner: (exitCode?: number) => {
   calls: RecordedSpawn[];
   spawner: Spawner;
 };
+interface SecretListRunnerResult {
+  code: number;
+  stderr: string;
+  stdout: string;
+}
+/** Runs an argv and resolves its captured output. Injected in tests. */
+type SecretListRunner = (command: string, args: ReadonlyArray<string>, cwd: string) => Promise<SecretListRunnerResult>;
+interface ListRemoteSecretsInputs {
+  cwd: string;
+  /** Cloudflare environment name (`--env`). */
+  env?: string;
+  /** Injected command runner; defaults to a real `wrangler secret list`. */
+  runner?: SecretListRunner;
+  /** Target a temporary-account deployment (`--temporary`). */
+  temporary?: boolean;
+}
+interface ListRemoteSecretsResult {
+  /** Diagnostic message when `ok` is false. */
+  error?: string;
+  /** Remote secret names (sorted), empty when none or on failure. */
+  names: ReadonlyArray<string>;
+  /** False when wrangler failed or its output could not be parsed. */
+  ok: boolean;
+}
+/**
+* Parse `wrangler secret list --format json` output into a sorted name list.
+* The payload is an array of `{ name, type }`; anything else yields `undefined`
+* so the caller can report a parse failure rather than silently returning [].
+*/
 type FetchLike = (input: string, init?: {
   body?: string;
   headers?: Record<string, string>;
@@ -312,6 +356,10 @@ interface DeployCommandOptions {
   preview?: boolean;
   /** Railpack-availability probe injected in tests. Defaults to a real `railpack --version` + `BUILDKIT_HOST` check. */
   railpackAvailable?: DockerProbe;
+  /** Confirm prompt for the missing-secret offer; injected in tests. Defaults to the TTY prompt. */
+  secretConfirm?: (message: string) => Promise<boolean>;
+  /** Remote-secret lister for the missing-secret offer; injected in tests. Defaults to `wrangler secret list`. */
+  secretLister?: (inputs: ListRemoteSecretsInputs) => Promise<ListRemoteSecretsResult>;
   skipCodegen?: boolean;
   spawner?: Spawner;
   /**
@@ -403,6 +451,34 @@ interface StudioServerHandle {
   /** The URL to open in a browser. */
   url: string;
 }
+/**
+* How the dev child runs. `wrangler` is the classic `lunora dev` stack (wrangler
+* worker + embedded studio + codegen watch) for a standalone class-C project.
+* `vite` is a project on `@lunora/vite`: the plugin already runs the worker,
+* studio, and codegen inside the Vite dev server, so `lunora dev` runs the
+* project's own dev script and gets out of the way — this also covers class-B
+* frameworks whose own dev server runs the worker in `workerd` (Astro 6 +
+* `@astrojs/cloudflare`, which embeds `@cloudflare/vite-plugin` in `astro dev`:
+* SSR + `/_lunora/*` + `ShardDO` in one process, HMR intact). `framework-worker`
+* is a class-B framework whose dev server CANNOT host the `ShardDO` Durable
+* Object (SvelteKit / Nuxt: their adapters use wrangler's `getPlatformProxy()`,
+* which runs an empty-script Miniflare and does not emulate internal DOs); there
+* `lunora dev` runs the framework's own dev server (front door, HMR, and — via
+* its `@lunora/vite` plugin — studio + codegen) AND a second `wrangler dev`
+* sidecar that owns the real `ShardDO` in `workerd`, wired via the committed
+* `wrangler.dev.jsonc`.
+*/
+type DevFlavor = "framework-worker" | "vite" | "wrangler";
+/**
+* Detect the dev flavor.
+*
+* A SvelteKit / Nuxt project needs the two-process `framework-worker` stack even
+* though it also declares `@lunora/vite` (which its framework dev server uses for
+* codegen/studio) — so the framework check comes FIRST. Everything else on
+* `@lunora/vite` (class-A frameworks + Astro + standalone Vite) delegates to the
+* project's own dev server (`vite`); a project without `@lunora/vite` is the
+* classic standalone `wrangler` stack.
+*/
 /** A running worker child the orchestrator controls: send signals, await its exit. */
 interface WorkerProcess {
   /** Resolves with the worker's exit code (1 if it failed to start). */
@@ -423,6 +499,14 @@ interface DevCommandOptions {
   ensureEnv?: typeof ensureDevVariables;
   /** Injection seam for tests — defaults to the real `.dev.vars.example` package-aware scaffolder. */
   ensureExample?: typeof ensureDevVarsExample;
+  /** Injection seam for tests — defaults to the real empty-secret/admin-token filler. */
+  fillSecrets?: typeof fillDevSecrets;
+  /** Injection seam for tests — defaults to the real free-port probe ({@link findAvailablePort}). */
+  findFreePort?: (preferred: number) => Promise<number>;
+  /** Dev flavor override (tests / callers that already detected it) — defaults to {@link detectDevFlavor}. */
+  flavor?: DevFlavor;
+  /** Injection seam for tests — defaults to the real IPv6-loopback probe ({@link hasIpv6Loopback}). */
+  hasIpv6Loopback?: () => boolean;
   logger: Logger;
   /** Injection seam for tests — defaults to the real remote-config materializer. */
   materializeRemote?: typeof materializeRemoteWranglerConfig;
@@ -457,13 +541,42 @@ interface DevRemotePlan {
 }
 interface DevCommandPlan {
   codegenEnabled: boolean;
+  /** Which stack the child runs — see {@link DevFlavor}. */
+  flavor: DevFlavor;
+  /**
+  * One-line redirect hint printed when a meta-framework is detected on the
+  * wrangler flavor: without `@lunora/vite` in the dependencies the worker
+  * still runs *inside* the framework's dev server, so the user should run
+  * their framework dev script for the full app. `undefined` for the vite
+  * flavor (`lunora dev` already runs the project's dev script there) and
+  * for a standalone project. Purely informational: the wrangler spawn runs
+  * regardless.
+  */
+  frameworkHint?: string;
+  /**
+  * True when `wrangler dev` was given `--ip 127.0.0.1` because the host has no
+  * IPv6 loopback (`::1`) — surfaced so the dev loop can note the rebind.
+  * Always `false` for the vite flavor (the plugin owns its own bind).
+  */
+  ipv4LoopbackForced: boolean;
   /** The remote-binding decision: which D1/KV/R2 bindings hit the deployed worker. */
   remote: DevRemotePlan;
+  /**
+  * The `wrangler dev` sidecar for the `framework-worker` flavor (SvelteKit /
+  * Nuxt): a second child that owns the real `ShardDO` in `workerd`, wired via
+  * the committed `wrangler.dev.jsonc`. `undefined` for every other flavor —
+  * only the two-process class-B stack has a sidecar. When present, `wrangler`
+  * (above) is the framework's own dev server (the front door / HMR) and this
+  * is the Lunora realtime plane.
+  */
+  sidecar?: SpawnDescriptor & {
+    tag: string;
+  };
   studioEnabled: boolean;
   studioPort: number;
   workerOrigin: string;
   workerPort: number;
-  /** The single child process `lunora dev` spawns: `wrangler dev`. */
+  /** The primary child `lunora dev` spawns: `wrangler dev` (wrangler flavor) or the framework/`vite dev` server (vite / framework-worker). */
   wrangler: SpawnDescriptor & {
     tag: string;
   };
@@ -477,10 +590,11 @@ interface DevCommandPlan {
 * to remote, the args stay empty and dev runs fully local.
 */
 /**
-* Plan `lunora dev`: it runs the worker via `wrangler dev` and nothing else as a
-* child process. Vite is intentionally NOT spawned — a project may not use Vite,
-* and when it does, the `@lunora/vite` plugin already runs the worker inside
-* Vite, so the user runs `vite` themselves. Pure + synchronous so it's unit-testable.
+* Plan `lunora dev`. Wrangler flavor: the worker runs via `wrangler dev` and
+* nothing else as a child process. Vite flavor (`@lunora/vite` declared): the
+* plugin already runs the worker inside the Vite dev server, so the one child
+* is the project's own dev script (`vite dev`, `astro dev`, …) and every CLI
+* sibling is disabled. Pure + synchronous so it's unit-testable.
 */
 declare const planDevCommand: (options: DevCommandOptions) => DevCommandPlan;
 /**
@@ -508,16 +622,133 @@ type PackageManagerProbe = (manager: PackageManager) => boolean;
 /** A registry item a feature can install. */
 type FeatureItem = "auth" | "auth-auth0" | "auth-clerk" | "mail";
 /** The auth-provider choices offered for `add auth` / the init auth prompt. Each value is a registry item name. */
-
+/** A single file the item scaffolds into the project. */
+interface RegistryFile {
+  /** Source path inside the item dir (e.g. `schema.ts`). */
+  from: string;
+  /** Merge strategy. `create-or-skip` writes whole files; `schema-extension` AST-merges schema.ts. */
+  merge: "create-or-skip" | "schema-extension";
+  /** Destination relative to the project root (e.g. `lunora/ratelimit/index.ts`). */
+  to: string;
+}
+/** A wrangler.jsonc binding addition. `path` is the jsonc key path; `value` the value to set. */
+interface RegistryBinding {
+  path: ReadonlyArray<string>;
+  value: unknown;
+}
+/**
+* An environment variable an item needs. Scaffolded into `.dev.vars` (Workers'
+* local-secrets file) on add — non-secrets get their `value`; secrets get an
+* empty placeholder and a reminder to run `wrangler secret put` for production.
+*/
+interface RegistryEnvVariable {
+  /** Human note on what the variable is for. */
+  description?: string;
+  /** The variable name (e.g. `RESEND_API_KEY`). */
+  name: string;
+  /** Mark as a secret: never write a value, only a placeholder, and remind about prod. Defaults to `true` when no `value` is given. */
+  secret?: boolean;
+  /** A default/example value for non-secret vars. */
+  value?: string;
+}
+/** The `registry.json` manifest shape. */
+interface RegistryManifest {
+  /** wrangler.jsonc additions (best-effort structural edits). */
+  bindings?: ReadonlyArray<RegistryBinding>;
+  /** npm deps to add to the project package.json (name → version range). */
+  deps?: Readonly<Record<string, string>>;
+  description?: string;
+  /** npm devDependencies to add to the project package.json. */
+  devDependencies?: Readonly<Record<string, string>>;
+  /** Post-install guidance printed after the item is added (per-item next steps). */
+  docs?: string;
+  /** Environment variables the item needs; scaffolded into `.dev.vars`. */
+  envVars?: ReadonlyArray<RegistryEnvVariable>;
+  files: ReadonlyArray<RegistryFile>;
+  name: string;
+  /** Other registry items this one depends on (resolved transitively, deps first). */
+  requires?: ReadonlyArray<string>;
+  /** Short human-readable label (distinct from the longer `description`). */
+  title?: string;
+}
+interface AddCommandOptions {
+  /** Bypass the `--source` safety gate (matches init). */
+  allowUnsafeSource?: boolean;
+  /** `registry build --check`: verify the index is current instead of rewriting it. */
+  check?: boolean;
+  /** Inject a confirmer for non-interactive callers / tests. */
+  confirm?: (prompt: string) => Promise<boolean>;
+  cwd?: string;
+  /** Preview the file-level changes (a content diff) and write nothing. */
+  diff?: boolean;
+  /** Print the plan and stop without writing anything. */
+  dryRun?: boolean;
+  /** Local registry root (offline / tests). Expects per-item subdirs, each with a `registry.json`. */
+  from?: string;
+  /** Emit a JSON snapshot of the plan/result. */
+  json?: boolean;
+  /** `--list`: enumerate available items instead of adding. */
+  list?: boolean;
+  logger: Logger;
+  /** Item names to add (positional args). */
+  names: ReadonlyArray<string>;
+  /** `registry build` output path for the generated catalog (defaults to the root's `index.json`). */
+  out?: string;
+  /** Force-overwrite existing files (take the incoming copy) instead of skipping/conflicting. */
+  overwrite?: boolean;
+  /** Override the git ref (branch, tag, or commit) items are fetched from (default: version-derived); appended to the `source` base when that is set. Ignored when `from` is set. */
+  ref?: string;
+  /** Override the remote registry source base (default gh:anolilab/lunora/registry). */
+  source?: string;
+  /**
+  * Customize each resolved manifest after it is loaded but before the plan is
+  * printed / reconciled — used to inject user-chosen values into otherwise
+  * static manifests (e.g. the R2 `bucket_name` the init storage prompt asks
+  * for). Applied to every item; return the manifest unchanged to leave it as-is.
+  */
+  transformManifest?: (manifest: RegistryManifest) => RegistryManifest;
+  /** Skip the package.json mutation confirmation prompt. */
+  yes?: boolean;
+}
+interface AddCommandResult {
+  /** Bindings written to wrangler.jsonc. */
+  bindings: ReadonlyArray<string>;
+  code: number;
+  /** Deps added to package.json. */
+  deps: ReadonlyArray<string>;
+  /** Files skipped because they already existed. */
+  skipped: ReadonlyArray<string>;
+  /** Files written (absolute paths). */
+  written: ReadonlyArray<string>;
+}
+/** One resolved item: its parsed manifest plus the (possibly staged) directory it lives in. */
 /**
 * A feature offered in the post-scaffold multi-select. `auth`/`email` carry a
 * sub-prompt or alias; every other value IS the registry item name applied
 * directly (`storage` → the `storage` registry item, etc.).
 */
 type StackFeature = "auth" | "backup" | "crons" | "email" | "presence" | "ratelimit" | "storage";
+/** Customize a resolved manifest before it is written (e.g. inject the chosen R2 bucket name). */
+type OfferTransformManifest = (manifest: RegistryManifest) => RegistryManifest;
+/**
+* One feature ready to apply: the registry item name(s), an optional manifest
+* transform, and a short `label` (the feature value) shown on the combined
+* progress line. Built up-front by the collectors so every prompt is answered
+* before any apply runs.
+*/
+interface FeatureApply {
+  label: string;
+  names: ReadonlyArray<string>;
+  transformManifest?: OfferTransformManifest;
+}
 interface OfferDeps {
-  /** Apply one or more registry items into the new project; resolves `true` on success. */
-  apply: (names: ReadonlyArray<string>) => Promise<boolean>;
+  /**
+  * Apply the collected features into the new project in one batch — resolves
+  * `true` when every item succeeds. The CLI renders this as a single progress
+  * line whose label changes per feature; each plan's `transformManifest`
+  * customizes that item's manifest before it is written.
+  */
+  applyAll: (plans: ReadonlyArray<FeatureApply>) => Promise<boolean>;
   /** When `false`, skip all prompts and print the later-setup hint. */
   interactive: boolean;
   logger: Logger;
@@ -529,6 +760,14 @@ interface OfferDeps {
   }>, settings?: {
     defaults?: ReadonlyArray<StackFeature>;
   }) => Promise<StackFeature[]>;
+  /**
+  * Features chosen non-interactively (the `--add` flag). When set, the
+  * multi-select and every sub-prompt are skipped — each feature is applied with
+  * its shipped defaults (base registry item, placeholder bindings).
+  */
+  preselected?: ReadonlyArray<StackFeature>;
+  /** The new project's name — seeds smart defaults like the `project-uploads` bucket name. */
+  projectName: string;
   /** Single-select among the auth providers (TTY-backed in production). */
   select: (message: string, options: ReadonlyArray<{
     description?: string;
@@ -537,17 +776,32 @@ interface OfferDeps {
   }>, settings?: {
     default?: FeatureItem;
   }) => Promise<FeatureItem | undefined>;
+  /** Single-line text input (TTY-backed in production) — used for the storage bucket-name prompt. */
+  text: (message: string, settings?: {
+    default?: string;
+    placeholder?: string;
+  }) => Promise<string>;
 }
 /**
 * Offer the stack features (auth, email, storage, rate limiting, crons,
-* presence, backups) in ONE multi-select after a successful scaffold. When auth
-* is picked, a follow-up single-select chooses the provider (email+password /
-* Clerk / Auth0); email maps to the `mail` item; every other feature value is
-* applied as its registry item directly. Picked items are applied in selection
-* order. Non-interactive: prints how to add them later and changes nothing.
+* presence, backups) in ONE multi-select after a successful scaffold. Auth,
+* email, and storage run a follow-up prompt (provider / destination / bucket
+* name); every other feature value is applied as its registry item directly.
+*
+* Every question is asked FIRST (in selection order), then the picked features
+* are applied together via {@link OfferDeps.applyAll} — the CLI renders that as a
+* single progress line whose label changes per feature, instead of one spinner
+* per item. Non-interactive: prints how to add them later and changes nothing.
 */
 type Template = "analog" | "astro" | "next" | "nuxt" | "react-router" | "standalone" | "sveltekit" | "tanstack-start-react" | "tanstack-start-solid";
 interface InitCommandOptions {
+  /**
+  * Add features non-interactively after scaffolding (the `--add` flag): a
+  * comma-separated list of `auth | email | storage | ratelimit | crons |
+  * presence | backup`. Bypasses the interactive multi-select and sub-prompts —
+  * each named feature is applied with its shipped defaults.
+  */
+  add?: string;
   /**
   * When true, accept `--source` values that don't start with `gh:` /
   * `github:` / `https://` or that contain `..`. Defaults to false; the CLI
@@ -559,6 +813,12 @@ interface InitCommandOptions {
   ci?: CiProvider;
   cwd?: string;
   /**
+  * Walk the whole flow — prompts, task list, next-steps, mascot — but make no
+  * changes: skip the template fetch/copy, the feature applies, the dependency
+  * install, and `git init`. Each skipped action logs a `would …` line instead.
+  */
+  dryRun?: boolean;
+  /**
   * Local directory containing the template subdirs (e.g. `vite/`,
   * `standalone/`). When provided, skips the network fetch entirely.
   * Useful for offline runs, the clean-machine smoke test, and unit tests.
@@ -599,10 +859,10 @@ interface InitCommandOptions {
   packageManagerProbe?: PackageManagerProbe;
   /**
   * Inject the offer's prompts (tests). When set, the offer is treated as
-  * interactive regardless of TTY, and these drive the feature multi-select
-  * and the auth-provider sub-select.
+  * interactive regardless of TTY, and these drive the feature multi-select,
+  * the auth-provider sub-select, and the storage bucket-name text input.
   */
-  prompt?: Pick<OfferDeps, "multiSelect" | "select">;
+  prompt?: Pick<OfferDeps, "multiSelect" | "select" | "text">;
   /**
   * Override the git ref (branch, tag, or commit) the default template source
   * is fetched from. Takes precedence over the version-derived ref. Ignored
@@ -639,11 +899,6 @@ interface InitCommandResult {
   files: ReadonlyArray<string>;
   target: string;
 }
-/**
-* `lunora init` entry: scaffold (in-place or a new directory), then — on success
-* — offer to add auth + email via the registry. The offer never affects the
-* scaffold's exit code.
-*/
 declare const runInitCommand: (options: InitCommandOptions) => Promise<InitCommandResult>;
 /** Narrow a raw `--template` value to a known {@link Template}. */
 interface MigrateGenerateCommandOptions {
@@ -681,99 +936,6 @@ interface IndexItem extends CatalogItem {
 declare const buildRegistryIndex: (root: string) => {
   items: IndexItem[];
 };
-/** A single file the item scaffolds into the project. */
-interface RegistryFile {
-  /** Source path inside the item dir (e.g. `schema.ts`). */
-  from: string;
-  /** Merge strategy. `create-or-skip` writes whole files; `schema-extension` AST-merges schema.ts. */
-  merge: "create-or-skip" | "schema-extension";
-  /** Destination relative to the project root (e.g. `lunora/ratelimit/index.ts`). */
-  to: string;
-}
-/** A wrangler.jsonc binding addition. `path` is the jsonc key path; `value` the value to set. */
-interface RegistryBinding {
-  path: ReadonlyArray<string>;
-  value: unknown;
-}
-/**
-* An environment variable an item needs. Scaffolded into `.dev.vars` (Workers'
-* local-secrets file) on add — non-secrets get their `value`; secrets get an
-* empty placeholder and a reminder to run `wrangler secret put` for production.
-*/
-interface RegistryEnvVariable {
-  /** Human note on what the variable is for. */
-  description?: string;
-  /** The variable name (e.g. `RESEND_API_KEY`). */
-  name: string;
-  /** Mark as a secret: never write a value, only a placeholder, and remind about prod. Defaults to `true` when no `value` is given. */
-  secret?: boolean;
-  /** A default/example value for non-secret vars. */
-  value?: string;
-}
-/** The `registry.json` manifest shape. */
-interface RegistryManifest {
-  /** wrangler.jsonc additions (best-effort structural edits). */
-  bindings?: ReadonlyArray<RegistryBinding>;
-  /** npm deps to add to the project package.json (name → version range). */
-  deps?: Readonly<Record<string, string>>;
-  description?: string;
-  /** npm devDependencies to add to the project package.json. */
-  devDependencies?: Readonly<Record<string, string>>;
-  /** Post-install guidance printed after the item is added (per-item next steps). */
-  docs?: string;
-  /** Environment variables the item needs; scaffolded into `.dev.vars`. */
-  envVars?: ReadonlyArray<RegistryEnvVariable>;
-  files: ReadonlyArray<RegistryFile>;
-  name: string;
-  /** Other registry items this one depends on (resolved transitively, deps first). */
-  requires?: ReadonlyArray<string>;
-  /** Short human-readable label (distinct from the longer `description`). */
-  title?: string;
-}
-interface AddCommandOptions {
-  /** Bypass the `--source` safety gate (matches init). */
-  allowUnsafeSource?: boolean;
-  /** `registry build --check`: verify the index is current instead of rewriting it. */
-  check?: boolean;
-  /** Inject a confirmer for non-interactive callers / tests. */
-  confirm?: (prompt: string) => Promise<boolean>;
-  cwd?: string;
-  /** Preview the file-level changes (a content diff) and write nothing. */
-  diff?: boolean;
-  /** Print the plan and stop without writing anything. */
-  dryRun?: boolean;
-  /** Local registry root (offline / tests). Expects per-item subdirs, each with a `registry.json`. */
-  from?: string;
-  /** Emit a JSON snapshot of the plan/result. */
-  json?: boolean;
-  /** `--list`: enumerate available items instead of adding. */
-  list?: boolean;
-  logger: Logger;
-  /** Item names to add (positional args). */
-  names: ReadonlyArray<string>;
-  /** `registry build` output path for the generated catalog (defaults to the root's `index.json`). */
-  out?: string;
-  /** Force-overwrite existing files (take the incoming copy) instead of skipping/conflicting. */
-  overwrite?: boolean;
-  /** Override the git ref (branch, tag, or commit) items are fetched from (default: version-derived); appended to the `source` base when that is set. Ignored when `from` is set. */
-  ref?: string;
-  /** Override the remote registry source base (default gh:anolilab/lunora/registry). */
-  source?: string;
-  /** Skip the package.json mutation confirmation prompt. */
-  yes?: boolean;
-}
-interface AddCommandResult {
-  /** Bindings written to wrangler.jsonc. */
-  bindings: ReadonlyArray<string>;
-  code: number;
-  /** Deps added to package.json. */
-  deps: ReadonlyArray<string>;
-  /** Files skipped because they already existed. */
-  skipped: ReadonlyArray<string>;
-  /** Files written (absolute paths). */
-  written: ReadonlyArray<string>;
-}
-/** One resolved item: its parsed manifest plus the (possibly staged) directory it lives in. */
 /** `lunora registry add` (one or more item names): scaffold items into the project. */
 declare const runAddCommand: (options: AddCommandOptions) => Promise<AddCommandResult>;
 /**