@metabase/cli 0.3.0 → 0.3.1-alpha.support-worktrees.b634907

package/dist/{update-D-NE60AV.mjs → update-D9OTkZhw.mjs}

@@ -1,7 +1,7 @@
-import { F as outputFlags, I as profileFlag, M as connectionFlags, c as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-DiKyBxOw.mjs";
-import { t as parseId } from "./parse-id-C_jmKFaa.mjs";
-import { t as readBody } from "./body-Cur4NJt9.mjs";
+import { H as profileFlag, R as connectionFlags, V as outputFlags, p as renderSummary } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
+import { t as parseId } from "./parse-id-DDCn3VXx.mjs";
+import { t as readBody } from "./body-DxRSAMNC.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { i as DocumentUpdateInput, t as Document } from "./document-Cd2mmqCp.mjs";
 import { t as documentView } from "./document-D6OybtP2.mjs";
@@ -12,6 +12,7 @@ var update_default = defineMetabaseCommand({
 		description: "Update a document by id"
 	},
 	capabilities: { minVersion: 58 },
+	worktree: "main-only",
 	args: {
 		...outputFlags,
 		...profileFlag,

package/dist/{update-dashcard-C3TuYO_k.mjs → update-dashcard-St-dGcE3.mjs}

@@ -1,10 +1,10 @@
-import { F as outputFlags, I as profileFlag, M as connectionFlags, c as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-DiKyBxOw.mjs";
-import { t as parseId } from "./parse-id-C_jmKFaa.mjs";
-import { t as readBody } from "./body-Cur4NJt9.mjs";
+import { H as profileFlag, R as connectionFlags, V as outputFlags, p as renderSummary } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
+import { t as parseId } from "./parse-id-DDCn3VXx.mjs";
+import { t as readBody } from "./body-DxRSAMNC.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
-import { l as DashcardPatchInput, s as Dashcard } from "./dashboard-BCpSq_G-.mjs";
-import { n as dashcardView } from "./dashboard-CsIFFpzK.mjs";
+import { l as DashcardPatchInput, s as Dashcard } from "./dashboard-CKUR8ZpQ.mjs";
+import { n as dashcardView } from "./dashboard-BlbNszi8.mjs";
 //#region src/commands/dashboard/update-dashcard.ts
 var update_dashcard_default = defineMetabaseCommand({
 	meta: {
@@ -12,6 +12,7 @@ var update_dashcard_default = defineMetabaseCommand({
 		description: "Patch a single dashcard's layout or settings on a dashboard"
 	},
 	capabilities: { minVersion: 58 },
+	worktree: "main-only",
 	args: {
 		...outputFlags,
 		...profileFlag,

package/dist/{update-CHNSUHK4.mjs → update-e7lyQPxq.mjs}

@@ -1,10 +1,10 @@
-import { F as outputFlags, I as profileFlag, M as connectionFlags, c as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-DiKyBxOw.mjs";
-import { t as parseId } from "./parse-id-C_jmKFaa.mjs";
-import { t as readBody } from "./body-Cur4NJt9.mjs";
+import { H as profileFlag, R as connectionFlags, U as worktreeFlag, V as outputFlags, p as renderSummary } from "./cli.mjs";
+import { i as assertInWorktree, r as WORKTREE_SCOPE_DETAIL, t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
+import { t as parseId } from "./parse-id-DDCn3VXx.mjs";
+import { t as readBody } from "./body-DxRSAMNC.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
-import { i as SnippetUpdateInput, t as Snippet } from "./snippet-CyKAgIZl.mjs";
-import { t as snippetView } from "./snippet-oJLaYW9V.mjs";
+import { i as SnippetUpdateInput, t as Snippet } from "./snippet-BxgvQ09J.mjs";
+import { t as snippetView } from "./snippet-DecHB4Dn.mjs";
 //#region src/commands/snippet/update.ts
 var update_default = defineMetabaseCommand({
 	meta: {
@@ -12,10 +12,13 @@ var update_default = defineMetabaseCommand({
 		description: "Update a native query snippet by id"
 	},
 	capabilities: { minVersion: 58 },
+	worktree: "scoped",
+	details: WORKTREE_SCOPE_DETAIL,
 	args: {
 		...outputFlags,
 		...profileFlag,
 		...connectionFlags,
+		...worktreeFlag,
 		...bodyInputFlags,
 		id: {
 			type: "positional",
@@ -31,13 +34,16 @@ var update_default = defineMetabaseCommand({
 		"mb snippet update 1 --body '{\"name\":\"renamed\"}'",
 		"mb snippet update 1 --body '{\"archived\":true}'"
 	],
-	async run({ args, ctx, getClient }) {
+	async run({ args, ctx, getClient, getWorktree }) {
 		const id = parseId(args.id);
 		const body = await readBody({
 			flag: args.body,
 			file: args.file
 		}, SnippetUpdateInput);
-		const updated = await (await getClient()).snippet.update(id, body);
+		const client = await getClient();
+		const scope = await getWorktree();
+		if (scope !== null) assertInWorktree("snippet", id, (await client.snippet.get(id)).worktree_id, scope);
+		const updated = await client.snippet.update(id, body);
 		renderSummary(updated, snippetView, `Updated snippet ${updated.id} "${updated.name}".`, ctx);
 	}
 });

package/dist/{update-CvOO8TED.mjs → update-rkbpH0lF.mjs}

@@ -1,7 +1,7 @@
-import { F as outputFlags, I as profileFlag, M as connectionFlags, c as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-DiKyBxOw.mjs";
-import { t as parseId } from "./parse-id-C_jmKFaa.mjs";
-import { t as readBody } from "./body-Cur4NJt9.mjs";
+import { H as profileFlag, R as connectionFlags, V as outputFlags, p as renderSummary } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
+import { t as parseId } from "./parse-id-DDCn3VXx.mjs";
+import { t as readBody } from "./body-DxRSAMNC.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { a as TableUpdateInput, t as Table } from "./table-CeeTJgQb.mjs";
 import { t as tableView } from "./table-CsIJNPFf.mjs";
@@ -12,6 +12,7 @@ var update_default = defineMetabaseCommand({
 		description: "Update a table (display name, description, visibility, etc.)"
 	},
 	capabilities: { minVersion: 58 },
+	worktree: "main-only",
 	args: {
 		...outputFlags,
 		...profileFlag,

package/dist/{upgrade-DXMV4AyP.mjs → upgrade-CUoRHfVg.mjs}

@@ -1,7 +1,7 @@
 import { f as errorMessage, l as TimeoutError, n as AbortError, s as NetworkError, u as UnknownError } from "./predicates-Bkm2IoeX.mjs";
-import { A as name, F as outputFlags, h as promptConfirm, j as version, o as renderItem, t as interruptSignal, u as writeText } from "./cli.mjs";
-import { t as defineMetabaseCommand, u as USER_AGENT } from "./runtime-DiKyBxOw.mjs";
-import { h as parseJson, r as HttpError } from "./network-error-CEb9ymDW.mjs";
+import { I as name, L as version, V as outputFlags, b as promptConfirm, d as renderItem, h as writeText, n as interruptSignal } from "./cli.mjs";
+import { g as USER_AGENT, t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
+import { h as parseJson, r as HttpError } from "./network-error-D6CiOEBw.mjs";
 import { n as throwIfAborted, t as combineAborts } from "./signal-CMd0EFUa.mjs";
 import { n as streamProcess } from "./process-DBOOrmET.mjs";
 import { z } from "zod";
@@ -292,6 +292,7 @@ var upgrade_default = defineMetabaseCommand({
 		description: "Upgrade the Metabase CLI itself to the latest published release"
 	},
 	capabilities: null,
+	worktree: "any",
 	args: {
 		...outputFlags,
 		check: {

package/dist/upload-BPd1Uzxc.mjs

@@ -0,0 +1,43 @@
+import { H as profileFlag, R as connectionFlags, V as outputFlags, p as renderSummary } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
+import { t as ContentTranslationUploadResult } from "./content-translation-BrHOrmj9.mjs";
+import { n as requireUploadFilePath, t as readCsvFile } from "./upload-CD555ui1.mjs";
+//#region src/output/views/content-translation.ts
+const contentTranslationUploadView = {
+	compactPick: ContentTranslationUploadResult,
+	tableColumns: [{
+		key: "success",
+		label: "Success"
+	}]
+};
+//#endregion
+//#region src/commands/content-translation/upload.ts
+var upload_default = defineMetabaseCommand({
+	meta: {
+		name: "upload",
+		description: "Replace the complete content translation dictionary from CSV"
+	},
+	details: "Uploads one complete dictionary and replaces every active content translation on the server. Keep the canonical full CSV in version control and download the current dictionary before replacing it. Metabase accepts dictionaries up to 1.5 MiB.",
+	capabilities: {
+		minVersion: 58,
+		tokenFeature: "content_translation"
+	},
+	worktree: "main-only",
+	args: {
+		...outputFlags,
+		...profileFlag,
+		...connectionFlags,
+		file: {
+			type: "string",
+			description: "Path to the complete translation dictionary CSV"
+		}
+	},
+	outputSchema: ContentTranslationUploadResult,
+	examples: ["mb content-translation upload --file translations.csv", "mb content-translation upload --file translations.csv --profile prod --json"],
+	async run({ args, ctx, getClient }) {
+		const file = await readCsvFile(requireUploadFilePath(args.file));
+		renderSummary(await (await getClient()).contentTranslation.upload(file), contentTranslationUploadView, `Replaced the content translation dictionary with "${file.filename}".`, ctx);
+	}
+});
+//#endregion
+export { upload_default as default };

package/dist/upload-C3z5ZaXA.mjs

@@ -0,0 +1,24 @@
+import { n as UploadUpdateResult, t as UploadResult } from "./upload-DAtxBBms.mjs";
+//#region src/output/views/upload.ts
+const uploadResultView = {
+	compactPick: UploadResult,
+	tableColumns: [{
+		key: "model_id",
+		label: "Model ID"
+	}, {
+		key: "table_id",
+		label: "Table ID"
+	}]
+};
+const uploadUpdateResultView = {
+	compactPick: UploadUpdateResult,
+	tableColumns: [{
+		key: "table_id",
+		label: "Table ID"
+	}, {
+		key: "action",
+		label: "Action"
+	}]
+};
+//#endregion
+export { uploadUpdateResultView as n, uploadResultView as t };

package/dist/{upload-CH632qW6.mjs → upload-CD555ui1.mjs}

@@ -1,30 +1,7 @@
 import { i as ConfigError, p as isFileNotFoundError } from "./predicates-Bkm2IoeX.mjs";
 import { n as fileNotFoundError } from "./input-DH9i67x_.mjs";
-import { n as UploadUpdateResult, t as UploadResult } from "./upload-DAtxBBms.mjs";
 import { basename } from "node:path";
 import { readFile } from "node:fs/promises";
-//#region src/output/views/upload.ts
-const uploadResultView = {
-	compactPick: UploadResult,
-	tableColumns: [{
-		key: "model_id",
-		label: "Model ID"
-	}, {
-		key: "table_id",
-		label: "Table ID"
-	}]
-};
-const uploadUpdateResultView = {
-	compactPick: UploadUpdateResult,
-	tableColumns: [{
-		key: "table_id",
-		label: "Table ID"
-	}, {
-		key: "action",
-		label: "Action"
-	}]
-};
-//#endregion
 //#region src/runtime/upload.ts
 function requireUploadFilePath(file) {
 	if (typeof file !== "string" || file.trim() === "") throw new ConfigError("provide the CSV file to upload with --file <path>");
@@ -43,4 +20,4 @@ async function readCsvFile(path) {
 	}
 }
 //#endregion
-export { uploadUpdateResultView as i, requireUploadFilePath as n, uploadResultView as r, readCsvFile as t };
+export { requireUploadFilePath as n, readCsvFile as t };

package/dist/upload-Dc3QLhZw.mjs

@@ -0,0 +1,13 @@
+import { t as defineCommandGroup } from "./group-YN6jj2AN.mjs";
+//#region src/commands/upload/index.ts
+var upload_default = defineCommandGroup({
+	name: "upload",
+	description: "Upload CSV files into Metabase",
+	subCommands: {
+		csv: () => import("./csv-DBNzJiWK.mjs").then((m) => m.default),
+		append: () => import("./append-B0avMkvW.mjs").then((m) => m.default),
+		replace: () => import("./replace-mt47dlRV.mjs").then((m) => m.default)
+	}
+});
+//#endregion
+export { upload_default as default };

package/dist/{uuid-BJkDWj9p.mjs → uuid-CFN8LIkP.mjs}

@@ -1,6 +1,6 @@
 import { i as ConfigError } from "./predicates-Bkm2IoeX.mjs";
-import { F as outputFlags, l as writeJson, u as writeText } from "./cli.mjs";
-import { R as parseInteger, t as defineMetabaseCommand } from "./runtime-DiKyBxOw.mjs";
+import { V as outputFlags, h as writeText, m as writeJson } from "./cli.mjs";
+import { K as parseInteger, t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
 import { z } from "zod";
 import { randomUUID } from "node:crypto";
 //#region src/commands/uuid.ts
@@ -17,6 +17,7 @@ var uuid_default = defineMetabaseCommand({
 		purpose: "where lib/uuid values are used"
 	}],
 	capabilities: null,
+	worktree: "any",
 	args: {
 		...outputFlags,
 		count: {

package/dist/{validate-query-DaGYSmpQ.mjs → validate-query-Chc43ezW.mjs}

@@ -1,5 +1,5 @@
 import { i as ConfigError } from "./predicates-Bkm2IoeX.mjs";
-import { l as writeJson } from "./cli.mjs";
+import { m as writeJson } from "./cli.mjs";
 import { i as validateQuery, r as isMbql5Query, t as assertNotLegacyEnvelopeWrappingMbql5 } from "./validate-BWchyW0V.mjs";
 //#region src/commands/validate-query.ts
 const skipValidateFlag = { "skip-validate": {

package/dist/{values-Dxf1JEoA.mjs → values-BL_U-Zdw.mjs}

@@ -1,6 +1,6 @@
-import { F as outputFlags, I as profileFlag, M as connectionFlags, c as renderSummary, f as formatScalar } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-DiKyBxOw.mjs";
-import { t as parseId } from "./parse-id-C_jmKFaa.mjs";
+import { H as profileFlag, R as connectionFlags, V as outputFlags, _ as formatScalar, p as renderSummary } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
+import { t as parseId } from "./parse-id-DDCn3VXx.mjs";
 import { s as FieldValues } from "./field-Cr2DPUG9.mjs";
 import { n as fieldValuesView } from "./field-BPsNa-TO.mjs";
 //#region src/commands/field/values.ts
@@ -10,6 +10,7 @@ var values_default = defineMetabaseCommand({
 		description: "Fetch the cached distinct values for a field (FieldValues list)"
 	},
 	capabilities: { minVersion: 58 },
+	worktree: "any",
 	args: {
 		...outputFlags,
 		...profileFlag,

package/dist/{verify-K96rItG5.mjs → verify-DnBaRmkI.mjs}

@@ -1,7 +1,7 @@
-import { n as createClient } from "./client-BqhzKdLM.mjs";
+import { n as createClient } from "./client-DYD8WZYy.mjs";
 import { f as errorMessage, l as TimeoutError, o as MetabaseError, s as NetworkError } from "./predicates-Bkm2IoeX.mjs";
-import { F as tryParseTag, I as SessionProperties, u as USER_AGENT } from "./runtime-DiKyBxOw.mjs";
-import { r as HttpError } from "./network-error-CEb9ymDW.mjs";
+import { U as tryParseTag, W as SessionProperties, g as USER_AGENT } from "./runtime-CNAZ_FuR.mjs";
+import { r as HttpError } from "./network-error-D6CiOEBw.mjs";
 //#region ../client/src/version/probe.ts
 const PROBE_PATH = "/api/session/properties";
 const PROBE_TIMEOUT_MS = 1e4;

package/dist/{wait-flags-DWEF9tX4.mjs → wait-flags-DzytMEG8.mjs}

@@ -1,5 +1,5 @@
-import { t as interruptSignal } from "./cli.mjs";
-import { t as parseId } from "./parse-id-C_jmKFaa.mjs";
+import { n as interruptSignal } from "./cli.mjs";
+import { t as parseId } from "./parse-id-DDCn3VXx.mjs";
 import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-75SvT7Zv.mjs";
 //#region src/commands/wait-flags.ts
 const waitScheduleFlags = {

package/dist/{wait-DoMDH226.mjs → wait-mPoOZxrw.mjs}

@@ -1,9 +1,9 @@
-import { F as outputFlags, I as profileFlag, M as connectionFlags, c as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-DiKyBxOw.mjs";
+import { H as profileFlag, R as connectionFlags, U as worktreeFlag, V as outputFlags, p as renderSummary } from "./cli.mjs";
+import { r as WORKTREE_SCOPE_DETAIL, s as scopeQuery, t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
 import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-75SvT7Zv.mjs";
-import { r as parseWaitSchedule } from "./wait-flags-DWEF9tX4.mjs";
-import { c as syncTaskView } from "./git-sync-DxD_ng48.mjs";
-import { a as throwIfFailedTask, i as taskPollOptions, n as formatSyncTask, r as syncTaskIdleView, t as SyncTaskOrIdle } from "./sync-task-BACcrs0i.mjs";
+import { r as parseWaitSchedule } from "./wait-flags-DzytMEG8.mjs";
+import { l as syncTaskView } from "./git-sync-LQIVMNxO.mjs";
+import { a as throwIfFailedTask, i as taskPollOptions, n as formatSyncTask, r as syncTaskIdleView, t as SyncTaskOrIdle } from "./sync-task-G1K47Nvn.mjs";
 //#region src/commands/git-sync/wait.ts
 const WaitResult = SyncTaskOrIdle;
 var wait_default = defineMetabaseCommand({
@@ -15,10 +15,13 @@ var wait_default = defineMetabaseCommand({
 		minVersion: 60,
 		tokenFeature: "remote_sync"
 	},
+	worktree: "scoped",
+	details: WORKTREE_SCOPE_DETAIL,
 	args: {
 		...outputFlags,
 		...profileFlag,
 		...connectionFlags,
+		...worktreeFlag,
 		timeout: {
 			type: "string",
 			description: "Polling timeout in ms",
@@ -32,9 +35,11 @@ var wait_default = defineMetabaseCommand({
 	},
 	outputSchema: WaitResult,
 	examples: ["mb git-sync wait", "mb git-sync wait --timeout 300000 --json"],
-	async run({ args, ctx, getClient }) {
+	async run({ args, ctx, getClient, getWorktree }) {
 		const schedule = parseWaitSchedule(args);
-		const final = await (await getClient()).gitSync.waitForTask(taskPollOptions(schedule));
+		const mb = await getClient();
+		const scope = await getWorktree();
+		const final = await mb.gitSync.waitForTask(taskPollOptions(schedule), scopeQuery(scope));
 		if (final === null) {
 			renderSummary({ status: "idle" }, syncTaskIdleView, "No git-sync task is running.", ctx);
 			return;

package/dist/{window-BkvrP0gB.mjs → window-DSb1tqSe.mjs}

@@ -1,4 +1,4 @@
-import { m as projectForList } from "./cli.mjs";
+import { y as projectForList } from "./cli.mjs";
 //#region src/output/window.ts
 const MAX_REQUEST_PAGE_SIZE = 200;
 function windowList(items, range, serverTotal) {

package/dist/worktree-ChdDlG3Q.mjs

@@ -0,0 +1,25 @@
+import { n as WorktreeCompact } from "./worktree-xAro1xAB.mjs";
+//#region src/output/views/worktree.ts
+const worktreeView = {
+	compactPick: WorktreeCompact,
+	tableColumns: [
+		{
+			key: "id",
+			label: "ID"
+		},
+		{
+			key: "branch",
+			label: "Branch"
+		},
+		{
+			key: "creator_id",
+			label: "Creator"
+		},
+		{
+			key: "created_at",
+			label: "Created"
+		}
+	]
+};
+//#endregion
+export { worktreeView as t };

package/dist/worktree-DC0kTxxQ.mjs

@@ -0,0 +1,20 @@
+import { t as defineCommandGroup } from "./group-YN6jj2AN.mjs";
+//#region src/commands/worktree/index.ts
+var worktree_default = defineCommandGroup({
+	name: "worktree",
+	description: "Manage git-sync worktrees: isolated checkouts of a branch's content",
+	skills: [{
+		skill: "git-sync",
+		purpose: "worktree lifecycle and pull/push"
+	}],
+	subCommands: {
+		list: () => import("./list-CbbKip6U.mjs").then((mod) => mod.default),
+		get: () => import("./get-mGEv-kag.mjs").then((mod) => mod.default),
+		create: () => import("./create-DwrhcI8r2.mjs").then((mod) => mod.default),
+		delete: () => import("./delete-D_OgiI4v.mjs").then((mod) => mod.default),
+		pin: () => import("./pin-BuZ_kg-u.mjs").then((mod) => mod.default),
+		unpin: () => import("./unpin-DxbXmLtW.mjs").then((mod) => mod.default)
+	}
+});
+//#endregion
+export { worktree_default as default };

package/dist/worktree-xAro1xAB.mjs

@@ -0,0 +1,24 @@
+import { z } from "zod";
+//#region ../client/src/domain/worktree.ts
+const WorktreeCreator = z.object({
+	id: z.number().int().positive(),
+	email: z.email().optional(),
+	common_name: z.string().optional()
+}).loose();
+const Worktree = z.object({
+	id: z.number().int().positive(),
+	branch: z.string(),
+	creator_id: z.number().int().positive().nullable().optional(),
+	created_at: z.string().optional(),
+	updated_at: z.string().optional(),
+	creator: WorktreeCreator.nullable().optional()
+}).loose();
+const WorktreeCompact = Worktree.pick({
+	id: true,
+	branch: true,
+	creator_id: true,
+	created_at: true
+}).strip();
+z.object({ branch: z.string().min(1) });
+//#endregion
+export { WorktreeCompact as n, Worktree as t };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metabase/cli",
-  "version": "0.3.0",
+  "version": "0.3.1-alpha.support-worktrees.b634907",
   "description": "Metabase CLI",
   "license": "AGPL-3.0",
   "repository": {

package/skill-data/core/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: core
-description: Foundations for driving Metabase from the terminal with the `mb` CLI — authentication and named profiles, the flag/output/`--json` conventions every command shares, JSON body input, command discovery via `--help` (add `--json` for machine-readable schemas), and the per-resource footguns (db, table, field, upload, card, dashboard, collection, segment, measure, timeline, alert, subscription, library, setting, search, eid). Load first for any `mb` task; it routes to the specialized skills for deeper work.
+description: Foundations for driving Metabase from the terminal with the `mb` CLI — authentication and named profiles, the flag/output/`--json` conventions every command shares, JSON body input, command discovery via `--help` (add `--json` for machine-readable schemas), and the per-resource footguns (db, table, field, upload, content translation, card, dashboard, collection, segment, measure, timeline, alert, subscription, library, setting, search, eid). Load first for any `mb` task; it routes to the specialized skills for deeper work.
 allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
 ---
 
@@ -11,9 +11,9 @@ The official Metabase CLI (`mb`) drives a Metabase instance over its REST API: a
 Top-level command groups (run `mb <group> --help` to discover verbs):
 
 ```
-auth | db | table | field | upload | query | card | dashboard | snippet | segment | measure | collection | library
+auth | db | table | field | upload | content-translation | query | card | dashboard | snippet | segment | measure | collection | library
 document | timeline | timeline-event | transform | transform-job | transform-tag | alert | subscription | setting
-search | git-sync | setup | eid | uuid | upgrade | skills
+search | git-sync | worktree | setup | eid | uuid | upgrade | skills
 ```
 
 The conventions below — auth, flags, output, body input — hold across **every** group. Per-command flags and examples live in each command's `--help`; add `--json` for the machine-readable form with the output JSON Schema. A few flows have their own skills (see "Specialized skills"). When a card needs a query, prefer MBQL over native SQL (portable, pre-flight-validated — load `mbql`); fall back to native SQL when MBQL can't express it.
@@ -47,6 +47,8 @@ Once a name is established, pass `--profile <name>` to **every** subsequent comm
 
 **`--wait` for async operations.** `transform run`, `git-sync import`, and similar verbs return immediately by default. Pass `--wait` whenever the next step depends on completion — without it you race the operation and see "not ready" / transient connection refusals.
 
+**`--worktree <id|branch>` scopes a command to a git-sync worktree** — an isolated checkout of one branch's content in the same instance (admin-only, v64+). Precedence: flag, then `MB_WORKTREE`, then the profile's pin (`mb worktree pin <ref>` / `unpin`). **The pin is a lock, not a default:** flag and env may only re-state it, a different worktree exits 2 — that is how a harness confines an agent to one worktree. Each command's `worktree` policy shows in `--help --json`: `scoped` honors the scope, `any` ignores it and takes no `--worktree`, `main-only` (`transform run`, main-app writes) refuses under one — report that refusal rather than unpinning. Workflow: the `git-sync` skill.
+
 **Some "lookup" verbs return JSON envelopes, not bare values.** `mb setting get <key>` returns `{"key": "...", "value": ...}`. Extract before reusing:
 
 ```bash
@@ -69,7 +71,7 @@ Every list verb takes `--limit <n>` (items this call returns) and `--offset <n>`
 
 - **`has_more` decides whether to keep going — never compare counts.** `total` is the server's count on endpoints that report one and `null` on those that don't, so arithmetic over it is not a termination condition.
 - **To continue, pass `next_offset` back as `--offset`.** When `has_more` is true `next_offset` is past the offset you sent, so the loop advances; when false the walk is over and `next_offset` is `null`.
-- **`truncated` means the byte cap cut the output, not that the data ran out.** `has_more`/`next_offset` are recomputed to the cut point, so a capped list resumes like any window. Its `bytes` is what the untruncated answer would have measured, so it sizes the work left rather than the reply you hold. Narrow rows with `--fields` rather than raising `--max-bytes` — a bigger cap spends context on fields you didn't ask for, and the cap counts only what you asked for, so `--fields` buys rows directly. A capped list always returns at least one row; when not even one fits it exits 2 with "the smallest response this list can produce is N bytes, over the M-byte --max-bytes cap; …".
+- **`truncated` means the byte cap cut the output, not that the data ran out.** `has_more`/`next_offset` are recomputed to the cut point, so a capped list resumes like any window. Its `bytes` is what the untruncated answer would have measured, so it sizes the work left rather than the reply you hold. Narrow rows with `--fields` rather than raising `--max-bytes` — the cap counts only what you asked for, so `--fields` buys rows directly. A capped list always returns at least one row; when not even one fits it exits 2 with "the smallest response this list can produce is N bytes, over the M-byte --max-bytes cap; …".
 - `limit` is echoed only when you passed `--limit` — except `mb search`, which defaults to `--limit 20` (an unbounded search is expensive server-side) and so always reports one. On nouns the server doesn't page, one large `--limit` with narrow `--fields` is a single request; many small `--offset` hops are one request each.
 
 The whole walk, literally:
@@ -104,7 +106,7 @@ mb <noun> create --file ./.scratch/body.json --profile <n> --json
 
 Single-quoted `'EOF'` stops the shell interpolating `$vars` inside the JSON.
 
-Write working files to **`./.scratch`** in the current directory (`mkdir -p ./.scratch` first), never `/tmp` — better permissions, they persist across the session, and the user can review them.
+Write working files to **`./.scratch`** in the current directory (`mkdir -p ./.scratch` first), never `/tmp` — they persist across the session and the user can review them.
 
 ## Discovering commands and schemas
 
@@ -123,26 +125,27 @@ mb transform --help --json | jq -r '.commands[].command'  # verbs under "transfo
 
 ## Resource quirks worth memorizing
 
-Routine verb shapes (list / get / create / update), every flag, and output schemas live in each command's `--help` (add `--json` for output schemas). Below is only what help does _not_ tell you: footguns and non-obvious behaviors.
+Routine verb shapes (list / get / create / update), every flag, and output schemas live in each command's `--help` (add `--json`). Below is only what help does _not_ tell you: footguns and non-obvious behaviors.
 
-- **db traversal: the hydration ladder.** Start with `database get <db-id> --include tables` — the compact table map (id, name, schema, description per table), one call that fits most databases. Pick the relevant tables, then `table fields <table-id>` per table (bounded: fields are per-table). `--include tables.fields` is the full rollup — small databases only. Hundreds of tables? Traverse by schema (`database schemas <db-id>` → `database schema-tables <db-id> <schema>`) or look tables up by name (`search <term> --models table --db-id <db-id> --limit 10`). `sync-schema` / `rescan-values` queue async work and return `{status:"ok"}` immediately; `sync-schema --wait` blocks until `initial_sync_status: complete`.
-- **table fields.** `table get` never returns fields on its own — pass `--include fields` (compact; the underlying query_metadata response also carries FK targets and dimensions, visible under `--full`) or use `table fields <id>` (list envelope). `table update` patches table-level metadata only; physical columns aren't editable.
+- **db traversal: the hydration ladder.** Start with `database get <db-id> --include tables` — the compact table map (id, name, schema, description per table), one call that fits most databases. Then `table fields <table-id>` per relevant table (bounded: fields are per-table). `--include tables.fields` is the full rollup — small databases only. Hundreds of tables? Traverse by schema (`database schemas <db-id>` → `database schema-tables <db-id> <schema>`) or look tables up by name (`search <term> --models table --db-id <db-id> --limit 10`). `sync-schema` / `rescan-values` queue async work and return `{status:"ok"}` immediately; `sync-schema --wait` blocks until `initial_sync_status: complete`.
+- **table fields.** `table get` never returns fields on its own — pass `--include fields` (compact; `--full` also carries FK targets and dimensions) or use `table fields <id>` (list envelope). `table update` patches table-level metadata only; physical columns aren't editable.
 - **field has no `list`.** Fields are per-table — get them via `table get <id> --include fields`. Never enumerate fields across a whole db (context blow-up). `field summary` is live cardinality `{field_id, count, distincts}`; `field values` is the cached distinct set (`has_more_values: true` ⇒ truncated cache). `field update` patches metadata only (`base_type` isn't editable) — this is where you set a column's `semantic_type` or foreign-key target.
 - **upload (CSV → tables).** `upload csv --file <path>` creates a new table + model (prints `{model_id, table_id}`); `upload append <table-id>` / `upload replace <table-id> --file <path>` add to / overwrite a table **previously created by upload** (columns must match). The destination db+schema is admin-configured, not per-call — check with `mb setting get uploads-settings --json` (`db_id: null` ⇒ uploads off/unconfigured; needs admin to read). `--collection <id|root>` only sets the model's collection. Max 50 MB. Errors: **"The uploads database is not configured."** = no db has uploads enabled; **"Uploads are not enabled."** = the append/replace target isn't an uploaded table.
+- **content-translation.** EE-only (`content_translation` premium feature), admin-only, separate from Remote Sync. `content-translation download > translations.csv` streams the complete active dictionary; `content-translation upload --file translations.csv` replaces every active translation with the file. Always upload the canonical complete CSV, never a partial patch. An empty dictionary downloads as Metabase's four-row sample — don't re-upload it as real translations. Dictionaries are limited to 1.5 MiB.
 - **card.** `dataset_query` is the **flat** `mbql/query` value, not a legacy `{type:"query",query:…}` envelope (→ `mbql`). `--export-format csv|xlsx` streams the raw export (pipe to a file), bypassing the JSON envelope. `archive` is the only delete; unarchive with `update --body '{"archived":false}'`. `visualization_settings` keys are scoped by `display` and aren't pre-flighted — see `visualization`.
-- **dashboard.** Dashcards round-trip through `PUT /api/dashboard/:id` (no per-dashcard endpoint): `update-dashcard <dash-id> <dashcard-id>` patches one safely; `update --body '{"dashcards":[…]}'` replaces the whole set (omitted ids are deleted server-side; negative ids for new cards). `create` accepts the **same** `dashcards` array in its initial body — lay out the whole dashboard in one call: negative ids for new cards, and `card_id:null` plus a `visualization_settings.virtual_card` block (`{display:"text"|"heading"|"link"|…}`) for non-question cards. `create`/`update` pre-flight every positive `card_id` and exit **2** with `{ok:false,errors:[…]}` on a bad ref (non-bypassable). `dashboard get <id>` (or `--full`) hydrates dashcards/tabs; `list` omits them. **The grid is 24 columns wide:** each dashcard's `{col, row, size_x, size_y}` is in grid units — **full-width is `size_x: 24`** (`size_x: 12` is half a row, the usual cause of a card filling only half the width). Keep `col + size_x ≤ 24`, start a full-width stack's `col` at 0, and don't overlap (the server stores collisions as sent — no auto-fix). Layout patterns and per-chart default sizes → the `dashboard` skill; load it before composing any `dashcards` array.
-- **dashboard parameters (filters).** A dashboard's `parameters` array holds its filter widgets; they're part of the dashboard record, so read them with `dashboard get <id> --fields parameters --json` (no separate verb). **Editing replaces the _whole_ array** (like dashcards), so it's a read-modify-write loop and omitting a parameter deletes it. A parameter only filters a card once it is **mapped** onto that dashcard's `parameter_mappings` — an unmapped parameter is an inert widget. `type` is a **closed enum**; an unlisted value is a hard parse error that echoes the full allowed set back to you. `dashboard parameter-values <id> <parameter-id> [--query <substr>]` fetches a widget's selectable values (`{values, has_more_values}`; `--query` is a case-insensitive substring search). Parameter types, ids, mapping targets, and value sources → the `dashboard` skill; load it before authoring a `parameters` array.
+- **dashboard.** Dashcards round-trip through `PUT /api/dashboard/:id` (no per-dashcard endpoint): `update-dashcard <dash-id> <dashcard-id>` patches one safely; `update --body '{"dashcards":[…]}'` replaces the whole set (omitted ids are deleted server-side; negative ids for new cards). Every dashcard must include `card_id`, including existing rows; use `card_id:null` plus a `visualization_settings.virtual_card` block (`{display:"text"|"heading"|"link"|…}`) for non-question cards. `create` accepts the **same** `dashcards` array in its initial body, so lay out the whole dashboard in one call. `create`/`update` pre-flight every positive `card_id` and exit **2** with `{ok:false,errors:[…]}` on a bad ref (non-bypassable). `dashboard get <id>` (or `--full`) hydrates dashcards/tabs; `list` omits them. **The grid is 24 columns wide:** each dashcard's `{col, row, size_x, size_y}` is in grid units — **full-width is `size_x: 24`** (`size_x: 12` is half a row, the usual cause of a half-width card). Keep `col + size_x ≤ 24`, start a full-width stack's `col` at 0, and don't overlap (the server stores collisions as sent — no auto-fix). Layout patterns and per-chart default sizes → the `dashboard` skill; load it before composing any `dashcards` array.
+- **dashboard parameters (filters).** A dashboard's `parameters` array holds its filter widgets; they're part of the dashboard record, so read them with `dashboard get <id> --fields parameters --json` (no separate verb). **Editing replaces the _whole_ array** (like dashcards), so it's a read-modify-write loop and omitting a parameter deletes it. A parameter only filters a card once it is **mapped** onto that dashcard's `parameter_mappings` — an unmapped parameter is an inert widget. `type` is a **closed enum**; an unlisted value is a hard parse error that echoes the allowed set back. `dashboard parameter-values <id> <parameter-id> [--query <substr>]` fetches a widget's selectable values (`{values, has_more_values}`; `--query` is a case-insensitive substring match). Parameter types, ids, mapping targets, and value sources → the `dashboard` skill; load it before authoring a `parameters` array.
 - **alert / subscription are two unrelated systems.** `alert` watches one **card** and fires on a send condition (`/api/notification`: a cron string, `channel/email`-prefixed handlers, typed recipients); `subscription` delivers one **dashboard** on a schedule (`/api/pulse`: structured `schedule_type` + hour/day/frame, bare `email` channels, `{id}|{email}` recipients). The bodies are not interchangeable. Both silently deliver nowhere if the server has no SMTP / Slack app — check `mb setting get 'email-configured?'` (quote it; the `?` is a shell glob) before creating either. Their list-valued fields (`handlers`/`subscriptions`, `channels`/`cards`) **replace wholesale** on update, so adding one recipient is a read-modify-write. `mb card alerts <id>` and `mb dashboard subscriptions <id>` list what's already attached to a card/dashboard; `archive` deactivates rather than deletes. Load the `notification` skill before authoring either body.
 - **snippet `--archived` is a swap, not a union** — list returns _either_ active _or_ archived rows, never both. (Same for `--filter archived` on dashboard/collection.)
 - **segment / measure.** `update` and `archive` require a non-blank `revision_message` (audit-logged); the CLI does not synthesize it on `update`. `archive` defaults to `"Archived via mb CLI"` — override with `--revision-message`. `definition` is a flat MBQL clause (→ `mbql`): segment = a filter, measure = exactly one aggregation.
-- **timeline / timeline-event.** Timelines are collection-scoped event annotations for time-series charts: a timeline's events render only on time-series questions saved in the **same collection** (`collection_id`; null = root) — sub-collections do **not** inherit, and events never draw on dashboard cards, only in the question (and collection) view. To annotate a question's chart, create the timeline in that question's collection, then add events; an event only draws when its `timestamp` falls inside the chart's displayed time range. Event `create` requires `timestamp` (ISO 8601), `timezone` (IANA name), `time_matters` (true = the time of day is significant, false = date-only), and `timeline_id` — the API never auto-creates a default timeline (that's UI-only). There is no `timeline-event list`; enumerate with `timeline events <id>` (`--archived` to include archived). Archiving a timeline cascades `archived` to its events; `delete` is a **hard** delete of the timeline and all its events — prefer `archive`.
+- **timeline / timeline-event.** Timelines are collection-scoped event annotations for time-series charts: a timeline's events render only on time-series questions saved in the **same collection** (`collection_id`; null = root) — sub-collections do **not** inherit, and events never draw on dashboard cards, only in the question (and collection) view. An event draws only when its `timestamp` falls inside the chart's displayed time range. Event `create` requires `timestamp` (ISO 8601), `timezone` (IANA name), `time_matters` (true = the time of day is significant, false = date-only), and `timeline_id` — the API never auto-creates a default timeline (that's UI-only). There is no `timeline-event list`; enumerate with `timeline events <id>` (`--archived` to include archived). Archiving a timeline cascades `archived` to its events; `delete` is a **hard** delete of the timeline and all its events — prefer `archive`.
 - **collection `<ref>`** accepts four forms only — positive int, `root`, `trash`, or a 21-char entity_id; anything else is a client-side `ConfigError`. `collection items` pages the server endpoint, pulling only as far as the output cap can show — read `has_more`/`next_offset` to continue. `collection tree` is **JSON-only** (`--format text` is rejected). A transform collection needs `collection create --namespace transforms`.
 - **setting set** parses the value as **strict JSON**: a string is `'"value"'` (inner quotes), booleans `true`/`false`, numbers bare. Wrong quoting silently errors — confirm with `setting get <key>` after. `setting get --json` works on every value type (wrapping bare-text responses into `{key, value}`).
 - **search vs. list.** For plain enumeration of cards/dashboards/collections use the dedicated `… list` verbs; reach for `search --models <kind>` only for ranking against a query string or a cross-resource lookup.
 - **transform.** Iterate with `transform update <id>`, never `delete` + `create` (keeps the row, `entity_id`, materialized table, and YAML filename — avoids `_2` suffixes and noisy git history). `transform run` needs `--wait` (or `--sync`, which also waits for the output table to register and returns `target_table_id`) or you get only `{run_id, final:null}`. (→ `transform`.)
 - **setup is one-shot.** `mb setup` walks `/api/setup` for a **fresh** instance only — errors against an already-configured one. Mostly for bootstrapping local / e2e instances.
 - **eid** translates a string entity id → numeric id: `mb eid --model <model> <eid1,eid2> --json`. Entity ids are NanoIDs that can start with `-`, which the positional form misreads as a flag (shell quotes don't help) — for those, use `--body '{"entity_ids":{"card":["-…"]}}'` (the id is a JSON string value, immune to flag parsing).
-- **library.** EE-only (`library` premium feature, v59+). The Library is a curated subtree (`library-data` "Data" + `library-metrics` "Metrics" under a `library` root): tables published to **Data** appear first in data pickers and rank up in search; metrics saved to **Metrics** are prioritized in nav, search, and the query builder — it's how you tell people (and agents) "start from these, they're trusted." `library get` shows the Library and its Data/Metrics collection ids; `library create` provisions it (idempotent). `library publish --table-ids/--db-ids/--schemas` publishes tables into Data — it **resolves the Data collection itself and creates the Library if absent** (no collection id to find); each `--schemas` entry is `<db-id>:<schema>` (e.g. `1:public`), not a bare name. `publish` cascades to upstream FK dependencies, `unpublish` to downstream dependents; both need **admin or data-analyst** (Curate alone won't publish) and exit **403** without write **and** query permission on every affected table. Publish status shows on the table: `table get`/`table list` carry `is_published` (`collection_id` under `--full`). Good candidates are finished, analysis-ready tables — clean/combine via transforms first, then publish the polished result. Publishing does not put the Data collection in the git-sync scope: on a remote-sync instance, `mb git-sync add-collection <data-collection-id>` is what makes exports carry the published tables' metadata (see the `git-sync` skill).
+- **library.** EE-only (`library` premium feature, v59+). The Library is a curated subtree (`library-data` "Data" + `library-metrics` "Metrics" under a `library` root): tables published to **Data** appear first in data pickers and rank up in search; metrics saved to **Metrics** are prioritized in nav, search, and the query builder — it's how you tell people (and agents) which to start from. `library get` shows the Library and its Data/Metrics collection ids; `library create` provisions it (idempotent). `library publish --table-ids/--db-ids/--schemas` publishes tables into Data — it **resolves the Data collection itself and creates the Library if absent**; each `--schemas` entry is `<db-id>:<schema>` (e.g. `1:public`), not a bare name. `publish` cascades to upstream FK dependencies, `unpublish` to downstream dependents; both need **admin or data-analyst** (Curate alone won't publish) and exit **403** without write **and** query permission on every affected table. `table get`/`table list` carry `is_published` (`collection_id` under `--full`). Good candidates are finished, analysis-ready tables — clean up via transforms first. Publishing does not put the Data collection in the git-sync scope: `mb git-sync add-collection <data-collection-id>` is what makes exports carry the published tables' metadata (see the `git-sync` skill).
 - **query / uuid.** `mb query` is the ad-hoc MBQL surface (`--print-schema` → `--dry-run` → run); `mb uuid --count <n>` mints the `lib/uuid` values MBQL clauses need. Both live in `mbql`.
 
 ## Specialized skills (load on demand)
@@ -157,8 +160,8 @@ This file is enough for any single-command task. For anything deeper, load the r
 - **`notification`** — scheduled delivery: question alerts (`mb alert`) and dashboard subscriptions (`mb subscription`). Choosing between them, the two schedule/recipient contracts, channel prerequisites, testing a send.
 - **`transform`** — transform body JSON, create + run-with-wait, run inspection, tags, jobs.
 - **`document`** — Metabase documents (TipTap body, embedding cards).
-- **`git-sync`** — round-tripping content to/from a git remote.
-- **`data-workflow`** — the guided, end-to-end data workflow: investigate raw data, build clean analysis-ready tables, define reusable segments/measures/metrics, answer questions, build dashboards. **Start here when the user states a goal rather than a single verb** — "make sense of my data", "build a data model", "go from raw data to a dashboard", "be my data analyst", "set up analytics for X". It detects where the data is and routes to the right stage.
+- **`git-sync`** — round-tripping content to/from a git remote, and worktrees.
+- **`data-workflow`** — the guided, end-to-end data workflow: investigate raw data, build clean analysis-ready tables, define reusable segments/measures/metrics, answer questions, build dashboards. **Start here when the user states a goal rather than a single verb** — "make sense of my data", "build a data model", "go from raw data to a dashboard", "set up analytics for X". It detects where the data is and routes to the right stage.
 
 If a task spans more than one, load each. `mb skills list` enumerates everything on the installed version.
 

package/skill-data/dashboard/SKILL.md

@@ -8,7 +8,7 @@ allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
 
 A dashboard starts as cards on a grid; it becomes an **app** when filters drive the cards, charts cross-filter each other, and clicks navigate. This skill owns both: the grid layout and the interactive layer.
 
-**`core` owns the transport mechanics** — the whole-array replace semantics (editing `dashcards` or `parameters` replaces the entire set; omitted entries are deleted; new cards use negative ids), `update-dashcard` for a single safe patch vs. `update --body` for a full replace, and the `parameter-values` verb. Read it first (`mb skills get core`). **`visualization`** owns each card's chart and the full `click_behavior` key catalog.
+**`core` owns the transport mechanics** — the whole-array replace semantics (editing `dashcards` or `parameters` replaces the entire set; omitted entries are deleted; every dashcard carries `card_id`, with `null` for virtual cards; new cards use negative ids), `update-dashcard` for a single safe patch vs. `update --body` for a full replace, and the `parameter-values` verb. Read it first (`mb skills get core`). **`visualization`** owns each card's chart and the full `click_behavior` key catalog.
 
 Inspect before you wire: `mb dashboard get <id> --json` hydrates `parameters`, `dashcards`, and `tabs`; `mb dashboard cards <id>` lists just the dashcards.
 
@@ -123,7 +123,7 @@ Set the **driver** chart's whole-card click behavior to `crossfilter`, mapping t
 - **Auto-connect / the missing map:** a filter that "does nothing" or "won't show" is almost always unmapped, or mapped only to cards on another tab.
 - **Time-grouping parameters** (`temporal-unit`) bind only to a datetime column in the query's **last** stage — add one after a time-bucketed summary and it can't attach.
 - **Required + default:** a `required: true` parameter with no `default` blocks its cards until a value is chosen; give it a `default` for expensive queries you don't want running unfiltered.
-- **Whole-array replace:** never send a partial `parameters`/`dashcards` array to `update` — you'll delete what you omit. Use `update-dashcard` for a single-card change.
+- **Whole-array replace:** never send a partial `parameters`/`dashcards` array to `update` — you'll delete what you omit. Include `card_id` on every dashcard (`null` for virtual cards). Use `update-dashcard` for a single-card change.
 
 ## Don't