# The rows a graph is drawn from

`GET /api/v1/snapshot`

Not on the MCP surface. It is served over REST only.

Every other view answers a question; this one answers none. It returns the tasks, edges, waits and references the scope can see, so a browser holding `@terezinha-flow/graph` computes the same readiness this server computes — same arithmetic, same rows.
The whole visible graph rather than a window, because readiness rests on the whole graph: a body narrowed to one project would carry blockers it could not see and report tasks as ready that are not. Narrow what is *drawn* in the client, or use `GET /api/v1/tasks` to have the narrowing done here.
`neighbours` is empty while this operation takes no window: it returns the whole graph you can see, so there is nothing outside it to reach. The field is here because the body is the graph the arithmetic takes, and a windowed read on this path is what would fill it.

## Responses

- `200` — The rows, flat