Publish an evidence-based release note

The problem

A commit or screenshot alone cannot establish that a release works for visitors.

Practical procedure

Record build revision, test results, known issues, deployed routes and independent live checks in one release note.

Worked scenario

A note might state 60 solver tests passed but mobile usability review remains pending.

Acceptance check

Do not assign a perfect score until acceptance criteria have independently verified evidence.

Apply the method

Use the related interactive tool to try the concept on an inspectable example. Record the starting assumptions and expected result before changing settings, then compare what the tool actually does. Where the result differs, keep the release marked experimental and document the discrepancy.

Further reading: Relevant primary technical documentation. This guide is an educational procedure, not a substitute for independent usability or compliance review.