Mixed create workflows with a closing respond show the raw receipt of a new create beside the rendered 'already exists' line #952

What

When a workflow or agent turn makes several create_event calls and one of them returns alreadyExists while another creates a new event, a closing respond step still prints the raw receipt of the new create next to the rendered 'already in the calendar' line, so the answer mixes two wordings. Next action: store the ToolAnswer of every confirmed write (not only the alreadyExists one) and render the whole answer with renderToolAnswer. Found by the single-seat review of #942 and recorded as deferred in #929.

Why (motivation)

The intent path now renders alreadyExists as 'already in the calendar' (PR 942), but only for answers that carry it; a mixed closing respond still prints the raw receipt of the created event beside it, which reads as two different results for one request.

User impact

A user who asks for two events where one already exists sees an inconsistent answer and may not know whether the second event was created.

Cost of inaction

Mixed answers keep contradicting themselves; the user cannot tell from the text which event is new.

Acceptance criteria

• A synthetic workflow with two create_event steps where the first returns alreadyExists and the second creates is answered through renderToolAnswer: one wording for both, no raw receipt line
• A test through the real IntentExecutor covers the mixed case and fails before the fix

Screenshots

(none)

Deploy

Deployed: no

Links

• (none)