@praxisui/ai 8.0.0-beta.102 → 8.0.0-beta.104

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +2 -0
  2. package/fesm2022/praxisui-ai.mjs +304 -62
  3. package/package.json +2 -2
  4. package/types/praxisui-ai.d.ts +41 -8
package/README.md CHANGED
@@ -150,6 +150,8 @@ The orchestrator owns the turn lifecycle:
150
150
 
151
151
  The orchestrator remains flow-agnostic. Each consumer provides a `PraxisAssistantTurnFlow` for its mode. For example, a config assistant flow can wrap `AiConfigAdapter` plus `/api/praxis/config/ai/patch`, while Page Builder agentic authoring can wrap `/api/praxis/config/ai/authoring/**`.
152
152
 
153
+ When `@praxisui/core` runtime component observations are registered, the orchestrator attaches them to `PraxisAssistantTurnRequest.runtimeComponentObservations` as untrusted frontend evidence. Stream clients forward non-empty observations with `runtimeComponentObservationTrustBoundary="untrusted_frontend_observation"`. This field is transport-only in `@praxisui/ai`: it does not resolve intent, promote capabilities, select quick replies, alter previews or bypass backend grounding.
154
+
153
155
  When a flow asks for clarification, direct user input while the controller is in `clarification` state is sent to the flow as a `clarify` action with the pending clarification context. Hosts should not rewrite short answers locally; they should pass the request context through to the backend or flow that owns the authoring semantics.
154
156
 
155
157
  `pendingClarification.diagnostics` is opaque flow state. It is preserved across the next clarification answer so backend-owned semantics can keep metadata-only context, including attachment summaries, without the shell understanding the domain or retaining local file payloads.