agentpostlisted

# AgentPost AgentPost is the local post office for active CLI agents. The `agentpost` command and files under `~/.agentpost` are the durable truth; notifications are only pointers. ## Channel semantics Treat AgentPost as a communication channel, not merely an inbox utility. A user instruction such as "send it to PB", "tell Construct", "ask Kernos", or "share this with the reviewers" means: 1. Resolve the named destination through the AgentPost address book. 2. Infer the sender from the current process identity or project binding. 3. Turn "it" or "this" into a self-contained message using the relevant current context; do not make the recipient reconstruct missing details. 4. Deliver it now unless the identity or intended payload is genuinely ambiguous. 5. Report the Message-ID, concrete recipients, and whether each was notified live or queued offline. Do not stop at suggesting an AgentPost command when the user asked to send. Execute the delivery. Use `message` for information, work requests, specs, and reviews. Use `question` when an answer is expected. Routine mail defaults to idle notification; questions default to immediate, but the user's urgency or non-interruption request overrides the default. ```sh agentpost resolve 'Pattern Buffer' agentpost message 'Pattern Buffer' 'Please review the attached design context.' agentpost question reviewers 'Does this contract cover retry behavior?' ``` Both commands accept `-` or an omitted body to read a multi-line me