React

A React front end scaffolds as a web service in its own directory, so it can sit alongside a separate backend without either plan touching the other’s files.

React fills the web role#

Naming React answers "what is the front end?" but not "what serves the data?" — so a request that also needs an API produces a two-service plan with disjoint directories.

Disjoint by construction is the point: the planner never has to negotiate which task may touch which file, because the layout already answers it.

It has to actually serve#

Install, then production build, then the preview server is started on a loopback port and its routes are requested. A build that produces no output, or a server that starts and does not answer, fails.

A failure here feeds the same repair loop the integration tests use — up to three fixer rounds, with scope widened to every path the plan touched, re-probing after each.

StacksNext.jsNext.js serves its own API, so naming it answers the "do we need a separate backend?" question — and it gets the full verification treatment, up to and including being started.StacksNode.jsNode fills the backend role. It gets the full verification path, including being started and asked whether it is alive.FeaturesVerificationEvery gate used to reason about the tree without ever starting it. Now the tree has to compile, the suite has to run, and the application has to boot and answer before anything is called finished.