SiteScaffolder
Corex\Cli\Site\SiteScaffolder · class · CLI layer
Scaffolds a client site (spec 049) from one name: a site plugin (<slug>-site, namespace <Name>Site\) + a site theme (<slug>) with the client’s own prefixes (distinct from Corex), plus the governance set (AGENTS/CLAUDE/README/PROGRESS/DECISIONS/ .gitignore + specs/docs). Pure render-all-before-write (mirrors ApiResourceScaffolder): an unresolved placeholder fails loudly without a half-written site. No WordPress. Options: force, plugin_only, theme_only, starter. With starter (spec 053 US4) it also emits a runnable, client-namespaced example vertical slice (model → repository → service → controller-on-envelope → block → option page → test + REMOVE-EXAMPLE.md) and a starter-theme asset architecture (SCSS/JS + wp-scripts build + an Assets url/path/version helper); the default and --minimal omit it. With the governance set it also writes what lets the site take framework updates (spec 102): corex-baseline.json, UPDATING-COREX.md and, when told where the repository root is, the client’s own CI workflow. It is given the baseline; it never asks git for it.