docs(review-policy): verify also checks each merged row's reader (GST-1406 follow-up) (#4019)

* docs(review-policy): verify also checks each merged row's reader (GST-1406 follow-up)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* chore: changelog fragment for the verify-reader docs line

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

changelog.d/gst-1406-verify-reader-doc.md

@@ -0,0 +1,3 @@
+### Fixed
+
+- **docs/review-policy.md now says `verify` checks each merged row's reader.** Since GST-1406, `gstack-review-dispatch verify` checks every merged row's reader, label and raw text against the output collect parsed. The policy text named only the label and raw text. This is the documentation debt #4017 shipped with.

docs/review-policy.md

@@ -798,7 +798,7 @@ ones, and the arm lost blockers. `bin/gstack-review-dispatch` closes both ends:
    byte-exact before anything was collected is void and counted (`voided=N` on the
    verdict line); one that produced an output stays `MISMATCH`. Then output hashes
    against the merged lines they produced, and each merged line against the finding collect
-   parses at that id's index from the unchanged output file, label and raw text byte for byte
+   parses at that id's index from the unchanged output file, its reader, label and raw text byte for byte
    (`merged_line_differs` on the OUTPUT and JUDGE rows otherwise, GST-541), so an edited
    merged.jsonl cannot lower a finding or swap its text. A recorded output file that is missing
    (`output_file_missing`), a judgment run on a merged file collect did not write