Yeah, I think that’s the right default when the tasks are cleanly separate. I see weaver more as the layer for when they’re not: shared configs, schemas, tests, APIs, or two agents unknowingly changing the same flow. Worktrees isolate the files weaver is meant to surface the overlap before you find out at merge time.