The Light backing of the opalContext facility (§SAL-2.2, D8): the node-free OPAL/LLM stack, stood up once per app. More...
| Header: | #include <StandaloneOpalContext> |
| Inherits: | QObject |
Bundles what the standalone OPAL surface needs — an LLMRegistry backed by <baseDir>/opal/llm_registry.json (providers + API keys), an LLMManager over it, and the OpalStatusContext that derives the readiness banner / send-gating from that registry (§OP-1 / §OB-3). libllm pulls in no identity/hive/comms, so this stays a self-contained HTTP client stack (proven by commit a4075edbe).
A QObject bridge per the -fno-rtti facility pattern (§ACF-6): register it under opalContext on the app's StandaloneActivityContext and recover it with qobject_cast. Constructing it does not touch the network — the registry only reports whether providers are configured; readiness stays gated until the user configures one.