mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Herald Service: Add Matrix output adapter for status broadcasts #382

New Issue
Closed
opened 2026-02-15 07:01:23 +00:00 by jason.woltje · 1 comment
jason.woltje commented 2026-02-15 07:01:23 +00:00
Owner
Copy Link

Summary

Extend the Herald service to broadcast job status updates to Matrix rooms in addition to (or instead of) Discord threads.

Context

Herald currently formats status updates and sends them via the Discord bridge. It needs to become bridge-agnostic — broadcasting to all active chat providers.

Implementation

Option A: Bridge Registry (recommended)

Herald receives an injected list of active IChatProvider instances and broadcasts to all of them:

class HeraldService {
  constructor(
    @Inject('CHAT_PROVIDERS') private providers: IChatProvider[]
  ) {}

  async broadcast(jobId: string, update: StatusUpdate) {
    for (const provider of this.providers) {
      if (provider.isConnected()) {
        await provider.sendThreadMessage({ threadId, content: formatted });
      }
    }
  }
}

Option B: Direct injection

Herald gets both DiscordService and MatrixService injected (simpler but less extensible).

Verbosity Levels

Same noise management as Discord:

  • Low (main room): Milestones only (job started, job completed/failed)
  • Medium (thread): Step completions, gate results
  • High (on request): Full step logs

Matrix-Specific Formatting

  • Use Matrix's m.notice message type for bot updates (not m.text) to avoid notification noise
  • Support formatted body (HTML) for rich status messages
  • Use reactions (✅ ❌ ⏳) on the original command message for quick status

Acceptance Criteria

  • Herald broadcasts to all active chat providers
  • Matrix rooms receive job status updates
  • Verbosity levels respected
  • Matrix-specific formatting (m.notice, HTML body)
  • No crash if Matrix is not configured
  • Tests verify broadcast to multiple providers

Refs

## Summary Extend the Herald service to broadcast job status updates to Matrix rooms in addition to (or instead of) Discord threads. ## Context Herald currently formats status updates and sends them via the Discord bridge. It needs to become bridge-agnostic — broadcasting to all active chat providers. ## Implementation ### Option A: Bridge Registry (recommended) Herald receives an injected list of active `IChatProvider` instances and broadcasts to all of them: ```typescript class HeraldService { constructor( @Inject('CHAT_PROVIDERS') private providers: IChatProvider[] ) {} async broadcast(jobId: string, update: StatusUpdate) { for (const provider of this.providers) { if (provider.isConnected()) { await provider.sendThreadMessage({ threadId, content: formatted }); } } } } ``` ### Option B: Direct injection Herald gets both `DiscordService` and `MatrixService` injected (simpler but less extensible). ### Verbosity Levels Same noise management as Discord: - **Low** (main room): Milestones only (job started, job completed/failed) - **Medium** (thread): Step completions, gate results - **High** (on request): Full step logs ### Matrix-Specific Formatting - Use Matrix's `m.notice` message type for bot updates (not `m.text`) to avoid notification noise - Support formatted body (HTML) for rich status messages - Use reactions (✅ ❌ ⏳) on the original command message for quick status ## Acceptance Criteria - [ ] Herald broadcasts to all active chat providers - [ ] Matrix rooms receive job status updates - [ ] Verbosity levels respected - [ ] Matrix-specific formatting (m.notice, HTML body) - [ ] No crash if Matrix is not configured - [ ] Tests verify broadcast to multiple providers ## Refs - Herald service location (find via grep for HeraldService) - Discord noise management: `apps/api/src/bridge/discord/discord.service.ts` - EPIC: #377 - Depends on: #378, #380
jason.woltje added the apiapi labels 2026-02-15 07:01:23 +00:00
jason.woltje added this to the M12-MatrixBridge (0.0.12) milestone 2026-02-15 07:01:51 +00:00
jason.woltje commented 2026-02-15 08:30:32 +00:00
Author
Owner
Copy Link

Completed in commit ad24720 on branch feature/m12-matrix-bridge.

  • Herald Service refactored from Discord-specific to bridge-agnostic CHAT_PROVIDERS array
  • Broadcasts to ALL active chat providers (Discord, Matrix, future)
  • Graceful error handling: one provider failure does not block others
  • Skips disconnected providers automatically
  • Tests verify multi-provider broadcasting behavior
Completed in commit ad24720 on branch feature/m12-matrix-bridge. - Herald Service refactored from Discord-specific to bridge-agnostic CHAT_PROVIDERS array - Broadcasts to ALL active chat providers (Discord, Matrix, future) - Graceful error handling: one provider failure does not block others - Skips disconnected providers automatically - Tests verify multi-provider broadcasting behavior
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label api api
Milestone
No items
No Milestone M12-MatrixBridge (0.0.12)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#382
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?