docs: write prose without dashes or semicolons

Profiles, the wiki, comments, docstrings, command output and schema descriptions carried em-dashes, clause-joining semicolons, unicode arrows, box-drawing banners and check-mark glyphs. Each sentence was rewritten rather than having its character swapped. Hashes, paths, source_ref values and every cited file:line are unchanged, which a comparison of each parsed profile against the previous revision confirms.

validate_pr comments now say PASS and FAIL in words, and source_ref values in a profile's structured blocks render as code. test_prose_style fails if any of these comes back, in tracked files or in the generated site.

scripts/auto_fetch.py

@@ -123,7 +123,7 @@ def _accepted(entry: dict, field: str) -> set[str]:
     """Every value an entry accepts for a hash field.
 
     A profile lists several revisions as a YAML list (daedalusx64's
-    n64.psh), a platform as a comma-separated string; read as one value,
+    n64.psh), a platform as a comma-separated string. Read as one value,
     the list stopped the run with an unhashable-type error.
     """
     value = entry.get(field)
@@ -264,7 +264,7 @@ def step4_search_archive_org(entry: dict) -> bytes | None:
     sha1s = sorted(_accepted(entry, "sha1"))
     if not sha1s:
         return None
-    # Each accepted revision is a query of its own; archive.org matches one.
+    # Each accepted revision is a query of its own: archive.org matches one.
     sha1 = " OR ".join(f"sha1:{value}" for value in sha1s)
 
     search_url = (