kenso 0.1.13 → 0.1.16

package/dist/kenso.js

@@ -2397,7 +2397,7 @@ var VERSION;
 var init_version = __esm({
   "src/core/version.ts"() {
     "use strict";
-    VERSION = true ? "0.1.13" : "0.0.0-dev";
+    VERSION = true ? "0.1.16" : "0.0.0-dev";
   }
 });
 
@@ -8395,10 +8395,10 @@ async function readCampaign(ctx, campaignId) {
   const channel = isRecord4(campaign) && typeof campaign.channel === "string" ? campaign.channel.toLowerCase() : "";
   return { linkedInOnly: LINKEDIN_ONLY_CHANNELS.has(channel) ? true : void 0 };
 }
-async function estimate(ctx, campaignId, leadCount) {
+async function estimate(ctx, leadCount) {
   if (leadCount === 0) return { estimate: null };
   try {
-    const res = await ctx.client.request({ method: "POST", path: "/v1/credits/estimates", body: { kind: "leads", leadCount, campaignId } });
+    const res = await ctx.client.request({ method: "POST", path: "/v1/credits/estimates", body: { kind: "leads", leadCount } });
     const data = unwrap(res.body);
     if (!isRecord4(data)) return { estimate: data ?? null };
     const credits = (key) => typeof data[key] === "number" ? data[key] / 1e3 : void 0;
@@ -8502,7 +8502,7 @@ var init_import2 = __esm({
           ...Object.keys(mapping.dropped).length > 0 ? { droppedColumns: mapping.dropped } : {},
           ...emailLess > 0 ? { emailLessRows: emailLess } : {}
         };
-        if (dryRun2) Object.assign(dryRunExtra, await estimate(ctx, campaignId, items.length));
+        if (dryRun2) Object.assign(dryRunExtra, await estimate(ctx, items.length));
         const outcome = await runBatch(
           {
             command: "contacts import",
@@ -9501,7 +9501,7 @@ var init_README = __esm({
 var studio_default;
 var init_studio = __esm({
   "docs/studio.md"() {
-    studio_default = "# Studio (beta)\n\nStudio templates are the pages, docs and other assets Kenso builds for each account or lead. The `kenso studio` commands let you edit a template as a folder of files on your machine, check it, preview it, and fill it for many accounts or leads at once. They are beta: they need the `studio` feature flag on your workspace. Help and `kenso describe` hide them until your workspace has it; `--all-commands` shows them.\n\n| Command | What it does |\n|---|---|\n| `studio pull <templateId> --dir <dir>` | Write a template version's files to a folder |\n| `studio push <templateId> --dir <dir>` | Save the folder's files to the template's draft and print the validation |\n| `studio validate <templateId> --dir <dir>` | Validate the folder against the template without saving |\n| `studio preview <templateId>` | Render a version for up to 3 accounts and print the preview links |\n| `studio fill <templateId>` | Fill the template for many accounts or campaign leads, estimate first |\n\nFind template ids with the generated commands:\n\n```bash\nkenso asset-templates list\n```\n\n## Edit a template locally\n\n```bash\nkenso studio pull 12 --dir ./my-template\nkenso studio validate 12 --dir ./my-template\nkenso studio push 12 --dir ./my-template\nkenso studio preview 12 --dir ./my-template --account-ids 501,502\nkenso studio push 12 --dir ./my-template --publish\n```\n\n### pull\n\n`pull` writes every file of the version under `--dir`: text files from the answer, binaries downloaded from signed links and checked against their SHA-256. It overwrites files with the same path and leaves other files in the folder alone. It checks every path before it writes anything, and refuses one that would land outside `--dir` (`unsafe_path`).\n\n`--template-version` picks the version: `draft`, `latest` (the latest published) or a version id. The default is the draft, else the latest published version. (The flag is not `--version`, which prints the CLI version.)\n\n```bash\nkenso studio pull 12 --dir ./v3 --template-version 345\nkenso studio pull 12 --dir ./my-template --dry-run\n```\n\nIt prints `{templateId, versionId, files, dir}`. `--dry-run` lists the paths and writes nothing.\n\n### push\n\n`push` reads `--dir`, skipping dotfiles, dot folders and `node_modules`.\n\n- A text file (valid UTF-8, no NUL byte, under 1 MB) goes inline.\n- Any other file is uploaded through a signed upload URL first, 4 at a time, up to 5 MB each. A larger file is refused before any call.\n- One push then saves the files into the draft and prints `{templateId, versionId, versionNumber, validation, changed, deleted}`.\n\nFiles that are in the draft but not in the folder stay, unless you pass `--delete-missing`. `--message` describes the change (default \"Pushed with the Kenso CLI\"). With `--publish`, the new version is published when validation passes, and the output adds `published`.\n\n```bash\nkenso studio push 12 --dir ./my-template --message \"New hero copy\"\nkenso studio push 12 --dir ./my-template --delete-missing --publish\nkenso studio push 12 --dir ./my-template --dry-run\n```\n\nWhen validation finds errors, the draft is still saved: the result prints, then the error `validation_failed` (exit 2) with the first problem as its `hint`. When publishing fails after a good push, the push result still prints and the error says which version was saved. `--dry-run` lists what would be sent and calls nothing.\n\n### validate\n\n`validate` reads the folder the same way and checks the files laid over the draft, as a push would, without saving them. Binaries are uploaded so they can be checked. `--delete-missing` validates exactly the folder's files. It prints the validation and exits 2 when there are errors.\n\n### preview\n\n`preview` renders a saved version, not your local files: the draft, else the latest published version, or `--version-id`. It takes up to a minute per account.\n\n```bash\nkenso studio preview 12\nkenso studio preview 12 --account-ids 501,502,503 --mode render\nkenso studio preview 12 --sample samples/acme.json\nkenso studio preview 12 --mode interact --interact @steps.json\n```\n\n- `--account-ids` takes up to 3 ids. Without it, Kenso picks the 3 most recently touched accounts, else the template's samples.\n- `--mode` is `render` (default) or `interact`. `--interact` takes the click, type and wait steps as JSON, `@file` or `-` (up to 20).\n- With `--dir`, the CLI compares your folder to the version it renders and warns on stderr when they differ, naming the push command to run first.\n\nThe output lists each preview's link, screenshots, console errors and link issues.\n\n## Fill a template for many accounts or leads\n\n`fill` creates pages for a list of accounts, or for the leads of a campaign. A fill is charged per page, so it always prices the work first.\n\n```bash\nkenso studio fill 12 --accounts accounts.txt\nkenso studio fill 12 --accounts accounts.csv --column accountId --yes --wait\nkenso studio fill 12 --campaign 345 --contacts leads.csv --yes\n```\n\n- **Ids** come from `--accounts <file>`, or from `--contacts <file>` with `--campaign <id>`; `-` reads stdin. A file holds one id per line, or a CSV or JSONL with an id column (`--column`, else `id`, else `contactId`). Repeated ids are filled once.\n- **Without `--yes`** (or with `--estimate`) it prints the estimate and the apply command, and creates nothing. For a campaign, the estimate counts one page per lead; Kenso builds one page per company, so it is an upper bound.\n- **With `--yes`** it creates one fill run per 500 ids, one after another.\n- **With `--wait`** it follows each run every 5 seconds until it completes, fails or is cancelled. Without it, follow a run with `kenso asset-runs get --run-id <id>`.\n\nThe summary lists `runs: [{runId, state, rows}]`, and `results.csv` has one line per id with its page id and state.\n\n**The same fill never runs twice.** Rebuilding a page charges again, so when you rerun a fill with the same file (the same bytes) and the same flags:\n\n- an unfinished fill continues where it stopped;\n- a finished fill where every id succeeded answers from that run and changes nothing;\n- anything else is refused with `already_filled` (exit 7). To retry only the ids that failed, take them from the earlier run's `results.csv` into a new file and fill that file.\n\nThe guard compares the file and the flags, not the ids: the same ids in another file, or in another order, are filled and charged again. Keep one ids file per fill, and check `kenso runs list` before you fill ids from a new file.\n\n## Other Studio commands\n\nEverything else (create a template, list versions, restore a version, datasets, publish) is a generated command under `asset-templates`, `asset-runs` and `asset-template-datasets`:\n\n```bash\nkenso asset-templates --help --all-commands\nkenso describe asset-templates\n```\n";
+    studio_default = "# Studio (beta)\n\nStudio templates are the pages, docs and other assets Kenso builds for each account or lead. The `kenso studio` commands let you edit a template as a folder of files on your machine, check it, preview it, and fill it for many accounts or leads at once. They are beta: they need the `studio` feature flag on your workspace. Help and `kenso describe` hide them until your workspace has it; `--all-commands` shows them.\n\n| Command | What it does |\n|---|---|\n| `studio pull <templateId> --dir <dir>` | Write a template version's files to a folder |\n| `studio push <templateId> --dir <dir>` | Save the folder's files to the template's draft and print the validation |\n| `studio validate <templateId> --dir <dir>` | Validate the folder against the template without saving |\n| `studio preview <templateId>` | Render a version for up to 3 accounts and print the preview links |\n| `studio fill <templateId>` | Fill the template for many accounts or campaign leads, estimate first |\n\nFind template ids with the generated commands:\n\n```bash\nkenso asset-templates list\n```\n\n## Edit a template locally\n\n```bash\nkenso studio pull 12 --dir ./my-template\nkenso studio validate 12 --dir ./my-template\nkenso studio push 12 --dir ./my-template\nkenso studio preview 12 --dir ./my-template --account-ids 501,502\nkenso studio push 12 --dir ./my-template --publish\n```\n\n### pull\n\n`pull` writes every file of the version under `--dir`: text files from the answer, binaries downloaded from signed links and checked against their SHA-256. It overwrites files with the same path and leaves other files in the folder alone. It checks every path before it writes anything, and refuses one that would land outside `--dir` (`unsafe_path`).\n\n`--template-version` picks the version: `draft`, `latest` (the latest published) or a version id. The default is the draft, else the latest published version. (The flag is not `--version`: after a command, `--version` fails with `unknown_flag` and points at `--template-version`.)\n\n```bash\nkenso studio pull 12 --dir ./v3 --template-version 345\nkenso studio pull 12 --dir ./my-template --dry-run\n```\n\nIt prints `{templateId, versionId, files, dir}`. `--dry-run` lists the paths and writes nothing.\n\n### push\n\n`push` reads `--dir`, skipping dotfiles, dot folders and `node_modules`.\n\n- A text file (valid UTF-8, no NUL byte, under 1 MB) goes inline.\n- Any other file is uploaded through a signed upload URL first, 4 at a time, up to 5 MB each. A larger file is refused before any call.\n- One push then saves the files into the draft and prints `{templateId, versionId, versionNumber, validation, changed, deleted}`.\n\nFiles that are in the draft but not in the folder stay, unless you pass `--delete-missing`. `--message` describes the change (default \"Pushed with the Kenso CLI\"). With `--publish`, the new version is published when validation passes, and the output adds `published`.\n\n```bash\nkenso studio push 12 --dir ./my-template --message \"New hero copy\"\nkenso studio push 12 --dir ./my-template --delete-missing --publish\nkenso studio push 12 --dir ./my-template --dry-run\n```\n\nWhen validation finds errors, the draft is still saved: the result prints, then the error `validation_failed` (exit 2) with the first problem as its `hint`. When publishing fails after a good push, the push result still prints and the error says which version was saved. `--dry-run` lists what would be sent and calls nothing.\n\n### validate\n\n`validate` reads the folder the same way and checks the files laid over the draft, as a push would, without saving them. Binaries are uploaded so they can be checked. `--delete-missing` validates exactly the folder's files. It prints the validation and exits 2 when there are errors.\n\n### preview\n\n`preview` renders a saved version, not your local files: the draft, else the latest published version, or `--version-id`. It takes up to a minute per account.\n\n```bash\nkenso studio preview 12\nkenso studio preview 12 --account-ids 501,502,503 --mode render\nkenso studio preview 12 --sample samples/acme.json\nkenso studio preview 12 --mode interact --interact @steps.json\n```\n\n- `--account-ids` takes up to 3 ids. Without it, Kenso picks the 3 most recently touched accounts, else the template's samples.\n- `--mode` is `render` (default) or `interact`. `--interact` takes the click, type and wait steps as JSON, `@file` or `-` (up to 20).\n- With `--dir`, the CLI compares your folder to the version it renders and warns on stderr when they differ, naming the push command to run first.\n\nThe output lists each preview's link, screenshots, console errors and link issues.\n\n## Fill a template for many accounts or leads\n\n`fill` creates pages for a list of accounts, or for the leads of a campaign. A fill is charged per page, so it always prices the work first.\n\n```bash\nkenso studio fill 12 --accounts accounts.txt\nkenso studio fill 12 --accounts accounts.csv --column accountId --yes --wait\nkenso studio fill 12 --campaign 345 --contacts leads.csv --yes\n```\n\n- **Ids** come from `--accounts <file>`, or from `--contacts <file>` with `--campaign <id>`; `-` reads stdin. A file holds one id per line, or a CSV or JSONL with an id column (`--column`, else `id`, else `contactId`). Repeated ids are filled once.\n- **Without `--yes`** (or with `--estimate`) it prints the estimate and the apply command, and creates nothing. For a campaign, the estimate counts one page per lead; Kenso builds one page per company, so it is an upper bound.\n- **With `--yes`** it creates one fill run per 500 ids, one after another.\n- **With `--wait`** it follows each run every 5 seconds until it completes, fails or is cancelled. Without it, follow a run with `kenso asset-runs get --run-id <id>`.\n\nThe summary lists `runs: [{runId, state, rows}]`, and `results.csv` has one line per id with its page id and state.\n\n**The same fill never runs twice.** Rebuilding a page charges again, so when you rerun a fill with the same file (the same bytes) and the same flags:\n\n- an unfinished fill continues where it stopped;\n- a finished fill where every id succeeded answers from that run and changes nothing;\n- anything else is refused with `already_filled` (exit 7). To retry only the ids that failed, take them from the earlier run's `results.csv` into a new file and fill that file.\n\nThe guard compares the file and the flags, not the ids: the same ids in another file, or in another order, are filled and charged again. Keep one ids file per fill, and check `kenso runs list` before you fill ids from a new file.\n\n## Other Studio commands\n\nEverything else (create a template, list versions, restore a version, datasets, publish) is a generated command under `asset-templates`, `asset-runs` and `asset-template-datasets`:\n\n```bash\nkenso asset-templates --help --all-commands\nkenso describe asset-templates\n```\n";
   }
 });
 
@@ -11892,7 +11892,7 @@ var init_help = __esm({
       ["--progress", "Print progress to stderr even when it is not a terminal"],
       ["--all-commands", "Show beta commands in help"],
       ["-h, --help", "Show help"],
-      ["--version", "Print the version"]
+      ["--version", "Print the CLI version (only on its own: kenso --version)"]
     ];
     GLOBAL_FLAGS_LINE = "Global flags: --dry-run, -y/--yes, --workspace <id>, --profile, -o/--output json|ndjson|table|ids, --fields, --query, -v, --progress (kenso --help --all-commands explains them).";
     COMMON_RESOURCES = [
@@ -12042,6 +12042,11 @@ async function unknownCommand(tokens, resource) {
     next: "kenso --help"
   });
 }
+function versionHint(spec) {
+  const own = Object.keys(spec.flags).filter((name) => name.includes("version") && !name.startsWith("no-"));
+  const cli = "--version prints the CLI version, and only on its own: kenso --version.";
+  return own.length > 0 ? `did you mean ${own.map((name) => `--${name}`).join(" or ")}? ${cli}` : cli;
+}
 function flagError(err, spec) {
   const name = commandName(spec);
   const code = err.code;
@@ -12049,21 +12054,21 @@ function flagError(err, spec) {
   if (code === "ERR_PARSE_ARGS_UNKNOWN_OPTION") {
     const flag = /'(-{1,2}[^']+)'/.exec(message)?.[1] ?? "";
     const bare = flag.replace(/^-+/, "").split("=")[0];
-    const suggestion = closest(bare, [...Object.keys(spec.flags), ...Object.keys(GLOBAL_OPTIONS)]);
+    const suggestion = closest(bare, [...Object.keys(spec.flags), ...Object.keys(COMMAND_GLOBAL_OPTIONS)]);
     return new KensoError({
       code: "unknown_flag",
       message: `Unknown flag ${flag} for ${name}.`,
       exitCode: ExitCode.Usage,
       field: bare || void 0,
-      hint: suggestion ? `did you mean --${suggestion}?` : `Run ${name} --help to list its flags.`,
+      hint: bare === "version" ? versionHint(spec) : suggestion ? `did you mean --${suggestion}?` : `Run ${name} --help to list its flags.`,
       next: `${name} --help`
     });
   }
   return new KensoError({ code: "invalid_flag", message: `${message} (${name}).`, exitCode: ExitCode.Usage, next: `${name} --help` });
 }
 function strictParse(argv, spec) {
-  const options = { ...GLOBAL_OPTIONS };
-  const booleans = new Set(GLOBAL_BOOLEANS);
+  const options = { ...COMMAND_GLOBAL_OPTIONS };
+  const booleans = new Set(COMMAND_GLOBAL_BOOLEANS);
   for (const [name, flag] of Object.entries(spec.flags)) {
     const option = { type: flag.type };
     if (flag.short) option.short = flag.short;
@@ -12161,7 +12166,7 @@ async function main(argv, env = process.env, overrides = {}) {
   let verbose = false;
   try {
     const loose = parseArgs({ args: normalizeBooleans(argv, new Set(GLOBAL_BOOLEANS), void 0), options: GLOBAL_OPTIONS, strict: false, allowPositionals: true });
-    if (loose.values.version === true) {
+    if (loose.values.version === true && loose.positionals.length === 0) {
       stdout.write(`${VERSION}
 `);
       return ExitCode.Ok;
@@ -12255,7 +12260,7 @@ function invokedDirectly() {
     return false;
   }
 }
-var GLOBAL_OPTIONS, INTERRUPT_GRACE_MS, GLOBAL_BOOLEANS, activeRuns, sigintCount, lookupFailed, LINGERING_REQUEST_GRACE_MS, guardedStreams;
+var GLOBAL_OPTIONS, INTERRUPT_GRACE_MS, GLOBAL_BOOLEANS, COMMAND_GLOBAL_OPTIONS, COMMAND_GLOBAL_BOOLEANS, activeRuns, sigintCount, lookupFailed, LINGERING_REQUEST_GRACE_MS, guardedStreams;
 var init_main = __esm({
   "src/main.ts"() {
     init_generated_hook();
@@ -12284,6 +12289,8 @@ var init_main = __esm({
     };
     INTERRUPT_GRACE_MS = 3e3;
     GLOBAL_BOOLEANS = Object.entries(GLOBAL_OPTIONS).filter(([, option]) => option.type === "boolean").map(([name]) => name);
+    COMMAND_GLOBAL_OPTIONS = Object.fromEntries(Object.entries(GLOBAL_OPTIONS).filter(([name]) => name !== "version"));
+    COMMAND_GLOBAL_BOOLEANS = GLOBAL_BOOLEANS.filter((name) => name !== "version");
     activeRuns = [];
     sigintCount = 0;
     lookupFailed = false;