The bridge documentation describes a host integration the repository had no end-to-end example of: only the AOT console sample existed, so the provider factory, startup warm-up and external-dependency verification were exercised by unit tests alone.
The sample runs an Awaiten container as the composition root of a minimal-API app and covers each documented claim with a request that goes over HTTP: scope alignment per request, transient freshness inside a shared scope, async-initialized singletons warmed before serving, `[ImportService<T>]` reaching host services, and keyed registrations bound through `[FromKeyedServices]`.
`dotnet run -- --smoke` starts the host on an ephemeral port, drives every endpoint and exits non-zero on failure, so this is a test rather than a demo — the same approach `Awaiten.AotSample` takes for native AOT.
The projection path is used deliberately; the README records why the full `AwaitenServiceProvider` replacement is unsuitable for minimal APIs today.
The bridge documentation describes a host integration the repository had no end-to-end example of: only the AOT console sample existed, so the provider factory, startup warm-up and external-dependency verification were exercised by unit tests alone.
The sample runs an Awaiten container as the composition root of a minimal-API app and covers each documented claim with a request that goes over HTTP: scope alignment per request, transient freshness inside a shared scope, async-initialized singletons warmed before serving,
[ImportService<T>]reaching host services, and keyed registrations bound through[FromKeyedServices].dotnet run -- --smokestarts the host on an ephemeral port, drives every endpoint and exits non-zero on failure, so this is a test rather than a demo — the same approachAwaiten.AotSampletakes for native AOT.The projection path is used deliberately; the README records why the full
AwaitenServiceProviderreplacement is unsuitable for minimal APIs today.