Ark DI public beta tested scopes, ownership, and teardown as one contract
The 0.1.0-dev.1 core and Flutter releases exposed typed registrations, async initialization, hierarchical scopes, ownership, and lifecycle-safe hosting.
A dependency container must also explain who closes what
The public beta of ark_di and ark_di_flutter introduced typed and named registrations, transient and lazy strategies, shared async initialization, hierarchical child scopes, parent overrides, cycle detection, and dependency-ordered teardown. Flutter added root and child scope hosting with controlled BuildContext lookup.
The beta treated ownership as a first-class contract. Ready instances could remain externally owned, while another registration could assign its disposer to a scope. Async initialization was shared between concurrent resolutions and became retryable after failure. The optional service-locator adapter stayed isolated rather than becoming implicit global state.
The beta packages remain in the pub.dev version history. Current applications should use the stable 1.0.0 line.