What
Hundreds of lazily initialised module bodies are now plain top-level values, and several call sites reach other modules by requiring a numbered chunk file at runtime instead of an in-bundle handshake. Nothing changes for users, but more of the CLI's own code now sits behind chunk boundaries that are opaque to inspection.
Details
- Flattened contents include schemas, sets, regexes, AWS and Bedrock service metadata, and slash-command descriptors.
- Call sites now using a chunk require include the MCP resource prefetcher, safe git executable resolution, the brief-mode check and session id compatibility conversion.
Evidence
import.meta.require("/$bunfs/root/chunk-XXXXXXXX.js")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.