Standards for writing and reviewing CliHelper entries.
An entry is filed under the message a reader sees, not under the program that produced it. Several programs emit the same error for different causes, and an entry indexed by message can point that out where one indexed by program cannot.
Where two failures produce similar text but have different causes, the entry covers both and says how to tell them apart. Collapsing them into one page loses the part the reader actually needed.
Every causal claim is checked against the tool's source or documentation, or reproduced directly. Where the cause is a plausible but unconfirmed reading, the entry says so in those words.
Exit statuses are not standardised. Where a status is tool-specific rather than defined by a shell or a specification, the entry says which of the two it is, because that determines whether it can be relied on.
A change that holds until the next restart is a workaround and is labelled one. A change that addresses the cause is labelled differently. Readers make different decisions depending on which they are getting.
A reported inaccuracy is reproduced before the entry changes. No entry is edited down on the strength of a single report without checking.
CliHelper documents failure modes of third-party command line tools. No software is stored or distributed here.