@llblab/pi-kit 0.8.0 → 0.8.1

package/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 All notable changes to `@llblab/pi-kit` are documented here.
 
+## 0.8.1 - 2026-09-11
+
+- `Telegram Schema Hotfix`: Advances the exact Telegram pin to `0.45.2`, whose bounded-depth `telegram_bind` argument schema is accepted by OpenAI and Gemini tool APIs again, restoring working agent requests while the bridge is connected. The package set, resource inventory, and explicit load order remain unchanged.
+
 ## 0.8.0 - 2026-09-11
 
 - `State Flow Resolution`: Advances the exact State Flow pin to `0.7.0`, bringing explicit PATCH/UNCHANGED resolution, bounded passive-stop continuation, runtime-owned artifact provenance, fixed hot history, local-first activation, asynchronous publication, and opt-in diagnostics while preserving the package set and resource order.

package/README.md

@@ -15,7 +15,7 @@ Package links lead to the owning repositories for usage, documentation, issues,
 | [`@llblab/pi-codex-usage`](https://github.com/llblab/pi-codex-usage) | `0.9.4` | Compact Codex/Spark subscription-limit status |
 | [`@llblab/pi-grow-loop`](https://github.com/llblab/pi-grow-loop) | `0.7.5` | Visible continuation scheduling and bounded worker Skills |
 | [`@llblab/pi-state-flow`](https://github.com/llblab/pi-state-flow) | `0.7.0` | Explicit scoped state resolution and bounded session continuation |
-| [`@llblab/pi-telegram`](https://github.com/llblab/pi-telegram) | `0.45.1` | Telegram companion, queues, files, voice, controls, and Generative Apps guidance |
+| [`@llblab/pi-telegram`](https://github.com/llblab/pi-telegram) | `0.45.2` | Telegram companion, queues, files, voice, controls, and Generative Apps guidance |
 | [`@llblab/skills`](https://github.com/llblab/skills) | `1.15.0` | Portable workflows for engineering, review, design, context maintenance, and other focused tasks |
 
 Versions are exact by design. An upstream release does not change an installed kit until this repository explicitly advances the dependency and publishes a new kit version. Runtime defects and package-specific feature requests belong in the linked repository; package selection and kit installation issues belong here.

package/node_modules/@llblab/pi-telegram/CHANGELOG.md

@@ -4,6 +4,10 @@
 
 ## Unreleased
 
+## 0.45.2: Provider-Compatible Bind Schema Hotfix
+
+- `Provider-Compatible Bind Argument`: Serializes the `telegram_bind` `argument` schema as an inline builder-made JSON-value union bounded to four container levels, with no `$ref`/`$defs` recursion or raw TypeBox marker leakage; OpenAI no longer rejects every request with "Recursive JSON schemas are not currently supported" (#273) and Gemini no longer rejects the unknown `~optional` field (#269) while the tool is registered.
+
 ## 0.45.1: Guest Mode And Channel Media Hotfixes
 
 - `Environment-backed bot tokens`: `telegram.json` profiles may store an exact `$NAME`/`${NAME}` reference instead of a copied token. Resolution happens only at validation/activation boundaries, including pairing identity hashing; setup prefills the first supported alias, validates the resolved value, and persists the alias; literals stay compatible; unresolved references fail closed with a redacted named-variable diagnostic in setup, connect, and status.

package/node_modules/@llblab/pi-telegram/docs/generative-apps.md

@@ -98,7 +98,7 @@ An absent, stale, or invalid bound app fails closed and never degrades into an a
 
 ## `telegram_bind` Tool
 
-One agent Tool owns installation and deliberate invocation through two mutually exclusive shapes. Its optional `argument` schema explicitly describes recursive JSON values (`null`, boolean, number, string, array, or object) rather than using an unconstrained subschema. Pi keeps the same JSON semantics, while schema aggregators cannot lower this field to a bare `true` schema that some llama-server grammars reject. The recursive definition lives in the tool root `$defs` and uses only local `#/$defs/TelegramBindJsonValue` references; it does not rely on named/remote reference resolution or newer TypeBox runtime helpers.
+One agent Tool owns installation and deliberate invocation through two mutually exclusive shapes. Its optional `argument` schema explicitly describes JSON values (`null`, boolean, number, string, array, or object) as a bounded union nested four container levels deep rather than using an unconstrained subschema. Pi keeps the same JSON semantics, while schema aggregators cannot lower this field to a bare `true` schema that some llama-server grammars reject. The union is built through standard schema builders and serialized inline with no `$ref`/`$defs` recursion, so provider tool APIs that reject recursive or reference-resolved schemas (OpenAI) accept it alongside providers strict about unknown schema fields (Gemini).
 
 Install an external self-contained module and initialize it:
 

package/node_modules/@llblab/pi-telegram/lib/generative-apps.ts

@@ -862,21 +862,23 @@ export function formatGenerativeAppToolError(error: unknown): Error {
   return new Error(`\n${message.replace(/^\n+/u, "") || "Generative App operation failed."}`);
 }
 
-const TELEGRAM_BIND_JSON_ARGUMENT_REFERENCE = "#/$defs/TelegramBindJsonValue";
-const TELEGRAM_BIND_JSON_ARGUMENT_SCHEMA = {
-  $ref: TELEGRAM_BIND_JSON_ARGUMENT_REFERENCE,
-} as unknown as ReturnType<typeof Type.Unknown>;
-const TELEGRAM_BIND_JSON_ARGUMENT_DEFINITION = {
-  anyOf: [
-    { type: "null" },
-    { type: "boolean" },
-    { type: "number" },
-    { type: "string" },
-    { type: "array", items: { $ref: TELEGRAM_BIND_JSON_ARGUMENT_REFERENCE } },
-    { type: "object", properties: {},
-      additionalProperties: { $ref: TELEGRAM_BIND_JSON_ARGUMENT_REFERENCE } },
-  ],
-};
+// Provider tool APIs reject recursive $ref schemas (OpenAI) and raw TypeBox
+// optional markers on non-builder objects (Gemini), while llama-server rejects
+// unconstrained subschemas; one bounded builder-made JSON-value union satisfies all.
+const TELEGRAM_BIND_JSON_ARGUMENT_MAX_DEPTH = 4;
+
+function createTelegramBindJsonArgumentSchema(
+  depth: number,
+): ReturnType<typeof Type.Union> {
+  const scalars = [Type.Null(), Type.Boolean(), Type.Number(), Type.String()];
+  if (depth <= 0) return Type.Union(scalars);
+  const nested = createTelegramBindJsonArgumentSchema(depth - 1);
+  return Type.Union([
+    ...scalars,
+    Type.Array(nested),
+    Type.Object({}, { additionalProperties: nested }),
+  ]);
+}
 
 export function registerTelegramBindTool(
   pi: ExtensionAPI,
@@ -893,10 +895,10 @@ export function registerTelegramBindTool(
       method: Type.Optional(Type.String()),
       replace: Type.Optional(Type.Boolean()),
       display: Type.Optional(Type.Boolean()),
-      argument: Type.Optional(TELEGRAM_BIND_JSON_ARGUMENT_SCHEMA),
-    }, { additionalProperties: false,
-      $defs: { TelegramBindJsonValue: TELEGRAM_BIND_JSON_ARGUMENT_DEFINITION },
-    }),
+      argument: Type.Optional(
+        createTelegramBindJsonArgumentSchema(TELEGRAM_BIND_JSON_ARGUMENT_MAX_DEPTH),
+      ),
+    }, { additionalProperties: false }),
     async execute(_toolCallId, params) {
       try {
         const result = await bindGenerativeApp({

package/node_modules/@llblab/pi-telegram/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llblab/pi-telegram",
-  "version": "0.45.1",
+  "version": "0.45.2",
   "private": false,
   "publishConfig": {
     "access": "public"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llblab/pi-kit",
-  "version": "0.8.0",
+  "version": "0.8.1",
   "private": false,
   "publishConfig": {
     "access": "public"
@@ -45,7 +45,7 @@
     "@llblab/pi-codex-usage": "0.9.4",
     "@llblab/pi-grow-loop": "0.7.5",
     "@llblab/pi-state-flow": "0.7.0",
-    "@llblab/pi-telegram": "0.45.1",
+    "@llblab/pi-telegram": "0.45.2",
     "@llblab/skills": "1.15.0"
   },
   "bundledDependencies": [