pullfrog 0.1.53 → 0.1.55

package/dist/utils/providerErrors.d.ts

@@ -1,5 +1,10 @@
 /** Stable label for the BYOK provider-billing-exhausted classification. */
 export declare const PROVIDER_BILLING_EXHAUSTED_LABEL = "provider billing exhausted";
+/** Stable label for "OpenRouter can route this model nowhere you permit". */
+export declare const PROVIDER_NO_ENDPOINTS_LABEL = "provider no routable endpoints";
+export declare function findAnthropicSpendCap(text: string): {
+    regainAt: string | null;
+} | null;
 /**
  * Result of a provider-error scan: the classification label plus a
  * human-readable excerpt centered on the matched line. The excerpt is what
@@ -22,6 +27,44 @@ export declare function isRouterKeylimitExhaustedError(text: string): boolean;
  * is the user's own provider account.
  */
 export declare function isProviderBillingExhausted(text: string): boolean;
+/**
+ * OpenRouter accepted the request and found nowhere to send it: the account's
+ * data policy or guardrail settings exclude every provider serving the picked
+ * model. Nothing is billed and no credential is at fault — the only fix is the
+ * privacy settings page or a different model. See #1164.
+ */
+export declare function isProviderNoRoutableEndpoints(text: string): boolean;
+/**
+ * OpenRouter's per-key ceiling, not an empty wallet. Topping up credits alone
+ * will not clear it, so it needs a different headline and a second lever than
+ * the generic billing-exhausted copy. Both shapes classify as
+ * `PROVIDER_BILLING_EXHAUSTED_LABEL`; this narrows within that class.
+ *
+ * TWO wire forms, and the obvious one is the rarer one. #1071's `Key limit
+ * exceeded (total limit)` names itself; #1164's is the `requires more credits,
+ * or fewer max_tokens` form, which is indistinguishable from a drained wallet
+ * except for the remedy the provider appends — a link to that key's own page.
+ * Anchor on the `/keys/<id>` URL rather than the "adjust the key's total limit"
+ * sentence, because the apostrophe in it arrives from provider JSON and may be
+ * typographic. A genuinely empty wallet (`Insufficient credits. Add more using
+ * …/settings/credits`) carries no `/keys/` path and correctly stays out.
+ */
+export declare function isOpenRouterKeyLimitExceeded(text: string): boolean;
+/**
+ * The upstream is having a moment: Anthropic's `API Error: 529 Overloaded`,
+ * OpenRouter's `provider_unavailable` / `timeout`, OpenCode Zen's `Streaming
+ * response failed: [5xx]`. Three transports, one condition — nothing the user
+ * configured is wrong and the next run will probably work, which is exactly
+ * what the contentless `Run failed.` comment failed to say across 28 runs that
+ * had already done up to 38 tool calls of real work (#1173).
+ *
+ * `error_type` is matched as the machine-readable FIELD it is rather than by
+ * substring-matching the human prose around it, which varies per upstream.
+ * Deliberately narrow on 5xx so it cannot reach a 401/402 that
+ * `isApiKeyAuthError` / `isProviderBillingExhausted` own — and `renderRunError`
+ * orders it after both regardless.
+ */
+export declare function isTransientUpstreamError(text: string): boolean;
 /**
  * Extract `providerID=foo` from agent error logs (OpenCode emits this on
  * `provider error detected (...)` lines). Returns the lowercase provider

package/dist/utils/proxy.d.ts

@@ -15,7 +15,7 @@
  * exist yet at this point in the pipeline.
  *
  *   - 402 → `BillingError` (card declined, balance empty, 3DS, etc.)
- *   - 503 → `TransientError` (transient sync issue — retry next dispatch)
+ *   - 5xx → `TransientError` (the mint is down — retried in-run first)
  *   - 404 → `TransientError` (stale repo↔account link — re-homes on next webhook)
  */
 import type { ToolState } from "../toolState.ts";

package/dist/utils/runContext.d.ts

