Coordinators run threads as separate processes

Yolop’s session coordination now uses the Everruns coordination capability, the same one Everruns Platform Chat runs, in place of Yolop’s own worker pool. Each thread runs as a headless yolop --serve process in its own worktree, supervised and restarted by its coordinator, so threads keep working while the coordinator is closed.

Enable coordination in a profile and start a session with it. The TUI opens a THREADS board in the activity rail; Enter on a row opens that thread, and quitting it returns to the coordinator. A thread’s sandbox escalations are asked in the coordinator’s approval prompt. yolop sessions live lists running sessions and threads.

See Session coordination, #835 and #837.