@metabase/cli 0.5.2 → 0.5.3

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

@@ -0,0 +1,87 @@
+---
+name: data-app-filters
+description: Build the filter controls of a Metabase data app — the filter contract, which cards a filter reaches, All by default, options from their own question, a searchable combobox for entities, date presets, `DateRangePopover` and `DateRangeCalendar` with labels from `useDateFormatter`, and a single-date picker. Triggers — "add a filter to the app", "filter the chart by date", "a date range picker", "filter by customer", "a dropdown of categories", "the filter doesn't change the chart", "the date shows the previous day". The query side — runtime clauses and their limits — is in `data-app-data`.
+allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
+requires: [dataApps]
+---
+
+# Filter controls in a data app
+
+A filter is an ordinary React control whose state becomes `filter(...)` clauses in a hook's second argument, on a column the question returns (`data-app-data`, _Runtime clauses_). This skill covers the controls; "panel" below means a chart, KPI or table on the page.
+
+## Write the contract first
+
+Before any control, write one row per filter: the question that gives its options, the raw value `filter(...)` receives, the panels whose question returns that column, and the panels whose question doesn't.
+
+| Filter    | Options question           | Raw value    | Panels                 | Not these      |
+| --------- | -------------------------- | ------------ | ---------------------- | -------------- |
+| Franchise | franchises, by id and name | franchise id | orders, revenue, stock | —              |
+| Plan      | orders broken out by plan  | plan text    | orders                 | revenue, stock |
+
+- A filter in the page's global bar changes every panel that can take it. One that can't reach a panel is scoped to its section, visibly, or left out. A KPI and its detail table about the same thing take the same filters, unless the UI says why not.
+- One date control per scope. Never a global date range beside a page-specific date where one of the two does nothing; a page whose cards use another date column gets one control for that column.
+- Build each panel's clauses from its own question's columns, inline at its hook call. Never reuse an array built for another question.
+
+## Values and options
+
+- Every filter starts at **All**. Keep it as `"all"` in state and send it as no clause (`[]`); treat `""`, `null` and `undefined` the same way. In a Yes/No/All filter, Yes and No each filter (`true`, `false`), and only All sends nothing.
+- Options come at runtime from their own question in the app's collection, broken out on the filtered column — never hardcoded unless the user gave a closed list. Dedupe them from its rows, and keep the label apart from the value.
+- Filter by a stable raw value (an id) and show its label; never filter by a display label when an id exists, and never feed free text into an exact-id filter.
+- All stays selectable while options load, come back empty or fail; don't disable the control. When fresh options no longer hold the selected value, reset to All:
+
+```tsx
+useEffect(() => {
+  if (selected !== "all" && !options.some((option) => option.value === selected)) {
+    setSelected("all");
+  }
+}, [options, selected]);
+```
+
+## Entities: a searchable combobox
+
+Any list whose options come from a question — an id shown as a name, a category, anything that can grow — is one searchable combobox, even while it's short. A `<select>` is only for a short closed list the user gave. Prefer the app's component library or a small established combobox package; hand-roll only a small one. Either way:
+
+- Click or focus opens the list at once, before any typing; search matches labels, not ids.
+- All is always an option, and picking an option stores its raw value.
+- The list is capped or scrolls, and looks like the app's other controls.
+- Don't close the list from the trigger's `onBlur` when the popover holds an auto-focused input — moving focus into it closes the list at once. Close on selection, Escape, or focus leaving the whole wrapper.
+
+## Date ranges
+
+A preset bar lists the durations, then All time, then Custom last — leave Custom out only if the user asked for fixed presets. Every option ends in the same `[start, end]` range (All time is `[null, null]`), so one `between` filter serves them all. Custom is `DateRangePopover` around your own trigger, or `DateRangeCalendar` inline, both from `@metabase/embedding-sdk-react/data-app`. No date-picker library and no `<input type="date">` for a range.
+
+```tsx
+import { DateRangePopover, filter, useDateFormatter } from "@metabase/embedding-sdk-react/data-app";
+
+const { formatDateRange } = useDateFormatter();
+const [range, setRange] = useState<[string | null, string | null]>([null, null]);
+const [start, end] = range;
+// at the hook: filters: start && end ? [filter({ type: "column", name: "CREATED_AT" }, "between", [start, end])] : []
+
+<DateRangePopover value={range} onChange={setRange}>
+  <button className="filter-button">{formatDateRange(range) || "Custom"}</button>
+</DateRangePopover>;
+```
+
+- Both ends are `YYYY-MM-DD` strings, the shape `filter(...)` takes. `onChange` fires on every click, so a half-picked range arrives as `[start, null]`: filter only once both ends are set, never with a sentinel date.
+- The child is the trigger: one element or a `forwardRef` component, since the popover attaches a ref and a click handler.
+- Label it with `formatDateRange(range)` (or `formatDate` for one end), which formats in the instance's locale; both take a dayjs `format`, and `formatDateRange` a `separator`. It returns `""` until the SDK loads. Never `new Date("YYYY-MM-DD")`: a date-only string parses as UTC and shows the previous day west of Greenwich.
+- The popover closes once both ends are picked (`closeOnSelect`); `opened` and `onOpenedChange` control it yourself. Also `defaultValue`, `minDate` and `maxDate` (`YYYY-MM-DD`), `numberOfColumns` (default 2) and `position` (default `bottom-start`). `DateRangeCalendar` takes the same value props plus `className` and `style`.
+
+A preset's range, from local dates — never `toISOString()`, which shifts the day:
+
+```ts
+const ymd = (d: Date) =>
+  `${d.getFullYear()}-${String(d.getMonth() + 1).padStart(2, "0")}-${String(d.getDate()).padStart(2, "0")}`;
+const lastMonths = (n: number): [string, string] => {
+  const end = new Date();
+  const start = new Date(end.getFullYear(), end.getMonth() - n, end.getDate());
+  return [ymd(start), ymd(end)];
+};
+```
+
+**A single date or a date-time** is the one case for a library: `npm install react-datepicker`, import `react-datepicker/dist/react-datepicker.css`, type the callback (`(date: Date | null) => …`), and convert with `ymd` above. Pass `null`, never `new Date("")`, for an empty value.
+
+## Check
+
+For every visible filter: All runs the unfiltered question; its options come from a question; each option changes every panel the contract says it reaches, and no other; a preset bar ends with Custom; and no scope has two date controls. Search the filter controls for `<select` and `type="date"` — an action form keeps its date inputs. Then build and publish (`data-app`, _Build and publish_).

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

