@metabase/cli 0.5.5 → 0.5.7-alpha.bryan-rci-6-coverage.6f886fd

package/dist/{update-D9fs-PSK.mjs → update-DwGo58Kc.mjs}

@@ -1,10 +1,10 @@
-import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as parseId } from "./parse-id-EXZan40V.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { at as connectionFlags, dt as profileFlag, l as renderSummary, ut as outputFlags } from "./cli.mjs";
+import { t as parseId } from "./parse-id-BXkvTl89.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { d as DashboardUpdateInput, o as DashboardDetail } from "./dashboard-Cwsf-e9T.mjs";
 import { n as dashboardView } from "./dashboard-Bx2sYijR.mjs";
-import { t as preflightDashcardCardReferences } from "./preflight-4iy2qzsh.mjs";
+import { t as preflightDashcardCardReferences } from "./preflight-BJ5Bve-N.mjs";
 //#region src/commands/dashboard/update.ts
 var update_default = defineMetabaseCommand({
 	meta: {

package/dist/{update-BemK_tZ_.mjs → update-DyXj5mTv.mjs}

@@ -1,6 +1,6 @@
-import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as parseId } from "./parse-id-EXZan40V.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { at as connectionFlags, dt as profileFlag, l as renderSummary, ut as outputFlags } from "./cli.mjs";
+import { t as parseId } from "./parse-id-BXkvTl89.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { i as CardDetail, l as CardUpdateInput } from "./card-BJRZ5D5Q.mjs";
 import { n as cardView } from "./card-VipF12MJ.mjs";

package/dist/{update-dashcard-Bpv45o1_.mjs → update-dashcard-BhT2FBd4.mjs}

@@ -1,6 +1,6 @@
-import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as parseId } from "./parse-id-EXZan40V.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { at as connectionFlags, dt as profileFlag, l as renderSummary, ut as outputFlags } from "./cli.mjs";
+import { t as parseId } from "./parse-id-BXkvTl89.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { h as DashcardPatchInput, m as DashcardDetail } from "./dashboard-Cwsf-e9T.mjs";
 import { r as dashcardView } from "./dashboard-Bx2sYijR.mjs";

package/dist/{update-BiBazvzY.mjs → update-t2zdccd5.mjs}

@@ -1,10 +1,10 @@
-import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as parseId } from "./parse-id-EXZan40V.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { at as connectionFlags, dt as profileFlag, l as renderSummary, ut as outputFlags } from "./cli.mjs";
+import { t as parseId } from "./parse-id-BXkvTl89.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
-import { n as DataAction, s as DataActionUpdateInput } from "./data-action-CuvI17XF.mjs";
+import { c as DataActionUpdateInput, r as DataAction } from "./data-action-DAw6WRTH.mjs";
 import { DATA_ACTION_DATASET_QUERY, skipValidateFlag } from "./validate-query-Bf5FhhMI.mjs";
