The dev panel that mounts itself

Set build: true and debug: true and the Phlo Control Center is there at /phlo. No package to install, no route to declare, no configuration.

That is deliberate. A development panel you have to set up is a panel that exists on the machine of whoever set it up, which is exactly the wrong distribution: the person who most needs to see the routes of an unfamiliar app is the one who has not configured anything. So the condition is the condition you are already in. You are in build mode with debug on, therefore you are developing, therefore the panel is useful.

It shows what the engine already knows: the routes it compiled, the views and resources in the app, the last errors with their source-mapped .phlo file and line, and the request trace. The same material is available from the CLI through reflect::, because the panel is a view onto the introspection layer rather than a thing of its own.

Two escape hatches, both one word. control: 'admin' moves it if /phlo collides with something of yours, and control: false switches it off. Outside build plus debug it is off regardless of what you say, so a release build has no panel to forget about.

Worth keeping the names apart: the Control Center is the per-app dev panel described here. The Phlo Dashboard is the separate application that manages a fleet of machines.

Engine 1.0. See the runtime configuration chapter.