The artifact hash prefix 87a49 is ambiguous and might mean any of the following:
87a492fe4f2563722316d84fc4c7bcb2e6ecd2825b7cbb6dfc8850f31d708270 -
Nobody picks a filesystem path when they make a repository on a forge, and requiring one made repo.add usable only by the machine's operator. --repos-root gives the server somewhere to put them; path is now optional and the response says where it landed.
Repositories gain a description — every forge has one and quarry had nowhere to put it, so the listing could only show names and counts.
Three surfaces on one op: quarry repo new|clone|list|remove drives the HTTP API rather than the database, so the CLI has no privileged path and anything it can do a client can; /new is the same three questions a forge always asks; and an empty repository shows how to push to it instead of a bare file table, because it is waiting, not broken.
A rejected form comes back as a form with the reason on it — an error page throws the reader's input away. by dmestas on 2026-08-18 01:59:53.
87a498ebefe437f863219b151318f12d1813a044fbb926fe449b301dce9f80d3 -