feat: cli demo no read only

This reverts commit 3603d0393c.

.cursor/rules/codebase-context.mdc

@@ -66,8 +66,6 @@ homarr/
 │   ├── analytics/       # Server-side analytics (Umami)
 │   ├── server-settings/ # Server setting keys/types
 │   ├── settings/        # User-facing settings UI context
-│   ├── old-import/      # Legacy Homarr import
-│   ├── old-schema/      # Legacy Homarr zod schemas
 │   └── cli/             # Node CLI for ops (brocli)
 ├── tooling/
 │   ├── typescript/      # Base tsconfig

.cursor/rules/mantine-datatable-migration.mdc

@@ -263,15 +263,6 @@ Even hidden options need translation keys or the translation test fails:
 "widget.mywidget.option.columnWidths.label": "Column widths"
 ```
 
-### Old-import mappings
-
-Add to `packages/old-import/src/widgets/options.ts`:
-
-```typescript
-columnOrder: () => undefined,
-columnWidths: () => undefined,
-```
-
 ### Dynamic storeKey
 
 Use a key that includes `itemId` and sorted column names. This prevents cross-widget localStorage bleeding:
@@ -610,13 +601,12 @@ if (isEditMode) rowContextMenuHandler = undefined;
 4. Add CSS file for transparent backgrounds (if widget context)
 5. Add responsive column visibility (if widget context)
 6. Add hidden options + hydration logic (if column persistence needed)
-7. Add old-import mappings for new options
-8. Add translation keys (including hidden option labels)
-9. Add context menu if row actions exist
-10. Add row expansion if detail view exists
-11. Add error handling on all mutations
-12. Add accessibility attributes
-13. Test at multiple widget widths
-14. Update docs in `apps/docs/docs/widgets/` if applicable
-15. Run `pnpm turbo typecheck` — catches old-import mismatches
-16. Run translation spec — catches missing keys
+7. Add translation keys (including hidden option labels)
+8. Add context menu if row actions exist
+9. Add row expansion if detail view exists
+10. Add error handling on all mutations
+11. Add accessibility attributes
+12. Test at multiple widget widths
+13. Update docs in `apps/docs/docs/widgets/` if applicable
+14. Run `pnpm turbo typecheck`
+15. Run translation spec — catches missing keys

.deepsource.toml

@@ -1,8 +0,0 @@
-version = 1
-
-[[analyzers]]
-name = "javascript"
-
-[analyzers.meta]
-plugins = ["react"]
-environment = ["nodejs"]

.env.example

@@ -67,7 +67,8 @@ HOMARR_WEBSITE_URL=https://homarr.dev
 # PocketBase API used by Homarr and by the standalone documentation site.
 # Defaults to HOMARR_WEBSITE_URL.
 # WORKSHOP_API_URL=https://homarr.dev
-# Public Workshop page opened from Homarr. Defaults to HOMARR_WEBSITE_URL/workshop.
+# Public Workshop website used by links in Homarr, Custom Widgets, onboarding,
+# and assistant context. Defaults to HOMARR_WEBSITE_URL/workshop.
 # WORKSHOP_WEB_URL=https://homarr.dev/workshop
 
 # Documentation and PocketBase deployment settings.

.github/workflows/ci.yml

@@ -3,10 +3,10 @@ name: CI
 on:
   pull_request:
     types: [opened, synchronize, reopened, ready_for_review]
-    branches: ["*"]
+    branches: ["**"]
   pull_request_target:
     types: [closed]
-    branches: ["*"]
+    branches: ["**"]
   push:
     branches: [main, dev, beta, next, v2]
   merge_group:

.github/workflows/workshop.yml

@@ -3,7 +3,7 @@ name: Workshop
 on:
   pull_request:
   push:
-    branches: [dev, v2, main]
+    branches: [dev, v2, release/v2, main]
 
 permissions:
   contents: read
@@ -28,7 +28,7 @@ jobs:
       - run: pnpm test:workshop-image
 
   publish:
-    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'main')
+    if: github.event_name == 'push' && (github.ref_name == 'v2' || github.ref_name == 'release/v2' || github.ref_name == 'main')
     needs: validate
     runs-on: ubuntu-24.04
     timeout-minutes: 30
@@ -50,7 +50,7 @@ jobs:
           images: ghcr.io/homarr-labs/workshop
           tags: |
             type=sha,prefix=sha-,format=long
-            type=raw,value=v2,enable=${{ github.ref_name == 'v2' }}
+            type=raw,value=v2,enable=${{ github.ref_name == 'v2' || github.ref_name == 'release/v2' }}
             type=raw,value=latest,enable=${{ github.ref_name == 'main' }}
       - uses: docker/build-push-action@v7
         with:

.impeccable/critique/2026-07-21T11-32-50Z__apps-docs-src-components-workshop.md

@@ -1,116 +0,0 @@
----
-target: Workshop store in the docs
-total_score: 20
-p0_count: 1
-p1_count: 3
-timestamp: 2026-07-21T11-32-50Z
-slug: apps-docs-src-components-workshop
----
-
-# Workshop Store Critique
-
-## Design Health Score
-
-| #         | Heuristic                           |     Score | Key issue                                                                                                                                                        |
-| --------- | ----------------------------------- | --------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 1         | Visibility of system status         |       1/4 | Fetch failure can show beside an empty-store message, so the system communicates two incompatible states.                                                        |
-| 2         | Match between system and real world |       3/4 | Widget, CSS, voting, revisions, and comments use familiar language.                                                                                              |
-| 3         | User control and freedom            |       2/4 | Filters are reversible, but the crashed route and failed fetch state offer no useful recovery.                                                                   |
-| 4         | Consistency and standards           |       2/4 | The submission editor uses CodeMirror, while revision editing falls back to a textarea; several tiny custom controls do not follow the shared button vocabulary. |
-| 5         | Error prevention                    |       2/4 | Submission validation exists, but disabled progression does not explain what is missing and destructive actions use a brief inline confirmation.                 |
-| 6         | Recognition rather than recall      |       3/4 | Labels, type choices, and the submission stepper are understandable without documentation.                                                                       |
-| 7         | Flexibility and efficiency          |       2/4 | Search covers titles only, signed-out users can select Yours, and installation is reduced to ambiguous Copy and Download actions.                                |
-| 8         | Aesthetic and minimalist design     |       3/4 | The restrained visual system is clean, but the browse toolbar and card action rows become dense.                                                                 |
-| 9         | Help users recover from errors      |       0/4 | The production route crashes with React error 130; the fetch error has no retry action or useful context.                                                        |
-| 10        | Help and documentation              |       2/4 | The editor explains its fields, but the store does not teach the full inspect, trust, download, and install journey.                                             |
-| **Total** |                                     | **20/40** | **Needs work before release**                                                                                                                                    |
-
-## Anti-Patterns Verdict
-
-The surface does not look like obvious AI-generated decoration. Its visual restraint, familiar controls, and practical editor are credible product UI. The weakness is product behavior rather than styling: contradictory states, tiny action controls, an overloaded responsive toolbar, and a primary installation journey that is not explicit.
-
-The deterministic Impeccable scan returned zero findings for `apps/docs/src/components/workshop`. This is useful but incomplete. The detector did not catch runtime failures, semantic state conflicts, touch-target sizing, or responsive grouping. Browser evidence found a full route crash, React error 130, and an earlier state that rendered both `Something went wrong.` and `No submissions yet`.
-
-No visual overlay was injected because the available browser evaluation surface is read-only. Screenshots, DOM snapshots, console logs, and source inspection were used instead.
-
-## Overall Impression
-
-The submission modal is now one of the stronger parts of the Workshop. The store around it is not release-ready. The single biggest opportunity is to make discovery and installation a dependable, explicit path: load reliably, show one truthful state, help users evaluate a submission, and give them one obvious next action.
-
-## What Is Working
-
-1. The visual system is restrained and consistent with the Homarr documentation. Typography, color, radii, and spacing do not compete with the content.
-2. The submission flow chunks a complex task into Type, Details, and Media. The shared JSON/CSS editor, drag-and-drop import, metadata autofill, and capped media previews reduce creator effort.
-3. The detail design exposes revision, author, reports, changelog, source content, and comments. This supports inspection rather than treating community code as a blind install.
-
-## Priority Issues
-
-### P0: The Workshop route crashes in the production docs build
-
-**Why it matters:** No visual polish matters if the store becomes a Docusaurus error page. A fresh independent tab consistently reached `This page crashed` with React error 130. The console attributed the thrown error to the Kapa widget bundle.
-
-**Fix:** Isolate or disable the Kapa script on Workshop routes, prevent third-party widget failures from reaching the Docusaurus route boundary, and add a route-level Workshop boundary that preserves navigation and retry. Reproduce against the built Docker docs image, not only the development server.
-
-**Suggested command:** `$impeccable harden`
-
-### P1: Failure and empty states contradict each other
-
-**Why it matters:** Showing `Something went wrong.` followed by `No submissions yet` makes users believe the store is both broken and empty. The generic message gives no cause and no recovery.
-
-**Fix:** Make loading, failure, empty, and results mutually exclusive. The failure state should say that listings could not be loaded, preserve the current filters, and provide `Try loading again`. Do not render filters or an empty store as authoritative data after the initial request fails.
-
-**Suggested command:** `$impeccable harden`
-
-### P1: Mobile discovery controls are too dense and do not form a responsive hierarchy
-
-**Why it matters:** The toolbar's inner row contains four type choices, sorting, and outdated visibility without wrapping. Most controls are 24 to 28 pixels tall. At narrow widths this is difficult to scan, easy to clip, and below a comfortable touch target.
-
-**Fix:** Put a full-width search first on mobile, keep All, Widgets, and CSS as the primary segmented choice, move sorting and outdated visibility into a compact secondary row or popover, and hide Yours when signed out or make it a sign-in affordance. Use at least 40 to 44 pixel touch targets. Add `aria-pressed` or proper tab semantics to the type filter.
-
-**Suggested command:** `$impeccable adapt`
-
-### P1: The store does not make the install journey obvious
-
-**Why it matters:** A first-time user sees Copy and Download without knowing which is recommended, what will be copied, how to inspect safety, or where the file goes in Homarr. This weakens the store's main purpose.
-
-**Fix:** Make the detail page the decision surface. Use one primary action named for its result, such as `Download widget JSON` or `Copy CSS`, with a short `Install in Homarr` explanation linked to the correct in-app flow. Cards should prioritize title, preview, compatibility, score, and `View details`; secondary utilities should not compete with evaluation.
-
-**Suggested command:** `$impeccable clarify`
-
-### P2: Card and moderation actions are too small and too numerous
-
-**Why it matters:** Vote, copy, download, comment, delete, and report controls compete in a compact footer. Low-contrast icon buttons are hard to discover and hard to use by touch. CSS columns also create a top-to-bottom visual reading order that can differ from the expected row order.
-
-**Fix:** Use a regular responsive grid, remove hover scaling, keep one or two visible card actions, and move owner/moderation actions to a menu. Keep voting visible but increase its target size. Correct the report copy: reports and reporter identities are moderation data, not public social proof.
-
-**Suggested command:** `$impeccable distill`
-
-## Persona Red Flags
-
-### Jordan, first-time self-hoster
-
-Jordan opens Workshop to install a widget. The route can crash before any listing appears. In the partial failure state, Jordan sees both an error and an empty store. If listings load, Copy and Download do not explain the Homarr destination or recommended path. Jordan is likely to leave before installing anything.
-
-### Alex, experienced Homarr administrator
-
-Alex can understand the JSON and appreciates the source viewer, but title-only search and limited filtering make a larger catalog inefficient. Compatibility and required secret information are not prominent at browse time. Tiny moderation and owner controls slow repeated management tasks.
-
-### Morgan, mobile user
-
-Morgan encounters a toolbar with more controls than fit comfortably in one decision group, 24 to 28 pixel targets, and a signed-out Yours filter that leads to an unhelpful no-results state. Submission cards add another dense row of small actions.
-
-## Minor Observations
-
-- Future submission steps are focusable buttons even when clicking them does nothing. Disable them or render non-interactive progress markers.
-- The report textarea relies on placeholder text and needs a persistent accessible label.
-- The revision editor should reuse the same JSON/CSS CodeMirror component as creation.
-- Search should include title, description, and author at minimum.
-- The timed inline `Confirm?` deletion pattern is easy to miss and weak for keyboard and touch users.
-- The detail-page changelog uses an uppercase tracked label, which is unnecessary in this otherwise restrained interface.
-- Loading comments should use the same skeleton vocabulary as listings rather than centered status text.
-
-## Questions to Consider
-
-1. Is Workshop primarily a catalog for discovery, or a technical exchange for copying source? The primary card and detail actions should commit to one answer.
-2. Should users evaluate compatibility and required secrets before opening a listing, or only on the detail page?
-3. Does Workshop need every moderation and ownership action visible inline, or should those actions live behind a menu?

.impeccable/critique/2026-07-21T12-29-41Z__apps-docs-src-components-workshop.md

@@ -1,64 +0,0 @@
----
-target: Workshop store in the docs
-total_score: 38
-p0_count: 0
-p1_count: 0
-timestamp: 2026-07-21T12-29-41Z
-slug: apps-docs-src-components-workshop
----
-
-# Workshop Store Critique — Post-Polish
-
-## Design Health Score
-
-| #         | Heuristic                           |     Score | Evidence                                                                                                                                                         |
-| --------- | ----------------------------------- | --------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 1         | Visibility of system status         |       4/4 | Loading, initial failure, stale refresh failure, empty, and results states are mutually exclusive; recovery actions are visible.                                 |
-| 2         | Match between system and real world |       4/4 | Actions describe their result: Download widget JSON, Copy CSS, View details, and Install in Homarr.                                                              |
-| 3         | User control and freedom            |       4/4 | Filters can be cleared, errors retried, dialogs cancelled, and destructive submission deletion requires explicit confirmation.                                   |
-| 4         | Consistency and standards           |       4/4 | Creation and revision editing share CodeMirror, buttons follow the shared system, and cards use a predictable responsive grid.                                   |
-| 5         | Error prevention                    |       3/4 | Validation, disabled progression, pending states, RLS, and confirmations are strong; disabled form progression could explain unmet requirements more explicitly. |
-| 6         | Recognition rather than recall      |       4/4 | Persistent labels, type descriptions, step status, source previews, and installation instructions minimize recall.                                               |
-| 7         | Flexibility and efficiency          |       4/4 | Search spans title, description, and author; signed-in filtering, sorting, responsive controls, and direct detail actions support repeat use.                    |
-| 8         | Aesthetic and minimalist design     |       3/4 | The catalog is restrained and scannable; long source documents and the complete creator form necessarily remain dense on small screens.                          |
-| 9         | Help users recover from errors      |       4/4 | Route, listing, edit, report, copy, OAuth, and detail failures remain local and provide a clear next action.                                                     |
-| 10        | Help and documentation              |       4/4 | The detail page explains the exact Homarr destination and links to updated Workshop documentation.                                                               |
-| **Total** |                                     | **38/40** | **Release-quality; minor polish remains**                                                                                                                        |
-
-## Anti-Patterns Verdict
-
-The surface is product-led rather than decorative. The redesign removes the overloaded card footer, hover scaling, tiny touch controls, public moderation details, contradictory states, and ambiguous install actions. The deterministic Impeccable detector reports zero findings.
-
-## What Improved
-
-1. The production route no longer collapses into the Docusaurus crash screen without recovery. A route-local boundary protects navigation, and the fresh-volume production path renders without console errors.
-2. Loading, failure, empty, stale-results, and populated states are truthful and mutually exclusive.
-3. Search and filters form a clear responsive hierarchy. Mobile targets are 40–44 pixels, signed-out users do not see Yours, and cards no longer overflow at 390 pixels.
-4. Cards prioritize evaluation: title, author, type, score, description, comments, and View details. Copy, download, reporting, editing, and deletion moved to the detail page.
-5. The detail page now teaches the installation journey and names its primary action precisely.
-6. Reports and reporter identities are admin-only through PocketBase rules. Public catalog UI no longer turns reports into social proof.
-7. The creator and revision dialogs share the CodeMirror editor, use bounded internal scrolling, expose pending/error states, and avoid step-selection layout shifts.
-
-## Remaining Minor Opportunities
-
-### P2: Explain disabled progression inline
-
-The Type and Details steps are understandable, but a disabled Next button could state the missing requirement for keyboard and first-time users. This is a refinement, not a blocker, because required fields and validation messages are already present.
-
-### P2: Consider a compact source summary on very small screens
-
-The read-only source viewer is intentionally complete and horizontally scrollable. A future collapse/expand summary could reduce page length for nontechnical visitors without hiding inspection entirely.
-
-## Verification Evidence
-
-- Fresh Docker Compose PocketBase volume and production docs image.
-- Populated catalog with widget, CSS, and outdated examples.
-- Desktop and 390px mobile layouts in light and dark themes.
-- Widget detail, installation instructions, CodeMirror source view, and comments.
-- Signed-in submission wizard through Type and Details, including the shared editor.
-- Zero browser console errors after the final fixes.
-- Impeccable deterministic detector: zero findings.
-
-## Compatibility Note
-
-An existing local development volume created from an earlier unreleased version of the reset migration still has a stale Workshop view. It is intentionally not migrated or deleted. A fresh volume created from the current unreleased migration is the supported validation target and works correctly.

.impeccable/critique/2026-07-22T15-58-15Z__apps-docs-src-components-workshop.md

@@ -1,106 +0,0 @@
----
-target: Homarr Workshop docs UI
-total_score: 27
-p0_count: 0
-p1_count: 2
-timestamp: 2026-07-22T15-58-15Z
-slug: apps-docs-src-components-workshop
----
-
-## Design Health Score
-
-| #         | Heuristic                       |     Score | Key Issue                                                                                                                                     |
-| --------- | ------------------------------- | --------: | --------------------------------------------------------------------------------------------------------------------------------------------- |
-| 1         | Visibility of System Status     |         3 | Strong loading, retry, stale-data, pending, and copy states; successful report/edit actions still end silently.                               |
-| 2         | Match System / Real World       |         3 | Core Workshop language is clear, but `networkScope`, query/action, and schema terminology assumes technical fluency.                          |
-| 3         | User Control and Freedom        |         3 | Back, cancel, clear filters, vote toggling, and destructive confirmations are present; destructive actions have no undo.                      |
-| 4         | Consistency and Standards       |         3 | Shared primitives are coherent, though Docusaurus chrome and the denser app-store vocabulary still feel slightly stitched together.           |
-| 5         | Error Prevention                |         2 | Validation and confirmations are good, but install safety and credential context appears after download/copy actions on small screens.        |
-| 6         | Recognition Rather Than Recall  |         3 | Author, revision, source, filters, and capabilities are visible; installation still asks users to remember a separate Homarr navigation path. |
-| 7         | Flexibility and Efficiency      |         2 | Search, filters, sort, drag-and-drop, autofill, and comment shortcuts help; the install handoff remains manual.                               |
-| 8         | Aesthetic and Minimalist Design |         2 | Hierarchy is clear, but repeated panels, badges, uppercase metadata labels, and overlapping install actions add noise.                        |
-| 9         | Error Recognition and Recovery  |         3 | Errors are plain-language and usually preserve work; the global action error can be detached from the failed control.                         |
-| 10        | Help and Documentation          |         3 | The installation guide and source explanation are useful; security terminology lacks inline definitions.                                      |
-| **Total** |                                 | **27/40** | **Acceptable, significant improvements needed**                                                                                               |
-
-## Anti-Patterns Verdict
-
-**LLM assessment:** Moderate AI-assisted feel, not outright slop. Domain-specific copy, extensive state coverage, and transparent source/capability information make the feature credible. The generic card grid, repeated rounded panels, icon tiles, uppercase tracked labels, and decorative changelog stripe still expose a component-recipe grammar. It looks competent but not fully edited into a distinctive Homarr store.
-
-**Deterministic scan:** `detect.mjs --json apps/docs/src/components/workshop` exited 0 with exact output `[]`: zero findings, zero triggered rules, and no false positives. The scan found none of Impeccable's deterministic anti-patterns.
-
-**Visual overlays:** No reliable user-visible overlay is available. The independent detector agent had no browser backend. The parent fallback opened a fresh browser tab and visually inspected the listing, but the browser API did not expose a mutable evaluation method for the required preflight, so injection and `[Human]` visibility were correctly skipped. Browser/source evidence was used instead.
-
-## Overall Impression
-
-The Workshop is already substantially better than a generic gallery: it communicates authorship, source code, API capabilities, secrets, revision history, reports, and discussion. The biggest opportunity is to turn that information into a deliberate trust sequence. Today the interface lets the user act first and understand safety later, especially on mobile.
-
-## What's Working
-
-- **State coverage is unusually strong.** Listing failures, stale data, loading skeletons, empty results, filter recovery, comment errors, pending actions, and destructive confirmations have explicit UI.
-- **Pre-install transparency is excellent.** API hosts, methods, configurable options, network scope, and credential requirements are visible instead of hidden behind a download.
-- **The new primitive layer is coherent.** Search, filters, menus, switches, dialogs, and code presentation share one restrained interaction vocabulary across light and dark themes.
-
-## Priority Issues
-
-### [P1] Safety context arrives after the install action on mobile
-
-**Why it matters:** Download and copy actions appear in the header, while source capabilities, credential requirements, and installation guidance live in an aside that drops below the long source and discussion sections under the desktop breakpoint. A first-time mobile user can commit before understanding what the widget contacts or what secrets it needs.
-
-**Fix:** Put a compact “Before you install” summary immediately below the header on small screens: API hosts, network scopes, credential count, and action/query counts. Keep the full sticky details panel on desktop.
-
-**Suggested command:** `$impeccable layout`
-
-### [P1] Primary button and own-comment contrast misses AA
-
-**Why it matters:** The requested theme's primary red with white foreground is about 3.4:1, below 4.5:1 for small text. The same pairing affects primary buttons and the author's comment bubbles.
-
-**Fix:** Darken the primary red or use a dark foreground in light mode, then verify default buttons and comment bubbles in both themes.
-
-**Suggested command:** `$impeccable colorize`
-
-### [P2] The listing's server-rendered fallback is blank
-
-**Why it matters:** Before hydration, the listing renders an empty block instead of preserving the page's hierarchy and indicating progress. This creates a visible dead zone on slower self-hosted deployments.
-
-**Fix:** Render the listing heading, toolbar silhouette, and shared skeleton cards as the `BrowserOnly` fallback, matching the detail page's loading treatment.
-
-**Suggested command:** `$impeccable harden`
-
-### [P2] Download, copy, source, and install compete for the same task
-
-**Why it matters:** “Download widget,” “Copy JSON,” a full source viewer, and a separate installation panel all appear as parallel paths. Users must infer the recommended workflow.
-
-**Fix:** Make “Download widget JSON” the single primary header action. Keep copy beside the source viewer and place the next import step directly beside or immediately after download.
-
-**Suggested command:** `$impeccable clarify`
-
-### [P2] Repeated metadata scaffolding creates visual noise
-
-**Why it matters:** Card shells, badges, icon tiles, uppercase tracked labels, and the changelog stripe make the detail page feel assembled from recipes and slow scanning.
-
-**Fix:** Flatten the widget details into a compact definition list, reserve badges for status, and remove the decorative changelog stripe.
-
-**Suggested command:** `$impeccable distill`
-
-## Persona Red Flags
-
-**Jordan, first-timer:** “Network scope,” queries, actions, options, and the manifest schema appear without inline explanation. Download versus copy has no stated recommendation. On mobile, credential and installation context arrives after source and discussion.
-
-**Sam, accessibility-dependent user:** Primary controls and author comment bubbles miss small-text contrast. Copy, optimistic votes, filter result changes, and successful report/edit completion do not expose explicit live-region behavior. Gallery controls and dots are below comfortable touch-target sizes.
-
-**Casey, distracted mobile user:** The most important safety panel falls to the bottom, while primary actions stay at the top. Long source and discussion content separate the decision from its explanation. The submit type selector remains dense at narrow widths.
-
-## Minor Observations
-
-- The internal installation guide uses an external-link icon.
-- The final publication action says “Submit” rather than “Publish submission.”
-- Dark-theme tokens are declared in two blocks, increasing drift risk.
-- Screenshot dots rely on opacity alone and lack `aria-current`.
-- Successful report and edit actions deserve a small confirmation instead of silent dismissal.
-
-## Questions to Consider
-
-- If source review is important enough to say “Review exactly what will be installed,” why can users download before seeing the capability and credential summary?
-- Is Workshop primarily a code catalog or a safety-conscious app store? The current action hierarchy tries to be both.
-- Should the successful end state be a downloaded file, or a confident handoff into Homarr with the next step already visible?

AGENTS.md

@@ -40,8 +40,6 @@ homarr/
 │   ├── analytics/       # Server-side analytics (Umami)
 │   ├── server-settings/ # Server setting keys/types
 │   ├── settings/        # User-facing settings UI context
-│   ├── old-import/      # Legacy Homarr import
-│   ├── old-schema/      # Legacy Homarr zod schemas
 │   └── cli/             # Node CLI for ops (brocli)
 ├── tooling/
 │   ├── typescript/      # Base tsconfig

CHANGES.md

@@ -1,96 +0,0 @@
-# Changes
-
-## Goal
-
-Remove widget-only services from Homarr's global Integration system.
-
-The affected services are release providers and Search.ch. They are only used by specific widgets, so keeping them as global integrations added unnecessary setup, UI, database rows, docs pages, and integration package code.
-
-ArchiveTeam Warrior remains a proper integration but is no longer auto-seeded on first install.
-
-## Why
-
-These services do not need shared integration state.
-
-- Release providers are selected per Releases widget repository.
-- Search.ch is only used by the Timetable widget.
-
-Moving them into widget options makes configuration simpler and removes dead-weight integration code from `packages/integrations`.
-
-## What Changed
-
-### Release Providers
-
-- Added release provider definitions in `packages/definitions/src/release-provider.ts`.
-- Removed release providers from `IntegrationKind`.
-- Moved release-fetching code out of `packages/integrations` and into `packages/request-handler/src/release-providers.ts`.
-- Updated the Releases widget to store provider configuration directly in widget options:
-  - `provider`
-  - `identifier`
-  - `versionFilter`
-  - `providerUrl`
-- Updated the Releases widget editor to use a provider select instead of an integration select.
-- Updated Docker import mapping so `ghcr.io` maps to `gitHubContainerRegistry`.
-- GitHub Container Registry now uses the public OCI registry API and accepts full image references such as `ghcr.io/homarr-labs/homarr:latest`.
-
-### Timetable / Search.ch
-
-- Removed Search.ch as an integration.
-- Added a Timetable widget `baseUrl` option, defaulting to `https://search.ch`.
-- Moved Search.ch request/parsing logic into `packages/request-handler/src/timetable.ts`.
-- Updated the Timetable API to receive `baseUrl` directly from widget options.
-
-### ArchiveTeam Warrior
-
-- Kept as a proper integration (not removed).
-- Removed `defaultUrl` from the integration definition to prevent auto-seeding on first install.
-
-### Integration Cleanup
-
-- Removed creators, exports, docs references, and implementation files for the deleted integrations.
-- Removed unused dependencies from `packages/integrations/package.json`.
-
-### Database Migration
-
-- Added `packages/db/migrations/custom/0003_remove_widget_only_integrations.ts`.
-- The migration moves old integration-linked widget config into widget options, then deletes the old widget-only integration rows.
-- Updated the earlier release widget migration to use the new `provider` field instead of `providerIntegrationId`.
-
-### Docs
-
-- Updated Releases widget docs to describe providers instead of integrations.
-- Updated Timetable docs to remove Search.ch integration setup.
-- Removed obsolete integration docs pages for the deleted integration kinds.
-- Updated docs sitemap and integration docs mappings.
-
-### Translations
-
-- Added English labels for the new widget options:
-  - `widget.timetable.option.baseUrl.label`
-  - `widget.releases.option.repositories.providerUrl.label`
-
-## How It Works Now
-
-Release provider configuration lives on each Releases widget repository entry. The request handler resolves provider metadata and fetches releases directly from the provider-specific endpoint. GHCR uses anonymous OCI registry access for public packages.
-
-Timetable passes its widget URL option directly to its API router and request handler. No global integration lookup is needed.
-
-ArchiveTeam Warrior continues to use the standard integration system, but users must manually add the integration (it is not auto-created on install).
-
-## Deliberate Non-Goals
-
-- No provider secret/token support was added.
-- No new secret storage model was introduced.
-- No compatibility layer was kept in `packages/integrations`.
-
-Widget options are client-visible, so storing provider credentials there would be wrong. If authenticated provider requests are needed later, they need a separate secret-storage design.
-
-## Verification So Far
-
-- Focused typechecks passed for affected packages.
-- Full `pnpm turbo typecheck` passed.
-- Full `pnpm lint` passed with existing warnings.
-- Focused release provider normalization tests passed.
-- Widget translation test passed.
-- Live GHCR smoke checks passed for `ghcr.io/muchobien/pocketbase:latest` and `ghcr.io/homarr-labs/homarr:latest`.
-- `pnpm test packages/integrations/test/pi-hole.spec.ts` passed earlier, but failed on rebased reruns because Pi-hole reported `domainsBeingBlocked` as `-2`/`0` instead of `> 1`.

