@poncho-ai/harness 0.43.0 → 0.43.1

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
-> @poncho-ai/harness@0.43.0 build /home/runner/work/poncho-ai/poncho-ai/packages/harness
+> @poncho-ai/harness@0.43.1 build /home/runner/work/poncho-ai/poncho-ai/packages/harness
 > node scripts/embed-docs.js && tsup src/index.ts --format esm --dts
 
 [embed-docs] Generated poncho-docs.ts with 4 topics
@@ -8,9 +8,9 @@
 CLI tsup v8.5.1
 CLI Target: es2022
 ESM Build start
+ESM dist/index.js            506.50 KB
 ESM dist/isolate-VY35DGLM.js 49.43 KB
-ESM dist/index.js            506.40 KB
-ESM ⚡️ Build success in 222ms
+ESM ⚡️ Build success in 164ms
 DTS Build start
-DTS ⚡️ Build success in 6907ms
+DTS ⚡️ Build success in 6912ms
 DTS dist/index.d.ts 80.85 KB

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @poncho-ai/harness
 
+## 0.43.1
+
+### Patch Changes
+
+- [`134fae7`](https://github.com/cesr/poncho-ai/commit/134fae7eb4f3658b8d2dc0a5e560b0bcad094679) Thanks [@cesr](https://github.com/cesr)! - fix(harness): conversations.search now works on Postgres
+
+  The SQL for `engine.conversations.search()` matched `data LIKE $3`, but
+  `data` is a `jsonb` column in Postgres — `jsonb LIKE text` raises
+  `operator does not exist: jsonb ~~ unknown` (Postgres error 42883), so
+  every search call against a Postgres-backed engine 500'd at runtime.
+
+  Cast `data` to text in the Postgres branch (`data::text LIKE $3`).
+  SQLite stores `data` as TEXT-of-JSON, so no cast there.
+
+  Discovered while wiring `GET /me/conversations/search` in PonchOS.
+
 ## 0.43.0
 
 ### Minor Changes

package/dist/index.js

@@ -3701,11 +3701,12 @@ var SqlStorageEngine = class {
       const filterTenant = tenantId !== void 0;
       const pattern = `%${query}%`;
       const params = [this.agentId, pattern, pattern];
+      const dataMatch = this.dialect.tag === "postgresql" ? "data::text LIKE $3" : "data LIKE $3";
       let sql = `SELECT id, title, updated_at, created_at, owner_id, tenant_id,
                         message_count, parent_conversation_id, parent_message_id,
                         has_pending_approvals, channel_meta
                  FROM conversations
-                 WHERE agent_id = $1 AND (title LIKE $2 OR data LIKE $3)`;
+                 WHERE agent_id = $1 AND (title LIKE $2 OR ${dataMatch})`;
       if (filterTenant) {
         sql += ` AND tenant_id = $4`;
         params.push(tid);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@poncho-ai/harness",
-  "version": "0.43.0",
+  "version": "0.43.1",
   "description": "Agent execution runtime - conversation loop, tool dispatch, streaming",
   "repository": {
     "type": "git",

package/src/storage/sql-dialect.ts

@@ -572,11 +572,16 @@ export abstract class SqlStorageEngine implements StorageEngine {
       const pattern = `%${query}%`;
       // SQLite uses positional ? so we can't reuse $2, need separate params
       const params: unknown[] = [this.agentId, pattern, pattern];
+      // Postgres rejects `jsonb LIKE text` — cast `data` to text in
+      // Postgres so the LIKE applies to its JSON serialization. SQLite's
+      // `data` column is TEXT (raw JSON string) so no cast needed.
+      const dataMatch =
+        this.dialect.tag === "postgresql" ? "data::text LIKE $3" : "data LIKE $3";
       let sql = `SELECT id, title, updated_at, created_at, owner_id, tenant_id,
                         message_count, parent_conversation_id, parent_message_id,
                         has_pending_approvals, channel_meta
                  FROM conversations
-                 WHERE agent_id = $1 AND (title LIKE $2 OR data LIKE $3)`;
+                 WHERE agent_id = $1 AND (title LIKE $2 OR ${dataMatch})`;
       if (filterTenant) {
         sql += ` AND tenant_id = $4`;
         params.push(tid);