Andrei Iacob

## Description This change doesn't affect any functionality, it just moves two classes outside of the `containerruntime.ts` file, which has gotten fairly large. ## Does this introduce a breaking change?...

The goal here is to have a prototype enabling one of the examples using the web loader with empty quorums.

Remove `DeltaScheduler` and `ScheduleManager` from the public API

1

## Description These are fluid internal classes which shouldn't be exported. ## Does this introduce a breaking change? yes

Getting this right is tricky, as installing packages need to happen before running any test, along with longer timeouts to allow for more time for the packages to be installed....

Some batching improvements part 1 (ScheduleManager) - work in progress

1

## Description Related to 743 in ADO. ## Does this introduce a breaking change? Yes, `ScheduleManager` now requires a callback to fetch the clientId in the constructor.

Same general idea as https://github.com/microsoft/FluidFramework/pull/11930 but it assumes there are no mix of concurrent runtimes using/not using aliasing.

The goal here is to move existing root datastores to aliasing, by aliasing their ids to themselves. This way, the root property of a datastore can have a single source...

Remove the 'experimental' notes from the grouped batching docs.

1

## Description This has been enabled for a while and running in Production for more than a month.

Azure client must use batching.

4

## Description `FlushMode.Immediate` will be deprecated soon. This is the only place where it is still being used, mainly due to the 1MB payload size limit which we've since fixed...

Nested datastores - part 2

2

### Description ADO:7302 Unifying the creation APIs of the runtime and the channel collection. From a functional perspective, this is moving the logic to actually create/fetch datastores from the runtime...