mesthiri — user guide¶
Four of six stages have now run for real. Every milestone has landed — dispatch, the shim workflow, all six stages, the sandbox — and the test suite drives a live pi process against a stub model server. What has since run against real models on a real repository: triage, code, review and fix have all done the job on
mesthiri/sandbox. What has never happened is a run ofprioritizeorretroagainst a real model, or an adopter outside that sandbox. This guide describes the experience mesthiri is built to deliver, written ahead of the code as a design tool, because a command that reads badly on the page will read worse in a terminal. Every transcript in this guide is designed, not captured. When something here turns out to be wrong once it is real, the guide is what changes first.
If a word here is unfamiliar or looks like it might mean two things, terminology.md defines it — including the several that genuinely are easy to confuse.
What you get¶
A repository that triages its own issues, implements the small ones, and opens pull requests you review. mesthiri runs entirely inside your existing CI — there is no server to operate, no database, and nothing listening on a port.
It never merges anything.