[sentry-junior]

Integration evals on PRs off main with both #2514 and #2504 failed four cases. Each failure has a root cause in a tool contract, a turn input, or the eval fixture. None is a runtime double post.

Attachments: "when the vision model cannot read an image" (0.50 in 4 of 4 runs on main; at the 0.75 floor in 9 of 13 earlier runs)
The turn input said only that the image "could not be analyzed". viewImage said "unsupported image format; use PNG, JPEG, GIF, or WebP" for a .png with bad bytes. The agent then told the user that the attachment "didn't come through" and asked for a re-upload, as if no file arrived. Both messages now say that the file arrived but could not be read as an image. The case now scores 1.0.

Slack Thread Status and Title, both cases ("expected 2 to have a length of 1")
This is not a double post and not a second title. The failing assertion is replies (lines 27 and 42). Since #2514, a how-to answer is about 2,200–2,400 characters, which is over the 2,200-character Slack inline budget. Delivery splits it into two posts. #2514's own branch failed this way at 08f9f6a. The fixture counted each post as a reply, and the judge saw the answer three times.

The fixture (slackCallReplies in src/fixture/results.ts) now treats the consecutive posts that make up one stored reply as one reply. A repeated post is still a second reply. The comparison removes the continuation marker and drops code fence lines. A split inside a code block closes the block in one post and reopens it, with its language tag, in the next. Dropping the fence lines also keeps a cut between two real code blocks matching. The fix is fixture-only, and Slack output code does not change. I checked it against the real split posts of the failing runs. Unit tests cover a plain split, a split inside a ```ts block, a cut between two code blocks, and a repeated post.

Schedule Creation: "simple one-off reminder" (Guardian ask, then the agent asked to confirm)
The createAutomation description said that the automation "delivers to the channel or DM of this conversation". Guardian believed it over the task_creator outcome and returned unclear_destination. The new Guardian snapshot reproduces this on the old description (run 41374373955: "schedules a reminder in the active public Slack channel") and allows on the new one (run 41374880826). The description now says that the automation belongs to the conversation and that its outcomes set where its messages go. A later cleanup removes the sentences that other surfaces already own. The <tool-policy> block owns creator credentials and subscribable tool results. The trigger identifier field and searchEventTypes own namespace-wide event reach. The cleanup also removes the provider example from core. The first invalid call (timezone beside schedule) is a model nesting slip that 8 earlier passing runs also had. The strict schema catches it, and the retry recovers.

Scheduled Delivery: the creator mention (run 41382009284 on 60f4efe, all 3 attempts)
createAutomation is in the tool list of every automation run. A change to its description stops the stored recordings from matching, so these cases run live. Live, a reminder for its creator often posted without the mention: "Reminder: The Automation creator, please do healthchecks.", "Reminder: Do your healthchecks.", and "Reminder: Do healthchecks.". Such a reminder posts to the channel without pinging its creator.

requireInstructionReferences makes a stored instruction call the creator "the Automation creator". renderTaskInput passed that text through, and only the Created by: line told the run to write the mention instead. renderTaskInput now writes the creator mention in place of "the Automation creator" (any case, whole words). Scheduled and event automations pass a creator. Watches do not, so their input does not change. The Created by: line stays, because it still covers "me" and "my". heartbeat-scheduled-automations.test.ts now checks that a stored "the Automation creator" reaches the run as the mention in the Instructions: line. The test fails without the fix.

All three failures were on "when a due reminder says me, mention its creator". Its legacy instruction says "me", not "the Automation creator", so this fix does not reach it. That case stays model choice. #2519, stacked on this PR, moves it to the behavioral suite. This PR does not move it.

CI: pending on a35f17f.

Part of #2488

via @dcramer.

--

View Session [Sentry]

[vercel]

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

Project	Deployment	Actions	Updated
junior-docs	Ready	Preview	Nov 2, 2026 4:59pm UTC

[dcramer]

fix the pr title/description

[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 4184e7f. Configure here.}