@koda-sl/baker-cli 0.470.0 → 0.471.0

package/README.md

@@ -1527,8 +1527,11 @@ baker analytics sources --map --source <id> --field email={{contact.email}} --fi
 baker analytics sources --create-hubspot --property lifecyclestage --value customer   # an event HubSpot keeps for Baker each time the property changes
 baker analytics sources --create-hubspot --property deal_value --operator greaterThan --value 1000   # any condition a Form's filter can say
 baker analytics sources --map --source <id> --field email={{work_email}} --field value={{deal_value}} --field currency=EUR   # repoint a HubSpot read
+baker analytics sources --create-activecampaign --events subscribe,deal_update   # ActiveCampaign's webhook sends these; each is an activecampaign.<event>
 ```
 
+**ActiveCampaign events.** `--create-activecampaign [--events …] [--name …] [--account <id>]` makes a source that ActiveCampaign's own webhook sends to — set up on the account when the chat is published (at once outside a chat), deleted when the source is removed. Each arrival is an event named `activecampaign.<event>` (`activecampaign.subscribe`, `activecampaign.deal_update`, …), about its contact, with the rest of the payload as `properties.*` — the name a scheduled agent on `event.received` is narrowed to.
+
 **Sources: where events reach Baker from a server.** Measure → Sources is three built-in doors — the Baker landings, the website tag, and **the client's own server** — plus the connections Baker reads (HubSpot today). `--server` prints the server's one address: made once, the same for ever, `counting` at once, Baker's own format (`sending-events` is the contract; `X-Baker-Mode: test` rehearses). A HubSpot event is a trigger in HubSpot's own words, kept by HubSpot's journal each time the property changes and counted within a minute. `--create --name <tool>` still makes an address for a tool that cannot be told what to send — its first send is a masked sample counted as nothing until `--map` confirms the rows — but the dashboard no longer offers those; a tool worth reading is a connection, requested from the Sources page. Each `--field` is a **template**: text with `{{path}}` mentions, one thing per mention (`--field currency=EUR` types a value, `--field first_name="{{who.first}} {{who.last}}"` joins two; there is no `{{a|b}}` fallback); a bare path is read as its mention when the sample has it. From then on every arrival is an ordinary event carrying `baker_source: <name>`, listed by `feed --source <name>`, and `--pause`, `--resume` and `--remove` are by `--source <id>`.
 
 **`--preview` then `--create-hubspot --property <name> [--operator <op>] --value <value>… [--name <name>] [--field <field>=<template>…] [--amount-property <n> --currency <c>]`: a HubSpot event.** HubSpot keeps each change to the property for Baker, filtered to the condition — on any plan, nothing to set up in HubSpot, an account of any size — and every contact whose new value satisfies the condition is one event, within a minute, named after the source (default: the trigger's words). The condition is any a Form's filter can say, by the property's kind: `is` / `isNot` (a dropdown, `--value` repeated for several), `contains` / `startsWith` / `endsWith` (text), `greaterThan` / `lessThanOrEqual` … (numbers), `isAfter` / `isBetween` (dates, `YYYY-MM-DD`), `isEmpty` / `isNotEmpty` (any); `--operator` is `is` when unsaid. Names, kinds and operators come from `baker hubspot contacts properties` and row properties from `baker hubspot contacts fields`; `--preview --property … [--operator …] --value … [--field …] [--contact <id or email>]` says how many contacts satisfy it today (NOT counted — only contacts that come to satisfy it from now on are) and returns `preview.record`, the one most recently there or the one asked for, to check every row against before making anything. `--set-trigger --source <id> --property … [--operator …] --value …` changes what an event watches later: the rows stay and `countingSince` moves to now. The connection must be allowed to read contacts, and a refusal names the reconnect. `counting` at once, no URL; the source carries `hubspot { property, propertyLabel, kind, operator, values, valueLabels }`, `countingSince`, `listening` (whether HubSpot has been told to keep its changes: `listening`, `not_configured` or `failed`, with a `detail`), `lastError` and `mapping` — the same field → template table as an address, over the contact's properties plus `{{id}}`, defaulting to HubSpot's standard ones (email, phone, the contact id, name, address, `hs_google_click_id`, `hs_facebook_click_id`); a `--field` row at creation replaces the default it names, `--map --field` replaces the whole set later, and `--amount-property … --currency …` is the short spelling for the `value` and `currency` rows. `--field properties.<name>=<template>` adds an extra property of the event (`--field properties.plan={{plan_tier}}`): it breaks the event down on Measure → Events and a send reads it back as `{{properties.<name>}}`. A deal is watched the same way with `--object deal`, and a lead with `--object lead` (`baker hubspot leads properties|fields`) — where HubSpot records qualification and disqualification as the lead's stage. A deal's or a lead's event is about its contacts (`--contacts every|first`), read as `{{contact.<name>}}`; a lead has no amount. Leads need Sales Hub Professional or Enterprise. Where the event is sent on (Meta, Google Ads…) is `sends`, edited on the event's own card on the Sources page.
@@ -1858,6 +1861,38 @@ baker ga4 draft clear
 
 ---
 
+### ActiveCampaign reads (`baker activecampaign`)
+
+Read the connected ActiveCampaign account live; nothing is stored and nothing in ActiveCampaign changes.
+
+```bash
+baker activecampaign account                                   # contacts, site tracking on/off + tracking account id, allowed domains, event tracking
+baker activecampaign campaigns [--status completed] [--since 2026-09-01] [--limit 20]   # email reports, most recently sent first
+baker activecampaign automations [--active-only]               # on/off, entered/exited, what starts each one
+baker activecampaign contacts [--id <contact id> | --email a@b.com | --tag <id|name> | --list <id|name> | --search <text>] [--limit 20]
+baker activecampaign deals [--pipeline <id|title>] [--stage <id|title>] [--status open|won|lost] [--owner <id|username|email>]
+baker activecampaign pipelines | lists | tags [--search <text>] | fields | users
+```
+
+A contact looked up by `--id` or `--email` also carries its `tags` and its `activity`: custom events, page visits, campaign emails sent, opened and clicked, automation runs and list subscriptions. Campaign rows carry `sends`, `opens`, `uniqueOpens`, `clicks`, `uniqueClicks`, `unsubscribes`, `hardBounces`, `softBounces` and `rates` (`open`, `click`, `unsubscribe` and `bounce` as shares of sends; `clickToOpen` as unique clicks over unique opens; `null` before anything is sent). Deal values are in the currency's major units, and `totals` sums every matching deal per currency. Every command takes `--account <id>` when the company has more than one ActiveCampaign connection, and `--full` adds each row's untouched ActiveCampaign payload as `raw`. Nothing connected answers `NO_ACTIVECAMPAIGN_CONNECTION`, a key ActiveCampaign stopped accepting `ACTIVECAMPAIGN_RECONNECT_REQUIRED` — both with a `request_connection` fix.
+
+### ActiveCampaign changes (`baker activecampaign stage` / `unstage` / `drafts`)
+
+Stage a custom contact field, list, tag or deal pipeline on the connected ActiveCampaign account. Nothing changes in ActiveCampaign until the chat is published; then each change is created — or, when the account already has it (a field by its personalization tag, the rest by name), reused rather than duplicated.
+
+```bash
+baker activecampaign stage field --utm                                   # UTM_SOURCE, UTM_MEDIUM, UTM_CAMPAIGN, UTM_CONTENT, UTM_TERM
+baker activecampaign stage field --title "Plan" --type dropdown --options "Basic,Pro"
+baker activecampaign stage list --name "Webinar sign-ups"
+baker activecampaign stage tag --name "hot-lead"
+baker activecampaign stage pipeline --title "Inbound" --stages "New lead,Qualified,Won" --currency usd
+baker activecampaign drafts [--chat <id>]                                # what is staged; after Publish, what happened to each
+baker activecampaign unstage <ref|name|perstag>                          # drop one staged change
+baker activecampaign unstage --all                                       # drop every staged change
+```
+
+A field is put on every list. Field types: `text`, `textarea`, `date`, `datetime`, `dropdown`, `listbox`, `radio`, `checkbox`, `hidden`; `dropdown`, `listbox`, `radio` and `checkbox` need `--options`. A new pipeline gets exactly `--stages`; an existing one only gains the stages it lacks. Every `stage` takes `--account <id>` when the company has more than one ActiveCampaign connection.
+
 ### Google Search Console (`baker gsc`)
 
 GSC commands for PPC-SEO arbitrage, brand halo analysis, and negative keyword discovery.
@@ -3881,13 +3916,14 @@ baker flows options calendly                        # what a step/destination ca
 baker flows connect contact --node book --resource <id>          # fill a Calendly/SavvyCal/GoHighLevel step yourself
 baker flows connect contact --side-effect se-gsheet-1 --resource <spreadsheetId>   # a sheet Baker can reach (--tab to pick the tab)
 baker flows connect contact --side-effect se-gsheet-1 --new-sheet "Contact leads" --columns "Name,Email"   # create one and wire it
-baker flows connect contact --side-effect se-pipedrive-1         # Pipedrive / GoHighLevel contact: the account is the destination
+baker flows connect contact --side-effect se-pipedrive-1         # Pipedrive / GoHighLevel / ActiveCampaign contact: the account is the destination
 baker flows connect contact --side-effect se-email-1 --email "ana@x.com, luis@x.com" --subject "New lead — Contact"   # an email destination: the agent states it, never a card
 baker flows connect contact --side-effect se-httpWebhook-1 --url https://hooks.example.com/lead   # a webhook that needs no token
 baker flows connect contact --all --type googleSpreadsheet --same-as madrid:se-gsheet-1   # copy another Form's destination
 baker flows map contact --from map.json --write     # a whole mapping at once — past ~3 fields, use this
 baker flows map contact --map A=nombre --write      # one or two fields
 baker flows map contact --hubspot-form <guid> --from map.json --write   # HubSpot: field types read off the form
+baker flows map contact --map email=email --map 'tags="withbaker-"+tracking:page_path' --write   # ActiveCampaign: fields read off the account; tag each lead with its page
 baker flows map contact --side-effect <id> --hubspot-form <guid> --prune-missing --write   # drop dead mappings
 baker flows map contact --from map.json --replace --write   # the slot becomes exactly this; drops everything not named
 baker flows normalize contact --write              # repairs a nulled optional; runs pre-commit anyway
@@ -3897,13 +3933,13 @@ Notes:
 
 - **`schema` takes the kind as an argument because `hubspot` is both** — a node type (embeds a form on the page) and a side-effect type (fires a behavioural event). They are different things with one name.
 - **`connect` wires a HubSpot form without asking the user.** When HubSpot is connected and the agent knows which form is meant, `baker flows connect <slug> --hubspot-form <formId> [--side-effect <id>]` attaches the account and the form to a `hubspotForm` side effect (`--all`: every one in the Form still missing it, never repointing one already wired) — the same thing the chat card writes, sealed by Baker so the config never passes through the agent. It refuses a form with spam prevention (captcha) on, and returns `destination.formGuid` for `map --hubspot-form`. The card (`request_flow_input`) stays for an unconnected account or an ambiguous choice.
-- **`options` + `connect` do the same for every other connected platform.** `baker flows options <kind>` lists what the connected account holds (Calendly events, SavvyCal links, GoHighLevel calendars and forms, the Google spreadsheets Baker can reach); `connect --node|--side-effect <id> --resource <id>` writes exactly what the card would. Pipedrive and a GoHighLevel contact take no resource. `--new-sheet` creates a spreadsheet in the connected Google account (Google only lets Baker reach sheets it created or the user chose), `--same-as <slug>:<id>` copies another Form's wired destination, `--all --type <kind>` fills every unwired one of a kind. Nothing connected answers `NOT_CONNECTED` with the `request_connection` fix; several accounts connected need `--account <id>`.
+- **`options` + `connect` do the same for every other connected platform.** `baker flows options <kind>` lists what the connected account holds (Calendly events, SavvyCal links, GoHighLevel calendars and forms, the Google spreadsheets Baker can reach); `connect --node|--side-effect <id> --resource <id>` writes exactly what the card would. Pipedrive, a GoHighLevel contact and an ActiveCampaign contact take no resource. `--new-sheet` creates a spreadsheet in the connected Google account (Google only lets Baker reach sheets it created or the user chose), `--same-as <slug>:<id>` copies another Form's wired destination, `--all --type <kind>` fills every unwired one of a kind. Nothing connected answers `NOT_CONNECTED` with the `request_connection` fix; several accounts connected need `--account <id>`.
 - **`--email` / `--url` replace a destination whole, so they leave alone what only the user can set.** `--all --email` passes over an email that replies to the visitor's own answer (and says so in its hints); naming one is refused. A webhook that sends a credential keeps its address until the user re-enters both through `request_flow_input`. Unreadable settings are also left alone by default. For one unreadable email, `--replace-unreadable --email <complete list> --subject <text>` replaces the old setup when the user intends replacement, without revealing it. Never use this to add to an unknown recipient list; it cannot override `--all`, a known visitor reply, or a webhook. `flows show` reads back only destinations sealed for this company.
 - **Configure the destination before you map.** `columnMapping`/`fieldMapping` describe a *specific* destination — sheet columns, a portal's field names — that only `connect` or `request_flow_input` can set, and both return it. A mapping written first is valid JSON that ships and drops every submission; `verify` blocks the half-wired result.
-- **`map` reads the record shape off the side effect's type.** One property name, four record shapes: a Sheet is addressed by column letter, HubSpot by property name, Pipedrive and GoHighLevel by field key, Crmble by field id. That is why there is no `--key`, and why `--entity` and `--custom`/`--standard` are required rather than defaulted.
+- **`map` reads the record shape off the side effect's type.** One property name, four record shapes: a Sheet is addressed by column letter, HubSpot by property name, Pipedrive and GoHighLevel by field key, ActiveCampaign by field key (`email`, `firstName`, a custom field's id, `tags`, `lists`, `automations`, `note`, or a qualified `deal.title` / `account.name` / `event.name`), Crmble by field id. That is why there is no `--key`, and why `--entity` and `--custom`/`--standard` are required rather than defaulted for Pipedrive and GoHighLevel.
 - **A mapping is usually eight to fifteen fields, so `--from` is the main door.** It takes `{ "map": { "<destField>": "<value>" } }` from a file or stdin; `--map` flags are for one or two. Both produce identical output.
 - **Most CRM fields are not fed by a form field.** The value grammar is a bare form field (`nombre`), `field:Step.name` when two steps share a name, `tracking:utm_source`, `global:Name`, `code:exposed_value`, a `"literal"`, or any of those joined with `+`. Tracking names are validated against the engine's own `TRACKING_FIELD_IDS`, read out of the workspace rather than copied — attribution columns are the most common CRM mapping there is, and they were unexpressible before.
-- **A CRM mapping's field type is derived from the destination, never defaulted.** Every CRM record types `fieldType` as required, and it is the account's answer, not the agent's — HubSpot builds its submission key as `<objectTypeId>.<fieldType>.<fieldName>`, so a wrong type on a date property skips the `YYYY-MM-DD` coercion and the value is dropped. `--hubspot-form <formGuid>` (or `"hubspotForm"` in the mapping file) reads every property's type and object type off the form, so nothing has to state one. Where a destination cannot be read, put the type on the LEFT — `c0ffee:varchar=email` — which leaves `:` on the right for the value kinds. A mapping with no type from either route is refused, never written without one.
+- **A CRM mapping's field type is derived from the destination, never defaulted.** Every CRM record types `fieldType` as required, and it is the account's answer, not the agent's — HubSpot builds its submission key as `<objectTypeId>.<fieldType>.<fieldName>`, so a wrong type on a date property skips the `YYYY-MM-DD` coercion and the value is dropped. `--hubspot-form <formGuid>` (or `"hubspotForm"` in the mapping file) reads every property's type and object type off the form, so nothing has to state one. An `activeCampaignContact` mapping reads the connected ActiveCampaign account's field list on every call — no flag — so its types (`standard`, `custom`, `tags`, `lists`, `automations`, `deal`, `account`, `note`, `event`) are derived too, a custom field may be named by its id, personalization tag or label (stored as the id) — or as `custom.<TAG>` for one that is only staged so far, resolved when each lead is sent — and a name the account does not have is refused with the list of the ones it does. Its `tags`, `lists` and `automations` mappings are comma-separated names or ids that may mix text and variables, e.g. `tags="withbaker-"+tracking:page_path`; `deal.title` or `deal.pipeline` creates a deal (`deal.value` in major units, `deal.stage` / `deal.owner` by name or id), `account.name` finds or creates the lead's company, `note` leaves a note and `event.name` records an event (it needs the account's event key on the connection). The answer's `hints` name a list, automation, pipeline, stage or user the account does not have, a deal nothing creates, and an event with no event key. Where a destination cannot be read, put the type on the LEFT — `c0ffee:varchar=email` — which leaves `:` on the right for the value kinds. A mapping with no type from either route is refused, never written without one.
 - **`email` maps like anything else**, into `body.fields`, while `body.format` is `"json"`. A `"body"`-format email is one written message with no keys to address, and `map` refuses it rather than reshaping the body.
 - **A Form can look finished and be losing every lead.** HubSpot refuses a submission that names a property it does not have — the whole submission, not the field — and the visitor still reaches the thank-you screen. Baker re-checks each Form's destination and `baker flows show <slug>` reports what it found: `data.drift[]` carries **one entry per drifted destination** — a Form with two HubSpot side effects has two mappings, two form ids and two repairs — each with the severity, a sentence naming the fields, the side-effect id and that destination's HubSpot form id; the hints carry one repair command per entry. `drift: null` means the check could not be made and is not the same answer as `[]`.
 - **`--prune-missing` is the repair; `--replace` is not.** With `--side-effect <id>` and `--hubspot-form <guid>`, `--prune-missing` drops exactly the mappings whose destination field is absent from that form's live field list, names each one in `dropped`, and leaves every other mapping alone. It needs no `--map` and runs on its own. `--replace` drops everything the call does not name, so using it to remove three dead mappings means first restating the ten good ones correctly.
@@ -3913,7 +3949,7 @@ Notes:
 - **`normalize` exists so authoring a Form does not require remembering an exception.** `oauthProviderId` is an optional `string`, so a `null` there fails typecheck one build later — it is repaired and staged instead of rejected.
 
 - **Secrets never travel through this CLI or the chat.** `show` reports only whether each field is configured (`[set]`/`[missing]`, `[connected]`/`[needs connection]`, selected/not selected) — never a value. Configured secrets appear only as `[configured]` ciphertext markers.
-- Confidential side-effect types: `httpWebhook`, `zapier`, `crmble` (typed credentials); `pipedrive`, `googleSpreadsheet`, `hubspotForm`, `goHighlevelContact` (OAuth connection + resource); `email`. Widget node types needing a resource pick: `calendly`, `savvycal`, `hubspot`, `hubspotMeeting`, `highlevel`, `highlevelForm`.
+- Confidential side-effect types: `httpWebhook`, `zapier`, `crmble` (typed credentials); `pipedrive`, `googleSpreadsheet`, `hubspotForm`, `goHighlevelContact`, `activeCampaignContact` (connected account + resource); `email`. Widget node types needing a resource pick: `calendly`, `savvycal`, `hubspot`, `hubspotMeeting`, `highlevel`, `highlevelForm`.
 - `request_flow_input` changes stage on the chat's branch and apply when the chat is published; discarding the chat drops them.
 
 ### Action Items (`baker actions`)

package/dist/{account-GIZWP5QF.js → account-SP2RA2XD.js}

@@ -2,7 +2,7 @@ import {
   csvOrJson,
   handleLinkedinError,
   resolveAccountIdArg
-} from "./chunk-XQ2FGDOQ.js";
+} from "./chunk-7NWOGEAW.js";
 import {
   writeAdsJson,
   writeAdsOutput
@@ -10,7 +10,7 @@ import {
 import {
   NO_CACHE_ARG
 } from "./chunk-Z3GHDRUA.js";
-import "./chunk-WXC3I4CT.js";
+import "./chunk-XABVEMC3.js";
 import "./chunk-GXDLWBOY.js";
 import "./chunk-GIWHHCD6.js";
 import "./chunk-XQIOCIDO.js";
@@ -68,7 +68,7 @@ Examples:
   },
   subCommands: {
     detail: accountDetailCommand,
-    "url-params": () => import("./write-commands-7FT3MTOZ.js").then((m) => m.accountUrlParamsCommand)
+    "url-params": () => import("./write-commands-JCM6ZMUJ.js").then((m) => m.accountUrlParamsCommand)
   },
   args: accountDetailCommand.args,
   default: "detail"
@@ -76,4 +76,4 @@ Examples:
 export {
   accountCommand
 };
-//# sourceMappingURL=account-GIZWP5QF.js.map
+//# sourceMappingURL=account-SP2RA2XD.js.map

package/dist/{accounts-CQUW36ZY.js → accounts-R2ZLSJEW.js}

@@ -1,7 +1,7 @@
 import {
   csvOrJson,
   handleLinkedinError
-} from "./chunk-XQ2FGDOQ.js";
+} from "./chunk-7NWOGEAW.js";
 import {
   connectedResourceHints
 } from "./chunk-P4NSJS54.js";
@@ -16,7 +16,7 @@ import {
 import {
   NO_CACHE_ARG
 } from "./chunk-Z3GHDRUA.js";
-import "./chunk-WXC3I4CT.js";
+import "./chunk-XABVEMC3.js";
 import "./chunk-GXDLWBOY.js";
 import "./chunk-GIWHHCD6.js";
 import "./chunk-XQIOCIDO.js";
@@ -74,4 +74,4 @@ Examples:
 export {
   accountsCommand
 };
-//# sourceMappingURL=accounts-CQUW36ZY.js.map
+//# sourceMappingURL=accounts-R2ZLSJEW.js.map

package/dist/{accounts-5KDBVRJ2.js → accounts-XG5W4JC4.js}

@@ -9,7 +9,7 @@ import {
   accountsInfluencedRequestSchema,
   influenceParams,
   warmAccounts
-} from "./chunk-A3VUXG5G.js";
+} from "./chunk-YRERFQ7Z.js";
 import "./chunk-GRQ2AXDX.js";
 import {
   TABLE_OUTPUT_FORMATS,
@@ -19,8 +19,8 @@ import {
 } from "./chunk-JM7C6OHU.js";
 import {
   failApi
-} from "./chunk-PYPILVCC.js";
-import "./chunk-WXC3I4CT.js";
+} from "./chunk-53DV3HBZ.js";
+import "./chunk-XABVEMC3.js";
 import "./chunk-GXDLWBOY.js";
 import "./chunk-GIWHHCD6.js";
 import "./chunk-XQIOCIDO.js";
@@ -602,10 +602,10 @@ var accountsCommand = defineCommand({
     warm: warmCommand,
     company: companyCommand,
     campaigns: campaignsCommand,
-    crm: () => import("./crm-I6E2FACM.js").then((m) => m.crmCommand)
+    crm: () => import("./crm-J3HX3ZT6.js").then((m) => m.crmCommand)
   }
 });
 export {
   accountsCommand
 };
-//# sourceMappingURL=accounts-5KDBVRJ2.js.map
+//# sourceMappingURL=accounts-XG5W4JC4.js.map

package/dist/{actions-BDC7CQ3R.js → actions-LZE7K24U.js}

@@ -30,26 +30,26 @@ Examples:
 Full guide: __tooling__/docs/tools/baker/actions.md`
   },
   subCommands: {
-    list: () => import("./list-H7V6MUUV.js").then((m) => m.listCommand),
-    log: () => import("./log-SA4GFECI.js").then((m) => m.logCommand),
-    draft: () => import("./draft-REIQ6JCS.js").then((m) => m.draftCommand),
-    get: () => import("./get-X5B6VCSC.js").then((m) => m.getCommand),
-    status: () => import("./status-TCOUMPJS.js").then((m) => m.statusCommand),
-    claim: () => import("./claim-YXL2HUFU.js").then((m) => m.claimCommand),
-    release: () => import("./release-HJZCWKY6.js").then((m) => m.releaseCommand),
-    create: () => import("./create-7L6SXSPH.js").then((m) => m.createCommand),
-    update: () => import("./update-4NHLEM64.js").then((m) => m.updateCommand),
-    complete: () => import("./complete-VABZEJTL.js").then((m) => m.completeCommand),
-    discard: () => import("./discard-6GTJKV37.js").then((m) => m.discardCommand),
-    reopen: () => import("./reopen-3VQ4NYZ5.js").then((m) => m.reopenCommand),
-    assign: () => import("./assign-SH76OUMA.js").then((m) => m.assignCommand),
-    members: () => import("./members-KDJBWRU5.js").then((m) => m.membersCommand),
-    link: () => import("./link-4DNY5OSY.js").then((m) => m.linkCommand),
-    unlink: () => import("./unlink-6M577LT6.js").then((m) => m.unlinkCommand),
-    tags: () => import("./tags-NBVQWFS2.js").then((m) => m.tagsCommand)
+    list: () => import("./list-QEPDSHHY.js").then((m) => m.listCommand),
+    log: () => import("./log-S4U4JQ77.js").then((m) => m.logCommand),
+    draft: () => import("./draft-UDDLC7YZ.js").then((m) => m.draftCommand),
+    get: () => import("./get-DC3WBYJD.js").then((m) => m.getCommand),
+    status: () => import("./status-GG6UTBWM.js").then((m) => m.statusCommand),
+    claim: () => import("./claim-KPJXAUQW.js").then((m) => m.claimCommand),
+    release: () => import("./release-B5B7TWMA.js").then((m) => m.releaseCommand),
+    create: () => import("./create-6NJRTWYT.js").then((m) => m.createCommand),
+    update: () => import("./update-4DATQZGJ.js").then((m) => m.updateCommand),
+    complete: () => import("./complete-Y3M6OXPA.js").then((m) => m.completeCommand),
+    discard: () => import("./discard-2357VMCI.js").then((m) => m.discardCommand),
+    reopen: () => import("./reopen-BAE4WPC6.js").then((m) => m.reopenCommand),
+    assign: () => import("./assign-3UKKZ3Q3.js").then((m) => m.assignCommand),
+    members: () => import("./members-3B43WCMP.js").then((m) => m.membersCommand),
+    link: () => import("./link-SJQFQLTY.js").then((m) => m.linkCommand),
+    unlink: () => import("./unlink-ANZSGHCG.js").then((m) => m.unlinkCommand),
+    tags: () => import("./tags-H6MESAFQ.js").then((m) => m.tagsCommand)
   }
 });
 export {
   actionsCommand
 };
-//# sourceMappingURL=actions-BDC7CQ3R.js.map
+//# sourceMappingURL=actions-LZE7K24U.js.map