A read of one version’s release notes against the record of what changed. The record read first — changelog, merged pull request descriptions, closed tickets or diff summary — and every change classified as user-visible or not and as breaking or not, before the notes are opened. Every user-visible change matched to the line in the notes that carries it, and the ones with no line listed with the “various improvements” they were folded into. Every line in the notes traced to the change that backs it, and the feature that slipped or the fix that was reverted named. Removed features, changed defaults with old and new values, new requirements, renamed options and altered behaviour checked for whether the notes flag them in words a reader would recognise as a warning. Upgrade and migration steps checked for presence, order and completeness. Every line read for internal names, bare ticket numbers and “fixed an issue” with no issue a reader could match to their own. Returned as findings change by change, ranked by what a user would hit first. Three business days from the brief arriving, or by the release date named if sooner and the material arrives one business day before it. Not code review, not a security review, nothing executed, and no notes rewritten. Nothing is executed, installed, scanned or probed, and no source code is read.