11b1bfbc94
A request can carry several of this capability's returns — a model can call search twice in one response — and the carrier was identified by message alone, so each of them received the whole capsule. It is selected by message and part now, so exactly one carries it however many share the request. The chat TUI passed its persisted state into the run, so tool synchronisation mutated it in place while the message history was promoted only on success. A cancelled or failed run therefore kept the evidence the tools had recorded and discarded the messages that justified it, and the next question derived its identity from the shorter history: behind the recorded epoch, refused as non-append-only, the conversation unusable until cleared. The run gets a copy, promoted with the messages or not at all. Five decorators had been left attached to a helper by an earlier extraction, which pytest does not collect, so the resume case they carried was silently untested. The wire test covers both resume shapes again, no prompt and deferred results. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_chat_app.py | ||
| test_image_input.py | ||