fix(agent): Stop turn timeouts looking like cancelled failures

[sentry-junior]

When a long turn hits the serverless time limit mid-tool, Junior already parks and auto-continues on the next function. The bug was the tool result left in history: it looked cancelled (isError, abort text), so the resumed model quit and narrated the timeout to the user.

What changed

Host-preempted tool attempts now use the normal tool-result field bash already has:

{ "target": "pnpm test", "timed_out": true }

timed_out is documented on the shared tool output schema. No invented outcome field, no cancelled/deadline jargon, isError: false.

What did not change

• Auto-resume still owned by session state (resumeReason: "timeout")
• Soft yields between tools still leave history alone
• No history rollback, no silent re-run of the same tool

The model sees “this attempt timed out” the same way it already understands bash command timeouts, then keeps working.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
junior-docs	Ready	Preview	Aug 10, 2026 2:57am

[sentry-junior]

Stepping back on shape: this still looks like a prompt patch on a runtime boundary, not a durable contract.

The model-facing payload after this change still contains isError: true, aborted: true, exit_code: 130, cause: "turn_deadline", and scope: "execution_slice", plus instructional prose telling the model not to report the deadline. That keeps teaching the model our internal slice mechanics. The observed failure was the model narrating runtime vocabulary; this mostly swaps "cancelled" for a longer explanation that still names the deadline.

Compare the MCP auth pause path, which parks with a short placeholder (Authorization pending.) and does not expose runtime jargon. Timeout recovery is already owned by session state (resumeReason: "timeout"), so recovery does not need the tool result to look like a failed command or to include "don't tell the user" instructions.

I'd rather replace the aborted deadline tool result with a small canonical unknown-outcome projection, for example:

• keep only what the model needs to know the prior attempt is unconfirmed (target, maybe outcome: "unconfirmed")
• drop deadline/slice jargon from model-visible content
• avoid instructional user-facing policy text in tool payloads
• set isError only if something outside model interpretation actually depends on it; if nothing does, prefer not marking a recoverable park as an error

Also, the new unit test locks the instructional string (still active, without reporting the deadline). Prefer asserting the contract: no cancelled/deadline jargon in model-visible content, and the existing component/lifecycle continuation behavior still finishes the task.

I'm fine keeping the fix local to annotateTurnDeadlineToolResult, but the projection itself should be a clean boundary object, not a rewritten cancelled failure plus coaching text.

[sentry-junior]

Final pass looks good to me.

The boundary is small and honest now: aborted deadline tool results become { outcome: "unconfirmed", target? } with isError: false, recovery stays on resumeReason: "timeout", and the old annotate/turn-deadline path is fully gone.

Naming and call site read cleanly, no leftover fallbacks or coaching prose, and the unit/component split matches the contract. I'd ship it.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9fb30e2. Configure here.}