@metabase/cli 0.3.1-alpha.support-worktrees.b634907 → 0.3.1-alpha.versioning.9ac5f50

package/skill-data/mbql/references/operators.md

@@ -106,21 +106,26 @@ Units (truncation only): `millisecond`, `second`, `minute`, `hour`, `day`, `week
 
 A stage's `aggregation` is a list of aggregation clauses.
 
-| Op                      | Args                       | Notes                            |
-| ----------------------- | -------------------------- | -------------------------------- |
-| `count`                 | none, or 1 expression      | with arg: count non-NULL         |
-| `sum` `avg` `min` `max` | 1 numeric/orderable        |                                  |
-| `distinct`              | 1 expression               | count of distinct values         |
-| `cum-count`             | none or 1 expression       | running count                    |
-| `cum-sum`               | 1 numeric                  | running sum                      |
-| `stddev` `var` `median` | 1 numeric                  |                                  |
-| `percentile`            | numeric, p (0.0–1.0)       |                                  |
-| `count-where`           | 1 boolean clause           |                                  |
-| `sum-where`             | numeric, boolean clause    |                                  |
-| `distinct-where`        | expression, boolean clause |                                  |
-| `share`                 | 1 boolean clause           | proportion 0–1                   |
-| `metric`                | metric id                  | reference a saved metric card    |
-| `measure`               | measure id                 | reference a saved measure (v59+) |
+| Op                      | Args                       | Notes                         |
+| ----------------------- | -------------------------- | ----------------------------- |
+| `count`                 | none, or 1 expression      | with arg: count non-NULL      |
+| `sum` `avg` `min` `max` | 1 numeric/orderable        |                               |
+| `distinct`              | 1 expression               | count of distinct values      |
+| `cum-count`             | none or 1 expression       | running count                 |
+| `cum-sum`               | 1 numeric                  | running sum                   |
+| `stddev` `var` `median` | 1 numeric                  |                               |
+| `percentile`            | numeric, p (0.0–1.0)       |                               |
+| `count-where`           | 1 boolean clause           |                               |
+| `sum-where`             | numeric, boolean clause    |                               |
+| `distinct-where`        | expression, boolean clause |                               |
+| `share`                 | 1 boolean clause           | proportion 0–1                |
+| `metric`                | metric id                  | reference a saved metric card |
+
+<!-- requires: measures -->
+
+`measure` takes a measure id and references a saved measure.
+
+<!-- /requires -->
 
 ```json
 ["count", {…}]

package/skill-data/metadata/SKILL.md

@@ -43,7 +43,7 @@ mb field update 1711 --body '{"semantic_type":"type/FK","fk_target_field_id":168
 - Queries can pull columns from the related table with no explicit join — `["field", {"source-field": 1711}, 1682]` in MBQL (see `mbql`).
 - Dashboard **linked filters** become possible (a State filter narrowing a City filter). **Linked filters read only these table-metadata FKs** — never a join you wrote inside a saved question — which is why a linked filter that "shows values it shouldn't" almost always means the FK isn't set in metadata. (See `dashboard`.)
 
-Removing the `type/FK` semantic type auto-clears `fk_target_field_id`. Point a FK only at a field in the **same database** — v60+ rejects a cross-database target; v58–v59 accept it silently and leave a broken relationship.
+Removing the `type/FK` semantic type auto-clears `fk_target_field_id`. Point a FK only at a field in the **same database** — a cross-database target is invalid and never resolves to a relationship.
 
 ## Semantic types are labels, not casts
 

package/skill-data/metadata/references/semantic-types.md

