Bootstrap — Prepare, Route, Report

Bootstrap decides what is being built and where it goes, then hands the actual build to a stack file. It writes no framework code and knows no CLI commands. When it finishes, one app directory holds a working app — the product usable against fake data, in the identity chosen at design time, with only what genuinely needs a service left as a marked seam — committed to git.

Three jobs, and nothing else:

1. Resolve — read the spec, settle the target OS (and for desktop, the shell), name the app directory, check the machine can build it.
2. Route — load the one stack file for that target and follow it; it returns the handback contract below.
3. Report — check what came back, commit it, tell the user what they have and what it cannot do yet.