[lesnik512]

The DI middleware is an outer middleware on dispatcher.update. aiogram's own ErrorsMiddleware is registered there first, so it wraps ours. When a handler raises, our middleware closes the update's child container. ErrorsMiddleware then calls the error handlers with the same data dict, which still holds the closed child. An @inject error handler that resolves a REQUEST-scoped dependency raised ContainerClosedError, and that error replaced the handler's original exception. auto_inject=True wraps error handlers too, so it had the same problem.

The same middleware instance is now also an outer middleware on dispatcher.errors. For an ErrorEvent it binds the failing Update and that update's event, so an error handler gets an open child of its own. Error handling also counts as in flight, so the shutdown wait covers it.

The error handler gets a second child, not the failing update's. Its REQUEST-scoped instances are fresh, and the first child's finalizers have already run by then. Sharing the first child would mean inserting our middleware ahead of ErrorsMiddleware, and aiogram's MiddlewareManager has no public insert. Its list is private.

The new test raises in a message handler and resolves a REQUEST dependency plus the event type in an @inject error handler. On main it fails with ContainerClosedError. All 53 tests pass with 100% coverage. CONTEXT.md now describes the second child.