@voltro/cli 0.49.0 → 0.50.0

package/dist/{dev-C31Nvlbv.js → dev-1yu42ubu.js}

@@ -3,7 +3,7 @@ import { t } from "./frameworkInspectState-CX2250XB.js";
 import { n } from "./appModuleLoader-C9r9mxZt.js";
 import { t as r } from "./bootRefusal-pgvDxlrU.js";
 import { n as i, r as a } from "./startupRunner-CEqQq7ax.js";
-import { t as o } from "./interruptedReplace-C1ZI84xi.js";
+import { t as o } from "./interruptedReplace-C3O3M1MM.js";
 import { r as s } from "./appPort-B_HpJ_ck.js";
 import { H as c, J as l, K as u, V as d, W as f, X as p, Y as m, Z as h, ct as g, ft as _, g as v, ht as ee, lt as y, pt as te, q as b, ut as x } from "./webDev-B4IEMB0n.js";
 import { n as ne, r as S } from "./dialectDriver-czCHYpeH.js";

package/dist/{dev-DFVuzOj7.js → dev-BWwE0QjK.js}

@@ -1,3 +1,3 @@
-import { c as e, d as t, f as n, i as r, u as i } from "./dev-C31Nvlbv.js";
+import { c as e, d as t, f as n, i as r, u as i } from "./dev-1yu42ubu.js";
 import "./dialectDriver-czCHYpeH.js";
 export { r as buildStore, e as loadApiConfig, i as loadDiscovered, t as runDev, n as walk };

package/dist/doctorCommand-BmovAwb7.js

@@ -0,0 +1,2 @@
+import { b as e, y as t } from "./doctorCommand-y-EbP8st.js";
+export { t as runDoctorCommand, e as runServePreflight };

package/dist/{doctorCommand-B3uraeAe.js → doctorCommand-y-EbP8st.js}

@@ -1,8 +1,8 @@
-import { Ht as e, Ut as t, Vt as n } from "./dev-C31Nvlbv.js";
+import { Ht as e, Ut as t, Vt as n } from "./dev-1yu42ubu.js";
 import { at as r, it as i, ot as a, s as o, st as s, t as c, w as l, y as u } from "./webDev-B4IEMB0n.js";
 import { x as d } from "./frameworkTableAssembly-BwJVEKLr.js";
 import { n as f } from "./pageConvention-cEiRxdab.js";
-import { r as p, u as m } from "./apiBuild-QmYHaCF4.js";
+import { r as p, u as m } from "./apiBuild-CFYXo06U.js";
 import { n as h, r as g, t as ee } from "./cliOutput-D1tSBoRM.js";
 import { n as _, t as te } from "./tsconfigPaths-BWXBWgcl.js";
 import { n as ne, r as re } from "./fileTaxonomy-CJfgOllU.js";
