@lunora/config 1.0.0-alpha.70 → 1.0.0-alpha.71

package/dist/index.d.mts

@@ -2,7 +2,7 @@ import { AgentIR, ContainerIR, WorkflowIR, QueueIR, WranglerVariableIR } from '@
 export type { AgentIR, ContainerIR, WorkflowIR } from '@lunora/codegen';
 import { Writable } from 'node:stream';
 import 'ts-morph';
-export { type A as AdditivePolicyEdit, type D as DestructivePolicyEdit, type P as PolicyEdit, type a as PolicyScaffoldFailureReason, type b as ScaffoldFileResult, type S as ScaffoldPolicyEdit, type c as WireResult, type W as WireRlsEdit, d as classifyPolicyEdit, s as scaffoldPolicyFile, w as wireRlsIntoProcedure } from "./packem_shared/policy-scaffold.d-DCmwn7zQ.mjs";
+export { type A as AdditivePolicyEdit, type D as DestructivePolicyEdit, type P as PolicyEdit, type a as PolicyScaffoldFailureReason, type b as ScaffoldFileResult, type S as ScaffoldPolicyEdit, type c as WireResult, type W as WireRlsEdit, d as classifyPolicyEdit, s as scaffoldPolicyFile, w as wireRlsIntoProcedure } from "./packem_shared/policy-scaffold.d-CFd2FlqG.mjs";
 /** Minimal env shape — `process.env` structurally, injectable for tests. */
 type EnvLike = Readonly<Record<string, string | undefined>>;
 /** One detected agent: which tool, and which env var gave it away. */
