@metabase/cli 0.4.1-alpha.release-65-integration-branch.5cbe297 → 0.5.1

package/dist/{update-Cv6IMLyu.mjs → update-DROjGe3Q.mjs}

@@ -1,7 +1,7 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
-import { t as readBody } from "./body-BVrHLwJU.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
+import { t as readBody } from "./body-BkkQkGJg.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { i as TransformTagUpdateInput, t as TransformTag } from "./transform-tag-CcElGp3C.mjs";
 import { t as transformTagView } from "./transform-tag-Dmb4u3-Q.mjs";

package/dist/{update-Bdi40RG0.mjs → update-DZHgr6Gu.mjs}

@@ -1,10 +1,10 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
-import { t as readBody } from "./body-BVrHLwJU.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
+import { t as readBody } from "./body-BkkQkGJg.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { o as DataActionUpdateInput, t as DataAction } from "./data-action-DZxVB_hD.mjs";
-import { n as DATA_ACTION_DATASET_QUERY_LABELS, o as preflightMbql5Query, s as skipValidateFlag } from "./validate-query-DIcK8alR.mjs";
+import { n as DATA_ACTION_DATASET_QUERY_LABELS, o as preflightMbql5Query, s as skipValidateFlag } from "./validate-query-CYUvRvVM.mjs";
 import { n as dataActionView } from "./data-action-R9qxJDPA.mjs";
 //#region src/commands/data-action/update.ts
 var update_default = defineMetabaseCommand({

package/dist/{update-CHA4VWKT.mjs → update-Dk0E66Va.mjs}

@@ -1,11 +1,11 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
-import { t as readBody } from "./body-BVrHLwJU.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
+import { t as readBody } from "./body-BkkQkGJg.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { c as CardUpdateInput, t as Card } from "./card-P5mBknsl.mjs";
 import { n as cardView } from "./card-CQNUT9pm.mjs";
-import { o as preflightMbql5Query, s as skipValidateFlag, t as CARD_DATASET_QUERY_LABELS } from "./validate-query-DIcK8alR.mjs";
+import { o as preflightMbql5Query, s as skipValidateFlag, t as CARD_DATASET_QUERY_LABELS } from "./validate-query-CYUvRvVM.mjs";
 //#region src/commands/card/update.ts
 var update_default = defineMetabaseCommand({
 	meta: {

package/dist/{update-DgmlUn64.mjs → update-DqCZsbLh.mjs}

@@ -1,10 +1,10 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
-import { t as readBody } from "./body-BVrHLwJU.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
+import { t as readBody } from "./body-BkkQkGJg.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
-import { o as TransformJobUpdateInput, t as TransformJob } from "./transform-job-CCguL6LP.mjs";
-import { t as transformJobView } from "./transform-job-AaMZRxAq.mjs";
+import { o as TransformJobUpdateInput, t as TransformJob } from "./transform-job-ClX8e5iO.mjs";
+import { t as transformJobView } from "./transform-job-BBZ5L46v.mjs";
 //#region src/commands/transform-job/update.ts
 var update_default = defineMetabaseCommand({
 	meta: {

package/dist/{update-CEhub3Wz.mjs → update-DrVc25R8.mjs}

@@ -1,10 +1,10 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
-import { t as readBody } from "./body-BVrHLwJU.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
+import { t as readBody } from "./body-BkkQkGJg.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { i as SegmentUpdateInput, t as Segment } from "./segment-OsrbUDzw.mjs";
-import { i as SEGMENT_DEFINITION_LABELS, o as preflightMbql5Query, s as skipValidateFlag } from "./validate-query-DIcK8alR.mjs";
+import { i as SEGMENT_DEFINITION_LABELS, o as preflightMbql5Query, s as skipValidateFlag } from "./validate-query-CYUvRvVM.mjs";
 import { t as segmentView } from "./segment-C_gl5ag6.mjs";
 //#region src/commands/segment/update.ts
 var update_default = defineMetabaseCommand({

package/dist/{update-CYQkWLpZ.mjs → update-Js0IiqCq.mjs}

@@ -1,10 +1,10 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
-import { t as readBody } from "./body-BVrHLwJU.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
+import { t as readBody } from "./body-BkkQkGJg.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
-import { t as Table, y as TableUpdateInput } from "./table-Ci6bhZkb.mjs";
-import { u as tableView } from "./table-BFIOH6Pb.mjs";
+import { t as Table, y as TableUpdateInput } from "./table-zAdW5_3H.mjs";
+import { u as tableView } from "./table-CFZU-BRg.mjs";
 //#region src/commands/table/update.ts
 var update_default = defineMetabaseCommand({
 	meta: {

package/dist/{update-DneJLQXe.mjs → update-dQeji6RA.mjs}

@@ -1,12 +1,12 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
-import { t as readBody } from "./body-BVrHLwJU.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
+import { t as readBody } from "./body-BkkQkGJg.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { f as TransformUpdateInput, t as Transform } from "./transform-DiW7bREn.mjs";
-import { a as TRANSFORM_SOURCE_QUERY_LABELS, o as preflightMbql5Query, s as skipValidateFlag } from "./validate-query-DIcK8alR.mjs";
-import { n as transformView } from "./transform-D4z70PIN.mjs";
-import { t as enrichTransformCollectionError } from "./collection-namespace-Cizv6-94.mjs";
+import { a as TRANSFORM_SOURCE_QUERY_LABELS, o as preflightMbql5Query, s as skipValidateFlag } from "./validate-query-CYUvRvVM.mjs";
+import { n as transformView } from "./transform-CWGJB8N_.mjs";
+import { t as enrichTransformCollectionError } from "./collection-namespace-B1OkM7p1.mjs";
 //#region src/commands/transform/update.ts
 var update_default = defineMetabaseCommand({
 	meta: {

package/dist/{update-dashcard-DNsf-gJ1.mjs → update-dashcard-BmkfJ7t9.mjs}

@@ -1,7 +1,7 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
-import { t as readBody } from "./body-BVrHLwJU.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
+import { t as readBody } from "./body-BkkQkGJg.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { d as DashcardPatchInput, l as Dashcard } from "./dashboard-Phz3XpRM.mjs";
 import { r as dashcardView } from "./dashboard-XSTr9QCr.mjs";

package/dist/{update-CXfLvhmK.mjs → update-nGURR-y6.mjs}

@@ -1,10 +1,10 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
-import { t as readBody } from "./body-BVrHLwJU.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
+import { t as readBody } from "./body-BkkQkGJg.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
-import { a as TransformTestUpdateInput, t as TransformTest } from "./transform-test-BjjCQ2xm.mjs";
-import { n as transformTestView } from "./transform-test-DHGKeuHa.mjs";
+import { a as TransformTestUpdateInput, t as TransformTest } from "./transform-test-Bexa_K89.mjs";
+import { n as transformTestView } from "./transform-test-C49ZTK7M.mjs";
 //#region src/commands/transform-test/update.ts
 var update_default = defineMetabaseCommand({
 	meta: {

package/dist/{upgrade-BRJH93W0.mjs → upgrade-B6V_1cUh.mjs}

@@ -1,7 +1,7 @@
-import { H as version, J as outputFlags, T as promptConfirm, V as name, _ as writeText, ft as TimeoutError, ht as errorMessage, it as AbortError, pt as UnknownError, t as interruptSignal, u as renderItem, ut as NetworkError } from "./cli.mjs";
-import { P as HttpError, R as parseJson, T as USER_AGENT, t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { n as throwIfAborted, t as combineAborts } from "./signal-0Yt8JTMn.mjs";
-import { n as streamProcess } from "./process-B3Di_HtV.mjs";
+import { Ct as NetworkError, Dt as UnknownError, Et as TimeoutError, W as HttpError, Z as parseJson, _ as promptConfirm, a as renderItem, ct as outputFlags, f as writeText, kt as errorMessage, nt as version, t as interruptSignal, tt as name, vt as AbortError } from "./cli.mjs";
+import { T as USER_AGENT, t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { n as throwIfAborted, t as combineAborts } from "./signal-4tpCIkqR.mjs";
+import { n as streamProcess } from "./process-DImdroix.mjs";
 import { z } from "zod";
 import { realpathSync } from "node:fs";
 import { compare, valid } from "semver";

package/dist/{upload-DJB7DMA1.mjs → upload-B6zBzMPW.mjs}

@@ -1,5 +1,5 @@
-import { _t as isFileNotFoundError, ot as ConfigError } from "./cli.mjs";
-import { n as fileNotFoundError } from "./input-DjHsV-kD.mjs";
+import { jt as isFileNotFoundError, yt as ConfigError } from "./cli.mjs";
+import { n as fileNotFoundError } from "./input-AXP2LCOV.mjs";
 import { basename } from "node:path";
 import { readFile } from "node:fs/promises";
 //#region src/runtime/upload.ts

package/dist/{upload-CGz8u2wG.mjs → upload-CfYmBv51.mjs}

@@ -1,7 +1,7 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
 import { t as ContentTranslationUploadResult } from "./content-translation-BrHOrmj9.mjs";
-import { n as requireUploadFilePath, t as readCsvFile } from "./upload-DJB7DMA1.mjs";
+import { n as requireUploadFilePath, t as readCsvFile } from "./upload-B6zBzMPW.mjs";
 //#region src/output/views/content-translation.ts
 const contentTranslationUploadView = {
 	compactPick: ContentTranslationUploadResult,

package/dist/upload-Dvjfz16M.mjs

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

package/dist/{uuid-3qmLYgrG.mjs → uuid-B8ynbkqG.mjs}

@@ -1,5 +1,5 @@
-import { J as outputFlags, _ as writeText, g as writeJson, ot as ConfigError } from "./cli.mjs";
-import { t as defineMetabaseCommand, tt as parseInteger } from "./runtime-X6hVzSMW.mjs";
+import { ct as outputFlags, d as writeJson, f as writeText, yt as ConfigError } from "./cli.mjs";
+import { Q as parseInteger, t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
 import { z } from "zod";
 import { randomUUID } from "node:crypto";
 //#region src/commands/uuid.ts

package/dist/{validate-D_iikPkc.mjs → validate-C7DGkwb-.mjs}

@@ -1,4 +1,4 @@
-import { ot as ConfigError, w as isPlainObject, yt as escapeJsonPointerSegment } from "./cli.mjs";
+import { Pt as escapeJsonPointerSegment, Y as isPlainObject, yt as ConfigError } from "./cli.mjs";
 import { z } from "zod";
 import Ajv2020 from "ajv/dist/2020.js";
 import addFormats from "ajv-formats";

package/dist/{validate-query-DIcK8alR.mjs → validate-query-CYUvRvVM.mjs}

@@ -1,5 +1,5 @@
-import { g as writeJson, ot as ConfigError } from "./cli.mjs";
-import { a as validateQuery, i as isMbql5Query, n as assertNotLegacyEnvelopeWrappingMbql5 } from "./validate-D_iikPkc.mjs";
+import { d as writeJson, yt as ConfigError } from "./cli.mjs";
+import { a as validateQuery, i as isMbql5Query, n as assertNotLegacyEnvelopeWrappingMbql5 } from "./validate-C7DGkwb-.mjs";
 //#region src/commands/validate-query.ts
 const skipValidateFlag = { "skip-validate": {
 	type: "boolean",

package/dist/{values-Bn2Wcz4t.mjs → values-36bzf9cK.mjs}

@@ -1,6 +1,6 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary, y as formatScalar } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, m as formatScalar, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
 import { u as FieldValues } from "./field-5nivEfd6.mjs";
 import { s as fieldValuesView } from "./field-wmN6raOG.mjs";
 //#region src/commands/field/values.ts

package/dist/{verify-CA4PEHlO.mjs → verify-BdW-GExk.mjs}

@@ -1,6 +1,6 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
 import { t as ModerationReview } from "./moderation-review-BdqEH6N1.mjs";
 import { i as moderationReviewView, n as verifyFlags, r as describeReview, t as reviewInput } from "./verify-flags-CMpRkMPa.mjs";
 //#region src/commands/dashboard/verify.ts

package/dist/{verify-C2K-zMuQ.mjs → verify-C4Tml4fD.mjs}

@@ -1,6 +1,6 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
 import { t as ModerationReview } from "./moderation-review-BdqEH6N1.mjs";
 import { i as moderationReviewView, n as verifyFlags, r as describeReview, t as reviewInput } from "./verify-flags-CMpRkMPa.mjs";
 //#region src/commands/card/verify.ts

package/dist/{verify-CCX2N98Q.mjs → verify-Cs9e28YA.mjs}

@@ -1,6 +1,6 @@
-import { n as createClient } from "./client-1UIUBA_V.mjs";
-import { ft as TimeoutError, ht as errorMessage, lt as MetabaseError, ut as NetworkError } from "./cli.mjs";
-import { P as HttpError, Q as probeServer, T as USER_AGENT } from "./runtime-X6hVzSMW.mjs";
+import { n as createClient } from "./client-BBwYPXDW.mjs";
+import { Ct as NetworkError, Et as TimeoutError, St as MetabaseError, W as HttpError, kt as errorMessage } from "./cli.mjs";
+import { I as probeServer, T as USER_AGENT } from "./runtime-Ckns6TKK.mjs";
 //#region src/core/auth/verify.ts
 const VERIFY_TIMEOUT_MS = 15e3;
 async function verifyAndProbe(url, credential, options = {}) {
@@ -35,7 +35,7 @@ function failure(error, which) {
 	if (error instanceof HttpError) return {
 		ok: false,
 		which,
-		kind: error.status === 401 || error.status === 403 ? "auth" : "server",
+		kind: error.kind === "auth" ? "auth" : "server",
 		status: error.status,
 		endpoint: error.developerDetail.url,
 		message: error.userMessage

package/dist/{wait-DCgCJBqX.mjs → wait-BV6JOdgi.mjs}

@@ -1,9 +1,9 @@
-import { J as outputFlags, U as connectionFlags, Y as profileFlag, p as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-X6hVzSMW.mjs";
-import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-DFZRtTA_.mjs";
-import { r as parseWaitSchedule } from "./wait-flags-aRQHTjwg.mjs";
-import { u as syncTaskView } from "./git-sync-DspFahwV.mjs";
-import { a as throwIfFailedTask, i as taskPollOptions, n as formatSyncTask, r as syncTaskIdleView, t as SyncTaskOrIdle } from "./sync-task-BAMOf6_t.mjs";
+import { c as renderSummary, ct as outputFlags, lt as profileFlag, rt as connectionFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-Ckns6TKK.mjs";
+import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-CX3jPtXb.mjs";
+import { r as parseWaitSchedule } from "./wait-flags-DjyK03cm.mjs";
+import { u as syncTaskView } from "./git-sync-Ch1V1fEK.mjs";
+import { a as throwIfFailedTask, i as taskPollOptions, n as formatSyncTask, r as syncTaskIdleView, t as SyncTaskOrIdle } from "./sync-task-DEzhiaU9.mjs";
 //#region src/commands/git-sync/wait.ts
 const WaitResult = SyncTaskOrIdle;
 var wait_default = defineMetabaseCommand({

package/dist/{wait-flags-aRQHTjwg.mjs → wait-flags-DjyK03cm.mjs}

@@ -1,6 +1,6 @@
 import { t as interruptSignal } from "./cli.mjs";
-import { t as parseId } from "./parse-id-CxHp2akh.mjs";
-import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-DFZRtTA_.mjs";
+import { t as parseId } from "./parse-id-Cv5eM7sg.mjs";
+import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-CX3jPtXb.mjs";
 //#region src/commands/wait-flags.ts
 const waitScheduleFlags = {
 	timeout: {

package/dist/{window-2ybHqui2.mjs → window-CfK_j6m1.mjs}

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metabase/cli",
-  "version": "0.4.1-alpha.release-65-integration-branch.5cbe297",
+  "version": "0.5.1",
   "description": "Metabase CLI",
   "license": "AGPL-3.0",
   "repository": {

package/skill-data/core/SKILL.md

@@ -13,7 +13,7 @@ Top-level command groups (run `mb <group> --help` to discover verbs):
 ```
 auth | db | table | field | upload | content-translation | query | card | dashboard | snippet | segment | measure | collection | library
 document | glossary | timeline | timeline-event | transform | transform-job | transform-tag | transform-test | alert | subscription | setting
-search | dependency | git-sync | setup | eid | uuid | upgrade | skills
+search | dependency | git-sync | data-action | 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.
@@ -124,7 +124,7 @@ 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.
+What `--help` doesn't say: 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`). `db sync-schema` / `rescan-values` queue async work and return `{status:"ok"}` at once; `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.
@@ -134,7 +134,7 @@ Routine verb shapes (list / get / create / update), every flag, and output schem
 - **content-translation.** Admin-only, and 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's contents. Always upload the canonical complete CSV, never a partial patch. An empty dictionary downloads as Metabase's four-row sample dictionary — don't re-upload it as real translations. Metabase limits dictionaries to 1.5 MiB.
 <!-- /requires -->
 - **card.** `dataset_query` is the `mbql/query` object itself (→ `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). 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`**. 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.** 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, existing ones included, needs `card_id`; use `card_id:null` plus a `visualization_settings.virtual_card` block (`{display:"text"|"heading"|"link"|…}`) for non-question cards. `create` takes the **same** `dashcards` array, 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`**. Keep `col + size_x ≤ 24`, start a full-width stack's `col` at 0, and don't overlap (the server stores collisions as sent). Load the `dashboard` skill (layout patterns, per-chart default sizes) 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.
 <!-- requires: contentVerification -->
 - **verify.** `card verify <id>` / `dashboard verify <id>` (admins only) mark it verified (rank boost, `search --verified`). `--remove` (or a card query edit) withdraws it; `--text` adds a note; `get <id> --fields moderation_reviews` reads it. Verify only what you checked and the user approved.
@@ -142,8 +142,11 @@ Routine verb shapes (list / get / create / update), every flag, and output schem
 - **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. 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.** A timeline's events draw only on time-series questions saved in the **same collection** (`collection_id`; null = root) — not sub-collections, never on dashboard cards — and only when the event's `timestamp` falls inside the chart's range. Event `create` requires `timestamp` (ISO 8601), `timezone` (IANA name), `time_matters` (false = date-only), and `timeline_id` — no default timeline is auto-created. There is no `timeline-event list`; use `timeline events <id>` (`--archived` to include archived). Archiving a timeline cascades to its events; `delete` is a **hard** delete of both — prefer `archive`.
 - **collection `<ref>`** (`get`/`items`): positive int, `root`, `trash`, or a 21-char entity_id; `update`/`archive` take the int only. `collection items` pages the server, pulling only what the cap can show — read `has_more`/`next_offset` to continue. `collection tree` is **JSON-only** and hides the Library without `--include-library`. A transform collection needs `collection create --namespace transforms`. `update` keeps `archived` unless `--archived` is given.
+<!-- requires: remoteSync -->
+- **remote-synced collections.** Synced content may depend only on synced content: a write that breaks this fails with 400 `Uses content that is not remote synced.` (a source outside sync scope) or `Used by remote synced content.` (archiving or moving out a dependency). Build versioned content inside the synced collection; to move existing content in, see `git-sync`.
+<!-- /requires -->
 - **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.** Enumerate with `… list` verbs; `search` ranks a query or spans resources. `--search-native-query` matches native query text and keeps only query-bearing models; dashboard questions need `--include-dashboard-questions`.
 <!-- requires: transforms -->
@@ -176,7 +179,10 @@ This file is enough for any single-command task. For anything deeper, load the r
 - **`transform-test-plan`** — planning transform tests.
 <!-- /requires -->
 - **`document`** — Metabase documents (TipTap body, embedding cards).
-<!-- requires: remoteSync -->
+<!-- requires: dataActionsWithoutModel -->
+- **`data-action`** — saved SQL writes: enabling, body, parameters, running.
+  <!-- /requires -->
+  <!-- requires: remoteSync -->
 - **`git-sync`** — round-tripping content to/from a git remote.
 <!-- /requires -->
 - **`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", "be my data analyst". It detects where the data is and routes to the right stage.

package/skill-data/dashboard/SKILL.md

@@ -12,6 +12,12 @@ A dashboard starts as cards on a grid; it becomes an **app** when filters drive
 
 Inspect before you wire: `mb dashboard get <id> --json` hydrates `parameters`, `dashcards`, and `tabs`; `mb dashboard cards <id>` lists just the dashcards. To start from an existing dashboard, `mb dashboard copy <id> --collection-id <id> --json` copies it with its tabs and dashcards (the cards stay referenced; `--deep` duplicates the questions and metrics into the target collection, and a dashboard holding dashboard questions needs it). Cards left out of the copy come back by id as `uncopied`.
 
+<!-- requires: remoteSync -->
+
+A dashboard bound for a remote-synced collection is built in it directly: create the dashboard there, then its cards. A card only this dashboard shows is best a **dashboard question** — `card create` with `"dashboard_id": <dash-id>` and the dashboard's `collection_id` — so the dashboard and its questions move as one unit. A card shared across dashboards is a regular card and moves into the synced collection before any dashboard that uses it (`git-sync` → "Moving content into or out of a synced collection").
+
+<!-- /requires -->
+
 ## Layout: the grid is 24 columns — not 12
 
 Every dashcard carries `{col, row, size_x, size_y}` in grid units: `col` is 0-indexed from the left edge, `row` grows downward, and `col + size_x ≤ 24`. **Full-width is `size_x: 24` — Metabase's per-chart _default_ width of 12 is half a row.** A layout authored on the usual 12-column web-grid assumption crams the whole dashboard into the left half of the viewport. The server stores whatever geometry you send — overlaps and gaps included, no auto-fix.

package/skill-data/git-sync/SKILL.md

@@ -15,7 +15,7 @@ This skill covers the import/export workflow. Flag conventions and auth setup li
 
 ## Precondition: read state before mutating
 
-Always run `status` (or `is-dirty` + `has-remote-changes`) before `import` or `export`. Importing on a dirty instance silently rejects unless you pass `--force`.
+Always run `status` (or the individual checks below) before `import` or `export`. Importing on a dirty instance silently rejects unless you pass `--force`.
 
 <!-- requires: remoteSyncMerge -->
 
@@ -26,11 +26,18 @@ Exporting after the remote moved on ends in a `conflict` task unless the export
 ```bash
 mb git-sync status              --profile <n> --json   # → branch, dirty, current task
 mb git-sync is-dirty            --profile <n> --json   # → {is_dirty: bool}; instance has unexported changes
-mb git-sync has-remote-changes  --profile <n> --json   # → {has_changes: bool, remote_version, local_version, cached}; remote has unimported commits
 mb git-sync dirty               --profile <n> --json   # → list the dirty objects
 mb git-sync current-task        --profile <n> --json   # → in-flight task (or idle)
 ```
 
+<!-- requires: remoteSyncRemoteChanges -->
+
+```bash
+mb git-sync has-remote-changes  --profile <n> --json   # → {has_changes: bool, remote_version, local_version, cached}; remote has unimported commits
+```
+
+<!-- /requires -->
+
 **Clean up before exporting.** If you've created entities you intend to delete (a failed transform you're going to retry, a card you authored to test a body shape, a draft dashboard) — do the deletes _before_ the first `git-sync export`. Once committed, the cleanup needs a second commit, and the failed entity stays visible in `git log` forever. For transforms, prefer `transform update <id>` over delete + create (see the `transform` skill).
 
 ## Import (remote → instance)
@@ -53,8 +60,13 @@ Pulls the configured branch and applies it to the instance. Polls until the task
 Workflow:
 
 1. Read state (above) — confirm `is_dirty: false` (or `--force` is intended).
-2. Confirm `has-remote-changes` reports `has_changes: true` — there's actually something to import.
-3. `git-sync import --branch <branch>` — runs to terminal status by default.
+2. `git-sync import --branch <branch>` — runs to terminal status by default.
+
+<!-- requires: remoteSyncRemoteChanges -->
+
+Between the two, confirm `has-remote-changes` reports `has_changes: true` — there's actually something to import.
+
+<!-- /requires -->
 
 <!-- requires: remoteSyncMerge -->
 
@@ -110,17 +122,29 @@ mb git-sync export-preflight --profile <n> --json   # → {has_changes, clean, c
 
 A dry run against the live remote branch, writing nothing. Read it between the state check and the export, and decide from the fields:
 
-| Answer                              | Meaning                                                                                                                                                                     | Move                                                                                                                                                                                                                                                                                                                                                                                                               |
-| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `has_changes: false`                | The remote has not moved past the last sync, or nothing has been synced yet — and then `force_push_casualties` is empty whatever the remote holds.                          | `export -m "..."` applies as-is. Don't read empty casualties on a never-synced instance as leave to `--force`.                                                                                                                                                                                                                                                                                                     |
-| `has_changes: true`, `reason: null` | The remote moved on. `clean` says whether a three-way merge would apply; `conflicts` names the entities changed on both sides; `summary` counts what a merge would fold in. | `clean: true`: `export --merge -m "..."`. `clean: false`: the conflicts need the user's call — `create-branch <name>` then `export -m "..."` pushes Metabase's side to a new branch and leaves the old one untouched, `import --force` takes the remote's side, `export --force` takes Metabase's. A plain `export` ends in a `conflict` task, and so does `stash`: its new branch starts at the moved remote tip. |
-| `reason: "history-rewritten"`       | The remote was force-pushed or rebased, so there is no merge base.                                                                                                          | Only `export --force` can push, and only with the user's explicit go-ahead; `force_push_casualties` is exactly what it would delete or overwrite.                                                                                                                                                                                                                                                                  |
+| Answer                              | Meaning                                                                                                                                                                     | Move                                                                                                                                                                                                                                                                    |
+| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `has_changes: false`                | The remote has not moved past the last sync, or nothing has been synced yet — and then `force_push_casualties` is empty whatever the remote holds.                          | `export -m "..."` applies as-is. Don't read empty casualties on a never-synced instance as leave to `--force`.                                                                                                                                                          |
+| `has_changes: true`, `reason: null` | The remote moved on. `clean` says whether a three-way merge would apply; `conflicts` names the entities changed on both sides; `summary` counts what a merge would fold in. | `clean: true`: `export --merge -m "..."`. `clean: false`: the conflicts need the user's call between the three options under "After a `conflict` task". A plain `export` ends in a `conflict` task, and so does `stash`: its new branch starts at the moved remote tip. |
+| `reason: "history-rewritten"`       | The remote was force-pushed or rebased, so there is no merge base.                                                                                                          | Only `export --force` can push, and only with the user's explicit go-ahead; `force_push_casualties` is exactly what it would delete or overwrite.                                                                                                                       |
+
+`force_push_casualties` is reported on every answer: it is the remote content a force push would discard instead of merging, so read it before ever passing `--force`. It is empty when nothing has been synced yet, yet `export --force` then replaces the remote's managed directories wholesale: check the remote before forcing a first export.
 
-`force_push_casualties` is reported on every answer: it is the remote content a force push would discard instead of merging, so read it before ever passing `--force`. It is empty when nothing has been synced yet, yet `export --force` then replaces the remote's managed directories wholesale: check the remote before forcing a first export. `--branch` defaults to the tracked `remote-sync-branch`; the server rejects any other branch with a 409 naming the current one, so pass it only to assert the branch you believe is tracked.
+Read the preflight before every export: an export that finds the divergence itself ends in `conflict`, and after that these fields can't be trusted (below).
 
 ### After a `conflict` task
 
-A task that ends in `conflict` makes the server count the remote commit it saw as synced. From then on `has-remote-changes` and `export-preflight` report nothing pending, and a retried `export`, `export --merge` or `import --merge` succeeds without bringing the remote's changes into Metabase; a full re-export can then remove them from the remote. So read `export-preflight` before exporting rather than letting an export find the divergence, and never answer a conflict with a retry: take the user's call between `import --force` (the remote's side), `export --force` (Metabase's side) and `create-branch <name>` then `export` (Metabase's side on a new branch).
+Never answer a conflict with a retry. A task that ends in `conflict` may make the server count the remote commit it saw as synced; the server version does not say whether it does. If it does, `has-remote-changes` and `export-preflight` report nothing pending, `force_push_casualties` comes back empty, and a retried `export`, `export --merge` or `import --merge` succeeds without bringing the remote's changes into Metabase; a later full or forced export can then overwrite them on the remote. So don't decide from those reads. Take the user's call between:
+
+- **The remote's side:** `import --force`. Discards Metabase's un-pushed work.
+- **Metabase's side:** `export --force`. Overwrites the remote, and its casualties can't be previewed after a conflict: show the user the remote's commits since the last export in git first.
+- **Both, through a reviewed PR:**
+  1. Note the tracked branch from `mb git-sync status --json` (`branch`): this is `<original>`.
+  2. `mb git-sync create-branch <name>`
+  3. `mb git-sync export -m "..."`
+  4. `mb git-sync import --force`, which reloads the instance from `<name>`.
+  5. Open a PR from `<name>` into `<original>` and review its diff before it merges. If the server counted the conflict as synced, `<name>` starts at the remote's tip, so the PR can undo the remote's edits to the conflicting entities without a git conflict: restore any such edit in the PR.
+  6. Once the PR merges, `mb git-sync import --branch <original>` tracks the original branch again and loads the merged result.
 
 <!-- /requires -->
 
@@ -169,7 +193,7 @@ mb git-sync remove-collection <collection-id> --profile <n> --json
 
 `<collection-id>` is a **positive integer** (the bulk endpoint's schema is `pos-int? → boolean`; nano-id / `root` / `trash` refs are not supported). Get the id from `collection list` (see `core`).
 
-Both verbs return `{ success: true, task_id?: <id> }`. The optional `task_id` only appears when the toggle triggered a follow-up task (e.g., a finalization import after switching to read-only mode); for a normal add/remove in read-write, expect `{ success: true }` and nothing else.
+Both verbs return `{ success: true }`, plus a `task_id` only when the toggle started a follow-up task (e.g. a finalization import after switching to read-only).
 
 **Cascade.** A toggle on a parent cascades to every descendant by `location` prefix — `add-collection 4` flips `4` plus every collection nested under it. `remove-collection 4` is the symmetric inverse. There is no per-leaf-only mode.
 
@@ -183,6 +207,32 @@ mb setting set remote-sync-type '"read-write"' --profile <n>
 
 **Verifying the result.** `mb git-sync status --profile <n> --json` lists the flagged collections under `synced_collections`, and `mb collection get <id> --json` shows the per-collection `is_remote_synced` flag.
 
+## Moving content into or out of a synced collection
+
+When remote sync is configured and the content is meant to be versioned, create it in the synced collection from the start. Nothing reaches git until `git-sync export`, and "Clean up before exporting" covers the drafts.
+
+Synced content may only depend on synced content. Creating a card, dashboard, document, or collection in a synced collection, moving one in, or updating one inside it walks its dependencies, and the server refuses with 400 `Uses content that is not remote synced.` if any of them sits outside sync scope. What counts as a dependency:
+
+- **Card:** the cards it is built on (source model, question, or metric), cards referenced as `{{#id}}` in native SQL, the card behind a filter's value source (`values_source_config.card_id`), and snippets — a snippet counts as synced only when the Library is.
+- **Dashboard:** every dashcard's card, `series` cards, cards in parameter mappings and parameter value sources, actions, and the cards and dashboards a link card points to.
+- Warehouse tables never count: a card on a raw table moves freely.
+
+Three ways through:
+
+1. **Bottom-up.** Move the sources first — models, then metrics, then the questions built on them — and the dashboard last. `card update <id> --body '{"collection_id":<synced-id>}'`, then `dashboard update <id> --body '{"collection_id":<synced-id>}'`.
+2. **The whole containing collection.** `mb collection update <id> --parent-id <synced-id>` checks once, after the whole subtree has moved, so references inside the subtree pass.
+3. **Dashboard questions.** A card created with `dashboard_id` (and the dashboard's `collection_id`) moves with its dashboard in the same transaction, so it never blocks the move.
+
+The reverse holds too: archiving something, or moving it out of sync scope, is refused with 400 `Used by remote synced content.` while synced content still depends on it. The error names the dependents by model and id (`Used by remote synced content: Card 12, Dashboard 3. …`); move or archive those first, or leave the dependency in place.
+
+Reading the inbound refusal: the error lists the blocking content as bare ids with no model type (`Uses content that is not remote synced: ids 412, 77. …`) — these are the dependencies to move first. Most are cards (`mb card get <id>`); otherwise try `mb dashboard get <id>` or `mb snippet get <id>`, and match the name against the content you meant to move.
+
+<!-- requires: dependencyGraph -->
+
+To plan the order before the first move, `mb dependency graph dashboard <id> --json` (or `card <id>`) lists everything the entity reads from; every card and snippet node outside the synced collection moves first.
+
+<!-- /requires -->
+
 <!-- requires: library -->
 
 ## Published table metadata (Library) and sync scope
@@ -203,11 +253,11 @@ Flagging the collection records it for the next export, which serializes its cur
 
 ## Don't (git-sync-specific)
 
-- Don't turn instance-side changes into hand-written repo files. When the changes were made against the instance, export them (`stash` / `create-branch` + `export`) and PR the exported branch; reconstructing them as YAML by hand — or pushing files in paths/formats the serializer doesn't own — produces content that never applies on import, and pushing behind Metabase's back races its own sync tasks. Hand-editing YAML belongs to the repo-first workflow, in the serialized layout the repo already uses.
+- Don't turn instance-side changes into hand-written repo files: export them and PR the exported branch (see the top of this skill). Files pushed behind Metabase's back race its own sync tasks.
 - Don't conclude from an empty `dirty` list that a change type isn't tracked. Dirty-tracking only records changes to _eligible_ objects; the usual cause is scope (the collection isn't flagged — see "Published table metadata"), not capability. Check `synced_collections` in `status` before concluding.
 - Don't run `git-sync import --force` or `git-sync export --force` without explicit user confirmation. Both are lossy — `--force` import discards instance-side work, `--force` export overwrites the remote branch.
 - Don't drive `git-sync` against a Metabase instance that doesn't have remote-sync configured — every verb returns an error pointing at the missing `remote-sync-*` settings. To check: `mb setting get remote-sync-url --profile <n> --json`.
 - Don't author content directly via `card create` / `transform create` and then assume `git-sync export` will commit it cleanly — the instance and repo can drift if you mix direct API writes with sync-tracked changes. If you do, follow direct writes immediately with `git-sync export -m "..."` to keep them in step.
+- Don't move a dashboard or question into a synced collection before what it depends on, and don't retry a `Uses content that is not remote synced.` refusal unchanged. Move the listed dependencies first, move the whole containing collection, or build the content in the synced collection to begin with (see "Moving content into or out of a synced collection").
 - Don't omit `-m` on `export` if the user wants a meaningful commit message — the default server-generated message is generic.
-- Don't `git-sync export` to `main`/`master` without explicit user confirmation — sync work is conventionally on a feature branch. See "Branch guard" above.
 - Don't reach for `mb setting set` to mark a collection as remote-synced — that endpoint writes single-key settings, not the bulk `collections` map. Use `mb git-sync add-collection <id>` / `mb git-sync remove-collection <id>` (above), and remember the toggle cascades to descendants.