@general-input/cli 0.13.0 → 0.14.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/cli.js CHANGED
@@ -18219,7 +18219,7 @@ function buildClientLabel() {
18219
18219
  return `geni CLI on ${hostname()}`;
18220
18220
  }
18221
18221
  function sleep(ms) {
18222
- return new Promise((resolve21) => setTimeout(resolve21, ms));
18222
+ return new Promise((resolve22) => setTimeout(resolve22, ms));
18223
18223
  }
18224
18224
 
18225
18225
  // src/services/WorkspaceService.ts
@@ -18288,7 +18288,7 @@ import chalk4 from "chalk";
18288
18288
  // package.json
18289
18289
  var package_default = {
18290
18290
  name: "@general-input/cli",
18291
- version: "0.13.0",
18291
+ version: "0.14.0",
18292
18292
  type: "module",
18293
18293
  description: "The agent-facing CLI for General Input. Authenticate, manage workflows, run bash with operator credentials injected by the cloud.",
18294
18294
  license: "SEE LICENSE IN LICENSE",
@@ -19056,7 +19056,13 @@ import {
19056
19056
  } from "fs";
19057
19057
  import { join as join3, relative, sep } from "path";
19058
19058
  var RESOURCE_MARKER_FILE = ".geni-resource.json";
19059
- var SKIP_DIRS = /* @__PURE__ */ new Set(["node_modules", ".git", "dist", ".turbo"]);
19059
+ var SKIP_DIRS = /* @__PURE__ */ new Set([
19060
+ "node_modules",
19061
+ ".git",
19062
+ "dist",
19063
+ ".turbo",
19064
+ "geni-skills"
19065
+ ]);
19060
19066
  function readMarker(dir) {
19061
19067
  const path = join3(dir, RESOURCE_MARKER_FILE);
19062
19068
  if (!existsSync2(path)) return null;
@@ -19155,12 +19161,12 @@ async function packResourceDir(dir) {
19155
19161
  }
19156
19162
  async function extractBundle(dir, buffer) {
19157
19163
  mkdirSync3(dir, { recursive: true });
19158
- await new Promise((resolve21, reject) => {
19164
+ await new Promise((resolve22, reject) => {
19159
19165
  const unpack = extract({
19160
19166
  cwd: dir,
19161
19167
  filter: (path) => !SKIP_DIRS.has(path.split("/")[0])
19162
19168
  });
19163
- unpack.on("close", resolve21);
19169
+ unpack.on("close", resolve22);
19164
19170
  unpack.on("error", reject);
19165
19171
  Readable.from(buffer).on("error", reject).pipe(unpack);
19166
19172
  });
@@ -19333,10 +19339,6 @@ var WorkflowAuthoringService = class {
19333
19339
  const { client } = await this.sessionContext.requireAuthed();
19334
19340
  return client.workflows.clearHandlerCache(id);
19335
19341
  }
19336
- async spec(type) {
19337
- const { client } = await this.sessionContext.requireAuthed();
19338
- return client.workflows.spec(type);
19339
- }
19340
19342
  async listTriggers(query) {
19341
19343
  const { client } = await this.sessionContext.requireAuthed();
19342
19344
  return client.workflows.listTriggers(query);
@@ -19401,10 +19403,17 @@ Write the instructions the loading agent should follow.
19401
19403
  const bundleKey = await this.uploadBundle(args.id, args.dir);
19402
19404
  return client.skills.publish(args.id, { bundleKey });
19403
19405
  }
19404
- async spec() {
19406
+ /**
19407
+ * Write a platform skill's full bundle (SKILL.md + references/) into `dir`.
19408
+ * Read-only reference material — no resource marker, never published.
19409
+ */
19410
+ async loadPlatformSkill(args) {
19405
19411
  const { client } = await this.sessionContext.requireAuthed();
19406
- const { spec } = await client.skills.spec();
19407
- return spec;
19412
+ const skill = await client.skills.platform(args.name);
19413
+ for (const file of skill.files) {
19414
+ this.writeFileInto(args.dir, file.path, file.content);
19415
+ }
19416
+ return { fileCount: skill.files.length, description: skill.description };
19408
19417
  }
19409
19418
  /** Tar `dir`, PUT it to a presigned URL, return the staged `bundleKey`. */
19410
19419
  async uploadBundle(id, dir) {
@@ -20042,10 +20051,6 @@ var WorkflowsApiClient = class {
20042
20051
  { method: "POST" }
20043
20052
  );
20044
20053
  }
20045
- async spec(type) {
20046
- this.http.requireAuthed();
20047
- return this.http.fetch(`/v1/workflows/spec/${encodeURIComponent(type)}`);
20048
- }
20049
20054
  async listTriggers(query) {
20050
20055
  this.http.requireAuthed();
20051
20056
  const suffix = query ? `?q=${encodeURIComponent(query)}` : "";
@@ -20665,9 +20670,10 @@ var SkillsApiClient = class {
20665
20670
  body
20666
20671
  });
20667
20672
  }
20668
- async spec() {
20673
+ /** Read-only platform skill detail: SKILL.md plus its references/ files. */
20674
+ async platform(name) {
20669
20675
  this.http.requireAuthed();
20670
- return this.http.fetch("/v1/skills/spec");
20676
+ return this.http.fetch(`/v1/skills/platform/${encodeURIComponent(name)}`);
20671
20677
  }
20672
20678
  };
20673
20679
 
@@ -20914,11 +20920,11 @@ var ChildProcessSpawner = class {
20914
20920
  process.on("SIGINT", forwardSignal);
20915
20921
  process.on("SIGTERM", forwardSignal);
20916
20922
  try {
20917
- const exitCode = await new Promise((resolve21, reject) => {
20923
+ const exitCode = await new Promise((resolve22, reject) => {
20918
20924
  child.once("exit", (code, signal) => {
20919
- if (code !== null) resolve21(code);
20920
- else if (signal !== null) resolve21(128 + signalNumber(signal));
20921
- else resolve21(1);
20925
+ if (code !== null) resolve22(code);
20926
+ else if (signal !== null) resolve22(128 + signalNumber(signal));
20927
+ else resolve22(1);
20922
20928
  });
20923
20929
  child.once("error", (err) => reject(err));
20924
20930
  });
@@ -20931,7 +20937,7 @@ var ChildProcessSpawner = class {
20931
20937
  }
20932
20938
  };
20933
20939
  function pipeWithScrubbing(source, dest, scrubber, onChunk) {
20934
- return new Promise((resolve21) => {
20940
+ return new Promise((resolve22) => {
20935
20941
  let flushed = false;
20936
20942
  const emit = (chunk) => {
20937
20943
  if (chunk.length === 0) return;
@@ -20942,13 +20948,13 @@ function pipeWithScrubbing(source, dest, scrubber, onChunk) {
20942
20948
  if (flushed) return;
20943
20949
  flushed = true;
20944
20950
  emit(scrubber.redact("", { final: true }));
20945
- resolve21();
20951
+ resolve22();
20946
20952
  };
20947
20953
  source.on("end", finishOnce);
20948
20954
  source.on("close", finishOnce);
20949
20955
  source.on("error", () => {
20950
20956
  flushed = true;
20951
- resolve21();
20957
+ resolve22();
20952
20958
  });
20953
20959
  source.setEncoding("utf8");
20954
20960
  source.on("data", (chunk) => {
@@ -21616,7 +21622,7 @@ ${ca.caCertPem}`
21616
21622
  log: () => {
21617
21623
  }
21618
21624
  });
21619
- const port = await new Promise((resolve21, reject) => {
21625
+ const port = await new Promise((resolve22, reject) => {
21620
21626
  connectListener.once("error", reject);
21621
21627
  connectListener.listen(0, "127.0.0.1", () => {
21622
21628
  const address = connectListener.address();
@@ -21624,7 +21630,7 @@ ${ca.caCertPem}`
21624
21630
  reject(new Error("egress proxy failed to bind a TCP port"));
21625
21631
  return;
21626
21632
  }
21627
- resolve21(address.port);
21633
+ resolve22(address.port);
21628
21634
  });
21629
21635
  });
21630
21636
  const proxyUrl = `http://127.0.0.1:${port}`;
@@ -21632,7 +21638,7 @@ ${ca.caCertPem}`
21632
21638
  env: buildEgressClientEnv({ proxyUrl, caFile, bundleFile }),
21633
21639
  stop: async () => {
21634
21640
  await new Promise(
21635
- (resolve21) => connectListener.close(() => resolve21())
21641
+ (resolve22) => connectListener.close(() => resolve22())
21636
21642
  );
21637
21643
  await rm(dir, { recursive: true, force: true });
21638
21644
  }
@@ -21707,6 +21713,10 @@ function exitOnApiError(error, opts = {}) {
21707
21713
  );
21708
21714
  exit(ExitCode.NotFound);
21709
21715
  }
21716
+ if (error.status === 426) {
21717
+ printError(error.message);
21718
+ exit(ExitCode.UpgradeRequired);
21719
+ }
21710
21720
  if (error.status >= 500) {
21711
21721
  printError(
21712
21722
  `Server error (HTTP ${error.status}): ${error.message} Retry once before reporting.`
@@ -22593,7 +22603,7 @@ function registerIntegrationCommands(program2) {
22593
22603
  import { resolve as resolve2 } from "path";
22594
22604
  function registerResourceCreate(parent) {
22595
22605
  parent.command("create").description(
22596
- "Create a resource (code or agent workflow, app, or skill) and scaffold its starting files locally. Edit them, then validate and publish. Read the contract first with `geni resource spec <type>`."
22606
+ "Create a resource (code or agent workflow, app, or skill) and scaffold its starting files locally. Edit them, then validate and publish. Load the authoring skill first with `geni skills load <type>` for the contract and a worked example."
22597
22607
  ).requiredOption(
22598
22608
  "--type <type>",
22599
22609
  'Resource type: "code" (deterministic, fixed steps), "agent" (LLM-driven, variable-length tasks), "app" (interactive React mini-app with server-side handlers), or "skill" (a SKILL.md instruction bundle agents load as context).'
@@ -22631,7 +22641,7 @@ function registerResourceCreate(parent) {
22631
22641
  printInfo(`id: ${skill.id}`);
22632
22642
  printInfo(`Scaffolded ${fileCount2} file(s) into ${dir}`);
22633
22643
  printInfo(
22634
- "Next: edit SKILL.md, then `geni resource validate` and `geni resource publish`. See the contract with `geni resource spec skill`."
22644
+ "Next: edit SKILL.md, then `geni resource validate` and `geni resource publish`. The contract ships in the skill-authoring platform skill: `geni skills load skill-authoring`."
22635
22645
  );
22636
22646
  return;
22637
22647
  }
@@ -22647,8 +22657,9 @@ function registerResourceCreate(parent) {
22647
22657
  printSuccess(`Created ${detail.workflowType} resource "${detail.name}"`);
22648
22658
  printInfo(`id: ${detail.id}`);
22649
22659
  printInfo(`Scaffolded ${fileCount} file(s) into ${dir}`);
22660
+ const authoringSkill = detail.workflowType === "app" ? "app" : `${detail.workflowType}-workflow`;
22650
22661
  printInfo(
22651
- "Next: edit the files, then `geni resource validate`. See the contract with `geni resource spec " + detail.workflowType + "`."
22662
+ `Next: \`geni skills load ${authoringSkill}\` for the contract and a worked example, edit the files, then \`geni resource validate\`.`
22652
22663
  );
22653
22664
  } catch (error) {
22654
22665
  exitOnApiError(error);
@@ -23070,33 +23081,10 @@ function registerResourcePublish(parent) {
23070
23081
  });
23071
23082
  }
23072
23083
 
23073
- // src/commands/resource/spec.ts
23074
- function registerResourceSpec(parent) {
23075
- parent.command("spec <type>").description(
23076
- "Print the resource-type contract (code | agent | app | skill): required files, runtime API, allowed/forbidden patterns. Read this before editing files."
23077
- ).action(async (type) => {
23078
- try {
23079
- if (type === "skill") {
23080
- const spec = await skillAuthoringService.spec();
23081
- process.stdout.write(spec.endsWith("\n") ? spec : spec + "\n");
23082
- return;
23083
- }
23084
- const result = await workflowAuthoringService.spec(type);
23085
- process.stdout.write(
23086
- result.spec.endsWith("\n") ? result.spec : result.spec + "\n"
23087
- );
23088
- } catch (error) {
23089
- exitOnApiError(error, {
23090
- notFoundMessage: `Unknown resource type "${type}". Use code, agent, app, or skill.`
23091
- });
23092
- }
23093
- });
23094
- }
23095
-
23096
23084
  // src/commands/resource/index.ts
23097
23085
  function registerResourceCommands(program2) {
23098
23086
  const resource = program2.command("resource").alias("resources").description(
23099
- "Author resources (workflows, apps, and skills) locally against the cloud: scaffold and pull files, edit them, then validate, wire credentials, and publish. Run `geni resource spec <type>` to learn a type contract."
23087
+ "Author resources (workflows, apps, and skills) locally against the cloud: scaffold and pull files, edit them, then validate, wire credentials, and publish. Run `geni skills load <type>` first to get the type contract and a worked example."
23100
23088
  ).action(() => executeResourceList({}));
23101
23089
  registerResourceCreate(resource);
23102
23090
  registerResourceList(resource);
@@ -23105,11 +23093,10 @@ function registerResourceCommands(program2) {
23105
23093
  registerResourceValidate(resource);
23106
23094
  registerResourceConfig(resource);
23107
23095
  registerResourcePublish(resource);
23108
- registerResourceSpec(resource);
23109
23096
  resource.addHelpText(
23110
23097
  "after",
23111
23098
  `
23112
- Build loop (run \`geni resource spec <type>\` first):
23099
+ Build loop (run \`geni skills load <code-workflow|agent-workflow|app|skill-authoring>\` first):
23113
23100
  1. geni resource create --type code --name "My Resource" scaffold files + the cloud resource
23114
23101
  2. (edit the files with your editor)
23115
23102
  3. geni resource validate spec + type check, no publish
@@ -23128,7 +23115,7 @@ Commands accept the resource id as a positional, or infer it from the
23128
23115
  import { resolve as resolve9 } from "path";
23129
23116
  function registerWorkflowSetType(parent) {
23130
23117
  parent.command("set-type <type> [id]").description(
23131
- "Switch a workflow's execution type (code <-> agent). Then rewrite the files for the new type and delete the old type's. Read `geni resource spec <type>`."
23118
+ "Switch a workflow's execution type (code <-> agent). Then rewrite the files for the new type and delete the old type's. Load the new type's authoring skill: `geni skills load <type>-workflow`."
23132
23119
  ).option("--dir <path>", "Resource directory. Defaults to cwd.").option("--json", "Machine-readable output.").action(
23133
23120
  async (type, id, opts) => {
23134
23121
  if (type !== "code" && type !== "agent") {
@@ -23156,7 +23143,7 @@ function registerWorkflowSetType(parent) {
23156
23143
  );
23157
23144
  }
23158
23145
  printInfo(
23159
- `Write the ${type} files, then validate. Read the contract: \`geni resource spec ${type}\`.`
23146
+ `Write the ${type} files, then validate. Load the authoring skill first: \`geni skills load ${type}-workflow\` (its references/ hold the contract and a worked example).`
23160
23147
  );
23161
23148
  } catch (error) {
23162
23149
  exitOnApiError(error, {
@@ -23299,7 +23286,7 @@ function parseTimeout(raw) {
23299
23286
  return seconds * 1e3;
23300
23287
  }
23301
23288
  function sleep2(ms) {
23302
- return new Promise((resolve21) => setTimeout(resolve21, ms));
23289
+ return new Promise((resolve22) => setTimeout(resolve22, ms));
23303
23290
  }
23304
23291
 
23305
23292
  // src/commands/workflow/triggerSample.ts
@@ -23965,7 +23952,7 @@ import {
23965
23952
  } from "fs";
23966
23953
 
23967
23954
  // src/skills/geni.md
23968
- var geni_default = "---\nname: geni\ndescription: Use the operator's connected services (Slack, Gmail, GitHub, Stripe, anything they've authorized in General Input) to fulfill their request, or build them a saved workflow (scheduled or event-driven automation). Load this whenever the user wants you to take an action on their behalf against an external SaaS account, fetch data from one of their tools, wire something up that crosses service boundaries, or set up a recurring/triggered automation.\n---\n\n# geni\n\n`geni` is a CLI that gives you credentialed access to the operator's\nconnected accounts. The cloud injects their tokens into a fresh bash\nsubprocess as env vars; you write the `curl`, you never see the\nsecret. Run `geni --help` for the full command surface.\n\n## How to talk about geni\n\nTreat geni as a teammate \u2014 the integration specialist who picks the\nright operation and runs the credentialed call. You're the one\nsynthesizing and replying.\n\nIn summaries of multi-step work, credit geni naturally: \"Geni pulled\nthe last 30 days of charges from Stripe; I rolled them into the report\nbelow.\" Skip the credit on trivial single calls; don't manufacture\nteam language (\"with geni's help\u2026\") to fill space. Lowercase `geni`\nin commands; capitalize \"Geni\" when personifying.\n\n## Request flow\n\nDiscovery first. Don't guess URLs, params, or env var names \u2014 the\noperation docs have them.\n\n1. `geni credential list [--service <slug>]` \u2014 find a connected\n credential id. If nothing's connected for the service, run\n `geni integration list -q \"<keyword>\"` to confirm the slug, then\n `geni credential connect <service>` (see \"Connecting a missing\n credential\" below).\n2. `geni integration operations <service> [-q \"<keyword>\"]` \u2014 find\n the operation you need.\n3. `geni integration operation <id> --format markdown` \u2014 read the\n HTTP shape, params, and **exact env var names** this call will set.\n4. `geni exec bash --cred <cred_id> --reason \"<what + why>\" -- '<curl>'`\n\n## Connecting a missing credential\n\n`geni credential connect <service>` opens the integration's\ndashboard page in the operator's browser. Tell the operator to\nfinish the connection there and come back \u2014 then re-run `geni\ncredential list --service <service>` to pick up the new id. Don't\npoll, don't loop. In non-interactive shells, add `--print-url` so\nthe URL prints to stdout instead.\n\n## Env vars\n\nRead the names off the operation docs; never derive them. Two flavors\nemitted per credential:\n\n- **Suffixed**: `<SERVICE>_<FIELD>_<id>` (e.g. `$SLACK_BOT_TOKEN_ABC`,\n `$SALESFORCE_INSTANCE_URL_KG`). The `<id>` is the credential id with\n `cred_` stripped, uppercased. Use these when fanning out across\n multiple credentials of the same service in one call.\n- **Canonical aliases**: well-known SDK names (`$GH_TOKEN`,\n `$SLACK_BOT_TOKEN`, `$OPENAI_API_KEY`, `$STRIPE_API_KEY`, \u2026) for\n tools that hardcode them.\n\nPlus `$PLATFORM_API_KEY` and `$PLATFORM_BASE_URL` on every exec \u2014 use\nthem to call General Input's first-party services (web search, image\ngen, weather, send-email) without `--cred`.\n\n## --reason is per-call\n\nEvery `geni exec bash --cred ...` requires `--reason`. It lands in\nthe operator's audit log and is shown to them. Be specific\n(\"Posting daily digest to #engineering\"), not generic (\"Slack call\").\nRe-state it on every call \u2014 the log is per-call, not per-session.\n\n## Output is scrubbed\n\nstdout and stderr pass through a streaming scrubber that replaces\nevery registered secret with `[REDACTED:credential_<id>]`. Don't try\nto exfiltrate via `echo $TOKEN | base64`; common encodings are\ncaught too. You don't need to see the secret to use it \u2014 the\nsubprocess can.\n\n## Building resources (workflows, apps, and skills)\n\n`geni exec bash` is for one-off actions. When the user wants something\nsaved and reusable, build a **resource**. A resource is one of four\ntypes: a `code` **workflow** (deterministic, fixed steps, runs on a\nschedule or trigger), an `agent` **workflow** (LLM-driven, variable-length\ntasks like research or triage), an `app` (an interactive React mini-app\nwith server-side handlers, like a dashboard or internal tool), or a\n`skill` (a SKILL.md instruction bundle the platform's cloud agents load\nas context \u2014 not executed). The shared lifecycle lives under `geni\nresource`; type-specific tools under `geni workflow` and `geni app`.\n\nYou author the files locally with your own editor; the cloud validates,\nconfigures, publishes, and runs them. This is the same build loop as the\ngeni chat, just on the user's machine with your brain driving it. Same\nloop for every type; apps add a build step and handler tools (see\n\"Building apps\" below), skills drop the config step (see \"Building\nskills\" below).\n\n**Read the spec first.** `geni resource spec <code|agent|app|skill>`\nprints the full contract: required files, the runtime API, allowed and\nforbidden patterns. Don't write a single file before reading it.\n\nThe loop:\n\n1. `geni resource create --type code --name \"Daily Digest\"`: creates the\n resource in the cloud and scaffolds its files into the current\n directory, with a `.geni-resource.json` marker so later commands here\n resolve the id automatically.\n2. Edit the files (`workflow.json`, `main.ts`, `package.json`) with your\n normal Read/Write/Edit tools. **Don't run `npm install`, `tsc`, or\n `bun` locally**: `@general-input/core` only resolves server-side, so\n a local compile always fails on the missing module. That's not a real\n error.\n3. `geni resource validate`: server-side spec + wiring + TypeScript\n check. Exit 9 means invalid; fix what it reports and re-run. A green\n validate is the compile gate.\n4. `geni resource config set`: wire what the workflow needs. Find\n credential ids with `geni credential list`; set them with\n `--cred <service>=<credentialId>`. Set consts with `--const k=v`,\n schedules with `--schedule <triggerId>=<cron>`. `geni resource config\nget` shows the current state. Find trigger providers with\n `geni trigger list`.\n5. `geni resource publish --summary \"<one plain sentence>\"`: promote\n your local files to the live version. Required before a test reflects\n your latest edits.\n6. `geni workflow test --payload '{...}'`: run a real cloud test\n execution and wait for the result, output, and logs. Iterate from\n step 2 until it does what the user asked.\n\nWhen a run misbehaves, `geni workflow execution <id> --download` writes\nits full trace to `executions/<id>/` (run.json, logs.txt, input.json, and\nthread.json). For an agent workflow, read `thread.json` to see every step\nthe agent took. Use `--thread` or `--input` to print those inline instead.\n\nUse the same discovery tools as exec: `geni integration operations\n<service>` and `geni integration operation <id>` to learn an API's shape\nbefore you write the `fetch` call in `main.ts`.\n\nFor a poll-triggered workflow, `geni workflow trigger-sample` returns\nlive sample records so you see the exact shape `input` receives before\nwriting `main.ts` (wire the trigger's credential and inputs with\n`config set` first). To test a file-type input, `geni workflow\nstage-input <file>` uploads a local file and prints a `store://` URI to\npass as that field's value in `--payload`.\n\n## Building apps\n\nAn `app` workflow is a React SPA (rendered in the dashboard's iframe)\nthat calls server-side handlers. Create it with `geni resource create\n--type app`; read the contract with `geni resource spec app`. The shared\ncommands work the same (validate, config set for credential slots,\npublish), with these differences:\n\n- The scaffold is a whole Vite project. Edit only `app.json`, `src/App.tsx`,\n `src/pages/*`, your own `src/components/*`, and `handlers/*.ts`. Leave\n the platform-owned files alone.\n- `geni resource publish` builds the app; the result's `build` reports\n whether the Vite build passed. You can't preview the UI from the CLI,\n so drive correctness through handlers and the build.\n- `geni app run-handler <name> --input '{...}'` runs a handler\n against the live app (publish first). `geni app invocations`\n shows recent handler runs, `geni app errors` shows browser\n errors the iframe reported, `geni app build-status` shows the\n build, and `geni app clear-cache` flushes the handler cache.\n\nThe loop: create --type app -> edit handlers + pages -> validate ->\nconfig set (wire credential slots) -> publish (builds) -> app run-handler\nto verify -> tell the user to open it in their dashboard.\n\n## Building skills\n\nA `skill` is a SKILL.md bundle (frontmatter `name` slug + `description`,\nthen the instructions body; optional `scripts/`, `references/`,\n`assets/`) that the platform's cloud agents load as context. It is not\nexecuted, so the loop is shorter: create --type skill -> edit SKILL.md ->\nvalidate -> publish. No `config set` (nothing to wire) and publish needs\nno `--summary`. The frontmatter `description` is the only thing agents\nsee before deciding to load it, so it must say what the skill does AND\nwhen to use it. Skill ids are `skl_`-prefixed; pull/validate/publish\nwork on them like any resource.\n\nA skill is never run and has no triggers. Once published, tell the user\nit's in their dashboard Skills page, ready for their agents to load into\nfuture work. Commands accept the skill id as a positional or infer it\nfrom the marker in the current directory.\n\n## Exit codes worth knowing\n\n- `0` \u2014 success; `1\u2013125` \u2014 subprocess's own exit (curl, jq, etc.)\n- `4` \u2014 resource not found (bad cred id, slug, operation id)\n- `77` \u2014 server refused to resolve a credential. Don't retry; surface\n to the operator.\n- `78` \u2014 session expired. Tell the operator to run `geni login`.\n\n## Don't\n\n- Don't construct a curl without reading the operation docs first.\n Guessing at URLs and env var names is the most common failure mode.\n- Don't hand-write workflow files before reading `geni resource spec\n<type>`. Don't try to compile or `npm install` them locally; let\n `geni resource validate` be the gate.\n- Use `--json` on list/get commands when you're going to parse the\n output. Table output is for humans.\n";
23955
+ var geni_default = "---\nname: geni\ndescription: Use the operator's connected services (Slack, Gmail, GitHub, Stripe, anything they've authorized in General Input) to fulfill their request, or build them a saved workflow (scheduled or event-driven automation). Load this whenever the user wants you to take an action on their behalf against an external SaaS account, fetch data from one of their tools, wire something up that crosses service boundaries, or set up a recurring/triggered automation.\n---\n\n# geni\n\n`geni` is a CLI that gives you credentialed access to the operator's\nconnected accounts. The cloud injects their tokens into a fresh bash\nsubprocess as env vars; you write the `curl`, you never see the\nsecret. Run `geni --help` for the full command surface.\n\n## How to talk about geni\n\nTreat geni as a teammate \u2014 the integration specialist who picks the\nright operation and runs the credentialed call. You're the one\nsynthesizing and replying.\n\nIn summaries of multi-step work, credit geni naturally: \"Geni pulled\nthe last 30 days of charges from Stripe; I rolled them into the report\nbelow.\" Skip the credit on trivial single calls; don't manufacture\nteam language (\"with geni's help\u2026\") to fill space. Lowercase `geni`\nin commands; capitalize \"Geni\" when personifying.\n\n## Request flow\n\nDiscovery first. Don't guess URLs, params, or env var names \u2014 the\noperation docs have them.\n\n1. `geni credential list [--service <slug>]` \u2014 find a connected\n credential id. If nothing's connected for the service, run\n `geni integration list -q \"<keyword>\"` to confirm the slug, then\n `geni credential connect <service>` (see \"Connecting a missing\n credential\" below).\n2. `geni integration operations <service> [-q \"<keyword>\"]` \u2014 find\n the operation you need.\n3. `geni integration operation <id> --format markdown` \u2014 read the\n HTTP shape, params, and **exact env var names** this call will set.\n4. `geni exec bash --cred <cred_id> --reason \"<what + why>\" -- '<curl>'`\n\n## Connecting a missing credential\n\n`geni credential connect <service>` opens the integration's\ndashboard page in the operator's browser. Tell the operator to\nfinish the connection there and come back \u2014 then re-run `geni\ncredential list --service <service>` to pick up the new id. Don't\npoll, don't loop. In non-interactive shells, add `--print-url` so\nthe URL prints to stdout instead.\n\n## Env vars\n\nRead the names off the operation docs; never derive them. Two flavors\nemitted per credential:\n\n- **Suffixed**: `<SERVICE>_<FIELD>_<id>` (e.g. `$SLACK_BOT_TOKEN_ABC`,\n `$SALESFORCE_INSTANCE_URL_KG`). The `<id>` is the credential id with\n `cred_` stripped, uppercased. Use these when fanning out across\n multiple credentials of the same service in one call.\n- **Canonical aliases**: well-known SDK names (`$GH_TOKEN`,\n `$SLACK_BOT_TOKEN`, `$OPENAI_API_KEY`, `$STRIPE_API_KEY`, \u2026) for\n tools that hardcode them.\n\nPlus `$PLATFORM_API_KEY` and `$PLATFORM_BASE_URL` on every exec \u2014 use\nthem to call General Input's first-party services (web search, image\ngen, weather, send-email) without `--cred`.\n\n## --reason is per-call\n\nEvery `geni exec bash --cred ...` requires `--reason`. It lands in\nthe operator's audit log and is shown to them. Be specific\n(\"Posting daily digest to #engineering\"), not generic (\"Slack call\").\nRe-state it on every call \u2014 the log is per-call, not per-session.\n\n## Output is scrubbed\n\nstdout and stderr pass through a streaming scrubber that replaces\nevery registered secret with `[REDACTED:credential_<id>]`. Don't try\nto exfiltrate via `echo $TOKEN | base64`; common encodings are\ncaught too. You don't need to see the secret to use it \u2014 the\nsubprocess can.\n\n## Building resources (workflows, apps, and skills)\n\n`geni exec bash` is for one-off actions. When the user wants something\nsaved and reusable, build a **resource**. A resource is one of four\ntypes: a `code` **workflow** (deterministic, fixed steps, runs on a\nschedule or trigger), an `agent` **workflow** (LLM-driven, variable-length\ntasks like research or triage), an `app` (an interactive React mini-app\nwith server-side handlers, like a dashboard or internal tool), or a\n`skill` (a SKILL.md instruction bundle the platform's cloud agents load\nas context \u2014 not executed). The shared lifecycle lives under `geni\nresource`; type-specific tools under `geni workflow` and `geni app`.\n\nYou author the files locally with your own editor; the cloud validates,\nconfigures, publishes, and runs them. This is the same build loop as the\ngeni chat, just on the user's machine with your brain driving it. Same\nloop for every type; apps add a build step and handler tools (see\n\"Building apps\" below), skills drop the config step (see \"Building\nskills\" below).\n\n**Load the authoring skill first.** `geni skills load\n<code-workflow|agent-workflow|app|skill-authoring>` writes the platform's\nauthoring skill for that type into `geni-skills/<name>/`: `SKILL.md` (the\nmethod), `references/spec.md` (the full contract \u2014 required files, the\nruntime API, allowed and forbidden patterns), and `references/example/`\n(a complete, validated example to mirror). Read SKILL.md and the spec,\nand copy shapes from the example. (`skill-authoring` is the one type\nwhose short spec is inline in SKILL.md, with no example.) Don't write a\nsingle file before loading it.\n\nThe loop:\n\n1. `geni resource create --type code --name \"Daily Digest\"`: creates the\n resource in the cloud and scaffolds its files into the current\n directory, with a `.geni-resource.json` marker so later commands here\n resolve the id automatically.\n2. Edit the files (`workflow.json`, `main.ts`, `package.json`) with your\n normal Read/Write/Edit tools. **Don't run `npm install`, `tsc`, or\n `bun` locally**: `@general-input/core` only resolves server-side, so\n a local compile always fails on the missing module. That's not a real\n error.\n3. `geni resource validate`: server-side spec + wiring + (code\n workflows) TypeScript check. Exit 9 means invalid; fix what it\n reports and re-run. For apps the compile gate is the publish build,\n not validate.\n4. `geni resource config set`: wire what the workflow needs. Find\n credential ids with `geni credential list`; set them with\n `--cred <service>=<credentialId>`. Set consts with `--const k=v`,\n schedules with `--schedule <triggerId>=<cron>`. `geni resource config\nget` shows the current state. Find trigger providers with\n `geni trigger list`.\n5. `geni resource publish --summary \"<one plain sentence>\"`: promote\n your local files to the live version. Required before a test reflects\n your latest edits.\n6. `geni workflow test --payload '{...}'`: run a real cloud test\n execution and wait for the result, output, and logs. Iterate from\n step 2 until it does what the user asked.\n\nWhen a run misbehaves, `geni workflow execution <id> --download` writes\nits full trace to `executions/<id>/` (run.json, logs.txt, input.json, and\nthread.json). For an agent workflow, read `thread.json` to see every step\nthe agent took. Use `--thread` or `--input` to print those inline instead.\n\nUse the same discovery tools as exec: `geni integration operations\n<service>` and `geni integration operation <id>` to learn an API's shape\nbefore you write the `fetch` call in `main.ts`.\n\nFor a poll-triggered workflow, `geni workflow trigger-sample` returns\nlive sample records so you see the exact shape `input` receives before\nwriting `main.ts` (wire the trigger's credential and inputs with\n`config set` first). To test a file-type input, `geni workflow\nstage-input <file>` uploads a local file and prints a `store://` URI to\npass as that field's value in `--payload`.\n\n## Building apps\n\nAn `app` workflow is a React SPA (rendered in the dashboard's iframe)\nthat calls server-side handlers. Create it with `geni resource create\n--type app`; load the authoring skill with `geni skills load app` (its\n`references/` hold the contract, the component catalog, and a complete\nexample app). The shared commands work the same (validate, config set\nfor credential slots, publish), with these differences:\n\n- The scaffold is a whole Vite project. Edit only `app.json`, `src/App.tsx`,\n `src/pages/*`, your own `src/components/*`, and `handlers/*.ts`. Leave\n the platform-owned files alone.\n- `geni resource publish` builds the app; the result's `build` reports\n whether the Vite build passed. You can't preview the UI from the CLI,\n so drive correctness through handlers and the build.\n- `geni app run-handler <name> --input '{...}'` runs a handler\n against the live app (publish first). `geni app invocations`\n shows recent handler runs, `geni app errors` shows browser\n errors the iframe reported, `geni app build-status` shows the\n build, and `geni app clear-cache` flushes the handler cache.\n\nThe loop: create --type app -> edit handlers + pages -> validate ->\nconfig set (wire credential slots) -> publish (builds) -> app run-handler\nto verify -> tell the user to open it in their dashboard.\n\n## Building skills\n\nA `skill` is a SKILL.md bundle (frontmatter `name` slug + `description`,\nthen the instructions body; optional `scripts/`, `references/`,\n`assets/`) that the platform's cloud agents load as context. It is not\nexecuted, so the loop is shorter: create --type skill -> edit SKILL.md ->\nvalidate -> publish. No `config set` (nothing to wire) and publish needs\nno `--summary`. The frontmatter `description` is the only thing agents\nsee before deciding to load it, so it must say what the skill does AND\nwhen to use it. Skill ids are `skl_`-prefixed; pull/validate/publish\nwork on them like any resource.\n\nA skill is never run and has no triggers. Once published, tell the user\nit's in their dashboard Skills page, ready for their agents to load into\nfuture work. Commands accept the skill id as a positional or infer it\nfrom the marker in the current directory.\n\n## Exit codes worth knowing\n\n- `0` \u2014 success; `1\u2013125` \u2014 subprocess's own exit (curl, jq, etc.)\n- `4` \u2014 resource not found (bad cred id, slug, operation id)\n- `77` \u2014 server refused to resolve a credential. Don't retry; surface\n to the operator.\n- `78` \u2014 session expired. Tell the operator to run `geni login`.\n- `79` \u2014 this geni is below the server's minimum version. Run\n `geni upgrade`, then `geni skills install`, and retry.\n\n## Don't\n\n- Don't construct a curl without reading the operation docs first.\n Guessing at URLs and env var names is the most common failure mode.\n- Don't hand-write resource files before loading the authoring skill\n (`geni skills load <code-workflow|agent-workflow|app|skill-authoring>`)\n and reading its spec + example. Don't try to compile or `npm install`\n them locally; let `geni resource validate` be the gate.\n- Use `--json` on list/get commands when you're going to parse the\n output. Table output is for humans.\n";
23969
23956
 
23970
23957
  // src/skills/geni-crm.md
23971
23958
  var geni_crm_default = '---\nname: geni-crm\ndescription: Read and write the operator\'s General Input CRM from the command line. Load this whenever the user wants you to look something up in their CRM, pull a list of people or companies, check a deal pipeline, find or verify someone\'s email or phone (enrichment), work outbound campaigns and their sequence drafts, OR change CRM data (create or update people/companies, manage lists and tags, add notes, create and resolve tasks, move deals through stages, log touchpoints). Full read/write access to people, companies, pipelines, deals, lists, tags, notes, tasks, enrichment, campaigns, and sequence drafts.\n---\n\n# geni crm\n\n`geni crm` reads and writes the operator\'s General Input CRM: the lead database\n(people and companies), deal pipelines and their cards, lists, tags, notes,\ntasks, touchpoints, custom fields, and outbound campaigns with their sequence\ndrafts. It is part of the same `geni` CLI, so it\nuses the same session and active workspace. The workspace must have CRM access,\nor these commands return a 403. Run `geni crm --help` for the full surface, and\n`geni crm <noun> --help` for a noun\'s verbs.\n\nThe shape is `geni crm <noun> <verb>`. Each noun is a group: `people`,\n`companies`, `lists`, `tags`, `notes`, `tasks`, `pipelines`, `stages`, `cards`,\n`touchpoints`, `fields`, `employments`, `contact-points`, `campaigns`,\n`sequences`, `waterfalls`, `enrich`, plus a top-level `search`.\n\n## Finding things, then acting on them\n\nThe same two-step flow as the rest of geni: find an id, then read or write it.\n\n1. Find by name with one query across everything:\n `geni crm search "<text>" [--type person|company|list|pipeline|card]`. Or\n list one kind: `geni crm people "<text>"`, `geni crm companies "<text>"`,\n `geni crm pipelines`, `geni crm lists`, `geni crm tags`, `geni crm tasks`.\n `people` and `companies` also take `--filter`, a JSON array of column\n conditions, e.g. `--filter \'[{"field":"seniority","operator":"any_of","values":["vp"]},{"field":"icpScore","operator":"gte","value":70}]\'` \u2014\n see `--help` for the field and operator lists (custom fields filter as\n `custom.<key>`).\n2. Read one record: `geni crm people get <id>`, `geni crm companies get <id>`,\n `geni crm cards get <id>`, `geni crm pipelines get <id>` (add `--board` for\n its cards), `geni crm tasks get <id>`.\n\n## Writing\n\nCreates and updates take the record body as `--json`; the server validates it,\nso a 400 means the body was wrong (read the error and fix the JSON). Run\n`geni crm <noun> <verb> --help` to see the expected fields.\n\n- **Create / update records** (JSON body):\n - `geni crm people create --json \'[{"fullName":"Ada Lovelace","companyName":"Acme","email":"ada@acme.com"}]\'` (batch, find-or-create, deduped). `companies create` mirrors it. A `"created": false` result matched an existing record by identity key (email/LinkedIn; domain for companies) \u2014 the CLI warns on stderr when the matched name differs, e.g. a shared inbox collapsing distinct people.\n - `geni crm people update --json \'[{"id":"<id>","title":"VP Eng","linkedinUrl":"https://\u2026"}]\'` (batch, ids inline). `companies update` mirrors it. Writes take the create field names (`title`, `linkedinUrl`), not the read names you see on `get` (`currentTitle`, `primaryLinkedinUrl`); unknown keys are rejected with a 400 naming them.\n - `geni crm lists create --json \'{"name":"Q3 ICP","type":"company"}\'`, `geni crm tags create --json \'{"name":"Customer","entityType":"company"}\'`, `geni crm tasks create --json \'{"title":"Follow up","entity":{"type":"person","id":"<id>"}}\'`, `geni crm cards create <pipelineId> --json \'{"title":"Acme renewal","amount":50000}\'`.\n- **Notes** take the text directly: `geni crm notes create person <id> --body "Met at the conference"`.\n- **State-change verbs** (no JSON, just flags/ids):\n - Lists/tags: `geni crm lists add <listId> <entityIds...>`, `geni crm tags assign <tagId> <entityIds...>` (and `remove` / `unassign`).\n - Tasks: `geni crm tasks done <id>` (also `dismiss`, `reopen`, `delete`).\n - Cards: `geni crm cards move <id> --stage <stageId>`, `geni crm cards status <id> --status won|lost|open [--reason "..."]`, `geni crm cards archive <id>`, `geni crm cards add-contact <cardId> <personId>`.\n- **Deals/touchpoints**: `geni crm touchpoints log <cardId> --json \'{"channel":"call","occurredAt":"2026-07-01T15:00:00Z","summary":"Pricing call"}\'`.\n- **Delete** is `<noun> delete <id...>` (people/companies/lists take multiple ids; most others take one).\n\nCard edits, moves, and status changes use optimistic concurrency. Pass\n`--expected-updated-at <ts>` to enforce it; omit it and the CLI reads the card\'s\ncurrent version first (last-write-wins), which is usually what you want from a\nscript. With the token, a stale card fails with an HTTP 409 conflict; re-read\nthe card and retry.\n\n## Output\n\nList commands print a table; pass `--json` to parse. `get` commands and all\nwrites print the affected record as JSON (state-change verbs print a short\nconfirmation). The single-record `get` commands take `--field <path>` to pull\none value, e.g. `geni crm cards get <id> --field status`.\n\nJSON shapes vary by verb: searches print `{"results": [...]}` (people/companies\nadd `nextCursor`), `people get` prints `{person, company, contactPoints, ...}`,\nand bare noun lists wrap in a named key (e.g. `{"lists": [...]}`) \u2014 check before\npiping into a parser.\n\n## Enrichment\n\nFind and verify contact info for people through the workspace\'s configured\nprovider waterfalls. This is **paid** (it spends credits per provider call), so\nevery verb requires `--yes` and a run is capped at 25 people. Only enrich when\nthe operator has asked you to. Found emails and numbers save onto the person\'s\ncontact points automatically.\n\n- See what\'s wired first: `geni crm waterfalls` lists the provider chain for each\n capability (email-enrichment, email-validation, phone-enrichment). An empty\n chain finds nothing and spends nothing.\n- `geni crm enrich emails <personIds...> --yes` finds work emails;\n `geni crm enrich phones <personIds...> --yes` finds mobile numbers (both take\n `--retry-unverified`).\n- `geni crm enrich validate <personIds...> --yes` checks deliverability \u2014 run it\n before sequencing so you don\'t send to a bad address.\n\n## Campaigns and sequences (draft here \u2014 the dashboard delivers)\n\nOutbound is prep + export: campaigns group people under one purpose, each\nmember gets a fully personalized per-person sequence **draft**, and the\noperator syncs the campaign to an external sequencer (Instantly, Smartlead,\nCSV) from the dashboard. There is no sending from General Input, and the CLI\ncannot sync \u2014 by design. When drafts are ready, tell the operator to review\nand sync from the campaign\'s page in the dashboard.\n\n- `geni crm campaigns [query]` lists campaigns with member/sequence rollups;\n `get <id>` shows one (its `purpose` is the messaging angle every draft in it\n must serve); `--person <id>` lists the campaigns a person is in.\n- `geni crm campaigns create --json \'{"name":"Q3 fintech CFOs","purpose":"Book intro calls about closing automation"}\'`.\n Names are unique per workspace. `update <id>` and `delete <id>` exist;\n deleting removes the campaign\'s drafts too.\n- Membership first: `geni crm campaigns add <campaignId> <personIds...>` adds\n people; `members <id>` shows who is in and who still has no draft.\n `remove` also deletes the member\'s synced leads from linked sequencers \u2014\n it\'s how "stop emailing them" propagates.\n- `geni crm sequences [query] [--person <id>] [--campaign <id>]` lists\n drafts; `get <id>` shows the steps.\n- Draft: `geni crm sequences create --person <id> --campaign <id> --json \'{"steps":[{"subject":"\u2026","body":"\u2026","waitDays":0},{"body":"\u2026","waitDays":3}]}\'`.\n The first step carries the subject; follow-ups reply in-thread after\n `waitDays` with no reply. Read the campaign\'s `purpose` first and write to\n it. A member has ONE draft per campaign \u2014 creating again rewrites it (and\n the next sync updates the lead instead of duplicating it).\n- `geni crm sequences update <id> --json \'\u2026\'` replaces a draft wholesale;\n `delete <id>` removes a draft (the person stays a member).\n- Consider `geni crm enrich validate` on recipients first so the operator\n isn\'t syncing mail to a dead address.\n\n## Composing with the rest of geni\n\nThe CRM is the source of who and what; connected credentials are how you act on\nthe outside world. To add contact info, prefer `geni crm enrich` (it runs the\nworkspace\'s provider waterfalls and saves results). For anything else, pull\npeople or a company from the CRM, reach a service through `geni exec bash` (send\nan email, update an external system), and write the result back to the CRM (a\nnote, a task, a touchpoint, a moved card). Credit each tool naturally in your\nsummary.\n\n## Exit codes worth knowing\n\n- `0` success.\n- `4` not found (bad id, or it is not in the active workspace).\n- `5` forbidden (the workspace lacks CRM access, or the record is out of scope).\n- `9` stale write (a card changed since you read it; re-read and retry, or pass `--expected-updated-at`).\n- `78` session expired. Tell the operator to run `geni login`.\n';
@@ -24149,13 +24136,39 @@ function registerSkillsUninstall(parent) {
24149
24136
  });
24150
24137
  }
24151
24138
 
24139
+ // src/commands/skills/load.ts
24140
+ import { resolve as resolve21, join as join8 } from "path";
24141
+ function registerSkillsLoad(parent) {
24142
+ parent.command("load <name>").description(
24143
+ "Download a platform skill (SKILL.md + references/) into a local directory. Load the matching authoring skill (code-workflow, agent-workflow, app, skill-authoring) before building a resource: its references/ hold the type spec and a complete worked example."
24144
+ ).option(
24145
+ "--dir <path>",
24146
+ "Destination directory. Defaults to ./geni-skills/<name>."
24147
+ ).action(async (name, opts) => {
24148
+ const dir = resolve21(opts.dir ?? join8("geni-skills", name));
24149
+ try {
24150
+ const { fileCount, description } = await skillAuthoringService.loadPlatformSkill({ name, dir });
24151
+ printSuccess(`Loaded ${name} (${fileCount} file(s)) into ${dir}`);
24152
+ printInfo(description);
24153
+ printInfo(
24154
+ `Start with ${join8(dir, "SKILL.md")}; the spec and worked example (when the skill ships them) are under ${join8(dir, "references")}/.`
24155
+ );
24156
+ } catch (error) {
24157
+ exitOnApiError(error, {
24158
+ notFoundMessage: `Platform skill "${name}" not found. Authoring skills: code-workflow, agent-workflow, app, skill-authoring.`
24159
+ });
24160
+ }
24161
+ });
24162
+ }
24163
+
24152
24164
  // src/commands/skills/index.ts
24153
24165
  function registerSkillsCommands(program2) {
24154
24166
  const skills = program2.command("skills").description(
24155
- "Install (or remove) the agent-facing geni instructions in your AI coding agent. Detects Claude Code (others coming) and writes a skill file the agent loads automatically."
24167
+ "Install (or remove) the agent-facing geni instructions in your AI coding agent, and load platform skills (authoring contracts + worked examples) into a local directory."
24156
24168
  );
24157
24169
  registerSkillsInstall(skills);
24158
24170
  registerSkillsUninstall(skills);
24171
+ registerSkillsLoad(skills);
24159
24172
  }
24160
24173
 
24161
24174
  // src/lib/options.ts
@@ -25349,23 +25362,6 @@ var SequenceExportDestinationIdSchema = z30.enum([
25349
25362
  "heyreach",
25350
25363
  "expandi"
25351
25364
  ]);
25352
- function isValidTimeZone(timeZone) {
25353
- try {
25354
- new Intl.DateTimeFormat("en-US", { timeZone });
25355
- return true;
25356
- } catch {
25357
- return false;
25358
- }
25359
- }
25360
- var SequenceSendScheduleInputSchema = z30.object({
25361
- name: z30.string().min(1).max(120),
25362
- timezone: z30.string().refine(isValidTimeZone, "Unknown timezone"),
25363
- startHour: z30.number().int().min(0).max(23),
25364
- endHour: z30.number().int().min(1).max(24),
25365
- sendDays: z30.array(z30.number().int().min(1).max(7)).min(1).max(7)
25366
- }).refine((schedule) => schedule.startHour < schedule.endHour, {
25367
- message: "Start must be before end"
25368
- });
25369
25365
 
25370
25366
  // ../../packages/crm-api/dist/types/campaign.js
25371
25367
  import { z as z31 } from "zod";
@@ -26128,6 +26124,11 @@ var OAUTH_PROVIDER_GROUPS = {
26128
26124
  "google-search-console"
26129
26125
  ]
26130
26126
  },
26127
+ "google-ads": {
26128
+ title: "Google Ads",
26129
+ iconUrl: "https://icons.generalinput.com/google-ads.png",
26130
+ services: ["google-ads"]
26131
+ },
26131
26132
  microsoft: {
26132
26133
  title: "Microsoft",
26133
26134
  iconUrl: "https://icons.generalinput.com/microsoft.png",
@@ -28158,7 +28159,7 @@ function registerCrmCommands(program2) {
28158
28159
  import chalk9 from "chalk";
28159
28160
 
28160
28161
  // src/lib/preflight.ts
28161
- import { delimiter, join as join8 } from "path";
28162
+ import { delimiter, join as join9 } from "path";
28162
28163
  import { accessSync, constants } from "fs";
28163
28164
  var REQUIRED_RUNTIME_DEPS = ["bash", "curl", "jq"];
28164
28165
  function findOnPath(name) {
@@ -28166,7 +28167,7 @@ function findOnPath(name) {
28166
28167
  if (!path) return null;
28167
28168
  for (const dir of path.split(delimiter)) {
28168
28169
  if (dir.length === 0) continue;
28169
- const candidate = join8(dir, name);
28170
+ const candidate = join9(dir, name);
28170
28171
  try {
28171
28172
  accessSync(candidate, constants.X_OK);
28172
28173
  return candidate;
@@ -28450,11 +28451,11 @@ function isInsideDirectory(args) {
28450
28451
  return args.path.startsWith(args.directory + sep2);
28451
28452
  }
28452
28453
  function runNpmInstall() {
28453
- return new Promise((resolve21, reject) => {
28454
+ return new Promise((resolve22, reject) => {
28454
28455
  const child = spawn3("npm", ["install", "-g", `${PACKAGE_NAME}@latest`], {
28455
28456
  stdio: "inherit"
28456
28457
  });
28457
- child.once("exit", (code) => resolve21(code ?? 1));
28458
+ child.once("exit", (code) => resolve22(code ?? 1));
28458
28459
  child.once("error", (err) => reject(err));
28459
28460
  });
28460
28461
  }