Every RAXXO error message has to pass a one-rule test before it ships: a stranger with zero context has to know what broke and what to do next The three-part shape I use now, what happened, why, what to try, replaced years of generic error text across Git Dojo, OhNine, and Statusline Builder A support question that repeats twice is treated as a copy bug, not a documentation gap, and gets fixed in the interface itself Rewriting error copy after shipping is now routine maintenance, not...