fix(queue): restore #3998's intended repair-attempt cap bump to 5 by JSONbored · Pull Request #4030 · JSONbored/loopover

JSONbored · 2026-07-07T11:08:38Z

Summary

fix(queue): repair malformed regate-repair diff breaking main typecheck #4023 fixed the syntax corruption fix(queue): prevent regate repair exhaustion from premature attempt counting #3998's own patch introduced and correctly moved repair_attempt recording to execution time, but left REGATE_REPAIR_MAX_ATTEMPTS_PER_SHA at 2 — fix(queue): prevent regate repair exhaustion from premature attempt counting #3998's own stated intent (point 3 of its PR description) was to raise it to 5, for resilience against transient failures (e.g. a single AI-provider timeout no longer exhausts the whole repair budget).
Bumps the constant and updates both #orb-retry-storm regression tests' hardcoded attempt counts to match the new cap.
One of those two tests was also still asserting the pre-fix(queue): prevent regate repair exhaustion from premature attempt counting #3998 dispatch-time recording behavior (never executing the fanned per-PR job before checking the attempt count) — same gap fix(queue): repair malformed regate-repair diff breaking main typecheck #4023 left in place. Fixed by actually running the fanned job before asserting.

Supersedes #4027 (same underlying gap, but that branch's diff conflicts with #4023 which already landed the syntax fix independently).

Scope

2 files: the one-line constant + the two dependent test updates.

Validation

npx tsc --noEmit — clean.
npx vitest run test/unit/queue.test.ts — full file green (both #orb-retry-storm tests pass).
Full unsharded npm run test:coverage — clean, changed line confirmed hit.

Safety

No secrets/wallets/hotkeys/trust-scores/reward-values touched.
No changelog edit; no site//CNAME/lovable changes.

#4023 fixed the syntax corruption #3998's own patch introduced and moved repair_attempt recording to execution time, but left REGATE_REPAIR_MAX_ATTEMPTS_PER_SHA at 2 -- #3998's stated intent was to raise it to 5 for resilience against transient failures (a single AI provider timeout no longer exhausts the budget). Bumps the constant and updates both orb-retry-storm regression tests' attempt counts to match; one of them was also still asserting the pre-#3998 dispatch-time recording behavior, never executing the fanned per-PR job.

superagent-security · 2026-07-07T11:09:02Z

Superagent didn't find any vulnerabilities or security issues in this PR.

codecov · 2026-07-07T11:15:49Z

❌ 51 Tests Failed:

Tests completed	Failed	Passed	Skipped
10417	51	10366	7

View the top 3 failed test(s) by shortest run time

test/unit/mcp-server-telemetry.test.ts > MCP server telemetry > records session-scoped MCP request errors without a tool name

Stack Traces | 0.0379s run time

Error: Failed to resolve entry for package "@jsonbored/gittensory-engine". The package may have incorrect main/module/exports specified in its package.json.
 ❯ .../gittensory-miner/lib/opportunity-fanout.js:2:1
 ❯ src/mcp/find-opportunities.ts:11:1

test/unit/mcp-server-telemetry.test.ts > MCP server telemetry > falls back when Hono does not expose an execution context

Stack Traces | 0.0554s run time

Error: Failed to resolve entry for package "@jsonbored/gittensory-engine". The package may have incorrect main/module/exports specified in its package.json.
 ❯ .../gittensory-miner/lib/opportunity-fanout.js:2:1
 ❯ src/mcp/find-opportunities.ts:11:1

test/unit/mcp-server-telemetry.test.ts > MCP server telemetry > records sanitized error telemetry when the MCP transport handler throws

Stack Traces | 0.193s run time

Error: Failed to resolve entry for package "@jsonbored/gittensory-engine". The package may have incorrect main/module/exports specified in its package.json.
 ❯ .../gittensory-miner/lib/opportunity-fanout.js:2:1
 ❯ src/mcp/find-opportunities.ts:11:1

View the full list of 48 ❄️ flaky test(s)

test/integration/api.test.ts > test/integration/api.test.ts