@wrangled/cli 0.3.56 → 0.3.57

package/dist/articles.js

@@ -0,0 +1,51 @@
+import { createHash } from "node:crypto";
+import { basename } from "node:path";
+import { CliError, exitCodes } from "./api.js";
+// As the server reads an article (src/lib/publishing/wordpress/html.ts): a tag ends at the first > outside quotes.
+const IMG_TAG = /<img\b(?:[^>"']|"[^"]*"|'[^']*')*>/gi;
+const ATTRIBUTE = /(\s+)([^\s"'>/=]+)(?:(\s*=\s*)(?:"([^"]*)"|'([^']*)'|([^\s"'>]+)))?/g;
+/**
+ * Points each <img src> that names a --file (as given, or by its file name) at that file as sha256:<its SHA-256>,
+ * the reference a publisher replaces with the address the file gets where it is published. Other sources are left.
+ */
+export function pointImagesAtFiles(html, files) {
+    if (files.length === 0)
+        return html;
+    const refs = new Map();
+    for (const { path, data } of files) {
+        const ref = `sha256:${createHash("sha256").update(data).digest("hex")}`;
+        for (const name of [path, basename(path), `./${basename(path)}`])
+            refs.set(name, ref);
+    }
+    return html.replace(IMG_TAG, (tag) => {
+        let seen = false;
+        return tag.replace(ATTRIBUTE, (whole, space, name, equals, double, single, bare) => {
+            if (seen || name.toLowerCase() !== "src" || equals === undefined)
+                return whole;
+            seen = true;
+            const ref = refs.get((double ?? single ?? bare ?? "").trim());
+            if (ref === undefined)
+                return whole;
+            const quote = single !== undefined ? "'" : '"';
+            return `${space}${name}${equals}${quote}${ref}${quote}`;
+        });
+    });
+}
+const WORDPRESS = "wordpress:";
+/**
+ * The publisher and target `content publish` sends. `--to wordpress:<site>` fills the target itself, with --status
+ * draft (the default) or publish; any other publisher takes its target as --target JSON, given here parsed.
+ */
+export function publishDestination(to, { target, status }) {
+    if (to.startsWith(WORDPRESS)) {
+        if (target !== undefined)
+            throw new CliError("--to wordpress:<site> sets the target itself; leave out --target.", exitCodes.usage);
+        const site = to.slice(WORDPRESS.length);
+        return { publisher: "wordpress", target: status === undefined ? { site } : { site, status } };
+    }
+    if (status !== undefined)
+        throw new CliError("--status goes with --to wordpress:<site>.", exitCodes.usage);
+    if (target === undefined)
+        throw new CliError(`--to ${to} needs --target '<json>'.`, exitCodes.usage);
+    return { publisher: to, target };
+}

package/dist/guide.js

