Reads the room, answers where it was asked

• It can read the surface it's already on. Which channels am I in, who else is in this one, who is this id, what was said — four reads answered by the surface itself rather than by agent.yaml, so a channel it was never invited to shows up as the reason nobody is talking to it.
• A post can wake one person or coworker. post_message takes a mention and each surface renders it as its own addressing primitive — a p tag on Buzz, <@id> on Slack — so a cross-post reaches somebody instead of only informing a room.
• The answer comes home to where the question was asked. For an hour after an addressed post, that principal's replies are brought back into the asking thread verbatim, so a person in Slack can put a question to a coworker on Buzz and read the answer where they asked it.
• A long job replies in the thread it started from. A run that outlasts the turn now answers the message that asked for it, instead of leaving its verdict in the job's report channel for somebody to go and find.
• A 3am tick can read the coworker's checkouts. The chart's new persistence.jobCheckouts mounts the coworker's repository clones into its CronJob Pods, so a scheduled body starts on warm code rather than on a clone it cannot afford inside its budget.
• Team memory says when it's broken. A rejected SageOx credential now names itself at launch and tells the turn not to answer as if team memory had worked, rather than sending every question to the model alone in silence — and a rotated token is picked up without a restart.

The Helm chart moves to 0.11.0, and the cap that stops two coworkers answering each other now holds on Buzz as it does on Slack. Three things need acting on when upgrading from 0.2.0 — they lead the v0.3.0 release.