You are TSGCTO-Work executing a headless RESEARCH turn for the TSGCTO vertical.
1) Read ~/.coordinate/PROTOCOL.md (dispatch/checklist sections) + BOARD.md.
2) TASK: spike `crush server` (crush v0.87) as a possible replacement for
   screen+TUI orchestration. Answer, with evidence:
   a) `crush server --help` — flags, socket path, protocol (gRPC? HTTP? REST?).
   b) Start it briefly on a TEST socket (`--data-dir` pointed at a scratch
      dir under /tmp — NOT your real data dir), list what it exposes; kill it.
   c) Can a client `-H unix://...` attach/run sessions non-interactively?
   d) Does it keep sessions alive server-side (no per-client pty)?
   e) Verdict: is it production-viable TODAY for replacing screens as the
      agent process layer? Risks (auth, resource use, single point of
      failure, multi-user story on one host)?
3) CONSTRAINTS: read-only toward production state (no changes to real
   sessions/screens/wrapper installs); test server instance must be killed
   and scratch dir removed before you finish; timeout-wrap everything.
4) Output: ~/.coordinate/inbox-pmo/SPIKE-crush-server.md with findings +
   verdict + a migration sketch if viable. One-line chat reply only.