fix(runner): keep recovery state read bounds consistent

Use the control-plane bound during initial recovery, revalidation, and cleanup snapshots. A retained state above 16 MiB reproduces the prior rejection; 32 focused recovery and authority checks now pass.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
DottaandPaperclip committed 2026-09-24 16:06:08 -07:00
1 parent c9618fcf16
commit 6262173bf5
2 files changed
+21 -9

No files matched your search

@@ -9100,6 +9100,7 @@ describe("runnerd provider runtime wiring", () => {
it.each([
"quarantined",
"large control plane",
"empty retry shell",
"unsuspended current",
"live runner",
@@ -9298,6 +9299,12 @@ describe("runnerd provider runtime wiring", () => {
},
],
committedEvents: [
...(scenario === "large control plane"
? Array.from({ length: 2048 }, () => ({
eventType: "item.delta",
envelope: { ...identity, payload: { delta: "x".repeat(8192) } },
}))
: []),
{ eventType: "run.terminal", envelope: identity },
],
}),
@@ -9337,6 +9344,7 @@ describe("runnerd provider runtime wiring", () => {
state.createTransport.mockClear();
const shouldRecover = [
"quarantined",
"large control plane",
"empty retry shell",
"unsuspended current",
"active goal",