@@ -15,10 +15,10 @@ interface AgentDetection {
 /** Env var that forces agent mode on (`1`/`true`) or off (`0`/`false`), overriding detection. */
 declare const AGENT_MODE_ENV = "LUNORA_AGENT_MODE";
 /**
-* Detect the AI agent driving this process, or `undefined` when none is.
-* `LUNORA_AGENT_MODE` wins over `@visulima/find-ai-runner`'s marker table in
-* both directions. Pure — pass a custom `env` in tests.
-*/
+ * Detect the AI agent driving this process, or `undefined` when none is.
+ * `LUNORA_AGENT_MODE` wins over `@visulima/find-ai-runner`'s marker table in
+ * both directions. Pure — pass a custom `env` in tests.
+ */
 declare const detectAiAgent: (env?: EnvLike) => AgentDetection | undefined;
 interface DiscoverAgentInfoResult {
   /** Discovered agent definitions; `[]` when none are declared or parsing failed. */
@@ -27,47 +27,47 @@ interface DiscoverAgentInfoResult {
   error?: string;
 }
 /**
-* Discover the project's `defineAgent` declarations. Returns `{ agents: [] }`
-* when the project has no `lunora/agents.ts` (not an error), or
-* `{ agents: [], error }` when the file exists but could not be parsed — callers
-* decide whether that is a warning (validator) or ignorable (inference).
-*/
+ * Discover the project's `defineAgent` declarations. Returns `{ agents: [] }`
+ * when the project has no `lunora/agents.ts` (not an error), or
+ * `{ agents: [], error }` when the file exists but could not be parsed — callers
+ * decide whether that is a warning (validator) or ignorable (inference).
+ */
 declare const discoverAgentInfo: (projectRoot: string, schemaDirectory: string) => DiscoverAgentInfoResult;
 /**
-* Project-relative directory the Lunora agent skills ("rules") install into.
-* This is the portable [Agent Skills](https://tanstack.com/intent/latest/docs/registry)
-* location — Cursor, Claude Code, and GitHub Copilot all discover skills here.
-*/
+ * Project-relative directory the Lunora agent skills ("rules") install into.
+ * This is the portable [Agent Skills](https://tanstack.com/intent/latest/docs/registry)
+ * location — Cursor, Claude Code, and GitHub Copilot all discover skills here.
+ */
 declare const AGENT_RULES_DIR = ".agents/skills";
 /** Env var the once-per-process-tree hint guard ({@link claimAgentRulesHint}) sets. */
 declare const AGENT_RULES_HINT_ENV = "LUNORA_RULES_HINT_SHOWN";
 /**
-* The Lunora agent skills shipped by `@lunora/cli`. The first entry (`lunora`)
-* is the router skill — its presence is what {@link detectAgentRules} treats as
-* "rules installed", since every other skill is reachable through it.
-*/
+ * The Lunora agent skills shipped by `@lunora/cli`. The first entry (`lunora`)
+ * is the router skill — its presence is what {@link detectAgentRules} treats as
+ * "rules installed", since every other skill is reachable through it.
+ */
 declare const LUNORA_SKILL_NAMES: ReadonlyArray<string>;
 /** The router skill whose presence marks the rule set as installed. */
 declare const ROOT_SKILL_NAME = "lunora";
 /**
-* The single "rules not installed" message shared by every surface (the CLI
-* `lunora dev` summary and the Vite dev plugin), so the wording and the
-* pointer at `lunora rules install` stay identical wherever it appears.
-*/
+ * The single "rules not installed" message shared by every surface (the CLI
+ * `lunora dev` summary and the Vite dev plugin), so the wording and the
+ * pointer at `lunora rules install` stay identical wherever it appears.
+ */
 declare const AGENT_RULES_HINT = "Lunora AI rules not installed — run `lunora rules install` so your coding agent knows how to use Lunora.";
 /**
-* Process-tree guard so the hint is emitted at most once. The first surface to
-* print it sets {@link AGENT_RULES_HINT_ENV} on `process.env`; later surfaces (a
-* Vite dev-server restart, or a child process that inherited the env) read it
-* and stay quiet. Returns `true` the first time, `false` afterwards.
-*/
+ * Process-tree guard so the hint is emitted at most once. The first surface to
+ * print it sets {@link AGENT_RULES_HINT_ENV} on `process.env`; later surfaces (a
+ * Vite dev-server restart, or a child process that inherited the env) read it
+ * and stay quiet. Returns `true` the first time, `false` afterwards.
+ */
 declare const claimAgentRulesHint: () => boolean;
 interface AgentRulesStatus {
   /**
-  * True when the `lunora` router skill is installed. We key on the router
-  * (not "all nine present") so a project that intentionally trims the set
-  * still counts as installed and isn't nagged.
-  */
+   * True when the `lunora` router skill is installed. We key on the router
+   * (not "all nine present") so a project that intentionally trims the set
+   * still counts as installed and isn't nagged.
+   */
   readonly installed: boolean;
   /** Skill names with no `SKILL.md` under `&lt;root>/.agents/skills/&lt;name>/`. */
   readonly missing: ReadonlyArray<string>;
@@ -75,12 +75,12 @@ interface AgentRulesStatus {
   readonly present: ReadonlyArray<string>;
 }
 /**
-* Detect whether the Lunora agent skills are installed in `projectRoot` by
-* checking the skills folder for each `SKILL.md`. Pure filesystem reads, safe to
-* call on every dev-server / CLI startup — the CLI, the Vite plugin, and the
-* studio host all use it to decide whether to surface the "rules not installed"
-* hint.
-*/
+ * Detect whether the Lunora agent skills are installed in `projectRoot` by
+ * checking the skills folder for each `SKILL.md`. Pure filesystem reads, safe to
+ * call on every dev-server / CLI startup — the CLI, the Vite plugin, and the
+ * studio host all use it to decide whether to surface the "rules not installed"
+ * hint.
+ */
 declare const detectAgentRules: (projectRoot: string) => AgentRulesStatus;
 interface DiscoverContainerInfoResult {
   /** Discovered container definitions; `[]` when none are declared or parsing failed. */
@@ -89,12 +89,12 @@ interface DiscoverContainerInfoResult {
   error?: string;
 }
 /**
-* Discover the project's `defineContainer` declarations. Returns
-* `{ containers: [] }` when the project has no `lunora/containers.ts` (not an
-* error), or `{ containers: [], error }` when the file exists but could not be
-* parsed — callers decide whether that is a warning (validator) or ignorable
-* (inference).
-*/
+ * Discover the project's `defineContainer` declarations. Returns
+ * `{ containers: [] }` when the project has no `lunora/containers.ts` (not an
+ * error), or `{ containers: [], error }` when the file exists but could not be
+ * parsed — callers decide whether that is a warning (validator) or ignorable
+ * (inference).
+ */
 declare const discoverContainerInfo: (projectRoot: string, schemaDirectory: string) => DiscoverContainerInfoResult;
 /** Severity a container output line is surfaced at: `stderr` → `error`, `stdout` → `info`. */
 type ContainerLogLevel = "error" | "info";
@@ -160,25 +160,25 @@ interface DockerLike {
   };
 }
 /**
-* Follow the local Docker logs of every declared container, emitting each output
-* line through `onLine` tagged with its export name. Polls for containers (they
-* start lazily on first request and may be replaced on restart), attaches once
-* per container id, and drops streams whose container has gone. Returns
-* immediately with a `close()` handle; all work happens asynchronously.
-*/
+ * Follow the local Docker logs of every declared container, emitting each output
+ * line through `onLine` tagged with its export name. Polls for containers (they
+ * start lazily on first request and may be replaced on restart), attaches once
+ * per container id, and drops streams whose container has gone. Returns
+ * immediately with a `close()` handle; all work happens asynchronously.
+ */
 declare const streamContainerLogs: (options: ContainerLogStreamOptions) => ContainerLogStreamHandle;
 /**
-* The meta-frameworks Lunora can compose with, plus `"none"` for a standalone
-* SPA / SSR-less project (the current default). Mirrors PLAN4 §2.4.
-*/
+ * The meta-frameworks Lunora can compose with, plus `"none"` for a standalone
+ * SPA / SSR-less project (the current default). Mirrors PLAN4 §2.4.
+ */
 type DetectedFramework = "astro" | "none" | "nuxt" | "react-router" | "solid-start" | "sveltekit" | "tanstack-start" | "tanstack-start-solid";
 /**
-* void's class model (PLAN4 §3). Class A is Vite-native and Lunora owns the
-* worker entry (`createWorker({ httpRouter })`). Class B frameworks own their own
-* Cloudflare adapter, so Lunora injects its worker composition into the
-* framework's server entry via hooks (PLAN4 M4). Class C is non-CF / SSR-less —
-* ship the client adapter + a standalone Lunora worker (today's default).
-*/
+ * void's class model (PLAN4 §3). Class A is Vite-native and Lunora owns the
+ * worker entry (`createWorker({ httpRouter })`). Class B frameworks own their own
+ * Cloudflare adapter, so Lunora injects its worker composition into the
+ * framework's server entry via hooks (PLAN4 M4). Class C is non-CF / SSR-less —
+ * ship the client adapter + a standalone Lunora worker (today's default).
+ */
 type FrameworkClass = "A" | "B" | "C";
 interface FrameworkDetection {
   /** void's composition class for the detected framework. */
@@ -187,20 +187,20 @@ interface FrameworkDetection {
   framework: DetectedFramework;
 }
 /**
-* Read and parse the project `package.json`, returning its merged
-* `dependencies` + `devDependencies` name set (empty on any failure). Public
-* so sibling consumers (e.g. the CLI's Vite-project detection) share one
-* best-effort reader instead of re-parsing `package.json` themselves.
-*/
+ * Read and parse the project `package.json`, returning its merged
+ * `dependencies` + `devDependencies` name set (empty on any failure). Public
+ * so sibling consumers (e.g. the CLI's Vite-project detection) share one
+ * best-effort reader instead of re-parsing `package.json` themselves.
+ */
 declare const readProjectDependencyNames: (root: string) => ReadonlySet<string>;
 /**
-* Detect which meta-framework a project uses by inspecting its `package.json`
-* dependencies, and classify it under void's class-A/B/C model (PLAN4 §3).
-*
-* Pure and best-effort: never throws. An unknown / missing / malformed
-* `package.json` yields `{ framework: "none", class: "C" }` so the standalone
-* SPA flow is preserved.
-*/
+ * Detect which meta-framework a project uses by inspecting its `package.json`
+ * dependencies, and classify it under void's class-A/B/C model (PLAN4 §3).
+ *
+ * Pure and best-effort: never throws. An unknown / missing / malformed
+ * `package.json` yields `{ framework: "none", class: "C" }` so the standalone
+ * SPA flow is preserved.
+ */
 declare const detectFramework: (root: string) => FrameworkDetection;
 /** Directory holding per-checkout Lunora state (gitignored by convention). */
 declare const DEV_STATE_DIR = ".lunora";
@@ -209,23 +209,23 @@ declare const DEV_STATE_FILE: string;
 /** Log file a backgrounded dev server's output is captured to, relative to the project root. */
 declare const DEV_LOG_FILE: string;
 /**
-* Marker env `lunora dev --background` sets on the detached server process
-* (the daemon `lunora dev` or `vite dev`), so it records itself as
-* `background: true` — and, for the CLI daemon, never re-detects an agent and
-* recurses into background mode again.
-*/
+ * Marker env `lunora dev --background` sets on the detached server process
+ * (the daemon `lunora dev` or `vite dev`), so it records itself as
+ * `background: true` — and, for the CLI daemon, never re-detects an agent and
+ * recurses into background mode again.
+ */
 declare const DEV_DAEMON_ENV = "LUNORA_DEV_DAEMON";
 /** Env carrying the capture-log path into the detached server, recorded in the state file. */
 declare const DEV_LOG_FILE_ENV = "LUNORA_DEV_LOG_FILE";
 /**
-* Env carrying the PID of a parent that holds a *provisional* state record it
-* expects the child dev server to supersede. The CLI claims `.lunora/dev.json`
-* with its own PID before spawning the real server (closing the duplicate-start
-* race for the vite flavor and the wrangler daemon), then hands its PID down
-* via this variable; the child's claim (see {@link claimDevServerState}'s
-* `supersedePid`) may replace exactly that record with the authoritative
-* URL + PID.
-*/
+ * Env carrying the PID of a parent that holds a *provisional* state record it
+ * expects the child dev server to supersede. The CLI claims `.lunora/dev.json`
+ * with its own PID before spawning the real server (closing the duplicate-start
+ * race for the vite flavor and the wrangler daemon), then hands its PID down
+ * via this variable; the child's claim (see {@link claimDevServerState}'s
+ * `supersedePid`) may replace exactly that record with the authoritative
+ * URL + PID.
+ */
 declare const DEV_HANDOFF_ENV = "LUNORA_DEV_HANDOFF_PID";
 /** How the recorded dev server runs. */
 type DevServerMode = "cli" | "vite";
@@ -247,56 +247,56 @@ interface DevServerState {
   url: string;
 }
 /**
-* True when a process with `pid` is currently alive AND signalable by this
-* user. Signal `0` performs the existence check without delivering anything.
-*
-* `EPERM` ("alive but another user's process") deliberately counts as NOT
-* alive here: every dev server this module tracks was spawned by the current
-* user, so a PID we cannot signal is by definition a recycled PID — treating
-* it as running would wedge the lockfile permanently and aim `dev stop`'s
-* kill escalation at an innocent process.
-*/
+ * True when a process with `pid` is currently alive AND signalable by this
+ * user. Signal `0` performs the existence check without delivering anything.
+ *
+ * `EPERM` ("alive but another user's process") deliberately counts as NOT
+ * alive here: every dev server this module tracks was spawned by the current
+ * user, so a PID we cannot signal is by definition a recycled PID — treating
+ * it as running would wedge the lockfile permanently and aim `dev stop`'s
+ * kill escalation at an innocent process.
+ */
 declare const isProcessAlive: (pid: number) => boolean;
 /**
-* True when the record's PID verifiably still refers to the dev server that
-* wrote the record — not merely "some process exists with that number".
-* Guards against PID reuse: a server process necessarily starts BEFORE its
-* record is written, so a process that started after `startedAt` (+ skew) is
-* a recycled PID wearing the corpse's number. The start-time check runs only
-* where the platform exposes it (Linux); elsewhere liveness alone decides.
-*/
+ * True when the record's PID verifiably still refers to the dev server that
+ * wrote the record — not merely "some process exists with that number".
+ * Guards against PID reuse: a server process necessarily starts BEFORE its
+ * record is written, so a process that started after `startedAt` (+ skew) is
+ * a recycled PID wearing the corpse's number. The start-time check runs only
+ * where the platform exposes it (Linux); elsewhere liveness alone decides.
+ */
 declare const isRecordedProcessCurrent: (state: DevServerState) => boolean;
 /**
-* Read the state record from `.lunora/dev.json`, or `undefined` when there is
-* no usable record. Best-effort; performs NO liveness check — use
-* {@link readLiveDevServerState} for "is a dev server actually running".
-*/
+ * Read the state record from `.lunora/dev.json`, or `undefined` when there is
+ * no usable record. Best-effort; performs NO liveness check — use
+ * {@link readLiveDevServerState} for "is a dev server actually running".
+ */
 declare const readDevServerState: (projectRoot: string) => DevServerState | undefined;
 /**
-* Write the state record to `.lunora/dev.json`, creating the `.lunora/`
-* directory when absent. Returns the absolute path written, or `undefined`
-* when the write failed (state is convenience metadata — a read-only checkout
-* must never crash dev startup).
-*/
+ * Write the state record to `.lunora/dev.json`, creating the `.lunora/`
+ * directory when absent. Returns the absolute path written, or `undefined`
+ * when the write failed (state is convenience metadata — a read-only checkout
+ * must never crash dev startup).
+ */
 declare const writeDevServerState: (projectRoot: string, state: DevServerState) => string | undefined;
 /**
-* Merge `patch` into the existing state record, when one exists. Used by the
-* CLI to stamp `background`/`logFile` onto the record the Vite plugin wrote.
-* Returns the merged record, or `undefined` when there was nothing to update.
-*/
+ * Merge `patch` into the existing state record, when one exists. Used by the
+ * CLI to stamp `background`/`logFile` onto the record the Vite plugin wrote.
+ * Returns the merged record, or `undefined` when there was nothing to update.
+ */
 declare const updateDevServerState: (projectRoot: string, patch: Partial<DevServerState>) => DevServerState | undefined;
 /**
-* Remove `.lunora/dev.json`. Idempotent and never throws. When `expectedPid`
-* is given, the file is only removed while it still records that PID — so a
-* shutting-down server can't clobber the record a newer server just wrote.
-*/
+ * Remove `.lunora/dev.json`. Idempotent and never throws. When `expectedPid`
+ * is given, the file is only removed while it still records that PID — so a
+ * shutting-down server can't clobber the record a newer server just wrote.
+ */
 declare const clearDevServerState: (projectRoot: string, expectedPid?: number) => void;
 /**
-* The state record of a dev server that is verifiably running right now, or
-* `undefined`. A record whose PID is dead — or recycled onto a different
-* process (see {@link isRecordedProcessCurrent}) — is stale: it is cleared on
-* the spot so subsequent starts don't keep re-reading a corpse.
-*/
+ * The state record of a dev server that is verifiably running right now, or
+ * `undefined`. A record whose PID is dead — or recycled onto a different
+ * process (see {@link isRecordedProcessCurrent}) — is stale: it is cleared on
+ * the spot so subsequent starts don't keep re-reading a corpse.
+ */
 declare const readLiveDevServerState: (projectRoot: string) => DevServerState | undefined;
 /** Result of {@link claimDevServerState}: claimed, or lost to the live server already recorded. */
 interface ClaimDevServerStateResult {
@@ -309,27 +309,25 @@ declare const claimDevServerState: (projectRoot: string, state: DevServerState,
   supersedePid?: number;
 }) => ClaimDevServerStateResult;
 /**
-* The `.dev.vars` line grammar — one owner, shared by every reader/writer of the
-* file so the format can't drift between packages. `@lunora/cli`'s `env`
-* command (parse/serialize) and `@lunora/config`'s scaffolder (comment-
-* preserving rewrite) do different *transforms*, but they agree on these
-* primitives: the filename, what a `KEY` looks like, how lines split, and how
-* quotes strip.
-*/
+ * The `.dev.vars` line grammar — one owner, shared by every reader/writer of the
+ * file so the format can't drift between packages. `@lunora/cli`'s `env`
+ * command (parse/serialize) and `@lunora/config`'s scaffolder (comment-
+ * preserving rewrite) do different *transforms*, but they agree on these
+ * primitives: the filename, what a `KEY` looks like, how lines split, and how
+ * quotes strip.
+ */
 /** The conventional filename for local Cloudflare dev secrets (gitignored). */
 declare const DEV_VARS_FILE: string;
 /** Its committed, secret-free counterpart that scaffolding reads from. */
 declare const DEV_VARS_EXAMPLE_FILE: string;
 /** A bare `KEY` identifier — the part left of `=` in a `.dev.vars` line. */
 declare const DEV_VARS_KEY_PATTERN: RegExp;
-/** Splits file content into lines on either newline style. */
-
-/**
-* Parse `.dev.vars` content into its `{ key, value }` entries, in file order,
-* with values unquoted and comments/blank/invalid lines dropped. The canonical
-* read of the whole file — callers that just want the variables (rather than a
-* comment-preserving rewrite) use this instead of hand-rolling the split loop.
-*/
+/**
+ * Parse `.dev.vars` content into its `{ key, value }` entries, in file order,
+ * with values unquoted and comments/blank/invalid lines dropped. The canonical
+ * read of the whole file — callers that just want the variables (rather than a
+ * comment-preserving rewrite) use this instead of hand-rolling the split loop.
+ */
 declare const parseDevVariableEntries: (content: string) => {
   key: string;
   value: string;
@@ -341,53 +339,53 @@ interface DiscoverWorkflowInfoResult {
   workflows: ReadonlyArray<WorkflowIR>;
 }
 /**
-* Discover the project's `defineWorkflow` declarations. Returns
-* `{ workflows: [] }` when the project has no `lunora/workflows.ts` (not an
-* error), or `{ workflows: [], error }` when the file exists but could not be
-* parsed — callers decide whether that is a warning (validator) or ignorable
-* (inference).
-*/
+ * Discover the project's `defineWorkflow` declarations. Returns
+ * `{ workflows: [] }` when the project has no `lunora/workflows.ts` (not an
+ * error), or `{ workflows: [], error }` when the file exists but could not be
+ * parsed — callers decide whether that is a warning (validator) or ignorable
+ * (inference).
+ */
 declare const discoverWorkflowInfo: (projectRoot: string, schemaDirectory: string) => DiscoverWorkflowInfoResult;
 interface DurableObjectSpec {
   binding: string;
   className: string;
 }
 /**
-* A `defineContainer` declaration plus whether its generated DO class is
-* exported by the worker entry. Only exported containers are safe to
-* provision — wrangler rejects a `containers[].class_name` (and its Durable
-* Object binding) that the worker doesn't export.
-*/
+ * A `defineContainer` declaration plus whether its generated DO class is
+ * exported by the worker entry. Only exported containers are safe to
+ * provision — wrangler rejects a `containers[].class_name` (and its Durable
+ * Object binding) that the worker doesn't export.
+ */
 interface InferredContainer extends ContainerIR {
   exported: boolean;
 }
 /**
-* A `defineWorkflow` declaration plus whether its generated
-* `WorkflowEntrypoint` class is exported by the worker entry. Only exported
-* workflows are safe to provision — wrangler rejects a `workflows[].class_name`
-* the worker doesn't export. Workflows are NOT Durable Objects, so this never
-* implies a `durable_objects` binding or migration.
-*/
+ * A `defineWorkflow` declaration plus whether its generated
+ * `WorkflowEntrypoint` class is exported by the worker entry. Only exported
+ * workflows are safe to provision — wrangler rejects a `workflows[].class_name`
+ * the worker doesn't export. Workflows are NOT Durable Objects, so this never
+ * implies a `durable_objects` binding or migration.
+ */
 interface InferredWorkflow extends WorkflowIR {
   exported: boolean;
 }
 /**
-* A `defineAgent` declaration plus whether its generated agent
-* `WorkflowEntrypoint` class (e.g. `SupportAgentWorkflow`) is exported by the
-* worker entry. An agent compiles onto a Cloudflare Workflow, so — exactly like
-* {@link InferredWorkflow} — only exported agents are safe to provision
-* (wrangler rejects a `workflows[].class_name` the worker doesn't export), and
-* an agent is NOT a Durable Object (no `durable_objects` binding or migration).
-*/
+ * A `defineAgent` declaration plus whether its generated agent
+ * `WorkflowEntrypoint` class (e.g. `SupportAgentWorkflow`) is exported by the
+ * worker entry. An agent compiles onto a Cloudflare Workflow, so — exactly like
+ * {@link InferredWorkflow} — only exported agents are safe to provision
+ * (wrangler rejects a `workflows[].class_name` the worker doesn't export), and
+ * an agent is NOT a Durable Object (no `durable_objects` binding or migration).
+ */
 interface InferredAgent extends AgentIR {
   exported: boolean;
 }
 /**
-* A queue declared in `lunora/queues.ts`. Unlike workflows, a queue needs no
-* worker-entry class export (its `queue()` handler rides `createWorker`), so
-* there is no `exported` flag — every declared queue is reconcilable into the
-* wrangler `queues.producers[]` / `queues.consumers[]`.
-*/
+ * A queue declared in `lunora/queues.ts`. Unlike workflows, a queue needs no
+ * worker-entry class export (its `queue()` handler rides `createWorker`), so
+ * there is no `exported` flag — every declared queue is reconcilable into the
+ * wrangler `queues.producers[]` / `queues.consumers[]`.
+ */
 type InferredQueue = QueueIR;
 interface InferredBindings {
   /** Agents declared in `lunora/agents.ts` (exported or not — see {@link InferredAgent.exported}); reconciled into `workflows[]`. */
@@ -397,11 +395,11 @@ interface InferredBindings {
   /** Durable Objects the worker entry exports → safe to bind. */
   durableObjects: DurableObjectSpec[];
   /**
-  * The wrangler `flagship[].binding` name implied by `lunora/flags.ts` when it
-  * uses the Flagship provider in binding mode — `undefined` for HTTP-mode
-  * Flagship, a custom OpenFeature provider, or no flags. The binding needs an
-  * un-mintable `app_id`, so it is reconciled as a hint, not auto-written.
-  */
+   * The wrangler `flagship[].binding` name implied by `lunora/flags.ts` when it
+   * uses the Flagship provider in binding mode — `undefined` for HTTP-mode
+   * Flagship, a custom OpenFeature provider, or no flags. The binding needs an
+   * un-mintable `app_id`, so it is reconciled as a hint, not auto-written.
+   */
   flagshipBinding?: string;
   /** Schema declares a `.global()` table → needs the `DB` D1 binding. */
   needsD1: boolean;
@@ -450,33 +448,33 @@ interface InferOptions {
   schemaDir?: string;
 }
 /**
-* Scan a Lunora project and report which Cloudflare bindings its code implies.
-* Read-only: performs no writes. Binding provisioning is driven by the worker
-* entry's Durable Object exports plus the schema's D1 need; capability imports
-* surface as hints.
-*/
+ * Scan a Lunora project and report which Cloudflare bindings its code implies.
+ * Read-only: performs no writes. Binding provisioning is driven by the worker
+ * entry's Durable Object exports plus the schema's D1 need; capability imports
+ * surface as hints.
+ */
 declare const inferLunoraBindings: (options: InferOptions) => Promise<InferredBindings>;
 /**
-* Derive the list of `@lunora/*` package names that are actively used by a
-* project, based on its already-resolved {@link InferredBindings}.
-*
-* This is the canonical bridge between binding inference and the package-aware
-* `.dev.vars.example` scaffolding in `scaffold-dev-variables.ts`. The result is
-* a stable, predictable slice of {@link CAPABILITY_SOURCES} source values,
-* filtered to the flags that are `true` in `bindings` — in CAPABILITY_SOURCES
-* declaration order.
-*/
+ * Derive the list of `@lunora/*` package names that are actively used by a
+ * project, based on its already-resolved {@link InferredBindings}.
+ *
+ * This is the canonical bridge between binding inference and the package-aware
+ * `.dev.vars.example` scaffolding in `scaffold-dev-variables.ts`. The result is
+ * a stable, predictable slice of {@link CAPABILITY_SOURCES} source values,
+ * filtered to the flags that are `true` in `bindings` — in CAPABILITY_SOURCES
+ * declaration order.
+ */
 declare const packageNamesFromBindings: (bindings: InferredBindings) => string[];
 /** Directory holding per-checkout Lunora state (gitignored by convention). */
 declare const LINKED_PROJECT_DIR = ".lunora";
 /** The canonical link filename, relative to the project root. */
 declare const LINKED_PROJECT_FILE: string;
 /**
-* The link record persisted to `.lunora/project.json`. Every field is optional
-* so a partially-populated link (e.g. a worker name with no URL yet) still
-* round-trips. `linkedAt` is an ISO-8601 stamp written at link time, purely
-* informational.
-*/
+ * The link record persisted to `.lunora/project.json`. Every field is optional
+ * so a partially-populated link (e.g. a worker name with no URL yet) still
+ * round-trips. `linkedAt` is an ISO-8601 stamp written at link time, purely
+ * informational.
+ */
 interface LinkedProject {
   /** Cloudflare account id the worker lives under, when known. */
   account?: string;
@@ -490,34 +488,17 @@ interface LinkedProject {
   workerUrl?: string;
 }
 /**
-* Read the link record from `.lunora/project.json`, or `undefined` when there
-* is no usable link. Best-effort: a missing file, parse error, or unexpected
-* shape all collapse to `undefined`.
-*/
+ * Read the link record from `.lunora/project.json`, or `undefined` when there
+ * is no usable link. Best-effort: a missing file, parse error, or unexpected
+ * shape all collapse to `undefined`.
+ */
 declare const readLinkedProject: (projectRoot: string) => LinkedProject | undefined;
 /**
-* Write the link record to `.lunora/project.json`, creating the `.lunora/`
-* directory when absent. Only defined fields are persisted (so an empty value
-* never clobbers a known one). Returns the absolute path written.
-*/
+ * Write the link record to `.lunora/project.json`, creating the `.lunora/`
+ * directory when absent. Only defined fields are persisted (so an empty value
+ * never clobbers a known one). Returns the absolute path written.
+ */
 declare const writeLinkedProject: (projectRoot: string, link: LinkedProject) => string;
-/**
-* Shared formatter for the structured log events the Lunora runtime emits to the
-* worker's `console` during development. Both the CLI `dev` command and the Vite
-* plugin pipe worker output through `formatLunoraEvent` so a developer sees
-* attributed, readable lines instead of raw JSON.
-*
-* The runtime emits two event shapes, each a single `console` line tagged
-* `source: "lunora"` (see `@lunora/do`'s `request-log.ts`): a `type: "log"`
-* event per `ctx.log.*` call, and a `type: "request"` event per RPC dispatch
-* (opt-in for successful calls, always for errors).
-*
-* This module is intentionally dependency-free and colour-free: it returns the
-* severity plus a plain display string, leaving ANSI/level colouring to each
-* caller (the CLI routes through its `pail` logger; the Vite plugin dims inline).
-* Any line that is not a lunora event returns `undefined`, signalling the caller
-* to pass it through unchanged.
-*/
 /** Severity a formatted line should be surfaced at, mapped onto the three logger channels. */
 type LunoraLineLevel = "error" | "info" | "warn";
 /** A formatted lunora event: the channel to surface it on, the display text, and which event produced it. */
@@ -532,11 +513,11 @@ interface LunoraFormattedLine {
 /** Stable `source` tag every lunora console event carries. Mirrors `REQUEST_LOG_EVENT_SOURCE` in `@lunora/do`. */
 declare const LUNORA_EVENT_SOURCE = "lunora";
 /**
-* Parse a single worker-output line and, when it is a lunora structured event,
-* return its severity plus display text. Returns `undefined` for anything else —
-* non-JSON lines, JSON that isn't a lunora event, or an unrecognised event type
-* — so the caller passes the original line through untouched. Pure and total.
-*/
+ * Parse a single worker-output line and, when it is a lunora structured event,
+ * return its severity plus display text. Returns `undefined` for anything else —
+ * non-JSON lines, JSON that isn't a lunora event, or an unrecognised event type
+ * — so the caller passes the original line through untouched. Pure and total.
+ */
 declare const formatLunoraEvent: (line: string) => LunoraFormattedLine | undefined;
 declare class LunoraReporter {
   #private;
@@ -545,32 +526,32 @@ declare class LunoraReporter {
   log(meta: unknown): void;
 }
 /**
-* Per-package secret-requirements registry for `.dev.vars` scaffolding.
-*
-* Each entry maps a `@lunora/*` package name → the secrets it requires at
-* runtime, expressed as `{ key, description, docsUrl }` records. The scaffolder
-* in {@link ./scaffold-dev-variables} reads this registry to emit package-aware
-* `.dev.vars.example` entries (placeholders + inline doc-pointer comments).
-*
-* ## Adding a new add-on
-*
-* When a new `@lunora/*` package requires runtime secrets, add one entry to
-* {@link PACKAGE_SECRETS_REGISTRY} keyed by its exact npm package name. Each
-* `SecretEntry` in the array needs:
-*
-* - `key`         — the env-var name the package reads from `env` (e.g. `RESEND_API_KEY`).
-* - `description` — one line describing the secret and how to obtain it.
-* - `docsUrl`     — a stable URL to the package/provider docs.
-*
-* The registry lives in `@lunora/config` so that add-ons themselves never need
-* to depend on it (no circular coupling). Add-ons document their secrets in
-* their own READMEs; the registry duplicates that knowledge in a machine-readable
-* form that the scaffolder can consume.
-*
-* **Never write a real secret value** in this file — `placeholderValue` entries
-* are the only allowed values (they must pass `isPlaceholderValue` from
-* scaffold-dev-variables).
-*/
+ * Per-package secret-requirements registry for `.dev.vars` scaffolding.
+ *
+ * Each entry maps a `@lunora/*` package name → the secrets it requires at
+ * runtime, expressed as `{ key, description, docsUrl }` records. The scaffolder
+ * in {@link ./scaffold-dev-variables} reads this registry to emit package-aware
+ * `.dev.vars.example` entries (placeholders + inline doc-pointer comments).
+ *
+ * ## Adding a new add-on
+ *
+ * When a new `@lunora/*` package requires runtime secrets, add one entry to
+ * {@link PACKAGE_SECRETS_REGISTRY} keyed by its exact npm package name. Each
+ * `SecretEntry` in the array needs:
+ *
+ * - `key`         — the env-var name the package reads from `env` (e.g. `RESEND_API_KEY`).
+ * - `description` — one line describing the secret and how to obtain it.
+ * - `docsUrl`     — a stable URL to the package/provider docs.
+ *
+ * The registry lives in `@lunora/config` so that add-ons themselves never need
+ * to depend on it (no circular coupling). Add-ons document their secrets in
+ * their own READMEs; the registry duplicates that knowledge in a machine-readable
+ * form that the scaffolder can consume.
+ *
+ * **Never write a real secret value** in this file — `placeholderValue` entries
+ * are the only allowed values (they must pass `isPlaceholderValue` from
+ * scaffold-dev-variables).
+ */
 /** A single secret variable required by a package. */
 interface SecretEntry {
   /** One sentence describing what this secret is and how to obtain it. */
@@ -580,96 +561,87 @@ interface SecretEntry {
   /** The env-var key as it appears in `.dev.vars`, e.g. `AUTH_SECRET`. */
   key: string;
   /**
-  * The placeholder value written into `.dev.vars.example`.
-  * Must pass `isPlaceholderValue` from scaffold-dev-variables so the
-  * scaffolder regenerates it when generating `.dev.vars`. Use angle-bracket
-  * conventions or a recognised marker like `replace-with-openssl-rand-hex-32`.
-  * Non-secret env-vars (e.g. `AUTH_URL`) may carry a real default value.
-  */
+   * The placeholder value written into `.dev.vars.example`.
+   * Must pass `isPlaceholderValue` from scaffold-dev-variables so the
+   * scaffolder regenerates it when generating `.dev.vars`. Use angle-bracket
+   * conventions or a recognised marker like `replace-with-openssl-rand-hex-32`.
+   * Non-secret env-vars (e.g. `AUTH_URL`) may carry a real default value.
+   */
   placeholderValue: string;
 }
 /**
-* Secrets every Lunora project needs regardless of which capability packages are
-* installed — scaffolded into `.dev.vars` always. `LUNORA_ADMIN_TOKEN` is the
-* bearer the local Studio uses to call the worker's admin endpoints (the data
-* browser, schema edits) in dev; the worker reads the SAME `.dev.vars` value via
-* its admin gate, so both agree and the Studio authenticates without a prompt.
-* Without it, every `/_lunora/admin/*` call is `ADMIN_FORBIDDEN` (403).
-*/
-
-/**
-* The canonical registry of per-package secret requirements.
-*
-* Keys are exact npm package names (e.g. `"@lunora/auth"`). Values are
-* non-empty arrays of {@link SecretEntry} — one entry per required secret key.
-*
-* The scaffolder in `scaffold-dev-variables.ts` calls
-* {@link secretsForPackages} to resolve the applicable entries from this map
-* given the set of detected capability package names.
-*/
+ * The canonical registry of per-package secret requirements.
+ *
+ * Keys are exact npm package names (e.g. `"@lunora/auth"`). Values are
+ * non-empty arrays of {@link SecretEntry} — one entry per required secret key.
+ *
+ * The scaffolder in `scaffold-dev-variables.ts` calls
+ * {@link secretsForPackages} to resolve the applicable entries from this map
+ * given the set of detected capability package names.
+ */
 declare const PACKAGE_SECRETS_REGISTRY: Readonly<Record<string, ReadonlyArray<SecretEntry>>>;
 /**
-* Collect all secret entries required by the given set of package names. The
-* order follows the order of `packageNames` (stable, predictable output), and
-* within each package the entries are returned in registry declaration order.
-*
-* Only packages present in {@link PACKAGE_SECRETS_REGISTRY} contribute entries;
-* unknown package names are silently ignored — this makes the call site resilient
-* to future capability flags whose packages have no secrets.
-*/
+ * Collect all secret entries required by the given set of package names. The
+ * order follows the order of `packageNames` (stable, predictable output), and
+ * within each package the entries are returned in registry declaration order.
+ *
+ * Only packages present in {@link PACKAGE_SECRETS_REGISTRY} contribute entries;
+ * unknown package names are silently ignored — this makes the call site resilient
+ * to future capability flags whose packages have no secrets.
+ */
 declare const secretsForPackages: (packageNames: ReadonlyArray<string>) => SecretEntry[];
 /** The canonical project-config filename probed at the project root. */
 declare const LUNORA_CONFIG_FILE = "lunora.json";
 /**
-* The parsed `remote` preference from `lunora.json`:
-*
-* - `true` / `false` — the boolean form: enable or explicitly disable remote dev.
-* - `undefined` — no usable preference (file absent, key absent, or malformed).
-*
-* The object form (scoping which binding kinds go remote) is reserved for a
-* future increment; for now an object value is treated as "enabled" (truthy
-* presence) so forward-written configs still turn remote on.
-*/
+ * The parsed `remote` preference from `lunora.json`:
+ *
+ * - `true` / `false` — the boolean form: enable or explicitly disable remote dev.
+ * - `undefined` — no usable preference (file absent, key absent, or malformed).
+ *
+ * The object form (scoping which binding kinds go remote) is reserved for a
+ * future increment; for now an object value is treated as "enabled" (truthy
+ * presence) so forward-written configs still turn remote on.
+ */
 type RemotePreference = boolean | undefined;
 /** The structural slice of `lunora.json` Lunora reads. */
 interface LunoraProjectConfig {
   remote?: unknown;
 }
 /**
-* Interpret a raw `remote` value into a tri-state preference. A boolean passes
-* through; an object is treated as enabled (the documented-but-not-yet-honored
-* scoping form is still an opt-in); anything else (string, number, null) is no
-* preference.
-*/
+ * Interpret a raw `remote` value into a tri-state preference. A boolean passes
+ * through; an object is treated as enabled (the documented-but-not-yet-honored
+ * scoping form is still an opt-in); anything else (string, number, null) is no
+ * preference.
+ */
 declare const interpretRemote: (value: unknown) => RemotePreference;
 /**
-* Read the project's `remote` preference from `lunora.json`, or `undefined` when
-* there's no usable preference. Best-effort: never throws — a missing file,
-* parse error, or unexpected shape all collapse to `undefined` so the caller
-* falls through to the env/flag layers.
-*/
+ * Read the project's `remote` preference from `lunora.json`, or `undefined` when
+ * there's no usable preference. Best-effort: never throws — a missing file,
+ * parse error, or unexpected shape all collapse to `undefined` so the caller
+ * falls through to the env/flag layers.
+ */
 declare const readProjectRemotePreference: (projectRoot: string) => RemotePreference;
 /**
-* Whether we can interactively prompt — stdin must be a TTY. In CI / piped
-* contexts this is false, and callers should fall back to a non-interactive
-* default (skip, or require an explicit `--yes`) rather than hang on a read.
-*/
+ * Whether we can interactively prompt — stdin must be a TTY. In CI / piped
+ * contexts this is false, and callers should fall back to a non-interactive
+ * default (skip, or require an explicit `--yes`) rather than hang on a read.
+ */
 declare const isInteractive: () => boolean;
 /**
-* Ask a yes/no question on stdin. With `defaultYes`, an empty answer (just
-* Enter) counts as yes and the prompt should read `[Y/n]`; otherwise empty is
-* no (`[y/N]`). Shared by the CLI (`reset`, `dev`) and the Vite dev server.
-*/
+ * Ask a yes/no question on stdin. With `defaultYes`, an empty answer (just
+ * Enter) counts as yes and the prompt should read `[Y/n]`; otherwise empty is
+ * no (`[y/N]`). Shared by the CLI (`reset`, `dev`) and the Vite dev server.
+ */
 declare const promptYesNo: (prompt: string, options?: {
   defaultYes?: boolean;
 }) => Promise<boolean>;
 /**
-* Build a default-yes `confirm(message)` for the scaffolders' `ensureDevVariables`:
-* an interactive `[Y/n]` prompt (optionally prefixed, e.g. `"[lunora] "`) when
-* stdin is a TTY, or an immediate `false` otherwise — so CI declines silently
-* instead of blocking. Keeps the "non-interactive ⇒ decline" policy in one place
-* rather than re-stated at every call site.
-*/
+ * Build a default-yes `confirm(message)` for the scaffolders' `ensureDevVariables`:
+ * an interactive `[Y/n]` prompt (optionally prefixed, e.g. `"[lunora] "`) when
+ * stdin is a TTY, or an immediate `false` otherwise — so CI declines silently
+ * instead of blocking. Keeps the "non-interactive ⇒ decline" policy in one place
+ * rather than re-stated at every call site.
+ */
 declare const createConfirm: (prefix?: string) => ((message: string) => Promise<boolean>);
 /** One choice in a {@link promptSelect} list. `value` is returned; `label` (and optional `description`) are shown. */
 interface SelectOption<T extends string> {
@@ -678,50 +650,50 @@ interface SelectOption<T extends string> {
   value: T;
 }
 /**
-* Ask the user to pick one option from a numbered list on stdin. Accepts the
-* 1-based number or the option's `value`/`label` typed verbatim; an empty answer
-* (just Enter) takes `settings.default`. In a non-interactive context (CI /
-* piped — no TTY) it never reads and returns `settings.default` (or `undefined`),
-* mirroring {@link createConfirm}'s "non-interactive ⇒ fall back" policy so
-* automation never blocks.
-*/
+ * Ask the user to pick one option from a numbered list on stdin. Accepts the
+ * 1-based number or the option's `value`/`label` typed verbatim; an empty answer
+ * (just Enter) takes `settings.default`. In a non-interactive context (CI /
+ * piped — no TTY) it never reads and returns `settings.default` (or `undefined`),
+ * mirroring {@link createConfirm}'s "non-interactive ⇒ fall back" policy so
+ * automation never blocks.
+ */
 declare const promptSelect: <T extends string>(message: string, options: ReadonlyArray<SelectOption<T>>, settings?: {
   default?: T;
 }) => Promise<T | undefined>;
 /**
-* Ask a free-text question on stdin, returning the trimmed answer. An empty
-* answer (just Enter) takes `settings.default`. In a non-interactive context
-* (CI / piped — no TTY) it never reads and returns `settings.default` (or
-* `undefined`), mirroring {@link promptSelect}'s "non-interactive ⇒ fall back"
-* policy so automation never blocks.
-*/
+ * Ask a free-text question on stdin, returning the trimmed answer. An empty
+ * answer (just Enter) takes `settings.default`. In a non-interactive context
+ * (CI / piped — no TTY) it never reads and returns `settings.default` (or
+ * `undefined`), mirroring {@link promptSelect}'s "non-interactive ⇒ fall back"
+ * policy so automation never blocks.
+ */
 declare const promptText: (message: string, settings?: {
   default?: string;
 }) => Promise<string | undefined>;
 /** One choice in a {@link promptMultiSelect} list. Identical shape to {@link SelectOption}; `value` is returned when picked. */
 type MultiSelectOption<T extends string> = SelectOption<T>;
 /**
-* Ask the user to pick zero or more options from a numbered list on stdin.
-* Accepts a comma- or space-separated list of 1-based numbers and/or option
-* `value`/`label`s typed verbatim; an empty answer (just Enter) takes
-* `settings.defaults`. In a non-interactive context (CI / piped — no TTY) it
-* never reads and returns `settings.defaults ?? []`, mirroring {@link promptSelect}'s
-* "non-interactive ⇒ fall back" policy so automation never blocks. Unknown
-* tokens are ignored; the returned list is de-duplicated and preserves option
-* order.
-*/
+ * Ask the user to pick zero or more options from a numbered list on stdin.
+ * Accepts a comma- or space-separated list of 1-based numbers and/or option
+ * `value`/`label`s typed verbatim; an empty answer (just Enter) takes
+ * `settings.defaults`. In a non-interactive context (CI / piped — no TTY) it
+ * never reads and returns `settings.defaults ?? []`, mirroring {@link promptSelect}'s
+ * "non-interactive ⇒ fall back" policy so automation never blocks. Unknown
+ * tokens are ignored; the returned list is de-duplicated and preserves option
+ * order.
+ */
 declare const promptMultiSelect: <T extends string>(message: string, options: ReadonlyArray<MultiSelectOption<T>>, settings?: {
   defaults?: ReadonlyArray<T>;
 }) => Promise<T[]>;
 /**
-* A container/workflow that is declared (so codegen emits its class) but the
-* worker entry never re-exports — the one wiring step the generators can't always
-* do for the developer. wrangler rejects a `class_name` the deployed worker
-* doesn't export, so a deploy fails late on this; surfacing it as structured data
-* lets the Vite plugin raise it in the dev error overlay (not just the console)
-* the moment the gap appears. The human-readable form is also folded into
-* {@link ReconcileBindingsResult.warnings}.
-*/
+ * A container/workflow that is declared (so codegen emits its class) but the
+ * worker entry never re-exports — the one wiring step the generators can't always
+ * do for the developer. wrangler rejects a `class_name` the deployed worker
+ * doesn't export, so a deploy fails late on this; surfacing it as structured data
+ * lets the Vite plugin raise it in the dev error overlay (not just the console)
+ * the moment the gap appears. The human-readable form is also folded into
+ * {@link ReconcileBindingsResult.warnings}.
+ */
 interface ExportGap {
   /** Generated class wrangler needs exported, e.g. `OrderPipelineWorkflow`. */
   className: string;
@@ -738,10 +710,10 @@ interface ReconcileBindingsResult {
   /** `true` when `wrangler.jsonc` was rewritten. */
   changed: boolean;
   /**
-  * Declared containers/workflows the worker entry doesn't re-export — the
-  * structured form of the corresponding `warnings` entries, for the dev error
-  * overlay. Empty when every declaration is wired.
-  */
+   * Declared containers/workflows the worker entry doesn't re-export — the
+   * structured form of the corresponding `warnings` entries, for the dev error
+   * overlay. Empty when every declaration is wired.
+   */
   exportGaps: ExportGap[];
   /** Reason reconciliation was skipped, for logging. */
   reason?: string;
@@ -751,11 +723,11 @@ interface ReconcileBindingsResult {
   wranglerPath?: string;
 }
 /**
-* Reconcile inferred Durable Object / D1 bindings into `wrangler.jsonc`.
-*
-* Writes only when something is missing; returns `changed: false` when the
-* config already satisfies the inferred needs.
-*/
+ * Reconcile inferred Durable Object / D1 bindings into `wrangler.jsonc`.
+ *
+ * Writes only when something is missing; returns `changed: false` when the
+ * config already satisfies the inferred needs.
+ */
 declare const reconcileWranglerBindings: (projectRoot: string, inferred: InferredBindings) => ReconcileBindingsResult;
 interface ReconcileCompatibilityDateResult {
   /** `true` when `wrangler.jsonc` was rewritten. */
@@ -768,9 +740,9 @@ interface ReconcileCompatibilityDateResult {
   wranglerPath?: string;
 }
 /**
-* Reconcile the `compatibility_date` in `wrangler.jsonc` when Workers Cache
-* is enabled but the date is below the minimum required.
-*/
+ * Reconcile the `compatibility_date` in `wrangler.jsonc` when Workers Cache
+ * is enabled but the date is below the minimum required.
+ */
 declare const reconcileWranglerCompatibilityDate: (projectRoot: string) => ReconcileCompatibilityDateResult;
 interface ReconcileResult {
   /** `true` when `wrangler.jsonc` was rewritten. */
@@ -781,38 +753,38 @@ interface ReconcileResult {
   wranglerPath?: string;
 }
 /**
-* Reconcile the codegen-derived cron schedules into the project's
-* `wrangler.jsonc` `triggers.crons` array, preserving comments and formatting
-* via `jsonc-parser`'s structural edits.
-*
-* When `triggers.crons` already matches `cronTriggers`, nothing is written (so
-* we don't churn the file or trip the dev server's file watcher). When the
-* project declares no crons, a stale non-empty array is cleared so removed
-* crons stop firing.
-*
-* This intentionally writes the SAME `triggers.crons` shape the
-* `@lunora/config` validator accepts, so the wrangler validator never fights
-* the generated value.
-*/
+ * Reconcile the codegen-derived cron schedules into the project's
+ * `wrangler.jsonc` `triggers.crons` array, preserving comments and formatting
+ * via `jsonc-parser`'s structural edits.
+ *
+ * When `triggers.crons` already matches `cronTriggers`, nothing is written (so
+ * we don't churn the file or trip the dev server's file watcher). When the
+ * project declares no crons, a stale non-empty array is cleared so removed
+ * crons stop firing.
+ *
+ * This intentionally writes the SAME `triggers.crons` shape the
+ * `@lunora/config` validator accepts, so the wrangler validator never fights
+ * the generated value.
+ */
 declare const reconcileWranglerCrons: (projectRoot: string, cronTriggers: ReadonlyArray<string>) => ReconcileResult;
 /**
-* The wrangler config sections Lunora can safely flip to remote mode in dev,
-* each with the human label used in logs and the structural `shape` the entry
-* lives in.
-*
-* `"array"` is a top-level array of binding objects (`d1_databases`,
-* `kv_namespaces`, `r2_buckets`, `vectorize`, `services`). `"producers"` is
-* `queues.producers[]` — consumers are NOT remoted (their schema has no `remote`
-* field) and the edit path is two levels deep. `"object"` is a single binding
-* object, not an array (`ai`), whose edit path targets the section key directly.
-*
-* Every kind here was confirmed against `wrangler/config-schema.json`: the
-* entry's schema declares a `remote` property. Deliberately omits
-* `durable_objects` (no CF remote-DO mode; shards stay local) and sections whose
-* schema has no `remote` field (`hyperdrive`, `analytics_engine_datasets`,
-* `secrets_store_secrets`, queue consumers, …). Widening further is a one-line
-* table edit.
-*/
+ * The wrangler config sections Lunora can safely flip to remote mode in dev,
+ * each with the human label used in logs and the structural `shape` the entry
+ * lives in.
+ *
+ * `"array"` is a top-level array of binding objects (`d1_databases`,
+ * `kv_namespaces`, `r2_buckets`, `vectorize`, `services`). `"producers"` is
+ * `queues.producers[]` — consumers are NOT remoted (their schema has no `remote`
+ * field) and the edit path is two levels deep. `"object"` is a single binding
+ * object, not an array (`ai`), whose edit path targets the section key directly.
+ *
+ * Every kind here was confirmed against `wrangler/config-schema.json`: the
+ * entry's schema declares a `remote` property. Deliberately omits
+ * `durable_objects` (no CF remote-DO mode; shards stay local) and sections whose
+ * schema has no `remote` field (`hyperdrive`, `analytics_engine_datasets`,
+ * `secrets_store_secrets`, queue consumers, …). Widening further is a one-line
+ * table edit.
+ */
 declare const REMOTE_ELIGIBLE_KEYS: {
   readonly ai: {
     readonly label: "AI";
@@ -856,11 +828,11 @@ interface RemoteBindingPlan {
   /** Short kind label for logging (`"D1"`, `"KV"`, `"R2"`, `"Vectorize"`, …). */
   kind: string;
   /**
-  * The jsonc edit path within {@link RemoteBindingPlan.section}, relative to
-  * the section key: `[index]` for an `"array"` section, `["producers", index]`
-  * for a queue producer, or `[]` for the single-object `ai` section. The
-  * materializer prepends the section key and appends `"remote"`.
-  */
+   * The jsonc edit path within {@link RemoteBindingPlan.section}, relative to
+   * the section key: `[index]` for an `"array"` section, `["producers", index]`
+   * for a queue producer, or `[]` for the single-object `ai` section. The
+   * materializer prepends the section key and appends `"remote"`.
+   */
   path: ReadonlyArray<number | string>;
   /** The wrangler config key the entry lives under. */
   section: RemoteEligibleKey;
@@ -878,19 +850,19 @@ interface RemoteWranglerShape {
   vectorize?: ReadonlyArray<BindingEntry | null | undefined>;
 }
 /**
-* Inspect a parsed wrangler config and list every eligible binding that should
-* be flipped to remote mode. Pure — no file-system access, no mutation. An
-* entry already carrying `"remote": true` is still reported (so logging is
-* complete) but the materializer's edit is a harmless no-op for it.
-*/
+ * Inspect a parsed wrangler config and list every eligible binding that should
+ * be flipped to remote mode. Pure — no file-system access, no mutation. An
+ * entry already carrying `"remote": true` is still reported (so logging is
+ * complete) but the materializer's edit is a harmless no-op for it.
+ */
 declare const planRemoteBindings: (parsed: RemoteWranglerShape) => RemoteBindingPlan[];
 /**
-* Inject `"remote": true` onto each planned binding in the config `text`,
-* comment-preservingly via jsonc edits. Pure string→string; the edits target
-* disjoint entries so applying them sequentially is safe. The edit path is
-* `[section, ...plan.path, "remote"]`, which resolves to the array element, the
-* `queues.producers[i]` entry, or the single `ai` object as the plan demands.
-*/
+ * Inject `"remote": true` onto each planned binding in the config `text`,
+ * comment-preservingly via jsonc edits. Pure string→string; the edits target
+ * disjoint entries so applying them sequentially is safe. The edit path is
+ * `[section, ...plan.path, "remote"]`, which resolves to the array element, the
+ * `queues.producers[i]` entry, or the single `ai` object as the plan demands.
+ */
 declare const injectRemoteFlags: (text: string, plans: ReadonlyArray<RemoteBindingPlan>) => string;
 interface MaterializeOptions {
   /** When `false`, the call is a no-op (returns `enabled: false`). */
@@ -899,18 +871,18 @@ interface MaterializeOptions {
 }
 interface MaterializeResult {
   /**
-  * Removes the generated temp config file. Always present and always safe to
-  * call: it is idempotent, a no-op when nothing was written (disabled /
-  * fall-through cases), and never throws if the path is already gone. The dev
-  * command calls this on every exit path (normal, signal, error).
-  */
+   * Removes the generated temp config file. Always present and always safe to
+   * call: it is idempotent, a no-op when nothing was written (disabled /
+   * fall-through cases), and never throws if the path is already gone. The dev
+   * command calls this on every exit path (normal, signal, error).
+   */
   cleanup: () => void;
   /**
-  * Absolute path to the generated temp config to pass to
-  * `wrangler dev --config`. `undefined` when remote mode is disabled, no
-  * wrangler config was found, it failed to parse, or it declared no eligible
-  * binding (nothing to remote — run plain local dev).
-  */
+   * Absolute path to the generated temp config to pass to
+   * `wrangler dev --config`. `undefined` when remote mode is disabled, no
+   * wrangler config was found, it failed to parse, or it declared no eligible
+   * binding (nothing to remote — run plain local dev).
+   */
   configPath?: string;
   /** Whether remote mode was requested at all. */
   enabled: boolean;
@@ -920,33 +892,33 @@ interface MaterializeResult {
   remoteBindings: RemoteBindingPlan[];
 }
 /**
-* Produce a temporary wrangler config with `"remote": true` on every eligible
-* binding, so `lunora dev` can run `wrangler dev --config &lt;temp>` against the
-* deployed D1/KV/R2 without touching the user's file.
-*
-* The temp file is written as a sibling of the source `wrangler.jsonc` (in the
-* project root), NOT an OS temp dir: wrangler resolves a config's relative paths
-* (`main`, `assets`, `migrations_dir`, …) against the **config file's own
-* directory**, so a temp config in `/tmp` would make wrangler look for
-* `/tmp/src/server.ts` and fail to start the worker. Keeping it beside the real
-* config preserves those relative paths. Returns `configPath: undefined` (with a
-* `reason`) for every fall-through case so the caller degrades to plain local
-* dev instead of failing.
-*/
+ * Produce a temporary wrangler config with `"remote": true` on every eligible
+ * binding, so `lunora dev` can run `wrangler dev --config &lt;temp>` against the
+ * deployed D1/KV/R2 without touching the user's file.
+ *
+ * The temp file is written as a sibling of the source `wrangler.jsonc` (in the
+ * project root), NOT an OS temp dir: wrangler resolves a config's relative paths
+ * (`main`, `assets`, `migrations_dir`, …) against the **config file's own
+ * directory**, so a temp config in `/tmp` would make wrangler look for
+ * `/tmp/src/server.ts` and fail to start the worker. Keeping it beside the real
+ * config preserves those relative paths. Returns `configPath: undefined` (with a
+ * `reason`) for every fall-through case so the caller degrades to plain local
+ * dev instead of failing.
+ */
 declare const materializeRemoteWranglerConfig: (options: MaterializeOptions) => MaterializeResult;
 /**
-* Parse a `LUNORA_REMOTE` env value into the on/off decision. Truthy when set to
-* `"1"` or `"true"` (case-insensitive); anything else — unset, `"0"`, `"false"`,
-* empty — is off. Mirrors the `"1" | "true"` convention used across the runtime.
-*/
+ * Parse a `LUNORA_REMOTE` env value into the on/off decision. Truthy when set to
+ * `"1"` or `"true"` (case-insensitive); anything else — unset, `"0"`, `"false"`,
+ * empty — is off. Mirrors the `"1" | "true"` convention used across the runtime.
+ */
 declare const isRemoteEnvEnabled: (value: string | undefined) => boolean;
 /** The three inputs that can switch remote-binding dev on, in precedence order. */
 interface RemoteEnableInputs {
   /**
-  * The `remote` preference from `lunora.json` (the lowest-priority signal).
-  * `undefined` means "no project preference"; an explicit `false` here loses
-  * to neither the flag nor the env when those are absent — it just stays off.
-  */
+   * The `remote` preference from `lunora.json` (the lowest-priority signal).
+   * `undefined` means "no project preference"; an explicit `false` here loses
+   * to neither the flag nor the env when those are absent — it just stays off.
+   */
   configPreference?: boolean;
   /** The raw `LUNORA_REMOTE` env value (parsed with {@link isRemoteEnvEnabled}). */
   envValue?: string;
@@ -954,44 +926,44 @@ interface RemoteEnableInputs {
   flag?: boolean;
 }
 /**
-* Resolve whether remote-binding dev is on, with a clear precedence:
-*
-* 1. an explicit `--remote` flag (highest — a deliberate per-invocation choice),
-* 2. then `LUNORA_REMOTE` in the environment,
-* 3. then the `remote` key in `lunora.json` (lowest — a project default).
-*
-* The flag and env are one-directional (they can only turn remote *on*); only
-* the config preference carries a meaningful `false`, and it applies solely when
-* neither stronger signal is present. So a project that sets `"remote": false`
-* is still overridable per-run by `--remote` or `LUNORA_REMOTE=1`.
-*/
+ * Resolve whether remote-binding dev is on, with a clear precedence:
+ *
+ * 1. an explicit `--remote` flag (highest — a deliberate per-invocation choice),
+ * 2. then `LUNORA_REMOTE` in the environment,
+ * 3. then the `remote` key in `lunora.json` (lowest — a project default).
+ *
+ * The flag and env are one-directional (they can only turn remote *on*); only
+ * the config preference carries a meaningful `false`, and it applies solely when
+ * neither stronger signal is present. So a project that sets `"remote": false`
+ * is still overridable per-run by `--remote` or `LUNORA_REMOTE=1`.
+ */
 declare const resolveRemoteEnabled: (inputs: RemoteEnableInputs) => boolean;
 /** Core (always-scaffolded) secrets followed by the package-specific ones for the detected capabilities. */
 declare const requiredSecrets: (packageNames: ReadonlyArray<string>) => SecretEntry[];
 /**
-* Whether an (already-unquoted) value looks like a fill-me-in placeholder —
-* empty, angle-bracketed, or containing a known marker — rather than a real
-* value. Used both when scaffolding (which values to regenerate) and by
-* `lunora env doctor` (which set values are still unfilled).
-*/
+ * Whether an (already-unquoted) value looks like a fill-me-in placeholder —
+ * empty, angle-bracketed, or containing a known marker — rather than a real
+ * value. Used both when scaffolding (which values to regenerate) and by
+ * `lunora env doctor` (which set values are still unfilled).
+ */
 declare const isPlaceholderValue: (value: string) => boolean;
 /**
-* True for a secret-looking key whose value Lunora can mint locally (a random
-* 32-byte hex, like `openssl rand -hex 32`) — e.g. `AUTH_SECRET`,
-* `LUNORA_ADMIN_TOKEN`, `STORAGE_SIGNING_SECRET`. False for provider-issued keys
-* ({@link PROVIDER_SECRET_KEYS}) and any non-secret key.
-*/
+ * True for a secret-looking key whose value Lunora can mint locally (a random
+ * 32-byte hex, like `openssl rand -hex 32`) — e.g. `AUTH_SECRET`,
+ * `LUNORA_ADMIN_TOKEN`, `STORAGE_SIGNING_SECRET`. False for provider-issued keys
+ * ({@link PROVIDER_SECRET_KEYS}) and any non-secret key.
+ */
 declare const isMintableSecretKey: (key: string) => boolean;
 /** Mint a fresh strong secret value — 64 hex chars (32 bytes), like `openssl rand -hex 32`. */
 declare const generateSecretValue: (randomHex?: (bytes: number) => string) => string;
 /**
-* The outcome of planning a scaffold — a discriminated union so the orchestrator
-* never has to re-derive whether `content` is present.
-*
-* `exists`: `.dev.vars` is already there; nothing to do.
-* `no-example`: nothing to scaffold from (stay silent — the project may not use secrets).
-* `generate`: write `content`, a copy of the example with secret-looking placeholders replaced by fresh random hex (`generatedKeys` lists which).
-*/
+ * The outcome of planning a scaffold — a discriminated union so the orchestrator
+ * never has to re-derive whether `content` is present.
+ *
+ * `exists`: `.dev.vars` is already there; nothing to do.
+ * `no-example`: nothing to scaffold from (stay silent — the project may not use secrets).
+ * `generate`: write `content`, a copy of the example with secret-looking placeholders replaced by fresh random hex (`generatedKeys` lists which).
+ */
 type ScaffoldPlan = {
   content: string;
   generatedKeys: string[];
@@ -1004,7 +976,8 @@ type ScaffoldPlan = {
 /** Decide whether (and what) to scaffold. Pure — given the current state of the two files. */
 declare const planDevVariablesScaffold: (input: {
   devVarsExists: boolean;
-  exampleContent: string | undefined; /** Injectable for deterministic tests; defaults to `crypto.randomBytes`. */
+  exampleContent: string | undefined;
+  /** Injectable for deterministic tests; defaults to `crypto.randomBytes`. */
   randomHex?: (bytes: number) => string;
 }) => ScaffoldPlan;
 interface AugmentPlan {
@@ -1016,22 +989,23 @@ interface AugmentPlan {
   missingKeys: string[];
 }
 /**
-* Plan how to top up an existing `.dev.vars` from the example: every example key
-* not already present becomes an appended line (secret placeholders filled with
-* fresh random hex, other values copied). Pure — no I/O. Empty `missingKeys`
-* means the file is already complete.
-*/
+ * Plan how to top up an existing `.dev.vars` from the example: every example key
+ * not already present becomes an appended line (secret placeholders filled with
+ * fresh random hex, other values copied). Pure — no I/O. Empty `missingKeys`
+ * means the file is already complete.
+ */
 declare const planDevVariablesAugment: (input: {
   exampleContent: string;
-  existingContent: string; /** Injectable for deterministic tests; defaults to `crypto.randomBytes`. */
+  existingContent: string;
+  /** Injectable for deterministic tests; defaults to `crypto.randomBytes`. */
   randomHex?: (bytes: number) => string;
 }) => AugmentPlan;
 interface EnsureDevVariablesDeps {
   /**
-  * Ask the user to confirm generating the file. Return `true` to generate.
-  * Consumers pass a TTY-aware prompt; in non-interactive contexts they should
-  * resolve `false` (we then report `"declined"` and the caller can hint).
-  */
+   * Ask the user to confirm generating the file. Return `true` to generate.
+   * Consumers pass a TTY-aware prompt; in non-interactive contexts they should
+   * resolve `false` (we then report `"declined"` and the caller can hint).
+   */
   confirm: (message: string) => Promise<boolean>;
   cwd: string;
   /** Emit a human-facing line (success / hint). */
@@ -1050,41 +1024,41 @@ interface EnsureDevVariablesResult {
   status: EnsureDevVariablesStatus;
 }
 /**
-* Reconcile the project's `.dev.vars` with its `.dev.vars.example`:
-*
-* - file missing → offer to generate it (secret placeholders auto-filled);
-* - file present but missing keys the example lists → offer to append them;
-* - file present and complete → nothing to do.
-*
-* Prompts via `confirm` (skipped when `yes`); never overwrites existing values.
-* Returns what happened so the caller can tailor any follow-up. Shared by
-* `lunora dev` and the `@lunora/vite` dev server. All side effects funnel
-* through `confirm`/`info`/`randomHex`.
-*/
+ * Reconcile the project's `.dev.vars` with its `.dev.vars.example`:
+ *
+ * - file missing → offer to generate it (secret placeholders auto-filled);
+ * - file present but missing keys the example lists → offer to append them;
+ * - file present and complete → nothing to do.
+ *
+ * Prompts via `confirm` (skipped when `yes`); never overwrites existing values.
+ * Returns what happened so the caller can tailor any follow-up. Shared by
+ * `lunora dev` and the `@lunora/vite` dev server. All side effects funnel
+ * through `confirm`/`info`/`randomHex`.
+ */
 declare const ensureDevVariables: (deps: EnsureDevVariablesDeps) => Promise<EnsureDevVariablesResult>;
 /**
-* Build the text that should be merged into `.dev.vars.example` for the given
-* set of package names. Only entries whose key is not already present in
-* `existingKeys` are included (additive / idempotent). Returns an empty string
-* when there is nothing to add.
-*
-* The output is grouped by package with a blank-line separator so the file
-* reads cleanly when multiple packages each contribute several keys.
-*
-* **Safety invariant:** this function never writes a real secret — every value
-* in the output is the entry's `placeholderValue`.
-*/
+ * Build the text that should be merged into `.dev.vars.example` for the given
+ * set of package names. Only entries whose key is not already present in
+ * `existingKeys` are included (additive / idempotent). Returns an empty string
+ * when there is nothing to add.
+ *
+ * The output is grouped by package with a blank-line separator so the file
+ * reads cleanly when multiple packages each contribute several keys.
+ *
+ * **Safety invariant:** this function never writes a real secret — every value
+ * in the output is the entry's `placeholderValue`.
+ */
 declare const buildPackageSecretsBlock: (packageNames: ReadonlyArray<string>, existingKeys: ReadonlySet<string>) => string;
 /**
-* Write (or update) `.dev.vars.example` so that it contains the secrets
-* required by `packageNames`. Existing lines are never removed or rewritten;
-* new entries are appended (with a blank-line separator after existing content).
-*
-* Idempotent: re-running with the same `packageNames` does not duplicate keys
-* already in the file. Returns the list of keys that were actually appended.
-*
-* **Safety invariant:** only placeholder values are written — no real secrets.
-*/
+ * Write (or update) `.dev.vars.example` so that it contains the secrets
+ * required by `packageNames`. Existing lines are never removed or rewritten;
+ * new entries are appended (with a blank-line separator after existing content).
+ *
+ * Idempotent: re-running with the same `packageNames` does not duplicate keys
+ * already in the file. Returns the list of keys that were actually appended.
+ *
+ * **Safety invariant:** only placeholder values are written — no real secrets.
+ */
 declare const ensureDevVariablesExample: (cwd: string, packageNames: ReadonlyArray<string>) => string[];
 interface DevSecretsFillPlan {
   /** {@link CORE_SECRETS} keys appended because they were absent (each generated). */
@@ -1095,19 +1069,19 @@ interface DevSecretsFillPlan {
   filledKeys: string[];
 }
 /**
-* Plan the in-place generation of dev secrets for a `.dev.vars`. First, every
-* line whose KEY looks like a secret (`*_SECRET`, `*_TOKEN`, `*_KEY`,
-* `*_PASSWORD`) and whose value is empty or a placeholder gets a freshly
-* generated value — so a `lunora add`-scaffolded `.dev.vars` (which writes each
-* secret blank) becomes usable on `lunora dev` / `vite dev` without the user
-* running `openssl` by hand. Second, any {@link CORE_SECRETS} key absent from
-* the file is appended (generated) — notably `LUNORA_ADMIN_TOKEN`, which the
-* local Studio needs to call the worker's admin gate in dev (without it the
-* Studio shows its login gate).
-*
-* Pure (given `randomHex`): real (non-placeholder) values are never touched, and
-* comments + non-secret entries are preserved verbatim.
-*/
+ * Plan the in-place generation of dev secrets for a `.dev.vars`. First, every
+ * line whose KEY looks like a secret (`*_SECRET`, `*_TOKEN`, `*_KEY`,
+ * `*_PASSWORD`) and whose value is empty or a placeholder gets a freshly
+ * generated value — so a `lunora add`-scaffolded `.dev.vars` (which writes each
+ * secret blank) becomes usable on `lunora dev` / `vite dev` without the user
+ * running `openssl` by hand. Second, any {@link CORE_SECRETS} key absent from
+ * the file is appended (generated) — notably `LUNORA_ADMIN_TOKEN`, which the
+ * local Studio needs to call the worker's admin gate in dev (without it the
+ * Studio shows its login gate).
+ *
+ * Pure (given `randomHex`): real (non-placeholder) values are never touched, and
+ * comments + non-secret entries are preserved verbatim.
+ */
 declare const planDevSecretsFill: (input: {
   existingContent: string;
   randomHex?: (bytes: number) => string;
@@ -1121,18 +1095,18 @@ interface FillDevSecretsResult {
   status: "created" | "filled" | "unchanged";
 }
 /**
-* Generate any missing/empty dev secrets in the project's `.dev.vars`, in place.
-*
-* Complements {@link ensureDevVariables} (which scaffolds `.dev.vars` from
-* `.dev.vars.example`). A `lunora add`-scaffolded project writes secrets blank
-* straight into `.dev.vars` (no example) and never includes `LUNORA_ADMIN_TOKEN`
-* — so the worker boots with empty secrets and the Studio shows its login gate.
-* This fills those gaps at dev startup, so both `lunora dev` and the
-* `@lunora/vite` dev server give a working project with zero manual `openssl`.
-*
-* Never overwrites a real (non-placeholder) value. The write is atomic + owner-
-* only (temp + rename, `mode: 0o600`), matching the other `.dev.vars` writers.
-*/
+ * Generate any missing/empty dev secrets in the project's `.dev.vars`, in place.
+ *
+ * Complements {@link ensureDevVariables} (which scaffolds `.dev.vars` from
+ * `.dev.vars.example`). A `lunora add`-scaffolded project writes secrets blank
+ * straight into `.dev.vars` (no example) and never includes `LUNORA_ADMIN_TOKEN`
+ * — so the worker boots with empty secrets and the Studio shows its login gate.
+ * This fills those gaps at dev startup, so both `lunora dev` and the
+ * `@lunora/vite` dev server give a working project with zero manual `openssl`.
+ *
+ * Never overwrites a real (non-placeholder) value. The write is atomic + owner-
+ * only (temp + rename, `mode: 0o600`), matching the other `.dev.vars` writers.
+ */
 declare const fillDevSecrets: (deps: {
   cwd: string;
   info?: (message: string) => void;
@@ -1149,11 +1123,11 @@ interface AddOptionalColumnEdit {
   readonly kind: "addOptionalColumn";
   readonly table: string;
   /**
-  * Inner validator expression text WITHOUT the `v.optional(...)` wrapper, e.g.
-  * `v.string()`. Always wrapped in `v.optional(...)` on apply, because only
-  * optional columns are additive-safe (a required column needs a backfill
-  * migration).
-  */
+   * Inner validator expression text WITHOUT the `v.optional(...)` wrapper, e.g.
+   * `v.string()`. Always wrapped in `v.optional(...)` on apply, because only
+   * optional columns are additive-safe (a required column needs a backfill
+   * migration).
+   */
   readonly validator: string;
 }
 /** Add a secondary index to an existing table. */
@@ -1167,9 +1141,9 @@ interface AddIndexEdit {
 /** Additive edits — the only requests {@link applyAdditiveEdit} applies. */
 type AdditiveEdit = AddIndexEdit | AddOptionalColumnEdit | AddTableEdit;
 /**
-* Destructive edits — never applied directly; routed to the migration handoff
-* (plan 024 Item 5). Carried as data so the editor can describe the request.
-*/
+ * Destructive edits — never applied directly; routed to the migration handoff
+ * (plan 024 Item 5). Carried as data so the editor can describe the request.
+ */
 interface DestructiveEdit {
   readonly column?: string;
   readonly kind: "changeColumnType" | "dropColumn" | "dropTable" | "makeRequired" | "renameColumn";
@@ -1180,9 +1154,9 @@ interface DestructiveEdit {
 /** Any edit the editor can request. */
 type SchemaEdit = AdditiveEdit | DestructiveEdit;
 /**
-* Classify an edit request. Additive edits ({@link AdditiveEdit}) apply
-* directly; everything else changes stored data and is destructive.
-*/
+ * Classify an edit request. Additive edits ({@link AdditiveEdit}) apply
+ * directly; everything else changes stored data and is destructive.
+ */
 declare const classifyEdit: (edit: SchemaEdit) => "additive" | "destructive";
 /** Failure reasons an additive edit can report. */
 type ApplyFailureReason = "aliased-define-schema" | "destructive" | "duplicate-column" | "duplicate-index" | "duplicate-table" | "invalid-identifier" | "invalid-validator" | "no-define-schema" | "non-object-argument" | "unknown-table";
@@ -1195,10 +1169,10 @@ type ApplyEditResult = {
   text: string;
 };
 /**
-* Apply an **additive** edit to a schema source string, preserving formatting.
-* Destructive edits are refused with `{ ok: false, reason: "destructive" }`;
-* route them through the migration handoff (plan 024 Item 5).
-*/
+ * Apply an **additive** edit to a schema source string, preserving formatting.
+ * Destructive edits are refused with `{ ok: false, reason: "destructive" }`;
+ * route them through the migration handoff (plan 024 Item 5).
+ */
 declare const applyAdditiveEdit: (source: string, edit: SchemaEdit) => ApplyEditResult;
 /** A single declared column: its name and the raw validator expression text. */
 interface SchemaColumn {
@@ -1237,16 +1211,10 @@ type ParseSchemaResult = {
   tables: ReadonlyArray<SchemaTable>;
 };
 /**
-* Every `CallExpression` at or below a node. `getDescendantsOfKind` excludes the
-* node itself, but a table initializer often is the outermost call in the
-* `defineTable(...).global().index(...)` chain, so include it explicitly.
-*/
-
-/**
-* Parse the tables (with typed columns + indexes) out of a `lunora/schema.ts`
-* source string. Returns a tagged result so callers can render a helpful
-* message per failure mode without throwing.
-*/
+ * Parse the tables (with typed columns + indexes) out of a `lunora/schema.ts`
+ * source string. Returns a tagged result so callers can render a helpful
+ * message per failure mode without throwing.
+ */
 declare const parseSchema: (source: string) => ParseSchemaResult;
 interface SchemaInfo {
   /** Whether the lunora schema declares any `.global()` table. */
@@ -1261,16 +1229,16 @@ interface DiscoverSchemaInfoResult {
   info: SchemaInfo | undefined;
 }
 /**
-* Discover {@link SchemaInfo} for a project. Returns `{ info: undefined }` when
-* the project declares no `schema.ts` (not an error), or `{ info: undefined,
-* error }` when a present schema could not be parsed — callers decide whether a
-* parse failure is a warning (validator) or simply ignorable (inference).
-*/
+ * Discover {@link SchemaInfo} for a project. Returns `{ info: undefined }` when
+ * the project declares no `schema.ts` (not an error), or `{ info: undefined,
+ * error }` when a present schema could not be parsed — callers decide whether a
+ * parse failure is a warning (validator) or simply ignorable (inference).
+ */
 declare const discoverSchemaInfo: (projectRoot: string, schemaDirectory: string) => DiscoverSchemaInfoResult;
 /**
-* A badge: the short colored label that prefixes a line. `bg`/`fg` are hex so the
-* same value drives both colorize's `bgHex().hex()` and the tui `&lt;Text>` props.
-*/
+ * A badge: the short colored label that prefixes a line. `bg`/`fg` are hex so the
+ * same value drives both colorize's `bgHex().hex()` and the tui `&lt;Text>` props.
+ */
 interface BadgeSpec {
   bg: `#${string}`;
   fg: `#${string}`;
@@ -1286,24 +1254,24 @@ type BadgeName = LevelBadgeName | StepBadgeName;
 /** The ordered step-phase names, used to register custom pail log types. */
 declare const STEP_BADGE_NAMES: ReadonlyArray<StepBadgeName>;
 /**
-* Every badge, keyed by name. Levels get their conventional colors (red/amber/
-* green/blue/grey); step phases follow create-astro's green→purple→cyan rhythm.
-*/
+ * Every badge, keyed by name. Levels get their conventional colors (red/amber/
+ * green/blue/grey); step phases follow create-astro's green→purple→cyan rhythm.
+ */
 declare const BADGES: Record<BadgeName, BadgeSpec>;
 /**
-* Luna, the mascot: the folklore rabbit-in-the-moon — a bunny tucked inside the
-* moon disc. Pure ASCII so it renders the same everywhere (including piped logs).
-* The CLI signs off the `init` flow with it, the way create-astro closes with
-* Houston.
-*/
+ * Luna, the mascot: the folklore rabbit-in-the-moon — a bunny tucked inside the
+ * moon disc. Pure ASCII so it renders the same everywhere (including piped logs).
+ * The CLI signs off the `init` flow with it, the way create-astro closes with
+ * Houston.
+ */
 declare const LUNA_NAME = "Luna";
 declare const LUNA_SIGNOFF = "Safe travels, voyager.";
 declare const LUNA_BUNNY: string;
 /**
-* {@link LUNA_BUNNY} with its leading newline stripped, ready to render inline
-* (beside the name + sign-off). Both render paths — the tui mascot frame and the
-* pail off-TTY fallback — use this so neither re-implements the strip.
-*/
+ * {@link LUNA_BUNNY} with its leading newline stripped, ready to render inline
+ * (beside the name + sign-off). Both render paths — the tui mascot frame and the
+ * pail off-TTY fallback — use this so neither re-implements the strip.
+ */
 declare const LUNA_ART: string;
 /** The colored part of a badge — the word with one space of padding each side. */
 declare const padBadge: (text: string) => string;
@@ -1318,16 +1286,16 @@ declare const paintBadge: (spec: BadgeSpec) => string;
 /** Dim continuation text (a step's chosen answer, shown under the question). */
 declare const paintAnswer: (text: string) => string;
 /**
-* Single source of truth for "does this wrangler config enable Workers
-* Cache?" and "what compatibility_date does that require?".
-*
-* Before this module, `reconcile-compatibility-date.ts` (auto-bump) and
-* `wrangler-validator.ts` (validation) each carried their own
-* `WORKERS_CACHE_MIN_DATE` literal and their own top-level/`exports[]`
-* cache-enabled walk — two copies of the same fact that could silently drift
-* apart (a date bumped in one file without the other would either validate a
-* config the reconciler wouldn't produce, or vice versa).
-*/
+ * Single source of truth for "does this wrangler config enable Workers
+ * Cache?" and "what compatibility_date does that require?".
+ *
+ * Before this module, `reconcile-compatibility-date.ts` (auto-bump) and
+ * `wrangler-validator.ts` (validation) each carried their own
+ * `WORKERS_CACHE_MIN_DATE` literal and their own top-level/`exports[]`
+ * cache-enabled walk — two copies of the same fact that could silently drift
+ * apart (a date bumped in one file without the other would either validate a
+ * config the reconciler wouldn't produce, or vice versa).
+ */
 /** The `compatibility_date` Workers Cache (`cache.enabled: true`) requires. */
 declare const WORKERS_CACHE_MIN_DATE = "2026-05-01";
 /** The subset of a parsed `wrangler.jsonc` the cache-enabled check reads. */
@@ -1342,11 +1310,11 @@ interface WranglerCacheShape {
   } | null> | null;
 }
 /**
-* Whether Workers Cache is enabled anywhere in a parsed wrangler config — the
-* top-level `cache.enabled` toggle, or a per-export override in
-* `exports[name].cache.enabled` (Workers can scope cache per named export).
-* `undefined`/`null` (an unparsed or absent config) is treated as disabled.
-*/
+ * Whether Workers Cache is enabled anywhere in a parsed wrangler config — the
+ * top-level `cache.enabled` toggle, or a per-export override in
+ * `exports[name].cache.enabled` (Workers can scope cache per named export).
+ * `undefined`/`null` (an unparsed or absent config) is treated as disabled.
+ */
 declare const isCacheEnabled: (parsed: WranglerCacheShape | null | undefined) => boolean;
 /** Candidate wrangler config filenames, in the order every consumer probes them. */
 declare const WRANGLER_FILES: readonly ["wrangler.jsonc", "wrangler.json"];
@@ -1359,28 +1327,28 @@ interface ReadWranglerResult<T> {
   text: string;
 }
 /**
-* Read and JSONC-parse a wrangler config file. Returns the raw `text` (for
-* structural edits) alongside `parsed`, which is `undefined` when the file is
-* not valid JSONC or does not parse to an object. Allows trailing commas, as
-* wrangler does.
-*/
+ * Read and JSONC-parse a wrangler config file. Returns the raw `text` (for
+ * structural edits) alongside `parsed`, which is `undefined` when the file is
+ * not valid JSONC or does not parse to an object. Allows trailing commas, as
+ * wrangler does.
+ */
 declare const readWranglerJsonc: <T = unknown>(wranglerPath: string) => ReadWranglerResult<T>;
 /**
-* Pure scan of a `vars` map for plaintext secrets — the FS-free core, exported for
-* unit tests. A variable is flagged when, for a **string** value that is neither a
-* placeholder nor a public/publishable key, EITHER the value matches a known
-* secret shape (`secretKindOf`) OR the key name strongly implies a secret and the
-* value is long enough to plausibly be one. `kind` is the matched shape, or
-* `secret_named_var` for the key-name path.
-*/
+ * Pure scan of a `vars` map for plaintext secrets — the FS-free core, exported for
+ * unit tests. A variable is flagged when, for a **string** value that is neither a
+ * placeholder nor a public/publishable key, EITHER the value matches a known
+ * secret shape (`secretKindOf`) OR the key name strongly implies a secret and the
+ * value is long enough to plausibly be one. `kind` is the matched shape, or
+ * `secret_named_var` for the key-name path.
+ */
 declare const scanWranglerVariablesForSecrets: (variables: Record<string, unknown> | undefined, file: string) => WranglerVariableIR[];
 /**
-* Read the project's `wrangler.jsonc` and return its plaintext-secret `vars` as IR
-* for the `plaintext_secret_in_wrangler_vars` lint. Returns `[]` when there is no
-* wrangler config, it doesn't parse, or nothing looks like a secret. Scans the
-* top-level `vars` block (mirroring the existing `validateCorsVariables` scope);
-* per-environment `env.&lt;name>.vars` overrides are out of scope for now.
-*/
+ * Read the project's `wrangler.jsonc` and return its plaintext-secret `vars` as IR
+ * for the `plaintext_secret_in_wrangler_vars` lint. Returns `[]` when there is no
+ * wrangler config, it doesn't parse, or nothing looks like a secret. Scans the
+ * top-level `vars` block (mirroring the existing `validateCorsVariables` scope);
+ * per-environment `env.&lt;name>.vars` overrides are out of scope for now.
+ */
 declare const collectWranglerSecretVariables: (projectRoot: string) => WranglerVariableIR[];
 declare const REQUIRED_COMPATIBILITY_DATE: string;
 declare const REQUIRED_FLAG: string;
@@ -1389,10 +1357,10 @@ interface WranglerDurableObjectBinding {
   name?: string;
 }
 /**
-* A `tail_consumers` entry: a Worker that receives this Worker's tail events
-* (logs, exceptions, fetch metadata) for forwarding to an external sink. See
-* `withTailConsumer` for the wiring helper.
-*/
+ * A `tail_consumers` entry: a Worker that receives this Worker's tail events
+ * (logs, exceptions, fetch metadata) for forwarding to an external sink. See
+ * `withTailConsumer` for the wiring helper.
+ */
 interface TailConsumer {
   /** Optional Cloudflare environment of the consumer Worker. */
   environment?: string;
@@ -1411,10 +1379,10 @@ interface WranglerContainerEntry {
   max_instances?: number;
 }
 /**
-* A wrangler `workflows[]` entry (parsed from untrusted JSONC). Unlike
-* containers, workflows are NOT Durable Objects — the entry stands alone (no
-* `durable_objects` binding, no migration class).
-*/
+ * A wrangler `workflows[]` entry (parsed from untrusted JSONC). Unlike
+ * containers, workflows are NOT Durable Objects — the entry stands alone (no
+ * `durable_objects` binding, no migration class).
+ */
 interface WranglerWorkflowEntry {
   binding?: string;
   class_name?: string;
@@ -1550,23 +1518,23 @@ interface WranglerValidationReport {
   warnings: string[];
 }
 /**
-* Return a new `WranglerConfig` with `consumer` present in `tail_consumers`,
-* wiring this Worker to forward its tail events (logs/exceptions) to another
-* Worker that fans them out to an external sink. Pure and idempotent: an
-* existing entry with the same `service` + `environment` is left untouched
-* rather than duplicated, so it is safe to call on every codegen/deploy.
-*/
+ * Return a new `WranglerConfig` with `consumer` present in `tail_consumers`,
+ * wiring this Worker to forward its tail events (logs/exceptions) to another
+ * Worker that fans them out to an external sink. Pure and idempotent: an
+ * existing entry with the same `service` + `environment` is left untouched
+ * rather than duplicated, so it is safe to call on every codegen/deploy.
+ */
 declare const withTailConsumer: (wrangler: WranglerConfig, consumer: TailConsumer) => WranglerConfig;
 /**
-* Pure validator: given a parsed `WranglerConfig` object and an optional
-* `SchemaInfo`, produce a structured report. Performs no I/O.
-*/
+ * Pure validator: given a parsed `WranglerConfig` object and an optional
+ * `SchemaInfo`, produce a structured report. Performs no I/O.
+ */
 declare const validateWranglerConfig: (wrangler: WranglerConfig | undefined, schema?: SchemaInfo) => WranglerValidationReport;
 /**
-* Convenience alias matching the original task-spec signature
-* `validateWrangler(wranglerJson, schema)` returning
-* `{ valid, errors, warnings }`.
-*/
+ * Convenience alias matching the original task-spec signature
+ * `validateWrangler(wranglerJson, schema)` returning
+ * `{ valid, errors, warnings }`.
+ */
 declare const validateWrangler: typeof validateWranglerConfig;
 interface WranglerProjectValidationOptions {
   projectRoot: string;
@@ -1578,10 +1546,10 @@ interface WranglerProjectValidationResult {
   wranglerPath: string | undefined;
 }
 /**
-* File-system aware variant: reads `wrangler.jsonc`/`wrangler.json` from
-* the given project root, discovers the schema (if any), and delegates to
-* `validateWranglerConfig`. Returns the legacy
-* `{ problems, wranglerPath }` shape plus the structured `report`.
-*/
+ * File-system aware variant: reads `wrangler.jsonc`/`wrangler.json` from
+ * the given project root, discovers the schema (if any), and delegates to
+ * `validateWranglerConfig`. Returns the legacy
+ * `{ problems, wranglerPath }` shape plus the structured `report`.
+ */
 declare const validateWranglerProject: (options: WranglerProjectValidationOptions) => WranglerProjectValidationResult;
 export { ACCENT, AGENT_MODE_ENV, AGENT_RULES_DIR, AGENT_RULES_HINT, AGENT_RULES_HINT_ENV, type AddIndexEdit, type AddOptionalColumnEdit, type AddTableEdit, type AdditiveEdit, type AgentDetection, type AgentRulesStatus, type ApplyEditResult, type ApplyFailureReason, type AugmentPlan, BADGES, BADGE_COLUMN_WIDTH, type BadgeName, type BadgeSpec, type ClaimDevServerStateResult, type ContainerLogLevel, type ContainerLogLine, type ContainerLogSource, type ContainerLogStreamHandle, type ContainerLogStreamOptions, DEV_DAEMON_ENV, DEV_HANDOFF_ENV, DEV_LOG_FILE, DEV_LOG_FILE_ENV, DEV_STATE_DIR, DEV_STATE_FILE, DEV_VARS_EXAMPLE_FILE, DEV_VARS_FILE, DEV_VARS_KEY_PATTERN, type DestructiveEdit, type DetectedFramework, type DevSecretsFillPlan, type DevServerMode, type DevServerState, type DiscoverAgentInfoResult, type DiscoverContainerInfoResult, type DiscoverSchemaInfoResult, type DiscoverWorkflowInfoResult, type DockerLike, type EnsureDevVariablesDeps, type EnsureDevVariablesResult, type EnsureDevVariablesStatus, type ExportGap, type FillDevSecretsResult, type FrameworkClass, type FrameworkDetection, type InferOptions, type InferredAgent, type InferredBindings, type InferredContainer, type InferredWorkflow, LINKED_PROJECT_DIR, LINKED_PROJECT_FILE, LUNA_ART, LUNA_BUNNY, LUNA_NAME, LUNA_SIGNOFF, LUNORA_CONFIG_FILE, LUNORA_EVENT_SOURCE, LUNORA_SKILL_NAMES, type LevelBadgeName, type LinkedProject, type LunoraFormattedLine, type LunoraLineLevel, type LunoraProjectConfig, LunoraReporter, type MaterializeOptions, type MaterializeResult, type MultiSelectOption, PACKAGE_SECRETS_REGISTRY, type ParseSchemaResult, REMOTE_ELIGIBLE_KEYS, REQUIRED_COMPATIBILITY_DATE, REQUIRED_FLAG, ROOT_SKILL_NAME, type ReadWranglerResult, type ReconcileBindingsResult, type ReconcileCompatibilityDateResult, type ReconcileResult as ReconcileCronsResult, type RemoteBindingPlan, type RemoteEnableInputs, type RemotePreference, type RemoteWranglerShape, STEP_BADGE_NAMES, type ScaffoldPlan, type SchemaColumn, type SchemaEdit, type SchemaIndex, type SchemaInfo, type SchemaTable, type SecretEntry, type SelectOption, type StepBadgeName, type TailConsumer, WORKERS_CACHE_MIN_DATE, WRANGLER_FILES, type WranglerCacheShape, type WranglerConfig, type WranglerContainerEntry, type WranglerProjectValidationOptions, type WranglerProjectValidationResult, type WranglerValidationReport, type WranglerWorkflowEntry, applyAdditiveEdit, badgeLead, badgeWidth, buildPackageSecretsBlock, claimAgentRulesHint, claimDevServerState, classifyEdit, clearDevServerState, collectWranglerSecretVariables, createConfirm, detectAgentRules, detectAiAgent, detectFramework, discoverAgentInfo, discoverContainerInfo, discoverSchemaInfo, discoverWorkflowInfo, ensureDevVariables, ensureDevVariablesExample as ensureDevVarsExample, fillDevSecrets, findWranglerFile, formatLunoraEvent, generateSecretValue, inferLunoraBindings, injectRemoteFlags, interpretRemote, isCacheEnabled, isInteractive, isMintableSecretKey, isPlaceholderValue, isProcessAlive, isRecordedProcessCurrent, isRemoteEnvEnabled, materializeRemoteWranglerConfig, packageNamesFromBindings, padBadge, paintAnswer, paintBadge, parseDevVariableEntries, parseSchema, planDevSecretsFill, planDevVariablesAugment, planDevVariablesScaffold, planRemoteBindings, promptMultiSelect, promptSelect, promptText, promptYesNo, readDevServerState, readLinkedProject, readLiveDevServerState, readProjectDependencyNames, readProjectRemotePreference, readWranglerJsonc, reconcileWranglerBindings, reconcileWranglerCompatibilityDate, reconcileWranglerCrons, requiredSecrets, resolveRemoteEnabled, scanWranglerVariablesForSecrets, secretsForPackages, streamContainerLogs, updateDevServerState, validateWrangler, validateWranglerConfig, validateWranglerProject, withTailConsumer, writeDevServerState, writeLinkedProject };