review-configuration

# Review configuration Run a **configuration-focused** review: environment and secrets handling, Cloudflare/wrangler setup, TypeScript and OXC configs, Vite and Wrangler configuration, build modes, and dev/staging/prod parity. Your reply must be a **plan of suggested changes**: concise, actionable, and structured-not only prose. ## Invocation Text after the slash command is additional scope/focus - narrow the review accordingly. If none given, use the default scope described below. ## Best practices alignment - **Secrets** - Never in repo or client bundle; use `.dev.vars` (workers) and wrangler env; document required vars in `.dev.vars.example`. - **Environment** - Clear split: client-exposed keys via Vite (`import.meta.env`, e.g. `VITE_*` if used); server-only secrets and config in Workers; build modes (development/production) consistent across tools. - **TypeScript** - Strict mode everywhere; shared configs from `@repo/typescript-config` (`strict.json` core → runtime presets); root solution `tsconfig.json` with project references; no conflicting compiler options between packages. - **OXC (oxfmt / oxlint)** - Single source of truth for format and lint; consistent rules; no conflicting formatters (e.g. Prettier). - **Cloudflare** - Wrangler and Vite build aligned; compatibility date and flags documented; bindings and env match usage; `front-app` assets (SPA) and `worker-api` worker entry configured correctly. Align with root [AGENTS.md](../../../AGENTS.md) and app AGEN...