@allocator-one/harness-cli 1.15.0 → 1.15.1

package/dist/{server-O7CX2ZCC.js → server-KVRQBVXI.js}

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import {
   ACTIVITY_MAX_LIMIT,
-  CLI_VERSION,
+  BUDGET_MAX_DOLLARS,
   CONDITION_KINDS,
   Client,
   GATE_OWNER_ROLES,
@@ -11,6 +11,8 @@ import {
   JOB_STATES,
   JOB_STATUS_ALIASES,
   MAX_IDEMPOTENCY_KEY_BYTES,
+  MCP_SURFACE,
+  OUTCOME_MAX_CHARACTERS,
   PLAN_EXECUTORS,
   RELATION_CREATE_TYPES,
   RELATION_UPDATE_TYPES,
@@ -61,6 +63,7 @@ import {
   planHold,
   planRelease,
   planShow,
+  prepareRun,
   procedureRun,
   procedureSave,
   procedureShow,
@@ -77,6 +80,7 @@ import {
   search,
   show,
   skillsList,
+  startRun,
   stateAdd,
   stateDelete,
   stateOrder,
@@ -92,7 +96,12 @@ import {
   upload,
   userList,
   workflowStates
-} from "./chunk-I2S2JVCQ.js";
+} from "./chunk-L2OWOZ4N.js";
+import {
+  CLI_VERSION,
+  invokedName,
+  named
+} from "./chunk-FQWV5MIC.js";
 
 // src/mcp/server.ts
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
@@ -102,11 +111,11 @@ var NeedsLoginError = class extends Error {
 };
 function context() {
   const resolved = resolveConfig();
-  for (const warning of resolved.warnings) process.stderr.write(warning + "\n");
+  for (const warning of resolved.warnings) process.stderr.write(named(warning + "\n"));
   if (resolved.kind === "error") throw new NeedsLoginError(resolved.message);
   if (resolved.kind === "needs-login") {
     throw new NeedsLoginError(
-      `Not signed in to ${resolved.baseUrl}. Run \`harness login\` in a terminal (or set HARNESS_API_TOKEN for headless use) \u2014 the MCP server never opens a browser itself.`
+      `Not signed in to ${resolved.baseUrl}. Run \`${invokedName()} login\` in a terminal (or set HARNESS_API_TOKEN for headless use) \u2014 the MCP server never opens a browser itself.`
     );
   }
   return { client: new Client(resolved.config), config: resolved.config };
@@ -122,7 +131,7 @@ async function run(work) {
     const output = await work(ctx);
     const content = [{ type: "text", text: JSON.stringify(output.json) }];
     if (output.notice !== void 0 && output.notice !== "") {
-      content.push({ type: "text", text: output.notice.trimEnd() });
+      content.push({ type: "text", text: named(output.notice.trimEnd()) });
     }
     if (output.partial === true) {
       content.push({ type: "text", text: "partial failure \u2014 inspect the JSON entries for per-item errors" });
@@ -133,10 +142,10 @@ async function run(work) {
     const error = explainExpertRefusal(caught, token);
     if (error instanceof NeedsLoginError) return toolError(error.message);
     if (error instanceof HttpError) {
-      return toolError(`${error.message} (HTTP ${error.status})${errorDetails(error.body)}`);
+      return toolError(named(`${error.message} (HTTP ${error.status})${errorDetails(error.body)}`));
     }
     if (error instanceof TransportError) return toolError(`cannot reach the API: ${error.message}`);
-    if (error instanceof Error) return toolError(error.message);
+    if (error instanceof Error) return toolError(named(error.message));
     throw error;
   }
 }
@@ -258,6 +267,40 @@ var OPERATOR_CONTROL_TOOLS = [
     handler: (ctx, args) => jobPause(ctx, args["id"])
   }
 ];
+var OPERATOR_RUN_TOOLS = [
+  {
+    name: "job_start",
+    description: `Start an Operator job from an outcome, as Run as job does in Chat Mode in the app: the request is posted, attributed to the caller, in a new organization chat of theirs, and Operator takes it from there under the caller's own current rights. Returns job_id, state, workbench_url and, when a change set already awaits approval, approval_url. Approval happens in the app: give a person the approval_url; this tool never approves anything, and no tool does. Each call starts another job, so never call it again to "retry": not after a timeout, a dropped connection or a 5xx either. An "Outcome unknown" error means a job may have been started; look for it with jobs_list (mine) before calling again. Only the organization's admins may pass a budget. Follow the job with job_show.`,
+    readOnly: false,
+    destructive: false,
+    idempotent: false,
+    shape: {
+      outcome: z.string().describe(
+        `what the job should achieve, in plain language: 1 to ${OUTCOME_MAX_CHARACTERS} characters once trimmed`
+      ),
+      budget: z.number().positive().max(BUDGET_MAX_DOLLARS).optional().describe(
+        `the job's budget in US dollars, at most two decimals, up to ${BUDGET_MAX_DOLLARS}; only the organization's admins may pass one`
+      ),
+      skill: z.string().optional().describe("an Operator skill's invocation name, like /summarize-lps (skills_list names them)")
+    },
+    handler: async (ctx, args) => {
+      const request = prepareRun(args["outcome"], {
+        budget: args["budget"] === void 0 ? void 0 : String(args["budget"]),
+        skill: args["skill"]
+      }, MCP_SURFACE);
+      const job = await startRun(ctx, request, MCP_SURFACE);
+      return {
+        json: {
+          job_id: job.job_id,
+          state: job.state,
+          workbench_url: job.workbench_url,
+          ...job.approval_url === null ? {} : { approval_url: job.approval_url }
+        },
+        human: `Started Operator job ${job.job_id}.`
+      };
+    }
+  }
+];
 var NOT_IDEMPOTENT = 'Not idempotent: never retry it automatically, not after a timeout or a 5xx either. An "Outcome unknown" error may have landed and says what to check before calling again; only "cannot reach the API" means the request never reached the server, so nothing changed.';
 var OPERATOR_LIFECYCLE_TOOLS = [
   {
@@ -499,7 +542,7 @@ var TOOLS = [
   },
   {
     name: "comment_list",
-    description: "An issue's full comment thread, untruncated.",
+    description: "An issue's complete comment thread, oldest first. Follows every older page; pagination failures return an error, not a partial thread.",
     readOnly: true,
     shape: { id: identifier },
     handler: (ctx, args) => comments(ctx, args["id"])
@@ -871,7 +914,7 @@ var TOOLS = [
   // ── Plans and gates ──
   {
     name: "plan_create",
-    description: "Create a plan: a root issue and up to 99 steps, created in one transaction or not at all, and held until a person releases it (plan_release). Steps refer to each other by key: parent (containment) and blocked_by (dependencies). executor operator files a step in the organization's Operator team, where only the plan driver claims it; a person's step goes to its team (or the plan's). conditions are wait conditions (not_before, gate, event); a gate may carry a key (gate: <key> is shorthand) and an owner, who alone ticks it. An invalid plan writes nothing and the error lists every violation by step key. Reuse idempotency_key when retrying.",
+    description: "Create a plan: a root issue and up to 99 steps, created in one transaction or not at all, and held until a person releases it (plan_release). Steps refer to each other by key: parent (containment) and blocked_by (dependencies). executor operator files a step in the organization's Operator team, where only the plan driver claims it; a person's step goes to its team (or the plan's). conditions are wait conditions (not_before, gate, event); a gate may carry a key (gate: <key> is shorthand) and an owner, who alone ticks it. An invalid plan writes nothing and the error lists every violation by step key. Reuse idempotency_key when retrying. Once released, the changes an Operator step proposes need a person's approval in the app, as plan_release says.",
     readOnly: false,
     shape: {
       team: z.string().optional().describe("team key for the root and people's steps; defaults to HARNESS_TEAM"),
@@ -889,7 +932,7 @@ var TOOLS = [
   },
   {
     name: "plan_edit",
-    description: "Change step executors and keys (each step named by its key or issue identifier) and the plan's budgets. Editing a released step holds it until the plan is released again; a budget edit needs the plan held. Descriptions, parents and edges are edited with issue_update and relation_add/relation_rm; conditions are set at plan_create, and gate_set ticks a gate.",
+    description: "Change step executors and keys (each step named by its key or issue identifier) and the plan's budgets. Editing a released step holds it until the plan is released again; a budget edit needs the plan held. Descriptions, parents and edges are edited with issue_update and relation_add/relation_rm; conditions are set at plan_create, and gate_set ticks a gate. Once released, the changes an Operator step proposes need a person's approval in the app, as plan_release says.",
     readOnly: false,
     shape: {
       id: planId,
@@ -904,7 +947,7 @@ var TOOLS = [
   },
   {
     name: "plan_release",
-    description: "Release a held plan (or one that needs attention) as the caller: freezes its next revision and lets its ready steps run. A plan with Operator steps needs a spend budget and the caller's right to run Operator; collaborators join its plan room.",
+    description: "Release a held plan (or one that needs attention) as the caller: freezes its next revision and lets its ready steps run. A plan with Operator steps needs a spend budget and the caller's right to run Operator; collaborators join its plan room. Each Operator step runs as a job (jobs_list names its plan_step), and the changes a job proposes need a person's approval in the app: give them the job's approval_url. No tool approves.",
     readOnly: false,
     shape: {
       id: planId,
@@ -927,7 +970,7 @@ var TOOLS = [
   },
   {
     name: "gate_set",
-    description: "Satisfy (satisfied true) or un-satisfy (false) a gate wait condition on an issue, found by its key, label or condition id (condition_list and issue_show list conditions). Needs staff standing in the organization or a place in its plan's room; only an owned gate's owner ticks it, and its owner or staff untick it. Anyone else gets a 403 naming the owner. An outside expert's pxc_ credential ticks the gates it owns on a step assigned to it (assignment_list); any other step is 404.",
+    description: "Satisfy (satisfied true) or un-satisfy (false) a gate wait condition on an issue, found by its key, label or condition id (condition_list and issue_show list conditions). Needs staff standing in the organization or a place in its plan's room; only an owned gate's owner ticks it, and its owner or staff untick it. Anyone else gets a 403 naming the owner. An outside expert's pxc_ credential ticks the gates it owns on a step assigned to it (assignment_list); any other step is 404. An Operator-only login (operator-cli) is refused here, as on every tool outside Operator's, even for a person in the plan's room.",
     readOnly: false,
     shape: {
       issue: identifier,
@@ -954,6 +997,8 @@ var TOOLS = [
   ...OPERATOR_JOB_TOOLS,
   // ── Operator job controls (CLI-46) ──
   ...OPERATOR_CONTROL_TOOLS,
+  // ── Operator job start (CLI-45) ──
+  ...OPERATOR_RUN_TOOLS,
   // ── Operator job lifecycle (CLI-47) ──
   ...OPERATOR_LIFECYCLE_TOOLS,
   // ── Uploads ──

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@allocator-one/harness-cli",
-  "version": "1.15.0",
+  "version": "1.15.1",
   "description": "CLI and MCP server for Harness, allocator.one's issue tracker",
   "type": "module",
   "license": "MIT",