Did Microsoft announce a replacement of "pac modelbuilder build"?

[tc-fertec]

I did not find a direct Microsoft statement saying: “replace pac modelbuilder build with X”.
The current docs still say that pac modelbuilder build is used to generate early-bound .NET classes for Dataverse tables, custom messages, and an OrganizationServiceContext-derived class. The same page also says that pac modelbuilder build replaced the older CrmSvcUtil.exe from Microsoft.CrmSdk.CoreTools. [learn.microsoft.com]
This creates an awkward state:

• Old tool: CrmSvcUtil.exe
• Replacement: pac modelbuilder build
• Now: pac modelbuilder is marked deprecated (LINK)
• But: no obvious official successor is documented yet

[petrochuk]

Model builder library is available here: https://github.com/microsoft/PowerPlatform-DataverseModelBuilder

[tc-fertec]

Thanks for pointing to the standalone Model Builder repo 👍
My main concern is actually about the deprecation of pac modelbuilder build itself.
From the current documentation and tooling evolution, the situation seems a bit unclear:

CrmSvcUtil.exe → replaced by pac modelbuilder build
pac modelbuilder build → now marked as deprecated
The GitHub repo provides the underlying library, but does not clearly describe the intended replacement workflow/tooling

Could you clarify:

Why pac modelbuilder build was deprecated? (e.g., architectural changes, shift to a different pattern, maintenance reasons, etc.)
What is the recommended approach going forward for generating early-bound classes?

Should we directly consume the ModelBuilder library?
Is there (or will there be) a new CLI command or tooling officially replacing it?

Right now it's not obvious how to align with the future direction, especially for automated/CI scenarios.
Thanks in advance for any clarification!