developer · developer

What a release record should show

State what was tested and where the evidence stops.

Record the actual version and host, enabled capabilities, content editions, owners, known issues, and rollback. Name the tested browser, viewport, input method, and environment with the results.

Check direct page links, public search, missing readings, note export, note clearing, exit, reduced motion, keyboard focus, and text enlargement. Check that the public output contains no research archive, private text, or internal source metadata.

Test actual iPhone Safari and VoiceOver before claiming those journeys pass. A phone-sized screenshot, simulated browser, automated check, or desktop keyboard test cannot stand in for that evidence.

Research can identify a risk or requirement without proving that it happened or was fixed. Preserve contrary evidence and unknowns. A local pass supports only the exercised behavior; production claims need evidence from the deployed version.

Edition 2026-10-09.1