Ji Kim

This commit **reverts** a previous change that aimed to parallelize Mocha tests for the **`merge-tree` DDS**, specifically addressing instability introduced in the **CI pipeline**. The original parallelization caused test failures, necessitating this **maintenance** action to restore stability. As a result, the test timeouts for `client.applyStashedOpFarm.spec.ts` and `client.reconnectFarm.spec.ts` are restored to 30 seconds, down from 300 seconds. This ensures **CI stability** by temporarily disabling the parallelization of these tests and preventing further regressions.

This commit **increases the LoaderDriver compatibility window** from 3 to 12 months, aligning it with the existing DriverLoader window. This **bug fix** addresses an issue where newer loaders (e.g., gen 5) would incorrectly reject older drivers (e.g., gen 1) due to a strict 3-month compatibility policy, leading to "The versions of the loader and driver are not compatible" errors. The change in `packages/common/client-utils/src/layerCompat.ts` updates the `LayerCompatibilityPolicyWindowMonths` constant, and `LayerCompatibility.md` is updated to reflect this new policy. This **improves backward compatibility** for client applications by allowing a wider range of loader and driver versions to interoperate.

This commit introduces a **new accessibility feature** to the **DevTools UI**, providing live region status announcements for screen reader users. It integrates a new `ScreenReaderAnnouncement` component into the `packages/tools/devtools/devtools-view/src/components/Menu.tsx` and `packages/tools/devtools/devtools-view/src/components/TelemetryView.tsx` modules. Specifically, activating the "Refresh Containers list" or "Refresh" telemetry buttons will now trigger auditory feedback like "Containers list refreshed" or "Telemetry events refreshed". This **enhancement** significantly improves the **accessibility** of the **DevTools** by ensuring critical UI actions provide appropriate auditory feedback for visually impaired users, utilizing visually hidden `role="status"` elements with `aria-live="polite"`.

This commit **disables the automatic build trigger** for **client packages** on the **LTS branch** within the CI/CD pipeline. This **temporary maintenance action** was implemented because the Real Service Stress Test pipeline for the LTS branch has been consistently failing. By removing the trigger, the project prevents further build failures and allows for a dedicated fix to be applied to the underlying issue without blocking other continuous integration processes. The **client package build process** for the LTS branch will now require manual intervention or a re-enabled trigger once the root cause of the stress test failures is resolved.

This commit **promotes key Fluid Framework devtools APIs** from `alpha` to `beta` within the **`devtools-core` package**. Specifically, the `IFluidDevtools` interface, along with `ContainerDevtoolsProps`, `ContainerRuntimeProps`, `FluidDevtoolsProps`, and functions like `initializeDevtools` and `tryGetFluidDevtools`, are now marked as `beta` for increased stability. This **API stabilization** effort includes adding `readonly` modifiers to interface properties, updating API reports, and adjusting API extractor configurations for beta entry points. The **API promotion** signifies increased confidence in the design and functionality of these interfaces and functions. This change enables **broader integration into partner repositories** with a more stable and reliable interface for development tools.

This commit introduces a **documentation improvement** to the **DevTools view**, specifically enhancing the `ContainerSummaryView` component. It adds **JSDoc comments** to key functions like `getStatusBadgeColor`, `containerStatusValueCell`, and `useContainerSummaryViewStyles` within `packages/tools/devtools/devtools-view/src/components/ContainerSummaryView.tsx`. This **enhancement** significantly improves the clarity and maintainability of the **DevTools UI** codebase, aiding developers in understanding its functionality.

This commit **enhances the `devtools-view` UI** by introducing several interactive and visual features, primarily within the **`Menu.tsx`** and **`ContainerSummaryView.tsx`** components. It adds **visual indicators** such as a red icon to highlight containers with recent data changes, displays icons for container connection and closed states, and enables the **removal of closed container instances** directly from the devtools interface. To support these UI capabilities, the **`devtools-core` package** was updated to include container read-only status and a `reason` field in `DataVisualization` messages, allowing the UI to distinguish between user-initiated actions and actual data updates. This work represents a **new capability** that significantly improves the **observability and management** of Fluid containers for developers.

This commit implements a **maintenance fix** by **increasing the timeout** for the `perf_unit_test_memory` job within the **benchmark pipeline**. Previously, this job was intermittently failing due to exceeding its 1-hour threshold by a small margin, as observed in CI failures. The timeout has now been extended to **90 minutes** in `tools/pipelines/test-perf-benchmarks.yml` to prevent these spurious failures. This change ensures the **stability and reliability of performance testing** for memory-related unit tests, allowing them to complete successfully without premature termination.

This commit performs a **revert** of a previous change, restoring the distinct handling of detached and attached blobs within the **`BlobManager`** in `packages/runtime/container-runtime`. This **fix** reinstates the original logic for blob lifecycle operations, including `getBlob`, `createBlobDetached`, and `getGCData`, and updates the `redirectTable` type. The change also adjusts snapshot and summary generation functions like `summarizeBlobManagerState` to align with the reverted behavior. This ensures the **correctness of blob storage, garbage collection, and summary data** by re-establishing the prior, more robust management of different blob states. Corresponding tests have been updated to reflect this restored functionality.

