From e033dd59a38d39a72f90b27f134f0553c258322e Mon Sep 17 00:00:00 2001
From: VibhorGautam <vibhorgautam907@gmail.com>
Date: Wed, 11 Mar 2026 12:26:25 +0530
Subject: [PATCH] fix the same rate_limit default in pi-embedded-runner probe
 gate

Two more sites in run.ts used "rate_limit" as the null-coalesce
default from resolveProfilesUnavailableReason. Update both to
"unknown" and add "unknown" to the transient cooldown probe
eligibility check so single-provider setups can still recover.
---
 src/agents/pi-embedded-runner/run.ts | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/src/agents/pi-embedded-runner/run.ts b/src/agents/pi-embedded-runner/run.ts
index 7f5f4f525b7..a28d74bf71e 100644
--- a/src/agents/pi-embedded-runner/run.ts
+++ b/src/agents/pi-embedded-runner/run.ts
@@ -553,7 +553,7 @@ export async function runEmbeddedPiAgent(
             resolveProfilesUnavailableReason({
               store: authStore,
               profileIds,
-            }) ?? "rate_limit"
+            }) ?? "unknown"
           );
         }
         const classified = classifyFailoverReason(params.message);
@@ -669,14 +669,15 @@ export async function runEmbeddedPiAgent(
           ? (resolveProfilesUnavailableReason({
               store: authStore,
               profileIds: autoProfileCandidates,
-            }) ?? "rate_limit")
+            }) ?? "unknown")
           : null;
         const allowTransientCooldownProbe =
           params.allowTransientCooldownProbe === true &&
           allAutoProfilesInCooldown &&
           (unavailableReason === "rate_limit" ||
             unavailableReason === "overloaded" ||
-            unavailableReason === "billing");
+            unavailableReason === "billing" ||
+            unavailableReason === "unknown");
         let didTransientCooldownProbe = false;
 
         while (profileIndex < profileCandidates.length) {