feat!: prepare Homarr v2 release (#6746)

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

@@ -11,14 +11,11 @@ import assistantWidgetImage from "../../management/img/assistant-widget.png";
 
 <WidgetHeader widget={assistantWidget} categories={["Productivity"]} />
 
-The Assistant widget brings the same conversation available from the user menu and command menu onto a
-board. Messages, conversations, tool calls, approvals, files, mentions, model controls, reasoning controls,
-usage details, and response actions remain synchronized with the app-wide assistant.
+The Assistant widget puts the app-wide assistant on a board. It uses the same active conversation as the user-menu and
+command-menu surfaces, so messages and approvals stay synchronized.
 
-The assistant must be enabled by an administrator in **Management → Assistant**. Signed-out users and users
-on an instance without an enabled model see an unavailable state instead of a broken composer. Signed-out users see
-**Sign in**; a configured provider without a saved model or with **Enable Assistant** off remains unavailable until
-the administrator saves a working connection, selects a model, and enables the assistant.
+An administrator must first configure and enable Assistant in **Management → Assistant**. Signed-out users are prompted
+to sign in, while an incomplete or disabled configuration shows an unavailable state.
 
 <img
   src={assistantWidgetImage}
@@ -26,44 +23,14 @@ the administrator saves a working connection, selects a model, and enables the a
   style={{ maxWidth: "100%" }}
 />
 
-The current preview capture labels the board-embedded surface: its header exposes conversation history, refresh,
-automatic approvals, and new-conversation controls, while the footer exposes the model, thinking mode, and composer.
-
 ### Adding the widget
 
 <AddingWidget />
 
-The default widget size is ten columns by four rows and automatically fits boards with fewer columns. Controls
-and labels condense as the widget becomes narrower, while the conversation remains scrollable and usable on
-touch devices. When a board layout does not provide enough height for conversation controls, the widget shows
-a compact **Open assistant** action instead of squeezing an unusable composer into the card. Increase its height
-in that layout to keep the complete conversation inline.
+The default size is ten columns by four rows and shrinks to fit narrower boards. Short layouts show an **Open
+assistant** action instead of compressing the conversation controls; increase the widget height to keep the complete
+conversation inline.
 
-The widget follows whichever conversation is active in the user-menu panel, `Shift + A`, or the command menu. This
-keeps every assistant entry point synchronized without storing a user's private conversation details in board settings.
-
-### Conversation features
-
-- Create, switch, rename, and delete conversations.
-- Send text and supported file or image attachments by picker, drag and drop, or image paste.
-- Mention permitted apps, integrations, boards, widgets, and tools with `@`.
-- Use `/` shortcuts for common dashboard tasks.
-- Review tool calls, approve mutations, and answer structured assistant questions inline.
-- Answer pending structured questions from the dock above the composer without scrolling through the conversation.
-- Enable conversation-scoped automatic approvals from the shield control to approve protected mutations, use presented form details, and choose answers categorized as affirmative without individual clicks.
-- Edit user messages and copy, regenerate, branch, quote, export, or rate responses.
-- Inspect syntax-highlighted Markdown, sources, generated files, tool results, streaming chain-of-thought,
-  cumulative conversation usage, per-turn token and context use, timing, speed, provider routing, and cost.
-- Change the model and reasoning effort for the active conversation. A model choice is saved per persisted thread,
-  does not change the administrator's default, and is restored when that thread is selected again; a new thread
-  starts from the configured default.
-- 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. Each visible surface keeps an
-independent draft, attachments, selection, and focus, so typing in a board widget cannot move or overwrite the
-floating panel composer.
-
-Automatic approvals are off by default, reset when switching conversations, and never select a neutral choice. A
-structured question shows **Other** only when the tool allows it (`allowOther` is not `false`); selecting **Other**
-opens a manual freeform response even when automatic approvals are enabled.
+Responses continue when the widget leaves the viewport. Drafts and attachments remain local to each visible Assistant
+surface, and private conversation data is never stored in board settings. Normal Homarr permissions and approval rules
+still apply to every action.

apps/docs/docs/widgets/timer/index.mdx

@@ -13,35 +13,20 @@ import { timerWidget } from ".";
 
 <WidgetHeader widget={timerWidget} categories={["Productivity", "Time"]} />
 
-The Timer / Pomodoro widget runs entirely in your browser and does not require an integration. The compact widget
-always keeps its start or pause button and reset button visible. A running timer uses a saved deadline, so reopening
-the board or returning to a background tab restores the correct remaining time instead of restarting the countdown.
+The Timer / Pomodoro widget runs in your browser and does not require an integration. A running timer uses a saved
+deadline, so reopening the board or returning from a background tab restores the correct remaining time.
 
 Timer mode uses one configured duration. Pomodoro mode starts with a focus session, follows most completed focus
 sessions with a short break, and uses a long break after the configured number of focus sessions. Automatic break and
 focus starts are separate options and are disabled by default. When automatic starts are enabled, elapsed phases are
 reconciled from their original deadlines after the board returns to the foreground.
 
-Advanced view shows the current sequence, configured durations, and local alert preferences. Browser notifications are
-requested only when enabled. Notification and sound preferences, live progress, deadlines, and cycle position are
-stored locally using the board and widget identifiers. They are separate for each browser or device, are available to
-guest viewers, and are removed by clearing site data. Widget previews are ephemeral and do not write local timer state.
+Advanced view shows the sequence, durations, and local alert preferences. Sounds are enabled by default, while browser
+notifications are requested only after you enable them. Progress and alert preferences are stored per board and widget
+in the current browser; clearing site data resets them, and widget previews do not persist timer state.
 
-Timer sounds are enabled by default and use the same low-volume Tiks sound system as onboarding: start and pause use
-rising and falling soft-theme cues, reset uses a short click, and phase completion uses the glass theme's resonant
-notification ding. You can disable them in advanced view. The cues respect the device's reduced-motion preference and
-supplement the visible timer state rather than replacing it.
-
-When automatic start is disabled, a completed phase labels the next step as ready and flashes the widget edges with the
-board's secondary color. The border glow and completion chime run together as a five-beat alarm burst at
-300-millisecond intervals, then stop. Reduced-motion and forced-colors modes replace the flash with a static border.
-The current phase stays pinned to the compact widget's top-left corner and wraps when needed. Timer text and controls
-use the dashboard theme's responsive size scale, with secondary details hidden when the widget preview is narrow or
-short.
-
-Alerts can fire while Homarr is open. Browser and operating-system notification settings may still suppress them.
-The timer's mode, durations, session count, and automatic-start behavior are permanent board settings and are edited
-from the widget context menu.
+Alerts can fire while Homarr is open, but browser or operating-system settings may suppress notifications. Reduced-motion
+and forced-colors preferences replace the animated completion effect with a static border.
 
 <WidgetInteractionGuide />