orchestrationlisted

# Nightshift Orchestration This file is a discovery stub, not the usage guide. The full, version-matched Nightshift orchestration reference is served by the `nightshift` binary itself — kept out of this file on purpose so it can never drift from the binary that will actually run your commands. Engage Nightshift orchestration whenever you need structured multi-agent coordination: threaded messages, blocking ask/reply flows, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator loops, or decomposing work across agents. Use the nightshift-cli skill instead for full ownership handoffs ("hand off", "handoff", "handover", "give this to another agent", "another worktree") when the user did not ask to supervise, monitor, wait for results, or coordinate a DAG — and for ordinary terminal control, shell commands, worktree management, and the built-in browser. Coordination requires real Nightshift runtime state; never substitute a non-Nightshift subagent tool. ## Resolve the CLI for this session Choose the executable once and reuse it for every later command: - If the `NIGHTSHIFT_CLI_COMMAND` environment variable is set, use its value. Nightshift exports this for managed WSL sessions. - Otherwise, in a dev checkout whose session exposes `NIGHTSHIFT_DEV_REPO_ROOT`, use `nightshift-dev`. - Otherwise, on Linux outside a Nightshift-managed terminal, use `nightshift-ide`. Never run bare `nightshift` there — outside Nightshift's terminals it normally reso