Release notes often describe a change with phrases such as “improved performance” or “fixed several issues.” Those phrases sound finished, but they do not tell a reader what changed, who is affected, or whether any action is required. I built ReleaseProof to check that narrow problem. It takes two pieces of text: Change evidence, such as PR titles, issue summaries, test results, or a short diff summary. The release-note draft intended for users. The checker then looks for...