@wrangled/cli 0.3.15 → 0.3.17

package/dist/guide.js

@@ -168,7 +168,7 @@ To suggest a fact, write it as JSON and run \`${cli} facts propose --file fact.j
 
 ## Ad tags
 
-Ads not made here (built by hand or by an agency, names in no pattern) get the marketing grammar's tags (docs/marketing-grammar.md) by Meta ad id. \`${cli} ads tags\` lists them (\`--ad <id>\`, \`--status proposed|confirmed|rejected|replaced\`, \`--limit <n>\`, \`--json\`); by default the live ones, proposed and confirmed. A proposed tag is usable at once, but not yet confirmed; only an Owner or Admin confirms, rejects or changes tags, in the app.
+Ads not made here (built by hand or by an agency, names in no pattern) get the marketing grammar's tags (docs/marketing-grammar.md) by Meta ad id. \`${cli} ads tags\` lists them (\`--ad <id>\`, \`--status proposed|confirmed|rejected|replaced\`, \`--limit <n>\`, \`--json\`); by default the live ones, proposed and confirmed. A proposed tag is usable at once, but not yet confirmed; only an Owner or Admin confirms, rejects or changes tags, on the app's Ad tags page.
 
 To suggest tags, write them as JSON and run \`${cli} ads tag --file tags.json\` (or pipe it on stdin), up to 500 ads at a time: \`{"ads": [{"ad_id": "120214567890123", "tags": {"angle": "discovery", "desire": "money", "hook_spot": "spoken", "hook_text": "$29,000 is the smallest lead", "hook_kind": "big_win", "format": "video", "style": "presenter", "tag_reasons": {"worry": "none"}}, "confidence": "medium", "evidence": {"ad_name": "County lead v2", "transcript_start": "$29,000 is the smallest lead"}}]}\`. The tag fields are \`marketing\`, \`offer_key\`, \`landing_funnel_key\`, \`landing_step_key\`, \`persona\`, \`awareness\`, \`concept\`, \`angle\`, \`desire\`, \`hook_spot\`, \`hook_text\`, \`hook_kind\`, \`hook2_spot\`, \`hook2_kind\`, \`format\`, \`style\`, \`speaker\`, \`cta\`, \`proof\` and \`worry\`; leave out what you did not judge. A part with no value goes in \`tag_reasons\` as \`none\` (nothing on its list applies) or \`unclear\` (too little to judge, never \`high\` confidence). Confidence is \`high\`, \`medium\` or \`low\`. A value off its list is refused with the allowed values. New tags replace an ad's proposed ones, which stay as \`replaced\`; an ad whose tags a person confirmed is kept as it is.
 

package/dist/main.js

@@ -686,13 +686,14 @@ const commands = {
         },
     },
     "content status": {
-        usage: "content status <sku | item-id> <status> [--platform <platform> --external-id <id>]",
+        usage: "content status <sku | item-id> <status> [--platform <platform> [--object-type <type>] --external-id <id>]",
         async run(args, options) {
             if (args.length !== 2)
-                throw new CliError("Usage: content status <sku | item-id> <status> [--platform <platform> --external-id <id>]", exitCodes.usage);
+                throw new CliError("Usage: content status <sku | item-id> <status> [--platform <platform> [--object-type <type>] --external-id <id>]", exitCodes.usage);
             const content = await api(await resolveConnection(options.apiUrl), `/api/v1/content/${encodeURIComponent(args[0])}/status`, {
                 status: args[1],
                 ...(options.platform === undefined ? {} : { platform: options.platform }),
+                ...(options.objectType === undefined ? {} : { objectType: options.objectType }),
                 ...(options.externalId === undefined ? {} : { externalId: options.externalId }),
             });
             printContent(content, options.format);
@@ -1827,6 +1828,8 @@ Options:
   --tool-run <id>       a succeeded tool run content create and edit link; repeat for several
   --run <id>            the agent run making the content (content), or the tool run to record (creatives create)
   --platform, --external-id   where content status launched says it was published, and that platform's id for it
+  --object-type <type>  what that platform's sync calls it (campaign_message or flow_message on klaviyo); needed where
+                        the sync matches several kinds, so its next read joins the item
   --notes <text>        what changed in the version skill publish adds
   --version <n>         the map version funnels show prints (default: the confirmed one)
   --based-on <n>        the map version funnels draft was written from; refused when someone saved since
@@ -1921,6 +1924,7 @@ function parseOptions(argv) {
             platform: { type: "string" },
             library: { type: "string" },
             "external-id": { type: "string" },
+            "object-type": { type: "string" },
             origin: { type: "string" },
             text: { type: "string" },
             mode: { type: "string" },
@@ -2014,6 +2018,7 @@ function parseOptions(argv) {
             platform: values.platform,
             library: values.library,
             externalId: values["external-id"],
+            objectType: values["object-type"],
             origin: values.origin,
             text: values.text,
             mode: values.mode,

package/dist/playbooks.js

@@ -1031,10 +1031,10 @@ When \`resumed\` was true and that story's \`author\` is \`agent_run:<run.id>\`,
 The story's days are the client's days. Find the workspace's reporting time zone:
 
 \`\`\`sh
-${cli} warehouse schema --table daily_funnel --format json > daily-funnel.json
+${cli} guide --format json > guide.json
 \`\`\`
 
-In \`daily-funnel.json\`, the table's \`description\` says "the rest are cut in the workspace reporting time zone, <zone>." Take that zone name, such as \`America/New_York\`. Write this query to \`windows.sql\` with \`${S.timeZone}\` replaced by the zone, keeping the quotes:
+From \`guide.json\`, take its \`timeZone\`, such as \`America/New_York\`. Write this query to \`windows.sql\` with \`${S.timeZone}\` replaced by the zone, keeping the quotes:
 
 \`\`\`sql
 ${storyWindowsQuery}

package/dist/runner/redact.js

@@ -10,7 +10,8 @@ const KEY_LIKE = new RegExp(`(?<![A-Za-z0-9])(?:${[brand.apiKeyPrefix, ...brand.
 const SECRET_PARAM = /\b(access_token|token|api_key|apikey|key|secret|signature|sig|password)=[^&\s"']+/gi;
 const BEARER = /\b(Bearer\s+)[A-Za-z0-9._~+/=-]{8,}/gi;
 const PROVIDER_KEY = /(?<![A-Za-z0-9])sk-[A-Za-z0-9_-]{16,}/g;
-const CREDENTIAL_ASSIGNMENT = /(["']?)([A-Za-z0-9_.-]*(?:key|token|secret|password|passwd|authorization|credential)[A-Za-z0-9_.-]*)\1(\s*[:=]\s*)(["']?)([^\s"'&,;}]{8,})/gi;
+// Starts only where a run of name characters starts, so one long run is not rescanned from each of its letters.
+const CREDENTIAL_ASSIGNMENT = /(["']?)(?<![A-Za-z0-9_.-])((?=[A-Za-z0-9_.-]*?(?:key|token|secret|password|passwd|authorization|credential))[A-Za-z0-9_.-]+)\1(\s*[:=]\s*)(["']?)([^\s"'&,;}]{8,})/gi;
 /** Known secrets, credential parameters, key-shaped strings, bearer tokens and credential-named values replaced. */
 export function redact(text, secrets) {
     let out = text;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wrangled/cli",
-  "version": "0.3.15",
+  "version": "0.3.17",
   "description": "Command-line access to your marketing data warehouse, for people and coding agents",
   "type": "module",
   "bin": {