Resiliency

The current repository does not contain a top-level .template.config/template.json. Treat packaging metadata as absent until the repo adds one.

Resiliency features must be documented from real source: retry policies, timeouts, circuit breakers, health checks, background retry loops, queue behavior, or generated infrastructure.

Current Evidence Points

• Appsettings files: 0
• Docker/compose files: 19
• Pipeline files: 2

If no resiliency implementation is present, consumers should rely on the generated app/runtime defaults and shared platform guidance.