MANTINE.md

@@ -54,7 +54,7 @@ For a single consolidated file with all content, use:
 - [How to integrate custom input with use-form hook?](https://mantine.dev/llms/q-custom-input-use-form.md): Learn how to add use-form support for custom inputs
 - [How to prevent Modal from closing?](https://mantine.dev/llms/q-how-to-prevent-modal-from-closing.md): Learn how to prevent Modal from closing when the user clicks outside of it or presses the Escape key
 - [How to scroll to the top of the form if the form is submitted with errors?](https://mantine.dev/llms/q-scroll-to-the-top-of-the-form.md): Learn how to call a function when the form is submitted with errors
-- [How to update Mantine dependencies?](https://mantine.dev/llms/q-how-to-update-dependencies.md): Learn how to update @mantine/_, @mantinex/_ and postcss-preset-mantine dependencies manually or with ncu script
+- [How to update Mantine dependencies?](https://mantine.dev/llms/q-how-to-update-dependencies.md): Learn how to update `@mantine/*`, `@mantinex/*` and `postcss-preset-mantine` dependencies manually or with ncu script
 - [How to use Dropzone with @mantine/form?](https://mantine.dev/llms/q-how-to-use-dropzone-with-form.md): Learn how to use Dropzone with @mantine/form to handle file selection state
 - [How to use Mantine template on GitHub?](https://mantine.dev/llms/q-templates-usage.md): Learn how to create a new repository based on Mantine template
 - [I get hydration warning about data-mantine-color-scheme attribute, what does it mean?](https://mantine.dev/llms/q-color-scheme-hydration-warning.md): Learn how hydration works and how to fix warnings

PRODUCT.md

@@ -1,39 +0,0 @@
-# Product
-
-## Register
-
-product
-
-## Users
-
-Homarr is for self-hosters and administrators who assemble dashboards for services across home labs and private infrastructure. They need dense, reliable controls and status at a glance, while retaining enough guidance to configure advanced features without hiding how they work.
-
-## Product Purpose
-
-Homarr provides one place to organize, observe, and operate self-hosted services. Success means users can build useful dashboards quickly, understand their state, recover from configuration errors, act on services, and reshape their workspace without repeatedly leaving the board. Boards must load immediately, stay visually stable, and keep widgets legible across screen sizes.
-
-## Brand Personality
-
-Direct, capable, precise, and approachable. Homarr should feel calm under load, be truthful about system state, and reward users who refine details.
-
-## Anti-references
-
-- Decorative dashboards, oversized metric cards, and motion without state meaning.
-- Wizard flows that fight ordinary scrolling or rigid layouts that force one workflow.
-- Hidden configuration magic and implementation complexity exposed before it is needed.
-- Clever custom controls where familiar platform or Mantine interactions already work.
-
-## Design Principles
-
-1. Keep configuration, consequences, and system state visible.
-2. Make simple tasks short without limiting advanced workflows.
-3. Preserve expert depth while prioritizing urgent information at small sizes.
-4. Reveal dense workspaces progressively through a consistent advanced focus mode.
-5. Isolate failures and show loading, stale, partial, empty, and failed states truthfully.
-6. Use the existing Mantine design language consistently across management and board surfaces.
-7. Keep spatial actions direct: moving, resizing, nesting, and using fixed rails happen on the canvas with immediate feedback.
-8. Preserve predictable widget composition with fixed logical tile sizes and horizontal scrolling before controls become inaccessible.
-
-## Accessibility & Inclusion
-
-Target WCAG 2.2 AA. Every pointer interaction needs a keyboard and coarse-pointer path. Support screen readers, visible and restored focus, sufficient contrast, reduced motion, non-color status cues, responsive layouts, actionable error messages, and keyboard equivalents for drag and resize operations.

REVIEW.md

@@ -1,263 +0,0 @@
-# PR #6502 widget-modernization ultra-review
-
-## Executive result
-
-**Merge recommendation: changes required.** No P0 was found, but the current branch still has five P1 issues: a pre-existing Custom API authorization/redirect weakness exposed by this subsystem review, an inaccessible manual advanced-focus interaction, a likely fixed-position/transform geometry defect, systemic false empty states for failed queries, and unvalidated integration-provided navigation URLs. Eight P2 issues cover raw error disclosure, unsafe runtime-ref interfaces, localization, responsive/theming drift, test coverage, and inaccurate PR copy.
-
-Audit health (Impeccable rubric): accessibility 1/4, performance 2/4, responsive design 2/4, theming 2/4, anti-patterns 3/4; **10/20 (Acceptable, significant work required)**. The UI does not look generically AI-generated; its problem is inconsistent technical behavior beneath an otherwise coherent Mantine vocabulary.
-
-## Reviewed revision and environment
-
-| Item                         | Value                                                                                          |
-| ---------------------------- | ---------------------------------------------------------------------------------------------- |
-| PR                           | #6502, `feat: modernize dashboard widgets`                                                     |
-| Reviewed head                | `96e92485a5fd45f3648cfac0453e614779c414ba`                                                     |
-| Base branch / fetched base   | `dev` / `d58a47b776a55d04dee2220f59d072b9af8bbed3`                                             |
-| Merge base                   | `d58a47b776a55d04dee2220f59d072b9af8bbed3`                                                     |
-| Diff                         | 359 files, +15,721/-4,478                                                                      |
-| PR state                     | open, non-draft, `BLOCKED`; no approval decision                                               |
-| Hosted checks at audit start | Fast gate, Container and E2E, CodeQL, JS/TS analysis, Actions analysis, title, auto-fix: green |
-| Inline threads               | 34 total, 7 unresolved; only 2 remain substantively valid                                      |
-| Mantine                      | repository lock: `@mantine/core`, hooks, charts and dates 9.4.1                                |
-| Local tools                  | Node 24.16.0 and pnpm 9.5.0; repository requires Node >=24.18.0 and pnpm >=11.15.1             |
-
-The former red baseline `7b7045202d289b7d83946befcee5d2845ea4a706` had a green Fast gate and a failed Container/E2E run (`30748255760`, job `91498308523`). The latest head has a green Container/E2E job (`30756067198`, job `91519039504`). This proves the current suite passed once; it does not satisfy the requested three-run flake characterization.
-
-## PR-description traceability
-
-| Claim                                                     | Result               | Evidence / correction                                                                                                                                                                                                                                      |
-| --------------------------------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| “all 54 widget renderers with compact and advanced modes” | **Inaccurate**       | 54 `WidgetKind` values exist. `displayMode="advanced"` reaches 53; `app` is deliberately excluded in `item-content.tsx:51` and documented as compact-only. Change copy to “53 widget renderers; app tiles remain compact,” or implement app advanced mode. |
-| advanced focus: hover, keyboard, touch, geometry          | **Partial**          | Entry paths, Escape ownership, reduced motion, close focus, touch button and zero-dimension guards exist. WID-002/003 remain.                                                                                                                              |
-| richer widget context actions                             | **Partial**          | `Menu.ContextMenu` is a good Mantine choice and query scope is item-aware. Dispatch still crosses `any`; Custom API action authorization is not represented.                                                                                               |
-| standardized query identity/cache/status                  | **Partial**          | Query keys, matchers, runtime capture, recovery and tests exist. Thirty-nine of 53 renderer query calls do not read errors; runtime ref registration is render-time mutable state.                                                                         |
-| safe polling                                              | **Mostly confirmed** | defaults are limited to `widget` namespace; Custom API resume immediately refetches; per-widget intervals exist. State/ref typing still needs redesign.                                                                                                    |
-| partial-failure rendering                                 | **Partial**          | settlement helper and several routers are strong; many renderer-level total failures still appear empty/disconnected.                                                                                                                                      |
-| bounded integration responses                             | **Mostly confirmed** | common bounded reader, Custom API 2 MiB, timetable 512 KiB, Traefik bounds and Beszel queue bounds exist. Custom action execution remains outside the hardened fetch path.                                                                                 |
-| timetable hardening                                       | **Confirmed**        | board/item permission checks, saved-value comparison, public-address resolution, private ranges, per-request DNS re-resolution, pinned dispatcher, redirect rejection, timeouts, response bounds and schemas are present.                                  |
-| precise placement                                         | **Mostly confirmed** | mouse, touch tolerance, keyboard, occupied-cell validation, dynamic bounds, nearest fit and immediate persistence exist. Failure/race/live responsive coverage remains insufficient.                                                                       |
-| widget catalog documentation                              | **Partial**          | all kinds have pages and shared interactions; wording overclaims focus behavior and validation counts are stale.                                                                                                                                           |
-| validation: 40 files/162 tests, 6/6 E2E                   | **Stale**            | current diff contains 57 changed unit-spec files (including three E2E specs); repository has 42 widget spec files and six E2E specs. Update from the exact final run.                                                                                      |
-| independent reviews “pass”                                | **Not supported**    | unresolved valid findings, current P1s, and unavailable live QA contradict an unqualified pass.                                                                                                                                                            |
-
-## Mantine suitability ledger
-
-Legend: **U** already used appropriately; **C** consolidation/replacement candidate; **R** relevant but current implementation can stay; **N** not relevant to widget runtime; **D** dependency/version addition. Exact 9.4.1 package archives were inspected in `/tmp`; live docs/Context7 include 9.5.0.
-
-### Core catalog
-
-- **U:** ActionIcon, Alert, Anchor, Avatar, Badge, Box, Button, Card, Center, Code, Divider, Flex, Grid, Group, Image, Loader, Menu (`Menu.ContextMenu`), Overlay, Paper, Popover, Portal, Progress, RingProgress, ScrollArea, SimpleGrid, Skeleton, Stack, Table, Tabs, Text, ThemeIcon, Title, Tooltip, UnstyledButton.
-- **C:** Accordion (dense integration sections), DataList (semantic label/value stats), EmptyState (replace bespoke empty state), FocusTrap and Modal compound API (WID-002), LoadingOverlay (background refetch without deleting content), NumberFormatter, OverflowList/Scroller (responsive action and chip rows), Table.ScrollContainer, Timeline (activity/feed histories), VisuallyHidden and Kbd, CloseButton, Dialog/HoverCard/Notification where persistent errors/actions need semantics.
-- **R:** Affix, AppShell, AspectRatio, BackgroundImage, Breadcrumbs, Burger, Checkbox, Chip, Collapse, ColorInput/ColorPicker/ColorSwatch/AlphaSlider/AngleSlider/HueSlider, Combobox/ComboboxPopover, Container, CopyButton, Drawer, Fieldset, FileButton/FileInput, FloatingIndicator/FloatingWindow, Highlight, Indicator, Input/JsonInput, List, Mark, Marquee, MaskInput, Menubar, MultiSelect/NativeSelect/NumberInput/PasswordInput/PillsInput/PinInput/Radio/RangeSlider/Rating/SegmentedControl/Select/Slider/Switch/TagsInput/Textarea/TextInput, Pagination, Pill, SemiCircleProgress, Space, Splitter, Spoiler, Stepper, Transition, Tree/TreeSelect, Typography. Use only where an existing widget requirement matches; do not churn working layouts.
-- **N:** Alpha/color/angle primitives outside configuration forms, AppShell/navigation primitives, TableOfContents, CorePackage documentation.
-- **D (9.5, not 9.4.1):** Cascader. **RollingNumber and Splitter are present in 9.4.1.**
-
-### Hooks catalog
-
-- **C:** `useFocusReturn`, `useFocusTrap`, `useReducedMotion`, `useRovingIndex`, `useLongPress`, `useScroller`, `useElementSize`, `useViewportSize`, `useHotkeys`, `useMediaQuery`, `useResizeObserver`.
-- **U/R:** focus-within, hover, disclosure, click-outside, merged-ref, interval/timeout, local-storage, event/window listeners, throttled/debounced values and list/set/map/state helpers are available in 9.4.1 and should replace local mechanics only when behavior and tests improve.
-- **N:** document title/favicon/hash/headroom/page-leave/OS/eye-dropper/fullscreen/network/orientation and other page-level utilities have no direct widget-remediation need. Every hook listed under `## Hooks` in `MANTINE.md` is covered by this rule; no hook requires 9.5 for the recommendations above.
-
-### Form, dates, charts, schedule, extensions, theme and styles
-
-- **Form:** existing `@homarr/form` should remain the abstraction over all cataloged form APIs. No widget-runtime replacement; use current validation/status APIs for widget editors (**R**).
-- **Dates:** all catalog entries are in installed 9.4.1 dates. `Calendar`, `MiniCalendar`, and `TimeValue` are candidates; other picker/input entries are editor-only (**R**). Importing dates directly into `@homarr/widgets` requires adding that workspace dependency (**D**).
-- **Charts:** 9.4.1 exports Area, Bar, BarsList, Bubble, Composite, Donut, Funnel, Heatmap, Line, Pie, Radar, RadialBar, Sankey, Scatter, Sparkline and Treemap (**C/R**). Prefer Sparkline for tiny trends, BarsList for ranked values, Heatmap for calendar/activity density, Composite for mixed analytics. **BulletChart and SunburstChart are 9.5-only (D)**. Replacement requires accessibility and bundle comparison, not blanket Recharts removal.
-- **Schedule:** all `AgendaView`, day/week/month/year/resource views and Schedule pages require new `@mantine/schedule` dependency (**D**). AgendaView is the only plausible calendar-widget candidate; its weight and semantics must beat the existing grouped list before adoption.
-- **Guides/FAQ/Other:** server components, portal testing, scroll lock, accessibility, nested popovers, zoom, responsive styling and version changelogs are relevant references (**R**); framework/setup/contribution/old migration entries are **N**. The 9.5 changelog is informational only.
-- **Theming/styles:** Colors, ColorSchemes, DefaultProps, MantineProvider, ThemeObject, CSS variables, data attributes, CSS Modules, responsive/RTL/style props/Styles API/performance are **U/R**. WID-009 requires shared layer/color tokens. Emotion, Sass, Vanilla Extract and unrelated global setup are **N**.
-- **Extensions:** existing modals, notifications, spotlight and rich-text abstractions are **U**; Carousel could consolidate Immich only after behavior parity; Dropzone/CodeHighlight/NProgress are **N** for this audit.
-
-## Complete 54-widget coverage matrix
-
-“Test” means a focused widget-local spec exists, not that all required states are covered. Every row still requires the common contract suite in WID-013.
-
-| WidgetKind                  | Family                  | Advanced    | Focused test | Principal audit gap                                        |
-| --------------------------- | ----------------------- | ----------- | ------------ | ---------------------------------------------------------- |
-| clock                       | basic                   | yes         | no           | query error, locale-format options                         |
-| weather                     | basic/feed              | yes         | yes          | query error; dayjs locale/time patterns                    |
-| app                         | basic/link              | **no**      | no           | PR wording; URL contract                                   |
-| iframe                      | custom content          | yes         | yes          | manual focus/iframe trapping; URL privacy thread now fixed |
-| video                       | custom content          | yes         | no           | media/focus/live behavior                                  |
-| notebook                    | notes                   | yes (inner) | yes          | editor focus inside manual surface                         |
-| anchorNote                  | notes                   | yes         | no           | query error, save/error regression                         |
-| dnsHoleSummary              | network                 | yes         | no           | total query error, hard-coded chart colors                 |
-| dnsHoleControls             | network/security        | yes         | no           | total error and permission matrix                          |
-| smartHome-entityState       | smart home              | yes         | no           | raw state in aria; action permissions                      |
-| smartHome-executeAutomation | smart home              | yes         | no           | mutation/permission/edit-mode E2E                          |
-| stockPrice                  | analytics               | yes         | yes          | total error                                                |
-| mediaServer                 | media                   | yes         | no           | total error and table a11y                                 |
-| calendar                    | calendar                | yes         | yes          | total error; fixed HH:mm; schedule tradeoff                |
-| downloads                   | media                   | yes         | yes          | four-state/component coverage, arbitrary z-index           |
-| mediaRequests-requestList   | media                   | yes         | no           | total error; external URLs/actions                         |
-| mediaRequests-requestStats  | media                   | yes         | no           | total error; links/colors                                  |
-| mediaTranscoding            | media                   | yes         | yes          | total error and responsive table                           |
-| mediaMissing                | media                   | yes         | yes          | total error and external URL                               |
-| minecraftServerStatus       | infrastructure          | yes         | no           | total error/malformed payload                              |
-| networkControllerSummary    | networking              | yes         | no           | total error; WAN/unknown localization                      |
-| networkControllerStatus     | networking              | yes         | no           | responsive rule duplication                                |
-| rssFeed                     | feed                    | yes         | yes          | strong stale/partial state; locale relative time           |
-| bookmarks                   | basic/link              | yes         | yes          | recomputation; URL contract                                |
-| indexerManager              | media                   | yes         | no           | total error; runtime action ref                            |
-| healthMonitoring            | infrastructure          | yes         | yes          | integration query error                                    |
-| releases                    | infrastructure/feed     | yes         | yes          | secret/item authorization needs E2E                        |
-| mediaReleases               | media                   | yes         | no           | total error; external URLs                                 |
-| dockerContainers            | infrastructure          | yes         | yes          | total error; z-index/table semantics                       |
-| firewall                    | networking/security     | yes         | yes          | partial-query matrix; loose router generics                |
-| notifications               | infrastructure          | yes         | no           | total error; untrusted href                                |
-| systemResources             | infrastructure          | yes         | yes          | total error; previous network thread fixed                 |
-| coolify                     | infrastructure          | yes         | yes          | total error; URL validation                                |
-| systemDisks                 | infrastructure          | yes         | yes          | total error                                                |
-| timetable                   | calendar                | yes         | no           | backend strong; component locale/live tests absent         |
-| immich-serverStats          | media                   | yes         | yes          | two ignored query errors                                   |
-| immich-albumCarousel        | media                   | yes         | yes (query)  | query error and nested overlay/focus E2E                   |
-| paperlessNgx                | analytics               | yes         | no           | former error thread fixed, no regression spec              |
-| patchmon                    | infrastructure          | yes         | yes          | total error                                                |
-| bazarr                      | media                   | yes         | yes          | total error                                                |
-| tracearr                    | analytics               | yes         | yes          | total error                                                |
-| speedtestTracker            | analytics               | yes         | yes          | total error                                                |
-| uptimeKuma                  | infrastructure          | yes         | yes          | total error                                                |
-| audioStats                  | media                   | yes         | yes          | good dual-error handling; partial-state tests needed       |
-| umami                       | analytics               | yes         | no           | runtime query registration; chart a11y                     |
-| vpn                         | networking/security     | yes         | no           | total error; status/permission matrix                      |
-| archiveTeamWarrior          | infrastructure          | yes         | yes          | suspense path; docs present                                |
-| ups                         | infrastructure          | yes         | no           | total error                                                |
-| beszelSystemTable           | monitoring              | yes         | yes          | nested chart/focus and live subscription                   |
-| beszelSystemGrid            | monitoring              | yes         | no           | live/error UI; no focused renderer test                    |
-| beszelAlerts                | monitoring              | yes         | no           | partial error and status semantics                         |
-| beszelSystemStats           | monitoring              | yes         | yes          | runtime refs, locale tooltip                               |
-| traefik                     | networking              | yes         | no           | total error; bounded backend positive                      |
-| customApi                   | custom content/security | yes         | yes          | WID-001/007/008; polling resume fixed                      |
-
-## Severity-ranked findings
-
-### WID-001 — P1 confirmed, pre-existing: Custom API actions lack resource authorization and hardened fetch policy
-
-- **Location/claim:** `packages/api/src/router/custom-widget/custom-widget-router.ts:57-102,392-451`; “harden Custom API” and action-permission semantics.
-- **Evidence/reproduction:** any authenticated account can call `customWidget.all`, learn every definition ID and URL, then call `customWidget.execute({definitionId})`. The mutation verifies neither board nor item nor an action permission. It decrypts administrator-provided secrets, uses `new URL()` only, and `redirect: "follow"`. The PR hardened `widget.customApi.getData`, but not this sibling execution path.
-- **Impact/rule:** unauthorized side effects against internal services and authenticated redirect chains; broken object-level authorization. A view-only account can invoke administrator-created controls outside any board context.
-- **Correction:** require `{boardId,itemId,definitionId}`; load the item and verify it is `customApi`, belongs to the board, references the definition, and the caller has an explicit execute policy. Until that policy exists, restrict to admin. Share `validateCustomApiUrl`, timeout, redirect rejection, bounded disposal and redacted errors with getData. Compatibility: old direct callers must send item/board context.
-- **Tests:** procedure tests for anonymous, unrelated authenticated, view-only, modifier, admin, mismatched item/definition, disabled definition, redirects, credential URL, timeout and secret non-disclosure; E2E action button across roles.
-
-### WID-002 — P1 confirmed, PR-introduced: manual advanced focus is not an accessible modal
-
-- **Location:** `advanced-focus/context.tsx:194-209`, `items/item-content.tsx:113-189`.
-- **Evidence:** manual mode renders an Overlay plus a `role="region"` Card. There is no FocusTrap, `aria-modal`, background inertness, scroll lock or backdrop dismissal. Only the close button is initially focused; Tab can leave the surface and activate dimmed board controls.
-- **Impact/rule:** keyboard/screen-reader users lose the interaction boundary; WCAG 2.1.2, 2.4.3 and ARIA dialog pattern. Iframes/editors make escape especially likely.
-- **Correction/Mantine:** render manual mode through `Modal.Root` compound parts (or ModalBase), using its portal, FocusTrap, scroll lock, Escape/return-focus and semantic content. Preserve preview mode as non-modal. Configure nested overlays and `removeScrollProps`; keep a 44px `Modal.CloseButton` and explicit title via VisuallyHidden if needed.
-- **Tests:** RTL portal/focus-cycle/return tests; Playwright Tab/Shift+Tab, nested Menu/Select/Popover/editor/iframe, backdrop and every close path; reduced motion and 200% zoom.
-
-### WID-003 — P1 probable, PR-introduced: fixed advanced surface remains under transformed Gridstack ancestry
-
-- **Location:** `advanced-focus.module.css:35-42`; Card remains inside the Gridstack item while only the backdrop is portaled.
-- **Evidence:** CSS fixed descendants establish their containing block at a transformed ancestor. Gridstack uses transforms for positioned items, so viewport-derived `left/top` can be interpreted relative to the item on affected layouts. A Portal wrapper exists only for Overlay.
-- **Impact:** off-screen, clipped or incorrectly scaled focus surface across breakpoints/remounts.
-- **Correction:** portal the focused surface itself (naturally achieved by WID-002) and calculate geometry in the same viewport coordinate system. Do not compensate with transform-specific offsets.
-- **Tests:** real Gridstack at every layout/viewport, scrolled page, header, dynamic section and resize/remount; assert bounding rect within viewport and finite scale.
-
-### WID-004 — P1 confirmed, regression-exposed/systemic: query failures still become valid empty/disconnected UI
-
-- **Location:** 39 of 53 renderer query calls do not read `error`, including bookmarks, weather, calendar, media server, system resources, Coolify, DNS Hole, Tracearr, notifications, Immich, VPN and others listed in the matrix. Query defaults do not set `throwOnError` (`trpc.tsx:69-93`).
-- **Evidence:** TanStack Query returns `data=undefined` on total failure. Components default to `[]`, `null`, or empty branches, so the board ErrorBoundary is never reached. Network Controller and Paperless were fixed, proving the pattern; it was not completed.
-- **Impact:** operators are told “empty” or “disconnected” when monitoring failed, violating the product’s truthful-state requirement.
-- **Correction/Mantine:** introduce a shared `WidgetQueryState` contract distinguishing initial Skeleton, background LoadingOverlay, stale Alert, partial warning, true EmptyState and terminal error. Either explicitly throw only when no usable cached data or render a shared error Alert. Preserve stale data.
-- **Tests:** parameterized contract tests for every queried widget: initial, success-empty, total failure, stale+failure, partial failure, refetch, remount/persisted cache and sibling isolation.
-
-### WID-005 — P1 confirmed, PR-introduced/systemic: integration-provided links bypass a shared URL policy
-
-- **Location:** examples include `media-missing/component.tsx:291`, `notifications/component.tsx:77`, media requests list/stats, Coolify resource/server links, releases, bookmarks and iframe. Only RSS and custom JSX visibly use explicit protocol sanitizers.
-- **Evidence:** dynamic strings are assigned directly to `href`/new-tab controls. Integration APIs and remote feeds are trust boundaries; no renderer-wide `http/https` guard is enforced.
-- **Impact:** unsafe schemes, credential-bearing URLs, internal detail disclosure and inconsistent opener behavior.
-- **Correction:** add one typed application URL helper returning a sanitized URL/undefined, with allowed schemes per use case, credential stripping/rejection, consistent `noopener noreferrer`, and disabled non-link presentation. Validate again server-side for action endpoints.
-- **Tests:** `javascript:`, `data:`, malformed, credential, relative, http/https and missing URLs for each shared link primitive.
-
-### WID-006 — P2 confirmed, PR-introduced: runtime query/action state mutates untyped refs during render
-
-- **Location:** `definition.ts:121-162`; runtime registration calls in media missing/transcoding, audio, calendar, Umami, Beszel and Immich; `widget-context-menu.tsx:157-174`.
-- **Evidence:** `setWidgetRuntimeQueries` mutates a shared object during render; concurrent/aborted renders can publish uncommitted query identity. Action dispatch casts the definition to `Record<string,unknown>` and `any`, then casts its result back.
-- **Correction:** make definition generics preserve kind/options/action types end-to-end; replace stringly opaque ref slots with a typed per-item registration API updated in a committed effect (or use `useSyncExternalStore`). Separate query registration from imperative actions.
-- **Tests:** StrictMode, interrupted/remount, options change and cleanup; compile-time `tsd`/type assertions rejecting wrong action props.
-
-### WID-007 — P2 confirmed, regression-exposed: raw backend errors are exposed to users and assistive text
-
-- **Location:** Custom API UI `component.tsx:561-576`; API `custom-api.ts:79-85`; several partial fallbacks use `error.message`.
-- **Impact:** internal hostnames, request paths and implementation details can appear in tooltips/aria labels and logs.
-- **Correction/Mantine:** return stable error codes plus redacted public messages; keep detailed causes server-side with correlation IDs. Render localized Alert/Notification details, never raw throwable text.
-- **Tests:** errors containing credentials, query strings, private hosts and multiline backend bodies must not reach tRPC payload, DOM, accessibility tree or notifications.
-
-### WID-008 — P2 confirmed, PR-introduced/regression-exposed: locale handling remains incomplete
-
-- **Locations:** Beszel chart/tooltip dayjs formats, calendar event `HH:mm`, downloads `YYYY-MM-DD HH:mm`, timetable `HH:mm:ss`, weather day/month/time formats; `_inputs/widget-location-input.tsx:199` hardcodes `Intl.NumberFormat("en")`.
-- **Also:** `beszel/_shared/disk-usage.tsx:41`, stats loading aria label, Network Controller `WAN`/`unknown` are English/raw accessible strings.
-- **Correction:** centralize app-locale date/time/number/duration/status helpers; load canonical dayjs locale only at the boundary; use localized translation keys for aria/status. NumberFormatter is suitable for simple display but application helpers should own locale.
-- **Tests:** at least `en-US`, `fr-FR`, `de-DE`, RTL locale, 12/24-hour preference and long translations, including accessibility names.
-
-### WID-009 — P2 confirmed: layer and color tokens are inconsistent
-
-- **Locations:** downloads z-index 1000 and rgba row colors; item title z-index 4; item menu/dynamic menu 10; media server white rgba; Indexer Manager hex colors; DNS Hole rgba palette; Umami hex tick colors.
-- **Correction:** define shared semantic layer tokens relative to Mantine CSS z-index variables and semantic status/chart tokens respecting light/dark/forced colors. Do not replace intentional service branding.
-- **Tests:** light/dark/forced-colors with nested overlays and tooltip ordering.
-
-### WID-010 — P2 confirmed: responsive decisions are duplicated and under-tested
-
-- **Location:** Network Controller Status `component.tsx:44,59-78` (open valid thread); Bookmark `component.tsx:94` recomputation (valid but low-impact thread); similar width/height literals across renderers.
-- **Correction:** small typed breakpoint lookup helpers per family, memoized only for genuinely expensive layout. Prefer container-query Grid/SimpleGrid where structural. Do not cargo-cult `useMemo` for a cheap pure calculation; benchmark Bookmark before accepting the review suggestion.
-- **Tests:** boundary tables for minimum/typical/wide/short/advanced sizes and 200% zoom.
-
-### WID-011 — P2 confirmed: PR/docs overstate behavior and validation
-
-- **Location:** PR body, board/getting-started copy “advanced preview in place,” validation numbers, and unqualified review pass.
-- **Correction:** state 53 advanced renderers plus compact-only app; call manual focus an overlay only after WID-002/003; publish exact final-SHA check/test counts and disclose unsupported/live-untested states.
-
-### WID-012 — P2 confirmed: focused automated coverage is far below the 54-widget/data-state claim
-
-- **Evidence:** 42 widget-local spec files are helper-heavy; 20+ renderers have no focused spec. Six E2E files exist, but only board interactions and Custom JSX directly exercise this modernization. The earlier Custom JSX login wait failed once and current exact-route wait remains.
-- **Correction:** add shared renderer contract harness plus family E2Es. Replace Custom JSX’s exact post-submit URL race with a shared login helper that waits for authenticated session/stable destination, then run it three times in CI.
-
-### WID-013 — P2 confirmed: open review-thread state no longer matches code
-
-| Thread                                      | Classification                                                      |
-| ------------------------------------------- | ------------------------------------------------------------------- |
-| iframe complete URL                         | already fixed/false positive at current line: only host is rendered |
-| system resources network gate               | already fixed, outdated                                             |
-| RSS total error                             | already fixed: no-data error throws; stale data retained            |
-| bookmarks memoization                       | valid P3/P2-low; benchmark first                                    |
-| network-controller total error              | already fixed, outdated                                             |
-| network-controller breakpoint consolidation | valid P2 maintainability                                            |
-| Paperless total error                       | already fixed, outdated                                             |
-
-Resolve the five stale threads with evidence; address or explicitly disposition the two live suggestions. Re-run review because CodeRabbit was paused during active development.
-
-## Systemic remediation roadmap
-
-1. **Security/authorization:** WID-001 and WID-005; add negative-role/protocol tests before merge.
-2. **Interaction accessibility:** replace manual focus with portaled Mantine modal semantics (WID-002/003), then test nested widget content.
-3. **Truthful data state:** build the shared query-state contract and migrate all 39 ambiguous sites; keep valid stale data and partial results.
-4. **Typed interfaces:** replace `widgetStateRef` slot mutation and `any` context dispatch with committed typed registrations.
-5. **Widget families:** media/downloads, infrastructure, networking/security, smart-home, analytics/calendar/feed, then Beszel; apply URL, state, locale, responsive and a11y contracts in that order.
-6. **Design-system cleanup:** semantic layers/colors and restrained Mantine consolidation. Do not add Schedule or upgrade to 9.5 without a separate dependency/bundle decision.
-7. **Docs/PR:** correct renderer count, behavior and exact validation evidence.
-8. **Final proof:** frozen install on supported Node/pnpm; format, lint, full typecheck, affected and full unit tests, production and docs builds; Custom JSX three times; complete production-container E2E; desktop/tablet/mobile keyboard/touch/light/dark/reduced-motion/zoom/a11y-tree QA. Push nothing until all refer to one unchanged SHA; close every review thread and obtain required approval.
-
-## Positive findings
-
-- Timetable is the strongest security work in the PR: saved resource authorization, private-range rejection, DNS rebinding resistance through pinned lookup, redirect rejection, bounds and schemas are coherently tested.
-- Bounded response helpers, Beszel bounded queue/cancellation, and partial-integration settlement materially reduce failure blast radius.
-- RSS preserves stale data and distinguishes partial feed failure; Network Controller and Paperless now correctly escalate total failures.
-- Item-scoped query matchers and tests address sibling-widget refresh isolation; global polling defaults are restricted to the widget namespace.
-- Touch long-press has movement tolerance; focus scale guards prevent Infinity/NaN; reduced-motion and remount cleanup are present.
-- Existing Homarr theme, Mantine components and shared UI vocabulary are generally preserved. Most proposed Mantine work is consolidation, not redesign.
-
-## Validation evidence and uncertainty
-
-- `MANTINE.md` was fetched from `https://mantine.dev/llms.txt` and passed byte-for-byte `cmp`; `llms-full.txt` stayed in `/tmp`.
-- Context7 current Mantine docs were queried for overlay/focus, responsive/data-state/accessibility, charts and Schedule. Static 9.4.1 archives verified exact exports; Cascader, BulletChart and SunburstChart are 9.5-only.
-- Local frozen install could not start because host Node/pnpm are below repository engine requirements. No dependencies, source files or machine toolchain were changed.
-- Docker API access is denied, so production-container E2E could not be rerun locally. Hosted exact-head Fast gate and Container/E2E are green.
-- `agent-browser` is not installed. Temporary `npx` execution was rejected by the environment’s security reviewer, so live exploratory QA/a11y-tree inspection was not performed.
-- External integrations were not available; malformed/partial/permission combinations are static-analysis conclusions unless a focused test already exists.
-- This review intentionally changes no production code and makes no commit, push, thread resolution or PR edit.
-
-Finalization must re-query the PR head/checks/threads. If the head differs from the reviewed SHA, this report is a snapshot and the delta requires review before merge.
-
-**Final refresh (2026-08-03):** head remained `96e92485a5fd45f3648cfac0453e614779c414ba`; all reported hosted checks remained successful; merge state remained `BLOCKED` with no approval decision; unresolved threads remained 7 of 34. The branch did not change during the audit.

apps/docs/blog/2024/09-23-version-1.0/index.mdx

@@ -13,8 +13,6 @@ This will be a one time occurrence and version > ``1.0`` will have less breaking
 This time more important than every; **read the breaking changes** list and **create a backup** before updating.
 Some third party installation methods may take multiple days or weeks to update to the new version.
 
-See [this guide on how to import your previous Homarr dashboard](/docs/getting-started/after-the-installation#importing-a-zip-from-version-before-100)
-
 ## Changes at a glance
 - **Asynchronous integrations system**: In versions prior to ``1.0``, we fetched data upon each request synchronously.
 This means that the user had to wait for the requests to finish so any data would appear.

apps/docs/blog/2025/01-19-migration-guide-1.0/index.mdx

@@ -10,12 +10,11 @@ If you are still on a version before 0.15.10, please update to 0.15.10 where we
 
 <!-- truncate -->
 
-## Export your data
+## Preserve your old installation
 
-As 1.0 is a complete rewrite of Homarr and therefor not compatible with the old docker mounts, we need to export your data first.
-For this you can navigate to the `Migrate to 1.0` page which you can find under `Management` > `Tools` > `Migrate to 1.0`.
-Here you can select which things you want to export and download the zip file.
-It will also show you a secret key which you will need to import the secret data like user password hashes, salts and integration secrets.
+Homarr 1.0 is a complete rewrite and cannot reuse the old Docker mounts. Keep the 0.15 installation and its data intact while you build the replacement. The historical `Management` > `Tools` > `Migrate to 1.0` export can still be kept as a record, but current Homarr releases cannot import that ZIP or its secret key.
+
+Plan to recreate your apps, integrations, and boards manually in the new installation. A SQLite database backup can be restored from the onboarding welcome screen only when it was created by a compatible current Homarr release; it is not a conversion path for a 0.15 database.
 
 ![Export page](./img/old-homarr-export-data.png)
 
@@ -28,28 +27,15 @@ Please note that if you are using docker you need to specify a diffrent external
 So in your compose file the ports would be `7576:7575` instead of `7575:7575`.
 
 ## Import your data
-Once the installation is completed you can access the new installation. During the onboarding you'll need to select `Import from Homarr before 1.0`.
 
-![Onboarding initial step](./img/onboarding-step-1.png)
+:::warning Legacy guide
 
-After that you can upload the zip file you downloaded in the first step.
+The pre-1.0 ZIP importer is no longer included in current Homarr releases. Keep the old installation available until you have manually verified the replacement. Compatible SQLite backups from current releases can still be restored from the onboarding welcome screen.
 
-![Onboarding import dropzone](./img/old-homarr-import-dropzone.png)
-
-After that you'll get a list with all your boards that can be imported. You can configure how it should be imported and can select which screensizes it should import.
-
-![Onboarding import list](./img/old-homarr-import-choose-imported-data.png)
-
-Once you have selected everything you can click on `Confirm import and continue` which will open the encryption key input dialog where you can input the secret key you got during the export.
-
-![Onboarding import key input](./img/old-homarr-import-decryption-token.png)
-
-After that you can continue the onboarding and you should see all your boards and data in the new installation.
-
-See [After the installation](https://homarr.dev/docs/getting-started/after-the-installation) for more information.
+:::
 
 ## Remove the old installation
 
 After you are happy with the new installation and everything is working as expected you can remove the old installation.
 Please make sure to backup the data before you remove the old installation.
-Also once the port 7575 is free again you can change the port mapping of the new installation to `7575:7575` if you want to.
+Also once the port 7575 is free again you can change the port mapping of the new installation to `7575:7575` if you want to.

apps/docs/docs/advanced/command-line/development/index.mdx

@@ -34,8 +34,10 @@ Images built by this CLI record their source checkout, revision, and optional pu
 ## Run images
 
 ```bash
+homarr --pr <number> --env HOMARR_WEBSITE_URL=https://app-v2.preview.homarr.dev/
 homarr run <name>
 homarr run --pr <number>
 ```
 
-Add `--detach` to run in the background, `--demo` to enable demo data, or repeat `--env KEY=VALUE` to provide additional environment variables.
+The direct `homarr --pr <number>` form is shorthand for `homarr run --pr <number>`. Add `--detach` to run in the
+background, `--demo` to enable demo data, or repeat `--env KEY=VALUE` to provide additional environment variables.

apps/docs/docs/advanced/environment-variables/index.mdx

@@ -35,7 +35,7 @@ Using the `PUID` and `PGID` will require you to set the correct permissions on t
 | `HOMARR_DISABLE_IPV6`    | Disables the IPv6 listener of the internal nginx proxy, even when the host supports IPv6. IPv6 is normally disabled automatically when the host has no IPv6 configured. See [#4596](https://github.com/homarr-labs/homarr/issues/4596) | `true` or `false`                   | `false`                       |
 | `HOMARR_WEBSITE_URL`     | Main Homarr documentation/site base used by runtime links. Must be an absolute HTTP(S) URL.                                                                                                                                            | HTTP(S) URL                         | `https://homarr.dev`          |
 | `WORKSHOP_API_URL`       | PocketBase API used by Homarr and standalone documentation.                                                                                                                                                                            | HTTP(S) URL                         | `HOMARR_WEBSITE_URL`          |
-| `WORKSHOP_WEB_URL`       | Public Workshop page opened from Homarr.                                                                                                                                                                                               | HTTP(S) URL                         | `HOMARR_WEBSITE_URL/workshop` |
+| `WORKSHOP_WEB_URL`       | Public Workshop website used by links in Homarr, Custom Widgets, onboarding, and assistant context.                                                                                                                                    | HTTP(S) URL                         | `HOMARR_WEBSITE_URL/workshop` |
 
 Workshop service operators can find its server-only configuration in the
 [Workshop operator guide](../../workshop/operator#environment-variables).

apps/docs/docs/advanced/keyboard-shortcuts/index.mdx

@@ -6,14 +6,37 @@ tags:
 
 Homarr has the following keyboard shortcuts:
 
-| Shortcut                                        | Description                                |
-| ----------------------------------------------- | ------------------------------------------ |
-| `MOD` + `K`                                     | Opens the search bar                       |
-| `MOD` + `J`                                     | Toggles Dark Mode                          |
-| `MOD` + `E`                                     | Toggles Edit Mode                          |
-| Hold `Shift` for 500 ms over a supported widget | Opens its temporary advanced view          |
-| `Shift` + `Enter` on a supported widget         | Opens its advanced view until it is closed |
-| `Esc`                                           | Closes an open advanced view or board menu |
+| Shortcut                                        | Description                                                                                                                |
+| ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `MOD` + `K`                                     | Opens the search bar                                                                                                       |
+| `MOD` + `J`                                     | Toggles Dark Mode                                                                                                          |
+| `MOD` + `E`                                     | Toggles Edit Mode                                                                                                          |
+| Hold `Shift` for 500 ms over a supported widget | Opens its temporary advanced view                                                                                          |
+| `Shift` + `Enter` on a supported widget         | Opens its advanced view until it is closed                                                                                 |
+| `Esc`                                           | Stops keyboard tile editing, cancels an active pointer or touch move/resize, or closes an open advanced view or board menu |
+
+## Widget advanced view
+
+Supported widgets open a temporary advanced view when you hold `Shift` over them for 500 ms. Focus a widget and press
+`Shift` + `Enter`, or use its menu, to keep the advanced view open.
+
+## Board editing
+
+`MOD` + `E` enters edit mode. Homarr keeps the current board visible while the editor prepares; movement and resizing become available when it is ready.
+
+When a tile is focused in edit mode:
+
+| Shortcut             | Description                                                                 |
+| -------------------- | --------------------------------------------------------------------------- |
+| `Enter` or `Space`   | Starts or stops keyboard editing                                            |
+| Arrow keys           | Moves the focused tile within its current canvas, rail, or Container        |
+| `Shift` + Arrow keys | Resizes from the tile's lower-right corner: Left/Up shrink; Right/Down grow |
+| `Esc`                | Stops keyboard editing without undoing its changes                          |
+
+Keyboard moves and resizes apply immediately. To move an item between a canvas, rail, or Container, drag it there or use **Move / resize item** for precise numeric placement.
+Commands at a grid boundary or at the tile's minimum size are ignored and announced instead of moving or shrinking the tile.
+
+On touch screens, press and hold a tile before moving it; a quick tap does not start a drag. Resize handles accept direct touch input. During a pointer or touch move or resize, `Esc` cancels the interaction and restores the layout from before it started.
 
 ## Board editing
 
@@ -33,9 +56,6 @@ Commands at a grid boundary or at the tile's minimum size are ignored and announ
 
 Here `MOD` refers to the modifier key, which is `Ctrl` on Windows and `Cmd` on macOS.
 
-Advanced view is available outside edit mode. Widgets without a distinct advanced experience adapt to their normal
-dimensions instead. A progress ring follows the pointer while the temporary advanced view is preparing to open.
-
 :::
 
 :::note

apps/docs/docs/advanced/styling/index.mdx

@@ -85,8 +85,8 @@ To do this, enter the board settings:
 
 ![](./img/enter-board-settings.png)
 
-Scroll down a bit and click on custom CSS.
-Here you can enter your CSS code, which will be applied on the respective board page.
+Scroll to the **Custom CSS** section on the board settings page. It is part of the unified settings form; enter your CSS
+there and save the board settings to apply it to that board.
 
 ![](./img/custom-css-setting.png)
 

apps/docs/docs/getting-started/after-the-installation.mdx

@@ -6,18 +6,16 @@ tags:
   - Configuration
 ---
 
-import imageStartFromScratchStepServerSettings from "./img/onboarding-from-scratch-step-server-settings.png";
-import imageStartFromScratchStepAdminUser from "./img/onboarding-from-scratch-step-admin-user.png";
-import imageStartFromScratchStepExternalAdminGroup from "./img/onboarding-from-scratch-step-external-admin-group.png";
-import imageStartFromScratchStepFinish from "./img/onboarding-from-scratch-step-finish.png";
-import manageBoardHeaderEditMode from "./img/manage-board-header-edit-mode.png";
-import manageBoardHeaderAddItem from "./img/manage-board-header-add-item-menu.png";
-import manageBoardHeaderChooseItem from "./img/manage-board-header-choose-item.png";
 import manageBoardNoApp from "./img/manage-board-no-app.png";
-import manageExportOldHomarr from "./img/old-homarr-export-data.png";
-import manageImportOldHomarrDropzone from "./img/old-homarr-import-dropzone.png";
-import manageImportOldHomarrChooseData from "./img/old-homarr-import-choose-imported-data.png";
-import manageImportDecryptionToken from "./img/old-homarr-import-decryption-token.png";
+import currentKeyboardTileEditing from "../management/boards/img/keyboard-tile-editing.png";
+import boardDesktopCurrent from "./img/onboarding-board-desktop-current.png";
+import boardEditModeCurrent from "./img/onboarding-board-edit-mode-current.png";
+import addContentMenuCurrent from "./img/onboarding-add-content-menu-current.png";
+import chooseItemCurrent from "./img/onboarding-choose-item-current.png";
+import editItemCurrent from "./img/onboarding-edit-item-current.png";
+import boardsHomeMobileMenu from "./img/onboarding-boards-home-mobile-menu.png";
+import moveResizeMenuCurrent from "./img/onboarding-move-resize-menu-current.png";
+import currentBoardMobileView from "./img/onboarding-board-mobile-current.png";
 
 :::tip
 
@@ -29,117 +27,50 @@ Congratulations on installing Homarr. Now it's time to get yourself familiar wit
 
 ## Onboarding
 
-The onboard will show the first time you start Homarr.
-This process will help you with your first steps and adding some initial data, such as the administrator account.
+Onboarding appears the first time Homarr starts. Its goal is to create a useful responsive board, not merely an
+administrator account. The setup uses one guided studio, so you can keep the safe defaults and finish quickly or review
+every detected service before anything is added to the board.
 
 :::note
 
-If you see this screen repeatitly after you restarted the Homarr container, your Docker mounting paths may be missing,
+If you see this screen repeatedly after restarting the Homarr container, your Docker mounting paths may be missing,
 incorrect or read-only. Read [our installation instructions](/docs/getting-started/installation/docker) again to fix this issue.
 
 :::
 
-You can either import a previous dashboard using the ZIP archive or start from scratch:
+### Restore or start fresh
 
-![Screenshot of Step 1 onboarding](./img/onboarding-step-1.png)
+SQLite installations can restore a complete Homarr database backup from the welcome screen. This restores current
+boards, people, apps, integrations, and settings. The pre-1.0 ZIP importer is no longer included.
 
-You may refresh anytime and continue from a different device - the onboarding is saved immediately on the server for your convenience.
+For a new installation, Homarr first creates either a credentials administrator or an administrator group matching your
+LDAP/OIDC provider. The browser that starts setup claims the first-run session; refreshes are safe, while another browser
+cannot change credentials or integrations during that setup.
 
-### Starting from scratch
+### Setup studio
 
-Depending on your auth provider configuration you will either first see the admin user creation form or the external group creation form.
-If the credentials provider was selected, you'll be prompted to create an admin user for Homarr.
-This user cannot be deleted and has full control over Homarr and all of its boards.
-You must choose a username and password (both can later be changed).
-We enforce strict password requirements when you enter your password to protect your instance if you accidentally
-expose it to the internet.
+The studio keeps related choices together:
 
-<img src={imageStartFromScratchStepAdminUser} alt={"Screenshot form to create admin user"} width={300} />
+1. **Essentials** sets the default language, color scheme, analytics preference, and the usual host, IP address, domain, or reverse-proxy path used by your services. URL suggestions can use separate ports, subdomains, or one path per service.
+2. **Discover** checks the actual database, Docker-compatible sockets, Kubernetes configuration, Workshop, and Assistant capabilities. Unavailable sources never block manual setup.
+3. **Connect** shows detected integrations and apps first, identifying whether each app came from an explicit [`homarr.*` or Homepage Docker label](/docs/integrations/docker-labels) or image matching. Select several integrations and apps at once, review every URL, and use the service-specific link to open its API-key settings when one is available. If a container has no published port or URL label, add its HTTP or HTTPS address before importing it.
+4. **Board** previews the Base layout, colors, widget radius, sidebars, selected apps, and widgets inferred from integrations or Docker labels. Choose 8 columns for a focused board, 10 for a balanced board, 12 for a wide board, or use the slider for a custom width up to 24 columns. Homarr still creates and reflows the protected Mobile layout automatically. A fast setup adds the integration-free Clock, Weather, and Bookmarks starter widgets.
+5. **Extend** explains and optionally configures Homarr Assistant, the community Workshop, and the separate Homarr MCP endpoint.
+6. **Review** tests the selected connections, then saves integrations, apps, widgets, settings, and the exact first board together. If any part fails, the database changes are rolled back and your form stays available to correct.
 
-If you selected external providers (such as LDAP or OIDC), you'll be prompted to create an admin group.
-This group will be used to synchronize users from your provider to Homarr.
-When a user logs in through the provider, any of their groups that match groups in Homarr will be assigned to the user.
-The name of the group must match exactly the name of the group in the provider.
+Docker discovery reports each configured host separately. Results from reachable hosts remain selectable if another socket
+is unavailable, which is useful for remote Docker, rootless Docker, Synology, and mixed deployments. On Kubernetes or
+bare-metal installations without a Docker socket, enter services manually and use the same integration catalog.
 
-<img
-  src={imageStartFromScratchStepExternalAdminGroup}
-  alt={"Screenshot form to create external admin group"}
-  width={300}
-/>
+After setup, **Open my board** takes you directly to the configured board. The in-product tour then introduces edit mode,
+responsive layouts, widgets, and search without delaying completion.
 
-Next, you can configure some basic settings for Homarr. We recommend to leave all settings at default for most users.
-Here you can also disable analytics. Please note that our analytics are completly anonymous and is fully compliant with GDPR and PECR.
-
-<img
-  src={imageStartFromScratchStepServerSettings}
-  alt={"Screenshot of analytics and indexing settings in the onboarding"}
-  width={300}
-/>
-
-### Setting up integrations
-
-After configuring server settings, the onboarding guides you through setting up your integrations.
-
-#### Docker service discovery
-
-If Docker is available (socket mounted), Homarr automatically detects running containers and matches them to known integration types.
-Matching integrations are pre-selected in the integration list, saving you from manually picking each one.
-
-#### URL templating
-
-You can define a base URL template to auto-fill integration URLs in bulk.
-Two modes are supported:
-
-- **Subdomain mode** - e.g. `{app}.example.com` where `{app}` is replaced with the integration name
-- **Port mode** - e.g. `192.168.1.1:{port}` where `{port}` is replaced with the integration's default port
-
-#### API key helper links
-
-For integrations that require API keys (such as Sonarr, Radarr, SABnzbd, or Seerr), a helper link opens the relevant settings page in the target application so you can quickly copy your key.
-
-#### Creating apps from Docker containers
-
-You can optionally auto-create bookmark apps for all discovered Docker containers, making them immediately available on your board.
-
-:::note
-
-Release providers and Search.ch are configured directly in their widgets instead of the integrations page.
-
-:::
-
-After this step, you finished the onboarding.
-The onboarding can no longer be started again.
-From here you can click on one of the provided links to continue your journey.
-We recommend you to continue with the section [creating your first board on this page](#creating-your-first-board).
-
-<img src={imageStartFromScratchStepFinish} alt={"Screenshot of the finish onboarding process with links"} width={300} />
-
-### Importing a ZIP from version before 1.0.0
-
-This is recommended when you used Homarr before and want to re-import your data.
-It is important that you first migrate correctly using [the list of breaking changes for 1.0](/blog/2024/09/23/version-1.0).
-
-<img src={manageExportOldHomarr} alt="Export from old Homarr" style={{ maxWidth: 500 }} />
-
-**How to export and import data**
-
-1. Navigate to your old Homarr, open your management pages, open the tools submenu and open `Migrate to 1.0`.
-2. Check the contents that you want to export. We recommend you to export all data.
-3. Click on the export data button
-4. Save the ZIP file, that is being downloaded, on your device. If you selected "integrations" or "users", you also get an encryption / decryption key.
-   Copy it and do not loose it!
-5. Go to your new >1.0.0 Homarr instance and start the onboarding. Choose `Import from Homarr before 1.0`
-6. Drag and drop your previously downloaded ZIP archive into the file upload: <br/><img src={manageImportOldHomarrDropzone} style={{ maxWidth: 500 }} />
-7. Next, choose the data that you want to import and how to import it. Since screen sizes were removed in 1.0, we create a new board for every screen size by default. We recommend you to only keep the best layout and adjust it later in 1.0.0 - but you can also import all of them and pick later.<br/><img src={manageImportOldHomarrChooseData} style={{ maxWidth: 500 }} />
-8. If you previously exported integrations or users, you will be asked to decrypt the data safely using your obtained encryption token. Paste into the modal and confirm your action.<br/><img src={manageImportDecryptionToken} style={{ maxWidth: 500 }} />
-9. Next, you can [follow the same setup as when starting from scratch](#starting-from-scratch). After you completed the onboarding, all of your data will be migrated and available.
-
-## Creating your first board
+## Creating another board
 
 In Homarr, you organize your apps and widgets on boards.
 Boards use fixed-size tiles so the same widget keeps the same proportions on every screen.
 Drag, resize, and section controls are available in edit mode.
-Let's create your first board by navigating here: `Manage` > `Boards` > `New board`:
+Onboarding already created the first board. To create another one, navigate to `Manage` > `Boards` > `New board`:
 ![](./img/manage-create-board-button.png)
 
 A board must always have a name and can either be public or private.
@@ -147,9 +78,25 @@ Public boards are also accessible for users, that are not logged in ([see access
 
 ![](./img/manage-create-board-modal.png)
 
-Congratulations - you've just created your first board. You can see boards, that you have access to, on this page:
+Congratulations - you've just created another board. You can see the boards you have access to on this page:
 
-![](./img/manage-view-board.png)
+<figure>
+  <img
+    src={boardsHomeMobileMenu}
+    alt="Boards management page showing a Home badge and separate desktop and mobile home-board menu entries"
+    style={{ maxWidth: "100%" }}
+  />
+  <figcaption>The Boards page selects the board opened from Home separately for desktop and mobile.</figcaption>
+</figure>
+
+The board marked **Home** is the board opened from the desktop Home route. **Set as your mobile board** selects which board
+opens on phones. This is separate from the **Mobile** layout: the home-board setting chooses a board, while **Mobile** and
+**Base** are responsive layouts inside that board. A phone can therefore open a different home board and still use that
+board's Mobile layout.
+
+New boards start with **Mobile** and **Base** responsive layouts automatically, so you can edit the board for phones and
+desktops without creating extra layouts first. Mobile starts at `0px` with 3 columns and Base at `768px` with 10 columns.
+Each layout keeps its own tile positions and sizes.
 
 ## Add your first app to Homarr
 
@@ -173,37 +120,63 @@ After you created the app, you'll see in on the apps page:
 Let's add your freshly created app, from the previous step, to the board.
 To do this, edit your previously created board by clicking on the big `Open board` button:
 
-![](./img/manage-view-board.png)
+<figure>
+  <img src={boardDesktopCurrent} alt="Current Homarr board opened from the Boards page" style={{ maxWidth: "100%" }} />
+  <figcaption>Open a board to view its dashboard, then enter edit mode to arrange its content.</figcaption>
+</figure>
 
 Here you have the following options in the header:
 
 ![](./img/manage-board-header.png)
 
 - **Search**: Here you can search for data. You can search for integrations, boards, actions, sites and much more. Some actions may be context dependent (eg. will only show when certain widgets are on your page)
-- **Edit mode**: Clicking this button will toggle the edit mode. In this mode you can edit the contents of your board.
+- **Edit board**: Clicking this button will toggle edit mode. In this mode you can edit the contents of your board.
 - **Settings**: Clicking this button will redirect you to a settings page where you can adjust the board settings (page title, colors, ...).
+- **Board switcher**: Use this button to open another board that you can access.
 - **Profile**: This avatar will be visible on every page. Clicking it will show a menu with actions.
 
 When entering the edit mode, you'll get some additional buttons to work with:
 
-<img src={manageBoardHeaderEditMode} alt={"Screenshot of buttons in the edit mode"} width={200} />
+<figure>
+  <img
+    src={boardEditModeCurrent}
+    alt="Current Homarr board editor with tile controls visible"
+    style={{ maxWidth: "100%" }}
+  />
+  <figcaption>The current editor keeps the board visible while its editing controls are available.</figcaption>
+</figure>
 
-- **Add item**: Click this button to add new elements to your page.
-- **Exit edit mode**: Click this button to save your changes and exit edit mode.
+- **Add board content**: Click this button to create a new item, app, integration, or Container.
+- **Save board**: Click this button to save your changes and leave edit mode. If you leave with unsaved changes, Homarr asks whether to discard them.
 
 Outside edit mode, right-click a widget for its live status, refresh, settings, quick options, and supported actions.
 Hold `Shift` while hovering a widget that supports advanced view to expand it in place while the rest of the board
 stays visible but dimmed. Release `Shift` to close it. You can also focus that widget and press `Shift` + `Enter` to
 keep its advanced view open until you close it. Widgets without a distinct advanced experience adapt in place.
 
-To continue, click the option "New Item":
+To continue, click **New item** in the add-content menu. New content is placed at the first available position on the main
+canvas; it is not inserted at a clicked empty cell or directly into a rail or Container:
 
-<img src={manageBoardHeaderAddItem} alt={"Screenshot of the add item menu"} width={200} />
+<figure>
+  <img
+    src={addContentMenuCurrent}
+    alt="Current add board content menu with item, app, integration, and Container actions"
+    style={{ maxWidth: "100%" }}
+  />
+  <figcaption>The add-content menu provides the four supported ways to place new content on the board.</figcaption>
+</figure>
 
 Next, you can choose what item you'd like to add.
 We will discuss the other options in the following sections - for now choose "App" to continue.
 
-<img src={manageBoardHeaderChooseItem} alt={"Screenshot of choosing the app item in the modal"} width={300} />
+<figure>
+  <img
+    src={chooseItemCurrent}
+    alt="Current item picker showing the App card and other item types"
+    style={{ maxWidth: "100%" }}
+  />
+  <figcaption>Choose the App item from the current picker to add an app tile.</figcaption>
+</figure>
 
 As soon as you chose the app, the modal will close and you'll get the following item on your board:
 
@@ -212,31 +185,52 @@ As soon as you chose the app, the modal will close and you'll get the following
 This is expected, because you haven't told Homarr what app it should show in this item.
 To configure this, click on the small 3 dots at the top of the item in the edit mode and choose "Edit item" in the menu.
 
-![](./img/manage-board-edit-app.gif)
+<figure>
+  <img
+    src={moveResizeMenuCurrent}
+    alt="Current board tile menu showing Edit item and Move or resize item"
+    style={{ maxWidth: "450px" }}
+  />
+  <figcaption>The tile menu contains the item editor and the separate move-and-resize tools.</figcaption>
+</figure>
 
 In the modal you can edit the app that you want to display:
 
-![](./img/manage-board-choose-app.png)
+<figure>
+  <img src={editItemCurrent} alt="Current Edit item modal for an App tile" style={{ maxWidth: "620px" }} />
+  <figcaption>Use the Edit item modal to choose the app and configure how its tile is displayed.</figcaption>
+</figure>
 
 As soon as you save your changes, the tile on the board will refresh and display your app.
-Use the resize handle at the bottom right to resize the tile.
-Press and hold the handle, move the pointer, and release it when the tile has the size you want.
+Resize from any visible edge or corner handle. For a Container, activate its top-left grip before using its resize handles.
+Press and hold a handle, move the pointer, and release it when the tile has the size you want.
 
-![](./img/resize-item.gif)
-
-To move a tile in edit mode, press and hold its content, move it to the desired position, and release it.
+To move a tile in edit mode, press and hold its inert content area, move it to the desired position, and release it.
 Widget content is disabled while editing so its controls do not intercept the drag; use the tile's settings button for edit actions.
-The tile snaps to the grid. Equally-sized tiles swap when one is dropped into the other's slot, while other neighboring tiles move out of the way automatically.
-
-![](./img/move-item.gif)
+The tile snaps to the grid. A single compatible collision may swap the two items when both resulting placements fit;
+otherwise the collision chain reflows neighboring tiles automatically.
 
 Every `1 × 1` tile has a logical content size of `200 × 200` pixels.
 Larger tiles use multiples of that fixed unit, with a consistent gap between cells.
 Homarr scales the complete board uniformly, like zooming a page.
-The complete canvas always fits the available width without horizontal board scrolling.
-Below 100%, Homarr preserves the widget's readable typography and control density instead of shrinking each widget independently.
+The complete canvas always fits the available width without horizontal board scrolling. Below 100%, Homarr preserves the
+widget's readable typography and control density instead of shrinking each widget independently.
 It does not squeeze or reflow the content of individual widgets, so a widget keeps the same design and proportions across screen sizes.
 
+On a narrow screen, Homarr uses the **Mobile layout** for the selected board and stacks the board content vertically while
+preserving each widget's fixed logical proportions:
+
+<figure>
+  <img
+    src={currentBoardMobileView}
+    alt="Homarr's Mobile layout in a 390-pixel-wide viewport, with tiles scaled to fit and stacked vertically"
+    style={{ maxWidth: "390px" }}
+  />
+  <figcaption>
+    At phone width, the selected board uses its Mobile layout and fits the complete canvas to the viewport.
+  </figcaption>
+</figure>
+
 :::note
 
 Viewing a board initially uses the lightweight, non-interactive layout.
@@ -252,16 +246,17 @@ This helps you to explore the capabilities of Homarr before you build your board
 
 :::
 
-Keyboard users can focus a tile, press Enter or Space, then use arrow keys to move and Shift plus arrow keys to resize.
-Press Escape to stop.
-For precise numeric controls or touch input, choose **Move / resize item** from the tile's edit menu.
-The dialog can also move the tile to another section or fixed sidebar:
+Keyboard users can focus a tile, press Enter or Space, then use arrow keys to move and Shift plus arrow keys to resize
+within its current canvas, rail, or Container. Press Escape to stop keyboard editing. Touch dragging starts after a short
+hold of about `200 ms`; resize handles accept direct touch input. During a pointer or touch move or resize, press Escape
+to cancel and restore the previous layout. For cross-grid moves or precise numeric controls, choose **Move / resize item**
+from the tile's edit menu.
+Keyboard commands at a grid boundary or minimum tile size are ignored and announced; they do not move or shrink the tile.
 
-![](./img/manage-board-move-resize-item-menu.png)
+<img src={currentKeyboardTileEditing} alt="A board tile focused for keyboard editing" style={{ maxWidth: "100%" }} />
 
-Be sure to save your changes by exiting edit mode!
-
-![](./img/exit-edit-mode.png)
+Open **Move / resize item** from the tile menu to move the tile to another section or rail and enter precise numeric
+coordinates and dimensions. After making changes, click **Save board** to persist them and leave edit mode.
 
 ## Adding your first integration
 
@@ -296,7 +291,14 @@ Let's add your integration, that you have configured in the section above, as a
 First, navigate back to your board that you want to add it to.
 Next, enter edit mode again and add another item to your board:
 
-![](./img/manage-board-header-add-item-menu.png)
+<figure>
+  <img
+    src={addContentMenuCurrent}
+    alt="Current add board content menu with item, app, integration, and Container actions"
+    style={{ maxWidth: "100%" }}
+  />
+  <figcaption>Use the same add-content menu to place an integration widget on the board.</figcaption>
+</figure>
 
 Instead of choosing an app, let's choose `System Health Monitoring` this time.
 Click on "Add to board":
@@ -323,9 +325,7 @@ Editing a widget will trigger a data update and data will soon appear:
 
 ![](./img/widget-system-health.png)
 
-As with every change, don't forget to save your changes using the exit edit mode button:
-
-![](./img/exit-edit-mode.png)
+As with every change, click **Save board** to persist your board changes and leave edit mode.
 
 ## Organizing items with Containers
 
@@ -338,7 +338,7 @@ Each Container can configure:
 - Show or hide **Open all in new tabs**.
 - Change its border color and custom CSS classes.
 
-Open the add-content menu and choose **New Container**.
+Open the add-content menu and choose **New container**.
 In edit mode, move and resize it like any other item, then drag items into or out of it.
 Nested content stays within the Container's bounds.
 While resizing, the solid outline follows the pointer continuously and the dashed grid preview shows the size that will be saved on release.

apps/docs/docs/integrations/docker-labels/index.mdx

@@ -0,0 +1,95 @@
+---
+title: "Docker labels"
+description: "Discover apps, integrations, and widgets from container labels during Homarr onboarding."
+---
+
+# Docker label discovery
+
+During onboarding, Homarr scans running containers on every reachable
+[Docker-compatible host](/docs/integrations/docker). Labels let you provide exact app metadata instead of relying on
+image-name matching. You can review and deselect every result before Homarr creates anything.
+
+A container with valid Homarr labels takes priority over image-based discovery. Containers without valid labels can
+still be suggested from their image and published ports.
+
+## Homarr labels
+
+`homarr.name` and `homarr.href` are required for label discovery. All other labels are optional.
+
+| Label                | Purpose                                                                    |
+| -------------------- | -------------------------------------------------------------------------- |
+| `homarr.name`        | App or integration display name                                            |
+| `homarr.href`        | Address opened by the app and used as the suggested integration address    |
+| `homarr.group`       | Container section that receives the selected app and compatible widget     |
+| `homarr.icon`        | App icon URL                                                               |
+| `homarr.description` | App description                                                            |
+| `homarr.ping`        | Address used for app status checks                                         |
+| `homarr.id`          | Stable source identifier; defaults to the Docker container ID              |
+| `homarr.board`       | Intended board name; see [Board targeting](#board-targeting)               |
+| `homarr.integration` | Homarr integration kind, for example `sonarr`                              |
+| `homarr.widget`      | Homarr widget kind to add when it supports the selected integration        |
+| `homarr.hide`        | Excludes the container when this label is present, regardless of its value |
+
+Unknown integration and widget kinds are ignored. Do not put API keys, passwords, or other secrets in labels. Enter
+credentials in onboarding, where Homarr stores them using its normal encrypted integration-secret flow.
+
+## Compose example
+
+```yaml
+services:
+  sonarr:
+    image: lscr.io/linuxserver/sonarr:latest
+    labels:
+      homarr.name: "Sonarr"
+      homarr.href: "http://server.local:8989"
+      homarr.group: "Media"
+      homarr.icon: "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/svg/sonarr.svg"
+      homarr.description: "TV library"
+      homarr.ping: "http://server.local:8989"
+      homarr.integration: "sonarr"
+      homarr.widget: "calendar"
+```
+
+Use an address that is reachable where it is needed. A Docker service name can work for server-side integration
+requests, while an app link opened in a browser usually needs a LAN hostname, IP address, or reverse-proxy address.
+Onboarding accepts these self-hosted address formats directly and only requires the field to be non-empty.
+
+## Homepage label fallback
+
+When `homarr.name` is absent, onboarding also understands these Homepage labels:
+
+- `homepage.name`
+- `homepage.href`
+- `homepage.group`
+- `homepage.icon`
+- `homepage.description`
+
+`homepage.name` and `homepage.href` are required for the fallback. Homarr does not combine partial Homarr metadata with
+Homepage metadata: once `homarr.name` is present, use `homarr.*` labels for the remaining fields too.
+
+## What onboarding creates
+
+In **Connect**, label-discovered apps and integrations appear before image-based suggestions. You can import multiple
+services in one pass and edit every suggested address. For image-matched apps, Homarr uses the detected service type
+when building host, subdomain, or reverse-proxy path suggestions.
+
+When setup completes, Homarr rechecks the selected container sources and then:
+
+- creates an app with its name, address, icon, description, and ping address;
+- creates the requested integration and links its app after you provide required credentials;
+- places grouped apps in a board container named by `homarr.group`;
+- places ungrouped apps in the main board area;
+- adds `homarr.widget` only when the widget kind is valid and compatible with the selected integration;
+- keeps image-based discovery available for unlabeled containers.
+
+If a selected container disappears, targets another board, or requests an incompatible widget, setup finishes with a
+warning instead of creating an invalid board item.
+
+## Board targeting
+
+On a fresh installation with one seeded `dashboard` board, one unique selected `homarr.board` value can name that first
+board. Otherwise, the label must match the board selected in onboarding. Services labeled for another board are skipped
+and reported in the completion warning.
+
+Onboarding configures one board at a time. Run normal board management after setup if you want to distribute services
+across several boards.

apps/docs/docs/integrations/docker/index.mdx

@@ -160,11 +160,13 @@ They are then available in the app list and can be used as normally added apps.
 
 ![Apps added from containers](img/add-to-homarr-apps.png)
 
-### Configuration
+### Container labels
 
-Currently Homarr supports one label for configuration of the containers:
+`homarr.hide` excludes a container from the Docker Containers widget, tools page, and onboarding discovery whenever the
+label is present.
 
-- **homarr.hide:** If set to any value, the container will be hidden from the Docker Containers widget and tools page.
+During first-run onboarding, Homarr can also discover apps, integrations, groups, and compatible widgets from
+`homarr.*` labels, with Homepage labels as a fallback. See the complete [Docker label reference](/docs/integrations/docker-labels).
 
 ### Security
 

apps/docs/docs/management/api/index.mdx

@@ -93,6 +93,10 @@ an optional `error` on a failed integration; media-request responses expose a `f
 requests endpoint returns its items in `requests`. When every selected integration fails, the query returns an error instead
 of a partial response.
 
+Other widgets use the same settlement pattern with endpoint-specific shapes: a failed integration may appear as a named
+fallback row, in a failure array, or be omitted while healthy results remain. Widget pages should identify the shape they
+render rather than assuming every query exposes an `error` field.
+
 ### Saving dashboard layouts
 
 The dashboard editor saves item positions and sections as one board update.

apps/docs/docs/management/apps/index.mdx

@@ -51,6 +51,6 @@ Note that the ping URL only accepts `http://` and `https://` URLs — custom URI
 
 ## List of apps
 
-On the apps management page you find all apps that exist in your Homarr instance. You can edit and delete them.
+On the apps management page you find all apps that exist in your Homarr instance. Search by name or URL, open an app directly, or use its row actions to edit and delete it. A filtered search can be cleared without leaving the page.
 
-![Apps list](./img/app-list.png)
+Viewing this list requires the `app-modify-all` permission. Creating an app requires `app-create`, editing requires `app-modify-all`, and deleting requires `app-full-all`; board permissions are not required.

apps/docs/docs/management/assistant.mdx

@@ -25,8 +25,8 @@ Open **Management → Assistant**.
 4. Enable the assistant and save.
 
 Choose a provider preset or use **Custom endpoint** with an OpenAI-compatible Chat Completions API. The
-[Homarr provider](../workshop/homarr-provider) needs no administrator API key; users sign in to the Community Workshop
-and receive a daily allowance.
+[Homarr provider](../workshop/homarr-provider) is the default and needs no administrator API key. The Homarr team pays
+for a limited number of Assistant uses for each user every day; users sign in to the Community Workshop to use them.
 
 :::info Local model servers
 

apps/docs/docs/management/backup.mdx

@@ -53,6 +53,9 @@ Before restoring, Homarr uses **sql.js WASM** to analyze the backup directly in
 
 Type `I understand` to acknowledge that restoring will replace your current database. This cannot be undone.
 
+During first-run onboarding, the database is still empty, so the restore preview goes directly to **Restore Database**
+without the extra typed confirmation. After Homarr restarts, onboarding opens the restored default home board.
+
 ### 4. Restore
 
 The backup ZIP is sent to the server, validated, and applied. After a successful restore:

apps/docs/docs/management/boards/index.mdx

@@ -11,15 +11,19 @@ tags:
 
 import iconColorImage from "./img/icon-color.png";
 import itemRadiusImage from "./img/item-radius.png";
-import layoutLargeImage from "./img/layout-large.png";
-import layoutMediumImage from "./img/layout-medium.png";
-import layoutSmallImage from "./img/layout-small.png";
+import layoutSettingsImage from "./img/layout-settings.png";
+import layoutSettingsCustomRailsImage from "./img/layout-settings-custom-rails.png";
+import boardViewModeImage from "./img/board-view-mode.png";
+import boardEditModeImage from "./img/board-edit-mode.png";
+import keyboardTileEditingImage from "./img/keyboard-tile-editing.png";
 
 Each dashboard is called a "board".
 You can create as many boards as you want.
 Boards can be restricted to user groups.
-A user may also have a "home board" which they will see at the root path (e.g. my-homarr.com or my-homarr.com/board).
-Other boards can be viewed by direct links (e.g. my-homarr.com/board/smart-home) or via the management pages.
+A user may also have a "home board" which they will see at the root path (e.g. my-homarr.com or my-homarr.com/boards).
+Other boards can be viewed by direct links (e.g. my-homarr.com/boards/smart-home) or via the management pages.
+The management page includes a compact structural preview of each board's Base layout so you can recognize it before
+opening it. Containers include their visible widgets and app icons instead of appearing empty.
 
 Names of boards must be unique because this will be used in the URL to load the desired board.
 
@@ -92,9 +96,23 @@ Homarr will fall back to the Homarr logo if nothing is set.
 
 In this section you can configure the different responsive layouts. Homarr selects the layout with the highest breakpoint that is not wider than the current screen, then scales its complete fixed-size canvas uniformly.
 
-![](./img/layout-settings.png)
+<img
+  src={layoutSettingsImage}
+  alt="Board settings showing protected Mobile and Base responsive layouts with rail controls"
+  style={{ maxWidth: "100%" }}
+/>
 
-Every board has two protected layouts:
+The layout cards show the representative geometry used for planning. This current example also shows a custom layout
+with both fixed rails enabled; the rails reserve columns and the remaining canvas reflows automatically.
+
+<img
+  src={layoutSettingsCustomRailsImage}
+  alt="Board layout settings with a custom layout and both fixed rails enabled"
+  style={{ maxWidth: "100%" }}
+/>
+
+Every board has two protected layouts. Creating a board adds **Mobile** at `0px` with three columns and **Base** at
+`768px` with the column count you choose. Both layouts can be edited, but neither can be removed.
 
 Every `1 × 1` tile has a `200 × 200` logical-pixel content area.
 The `24` logical-pixel gap between tiles is separate from that size.
@@ -107,9 +125,18 @@ The complete canvas always fits the available width and never adds horizontal bo
 - **Mobile** starts at `0px` and uses three columns on new boards.
 - **Base** is the widest layout and starts at `768px` on new boards.
 
-Mobile and Base can be renamed and their column counts can be changed, but they cannot be removed. Mobile has no fixed rails; rail configuration is available only on Base and custom layouts. You can add removable custom layouts between their breakpoints.
+Mobile and Base can be renamed and their column counts can be changed, but they cannot be removed. Mobile has no fixed
+rails; rail configuration is available only on Base and custom layouts. You can add removable custom layouts between
+their breakpoints.
 
-Each layout stores independent positions and sizes. Moving or resizing a widget while editing Mobile does not move it in Base or any custom layout. New custom layouts are generated from Base and scaled to their selected column count.
+Each layout stores independent positions and sizes. Moving or resizing a widget while editing Mobile does not move it in
+Base or any custom layout. New custom layouts start from Base's current column count and rail widths; Homarr chooses a
+free breakpoint between Mobile and Base, and you can then change the breakpoint, columns, and rails.
+
+Older or incomplete boards are repaired automatically. A board with no layouts receives Mobile at `0px` with three
+columns and Base at `768px` with ten columns. A board with one layout keeps it as Base and receives a generated Mobile
+layout. With multiple layouts, the narrowest becomes Mobile, the widest becomes Base, and intermediate layouts remain
+custom. Duplicate or out-of-order breakpoints are normalized without discarding saved positions.
 
 Use **Reset from Base** on Mobile or a custom layout to replace all of its positions and sizes with a newly generated version of Base. The layout's name, breakpoint, and column count are kept.
 
@@ -128,13 +155,14 @@ The total number of columns in the layout. Changing it projects the saved positi
 
 #### Fixed rails
 
-Base and custom responsive layouts can enable a fixed left rail, a fixed right rail, or both. Mobile has no fixed rails.
+Each responsive layout can enable a fixed left rail, a fixed right rail, or both.
 Set a rail width to zero to disable it for that layout.
 Choose a width from one to three columns with the three-step slider.
 The preview shows how much space remains for the main canvas.
 
 Rail columns are reserved from the layout's total column count.
 For example, a 12-column layout with a two-column left rail leaves ten columns for the canvas.
+The combined rail widths cannot consume the final main-canvas column.
 Enabling or widening a rail reflows canvas items into the remaining columns.
 Disabling a rail moves its contents back into the next available canvas positions.
 
@@ -143,39 +171,63 @@ Apps, widgets, and Containers inside them still use the same fixed `200 × 200`
 
 #### Breakpoint
 
-The minimum screen width where the layout is used. Mobile is fixed at `0px`. Custom breakpoints must be unique and sit between Mobile and Base. Base must remain the highest breakpoint.
+The minimum screen width where the layout is used; a layout is eligible at its breakpoint and above. Mobile is fixed at
+`0px`. Custom breakpoints must be unique and sit between Mobile and Base. Base must remain the highest breakpoint.
+When the initial viewport is not available, Homarr uses its remembered viewport information, client hints, or User-Agent
+fallback to select a layout.
 
 #### View and edit modes
 
 View mode renders a static board without executing the drag-and-drop editor.
 After the board is interactive, Homarr prepares the editor in the background for users who can modify it.
-Entering edit mode keeps the static board visible until that preparation finishes, then enables collision-aware movement and resizing without changing the board geometry.
-Widget content is inert in edit mode, so dragging anywhere on the content moves the tile instead of activating the widget; its settings button remains visible in the compact header above the tile.
-Dropping a tile into another tile's exact slot swaps their positions when both resulting placements fit without overlapping other content.
-For other collisions, or when a tile grows into occupied space, nearby tiles are compacted out of the way.
+Entering edit mode keeps the static board visible until that preparation finishes, then enables collision-aware movement and resizing.
+Collapsed Containers are expanded while editing so their contents and controls are reachable.
+
+<img
+  src={boardViewModeImage}
+  alt="A Homarr board in view mode with the dashboard canvas and static widgets visible"
+  style={{ maxWidth: "100%" }}
+/>
+
+Widget content is inert in edit mode, so dragging from the inert widget area moves the tile instead of activating the widget;
+settings and other controls remain usable in the compact header above the tile.
+A single compatible collision can swap two items when both resulting placements fit, including different-sized or lateral moves.
+For other collisions, or when a tile grows into occupied space, nearby tiles are compacted out of the way and collision chains reflow.
 The visible corner controls provide a 44-pixel resize target, and edge controls appear on hover for horizontal or vertical resizing.
 Resize handles stop at the tile's minimum allowed size while the pointer is still moving.
-Exit edit mode to save the resulting positions.
+Use the pencil button in the board header to enter edit mode; click it again to save. If you leave the page with unsaved
+changes, Homarr asks whether to discard them. If the editor cannot load, the board remains in view mode.
 
-Pointer users can drag anywhere on a widget tile. Containers use the grab button at their top-left corner.
-Resize tiles from any edge or corner handle.
-On a touch screen, press and hold the tile before moving it; resize handles support direct touch input.
+<img
+  src={boardEditModeImage}
+  alt="Board in edit mode with the board header controls and editable dashboard tiles visible"
+  style={{ maxWidth: "100%" }}
+/>
+
+Pointer users can drag from the inert widget area; interactive controls are excluded. Containers use the grab button at their top-left corner.
+Widgets can be resized from any edge or corner handle. Activate a Container's chrome with its top-left grip before using
+its resize handles.
+On a touch screen, press and hold a tile for about `200 ms` before moving it; a quick tap does not start a drag. Resize
+handles support direct touch input.
 Keyboard users can focus a tile, press Enter or Space to start editing, use the arrow keys to move it, and use Shift plus the arrow keys to resize it.
 Press Enter, Space, or Escape to stop keyboard editing.
-Keyboard moves and resizes apply immediately; Escape stops keyboard editing without undoing those changes.
+Keyboard moves and resizes apply immediately within the current canvas, rail, or Container; they cannot move an item
+between grids. Use pointer drag or **Move / resize item** for that.
+Escape stops keyboard editing without undoing those changes.
 During a pointer or touch interaction, Escape cancels the move or resize and restores the layout from before that interaction.
+Invalid, outside, or otherwise forbidden drops are cancelled in the same way.
 The **Move / resize item** action in the edit menu remains available for precise numeric input.
 
+<img src={keyboardTileEditingImage} alt="A focused board tile in keyboard editing mode" style={{ maxWidth: "100%" }} />
+
 #### Preview
 
-Layout Settings shows a lightweight structural preview for every layout, including saved spans, Containers, widget labels, and app icons. The canvas width represents the screen range where that layout is active.
+Layout Settings shows a lightweight structural preview for every layout, including saved spans, Containers, widget labels, and app icons.
+It uses a representative viewport width to project the saved geometry; it does not execute widget queries or represent every
+pixel of the screen range where the layout is active.
 
 Choose **Edit layout** to open the real board editor at that representative width on desktop. Save returns to Layout Settings. Cancel discards the local changes. On phones and tablets, the normal board editor continues to use the layout selected by the device width.
 
-<img src={layoutSmallImage} height={256} />
-<img src={layoutMediumImage} height={256} />
-<img src={layoutLargeImage} height={256} />
-
 ### Containers and rails
 
 Containers can hold apps, widgets, and nested Containers.
@@ -247,9 +299,10 @@ Change the radius of your items and Containers.
 This is the field where you can enter custom CSS.
 The styling will only be applied on the respective board page.
 
-When Homarr Assistant is enabled, users with modify permission can also ask it to edit the board's Custom
-CSS and other visual or behavior settings. The assistant reads the current stylesheet first and presents an
-editable review form before requesting approval to save the change.
+When Homarr Assistant is enabled, users with modify permission can also ask it to edit the board's General, Background,
+Appearance, Custom CSS, and app-status settings. The assistant reads the current stylesheet first and presents an
+editable review form before requesting approval to save the change. It does not edit responsive layouts, access control,
+or Danger zone actions.
 
 [See this guide on how to work with custom CSS](/docs/advanced/styling/).
 
@@ -266,12 +319,12 @@ Widgets expose their routine controls without requiring edit mode:
 - Hold `Shift` while hovering a widget that supports advanced view to expand it in place while the other widgets
   remain visible but dimmed. Release `Shift` to close it. Focus that widget and press `Shift` + `Enter` to keep the view
   open until you close it. On touch devices, open it from the widget menu. Other widgets adapt in place instead.
-- Right-click a widget to inspect its live query status, refresh its data, change quick options, open settings, or run
-  supported actions. Available controls follow your board and integration permissions.
-- If you can modify the board, right-click or touch and hold an empty grid cell to add an item there. Focus a board
-  section and press `Shift` + `F10` for the keyboard equivalent.
+- When signed in, outside edit mode, and with **Enable right click on widgets** enabled, right-click a widget to inspect
+  its live query status, refresh its data, change quick options, open settings, or run supported actions. App tiles do
+  not use this widget menu, and available controls follow your board and integration permissions.
 
-Widget and empty-space context menus follow the **Enable right click on widgets** preference in your user settings.
+The widget context menu follows the **Enable right click on widgets** preference in your user settings. On touch devices,
+use the widget menu where your browser exposes it.
 
 ### Access control
 
@@ -330,7 +383,8 @@ Duplicating a board will not copy the users and groups that have access to the b
 nor the integrations the user does not have access to.
 :::
 
-Duplicating a board will create a new board with the same settings and layout as the original board.
+Duplicating a board will create a new board with the same settings, all responsive layouts, and independent positions as the original board.
+Duplicating a board that contains Custom Widgets also requires an administrator.
 You can duplicate a board by clicking on the three dots in the list of boards and selecting "Duplicate board".
 
 ![](./img/duplicate-board-modal.png)
@@ -388,5 +442,13 @@ For the global home board you can only select boards that are public.
 
 ### Mobile home board
 
-Same as the home board, you can also set a mobile home board.
-It will be used for devices that are detected as mobile devices. (Using User-Agent header)
+The mobile home board controls which board opens for devices that Homarr detects as mobile from the User-Agent header.
+This is separate from a board's **Mobile layout**, which controls the layout selected inside that board.
+You can set a mobile home board for yourself in your user preferences, for a user or group through management, or for the
+whole server with **Global mobile board** under `Management` > `Settings` > `Boards`.
+
+For signed-in users, Homarr checks the user's mobile home board, then the user's desktop home board, then the mobile and
+desktop defaults for the lowest-position matching group, followed by the mobile and desktop defaults for the `Everyone`
+group, and finally the server-wide mobile and desktop defaults. Anonymous visitors use the server-wide mobile default and
+then the server-wide desktop default. Server-wide fallback boards must be public. See the
+[global board defaults](/docs/management/settings#boards) for the complete precedence and the required public-board rule.

apps/docs/docs/management/custom-widgets/agent-authoring.mdx

@@ -67,17 +67,23 @@ These interfaces do not return an archive URL or archive hash.
 
 1. Load `customWidget_getSkill`, then get the prompt and live schema.
 2. Call `customWidget_getComponentCatalog`, followed by `customWidget_getComponent` for only the relevant installed
-   components and `customWidget_getExample` when one catalog example matches the interaction pattern. If shared props
-   are needed, collect their catalog names and call `customWidget_getSharedProps` once for that set.
+   components and `customWidget_getExample` when one catalog example matches the interaction pattern. Fetch at most
+   eight component documents before the first validation (or four after a complete example already matches). If shared
+   props are needed, collect their catalog names and call `customWidget_getSharedProps` once for that set.
 3. Read the external API documentation.
 4. Build one definition, using `templateLines` for multiline JSX tool input.
 5. Validate the definition without saving it and repair every reported issue.
 6. Create a preview session.
-7. Run `customWidget_previewQuery` for every query returned by the preview and inspect its actual status and data shape.
+7. Run `customWidget_previewQuery` for every query returned by the preview and inspect its actual status and data shape. Assistant conversations retain a bounded response preview so large APIs cannot exhaust the model context. Use
+   `{}` for load queries; manual queries require exactly the returned primitive `parameterNames`.
 8. Test relevant actions in simulation mode.
 9. Open the returned preview path with browser tools.
-10. Inspect the redacted journal and revise the local candidate until validation, data, and rendering all work.
-11. Create the widget, including any source URLs and credentials the user already supplied.
+10. Inspect the redacted journal and revise the local candidate until validation, data, and rendering all work. Keep the
+    exact tested preview candidate locally. Any definition, template, or source change requires a new validation and preview;
+    earlier query evidence belongs to the previous preview revision.
+11. Create the widget from that final tested preview with `customWidget_createFromPreview`. The preview session already carries
+    the source URLs and encrypted credentials supplied during preview; the create call accepts only its session ID plus an
+    optional target board and persists that tested preview.
 12. Open its returned management path, and use a structured question when the user must choose whether to place it on a board.
 13. Otherwise, ask the user to configure the saved definition with the ten-minute Homarr source-setup URL.
 14. Create a final preview with the saved definition ID so Homarr loads its stored credentials, then test it again.

apps/docs/docs/management/custom-widgets/authoring.mdx

@@ -1,8 +1,37 @@
 # Create a Custom Widget
 
 import { CanonicalCustomWidgetExample } from "@site/src/components/custom-widget-code";
+import workbenchImage from "./img/workbench.png";
+import workbenchMobileImage from "./img/workbench-mobile.png";
+import workbenchValidationImage from "./img/workbench-validation.png";
 
-The workbench is visual-first: configure the default API connection, add request cards, add option rows, then write JSX. Additional sources and raw manifest JSON remain under Advanced. Code and preview sit side by side on desktop and use tabs on mobile.
+The workbench exposes **General**, **API sources**, **Requests**, **Options**, **JSX**, and **Preview** sections. Advanced JSON is
+available in the manifest and request/option editors. Code and preview sit side by side on desktop; on smaller screens the
+**Configure**/**Preview** switch shows one pane at a time and the section navigation scrolls horizontally. Preview sizes display
+as **S/M/L** (Compact/Standard/Wide), and fixtures are **Live**, **Loading**, **Empty**, or **Error**.
+For multiline JSX, prefer `templateLines` in agent or MCP input and keep the final tested preview as the source of truth before saving.
+
+<img
+  src={workbenchImage}
+  alt="Custom Widget workbench with configuration sections and a live preview"
+  style={{ maxWidth: "100%" }}
+/>
+
+<img
+  src={workbenchMobileImage}
+  alt="Mobile Custom Widget workbench with Configure and Preview switch and horizontally scrollable section navigation"
+  style={{ maxWidth: "100%" }}
+/>
+
+The workbench keeps the configuration and preview together so you can inspect validation diagnostics, the redacted request
+journal, fixture data, and preview size before saving. Invalid fields stay marked in the form while the preview explains why it
+needs attention.
+
+<img
+  src={workbenchValidationImage}
+  alt="Custom Widget workbench showing a Base URL validation error with Test, preview, and Create actions disabled"
+  style={{ maxWidth: "100%" }}
+/>
 
 ## Manual workflow
 
@@ -21,7 +50,9 @@ The workbench is visual-first: configure the default API connection, add request
 
 <CanonicalCustomWidgetExample id="widget-options" label="Widget options" example="options" height="360px" />
 
-Every option has a default. Supported controls include text, textarea, number, switch, select, multi-select, slider, date, time, color, icon, URL, duration, time zone, and JSON. Dynamic choices use `choicesFrom` with a query ID and value/label paths.
+Every option has a default. Supported controls include text, textarea, number, switch, select, multi-select, slider, date, time, color, icon, URL, duration, time zone, and JSON. Dynamic choices use `choicesFrom: { request, itemsPath?, valuePath, labelPath }`; the request must be a load query without invocation parameters, and you cannot provide both static `choices` and `choicesFrom`.
+
+Preview actions are simulated by default and recorded in the journal without contacting the service. Enable **Run actions against the configured API** only when you intend a real mutation; live actions still require configured confirmation.
 
 ## ChatGPT or Claude
 
@@ -31,7 +62,8 @@ The model must return one fenced `json` block containing the complete widget, in
 field. Copy that single block and select **Paste**. Homarr fills the visual builders and the JSX editor
 without any placeholder replacement or second paste.
 
-Homarr shows all actionable schema or JSX errors inline. Enter credentials separately. The prompt deliberately
+Homarr shows all actionable schema or JSX errors inline. Enter credentials separately. The copied prompt does not include the
+latest preview response; use **Preview** > **Data** to inspect it and mention important response fields in your request. The prompt deliberately
 recommends a focused Mantine component set, visual hierarchy, responsive layout, theme compatibility, and loading,
 empty, failure, and success states.
 

apps/docs/docs/management/custom-widgets/custom-jsx.mdx

@@ -7,7 +7,21 @@ Templates are JSX expressions interpreted inside a widget-local safety and rende
 - `options.name` — saved widget configuration
 - `inputs.name` — temporary values from declarative `bind`
 
+The v2 manifest requires a `default` source and supports up to eight sources, 64 requests, and 64 options. Source IDs are
+case-insensitively unique. Each request allows up to 32 static headers and 32 invalidation targets; a widget can contain
+up to 24 secrets, each up to 8,192 characters, and templates are limited to 50,000 characters. Validation reports the
+exact field when a limit is exceeded.
+
+Authoring input accepts either `template` or `templateLines`, not both. `templateLines` accepts 1–2,000 lines, each up to
+10,000 characters; after joining lines with newlines, the complete template must still fit the 50,000-character limit.
+
+The safe interpreter also bounds JSX evaluation: AST depth 64, 25,000 operations, 4,000 collection items, 10,000 rendered
+nodes, and 200,000 characters in one string or rendered value. API responses are bounded separately before they reach the
+template.
+
 Use normal Mantine layouts, typography, feedback, dates, and charts. Official compound names such as `Card.Section`, `Tabs.List`, and `Radio.Group` are supported. Ordinary safe props pass through; a dangerous capability produces an explicit error.
+Unsafe URLs, callback props, and unapproved style properties are stripped. Response data is deep-sanitized and budgeted
+before it reaches `data`, so treat it as untrusted input even when the source is private.
 
 ## Temporary inputs
 
@@ -15,7 +29,7 @@ Use normal Mantine layouts, typography, feedback, dates, and charts. Official co
 <Stack>
   <TextInput bind="search" defaultValue="" label="Search" />
   <SubFetch requestId="search" params={{ query: inputs.search }}>
-    {(results) => (
+    {(results, meta) => (
       <Stack>
         {(results ?? []).map((item) => (
           <Text key={item.id}>{item.name}</Text>
@@ -32,14 +46,23 @@ Bound values live only in React memory while the widget is mounted. They are not
 
 Use expressions, conditionals, optional chaining, arrays, objects, template strings, safe standard helpers, and expression callbacks for `map`, `filter`, `sort`, and trusted runtime slots. Callback blocks, authored `const`, IIFEs, authored recursion, arbitrary functions, imports, hooks, refs, raw events, browser requests, `eval`, and bigint are blocked.
 
-Bounded regex literals are supported for string matching, splitting, search, and replacement. Patterns with lookbehind, backreferences, nested quantifiers, excessive length, or unsupported flags are rejected.
+Bounded regex literals are supported for string matching, splitting, search, and replacement. Regex literals are limited to
+128 characters and flags `gimsu`; lookarounds, backreferences, repeated alternatives/groups, unsupported flags, and more
+than one variable quantifier are rejected.
 
 ## Runtime components
 
-- `SubFetch` runs a manual query with its `params`. Set `triggerContent` to a card or image to make that content the accessible click and keyboard trigger instead of showing the default load button.
-- `ActionButton` and `ToggleSwitch` run actions.
-- `RefreshButton` renders a compact, accessible icon control that refreshes load queries for authenticated viewers. It
-  is disabled for anonymous public-board viewers because refreshing invalidates shared server cache state.
+- `SubFetch` runs a named query. Automatic queries run when the widget loads; set `trigger="manual"` to defer one and pass
+  primitive `params` for its invocation references. With `triggerContent`, any content node (commonly a card or image) becomes
+  the accessible click and keyboard trigger instead of showing the default load button.
+- `SubFetch` with `trigger="manual"` keeps its result local to that instance; it does not populate the shared
+  `data.requestId` or `status.requestId` roots. The child callback receives `(result, meta)`, while loading, errors, and
+  retry are handled by `SubFetch`. Provide both `triggerContent` and `triggerAriaLabel` when custom content launches it.
+- `ActionButton` and `ToggleSwitch` run actions only when the widget is mounted outside edit mode. A toggle needs both
+  enabled and disabled request parameters and rolls back its visual state if the action fails.
+- `RefreshButton` renders a compact, accessible icon control that invalidates the client&apos;s load-query cache so active load
+  queries can refetch; it does not execute a request itself. It is disabled when the widget has no active item or preview
+  session, or while the board is in edit mode.
 - `Icon`/`TablerIcon` resolves installed safe icons.
 
 Always include responsive loading, empty, error, and success states. Runtime failures remain inside the widget tile.

apps/docs/docs/management/custom-widgets/index.mdx

@@ -42,9 +42,14 @@ interface HomarrCustomWidgetV2 {
 
 ### Design with AI
 
-The **Design with AI** action is available while creating or editing a custom widget. Describe what the widget should show and, when [Homarr Assistant](../assistant) is enabled, send the request directly from the form. The assistant receives the widget schema, current non-secret configuration, and latest test response, then proposes the matching create or update tool for your approval.
+The **Design with AI** action is available while creating or editing a custom widget. Describe what the widget should show and,
+when [Homarr Assistant](../assistant) is enabled, send the request directly from the form. The generated prompt includes the
+widget schema and current non-secret configuration, but not the latest preview response. It proposes the matching create or
+update tool for your approval.
 
-Run **Test** first when possible so the prompt includes the endpoint's real response shape. Saved secrets are never added to the prompt. **Copy to clipboard** remains available when the Assistant is disabled or when you prefer another AI service.
+Use the preview's **Data** tab to inspect the endpoint's real response shape and mention important fields in your request; the
+copied prompt does not automatically include the latest preview response. Saved secrets are never added to the prompt. **Copy to
+clipboard** remains available when the Assistant is disabled or when you prefer another AI service.
 
 <CustomWidgetCodeExample
   id="complete-widget-manifest"
@@ -62,9 +67,9 @@ preview, publish, install, configure, or write secrets, including through HTTP a
 only lists Custom Widget MCP tools, prompts, and resources when its owner is an administrator.
 
 Adding or configuring a Custom Widget placement requires both administrator access and permission to modify that
-board. A non-administrator with board-modify access can move, resize, change presentation settings, or remove an
-existing placement, but cannot add one, change its definition, refresh interval, or Custom Widget options. Duplicating
-a board that contains Custom Widgets also requires an administrator.
+board. Duplicating a board that contains Custom Widgets also requires an administrator. A non-administrator with
+board-modify access can move, resize, change presentation settings, or remove an existing placement, but cannot add one,
+change its definition, refresh interval, or Custom Widget options.
 
 Once an administrator has placed a widget, ordinary board permissions apply to rendering and requests. Authorized
 non-administrators can use it on private boards, and queries can render for anonymous viewers on public boards.
@@ -99,14 +104,12 @@ logs, or exports.
 For administrators adding widgets while editing a board, the Custom Widgets section includes **Import from
 Workshop**. Non-administrators do not see the Custom Widget picker or Workshop actions. Selecting **Install widget**
 opens a two-step modal flow: first review the Workshop entry and its complete source in the read-only editor, then
-confirm API sources and credentials. The steps keep the same dimensions and the previous step remains available when
-you go back. After import, the new definition appears in the picker. Its tile
-waits for the board to be saved before server requests run and loads automatically after a successful save; no page
-reload is required.
+confirm API sources and credentials. After import, the new definition appears in the picker. Its tile waits for the board
+to be saved before server requests run.
 
 ## Import and Workshop
 
-The install flow always links to the corresponding public Workshop entry using `WORKSHOP_WEB_URL`. Import confirmation shows origins, authentication modes, network scopes, methods, actions, and permissions. Every source has a suggested URL, but private and loopback sources must be confirmed or replaced for the current Homarr installation. The same screen accepts API keys, tokens, usernames, and passwords; credentials remain optional at install time and missing values stay visible on the Custom Widgets page.
+The install flow always links to the corresponding public Workshop entry under the configured Workshop origin. Import confirmation shows origins, authentication modes, network scopes, methods, actions, and permissions. Every source has a suggested URL, but private and loopback sources must be confirmed or replaced for the current Homarr installation. The same screen accepts API keys, tokens, usernames, and passwords; credentials remain optional at install time and missing values stay visible on the Custom Widgets page.
 
 For example, installing **Tautulli Activity** asks for both the user's Tautulli URL and API key. A stable public source such as PokéAPI keeps its published URL without creating unnecessary setup work.
 
@@ -131,6 +134,7 @@ replace the v1 backup.
 
 ## Bundled examples
 
-Homarr seeds five disabled examples without credentials and never overwrites an edited seed. They use the same public contract. The Tautulli example is the highest-scoring widget preserved from Homarr's AI authoring evaluation:
+Homarr seeds five disabled examples without credentials and never overwrites an edited seed. They use the same public
+contract. Tautulli Activity is one of the bundled examples preserved from Homarr's AI authoring evaluation:
 
 <BundledCustomWidgetGallery />

apps/docs/docs/management/custom-widgets/requests-and-security.mdx

@@ -1,6 +1,11 @@
 # Configure requests and security
 
-Most widgets use a single source named `default`. Extra keyed sources are available under Advanced for widgets that combine APIs. Authentication is `none`, `bearer`, `basic`, an API-key header, or an API-key query parameter. Credentials belong to the widget but remain outside its manifest.
+Most widgets use a single source named `default`; the manifest must contain it. Extra keyed sources are available for widgets
+that combine APIs. Source IDs are case-insensitively unique. Base URLs must use HTTP(S), contain no embedded credentials,
+query string, or fragment, and sources can be `public`, `private`, or `loopback`. Authentication is `none`, `bearer`,
+`basic`, an API-key header, or an API-key query parameter. Credentials belong to the widget but remain outside its manifest.
+Source origins are fixed by the definition and source-setup flow; widget options and invocation parameters cannot redirect a
+request to a different origin.
 
 ## Named requests
 
@@ -35,19 +40,28 @@ Bind values directly where they are used:
 
 `{option:name}` and `$option` read saved widget options. `{param:name}` and `$param` read invocation-time `params`. Load queries cannot use invocation parameters. Homarr infers the exact parameter names and primitive values from these references, rejecting missing or extra invocation params at the request boundary.
 
-Paths and query-string values must resolve to text, numbers, or booleans. JSON bodies can also use structured `json` and `multiSelect` option values, for example `{ "entity_ids": { "$option": "entities" } }`.
+Path placeholders and query values must resolve to text, numbers, or booleans. `$option` and `$param` references may appear
+recursively in JSON bodies; invocation parameters remain primitive, and load queries cannot use `$param`. JSON bodies can
+also use structured `json` and `multiSelect` option values, for example `{ "entity_ids": { "$option": "entities" } }`.
 
 ## Protection
 
 Every request uses Homarr's existing server executor: same-origin source enforcement, network scope, DNS and redirect validation, SSRF protection, board permissions, rate and request limits, body and response limits, timeouts, and encrypted credential injection. Static headers cannot override credentials, cookies, routing, proxy, forwarding, or hop-by-hop headers.
 
+The executor caps request bodies at 10 KiB and response bodies at 1 MiB. Parsed JSON is limited to depth 32 and 50,000 nodes;
+each network hop has a ten-second timeout, queries follow at most three same-origin redirects, actions do not follow redirects,
+and the total request deadline is 45 seconds.
+
+The limiter allows four concurrent requests per user/item and eight per definition. Per minute, a user/item can make up to 60
+queries, 10 actions, or 3 DELETE actions; a definition can receive up to 240, 40, or 12 of those request categories.
+
 Queries default to view permission and actions to modify. DELETE always requires full permission and confirmation. Actions are never cached, retried, or run on load.
 
 Management and runtime are intentionally separate. A Homarr administrator with board-modify permission places and
 configures the widget. After placement, query and action authorization follows the request's board permission. Public
 boards may execute queries for anonymous viewers, but mutations stay authenticated. This includes shared-cache
-invalidation: `RefreshButton` is disabled for anonymous viewers, while ordinary scheduled query rendering remains
-available.
+invalidation: `RefreshButton` is disabled only without an active item or preview session, or in edit mode, while ordinary
+scheduled query rendering remains available to anonymous viewers.
 
 Responses use bounded, versioned shared-Redis cache keys. Action invalidation advances the shared version so every
 Homarr replica stops serving the previous response without scanning or deleting a key prefix.

apps/docs/docs/management/custom-widgets/troubleshooting.mdx

@@ -41,7 +41,8 @@ The workbench marks the invalid field while you type. An invalid URL does not re
 
 An invalid definition disables widget preview and Save/Create. The Data, Options, Actions, and Diagnostics tabs remain available so you can correct it.
 
-The Diagnostics tab shows the current schema errors.
+The Diagnostics tab shows current schema and JSX errors, accessibility checks, and (after a preview) the redacted request
+journal. It does not expose credentials or raw secret values.
 
 ## Workshop unavailable
 

apps/docs/docs/management/integrations/index.mdx

@@ -13,9 +13,11 @@ Check [the available integrations](/docs/category/integrations) for further info
 
 ## Create an integration
 
-To create an integration, you can choose the supported application from the dropdown at the top right:
+To create an integration, choose **New integration** and select the supported application from the searchable grid. The grid groups related services visually and shows which widgets each integration supports.
 
-![](./img/create-integration-dropdown.png)
+The integrations management page uses a searchable list. Each row shows the integration type and URL, with the actions you have permission to use.
+
+This page is only visible to users with the global `integration-full-all` permission or with full access on at least one integration. Without the global permission, only the integrations you have full access to are shown.
 
 Next, you'll need to fill out the required fields to configure the integration:
 

apps/docs/docs/management/mcp.mdx

@@ -23,9 +23,9 @@ approval before running mutating procedures.
 
 ## Getting Started
 
-The MCP endpoint lives under the **API** page at `Management` → `Tools` → `API` → **MCP** tab.
+The MCP endpoint lives under the **API** page at `Management` → `Tools` → `API` → **AI / MCP** tab.
 
-![MCP Instructions Page](./api/img/mcp-instructions.png)
+![AI / MCP tab showing the endpoint, API-key warning, and client configuration](./api/img/mcp-instructions.png)
 
 ### 1. Create an API Key
 

apps/docs/docs/management/search-engines/index.mdx

@@ -8,8 +8,7 @@ tags:
 # Search Engines
 
 Using the search engines, terms can be quickly searched simply by opening the search bar at the top or using the keyboard shortcut `CTRL + K`.
-
-![](./img/search-engines.png)
+The management page provides a searchable list with the shortcut, URL template, source, and available row actions for each engine.
 
 You can add any search engine that has a search URL that accepts a search term as a parameter.
 

apps/docs/docs/management/users/index.mdx

@@ -163,19 +163,59 @@ Members can be removed from the group using the remove button at the end:
 #### Permissions tab
 
 In this tab, you manage what permissions the members of this group will have.
-Currently, the following permissions are available:
+Permissions are organized by category (boards, apps, integrations, and so on). Each category is a row with a
+segmented control that lets you pick a single access level. Selecting a level grants that level and every lower
+level in the same category. Choosing **None** removes all permissions for that category.
 
-- Boards
-  - **Create boards**: Allow members to create boards
+Selecting **Administrator** grants full access to everything. While the administrator level is selected, every
+other category is disabled and shows a **Granted via Administrator** caption, because administrators already have
+all permissions. Deselecting it (choosing **None** on the administrator row) re-enables the other categories.
+
+##### Presets
+
+Above the rows you can apply a preset to fill in a common configuration in one click:
+
+- **Viewer**: view access to boards, use access to apps and integrations, and viewing media.
+- **Editor**: modify access to boards and apps, interact with integrations, modify search engines (includes creating), and viewing media.
+- **Admin**: grants the administrator permission (full access to everything).
+
+When the current selection does not match any preset, a **Custom** badge is shown.
+
+##### Implied permissions
+
+Some levels include additional permissions automatically. When a level implies extra permissions (for example,
+full board access also allows creating boards), a dimmed `also grants: …` hint is shown under the category row.
+
+##### Effective permissions
+
+Below the rows, the **Effective permissions** panel can be expanded to review everything members of this group
+will be able to do, including implied permissions, grouped by category with a count for each.
+
+Each category below is a segmented control that starts with **None**; the remaining segments are the access levels
+in ascending order (higher levels include the lower ones and may imply extra permissions shown in the hint):
+
+- Boards — None
   - **View all boards**: Allow members to view all boards
   - **Modify all boards**: Allow members to modify all boards (Does not include access control and danger zone)
-  - **Full board access**: Allow members to view, modify, and delete all boards (Including access control and danger zone)
-- Integrations
-  - **Create integrations**: Allow members to create integrations
-  - **Use all integrations**: Allows members to add any integrations to their boards
+  - **Full board access**: Allow members to view, modify, and delete all boards (Including access control and danger zone; includes creating boards)
+- Apps — None
+  - **Use all apps**: Allow members to add any apps to their boards
+  - **Modify all apps**: Allow members to modify all apps (includes creating apps)
+  - **Full app access**: Allow members to manage, use and delete any app
+- Integrations — None
+  - **Use all integrations**: Allow members to add any integrations to their boards
   - **Interact with any integration**: Allow members to interact with any integration
-  - **Full integration access**: Allow members to manage, use and interact with any integration
-- **Administrator**: Members with this permission have full access to all features and settings
+  - **Full integration access**: Allow members to manage, use and interact with any integration (includes creating integrations)
+- Search engines — None
+  - **Modify all search engines**: Allow members to modify all search engines (includes creating search engines)
+  - **Full search engine access**: Allow members to manage and delete any search engine
+- Medias — None
+  - **View all medias**: Allow members to view all medias
+  - **Full media access**: Allow members to manage and delete any media (includes uploading medias)
+- Other — None
+  - **View logs**: Allow members to view logs
+- Administrator — None
+  - **Administrator**: Members with this permission have full access to all features and settings
 
 Custom Widget authoring, import, migration, preview, secrets, Workshop access, and placement configuration are reserved
 for administrators and are not separate assignable group permissions. Board modifiers can still move, resize, change
@@ -220,7 +260,8 @@ Clicking the `Copy & close` button will copy the URL to your clipboard.
 
 ### Self-onboarding
 
-Clicking the invitation link will bring up a form with fields for the username and password:
+Clicking the invitation link opens a centered registration form that uses the same visual shell as Homarr's onboarding
+and sign-in pages, with fields for the username and password:
 
 ![](./img/invitation-self-onboarding.png)
 

apps/docs/docs/widgets/app/index.mdx

@@ -28,7 +28,8 @@ import piHoleApp from "./img/pi-hole-ping-icon.png";
 
 ### Interactions
 
-App tiles stay compact and open their configured destination directly. Right-click a tile to inspect its status or change its settings when the board and your preferences allow it.
+App tiles stay compact and open their configured destination directly. They do not use the shared widget context menu;
+configure the app and its status check from the tile's edit actions.
 
 ### Adding the widget
 

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

@@ -7,6 +7,7 @@ hide_title: true
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { assistantWidget } from ".";
+import assistantWidgetImage from "../../management/img/assistant-widget.png";
 
 <WidgetHeader widget={assistantWidget} categories={["Productivity"]} />
 
@@ -15,7 +16,18 @@ board. Messages, conversations, tool calls, approvals, files, mentions, model co
 usage details, and response actions remain synchronized with the app-wide assistant.
 
 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.
+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.
+
+<img
+  src={assistantWidgetImage}
+  alt="Assistant widget embedded on a dashboard with its conversation header, automatic approvals control, model selector, and composer"
+  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
 
@@ -42,10 +54,16 @@ keeps every assistant entry point synchronized without storing a user's private
 - 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.
+- 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.

apps/docs/docs/widgets/beszel-system-grid/index.mdx

@@ -4,12 +4,11 @@ description: "Card grid view of all Beszel-monitored systems with real-time metr
 hide_title: true
 ---
 
-import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
-
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetIntegrations } from "@site/src/components/widgets/integrations";
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
 import { beszelSystemGridWidget } from ".";
 import { beszelIntegration } from "@site/docs/integrations/beszel";
 

apps/docs/docs/widgets/beszel-system-stats/index.mdx

@@ -17,7 +17,7 @@ import beszelSystemStats from "./img/beszel-system-stats.png";
 
 <WidgetHeader widget={beszelSystemStatsWidget} categories={["System Monitoring", "Charts"]} />
 
-This widget displays time-series charts for a selected Beszel system, including CPU, memory, disk, network, and Docker container metrics. The Disk Usage chart combines the root disk and every extra filesystem reported by Beszel. Hover over or focus the widget controls to switch between the realtime Live view and historical periods ranging from 1 hour to 30 days. Live view keeps a one-minute window and pauses while the browser tab is hidden. If the live stream drops, the widget now shows the connection failure state immediately and can switch back to historical data.
+This widget displays time-series charts for a selected Beszel system, including CPU, memory, disk, network, and Docker container metrics. The Disk Usage chart combines the root disk and every extra filesystem reported by Beszel. Use the widget controls to switch between the realtime Live view and historical periods ranging from 1 hour to 30 days. Live view keeps a one-minute window and pauses while the browser tab is hidden. If the live stream drops, the widget now shows the connection failure state immediately and can switch back to historical data.
 
 ### Screenshots
 

apps/docs/docs/widgets/beszel-system-table/index.mdx

@@ -4,12 +4,11 @@ description: "Table view of all Beszel-monitored systems with sortable columns a
 hide_title: true
 ---
 
-import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
-
 import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetIntegrations } from "@site/src/components/widgets/integrations";
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
 import { beszelSystemTableWidget } from ".";
 import { beszelIntegration } from "@site/docs/integrations/beszel";
 

apps/docs/docs/widgets/bookmarks/index.mdx

@@ -13,8 +13,9 @@ import { bookmarksWidget } from ".";
 
 <WidgetHeader widget={bookmarksWidget} categories={["Links", "Apps"]} />
 
-The bookmarks widget allows you to display multiple app links in a single widget.
-You can add links to your favorite applications, websites, or any other resources you want quick access to.
+The bookmarks widget allows you to display multiple links in a single widget.
+Select one or more existing Apps directly in the widget settings; these bookmarks keep a reference to the App, so changes to its name, icon, or URL are reflected automatically.
+For links that do not need an App, add their URLs under **Custom links** instead.
 Its normal view adapts each configured layout to the available width and height: lower-priority hostnames are hidden before names or icons, and larger collections scroll instead of crushing cards.
 Advanced view shows every bookmark as a roomy card with its full title, hostname, icon, and complete description regardless of the compact layout and visibility choices.
 

apps/docs/docs/widgets/bookmarks/index.ts

@@ -47,9 +47,15 @@ export const bookmarksWidget: WidgetDefinition = {
       {
         name: "Bookmarks",
         description: "List of bookmarks to display in the widget.",
-        values: "Select of all your apps and order them as you like.",
+        values: "Select one or more Apps directly, then order them as you like.",
         defaultValue: "No bookmarks selected",
       },
+      {
+        name: "Custom links",
+        description: "URLs to display without first creating an App.",
+        values: "List of URLs.",
+        defaultValue: "No custom links",
+      },
     ],
   },
 };

apps/docs/docs/widgets/calendar/index.mdx

@@ -31,16 +31,12 @@ the same data is requested through Homarr's MCP or Assistant tools.
 
 ### Screenshots
 
-import popover from "./img/popover.png";
-import withIntegrations from "./img/with-integrations.png";
-import withoutIntegrations from "./img/without-integrations.png";
+import currentView from "./img/current-view.png";
+import advancedView from "./img/advanced-view.png";
 
-<div className="flex gap-1">
-  <img src={withIntegrations} alt="calendar with-integrations big-size" width={256 + 4} height={256 + 4} />
-  <div className="flex flex-col gap-1">
-    <img src={popover} alt="calendar popover-details the-mandalorian" width={128 * 3} height={128} />
-    <img src={withoutIntegrations} alt="calendar without-integrations small-size" width={256} height={128} />
-  </div>
+<div className="flex flex-col gap-1">
+  <img src={currentView} alt="Calendar month view with marked events" width={513} height={303} />
+  <img src={advancedView} alt="Calendar advanced view with grouped events" width={800} height={484} />
 </div>
 
 ### Supported Integrations

apps/docs/docs/widgets/custom-api/index.mdx

@@ -32,7 +32,8 @@ Credentials remain on the server.
 
 :::note
 Custom API widgets must first be created in **Management → Custom Widgets** before they appear in the widget picker.
-Action buttons can only be executed by administrators.
+Action buttons require the request's minimum board permission, which is `modify` by default. Anonymous viewers cannot run
+mutations. DELETE additionally requires full permission and confirmation.
 :::
 
 ### Permissions and actions

apps/docs/docs/widgets/dns-hole-controls/index.mdx

@@ -22,7 +22,7 @@ import { technitiumDnsIntegration } from "@site/docs/integrations/technitium-dns
 
 When several DNS integrations are selected, Homarr keeps healthy controls available if one source fails and shows a warning identifying the unavailable integration.
 
-This widget lets permitted users enable, disable, or temporarily pause one or more DNS services. It shares the summary query and cache with DNS Hole Summary. Every selected source stays available in the normal scrollable view, while cards and controls adapt to the widget's width and height.
+This widget lets permitted users enable, disable, or temporarily pause one or more DNS services. It shares the summary query and cache with DNS Hole Summary. Every selected source stays available in the normal scrollable view, while cards and controls adapt to the widget's width and height. Bulk actions keep successful results visible and report the number of failures.
 
 ### Screenshots
 

apps/docs/docs/widgets/docker-containers/index.mdx

@@ -8,6 +8,7 @@ import { WidgetHeader } from "@site/src/components/widgets/header";
 import { AddingWidget } from "@site/src/components/widgets/adding";
 import { WidgetConfig } from "@site/src/components/widgets/configuration";
 import { WidgetIntegrations } from "@site/src/components/widgets/integrations";
+import { WidgetInteractionGuide } from "@site/src/components/widgets/interactions";
 import { IconAd } from "@tabler/icons-react";
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
@@ -49,6 +50,8 @@ Each container row has an action menu, accessible via the three-dot icon or by r
 - **Remove** - permanently remove the container after a second confirmation click
 - **Add to Homarr** - create a bookmark app from the container
 
+<WidgetInteractionGuide advancedView={false} />
+
 ### Adding the widget
 
 <AddingWidget />

apps/docs/docs/widgets/downloads/index.mdx

@@ -21,36 +21,79 @@ import { downloadsWidget } from ".";
 
 <WidgetHeader widget={downloadsWidget} categories={["Torrent client", "Usenet client", "Downloads"]} />
 
-This widget displays a list of torrents or usenet-articles that are currently being downloaded, along with their progress and other relevant information. It supports 7 download client integrations and provides a rich, responsive table interface.
+This widget displays torrent, Usenet, and miscellaneous download jobs, along with their progress and other relevant information. It supports 7 download client integrations and provides a rich, responsive table interface.
 
 ### Screenshots
 
 import downloadsCard from "./img/screenshot.png";
 import contextMenuImg from "./img/context-menu.png";
+import advancedViewImg from "./img/advanced-view.png";
+import filterPanelImg from "./img/filter-panel.png";
 
 <div>
   <img src={downloadsCard} alt="Downloads widget showing torrent and usenet items" width={128 * 4} />
 </div>
 
-#### Right-click context menu
+#### Download-row context menu
 
 <div>
-  <img src={contextMenuImg} alt="Downloads widget context menu with pause, delete, and copy actions" width={128 * 4} />
+  <img src={contextMenuImg} alt="Downloads row context menu with pause, delete, and copy actions" width={128 * 4} />
+</div>
+
+#### Advanced view
+
+<div>
+  <img
+    src={advancedViewImg}
+    alt="Downloads widget in advanced view with stats, sortable columns, and expanded details"
+    width={128 * 6}
+  />
+</div>
+
+#### Advanced filter panel
+
+<div>
+  <img src={filterPanelImg} alt="Downloads advanced view with the status filter panel open" width={128 * 6} />
 </div>
 
 ### Features
 
-- **Responsive table** — columns automatically adapt to widget width, hiding less important columns at smaller sizes
-- **Sortable columns** — click any column header to sort ascending/descending
+- **Responsive compact table** — in compact mode, selected columns adapt to both widget width and height; narrow or short tiles hide speed/state columns, and the shortest tiles also hide the ETA column
+- **Sortable columns** — click any sortable column header to sort the current view; the configured default controls the initial column and direction
 - **Column customization** — choose which columns to display, then hover a header to reveal its grab handle for reordering or drag its edge to resize it; layouts save automatically per widget
-- **Right-click context menu** — copy download names, or pause, resume, and delete when your account has Interact access and the client supports those actions
+- **Download-row context menu** — copy a download name or ID from any row; pause, resume, and delete actions appear when you have Interact access to that integration
 - **Row expansion** — click any row to see full details inline without opening a separate modal
 - **Hover tooltips** — hover a download name to see size, speeds, ETA, ratio, and category; open tooltips close when switching between compact and advanced mode
-- **Global stats bar** — toggle a summary bar showing queue progress, total size, speeds, ratio, and per-state counts
+- **Global stats bar** — show queue progress, downloaded/total size, transfer speeds, global torrent ratio, and per-state counts in compact mode; advanced view always includes it
 - **Client filtering** — filter downloads by integration or status using the footer filter panel
-- **Global controls** — pause/resume downloads from supported clients when your account has Interact access; read-only clients such as slskd do not expose these controls
+- **Global controls** — pause/resume actionable queues from the footer bar, limited to selected integrations where you have Interact access
 - **Status indicators** — color-coded badges show download state at a glance
-- **Speed overview** — total download and upload speeds displayed in the footer
+- **Speed overview** — total download and upload speeds for the selected clients are displayed in the footer
+
+:::note
+
+Compact layouts use both dimensions: below 500px wide, speed columns are hidden; below 300px wide, the ETA and state
+columns are hidden too. A tile shorter than 180px hides speed and state columns, and a tile shorter than 120px also
+hides ETA. The footer is hidden below 96px in compact mode. Advanced view bypasses these compact size reductions,
+keeps the selected column set, and always includes the stats bar and footer controls, with the filter panel available
+from the footer.
+
+The filter panel changes the visible rows. Its client/status filters also change the stats bar's progress, size, and
+state counts, while transfer-speed totals summarize the selected clients and the global torrent ratio summarizes the
+selected torrent clients. The configured category/label filter can optionally be applied to the global torrent ratio
+through **Use category filter for global torrent ratio**; footer client/status filters do not change that ratio.
+
+The per-item **Ratio** is sent bytes divided by the item's total size. **Global Ratio** is total uploaded bytes divided
+by total downloaded bytes.
+
+Mutation controls depend on the integration's Interact permission. Users without that permission can still view rows and
+use the row menu's copy actions. `slskd` is list-only: its pause, resume, and delete operations are no-ops, so those
+controls have no effect for that client even when Interact permission exposes them.
+
+The screenshot above is a Downloads row menu, separate from the shared widget context menu. When board right-click menus
+are enabled, the shared menu provides widget-level actions such as advanced view, widget options, refresh, and settings.
+
+:::
 
 ### Supported Integrations
 
@@ -82,20 +125,21 @@ import contextMenuImg from "./img/context-menu.png";
     },
     {
       integration: slskdIntegration,
-      note: "Soulseek client (read-only)",
+      note: "Soulseek client (list-only; mutation controls are no-ops)",
     },
   ]}
 />
 
 ### Interactions
 
-- **Right-click** any download to copy its name; pause/resume and delete require Interact access and client support
+- **Right-click** any download to copy its name or ID; pause, resume, and delete are available only with Interact access
 - **Click** any row to expand it and see full download details inline
 - **Hover** a download name for a quick stats tooltip
-- **Stats toggle** — show or hide the global stats bar from the footer
-- **Pause / Resume** downloads from supported clients using the footer controls when you have Interact access; slskd remains read-only
-- **Filter** by integration or status using the filter button in the footer
-- **Sort** the current view by clicking column headers to switch direction
+- **Stats toggle** — show or hide the global stats bar in compact mode; advanced view always shows the stats bar without
+  changing the compact choice
+- **Pause / Resume** actionable queues using the footer controls
+- **Filter** rows by integration or status using the filter button in the footer
+- **Sort** by clicking sortable column headers; the default sort is configured per widget, while header changes apply to the current view
 
 <WidgetInteractionGuide />
 

apps/docs/docs/widgets/downloads/index.ts

@@ -30,19 +30,20 @@ export const downloadsWidget: WidgetDefinition = {
       {
         name: "Columns to show",
         description:
-          "Select the columns you want to display in the widget. Columns automatically hide/show based on widget width.",
+          "Select the columns you want to display in the widget. Compact layouts automatically hide/show selected columns based on widget width and height; advanced view keeps the selected columns visible.",
         values: `List of columns: ${columnsList.join(", ")}`,
         defaultValue: ["name", "progress", "downSpeed", "time", "state"].join(", "),
       },
       {
         name: "Default sort column",
-        description: "The column used for initial sorting when the widget loads.",
+        description:
+          "The column used for initial sorting when the widget loads. Clicking a column header changes the current view only.",
         defaultValue: "progress",
         values: `List of columns: ${sortColumns.join(", ")}`,
       },
       {
         name: "Invert sorting",
-        description: "This will invert the default sorting order.",
+        description: "This sets the initial sorting direction.",
         values: { type: "boolean" },
         defaultValue: "no",
       },
@@ -66,8 +67,7 @@ export const downloadsWidget: WidgetDefinition = {
       },
       {
         name: "Hide completed torrent under this threshold (in kiB/s)",
-        description:
-          "This will hide completed torrent entries that have an upload speed below the specified threshold.",
+        description: "This will hide completed torrent entries whose upload speed is below the specified threshold.",
         values: "Any number above 0, 0 to disable",
         defaultValue: "0",
       },
@@ -85,15 +85,16 @@ export const downloadsWidget: WidgetDefinition = {
         defaultValue: "no",
       },
       {
-        name: "Use filter to calculate Ratio",
-        description: "This will use the category filter when calculating the global torrent ratio.",
+        name: "Use category filter for global torrent ratio",
+        description:
+          "When enabled, the configured category/label filter is applied to the global torrent ratio. Footer client/status filters do not change this ratio.",
         values: { type: "boolean" },
         defaultValue: "yes",
       },
       {
         name: "Limit items per integration",
         description: "This will limit the number of items shown per integration, not globally.",
-        values: "Any number above 1",
+        values: "Any whole number from 1 upward",
         defaultValue: "50",
       },
     ],

apps/docs/docs/widgets/media-server/index.mdx

@@ -31,8 +31,12 @@ Sessions without user metadata remain visible and are labeled as an unknown user
 ### Screenshots
 
 import mediaTable from "./img/table.png";
+import mediaAdvancedView from "./img/advanced-view.png";
 
-<img src={mediaTable} alt="media-server-streams" width={128 * 3 * 1.5} height={128 * 1.5} />
+<div className="flex flex-col gap-1">
+  <img src={mediaTable} alt="Media server compact streams table" width={303} height={198} />
+  <img src={mediaAdvancedView} alt="Media server advanced view with stream summary" width={800} height={484} />
+</div>
 
 ### Supported Integrations
 

apps/docs/docs/widgets/weather/index.mdx

@@ -15,17 +15,20 @@ import { weatherWidget } from ".";
 
 The Weather Widget uses your location to display the current, highest and lowest temperature.
 In the compact view, select a condition icon or forecast day to open details with a mouse, keyboard or touch.
-The advanced view always combines current conditions with the full seven-day forecast, including humidity, wind,
-gusts, sunrise and sunset. Both views reuse the same cached Open Meteo response.
+The compact forecast shows up to the configured number of days. The advanced view combines current conditions with the
+available daily forecast, including humidity, wind, gusts, sunrise and sunset. Both views reuse the same cached Open
+Meteo response.
 
 ### Screenshots
 
 import forecastWeather from "./img/forecast.png";
 import currentWeather from "./img/current.png";
+import advancedWeather from "./img/advanced-view.png";
 
 <div className="flex flex-col gap-1">
-  <img src={forecastWeather} alt="weather forecast-5-days" width={128 * 4.5} />
-  <img src={currentWeather} alt="weather current" width={128 * 3} />
+  <img src={forecastWeather} alt="Weather compact forecast" width={238} height={112} />
+  <img src={currentWeather} alt="Weather compact current conditions" width={198} height={93} />
+  <img src={advancedWeather} alt="Weather advanced view with seven-day forecast details" width={800} height={484} />
 </div>
 
 <WidgetInteractionGuide />

apps/docs/docs/workshop/development.mdx

@@ -38,7 +38,6 @@ Point Homarr at the local services with:
 ```dotenv
 HOMARR_WEBSITE_URL=http://127.0.0.1:3003
 WORKSHOP_API_URL=http://127.0.0.1:8090
-WORKSHOP_WEB_URL=http://127.0.0.1:3003/workshop
 ```
 
 Restart `pnpm dev:docs` after changing the Docusaurus URL variables. If Homarr is also running, restart its `pnpm dev`
@@ -48,9 +47,9 @@ Workshop moderator promotion, logs, tests, backup, restore, stopping, and intent
 
 ## URL testing
 
-Docusaurus reads `HOMARR_WEBSITE_URL` and `WORKSHOP_API_URL` when it starts or builds. Homarr also reads
-`WORKSHOP_WEB_URL` when its server starts, so these values do not rely on `NEXT_PUBLIC_*` build variables. Test a
-separate API origin before release:
+Docusaurus reads `HOMARR_WEBSITE_URL`, `WORKSHOP_API_URL`, and `WORKSHOP_WEB_URL` when it starts or builds. Homarr uses
+`WORKSHOP_WEB_URL` for public Workshop links while API and documentation origins remain independent. These values do
+not rely on `NEXT_PUBLIC_*` build variables. Test separate origins before release:
 
 ```sh
 HOMARR_WEBSITE_URL=http://127.0.0.1:3003 \

apps/docs/docs/workshop/index.mdx

@@ -32,14 +32,12 @@ Homarr instance and are never included in a Workshop submission.
 
 ## Share your work
 
-1. Sign in to the Workshop with GitHub.
-2. Select **Share yours**.
-3. Choose **Custom Widget** or **Custom CSS**.
-4. Add the source, a short description, screenshots, and a changelog.
-5. Review and publish the submission.
+For a saved Custom Widget, open **Management → Custom Widgets**, use its action menu, and select **Publish to
+Workshop**. Review the public listing details and source URLs, then publish the credential-free export. Custom CSS and
+manual submissions can be shared directly from the Workshop website with **Share yours**.
 
-Export Custom Widget JSON from **Management → Custom Widgets → Export**. You can edit a submission later without
-changing its Workshop URL.
+Publishing creates the listing immediately. To update or delete it, review reports, or mark it outdated, open the
+Workshop website, sign in, and select **Yours**. Editing a submission does not change its Workshop URL.
 
 ## Voting, comments, and reports