Design review: generated scaffold scope and ownership

[aatuh]

Context

Generated services are app-owned code. The scaffold should provide production-conscious HTTP defaults without turning api-toolkit into the downstream product architecture.

Review paths

• ROADMAP.md
• docs/scaffold-first.md
• docs/scaffold-support.md
• docs/full-service-scaffold.md
• docs/reference-service.md
• examples/reference-saas-api/README.md

Questions

• Is the split between saas-api and saas-api-full clear enough?
• Which generated assets are useful defaults versus product-domain assumptions?
• Where should regeneration expectations be stricter or more explicit?
• What should never be added to generated services by default?

Desired outcome

A scope recommendation for future scaffold changes, including any non-goals that should be stronger in docs or templates.