@m6d/cortex-cli 0.7.0 → 0.8.1

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@m6d/cortex-cli",
-    "version": "0.7.0",
+    "version": "0.8.1",
     "description": "Scaffold and operate Cortex servers",
     "license": "MIT",
     "type": "module",

package/src/contracts/charts/chart-spec.ts

@@ -1,6 +1,6 @@
 /*
  * The boundary on a Vega-Lite spec the model wrote, shared by the widget
- * (which draws it live) and, as needed, the server:
+ * (which draws it live) and the server (which describes it to the model):
  * inline data only, no fetches, no interactivity, bounded work.
  */
 
@@ -18,6 +18,9 @@ const EXPANDING_TRANSFORMS = new Set([
     "sample",
 ]);
 
+/** The boundary as the model reads it in its system prompt, so it writes specs this file accepts. */
+export const CHART_SPEC_GUIDE = `Use Vega-Lite JSON with inline \`data.values\` only, at most ${MAX_CHART_ROWS} rows, and no \`url\` anywhere. Compute folds, trend lines and densities yourself. For several series, write one row per series and x value, or keep one row per x value and draw a layer per series (color by \`datum\`) when that would exceed the row limit. These keys are refused anywhere in the spec: ${[...EXPANDING_TRANSFORMS, "params", "selection"].join(", ")}. Expressions in \`calculate\`, \`filter\` and \`labelExpr\` may use only datum fields, literals, operators and simple math or date-part functions (no format or timeFormat), so put formatted values in the rows or use an axis \`format\`.`;
+
 /** What a single key or value in a chart spec may not be; undefined when it is fine on its own. */
 function chartNodeViolation(key: string, value: unknown) {
     if (key === "url") return "Charts may only use inline data and no URLs.";

package/src/contracts/charts/index.ts

@@ -1,4 +1,5 @@
 export {
+    CHART_SPEC_GUIDE,
     chartSpecViolation,
     externalResourceIn,
     IMAGE_FUNCTION,

package/src/contracts/runtime/triggers.ts

@@ -20,6 +20,9 @@ import {
 
 export const MESSAGE_TRIGGER_NAME = "message";
 
+/** The tool a trigger run with an output schema answers through; no other tool may take its name. */
+export const TRIGGER_ANSWER_TOOL_NAME = "submitAnswer";
+
 /**
  * The first characters of a fire bearer say what it is: the secret callers
  * hold, or a one-shot test token the console minted. A test token is a JWT
@@ -98,9 +101,10 @@ export const triggerDeclarationSchema = z.object({
     input: z.record(z.string(), z.unknown()),
     /**
      * JSON Schema the run's answer must match, or null for a free-text run.
-     * The server asks the model for that shape, validates what comes back,
-     * and stores it as the firing's `output`; a run whose answer does not
-     * parse fails with reason `invalid_output`.
+     * The run submits it through an answer tool whose input is this schema,
+     * and the server stores it as the firing's `output`; a run that never
+     * submits fails with `no_output`, one whose answers the schema refused
+     * with `invalid_output`.
      */
     output: z.record(z.string(), z.unknown()).nullable(),
     /**

package/src/scaffold/files.ts

@@ -27,7 +27,7 @@ export type Database = "postgres" | "mssql";
 // sync (scripts/sync-package-versions.ts) restamps it and files.test.ts holds
 // them to that.
 export const DEPENDENCIES = {
-    "@m6d/cortex-server": "~0.7.0",
+    "@m6d/cortex-server": "~0.8.1",
     "@tanstack/ai": "^0.55.0",
     "@tanstack/ai-openai": "^0.22.8",
     hono: "^4.12.3",