@voltro/cli 0.43.1 → 0.44.0

package/CHANGELOG.md

@@ -39,6 +39,71 @@ _Changes staged for the next release accumulate here (rolled up from
 
 ---
 
+## [0.44.0] — 2026-08-19
+
+### ⚠ BREAKING
+
+- **@voltro/data-transfer, @voltro/cli** — `runImport` returns an `ImportOutcome` instead of the bundle's `Manifest`, and `--mode replace` runs as ONE transaction by default.
+
+  **Why the return type changed.** The summary line counted the rows the BUNDLE carries, not the rows the run wrote. Those differ most exactly where it matters: a bundle directory carries its own resume ledger, so a copied directory imports nothing — correctly, with a warning naming the file to delete — and the run then printed `import complete … rows: 242950` over a target it had not touched. The warning was one line above, which is one line too far for anyone piping the output through `tail -1`. The outcome carries `rowsWritten`, `rowsSkipped` and `fullyResumed`, the CLI reports written-vs-carried, and a fully-skipped run says so on its LAST line.
+
+  Migration: `runImport(...)` now resolves to `{ manifest, tablesWritten, rowsWritten, tablesSkipped, rowsSkipped, fullyResumed }`. Read `.manifest` where you read the manifest before.
+
+  **Why replace is atomic now.** The all-or-nothing guarantee was written for the emptying step, and read — reasonably — as covering the run. A replace that died partway through the LOAD left the target emptied of its old rows and holding part of the new ones, measured on a live instance over sixteen minutes. There is no useful state for a replace to stop in, so it is a default rather than a flag you have to know about. It also closes the window that produced that failure: with the tables emptied and the load uncommitted, a concurrent writer in the application waits instead of inserting a row the bundle is about to insert too.
+
+  `--no-atomic` (CLI) / `atomic: false` (API) opts out. The trade is stated where it bites: every write to those tables waits for the load, and on postgres the bulk `COPY` loader cannot join a transaction it does not own — an atomic run now says that once rather than being quietly slower.
+
+  Two smaller things from the same report: `--mode replace` against a running instance warns about the empty-target window when it is NOT atomic, and the `--target api` upload reports progress per chunk plus a line explaining that the final request stays open for the whole import — sixteen minutes of silence is indistinguishable from a hang, and one operator killed a run that had finished.
+
+  **`voltro update` carries you across this** — codemod `0.44.0/01_import-outcome`.
+
+### Fixed
+
+- **@voltro/sql-mysql, @voltro/sql-postgres, @voltro/sql-sqlite, @voltro/sql-mssql, @voltro/data-transfer** — A write and its write-recorders now succeed or fail together on every SQL dialect, and the data importer's retry is idempotent.
+
+  A recorder (a versioning trail, an audit log) runs on the caller's connection and is ALLOWED to fail — a recorder that throws must take the write down with it, that is its contract. Outside a caller transaction the two were not one unit: the row's statement committed on its own, and the recorder's INSERT ran afterwards as a second autocommit statement. So a recorder that threw left a COMMITTED row behind a write that reported failure. Measured directly: `insert` throws, the row is in the table, and a second attempt at the same row is `ER_DUP_ENTRY` on PRIMARY.
+
+  Anything that retries a failed write then meets its own row. The data importer retries by design — it holds a row whose write failed and tries again once the remaining tables have streamed — so a `--mode replace` that had just emptied a table failed on a duplicate key IN that table. From outside, that is the impossible-looking thing: an import that emptied a table and then failed because something was already in it. Reproduced verbatim, including the table name and `[ER_DUP_ENTRY/1062]`, by putting the old retry back.
+
+  Both ends are closed, and they are independent on purpose:
+
+  - **The cause.** A table that HAS recorders writes inside a transaction now, so the row and the trail commit together or not at all — on mysql, mariadb, postgres, sqlite and mssql, verified by one suite that asks all five the same question. A table with no recorders — the default — takes the direct path unchanged; `recordsTable` is a Map-size check first, so it costs one comparison. - **The defence.** The importer's retry upserts instead of inserting in `replace` mode. That covers every OTHER way a write can land while reporting failure: a driver timeout on a write the server applied, a connection lost after the commit, a concurrent writer inserting the same key. It is sound precisely because the table was emptied by this same run — there is nothing in it that is not ours.
+
+  The test that pinned the divergence went red when the fix landed, exactly as its own note said it would, and is inverted with that note kept.
+
+---
+
+## [0.43.2] — 2026-08-18
+
+### Fixed
+
+- **@voltro/sql-mysql, @voltro/database, @voltro/cli** — The mysql-family binlog reader no longer keeps a table excluded after the very migration that fixed it.
+
+  A UNIQUE on an unbounded text column is a MariaDB hash long-unique, whose hidden `DB_ROW_HASH_n` column the reader can never account for — so the table is held out of binlog capture and the exclusion is reported. `voltro dev` builds its store BEFORE it migrates (kv, cross-replica broadcast and the analytics mirror all need one), so on a boot whose own auto-migration bounds the column, that finding was drawn from a schema that stopped existing about a second later. The exclusion then outlived its cause for the life of the process, and the message — correct when written, and typically the only error line in the boot log — went on describing the pre-migration database.
+
+  Three changes:
+
+  - `DataStore.refreshChangeCaptureExclusions()` (optional; implemented by the mysql-family store) re-runs the probe and re-points the LIVE reader, in both directions — schema work that CREATES the condition now excludes the table immediately instead of after three failed writes. `voltro dev` calls it once, after all its schema work. `voltro serve` needs no equivalent: it builds its store after every schema step and never applies DDL itself. - The definitive message now states its own durability — that it is the schema as read at reader attach, and that applying the remedy does not by itself lift the exclusion. - On a boot that will re-check, the finding is reported as a provisional note rather than as a verdict, so a boot that fixes the condition leaves no error line about it. The note escalates to the full verdict on its own if the re-check never runs. - Two reader fixes the re-check depended on: applying a new exclusion set now WAITS for a reconnect already in flight (it is what applies the set, so resolving before it landed meant the caller's next write hit the old filter), and the reconnect loop no longer keeps resuming from an offset it has just jumped away from — that turned one purged offset into a reconnect every watchdog interval, forever, delivering nothing.
+- **@voltro/data-transfer, @voltro/database, @voltro/sql-mysql, @voltro/sql-postgres, @voltro/sql-sqlite, @voltro/sql-mssql, @voltro/cli** — `voltro data import --mode replace` no longer leaves a target in neither state, and now works against schemas that have foreign keys.
+
+  The delete step ran table by table and stopped at the first refusal, so a run that could not finish left dozens of tables emptied and nothing loaded — and a second attempt destroyed more than the first, because it got further before hitting the same wall. The wall itself was not exotic: MySQL, MariaDB and SQL Server check a foreign key as each ROW is deleted, so a table that references ITSELF cannot be emptied by any ordering of the tables. `createdBy → actors` on the `actors` table is exactly that shape, and it is what an audit mixin on an actor table produces.
+
+  - `DataStore.emptyTables()` (per dialect) empties the whole set as one unit, in one transaction, with referential integrity suspended for the duration — `FOREIGN_KEY_CHECKS` on the mysql family, a multi-table `TRUNCATE` on postgres, `defer_foreign_keys` on sqlite, per-table `NOCHECK`/`WITH CHECK CHECK` on mssql. All-or-nothing on every engine, including under `--atomic`, where it runs on the transaction the import already holds. - A **pre-flight refusal**: if a table OUTSIDE the bundle holds rows referencing one inside it, the import refuses before deleting anything and names the tables, the columns and the row counts. Those rows cannot be restored from the bundle, so forcing it is not an option. An EMPTY outside table blocks nothing. - Table-level failures carry the driver's own reason and code, the way row-level failures already did. `truncate <table> failed: Failed to execute statement` fits every plausible cause equally; the classification that produced `foreign key <name>: … [ER_NO_REFERENCED_ROW_2/1452]` one level down now applies one level up. The word "truncate" is gone from the message too — the step issues DELETE, and naming a statement it does not run sends whoever reads it to reproduce the wrong thing. - A typed refusal reaching the `--target api` transport keeps its text: the admin import endpoint answers `409` with the reason instead of flattening it to `import failed`, on the one transport where the operator has no other way to see it.
+
+  The bulk empty emits no change events, where the per-table loop emitted one per row. An import through `--target api` now asks every live subscription to re-read once it lands — the coarse refresh the framework already uses after a broadcast gap — so neither the missing deletes nor a table the bundle carries EMPTY leaves a subscriber holding rows that are gone. Wired where the route is mounted, which is the one place both boot paths share.
+
+  On postgres the emptying is a `DELETE` per table, not a `TRUNCATE`, and the difference is not performance: postgres refuses `TRUNCATE` on a table with ANY incoming foreign key, rows or not, while the mysql family refuses a DELETE only when rows actually reference the doomed ones. A `TRUNCATE` version made an EMPTY table outside the bundle block a replace on postgres and not on mariadb — one import, refused on one engine and accepted on the other, over a table holding nothing.
+
+  `--target api` also no longer times out on a full bundle. Both api-target calls went through `fetch`, whose undici default gives up after 300 s — a bound on the caller's database size, on a call whose response arrives only when the import does. They wait as long as the instance needs now, stream the body instead of buffering the whole bundle, and take `--timeout <seconds>` when a deadline is wanted. If one is hit, the message says the instance is probably still importing — and gives different advice for `replace` than for the idempotent modes, since re-running the first while it is mid-flight would empty the target under it.
+
+  Two more, found by measuring rather than by reading:
+
+  - **`--atomic` on postgres could not import a bundle that needed the deferred-FK repair at all.** A failed statement aborts the transaction there, and that repair depends on a row whose parent has not loaded yet failing, being held, and being retried — so the first such row poisoned every write after it. Every tolerated write now runs inside a savepoint. Per-row savepoints measured 2.40x the time of none on 5 000 rows, so they are amortised: one savepoint per batch of 200, and a batch that fails rolls back whole and replays row by row. The mysql family and sqlite leave a transaction usable after a failed statement and pay nothing for any of this. - **The replace pre-flight asked the caller's snapshot.** Over `--target api` that is the app's DECLARED schema, which cannot show a table the app stopped declaring but the database still has — and rows in a table nobody declares are exactly the rows nobody is watching. `DataStore.incomingForeignKeys()` reads the live catalog per dialect; the snapshot remains the fallback for stores without one.
+
+  A bundle bigger than one chunk is now uploaded as a series of short requests, so a proxy body cap or an ingress read timeout has nothing large to choke on, and the switch is automatic — the packer's stream is buffered one chunk ahead, so a small bundle is sent exactly as before and nobody has to know in advance which table is the big one. The import still runs ONCE, at the end, over the whole bundle. Resume is byte-exact (`packBundle` is deterministic over a directory, which this package now asserts), guarded by a bundle key so a different bundle under the same upload id is refused rather than spliced into the partial one, and by a contiguity check so a mis-ordered append cannot produce an archive that only fails later during decode. `--chunk-size <mb>` overrides the 16 MiB default.
+
+---
+
 ## [0.43.1] — 2026-08-18
 
 ### Fixed

package/dist/{apiBuild-DF0f69Gf.js → apiBuild-DvWreIQP.js}

@@ -1,4 +1,4 @@
-import { f as e } from "./dev-B2rZfqxw.js";
+import { f as e } from "./dev-D-JZ6CGQ.js";
 import { vt as t } from "./webDev-101csg6Q.js";
 import { t as n } from "./dialectDriver-czCHYpeH.js";
 import { dirname as r, isAbsolute as i, join as a, relative as o, resolve as s } from "node:path";

package/dist/apiBuild-XaW40W8x.js

@@ -0,0 +1,2 @@
+import { c as e, l as t } from "./apiBuild-DvWreIQP.js";
+export { e as runApiBuild, t as runServeBundleBuild };

package/dist/bin.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { r as e } from "./commands-CbQcuWsE.js";
+import { r as e } from "./commands-fsnezHLH.js";
 import { a as t } from "./nodeEnvironment-cGFAj1J8.js";
 import { t as n } from "./loadEnv-D9nEOClM.js";
 import { n as r } from "./cliError-BmdYnghb.js";

package/dist/{build-LC_IJaHL.js → build-Ckc-FA7d.js}

@@ -1,8 +1,8 @@
-import { hn as e } from "./dev-B2rZfqxw.js";
+import { hn as e } from "./dev-D-JZ6CGQ.js";
 import { $ as t, A as n, F as r, I as i, L as a, Q as o, a as s, b as c, d as l, et as u, f as d, ht as f, k as p, rt as m, s as h, v as g, vt as _, y as v } from "./webDev-101csg6Q.js";
 import { t as y } from "./cliRuntime-Dh7UDinH.js";
 import { a as b } from "./renderModeScan-D7J1B7Kw.js";
-import { i as x, o as S, s as C } from "./apiBuild-DF0f69Gf.js";
+import { i as x, o as S, s as C } from "./apiBuild-DvWreIQP.js";
 import { n as w } from "./renderProfile-1OWWAAtx.js";
 import { dirname as T, join as E, resolve as D } from "node:path";
 import { existsSync as O, promises as k } from "node:fs";
@@ -477,7 +477,7 @@ var N = A({ scope: "voltro:build" }), P = async (e) => {
 		file: n.file,
 		reason: n.reason
 	});
-	let { regenerateRpcGroup: r } = await import("./codegenCommand-LjxfK4Am.js"), i = await r(e);
+	let { regenerateRpcGroup: r } = await import("./codegenCommand-iClXoRCW.js"), i = await r(e);
 	if (i.kind === "refused") {
 		F.warn("could not regenerate the rpc group — building against what is on disk", { reason: i.reason });
 		return;
@@ -489,10 +489,10 @@ var N = A({ scope: "voltro:build" }), P = async (e) => {
 }, K = async (e) => {
 	let n = await l(e);
 	if (!n) {
-		let { loadApiConfig: t } = await import("./dev-D0E5x2Ue.js"), n = await t(e);
+		let { loadApiConfig: t } = await import("./dev-BZO5aLdr.js"), n = await t(e);
 		if (n) {
 			F.info("building api app", { app: n.name ?? "(unnamed)" }), await G(e);
-			let { runApiBuild: t, runServeBundleBuild: r } = await import("./apiBuild-B7NgSMhX.js");
+			let { runApiBuild: t, runServeBundleBuild: r } = await import("./apiBuild-XaW40W8x.js");
 			await t(e);
 			try {
 				await r(e);
@@ -711,7 +711,7 @@ var N = A({ scope: "voltro:build" }), P = async (e) => {
 	return t.ran ? t.exitCode : (yield* j.logError("no web app found at this path", { hint: "looked for app.config.ts with `type: 'web'`" }), 1);
 }), J = async (t) => {
 	if (t.includes("--target")) {
-		let { runSdkBuildCommand: e } = await import("./sdkgen-DbTFGCjg.js");
+		let { runSdkBuildCommand: e } = await import("./sdkgen-7dr8-Onw.js");
 		return e(t);
 	}
 	let n = t.find((e) => !e.startsWith("-")) ?? process.cwd(), r = await y(q(n), { scope: "voltro:build" }), i = e(n);

package/dist/{checkCommand-DBpTSK8d.js → checkCommand-AlbawIal.js}

@@ -1,2 +1,2 @@
-import { n as e, r as t, t as n } from "./checkCommand-DDxwJCja.js";
+import { n as e, r as t, t as n } from "./checkCommand-BNfEs4KG.js";
 export { n as offlineManifest, e as runCheckCommand, t as toInput };

package/dist/{checkCommand-DDxwJCja.js → checkCommand-BNfEs4KG.js}

@@ -4,7 +4,7 @@ import { r } from "./appGraph-KGDPTuTy.js";
 import { n as i } from "./cliOutput-D1tSBoRM.js";
 import { n as a, o, r as s, t as c } from "./inspectFetch-EMuhTG_9.js";
 import { r as l } from "./fileTaxonomy-CJfgOllU.js";
-import { x as u } from "./doctorCommand-Ct_3BHgd.js";
+import { x as u } from "./doctorCommand-BlUyESpD.js";
 import { resolve as d } from "node:path";
 import { readdirSync as f, statSync as p } from "node:fs";
 //#region src/observedDiff.ts
@@ -141,7 +141,7 @@ var m = (e) => e === void 0 ? [] : typeof e == "string" ? [e] : e, h = /* @__PUR
 	let t = e.severity === "error" ? "✗ error" : "⚠ warn", n = e.file ? ` (${e.file})` : "";
 	return `${t}  ${e.rule}  ${e.node}${n}\n    ${e.breaks.join("; ")}\n    fix: ${e.fix}`;
 }).join("\n"), C = async (e) => {
-	let { walk: t, loadDiscovered: n, loadApiConfig: r } = await import("./dev-D0E5x2Ue.js"), { buildRpcEntry: i } = await import("./manifestBuild-j0n109tt.js"), { buildCapabilityManifest: a } = await import("./inspect-DUze25t0.js"), { relative: o } = await import("node:path"), s = await n(await t(e)), c = (t, n, r) => i(t, n, o(e, r)), l = [
+	let { walk: t, loadDiscovered: n, loadApiConfig: r } = await import("./dev-BZO5aLdr.js"), { buildRpcEntry: i } = await import("./manifestBuild-j0n109tt.js"), { buildCapabilityManifest: a } = await import("./inspect-DUze25t0.js"), { relative: o } = await import("node:path"), s = await n(await t(e)), c = (t, n, r) => i(t, n, o(e, r)), l = [
 		...s.queries.map((e) => c(e.descriptor, "query", e.file)),
 		...s.mutations.map((e) => c(e.descriptor, "mutation", e.file)),
 		...s.actions.map((e) => c(e.descriptor, "action", e.file)),

package/dist/{codegenCommand-LjxfK4Am.js → codegenCommand-iClXoRCW.js}

@@ -1,4 +1,4 @@
-import { l as e, z as t } from "./dev-B2rZfqxw.js";
+import { l as e, z as t } from "./dev-D-JZ6CGQ.js";
 import { dt as n } from "./webDev-101csg6Q.js";
 import { r } from "./codegen-CbpGCWLG.js";
 import { basename as i, join as a, relative as o, resolve as s } from "node:path";

package/dist/{codemodRunner-Cnnz4-I7.js → codemodRunner-BKTnaGOz.js}

@@ -5618,6 +5618,28 @@ var b = (e, t, n) => {
 			});
 			return r > 0 && n(`renamed ${r} import(s) of DanglingReferenceError → RowsRefusedError. A tag STRING (Effect.catchTag('DanglingReferenceError', …) or err._tag === '…') is NOT rewritten — change it to 'RowsRefusedError'. The payload also gained primaryCount, and each row a boolean derived.`), r;
 		}
+	}),
+	S({
+		version: "0.44.0",
+		id: "0.44.0/01_import-outcome",
+		title: "`runImport` returns an ImportOutcome — read `.manifest` for the bundle",
+		kind: "manual",
+		appliesTo: ({ project: e }) => e.getSourceFiles().some((e) => e.getImportDeclarations().some((e) => e.getModuleSpecifierValue().startsWith("@voltro/data-transfer") && e.getNamedImports().some((e) => e.getName() === "runImport"))),
+		note: [
+			"`runImport(...)` now resolves to `{ manifest, tablesWritten, rowsWritten, tablesSkipped, rowsSkipped, fullyResumed }`",
+			"instead of the bundle's `Manifest`.",
+			"",
+			"  1. Where you read the bundle — `.tables`, `.assets`, `.scope`, `.source` — read `.manifest.tables` and so on.",
+			"  2. Where you REPORTED a row count, prefer `rowsWritten`. The manifest total is what the bundle CARRIES:",
+			"     a run that skipped every table (an earlier run of the same bundle directory had already applied them)",
+			"     carries the full count while writing nothing, which is exactly how a no-op used to read as a success.",
+			"  3. `fullyResumed` is true precisely in that case.",
+			"",
+			"Same release, unrelated to the return type: `--mode replace` now runs in ONE transaction unless you pass",
+			"`--no-atomic` (CLI) or `atomic: false` (API) — a replace that failed mid-load used to leave the target",
+			"emptied of its old rows and holding part of the new ones. If you relied on per-table resume for a replace,",
+			"that is the non-atomic path."
+		].join("\n")
 	})
 ], Y = /* @__PURE__ */ new Set([
 	"node_modules",

package/dist/{commands-CbQcuWsE.js → commands-fsnezHLH.js}

@@ -91,7 +91,7 @@ var c = () => {
 		name: "dev",
 		summary: "Start the local development server (auto-discovers routes / mutations).",
 		status: "wired",
-		run: (e) => import("./dev-D0E5x2Ue.js").then((t) => t.runDev(e)),
+		run: (e) => import("./dev-BZO5aLdr.js").then((t) => t.runDev(e)),
 		help: {
 			usage: "[app]",
 			examples: [["voltro dev", "boot the app in the current directory"], ["voltro dev apps/acme/api", "boot a specific app"]],
@@ -109,7 +109,7 @@ var c = () => {
 		name: "dashboard",
 		summary: "Serve the DevTools dashboard standalone (from @voltro/dashboard). Targets via VOLTRO_DASHBOARD_APPS; --port to override.",
 		status: "wired",
-		run: (e) => import("./dashboardCommand-CAHjCe_9.js").then((t) => t.runDashboardCommand(e)),
+		run: (e) => import("./dashboardCommand-DHDmlo9A.js").then((t) => t.runDashboardCommand(e)),
 		help: {
 			usage: "[--port <n>]",
 			flags: [["--port <n>", "port to serve the dashboard on"]],
@@ -121,7 +121,7 @@ var c = () => {
 		name: "check",
 		summary: "Verify the app graph (blast-radius checks) against a running api; LLM-shaped --json diagnostics. Flags: --json, --process <p>, --diff removeTable:<name>.",
 		status: "wired",
-		run: (e) => import("./checkCommand-DBpTSK8d.js").then((t) => t.runCheckCommand(e)),
+		run: (e) => import("./checkCommand-AlbawIal.js").then((t) => t.runCheckCommand(e)),
 		help: {
 			usage: "[--json] [--offline] [--process <name>] [--diff removeTable:<name>]",
 			flags: [
@@ -155,7 +155,7 @@ var c = () => {
 		name: "webhooks",
 		summary: "Outbound-webhook artefacts. `consumer` generates the ZERO-DEPENDENCY Standard-Webhooks verification package a subscriber installs, from this app's own declared events; `events` lists the events a subscriber can register for. Usage: voltro webhooks <consumer|events> [path] [--out <dir>] [--name <pkg>] [--json].",
 		status: "wired",
-		run: (e) => import("./webhooksCommand-BXUP5YjW.js").then((t) => t.runWebhooksCommand(e)),
+		run: (e) => import("./webhooksCommand-BfO_JF2b.js").then((t) => t.runWebhooksCommand(e)),
 		help: {
 			usage: "<consumer|events> [path] [--out <dir>] [--name <pkg>] [--json]",
 			flags: [
@@ -171,7 +171,7 @@ var c = () => {
 		name: "evolve",
 		summary: "Schema-evolution copilot: propose an observed-graph-driven codemod + a branch-verified backfill for a schema change (rename/retype/split/drop a column, rename a table). Dry-run by default; --write applies. Usage: voltro evolve rename-column <table>.<col> --to <newName> [--write] [--json].",
 		status: "wired",
-		run: (e) => import("./evolveCommand-D5opB48I.js").then((t) => t.runEvolveCommand(e)),
+		run: (e) => import("./evolveCommand-CBV3-TtK.js").then((t) => t.runEvolveCommand(e)),
 		help: {
 			usage: "<rename-column|rename-table|retype-column|split-column|drop-column> <target> [--to <new>] [--write]",
 			flags: [
@@ -188,7 +188,7 @@ var c = () => {
 		name: "codegen",
 		summary: "Emit rpcGroup.generated.ts from discovered route / mutation descriptors.",
 		status: "wired",
-		run: (e) => import("./codegenCommand-LjxfK4Am.js").then((t) => t.runCodegenCommand(e)),
+		run: (e) => import("./codegenCommand-iClXoRCW.js").then((t) => t.runCodegenCommand(e)),
 		help: {
 			usage: "[app]",
 			examples: [["voltro codegen", "regenerate rpcGroup.generated.ts for the app in the cwd"]],
@@ -259,7 +259,7 @@ var c = () => {
 		name: "info",
 		summary: "Report versions (CLI, node, every installed @voltro/* — flags lockstep skew), package manager, and dialect. --json for CI. Exits 1 on version skew.",
 		status: "wired",
-		run: (e) => import("./infoCommand-Bs_8RU22.js").then((t) => t.runInfoCommand(e)),
+		run: (e) => import("./infoCommand-DJoA9cKD.js").then((t) => t.runInfoCommand(e)),
 		help: {
 			usage: "[--json]",
 			flags: [["--json", "machine-readable report"]],
@@ -280,7 +280,7 @@ var c = () => {
 		name: "env",
 		summary: "Inspect/sync the typed-env manifest. Subcommands: check (default), sync (.env.example), types (env.generated.d.ts for CI tsc), turbo.",
 		status: "wired",
-		run: (e) => import("./envCommand-7qjlQgLD.js").then((t) => t.runEnvCommand(e)),
+		run: (e) => import("./envCommand-CpCbYAgR.js").then((t) => t.runEnvCommand(e)),
 		help: {
 			usage: "[check|sync|types|turbo] [--force]",
 			flags: [["--force", "overwrite the generated file instead of refusing on a conflict"]],
@@ -309,12 +309,12 @@ var c = () => {
 		run: async (e) => {
 			let t = e.find((e) => !e.startsWith("-")) ?? process.cwd();
 			if (e.includes("--preflight")) {
-				let { runServePreflight: e } = await import("./doctorCommand-CdsctSwg.js");
+				let { runServePreflight: e } = await import("./doctorCommand-BeLOwq7S.js");
 				return e(a(t), !0);
 			}
 			let { tryRunWebServe: n } = await import("./webDev-BLKBO34K.js"), r = await n(a(t));
 			if (!r.ran) {
-				let { runServeDispatch: t } = await import("./serveCommand-CGNTXafv.js");
+				let { runServeDispatch: t } = await import("./serveCommand-Dg_E1ev4.js");
 				return t(e);
 			}
 			return r.exitCode;
@@ -342,13 +342,13 @@ var c = () => {
 		handlesHelp: !0,
 		summary: "Preflight an app for production: the precompiled serve bundle, hand-rolled primitives (naming the shipped one), @voltro/* version skew, executors with no access check, `.serverOnly()` leaks, and junction-FK gaps.",
 		status: "wired",
-		run: (e) => import("./doctorCommand-CdsctSwg.js").then((t) => t.runDoctorCommand(e))
+		run: (e) => import("./doctorCommand-BeLOwq7S.js").then((t) => t.runDoctorCommand(e))
 	},
 	{
 		name: "build",
 		summary: "Production build for a web app (vite build + per-page SSG pre-render).",
 		status: "wired",
-		run: (e) => import("./build-LC_IJaHL.js").then((t) => t.runBuildCommand(e)),
+		run: (e) => import("./build-Ckc-FA7d.js").then((t) => t.runBuildCommand(e)),
 		help: {
 			usage: "[app] [--target <t>]",
 			flags: [["--target <t>", "build target"]],
@@ -364,7 +364,7 @@ var c = () => {
 		name: "prune-runtime",
 		summary: "Trim a deployed web tree’s node_modules to the reachable runtime set (standalone image slimming).",
 		status: "wired",
-		run: (e) => import("./runtimeTrace-Wmi7V-wN.js").then((t) => t.runPruneRuntimeCommand(e)),
+		run: (e) => import("./runtimeTrace-DJ9tPhrc.js").then((t) => t.runPruneRuntimeCommand(e)),
 		hidden: !0
 	},
 	{
@@ -382,7 +382,7 @@ var c = () => {
 		name: "dormancy",
 		summary: "Single-node scale-to-zero: front the API with a wake-orchestrator that stops the app when idle and brings it back on a request or a due wakeup (cron/workflow). Needs a SQL store. Flags: --port, --app-port, --idle-grace-ms, --tick-ms.",
 		status: "wired",
-		run: (e) => import("./dormancyCommand-D1DKnYce.js").then((t) => t.runDormancyCommand(e)),
+		run: (e) => import("./dormancyCommand-lQxdrU8C.js").then((t) => t.runDormancyCommand(e)),
 		help: {
 			usage: "[app] [--port <n>] [--app-port <n>] [--idle-grace-ms <n>] [--tick-ms <n>]",
 			flags: [
@@ -469,7 +469,7 @@ var c = () => {
 		name: "data",
 		summary: "Export/import + backup/restore of app data. Logical (rows + optional assets): export <dir> [--tenant <id>|--tables a,b] [--assets] [--compression zstd|gzip|none] [--consistency live|snapshot]; import <dir> [--assets] [--no-verify]. Native (rows ONLY — no blobs): backup <dir> / restore <dir> (pg_dump/mariadb-dump/…). Resumable; typed-NDJSON; content-addressed assets on the logical path.",
 		status: "wired",
-		run: (e) => import("./dataCommand-CrqvbVOv.js").then((t) => t.runDataCommand(e)),
+		run: (e) => import("./dataCommand-sfpGV694.js").then((t) => t.runDataCommand(e)),
 		help: {
 			usage: "<export|import|backup|restore> <dir> [options]",
 			flags: [
@@ -524,20 +524,20 @@ var c = () => {
 		handlesHelp: !0,
 		summary: "Upgrade the app to the latest framework: bump every @voltro/* dependency (across ALL workspace members, install once at the workspace root), then run the codemods shipped with the target version. Flags: --to <version>, --from <version>, --codemods-only, --dry-run, --force, --exact, --help. After: run `voltro db apply`.",
 		status: "wired",
-		run: (e) => import("./updateCommand-BvkKlV7D.js").then((t) => t.runUpdateCommand(e))
+		run: (e) => import("./updateCommand-DcKVmLVN.js").then((t) => t.runUpdateCommand(e))
 	},
 	{
 		name: "_apply-codemods",
 		summary: "Internal: apply shipped codemods for a framework version jump (re-exec target of `voltro update`).",
 		status: "wired",
 		hidden: !0,
-		run: (e) => import("./updateCommand-BvkKlV7D.js").then((t) => t.runApplyCodemods(e))
+		run: (e) => import("./updateCommand-DcKVmLVN.js").then((t) => t.runApplyCodemods(e))
 	},
 	{
 		name: "embeddings",
 		summary: "Embeddings tooling. Subcommand: backfill <table> --text <field> --vector <field> [--model <m>] [--model-field <f>] [--batch <n>] [--dry-run] — (re)embed rows the vectorEmbedding() mixin missed.",
 		status: "wired",
-		run: (e) => import("./embeddingsCommand-1sZRBKlM.js").then((t) => t.runEmbeddingsCommand(e)),
+		run: (e) => import("./embeddingsCommand-ByBTju6X.js").then((t) => t.runEmbeddingsCommand(e)),
 		help: {
 			usage: "backfill <table> --text <field> --vector <field> [--model <m>] [--batch <n>] [--dry-run]",
 			flags: [

package/dist/{dashboardCommand-CAHjCe_9.js → dashboardCommand-DHDmlo9A.js}

@@ -1,4 +1,4 @@
-import { d as e } from "./dev-B2rZfqxw.js";
+import { d as e } from "./dev-D-JZ6CGQ.js";
 import { H as t, z as n } from "./webDev-101csg6Q.js";
 import { t as r } from "./start-Ds3xyn8R.js";
 import { join as i } from "node:path";