docs: describe a platform list without judging it

adding-a-platform said a platform's list leaves files out. It now says
the files its list does not name.

tests/test_doc_pages.py

@@ -1900,6 +1900,18 @@ class SkipFlagsNameTheSteps(unittest.TestCase):
                     self.assertEqual(set(re.findall(self.STEP, text)), steps)
 
 
+class APlatformListIsDescribedNotJudged(unittest.TestCase):
+    """adding-a-platform opened on files a platform's own list "leaves out",
+    read first by the maintainer of that platform: "does not name" says the
+    same without imputing an omission."""
+
+    def test_no_page_says_a_list_leaves_files_out(self):
+        pattern = re.compile(r"\blists? (?:leaves|left|leave) out\b")
+        for page in sorted(WIKI.glob("*.md")):
+            with self.subTest(page=page.name):
+                self.assertIsNone(pattern.search(page.read_text(encoding="utf-8")))
+
+
 class ArchivedIsWhatTheToolsDo(unittest.TestCase):
     """The README and the setup pages said an archived platform is no longer
     scraped on a schedule, and adding-a-platform said `active` feeds a CI

wiki/adding-a-platform.md

@@ -7,7 +7,7 @@ order: 20
 
 Adding a platform gives its users a pack and a one-line install with the files
 their setup checks, in the place it checks them, plus every file its emulators
-need that its own list leaves out. The work is to read how the platform
+need that its own list does not name. The work is to read how the platform
 declares and checks BIOS files, then teach this project to read that
 declaration. A platform can be a frontend like Batocera, a manager like EmuDeck
 or a firmware database like BizHawk.