chore: mame recipes start at 0.177 now

The site's neogeo.zip line, the identification note and the recipe count sentence follow the 113 imported releases.

scripts/generate_site.py

@@ -6107,7 +6107,7 @@ def _romset_line(f: dict) -> str:
     MAME and FBNeo check the members of an archive by CRC32, never its own
     bytes or its member names: a set works with a release when it holds
     every CRC32 the release's recipe lists, extra members or not. The
-    main neogeo.zip, which every MAME from 0.190 to 0.289 loads, read "No
+    main neogeo.zip, which every MAME from 0.177 to 0.289 loads, read "No
     match" when names had to agree and no member could be extra. Empty
     when no recipe names the archive or the file is not on disk.
     """

scripts/romset_recipes.py

@@ -699,7 +699,7 @@ def main() -> int:
         )
         print(
             "  The label is the oldest version producing these bytes: a recipe "
-            "unchanged since 0.190 is counted there, not at its own version."
+            "unchanged since 0.177 is counted there, not at its own version."
         )
         by_recipe: dict[str, int] = defaultdict(int)
         for record in ident["identified"]:

tests/test_site_systems.py

@@ -752,7 +752,7 @@ class TheRomsetLineMatchesByCrc(unittest.TestCase):
         if main is None or not (REPO_ROOT / main["path"]).is_file():
             self.skipTest("the main neogeo.zip is not in this checkout")
         line = gs._romset_line(main)
-        self.assertIn("Holds every ROM of MAME 0.190 to 0.289", line)
+        self.assertIn("Holds every ROM of MAME 0.177 to 0.289", line)
         self.assertNotIn("No match", line)
 
 

wiki/tools.md

@@ -1520,10 +1520,10 @@ against. Every MAME release with a `-listxml` asset is imported, 0.177 to
 A `romof` parent's members are merged into the child, and members with no
 CRC32 are dropped: those are undumped and a real romset does not carry them.
 
-The store is compacted: 113 MAME versions produce 173,985 entries but only
-2,936 distinct recipes, since most sets do not change between releases. Each
-is kept once, `dats` listing every version that agrees and `dat` naming the
-earliest, so an identification reads as "unchanged since that version".
+The store is compacted: 113 MAME versions produce 173,985 entries but only 2,936
+distinct recipes, since most sets do not change between releases. Each is kept
+once, `dats` listing every version that agrees and `dat` naming the earliest, so
+an identification reads as "unchanged since that version".
 
 `--identify` answers what an archive on disk actually is: the version whose
 recipe reproduces it byte for byte. Step 1c of the pipeline prints how many