@letterstory/cli 0.33.5 → 0.33.6

package/lib/cli.mjs

@@ -45,7 +45,7 @@ import {
 } from "./commands.mjs";
 
 // Keep in sync with cli/package.json.
-export const VERSION = "0.33.5";
+export const VERSION = "0.33.6";
 
 // Flags that never take a value. Listing them explicitly means `deploy get --json <id>`
 // can't accidentally swallow the id as --json's value.

package/lib/commands/kernel.mjs

@@ -198,6 +198,26 @@ export const ARGS = {
 		endpoint_id: { positional: 1, label: "endpoint-id", required: true },
 		config: { value: (flags) => readJsonFileFlag(flags, "file") },
 	},
+	// The eval itself is one JSON file (--file), not flags — `detector` is a discriminated
+	// union with a different shape per kind, which flags-per-field cannot represent without
+	// nine different flag sets. Each field below reads the same file; a small re-parse per
+	// field, harmless for a one-shot CLI command against a small file.
+	add_kernel_custom_eval: {
+		kernel_id: { positional: 1, label: "kernel-id", required: true },
+		// `value` sources aren't checked against `required` (see shared.mjs readArgSource) —
+		// a missing id/name/detector reaches the tool call and comes back as the tool's own
+		// "Invalid arguments" error, same as any other malformed submission.
+		id: { value: (flags) => readJsonFileFlag(flags, "file")?.id },
+		name: { value: (flags) => readJsonFileFlag(flags, "file")?.name },
+		description: { value: (flags) => readJsonFileFlag(flags, "file")?.description },
+		detector: { value: (flags) => readJsonFileFlag(flags, "file")?.detector },
+		repair: { value: (flags) => readJsonFileFlag(flags, "file")?.repair },
+		regimes: { value: (flags) => readJsonFileFlag(flags, "file")?.regimes },
+	},
+	remove_kernel_custom_eval: {
+		kernel_id: { positional: 1, label: "kernel-id", required: true },
+		eval_id: { positional: 2, label: "eval-id", required: true },
+	},
 };
 
 export async function cmdKernel(ctx) {
@@ -215,6 +235,8 @@ export async function cmdKernel(ctx) {
 			return kernelEndpoints(rest);
 		case "endpoint":
 			return kernelEndpoint(rest);
+		case "eval":
+			return kernelEval(rest);
 		case "write":
 			return kernelWrite(rest);
 		case "polish":
@@ -227,7 +249,7 @@ export async function cmdKernel(ctx) {
 			return kernelBalance(rest);
 		default:
 			throw new CliError(
-				`Unknown kernel subcommand: ${sub ?? "(none)"}. Try: list, endpoints, endpoint, write, polish, run-status, runs, balance, run, status`
+				`Unknown kernel subcommand: ${sub ?? "(none)"}. Try: list, endpoints, endpoint, eval, write, polish, run-status, runs, balance, run, status`
 			);
 	}
 }
@@ -402,6 +424,54 @@ async function kernelEndpoint(ctx) {
 	throw new CliError(`Unknown kernel endpoint action: ${action ?? "(none)"}. Try: create, delete, config`);
 }
 
+/**
+ * `kernel eval add|rm` — an org-owned kernel's `rules.custom[]`, its own evals filed
+ * alongside the kernels service's built-in rules.
+ *
+ * `add` reads the whole eval (id/name/description/detector/repair/regimes) from one
+ * JSON file rather than flags: `detector` is a discriminated union with a different
+ * shape per kind, which a flag-per-field mapping (the pattern the rest of this file
+ * uses) cannot represent without nine different flag sets. Every genuinely new id
+ * lands at status "proposed" on the kernels service and is never auto-activated —
+ * this command cannot change that, only file the proposal.
+ */
+async function kernelEval(ctx) {
+	const { client, positionals, flags, io } = ctx;
+	const action = positionals[0];
+	if (action === "add") {
+		if (flagStr(flags.file) === undefined) {
+			throw new CliError(
+				"Provide the eval as JSON with --file <path> (id/name/description/detector/repair/regimes)."
+			);
+		}
+		const args = argsFromFlags(ARGS.add_kernel_custom_eval, flags, positionals);
+		const result = await client.callTool("add_kernel_custom_eval", args);
+		const filing = toolField(result, "custom_evals");
+		if (filing?.filed?.includes(args.id)) ok(ctx, `Filed "${args.id}" as a proposal (status: proposed).`);
+		else if (filing?.skipped?.includes(args.id))
+			ok(
+				ctx,
+				`"${args.id}" was already filed from an earlier submission — this only updated the kernel's own declaration.`
+			);
+		printResult(io, flags, result);
+		return 0;
+	}
+	if (action === "rm" || action === "remove" || action === "delete") {
+		const args = argsFromFlags(ARGS.remove_kernel_custom_eval, flags, positionals);
+		if (!flags.yes) {
+			io.error(
+				`This only stops declaring the eval on this kernel — it does NOT retire anything already filed or approved server-side. Re-run with --yes to confirm: ${ctx.bin} kernel eval rm ${args.kernel_id} ${args.eval_id} --yes`
+			);
+			return 1;
+		}
+		const result = await client.callTool("remove_kernel_custom_eval", args);
+		ok(ctx, `Stopped declaring "${args.eval_id}" on this kernel.`);
+		printResult(io, flags, result);
+		return 0;
+	}
+	throw new CliError(`Unknown kernel eval action: ${action ?? "(none)"}. Try: add, rm`);
+}
+
 /**
  * The OTHER door: run the same pipeline against a document you already have, instead of
  * writing a new one. Decomposed into a brief and GENERATED FRESH (content_kind: "article",

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@letterstory/cli",
-	"version": "0.33.5",
+	"version": "0.33.6",
 	"description": "Spin up and manage Letterstory phantom blogs from your terminal.",
 	"type": "module",
 	"license": "UNLICENSED",