@axiom-lattice/pg-stores 5.2.0 → 5.2.2

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
-> @axiom-lattice/pg-stores@5.2.0 build /home/runner/work/agentic/agentic/packages/pg-stores
+> @axiom-lattice/pg-stores@5.2.2 build /home/runner/work/agentic/agentic/packages/pg-stores
 > tsup src/index.ts --format cjs,esm --dts --sourcemap
 
 CLI Building entry: src/index.ts
@@ -10,11 +10,11 @@
 ESM Build start
 CJS dist/index.js     585.57 KB
 CJS dist/index.js.map 1.04 MB
-CJS ⚡️ Build success in 1619ms
+CJS ⚡️ Build success in 1523ms
 ESM dist/index.mjs     574.26 KB
 ESM dist/index.mjs.map 1.04 MB
-ESM ⚡️ Build success in 1620ms
+ESM ⚡️ Build success in 1524ms
 DTS Build start
-DTS ⚡️ Build success in 15871ms
+DTS ⚡️ Build success in 12008ms
 DTS dist/index.d.ts  123.99 KB
 DTS dist/index.d.mts 123.99 KB

package/CHANGELOG.md

@@ -1,5 +1,132 @@
 # @axiom-lattice/pg-stores
 
+## 5.2.2
+
+### Patch Changes
+
+- 9bbf5ce: ## Collection batch tools and Open MCP consolidation
+
+  BREAKING (core): the collection agent tool `add_entry` is replaced by
+  `add_entries` without a compatibility alias, so agent prompts, skills, and
+  saved tool allowlists that name `add_entry` must update. `add_entries` accepts
+  1-50 entries, performs one all-or-nothing vector-store call, and generates each
+  entry's `_id` and `_created_at`. Collection middleware, plugin metadata,
+  capability mapping, built-in guidance, and the React tool catalog are kept in
+  sync.
+
+  The collection delete agent tool `delete_entry` is also replaced by
+  `delete_entries` without a compatibility alias: it accepts 1-50 ids and performs
+  one idempotent `in` vector-store delete on pgvector/memory, with an exact-ID
+  fallback for unknown backends so an unsupported filter cannot wipe a collection.
+  `SimpleMemoryVectorStore` now supports `in`/`notIn` metadata filters. Deleting a
+  collection now also drops its vector store, and single-entry create/update keep
+  server-owned identity and attempt to restore the old entry if a rewrite fails.
+
+  Open MCP now exposes all ten collection tools under the sole `collection` domain
+  (`collection_<action>`) with readOnly/destructive annotations. The built-in
+  `kbProvider` / `kb_search` tool and `kb` domain are removed; browser/preview and
+  sandbox tokens now carry the read-only `collection.search_collection` grant
+  instead. Open credentials still need a collection grant to call the tools, and key
+  creation/update rejects empty-item collection grants so a destructive domain
+  cannot be granted wholesale by accident.
+
+  Additive surfaces: REST gains `POST /api/collections/:name/entries/batch` and
+  `DELETE /api/collections/:name/entries/batch`, and the client SDK gains
+  `client.collections.entries(name).createMany()` / `deleteMany()`, sharing the
+  same limit and all-or-nothing semantics. Existing single-entry endpoints,
+  `create()`, and `delete(id)` are unchanged.
+
+  ## OIDC public clients
+
+  Make the OIDC client secret optional so public clients can use Authorization
+  Code + PKCE with `token_endpoint_auth_method=none`, matching the protocol
+  default. `OIDC_CLIENT_SECRET` may be omitted for the env provider, Platform
+  Admin's provider form no longer requires a secret on create, and the gateway,
+  client SDK, and Platform Ops provider tools accept a secret-less configuration.
+  Confidential clients continue to use the existing encrypted client-secret flow.
+
+  ## Security dependency updates
+
+  Follow up the Wiz remediation with `pnpm audit`: bump the pinned transitive
+  dependencies to the advisories published after the scan (shell-quote 1.11 —
+  critical command injection — fastify 5.12.6, @fastify/busboy 3.2.2,
+  @hono/node-server 2.1.3, brace-expansion 1.1.21/2.1.7/5.0.12,
+  body-parser 1.20.9/2.4.0, decode-uri-component 0.5.1, fast-uri 3.1.9/4.2.3,
+  glob 10.5/11.1/14.0.4, langsmith 0.12, picomatch 2.3.2/4.0.4,
+  protobufjs 7.6.5/8.8.1, source-map-js 1.2.2, undici 7.30.1, sanitize-html
+  2.18.1, tar 7.5.22, tmp 0.2.7, vite 6.4.5, yaml 2.9.1, ajv 6.14/8.18,
+  mysql2 3.23.1, uuid 11.1, and others). Overrides are scoped per major line
+  where different majors are both required, and none pins below a declaring
+  package's range. Further zero-out pass: echarts 5.5 → 6.1 in react-sdk,
+  katex 0.19.1 (the patched range starts at 0.18.2), glob 14.0.4 for every
+  affected major line (10/11/13/14; glob 7 is outside the advisory range),
+  minimatch 11.0.8 for every vulnerable line, rimraf 4/5 → 6.1.4 (drops the
+  glob 9 dependency), ibm-cloud-sdk-core 5.9.4 (pulls file-type 21.3.4), and
+  fast-xml-parser 5.12.0. The client-sdk build moves from tsup 6.7 to 8.5,
+  clearing the last GHSA-3mv9-4h5g-vhg3 finding. Drop the unused `xlsx`
+  dependency from `apps/web`, which has no patched npm release.
+
+  Overrides only apply to this monorepo, so also raise the published packages'
+  own dependency ranges to patched versions, otherwise downstream consumers
+  (fina_demo) resolve the old lower bounds when they reinstall: fastify
+  ^5.12.6 (gateway, microsandbox-service, opensandbox-gateway), react-router
+  ^7.18.2, vite ^6.4.5, mysql2 ^3.23.1 (core), and uuid ^11.1.1 (core, gateway,
+  pg-stores, react-sdk, and the cli-a2a peer range).
+
+  ## Reverse-proxy mount-prefix support
+
+  Support deploying the gateway behind a reverse-proxy path prefix (`/harness`
+  or any other mount point) without hardcoding it.
+
+  Gateway-rendered pages no longer emit root-absolute asset URLs: the embed chat
+  shell and MCP App share shell reference their bundles relative to the page, and
+  shared HTML gets a relative `<base href>` (plus a page-relative password-unlock
+  request). Client-side URL derivation now keeps the externally visible prefix
+  instead of reducing URLs to `location.origin`: the embed loader strips its known
+  `/embed/agent-chat-loader.js` suffix, the embed page recovers its base from
+  `<mount>/api/web-apps/:id/chat`, the MCP App share page keeps `<mount>/s/:token`,
+  and MCP App link resolution/sandbox loading use the gateway base derived from the
+  client `baseURL`. Root-path deployments resolve to the same absolute URLs as
+  before. Adds a deterministic `/harness` embed e2e (prefix-stripping proxy) and
+  random-prefix unit coverage.
+
+- Updated dependencies [9bbf5ce]
+  - @axiom-lattice/core@13.0.0
+  - @axiom-lattice/protocols@7.4.0
+
+## 5.2.1
+
+### Patch Changes
+
+- b928a17: Follow up the Wiz remediation with `pnpm audit`: bump the pinned transitive
+  dependencies to the advisories published after the scan (shell-quote 1.11 —
+  critical command injection — fastify 5.12.6, @fastify/busboy 3.2.2,
+  @hono/node-server 2.1.3, brace-expansion 1.1.21/2.1.7/5.0.12,
+  body-parser 1.20.9/2.4.0, decode-uri-component 0.5.1, fast-uri 3.1.9/4.2.3,
+  glob 10.5/11.1/14.0.4, langsmith 0.12, picomatch 2.3.2/4.0.4,
+  protobufjs 7.6.5/8.8.1, source-map-js 1.2.2, undici 7.30.1, sanitize-html
+  2.18.1, tar 7.5.22, tmp 0.2.7, vite 6.4.5, yaml 2.9.1, ajv 6.14/8.18,
+  mysql2 3.23.1, uuid 11.1, and others). Overrides are scoped per major line
+  where different majors are both required, and none pins below a declaring
+  package's range. Further zero-out pass: echarts 5.5 → 6.1 in react-sdk,
+  katex 0.19.1 (the patched range starts at 0.18.2), glob 14.0.4 for every
+  affected major line (10/11/13/14; glob 7 is outside the advisory range),
+  minimatch 11.0.8 for every vulnerable line, rimraf 4/5 → 6.1.4 (drops the
+  glob 9 dependency), ibm-cloud-sdk-core 5.9.4 (pulls file-type 21.3.4), and
+  fast-xml-parser 5.12.0. The client-sdk build moves from tsup 6.7 to 8.5,
+  clearing the last GHSA-3mv9-4h5g-vhg3 finding. Drop the unused `xlsx`
+  dependency from `apps/web`, which has no patched npm release.
+
+  Overrides only apply to this monorepo, so also raise the published packages'
+  own dependency ranges to patched versions, otherwise downstream consumers
+  (fina_demo) resolve the old lower bounds when they reinstall: fastify
+  ^5.12.6 (gateway, microsandbox-service, opensandbox-gateway), react-router
+  ^7.18.2, vite ^6.4.5, mysql2 ^3.23.1 (core), and uuid ^11.1.1 (core, gateway,
+  pg-stores, react-sdk, and the cli-a2a peer range).
+
+- Updated dependencies [b928a17]
+  - @axiom-lattice/core@12.3.1
+
 ## 5.2.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@axiom-lattice/pg-stores",