@@ -0,0 +1,120 @@
+---
+name: data-app-ui
+description: Write a Metabase data app's UI — what the sandbox blocks and what replaces it, external APIs through `allowed_hosts`, layout and sizing, the SDK theme, a custom error state, the SDK components on offer, a Metabase chart versus a hand-drawn one and its visualization settings, pages with `DataAppRouter`, and what the app may show. Triggers — "change the layout", "theme the app", "add a page", "link between pages", "call an external API from the app", "the chart overflows", "invisible chart labels", "make it look like our brand". Creating and publishing is `data-app`; its data is `data-app-data`.
+allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
+requires: [dataApps]
+---
+
+# A data app's UI
+
+Everything here runs inside the sandbox, the same in the dev preview as in Metabase; check each change in the preview and its diagnostics feed (`data-app`).
+
+## Source
+
+- Plain ESM and TSX. SDK components come from `@metabase/embedding-sdk-react`; the data hooks, routing, `copy`, `DateRangePopover`, `DateRangeCalendar` and `useDateFormatter` from `@metabase/embedding-sdk-react/data-app`. JSX needs no `import React`; import hooks and React types by name.
+- React, React DOM and both SDK entries come from the host. Never read SDK values off `globalThis`: the sandbox globals there are private.
+- The build is one self-contained file: CSS is inlined, `import logo from "./logo.png"` is a data URI, `import Icon from "./icon.svg?react"` a component (add `declare module "*.svg?react";` in a `.d.ts` under `src/` if the editor doesn't know it). Keep large binaries out. There's no `index.html` and no Vite plugin to add: solve it in `src/`.
+- Once the app grows: `src/App.tsx` for routing and composition, `pages/` one file per screen, `components/`, `hooks/`, `lib/` for pure helpers.
+
+## What the app shows
+
+- Only what Metabase returned, or deterministic transforms of it: no sample data, invented KPIs, trends, statuses, or claims such as "real-time" or "at risk" the data doesn't support. A section no question supports is left out.
+- Don't read a `rate`, `score`, `margin` or `percent` column as a percentage or threshold — no `%`, `* 100`, colors or stars — unless its `semanticType` in `src/metabase.ts`, or the user, says so.
+- Every panel has a loading state, its error, and an empty state for no rows — never an empty slot or a stale value.
+- Label with names, not ids; currency to two decimals, counts as integers; a `null` breakout is "Unknown". A trend needs several points: never a sparkline from one value. Cap long lists with a limit, pages or a scroll area.
+
+## What the sandbox blocks
+
+| Blocked                                                                                                    | Use instead                                                                               |
+| ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
+| `fetch` to Metabase or to any origin outside the app's `allowed_hosts`; `XMLHttpRequest`; `WebSocket`      | The data hooks for Metabase; _External APIs_ for anything else.                           |
+| `alert`, `confirm`, `prompt`                                                                               | A modal in your own tree.                                                                 |
+| `localStorage`, `sessionStorage`, `indexedDB`, `document.cookie`                                           | Nothing persists across reloads; persist through an action (`data-app-actions`).          |
+| `window.open`, `history.pushState`, `history.replaceState`                                                 | `useDataAppLocation().navigate`; `<a target="_blank" rel="noopener">` for external links. |
+| `navigator.clipboard`, `execCommand("copy")`                                                               | `await copy(text)` in a user event — write-only, there's no paste.                        |
+| `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"]}'`, plus an `allowed_hosts:` list in `data_app.yaml` beside `package.json` for the preview, 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
+
+- The root element gets `minHeight: "100vh"` (plus `boxSizing: "border-box"` with padding) and the page background; never `height`. Regions that reach the bottom, such as a sidebar, go in a flex-column root with `flex: 1`. Check the emptiest screens — loading, empty, a lone KPI — since they render shortest.
+- SDK questions don't size to their parent: pass `height` and `width` to the component that draws (`StaticQuestion`, `InteractiveQuestion`, or `InteractiveQuestion.QuestionVisualization`) — the height actually left in its panel, or `height="100%"` in a fixed-height box. A KPI needs little: about `120` for a `scalar`, more for a `smartscalar`'s comparison or a `gauge`.
+- Don't wrap an SDK question in `overflow: hidden`, hover transforms or hover-driven layout shifts: its menus and tooltips need stable geometry.
+
+## Theme
+
+`src/theme.ts`, passed as `providerProps.theme`, is the only way to style SDK components, one theme for the whole app; it never styles your own UI (inline styles or CSS modules).
+
+| Key                                                    | Rule                                                                                                                                     |
+| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
+| `colors.brand`                                         | The app's accent.                                                                                                                        |
+| `colors["brand-hover"]`, `colors["brand-hover-light"]` | A light tint (`#EAF4FF` for a blue brand), never the saturated brand.                                                                    |
+| `colors.charts`                                        | All 8 slots, starting with `brand`, vivid and distinct — never pale tints, which can color labels. An empty slot keeps Metabase's color. |
+| `colors.background`, `colors["background-secondary"]`  | The color of the SDK component's own container: `white` inside a white card.                                                             |
+| `colors["text-primary"]`, `-secondary`, `-tertiary`    | Contrast with `background`; set them whenever you set it. Missing contrast is the "invisible chart labels" bug.                          |
+| `colors.positive`, `colors.negative`, `fontFamily`     | Up and down in trends and changes; the SDK's typeface. A `text-hover` must contrast with both brand-hover colors in open menus.          |
+
+**Error state.** A question that can't load shows Metabase's neutral error. To match the app, add an `errorComponent` to `providerProps` — it replaces the error of every SDK component, so keep the wording generic, render its `message` (a `ReactNode`) as it is, and use no data hooks in it:
+
+```tsx
+import type { SdkErrorComponentProps } from "@metabase/embedding-sdk-react";
+
+export function AppError({ message }: SdkErrorComponentProps) {
+  return <div style={{ padding: 16, color: "#6b7280" }}>{message}</div>;
+}
+// src/index.tsx: providerProps: { theme, errorComponent: AppError }
+```
+
+## SDK components
+
+| Import                                                                           | For                                                                   |
+| -------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
+| `StaticQuestion`                                                                 | A chart, KPI or table without drill-through — the default.            |
+| `InteractiveQuestion`                                                            | One meant to be explored: drill-through, chart switching, the editor. |
+| `StaticDashboard`, `InteractiveDashboard`, `EditableDashboard`                   | A dashboard.                                                          |
+| `CreateQuestion`, `MetabotQuestion`, `CollectionBrowser`, `CreateDashboardModal` | Authoring flows, rarely in an app.                                    |
+
+## A Metabase chart or your own
+
+Ask "can Metabase draw this at all?", never "which looks closer to the design?" — and decide per element, not per page.
+
+- **Yes** — bar, line, area, combo, row, pie, scalar, smartscalar, gauge, progress, funnel, scatter, waterfall, boxplot, sankey, pivot, map, tables: render it with `useMetabaseQueryObject` and `StaticQuestion` (`data-app-data`). It keeps the instance's formatting, tooltips, theming and drill-through. Styling is never a reason to draw it yourself.
+- **No**, or the user asked for a custom one — scorecards, timelines, calendar grids, one visual from several queries: draw it from `useMetabaseQuery` rows, with SVG or a chart library the app already has.
+- A KPI is `scalar`, `smartscalar`, `gauge` or `progress`; put what Metabase doesn't draw (a caption, stars) beside it.
+- `InteractiveQuestion`: pass `isSaveEnabled={false}`, and `title={false}` in a panel with its own heading. Children replace its layout: `<InteractiveQuestion card={card}><InteractiveQuestion.QuestionVisualization height={360} /></InteractiveQuestion>` is the chart alone.
+
+**Visualization settings.** Add `visualizationSettings` only for a change the user asked for. Their keys are a question's `visualization_settings` keys — the `visualization` skill lists them — and the installed types decide what's legal: `rg -n "<key>|declare type .*VisualizationSettings" node_modules/@metabase/embedding-sdk-react/dist/index.d.ts`, never the whole file, never from memory. Keep them few: keys such as `graph.dimensions`, `pie.metric` and `column_settings` name result columns and break when the question changes.
+
+- A `table` with two breakouts and one aggregation renders as a pivot when a breakout has at most 16 values; `{ "table.pivot": false }` keeps one row per group.
+- A scalar shows the first column: with a key column first, point it at the number with `{ "scalar.field": "avg_rating" }`.
+- A header: `column_settings: { '["name","approvers"]': { column_title: "Approvers" } }`.
+
+## Pages
+
+No router library — it calls `history.pushState`, which the sandbox blocks. Wrap the app once in `<DataAppRouter>`, link with `<DataAppLink to="/customers/42">` (an `<a href>` that takes the usual anchor props), and read `{ pathname, navigate }` from `useDataAppLocation()`. There's no `useParams`: match `pathname` yourself.
+
+```tsx
+const TABS = [
+  { path: "/", label: "Overview", render: () => <Overview /> },
+  { path: "/customers", label: "Customers", render: () => <Customers /> },
+];
+// `/` and any unknown path open the first tab
+const activeTab = (pathname: string) =>
+  TABS.find((tab) => tab.path !== "/" && pathname.startsWith(tab.path)) ?? TABS[0];
+
+function Page() {
+  const { pathname } = useDataAppLocation();
+  const customerId = pathname.match(/^\/customers\/(\d+)$/)?.[1];
+  return customerId ? <CustomerDetail id={Number(customerId)} /> : activeTab(pathname).render();
+}
+// nav: <DataAppLink to={tab.path} aria-current={tab === activeTab(pathname) ? "page" : undefined}>
+// App: <DataAppRouter><Nav /><Page /></DataAppRouter>
+```
+
+Metabase mirrors each route to `/apps/<slug>/<path>`, and a reload there opens that page. A middle-click opens a new tab only in the preview; in Metabase that tab shows "This data app can't be opened directly." Check in the preview: reload on a sub-path, then on `/` — the first tab shows, marked selected.
+
+## Before handoff
+
+`npm run dev` only transpiles: run `npm run typecheck` after every round of edits and fix what it reports, and report the result, errors grouped by cause. Search the changed files and fix what turns up: `card={{` (every `card` comes from `useMemo`), `row[0]` and `as unknown as` (rows are keyed by column name), `<select` for a list from a question (`data-app-filters`), `type="date"` and `new Date(` in a date filter, `* 100` and `%`. Read the diagnostics feed with every panel mounted, then build and publish (`data-app`, _Build and publish_).

package/dist/delete-runtime-DRGveT8H.mjs

@@ -1,55 +0,0 @@
-import { St as ConfigError, _ as promptConfirm, c as renderSummary } from "./cli.mjs";
-import { z } from "zod";
-//#region src/commands/delete-runtime.ts
-const DeleteResult = z.object({
-	deleted: z.boolean(),
-	aborted: z.boolean(),
-	id: z.number().int()
-});
-const deleteResultView = {
-	compactPick: DeleteResult,
-	tableColumns: [
-		{
-			key: "id",
-			label: "ID"
-		},
-		{
-			key: "deleted",
-			label: "Deleted"
-		},
-		{
-			key: "aborted",
-			label: "Aborted"
-		}
-	]
-};
-async function confirmDestructive(args) {
-	if (args.yes) return true;
-	if (process.stdin.isTTY !== true) throw new ConfigError(`refusing to ${args.action} without confirmation — pass --yes to proceed non-interactively`);
-	return promptConfirm({
-		message: args.promptMessage,
-		initialValue: false
-	});
-}
-async function confirmAndDelete(args) {
-	if (!await confirmDestructive({
-		yes: args.yes,
-		action: `delete ${args.id}`,
-		promptMessage: args.promptMessage
-	})) {
-		renderSummary({
-			deleted: false,
-			aborted: true,
-			id: args.id
-		}, deleteResultView, args.abortMessage, args.ctx);
-		return;
-	}
-	await args.deleteResource();
-	renderSummary({
-		deleted: true,
-		aborted: false,
-		id: args.id
-	}, deleteResultView, args.successMessage, args.ctx);
-}
-//#endregion
-export { confirmAndDelete as n, confirmDestructive as r, DeleteResult as t };

package/dist/git-sync-CNTB5jvI.mjs

@@ -1,29 +0,0 @@
-import { t as defineCommandGroup } from "./group-81zoQcEP.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-lCN8unWe.mjs").then((mod) => mod.default),
-		"is-dirty": () => import("./is-dirty-DHYYRl6Y.mjs").then((mod) => mod.default),
-		"has-remote-changes": () => import("./has-remote-changes-DxsRvZsw.mjs").then((mod) => mod.default),
-		dirty: () => import("./dirty-DsrGfLit.mjs").then((mod) => mod.default),
-		"current-task": () => import("./current-task-C2PPBVVv.mjs").then((mod) => mod.default),
-		"cancel-task": () => import("./cancel-task-acq1GT6Z.mjs").then((mod) => mod.default),
-		wait: () => import("./wait-Cvt8xO0h.mjs").then((mod) => mod.default),
-		import: () => import("./import-izn2_OsW.mjs").then((mod) => mod.default),
-		export: () => import("./export-CIW-dHft.mjs").then((mod) => mod.default),
-		"export-preflight": () => import("./export-preflight-BMlz3Hp9.mjs").then((mod) => mod.default),
-		stash: () => import("./stash-Dyc1xZ8u.mjs").then((mod) => mod.default),
-		branches: () => import("./branches-C7mNYAky.mjs").then((mod) => mod.default),
-		"create-branch": () => import("./create-branch-C4Ql9G2g.mjs").then((mod) => mod.default),
-		"add-collection": () => import("./add-collection-C0BQHjJd.mjs").then((mod) => mod.default),
-		"remove-collection": () => import("./remove-collection-DfUsf6Dd.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { git_sync_default as default };

package/dist/table-Cb_Uvw8m.mjs

@@ -1,26 +0,0 @@
-import { t as defineCommandGroup } from "./group-81zoQcEP.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-BxIulkp3.mjs").then((m) => m.default),
-		get: () => import("./get-DRhcS76J.mjs").then((m) => m.default),
-		fields: () => import("./fields-CcerFaiu.mjs").then((m) => m.default),
-		fks: () => import("./fks-CYfBesHV.mjs").then((m) => m.default),
-		update: () => import("./update-8eXJso_l.mjs").then((m) => m.default),
-		"sync-schema": () => import("./sync-schema-B3nyoKZl.mjs").then((m) => m.default),
-		"rescan-values": () => import("./rescan-values-BuDmeda3.mjs").then((m) => m.default),
-		"discard-values": () => import("./discard-values-BfpwwC62.mjs").then((m) => m.default),
-		"bulk-edit": () => import("./bulk-edit-Cce05vb_.mjs").then((m) => m.default),
-		"bulk-sync-schema": () => import("./bulk-sync-schema-DLWf5dCl.mjs").then((m) => m.default),
-		"bulk-rescan-values": () => import("./bulk-rescan-values-DIQN4VT_.mjs").then((m) => m.default),
-		"bulk-discard-values": () => import("./bulk-discard-values-D_d5_1w5.mjs").then((m) => m.default)
-	}
-});
-//#endregion
-export { table_default as default };

