Why: LLMRunner should use runtime.Run instead of a second turn loop.
Evidence: go test ./... passed. Existing internal/runtime assertions were unchanged.
Depends on the Agent-Native PR. Merge before the Dev gitlink PR.
Refs: feature/agent-harness-p1
Why: LLMRunner should use runtime.Run instead of a second turn loop.
Evidence: go test ./... passed. Existing internal/runtime assertions were unchanged.
Depends on the Agent-Native PR. Merge before the Dev gitlink PR.
Refs: feature/agent-harness-p1
Why: deliverable checks, truncation continuation, and tool budgets should live in one loop instead of a second copy inside LLMRunner.
Evidence: go test ./... in backend passed. Existing runtime assertions were unchanged; new tests cover whole-batch tool-cap rejection with parts saved, and length continuation.
Impact: the direct path enables repeat guard and length continuation. Squad still uses the one-shot deliverable predicate and does not set the new kernel switches.
Refs: feature/agent-harness-p1
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
merged commit 9f648a4cd7 into main2026-10-01 13:41:41 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: LLMRunner should use runtime.Run instead of a second turn loop.
Evidence: go test ./... passed. Existing internal/runtime assertions were unchanged.
Depends on the Agent-Native PR. Merge before the Dev gitlink PR.
Refs: feature/agent-harness-p1