Best possible solution:

Land the narrow test-harness speedup after maintainer approval and green required CI, keeping production cron runtime behavior unchanged.

Do we have a high-confidence way to reproduce the issue?

Not applicable; this is a test-harness performance cleanup rather than a reported runtime bug. The review checked current main, the PR diff, and the PR body's before/after timing proof instead of a user-facing repro.

Is this the best way to solve the issue?

Yes; the patch targets the expensive test-only seams with a harness mock and per-suite fast-mode opt-in, which is narrower than changing production cron fallback or runtime behavior.

AGENTS.md: found and applied where relevant.

Codex review notes: model gpt-5.5, reasoning high; reviewed against e805ffd2eb75.

Label justifications:

• P3: This is a low-risk test-harness performance cleanup with no intended production runtime behavior change.
• rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster and patch quality is 🦞 diamond lobster.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): Sufficient: the PR body includes after-fix wrapper commands, before/after timings, broader test pass counts, and clean focused static checks for the test-harness speedup.
• proof: sufficient: Contributor real behavior proof is sufficient. Sufficient: the PR body includes after-fix wrapper commands, before/after timings, broader test pass counts, and clean focused static checks for the test-harness speedup.

PR surface:

Source +16, Tests +4. Total +20 across 4 files.

What I checked:

• Repository policy read: The full root AGENTS.md was read and applied; its review policy keeps maintainer/protected-label PRs in maintainer handling and treats test-performance changes as requiring scoped proof rather than auto-close cleanup. (AGENTS.md:18, e805ffd2eb75)
• Scoped agent test guide read: The relevant scoped guide says agent tests are often import-bound and asks performance edits to keep expensive runtime work behind dependency injection or narrow helpers, which matches the PR's test-harness mock direction. (src/agents/AGENTS.md:1, e805ffd2eb75)
• Current main lacks the new fast option: On current main, setupRunCronIsolatedAgentTurnSuite has no options parameter and always clears OPENCLAW_TEST_FAST, so the PR's opt-in fast-suite behavior is not already implemented. (src/cron/isolated-agent/run.suite-helpers.ts:11, e805ffd2eb75)
• Runtime alias boundary matches the mock: The cron executor resolves resolveCliRuntimeExecutionProvider immediately before deciding whether to run the CLI path, so mocking that dependency in the harness is targeted to the expensive behavior under test. (src/cron/isolated-agent/run-executor.ts:203, e805ffd2eb75)
• PR diff is test-only and narrow: The fetched PR diff changes only run.test-harness.ts, run.suite-helpers.ts, run.payload-fallbacks.test.ts, and run.fast-mode.test.ts; it adds the alias mock and fast-suite option without production runtime edits. (src/cron/isolated-agent/run.test-harness.ts:49, bb22882c06c6)
• Contributor proof is present: The PR body reports before/after hotspot timings, focused and broader Vitest wrapper runs, focused oxfmt/oxlint/tsgo, and autoreview results after the patch. (bb22882c06c6)

Likely related people:

• steipete: Local blame and the commits API show repeated recent ownership of the shared isolated cron harness, fast-mode tests, and payload fallback tests that this PR adjusts. (role: recent area contributor; confidence: high; commits: b1c30f0ba9b8, bb46b79d3c14, cd993f4584e7; files: src/cron/isolated-agent/run.suite-helpers.ts, src/cron/isolated-agent/run.test-harness.ts, src/cron/isolated-agent/run.fast-mode.test.ts)
• yinghaosang: The payload fallback test surface traces back to the merged payload.fallbacks feature commit, which is the behavior this PR keeps covered while speeding the test. (role: feature-history contributor; confidence: medium; commits: f902697bd5c4; files: src/cron/isolated-agent/run.payload-fallbacks.test.ts)
• vincentkoc: The test harness history shows adjacent cron runtime seam and lazy-load performance work in the same isolated cron area. (role: adjacent runtime-performance contributor; confidence: medium; commits: 35176f3cb730, a08fbfb1aea9, 101c16b0b133; files: src/cron/isolated-agent/run.test-harness.ts, src/cron/isolated-agent/run.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Share on X: post this hatch
Copy: My PR egg hatched a 🥚 common Clockwork Crabkin in ClawSweeper.
Hatchability:

• Merged PRs are hatchable.
• Open PRs are hatchable when they are status: 👀 ready for maintainer look, status: 🚀 automerge armed, or labeled clawsweeper:automerge.
• Closed unmerged PRs are hatchable only when one of those hatchable labels is still present in the durable record.

About:

• Eggs appear after real-behavior proof passes. They are collectible flavor only.
• Review momentum changes the shell state: follow-up work warms it, re-review makes it wobble, and a clean final review lets it hatch.
• The hatch is seeded from this repository and PR number, so the same PR keeps the same creature; the reviewed head SHA can only change safe visual details.
• Rarity is just collectible sparkle: 🥚 common, 🌱 uncommon, 💎 rare, ✨ glimmer, and 🌈 legendary.