refresh views after assistant changes

apps/docs/docs/management/assistant.mdx

@@ -173,9 +173,14 @@ modify permission on the selected board. The empty conversation includes an **Im
 and `/style` prepares the same guided workflow from the composer.
 
 Homarr also exposes a small set of browser-only actions to the assistant. These actions can navigate to
-safe internal routes and open Homarr interfaces such as the command menu and media request search.
+safe internal routes, refresh the current view, and open Homarr interfaces such as the command menu and media request search.
 They never receive provider credentials and cannot navigate to arbitrary external URLs.
 
+After an approved mutation completes, Homarr automatically refetches active page and dashboard data so
+board items, settings, custom CSS, apps, and other visible results update without a full browser reload.
+The refresh action in the conversation header performs the same safe refetch manually. It keeps the
+conversation open while refreshing both client queries and server-rendered route data.
+
 :::warning
 
 Assistant prompts and selected tool results are sent to the configured model endpoint. Review that

apps/docs/docs/widgets/assistant/index.mdx

@@ -51,6 +51,7 @@ active conversation silently: select **Open conversation** inside the widget bef
 - Inspect Markdown, sources, generated files, tool results, reasoning, token use, context-window use, timing,
   speed, provider routing, and cost.
 - Change the model and reasoning effort for the active conversation.
+- Refresh the current board from the conversation header. Approved mutations also refresh visible board data automatically.
 
 The expanded assistant and board widget use the same persisted thread runtime. A response continues in the
 background when the widget leaves the viewport or the expanded panel is minimized.