The dev tools move into the engine

The development dashboard and the browser IDE are no longer libraries your app builds. They are part of the engine.

Being written in the language they serve was elegant, and it also meant every app compiled them, carried them in its own build, and had to remember to list them. Tooling that costs an app build time is tooling people switch off, which is the opposite of what a dashboard is for.

As engine files they load only when the app is in build and debug mode, and only for requests under the dashboard path. An app pays nothing for them and configures nothing. A panel you have to set up is a panel that exists only on the machine of whoever set it up, and the person who most needs to see the routes of an unfamiliar app is the one who has configured nothing.

Nothing shrank in the move. The sections are still there: configuration, errors, the library list, the parsed nodes, the source, the generated PHP and the release build, which are all ways of looking at the same compiler from different distances.

Arriving in the same pass: a constants file naming the characters you type all day, and a small preload that warms the opcode cache for the three files every request touches. Both are the kind of change nobody notices, which is the point.