@@ -93,7 +93,7 @@ To find content, such as "the 10 emails with the best click rate", "our 5 best v
 
 - \`--text "<words>"\` finds words in the current version's subject, headline and body, or in a video's or call recording's transcript. Words are stemmed ("guarantee" finds "guaranteed"); use "quotes" for a phrase and -word to leave a word out.
 - \`--mode meaning\` finds content that means something close to \`--text\`, even in other words: \`--text "saves time"\` also finds "done in five minutes". Results come nearest first, each with its distance (0 is the same meaning) and the closest passage as its words. It takes no \`--sort\` or \`--order\`, and finds only content embedded so far (each hour, new versions and transcripts are embedded).
-- \`--kind\` (ad, email, sms, landing_page, video, social_post, conversation), \`--platform\` (meta, ghl, klaviyo, roezan, bayengage, activecampaign, mailchimp, hubspot, kit, instantly, kajabi, omnisend, google_ads, tiktok, microsoft_ads, pinterest, linkedin, web, youtube, instagram, facebook_page, callrail, zoom, fathom, google_drive, ad_library, workspace, upload) and \`--origin\` (discovered or made) narrow it. \`--from\` and \`--to\` keep content live on those days: from its first day with numbers (or the day the library first saw it) to its last.
+- \`--kind\` (ad, email, sms, landing_page, video, social_post, article, conversation), \`--platform\` (meta, ghl, klaviyo, roezan, bayengage, activecampaign, mailchimp, hubspot, kit, instantly, kajabi, omnisend, google_ads, tiktok, microsoft_ads, pinterest, linkedin, web, wordpress, youtube, instagram, facebook_page, callrail, zoom, fathom, google_drive, ad_library, workspace, upload) and \`--origin\` (discovered or made) narrow it. \`--from\` and \`--to\` keep content live on those days: from its first day with numbers (or the day the library first saw it) to its last.
 - \`--sort\` is \`recent\` (the default, newest first) or any number in the \`content_scorecard\` view, such as \`click_rate\`, \`open_rate\`, \`roas\`, \`spend\` or their \`_30d\` twins for the last 30 days. Content with money in several currencies has a number per currency and sorts by its best. Content without that number comes last. \`--order asc\` turns it around; \`--limit\` is 1 to 50 (default 10).
 - Each result has the item's id or SKU, its words, how many files it has, whether it has a transcript, and its scorecard numbers. \`${cli} content show <sku | item-id>\` prints one item in full: its words, how many versions it has, its transcript and every number; \`--format json\` adds every version, and links to its files.
 - To add marketing that lives somewhere no source connects to, such as a sales video, a webinar recording, a script or an email from another tool, run \`${cli} content capture --kind <kind> --name <name>\` with \`--body\`, \`--file\`, \`--source\` (where it came from) and \`--url\`. It is kept as found, with no SKU, so it is never approved or published; \`--platform upload\` finds these. Videos and audio are transcribed on their own; give \`--transcript @file\` when you already have one, so none is paid for.
@@ -213,7 +213,7 @@ Save anything you make before it goes anywhere: an ad written without a tool, an
 
 ### Publishing
 
-\`${cli} content publish <sku> --to <publisher> --target '<json>' --idempotency-key <key>\` publishes an approved item through one of ${brand.name}'s publishers, adding \`--plan <plan-id>\` when it is part of a launch plan and \`--run <run-id>\` from a hand's run. Only the approved version is published; an item edited after approval must be approved again. The server checks every rule first and refuses with each failure listed, recording nothing: one unfinished send per platform account, and at least 15 seconds between sends to one account. Otherwise it records exactly what it sends before sending it, then saves the platform's ids, marks the item launched, and moves the launch plan to live once all its items are out. For Meta without the \`--run\` of a hand in live mode, nothing is sent: the publication is saved as \`not_sent_practice\` with the full request. A send that may or may not have landed stays \`sending\` and is never retried; \`${cli} content reconcile <publication-id>\` asks the platform and finishes it. The same key returns the same publication. A page host is the publisher \`page_host:<host>\` with the target \`{"site":"...","path":"/..."}\`: it puts an approved landing page's HTML online, tags each link that leaves the page with the SKU, and is never held back by practice mode. \`${cli} content show <sku>\` lists the page's deployments with their ids. \`${cli} content unpublish <deployment-id>\` takes one live page down; the site's other pages stay up, and the deployment records when and by whom. It is refused while a synced Meta ad that is delivering links to the page, naming each ad, because a broken link in a running ad wastes money; \`--force\` takes it down anyway. Never roll a site back in Vercel's dashboard instead: the next deploy brings the rolled-away pages back.
+\`${cli} content publish <sku> --to <publisher> --target '<json>' --idempotency-key <key>\` publishes an approved item through one of ${brand.name}'s publishers, adding \`--plan <plan-id>\` when it is part of a launch plan and \`--run <run-id>\` from a hand's run. Only the approved version is published; an item edited after approval must be approved again. The server checks every rule first and refuses with each failure listed, recording nothing: one unfinished send per platform account, and at least 15 seconds between sends to one account. Otherwise it records exactly what it sends before sending it, then saves the platform's ids, marks the item launched, and moves the launch plan to live once all its items are out. For Meta without the \`--run\` of a hand in live mode, nothing is sent: the publication is saved as \`not_sent_practice\` with the full request. A send that may or may not have landed stays \`sending\` and is never retried; \`${cli} content reconcile <publication-id>\` asks the platform and finishes it. The same key returns the same publication. A page host is the publisher \`page_host:<host>\` with the target \`{"site":"...","path":"/..."}\`: it puts an approved landing page's HTML online, tags each link that leaves the page with the SKU, and is never held back by practice mode. \`${cli} content show <sku>\` lists the page's deployments with their ids. \`${cli} content unpublish <deployment-id>\` takes one live page down; the site's other pages stay up, and the deployment records when and by whom. It is refused while a synced Meta ad that is delivering links to the page, naming each ad, because a broken link in a running ad wastes money; \`--force\` takes it down anyway. Never roll a site back in Vercel's dashboard instead: the next deploy brings the rolled-away pages back. An article (\`${cli} content create --kind article --headline "<title>" --html @post.html --file hero.jpg\`) goes to the client's WordPress site with \`${cli} content publish <sku> --to wordpress:<site> --idempotency-key <key>\`, as a draft, or live with \`--status publish\`. Its images are uploaded once per site and each \`<img src>\` naming a \`--file\` points at the uploaded copy. The site's sign-in is saved first with \`${cli} secrets set wordpress:<site> --file wp.json\`, the file holding \`{"baseUrl": "https://...", "username": "...", "applicationPassword": "..."}\` (an application password made in WordPress under Users, Profile).
 
 The \`meta_ads\` publisher puts an approved ad on Facebook, always paused, in an ad set that already exists, \`--to meta_ads --target '{"accountId": "act_<id>", "adsetId": "<id>"}'\`, or in one made with \`${cli} meta adset publish\` (below), \`"adsetPublicationId": "<id>"\` in place of \`adsetId\`. \`"urlTags": "sku"\` (the default) adds the SKU tracking tags to the link; \`"urlTags": "none"\` sends the link exactly as written, Meta macros such as \`{{ad.name}}\` included. The ad needs pictures or a video (not both), body text and an https link in \`fields.link_urls\` (\`fields.cta\`, such as "Shop now", sets the button; \`fields.bodies\`, \`fields.titles\` and \`fields.descriptions\` add variations). The account, the ad set's campaign and the ad set must all be on the hand's publish list, which only an operator sets, and the ad set and campaign must be in the last Meta sync and not archived. A live send also needs a run of the Facebook ads hand, Meta numbers pulled under 12 hours ago, and room under the daily limit of new ads. The ad is named \`<SKU> | <name>\` and its creative's \`url_tags\` carry the SKU. In practice mode the same command stores the full request for review and sends nothing. Each publication's \`targetSnapshot\` names the campaign and ad set as they were at publish time.
 
@@ -402,7 +402,7 @@ ${cli} tools get <run-id>           show a tool run, waiting for it to finish (-
 ${cli} tools usage [--month <YYYY-MM>] [--by tool|run]   what tool runs cost in a month, per tool or per scheduled run, split by whose key paid
 ${cli} enrich email --file <people.csv | people.json> [--steps <tool,tool>]   find one verified work email per person, cheapest provider first
 ${cli} secrets list                 which provider keys the client has and which key runs use; never the keys themselves
-${cli} secrets set <provider> [--file <path>]   save the client's own provider key from stdin or a file (keys with "Can manage settings")
+${cli} secrets set <provider> [--file <path>]   save the client's own provider key from stdin or a file (keys with "Can manage settings"); wordpress:<site> saves a WordPress site's sign-in
 ${cli} secrets remove <provider>    remove it, so runs use the shared key again
 ${cli} creatives list               list creatives (--status, --kind, --limit)
 ${cli} creatives show <sku>         show one creative with its spec and lineage
@@ -418,6 +418,7 @@ ${cli} content pull <dir> [--kind <kind>] [--platform <p>] [--origin <o>] [--med
 ${cli} content show <sku | item-id> | content edit <sku> [...] --note <why> | content status <sku> <status>
 ${cli} content diff <sku | item-id> [--from <n>] [--to <n>]   what changed between two versions
 ${cli} content publish <sku> --to <publisher> --target '<json>' --idempotency-key <key> [--plan <id>] [--version <n>] [--run <run-id>]   publish an approved item
+${cli} content publish <sku> --to wordpress:<site> [--status publish] --idempotency-key <key>   put an approved article on a WordPress site, as a draft unless --status publish
 ${cli} content reconcile <publication-id>   check whether a publish left sending landed
 ${cli} content unpublish <deployment-id> [--force]   take one deployed landing page down
 ${cli} meta adset publish --plan '<json>' --idempotency-key <key> [--run <run-id>]   make a paused Meta ad set to add ads to

package/dist/main.js

@@ -12,6 +12,7 @@ import { META_AD_CREATE_USAGE, metaAdCreateBody } from "./meta-ad.js";
 import { firstSymlink, inRunFolder, writeFileAtomic } from "./files.js";
 import { scheduleCreateBody, scheduleIdFor, SCHEDULES_CREATE_USAGE } from "./schedules.js";
 import { secretBody, secretProvider, SECRETS_SET_USAGE } from "./secrets.js";
+import { pointImagesAtFiles, publishDestination } from "./articles.js";
 import { dollars, toolUsageReport, toolUsageRequest, TOOLS_USAGE_USAGE } from "./tool-usage.js";
 import { guide, skill } from "./guide.js";
 import { PULL_STATE_FILE, pullContent } from "./pull.js";
@@ -25,6 +26,7 @@ const META_CHANGE_COLUMNS = ["id", "level", "object", "change", "status", "when"
 const GOOGLE_ADS_CHANGE_COLUMNS = ["id", "account", "level", "object", "change", "status", "when", "by", "reason"];
 const SERVER_WAIT_CAP = 50;
 const VOICE_USAGE = "voice [--kind opener|objection|pain|desire|phrase] [--since <YYYY-MM-DD>] [--sort common|useful] [--limit <n>] [--json]";
+const CONTENT_PUBLISH_USAGE = "content publish <sku | item-id> (--to <publisher> --target '<json>' | --to wordpress:<site> [--status draft|publish]) --idempotency-key <key> [--plan <plan-id>] [--version <n>] [--run <run-id>]";
 const META_MOVE_USAGE = 'meta ads move <ad-id> --to-adset <adset-id> --reason "<why>" [--keep-original] [--status active|paused] [--run <run-id>] [--idempotency-key <key>]';
 const OUTBOUND_PUSH_USAGE = `outbound push --to instantly:<campaign-id> (--csv <file> | --table <import_ or agent_ table>) [--dry-run] [--max <n>] [--idempotency-key <key>]`;
 const commands = {
@@ -448,6 +450,9 @@ const commands = {
             const { secret } = await api(connection, secretPath(provider), secretBody(text), "PUT");
             if (options.format === "json")
                 return printJson({ secret });
+            if (secret.provider.startsWith("wordpress:")) {
+                return console.log(`Saved the sign-in for the WordPress site ${secret.provider.slice("wordpress:".length)}. content publish --to ${secret.provider} uses it.`);
+            }
             console.log(`Saved the client's own ${secret.provider} key. Its ${secret.provider} runs now use it instead of the shared one.`);
         },
     },