-  "version": "5.2.0",
+  "version": "5.2.2",
   "description": "PG stores implementation for Axiom Lattice framework",
   "main": "dist/index.js",
   "module": "dist/index.mjs",
@@ -24,15 +24,14 @@
     "@langchain/langgraph-checkpoint-postgres": "1.1.2",
     "@langchain/core": "1.3.2",
     "pg": "^8.16.3",
-    "uuid": "^9.0.1",
-    "@axiom-lattice/core": "12.3.0",
-    "@axiom-lattice/protocols": "7.3.0"
+    "uuid": "^11.1.1",
+    "@axiom-lattice/core": "13.0.0",
+    "@axiom-lattice/protocols": "7.4.0"
   },
   "devDependencies": {
     "@types/jest": "^29.5.14",
     "@types/node": "^20.11.24",
     "@types/pg": "^8.11.10",
-    "@types/uuid": "^9.0.8",
     "@typescript-eslint/eslint-plugin": "^7.2.0",
     "@typescript-eslint/parser": "^7.2.0",
     "eslint": "^8.57.0",

package/src/__tests__/PGVectorStore.delete-filter.integration.test.ts

@@ -0,0 +1,90 @@
+import { randomUUID } from "node:crypto";
+import { Pool } from "pg";
+import { PGVectorStore } from "@langchain/community/vectorstores/pgvector";
+import { Embeddings } from "@langchain/core/embeddings";
+import { Document } from "@langchain/core/documents";
+
+const databaseUrl = process.env.TEST_DATABASE_URL;
+const describeIfDatabase = databaseUrl ? describe : describe.skip;
+
+class FakeEmbeddings extends Embeddings {
+  constructor() {
+    super({});
+  }
+
+  async embedDocuments(texts: string[]): Promise<number[][]> {
+    return texts.map(() => [0.1, 0.2, 0.3]);
+  }
+
+  async embedQuery(): Promise<number[]> {
+    return [0.1, 0.2, 0.3];
+  }
+}
+
+describeIfDatabase("PGVectorStore collection delete filter", () => {
+  const tableName = `collection_delete_${randomUUID().replace(/-/g, "")}`;
+  let store: PGVectorStore | undefined;
+  let pool: Pool;
+  let available = false;
+
+  beforeAll(async () => {
+    pool = new Pool({ connectionString: databaseUrl });
+    try {
+      await pool.query("CREATE EXTENSION IF NOT EXISTS vector");
+      store = await PGVectorStore.initialize(new FakeEmbeddings(), {
+        postgresConnectionOptions: { connectionString: databaseUrl },
+        tableName,
+        columns: {
+          idColumnName: "id",
+          vectorColumnName: "vector",
+          contentColumnName: "content",
+          metadataColumnName: "metadata",
+        },
+        distanceStrategy: "cosine" as never,
+      });
+      available = true;
+    } catch (error) {
+      console.warn(
+        "PGVectorStore delete filter integration test skipped: pgvector is unavailable",
+        error instanceof Error ? error.message : String(error),
+      );
+    }
+  });
+
+  beforeEach(async () => {
+    if (!available || !store) return;
+    await store.delete({ filter: { marker: "seed" } });
+    await store.addDocuments([
+      new Document({ pageContent: "one", metadata: { _id: "1", marker: "seed" } }),
+      new Document({ pageContent: "two", metadata: { _id: "2", marker: "seed" } }),
+      new Document({ pageContent: "three", metadata: { _id: "3", marker: "seed" } }),
+    ]);
+  });
+
+  afterAll(async () => {
+    if (available) {
+      await pool.query(`DROP TABLE IF EXISTS "${tableName}"`);
+    }
+    if (store) await store.end();
+    await pool.end();
+  });
+
+  async function remainingIds(): Promise<string[]> {
+    const result = await pool.query<{ id: string }>(
+      `SELECT metadata->>'_id' AS id FROM "${tableName}" WHERE metadata->>'marker' = 'seed' ORDER BY id`,
+    );
+    return result.rows.map((row) => row.id);
+  }
+
+  it("deletes only the requested ids with the in operator", async () => {
+    if (!available || !store) return;
+    await store.delete({ filter: { _id: { in: ["1", "3"] } } });
+    await expect(remainingIds()).resolves.toEqual(["2"]);
+  });
+
+  it("leaves every row intact when the in batch matches nothing", async () => {
+    if (!available || !store) return;
+    await store.delete({ filter: { _id: { in: ["missing"] } } });
+    await expect(remainingIds()).resolves.toEqual(["1", "2", "3"]);
+  });
+});