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/hashing.py

@@ -1,6 +1,6 @@
 """Content digests.
 
-SHA-1 is the collection's primary key; the rest are what the various
+SHA-1 is the collection's primary key. The rest are what the various
 frontends check against."""
 
 from __future__ import annotations
@@ -15,7 +15,7 @@ from pathlib import Path
 _ALL_ALGORITHMS = frozenset({"sha1", "md5", "sha256", "crc32", "adler32"})
 
 # (path, inode, size, mtime_ns, ctime_ns) -> the digests read so far.
-# verify --all hashed GB_dmg.bin 13 times, once per platform and entry; the
+# verify --all hashed GB_dmg.bin 13 times, once per platform and entry. The
 # bytes are still read from disk, once per file and change.
 _hash_cache: dict[tuple, dict[str, str]] = {}
 
@@ -118,7 +118,7 @@ def parse_hash_list(raw: str | list | int | None) -> list[str]:
     """Normalize any hash field into its accepted values, lowercase.
 
     A field holds one value, a YAML list, or one comma-joined string
-    (Recalbox md5, mesence's four sha256 for one entry); a crc32 may carry
+    (Recalbox md5, mesence's four sha256 for one entry), and a crc32 may carry
     a 0x prefix. Read one way here, the resolver, the gap report and
     profile_sync accept the same values.
     """