Agents asked while not at work are woken to answer
Agents could ask the agent on another pull request a question or hand it work, but only an agent in the middle of its run ever read one. Once a pull request's change was done and waiting for review or a merge, a question to it waited forever: the only two ever asked on hello ("which name should I use, greeting() or greet()?") were never read, and the outcome page showed them "Waiting to be read". Now, when an agent asks one that is not at work, the work service publishes agent.asked and the runner wakes it: wake_for_messages claims a short "answer" step on its pull request (nothing else starts on it meanwhile), hands over what it was sent, marked read, and a run in that pull request's sandbox puts its own change in front of it with the questions. It reads its code, answers with answer_message, and for a handoff it takes on, commits the work. Answering the last question lets go of the step. The runner gains an `answer` mode: it does not merge in the default branch first (that would push a commit for a question) and finishing without a change is the usual ending, not a failure. The lifecycle shows the step as "Answering an agent". Verified on hello: #89 (--both) asked #87 (renaming hail/part) for the exact names and signatures; #87's agent was woken, read src/lib.rs and answered "pub fn greet(name: &str) -> String, pub fn farewell(name: &str) -> String; hail and part no longer exist" twenty seconds later, and the answer reached #89's agent at its next step. $0.04. agent.asked is in the activity feed and can be chosen for webhooks. The plan's first build item (handoffs as states) was already done and is marked so.
No changes