add telegram and ntfy event delivery

This commit is contained in:
kami
2026-07-26 20:31:42 +04:00
parent f818003ad5
commit 4093bdb683
3 changed files with 147 additions and 0 deletions
+2
View File
@@ -65,6 +65,8 @@ Provider supervision/reflection is now wired: Gitea webhook and polling use appe
Quota reporting now has strict payload validation, and `router.QuotaAvailability` implements rolling-window conservative headroom filtering: a harness is considered full at 80% of its configured limit. Standup event payloads also require an items field; scheduled advisory production and approval application remain open.
Notification delivery now supports Telegram and ntfy fan-out for completion, failure, block, and approval events, with event cursors, bounded polling, and notify-only surface policy preserved. Configure `ORCHESTRA_TELEGRAM_BOT_TOKEN`/`ORCHESTRA_TELEGRAM_CHAT_ID` or `ORCHESTRA_NTFY_TOPIC` to enable it.
Recommended order:
1. Add the orchestration coordinator: lease → worktree → harness session → bootstrap → lifecycle events.