@@ -858,11 +863,11 @@ const commands = {
         usage: "content create --kind <kind> [--name <name>] [--subject <s>] [--preview <s>] [--headline <s>] [--body <text> | @file] [--html @file] [--fields '<json>' | @file.json] [--file <path> ...] [--tool-run <id> ...] [--run <agent-run-id>] [--note <why>] [--plan <plan-id> [--role <role>]]",
         async run(args, options) {
             if (args.length > 0 || !options.kind)
-                throw new CliError("Usage: content create --kind ad|email|sms|landing_page|video|social_post [...]", exitCodes.usage);
+                throw new CliError("Usage: content create --kind ad|email|sms|landing_page|video|social_post|article [...]", exitCodes.usage);
             const connection = await resolveConnection(options);
             const content = await api(connection, "/api/v1/content", {
                 kind: options.kind,
-                ...(await contentInput(options, connection)),
+                ...(await contentInput(options, connection, async () => options.kind)),
                 ...(options.plan === undefined ? {} : { launchPlanId: options.plan }),
                 ...(options.role === undefined ? {} : { launchPlanRole: options.role }),
             });
@@ -880,7 +885,7 @@ const commands = {
             const connection = await resolveConnection(options);
             const content = await api(connection, "/api/v1/content/captures", {
                 kind: options.kind,
-                ...(await contentInput(options, connection)),
+                ...(await contentInput(options, connection, async () => options.kind)),
                 transcript: options.transcript === undefined ? undefined : { text: await textOrFile(options.transcript), language: options.language },
                 source: options.source,
                 url: options.url,
@@ -1107,7 +1112,7 @@ const commands = {
             if (args.length !== 1)
                 throw new CliError("Usage: content edit <sku | item-id> [--body <text> | @file] [--note <why>] [...]", exitCodes.usage);
             const connection = await resolveConnection(options);
-            const input = await contentInput(options, connection);
+            const input = await contentInput(options, connection, async () => (await api(connection, `/api/v1/content/${encodeURIComponent(args[0])}`)).item.kind);
             if (Object.keys(input).every((k) => k === "runId" || k === "note")) {
                 throw new CliError("content edit needs something to change, such as --body, --subject or --file.", exitCodes.usage);
             }
@@ -1130,17 +1135,19 @@ const commands = {
         },
     },
     "content publish": {
-        usage: "content publish <sku | item-id> --to <publisher> --target '<json>' --idempotency-key <key> [--plan <plan-id>] [--version <n>] [--run <run-id>]",
+        usage: CONTENT_PUBLISH_USAGE,
         async run(args, options) {
-            if (args.length !== 1 || !options.to || options.target === undefined || !options.idempotencyKey) {
-                throw new CliError("Usage: content publish <sku | item-id> --to <publisher> --target '<json>' --idempotency-key <key> [--plan <plan-id>] [--version <n>] [--run <run-id>]", exitCodes.usage);
-            }
+            if (args.length !== 1 || !options.to || !options.idempotencyKey)
+                throw new CliError(`Usage: ${CONTENT_PUBLISH_USAGE}`, exitCodes.usage);
             const version = options.version === undefined ? undefined : Number(options.version);
             if (version !== undefined && !(Number.isInteger(version) && version >= 1))
                 throw new CliError("--version must be a whole number from 1.", exitCodes.usage);
+            const destination = publishDestination(options.to, {
+                target: options.target === undefined ? undefined : await parseJson(options.target, "--target"),
+                status: options.status,
+            });
             const { publication } = await api(await resolveConnection(options), `/api/v1/content/${encodeURIComponent(args[0])}/publish`, {
-                publisher: options.to,
-                target: await parseJson(options.target, "--target"),
+                ...destination,
                 idempotencyKey: options.idempotencyKey,
                 ...(options.plan === undefined ? {} : { launchPlanId: options.plan }),
                 ...(version === undefined ? {} : { version }),
@@ -3771,9 +3778,12 @@ const INLINE_CONTENT_BYTES = 3 * 1024 * 1024;
  * The request body the content create and edit flags describe; flags not given are left out. Files go base64 while
  * they and the HTML fit in one request; any other file goes to storage first and is named by its upload id.
  */
-async function contentInput(options, connection) {
-    const html = options.html === undefined ? undefined : await textOrFile(options.html);
-    const files = await sendableFiles(await readContentFiles(options.files), connection, html === undefined ? 0 : Buffer.byteLength(html));
+async function contentInput(options, connection, kindOf) {
+    const read = await readContentFiles(options.files);
+    const given = options.html === undefined ? undefined : await textOrFile(options.html);
+    // Only an article's publisher swaps sha256: sources for uploaded files; any other kind keeps its HTML as written.
+    const html = given !== undefined && read.length > 0 && (await kindOf()) === "article" ? pointImagesAtFiles(given, read) : given;
+    const files = await sendableFiles(read, connection, html === undefined ? 0 : Buffer.byteLength(html));
     const input = {
         name: options.name,
         subject: options.subject,
@@ -3801,7 +3811,7 @@ async function readContentFiles(paths) {
         const contentType = FILE_TYPES[extname(path).toLowerCase()];
         if (!contentType)
             throw new CliError(`${path}: --file takes ${Object.keys(FILE_TYPES).join(", ")} files.`, exitCodes.usage);
-        read.push({ contentType, data: await readFile(await inRunFolder(path)) });
+        read.push({ path, contentType, data: await readFile(await inRunFolder(path)) });
     }
     return read;
 }

package/package.json

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