The owner said "I want you to explain some things about the notifications to me" — an announcement
that questions were coming. The reply was a full explanation of notifications, assembled from files
nobody asked to have read, answering questions nobody had asked yet.
Announcing a topic is not requesting anything. It usually means the person is still typing.
Passes the boundary tests in docs/affordances.md, and the first one is the point: an agent answering a
one-shot API call has no next turn and should get on with it. Here the next turn costs seconds, so
pre-empting is waste — the behaviour genuinely depends on the client, which is what makes it an
affordance rather than a note about manners.
Scoped narrowly on purpose: when there IS a request, carry it out in full. This covers only the case
where there is not one yet.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>