Add a Messaging Platform Adapter

This build lab focuses on the adapter layer that lets one agent runtime support many messaging platforms. The goal is not to copy a private machine setup. The goal is to learn the architecture pattern well enough to build a small, classroom-safe version.

A platform adapter normalizes incoming events, authenticates the sender, maps the session, sends replies, and exposes platform-specific tools only when allowed.

Build the small version

1. 1Draw or write an adapter checklist for adding a school forum, Teams channel, or Discord bot.
2. 2Mark which parts are user-facing, which parts are internal, and which parts require approval.
3. 3Choose one low-risk workflow and implement only that workflow first.
4. 4Add one failure case before adding a second feature.
5. 5Write a short operator note: what the agent may do, what it must ask about, and what it must never do.

adapter contract:
  name: school_forum
  verify(event) -> boolean
  parse(event) -> NormalizedMessage
  session(message) -> SessionSource
  send(session, reply) -> DeliveryResult
  tools(session) -> AllowedTools[]

The big idea: adapter is not decoration. It is part of the product architecture students need before an agent becomes safe enough to use with real people.