Repo Query

Answer a SQL question about this tree. SELECT only, always read-only.

THE FRONTMATTER IS THE SCHEMA. Every key: value in the tree becomes a row in fields, so a field this shop invented this afternoon is queryable this afternoon and nothing has to be added here for it to work. The columns on docs are only the concepts the whole product already shares a definition of — settled, waiting, due — promoted so that this route and the open-loops block cannot come to disagree about the same file.

THE WORKING TREE, NOT THE BARE REPO. _repo_for falls back to a bare repository, which is right for browsing a ref and wrong here: this reads files off disk, and a bare repo has none. It is a 409 rather than a silent empty result, because "no rows" and "nowhere to look" are different answers and a model cannot tell them apart.

THE BODY IS {"sql": "SELECT …", "limit": 60} — and query, q, select and statement land on the same field, because no code in this repository writes this body and a model that guessed one of those was refused for a word rather than for a mistake. See TreeQuery.