@praxisui/ai 8.0.0-beta.2 → 8.0.0-beta.20

package/README.md

@@ -61,7 +61,7 @@ Peer dependencies (Angular v20):
 ## What this package is responsible for
 
 - assistant UX surfaces and interaction flow
-- reusable assistant shell primitives such as conversation messages, quick replies, prompt composer, apply actions and drag/resize chrome
+- reusable assistant shell primitives such as conversation messages, quick replies, prompt composer, apply actions, drag/resize chrome and minimized-session dock
 - backend API orchestration for provider catalog, suggestions, and patch generation
 - local lightweight session history with tenant/env/user scoping
 - confirmation and risk policy integration for sensitive changes
@@ -76,10 +76,17 @@ The shell owns the shared UX primitives:
 - conversation messages and message actions such as edit/resend/custom actions
 - prompt composer, Enter-to-submit behavior, pasted or selected file attachments, submit/apply actions and attach/remove attachment events
 - active context chips for component, schema, selection, route, tenant or custom context
+- rich quick reply chips with optional description, icon, tone and structured context hints
 - attached context metadata for files, images, JSON, schema and text payloads
 - mode and state labels for `config`, `agentic-authoring`, `chat`, `diagnostic`, `review` and `inline-help`
 - draggable/resizable panel layout and accessibility labels
 
+`PraxisAiAssistantDockComponent` is the companion minimized-session surface for the same assistant identity. Hosts use it when a specialized assistant session remains active but the full shell is minimized. The dock owns the shared visual language for assistant presence, state badges and reopen affordance; hosts still provide the semantic session summary and decide what reopening means.
+
+`PraxisAssistantSessionRegistryService` is the canonical in-memory registry for assistant sessions opened by different Praxis components in the same application shell. Component hosts register their active or minimized sessions with stable `ownerId`/`ownerType` metadata so a future global assistant host can present one shared experience while preserving each component's semantic context.
+
+`PraxisAiAssistantSessionHostComponent` is the canonical presence host for minimized assistant sessions in an application or page shell. It reads `PraxisAssistantSessionRegistryService`, renders the shared dock for each minimized session, and emits the opened session snapshot after promoting that session to active in the registry. Specialized components still own the full shell events until their authoring action contracts are promoted to shared platform contracts.
+
 The shell intentionally does not own component semantics. Specialized flows still own their adapter/service contract:
 - configuration assistants continue to use `AiConfigAdapter`, capabilities, suggestions and patch review
 - Page Builder agentic authoring continues to use `/api/praxis/config/ai/authoring/**`
@@ -106,7 +113,7 @@ The orchestrator owns the turn lifecycle:
 - stable `sessionId` creation per controller when the host does not provide one
 - fresh `clientTurnId` creation for each executable submit/apply/retry/cancel turn
 - LLM-assisted clarification as a first-class `clarification` state
-- structured clarification questions and quick replies
+- structured clarification questions and quick replies, including rich chip metadata from backend flows
 - edit/resend actions for user messages, including conversation fork semantics
 - attached context add/remove state
 - apply/retry/cancel dispatch when the active flow supports it
@@ -118,6 +125,8 @@ When a flow asks for clarification, direct user input while the controller is in
 
 `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.
 
+Backend-owned flows may return quick replies as clickable chips for candidate resources, catalog follow-ups or clarification options. Hosts should keep the full quick reply object: `description`, `icon` and `tone` are presentation hints, while `contextHints` carries structured values such as `resourcePath`, `submitUrl`, `operation` and `schemaUrl` for the next turn. Do not downcast these replies to label/prompt pairs or recompute the options in the UI.
+
 When a user edits or resends an earlier user message, the controller forks the conversation from that message before invoking the flow again. Downstream assistant/user messages, quick replies, pending clarification and preview state are cleared so the backend receives the revised conversation branch instead of stale follow-up context. Hosts that expose an edit composer should call `submitEditedMessage(messageId, text)` when the revised prompt is submitted.
 
 ## What this package does not own
@@ -193,6 +202,24 @@ Notes:
 - `currentState` must be the config root (not wrapped under `config`).
 - Clarifications may return `{ type: "clarification", message, options }`.
 
+### Agentic authoring manifest tools
+- `GET /api/praxis/config/ai/authoring/manifests/{componentId}`
+- `GET /api/praxis/config/ai/authoring/manifests/{componentId}/editable-targets`
+- `GET /api/praxis/config/ai/authoring/manifests/{componentId}/operations`
+- `POST /api/praxis/config/ai/authoring/manifests/{componentId}/resolve-target`
+- `POST /api/praxis/config/ai/authoring/manifests/{componentId}/validate-plan`
+- `POST /api/praxis/config/ai/authoring/manifests/{componentId}/compile-patch`
+
+`AiBackendApiService` exposes these endpoints through typed methods so hosts can inspect the executable manifest, resolve targets, validate a component edit plan and compile a backend-owned patch without routing by local keywords.
+
+### Agentic authoring turn streaming
+- `POST /api/praxis/config/ai/authoring/turn/stream/start`
+- `GET /api/praxis/config/ai/authoring/turn/stream/{streamId}`
+- `GET /api/praxis/config/ai/authoring/turn/stream/{streamId}/probe`
+- `POST /api/praxis/config/ai/authoring/turn/stream/{streamId}/cancel`
+
+`AiBackendApiService.startAgenticAuthoringTurnStream`, `connectAgenticAuthoringTurnStream` and `cancelAgenticAuthoringTurnStream` use the same SSE envelope contract as patch streaming. Browser `EventSource` cannot send custom headers, so signed stream tokens returned by the backend should be passed to `connectAgenticAuthoringTurnStream` and `cancelAgenticAuthoringTurnStream` when the backend uses signed-url stream auth.
+
 ## Assistant local history (UI)
 
 The assistant stores a lightweight local history in the browser using `localStorage`. It is scoped by