@promptev/context-engine 0.0.4 → 0.0.5

package/dist/skills/context-engine/SKILL.md

@@ -130,6 +130,31 @@ await engine.search(q, { principals: user.groups }); // scoped
   header before the LLM sees a schema, and sweeps the result.
 - Filing a document under an ACL the caller does not hold returns **403**, on
   ingest and on PATCH alike.
+- **`executeTool` cuts its `result` to 8,000 characters and 100 rows by
+  default.** A cut result is `{ _truncated, _original_size }` — a model
+  reading only that prefix will say "not found" about data that was there.
+  Size the budget to the model's window with `resultMaxChars` /
+  `resultMaxRows` (omitted = default, `null` = no limit; rows are per table,
+  and a db tool's own `max_rows`, default 1000, still applies first).
+  `responseMode: "tsv"` works for ANY tool: every array of objects in the
+  result (db `rows`, an HTTP body's list, a function's returned list) becomes
+  a TSV string under the same key — header first, `\N` = NULL, nested values
+  as JSON cells, tab/newline/backslash escaped — and the budget cuts at whole
+  rows, reporting `_result_shaping: { "<dotted.path>": { rows_returned,
+  rows_omitted } }`. Everything else stays JSON. The audit row keeps the
+  original under its own 50KB cap regardless. An http tool can store
+  `response_mode: "tsv"` in its config (every method, `QUERY` included;
+  omitted = `json`); an explicit `responseMode` on the call wins. The
+  conversion alone is `formatResult(result, "tsv")`.
+
+  ```ts
+  const out = await engine.executeTool("db_sales", { query: "SELECT * FROM orders" }, {
+    principals,
+    resultMaxChars: 200_000,
+    resultMaxRows: null,
+    responseMode: "tsv",
+  });
+  ```
 
 ## Search
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@promptev/context-engine",
-  "version": "0.0.4",
+  "version": "0.0.5",
   "description": "Promptev Context Engine — language-agnostic ingestion + hybrid retrieval (TypeScript)",
   "license": "Apache-2.0",
   "author": "Promptev Inc",

package/src/skills/context-engine/SKILL.md

@@ -130,6 +130,31 @@ await engine.search(q, { principals: user.groups }); // scoped
   header before the LLM sees a schema, and sweeps the result.
 - Filing a document under an ACL the caller does not hold returns **403**, on
   ingest and on PATCH alike.
+- **`executeTool` cuts its `result` to 8,000 characters and 100 rows by
+  default.** A cut result is `{ _truncated, _original_size }` — a model
+  reading only that prefix will say "not found" about data that was there.
+  Size the budget to the model's window with `resultMaxChars` /
+  `resultMaxRows` (omitted = default, `null` = no limit; rows are per table,
+  and a db tool's own `max_rows`, default 1000, still applies first).
+  `responseMode: "tsv"` works for ANY tool: every array of objects in the
+  result (db `rows`, an HTTP body's list, a function's returned list) becomes
+  a TSV string under the same key — header first, `\N` = NULL, nested values
+  as JSON cells, tab/newline/backslash escaped — and the budget cuts at whole
+  rows, reporting `_result_shaping: { "<dotted.path>": { rows_returned,
+  rows_omitted } }`. Everything else stays JSON. The audit row keeps the
+  original under its own 50KB cap regardless. An http tool can store
+  `response_mode: "tsv"` in its config (every method, `QUERY` included;
+  omitted = `json`); an explicit `responseMode` on the call wins. The
+  conversion alone is `formatResult(result, "tsv")`.
+
+  ```ts
+  const out = await engine.executeTool("db_sales", { query: "SELECT * FROM orders" }, {
+    principals,
+    resultMaxChars: 200_000,
+    resultMaxRows: null,
+    responseMode: "tsv",
+  });
+  ```
 
 ## Search