The security-reviewer agent ran for over three and a half hours on the ahoy branch with no report, while a fresh copy of the same review given an explicit budget of about twenty-five tool calls reported in eight minutes and found the same class. Review prompts should carry a budget and a report-what-you-have instruction, and the orchestrator should time-box a review rather than wait; the run's BRIEF for lane agents already says validation runs in the foreground because a backgrounded gate never wakes the agent that started it, and the same harness shape applies here.

The security-reviewer agent ran for over three and a half hours on the ahoy branch with no report, while a fresh copy of the same review given an explicit budget of about twenty-five tool calls reported in eight minutes and found the same class. Review prompts should carry a budget and a report-what-you-have instruction, and the orchestrator should time-box a review rather than wait; the run's BRIEF for lane agents already says validation runs in the foreground because a backgrounded gate never wakes the agent that started it, and the same harness shape applies here.

Grounds

• pursued: a budgeted review reports within its budget instead of running for hours; a dispatched security review that again runs past its budget with no report would show it wrong