Verify by real use

Verify a thing works by exercising it the way its real user will, not by trusting a proxy. The general principle behind any 'is it actually done' check, for ANY artefact — a game, a level, a UI, a document, a data export, a flow — not only code diffs. Use before reporting any build, feature, fix, game, or flow as done, working, verified, passing, or shippable, and treat it as a hard checkpoint whenever the evidence is a proxy: a green build, passing tests, a solver or automated checker, a headless run, an HTTP 200, or a string-grep, rather than the artefact being driven end-to-end. Especially important where a checker and reality can disagree: puzzle or level solvability,…