The builder, pane by pane

Four panes, and the useful half of this page is what each one does not show. A pane that looks like it reports everything, and reports some of it, is worse than one that says where it stops.

Preview

Until you start a sandbox, this is a local mock: static HTML assembled from the accepted plan and stylesheet, rendered in a fully restricted frame. No dependencies are installed and no generated code is executed. It is a picture of the intent, not a run of the project.

Once a sandbox is running, the frame is the sandbox and the mock is gone. The two are never shown side by side, because a stale mock next to a live copy of the same project invites exactly the wrong conclusion about which one you are looking at.

A sandbox serves the checkpoint it was started from. Accept a later one and the frame says so and asks you to restart it. It does not silently become the new project.

Code

The generated files, as files. This is the pane to read before accepting anything.

While a newer checkpoint is staged, the list shows the staged files, but the Export, Push and Publish buttons beneath it act on the last accepted checkpoint. The pane says so when the two differ, because a button that acts on something other than the list above it is a trap.

Console

Generation lifecycle events: what the run is doing, when it started, when it finished, what it cost.

It is not the sandbox’s output. Sandbox execution is real, but its process output is not piped into this pane yet. If your project logs something at runtime, that log is in the sandbox, not here.

Problems

Validation findings for the staged project: what vibld’s own checks found in the files before you accepted them.

It is not the sandbox’s errors. Install failures, build failures and type errors from a sandbox run are not reported here yet. A sandbox that fails to start says so in the Preview pane, which is currently the only place that knows.

The header and the footer

The header reports which provider and model served the last run, your tier, and this period’s spend against your allowance. It claims nothing before there has been a run.

The footer carries the two limitations above in one line, for anybody who never opens those tabs. It is built from the same source the panes are, so it cannot drift away from them.

Where this is going

Both gaps are about wiring an existing thing into a pane, not about building the thing. The sandbox already produces the output and the errors. Until they arrive here, this page and the panes themselves will keep saying so.