-import { n as dataActionView } from "./data-action-DLj9cgpu.mjs";
+import { n as dataActionView } from "./data-action-Co_Yf1uC.mjs";
 //#region src/commands/data-action/update.ts
 var update_default = defineMetabaseCommand({
 	meta: {

package/dist/{update-CsH0lSpQ2.mjs → update-wh2EjN242.mjs}

@@ -1,6 +1,6 @@
-import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as parseId } from "./parse-id-EXZan40V.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { at as connectionFlags, dt as profileFlag, l as renderSummary, ut as outputFlags } from "./cli.mjs";
+import { t as parseId } from "./parse-id-BXkvTl89.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { o as TransformJobUpdateInput, t as TransformJob } from "./transform-job-CDIb3B9o.mjs";
 import { t as transformJobView } from "./transform-job-D18XRLBK.mjs";

package/dist/{update-CyfLXFKR.mjs → update-xYxKw2UB.mjs}

@@ -1,6 +1,6 @@
-import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as parseId } from "./parse-id-EXZan40V.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { at as connectionFlags, dt as profileFlag, l as renderSummary, ut as outputFlags } from "./cli.mjs";
+import { t as parseId } from "./parse-id-BXkvTl89.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
 import { t as bodyInputFlags } from "./body-flags-AqKpN01Y.mjs";
 import { c as TimelineUpdateInput, t as Timeline } from "./timeline-DcsCXNUt.mjs";
 import { n as timelineView } from "./timeline-BgWz8DYK.mjs";

package/dist/{upgrade-D3aDQZwd.mjs → upgrade-BqBjnjjU.mjs}

@@ -1,8 +1,7 @@
 import { g as errorMessage, i as AbortError, m as UnknownError, p as TimeoutError, u as NetworkError } from "./predicates-0C0TsWcJ.mjs";
-import { K as HttpError, X as parseJson, lt as outputFlags, nt as name, o as renderItem, p as writeText, rt as version, t as interruptSignal, v as promptConfirm } from "./cli.mjs";
-import { E as USER_AGENT, t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
-import { n as throwIfAborted, t as combineAborts } from "./signal-BNUlQjpc.mjs";
-import { n as streamProcess } from "./process-BQC3mK2k.mjs";
+import { Z as parseJson, it as version, m as writeText, o as renderItem, q as HttpError, rt as name, t as interruptSignal, ut as outputFlags, y as promptConfirm } from "./cli.mjs";
+import { E as USER_AGENT, U as combineAborts, W as throwIfAborted, t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
+import { a as streamProcess } from "./process-cDa9fEBe.mjs";
 import { z } from "zod";
 import { realpathSync } from "node:fs";
 import { compare, valid } from "semver";

package/dist/upload-C0GfBUvp.mjs

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

package/dist/{upload-BAD_9okY.mjs → upload-D0zRTkyv.mjs}

@@ -1,5 +1,5 @@
 import { o as ConfigError, v as isFileNotFoundError } from "./predicates-0C0TsWcJ.mjs";
-import { D as fileNotFoundError } from "./runtime-D5yfliIq.mjs";
+import { D as fileNotFoundError } from "./runtime-DsfR_yrb.mjs";
 import { readFile } from "node:fs/promises";
 import { basename } from "node:path";
 //#region src/runtime/upload.ts

package/dist/{upload-B8HbBXb8.mjs → upload-kM0-7Bx2.mjs}

@@ -1,7 +1,7 @@
-import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { at as connectionFlags, dt as profileFlag, l as renderSummary, ut as outputFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
 import { t as ContentTranslationUploadResult } from "./content-translation-BrHOrmj9.mjs";
-import { n as requireUploadFilePath, t as readCsvFile } from "./upload-BAD_9okY.mjs";
+import { n as requireUploadFilePath, t as readCsvFile } from "./upload-D0zRTkyv.mjs";
 //#region src/output/views/content-translation.ts
 const contentTranslationUploadView = {
 	compactPick: ContentTranslationUploadResult,

package/dist/{uuid-BIDBDPLI.mjs → uuid-DsuYe9z7.mjs}

@@ -1,6 +1,6 @@
 import { o as ConfigError } from "./predicates-0C0TsWcJ.mjs";
-import { f as writeJson, lt as outputFlags, mt as parseInteger, p as writeText } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { f as writeJson, ht as parseInteger, m as writeText, ut as outputFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
 import { z } from "zod";
 import { randomUUID } from "node:crypto";
 //#region src/commands/uuid.ts

package/dist/{values-BDekphEw.mjs → values-kLEvyjSy.mjs}

@@ -1,6 +1,6 @@
-import { h as formatScalar, it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as parseId } from "./parse-id-EXZan40V.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { at as connectionFlags, dt as profileFlag, g as formatScalar, l as renderSummary, ut as outputFlags } from "./cli.mjs";
+import { t as parseId } from "./parse-id-BXkvTl89.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
 import { d as FieldValues } from "./field-C2qOViFZ.mjs";
 import { s as fieldValuesView } from "./field-CT4r6b92.mjs";
 //#region src/commands/field/values.ts

package/dist/{verify-k0WHgc16.mjs → verify-ChvmI4lq.mjs}

@@ -1,7 +1,7 @@
-import { n as createClient } from "./client-D2ycdMRO.mjs";
+import { n as createClient } from "./client-C_5K9lZA.mjs";
 import { g as errorMessage, l as MetabaseError, p as TimeoutError, u as NetworkError } from "./predicates-0C0TsWcJ.mjs";
-import { K as HttpError } from "./cli.mjs";
-import { B as probeServer, E as USER_AGENT } from "./runtime-D5yfliIq.mjs";
+import { q as HttpError } from "./cli.mjs";
+import { B as probeServer, E as USER_AGENT } from "./runtime-DsfR_yrb.mjs";
 //#region src/core/auth/verify.ts
 const VERIFY_TIMEOUT_MS = 15e3;
 async function verifyAndProbe(url, credential, options = {}) {

package/dist/{verify-CMTrDvAW.mjs → verify-CvYsiaqY.mjs}

@@ -1,6 +1,6 @@
-import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as parseId } from "./parse-id-EXZan40V.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { at as connectionFlags, dt as profileFlag, l as renderSummary, ut as outputFlags } from "./cli.mjs";
+import { t as parseId } from "./parse-id-BXkvTl89.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
 import { t as ModerationReview } from "./moderation-review-Bf9bPNQI.mjs";
 import { i as moderationReviewView, n as verifyFlags, r as describeReview, t as reviewInput } from "./verify-flags-DEVMB9w0.mjs";
 //#region src/commands/card/verify.ts

package/dist/{verify-BnZqq9Aw.mjs → verify-D27n5y3t.mjs}

@@ -1,6 +1,6 @@
-import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as parseId } from "./parse-id-EXZan40V.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
+import { at as connectionFlags, dt as profileFlag, l as renderSummary, ut as outputFlags } from "./cli.mjs";
+import { t as parseId } from "./parse-id-BXkvTl89.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
 import { t as ModerationReview } from "./moderation-review-Bf9bPNQI.mjs";
 import { i as moderationReviewView, n as verifyFlags, r as describeReview, t as reviewInput } from "./verify-flags-DEVMB9w0.mjs";
 //#region src/commands/dashboard/verify.ts

package/dist/{wait-C69z8PSw.mjs → wait-DioDMGLJ.mjs}

@@ -1,7 +1,7 @@
-import { it as connectionFlags, l as renderSummary, lt as outputFlags, ut as profileFlag } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-D5yfliIq.mjs";
-import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-vxN__4cz.mjs";
-import { r as parseWaitSchedule } from "./wait-flags-C3cu_O0w.mjs";
+import { at as connectionFlags, dt as profileFlag, l as renderSummary, ut as outputFlags } from "./cli.mjs";
+import { t as defineMetabaseCommand } from "./runtime-DsfR_yrb.mjs";
+import { n as DEFAULT_TIMEOUT_MS, t as DEFAULT_INTERVAL_MS } from "./poll-D5eA9cN2.mjs";
+import { r as parseWaitSchedule } from "./wait-flags-Qqvlb3Rv.mjs";
 import { u as syncTaskView } from "./git-sync-D1aKczo6.mjs";
 import { a as throwIfFailedTask, i as taskPollOptions, n as formatSyncTask, r as syncTaskIdleView, t as SyncTaskOrIdle } from "./sync-task-Gf86CU9l.mjs";
 //#region src/commands/git-sync/wait.ts

package/dist/{wait-flags-C3cu_O0w.mjs → wait-flags-Qqvlb3Rv.mjs}

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

package/dist/{window-D1w7B0vh.mjs → window-BoW2xWwm.mjs}

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

package/dist/yaml-QoEP-7KU.mjs

@@ -0,0 +1,38 @@
+import { g as errorMessage, h as ValidationError, o as ConfigError } from "./predicates-0C0TsWcJ.mjs";
+import { YAMLParseError, parse } from "yaml";
+//#region src/runtime/yaml.ts
+function parseYaml(input, schema, opts = {}) {
+	const result = parseYamlResult(input, schema, opts);
+	if (!result.ok) throw result.error;
+	return result.value;
+}
+function parseYamlResult(input, schema, opts = {}) {
+	const sourcePrefix = opts.source ? `${opts.source}: ` : "";
+	let raw;
+	try {
+		raw = parse(input);
+	} catch (error) {
+		if (error instanceof YAMLParseError) return {
+			ok: false,
+			error: new ConfigError(`${sourcePrefix}invalid YAML: ${error.message}`)
+		};
+		return {
+			ok: false,
+			error: new ConfigError(`${sourcePrefix}invalid YAML: ${errorMessage(error)}`)
+		};
+	}
+	const parsed = schema.safeParse(raw);
+	if (!parsed.success) return {
+		ok: false,
+		error: new ValidationError(`${sourcePrefix}value did not match expected schema`, {
+			source: opts.source ?? "<input>",
+			zodIssues: parsed.error.issues
+		})
+	};
+	return {
+		ok: true,
+		value: parsed.data
+	};
+}
+//#endregion
+export { parseYaml as t };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metabase/cli",
-  "version": "0.5.5",
+  "version": "0.5.7-alpha.bryan-rci-6-coverage.6f886fd",
   "description": "Metabase CLI",
   "license": "AGPL-3.0",
   "repository": {

package/skill-data/core/SKILL.md

@@ -181,7 +181,7 @@ This file is enough for any single-command task. For anything deeper, load the r
 <!-- /requires -->
 - **`document`** — Metabase documents (TipTap body, embedding cards).
 <!-- requires: dataActionsWithoutModel -->
-- **`data-action`** — saved SQL writes: enabling, body, parameters, running.
+- **`data-action`** — writes, as table actions or SQL query actions: enabling, body, parameters, running.
   <!-- /requires -->
   <!-- requires: remoteSync -->
 - **`git-sync`** — round-tripping content to/from a git remote.

package/skill-data/data-action/SKILL.md

@@ -1,16 +1,21 @@
 ---
 name: data-action
-description: Author and run Metabase data actions with the `mb` CLI — saved, parameterized native SQL writes (INSERT, UPDATE, DELETE) filed in a collection and run with values. Covers enabling them on a database, the collection they go in, the body, mapping template tags to parameters, running, and the lifecycle. Triggers — "add a data action", "let users update a row", "a button that inserts a record", "run a write query", "a form that saves to the database", "delete rows from Metabase". Inside a data app, start with `data-app-actions`.
+description: Author and run Metabase data actions with the `mb` CLI — table actions that insert, update or delete one row of a table, and query actions that run a parameterized native SQL write (INSERT, UPDATE, DELETE), filed in a collection and run with values. Covers enabling them on a database, picking the type, the collection they go in, each type's body and parameters, running, and the lifecycle. Triggers — "add a data action", "let users update a row", "a button that inserts a record", "add a record to a table", "run a write query", "a form that saves to the database", "delete rows from Metabase". Inside a data app, start with `data-app-actions`.
 allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
 requires: [dataActionsWithoutModel]
 ---
 
 # Data actions
 
-A **data action** is one native SQL statement that writes — `INSERT`, `UPDATE` or `DELETE` — with named inputs. It lives in a collection, and dashboards, apps and `mb data-action execute` run it with values.
+A **data action** writes to a database with named inputs. A **table action** (`type: "implicit"`) inserts, updates or deletes one row of a table; a **query action** (`type: "query"`) runs one native SQL statement — `INSERT`, `UPDATE` or `DELETE`. Either lives in a collection, and dashboards, apps and `mb data-action execute` run it with values.
 
 Flag conventions and `./.scratch` are in `core`; the native query and its template tags follow `native-sql`. This skill covers what a data action adds.
 
+## Pick the type
+
+- **Table action** (_Table actions_) for a write of one row by its primary key: insert a row, change some of its columns, delete it. There is no SQL to write.
+- **Query action** (_Query actions_) for anything else: a computed value (`now()`), several rows or tables, rows matched by another column, a table without exactly one primary key, or setting a column to `NULL`.
+
 ## Check the database first
 
 Data actions are off on every database until an admin turns on **Data actions** for it ("Allow data actions that use this database to be run", Admin → Databases → the database). That toggle is the database setting `database-enable-actions`.
@@ -30,7 +35,7 @@ A data action goes in a data actions collection, a data app collection, or the d
 mb collection create --namespace data-actions --body '{"name":"Order actions"}' --json
 ```
 
-## The body
+## Query actions
 
 Mint one template-tag `id` per tag with `mb uuid --count <n> --format text`.
 
@@ -38,7 +43,6 @@ Mint one template-tag `id` per tag with `mb uuid --count <n> --format text`.
 {
   "name": "Set order note",
   "type": "query",
-  "database_id": 1,
   "collection_id": 12,
   "dataset_query": {
     "lib/type": "mbql/query",
@@ -87,12 +91,12 @@ Mint one template-tag `id` per tag with `mb uuid --count <n> --format text`.
 }
 ```
 
-- `type` is always `"query"`. Never set `model_id` or `type: "implicit"`; `mb data-action create` refuses both.
-- `database_id` and `dataset_query.database` are the same id (`mb db list`). `collection_id` is the data actions collection (here `12`); omit it for the data actions root.
+- Never set `model_id`; `mb data-action create` refuses it.
+- `dataset_query.database` is the database the action writes to (`mb db list`); Metabase takes the action's `database_id` from it. `collection_id` is the data actions collection (here `12`); omit it for the data actions root.
 - A template tag's `id` is a UUID, unique among the tags: the representation schema requires one.
 - One statement, no `;`. `create` and `update` validate `dataset_query` as `native-sql` does.
 
-## Parameters: one per template tag
+### Parameters: one per template tag
 
 Each `{{name}}` needs a `template-tags` entry and a `parameters` entry, all using the same name:
 
@@ -108,26 +112,54 @@ Each `{{name}}` needs a `template-tags` entry and a `parameters` entry, all usin
 - Set `required: true` on every input the statement cannot run without (`WHERE` keys, `NOT NULL` columns).
 - Wrap an optional input in `[[ … ]]` with `required: false`; the clause drops out when no value is given. This makes one action do partial updates: `UPDATE orders SET updated_at = now() [[, note = {{note}}]] [[, status = {{status}}]] WHERE id = {{order_id}}`.
 
+## Table actions
+
+```json
+{
+  "name": "Add customer",
+  "type": "implicit",
+  "kind": "row/create",
+  "table_id": 7,
+  "collection_id": 12
+}
+```
+
+- `kind` is `row/create`, `row/update` or `row/delete`; `table_id` comes from `mb table list --db-id <id>`. The table needs exactly one primary key, or create answers `An implicit action needs a table with exactly one primary key.`
+- In a data app's collection the table must also be published to the Library (`mb library publish`), or create answers `An implicit action in a data app's collection can write only to a table published to the Library.`
+- The body has no `dataset_query` or `parameters`: Metabase derives the parameters from the table's columns, without sensitive and retired ones. Each parameter `id` is its column name, slugified; `mb data-action get <id> --full --json` lists them.
+
+| `kind`       | Parameters                             | Answers                                                                 |
+| ------------ | -------------------------------------- | ----------------------------------------------------------------------- |
+| `row/create` | every column but an auto-increment key | `{"created-row": {...}}`: the new row's parameter columns, key included |
+| `row/update` | the key and every other column         | `{"rows-updated": 1}`                                                   |
+| `row/delete` | the key                                | `{"rows-deleted": 1}`                                                   |
+
+- `required` marks each `NOT NULL` column without a default, and the key of an update or delete. Execution itself checks only that an update or delete has the key; an insert without a `NOT NULL` column fails in the database.
+- An update writes only the columns given a value. A `null` value is dropped, so an update can't clear a column. A key that matches no row is refused: `Sorry, the row you're trying to update doesn't exist` (or `delete`).
+- `visualization_settings.fields.<parameter id>.hidden: true` hides a parameter: execution refuses a value for it, and a data app's `src/metabase.ts` leaves it out. Hide a column an insert needs only when the same field has a `defaultValue`.
+- A patch (_Lifecycle_) changes a query action's `dataset_query` or a table action's `kind` and `table_id`, never both.
+
 ## Run it
 
 ```bash
 mb data-action execute <id> --body '{"parameters":{"order_id":1042,"note":"rush delivery"}}'
 ```
 
-`parameters` is keyed by parameter `id`. The result is `{"rows-affected": <n>}`. A missing required value is refused. A run cannot be undone, so confirm with the user before running against data that matters, and test a new action on a row created for the purpose.
+`parameters` is keyed by parameter `id`. A query action refuses a missing required value and answers `{"rows-affected": <n>}`; a table action answers as _Table actions_ shows. A run cannot be undone, so confirm with the user before running against data that matters, and test a new action on a row created for the purpose.
 
 ## Lifecycle
 
-| Task                     | Command                                                                                  |
-| ------------------------ | ---------------------------------------------------------------------------------------- |
-| Find                     | `mb data-action list` (unarchived only), `mb search --models action <text>`              |
-| Inspect                  | `mb data-action get <id> --full --json`                                                  |
-| Change SQL, inputs, name | `mb data-action update <id> --file patch.json` (changed fields only)                     |
-| Move                     | `mb data-action update <id> --body '{"collection_id":<id>}'`                             |
-| Archive / restore        | `mb data-action archive <id>` / `mb data-action update <id> --body '{"archived":false}'` |
-| Delete                   | `mb data-action delete <id> --yes` (also removes the dashboard buttons that run it)      |
-
-Archiving or deleting a collection archives or deletes its data actions. Existing model-bound or implicit data actions still list, run and archive; leave them as they are.
+| Task                  | Command                                                                                  |
+| --------------------- | ---------------------------------------------------------------------------------------- |
+| Find                  | `mb data-action list` (unarchived only), `mb search --models action <text>`              |
+| Inspect               | `mb data-action get <id> --full --json`                                                  |
+| Change a query action | `mb data-action update <id> --file patch.json` (changed fields only)                     |
+| Change a table action | `mb data-action update <id> --body '{"kind":"row/update"}'` (or `table_id`)              |
+| Move                  | `mb data-action update <id> --body '{"collection_id":<id>}'`                             |
+| Archive / restore     | `mb data-action archive <id>` / `mb data-action update <id> --body '{"archived":false}'` |
+| Delete                | `mb data-action delete <id> --yes` (also removes the dashboard buttons that run it)      |
+
+Archiving or deleting a collection archives or deletes its data actions. Existing data actions of a model still list, run and archive; leave them as they are.
 
 ## Don't
 

package/skill-data/data-app/SKILL.md

@@ -39,7 +39,7 @@ mb data-app create --body '{"name":"sales-overview","display_name":"Sales overvi
 mb data-app scaffold <repo>/data_apps/sales-overview && cd <repo>/data_apps/sales-overview
 ```
 
-`scaffold [dir]` takes a **directory**, not the slug: it copies the Vite + React + TypeScript template into a new or empty directory (the current one when omitted) and needs no server. When the instance syncs with a git repository (`mb git-sync status`), the directory is `data_apps/<slug>/` in a local clone of that repository (ask the user for its path, or clone the remote), where an export writes the app's `data_app.yaml` and bundle: an export leaves the source alone and an import ignores it, so the repository keeps the source with the app. `scaffold` needs an empty directory, so scaffold before the app's first export; for an app already in the repository, scaffold into a new directory and copy its files, dotfiles included (`cp -R <dir>/. data_apps/<slug>/`), in beside `data_app.yaml` and `dist/`; check `.gitignore` is there before `npm install`. Without a repository, use any new directory, and once remote sync is set up, move the project (without `node_modules/`, `dist/`, `.env.local` and a hand-written `data_app.yaml`) into `data_apps/<slug>/` before committing its source. Then install the SDK, then the rest:
+`scaffold [dir]` takes a **directory**, not the slug: it copies the Vite + React + TypeScript template into a new or empty directory (the current one when omitted) and needs no server. When the instance syncs with a git repository (`mb git-sync status`), the directory is `data_apps/<slug>/` in a local clone of that repository (ask the user for its path, or clone the remote), where an export writes the app's `data_app.yaml` and bundle: an export leaves the source alone and an import ignores it, so the repository keeps the source with the app. `scaffold` needs an empty directory, so scaffold before the app's first export; for an app already in the repository, scaffold into a new directory and copy its files, dotfiles included (`cp -R <dir>/. data_apps/<slug>/`), in beside `data_app.yaml` and `dist/`; check `.gitignore` is there before `npm install`. Without a repository, use any new directory, and once remote sync is set up, move the project (without `node_modules/`, `build/`, `dist/`, `.env.local` and a hand-written `data_app.yaml`) into `data_apps/<slug>/` before committing its source. Then install the SDK, then the rest:
 
 ```bash
 npm install @metabase/embedding-sdk-react@<major>-beta   # <major>: 66 for a version tag v1.66.x (`mb auth status --profile <name> --json | jq -r .version.tag`)
@@ -112,7 +112,7 @@ npm run typecheck && npm run build
 mb data-app set-bundle sales-overview
 ```
 
-`set-bundle` uploads `dist/index.js` (`--bundle` for another path) and replaces the app's bundle, live at once. A new app is on from the start; `mb data-app set-enabled <slug> false` turns it off, which only the user decides. An app turned off opens only in Data Studio → Data apps → the app → Overview; `/apps/<slug>` says "not found", for admins too. Give the user `<metabase-url>/apps/<slug>`.
+`set-bundle` uploads `build/index.js`, the file `npm run build` writes (`--bundle` for another path), and replaces the app's bundle, live at once. A new app is on from the start; `mb data-app set-enabled <slug> false` turns it off, which only the user decides. An app turned off opens only in Data Studio → Data apps → the app → Overview; `/apps/<slug>` says "not found", for admins too. Give the user `<metabase-url>/apps/<slug>`.
 
 A viewer needs one of their groups assigned to the app (otherwise "You don't have access"), which only the user can do (Data Studio → Data apps → the app → Permissions). A group reaches the app's collection and nothing more, so a viewer also needs data access to the tables its questions read.
 
@@ -133,5 +133,5 @@ A viewer needs one of their groups assigned to the app (otherwise "You don't hav
 
 - **Turn off:** `mb data-app set-enabled <slug> false`. **Rename:** `mb data-app update <slug> --body '{"display_name":"…"}'` (also `description`, `allowed_hosts`).
 - **Outdated:** an app Data Studio lists as _Outdated_ targets an older data-app contract: it won't open for anyone, and only admins see it, until it's migrated. Tell the user; don't change its code ad hoc.
-- **Move to another instance:** the app, its collection and what the collection holds are git-synced content. `mb git-sync export` (`git-sync`) writes `data_apps/<slug>/` with the bundle, and the collection under `collections/data_apps/`; importing the repository on the other instance recreates them with the same entity IDs, so the same `src/metabase.ts` works there. The first import there creates the app on, like `create`, open to admins until the user assigns groups; later imports keep its on/off state. The import doesn't check that the questions' tables are published on that instance, so the Library content they read goes in the same export: flag the Library root once (`mb git-sync add-collection <library-id>`, `git-sync`), or its metrics, measures and segments stay out of the repository; a data action needs its database's toggle on there too. Once the app is done, commit its source in `data_apps/<slug>/` on the branch you exported to, after the export. Pull the export branch: `git restore` a modified `dist/index.js`, then `git fetch`, `git switch <branch>`, `git pull --ff-only`. Then `git add data_apps/<slug>`, commit and push, and `mb git-sync import` whatever a cached `has-remote-changes` says, or the next export ends in `conflict`. The export writes `data_app.yaml` and `dist/index.js`, the bundle you uploaded; never edit or commit those two yourself, and when a fresh build changes `dist/index.js`, set the bundle and export again instead. The template's `.gitignore` keeps `node_modules/` and `.env.local` out. On a read-only synced instance only `set-enabled` works: creating, bundling, updating and deleting an app answer 403, and so does editing its collection; change it where it was built and export again.
+- **Move to another instance:** the app, its collection and what the collection holds are git-synced content. `mb git-sync export` (`git-sync`) writes `data_apps/<slug>/` with the bundle, and the collection under `collections/data_apps/`; importing the repository on the other instance recreates them with the same entity IDs, so the same `src/metabase.ts` works there. The first import there creates the app on, like `create`, open to admins until the user assigns groups; later imports keep its on/off state. The import doesn't check that the questions' tables are published on that instance, so the Library content they read goes in the same export: flag the Library root once (`mb git-sync add-collection <library-id>`, `git-sync`), or its metrics, measures and segments stay out of the repository; a data action needs its database's toggle on there too. Once the app is done, commit its source in `data_apps/<slug>/` on the branch you exported to, after the export. Pull the export branch: `git fetch`, `git switch <branch>`, `git pull --ff-only`. Then `git add data_apps/<slug>`, commit and push, and `mb git-sync import` whatever a cached `has-remote-changes` says, or the next export ends in `conflict`. The export writes `data_app.yaml` and `dist/index.js`, the bundle you uploaded; never edit those two, and leave them out of your commits unless the bundle ships through git (below). The template's `.gitignore` keeps `node_modules/`, `build/` and `.env.local` out. A bundle can instead ship through git, from CI say: `npm run build:ci` writes `dist/index.js`, and once that is committed and pushed, the next import loads it. On a read-only synced instance only `set-enabled` works: creating, bundling, updating and deleting an app answer 403, and so does editing its collection; change it where it was built and export again.
 - **Delete:** confirm with the user, then `mb data-app delete <slug> --yes` — it removes the app, its bundle, its collection and the questions and actions in it. The project directory stays: in a synced repository, the next export removes the app's `data_app.yaml`, bundle and collection files; after that export, switch and pull the same way, delete the source in `data_apps/<slug>/` in a commit of your own, push, and import.

package/skill-data/data-app/template/README.md

@@ -20,10 +20,14 @@ npm install
 ```bash
 npm run dev         # preview at http://localhost:5174, in the sandbox Metabase runs apps in
 npm run typecheck   # type-checks src/ and vite.config.ts
-npm run build       # builds dist/index.js
+npm run build       # builds build/index.js
 mb data-app typed-schema <slug> --out src/metabase.ts   # the app's queries and actions
-mb data-app set-bundle <slug>                     # makes dist/index.js the app's bundle
+mb data-app set-bundle <slug>                     # makes build/index.js the app's bundle
 ```
 
+To ship the bundle through git instead, for example from CI, run
+`npm run build:ci` and commit `dist/index.js`, the file the app's
+`data_app.yaml` names; the next git-sync import loads it.
+
 `npm run dev` reads `DATA_APP_MB_URL` and `DATA_APP_MB_API_KEY` from
 `.env.local`; `.env.local.example` lists them.

package/skill-data/data-app/template/gitignore

@@ -1,5 +1,5 @@
 node_modules
-dist
+build
 .env.local
 .vite
 .idea

package/skill-data/data-app/template/package.json

@@ -6,6 +6,7 @@
   "scripts": {
     "dev": "vite",
     "build": "vite build",
+    "build:ci": "vite build --outDir dist",
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {

package/skill-data/data-app-actions/SKILL.md

@@ -1,15 +1,15 @@
 ---
 name: data-app-actions
-description: Make a Metabase data app write data — an action in the app's collection, its typed definition in `src/metabase.ts`, and the `useAction` hook from `@metabase/embedding-sdk-react/data-app` behind a form or a button, with inputs typed from each parameter, the server's error shown as it comes, and every affected query refreshed. Triggers — "a form that saves a row", "a button that updates a record", "delete an entry from the app", "submit doesn't refresh the list", "the action fails in the app". Creating the action itself is `data-action`; reads are `data-app-data`.
+description: Make a Metabase data app write data — an action in the app's collection (a table action that inserts, updates or deletes a row, or a SQL query action), its typed definition in `src/metabase.ts`, and the `useAction` hook from `@metabase/embedding-sdk-react/data-app` behind a form or a button, with inputs typed from each parameter, the server's error shown as it comes, and every affected query refreshed. Triggers — "a form that saves a row", "a button that updates a record", "delete an entry from the app", "submit doesn't refresh the list", "the action fails in the app". Creating the action itself is `data-action`; reads are `data-app-data`.
 allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
 requires: [dataApps]
 ---
 
 # Writes in a data app
 
-An **action** is a saved, parameterized SQL write — `INSERT`, `UPDATE` or `DELETE`. A data app runs only the actions in **the app's collection** (`data-app`, _Create the app_).
+An **action** is a table action, which inserts, updates or deletes one row of a table, or a query action, a saved SQL write (`data-action`). A data app runs only the actions in **the app's collection** (`data-app`, _Create the app_).
 
-1. Draft the action as `data-action` describes — the database must allow actions — with `collection_id` the app's collection. Show the user its SQL and parameters, and create it once they agree.
+1. Draft the action as `data-action` describes, with `collection_id` the app's collection: the database must allow actions, and a table action's table must be published to the Library, as every table the app reads is. Pick the type as `data-action`, _Pick the type_, says. Show the user the table and kind, or the SQL, and the parameters; create it once they agree.
 2. Regenerate `src/metabase.ts` (`data-app-data`).
 3. Pass `actions.<name>` from it to `useAction`.
 
@@ -29,7 +29,7 @@ const { execute, isExecuting, result, error, reset } = useAction(actions.setOrde
 - **Import it from `/data-app`.** The main `@metabase/embedding-sdk-react` entry exports the general SDK `useAction`, which takes raw ids and isn't typed from the definition. Write no generics: the definition types `execute`'s keys and values.
 - `execute(params)` resolves to the response body; on failure it both throws and sets `error`. It resolves to `null` without sending anything while the SDK is still starting, so guard a call that can happen at mount. It never runs on its own and has no `enabled`: return early in the handler to skip it.
 - `isExecuting` is true until it settles: disable the trigger and show progress, so a double click can't send twice.
-- `result` is the last response, `null` before the first call; `result?.["rows-affected"]` is a quick confirmation. `reset()` clears `result` and `error`, for example when the user dismisses a message.
+- `result` is the last response, `null` before the first call; a query action answers `{"rows-affected": <n>}`, a table action `rows-updated`, `rows-deleted` or `created-row` (`data-action`, _Table actions_). `reset()` clears `result` and `error`, for example when the user dismisses a message.
 
 ## A form
 
@@ -76,9 +76,15 @@ export function NoteForm({ orderId, onSaved }: { orderId: number; onSaved: () =>
 | `Date`    | `type="date"`, or `datetime-local` when a time is expected |
 | `unknown` | `type="text"`, converted at the call                       |
 
+**Table actions.** The parameter slugs are the table's column names, slugified.
+
+- **Insert** (`row/create`): every column but an auto-increment key. `result["created-row"]` holds the new row's parameter columns, its key among them.
+- **Update** (`row/update`): the key and every other column, `required` on each `NOT NULL` one without a default. Start the form from the row's current values, read by the query on screen, and send them all. A `null` is dropped, so an update can't clear a column.
+- **Delete** (`row/delete`): the key only. Ask the viewer to confirm first.
+
 **Validation** is `required` on each required parameter and nothing else — no length, range or format checks of your own. Disable submit from the browser's verdict, `form.checkValidity()`, never from hand-rolled checks. Anything stricter comes back from the server.
 
-**Errors.** `error` is `{ status?, data: { message?, errors? }, isCancelled }` — read it without a cast. A failing SQL action comes back as a 500 whose `data.message` wraps the driver's text (`Error executing Action: …`): show it as it comes, in a `white-space: pre-wrap` element, since driver messages span lines — never "Something went wrong", `String(error)` or a friendlier paraphrase. `error.data.errors?.[parameterSlug]`, when present, goes beside its field (`aria-invalid` on the input).
+**Errors.** `error` is `{ status?, data: { message?, errors? }, isCancelled }` — read it without a cast. A failing query action comes back as a 500 whose `data.message` wraps the driver's text (`Error executing Action: …`): show it as it comes, in a `white-space: pre-wrap` element, since driver messages span lines — never "Something went wrong", `String(error)` or a friendlier paraphrase. A table action's refusals and constraint errors are 400s, shown the same way (`Sorry, the row you're trying to update doesn't exist`). `error.data.errors?.[parameterSlug]`, when present, goes beside its field (`aria-invalid` on the input).
 
 ## Refresh
 

package/skill-data/mbql/SKILL.md

@@ -49,7 +49,7 @@ An options key the server doesn't know is rejected or silently dropped, never ap
 - `filters` are ANDed; OR is `["or", {}, a, b, …]`. Multi-value is `["in", {}, <field>, "a", "b"]` / `["not-in", …]`.
 - Relative dates: `["time-interval", {}, <field>, -30, "day"]`, `["time-interval", {}, <field>, "current", "month"]`. A stated year or date range is absolute: `["between", {}, <field>, "2024-01-01", "2024-12-31"]` (inclusive).
 - `aggregation` is a list of aggregation clauses, `breakout` a list of refs. "only / where X" is a filter; "by / per / over time" is a breakout.
-- Name every aggregation a later stage, a chart setting or a target table reads: `["sum", {"name": "revenue", "display-name": "Revenue"}, <field>]`. Unnamed, it is `count`, `sum`, `avg`, … and a second `sum` is `sum_2`.
+- An unnamed aggregation is `count`, `sum`, `avg`, …, a breakout keeps its field's name, and a repeat gets a suffix that moves when clauses change: a second `sum` is `sum_2`, a second `ID` breakout (another table's) `ID_2`. When a later stage, a chart setting or a target table reads such a column, set `"name"` in the clause's options: `["sum", {"name": "revenue", "display-name": "Revenue"}, <field>]`, `["field", {"name": "product_id", "source-field": 11}, 12]`.
 - An aggregation can be arithmetic over aggregations: `["/", {"name": "aov"}, ["sum", {}, <field>], ["count", {}]]`.
 - Date arithmetic is `["datetime-diff", {}, a, b, "day"]`.
 
@@ -122,7 +122,7 @@ A later stage reads the previous stage's output by column name, with the column'
 ]
 ```
 
-The names and base types are the `name` and `base_type` of the columns the earlier stages return: run them once (`mb query … --json`, `data.cols`) and copy both. A breakout keeps its field's name (`CREATED_AT`, even when bucketed); an aggregation has the `name` you gave it.
+The names and base types are the `name` and `base_type` of the columns the earlier stages return: run them once (`mb query … --json`, `data.cols`) and copy both. A breakout keeps its field's name (`CREATED_AT`, even when bucketed) and an aggregation its operator's, unless its options set `name`.
 
 **Window:** `offset` sits in `aggregation` and reads another breakout row. Month-over-month against a monthly breakout:
 

package/dist/api-key-DJfhPe4x.mjs

@@ -1,13 +0,0 @@
-import { t as defineCommandGroup } from "./group--6adAsqG.mjs";
-//#region src/commands/api-key/index.ts
-var api_key_default = defineCommandGroup({
-	name: "api-key",
-	description: "Manage Metabase API keys",
-	subCommands: {
-		list: () => import("./list-Dz2YVD7m.mjs").then((mod) => mod.default),
-		create: () => import("./create-cpxnjNMC.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-Bw8CMa_A.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { api_key_default as default };

package/dist/card-nOX_QJ9u.mjs

@@ -1,25 +0,0 @@
-import { t as defineCommandGroup } from "./group--6adAsqG.mjs";
-//#region src/commands/card/index.ts
-var card_default = defineCommandGroup({
-	name: "card",
-	description: "Manage Metabase cards (questions, models, metrics)",
-	skills: [{
-		skill: "mbql",
-		purpose: "author the dataset_query"
-	}, {
-		skill: "visualization",
-		purpose: "choose display and visualization_settings"
-	}],
-	subCommands: {
-		list: () => import("./list-DDV5PylU.mjs").then((mod) => mod.default),
-		get: () => import("./get-CEreA2oN.mjs").then((mod) => mod.default),
-		query: () => import("./query-C8w04b4F.mjs").then((mod) => mod.default),
-		alerts: () => import("./alerts-DWVmtHEJ.mjs").then((mod) => mod.default),
-		create: () => import("./create-BfgTvPvI.mjs").then((mod) => mod.default),
-		update: () => import("./update-BemK_tZ_.mjs").then((mod) => mod.default),
-		verify: () => import("./verify-CMTrDvAW.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-BZxa5zJk.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { card_default as default };