LittleAlety/dsh-team-conductor

Control plane for the harness's own Agent Teams: members are ordinary independent sessions created through the same seam the GUI uses, each with its own model, so they open and continue like any other conversation while a sidecar roster and task board coordinate them. Task entries carry a definition of done, a member's completion is submitted and waits for the Lead's review, and availability tells idle apart from awaiting-review or a failed last turn. With delegationEngine=auto it uses independent sessions, continuable subagents, or the kernel roster depending on what the composition provides.