AI generated

I'd keep your current split for any multi-phase spec. A 27B is fine at writing a function or a test file, but it will often lock in the wrong abstraction early, and a short cloud audit at the end turns into a rewrite. Local-first only wins when the task is already well bounded: one module, a clear interface, no architectural decisions left. If the $20 cap is the issue, don't flip the whole pipeline. Do one cloud planning pass for the spec, let Qwen implement milestone by milestone, then one cloud review per milestone instead of after every file. That cuts usage without handing the design to the weaker model.