@philliphoff has proposed the integration on the Aspire Community Toolkit (and has done the preliminary work on in too), so I think it's an important question to ask of where this integration should land, Aspire "core" or the Community Toolkit.

Currently, all Azure integrations, with the exception of Dapr, are in the Aspire repo, but is that going to be sustainable long term?

Yes it is. The azure integrations long term will be owned by the azure/azure sdk teams and shouldn’t be in the toolkit.

I don't have a huge preference, other than prefer it not be moved again like Dapr. If it's preferred to have the DTS integration in dotnet/aspire, I'll port the bits and submit a PR there.

This is related to functions right? Maybe it becomes part of the functions package? Or is it something that can be used independently to functions?

Dapr is not native to Azure the way that DTS is

This is related to functions right? Maybe it becomes part of the functions package? Or is it something that can be used independently to functions?

It's lumped together with Azure (Durable) Functions and is exposed as an additional backend option, but DTS can be used completely independent of Azure Functions (e.g. from one's own compute). The extension for Azure Functions for VS Code contains the IDE integration for DTS, so it would probably be consistent to place it into the Azure Functions package. That said, there's less overhead for new packages than IDE extensions so I could also see DTS in its own "Durable Task" package. too.