Fixed the visual briefing scrolling and raise it to beta (#954)

app/MindWork AI Studio/Assistants/VisualBriefing/VisualBriefingAssistant.razor

@@ -6,14 +6,18 @@
 
 <CascadingValue Value="Components.VISUAL_BRIEFING_ASSISTANT">
     <CascadingValue Value="@this.CurrentMediaOwner">
-        <div class="visual-briefing-shell">
-            <PreviewPrototype ApplyInnerScrollingFix="true"/>
+        @* The assistant does not inherit AssistantBase, so it sets up the inner scrolling itself, the
+           way the log viewer does. A plain div is enough here: unlike AssistantBase, this assistant
+           deliberately has no area-wide drop zone, because its two zones have to be aimed at. *@
+        <div class="inner-scrolling-context">
+            <PreviewBeta ApplyInnerScrollingFix="true"/>
             <MudStack Row="true" AlignItems="AlignItems.Center" Class="mb-3 mr-3" StretchItems="StretchItems.Start">
                 <MudText Typo="Typo.h3">@T("Visual Briefings")</MudText>
                 <MudSpacer/>
                 <MudIconButton Variant="Variant.Text" Icon="@Icons.Material.Filled.Settings" OnClick="@this.OpenSettingsDialogAsync"/>
             </MudStack>
 
+            <InnerScrolling>
                 <MudList T="Guid"
                          Color="Color.Primary"
                          Class="mb-1"
@@ -334,6 +338,7 @@
                         }
                     }
                 </main>
+            </InnerScrolling>
         </div>
     </CascadingValue>
 </CascadingValue>

app/MindWork AI Studio/Assistants/VisualBriefing/VisualBriefingAssistant.razor.css

@@ -1,10 +1,3 @@
-.visual-briefing-shell {
-    height: 100%;
-    min-height: 0;
-    overflow-x: hidden;
-    overflow-y: auto;
-}
-
 .visual-briefing-main {
     min-width: 0;
     padding-bottom: 1rem;

app/MindWork AI Studio/MindWork AI Studio.csproj

@@ -137,4 +137,30 @@
         
     </Target>
 
+    <!--
+        Scoped CSS (`.razor.css`) is bundled into `$(AssemblyName).styles.css`, which App.razor links.
+        That bundle is generated at build time, so it never lives in the source tree's wwwroot. The
+        release build, though, serves static files solely from the ManifestEmbeddedFileProvider (see
+        Program.cs), fed by the `wwwroot\**` EmbeddedResource above. Without this target the bundle is
+        therefore missing at runtime and every scoped rule is dropped without a word, while the debug
+        build keeps working through the static web assets. Hence: build the bundle, then embed it
+        before the manifest is written.
+    -->
+    <Target Name="EmbedScopedCssBundle" DependsOnTargets="GenerateScopedCssFiles" BeforeTargets="_CalculateEmbeddedFilesManifestInputs">
+        <PropertyGroup>
+            <ScopedCssBundleToEmbed>$(IntermediateOutputPath)scopedcss\bundle\$(AssemblyName).styles.css</ScopedCssBundleToEmbed>
+        </PropertyGroup>
+
+        <!--
+            Fail loudly instead of shipping a release without the bundle: a missing file here means the
+            SDK changed where it writes the bundle, and every scoped rule would silently vanish again.
+        -->
+        <Error Condition="!Exists('$(ScopedCssBundleToEmbed)')"
+               Text="The scoped CSS bundle was not found at '$(ScopedCssBundleToEmbed)'. Without it, the release build serves no scoped CSS at all. Check where the SDK writes the bundle and adjust the EmbedScopedCssBundle target." />
+
+        <ItemGroup>
+            <EmbeddedResource Include="$(ScopedCssBundleToEmbed)" Link="wwwroot\$(AssemblyName).styles.css" />
+        </ItemGroup>
+    </Target>
+
 </Project>

app/MindWork AI Studio/Settings/DataModel/PreviewVisibilityExtensions.cs

@@ -14,6 +14,7 @@ public static class PreviewVisibilityExtensions
             features.Add(PreviewFeatures.PRE_DOCUMENT_ANALYSIS_2025);
             features.Add(PreviewFeatures.PRE_META_ASSISTANT_V1);
             features.Add(PreviewFeatures.PRE_RAG_2024);
+            features.Add(PreviewFeatures.PRE_VISUAL_BRIEFING_ASSISTANT_2026);
         }
         
         if (visibility >= PreviewVisibility.ALPHA)
@@ -22,7 +23,6 @@ public static class PreviewVisibilityExtensions
         
         if (visibility >= PreviewVisibility.PROTOTYPE)
         {
-            features.Add(PreviewFeatures.PRE_VISUAL_BRIEFING_ASSISTANT_2026);
         }
         
         if (visibility >= PreviewVisibility.EXPERIMENTAL)

app/MindWork AI Studio/wwwroot/changelog/v26.9.1.md

@@ -16,3 +16,5 @@
 - Improved loading web content in the assistants: it now uses the same reader as the Read Web Page tool, which extracts the main content of a page more reliably and skips navigation and boilerplate. Pages from your own network, including local servers, keep working as before. When a page cannot be read, AI Studio now says why instead of leaving the field empty.
 - Changed how provider trust and provider confidence work together. Marking a provider as trustworthy in a configuration no longer also satisfies a required confidence level: one says who runs the provider, the other how confidential it is. Organizations raise a provider's level in their own confidence scheme instead. This applies beyond local data sources, for example, when a model reads a page from your intranet.
 - Fixed a dropped file being processed several times, e.g., after the computer woke up from sleep.
+- Fixed the Visual Briefing Assistant (in preview) not scrolling, which put everything below the window edge out of reach and made the assistant unusable. The briefing preview is now shown at its intended size inside its frame, and switching between the desktop, tablet, and mobile view changes its width as it should.
+- Upgraded the Visual Briefing Assistant (in preview) from the prototype to the beta state. The assistant is now completely implemented and is undergoing a deeper testing phase in preparation for release. To try it, open the app settings, allow preview features down to beta, and then enable the Visual Briefing Assistant there.