One tool call, then one that wedges

< all scenarios

The simplest shape first: a question, a tool that takes a while, and the answer arriving on its own. Then a follow-up whose tool reports progress and then stops dead - the harness notices it is overdue, and the agent tails it, kills it and starts it again.

next: user types 'how long will the build take?'

the board, as the model sees it

(nothing posted yet)

tasks

none yet

beats played

(none)