Ant Design static message and Modal methods bypass ConfigProvider theme and locale context

Ant Design's static message, notification, and Modal.confirm methods are documented as imperative helpers that render outside the normal React component tree. In applications that rely on ConfigProvider for dynamic theme tokens or locale switching, these static calls are expected to use default styling and default language strings rather than inheriting the surrounding context.

The library provides the App component and App.useApp() hook as a context-aware alternative, but adopting them requires refactoring existing call sites and may affect test mocks or utility wrappers. Because the static methods remain context-unaware for backward compatibility across major versions, teams need to decide whether to migrate call sites or accept the visual and language mismatch.

When planning a repeatable development environment, it is unclear how much of the ConfigProvider context is intentionally excluded from static methods versus an implementation detail that might change. The exact boundary between context-aware and context-unaware calls also depends on where the App wrapper sits in the component tree.

Which ConfigProvider properties are guaranteed to be ignored by static message, notification, and Modal methods in current major versions? Does the App component restore both theme token and locale context for all three static APIs, or only for a subset? What is the recommended placement of App so that imperative calls from nested components still receive the intended context?