Interface DiPluginOptions

When true, resolving a token not registered in the container automatically falls back to the kernel's ServiceRegistry. The first successful fallback is cached as a singleton so subsequent resolves are fast. Explicit DI registrations always take precedence. Defaults to true, so a provider can inject a framework capability such as CAPABILITIES.LOGGER; false confines resolution to the container's own registrations.

Default lifecycle scope for providers registered without an explicit scope. Defaults to 'singleton'.