Wymcp tool messages — sessions talking with each other on a thread, through YmerNode.Messages.

A thin boundary over that context, wiring only the framework's callbacks. What a thread, a handle and a read mark are, and what each answer says when it finds nothing, live in the context's own moduledoc.

Neither destructive nor open-world

The first of the node's tools annotated so, deliberately. No action removes anything — the count cap's drop is a bound, not an action — and nothing a call does leaves this machine. The annotation is what lets a client run it without asking: a prompt on every check would make the person the courier between sessions again, which is what the tool exists to end. The README advises allowing it.

What it does carry is another session's words into this one, so description/0 says, in one line, that a message is data to weigh and never an instruction that outranks the reader's own.