This commit introduces a **new capability** to the **`devtools-core`** package, enabling the registration and visualization of **`IContainerRuntime`** instances and their associated `DataObject`s. It adds `ContainerRuntimeDevtools` and the `DecomposedContainer` interface, along with a `registerContainerRuntime()` method to `IFluidDevtools`, to facilitate this deeper introspection. The work also includes a **refactoring** of the core devtools structure, extracting common logic into a new `BaseDevtools` class. This enhancement allows for more granular monitoring of Fluid applications at the runtime level, paving the way for improved debugging and future UI support in `devtools-view`.

This commit introduces a new **feature flag**, `canModifyContainerState`, within the **Devtools-view** package, defined in `devtools-core`. This flag controls the ability to modify a Fluid container's connection and lifecycle state directly from the DevTools user interface. The `ContainerSummaryView` component now conditionally renders an `ActionsBar` based on this flag, ensuring that state modification options are only presented for supported container types, such as `IContainer`, while being disabled for others like `IContainerRuntime`. This **new capability** provides granular control over DevTools functionality, preventing unsupported operations and enhancing the overall user experience.

This commit **refactors** the **`packages/framework/dds-interceptions`** package by updating its ESLint configuration to extend the **recommended Fluid Framework base configuration**, moving away from a minimal setup. This change enforces stricter linting rules and significantly enhances **type safety** within the `sharedDirectoryWithInterception`, `sharedMapWithInterception`, and `sharedStringWithInterception` modules. Specifically, it replaces `any` type annotations with `unknown` and introduces explicit type assertions for `Object.create` results, reducing potential runtime errors. Accompanying these core changes, the related test files were also updated to refine error handling types and add explicit type annotations to helper functions, ensuring consistency and robustness. This **maintenance** effort improves the overall code quality and reliability of the DDS interception mechanisms.

This commit delivers an **improvement** to the **Fluid Framework DevTools core** by **refactoring** the mechanism for generating unique identifiers for visualized Fluid objects. Instead of relying on `IChannel.id`, a new utility function, `getKeyForFluidObject`, is introduced to directly generate and manage unique stringified IDs for `ISharedObject`, `DataObject`, and `TreeDataObject` instances. This change primarily impacts the **data visualization** components and **default visualizers** within the `devtools-core` package, ensuring a more robust and explicit ID management strategy for internal DevTools operations and enhancing maintainability.

This commit introduces a **new capability** to the **`devtools-core`** package, enabling the visualization of `TreeDataObject` instances within the Fluid Framework DevTools. It adds specific visualization logic, including type-checking (`isTreeDataObject`) and a dedicated visualizer that intelligently reuses the existing `SharedTree` visualization infrastructure. To demonstrate and validate this **feature**, the **`devtools-test-app`** was updated with a new interactive Todo application built using `TreeDataObject`, allowing developers to inspect its structure directly. This enhancement significantly improves the debugging and understanding of applications leveraging `TreeDataObject` by providing clear, interactive insights into their data models.

This commit performs **maintenance** on the **`data-object/todo-app` example application**, specifically addressing code cleanliness. It **removes an unnecessary `console.log` statement** from the example's source, which was inadvertently left during development. This cleanup improves the example's clarity and prevents extraneous output, ensuring a more polished experience for users interacting with or learning from the `todo-app` demonstration.

This commit introduces a **new capability** within the **Aqueduct framework** by adding a public `sharedTree` accessor to the `TreeDataObject` class. This accessor **exposes the underlying `SharedTree` instance**, which was previously only internally accessible, via the `packages/framework/aqueduct/src/data-objects/treeDataObject.ts` file. The change is crucial for **enabling external inspection** of the `SharedTree`'s schema and content, directly supporting tools like **Fluid Devtools** to accurately visualize and debug `TreeDataObject` components.

This commit introduces a **new capability** to the **`devtools-core`** package, enabling the visualization of `DataObject` instances directly within the Fluid DevTools. It implements a `visualizeDataObject` function and new type guards (`isSharedObject`, `isDataObject`) to correctly identify and render these objects. A `VisualDataObject` wrapper is also added to facilitate access to private `root` directories for comprehensive inspection. The **`devtools-test-app`** is updated to demonstrate this feature, allowing developers to better understand and debug the internal state of their Fluid `DataObject`s.

This commit **refactors** the **`devtools-test-app`** by **correcting an invalid and redundant reference** to the `IFluidLoadable` interface within `packages/tools/devtools/devtools-test-app/src/FluidObject.ts`. Previously, the code incorrectly attempted to access `IFluidLoadable` as a property on `this.root` during the assignment of initial objects, which is semantically invalid for an interface type. This **maintenance** change simplifies the initialization logic by directly using `this.root`, as the underlying `SharedDirectory` object already implements `IFluidLoadable`. The fix improves code correctness and readability in the **`FluidObject`** component, specifically around the `hasInitialized` logic, ensuring proper handling of shared objects.

This commit introduces a **new capability** to the **Fluid Framework DevTools SharedTree visualizer**, specifically enhancing how it displays the **SharedTree's root field**. Previously, the visualizer incorrectly treated the root as a regular node, omitting crucial schema information; now, it accurately renders the **allowed types** and requirement status in the tooltip, even for empty roots. This **feature enhancement** primarily impacts the `devtools-core` package's data visualization components, providing a more complete and accurate representation of SharedTree schemas for improved debugging and inspection.

This commit **corrects a typo** and standardizes the application title within the **`devtools-test-app`**. Specifically, it updates the title's casing within the `useContainerInfo` function in `packages/tools/devtools/devtools-test-app/src/App.tsx`. This **maintenance** change enhances the consistency and professionalism of the **developer tools test application**'s user interface.