How are you managing the use of explicitly spawned subagents?

I’d separate exploratory subagents from release-boundary subagents. During exploration, I agree not every child needs a full matrix run; that can turn orchestration into ceremony. But before anything touches a shared branch, production surface, or customer-visible state, the orchestrator should require a small closeout: files changed, tests run or intentionally skipped, known risks, and why the child stopped. If we describe subagents as junior devs, that is exactly why the receipt matters. The trick is keeping the receipt cheaper than another rerun.