failproofai 1.0.12 → 1.0.13-beta.1

package/.next/standalone/SECURITY.md

@@ -56,8 +56,9 @@ The gate above scans the lockfiles it is *given* (the `--lockfile` list in the
 workflow). GitHub's dependency graph reads **every** lockfile in the repository, so
 Dependabot alerts cover trees the gate does not — in particular the TypeScript SDK's
 integration fixtures, `sdk/typescript/integration/fixtures/*/package-lock.json`.
-Those are not in the scanner's list and are not a Dependabot *update* ecosystem in
-[`.github/dependabot.yml`](.github/dependabot.yml) either, so an alert is the only
+Those are not in the scanner's list and get no Dependabot *version* updates either
+(the four floor fixtures have entries in [`.github/dependabot.yml`](.github/dependabot.yml),
+but only to restrain its security updates; see below), so an alert is the only
 thing that will ever mention them. Treat the alert list as authoritative for those
 paths, and see *Triaging a Dependabot alert in an integration fixture* below for how
 to resolve one.
@@ -118,17 +119,32 @@ That splits an alert in one of these lockfiles into two cases:
    the scanner does not read these lockfiles, so an `[[IgnoredVulns]]` entry for one
    would filter nothing and be reported as an unused ignore.
 
+Dependabot's own security updates know neither case. Given a case-2 advisory they
+reach the fix by moving the framework, which is how #838, #931 and #935 happened
+(#935 opened three minutes after #934 put the pins back). So each floor fixture —
+`ai-4`, `langchain-0.3`, `llamaindex-0.11`, `mastra-0` — has a security-updates-only
+entry in [`.github/dependabot.yml`](.github/dependabot.yml)
+(`open-pull-requests-limit: 0`) whose `ignore` ranges hold its framework on its
+line, and zod on 3 where that framework requires it; a fix that stays on the line
+still arrives. A new floor fixture needs its own entry, and
+`__tests__/ci/ts-sdk-fixture-pins.test.ts` fails without one. A Dependabot PR that
+moves a pin anyway fails that same test: close it rather than merge it.
+
 ### Accepted, with no fix available
 
 | Advisory | Package | Fixtures | Why it stays |
 |---|---|---|---|
 | [GHSA-rwvc-j5jr-mgvh](https://github.com/advisories/GHSA-rwvc-j5jr-mgvh) (low, CVSS 3.7) | `ai@4.3.19` | `ai-4`, `mastra-0` | A filetype-whitelist bypass on **file upload**. Fixed in `ai@5.0.52` — the major the `ai-4` fixture exists to stay below, and one `@mastra/core@0.24.9` cannot take either (it requires `ai@^4`). Neither fixture uploads a file or exposes an upload surface; each runs one scripted agent against an in-process model. |
 | [GHSA-866g-f22w-33x8](https://github.com/advisories/GHSA-866g-f22w-33x8) (low, CVSS 4.3) | `@ai-sdk/provider-utils@2.2.8` | `ai-4`, `mastra-0` | Unbounded response-body reads in `createJsonResponseHandler` and its siblings. Fixed in `3.0.28`; `2.2.8` ships *inside* `ai@4.3.19`, which uses the v2 API, so the fix is the same blocked major as the row above. Exploiting it needs a hostile **model-provider HTTP response**; these fixtures never call one. |
+| [GHSA-mrhx-c7xc-m3w5](https://github.com/advisories/GHSA-mrhx-c7xc-m3w5) (high, CVSS 7.5) | `zod@3.25.76` | `ai-4`, `langchain-0.3`, `llamaindex-0.11`; nested in `langchain-dup-core` and `mastra-0` | An array schema keeps every failing element's validation issues, uncapped, so one oversized input can exhaust memory. Fixed only in `4.6.6`: no zod 3 release carries the fix, and `3.25.76` is the newest. Each copy is held to `^3` by the release its fixture pins — `ai@4.3.19` and its `@ai-sdk/*` packages peer on `^3.23.8`, `@langchain/core@0.3.80` (in `langchain-dup-core`, the vendored provider's own copy) and `@langchain/langgraph@0.4.10` depend on `^3.25.32`, `@llamaindex/core@0.6.8` and `@llamaindex/workflow@1.1.5` need `^3.23.8`, and in `mastra-0`, `zod-from-json-schema-v3` (`zod-from-json-schema@0.0.5`, which builds zod 3 schemas for `@mastra/core` and `@mastra/mcp`) depends on `^3.24.2`. Exploiting it needs untrusted input validated against one of those schemas; each fixture validates only its own scripted tool arguments. |
 
-Both rows are bounded by the same facts: these are test fixtures — `"private": true`,
+Every row is bounded by the same facts: these are test fixtures — `"private": true`,
 never published, installed with `--ignore-scripts`, and run only in CI against
 scripted in-process models. Re-check them whenever the supported framework floor
-moves; dropping `ai` 4.x from the matrix is what actually retires them.
+moves. The first two rows retire once `ai` 4.x has left the matrix, which takes
+`mastra-0` as well as `ai-4`, because `@mastra/core@0.24.9` requires `ai@^4`. The
+zod row retires only once `ai` 4.x, LangChain 0.3, LlamaIndex 0.11 and Mastra 0.x
+have all left it.
 
 ## Maintainer setup (one-time)
 

package/.next/standalone/fp-cloud-cli/CHANGELOG.md

@@ -1,6 +1,20 @@
 # Changelog — `fp` CLI
 
-## 0.0.2b0 — 2026-09-22
+## 0.0.3b0 — 2026-10-25
+
+Open for the next release. `0.0.2` published on 2026-10-25 and the `bump` job
+moved the version here automatically; nothing has landed against `0.0.3b0` yet.
+Add entries as changes merge — this section becomes the GitHub Release body when
+it ships.
+
+## 0.0.2 — 2026-10-25
+
+**Stable release.** The `0.0.2b0` line the `bump` job opened after `0.0.1` is cut stable
+here rather than published, because the server endpoints these commands drive are now
+deployed to FailproofAI Cloud and the CLI should not trail them as a pre-release.
+
+Nothing about the command surface changes at the cut: the entries below are the entire
+diff from `0.0.1`, and the `bump` job opens `0.0.3b0` after the upload.
 
 ### Added
 

package/.next/standalone/fp-cloud-cli/fp_cli/_version.py

@@ -1 +1 @@
-__version__ = "0.0.2b0"
+__version__ = "0.0.3b0"

package/.next/standalone/fp-cloud-cli/uv.lock

@@ -1,5 +1,5 @@
 version = 1
-revision = 3
+revision = 5
 requires-python = ">=3.10"
 
 [[package]]
@@ -372,7 +372,7 @@ wheels = [
 
 [[package]]
 name = "posthog"
-version = "7.71.0"
+version = "7.75.11"
 source = { registry = "https://pypi.org/simple" }
 dependencies = [
     { name = "backoff" },
@@ -380,9 +380,9 @@ dependencies = [
     { name = "requests" },
     { name = "typing-extensions" },
 ]
-sdist = { url = "https://files.pythonhosted.org/packages/c6/9b/12e2e82fbbf5d70f554cfd1930631a6d1cce8975721ad50b5d7b47e580ff/posthog-7.71.0.tar.gz", hash = "sha256:00950999edf7f613a90015126bacc431d3ab3964a70d91c2f792e6a0dc81f358", size = 763019, upload-time = "2026-10-16T19:24:33.765Z" }
+sdist = { url = "https://files.pythonhosted.org/packages/20/ee/6c0ad2557d82a626dbd14453fada5b93c4c78a9e696f4e74b5672facd29a/posthog-7.75.11.tar.gz", hash = "sha256:c55e8de3943cc9cd86a8eda893f5ea1b9d631f52a2758dd14c0c17ef52632908", size = 819642, upload-time = "2026-10-23T15:26:56.068Z" }
 wheels = [
-    { url = "https://files.pythonhosted.org/packages/f5/8e/9b185e665800a922e95fb965fb9c17d2a54cee575cf5e425308250663393/posthog-7.71.0-py3-none-any.whl", hash = "sha256:52cb1320b7e178b36ef7594cf15b4a8c492c24d4d1c46700f5bee0089ba5c6ac", size = 892234, upload-time = "2026-10-16T19:24:31.706Z" },
+    { url = "https://files.pythonhosted.org/packages/50/8c/7765ea5122fe96daf9d3db4653fc37f2ca5115e2f6f7f4d74f0867433a8a/posthog-7.75.11-py3-none-any.whl", hash = "sha256:c65d173b24ec82cbf0f977f4779348512a7f71b761809786e87ae47e347ebab1", size = 958056, upload-time = "2026-10-23T15:26:54.116Z" },
 ]
 
 [[package]]

package/.next/standalone/hermes-plugin/plugin.yaml

@@ -1,5 +1,5 @@
 name: failproofai
-version: 1.0.12
+version: 1.0.13-beta.1
 description: Real-time FailproofAI policy enforcement for Hermes
 manifest_version: 2
 api_version: 1

package/.next/standalone/node_modules/@next/env/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@next/env",
-  "version": "16.4.2",
+  "version": "16.4.3",
   "keywords": [
     "react",
     "next",

package/.next/standalone/node_modules/next/dist/build/swc/index.js

@@ -130,7 +130,7 @@ function _interop_require_wildcard(obj, nodeInterop) {
     }
     return newObj;
 }
-const nextVersion = "16.4.2";
+const nextVersion = "16.4.3";
 const ArchName = (0, _os.arch)();
 const PlatformName = (0, _os.platform)();
 function infoLog(...args) {