Web / Development
Configuration
Keep application configuration explicit and provider credentials on the server.
Start with the environment example
The root .env.example is the configuration inventory. Shared validation lives in packages/config. Review the selected application environment and provider modes together; a local interface is not a production credential strategy.
The credential-free reference mode requires local/test application configuration and fake/local providers. Selecting a production provider changes the runtime requirements.
Keep secrets behind the API
Authentication secrets, database credentials, provider keys, Stripe secrets, and Trigger credentials are server-only. Never prefix them with NEXT_PUBLIC_ or EXPO_PUBLIC_. Do not print them during setup or include them in error responses.
The browser receives public configuration and allowed model aliases. Workspace ownership, entitlement decisions, budgets, and provider selection remain server-enforced.
Check a change before using it
Validate configuration through the existing config package and run the relevant deterministic tests. Use the separately opted-in provider smoke path when you are ready to verify real integrations.
pnpm test
pnpm check
pnpm build