Aggregated OPAL pipeline status surface. More...
| Header: | #include <OpalStatusContext> |
| Since: | 1.0 |
| Inherits: | QObject |
Single facade over the four+1 independent sources that determine whether OPAL is configured, reachable, and what it is doing right now: LLMRegistry, OpalAuthContext, OpalTaskRuntime, the HTTP layer's reachability reports, and the various "needs-attention" surfaces (permission requests, pending sentient requests, …).
The button (§OB) and any other UI consumer subscribes to this one context rather than reconciling four sources themselves. See the precedence ladder in activity-header-makeover/opal-button.md §OB-3.
Wiring to the concrete sources is per-Node and happens in NodeWindow::configure() — this class only owns the aggregation logic and the externally-visible status property. Source-specific hooks are exposed as public slots so concrete sources can push state in without OpalStatusContext having to depend on each lib directly.