@@ -1350,7 +1350,7 @@ var le = /* @__PURE__ */ new Set([
 	let t = Wt.get(e);
 	if (t !== void 0) return t;
 	let n = (async () => {
-		let { walk: t, loadDiscovered: n } = await import("./dev-DFVuzOj7.js"), r = await t(e);
+		let { walk: t, loadDiscovered: n } = await import("./dev-BWwE0QjK.js"), r = await t(e);
 		return {
 			files: r,
 			discovered: await n(r)
@@ -1459,7 +1459,7 @@ var le = /* @__PURE__ */ new Set([
 	}
 }, J = async (r) => {
 	try {
-		let { loadApiConfig: i } = await import("./dev-DFVuzOj7.js"), { discovered: a } = await U(r), o = e(await i(r)), s = {
+		let { loadApiConfig: i } = await import("./dev-BWwE0QjK.js"), { discovered: a } = await U(r), o = e(await i(r)), s = {
 			queries: a.queries,
 			mutations: a.mutations,
 			actions: a.actions,
@@ -1543,7 +1543,7 @@ var le = /* @__PURE__ */ new Set([
 }, nn = async (e) => nt({
 	hasWorkflows: async () => (await U(e)).discovered.workflows.length > 0,
 	openStore: async () => {
-		let { loadApiConfig: t, buildStore: n } = await import("./dev-DFVuzOj7.js"), r = await t(e);
+		let { loadApiConfig: t, buildStore: n } = await import("./dev-BWwE0QjK.js"), r = await t(e);
 		if (r === null) throw Error("no app.config.ts in this directory");
 		let i = await n(r, void 0);
 		return {
@@ -1623,7 +1623,7 @@ var le = /* @__PURE__ */ new Set([
 	}
 }, ln = async (e) => {
 	try {
-		let { loadApiConfig: t } = await import("./dev-DFVuzOj7.js"), n = (await t(e))?.doctor?.scopeVocabulary;
+		let { loadApiConfig: t } = await import("./dev-BWwE0QjK.js"), n = (await t(e))?.doctor?.scopeVocabulary;
 		if (typeof n != "string") return [];
 		let [r, i] = n.split("#");
 		if (r === void 0 || i === void 0) return [];
@@ -1640,7 +1640,7 @@ var le = /* @__PURE__ */ new Set([
 		findings: []
 	});
 	try {
-		let { offlineManifest: n, toInput: r } = await import("./checkCommand-udbQpphy.js"), { buildAppGraph: i, checkAppGraph: a } = await import("./appGraph-zuMGKVYX.js"), o = await n(e), s = r(o.manifest, o.tables), c = await ln(e), l = [.../* @__PURE__ */ new Set([...s.scopes ?? [], ...c])];
+		let { offlineManifest: n, toInput: r } = await import("./checkCommand-OL41BMIb.js"), { buildAppGraph: i, checkAppGraph: a } = await import("./appGraph-zuMGKVYX.js"), o = await n(e), s = r(o.manifest, o.tables), c = await ln(e), l = [.../* @__PURE__ */ new Set([...s.scopes ?? [], ...c])];
 		if (l.length === 0) {
 			try {
 				let { loadAppSchemaInputs: t } = await import("./frameworkTableAssembly-CVDB2hCq.js");
@@ -1694,7 +1694,7 @@ var le = /* @__PURE__ */ new Set([
 	if (n === void 0 || r.length === 0) return;
 	let i = [];
 	try {
-		let { loadApiConfig: t } = await import("./dev-DFVuzOj7.js");
+		let { loadApiConfig: t } = await import("./dev-BWwE0QjK.js");
 		i = (await t(e))?.locales ?? [];
 	} catch {
 		return;
@@ -1725,7 +1725,7 @@ var le = /* @__PURE__ */ new Set([
 }, pn = async (e) => {
 	let { discovered: t } = await U(e), n = [];
 	try {
-		let { loadApiConfig: t } = await import("./dev-DFVuzOj7.js");
+		let { loadApiConfig: t } = await import("./dev-BWwE0QjK.js");
 		n = ((await t(e))?.plugins ?? []).map((e) => {
 			let t = (e.extendSchema?.tables ?? []).map((e) => {
 				let t = e;
@@ -1870,7 +1870,7 @@ var le = /* @__PURE__ */ new Set([
 	return n.unchecked.length > $ && console.log(`  … and ${n.unchecked.length - $} more — \`voltro doctor --json\` prints every one (\`authz.unchecked\`).`), i === void 0 ? (console.log(`\nNo ${X} yet, so this run is advisory. To start the ratchet:`), console.log("\n    voltro doctor --write-authz-allowlist\n"), console.log("That records today's unchecked handlers as DEBT and fails every run after on"), console.log("anything NEW. Fix a handler and its line stops mattering — the scan reports it as"), console.log("guarded whether or not the line is still there."), !1) : (console.log(`\n${n.unchecked.length} executor(s) with no access check are not in ${X}.`), console.log("Add a guard, or add the tag to that file if it is genuinely open."), console.log("\nBefore hand-rolling another check: `guards: [{ action, resourceType, resource }]`"), console.log("answers \"may this subject act on THIS row\" declaratively, and an app whose"), console.log("relationships live in its own tables registers its own tuple source rather than"), console.log("copying data into a framework table. See the authorization docs."), !0);
 }, yn = async (e) => {
 	try {
-		let { loadApiConfig: t } = await import("./dev-DFVuzOj7.js"), { decidedSchemaReport: n } = await import("./doctorDecidedSchema-BlbWgCD_.js"), r = await t(e);
+		let { loadApiConfig: t } = await import("./dev-BWwE0QjK.js"), { decidedSchemaReport: n } = await import("./doctorDecidedSchema-BlbWgCD_.js"), r = await t(e);
 		return r == null ? null : n({
 			...r.schema ? { declared: r.schema } : {},
 			...r.store === void 0 ? {} : { store: r.store },

package/dist/{dormancyCommand-QUXQ9yoz.js → dormancyCommand-Dc7KRNCG.js}

@@ -1,4 +1,4 @@
-import { c as e, i as t } from "./dev-C31Nvlbv.js";
+import { c as e, i as t } from "./dev-1yu42ubu.js";
 import { n, t as r } from "./cliArgs-D4p8n7EE.js";
 import { r as i } from "./appPort-B_HpJ_ck.js";
 import { resolve as a } from "node:path";

package/dist/{embeddingsCommand-Zw1-rYSF.js → embeddingsCommand-kPs132bB.js}

@@ -1,4 +1,4 @@
-import { c as e, i as t } from "./dev-C31Nvlbv.js";
+import { c as e, i as t } from "./dev-1yu42ubu.js";
 import { Effect as n } from "effect";
 import { embedMany as r } from "@voltro/ai";
 //#region src/embeddingsBackfill.ts

package/dist/{envCommand-DtaJ4xEf.js → envCommand-E12zSt51.js}

@@ -1,4 +1,4 @@
-import { c as e } from "./dev-C31Nvlbv.js";
+import { c as e } from "./dev-1yu42ubu.js";
 import { _t as t, gt as n, mt as r, pt as i } from "./webDev-B4IEMB0n.js";
 import { join as a } from "node:path";
 import { promises as o } from "node:fs";

package/dist/{evolveCommand-JDD3hE1i.js → evolveCommand-B3nagPVc.js}

@@ -1,6 +1,6 @@
 import { n as e } from "./cliOutput-D1tSBoRM.js";
-import { t } from "./checkCommand-D8vjQXQt.js";
-import { i as n, n as r } from "./codemodRunner-De1_316I.js";
+import { t } from "./checkCommand-Do3SQbLx.js";
+import { i as n, n as r } from "./codemodRunner-De3k0pRd.js";
 import { basename as i, join as a, resolve as o } from "node:path";
 import { branchNamespaceName as s, planBranchProvision as c } from "@voltro/database";
 import { readFile as l } from "node:fs/promises";

package/dist/index.js

@@ -1,4 +1,4 @@
-import { a as e, i as t, n, o as r, r as i, t as a } from "./commands-a5PxCaIg.js";
+import { a as e, i as t, n, o as r, r as i, t as a } from "./commands-By23Ljny.js";
 import { r as o } from "./templates-BR-fb4SP.js";
 //#region src/index.ts
 var s = "framework";

package/dist/{infoCommand-COsUC1DB.js → infoCommand-Cq0Yz98u.js}

@@ -1,5 +1,5 @@
 import { n as e, r as t, t as n } from "./cliOutput-D1tSBoRM.js";
-import { o as r } from "./updateCommand-2BfbeMvp.js";
+import { o as r } from "./updateCommand-i8JbrLAA.js";
 import { join as i, resolve as a } from "node:path";
 import { readFileSync as o, readdirSync as s, statSync as c } from "node:fs";
 //#region src/infoCommand.ts

package/dist/{interruptedReplace-C1ZI84xi.js → interruptedReplace-C3O3M1MM.js}

@@ -14,7 +14,8 @@ var n = async (n) => {
 		let i = r.map((e) => ({
 			id: String(e.id ?? ""),
 			startedAt: e.startedAt instanceof Date ? e.startedAt : new Date(String(e.startedAt ?? "")),
-			tables: Number(e.tables ?? 0),
+			kind: e.kind === void 0 || e.kind === null ? "replace" : String(e.kind),
+			tables: e.tables === null || e.tables === void 0 ? null : Number(e.tables),
 			capture: e.capture === null || e.capture === void 0 ? null : String(e.capture),
 			via: String(e.via ?? "unknown")
 		}));

package/dist/interruptedReplace-CvmiAM9K.js

@@ -0,0 +1,2 @@
+import { t as e } from "./interruptedReplace-C3O3M1MM.js";
+export { e as interruptedReplaceAtBoot };

package/dist/{runtimeTrace-Di6fcndp.js → runtimeTrace-BpLUcrfy.js}

@@ -1,4 +1,4 @@
-import { n as e } from "./apiBuild-QmYHaCF4.js";
+import { n as e } from "./apiBuild-CFYXo06U.js";
 import { join as t, resolve as n, sep as r } from "node:path";
 import { existsSync as i, promises as a } from "node:fs";
 import { createLogger as o } from "@voltro/logger";

package/dist/{sdkgen-CIi5gM17.js → sdkgen-dl4-WKF6.js}

@@ -422,7 +422,7 @@ let package = Package(
 		await l.mkdir(o(e), { recursive: !0 }), await l.writeFile(e, n.content, "utf8");
 	}
 }, X = async (e) => {
-	let { offlineManifest: t } = await import("./checkCommand-udbQpphy.js"), { manifest: n } = await t(e);
+	let { offlineManifest: t } = await import("./checkCommand-OL41BMIb.js"), { manifest: n } = await t(e);
 	return n;
 }, Z = async (e) => {
 	let t = J(await (e.manifestProvider ?? X)(e.root), {

package/dist/{serveCommand-N3udT49p.js → serveCommand-8CTzQCY0.js}

@@ -3,8 +3,8 @@ import { t } from "./frameworkInspectState-CX2250XB.js";
 import { r as n, t as r } from "./appModuleLoader-C9r9mxZt.js";
 import { t as i } from "./bootRefusal-pgvDxlrU.js";
 import { n as a, r as o } from "./startupRunner-CEqQq7ax.js";
-import { t as s } from "./interruptedReplace-C1ZI84xi.js";
-import { $ as c, $t as l, A as u, At as d, Bt as f, C as ee, Cn as te, Ct as ne, D as p, Dt as m, E as h, En as re, Et as g, F as ie, Ft as ae, G as oe, Gt as se, H as _, Ht as ce, I as le, It as ue, J as de, Jt as v, K as y, Kt as fe, L as b, Lt as pe, M as me, Mt as he, N as ge, Nt as _e, O as ve, Ot as ye, P as be, Pt as xe, Q as Se, Qt as Ce, R as x, Rt as we, S as Te, St as Ee, T as De, Tn as Oe, Tt as S, U as ke, V as Ae, W as je, Wt as Me, X as Ne, Xt as Pe, Y as Fe, Yt as C, Z as Ie, Zt as Le, _ as w, _n as Re, _t as T, an as ze, at as Be, b as Ve, bn as He, bt as Ue, c as We, cn as Ge, ct as Ke, dn as qe, dt as Je, en as Ye, et as Xe, f as Ze, fn as Qe, ft as $e, g as et, gt as tt, h as nt, hn as rt, ht as it, i as at, in as ot, it as st, j as ct, jt as lt, k as ut, kt as dt, ln as ft, lt as pt, m as mt, mn as ht, mt as gt, nn as _t, nt as E, o as D, on as vt, ot as O, p as k, pn as yt, pt as bt, q as xt, qt as St, r as Ct, rn as A, rt as wt, sn as j, st as Tt, t as Et, tn as Dt, tt as Ot, u as kt, un as At, ut as jt, v as Mt, vn as Nt, vt as M, w as N, wn as Pt, wt as Ft, x as It, xn as Lt, xt as Rt, y as zt, yn as Bt, yt as Vt, zt as Ht } from "./dev-C31Nvlbv.js";
+import { t as s } from "./interruptedReplace-C3O3M1MM.js";
+import { $ as c, $t as l, A as u, At as d, Bt as f, C as ee, Cn as te, Ct as ne, D as p, Dt as m, E as h, En as re, Et as g, F as ie, Ft as ae, G as oe, Gt as se, H as _, Ht as ce, I as le, It as ue, J as de, Jt as v, K as y, Kt as fe, L as b, Lt as pe, M as me, Mt as he, N as ge, Nt as _e, O as ve, Ot as ye, P as be, Pt as xe, Q as Se, Qt as Ce, R as x, Rt as we, S as Te, St as Ee, T as De, Tn as Oe, Tt as S, U as ke, V as Ae, W as je, Wt as Me, X as Ne, Xt as Pe, Y as Fe, Yt as C, Z as Ie, Zt as Le, _ as w, _n as Re, _t as T, an as ze, at as Be, b as Ve, bn as He, bt as Ue, c as We, cn as Ge, ct as Ke, dn as qe, dt as Je, en as Ye, et as Xe, f as Ze, fn as Qe, ft as $e, g as et, gt as tt, h as nt, hn as rt, ht as it, i as at, in as ot, it as st, j as ct, jt as lt, k as ut, kt as dt, ln as ft, lt as pt, m as mt, mn as ht, mt as gt, nn as _t, nt as E, o as D, on as vt, ot as O, p as k, pn as yt, pt as bt, q as xt, qt as St, r as Ct, rn as A, rt as wt, sn as j, st as Tt, t as Et, tn as Dt, tt as Ot, u as kt, un as At, ut as jt, v as Mt, vn as Nt, vt as M, w as N, wn as Pt, wt as Ft, x as It, xn as Lt, xt as Rt, y as zt, yn as Bt, yt as Vt, zt as Ht } from "./dev-1yu42ubu.js";
 import { n as Ut } from "./cliArgs-D4p8n7EE.js";
 import { r as P } from "./appPort-B_HpJ_ck.js";
 import { ht as Wt, pt as Gt } from "./webDev-B4IEMB0n.js";
@@ -18,7 +18,7 @@ import { h as pn, o as mn } from "./inspect-B7U7Cl_Z.js";
 import { n as hn } from "./mssqlClusterPatch-_4cE_nun.js";
 import { i as gn, n as _n, r as vn, t as yn } from "./webhookDiscovery-CphsQe59.js";
 import { t as bn } from "./inspectMetrics-CfdKLh6t.js";
-import { r as xn, u as Sn } from "./apiBuild-QmYHaCF4.js";
+import { r as xn, u as Sn } from "./apiBuild-CFYXo06U.js";
 import { t as Cn } from "./bootTiming-BdyP9nYw.js";
 import { a as wn, o as Tn, t as En } from "./dataProfile-Du3ztYxv.js";
 import L, { basename as Dn, join as On } from "node:path";
@@ -97,7 +97,7 @@ var Zi = /* @__PURE__ */ ((e) => typeof require < "u" ? require : typeof Proxy <
 			await a(e), await o();
 		}
 	};
-}, ta = "/_voltro/admin/import", na = "/_voltro/admin/import/start", ra = "/_voltro/admin/export", ia = "/_voltro/admin/export/download", aa = "/_voltro/admin/imports", Z = (e, t) => ({
+}, ta = "/_voltro/admin/import", na = "/_voltro/admin/import/start", ra = "/_voltro/admin/export", ia = "/_voltro/admin/export/download", aa = "/_voltro/admin/transfers", Z = (e, t) => ({
 	status: e,
 	contentType: "application/json; charset=utf-8",
 	body: JSON.stringify(t)
@@ -463,7 +463,7 @@ var Zi = /* @__PURE__ */ ((e) => typeof require < "u" ? require : typeof Proxy <
 		atomic: r.atomic,
 		...r.dryRun ? { dryRun: !0 } : {},
 		recorded: f,
-		outcome: "poll /_voltro/admin/imports for this runId — a 202 means started, not finished"
+		outcome: "poll /_voltro/admin/transfers for this runId — a 202 means started, not finished"
 	});
 }, La = async (e) => {
 	let t = await Wi(e, ["manifest.json"]).then((e) => e.get("manifest.json"), () => null);
@@ -679,7 +679,7 @@ var Zi = /* @__PURE__ */ ((e) => typeof require < "u" ? require : typeof Proxy <
 		transport: c ? "storage" : "download",
 		...c ? { bundleKey: r.bundleKey } : {},
 		recorded: d,
-		outcome: "poll /_voltro/admin/imports for this runId; fetch the bytes from /_voltro/admin/export/download"
+		outcome: "poll /_voltro/admin/transfers for this runId; fetch the bytes from /_voltro/admin/export/download"
 	});
 }, to = async (e, t) => {
 	try {

package/dist/serveCommand-C_WI4TTG.js

@@ -0,0 +1,2 @@
+import { n as e } from "./serveCommand-8CTzQCY0.js";
+export { e as runServeDispatch };

package/dist/serveEntry.js

@@ -1,4 +1,4 @@
-import { t as e } from "./serveCommand-N3udT49p.js";
+import { t as e } from "./serveCommand-8CTzQCY0.js";
 import { t } from "./loadEnv-D9nEOClM.js";
 import { r as n } from "./appModuleLoader-C9r9mxZt.js";
 import { i as r } from "./dialectDriver-czCHYpeH.js";

package/dist/updateCommand-D91-TZ7E.js

@@ -0,0 +1,2 @@
+import { f as e, p as t } from "./updateCommand-i8JbrLAA.js";
+export { e as runApplyCodemods, t as runUpdateCommand };

package/dist/{updateCommand-2BfbeMvp.js → updateCommand-i8JbrLAA.js}

@@ -1,4 +1,4 @@
-import { n as e, r as t, t as n } from "./codemodRunner-De1_316I.js";
+import { n as e, r as t, t as n } from "./codemodRunner-De3k0pRd.js";
 import { basename as r, dirname as i, join as a, relative as o, resolve as s } from "node:path";
 import { existsSync as c, readFileSync as l, readdirSync as u, statSync as d, writeFileSync as f } from "node:fs";
 import { totalmem as p } from "node:os";
@@ -579,6 +579,7 @@ with \`--only\` / \`--root\`.`;
 		for (let e of r.manual) {
 			console.log(`\n▸ ${e.id} — ${e.title}`);
 			for (let t of e.note.split("\n")) console.log(`  ${t}`);
+			e.certain || (console.log(""), console.log("  ── nothing in this repository matched. That is NOT a clean bill of health:"), console.log("     `voltro update` reads the files git tracks here, and a CLI call also lives"), console.log("     in places it cannot reach — an inline script in a CI runner, a CronJob"), console.log("     spec in another repo, a runbook, a deploy job. Search those by hand."));
 		}
 	}
 	return n.dryRun && console.log("\n(dry-run — no files written)"), 0;

package/dist/{webhooksCommand-CwX9IzvJ.js → webhooksCommand-B0bdyuQ4.js}

@@ -222,7 +222,7 @@ createVerifier({ secret: [process.env.WEBHOOK_SECRET, process.env.WEBHOOK_SECRET
 		...t === void 0 ? {} : { payload: t }
 	};
 }, S = u({ scope: "voltro:webhooks" }), C = ["--out", "--name"], w = async (e) => {
-	let { walk: t, loadDiscovered: n } = await import("./dev-DFVuzOj7.js"), { outgoingFromEvents: r } = await import("./webhookDiscovery-il9ti-HE.js");
+	let { walk: t, loadDiscovered: n } = await import("./dev-BWwE0QjK.js"), { outgoingFromEvents: r } = await import("./webhookDiscovery-il9ti-HE.js");
 	return r((await n(await t(e))).events.map((e) => ({
 		file: e.file,
 		descriptor: e.descriptor

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@voltro/cli",
-  "version": "0.49.0",
+  "version": "0.50.0",
   "description": "The `voltro` CLI — dev server, codegen, migrations, project scaffolding, agent-docs seeding, and production serve.",
   "keywords": [
     "voltro",
@@ -676,6 +676,24 @@
         "title": "store.query() now returns the row type — casts on row fields may stop compiling",
         "kind": "manual"
       },
+      {
+        "version": "0.50.0",
+        "id": "0.50.0/01_transfer-runs-endpoint",
+        "title": "`GET /_voltro/admin/imports` → `GET /_voltro/admin/transfers`",
+        "kind": "manual"
+      },
+      {
+        "version": "0.50.0",
+        "id": "0.50.0/02_reissue-data-imports-rename",
+        "title": "RE-CHECK: `voltro data imports` → `voltro data transfers` (0.49.0's note could not see your scripts)",
+        "kind": "manual"
+      },
+      {
+        "version": "0.50.0",
+        "id": "0.50.0/03_interrupted-replace-tables-nullable",
+        "title": "`InterruptedReplace.tables` is `number | null`",
+        "kind": "manual"
+      },
       {
         "version": "0.6.0",
         "id": "0.6.0/01_no-dev-session-secret",
@@ -751,22 +769,22 @@
     "@effect/platform-node": "^0.108.0",
     "@effect/sql": "^0.52.0",
     "@effect/workflow": "^0.19.0",
-    "@voltro/ai": "0.49.0",
-    "@voltro/cache": "0.49.0",
-    "@voltro/data-transfer": "0.49.0",
-    "@voltro/database": "0.49.0",
-    "@voltro/env": "0.49.0",
-    "@voltro/kv": "0.49.0",
-    "@voltro/logger": "0.49.0",
-    "@voltro/plugin-auth": "0.49.0",
-    "@voltro/plugin-broadcast": "0.49.0",
-    "@voltro/plugin-mail": "0.49.0",
-    "@voltro/plugin-storage": "0.49.0",
-    "@voltro/plugin-webhooks": "0.49.0",
-    "@voltro/protocol": "0.49.0",
-    "@voltro/runtime": "0.49.0",
-    "@voltro/serverless": "0.49.0",
-    "@voltro/workflow": "0.49.0",
+    "@voltro/ai": "0.50.0",
+    "@voltro/cache": "0.50.0",
+    "@voltro/data-transfer": "0.50.0",
+    "@voltro/database": "0.50.0",
+    "@voltro/env": "0.50.0",
+    "@voltro/kv": "0.50.0",
+    "@voltro/logger": "0.50.0",
+    "@voltro/plugin-auth": "0.50.0",
+    "@voltro/plugin-broadcast": "0.50.0",
+    "@voltro/plugin-mail": "0.50.0",
+    "@voltro/plugin-storage": "0.50.0",
+    "@voltro/plugin-webhooks": "0.50.0",
+    "@voltro/protocol": "0.50.0",
+    "@voltro/runtime": "0.50.0",
+    "@voltro/serverless": "0.50.0",
+    "@voltro/workflow": "0.50.0",
     "chokidar": "^5.0.0",
     "ioredis": "^5.11.1",
     "tinyglobby": "^0.2.17",

package/templates/AGENTS.md

@@ -707,7 +707,7 @@ each plugin's own README.
 
 | Topic | Open | Summary |
 |---|---|---|
-| **What's new in 0.49.0** | `node_modules/@voltro/cli/templates/agent-docs/whats-new.md` | Everything that changed in this version. Read it before hand-rolling something the framework may now ship. |
+| **What's new in 0.50.0** | `node_modules/@voltro/cli/templates/agent-docs/whats-new.md` | Everything that changed in this version. Read it before hand-rolling something the framework may now ship. |
 | AI | `node_modules/@voltro/cli/templates/agent-docs/ai.md` | How Voltro treats AI — agents, tools, streaming, RAG — all primitives over the same WebSocket as the rest of the framework. |
 | Authentication | `node_modules/@voltro/cli/templates/agent-docs/authentication.md` | How @voltro/plugin-auth wires password + session-cookie auth across api + web, plus the pluggable identity-strategy protocol. |
 | Caching | `node_modules/@voltro/cli/templates/agent-docs/caching.md` | Voltro's caching layer (@voltro/cache) — an always-on memory default, swappable Redis-compatible backends, a low-level wrap primitive, and automatic query-result invalidation. |

package/templates/agent-docs/_index.md

@@ -9,7 +9,7 @@ each plugin's own README.
 
 | Topic | Open | Summary |
 |---|---|---|
-| **What's new in 0.49.0** | `node_modules/@voltro/cli/templates/agent-docs/whats-new.md` | Everything that changed in this version. Read it before hand-rolling something the framework may now ship. |
+| **What's new in 0.50.0** | `node_modules/@voltro/cli/templates/agent-docs/whats-new.md` | Everything that changed in this version. Read it before hand-rolling something the framework may now ship. |
 | AI | `node_modules/@voltro/cli/templates/agent-docs/ai.md` | How Voltro treats AI — agents, tools, streaming, RAG — all primitives over the same WebSocket as the rest of the framework. |
 | Authentication | `node_modules/@voltro/cli/templates/agent-docs/authentication.md` | How @voltro/plugin-auth wires password + session-cookie auth across api + web, plus the pluggable identity-strategy protocol. |
 | Caching | `node_modules/@voltro/cli/templates/agent-docs/caching.md` | Voltro's caching layer (@voltro/cache) — an always-on memory default, swappable Redis-compatible backends, a low-level wrap primitive, and automatic query-result invalidation. |

package/templates/agent-docs/cli.md

@@ -2996,7 +2996,7 @@ $ voltro data transfers --target api --api-url https://app.example
   2026-08-23T08:00:00.000Z · export all — 228866 row(s) across 104 table(s) · via api · from backups/nightly.vbundle
 ```
 
-Same data over `GET /_voltro/admin/imports?limit=20`, behind the same
+Same data over `GET /_voltro/admin/transfers?limit=20`, behind the same
 data-transfer secret (the row names bundles and schema fingerprints). It works
 from a different machine than the one that started the import, and through
 anything that forwards a GET.
@@ -3330,12 +3330,62 @@ yield* runImport({ store: target, bundleDir: './backup', targetSnapshot }).pipe(
 ## Native backup / restore
 
 ```bash
-voltro data backup ./backups/2026-07-01     # pg_dump --format=custom / mysqldump --single-transaction / …
-voltro data restore ./backups/2026-07-01    # pg_restore / mysql / …
+voltro data backup ./backups/2026-07-01              # pg_dump --format=custom / mariadb-dump --single-transaction / …
+voltro data backup ./backups/2026-07-01 --assets     # rows AND the stored blobs
+voltro data restore ./backups/2026-07-01 --assets    # pg_restore / mariadb / … + the blobs
 ```
 
 These shell out to the vendor tools resolved from your `DB_DIALECT` + connection env. They produce a dialect-native artifact (`db.dump`, `db.sql`, `db.sqlite`, `db.bacpac`) that is lossless and point-in-time consistent for **same-dialect** restore — the right tool for disaster recovery. Secrets are passed via the tools' environment variables (`PGPASSWORD`, `MYSQL_PWD`), never on the command line, where the tool supports it. The named tool must be installed and on `PATH`.
 
+### `--assets` — the blobs are not in the dump
+
+A vendor dump contains rows. Your blobs are in object storage, and no `pg_dump` has ever seen them. So a rows-only backup restores a database whose rows reference objects that are not there — and the reference and the object are checked at different times, which is why that state is discovered by a user, months later, rather than by the restore.
+
+`--assets` captures them alongside the dump, through the same content-addressed pipeline `voltro data export --assets` uses: each blob is streamed (never buffered whole), stored under `assets/<sha256>` so identical content is stored once, and listed in `assets/index.ndjson`. `restore --assets` streams them back and **re-hashes on the way**, so a corrupted artifact can never silently overwrite good bytes.
+
+```
+backups/2026-07-01/
+├─ db.dump                       # the vendor artifact (rows)
+├─ voltro-backup-stamp.json      # provenance, incl. what --assets captured
+├─ assets/index.ndjson           # key → sha256 → size → contentType
+└─ assets/<sha256>               # the blob bodies, deduped by content
+```
+
+Three refusals, each for a belief that is otherwise acted on silently:
+
+- **`backup --assets` with no storage provider configured → refused.** There is nothing to capture, and a flag that is accepted and ignored lets you build a rollback story on an artifact that does not contain what you asked for.
+- **`restore --assets` on a rows-only backup → refused.** You believe the blobs are in there. Restoring the rows anyway produces exactly the dangling state this exists to prevent.
+- **restore *without* `--assets` on a backup that HAS them → warned, not refused.** Restoring rows without blobs is legitimate (a schema drill, a lower environment), and refusing it would push people at `--force`.
+
+Resume is per blob key, so re-running a `--assets` capture that was interrupted transfers only what is missing. The **dump itself has no resume** — a vendor artifact is one opaque file with no offset to restart from. If you need a resumable, chunkable, observable transfer, that is the logical path (`export` / `import`), and it is why the logical path exists.
+
+### A restore that is interrupted refuses the next boot
+
+`restore` writes one row into `_voltro_replace_in_progress` **before** the first destructive statement and removes it **after** the last write — the blobs included. Its presence at boot is a refusal naming the artifact that was going in.
+
+This is the counterpart to `--allow-live`, and it guards from the other side: `--allow-live` asks you not to restore over a running instance, and this says *this database is mid-restore, do not serve it*. A half-restored database looks exactly like a normal one from the inside — every query answers, nothing errors.
+
+Whether the marker survives the restore depends on the dialect's restore shape, and that is stated rather than implied:
+
+| dialect | shape | effect |
+|---|---|---|
+| postgres, mysql, mariadb | drops only the objects the dump names | the marker survives, so a killed restore is caught at the next boot |
+| sqlite, turso | whole-file replacement — made **atomic** (temp file + rename) | there is no half-restored state to catch; a killed restore leaves the live file untouched |
+| mssql | `sqlpackage /Action:Import` replaces the database | a *failed* import is the one case not covered here — verify with `--drill` |
+
+Clear a marker deliberately with `voltro data clear-replace-marker --yes` once you have decided the current state is correct.
+
+### Both directions are in the history
+
+`backup` and `restore` write a row to the same `_voltro_data_transfers` record `import` and `export` use, so `voltro data transfers` answers "did last night's backup finish" from the instance that ran it:
+
+```
+2026-08-23T02:00:00.000Z · backup native postgres + assets — finished (412 blob(s)) · via cli · from ./backups/2026-08-23/db.dump
+2026-08-22T09:14:02.000Z · FAILED restore native mariadb — mariadb-dump: exited with code 2 · via cli · from ./backups/2026-08-21/db.sql
+```
+
+A native run reports **blobs**, not rows: the vendor tool reports no row count we can trust, and printing `0 row(s)` over a `pg_dump` that worked would be a measurement, and a wrong one. A target with no `_voltro_data_transfers` table still gets its backup — the closing line says it was not recorded, rather than implying it was.
+
 ### The provenance stamp — a restore that refuses the wrong DB
 
 A native dump is opaque: it doesn't say which dialect made it, which schema shape it carries, or when. `backup` writes a sidecar `voltro-backup-stamp.json` next to the artifact recording exactly that — `dialect`, the live schema `fingerprint`, the `@voltro/cli` version, and the timestamp.

package/templates/agent-docs/whats-new.md

@@ -1,4 +1,4 @@
-# What's new in 0.49.0
+# What's new in 0.50.0
 
 Read this FIRST when a task touches an area you have not worked in recently.
 It is the cheapest way to notice that the framework grew the thing you were
@@ -9,63 +9,54 @@ BREAKING entries name a codemod; run `voltro update` to apply it.
 
 ### ⚠ BREAKING
 
-- **@voltro/cli, @voltro/data-transfer, @voltro/database, @voltro/sql-sqlite, @voltro/voltro** — A data transfer is a series of short requests now — no single one may outlive a caller's budget.
+- **@voltro/cli** — The read-only run-history endpoint moved:
 
-  **The rule:** *a request that carries bytes never runs a transfer; a request that starts a transfer never carries bytes.* It was broken in the worst available place. The upload was already chunked and resumable — many short requests, each abandonable — and then the FINAL chunk fell through and ran the whole import. So the longest request of the flow arrived AFTER the entire upload had succeeded, and a caller under a policy that caps a single request (a job runner that kills a client at ten minutes; a 30 s ingress ceiling) lost the most expensive thing they had already paid for. A single-request upload had the same shape without the excuse, and the export had no protocol at all: one request that read the whole database and streamed it back.
+  GET /_voltro/admin/imports → GET /_voltro/admin/transfers
 
-  **Import.** `POST /_voltro/admin/import` accumulates and answers `202`. `POST /_voltro/admin/import/start` begins the run and answers `202 { runId }` as soon as the run's first row exists. `start` is idempotent per upload — it is a short request and therefore a retryable one, and without a claim a retry would begin a second destructive run from the same bytes. A claim whose run has ENDED is taken over rather than honoured forever, so a process that dies holding one cannot poison a bundle.
+  Same secret, same query parameters, same response shape. Only the path changed.
 
-  **Export.** `POST /_voltro/admin/export` answers `202 { runId }` and produces in the background; the bytes come back from `GET /_voltro/admin/export/download?runId=&offset=&length=` in ranges, resumable, with the total in a header. Object storage (`--bundle-key`) remains for a bundle you want to KEEP — it is no longer the only way to get one out, because requiring it would leave an instance without storage unable to export at all.
+  It answers for four directions now — import, export, native backup, native restore — and it named one of them. The subcommand and the table were renamed for exactly that reason in 0.49.0 and this path was left behind, which is worse than renaming none of them: a reader who follows a rename tries the matching path, gets a 404, and concludes the instance is too old.
 
-  **The client.** `--max-request-seconds` (or `VOLTRO_MAX_REQUEST_SECONDS`) declares the budget — declared rather than probed, because the thing that kills a request is a policy on the caller's side and only they know it. `--detach` returns once the run has started and says the outcome is NOT known. Attached, the CLI polls the record and prints per-table progress; Ctrl-C then loses the watching and never the run.
+  `voltro data transfers --target api` uses the new path for you. What needs a hand is anything calling it directly — a monitoring check, an uptime probe, a curl in a runbook, a dashboard datasource. The codemod is `manual` and declares `reach: 'beyond-source'`, so it prints whether or not the path is found in your repository.
+- **@voltro/database, @voltro/voltro** — `InterruptedReplace.tables` is `number | null`, and the interface gains `kind?: 'replace' | 'restore'`.
 
-  **The trap, stated because it is the one way to get this wrong:** a failure used to arrive in the response (409 on drift, 409 on a refused mode, 500 otherwise). After the split the response is a `202`, so **a client deriving its exit code from the status line reports a failed import as a success.** The exit code comes from the polled record, in one shared function, and the drift check moved into `start` where it can still be a refusal that leaves no history.
+  `_voltro_replace_in_progress` records two destructive operations now — an import's `--mode replace` and a native `voltro data restore`. A restore replaces the whole database from an artefact, so "how many tables was this going to empty and refill" has no answer: not known up front, not meaningful after.
 
-  **Two knobs that were constants.** `VOLTRO_IMPORT_UPLOAD_DIR` and `VOLTRO_EXPORT_ARTIFACT_DIR` move the staging areas off the default temp filesystem — which on a container is frequently a small tmpfs, so an instance simply could not accept a bundle the size a grown database produces, and the failure arrived as a write error halfway through an upload somebody had been waiting on.
+  Writing `0` would have preserved the type and been worse. That number is rendered into the boot refusal, which is read under pressure, and it would have said `began emptying 0 table(s)` — a measurement that was never taken. The framework's own text says "this database" instead; `Number(null)` is `0`, so coercing it reintroduces exactly the sentence being avoided.
 
-  **Renamed:** `voltro data imports` → `voltro data transfers`, and `_voltro_data_imports` → `_voltro_data_transfers` with a `direction` column. The command showed one direction and now shows both; the table rename carries its rows via the declarative differ on every dialect and needs nothing from you. The CLI rename ships a `manual` codemod — the command lives in scripts, CI jobs and runbooks, which `voltro update` cannot see or rewrite. The four PUBLIC exports that named the same record were renamed with it (`ImportRun`, `describeImportRun`, `IMPORT_RUNS_TABLE`, `_voltroImportRunsTable`); those are application source, they ship their own `transform` codemod, and they have their own entry.
-- **@voltro/database, @voltro/voltro** — The run-history exports say `transfer`, not `import`.
+  `DataTransferRun.direction` also widens to name `'backup'` and `'restore'` explicitly. That one is documentary — the union already ended in `| string`, so no assignability changes.
 
-  `@voltro/database` (and `voltro/database`) renamed four public exports along with the table behind them:
-
-  | was | is | |---|---| | `ImportRun` | `DataTransferRun` | | `describeImportRun` | `describeTransferRun` | | `IMPORT_RUNS_TABLE` | `DATA_TRANSFERS_TABLE` | | `_voltroImportRunsTable` | `_voltroDataTransfersTable` |
-
-  An EXPORT writes to this record now — the row carries a `direction` — so every one of those names described half of what it holds.
-
-  A `transform` codemod rewrites all four, alias-aware, from either module spelling. It also rewrites a hand-spelled `_voltro_data_imports` in a string, template or raw-SQL fragment, and that is the half worth stating: the four identifiers announce themselves as compile errors, while a query that addresses the table by name has nothing to fail on. The table itself moves with its rows via the declarative differ on every dialect.
-
-  This is filed apart from the transfer-protocol entry beside it deliberately. That one's codemod is `manual` and is about a CLI invocation living in scripts and CI jobs; this one is application source and is rewritten for you. Reading the first as covering both is what would leave a build broken with a note saying nothing in your source was affected.
+  **`voltro update` carries you across this** — codemod `0.50.0/03_interrupted-replace-tables-nullable`.
 
 ### Added
 
-- **@voltro/database, @voltro/data-transfer, @voltro/cli** — An import records WHETHER it staged, and a soft-dropped column says so in a drift refusal.
+- **@voltro/cli, @voltro/data-transfer, @voltro/database** — `voltro data backup --assets` and `voltro data restore --assets` now move the stored blobs alongside the vendor dump, through the same content-addressed phase the logical `export` / `import` path uses — streamed, deduped by sha256, verified on the way back, resumable per key.
 
-  **`_voltro_data_imports.staged`.** The pre-upload preflight says what the instance WILL do; the run's own line says what it did — and that line is printed inside the instance, which is exactly where an operator using `--target api` cannot read it. So "we were told it would stage" and "it staged" were two claims with no way to close the gap between them from outside. The column is `null` for a mode where the question does not arise; `voltro data imports` and `GET /_voltro/admin/imports` both carry it.
+  `--assets` was accepted by `backup` and silently ignored, with the only signal a field in the closing JSON reading `NOT included`; `restore` did not accept it at all. A rows-only backup restores a database whose rows reference objects nothing puts back, and the reference and the object are checked at different times, so that state is discovered by a user rather than by the restore.
 
-  **A soft-dropped column is named as one.** `<original>__dropped_<stamp>` is what the differ leaves behind when an app stops declaring a column — only the database that did the drop has it, so it drifts against every target. The refusal reported it as an ordinary missing column ("the value has nowhere to go"), which points at the TARGET's schema: the one place the fix does not lie. It now says where the column lives and how to reclaim it.
+  Three refusals, each for a belief that is otherwise acted on silently: `backup --assets` with no storage provider is refused rather than swallowed; `restore --assets` on a rows-only artefact is refused; a restore WITHOUT `--assets` over an artefact that has them warns and proceeds, because restoring rows without blobs is legitimate and refusing it would push people at `--force`.
 
-### Fixed
-
-- **@voltro/data-transfer, @voltro/sql-sqlite, @voltro/database** — A successful `--mode replace --no-atomic` left a marker that refused the next boot.
+  The dump itself still has no resume — a vendor artefact is one opaque file with no offset to restart from, and the logical path is what exists for that.
+- **@voltro/cli, @voltro/database, @voltro/data-transfer** — A native `backup` / `restore` now writes to the same `_voltro_data_transfers` record `import` and `export` use, so `voltro data transfers` answers "did last night's backup finish" from the instance that ran it. A native run reports blobs rather than rows — a vendor tool reports no row count we can trust, and printing `0 row(s)` over a dump that worked would be a wrong measurement.
 
-  Two defects, one visible symptom, and both were silent by construction.
+  `restore` also writes the `_voltro_replace_in_progress` marker before its first destructive statement and clears it after the last write, blobs included, so a killed restore refuses the next boot instead of serving a half-loaded database. `--allow-live` guards from the wrong side — it asks you not to — and this guards from the right one. The marker carries a `kind` so the refusal can say something different for a `replace` (re-import the capture) and a `restore` (finish the restore), and `tables` is nullable because a native restore has no table count to claim.
 
-  **The clear was gated on the WRITE's condition.** `!(useLedger && ledger.truncated)` means "an earlier attempt already recorded this destructive run, do not write a second row" — correct on the write. Copied down to the clear its meaning inverts: `ledger.truncated` is set by the emptying step of THIS run, so on `--no-atomic` (the only mode where `useLedger` is true) the clear was skipped by the very run that wrote the marker.
+  The sqlite / turso restore is atomic now (temp file + rename): its marker lives in the very file being replaced, so a plain in-place copy would leave a truncated database with nothing left to catch it.
 
-  **And a `Date` in a predicate is not bindable on sqlite.** `better-sqlite3` binds numbers, strings, bigints, buffers and null; the row path has coerced Dates since that store was written, and the eager-join compiler carried its own private copy of the fix, but `query` / `updateMany` / `deleteMany` bound the raw value. So every comparison of a timestamp column against a `Date` failed with `Failed to execute statement` — including the marker's clear, which swallows its errors ON PURPOSE (a store with no marker table must not fail an import over a bookkeeping row) and therefore said nothing. The retention sweep compares `lt(column, cutoff)` the same way.
+  A target with no `_voltro_data_transfers` table still gets its backup; the closing line says it was not recorded rather than implying it was.
+- **@voltro/cli** — A re-issued migration note for the `voltro data imports` → `voltro data transfers` rename that shipped in 0.49.0.
 
-  Together: a fully successful replace left the marker standing, and the next boot REFUSED with "a destructive import did not finish" over a database that was completely fine. The one recovery is a command the operator has no reason to think they need. It stayed invisible because `atomic` defaults to true for `replace`, and because a staged replace writes no marker at all — two defaults hiding the one mode that exists for large, interruptible loads.
+  Codemods are selected by `from < version <= to`, so the 0.49.0 note fires once, on the jump that crosses 0.49.0, and cannot be corrected for anyone already past it. Its gate searched `.ts` / `.tsx` while the command it is about lives in shell scripts, CI job definitions and runbooks — so a project whose only occurrence sat in `.gitlab-ci.yml` crossed 0.49.0 and was told there was nothing to apply.
 
-  The coercion is shared now and applied at all three predicate sites, with a guard that fails on a fourth that forgets. A dry run also closes its trace row: a preview that finished instantly used to leave the record open, so a polling caller waited out its whole budget over a run that was long done.
-- **@voltro/cli** — `voltro codegen` declared twenty framework tables fewer than a boot.
+  The re-issue is filed under 0.50.0, prints unconditionally, and says what to grep for. Redundant for anyone already fixed; the alternative is firing for nobody.
 
-  The app half of this was fixed last release and looked like the whole thing. It was not: `codegen` derived the FEATURE MIX from the file list it had just walked, and that list is the entity/relations set — which contains no `*.workflow.tsx`, no `*.agent.ts`, no `*.cron.tsx`. So every feature flag came back false, and the dialect was never passed at all, taking `_voltro_cdc_offsets` with it. Measured on an app with two workflow files: 18 framework tables where the shared assembly produces 33.
+### Fixed
 
-  It calls `assembleFrameworkTables({ root })` now — the same entry `voltro db plan/apply` uses, which detects the mix from the root rather than being handed one.
+- **@voltro/cli** — A `manual` codemod's `appliesTo` can now search every text file the project owns — `.sh`, `.yml`, `.json`, `.md`, `Makefile`, the `.js` scripts — through a new `ctx.text` on the predicate context, and a codemod may declare `reach: 'beyond-source'` to print its note even when nothing matched.
 
-  The parity guard moved with it. Comparing the two WALKS could not see this: both walks were right about files, and the divergence was introduced one layer past them. It compares the assembled SETS now, and runs codegen's own table function on a tree whose only feature signals are a workflow file and an agent file — a source assertion that the right function is CALLED cannot see a wrong argument handed to it, and a wrong argument is what this was.
-- **@voltro/cli** — `voltro data --help` advertised four subcommands out of nine.
+  Both halves close the same gap, and it was in the codemod most in need of a gate. A manual codemod exists BECAUSE its subject could not be transformed, which usually means it is not source at all — and `appliesTo` was reading the ts-morph project, which holds `.ts` / `.tsx` and nothing else. Measured with one identical CLI invocation in four files: the `.ts` one printed the note, the `.sh`, `.yml` and `.md` ones printed nothing, and the run reported `codemods: nothing to apply for this jump`. That is an acquittal from a check that never looked at the file, and an acquittal gets acted on.
 
-  It printed `<export|import|backup|restore>` while the command dispatched those four plus `imports`, `inspect`, `unpack`, `clear-replace-marker` and `clear-staging`. A quoted enumeration is read as exhaustive — the same failure `subcommandNames.ts` was written for after a `db` list cost two wrong conclusions — and the missing entry here is the one that answers "what is my import doing right now" for somebody who cannot reach the pod.
+  `reach: 'beyond-source'` covers what no scan of one repository can reach — an inline script in a CI runner's own UI, a CronJob spec in another repo, a wiki runbook. The note prints either way; only its framing changes, and an uncertain one says plainly that we could not look there.
+- **@voltro/data-transfer** — When `mariadb-dump` is absent and the mysql-family fallback runs Oracle's `mysqldump` against a MariaDB server, the failure now names the way out.
 
-  `subcommandHelpParity.test.ts` had listed `data` among the commands it could not check, loudly and correctly: there was no name list to check against. There is one now (`DATA_SUBCOMMANDS`), the dispatch is a keyed `Record`, so a subcommand with no name and a name with no handler are both compile errors, and the usage line is generated from the same array. `data` is out of the unchecked list.
+  The stderr it prints is the child's own words and is the right first thing to show — and on its own it is a dead end: `Unknown table 'COLUMN_STATISTICS' in information_schema (1109)` names a table nobody asked for, in a schema nobody wrote, about a feature nobody enabled. Everything needed to act on it was known where the fallback was DECIDED: which binary we wanted, which one we took, and why the difference matters. That travels with the step now and prints under the stderr, including the counter-move a reader reaches for on their own (`--column-statistics=0` does not exist on `mariadb-dump`, so it fixes the wrong client and breaks the right one).