wave-based-dispatchlisted

# Wave-Based Dispatch The agent-side dispatch discipline for sequential WO chains. Same pillars as `parallel-agent-dispatch` — disjoint ownership, return contracts, shared-file exclusion — but the gates **between** waves are different from the gates **inside** a wave. This skill is those between-wave gates. ## When to Use This Skill | Use wave-based dispatch when… | Use `parallel-agent-dispatch` alone when… | Use `exclusive-lock-dispatch` when… | |-------------------------------|-------------------------------------------|--------------------------------------| | A later WO needs a file, type, or API the earlier WO defines | All WOs operate on disjoint, lock-free scopes | One tool holds an exclusive lock and N agents need its outputs | | A research probe (Ghidra decomp, spec experiment, API trace) gates downstream scope | Scope is fully known up front | Lock-holder is slow enough to amortise via pre-dump | | Two candidate agents would both modify the same shared manifest / tracker / build file | Shared-file exclusion list is small and stable | Pre-computed artefacts can replace re-running the lock holder | | A bug surfaced during orchestrator-apply needs the same context as the dispatched agent | Issues are recoverable inside a single wave | Lock contention is the only sequencing reason | The three skills compose: each wave is itself a `parallel-agent-dispatch`, lock-holding waves use `exclusive-lock-dispatch` for the pre-dump, and this skill covers the boundary between w