orchestrate

# Orchestrate Coordinate caller-authorized work through its existing tracker and runtime. Use the accepted task or conversation; a clear task needs zero mandatory skills. Selecting Orchestrate adds in-session guidance, not an AgentOps scheduler, work index, queue, ownership system, aggregate retry controller or delivery authority. The caller's tracker owns assignments and dependencies; its runtime owns running contexts, bounds and supervision; repository policy owns integration and delivery. ## Recover the actual work Read the accepted outcome, examples and scope from their current owner. Recover settled caller choices and rationale, completed history, consequential open questions and the next investigation from the existing native handoff. Do not repeat settled interviews or require the full transcript. Missing or contradictory pointers require source investigation, not a guessed decision. Before dispatch, inspect actual prerequisite content in the intended checkout, its identity and applicable evidence. A closed prerequisite whose bytes are missing, stale or unavailable is not usable readiness. Resolve that gap before dependent execution; preserve its native status and report the distinction. Inspect native assignments and runtime state together: task acceptance, observed worker/context identity, workspace and starting content, occupied write scope, pending checks and review, current candidate identity, and integration owner. Include active validators as well as writer...