Repository navigation
fix(OMN-10079): publish terminal outputs for brokered runtime commands - #1515
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAdds orchestrator "terminal_event" support: contract metadata, discovery parsing, model field, wiring selection for terminal-topic result dispatch, Pattern B package-name derivation tweak, and unit/integration tests plus a new contract file. ChangesTerminal Event Result Handling
Sequence DiagramsequenceDiagram
participant Contract as Contract YAML
participant Discovery as Discovery Parser
participant Model as ModelDiscoveredContract
participant Wiring as Handler Wiring
participant Bus as Event Bus
participant Handler as Handler
participant Applier as DispatchResultApplier
Contract->>Discovery: load contract (OMN-10079)
Discovery->>Model: create ModelDiscoveredContract (includes terminal_event)
Model->>Wiring: supply discovered contract
Wiring->>Wiring: determine output_topic (single publish or terminal_event)
Bus->>Handler: deliver command envelope
Handler->>Handler: process -> result model
Handler->>Applier: return result
Applier->>Bus: publish result to terminal_event topic
Bus->>Bus: emit terminal-topic message
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Ticket
Summary
Live proof
Verification
Summary by CodeRabbit
New Features
Tests
Chores