Automations check their proposals, post to your tracker, Slack, email and webhooks, and fire from a webhook
A proposal's edits are now checked in a Sandbox with the repository's own type checker, linter, Semgrep or Theme Check before the pull request opens; what the tools report on the changed lines goes back to the agent for one more round, and the pull request says what was checked. Four new outputs: a comment on the pull request's ticket in Linear, Jira or Shortcut (or a tracker issue in a team or project you name), an email digest per firing, a Slack message per firing through an incoming webhook, and a signed POST per run to a URL of yours.
A new Webhook trigger gives an automation its own firing URL with a token shown once: anything that can POST (a Shopify webhook, a deploy hook, a script) fires it on every repository in scope, with the request's body as data for the agent. Rotate the token from the automation's page.
From a pull request, @auditor automation <name> runs the team automation of that name on that repository with the pull request as its subject.
Slack URLs and signing secrets are stored sealed and never shown again. Tracker posts use the connection under Ticket links, so its token has to be able to write.
More in Outputs.