Webhooks

Events from outside become board tasks or workflow runs. The daemon serves POST /v1/webhooks/{source} with a bearer token (the module’s token setting); a connected daemon’s sources can post through the cloud instead - the module sees no difference.

• Sources: each names its kind, the workspace and board its tasks go to (or the workflow its requests run), the member they are assigned to, and a channel destination to tell at once. Alertmanager comes first; a generic JSON source runs workflows.
• One task per incident: a firing alert group opens one task (keyed, so it fires again into the same task); a resolved group comments its duration and records the incident to memory, so the next alert like it recalls the diagnosis. A task the member labeled no-action closes on resolve.
• A notification with no alerts does nothing - a probe costs no agent turn.