[.NET] Fix ConfigureDurableAgents and ConfigureDurableWorkflows not composing

[Shyju Krishnankutty (kshyju)]

Fixes #27

ConfigureDurableAgents(...) and ConfigureDurableWorkflows(...) could not be used together, forcing callers onto ConfigureDurableOptions(...).

Implementation: all three Functions extension methods now route through a shared ConfigureDurableCore, so the execution middleware is registered once with a predicate covering both agent and workflow entry points. At the core layer, separate markers track worker and client registration so a workerBuilder/clientBuilder supplied to a later call is no longer dropped. Both call orders now produce identical registrations.

Tests are committed separately (af0f0777b) and fail without the fix.

[Copilot]

Pull request overview

This PR fixes configuration composition so ConfigureDurableAgents(...) and ConfigureDurableWorkflows(...) can be used together (in any order) without forcing callers onto ConfigureDurableOptions(...), aligning Azure Functions and core IServiceCollection behavior with the intended additive options model.

Changes:

• Unifies Azure Functions configuration paths via a shared core registration method so built-in middleware/executor routing works for both agent and workflow entry points regardless of call order.
• Fixes core DI registration so workerBuilder / clientBuilder provided in a later Configure* call are no longer silently ignored.
• Adds regression tests plus sample/docs updates and changelog entries documenting the supported, composable configuration experience.

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
dotnet/tests/Microsoft.Agents.AI.Hosting.AzureFunctions.UnitTests/FunctionsDurableConfigurationCompositionTests.cs	New regression tests validating built-in entry points route to BuiltInFunctionExecutor and middleware/executor are registered once.
dotnet/tests/Microsoft.Agents.AI.DurableTask.UnitTests/DurableConfigurationCompositionTests.cs	New regression tests validating additive agent/workflow registration and honoring worker/client builders across multiple calls.
dotnet/src/Microsoft.Agents.AI.Hosting.AzureFunctions/FunctionsApplicationBuilderExtensions.cs	Refactors durable configuration into a shared core path and expands middleware predicate coverage to include workflow entry points.
dotnet/src/Microsoft.Agents.AI.Hosting.AzureFunctions/CHANGELOG.md	Documents the Azure Functions composition fix.
dotnet/src/Microsoft.Agents.AI.DurableTask/ServiceCollectionExtensions.cs	Splits “core shared services” registration from worker/client registration so later worker/client builders are honored without duplicating shared services.
dotnet/src/Microsoft.Agents.AI.DurableTask/DurableServicesMarker.cs	Introduces dedicated markers for worker/client configuration to support composition across calls.
dotnet/src/Microsoft.Agents.AI.DurableTask/CHANGELOG.md	Documents the core IServiceCollection builder-composition fix.
dotnet/samples/DurableWorkflows/ConsoleApps/04_WorkflowAndAgents/Program.cs	Updates sample narrative to reflect that all three configuration methods compose additively.
dotnet/samples/DurableWorkflows/AzureFunctions/05_WorkflowAndAgents/README.md	Updates sample docs to show separate, composable ConfigureDurableAgents + ConfigureDurableWorkflows usage (and optional ConfigureDurableOptions).
dotnet/samples/DurableWorkflows/AzureFunctions/05_WorkflowAndAgents/Program.cs	Switches sample implementation to separate composable configuration calls.
docs/features/durable-agents/README.md	Updates feature documentation to explicitly describe hosting workflows alongside agents using composable calls.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 11 out of 11 changed files in this pull request and generated no new comments.

Suppressed comments (2)

dotnet/tests/Microsoft.Agents.AI.Hosting.AzureFunctions.UnitTests/FunctionsDurableConfigurationCompositionTests.cs:51

• The built-in entry point routing tests don't cover all entry points that EnsureMiddlewareRegistered routes to BuiltInFunctionExecutionMiddleware (notably the agent MCP tool trigger, workflow MCP tool trigger, and workflow HTTP response entry point). Adding these cases would better protect against regressions in the shared predicate and ensure composition works for all built-in triggers.

    public static TheoryData<string> BuiltInEntryPointNames() =>
    [
        "AgentHttp",
        "AgentEntity",
        "WorkflowOrchestrationHttp",
        "WorkflowOrchestration",
        "WorkflowActivity",
        "WorkflowStatusHttp",
    ];

    private static string ResolveEntryPoint(string name) => name switch
    {
        "AgentHttp" => BuiltInFunctions.RunAgentHttpFunctionEntryPoint,
        "AgentEntity" => BuiltInFunctions.RunAgentEntityFunctionEntryPoint,
        "WorkflowOrchestrationHttp" => BuiltInFunctions.RunWorkflowOrchestrationHttpFunctionEntryPoint,
        "WorkflowOrchestration" => BuiltInFunctions.RunWorkflowOrchestrationFunctionEntryPoint,
        "WorkflowActivity" => BuiltInFunctions.InvokeWorkflowActivityFunctionEntryPoint,
        "WorkflowStatusHttp" => BuiltInFunctions.GetWorkflowStatusHttpFunctionEntryPoint,
        _ => throw new ArgumentOutOfRangeException(nameof(name), name, "Unknown built-in entry point."),
    };

dotnet/src/Microsoft.Agents.AI.Hosting.AzureFunctions/FunctionsApplicationBuilderExtensions.cs:70

• The parameter indentation on ConfigureDurableWorkflows is off by one space compared to the rest of the file, which makes the signature formatting inconsistent and harder to scan.

    public static FunctionsApplicationBuilder ConfigureDurableWorkflows(
         this FunctionsApplicationBuilder builder,
         Action<DurableWorkflowOptions> configure)