.NET: Improve Hosted Agent LRA Resilient Recovery Sample

[Roger Barreto (rogerbarreto)]

Motivation & Context

Make the .NET Foundry hosted workflow resilience sample easier to follow and show why downstream services must tolerate repeated calls during recovery. Recovering workflow progress and replaying response events do not prevent an unfinished step from being executed again.

Description & Review Guide

• What are the major changes? Simplify the countdown executors and use one E2E flow for Crash and Shutdown. Run a SQLite-backed idempotent service in a separate process through the same E2E executable's --idempotent-service mode. Share IdempotentServiceClient between the hosted workflow and E2E. Replace the output converter's checkpoint callback with explicit checkpoint items handled by AgentFrameworkResponseHandler, add coverage for the marker, and update sample documentation and XML remarks. Ignore local launch settings for the Claw hosted sample.
• What is the impact of these changes? Makes the checkpoint coordination and process lifetimes explicit while preserving the existing recovery model. Repeated service calls reuse stored results instead of inserting duplicate operations. The client displays replayed output and reports the stored operation count. The examples explicitly distinguish service idempotency from exactly-once workflow execution and are not production implementations.
• What do you want reviewers to focus on? Checkpoint event ordering and cancellation/shutdown handling, the service remaining alive across hosted process replacement, and the distinction between replayed text and repeated downstream effects.

Related Issue

N/A

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR is linked to an issue and there is no other open PR for this issue (see Related Issue above).
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix). A workflow keeps the label and title prefix in sync automatically.

[Copilot]

🟡 Changes recommended

The hosted deployment has an unavailable sibling project dependency, and the E2E can mask failures while reporting success.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Simplifies resilient workflow recovery while demonstrating idempotent downstream operations through a SQLite-backed service.

Changes:

• Introduces explicit workflow-checkpoint items and handler persistence.
• Adds crash/shutdown recovery scenarios with an idempotent service.
• Updates deployment configuration, documentation, and tests.

File summaries

File	Description
OutputConverterWorkflowTests.cs	Tests checkpoint item emission.
OutputConverter.cs	Adds explicit checkpoint boundaries.
AgentFrameworkResponseHandler.cs	Persists checkpoint items in order.
Using-Samples/README.md	Updates resilience sample reference.
Using-E2E-Resilience.csproj	Adds SQLite and ASP.NET dependencies.
ServerProcess.cs	Manages child-process output and lifetime.
ServerManager.cs	Coordinates builds, services, and recovery.
Using-E2E-Resilience/README.md	Documents recovery and idempotency flow.
Using-E2E-Resilience/Program.cs	Runs crash and shutdown scenarios.
IdempotentService.cs	Implements the SQLite-backed service.
Hosted-Workflow-Resilient-Long-Running/README.md	Documents revised workflow behavior.
Hosted-Workflow-Resilient-Long-Running/Program.cs	Integrates idempotent operations and shutdown handling.
HostedWorkflowResilientLongRunning.csproj	References the shared client project.
azure.yaml	Configures service endpoint and scope.
.env.example	Adds local idempotency settings.
IdempotentServiceClient.cs	Adds the shared HTTP client.
ClawAgent.Hosted/.gitignore	Ignores local launch settings.
Directory.Packages.props	Pins Microsoft.Data.Sqlite.

Review details

• Files reviewed: 18/18 changed files
• Comments generated: 5
• Review effort level: Balanced

---

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