@jaypie/mcp 0.8.178 → 0.8.179

package/dist/assets.js

@@ -55,11 +55,11 @@ function getMcpAssetPaths() {
  */
 function getMcpBuildInfo() {
     return {
-        commit: "77e42bd7"
+        commit: "4e0d56bd"
             ,
-        version: "0.8.178"
+        version: "0.8.179"
             ,
-        versionString: "@jaypie/mcp@0.8.178#77e42bd7"
+        versionString: "@jaypie/mcp@0.8.179#4e0d56bd"
             ,
     };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jaypie/mcp",
-  "version": "0.8.178",
+  "version": "0.8.179",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/jaypie/1.2.115.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.115
+date: 2026-09-28
+summary: Pulls @jaypie/llm 1.3.56
+---
+
+## Changes
+
+- **`@jaypie/llm` 1.3.56**: failing over down a fallback chain logs at `debug` instead of `error` and `warn`; the report tally counts `failures` and `fallbacks`.

package/release-notes/llm/1.3.56.md

@@ -0,0 +1,26 @@
+---
+version: 1.3.56
+date: 2026-09-28
+summary: Failing over down a fallback chain logs at debug instead of error and warn, and the report tally counts failures and fallbacks
+---
+
+## Changes
+
+### Failover logging
+
+A timeout (or any failure) on a fail-fast attempt down a fallback chain logged `API call failed after 0 retries` at `error` and `Provider X failed` at `warn`, although the next model took over as designed.
+
+- `RetryExecutor` logs a zero-budget failure at `debug`: `API call timed out after 60000ms; not retrying` for a timeout, `API call failed; not retrying` or `API call rate limited; not retrying` otherwise. Exhausting a nonzero budget still logs `error`.
+- `runWithFallback` logs `Provider X failed; failing over` at `debug` when another model remains. Only the failure that reaches the caller (a lone model, or the linger pass) logs at `warn`. Both carry `kind` (`timeout` or the `LlmError` category).
+- A timeout that retries on the transient budget names its deadline in the retry `debug` line.
+
+### Report tally
+
+Inside a Jaypie handler, `operate()`, `ocr()`, and `question()` tally each failed provider attempt onto the `llm` report key:
+
+- `failures`: counts by `provider:model` and kind, e.g. `{ "openai:gpt-5.5": { "timeout": 1 } }`
+- `fallbacks`: counts each hand-off to another model, including the linger pass back to the primary
+
+## Testing
+
+- `npm run test -w packages/llm`: new `tallyFailure` and `runWithFallback` specs cover failure kinds, key resolution, the fallback count, and the debug/warn split; `RetryExecutor` specs cover the zero-budget debug lines for transient, rate-limit, and timeout failures

package/release-notes/mcp/0.8.179.md

@@ -0,0 +1,10 @@
+---
+version: 0.8.179
+date: 2026-09-28
+summary: Release notes for @jaypie/llm 1.3.56 and jaypie 1.2.115; llm skill documents failover logging and the failures/fallbacks tally
+---
+
+## Changes
+
+- **Release notes**: `@jaypie/llm` 1.3.56 and `jaypie` 1.2.115
+- **`llm` skill**: documents the `failures` and `fallbacks` report totals and the debug-level failover logging under Attempt Timeout

package/skills/llm.md

@@ -864,6 +864,7 @@ const response = await llm.operate(input, {
 - `stream()` treats `timeout` as an idle timeout: it restarts with every chunk and pauses while the consumer holds one. A stall after partial output yields an error chunk.
 - No default applies; unset means no deadline. Size it above the slowest legitimate non-streaming response (long reasoning runs take minutes).
 - `Llm.ocr` keeps `timeout` as the LlamaParse job deadline.
+- A timeout that hands off to the next model logs at `debug` (`API call timed out after 60000ms; not retrying`, then `Provider openai failed; failing over`). Only the failure that reaches the caller logs at `warn`. The report tally counts it under `failures` and `fallbacks`.
 
 ### Fallback Response Metadata
 
@@ -922,6 +923,8 @@ Inside a Jaypie handler (`expressHandler`, `lambdaHandler`, and stream variants)
 ```json
 {
   "llm": {
+    "failures": { "openai:gpt-5.5": { "timeout": 1 } },
+    "fallbacks": 1,
     "operates": 2,
     "toolCalls": 3,
     "tools": { "get_weather": 2, "roll": 1 },
@@ -941,6 +944,8 @@ Inside a Jaypie handler (`expressHandler`, `lambdaHandler`, and stream variants)
 - `operates` counts loop executions; repeated calls sum every number
 - `usage` is keyed `provider:model` — fallback providers appear as separate keys
 - `tools` appears only when tools were called
+- `failures` counts failed provider attempts by `provider:model` and kind (`timeout`, `rate_limit`, `retryable`, `quota`, `unrecoverable`, `unknown`), from `operate()`, `ocr()`, and `question()`
+- `fallbacks` counts hand-offs to another model, including the final retry of the primary once a chain is spent
 - Outside a handler session the tally is skipped entirely (guarded on `log.sessionActive`), so a CLI or script calling `operate()` directly emits nothing
 
 ## LLM Observability (Datadog)