@inflexa-ai/harness 0.41.1 → 0.41.2

package/dist/state/migrations/index.d.ts

@@ -0,0 +1,10 @@
+/**
+ * The versioned migrations of the Cortex state tables.
+ *
+ * The migrator applies them in the order of their names and records each one,
+ * thus a migration never changes after a release. A schema change is a new
+ * entry, with a name that sorts after every existing one.
+ */
+import type { Migration } from "kysely/migration";
+import type { Logger } from "../../lib/logger.js";
+export declare function cortexMigrations(logger: Logger): Record<string, Migration>;

package/dist/state/migrations/index.js

@@ -0,0 +1,13 @@
+/**
+ * The versioned migrations of the Cortex state tables.
+ *
+ * The migrator applies them in the order of their names and records each one,
+ * thus a migration never changes after a release. A schema change is a new
+ * entry, with a name that sorts after every existing one.
+ */
+import { baseline } from "./20260927120000_baseline.js";
+export function cortexMigrations(logger) {
+    return {
+        "20260927120000_baseline": baseline(logger),
+    };
+}

package/dist/tools/display/show-user.js

@@ -61,11 +61,13 @@ export const showUserTool = defineTool({
         "(kind=structure, by the URL `alphafold_prediction` returned). The content is inlined on the wire. " +
         "Pick this tool by what you are referencing, not by how the output looks: " +
         "NOT for an existing analysis file — never read an artifact and paste its bytes here, reference it with `show_file` " +
-        "(images, CSVs, PDFs, notebooks). NOT for a stored plan — use `show_plan`. " +
+        "(images, CSVs, PDFs, notebooks). Your own prose about the results is content you compose, so it belongs here. " +
+        "NOT for a stored plan — use `show_plan`. " +
         "NEVER put markdown image syntax pointing at a workspace file in a `markdown` body: `![](runs/.../volcano.png)` " +
-        "renders as a broken image, because the chat UI cannot resolve workspace-relative paths. To interleave figures " +
-        "with prose (a write-up, a narrative summary), emit a SEQUENCE of cards in display order — `show_user(markdown)` " +
-        "for a prose section, then `show_file` for the figures that follow it, and so on — instead of one monolithic card. " +
+        "renders as a broken image, because the chat UI cannot resolve workspace-relative paths. When an answer discusses " +
+        "two or more figures, emit a SEQUENCE of cards in one batch, in reading order — `show_user(markdown)` for a prose " +
+        "section, then the chart or the `show_file` it discusses, then the next section — instead of one monolithic card " +
+        "or reply text below all the cards. " +
         "One card per call, rendered in call order; an identical repeat call resolves to the same card, so compose the " +
         "finished content before calling rather than re-rendering a draft.",
     inputSchema: ShowUserInputSchema,

package/dist/tools/workspace/show-file.js

@@ -25,7 +25,7 @@ const ShowFileInputSchema = z.object({
     }))
         .min(1)
         .max(MAX_FILES)
-        .describe(`The related set of files to show together, 1 to ${MAX_FILES} per call; multiple render as ONE gallery card. Pass a related set in a single call — do not make one call per figure.`),
+        .describe(`The files to show together, 1 to ${MAX_FILES} per call; multiple render as ONE gallery card. Pass all the figures that one prose section discusses in a single call. Figures for different sections go in separate calls.`),
 });
 export const showFileTool = defineTool({
     id: "show_file",
@@ -36,8 +36,9 @@ export const showFileTool = defineTool({
         "Paths are analysis-rooted (no leading slash, no `..`); discover them with `workspace_search` or `list_files`. " +
         "The tool checks the shape of each path only, not that the file exists, so a wrong path fails only when the user views the card; " +
         "`shown: false` with `invalid_path` means a path has a leading slash or a `..` segment. " +
-        "Up to 10 files per call — pass a related set in ONE call and they render as a gallery, rather than one call per figure. " +
-        "Cards render in call order, so to interleave figures with prose alternate `show_user(markdown)` and `show_file` calls " +
+        "Up to 10 files per call, rendered as one gallery — pass all the figures that one prose section discusses in ONE call. " +
+        "Cards render in call order, so to put figures next to their prose, emit `show_user(markdown)` sections and `show_file` " +
+        "calls in one batch, in reading order: a section, then the `show_file` for its figures, then the next section " +
         "(markdown image syntax pointing at a workspace file does NOT render — this tool is the only way to show one).",
     inputSchema: ShowFileInputSchema,
     // `.min(1)` on `files` makes index 0 total after the parse.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@inflexa-ai/harness",
-    "version": "0.41.1",
+    "version": "0.41.2",
     "description": "Host-agnostic bioinformatics agent harness — hand-rolled agent loop, DBOS-durable workflows, sandboxed compute.",
     "license": "Apache-2.0",
     "type": "module",
@@ -77,6 +77,7 @@
         "hono": "^4.12.34",
         "hyparquet": "^1.28.1",
         "js-tiktoken": "^1.0.21",
+        "kysely": "^0.29.6",
         "mime": "^4.1.0",
         "nanoid": "^5.1.16",
         "neverthrow": "^8.2.0",