@@ -76,6 +76,16 @@ export interface RunContext {
      * distinction a transient failure renders as "you have no API key".
      */
     secretsUnavailable?: boolean | undefined;
+    /**
+     * the Router was this account's funding path and its wallet is empty, so the
+     * server declined the mint rather than 402ing — the run falls through to
+     * BYOK, which is the documented affordance for a router-mode account whose
+     * key lives in workflow `env:`. only meaningful when the key search then
+     * comes up dry, where it turns "go add an API key" into copy that also names
+     * topping up. defaults false: an unreachable server must not assert a
+     * funding state. see wiki/billing.md.
+     */
+    routerUnfunded?: boolean | undefined;
 }
 /**
  * fetch run context from Pullfrog API

package/dist/utils/runContextData.d.ts

@@ -17,6 +17,9 @@ export interface RunContextData {
     /** stored secrets couldn't be materialized for this run — not the same as
      * the user having none. see `RunContext.secretsUnavailable`. */
     secretsUnavailable?: boolean | undefined;
+    /** the Router was declined because the wallet is empty. see
+     * `RunContext.routerUnfunded`. */
+    routerUnfunded?: boolean | undefined;
 }
 interface ResolveRunContextDataParams {
     octokit: OctokitWithPlugins;

package/dist/utils/runErrorRenderer.d.ts

@@ -35,6 +35,12 @@
  *      `maximum context length is N tokens`. Actionable, so it renders on
  *      both surfaces rather than collapsing to the one-line comment.
  *
+ *   4c. Transient upstream failure (#1173) — Anthropic `529 Overloaded`,
+ *      OpenRouter `provider_unavailable` / `timeout`, Zen `Streaming response
+ *      failed: [5xx]`. Last of the classified branches so every more specific
+ *      one wins first. Renders on both surfaces: the remedy is re-triggering,
+ *      which the user can only know if we say so.
+ *
  *   5. Activity-timeout hang — `errorMessage` starts with
  *      `"activity timeout"` or `"agent still pending"` AND none of the
  *      above matched. The harness keeps structured diagnostic state on
@@ -52,8 +58,8 @@
  *      the hang case, since the raw internal string helps nobody on the PR.
  *
  * Net: the actionable classifications (billing, API-key, model-not-found,
- * no-provider-available, context-overflow) render identical bodies on both
- * surfaces; the non-actionable ones (hang,
+ * no-provider-available, context-overflow, transient-upstream) render identical
+ * bodies on both surfaces; the non-actionable ones (hang,
  * generic) keep the forensics in the Actions job summary and show a calm
  * one-liner in the PR comment, whose footer already carries Pullfrog
  * branding + rerun links.

package/dist/utils/runStatusCheck.d.ts

@@ -35,11 +35,18 @@ export declare const RUN_STATUS_CHECK_NAME = "pullfrog";
 /** the review-verdict check. opt-in, terminal-only, and deliberately separate from the above. */
 export declare const APPROVAL_CHECK_NAME = "pullfrog-approval";
 /**
- * The terminal states we report. Exactly GitHub's check-run `conclusion` enum, which
- * happens to be `WorkflowRunStatus` minus `running` — so the server can map a finished
- * run's status straight across (`checkConclusionFromStatus` in utils/workflowRunStatus.ts).
+ * The terminal states we report: exactly GitHub's check-run `conclusion` enum.
+ *
+ * NOT `WorkflowRunStatus`. `stale` is a valid `workflow_run.conclusion` and is
+ * NOT a member of the Checks API enum, which GitHub's own 422 enumerates as
+ * `["success", "failure", "neutral", "cancelled", "timed_out",
+ * "action_required", "skipped"]`. Admitting it here let
+ * `checkConclusionFromStatus` type-check while producing a value the wire
+ * always rejects, so 100% of reaper-expired rows failed close-out — and since
+ * the failure left `checkRunId` set, the hourly sweep re-sent the same illegal
+ * conclusion forever. See [#1178](https://github.com/pullfrog/app/issues/1178).
  */
-export type RunStatusCheckConclusion = "success" | "failure" | "cancelled" | "timed_out" | "action_required" | "neutral" | "skipped" | "stale";
+export type RunStatusCheckConclusion = "success" | "failure" | "cancelled" | "timed_out" | "action_required" | "neutral" | "skipped";
 /**
  * Parse the on-the-wire `{ id: string }` shape (the form carried in `JsonPayload`) into
  * a check-run id. Mirrors `parseProgressComment` — returns undefined when the id isn't a
@@ -101,6 +108,9 @@ export interface RunStatusCheckOctokit {
                 data: {
                     check_runs: {
                         id: number;
+                        app?: {
+                            slug?: string | null;
+                        } | null;
                     }[];
                 };
             }>;