Shared by both generators so the defaults cannot drift between entity subclasses and
GraphQL resolvers — they must agree, or one emits per-schema while the other emits a
monolith and the two rosters stop lining up.
parallel / concurrency are resolved for every caller even though only the entity
generator uses them: its per-schema assembly is async (each file awaits its entities),
while GraphQL assembly is synchronous, so there is nothing to overlap there.
Fill in a partial SchemaEmitOptions from config defaults.
Shared by both generators so the defaults cannot drift between entity subclasses and GraphQL resolvers — they must agree, or one emits per-schema while the other emits a monolith and the two rosters stop lining up.
parallel/concurrencyare resolved for every caller even though only the entity generator uses them: its per-schema assembly is async (each file awaits its entities), while GraphQL assembly is synchronous, so there is nothing to overlap there.