docs: state each verification rule once

architecture.md drew path_suffix ahead of SHA1 and listed a core
resolution that missed the retroarch list entry and built_by. Both now
link to the one statement that matches common.py. The Recalbox table
read hashMatchMandatory into verify.py, which never reads it, and
md5_composite hashes member contents, not member MD5s
(Zip.cpp:71-96). The validation index is built from the platform's
resolved profiles only. The requirement table gains the fields that
make a platform YAML reversible, and pages that name a platform list
say what changes rather than judging it.

wiki/adding-a-scraper.md

@@ -425,19 +425,19 @@ be missing from the round trip.
 # Scrape upstream -> platform YAML
 python -m scripts.scraper.myplatform_scraper --output platforms/myplatform.yml
 
-# Rewrite the platform's own file, corrected
+# Rewrite the platform's own file with the changes applied
 python scripts/export_native.py --platform myplatform --fetch \
     --output-dir tmp/native
 
 # Compare with the file upstream publishes, cached by --fetch
-diff .cache/upstream-native/myplatform/<their file> \
-     tmp/native/myplatform/<their file>
+diff .cache/upstream-native/myplatform/<original file> \
+     tmp/native/myplatform/<original file>
 ```
 
-Every line in that diff should be a correction you can defend. A line that
-merely reshapes their formatting means the scraper lost something the
-exporter then had to invent: add it to the requirement instead, through
-`native_path`, `native_system` or the `native` dict.
+Every line of that diff is a change the emulator source supports. A line that
+only reshapes the original formatting means the scraper lost something the
+exporter then had to invent: record it in the requirement instead, through
+the fields listed in [BiosRequirement fields](adding-a-platform.md#biosrequirement-fields).
 
 ### Common issues