VSF2 replaces VSF1 static config with split middleware.config.js and public runtimeConfig
A team is porting a multi-store VSF1 theme to VSF2 and must decide where each former config/default.json key belongs now that configuration is split between server middleware and public runtime config. In VSF1, one static tree was visible to both server and client and fixed at build time. VSF2 instead reads server-only values from middleware.config.js and br