pi-model-fallback 0.5.1 → 0.5.2

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 ## Unreleased
 
+## [0.5.2] - 2026-10-07
+
+### Changed
+
+- Update `@earendil-works/pi-*` development dependencies to `1.0.4`.
+
+### Fixed
+
+- Recognize a status in parentheses when a provider error wrapper precedes it, for example `omni API error (503): ...`. Previously such messages yielded no status, so rules listing `503` were never evaluated even when configured.
+
 ## [0.5.1] - 2026-09-30
 
 ### Changed

package/README.md

@@ -123,7 +123,7 @@ If the package is installed project-locally and the current project references i
 
 - Successful responses do nothing.
 - Matching failures from `after_provider_response` can trigger fallback immediately.
-- Assistant error messages parsed at `turn_end` can also persist fallback state for SDK/provider failures that do not emit the normal response hook. Status extraction looks for HTTP-style tokens (for example `status 429`, `HTTP 503`, or `rate limit`) rather than any bare 3-digit number in the message.
+- Assistant error messages parsed at `turn_end` can also persist fallback state for SDK/provider failures that do not emit the normal response hook. Status extraction looks for HTTP-style tokens (for example `status 429`, `HTTP 503`, or `rate limit`) rather than any bare 3-digit number in the message. A status in parentheses is only recognized when an error wrapper keyword precedes it, as in `omni API error (503): ...`; a parenthesized number with no such wrapper, such as `(503) items processed`, stays unmatched.
 - With the default `autoRetry: true`, the failed prompt is automatically queued once per fallback transition on the fallback model. A fallback chain may therefore replay the prompt more than once. Set `autoRetry: false` to switch models without replaying it.
 
 Rules never fall back to the failing model itself; a rule whose fallback target equals the failing model is skipped so the next matching rule (or no rule) applies.

package/lib/error-status.ts

@@ -51,6 +51,13 @@ export function parseStatusFromErrorMessage(message: string): number | undefined
     // "429 tokens remaining in context window", which must stay unmatched.
     /^\s*error\s*:?\s*([1-5][0-9]{2})\b/i,
     /\b(?:status|code|http)\s*[:\s]?\s*([1-5][0-9]{2})\b/i,
+    // Parenthesized status inside a provider error wrapper, e.g.
+    // "omni API error (503): overloaded" or "chat_completion_error (429): ...".
+    // Without this the wrapper text sits between "error" and the number, so the
+    // anchored "error <status>" pattern cannot see it and the rule set never
+    // sees a status at all. The wrapper keyword and the parentheses are both
+    // required so prose such as "(503) items processed" stays unmatched.
+    /\b\w*(?:error|failure|failed)\s*\(\s*([1-5][0-9]{2})\s*\)/i,
     /\bHTTP\/\d(?:\.\d)?\s+([1-5][0-9]{2})\b/,
     /\b(?:rate[\s-]?limit(?:ed)?|too many requests)[^0-9]{0,40}([45][0-9]{2})\b/i,
     /\b([45][0-9]{2})\s+(?:error|quota|too many requests|service unavailable|bad gateway|gateway timeout|internal server error)\b/i,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-model-fallback",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "description": "Pi extension that switches to a fallback model after provider failures such as 429 rate limits.",
   "type": "module",
   "license": "MIT",
@@ -50,10 +50,10 @@
     "typebox": "*"
   },
   "devDependencies": {
-    "@earendil-works/pi-agent-core": "^0.99.1",
-    "@earendil-works/pi-ai": "^0.99.1",
-    "@earendil-works/pi-coding-agent": "^0.99.1",
-    "@earendil-works/pi-tui": "^0.99.1",
+    "@earendil-works/pi-agent-core": "^1.0.4",
+    "@earendil-works/pi-ai": "^1.0.4",
+    "@earendil-works/pi-coding-agent": "^1.0.4",
+    "@earendil-works/pi-tui": "^1.0.4",
     "@types/node": "^26.6.3",
     "jiti": "^2.7.0",
     "typebox": "latest",