lowsbarrel

Thanks, this is useful. Services are already decoupled from SvelteKit (routes, cron, queues, and workflows just build a Ctx and call them) and the database is standard Postgres via Drizzle. However, you're right that services still touch Cloudflare bindings directly (like [`env.EMAIL`](http://env.EMAIL) and `env.RATE_LIMITER`), so I'll likely wrap those in small Ctx interfaces to simplify testing and adapter swaps. I'm less sold on a full monorepo with ports-and-adapters for this template. it's meant to stay Cloudflare-opinionated and easy to ship without extra layers of indirection. That said, how do you typically split it: what stays in your core package versus the app, and do you keep Drizzle schemas in core or abstract them behind repositories?