rcourtman 817aaeabc1 feat(ai): surface the Assistant at first AI setup and fix blessed-path readiness ... Telemetry shows thousands of installs configure an AI provider but almost none ever use the interactive Assistant. A live first-session exercise (fresh install, Ollama qwen3:8b quickstart) found why: after enabling, nothing changes on screen — the launcher and handoff buttons are gated on sessionCapabilities.assistantEnabled, which was only read at page load; the empty transcript was blank; and the blessed Ollama+qwen3:8b path reported Patrol degraded while telling the user to pull the model they had just selected. - Setup-modal success now opens the Assistant drawer, and the AI settings save paths refresh the assistantEnabled capability in place (aiChatStore.refreshEnabledFromServer) so entry points appear without a reload; toasts point at the Assistant instead of back at settings. - The empty transcript owns a plain-language welcome and three suggested prompts that dispatch as real turns (ASSISTANT_SUGGESTED_PROMPTS). - Patrol static readiness: the blessed Ollama Patrol model is Ready; other Ollama models keep the warning, now naming the selected model. - pulse_summarize fleet argument errors instruct the model to enumerate resources itself instead of interrogating the operator (observed live: 'how is my machine doing?' ended in a resource-ID elicitation). Contracts: ai-runtime and frontend-primitives Current State updated. Tests: full internal/ai + internal/api suites green; vitest ChatMessages, AISettings, aiChat store, and settingsArchitecture suites green; flow verified live end-to-end.		2026-07-17 23:20:44 +01:00
..
internal	Govern commercial offer and lifecycle	2026-07-14 11:54:22 +01:00
v6	feat(ai): surface the Assistant at first AI setup and fix blessed-path readiness	2026-07-17 23:20:44 +01:00
control_plane.json	Update release control to use main	2026-07-05 15:20:37 +01:00
control_plane.schema.json