package/dist/transform-job-Dlx2c6II.mjs

@@ -1,22 +0,0 @@
-import { t as defineCommandGroup } from "./group-81zoQcEP.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-BEBAq1xc.mjs").then((mod) => mod.default),
-		get: () => import("./get-Cj3-w_Nu.mjs").then((mod) => mod.default),
-		create: () => import("./create-DiG165B2.mjs").then((mod) => mod.default),
-		update: () => import("./update-DpP1EEC0.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-DeqGTuwO.mjs").then((mod) => mod.default),
-		run: () => import("./run-BG_5lR0x.mjs").then((mod) => mod.default),
-		transforms: () => import("./transforms-DRAws1f4.mjs").then((mod) => mod.default),
-		"set-active": () => import("./set-active-32IaLx1O.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { transform_job_default as default };

package/dist/transform-kP11Mv9_.mjs

@@ -1,28 +0,0 @@
-import { t as defineCommandGroup } from "./group-81zoQcEP.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-CT7AOXTS.mjs").then((mod) => mod.default),
-		get: () => import("./get-BFloqjrN.mjs").then((mod) => mod.default),
-		dependencies: () => import("./dependencies-DD48u9i3.mjs").then((mod) => mod.default),
-		create: () => import("./create-B6dABrs7.mjs").then((mod) => mod.default),
-		update: () => import("./update-CnxzmPRG.mjs").then((mod) => mod.default),
-		delete: () => import("./delete-CH32Ew4m.mjs").then((mod) => mod.default),
-		"delete-table": () => import("./delete-table-BEuMlqw1.mjs").then((mod) => mod.default),
-		run: () => import("./run-BBRnFayr.mjs").then((mod) => mod.default),
-		cancel: () => import("./cancel-rnd6UI-6.mjs").then((mod) => mod.default),
-		"get-run": () => import("./get-run-C3AHKn3-.mjs").then((mod) => mod.default),
-		runs: () => import("./runs-CovgMSwy.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { transform_default as default };