@@ -71,7 +71,13 @@ Everything else on a field/table (physical `name`, `base_type`, `effective_type`
 `display_name` · `description` · `caveats` · `points_of_interest` · `semantic_type` · `coercion_strategy` · `fk_target_field_id` · `visibility_type` · `has_field_values` · `settings` · `nfc_path` · `json_unfolding`
 
 **`PUT /api/table/:id` (`mb table update`)**
-`display_name` · `description` · `visibility_type` · `field_order` (`database` / `alphabetical` / `custom` / `smart`) · `entity_type` · `caveats` · `points_of_interest` · `show_in_getting_started` · `owner_user_id` / `owner_email` (ownership) · `data_layer` / `data_authority` / `data_source` (data-governance tiers) · `collection_id` (v62+)
+`display_name` · `description` · `visibility_type` · `field_order` (`database` / `alphabetical` / `custom` / `smart`) · `entity_type` · `caveats` · `points_of_interest` · `show_in_getting_started` · `owner_user_id` / `owner_email` (ownership) · `data_layer` / `data_authority` / `data_source` (data-governance tiers)
+
+<!-- requires: library -->
+
+· `collection_id` — the Library **Data** collection a published table sits in (`mb library publish` sets it; see `core`)
+
+<!-- /requires -->
 
 ## Coercion strategies (common)
 

package/skill-data/native-sql/references/template-tags.md

@@ -86,9 +86,13 @@ SQL: `{{snippet: Active Rows}}`. Create/manage the fragment with `mb snippet` (`
 
 SQL: `{{#42}}` or `{{#42-slug}}`, used where a table/subquery goes (`FROM {{#42}}`, `WITH x AS {{#42}}`). Runs with the referenced card's own defaults; no user value.
 
-### Source table — `table` (v59+)
+<!-- requires: nativeTableTemplateTag -->
 
-A niche v59+ type that references a warehouse table by id (`{type: "table", table-id: <id>}`, optional `source-filters`) where a table/subquery goes — analogous to a card reference but pointing at a raw table. Absent on v0.58. Reach for a card reference (`card`) unless you specifically need a bare-table source tag.
+### Source table — `table`
+
+A niche type that references a warehouse table by id (`{type: "table", table-id: <id>}`, optional `source-filters`) where a table/subquery goes — analogous to a card reference but pointing at a raw table. Reach for a card reference (`card`) unless you specifically need a bare-table source tag.
+
+<!-- /requires -->
 
 ### Temporal unit — `temporal-unit`
 

package/skill-data/notification/SKILL.md

@@ -110,7 +110,13 @@ An alert body has exactly three parts:
 
 Recipients are `{"email": "a@b.com"}` for an external address or `{"id": <user-id>}` for a Metabase user. A Slack channel is **not** a recipient — it goes in `details`: `{"channel_type": "slack", "details": {"channel": "#general"}, …}`.
 
-**`skip_if_empty: true`** suppresses the send when the dashboard's questions return no rows — the way to build a "only tell me when something happened" dashboard report. **`parameters`** sets filter values for this subscription only, so one dashboard can feed several audiences a different slice (Pro/Enterprise). Its entries are dashboard parameter values — the parameter `id`s come from `mb dashboard get <id> --fields parameters --json` (see the `dashboard` skill).
+**`skip_if_empty: true`** suppresses the send when the dashboard's questions return no rows — the way to build a "only tell me when something happened" dashboard report.
+
+<!-- requires: dashboardSubscriptionFilters -->
+
+**`parameters`** sets filter values for this subscription only, so one dashboard can feed several audiences a different slice. Its entries are dashboard parameter values — the parameter `id`s come from `mb dashboard get <id> --fields parameters --json` (see the `dashboard` skill).
+
+<!-- /requires -->
 
 `mb subscription list --archived` is a **swap, not a union** — it returns archived subscriptions _instead of_ active ones, never both. `mb dashboard subscriptions <id>` is the list scoped to one dashboard. `mb subscription archive <id>` also disables every channel on it, so restoring takes two steps: `update --body '{"archived":false}'`, then re-send the `channels` array with `enabled: true`.
 

package/skill-data/transform/SKILL.md

@@ -2,6 +2,7 @@
 name: transform
 description: Author and run Metabase transforms via `mb` — body shape (native SQL or structured MBQL), create + run-with-wait, run inspection, dependencies, cancel, the `update`-vs-recreate iteration rule, the writable-keys-only PATCH contract, plus transform tags and tag-driven transform-job schedules. Load when the user touches transforms — "create a transform", "run a transform", "fix a failing transform", "list transform runs", "cancel a running transform", "manage transform tags", "run a transform job", or anything `mb transform …` / `mb transform-job …` / `mb transform-tag …`.
 allowed-tools: Read, Write, Edit, Bash, AskUserQuestion
+requires: [transforms]
 ---
 
 # Transforms
@@ -48,7 +49,7 @@ mb transform run "$TRANSFORM_ID" --wait --profile <name> --json
 - `--wait` polls until status is `succeeded` or `failed`. Without it you get only `{message: "Transform run started", run_id, final: null}` and must poll yourself — don't put bare `transform run` in a tight loop; let `--wait` do the polling.
 - `--sync` implies `--wait`, then waits until the run registers its output table (the run registers it itself — no `db sync-schema` needed), adding `target_table_id` to the envelope. Use it when you'll build MBQL on the output (see "Inspect").
 - The `--json` envelope is shape-stable: `{message, run_id, final}` (plus `target_table_id` under `--sync` — a number, or `null` if the table didn't register before the timeout). `final` is `null` when `--wait` is omitted or the run never started, otherwise a full `TransformRun` with `status` and `message`. On a failed run (`final.status` ∈ {`failed`, `timeout`, `canceled`}) the CLI exits 1 and writes a one-line `transform run <id> failed` to stderr; the failure detail lives only in `final.message` on stdout, so `jq -r '.final.message'` is where to look.
-- `transform create --json` returns the agent-facing compact projection: `{id, name, description, source_type, target: {type, database, schema, name}, target_db_id, worktree_id}`. Read `target.schema`/`target.name` directly off it — no follow-up `transform get`.
+- `transform create --json` returns the agent-facing compact projection: `{id, name, description, source_type, target: {type, database, schema, name}, target_db_id}`. Read `target.schema`/`target.name` directly off it — no follow-up `transform get`.
 - If a transform with the same `name` already has a YAML representation on disk under the configured remote-sync repo, `create` mints a `_2` suffix on the exported filename (the new transform gets a fresh `entity_id`; the prior one isn't touched). For "iterate on the same concept", prefer `transform update <id>` — see "Iterating on a failing transform".
 - **`collection_id` only accepts a collection in the `:transforms` namespace.** Transforms aren't filed next to cards and dashboards — a normal analytics collection id fails create/update with `collection_id: A Transform can only go in Collections in the :transforms namespace.` Omit `collection_id` to leave the transform uncollected (the common case), or provision one with `mb collection create --body '{"name":"…"}' --namespace transforms --json` (see `core`) and pass the returned `id`. Cards and dashboards you build **on top of** the output table go in ordinary collections — so "put the transform and its dashboard in collection X" means _X holds the dashboard + cards; the transform stays in the transforms namespace._
 
@@ -67,18 +68,10 @@ TABLE_ID=$(mb transform run <id> --sync --profile <name> --json | jq -r '.target
 mb table get "$TABLE_ID" --include fields --profile <name> --json   # field ids for MBQL
 ```
 
-On `target_table_id: null` (still syncing when the poll timed out; exit 0) re-poll `mb transform get <id> --full --json` until the `target_table_id` / `table` linkage lands.
+On `target_table_id: null` (still syncing when the poll timed out; exit 0) re-poll `mb transform get <id> --json` until `target_table_id` is a number.
 
 Columns and types are inferred from the result set; change the SELECT shape and the next run fails on a column mismatch — drop the table first (`transform delete-table <id>`). A changed shape also needs a re-run with `--sync` before MBQL sees the new/renamed columns.
 
-## Editing transforms safely in a worktree
-
-A **worktree** is an isolated checkout of one git branch's content inside the same instance — the way to build a chain of transforms for PR review without touching production transforms or their tables. The lifecycle (create → pin → export-preflight → export → PR → delete) lives in the `git-sync` skill, section "Worktrees": **`mb skills get git-sync`**. What matters while authoring:
-
-- **`worktree_id` says where a transform lives.** `transform get` and `transform list` carry it: an integer for a worktree's transform, `null` for a main-app one. Read it before editing anything you did not create in this session — under a scope, `update` / `delete` / `delete-table` of a main-app transform is refused with `transform <id> is not in worktree <n> (<branch>); refusing to touch main-app content`.
-- **The scope is implicit once the profile is pinned.** With `--worktree <id|branch>`, `MB_WORKTREE`, or a pin in force, `transform list` shows only that worktree's transforms and `transform create` files what it creates into it. Without a scope both address the main app, whose listing excludes every worktree's rows.
-- **`transform run` is refused under a scope**, and the server rejects worktree runs anyway: `transform run is not available inside a worktree (…); it changes main-app content.` The create → run → fix loop therefore does not close inside a worktree. Validate the query with `--dry-run` (see `mbql`) before creating, iterate the body with `transform update`, and run it in the main app once the branch is merged and imported. Don't unpin, don't switch to another profile, and don't stand in a run with `mb query` — tell the user the run waits for the merge.
-
 ## Inspect runs and cancel an in-flight run
 
 ```bash
@@ -206,7 +199,16 @@ Key verbs (`mb transform-job --help` for the full list):
 mb transform-job transforms <id> --profile <name> --json   # preview which transforms this job resolves to (by tag)
 mb transform-job run <id> --profile <name> --json          # trigger a job now; runs all its tagged transforms
 mb transform-job run <id> --force-refresh --profile <name> --json   # also re-run dependencies that are already fresh
+```
+
+<!-- requires: transformJobActivation -->
+
+```bash
 mb transform-job set-active false --profile <name> --json  # disable every job at once (true re-enables); admin only
 ```
 
-`transform-job run` is fire-and-forget — the server returns `{message, job_run_id}` immediately, with no per-job-run polling (no `--wait`). Most ad-hoc agent work is one-off `transform run`, not job authoring.
+<!-- /requires -->
+
+Every job row carries `active`; it is `null` on a server that cannot switch jobs off, where every job runs on schedule.
+
+`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/skill-data/visualization/SKILL.md

@@ -27,7 +27,10 @@ Decide which relationship in the data matters most, then pick the chart. The sha
 - **Compare a measure across categories** → `bar` (vertical). Use `row` (horizontal bar) when labels are long or there are many categories. Sort by value unless the dimension has a natural order.
 - **Change over time / trend** → `line` for a continuous series; `bar`/`area` for a few discrete periods. Two measures on unlike scales → `combo` (line + bar, dual-axis) — only when the metrics are genuinely related.
 - **Part-to-whole, one snapshot** → `pie`, but only for a meaningful whole with **≤5 slices**; beyond that use a sorted `bar`/`row`. Composition over time → stacked `area`/`bar`.
-- **Distribution / spread / outliers** → a `bar` histogram (bin the measure — see `mbql` binning); on **v59+** servers `boxplot` compares several groups' spread directly.
+- **Distribution / spread / outliers** → a `bar` histogram (bin the measure — see `mbql` binning).
+<!-- requires: boxplotDisplay -->
+- **Spread across several groups** → `boxplot` compares the groups' distributions directly.
+<!-- /requires -->
 - **Correlation between two measures** → `scatter` (a third measure → bubble size).
 - **Sequential additive contributions** (start → +/− steps → total) → `waterfall`.
 - **Stage drop-off in an ordered, cumulative funnel** → `funnel`.
@@ -35,7 +38,7 @@ Decide which relationship in the data matters most, then pick the chart. The sha
 - **Geographic** → `map`: region/choropleth (a region dimension + a measure), pin (lat + long), or grid/heat (coordinates + measure).
 - **Precise values, many columns, mixed types, or no chart fits** → `table`; `pivot` for a cross-tab of two dimensions; `object` for a single record's detail.
 
-Valid `display` values — the registered visualizations: `table`, `bar`, `line`, `area`, `row`, `pie`, `scalar`, `smartscalar`, `combo`, `pivot`, `funnel`, `map`, `scatter`, `waterfall`, `progress`, `gauge`, `object`, `sankey`. The API types `display` as a plain string and accepts any value — it renders an unknown one as nothing. (`boxplot` is registered only on **v59+** servers — older ones render it blank; use a `bar` histogram for distributions instead. `scalar` **is** the "Number" viz — `display: number` is a legacy serialization alias, not a registered visualization; use `scalar`. `list` exists but is hidden — don't pick it. `heading`/`text`/`link`/`iframe`/`action` are dashcard virtuals, not standalone cards — see references.) A typo like `bargraph`/`linechart` is accepted and renders blank — the most common "why is my chart blank" cause.
+Valid `display` values — the registered visualizations: `table`, `bar`, `line`, `area`, `row`, `pie`, `scalar`, `smartscalar`, `combo`, `pivot`, `funnel`, `map`, `scatter`, `waterfall`, `progress`, `gauge`, `object`, `sankey`. The API types `display` as a plain string and accepts any value — it renders an unknown one as nothing. (`scalar` **is** the "Number" viz — `display: number` is a legacy serialization alias, not a registered visualization; use `scalar`. `list` exists but is hidden — don't pick it. `heading`/`text`/`link`/`iframe`/`action` are dashcard virtuals, not standalone cards — see references.) A typo like `bargraph`/`linechart` is accepted and renders blank — the most common "why is my chart blank" cause.
 
 ## Step 2 — bind data columns and set options
 
@@ -53,7 +56,6 @@ Valid `display` values — the registered visualizations: `table`, `bar`, `line`
 | `row`                       | as bar; prefer for long/many category labels              | `graph.dimensions`, `graph.metrics`                        |
 | `scatter`                   | two numeric measures (correlation)                        | `graph.dimensions`, `graph.metrics` (`scatter.bubble` opt) |
 | `waterfall`                 | exactly 1 dimension + ≥1 measure; sequential              | `graph.dimensions` (1), `graph.metrics` (1)                |
-| `boxplot` _(v59+)_          | ≥3 cols, ≥2 dimensions, ≥1 measure                        | `graph.dimensions`, `graph.metrics`                        |
 | `pie`                       | ≥2 rows, ≥2 cols, ≥1 dimension + ≥1 measure; ≤~5 slices   | `pie.dimension`, `pie.metric`                              |
 | `funnel`                    | 2 columns (stage + value); ordered stages                 | `funnel.dimension`, `funnel.metric`                        |
 | `map` (region)              | a string/region dimension + a measure                     | `map.region`, `map.dimension`, `map.metric`                |
@@ -62,6 +64,12 @@ Valid `display` values — the registered visualizations: `table`, `bar`, `line`
 | `pivot`                     | ≥2 cols, all aggregated/breakout                          | — (`pivot_table.column_split` auto)                        |
 | `table` `object`            | anything (table is the universal fallback)                | — (always renders)                                         |
 
+<!-- requires: boxplotDisplay -->
+
+`boxplot` is registered too: ≥3 cols, ≥2 dimensions, ≥1 measure, on **unaggregated** rows; required keys `graph.dimensions`, `graph.metrics`.
+
+<!-- /requires -->
+
 ### The rule that trips everyone: settings name **output columns**, by name
 
 `graph.dimensions`, `graph.metrics`, `pie.dimension`, `pie.metric`, `scalar.field`, `funnel.metric`, `map.latitude_column`, `sankey.source`, … all take **output column-name strings** — the names the query _produces_, not field ids. A `count` aggregation outputs the column `count`; a breakout on a field outputs that field's name; a named aggregation outputs its `name`. These strings are **identical in the API form and the portable (git-sync) form** — no numeric-vs-name footgun here.

package/skill-data/visualization/references/settings.md

@@ -2,7 +2,7 @@
 
 ## Contents
 
-- [Cartesian — `bar`, `line`, `area`, `combo`, `scatter`, `waterfall`, `row`, `boxplot`](#cartesian--bar-line-area-combo-scatter-waterfall-row-boxplot) — shared keys (binding, stacking, goal/trend, data labels, axes, tooltip) plus `scatter`, `waterfall`, `row`, `boxplot` extras
+- [Cartesian — `bar`, `line`, `area`, `combo`, `scatter`, `waterfall`, `row`](#cartesian--bar-line-area-combo-scatter-waterfall-row) — shared keys (binding, stacking, goal/trend, data labels, axes, tooltip) plus `scatter`, `waterfall`, `row` extras
 - [Part-to-whole & single value — `pie`, `funnel`, `gauge`, `progress`, `scalar`, `smartscalar`](#part-to-whole--single-value--pie-funnel-gauge-progress-scalar-smartscalar)
 - [Tabular, geographic & flow — `table`, `pivot`, `object`, `map`, `sankey`](#tabular-geographic--flow--table-pivot-object-map-sankey) — includes `table.column_formatting` conditional formatting
 - [`column_settings` — per-column formatting](#column_settings--per-column-formatting) — number/date/currency, `view_as`, alignment, mini bars
@@ -18,7 +18,7 @@ All column-naming keys (`graph.dimensions`, `pie.dimension`, `table.columns[].na
 
 ---
 
-# Cartesian — `bar`, `line`, `area`, `combo`, `scatter`, `waterfall`, `row`, `boxplot`
+# Cartesian — `bar`, `line`, `area`, `combo`, `scatter`, `waterfall`, `row`
 
 `bar`/`line`/`area`/`combo` share an identical key set (combo just defaults the first series to a line, the rest to bars). `scatter`/`waterfall`/`row`/`boxplot` use a subset plus their own extras. Most allow up to 2 dimensions and unlimited metrics; **waterfall is 1 dimension + 1 metric**, boxplot allows 2 dimensions.
 
@@ -102,9 +102,9 @@ Use for sequential additive contributions (start → +/− steps → total). **U
 
 Horizontal bars — use when category labels are long or numerous. Here `graph.dimensions` is the y-axis (categories) and `graph.metrics` the x-axis (values). X-scale is `"ordinal"` only; no trend line, tooltip columns, or split panels. **Required:** `graph.dimensions`, `graph.metrics`.
 
-## boxplot
+<!-- requires: boxplotDisplay -->
 
-_Registered only on **v59+** servers — older ones render `display: boxplot` blank; use a `bar` histogram there._
+## boxplot
 
 Use for distribution/spread/outliers, especially across several groups. Needs **unaggregated** rows. **Use for:** ≥3 columns, ≥2 dimensions, ≥1 measure. **Required:** `graph.dimensions`, `graph.metrics`. X-scale is `"ordinal"`.
 
@@ -115,6 +115,8 @@ Use for distribution/spread/outliers, especially across several groups. Needs **
 | `boxplot.show_mean`        | boolean |                                                | `true`       |
 | `boxplot.show_values_mode` | string  | `"median"`, `"all"` (when `graph.show_values`) | `"median"`   |
 
+<!-- /requires -->
+
 ---
 
 # Part-to-whole & single value — `pie`, `funnel`, `gauge`, `progress`, `scalar`, `smartscalar`

package/skills/metabase-cli/SKILL.md

@@ -17,7 +17,7 @@ Before running any `mb` command, load the workflow content from the CLI:
 
 ```bash
 mb skills get core    # auth, flag conventions, every command group
-mb skills list        # everything available on the installed version
+mb skills list        # every bundled skill the profile's server can use (--all for all of them)
 ```
 
 **Doing a whole job, not one command?** If the user wants an outcome — "make sense of my data", "build a data model", "go from raw data to a dashboard", "answer questions about my data", "be my data analyst", "set up analytics for X" — load the guided end-to-end skill instead and let it drive:

package/dist/archive-CqOKKrb2.mjs

@@ -1,38 +0,0 @@
-import { H as profileFlag, R as connectionFlags, U as worktreeFlag, V as outputFlags, p as renderSummary } from "./cli.mjs";
-import { i as assertInWorktree, r as WORKTREE_SCOPE_DETAIL, t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
-import { t as parseId } from "./parse-id-DDCn3VXx.mjs";
-import { t as Snippet } from "./snippet-BxgvQ09J.mjs";
-import { t as snippetView } from "./snippet-DecHB4Dn.mjs";
-//#region src/commands/snippet/archive.ts
-var archive_default = defineMetabaseCommand({
-	meta: {
-		name: "archive",
-		description: "Archive (soft-delete) a native query snippet by id"
-	},
-	capabilities: { minVersion: 58 },
-	worktree: "scoped",
-	details: WORKTREE_SCOPE_DETAIL,
-	args: {
-		...outputFlags,
-		...profileFlag,
-		...connectionFlags,
-		...worktreeFlag,
-		id: {
-			type: "positional",
-			description: "Snippet id",
-			required: true
-		}
-	},
-	outputSchema: Snippet,
-	examples: ["mb snippet archive 1", "mb snippet archive 1 --json"],
-	async run({ args, ctx, getClient, getWorktree }) {
-		const id = parseId(args.id);
-		const client = await getClient();
-		const scope = await getWorktree();
-		if (scope !== null) assertInWorktree("snippet", id, (await client.snippet.get(id)).worktree_id, scope);
-		const updated = await client.snippet.archive(id);
-		renderSummary(updated, snippetView, `Archived snippet ${updated.id} "${updated.name}".`, ctx);
-	}
-});
-//#endregion
-export { archive_default as default };

package/dist/archive-DCjdICg7.mjs

@@ -1,38 +0,0 @@
-import { H as profileFlag, R as connectionFlags, U as worktreeFlag, V as outputFlags, p as renderSummary } from "./cli.mjs";
-import { i as assertInWorktree, r as WORKTREE_SCOPE_DETAIL, t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
-import { t as parseId } from "./parse-id-DDCn3VXx.mjs";
-import { r as Collection } from "./collection-BxE7OzcQ.mjs";
-import { n as collectionView } from "./collection-CJHqsFKP.mjs";
-//#region src/commands/collection/archive.ts
-var archive_default = defineMetabaseCommand({
-	meta: {
-		name: "archive",
-		description: "Archive (soft-delete) a collection by id"
-	},
-	capabilities: { minVersion: 58 },
-	worktree: "scoped",
-	details: WORKTREE_SCOPE_DETAIL,
-	args: {
-		...outputFlags,
-		...profileFlag,
-		...connectionFlags,
-		...worktreeFlag,
-		id: {
-			type: "positional",
-			description: "Collection id",
-			required: true
-		}
-	},
-	outputSchema: Collection,
-	examples: ["mb collection archive 4", "mb collection archive 4 --json"],
-	async run({ args, ctx, getClient, getWorktree }) {
-		const id = parseId(args.id);
-		const client = await getClient();
-		const scope = await getWorktree();
-		if (scope !== null) assertInWorktree("collection", id, (await client.collection.get(id)).worktree_id, scope);
-		const updated = await client.collection.archive(id);
-		renderSummary(updated, collectionView, `Archived collection ${updated.id} "${updated.name}".`, ctx);
-	}
-});
-//#endregion
-export { archive_default as default };

package/dist/branch-BSeGrtP7.mjs

@@ -1,28 +0,0 @@
-import { i as ConfigError } from "./predicates-Bkm2IoeX.mjs";
-//#region src/commands/git-sync/branch.ts
-const BRANCH_PINNED_REFUSAL = "a worktree is pinned to its branch; drop --branch";
-const BRANCH_UNSET_REFUSAL = "remote-sync-branch is not set; configure git-sync first";
-function syncBranchTarget(input) {
-	const stated = input.flag === void 0 || input.flag === "" ? null : input.flag;
-	if (input.scope !== null) {
-		if (stated !== null) throw new ConfigError(BRANCH_PINNED_REFUSAL);
-		return {
-			branch: input.scope.branch,
-			expected: input.scope.branch
-		};
-	}
-	if (input.tracked === null) throw new ConfigError(BRANCH_UNSET_REFUSAL);
-	return {
-		branch: stated ?? input.tracked,
-		expected: input.tracked
-	};
-}
-async function resolveSyncBranch(mb, scope, flag) {
-	return syncBranchTarget({
-		scope,
-		flag,
-		tracked: scope === null ? await mb.gitSync.branch() : null
-	});
-}
-//#endregion
-export { resolveSyncBranch as t };

package/dist/cancel-task-BMQXtjW5.mjs

@@ -1,34 +0,0 @@
-import { H as profileFlag, R as connectionFlags, U as worktreeFlag, V as outputFlags, p as renderSummary } from "./cli.mjs";
-import { r as WORKTREE_SCOPE_DETAIL, t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
-import { u as SyncTask } from "./git-sync-DLzJrdMi.mjs";
-import { l as syncTaskView } from "./git-sync-LQIVMNxO.mjs";
-//#region src/commands/git-sync/cancel-task.ts
-var cancel_task_default = defineMetabaseCommand({
-	meta: {
-		name: "cancel-task",
-		description: "Cancel the running git-sync task"
-	},
-	capabilities: {
-		minVersion: 60,
-		tokenFeature: "remote_sync"
-	},
-	worktree: "scoped",
-	details: WORKTREE_SCOPE_DETAIL,
-	args: {
-		...outputFlags,
-		...profileFlag,
-		...connectionFlags,
-		...worktreeFlag
-	},
-	outputSchema: SyncTask,
-	examples: ["mb git-sync cancel-task", "mb git-sync cancel-task --json"],
-	async run({ ctx, getClient, getWorktree }) {
-		const mb = await getClient();
-		const scope = await getWorktree();
-		const params = scope === null ? {} : { worktree_id: scope.id };
-		const task = await mb.gitSync.cancelTask(params);
-		renderSummary(task, syncTaskView, `Requested cancellation of ${task.sync_task_type} task #${task.id}.`, ctx);
-	}
-});
-//#endregion
-export { cancel_task_default as default };

package/dist/card-RlzLDB2z.mjs

@@ -1,24 +0,0 @@
-import { t as defineCommandGroup } from "./group-YN6jj2AN.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-oAAgU5uE.mjs").then((mod) => mod.default),
-		get: () => import("./get-CWf46UFu.mjs").then((mod) => mod.default),
-		query: () => import("./query-Bka77J62.mjs").then((mod) => mod.default),
-		alerts: () => import("./alerts-DmwyyBfW.mjs").then((mod) => mod.default),
-		create: () => import("./create-ByuJ6T4k.mjs").then((mod) => mod.default),
-		update: () => import("./update-CpLEEbiJ.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-BZEu6UfT.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { card_default as default };

package/dist/collection-Bhe20ckt.mjs

@@ -1,20 +0,0 @@
-import { t as defineCommandGroup } from "./group-YN6jj2AN.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-Dg2XeDON.mjs").then((mod) => mod.default),
-		get: () => import("./get-DwdMvWXU.mjs").then((mod) => mod.default),
-		items: () => import("./items-Cv6iAzrI.mjs").then((mod) => mod.default),
-		tree: () => import("./tree-DtyJhD54.mjs").then((mod) => mod.default),
-		create: () => import("./create-D0anrINz.mjs").then((mod) => mod.default),
-		archive: () => import("./archive-DCjdICg7.mjs").then((mod) => mod.default)
-	}
-});
-//#endregion
-export { collection_default as default };

package/dist/create-DwrhcI8r2.mjs

@@ -1,144 +0,0 @@
-import { i as ConfigError } from "./predicates-Bkm2IoeX.mjs";
-import { H as profileFlag, R as connectionFlags, V as outputFlags, p as renderSummary } from "./cli.mjs";
-import { A as readProfileRecord, I as writeProfileWorktree, t as defineMetabaseCommand } from "./runtime-CNAZ_FuR.mjs";
-import { o as SyncImportResult } from "./git-sync-DLzJrdMi.mjs";
-import { n as WorktreeCompact, t as Worktree } from "./worktree-xAro1xAB.mjs";
-import { n as parseWaitFlags, t as gitSyncWaitFlags } from "./wait-flags-DzytMEG8.mjs";
-import { a as throwIfFailedTask, i as taskPollOptions, n as formatSyncTask } from "./sync-task-G1K47Nvn.mjs";
-import { z } from "zod";
-//#region src/commands/worktree/create.ts
-const WorktreeCreateResult = z.object({
-	worktree: Worktree,
-	branch_created: z.boolean(),
-	pull: SyncImportResult.nullable()
-});
-const worktreeCreateView = {
-	compactPick: WorktreeCreateResult.extend({ worktree: WorktreeCompact }),
-	tableColumns: [
-		{
-			key: "worktree",
-			label: "Worktree",
-			format: (value) => renderWorktreeCell(value)
-		},
-		{
-			key: "branch_created",
-			label: "Branch created"
-		},
-		{
-			key: "pull",
-			label: "Pull",
-			format: (value) => renderPullCell(value)
-		}
-	]
-};
-function renderWorktreeCell(value) {
-	const parsed = Worktree.safeParse(value);
-	return parsed.success ? `${parsed.data.id} (${parsed.data.branch})` : "—";
-}
-function renderPullCell(value) {
-	const parsed = SyncImportResult.safeParse(value);
-	if (!parsed.success) return "—";
-	return parsed.data.task_id === null ? "no task" : `task #${parsed.data.task_id}`;
-}
-var create_default = defineMetabaseCommand({
-	meta: {
-		name: "create",
-		description: "Create a git-sync worktree for a branch and pull the branch into it"
-	},
-	capabilities: {
-		minVersion: 64,
-		tokenFeature: "remote_sync"
-	},
-	worktree: "any",
-	details: "A worktree is bound to its branch for life. The branch is created on the remote first when it is missing, then the branch's content is pulled into the worktree so the checkout starts in sync.",
-	args: {
-		...outputFlags,
-		...profileFlag,
-		...connectionFlags,
-		branch: {
-			type: "positional",
-			description: "Branch to check out",
-			required: true
-		},
-		pull: {
-			type: "boolean",
-			description: "Import the branch into the new worktree (default: true; --no-pull skips it)",
-			default: true
-		},
-		createBranch: {
-			type: "boolean",
-			description: "Create the branch on the remote when it is missing (default: true; --no-create-branch assumes it exists)",
-			default: true,
-			alias: "create-branch"
-		},
-		pin: {
-			type: "boolean",
-			description: "Pin the profile to the new worktree so every later command runs inside it",
-			default: false
-		},
-		...gitSyncWaitFlags
-	},
-	outputSchema: WorktreeCreateResult,
-	examples: [
-		"mb worktree create feat/transforms",
-		"mb worktree create feat/transforms --pin --json",
-		"mb worktree create feat/transforms --no-create-branch --no-pull"
-	],
-	async run({ args, ctx, getClient, getResolvedConfig }) {
-		const branch = args.branch.trim();
-		if (branch === "") throw new ConfigError("invalid branch: branch name must not be blank");
-		const wait = parseWaitFlags(args);
-		const profile = (await getResolvedConfig()).profile;
-		await assertPinAllows(profile, branch);
-		const mb = await getClient();
-		const branchCreated = args.createBranch ? await ensureBranch(mb, branch) : false;
-		const worktree = await mb.gitSync.createWorktree({ branch });
-		const pull = args.pull ? await pullBranch(mb, worktree.id, branch, wait) : null;
-		if (args.pin) await writeProfileWorktree(profile, {
-			id: worktree.id,
-			branch: worktree.branch
-		});
-		const result = {
-			worktree,
-			branch_created: branchCreated,
-			pull
-		};
-		renderSummary(result, worktreeCreateView, () => summarize(result, profile, args.pin), ctx);
-		throwIfFailedTask(pull?.final ?? null, "import");
-	}
-});
-async function assertPinAllows(profile, branch) {
-	const pin = (await readProfileRecord(profile))?.worktree ?? null;
-	if (pin === null || pin.branch === branch) return;
-	throw new ConfigError(`profile "${profile}" is pinned to worktree ${pin.id} (${pin.branch}); refusing to create a worktree for branch "${branch}"`);
-}
-async function ensureBranch(mb, branch) {
-	const { data } = await mb.gitSync.branches();
-	if (data.includes(branch)) return false;
-	await mb.gitSync.createBranch({
-		name: branch,
-		checkout: false
-	});
-	return true;
-}
-async function pullBranch(mb, worktreeId, branch, wait) {
-	const params = {
-		branch,
-		expected_branch: branch,
-		worktree_id: worktreeId
-	};
-	if (wait.enabled) params.wait = taskPollOptions(wait.schedule);
-	return mb.gitSync.import(params);
-}
-function summarize(result, profile, pinned) {
-	const origin = result.branch_created ? " (branch created on the remote)" : "";
-	const lines = [`Created worktree ${result.worktree.id} for branch "${result.worktree.branch}"${origin}.`];
-	if (result.pull === null) lines.push("Skipped the initial pull; the worktree is empty until you import into it.");
-	else if (result.pull.final !== null && result.pull.final !== void 0) lines.push(formatSyncTask(result.pull.final));
-	else if (result.pull.task_id === null) lines.push(result.pull.message ?? "Nothing to import.");
-	else lines.push(`Started import task #${result.pull.task_id}.`);
-	if (pinned) lines.push(`Pinned profile "${profile}" to worktree ${result.worktree.id}.`);
-	return lines.join("\n");
-}
-//#endregion
-export { create_default as default };