Write down what is broken
A Known issues section, and a correction to my own earlier description of a bug.
BariCare's README has a Known issues section. One entry corrects the README's own earlier description of a bug, which had been wrong. It also has a section on what is not built yet, sorted by what is blocking each item.
JamScript's README does the same for performance. It records the measured database latency before and after a region move, and says plainly what those numbers do not prove.
The first page a new reader sees should not be more optimistic than the code. A list of what is broken takes a few minutes to write and spares the next reader from finding each item the slow way.
BariCare's instructions for coding agents go one step further. They record two shipped mistakes and the check that would have caught each. Those two are the ones in the note An iPad is a Mac.