@metabase/cli 0.2.1 → 0.2.2

package/dist/{update-DajyWtBN.mjs → update-CuKHukZ6.mjs}

@@ -1,11 +1,11 @@
-import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-DOTcPraV.mjs";
+import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand } from "./runtime-Ab96yYlM.mjs";
-import "./input-DzbvxKYU.mjs";
-import { parseId } from "./parse-id-CD54Chc5.mjs";
-import { readBody } from "./body-DKcQw7G5.mjs";
-import { bodyInputFlags } from "./body-flags-CgHgJBRC.mjs";
-import { Timeline, TimelineUpdateInput, timelineView } from "./timeline-BCTRThc-.mjs";
+import { defineMetabaseCommand } from "./runtime-CPIHg_Zg.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import "./input-BpXlmJ5J.mjs";
+import { readBody } from "./body-DXJ2v3GY.mjs";
+import { bodyInputFlags } from "./body-flags-Cbv-Ba6W.mjs";
+import { Timeline, TimelineUpdateInput, timelineView } from "./timeline-BNwnJ3g9.mjs";
 
 //#region src/commands/timeline/update.ts
 var update_default = defineMetabaseCommand({

package/dist/{update-CGWTX1Z0.mjs → update-CzrbMLZq.mjs}

@@ -1,11 +1,11 @@
-import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-DOTcPraV.mjs";
+import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand } from "./runtime-Ab96yYlM.mjs";
-import "./input-DzbvxKYU.mjs";
-import { parseId } from "./parse-id-CD54Chc5.mjs";
-import { readBody } from "./body-DKcQw7G5.mjs";
-import { bodyInputFlags } from "./body-flags-CgHgJBRC.mjs";
-import { Snippet, SnippetUpdateInput, snippetView } from "./snippet-DWiXNy4T.mjs";
+import { defineMetabaseCommand } from "./runtime-CPIHg_Zg.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import "./input-BpXlmJ5J.mjs";
+import { readBody } from "./body-DXJ2v3GY.mjs";
+import { bodyInputFlags } from "./body-flags-Cbv-Ba6W.mjs";
+import { Snippet, SnippetUpdateInput, snippetView } from "./snippet-1xYckIwc.mjs";
 
 //#region src/commands/snippet/update.ts
 var update_default = defineMetabaseCommand({

package/dist/{update-CO9uCJxV.mjs → update-DDVuyquf.mjs}

@@ -1,13 +1,13 @@
-import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-DOTcPraV.mjs";
+import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand } from "./runtime-Ab96yYlM.mjs";
-import "./input-DzbvxKYU.mjs";
-import { parseId } from "./parse-id-CD54Chc5.mjs";
-import { readBody } from "./body-DKcQw7G5.mjs";
-import { bodyInputFlags } from "./body-flags-CgHgJBRC.mjs";
-import "./validate-Cqa14t7o.mjs";
-import { SEGMENT_DEFINITION_LABELS, preflightMbql5Query, skipValidateFlag } from "./validate-query-D1N30wJ7.mjs";
-import { Segment, SegmentUpdateInput, segmentView } from "./segment-BPb1H6DW.mjs";
+import { defineMetabaseCommand } from "./runtime-CPIHg_Zg.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import "./input-BpXlmJ5J.mjs";
+import { readBody } from "./body-DXJ2v3GY.mjs";
+import { bodyInputFlags } from "./body-flags-Cbv-Ba6W.mjs";
+import "./validate-BoY75_M3.mjs";
+import { SEGMENT_DEFINITION_LABELS, preflightMbql5Query, skipValidateFlag } from "./validate-query-Di0VKMF-.mjs";
+import { Segment, SegmentUpdateInput, segmentView } from "./segment-cwIOOF0v.mjs";
 
 //#region src/commands/segment/update.ts
 var update_default = defineMetabaseCommand({

package/dist/{update-B1dkPypu.mjs → update-DpIzJ8Ts.mjs}

@@ -1,14 +1,14 @@
-import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-DOTcPraV.mjs";
+import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand } from "./runtime-Ab96yYlM.mjs";
-import "./input-DzbvxKYU.mjs";
-import { parseId } from "./parse-id-CD54Chc5.mjs";
-import { readBody } from "./body-DKcQw7G5.mjs";
-import { bodyInputFlags } from "./body-flags-CgHgJBRC.mjs";
-import "./validate-Cqa14t7o.mjs";
-import { TRANSFORM_SOURCE_QUERY_LABELS, preflightMbql5Query, skipValidateFlag } from "./validate-query-D1N30wJ7.mjs";
-import { Transform, TransformUpdateInput, transformView } from "./transform-BVHYzWpK.mjs";
-import { enrichTransformCollectionError } from "./collection-namespace-C7mr_a8H.mjs";
+import { defineMetabaseCommand } from "./runtime-CPIHg_Zg.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import "./input-BpXlmJ5J.mjs";
+import { readBody } from "./body-DXJ2v3GY.mjs";
+import { bodyInputFlags } from "./body-flags-Cbv-Ba6W.mjs";
+import "./validate-BoY75_M3.mjs";
+import { TRANSFORM_SOURCE_QUERY_LABELS, preflightMbql5Query, skipValidateFlag } from "./validate-query-Di0VKMF-.mjs";
+import { Transform, TransformUpdateInput, transformView } from "./transform-BkSkCvpx.mjs";
+import { enrichTransformCollectionError } from "./collection-namespace-8i_CvWsg.mjs";
 
 //#region src/commands/transform/update.ts
 var update_default = defineMetabaseCommand({

package/dist/{update-iY9WZqy0.mjs → update-DrvAdi-O.mjs}

@@ -1,12 +1,12 @@
-import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-DOTcPraV.mjs";
+import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand } from "./runtime-Ab96yYlM.mjs";
-import "./input-DzbvxKYU.mjs";
-import "./field-DsXTeqBy.mjs";
-import { parseId } from "./parse-id-CD54Chc5.mjs";
-import { readBody } from "./body-DKcQw7G5.mjs";
-import { bodyInputFlags } from "./body-flags-CgHgJBRC.mjs";
-import { Table, TableUpdateInput, tableView } from "./table-C3RIKiYM.mjs";
+import { defineMetabaseCommand } from "./runtime-CPIHg_Zg.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import "./input-BpXlmJ5J.mjs";
+import { readBody } from "./body-DXJ2v3GY.mjs";
+import { bodyInputFlags } from "./body-flags-Cbv-Ba6W.mjs";
+import "./field-RYBTW2KS.mjs";
+import { Table, TableUpdateInput, tableView } from "./table-fDvuvqoU.mjs";
 
 //#region src/commands/table/update.ts
 var update_default = defineMetabaseCommand({

package/dist/{update-Cyxjg496.mjs → update-Tw0kARao.mjs}

@@ -1,11 +1,11 @@
-import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-DOTcPraV.mjs";
+import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand } from "./runtime-Ab96yYlM.mjs";
-import "./input-DzbvxKYU.mjs";
-import { parseId } from "./parse-id-CD54Chc5.mjs";
-import { readBody } from "./body-DKcQw7G5.mjs";
-import { bodyInputFlags } from "./body-flags-CgHgJBRC.mjs";
-import { Document, DocumentUpdateInput, documentView } from "./document-CL4ML5FN.mjs";
+import { defineMetabaseCommand } from "./runtime-CPIHg_Zg.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import "./input-BpXlmJ5J.mjs";
+import { readBody } from "./body-DXJ2v3GY.mjs";
+import { bodyInputFlags } from "./body-flags-Cbv-Ba6W.mjs";
+import { Document, DocumentUpdateInput, documentView } from "./document-C7IR6T8c.mjs";
 
 //#region src/commands/document/update.ts
 var update_default = defineMetabaseCommand({

package/dist/{update-D80GWpWl.mjs → update-ZJ5T-SBW.mjs}

@@ -1,13 +1,13 @@
-import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-DOTcPraV.mjs";
+import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand } from "./runtime-Ab96yYlM.mjs";
-import "./input-DzbvxKYU.mjs";
-import { parseId } from "./parse-id-CD54Chc5.mjs";
-import { readBody } from "./body-DKcQw7G5.mjs";
-import { bodyInputFlags } from "./body-flags-CgHgJBRC.mjs";
-import "./validate-Cqa14t7o.mjs";
-import { MEASURE_DEFINITION_LABELS, preflightMbql5Query, skipValidateFlag } from "./validate-query-D1N30wJ7.mjs";
-import { Measure, MeasureUpdateInput, measureView } from "./measure-S9WszHre.mjs";
+import { defineMetabaseCommand } from "./runtime-CPIHg_Zg.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import "./input-BpXlmJ5J.mjs";
+import { readBody } from "./body-DXJ2v3GY.mjs";
+import { bodyInputFlags } from "./body-flags-Cbv-Ba6W.mjs";
+import "./validate-BoY75_M3.mjs";
+import { MEASURE_DEFINITION_LABELS, preflightMbql5Query, skipValidateFlag } from "./validate-query-Di0VKMF-.mjs";
+import { Measure, MeasureUpdateInput, measureView } from "./measure-DH3ow2ko.mjs";
 
 //#region src/commands/measure/update.ts
 var update_default = defineMetabaseCommand({

package/dist/{update-dashcard-DLq7ihNO.mjs → update-dashcard-Dnfa8_aJ.mjs}

@@ -1,13 +1,13 @@
-import { ConfigError, connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-DOTcPraV.mjs";
+import { ConfigError, connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand } from "./runtime-Ab96yYlM.mjs";
-import "./input-DzbvxKYU.mjs";
-import "./embedding-CKdw8q7p.mjs";
-import "./parameter-BZ6y-Gfs.mjs";
-import { parseId } from "./parse-id-CD54Chc5.mjs";
-import { readBody } from "./body-DKcQw7G5.mjs";
-import { bodyInputFlags } from "./body-flags-CgHgJBRC.mjs";
-import { DashboardDetail, Dashcard, DashcardPatchInput, dashcardView } from "./dashboard-B-MTpfeS.mjs";
+import { defineMetabaseCommand } from "./runtime-CPIHg_Zg.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import "./input-BpXlmJ5J.mjs";
+import { readBody } from "./body-DXJ2v3GY.mjs";
+import { bodyInputFlags } from "./body-flags-Cbv-Ba6W.mjs";
+import "./embedding-B0x9CPkU.mjs";
+import "./parameter-hCQ80jnc.mjs";
+import { DashboardDetail, Dashcard, DashcardPatchInput, dashcardView } from "./dashboard-BSCXTX4H.mjs";
 
 //#region src/commands/dashboard/update-dashcard.ts
 var update_dashcard_default = defineMetabaseCommand({

package/dist/{update-8bTrglfc.mjs → update-hoCyoR-u.mjs}

@@ -1,11 +1,11 @@
-import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-DOTcPraV.mjs";
+import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand } from "./runtime-Ab96yYlM.mjs";
-import "./input-DzbvxKYU.mjs";
-import { parseId } from "./parse-id-CD54Chc5.mjs";
-import { readBody } from "./body-DKcQw7G5.mjs";
-import { bodyInputFlags } from "./body-flags-CgHgJBRC.mjs";
-import { TimelineEvent, TimelineEventUpdateInput, timelineEventView } from "./timeline-BCTRThc-.mjs";
+import { defineMetabaseCommand } from "./runtime-CPIHg_Zg.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import "./input-BpXlmJ5J.mjs";
+import { readBody } from "./body-DXJ2v3GY.mjs";
+import { bodyInputFlags } from "./body-flags-Cbv-Ba6W.mjs";
+import { TimelineEvent, TimelineEventUpdateInput, timelineEventView } from "./timeline-BNwnJ3g9.mjs";
 
 //#region src/commands/timeline-event/update.ts
 var update_default = defineMetabaseCommand({

package/dist/{upgrade-CXoNQ4FH.mjs → upgrade-D0HiyTxw.mjs}

@@ -1,8 +1,8 @@
-import { AbortError, NetworkError, TimeoutError, UnknownError, errorMessage, outputFlags, package_default, renderItem, writeText } from "./capabilities-DOTcPraV.mjs";
+import { AbortError, NetworkError, TimeoutError, UnknownError, errorMessage, outputFlags, package_default, renderItem, writeText } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { HttpError, USER_AGENT, combineAborts, defineMetabaseCommand, parseJson, throwIfAborted } from "./runtime-Ab96yYlM.mjs";
-import { promptConfirm } from "./prompt-BgkWNgIR.mjs";
-import { streamProcess } from "./process-HDPKLS_z.mjs";
+import { HttpError, USER_AGENT, combineAborts, defineMetabaseCommand, parseJson, throwIfAborted } from "./runtime-CPIHg_Zg.mjs";
+import { promptConfirm } from "./prompt-DmxSLNrO.mjs";
+import { streamProcess } from "./process-BxAUv3Wx.mjs";
 import { z } from "zod";
 import { realpathSync } from "node:fs";
 import { compare, valid } from "semver";

package/dist/upload-WT6SywFa.mjs

@@ -0,0 +1,16 @@
+import "./command-augment-D9pI9Vbh.mjs";
+import { defineCommandGroup } from "./group-DfTvzGz-.mjs";
+
+//#region src/commands/upload/index.ts
+var upload_default = defineCommandGroup({
+	name: "upload",
+	description: "Upload CSV files into Metabase",
+	subCommands: {
+		csv: () => import("./csv-yoFA1hhv.mjs").then((m) => m.default),
+		append: () => import("./append-lL0IaI6U.mjs").then((m) => m.default),
+		replace: () => import("./replace-sHtPBNnA.mjs").then((m) => m.default)
+	}
+});
+
+//#endregion
+export { upload_default as default };

package/dist/{uuid-D6dao_q4.mjs → uuid-D7NcSTj8.mjs}

@@ -1,6 +1,6 @@
-import { ConfigError, outputFlags, writeJson, writeText } from "./capabilities-DOTcPraV.mjs";
+import { ConfigError, outputFlags, writeJson, writeText } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand, parseInteger } from "./runtime-Ab96yYlM.mjs";
+import { defineMetabaseCommand, parseInteger } from "./runtime-CPIHg_Zg.mjs";
 import { z } from "zod";
 import { randomUUID } from "node:crypto";
 

package/dist/{validate-Cqa14t7o.mjs → validate-BoY75_M3.mjs}

@@ -1,4 +1,4 @@
-import { ConfigError, escapeJsonPointerSegment, isPlainObject } from "./capabilities-DOTcPraV.mjs";
+import { ConfigError, escapeJsonPointerSegment, isPlainObject } from "./capabilities-1HTHeDa4.mjs";
 import { z } from "zod";
 import Ajv2020 from "ajv/dist/2020.js";
 import addFormats from "ajv-formats";

package/dist/{validate-query-D1N30wJ7.mjs → validate-query-Di0VKMF-.mjs}

@@ -1,5 +1,5 @@
-import { ConfigError, writeJson } from "./capabilities-DOTcPraV.mjs";
-import { assertNotLegacyEnvelopeWrappingMbql5, isMbql5Query, validateQuery } from "./validate-Cqa14t7o.mjs";
+import { ConfigError, writeJson } from "./capabilities-1HTHeDa4.mjs";
+import { assertNotLegacyEnvelopeWrappingMbql5, isMbql5Query, validateQuery } from "./validate-BoY75_M3.mjs";
 
 //#region src/commands/validate-query.ts
 const skipValidateFlag = { "skip-validate": {

package/dist/{values-DIBAgSyz.mjs → values-OBiEVCVH.mjs}

@@ -1,8 +1,8 @@
-import { connectionFlags, formatScalar, outputFlags, profileFlag, renderSummary } from "./capabilities-DOTcPraV.mjs";
+import { connectionFlags, formatScalar, outputFlags, profileFlag, renderSummary } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand } from "./runtime-Ab96yYlM.mjs";
-import { FieldValues, fieldValuesView } from "./field-DsXTeqBy.mjs";
-import { parseId } from "./parse-id-CD54Chc5.mjs";
+import { defineMetabaseCommand } from "./runtime-CPIHg_Zg.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import { FieldValues, fieldValuesView } from "./field-RYBTW2KS.mjs";
 
 //#region src/commands/field/values.ts
 var values_default = defineMetabaseCommand({

package/dist/{verify-DvhZWmS2.mjs → verify-VEB7TBQ_.mjs}

@@ -1,5 +1,5 @@
-import { MetabaseError, NetworkError, TimeoutError, errorMessage } from "./capabilities-DOTcPraV.mjs";
-import { HttpError, createClient, probeServer } from "./runtime-Ab96yYlM.mjs";
+import { MetabaseError, NetworkError, TimeoutError, errorMessage } from "./capabilities-1HTHeDa4.mjs";
+import { HttpError, createClient, probeServer } from "./runtime-CPIHg_Zg.mjs";
 import { z } from "zod";
 
 //#region src/domain/user.ts

package/dist/{wait-CW1OawkI.mjs → wait-B9qNlcTe.mjs}

@@ -1,9 +1,9 @@
-import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-DOTcPraV.mjs";
+import { connectionFlags, outputFlags, profileFlag, renderSummary } from "./capabilities-1HTHeDa4.mjs";
 import "./command-augment-D9pI9Vbh.mjs";
-import { defineMetabaseCommand } from "./runtime-Ab96yYlM.mjs";
-import { parseId } from "./parse-id-CD54Chc5.mjs";
-import { DEFAULT_INTERVAL_MS, DEFAULT_TIMEOUT_MS } from "./poll-DVF9EnEb.mjs";
-import { SyncTaskOrIdle, formatSyncTask, pollSyncTask, syncTaskIdleView, syncTaskView, throwIfFailedTask } from "./poll-task-CpHGQOd5.mjs";
+import { defineMetabaseCommand } from "./runtime-CPIHg_Zg.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import { DEFAULT_INTERVAL_MS, DEFAULT_TIMEOUT_MS } from "./poll-rqLkEJVP.mjs";
+import { SyncTaskOrIdle, formatSyncTask, pollSyncTask, syncTaskIdleView, syncTaskView, throwIfFailedTask } from "./poll-task-CiB1o1wG.mjs";
 
 //#region src/commands/git-sync/wait.ts
 const WaitResult = SyncTaskOrIdle;

package/dist/{wait-flags-DvNU8ahZ.mjs → wait-flags-D0FEgH6k.mjs}

@@ -1,5 +1,5 @@
-import { parseId } from "./parse-id-CD54Chc5.mjs";
-import { DEFAULT_INTERVAL_MS, DEFAULT_TIMEOUT_MS } from "./poll-DVF9EnEb.mjs";
+import { parseId } from "./parse-id-waEVK-uR.mjs";
+import { DEFAULT_INTERVAL_MS, DEFAULT_TIMEOUT_MS } from "./poll-rqLkEJVP.mjs";
 
 //#region src/commands/wait-flags.ts
 const waitScheduleFlags = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metabase/cli",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "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, 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, 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
 ---
 
@@ -12,8 +12,8 @@ Top-level command groups (run `mb <group> --help` to discover verbs):
 
 ```
 auth | db | table | field | upload | query | card | dashboard | snippet | segment | measure | collection | library
-document | timeline | timeline-event | transform | transform-job | transform-tag | setting | search | git-sync | setup
-eid | uuid | upgrade | skills
+document | timeline | timeline-event | transform | transform-job | transform-tag | alert | subscription | setting
+search | git-sync | 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.
@@ -129,6 +129,7 @@ Routine verb shapes (list / get / create / update), every flag, and output schem
 - **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: pull the current set with `dashboard get <id> --fields parameters --json`, add/change entries, and send the full array back via `dashboard update --body '{"parameters":[…]}'` (or supply it in `create`). Omitting a parameter deletes it. Each parameter is `{id, type, …}`. **`id` is a descriptive slug-like string you pick (e.g. `order_status`), unique within this dashboard — Metabase stores any non-blank string verbatim. Do NOT invent a random/opaque id by guessing; reuse the `slug`. If you genuinely need an opaque id, mint one with `mb uuid` — never fabricate one.** `type` is a **closed enum**; an unlisted value is a hard parse error that echoes the full allowed set back to you: string ops `string/=` `string/!=` `string/contains` `string/does-not-contain` `string/starts-with` `string/ends-with`; number ops `number/=` `number/!=` `number/between` `number/>=` `number/<=`; date `date/single` `date/range` `date/relative` `date/month-year` `date/quarter-year` `date/all-options`; plus `category`, `id`, `boolean/=`, `temporal-unit`, and bare `number`/`text`/`date`/`boolean`. A parameter only filters a card once it is **mapped**: each dashcard's `parameter_mappings` is `[{parameter_id, target}]` where `parameter_id` must match a parameter's `id` exactly, and `target` is `["dimension", ["field", <field-id>, null]]` for an MBQL card column, `["dimension", ["template-tag", "<tag>"]]` for a native field-filter tag, or `["variable", ["template-tag", "<tag>"]]` for a native raw-value tag. Populate a dropdown with `values_source_type`: `"static-list"` + `values_source_config.values`, or `"card"` + `{card_id, value_field, label_field}`; omit it to pull live distinct values from the mapped field. `dashboard parameter-values <id> <parameter-id> [--query <substr>]` fetches those selectable values (`{values, has_more_values}`); `--query` is a case-insensitive substring search.
+- **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`.
@@ -138,7 +139,7 @@ Routine verb shapes (list / get / create / update), every flag, and output schem
 - **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.
+- **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).
 - **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)
@@ -150,6 +151,7 @@ This file is enough for any single-command task. For anything deeper, load the r
 - **`visualization`** — choosing a card's `display` and authoring `visualization_settings`. The presentation counterpart to `mbql`.
 - **`dashboard`** — building interactive dashboards: wiring filters (parameters + mappings), linked/cascading filters, cross-filtering, click behavior, series, and tabs. Load beyond a plain card-layout task.
 - **`metadata`** — setting field/table metadata: semantic types, foreign-key targets, dropdown/scan behavior, and column visibility, and the downstream features each unlocks. Load when editing what a column _means_, not its data.
+- **`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.

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

@@ -1,12 +1,14 @@
 ---
 name: git-sync
-description: Round-trip Metabase content (cards, dashboards, transforms, snippets, collections) between an instance and a git remote via `mb git-sync …` — status, dirty / has-remote-changes checks, import, export (with branch guard), branches, stash, add/remove a collection from sync. Load when the user wants to "import the latest changes", "export to git", "git sync", "dirty check", "stash before pulling", "add a collection to sync", or anything `mb git-sync …`.
+description: Round-trip Metabase content (cards, dashboards, transforms, snippets, collections, Library-published table/field metadata) between an instance and a git remote via `mb git-sync …` — status, dirty / has-remote-changes checks, import, export (with branch guard), branches, stash, add/remove a collection from sync. Load when the user wants to "import the latest changes", "export to git", "push my changes to the repo", "open a PR with my Metabase changes", "git sync", "dirty check", "stash before pulling", "add a collection to sync", or anything `mb git-sync …`.
 allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
 ---
 
 # git-sync (representations ↔ instance)
 
-Metabase content (cards, dashboards, transforms, snippets, collections, …) can live in a git repo as YAML and round-trip in and out of a Metabase instance via the `git-sync` verbs. The instance is configured with a `remote-sync-*` settings block (URL, branch, token, type read-only/read-write); the CLI drives the sync tasks against `/api/ee/remote-sync/*`. Only collections flagged for sync serialize; everything else is local-only.
+Metabase content (cards, dashboards, transforms, snippets, collections, …) can live in a git repo as YAML and round-trip in and out of a Metabase instance via the `git-sync` verbs. The instance is configured with a `remote-sync-*` settings block (URL, branch, token, type read-only/read-write); the CLI drives the sync tasks against `/api/ee/remote-sync/*`. Only collections flagged for sync serialize; everything else is local-only. Table and field metadata round-trips too, for Library-published tables in a flagged collection — see "Published table metadata" below.
+
+The repo and the instance are two ends of the same state; what "push my changes" means depends on where the changes were made. If they were made **in the instance** (CLI verbs against a read-write instance — cards edited, transforms created, tables published, metadata written), "push my changes" / "save this to the repo" / "open a PR with these changes" means driving the instance's export to a branch (`stash` or `create-branch` + `export`) and opening the PR from that branch — not reconstructing the changes as files. If the workflow is **repo-first** (content YAML edited in the repo, the instance imports it), plain `git` against the repo is the way — but only in the serialized layout already there: files in paths or formats the serializer doesn't own are invisible to Metabase and never apply on import.
 
 This skill covers the import/export workflow. Flag conventions and auth setup live in `core` (`mb skills get core`). To author content YAML by hand: the per-resource clause and settings shapes mirror the API form — query bodies follow the `mbql` skill, `visualization_settings` follow the `visualization` skill — except the portable YAML uses **name-based** references (e.g. `[Sample Database, PUBLIC, ORDERS, TOTAL]`, and entity-ids for cross-entity FKs) where the API form uses numeric ids. For the on-disk folder layout, model new files on what the synced repo already contains.
 
@@ -126,13 +128,26 @@ mb setting set remote-sync-type '"read-write"' --profile <n>
 
 (`setting set` parses the value as strict JSON — mind the inner double quotes; see `core`.) The server also rejects switching to `:read-only` while the Remote Sync collection is dirty; export or `--force` import first if you're going the other way.
 
-**Verifying the result.** The CLI's `Collection` schema doesn't yet expose `is_remote_synced`, so `collection get --json` won't show the flag. The pragmatic confirmation paths are:
+**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.
+
+## Published table metadata (Library) and sync scope
+
+Table and field metadata — table/field descriptions, semantic types (`type/PK`, `type/FK`), FK targets, plus segments and measures on the table — serializes for **Library-published tables only**, under `databases/<db>/schemas/<schema>/tables/<table>/…` in the repo. Eligibility is two-gated: the table must be published (`mb library publish`), **and** the Library collection holding it must itself carry `is_remote_synced: true`. An ordinary warehouse table, or a transform's target table that isn't published, never serializes — a transform's YAML carries only the transform definition (query, target, description), not the output table's field metadata.
+
+The classic trap: publish tables, write field metadata, then `git-sync dirty` comes back empty and nothing lands in the repo. That does not mean git-sync can't carry table metadata — it means the Library collection isn't in the sync scope, so nothing was eligible for dirty-tracking when the writes happened. Check the scope (`synced_collections` in `status`), then:
+
+```bash
+mb library get --profile <n> --json                                # Library Data collection id
+mb git-sync add-collection <library-data-id> --profile <n>
+mb git-sync stash --new-branch <branch> -m "..." --profile <n>     # or create-branch + export
+```
 
-- `mb git-sync is-dirty --profile <n> --json` after editing a card in the now-synced collection — a `true` reading proves it's tracked.
-- The Metabase Admin UI's Remote Sync page renders the per-collection toggles.
+Flagging the collection records it for the next export, which serializes its current content — including already-published tables and their field metadata. `mb library publish` prints a reminder when the target collection is outside the sync scope on an instance with a configured remote.
 
 ## 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 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.