REST API

The interface uses the REST API under /api; it is not a separate execution path. Read endpoints return state immediately. Operations return 202 Accepted with a job identifier, and GET /api/jobs/<id> reports their progress, steps and log.

The principal resources are:

The commits of a worktree are read a page at a time. GET /api/worktrees/<name>/commits answers with the upstream, the branch the worktree was cut from, and what git log would print, newest first; each entry says whether the remote has it and whether it is the branch's own or the base's. ?skip=<n> is the page behind that one, /commits/<sha> one commit in full with the files it touched, and /commits/<sha>/diff?path=<path> one of those files. It is what the interface shows before a discard.

An operation is read a piece at a time. GET /api/jobs/<id> answers with its steps and its log, and with size: how much of the log that answer accounts for. Handing that back as ?since=<size> asks for what has been written in the meantime -- the answer then carries partial: true, its log is the piece to add to what you already have, and a step that was over before that point carries output: null rather than saying the same thing again.

Reading the whole of it every time is still correct and still supported; a composer install writes hundreds of kilobytes, and asking once a second is what the interface does.