Sharper on Slack, steadier on schedule

• A mention is a person, not an id. Slack mentions arrive as the names your team uses, so the coworker can answer a question about someone instead of about <@U04…>.
• A reply addresses only who it meant to. The brain's text is escaped before it posts, so an @channel it happened to type reads as words rather than paging the room — and the turn still ends in an answer instead of an error.
• Messages sent while it was down get answered. A coworker that comes back picks up the DMs it missed, and a job that posts to a thread can read that thread back, so a roll call in Slack has replies to count.
• Scheduled work stops hanging. A tick runs wherever the cluster places it instead of only on the coworker's own node — no more jobs that sit in init until their deadline kills them, with nothing in the log to say why.
• The kill switch parks automation, not people. A job whose switch is parked still runs when someone asks for it by name.
• Credentials the gateway never holds. A bundle can declare which of a job's secrets belong to the job alone, and a launch that's missing one names the field that would let it start.

The base image now pins ox 0.14.3. Full notes are on the v0.2.0 release; the quickstart is the place to start if you haven't run one yet.