services

Overview ¶

Command services is the harness's domain worker (plan items P3.5, P3.10).

It runs the three background workloads §1.2 defines — a 50k-row SQLite import, a full-text re-index over them, and a 2MB JSON decode — none of which belong on the render thread. That relocation IS v5's thesis: heavier work takes longer to complete, never longer to paint.

The v4 harness ran all three on the render thread and measured a loaded p95 frame of 1633 ms against a 16.8 ms idle frame. This binary exists so the same harness can measure the same workloads with them somewhere else.

It speaks a deliberately small protocol, because the point of the measurement is where the WORK runs, not how elaborate the messaging is:

in   {op:"start"|"stop", workload:"import"|"reindex"|"decode"}
out  {workload, completed, err}   progress, posted as it happens