CrewAI 1.15.22 traces human pauses: put the Sume dry run before them

Run a Sume dry_run before the CrewAI human pause, not after it. CrewAI 1.15.22, released September 16, 2026, collects human feedback and pause events in tracing, so the trace will show what the reviewer was asked. Make that the previewed cost, then submit with the same inputs and an idempotency_key.

The CrewAI line is from its GitHub release, read 2026-10-01. The release notes do not describe the trace format, so check yours. The Sume fields are from its MCP docs.

What did 1.15.22 add?

The release lists "Collect human feedback and pause events in tracing", alongside support for aliases as connection identifiers. Only the first affects an approval step.

What should the reviewer see?

Sume's tools and gates docs say dry_run previews a paid call without submitting it. Show that preview, plus the model and duration, at the pause. Generation admission is the page for what happens when a submit is accepted or refused.

What if the reviewer resumes twice?

Derive the idempotency_key from the task, not from the attempt. A repeated resume then sends the same key, so it does not buy a second render. Add max_spend_usd so the submit cannot exceed what was approved.