Hi Christopher, Eric, Jochen, Thanks for laying out the options. GROOVY-11143 is still the right place to track this, and Jochen's split between today's extension methods / dynamic categories and a true "static category" (lexically scoped, static-friendly) matches how I see the gap.
Kotlin-style static import of extension methods in the same compilation unit would remove real friction for DSL and LLM tooling work, but it is a new feature rather than a small tweak: we need clear rules for dynamic vs static, how far the effect reaches, and how it interacts with the manifest-based path. I am in favour of advancing that design on the JIRA (and a short GEP if the surface grows), and I am happy to help review concrete proposals. Cheers, Daniel Sun
