[adiled]

Why

wryme delivers a finished background job, or another window's note, as a made-up tool call and its result at the end of a request, with no new user words. Through hum to any claude-* model this failed with 400 cannot-grow-on, because the claude-cli nurse refused every prompt with no words. Separately, every request from wryme started a new sigil, so each turn spun up a new claude session and re-stitched the whole history.

Two expectations hold after this PR:

1. A client that runs its own tools has its conversation grafted as it was, by every nurse, whatever shape it comes back in.
2. A tool the server runs, a nurse's own or an attendant's, reaches the client the same way through chat completions and the Responses API.

What changes

claude-cli grows on from tool results (hives/claude-cli)

• grows_on() is now true. A prompt with no words whose graft ends in tool results (graft::ends_in_grasps) keeps those results as the stitched transcript's last entries, and the cell sends stream::CONTINUE as the user message, since claude only takes a turn from one.
• When claude --resume loads a transcript that ends in tool results, it first writes its own empty reply, "No response requested.". The continue line tells the model that reply was added by the session, not by it.
• Anything else with no words (assistant words to continue, plain-text completion, a scion) is refused with cannot-grow-on, so /v1/completions and prefill still get a 400.
• graft() stitches on the tool results a held transcript lacks, matched by the tool and its answer, not counted. A transcript can hold answers the client never saw (a tool the server ran, a call the nest gave up on), and counting let those hide a delivery. Ids can't be used: claude names its calls by its own ids, the client by the nest's.

A conversation keeps its sigil (hives/openai-server)

• The trace reads a turn's words, calls and answers each in order but apart, words whitespace aside, so a turn sent back as one message matches the turn grown in steps.
• A conversation that ends in tool answers also finds the sigil it had before them. A delivery, or an answer that came after its call was let go, now grows on in the same claude session instead of starting a new one.
• A tool the server ran is left out of the trace, so a client finds its sigil whether it sends that call back or not.

Every nurse grafts a delivery

• openai-server's own nurse added nothing when a delivery kept the bloom count the same; answers added to the last bloom now join its kept conversation by call id.
• ollama refused any conversation ending in tool answers; it now grows on from them through /api/chat.
• openai-server held a caller's call 30 minutes while the nest gives up after 10½, so an answer in between went to a call no one waited on. The hold is now 10 minutes, and a later answer grows on from the graft.

A tool the server ran passes through both APIs

• Chat completions now carries it on the message as mcp_calls, each shaped as the Responses API's mcp_call item, streamed as a delta like tool_calls, and reads it back when the client sends the message back.
• Both APIs remember it, in the order it grew, so a previous_response_id graft holds it.

Code is speech: the doc comments the first commit added are gone, answered is ends_in_grasps, and headers say only what the code can't.

Testing

• claude-cli: all pass, with new tests for a delivery in a turn where the server ran a tool, and an answer that came after the nest gave up.
• ollama-server: all pass, with new tests for growing on from tool answers through /api/chat.
• openai-server: 59 unit and e2e tests pass against a real humd: mcp_calls whole and streamed and read back; the trace with and without served calls; a delivery finding its sigil; late answers in the nurse.
• Live (HUM_LIVE_CLAUDE=1, claude-haiku-4-5): 18/18 pass, including a delivery in a turn where the server ran lookup, which stays on its sigil, stitches the late result (graft.late-results) and is answered.

Not done

• ollama never sends the prompt's tools to Ollama, so it can answer a delivered result but not call tools itself.
• anthropic-server was not checked for the same pass-through.