@metabase/cli 0.5.8 → 0.5.9

package/dist/{yaml-BthVUNj3.mjs → yaml-Ctv1l2-P.mjs}

@@ -35,13 +35,12 @@ function parseYamlResult(input, schema, opts = {}) {
 	};
 }
 const YAML_1_1_LINE_BREAKS = /[\u0085\u2028\u2029]/;
-function parseMetabaseYaml(input, source) {
-	if (YAML_1_1_LINE_BREAKS.test(input)) throw new ValidationError(`${source}: holds U+0085, U+2028 or U+2029, which Metabase reads as a line break and this check does not; remove the character`, {
-		source,
-		zodIssues: []
-	});
+function parseAs(input, source, version) {
 	try {
-		return parse(input, { merge: true });
+		return parse(input, {
+			merge: true,
+			version
+		});
 	} catch (error) {
 		throw new ValidationError(`${source}: invalid YAML: ${errorMessage(error)}`, {
 			source,
@@ -49,5 +48,15 @@ function parseMetabaseYaml(input, source) {
 		});
 	}
 }
+function parseMetabaseYaml(input, source) {
+	if (YAML_1_1_LINE_BREAKS.test(input)) throw new ValidationError(`${source}: holds U+0085, U+2028 or U+2029, which Metabase reads as a line break and this check does not; remove the character`, {
+		source,
+		zodIssues: []
+	});
+	return {
+		yaml12: parseAs(input, source, "1.2"),
+		yaml11: parseAs(input, source, "1.1")
+	};
+}
 //#endregion
 export { parseYaml as n, parseMetabaseYaml as t };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metabase/cli",
-  "version": "0.5.8",
+  "version": "0.5.9",
   "description": "Metabase CLI",
   "license": "AGPL-3.0",
   "repository": {

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

@@ -12,17 +12,20 @@ A **data app** is a React app built into one JavaScript bundle, which Metabase r
 The work, in order:
 
 1. Create the app on the instance.
-2. Scaffold the project and install the SDK.
+2. Scaffold the project in the synced git repository and install the SDK.
 3. Give it data: questions over the Library's published tables and metrics in the app's collection, then `src/metabase.ts` (`data-app-data`); writes are `data-app-actions`.
 4. Start the dev preview (_Dev preview_), then write the UI under `src/` (`data-app-ui`; filter controls in `data-app-filters`).
-5. Build and publish (_Build and publish_).
+5. Build, test, and push the source and the bundle together (_Build and publish_).
 
-For every later change: first pass the checks in _An existing project_ (_Scaffold and install_), then regenerate `src/metabase.ts` if the app's collection changed, then build and set the bundle; in a synced repository, then export and commit the source as in _Move to another instance_. Metabase receives only the built bundle; the source stays in the project directory, which is the app's folder in the synced git repository when there is one (_Scaffold and install_).
+For every later change: first pass the checks in _An existing project_ (_Scaffold and install_), then regenerate `src/metabase.ts` if the app's collection changed, then build and publish (_Build and publish_). The bundle reaches Metabase only through git: a git-sync import loads the `dist/index.js` committed in the app's folder.
 
 ## Before you start
 
 - Use an **admin** profile — only admins create apps and write the app's collection. `mb auth status --profile <name> --json | jq .user.isAdmin` prints `true` for one, and every command below takes that `--profile`; otherwise ask the user for an admin profile (`mb auth list`).
 - Run `mb data-app list`. A failure means the instance has no data apps: stop and tell the user.
+- The app ships through the instance's synced git repository. Check both ends first; if either fails, stop and tell the user which, changing nothing:
+  - `mb git-sync status --profile <name> --json` reports `remote_configured: true` and `sync_type: "read-write"`.
+  - The working folder is a clone of it: `git rev-parse --show-toplevel` succeeds, and `git remote -v` lists the repository `mb setting get remote-sync-url --profile <name>` names, in HTTPS or SSH form. That top level is `<repo>` below.
 - Settle the **slug**, the `/apps/<slug>` URL: lowercase letters, digits and single dashes (`sales-overview`), at most 100 characters. If the app's purpose is unclear, ask "what's this app for?" and propose one.
 
 ## Create the app
@@ -39,14 +42,14 @@ 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/`, `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:
+`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. The directory is `data_apps/<slug>/` in `<repo>`, 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`. 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`)
-npm install && npm run typecheck && npm run build
+npm install && npm run typecheck
 ```
 
-Skip the SDK line when `package.json` already points it at a local build (`file:` or `link:`), and never install `latest`. A tag without a version number, such as `vLOCAL_DEV`, is a development build: ask the user which SDK build to install. The starter renders "Hello, data app".
+Skip the SDK line when `package.json` already points it at a local build (`file:` or `link:`), and never install `latest`. A tag without a version number, such as `vLOCAL_DEV`, is a development build: ask the user which SDK build to install. The starter renders "Hello, data app". Build only in _Build and publish_, after the export: both write `dist/index.js`.
 
 The template is the bundle contract. Don't edit `package.json` by hand, and never rewrite `vite.config.ts`, `tsconfig.json` or `src/index.tsx`: `vite.config.ts` stays `export default dataAppConfig()` (its only option is `port`), and `src/index.tsx` default-exports the `DataAppFactory` — change it only to add a `providerProps` key. Metabase and the dev preview each wrap the app in a `<MetabaseProvider>`, so the app never renders one.
 
@@ -56,11 +59,11 @@ The template is the bundle contract. Don't edit `package.json` by hand, and neve
 - `src/index.tsx` default-exports a `DataAppFactory` that takes no arguments and returns `{ component, providerProps? }`.
 - `npm ls react react-dom` exits 0 and reports 19.x. A 19.x it marks `invalid` fails. This check applies whatever the instance or SDK version; to skip it, ask the user first.
 
-Fix a failed React check yourself, before any other change: upgrade `react`, `react-dom`, `@types/react` and `@types/react-dom` to 19 until `npm run typecheck && npm run build` passes and the diagnostics feed is clean (_Dev preview_); then publish (_Build and publish_). If either other check fails, stop: tell the user the project differs from the template, and ask whether to scaffold a fresh project and port the code over, or go on at their own risk.
+Fix a failed React check yourself, before any other change: upgrade `react`, `react-dom`, `@types/react` and `@types/react-dom` to 19 until `npm run typecheck` passes and the diagnostics feed is clean (_Dev preview_); then publish (_Build and publish_). If either other check fails, stop: tell the user the project differs from the template, and ask whether to scaffold a fresh project and port the code over, or go on at their own risk.
 
 ## Dev preview
 
-`npm run dev` serves the app at `http://localhost:5174` — or the next free port, in Vite's `Local:` line — through the same sandbox Metabase uses. An edit under `src/` rebuilds the bundle and remounts the app, resetting component state. The preview reads `DATA_APP_MB_URL` and an admin `DATA_APP_MB_API_KEY` from `.env.local` beside `package.json`. Write a new key straight into that file, never into the chat or the terminal:
+`npm run dev` serves the app at `http://localhost:5174` — or the next free port, in Vite's `Local:` line — through the same sandbox Metabase uses. An edit under `src/` rebuilds the bundle and remounts the app, resetting component state. The preview reads `DATA_APP_MB_URL` and an admin `DATA_APP_MB_API_KEY` from `.env.local` beside `package.json`. Create that key only on the user's yes: ask with `AskUserQuestion` ("Create an admin API key `data-app <slug> dev` for the preview? It goes in `.env.local` and is deleted at handoff."). On a no, the user fills in `.env.local` from `.env.local.example`. Write a new key straight into that file, never into the chat or the terminal:
 
 ```bash
 ( umask 077
@@ -102,7 +105,7 @@ curl -s "http://localhost:5174/__data-app/diagnostics?startEventId=0"
 - `clients: 0` means no tab is open, so empty `entries` prove nothing.
 - Before an edit, note `nextEventId`; after it, read again with that value as `startEventId`.
 - The feed answers for the running bundle: entries from replaced builds are counted in `staleEntries`, and anything still broken reports again under the new `buildId` (`?includeStale=true` shows the withheld ones). A failed build doesn't advance `buildId` and doesn't reach the feed — read the `npm run dev` terminal.
-- Quote `summary` as it is when you report it, and follow `hint` when there is one — except that you never add the Metabase URL to `allowed_hosts`, and in a synced repository you set `allowed_hosts` with `mb data-app update`, export, and pull the export branch (_Move to another instance_) instead of editing `data_app.yaml`. A `frame-src` or `form-action` block can't be lifted in the preview (`data-app-ui`). The feed keeps the last 200 entries; `curl -X DELETE …/__data-app/diagnostics` clears it.
+- Quote `summary` as it is when you report it, and follow `hint` when there is one — except that you never add the Metabase URL to `allowed_hosts`, and you set `allowed_hosts` with `mb data-app update`, then export and pull (_Build and publish_, step 1), instead of editing `data_app.yaml`. A `frame-src` or `form-action` block can't be lifted in the preview (`data-app-ui`). The feed keeps the last 200 entries; `curl -X DELETE …/__data-app/diagnostics` clears it.
 
 | `kind`                             | Fix                                                                                                                 |
 | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
@@ -113,12 +116,15 @@ curl -s "http://localhost:5174/__data-app/diagnostics?startEventId=0"
 
 ## Build and publish
 
-```bash
-npm run typecheck && npm run build
-mb data-app set-bundle sales-overview
-```
+Build the bundle last, test it in the dev preview, then push it with the source in one commit:
+
+1. Export the app's `data_app.yaml` and the questions and actions in its collection: `mb git-sync export` (`git-sync`), then in `<repo>` `git fetch`, `git switch <branch>`, `git pull --ff-only`.
+2. `npm run typecheck && npm run build`, which overwrites the exported `dist/index.js`.
+3. With `npm run dev` running and a preview tab open, read the diagnostics feed (_Dev preview_) with every page mounted; fix what it reports and build again.
+4. Commit `data_apps/<slug>/` — the source and `dist/index.js` together — and push.
+5. `mb git-sync import --profile <name>`, whatever a cached `has-remote-changes` says. The new bundle is live at once.
 
-`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 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.
 
@@ -126,7 +132,7 @@ A viewer needs one of their groups assigned to the app (otherwise "You don't hav
 
 | Symptom                                                             | Fix                                                                                                                    |
 | ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| `set-bundle`: bundle not found                                      | Run `npm run build` in the project directory first.                                                                    |
+| The app still runs the old bundle                                   | `dist/index.js` was built before the export's pull, or isn't in the pushed commit: build, commit, push, import.        |
 | Blank app, `Bundle did not assign a function to __dataAppFactory__` | `src/index.tsx` must `export default` the factory and nothing else; otherwise the diagnostics feed has the real error. |
 | "Failed to fetch the user, the session might be invalid."           | A bad key in `.env.local`, or CORS (_Dev preview_).                                                                    |
 | A bundle of several MB                                              | `vite.config.ts` no longer uses `dataAppConfig()`, or the SDK isn't the `<major>-beta` tag.                            |
@@ -139,5 +145,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 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.
+- **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. Never edit `data_app.yaml`; `dist/index.js` changes only through `npm run build` (_Build and publish_). The template's `.gitignore` keeps `node_modules/` and `.env.local` out. On a read-only synced instance only `set-enabled` works: creating, updating and deleting an app answer 403, and so does editing its collection; change it where it was built, push, and import there.
+- **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: 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,14 +20,13 @@ 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 build/index.js
+npm run build       # builds dist/index.js, the app's bundle
 mb data-app typed-schema <slug> --out src/metabase.ts   # the app's queries and actions
-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.
+The bundle ships through git: commit `dist/index.js` (the file
+`data_app.yaml` names) with the source and push; 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,4 @@
 node_modules
-build
 .env.local
 .vite
 .idea

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

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

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

@@ -38,7 +38,7 @@ Everything here runs inside the sandbox, the same in the dev preview as in Metab
 | `navigator.geolocation` and other device APIs                                                              | Nothing.                                                                                  |
 | Key, input, composition and clipboard listeners (`keydown`, `paste`, `input`, …) on `window` or `document` | A React handler (`onKeyDown`, `onPaste`, …) on your own element.                          |
 
-**External APIs.** A raw `fetch` reaches only the origins in the app's `allowed_hosts`, exact or with a `*.` subdomain wildcard: `mb data-app update <slug> --body '{"allowed_hosts":["https://api.example.com"]}'`. The preview reads the `allowed_hosts:` list in `data_app.yaml` beside `package.json`: in a synced repository that file is the app's exported manifest, so export again and pull the export branch (`data-app`, _Move to another instance_) to refresh it rather than writing it; without one, write the list there yourself. Then restart `npm run dev`. Never list the Metabase URL. In Metabase the same list governs `<iframe src>` and native `<form action>` submits, and the target must allow framing; the preview blocks both. Use `<form onSubmit>` with `preventDefault`: a native submit navigates the app away.
+**External APIs.** A raw `fetch` reaches only the origins in the app's `allowed_hosts`, exact or with a `*.` subdomain wildcard: `mb data-app update <slug> --body '{"allowed_hosts":["https://api.example.com"]}'`. The preview reads the `allowed_hosts:` list in `data_app.yaml` beside `package.json`, the app's exported manifest: refresh it by exporting and pulling the export branch (`data-app`, _Build and publish_, step 1), never by writing it. Then restart `npm run dev`. Never list the Metabase URL. In Metabase the same list governs `<iframe src>` and native `<form action>` submits, and the target must allow framing; the preview blocks both. Use `<form onSubmit>` with `preventDefault`: a native submit navigates the app away.
 
 ## Layout
 

package/skill-data/transform/SKILL.md

@@ -271,6 +271,6 @@ mb transform-job set-active false --profile <name> --json  # disable every job a
 
 <!-- /requires -->
 
-Every job row carries `active`; it is `null` on a server that cannot switch jobs off, where every job runs on schedule.
+Every job row carries `active`; it is `null` on a server that cannot switch jobs off, where every job runs on schedule. A job with `active: false` never runs on schedule, and a fresh install of a newer server starts the built-in jobs that no transform uses that way: before relying on one, check `active`, and turn it on only with the user's yes (`transform-job update <id> --body '{"active":true}'`, admin only).
 
 `transform-job run` is fire-and-forget — it returns `{message, started, run_id}` immediately (both `null` when the server does not number job runs: the request was accepted and whether a run started is unsaid), with no per-job-run polling (no `--wait`). Most ad-hoc agent work is one-off `transform run`, not job authoring.

package/dist/api-key-Cia6SHQ9.mjs

@@ -1,13 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.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-mRSKPKoO.mjs").then((mod) => mod.default),
-		create: () => import("./create-Dm8BvbsU.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-D_l7FRE6.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { api_key_default as default };

package/dist/card-C-KsmoJW.mjs

@@ -1,25 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.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-DAdWd8gn.mjs").then((mod) => mod.default),
-		get: () => import("./get-3XwqrjxC.mjs").then((mod) => mod.default),
-		query: () => import("./query-B4xK9j0u.mjs").then((mod) => mod.default),
-		alerts: () => import("./alerts-C7vJ-NAI.mjs").then((mod) => mod.default),
-		create: () => import("./create-C6c-clLK.mjs").then((mod) => mod.default),
-		update: () => import("./update-BGFGng3a.mjs").then((mod) => mod.default),
-		verify: () => import("./verify-BSlj7S_E.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-CuygjxgQ.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { card_default as default };

package/dist/collection-DsNRlVcN.mjs

@@ -1,21 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/collection/index.ts
-var collection_default = defineCommandGroup({
-	name: "collection",
-	description: "Manage Metabase collections",
-	skills: [{
-		skill: "core",
-		purpose: "collection ref forms and the transforms namespace"
-	}],
-	subCommands: {
-		list: () => import("./list-CcfGHN19.mjs").then((mod) => mod.default),
-		get: () => import("./get-DvPgnqAA.mjs").then((mod) => mod.default),
-		items: () => import("./items-B1DXzdwg.mjs").then((mod) => mod.default),
-		tree: () => import("./tree-BDhm4E_W.mjs").then((mod) => mod.default),
-		create: () => import("./create-zALsdMhF.mjs").then((mod) => mod.default),
-		update: () => import("./update-DU3jpGps.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-TBPRGm7s.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { collection_default as default };

package/dist/dashboard-BRQtw_1e.mjs

@@ -1,35 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/dashboard/index.ts
-var dashboard_default = defineCommandGroup({
-	name: "dashboard",
-	description: "Manage Metabase dashboards",
-	skills: [
-		{
-			skill: "dashboard",
-			purpose: "wiring filters, linked filters, cross-filtering, click behavior, tabs"
-		},
-		{
-			skill: "visualization",
-			purpose: "dashcard display and visualization_settings"
-		},
-		{
-			skill: "core",
-			purpose: "the 24-column dashcard grid layout"
-		}
-	],
-	subCommands: {
-		list: () => import("./list-DZLGnsAK.mjs").then((mod) => mod.default),
-		get: () => import("./get-CU6AWbqL.mjs").then((mod) => mod.default),
-		cards: () => import("./cards-D6jWz0N9.mjs").then((mod) => mod.default),
-		"parameter-values": () => import("./parameter-values-to5u_-2n.mjs").then((mod) => mod.default),
-		subscriptions: () => import("./subscriptions-Cu4km2CN.mjs").then((mod) => mod.default),
-		create: () => import("./create-lHqpAdxg.mjs").then((mod) => mod.default),
-		update: () => import("./update-BenGrugz.mjs").then((mod) => mod.default),
-		"update-dashcard": () => import("./update-dashcard-BU3Wqcnf.mjs").then((mod) => mod.default),
-		copy: () => import("./copy-D-VIVVB1.mjs").then((mod) => mod.default),
-		verify: () => import("./verify-BwodYH0C.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-CyhH-395.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { dashboard_default as default };

package/dist/data-action-Bm6QMyV0.mjs

@@ -1,24 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/data-action/index.ts
-var data_action_default = defineCommandGroup({
-	name: "data-action",
-	description: "Manage Metabase data actions",
-	skills: [{
-		skill: "data-action",
-		purpose: "author and run data actions"
-	}, {
-		skill: "native-sql",
-		purpose: "the data action's native query and its template tags"
-	}],
-	subCommands: {
-		list: () => import("./list-BSvQ0AT_.mjs").then((mod) => mod.default),
-		get: () => import("./get-DJeeXbwj.mjs").then((mod) => mod.default),
-		create: () => import("./create-HNchuWpj.mjs").then((mod) => mod.default),
-		update: () => import("./update-DT8KwBxO.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-CmhV_hlP.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-CxL5okLN.mjs").then((mod) => mod.default),
-		execute: () => import("./execute-C9foK2IU.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { data_action_default as default };

package/dist/dependency-B0KmVz2u.mjs

@@ -1,15 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/dependency/index.ts
-var dependency_default = defineCommandGroup({
-	name: "dependency",
-	description: "Trace what Metabase content depends on and what depends on it",
-	subCommands: {
-		graph: () => import("./graph-B2YkV2oX.mjs").then((m) => m.default),
-		dependents: () => import("./dependents-B4V8pDYq.mjs").then((m) => m.default),
-		broken: () => import("./broken-BbpNq5WG.mjs").then((m) => m.default),
-		unreferenced: () => import("./unreferenced-B2nDcQ7m.mjs").then((m) => m.default),
-		breaking: () => import("./breaking-VMUrgVVE.mjs").then((m) => m.default)
-	}
-});
-//#endregion
-export { dependency_default as default };

package/dist/document--zYZP-u3.mjs

@@ -1,20 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/document/index.ts
-var document_default = defineCommandGroup({
-	name: "document",
-	description: "Manage Metabase documents",
-	skills: [{
-		skill: "document",
-		purpose: "author the ProseMirror document body"
-	}],
-	subCommands: {
-		list: () => import("./list-DX5SmBCQ.mjs").then((mod) => mod.default),
-		get: () => import("./get-m-vpr7GN.mjs").then((mod) => mod.default),
-		create: () => import("./create-DcDyXL4g.mjs").then((mod) => mod.default),
-		update: () => import("./update-CWzmrGS_.mjs").then((mod) => mod.default),
-		copy: () => import("./copy-BeD_fk5J.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-5pjvTser.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { document_default as default };

package/dist/field-Bk09crKC.mjs

@@ -1,21 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/field/index.ts
-var field_default = defineCommandGroup({
-	name: "field",
-	description: "Manage Metabase fields",
-	skills: [{
-		skill: "metadata",
-		purpose: "semantic types, FK targets, visibility, dropdown behavior"
-	}],
-	subCommands: {
-		get: () => import("./get-BAGQ-bvt.mjs").then((m) => m.default),
-		values: () => import("./values-BVtqwRlR.mjs").then((m) => m.default),
-		summary: () => import("./summary-3Av5251t.mjs").then((m) => m.default),
-		update: () => import("./update-BMHPp3nt.mjs").then((m) => m.default),
-		search: () => import("./search-CyyySVTz.mjs").then((m) => m.default),
-		remapping: () => import("./remapping-DT305P-k.mjs").then((m) => m.default),
-		"set-sensitivity": () => import("./set-sensitivity-DDzrkjdv.mjs").then((m) => m.default)
-	}
-});
-//#endregion
-export { field_default as default };

package/dist/git-sync-DMyH3Y85.mjs

@@ -1,29 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/git-sync/index.ts
-var git_sync_default = defineCommandGroup({
-	name: "git-sync",
-	description: "Sync Metabase content with a git remote",
-	skills: [{
-		skill: "git-sync",
-		purpose: "import/export round-trip and dirty checks"
-	}],
-	subCommands: {
-		status: () => import("./status-CJLd6Uk6.mjs").then((mod) => mod.default),
-		"is-dirty": () => import("./is-dirty-Bud2wuxQ.mjs").then((mod) => mod.default),
-		"has-remote-changes": () => import("./has-remote-changes-ChMSjhmC.mjs").then((mod) => mod.default),
-		dirty: () => import("./dirty-DKj4ScBN.mjs").then((mod) => mod.default),
-		"current-task": () => import("./current-task-GG6JqfGp.mjs").then((mod) => mod.default),
-		"cancel-task": () => import("./cancel-task-DWiicb_t.mjs").then((mod) => mod.default),
-		wait: () => import("./wait-DZclBI3D.mjs").then((mod) => mod.default),
-		import: () => import("./import-CNpN9iS0.mjs").then((mod) => mod.default),
-		export: () => import("./export-B8QyoPWP.mjs").then((mod) => mod.default),
-		"export-preflight": () => import("./export-preflight-BQbwxyoJ.mjs").then((mod) => mod.default),
-		stash: () => import("./stash-d3FtnE2F.mjs").then((mod) => mod.default),
-		branches: () => import("./branches-BM0L124r.mjs").then((mod) => mod.default),
-		"create-branch": () => import("./create-branch-C8arQT4M.mjs").then((mod) => mod.default),
-		"add-collection": () => import("./add-collection-DIrpeq9O.mjs").then((mod) => mod.default),
-		"remove-collection": () => import("./remove-collection-Bsme1OBA.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { git_sync_default as default };

package/dist/glossary-CcRGJaVi.mjs

@@ -1,14 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/glossary/index.ts
-var glossary_default = defineCommandGroup({
-	name: "glossary",
-	description: "Manage the Metabase glossary of business terms",
-	subCommands: {
-		list: () => import("./list-CAAvhl9h.mjs").then((mod) => mod.default),
-		create: () => import("./create-BlmRvuQg.mjs").then((mod) => mod.default),
-		update: () => import("./update-B9iHHoJB.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-Dkwk2mZH.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { glossary_default as default };

package/dist/set-bundle-B-qAvkDo.mjs

@@ -1,40 +0,0 @@
-import { dt as outputFlags, ft as profileFlag, ot as connectionFlags, u as renderSummary } from "./cli.mjs";
-import { t as defineMetabaseCommand } from "./runtime-Dd2uBKqN.mjs";
-import { t as DataApp } from "./data-app-BUW-HlUo.mjs";
-import { t as dataAppView } from "./data-app-Blz61mG5.mjs";
-import { n as slugArg, t as parseSlug } from "./slug-COdwq63O.mjs";
-import { n as readBundle, t as DEFAULT_BUNDLE_PATH } from "./data-app-project-CHYcJRrU.mjs";
-//#region src/commands/data-app/set-bundle.ts
-var set_bundle_default = defineMetabaseCommand({
-	meta: {
-		name: "set-bundle",
-		description: "Replace a data app's bundle with a built one"
-	},
-	details: "Reads the built bundle (`npm run build` writes `build/index.js`) and makes it the bundle Metabase serves at /apps/<slug>, at once. A new app is enabled; viewers reach it once a group is assigned. A disabled app opens only in Data Studio (Data apps → the app → Overview).",
-	skills: [{
-		skill: "data-app",
-		purpose: "build and publish an app"
-	}],
-	requires: ["dataApp.replaceBundle"],
-	args: {
-		...outputFlags,
-		...profileFlag,
-		...connectionFlags,
-		...slugArg,
-		bundle: {
-			type: "string",
-			description: "Built bundle file",
-			default: DEFAULT_BUNDLE_PATH
-		}
-	},
-	outputSchema: DataApp,
-	examples: ["mb data-app set-bundle sales-overview", "mb data-app set-bundle sales-overview --bundle out/index.js"],
-	async run({ args, ctx, getClient }) {
-		const slug = parseSlug(args.slug);
-		const bundle = await readBundle(args.bundle);
-		const app = await (await getClient()).dataApp.replaceBundle(slug, bundle);
-		renderSummary(app, dataAppView, `Set the bundle of data app ${slug}; it is ${app.enabled ? `served at /apps/${slug}` : "disabled, so it opens only in Data Studio"}.`, ctx);
-	}
-});
-//#endregion
-export { set_bundle_default as default };

package/dist/snippet-Czzma-M2.mjs

@@ -1,19 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/snippet/index.ts
-var snippet_default = defineCommandGroup({
-	name: "snippet",
-	description: "Manage Metabase native query snippets",
-	skills: [{
-		skill: "core",
-		purpose: "native-SQL snippets and body input"
-	}],
-	subCommands: {
-		list: () => import("./list-BVz0N0g_.mjs").then((mod) => mod.default),
-		get: () => import("./get-CtRJUybv.mjs").then((mod) => mod.default),
-		create: () => import("./create-DF7nC9qW.mjs").then((mod) => mod.default),
-		update: () => import("./update-CFLJWHOT.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-Cy6RUJaD.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { snippet_default as default };

package/dist/table-CwfF6ZTZ.mjs

@@ -1,26 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/table/index.ts
-var table_default = defineCommandGroup({
-	name: "table",
-	description: "Manage Metabase tables",
-	skills: [{
-		skill: "metadata",
-		purpose: "table and column metadata, semantic types, visibility"
-	}],
-	subCommands: {
-		list: () => import("./list-Dk3upD11.mjs").then((m) => m.default),
-		get: () => import("./get-DG5fPl-S.mjs").then((m) => m.default),
-		fields: () => import("./fields-TE3PnmwW.mjs").then((m) => m.default),
-		fks: () => import("./fks-B41Re5dt.mjs").then((m) => m.default),
-		update: () => import("./update-BS-E7QLh.mjs").then((m) => m.default),
-		"sync-schema": () => import("./sync-schema-BYJuUBsG.mjs").then((m) => m.default),
-		"rescan-values": () => import("./rescan-values-C0P0upEB.mjs").then((m) => m.default),
-		"discard-values": () => import("./discard-values-5l91z3Dy.mjs").then((m) => m.default),
-		"bulk-edit": () => import("./bulk-edit-B9-XH592.mjs").then((m) => m.default),
-		"bulk-sync-schema": () => import("./bulk-sync-schema-CorpcAjz.mjs").then((m) => m.default),
-		"bulk-rescan-values": () => import("./bulk-rescan-values-CsWKirZw.mjs").then((m) => m.default),
-		"bulk-discard-values": () => import("./bulk-discard-values-Cohox-Zb.mjs").then((m) => m.default)
-	}
-});
-//#endregion
-export { table_default as default };

package/dist/timeline-C4WCMzDX.mjs

@@ -1,21 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/timeline/index.ts
-var timeline_default = defineCommandGroup({
-	name: "timeline",
-	description: "Manage Metabase timelines (event annotations for time-series charts)",
-	skills: [{
-		skill: "core",
-		purpose: "collection scoping — events render only on questions in the timeline's collection"
-	}],
-	subCommands: {
-		list: () => import("./list-BeaA7gQ7.mjs").then((mod) => mod.default),
-		get: () => import("./get-BrhIHZYg.mjs").then((mod) => mod.default),
-		events: () => import("./events-CE80dTib.mjs").then((mod) => mod.default),
-		create: () => import("./create-MmZVmRsH.mjs").then((mod) => mod.default),
-		update: () => import("./update-pzu78yZB.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-BrGj2yoP.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-YKX2HilI.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { timeline_default as default };

package/dist/transform-job-SQ57QOlQ.mjs

@@ -1,22 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/transform-job/index.ts
-var transform_job_default = defineCommandGroup({
-	name: "transform-job",
-	description: "Manage Metabase transform jobs",
-	skills: [{
-		skill: "transform",
-		purpose: "tag-driven job schedules"
-	}],
-	subCommands: {
-		list: () => import("./list-JqIFAXpw.mjs").then((mod) => mod.default),
-		get: () => import("./get-DeiC05Lm.mjs").then((mod) => mod.default),
-		create: () => import("./create-D44fg_iT.mjs").then((mod) => mod.default),
-		update: () => import("./update-DrvDC_0m2.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-Cx75BsN6.mjs").then((mod) => mod.default),
-		run: () => import("./run-bVD66LrU.mjs").then((mod) => mod.default),
-		transforms: () => import("./transforms-CstSQgQ-.mjs").then((mod) => mod.default),
-		"set-active": () => import("./set-active-BexM75_s.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { transform_job_default as default };

package/dist/transform-jxF8cjNA.mjs

@@ -1,28 +0,0 @@
-import { t as defineCommandGroup } from "./group-D1nGaEXW.mjs";
-//#region src/commands/transform/index.ts
-var transform_default = defineCommandGroup({
-	name: "transform",
-	description: "Manage Metabase transforms",
-	skills: [{
-		skill: "transform",
-		purpose: "body shape, run-with-wait, iterate"
-	}, {
-		skill: "mbql",
-		purpose: "MBQL source.query bodies"
-	}],
-	subCommands: {
-		list: () => import("./list-B2PbnXp4.mjs").then((mod) => mod.default),
-		get: () => import("./get-CCTRO18v.mjs").then((mod) => mod.default),
-		dependencies: () => import("./dependencies-W2dxsCpF.mjs").then((mod) => mod.default),
-		create: () => import("./create-Bw9DAq_x2.mjs").then((mod) => mod.default),
-		update: () => import("./update-DxLypq9G.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-AF64p0xG.mjs").then((mod) => mod.default),
-		"delete-table": () => import("./delete-table-CubRk-5H.mjs").then((mod) => mod.default),
-		run: () => import("./run-BaEBHum8.mjs").then((mod) => mod.default),
-		cancel: () => import("./cancel-iGUVm1h2.mjs").then((mod) => mod.default),
-		"get-run": () => import("./get-run-DnKCnvUa.mjs").then((mod) => mod.default),
-		runs: () => import("./runs-DWm1pIdP.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { transform_default as default };